Broadband Forum assigned 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.
Enterprise Number
The Broadband Forum Enterprise Number is 3561 decimal (0x0DE9), is registered with IANA, and is listed in the IANA Private Enterprise Numbers registry.
DHCP Sub-options
DHCPv4 Option 43 Sub-options
Option 43: xxx.
DHCPv3 Option 124 Sub-options
Option 124: xxx.
????
DHCPv4 Option 125 Sub-options
Option 125: xxx.
Sub-option | Usage | Reference | Notes |
---|---|---|---|
1-4 | Device info | TR-124 Issue x xxx | Apparent conflict with TR-069 |
1-6 | Device / Gateway association | TR-069 xxx | |
7-10 | Unassigned | ||
11-14 | ACS discovery | ||
15-16 | Unassigned | ||
17-20 | Reserved | ||
21 | Tunnel protocol | TR-317 xxx | |
22-23 | Tunnel endpoints | ||
24 | BRG indication | ||
25-30 | Reserved | ||
160 | DPU Discover | WT-301 Issue 2 xxx | Defined as 0xA0 |
161 | PMA Information | Defined as 0xA1 |
DHCPv6 Option 16 Sub-options
Option 16: xxx.
????
DHCPv6 Option 17 Sub-options
Option 17: Vendor-specific Information.
Sub-option | Usage | Reference | Notes |
---|---|---|---|
1-4 | Device info | TR-124 Issue x xxx | Apparent conflict with TR-069 |
1-4 | ACS discovery | TR-069 Amendment 5 xxx | |
5-10 | Unassigned | ||
11-16 | Device / Gateway association | ||
17-20 | Reserved | ||
21 | Reserved | TR-317 xxx | |
22-23 | Tunnel endpoints | ||
24-30 | Reserved | ||
160 | DPU Discover | WT-301i2 xxx | Defined as 0xA0 |
161 | PMA Information | Defined as 0xA1 |
URN Namespaces
Note: 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.
A namespace (in the table below) that ends with a colon (:) is a prefix, and the referenced standards should define the rules governing the remaining part of the URN.
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; sdp is used only as a flow identifier Note: In theory additional protocol and flow identifiers could be defined (this is unlikely) |
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:yang: | BBF YANG module namespaces | TR-355 etc. | Some examples:
|