[IPsec] Comments to draft-ietf-ipsecme-eap-mutual-02.txt

Tero Kivinen <kivinen@iki.fi> Tue, 18 May 2010 12:59 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <19442.36613.651993.353644@fireball.kivinen.iki.fi>
Date: Tue, 18 May 2010 15:58:45 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: ipsec@ietf.org
Subject: [IPsec] Comments to draft-ietf-ipsecme-eap-mutual-02.txt
Precedence: list

I read this document and it seems to be mostly ok.

I might disagree on some parts of the section 1 text talking why EAP
is needed (I think the main reason was to support legacy systems. The
public keys are flexible enough to meet requirements of many
deployment scenarios unless your requirement includes "that must
support old legacy infrastructure"), but I do not think there is need
to change text there.

The section 3 should add text telling what protocol ID is used for the
notification, just like most of the other extensions do: "Protocol ID
and the SPI Size fields MUST both be sent as 0.", i.e. change:

                                             The SPI size field is set
   to zero, and there is no additional data associated with this
   notification.

to

                           The protocol ID and SPI size fields are set
   to zero, and there is no additional data associated with this
   notification.
-- 
kivinen@iki.fi

[IPsec] Comments to draft-ietf-ipsecme-eap-mutual… Tero Kivinen
Re: [IPsec] Comments to draft-ietf-ipsecme-eap-mu… Yaron Sheffer