Re: [sfc] Use of Alternate Marking Method in SFC

Dave Dolson <ddolson@sandvine.com> Wed, 05 July 2017 21:14 UTC

Return-Path: <ddolson@sandvine.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFF8131762 for <sfc@ietfa.amsl.com>; Wed, 5 Jul 2017 14:14:19 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 AiyXPnWNUeeS for <sfc@ietfa.amsl.com>; Wed, 5 Jul 2017 14:14:17 -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 5F32C1200E5 for <sfc@ietf.org>; Wed, 5 Jul 2017 14:14:17 -0700 (PDT)
Received: from WTL-EXCHP-1.sandvine.com ([fe80::ac6b:cc1e:f2ff:93aa]) by wtl-exchp-2.sandvine.com ([::1]) with mapi id 14.03.0319.002; Wed, 5 Jul 2017 17:14:15 -0400
From: Dave Dolson <ddolson@sandvine.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] Use of Alternate Marking Method in SFC
Thread-Index: AQHS5R4NPrcaAk2ijkiHxpcWTDCPmaJD77BwgAC/TACAASsg0A==
Date: Wed, 05 Jul 2017 21:14:14 +0000
Message-ID: <E8355113905631478EFF04F5AA706E9870632CE3@wtl-exchp-1.sandvine.com>
References: <CA+RyBmVMN34DC49E01eCcLkSRjvCe4e43s6-rb7fZg4-AELJQg@mail.gmail.com> <E8355113905631478EFF04F5AA706E987062F10D@wtl-exchp-1.sandvine.com> <CA+RyBmXh_xP_21nyaCk3jipeV5vd74oJvbkErLgFFnCm0PQBwA@mail.gmail.com>
In-Reply-To: <CA+RyBmXh_xP_21nyaCk3jipeV5vd74oJvbkErLgFFnCm0PQBwA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.200.114]
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: multipart/alternative; boundary="_000_E8355113905631478EFF04F5AA706E9870632CE3wtlexchp1sandvi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/npZzTjFWXmVq2uR2csjaTodFcak>
Subject: Re: [sfc] Use of Alternate Marking Method in SFC
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 21:14:19 -0000

(Adding sfc list)
Thanks Greg. I see I reviewed an older document by mistake.
I still feel that the brief theory of operation does a disservice to the document by raising questions, whereas the ippm-alt-mark is much more nuanced and complete.
Having said that, you could pre-amble the theory of operation with, “The following is an over-simplified description for the sake of providing context…”

-Dave


From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Tuesday, July 4, 2017 7:13 PM
To: Dave Dolson
Subject: Re: [sfc] Use of Alternate Marking Method in SFC

Hi Dave,
many thanks for your interest in this draft and the most helpful comments. I agree that given progress of the Alternate Marking draft at IPPM WG there's no apparent reason to replicate much information in this document (engineers are expected to be able to follow references and links). Couple notes in-line and tagged GIM>>.

Regards,
Greg

On Tue, Jul 4, 2017 at 8:53 AM, Dave Dolson <ddolson@sandvine.com<mailto:ddolson@sandvine.com>> wrote:
Greg,
Given that this document doesn’t explain everything—certainly not enough to implement it—consider making this document very simple, and refer to the draft-ietf-ippm-alt-mark for details.
E.g., this document should just contain:
- which NSH bits are used for Single and Double
GIM>> With -01 version that is more specific on Mark field allocation and bit position designation and use.
- which SFC functions are permitted to write the marks (I think just the classifier, but I don’t think you even say this)
GIM>> Very helpful, thank you! Indeed, the Classifier is the most logical function to perform marking for SFC. Though I'd consider making it as strong recommendation thus allowing marking by other functions.
- where should measurements be taken.
GIM>> Measurements may be taken anywhere along the SFP and without any restrictions to packet size, as measurement results been stored locally and may be exported by out-band transport, e.g. YANG notifications (Netconf or Rest), IPFIX, gRPC. That, in my opinion, is advantage of the AM method when compared to, for example, iOAM.

In other words, I suggest removing any intent to describe the theory of operation or algorithm, when draft-ietf-ippm-alt-mark explains it all.

-Dave


From: sfc [mailto:sfc-bounces@ietf.org<mailto:sfc-bounces@ietf.org>] On Behalf Of Greg Mirsky
Sent: Wednesday, June 14, 2017 10:54 AM
To: sfc@ietf.org<mailto:sfc@ietf.org>
Cc: Fioccola Giuseppe (giuseppe.fioccola@telecomitalia.it<mailto:giuseppe.fioccola@telecomitalia.it>)
Subject: [sfc] Use of Alternate Marking Method in SFC

Dear All,
would like to bring your attention to the draft  Performance Measurement (PM) with Alternate Marking Method in Service <https://tools.ietf.org/html/draft-mirsky-sfc-pmamm-00>
Function Chaining (SFC) Domain<https://tools.ietf.org/html/draft-mirsky-sfc-pmamm-00>
we've submitted earlier. Alternate Marking method allows performance measurement performed close to passive measurement methods.
Greatly appreciate your questions, comments, and suggestions.

Regards,
Greg