[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IPComp rfc2393bis-00
>> If you would like to negotiate the existence/support for IPComp
>> at each end, you will need to perform IKE negotiation for well-known
>> CPI. Is there any other way available for us to check such a
>> situation?
>>
>> Problem: node A has IPComp support, node B has no IPComp support.
>> Under your assumption node A will be using well-known CPI IPComp
>> without negotiating with node B. Packets will be dropped at node B.
>Node A has to offer CPI + Protocol ID + Transform(s)
>where
> The CPI is sent in the SPI field of the proposal, with the SPI size
> field set to match.
>[...]
> In the Internet IP Security Domain of Interpretation (DOI), IPComp is
> negotiated as the Protocol ID PROTO_IPCOMP. The compression
> algorithm is negotiated as one of the defined IPCOMP Transform
> Identifiers.
>What is missing?
Thanks for clarification, I did not notice the following. I would
add a word ONLY, like "and are used ONLY for manual setup".
>> 0-63 define well-known compression algorithms, which require no
>> additional information, and are used for manual setup. The
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
itojun
Follow-Ups:
References: