[core] /.well-known/core and multicast addresses
Jim Schaad <ietf@augustcellars.com> Fri, 07 December 2018 05:27 UTC
Return-Path: <ietf@augustcellars.com>
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 CAF4912875B for <core@ietfa.amsl.com>; Thu, 6 Dec 2018 21:27:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 SfbnS24PWaxp for <core@ietfa.amsl.com>; Thu, 6 Dec 2018 21:27:23 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 212E81277C8 for <core@ietf.org>; Thu, 6 Dec 2018 21:27:23 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 6 Dec 2018 21:22:19 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: core@ietf.org
Date: Thu, 06 Dec 2018 21:27:14 -0800
Message-ID: <004301d48ded$8487b9c0$8d972d40$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdSN7JL4UBoA1h0PSFKeNXctutRlCw==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/YatxrF_x_VGScDRBpJA1wTqV2uE>
Subject: [core] /.well-known/core and multicast addresses
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Dec 2018 05:27:25 -0000
I am unsure how to get to the correct answer in this case. I do a multicast get to /.well-known/core The response comes back on a unicast address with relative URIs and without an anchor. I resolve the relative URI against ??? At this point I am supposed to resolve against the origin of the target URI, but from my understanding this would be the multicast address which is probably the wrong answer but may not be. It would depend if this is a really a multicast resource or is just a unicast resource. However I am not sure where the hint is going to be deep in my code that I should resolve against the return address rather than against the query address. I would know that using the return address is wrong in the event that the query went first to a proxy or gateway before going to the correct location. Jim
- [core] /.well-known/core and multicast addresses Jim Schaad
- Re: [core] /.well-known/core and multicast addres… Christian Amsüss
- Re: [core] /.well-known/core and multicast addres… Jim Schaad
- Re: [core] /.well-known/core and multicast addres… Carsten Bormann
- Re: [core] /.well-known/core and multicast addres… Christian Amsüss
- Re: [core] /.well-known/core and multicast addres… Jim Schaad
- Re: [core] /.well-known/core and multicast addres… Christian Amsüss
- Re: [core] /.well-known/core and multicast addres… Peter van der Stok
- Re: [core] /.well-known/core and multicast addres… 'Christian Amsüss'