|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved as Internet Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
1
|
|
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=8300
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 8300 was approved in January 2018.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 8300 was published in 2018. It is a standards-track document. Current standards status of this document can be found at https://datatracker.ietf.org/doc/rfc8300/
|
|
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./
[RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function Chaining (SFC) Architecture", RFC 7665, DOI 10.17487/RFC7665, October 2015./
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017./
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017./
/
Informative references/
[NSH-BROADBAND-ALLOCATION]/
Napper, J., Kumar, S., Muley, P., Henderickx, W., and M./
Boucadair, "NSH Context Header Allocation -- Broadband",/
Work in Progress, draft-napper-sfc-nsh-broadband-/
allocation-04, November 2017./
/
[NSH-DC-ALLOCATION]/
Guichard, J., Smith, M., Kumar, S., Majee, S., Agarwal,/
P., Glavin, K., Laribi, Y., and T. Mizrahi, "Network/
Service Header (NSH) MD Type 1: Context Header Allocation/
(Data Center)", Work in Progress,/
draft-guichard-sfc-nsh-dc-allocation-07, August 2017./
/
[NSH-ENCRYPT]/
Reddy, T., Patil, P., Fluhrer, S., and P. Quinn,/
"Authenticated and encrypted NSH service chains", Work in/
Progress, draft-reddy-sfc-nsh-encrypt-00, April 2015./
[PROOF-OF-TRANSIT]/
Brockners, F., Bhandari, S., Dara, S., Pignataro, C.,/
Leddy, J., Youell, S., Mozes, D., and T. Mizrahi, "Proof/
of Transit", Work in Progress, draft-brockners-proof-/
of-transit-04, October 2017./
/
[RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P./
Traina, "Generic Routing Encapsulation (GRE)", RFC 2784,/
DOI 10.17487/RFC2784, March 2000,/
https://www.rfc-editor.org/info/rfc2784./
/
[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC/
Text on Security Considerations", BCP 72, RFC 3552,/
DOI 10.17487/RFC3552, July 2003,/
https://www.rfc-editor.org/info/rfc3552./
/
[RFC3692] Narten, T., "Assigning Experimental and Testing Numbers/
Considered Useful", BCP 82, RFC 3692,/
DOI 10.17487/RFC3692, January 2004,/
https://www.rfc-editor.org/info/rfc3692./
/
[RFC6071] Frankel, S. and S. Krishnan, "IP Security (IPsec) and/
Internet Key Exchange (IKE) Document Roadmap", RFC 6071,/
DOI 10.17487/RFC6071, February 2011,/
https://www.rfc-editor.org/info/rfc6071./
/
[RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu,/
D., and S. Mansfield, "Guidelines for the Use of the "OAM"/
Acronym in the IETF", BCP 161, RFC 6291,/
DOI 10.17487/RFC6291, June 2011,/
https://www.rfc-editor.org/info/rfc6291./
/
[RFC7325] Villamizar, C., Ed., Kompella, K., Amante, S., Malis, A.,/
and C. Pignataro, "MPLS Forwarding Compliance and/
Performance Requirements", RFC 7325, DOI 10.17487/RFC7325,/
August 2014, https://www.rfc-editor.org/info/rfc7325./
/
[RFC7498] Quinn, P., Ed. and T. Nadeau, Ed., "Problem Statement for/
Service Function Chaining", RFC 7498,/
DOI 10.17487/RFC7498, April 2015,/
https://www.rfc-editor.org/info/rfc7498./
/
[RFC7676] Pignataro, C., Bonica, R., and S. Krishnan, "IPv6 Support/
for Generic Routing Encapsulation (GRE)", RFC 7676,/
DOI 10.17487/RFC7676, October 2015,/
https://www.rfc-editor.org/info/rfc7676/
[RFC8165] Hardie, T., "Design Considerations for Metadata/
Insertion", RFC 8165, DOI 10.17487/RFC8165, May 2017,/
https://www.rfc-editor.org/info/rfc8165./
/
[RFC8201] McCann, J., Deering, S., Mogul, J., and R. Hinden, Ed.,/
"Path MTU Discovery for IP version 6", STD 87, RFC 8201,/
DOI 10.17487/RFC8201, July 2017,/
https://www.rfc-editor.org/info/rfc8201./
/
[RTG-ENCAP]/
Nordmark, E., Tian, A., Gross, J., Hudson, J., Kreeger,/
L., Garg, P., Thaler, P., and T. Herbert, "Encapsulation/
Considerations", Work in Progress,/
draft-ietf-rtgwg-dt-encap-02, October 2016./
/
[SFC-CONTROL-PLANE]/
Boucadair, M., "Service Function Chaining (SFC) Control/
Plane Components & Requirements", Work in Progress,/
draft-ietf-sfc-control-plane-08, October 2016./
/
[SFC-OAM-FRAMEWORK]/
Aldrin, S., Pignataro, C., Kumar, N., Akiya, N., Krishnan,/
R., and A. Ghanwani, "Service Function Chaining (SFC)/
Operation, Administration and Maintenance (OAM)/
Framework", Work in Progress,/
draft-ietf-sfc-oam-framework-03, September 2017./
/
[VXLAN-GPE]/
Maino, F., Kreeger, L., and U. Elzur, "Generic Protocol/
Extension for VXLAN", Work in Progress,/
draft-ietf-nvo3-vxlan-gpe-05, October 2017.
|
|
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
|
|
