Re: [Gen-art] Last Call review of draft-ietf-sfc-architecture-08

Jari Arkko <jari.arkko@piuha.net> Thu, 28 May 2015 12:51 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8341A914F for <gen-art@ietfa.amsl.com>; Thu, 28 May 2015 05:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 QcPbR-dHXwG0 for <gen-art@ietfa.amsl.com>; Thu, 28 May 2015 05:51:42 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 00E761A9151 for <gen-art@ietf.org>; Thu, 28 May 2015 05:51:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DE8E32CC5A; Thu, 28 May 2015 15:51:38 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a7pIVYPrN7N2; Thu, 28 May 2015 15:51:38 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E968E2CC49; Thu, 28 May 2015 15:51:37 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_931A0F47-FC8C-4801-87CA-2C06E0EEB7C7"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <555E7E17.9050608@gmail.com>
Date: Thu, 28 May 2015 15:51:38 +0300
Message-Id: <B6EC16FE-1CA9-49B2-9613-CF0AAC79FF4E@piuha.net>
References: <555E7E17.9050608@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/KYCbpc8HsMTzmW7Z7CPufcr_GhA>
Cc: Alia Atlas <akatlas@gmail.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Gen Art <gen-art@ietf.org>, Jim Guichard <jguichar@cisco.com>
Subject: Re: [Gen-art] Last Call review of draft-ietf-sfc-architecture-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2015 12:51:44 -0000

Thanks for your review, Tom

Jari

On 22 May 2015, at 03:53, Tom Taylor <tom.taylor.stds@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> Document: draft-ietf-sfc-architecture-08
> Reviewer: Tom Taylor
> Review Date:        2015-05-17
> IETF LC End Date:   2015-05-25
> IESG Telechat date: 2015-05-28
> 
> Summary:
> 
> There is one IPR declaration, which was repeated for two predecessor documents but not for the current draft. The draft is basically ready to go with a very minor issue and a few nits.
> 
> Major issues:
> 
> Minor issues:
> 
> The Security Considerations section rightly mentions the need to avoid leaking SFC information. However, it does this under the heading of "Classification". Could I suggest that the first two sentences of the "Classification" bullet be separated out under the title "Boundaries"?
> 
> Nits/editorial comments:
> 
> Sec. 1.2, third bullet from the bottom: spell out SFF on first use, and give a forward reference to the next section, i.e.,
>   "...interconnect the Service Function Forwarders (SFFs, see next
>    section) ..."
> 
> Sec. 1.2, next bullet: according to the RFC Editor Style Guide abbreviations list, FIB and RIB are not well-known abbreviations, hence need to be spelled out.
> 
> Sec. 1.3, Service Function Forwarder, last line: spell out SFP? I know the definition is just a few lines down, so this is a maybe.
> 
> Alternative suggestion: introduce a Section 1.3.1 at the beginning of the section, as follows:
> 
> "1.3.1 Key Abbreviations
> 
>   The terms listed here are defined in Section 1.3.2.
> 
>   SF	Service Function
>   SFC	Service Function Chain or Service Function Chaining
>   SFF	Service Function Forwarder
>   SFP	Service Function Path
>   RSP	Rendered Service Path"
> 
> Sec. 2.1, second para., third line from bottom: s/the the/the/
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art