Re: draft-van-beijnum-multi-mtu-05.txt

otroan@employees.org Thu, 14 April 2016 13:05 UTC

Return-Path: <otroan@employees.org>
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 B685812D6B1 for <ipv6@ietfa.amsl.com>; Thu, 14 Apr 2016 06:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level:
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 lGjIrQHS5S5d for <ipv6@ietfa.amsl.com>; Thu, 14 Apr 2016 06:05:16 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) by ietfa.amsl.com (Postfix) with ESMTP id 56E8D12D641 for <ipv6@ietf.org>; Thu, 14 Apr 2016 06:05:16 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP; 14 Apr 2016 13:05:15 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 8BAD3D7882; Thu, 14 Apr 2016 06:05:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=TqEMMWu47/rblqi2wwVDoKygH9M=; b= ijtcO+63Fe3qnBGB5hMVY/fJyufGuyx9LWJXUf/uHqmHPIS5pWejG9LSqYGJI7aI vi0MkxdLyaqFpTDFBk6twKgB91vdMkVluFMhHaW+ZWkkd/YPE7bkXK/Ulwsa3VwZ 0iY0VlGaAdmvLAAH9wPTPsH3LsExUeaWuuEcspndHlc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=nJnDQZo4yVkz4BlaUb5LVYakoP ganrhJ68Y504uHz5zdcWqgIzioqWBuV9IKWhN237E/MPy8aUSQeVXWUO0O1/0+Mu ihgO37RWOeUK3Mv2QZuYKy6LBO6Bjgo48Lwb/dxh8FKJ5nmeDzuBx6KmRTOvfJwO No3Te/Ab9cHDLQypQ=
Received: from h.hanazo.no (unknown [173.38.220.43]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 235F1D7886; Thu, 14 Apr 2016 06:05:14 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by h.hanazo.no (Postfix) with ESMTP id C38E214620A0; Thu, 14 Apr 2016 15:05:12 +0200 (CEST)
Subject: Re: draft-van-beijnum-multi-mtu-05.txt
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_AC63ADB5-F4D0-4458-972F-AFA7F3E4CED2"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <20160414124807.GP518778@eidolon>
Date: Thu, 14 Apr 2016 15:05:11 +0200
Message-Id: <A4C36230-C4E4-432A-A427-81EA6627D7D5@employees.org>
References: <20160406151831.GZ518778@eidolon> <570569C2.4030601@acm.org> <20160406212048.GB518778@eidolon> <20160406220411.GC518778@eidolon> <E27329D1-400E-4470-8277-64A664508854@employees.org> <20160414122245.GN518778@eidolon> <07555AE0-8B99-464D-8F22-1663BF6579A7@employees.org> <20160414124807.GP518778@eidolon>
To: David Lamparter <equinox@diac24.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Ppr1y5cWILTBzewcR3X5GPoWbh0>
Cc: Erik Nordmark <nordmark@acm.org>, Iljitsch van Beijnum <iljitsch@muada.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 14 Apr 2016 13:05:17 -0000

David,

>> why couldn't it be done as end-to-end MTU?
>> 
>> the directly connected mechanism would be just to give a hint that
>> there might be nodes here capable of a higher MTU. then do normal MTU
>> probing / detection.
>> 
>> what would be gain be to have a specific protocol to probe directly
>> connected neighbors?
> 
> It can:
> - work (pro-)actively and independent of higher-layer protocols,
>  establishing MTU once

to a large extent we have failed at doing MTU discovery at the network layer.
too hard, couldn't do it, let's make it someone else's problem. ;-)
transport or application that is.

> - contain the different logic to understand that the router's MTU is the
>  upper cap for all destinations behind that router
> - contain the different probing parameters (being more aggressive) that
>  are appropriate for a local network
> - optionally carry extra information to reuse probing results across
>  different addresses that a host has on a segment
> 
> I suppose this can be achieved by using a specialized version of 4821 on
> the link... something like this:
> 
> - host does NS as usual, or catches unsolicited NA
> - NA contains new "MTU discovery" option with contents:
>  - indication of capability of first-hop MTU discovery
>  - known maximum MRU of NA's sender (i.e. upper limit)
>  - link-local address(?) + TCP port number(?) for PLMTUD probing
> - host establishes one or more TCP sessions to that port with the
>  express and only purpose of probing MTU
>  (may as well do it on an existing TCP session if one exists)
> - PLMTUD switches into some "first-hop" special mode (lower timers,
>  parallel operation, different values) to establish and store the value
>  with proper semantics (router case)
> 
> Is that what you have in mind?

I was thinking of something much simpler.
the NS/NA MTU option triggers the stack (transport / application) to use packets up to that MTU.
the transport or application has to do normal PLMTUD.

think of it as if you had a p2p link to the neighbor and that the interface MTU was set to whatever you received in the MTU option from that neighbour.

an on-link router already advertises an MTU in an RA. I'm not sure if it would make sense if it advertised per neighbor MTU options, and how those should be interpreted.

cheers,
Ole