Re: [core] Questions and comments against the github version

[Peter van der Stok <[e-mail]>]

Jim Schaad schreef op 2018-12-11 18:41:

> FROM: Peter van der Stok <[e-mail]> 
> SENT: Tuesday, December 11, 2018 12:59 AM
> TO: Jim Schaad <[e-mail]>
> CC: [e-mail]; [e-mail]
> SUBJECT: Re: Questions and comments against the github version 
> 
> Hi Jim,
> 
> thanks, for the questions.
> One explanation for one question. 
> 
> Jim Schaad schreef op 2018-12-11 03:22:
> 
>> *  In section 5.3, I don't understand why the rule exists that if the
>> attribute values are different then the location of the registration needs
>> to be changed.   It seems that this could lead to some interesting conflicts
>> in behavior depending on what messages are used.  For example  (content
>> omitted for clarity):
>> 
>> POST /rd?ep=e1&foo=over
>> 
>> Res: 2.01 Created
>> Location-Path: /rd/4001
>> 
>> POST /rd?ep=e1&foo=under
>> 
>> Res: 2.01 Created
>> Location-Path: /rd/4002
>> 
>> As opposed to:
>> 
>> POST /rd?ep=e1&foo=over
>> 
>> Res: 2.01 Created
>> Location-Path: /rd/4001
>> 
>> POST /rd/4001?foo=under
>> 
>> Res: 2.01 Changed
>> 
>> <pvds>
>> The feeling was that a first ep having done the earlier registration /rd/4001 
>> should not be able to manipulate the 2nd registration by a 2nd ep, by removing /rd/4001
>> and having a registration /rd/4002 only known to 2nd ep.
>> </pvds>
>> 
>> [JLS] The only problem with this is that the query of endpoints needs to be changed so that the endpoint locations are not returned.  Once the query is done then the location is known to a 2nd ep.
>> 
>> <pvds>
>> Is true.
>> The above statement is not about security and hiding information.
>> It is to prevent non-malicious unwanted mistakes.
>> </pvds>