Broadband Radio Access Networks (BRAN); HiperMAN; Conformance Testing for the Network layer of the HiperMAN/WiMAX terminal devices; Part 2: Test Suite Structure and Test Purposes (TSS&TP)

DTS/BRAN-004T009-2

General Information

Status
Published
Publication Date
30-Oct-2008
Current Stage
12 - Completion
Due Date
10-Nov-2008
Completion Date
31-Oct-2008
Ref Project

Buy Standard

Standard
ETSI TS 102 624-2 V1.1.1 (2008-10) - Broadband Radio Access Networks (BRAN); HiperMAN; Conformance Testing for the Network layer of the HiperMAN/WiMAX terminal devices; Part 2: Test Suite Structure and Test Purposes (TSS&TP)
English language
35 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 102 624-2 V1.1.1 (2008-10)
Technical Specification


Broadband Radio Access Networks (BRAN);
HiperMAN;
Conformance Testing for the Network layer of
the HiperMAN/WiMAX terminal devices;
Part 2: Test Suite Structure and Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 102 624-2 V1.1.1 (2008-10)



Reference
DTS/BRAN-004T009-2
Keywords
HiperMAN, layer 3, terminal, testing, TSS&TP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
© WIMAX Forum 2008.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 102 624-2 V1.1.1 (2008-10)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope.5
2 References.5
2.1 Normative references.5
2.2 Informative references.7
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Test Suite Structure (TSS).8
4.1 Structure.8
4.2 Test groups.9
4.2.1 Protocol services.9
4.2.2 Main test types.9
4.2.2.1 Valid Behaviour (BV) tests.9
4.2.2.2 Invalid Behaviour (BI) tests .9
4.2.2.3 Inopportune Behaviour (BO) tests .9
4.2.2.4 Timer and counter (TI) tests.9
5 Test Purposes (TP).9
5.1 Introduction.9
5.1.1 TP definition conventions.9
5.1.2 TP Identifier naming conventions.10
5.1.3 Sources of TP definitions.10
5.1.4 TP selection criteria name convention.10
5.2 Test purposes for MS .11
5.2.1 Network selection and entry .11
5.2.2 DHCP group.11
5.2.2.1 DHCP timer.14
5.2.3 CMIPv4.15
5.2.4 QoS.18
5.2.5 Security.19
5.2.5.1 Device authentication.19
5.2.5.1.1 Retry behaviour.21
5.2.5.1.2 Fragmentation.21
5.2.5.2 User authentication.22
5.2.5.2.1 EAP-AKA.22
5.2.5.2.2 EAP-TTLS.24
5.2.5.3 CMAC Keys.27
5.2.6 IPv6.28
5.2.7 CMIPv6.29
Annex A (informative): Bibliography.34
History .35

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 624-2 V1.1.1 (2008-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Broadband Radio Access
Networks (BRAN).
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 624-2 V1.1.1 (2008-10)
1 Scope
The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the HiperMAN/WiMAX
terminals based on the WiMAX Forum Network Architecture specifications.
The objective of the present document is to provide a basis for conformance tests for WiMAX terminal equipment
giving a high probability of air interface inter-operability between different manufacturers' WiMAX equipment.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [21] and ISO/IEC 9646-2 [22]) as well
as the ETSI rules for conformance testing (ETS 300 406 [20]) are used as a basis for the test methodology.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] WiMAX Forum (V1.2.1): "WiMAX Forum Network Architecture; Stage 1: Architecture Tenets,
Reference Model and Reference Points, Part 1".
NOTE: Available at
http://www.wimaxforum.org/technology/documents/WiMAX_Forum_Network_Architecture_Stage_2-
3_Rel_1v1.2.zip.
[2] WiMAX Forum (V1.2.1): "WiMAX Forum Network Architecture, Stage 2: Architecture Tenets,
Reference Model and Reference Points, Part 2".
NOTE: Available at
http://www.wimaxforum.org/technology/documents/WiMAX_Forum_Network_Architecture_Stage_2-
3_Rel_1v1.2.zip.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 624-2 V1.1.1 (2008-10)
[3] WiMAX Forum (V1.2.1): "WiMAX Forum Network Architecture, Stage 3: Detailed Protocols and
Procedures".
NOTE: Available at
http://www.wimaxforum.org/technology/documents/WiMAX_Forum_Network_Architecture_Stag
e_2-3_Rel_1v1.2.zip.
[4] ETSI TS 102 624-1: "Broadband Radio Access Networks (BRAN); HiperMAN; Conformance
Testing for the Network Layer of HiperMAN/WiMAX terminal devices; Part 1: Protocol
Implementation Conformance Statement (PICS) proforma".
[5] IEEE 802.16e-2005: "IEEE Standard for Local and metropolitan area networks - Part 16: Air
Interface for Fixed and Mobile Broadband Wireless Access Systems. Amendment 2: Physical and
Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and
Corrigendum 1".
NOTE: Available at http://standards.ieee.org/getieee802/802.16.html.
[6] IETF RFC 1256 (September 1991): "ICMP Router Discovery Messages ".
[7] IETF RFC 5216: "The EAP-TLS Authentication Protocol".
[8] IETF RFC 2131 (March 1997): "Dynamic Host Configuration Protocol".
[9] IETF RFC 2132 (March 1997): "DHCP Options and BOOTP Vendor Extensions".
[10] IETF RFC 3344 (August 2002): "IP Mobility Support for IPv4".
[11] IETF RFC 4187 (January 2006): "Extensible Authentication Protocol Method for 3rd Generation
Authentication and Key Agreement (EAP-AKA)".
[12] IETF RFC 5281: "Extensible Authentication Protocol Tunneled Transport Layer Security
Authenticated Protocol Version 0 (EAP-TTLSv0)".
[13] IETF RFC 3748 (June 2004): "Extensible Authentication Protocol (EAP)".
[14] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)".
[15] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration".
[16] IETF RFC 3315 (July 2003): "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[17] IETF RFC 3775 (June 2004): "Mobility Support in IPv6".
[18] IETF RFC 4285 (January 2006): "Authentication Protocol for Mobile IPv6".
[19] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2".
[20] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[21] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts". (See also ITU-T
Recommendation X.290 (1991).
[22] ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 2: Abstract Test Suite specification". (See also ITU-T
Recommendation X.291 (1991).
[23] ISO/IEC 9646-6 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 6: Protocol profile test specification".
[24] ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 7: Implementation Conformance Statement".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 624-2 V1.1.1 (2008-10)
[25] ETSI TS 155 205: "Digital cellular telecommunications system (Phase 2+); Specification of the
GSM-MILENAGE algorithms: An example algorithm set for the GSM Authentication and Key
Generation Functions A3 and A8 (3GPP TS 55.205 version 7.0.0 Release 7)".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
[i.1] ETSI TS 102 178: "Broadband Radio Access Networks (BRAN); HiperMAN; Data Link Control
(DLC) layer".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [24], TS 102 178 [i.1] and
IEEE 802.16e-2005 [5] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [21], ISO/IEC 9646-6 [23],
ISO/IEC 9646-7 [24], TS 102 178 [i.1], IEEE 802.16e-2005 [5] and the following apply:
AKA Authentication and Key Agreement
AVP Attribute Value Pair
BO Inopportune Behaviour
BS Base Station
BU Binding Update
BV Valid Behaviour
DAD Duplicate Address Detection
DHCP Dynamic Host Configuration Protocol
DL Downlink
EAP Extensible Authentication Protocol
FQDN Fully Qualified Domain Name
IP Internet Protocol
ISF Initial Service Flow
IUT Implementation Under Test
MAC Medium Access Control
MS Mobile Station
NAI Network Access Identifier
NAP Network Access Provider
NSP Network Service Provider
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
QoS Quality of Service
TE Test Equipment
TE Test Equipment
TI Timer
TLS Transport Layer Security
TP Test Purposes
TSS Test Suite Structure
TTLS Tunneled Transport Layer Security
UL UplinkBI Invalid Behaviour
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 624-2 V1.1.1 (2008-10)
4 Test Suite Structure (TSS)
4.1 Structure
Figure 1 shows the DLC Test Suite Structure (TSS) including its subgroups defined for conformance testing.
Group Function Sub-function
Network Entry (4.1)
Network Discovery (4.1.2)
Network Selection/re-selection 4.1.2)
Addressing
CMIPv4
 MS Registration
 MS Re-registration
 Session Termination
 CSN anchor mobility
CMIPv6
 MS Registration
 Inter-access Router Handover
 Session Renewal
 Session Termination
IPv6 Stateless address management
 Router Solicitation
 Without Router Solicitation
Client DHCPv4
Discover
Request-Response
Use of DHCP allocated IP address
DHCP Renew
Security
Device authentication (4.4.1.2.1 stg3)
 EAP-TLS
User authentication
 EAP-AKA
 EAP-TTLS
EAP-AKA
EAP-TTLSv0/MS-CHAP-v02
 Certificate Request
 Without Certificate Request
Network Entry and Exit
Nwk Entry - Single EAP (4.5.1.1)
Nwk Entry - Double EAP (4.5.1.2)
Nwk Exit – Normal mode (4.5.2.1)
Nwk Exit – Idle mode (4.5.2.2)
Mobility (CSN anchored) 4.8
Client MIP4 (4.8.3)
Client MIP6 (4.8.4)
IPv6

Figure 1: TSS for WiMAX Forum Network architecture
The test suite is structured as a tree with the root defined as DLC-BS or DLC-MS representing the protocol groups
"DLC for BS" or "DLC for MS". The tree is of rank 3 with the first rank a Group, the second a Function, and the third a
sub-function. The third rank is broken down into the standard ISO conformance test categories CA, BV, BI, BO and TI
(discussed below).
NOTE: For compatibility with TP identifier names in earlier releases of the HiperMAN DLC Test Purposes
document, the protocol group "DLC for MS" in the present document is still denoted "SS".
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 624-2 V1.1.1 (2008-10)
4.2 Test groups
Each test group has a total of three levels. The first level is the protocol services. The second level separates the
protocol services into the various functional areas. The third level are the sub-functional areas. The fourth level, if
required, is used to indicate the initiator (BS or MS) or the direction of communication (DL or UL). This fourth level is
not shown in figure 1.
4.2.1 Protocol services
To be added in the next release.
4.2.2 Main test types
The main test types are the valid behaviour group, the invalid behaviour group and the inopportune behaviour group.
4.2.2.1 Valid Behaviour (BV) tests
This test group shall verify that the IUT reacts in conformity with the base specifications after receipt or exchange of
valid Protocol Data Units (PDUs). Valid PDUs means that the exchange of messages and the content of the exchanged
messages are considered as valid.
4.2.2.2 Invalid Behaviour (BI) tests
This test sub group shall verify that the IUT reacts in conformity with the base specifications after receipt of a
syntactically invalid PDU.
4.2.2.3 Inopportune Behaviour (BO) tests
This test sub group shall verify that the IUT reacts in conformity with the base specifications after receipt of a
syntactically correct PDU not expected in the actual message exchange.
4.2.2.4 Timer and counter (TI) tests
This test group shall verify that the IUT reacts in conformity with the base specifications after expiry of a defined timer
or counter.
5 Test Purposes (TP)
5.1 Introduction
5.1.1 TP definition conventions
The TPs are defined by the rules shown in table 1.
Table 1: TP definition rules
TP Definition Item Item Description
TP Id The TP Id is a unique identifier formed according to the TP naming conventions
defined in the clause below.
WiMAX Forum Nwrk A pointer to the base specification requirement from which the TP is derived
Architecture Reference (specification reference, clause and paragraph).
PICS Item The PICS item(s) associated with this TP.
Initial Condition The IUT's state to which the TP is applied.
Expected behaviour Definition of the events that are expected from the IUT pursuant to the base
specification given a certain stimulus.
Notes Additional optional information provided to the TP reader.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 624-2 V1.1.1 (2008-10)

5.1.2 TP Identifier naming conventions
The identifier of the TP is built according to table 2.
Table 2: TP naming convention
Identifier TP////-H
 = side type MS Mobile Station
 = protocol group CMIPv4 Client Mobile IP v4
 DHCP Dynamic Host Configuration Protocol
 QoS Quality of Service
 SEC Security
 IPv6 IP v6
 CMIPv6 Client Mobile IP v6
= function group To be added in subsequent releases
= subfunction group To be added in subsequent releases
= type of testing To be added in subsequent releases
= sequential number Hnnn (H000, H001, etc.)

5.1.3 Sources of TP definitions
All TPs are specified according to WiMAX Forum Network Architecture Stage 2, and 3 documents [1], [2] and [3].
5.1.4 TP selection criteria name convention
The mapping relationship between selection criteria of the TP and answer items of PICS is listed in table 3.
Table 3: TP Selection Criteria name convention
Identifier Selection Criteria in TP Answer Items in PICS Criteria
1 PIC_CMIPV4 Ax.x [x] MS supports CMIPv4 for address
assignment
2 PIC_EAPAKA Ay.y [x] MS supports EAP-AKA user
authentication.
3 PIC_EAPTTLS Ay.y [x] MS supports EAP-TTLS user
authentication.
4 PIC_DHCPv4 A.2/1 [4] MS supports DHCPv4
5 PIC_CMIPV4 A.2/2 MS supports CMIPv4
6
7
8
9
10
11
12
13

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 624-2 V1.1.1 (2008-10)
5.2 Test purposes for MS
5.2.1 Network selection and entry
TP ID TP/MS/NWE/BV-H000
Reference WFNA Stage3 [3]: section 4.1.2.3.1.
PICS Item
Initial Condition The IUT is attempting network entry using manual mode for NSP selection and NSPs
are available to the IUT as a result of the NSP discovery procedure.
Expected Behaviour Check that: When the IUT has entered and performed successful authentication to
the selected NSP, the IUT indicates the selected NSP.
Test strategy
Notes Requires an upper tester.

TP ID TP/MS/NWE/BV-H0013
Reference WFNA Stage3 [3]: section 4.1.2.3.2.
PICS Item
Initial Condition The IUT is attempting network entry using automatic mode without user intervention
and more NSPs are available including the Home NSP.
Expected Behaviour Check that: The IUT initially selects and attempts authentication with the Home NSP
and if successful the IUT indicates the selected NSP.
Test strategy
Notes Requires an upper tester.

TP ID TP/MS/NWE/BV-H002
Reference WFNA Stage3 [3]: section 4.1.2.2, figure 4-1.
PICS Item
Initial Condition The IUT is attempting network discovery.
Expected Behaviour Check that when the IUT receives a SII-ADV or SBC-RSP with a Base Station ID with
the NSP Identifier flag set to ‘0' (indicating only one NSP associated with NAP) no
more NSP identification operations are performed.
Test strategy
Notes May be difficult to test.

5.2.2 DHCP group
TP ID TP/MS/DHCP/BV-H000
Reference WFNA Stage2p2 [2]: sections 7.2.1.3 and 7.8.1.8.
WFNA Stage3 [3]: sections 4.8.2.1.2.1 and 4.8.2.1.7.1.
RFC 2131 [8]: section 4.3.2.
PICS Item PIC_DHCPv4.
Initial Condition MS uses DHCP (and not MIP) for getting its PoA address from the network.
The MS has completed initial network entry procedures including authentication and
initial service flow (ISF) setup, i.e. initial connection establishment
(DSA-REQ/RSP/ACK).
Expected Behaviour Check that the IUT sends the DHCPDISCOVER message and that the message is
formatted per RFC 2131 [8].
Detailed observation results are described in [2] Stage 3: section 4.8.2.1.7.1.
Test strategy
Notes

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 624-2 V1.1.1 (2008-10)
TP ID TP/MS/DHCP/BV-H001
Reference WFNA Stage2p2 [2]: sections 7.2.1.3 and 7.8.1.8.
WFNA Stage3 [3]: sections 4.8.2.1.2.1 and 4.8.2.1.7.1.
RFC 2131 [8]: section 4.3.2.
PICS Item PIC_DHCPv4
Initial Condition An ISF exists, and the MS has sent an initial DHCPDISCOVER message to the
network over the ISF. The network (TE) has sent a DHCPOFFER message to the
MS.
Expected Behaviour Check that: The MS sends a DHCPREQUEST message to the network over the ISF
(Initial Service Flow) and the DHCPREQUEST message is formatted per
RFC 2131 [8] (section 4.3.2).
Test strategy
Notes

TP ID TP/MS/DHCP/BV-H002
Reference WFNA Stage2p2 [2]: sections 7.2.1.3 and 7.8.1.8.
WFNA Stage3 [3]: sections 4.8.2.1.2 and 4.8.2.1.7.1.
RFC 2131 [8].
PICS Item PIC_DHCPv4
Initial Condition The IUT has sent a DHCPREQUEST message to the network, including a previously
assigned or previously offered IP address (PoA address), and the TE has confirmed
the IP address by sending a DHCPACK message to the IUT.
Expected Behaviour Check that: When the IUT sends an IP packet, the source address of the IP packet is
the assigned IP address.
Test strategy
Notes To make the IUT send an IP packet the network may send an IP packet to the IUT
requesting a response from the MS, e.g. a "ping" message.

TP ID TP/MS/DHCP/BV-H003
Reference WFNA Stage2p2 [2]: sections 7.2.1.3 and 7.8.1.8.
WFNA Stage3 [3]: sections 4.8.2.1.2.1 and 4.8.2.1.7.1.
RFC 2131 [8]: section 4.3.2.
PICS Item PIC_DHCPv4.
Initial Condition An ISF exists, a DHCP renewal has already taken place and the MS has sent a new
DHCPDISCOVER message to the network over the ISF. The network (TE) has sent
a DHCPOFFER message to the MS.
Expected Behaviour Check that: The MS sends a DHCPREQUEST message to the network over the ISF
(Initial Service Flow) and the DHCPREQUEST message is formatted per
RFC 2131 [8] (section 4.3.2).
Test strategy
Notes

TP ID TP/MS/DHCP/BV-H004
Reference WFNA Stage2p2 [2]: sections 7.2.1.3 and 7.8.1.8.
WFNA Stage3 [3]: sections 4.8.2.1.2.1 and 4.8.2.1.7.1.
RFC 2131 [8]: section 4.3.2.
RFC 2132 [9].
PICS Item PIC_DHCPv4.
Initial Condition An ISF exists, and the IUT has sent an initial DHCPDISCOVER message to the
network over the ISF. The network (TE) has sent a DHCPOFFER message to the
IUT. The IUT has responded by sending a DHCPREQUEST message to select the
offered binding.
Expected Behaviour Check that: When the IUT receives a DHCPACK message with valid parameters, the
IUT enters the Bound state.
Test strategy
Notes The Bound state can be checked by the discard of e.g. DHCPACK message from TE
when in Bound state.

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 102 624-2 V1.1.1 (2008-10)
TP ID TP/MS/DHCP/BV-H005
Reference WFNA Stage2p2 [2]: sections 7.2.1.3 and 7.8.1.8.
WFNA Stage3 [3]: sections 4.8.2.1.2.1 and 4.8.2.1.7.1.
RFC 2131 [8]: section 4.3.2.
RFC 2132 [9].
PICS Item PIC_DHCPv4.
Initial Condition The MS has been assigned a network address (PoA) and a lease time from which
timers T1 and T2 are derived. The IUT has sent a DHCPREQUEST message to the
address of the DHCP server that allocated the PoA in order to renew the lease time.
Expected Behaviour Check that: When the IUT receives a DHCPACK message with valid parameters
before expiry of timer T2, the IUT returns to state Bound and continues to use the
assigned network address.
Test strategy
Notes The Bound state can be checked by the discard of e.g. DHCPACK message from TE
when in Bound state.

TP ID TP/MS/DHCP/BV-H006
Reference WFNA Stage2p2 [2]: sections 7.2.1.3 and 7.8.1.8.
WFNA Stage3 [3]: sections 4.8.2.1.2.1 and 4.8.2.1.7.1.
RFC 2131 [8]: section 4.3.2.
RFC 2132 [9].
PICS Item PIC_DHCPv4.
Initial Condition The MS has been assigned a network address (PoA) and a lease time from which
timers T1 and T2 are derived. The IUT has sent a DHCPREQUEST
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.