Re: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt

Glen Turner <gdt@gdt.id.au> Mon, 24 June 2013 00:53 UTC

Return-Path: <gdt@gdt.id.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4183221F9FA5 for <ipv6@ietfa.amsl.com>; Sun, 23 Jun 2013 17:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001]
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 BuT0IPkjMYM3 for <ipv6@ietfa.amsl.com>; Sun, 23 Jun 2013 17:53:30 -0700 (PDT)
Received: from neotokyo.gdt.id.au (neotokyo.adelaide.aarnet.edu.au [202.158.193.52]) by ietfa.amsl.com (Postfix) with ESMTP id 0E79D21F9CD9 for <ipv6@ietf.org>; Sun, 23 Jun 2013 17:53:29 -0700 (PDT)
Received: from [192.168.255.5] (eth6445.sa.adsl.internode.on.net [150.101.30.44]) by neotokyo.gdt.id.au (Postfix) with ESMTPSA id 0E18932A0C82; Mon, 24 Jun 2013 10:23:15 +0930 (CST)
Subject: Re: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_58D9B586-CA7E-48D5-BFFF-24A536B6BA46"
From: Glen Turner <gdt@gdt.id.au>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B9237F3@xmb-rcd-x09.cisco.com>
Date: Mon, 24 Jun 2013 10:23:12 +0930
Message-Id: <D9259C6F-303B-45CD-AB08-CE8659FF163A@gdt.id.au>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F85151@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C56E60.5040009@fud.no> <8C48B86A895913448548E6D15DA7553B9237F3@xmb-rcd-x09.cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1283)
X-Virus-Scanned: clamav-milter 0.97.8 at neotokyo
X-Virus-Status: Clean
Cc: "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 00:53:36 -0000

On 24/06/2013, at 8:41 AM, Fred Baker (fred) wrote:
> 
> I'm in a similar case with respect to protocols above IPv6 (OSPF and NFS/UDP come quickly to mind) that depend on fragmentation to deal with the issue. I think the Robustness Principle tells us that such applications SHOULD figure out how to live with PMTU, but it also tells us that we can't deprecate fragmentation unless all known instances that depend on it have defined practical work-arounds. I suspect that this would imply the re-creation of the fragmentation feature in an intermediate protocol, which seems like a lot of work with little real gain.

Calculating the PMTU for UDP protocols is left to applications, the sockets API doesn't do this under the hood like it does for TCP. As a result most UDP-using applications don't probe the PMTU. This is the case for both IPv4 and IPv6, although the effect with IPv6 is lost connectivity rather than in-flight fragmentation.

Some small changes to the socket API for unconnected protocols would make life substantially better for RADIUS implementors (and, I imagine, DNS). We're more than happy to repeatedly pass the same application protocol data unit into the socket whilst the socket probes the path MTU.

-glen