draft-ietf-pana-pana-09.txt   draft-ietf-pana-pana-10.txt 
PANA Working Group D. Forsberg PANA Working Group D. Forsberg
Internet-Draft Nokia Internet-Draft Nokia
Expires: January 12, 2006 Y. Ohba (Ed.) Expires: January 17, 2006 Y. Ohba (Ed.)
Toshiba Toshiba
B. Patil B. Patil
Nokia Nokia
H. Tschofenig H. Tschofenig
Siemens Siemens
A. Yegin A. Yegin
Samsung Samsung
July 11, 2005 July 16, 2005
Protocol for Carrying Authentication for Network Access (PANA) Protocol for Carrying Authentication for Network Access (PANA)
draft-ietf-pana-pana-09 draft-ietf-pana-pana-10
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 41 skipping to change at page 1, line 41
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 12, 2006. This Internet-Draft will expire on January 17, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document defines the Protocol for Carrying Authentication for This document defines the Protocol for Carrying Authentication for
Network Access (PANA), a link-layer agnostic transport for Extensible Network Access (PANA), a link-layer agnostic transport for Extensible
Authentication Protocol (EAP) to enable network access authentication Authentication Protocol (EAP) to enable network access authentication
skipping to change at page 52, line 47 skipping to change at page 52, line 47
8.10 Notification AVP 8.10 Notification AVP
The Notification AVP (AVP Code 10) is optionally used to convey a The Notification AVP (AVP Code 10) is optionally used to convey a
displayable message sent by either the PaC or the PAA. It can be displayable message sent by either the PaC or the PAA. It can be
included in any message, whether it is a request or answer. In case included in any message, whether it is a request or answer. In case
a notification needs to be sent but there is no outgoing PANA message a notification needs to be sent but there is no outgoing PANA message
to deliver this AVP, a PANA-Update-Request that only carries a to deliver this AVP, a PANA-Update-Request that only carries a
Notification AVP SHOULD be generated. Notification AVP SHOULD be generated.
The 'M' bit in the AVP header of this AVP MUST NOT be set.
Receipt this AVP does not change PANA state. Receipt this AVP does not change PANA state.
AVP data is of type OctetString and it contains UTF-8 encoded ISO AVP data is of type OctetString and it contains UTF-8 encoded ISO
10646 characters [RFC2279]. The length of the displayable message is 10646 characters [RFC2279]. The length of the displayable message is
determined by the AVP Length field. The message MUST NOT be null determined by the AVP Length field. The message MUST NOT be null
terminated. terminated.
8.11 Post-PANA-Address-Configuration (PPAC) AVP 8.11 Post-PANA-Address-Configuration (PPAC) AVP
The PPAC AVP (AVP Code 11) is used for conveying the available types The PPAC AVP (AVP Code 11) is used for conveying the available types
skipping to change at page 71, line 9 skipping to change at page 71, line 9
The PANA protocol supports the ability for both the PaC and the PAA The PANA protocol supports the ability for both the PaC and the PAA
to transmit a tear-down message before the session lifetime expires. to transmit a tear-down message before the session lifetime expires.
This message causes state removal, a stop of the accounting procedure This message causes state removal, a stop of the accounting procedure
and removes the installed per-PaC state on the EP(s). This message and removes the installed per-PaC state on the EP(s). This message
is cryptographically protected when PANA SA is present. is cryptographically protected when PANA SA is present.
12. Acknowledgments 12. Acknowledgments
We would like to thank Jari Arkko, Mohan Parthasarathy, Julien We would like to thank Jari Arkko, Mohan Parthasarathy, Julien
Bournelle, Rafael Marin Lopez, Pasi Eronen, Randy Turner, Erik Bournelle, Rafael Marin Lopez, Pasi Eronen, Randy Turner, Erik
Nordmark, Lionel Morand, Avi Lior, Susan Thomson, Giaretta Gerardo Nordmark, Lionel Morand, Avi Lior, Susan Thomson, Giaretta Gerardo,
and all members of the PANA working group for their valuable comments Joseph Salowey and all members of the PANA working group for their
to this document. valuable comments to this document.
13. References 13. References
13.1 Normative References 13.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997. RFC 2131, March 1997.
skipping to change at page 73, line 20 skipping to change at page 73, line 20
"Protocol for Carrying Authentication for Network Access "Protocol for Carrying Authentication for Network Access
(PANA) Requirements", RFC 4058, May 2005. (PANA) Requirements", RFC 4058, May 2005.
[I-D.ietf-eap-keying] [I-D.ietf-eap-keying]
Aboba, B., "Extensible Authentication Protocol (EAP) Key Aboba, B., "Extensible Authentication Protocol (EAP) Key
Management Framework", draft-ietf-eap-keying-06 (work in Management Framework", draft-ietf-eap-keying-06 (work in
progress), April 2005. progress), April 2005.
[I-D.ietf-pana-ipsec] [I-D.ietf-pana-ipsec]
Parthasarathy, M., "PANA Enabling IPsec based Access Parthasarathy, M., "PANA Enabling IPsec based Access
Control", draft-ietf-pana-ipsec-06 (work in progress), Control", draft-ietf-pana-ipsec-07 (work in progress),
May 2005. July 2005.
[I-D.ietf-pana-framework] [I-D.ietf-pana-framework]
Jayaraman, P., "PANA Framework", Jayaraman, P., "PANA Framework",
draft-ietf-pana-framework-04 (work in progress), May 2005. draft-ietf-pana-framework-05 (work in progress),
July 2005.
[I-D.ietf-pana-snmp] [I-D.ietf-pana-snmp]
Mghazli, Y., "SNMP usage for PAA-EP interface", Mghazli, Y., "SNMP usage for PAA-EP interface",
draft-ietf-pana-snmp-04 (work in progress), July 2005. draft-ietf-pana-snmp-04 (work in progress), July 2005.
[I-D.ietf-eap-statemachine] [I-D.ietf-eap-statemachine]
Vollbrecht, J., Eronen, P., Petroni, N., and Y. Ohba, Vollbrecht, J., Eronen, P., Petroni, N., and Y. Ohba,
"State Machines for Extensible Authentication Protocol "State Machines for Extensible Authentication Protocol
(EAP) Peer and Authenticator", (EAP) Peer and Authenticator",
draft-ietf-eap-statemachine-06 (work in progress), draft-ietf-eap-statemachine-06 (work in progress),
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/