Versions Compared

Old Version 7

changes.mady.by.user William Lupton

Saved on

compared with

New Version 8

changes.mady.by.user William Lupton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt

Broadband Forum assigned names and numbers.


Table of Contents

Introduction

Note

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.

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.

TCP and UDP Ports

The following ports are listed in the IANA Service Name and Transport Protocol Port Number Registry.

Service NamePort NumberTransport ProtocolReferenceNotes
cwmp7547tcpTR-069 ACS and Connection Request URLs can use this port
cwmp7547udpTR-069 UDP Connection Request URL can use this port (it's the default)

DHCP Sub-options

DHCPv4 Option 43 Sub-options

Option 43: xxx.

DHCPv3 Option 124 Sub-options

Option 124: xxx.

...

 Vendor Specific Information.

Sub-optionUsageReferenceNotes
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

DHCPv4 Option 125 Sub-options

Option 125: xxxVendor-Identifying Vendor-Specific Information.

Issue x xxxApparent conflict xxx  17Tunnel protocol xxx   Discover 2 xxxDefined InformationDefined
Sub-optionUsageReferenceNotes
1-4Device infoTR-124 WAN.DHCPC

Sub-option usage:

  • 1: Manufacturer OUI
  • 2: Product class
  • 3: Model name
  • 4: Serial number

These sub-options 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 ReservedTR-069 Annex FTR-069 doesn't mention these sub-options
11-14ACS discovery  
15-16Unassigned  
TR-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-20Reserved  21TR-069TR-069 doesn't mention these sub-options
21-23GRE tunnelingTR-317  
22-23Tunnel endpoints  
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
24BRG indication 
25-30Reserved TR-317TR-317 doesn't mention these sub-options
160DPU DiscoveryWT-301 Issue 2 Section 16.5.2.1

Sub-option is defined as 0xA0

161PMA OfferWT-301 Issue 2 Section 16.5.2.2Sub-option is defined   as 0xA1

DHCPv6 Option 16 Sub-options

Option 16: xxx.

...

162-170ReservedWT-301 Issue 2WT-301 Issue 2 doesn't mention these sub-options

DHCPv6 Option 17 Sub-options

Option 17: Vendor-specific Information.

Device info124 Issue x xxx Unassigned    xxx    Discover301i2 xxxDefined InformationDefined as 0xA1
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
Apparent conflict with TR-0691-4ACS discoveryTR-069 Amendment 5 xxx
5-10Reserved TR-069TR-069 doesn't mention these sub-options
11-16Device / Gateway association TR-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

Prior to TR-069 Amendment 5, sub-options 1-6 were used

17-20Reserved TR-069TR-069 doesn't mention these sub-options
21ReservedTR-317TR-317 doesn't mention this sub-option
22-23Tunnel endpoints GRE tunnelingTR-317 Section 7.1.3.3.2

Sub-option usage:

  • 22: Server endpoint
  • 23: Client endpoint
24-30Reserved TR-317TR-317 doesn't mention these sub-options
160DPU DiscoveryWT-301 Issue 2 Section 16.5.2.1

Sub-option is defined

as 0xA0

161PMA  OfferWT-301 Issue 2 Section 16.5.2.2Sub-option is defined as 0xA1
162-170ReservedWT-301 Issue 2WT-301 Issue 2 doesn't mention these sub-options

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.

Note

A namespace (in the tables below) that ends with a colon (:) is a prefix, and the referenced standards should define the rules governing the remaining part of the URN.

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:bbf:

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

Some examples:

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