IETF Logo Mail Archive

Re: [Anima-bootstrap] M_FLOOD and mDNS (was Re: Anima bootstrap: discover protocol multicast notes)

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 16 February 2017 19:09 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC2B12941A for <anima-bootstrap@ietfa.amsl.com>; Thu, 16 Feb 2017 11:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 2cM-oK1QGzfI for <anima-bootstrap@ietfa.amsl.com>; Thu, 16 Feb 2017 11:09:42 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A3BA12955E for <anima-bootstrap@ietf.org>; Thu, 16 Feb 2017 11:02:08 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DFFFB2009E; Thu, 16 Feb 2017 14:23:40 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4133A636BB; Thu, 16 Feb 2017 14:02:07 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: consultancy@vanderstok.org
In-Reply-To: <9341e5c2d9ecb3decf70fb68da0f6f50@xs4all.nl>
References: <20170117171732.GA14606@faui40p.informatik.uni-erlangen.de> <20170117172824.GB14606@faui40p.informatik.uni-erlangen.de> <11820.1486936729@obiwan.sandelman.ca> <8a8567bb1b9993c077d84abf4bfc82f3@xs4all.nl> <18113.1487095987@obiwan.sandelman.ca> <f035b7675e761046b6486db3f54794e8@xs4all.nl> <20582.1487174374@obiwan.sandelman.ca> <77ef9d9a0fe928ce0d857de188fc991b@xs4all.nl> <26993.1487255351@obiwan.sandelman.ca> <9341e5c2d9ecb3decf70fb68da0f6f50@xs4all.nl>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Thu, 16 Feb 2017 14:02:07 -0500
Message-ID: <22170.1487271727@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-bootstrap/y4WiIW9MzhxKwbCkxJ00gVfFAKY>
Cc: anima-bootstrap@ietf.org, Toerless Eckert <tte@cs.fau.de>
Subject: Re: [Anima-bootstrap] M_FLOOD and mDNS (was Re: Anima bootstrap: discover protocol multicast notes)
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <anima-bootstrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-bootstrap/>
List-Post: <mailto:anima-bootstrap@ietf.org>
List-Help: <mailto:anima-bootstrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 19:09:43 -0000

peter van der Stok <stokcons@xs4all.nl> wrote:
    >> I'm not sure what is CoAP discovery... tell me about it!
    >>
    >> And we are talking about non-802.15.4 (like) networks, because I think
    >> 15.4 networks can be handled differently.

    > Below the text to appear in the est-coaps draft.  I hope it is clear;
    > otherwise I can send text from the resource directory draft where the
    > subject is more exhaustively treated.
    > _________________________________________________________________ The
    > presence and location of (path to) the EST-coaps resources are
    > discovered by multicasting a GET request to "/.well-known/core"
    > including a resource type (RT) parameter with the value "core.est"

Ah, I see.

    >      REQ: GET /.well-known/core?rt=core.est
    >      RES: 2.05 Content </est>; rt="core.est"



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email