|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 6335 (2011)
|
|
Title:
|
Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC - Best Current Practice approved August 2011
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation calls out the procedures as necessary to service names as specified in the reference.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/draft=&rfc=6335&doctitle=&group=&holder=&iprtitle=&patent=&submit=rfc
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC was published August 2011 and is currently a Best Current Practice through the Standards Track RFC.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Best Current Practice Standards Track RFC.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ANSI.X3.4-1986] American National Standards Institute, "Coded/
Character Set - 7-bit American Standard Code for/
Information Interchange", ANSI X3.4, 1986./
/
[RFC0768] Postel, J., "User Datagram Protocol", STD 6,/
RFC 768, August 1980./
/
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,/
RFC 793, September 1981./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation/
Guidelines For Values In the Internet Protocol and/
Related Headers", BCP 37, RFC 2780, March 2000./
/
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS/
RR for specifying the location of services (DNS/
SRV)", RFC 2782, February 2000./
/
[RFC3828] Larzon, L-A., Degermark, M., Pink, S., Jonsson,/
L-E., and G. Fairhurst, "The Lightweight User/
Datagram Protocol (UDP-Lite)", RFC 3828, July 2004./
/
[RFC4020] Kompella, K. and A. Zinin, "Early IANA Allocation/
of Standards Track Code Points", BCP 100, RFC 4020,/
February 2005./
/
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram/
Congestion Control Protocol (DCCP)", RFC 4340,/
March 2006./
/
[RFC4727] Fenner, B., "Experimental Values In IPv4, IPv6,/
ICMPv4, ICMPv6, UDP, and TCP Headers", RFC 4727,/
November 2006./
/
[RFC4960] Stewart, R., "Stream Control Transmission/
Protocol", RFC 4960, September 2007./
/
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for/
Writing an IANA Considerations Section in RFCs",/
BCP 26, RFC 5226, May 2008./
/
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for/
Syntax Specifications: ABNF", STD 68, RFC 5234,/
January 2008./
/
[RFC5595] Fairhurst, G., "The Datagram Congestion Control/
Protocol (DCCP) Service Codes", RFC 5595,/
September 2009.
|
|
9.
|
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):
|
|
|
None
|
|
