NAME

        SV_RFC1035_2_3_2_order_octets - Order of transmission of octets and bits

VERIFICATION POINTS

        Verify that a NUT transmits correct order of transmission of octets and bits

The order of transmission of the header and data is resolved to the octet level. The order of transmission of octets is the normal order in which they are read in English.

Whenever an octet represents a numeric quantity, the left most bit in the diagram is the high order or most significant bit.

Similarly, whenever a multi-octet field represents a numeric quantity the left most bit of the whole field is the most significant bit. When a multi-octet quantity is transmitted the most significant octet is transmitted first.

TARGET

        Caching Server

SYNOPSIS

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

INITIALIZATION

Network Topology

                                 . domain
        AP Server1 (TN)          DNS Server2
          |A.example.org           |A.ROOT.NET
          |3ffe:501:ffff:101::10   |3ffe:501:ffff:101::20 
          |192.168.1.10            |192.168.1.20
          |                        | 
Net-y   --+--------+---------------+---------- 3ffe:501:ffff:101::/64
                   |                            192.168.1/24
                   |
                   |
                 Router (TN)
                   |3ffe:501:ffff:100::1
                   |192.168.0.1
                   |
                   |
Net-z   --+--------+-----------------+-------- 3ffe:501:ffff:100::/64
          |                          |          192.168.0/24
          |                          |
        DNS Server1 (NUT)          DNS Client1 (TN)
           3ffe:501:ffff:100::XXXX    3ffe:501:ffff:100::20 
           192.168.0.10               192.168.0.20
	

	XXXX: EUI64

Setup

Set the DNS Server1's (NUT) address as above mentioned Network Topology.

Configure the Server1's (NUT) zone file to response query from TN.

Example of root server list:

For IPv4:

.                       3600000         IN      NS      A.ROOT.NET.
A.ROOT.NET.             3600000                 A       192.168.1.20

For IPv6:

.                       3600000         IN      NS      A.ROOT.NET.
A.ROOT.NET.             3600000                 AAAA    3ffe:501:ffff:101::20

Example of example.com zone file:

$TTL    86400           ; TTL of 1 day
@ IN SOA NS1.example.com. root.example.com. (
	2005081600	; serial
	3600		; refresh every 1 hr
	900		; retry every 15 min
	604800		; expire after a week
	3600		; Minimum TTL of a 1 hr
)
;
	IN	NS	NS1.example.com.
NS1	IN	A	192.168.0.10
;

TEST PROCEDURE

        This test sequence is following.

   Client1 (TN)             DNS Server1 (NUT)                 DNS Server2 (TN)
        |                              |                                 |
        |----------------------------->|                                 |
        | 1. Send standard query       |                                 |
        |    QNAME=A.example.org       |                                 |
        |    QTYPE=A                   |                                 |
        |                              |                                 |
        |                              |-------------------------------->|
        |                              | 2. Send standard query          |
        |                              |  QNAME=A.example.org            |
        |                              |  QTYPE=A                        |
        |                              |                                 |
        v                              v                                 v

        1. TN send standard query QNAME=A.example.org, QTYPE=A to NUT.
        2. NUT transmits standard query to DNS Server2 (TN: root name server) (Judgment *2)

Packet Description

1st packet.

Standard query from DNS Client1 (TN) to Server1 (NUT)
IP Header	Source Address	CL1_NETZ
IP Header	Destination Address	NUT_NETZ
UDP Header	Src Port	2000
UDP Header	Dst Port	53
DNS Header	ID	0x1000
	QR	0
	OPCODE	0
	AA	0
	TC	0
	RD	1
	RA	0
	Z	0
	RCODE	0
	QDCOUNT	1
	ANCOUNT	0
	NSCOUNT	0
	ARCOUNT	0
DNS Question section	QNAME	A.example.org
	QTYPE	A (0x0001)
	QCLASS	IN (0x0001)

2nd packet.

Standard query from DNS Server1 (NUT) to Server2 (TN)
IP Header	Source Address	NUT_NETZ
IP Header	Destination Address	SV2_NETY
UDP Header	Src Port	any
UDP Header	Dst Port	53
DNS Header	ID	any
	QR	0
	OPCODE	0
	AA	any
	TC	0
	RD	0
	RA	any
	Z	any(must be numeric quantity)
	RCODE	any
	QDCOUNT	1
	ANCOUNT	0
	NSCOUNT	0
	ARCOUNT	any(must be numeric quantity)
DNS Question section	QNAME	any
	QTYPE	any
	QCLASS	any

Exp.

NUT_NETZ	DNS Server1's (NUT) Net-z address
CL1_NETZ	DNS Client1's (TN) Net-z address
SV2_NETY	DNS Server2's (TN) Net-y address
SV3_NETY	DNS Server3's (TN) Net-y address
SV4_NETY	DNS Server4's (TN) Net-y address

JUDGMENT

        2. Received standard query including QNAME=A.example.org, QTYPE=A.
                *Order of transmission of octets is the normal in which they are read in English.
                        *Check order of transmission of octets in DNS header.
                *The left most bit in the octets is most significant bit.
                        *Check numeric quantity of OPCODE, Z fields in DNS header.
                *The left most bit in the multi-octets field is most significant bit.
                        *Check numeric quantity of QDCOUNT, ANCOUNT, NSCOUNT, ARCOUNT fields in DNS header.

TERMINATION

        None

REFERENCE

        RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION
        2.3.2. Data Transmission Order