[pcp] Agenda question about Wednesday's meeting

Sam Hartman <hartmans@painless-security.com> Tue, 16 October 2012 03:56 UTC

Return-Path: <hartmans@painless-security.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 337351F0CA0 for <pcp@ietfa.amsl.com>; Mon, 15 Oct 2012 20:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.365
X-Spam-Level: ****
X-Spam-Status: No, score=4.365 tagged_above=-999 required=5 tests=[AWL=0.077, 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, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UmdCfOlhUW0P for <pcp@ietfa.amsl.com>; Mon, 15 Oct 2012 20:56:49 -0700 (PDT)
Received: from ec2-23-21-227-93.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 945A41F0C9C for <pcp@ietf.org>; Mon, 15 Oct 2012 20:56:49 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 6AA5120146 for <pcp@ietf.org>; Mon, 15 Oct 2012 23:56:33 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id DE6EC4AD5; Mon, 15 Oct 2012 23:56:40 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: pcp@ietf.org
Date: Mon, 15 Oct 2012 23:56:40 -0400
Message-ID: <tsl7gqr83yf.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [pcp] Agenda question about Wednesday's meeting
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, 16 Oct 2012 03:56:50 -0000

Hi.
First, I want to thank the folks working on the PANA proposals.
Based on discussion, I think the issues resolved at the last meeting
regarding  version negotiation and other discussions that were
PANA-specific brought up at the meeting have been resolved to my
satisfaction.
I still prefer the PANA encapsulation option to the PANA
demultiplexing option, although I agree that both PANA options will
work.

At last meeting, we got kind of stuck in the details of the specific
proposals. It was good that we discussed the specific version number to
use and it was good that we discussed some of the rationale for single
ports.
However, we didn't get around to discussing the broader architectural
questions like:

1) Does PCP need re-authentication

2) Do we want authentication to be server or client initiated in PCP?

ETc.
We had some great discussion leading up to the last meeting and  were
approaching understanding of the architectural issues that I think we
need to consider in order to make a decision about the authentication
approach.
However, we got stuck  in the details and didn't get a chance to discuss
these issues.

I want to confirm that we're going to give priority to these
architectural issues in this call, focusing on them rather than updates
to the PANA proposals or discussion of the specifics of the PCP-specific
approach.  I hope we're all on the same page on that.  If not, I'd like
to start an agenda bashing discussion now.