Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

Broadband Forum assigned names and numbers. 

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 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 
ptmWT-383 

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
cwmp7547tcpTR-069ACS and Connection Request URLs can use this port
cwmp7547udpTR-069UDP Connection Request URL can use this port (it's the default)

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-coapudpUSP Project

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-httptcpUSP Project
usp-agt-stomptcpUSP Project
usp-ctr-coapudpUSP Project
usp-ctr-httptcpUSP Project
usp-ctr-stomptcpUSP Project

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.

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.

URN Namespaces

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

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

urn:bbf:

NamespaceUsageReferenceNotes
urn:bbf:yang:BBF YANG module namespacesTR-355
etc. 

Some examples:

  • urn:bbf:yang:bbf-fastdsl
  • urn:bbf:yang:bbf-fast

DHCP Sub-options

DHCPv4 Option 43 Sub-options (Codes)

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

CodeUsageReferenceNotes
1-4ACS 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-254Unassigned  

DHCPv4 Option 125 Sub-options

RFC 3925 Section 4: Option 125: Vendor-Identifying Vendor-Specific Information. Sub-option range: 1-254 (8 bits).

Sub-optionUsageReferenceNotes
1-4Device 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 but this is unlikely to be a practical problem.

1-6Device / 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
7-10Unassigned  
11-14ACS 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
15-16ReservedTR-069Reserved because they're assigned as DHCPv6 option 17 sub-options
17-20Unassigned  
21-23GRE tunnelingTR-317 Section 7.1.3.3.2

Sub-option usage:

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

Sub-option usage:

  • 24: Device type
25-254Unassigned  

DHCPv6 Option 17 Sub-options

RFC 3315 Section 22.17: Option 17: Vendor-specific Information. Sub-option range: 1-65534 (16 bits).

Sub-optionUsageReferenceNotes
1-4ACS 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
5-6ReservedTR-069Reserved because they were used prior to TR-069 Amendment 5, and because they're assigned as DHCPv4 option 125 sub-options
7-10Unassigned  
11-16Device / 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-20Unassigned  
21ReservedTR-317Reserved because it's assigned as a DHCPv4 option 125 sub-option
22-23GRE tunnelingTR-317 Section 7.1.3.3.2

Sub-option usage:

  • 22: Server endpoint
  • 23: Client endpoint
24ReservedTR-317Reserved because it's assigned as a DHCPv4 option 125 sub-option
25-65534Unassigned  

RADIUS Attributes

TBD

  • No labels