Brian, did I get this right? 4.1.1. Proxy Grasp announcements
A proxy uses the GRASP M_FLOOD mechanism to announce itself. The
pledge SHOULD listen for messages of these form. This announcement
can be within the same message as the ACP announcement detailed in
[I-D.ietf-anima-autonomic-control-plane]. The M_FLOOD is formatted
as follows:
[M_FLOOD, 12340815, h'fe80::1', 180000,
["AN_Proxy", 4, 1, ""],
[O_IPv6_LOCATOR,
h'fe80::1', 'TCP', 4443]]
Figure 6b: Proxy Discovery
The formal CDDL definition is:
flood-message = [M_FLOOD, session-id, initiator, ttl,
+[objective, (locator-option / [])]]
objective = ["AN_Proxy", objective-flags, loop-count,
objective-value]
ttl = 180000 ; 180,000 ms (3 minutes)
initiator = ACP address to contact Registrar
objective-flags = sync-only ; as in GRASP spec
sync-only = 4 ; M_FLOOD only requires synchronization
loop-count = 1 ; one hop only
objective-value = '' ; none
locator = [ O_IPv6_LOCATOR, ipv6-address,
transport-proto, port-number ]
ipv6-address = the v6 LL of the proxy
transport-proto = 'TCP'
port-number = selected by proxy
Figure 6c: AN_Proxy CDDL
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
