|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
When auto configuration service is implmented, this standard is recommended as management protocol.
|
|
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 6 was approved in March 2018.
|
|
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:
|
|
|
The following references are associated with document conventions or context for this/
specification, but are not associated with requirements of the CPE WAN Management/
Protocol itself./
[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/
The following references are associated with required components of the CPE WAN/
Management Protocol./
[5] RFC 1034, Domain names – concepts and facilities,/
http://www.ietf.org/rfc/rfc1034.txt/
[6] RFC 7230, Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing,/
http://www.ietf.org/rfc/rfc7230.txt/
[7] RFC 7231, Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content,/
http://www.ietf.org/rfc/rfc7231.txt/
[8] RFC 7235, Hypertext Transfer Protocol (HTTP/1.1): Authentication,/
http://www.ietf.org/rfc/rfc7235.txt/
[9] RFC 7616, HTTP Digest Access Authentication, http://www.ietf.org/rfc/rfc7616.txt/
[10] RFC 7617, The 'Basic' HTTP Authentication Scheme,/
http://www.ietf.org/rfc/rfc7617.txt/
[11] RFC 6265, HTTP State Management Mechanism, http://www.ietf.org/rfc/rfc6265.txt/
[12] Simple Object Access Protocol (SOAP) 1.1, http://www.w3.org/TR/2000/NOTESOAP-20000508/
[13] Organizationally Unique Identifiers (OUIs), http://standards.ieee.org/faqs/OUI.html/
[14] RFC 5246, The Transport Layer Security (TLS) Protocol, Version 1.2,/
http://www.ietf.org/rfc/rfc5246.txt/
[15] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax,/
http://www.ietf.org/rfc/rfc3986.txt/
CPE WAN Management Protocol TR-069 Issue 1 Amendment 6/
March 2018 © The Broadband Forum. All rights reserved. Page 77 of 276/
[16] TR-106, Data Model Template for TR-069-Enabled Devices, Broadband Forum/
Technical Report/
The following references are associated with optional or recommended components of/
the CPE WAN Management Protocol./
[17] RFC 2132, DHCP Options and BOOTP Vendor Extensions,/
http://www.ietf.org/rfc/rfc2132.txt/
[18] XML-Signature Syntax and Processing, http://www.w3.org/2000/09/xmldsig/
[19] PKCS #7, Cryptographic Message Syntax Standard,/
http://www.rsasecurity.com/rsalabs/pkcs/pkcs-7/index.html or/
http://www.ietf.org/rfc/rfc2315.txt/
[20] Port Numbers, http://www.iana.org/assignments/port-numbers/
[21] IANA Private Enterprise Numbers registry,/
http://www.iana.org/assignments/enterprise-numbers/
[22] RFC 2104, HMAC: Keyed-Hashing for Message Authentication,/
http://www.ietf.org/rfc/rfc2104.txt/
[23] RFC 2131, Dynamic Host Configuration Protocol,/
http://www.ietf.org/rfc/rfc2131.txt/
[24] RFC 3489, STUN - Simple Traversal of User Datagram Protocol (UDP) Through/
Network Address Translators (NATs), http://www.ietf.org/rfc/rfc3489.txt/
[25] RFC 3925, Vendor-Identifying Vendor Options for Dynamic Host Configuration/
Protocol version 4 (DHCPv4), http://www.ietf.org/rfc/rfc3925.txt/
[26] HTML 4.01 Specification, http://www.w3.org/TR/html4/
[27] TR-098, Internet Gateway Device Data Model for TR-069, Broadband Forum/
Technical Report (DEPRECATED)/
[28] TR-104, Provisioning Parameters for VoIP CPE, Broadband Forum Technical/
Report/
[29] TR-135, Data Model for a TR-069 Enabled STB, Broadband Forum Technical/
Report/
[30] TR-140 Issue 1.1, TR-069 Data Model for Storage Service Enabled Devices,/
Broadband Forum Technical Report/
[31] TR-143, Enabling Network Throughput Performance Tests and Statistical/
Monitoring, Broadband Forum Technical Report/
[32] TR-157, Component Objects for CWMP, Broadband Forum Technical Report/
[33] TR-196, Femto Access Point Service Data Model, Broadband Forum Technical/
Report/
[34] TR-181 Issue 1, Device Data Model for TR-069, Broadband Forum Technical/
Report (DEPRECATED)/
CPE WAN Management Protocol TR-069 Issue 1 Amendment 6/
March 2018 © The Broadband Forum. All rights reserved. Page 78 of 276/
[35] TR-181 Issue 2, Device Data Model for TR-069, Broadband Forum Technical/
Report/
[36] RFC 5389, Session Traversal Utilities for NAT (STUN),/
http://www.ietf.org/rfc/rfc5389.txt/
[37] RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace,/
http://www.ietf.org/rfc/rfc4122.txt/
[38] RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6),/
http://www.ietf.org/rfc/rfc3315.txt/
[39] IEEE 802a, IEEE Standard for Local and Metropolitan Area Networks: Overview/
and Architecture - Amendment 1: Ethertypes for Prototype and Vendor-Specific/
Protocol Development./
[40] RFC 6120, Extensible Messaging and Presence Protocol (XMPP): Core,/
http://www.ietf.org/rfc/rfc6120.txt/
[41] tr-157-1-8.xml, Component Objects for CWMP, Broadband Forum,/
http://www.broadband-forum.org/cwmp/tr-157-1-8.xml/
[42] UPnP IGD v1, UPnP InternetGatewayDevice:1 Device Template, UPnP Forum,/
http://upnp.org/specs/gw/UPnP-gw-InternetGatewayDevice-v1-Device.pdf/
[43] UPnP IGD v2, UPnP InternetGatewayDevice:2 Device Template, UPnP Forum,/
http://upnp.org/specs/gw/UPnP-gw-InternetGatewayDevice-v2-Device.pdf/
[44] UPnP WAN PPP v1, UPnP WANPPPConnection:1 Service, UPnP Forum,/
http://upnp.org/specs/gw/UPnP-gw-WANPPPConnection-v1-Service.pdf/
[45] UPnP WAN IP v2, UPnP WANIPConnection:2 Service, UPnP Forum,/
http://upnp.org/specs/gw/UPnP-gw-WANIPConnection-v2-Service.pdf/
[46] UPnP WAN IPv6 FW v1, UPnP WANIPv6FirewallControl:1 Service, UPnP/
Forum, http://upnp.org/specs/gw/UPnP-gw-WANIPv6FirewallControl-v1-/
Service.pdf/
[47] RFC 6092, Recommended Simple Security Capabilities in Customer Premise/
Equipment (CPE) for Providing Residential IPv6 Internet Services,/
http://www.ietf.org/rfc/rfc6092.txt/
[48] TR-124 Issue 3, Functional Requirements for Broadband Residential Gateway/
Devices, Broadband Forum Technical Report/
[49] RFC 6125, Representation and Verification of Domain-Based Application Service/
Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates/
in the Context of Transport Layer Security (TLS),/
https://tools.ietf.org/rfc/rfc6125.txt/
[50] RFC 6066, Transport Layer Security (TLS) Extensions: Extension Definitions,/
https://tools.ietf.org/rfc/rfc6066.txt./
[51] RFC 5077, Transport Layer Security (TLS) Session Resumption without Server-Side/
State, https://tools.ietf.org/rfc/rfc5077.txt./
CPE WAN Management Protocol TR-069 Issue 1 Amendment 6/
March 2018 © The Broadband Forum. All rights reserved. Page 79 of 276/
[52] RFC 4180, Common Format and MIME Type for Comma-Separated Values (CSV)/
Files, https://www.ietf.org/rfc/rfc4180.txt/
[53] RFC 7159, The JavaScript Object Notation (JSON) Data Interchange Format,/
https://www.ietf.org/rfc/rfc7159.txt/
[54] OWASP, Cross-site Scripting, https://www.owasp.org/index.php/Crosssite_Scripting_(XSS)/
[55] OWASP, Cross-Site Request Forgery, https://www.owasp.org/index.php/CrossSite_Request_Forgery_(CSRF)/
[56] RFC 7525, Recommendations for Secure Use of Transport Layer Security (TLS)/
and Datagram Transport Layer Security (DTLS), http://www.ietf.org/rfc/rfc7525.txt/
[57] RFC 7568, Deprecating Secure Sockets Layer Version 3.0,/
http://www.ietf.org/rfc/rfc7568.txt/
[58] RFC 7395, An Extensible Messaging and Presence Protocol (XMPP) Subprotocol/
for WebSocket, http://www.ietf.org/rfc/rfc7395.txt
|
|
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.
|
|
