Network Working Group M. Garcia-Martin
Internet-Draft Nokia
Expires: August 3, 2004 February 3, 2004
The AAA and AAAS Uniform Resource Identifier (URI) schemes
draft-garcia-aaa-uri-00
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at 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 August 3, 2004.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
This memo normatively defines the ABNF of the AAA and AAAS URI
schemes and provides instructions to IANA to register them in the
namespace of registered URI schemes.
Garcia-Martin Expires August 3, 2004 [Page 1]
Internet-Draft AAA URI February 2004
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The AAA and AAAS URIs . . . . . . . . . . . . . . . . . . . . . 3
4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5
Normative References . . . . . . . . . . . . . . . . . . . . . . 5
Informative References . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . 7
Garcia-Martin Expires August 3, 2004 [Page 2]
Internet-Draft AAA URI February 2004
1. Introduction
RFC 3588 [11] describes the Diameter base protocol for
authentication, authorization and accounting purposes. The RFC
provides for the existence of a DiameterURI AVP that contains a AAA
or AAAS URI. RFC 3588 [11] does not provide, though, instructions to
IANA to register either of those URI schemes in the Official IANA
Registry of URI schemes (available at http://www.iana.org/
assignments/uri-schemes/).
This memo defines the syntax of the AAA and AAAS URI for the purpose
of the registration of both URIs in the Official IANA Registry of URI
schemes. The syntax of both URIs defined in this document is
compatible with that initially defined in RFC 3588.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [1] and
indicate requirement levels for compliant implementations.
3. The AAA and AAAS URIs
This section defines the syntax of the AAA and AAAS URI schemes in
augmented Backus-Naur Form (BNF) defined in RFC 2234 [2]. The syntax
in this section adopts the definitions of "absoluteURI", "host" and
"port" from RFC 2396 [3] and their corresponding updates specified in
RFC 2732 [4].
Both the AAA and the AAAS URI schemes are used to identify resources
related to authentication, authorization and accounting (AAA)
functions that are accessed with AAA protocols such as RADIUS [9] or
Diameter [11].
The AAA URI scheme indicates that transport layer security is not
required or used. The AAAS URI scheme indicates the requirement to
the AAA protocol to use a transport protocol that provides security
functions, such as TLS [8].
There URIs use he USASCII character encoding scheme.
The AAA and AAA URI schemes have the following ABNF:
AAA-URI = "aaa://" host [":" port] [ transport ] [ protocol ]
AAAS-URI = "aaas://" host [":" port] [ transport ] [ protocol ]
Garcia-Martin Expires August 3, 2004 [Page 3]
Internet-Draft AAA URI February 2004
The semantics and syntax of "host" and "port" are defined in RFC 2396
[3] and updated in RFC 2732 [4]. If "host" includes a "hostname" (as
opposed to an "IPv4address" or an "IPv6address") then it MUST be a
Fully Qualified Domain Name. If the port is empty or not given, the
default port allocated to Diameter (3868) is assumed.
OPEN ISSUE: Note that the initial definition of the AAA/AAAS URIs
in RFC 3588 mandate an FQDN. Now we have included "host", that can
be either a hostname, IPv4address or IPv6address (see RFC 2396 and
RFC 2732 for details). Doest the inclusion of IP addresses
represent a problem?
transport = ";transport=" transport-protocol
transport-protocol = ( "tcp" / "sctp" / "udp" )
OPEN ISSUE: As TLS over TCP and TLS over SCTP are transpor
protocols, should we add them to the list of transport protocols
above?
TCP refers to the Transmission Control Protocol specified in RFC 793
[6]. SCTP refers to the Stream Control Transport Protocol specified
in RFC 2960 [10]. UDP refers to the User Datagram Protocol specified
in RFC 768 [5]. TLS refers to the Transport Layer Security over TCP
specified in RFC 2246 [8]. If the transport parameter is empty or not
given, the default transport protocol, SCTP, is assumed
protocol = ";protocol=" aaa-protocol
aaa-protocol = ( "diameter" / "radius" / "tacacs+" )
The token "diameter" refers to the Diameter base protocol specified
in RFC 3588 [11]. The token "radius" refers to the RADIUS protocol
specified in RADIUS [9]. The token "tacacs+" refers to the TACACS
protocol defined in RFC 1492 [7]. If the protocol parameter is not
given or empty, the default AAA protocol, Diameter, is assumed.
Diameter does not provide support for UDP as a transport protocol,
therefore, UDP MUST NOT be used when Diameter is the AAA protocol.
4. Examples
The following are examples of valid AAA and AAAS URIs:
aaa://host.example.com;transport=tcp
aaas://host.example.com;transport=tls;protocol=diameter
aaa://host.example.com;protocol=diameter
aaa://host.example.com:6666;protocol=diameter
aaa://host.example.com:6666;transport=tcp;protocol=diameter
Garcia-Martin Expires August 3, 2004 [Page 4]
Internet-Draft AAA URI February 2004
aaa://host.example.com:1813;transport=udp;protocol=radius
5. IANA Considerations
This memo instructs IANA the following actions:
o To include "aaa" and "aaas" in the Official IANA Registry of URI
Schemes, http://www.iana.org/assignments/uri-schemes
o To create a new "transport" sub-registry under http://
www.iana.org/assignments/aaa-parameters, whose values are as per
Section Section 3.
o To create a mew "protocol" sub-registry under http://www.iana.org/
assignments/aaa-parameters, whose values are as defined Section
Section 3.
Contact information: IETF AAA Working group. In case the WG does no
exist anymore, any person appointed by the IETF Operations and
Management Area Director.
Registered-by: Miguel Garcia, miguel.an.garcia@nokia.com
Change control:
OPEN ISSUE: Need to define the procedure to add new parameters or
tokens to existing parameters to those URIs. Is an expert review
needed?
6. Security Considerations
This memo does not specify a protocol, but the syntax of the AAA and
AAAS URI. The AAAS URI is used to indicate that a secured transport
layer is required, such as TLS [8]. These URIs are transport
independent, therefore, each particular protocol defines its own
security considerations.
7. Acknowledgements
The auhor would to thank Eero Pasinen and John Loughney for providing
an initial set of comments.
Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
Garcia-Martin Expires August 3, 2004 [Page 5]
Internet-Draft AAA URI February 2004
[3] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[4] Hinden, R., Carpenter, B. and L. Masinter, "Format for Literal
IPv6 Addresses in URL's", RFC 2732, December 1999.
Informative References
[5] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August
1980.
[6] Postel, J., "Transmission Control Protocol", STD 7, RFC 793,
September 1981.
[7] Finseth, C., "An Access Control Protocol, Sometimes Called
TACACS", RFC 1492, July 1993.
[8] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC
2246, January 1999.
[9] Rigney, C., Willens, S., Rubens, A. and W. Simpson, "Remote
Authentication Dial In User Service (RADIUS)", RFC 2865, June
2000.
[10] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer,
H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson,
"Stream Control Transmission Protocol", RFC 2960, October 2000.
[11] Calhoun, P., Loughney, J., Guttman, E., Zorn, G. and J. Arkko,
"Diameter Base Protocol", RFC 3588, September 2003.
Author's Address
Miguel A. Garcia-Martin
Nokia
P.O. Box 407
NOKIA GROUP, FIN 00045
Finland
Phone: +358 50 480 4586
EMail: miguel.an.garcia@nokia.com
Garcia-Martin Expires August 3, 2004 [Page 6]
Internet-Draft AAA URI February 2004
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
Garcia-Martin Expires August 3, 2004 [Page 7]
Internet-Draft AAA URI February 2004
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Garcia-Martin Expires August 3, 2004 [Page 8]