Re: [pcp] single port PANA+PCP

Margaret Wasserman <mrw@LILACGLADE.ORG> Thu, 09 August 2012 19:17 UTC

Return-Path: <mrw@LILACGLADE.ORG>
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 EA2C021F86FD for <pcp@ietfa.amsl.com>; Thu, 9 Aug 2012 12:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.392
X-Spam-Level:
X-Spam-Status: No, score=-95.392 tagged_above=-999 required=5 tests=[AWL=-0.281, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
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 aoHq5dHawzhB for <pcp@ietfa.amsl.com>; Thu, 9 Aug 2012 12:17:30 -0700 (PDT)
Received: from ec2-23-21-76-251.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7CE21F86B3 for <pcp@ietf.org>; Thu, 9 Aug 2012 12:17:30 -0700 (PDT)
Received: from lilac-too.home (permutation-city.suchdamage.org [69.25.196.28]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id 4857D202A6; Thu, 9 Aug 2012 15:12:05 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-3--987378556"
From: Margaret Wasserman <mrw@LILACGLADE.ORG>
In-Reply-To: <BC3E2B3B-630B-443E-B43E-8A7D67E736B4@yegin.org>
Date: Thu, 09 Aug 2012 15:12:05 -0400
Message-Id: <81DFAB1F-55BD-427B-88D4-4558BDDC926E@LILACGLADE.ORG>
References: <9B57C850BB53634CACEC56EF4853FF653B6EC381@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <7FE144CF-00E3-4451-8CBE-A6A684DB7CC4@yegin.org> <067d01cd73fd$765a6c50$630f44f0$@com> <D6D2DEED-C35A-45AB-8B72-96195C308DB9@yegin.org> <57FF0F8E-1B86-410F-8B6B-C4893A28222F@lilacglade.org> <BB72B80F-0622-4A5B-A985-79D8AED13E0B@apple.com> <003b01cd7587$a111b760$e3352620$@com> <15990E87-2D59-49B1-845C-2A4CB5A1FBD6@lilacglade.org> <008801cd758f$3fd306e0$bf7914a0$@com> <C72CBD9FE3CA604887B1B3F1D145D05E2CE65225@szxeml528-mbx.china.huawei.com> <028801cd75d6$c5765490$5062fdb0$@com> <2F9BADF9-2D26-4651-91F2-DAAF3089B9E3@yegin.org> <9C09773C-F3CC-4BBA-AFE9-AE427DA58F6E@lilacglade.org> <BC3E2B3B-630B-443E-B43E-8A7D67E736B4@yegin.org>
To: Alper Yegin <alper.yegin@yegin.org>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] single port PANA+PCP
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: Thu, 09 Aug 2012 19:17:31 -0000

Hi Alper,

On Aug 9, 2012, at 11:41 AM, Alper Yegin wrote:
> 
> There was a clear decision at the meeting to go with a PANA-based solution, not with EAP-over-PCP solution. Given that the decision is already made, why do we need to keep other options still floating in the WG document?

I'm not a WG chair, so it is not my place to call consensus of the room.  However, I don't _think_ we actually had consensus at that point in the discussion...  IIRC (and you should feel free to refer to the minutes when available to check my memory), about 1/3 of the people who expressed an opinion preferred a PCP-specific approach and 2/3 preferred a PANA-based approach (either a PANA encapsulation or a PCP/PANA demultiplexing).

There was, IIRC, consensus that we wanted a single-port solution.

I'm hoping we will emerge from the interim conference call with consensus on a single approach to pursue, and I currently expect it will be one of the PANA-based approaches.  However, I don't think that has been completely nailed down yet.

We also have the open question from Dave Thaler about whether to consider at DTLS-based approach.  I would be interested in hearing from other members of the WG whether a DTLS-based approach is of enough interest that we should document what that would look like, and include it in the trade-off discussion at the interim, or not.

I'm not really looking for _more_ choices here, but I would like us to fairly considered all of the sensible options and make a solid, technical choice.

Margaret