Re: [spring] I-D Action: draft-ietf-spring-sr-oam-requirement-02.txt
Gregory Mirsky <gregory.mirsky@ericsson.com> Thu, 07 July 2016 04:14 UTC
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C16A012D1D8 for <spring@ietfa.amsl.com>; Wed, 6 Jul 2016 21:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 4nzLbOt3MK7v for <spring@ietfa.amsl.com>; Wed, 6 Jul 2016 21:14:40 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D2A312D0C3 for <spring@ietf.org>; Wed, 6 Jul 2016 21:14:40 -0700 (PDT)
X-AuditID: c6180641-f796f6d000000e1e-46-577dd6ed3b41
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 6F.E7.03614.DE6DD775; Thu, 7 Jul 2016 06:13:33 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0294.000; Thu, 7 Jul 2016 00:14:39 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: David Allan I <david.i.allan@ericsson.com>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] I-D Action: draft-ietf-spring-sr-oam-requirement-02.txt
Thread-Index: AQHR06vsArfNwudLBk2IB1qZgLqlnqAEAnGAgAgQdOA=
Date: Thu, 07 Jul 2016 04:14:38 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF11221AC388D@eusaamb103.ericsson.se>
References: <20160701151906.24589.40199.idtracker@ietfa.amsl.com> <E6C17D2345AC7A45B7D054D407AA205C4BD307F2@eusaamb105.ericsson.se>
In-Reply-To: <E6C17D2345AC7A45B7D054D407AA205C4BD307F2@eusaamb105.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyuXRPlO7ba7XhBsdmmVgcv/Cb0YHRY8mS n0wBjFFcNimpOZllqUX6dglcGTtnPWEr+K5Y8fPtQ7YGxgVSXYycHBICJhK7mvazQNhiEhfu rWfrYuTiEBI4yijxon8bC4SzjFFiwuod7CBVbAJGEi829oDZIgKhEp0T5gHZHBzCAr4Sm88G gpgiAgESi+faQ1RYSSy/94ARxGYRUJHouX+LGcTmBar+fucEM8T4VkaJw0emgo3kFPCTeNZ2 FqyIEeig76fWMIHYzALiEreezGeCOFRAYsme88wQtqjEy8f/WCFsJYmPv+ezQ9TrSCzY/YkN wtaWWLbwNdRiQYmTM5+wTGAUnYVk7CwkLbOQtMxC0rKAkWUVI0dpcUFObrqR4SZGYOAfk2Bz 3MG4t9fzEKMAB6MSD29CfW24EGtiWXFl7iFGCQ5mJRHejstAId6UxMqq1KL8+KLSnNTiQ4zS HCxK4rz6LxXDhQTSE0tSs1NTC1KLYLJMHJxSDYxKWyoOfef4V1AWE158SVCxNWv+qYDjSUvW PDmyYWGtyMdjir9fOb+c9XvtMnbPFBVrM84AmTUntBbcEddJOaaxMC+iSdG4XEfuZ8H97Hjp pCtLsi/ksVz9yqcdE8/6e8ZC15faJyeHb5OT2lR6OzWmWOrBqSlNK6oq5fNTWcO0uJ6d7v0R ckuJpTgj0VCLuag4EQAG9c1ceAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/1eaG0BZSTA7TcwvDkPiMKr8EaFM>
Subject: Re: [spring] I-D Action: draft-ietf-spring-sr-oam-requirement-02.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 04:14:43 -0000
Hi Dave, many thanks for your thorough review and insightful comments. Apologies for the delayed response as we been tied in with other activities. Will discuss and continue work after the meeting. Regards, Greg -----Original Message----- From: spring [mailto:spring-bounces@ietf.org] On Behalf Of David Allan I Sent: Friday, July 01, 2016 9:12 AM To: spring@ietf.org Subject: Re: [spring] I-D Action: draft-ietf-spring-sr-oam-requirement-02.txt Hi I looked over this and have a few modest suggestions.... 1) Could be clarified a bit... REQ#2: The SR OAM packet MUST follow exactly the same path as dataplane traffic Suggested change REQ#2: An SR OAM packet MUST follow exactly the same path as the dataplane traffic it is intended to instrument. We could also argue about "exact path", as best we can do is in the nodal sense.... 2) Delete REQ 3 and REQ 4 Reason: Clarity. Packets do not discover anything, systems can. If the system implements ECMP and/or UCMP and the OAM system meets requirement 2, you're done. 3) REQ5, question... When you say available, is this in the sense that the path meets a specified criteria of information transfer capability? Depending on the answer I may suggest an edit or two...and it may be necessary to include a definition of availability. (definition, not specification as we'll argue till the cows come home :-) 4) REQ9, clarification The current text reads like the CC mechanism itself failed, not what it was instrumenting. Suggested tweak... REQ#9: In case of any path failure detected with continuity check, SR OAM SHOULD support rapid Connectivity Fault localization to isolate the node on which the failure occurs. 5) REQ11 Just reads strange.... for example, an edge node may not be adjacent to a failure therefore confining actions to edge nodes makes no sense. If the actual intention is to include all consequent actions of OAM states, there will be a few requirements that fall out of this. Something to discuss. There is also the imbedded assumption that transactions are both p2p and bi-directional. I would like to see REQxx OAM probes may be unidirectional or bi-directional. REQxx+1 OAM probes must be able to instrument p2p, mp2p and p2mp paths. My 2 cents, hope it is useful. Dave -----Original Message----- From: spring [mailto:spring-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Friday, July 01, 2016 8:19 AM To: i-d-announce@ietf.org Cc: spring@ietf.org Subject: [spring] I-D Action: draft-ietf-spring-sr-oam-requirement-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Packet Routing in Networking of the IETF. Title : OAM Requirements for Segment Routing Network Authors : Nagendra Kumar Carlos Pignataro Nobo Akiya Ruediger Geib Greg Mirsky Stephane Litkowski Filename : draft-ietf-spring-sr-oam-requirement-02.txt Pages : 7 Date : 2016-07-01 Abstract: This document describes a list of functional requirement for OAM in Segment Routing (SR) based network. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-spring-sr-oam-requirement/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-spring-sr-oam-requirement-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-sr-oam-requirement-02 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
- Re: [spring] I-D Action: draft-ietf-spring-sr-oam… Gregory Mirsky
- Re: [spring] I-D Action: draft-ietf-spring-sr-oam… David Allan I
- [spring] I-D Action: draft-ietf-spring-sr-oam-req… internet-drafts