NAME

        CL_RFC3404_5_NAPTR_urn - URN resolution


VERIFICATION POINTS

        Verify a NUT process to resolve URN.


TARGET

        Client (ADVANCED)


SYNOPSIS

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


INITIALIZATION


TEST PROCEDURE

        This test sequence is following.
    DNS Client1 (NUT)                               DNS Server1 (TN)
        |                                               |
        | Invoke some application                       |
        |    on NUT (Ex. RCDS or THTTP)                 |
        |                                               |
        |---------------------------------------------->|
        | 1. Send standard query                        |
        |    QNAME="foo.urn.arpa."                      |
        |    QTYPE=NAPTR                                |  
        |                                               |
        |<----------------------------------------------|
        | 2. Send standard query response               |
        |                                               |
        |---------------------------------------------->|
        | 3. Send standard query                        |
        |    QNAME="_rcds._udp.example.com"             |
        |    QTYPE=SRV                                  |  
        |                                               |
        |       or                                      |
        |                                               |
        |    QNAME="_thttp._tcp.example.com"            |
        |    QTYPE=SRV                                  |  
        |                                               |
        v                                               v
        1. DNS Client (NUT) sends a standard query with QNAME = "foo.urn.arpa." type = NAPTR 
        2. DNS Server1 (NUT) transmits a response to DNS Client1 (NUT) with:
           $ORIGIN foo.urn.arpa.
           ;;      order pref flags service          regexp        replacement
           IN NAPTR 100  10  "s" "foolink+I2L+I2C"  ""   _foolink._udp.example.com.
           IN NAPTR 100  20  "s" "rcds+I2C"          ""  _rcds._udp.example.com.
           IN NAPTR 100  30  "s" "thttp+I2L+I2C+I2R" ""  _thttp._tcp.example.com.
        3. DNS Client (NUT) sends a standard query message which one NUT application supporting 
           RCDS includes QNAME = "_rcds._udp.example.com.", type = SRV, the other NUT application 
           supporting THTTP includes QNAME = "_thttp._tcp.example.com", type = SRV. Judgment (Check *3)


JUDGMENT

        3. Received a query message in response to TN sent NAPTR resource record.


TERMINATION

        If NUT has cache function, clear the cache.


REFERENCE

	RFC3403 Dynamic Delegation Discovery System (DDDS)
                Part Three: The Domain Name System (DNS) Database
	        4. NAPTR RR Format 
	RFC3404 Dynamic Delegation Discovery System (DDDS)
	        Part Four: The Uniform Resource Identifiers (URI)
	                      Resolution Application
	        5.1 An Example Using a URN
	RFC2782 A DNS RR for specifying the location of services (DNS SRV)