|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
Broadband Forum TR-369 describes the architecture, protocol, and data model that build an intelligent User Services Platform. It is targeted towards application developers, application service providers, vendors, consumer electronics manufacturers, and broadband and mobile network providers who want to expand the value of the end user’s network connection and their connected devices.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
None.
|
|
5.
|
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.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
TR-369 Issue 1, Amendment 4 was approved in July 2024
|
|
7.
|
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.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] TR069Amendment6,CPEWANManagementProtocol,BroadbandForum,2018 /
[2] TR106,DataModelTemplateforCWMPEndpointsandUSPAgents,BroadbandForum /
[3] TR181Issue2,DeviceDataModel,BroadbandForum /
[4] ProtocolBuffersv3,ProtocolBuffersMechanismforSerializingStructuredDataVersion3,Google /
[5] IMEIDatabase,InternationalMobileEquipmentIdentity,GSMA /
[6] IANA,InternetAssignedNumbersAuthority,IANA /
[7] Assignments,IEEERegistrationAuthority,IEEE /
[8] RFC1035,DomainNamesImplementationandSpecification,IETF,1987 /
[9] RFC2119,KeywordsforuseinRFCstoIndicateRequirementLevels,IETF,1997 /
[10] RFC2141,URNSyntax,IETF,1997 /
[11] RFC2234,AugmentedBNFforSyntaxSpecifications:ABNF,IETF,1997 /
[12] RFC3279,AlgorithmsandIdentifiersfortheInternetX.509PublicKeyInfrastructureCertificateand CertificateRevocationList(CRL)Profile,IETF,2002 /
[13] RFC3315,DynamicHostConfigurationProtocolforIPv6(DHCPv6),IETF,2003 /
[14] RFC3925,Vendor IdentifyingVendorOptionsforDynamicHostConfigurationProtocolversion4 (DHCPv4),IETF,2004 /
[15] RFC3986,UniformResourceIdentifier(URI):GenericSyntax,IETF,2005 /
[16] RFC5705,KeyingMaterialExportersforTransportLayerSecurity(TLS),IETF,2010 /
[17] RFC6066,TransportLayerSecurity(TLS)Extensions:ExtensionDefinitions,IETF,2011 /
[18] RFC6125,RepresentationandVerificationofDomainBasedApplicationServiceIdentitywithin InternetPublicKeyInfrastructureUsingX.509(PKIX)CertificatesintheContextofTransportLayer Security(TLS),IETF,2011 /
[19] RFC6455,TheWebSocketProtocol,IETF,2011 July2024 ©TheBroadbandForum.Allrightsreserved 17of247TheUserServicesPlatform TR369Issue1Amendment4 /
[20] RFC6762,MulticastDNS,IETF,2013 /
[21] RFC6763,DNSBasedServiceDiscovery,IETF,2013 /
[22] RFC6818,UpdatestotheInternetX.509PublicKeyInfrastructureCertificateandCertificate RevocationList(CRL)Profile,IETF,2013 /
[23] RFC6979,DeterministicUsageoftheDigitalSignatureAlgorithm(DSA)andEllipticCurveDigital SignatureAlgorithm(ECDSA),IETF,2013/
[24] RFC8446,TheTransportLayerSecurity(TLS)ProtocolVersion1.3,IETF,2018 /
[25] FIPSPUB1804,SecureHashStandard(SHS),NIST /
[26] FIPSPUB1864,DigitalSignatureStandard(DSS),NIST /
[27] MQTT3.1.1,MQTelemetryTransport3.1.1,OASIS /
[28] MQTT5.0,MQTelemetryTransport5.0,OASIS /
[29] SOAP1.1,SimpleObjectAccessProtocol(SOAP)1.1,W3C,2000 /
[30] XMLSchemaPart2,XMLSchemaPart2:DatatypesSecondEdition,W3C,2004 /
[31] RFC4122,AUniversallyUniqueIDentifier(UUID)URNNamespace,2005 /
[32] RFC4180,CommonFormatandMIMETypeforCommaSeparatedValues(CSV)Files,2005 /
[33] RFC5246,TheTransportLayerSecurity(TLS)ProtocolVersion1.2,2008 /
[34] RFC5280,InternetX.509PublicKeyInfrastructureCertificateandCertificateRevocationList(CRL) Profile,2008 /
[35] RFC7159,TheJavaScriptObjectNotation(JSON)DataInterchangeFormat,2014 /
[36] RFC7252,TheConstrainedApplicationProtocol(CoAP),2014 /
[37] RFC7925,TransportLayerSecurity(TLS)/DatagramTransportLayerSecurity(DTLS)Profilesfor theInternetofThings,2016 /
[38] RFC7959,BlockWiseTransfersintheConstrainedApplicationProtocol(CoAP),2016 /
[39] RFC8766,DiscoveryProxyforMulticastDNSBasedServiceDiscovery,2020 /
[40] STOMP12,SimpleTextOrientedMessageProtocol
|
|
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.
|
|
