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://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. Interface Type | Reference | Notes |
---|
fastdsl | TR-355 | |
| ghn | WTTR-374 |
| ptm | TR-383 |
|
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 Name | Port Number | Transport Protocol | Reference | Notes |
---|
pon-ictp | 7202 | tcp | TR-352 |
| cwmp | 7547 | tcp | TR-069 | ACS and Connection Request URLs can use this port | cwmp | 7547 | udp | TR-069 | UDP 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 Name | Transport Protocol | Published Reference or Current Project | TXT Parameters | Subtypes |
---|
usp-agt-coap | udp | TR-369 | path=<resource path> name=<device or USP friendly name> encrypt code=<provisioning code> retry-min=< USP retry minimum wait interval> retry-mult=< USP retry interval multiplier> | No defined subtypes | usp-agt-http | tcp | TR-369 | usp-agt-mqtt | tcp | TR-369 | usp-agt-stomp | tcp | TR-369 | usp-agt-ws | tcp | TR-369 | usp-ctr-coap | udp | TR-369 | usp-ctr-http | tcp | TR-369 | usp-ctr-mqtt | tcp | TR-369 | usp-ctr-stomp | tcp | TR-369 | usp-ctr-ws | tcp | TR-369 |
URN NamespacesThe 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. 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 Type | Reference |
---|
application/vnd.bbf.usp.error | TR-369: User Services Platform (USP) This Media Type is currently described in the draft Issue 1 Amendment 1 of TR-369. This will be available at the above-referenced URL after TR-369i1a1 is published. | 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. |
WebSocket Subprotocol 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. Range | Meaning |
---|
0x0200 | BBF Specific NSH Metadata |
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. - "<function>" should use words (not acronyms), with initial capital letters and hyphen separators. For example, "EXPORTER-BBF-Dying-Gasp"
The following TLS Exporter Labels have been assigned to BBF. URN Namespacesurn:dslforum-org:Namespace | Usage | Reference | Notes |
---|
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 TR-133 | 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: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-tQoS 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:device: | BBF-defined UPnP devices | TR-064i1 TR-133 | Both these TRs are DEPRECATED TR-064i2 is not deprecated, but does not make use of this namespace. | urn:dslforum-org:service: | BBF-defined UPnP services | TR-064i1 TR-133 | Both these TRs are DEPRECATED TR-064i2 is not deprecated, but does not make use of this namespace. | 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: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 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:Namespace | Usage | Reference | Notes |
---|
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. | 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 CWMP | TR-069 TR-106 | Some examples: urn:broadband-forum-org:cwmp:xmppConnReq-1-0urn:broadband-forum-org:cwmp:lwnotif-1-0urn:broadband-forum-org:cwmp:datamodel-1-5 |
---|
urn:broadband-forum-org:cwmp:datamodel-report-0-1tr-nnn-i-a-c urn:broadband-forum-org:cwmp:devicetypetr-1-3nnn-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:devicetype-featurestr-069-1-5-0
- urn:broadband-forum-org:tr-181-2-11
| urn:broadband-forum-org:cwmpipdr: | XML Schemas used with IPDRCWMP | TR-069 TR-232106 | Some examples: - urn:broadband-forum-org:ipdrcwmp:trxmppConnReq-232-1-0
- urn:
|
bbf:- 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 IPDR | TR-232 | Some examples: - urn:broadband-forum-org:ipdr:tr-232-1-0
|
urn:bbf:Namespace | Usage | Reference | Notes |
---|
urn:bbf:yang: | BBF YANG module namespaces | YANG Projects | Within this namespace, the following have been defined: |
Namespace | Usage | Reference | Notes |
---|
urn:bbf:yang: | BBF YANG module namespaces | TR-355 TR-383 | Within this namespace, the following have been defined: urn:bbf:yang:bbf-availabilityurn:bbf:yang:bbf-dot1q-typesurn:bbf:yang:bbf-ethernet-performance-managementurn:bbf:yang:bbf-fasturn:bbf:yang:bbf-fastdslurn:bbf:yang:bbf-frame-classificationghnghshardwarerpfdpuhardwarerpfdpustate- extensions
- urn:bbf:yang:bbf-ancp-
| hardwaretypes- thresholds
- urn:bbf:yang:bbf-
| iftype- interfaces
- urn:bbf:yang:bbf-
| inet-types- availability
- urn:bbf:yang:bbf-
| interfacesperformance-managementinterfaces-statistics-managementinterfaceusage- dhcpra
- urn:bbf:yang:bbf-d-
| l2dhcpv4relayl2dhcpv4relay-forwardingl2-forwarding- d-olt-network-function-types
- urn:bbf:yang:bbf-
| l2forwardingsharedfdbldra- olt-onuauth
- urn:bbf:yang:bbf-
| melt- d-olt-pppoe-intermediate-agent
- urn:bbf:yang:bbf-
| mgmdmgmdtypes- aggregation
- urn:bbf:yang:bbf-
| pppoeintermediate-agentptm- dot1q-cfm
- urn:bbf:yang:bbf-dot1q-cfm-
| qosclassifiersqosenhancedscheduling- interfaces
- urn:bbf:yang:bbf-
| qos-filters- dot1q-cfm-interfaces-state
- urn:bbf:yang:bbf-
| qospolicerenvelopeprofiles- forwarding
- urn:bbf:yang:bbf-
| qospoliciesqos-policies-sub-interfaces- end-user
- urn:bbf:yang:bbf-
| qospolicing- inventory
- urn:bbf:yang:bbf-
| qospolicingtypes- management
- urn:bbf:yang:bbf-
| qos-rate-controlqosshapingqos-traffic-mngtqostypes- classification
- urn:bbf:yang:bbf-frame-
| selt- processing-profiles
- urn:bbf:yang:bbf-
| subinterfacessub-interface-taggingsubscriberprofilessubscriber-typesvdslyangtypeslmap:BBF LMAP Performance Metrics Registry | TR-181i2a12 Appendix XX | TR-181i2a12 Appendix XX provides Theory of Operation and describes usage. - yang:bbf-grpc-server
- urn:bbf:yang:bbf-hardware
| The format for a registry entry within this namespace is:lmap:<BBF TR>:<DiagnosticProfileName>Example: - yang:bbf-hardware-cpu
- urn:bbf:
| lmaptr1812-11-0:UploadDiagnostics-1The following IETF references define format of a registry entry and provide examples. draft-ietf-ippm-metric-registrydraft-ietf-ippm-initial-registryuspUSP | TR-369 | Within this namespace, the following have been defined in TR-369:- urn:bbf:usp:id:<Endpoint ID>
| Anchor |
---|
|