This page will soon be deactivated—explore our new, faster, mobile-friendly site, now centralized in MyWorkspace!

Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : G.9962     
  ITU-T A.5 justification information for referenced document BBF TR-181 Issue 2, Amendment 8 in draft G.9962
1. Clear description of the referenced document:
Name: BBF TR-181 Issue 2, Amendment 8
Title: Broadband Forum TR-181 Issue 2, Amendment 8 (2014), Device data model for TR-069
2. Status of approval:
Approved - December 2014
3. Justification for the specific reference:
TR-181 Issue 2 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-181 Issue 2 Amendment 8. was approved in December 2014. Specification is publicly available from BBF
6. The degree of stability or maturity of the document:
TR-181 Issue 2 was approved in March 2010. Amendments have been done to include new technologies but do not affect the core of the document.
7. Relationship with other existing or emerging documents:
TR-181 Issue 2 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, IETF, 1997 /
[2] TR-069 Amendment 5, CPE WAN Management Protocol, Broadband Forum, 2013 /
[3] TR-106 Amendment 7, Data Model Template for TR-069-Enabled Devices, Broadband Forum, 2013 /
[4] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, IETF, 2005 /
[5] XML Schema Part 0: Primer Second Edition, W3C, 2004 /
[6] RFC 2863, The Interfaces Group MIB, IETF, 2000 /
[7] X.200, Information technology - Open Systems Interconnection - Basic Reference Model: The basic model, ITU-T, 1994 /
[8] 802.1D-2004, Media Access Control (MAC) Bridges, IEEE, 2004 /
[9] 802.1Q-2011, Media Access Control (MAC) Bridges and Virtual Bridge Local Area Networks, IEEE, 2011 /
[10] RFC 2597, Assured Forwarding PHB Group, IETF, 1999 /
[11] RFC 3246, An Expedited Forwarding PHB (Per-Hop Behavior), IETF, 2002 /
[12] RFC 3261, SIP: Session Initiation Protocol, IETF, 2002 /
[13] RFC 3435, Media Gateway Control Protocol (MGCP) - Version 1.0, IETF, 2003 /
[14] RFC 4566, SDP: Session Description Protocol, IETF, 2006 /
[15] RFC 2453, RIP Version 2, IETF, 1998 /
[16] RFC 2460, Internet Protocol Version 6 (IPv6) Specification, IETF, 1998 /
[17] RFC 2464, Transmission of IPv6 Packets over Ethernet Networks, IETF, 1998 /
[18] RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6), IETF, 2003 /
[19] RFC 3633, IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6, IETF, 2003 /
[20] RFC 4191, Default Router Preferences and More-Specific Routes, IETF, 2005 /
[21] RFC 4193, Unique Local IPv6 Unicast Addresses, IETF, 2005 /
[22] RFC 4861, Neighbor Discovery for IP version 6 (IPv6), IETF, 2007 /
[23] RFC 4862, IPv6 Stateless Address Autoconfiguration, IETF, 2007 /
[24] RFC 5072, IP Version 6 over PPP, IETF, 2007 /
[25] RFC 5969, IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) – Protocol Specification, IETF, 2010 /
[26] RFC 6106, IPv6 Router Advertisement Options for DNS Configuration, IETF, 2010 /
[27] RFC 6333, Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion, IETF, 2011 /
[28] RFC 6334, Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Options for DualStack Lite, IETF, 2011 /
[29] TR-101, Migration to Ethernet Based DSL Aggregation, Broadband Forum, 2006 /
[30] TR-124 Issue 2, Functional Requirements for Broadband Residential Gateway Devices, Broadband Forum, 2010 /
[31] TR-177, IPv6 in the context of TR-101, Broadband Forum, 2010 /
[32] TR-187, IPv6 for PPP Broadband Access, Broadband Forum, 2010 /
[33] ICSA Baseline Modular Firewall Certification Criteria, Baseline module – version 4.1, ICSA Labs, 2008 /
[34] ICSA Residential Modular Firewall Certification Criteria, Required Services Security Policy – Residential Category module – version 4.1, ICSA Labs, 2008 /
[35] RFC 4301, Security Architecture for the Internet Protocol, IETF, 2005 /
[36] RFC 4302, IP Authentication Header (AH), IETF, 2005. /
[37] RFC 4303, IP Encapsulating Security Payload (ESP), IETF, 2005 /
[38] RFC 5996, Internet Key Exchange Protocol Version 2 (IKEv2), IETF, 2010 /
[39] ETSI TS 102 690 v1.1.6, Machine-to-Machine Communications (M2M Functional Architecture), ETSI, 2012 /
[40] ETSI TS 102 921 v1.1.6, M2M mIa, dIa and mId Interfaces, ETSI, 2012 /
[41] ETSI TS 103 093 v1.1.3, Machine to Machine (M2M); BBF TR-069 Compatible Data Model for ETSI M2M, ETSI, 2012 /
[42] ZigBee-2007, ZigBee Specification, The ZigBee Alliance, 2007 /
[43] RFC 6887, Port Control Protocol (PCP), IETF, 2013 /
[44] RFC 6970, Universal Plug and Play (UPnP) Internet Gateway Device – Port Control Protocol Interworking Function (IGD-PCP IWF), IETF, 2013 /
[45] RFC 7291, DHCP Options for the Port Control Protocol (PCP), IETF, 2014 /
[46] draft-ietf-pcp-proxy, Port Control Protocol (PCP) Proxy Function, IETF, 2014 /
[47] draft-ietf-pcp-server-selection, PCP Server Selection, IETF, 2014 /
[48] draft-boucadair-pcp-flow-examples, Port Control Protocol (PCP) Flow Examples, IETF, 2013 /
[49] RFC 2661, Layer Two Tunneling Protocol “L2TP”, IETF, 1999 /
[50] RFC 2784, Generic Routing Encapsulation (GRE), IETF, 2000 /
[51] RFC 2890, Key and Sequence Number Extensions to GRE, IETF, 2000 /
[52] draft-ietf-softwire-map, Mapping of Address and Port with Encapsulation (MAP), IETF, 2014 /
[53] draft-ietf-softwire-map-t, Mapping of Address and Port using Translation (MAP-T), IETF, 2014 /
[54] draft-ietf-softwire-map-dhcp, DHCPv6 Options for configuration of Softwire Address and Port Mapped Clients, IETF, 2014/
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):
Note: This form is based on Recommendation ITU-T A.5