That seems reasonable. Peter
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stewart Bryant Sent: Friday, April 20, 2012 10:03 AM To: AshwoodsmithPeter Cc: [email protected]; [email protected] Subject: Re: [nvo3] WG Review: Network Virtualization Overlays (nvo3) On 20/04/2012 14:32, AshwoodsmithPeter wrote: >> Any documented solutions will use existing IETF protocols if suitable, or> >> will develop IETF protocols if necessary. > Stuart, Won't that preclude the use of any open source distributed databases ? > > Peter That was not the intention, and I hate to add additional words since the wordier a charter the greater the number of loopholes and lockouts. However, how about: OLD Any documented solutions will use existing IETF protocols if suitable, or will develop IETF protocols if necessary. NEW Any documented solutions will use existing IETF protocols if suitable. Otherwise, the NVO3 WG may propose the development of new IETF protocols, or the writing of an applicability statement for a non-IETF protocol. END Stewart > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Stewart Bryant > Sent: Friday, April 20, 2012 9:21 AM > To: [email protected] > Cc: [email protected] > Subject: Re: [nvo3] WG Review: Network Virtualization Overlays (nvo3) > > On 17/04/2012 17:47, IESG Secretary wrote: >> Driven by the requirements and consistent with the gap analysis, >> the WG may request being rechartered to document solutions >> consisting of one or more data plane encapsulations and >> control plane protocols as applicable. Any documented >> solutions will use existing mechanisms if suitable, or >> will develop new mechanisms if necessary. > There are some changes we should consider > > OLD > Driven by the requirements and consistent with the gap analysis, > the WG may request that work is chartered to document solutions > consisting of one or more data plane encapsulations and > control plane protocols as applicable. > NEW > Driven by the requirements and consistent with the gap analysis, > the WG may request that work be chartered in the IETF to > document solutions consisting of one or more data plane > encapsulations and control plane protocols as applicable. > END > > Reason: > The work may be chartered in NVO3, L2VPN, L3VPN, LISP, > elsewhere or in some combination of the above. Until > we get through requirements and framework we do not know > the right place to do it. > > If the work is already chartered in the IETF the "may" > comes into effect and no new work is chartered. > > OLD > Any documented > solutions will use existing mechanisms if suitable, or > will develop new mechanisms if necessary. > > NEW > Any documented > solutions will use existing IETF protocols if suitable, or > will develop IETF protocols if necessary. > > END > > Reason: > 1) They are protocols and not mechanisms > 2) It had been suggested that we use "standards" but that > may be interpreted to mean "Standards Track RFC" and > hence would be a charter end-run on any IETF protocol that > was informational or experimental. > > > Putting it all together: > > the WG may request that work be chartered in the IETF to > document solutions consisting of one or more data plane > encapsulations and control plane protocols as applicable. > Any documented solutions will use existing IETF protocols > if suitable, or will develop IETF protocols if necessary. > > > - Stewart > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 > -- For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
