[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IKEv2 (son-of-ike) draft - IPComp-related comments
dharkins@tibernian.com wrote:
> Please send comments to the list.
Attached are few IPComp-related, mostly editorial, comments.
Thanks,
avram
>1.1 The IKE Protocol
>
> IKE performs mutual authentication between two parties and
> establishes an IKE security association that includes shared secret
> information that can be used to efficiently establish SAs for ESP
> (RFC 2406), AH (RFC 2402) and/or IPcomp (RFC 2393).
s/IPcomp/IPComp/
s/RFC 2393/RFC 3173/
>7.3.1 Proposal Substructure
[...]
> o SPI Size (1 byte) - During phase 1 negotiation this field
> MUST be zero. During phase 2 negotiation it is equal to the
> size, in bytes, of the SPI of the corresponding protocol
> (4 for ESP and AH, 2 for IPcomp).
Current implementations are divided on the size of SPI for IPComp,
leading to a compromise where two-octet field is a SHOULD,
four-octet a MAY, and the receiving node MUST be able to process both
forms (see RFC3173, 4.1. Use of IKE).
A single field size of two-octet could simplify the matter, no doubt,
but such change should first gain implementors' support.
>7.3.2 Transform Substructure
[...]
> For Transform Type 6 (Compression), defined Transform-IDs are:
>
> Name Number Defined In
> RESERVED 0
> IPCOMP_OUI 1 (w/attributes)
> IPCOMP_DEFLATE 2
> (RFC2394)
> IPCOMP_LZS 3
> (RFC2395)
>
> values 4-240 are reserved to IANA. Values 241-255 are for
> private use among mutually consenting parties.
Following RFC 3051, the above should read:
For Transform Type 6 (Compression), defined Transform-IDs are:
Name Number Defined In
RESERVED 0
IPCOMP_OUI 1 (w/attributes)
IPCOMP_DEFLATE 2 (RFC2394)
IPCOMP_LZS 3 (RFC2395)
IPCOMP_LZJH 4 (RFC3051)
values 5-240 are reserved to IANA. Values 241-255 are for
private use among mutually consenting parties.
=== eom ===
>
>
>
References: