IETF Logo Mail Archive

Re: [core] 🔔 WGLC for Resource Directory

Ted Lemon <mellon@fugue.com> Tue, 28 May 2019 17:43 UTC

Return-Path: <mellon@fugue.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 5F984120048 for <core@ietfa.amsl.com>; Tue, 28 May 2019 10:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 REU6kZ_xCf4e for <core@ietfa.amsl.com>; Tue, 28 May 2019 10:43:32 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11613120123 for <core@ietf.org>; Tue, 28 May 2019 10:43:32 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id h2so8354090pgg.1 for <core@ietf.org>; Tue, 28 May 2019 10:43:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Hn8UP2qpDulgsqVcPWYXv/krPGjHNWpvw8c371w8fF0=; b=1vBYQVnt5bZYRXUcrSAt9M13k5ZBkrc7MXtdaD9ZjGbAffGK+pfDIb+ddE/OmnEcYH GiQ8c4NKXMo1Ws4szrFnjPMUdxKwcjh6BuKSzhiynYY47ZaIBv8pmxGmKzwxpj+cGg2l XswUhOm9mbkOhVasokU0XPXCE3AtJgVmGo3xSIpMYlOTAgmSdKL2z/OiKzORLZsRXJKv x08B6OyAfXtBC67J5O2vgrYH5gcPkMDGw4THmJt4JaLIDCLOIf+ZnbR6hp7sI8YUt9oS D/BLZ9AaSC7cq+g6VxEStxXX9lDKqy00/eFgjXY2v/uHNuRDyZfHO1g6NAiq11fdHl5d zaaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Hn8UP2qpDulgsqVcPWYXv/krPGjHNWpvw8c371w8fF0=; b=rlDXeVEyXzjui4/nIn7MHGanzFRHDoADbe911M4h2D79SX52YAHOCQe93h5IZfDGgi +Tv1duWKkcDjWfi54pAwz45PRfCW0wp4GxoR7tN4Dp2snJlTNIfnLkXPIe9CUzov16TT E0M972MpsZ8H8QseQeYn8Wv3TlfJP0OHkFNWWQDJHjudbN+XAMUX53niKQr6x4FnE5Yg LyvZ9beooh21o2PU9DyfMMoZ0GgXZMS2JrloLFLmq6rp4ZQgLO7NqolAYGgLNu30VhS6 I87BOYTVEyWTCBRauPKWwA0nUwyLlfGPOW4lsVZzsRvVh53LzThSIsMXmBUwJRECQW45 uANw==
X-Gm-Message-State: APjAAAVEB0XMxGQxJRT1ucMQt3mZCSl+/uyTVxCHWUKlPRFf9h+gBQM1 /Lg//umtkmrgw68gFtG078DATA==
X-Google-Smtp-Source: APXvYqxn5UmKm1dpEUA8DFwwgOuEbU6IkSuYbci805qZBzJwiHBTe6X8v0hpRjx5+Ay2hkoJ5/L3OA==
X-Received: by 2002:a63:1657:: with SMTP id 23mr79788466pgw.98.1559065410697; Tue, 28 May 2019 10:43:30 -0700 (PDT)
Received: from [17.230.170.110] ([17.230.170.110]) by smtp.gmail.com with ESMTPSA id b21sm19207098pfb.46.2019.05.28.10.43.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 May 2019 10:43:29 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <137192BD-7638-4D2E-A6E5-E1618499366F@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3DDD7066-0767-494C-9CB7-91BBFE6C2FEE"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.2\))
Date: Tue, 28 May 2019 10:43:28 -0700
In-Reply-To: <f7fe549e40f879c6f46a0a7d8242241a@bbhmail.nl>
Cc: core@ietf.org, Stuart Cheshire <cheshire@apple.com>
To: consultancy@vanderstok.org
References: <AM5PR0701MB230754CF5CD643B6B7DC1A7697420@AM5PR0701MB2307.eurprd07.prod.outlook.com> <EBFF17D7-86DF-4C3E-B69E-EF69206A6D17@fugue.com> <02585a832a91742de93f6d311259ae61@bbhmail.nl> <CF34C053-A417-4914-BB28-B4E47E97A625@fugue.com> <498bff27c1804f08365f0e11e6d24050@bbhmail.nl> <32B6BB77-91AA-4F85-B5EA-6AC8C6407F7F@fugue.com> <a97554a90cfd49ce21fb59e43ff0ed63@bbhmail.nl> <33B4FD70-E650-47E4-A603-BD4928E4C47F@fugue.com> <f7fe549e40f879c6f46a0a7d8242241a@bbhmail.nl>
X-Mailer: Apple Mail (2.3445.104.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/2Qn4zDawoPqHVnPox9gfzdxbRho>
Subject: Re: [core] 🔔 WGLC for Resource Directory
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: Tue, 28 May 2019 17:43:34 -0000

On May 27, 2019, at 12:31 AM, Peter van der Stok <stokcons@bbhmail.nl> wrote:
> For example, in those cases a border router is present once a month for a few hours to read out data.
> No RDA0 option,  avoid multicast, no host names. Therefore, the configured RD IP address seems reasonable. 

Isn’t it the case generally that in order for the device to know that there is a BR present, the BR has to do some kind of multicast?

v2.23.0 | Report a Bug | By Email