Broadband Forum assigned names and numbers.
Q: Should we put all the assigned numbers and names in this page or have a child page (with known URL) for each category?
- A: There aren't many, so let's put them all here for now. We can define permalinks, e.g. for DHCP sub-options, that all point here for now and could move later.
Q: How should we reference TRs?
- A: TR-xxx implies Issue 1 and the latest Amendment / Corrigendum unless otherwise stated (causes a problem for TR-124 etc that use Issues for what should be Amendments).
Q: Should we mention deprecated TRs at all, e.g. TR-064, TR-133, TR-098, TR-181 Issue 1?
- A: No.
Q: This will be a public page. Should we include WTs?
- A: No. In-progress assignments are listed on a separate In-progress Assigned Names and Numbers page and will be transferred here when official.
Names and Numbers Assigned by Other Organizations
The Broadband Forum Enterprise Number is 3561 decimal (0x0DE9) and is listed in the IANA Private Enterprise Numbers Registry.
IANA Interface Types
TCP and UDP Ports
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)|
DHCPv4 Option 43 Sub-options (Codes)
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|
DHCPv4 Option 125 Sub-options
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 22.214.171.124.2|
|24||Client requirements||TR-317 Section 126.96.36.199|
DHCPv6 Option 17 Sub-options
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|
|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 188.8.131.52.2|
|24||Reserved||TR-317||Reserved because it's assigned as a DHCPv4 option 125 sub-option|
The urn:dslforum-org:, urn:broadband-forum-org: and urn:bbf: prefixes are being registered with IANA. See Uniform Resource Name (URN) Namespaces for Broadband Forum.
To get a namespace assignment, requesters must go through the Broadband Forum project and documentation creation process.
A namespace (in the tables below) that ends with a colon (:) is a prefix, and the referenced standards should define the rules governing the remaining part of the URN.
|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:bbf:yang:||BBF YANG module namespaces||TR-355|