On Thu, Oct 2, 2014 at 1:20 PM, Thomas Narten <[email protected]> wrote:
> > overlay/underlay, I was confused, and had to re-read the charter multiple > > times. In discussing this matter with Adrian, we concluded: "Definitely > > worth a Comment saying "please pick one term and use it" > > Heh. At first reading, this comment didn't make sense to me. > > The WG has consistently used the terms overlay and underlay to mean > different things. NVO3 is about building an *overlay* network over an > existing *underlay* network. Overlay/underlay are two different terms. > > But looking at the charter, it seems we didn't even use "overlay" in > the charter text itself! > That's because I updated it after this email went out - on the telechat - to clarify. If you look at the diff between the two versions of the charter ( http://www.ietf.org/rfcdiff?url1=http%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-nvo3%2Fwithmilestones-01-02.txt&difftype=--html&submit=Go%21&url2=http%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-nvo3%2Fwithmilestones-01-03.txt ) , I changed it from "environment using an IP-based overlay approach" to "environment that assumes an IP-based underlay". Regards, Alia Suggestion: > > Old: > > The purpose of the NVO3 WG is to develop a set of protocols and/or > protocol extensions that enable network virtualization within a > data center (DC) environment that assumes an IP-based underlay. > > New: > > The purpose of the NVO3 WG is to develop a set of protocols and/or > protocol extensions that enable network virtualization USING > OVERLAYS within a data center (DC) environment that assumes an > IP-based underlay NETWORK. > > (Added words captilized to highlight). > > > "Such requirements should consider OAM and security" > > Hopefully LIME will be approved at that same time as this new NVO3 > > charter. > > WFM. > > Thomas > >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
