|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
Q.3052 (Q.M2M_pro_overview) refers to overall specification of IETF RFC 6886 for APIs and protocols for M2M service layer.
|
|
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=6886
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since April 2013.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 6886 was published in April 2013. It is a standards-track document and is currently in the "Informational" state.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item 8. Errata exhist.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,/
and E. Lear, "Address Allocation for Private Internets",/
BCP 5, RFC 1918, February 1996./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[Bonjour] Apple "Bonjour" http://developer.apple.com/bonjour/./
/
[ETEAISD] J. Saltzer, D. Reed and D. Clark: "End-to-end arguments in/
system design", ACM Trans. Comp. Sys., 2(4):277-88,/
November 1984./
/
[IGD] UPnP Standards "Internet Gateway Device (IGD) Standardized/
Device Control Protocol V 1.0", November 2001,/
http://www.upnp.org/standardizeddcps/igd.asp./
/
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC/
2131, March 1997./
/
[RFC2663] Srisuresh, P. and M. Holdrege, "IP Network Address/
Translator (NAT) Terminology and Considerations", RFC/
2663, August 1999./
/
[RFC3007] Wellington, B., "Secure Domain Name System (DNS) Dynamic/
Update", RFC 3007, November 2000./
/
[RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network/
Address Translator (Traditional NAT)", RFC 3022, January/
2001./
/
[RFC3424] Daigle, L., Ed., and IAB, "IAB Considerations for/
UNilateral Self-Address Fixing (UNSAF) Across Network/
Address Translation", RFC 3424, November 2002./
/
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the/
Internet Protocol", RFC 4301, December 2005./
/
[RFC6281] Cheshire, S., Zhu, Z., Wakikawa, R., and L. Zhang,/
"Understanding Apple's Back to My Mac (BTMM) Service", RFC/
6281, June 2011./
/
[RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service/
Discovery", RFC 6763, February 2013./
/
[RFC6887] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and/
P. Selkirk, "Port Control Protocol (PCP)", RFC 6887, April/
2013./
/
[SEE] SubEthaEdit, http://www.codingmonkeys.de/subethaedit/./
/
[VU347812] United States Computer Emergency Readiness Team/
Vulnerability Note VU#347812,
|
|
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
|
|
