I think this a good template for an nvo3 gap analysis, however it should
include LISP [RFC6830] in the list of initial candidate technologies.
Provided LISP is added to the list, I'd be supporting adoption (...and
yes, I'm willing to contribute text).
Thanks,
Fabio
On 9/6/13 6:57 AM, Bocci, Matthew (Matthew) wrote:
This email begins a two week poll to help the chairs judge if there is
consensus to adopt draft-gbclt-nvo3-gap-analysis-00.txt as an NVO3
working group draft.
Please respond to this email on the list with 'support' or 'do not
support'.
Please also send any comments on the draft to the NVO3 list.
Please consider whether this draft takes the right basic approach to a
gap analysis, and is a good basis for the work going forward (and
potential future rechartering). It does not have to be perfect at this
stage.
Coincidentally, we are also polling for knowledge of any IPR that
applies to this draft, to ensure that IPR has been disclosed in
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for
more details).
If you are listed as a document author or contributor please respond
to this email whether or not you are aware of any relevant IPR. The
draft will not be adopted until a response has been received from each
author and contributor.
If you are on the NVO3 WG email list but are not listed as an author
or contributor, then please explicitly respond only if you are aware
of any IPR that has not yet been disclosed in conformance with IETF rules.
This poll closes on Friday 20th September.
Regards
Matthew and Benson
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
