Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

83% Positive

Analyzed from 359 words in the discussion.

Trending Topics

#packet#gateway#host#address#neighbour#discovery#solution#own#reading#ripe

Discussion (7 Comments)Read Original on HackerNews

mort96•about 1 hour ago
Wait I don't get this.

If I understand correctly, traditional IPv6 flow is:

    * A host configures its own IP address via SLAAC
    * The host sends a packet to its gateway with some destination address
    * The gateway forwards the packet to the Internet
    * Eventually, a response packet arrives to the gateway
    * At this point, the gateway does neighbour discovery to try to figure out how to send the packet to the host
    * The gateway might drop the packet or delay forwarding it until neighbour discovery completes
Why couldn't we change the flow to:

    * A host configures its own IP address via SLAAC
    * The host sends a packet to its gateway with some destination address
    * The gateway forward the packet, and at the same time starts neighbour discovery because almost all computers which send outgoing packets will eventually receive some incoming packet
    * When the response packet arrives, neighbour discovery is likely already done, or if not it got a good head start
Isn't this the obvious solution which wouldn't require changes to hosts or new protocols, just a small tweak to the router? Usually, when there's a seemingly obvious simple solution to a real problem and that solution hasn't been implemented by any of the clever people working in networking standards, there's a good reason and the solution isn't as simple as it seems. So what am I missing?
convolvatron•39 minutes ago
Im mildly confused as well, there is an even more immediate shortcut that I've certainly implemented before. in arp its not unusual to to just create a mac->ip binding from the source information in the ethernet header. where this potentially breaks down if we start looking at issues of trust. but its already the case in ND that we trust the endpoint to have executed the state machine to search for duplicates. so what's preventing us from doing the same thing here? maybe just layering concerns?
basilikum•17 minutes ago
Interesting topic.

Started reading, the text is dreadfully lengthy, hard to stay concentrate on due to all the filler and mindlessly arranged words that obscure the actual content, notice AI tell signs.

Stop reading, paste into Pangram, mostly AI,

scroll down on the text, find this:

> Note: The author used AI tools to assist with drafting and language. The technical work, analysis and conclusions are the author’s own. For more information about our policy on AI-generated content, see our Contributing to RIPE Labs page.

Do better RIPE. I assumed RIPE had some standard. If you decide to not have any standards, at the very least put the AI disclaimer at the top so I don't waste my time on slop. It's disrespectful.

Does anyone have an article about NDP and GRAND that is not slop and worth sharing and reading?