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

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Wed, 27 May 2015 18:53 UTC

Return-Path: <cpignata@cisco.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 91D481A8737; Wed, 27 May 2015 11:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 jcD8tpE_QByM; Wed, 27 May 2015 11:53:32 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 837111A8734; Wed, 27 May 2015 11:53:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16793; q=dns/txt; s=iport; t=1432752812; x=1433962412; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=kolSzwAE8QfYlbj+OFYBi/3/06LfDM9MdWeJ2C1SYhE=; b=kj8DtOQWIa4FZOsgYFnGoDclbbbbcN7M1gwZS4Cd2zRRNgYqmR8PCFD8 6LZVjB0RDb2GuLjk4kxH8oj3Sxu8Kdnzd+tlwrCAnZ4etJRuNv+kdMpV4 5NoODuQNm2zd41WZA5HpeqE3/ptUZX6NT/lt5EfG2TCJE9UGtx57R71nR 0=;
X-Files: signature.asc : 841
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BJBQDtEWZV/5NdJa1cDoI3S4EyBoMZvV+IPwKBQEwBAQEBAQGBC4QiAQEBAwEjVgULAgEGAhIGKgICMhcOAgQOBQ6IFwiREp0RpBoBAQEBAQEBAQEBAQEBAQEBAQEBAQEXizqFBQeCaC+BFgEEkEyCPIISgUOHOpcvI4M6Pm+BRoEBAQEB
X-IronPort-AV: E=Sophos;i="5.13,507,1427760000"; d="asc'?scan'208,217";a="423096635"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-6.cisco.com with ESMTP; 27 May 2015 18:53:20 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t4RIrKlQ016943 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 27 May 2015 18:53:20 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.147]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Wed, 27 May 2015 13:53:20 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Thread-Topic: [secdir] Review of draft-ietf-sfc-architecture-08
Thread-Index: AQHQllVoiI0EciI2k0ypB2MTIDGLzJ2L5tT3gAIA+oCAAJkTAIAAwU8AgAEfd4CAABfhgIAACmqA
Date: Wed, 27 May 2015 18:53:19 +0000
Message-ID: <F5E7E866-FB1C-48C0-8306-33579AE856CB@cisco.com>
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> <alpine.GSO.1.10.1505271355150.22210@multics.mit.edu>
In-Reply-To: <alpine.GSO.1.10.1505271355150.22210@multics.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.150.54.90]
Content-Type: multipart/signed; boundary="Apple-Mail=_50254197-7287-45DF-B9C7-57DF5C86C7F9"; protocol="application/pgp-signature"; micalg="pgp-sha256"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/28MJj-tHXVUfDmXAZdsfIQxBORA>
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 18:53:34 -0000

Ben,

> On May 27, 2015, at 2:16 PM, Benjamin Kaduk <kaduk@MIT.EDU> wrote:
>> I do not disagree. Are there areas beyond what’s already in the Security
>> considerations that require specific focus?
> 
> I think I only have the points I mentioned above (lack of clarity
> regarding protecting the original payload, and clear rhetoric).

OK, let’s make sure we have a way forward for both of them.

>>> That reevaluation will
>>> include security/privacy issues for the original payload as well as the
>>> classification and encapsulation data added by the SFC protocol(s).
>>> 
>>> 
>> 
>> Yes — which is what the doc already says.
> 
> Just to ensure we're getting through to each other, do you mind pointing
> to the specific text that you have in mind that is supposed to already
> say this?
> 

What changes the flow of data in the network (i.e., direct user traffic to the ‘remote machine’ (as you called it) is the overlay — that is why in the “Service Overlay” section of the Security Considerations we have:

        and can also include authenticity and integrity checking, and/or
        confidentiality provisions.

The use of the SFC Encapsulation is for SFP encapsulation and metadata sharing.

>> “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.”
> 
> I might add in "new" or "chained" before the very last "model", but this
> seems to catch the sentiment I was going for.

Either ‘chain’ or ‘new’ univocally disambiguates ‘model’ — sure.

> The idea would be to insert
> this as a new paragraph after the first paragraph of section 6?
> 

Yes, or as the first paragraph of Section 6, as a preamble to the section. Either.

Thank you,

— Carlos.

> Thank you,
> 
> Ben