As defined in {{bibref|TR-106a1}}. This value MUST remain fixed over the lifetime of the device, including across firmware updates. This value MUST remain fixed over the lifetime of the device, including across firmware updates. This value MUST remain fixed over the lifetime of the device, including across firmware updates. A string identifying the software version currently installed in the CPE. To allow version comparisons, this element SHOULD be in the form of dot-delimited integers, where each successive integer represents a more minor category of variation. For example, ''3.0.21'' where the components mean: ''Major.Minor.Build''. The OptionName of each Option that is currently enabled in the CPE. The OptionName of each is identical to the OptionName element of the OptionStruct described in {{bibref|TR-069a2}}. Only those options are listed whose State indicates the option is enabled. An alternative to this parameter, e.g. when the configuration file is larger than the parameter size limit, is to use the Upload and Download RPCs with a FileType of ''1 Vendor Configuration File''. Enables and disables the CPE's support for CWMP. {{false}} means that CWMP support in the CPE is disabled, in which case the device MUST NOT send any Inform messages to the ACS or accept any Connection Request notifications from the ACS. {{true}} means that CWMP support on the CPE is enabled. The factory default value MUST be {{true}}. The subscriber can re-enable the CPE's CWMP support either by performing a factory reset or by using a LAN-side protocol to change the value of this parameter back to {{true}}. An absolute time reference in UTC to determine when the CPE will initiate the periodic Inform method calls. Each Inform call MUST occur at this reference time plus or minus an integer multiple of the {{param|PeriodicInformInterval}}. {{param}} is used only to set the "phase" of the periodic Informs. The actual value of {{param}} can be arbitrarily far into the past or future. For example, if {{param|PeriodicInformInterval}} is 86400 (a day) and if {{param}} is set to UTC midnight on some day (in the past, present, or future) then periodic Informs will occur every day at UTC midnight. These MUST begin on the very next midnight, even if {{param}} refers to a day in the future. The Unknown Time value defined in {{bibref|TR-098a2|section 2.2}} indicates that no particular time reference is specified. That is, the CPE MAY locally choose the time reference, and needs only to adhere to the specified {{param|PeriodicInformInterval}}. If absolute time is not available to the CPE, its periodic Inform behavior MUST be the same as if the {{param}} parameter was set to the Unknown Time value. Indicates whether or not the ACS will manage upgrades for the CPE. If {{true}}, the CPE SHOULD NOT use other means other than the ACS to seek out available upgrades. If {{false}}, the CPE MAY use other means for this purpose. Note that an autonomous upgrade (reported via an ''10 AUTONOMOUS TRANSFER COMPLETE'' Inform Event code) SHOULD be regarded as a managed upgade if it is performed according to ACS-specified policy. This parameter is used to control throttling of active notifications sent by the CPE to the ACS. It defines the minimum number of seconds that the CPE MUST wait since the end of the last session with the ACS before establishing a new session for the purpose of delivering an active notification. In other words, if CPE needs to establish a new session with the ACS for the sole purpose of delivering an active notification, it MUST delay establishing such a session as needed to ensure that the minimum time since the last session completion has been met. The time is counted since the last successfully completed session, regardless of whether or not it was used for active notifications or other purposes. However, if connection to the ACS is established for purposes other than just delivering active notifications, including for the purpose of retrying a failed session, such connection MUST NOT be delayed based on this parameter value, and the pending active notifications MUST be communicated during that connection. The time of the last session completion does not need to be tracked across reboots. Address and port to which an ACS MAY send a UDP Connection Request to the CPE (see {{bibref|TR-069a2|Annex G}}). This parameter is represented in the form of an Authority element as defined in {{bibref|RFC3986}}. The value MUST be in one of the following two forms: : host:port : host When {{param|STUNEnable}} is {{true}}, the ''host'' and ''port'' portions of this parameter MUST represent the public address and port corresponding to the NAT binding through which the ACS can send UDP Connection Request messages (once this information is learned by the CPE through the use of STUN). When {{param|STUNEnable}} is {{false}}, the ''host'' and ''port'' portions of the URL MUST represent the local IP address and port on which the CPE is listening for UDP Connection Request messages. The second form of this parameter MAY be used only if the port value is equal to "80". Each entry in this table corresponds to a distinct LAN Device that supports Device-Gateway Association according to {{bibref|TR-069a2|Annex F}} as indicated by the presence of the DHCP option specified in that Annex. {{reference|a ''Host'' table row}} This list MUST include an item for each ''Host'' table entry, whether active or inactive, that corresponds to this physical LAN Device. As such entries are added to or removed from the ''Host'' tables, the value of this parameter MUST be updated accordingly. For example: ''InternetGatewayDevice.LANDevice.1.Hosts.Host.1,InternetGatewayDevice.LANDevice.1.Hosts.Host.5'' Enables or disables the NTP or SNTP time client. Status of Time support on the CPE. {{enum}} The {{enum|Unsynchronized}} value indicates that the CPE's absolute time has not yet been set. The {{enum|Synchronized}} value indicates that the CPE has acquired accurate absolute time; its current time is accurate. The {{enum|Error_FailedToSynchronize}} value indicates that the CPE failed to acquire accurate absolute time; its current time is not accurate. The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. The local time zone offset from UTC, ignoring daylight savings time adjustments, in the form: : +hh:mm : -hh:mm For example, this will always be "-08:00" for California, "+00:00" or "-00:00" for the United Kingdom, and "+01:00" for France. This parameter is OBSOLETED because the information that it represents is fully covered by {{param|LocalTimeZoneName}}. The name SHOULD be encoded according to IEEE 1003.1 (POSIX). The following is an example value: ''EST+5EDT,M4.1.0/2,M10.5.0/2'' This parameter is OBSOLETED because the information that it represents is fully covered by {{param|LocalTimeZoneName}}. Current local date and time at which the switch to daylight savings time occurs. If daylight savings time is not used, this value is ignored. This parameter is OBSOLETED because the information that it represents is fully covered by {{param|LocalTimeZoneName}}. Current local date and time at which the switch from daylight savings time will occur. If daylight savings time is not used, this value is ignored. This parameter is OBSOLETED because the information that it represents is fully covered by {{param|LocalTimeZoneName}}. Present only if the CPE provides a password-protected LAN-side user interface. Indicates whether or not the CPE supports a user database that provides per-user passwords that can be used for accessing the local user interface. Present only if the CPE provides a password-protected LAN-side user interface. Indicates whether or not a single shared password MUST protect the local user interface, or whether per-user passwords can be used. If either UserDatabaseSupported or PasswordUserSelectable is {{false}}, the CPE MUST ignore the value of this parameter. Available user-interface languages, where each language is specified according to RFC 3066 {{bibref|RFC3066}}. Current user-interface language, specified according to RFC 3066 {{bibref|RFC3066}}. This object contains parameters relating to the captive portal configuration on the CPE. The captive portal configuration defines the CPE's WAN-destined HTTP (port 80) traffic redirect behavior. When the captive portal is disabled, WAN-destined HTTP (port 80) traffic MUST be permitted to all destinations. When the captive portal is enabled, WAN-destined HTTP (port 80) traffic MUST be permitted only to destinations listed in the {{param|AllowedList}}; traffic to all other destinations MUST be redirected to the {{param|CaptivePortalURL}}. Enables or disables the captive portal. Indicates the status of the captive portal. {{enum}} The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. {{param|CaptivePortalURL}} is {{empty}} IP addresses to which HTTP (port 80) traffic MUST always be permitted, regardless of whether the captive portal is enabled. Each entry in the list MUST be either an IP address or an IP subnet specified using variable length subnet mask (VLSM) syntax. An IP subnet is specified as an IP address followed (with no intervening white space) by "/n", where n is an integer in the range 0-32; this is equivalent to a subnet mask consisting of n 1s followed by 32 minus n 0s. For example, 1.2.3.4 specifies a single IP address, and 1.2.3.4/24 specifies a class C subnet with subnet mask 255.255.255.0. The maximum length of a single entry (plus comma) is 19 characters so 10000 bytes is sufficient for more than 500 IP addresses and/or IP subnets. Captive portal URL to which WAN-destined HTTP (port 80) traffic to destinations not listed in the {{param|AllowedList}} will be redirected. The captive portal URL MUST be an HTTP (not HTTPS) URL. The CPE MUST permit the captive portal URL to be set to {{empty}}, which has the effect of disabling the captive portal (if {{param|Enable}} is {{true}} and the captive portal URL is {{empty}}, {{param|Status}} MUST be {{enum|Error_URLEmpty|Status}}). Specifies the default WAN interface. The content is the full hierarchical parameter name of the default layer 3 connection object. Example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1''. Layer 3 forwarding table. In addition to statically configured routes, this table MUST include dynamic routes learned through layer 3 routing protocols, including RIP, OSPF, DHCP, and IPCP. The CPE MAY reject attempts to delete or modify a dynamic route entry. For each incoming packet, the layer 3 forwarding decision is conceptually made as follows: * Only table entries with a matching {{param|ForwardingPolicy}} are considered, i.e. those that either do not specify a {{param|ForwardingPolicy}}, or else specify a {{param|ForwardingPolicy}} that matches that of the incoming packet. * For the remaining table entries, those for which the source address/mask matches are sorted by longest prefix, i.e. with the most specific networks first (an unspecified source address is a wild-card and always matches, with a prefix length of zero). * For the remaining table entries, those for which the destination address/mask matches are sorted by longest prefix, i.e. with the most specific networks first (an unspecified destination address is a wild-card and always matches, with a prefix length of zero). * The first of the remaining table entries is applied to the packet. If {{true}}, this route is a Static route. IP address of the gateway. Only one of GatewayIPAddress and Interface SHOULD be configured for a route. If both are configured, {{param}} and {{param|Interface}} MUST be consistent with each other. Specifies the egress interface associated with this entry. {{reference|the layer 3 connection object}} Example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1''. Only one of {{param|GatewayIPAddress}} and {{param}} SHOULD be configured for a route. If both are configured, {{param|GatewayIPAddress}} and {{param}} MUST be consistent with each other. For a route that was configured by setting {{param|GatewayIPAddress}} but not {{param}}, read access to {{param}} MUST return the full hierarchical parameter name for the route's egress interface. Layer 2 bridging configuration. Specifies bridges between layer 2 LAN and/or WAN interfaces. Bridges can be defined to include layer 2 filter criteria to selectively bridge traffic between interfaces. This object can be used to configure both 802.1D {{bibref|802.1D-2004}} and 802.1Q {{bibref|802.1Q-2005}} bridges. Not all 802.1D and 802.1Q features are modeled, and some additional features not present in either 802.1D or 802.1Q are modeled. If the Layer2Bridging object is implemented, the view that it provides of the CPE's underlying bridging configuration MUST be consistent with the view provided by any LANDevice and WAN**Connection objects. The implications of this are explained in Annex A.6. The maximum number of 802.1D {{bibref|802.1D-2004}} entries available in the {{object|Bridge}} table. A positive value for this parameter implies support for 802.1D. There is no guarantee that this many 802.1D Bridges can be configured. For example, the CPE might not be able simultaneously to support both 802.1D and 802.1Q Bridges. The maximum number of 802.1Q {{bibref|802.1Q-2005}} entries available in the {{object|Bridge}} table. A positive value for this parameter implies support for 802.1Q. There is no guarantee that this many 802.1Q Bridges can be configured. For example, the CPE might not be able simultaneously to support both 802.1D and 802.1Q Bridges. The maximum number of 802.1Q {{bibref|802.1Q-2005}} VLANs supported per {{object|Bridge}} table entry. Bridge table. Each entry in this table represents a single physical 802.1D {{bibref|802.1D-2004}} or 802.1Q {{bibref|802.1Q-2005}} bridge. If the Bridge Port table is supported, it explicitly defines the Bridge's interfaces. Otherwise, they are implicitly defined via the union of the FilterInterface / MarkingInterface parameters for all the Filter and Marking table entries that are associated with the Bridge. Selects the standard supported by this Bridge table entry. {{bibref|802.1D-2004}} {{bibref|802.1Q-2005}} For an 802.1D {{bibref|802.1D-2004}} Bridge, which has no concept of VLANs, the value of this parameter MUST be 0. For an 802.1Q {{bibref|802.1Q-2005}} Bridge, this is the Bridge's default VLAN ID, i.e. the VLAN ID that applies to Filter table entries with ''VLANIDFilter''=-1. For an 802.1Q Bridge, the value of this parameter MUST NOT be 0. Number of entries in the Bridge {{object|Port}} table. Number of entries in the Bridge {{object|VLAN}} table. Bridge Port table. If this table is supported, it MUST contain an entry for each Bridge Port. Enables or disables this Bridge Port table entry. The interface associated with this Bridge Port table entry. Represents a bridge port as defined in 802.1D {{bibref|802.1D-2004}} and 802.1Q {{bibref|802.1Q-2005}}. To associate this Bridge Port with an interface listed in the ''AvailableInterface'' table, the {{param}} value is set to the value of the corresponding ''AvailableInterfaceKey''. Bridge Port state as defined in 802.1D {{bibref|802.1D-2004}} and 802.1Q {{bibref|802.1Q-2005}}. Default Port VLAN ID as defined in 802.1Q {{bibref|802.1Q-2005}}. For an 802.1D {{bibref|802.1D-2004}} Bridge, this parameter MUST be ignored. Bridge Port acceptable frame types as defined in 802.1Q {{bibref|802.1Q-2005}}. {{enum}} For an 802.1D {{bibref|802.1D-2004}} Bridge, the value of this parameter MUST be {{enum|AdmitAll}}. Enables or disables Ingress Filtering as defined in 802.1Q {{bibref|802.1Q-2005}}. For an 802.1D {{bibref|802.1D-2004}} Bridge, the value of this parameter MUST be {{false}}. Bridge VLAN table. If this table is supported, if MUST contain an entry for each VLAN known to the Bridge. This table only applies to an 802.1Q {{bibref|802.1Q-2005}} Bridge. Enables or disables this VLAN table entry. Human-readable name for this VLAN table entry. VLAN ID of the entry, For both 802.1D {{bibref|802.1D-2004}} and 802.1Q {{bibref|802.1Q-2005}} Bridges, this table is used for the following: # If the Bridge Port table is not supported, it implicitly specifies the Bridge interfaces (in collaboration with the Marking table). # It specifies destination MAC address classification rules. For an 802.1Q Bridge, this table is also used for the following: # For each VLAN ID, it specifies the interfaces that are in the VLAN's Member Set. # If the Bridge Port table is not supported, it specifies the Port VLAN ID (PVID) for each interface. This table also supports several concepts that are not covered by either 802.1D or 802.1Q: # It allows a given packet to be admitted to multiple Bridges. # It supports Ethertype and source MAC address classification rules. If the Bridge Port table is supported, but none of its entries correspond to {{param|FilterInterface}}, or if such an entry exists but is disabled, {{param}} MUST NOT indicate {{enum|Enabled}}. If the Bridge VLAN table is supported, but none of its entries correspond to {{param|VLANIDFilter}}, or if such an entry exists but is disabled, {{param}} MUST NOT indicate {{enum|Enabled}}. Whether or not the Filter definition is exclusive of all others. And if the entry is exclusive, order of precedence. A value of 1 or greater indicates an Exclusive Filter, where the value 1 indicates the first entry to be considered (highest precedence). A value of 0 indicates a Non-Exclusive Filter (OPTIONAL). For each packet, if the packet matches any Exclusive Filters, the packet is assigned to the Bridge associated with the highest precedence Exclusive Filter to which it matches (lowest {{param}} value). If and only if the packet does not match any Exclusive Filters, the packet is assigned to all Bridges associated with each Non-Exclusive Filter for which it matches the defining criteria. If a packet matches no Filter, it is discarded. When the {{param}} is set to match that of an existing Exclusive Filter (1 or greater), the value for the existing entry and all higher numbered entries is incremented (lowered in precedence) to ensure uniqueness of this value. A deletion or change in {{param}} of an Exclusive Filter causes {{param}} values of other Exclusive Filters (values 1 or greater) to be compacted. Note that the use of Exclusive Filters to associate a layer 3 router interface with LAN and/or WAN interfaces via a Bridge entry overrides and updates the association between layer 3 and layer 2 objects implied by the ''InternetGatewayDevice'' object hierarchy. Support for Non-Exclusive Filter entries, i.e. entries with an {{param}} value of 0, is OPTIONAL because 802.1D {{bibref|802.1D-2004}} and 802.1Q {{bibref|802.1Q-2005}} do not consider the case of a packet potentially being admitted to more than one bridge. The interface or interfaces associated with this Filter table entry. The bridge corresponding to this Filter table entry is defined to admit packets on ingress to the bridge from the specified interfaces that meet all of the criteria specified in the Filter table entry. The following values are defined. * To associate this Filter with a single interface listed in the ''AvailableInterface'' table, the {{param}} value is set to the value of the corresponding ''AvailableInterfaceKey''. * ''AllInterfaces'' indicates that this Filter is associated with all LAN and WAN interfaces listed in the ''AvailableInterface'' table (all entries of ''InterfaceType'' ''LANInterface'' or ''WANInterface''). This value is DEPRECATED because of the configuration complexity it requires. * ''LANInterfaces'' indicates that this Filter is associated with all LAN interfaces listed in the ''AvailableInterface'' table (all entries of ''InterfaceType'' ''LANInterface''). This value is DEPRECATED because of the configuration complexity it requires. * ''WANInterfaces'' indicates that this Filter is associated with all WAN interfaces listed in the ''AvailableInterface'' table (all entries of ''InterfaceType'' ''WANInterface''). This value is DEPRECATED because of the configuration complexity it requires. {{empty}} indicates the Filter table entry is not associated with any interface (and has no effect) The 802.1Q {{bibref|802.1Q-2005}} VLAN ID associated with this Filter table entry. A value of -1 indicates that the default VLAN ID for the Bridge MUST be used instead (as specified by {{param|InternetGatewayDevice.Layer2Bridging.Bridge.{i}.VLANID}} for the Bridge table entry associated with this Filter table entry). For an 802.1Q bridge, the value of this parameter MUST NOT be 0, and it is interpreted as follows (more than one condition can apply, e.g. a single Filter table entry might both add an interface to a VLAN's Member Set, and define a classification rule). # If the Bridge Port table is not supported, it is a candidate to be the 802.1Q Port VLAN ID (PVID) for the interface associated with this Filter. Where there is more than one such candidate for a given interface, the PVID MUST be selected according to the {{param|ExclusivityOrder}} precedence rules. # The interface associated with this Filter is added to the VLAN's 802.1Q Member Set. # If a classification parameter, e.g. {{param|DestMACAddressFilterList}}, is specified, a classification rule for this VLAN ID is added. For an 802.1D {{bibref|802.1D-2004}} Bridge, which has no concept of VLANs, the VLAN ID MUST be 0. This is most easily achieved by allowing this parameter to retain its default value of -1 and relying on the fact that the default VLAN ID for an 802.1D bridge will always be 0. 802.1Q {{bibref|802.1Q-2005}} Acceptable Frame Types criterion. This parameter is DEPRECATED, because it only partly models 802.1Q Acceptable Frame Types (and Ingress Filtering). The Bridge Port table SHOULD be used instead and, if supported, MUST take precedence over this parameter. If {{true}}, the Bridge admits only packets tagged with VLAN IDs that include the ingress interface in their 802.1Q Member Sets. If {{false}}, the Bridge admits both packets tagged with VLAN IDs that include the ingress interface in their 802.1Q Member Sets, and any Untagged or PriorityOnly packets. All Untagged or PriorityOnly packets are associated on ingress with the interface's Port VLAN ID (PVID). See the description of {{param|VLANIDFilter}} for an explanation of how the Member Set and PVID are determined. If more than one Filter table entry is associated with a given interface, the value of {{param}} MUST be the same for all such entries. For an 802.1D {{bibref|802.1D-2004}} Bridge, which has no concept of VLANs, the value of this parameter MUST be {{false}}. Classification criterion. {{list|each representing an Ethertype value}} Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on Ethertype. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on Ethertype. Classification criterion. {{list|each representing a MAC Address}} Each list entry MAY optionally specify a bit-mask, where matching of a packet's MAC address is only to be done for bit positions set to one in the mask. If no mask is specified, all bits of the MAC Address are to be used for matching. For example, the list might be: ''01:02:03:04:05:06, 1:22:33:00:00:00/FF:FF:FF:00:00:00, 88:77:66:55:44:33'' Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. Classification criterion. {{list|each representing a MAC Address}} Each list entry MAY optionally specify a bit-mask, where matching of a packet's MAC address is only to be done for bit positions set to one in the mask. If no mask is specified, all bits of the MAC Address are to be used for matching. For example, the list might be: ''01:02:03:04:05:06, 1:22:33:00:00:00/FF:FF:FF:00:00:00, 88:77:66:55:44:33'' Classification criterion. A string used to identify one or more devices via DHCP for which MAC address filtering would subsequently apply. A device is considered matching if its DHCP Vendor Class Identifier (Option 60 as defined in RFC 2132 {{bibref|RFC2132}}) in the most recent DHCP lease acquisition or renewal matches the specified value according to the match criterion in SourceMACFromVendorClassIDMode. Case sensitive. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. {{param|SourceMACFromVendorClassIDFilter}} pattern match criterion. {{enum}} For example, if {{param|SourceMACFromVendorClassIDFilter}} is "Example" then an Option 60 value of "Example device" will match with {{param}} values of {{enum|Prefix}} or {{enum|Substring}}, but not with {{enum|Exact}} or {{enum|Suffix}}. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. Classification criterion. A string used to identify one or more devices via DHCP for which MAC address filtering would subsequently apply. A device is considered matching if its DHCP Vendor Class Identifier (Option 60 as defined in RFC 2132 {{bibref|RFC2132}}) in the most recent DHCP lease acquisition or renewal matches the specified value according to the match criterion in {{param|DestMACFromVendorClassIDMode}}. Case sensitive. {{param|DestMACFromVendorClassIDFilter}} pattern match criterion. {{enum}} For example, if {{param|DestMACFromVendorClassIDFilter}} is ''Example'' then an Option 60 value of "Example device" will match with {{param}} values of {{enum|Prefix}} or {{enum|Substring}}, but not with {{enum|Exact}} or {{enum|Suffix}}. Classification criterion. A string used to identify one or more devices via DHCP for which MAC address filtering would subsequently apply. A device is considered matching if its DHCP Client Identifier (Option 61 as defined in RFC 2132 {{bibref|RFC2132}}) in the most recent DHCP lease acquisition or renewal was equal to the specified value. The option value is binary, so an exact match is REQUIRED. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. Classification criterion. A string used to identify one or more devices via DHCP for which MAC address filtering would subsequently apply. A device is considered matching if its DHCP Client Identifier (Option 61 as defined in RFC 2132 {{bibref|RFC2132}}) in the most recent DHCP lease acquisition or renewal was equal to the specified value. The option value is binary, so an exact match is REQUIRED. Classification criterion. A string used to identify one or more devices via DHCP for which MAC address filtering would subsequently apply. A device is considered matching if its DHCP User Class Identifier (Option 77 as defined in RFC 3004 {{bibref|RFC3004}}) in the most recent DHCP lease acquisition or renewal was equal to the specified value. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. Note that neither 802.1D {{bibref|802.1D-2004}} nor 802.1Q {{bibref|802.1Q-2005}} support classification based on source MAC address. Classification criterion. A string used to identify one or more devices via DHCP for which MAC address filtering would subsequently apply. A device is considered matching if its DHCP User Class Identifier (Option 77 as defined in RFC 3004 {{bibref|RFC3004}}) in the most recent DHCP lease acquisition or renewal was equal to the specified value. Marking table identifying non-default layer 2 marking behavior for packets on egress from the specified interfaces. This table is not relevant to 802.1D {{bibref|802.1D-2004}} Bridges, which are not VLAN-aware. For 802.1Q {{bibref|802.1Q-2005}} Bridges, this table is used for the following: # It specifies whether VLAN tags are to be removed on egress. This table also supports several concepts that are not covered by 802.1Q: # It allows the VLAN ID to be changed on egress. # It allows the Ethernet Priority to be changed on egress. If the Bridge Port table is supported, but none of its entries correspond to {{param|MarkingInterface}}, or if such an entry exists but is disabled, {{param}} MUST NOT indicate {{enum|Enabled}}. The interface or interfaces associated with this Marking table entry for which the specified marking behavior is to apply on egress from the associated bridge. The following values are defined. * To associate this Marking table entry with a single interface listed in the ''AvailableInterface'' table, the {{param}} value is set to the value of the corresponding ''AvailableInterfaceKey''. * ''AllInterfaces'' indicates that this Marking table entry is associated with all LAN and WAN interfaces listed in the ''AvailableInterface'' table (all entries of ''InterfaceType'' ''LANInterface'' or ''WANInterface''). This value is DEPRECATED because of the configuration complexity it requires. * ''LANInterfaces'' indicates that this Marking table entry is associated with all LAN interfaces listed in the ''AvailableInterface'' table (all entries of ''InterfaceType'' ''LANInterface''). This value is DEPRECATED because of the configuration complexity it requires. * ''WANInterfaces'' indicates that this Marking table entry is associated with all WAN interfaces listed in the ''AvailableInterface'' table (all entries of ''InterfaceType'' ''WANInterface''). This value is DEPRECATED because of the configuration complexity it requires. * {{empty}} indicates the Marking table entry table entry is not associated with any interface (and has no effect) If there is more than one enabled Marking table entry that specifies one or more of the same interfaces for the same bridge (identical values of {{param|MarkingBridgeReference}}), then for packets on egress from the specified bridge to those interfaces, the applied marking MUST be that specified in the Marking table entry among those in conflict with the lowest {{param|MarkingKey}} value. If an interface in a given bridge does not have a corresponding Marking table entry, the marking is left unchanged on egress. If {{true}}, on egress to the interfaces associated with this Marking table entry, all packets are sent Untagged. If {{false}}, on egress to the interfaces associated with this Marking table entry, all packets are sent Tagged with the VLAN ID of the VLAN in which the packet is being bridged. The 802.1Q {{bibref|802.1Q-2005}} VLAN ID to be used on egress to the interfaces associated with this Marking table entry. A value of -1 indicates that the VLAN ID of the VLAN in which the packet is being bridged is to be used, i.e. no change. The value of this parameter MUST NOT be 0. If {{param|VLANIDUntag}} is {{true}}, then no VLAN marking is done since the tag containing the VLAN ID is removed. Note that 802.1Q does not support re-marking on egress. If {{false}}, on egress to the interfaces associated with this Marking table entry, the {{param|VLANIDMark}}, if specified, is applied only to PriorityOnly packets. If {{true}}, on egress to the interfaces associated with this Marking table entry, the {{param|VLANIDMark}}, if specified, is to be applied to all packets on this Bridge. If {{param|VLANIDUntag}} is {{true}}, then no VLAN marking is done since the tag containing the VLAN ID is removed. Note that 802.1Q {{bibref|802.1Q-2005}} does not support re-marking on egress. Ethernet priority code (as defined in 802.1D {{bibref|802.1D-2004}}) to mark traffic with that falls into this Bridge on egress to the interfaces associated with this Marking table entry. A value of -1 indicates no change from the incoming packet or the mark assigned by the classifier. Note that 802.1Q {{bibref|802.1Q-2005}} does not support re-marking on egress. If {{false}}, on egress to the interfaces associated with this Marking table entry, the {{param|EthernetPriorityMark}}, if specified, is applied only to packets of priority 0. If {{true}}, on egress to the interfaces associated with this Marking table entry, the {{param|EthernetPriorityMark}}, if specified, is to be applied to all packets on this Bridge. Note that 802.1Q {{bibref|802.1Q-2005}} does not support re-marking on egress. Table containing all LAN and WAN interfaces that are available to be referenced by the Bridge table. Only interfaces that can carry layer 2 bridged traffic are included. {{reference|an available LAN or WAN interface}} This table SHOULD contain a single entry for each available LAN and WAN interface. When such an interface is modeled in more than one place within the data model, the value of this parameter MUST include the full hierarchical parameter names of all of the corresponding objects. For example, if a given Ethernet interface is present within two ''LANDevice'' instances, the value of this parameter might be: ''InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.1, InternetGatewayDevice.LANDevice.2.LANEthernetInterfaceConfig.1'' Note that the remainder of the parameter description does not refer to the possibility that the parameter value is a comma-separated list. Nevertheless, the above requirement does apply. * For a WAN interface, this parameter is the full hierarchical parameter name of a particular ''WANConnectionDevice''. A ''WANConnectionDevice'' is considered available (included in this table) only if it supports layer 2 bridged traffic. That is, this table MUST include only ''WANConnectionDevice''s that contain either a ''WANEthernetLinkConfig'' object, or that contain a ''WANDSLLinkConfig'' object for which the ''LinkType'' is ''EoA''. For example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2'' * For a LAN interface, this parameter is the full hierarchical parameter name of a particular ''LAN**InterfaceConfig'' object, or a ''WLANConfiguration'' object. This table SHOULD include one entry for each such object. For example: ''InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.2'' * For a WAN-side connection to the Gateway's IP router, this parameter is the full hierarchical parameter name of a particular ''WAN**Connection'' service. This table SHOULD include an entry for each layer 3 WAN connection. For example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1'' * For a LAN-side connection to the Gateway's IP router, this parameter is the full hierarchical parameter name of a particular ''LANDevice''. This table SHOULD include an entry for each ''LANDevice'', each of which is associated with a LAN-side layer 3 connection to the Gateway's IP router. For example: ''InternetGatewayDevice.LANDevice.2'' The number of entries in the {{object|QueueStats}} table. Identifier of the traffic class associated with traffic not associated with any specified classifier. A value of -1 indicates a null traffic class. A value of 0xffffffff (-1) indicates a null queue (permitted in data model versions 1.4 and later). The value on creation of a Classification table entry MUST be one greater than the largest current value. Classification criterion. Used to identify one or more LAN devices, value of the DHCP Vendor Class Identifier (Option 60) as defined in RFC 2132 {{bibref|RFC2132}}, matched according to the criterion in {{param|SourceVendorClassIDMode}}. Case sensitive. {{empty}} indicates this criterion is not used for classification. SourceVendorClassID pattern match criterion. {{enum}} For example, if {{param|SourceVendorClassID}} is "Example" then an Option 60 value of "Example device" will match with {{param}} values of {{enum|Prefix}} or {{enum|Substring}}, but not with {{enum|Exact}} or {{enum|Suffix}}. Classification criterion. Used to identify one or more LAN devices, value of the DHCP Vendor Class Identifier (Option 60) as defined in RFC 2132 {{bibref|RFC2132}}, matched according to the criterion in {{param|DestVendorClassIDMode}}. Case sensitive. {{empty}} indicates this criterion is not used for classification. DestVendorClassID pattern match criterion. {{enum}} For example, if {{param|DestVendorClassID}} is "Example" then an Option 60 value of "Example device" will match with {{param}} values of {{enum|Prefix}} or {{enum|Substring}}, but not with {{enum|Exact}} or {{enum|Suffix}}. Classification criterion. Used to identify one or more LAN devices, value of the DHCP Client Identifier (Option 61) as defined in RFC 2132 {{bibref|RFC2132}}. The option value is binary, so an exact match is REQUIRED. {{empty}} indicates this criterion is not used for classification. Classification criterion. Used to identify one or more LAN devices, value of the DHCP Client Identifier (Option 61) as defined in RFC 2132 {{bibref|RFC2132}}. The option value is binary, so an exact match is REQUIRED. {{empty}} indicates this criterion is not used for classification. Classification criterion. Used to identify one or more LAN devices, value of the DHCP User Class Identifier (Option 77) as defined in RFC 3004 {{bibref|RFC3004}}. {{empty}} indicates this criterion is not used for classification. Classification criterion. Used to identify one or more LAN devices, value of the DHCP User Class Identifier (Option 77) as defined in RFC 3004 {{bibref|RFC3004}}. {{empty}} indicates this criterion is not used for classification. Classification criterion. Used to identify one or more LAN devices, value of the DHCP Vendor-specific Information (Option 125) as defined in RFC 3925 {{bibref|RFC3925}}, matched according to the criteria in {{param|SourceVendorSpecificInfoEnterprise}}, {{param|SourceVendorSpecificInfoSubOption}} and {{param|SourceVendorSpecificInfoMode}}. Case sensitive. {{empty}} indicates this criterion is not used for classification. If {{false}}, the class includes only those packets sourced from LAN devices that match the {{param|SourceVendorSpecificInfo}} entry, if specified. If {{true}}, the class includes all packets except those sourced from LAN devices that match the {{param|SourceVendorSpecificInfo}} entry, if specified. {{param|SourceVendorSpecificInfo}} Enterprise Number as defined in RFC 3925 {{bibref|RFC3925}}. The default value (0) is assigned to IANA and will probably need to be replaced with an appropriate enterprise number. {{param|SourceVendorSpecificInfo}} Sub Option Code as defined in RFC 3925 {{bibref|RFC3925}}. {{param|SourceVendorSpecificInfo}} pattern match criterion. Classification criterion. Used to identify one or more LAN devices, value of the DHCP Vendor-specific Information (Option 125) as defined in RFC 3925 {{bibref|RFC3925}}, matched according to the criteria in {{param|DestVendorSpecificInfoEnterprise}}, {{param|DestVendorSpecificInfoSubOption}} and {{param|DestVendorSpecificInfoMode}}. {{empty}} indicates this criterion is not used for classification. If {{false}}, the class includes only those packets destined for LAN devices that match the {{param|DestVendorSpecificInfo}} entry, if specified. If {{true}}, the class includes all packets except those destined for LAN devices that match the {{param|DestVendorSpecificInfo}} entry, if specified. {{param|DestVendorSpecificInfo}} Enterprise Number as defined in RFC 3925 {{bibref|RFC3925}}. The default value (0) is assigned to IANA and will probably need to be replaced with an appropriate enterprise number. {{param|DestVendorSpecificInfo}} Sub Option Code as defined in RFC 3925 {{bibref|RFC3925}}. {{param|DestVendorSpecificInfo}} pattern match criterion. Classification criterion. DiffServ codepoint (defined in RFC 2474 {{bibref|RFC2474}}). If set to a Class Selector Codepoint (defined in RFC 2474), all DSCP values that match the first 3 bits will be considered a valid match. A value of -1 indicates this criterion is not used for classification. Classification criterion. Allows traffic to be distinguished based on out-of-band information such as physical port or application ID. Primarily intended for, but not restricted to, locally sourced traffic. If specified, this entry applies to traffic with matching out-of-band information. A value of -1 indicates this criterion is not used for classification. Classification result. Identifier of the traffic class associated with traffic that falls in this classification. If specified, at least one Queue table entry MUST include this traffic class in its ''TrafficClass'' parameter (which is a comma-separated list). A value of -1 indicates a null traffic class. {{param}}, {{param|ClassQueue}} and {{param|ClassApp}} are mutually exclusive and one of the three MUST be specified. If {{param}} and {{param|ClassQueue}} are null, {{param|ClassApp}} MUST be specified, and vice versa. Classification result. Instance number of the Queue table entry for traffic that falls in this classification. A value of -1 indicates a null queue. {{param|TrafficClass}}, {{param}} and {{param|ClassApp}} are mutually exclusive and one of the three MUST be specified. If {{param|TrafficClass}} and {{param}} are null, {{param|ClassApp}} MUST be specified, and vice versa. Classification result. Instance number of the App table entry for traffic that falls in this classification. A value of -1 indicates a null App table entry. {{param|TrafficClass}}, {{param|ClassQueue}} and {{param}} are mutually exclusive and one of the three MUST be specified. If {{param|TrafficClass}} and {{param|ClassQueue}} are null, {{param}} MUST be specified, and vice versa. Identifier of the traffic class associated with traffic associated with this App table entry, but not associated with any specified flow. A value of -1 indicates a null traffic class. {{param}} and {{param|AppDefaultQueue}} MUST NOT both be specified. {{param|AppDefaultTrafficClass}} and {{param}} MUST NOT both be specified. Identifier of the traffic class associated with this flow. A value of -1 indicates a null traffic class. {{param}} and {{param|FlowQueue}} MUST NOT both be specified. {{param|FlowTrafficClass}} and {{param}} MUST NOT both be specified. Identifies the method of traffic measurement to be used for this policer. {{enum}} {{enum|SimpleTokenBucket}} makes use of {{param|CommittedRate}} and {{param|CommittedBurstSize}}. {{enum|SingleRateThreeColor}} makes use of {{param|CommittedRate}}, {{param|CommittedBurstSize}}, and {{param|ExcessBurstSize}} as defined in RFC 2697 {{bibref|RFC2697}}. {{enum|TwoRateThreeColor}} makes use of {{param|CommittedRate}}, {{param|CommittedBurstSize}}, {{param|PeakRate}}, and {{param|PeakBurstSize}} as defined in RFC 2698 {{bibref|RFC2698}}. Instructions for how to handle traffic that is conforming. {{pattern}} {{pattern|Null}} corresponds with no action. A {{pattern|Count}} action (and only the {{pattern|Count}} action) increases the meter instance count statistics in the {{param|CountedPackets}} and {{param|CountedBytes}} parameters. {{pattern|Count}} actions are DEPRECATED because they can not be combined with other actions, e.g. marking actions. ''<DSCP Value>'' is an unsigned integer that corresponds with a mark action overwriting the traffic's DSCP with the configured DSCP. ''<:Ethernet Priority>'' is a colon (":") followed by an unsigned integer (no white space). It corresponds with a mark action overwriting the traffic's Ethernet Priority with the configured Ethernet Priority. ''<DSCP Value:Ethernet Priority>'' is an unsigned integer followed by a colon (":") and a second unsigned integer (no white space). It corresponds with a mark action overwriting the traffic's DSCP and Ethernet Priority with the configured values. For example, "24" specifies a DSCP value of 24, ":3" specifies an Ethernet Priority of 3, and "24:3" specifies both. <DSCP Value> <Ethernet Priority> <DSCP Value:Ethernet Priority> Instructions for how to handle traffic that is partially conforming (colored yellow). {{pattern}} {{pattern|Null}} corresponds with no action. A {{pattern|Count}} action (and only the {{pattern|Count}} action) increases the meter instance count statistics in the {{param|CountedPackets}} and {{param|CountedBytes}} parameters. {{pattern|Count}} actions are DEPRECATED because they can not be combined with other actions, e.g. marking actions. ''<DSCP Value>'' is an unsigned integer that corresponds with a mark action overwriting the traffic's DSCP with the configured DSCP.Only applies for three-color meters. ''<:Ethernet Priority>'' is a colon (":") followed by an unsigned integer (no white space). It corresponds with a mark action overwriting the traffic's Ethernet Priority with the configured Ethernet Priority. ''<DSCP Value:Ethernet Priority>'' is an unsigned integer followed by a colon (":") and a second unsigned integer (no white space). It corresponds with a mark action overwriting the traffic's DSCP and Ethernet Priority with the configured values. For example, "24" specifies a DSCP value of 24, ":3" specifies an Ethernet Priority of 3, and "24:3" specifies both. <DSCP Value> <Ethernet Priority> <DSCP Value:Ethernet Priority> Instructions for how to handle traffic that is non-conforming. {{pattern}} {{pattern|Null}} corresponds with no action. A {{pattern|Count}} action (and only the {{pattern|Count}} action) increases the meter instance count statistics in the {{param|CountedPackets}} and {{param|CountedBytes}} parameters. {{pattern|Count}} actions are DEPRECATED because they can not be combined with other actions, e.g. marking actions. ''<DSCP Value>'' is an unsigned integer that corresponds with a mark action overwriting the traffic's DSCP with the configured DSCP. ''<:Ethernet Priority>'' is a colon (":") followed by an unsigned integer (no white space). It corresponds with a mark action overwriting the traffic's Ethernet Priority with the configured Ethernet Priority. ''<DSCP Value:Ethernet Priority>'' is an unsigned integer followed by a colon (":") and a second unsigned integer (no white space). It corresponds with a mark action overwriting the traffic's DSCP and Ethernet Priority with the configured values. For example, "24" specifies a DSCP value of 24, ":3" specifies an Ethernet Priority of 3, and "24:3" specifies both. <DSCP Value> <Ethernet Priority> <DSCP Value:Ethernet Priority> Number of Packets counted as result of a ''Count'' meter action. This parameter is DEPRECATED because the ''Count'' meter action is DEPRECATED. Number of Bytes counted as result of a ''Count'' meter action. This parameter is DEPRECATED because the ''Count'' meter action is DEPRECATED. Total number of Packets counted by this policer, regardless of meter action. Total number of Bytes counted by this policer, regardless of meter action. Number of conforming Packets counted by this policer, regardless of meter action. Number of conforming Bytes counted by this policer, regardless of meter action. Number of partially conforming Packets counted by this policer, regardless of meter action. Number of partially conforming Bytes counted by this policer, regardless of meter action. Number of non-conforming Packets counted by this policer, regardless of meter action. Number of non-conforming Bytes counted by this policer, regardless of meter action. Identifies the set of traffic classes associated with this queue. If this list is empty then traffic can be sent to this queue only as a result of a direct reference from a Classification, App or Flow table entry, e.g. via the Classification table's ''ClassQueue'' parameter. If this list is non-empty then traffic can additionally be sent to this queue if a Classification, App or Flow table entry specifies a traffic class, e.g. via the Classification table's ''TrafficClass'' parameter. If more than one queue on a given egress interface is associated with a given traffic class, the implementation will choose which queue to send traffic of this class to. Rate to shape this queue's traffic to. For leaky bucket (constant rate shaping), this is the constant rate. For token bucket (variable rate shaping), this is the average rate. If <= 100, in percent of the rate of the highest rate-constrained layer over which the packet will travel on egress. If > 100, in bits per second. A value of -1 indicates no shaping. For example, for packets destined for a WAN DSL interface, if the egress will be on a PPP or IP link with a specified ''ShapingRate'', the percentage is calculated relative to this rate. Otherwise, if the ATM layer is rate-constrained, then the rate is calculated relative to this rate. Otherwise, the rate is calculated relative to the physical-layer DSL rate. Queue statistics table. This table is managed by the ACS, which will create entries only for those {Queue, Interface} combinations for which statistics are to be collected. Enables or disables this object. The status of this object. Enabled and {Queue,Interface} is valid Enabled but {Queue,Interface} is invalid Instance number of the Queue table entry with which this object is associated. Egress interface for which this object contains statistics. This parameter MUST be the full hierarchical parameter name of the particular ''WANDevice'', ''WANConnectionDevice'', ''WAN**Connection'', ''LANDevice'', ''LAN**InterfaceConfig'', or ''WLANConfiguration'' object. Number of packets output through the queue. Number of bytes output through the queue. Number of packets dropped by the queue. Number of bytes dropped by the queue. Queue occupancy in packets (gives a measure of queue latency). Queue occupancy as a percentage, i.e. 100 * queue occupancy in bytes / queue size in bytes (gives a measure of queue usage). A password to allow LAN access to protected auto-configuration services. If the CPE supports TR-064 (LAN-side DSL CPE Configuration Protocol), this parameter is to be used as the ''dslf-config'' password (as defined in TR-064). If the CPE has a user interface with password protection enabled, this parameter is also to be used as the user password for password-protected operations. However, this parameter MUST NOT be used to set the user password if the parameter {{param|InternetGatewayDevice.UserInterface.PasswordUserSelectable}} is {{true}}. {{reference|the WAN or LAN IP-layer interface over which the test is to be performed}} This identifies the source IP address to use when performing the test. The following is a WAN interface example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1'' The following is a LAN interface example: ''InternetGatewayDevice.LANDevice.1.LANHostConfigManagement.IPInterface.1'' The value of this parameter MUST be either a valid interface or {{empty}}. An attempt to set this parameter to a different value MUST be rejected as an invalid parameter value. If {{empty}} is specified, the CPE MUST use the interface as directed by its routing policy (Forwarding table entries) to determine the appropriate interface. This object is defines access to an IP-layer trace-route test for the specified IP interface. Indicates availability of diagnostic data. {{enum}} If the ACS sets the value of this parameter to {{enum|Requested}}, the CPE MUST initiate the corresponding diagnostic test. When writing, the only allowed value is {{enum|Requested}}. To ensure the use of the proper test parameters (the writable parameters in this object), the test parameters MUST be set either prior to or at the same time as (in the same SetParameterValues) setting the {{param}} to {{enum|Requested}}. When requested, the CPE SHOULD wait until after completion of the communication session with the ACS before starting the diagnostic. When the diagnostic initiated by the ACS is completed (successfully or not), the CPE MUST establish a new connection to the ACS to allow the ACS to view the results, indicating the Event code ''8 DIAGNOSTICS COMPLETE'' in the Inform message. {{reference|the WAN or LAN IP-layer interface over which the test is to be performed}} This identifies the source IP address to use when performing the test. The following is a WAN interface example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1'' The following is a LAN interface example: ''InternetGatewayDevice.LANDevice.1.LANHostConfigManagement.IPInterface.1'' Host name or address of the host to find a route to Number of tries per hop. Set prior to running Diagnostic. By default, the CPE SHOULD set this value to 3. Timeout in milliseconds for the trace route test. By default the CPE SHOULD set this value to 5000. Size of the data block in bytes to be sent for each trace route. By default, the CPE SHOULD set this value to 38. DiffServ codepoint to be used for the test packets. By default the CPE SHOULD set this value to 0. The maximum number of hop used in outgoing probe packets (max TTL). By default the CPE SHOULD set this value to 30. Result parameter indicating the response time in milliseconds the most recent trace route test. If a route could not be determined, this value MUST be zero. Number of entries in the {{object|RouteHops}} table. Contains the array of results returned. If a route could not be determined, this array will be empty Result parameter indicating the Host Name if DNS is able to resolve or IP Address of a hop along the discovered route. If this parameter is not {{empty}} it will contain the last IP address of the host returned for this hop and the {{param|HopHost}} will contain the Host Name returned from the reverse DNS query. Contains the error code returned for this hop This code is directly from the ICMP CODE field. Contains one or more round trip times in milliseconds (one for each repetition) for this hop. The URL, as defined in {{bibref|RFC3986}}, for the CPE to perform the download on. This parameter MUST be in the form of a valid HTTP {{bibref|RFC2616}} or FTP {{bibref|RFC862}} URL. When using FTP transport, FTP binary transfer MUST be used. When using HTTP transport, persistent connections MUST be used and pipelining MUST NOT be used. When using HTTP transport the HTTP Authentication MUST NOT be used. This object defines the diagnostics configuration for a HTTP or FTP UploadDiagnostics test. Files sent by the UploadDiagnostics do not require file storage on the CPE device, and MAY be an arbitrary stream of bytes. The URL, as defined in {{bibref|RFC3986}}, for the CPE to Upload to. This parameter MUST be in the form of a valid HTTP {{bibref|RFC2616}} or FTP {{bibref|RFC862}} URL. When using FTP transport, FTP binary transfer MUST be used. When using HTTP transport, persistent connections MUST be used and pipelining MUST NOT be used. When using HTTP transport the HTTP Authentication MUST NOT be used. Each instance models a LAN side layer 3 IP interface. Each instance has children that correspond to the layer 2 interfaces that are connected to the Gateway's IP router via the modeled IP interface. If a LANDevice instance is deleted, the objects modeling those layer 2 interfaces that are as a result no longer connected to the Gateway's IP router will move to the InternetGatewayDevice.LANInterfaces object. If the ''Layer2Bridging'' object is implemented, the view that it provides of the CPE's underlying bridging configuration MUST be consistent with the view provided by any ''LANDevice'' and ''WAN**Connection'' objects. The implications of this are explained in {{bibref|TR-098a2|Annex A.6}}. The DHCP parameters in this object define the behavior of the default DHCP server, i.e. the behavior for DHCP requests that do not match any of the DHCP conditional serving pool entries. The MAC address associated with the IP interface modeled by this LANDevice instance. This is the MAC address that is returned in response to an ARP request for any of the IP interface's IP addresses. It is also the source MAC address in all IP traffic sent over the IP interface. If no single MAC address meets the above criteria, the value of this parameter MUST be the all-zero MAC address ''00:00:00:00:00:00''. Indicates if the DHCP server performs the role of a server ({{false}}) or a relay ({{true}}) on the LAN interface. This parameter is DEPRECATED because the functionality that it describes is not well-defined. The CPE MAY set it to the value that it thinks most appropriate, based on its configuration. This parameter MUST have a valid value before the DHCP server can be enabled. This parameter MUST have a valid value before the DHCP server can be enabled. Addresses marked reserved from the address allocation pool. This parameter MUST have a valid value before the DHCP server can be enabled. Controls use of addresses from the associated WAN connection. {{enum}} If {{enum|Normal}}, the address pool is directly configured by the ACS. If {{enum|UseAllocatedSubnet}}, behavior is the same as for {{enum|Passthrough}} with an empty {{param|PassthroughMACAddress}}. For this reason, {{enum|UseAllocatedSubnet}} is DEPRECATED. If {{enum|Passthrough}}, and {{param|PassthroughMACAddress}} is {{empty}}, the configured values of the {{param|MinAddress}}, {{param|MaxAddress}}, {{param|SubnetMask}} and {{param|DNSServers}} parameters are ignored. The corresponding address pool values are instead taken from the WAN connection specified by {{param|AssociatedConnection}}. If {{enum|Passthrough}}, and {{param|PassthroughMACAddress}} is not {{empty}}, the LAN Host identified by {{param|PassthroughMACAddress}} is given a WAN IP address from the WAN connection specified by {{param|AssociatedConnection}}. Other LAN Hosts are treated as for {{enum|Normal}}. Use of {{param|PassthroughMACAddress}} does not cover the case where more than one LAN Host is to be given a WAN IP address. This can be achieved by using a DHCP conditional serving pool. {{reference|the connection instance to be used for address allocation if {{param|UseAllocatedWAN}} is set to {{enum|UseAllocatedSubnet|UseAllocatedWAN}} or {{enum|Passthrough|UseAllocatedWAN}}}} The content is the full hierarchical parameter name of a WAN-side layer 3 connection object. Example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1''. If {{param|UseAllocatedWAN}} is {{enum|UseAllocatedSubnet|UseAllocatedWAN}} or {{enum|Passthrough|UseAllocatedWAN}}, this parameter MUST have a valid value before the DHCP server can be enabled. DHCP lease time in seconds given to the LAN Host that is used to passthrough a WAN IP address if {{param|UseAllocatedWAN}} is {{enum|Passthrough|UseAllocatedWAN}}. Note: A temporary private IP address with short lease (for example, 1 min) might be given to the passthrough LAN Host before the WAN IP address is acquired. Hardware address of the LAN Host that is used to passthrough a WAN IP address if {{param|UseAllocatedWAN}} is {{enum|Passthrough|UseAllocatedWAN}}. Note: {{empty}} indicates that no specific LAN Host is designated, and results in the same behavior as the (DEPRECATED) {{enum|UseAllocatedSubnet|UseAllocatedWAN}}. The number of entries in the {{object|IPInterface}} table. The number of entries in the {{object|DHCPStaticAddress}} table. The number of entries in the {{object|DHCPOption}} table. The number of entries in the {{object|DHCPConditionalServingPool}} table. IP address table with each object representing an IP address on the LANDevice IP interface. Support for more than one interface instance is OPTIONAL. DHCP static address table. Entries in this table correspond to what RFC 2131 {{bibref|RFC2131}} calls "manual allocation", where a client's IP address is assigned by the network administrator, and DHCP is used simply to convey the assigned address to the client. Each instance of this object specifies a hardware address (MAC address) and an IP address within the pool. When serving from this pool, this IP address MUST, if available, be assigned to the DHCP client with this hardware address, and MUST NOT be assigned to any other client. Note that it is possible that an IP address in this table is present in one or more of the conditional serving pools, in which case it is possible that such an address will be assigned to a different client. Enables or disables the DHCPStaticAddress table entry. Disabling an entry does not return the IP address to the pool. Hardware address (MAC address) of the physical interface of the DHCP client. This parameter MUST have a valid value before the table entry can be enabled. IP address to be assigned by the DHCP server to the DHCP client with the specified hardware address (MAC address). This parameter MUST have a valid value before the table entry can be enabled. This object specifies the DHCP options that MUST, if enabled, be returned to clients whose DHCP requests do not match any of the DHCP conditional serving pool entries. Enables or disables this DHCPOption table entry. Option tag as defined in RFC 2132 {{bibref|RFC2132}}. Base64 encoded option value. DHCP conditional serving pool table. Each instance of this object defines a DHCP conditional serving pool. Client requests are associated with pools based on criteria such as source interface, supplied DHCP options, and MAC address. If a DHCP request does not match any of the DHCP conditional serving pool entries, the handling of the request is determined by the default DHCP server behavior that is defined by the LANHostConfigManagement object. Overlapping pool ranges MUST be supported. Enables or disables the DHCPConditionalServingPool entry. Position of the pool entry in the order of precedence. A value of 1 indicates the first entry considered. For each DHCP request, the highest ordered entry that matches the association criteria is applied. All lower order entries are ignored. When this value is modified, if the value matches that of an existing entry, the Order value for the existing entry and all lower Order entries is incremented (lowered in precedence) to ensure uniqueness of this value. A deletion causes Order values to be compacted. When a value is changed, incrementing occurs before compaction. The value on creation of a DHCPConditionalServingPool table entry MUST be one greater than the largest current value. Pool association criterion. {{list}} {{reference|the layer 2 ingress interfaces associated with this entry, i.e. the corresponding ''LAN**InterfaceConfig'' or ''WLANConfiguration'' objects}} For example: ''InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.2,InternetGatewayDevice.LANDevice.1.WLANConfiguration.3'' {{empty}} indicates this entry is to apply to all layer 2 interface objects under this ''LANDevice'' instance. Pool association criterion. Used to identify one or more LAN devices, value of the DHCP Vendor Class Identifier (Option 60) as defined in RFC 2132 {{bibref|RFC2132}}, matched according to the criterion in {{param|VendorClassIDMode}}. Case sensitive. {{empty}} indicates this criterion is not used for conditional serving. If {{false}}, matching packets are those that match the {{param|VendorClassID}} entry, if specified. If {{true}}, matching packets are those that do not match the {{param|VendorClassID}} entry, if specified. {{param|VendorClassID}} pattern match criterion. {{enum}} For example, if {{param|VendorClassID}} is "Example" then an Option 60 value of "Example device" will match with {{param}} values of {{enum|Prefix}} or {{enum|Substring}}, but not with {{enum|Exact}} or {{enum|Suffix}}. Pool association criterion. Used to identify one or more LAN devices, value of the DHCP Client Identifier (Option 61) as defined in RFC 2132 {{bibref|RFC2132}}. The option value is binary, so an exact match is REQUIRED. {{empty}} indicates this criterion is not used for conditional serving. If {{false}}, matching packets are those that match the {{param|ClientID}} entry, if specified. If {{true}}, matching packets are those that do not match the {{param|ClientID}} entry, if specified. Pool association criterion. Used to identify one or more LAN devices, value of the DHCP User Class Identifier (Option 77) as defined in RFC 3004 {{bibref|RFC3004}}. {{empty}} indicates this criterion is not used for conditional serving. If {{false}}, matching packets are those that match the {{param|UserClassID}} entry, if specified. If {{true}}, matching packets are those that do not match the {{param|UserClassID}} entry, if specified. Pool association criterion. Hardware address (MAC address.) of the physical interface of the DHCP client. {{empty}} indicates this criterion is not used for conditional serving. Bit-mask for the MAC address, where matching of a packet's MAC address with the {{param|Chaddr}} is only to be done for bit positions set to one in the mask. A mask of FF:FF:FF:FF:FF:FF or {{empty}} indicates all bits of the {{param|Chaddr}} are to be used for conditional serving classification. If {{false}}, matching packets are those that match the (masked) {{param|Chaddr}} entry, if specified. If {{true}}, matching packets are those that do not match the (masked) {{param|Chaddr}} entry, if specified. If {{true}}, then the local DHCP server will assign an IP address from the specific address pool specified in this object. If {{false}}, the DHCP server will send the request to the {{param|DHCPServerIPAddress}} configured for this pool. Specifies first address in the pool to be assigned by the DHCP server on the LAN interface. This parameter is configurable only if {{param|UseAllocatedWAN}} is {{enum|Normal|UseAllocatedWAN}}. This parameter MUST have a valid value before this pool can be enabled. Specifies last address in the pool to be assigned by the DHCP server on the LAN interface. This parameter is configurable only if {{param|UseAllocatedWAN}} is {{enum|Normal|UseAllocatedWAN}}. This parameter MUST have a valid value before this pool can be enabled. IP addresses marked reserved from the address allocation pool. Specifies the client's network subnet mask. This parameter is configurable only if {{param|UseAllocatedWAN}} is {{enum|Normal|UseAllocatedWAN}}. This parameter MUST have a valid value before this pool can be enabled. DNS servers offered to DHCP clients. Support for more than three DNS Servers is OPTIONAL. This parameter is configurable only if {{param|UseAllocatedWAN}} is {{enum|Normal|UseAllocatedWAN}}. Sets the domain name to provide to clients on the LAN interface. IP addresses of routers on this subnet. Also known as default gateway. Support for more than one Router address is OPTIONAL. Specifies the lease time in seconds of client assigned addresses. A value of -1 indicates an infinite lease. Controls whether the {{param|MinAddress}}, {{param|MaxAddress}}, {{param|SubnetMask}} and {{param|DNSServers}} parameters are configurable or are taken from the associated WAN connection. {{enum}} If {{enum|Normal}}, the above-mentioned pool parameters are directly configured by the ACS. If {{enum|Passthrough}}, the above-mentioned pool parameters cannot be configured by the ACS. Their values are instead taken from the WAN connection specified by {{param|AssociatedConnection}}. {{reference|the connection instance to be used for address allocation if {{param|UseAllocatedWAN}} is set to {{enum|Passthrough|UseAllocatedWAN}}}} The content is the full hierarchical parameter name of a WAN-side layer 3 connection object. Example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1''. If {{param|UseAllocatedWAN}} is {{enum|Passthrough|UseAllocatedWAN}}, this parameter MUST have a valid value before this pool can be enabled. IP address of the DHCP server, where the request has to be sent to when there is a conditional match with this pool and {{param|LocallyServed}} is {{false}}. If this parameter is not configured, then the DHCP request is dropped. The number of entries in the {{object|DHCPStaticAddress}} table. The number of entries in the {{object|DHCPOption}} table. DHCP static address table. Entries in this table correspond to what RFC 2131 {{bibref|RFC2131}} calls "manual allocation", where a client's IP address is assigned by the network administrator, and DHCP is used simply to convey the assigned address to the client. Each instance of this object specifies a hardware address (MAC address) and an IP address within the pool. When serving from this pool, this IP address MUST, if available, be assigned to the DHCP client with this hardware address, and MUST NOT be assigned to any other client. Note that it is possible that an IP address in this table is present in the main pool and/or one or more of the other conditional serving pools, in which case it is possible that such an address will be assigned to a different client. Enables or disables the DHCPStaticAddress table entry. Disabling an entry does not return the IP address to the pool. Hardware address (MAC address) of the physical interface of the DHCP client. This parameter MUST have a valid value before the table entry can be enabled. IP address to be assigned by the DHCP server to the DHCP client with the specified hardware address (MAC address). This parameter MUST have a valid value before the table entry can be enabled. This object specifies the DHCP options that MUST, if enabled, be returned to clients whose DHCP requests are associated with this pool. Enables or disables this DHCPOption table entry. Option tag as defined in RFC 2132 {{bibref|RFC2132}}. Base64 encoded option value. The name of this layer 2 interface, chosen by the vendor, e.g. "eth0" or "eth0:1". Note that these statistics refer to the link layer, not to the physical layer. The total number of bytes transmitted out of the interface, including framing characters. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of bytes received on the interface, including framing characters. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets transmitted out of the interface. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets which were received on this interface. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets that could not be transmitted because of errors. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets that contained errors preventing them from being deliverable. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were not addressed to a multicast or broadcast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were not addressed to a multicast or broadcast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were addressed to a multicast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a multicast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were addressed to a broadcast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a broadcast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets received via the interface which were discarded because of an unknown or unsupported protocol. The value of this counter MAY be reset to zero when the CPE is rebooted. The name of this layer 2 interface, chosen by the vendor, e.g. "usb0". Note that these statistics refer to the link layer, not to the physical layer. The total number of bytes transmitted out of the interface, including framing characters. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of bytes received on the interface, including framing characters. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets (cells) transmitted out of the interface. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets (cells) which were received on this interface. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets that could not be transmitted because of errors. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets that contained errors preventing them from being deliverable. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were not addressed to a multicast or broadcast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were not addressed to a multicast or broadcast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were addressed to a multicast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a multicast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were addressed to a broadcast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a broadcast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets received via the interface which were discarded because of an unknown or unsupported protocol. The value of this counter MAY be reset to zero when the CPE is rebooted. The name of this layer 2 interface, chosen by the vendor, e.g. "wlan0". The current radio channel used by the connection. To request automatic channel selection, set {{param|AutoChannelEnable}} to {{true}}. Whenever {{param|AutoChannelEnable}} is {{true}}, the value of the {{param}} parameter MUST be the channel selected by the automatic channel selection procedure. Enable or disable automatic channel selection. Set to {{false}} to disable the automatic channel selection procedure, in which case the currently selected channel remains selected. Set to {{true}} to enable the automatic channel selection procedure. This procedure MUST automatically select the channel, and MAY also change it subsequently. {{param}} MUST automatically change to {{false}} whenever the channel is manually selected, i.e. whenever the {{param|Channel}} parameter is written. Whenever {{param}} is {{true}}, the value of the {{param|Channel}} parameter MUST be the channel selected by the automatic channel selection procedure. The capabilities that are currently enabled on the access point (and that are announced via beacons if {{param|BeaconAdvertisementEnabled}} is {{true}}). Write access to this parameter enables and disables such capabilities. An attempt to set this parameter to one of the REQUIRED (mandatory) values MAY be rejected if (and only if) the requested capability is not available on this WLANConfiguration instance but is available on another WLANConfiguration instance within this Internet Gateway Device. For example, only basic 802.11 might be supported by one virtual AP, and only WPA might be supported by another virtual AP. A value of {{enum|None}} means that no capabilities are currently enabled on the access point and that no stations will be able to associate with it. {{enum}} {{enum|11i}} SHOULD be taken to refer to both the 802.11i specification and to the WPA2 specification (any WPA2-certified device will implement all mandatory parts of the 802.11i standard). The OBSOLETED values are those for Basic + WPA/WPA2 mixed modes, which are not permitted by the WPA specifications. b and g clients supported only g clients supported Indicates whether or not beacons include the SSID name. This parameter has an effect only if {{param|BeaconAdvertisementEnabled}} is {{true}}. Supported transmit power levels as percentages of full power. For example, "0,25,50,75,100". Indicates the current transmit power level as a percentage of full power. The value MUST be one of the values reported by the {{param|TransmitPowerSupported}} parameter. The current access-point operating mode. The OPTIONAL modes permit the AP to be configured as a wireless bridge (to bridge two wired networks), repeater (a bridge that also serves wireless clients), or wireless station. Ad hoc stations are not supported. Indicates whether this interface supports WiFi Multimedia (WMM) Access Categories (AC). Indicates whether this interface supports WMM Unscheduled Automatic Power Save Delivery (U-APSD). Note: U-APSD support implies WMM support. Whether WMM support is currently enabled. When enabled, this is indicated in beacon frames Whether U-APSD support is currently enabled. When enabled, this is indicated in beacon frames. Note: U-APSD can only be enabled if WMM is also enabled. The total number of bytes transmitted out of the interface, including framing characters. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of bytes received on the interface, including framing characters. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets transmitted out of the interface. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets which were received on this interface. The value of this counter MAY be reset to zero when the CPE is rebooted. The number of devices currently associated with the access point. This corresponds to the number of entries in the AssociatedDevice table. This object contains statistics for an 802.11 LAN interface on a CPE device. Note that these statistics refer to the link layer, not to the physical layer. Note that this object does not include the total byte and packet statistics, which are, for historical reasons, in the parent object. The total number of outbound packets that could not be transmitted because of errors. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets that contained errors preventing them from being deliverable. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were not addressed to a multicast or broadcast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were not addressed to a multicast or broadcast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were addressed to a multicast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a multicast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were addressed to a broadcast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a broadcast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets received via the interface which were discarded because of an unknown or unsupported protocol. The value of this counter MAY be reset to zero when the CPE is rebooted. This object contains parameters related to WPS (Wi-Fi Protected Setup) {{bibref|WPSv1.0}} that apply to a CPE acting as an Access Point. Enables or disables WPS functionality for this interface. User-friendly description of the device. This parameter corresponds directly to the "Device Name" attribute of the WPS specification {{bibref|WPSv1.0}}. Represents the DevicePassword used (commonly known as PIN). This parameter corresponds directly to the "Device Password" attribute of the WPS specification {{bibref|WPSv1.0}}. UUID of the device. This is represented as specified in RFC 4122 {{bibref|RFC4122}} but omitting the leading "urn:uuid:", e.g. "f81d4fae-7dec-11d0-a765-00a0c91e6bf6". This parameter corresponds directly to the "UUID-E" (enrollee) and "UUID-R" (registrar) attributes of the WPS specification {{bibref|WPSv1.0}}. Note that if the Access Point can act both as an enrollee and as a registrar then UUID-E and UUID-R will be the same as each other. The Wi-Fi Protected Setup version supported by the device. This parameter corresponds directly to the "Version" attribute of the WPS specification {{bibref|WPSv1.0}}. WPS configuration methods supported by the device. {{enum}} This parameter corresponds directly to the "Config Methods" attribute of the WPS specification {{bibref|WPSv1.0}}. WPS configuration methods enabled on the device. This parameter corresponds directly to the "Permitted Config Methods" attribute of the WPS specification {{bibref|WPSv1.0}}. Indicates if the AP Setup mode is enabled for configuration of the AP through an external registrar. The AP Setup mode can be disabled by the user, by the remote management or in case of a brute force attack against the AP's PIN (Wrong PIN provided to AP multiple times). {{enum}} This parameter corresponds directly to the "AP Setup Locked" attribute of the WPS specification {{bibref|WPSv1.0}}. The factory default setting is {{enum|Unlocked}}. When set to {{true}}, the Access Point will refuse to accept new external registrars; already established registrars will continue to be able to add new enrollees (the {{param|SetupLockedState}} becomes {{enum|LockedByRemoteManagement|SetupLockedState}}). When set to {{false}}, the Access Point is enabled for configuration through an external registrar (the {{param|SetupLockedState}} becomes {{enum|Unlocked|SetupLockedState}}). The factory default setting is {{false}}. Description of the WPS status on the Wireless Access Point side. {{enum}} This parameter corresponds directly to the "Wi-Fi Protected Setup State" attribute of the WPS specification {{bibref|WPSv1.0}}. WLAN interface is unconfigured: out-of-the box configuration WLAN interface is configured Shows the result of the last external registrar attempt to configure the Access Point. {{enum}} If no external registrar has yet attempted to configure the Access Point, this parameter MUST have the value {{enum|NoError}}. The value of this parameter MUST persist across CPE reboots. This parameter corresponds directly to the "Configuration Error" attribute of the WPS specification {{bibref|WPSv1.0}}. Number of entries in the Registrar table: number of Registrars that currently have an association with the Access Point. This parameter corresponds directly to the "Registrar Current" attribute of the WPS specification {{bibref|WPSv1.0}}. {{true}} if the Access Point has ever previously created an association with a Registrar. This parameter corresponds directly to the "Registrar Established" attribute of the WPS specification {{bibref|WPSv1.0}}. The factory default setting is {{false}}. This table lists the Registrars associated with the Access Point. This table MUST persist across CPE reboots. The registrar UUID is the unique key. This object corresponds directly to the "Registrar List" attribute of the WPS specification {{bibref|WPSv1.0}}. If {{true}}, the registrar can be used by the Access Point for WPS procedures. UUID of the registrar. This is represented as specified in RFC 4122 {{bibref|RFC4122}} but omitting the leading "urn:uuid:", e.g. ''f81d4fae-7dec-11d0-a765-00a0c91e6bf6''. This parameter corresponds directly to the "UUID-R" attribute of the WPS specification {{bibref|WPSv1.0}}. Device Name of the registrar. This parameter corresponds directly to the "Device Name" attribute of the WPS specification {{bibref|WPSv1.0}}. The data transmit rate that was most recently used for a station with a specified MAC address. A passphrase from which the PSK is to be generated. The first table entry is the same as the parameter {{param|InternetGatewayDevice.LANDevice.{i}.WLANConfiguration.{i}.KeyPassphrase}} for the same instance of WLANConfiguration. When either parameter is changed, the value of the other is changed as well. If {{param}} is written, the PSK is immediately generated. The ACS SHOULD NOT set the passphrase and also set the PSK directly (the result of doing this is undefined). The key is generated as specified by WPA, which uses PBKDF2 from PKCS #5: Password-based Cryptography Specification Version 2.0 (RFC 2898 {{bibref|RFC2898}}). This is a table of WMM parameters for traffic that originates at the wireless access point, i.e. for outgoing traffic. The size of this table is fixed, with 4 entries (with instance numbers 1 through 4). Instance numbers MUST be assigned as follows: # BE AC (Best Effort) # BK AC (Background) # VI AC (Video) # VO AC (Voice) Arbitration Inter Frame Spacing (Number). This is the number of time slots in the arbitration interframe space. Exponent of Contention Window (Minimum). This encodes the Values of CWMin as an exponent: CWMin = 2^ECWMin - 1. For example, if ECWMin is 8, then CWMin is 2^8 - 1, or 255, Exponent of Contention Window (Maximum). This encodes the Values of CWMax as an exponent: CWMax = 2^ECWMax - 1. For example, if ECWMax is 8, then CWMax is 2^8 - 1, or 255, Transmit Opportunity, in multiples of 32 microseconds. Ack Policy, where {{false}}=''Do Not Acknowledge'' and {{true}}=''Acknowledge''. This is a table of WMM parameters for traffic that originates at the wireless station, i.e. for incoming traffic. The size of this table is fixed, with 4 entries (with instance numbers 1 through 4). Instance numbers MUST be assigned as follows: # BE AC (Best Effort) # BK AC (Background) # VI AC (Video) # VO AC (Voice) Arbitration Inter Frame Spacing (Number). This is the number of time slots in the arbitration interframe space. Exponent of Contention Window (Minimum). This encodes the Values of CWMin as an exponent: CWMin = 2^ECWMin - 1. For example, if ECWMin is 8, then CWMin is 2^8 - 1, or 255, Exponent of Contention Window (Maximum). This encodes the Values of CWMax as an exponent: CWMax = 2^ECWMax - 1. For example, if ECWMax is 8, then CWMax is 2^8 - 1, or 255, Transmit Opportunity, in multiples of 32 microseconds. Ack Policy, where {{false}}=''Do Not Acknowledge'' and {{true}}=''Acknowledge''. This parameter is the full hierarchical parameter name of a particular ''LAN**InterfaceConfig'' object or a ''WLANConfiguration'' object. For example: ''InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.2''. In the case of an embedded Ethernet switch, the {{param}} parameter references the ''LANEthernetInterfaceConfig'' object that corresponds to the switch port the device is connected to (a ''LANEthernetInterfaceConfig'' instance for each switch port). In the case of an embedded WLAN access point, the {{param}} parameter references the ''WLANConfiguration'' object that corresponds to the SSID the device is connected to (if the access point supports multiple SSIDs, then each SSID is a separate instance). Vendor Class Identifier DHCP option (Option 60) of the host. It MAY be defined when ''AddressSource'' is ''DHCP''. {{empty}} indicates this option is not used. Client Identifier DHCP option (Option 61) for the specific IP connection of the client. The option value is binary, so an exact match is REQUIRED. It MAY be defined when ''AddressSource'' is ''DHCP''. {{empty}} indicates this option is not used. User Class Identifier DHCP option (Option 77) of the host. It MAY be defined when ''AddressSource'' is ''DHCP''. {{empty}} indicates this option is not used. Whether or not the host is currently present on the LAN. The method of presence detection is a local matter to the CPE. The ability to list inactive hosts is OPTIONAL. If the CPE includes inactive hosts in this table, this variable MUST be set to {{false}} for each inactive host. The length of time an inactive host remains listed in this table is a local matter to the CPE. This object contains LAN-side layer 1/2 interfaces that are not currently connected to the Gateway's IP router and which therefore do not currently reside within a ''LANDevice'' instance. Number of instances of {{object|LANEthernetInterfaceConfig}} in this object. Number of instances of {{object|LANUSBInterfaceConfig}} in this object. Number of instances of {{object|WLANConfiguration}} in this object object. This object models an Ethernet LAN connection on a CPE device. The object definition is identical to that for {{object|InternetGatewayDevice.LANDevice.{i}.LANEthernetInterfaceConfig.{i}}}. This object models a USB LAN connection on a CPE device. The object definition is identical to that for {{object|InternetGatewayDevice.LANDevice.{i}.LANUSBInterfaceConfig.{i}}}. This object models an 802.11 LAN connection on a CPE device. The object definition is identical to that for {{object|InternetGatewayDevice.LANDevice.{i}.WLANConfiguration.{i}}}. Specifies a WAN connection object associated with this connection instance. The content is the full hierarchical parameter name of the layer 3 connection object. Example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1''. Indicates which link encapsulation standards and recommendations are supported by the B-NT. Auto Indicates the link encapsulation standard requested by the B-NT. Indicates the link encapsulation standard that the B-NT is using for the connection. {{enum}} When the standard identifies ATM encapsulation then the {{object|InternetGatewayDevice.WANDevice.{i}.WANConnectionDevice.{i}.WANDSLLinkConfig}} object MUST be used. When the standard identifies PTM encapsulation then the {{object|InternetGatewayDevice.WANDevice.{i}.WANConnectionDevice.{i}.WANPTMLinkConfig}} object MUST be used. {{enum}} This parameter, which was inherited from WANDSLLinkConfig, is DEPRECATED because it is in general not clear which standards correspond to which of the the above enumerated values. It is RECOMMENDED that the {{param|StandardUsed}} parameter be used to indicate which standard is in use. Indicates which DSL standards and recommendations are supported by the B-NT. Indicates the standard that the B-NT is using for the connection. Indicates which VDSL2 profiles are allowed on the line. {{enum}} Note: In G.997.1, this parameter is called PROFILES. See ITU-T Recommendation G.997.1. Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be {{empty}}. Indicates which VDSL2 profile is currently in use on the line. Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be {{empty}}. The power management state of the line. The success failure cause of the initialization. An enumeration of the following integer values: * 0: Successful * 1: Configuration error. This error occurs with inconsistencies in configuration parameters, e.g. when the line is initialized in an xDSL Transmission system where an xTU does not support the configured Maximum Delay or the configured Minimum or Maximum Data Rate for one or more bearer channels. * 2: Configuration not feasible on the line. This error occurs if the Minimum Data Rate cannot be reached on the line with the Minimum Noise Margin, Maximum PSD level, Maximum Delay and Maximum Bit Error Ratio for one or more bearer channels. * 3: Communication problem. This error occurs, for example, due to corrupted messages or bad syntax messages or if no common mode can be selected in the G.994.1 handshaking procedure or due to a timeout.. * 4: No peer xTU detected. This error occurs if the peer xTU is not powered or not connected or if the line is too long to allow detection of a peer xTU. * 5: Any other or unknown Initialization Failure cause. This parameter represents the last successful transmitted initialization state in the downstream direction in the last full initialization performed on the line. Initialization states are defined in the individual xDSL Recommendations and are counted from 0 (if G.994.1 is used) or 1 (if G.994.1 is not used) up to Showtime. This parameter needs to be interpreted along with the xDSL Transmission System. This parameter is available only when, after a failed full initialization, the line diagnostics procedures are activated on the line. This parameter represents the last successful transmitted initialization state in the upstream direction in the last full initialization performed on the line. Initialization states are defined in the individual xDSL Recommendations and are counted from 0 (if G.994.1 is used) or 1 (if G.994.1 is not used) up to Showtime. This parameter needs to be interpreted along with the xDSL Transmission System. This parameter is available only when, after a failed full initialization, the line diagnostics procedures are activated on the line. This parameter contains the estimated electrical loop length expressed in dB at 1MHz, kle (see O-UPDATE in section 12.2.4.2.1.2/G.993.2). The value SHALL be coded as an unsigned 16 bit number in the range 0 (coded as 0) to 128 dB (coded as 1280) in steps of 0.1 dB. This parameter SHALL contain the set of breakpoints exchanged in the MREFPSDds fields of the O-PRM message of G.993.2. Base64 encoded of the binary representation defined in Table 12-19/G.993.2 (maximum length is 145 octets, which requires 196 bytes for Base64 encoding). This parameter SHALL contain the set of breakpoints exchanged in the MREFPSDus fields of the R-PRM message of G.993.2. Base64 encoded of the binary representation defined in Table 12-19/G.993.2 (maximum length is 145 octets, which requires 196 bytes for Base64 encoding). Indicates the enabled VDSL2 Limit PSD mask of the selected PSD mask class. Bit mask as specified in ITU-T Recommendation G.997.1. Note: For a VDSL2-capable multimode device operating in a mode other than VDSL2, the value of this parameter SHOULD be set to 0. Indicates the allowed VDSL2 US0 PSD masks for Annex A operation. Bit mask as specified in see ITU-T Recommendation G.997.1. Note: For a VDSL2-capable multimode device operating in a mode other than VDSL2, the value of this parameter SHOULD be set to 0. {{enum}} Note1: This parameter is only applicable to G.992.1. Note2: For an ADSL1-capable multimode device operating in a mode other than ADSL1, the value of this parameter SHOULD be set to {{enum|None}}. ADSL1 Interleaved depth. This variable is only applicable to ADSL1 and only if {{param|DataPath}} = {{enum|Interleaved|DataPath}}. Otherwise, the value of this parameter MUST be zero. Reports the index of the latency path supporting the bearer channel. For single-latency connections, LPATH = 0. Note: See ITU-T Recommendation G.997.1. Reports the interleaver depth D for the latency path indicated in LPATH. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to -1. Reports the interleaver block length in use on the latency path indicated in LPATH. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to -1. Reports the actual delay, in milliseconds, of the latency path due to interleaving. Note: In G.997.1, this parameter is called "Actual Interleaving Delay." See ITU-T Recommendation G.997.1. Reports the actual impulse noise protection (INP) provided by the latency path indicated in LPATH. The value is the actual INP in the L0 (i.e., Showtime) state. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to -1. Reports whether the value reported in ACTINP was computed assuming the receiver does not use erasure decoding. Valid values are 0 (computed per the formula assuming no erasure decoding) and 1 (computed by taking into account erasure decoding capabilities of receiver). Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to {{false}}. Reports the size, in octets, of the Reed-Solomon codeword in use on the latency path indicated in LPATH. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to -1. Reports the number of redundancy bytes per Reed-Solomon codeword on the latency path indicated in LPATH. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to -1. Reports the number of bits per symbol assigned to the latency path indicated in LPATH. This value does not include overhead due to trellis coding. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to -1. Reports whether trellis coding is enabled in the downstream direction. A value of 1 indicates that trellis coding is in use, and a value of 0 indicates that the trellis is disabled. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to -1. Reports whether trellis coding is enabled in the upstream direction. A value of 1 indicates that trellis coding is in use, and a value of 0 indicates that the trellis is disabled. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to -1. Reports whether the OPTIONAL virtual noise mechanism is in use in the downstream direction. A value of 1 indicates the virtual noise mechanism is not in use, and a value of 2 indicates the virtual noise mechanism is in use. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Reports whether the OPTIONAL virtual noise mechanism is in use in the upstream direction. A value of 1 indicates the virtual noise mechanism is not in use, and a value of 2 indicates the virtual noise mechanism is in use. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Reports the virtual noise PSD for the downstream direction. Base64 encoded of the binary representation defined in G.997.1 by the parameter called TXREFVNds (maximum length is 97 octets, which requires 132 bytes for Base64 encoding). See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to {{empty}}. Reports the virtual noise PSD for the upstream direction. Base64 encoded of the binary representation defined in G.997.1by the parameter called TXREFVNus (maximum length is 49 octets, which requires 68 bytes for Base64 encoding). See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to {{empty}}. Reports the actual cyclic extension, as the value of m, in use for the connection. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 99. Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, it MUST have the value 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, it MUST have the value 4294967295 (the maximum for its data type). Note: This parameter is related to the G.997.1 parameter ATTNDRus, which is measured in bits/s. See ITU-T Recommendation G.997.1. Note: This parameter is related to the G.997.1 parameter ATTNDRds, which is measured in bits/s. See ITU-T Recommendation G.997.1. The current signal-to-noise ratio margin (expressed in 0.1 dB) in the upstream direction. Note: In G.997.1, this parameter is called SNRMus. See ITU-T Recommendation G.997.1. The current signal-to-noise ratio margin (expressed in 0.1 dB) in the downstream direction. Note: In G.997.1, this parameter is called SNRMds. See ITU-T Recommendation G.997.1. The current signal-to-noise ratio margin of each upstream band. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. The current signal-to-noise ratio margin of each band. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. The Impulse Noise Monitoring (INM) Inter Arrival Time (IAT) Offset, measured in DMT symbols, that the xTU receiver uses to determine in which bin of the IAT histogram the IAT is reported. Note: In G.997.1, this parameter is called INMIATO. See ITU-T Recommendation G.997.1. The Impulse Noise Monitoring (INM) Inter Arrival Time (IAT) Step that the xTU receiver uses to determine in which bin of the IAT histogram the IAT is reported. Note: In G.997.1, this parameter is called INMIATS. See ITU-T Recommendation G.997.1. The Impulse Noise Monitoring (INM) Cluster Continuation value, measured in DMT symbols, that the xTU receiver uses in the cluster indication process. Note: In G.997.1, this parameter is called INMCC. See ITU-T Recommendation G.997.1. The Impulse Noise Monitoring (INM) Equivalent Impulse Noise Protection (INP) Mode that the xTU receiver uses in the computation of the Equivalent INP. Note: In G.997.1, this parameter is called INM_INPEQ_MODE. See ITU-T Recommendation G.997.1. The current output power at the CPE's DSL interface (expressed in 0.1 dBmV). The current received power at the CPE's DSL interface (expressed in 0.1 dBmV). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, it MUST have the value "00000000". Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, it MUST have the value "0000". When T1.413 modulation is not in use, the parameter value SHOULD be 0. When T1.413 modulation is not in use, the parameter value SHOULD be 0. Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, it MUST have the value "00000000". Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, it MUST have the value "0000". When T1.413 modulation is not in use, the parameter value SHOULD be 0. When T1.413 modulation is not in use, the parameter value SHOULD be 0. Number of seconds since the most recent DSL Showtime - the beginning of the period used for collection of ''Showtime'' statistics. Showtime is defined as successful completion of the DSL link establishment process. The ''Showtime'' statistics are those collected since the most recent establishment of the DSL link. Number of seconds since the beginning of the period used for collection of ''CurrentDay'' statistics. The CPE MAY align the beginning of each CurrentDay interval with days in the UTC time zone, but does not have to do so. Statistics SHOULD continue to be accumulated across CPE reboots, though this might not always be possible. Number of seconds since the beginning of the period used for collection of ''QuarterHour'' statistics. The CPE MAY align the beginning of each QuarterHour interval with real-time quarter-hour intervals, but does not have to do so. Statistics SHOULD continue to be accumulated across CPE reboots, though this might not always be possible. This object contains the DSL test parameters that are available during the L0 (i.e., Showtime) state. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|HLOGpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|HLOGpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Downstream logarithmic channel characteristics per sub-carrier group. The maximum number of elements is 256 for G.992.3, and 512 for G.992.5. For G.993.2, the number of elements will depend on the value of {{param|HLOGGds}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Note: {{param}} is measured during initialization and is not updated during Showtime. Upstream logarithmic channel characteristics per sub-carrier group. The maximum number of elements is 64 for G.992.3 and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|HLOGGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Note: {{param}} is measured during initialization and is not updated during Showtime. Indicates the number of symbols over which {{param|HLOGpsds}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|HLOGpsus}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|QLNpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|QLNpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Downstream quiet line noise per subcarrier group. The maximum number of elements is 256 for G.992.3 and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|QLNGds}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter should be set to ''None''. Note: {{param}} is measured during initialization and is not updated during Showtime. Upstream quiet line noise per subcarrier group. The maximum number of elements is 64 for G.992.3 and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|QLNGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter should be set to ''None''. Note: {{param}} is measured during initialization and is not updated during Showtime. Indicates the number of symbols over which {{param|QLNpsds}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|QLNpsus}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|SNRpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|SNRpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Downstream SNR per subcarrier group. The maximum number of elements is 256 for G.992.3, and 512 for G.992.5. For G.993.2, the number of elements will depend on the value of {{param|SNRGds}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter should be set to ''None''. Note: {{param}} is first measured during initialization and is updated during Showtime. Upstream SNR per subcarrier group. The maximum number of elements is 64 for G.992.3 and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|SNRGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter should be set to ''None''. Note: {{param}} is first measured during initialization and is updated during Showtime. Indicates the number of symbols over which {{param|SNRpsds}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|SNRpsus}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Downstream line attenuation per usable band, as computed during initialization. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. Upstream line attenuation per usable band, as computed during initialization. Number of elements is dependent on the number of upstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. Downstream signal attenuation per usable band, as computed during the L0 (i.e., Showtime) state. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. Upstream signal attenuation per usable band, as computed during the L0 (i.e., Showtime) state. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. Total number of successfully received blocks, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Total number of successfully transmitted blocks, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not defined in G.997.1. LInit is a flag to signal that a failure occurred as defined in G.997.1. This parameter is DEPRECATED because it is not defined in G.997.1. This parameter corresponds to LOF as defined in ITU-T Rec. G.997.1. LOF is a flag to signal that a failure occurred. Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Total number of errored seconds detected by the ATU-C (ES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Total number of severely errored seconds detected by the ATU-C (SES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of successfully received blocks since the most recent DSL Showtime, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of successfully transmitted blocks since the most recent DSL Showtime, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not defined in G.997.1. LInit is a flag to signal that a failure occurred as defined in G.997.1. This parameter is DEPRECATED because it is not defined in G.997.1. This parameter corresponds to LOF as defined in ITU-T Rec. G.997.1. LOF is a flag to signal that a failure occurred. Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of errored seconds since the most recent DSL Showtime detected by the ATU-C (ES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of severely errored seconds since the most recent DSL Showtime detected by the ATU-C (SES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of successfully received blocks since the second most recent DSL Showtime, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of successfully transmitted blocks since the second most recent DSL Showtime, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. This parameter is DEPRECATED because it is not defined in G.997.1. LInit is a flag to signal that a failure occurred as defined in G.997.1. This parameter is DEPRECATED because it is not defined in G.997.1. This parameter corresponds to LOF as defined in ITU-T Rec. G.997.1. LOF is a flag to signal that a failure occurred. Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of errored seconds since the second most recent DSL Showtime detected by the ATU-C (ES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of severely errored seconds since the second most recent DSL Showtime (SES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of severely errored seconds since the second most recent DSL Showtime detected by the ATU-C (SES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of FEC errors detected since the second most recent DSL Showtime (FEC-C as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of FEC errors detected by the ATU-C since the second most recent DSL Showtime (FEC-CFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of HEC errors detected since the second most recent DSL Showtime (HEC-P as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of HEC errors detected by the ATU-C since the second most recent DSL Showtime (HEC-PFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of CRC errors detected since the second most recent DSL Showtime (CV-C as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of CRC errors detected by the ATU-C since the second most recent DSL Showtime (CV-CFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of successfully received blocks during the current day, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of successfully transmitted blocks during the current day, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of cell-delineation errors during the current day (total seconds with NCD or LCD failures as defined in ITU-T Rec. G.997.1). This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of link-retrain errors during the current day (Full Initialization Count as defined in ITU-T Rec. G.997.1). This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of initialization errors during the current day (LINIT failures as defined in ITU-T Rec. G.997.1). This parameter is DEPRECATED because it is not defined in G.997.1. LInit is a flag to signal that a failure occurred as defined in G.997.1. Number of loss-of-framing errors during the current day (LOF failures as defined in ITU-T Rec. G.997.1). This parameter is DEPRECATED because it is not defined in G.997.1. This parameter corresponds to LOF as defined in ITU-T Rec. G.997.1. LOF is a flag to signal that a failure occurred. Number of errored seconds during the current day (ES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of errored seconds during the current day detected by the ATU-C (ES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of severely errored seconds during the current day (SES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of severely errored seconds during the current day detected by the ATU-C (SES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of FEC errors detected during the current day (FEC-C as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of FEC errors detected by the ATU-C during the current day (FEC-CFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of HEC errors detected during the current day (HEC-P as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of HEC errors detected by the ATU-C during the current day (HEC-PFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of CRC errors detected during the current day (CV-C as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of CRC errors detected by the ATU-C during the current day (CV-CFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of successfully received blocks during the current quarter hour, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of successfully transmitted blocks during the current quarter hour, where a block is as defined in RFC 2662 {{bibref|RFC2662}}. This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of cell-delineation errors during the current quarter hour (total seconds with NCD or LCD failures as defined in ITU-T Rec. G.997.1). This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of link-retrain errors during the current quarter hour (Full Initialization Count as defined in ITU-T Rec. G.997.1). This parameter is DEPRECATED because it is not available at either the G or the S/T interface. Number of initialization errors during the current quarter hour (LINIT failures as defined in ITU-T Rec. G.997.1). This parameter is DEPRECATED because it is not defined in G.997.1. LInit is a flag to signal that a failure occurred as defined in G.997.1. Number of loss-of-framing errors during the current quarter hour (LOF failures as defined in ITU-T Rec. G.997.1). This parameter is DEPRECATED because it is not defined in G.997.1. This parameter corresponds to LOF as defined in ITU-T Rec. G.997.1. LOF is a flag to signal that a failure occurred. Number of errored seconds during the current quarter hour (ES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of errored seconds during the current quarter hour detected by the ATU-C (ES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of severely errored seconds during the current quarter hour (SES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of severely errored seconds during the current quarter hour detected by the ATU-C (SES-L as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of FEC errors detected during the current quarter hour (FEC-C as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of FEC errors detected by the ATU-C during the current quarter hour (FEC-CFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of HEC errors detected during the current quarter hour (HEC-P as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of HEC errors detected by the ATU-C during the current quarter hour (HEC-PFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of CRC errors detected during the current quarter hour (CV-C as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Number of CRC errors detected by the ATU-C during the current quarter hour (CV-CFE as defined in ITU-T Rec. G.997.1). Note: This parameter is OPTIONAL at the G and S/T interfaces in G.997.1 Amendment 1. If the parameter is implemented but no value is available, its value MUST be 4294967295 (the maximum for its data type). Rate to shape this connection's egress traffic to. For leaky bucket (constant rate shaping), this is the constant rate. For token bucket (variable rate shaping), this is the average rate. If <= 100, in percent of the rate of the highest rate-constrained layer over which the packet will travel on egress. If > 100, in bits per second. A value of -1 indicates no shaping. For example, for packets destined for a WAN DSL interface, if the ATM layer is rate-constrained, then the rate is calculated relative to this rate. Otherwise, the rate is calculated relative to the physical-layer DSL rate. Burst size in bytes. For both leaky bucket (constant rate shaping) and token bucket (variable rate shaping) this is the bucket size and is therefore the maximum burst size. Specifies a WAN connection object associated with this connection instance. The content is the full hierarchical parameter name of the layer 3 connection object. Example: ''InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1''. This parameter is OBSOLETED because it is within an OBSOLETED object. Note: See ITU-T Recommendation G.997.1. Note: See ITU-T Recommendation G.997.1. Note: See ITU-T Recommendation G.997.1. Note: See ITU-T Recommendation G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Scaling used to represent the upstream linear channel characteristics. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|HLINpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|HLINpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|HLOGpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|HLOGpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Downstream logarithmic channel characteristics per sub-carrier group. The maximum number of elements is 256 for G.992.3, and 512 for G.992.5. For G.993.2, the number of elements will depend on the value of {{param|HLOGGds}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Note: {{param}} is measured during initialization and is not updated during Showtime. Upstream logarithmic channel characteristics per sub-carrier group. The maximum number of elements is 64 for G.992.3 and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|HLOGGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Note: {{param}} is measured during initialization and is not updated during Showtime. Indicates the number of symbols over which {{param|HLOGpsds}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|HLOGpsus}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Downstream line attenuation per usable band, as computed during initialization. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. Upstream line attenuation per usable band, as computed during initialization. Number of elements is dependent on the number of upstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. Downstream signal attenuation per usable band, as computed during the L0 (i.e., Showtime) state. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. Upstream signal attenuation per usable band, as computed during the L0 (i.e., Showtime) state. Number of elements is dependent on the number of downstream bands but will exceed one only for G.993.2. Interpretation of {{param}} is as defined in ITU-T Rec. G.997.1. Note: See ITU-T Recommendation G.997.1. Downstream linear channel characteristics per subcarrier group. Maximum number of complex pairs is 256 for G.992.3, and 512 for G.992.5. For G.993.2, the number of pairs will depend on the value of {{param|HLINGds}} but will not exceed 512. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: HLIN is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Upstream linear channel characteristics per sub-carrier group. Maximum number of complex pairs is 64 for G.992.3, and G.992.5. For G.993.2, the number of pairs will depend on the value of {{param|HLINGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: HLIN is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|QLNpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|QLNpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Downstream quiet line noise per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. For G.993.2, the number of elements will depend on the value of {{param|QLNGds}} but will not exceed 512. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: QLN is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Upstream quiet line noise per subcarrier group. The maximum number of elements is 64 for G.992.3, and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|QLNGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: QLN is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Indicates the number of symbols over which {{param|QLNpsds}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|QLNpsus}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Number of sub-carriers per sub-carrier group in the downstream direction for {{param|SNRpsds}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Number of sub-carriers per sub-carrier group in the upstream direction for {{param|SNRpsus}}. Valid values are 1, 2, 4, and 8. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 1. Downstream SNR per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. For G.993.2, the number of elements will depend on the value of {{param|SNRGds}} but will not exceed 512. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Note: SNRps is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Upstream SNR per subcarrier group. The maximum number of elements is 64 for G.992.3, and G.992.5. For G.993.2, the number of elements will depend on the value of {{param|SNRGus}} but will not exceed 512. Interpretation of the values is as defined in ITU-T Rec. G.997.1. Note: SNRps is not applicable in PLOAM for G.992.1 or G.992.2. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to ''None''. Indicates the number of symbols over which {{param|SNRpsds}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Indicates the number of symbols over which {{param|SNRpsus}} was measured. Note: See ITU-T Recommendation G.997.1. For a multimode device operating in a mode in which this parameter does not apply, the value of this parameter SHOULD be set to 0. Downstream bit allocation per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Upstream bit allocation per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. Interpretation of the value is as defined in ITU-T Rec. G.997.1. Downstream gain allocation per subcarrier group. Maximum number of elements is 256 for G.992.3, 512 for G.992.5. Interpretation of the value is as defined in ITU-T Rec. G.997.1. This parameter is DEPRECATED. Each instance contains objects associated with a given WAN link. In the case of DSL, each instance corresponds to either a single ATM VC or a PTM Ethernet link. On creation of a ''WANConnectionDevice'' instance, there are initially no connection objects contained within. In the case of Ethernet (interface or link), only one ''WANConnectionDevice'' instance is supported. Indicates the type of DSL connection and refers to the complete stack of protocol used for this connection. {{enum}} The value {{enum|PPPoE}} has always been DEPRECATED and {{enum|EoA}} SHOULD be used instead (see {{bibref|TR-098a2|Annex B}}). The ACS MUST NOT set this parameter to {{enum|PPPoE}} and the CPE MUST reject attempts to do so. RFC 2684 {{bibref|RFC2684}} bridged Ethernet over ATM RFC 2684 {{bibref|RFC2684}} routed IP over ATM RFC 2364 {{bibref|RFC2634}} PPP over ATM RFC 2516 {{bibref|RFC2516}} PPP over Ethernet on RFC 2684 {{bibref|RFC2684}} bridged Ethernet over ATM RFC 2225 {{bibref|RFC2225}} Classical IP over ATM This flag tells if a checksum SHOULD be added in the ATM payload. It does not refer to the checksum of one of the ATM cells or AALX packets. In case of LLC or VCMUX encapsulation, this ATM checksum is the FCS field described in RFC 2684 {{bibref|RFC2684}}. It is only applicable in the upstream direction. Ordered list of VPI/VCI pairs to search if a link using the {{param|DestinationAddress}} cannot be established. In the form: : ''VPI1/VCI1, VPI2/VCI2, ...'' Example: : ''0/35, 8/35, 1/35'' This object models the PTM layer properties specific to a layer 2 interface of a DSL modem used for Internet access on a CPE. This object is intended for a CPE with a DSL modem WAN interface, and is exclusive of any other ''WAN*LinkConfig'' object within a given ''WANConnectionDevice'' instance. The PTM Link Layer object exists when the ''WANDSLInterfaceConfig'' ''LinkEncapsulationSupported'' parameter includes any of: * ''G.992.3_Annex_K_PTM'' * ''G.993.2_Annex_K_PTM'' * ''G.994.1'' Enables or disables the link. On creation of a ''WANConnectionDevice'', this object is disabled by default. Status of the link. The physical address of the interface. This object represents the statistics collected and returned over a PTM link. The total number of bytes transmitted out of the interface, including framing characters. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of bytes received on the interface, including framing characters. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets (frames) transmitted out of the interface. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets (frames) which were received on this interface. The value of this counter MAY be reset to zero when the CPE is rebooted. Indication that the CPE has detected the link is Out of Synchronization since the CPE rebooted or the interface was last enabled. Indication that the remote device has detected the link is Out of Synchronization since the CPE rebooted or the interface was last enabled. The total number of outbound packets that could not be transmitted because of errors. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets that contained errors preventing them from being deliverable. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were not addressed to a multicast or broadcast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were not addressed to a multicast or broadcast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were addressed to a multicast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a multicast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were addressed to a broadcast address, including those that were discarded or not sent. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a broadcast address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets received via the interface which were discarded because of an unknown or unsupported protocol. The value of this counter MAY be reset to zero when the CPE is rebooted. If the ''Layer2Bridging'' object is implemented, the view that it provides of the CPE's underlying bridging configuration MUST be consistent with the view provided by any ''LANDevice'' and ''WAN**Connection'' objects. The implications of this are explained in {{bibref|TR-098a2|Annex A.6}}. When set to {{true}}, the device MUST tear down the existing IP connection represented by this object and establish a new one. The device MUST initiate the reset after completion of the current CWMP session. The device MAY delay resetting the connection in order to avoid interruption of a user service such as an ongoing voice call. When read, this parameter always returns {{false}}. {{enum}} The value {{enum|Disconneting}} is DEPRECATED because it is a typo. The ACS MUST treat {{enum|Disconneting}} and {{enum|Disconnecting}} the same. Rate to shape this connection's egress traffic to. For leaky bucket (constant rate shaping), this is the constant rate. For token bucket (variable rate shaping), this is the average rate. If <= 100, in percent of the rate of the highest rate-constrained layer over which the packet will travel on egress. If > 100, in bits per second. A value of -1 indicates no shaping. For example, for packets destined for a WAN DSL interface, if the ATM layer is rate-constrained, then the rate is calculated relative to this rate. Otherwise, the rate is calculated relative to the physical-layer DSL rate. This object contains DHCP client configuration parameters. The number of entries in the {{object|SentDHCPOption}} table. The number of entries in the {{object|ReqDHCPOption}} table. The external port (or the first port of a range of external ports) that the NAT gateway would listen on for connection requests to a corresponding {{param|InternalPort}}. Inbound packets to this external port on the WAN interface SHOULD be forwarded to {{param|InternalClient}} on the {{param|InternalPort}}. A value of zero (0) represents a "wildcard". If this value is a wildcard, connection requests on all external ports (that are not otherwise mapped) will be forwarded to {{param|InternalClient}}. In the wildcard case, the value(s) of {{param|InternalPort}} on {{param|InternalClient}} are ignored. When wildcard values are used for {{param|RemoteHost}} and/or {{param}}, the following precedence order applies (with the highest precedence listed first): # Explicit {{param|RemoteHost}}, explicit {{param}} # Explicit {{param|RemoteHost}}, wildcard {{param}} # Wildcard {{param|RemoteHost}}, explicit {{param}} # Wildcard {{param|RemoteHost}}, wildcard {{param}} If an incoming packet matches the criteria associated with more than one entry in this table, the CPE MUST apply the port mapping associated with the highest precedence entry. At most one entry in this table can exist with all of the same values for {{param|RemoteHost}}, {{param}}, and {{param|PortMappingProtocol}}. Indicates the last port of the external port range that starts with {{param|ExternalPort}}. If an external port range is specified, then the behavior described for {{param|ExternalPort}} applies to all ports within the range. A value of zero (0) indicates that no external port range is specified, i.e. that the range consists only of {{param|ExternalPort}}. If {{param|ExternalPort}} is zero (wildcard), the value of this parameter MUST be ignored. If specified, the value of this parameter MUST be greater than or equal to the value of {{param|ExternalPort}}. The total number of bytes transmitted, including framing characters, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of bytes received, including framing characters, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets transmitted over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets which were received over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets that could not be transmitted because of errors, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets that contained errors preventing them from being deliverable, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were not addressed to a multicast or broadcast address, including those that were discarded or not sent, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were not addressed to a multicast or broadcast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission, including those that were discarded or not sent, which were addressed to a multicast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a multicast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission, including those that were discarded or not sent, which were addressed to a broadcast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a broadcast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets which were discarded because of an unknown or unsupported protocol, received over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. Each instance of this object represents a DHCP option that MUST, if enabled, be sent in DHCP client requests. All sent DHCP options MUST be listed. Enables or disables this SentDHCPOption table entry. Option tag as defined in RFC 2132 {{bibref|RFC2132}}. Base64 encoded option value. Each instance of this object represents a DHCP option that MUST, if enabled, be requested in DHCP client requests. All requested DHCP options MUST be listed. Enables or disables this ReqDHCPOption table entry. Position of the option in the DHCP client request. A value of 1 indicates the first entry. When this value is modified, if the value matches that of an existing entry, the Order value for the existing entry and all lower Order entries is incremented to ensure uniqueness of this value. A deletion causes Order values to be compacted. When a value is changed, incrementing occurs before compaction. The value on creation of a ReqDHCPOption table entry MUST be one greater than the largest current value. Option tag as defined in RFC 2132 {{bibref|RFC2132}}. Base64 encoded most recently received DHCP option value. If no option value has been received, then the value MUST represent {{empty}}. Received DHCP option values MAY, but need not, persist across CPE reboots. If the ''Layer2Bridging'' object is implemented, the view that it provides of the CPE's underlying bridging configuration MUST be consistent with the view provided by any ''LANDevice'' and ''WAN**Connection'' objects. The implications of this are explained in {{bibref|TR-098a2|Annex A.6}}. When set to {{true}}, the device MUST tear down the existing PPP connection represented by this object and establish a new one. The device MUST initiate the reset after completion of the current CWMP session. The device MAY delay resetting the connection in order to avoid interruption of a user service such as an ongoing voice call. When read, this parameter always returns {{false}}. Represents the PPPoE Session ID. Represents the IP Address of the remote end Default Gateway established through PPPoE. Rate to shape this connection's egress traffic to. For leaky bucket (constant rate shaping), this is the constant rate. For token bucket (variable rate shaping), this is the average rate. If <= 100, in percent of the rate of the highest rate-constrained layer over which the packet will travel on egress. If > 100, in bits per second. A value of -1 indicates no shaping. For example, for packets destined for a WAN DSL interface, if the ATM layer is rate-constrained, then the rate is calculated relative to this rate. Otherwise, the rate is calculated relative to the physical-layer DSL rate. The external port (or the first port of a range of external ports) that the NAT gateway would listen on for connection requests to a corresponding {{param|InternalPort}}. Inbound packets to this external port on the WAN interface SHOULD be forwarded to {{param|InternalClient}} on the {{param|InternalPort}}. A value of zero (0) represents a "wildcard". If this value is a wildcard, connection request on all external ports (that are not otherwise mapped) will be forwarded to {{param|InternalClient}}. In the wildcard case, the value(s) of {{param|InternalPort}} on {{param|InternalClient}} are ignored. When wildcard values are used for {{param|RemoteHost}} and/or {{param}}, the following precedence order applies (with the highest precedence listed first): # Explicit {{param|RemoteHost}}, explicit {{param}} # Explicit {{param|RemoteHost}}, wildcard {{param}} # Wildcard {{param|RemoteHost}}, explicit {{param}} # Wildcard {{param|RemoteHost}}, wildcard {{param}} If an incoming packet matches the criteria associated with more than one entry in this table, the CPE MUST apply the port mapping associated with the highest precedence entry. At most one entry in this table can exist with all of the same values for {{param|RemoteHost}}, {{param}}, and {{param|PortMappingProtocol}}. Indicates the last port of the external port range that starts with {{param|ExternalPort}}. If an external port range is specified, then the behavior described for {{param|ExternalPort}} applies to all ports within the range. A value of zero (0) indicates that no external port range is specified, i.e. that the range consists only of {{param|ExternalPort}}. If {{param|ExternalPort}} is zero (wildcard), the value of this parameter MUST be ignored. If specified, the value of this parameter MUST be greater than or equal to the value of {{param|ExternalPort}}. The total number of bytes transmitted, including framing characters, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of bytes received, including framing characters, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets transmitted over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets which were received over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets that could not be transmitted because of errors, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets that contained errors preventing them from being deliverable, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission which were not addressed to a multicast or broadcast address, including those that were discarded or not sent, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were not addressed to a multicast or broadcast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. One possible reason for discarding such a packet could be to free up buffer space. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission, including those that were discarded or not sent, which were addressed to a multicast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a multicast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets requested for transmission, including those that were discarded or not sent, which were addressed to a broadcast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of received packets which were addressed to a broadcast address, over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted. The total number of packets which were discarded because of an unknown or unsupported protocol, received over all connections within the same ''WANConnectionDevice'' that share a common MAC address. The value of this counter MAY be reset to zero when the CPE is rebooted.