[pcp] REQ-14 in PCP Authentication Requirements

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Wed, 17 July 2013 06:15 UTC

Return-Path: <tireddy@cisco.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 15BA921F9AA3 for <pcp@ietfa.amsl.com>; Tue, 16 Jul 2013 23:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 lK-Jh8j0Twtg for <pcp@ietfa.amsl.com>; Tue, 16 Jul 2013 23:15:47 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 4454D21F9A8C for <pcp@ietf.org>; Tue, 16 Jul 2013 23:15:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2526; q=dns/txt; s=iport; t=1374041747; x=1375251347; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ye3p8j5Ai5Ga65A6oxlrtvrVQbYI/HVYGGJEmMx+h2M=; b=Bm5tepGLOEDj6jwHfD4Dxg7H4T0gv/1aamoZa7YzLm1ES38vDcOGZ0Ia qqFfzZUYW6hpKagAFqNwZQTV4blh8OpnMnJkk1KM876/kV05NT6RZfv8E nQT2aQbx3J0Gv72Hu8PxEyUTgGba6Z+s2wzJTuyAPAauVquABusiTu3d7 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAHQ15lGtJV2a/2dsb2JhbABagwaBA8IygQ0WdIIjAQEBBIEFBAIBFgMEAQELHQcyFAkIAgQBEggTh3W1co89BjIGgwZuA4hvoDqDEoIo
X-IronPort-AV: E=Sophos;i="4.89,682,1367971200"; d="scan'208";a="235773245"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP; 17 Jul 2013 06:15:44 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6H6Fijw030553 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Jul 2013 06:15:44 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Wed, 17 Jul 2013 01:15:44 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Dave Thaler <dthaler@microsoft.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: REQ-14 in PCP Authentication Requirements
Thread-Index: AQHOgYO2dz+IlsSN4UWh+//hlms7JZlnUekQ
Date: Wed, 17 Jul 2013 06:15:44 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A14B9B7B8@xmb-rcd-x10.cisco.com>
References: <c91bb8469abe4b079e46454e022546e6@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <c91bb8469abe4b079e46454e022546e6@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.63.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [pcp] REQ-14 in PCP Authentication Requirements
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: Wed, 17 Jul 2013 06:15:53 -0000

I have a clarification for both the drafts - how do EAP-in-PCP, PANA solutions meet REQ-14 ?

--Tiru.

> -----Original Message-----
> From: Dave Thaler [mailto:dthaler@microsoft.com]
> Sent: Monday, July 15, 2013 6:03 AM
> To: pcp@ietf.org
> Subject: [pcp] CONSENSUS CALL on PCP security
> 
> The WG has discussed two approaches for using EAP with PCP:
> direct EAP-in-PCP vs using PANA.
> 
> At IETF 84, we polled the room and got 5 hands for direct EAP-in-PCP
> and 10 or 11 for PANA. There was significant confusion/disagreement
> around requirements and proposed solutions at that time.
> 
> At IETF 85, we again polled the room and got a different result, this
> time 12 hands for direct EAP-in-PCP and 6 for PANA. There was, however,
> still significant confusion/disagreement around requirements and
> proposed solutions.
> 
> Since IETF 85, we have made lots of progress on getting agreement
> on the requirements, and draft-reddy-pcp-auth-req now seems to be
> relatively stable without significant areas of disagreement known.
> Discussion may of course continue if new issues are raised but we
> believe any additional changes are unlikely to affect people's
> position on overall solution approach, i.e. direct EAP-in-PCP vs. PANA.
> 
> The general sense of the WG also seems to be that either approach could be
> made to fit the requirements, so we believe it is now time for us to
> determine consensus (draft-resnick-on-consensus is a great read)
> on the approach question. We know many folks would just like to
> make a decision and move on.
> 
> Hence the chairs would like to ask the WG which solution direction the
> WG should pursue in meeting the requirements. Please state your
> recommendation on this thread, preferably along with your rationale.
> Avoid responding on this thread to others' rationale, use a separate
> thread as needed.
> 
> To help us judge consensus, please use the template below and
> respond by SUNDAY JULY 28.
> 
> -Dave and Reinaldo
> 
> ---
> 
> 1) Could you *live with* EAP-in-PCP? If not, state reason you would object.
> 
>     <NO and state reason, or YES>
> 
> 2) Could you *live with* PANA? If not, state reason you would object.
> 
>     <NO and state reason, or YES>
> 
> 3) If you said yes to both 1 and 2, but have a strong preference between
> the two, which approach do you prefer and why?
> 
>     <EAP-in-PCP, or PANA>.  <state reason>
>