errata logo graphic

Found 2 records.

Status: Held for Document Update (2)

RFC5858, "IPsec Extensions to Support Robust Header Compression over IPsec", May 2010

Source of RFC: rohc (tsv)

Errata ID: 2277

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2010-05-19
Held for Document Update by: Lars Eggert

Section 4.2, pg. 7 says:


                BEFORE COMPRESSION AND APPLICATION OF ESP
                ----------------------------
          IPv4  |orig IP hdr  |     |      |
                |(any options)| TCP | Data |
                ----------------------------

                 AFTER ROHCOIPSEC COMPRESSION AND APPLICATION OF ESP
               ------------------------------------------------------
         IPv4  | new IP hdr  |     | Cmpr. |    | ROHC | ESP   | ESP|
               |(any options)| ESP | Hdr.  |Data| ICV  |Trailer| ICV|
               ------------------------------------------------------

   Figure 1.  Example of a ROHCoIPsec-Processed Packet

It should say:


                BEFORE COMPRESSION AND APPLICATION OF ESP
                ----------------------------
          IPv4  |orig IP hdr  |     |      |
                |(any options)| TCP | Data |
                ----------------------------

                 AFTER ROHCOIPSEC COMPRESSION AND APPLICATION OF ESP
               ------------------------------------------------------
         IPv4  | new IP hdr  |     | Cmpr. |    | ROHC | ESP   | ESP|
               |(any options)| ESP | Hdr.  |Data| ICV  |Trailer| ICV|
|              --------------------+===================+-------------

|  Figure 1.  Example of a ROHCoIPsec-Processed Packet ( +=====+ in
|             the diagram indicates the plaintext that undergoes ESP
|             protection; the packet actually contains the ciphertext)

Notes:

Rationale:
The lower part of Figure 1 misrepresents the packet format;
in the general case (not ESP NULL encryption), the structure
of the inner part of the ESP tunnel mode packet is hidden by
encryption.
The graphical presentation therefore might mislead the reader.
The suggested Corrected Text tries to avoid this by graphically
marking this part of the packet and adding a short note that the
diagram represents the plaintext structure only.


Errata ID: 2276

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2010-05-19
Held for Document Update by: Lars Eggert

Section 3.2, pg. 5 says:

   The data items contained within the SAD are defined in RFC 4301
   [IPSEC], Section 4.4.2.1.  To support ROHC, the SAD must include a
|  "ROHC Data Item"; this data item contains parameters used by ROHC
   instance.  The ROHC Data Item exists for both inbound and outbound
   SAs.

   The ROHC Data Item includes the ROHC channel parameters for the SA.
   These channel parameters (i.e., MAX_CID, PROFILES, MRRU) are
   enumerated above in Section 3.1.  For inbound SAs, the ROHC Data Item
   MUST specify the ROHC channel parameters that are used by the local
   decompressor instance; conversely, for outbound SAs, the ROHC Data
|  Item MUST specify the ROHC channel parameters that are used by local
   compressor instance.

It should say:

   The data items contained within the SAD are defined in RFC 4301
   [IPSEC], Section 4.4.2.1.  To support ROHC, the SAD must include a
|  "ROHC Data Item"; this data item contains parameters used by the ROHC
   instance.  The ROHC Data Item exists for both inbound and outbound
   SAs.

   The ROHC Data Item includes the ROHC channel parameters for the SA.
   These channel parameters (i.e., MAX_CID, PROFILES, MRRU) are
   enumerated above in Section 3.1.  For inbound SAs, the ROHC Data Item
   MUST specify the ROHC channel parameters that are used by the local
   decompressor instance; conversely, for outbound SAs, the ROHC Data
|  Item MUST specify the ROHC channel parameters that are used by the
   local compressor instance.

Notes:

Rationale: missing definite article (2 instances)


Report New Errata