Re: [pcp] Comparison of PCP authentication

Alper Yegin <alper.yegin@yegin.org> Tue, 07 August 2012 08:11 UTC

Return-Path: <alper.yegin@yegin.org>
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 1ADB121F85AD for <pcp@ietfa.amsl.com>; Tue, 7 Aug 2012 01:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level:
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, 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 Zesjq-MMej3F for <pcp@ietfa.amsl.com>; Tue, 7 Aug 2012 01:11:05 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id B4C1321F8624 for <pcp@ietf.org>; Tue, 7 Aug 2012 01:11:05 -0700 (PDT)
Received: from [192.168.2.5] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MFLYq-1SvPEP0B4G-00F02y; Tue, 07 Aug 2012 04:10:56 -0400
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <5020688F.4060004@toshiba.co.jp>
Date: Tue, 07 Aug 2012 11:10:38 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <955DC538-A1D9-4B19-B1A5-A7741EA7FB35@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> <075301cd7419$19557dd0$4c007970$@com> <5020688F.4060004@toshiba.co.jp>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
X-Mailer: Apple Mail (2.1278)
X-Provags-ID: V02:K0:jrVWfuKJBQQqbvYsMOJX2g8QlKYuSmqQnfeOWG8tdwn tY+TVckizwKQJFDwQ6F/N+8VIZlsZNoNh5wLS/sJe4uv5y1d+V vcJScbIudzMParde+0DefNBNtspBk4gGJBqYLWHQ6NEW/yK8gN HzG8aZCdYk0WIMrKrHjFhxRsmpyipcEFAWgMYckbYS+rHOWqJ3 DqFD+YMf/wBKmWMqgjjVy1uXVxHWYiLdD7Yrkx5b8DkzZS+Xbc usOjA306p1nEhLMAvRQaEgz9VdFyUWtjRZJ5VBXAKVB9VO0+cE rlX8QIiEpkZ2ZbUN/IaZcOAQbnftGV1fkaEHEC3LIYhhtTf2Le 2BFf99eYJ5jxcnNk1oFrbfi9V2yk09oIcnJvEjfCRT1S2nnZCu fTPFNPScUmeYw==
Cc: pcp@ietf.org
Subject: Re: [pcp] Comparison of PCP authentication
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, 07 Aug 2012 08:11:07 -0000

>> Also, if an update to PANA allows 0b00000010 in that first octet, we will
>> have a problem.  It would be safer if we assign the last two bits in that
>> first octet of PANA to must-be-zero.  Perhaps via an Errata against the PANA
>> spec, if we decide this is the best solution.
> 


> 
> If we specify a new use of PANA "Reserved" field, it cannot be an
> Errata because it is not a specification error.  It needs to be a new
> RFC that updates RFC 5191.


Those bits are reserved for "future." 
And because of this demux design, "now" we want to make sure no one will ever set bit#7.
What we need is to allocate that bit and state it's always set to 0. I don't think we need a separate RFC for this, this'd be the RFC that defines how PANA and PCP are used together.

Alper