1.
|
Clear description of the referenced document:
|
|
|
2.
|
Status of approval:
|
|
Approved standards-track document.
|
3.
|
Justification for the specific reference:
|
|
IETF RFC 4291 (2006) is referenced in Q.3405 (ex. Q.IPv6ProBB).
|
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=4291
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
Generally stable and well-understood; real implementation desirable but not necessary; no known technical flaws; considered immature; may be changed if problems are found or better solutions are identified; deploying implementation of such standards into a disruption-sensitive environment is not recommended.
|
6.
|
The degree of stability or maturity of the document:
|
|
Generally stable and well-understood; real implementation desirable but not necessary; no known technical flaws; considered immature; may be changed if problems are found or better solutions are identified; deploying implementation of such standards into a disruption-sensitive environment is not recommended.
|
7.
|
Relationship with other existing or emerging documents:
|
|
None.
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
[1] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998./
|
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.
|