Re: [secdir] Review of draft-ietf-sfc-architecture-08

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 27 May 2015 17:00 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5A131A8740; Wed, 27 May 2015 10:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 7RTg6zd1u4Y6; Wed, 27 May 2015 10:00:04 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78F461A8713; Wed, 27 May 2015 10:00:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 5F1672510AB; Wed, 27 May 2015 10:00:04 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (75-146-28-117-Richmond.hfc.comcastbusiness.net [75.146.28.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 8F437251087; Wed, 27 May 2015 10:00:03 -0700 (PDT)
Message-ID: <5565F812.2080301@joelhalpern.com>
Date: Wed, 27 May 2015 13:00:02 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Benjamin Kaduk <kaduk@MIT.EDU>
References: <20150524211041.52cde768@latte.josefsson.org> <02FCDA94-FCC3-4875-AFBE-D07CC792B0C9@cisco.com> <alpine.GSO.1.10.1505252257290.22210@multics.mit.edu> <2DB7995B-8AF1-4EEE-971E-40A1A6294461@cisco.com> <alpine.GSO.1.10.1505261917240.22210@multics.mit.edu> <53F5D306-5860-4415-8AA4-390882ED94AB@cisco.com>
In-Reply-To: <53F5D306-5860-4415-8AA4-390882ED94AB@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/ygNOjXKxs2_HvEhWGDmKMmJWnb4>
Cc: "secdir@ietf.org" <secdir@ietf.org>, "draft-ietf-sfc-architecture.all@tools.ietf.org" <draft-ietf-sfc-architecture.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [secdir] Review of draft-ietf-sfc-architecture-08
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 27 May 2015 17:00:06 -0000

While I can live with the change you propose, I do not think it improves 
the document in any way.

Yours,
Joel

On 5/27/15 12:50 PM, Carlos Pignataro (cpignata) wrote:
> Hi, Ben,
>
...
>
> “Reevaluated” is significantly better, of course. Here’s another proposal:
>
> "The architecture described here is different from the current model, and
> moving to the new model could lead to different security arrangements and
> modeling. In the SFC architecture, a relatively static topologically-dependent
> deployment model is replaced with the chaining of sets of service functions.
> This can change the flow of data through the network, and the security and
> privacy considerations of the protocol and deployment will need to be
> reevaluated in light of the model.”
>
> Simon, Ben, Joel, Jim, Thomas, Alia, WG,
>
> Thoughs?
>
> — Carlos.
>
>> The word "reevaluated" is intended to indicate that a new analysis should
>> be performed, but not that a different conclustion must necessarily be
>> reached.
>>
>> -Ben
>>
>> P.S. "consdierations" in the second paragraph of section 6 is a typo
>