draft-ietf-radext-rfc2486bis-00.txt | draft-ietf-radext-rfc2486bis-01.txt | |||
---|---|---|---|---|
Network Working Group B. Aboba | Network Working Group B. Aboba | |||
Internet-Draft Microsoft | Internet-Draft Microsoft | |||
Expires: March 31, 2005 M. Beadles | Expires: April 19, 2005 M. Beadles | |||
SmartPipes | SmartPipes | |||
J. Arkko | J. Arkko | |||
Ericsson | Ericsson | |||
P. Eronen | P. Eronen | |||
Nokia | Nokia | |||
September 30, 2004 | October 19, 2004 | |||
The Network Access Identifier | The Network Access Identifier | |||
draft-ietf-radext-rfc2486bis-00 | draft-ietf-radext-rfc2486bis-01 | |||
Status of this Memo | Status of this Memo | |||
This document is an Internet-Draft and is subject to all provisions | This document is an Internet-Draft and is subject to all provisions | |||
of section 3 of RFC 3667. By submitting this Internet-Draft, each | of section 3 of RFC 3667. By submitting this Internet-Draft, each | |||
author represents that any applicable patent or other IPR claims of | author represents that any 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 is aware have been or will be disclosed, and any of | |||
which he or she become aware will be disclosed, in accordance with | which he or she become aware will be disclosed, in accordance with | |||
RFC 3668. | RFC 3668. | |||
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 March 31, 2005. | This Internet-Draft will expire on April 19, 2005. | |||
Copyright Notice | Copyright Notice | |||
Copyright (C) The Internet Society (2004). | Copyright (C) The Internet Society (2004). | |||
Abstract | Abstract | |||
In order to provide roaming services, it is necessary to have a | In order to provide roaming services, it is necessary to have a | |||
standardized method for identifying users. This document defines the | standardized method for identifying users. This document defines the | |||
syntax for the Network Access Identifier (NAI), the user identity | syntax for the Network Access Identifier (NAI), the user identity | |||
skipping to change at page 6, line 10 | skipping to change at page 6, line 10 | |||
c =/ %x5f ; '_' allowed | c =/ %x5f ; '_' allowed | |||
c =/ %x60 ; '`' allowed | c =/ %x60 ; '`' allowed | |||
c =/ %x61-7a ; 'a'-'z' allowed | c =/ %x61-7a ; 'a'-'z' allowed | |||
c =/ %x7b ; '{' allowed | c =/ %x7b ; '{' allowed | |||
c =/ %x7c ; '|' allowed | c =/ %x7c ; '|' allowed | |||
c =/ %x7d ; '}' allowed | c =/ %x7d ; '}' allowed | |||
c =/ %x7e ; '~' allowed | c =/ %x7e ; '~' allowed | |||
; DEL not allowed | ; DEL not allowed | |||
c =/ %x80-ff ; UTF-8 allowed (not in RFC 2486) | c =/ %x80-ff ; UTF-8 allowed (not in RFC 2486) | |||
; c must also satisfy rules in Section 2.4 | ; c must also satisfy rules in Section 2.4 | |||
x = %x00-7F ; all 128 ASCII characters, no exception | x = %x00-FF ; all 128 ASCII characters, no exception; | |||
; as well as all UTF-8 characters (this | ||||
; was not allowed in RFC 2486) | ||||
realm = 1*( label "." ) label | realm = 1*( label "." ) label | |||
label = let-dig * (ldh-str) | label = let-dig * (ldh-str) | |||
ldh-str = *( alpha / digit / "-" ) let-dig | ldh-str = *( alpha / digit / "-" ) let-dig | |||
let-dig = alpha / digit | let-dig = alpha / digit | |||
alpha = %x41-5A ; 'A'-'Z' | alpha = %x41-5A ; 'A'-'Z' | |||
alpha =/ %x61-7A ; 'a'-'z' | alpha =/ %x61-7A ; 'a'-'z' | |||
digit = %x30-39 ; '0'-'9' | digit = %x30-39 ; '0'-'9' | |||
2.2 NAI Length Considerations | 2.2 NAI Length Considerations | |||
skipping to change at page 8, line 47 | skipping to change at page 8, line 47 | |||
NAI, the other realm MUST convert the format back to | NAI, the other realm MUST convert the format back to | |||
"user@homerealm.example.net" when passing the NAI forward, as well as | "user@homerealm.example.net" when passing the NAI forward, as well as | |||
applying appropriate AAA routing for the transaction. | applying appropriate AAA routing for the transaction. | |||
The conversion process may apply also recursively. That is, after | The conversion process may apply also recursively. That is, after | |||
the conversion the result may still have one or more '!' characters | the conversion the result may still have one or more '!' characters | |||
in the username. For instance, the NAI | in the username. For instance, the NAI | |||
other2.example.net!home.example.net!user@other1.example.net | other2.example.net!home.example.net!user@other1.example.net | |||
would first be converted in other1.example net to | would first be converted in other1.example.net to | |||
home.example.net!user@other2.example.net | home.example.net!user@other2.example.net | |||
and then at other2.example.net finally to | and then at other2.example.net finally to | |||
user@homerealm.example.net | user@homerealm.example.net | |||
2.8 Examples | 2.8 Examples | |||
Examples of valid Network Access Identifiers include: | Examples of valid Network Access Identifiers include: | |||
skipping to change at page 15, line 12 | skipping to change at page 15, line 12 | |||
o Several clarifications and improvements have been incorporated to | o Several clarifications and improvements have been incorporated to | |||
the ABNF specification for NAIs. | the ABNF specification for NAIs. | |||
Appendix B. Acknowledgements | Appendix B. Acknowledgements | |||
Thanks to Glen Zorn for many useful discussions of this problem | Thanks to Glen Zorn for many useful discussions of this problem | |||
space, and for Farid Adrangi and others for suggesting mediating | space, and for Farid Adrangi and others for suggesting mediating | |||
network representation in NAIs. Jonathan Rosenberg reported the BNF | network representation in NAIs. Jonathan Rosenberg reported the BNF | |||
error. Dale Worley suggested clarifications of the x and special BNF | error. Dale Worley suggested clarifications of the x and special BNF | |||
entries. Arne Norefors reported the length differences between RFC | entries. Arne Norefors reported the length differences between RFC | |||
2486 and RFC 2865. Kalle Tammela, Stefaan De Cnodder, Nagi Jonnala, | 2486 and RFC 2865. Paul Hoffman helped with the international | |||
Bert Wijnen, Blair Bullock, Yoshihiro Ohba, and Richard Perlman | character set issues. Kalle Tammela, Stefaan De Cnodder, Nagi | |||
provided many useful comments on this draft. The ABNF validator at | Jonnala, Bert Wijnen, Blair Bullock, Yoshihiro Ohba, Ignacio Goyret, | |||
http://www.apps.ietf.org/abnf.html was used to verify the syntactic | and Richard Perlman provided many useful comments on this draft. The | |||
correctness of the ABNF in Section 2.1. | ABNF validator at http://www.apps.ietf.org/abnf.html was used to | |||
verify the syntactic correctness of the ABNF in Section 2.1. | ||||
Intellectual Property Statement | Intellectual Property Statement | |||
The IETF takes no position regarding the validity or scope of any | The IETF takes no position regarding the validity or scope of any | |||
Intellectual Property Rights or other rights that might be claimed to | Intellectual Property Rights or other rights that might be claimed to | |||
pertain to the implementation or use of the technology described in | pertain to the implementation or use of the technology described in | |||
this document or the extent to which any license under such rights | this document or the extent to which any license under such rights | |||
might or might not be available; nor does it represent that it has | might or might not be available; nor does it represent that it has | |||
made any independent effort to identify any such rights. Information | made any independent effort to identify any such rights. Information | |||
on the procedures with respect to rights in RFC documents can be | on the procedures with respect to rights in RFC documents can be | |||
End of changes. | ||||
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |