On Wed, Nov 4, 2015 at 9:31 PM, Haoweiguo wrote:
> Hi Sam,
>
> The extra bit in VXLAN reserved field has no side effect on regular VXLAN
> forwarding process. The hardware requirements for intermediate nodes is also
> low, the intermediate nodes only need to grab the data
Hi,
I double checked with all of my hardware teams, Reserved bit are usually
ignored on reception so there’s no side effect to vxlan hardware, I believe TCP
also was extended to support ECN this way. Also we are keeping this within
network so server/vm won’t see this traffic.
Now when new
Fully agree. ^_^
在 15-11-5 上午9:46, "Liyizhou" 写入:
>RFC7348 VxLAN itself is an informational document. IMO, being
>informational does not necessarily mean no new bit can be defined. The
>document can be improved to clearly state the applicable scenario and
>compatibility
Just so you know, VXLAN RFC was not WG document, rather independent
submission.
As you are bringing this to NVo3 WG and asking for comments, they are given.
There is nothing wrong in either direction, unless you feel it that way.
-sam
On Wed, Nov 4, 2015 at 5:46 PM, Liyizhou
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 : Generic Protocol Extension for VXLAN
Authors : Paul Quinn