On 3/19/15, 1:27 PM, "Tom Herbert" <[email protected]> wrote:
>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? I agree that it is nicer to keep the different components decoupled. I would start with just the adoption of the base draft and go from there to keep things simpler but that¹s just my personal opinion, I don¹t think it really matters all that much. _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
