IETF Logo Mail Archive

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

mohamed.boucadair@orange.com Wed, 16 February 2022 15:30 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 7AF053A0D5D for <sfc@ietfa.amsl.com>; Wed, 16 Feb 2022 07:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 TX73gpu8p10z for <sfc@ietfa.amsl.com>; Wed, 16 Feb 2022 07:30:38 -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 E10263A0D41 for <sfc@ietf.org>; Wed, 16 Feb 2022 07:30:37 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) (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 4JzMNW3YMXzFpxy; Wed, 16 Feb 2022 16:30:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1645025435; bh=sKbub1Y6ENIrPWMHqsHOhVV73IJc4GjfHkSbaG7g6yM=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=jixujmh2FUZbYXeFFYtsTHLjUJNGph4xVr9ou1Q6+TdD6s5u9cGov/hyXNX39JzwJ YpaN9UYvXC+2XSvaiXPrCZN7lAnQRWhybVE22ghSFFX5nwrvVhjZNcTkTMqhscKl0k ocvuR1Pkkd3z6s9XLVlGkWf+63hORT7D5gvtgSqGiQDamZ73bKCAJwgPMo8JZOg3tb QA8wQgQQoQmPodvtmOwm5f6JdjAJrXnlxf2gQLmwA6t7A0b79OGzzz0pN7AYGPP4eL nGKuvYPsKoB5MfN8xZozhgtaIIUic8k68KR1m47ReN5drK8yMMlu597Ca8nr0PJUwp HRMmZxS2USfEQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar02.francetelecom.fr (ESMTP service) with ESMTPS id 4JzMNW2gFszCqkP; Wed, 16 Feb 2022 16:30:35 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] TR: I-D Action: draft-boucadair-sfc-oam-packet-00.txt
Thread-Index: AQHYI0LOqTeC5k5EYkSp4mi5aRUmyqyWSPcMgAAATbA=
Content-Class:
Date: Wed, 16 Feb 2022 15:30:34 +0000
Message-ID: <30956_1645025435_620D189B_30956_353_1_787AE7BB302AE849A7480A190F8B933035494DD5@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164502226599.23621.11371897310173936133@ietfa.amsl.com> <14238_1645022412_620D0CCC_14238_64_1_787AE7BB302AE849A7480A190F8B933035494D1E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CA+RyBmXTSUdfovvnSpQjoo_Svwm-amC-bRm0eyscUHgY2hYx9g@mail.gmail.com>
In-Reply-To: <CA+RyBmXTSUdfovvnSpQjoo_Svwm-amC-bRm0eyscUHgY2hYx9g@mail.gmail.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-16T15:14:44Z; 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=987ee2e2-cf38-4928-a9f9-08e755e58c40; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933035494DD5OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/KqwZyr2Svb6E-GJTaOB8QHX2OCM>
Subject: Re: [sfc] TR: 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:30:43 -0000

Hi Greg,

Please see inline.

Cheers,
Med

De : Greg Mirsky <gregimirsky@gmail.com>
Envoyé : mercredi 16 février 2022 16:13
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
Cc : sfc@ietf.org
Objet : Re: [sfc] TR: I-D Action: draft-boucadair-sfc-oam-packet-00.txt

Hi Med,
many thanks for taking the lead and putting the proposal on the table.
I have a question on the proposed new text for the O bit and its possible effect on IOAM:
   O bit:  Setting this bit indicates an SFC OAM packet.  Such a packet
      is any NSH-encapasulated packet that exclusively includes an OAM
      command and/or OAM data.
My understanding of the new definition of the O bit is that the NSH includes and/or encapsulates only OAM command and/or data. IOAM, as I understand its application in NSH, may follow the NSH and have user payload after the IOAM data.

[Med] Packets that include also user data are not considered as “OAM packets” as per the new definition.

And another scenario, if Flow ID TLV is used to influence user data through SFP, OAM will apply the same Flow ID value. Would such packet still be considered as "exclusively includes OAM command and/or data"?

[Med] Yes, they are. Flow id is just a constraint, if you will, that is used to influence how OAM commands will be executed.

Regards,
Greg

On Wed, Feb 16, 2022 at 6:40 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
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<mailto:i-d-announce-bounces@ietf.org>> De la part de internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Envoyé : mercredi 16 février 2022 15:38
À : i-d-announce@ietf.org<mailto: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://datatracker.ietf.org/doc/draft-boucadair-sfc-oam-packet/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-boucadair-sfc-oam-packet-00


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_________________________________________________________________________________________________________________________

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<mailto: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