IETF Logo Mail Archive

Re: [core] /.well-known/core and multicast addresses

'Christian Amsüss' <christian@amsuess.com> Mon, 17 December 2018 13:50 UTC

Return-Path: <christian@amsuess.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 ED84D128D68 for <core@ietfa.amsl.com>; Mon, 17 Dec 2018 05:50:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 tEty4YgCiQjm for <core@ietfa.amsl.com>; Mon, 17 Dec 2018 05:50:04 -0800 (PST)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70E13128766 for <core@ietf.org>; Mon, 17 Dec 2018 05:50:02 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id 074114250B; Mon, 17 Dec 2018 14:49:58 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 1B6354D; Mon, 17 Dec 2018 14:49:57 +0100 (CET)
Received: from hephaistos.amsuess.com (hephaistos.amsuess.com [IPv6:2a02:b18:c13b:8010::71b]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 9A9D334A; Mon, 17 Dec 2018 14:49:56 +0100 (CET)
Received: (nullmailer pid 4377 invoked by uid 1000); Mon, 17 Dec 2018 13:49:56 -0000
Date: Mon, 17 Dec 2018 14:49:56 +0100
From: 'Christian Amsüss' <christian@amsuess.com>
To: consultancy@vanderstok.org
Cc: Jim Schaad <ietf@augustcellars.com>, core@ietf.org
Message-ID: <20181217134955.GA3694@hephaistos.amsuess.com>
References: <004301d48ded$8487b9c0$8d972d40$@augustcellars.com> <20181212204344.GA665@hephaistos.amsuess.com> <04f001d4926d$9eac0070$dc040150$@augustcellars.com> <20181214111816.GA19507@hephaistos.amsuess.com> <002101d493cd$fe4f5de0$faee19a0$@augustcellars.com> <fdcfc56fad0b88e1ad8a602aea96e4b1@bbhmail.nl>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI"
Content-Disposition: inline
In-Reply-To: <fdcfc56fad0b88e1ad8a602aea96e4b1@bbhmail.nl>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/cqX9huuMIz0h2G9BG3tJxKg5tjU>
Subject: Re: [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: Mon, 17 Dec 2018 13:50:08 -0000

On Mon, Dec 17, 2018 at 11:38:30AM +0100, Peter van der Stok wrote:
> > Req: POST coap://[MCD1]/rd?ep=node1
>
> It might make sense to complement the example to remove the issue cited
> by Jim.
> What do you think?

We already have an example on that in there: In B.1/B.2 a GET is sent to
a multicast .well-known/core, and the sender's IP literal is replaced in
for further resolution steps.

Best regards
Christian

-- 
Yesterday is history, tomorrow is a mystery, and today is a gift. That
is why it is called the present.
  -- ancient saying

v2.23.0 | Report a Bug | By Email