Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-07.txt

mohamed.boucadair@orange.com Fri, 16 April 2021 13:28 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 1980B3A25E7; Fri, 16 Apr 2021 06:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level:
X-Spam-Status: No, score=-2.117 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_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 lbbHU9sQ-CnC; Fri, 16 Apr 2021 06:28:29 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (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 E2D693A25E6; Fri, 16 Apr 2021 06:28:28 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 4FMH8n6zs2z4wc3; Fri, 16 Apr 2021 15:28:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1618579706; bh=IQnijOLpFawDtiDzdY1sOMbtJZNYjhvTgQ8rD9IIjNM=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=ZHR9r+nfl78ifgPlux+9+HQD88Oj+uHOf8SUHPCmv/4aJ4MGEETd2Mta4TpkiVqlv VRXE/2B6Q6Bpy84kZNuFmx+etbGAON4/Lsbf7beQc5j8IdJBhdZ3MBvyMfdMIAQyrz hYWSkCY+yGvfC9bwE4SsR+nMMPKwkClwVr/hWY8L5M+aBytHW2eTZ5jkohbvBltPsR 1XNCA1H8o0nBKIpvKrFyZuJndI7k8kkag6Qfxws6nwYYktAorrG9mzOAycCmhJTl3L swD/zWg6VcjhBZ7sRHQpctH+vFGsXvRxkp/Mm1nqo/isZV4FwWniw6XdgybjzjGTCm ydIvGQZF1ilfA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.20]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 4FMH8n6BjRz1xpP; Fri, 16 Apr 2021 15:28:25 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: Greg Mirsky <gregimirsky@gmail.com>
CC: "draft-ietf-sfc-multi-layer-oam@ietf.org" <draft-ietf-sfc-multi-layer-oam@ietf.org>, "sfc-chairs@ietf.org" <sfc-chairs@ietf.org>, Service Function Chaining IETF list <sfc@ietf.org>
Thread-Topic: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-07.txt
Thread-Index: AQHXAN1X0RpE7fLdUUO2xMJIz1rt76q3hkgA
Date: Fri, 16 Apr 2021 13:28:24 +0000
Message-ID: <8551_1618579705_607990F9_8551_401_1_787AE7BB302AE849A7480A190F8B93303536C01F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <160799455546.19145.6717090076172979397@ietfa.amsl.com> <CA+RyBmVnC6h3oPzy_eCUAPaRjF_=_ohySdpU-MuHxqNPGtxKhQ@mail.gmail.com> <17739_1610546014_5FFEFB5E_17739_272_1_787AE7BB302AE849A7480A190F8B9330315B8FB6@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CA+RyBmV9JJvYjKZ_ErErBsZ-Cf7M1NW8UHc4z9v4XbXDFhw6Dw@mail.gmail.com>
In-Reply-To: <CA+RyBmV9JJvYjKZ_ErErBsZ-Cf7M1NW8UHc4z9v4XbXDFhw6Dw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93303536C01FOPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/TMHkAI2DKYCOA3Ix5RUoL81q5DU>
Subject: Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-07.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: Fri, 16 Apr 2021 13:28:34 -0000

Hi Greg,

Apologies for the delay to follow-up.

The new version looks better. Thank you so much.

I do still have some comments that you can find at fwiw:

·         pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-sfc-multi-layer-oam-10-rev%20Med.pdf

·         doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-sfc-multi-layer-oam-10-rev%20Med.docx

Cheers,
Med

De : sfc [mailto:sfc-bounces@ietf.org] De la part de Greg Mirsky
Envoyé : vendredi 12 février 2021 02:21
À : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>
Cc : draft-ietf-sfc-multi-layer-oam@ietf.org; sfc-chairs@ietf.org; Service Function Chaining IETF list <sfc@ietf.org>
Objet : Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-07.txt

Dear Med,
the authors are indebted to you for your thorough review of the draft, thoughtful comments, and helpful suggestions.
We've accepted all editorial; suggestions and applied them to the new version<https://tools.ietf.org/html/draft-ietf-sfc-multi-layer-oam-09>. We've discussed your comments and suggestions and updated the draft resulting from these discussions. We hope that these updates address your concerns.
Attached, please find the diff highlighting changes in the new version and 09 version of the draft.
Once again, many thanks for your help in improving this document.

Kind regards,
Greg

On Wed, Jan 13, 2021 at 5:53 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Hi Greg,

FWIW, some comments on the first part of the document can be seen at:


•         doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-sfc-multi-layer-oam-07-rev%20Med.doc

•         pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-sfc-multi-layer-oam-07-rev%20Med.pdf

Hope this helps.

Cheers,
Med

De : sfc [mailto:sfc-bounces@ietf.org<mailto:sfc-bounces@ietf.org>] De la part de Greg Mirsky
Envoyé : mardi 15 décembre 2020 02:18
À : Service Function Chaining IETF list <sfc@ietf.org<mailto:sfc@ietf.org>>; sfc-chairs@ietf.org<mailto:sfc-chairs@ietf.org>
Objet : [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-07.txt

Dear All,
in addition to a number of nits being fixed, updates in this version include:

  *   a change in the format of the TLV used in the SFC Echo Request/Reply. The shorter Type field seems not to affect extensibility but an additional one-octet-long filed can be used in some cases (one being the new Authentication TLV);
  *   a new Authentication TLV that can be used to protect the base SFC Echo Request/Reply as well as any optional TLV.
Authors welcome your comments, questions, and suggestions.

Regards,
Greg

---------- Forwarded message ---------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Mon, Dec 14, 2020 at 5:10 PM
Subject: [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-07.txt
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Cc: <sfc@ietf.org<mailto:sfc@ietf.org>>



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Service Function Chaining WG of the IETF.

        Title           : Active OAM for Service Function Chains in Networks
        Authors         : Greg Mirsky
                          Wei Meng
                          Bhumip Khasnabish
                          Cui Wang
        Filename        : draft-ietf-sfc-multi-layer-oam-07.txt
        Pages           : 22
        Date            : 2020-12-14

Abstract:
   A set of requirements for active Operation, Administration and
   Maintenance (OAM) of Service Function Chains (SFCs) in networks is
   presented.  Based on these requirements, an encapsulation of active
   OAM message in SFC and a mechanism to detect and localize defects
   described.  Also, this document updates RFC 8300 in the definition of
   O (OAM) bit in the Network Service Header (NSH) and defines how the
   active OAM message is identified in SFC NSH.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-sfc-multi-layer-oam-07
https://datatracker.ietf.org/doc/html/draft-ietf-sfc-multi-layer-oam-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-multi-layer-oam-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


_______________________________________________
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.

_________________________________________________________________________________________________________________________

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.