IETF Logo Mail Archive

Re: [sfc] I-D Action: draft-boucadair-sfc-oam-packet-00.txt

mohamed.boucadair@orange.com Wed, 16 February 2022 15:08 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 E6A753A136D for <sfc@ietfa.amsl.com>; Wed, 16 Feb 2022 07:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 i31uB7NsAAta for <sfc@ietfa.amsl.com>; Wed, 16 Feb 2022 07:08:35 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (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 46CA03A136C for <sfc@ietf.org>; Wed, 16 Feb 2022 07:08:35 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) (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 opfedar21.francetelecom.fr (ESMTP service) with ESMTPS id 4JzLv51csWz7trK; Wed, 16 Feb 2022 16:08:33 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1645024113; bh=xKHrWVy7yBk0hCI7YxDcIyjvF1Amap2C/SDyqbmag/M=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=iJB2mIrX6sO9z3Z8fFCrLL4mNMiRyxUfQemigUe/uEK1kijz8UpETJc/xTj/pvEwE 1Gg1XInXoFBId0qaMJ5Nw6HXFWLFT4E5DqCD2NF2AkRh7sGF43ltJnEIRDe+DghQje PowhWPEutIikZ7fX/zIn29fjM9bazahRxer0irb8ov5Pf8A6ABrUAWhNfkUwJhT8gh KzYn185fMhzDIGni9SeKlPETeb6WkunqAzR7XXJdSr2Y54dUq8gLVKYXpZmxw5GiXX SNh8NOJTba/uTwjPo/jN/CgNwAo8JitsVX/8S+1VeP9ewDXclUVUN+XWRKBSrNe80m +DsACcqD0HU2Q==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar06.francetelecom.fr (ESMTP service) with ESMTPS id 4JzLv50mVXz3wbJ; Wed, 16 Feb 2022 16:08:33 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: James Guichard <james.n.guichard@futurewei.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: I-D Action: draft-boucadair-sfc-oam-packet-00.txt
Thread-Index: AQHYI0LOqTeC5k5EYkSp4mi5aRUmyqyWP62A///+fqCAAATzUA==
Content-Class:
Date: Wed, 16 Feb 2022 15:08:31 +0000
Message-ID: <21823_1645024113_620D1371_21823_465_1_787AE7BB302AE849A7480A190F8B933035494D9C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164502226599.23621.11371897310173936133@ietfa.amsl.com> <14238_1645022412_620D0CCC_14238_64_1_787AE7BB302AE849A7480A190F8B933035494D1E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <MN2PR13MB42068BEA86DA57E21A4ECBD1D2359@MN2PR13MB4206.namprd13.prod.outlook.com>
In-Reply-To: <MN2PR13MB42068BEA86DA57E21A4ECBD1D2359@MN2PR13MB4206.namprd13.prod.outlook.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-02-16T14:53:13Z; 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=5899aa03-3936-45a9-bf70-0492ae0d80a7; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/dNpny93D7Tf4VeuyILxA18RVDWo>
Subject: Re: [sfc] I-D Action: draft-boucadair-sfc-oam-packet-00.txt
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, 16 Feb 2022 15:08:40 -0000

Hi Jim, 

Great questions and I hope to hear more from the WG. 

Please see inline my current thoughts on this.

Cheers,
Med

> -----Message d'origine-----
> De : sfc <sfc-bounces@ietf.org> De la part de James Guichard
> Envoyé : mercredi 16 février 2022 15:47
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>om>;
> sfc@ietf.org
> Objet : Re: [sfc] I-D Action: draft-boucadair-sfc-oam-packet-00.txt
> 
> Hi Med,
> 
> Thank you for doing this!
> 
> I think the following questions are relevant and should be clarified as
> part of the draft text:
> 
> (1) Should the O-bit be set ONLY for OAM packets that are specific to the
> SFC service layer?

[Med] The proposed update less restrictive as it allows to include an OAM command/data even in the inner packet. 

> (2) Should the O-bit be set in the cases where a solution uses the next
> protocol field in the NSH header? In this case what is the purpose of the
> O-bit given that the next protocol field already indicates the expected
> behavior?

[Med] The proposed update allows for this. Setting the O-bit allows to make sure that all traversed SFC elements supports that OAM functionality. The packet will get dropped if so.  This is deterministic if we want the OAM outcome to be reliable, otherwise there is a risk that the OAM data does not reflect the full path. 

> (3) If the O-bit is set is it the expected behavior to find relevant SFC
> service layer OAM information ONLY in the context headers?

[Med] The proposed update is less restrictive as it allows to have it in context headers or even the payload. The next-protocol will help interpreting the data. The O-bit is allowed to be unset only when the OAM data is jointly sent with the user data.  

> (4) If the answer to (3) is no then what is the sequence of behavior to
> find the OAM information? (1) look in context headers and then next
> protocol?, (2) look at next protocol and if not an OAM protocol look in
> context headers?, (3) some other sequence?

[Med] The exact sequence will depend on the definition of the context header and the data identified by the next-protocol. I'm not sure we can impose a generic sequence here, but I may be wrong. 

> 
> Jim
> 
> -----Original Message-----
> From: sfc <sfc-bounces@ietf.org> On Behalf Of mohamed.boucadair@orange.com
> Sent: Wednesday, February 16, 2022 9:40 AM
> To: sfc@ietf.org
> Subject: [sfc] TR: I-D Action: draft-boucadair-sfc-oam-packet-00.txt
> 
> Hi all,
> 
> A proposal to clarify the intent of SFC OAM packet. Comments are welcome.
> 
> Cheers,
> Med
> 
> -----Message d'origine-----
> De : I-D-Announce <i-d-announce-bounces@ietf.org> De la part de internet-
> drafts@ietf.org Envoyé : mercredi 16 février 2022 15:38 À : i-d-
> announce@ietf.org Objet : I-D Action: draft-boucadair-sfc-oam-packet-00.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
>         Title           : Clarifying Ambiguity related to Network Service
> Header (NSH) OAM Packet
>         Author          : Mohamed Boucadair
> 	Filename        : draft-boucadair-sfc-oam-packet-00.txt
> 	Pages           : 5
> 	Date            : 2022-02-16
> 
> Abstract:
>    This document clarifies an ambiguity in the Network Service Header
>    (NSH) specification related to the handling of O-bit.  In particular,
>    this document clarifies the meaning of "OAM packet".
> 
>    This document updates RFC8300.
> 
> 
> The IETF datatracker status page for this draft is:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
> er.ietf.org%2Fdoc%2Fdraft-boucadair-sfc-oam-
> packet%2F&amp;data=04%7C01%7Cjames.n.guichard%40futurewei.com%7Ca3484be3413
> e4d7f0ded08d9f15a462e%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C63780619
> 2321886192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=InMITh%2FD%2FNkAnNh0rvL5Eeeshzd
> TbrxXeGKwOCVNyAA%3D&amp;reserved=0
> 
> There is also an htmlized version available at:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
> er.ietf.org%2Fdoc%2Fhtml%2Fdraft-boucadair-sfc-oam-packet-
> 00&amp;data=04%7C01%7Cjames.n.guichard%40futurewei.com%7Ca3484be3413e4d7f0d
> ed08d9f15a462e%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637806192321886
> 192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1
> haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=XzLwiIMGzlBD0rM6Q%2Bf4v68iFYlcee3Kegm0
> 8FVcUmw%3D&amp;reserved=0
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-
> drafts
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.
> org%2Fmailman%2Flistinfo%2Fi-d-
> announce&amp;data=04%7C01%7Cjames.n.guichard%40futurewei.com%7Ca3484be3413e
> 4d7f0ded08d9f15a462e%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637806192
> 321886192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> iI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=W3MJq4OJvBesWQg5t6FS%2FJQH7BSK7G
> QqAQzQV5rT2gY%3D&amp;reserved=0
> Internet-Draft directories:
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ietf.o
> rg%2Fshadow.html&amp;data=04%7C01%7Cjames.n.guichard%40futurewei.com%7Ca348
> 4be3413e4d7f0ded08d9f15a462e%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6
> 37806192321886192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
> zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=8fnzdUA6tJApFT%2FhR3fgCI
> mL7TNZen3Qox4%2FAWEqknU%3D&amp;reserved=0 or
> https://nam11.safelinks.protection.outlook.com/?url=ftp%3A%2F%2Fftp.ietf.or
> g%2Fietf%2F1shadow-
> sites.txt&amp;data=04%7C01%7Cjames.n.guichard%40futurewei.com%7Ca3484be3413
> e4d7f0ded08d9f15a462e%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C63780619
> 2321886192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=HGYz6%2BCCQ%2Bnv7ZTVibxMJgujKFp
> HcXMj0XpmOEba0Ww%3D&amp;reserved=0
> 
> ___________________________________________________________________________
> ______________________________________________
> 
> 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.
> 
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.
> org%2Fmailman%2Flistinfo%2Fsfc&amp;data=04%7C01%7Cjames.n.guichard%40future
> wei.com%7Ca3484be3413e4d7f0ded08d9f15a462e%7C0fee8ff2a3b240189c753a1d5591fe
> dc%7C1%7C0%7C637806192321886192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=Q6Wls3Pms3
> n4YDK1Ert9f1GRoiFaaX2kVPgUlmjTm8A%3D&amp;reserved=0
> 
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc

_________________________________________________________________________________________________________________________

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