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

peter van der Stok <> Thu, 16 February 2017 15:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B328E129ADC for <>; Thu, 16 Feb 2017 07:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Yklif-9nmotP for <>; Thu, 16 Feb 2017 07:14:52 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8FA4D129509 for <>; Thu, 16 Feb 2017 07:14:46 -0800 (PST)
Received: from ([IPv6:2001:888:0:22:194:109:20:214]) by with ESMTP id lTEk1u00E0F6qFb01TEkwn; Thu, 16 Feb 2017 16:14:44 +0100
Received: from ([]) by with HTTP (HTTP/1.1 POST); Thu, 16 Feb 2017 16:14:44 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Thu, 16 Feb 2017 16:14:44 +0100
From: peter van der Stok <>
To: Michael Richardson <>
Organization: vanderstok consultancy
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <>
Message-ID: <>
User-Agent: XS4ALL Webmail
Archived-At: <>
Cc:, Toerless Eckert <>,
Subject: Re: [Anima-bootstrap] M_FLOOD and mDNS (was Re: Anima bootstrap: discover protocol multicast notes)
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 Feb 2017 15:14:54 -0000

>     > personally I would use CoAP discovery; we talk about CoAP here.  
> And
>     > specify a join-proxy resource-type in the coap registry.
> 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" 
    a resource type (RT) parameter with the value "core.est" [RFC6690].
    Upon success, the return payload will contain the root resource of
    the EST resources.  It is up to the implementation to choose its root
    resource, but it is recommended that the value "/est" is used, where
    possible.  The example below shows the discovery of the presence and
    location of management data.

      REQ: GET /.well-known/core?rt=core.est

      RES: 2.05 Content </est>; rt="core.est"