[stir] comments on draft-rescorla-stir-fallback-02

Robert Sparks <rjsparks@nostrum.com> Fri, 16 June 2017 15:25 UTC

To: stir@ietf.org
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <8005efd1-b2ba-6a03-5914-e003f9aa38db@nostrum.com>
Date: Fri, 16 Jun 2017 10:25:42 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/CSVfF6EeIg4KzFxHAKqPP-fWKGc>
Subject: [stir] comments on draft-rescorla-stir-fallback-02
Precedence: list

A thought and an observation:

1) At the point where you're speculating how the CPS might figure out 
what objects to return for a given query, it occurs to me that the 
publisher could _say_ what objects are associated, at least in some 
circumstances - div in particular.

An agent making a diversion has possession of the original passport. 
Send it (or a hash of it) as part of the insertion request for the div 
passport. Then the CPS can bind it to the copy of the original it 
already has.

2) The treatment of multiple passports here further reinforces that the 
set of passports associated with a particular call is an unordered set 
(see my comment about the order of identity header field values in my 
comments on 'div')

[stir] comments on draft-rescorla-stir-fallback-02 Robert Sparks