|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
RFC 7665 was approved as an informational document in October 2015.
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 7665 (2015) is used as a reference in Q.xxx.
|
|
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=7665
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 7665 was approved in October 2015.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 7665 was published in 2015. It is an informational document. Current standards status of this document can be found at https://datatracker.ietf.org/doc/rfc7665/
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative references/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997./
Informative references/
[Boucadair2014] /
Boucadair, M., Jacquenet, C., Parker, R., Lopez, D.,/
Guichard, J., and C. Pignataro, "Service FunctionChaining: Framework & Architecture", Work in Progress,/
draft-boucadair-sfc-framework-02, February 2014./
/
[Quinn2014]/
Quinn, P. and J. Halpern, "Service Function Chaining (SFC)/
Architecture", Work in Progress, draft-quinn-sfc-arch-05,/
May 2014./
/
[RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network/
Address Translator (Traditional NAT)", RFC 3022,/
DOI 10.17487/RFC3022, January 2001,/
http://www.rfc-editor.org/info/rfc3022./
/
[RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful/
NAT64: Network Address and Protocol Translation from IPv6/
Clients to IPv4 Servers", RFC 6146, DOI 10.17487/RFC6146,/
April 2011, http://www.rfc-editor.org/info/rfc6146./
[RFC6296] Wasserman, M. and F. Baker, "IPv6-to-IPv6 Network Prefix/
Translation", RFC 6296, DOI 10.17487/RFC6296, June 2011,/
http://www.rfc-editor.org/info/rfc6296./
/
[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,/
Morris, J., Hansen, M., and R. Smith, "Privacy/
Considerations for Internet Protocols", RFC 6973,/
DOI 10.17487/RFC6973, July 2013,/
http://www.rfc-editor.org/info/rfc6973./
/
[RFC7498] Quinn, P., Ed. and T. Nadeau, Ed., "Problem Statement for/
Service Function Chaining", RFC 7498,/
DOI 10.17487/RFC7498, April 2015,/
http://www.rfc-editor.org/info/rfc7498.
|
|
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
|
|
