|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards track document - Proposed Standard approved September 2013.
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendations allows the use of valid IPFIX 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=7012&doctitle=&group=&holder=&iprtitle=&patent=&submit=
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 7012 was published in September 2013 and is a standards track RFC.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard approved September 2013.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Obsoletes 5102
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates,/
"Export of Structured Data in IP Flow Information Export/
(IPFIX)", RFC 6313, July 2011./
/
[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken,/
"Specification of the IP Flow Information Export (IPFIX)/
Protocol for the Exchange of Flow Information", STD 77,/
RFC 7011, September 2013./
/
[RFC7013] Trammell, B., and B. Claise, "Guidelines for Authors and/
Reviewers of IP Flow Information Export (IPFIX)/
Information Elements", BCP 184, RFC 7013, September 2013.
|
|
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.
|
