Hi Diego,
Diego Garcia del Rio :
On BGP-evpn we can use the tunnel-type extended community and add a
new type specifically for vxlan-gpe. Given the backwards compatibility
of vxlan gpe we can assume that a gpe capable end point should be
capable of receiving "classic" vxlan.
[...]
I don't
Comments inline
Yours Irrespectively,
John
> -Original Message-
> From: nvo3 [mailto:nvo3-boun...@ietf.org] On Behalf Of Diego Garcia del
> Rio
> Sent: Wednesday, September 23, 2015 10:02 PM
> To: Larry Kreeger (kreeger)
> Cc: Tom Herbert; Shahram Davari; Anoop Ghanwani; Sandeep Kumar
>
See inline below.
From: nvo3 [mailto:nvo3-boun...@ietf.org] On Behalf Of Anoop Ghanwani
Sent: Thursday, September 24, 2015 12:22 AM
To: Larry Kreeger (kreeger)
Cc: Sandeep Kumar (Sandeep) Relan; nvo3@ietf.org; Shahram Davari
Subject: Re: [nvo3] destination UDP port : draft-ietf-nvo3-vxlan-gpe-00
> What we may want to say, then, is that if a P bit of 0 is used then none of
> the other flags must be set. This would prevent someone from generating a
> packet with a P bit of 0 and trying to use new GPE features.
>
> [Lucy] The P bit is used for version purpose too. The rule is if the GPE
>
FYI, NVGRE is published as an information RFC 7637. Your documents that
reference NVGRE, please use this RFC number.
Thanks
Pankaj
> To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
> Subject: RFC 7637 on NVGRE: Network Virtualization Using Generic Routing
> Encapsulation
> From:
Thanks for the references thomas! I was replying from my phone and had a
hard time finding these.
On Thu, Sep 24, 2015 at 12:24 AM, wrote:
> Hi Diego,
>
> Diego Garcia del Rio :
>
>> On BGP-evpn we can use the tunnel-type extended community and add a
>> new type
On 9/24/15, 8:14 AM, "Lucy yong" wrote:
>
>
>See inline below.
>
>-Original Message-
>From: Tom Herbert [mailto:t...@herbertland.com]
>Sent: Thursday, September 24, 2015 10:08 AM
>To: Lucy yong
>Cc: Anoop Ghanwani; Larry Kreeger (kreeger); Sandeep Kumar (Sandeep)
Larry,
On Thu, Sep 24, 2015 at 6:18 PM, Larry Kreeger (kreeger)
wrote:
>
>
> If I can restate what I think you two agree on, it is: If VXLAN evolves
> independently from VXLAN GPE, then a VXLAN GPE endpoint that understands
> only how to be backward compatible with RFC7348