Daniele,

Perhaps this will help:

By design, a node that is about to "discover" a domain that it wishes to join does not care about existing routing that may (or may not) exist in parallel with it. The only requirement on the node (at least for the basic ANIMA specification) is that it have a link-local address, and an appropriate certificate that will permit it to join the domain. The link-local addressing permits it to "discover" a node that is already a member of the domain, and the certificate allows it to request membership in the domain. Any subsequent routing within the domain can then be established (securely), based on certification and addressing that are assigned to the node as it joins.

  Bill Atwood

On 2026-07-15 4:59 p.m., Brian E Carpenter wrote:
Attention This email originates from outside the concordia.ca domain. // Ce courriel provient de l'extérieur du domaine de concordia.ca

On 16-Jul-26 07:48, Michael Richardson wrote:
Daniele Ceccarelli via Datatracker <[email protected]> wrote:
     > I have some minor concerns about this document that I think should be      > resolved before it is submitted to the IESG.  The draft explains WHAT      > can be discovered (registrars, proxies, pledges) and HOW variations      > are signaled, but I found it hard to understand HOW this fits into a      > normal routed network with VLANs, routers, and possibly no IPv6. The
     > core ideas seem reasonable, but more plain-language deployment
     > guidance would help non-experts and operators.

GRASP runs over the RFC8994 ACP overlay, which is explicitely IPv6.

To be clear, there's nothing in GRASP that couldn't be hammered into IPv4, but it was designed for an IPv6-only ACP environment. It is blind to VLANs I think, and it uses link-local IPv6 heavily, but is perfectly happy with routeable IPv6
addresses. RFC8993 is a good reference if you want an overview.

Even if what's underneath is DECnet, SNA or IPX...

Or X.25? (I hope nobody ever does that.)


The overlay usually runs between routers using IPv6-LL, which are always available.
However, explicit configuration could overlay over NAT44/NAPT.

RFC8993 is a good reference if you want an overview.

     Brian


--
Michael Richardson <[email protected]>, Sandelman Software Works
  -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*




_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]

_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--
Dr. J.W. Atwood, Eng. (retired)
Distinguished Professor Emeritus
Department of Computer Science
   and Software Engineering
Concordia University ER 1234      email:[email protected]
1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8

_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to