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

[peter van der Stok <[e-mail]>]

> 
>     > 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" 
including
    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"
_____________________________________________________________
cheerio,
Peter