On Thu, Oct 30, 2014 at 2:55 PM, Larry Kreeger (kreeger) <kree...@cisco.com> wrote: > Hi Tom, > > We do have a term in NVO3 - Tenant System. It is when it comes to > concrete examples that we fall back on the most prominent example of the > VM. > I'm referring to wording in section 3.4:
"From an NVO3 perspective, it should be assumed that where the document uses the term "VM" and "hypervisor", the intention is that the discussion also applies to other systems" > - Larry > > On 10/30/14 2:52 PM, "Tom Herbert" <therb...@google.com> wrote: > >>On Thu, Oct 30, 2014 at 1:50 PM, Behcet Sarikaya <sarikaya2...@gmail.com> >>wrote: >>> Hi Tom, >>> >>> Did you check Linux Containers discussion in the revision? What do you >>>think? >>> >>Thanks for the clarify text. I still wish there was a more networking >>specific term than VM for this, much like we talk about hosts instead >>of machines, but I suppose the use of VM is pretty burned in at this >>point. >> >>Tom >> >>> Regards, >>> >>> Behcet >>> >>> >>> A New Internet-Draft is available from the on-line Internet-Drafts >>>directories. >>> This draft is a work item of the Network Virtualization Overlays >>> Working Group of the IETF. >>> >>> Title : An Architecture for Overlay Networks (NVO3) >>> Authors : David Black >>> Jon Hudson >>> Lawrence Kreeger >>> Marc Lasserre >>> Thomas Narten >>> Filename : draft-ietf-nvo3-arch-02.txt >>> Pages : 31 >>> Date : 2014-10-27 >>> >>> Abstract: >>> This document presents a high-level overview architecture for >>> building overlay networks in NVO3. The architecture is given at a >>> high-level, showing the major components of an overall system. An >>> important goal is to divide the space into individual smaller >>> components that can be implemented independently and with clear >>> interfaces and interactions with other components. It should be >>> possible to build and implement individual components in isolation >>> and have them work with other components with no changes to other >>> components. That way implementers have flexibility in implementing >>> individual components and can optimize and innovate within their >>> respective components without requiring changes to other components. >>> >>> >>> The IETF datatracker status page for this draft is: >>> https://datatracker.ietf.org/doc/draft-ietf-nvo3-arch/ >>> >>> There's also a htmlized version available at: >>> http://tools.ietf.org/html/draft-ietf-nvo3-arch-02 >>> >>> A diff from the previous version is available at: >>> http://www.ietf.org/rfcdiff?url2=draft-ietf-nvo3-arch-02 >>> >>> >>> Please note that it may take a couple of minutes from the time of >>>submission >>> until the htmlized version and diff are available at tools.ietf.org. >>> >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>> >>> _______________________________________________ >>> nvo3 mailing list >>> nvo3@ietf.org >>> https://www.ietf.org/mailman/listinfo/nvo3 >> >>_______________________________________________ >>nvo3 mailing list >>nvo3@ietf.org >>https://www.ietf.org/mailman/listinfo/nvo3 > _______________________________________________ nvo3 mailing list nvo3@ietf.org https://www.ietf.org/mailman/listinfo/nvo3
