Allow incoming IP connections from any IPv4 address. The source prefixes defined in {{param|IPv4AllowedSourcePrefix}} will be ignored. Allow only incoming IP connections from the provided list of IPv4 prefixes. When {{param}} is set to {{empty}} and {{param|AllowAllIPv4}} is set to ''false'', no incoming IP connections are allowed. When {{param|AllowAllIPv4}} is set ''true'', {{param}} is ignored. Allow incoming IP connections from any IPv6 address. The source prefixes defined in {{param|IPv6AllowedSourcePrefix}} will be ignored. Allow only incoming IP connections from the provided list of IPv6 prefixes. When {{param}} is set to {{empty}} and {{param|AllowAllIPv6}} is set to ''false'', no incoming IP connections are allowed. When {{param|AllowAllIPv6}} is set ''true'', {{param}} is ignored. Specifies the IP protocol version, following the definitions in {{bibref|IANA-ipversionnumbers}}. Valid values are: {{range}}. IPv4 IPv6 No specific IP version is required {{reference}} The layer 2 or layer 3 interface over which the test is to be performed. Example: ''Device.IP.Interface.1'', ''Device.Bridge.1.Port.2'' {{template|INTERFACE-ROUTING}} Indicates the IP protocol to be used. Use either IPv4 or IPv6 depending on the system preference Use IPv4 for the Ping requests Use IPv6 for the Ping requests Host name or address of the host to ping. In the case where {{param}} is specified by name, and the name resolves to more than one address, it is up to the device implementation to choose which address to use. Number of repetitions of the ping test to perform before reporting the results. Timeout in {{units}} for the ping test. Size of the data block in bytes to be sent for each ping. DiffServ codepoint to be used for the test packets. By default the CPE SHOULD set this value to zero. Indicates which IP address was used to send the Ping request. The parameter is only valid if the {{param|DiagnosticsState}} is {{enum|Complete|DiagnosticsState}}. Result parameter indicating the number of successful pings (those in which a successful response was received prior to the timeout) in the most recent ping test. Result parameter indicating the number of failed pings in the most recent ping test. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent ping test. If there were no successful responses, this value MUST be zero. {{reference}} The layer 2 or layer 3 interface over which the test is to be performed. Example: ''Device.IP.Interface.1'', ''Device.Bridge.1.Port.2'' {{template|INTERFACE-ROUTING}} Indicates the IP protocol to be used. Use either IPv4 or IPv6 depending on the system preference Use IPv4 for the TraceRoute Use IPv6 for the TraceRoute Host name or address of the host to find a route to. In the case where {{param}} is specified by name, and the name resolves to more than one address, it is up to the device implementation to choose which address to use. Number of tries per hop. Set prior to running Diagnostic. By default, the CPE SHOULD set this value to 3. Timeout in {{units}} for each hop of 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. {{numentries}} Indicates which IP address was used for TraceRoute. The parameter is only valid if the {{param|DiagnosticsState}} is {{enum|Complete|DiagnosticsState}}. Result parameter indicating the response time in {{units}} the most recent trace route test. If a route could not be determined, this value MUST be zero. Contains the array of hop 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|Host}} 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. {{list}} Each list item contains one or more round trip times in {{units}} (one for each repetition) for this hop. A list item of 0 indicates that the corresponding response was not received. Round trip times of less than 1 {{units}} MUST be rounded up to 1. The number of list entries is determined by the value of {{param|#.NumberOfTries}}. Supported ''DownloadDiagnostics'' transport protocols for a CPE device. Indicates the maximum number of connections that are supported by Download Diagnostics. The maximum number of rows in {{object|IncrementalResult}} that the CPE will store. {{reference}} The IP-layer interface over which the test is to be performed. Example: Device.IP.Interface.1 {{template|INTERFACE-ROUTING}} The {{datatype}} for the CPE to perform the download on. This parameter MUST be in the form of a valid HTTP {{bibref|RFC2616}} or FTP {{bibref|RFC959}} 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. Note: For time based tests ({{param|TimeBasedTestDuration}} > 0) the Controller MAY add a hint to duration of the test to the URL. See {{bibref|TR-143|Section 4.3}} for more details. The DiffServ code point for marking packets transmitted in the test. The default value SHOULD be zero. Ethernet priority code for marking packets transmitted in the test (if applicable). The default value SHOULD be zero. Controls time based testing {{bibref|TR-143|Section 4.3}}. When {{param}} > 0, {{param}} is the duration in {{units}} of a time based test. If {{param}} is 0, the test is not based on time, but on the size of the file to be downloaded. The default value SHOULD be 0. The measurement interval duration in {{units}} for objects in {{object|IncrementalResult}} for a time based FTP/HTTP download test (when {{param|TimeBasedTestDuration}} > 0). The default value SHOULD be 0, which implies {{object|IncrementalResult}} collection is disabled. For example if {{param|TimeBasedTestDuration}} is 90 {{units}} and {{param}} is 10 {{units}}, there will be 9 results in {{object|IncrementalResult}}, each with a 10 {{units}} duration. This {{param}} works in conjunction with {{param|TimeBasedTestMeasurementInterval}} to allow the interval measurement to start a number of {{units}} after {{param|BOMTime}}. The test measurement interval in {{object|IncrementalResult}} starts at time {{param|BOMTime}} + {{param}} to allow for slow start window removal of file transfers. This {{param}} is in {{units}}. The default value SHOULD be 0. Indicates the IP protocol version to be used. The default value SHOULD be {{enum|Any}}. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests Use IPv6 for the requests. The number of connections to be used in the test. The default value SHOULD be 1. {{param}} MUST NOT be set to a value greater than {{param|DownloadDiagnosticMaxConnections}}. The results must be returned in the {{object|PerConnectionResult}} table for every connection when set to {{true}}. The default value SHOULD be {{false}}. {{numentries}} {{numentries}} Indicates which IP address was used to send the request. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the client sends the GET command. * For FTP this is the time at which the client sends the RTRV command. If multiple connections are used, then {{param}} is set to the earliest {{param}} across all connections. Begin of transmission time in UTC, which MUST be specified to microsecond precision For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the first data packet is received. * For FTP this is the time at which the client receives the first data packet on the data connection. If multiple connections are used, then {{param}} is set to the earliest {{param}} across all connections. End of transmission in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the last data packet is received. * For FTP this is the time at which the client receives the last packet on the data connection. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. The number of {{units}} received during the FTP/HTTP transaction including FTP/HTTP headers, between {{param|BOMTime}} and {{param|EOMTime}} across all connections. The total number of {{units}} (at the IP layer) received on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.BytesReceived on the {{param|Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. If {{param|Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The total number of {{units}} (at the IP layer) sent on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.BytesSent on the {{param|Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. If {{param|Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The number of {{units}} of the test file received between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} across all connections. The total number of {{units}} (at the IP layer) received in between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}}. This MAY be calculated by sampling Stats.BytesReceived on the {{param|Interface}} object at the latest {{param|PerConnectionResult.{i}.BOMTime}} and at the earliest {{param|PerConnectionResult.{i}.EOMTime}} and subtracting. The total number of {{units}} (at the IP layer) sent between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}}. This MAY be calculated by sampling Stats.BytesSent on the {{param|Interface}} object at the latest {{param|PerConnectionResult.{i}.BOMTime}} and at the earliest {{param|PerConnectionResult.{i}.EOMTime}} and subtracting. The period of time in {{units}} between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} of the test. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP socket open (SYN) was sent for the HTTP connection. * For FTP this is the time at which the TCP socket open (SYN) was sent for the data connection. Note: Interval of 1 microsecond SHOULD be supported. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. Response time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP ACK to the socket opening the HTTP connection was received. * For FTP this is the time at which the TCP ACK to the socket opening the data connection was received. Note: Interval of 1 microsecond SHOULD be supported. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. Results for individual connections. This table is only populated when {{param|#.EnablePerConnectionResults}} is {{true}}. A new object is created for each connection specified in {{param|#.NumberOfConnections}}. Instance numbers MUST start at 1 and sequentially increment as new instances are created. All instances are removed when {{param|#.DiagnosticsState}} is set to {{enum|Requested|#.DiagnosticsState}} or {{enum|None|#.DiagnosticsState}}. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the client sends the GET command. * For FTP this is the time at which the client sends the RTRV command. Begin of transmission time in UTC, which MUST be specified to microsecond precision For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the first data packet is received. * For FTP this is the time at which the client receives the first data packet on the data connection. End of transmission in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the last data packet is received. * For FTP this is the time at which the client receives the last packet on the data connection. The number of {{units}} of the test file received during the FTP/HTTP transaction including FTP/HTTP headers, between {{param|BOMTime}} and {{param|EOMTime}}. The total number of {{units}} (at the IP layer) received on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.BytesReceived on the {{param|#.Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. The total number of {{units}} (at the IP layer) sent on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.BytesSent on the {{param|#.Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP socket open (SYN) was sent for the HTTP connection. * For FTP this is the time at which the TCP socket open (SYN) was sent for the data connection. Response time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP ACK to the socket opening the HTTP connection was received. * For FTP this is the time at which the TCP ACK to the socket opening the data connection was received. Results for time segmented tests (tests where {{param|#.TimeBasedTestDuration}} > 0 and {{param|#.TimeBasedTestMeasurementInterval}} > 0). This data is totaled across all connections in the test. A new object is created every {{param|#.TimeBasedTestMeasurementInterval}} after that interval has completed. Instance numbers MUST start at 1 and sequentially increment as new instances are created. All instances are removed when {{param|#.DiagnosticsState}} is set to {{enum|Requested|#.DiagnosticsState}} or {{enum|None|#.DiagnosticsState}}. Change in the value of {{param|#.TestBytesReceivedUnderFullLoading}} between {{param|StartTime}} and {{param|EndTime}}, measured in {{units}}. The total number of {{units}} (at the IP layer) received on the Interface between {{param|StartTime}} and {{param|EndTime}}. This MAY be calculated by sampling Stats.BytesReceived on the {{param|#.Interface}} object at {{param|StartTime}} and at {{param|EndTime}} and subtracting. If {{param|#.Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The total number of {{units}} (at the IP layer) sent on the Interface between {{param|StartTime}} and {{param|EndTime}}. This MAY be calculated by sampling Stats.BytesSent on the {{param|#.Interface}} object at {{param|StartTime}} and at {{param|EndTime}} and subtracting. If {{param|#.Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The start time of this interval which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z The end time of this interval which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z Supported ''UploadDiagnostics'' transport protocols for a CPE device. Indicates the maximum number of connections that are supported by Upload Diagnostics. The maximum number of rows in {{object|IncrementalResult}} that the CPE will store. {{reference}} The IP-layer interface over which the test is to be performed. Example: Device.IP.Interface.1 {{template|INTERFACE-ROUTING}} The {{datatype}} for the CPE to Upload to. This parameter MUST be in the form of a valid HTTP {{bibref|RFC2616}} or FTP {{bibref|RFC959}} 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. DiffServ code point for marking packets transmitted in the test. The default value SHOULD be zero. Ethernet priority code for marking packets transmitted in the test (if applicable). The default value SHOULD be zero. The size of the file {{units}} to be uploaded to the server. The CPE MUST insure the appropriate number of bytes are sent. Controls time based testing {{bibref|TR-143|Section 4.3}}. When {{param}} > 0, {{param}} is the duration in {{units}} of a time based test. If {{param}} is 0, the test is not based on time, but on the size of the file to be uploaded. The default value SHOULD be 0. The measurement interval duration in {{units}} for objects in {{object|IncrementalResult}} for a time based FTP/HTTP upload test (when {{param|TimeBasedTestDuration}} > 0). The default value SHOULD be 0, which implies {{object|IncrementalResult}} collection is disabled. For example if {{param|TimeBasedTestDuration}} is 90 {{units}} and {{param}} is 10 {{units}}, there will be 9 results in {{object|IncrementalResult}}, each with a 10 {{units}} duration. This {{param}} works in conjunction with {{param|TimeBasedTestMeasurementInterval}} and allows the interval measurement to start a number of {{units}} after {{param|BOMTime}}. The test measurement interval in {{object|IncrementalResult}} starts at time {{param|BOMTime}} + {{param}} to allow for slow start window removal of file transfers. This {{param}} is in {{units}}. The default value SHOULD be 0. Indicates the IP protocol version to be used. The default value SHOULD be {{enum|Any}}. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests Use IPv6 for the requests. The number of connections to be used in the test. The default value SHOULD be 1. {{param}} MUST NOT be set to a value greater than {{param|UploadDiagnosticsMaxConnections}}. The results must be returned in the {{object|PerConnectionResult}} table for every connection when set to {{true}}. The default value SHOULD be {{false}}. {{numentries}} {{numentries}} Indicates which IP address was used to send the request. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the client sends the GET command. * For FTP this is the time at which the client sends the RTRV command. If multiple connections are used, then {{param}} is set to the earliest {{param}} across all connections. Begin of transmission time in UTC, which MUST be specified to microsecond precision For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the first data packet is received. * For FTP this is the time at which the client receives the first data packet on the data connection. If multiple connections are used, then {{param}} is set to the earliest {{param}} across all connections. End of transmission in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the last data packet is received. * For FTP this is the time at which the client receives the last packet on the data connection. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. The number of {{units}} of the test file sent during the FTP/HTTP transaction including FTP/HTTP headers, between {{param|BOMTime}} and {{param|EOMTime}} across all connections. The total number of {{units}} (at the IP layer) received on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.BytesReceived on the {{param|Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. If {{param|Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The total number of {{units}} (at the IP layer) sent on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.BytesSent on the {{param|Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. If {{param|Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The number of {{units}} of the test file sent between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} across all connections. The total number of {{units}} (at the IP layer) received between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} across all connections in the test. This MAY be calculated by sampling Stats.BytesReceived on the {{param|Interface}} object at the latest {{param|PerConnectionResult.{i}.BOMTime}} and at the earliest {{param|PerConnectionResult.{i}.EOMTime}} and subtracting. If {{param|Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The total number of {{units}} (at the IP layer) sent between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} across all connections in the test. This MAY be calculated by sampling Stats.BytesSent on the {{param|Interface}} object at the latest {{param|PerConnectionResult.{i}.BOMTime}} and at the earliest {{param|PerConnectionResult.{i}.EOMTime}} and subtracting. If {{param|Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The period of time in {{units}} between the latest {{param|PerConnectionResult.{i}.BOMTime}} and the earliest {{param|PerConnectionResult.{i}.EOMTime}} of the test. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP socket open (SYN) was sent for the HTTP connection. * For FTP this is the time at which the TCP socket open (SYN) was sent for the data connection. Note: Interval of 1 microsecond SHOULD be supported. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. Response time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP ACK to the socket opening the HTTP connection was received. * For FTP this is the time at which the TCP ACK to the socket opening the data connection was received. Note: Interval of 1 microsecond SHOULD be supported. If multiple connections are used, then {{param}} is set to the latest {{param}} across all connections. Results for individual connections. This table is only populated when {{param|#.EnablePerConnectionResults}} is {{true}}. A new object is created for each connection specified in {{param|#.NumberOfConnections}}. Instance numbers MUST start at 1 and sequentially increment as new instances are created. All instances are removed when {{param|#.DiagnosticsState}} is set to {{enum|Requested|#.DiagnosticsState}} or {{enum|None|#.DiagnosticsState}}. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the client sends the GET command. * For FTP this is the time at which the client sends the RTRV command. Begin of transmission time in UTC, which MUST be specified to microsecond precision For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the first data packet is received. * For FTP this is the time at which the client receives the first data packet on the data connection. End of transmission in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the last data packet is received. * For FTP this is the time at which the client receives the last packet on the data connection. The number of {{units}} of the test file sent during the FTP/HTTP transaction including FTP/HTTP headers, between {{param|BOMTime}} and {{param|EOMTime}}. The total number of {{units}} (at the IP layer) received on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.BytesReceived on the {{param|#.Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. If {{param|#.Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The total number of {{units}} (at the IP layer) sent on the Interface between {{param|BOMTime}} and {{param|EOMTime}}. This MAY be calculated by sampling Stats.BytesSent on the {{param|#.Interface}} object at {{param|BOMTime}} and at {{param|EOMTime}} and subtracting. If {{param|#.Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. Request time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP socket open (SYN) was sent for the HTTP connection. * For FTP this is the time at which the TCP socket open (SYN) was sent for the data connection. Response time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z * For HTTP this is the time at which the TCP ACK to the socket opening the HTTP connection was received. * For FTP this is the time at which the TCP ACK to the socket opening the data connection was received. Results for time segmented tests (tests where {{param|#.TimeBasedTestDuration}} > 0 and {{param|#.TimeBasedTestMeasurementInterval}} > 0). This data is totaled across all connections in the test. A new object is created every {{param|#.TimeBasedTestMeasurementInterval}} after that interval has completed. Instance numbers MUST start at 1 and sequentially increment as new instances are created. All instances are removed when {{param|#.DiagnosticsState}} is set to {{enum|Requested|#.DiagnosticsState}} or {{enum|None|#.DiagnosticsState}}. Change in the value of {{param|#.TestBytesSent}} between {{param|StartTime}} and {{param|EndTime}}, measured in {{units}}. The total number of {{units}} (at the IP layer) received on the Interface between {{param|StartTime}} and {{param|EndTime}}. This MAY be calculated by sampling Stats.BytesReceived on the {{param|#.Interface}} object at {{param|StartTime}} and at {{param|EndTime}} and subtracting. If {{param|#.Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The total number of {{units}} (at the IP layer) sent on the Interface between {{param|StartTime}} and {{param|EndTime}}. This MAY be calculated by sampling Stats.BytesSent on the {{param|#.Interface}} object at {{param|StartTime}} and at {{param|EndTime}} and subtracting. If {{param|#.Interface}} is {{empty}}, this parameter cannot be determined and SHOULD be 0. The start time of this interval which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z The end time of this interval which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z The maximum number of rows in {{object|IndividualPacketResult}} that the CPE will store. If a test would create more rows than {{param}} only the first {{param}} rows are present in {{object|IndividualPacketResult}}. The IP-layer interface over which the test is to be performed. Example: Device.IP.Interface.1 {{template|INTERFACE-ROUTING}} Host name or address of the host to perform tests to. Port on the host to perform tests to. Number of repetitions of the test to perform before reporting the results. The default value SHOULD be 1. Timeout in {{units}} for the test. That is, the amount of time to wait for the return of a packet that was sent to the {{param|Host}}. Size of the data block in {{units}} to be sent for each packet. The default value SHOULD be 24. DiffServ codepoint to be used for the test packets. The default value SHOULD be zero. The time in {{units}} between the {{param|NumberOfRepetitions}} of packets sent during a given test. The default value SHOULD be 1000. Indicates the IP protocol version to be used. The default value SHOULD be {{enum|Any}}. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests Use IPv6 for the requests. The results must be returned in the {{object|IndividualPacketResult}} table for every repetition of the test when set to {{true}}. The default value SHOULD be {{false}}. {{numentries}} Indicates which IP address was used to send the request. Result parameter indicating the number of successful packets (those in which a successful response was received prior to the timeout) in the most recent test. Result parameter indicating the number of failed packets (those in which a successful response was not received prior to the timeout) in the most recent test. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent test. If there were no successful responses, this value MUST be zero. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent test. If there were no successful responses, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent test. If there were no successful responses, this value MUST be zero. This object provides the results from individual UDPEchoPlus test packets collected during a test if {{param|#.EnableIndividualPacketResults}} is set to true. When {{param|#.DiagnosticsState}} is set to {{enum|Complete|#.DiagnosticsState}} it should contain {{param|#.NumberOfRepetitions}} objects. Instance numbers MUST start at 1 and sequentially increment as new instances are created. The instance number should match the TestIterationNumber field of the request and response packet. All instances are removed when {{param|#.DiagnosticsState}} is set to {{enum|Requested|#.DiagnosticsState}} or {{enum|None|#.DiagnosticsState}}. Indicates that the response to this UDP Echo Plus packet sent was received by the client. When this value is {{true}}, then all the remaining parameters in this instance are valid. Otherwise only the values originally set by the CPE client (e.g. {{param|PacketSendTime}} and {{param|TestGenSN}}) MAY be set to valid values. Time the client sent this UDP Echo Plus packet in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z Time the client receives the response packet in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456Z If this response is never received, {{param}} SHOULD be set to the Unknown Time value as specified in {{bibref|TR-106|Section 3.2.2}}. The TestGenSN field in the UDPEcho Plus packet {{bibref|TR-143|Section A.1.4}} sent by the CPE client. The TestRespSN field in the response packet {{bibref|TR-143|Section A.1.4}} from the UDP Echo Plus server (i.e. {{param|#.Host}}) for this Echo Plus packet sent by the CPE client. If {{param|PacketSuccess}} is {{false}}, {{param}} SHOULD be 0. The TestRespRcvTimeStamp field in the response packet {{bibref|TR-143|Section A.1.4}} from the UDP Echo Plus server (i.e. {{param|#.Host}}) to record the reception time in {{units}} of this UDP Echo Plus packet sent from the CPE client. If {{param|PacketSuccess}} is {{false}}, {{param}} SHOULD be 0. The TestRespReplyTimeStamp field in the response packet {{bibref|TR-143|Section A.1.4}} from the UDP Echo Plus server (i.e. {{param|#.Host}}) to record the server reply time in {{units}} of this UDP Echo Plus packet sent from the CPE client. That is, the time that the server returned the UDP Echo Plus packet. If {{param|PacketSuccess}} is {{false}}, {{param}} SHOULD be 0. The count value that was set by the UDP Echo Plus server (i.e. {{param|#.Host}}) to record the number of dropped echo response packets by the server. This count is incremented if a valid echo request packet is received at a UDP EchoPlus server but for some reason cannot be responded to (e.g. due to local buffer overflow, CPU utilization, etc...). If {{param|PacketSuccess}} is {{false}}, {{param}} SHOULD be 0. Indicates the maximum number of connections that are supported for an IP-Layer Capacity test. The maximum number of rows in {{object|IncrementalResult}} that the device will store. Indicates the installed version of the test software. The software version string will be implementation-dependent, and SHOULD identify both the implementation and the version (e.g., UDPST-7.2.1). Indicates the control protocol version supported by the test software. Refer to {{bibref|TR-471}} for more information. Indicates the test metrics from {{bibref|TR-471|Section 5.2}} that are supported by the device. Note that {{bibref|TR-471}} mandates support for and use of IPLR and Sampled RTT. IP packet Loss Ratio Sampled Round Trip Time IP packet Delay Variation IP packet Reordering Ratio Replicated IP packet Ratio {{numentries}} Authentication Code table containing list of keys to be used by the client when connecting to the server. A passphrase that is used by the client to authenticate with the server. {{reference}} The IP-layer interface over which the test is to be performed. Example: Device.IP.Interface.1 {{template|INTERFACE-ROUTING}} Indicates whether the device will act as Sender or Receiver of test packets. The device will act as the Receiver. The device will act as the Sender. The Fully Qualified Domain Name (FQDN) or IP address of the Test Endpoint to perform the UDP Capacity tests with. {{deprecated|2.17|because it is superseded by {{param|ServerList}} with multi-flow and server capability. Refer to {{bibref|TR-471}} for details}} {{obsoleted|2.19}} {{deleted|2.20}} A list of servers intended as testing partners for the client. The client works through the server list attempting individual test flows in a round-robin sequence. One flow is attempted to each server and all flows are required for testing, unless the optional {{param|FlowCount}} and {{param|MaximumFlows}} parameters are specified. The list contains each server’s Fully Qualified Domain Name or IP address and listening port in the format ''server:port''. Port on the Test Endpoint host. {{deprecated|2.17|because it is superseded by {{param|ServerList}} with multi-flow and server capability. Refer to {{bibref|TR-471}} for details}} {{obsoleted|2.19}} {{deleted|2.20}} If {{true}}, jumbo frames are allowed above 1 Gbps. The default value SHOULD be {{true}}. The MTU to be used for this test. Common MTU settings are 1500, 1250 and 9000. When set to {{true}}, the client is invoked with the option which uses the bytes statistics on the interface along with the test traffic to determine the maximum IP layer capacity. When set to {{false}}, only test traffic is used to calculate IP layer capacity metrics. If {{true}}, client uses authentication for the test. If {{false}}, the client does not use authentication. Refer to {{template|IPLAYERCAPACITY}} for description on how the input arguments are provided to enable authentication for the test. The authentication code or key to use when the client connects to the server. Refer to {{template|IPLAYERCAPACITY}} for description on how the input arguments are provided to enable authentication for the test. The reference to {{object|IPLayerCapacityAuthCode}} table by Alias. Refer to {{template|IPLAYERCAPACITY}} for description on how the input arguments are provided to enable authentication for the test. The key file location the client uses to derive the {{param|AuthenticationCode}} and {{param|AuthenticationAlias}} to be used for authentication. Refer to {{template|IPLAYERCAPACITY}} for description on how the input arguments are provided to enable authentication for the test. The number of connections to be used in the test. The default value SHOULD be 1. {{param}} MUST NOT be set to a value greater than {{param|{{template|IP-DIAGNOSTICS-PARENT}}IPLayerMaxConnections}}. {{deprecated|2.17|because it is superseded by {{param|ServerList}} with multi-flow and server capability and related parameters. Refer to {{bibref|TR-471}} for details}} {{obsoleted|2.19}} {{deleted|2.20}} Optional Number of flows required for a test. The default SHOULD be 0 (a magic number that indicates the parameter is not used). {{param}} MUST NOT be set to a value greater than {{param|{{template|IP-DIAGNOSTICS-PARENT}}IPLayerMaxConnections}}. Optional number of flows to attempt. MaximumFlows must be greater than the size of ServerList or FlowCount. The default SHOULD be 0 (a magic number that indicates the parameter is not used). {{param}} MUST NOT be set to a value greater than {{param|{{template|IP-DIAGNOSTICS-PARENT}}IPLayerMaxConnections}}. Ethernet priority code for marking packets transmitted in the test (if applicable). The default value SHOULD be zero. The DiffServ code point for marking packets transmitted in the test. The default value SHOULD be zero. Indicates the IP protocol version to be used. The default value SHOULD be {{enum|Any}}. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests Use IPv6 for the requests. Minimum reference size of UDP payload in {{units}}. No default. The implementation will algorithmically determine a value if none is configured. The value SHOULD be set to a value that avoids fragmentation (i.e., using path MTU discovery). Maximum reference size of UDP payload in {{units}}. No default. The implementation will algorithmically determine a value if none is configured. The value SHOULD be set to the largest value that avoids fragmentation (i.e., using path MTU discovery). If {{param|JumboFramesPermitted}} is {{false}}, the maximum value MUST be 1472 octets. If {{param|JumboFramesPermitted}} is {{true}}, this value can be as large as 8972 octets. {{param}} MUST be greater than or equal to {{param|UDPPayloadMin}}. UDP Payload Content Type, If there is payload compression in the path and tests intend to characterize a possible advantage due to compression, then payload content SHOULD be supplied by a pseudo-random sequence generator, by using part of a compressed file, or by other means. Payload may also contain the test protocol PDUs. The default value SHOULD be {{enum|zeroes}}. All zero (0) payload content. All one (1) payload content. Alternating zero (0) and one (1) payload content. Random payload content. Starting value for range of Dynamic Ports supported for test traffic and status feedback messages. {{param}} MUST be less than or equal to {{param|PortMax}}, if specified. If {{param}} and {{param|PortMax}} are not specified, the full range of Ports in the Dynamic Ports range (49152-65535) that have been specifically set aside by IANA MAY be used. Indicates the upper bound of the supported Dynamic Port range, where {{param|PortMin}} indicates the starting port number. {{param}} MUST be greater than or equal to {{param|PortMin}}, if specified. If {{param|PortMin}} and {{param}} are not specified, the full range of Ports in the Dynamic Ports range (49152-65535) that have been specifically set aside by IANA MAY be used. Starting value for range of User Ports supported for test traffic and status feedback messages. A value of zero (0) indicates no User Ports are used for test traffic or status feedback messages. Indicates the upper bound of the supported User Port range, where {{param|PortOptionalMin}} indicates the starting port number. {{param}} MUST be greater than or equal to {{param|PortOptionalMin}}. A value of zero (0) indicates no User Ports are used for test traffic or status feedback messages. Indicates the type of IP-Layer Capacity test being run. The default value SHOULD be {{enum|Search}}. Search algorithm will be used to determine sending rate. Fixed sending rate will be used. Enables one-way IPDV (IP Packet Delay Variation) metric for load rate adjustment algorithm. When {{true}} (enabled), one-way delay variation is used, otherwise round-trip delay variation is used. The default value SHOULD be {{false}}. Enables IPRR (IP packet Reordering Ratio) metric. The default value SHOULD be {{false}}. Enables RIPRR (Replicated IP Packet Ratio) metric. The default value SHOULD be {{false}}. Duration of the preamble testing, when traffic is being sent and/or received but the test clock has not been started. This is done to ensure all network elements in the path are "awake". The default value SHOULD be 2 {{units}}. Value specified in {{units}}. The rate limiting or admission control bandwidth to be configured on the client for the test. A value of 0 indicates the client does not use rate limiting or admission control. The value is expressed in {{units}}. The Sending Rate for a {{enum|Fixed|TestType}} test or the initial Sending Rate value for a {{enum|Search|TestType}} test. Value specified in {{units}}. The default value SHOULD be 500 {{units}}. The configurable initial Sending Rate index (to a row of the sending rate table) for a {{enum|Fixed|TestType}} or {{enum|Search|TestType}} test. {{param}} overrides {{param|StartSendingRate}} if both parameters are present. See Annex A of {{bibref|TR-471}} for details. The default value SHOULD be 0. Number of intermediate measurement reporting intervals. The value MUST NOT be greater than {{param|{{template|IP-DIAGNOSTICS-PARENT}}IPLayerMaxIncrementalResult}}. The default value SHOULD be 10. When the value >= 1, bimodal test mode is requested and the value represents the number of sub-intervals to be included in the first capacity test mode. The remaining sub-intervals of {{param|NumberTestSubIntervals}} are for the second capacity test mode. Value = 0 indicates that bimodal testing is disabled. The value MUST NOT be greater than {{param|NumberTestSubIntervals}}. The default value SHOULD be 0. Duration of intermediate measurement reporting intervals. {{param}} * {{param|NumberTestSubIntervals}} MUST result in an integer value in seconds, in the range 5 seconds <= {{param}} * {{param|NumberTestSubIntervals}} <= 60 seconds. The default value SHOULD be 1000 {{units}}. Value specified in {{units}}. Period of status feedback message (receiver of offered load returns messages to the sender with results of measured metrics). Value specified in {{units}}. The default value SHOULD be 50 {{units}}. Timeout value. Value specified in {{units}}. The default value SHOULD be 5 {{units}}. {{deprecated|2.15|because it is superseded by {{param|TimeoutNoTestTraffic}} due to new precision requirement. Refer to {{bibref|TR-471}} for details}} {{obsoleted|2.17}} {{deleted|2.18}} Timeout value. If no test traffic packets are received for {{param}} {{units}}, test will timeout. Value specified in {{units}}. The default value SHOULD be 1000 {{units}}. Timeout value. If no status message packets are received for {{param}} {{units}}, test will timeout. Value specified in {{units}}. The default value SHOULD be 1000 {{units}}. Maximum waiting time for packets to arrive. Value specified in {{units}}. The default value SHOULD be 1000 {{units}}. Maximum Round Trip Time waiting time for packets to arrive. Value specified in {{units}}. The default value SHOULD be 3000 {{units}}. Indicates the requested precision of timestamp values. The test implementation will determine the actual precision to use based on the implemented resolution capabilities of the protocols used and this requested value. If the implemented resolution capabilities of the {{param|{{template|IP-DIAGNOSTICS-PARENT}}IPLayerCapSupportedMetrics}} protocols being used are able to provide the requested resolution, this resolution SHOULD be provided. Value specified in {{units}}. The default value SHOULD be 1 {{units}}. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. Threshold for Loss or Reordering or Replication impairments measured (events where received packet sequence number did not increase by one). The default value SHOULD be 10. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. When {{true}} (enabled) only Loss counts toward received packet sequence number errors, and Reordering and Duplication impairments are ignored. When {{false}} (disabled), Loss, Reordering and Duplication are all counted as sequence number errors. The default value SHOULD be {{true}} (enabled). This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. The lower threshold on the range of Round Trip Time (RTT) variation. Value specified in {{units}}. The default value SHOULD be 30 {{units}}. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. The upper threshold on the range of Round Trip Time (RTT) variation. Value specified in {{units}}. The default value SHOULD be 90 {{units}}. The initial number of retries before activating “fast” sending rate increase mode. Different paths through the flow chart increase the sending rate, either fast or slow, or decrease the rate, etc. The algorithm doubles the threshold each time on subsequent activations. See Annex B of {{bibref|TR-471}} for details. The default value SHOULD be 5. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. The number of rows to move in a single adjustment when initially increasing offered load (to ramp up quickly). The default value SHOULD be 10. Configurable choice of Load Rate Adjustment Algorithm. Refer to {{bibref|TR-471}} for details. Use type "B" Load Rate Adjustment Algorithm. See section 5.2.1 in {{bibref|TR-471}} for details. Use type "C" Load Rate Adjustment Algorithm. See Annex B in {{bibref|TR-471}} for details. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. Threshold on the measured number of consecutive status reports indicating loss and/or delay variation above {{param|UpperThresh}} (SlowAdjCount). The default value SHOULD be 3. This parameter is only meaningful if {{param|TestType}} is {{enum|Search|TestType}}. Threshold for transition between low and high sending rate step sizes (such as 1Mbps and 100 Mbps). If {{param|JumboFramesPermitted}} is {{true}} this may result in use of jumbo frames. The default value SHOULD be 1 {{units}}. {{numentries}} {{numentries}} Status code of the test returned by the client, if applicable. Status message of the test returned by the client, if applicable. Beginning of transmission send/receive time in UTC, which MUST be specified to {{param|TimestampResolution}} precision. If multiple connections are used, then {{param}} is set to the earliest value across all connections. For example: 2008-04-09T15:01:05.123456Z End of transmission in UTC, which MUST be specified to {{param|TimestampResolution}} precision. If multiple connections are used, then {{param}} is set to the latest value across all connections. For example: 2008-04-09T15:01:05.123456Z Configured value of {{param|Tmax}} used in the test. This value is expressed in {{units}}. Duration of the test (either downlink or uplink). This value is expected to equal {{param|TestSubInterval}} * {{param|NumberTestSubIntervals}}. This value is expressed in {{units}}. The maximum IP-Layer Capacity metric from among all {{param|IncrementalResult.{i}.IPLayerCapacity}} values measured between {{param|BOMTime}} and {{param|EOMTime}} across all connections for this test. This is calculated according to {{bibref|TR-471}} Equation 1. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Time in UTC of end of the sub-interval when {{param|MaxIPLayerCapacity}} was measured. If the value of {{param|MaxIPLayerCapacity}} occurred in multiple sub-intervals, this MUST be the earliest of these sub-intervals. Value MUST be specified to {{param|TimestampResolution}} precision. For example: 2008-04-09T15:01:05.123456Z Results of measurements using the Maximum IP-Layer Capacity metric, according to {{bibref|TR-471}} Equation 1, and calculations to estimate the capacity at Layer 2 with Preamble and Inter-frame gap, but no ETH Frame Check Sequence. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Results of measurements using the Maximum IP-Layer Capacity metric, according to {{bibref|TR-471}} Equation 1, and calculations to estimate the capacity at Layer 2 with ETH Frame Check Sequence. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Results of measurements using the Maximum IP-Layer Capacity metric, according to {{bibref|TR-471}} Equation 1, and calculations to estimate the capacity at Layer 2 with ETH Frame Check Sequence and VLAN tag. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Ratio of lost packets to total packets during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. The range of Round Trip Time (RTT) during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. The range of Packet Delay Variation (PDV) during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. The minimum one-way delay during the sub-interval of {{param|MaxIPLayerCapacity}}. The minimum one-way delay is calculated at the conclusion of the test and SHALL be calculated using the conditional distribution of all packets with a finite one-way delay value (undefined delays are excluded). This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. Ratio of reordered packets to total packets during the sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. Ratio of replicated packets to total packets during the sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. The value of minimum Round Trip Time (RTT) during the sub interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. The value of maximum Round Trip Time (RTT) during the sub interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. The number of bits observed on the Interface during an IP-Layer Capacity test for time interval of duration {{param|TestSubInterval}} ending at {{param|IncrementalResult.{i}.TimeOfSubInterval}} corresponding to the {{param|MaxIPLayerCapacity}}, divided by the duration of {{param|TestSubInterval}}. Result is expressed in Mbps with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. This is primarily a diagnostic measurement. Measurement direction follows the {{param|Role}}. The IP-Layer Capacity metric from among all {{param|IncrementalResult.{i}.IPLayerCapacity}} values measured between {{param|BOMTime}} and {{param|EOMTime}} across all connections for this test. This is calculated according to {{bibref|TR-471}} Equation 1. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Ratio of lost packets to total packets during the complete {{param|TestInterval}}. This value is expressed as a decimal to 9 decimal digits. The range of measured Round Trip Time (RTT) during the complete {{param|TestInterval}}. This value is expressed in {{units}}, as a decimal to 9 decimal digits. The range of Packet Delay Variation (PDV) during the complete {{param|TestInterval}}. This value is expressed in {{units}}, as a decimal to 9 decimal digits. The minimum one-way delay during the complete {{param|TestInterval}}. This value is expressed in {{units}}, as a decimal to 9 decimal digits. The minimum RTT during the complete {{param|TestInterval}}. This value is expressed in {{units}}, as a decimal to 9 decimal digits. Ratio of reordered packets to total packets during the complete {{param|TestInterval}}. This value is expressed as a decimal to 9 decimal digits. Ratio of replicated packets to total packets during the complete {{param|TestInterval}}. This value is expressed as a decimal to 9 decimal digits. The number of bits observed on the {{param|Interface}} during an IP-Layer Capacity test for the entire time interval of duration {{param|TestInterval}}, divided by the duration of {{param|TestInterval}}. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. This is primarily a diagnostic measurement. Measurement direction follows the {{param|Role}}. Configured value of {{param|TmaxRTT}} used in the test. This value is expressed in {{units}}. Indicates the timestamp resolution of reported results. This is a function of the measurement protocol, and it is usually determined once the protocol chosen. Value specified in {{units}}. Number of flows set-up and used for a test. Modal test results. Only returned when bimodal test mode is enabled ({{param|#.NumberFirstModeTestSubIntervals}} >=1). If returned, it MUST contain 1 or more entries, with instance number 1 corresponding to the second mode and instance number 2 corresponding to the third mode. Results for the Maximum in each mode/instance are calculated based on {{object|#.IncrementalResult.{i}.}} data within the boundary of its corresponding mode. The maximum IP-Layer Capacity metric from among all {{param|#.IncrementalResult.{i}.IPLayerCapacity}} values within corresponding mode across all connections for this test. This is calculated according to {{bibref|TR-471}} Equation 1. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Time in UTC of end of the sub-interval when {{param|MaxIPLayerCapacity}} was measured. If the value of {{param|MaxIPLayerCapacity}} occurred in multiple sub-intervals, this MUST be the earliest of these sub-intervals. Value MUST be specified to {{param|#.TimestampResolution}} precision. For example: 2008-04-09T15:01:05.123456Z Results of measurements using the Maximum IP-Layer Capacity metric, according to {{bibref|TR-471}} Equation 1, and calculations to estimate the capacity at Layer 2 with Preamble and Inter-frame gap, but no ETH Frame Check Sequence. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Results of measurements using the Maximum IP-Layer Capacity metric, according to {{bibref|TR-471}} Equation 1, and calculations to estimate the capacity at Layer 2 with ETH Frame Check Sequence. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Results of measurements using the Maximum IP-Layer Capacity metric, according to {{bibref|TR-471}} Equation 1, and calculations to estimate the capacity at Layer 2 with ETH Frame Check Sequence and VLAN tag. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Ratio of lost packets to total packets during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. The range of Round Trip Time (RTT) during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. The range of Packet Delay Variation (PDV) during sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. The minimum one-way delay during the sub-interval of {{param|MaxIPLayerCapacity}}. The minimum one-way delay is calculated at the conclusion of the test and SHALL be calculated using the conditional distribution of all packets with a finite one-way delay value (undefined delays are excluded). This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. Ratio of reordered packets to total packets during the sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. Ratio of replicated packets to total packets during the sub-interval of {{param|MaxIPLayerCapacity}}. This value is expressed as a decimal to 9 decimal digits. The number of bits observed on the {{param|#.Interface}} during an IP-Layer Capacity test for time interval of duration {{param|#.TestSubInterval}} ending at {{param|#.IncrementalResult.{i}.TimeOfSubInterval}} corresponding to the {{param|MaxIPLayerCapacity}}, divided by the duration of {{param|#.TestSubInterval}}. Result is expressed in Mbps with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. This is primarily a diagnostic measurement. Measurement direction follows the {{param|#.Role}}. Results for time segmented tests (tests where {{param|#.NumberTestSubIntervals}} > 1). This data is calculated across all connections in the test. A new object is created every {{param|#.TestSubInterval}} after that interval has completed. Instance numbers MUST start at 1 and sequentially increment as new instances are created. All instances are removed when new test is started or results are otherwise cleared. Results of measurements using the maximum IP-Layer Capacity metric calculation for a single interval from {{bibref|TR-471}} Equation 1, for time interval of duration {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}} ending at {{param|TimeOfSubInterval}} across all connections for this test. Result is expressed in {{units}} with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. Time in UTC of end of sub-interval when {{param|IPLayerCapacity}} was measured. Value MUST be specified to {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TimestampResolution}} precision. For example: 2008-04-09T15:01:05.123456Z Ratio of lost packets to total packets, for time interval of duration {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}} ending at {{param|TimeOfSubInterval}} across all connections for this test. This value is expressed as a decimal to 9 decimal digits. The range of Round Trip Time (RTT), for time interval of duration {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}} ending at {{param|TimeOfSubInterval}} across all connections for this test. See {{bibref|TR-471}} for description of how value is calculated. This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. The range of Packet Delay Variation (PDV), for time interval of duration {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}} ending at {{param|TimeOfSubInterval}} across all connections for this test. See {{bibref|TR-471}} for description of how value is calculated. This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. The minimum one-way delay, for time interval of duration {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}} ending at {{param|TimeOfSubInterval}} across all connections for this test. The minimum one-way delay is calculated at the conclusion of the test and SHALL be calculated using the conditional distribution of all packets with a finite one-way delay value (undefined delays are excluded). This value is expressed in {{units}}. This value is expressed as a decimal to 9 decimal digits. Ratio of reordered packets to total packets, for time interval of duration {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}} ending at {{param|TimeOfSubInterval}} across all connections for this test. This value is expressed as a decimal to 9 decimal digits. Ratio of replicated packets to total packets, for time interval of duration {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}} ending at {{param|TimeOfSubInterval}} across all connections for this test. This value is expressed as a decimal to 9 decimal digits. The number of bits observed on the {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}Interface}} during an IP-Layer Capacity test for time interval of duration {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}} ending at {{param|TimeOfSubInterval}}, divided by the duration of {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}TestSubInterval}}. Result is expressed in Mbps with 2 digits beyond the decimal. 10^6^ bits/second = 1 {{units}}. This is primarily a diagnostic measurement. Measurement direction follows the {{param|{{template|IP-LAYER-CAPACITY-DIAG-PARENT}}Role}}. {{reference|the IP-layer interface over which the test is to be performed}} Example: Device.IP.Interface.1 {{template|INTERFACE-ROUTING}} Indicates the IP protocol version to be used. Use either IPv4 or IPv6 depending on the system preference. Use IPv4 for the requests. Use IPv6 for the requests. The protocol over which the test is to be performed. Each entry is a Host name or address of a host to ping. Number of repetitions of the ping test to perform for each {{param|HostList}} entry before reporting the results. Timeout in {{units}} for each iteration of the ping test where the total number of iterations is the value of {{param|NumberOfRepetitions}} times the number of entities in the {{param|HostList}} Parameter. Result parameter indicating the Host (one of the items within the {{param|HostList}} Parameter) with the smallest average response time. Result parameter indicating the minimum response time in {{units}} over all repetitions with successful responses of the most recent ping test for the Host identified in {{param|FastestHost}}. Success is defined by the underlying protocol used. If there were no successful responses across all Hosts, this value MUST be zero. Result parameter indicating the average response time in {{units}} over all repetitions with successful responses of the most recent ping test for the Host identified in {{param|FastestHost}}. Success is defined by the underlying protocol used. If there were no successful responses across all Hosts, this value MUST be zero. Result parameter indicating the maximum response time in {{units}} over all repetitions with successful responses of the most recent ping test for the Host identified in {{param|FastestHost}}. Success is defined by the underlying protocol used. If there were no successful responses across all Hosts, this value MUST be zero. Indicates which IP address was used to send the request to the host identified in {{param|FastestHost}}. IP object that contains the {{object|Interface}}, {{object|ActivePort}}, and {{object|Diagnostics}} objects. Indicates whether the device is IPv4 capable. Enables or disables the IPv4 stack, and so the use of IPv4 on the device. This affects only layer 3 and above. When {{false}}, IP interfaces that had been operationally up and passing IPv4 packets will now no longer be able to do so, and will be operationally down (unless also attached to an enabled IPv6 stack). Indicates the status of the IPv4 stack. {{enum}} The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. Indicates whether the device is IPv6 capable. Note: If {{false}}, it is expected that IPv6-related parameters, enumeration values, etc will not be implemented by the device. Enables or disables the IPv6 stack, and so the use of IPv6 on the device. This affects only layer 3 and above. When {{false}}, IP interfaces that had been operationally up and passing IPv6 packets will now no longer be able to do so, and will be operationally down (unless also attached to an enabled IPv4 stack). Indicates the status of the IPv6 stack. {{enum}} The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. The ULA /48 prefix {{bibref|RFC4193|Section 3}}. {{numentries}} IP interface table (a stackable interface object as described in {{bibref|TR-181i2|Section 4.2}}). This table models the layer 3 IP interface. Each IP interface can be attached to the IPv4 and/or IPv6 stack. The interface's IP addresses and prefixes are listed in the {{object|IPv4Address}}, {{object|IPv6Address}} and {{object|IPv6Prefix}} tables. Note that support for manipulating {{param|Loopback}} interfaces is OPTIONAL, so the implementation MAY choose not to create (or allow the Controller to create) {{object}} instances of type {{enum|Loopback|Type}}. When the Controller administratively disables the interface, i.e. sets {{param|Enable}} to {{false}}, the interface's automatically-assigned IP addresses and prefixes MAY be retained. When the Controller administratively enables the interface, i.e. sets {{param|Enable}} to {{true}}, these IP addresses and prefixes MUST be refreshed. It's up to the implementation to decide exactly what this means: it SHOULD take all reasonable steps to refresh everything but if it is unable, for example, to refresh a prefix that still has a significant lifetime, it might well choose to retain rather than discard it. Any {{enum|Tunneled|Type}} IP interface instances instantiated by the CPE MUST NOT have any statistics, writable parameters, IP addresses or IPv6 prefixes. Any read-only parameters, e.g. {{param|Status}}, MUST return the same information as for the corresponding {{enum|Tunnel|Type}} interface. The reason for these rules is that {{enum|Tunneled|Type}} IP interfaces exist only in order to be the targets of references (within the data model) and do not model any concepts over and above those already modeled by the {{enum|Tunnel|Type}} IP interfaces. Note that {{enum|Tunnel|Type}} and {{enum|Tunneled|Type}} IP interfaces are part of a legacy mechanism that is only used for {{object|##.IPv6rd}}, {{object|##.DSLite}} and {{object|##.IPsec}} tunnels and MUST NOT be used in any other context. For all other tunneling mechanisms {{enum|Normal|Type}} IP interfaces are stacked above technology-specific Tunnel Interfaces, e.g. above {{object|##.GRE.Tunnel.{i}.Interface}} or {{object|##.MAP.Domain.{i}.Interface}} objects. Enables or disables the interface (regardless of {{param|IPv4Enable}} and {{param|IPv6Enable}}). This parameter is based on ''ifAdminStatus'' from {{bibref|RFC2863}}. {{param}} MUST be {{empty}} and read-only when {{param|Type}} is {{enum|Loopback|Type}}, {{enum|Tunnel|Type}}, or {{enum|Tunneled|Type}}. If set to {{true}}, attaches this interface to the IPv4 stack. If set to {{false}}, detaches this interface from the IPv4 stack. Once detached from the IPv4 stack, the interface will now no longer be able to pass IPv4 packets, and will be operationally down (unless also attached to an enabled IPv6 stack). For an IPv4 capable device, if {{param}} is not present this interface SHOULD be permanently attached to the IPv4 stack. Note that {{param}} is independent of {{param|Enable}}, and that to administratively enable an interface for IPv4 it is necessary for both {{param|Enable}} and {{param}} to be {{true}}. If set to {{true}}, attaches this interface to the IPv6 stack. If set to {{false}}, detaches this interface from the IPv6 stack. Once detached from the IPv6 stack, the interface will now no longer be able to pass IPv6 packets, and will be operationally down (unless also attached to an enabled IPv4 stack). For an IPv6 capable device, if {{param}} is not present this interface SHOULD be permanently attached to the IPv6 stack. Note that {{param}} is independent of {{param|Enable}}, and that to administratively enable an interface for IPv6 it is necessary for both {{param|Enable}} and {{param}} to be {{true}}. Controls whether or not ULAs {{bibref|RFC4193}} are generated and used on this interface. {{reference}} The ''Router'' instance that is associated with this IP Interface entry. The maximum transmission unit (MTU); the largest allowed size of an IP packet (including IP headers, but excluding lower layer headers such as Ethernet, PPP, or PPPoE headers) that is allowed to be transmitted by or through this device. IP interface type. {{enum}} For {{enum|Loopback}}, {{enum|Tunnel}}, and {{enum|Tunneled}} IP interface objects, the {{param|LowerLayers}} parameter MUST be {{empty}}. Only used with legacy ({{enum|Tunnel}},{{enum|Tunneled}}) IP interface pairs Only used with legacy ({{enum|Tunnel}},{{enum|Tunneled}}) IP interface pairs When set to {{true}}, the IP interface becomes a loopback interface and the CPE MUST set {{param|Type}} to {{enum|Loopback|Type}}. In this case, the CPE MUST also set {{param|LowerLayers}} to {{empty}} and fail subsequent attempts at setting {{param|LowerLayers}} until the interface is no longer a loopback. Support for manipulating loopback interfaces is OPTIONAL. {{numentries}} {{numentries}} {{numentries}} If {{true}}, enables auto-IP on the interface {{bibref|RFC3927}}. This mechanism is only used with IPv4. When auto-IP is enabled on an interface, an {{object|IPv4Address}} object will dynamically be created and configured with auto-IP parameter values. The exact conditions under which an auto-IP address is created (e.g. always when enabled or only in absence of dynamic IP addressing) is implementation specific. {{numentries}} IPv4 address table. Entries are auto-created and auto-deleted as IP addresses are added and deleted via DHCP, auto-IP, 3GPP-NAS (3GPP Non Access Stratum), or IPCP. Static entries are created and configured by the Controller. Enables or disables this IPv4 address. The status of this {{object}} table entry. {{enum}} The {{enum|Error_Misconfigured}} value indicates that a necessary configuration value is undefined or invalid. The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. This parameter can only be modified if {{param|AddressingType}} is {{enum|Static|AddressingType}}. IPv4 address. This parameter can only be modified if the {{param|AddressingType}} is {{enum|Static|AddressingType}}. Subnet mask. This parameter can only be modified if the {{param|AddressingType}} is {{enum|Static|AddressingType}}. Addressing method used to assign the IP address. {{enum}} Assigned by IKEv2 {{bibref|RFC5996}}. Assigned by the core network (fixed or cellular) using 3GPP NAS signalling methods. e.g. PDU Session Establishment Request {{bibref|3GPP-TS.24.501|Clause 6.2.4.2}}, PDN Connectivity Request {{bibref|3GPP-TS.24.301|Clause 6.2.2}}, PDP Context Activation Request {{bibref|3GPP-TS.24.008|Clause 6.1.2A}}, ... This information is available from the AT commands {{bibref|3GPP-TS.27.007|Clause 10.1.23}} PDP context read dynamic parameters +CGCONTRDP. This object contains parameters associated with the configuration that permits this interface to be used as Two-Way Active Measurement Protocol (TWAMP) reflector as defined in {{bibref|TR-390}}. Enables or disables the TWAMP reflector. The current operational state of the TWAMP reflector. The port used to listen for the TWAMP test packets. The maximum TTL of a received packet that this TWAMP reflector will reflect to the TWAMP controller. {{list}} List items represent source IP addresses and subnets from which test packets MUST always be received. {{empty}} list will allow test packets to be received from any source IP address. Each entry in the list MUST be either an IP address, or an IP prefix specified using Classless Inter-Domain Routing (CIDR) notation {{bibref|RFC4632}}. An IP prefix is specified as an IP address followed (with no intervening white space) by "/n", 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 prefix. IPv4 example: * 1.2.3.4 specifies a single IPv4 address, and 1.2.3.4/24 specifies a class C subnet with subnet mask 255.255.255.0. * 1.2.0.0/22 represents the 1024 IPv4 addresses from 1.2.0.0 to 1.2.3.255. IPv6 example: * fec0::220:edff:fe6a:f76 specifies a single IPv6 address. * 2001:edff:fe6a:f76::/64 represents the IPv6 addresses from 2001:edff:fe6a:f76:0:0:0:0 to 2001:edff:fe6a:f76:ffff:ffff:ffff:ffff. {{list}} List items represent source port ranges from which test packets MUST always be received. {{empty}} list will allow test packets to be received from any source port. Each entry in the list MUST be either a port number or a range of port numbers separated by a hyphen (-). For example, an entry with the value: '2-40' accepts test packets from any allowed source IP addresses with a source port between 2 and 40 inclusive. An entry of '3' accepts test packets from allow source IP addresses with a port of 3. This table contains the IP interface's IPv6 unicast addresses. There MUST be an entry for each such address, including anycast addresses. There are several ways in which entries can be added to and deleted from this table, including: * Automatically via SLAAC {{bibref|RFC4862}}, which covers generation of link-local addresses (for all types of device) and global addresses (for non-router devices). * Automatically via DHCPv6 {{bibref|RFC8415}}, which covers generation of any type of address (subject to the configured DHCP server policy). * Manually via a GUI or some other local management interface. * Manually via factory default configuration. * By the Controller. This table MUST NOT include entries for the Subnet-Router anycast address {{bibref|RFC4291|Section 2.6.1}}. Such entries would be identical to others but with a zero interface identifier, and would add no value. A loopback interface will always have address ''::1'' {{bibref|RFC4291|Section 2.5.3}} and MAY also have link-local address ''fe80::1''. This object is based on ''ipAddressTable'' from {{bibref|RFC4293}}. Enables or disables this {{object}} entry. The status of this {{object}} table entry. {{enum}} The {{enum|Error_Misconfigured}} value indicates that a necessary configuration value is undefined or invalid. The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. The status of {{param|IPAddress}}, indicating whether it can be used for communication. See also {{param|PreferredLifetime}} and {{param|ValidLifetime}}. {{enum}} This parameter is based on ''ipAddressStatus'' and ''ipAddressStatusTC'' from {{bibref|RFC4293}}. Valid address that can appear as the destination or source address of a packet. Valid but deprecated address that is not intended to be used as a source address. Invalid address that is not intended to appear as the destination or source address of a packet. Valid address that is not accessible because the interface to which it is assigned is not operational. Address status cannot be determined for some reason. The uniqueness of the address on the link is being verified. Invalid address that has been determined to be non-unique on the link. Valid address that is available for use, subject to restrictions, while its uniqueness on a link is being verified. This parameter can only be modified if {{param|Origin}} is {{enum|Static|Origin}}. IPv6 address. This parameter can only be modified if the {{param|Origin}} is {{enum|Static|Origin}}. This parameter is based on ''ipAddressAddr'' from {{bibref|RFC4293}}. Mechanism via which the IP address was assigned. {{enum}} This parameter is based on ''ipOrigin'' from {{bibref|RFC4293}}. Automatically generated. For example, a link-local address as specified by SLAAC {{bibref|RFC4862|Section 5.3}}, a global address as specified by SLAAC {{bibref|RFC4862|Section 5.5}}, or generated via CPE logic (e.g. from delegated prefix as specified by {{bibref|RFC8415}}), or from ULA /48 prefix as specified by {{bibref|RFC4193}}. Assigned by DHCPv6 {{bibref|RFC8415}}. Assigned by IKEv2 {{bibref|RFC5996}}. Assigned by MAP {{bibref|RFC7597}}, i.e. is this interface's ''MAP IPv6 address'' Specified by a standards organization, e.g. the ''::1'' loopback address, which is defined in {{bibref|RFC4291}}. Address assigned by the core network (fixed or cellular) using 3GPP NAS signalling methods. e.g. PDU Session Establishment Request {{bibref|3GPP-TS.24.501|Clause 6.2.4.2}}, PDN Connectivity Request {{bibref|3GPP-TS.24.301|Clause 6.2.2}}, PDP Context Activation Request {{bibref|3GPP-TS.24.008|Clause 6.1.2A}}, ... This information is available from the AT commands {{bibref|3GPP-TS.27.007|Clause 10.1.23}} PDP context read dynamic parameters +CGCONTRDP. For example, present in the factory default configuration (but not {{enum|WellKnown}}), created by the Controller, or created by some other management entity (e.g. via a GUI). IPv6 address prefix. Some addresses, e.g. addresses assigned via the DHCPv6 IA_NA option, are not associated with a prefix, and some {{enum|WellKnown|#.IPv6Prefix.{i}.Origin}} prefixes might not be modeled. In both of these cases {{param}} will be {{null}}. This parameter can only be modified if the {{param|Origin}} is {{enum|Static|Origin}}. This parameter is based on ''ipAddressPrefix'' from {{bibref|RFC4293}}. The time at which this address will cease to be preferred (i.e. will become deprecated), or {{null}} if not known. For an infinite lifetime, the parameter value MUST be 9999-12-31T23:59:59Z. This parameter can only be modified if the {{param|Origin}} is {{enum|Static|Origin}}. The time at which this address will cease to be valid (i.e. will become invalid), or {{null}} if unknown. For an infinite lifetime, the parameter value MUST be 9999-12-31T23:59:59Z. This parameter can only be modified if the {{param|Origin}} is {{enum|Static|Origin}}. Indicates whether this is an anycast address {{bibref|RFC4291|Section 2.6}}. Anycast addresses are syntactically identical to unicast addresses and so need to be configured explicitly. This parameter can only be modified if the {{param|Origin}} is {{enum|Static|Origin}}. This parameter is based on ''ipAddressType'' from {{bibref|RFC4293}}. This table contains the interface's IPv6 prefixes. There MUST be an entry for each such prefix, not only for prefixes learned from router advertisements. There are several ways in which entries can be added to and deleted from this table, including: * Automatically via {{bibref|RFC4861}} Router Advertisements. See also {{object|###.RouterAdvertisement}}. * Automatically via DHCPv6 {{bibref|RFC8415}} prefix delegation {{bibref|RFC8415}}. See also {{object|###.DHCPv6.Client}}. * Automatically via internal CPE logic, e.g. creation of child prefixes derived from a parent prefix. * Manually via a GUI or some other local management interface. * Manually via factory default configuration. * By the Controller. The CPE MAY choose not to create {{object}} entries for {{enum|WellKnown|Origin}} prefixes or for the ULA /48 prefix {{bibref|RFC4193}}. If an {{object}} entry exists for the ULA /48 prefix, it MUST be on a downstream interface (i.e. an interface for which the physical layer interface object has ''Upstream'' = {{false}}). This object is based on ''ipAddressPrefixTable'' from {{bibref|RFC4293}}. Enables or disables this {{object}} entry. The status of this {{object}} table entry. {{enum}} The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. The status of {{param|Prefix}}, indicating whether it can be used for communication. See also {{param|PreferredLifetime}} and {{param|ValidLifetime}}. {{enum}} This parameter is based on ''ipAddressStatus'' and ''ipAddressStatusTC'' from {{bibref|RFC4293}}. Valid prefix. Valid but deprecated prefix. Invalid prefix. Valid prefix that is not accessible because the interface to which it is assigned is not operational. Prefix status cannot be determined for some reason. This parameter can only be modified if {{param|Origin}} is {{enum|Static|Origin}}. IPv6 address prefix. This parameter can only be modified if the {{param|Origin}} is {{enum|Static|Origin}}. This parameter is based on ''ipAddressPrefixPrefix'' from {{bibref|RFC4293}}. Mechanism via which the prefix was assigned or most recently updated. {{enum}} Note that: * {{enum|PrefixDelegation}} and {{enum|RouterAdvertisement}} prefixes can exist only on upstream interfaces (i.e. interfaces for which the physical layer interface object has ''Upstream'' = {{true}}), * {{enum|AutoConfigured}} and {{enum|WellKnown}} prefixes can exist on any interface, and * {{enum|Static}} and {{enum|Child}} prefixes can exist only on downstream interfaces (i.e. interfaces for which the physical layer interface object has ''Upstream'' = {{false}}). Also note that a {{enum|Child}} prefix's {{param|ParentPrefix}} will always be an {{enum|AutoConfigured}}, {{enum|PrefixDelegation}}, or {{enum|RouterAdvertisement}} prefix. This parameter is based on ''ipAddressOrigin'' from {{bibref|RFC4293}}. Generated via internal CPE logic (e.g. the ULA /48 prefix) or derived from an internal prefix that is not modeled in any {{object}} table. Delegated via DHCPv6 {{bibref|RFC8415}} or some other protocol, e.g. IPv6rd {{bibref|RFC5969}}. Also see {{param|StaticType}}. Discovered via router advertisement {{bibref|RFC4861}} Prefix Information Option. Specified by a standards organization, e.g. ''fe80::/10'' for link-local addresses, or ''::1/128'' for the loopback address, both of which are defined in {{bibref|RFC4291}}. Created by the Controller, by some other management entity (e.g. via a GUI), or present in the factory default configuration (but not {{enum|WellKnown}}). Unrelated to any shorter length prefix that might exist on the CPE. Also see {{param|StaticType}}. Can be used for RA (Prefix Information), DHCPv6 address assignment (IA_NA) or DHCPv6 prefix delegation (IA_PD). Derived from an associated {{enum|AutoConfigured}} or {{enum|PrefixDelegation}} parent prefix. Also see {{param|StaticType}}, {{param|ParentPrefix}} and {{param|ChildPrefixBits}}. Can be used for RA (Prefix Information), DHCPv6 address assignment (IA_NA) or DHCPv6 prefix delegation (IA_PD). Static prefix sub-type. For a {{enum|Static|Origin}} prefix, this can be set to {{enum|PrefixDelegation}} or {{enum|Child}}, thereby creating an unconfigured prefix of the specified type that will be populated in preference to creating a new instance. This allows the Controller to pre-create "prefix slots" with known path names that can be referenced from elsewhere in the data model before they have been populated. {{enum}} This mechanism works as follows: * When this parameter is set to {{enum|PrefixDelegation}} or {{enum|Child}}, the instance becomes a "prefix slot" of the specified type. * Such an instance can be administratively enabled ({{param|Enable}} = {{true}}) but will remain operationally disabled ({{param|Status}} = {{enum|Disabled|Status}}) until it has been populated. * When a new prefix of of type T is needed, the CPE will look for a matching unpopulated instance, i.e. an instance with ({{param|Origin}},{{param}},{{param|Prefix}}) = ({{enum|Static|Origin}},T,""). If the CPE finds at least one such instance it will choose one and populate it. If already administratively enabled it will immediately become operationally enabled. If the CPE finds no such instances, it will create and populate a new instance with ({{param|Origin}},{{param}}) = (T,T). If the CPE finds more than one such instance, the algorithm via which it chooses which instance to populate is implementation-specific. * When a prefix that was populated via this mechanism becomes invalid, the CPE will reset {{param|Prefix}} to {{empty}}. This does not affect the value of the {{param|Enable}} parameter. The prefix {{param}} can only be modified if {{param|Origin}} is {{enum|Static|Origin}}. Prefix is a "normal" {{enum|Static|Origin}} prefix. Prefix is not {{enum|Static|Origin}}, so this parameter does not apply. Prefix will be populated when a {{enum|PrefixDelegation|Origin}} prefix needs to be created. Prefix will be populated when a {{enum|Child|Origin}} prefix needs to be created. In this case, the Controller needs also to set {{param|ParentPrefix}} and might want to set {{param|ChildPrefixBits}} (if parent prefix is not set, or goes away, then the child prefix will become operationally disabled). Indicates the parent prefix from which this prefix was derived. The parent prefix is relevant only for {{enum|Child|Origin}} prefixes and for {{enum|Static|Origin}} {{enum|Child|StaticType}} prefixes (both of which will always be on downstream interfaces), i.e. for {{param|Origin}}={{enum|Child|Origin}} and for ({{param|Origin}},{{param|StaticType}}) = ({{enum|Static|Origin}},{{enum|Child|StaticType}}) prefixes. This parameter can only be modified if {{param|Origin}} is {{enum|Static|Origin}} (which makes sense only for a prefix whose {{param|StaticType}} is already or will be changed to {{enum|Child|StaticType}}). A prefix that specifies the length of {{enum|Static|Origin}} {{enum|Child|StaticType}} prefixes and how they are derived from their {{param|ParentPrefix}}. It will be used if and only if it is not {{empty}} and is longer than the parent prefix (if it is not used, derivation of such prefixes is implementation-specific). Any bits to the right of the parent prefix are set to the bits in this prefix. For example, for a parent prefix of fedc::/56, if this parameter had the value 123:4567:89ab:cdef::/64, the child /64 would be fedc:0:0:ef::/64. For a parent prefix of fedc::/60, the child /64 would be fedc:0:0:f::/64. This parameter can only be modified if {{param|Origin}} is {{enum|Static|Origin}}. On-link flag {{bibref|RFC4861|Section 4.6.2}} as received (in the RA) for RouterAdvertisement. Indicates whether this prefix can be used for on-link determination. This parameter can only be modified if {{param|Origin}} is {{enum|Static|Origin}}. This parameter is based on ''ipAddressPrefixOnLinkFlag'' from {{bibref|RFC4293}}. Autonomous address configuration flag {{bibref|RFC4861|Section 4.6.2}} as received (in the RA) for RouterAdvertisement. Indicates whether this prefix can be used for generating global addresses as specified by SLAAC {{bibref|RFC4862}}. This parameter can only be modified if {{param|Origin}} is {{enum|Static|Origin}}. This parameter is based on ''ipAddressPrefixAutonomousFlag'' from {{bibref|RFC4293}}. This parameter is based on ''ipAddressPrefixAdvPreferredLifetime'' from {{bibref|RFC4293}}. The time at which this prefix will cease to be preferred (i.e. will become deprecated), or {{null}} if not known. For an infinite lifetime, the parameter value MUST be 9999-12-31T23:59:59Z. This parameter can only be modified if {{param|Origin}} is {{enum|Static|Origin}}. This parameter is based on ''ipAddressPrefixAdvValidLifetime'' from {{bibref|RFC4293}}. The time at which this prefix will cease to be valid (i.e. will become invalid), or {{null}} if not known. For an infinite lifetime, the parameter value MUST be 9999-12-31T23:59:59Z. This parameter can only be modified if {{param|Origin}} is {{enum|Static|Origin}}. This table lists the ports on which TCP connections are listening or established. Connection local IP address. Connection local port. The remote IP address of the source of inbound packets. This will be {{null}} for listening connections (only connections in {{enum|ESTABLISHED|Status}} state have remote addresses). The remote port of the source of inbound packets. This will be {{null}} for listening connections (only connections in {{enum|ESTABLISHED|Status}} state have remote addresses). Current operational status of the connection. {{enum}} The IP Diagnostics object. Indicates that Ping over IPv4 is supported. Indicates that Ping over IPv6 is supported. Indicates that TraceRoute over IPv4 is supported. Indicates that TraceRoute over IPv6 is supported. Indicates that Download Diagnostics over IPv4 is supported. Indicates that Download Diagnostics over IPv6 is supported. Indicates that Upload Diagnostics over IPv4 is supported. Indicates that Upload Diagnostics over IPv6 is supported. Indicates that UDPEcho Diagnostics over IPv4 is supported. Indicates that UDPEcho Diagnostics over IPv6 is supported. Indicates that IP Layer Capacity measurement is supported. Indicates that ServerSelection Diagnostics over IPv4 is supported. Indicates that ServerSelection Diagnostics over IPv6 is supported. This object allows the CPE to be configured to perform the UDP Echo Service defined in {{bibref|RFC862}} and UDP Echo Plus Service defined in {{bibref|TR-143|Appendix A.1}}. MUST be enabled to receive UDP echo. When enabled from a disabled state all related timestamps, statistics and UDP Echo Plus counters are cleared. {{reference|IP-layer interface over which the CPE MUST listen and receive UDP echo requests on}} 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 listen and receive UDP echo requests on all interfaces. Note: Interfaces behind a NAT MAY require port forwarding rules configured in the Gateway to enable receiving the UDP packets. The Source IP address of the UDP echo packet. The CPE MUST only respond to a UDP echo from this source IP address. The UDP port on which the UDP server MUST listen and respond to UDP echo requests. If {{true}} the CPE will perform necessary packet processing for UDP Echo Plus packets. {{true}} if UDP Echo Plus is supported. Incremented upon each valid UDP echo packet received. Incremented for each UDP echo response sent. The number of UDP received bytes including payload and UDP header after the UDPEchoConfig is enabled. The number of UDP responded bytes, including payload and UDP header sent after the UDPEchoConfig is enabled. Time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456, The time that the server receives the first UDP echo packet after the UDPEchoConfig is enabled. Time in UTC, which MUST be specified to microsecond precision. For example: 2008-04-09T15:01:05.123456 The time that the server receives the most recent UDP echo packet.