>>>>> On Thu, 18 Apr 2002 08:16:24 -0700,
>>>>> Toerless Eckert <[EMAIL PROTECTED]> said:
>> I've attached a revised version of the proposed text according to
>> discussions after the proposal, including very recent results.
>> I'll soon submit a new I-D with this change, but if you see something
>> missing in the attached text, please let me know.
>> Also, path MTU discovery for multicast has severe scalability
>> limitations and should thus be avoided.
> ... by default.
> Not sure if you want to spend rfc space on tis, but this would be the
> rationale i would give:
> ... Applications sending multicast traffic should explicitly enable
> path MTU discovery only when they understand that the benefit of
> possibly larger MTU usage outweights the possible impact of MTU
> discovery for active sources across the delivery tree(s).
> And here is an outlook you may want to add (or not):
> ... This default behavior is based on todays available MTU path discovery
> mechanism and may change in the future once better scalable mechanisms are
> sufficiently ubiquitously available.
I'm okay with the addition, but let me check, is the following your
intended text?
...A
potential example is a DNS server.
Also, path MTU discovery for multicast has severe scalability
limitations and should thus be avoided by default. Applications
sending multicast traffic should explicitly enable path MTU
discovery only when they understand that the benefit of possibly
larger MTU usage outweights the possible impact of MTU discovery
for active sources across the delivery tree(s). This default
behavior is based on todays available MTU path discovery mechanism
and may change in the future once better scalable mechanisms are
sufficiently ubiquitously available.
This specification defines a mechanism to avoid path MTU discovery by
sending at the minimum IPv6 MTU [RFC-2460]....
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
