Re: [v6ops] proposed TCP MSS text for rfc6204bis

Rémi Després <despres.remi@laposte.net> Tue, 22 May 2012 15:43 UTC

Return-Path: <despres.remi@laposte.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E05FC21F85F6 for <v6ops@ietfa.amsl.com>; Tue, 22 May 2012 08:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.034
X-Spam-Level:
X-Spam-Status: No, score=-1.034 tagged_above=-999 required=5 tests=[AWL=0.315, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnP9laBcdYiA for <v6ops@ietfa.amsl.com>; Tue, 22 May 2012 08:43:06 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.19]) by ietfa.amsl.com (Postfix) with ESMTP id 3E86321F85EF for <v6ops@ietf.org>; Tue, 22 May 2012 08:42:58 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2302.sfr.fr (SMTP Server) with ESMTP id 188017000181; Tue, 22 May 2012 17:42:57 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2302.sfr.fr (SMTP Server) with ESMTP id 2B0507000110; Tue, 22 May 2012 17:42:56 +0200 (CEST)
X-SFR-UUID: 20120522154256176.2B0507000110@msfrf2302.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="windows-1252"
From: Rémi Després <despres.remi@laposte.net>
In-Reply-To: <96B542C8-F19D-470D-B648-154946D791A6@kumari.net>
Date: Tue, 22 May 2012 17:42:55 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F4D41D8-78ED-4EBB-883C-9B4462EBE14A@laposte.net>
References: <4FB74456.2090009@gmail.com> <20120519080006.GZ84425@Space.Net> <4FB775A3.1030900@gmail.com> <20120519.141906.74656347.sthaug@nethelp.no> <4FB7A7CC.6060503@gmail.com> <m27gw7eub0.wl%randy@psg.com> <4FB89733.2080106@gmail.com> <20120520140421.9E5A520C611B@drugs.dv.isc.org> <96B542C8-F19D-470D-B648-154946D791A6@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1084)
Cc: v6ops@ietf.org
Subject: Re: [v6ops] proposed TCP MSS text for rfc6204bis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 15:43:08 -0000

Hi Warren,

Le 2012-05-21 à 16:49, Warren Kumari a écrit :

> [ Top posting / meta questions ]
> 
> So, both my memory and my google-foo are failing me…
> 
> Can anyone remember *why* the v6 in MTU is 1280 (and please don't say "Because the RFC says so!"…)

In the excellent French book in which I learned IPv6 in 2003 (livre.g6.asso.fr/index.php/Format_du_paquet_IPv6), here is what I learned:
"Choice of 1280 as minimum MTU is to permit IPv6 tunneling. 1500 octets is the generally admitted link MTU, that imposed by Ethernet." 

As this permits multiple tunneling layers without fragmentation on the most typical links, and limits to a moderate ratio waste of bandwidth on 1500-octet remote links, this is IMHO a valuable choice.

RD



> I have some niggling voice in the back of my head making 3GPP noises, but…
> 
> W
> 
> On May 20, 2012, at 10:04 AM, Mark Andrews wrote:
> 
>> 
>> In message <4FB89733.2080106@gmail.com>, Brian E Carpenter writes:
>>> On 2012-05-19 22:26, Randy Bush wrote:
>>>>> If you want to send packets of arbitrary size, in any environment
>>>>> where PMTUD is impossible or fails, won't you need to always include
>>>>> a fragmentation header in every packet greater than 1280?
>>>> 
>>>> see discussion of jumbo frames, commonly 4k or 9k, between consenting
>>>> adults on known links
>>> 
>>> Yes indeed, but that isn't the general case. Across the open Internet,
>>> I think we have the situation I described.
>>> 
>>> On 2012-05-19 21:16, Gert Doering wrote:
>>> 
>>>>>> UDP packets larger than 1280 bytes
>>>>>> Don't do that!
>>>> 
>>>> Tell that to the DNS people.  They seem to really like not-using-TCP.
>>> 
>>> Yes, but I understand that DNSSEC more or less dooms that plan anyway.
>>> 
>>> However, I thinks it's true that the only fail-safe solution is to
>>> include a frag header if you need to send UDP >1280.
>>> 
>>>  Brian
>> 
>> For DNS we just fragment at 1280 using IPV6_USE_MIN_MTU.   We were
>> thinking about this back in 1998 (draft-ietf-ipngwg-bsd-frag-00.txt)
>> which was rolled into the advanced socket api.  It took a few more
>> years than I would have liked to become RFC and for implementations
>> to be available.  EDNS was already being developed back then and
>> it was obvious that PMTUD wouldn't work for large nameservers even
>> if they got the ICMPv6 PTBs.
>> 
>> For DNS there is little to be gained by trying to send any bigger
>> packets.
>> 
>> YMMV for other UDP based protocols.
>> 
>> Mark
>> 
>>>   Brian
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>> -- 
>> Mark Andrews, ISC
>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>> 
> 
> -- 
> With Feudalism, it's your Count that votes.
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops