Re: [Anima-bootstrap] 6tisch join -01 documented posted

[Brian E Carpenter <[e-mail]>]

On 14/11/2016 12:08, Michael Richardson wrote:
> Brian E Carpenter <[e-mail]> wrote:
>     > My model was that the proxy would get all the floods available and
>     > choose the one it liked best, based on the available method and
>     > distance, using the weight and priority as for mDNS. (Personally I
>     > think the mDNS stuff is overkill, but Toerless suggested we should be
>     > feature-equivalent.)
> 
> I never proposed that the Proxy would learn of the registrar via mDNS, btw.
> 
>     > 2. Your CDDL looks OK to me. The format and semantics of the value
>     > field of a GRASP objective are completely flexible, so I don't see a
>     > problem with the first "request" to the Registrar being [IID,
>     > join-method]. The reply from the registrar could be [IID,
>     > another-join-method] if it didn't like the first one proposed. Once
>     > either side receives a join-method it likes, it would send
>     > [M_END,,[O_ACCEPT]] and we're done.
> 
>     > 3. Mini-question, is this really IPv6-specific? If not I'd prefer a
>     > name that flags it as an AN infrastructure objective, e.g. "AN_Join"
> 
> okay.  The problem in 6tisch for proxy<->registrar communication (admission
> control) is the TCP stack required. 

Right. I've been assuming that a "BRSKI-COAP" method is available, and if
we use GRASP Flood, no TCP is needed at the pledge side.

   Brian