Re: [pcp] single port PANA+PCP

"Dan Wing" <dwing@cisco.com> Thu, 09 August 2012 17:07 UTC

Return-Path: <dwing@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 204D421F879F for <pcp@ietfa.amsl.com>; Thu, 9 Aug 2012 10:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.206
X-Spam-Level:
X-Spam-Status: No, score=-110.206 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8, 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 uFM7BBXN5kR6 for <pcp@ietfa.amsl.com>; Thu, 9 Aug 2012 10:07:45 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id CA14C21F87A1 for <pcp@ietf.org>; Thu, 9 Aug 2012 10:07:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1033; q=dns/txt; s=iport; t=1344532066; x=1345741666; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=dmNfaY/LFttKpT5vXXr8oDVCpY3dOt2cl/gOscLZdPY=; b=aauPQ2JpT+zB68QQfmM6CeOs8mSx80CWs/EyPQGzC2cLms3fp3/jTllg TV7s0yfbo5y1Xj29G969XtxqeCc7A37sslEe8ziWk12vZevYoV/TDA24b TS1ppGatxmV+0Y8BbB9HDh/xLF1iwj48MBeV3ACVVl8QNbj1FSknPfO9Q A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAIzgI1CrRDoI/2dsb2JhbABFqiCPQoEHgiABAQEECAoBFxA/DAEDAgkPAgQBASgHGSMKCQgBAQQTCxeHapsHoG2LD4ZkA4hOhQyWGIFmgn8
X-IronPort-AV: E=Sophos;i="4.77,741,1336348800"; d="scan'208";a="54559063"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 09 Aug 2012 17:07:44 +0000
Received: from dwingWS (sjc-vpn7-1991.cisco.com [10.21.151.199]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q79H7baC023470; Thu, 9 Aug 2012 17:07:44 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Alper Yegin' <alper.yegin@yegin.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>
In-Reply-To: <2F9BADF9-2D26-4651-91F2-DAAF3089B9E3@yegin.org>
Date: Thu, 09 Aug 2012 10:07:08 -0700
Message-ID: <03bd01cd7651$7db058b0$79110a10$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac12EeMVsBCuAh+gQKa5gwXkZmZlhwAO4eIQ
Content-Language: en-us
Cc: 'Margaret Wasserman' <mrw@lilacglade.org>, 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 17:07:47 -0000

> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@yegin.org]
> Sent: Thursday, August 09, 2012 2:32 AM
> To: Dan Wing
> Cc: 'Zhangdacheng (Dacheng)'; 'Margaret Wasserman'; hartmans@painless-
> security.com; pcp@ietf.org
> Subject: single port PANA+PCP
> 
> > If the PCP server doesn't want authentication, I believe we can
> always
> > rely on a PCP error response if for PANA messages and for
> > PCP-encapsulated (tunneled) PANA messages (which I believe are the
> two
> > proposals being considered)
> 
> My understand is that there are two alternatives we are considering for
> using PANA for PCP authentication over the same PCP port:
> 
> 1. Encapsulate PANA over PCP (e.g., define a dedicated PCP option that
> encapsulate PANA packet).
> 2. Define a way to demux PANA and PCP even when they operate over the
> same port (no encapsulation).
> 
> Right?
> 
> I might have lost track, just seeking confirmation.

Yes, I believe those are the two approaches being considered.

-d