[pcp] Authentication scenarios (was Re: PANA implementatinos to consider)

Alper Yegin <alper.yegin@yegin.org> Mon, 17 September 2012 08:02 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 A6A9E21F846E for <pcp@ietfa.amsl.com>; Mon, 17 Sep 2012 01:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level:
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 XIvn3WRDhmj2 for <pcp@ietfa.amsl.com>; Mon, 17 Sep 2012 01:02:47 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 78F7521F846D for <pcp@ietf.org>; Mon, 17 Sep 2012 01:02:47 -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=mrus2) with ESMTP (Nemesis) id 0MRGkB-1T5VYE0XvT-00U7n1; Mon, 17 Sep 2012 04:02:45 -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: <6F4080C4-A6E2-4FC0-9D3E-61992E86C22F@gmail.com>
Date: Mon, 17 Sep 2012 11:02:26 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <040C6F6B-1884-49FD-B51C-E82F9F9772F4@yegin.org>
References: <0MZjvC-1SyMXc0ZaA-00Lf23@mx.perfora.net> <F621C78A-2005-46E4-969C-DF25495A735A@yegin.org> <B860EA81-0451-4F26-BF46-382176DC9103@lilacglade.org> <6657E02B-2D08-40BE-A567-F8AB976F2741@yegin.org> <6F4080C4-A6E2-4FC0-9D3E-61992E86C22F@gmail.com>
To: Margaret Wasserman <margaretw42@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-Provags-ID: V02:K0:OI5/CAP9UtnlVp0PqjIwaSDXB9OCk9ev8Pspdie5VNR Fbt7D45JLm6VDpkea/k3CklwwXFMVOeVzQHUhjQThIwVprya1D Tz3/712DjxOCpZfcbDblnf7hlkdwnXY0IycdZGKWSRrVBQLmq0 JHkc/sHiTPYmSZSTW80WkhZEgSYgb+xc4KuZCxrW7GfUpLzjYF 69tvpxCDLB9cY+fneMOPowViu8KMVOpUYq7bnWLx0zhGi6sr88 fk/L434rDEKp+YG/KaGGAyzZeokvnKxSXqFkXcB/GhpwwWGQlM fJfx1nAd/VpdSs7G5yGC3TjgkuXKWw4J6+UwJVbnhI91cP1WGB 4jSIsuP6Rr9zoUsaV+WbrMO/eKuX+6ZsaJI6fhplsM6VjRrI30 de98NTK/raXOg==
Cc: pcp@ietf.org
Subject: [pcp] Authentication scenarios (was Re: PANA implementatinos to consider)
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: Mon, 17 Sep 2012 08:02:48 -0000

>> I'd like to first understand how the client-side decides when to use authentication, and when not to?
>> Can you, or someone, explain that? Once I understand the scenarios we are trying to cover, I can come back and answer your question.
> 
> There are two cases we have considered where PCP clients may send authenticated PCP requests:
> 
> (1) Cases where the client sends an unauthenticated request and is told that authentication is required, so it retries with an authenticated request.  
> 
> (2) Cases where the client initially attempts to send an authenticated request.
> 
> In the first case, the PCP Server will (we hope :-)) not return the "authentication required" error if it doesn't actually support authentication.  But, in the second case, a client may try to send an authenticated request to a PCP Server that does not support authentication.  Obviously, an error will result, be we want to be certain that the error can be properly detected and returned to the user, so that the user can understand what went wrong.
> 


Few questions:

- Why is there an unauthenticated case? Or, under what real-life scenarios would authentication be necessary? And under what real-life scenarios would authentication be unnecessary? 

- If authentication is optional, is it client's preference to use it, or network's? Would client ever attempt to use it w/o knowing network's preference? Would it bail out if network does not support/use it? 

- Are we talking about optional to use or optional to implement? You mentioned "PCP Server that does not support authentication".


Thanks.

Alper




> Margaret
> 
>