NAME

        CL_RFC1034_3_1_LabelLength - Label length


VERIFICATION POINTS

        Verify that a NUT transmits messages name space specifications


TARGET

        Client


SYNOPSIS

	CL_RFC1034_3_1_LabelLength.seq [-tooloption ...]: KOI tool option
	See also DNSConfig.pm


INITIALIZATION


TEST PROCEDURE

	This test sequence is following.

DNS Client1 (NUT) DNS Server1 (TN) | | |--------------------------------------------->| | 1. Send standard query | | QNAME=AAA******A.example.com | | <---63---> | | | |<---------------------------------------------| | 2. Standard query response | | | | | |--------------------------------------------->| | 3. Send standard query | | QNAME=A.example.com | | | |<---------------------------------------------| | 4. Standard query response | | | | | |------------------------------------------> X | | 5. Send standard query | | QNAME=AAA******A.example.com | | <---64---> | | | v v
1. NUT send standard query w/ 63 octets label to TN. Judgment (Check *1) 2. TN send standard query response to NUT. 3. NUT send standard query w/ 1 octets label to TN. Judgment (Check *3) 4. TN send standard query response to NUT. 5. NUT send standard query w/ 64 octets label to TN. Judgment (Check *5)


JUDGMENT

        1. Received standard query w/ label length 63 from NUT.
        3. Received standard query w/ label length 1 from NUT.
        5. Not received standard query w/ label length 64 from NUT.


TERMINATION

        If NUT has cache function, clear the cache.


REFERENCE

	RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES
	3.1. Name space specifications and terminology
	3.5. Preferred name syntax

RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION 2.3.1 Preferred name syntax
RFC1123 Requirements for internet Hosts -- Application and Support 2.1 Host Names and Numbers