Hi Benson
This statement strikes me as too terse:
BGP-based solutions to network virtualization within a data center environment
will be developed in the BGP-Enabled Services (BESS) WG.
It almost sounds as if BGP solutions are out of scope for NVO3.
What I think is important is:
If an
Hi Benson,
Sounds good to me. Thanks for the clarification.
Regards,
Osama
From: Benson Schliesser [mailto:bens...@queuefull.net]
Sent: Monday, August 25, 2014 4:49 PM
To: Osama Zia
Cc: nvo3@ietf.org
Subject: Re: [nvo3] Second Draft Charter Update for Discussion
Hi, Osama.
On Mon,
Remote checksum offload is intended to be used to get checksum offload
of encapsulated packets to work with legacy NICs (those that don't
understand encapsulation protocols). I will be posting an
implementation to Linux shortly for GUE and/or Geneve.
Thanks,
Tom
-- Forwarded message
On 26/08/14 21:47, Tom Herbert wrote:
Remote checksum offload is intended to be used to get checksum offload
of encapsulated packets to work with legacy NICs (those that don't
understand encapsulation protocols). I will be posting an
implementation to Linux shortly for GUE and/or Geneve.
This
Code is king. I agree with what you said below.
Tom
On Aug 26, 2014, at 5:09 PM, Anton Ivanov anton.iva...@kot-begemot.co.uk
wrote:
On 26/08/14 21:47, Tom Herbert wrote:
Remote checksum offload is intended to be used to get checksum offload
of encapsulated packets to work with legacy
However, deployed code is the kingdom.
Dino
On Aug 26, 2014, at 3:22 PM, Thomas Nadeau tnad...@lucidvision.com wrote:
Code is king. I agree with what you said below.
Tom
On Aug 26, 2014, at 5:09 PM, Anton Ivanov anton.iva...@kot-begemot.co.uk
wrote:
On 26/08/14 21:47, Tom Herbert
Hi, Larry.
On Aug 25, 2014, at 9:22 PM, Larry Kreeger (kreeger) kree...@cisco.com wrote:
Overall, I think this is much better. I have a few nits inline below.
Thanks for the constructive feedback. Comments inline.
An NVO3 solution is a set of protocols and/or protocol extensions that
FYI. VXLAN has been published as an Independent stream, Informational
RFC. It originally started out as being AD sponsored (by Stewart), but
changed to Independent after Stewart was no longer AD, which caused some
delay.
Any documents that refer to VXLAN can now refer to this RFC.
Thanks,
