You wrote; "we can, if we wish, continue to standardize one protocol, watch
as the world deploys a different one, and still pretent that our effort was
worthwhile. however, this would fit the technical definition of "insanity",
and i urge that we avoid this course of action."
The IETF has been doi
On September 22, 2017 9:58:42 AM EDT, Andrew Sullivan
wrote:
>On Thu, Sep 21, 2017 at 07:31:29PM -0700, Paul Vixie wrote:
>
>[…]
>
>> we need a kernel option for various open source operating systems
>which
>> causes all UDP to be fragmented at 512 octets of payload.
>
>If working on a protocol
On Thu, Sep 21, 2017 at 07:31:29PM -0700, Paul Vixie wrote:
> we can, if we wish, continue to standardize one protocol, watch as the world
> deploys a different one, and still pretent that our effort was worthwhile.
> however, this would fit the technical definition of "insanity", and i urge
> that
In message <20170922042453.08ea187a1...@rock.dv.isc.org>, Mark Andrews writes:
> I've tested enough version negotiation paths. See https://ednscomp.isc.org/
> The entries with "badversion" show a failed EDNS version negotiation.
> The entire Alexa top 1M is scanned once a month.
I've added a li
In message <59c48658.9000...@redbarn.org>, Paul Vixie writes:
> Mark Andrews wrote:
> ...
> > Just padding UDP responses to EDNS buffer size should be enough to
> > force fragmentation. If you advertise a 4096 buffer you should be
> > able to accept such a response.
>
> i don't want to waste the
Mark Andrews wrote:
...
Just padding UDP responses to EDNS buffer size should be enough to
force fragmentation. If you advertise a 4096 buffer you should be
able to accept such a response.
i don't want to waste the octets. a lot of links are still mobile.
forcing source fragmentation for pa
In message <59c47601.5030...@redbarn.org>, Paul Vixie writes:
> Davey Song() wrote:
> > Hi Paul,
> >
> > I know you suggest expose the problem and let the trouble maker
> > feeling the pain themselves. But return to the specific issue, from
> > APNIC's measurement the ASes in the path are dropping
Davey Song(宋林健) wrote:
Hi Paul,
I know you suggest expose the problem and let the trouble maker
feeling the pain themselves. But return to the specific issue, from
APNIC's measurement the ASes in the path are dropping the fragments,
rather than end ASes. From these ASes' view , it's your pain
Hi Paul,
I know you suggest expose the problem and let the trouble maker feeling the
pain themselves. But return to the specific issue, from APNIC's measurement the
ASes in the path are dropping the fragments, rather than end ASes. From these
ASes' view , it's your pain not theirs.
In anothe
