Hi Tom,
- Original Message -
From: Tom Herbert therb...@google.com
To: Mark ZZZ Smith markzzzsm...@yahoo.com.au
Cc: nvo3@ietf.org nvo3@ietf.org
Sent: Saturday, 6 September 2014, 7:55
Subject: Re: [nvo3] Enhancing Virtual Network Encapsulation with IPv6
On Sat, Aug 16, 2014 at
I'm not sure how practical this is. There's already deployment to use
the flow label as representative of inner flow (like for ECMP hashing,
etc.).
Is this use in the flow label fields of the outer IPv6 packets when they're
the encapsulation protocol between NVEs in the underlay network?
If, as you suggest, multicast is already within scope because we haven't
explicitly excluded it, then I'm fine with the charter text.
Of course multicast is already within scope for the WG. I find myself
scratching my head a bit that anyone thinks that it might not be, and
that wording needs
Hi Benson.
Thanks for the updated charter. Here are some possible wording
clarifications. I do not believe the change the charter in a material
way (and are not intended to). But they may make aspects of it a bit
clearer.
Thomas,
Some Comments:
A Network Virtualization Edge (NVE) that sits at the edge of an
underlay network and provides L2 and/or L3 network virtualization
functions to Tenant Systems
Comment: If NVE resides on a Server that is a host in an underlay network, IMO:
this is not the case that
If Server has an interface to underlay network, I am not sure if we can call
the server as the edge of underlay network.
NVE is the edge of a virtual network.
Lucy
-Original Message-
From: Thomas Narten [mailto:nar...@us.ibm.com]
Sent: Monday, September 08, 2014 4:15 PM
To: Lucy
We need move forward on the framework and live with this statement.
Lucy
-Original Message-
From: Thomas Narten [mailto:nar...@us.ibm.com]
Sent: Monday, September 08, 2014 5:10 PM
To: Lucy yong
Cc: Benson Schliesser; nvo3@ietf.org
Subject: Re: [nvo3] Last Call for Comments on Proposed
One last try to split this nose hair:
NVA: Find logically centralized replace with logically distinguished a
service defined by the NVE-NVA interface
(and not by implementation eg BGP, DHT, X500..)
The NVO3 WG will develop solutions for network virtualization based on the
following
