Broadband Forum assigned names and numbers.
Introduction
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 WTs and 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: Yes. No sensitive information is likely to leak, and this is easier than maintaining a separate internal list.
Q: Why have you reserved various ranges?
- A: To imply that codes will always be assigned to TRs in groups of 10. WT-301i2 is anomalous and might naturally expect instead to use 31-40.
Names and Numbers Assigned by Other Organizations
Enterprise Number
The Broadband Forum Enterprise Number is 3561 decimal (0x0DE9) and is listed in the IANA Private Enterprise Numbers Registry.
IANA Interface Types
The following interface types were requested by BBF and are listed in the IANA ifType MIB (there's also a YANG version).
Interface Type | Reference | Notes |
---|---|---|
fastdsl | TR-355 | |
ptm | WT-383 | Not yet requested |
TCP and UDP Ports
The following ports were requested by BBF 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) |
pon-ictp | ???? | tcp | WT-352 | Not yet requested |
DHCP Sub-options
DHCPv4 Option 43 Sub-options
Option 43: Vendor Specific Information.
Sub-option | Usage | Reference | Notes |
---|---|---|---|
1-4 | ACS discovery | TR-069 Section 3.1 | Sub-option usage:
|
DHCPv4 Option 125 Sub-options
Option 125: Vendor-Identifying Vendor-Specific Information.
Sub-option | Usage | Reference | Notes |
---|---|---|---|
1-4 | Device info | TR-124 WAN.DHCPC | Sub-option usage:
These sub-options overlap with TR-069 Annex F but this is unlikely to be a practical problem. |
1-6 | Device / Gateway association | TR-069 Annex F | Sub-option usage:
|
7-10 | Reserved | TR-069 Annex F | TR-069 doesn't mention these sub-options |
11-14 | ACS discovery | TR-069 Section 3.1 | Sub-option usage:
|
15-20 | Reserved | TR-069 | TR-069 doesn't mention these sub-options |
21-23 | GRE tunneling | TR-317 Section 7.1.3.3.2 | Sub-option usage:
|
24 | Client requirements | TR-317 Section 7.4.3.7 | Sub-option usage:
|
25-30 | Reserved | TR-317 | TR-317 doesn't mention these sub-options |
160 | DPU Discovery | WT-301 Issue 2 Section 16.5.2.1 | Sub-option is defined as 0xA0 |
161 | PMA Offer | WT-301 Issue 2 Section 16.5.2.2 | Sub-option is defined as 0xA1 |
162-170 | Reserved | WT-301 Issue 2 | WT-301 Issue 2 doesn't mention these sub-options |
DHCPv6 Option 17 Sub-options
Option 17: Vendor-specific Information.
Sub-option | Usage | Reference | Notes |
---|---|---|---|
1-4 | ACS discovery | TR-069 Section 3.1 | Sub-option usage:
|
5-10 | Reserved | TR-069 | TR-069 doesn't mention these sub-options |
11-16 | Device / Gateway association | TR-069 Annex F | Sub-option usage:
Prior to TR-069 Amendment 5, sub-options 1-6 were used |
17-20 | Reserved | TR-069 | TR-069 doesn't mention these sub-options |
21 | Reserved | TR-317 | TR-317 doesn't mention this sub-option |
22-23 | GRE tunneling | TR-317 Section 7.1.3.3.2 | Sub-option usage:
|
24-30 | Reserved | TR-317 | TR-317 doesn't mention these sub-options |
160 | DPU Discovery | WT-301 Issue 2 Section 16.5.2.1 | Sub-option is defined as 0xA0 |
161 | PMA Offer | WT-301 Issue 2 Section 16.5.2.2 | Sub-option is defined as 0xA1 |
162-170 | Reserved | WT-301 Issue 2 | WT-301 Issue 2 doesn't mention these sub-options |
RADIUS Attributes
TBD
URN Namespaces
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:
Namespace | Usage | Reference | Notes |
---|---|---|---|
urn:dslforum-org:device: | BBF-defined UPnP devices | TR-064 TR-133 | Both these TRs are DEPRECATED |
urn:dslforum-org:service: | BBF-defined UPnP services | TR-064 | 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 Some examples:
|
urn:dslforum-org:sip | 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 |
urn:broadband-forum-org:
Namespace | Usage | Reference | Notes |
---|---|---|---|
urn:broadband-forum-org:tr-nnn-i-a-c urn:broadband-forum-org:tr-nnn-i-a | References to BBF Technical Reports | TR-106 TR-181 etc. | 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) Some examples:
|
urn:broadband-forum-org:cwmp: | XML Schemas used with CWMP | TR-069 TR-106 | Some examples:
|
urn:bbf:
Namespace | Usage | Reference | Notes |
---|---|---|---|
urn:bbf:yang: | BBF YANG module namespaces | TR-355 etc. | Some examples:
|