Re: complication in ikev2

Antonio Forzieri <antonio.forzieri@cefriel.it> Thu, 27 March 2003 16:00 UTC

Message-ID: <3E8304FB.7080608@cefriel.it>
Date: Thu, 27 Mar 2003 15:04:43 +0100
From: Antonio Forzieri <antonio.forzieri@cefriel.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; it-IT; rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: ipsec@lists.tislabs.com
Subject: Re: complication in ikev2
References: <3E81AD91.6010806@roc.co.in>
In-Reply-To: <3E81AD91.6010806@roc.co.in>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ravi ha scritto:
> May I know why ikev2 should listen on both 500 and 4500.?What purpose 
> does it solve? In my view, we are complicating the protocol and 
> implementation by doing this. If both IKEv1 and IKEv2 exist (most 
> probably they exist as separate processes or tasks and it is easy if we 
> let IKEv1 and V2 exist separately), ikev1 can listen on port 500 and 
> ikev2 listen on 4500.
Agreed. I state this in a previous message, and I was given this response
[COPY&PASTE BEGIN]
=> nothing but the current draft wording suggests that IKE_SA_INIT
always runs over UDP 500. This should be fixed.
[COPY&PASTE END]

[SNIP]


-- 
------------------------------------------------
Antonio Forzieri
CEFRIEL - Politecnico di Milano
Tesista Area E-Service Tecnologies
Tel: 02-23954.334 - email: forzieri@cefriel.it
ICQ# 177683894
------------------------------------------------

complication in ikev2 Ravi
Re: complication in ikev2 Antonio Forzieri