Re: [pcp] CONSENSUS CALL on PCP security

Margaret Wasserman <margaretw42@gmail.com> Tue, 30 July 2013 11:27 UTC

Return-Path: <margaretw42@gmail.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AA1711E81DA for <pcp@ietfa.amsl.com>; Tue, 30 Jul 2013 04:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.993
X-Spam-Level:
X-Spam-Status: No, score=-1.993 tagged_above=-999 required=5 tests=[AWL=0.607, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e6XQUd-PPnqy for <pcp@ietfa.amsl.com>; Tue, 30 Jul 2013 04:27:10 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id E93E521F9EE5 for <pcp@ietf.org>; Tue, 30 Jul 2013 04:27:09 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 10so6577998pdi.11 for <pcp@ietf.org>; Tue, 30 Jul 2013 04:27:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=8ax3msdDKzotJQGh1xqNdXg/f/z7ntb0krowTfT5qvU=; b=lvrFuGeOx8mgd8LFpqoRUl1mzRMFDV39AgxVc9wt3otK5/pWz2I29nJ9Cj/GjlWhoe uzVg+wMV0E1uVw2Z+IjUagzKiWJpbHprO80a3LdVOrFZWkrRffz3TcyJmGVZKN5qAcMb ethBU4RT7pgWmm/T4YO00KLlj4SPzhXysTxkRH5v+gIPQoJ0hkb58PtNqTesBpklpJTE UHJ1im9ARB8ZnqsbWj/W3AnJFtxpHqUSaNQUZF4gL7q/Qk9kGGCRq1ZNpfgcWjxLzVxR p0dZrHXetdLwccvrTIPNYh+oTMnbzQtqg4NlQS34ptcv4we0ymInSJl6Oah2yaZOshu4 xY4g==
X-Received: by 10.68.100.98 with SMTP id ex2mr13390085pbb.36.1375183629674; Tue, 30 Jul 2013 04:27:09 -0700 (PDT)
Received: from ?IPv6:2001:df8::8:9c02:c82c:438d:d376? ([2001:df8:0:8:9c02:c82c:438d:d376]) by mx.google.com with ESMTPSA id iq6sm82603770pbc.1.2013.07.30.04.27.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 04:27:08 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <1A7721F2-825C-412C-A0A8-A7D0A149E3FC@yegin.org>
Date: Tue, 30 Jul 2013 13:27:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FCFCE6E5-0958-404C-9FB7-535D3D35DA2C@gmail.com>
References: <c91bb8469abe4b079e46454e022546e6@BY2PR03MB269.namprd03.prod.outlook.com> <913383AAA69FF945B8F946018B75898A14B9AE60@xmb-rcd-x10.cisco.com> <a9f43a37e6fb4a11a05a66fb75182604@BY2PR03MB269.namprd03.prod.outlook.com> <1A7721F2-825C-412C-A0A8-A7D0A149E3FC@yegin.org>
To: Alper Yegin <alper.yegin@yegin.org>
X-Mailer: Apple Mail (2.1508)
Cc: "pcp@ietf.org" <pcp@ietf.org>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Subject: Re: [pcp] CONSENSUS CALL on PCP security
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 11:27:11 -0000

I think we should try to reach consensus on a a way forward now.  If we don't get moving, we may not be able to finish any PCP security solution before the WG disappears, and I think it is important to have a security solution.  Because of that I do not support asking any new questions now.

From my perspective, though, the only PANA solution I can live with is the encapsulated approach.

I understand that it is possible to specify some sort of hack involving the version fields and/or create a new short header to allow the side-by-side PANA approach to work on a single port, but I think that is equally undesirable to running the side-by-side version on two ports.  

After talking to Subir about his implementation, he indicated that the PANA messages in his implementation are transmitted inside PCP headers, which (in my mind) means that he has implemented the encapsulated option.  The fact that he has said that he implements the side-by-side option makes me concerned that we may not have the same idea of what those two different options actually are.  We will need to make sure we know exactly what we are comparing before we ask people to choose between them.

Margaret


On Jul 16, 2013, at 10:01 PM, Alper Yegin <alper.yegin@yegin.org> wrote:

> Dave,
> 
> Last time we conducted this polling, the two pana-based solutions were asked separately.
> Based on the discussions and the result of the poll, I realized some people preferred one PANA solution over the other, with possibly varying preference with respect to the EAP-o-PCP solution.
> Bundling them up as one option is not a good idea.
> So, I suggest we pose them as separate questions (like we did last time). After all, they are technically different.
> 
> One other thing: 
> 
> I'm not sure if enough thought went into the PCP Proxy security. As much as I'd love to be DONE! with this discussion, I also want to make sure people feel comfortable having thought all aspects around the proxy use. For (very important) example, what kind of security associations are needed for securing the proxy use: An SA btw client and server, an SA btw client and proxy, an SA btw proxy and server -- which combinations of these are needed? Then we need to talk about how we dynamically create those using any one of these solutions.
> 
> Alper
> 
> 
> 
> 
> 
> On Jul 16, 2013, at 7:50 PM, Dave Thaler wrote:
> 
>>> -----Original Message-----
>>> From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>>> Sent: Monday, July 15, 2013 10:51 PM
>>> To: Dave Thaler; pcp@ietf.org
>>> Subject: RE: [pcp] CONSENSUS CALL on PCP security
>>> 
>>> Hi Dave,
>>> 
>>> In the poll when you refer to PANA, please clarify the draft you are referring
>>> to http://tools.ietf.org/html/draft-ohba-pcp-pana-04 or
>>> http://tools.ietf.org/html/draft-ohba-pcp-pana-encap-01 ?
>>> 
>>> --Tiru.
>> 
>> The question is intentionally agnostic as this is about a general approach,
>> not which specific implementation.  If it helps, you can interpret the
>> answer as "which of the two you think is better".
>> 
>> If the consensus is PANA rather than direct EAP-in-PCP, then we could 
>> ask as a follow-up question which of the two we should go with. If
>> you'd like to include your answer to that now though, feel free to
>> include that in your response to the call.
>> 
>> -Dave
>> 
>> 
>> 
>> _______________________________________________
>> pcp mailing list
>> pcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcp
> 
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp