I suspect that for most GRASP purposes, even if there is a layer 2
network between the parties, we are not much worried about how LAG
handles GRASP packets? If we care about that, then the source port
should be randomized between flows, and stable for sequences of related
messages.
Yours,
Joel
On 4/27/2020 6:14 PM, Michael Richardson wrote:
Brian E Carpenter <[email protected]> wrote:
> No, that normally gets resolved when they actually start editing, but
> yes of course it's on my checklist.
> I'm quite sure the early aassignments were announced on the list, but
> when I forget what values were pre-assigned I just go and look at my
> code:
I thought that early allocations were supposed to go into the document so
they don't get assigned twice by mistake.
> ALL_GRASP_NEIGHBORS_6 = ipaddress.IPv6Address('ff02::13') # LL
multicast
> ALL_GRASP_NEIGHBORS_4 = ipaddress.IPv4Address('224.0.0.119') # LL
multicast
> GRASP_LISTEN_PORT = 7017 # IANA port number
Thank you.
Is there any reason why the source port (for DULL, and normal) can't be port
7017 as well?
It clearly could be any port...
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima
