[nvo3] One question about draft draft-tissa-nvo3-oam-fm-00
Haoweiguo <haoweiguo@huawei.com> Fri, 13 June 2014 09:07 UTC
Return-Path: <haoweiguo@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8491A030E for <nvo3@ietfa.amsl.com>; Fri, 13 Jun 2014 02:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rq9cMoKccvo8 for <nvo3@ietfa.amsl.com>; Fri, 13 Jun 2014 02:07:09 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EABC1A038C for <nvo3@ietf.org>; Fri, 13 Jun 2014 02:07:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BFJ38175; Fri, 13 Jun 2014 09:07:07 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Jun 2014 10:07:05 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Fri, 13 Jun 2014 17:07:02 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: "tsenevir@cisco.com" <tsenevir@cisco.com>
Thread-Topic: One question about draft draft-tissa-nvo3-oam-fm-00
Thread-Index: Ac+G5tZ/EZg4wop1QC6e30AzRpcCWA==
Date: Fri, 13 Jun 2014 09:07:01 +0000
Message-ID: <DD5FC8DE455C3348B94340C0AB5517334F7D3EB6@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.23.94]
Content-Type: multipart/alternative; boundary="_000_DD5FC8DE455C3348B94340C0AB5517334F7D3EB6nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/PjJY2z9Kich_tUEmClWmLfkZZTE
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Subject: [nvo3] One question about draft draft-tissa-nvo3-oam-fm-00
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 09:07:10 -0000
Hi Tissa, In section 10.1 in your draft of draft-tissa-nvo3-oam-fm-00, theory of operation is discribed, you say that originator device should specify the TTL of the transport header as 1 for the first request. Because transit devices in underlying network normally don't support the OAM function, if you specify TTL as 1, the first transit device will drop it, remote MEP or MIP won't receive the message if two or more hops exists between ingress and egress MEPs, so the response timer will expire on originator device. How can you ensure the OAM state machine on originator runs correctly in this scenario? Thanks weiguo
- [nvo3] One question about draft draft-tissa-nvo3-… Haoweiguo
- Re: [nvo3] One question about draft draft-tissa-n… Tissa Senevirathne (tsenevir)
- [nvo3] 答复: One question about draft draft-tissa-n… Haoweiguo