Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH
Dave Dolson <ddolson@sandvine.com> Thu, 21 July 2016 07:58 UTC
Return-Path: <ddolson@sandvine.com>
X-Original-To: rtg-ooam-dt@ietfa.amsl.com
Delivered-To: rtg-ooam-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C871512DAD9; Thu, 21 Jul 2016 00:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.207
X-Spam-Level:
X-Spam-Status: No, score=-3.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287] 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 n_-hzKKVdLRs; Thu, 21 Jul 2016 00:58:05 -0700 (PDT)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46D3612DA81; Thu, 21 Jul 2016 00:58:05 -0700 (PDT)
Received: from WTL-EXCHP-2.sandvine.com ([fe80::68ac:f071:19ff:3455]) by wtl-exchp-1.sandvine.com ([::1]) with mapi id 14.03.0294.000; Thu, 21 Jul 2016 03:58:03 -0400
From: Dave Dolson <ddolson@sandvine.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] Identifying OAM in NSH
Thread-Index: AQHR4yWb0Kt3ZKrawUWZ2rsvELgMRQ==
Date: Thu, 21 Jul 2016 07:58:02 +0000
Message-ID: <20160721075801.5697618.51293.99071@sandvine.com>
References: <7347100B5761DC41A166AC17F22DF11221ADA9CB@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF11221ADA9CB@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/4dt5nvGlmvaFHUgqCXEarHe6d5Y>
Cc: "rtg-ooam-dt@ietf.org" <rtg-ooam-dt@ietf.org>
Subject: Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH
X-BeenThere: rtg-ooam-dt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List is used by the Routing Area Overlay OAM Design team for internal coordination and discussion <rtg-ooam-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-ooam-dt>, <mailto:rtg-ooam-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-ooam-dt/>
List-Post: <mailto:rtg-ooam-dt@ietf.org>
List-Help: <mailto:rtg-ooam-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-ooam-dt>, <mailto:rtg-ooam-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2016 07:58:07 -0000
Greg, This answers some of the questions I had after your presentations. However, regarding appending OAM after the packet, NSH header doesn't have a length field that could indicate where the appended portion begins. The current Length field is regarding the header size. -Dave From: Gregory Mirsky Sent: Thursday, July 21, 2016 9:01 AM To: sfc@ietf.org Cc: rtg-ooam-dt@ietf.org Subject: [sfc] Identifying OAM in NSH Dear All, we had very good discussion on OAM this week. We’ve touched on Active, Passive and Something-in-between OAM. But can NSH indicate which OAM type, if any, associated with a packet? I think that the current version of draft-ietf-sfc-nsh does not allow that and may be ambiguous in some cases. I propose change to interpretation and applicability description of the O(AM) flag and allocation of the new protocol type to be used in the Next Protocol field. RFC 7799 defines Active OAM as following: An Active Metric or Method depends on a dedicated measurement packet stream and observations of the stream. Thus, regardless of encapsulation used by OAM, it is the packet constructed solely for monitoring, measuring network’s metric and should not leave given domain. And, I believe, such packets should be identified by the protocol type of their own. OAM which behaves as much as Passive OAM or Something-in-between, e.g. OAM appended to data packet either at the domain’s edge or on-the-fly, identified by the protocol type of the data packet carried in NSH. Below are changes I’d like to propose: Section 3.2 O-bit: OLD O bit: when set to 0x1 indicates that this packet is an Operations, Administration and Maintenance (OAM) message. The receiving SFF and SFs nodes MUST examine the payload and take appropriate action (e.g. return status information). OAM message specifics and handling details are outside the scope of this document. END NEW O bit: when set to 0x1 indicates that data packet identified by the Next Protocol type has OAM metadata appended. Definition of the format(s) used by OAM metadata is outside the scope of this document. END At the end of Section 3.2: OLD This draft defines the following Next Protocol values: 0x1 : IPv4 0x2 : IPv6 0x3 : Ethernet 0x4: NSH 0x5: MPLS 0x6-0xFD: Unassigned 0xFE-0xFF: Experimental END NEW This draft defines the following Next Protocol values: 0x1 : IPv4 0x2 : IPv6 0x3 : Ethernet 0x4: NSH 0x5: MPLS 0x6: Active OAM 0x7-0xFD: Unassigned 0xFE-0xFF: Experimental END And, consequently, section 13.2.5 in IANA Considerations section will request allocation of value 0x6 to be assigned to Active OAM protocols. Greatly appreciate your consideration and comments. Regards, Greg
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Joel M. Halpern
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Joel M. Halpern
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Dave Dolson
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Dave Dolson
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Dave Dolson
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Joel M. Halpern
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Joel M. Halpern
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Dave Dolson
- Re: [Rtg-ooam-dt] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] Identifying OAM in NSH Gregory Mirsky
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Dave Dolson
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] Identifying OAM in NSH Carlos Pignataro (cpignata)
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Gregory Mirsky
- Re: [Rtg-ooam-dt] [sfc] Identifying OAM in NSH Dave Dolson
- [Rtg-ooam-dt] Identifying OAM in NSH Gregory Mirsky