ITU-T A.5 reference justification

Home : ITU-T Home : ITU-T Work Programme : Q.3301.1 v3

ITU-T A.5 justification information for referenced document IETF RFC 4005 (2005) in draft Q.3301.1 v3

Clear description of the referenced document:

Name:	IETF RFC 4005 (2005)
Title:	Diameter Network Access Server Application.

Status of approval:

Published (2005-05)

Justification for the specific reference:

6.2.1Initial reservation for a session 9.1Commands 9.1.1AA-Request (AAR) command 9.1.2AA-Answer (AAA) command

Current information, if any, about IPR issues:

Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=4005

Other useful information describing the "Quality" of the document:

Proposed Standard

The degree of stability or maturity of the document:

Proposed Standard

Relationship with other existing or emerging documents:

References within the referenced RFCs are listed under item (8).

Any explicit references within that referenced document should also be listed:

Normative References/
/
[BASE] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and/
J. Arkko, "Diameter Base Protocol", RFC 3588,/
September 2003./
/
[DiamTrans] Aboba, B. and J. Wood, "Authentication, Authorization/
and Accounting (AAA) Transport Profile", RFC 3539,/
June 2003./
/
[RADIUS] Rigney, C., Willens, S., Rubens, A., and W. Simpson,/
"Remote Authentication Dial In User Service (RADIUS)",/
RFC 2865, June 2000./
/
[RADIUSTypes] IANA, "RADIUS Types", URL:/
http://www.iana.org/assignments/radius-types/
/
[RADIUSIPv6] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6",/
RFC 3162, August 2001./
/
[IPv6Addr] Nerenberg, L., "IMAP4 Binary Content Extension", RFC/
3516, April 2003./
/
[PPPCHAP] Simpson, W., "PPP Challenge Handshake Authentication/
Protocol (CHAP)", RFC 1994, August 1996./
/
/
[IANAConsid] Narten, T. and H. Alvestrand, "Guidelines for Writing/
an IANA Considerations Section in RFCs", BCP 26, RFC/
2434, October 1998./
/
[IANA] IANA Assigned Numbers Database, URL:/
http://www.iana.org/numbers.html/
/
[Keywords] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[ANITypes] NANPA Number Resource Info, ANI Assignments, URL:/
http://www.nanpa.com/number_resource_info//
ani_ii_assignments.html/
/
Informative References/
/
[RADIUSAcct] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000./
/
[RADIUSExt] Rigney, C., Willats, W., and P. Calhoun, "RADIUS/
Extensions", RFC 2869, June 2000./
/
[RADTunnels] Zorn, G., Leifer, D., Rubens, A., Shriver, J.,/
Holdrege, M., and I. Goyret, "RADIUS Attributes for/
Tunnel Protocol Support", RFC 2868, June 2000./
/
[RADTunlAcct] Zorn, G., Aboba, B., and D. Mitton, "RADIUS Accounting/
Modifications for Tunnel Protocol Support", RFC 2867,/
June 2000./
/
[RADDynAuth] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B./
Aboba, "Dynamic Authorization Extensions to Remote/
Authentication Dial In User Service (RADIUS)", RFC/
3576, July 2003./
/
[RADIUSIANA] Aboba, B., "IANA Considerations for RADIUS (Remote/
Authentication Dial In User Service)", RFC 3575, July/
2003./
/
[NASModel] Mitton, D. and M. Beadles, "Network Access Server/
Requirements Next Generation (NASREQNG) NAS Model",/
RFC 2881, July 2000./
/
[NASCriteria] Beadles, M. and D. Mitton, "Criteria for Evaluating/
Network Access Server Protocols", RFC 3169, September/
2001./
/
/
[AAACriteria] Aboba, B., Calhoun, P., Glass, S., Hiller, T., McCann,/
P., Shiino, H., Zorn, G., Dommety, G., Perkins, C.,/
Patil, B., Mitton, D., Manning, S., Beadles, M.,/
Walsh, P., Chen, X., Sivalingham, S., Hameed, A.,/
Munson, M., Jacobs, S., Lim, B., Hirschman, B., Hsu,/
R., Xu, Y., Campbell, E., Baba, S., and E. Jaques,/
"Criteria for Evaluating AAA Protocols for Network/
Access", RFC 2989, November 2000./
/
[DiamEAP] Eronen, P., "Diameter EAP Application", Work in/
Progress, May 2004./
/
[DiamCMS] Calhoun, P., Bulley, W., and S. Farrell, "Diameter CMS/
Security Application", Work in Progress, March 2002./
/
[DiamMIP] Calhoun, P., Johansson, T., Perkins, C., Hiller, T.,/
and P. McCann "Diameter Mobile IPv4 Application", RFC/
4004, August 2005./
/
[VSA] Mitton, D., "Diameter/RADIUS Vendor Specific AVP/
Translation", Work in Progress, April 2005./
/
[RAD802.1X] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J./
Roese, "IEEE 802.1X Remote Authentication Dial In User/
Service (RADIUS) Usage Guidelines", RFC 3580,/
September 2003./
/
[CDMA2000] 3GPP2 "P.S0001-B", Wireless IP Network Standard,/
October 2002./
http://www.3gpp2.com/Public_html/specs/P.S0001-/
B_v1.0.pdf/
/
[AppleTalk] Sidhu, Gursharan; Andrews, Richard F. & Oppenheimer,/
Alan B. "Inside AppleTalk", Second Edition, Apple/
Computer., 1990/
/
[ARAP] Apple Remote Access Protocol (ARAP) Version 2.0/
External Reference Specification", Apple Computer,/
September 1994, R0612LL/B/
/
[IPX] Novell, Inc., "NetWare System Technical Interface/
Overview", June 1989, # 883-000780-001/
/
[LAT] Local Area Transport (LAT) Specification V5.0, Digital/
Equipment Corp., AA-NL26A-TE, June 1989/
/
/
[DIFFSERV] Nichols, K., Blake, S., Baker, F., and D. Black,/
"Definition of the Differentiated Services Field (DS/
Field) in the IPv4 and IPv6 Headers", RFC 2474,/
December 1998./
/
[DIFFSERVAF] Heinanen, J., Baker, F., Weiss, W., and J. Wroclawski,/
"Assured Forwarding PHB Group", RFC 2597, June 1999./
/
[DIFFSERVEF] Davie, B., Charny, A., Bennet, J.C., Benson, K., Le/
Boudec, J., Courtney, W., Davari, S., Firoiu, V., and/
D. Stiliadis, "An Expedited Forwarding PHB (Per-Hop/
Behavior)", RFC 3246, March 2002./
/
[UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", STD 63, RFC 3629, November 2003./
/
[ISOLatin] ISO 8859. International Standard -- Information/
Processing -- 8-bit Single-Byte Coded Graphic/
Character Sets -- Part 1: Latin Alphabet No. 1, ISO/
8859-1:1987. URL:/
http://www.iso.ch/cate/d16338.html/
/
[PPP] Simpson, W., "The Point-to-Point Protocol (PPP)", STD/
51, RFC 1661, July 1994./
/
[PAP] Lloyd, B. and W. Simpson, "PPP Authentication/
Protocols", RFC 1334, October 1992./
/
[L2TP] Townsley, W., Valencia, A., Rubens, A., Pall, G.,/
Zorn, G., and B. Palter, "Layer Two Tunneling Protocol/
"L2TP"", RFC 2661, August 1999./
/
[PPPMP] Sklower, K., Lloyd, B., McGregor, G., Carr, D., and T./
Coradetti, "The PPP Multilink Protocol (MP)", RFC/
1990, August 1996./
/
[PPTP] Hamzeh, K., Pall, G., Verthein, W., Taarud, J.,/
Little, W., and G. Zorn, "Point-to-Point Tunneling/
Protocol", RFC 2637, July 1999./
/
[IEEE 802.11F] IEEE, "Trial-Use Recommended Practice for Multi-Vendor/
Access Point Interoperability via an Inter-Access/
Point Protocol Across Distribution Systems Supporting/
IEEE 802.11 Operation", IEEE 802.11F-2003, June 2003./
/

Qualification of ISOC/IETF:

9.1-9.6     Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7     The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8     Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.

10.

Other (for any supplementary information):

References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.

Note: This form is based on Recommendation ITU-T A.5

Committed to connecting the world

ITU-T work programme