ITU-T A.5 reference justification

Home : ITU-T Home : ITU-T Work Programme : J.1611

ITU-T A.5 justification information for referenced document BBF TR-369 Issue 1 Amendment 2 in draft J.1611

Clear description of the referenced document:

Name:	BBF TR-369 Issue 1 Amendment 2
Title:	User Services Platform protocol Issue:1 Amendment 2

Status of approval:

Approved

Justification for the specific reference:

BBF TR-369 Issue 1 Amendment 2 is a normative reference in ITU-T J.1611

Current information, if any, about IPR issues:

None.

Other useful information describing the "Quality" of the document:

The Broadband Forum has produced a new standard that represents an evolution from TR-069, called the “User Services Platform” (USP), defined in TR-369. We recommend that any documents that reference BBF management standards in an agnostic way also reference this as it has significant improvements and advantages over TR-069.

The degree of stability or maturity of the document:

TR-369 Issue 1, Amendment 2 was approved in January 2022

Relationship with other existing or emerging documents:

TR-369 is evolved from TR-069. 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.

Any explicit references within that referenced document should also be listed:

[1] Assignments, IEEE Registration Authority, IEEE/
[2] FIPS PUB 180-4, Secure Hash Standard (SHS), NIST/
[3] FIPS PUB 186-4, Digital Signature Standard (DSS), NIST/
[4] MQTT 3.1.1, MQ Telemetry Transport 3.1.1, OASIS/
[5] MQTT 5.0, MQ Telemetry Transport 5.0, OASIS/
[6] Protocol Buffers v3, Protocol Buffers Mechanism for Serializing Structured Data Version 3, Google/
[7] RFC 1035, Domain Names - Implementation and Specification, IETF, 1987/
[8] RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, IETF, 1997/
[9] RFC 2141, URN Syntax, IETF, 1997/
[10] RFC 2234, Augmented BNF for Syntax Specifications: ABNF, IETF, 1997/
[11] RFC 3279, Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, IETF, 2002/
[12] RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6), IETF, 2003/
[13] RFC 3925, Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4), IETF, 2004/
[14] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, IETF, 2005/
[15] RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace, 2005/
[16] RFC 4180, Common Format and MIME Type for Comma-Separated Values (CSV) Files, 2005/
[17] RFC 5246, The Transport Layer Security (TLS) Protocol Version 1.2, 2008/
[18] RFC 5280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, 2008/
[19] RFC 5705, Keying Material Exporters for Transport Layer Security (TLS), IETF, 2010/
[20] RFC 6066, Transport Layer Security (TLS) Extensions: Extension Definitions, IETF, 2011/
[21] 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), IETF, 2011/
[22] RFC 6347, Datagram Transport Layer Security Version 1.2, IETF, 2012/
[23] RFC 6455, The WebSocket Protocol, IETF, 2011/
[24] RFC 6762, Multicast DNS, IETF, 2013/
[25] RFC 6763, DNS-Based Service Discovery, IETF, 2013/
[26] RFC 6818, Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, IETF, 2013/
[27] RFC 6979, Deterministic Usage of the Digital Signature Algorithm (DSA) and Elliptic Curve Digital Signature Algorithm (ECDSA), IETF, 2013/
[28] RFC 7159, The JavaScript Object Notation (JSON) Data Interchange Format, 2014/
[29] RFC 7252, The Constrained Application Protocol (CoAP), 2014/
[30] RFC 7925, Transport Layer Security (TLS) / Datagram Transport Layer Security (DTLS) Profiles for the Internet of Things, 2016/
[31] RFC 7959, Block-Wise Transfers in the Constrained Application Protocol (CoAP), 2016/
[32] RFC 8446, The Transport Layer Security (TLS) Protocol Version 1.3, IETF, 2018/
[33] RFC 8766, Discovery Proxy for Multicast DNS-Based Service Discovery, 2020/
[34] SOAP 1.1, Simple Object Access Protocol (SOAP) 1.1, W3C, 2000/
[35] STOMP-1-2, Simple Text Oriented Message Protocol/
[36] TR-069 Amendment 6, CPE WAN Management Protocol, Broadband Forum, 2018/
[37] TR-106, Data Model Template for CWMP Endpoints and USP Agents, Broadband Forum/
[38] TR-181 Issue 2, Device Data Model, Broadband Forum/
[39] XML Schema Part 2, XML Schema Part 2: Datatypes Second Edition, W3C, 2004

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.

Note: This form is based on Recommendation ITU-T A.5

Committed to connecting the world

ITU-T work programme