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]
