RFC 5858, "IPsec Extensions to Support Robust Header Compression over IPsec", May 2010
Source of RFC: rohc (tsv)
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)