I think draft-herbert-gue-03 should reference draft-hy-nvo3-gue-4-nvo-01 (not referenced, although implied in the language) and draft-hy-gue-4-secure-transport-01 (-00 is referenced in the draft at the moment) to tie this together in the context of virtualization.
With that, I think the three components should be submitted as they are for adoption as three separate drafts making up the sum that is GUE for virtualization. Best regards, Christian -----Original Message----- From: nvo3 [mailto:[email protected]] On Behalf Of Tom Herbert Sent: Thursday, March 19, 2015 1:27 PM To: Benson Schliesser Cc: [email protected] Subject: Re: [nvo3] Call for WG Adoption of draft-herbert-gue-03 On Thu, Mar 19, 2015 at 11:31 AM, Benson Schliesser <[email protected]> wrote: > This message starts a 2-week Call for Adoption of draft-herbert-gue-03 > as a > NVO3 WG item. > Benson asked me to query the list on this... There is a subtlety for GUE. draft-herbert-gue-03 specifies GUE as a generic encapsulation protocol.The use of GUE for network virtualization is specified in draft-hy-nvo3-gue-4-nvo-01. We also specified the security which I believe is critical to NVO3 deployment in draft-hy-gue-4-secure-transport-01. I personally think it's a good idea to keep the general specification somewhat decoupled from the network virtualization use case as we are already seeing deployment use cases for that. But for purposes of WG adoption in NVO3 these is a question as to how we should proceed: Should we request WG adoption for each of these? Is it okay to just request adoption of the primary GUE draft? Should we consolidate these into one draft for NVO3 purposes? Thanks, Tom > The chairs believe that WG consensus is in favor of adoption of this draft. > Please reply to this email thread, to the nvo3 email list, with > expressions of support or opposition. If expressing opposition to > adoption please elaborate substantially on the issues that motivate this view. > > This Call for Adoption will conclude on 2015-03-15, at which times the > chairs will reevaluate their view of consensus based on mailing list > discussion. > > Thanks, > -Benson & Matthew > > > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
