Table of Contents
Numbered Headings | ||||||
---|---|---|---|---|---|---|
Names and Numbers Assigned by Other OrganizationsEnterprise |
Table of Contents
Numbered Headings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Names and Numbers Assigned by Other OrganizationsEnterprise Number and OUIThe Broadband Forum Enterprise Number is 3561 decimal (0x0DE9) and is listed in the IANA Private Enterprise Numbers Registry. The Enterprise Number also identifies the BBF’s node in the object identifier (OID) hierarchy, with the full arc extending back to its root defined as follows: 1.3.6.1.4.1.3561. Information on the object identifier hierarchy can be found at ITU-T X.660 and ISO/IEC 9834. The Broadband Forum IEEE OUI is 0x00256D. More information regarding IEEE OUI is at https:The Broadband Forum IEEE OUI is 0x00256D. More information regarding IEEE OUI is at https://standards.ieee.org/develop/regauth/oui/. IANA Interface TypesThe following interface types were registered by BBF with IANA and are listed in on the IANA MIB Module Registrations page, which references the iana-if-type YANG module (there's also an IANA ifType MIB)and the IANAifType MIB.
TCP and UDP PortsThe following ports were registered by BBF with IANA and are listed in the IANA Service Name and Transport Protocol Port Number Registry.
Service NamesThe 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.
URN NamespacesThe 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. Media TypesIANA 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.
WebSocketSubprotocol NameAssignmentsIANA WebSocket Subprotocol Name assignments are listed at https://www.iana.org/assignments/websocket/websocket.xhtml. The following WebSocket Subprotocol Names have been assigned to BBF.
The following WebSocket Extension Names have been assigned to BBF.
Constrained RESTful Environments (CoRE) ParametersIANA CoRE parameter assignments are listed at https://www.iana.org/assignments/core-parameters/core-parameters.xhtml. The following CoRE parameter values have been assigned to BBF.
URN Namespacesurn:dslforum-org:Network Service Header (NSH) ParametersIANA NSH parameter assignments are listed at https://www.iana.org/assignments/nsh. The following NSH Metadata (MD) classes have been assigned to BBF.
TLS Exporter LabelsIANA TLS Exporter Label assignments are listed at https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml. The process for registering new labels is defined in RFC 8447; registration requests should be sent to the tls-reg-review@ietf.org mailing list as specified in section 17. BBF-registered TLS Exporter Label names will be of the form "EXPORTER-BBF-<function>" where "<function>" is a unique function name within the BBF scope.
The following TLS Exporter Labels have been assigned to BBF.
URN Namespacesurn:dslforum-org:
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. |
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 |
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:
Namespace | Usage | Reference | Notes | tr-069-1-5-0|
---|---|---|---|---|
urn:broadband-forum-org:tr-nnn-181i-2a-11c urn:broadband-forum-org:cwmp:tr-nnn-i-a | References to BBF Technical ReportsXML Schemas used with CWMP | TR-069106 TR-106 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:
Some examples:
| |
urn:broadband-forum-org:cwmp:datamodel-1-5 | XML Schemas used with CWMP | TR-069 TR-106 | Some examples:
| |
urn:broadband-forum-org:ipdr: | XML XML Schemas used with IPDR | TR-232 | Some examples:
|
urn:bbf:
Namespace | Usage | Reference | Notes |
---|---|---|---|
urn:bbf:yang: | BBF YANG module namespaces |
TR-383
Within this namespace, the following have been defined:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TR-181i2a12 Appendix XVII provides Theory of Operation and describes usage.
The format for a registry entry within this namespace is:
|
Example:
|
The following IETF references define format of a registry entry and provide examples.
|
|
|
- urn:bbf:usp:id:<Endpoint ID>
Common Sub-option codes used with DHCPv4, DHCPv6, PPPoE and RADIUS. Code range: 1-254 (0x01-0xfe), 8 bits.
Dec
Usage
Reference
Notes
Agent Circuit ID
Actual data rate Upstream
Actual data rate Downstream
DHCP Sub-options
DHCPv4 Option 43 Sub-options (Codes)
RFC 2132 Section 8.4: Option 43: Vendor Specific Information. Code range: 1-254 (0x01-0xfe), 8 bits.
Sub-option usage:
- 1: ACS URL
- 2: Provisioning code
- 3: CWMP retry minimum wait interval
- 4: CWMP retry interval multiplier
DHCPv4 Option 82, Sub-option 9 Codes
RFC 4243: Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option. Code range 1-254 (0x01-0xfe), 8 bits.
The following Sub-options are used with enterprise number 3561 (BBF).
DHCPv4 Option 125 Sub-options
RFC 3925 Section 4: Option 125: Vendor-Identifying Vendor-Specific Information. Sub-option range: 1-254 (0x01-0xfe), 8 bits.
The following Sub-options are used with enterprise number 3561 (BBF).
Sub-option usage:
- 1: Manufacturer OUI
- 2: Product class
- 3: Model name
- 4: Serial number
Sub-options 1-4 overlap with TR-069 Annex F
Sub-option usage:
- 1: Device manufacturer OUI
- 2: Device serial number
- 3: Device product class
- 4: Gateway manufacturer OUI
- 5: Gateway serial number
- 6: Gateway product class
Sub-options 1-4 overlap with TR-124
Sub-option usage:
- 11: ACS URL
- 12: Provisioning code
- 13: CWMP retry minimum wait interval
- 14: CWMP retry interval multiplier
Sub-option usage:
- 21: Tunnel type
- 22: Server endpoint
- 23: Client endpoint
Sub-option usage:
- 24: Device type
USP Controller Discovery
Sub-option usage:
- 25: URL of the Controller
- 26: Provisioning code
- 27: USP retry minimum wait interval
- 28: USP retry interval multiplier
DHCPv6 Option 17 Sub-options
RFC 3315 Section 22.17: Option 17: Vendor-specific Information. Sub-option range: 1-65534 (0x0001-0xfffe), 16 bits.
The following Sub-options are used with enterprise number 3561 (BBF).
Sub-option usage:
- 1: URL of the ACS
- 2: Provisioning code
- 3: CWMP retry minimum wait interval
- 4: CWMP retry interval multiplier
Sub-options 1-2 overlap with TR-156 / TR-177
Sub-option usage:
- 11: Device manufacturer OUI
- 12: Device serial number
- 13: Device product class
- 14: Gateway manufacturer OUI
- 15: Gateway serial number
- 16: Gateway product class
Sub-options 1-6 were used prior to TR-069 Amendment 5
Sub-option usage:
- 22: Server endpoint
- 23: Client endpoint
USP Controller Discovery
- 25: URL of the Controller
- 26: Provisioning code
- 27: USP retry minimum wait interval
- 28: USP retry interval multiplier
PPPoE Tags
PPPoE Tag 261 Sub-options
RFC 2516 Appendix A: Tag 261 (0x0105): Vendor-Specific. Sub-option range: 1-254 (0x01-0xfe), 8 bits.
The following Sub-options are used with enterprise number 3561 (BBF).
PPPoA/oE IWF session flag
TR-101
Indicates the presence of PPPoA/oE IWF session
RADIUS Attributes
RADIUS Attribute 26 Sub-options
RFC 2865 Section 5.26: Tag 26: Vendor-Specific. Sub-option range: 1-254 (0x01-0xfe), 8 bits.
The following Sub-options are used with enterprise number 3561 (BBF).
PPPoA/oE IWF session flag
TR-101
Indicates the presence of PPPoA/oE IWF session
User Services Platform Project Stream
WT-369 is available via the above project stream page.Once finalized, the above link will be replaced by a link to the published and publicly available TR-369.
Common Sub-option codes used with DHCPv4, DHCPv6, PPPoE and RADIUS. Code range: 1-254 (0x01-0xfe), 8 bits.
DHCP Sub-optionsDHCPv4 Option 43 Sub-options (Codes)RFC 2132 Section 8.4: Option 43: Vendor Specific Information. Code range: 1-254 (0x01-0xfe), 8 bits.
DHCPv4 Option 82, Sub-option 9 CodesRFC 4243: Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option. Code range 1-254 (0x01-0xfe), 8 bits. The following Sub-options are used with enterprise number 3561 (BBF).
DHCPv4 Option 125 Sub-optionsRFC 3925 Section 4: Option 125: Vendor-Identifying Vendor-Specific Information. Sub-option range: 1-254 (0x01-0xfe), 8 bits. The following Sub-options are used with enterprise number 3561 (BBF).
DHCPv6 Option 17 Sub-optionsRFC 3315 Section 22.17: Option 17: Vendor-specific Information. Sub-option range: 1-65534 (0x0001-0xfffe), 16 bits. The following Sub-options are used with enterprise number 3561 (BBF).
PPPoE TagsPPPoE Tag 261 Sub-options RFC 2516 Appendix A: Tag 261 (0x0105): Vendor-Specific. Sub-option range: 1-254 (0x01-0xfe), 8 bits. The following Sub-options are used with enterprise number 3561 (BBF).
RADIUS AttributesRADIUS Attribute 26 Sub-options RFC 2865 Section 5.26: Tag 26: Vendor-Specific. Sub-option range: 1-254 (0x01-0xfe), 8 bits. The following Sub-options are used with enterprise number 3561 (BBF).
IP Flow Information Export (IPFIX) Information Element IdentifiersThe following IPFIX IEs are defined by BBF for use with enterprise number 3561 (BBF).
Packet Forwarding Control Protocol (PFCP) Information Element (IE) ExtensionsThe Broadband Forum (BBF) Enterprise Number is 3561 decimal (0x0DE9) and is listed in the IANA Private Enterprise Numbers Registry. PFCP IEs extended by BBF follow the 3GPP TS 29.244 specified format of vendor-specific IEs.
|