hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.5.1 Overview | This clause defines request types for the NE to report issues to the ADMF. It is distinct from "Getting Status", in which the ADMF retrieves information from the NE (see clause 6.4). Issues may be: • Relating to a particular XID (including delivery issues with that XID). • Relating to a particular DID. • Relating to th... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.5.2 ReportTaskIssue on given XID | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.5.2.1 Summary | DIRECTION: NE to ADMF. USAGE: The NE shall send a ReportTaskIssue request when it becomes aware of an issue (warning or fault) relating specifically to a particular XID. It shall also be used to follow up on an "OK - Acknowledged" response, to signal that a request has been completed (clause 5.2) successfully or unsucc... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.5.2.2 Task report types | The TaskReportType shall be one of the following: • All clear: non-terminating fault resolved. • Warning: not traffic-affecting. • Non-terminating fault (e.g. currently unable to collect traffic but not terminating). • Terminating fault. The message is used by the NE to indicate that the Task has experienced a terminat... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.5.3 ReportDestinationIssue on given DID | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.5.3.1 Summary | DIRECTION: NE to ADMF. USAGE: The NE shall send a ReportDestinationIssue request when it becomes aware of an issue (warning or fault) relating specifically to a particular DID. It shall also be used to follow up on an "OK - Acknowledged" response, to signal that a request has been completed (clause 5.2) successfully or... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.5.4 ReportNEIssue | DIRECTION: NE to ADMF. USAGE: The NE shall send a ReportNEIssue request when it becomes aware of an issue (warning, alert or fault) relating to the whole NE. NE issues can relate to: • Any hardware or software issue on NE (storage nearly full, power issue). • Current security issue on NE. • Any issues with logging or a... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.6 Message details: pings and keepalives | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.6.1 Ping | DIRECTION: Either direction. USAGE: At any time from the ADMF or NE, to get a response over the X1 interface (does not test X2 or X3 or onward delivery). Table 6.6.1-1: PingRequest Field Description Format M/C/O There shall be no request parameters. ETSI ETSI TS 103 221-1 V1.23.1 (2026-03) 34 Table 6.6.1-2: PingRespons... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.6.2 Keepalive | DIRECTION: The Keepalive command goes from ADMF to NE. USAGE: See below. Table 6.6.2-1: KeepaliveRequest Field Description Format M/C/O There shall be no request parameters. Table 6.6.2-2: KeepaliveResponse Field Description Format M/C/O OK or Error The OK message has no other content. The general errors in clause 6.7 ... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.7 Protocol error details | If the Responder is unable to perform an action requested as part of a Request Message, then it shall respond to that Request Message with an Error Response. An ErrorResponse is a response which has the information from clause 6.1, but the response body has an error code from the list below and a free text field for fu... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8 Message definitions: managing general objects | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.1 CreateObject | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.1.1 Summary | DIRECTION: ADMF to NE. USAGE: Used by the ADMF to add a new Generic Object to the NE. Table 6.8.1.1-1: CreateObjectRequest Field Description Format M/C/O createObject Contains a structure derived from the GenericObject.XSD type. See clause 6.8.1.2. M Table 6.8.1.1-2: CreateObjectResponse Field Description Format M/C/O ... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.1.2 Generic Object Structure | All Generic Objects shall be descended from the abstract X1Object defined in the schema of the present document. The X1Object definition contains the following fields. Table 6.8.1.2-1: X1Object Field Description Format M/C/O objectID Shall uniquely identify the Generic Object at the NE. GenericObjectID (see clause 6.8.... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.1.3 GenericObjectID | A GenericObjectID uniquely identifies a given Generic Object. Derived Generic Object types may introduce further identifier fields, but the GenericObjectID shall be unique for that object at the NE, and shall be the identifier used in relevant Generic Object messages (see clause 6.8). The GenericObjectID shall be given... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.2 ModifyObject | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.2.1 Summary | 6. |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 8.2.1 Summary | DIRECTION: ADMF to NE. USAGE: Used by the ADMF to modify an existing Generic Object on the NE. All the details for the object shall be given (i.e. the modified details and the information that is unchanged) to totally replace the previous object details. Table 6.8.2.1-1: ModifyObjectRequest Field Description Format M/C... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.3 DeleteObject | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.3.1 Summary | DIRECTION: ADMF to NE. USAGE: Used by the ADMF to remove a Generic Object from the NE. Table 6.8.3.1-1: DeleteObjectRequest Field Description Format M/C/O objectID Unique identifier for the object. See clause 6.8.1.3. M Table 6.8.3.1-2: DeleteObjectResponse Field Description Format M/C/O OK or Error The general errors ... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.4 GetObject | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.4.1 Summary | DIRECTION: ADMF to NE. USAGE: Used by the ADMF to retrieve details of a particular Generic Object from the NE. Table 6.8.4.1-1: GetObjectRequest Field Description Format M/C/O objectID Unique identifier for the object. See clause 6.8.1.3. M ETSI ETSI TS 103 221-1 V1.23.1 (2026-03) 39 Table 6.8.4.1-2: GetObjectResponse ... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.5 ListObjectsOfType | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.5.1 Summary | DIRECTION: ADMF to NE. USAGE: Used by the ADMF to retrieve all identifiers (objectIDs) of objects stored at the NE that have a particular type. Table 6.8.5.1-1: ListObjectsOfTypeRequest Field Description Format M/C/O objectType Shall be set to the name of the specific XSD type required. URIQualifiedName (as defined in ... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.6 DeleteAllObjects | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 6.8.6.1 Summary | DIRECTION: ADMF to NE. USAGE: If enabled, the DeleteAllObjects command shall perform a "DeleteObject" command for all Generic Objects on the NE. Table 6.8.6.1-1: DeleteAllObjectsRequest Field Description Format M/C/O There shall be no request parameters. Table 6.8.6.1-2: DeleteAllObjectsResponse Field Description Forma... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 7 Transport and Encoding | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 7.1 Introduction | The present document defines a single profile for transport and encoding of X1 messages. |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 7.2 Profile A | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 7.2.1 Encoding | XML encoding shall be used. An XML schema (XSD) is provided in archive ts_10322101v012301p0.zip which accompanies the present document. In the event of a discrepancy between the XSD and encoding requirements that are stated in the present document, the XSD shall be considered authoritative. With the XSD being authorita... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 7.2.2 Transport layer | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 7.2.2.1 HTTPS and HTTP | HTTPS shall be used as per IETF RFC 2818 [12]. The details relating to HTTP are given in this clause and the details relating to TLS are specified in clause 8.2. In this clause, the term HTTP is used (it is implicit that it is in fact HTTPS i.e. that the HTTP is used over TLS). |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 7.2.2.2 How HTTP is used | The ADMF and NE shall both run HTTP clients and servers: • For messages where the ADMF is the requester, the ADMF shall use its HTTP client and the NE shall use its HTTP server. • For messages where the NE is the requester, the NE shall use its HTTP client and the ADMF shall use its HTTP server. Details in the request:... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 7.2.2.3 Profile | The following profile shall be used: HTTP version 1.1 or HTTP/2 shall be used. ADMF implementations shall support both. Where used, HTTP version 1.1 shall be used as per IETF RFC 7230 [13] and related specifications. NOTE: HTTP/1.1 defaults to the use of "persistent connections" (see IETF RFC 7230 [13], section 6.3). I... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 8 Security | |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 8.1 Overview | This clause details security measures to be implemented for the X1 interface. Other security aspects related to the NE (e.g. secure storage of information, access control) are out of scope of the present document. |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 8.2 Transport Security | 8.2.1 Summary TLS shall be used which provides authentication and authorization, integrity and confidentiality as well as replay protection between the TLS endpoints. ETSI ETSI TS 103 221-1 V1.23.1 (2026-03) 42 |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 8.2.2 Profile | TLS shall be followed, using at least version 1.2 as defined in IETF RFC 5246 [14], supporting the recommendations given in IETF RFC 7525 [16]. New implementations should support TLS 1.3 as defined in IETF RFC 8446 [20]. |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 8.2.3 Key generation, deployment and storage | Apart from requirements given in clauses 8.2.1, 8.2.2 and 8.2.4, aspects concerning the generation, distribution, storage and revocation of key material and certificates are out of scope of the present document. Implementations are encouraged to support best practice e.g. the guidance given in OWASP [i.1] TLS Cheat She... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 8.2.4 Authentication | Implementations shall perform mutual authentication using X.509 certificates following IETF RFC 6125 [17]. Implementations shall ensure that it is configurable which certificates are used. An implementation shall consider the authentication procedure to have succeeded if TLS authentication succeeds and either or both o... |
110c3f54a6d6c21aa1b5ed12398734d0 | 103 221-1 | 8.3 Additional security measures (beyond transport layer) | It will be important to follow general security best practice (e.g. use of firewalls and/or access lists to prevent denial-of-service attacks). This is out of scope of the present document. However, implementers are specifically encouraged to follow XML best practices outlined in the OWASP [i.1] XML Security Cheat Shee... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes (TSS&TP) descriptions for the IPv6 transition technology MAP-E to valaidate its implementation within a cable communications networks. The tests are in reference to ETSI TS 101 569-1 [1], the ETSI specification for IPv6 transition technology. The ... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 101 569-1: "Integrated Broadband Cable Telecommunication Networks (CABLE); Cable Network Transition to IPv6 Part 1: IPv6 Transition Requirements". |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework- - Part 1: General con... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATS Abstract Test Suite B4 (MAP-E) Basic Bridging BroadBand element CPE Customer Premises Equipment DF bit Don't Fragment flag (in IPv4 header) DHCP Dynamic Host Configuration Protocol DMR Default Mapping Rule DNS Domain Name System GW GateWay... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 4 Test Suite Structure | The identifier of the TP is built according to table 1 as recommended in the MTS methodologies. Table 1: TP naming convention for MAP-E TP/<root>/<gr>/<sgr>/<x>/<nn> <root> = root MAP-E Mapping of Address and Port – Encapsulation Mode <gr> = group BR Border Relay CPE Customer Premise Equipment <sgr> = sub-group GWA Gat... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5 Test Purposes (TP) | This clause proposes a TP proforma which is used in the present document. The fields of this proforma as used in the present document are explained in table 2. ETSI ETSI TS 103 239-2 V1.1.1 (2014-12) 7 Table 2: TP proforma field description TP Header TP ID The TP ID is a unique identifier according to the TP naming con... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.1 TPs for BR | |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.1.1 Basic Function | TP Id TP/MAP-E/BR/BF/BV/01 Test objective Check that the IUT supports the functionality of MAP-E base NAT mapping Reference [1]: clause 6.7.10.7 Feature: Packet Encapsulation Initial conditions with { the IUT being properly provisioned and the interfaces are connected & functional } Expected behaviour ensure that { whe... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.1.2 Address Structure | TP Id TP/MAP-E/BR/AS/BV/01 Test objective Check that the IUT supports the functionality of unknown destination response Reference [1]: clause 6.7.10.7 Feature: Packet Encapsulation Initial conditions with { the IUT is properly provisioned the interfaces are connected & functional ] Expected behaviour ensure that { when... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.1.3 Session Control | TP Id TP/MAP-E/BR/SC/BV/01 Test objective Check that the IUT supports session control within port ranges Reference [1]: clause 6.7.9.14 Feature: MAP- E Inbound Session control Initial conditions with { the IUT is properly provisioned the interfaces are connected & functional the IUT is configured for a specific port ra... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.1.4 Anycast Addressing | TP Id TP/MAP-E/BR/AA/BV/01 Test objective Check that the IUT supports Anycast GW addressing Reference [1]: clause 6.7.7.1 Feature: MAP-E Addressing Initial conditions with { the IUT is properly provisioned the interfaces are connected & functional the IUT is configured with an Anycast address ] Expected behaviour ensur... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.1.5 MSS Clamping | TP Id TP/MAP-E/BR/MSSC/BV/01 Test objective Check that the IUT functions with MSS clamping Reference [1]: clause 6.7.7.5 Feature: MSS Clamping Initial conditions with { the physical MTU (Phy-MTU) size being equal or greater than the MAP-E IPv6 packet between all devices and the MAP Tunnel MTU (MAP-MTU) being lower than... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.1.6 Fragmentation | TP Id TP/MAP-E/BR/FRAG/BV/01 Test objective Check that the IUT fragments an HTML IPv4 packet downstream Reference [1]: clause 6.7.7.4 Feature: MTU Size and Fragmentation Initial conditions with { the physical MTU (Phy-MTU) size being equal or greater than the MAP-E IPv6 packet between all devices and the MAP Tunnel MTU... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.2 TPs for CPE | |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.2.1 Gateway Assignment | TP Id TP/MAP-E/CPE/GWA/BV/01 Test objective Check that IUT sends a DHCPv6 Request to the DHCPv6 Server after initialization Reference [1]: clause 6.7.9.1 Feature Device Provisioning Initial conditions with { the IUT is properly provisioned the interfaces are connected & functional } Expected behaviour ensure that { whe... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.2.2 Basic Function | TP Id TP/MAP-E/CPE/BF/BV/01 Test objective Check that the IUT supports the functionality of MAP-E NAT & encapsulation base function Reference [1]: clause 6.7.10.7 Feature: Packet Encapsulation Initial conditions with { the IUT being properly provisioned and the interfaces are connected & functional } Expected behaviour... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.2.3 Address Structure | TP Id TP/MAP-E/CPE/AS/BV/01 Test objective Check that the IUT supports dropping of packets using broadcast IPv4 destination addresses Reference [1]: clause 6.7.10.7 Feature: Packet Encapsulation Initial conditions with { the IUT being properly provisioned and the interfaces are connected & functional } Expected behavio... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.2.4 Fragmentaton | TP Id TP/MAP-E/CPE/FRAG/BV/01 Test objective Check that the IUT fragments an HTML IPv4 packet upstream Reference [1]: clause 6.7.7.4 Feature: MTU Size and Fragmentation Initial conditions with { the physical MTU (Phy-MTU) size being equal or greater than the MAP-E IPv6 packet between all devices and the MAP Tunnel MTU ... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.2.5 MSS Clamping | TP Id TP/MAP-E/CPE/MSSC/BV/01 Test objective Check that the IUT functions with MSS clamping Reference [1]: clause 6.7.7.5 Feature: MSS Clamping Initial conditions with { the physical MTU (Phy-MTU) size being equal or greater than the MAP-E IPv6 packet between all devices and the MAP Tunnel MTU (MAP-MTU) being lower tha... |
6f412d8790d7822a67e4eccf236612f1 | 103 239-2 | 5.2.6 Session Control | TP Id TP/MAP-E/CPE/SC/BV/01 Test objective Check that the IUT supports session control within port ranges Reference [1]: clause 6.7.9.14 Feature: MAP- E Inbound Session control Initial conditions with { the IUT being properly provisioned, and the interfaces are connected & functional, and the IUT is configured for a sp... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 1 Scope | The present document provides requirements on the jitter that need to be considered at the Segment-connection of Voice over IP (VoIP) services, voice band data (VBD) services and conversational video service in an IP Multimedia Subsystem. The present document considers only the transport layer. |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Recommendation ITU-T Y.1540 (2007): "Internet protocol data communication service - IP packet transfer and availability performance parameters". [i.2]... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 3 Definitions and abbreviations | |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access segment: network segment from the customer interface (UNI) to the interface on the customer side of the first Gateway Router ETSI ETSI TS 103 210 V1.2.1 (2014-05) 6 real time service: class of telecommunications service requirin... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: DSLAM Digital Subscriber Line Access Manager ETH Ethernet GSMA GSM Association GW GateWay IAD Integrated Access Device I-BGF Interconnection Border Control Functions IMS IP Multimedia Subsystem IP Internet Protocol IPDV IP packet Delay Variati... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 4 Reference Configuration | Compared to networks and systems that are circuit-based, those based on IP pose distinctly different challenges for planning and achieving the end-to-end performance levels necessary to adequately support the wide array of user applications (voice, data, fax, video, etc.). The fundamental quality objectives for these a... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 4.1 Generic Segment-connection Points | Due to real-world constraints the simplified static divisor approach according to Recommendation ITU-T Y.1542 [i.3] has been chosen for the impairment apportionment between access and transit networks. This approach "divides" the UNI-to-UNI path into three segments and budgets the impairments such that the total object... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 5 Guidance on Segment-connection limits | QoS objectives in Recommendation ITU-T Y.1541 [i.2] are deemed to be applicable when access link speeds are at the T1 or E1 rate and higher. Today many network providers use technologies where they offer access link speeds much smaller then T1or E1. Fortunately, de-jitter buffers in international MGW are often limited ... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 5.1 Guidance on Access Segment limits | The following IPDV limits can be applied for access networks (between TE and included SBC). See figure 3 for details. Table 1: Maximal IPDV values for xDSL and ETH Access Segment Nature of Network Application Jitter Value Access Network (sending side) Voice < 35 ms Conversational video < 5 ms Access Network (receiving ... |
b257e8f1b82761021c10d3f6bba91519 | 103 210 | 5.2 Guidance on Total Transit Segment Limits | The following limits can be applied between: • Segment-connection point A Segment-connection point C. See figure 1 for details. The maximum IPDV value per service provider transit segment (NGN Core) is 5 ms (included SBC). Table 3: Guidance on Limits for IP Packet eXchange (IPX) Networks Nature of Network Jitter val... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for NAT64 technology as defined in RFC 6052 [1] and RFC 6146 [2] which address specific cable industry requirements as defined in ETSI TS 101 569-1 [11] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC ... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 2 References | |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 3 Definitions and abbreviations | |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 101 569-1 [11], ISO/IEC 9646-1 [3] and ISO/IEC 9646-7 [6] apply. |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply. ALG Application Layer Gateway ASP Abstract Services Primitives ATM Abstract Test Method ATS Abstract Test Suite CPE Customer Premises Equipment DHCP Dynamic Host Configuration Protocol DNS Domain Name System FTP File Transfer Protocol GRT Glob... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 4 Abstract test method | This clause describes the ATM used to test the NAT64 technology. |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 4.1 Abstract protocol tester | An abstract protocol tester presented in figure 1 is a process providing the test behaviour for testing an IUT. Thus it will emulate an entity which is capable of proving the IUT functionalities. This type of test architecture provides a situation of communication which is equivalent to real operation between real devi... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 4.2 Test configurations | The test suite for NAT64 uses only a test configuration to cover the different test scenarios where Large Scale NAT (LSN) is the IUT. |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 4.2.1 CF01: LSN as IUT | In this configuration, the LSN is the IUT and the test system simulates an IPv6 client in one side and a IPv4 server in the other side. Figure 3: CF01, LSN equipment is the IUT LSN - IUT Test system (TTCN-3) IPv4 Host - Simulated IPv6 Host - Simulated Test System IPv4/IPv6 Ethernet System Under Test NAT64 Functionality... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 4.3 TTCN-3 Test architecture | In general, a conformance test system architecture based on TTCN-3 is as figure 4 shows. Figure 4: Global test architecture The "System Under Test" (SUT) contains: • The "Implementation Under Test" (IUT), i.e. the object of the test. • The "Upper tester application" enables to trigger or capture some actions (i.e. high... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 4.4.1 TTCN-3 ports | The NAT64 Test Suite implements the following ports: • Ipv6Port, to send and receive IPv6 packets. • Ipv4Port, to send and receive IPv4 packets. • SipPort, to trigger the following SIP actions: authentication and data sending. It can monitor incoming traffic. • RstpPort, to trigger the following RSTP actions: session s... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 4.4.2 Abstract Service Primitives | Abstract service primitives are commands or actions that need to be performed on the IUT in order to trigger certain behaviour or to obtain information about the IUT state. The list of ASP used in the NAT64 ATS is shown in table 1. Table 1: NAT64 Abstract Service Primitives TTCN-3 text Action/Command Description Are ro... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 5 Implemented Test Purposes | Table 2 shows the test purposes from [10] which have been implemented and included in the present document. Table 2: Implemented Test Purposes TP Identifier TC Identifier Group Subgroup PICS Untestable Implemented TP/NAT64/LSN/BF/BV/01 TC_NAT64_LSN_BF_BV_01 LSN Basic Function Yes TP/NAT64/LSN/BF/BV/02 TC_NAT64_LSN_BF_B... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 6 ATS conventions | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 6.1 Naming conventions | This test suite follows the naming convention guidelines provided in [7] and [i.1]. |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 6.1.1 General guidelines | The naming convention is based on the following underlying principles: • Identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents. • Suffixes should not be used except in those specific cases identified in table 3. • Prefixes and suffixes s... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 6.1.2 NAT64 specific TTCN-3 naming conventions | In addition to such general naming conventions, table 4 shows specific naming conventions that apply to the NAT64 technololy TTCN-3 test suite. Table 4: NAT64 specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier NAT64 Module Use upper-case initial letter AtsNat64_ AtsNat64_ Mo... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 6.1.3 Usage of Log statements | All TTCN-3 log statements use the following format: • Three asterisks followed by a blank character. • The TTCN-3 test case or function identifier in which the log statement is defined followed by a colon and a blank character. • One of the log categories: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT followed by a... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 6.1.4 Test Case (TC) identifier | The identifier of the TC is built according to table 5 as recommended in [7]. Table 5: TC naming convention for NAT64 TC_<root>_<gr>_<sgr>_<x>_<nn> <root> = root NAT64 NAT64 <gr> = group LSN LSN as IUT <sgr> = sub-group NP NAT Pools BF Basic Function FRAG Fragmentation ALG Application Layer Gateway MSSC Maximum Segment... |
e99e7465f2de65dedb3a98a74635fdf1 | 103 238-3 | 6.2 On line documentation | Using the T3D tool enables providing on-line documentation browser in HTML, by tagging TTCN-3 comments. These tags are defined in table 6. Table 6: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of... |
443c8f283ffc488872ea282fccb3278f | 103 238-2 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes (TSS&TP) descriptions for the IPv6 transition technology NAT64 to validate its implementation within a cable communications networks. The tests are in reference to [1], the ETSI specifications for IPv6 transition technology. The ISO standard for t... |
443c8f283ffc488872ea282fccb3278f | 103 238-2 | 2 References |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.