IETF Logo Mail Archive

Re: [secdir] Secdir last call review of draft-ietf-sfc-hierarchical-08

<mohamed.boucadair@orange.com> Wed, 13 June 2018 09:20 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB97130E0A; Wed, 13 Jun 2018 02:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 8E1bXcuMq-Ap; Wed, 13 Jun 2018 02:20:14 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.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 A33EC130EB2; Wed, 13 Jun 2018 02:20:14 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 2D3EEC078D; Wed, 13 Jun 2018 11:20:13 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.58]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 01E08120083; Wed, 13 Jun 2018 11:20:13 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0389.001; Wed, 13 Jun 2018 11:20:12 +0200
From: mohamed.boucadair@orange.com
To: Sean Turner <sean@sn3rd.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-sfc-hierarchical.all@ietf.org" <draft-ietf-sfc-hierarchical.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Secdir last call review of draft-ietf-sfc-hierarchical-08
Thread-Index: AQHT91gIey1rcuKs3U+uFAmpphPKT6Rd/37g
Date: Wed, 13 Jun 2018 09:20:12 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DF357C6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <152760355124.12572.4328281075629737814@ietfa.amsl.com>
In-Reply-To: <152760355124.12572.4328281075629737814@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.2]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/UqDTWGo0_FD6Dpa8dSDcyHjT11I>
Subject: Re: [secdir] Secdir last call review of draft-ietf-sfc-hierarchical-08
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2018 09:20:20 -0000

Hi Sean, 

Thank you.

Figure 4 is provided as ** an example ** to illustrate how the flow ID can be placed on the NSH. This is not normative.   

Cheers,
Med

> -----Message d'origine-----
> De : Sean Turner [mailto:sean@sn3rd.com]
> Envoyé : mardi 29 mai 2018 16:19
> À : secdir@ietf.org
> Cc : draft-ietf-sfc-hierarchical.all@ietf.org; ietf@ietf.org; sfc@ietf.org
> Objet : Secdir last call review of draft-ietf-sfc-hierarchical-08
> 
> Reviewer: Sean Turner
> Review result: Ready
> 
> Hi! I’m no expert on SFC so I spent some time reviewing RFC7665 and Simon
> Josefsson’s secdir review [0] as well as RFC 8300 and 8393.  It looks like
> all
> the things I was going to pick on are addressed by the references.
> 
> I’ll let somebody else on the IESG debate whether Figure 4 is trying to be a
> little different than the rest of this architectural document by specify some
> protocols bits; informational still?
> 
> [0]
> https://datatracker.ietf.org/doc/review-ietf-sfc-architecture-08-secdir-lc-
> josefsson-2015-05-28/

v2.23.0 | Report a Bug | By Email