|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2663 (1999)
|
|
Title:
|
IP Network Address Translator (NAT) Terminology and Considerations
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
The NAT terminology is used in H.248.64.
|
|
4.
|
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=2663
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
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:
|
|
|
[1] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot,G. and E./
Lear, "Address Allocation for Private Internets", BCP 5, RFC/
1918, February 1996./
/
[2] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700,/
October, 1994./
/
[3] Braden, R., "Requirements for Internet Hosts -- Communication/
Layers", STD 3, RFC 1122, October 1989./
/
[4] Braden, R., "Requirements for Internet Hosts -- Application and/
Support", STD 3, RFC 1123, October 1989./
/
[5] Baker, F., "Requirements for IP Version 4 Routers", RFC 1812,/
June 1995./
/
[6] Postel, J. and J. Reynolds, "File Transfer Protocol (FTP)", STD/
9, RFC 959, October 1985./
/
[7] Postel, J., "Transmission Control Protocol (TCP) Specification",/
STD 7, RFC 793, September 1981./
/
[8] Postel, J., "Internet Control Message Protocol Specification"/
STD 5, RFC 792, September 1981./
/
[9] Postel, J., "User Datagram Protocol (UDP)", STD 6, RFC 768,/
August 1980./
/
[10] Mogul, J. and J. Postel, "Internet Standard Subnetting/
Procedure", STD 5, RFC 950, August 1985./
/
/
/
[11] Carpenter, B., Crowcroft, J. and Y. Rekhter, "IPv4 Address/
Behavior Today", RFC 2101, February 1997./
/
[12] Kent, S. and R. Atkinson, "Security Architecture for the/
Internet Protocol", RFC 2401, November 1998./
/
[13] Kent, S. and R. Atkinson, "IP Encapsulating Security Payload/
(ESP)", RFC 2406, November 1998./
/
[14] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402,/
November 1998./
/
[15] Harkins, D. and D. Carrel, "The Internet Key Exchange (IKE)",/
RFC 2409, November 1998./
/
[16] Piper, D., "The Internet IP Security Domain of Interpretation/
for ISAKMP", RFC 2407, November 1998./
/
[17] Heffernan, A., "Protection of BGP Sessions via the TCP MD5/
Signature Option", RFC 2385, August 1998./
/
[18] Eastlake, D., "Domain Name System Security Extensions", RFC/
2535, March 1999.
|
|
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):
|
|
|
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.
|
|
