Broadband Forum assigned 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?
Q: How should we reference WTs and TRs?
Q: Should we mention deprecated TRs at all, e.g. TR-064, TR-133, TR-098, TR-181 Issue 1?
|
The Broadband Forum Enterprise Number is 3561 decimal (0x0DE9) and is listed in the IANA Private Enterprise Numbers Registry.
The following ports 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 | |
| cwmp | 7547 | udp | TR-069 |
Option 43: xxx.
Option 124: xxx.
????
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 |
Option 16: xxx.
????
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 |
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, 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: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:
|