[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IPComp rfc2393bis-00




>>Additionally, and more importantly is that there is no way to uniquely
>>identify an IPComp Association.  It is entirely possible that 2 systems
>>may have more than 1 IPComp Association (maybe part of an SA bundle with
>>IPSec) using the same compression algo.  
>Again, when the CPI is negotiated in the range 256-61439, what blocks
>implementations from identifying IPComp Associations?

	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.

itojun



Follow-Ups: References: