NAME

  SG_I_RFC2408_5_6_2_2_T - [Initiator Test] Check the Transform to confirm it is valid

TARGET

SGW

SYNOPSIS

  SG_I_RFC2408_5_6_2_2_T.seq [-tooloption ...] -pkt SG_I_RFC2408_5_6_2_2_T.def -tooloption : v6eval tool option
  See also ike_common.def and ike_ipsec.def and ike_addr.def and ike_pkt_ph1_recv.def and ike_pkt_ph2_recv.def

INITIALIZATION

Network Topology

                                 HOST-2(TN)
                                   |3ffe:501:ffff:104::11
                                   |
Net-v   --+------------------------+-------- 3ffe:501:ffff:104::/64
          |
          |
         SGW-2(TN):responder
          |3ffe:501:ffff:103::11
          |                     
Net-w   --+--------+------------------------ 3ffe:501:ffff:103::/64
                   |
                   |
                  ROUTER-2(TN)
                   | 3ffe:501:ffff:102::11
                   |
Net-x   --+--------+------------------------ 3ffe:501:ffff:102::/64
          |
          |3ffe:501:ffff:102::1
         SGW-1(NUT):initiator
          |3ffe:501:ffff:101::1
          |
Net-y   --+--------+------------------------ 3ffe:501:ffff:101::/64
                   |
                   | 3ffe:501:ffff:101::11
                  ROUTER-1(TN)
                   |
                   |
Net-z   -----------+---------------+-------- 3ffe:501:ffff:100::/64
                                   |
                                   |3ffe:501:ffff:100::13
                                 HOST-1(TN)

Verification Points

Ensure the Transforms are presented according to the details given in section 3.6 and 4.2. If the transforms are not formed correctly, the following actions are taken:
(a) Possible events, BAD PROPOSAL SYNTAX, INVALID TRANSFORM, INVALID ATTRIBUTES, are logged in the appropriate system audit file.

(b) An Informational Exchange with a Notification payload containing the BAD-PROPOSAL-SYNTAX, PAYLOAD-MALFORMED or ATTRIBUTES-NOT-SUPPORTED message type MAY be sent to the transmitting entity. This action is dictated by a system security policy.

Configuration

       Transform Payload Format(HOST-2:Responder)
          SA Attributes field : not set (see below)
       Initiator and Responder IKE parameter
At least, following parameter must be included in proposal.
          
          
          
            Machine              
            Src              
            Dest              
            Phase I             
            Phase II
                       
                       
            Ex mode
            Key Value 
            Enc Alg
            Hash Alg           
            Auth Method           
            DH Group           
            PH1 Lt
            IDx
            Proto ID
            Trans ID
            Mode
            Auth Alg
            PH2 Lt
            IDci
            IDcr
            Upper
          
          
            SGW-1           
            SGW-1 addr           
            SGW-2 addr           
            Main  
            IKE-TEST                               
            3DES           
            SHA           
            pre-shared key           
            2           
            8 Hour            
            SGW-1 addr              
            PROTO_IPSEC_ESP  
            ESP_3DES           
            Tunnel           
            HMAC-SHA 
            8 Hour            
            Net-z addr          
            Net-v addr   
            any            
             
             
            SGW-2
            SGW-2 addr
            SGW-1 addr
            Main
            IKE-TEST      
             
             
                        
                        
             
            SGW-2 addr    
            PROTO_IPSEC_ESP 
            ESP_3DES 
            Tunnel
            HMAC-SHA
            8 Hour  
            Net-z addr          
            Net-v addr   
            any
          
          
        
          *Ex Mode = Exchange mode
          *IDx = identity payload(FQDN or user FQDN  can also be chosen as IDx)
          *IDci = identity payload
          *IDcr = identity payload
          *Enc Alg = IKE Encryption Algorithm
          *Hash Alg = IKE Authentication Algorithm
          *Key Value = pre-shared key value
          *PH1 Lt = Phase-1 Lifetime
          *PH2 Lt = Phase-2 Lifetime
          *Proto ID = Protocol Identifier
          *Trans ID = Transform Identifier
          *Mode = Encapsulation Mode
          *Auth Alg = Authentication Algorithm
          *Auth Method = Authentication Method
          *DH Group = Diffie-Hellman Group
          *Upper = Upper Layer Protocol
          *SGW-1 addr = SGW-1 address
          *SGW-2 addr = SGW-2 address
          *Net-z = Net-z network address
          *Net-v = Net-v network address

Pre-Sequence

       In order to start the negotiation of IKE, 
       TN(HOST-1) transmits Echo Request to TN(HOST-2).

TEST PROCEDURE

  This test check is following.


           IDENTITY PROTECTION EXCHANGE


 #   Initiator(NUT)   Direction    Responder(TN)
(1)  HDR; SA         ========>


(2)                  <========       HDR; SA     <-----SA Attributes field : not set(invalid)


(3-A)HDR; KE; NONCE  ========> X                 <-----Must not transmit
         or
(3-B)HDR; N/D        ========>      
                Judgement (Check *1)


   1. Receive the first message from NUT
      In the first message (1), the initiator generates a proposal it
      considers adequate to protect traffic for the given situation.  The
      Security Association, Proposal, and Transform payloads are included
      in the Security Association payload (for notation purposes).


   2. Send the second message from TN
      In the second message (2), the responder indicates the protection
      suite it has accepted with the Security Association, Proposal, and
      Transform payloads. 


   3. Receive the third message from NUT
      In the third message (3-B), the initiator indicates either an ISAKMP
      Notify Payload or an ISAKMP delete Payload.

JUDGEMENT

      The second message must not be accepted. And the third message(3-A) 
      must not be returned (* or BAD-PROPOSAL-SYNTAX, PAYLOAD-MALFORMED or
      ATTRIBUTES-NOT-SUPPORTED  message(3-B) is returned).
      *option : if you want to check the retruned Notify message.

TERMINATION

  Clean up SAD and SPD

REFERENCE

  RFC2408
  5.6 Transform Payload Processing


(omit)


   When a Transform payload is received, the receiving entity (initiator
   or responder) MUST do the following:


   1.  Determine if the Transform is supported.  If the Transform-ID
       field contains an unknown or unsupported value, then that
       Transform payload MUST be ignored and MUST NOT cause the
       generation of an INVALID TRANSFORM event.  If the Transform-ID
       field is invalid, the payload is discarded and the following
       actions are taken:


       (a)  The event, INVALID TRANSFORM, MAY be logged in the
            appropriate system audit file.


       (b)  An Informational Exchange with a Notification payload
            containing the INVALID-TRANSFORM-ID message type MAY be sent
            to the transmitting entity.  This action is dictated by a
            system security policy.


   2.  Ensure the Transforms are presented according to the details
       given in section 3.6 and 4.2.  If the transforms are not formed
       correctly, the following actions are taken:


       (a)  Possible events, BAD PROPOSAL SYNTAX, INVALID TRANSFORM,
            INVALID ATTRIBUTES, are logged in the appropriate system
            audit file.


       (b)  An Informational Exchange with a Notification payload
            containing the BAD-PROPOSAL-SYNTAX, PAYLOAD-MALFORMED or
            ATTRIBUTES-NOT-SUPPORTED message type MAY be sent to the
            transmitting entity.  This action is dictated by a system
            security policy.


   3.  Process the subsequent Transform and Proposal payloads as defined
       by the Next Payload field.  Examples of processing these payloads
       are given in section 4.2.1.