4.4 MGMT – Management &
Diagnostics 
4.4.1 MGMT.GEN – General 
4.4.2 MGMT.UPnP – UPnP 
4.4.2.1 MGMT.UPnP.IGD – UPnP IGD 
ID | Requirement |
---|---|
MGMT.UPnP.IGD.1 ![]() |
This requirement has been replaced by MGMT.UPnP.IGD.4. |
MGMT.UPnP.IGD.2 ![]() |
The RG MUST allow the user to enable logging of all UPnP IGD actions and events. |
MGMT.UPnP.IGD.3 ![]() |
The user SHOULD be warned upon enabling UPnP IGD that this may allow applications to configure the box and allow unintended access to local devices. |
MGMT.UPnP.IGD.4 ![]() |
At a minimum, the RG MUST support UPnP InternetGatewayDevice:2 device template version 1.01 standardized DCP. This specification is available for download at http://www.upnp.org. |
4.4.2.1.1 MGMT.UPnP.IGD.ACRF – UPnP
IGD to allow Connection Request Forwarding 
ID | Requirement |
---|---|
MGMT.UPnP.IGD.ACRF.1 ![]() |
The RG MUST support UPnP Internet Gateway Device:2 root device. This specification is available for download at http://upnp.org/specs/gw/UPnP-gw-InternetGatewayDevice-v2-Device.pdf |
MGMT.UPnP.IGD.ACRF.2 ![]() |
The RG MUST support IGD specific security as defined in section 2.3 Security Policies of UPnP InternetGatewayDevice:2. |
MGMT.UPnP.IGD.ACRF.3 ![]() |
Across resets or reboots, the RG MUST remove port mappings and pinholes. |
4.4.2.1.1.1
MGMT.UPnP.IGD.ACRF.IPv4 – UPnP IGD to allow Connection Request
Forwarding through the NAT of the 
device {#req:mgmt.upnp.igd.acrf.ipv4}
ID | Requirement |
---|---|
MGMT.UPnP.IGD.ACRF.IPv4.1 ![]() |
When the external IP address (ExternalIPAddress parameter) of the RG changes, the RG MUST continue to forward packets received on the new external IP as defined by the existing NAT port mappings rules |
MGMT.UPnP.IGD.ACRF.IPv4.2 ![]() |
The RG MUST have a WANIPConnection:2 service when supporting a WAN IP Connection. The specification is available for download at http://upnp.org/specs/gw/UPnP-gw-WANIPConnection-v2-Service.pdf |
MGMT.UPnP.IGD.ACRF.IPv4.3 ![]() |
The RG MUST have a WANPPPConnection:1 service when supporting a WAN PPP Connection. The specification is available for download at http://upnp.org/specs/gw/UPnP-gw-WANPPPConnection-v1-Service.pdf |
MGMT.UPnP.IGD.ACRF.IPv4.4 ![]() |
When supporting a WAN PPP Connection, the RG MUST support internal and external port values being different (the RG MUST NOT return SamePortValuesRequired on AddPortMapping). |
MGMT.UPnP.IGD.ACRF.IPv4.5 ![]() |
When supporting a WAN PPP Connection, the RG MUST support non permanent leases on port mappings (the RG MUST NOT return OnlyPermanentLeasesSupported on AddPortMapping). |
MGMT.UPnP.IGD.ACRF.IPv4.6 ![]() |
When supporting a WAN PPP Connection, the RG MUST support specific IP address for RemoteHost (the RG MUST NOT return RemoteHostOnlySupportsWildcard on AddPortMapping). |
MGMT.UPnP.IGD.ACRF.IPv4.7 ![]() |
When supporting a WAN PPP Connection, the RG MUST support specific port value for external port (the RG MUST NOT return ExternalPortOnlySupportsWildcard on AddPortMapping). |
MGMT.UPnP.IGD.ACRF.IPv4.8 ![]() |
The RG MUST support NAT (UPnP NATEnabled state variable set to “1” as well as UPnP ConnectionType state variable set to “IP_Routed”). |
4.4.2.1.1.2
MGMT.UPnP.IGD.ACRF.IPv6 – UPnP IGD to allow Connection Request
Forwarding through the Firewall 
of the device {#req:mgmt.upnp.igd.acrf.ipv6}
ID | Requirement |
---|---|
MGMT.UPnP.IGD.ACRF.IPv6.1 ![]() |
The RG MUST have a WANIPv6FirewallControl:1 service. The specification is available for download at http://upnp.org/specs/gw/UPnP-gw-WANIPv6FirewallControl-v1-Service.pdf |
MGMT.UPnP.IGD.ACRF.IPv6.2 ![]() |
The RG MUST allow Inbound Pinhole management (InboundPinholeAllowed set to “1”). |
4.4.3 MGMT.LOCAL – Local Management 
ID | Requirement |
---|---|
MGMT.LOCAL.1
![]() |
If the RG is in a bridged configuration the RG MUST be able to disable all LAN side configuration mechanisms (i.e. the Web GUI, Broadband Forum TR-064i2 [158], etc.). |
MGMT.LOCAL.2
![]() |
The RG MUST support a configuration mechanism from the PC as defined in Broadband Forum TR-064i2 [158]. |
MGMT.LOCAL.3
![]() |
This requirement has been obsoleted. |
MGMT.LOCAL.4
![]() |
The RG MUST be configurable via embedded, easy-to-use Web GUI pages. |
MGMT.LOCAL.5
![]() |
Broadband Forum TR-064i2 [158] and Web GUI authorization MUST time out after 30 minutes of disuse. |
MGMT.LOCAL.6
![]() |
The Web GUI pages MUST be available when the RG is in bridged mode. |
MGMT.LOCAL.7
![]() |
The RG MUST NOT require browser support of Java, ActiveX nor VBSCRIPT in its web pages. |
MGMT.LOCAL.8
![]() |
The Web GUI pages SHOULD minimize internal page complexity (e.g. excessive use of frames, pop-ups, style sheets, JavaScript, etc.) that places demands on browser resources or causes interoperability problems with different browsers. In general, all pages SHOULD load within five seconds. |
MGMT.LOCAL.9
![]() |
The web interface MUST be OS independent and browser independent (e.g. must work with versions of Internet Explorer, Firefox, Chrome, Safari and Opera that were released within the past five years). |
MGMT.LOCAL.10
![]() |
The RG MUST have a software mechanism by which the user can reset it to default factory settings. |
MGMT.LOCAL.11
![]() |
The RG MUST support an RG access code (i.e. password) that protects it from being updated (firmware, configuration, operational state, etc.) from the local LAN. |
MGMT.LOCAL.12
![]() |
If a default RG access code has been set, the default RG access code MUST be on the bottom of the RG. |
MGMT.LOCAL.13
![]() |
If a default RG access code has been set, the RG MUST force the user to accept the default RG access code or install a new RG access code prior to allowing any initial configuration (e.g. during initial installation or after an RG reset to factory defaults). |
MGMT.LOCAL.14
![]() |
The user MUST be able to disable the use of the RG access code. The user MUST be warned in the Web GUI of the implications of undertaking this action. |
MGMT.LOCAL.15
![]() |
The RG MUST support updating of its firmware via the Web GUI and Broadband Forum TR-064i2 [158] interfaces. |
MGMT.LOCAL.16
![]() |
The RG MUST use standard protocols when using FTP, HTTP and HTTPS as defined in IETF RFCs 959, 2616, 5246, and 2818. |
MGMT.LOCAL.17
![]() |
The RG MUST support restarting the broadband connection (all layers) via the Web GUI and Broadband Forum TR-064i2 [158] interfaces. |
MGMT.LOCAL.18
![]() |
The RG SHOULD be able to copy log files to a PC on the local LAN or network server in ASCII text format, using the Web GUI and Broadband Forum TR-064i2 [158] interfaces. |
MGMT.LOCAL.19
![]() |
The RG MUST have a quick start page in the Web GUI allowing for rapid configuration in a minimum number of steps (e.g. on a single page). Default values for PPPoE and PVC can be used to facilitate this. |
MGMT.LOCAL.20
![]() |
The model and firmware/software versions MUST be easily identifiable via the Web GUI interface. |
MGMT.LOCAL.21
![]() |
The Web GUI interface MUST allow the user to browse and select an update file from a local PC and use HTTP to update the RG using this file (see IETF RFCs 1867, 2388 and HTML 4.1 specifications for more details). |
MGMT.LOCAL.22
![]() |
If the RG has been configured to do so, the Web GUI MUST allow the user to specify that firmware be updated from a predefined web location. The RG MUST allow the web location to be specified via the Web GUI and Broadband Forum TR-064i2 [158] interfaces. |
MGMT.LOCAL.23
![]() |
The web location MAY be predefined by the RG manufacturer. This value is overridden by the mechanisms and information identified in requirement MGMT.LOCAL.21. |
MGMT.LOCAL.24
![]() |
If the RG has been configured to allow updating from a predefined web location, the RG MUST display an update button in the Web GUI. The user can then select the update button to initiate an update using a file retrieved via ftp or http as identified in the associated URL (2 URLs may be hard coded; the second URL will be used if file retrieval is not possible from the first URL). |
If the RG has been configured to allow updating from a predefined web location, the mechanism used to identify the availability of an update, the description of the update and the actual update SHOULD operate solely based on the presence (or absence) of named files returned in a directory list using the web location URL. For example, an RG might retrieve the directory list, find the update associated with the RG by the presence of the following file: Vendor-model-v100210-n100215.pkg This would identify that for device “model” from “vendor” currently running version 10.02.10 there exists an update whose version is 10.02.15. The text describing the update, if available, might be located in a file of the name: Vendor-model-v100210-n100215.txt |
|
MGMT.LOCAL.26
![]() |
If the RG has been configured to do so, the Web GUI MUST display a web link to which the user may go to browse for update files and other update information. The RG MUST allow this URL to be specified and overridden by the Broadband Forum TR-064i2 [158] interfaces and from a Controller. |
MGMT.LOCAL.27
![]() |
The web link MAY be set to a default value by the RG manufacturer. |
4.4.3.1 MGMT.LOCAL.TR-064 – TR-064
Issue 2 
ID | Requirement |
---|---|
MGMT.LOCAL.TR-064.1 ![]() |
The RG MUST support requirements defined in Broadband Forum TR-064i2 [158]. |
MGMT.LOCAL.TR-064.2 ![]() |
The RG SHOULD support logging of all Broadband Forum TR-064i2 [158] actions and events. |
4.4.4 MGMT.REMOTE – Remote Management 
4.4.4.1 MGMT.REMOTE.TR-069 – Remote
Management (TR-069) 
ID | Requirement |
---|---|
MGMT.REMOTE.TR-069.1 ![]() |
The RG MUST support the remote management protocol as defined in Broadband Forum TR-069 [160] CPE WAN Management protocol. |
MGMT.REMOTE.TR-069.2 ![]() |
The RG MUST support the latest version of Broadband Forum Device:2 [167] data model for CWMP (profile Baseline:3). |
MGMT.REMOTE.TR-069.3 ![]() |
If the RG supports built-in file sharing clients (e.g. Windows networking, CIFS, Samba) or includes integrated storage server functions, the RG MUST NOT allow the use of the TR-069 file transfer mechanisms (i.e. upload and download RPCs) to place or retrieve files that are not explicitly authorized by the user on network shared storage locations to which the RG may have access. |
4.4.4.2 MGMT.REMOTE.USP – Remote
Management (USP) 
ID | Requirement |
---|---|
MGMT.REMOTE.USP.1 ![]() |
The RG MUST support the remote management protocol as defined in Broadband Forum User Services Platform (USP) [169]. |
MGMT.REMOTE.USP.2 ![]() |
The RG MUST support the latest version of Broadband Forum Device:2 [167] data model for USP. |
4.4.4.3 MGMT.REMOTE.WEB – Remote
Management (Web Browser) 
This module applies to IPv6 as well as IPv4, but only if the RG has an IPv6 stack.
4.4.5 MGMT.NTP – Network Time Client 
This module applies to IPv6 as well as IPv4, but only if the RG has an IPv6 stack.
ID | Requirement |
---|---|
MGMT.NTP.1 ![]() |
The RG MUST support an internal clock with a date and time mechanism. |
MGMT.NTP.2 ![]() |
The RG clock MUST be able to be set via an internal time client from an Internet source using RFC 1305 [52]. |
MGMT.NTP.3 ![]() |
The RG MUST support the use of time server identification by both domain name and IP (v4 or v6) address. |
MGMT.NTP.4 ![]() |
If the RG includes default time server values, they SHOULD be specified by domain name and not by IP (v4 or v6) address. |
MGMT.NTP.5 ![]() |
The RG SHOULD allow configuration of the primary and alternate time server values in addition to or in place of any default values. |
MGMT.NTP.6 ![]() |
If the RG includes default time server values or if time server values are identified in documentation, these values SHOULD be selected using industry best practices for NTP and SNTP clients, as published in section 10 of RFC 4330 [106]. |
MGMT.NTP.7 ![]() |
The time client SHOULD support DNS responses with CNAMEs or multiple A or AAAA records. |
MGMT.NTP.8 ![]() |
The default frequency with which the RG updates its time from a time server MUST NOT be less than 60 minutes, or use an operator-specific configuration. |
MGMT.NTP.9 ![]() |
The default frequency with which the RG updates its time from a time server MUST NOT be greater than 24 hours, or use an operator-specific configuration. |
MGMT.NTP.10 ![]() |
The frequency with which the RG updates its time from a time server SHOULD be able to be configured. |
4.4.6 MGMT.TWAMP – Two Way Active
Measurement Protocol 
This module applies to IPv6 as well as IPv4, but only if the RG has an IPv6 stack.
4.4.7 MGMT.DATCOL – Data collection
Requirements 
4.4.7.1 MGMT.DATCOL.WIFIDIAG –
Wi-Fi Diagnostics Data Collection 
For measuring the WiFi experience in the home, these requirements specify which data is continuously collected about the state and performance of the home Wi-Fi network(s).
ID | Requirement |
---|---|
The RG MUST support the collection of these operation parameters for each AP device it controls (integrated or connected in the home network) :
|
|
The RG SHOULD support the collection of these parameters for each AP device it controls (integrated or in home network) :
|
|
The RG MUST support the collection of these operation parameters for each radio per AP device it controls (integrated or connected in the home network) :
The RG SHOULD support the collection of these operation parameters for each radio per AP device it controls (integrated or connected in the home network) :
|
|
The RG MUST support the collection of these neighborhood (channel scan) parameters from each radio per AP device it controls (integrated or connected in the home network):
|
|
The RG SHOULD support the collection of these neighborhood station information from each radio per AP device it controls (integrated or connected in the home network):
|
|
The RG MUST support the collection of these configuration parameters for each AP per radio on all AP devices it controls:
|
|
The RG MUST support the collection of these station parameters for each AP it controls:
|
|
The RG MUST support the collection of these Wi-Fi station parameters per AP for each connected device (STA):
|
|
The RG SHOULD support the collection of these Wi-Fi station parameters per AP for each connected device (STA):
|
|
The RG SHOULD support the collection of these Wi-Fi station statistics for each connected device (STA):
|