RE: [Ipsec] draft-ietf-ipsec-ikev2-17.txt

This is hinging one rfc2401bis.  If rfc2401bis is finished quickly, then 
references to AHbis and ESPbis can be used.

Russ

At 02:30 PM 10/4/2004, Charlie Kaufman wrote:
>I couldn't find RFC2402bis and RFC2406bis in forms that could be
>referenced, so no. Are these part of the set that will be advanced
>together? If so, I assume there is some mechanism to get them to all
>reference one another as part of the advancement process.
>
>Pointers to how to make sure this happens would be appreciated.
>
>         --Charlie
>
>-----Original Message-----
>From: Stephen Kent [mailto:kent@bbn.com]
>Sent: Monday, October 04, 2004 9:11 AM
>To: Charlie Kaufman
>Cc: ipsec@ietf.org
>Subject: Re: [Ipsec] draft-ietf-ipsec-ikev2-17.txt
>
>At 10:03 PM -0700 10/2/04, Charlie Kaufman wrote:
> >One more time, with feeling...
> >
> >A couple more last minute changes.
> >
> >       --Charlie
> >
> >H.17 Changes from IKEv2-16 to IKEv2-17 September 2004
> >
> >    1) Removed all references to Alice and Bob, replacing them with
>"the
> >    initiator" and "the responder". Also fixed the corresponding
>he/she,
> >    his/her, and the capitalization of initiator and responder.
> >
> >    2) Changed specification of BER encoded fields to be DER encoded
> >    fields.
> >
> >    3) Removed obsolete reference to CA names appearing in CERTREQ
> >    fields.
> >
> >    4) Fixed the specification of INTERNAL_IPx_SUBNET Configuration
> >    Attributes to indicate that they could be multi-valued.
> >
> >    5) Added informative references to RFC 2402 and RFC 2406.
>
>Charlie,
>
>presumably these are to 2402bis and 2406bis, right?
>
>Steve
>
>_______________________________________________
>Ipsec mailing list
>Ipsec@ietf.org
>https://www1.ietf.org/mailman/listinfo/ipsec

_______________________________________________
Ipsec mailing list
Ipsec@ietf.org
https://www1.ietf.org/mailman/listinfo/ipsec