Re: [sfc] I-D Action: draft-ietf-sfc-proof-of-transit-06.txt

mohamed.boucadair@orange.com Fri, 07 August 2020 12:54 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 E3E233A0BA3; Fri, 7 Aug 2020 05:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_H4=0.001, RCVD_IN_MSPIKE_WL=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 2kAIAJviUUbi; Fri, 7 Aug 2020 05:54:22 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E4E53A0BA0; Fri, 7 Aug 2020 05:54:22 -0700 (PDT)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 4BNQKm4Lmyz4xlx; Fri, 7 Aug 2020 14:54:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1596804860; bh=Afn8qqwtvvk/Q7W6kGm3NU16Jroasux3rM6T4ARM/kY=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=jT6060LREAqFI2wWBxFn/VF6SvA7vyH103IakExBiqthFdtaNLWu2ruAKFGyrEkxc wHCuZlPeh9a8w73ija0ciRO+T1xvqeA5uRi4ESGTPloGXfbC+Qgc2OUCbdxR0yNpTV dgBZDy9t2nKRW59Rg+gkiPPATEC2yTxDCTYDjhy/cEWQyIDC+4wR2AvX1WV/lWt78Q 6mgBEmMRAy/W9eMjb5bd/Hna5CgRcL2viQznfP6rVvcsiRJnT9P4VMaDtFhKoRfDHd maAtySPP6rISY6uwgGYZlz9EUgOcSIJRGRJQrgS+ewX5INvWtszybzhOaMszif82v3 mbpCO4n/C3Isw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.98]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 4BNQKm3dm8zDq7s; Fri, 7 Aug 2020 14:54:20 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: t petch <ietfa@btconnect.com>, "sfc@ietf.org" <sfc@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: [sfc] I-D Action: draft-ietf-sfc-proof-of-transit-06.txt
Thread-Index: AQHWbKRLdc5bnnsbkU2/flMKEG1zxaksmbbw
Date: Fri, 07 Aug 2020 12:54:19 +0000
Message-ID: <20452_1596804860_5F2D4EFC_20452_303_1_787AE7BB302AE849A7480A190F8B93303151AE77@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <5F2D2AA2.7050806@btconnect.com>
In-Reply-To: <5F2D2AA2.7050806@btconnect.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: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/sRMwOYrmBvGIeYFwjDdXkvw7-08>
Subject: Re: [sfc] I-D Action: draft-ietf-sfc-proof-of-transit-06.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, 07 Aug 2020 12:54:24 -0000

Hi Tom, 

FWIW, the authors are working on an updated version that will fixes many of the points you raised. Some of the issues (e.g., the grouping) are clarified here: https://mailarchive.ietf.org/arch/msg/sfc/ZOf8Yb_JK68v9O40PbD2MSjqJ48/ 

Cheers,
Med

> -----Message d'origine-----
> De : sfc [mailto:sfc-bounces@ietf.org] De la part de t petch
> Envoyé : vendredi 7 août 2020 12:19
> À : sfc@ietf.org; ippm@ietf.org
> Objet : Re: [sfc] I-D Action: draft-ietf-sfc-proof-of-transit-06.txt
> 
> There is quite a lot wrong with this I-D from the YANG point of view.
> I am surprised that it passes YANG validation, as the data tracker
> reports, but that is validation for you!  Most of these comments
> derive from YANG Guidelines RFC8407.
> 
> Tree diagram is now standardised as RFC8340 and is not normally
> regarded as CODE
> 
> YANG version 1 was replaced in 2016
> 
> Prefix ietf-pot-profile is cumbersome - 3-5 characters is more than
> enough for a prefix
> 
> Contact needs Editors
> 
> Copyright 2018 (feels about right:-)
> 
> Revision reference must reference this I-D/RFC2be
> 
> A grouping that is only used once increases size and complexity for no
> benefit but in this case pot-profile is imported by IPPM; worth a
> mention somewhere.
> 
> List identifiers are conventionally plural.
> 
> IANA considerations are mandatory - if the module is not registered
> with IANA there is no module
> 
> Security Considerations for YANG are mandatory - YANG Guidelines
> points to the current text albeit trivial compared with those for
> POT:-).
> 
> These two Considerations will pull in another half a dozen Mandatory
> references.
> 
> Key Words is ood - see RFC8174
> 
> When MTU is Maxiumum Transmission Unit, then it is a recognised
> abbreviation and does not need expanding.
> 
> HMAC is Hashed ...in the RFC Editor list
> 
> Abstract/Introduction should mention that there is a YANG module, that
> it conforms to NMDA and reference RFC7950.  IANA Considerations on the
> other hand should reference RFC6020.
> 
> IPPM import this module so I copy that list.
> 
> Tom Petch
> 
> ----- Original Message -----
> From: <internet-drafts@ietf.org>
> To: <i-d-announce@ietf.org>
> Cc: <sfc@ietf.org>
> Sent: Tuesday, June 16, 2020 10:01 AM
> Subject: I-D Action: draft-ietf-sfc-proof-of-transit-06.txt
> 
> 
> >
> > 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           : Proof of Transit
> >         Authors         : Frank Brockners
> >                           Shwetha Bhandari
> >                           Tal Mizrahi
> >                           Sashank Dara
> >                           Stephen Youell
> > Filename        : draft-ietf-sfc-proof-of-transit-06.txt
> > Pages           : 29
> > Date            : 2020-06-16
> >
> > Abstract:
> >    Several technologies such as Traffic Engineering (TE), Service
> >    Function Chaining (SFC), and policy based routing are used to
> steer
> >    traffic through a specific, user-defined path.  This document
> defines
> >    mechanisms to securely prove that traffic transited a defined
> path.
> >    These mechanisms allow to securely verify whether, within a given
> >    path, all packets traversed all the nodes that they are supposed
> to
> >    visit.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-sfc-proof-of-transit/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-sfc-proof-of-transit-06
> >
> https://datatracker.ietf.org/doc/html/draft-ietf-sfc-proof-of-transit-
> 06
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-proof-of-transit-06
> >
> >
> > 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.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/[sfc] I-D Action:
> draft-ietf-sfc-proof-of-transit-06.txt
> > internet-drafts@ietf.org Tue, 16 June 2020 12:52 UTCShow header
> >
> >
> >
> >
> >
> >
> >
> > ftp://ftp.ietf.org/
> 
> _______________________________________________
> 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.