[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04

Network Working Group                                       L-E. Jonsson
INTERNET-DRAFT                                                  Ericsson
Expires: September 2005                                   March 22, 2005





                        Interoperability of RFC 3095
            <draft-ietf-rohc-rtp-rfc3095-interoperability-04.txt>


Status of this memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of RFC 3668.

   By submitting this Internet-Draft, I (we) accept the provisions of
   Section 3 of RFC 3978 (BCP 78).

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress".

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This document is a submission of the IETF ROHC WG. Comments should be
   directed to the ROHC WG mailing list, rohc@ietf.org.


Abstract

   RFC 3095 defines a Proposed Standard protocol for RObust Header
   Compression (ROHC). In order to move the standard further to Draft
   Standard status, it is required to demonstrate interoperability for
   all functionality defined by the RFC. This document outlines those
   features to be tested, and also the test status for each feature,
   based on reports from interoperability tests or other proof of
   interoperability.



Jonsson                                                         [Page 1]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004




Table of Contents

   1. Introduction.....................................................2
      1.1. Overview of Test Strategies.................................3
   2. General ROHC Feature Tests.......................................3
   3. Profile 0 Feature Tests..........................................4
   4. Profile 1 Feature Tests..........................................5
      4.1. Header Formats..............................................5
      4.2. Feedback Formats...........................................12
      4.3. Mode Transitions...........................................12
      4.4. Other features.............................................13
   5. Profile 2 Interoperability Tests................................14
      5.1. Header Formats.............................................14
      5.2. Feedback Formats...........................................20
      5.3. Mode Transitions...........................................20
      5.4. Other features.............................................21
   6. Profile 3 Interoperability Tests................................22
      6.1. Header Formats.............................................22
      6.2. Feedback Formats...........................................27
      6.3. Mode Transitions...........................................28
      6.4. Other features.............................................29
   7. Security Considerations.........................................29
   8. IANA Considerations.............................................29
   9. Acknowledgements................................................29
   10. References.....................................................30
   11. Authors' Addresses.............................................30


1. Introduction

   The Internet standards process [1] places a number of requirements on
   a standards track protocol specification. In particular, when
   advancing a protocol from Proposed Standard to Draft Standard level
   it is necessary to demonstrate at least two independent and
   interoperable implementations, from different code bases, of all
   options and features of that protocol. Further, in cases where one or
   more options or features have not been demonstrated in at least two
   interoperable implementations, the specification may advance to Draft
   Standard level only if those options or features are removed.

   The RObust Header Compression (ROHC) framework and initial profiles
   was originally specified in RFC 3095 as a Proposed Standard [2].
   Since the publication of RFC 3095, the protocol has been implemented
   by a number of different parties, who have also performed
   interoperability tests to verify both their implementations and the
   standard itself.

   As part of the process of taking RFC 3095 further to Draft Standard
   level, it has become necessary to clearly define what must be tested,



Jonsson                                                         [Page 2]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


   and also collect the test status for each item. This document aims at
   providing that, by listing all pieces of the RFC 3095 mechanisms
   which must be subject to interoperability testing, as well as
   indicating which tests have so far been conducted and reported. Tests
   for which successful interoperability has been reported from the
   community are marked with a "*". Tests for which successful
   interoperability has NOT been reported MAY be marked "##". The ROHC
   WG chairs have a detailed list of which parties have reported
   interoperability for each item.


1.1. Overview of Test Strategies

   This document basically consists of two parts. First, section 2 lists
   general, profile independent, pieces to be tested, and then the rest
   of the document covers detailed test cases for each profile in
   separate sections.
   All profile test lists have a common structure and covers the
   following test case groups:
   - Interoperable exchange of all header formats
   - Interoperable exchange of feedback data, using all feedback formats
   - All possible mode transitions
   - Other features, such as various encoding mechanisms that use the
     same header formats.

   An interoperable exchange includes compression and transmission, but
   especially correct interpretation and decompression. Correctness is
   assumed to be verified by comparing the uncompressed input header
   with the decompressed output. For feedback data, an interoperable
   exchange assumes a similar procedure in the opposite transmission
   direction. However, since feedback packets are generated by the
   decompressor and terminated by the compressor, there are no original
   data to compare with output data. Correct interpretation of feedback
   data must therefore be ensured by other means. Since robustness is an
   important goal of the ROHC scheme, there are several mechanisms that
   would not be exceedingly tested without operating on the robustness
   limits of those mechanisms. However, it gets extremely complicated to
   define test cases covering all potential combinations of compressed
   headers, loss scenarios, and the resulting decompression. Therefore,
   if not explicitly stated otherwise, tests defined in this document
   assume loss-less transmission between compressor and decompressor.


2. General ROHC Feature Tests

   Although not yet explicitly defined, the ROHC framework includes a
   number of general mechanisms that are common for all profiles. This
   section lists test cases for these framework mechanisms (FW).






Jonsson                                                         [Page 3]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


   Test cases for ROHC framework mechanisms:

    *FW-CID-S.  Interoperable exchange of non-padded and non-segmented
                ROHC small-CID packets without an ADD-CID octet.

    *FW-CID-A.  Interoperable exchange of non-padded and non-segmented
                ROHC small-CID packets with the ADD-CID octet present.

    *FW-CID-L.  Interoperable exchange of non-padded and non-segmented
                ROHC large-CID packets.

    *FW-SEG-1.  Interoperable exchange of ROHC packets segmented with
                the ROHC segmentation scheme, correctly reassembled, and
                validated with the 4-octet segmentation CRC.

    *FW-SEG-2.  Interoperable exchange of ROHC packet segments where a
                lost segment causes the reassembled packet to be
                discarded due to an invalidation by the 4-octet
                segmentation CRC.

    *FW-PAD.    Interoperable exchange of ROHC packets which use ROHC
                padding.

    *FW-FB-1-D. Interoperable exchange of ROHC FEEDBACK-1 data over a
                dedicated ROHC feedback channel.

    *FW-FB-2-D. Interoperable exchange of ROHC FEEDBACK-2 data over a
                dedicated ROHC feedback channel.

    *FW-FB-1-P. Interoperable exchange of ROHC FEEDBACK-1 data through
                piggybacking in ROHC packets.

    *FW-FB-2-P. Interoperable exchange of ROHC FEEDBACK-2 data through
                piggybacking in ROHC packets.

    *FW-FB-1-I. Interoperable exchange of ROHC FEEDBACK-1 data through
                interspersing among ROHC packets.

    *FW-FB-2-I. Interoperable exchange of ROHC FEEDBACK-2 data through
                interspersing among ROHC packets.


3. Profile 0 Feature Tests

   Test cases for ROHC profile 0x0000 (no compression):

    *P0-IR. Interoperable exchange of profile 0x0000 IR packets.

    *P0-NP. Interoperable exchange of profile 0x0000 Normal packets.

    *P0-FB. Interoperable exchange of profile 0x0000 Feedback.



Jonsson                                                         [Page 4]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


4. Profile 1 Feature Tests

   This section lists test cases for ROHC profile 0x0001 (IP/UDP/RTP).


4.1. Header Formats

   Test cases for IR formats:

    *P1-IR-4.  Interoperable exchange of profile 0x0001 IR packets for
               IPv4.

    *P1-IR-6.  Interoperable exchange of profile 0x0001 IR packets for
               IPv6.

    *P1-IRD-4. Interoperable exchange of profile 0x0001 IR-DYN packets
               for IPv4.

    *P1-IRD-6. Interoperable exchange of profile 0x0001 IR-DYN packets
               for IPv6.


   Test cases for CO formats:

    *P1-CO-1. Interoperable exchange of profile 0x0001 UO-0 packets.

    *P1-CO-2. Interoperable exchange of profile 0x0001 UO-1 packets.

    *P1-CO-3. Interoperable exchange of profile 0x0001 UO-1-ID packets.

    *P1-CO-4. Interoperable exchange of profile 0x0001 UO-1-TS packets.

    *P1-CO-5. Interoperable exchange of profile 0x0001 UOR-2 packets.

    *P1-CO-6. Interoperable exchange of profile 0x0001 UOR-2-ID
              packets.

    *P1-CO-7. Interoperable exchange of profile 0x0001 UOR-2-TS
              packets.

    *P1-CO-R1. Interoperable exchange of profile 0x0001 R-0 packets.

    *P1-CO-R2. Interoperable exchange of profile 0x0001 R-0-CRC packets.

    *P1-CO-R3. Interoperable exchange of profile 0x0001 R-1 packets.

    *P1-CO-R4. Interoperable exchange of profile 0x0001 R-1-ID packets.

    *P1-CO-R5. Interoperable exchange of profile 0x0001 R-1-TS packets.





Jonsson                                                         [Page 5]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


   Test cases for optional mechanisms in CO formats:

    *P1-OP-U1. Interoperable exchange of profile 0x0001 compressed
               packets with the UDP checksum enabled (included).

    *P1-OP-U2. Interoperable exchange of profile 0x0001 compressed
               packets with the UDP checksum disabled (not included).

    *P1-OP-I1. Interoperable exchange of profile 0x0001 compressed
               packets with an outer IPv4 header IP-ID value.

    *P1-OP-I2. Interoperable exchange of profile 0x0001 compressed
               packets without an outer IPv4 header IP-ID value.

    *P1-OP-I3. Interoperable exchange of profile 0x0001 compressed
               packets with an inner IPv4 header IP-ID value.

    *P1-OP-I4. Interoperable exchange of profile 0x0001 compressed
               packets without an inner IPv4 header IP-ID value.

   ##P1-OP-A1. Interoperable exchange of profile 0x0001 compressed
               packets with outer list AH data.

    *P1-OP-A2. Interoperable exchange of profile 0x0001 compressed
               packets without outer list AH data.

   ##P1-OP-A3. Interoperable exchange of profile 0x0001 compressed
               packets with inner list AH data.

    *P1-OP-A4. Interoperable exchange of profile 0x0001 compressed
               packets without inner list AH data.

   ##P1-OP-G1. Interoperable exchange of profile 0x0001 compressed
               packets with an outer header GRE checksum.

    *P1-OP-G2. Interoperable exchange of profile 0x0001 compressed
               packets without an outer header GRE checksum.

   ##P1-OP-G3. Interoperable exchange of profile 0x0001 compressed
               packets with an inner header GRE checksum.

    *P1-OP-G4. Interoperable exchange of profile 0x0001 compressed
               packets without an inner header GRE checksum.


   Test cases for extensions to CO formats:

    *P1-EX0-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 0, where the base compressed header does not
               carry a T-bit.




Jonsson                                                         [Page 6]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


    *P1-EX0-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 0, where the base compressed header carries
               a T-bit with value 1.

    *P1-EX0-3. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 0, where the base compressed header carries
               a T-bit with value 0.

    *P1-EX1-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 1, where the base compressed header does not
               carry a T-bit.

    *P1-EX1-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 1, where the base compressed header carries
               a T-bit with value 1.


    *P1-EX1-3. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 1, where the base compressed header carries
               a T-bit with value 0.

    *P1-EX2-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 2, where the base compressed header does not
               carry a T-bit.

    *P1-EX2-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 2, where the base compressed header carries
               a T-bit with value 1.

    *P1-EX2-3. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 2, where the base compressed header carries
               a T-bit with value 0.

    *P1-EX3-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where the SN octet is present (S=1).

    *P1-EX3-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where the SN octet is not present (S=0).

    *P1-EX3-3. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where TS octets are present (R-TS=1).

    *P1-EX3-4. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where no TS octets are present (R-TS=0).

    *P1-EX3-5. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where the ID octet is present (I=1).

    *P1-EX3-6. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where the ID octet is not present (I=0).




Jonsson                                                         [Page 7]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


    *P1-EX3-7. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where inner IP header flags are present
               (ip=1).

    *P1-EX3-8. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where inner IP header flags are not
               present (ip=0).

    *P1-EX3-9. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3, where outer IP header flags are present
               (ip2=1).

    *P1-EX3-10. Interoperable exchange of profile 0x0001 CO packets with
                an Extension 3, where outer IP header flags are not
                present (ip2=0).

   Test cases for additional flags and fields in Extension 3:

    *P1-X3I-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TOS field is present (TOS=1).

    *P1-X3I-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TOS field is not present (TOS=0).

    *P1-X3I-3. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TTL field is present (TTL=1).

    *P1-X3I-4. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TTL field is not present (TTL=0).

   ##P1-X3I-5. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header Protocol/Next Header field is present
               (PR=1).

    *P1-X3I-6. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header Protocol/Next Header field is not present
               (PR=0).

   ##P1-X3I-7. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and inner IP header fields, where inner IP
               header extension headers are present (IPX=1).

    *P1-X3I-8. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and inner IP header fields, where inner IP
               header extension headers are not present (IPX=0).



Jonsson                                                         [Page 8]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004



    *P1-X3O-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TOS field is present (TOS2=1).

    *P1-X3O-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TOS field is not present (TOS2=0).

    *P1-X3O-3. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TTL field is present (TTL2=1).

    *P1-X3O-4. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TTL field is not present (TTL2=0).

   ##P1-X3O-5. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header Protocol/Next Header field is present
               (PR2=1).

    *P1-X3O-6. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header Protocol/Next Header field is not present
               (PR2=0).

   ##P1-X3O-7. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where outer IP
               header extension headers are present (IPX2=1).

    *P1-X3O-8. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where outer IP
               header extension headers are not present (IPX2=0).

    *P1-X3O-9. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header IP-ID field is present (I2=1).

    *P1-X3O-10. Interoperable exchange of profile 0x0001 CO packets with
                an Extension 3 and outer IP header fields, where the
                outer IP header IP-ID field is not present (I2=0).

    *P1-X3R-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and RTP header field, where the RTP PT
               field is present (R-PT=1).

    *P1-X3R-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and RTP header fields, where the RTP PT
               field is not present (R-PT=0).




Jonsson                                                         [Page 9]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


    *P1-X3R-3. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and RTP header fields, where the
               Compressed CSRC list is present (CSRC=1).

    *P1-X3R-4. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and RTP header fields, where the
               Compressed CSRC list is not present (CSRC=0).

    *P1-X3R-5. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and RTP header fields, where TS_STRIDE
               octets are present (TSS=1).

    *P1-X3R-6. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and RTP header fields, where TS_STRIDE
               octets are not present (TSS=0).

   ##P1-X3R-7. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and RTP header fields, where TIME_STRIDE
               octets are present (TIS=1).

    *P1-X3R-8. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and RTP header fields, where TIME_STRIDE
               octets are not present (TIS=0).


   Test cases for IP extension header fields in Extension 3:

   ##P1-X3L-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed header list is present (CL=1).

   ##P1-X3L-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed header list is not present (CL=0).

   ##P1-X3A-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed AH sequence number is present (ASeq=1).

   ##P1-X3A-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed AH sequence number is not present (ASeq=0).

   ##P1-X3E-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed ESP sequence number is present (ESeq=1).

   ##P1-X3E-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed ESP sequence number is not present (ESeq=0).




Jonsson                                                        [Page 10]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


   ##P1-X3G-1. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed GRE sequence number is present (GSeq=1).

   ##P1-X3G-2. Interoperable exchange of profile 0x0001 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed GRE sequence number is not present (GSeq=0).


   Test cases for compressed lists:

    *P1-L0.    Interoperable exchange of profile 0x0001 packets with a
               compressed list using the generic list scheme (ET=0).

   ##P1-L1-1.  Interoperable exchange of profile 0x0001 packets with a
               compressed list using the insertion only scheme (ET=1)
               with a 1-octet insertion bit mask.

   ##P1-L1-2.  Interoperable exchange of profile 0x0001 packets with a
               compressed list using the insertion only scheme (ET=1)
               with a 2-octet insertion bit mask.

    *P1-L2-1.  Interoperable exchange of profile 0x0001 packets with a
               compressed list using the removal only scheme (ET=2) with
               a 1-octet removal bit mask.

   ##P1-L2-2.  Interoperable exchange of profile 0x0001 packets with a
               compressed list using the removal only scheme (ET=2) with
               a 2-octet removal bit mask.

   ##P1-L3.    Interoperable exchange of profile 0x0001 packets with a
               compressed list using the remove then insert scheme
               (ET=3).

    *P1-L-1.   Interoperable exchange of profile 0x0001 packets with a
               compressed list, where the generation identifier (gen_id)
               is present (GP=1).

   ##P1-L-2.   Interoperable exchange of profile 0x0001 packets with a
               compressed list, where the generation identifier (gen_id)
               is not present (GP=0).

    *P1-L-3.   Interoperable exchange of profile 0x0001 packets with a
               compressed list, where the XI fields are 8 bits long
               (PS=1).


    *P1-L-4.   Interoperable exchange of profile 0x0001 packets with a
               compressed list, where the XI fields are 4 bits long
               (PS=1) and m is even.




Jonsson                                                        [Page 11]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


    *P1-L-5.   Interoperable exchange of profile 0x0001 packets with a
               compressed list, where the XI fields are 4 bits long
               (PS=1) and m is odd.


4.2. Feedback Formats

   Test cases for feedback base formats:

    *P1-FB-1. Interoperable exchange of profile 0x0001 FEEDBACK-1
              packets.

    *P1-FB-2. Interoperable exchange of profile 0x0001 FEEDBACK-2
              packets without any feedback options present.

    *P1-FB-3. Interoperable exchange of profile 0x0001 FEEDBACK-2
              packets with feedback options.

   Test cases for feedback options:

    *P1-FBO-1. Interoperable exchange of profile 0x0001 FEEDBACK-2
               packets with the CRC option present.

   ##1-FBO-2. Interoperable exchange of profile 0x0001 FEEDBACK-2
               packets with the REJECT option present.

   ##P1-FBO-3. Interoperable exchange of profile 0x0001 FEEDBACK-2
               packets with the SN-NOT-VALID option present.

    *P1-FBO-4. Interoperable exchange of profile 0x0001 FEEDBACK-2
               packets with the SN option present.

    *P1-FBO-5. Interoperable exchange of profile 0x0001 FEEDBACK-2
               packets with the CLOCK option present.

   ##P1-FBO-6. Interoperable exchange of profile 0x0001 FEEDBACK-2
               packets with the JITTER option present.

    *P1-FBO-7. Interoperable exchange of profile 0x0001 FEEDBACK-2
               packets with the LOSS option present.


4.3. Mode Transitions

   Test cases for mode transitions:

    *P1-MT-UO. Interoperable exchange of profile 0x0001 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Unidirectional to Bi-directional Optimistic mode of
               operation.



Jonsson                                                        [Page 12]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004



    *P1-MT-OR. Interoperable exchange of profile 0x0001 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Optimistic to Bi-directional Reliable mode
               of operation.

    *P1-MT-UR. Interoperable exchange of profile 0x0001 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Unidirectional to Bi-directional Reliable mode of
               operation.

    *P1-MT-RO. Interoperable exchange of profile 0x0001 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Reliable to Bi-directional Optimistic mode
               of operation.

    *P1-MT-OU. Interoperable exchange of profile 0x0001 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Optimistic to Unidirectional mode of
               operation.

    *P1-MT-RU. Interoperable exchange of profile 0x0001 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Reliable to Unidirectional mode of
               operation.


4.4. Other features

   Test cases for encoding mechanisms:

    *P1-ET-US. Interoperable exchange of profile 0x0001 packets with TS
               values transmitted in unscaled W-LSB form.

    *P1-ET-SC. Interoperable exchange of profile 0x0001 packets with TS
               values transmitted based on the Scaled RTP Timestamp
               encoding method.

   ##P1-ET-TB. Interoperable exchange of profile 0x0001 packets with TS
               values transmitted based on the Timer-Based RTP Timestamp
               encoding method.

    *P1-EI-1.  Interoperable exchange of profile 0x0001 IPv4 packets
               with offset IP-ID values in NBO (Network Byte Order).





Jonsson                                                        [Page 13]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


    *P1-EI-2.  Interoperable exchange of profile 0x0001 IPv4 packets
               with offset IP-ID values in non-NBO (non-Network Byte
               Order).


   Test cases for header compression CRC's:

    *P1-CRC-3. Interoperable exchange of profile 0x0001 packets with a
               3-bit CRC, where packets are correctly verified by a
               matching CRC.

    *P1-CRC-7. Interoperable exchange of profile 0x0001 packets with a
               7-bit CRC, where packets are correctly verified by a
               matching CRC.

    *P1-CRC-8. Interoperable exchange of profile 0x0001 packets with a
               8-bit CRC, where packets are correctly verified by a
               matching CRC.


5. Profile 2 Interoperability Tests

   This section lists test cases for ROHC profile 0x0002 (IP/UDP).


5.1. Header Formats

   Test cases for IR formats:

    *P2-IR-4.  Interoperable exchange of profile 0x0002 IR packets for
               IPv4.

    *P2-IR-6.  Interoperable exchange of profile 0x0002 IR packets for
               IPv6.

    *P2-IRD-4. Interoperable exchange of profile 0x0002 IR-DYN packets
               for IPv4.

    *P2-IRD-6. Interoperable exchange of profile 0x0002 IR-DYN packets
               for IPv6.


   Test cases for CO formats:

    *P2-CO-1. Interoperable exchange of profile 0x0002 UO-0 packets.

    *P2-CO-2. Interoperable exchange of profile 0x0002 UO-1 packets.

    *P2-CO-3. Interoperable exchange of profile 0x0002 UOR-2 packets.

    *P2-CO-R1. Interoperable exchange of profile 0x0002 R-0 packets.



Jonsson                                                        [Page 14]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004



    *P2-CO-R2. Interoperable exchange of profile 0x0002 R-0-CRC packets.

    *P2-CO-R3. Interoperable exchange of profile 0x0002 R-1 packets.


   Test cases for optional mechanisms in CO formats:

    *P2-OP-U1. Interoperable exchange of profile 0x0002 compressed
               packets with the UDP checksum enabled (included).

    *P2-OP-U2. Interoperable exchange of profile 0x0002 compressed
               packets with the UDP checksum disabled (not included).

    *P2-OP-I1. Interoperable exchange of profile 0x0002 compressed
               packets with an outer IPv4 header IP-ID value.

    *P2-OP-I2. Interoperable exchange of profile 0x0002 compressed
               packets without an outer IPv4 header IP-ID value.

    *P2-OP-I3. Interoperable exchange of profile 0x0002 compressed
               packets with an inner IPv4 header IP-ID value.

    *P2-OP-I4. Interoperable exchange of profile 0x0002 compressed
               packets without an inner IPv4 header IP-ID value.

   ##P2-OP-A1. Interoperable exchange of profile 0x0002 compressed
               packets with outer list AH data.

   ##P2-OP-A2. Interoperable exchange of profile 0x0002 compressed
               packets without outer list AH data.

   ##P2-OP-A3. Interoperable exchange of profile 0x0002 compressed
               packets with inner list AH data.

   ##P2-OP-A4. Interoperable exchange of profile 0x0002 compressed
               packets without inner list AH data.

   ##P2-OP-G1. Interoperable exchange of profile 0x0002 compressed
               packets with an outer header GRE checksum.

   ##P2-OP-G2. Interoperable exchange of profile 0x0002 compressed
               packets without an outer header GRE checksum.

   ##P2-OP-G3. Interoperable exchange of profile 0x0002 compressed
               packets with an inner header GRE checksum.

   ##P2-OP-G4. Interoperable exchange of profile 0x0002 compressed
               packets without an inner header GRE checksum.





Jonsson                                                        [Page 15]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


   Test cases for extensions to CO formats:

    *P2-EX0.   Interoperable exchange of profile 0x0002 CO packets with
               an Extension 0.

    *P2-EX1.   Interoperable exchange of profile 0x0002 CO packets with
               an Extension 1.

    *P2-EX2.   Interoperable exchange of profile 0x0002 CO packets with
               an Extension 2.

    *P2-EX3-1. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3, where the SN octet is present (S=1).

    *P2-EX3-2. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3, where the SN octet is not present (S=0).

    *P2-EX3-3. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3, where the ID octet is present (I=1).

    *P2-EX3-4. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3, where the ID octet is not present (I=0).

    *P2-EX3-5. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3, where inner IP header flags are present
               (ip=1).

    *P2-EX3-6. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3, where inner IP header flags are not
               present (ip=0).

    *P2-EX3-7. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3, where outer IP header flags are present
               (ip2=1).

    *P2-EX3-8. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3, where outer IP header flags are not
               present (ip2=0).


   Test cases for additional flags and fields in Extension 3:

    *P2-X3I-1. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TOS field is present (TOS=1).

    *P2-X3I-2. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TOS field is not present (TOS=0).





Jonsson                                                        [Page 16]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


    *P2-X3I-3. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TTL field is present (TTL=1).

    *P2-X3I-4. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TTL field is not present (TTL=0).

   ##P2-X3I-5. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header Protocol/Next Header field is present
               (PR=1).



    *P2-X3I-6. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header Protocol/Next Header field is not present
               (PR=0).

   ##P2-X3I-7. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and inner IP header fields, where inner IP
               header extension headers are present (IPX=1).

    *P2-X3I-8. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and inner IP header fields, where inner IP
               header extension headers are not present (IPX=0).

    *P2-X3O-1. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TOS field is present (TOS2=1).

    *P2-X3O-2. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TOS field is not present (TOS2=0).

    *P2-X3O-3. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TTL field is present (TTL2=1).

    *P2-X3O-4. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TTL field is not present (TTL2=0).

   ##P2-X3O-5. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header Protocol/Next Header field is present
               (PR2=1).






Jonsson                                                        [Page 17]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


   ##P2-X3O-6. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header Protocol/Next Header field is not present
               (PR2=0).

   ##P2-X3O-7. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where outer IP
               header extension headers are present (IPX2=1).

   ##P2-X3O-8. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where outer IP
               header extension headers are not present (IPX2=0).

    *P2-X3O-9. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header IP-ID field is present (I2=1).

    *P2-X3O-10. Interoperable exchange of profile 0x0002 CO packets with
                an Extension 3 and outer IP header fields, where the
                outer IP header IP-ID field is not present (I2=0).


   Test cases for IP extension header fields in Extension 3:

   ##P2-X3L-1. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed header list is present (CL=1).

   ##P2-X3L-2. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed header list is not present (CL=0).

   ##P2-X3A-1. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed AH sequence number is present (ASeq=1).

   ##P2-X3A-2. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed AH sequence number is not present (ASeq=0).

   ##P2-X3E-1. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed ESP sequence number is present (ESeq=1).

   ##P2-X3E-2. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed ESP sequence number is not present (ESeq=0).

   ##P2-X3G-1. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed GRE sequence number is present (GSeq=1).



Jonsson                                                        [Page 18]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004



   ##P2-X3G-2. Interoperable exchange of profile 0x0002 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed GRE sequence number is not present (GSeq=0).


   Test cases for compressed lists:

   ##P2-L0.    Interoperable exchange of profile 0x0002 packets with a
               compressed list using the generic list scheme (ET=0).

   ##P2-L1-1.  Interoperable exchange of profile 0x0002 packets with a
               compressed list using the insertion only scheme (ET=1)
               with a 1-octet insertion bit mask.



   ##P2-L1-2.  Interoperable exchange of profile 0x0002 packets with a
               compressed list using the insertion only scheme (ET=1)
               with a 2-octet insertion bit mask.

   ##P2-L2-1.  Interoperable exchange of profile 0x0002 packets with a
               compressed list using the removal only scheme (ET=2) with
               a 1-octet removal bit mask.

   ##P2-L2-2.  Interoperable exchange of profile 0x0002 packets with a
               compressed list using the removal only scheme (ET=2) with
               a 2-octet removal bit mask.

   ##P2-L3.    Interoperable exchange of profile 0x0002 packets with a
               compressed list using the remove then insert scheme
               (ET=3).

   ##P2-L-1.   Interoperable exchange of profile 0x0002 packets with a
               compressed list, where the generation identifier (gen_id)
               is present (GP=1).

   ##P2-L-2.   Interoperable exchange of profile 0x0002 packets with a
               compressed list, where the generation identifier (gen_id)
               is not present (GP=0).

   ##P2-L-3.   Interoperable exchange of profile 0x0002 packets with a
               compressed list, where the XI fields are 8 bits long
               (PS=1).


   ##P2-L-4.   Interoperable exchange of profile 0x0002 packets with a
               compressed list, where the XI fields are 4 bits long
               (PS=1) and m is even.





Jonsson                                                        [Page 19]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


   ##P2-L-5.   Interoperable exchange of profile 0x0002 packets with a
               compressed list, where the XI fields are 4 bits long
               (PS=1) and m is odd.


5.2. Feedback Formats

   Test cases for feedback base formats:

    *P2-FB-1. Interoperable exchange of profile 0x0002 FEEDBACK-1
              packets.

    *P2-FB-2. Interoperable exchange of profile 0x0002 FEEDBACK-2
              packets without any feedback options present.

    *P2-FB-3. Interoperable exchange of profile 0x0002 FEEDBACK-2
              packets with feedback options.

   Test cases for feedback options:

    *P2-FBO-1. Interoperable exchange of profile 0x0002 FEEDBACK-2
               packets with the CRC option present.

   ##P2-FBO-2. Interoperable exchange of profile 0x0002 FEEDBACK-2
               packets with the REJECT option present.

   ##P2-FBO-3. Interoperable exchange of profile 0x0002 FEEDBACK-2
               packets with the SN-NOT-VALID option present.

    *P2-FBO-4. Interoperable exchange of profile 0x0002 FEEDBACK-2
               packets with the SN option present.

    *P2-FBO-5. Interoperable exchange of profile 0x0002 FEEDBACK-2
               packets with the LOSS option present.


5.3. Mode Transitions

   Test cases for mode transitions:

    *P2-MT-UO. Interoperable exchange of profile 0x0002 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Unidirectional to Bi-directional Optimistic mode of
               operation.

    *P2-MT-OR. Interoperable exchange of profile 0x0002 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Optimistic to Bi-directional Reliable mode
               of operation.



Jonsson                                                        [Page 20]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004



    *P2-MT-UR. Interoperable exchange of profile 0x0002 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Unidirectional to Bi-directional Reliable mode of
               operation.

    *P2-MT-RO. Interoperable exchange of profile 0x0002 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Reliable to Bi-directional Optimistic mode
               of operation.

    *P2-MT-OU. Interoperable exchange of profile 0x0002 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Optimistic to Unidirectional mode of
               operation.

    *P2-MT-RU. Interoperable exchange of profile 0x0002 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Reliable to Unidirectional mode of
               operation.


5.4. Other features

   Test cases for encoding mechanisms:

    *P2-EI-1.  Interoperable exchange of profile 0x0002 IPv4 packets
               with offset IP-ID values in NBO (Network Byte Order).

    *P2-EI-2.  Interoperable exchange of profile 0x0002 IPv4 packets
               with offset IP-ID values in non-NBO (non-Network Byte
               Order).


   Test cases for header compression CRC's:

    *P2-CRC-3. Interoperable exchange of profile 0x0002 packets with a
               3-bit CRC, where packets are correctly verified by a
               matching CRC.

    *P2-CRC-7. Interoperable exchange of profile 0x0002 packets with a
               7-bit CRC, where packets are correctly verified by a
               matching CRC.

    *P2-CRC-8. Interoperable exchange of profile 0x0002 packets with a
               8-bit CRC, where packets are correctly verified by a
               matching CRC.



Jonsson                                                        [Page 21]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004




6. Profile 3 Interoperability Tests

   This section lists test cases for ROHC profile 0x0003 (IP/ESP).


6.1. Header Formats

   Test cases for IR formats:

     P3-IR-4.  Interoperable exchange of profile 0x0003 IR packets for
               IPv4.

     P3-IR-6.  Interoperable exchange of profile 0x0003 IR packets for
               IPv6.


     P3-IRD-4. Interoperable exchange of profile 0x0003 IR-DYN packets
               for IPv4.

     P3-IRD-6. Interoperable exchange of profile 0x0003 IR-DYN packets
               for IPv6.


   Test cases for CO formats:

     P3-CO-1. Interoperable exchange of profile 0x0003 UO-0 packets.

     P3-CO-2. Interoperable exchange of profile 0x0003 UO-1 packets.

     P3-CO-3. Interoperable exchange of profile 0x0003 UOR-2 packets.

     P3-CO-R1. Interoperable exchange of profile 0x0003 R-0 packets.

     P3-CO-R2. Interoperable exchange of profile 0x0003 R-0-CRC packets.

     P3-CO-R3. Interoperable exchange of profile 0x0003 R-1 packets.


   Test cases for optional mechanisms in CO formats:

     P3-OP-I1. Interoperable exchange of profile 0x0003 compressed
               packets with an outer IPv4 header IP-ID value.

     P3-OP-I2. Interoperable exchange of profile 0x0003 compressed
               packets without an outer IPv4 header IP-ID value.

     P3-OP-I3. Interoperable exchange of profile 0x0003 compressed
               packets with an inner IPv4 header IP-ID value.




Jonsson                                                        [Page 22]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


     P3-OP-I4. Interoperable exchange of profile 0x0003 compressed
               packets without an inner IPv4 header IP-ID value.

     P3-OP-A1. Interoperable exchange of profile 0x0003 compressed
               packets with outer list AH data.

     P3-OP-A2. Interoperable exchange of profile 0x0003 compressed
               packets without outer list AH data.

     P3-OP-A3. Interoperable exchange of profile 0x0003 compressed
               packets with inner list AH data.

     P3-OP-A4. Interoperable exchange of profile 0x0003 compressed
               packets without inner list AH data.

     P3-OP-G1. Interoperable exchange of profile 0x0003 compressed
               packets with an outer header GRE checksum.

     P3-OP-G2. Interoperable exchange of profile 0x0003 compressed
               packets without an outer header GRE checksum.

     P3-OP-G3. Interoperable exchange of profile 0x0003 compressed
               packets with an inner header GRE checksum.

     P3-OP-G4. Interoperable exchange of profile 0x0003 compressed
               packets without an inner header GRE checksum.


   Test cases for extensions to CO formats:

     P3-EX0.   Interoperable exchange of profile 0x0003 CO packets with
               an Extension 0.

     P3-EX1.   Interoperable exchange of profile 0x0003 CO packets with
               an Extension 1.

     P3-EX2.   Interoperable exchange of profile 0x0003 CO packets with
               an Extension 2.

     P3-EX3-1. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3, where the SN octet is present (S=1).

     P3-EX3-2. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3, where the SN octet is not present (S=0).

     P3-EX3-3. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3, where the ID octet is present (I=1).

     P3-EX3-4. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3, where the ID octet is not present (I=0).




Jonsson                                                        [Page 23]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


     P3-EX3-5. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3, where inner IP header flags are present
               (ip=1).

     P3-EX3-6. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3, where inner IP header flags are not
               present (ip=0).

     P3-EX3-7. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3, where outer IP header flags are present
               (ip2=1).

     P3-EX3-8. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3, where outer IP header flags are not
               present (ip2=0).



   Test cases for additional flags and fields in Extension 3:

     P3-X3I-1. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TOS field is present (TOS=1).

     P3-X3I-2. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TOS field is not present (TOS=0).

     P3-X3I-3. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TTL field is present (TTL=1).

     P3-X3I-4. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header TTL field is not present (TTL=0).

     P3-X3I-5. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header Protocol/Next Header field is present
               (PR=1).

     P3-X3I-6. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and inner IP header fields, where the
               inner IP header Protocol/Next Header field is not present
               (PR=0).

     P3-X3I-7. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and inner IP header fields, where inner IP
               header extension headers are present (IPX=1).





Jonsson                                                        [Page 24]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


     P3-X3I-8. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and inner IP header fields, where inner IP
               header extension headers are not present (IPX=0).

     P3-X3O-1. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TOS field is present (TOS2=1).

     P3-X3O-2. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TOS field is not present (TOS2=0).

     P3-X3O-3. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TTL field is present (TTL2=1).

     P3-X3O-4. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header TTL field is not present (TTL2=0).

     P3-X3O-5. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header Protocol/Next Header field is present
               (PR2=1).

     P3-X3O-6. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header Protocol/Next Header field is not present
               (PR2=0).

     P3-X3O-7. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where outer IP
               header extension headers are present (IPX2=1).

     P3-X3O-8. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where outer IP
               header extension headers are not present (IPX2=0).

     P3-X3O-9. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and outer IP header fields, where the
               outer IP header IP-ID field is present (I2=1).

     P3-X3O-10. Interoperable exchange of profile 0x0003 CO packets with
                an Extension 3 and outer IP header fields, where the
                outer IP header IP-ID field is not present (I2=0).









Jonsson                                                        [Page 25]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


   Test cases for IP extension header fields in Extension 3:

     P3-X3L-1. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed header list is present (CL=1).

     P3-X3L-2. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed header list is not present (CL=0).

     P3-X3A-1. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed AH sequence number is present (ASeq=1).

     P3-X3A-2. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed AH sequence number is not present (ASeq=0).

     P3-X3E-1. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed ESP sequence number is present (ESeq=1).

     P3-X3E-2. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed ESP sequence number is not present (ESeq=0).

     P3-X3G-1. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed GRE sequence number is present (GSeq=1).

     P3-X3G-2. Interoperable exchange of profile 0x0003 CO packets with
               an Extension 3 and an IP extension header field, where a
               compressed GRE sequence number is not present (GSeq=0).


   Test cases for compressed lists:

     P3-L0.    Interoperable exchange of profile 0x0003 packets with a
               compressed list using the generic list scheme (ET=0).

     P3-L1-1.  Interoperable exchange of profile 0x0003 packets with a
               compressed list using the insertion only scheme (ET=1)
               with a 1-octet insertion bit mask.

     P3-L1-2.  Interoperable exchange of profile 0x0003 packets with a
               compressed list using the insertion only scheme (ET=1)
               with a 2-octet insertion bit mask.

     P3-L2-1.  Interoperable exchange of profile 0x0003 packets with a
               compressed list using the removal only scheme (ET=2) with
               a 1-octet removal bit mask.



Jonsson                                                        [Page 26]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004



     P3-L2-2.  Interoperable exchange of profile 0x0003 packets with a
               compressed list using the removal only scheme (ET=2) with
               a 2-octet removal bit mask.

     P3-L3.    Interoperable exchange of profile 0x0003 packets with a
               compressed list using the remove then insert scheme
               (ET=3).

     P3-L-1.   Interoperable exchange of profile 0x0003 packets with a
               compressed list, where the generation identifier (gen_id)
               is present (GP=1).

     P3-L-2.   Interoperable exchange of profile 0x0003 packets with a
               compressed list, where the generation identifier (gen_id)
               is not present (GP=0).

     P3-L-3.   Interoperable exchange of profile 0x0003 packets with a
               compressed list, where the XI fields are 8 bits long
               (PS=1).

     P3-L-4.   Interoperable exchange of profile 0x0003 packets with a
               compressed list, where the XI fields are 4 bits long
               (PS=1) and m is even.

     P3-L-5.   Interoperable exchange of profile 0x0003 packets with a
               compressed list, where the XI fields are 4 bits long
               (PS=1) and m is odd.


6.2. Feedback Formats

   Test cases for feedback base formats:

     P3-FB-1. Interoperable exchange of profile 0x0003 FEEDBACK-1
              packets.

     P3-FB-2. Interoperable exchange of profile 0x0003 FEEDBACK-2
              packets without any feedback options present.

     P3-FB-3. Interoperable exchange of profile 0x0003 FEEDBACK-2
              packets with feedback options.


   Test cases for feedback options:

     P3-FBO-1. Interoperable exchange of profile 0x0003 FEEDBACK-2
               packets with the CRC option present.

     P3-FBO-2. Interoperable exchange of profile 0x0003 FEEDBACK-2
               packets with the REJECT option present.



Jonsson                                                        [Page 27]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004



     P3-FBO-3. Interoperable exchange of profile 0x0003 FEEDBACK-2
               packets with the SN-NOT-VALID option present.

     P3-FBO-4. Interoperable exchange of profile 0x0003 FEEDBACK-2
               packets with the SN option present.

     P3-FBO-5. Interoperable exchange of profile 0x0003 FEEDBACK-2
               packets with the LOSS option present.


6.3. Mode Transitions

   Test cases for mode transitions:

     P3-MT-UO. Interoperable exchange of profile 0x0003 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Unidirectional to Bi-directional Optimistic mode of
               operation.

     P3-MT-OR. Interoperable exchange of profile 0x0003 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Optimistic to Bi-directional Reliable mode
               of operation.

     P3-MT-UR. Interoperable exchange of profile 0x0003 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Unidirectional to Bi-directional Reliable mode of
               operation.

     P3-MT-RO. Interoperable exchange of profile 0x0003 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Reliable to Bi-directional Optimistic mode
               of operation.

     P3-MT-OU. Interoperable exchange of profile 0x0003 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Optimistic to Unidirectional mode of
               operation.

     P3-MT-RU. Interoperable exchange of profile 0x0003 packets in one
               continuous sequence, including packets sent before,
               during, and after a complete mode transition from
               Bi-directional Reliable to Unidirectional mode of
               operation.




Jonsson                                                        [Page 28]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004



6.4. Other features

   Test cases for encoding mechanisms:

     P3-EI-1.  Interoperable exchange of profile 0x0003 IPv4 packets
               with offset IP-ID values in NBO (Network Byte Order).

     P3-EI-2.  Interoperable exchange of profile 0x0003 IPv4 packets
               with offset IP-ID values in non-NBO (non-Network Byte
               Order).


   Test cases for header compression CRC's:

     P3-CRC-3. Interoperable exchange of profile 0x0003 packets with a
               3-bit CRC, where packets are correctly verified by a
               matching CRC.

     P3-CRC-7. Interoperable exchange of profile 0x0003 packets with a
               7-bit CRC, where packets are correctly verified by a
               matching CRC.

     P3-CRC-8. Interoperable exchange of profile 0x0003 packets with a
               8-bit CRC, where packets are correctly verified by a
               matching CRC.


7. Security Considerations

   When implementing and testing various protocol mechanisms as
   described in this document, the security issues of [2] should be
   taken into consideration. This document, however, does not imply any
   additional security aspects to be considered.


8. IANA Considerations

   This document does not require any IANA actions.


9. Acknowledgements

   The "RTP Interoperability Statement" draft by Colin Perkins has been
   a valuable source for ideas to this document. Thanks also to Carsten
   Bormann, Vicknesan Ayadurai, Mark West, Kristofer Sandlund and Tommy
   Lundemo for fruitful discussions and comments.







Jonsson                                                        [Page 29]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


10. References

   [1]  Bradner, S., "The Internet Standards Process", RFC 2026, October
        1996.

   [2]  C. Bormann, et al., "RObust Header Compression (ROHC)",
        RFC 3095, July 2001.


11. Authors' Addresses

   Lars-Erik Jonsson
   Ericsson AB
   Box 920
   SE-971 28 Lulea, Sweden
   Phone: +46 70 513 56 21
   Fax:   +46 920 20 20 99
   EMail: lars-erik.jonsson@ericsson.com




































Jonsson                                                        [Page 30]


INTERNET-DRAFT        Interoperability of RFC 3095       March 22, 2004


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights. Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard. Please address the information to the IETF at ietf-
   ipr@ietf.org.


Copyright Statement

   Copyright (C) The Internet Society (2004). This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.






This Internet-Draft expires September 22, 2005.






Jonsson                                                        [Page 31]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/