IETF Logo Mail Archive

Re: [sfc] Regarding last call for draft-ietf-sfc-multi-layer-oam

mohamed.boucadair@orange.com Wed, 05 January 2022 13:44 UTC

Return-Path: <mohamed.boucadair@orange.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 539133A0910 for <sfc@ietfa.amsl.com>; Wed, 5 Jan 2022 05:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 turapFljySUG for <sfc@ietfa.amsl.com>; Wed, 5 Jan 2022 05:44:39 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F4AF3A094B for <sfc@ietf.org>; Wed, 5 Jan 2022 05:44:39 -0800 (PST)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar26.francetelecom.fr (ESMTP service) with ESMTPS id 4JTW1c4TrKzFq67; Wed, 5 Jan 2022 14:44:36 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641390276; bh=5Z5+PskCeckNaBJ8PalomLVmPbMqTpnvT/zcDS18Uqo=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=nMBkfVO+YW6DBKpBkRZlUXNL+tA5JEINCCmsfgjjcU5isL6wEQjMOAtPySpuZbRuF IJ+GCLtboQ5qRDPv5Ai+GvCyI2kVEfNWmGaSJDqJObtUpP4xM3BpVWk55pqeZ1tyCj LezTljXfwsXXwf8a5sti/IBybkmKm/bNpVwl9XVeq3SRAjL3F+dEIeNS8Ob4pesLRZ /n9wr0lp2F5bQ88LVYQUgPZODlsmsBK2NyMWTgGnc6u7iMK2jtCQFyyR4ExEforDtw GhbcesLEGjKG+x4oj0+1tPg+OnQyOk/coE3CJg5c2/5RJgLbd6MIstC7hVsCVpClEp 0QPlLfC0h1JrA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar05.francetelecom.fr (ESMTP service) with ESMTPS id 4JTW1c3WXyz2xDh; Wed, 5 Jan 2022 14:44:36 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
CC: Greg Mirsky <gregimirsky@gmail.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] Regarding last call for draft-ietf-sfc-multi-layer-oam
Thread-Index: AQHXz1F51znvKMj22UuU/rlSA5k5qqwCudcAgAjtvoCAABcDgIAAKZkAgAAKXICAALeogIACHMmAgAFQW4CAACcHAIABERUAgAAC4wCABSLBgIAAZPeAgAAFfoCAAA1TAIAdpT2AgASQIoCAACOAgIADKDAA///w+YCAAADlgIAAHmUAgBhAtBA=
Content-Class:
Date: Wed, 5 Jan 2022 13:44:35 +0000
Message-ID: <6443_1641390276_61D5A0C4_6443_170_1_787AE7BB302AE849A7480A190F8B93303546D415@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <4bb5abb4-a8dc-c8f0-9b99-549f683e7729@joelhalpern.com> <B4F81D2C-1273-493E-8E90-35D32ACDE6D1@cisco.com> <DM8PR11MB560669E2E2C77AD662F6251CDA9F9@DM8PR11MB5606.namprd11.prod.outlook.com> <CA+RyBmXUBYFFgNfopErFYUgJDfJWVY59ERM0LrkEnxw_xC2MYg@mail.gmail.com> <DM8PR11MB5606B943F4D1A3B2702D53EBDA609@DM8PR11MB5606.namprd11.prod.outlook.com> <A012EBFA-FDAB-4591-8F3A-9D5882B69A57@cisco.com> <DM8PR11MB5606D7CDC99EB7FFE63095DFDA639@DM8PR11MB5606.namprd11.prod.outlook.com> <896B8A4B-3717-4150-9944-44906A593BC9@cisco.com> <CA+RyBmUaeSsjLE191jK94bGV3Nzed95tkN+mn-kCDs6WxucFRg@mail.gmail.com> <1B31F06E-974A-4BDA-8C89-81E61B8E6868@cisco.com> <CA+RyBmUax4VmKpMvW-JErrdjZj09kV2fCofiKH91E0qYRhGatA@mail.gmail.com> <CE085BD4-1DD3-484E-B94C-6800C9F38CFA@cisco.com> <005e334c-fd02-e7b2-4bef-3d0551c1b289@joelhalpern.com> <FE19CCFA-D499-4C3E-AB52-0E1F771D5371@cisco.com> <07cd39c5-9078-ec76-b340-43665d8805eb@joelhalpern.com> <2C6BEA5E-D7A3-4ED7-B1AD-A9353777045D@cisco.com> <d62da18b-6fd5-da1d-aae3-e07563fa803f@joelhalpern.com>
In-Reply-To: <d62da18b-6fd5-da1d-aae3-e07563fa803f@joelhalpern.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-05T12:22:17Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=abf70392-a64c-4d1c-a201-1fa3e5ed07c6; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/F_oChVABsid61iWJelnYnvbeqO8>
Subject: Re: [sfc] Regarding last call for draft-ietf-sfc-multi-layer-oam
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
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 Jan 2022 13:44:50 -0000

Hi Joel, Greg, all,

I used to have in the past a comment about the same part quoted by Carlos. 

We could leave without tagging the document as it updates 8300 by indicating that, in the context of active OAM covered in the I-D, an OAM packet (mentioned in 8300) is "an OAM command and/or data in the NSH Context Header or packet payload". 

However, the rules for interpreting the combination of 0-bit and next-protocol justifies the "updates" header as the document provides useful characterization of an OAM packet and zooms into this part of 8300:

      The actual format and processing of SFC OAM packets is outside the
      scope of this specification (for example, see [SFC-OAM-FRAMEWORK]
      for one approach). 

Of course, "updates" here is to be understood as "extends", not "amends".

Cheers,
Med

> -----Message d'origine-----
> De : sfc <sfc-bounces@ietf.org> De la part de Joel M. Halpern
> Envoyé : mardi 21 décembre 2021 04:00
> À : Carlos Pignataro (cpignata) <cpignata=40cisco.com@dmarc.ietf.org>rg>;
> Joel Halpern Direct <jmh.direct@joelhalpern.com>
> Cc : James N Guichard <james.n.guichard@futurewei.com>om>; Greg Mirsky
> <gregimirsky@gmail.com>om>; Frank Brockners (fbrockne)
> <fbrockne=40cisco.com@dmarc.ietf.org>rg>; sfc@ietf.org; Gyan Mishra
> <hayabusagsm@gmail.com>
> Objet : Re: [sfc] Regarding last call for draft-ietf-sfc-multi-layer-oam
> 
> At this point I would really like to hear from other people in the
> working group.
> 
> Is anyone other than the authors, Carlos, adn Frank, paying attention?
> Please?
> 
> Thank you,
> Joel

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

v2.8.7 | Report a Bug | By Email