|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
TR-106 was approved in November 2006.
|
|
3.
|
Justification for the specific reference:
|
|
|
TR-106 Amendment 5 specifies data model guidelines to be followed by all TR-069-enabled devices. These guidelines include structural requirements for the data hierarchy, requirements for versioning of data models, and requirements for defining profiles.
J.STB-CTS requires Remote management and Diagnostic feature which need to refer the existing specification in TR-106 Amendment 5
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
None.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
TR-106 was approved in Nov 2010. Specification is publicly available from BBF.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
TR-106 was approved in Nov 2010. After 5 amendments were approved in Nov 2006, Nov 2008, Sep 2009, Feb 2010 and Nov 2010
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
TR-106 is part of a set of specifications related to remote management of CPE.
The set consists of TR-069, TR-104, TR-106, TR-135, TR-140, TR-143, TR-157, TR-181 Issue 2, and TR-196.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt/
[2] TR-069 Amendment 2, CPE WAN Management Protocol, Broadband Forum Technical Report/
[3] TR-098 Amendment 2, Internet Gateway Device Data Model for TR-069, Broadband Forum Technical Report/
[4] Organizationally Unique Identifiers (OUIs), http://standards.ieee.org/faqs/OUI.html/
[5] Simple Object Access Protocol (SOAP) 1.1, http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[6] RFC 3513, Internet Protocol Version 6 (IPv6) Addressing Architecture, http://www.ietf.org/rfc/rfc3513.txt/
[7] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, http://www.ietf.org/rfc/rfc3986.txt/
[8] Extensible Markup Language (XML) 1.0 (Fourth Edition), http://www.w3.org/TR/REC-xml/
[9] RFC 2648, A URN Namespace for IETF Documents, http://www.ietf.org/rfc/rfc2648.txt/
[10] TR-143 Corrigendum 1, Enabling Network Throughput Performance Tests and Statistical Monitoring, Broadband Forum Technical Report/
[11] XML Schema Part 0: Primer Second Edition, http://www.w3.org/TR/xmlschema-0/
[12] TR-157 Amendment 1, Component Objects for CWMP, Broadband Forum Technical Report/
[13] TR-181 Issue 1, TR-181 Issue 2, Device Data Model for TR-069, Broadband Forum Technical Report/
|
|
9.
|
Qualification of
Broadband Forum:
|
|
|
The Broadband Forum was qualified in accordance with ITU-T A.4 and ITU-T A.5 on 27 January 2010.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None.
|
