Hi Team,

I think we can have Introduction and IKE Protocol View [today's Sec.
1.2-1.5] as Section 1 and move Usage scenario to IKE Protocol Details and
Variations.
Usage scenario can make more sense after brief protocol description and it's
difference with IKEv1.

Regards,
Raj

On Thu, Jul 2, 2009 at 2:11 AM, Paul Hoffman <paul.hoff...@vpnc.org> wrote:

> At 7:36 PM +0300 7/1/09, Yaron Sheffer wrote:
> >I'd like to propose:
> >
> >   1.  Introduction
> >     1.1.  Usage Scenarios
> >       1.1.1.  Security Gateway to Security Gateway Tunnel Mode
> >       1.1.2.  Endpoint-to-Endpoint Transport Mode
> >       1.1.3.  Endpoint to Security Gateway Tunnel Mode
> >       1.1.4.  Other Scenarios
> >     1.2.  Requirements Terminology
> >
> >   2.  IKE Protocol Overview (or "Essentials") [today's Sec. 1.2-1.5]
> >     2.1.  The Initial Exchanges
> >     2.2.  The CREATE_CHILD_SA Exchange
> >       2.2.1.  Creating New Child SAs with the CREATE_CHILD_SA
> >               Exchange
> >       2.2.2.  Rekeying IKE SAs with the CREATE_CHILD_SA Exchange
> >       2.2.3.  Rekeying Child SAs with the CREATE_CHILD_SA
> >               Exchange
> >     2.3.  The INFORMATIONAL Exchange
> >       2.3.1.  Deleting an SA with INFORMATIONAL Exchanges
> >     2.4.  Informational Messages outside of an IKE SA
> >
> >   3.  IKE Protocol Details and Variations [today's Sec. 2]
> >
> >   Appendix X: Differences Between RFC 4306 and This Document [today's
> Sec.
> >1.7]
>
> A different idea is to simply rename Section 1 "IKE Protocol Overview", and
> move the requirements terminology (which is, in essence, boilerplate that
> most people ignore anyway) and the differences to appendixes.
>
> >Do you see value in this, or do you prefer keeping the existing order?
>
> I see only minor value to the original proposal, and a high cost to me (the
> editor). I think my alternate proposal isn't so onerous, but am happy to
> follow Yaron's proposal if people really like it.
>
> --Paul Hoffman, Director
> --VPN Consortium
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>
_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec

Reply via email to