On Sun, Mar 14, 2021 at 9:16 PM wrote:
> Dear DNSOP participants,
>
> Thanks very much for good comments for
> draft-ietf-dnsop-avoid-fragmentation.
>
> These are my proposal of Section 3.3. Default Maximum DNS/UDP payload
> size.
>
> I'm not sure what to do with "MAY, "SHOULD", or "MUST",
> so
On 19 Mar 2021, at 02:42, Viktor Dukhovni wrote:
>
> On Mon, Mar 15, 2021 at 05:38:40PM +, Jim Reid wrote:
>
>> Measuring the MTU to well-known locations on the Internet won’t be
>> appropriate for some use cases. For instance inside private nets that
>> aren’t connected to the Internet or f
Hi,
On Thu, Mar 18, 2021 at 10:43 PM Viktor Dukhovni wrote:
> On Mon, Mar 15, 2021 at 05:38:40PM +, Jim Reid wrote:
>
> > ...
> ...
> > This could get nasty with icky CPE
> > firmware: imagine every home router in (say) Comcast’s net doing PMTU
> > to the same root server.
>
> These would gen
On Mon, Mar 15, 2021 at 05:38:40PM +, Jim Reid wrote:
> > However, operators of DNS servers SHOULD measure their path MTU to
> > well-known locations on the Internet, such as [a-m].root-servers.net
> > or [a-m].gtld-servers.net at setting up the servers.
>
> I think it would be better to repl
> On 15 Mar 2021, at 04:16, fujiw...@jprs.co.jp wrote:
>
> Dear DNSOP participants,
>
> Thanks very much for good comments for draft-ietf-dnsop-avoid-fragmentation.
>
> These are my proposal of Section 3.3. Default Maximum DNS/UDP payload size.
>
> I'm not sure what to do with "MAY, "SHOULD"
Dear DNSOP participants,
Thanks very much for good comments for draft-ietf-dnsop-avoid-fragmentation.
These are my proposal of Section 3.3. Default Maximum DNS/UDP payload size.
I'm not sure what to do with "MAY, "SHOULD", or "MUST",
so please give us your opinion.
If it is acceptable, I will
