Subject: [nvo3] 答复: Request for comments: draft-jain-nvo3-overlay-oam-01.txt

From: Haoweiguo <[email-masked]>
Date: Tue, 4 Mar 2014 08:51:04 +0000

Hi Authors,

Yesterday on L2VPN meeting site, i asked a question and please allow me to repeat the question here again.

Is the solution in your draft only supports unicast ping/trace? or both multicast and unicast ping/trace?

Because overlay network can support both unicast and multicast service, so OAM framework should include both unicast and multicast path connectivity verification functionality.

For unicast, relying on path trace mechanism in your draft, the underlying network fault can be located. Echo request are sent with incremental TTL of outer header, relying on underlying network ICMP function, the underlying network fault can be located.But for multicast traffic, it is hard to rely on this mechanism to locate detail underlying network error.

Further question:

In your draft,i think it has a assumption that underlying network for NVO3 should be IP network, but if underlying network is Ethernet, or TRILL, or SPB network, how can you locate detail underlying network fault?

thanks

weiguo

________________________________

发件人: Kanwar Singh [[email-masked]]
发送时间: 2014年2月14日 4:05
收件人: [email-masked]
抄送: Pradeep Jain; Anil Lohiya; Florin Balus; Kanwar Singh; Vinay Bannai; Ravi Shekhar; Wim Henderickx
主题: [nvo3] Request for comments: draft-jain-nvo3-overlay-oam-01.txt

Greetings All:

We have submitted the draft that proposes Generic Overlay OAM framework and Datapath Failures detection mechanisms.

Please review the same update us with your valuable comments/feedback.

Warm Regards,

- Authors

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.