Hi Brian.

The answer consists of a selection of text of section 7 of the draft.
The discovery follows the standard coap discovery.
________________________________________________________________
The discovery of the Join-Proxy by the
   Pledge is an extension to the discovery described in section 4 of
   [I-D.ietf-anima-bootstrapping-keyinfra].  In particular this section
   replaces section 4.2 of [I-D.ietf-anima-bootstrapping-keyinfra].

   The Pledge can discover a Join-Proxy by sending a link-local
   multicast message to ALL CoAP Nodes with address FF01::FD.  Multiple
   or no nodes may respond.  The handling of multiple responses and the
   absence of responses follow section 4 of
   [I-D.ietf-anima-bootstrapping-keyinfra].

The presence and location of (path to) the join-proxy resource are
   discovered by sending a MC GET request to "/.well-known/core"
including
   a resource type (RT) parameter with the value "brski-proxy"
   [RFC6690].  Upon success, the return payload will contain the root
   resource of the Join-Proxy resources.

____________________________________________________________ Looking
forward to your comments and suggestions,

Peter
Brian E Carpenter schreef op 2018-10-05 04:03:

> How does the constrained pledge discover the LL address of the constrained 
> proxy?
> 
> Regards
> Brian Carpenter
> 
> On 2018-09-30 09:13, [email protected] wrote: 
> 
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>> 
>> Title           : Constrained Join Proxy for Bootstrapping Protocols
>> Authors         : Michael Richardson
>> Peter van der Stok
>> Panos Kampanakis
>> Filename        : draft-vanderstok-constrained-anima-dtls-join-proxy-00.txt
>> Pages           : 10
>> Date            : 2018-09-29
>> 
>> Abstract:
>> This document defines a protocol to securely assign a pledge to an
>> owner, using an intermediary node between pledge and owner.  This
>> intermediary node is known as a "constrained-join-proxy".
>> 
>> This document extends the work of
>> [I-D.ietf-anima-bootstrapping-keyinfra] by replacing the Circuit-
>> proxy by a stateless constrained join-proxy, that uses IP
>> encapsulation.
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-vanderstok-constrained-anima-dtls-join-proxy/
>> 
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-vanderstok-constrained-anima-dtls-join-proxy-00
>> https://datatracker.ietf.org/doc/html/draft-vanderstok-constrained-anima-dtls-join-proxy-00
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> _______________________________________________
>> I-D-Announce mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> _______________________________________________
> Anima mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/anima
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima

Reply via email to