Re: [nvo3] Fwd: DRAFT Charter Update for Discussion

[Benson Schliesser <[e-mail]>]

Hi, Don. Thanks for the specific, constructive feedback.

The sparseness was an intentional choice aimed at making the charter more
concise. But I'm perfectly comfortable admitting that I may have taken it
too far... Your proposed text seems like a pretty good improvement to me.

I'd be interested in hearing feedback from other participants here.

Cheers,
-Benson





On Thu, Aug 14, 2014 at 9:19 AM, Fedyk, Don <[e-mail]> wrote:

>  The first paragraph seems a little sparse.  One would have to read the
> problem statement and framework to determine the scope.
>
>
>
> My suggestion is expanding something like this:
>
>
>
> An NVO3 solution, also known as a Data Center Virtual Private Network
> (DCVPN), is a set of protocols and/or protocol extensions *that address
> providing both Layer 2 and Layer 3 Services within and between DCVPNs.* *The
> issues addressed include virtualization, multi-tenancy, multi-site,
> mobility, optimization, management and security* *as* described by
> draft-ietf-nvo3-overlay-problem-statement consistent with the approach
> described by draft-ietf-nvo3-framework.
>
>
>
> I’d also suggest expanding NVA and NVE acronyms.
>
>
>
> Cheers,
> Don
>
>    ---------- Forwarded message ----------
> From: *Benson Schliesser* <[e-mail]>
> Date: Fri, Aug 8, 2014 at 4:53 PM
> Subject: DRAFT Charter Update for Discussion
> To: [e-mail]
>
>
> Dear NVO3 Contributors -
>
> As discussed during the NVO3 meeting at IETF-90 in Toronto, the chairs
> have been drafting a new / revised charter for the WG. The latest draft
> charter text is below for your review.
>
> Frankly, we suspect that some of the wording could be further improved to
> be more clear and/or precise. With that in mind we ask for your help -
> please let us know if something seems unclear or if you have suggestions
> for better wording.
>
> If you have feedback please post it to the list for discussion within the
> next 2 weeks.
>
> Thanks,
> -Benson & Matthew
>
> An NVO3 solution, also known as a Data Center Virtual Private Network
> (DCVPN),
> is a set of protocols and/or protocol extensions that address the issues
> described by draft-ietf-nvo3-overlay-problem-statement consistent with the
> approach described by draft-ietf-nvo3-framework.
>
> NVO3 will document DCVPN requirements for both control plane protocol(s)
> and
> data plane encapsulation format(s), as well as management, operational,
> maintenance, troubleshooting, security and OAM protocol requirements.
> Additionally, NVO3 will document common use-cases for DCVPN solutions.
>
> Consistent with the documents described above, the NVO3 WG will document an
> architecture for DCVPNs within a data center environment based on the
> following
> architectural design points:
> -   A logically centralized NVA control plane
> -   Support for an underlay IP data plane between NVEs
>
> Based on this architecture the NVO3 WG will develop one or more NVO3
> solutions.
> This may include documenting applicability of existing protocols,
> contributing
> to the development of protocol extensions by other WGs and/or SDOs, and/or
> developing new protocols as appropriate.
>
> Solutions and/or protocols that were developed outside of the IETF, but not
> developed by another SDO, and that have multiple interoperable
> implementations
> may be adopted by the NVO3 WG for further development, based on WG
> consensus,
> if requested by the authors .
>
> If the NVO3 WG anticipates the adoption of the technologies of another SDO,
> such as the IEEE, as part of any DCVPN solution, it will liaise with that
> SDO
> to ensure the compatibility of the approach.
>
>
>
>