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

Hannes,

I am not completely clear.  Are you saying that the RD should not have the endpoint name parameter as a defined property or something else?

Jim

From: core <core-bounces@ietf.org> On Behalf Of Hannes Tschofenig
Sent: Wednesday, April 4, 2018 10:41 AM
To: Jaime Jiménez <jaime.jimenez@ericsson.com>
Cc: core@ietf.org WG <core@ietf.org>
Subject: Re: [core] Endpoint Client Name / Endpoint Name in RD draft

Hi Jaime, 

using IP address and port for an endpoint (client) name would not be a good idea. 

In general, it was not a good idea to have this parameter defined in the first place. It might actually be better to remove it altogether. 

Ciao

Hannes

From: Jaime Jiménez [mailto:jaime.jimenez@ericsson.com] 
Sent: 04 April 2018 17:32
To: Hannes Tschofenig
Cc: core@ietf.org <mailto:core@ietf.org>  WG; Carsten Bormann
Subject: Re: [core] Endpoint Client Name / Endpoint Name in RD draft

Hi,

Note that endpoint can refer to both source and destination, being and IP:port in its simplest form: 

https://tools.ietf.org/html/rfc7252#page-6 

The fact that LWM2M swaps those role names might actually add to the confusion, probably OMA LWM2M should be the one changing the terminology as the device is mostly a “server” hosting resources and only is a “client” during bootstrapping and registration. We could have used terms like “servient” instead but it might be too late for that.

Ciao!

- - Jaime Jiménez

On 4 Apr 2018, at 16.41, Hannes Tschofenig <Hannes.Tschofenig@arm.com <mailto:Hannes.Tschofenig@arm.com> > wrote:

Hi all, 

I noticed that the term “endpoint name” is used in the IETF RD draft while the OMA LwM2M spec uses the term “endpoint client name”. Endpoint is a confusing term since it is used differently in the CoAP spec than in the Web environment.

For this reason I believe it would be better to use the term “endpoint client name” also in the RD draft. This would improve alignment between the two specs.

Ciao

Hannes

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________
core mailing list
 <mailto:core@ietf.org> core@ietf.org
 <https://www.ietf.org/mailman/listinfo/core> https://www.ietf.org/mailman/listinfo/core

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. 