|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
The packet format used for routing in G.cmsr is the one described in RF C4944. Also the G.cmsr packet routing mechanism is based on clause 11.1 of RFC 4944.
|
|
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=4944
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since 2007.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4944 was published in 2007. It is a standards-track document. Current standards status of this document can be found at http://www.rfc-editor.org/rfcxx00.html.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Updated by RFC 6282, RFC 6775.
|
|
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./
/
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing/
an IANA Considerations Section in RFCs", BCP 26,/
RFC 2434, October 1998./
/
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol,/
Version 6 (IPv6) Specification", RFC 2460,/
December 1998./
/
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over/
Ethernet Networks", RFC 2464, December 1998./
/
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing/
Architecture", RFC 4291, February 2006./
/
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H./
Soliman, "Neighbor Discovery for IP version 6/
(IPv6)", RFC 4861, September 2007./
/
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6/
Stateless Address Autoconfiguration", RFC 4862,/
September 2007./
/
[ieee802.15.4] IEEE Computer Society, "IEEE Std. 802.15.4-2003",/
October 2003./
|
|
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
|
|
