Re: [core] My endpoint has two addresses

peter van der Stok <stokcons@xs4all.nl> Fri, 08 September 2017 07:28 UTC

Return-Path: <stokcons@xs4all.nl>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32562133142; Fri, 8 Sep 2017 00:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham 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 hm57FQz8ZxU7; Fri, 8 Sep 2017 00:28:43 -0700 (PDT)
Received: from lb3-smtp-cloud8.xs4all.net (lb3-smtp-cloud8.xs4all.net [194.109.24.29]) (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 2DC65133140; Fri, 8 Sep 2017 00:28:43 -0700 (PDT)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:208]) by smtp-cloud8.xs4all.net with ESMTPA id qDiTd2c4WcQyLqDiTde3Vv; Fri, 08 Sep 2017 09:28:41 +0200
Received: from 83-161-167-172.mobile.xs4all.nl ([83.161.167.172]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Fri, 08 Sep 2017 09:28:41 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Fri, 08 Sep 2017 09:28:41 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Jim Schaad <ietf@augustcellars.com>
Cc: draft-ietf-core-resource-directory@ietf.org, core@ietf.org
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <007801d32694$51c49790$f54dc6b0$@augustcellars.com>
References: <007801d32694$51c49790$f54dc6b0$@augustcellars.com>
Message-ID: <1f46d054a227bdba7dc07e5c22bd1549@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfFVbgnpdA71mmK2+Bk23DsDAuV0EZ5uynRCBDBbNaTiYMZIxQFVQAbzYQdUtesSw5xmmQTPQ544sYsR/vw+Zjw9+IF4ihUUQ2Ojsco/TBYmpWOYsOrrA QoorP/fuLUeyWHEqM+2A4dHRL02QThDcL0edOE+OiFsg/ERtvj7YYRvcJtdHqpSSDw3svuswkSyVCOFmMkYedD/W/Q/Sq0WRoIXFKbxi5Rd82z8bctiu2JkT dQ6J8Uiqtat65HwchF+eWw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/LZJIt7lT523d-LlSgwcxqI3TXlU>
Subject: Re: [core] My endpoint has two addresses
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 07:28:45 -0000

Hi Jim,

Indeed this is an issue that was also brought up by Dave Thaler, where 
he referred to the multiple types of coap schemes that became possible.

For the moment, we made the model such that and extension to multiple 
contexts is possible, but not yet supported by the RD, given that all 
these extensions are still under discussion,

Peter

Jim Schaad schreef op 2017-09-06 00:14:
> One of the issues that I just come up with, and might be part of an I 
> don't
> care space, is that if an endpoint has two different addresses then the
> registration resource cannot have two different addresses associated 
> with
> it.  You cannot have two different registration resources with the same
> endpoint name.  This means if I want to register both IPv6 and IPv4 (or
> other address types) with the same endpoint there is a problem.   I 
> also
> just realized that same issue arises with schema.  These only apply if 
> you
> want to use the context parameter.  If you are going to supply full URL
> addresses to resources then this is doable.  Given that the context
> parameter is for space savings, I wonder if some method of dealing with 
> this
> should be considered.  Possibly defining some type of context selector 
> or
> something?
> 
> Jim
> 
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core