Hi Anoop,
thank you for the suggestion, it does make lots of sense. Frankly, need to
refresh my memory on this draft.
Would appreciate your review and comments on the work by OOAM-DT.
Regards,
Greg
From: [email protected] [mailto:[email protected]] On Behalf Of Anoop Ghanwani
Sent: Monday, May 23, 2016 4:12 PM
To: Gregory Mirsky
Cc: [email protected]; [email protected]
Subject: Re: [nvo3] FW: New Version Notification for
draft-spallagatti-bfd-vxlan-03.txt
Thanks Greg.
Perhaps what you meant to say was that the Ethertype in the inner MAC header
must be either IPv4 or IPv6.
Anoop
On Mon, May 23, 2016 at 2:46 PM, Gregory Mirsky
<[email protected]<mailto:[email protected]>> wrote:
Hi Anoop, Larry, Shahram, et. al,
thank you for the correction. We’ll address it in the next update.
Regards,
Greg
From: Rtg-bfd
[mailto:[email protected]<mailto:[email protected]>] On Behalf Of
Anoop Ghanwani
Sent: Monday, May 23, 2016 2:35 PM
To: Greg Mirsky
Cc: [email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>
Subject: Re: [nvo3] FW: New Version Notification for
draft-spallagatti-bfd-vxlan-03.txt
Hi Greg,
I think Larry has covered the points I was trying to bring up...if there's a
MAC header present, then the VXLAN GPE next header has to indicate "Ethernet"
rather than "IPv4" or "IPv6".
Thanks,
Anoop
On Mon, May 23, 2016 at 12:47 PM, Greg Mirsky
<[email protected]<mailto:[email protected]>> wrote:
+BFD WG and RTGWG OOAM DT
Hi Anoop,
thank you for your review and the question. The scope of this draft is only for
the VXLAN. The Overlay OAM Desing Team is working on the Requirements, Gap
Analysis and, if there will be required, enhancements and/or new OAM protocols
for BIER, NSH, VXLAN-GPE, GENEVE, and GUE, as defined in its charter. Would
appreciate you review and comments of the two documents the OOAM-DT already
presented in BA meeting:
* OOAM Requirements
* OAM for Overlay Networks: Gap analysis
In the latter you'll find the example to demonstrate applicability of BFD Async
mode in BIER domain. As we've discussed, other BFD may be applied to other
overlay networks that I've listed above even though their method of indication
OAM payload may be different from BIER. Would you agree, or suggest to have
another example of BFD?
Regards, Greg
On Mon, May 23, 2016 at 12:26 PM, Anoop Ghanwani
<[email protected]<mailto:[email protected]>> wrote:
Authors,
In section 4.1, you have this:
>>>
Next Protocol Field in GPE header MUST be set to IPv4 or IPv6.
...
The BFD packet MUST be carried inside the inner MAC frame of the
VxLAN packet. The inner MAC frame carrying the BFD payload has the
following format:
>>>
These two statements seem to contradict each other. If the GPE header
indicates IPv4 or IPv6, then how can the BFD packet be encapsulated within a
MAC frame?
Can you please clarify?
Thanks,
Anoop
On Mon, May 23, 2016 at 8:15 AM, Bocci, Matthew (Nokia - GB)
<[email protected]<mailto:[email protected]>> wrote:
Folks
Please could you direct any discussion on this draft to the NVO3 working
group list.
Regards
Matthew
On 18/04/2016, 07:54, "nvo3 on behalf of Vengada Prasad Govindan
(venggovi)" <[email protected]<mailto:[email protected]> on behalf of
[email protected]<mailto:[email protected]>> wrote:
>Hello all,
> The authors request comments on the draft below.
>Thanks
>Prasad
>
>-----Original Message-----
>From: [email protected]<mailto:[email protected]>
>[mailto:[email protected]<mailto:[email protected]>]
>Sent: Saturday, April 16, 2016 11:33 AM
>To: MALLIK MUDIGONDA (mmudigon)
><[email protected]<mailto:[email protected]>>; Basil Saji
><[email protected]<mailto:[email protected]>>; Greg Mirsky
><[email protected]<mailto:[email protected]>>; Vengada
>Prasad Govindan (venggovi) <[email protected]<mailto:[email protected]>>;
>Juniper Networks
><[email protected]<mailto:[email protected]>>; Sudarsan Paragiri
><[email protected]<mailto:[email protected]>>;
>Santosh Pallagatti <[email protected]<mailto:[email protected]>>;
>[email protected]<mailto:[email protected]>
><[email protected]<mailto:[email protected]>>
>Subject: New Version Notification for draft-spallagatti-bfd-vxlan-03.txt
>
>
>A new version of I-D, draft-spallagatti-bfd-vxlan-03.txt
>has been successfully submitted by Vengada Prasad Govindan and posted to
>the IETF repository.
>
>Name: draft-spallagatti-bfd-vxlan
>Revision: 03
>Title: BFD for VXLAN
>Document date: 2016-04-15
>Group: Individual Submission
>Pages: 9
>URL:
>https://www.ietf.org/internet-drafts/draft-spallagatti-bfd-vxlan-03.txt
>Status:
>https://datatracker.ietf.org/doc/draft-spallagatti-bfd-vxlan/
>Htmlized: https://tools.ietf.org/html/draft-spallagatti-bfd-vxlan-03
>Diff:
>https://www.ietf.org/rfcdiff?url2=draft-spallagatti-bfd-vxlan-03
>
>Abstract:
> This document describes use of Bidirectional Forwarding Detection
> (BFD) protocol for VXLAN .
>
>
>
>
>
>
>Please note that it may take a couple of minutes from the time of
>submission until the htmlized version and diff are available at
>tools.ietf.org<http://tools.ietf.org>.
>
>The IETF Secretariat
>
>_______________________________________________
>nvo3 mailing list
>[email protected]<mailto:[email protected]>
>https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
nvo3 mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
nvo3 mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
