Re: [pcp] Revising PANA side-by-side approach

Margaret Wasserman <margaretw42@gmail.com> Sat, 06 October 2012 00:59 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 D985221F861C for <pcp@ietfa.amsl.com>; Fri, 5 Oct 2012 17:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 iW6W-XP4fWiQ for <pcp@ietfa.amsl.com>; Fri, 5 Oct 2012 17:59:07 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5B45521F857A for <pcp@ietf.org>; Fri, 5 Oct 2012 17:59:07 -0700 (PDT)
Received: by mail-gh0-f172.google.com with SMTP id g10so703982ghb.31 for <pcp@ietf.org>; Fri, 05 Oct 2012 17:59:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=LRdd6JwYBabj2HOqsk0GPn8GbmB/dKsjxvPq2Vh2T80=; b=RFXuObEzm2tFS31A2S7xc2+JwV1AATwj0Qfa+bNjrsYSijXuX4FPKyS5J4bav9nyFP updfmOIVLYo1YjMEC6OfENjoJkWw1FeqCfckiTp6ykzyS8kVtf33vytZY0MzqcQzXi0D ISNOCceqoBjc3EYMYiIKcF9Y/rIykdrfvLUe4oyMmQrwaVrIAopOQvy5n22ab6QIhZWO fu7WWRKf38rqV+yoYieK8Wf3PULUaeJ87xkb0ZWPdt5ULso3Hxuvt6vDrobOPO8XSAOp PMjmkIXuG/Acfkvh1lzW03pp0xlMWrZJg5hEzABMNdzWV/YiEyKdDt0hyMm5T0iFSpr+ /4nA==
Received: by 10.236.191.69 with SMTP id f45mr10416290yhn.8.1349485146898; Fri, 05 Oct 2012 17:59:06 -0700 (PDT)
Received: from [192.168.1.100] (66-190-170-209.dhcp.crtn.ga.charter.com. [66.190.170.209]) by mx.google.com with ESMTPS id e24sm16467084yhh.4.2012.10.05.17.58.58 (version=SSLv3 cipher=OTHER); Fri, 05 Oct 2012 17:59:03 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <506EF099.3030503@toshiba.co.jp>
Date: Fri, 05 Oct 2012 20:58:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABE07BD4-85E7-4A9B-9125-8507231DACBE@gmail.com>
References: <506E5175.3020802@toshiba.co.jp> <712CABEE-96A2-493A-B2F8-94BC2548E0FD@lilacglade.org> <506EF099.3030503@toshiba.co.jp>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] Revising PANA side-by-side approach
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: Sat, 06 Oct 2012 00:59:08 -0000

Hi Yoshi,

>> 1) Provide a clear explanation of what parts of PANA will be used with PCP.   For example, the notion of a network access enforcement point doesn't really make sense in a PCP context.
> 
> I agree that EP is not needed in the context of PCP authentication. We probably do not need
> to use 'I' (IP Reconfiguration) and 'P' (Ping) flags either.

I doubt we have any major disconnect regarding what parts of PANA would/wouldn't be used with PCP.  However, we need to capture that understanding and document it, for people who are attempting to implement PANA for use with PCP.  I believe we will find that we are only using a fairly small subset of PANA for this purpose.

>>  2) Describe a clean mechanism that allows PANA to be used for authentication of other protocols.
>> 
>> Overloading a single bit in the PCP version field, because it happens to coincide with a flag bit in PANA doesn't seem like a method that will work for other protocols, and I am concerned that it doesn't provide a clean basis for moving forward.

The cleanest mechanism, IMO, would be to define a demultiplexing header that is used to determine whether the contents beyond that header are a PCP packet or a PANA packet.  If we want to send that header over the PCP port, though, it needs to look like a PCP header, which quickly devolves to the encapsulation approach.

Margaret