|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
TR-069 Amendment 5 describes the CPE WAN Management Protocol, intended for communication between a CPE and Auto-Configuration Server (ACS).
The CPE WAN Management Protocol defines a mechanism that encompasses secure auto-configuration of a CPE, and also incorporates other CPE management functions into a common framework. This document specifies the generic requirements of the management protocol methods which can be applied to any TR-069 CPE. Other documents specify the managed objects, or data models, for specific types of devices or services.
J.STB-CTS requires Remote management and Diagnostic feature which need to refer the existing specification in TR-069 Amendment 5.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
None.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
TR-069 was approved in December 2007. Specification is publicly available from BBF.
It is widely recognized as an industry standard, and referenced by several other fora and SDOs.
It is deployed by over 20 service providers and implemented by over 50 vendors.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
TR-069 Issue 1, Amendment 5 was approved in November 2013.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
TR-069 is the core specification 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-046, Auto-Configuration Architecture & Framework, Broadband Forum Technical Report/
[3] TR-062, Auto-Configuration for the Connection Between the DSL Broadband Network Termination (B-NT) and the Network using ATM, Broadband Forum Technical Report/
[4] TR-044, Auto-Configuration for Basic Internet (IP-based) Services, Broadband Forum Technical Report/
[5] RFC 1034, Domain names – concepts and facilities,/
http://www.ietf.org/rfc/rfc1034.txt/
[6] RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1,/
http://www.ietf.org/rfc/rfc2616.txt/
[7] RFC 2617, HTTP Authentication: Basic and Digest Access Authentication,/
http://www.ietf.org/rfc/rfc2617.txt/
[8] RFC 6265, HTTP State Management Mechanism, http://www.ietf.org/rfc/rfc6265.txt/
[9] Simple Object Access Protocol (SOAP) 1.1, http://www.w3.org/TR/2000/NOTESOAP-20000508/
[10] Organizationally Unique Identifiers (OUIs), http://standards.ieee.org/faqs/OUI.html/
[11] RFC 5246, The Transport Layer Security (TLS) Protocol, Version 1.2,/
http://www.ietf.org/rfc/rfc5246.txt/
[12] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax,/
http://www.ietf.org/rfc/rfc3986.txt/
[13] TR-106, Data Model Template for TR-069-Enabled Devices, 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.
|
|
