> On 30. jun. 2015, at 07.45, Suresh Krishnan <[email protected]> > wrote: > > Hi Michael, > > On 06/29/2015 06:35 PM, Michael Welzl wrote: >> Dear all, >> >> We just posted the draft below. Not knowing which other group would fit, >> we're sending it here. We're really transport people and at least I am >> newbie to this group... very curious to hear your thoughts: >> - completely idiotic? >> - exactly what the world has been waiting for? >> >> ... I guess it can only be one of the two above :-) If the chairs think >> that this makes sense to discuss in Prague, we'll be there, and I'd be happy >> to do a supershort presentation, but let us first hear what you think. It's >> a short and easy read, we promise that! :-) > > Since you are requesting an ICMPv6 codepoint, I think 6man would be a > better venue for this work if it progresses.
I thought about it before sending to intarea but I'm not sure: this is really not v6 "maintenance" - and this is really about ICMP in general, we only provided the spec for v6 up to now because that was faster for us to do (the draft says that future versions will include v4) > As for the draft itself, I have a few thoughts. > > * It is unclear how the plaintext message ripples up to the > administrator. Some clarity about this would be very useful. Can be added. No problem I think. > * What about DoS attacks? There is no rate-limiting? We can insert a recommendation to not send this message too often FWIW :-) but I think this is just as "dangerous" as ICMP Echo Request or whatever. How often you process these messages / how many of them you process on a middlebox is really your own decision, it's always safe to ignore or drop. > * Need to specify type>128 for IANA ACK > * A +1 for Joel's and Joe's comments ... but these were not convincing arguments at all I think. Honestly if someone would tell me to go away because the idea of sending ascii around in ICMP is just plain silly, that'd seem to me to be a better argument than those :-) Cheers, Michael _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
