Re: Path MTU Hop-by-Hop Option
Tom Herbert <tom@herbertland.com> Wed, 17 October 2018 15:33 UTC
Return-Path: <tom@herbertland.com>
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 7C029130DE8 for <ipv6@ietfa.amsl.com>; Wed, 17 Oct 2018 08:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 kOWvv54JEjON for <ipv6@ietfa.amsl.com>; Wed, 17 Oct 2018 08:33:56 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 8288A130DE4 for <ipv6@ietf.org>; Wed, 17 Oct 2018 08:33:56 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id j46-v6so30504795qtc.9 for <ipv6@ietf.org>; Wed, 17 Oct 2018 08:33:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3CNww5POyzhPAMLi3vd4orys5Fyhmu1E2ffmbLaOR6Q=; b=N/XQcKdCmERsnmMLMIC2BKtWBIjzSM8hsPdOOA+hs0+G0X45Xl+THpKSUTzTI+2O66 py+6jI+X9KgZ6/hwpfeaDebz5CM2SMIZIIA8xqm72LoMyX0gnC8fNhrh2lo8fm7d9bqW +abDdlDM19Fwicu9sDdYrM9h7OW4j+SYJGEkIbGmo12FFFpU6gizQBBxZJTmNBoy5Gsw x7tRSQzW7Zy1qGJQ+YEg3zaTYPkL54ieHJQo4SrB1ZpaXns7p/pBc6fluzuRY6Zk3e9Q IiL4f+7/8Fb8lRP2REMID/qFp/LjzP3M5EhZ347QuLFUp0/gCSnhSyb3t6Br2jvcWhqp h3eA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3CNww5POyzhPAMLi3vd4orys5Fyhmu1E2ffmbLaOR6Q=; b=QFkhiJQzhX35Me2Pu7TGPHBI9M8o7e4L6dr3braZysIVb/8WIC+7zRhRQwQKxTuoH6 sH51yF9HwfApuZ7+LWh6qptsiPUi/tbif7V8Wdno1yrrTN4xrqpRY/CDLx5xVDVsycBG BJn5fNJOAT0TEtNYMWuTDoGdTACatpM9m62uDs42Og2nlThsTaEcl8/OMgnooKXHmiyA nqBbeIkTkOiTPxd81VMT+Y7FRSchT4to0oyWMj9YcOn8u7wbo4KHkTzuO0xFQSKA3Joj +8Nwz8nTNtGnI8fmmsLI9NKf7wrFUSX206k138XnIsGcJluQeqoW3ULGrQ2TVGyco7u2 kuPA==
X-Gm-Message-State: ABuFfoja2vqvY31U0sQ4SfpY0Jj7+u0ixruhdtP76I7UrOrRIIMiuodd TiHYVmJFI9eGiKVY2Ge+ByDU91dtD8OAgEzX3ggUKuI9
X-Google-Smtp-Source: ACcGV63IaXuStR5+1fbhyhkams1qaPqGDDzldsdrWdpHs0KgKRB2ZgbTQiNHd2P/F4rGKOsBPOrocHU5X+eVaBX0crU=
X-Received: by 2002:a0c:ec8b:: with SMTP id u11mr18843942qvo.168.1539790435503; Wed, 17 Oct 2018 08:33:55 -0700 (PDT)
MIME-Version: 1.0
References: <153972960647.9465.12295361632444928551.idtracker@ietfa.amsl.com> <E97952C5-3E3C-4EC1-B414-BDA8717FD7DF@gmail.com> <24F21185-0E76-449D-B9C7-729DD8CD30EE@tzi.org>
In-Reply-To: <24F21185-0E76-449D-B9C7-729DD8CD30EE@tzi.org>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 17 Oct 2018 08:33:43 -0700
Message-ID: <CALx6S353b4bRSxka2ZpGiLRCOd1o9_GQbU7+anYg4YXbV-Nvmw@mail.gmail.com>
Subject: Re: Path MTU Hop-by-Hop Option
To: Carsten Bormann <cabo@tzi.org>
Cc: Bob Hinden <bob.hinden@gmail.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IPv6 List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eff06205786e654f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/dJnp8Twt3avPF6x7V95FXZ7k0uM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 17 Oct 2018 15:33:58 -0000
On Tue, Oct 16, 2018, 9:50 PM Carsten Bormann <cabo@tzi.org> wrote: > On Oct 17, 2018, at 00:55, Bob Hinden <bob.hinden@gmail.com> wrote: > > > > This document specifies a new Hop-by-Hop IPv6 option that is used to > > record the minimum Path MTU > > A while ago I proposed something similar to collect information about > adaptation layer fragmentation MTUs (information about which is truly not > available in any other way): > > https://tools.ietf.org/html/draft-bormann-intarea-alfi-04 > > (I also only looked at the Internet layer here — leaving it as an exercise > to put in transport/application protocol support.) > > After mulling an initial version of the proposal, there was pretty much > consensus that hop-by-hop options were not really available on the > Internet. So I put in an alternative way to collect the information, see > above if you are interested. Then at some point SPUD came along and I was > hoping that would lead to a framework within in which this information > could be better handled. > Carsten, > SPUD would put this sort of information in a UDP payload. This would then have intermediate nodes modifying payloads to record the MTU. That's fundamentally incorrect since port numbers, which would be used to identify SPUD, only have meaning at the end points. If intermediate nodes are to set arbitrary information in packets, then Hop-by-Hop options are really the only correct and generic way to do that. > Maybe it’s time to pull the old draft out again. The hop-by-hop option > problem of course hasn’t gone away. > As the draft states, RFC8200 relaxed the requirements of HBH options so that intermediate nodes ignore them instead of dropping. That is reasonable and easy to implement. There are still going to be some drops so implementations will need to fall back when they don't work for a flow (same thing would be true SPUD since UDP isn't guaranteed to work across the whole Internet). Tom > Grüße, Carsten > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
- Path MTU Hop-by-Hop Option Bob Hinden
- Re: Path MTU Hop-by-Hop Option Tom Herbert
- Re: Path MTU Hop-by-Hop Option Fred Baker
- RE: Path MTU Hop-by-Hop Option Lubashev, Igor
- Re: Path MTU Hop-by-Hop Option Carsten Bormann
- Re: Path MTU Hop-by-Hop Option Mikael Abrahamsson
- Re: Path MTU Hop-by-Hop Option Gorry Fairhurst
- Re: Path MTU Hop-by-Hop Option Havard Eidnes
- Re: Path MTU Hop-by-Hop Option Gorry Fairhurst
- Re: Path MTU Hop-by-Hop Option Jen Linkova
- Re: Path MTU Hop-by-Hop Option Mikael Abrahamsson
- Re: Path MTU Hop-by-Hop Option Ole Troan
- Re: Path MTU Hop-by-Hop Option Jen Linkova
- Re: Path MTU Hop-by-Hop Option Nick Hilliard
- Re: Path MTU Hop-by-Hop Option Nick Hilliard
- Re: Path MTU Hop-by-Hop Option Rajiv Asati (rajiva)
- Re: Path MTU Hop-by-Hop Option Michael Richardson
- Re: Path MTU Hop-by-Hop Option Mark Andrews
- RE: Path MTU Hop-by-Hop Option Templin (US), Fred L
- Re: Path MTU Hop-by-Hop Option - Tunnels? Joel M. Halpern
- Re: Path MTU Hop-by-Hop Option - Tunnels? Gorry Fairhurst
- Re: Path MTU Hop-by-Hop Option Tom Herbert
- Re: Path MTU Hop-by-Hop Option Gorry Fairhurst
- Re: Path MTU Hop-by-Hop Option Tom Herbert
- Re: Path MTU Hop-by-Hop Option Mikael Abrahamsson
- Re: Path MTU Hop-by-Hop Option George Michaelson
- Re: Path MTU Hop-by-Hop Option Bob Hinden
- Re: Path MTU Hop-by-Hop Option Bob Hinden
- Re: Path MTU Hop-by-Hop Option Bob Hinden
- Re: Path MTU Hop-by-Hop Option Tom Herbert
- Re: Path MTU Hop-by-Hop Option Christian Huitema
- Re: Path MTU Hop-by-Hop Option Nick Hilliard
- Re: Path MTU Hop-by-Hop Option Gorry Fairhurst
- operational stoppers to > 1500 MTU deployment in … Mikael Abrahamsson
- Re: operational stoppers to > 1500 MTU deployment… George Michaelson
- Re: operational stoppers to > 1500 MTU deployment… Mikael Abrahamsson
- Re: Path MTU Hop-by-Hop Option Nick Hilliard
- Re: operational stoppers to > 1500 MTU deployment… Christopher Morrow
- Re: operational stoppers to > 1500 MTU deployment… Philip Homburg
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- Re: operational stoppers to > 1500 MTU deployment… Nick Hilliard
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- RE: operational stoppers to > 1500 MTU deployment… Mikael Abrahamsson
- Re: operational stoppers to > 1500 MTU deployment… Mikael Abrahamsson
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- Re: operational stoppers to > 1500 MTU deployment… Tom Herbert
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- RE: operational stoppers to > 1500 MTU deployment… Mikael Abrahamsson
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- RE: operational stoppers to > 1500 MTU deployment… Mikael Abrahamsson
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- Re: operational stoppers to > 1500 MTU deployment… 神明達哉
- Re: operational stoppers to > 1500 MTU deployment… Mikael Abrahamsson
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- Re: operational stoppers to > 1500 MTU deployment… Tom Herbert
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- Re: operational stoppers to > 1500 MTU deployment… Dale W. Carder
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- QUIC and DF [Re: Path MTU Hop-by-Hop Option] Brian E Carpenter
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- Re: QUIC and DF [Re: Path MTU Hop-by-Hop Option] Ole Troan
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- Re: Path MTU Hop-by-Hop Option Bob Hinden
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- RE: operational stoppers to > 1500 MTU deployment… Templin (US), Fred L
- Re: QUIC and DF [Re: Path MTU Hop-by-Hop Option] Brian E Carpenter
- RE: operational stoppers to > 1500 MTU deployment… Mikael Abrahamsson
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- Re: operational stoppers to > 1500 MTU deployment… Carsten Bormann
- Re: QUIC and DF [Re: Path MTU Hop-by-Hop Option] Christian Huitema
- Re: QUIC and DF [Re: Path MTU Hop-by-Hop Option] Christian Huitema
- Re: operational stoppers to > 1500 MTU deployment… Ole Troan
- Re: operational stoppers to > 1500 MTU deployment… Carsten Bormann
- Re: operational stoppers to > 1500 MTU deployment… Nick Hilliard
- Re: QUIC and DF [Re: Path MTU Hop-by-Hop Option] Nick Hilliard
- Re: operational stoppers to > 1500 MTU deployment… Tim Chown
- Re: Path MTU Hop-by-Hop Option Fernando Gont
- Re: Path MTU Hop-by-Hop Option G Fairhurst
- Re: Path MTU Hop-by-Hop Option Fernando Gont
- Re: Path MTU Hop-by-Hop Option Fernando Gont
- Re: Path MTU Hop-by-Hop Option Fernando Gont
- Re: Path MTU Hop-by-Hop Option Fernando Gont
- Re: Path MTU Hop-by-Hop Option Tom Herbert
- Re: Path MTU Hop-by-Hop Option Fernando Gont
- Re: Path MTU Hop-by-Hop Option Havard Eidnes
- Re: Path MTU Hop-by-Hop Option Tom Herbert
- Re: Path MTU Hop-by-Hop Option Fernando Gont
- Re: Path MTU Hop-by-Hop Option Tom Herbert
- Re: Path MTU Hop-by-Hop Option Brian E Carpenter