Question(s):
8/11
Meeting, date:
Study Group:
11
Working Party:
2/11
Source:
Editor of X.609.4 (ex X.mp2p-mspp)
Title:
A.5 justification information for draft new X.609.4 (ex X.mp2p-mspp) "Managed P2P communications: Multimedia streaming peer protocol"
Contact:
Name
Organization
Country
Tel: +
xx
E-mail:
a@b.com
Contact:
Tel: +xx
E-mail:a@b.com
Abstract:
This TD contains the A.5 justification for draft new X.609.4 (ex X.mp2p-mspp) "Managed P2P communications: Multimedia streaming peer protocol" including the following normative references: IETF RFC 7159 (2014).
1Introduction
According to ITU procedures, as described in
ITU-T Recommendation A.5
, any normative reference to documentation produced outside the ITU (other than ISO and IEC texts) needs to be evaluated by the study group or working party before a decision is made to incorporate the reference in an ITU-T Recommendation.
This TD contains the A.5 justification information for new X.609.4 (ex X.mp2p-mspp) "Managed P2P communications: Multimedia streaming peer protocol".
2Referred documents and respective justifications
- IETF RFC 7159 (2014): The JavaScript Object Notation (JSON) Data Interchange Format
-
This RFC was approved as proposed Standard in March 2014 and obsoleted by RFC 8259 in December 2017. Normarive reference should normally not be made to this RFC.
-
It is used as a reference in the Recommendation ITU-T X.609.4
-
Complete A.5 justification information can be found in
Annex 1
.
Annex 1
A.5 justification information for the reference to IETF RFC 7159 (2014)
1
Clear description of the referenced document:
IETF RFC 7159 (2014): The JavaScript Object Notation (JSON) Data Interchange Format
2
Status of approval:
This RFC was approved as proposed Standard in March 2014 and obsoleted by RFC 8259 in December 2017. Normarive reference should normally not be made to this RFC.
3
Justification for the specific reference:
It is used as a reference in the Recommendation ITU-T X.609.4
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=6749&submit=rfc&doctitle=&group=&holder=&iprtitle=&patent=
5
Other useful information describing the "Quality" of the document:
This RFC was obsoleted by RFC 8259. It obsoletes RFC 7158, RFC 4627. Errata exist.
6
The degree of stability or maturity of the document:
This obsolete "Proposed Stanadard" RFC is replaced by RFC8259. Errata exist.
7
Relationship with other existing or emerging documents:
References within the referenced RFC are listed under item (8).
8
Any explicit references within that referenced document should also be listed:
Normative References[IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic", IEEE Standard 754, August 2008,http://grouper.ieee.org/groups/754/.[RFC2119] Bradner, S., "Key words for use in RFCs to IndicateRequirement Levels", BCP 14, RFC 2119, March 1997.[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for SyntaxSpecifications: ABNF", STD 68, RFC 5234, January 2008.[UNICODE] The Unicode Consortium, "The Unicode Standard",http://www.unicode.org/versions/latest/.Informative References[ECMA-262] Ecma International, "ECMAScript Language SpecificationEdition 5.1", Standard ECMA-262, June 2011,http://www.ecma-international.org/publications/standards/Ecma-262.htm.[ECMA-404] Ecma International, "The JSON Data Interchange Format",Standard ECMA-404, October 2013,http://www.ecma-international.org/publications/standards/Ecma-404.htm.[Err3607] RFC Errata, Errata ID 3607, RFC 3607,http://www.rfc-editor.org.[Err607] RFC Errata, Errata ID 607, RFC 607,http://www.rfc-editor.org.[RFC4627] Crockford, D., "The application/json Media Type for JavaScript Object Notation (JSON)", RFC 4627, July 2006.
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):
N/A.
_________________
-
PAGE
1
-