Two minor things:
[O_IPv6_LOCATOR, fe80::1234, 41, nil]
The address is represented as 128 bit quantity, bytes .size 16 in CDDL, so
it will actually just be an in6_addr in C terms. If you really want
to write it down, 0xfe801234
nil is a valid element in CDDL, but is there
Regards
Brian Carpenter
On 09/01/2017 13:57, Michael Richardson wrote:
>
> Brian E Carpenter wrote:
> >> We want to use GRASP to permit the bootstrap proxy to discover where
> >> the Registrar(s) are. As far as I can see there are really two
> >> options, and they might not b
On 09/01/2017 14:02, Michael Richardson wrote:
>
> When I read:
> divert-option = [O_DIVERT, +locator-option]
>
> I think that it means that +locator-option means that one can multiple
> options, and that they would be inside an array?
>
> So, for example:
>
> [O_DIVERT, [ [O_IPv6_LOCATOR,
Michael Richardson wrote:
bc> Secondly, the methods aren't mutually exclusive. If the "normal"
bc> method is flooding an objective that I've called "AN_registrar" in my
bc> toy code, nothing prevents discovery/synchronize being used as a
bc> backup.
> Question: should all the
When I read:
divert-option = [O_DIVERT, +locator-option]
I think that it means that +locator-option means that one can multiple
options, and that they would be inside an array?
So, for example:
[O_DIVERT, [ [O_IPv6_LOCATOR, ipv6-address, transport-proto, port-number],
[O_IPv4_
Brian E Carpenter wrote:
>> We want to use GRASP to permit the bootstrap proxy to discover where
>> the Registrar(s) are. As far as I can see there are really two
>> options, and they might not be mutually exclusive.
>>
>> a) start a multicast M_DISCOVERY which will be propag
On 09/01/2017 06:27, Michael Richardson wrote:
>
> We want to use GRASP to permit the bootstrap proxy to discover where the
> Registrar(s) are. As far as I can see there are really two options, and they
> might not be mutually exclusive.
>
> a) start a multicast M_DISCOVERY which will be propaga
We want to use GRASP to permit the bootstrap proxy to discover where the
Registrar(s) are. As far as I can see there are really two options, and they
might not be mutually exclusive.
a) start a multicast M_DISCOVERY which will be propagated forward and can be
answered from caches.
b) listen f
