1. PANA Requirements and Terminology - IETF54 -

2. PANA WG, IETF 54, Requirements and Terminology draft-ietf-pana-requirements-02.txt Changes Comments/questions

3. PANA WG, IETF 54, Requirements and Terminology Authentication Protocol Not invent a new authentication protocol Current thinking: EAP is sufficient If extensions to EAP needed: –PANA WG will define requirements, not solutions

4. PANA WG, IETF 54, Requirements and Terminology EAP Issues Device Identifier needs to be integrity protected in PANA request sent by PaC –EAP doesn’t do that, but do we really need this? If per-packet auth/encryption is not used, spoofing can happen anytime If per-packet auth/encryption is used, checking DI is redundant

5. PANA WG, IETF 54, Requirements and Terminology PAA and EP PAA needs to communicate filters, etc. to EP PAA and EP are co-located –Anything else is outside the scope of PANA

6. PANA WG, IETF 54, Requirements and Terminology PAA Location On the same IP link as PaC Generally on the first-hop router Discovery mechanism needed

7. PANA WG, IETF 54, Requirements and Terminology IP Address Configuration PaC can use PANA only after it has usable IP address (via DHCP, address autoconfig, etc..) If PaC needs to reconfigure a new IP address after PANA, co-located PAA/router/dhcp_server will be helpful

8. PANA WG, IETF 54, Requirements and Terminology Simplifying Assumptions Internet PaC PAA/ EP/ First hop router (/DHCP) PANA

9. PANA WG, IETF 54, Requirements and Terminology Separation Internet PaC PAA First hop router (/DHCP) EP PANA

10. PANA WG, IETF 54, Requirements and Terminology Heartbeat Required for links that do not provide disconnect indication Optional usage

11. PANA WG, IETF 54, Requirements and Terminology Comments/Issues/Questions?