Re: Request for comments: draft-jain-nvo3-overlay-oam-01.txt

[Greg Mirsky <[e-mail]>]

Hi Kanwar, et. al,
the document is certainly interesting and very detailed. But I believe that
it is rather too early to discuss applicability of particular OAM tools
without agreed upon set of requirements for NVO3 OAM and comprehensive gap
analysis.

Regards,
Greg


On Thu, Feb 27, 2014 at 7:46 AM, Kanwar Singh <[e-mail]>wrote;wrote:

> Dear All,
>
> We have submitted the below draft that proposes Generic OAM and Datapath
> Failure Detection Mechanism(s) for Overlay Networks.
>
> We would like to solicit inputs from the members of L2VPN WG.
>
> Please review the same and update us with your inputs/feedback.
>
> Warm Regards
>
> - Kanwar
>
>
>
> A new version of I-D, draft-jain-nvo3-overlay-oam-01.txt has been successfully submitted by Kanwar Singh and posted to the
>
> IETF repository.
>
>
> Name:           draft-jain-nvo3-overlay-oam
> Revision:       01
> Title:          Generic Overlay OAM and Datapath Failure Detection
>
> Document date:  2014-02-12
> Group:          Individual Submission
> Pages:          44
> URL:            http://www.ietf.org/internet-drafts/draft-jain-nvo3-overlay-oam-01.txt
>
> Status:         https://datatracker.ietf.org/doc/draft-jain-nvo3-overlay-oam/
>
> Htmlized:      http://tools.ietf.org/html/draft-jain-nvo3-overlay-oam-01
>
> Diff:              http://www.ietf.org/rfcdiff?url2=draft-jain-nvo3-overlay-oam-01
>
>
> Abstract:
>
>    This proposal describes a mechanism that can be used to detect Data
>
>    Path Failures of various overlay technologies as VXLAN, NVGRE,
>
>    MPLSoGRE and MPLSoUDP and verifying/sanity of their Control and Data
>
>    Plane for given Overlay Segment.  This document defines the following
>
>    for each of the above Overlay Technologies:
>
>    o  Encapsulation of OAM Packet, such that it has same Outer and
>
>       Overlay Header as any End-System's data going over the same
>
>       Overlay Segment.
>
>    o  The mechanism to trace the Underlay that is exercised by any
>
>       Overlay Segment.
>
>    o  Procedure to verify presence of any given Tenant VM or End-System
>
>       within a given Overlay Segment at Overlay End-Point.
>
>    Even though the present proposal addresses Overlay OAM for VXLAN,
>
>    NVGRE, MPLSoGRE and MPLSoUDP, but the procedures described are
>
>    generic enough to accommodate OAM for any other Overlay Technology.
>
>