Re: Is Fragmentation at IP layer even needed ?

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 15 February 2016 18:43 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A17A1ACD94 for <ietf@ietfa.amsl.com>; Mon, 15 Feb 2016 10:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id und0BnQMz6ND for <ietf@ietfa.amsl.com>; Mon, 15 Feb 2016 10:43:25 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F9931ACD84 for <ietf@ietf.org>; Mon, 15 Feb 2016 10:43:25 -0800 (PST)
Received: by mail-pa0-x229.google.com with SMTP id ho8so90544209pac.2 for <ietf@ietf.org>; Mon, 15 Feb 2016 10:43:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=ze0rzbfRUZgw2hBF2p8lxC81LMy5cTf72WLABDJMNso=; b=VDX0lP/QQHQFKblrCDNc8H/7cAmKbtg4bjMY93ELyFb/LJuYtC3LHagWFH+23xv1hb bFKRX/ZNOKZo1TU0txDl9glCLfBT/bspC7GoDD1CESVGImIOnLKigeZAbIUlojvkJpq8 RD0aiAJ9elyzU1D5oDdk8eu4Z9cAetb5jWNMVczLIJtjVSXleij1CHqfV705qJmJqW7N aGTUCu71RkD0Y0GSoeLnDX6sWCvHP531gpO3c3IszQ58JUW7zO3E7tdJ1fybgzMXvFzZ KsO209kg9x6JG0GxhFMjLpyzHgqoee38KKW/B7WUgDwKM32K9D1xd5BU9O71h9CBWRUv XbJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=ze0rzbfRUZgw2hBF2p8lxC81LMy5cTf72WLABDJMNso=; b=m0tdxmee+OLDkgt/JA5cnGpDaFwRxj+cYPR267hgdBBATgdPgY7cNOCwv9yKr5Ydk7 zZ7AbWLXBUIa6M4NNE+/I5A0lcqbdBpTWdHsYUkZL0wJh6cdOTRumBItLahKLxN80ffu X1bR/nXmC2tZtB2hEwwOEfoQVzADGbbEgOQKPlzAJ+xn6SLtO8N82l7eYV72YwoG9M4p NO4DulnmeQ9CTeZDV9owKzy+FDMuU0jkoCFBZ+G5KwPPcd9fb6+VfxUzeeJZkP0fJuoe PiReEA0HbLC/rzv6sTTCL07PO0BB0BbaqSx+44LXdeOIMTlATFMzigRTXoca+R6vlL2s UgXQ==
X-Gm-Message-State: AG10YORt6o0+8DbkeApsF+iRWnVhLPE0EsWHBFtJib+UFjLgEHP7R6R8n+GOCLKu0tuOmQ==
X-Received: by 10.67.4.225 with SMTP id ch1mr24823695pad.77.1455561804847; Mon, 15 Feb 2016 10:43:24 -0800 (PST)
Received: from ?IPv6:2406:e007:6fe2:1:28cc:dc4c:9703:6781? ([2406:e007:6fe2:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id z5sm40276576pas.29.2016.02.15.10.43.22 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 15 Feb 2016 10:43:23 -0800 (PST)
Subject: Re: Is Fragmentation at IP layer even needed ?
To: ietf@ietf.org
References: <CAOJ6w=EvzE3dM4Y2mFFR=9YyPBdmFu_jkF4-42LjkdbRd3yz_w@mail.gmail.com> <BLUPR05MB1985F5F2BB3118362C67B921AED50@BLUPR05MB1985.namprd05.prod.outlook.com> <20160208200943.A615941B5B96@rock.dv.isc.org> <CAMm+LwgLoYpQ1TNOTOuJzh+cu+GyRBf9=y_K7K35boQ9WcZKjA@mail.gmail.com> <56B92A96.9050200@si6networks.com> <CAMm+LwifTXvVd1mPZOfcOOR03Fnj-82H9aDVS01=wGezePtnXw@mail.gmail.com> <56BA4BC7.1010002@isi.edu> <CAMm+Lwi-n=be4AWGibs+Zq9egYw5pSDmPGb-4P0LDEcX1E6osA@mail.gmail.com> <56BA68CE.7090304@isi.edu> <CAMm+LwiM2sFUeejgJZe650UQbVHrh7EHrEF2omvPrZJPodgJLA@mail.gmail.com> <56BA739D.7060309@isi.edu> <CAMm+Lwij1dOkK0b2ZnJiPMtba=wc823WgYjqw0iwAApa3KBYcg@mail.gmail.com> <56BA95C7.8060109@isi.edu> <56BAD6CC.2030209@necom830.hpcl.titech.ac.jp> <56BBAAF7.6020903@isi.edu> <56BC9516.6050305@necom830.hpcl.titech.ac.jp> <56BCCBB4.4050909@isi.edu> <56BCF514.6040401@necom830.hpcl.titech.ac.jp> <56BE23F0.4090403@isi.edu> <56BFD7B3.9080505@necom830.hpcl.titech.ac.jp> <56C14D50.4040802@isi.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56C21C4B.50304@gmail.com>
Date: Tue, 16 Feb 2016 07:43:23 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56C14D50.4040802@isi.edu>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Lg_2JKhq18UQMxvbt-qzwuZ9k8M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2016 18:43:26 -0000

On 15/02/2016 17:00, Joe Touch wrote:
> 
> 
> On 2/13/2016 5:26 PM, Masataka Ohta wrote:
>> QoS (not CoS but real QoS) capable routers must inspect L4.
> 
> That must be why there are QoS indicators in the L4 header.
> 
> Oh, wait - those are in L3 (RFC2474 and its successors).
> 
> Yes, layering is a difficult concept.

That's also why the IPv6 flow label is recommended to be a hash
of layer 3 and layer 4 information (RFC 6437, yes, it took us some
years to get that ~right).

   Brian