1. March 20, 2006IETF65 PANA WG PANA Specification Updates (draft-ietf-pana-pana-11.txt) Yoshihiro Ohba (yohba@tari.toshiba.com)

2. Issues 23 issues are part of AD review 2 other issues Only major issues are explained

3. Issues on stateless PAA discovery Issue 223: Cookie example –Issue Cookie example is not useful –Resolution: Cookie example was removed Reference to RFC 4083 is added for randomness of cookie value Issue 224: Concern on stateless discovery –Issue: Is complexity of stateless discovery worth adding? –Resolution: Rejected because the stateless feature is more important in multi-hop scenarios Issue 225: Stateless discovery indication –Issue: There is no explicit indication of stateless discovery Only insertion of a Cookie AVP implicitly indicates stateless discovery –Resolution: Added ‘L’-flag in PANA header

4. Issue 240: PaC updating its IP address Issue: When a PaC moves to a new subnet, not only IP address but also device id may change –This can happens when IP address is used as device id –PANA-Update exchange should support this Resolution: –Added optional Device-Id AVP in PUR to update PaC’s device id –Added Device-Id AVP in PUA to update the device identifier(s) of EP(s)

5. Issues 169 and 245: PANA lower layer ciphering and KDF Issue: –HMAC-SHA1 as KDF without iteration does not produce 64-octet key –KDF should not be hard-coded in the spec Resolution: –Use of IKEv2 prf+ to generate keys of arbitrary length based on iteration of a base algorithm –The hash algorithm used for prf+ is carried in Algorithm AVP The first 2 bytes of the value field contains the hash algorithm The last 2 bytes carries integrity algorithm used for generating AUTH AVP (MAC AVP is renamed to AUTH AVP based on Issue 221) The algorithm code space is defined in IKEv2 and managed by IANA –Mandatory supported base algorithms for prf+ HMAC-SHA1 for both key derivation and integrity algorithms

6. Other issues Issue 227: Rate limiting to responding to request –Issue: Missing details on rate limitation –Resolution: Rate limiting to responding to duplicate request is a “MUST” Rate limiting to responding to non-duplicate Ping-Request is a “MAY” Issue 235 Nonces –Issues: What is the suggested length of nonce? –Resolution: The nonce length is at least the length of the PRF key