Marc,

NVO3 work is not just to repeat what we have done before. I am not aware of a 
specific RFC describes IRB. But as you pointed out, IRB is widely deployed in 
the physical networks today, but it is not in VPN bases. Please look at 
Microsoft hyper-v, it also implements IRB for network virtualization. 

I know that the combination of L2 NVE and L3 NVE can serve some applications 
and it is useful, but it is not equivalent to IRB function. To support IRB 
function, the data plane has to perform MAC address translation and prevent the 
broadcast traffic in one subnet network from sending to another. There is no 
such requirement in current data plane requirement document.  

Hope this convince you a new service type of NVE.

Regards,
Lucy

> -----Original Message-----
> From: LASSERRE, MARC (MARC) [mailto:[email protected]]
> Sent: Thursday, December 13, 2012 4:17 AM
> To: Lucy yong; [email protected]; [email protected]; Bocci, Matthew
> (Matthew)
> Cc: [email protected]; draft-bl-nvo3-dataplane-
> [email protected]
> Subject: RE: [nvo3] FW: New Version Notification for draft-yong-nvo3-
> frwk-dpreq-addition-00.txt
> 
> Lucy,
> 
> The statement "Neither of them naturally supports the communication
> among the VMs
> When some VMs are on the same subnet and other on different" in the
> introduction of
> your draft is inaccurate.
> 
> Integrated routing and switching is configuration/implementation
> specific to a router.
> Can you point to a specific RFC that describes IRB and a new interface
> type?
> This capibility can be enabled as already mentioned in the dataplane
> requirements draft.
> Hence, there is no need to specify a new NVE service type.
> 
> As far as mobility is concerned, I'm finishing up a new section for the
> framework draft.
> 
> Marc
> 
> 
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]] On
> > Behalf Of Lucy yong
> > Sent: Tuesday, December 11, 2012 11:19 PM
> > To: [email protected]; [email protected]; Bocci, Matthew (Matthew)
> > Cc: [email protected];
> > [email protected]
> > Subject: [nvo3] FW: New Version Notification for
> > draft-yong-nvo3-frwk-dpreq-addition-00.txt
> >
> > Hello,
> >
> > FYI. We just upload this draft. It provides additions to the
> > nvo3 framework and data plane requirement beside current
> > documents. The objective of this draft is to merge the
> > suggested text into the framework and data plane requirement
> > documents.
> >
> > Your comments on this are welcome.
> >
> > Regards,
> > Lucy
> >
> > > -----Original Message-----
> > > From: [email protected] [mailto:[email protected]]
> > > Sent: Tuesday, December 11, 2012 4:04 PM
> > > To: Lucy yong
> > > Cc: Linda Dunbar
> > > Subject: New Version Notification for draft-yong-nvo3-frwk-dpreq-
> > > addition-00.txt
> > >
> > >
> > > A new version of I-D, draft-yong-nvo3-frwk-dpreq-addition-00.txt
> > > has been successfully submitted by Lucy Yong and posted to the IETF
> > > repository.
> > >
> > > Filename:  draft-yong-nvo3-frwk-dpreq-addition
> > > Revision:  00
> > > Title:             NVO3 Framework and Data Plane
> > Requirement Addition
> > > Creation date:     2012-12-11
> > > WG ID:             Individual Submission
> > > Number of pages: 9
> > > URL:
> > http://www.ietf.org/internet-drafts/draft-yong-nvo3-
> > > frwk-dpreq-addition-00.txt
> > > Status:
> > http://datatracker.ietf.org/doc/draft-yong-nvo3-frwk-
> > > dpreq-addition
> > > Htmlized:
> > http://tools.ietf.org/html/draft-yong-nvo3-frwk-dpreq-
> > > addition-00
> > >
> > >
> > > Abstract:
> > >    This document describes some additional functions and
> > requirements
> > >    for NVO3 framework [NVO3FRWK] and data plane
> > requirements [DPREQ].
> > >    These additions are necessary in supporting VM communication and
> > >    mobility.
> > >
> > >
> > >
> > >
> > >
> > > The IETF Secretariat
> >
> > _______________________________________________
> > nvo3 mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/nvo3
> >
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to