Yes, of course. We can never change a standards track protocol. That would be wrong. :)
What I’m trying to understand is how bad a problem this is. > On Sep 19, 2019, at 04:56, Juliusz Chroboczek <[email protected]> wrote: > > >> >> This still doesn’t address the problem that the HNCP packet needs to be >> fragmented. Fragmented Multicast doesn’t scale well. > > HNCP doesn't fragment multicast, it only uses fragmentation for (link-local) > unicast. This is way less severe than what you incorrectly claim. > > At any rate, the right time to discuss that was 2015, not now. HNCP is > a standards track protocol, and there's nobody left who's willing and > competent to work on a new revision. > > -- Juliusz _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
