[nvo3] Comments to NVO3 OAM draft-tissa-nvo3-oam-fm-00.txt
Gregory Mirsky <gregory.mirsky@ericsson.com> Thu, 27 February 2014 17:56 UTC
Return-Path: <gregory.mirsky@ericsson.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 98AB61A0074 for <nvo3@ietfa.amsl.com>; Thu, 27 Feb 2014 09:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 5fGbKXxPXtjQ for <nvo3@ietfa.amsl.com>; Thu, 27 Feb 2014 09:56:03 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id B0D6F1A00AE for <nvo3@ietf.org>; Thu, 27 Feb 2014 09:56:01 -0800 (PST)
X-AuditID: c618062d-b7f858e0000031c7-dd-530f7c2bfd78
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 3C.83.12743.B2C7F035; Thu, 27 Feb 2014 18:55:55 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0387.000; Thu, 27 Feb 2014 12:55:58 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "tsenevir@cisco.com" <tsenevir@cisco.com>, "nfinn@cisco.com" <nfinn@cisco.com>, "ssalam@cisco.com" <ssalam@cisco.com>, "dekumar@cisco.com" <dekumar@cisco.com>, "d3e3e3@gmail.com" <d3e3e3@gmail.com>, "Sam Aldrin (aldrin.ietf@gmail.com)" <aldrin.ietf@gmail.com>
Thread-Topic: Comments to NVO3 OAM draft-tissa-nvo3-oam-fm-00.txt
Thread-Index: Ac8pUrrMlV9MygzfRkKtDaUyb/RcoQ==
Date: Thu, 27 Feb 2014 17:55:57 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B773598@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B773598eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBLMWRmVeSWpSXmKPExsUyuXSPt652DX+wwdtPchYTWr8wWhzcrmnx c9Undov3vaYWT+dLWjyZt5LdovvHUzYHdo8pvzeyeuycdZfdY8mSn0wBzFFcNimpOZllqUX6 dglcGR+6lzAWLPGueN37gqmBcZpTFyMnh4SAicTByb/YIGwxiQv31gPZXBxCAkcYJX6vfw/l LGeUmP9lFStIFZuAkcSLjT3sIAkRgV4mibNPn7F0MXJwMAsoSzR3WoPUCAvYSDxbuIcJJCwi 4ChxrzMWJCwioCfx9nEfC4jNIqAqMXfqNLDFvAK+Eq0zPoLFGYGO+H5qDROIzSwgLnHryXwm iOMEJJbsOc8MYYtKvHz8jxXCVpKYtPQcK0R9vsT+j+8ZIWYKSpyc+YRlAqPwLCSjZiEpm4Wk DCKuI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9i5CgtTi3LTTcy2MQIjK1jEmy6Oxj3vLQ8 xCjNwaIkzvvlrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkbvvRs1HSI4+z9fkD50xeHa zRNLb51TDHS1u+p6plRd7v4KnqOzW8x3SGY2XlDXYno9U31u1YeUs8eZJLIzX8z4WDsnU07j vmT5kr/nJGQ2TapdP3nrofpLdzb/PLX+2v8cmaBCpZsfnGMDTkm6Pqri1bY4nl1Ye/nK3GV3 FNdlLZTQ91TTT61UYinOSDTUYi4qTgQAqYik43sCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/C1O6AxsJlCUZJiubCO-lZ_wnJFw
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Subject: [nvo3] Comments to NVO3 OAM draft-tissa-nvo3-oam-fm-00.txt
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: Thu, 27 Feb 2014 17:56:05 -0000
Dear Authors,
I have several architectural questions to presented in the draft NVO3 OAM before diving into detailed analysis of protocol design.
The NVO3 Operations, Administration, and Maintenance Requirements (draft-ashwood-nvo3-oam-requirements) defines scope of NVO3 OAM as domain within NV-Edge entities. If you agree with this definition, then:
* where in NVO3 OAM domain a MIP can exist if, as I think, MEP is at NV-Edge entity;
* what is benefit of MD Level for this model of OAM as it appears to be flat and OAM layers for NVO3 viewed as Tenant (Service), NV Edge, and Transport (VPN);
* what are benefits of Entropy TLV for Continuity Check OAM? I believe that ensuring in-band behavior for proactive CC OAM is sufficient requirement even for multipath segments;
* what is meaning of "Semantics and usage of Type values allocated for TRILL OAM purpose are defined by this document and other future related documents." in Sec. 8.3. Format of IETF Overlay OAM TLV
* would it be prudent to complete work on NVO3 Requirements followed with OAM Gap Analysis and then work on extending and augmenting NVO3 OAM toolbox.
Regards,
Greg
- [nvo3] Comments to NVO3 OAM draft-tissa-nvo3-oam-… Gregory Mirsky