|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 7675 (2015)
|
|
Title:
|
Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track "Proposed Standard" RFC approved in October 2015.
|
|
3.
|
Justification for the specific reference:
|
|
|
H.248.50 defines a new H.248 package for support of procedures according to RFC 7675.
|
|
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=7675
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standards Track RFC approved October 2015.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards Track RFC approved October 2015.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
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,/
DOI 10.17487/RFC2119, March 1997,/
http://www.rfc-editor.org/info/rfc2119./
/
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment/
(ICE): A Protocol for Network Address Translator (NAT)/
Traversal for Offer/Answer Protocols", RFC 5245,/
DOI 10.17487/RFC5245, April 2010,/
http://www.rfc-editor.org/info/rfc5245./
/
[RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,/
"Session Traversal Utilities for NAT (STUN)", RFC 5389,/
DOI 10.17487/RFC5389, October 2008,/
http://www.rfc-editor.org/info/rfc5389./
|
|
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
|
