Re: [core] /.well-known/core and multicast addresses
Peter van der Stok <stokcons@bbhmail.nl> Mon, 17 December 2018 10:38 UTC
Return-Path: <stokcons@bbhmail.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 9F5AE130E19 for <core@ietfa.amsl.com>; Mon, 17 Dec 2018 02:38:35 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 89Nbhsv4KjCz for <core@ietfa.amsl.com>; Mon, 17 Dec 2018 02:38:33 -0800 (PST)
Received: from smtprelay.hostedemail.com (smtprelay0061.hostedemail.com [216.40.44.61]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BDBF12D4F2 for <core@ietf.org>; Mon, 17 Dec 2018 02:38:33 -0800 (PST)
Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay08.hostedemail.com (Postfix) with ESMTP id CBCC2182CF671; Mon, 17 Dec 2018 10:38:31 +0000 (UTC)
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Spam-Summary: 2, 0, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :::::, RULES_HIT:41:72:152:355:379:582:599:800:960:962:967:968:973:983:988:989:1152:1189:1208:1221:1260:1313:1314:1345:1359:1431:1436:1437:1516:1517:1518:1535:1542:1575:1588:1589:1592:1594:1711:1712:1730:1776:1792:2198:2199:2553:2559:2562:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3870:3871:3872:3873:3874:4250:5007:6261:6657:6659:6678:7576:7903:8603:9177:10004:10400:10848:11232:11658:11914:12043:12663:12740:12895:13071:13095:13846:13972:14093:14096:14180:14181:14721:21060:21080:21324:21433:21451:21611:21627:30003:30054:30063:30076:30083:30090:30091, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:27, LUA_SUMMARY:none
X-HE-Tag: judge41_10351c7ae3711
X-Filterd-Recvd-Size: 5503
Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf13.hostedemail.com (Postfix) with ESMTPA; Mon, 17 Dec 2018 10:38:31 +0000 (UTC)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_1c547507ad83ab41094ee44d86d751eb"
Date: Mon, 17 Dec 2018 11:38:30 +0100
From: Peter van der Stok <stokcons@bbhmail.nl>
To: Jim Schaad <ietf@augustcellars.com>
Cc: 'Christian Amsüss' <christian@amsuess.com>, core@ietf.org
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <002101d493cd$fe4f5de0$faee19a0$@augustcellars.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>
Message-ID: <fdcfc56fad0b88e1ad8a602aea96e4b1@bbhmail.nl>
X-Sender: stokcons@bbhmail.nl
User-Agent: Roundcube Webmail/1.2.7
X-Originating-IP: [5.206.216.229]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/nRTTuhF6Ujp-9GaKgoRJ7ceRppw>
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 10:38:36 -0000
Hi Christian, It might make sense to complement the example to remove the issue cited by Jim. What do you think? Peter > -----Original Message----- > From: Christian Amsüss <christian@amsuess.com > > On Wed, Dec 12, 2018 at 02:54:18PM -0800, Jim Schaad wrote: > >> I was rather afraid that this was the case. So just to be specific >> because this is the context that I ran across the issue. >> >> As a client I am looking for an RD to register with. So I send the request: >> Req: GET coap://[MCD1]/.well-known/core?rt=core.rd* >> >> I get back one or more responses with the following links: >> >> Res: 2.05 Content >> </rd>;rt="core.rd";ct=40, >> </rd-lookup/ep>;rt="core.rd-lookup-ep";ct=40, >> </rd-lookup/res>;rt="core.rd-lookup-res";ct=40, >> >> (Note this is an example that is copied straight out of the RD draft.) >> >> I am now going to register myself by sending a registration request: >> >> Req: POST coap://[MCD1]/rd?ep=node1 > > Nope -- you're following a </rd> reference, and the base URI already contains > the IP literal that sent the response. Therefore, your registration POST already > goes to a unicast address. I don't see how you got to here. In you previous message you said: " You resolve against ... the origin of) the URI of the requested resource .... the IP literal of the multicast request as per section 8.2"
- [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'