Re: [stir] Review of: draft-ietf-stir-rfc4474bis-10

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 19 August 2016 15:49 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C453612DB96 for <stir@ietfa.amsl.com>; Fri, 19 Aug 2016 08:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60qr94afNlQh for <stir@ietfa.amsl.com>; Fri, 19 Aug 2016 08:49:42 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B424512DB94 for <stir@ietf.org>; Fri, 19 Aug 2016 08:49:42 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-11v.sys.comcast.net with SMTP id am1kbsvhTlSxsam3Bb7SRo; Fri, 19 Aug 2016 15:49:41 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-10v.sys.comcast.net with SMTP id am3Abxkk9duaCam3Bb3gaR; Fri, 19 Aug 2016 15:49:41 +0000
To: stir@ietf.org
References: <c3a85ffc-8340-ac54-4d8e-21a16fefd032@dcrocker.net> <D3D41210.1A72E4%jon.peterson@neustar.biz> <CAHBDyN7W8zkgGjeUqzGaxLfRD-nFDgD9R3kxioQ47Kbp4_B8EA@mail.gmail.com> <6bd1e4bc946a4a02a1f4fdac385984b9@PLSWE13M08.ad.sprint.com> <D3DB2EE9.1A7B59%jon.peterson@neustar.biz> <fbf38cef-bfb0-60df-175d-c57362917c4c@dcrocker.net>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <8b99c0c3-67af-9eec-e6c0-6fad56413318@alum.mit.edu>
Date: Fri, 19 Aug 2016 11:49:39 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <fbf38cef-bfb0-60df-175d-c57362917c4c@dcrocker.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfPZGQ+StMKQTnp7SCR+Cp+GbPS8qa4N9I78ecqiDJHMYBaZS/jD4lREWdHirES8gkEPDVVSZu+4A2sV1KzCimmdFhhjNR4feG89WY7dU+odUXSWU3t2z p5KUNcSJz94ZwOSz+O59cjMs+5DW/pyE7P2ru3r991WjYcjU564l0RaWc9AbMKWBSyT9AZKQJx5yLQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/mVQQQy8soF7cGD9_VjCseVYoi1E>
Subject: Re: [stir] Review of: draft-ietf-stir-rfc4474bis-10
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 15:49:44 -0000

On 8/18/16 1:05 PM, Dave Crocker wrote:
> On 8/18/2016 9:48 AM, Peterson, Jon wrote:
>> Oh, we've allowed for multiple Identity headers for some time - the
>> problem is we don't really give any reason why we allow them or any
>> sense of what it might mean to have more than one. We need to say at
>> least something about that, though largely this is a matter of forward
>> compatibility with some future use cases that we know are under
>> consideration that we don't want to rule out.
>
>
> 1. In the abstract, there could be different identifiers that are
> authenticated.  That's probably not supposed to be allowed for a SIP
> environment, but since there apparently can be different identifiers
> used as input to validation, perhaps it is allowed.
>
> 2. There can be different authorities used to create the authentication.
> This permits trust assessment of a combination of entities making
> validity assertions.
>
> 3. There can be different technical details to the signature.  Different
> canonicalizations, different crypto algorithms, different keys.  All of
> these might affect survival through transit and/or ability of the
> recipient to process.

I think all of these are plausible and valid possibilities.

What this means is that any *prioritization* of these needs to be a 
decision made by the validator (perhaps differently for different 
validators in the same call), and not by the signers.

	Thanks,
	Paul