I completely agree that we shouldn't be duplicating the NEA protocols. OTOH,
I'm willing to consider transport of NEA information within IKE/IPsec if people
are interested. Note that NEA has just only started to look at their own
mainstream transport protocol (NEA-PT). This is very likely to end up being EAP.
Thanks,
Yaron
> -----Original Message-----
> From: ipsec-boun...@ietf.org [mailto:ipsec-boun...@ietf.org] On Behalf Of
> Stephen Kent
> Sent: Saturday, September 12, 2009 10:48
> To: mw...@huawei.com
> Cc: ipsec@ietf.org
> Subject: Re: [IPsec] draft-wong-ipsecme-ikev2-integrity-data-00.txt
>
> At 4:06 PM -0400 9/11/09, Marcus Wong wrote:
> >Steve, you are mostly right, but this I-D only deals with the integrity
> data
> >exchange using the notify payload. Thanks.
> >
> >Marcus
> >
>
> Thanks for the clarification. That still raises the question of why
> we ought to duplicate this NEA functionality in IKE. Does the I-D
> provide suitable motivation for that, and has the idea been passed by
> the NEA WG folks?
>
> Steve
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>
> Scanned by Check Point Total Security Gateway.
_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec
