Skip to end of metadata
Go to start of metadata
About this page

This is a publicly viewable page on the Broadband Forum's collaborative members' wiki. It lists the Broadband Forum "assigned names and numbers", i.e. things like URN prefixes, TCP port numbers and DHCP options that are used within BBF standards. These names and numbers are a mixture of those assigned by outside organizations, e.g. IANA (Internet Assigned Numbers Authority) and those assigned directly by BBF.

Link for Public Visitors

Return to the
BBF Public web site
  

Table of Contents

1. Names and Numbers Assigned by Other Organizations

1.1. Enterprise Number and OUI

The Broadband Forum Enterprise Number is 3561 decimal (0x0DE9) and is listed in the IANA Private Enterprise Numbers Registry.

The Broadband Forum IEEE OUI is 0x00256D. More information regarding IEEE OUI is at https://standards.ieee.org/develop/regauth/oui/.

1.2. IANA Interface Types

The following interface types were registered by BBF with IANA and are listed in the iana-if-type YANG module (there's also an IANA ifType MIB).

Interface TypeReferenceNotes
fastdslTR-355 
ghnWT-374
ptmTR-383 

1.3. 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 NamePort NumberTransport ProtocolReferenceNotes
pon-ictp7202tcpTR-352
cwmp7547tcpTR-069ACS and Connection Request URLs can use this port
cwmp7547udpTR-069UDP Connection Request URL can use this port (it's the default)

1.4. Service Names

The 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.

Service NameTransport ProtocolPublished Reference or Current ProjectTXT ParametersSubtypes
usp-agt-coapudpTR-369

path=<resource path>

name=<device or USP friendly name>

code=<provisioning code>

retry-min=< USP retry mini­mum wait interval>

retry-mult=< USP retry interval multiplier>

No defined subtypes
usp-agt-httptcpTR-369
usp-agt-stomptcpTR-369
usp-agt-wstcpTR-369
usp-ctr-coapudpTR-369
usp-ctr-httptcpTR-369
usp-ctr-stomptcpTR-369
usp-ctr-wstcpTR-369

1.5. URN Namespaces

The dslforum-org, broadband-forum-org and bbf URN namespaces have been registered with IANA. See RFC 8057 (URN Namespaces for Broadband Forum).

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.

1.6. Media Types

IANA 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.

Media TypeReference
application/vnd.bbf.usp.msg

TR-369: User Services Platform (USP)

application/vnd.bbf.usp.msg+json 

TR-369: User Services Platform (USP)

This Media Type is not mentioned in the USP specification, as it is not intended for use in active deployments. It is intended for debugging and testing purposes only. It indicates the USP Record and Message headers are expressed in JSON without Protobuf encoding.

1.7. WebSocket Subprotocol Name

IANA 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.

WebSocket Subprotocol NameReference
v1.usp

TR-369: User Services Platform (USP)

1.8. Constrained RESTful Environments (CoRE) Parameters

IANA 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.

RegistryCoRE Parameter ValueReference

Resource Type (rt=) Link Target Attribute

bbf.usp.endpoint

TR-369: User Services Platform (USP)

Interface Description (if=) Link Target Attribute

bbf.usp.c

TR-369: User Services Platform (USP)

Interface Description (if=) Link Target Attribute

bbf.usp.a

TR-369: User Services Platform (USP)


2. URN Namespaces

2.1. urn:dslforum-org:

NamespaceUsageReferenceNotes
urn:dslforum-org:device:BBF-defined UPnP devicesTR-064
TR-133 
Both these TRs are DEPRECATED
urn:dslforum-org:service:BBF-defined UPnP services

TR-064
TR-133

Both these TRs are DEPRECATED

urn:dslforum-org:cwmp-n-mCWMP version n.mTR-069

n and m indicate the CWMP major and minor version respectively

Some examples:

  • urn:dslforum-org:cwmp-1-0
  • urn:dslforum-org:cwmp-1-1

urn:dslforum-org:sip
urn:dslforum-org:h.323
urn:dslforum-org:h.248
urn:dslforum-org:mgcp
urn:dslforum-org:pppoe
urn:dslforum-org:sdp-m-t

QoS protocol and flow identifiersTR-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

2.2. urn:broadband-forum-org:

NamespaceUsageReferenceNotes
urn:broadband-forum-org:tr-nnn-i-a-c
urn:broadband-forum-org:tr-nnn-i-a
References to BBF Technical ReportsTR-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:tr-069-1-5-0
  • urn:broadband-forum-org:tr-181-2-11
urn:broadband-forum-org:cwmp:XML Schemas used with CWMPTR-069
TR-106 

Some examples:

  • urn:broadband-forum-org:cwmp:xmppConnReq-1-0
  • urn:broadband-forum-org:cwmp:lwnotif-1-0
  • urn:broadband-forum-org:cwmp:datamodel-1-5
  • urn:broadband-forum-org:cwmp:datamodel-report-0-1
  • urn:broadband-forum-org:cwmp:devicetype-1-3
  • urn:broadband-forum-org:cwmp:devicetype-features
urn:broadband-forum-org:ipdr:XML Schemas used with IPDRTR-232

Some examples:

  • urn:broadband-forum-org:ipdr:tr-232-1-0

2.3. urn:bbf:

NamespaceUsageReferenceNotes
urn:bbf:yang:BBF YANG module namespacesTR-355
TR-383

Within this namespace, the following have been defined:

  • urn:bbf:yang:bbf-availability
  • urn:bbf:yang:bbf-dot1q-types
  • urn:bbf:yang:bbf-ethernet-performance-management
  • urn:bbf:yang:bbf-fast
  • urn:bbf:yang:bbf-fastdsl
  • urn:bbf:yang:bbf-frame-classification
  • urn:bbf:yang:bbf-ghn
  • urn:bbf:yang:bbf-ghs
  • urn:bbf:yang:bbf-if-type
  • urn:bbf:yang:bbf-inet-types
  • urn:bbf:yang:bbf-interfaces-performance-management
  • urn:bbf:yang:bbf-interfaces-statistics-management
  • urn:bbf:yang:bbf-interface-usage
  • urn:bbf:yang:bbf-l2-dhcpv4-relay
  • urn:bbf:yang:bbf-l2-dhcpv4-relay-forwarding
  • urn:bbf:yang:bbf-l2-forwarding
  • urn:bbf:yang:bbf-l2-forwarding-shared-fdb
  • urn:bbf:yang:bbf-ldra
  • urn:bbf:yang:bbf-melt
  • urn:bbf:yang:bbf-mgmd
  • urn:bbf:yang:bbf-mgmd-types
  • urn:bbf:yang:bbf-pppoe-intermediate-agent
  • urn:bbf:yang:bbf-ptm
  • urn:bbf:yang:bbf-qos-classifiers
  • urn:bbf:yang:bbf-qos-enhanced-scheduling
  • urn:bbf:yang:bbf-qos-filters
  • urn:bbf:yang:bbf-qos-policer-envelope-profiles
  • urn:bbf:yang:bbf-qos-policies
  • urn:bbf:yang:bbf-qos-policies-sub-interfaces
  • urn:bbf:yang:bbf-qos-policing
  • urn:bbf:yang:bbf-qos-policing-types
  • urn:bbf:yang:bbf-qos-rate-control
  • urn:bbf:yang:bbf-qos-shaping
  • urn:bbf:yang:bbf-qos-traffic-mngt
  • urn:bbf:yang:bbf-qos-types
  • urn:bbf:yang:bbf-selt
  • urn:bbf:yang:bbf-sub-interfaces
  • urn:bbf:yang:bbf-sub-interface-tagging
  • urn:bbf:yang:bbf-subscriber-profiles
  • urn:bbf:yang:bbf-subscriber-types
  • urn:bbf:yang:bbf-vdsl
  • urn:bbf:yang:bbf-yang-types

urn:bbf:lmap:

BBF LMAP Performance Metrics RegistryTR-181i2a12 Appendix XX

TR-181i2a12 Appendix XX provides Theory of Operation and describes usage.

The format for a registry entry within this namespace is:

  • urn:bbf:lmap:<BBF TR>:<DiagnosticProfileName>

Example:

  • urn:bbf:lmap:tr-181-2-11-0:UploadDiagnostics-1

The following IETF references define format of a registry entry and provide examples.

urn:bbf:usp:USPTR-369Within this namespace, the following have been defined in TR-369:
  • urn:bbf:usp:id:<Endpoint ID>

3. Common Sub-options

Common Sub-option codes used with DHCPv4, DHCPv6, PPPoE and RADIUS. Code range: 1-254 (0x01-0xfe), 8 bits.

Dec

Hex

Usage

Reference

Notes

10x01

Agent Circuit ID

TR-156 / TR-177
20x02Agent Remote IDTR-156 / TR-177
3-1280x03-0x80Unassigned

1290x81

Actual data rate Upstream

TR-156 / TR-17732 bit binary value in kbps
1300x82

Actual data rate Downstream

TR-156 / TR-17732 bit binary value in kbps
1310x83Minimum Data Rate UpstreamTR-156 / TR-17732 bit binary value in kbps
1320x84Minimum Data Rate DownstreamTR-156 / TR-17732 bit binary value in kbps
1330x85Attainable Data Rate UpstreamTR-156 / TR-17732 bit binary value in kbps
1340x86Attainable Data Rate DownstreamTR-156 / TR-17732 bit binary value in kbps
1350x87Maximum Data Rate UpstreamTR-156 / TR-17732 bit binary value in kbps
1360x88Maximum Data Rate DownstreamTR-156 / TR-17732 bit binary value in kbps
1370x89Minimum Data Rate Upstream in low power stateTR-156 / TR-17732 bit binary value in kbps
1380x8aMinimum Data Rate Downstream in low power stateTR-156 / TR-17732 bit binary value in kbps
1390x8bMaximum Interleaving Delay UpstreamTR-156 / TR-17732 bit binary value in milliseconds
1400x8cActual interleaving Delay UpstreamTR-156 / TR-17732 bit binary value in milliseconds
1410x8dMaximum Interleaving Delay DownstreamTR-156 / TR-17732 bit binary value in milliseconds
1420x8eActual interleaving Delay DownstreamTR-156 / TR-17732 bit binary value in milliseconds
1430x8fUnassigned

1440x90Access loop encapsulationTR-101 Appendix A24 bit binary value
145-1540x91-0x9aUnassigned

1550x9bExpected throughput (ETR) upstreamTR-30132 bit binary value in kbps
1560x9cExpected throughput (ETR) downstreamTR-30132 bit binary value in kbps
1570x9dAttainable expected throughput (ATTETR) upstreamTR-30132 bit binary value in kbps
1580x9eAttainable expected throughput (ATTETR) downstreamTR-30132 bit binary value in kbps
1590x9fGamma data rate (GDR) upstreamTR-30132 bit binary value in kbps
1600xa0Gamma data rate (GDR) downstreamTR-30132 bit binary value in kbps
1610xa1Attainable gamma data rate (ATTGDR) upstreamTR-30132 bit binary value in kbps
1620xa2Attainable gamma data rate (ATTGDR) downstreamTR-30132 bit binary value in kbps
163-1910xa3-0xbfUnassigned

1920xc0DPU DiscoveryTR-301 Issue 2 Section 16.5.2.1


1930xc1PMA OfferTR-301 Issue 2 Section 16.5.2.2
194-2540xc2-0xfeUnassigned

4. DHCP Sub-options

4.1. DHCPv4 Option 43 Sub-options (Codes)

RFC 2132 Section 8.4: Option 43: Vendor Specific Information. Code range: 1-254 (0x01-0xfe), 8 bits.

DecHexUsageReferenceNotes
1-40x01-0x04ACS discoveryTR-069 Section 3.1

Sub-option usage:

  • 1: ACS URL
  • 2: Provisioning code
  • 3: CWMP retry minimum wait interval
  • 4: CWMP retry interval multiplier
5-2540x05-0xfeUnassigned  

4.2. 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).

DecHexUsageReferenceNotes
1-20x01-0x02Common Sub-optionsTR-156 / TR-177


3-1280x03-0x80Unassigned

129-1420x81-0x8eCommon Sub-options
TR-156 / TR-177
1430x8fUnassigned

1440x90Common Sub-options
TR-101 Appendix A
145-1540x91-0x9aUnassigned

155-1620x9b-0xa2Common Sub-options
TR-301
163-1910xa3-0xbfUnassigned

192-1930xc0-0xc1Common Sub-options
TR-301 Issue 2
194-2540xc2-0xfeUnassigned

4.3. 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).

DecHexUsageReferenceNotes
1-40x01-0x04Device infoTR-124 WAN.DHCPC

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

1-60x01-0x06Device / Gateway associationTR-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

7-100x07-0x0aUnassigned  
11-140x0b-0x0eACS discoveryTR-069 Section 3.1

Sub-option usage:

  • 11: ACS URL
  • 12: Provisioning code
  • 13: CWMP retry minimum wait interval
  • 14: CWMP retry interval multiplier
15-160x0f-0x10ReservedTR-069Reserved because they're assigned as DHCPv6 option 17 sub-options
17-200x11-0x14Unassigned  
21-230x15-0x17GRE tunnelingTR-317 Section 7.1.3.3.2

Sub-option usage:

  • 21: Tunnel type
  • 22: Server endpoint
  • 23: Client endpoint
240x18Client requirementsTR-317 Section 7.4.3.7

Sub-option usage:

  • 24: Device type
25-280x19-0x1c

USP Controller Discovery

TR-369 Discovery and Advertisement

Sub-option usage: 

  • 25: URL of the Controller
  • 26: Provisioning code
  • 27: USP retry mini­mum wait interval
  • 28: USP retry interval multiplier
29-1910x1d-0xbfUnassigned  
192-1930xc0-0xc1Common Sub-optionsTR-301 Issue 2 
194-2540xc2-0xfeUnassigned  

4.4. 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).

DecHexUsageReferenceNotes
1-20x0001-0x0002

Common Sub-options

TR-156 / TR-177Sub-options 1-2 overlap with TR-069
1-40x0001-0x0004ACS discoveryTR-069 Section 3.1

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

5-60x0005-0x0006ReservedTR-069Reserved because they were used prior to TR-069 Amendment 5, and because they're assigned as DHCPv4 option 125 sub-options
7-100x0007-0x000aUnassigned  
11-160x000b-0x0010Device / Gateway associationTR-069 Annex F

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

17-200x0011-0x0014Unassigned  
210x0015ReservedTR-317Reserved because it's assigned as a DHCPv4 option 125 sub-option
22-230x0016-0x0017GRE tunnelingTR-317 Section 7.1.3.3.2

Sub-option usage:

  • 22: Server endpoint
  • 23: Client endpoint
240x0018ReservedTR-317Reserved because it's assigned as a DHCPv4 option 125 sub-option
25-280x0019-0x001c

USP Controller Discovery

TR-369 Discovery and AdvertisementSub-option usage: 
  • 25: URL of the Controller
  • 26: Provisioning code
  • 27: USP retry mini­mum wait interval
  • 28: USP retry interval multiplier
29-1280x001d-0x0080Unassigned  
129-1420x0081-0x008eCommon Sub-options
TR-156 / TR-177
1430x008fUnassigned

1440x0090Common Sub-options
TR-101 Appendix A
145-1540x0091-0x009aUnassigned

155-1620x009b-0x00a2Common Sub-options
TR-301
163-1910x00a3-0x00bfUnassigned

192-1930x00c0-0x00c1Common Sub-options
TR-301 Issue 2
194-655340x00c2-0xfffeUnassigned

5. 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).

DecHexUsageReferenceNotes
1-20x01-0x02

Common Sub-options

TR-156 / TR-177
3-1280x03-0x80Unassigned

129-1420x81-0x8eCommon Sub-options
TR-156 / TR-177
1430x8fUnassigned

1440x90Common Sub-options
TR-101 Appendix A
145-1540x91-0x9aUnassigned

155-1620x9b-0xa2Common Sub-options
TR-301
163-2530xa3-0xfdUnassigned

2540xfe

PPPoA/oE IWF session flag

TR-101

Indicates the presence of PPPoA/oE IWF session

6. 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).

DecHexUsageReferenceNotes
1-20x01-0x02

Common Sub-options

TR-156 / TR-177
3-1280x03-0x80Unassigned

129-1420x81-0x8eCommon Sub-options
TR-156 / TR-177
1430x8fUnassigned

1440x90Common Sub-options
TR-101 Appendix A
145-1540x91-0x9aUnassigned

155-1620x9b-0xa2Common Sub-options
TR-301
163-2530xa3-0xfdUnassigned

2540xfe

PPPoA/oE IWF session flag

TR-101

Indicates the presence of PPPoA/oE IWF session

Media TypeReferenceapplication/vnd.bbf.usp.msg

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.

  • No labels