Re: [core] Endpoint Client Name / Endpoint Name in RD draft

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

Hi Hannes,

This e-mail of you to Matthias answers my questions I had before. 
thanks.
I was under the impression that you wanted to cater for malicious nodes 
that forged the authorization token.

> 
> The requirement for applications using Endpoint Client Names that are
> different from the names in the device certificates/authentication
> credentials for registration appears fuzzy and not well justified.
> What identifier do you believe you can put in an endpoint client name
> but not in a security protocol or what are the needs of an application
> that cannot be met?
> 
For example, the d=value is typically installation dependent.
To my knowledge, using d= is envisaged in building installations.
at the same time, the ep=value does not need a value with a semantic 
meaning, so any identifier will do in my opinion.

I could imagine that a claim with "d"= is added to the token when 
required.
Same approach for installations which can afford the overhead and want 
human readable ep names.

Peter