Broadband Forum assigned names and numbers.
The Broadband Forum Enterprise Number is 3561 decimal (0x0DE9) and is listed in the IANA Private Enterprise Numbers Registry.
The following interface types were registered by BBF with IANA and are listed in the iana-if-type YANG module (there's also an IANA ifType MIB).
The following ports were registered by BBF with IANA and are listed in the IANA Service Name and Transport Protocol Port Number Registry.
|Service Name||Port Number||Transport Protocol||Reference||Notes|
|cwmp||7547||tcp||TR-069||ACS and Connection Request URLs can use this port|
|cwmp||7547||udp||TR-069||UDP Connection Request URL can use this port (it's the default)|
The following Service Names (without ports) were registered by BBF and are listed in the IANA Service Name and Transport Protocol Port Number Registry. Additional links are provided here to identify references for use of these Services Names, and defined TXT parameters associated with them.
|Service Name||Transport Protocol||Published Reference or Current Project||TXT Parameters||Subtypes|
name=<device or USP friendly name>
retry-min=< USP retry minimum wait interval>
retry-mult=< USP retry interval multiplier>
|No defined subtypes|
bbf URN namespaces have been registered with IANA. See RFC 8057 (URN Namespaces for Broadband Forum).
The first two (old) prefixes will continue to be used for new assignments relating to the standards with which they are already used, and the third (new) prefix will be used for assignments relating to all new standards.
To get a namespace assignment, requesters must go through the Broadband Forum project and documentation creation process.
IANA media type assignments are listed at https://www.iana.org/assignments/media-types/media-types.xhtml.
The following Media Types have been assigned to BBF.
WT-369 is available via the above project stream page.
|urn:dslforum-org:device:||BBF-defined UPnP devices||TR-064|
|Both these TRs are DEPRECATED|
|urn:dslforum-org:service:||BBF-defined UPnP services|
Both these TRs are DEPRECATED
|urn:dslforum-org:cwmp-n-m||CWMP version n.m||TR-069|
n and m indicate the CWMP major and minor version respectively
|QoS protocol and flow identifiers||TR-181 Issue 2|
m and t indicate media type and transport respectively
Note: pppoe is used both as a protocol and a flow identifier, and sdp is used only as a flow identifier. In theory additional protocol and flow identifiers could be defined, but this is unlikely
|References to BBF Technical Reports||TR-106|
nnn, i, a and c indicate the TR number, Issue, Amendment and Corrigendum respectively (-c is optional)
Note: wt is used instead of tr to reference a BBF Working Text (never in a published standard)
|urn:broadband-forum-org:cwmp:||XML Schemas used with CWMP||TR-069|
|urn:broadband-forum-org:ipdr:||XML Schemas used with IPDR||TR-232|
|urn:bbf:yang:||BBF YANG module namespaces||TR-355|
RFC 2132 Section 8.4: Option 43: Vendor Specific Information. Code range: 1-254 (8 bits).
|1-4||ACS discovery||TR-069 Section 3.1|
RFC 3925 Section 4: Option 125: Vendor-Identifying Vendor-Specific Information. Sub-option range: 1-254 (8 bits).
|1-4||Device info||TR-124 WAN.DHCPC|
Sub-options 1-4 overlap with TR-069 Annex F but this is unlikely to be a practical problem.
|1-6||Device / Gateway association||TR-069 Annex F|
|11-14||ACS discovery||TR-069 Section 3.1|
|15-16||Reserved||TR-069||Reserved because they're assigned as DHCPv6 option 17 sub-options|
|21-23||GRE tunneling||TR-317 Section 126.96.36.199.2|
|24||Client requirements||TR-317 Section 188.8.131.52|
RFC 3315 Section 22.17: Option 17: Vendor-specific Information. Sub-option range: 1-65534 (16 bits).
|1-4||ACS discovery||TR-069 Section 3.1|
|5-6||Reserved||TR-069||Reserved because they were used prior to TR-069 Amendment 5, and because they're assigned as DHCPv4 option 125 sub-options|
|11-16||Device / Gateway association||TR-069 Annex F|
Sub-options 1-6 were used prior to TR-069 Amendment 5
|21||Reserved||TR-317||Reserved because it's assigned as a DHCPv4 option 125 sub-option|
|22-23||GRE tunneling||TR-317 Section 184.108.40.206.2|
|24||Reserved||TR-317||Reserved because it's assigned as a DHCPv4 option 125 sub-option|