A non-volatile handle used to reference this instance. '''This is intended only for use in protocol-independent "common" definitions, and MUST NOT be used in protocol-specific definitions.''' A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in {{bibref|TR-069|3.6.1}} and described in {{bibref|TR-069|Appendix II}}, the following mandatory constraints MUST be enforced: * Its value MUST NOT be empty. * Its value MUST start with a letter. * If its value is not assigned by the ACS, it MUST start with a "cpe-" prefix. * The CPE MUST NOT change the parameter value. A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in {{bibref|TR-069|3.6.1}} and described in {{bibref|TR-069|Appendix II}}, the following mandatory constraints MUST be enforced: * Its value MUST NOT be empty. * Its value MUST start with a letter. * If its value is not assigned by the ACS, it MUST start with a "cpe-" prefix. * The CPE MUST NOT change the parameter value. The value is measured in ''dBm/1000'', i.e. the value divided by 1000 is dB relative to 1 mW. For example, -12345 means -12.345 dBm, 0 means 0 dBm (1 mW) and 12345 means 12.345 dBm. Indicates the availability of diagnostics data. Enumeration of: {{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 values are {{enum|Requested}} and {{enum|Canceled}}. To ensure the use of the proper test parameters (the writable parameters in this object), the test parameters MUST be set, and any errors or inconsistencies in the test parameters MUST be detected, either prior to or at the same time as (in the same SetParameterValues) setting this parameter to {{enum|Requested}}. When requested, the CPE SHOULD wait until after completion of the communication session with the ACS before starting the diagnostic test. When the test is completed, the value of this parameter MUST be either {{enum|Complete}} (if the test completed successfully), or one of the ''Error'' values listed above. If the value of this parameter is anything other than {{enum|Complete}}, the values of the results parameters for this test are indeterminate. When the diagnostic initiated by the ACS is completed (successfully or not), but not if it is canceled for any reason, 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. After the diagnostic is complete, the value of all result parameters (all read-only parameters in this object) MUST be retained by the CPE until either this diagnostic is run again, or the CPE reboots. After a reboot, if the CPE has not retained the result parameters from the most recent test, it MUST set the value of this parameter to {{enum|None}}. Modifying any of the writable parameters in this object except for this one MUST result in the value of this parameter being set to {{enum|None}}. While the test is in progress, modifying any of the writable parameters in this object except for this one MUST result in the test being terminated and the value of this parameter being set to {{enum|None}}. While the test is in progress, setting this parameter to {{enum|Requested}} (and possibly modifying other writable parameters in this object) MUST result in the test being terminated and then restarted using the current values of the test parameters. While the test is in progress, setting this parameter to {{enum|Canceled}} MUST result in the test being canceled and the value of this parameter being set to {{enum|None}}. If the CPE does not support the {{enum|Canceled}} value, it MUST return a SPV error with "Invalid Parameter value" (9007) to the ACS instead. The IEEE EUI 64-bit identifier as defined in {{bibref|IEEE_EUI64}}. The IEEE defined 64-bit extended unique identifier (EUI-64) is a concatenation of: * The 24-bit (OUI-24) or 36-bit (OUI-36) company_id value assigned by the IEEE Registration Authority (IEEE-RA), and * The extension identifier (40 bits for OUI-24 or 28 bits for OUI-36) assigned by the organization with that company_id assignment. IP address, i.e. IPv4 address (or IPv4 subnet mask) or IPv6 address. All IPv4 addresses and subnet masks MUST be represented as strings in IPv4 dotted-decimal notation. Here are some examples of valid IPv4 address textual representations: * 216.52.29.100 * 192.168.1.254 All IPv6 addresses MUST be represented using any of the 3 standard textual representations defined in {{bibref|RFC4291}} Sections 2.2.1, 2.2.2 and 2.2.3. Both lower-case and upper-case letters can be used, but use of lower-case letters is RECOMMENDED. Here are some examples of valid IPv6 address textual representations: * 1080:0:0:800:ba98:3210:11aa:12dd * 1080::800:ba98:3210:11aa:12dd * 0:0:0:0:0:0:13.1.68.3 IPv6 addresses MUST NOT include zone identifiers. Zone identifiers are discussed in {{bibref|RFC4007|Section 6}}. Unspecified or inapplicable addresses (or IPv4 subnet masks) MUST be represented as empty strings unless otherwise specified by the parameter definition. IPv4 address (or subnet mask). Can be any IPv4 address that is permitted by the ''IPAddress'' data type. IPv6 address. Can be any IPv6 address that is permitted by the ''IPAddress'' data type. IPv4 or IPv6 routing prefix in Classless Inter-Domain Routing (CIDR) notation {{bibref|RFC4632}}. This is specified as an IP address followed by an appended "/n" suffix, where ''n'' (the prefix size) is an integer in the range 0-32 (for IPv4) or 0-128 (for IPv6) that indicates the number of (leftmost) '1' bits of the routing prefix. * IPv4 example: 192.168.1.0/24 * IPv6 example: 2001:edff:fe6a:f76::/64 This notation can also represent individual addresses by specifying all bits. * IPv4 example: 192.168.1.1/32 * IPv6 example: 2001:edff:fe6a:f76::1/128 If the IP address part is unspecified or inapplicable, it MUST be {{empty}} unless otherwise specified by the parameter definition. In this case the IP prefix will be of the form "/n". If the entire IP prefix is unspecified or inapplicable, it MUST be {{empty}} unless otherwise specified by the parameter definition. IPv4 address prefix. Can be any IPv4 prefix that is permitted by the ''IPPrefix'' data type. IPv6 address prefix. Can be any IPv6 prefix that is permitted by the ''IPPrefix'' data type. All MAC addresses are represented as strings of 12 hexadecimal digits (digits 0-9, letters A-F or a-f) displayed as six pairs of digits separated by colons. Unspecified or inapplicable MAC addresses MUST be represented as empty strings unless otherwise specified by the parameter definition. Position of the {{object}} entry in the order of precedence. A value of ''1'' indicates the first entry to be considered (highest precedence). When a {{object}} instance is created, or when an existing {{param}} value is modified, if the value matches that of an existing entry, the {{param}} values for the existing entry and all lower {{param}} entries are incremented (lowered in precedence) to ensure uniqueness of this value. A deletion causes {{param}} values to be compacted. When a value is changed, incrementing occurs before compaction. If no {{param}} value is supplied on creation of a {{object}} instance, it MUST be assigned a value that is one more than the largest current value (lowest precedence). A 32-bit statistics parameter, e.g. a byte counter. This data type SHOULD NOT be used for statistics parameters whose values might become greater than the maximum value that can be represented as an ''unsignedInt'' (i.e. 0xffffffff, referred to below as ''maxval''). ''StatsCounter64'' SHOULD be used for such parameters. The value ''maxval'' indicates that no data is available for this parameter. In the unlikely event that the actual value of the statistic is ''maxval'', the CPE SHOULD return ''maxval - 1''. The actual value of the statistic might be greater than ''maxval''. Such values SHOULD wrap around through zero. The term ''packet'' is to be interpreted as the transmission unit appropriate to the protocol layer in question, e.g. an IP packet or an Ethernet frame. A 64-bit statistics parameter, e.g. a byte counter. This data type SHOULD be used for all statistics parameters whose values might become greater than the maximum value that can be represented as an ''unsignedInt''. The maximum value that can be represented as an ''unsignedLong'' (i.e. 0xffffffffffffffff) indicates that no data is available for this parameter. The term ''packet'' is to be interpreted as the transmission unit appropriate to the protocol layer in question, e.g. an IP packet or an Ethernet frame. Universally Unique Identifier. See {{bibref|RFC4122}}. Uniform Resource Identifier. See {{bibref|RFC3986}}. Uniform Resource Locator. See {{bibref|RFC3986}} (URI), {{bibref|IANA-uri-schemes}}, and individual URI scheme RFCs such as {{bibref|RFC7252}} (''coap'', ''coaps'') and {{bibref|RFC7230}} (''http'', ''https''). The ZigBee 16-bit network address (NWK) as defined in {{bibref|ZigBee2007}}. The address is assigned to a device by the network layer and used by the network layer for routing messages between devices. Pair of 32-bit signed integers a(i),b(i) with each pair representing a complex component of the uncalibrated echo response (UER); # Real UER component, a(i) # Imaginary UER component, b(i) for values of i starting at i=0. Both values are represented as signed integers. The interpretation of the UER value is as defined in {{bibref|G.996.2|Clause A.2.2.1}}. # the Power Spectral Density (PSD) breakpoint sub-carrier index in the range [0:49152] with Df = 4.3125 kHz frequency spacing, and # the value of the level of the PSD at this sub-carrier expressed in ''0.1 dBm/Hz'' with an offset of -200 dBm/Hz. The range of valid values for PSD is -30 to -200 dBm/Hz. Both values are represented as unsignedInt. # The paired frequency spacing index in the range [0:8191], and # The transfer function log value, i.e. [i, TFlog(i * {{param|TFlogGroupSize}} * Df)], where the reference frequency spacing Df = 4.3125 kHz, the index i valid range is 0 to 8191, and TFlog(i * {{param|TFlogGroupSize}} * Df) spans a range from +6.0 dB down to -96.2 dB with units of 0.1 dB. Both values are represented as unsignedInt. This data type represents power levels that are normally expressed in dBmV. Units are in tenths of a dBmV; for example, 5.1 dBmV will be represented as 51. This data type represents power levels that are normally expressed in dB. Units are in tenths of a dB; for example, 5.1 dB will be represented as 51. Indicates the DOCSIS Upstream Channel Type. Information not available Time Division Multiple Access Advanced Time Division Multiple Access Synchronous Code Division Multiple Access Simultaneous support of TDMA and A-TDMA modes This data type represents the equalizer data as measured at the receiver interface. The format of the equalizer follows the structure of the Transmit Equalization Adjust RNG-RSP TLV of DOCSIS RFI v2.0. The equalizer coefficients are considered signed 16-bit integers in the range from -32768 (0x8000) to 32767 (0x7FFF). DOCSIS specifications require up to a maximum of 64 equalizer taps (n + m); therefore, this object size can be up to 260 bytes (4 + 4x64). The minimum object size (other than zero) for a t-spaced tap with a minimum of 8 symbols will be 36 (4 + 4x8). See {{bibref|CM-SP-RFIv2.0|Figure 8-23}}. This data type defines the CM connectivity state as reported by the CM. {{enum}} See {{bibref|CM-SP-MULPIv3.0}}, Cable Modem - CMTS Interaction. indicates any state not described below indicates that the CM has not started the registration process yet indicates that the CM has not initiated or completed the synchronization of the downstream physical layer indicates that the CM has completed the synchronization of the downstream physical layer indicates that the CM has completed the upstream parameters acquisition or have completed the downstream and upstream service groups resolution, whether the CM is registering in a pre-3.0 or a 3.0 CMTS indicates that the CM has completed initial ranging and received a Ranging Status of success from the CMTS in the RNG-RSP message indicates that the CM has received a DHCPv4 ACK message from the CMTS indicates that the CM has successfully acquired time of day. If the ToD is acquired after the CM is operational, this value should not be reported indicates that the CM has successfully completed the BPI initialization process indicates that the CM has completed the config file download process indicates that the CM has successfully completed the Registration process with the CMTS indicates that the CM has completed all necessary initialization steps and is operational indicates that the CM has received a registration aborted notification from the CMTS indicates that the CM has sent an Auth Info message for EAE indicates that the CM has sent a DHCPv4 DISCOVER to gain IP connectivity indicates that the CM has sent an DHCPv6 Solicit message indicates that the CM has received a DHCPv6 Reply message from the CMTS indicates that the CM has sent a Registration Request (REG-REQ or REG-REQ-MP) indicates that the CM has started the BPI initialization process as indicated in the CM config file. If the CM already performed EAE, this state is skipped by the CM indicates that the registration process was completed, but the network access option in the received configuration file prohibits forwarding indicates that the CM is attempting to determine its MD-DS-SG indicates that the CM has initiated the ranging process indicates that the CM is instructed to mute all channels in the CM-CTRL-REQ message from CMTS This data type represents a sequence of spectral amplitudes. Each spectral amplitude value corresponds to a bin. The format of the bin measurement is as follows. Sequence of: : 4 bytes: ChCenterFreq :: The center frequency of the upstream channel. : 4 bytes: FreqSpan :: The width in Hz of the band across which the spectral amplitudes characterizing the channel are measured. : 4 bytes: NumberOfBins :: The number of data points or bins that compose the spectral data. The leftmost bin corresponds to the lower band edge, the rightmost bin corresponds to the upper band edge, and the middle bin center is aligned with the center frequency of the analysis span. : 4 bytes: :: BinSpacing The frequency separation between adjacent bin centers. It is derived from the frequency span and the number of bins or data points. The bin spacing is computed as: ::: BinSpacing = FrequencySpan/(NumberOfBins -1) ::The larger the number of bins the finer the resolution. : 4 bytes: ResolutionBW :: The resolution bandwidth or equivalent noise bandwidth of each bin. If spectral windowing is used (based on vendor implementation), the bin spacing and resolution bandwidth would not generally be the same. : n bytes: Amplitude (2 bytes * NumberOfBins) :: A sequence of two byte elements. Each element represents the spectral amplitudes in relation to the expected received signal power of a bin, in units of 0.01dB. That is, a test CMTS input signal with square-root raised-cosine spectrum, bandwidth equal to the expected received signal bandwidth, and power equal to the expected received signal power, which is present for the entire spectrum sampling period, will exhibit a spectrum measurement of 0 dB average power in each bin of the signal passband. Each bin element amplitude value format is 2's complement which provides a range of -327.68 dB to 327.67 dB amplitude value for the bin measurement. This object controls the windowing function which will be used when performing the discrete Fourier transform for the analysis. Note that all window functions may not be supported by all devices. If an attempt is made to set the object to an unsupported window function, an error of inconsistentValue will be returned. This data type represents a single TLV encoding. This first octet represents the Type of the TLV. The second octet represents an unsigned 8-bit Length of the subsequent Value part of the TLV. The remaining octets represent the value. The Value could be an atomic value or a sequence of one or more sub-TLVs. See {{bibref|CM-SP-MULPIv3.0}}, Common Radio Frequency Interface Encodings Annex. This data type defines the CM ranging state as reported by the CMTS. The enumerated values associated with the RangingState are: {{enum}} See {{bibref|CM-SP-MULPIv3.0}}, Cable Modem - CMTS Interaction. indicates any state not described below indicates that the CMTS has sent a ranging abort indicates that the CM ranging retry limit has exceeded indicates that the CMTS has sent a ranging success in the ranging response indicates that the CMTS has sent a ranging continue in the ranging response indicates that the T4 timer expired on the CM Represents one or more MoCA channel RF center frequencies using a hexadecimal encoded 64-bit mask. Bit 63 (the leftmost bit of the leftmost character) is the most significant bit (highest frequency), and bit 0 (the rightmost bit of the rightmost character) is the least significant bit (lowest frequency). Not all bits are valid MoCA channels. Each bit represents 25 MHz of spectrum, but the mapping from bits to frequencies varies with the MoCA version: * MoCA 1.0 and MoCA 1.1: bits 63 through 32 are not used, bit 31 represents 1575 MHz and bit 0 represents 800 MHz * MoCA 2.0 and MoCA 2.5: bit 63 represents 1975 MHz and bit 0 represents 400 MHz For example, a MoCA 1.0 or MoCA 1.1 interface would use 0x000000001FFFC000 to represent 1150 MHz through 1500 MHz. Note that the MoCA version is indicated by the {{param|HighestVersion}} parameter. Represents a MoCA Node ID. * MoCA 1.0 network can have a maximum of 8 MoCA Nodes, so Node ID is 0 to 7. * MoCA 1.1, MoCA 2.0, or MoCA 2.5 network can have a maximum of 16 MoCA Nodes, so Node ID is 0 to 15. Represents the transmit PHY rate in Mbps. Represents the MAC throughput in Kbps. Represents one decibel or 1 dB. Represents a measure of power in mW expressed in decibels, and calculated as follows: power = 10*log10( Vrms^2 / R * 1000 ) where Vrms is the root-mean-square Voltage of the received waveform and R is 75 ohms. Represents the subcarrier modulation. Binary string array (array of two hexadecimal characters) with 1 byte for each subcarrier. The value of each byte represents the subcarrier modulation for the corresponding subcarrier. See {{bibref|MoCAv2.0|section 14.3.6.3}} and {{bibref|MOCA20-MIB|Appendix A}} for the encoding of this parameter. Represents the MoCA Bands and sub-bands the device is configured to operate in or that the device supports. {{enum}} See {{bibref|MoCAv2.0|section 15}}. Represents the Power State defined by the MoCA2.0 specification. {{enum}} See {{bibref|MoCAv2.0|section 12}}. Power State M0: Active. Power State M1: Low Power Idle. Power State M2: Standby. Power State M3: Sleep. Represents the MoCA 2.0 PQOS Ingress Classification Rule. Represents the MoCA 2.0 primary or secondary channel, or MoCA 2.5 first, second, third, fourth, or fifth channel. Represents a type of MoCA Privacy. Cut-down version of SNMP RowStatus that supports only its "status" values, not its "control" values. The row is available for use by the managed device. The row exists in the Agent, but is unavailable for use by the managed device (see NOTE below); "notInService" has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device. The row exists in the Agent, but is missing information necessary in order to be available for use by the managed device, i.e., one or more required parameter in the row have not been populated. Not used. Not used. Not used. # The PSM breakpoint sub-carrier index in the range [0:4095], and # the value of the level of the PSM at this sub-carrier expressed in ''0.1 dBm/Hz'' with an offset of -140 dBm/Hz. Both values are represented as unsignedInt. {{bibref|G.9964|Clause 5.2}} defines limits on PSM breakpoint levels. Service Slice Type (SST). {{enum}} See {{bibref|3GPP-TS.23.501|Clause 5.15.2.2}}. 5G Enhanced Mobile Broadband Ultra-Reliable Low Latency Communications Massive IoT Vehicle to Everything High Speed Packet data Access (HSPA) 3GPP https://www.3gpp.org/technologies/keywords-acronyms/99-hspa 3GPP TS 23.003 3GPP CT WG4 https://www.3gpp.org/ftp/Specs/html-info/23003.htm 3GPP TS 23.501 3GPP SA WG2 https://www.3gpp.org/ftp/Specs/html-info/23501.htm 3GPP TS 24.008 3GPP CT WG1 https://www.3gpp.org/ftp/Specs/html-info/24008.htm 3GPP TS 24.301 3GPP CT WG1 https://www.3gpp.org/ftp/Specs/html-info/24301.htm 3GPP TS 24.501 3GPP CT WG1 https://www.3gpp.org/ftp/Specs/html-info/24501.htm 3GPP TS 24.526 3GPP CT WG1 https://www.3gpp.org/ftp/Specs/html-info/24526.htm 3GPP TS 25.171 3GPP RAN WG4 https://www.3gpp.org/ftp/Specs/html-info/25171.htm CM-SP-RFIv2.0 CableLabs April 2009 https://www.cablelabs.com/specifications CM-SP-MULPIv3.0 CableLabs December 2017 https://www.cablelabs.com/specifications CM-SP-OSSIv3.0 CableLabs December 2017 https://www.cablelabs.com/specifications CM-SP-CM-OSSIv3.1 CableLabs October 2020 https://www.cablelabs.com/specifications Organizationally Unique Identifiers (OUIs) https://standards.ieee.org/faqs/regauth Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority IEEE March 1997 https://standards.ieee.org/regauth/oui/tutorials/EUI64.html IEEE Std 802.1AB-2009 IEEE 2009 https://standards.ieee.org/getieee802/download/802.1AB-2009.pdf IEEE Std 802.1ad-2005 IEEE May 2005 https://standards.ieee.org/getieee802/download/802.1ad-2005.pdf IEEE Std 802.1AX-2014 IEEE 2014 https://ieeexplore.ieee.org/servlet/opac?punumber=6997981 IEEE Std 802.1D-2004 IEEE 2004 https://standards.ieee.org/getieee802/download/802.1D-2004.pdf IEEE Std 802.1Q-2005 IEEE 2006 https://standards.ieee.org/getieee802/download/802.1Q-2005.pdf IEEE Std 802.1Q-2011 IEEE 2011 https://standards.ieee.org/getieee802/download/802.1Q-2011.pdf IEEE Std 802.1x-2004 IEEE 2004 https://standards.ieee.org/getieee802/download/802.1X-2004.pdf IEEE Std 802.3-2015 IEEE 2015 https://ieeexplore.ieee.org/servlet/opac?punumber=7428774 IEEE 802.3-2012 - Section Six IEEE December 2012 https://standards.ieee.org/getieee802/download/802.3-2012_section6.pdf IEEE Std 802.11-2007 IEEE 2007 https://standards.ieee.org/getieee802/download/802.11-2007.pdf IEEE Std 802.11-2012 IEEE March 2012 https://standards.ieee.org/getieee802/download/802.11-2012.pdf IEEE Std 802.11-2016 IEEE December 2016 https://ieeexplore.ieee.org/document/7786995 IEEE Std 802.11-2020 IEEE December 2020 https://ieeexplore.ieee.org/document/9363693 IEEE Std 802.11a-1999 IEEE 1999 https://standards.ieee.org/getieee802/download/802.11a-1999.pdf IEEE Std 802.11ac-2013 IEEE December 2013 https://www.ieee802.org/11/Reports/tgac_update.htm IEEE Std 802.11ax IEEE May 2021 https://standards.ieee.org/standard/802_11ax-2021.html IEEE Std 802.11be IEEE March 2019 https://standards.ieee.org/ieee/802.11be/7516/ IEEE Std 802.11b-1999 IEEE 1999 https://standards.ieee.org/getieee802/download/802.11b-1999.pdf IEEE Std 802.11g-2003 IEEE 2003 https://standards.ieee.org/getieee802/download/802.11g-2003.pdf IEEE Std 802.11h-2003 IEEE 2003 https://standards.ieee.org/getieee802/download/802.11h-2003.pdf IEEE Std 802.11k IEEE May 2008 https://standards.ieee.org/standard/802_11k-2008.html IEEE Std 802.11n-2009 IEEE 2009 https://ieeexplore.ieee.org/xpl/freeabs_all.jsp?reload=true&arnumber=5307322 IEEE 1905.1a IEEE December 2014 https://www.IEEE.org TS 102 824 ETSI July 2008 https://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=27769 ETSI EN 301 893 ETSI https://www.etsi.org/deliver/etsi_en/301800_301899/301893/01.08.01_60/en_301893v010801p.pdf ETSI TS 102 690 v1.1.6 ETSI June 2012 https://docbox.etsi.org/M2M/Open/Latest_Drafts/00002ed121v116.pdf ETSI TS 102 921 v1.1.6 ETSI August 2012 https://docbox.etsi.org/M2M/Open/Latest_Drafts/00010ed121v116.pdf ITU E.118 International Telecommunication Union May 2006 https://www.itu.int/rec/T-REC-E.118-200605-I/en ITU E.164 International Telecommunication Union October 2010 https://www.itu.int/rec/T-REC-E.164-201011-I/en G.984.3 ITU-T January 2010 https://www.itu.int/rec/T-REC-G.984.3-201401-I/en G.987.3 ITU-T January 2014 https://www.itu.int/rec/T-REC-G.987.3-201401-I/en G.988 ITU-T 2010 https://www.itu.int/rec/T-REC-G.988-201010-P/en G.989.3 ITU-T May 2021 https://www.itu.int/rec/T-REC-G.989.3-202105-I/en G.992.3 ITU-T https://www.itu.int/rec/T-REC-G.992.3 G.992.4 ITU-T https://www.itu.int/rec/T-REC-G.992.4 G.992.5 ITU-T https://www.itu.int/rec/T-REC-G.992.5 G.993.1 ITU-T https://www.itu.int/rec/T-REC-G.993.1 G.993.2 ITU-T https://www.itu.int/rec/T-REC-G.993.2 G.994.1 ITU-T https://www.itu.int/rec/T-REC-G.994.1 G.996.2 ITU-T https://www.itu.int/rec/T-REC-G.996.2 G.997.1 ITU-T https://www.itu.int/rec/T-REC-G.997.1 G.997.2 ITU-T 2015 https://www.itu.int/rec/T-REC-G.997.2-201505-I G.998.1 ITU-T 2005 https://www.itu.int/rec/T-REC-G.998.1 G.998.2 ITU-T 2005 https://www.itu.int/rec/T-REC-G.998.2 G.998.3 ITU-T 2005 https://www.itu.int/rec/T-REC-G.998.2 G.9807.1 ITU-T June 2016 https://www.itu.int/rec/T-REC-G.9807.1-201606-I/en G.9954 ITU-T 2007 https://www.itu.int/rec/T-REC-G.9954/en G.9960 ITU-T G.hn series https://www.itu.int/rec/T-REC-G.9960-201006-P G.9961 ITU-T G.hn series https://www.itu.int/rec/T-REC-G.9961-201006-P G.9962 ITU-T G.hn series https://www.itu.int/rec/T-REC-G.9962-201308-P G.9964 ITU-T G.hn series https://www.itu.int/rec/T-REC-G.9962-201308-P G.9973 ITU-T 2011 https://www.itu.int/rec/T-REC-G.9973-201110-I/en G.9701 ITU-T 2014 https://www.itu.int/rec/T-REC-G.9701-201412-P ITU X.733 International Telecommunication Union February 1992 https://www.itu.int/rec/T-REC-X.733/en IANAifType IANA 2009 https://www.iana.org/assignments/ianaiftype-mib/ianaiftype-mib IANAMauMIB IANA 2022 https://www.iana.org/assignments/ianamau-mib/ianamau-mib IANA IP Version Numbers IANA https://www.iana.org/assignments/version-numbers IANA Protocol Numbers IANA https://www.iana.org/assignments/protocol-numbers IANA Uniform Resource Identifier (URI) Schemes Registry IANA https://www.iana.org/assignments/uri-schemes IKEv2 Parameters IANA https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xml ISO/IEC 13818-6:1998 ISO 1998 https://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=25039 ISO 639-1 ISO 2002 https://www.iso.org/iso/language_codes ISO/IEC 646-1991 ISO 1991 ISO 3166-1 ISO 2006 https://www.iso.org/iso/country_codes.htm draft-ietf-ippm-metric-registry-12 IETF Internet Draft June 30, 2017 https://datatracker.ietf.org/doc/html/draft-ietf-ippm-metric-registry RFC 7648 IETF RFC September 2015 https://www.rfc-editor.org/rfc/rfc7648 RFC 792 IETF RFC September 1981 https://www.rfc-editor.org/rfc/rfc792 RFC 793 IETF RFC September 1981 https://www.rfc-editor.org/rfc/rfc793 RFC 862 IETF RFC 1983 https://www.rfc-editor.org/rfc/rfc862 RFC 959 IETF RFC 1985 https://www.rfc-editor.org/rfc/rfc958 RFC 1035 IETF RFC 1987 https://www.rfc-editor.org/rfc/rfc1035 RFC 1123 IETF RFC 1989 https://www.rfc-editor.org/rfc/rfc1123 RFC 1323 IETF RFC May 1992 https://www.rfc-editor.org/rfc/rfc1323 RFC 1332 IETF 1992 https://www.rfc-editor.org/rfc/rfc1332 RFC 1378 IETF RFC 1992 https://www.rfc-editor.org/rfc/rfc1378 RFC 1552 IETF RFC 1993 https://www.rfc-editor.org/rfc/rfc1552 RFC 1661 IETF 1994 https://www.rfc-editor.org/rfc/rfc1661 RFC 1877 IETF 1995 https://www.rfc-editor.org/rfc/rfc1877 RFC 1974 IETF 1996 https://www.rfc-editor.org/rfc/rfc1974 RFC 2080 IETF RFC 1997 https://www.rfc-editor.org/rfc/rfc2080 RFC 2097 IETF RFC 1997 https://www.rfc-editor.org/rfc/rfc2097 RFC 2104 IETF RFC 1997 https://www.rfc-editor.org/rfc/rfc2104 RFC 2131 IETF RFC https://www.rfc-editor.org/rfc/rfc2131 RFC 2132 IETF RFC https://www.rfc-editor.org/rfc/rfc2132 RFC 2225 IETF RFC https://www.rfc-editor.org/rfc/rfc2225 RFC 2364 IETF 1998 https://www.rfc-editor.org/rfc/rfc2364 RFC 2474 IETF RFC https://www.rfc-editor.org/rfc/rfc2474 RFC 2581 IETF RFC April 1999 https://www.rfc-editor.org/rfc/rfc2581 RFC 2582 IETF RFC April 1999 https://www.rfc-editor.org/rfc/rfc2582 RFC 2616 IETF RFC 1999 https://www.rfc-editor.org/rfc/rfc2616 RFC 2684 IETF RFC https://www.rfc-editor.org/rfc/rfc2684 RFC 2697 IETF RFC https://www.rfc-editor.org/rfc/rfc2697 RFC 2698 IETF RFC https://www.rfc-editor.org/rfc/rfc2698 RFC 2782 IETF RFC 2000 https://www.rfc-editor.org/rfc/rfc2782 RFC 2784 IETF RFC November 2000 https://www.rfc-editor.org/rfc/rfc2784 RFC 2818 IETF RFC May 2000 https://www.rfc-editor.org/rfc/rfc2818 RFC 2819 IETF 2000 RFC 2863 IETF 2000 https://www.rfc-editor.org/rfc/rfc2863 RFC 2865 IETF 2000 https://www.rfc-editor.org/rfc/rfc2865 RFC 2866 IETF RFC 2000 RFC 2869 IETF RFC 2000 RFC 2890 IETF RFC November 2000 https://www.rfc-editor.org/rfc/rfc2890 RFC 2898 IETF RFC https://www.rfc-editor.org/rfc/rfc2898 RFC 2974 IETF RFC October 2000 https://www.rfc-editor.org/rfc/rfc2974 RFC 3004 IETF RFC https://www.rfc-editor.org/rfc/rfc3004 RFC 3066 IETF RFC https://www.rfc-editor.org/rfc/rfc3066 RFC 3174 IETF Draft Standard September, 2001 https://www.rfc-editor.org/rfc/rfc3174 RFC 3232 IETF RFC 2002 https://www.rfc-editor.org/rfc/rfc3232 RFC 3315 IETF RFC 2003 https://www.rfc-editor.org/rfc/rfc3315 RFC 3339 IETF Draft Standard July, 2002 https://www.rfc-editor.org/rfc/rfc3339 RFC 3489 IETF RFC https://www.rfc-editor.org/rfc/rfc3489 RFC 3596 IETF RFC 2003 https://www.rfc-editor.org/rfc/rfc3596 RFC 3633 IETF RFC 2003 https://www.rfc-editor.org/rfc/rfc3633 RFC 3646 IETF RFC 2003 https://www.rfc-editor.org/rfc/rfc3646 RFC 3775 IETF RFC 2004 https://www.rfc-editor.org/rfc/rfc3775 RFC 3925 IETF RFC https://www.rfc-editor.org/rfc/rfc3925 RFC 3926 IETF RFC October 2004 https://www.rfc-editor.org/rfc/rfc3926 RFC 3927 IETF 2005 https://www.rfc-editor.org/rfc/rfc3927 RFC 3931 IETF RFC March 2005 RFC 3948 IETF RFC January 2005 https://www.rfc-editor.org/rfc/rfc3948 RFC 3986 IETF RFC https://www.rfc-editor.org/rfc/rfc3986 RFC 4007 IETF RFC https://www.rfc-editor.org/rfc/rfc4007 RFC 4122 IETF RFC 2005 https://www.rfc-editor.org/rfc/rfc4122 RFC4180 IETF RFC October 2005 https://www.rfc-editor.org/rfc/rfc4180 RFC 4191 IETF RFC 2005 https://www.rfc-editor.org/rfc/rfc4191 RFC 4193 IETF RFC 2005 https://www.rfc-editor.org/rfc/rfc4193 RFC 4242 IETF RFC 2005 https://www.rfc-editor.org/rfc/rfc4242 RFC 4291 IETF RFC 2006 https://www.rfc-editor.org/rfc/rfc4291 RFC 4292 IETF RFC 2006 https://www.rfc-editor.org/rfc/rfc4292 RFC 4293 IETF RFC 2006 https://www.rfc-editor.org/rfc/rfc4293 RFC 4301 IETF December 2005 https://www.rfc-editor.org/rfc/rfc4301 RFC 4302 IETF RFC December 2005 https://www.rfc-editor.org/rfc/rfc4302 RFC 4303 IETF RFC December 2005 https://www.rfc-editor.org/rfc/rfc4303 RFC 4389 IETF RFC 2006 https://www.rfc-editor.org/rfc/rfc4389 RFC 4443 IETF RFC March 2006 https://www.rfc-editor.org/rfc/rfc4443 RFC 4546 IETF RFC June 2006 https://www.rfc-editor.org/rfc/rfc4546 RFC 4632 IETF 2006 https://www.rfc-editor.org/rfc/rfc4632 RFC 4719 IETF RFC November 2006 RFC 4835 IETF RFC 2007 https://www.rfc-editor.org/rfc/rfc4835 RFC 4861 IETF RFC 2007 https://www.rfc-editor.org/rfc/rfc4861 RFC 4862 IETF RFC 2007 https://www.rfc-editor.org/rfc/rfc4862 RFC 4868 IETF RFC 2007 https://www.rfc-editor.org/rfc/rfc4868 RFC 5072 IETF RFC 2007 https://www.rfc-editor.org/rfc/rfc5072 RFC 5139 IETF February 2008 https://www.rfc-editor.org/rfc/rfc5139 RFC 5280 IETF May 2008 https://www.rfc-editor.org/rfc/rfc5280 RFC 5424 IETF May 2009 https://www.rfc-editor.org/rfc/rfc5424 RFC 5425 IETF May 2009 https://www.rfc-editor.org/rfc/rfc5425 RFC 5426 IETF May 2009 https://www.rfc-editor.org/rfc/rfc5425 RFC 5491 IETF March 2009 https://www.rfc-editor.org/rfc/rfc5491 RFC 5625 IETF 2009 https://www.rfc-editor.org/rfc/rfc5625 RFC 5905 IETF RFC 2010 https://www.rfc-editor.org/rfc/rfc5905 RFC 5969 IETF RFC 2010 https://www.rfc-editor.org/rfc/rfc5969 RFC 5996 IETF RFC September 2010 https://www.rfc-editor.org/rfc/rfc5996 RFC 6106 IETF RFC 2010 https://www.rfc-editor.org/rfc/rfc6106 RFC 6120 IETF 2011 https://www.rfc-editor.org/rfc/rfc6120 RFC 6234 IETF Draft Standard May, 2011 https://www.rfc-editor.org/rfc/rfc6234 RFC 6333 IETF RFC 2011 RFC 6334 IETF RFC 2011 RFC 6455 IETF RFC December 2011 https://www.rfc-editor.org/rfc/rfc6455 RFC 6587 IETF RFC April 2012 https://www.rfc-editor.org/rfc/rfc6587 RFC 6762 IETF RFC February 2013 https://www.rfc-editor.org/rfc/rfc6762 RFC 6763 IETF RFC 2013 https://www.rfc-editor.org/rfc/rfc6763 RFC 6838 IETF Best Current Practice January 2013 https://www.rfc-editor.org/rfc/rfc6838 RFC 6887 IETF 2013 https://www.rfc-editor.org/rfc/rfc6887 RFC 6970 IETF 2013 https://www.rfc-editor.org/rfc/rfc6970 RFC7159 IETF RFC March 2014 https://www.rfc-editor.org/rfc/rfc7159 RFC 7230 IETF RFC June 2014 https://www.rfc-editor.org/rfc/rfc7230 RFC 7252 IETF RFC June 2014 https://www.rfc-editor.org/rfc/rfc7252 RFC 7291 IETF RFC July 2014 https://www.rfc-editor.org/rfc/rfc7291 RFC 7348 IETF RFC August 2014 RFC 7395 IETF Standards Track October 2014 https://www.rfc-editor.org/rfc/rfc7395 RFC 7398 IETF Informational RFC February 2015 https://www.rfc-editor.org/rfc/rfc7398 RFC 7468 IETF Standards Track April 2015 https://www.rfc-editor.org/rfc/rfc7468 RFC 7594 IETF Informational RFC September 2015 https://www.rfc-editor.org/rfc/rfc7594 RFC 7597 IETF RFC July 2015 https://www.rfc-editor.org/rfc/rfc7597 RFC 7598 IETF RFC July 2015 https://www.rfc-editor.org/rfc/rfc7598 RFC 7599 IETF RFC July 2015 https://www.rfc-editor.org/rfc/rfc7599 RFC 7616 IETF RFC September 2015 https://www.rfc-editor.org/rfc/rfc7616 RFC 7617 IETF RFC September 2015 https://www.rfc-editor.org/rfc/rfc7617 RFC 7693 IETF RFC November 2015 https://www.rfc-editor.org/rfc/rfc7693 RFC 8089 IETF RFC February 2017 https://www.rfc-editor.org/rfc/rfc8089 RFC 8106 IETF RFC March 2017 https://www.rfc-editor.org/rfc/rfc8106 RFC 8141 IETF RFC April 2017 https://www.rfc-editor.org/rfc/rfc8141 RFC 8193 IETF Informational RFC August 2017 https://www.rfc-editor.org/rfc/rfc8193 RFC 8325 IETF Proposed Standard February 2018 https://www.rfc-editor.org/rfc/rfc8325 RFC 8349 IETF RFC March 2018 https://www.rfc-editor.org/rfc/rfc8349 RFC 8822 IETF RFC April 2021 https://www.rfc-editor.org/rfc/rfc8822 RFC 8966 IETF Proposed Standard January 2021 https://www.rfc-editor.org/info/rfc8966 RFC 8967 IETF Proposed Standard January 2021 https://www.rfc-editor.org/info/rfc8967 RFC 8968 IETF Proposed Standard January 2021 https://www.rfc-editor.org/info/rfc8968 RFC 9046 IETF Informational June 2021 https://www.rfc-editor.org/info/rfc9046 RFC 9110 IETF RFC June 2022 https://www.rfc-editor.org/rfc/rfc9110 RFC 9249 IETF RFC July 2022 https://www.rfc-editor.org/rfc/rfc9249 draft-ietf-netmod-syslog-model IETF Internet Draft April 2023 https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model TR-064 Corrigendum 1 Broadband Forum TR August 2015 TR-069 Amendment 6 Broadband Forum TR April 2018 TR-106 Amendment 8 Broadband Forum TR May 2018 TR-124 Issue 5 Broadband Forum TR July 2016 TR-124 Issue 6 Broadband Forum TR July 2020 TR-143 Amendment 1 Corrigendum 1 Broadband Forum TR August 2015 TR-159 Broadband Forum TR December 2008 TR-181 Issue 2 Amendment 15 Broadband Forum TR January 2022 TR-232 Broadband Forum Technical Report May 2012 TR-262 Broadband Forum TR November 2011 TR-304 Broadband Forum Technical Report February 2015 TR-369 Issue 1 Amendment 2 Broadband Forum Technical Report January 2022 https://usp.technology/specification TR-390 Broadband Forum Technical Report May 2017 TR-471 Broadband Forum Technical Report December 2023 https://www.broadband-forum.org/download/TR-471_Issue-4.pdf Agile MultiBand Specification Wi-Fi Alliance December 2018 https://www.wi-fi.org/discover-wi-fi/specifications Data Elements Specification Wi-Fi Alliance 2024 https://www.wi-fi.org/discover-wi-fi/specifications Wi-Fi Easy Connect Specification Wi-Fi Alliance November 2022 https://www.wi-fi.org/discover-wi-fi/specifications EasyMesh Specification Wi-Fi Alliance August 2024 https://www.wi-fi.org/discover-wi-fi/specifications Wi-Fi Multimedia Technical Specification Wi-Fi Alliance May 2012 https://www.wi-fi.org/discover-wi-fi/specifications Wi-Fi Protected Setup Specification Version 1.0h 2006 https://www.wi-fi.org/discover-wi-fi/specifications WSC 2.0 Wi-Fi Alliance https://www.wi-fi.org/discover-wi-fi/specifications WPA3v3.0 Wi-Fi Alliance https://www.wi-fi.org/discover-wi-fi/specifications Blue https://en.wikipedia.org/wiki/Blue_(queue_management_algorithm) BPF FreeBSD.org October 2016 https://www.freebsd.org/cgi/man.cgi?query=bpf DLNA Networked Device Interoperability Guidelines DLNA October 2006 https://www.dlna.org/industry/certification/guidelines/ HomePlug™ AV Specification HomePlug Alliance 2007 https://en.wikipedia.org/wiki/HomePlug HTML 4.01 Specification W3C https://www.w3.org/TR/html4 ICSA Baseline Modular Firewall Certification Criteria ICSA Labs 2008 https://www.icsalabs.com/sites/default/files/baseline.pdf ICSA Residential Modular Firewall Certification Criteria ICSA Labs 2008 https://www.icsalabs.com/sites/default/files/residential.pdf IPDR File Transfer Protocol TM Forum https://www.tmforum.org/ipdr/ IPDR Streaming Protocol TM Forum https://www.tmforum.org/ipdr/ IPDR XDR Encoding Format TM Forum https://www.tmforum.org/ipdr/ IPDR XML File Encoding Format TM Forum https://www.tmforum.org/ipdr/ JJ-300.00 TTC 2017 https://www.ttc.or.jp/application/files/1115/5443/0461/JJ-300.00Ev3.pdf JJ-300.01 TTC 2018 https://www.ttc.or.jp/application/files/8315/5443/0461/JJ-300.01Ev2.1.pdf Libpcap Wireshark 2015 https://wiki.wireshark.org/Development/LibpcapFileFormat MoCA v1.0 MoCA Alliance 2009 https://www.mocalliance.org MoCA v1.1 MoCA Alliance 2009 https://www.mocalliance.org MoCA v2.0 MoCA Alliance 2017 https://www.mocalliance.org https://www.mocalliance.org MoCA v2.5 MoCA Alliance 2017 https://www.mocalliance.org https://www.mocalliance.org MOCA11-MIB MoCA Alliance 2009 https://www.mocalliance.org MOCA20-MIB MoCA Alliance 2020 https://www.mocalliance.org https://www.mocalliance.org MOCA25-MIB MoCA Alliance 2018 https://www.mocalliance.org https://www.mocalliance.org MQTT v3.1 2010 https://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html MQTT Version 3.1.1 OASIS Message Queuing Telemetry Transport (MQTT) TC October 2014 https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html MQTT Version 5.0 OASIS Message Queuing Telemetry Transport (MQTT) TC February 2019 https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html References on RED (Random Early Detection) Queue Management http://www.icir.org/floyd/red.html ISO/IEC/IEEE 9945 ISO/IEC/IEEE September 2009 https://ieeexplore.ieee.org/xpl/mostRecentIssue.jsp?punumber=4694974 SFF-8024 SNIA May 2021 https://members.snia.org/document/dl/26423 SFF-8472 SNIA March 2021 https://members.snia.org/document/dl/25916 Simple Object Access Protocol (SOAP) 1.1 W3C https://www.w3.org/TR/2000/NOTE-SOAP-20000508 STOMP Protocol Specification https://stomp.github.io/stomp-specification-1.2.html Universal Powerline Association UPA https://www.upaplc.org UPnP Device Architecture UPnP Forum April 2008 http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20080424.pdf UPnP Device Architecture 1.1 UPnP Forum October, 2008 http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf UPnP Device Management:1 https://openconnectivity.org/developer/specifications/upnp-resources/upnp/device-management1-2 UPnP InternetGatewayDevice:1 UPnP SDCP 2001 http://upnp.org/specs/gw/UPnP-gw-InternetGatewayDevice-v1-Device.pdf UPnP InternetGatewayDevice:2 UPnP SDCP 2010 http://upnp.org/specs/gw/UPnP-gw-InternetGatewayDevice-v2-Device.pdf USB 1.0 USB-IF January 1996 https://www.usb.org/documents USB 2.0 USB-IF April 2000 https://www.usb.org/documents USB 3.0 USB-IF November 2008 https://www.usb.org/documents Z-Wave https://www.z-wave.com ZigBee https://csa-iot.org/all-solutions/zigbee ZigBee 2007 Specification ZigBee Alliance October 2007 https://csa-iot.org/all-solutions/zigbee