< draft-yegin-pana-unspecified-addr-01.txt   draft-yegin-pana-unspecified-addr-02.txt >
Network Working Group A. Yegin Network Working Group A. Yegin
Internet-Draft Samsung Internet-Draft Samsung
Intended status: Standards Track Y. Ohba Intended status: Standards Track Y. Ohba
Expires: September 9, 2010 Toshiba Expires: March 14, 2011 Toshiba
L. Morand L. Morand
Orange Labs Orange Labs
J. Kaippallimalil J. Kaippallimalil
Huawei USA Huawei USA
March 8, 2010 September 10, 2010
Protocol for Carrying Authentication for Network Access (PANA) with IPv4 Protocol for Carrying Authentication for Network Access (PANA) with IPv4
Unspecified Address Unspecified Address
draft-yegin-pana-unspecified-addr-01 draft-yegin-pana-unspecified-addr-02
Abstract Abstract
This document defines how PANA client (PaC) can perform PANA This document defines how PANA client (PaC) can perform PANA
authentication prior to configuring an IP address. authentication prior to configuring an IP address.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 This Internet-Draft will expire on March 14, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 9, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Specification of Requirements . . . . . . . . . . . . . . . 3 1.1. Specification of Requirements . . . . . . . . . . . . . . . 3
2. Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. PaC Behavior . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. PaC Behavior . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. PAA Behavior . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. PAA Behavior . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. AVP Definition . . . . . . . . . . . . . . . . . . . . . . . . 6 5. AVP Definition . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Token AVP . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.1. Token AVP . . . . . . . . . . . . . . . . . . . . . . . . . 6
skipping to change at page 7, line 47 skipping to change at page 7, line 47
When the PAA is not capable of L2-unicasting PANA messages to the When the PAA is not capable of L2-unicasting PANA messages to the
target PaC, other nodes on the same subnet can receive those target PaC, other nodes on the same subnet can receive those
messages. This may pose a risk if there is any confidential data messages. This may pose a risk if there is any confidential data
exposed in the messages. Typically no such exposure exists as PANA, exposed in the messages. Typically no such exposure exists as PANA,
EAP, an EAP methods are defined in a way they can also be used in EAP, an EAP methods are defined in a way they can also be used in
wireless networks where snooping is always a possibility. wireless networks where snooping is always a possibility.
8. IANA Considerations 8. IANA Considerations
As described in Section 5.1 and following the new IANA allocation As described in Section 5.1 and following the new IANA allocation
policy on PANA message [I-D.arkko-pana-iana], a new AVP Code for policy on PANA message [RFC5872], a new AVP Code for Token AVP needs
Token AVP needs to be assigned by IANA. to be assigned by IANA.
9. Acknowledgments 9. Acknowledgments
TBD. TBD.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A. [RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A.
skipping to change at page 8, line 25 skipping to change at page 8, line 25
Access (PANA)", RFC 5191, May 2008. Access (PANA)", RFC 5191, May 2008.
[RFC5193] Jayaraman, P., Lopez, R., Ohba, Y., Parthasarathy, M., and [RFC5193] Jayaraman, P., Lopez, R., Ohba, Y., Parthasarathy, M., and
A. Yegin, "Protocol for Carrying Authentication for A. Yegin, "Protocol for Carrying Authentication for
Network Access (PANA) Framework", RFC 5193, May 2008. Network Access (PANA) Framework", RFC 5193, May 2008.
[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.
Levkowetz, "Extensible Authentication Protocol (EAP)", Levkowetz, "Extensible Authentication Protocol (EAP)",
RFC 3748, June 2004. RFC 3748, June 2004.
[I-D.arkko-pana-iana] [RFC5872] Arkko, J. and A. Yegin, "IANA Rules for the Protocol for
Arkko, J. and A. Yegin, "IANA Rules for PANA (Protocol for Carrying Authentication for Network Access (PANA)",
Carrying Authentication for Network Access)", RFC 5872, May 2010.
draft-arkko-pana-iana-02 (work in progress),
February 2010.
10.2. Informative References 10.2. Informative References
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets", E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996. BCP 5, RFC 1918, February 1996.
[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.
 End of changes. 8 change blocks. 
21 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/