Re: [pcp] EAP-over-PCP

Margaret Wasserman <margaretw42@gmail.com> Tue, 18 September 2012 11:12 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 A833521F85C4 for <pcp@ietfa.amsl.com>; Tue, 18 Sep 2012 04:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 p5HQdS4JMcTs for <pcp@ietfa.amsl.com>; Tue, 18 Sep 2012 04:12:28 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id C825C21F8422 for <pcp@ietf.org>; Tue, 18 Sep 2012 04:12:27 -0700 (PDT)
Received: by qadz3 with SMTP id z3so2418815qad.10 for <pcp@ietf.org>; Tue, 18 Sep 2012 04:12:27 -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 :message-id:references:to:x-mailer; bh=exdHMi2Iddq+fQ5vgnnqwzwGBZic0qv7lcoPA9n0HCk=; b=MIBXCrJxaIE1Pbm/npljwKBMJ/fLVWC8uaa7HpMQKNy9yGka+a+1AfltWBxbVcrjBJ Hbj6NWe3cPY3DT5CVkw/OMn/mmRGzF5Ks16f8qUqHsXjBglxwZgZYjx8GNfIoF+0cPP0 okbMfZY2/LQw7/WUj8cf5lDvkydKZV7P//zX+PVWxRhWGmBa7fL2J6gXTGLST5kV1ZHq 83GnAo1ubythT/UL90OsZQQheOOsts7eeQSIuhd7qIvJdmyy7U47K7M7ov1wP1ifSpae LJAVr2NpJ9IXkjM9mpXVsQYBnd6NnhD/uOVWclqC5UXAVPyNXh9Jj5uS5qhYjluc1ajI mXTQ==
Received: by 10.229.137.68 with SMTP id v4mr9203764qct.51.1347966747240; Tue, 18 Sep 2012 04:12:27 -0700 (PDT)
Received: from lilac-too.home (pool-71-184-79-25.bstnma.fios.verizon.net. [71.184.79.25]) by mx.google.com with ESMTPS id fl3sm19121394qab.3.2012.09.18.04.12.24 (version=SSLv3 cipher=OTHER); Tue, 18 Sep 2012 04:12:25 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-12-292355293"
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <9A2322BB-699A-4A71-89D5-9E3E48979272@yegin.org>
Date: Tue, 18 Sep 2012 07:12:22 -0400
Message-Id: <F05BA698-ADEB-42A4-BCDA-F0F5D9F3AC2D@lilacglade.org>
References: <14C7F4F06DB5814AB0DE29716C4F6D6702E12ABC28@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <CB96F2AF-7545-457D-96EB-F78B7666C00C@yegin.org> <tsl1ui0wvmo.fsf_-_@mit.edu> <E91C9554-FBCF-4324-A1BF-5C4D75F5264A@yegin.org> <9A2322BB-699A-4A71-89D5-9E3E48979272@yegin.org>
To: Alper Yegin <alper.yegin@yegin.org>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] EAP-over-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: Tue, 18 Sep 2012 11:12:28 -0000

On Sep 18, 2012, at 4:40 AM, Alper Yegin wrote:
> Earlier version of the I-D had softly acknowledged that:
> 
>    Some of the ideas in this document were adopted from PANA[RFC5191].
> 
> Interestingly, this statement disappeared in the latest doc

Um, the latest doc describes two solutions, one of which _is_ PANA (encapsulated in PCP), so it would seem a bit strange to claim the ideas were "adapted from" PANA...

> If you folks revert the terminology back to PANA's, we can be done :-)

Both mechanisms described in the current draft are encapsulation mechanisms, and I was under the impression that you were arguing that a demultiplexing (side-by-side) mechanism was substantially preferable...  Am I missing something?

The PCP-Specific mechanism is very similar to an encapsulated PANA mechanism with certain specific differences:

- It is a simplified protocol, because it doesn't need to handle things like address reallocation that are specific to the Network Access case.
- It is fully integrated with the PCP header, so there are no overlapping fields that need to be check for consistency, etc.

So, if we re-titled our initial PCP-Specific proposal to be called "Simplified PANA Authentication for PCP", would that resolve all of your concerns?

I don't have a strong personal preference between these two approaches, because they aren't very different.  If we do end-up defining an encapsulated PANA mechanism, our draft will need to describe what subset of PANA needs to be implemented/supported for use with PCP, and it will need to explain how to consistency-check the PANA packet against fields in the PCP header.  So, we'll end up with a protocol that uses (a subset of) PANA and requires a bit more run-time processing and a few more error cases than a PCP-Specific solution (for the consistency checking), but one that is otherwise very similar.

As I have said over and over, all of these solutions have far more in common (conceptually, functionally and even in the bits they will send on the wire) than their differences.

Margaret