|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
TR-069 is an essential part of the CWMP and is included as normative reference rather than including the full text.
|
|
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 was approved in December 2007.
|
|
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 2616, Hypertext Transfer Protocol -- HTTP/1.1, http://www.ietf.org/rfc/rfc2616.txt/
[6] RFC 2617, HTTP Authentication: Basic and Digest Access Authentication, http://www.ietf.org/rfc/rfc2617.txt/
[7] RFC 2965, HTTP State Management Mechanism, http://www.ietf.org/rfc/rfc2965.txt/
[8] Simple Object Access Protocol (SOAP) 1.1, http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[9] Organizationally Unique Identifiers (OUIs), http://standards.ieee.org/faqs/OUI.html/
[10] The SSL Protocol, Version 3.0, http://wp.netscape.com/eng/ssl3/
[11] RFC 2246, The TLS Protocol, Version 1.0, http://www.ietf.org/rfc/rfc2246.txt/
[12] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, http://www.ietf.org/rfc/rfc3986.txt/
[13] TR-106 Amendment 1, Data Model Template for TR-069-Enabled Devices, Broadband Forum Technical Report/
[14] RFC 2132, DHCP Options and BOOTP Vendor Extensions, http://www.ietf.org/rfc/rfc2132.txt/
[15] XML-Signature Syntax and Processing, http://www.w3.org/2000/09/xmldsig/
[16] PKCS #7, Cryptographic Message Syntax Standard, http://www.rsasecurity.com/rsalabs/pkcs/pkcs-7/index.html or http://www.ietf.org/rfc/rfc2315.txt/
[17] Port Numbers, http://www.iana.org/assignments/port-numbers/
[18] IANA Private Enterprise Numbers registry, http://www.iana.org/assignments/enterprise-numbers/
[19] RFC 2104, HMAC: Keyed-Hashing for Message Authentication, http://www.ietf.org/rfc/rfc2104.txt/
[20] RFC 2131, Dynamic Host Configuration Protocol, http://www.ietf.org/rfc/rfc2131.txt/
[21] RFC 3489, STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs), http://www.ietf.org/rfc/rfc3489.txt/
[22] RFC 3925, Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4), http://www.ietf.org/rfc/rfc3925.txt/
[23] HTML 4.01 Specification, http://www.w3.org/TR/html4/
[24] TR-098 Amendment 1, Internet Gateway Device Data Model for TR-069, Broadband Forum Technical Report/
[25] TR-104, Provisioning Parameters for VoIP CPE, 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.
|
|
