IETF Logo Mail Archive

Re: Non-Last Small IPv6 Fragments

Fred Baker <fredbaker.ietf@gmail.com> Wed, 16 January 2019 17:20 UTC

Return-Path: <fredbaker.ietf@gmail.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 D035C124BE5 for <ipv6@ietfa.amsl.com>; Wed, 16 Jan 2019 09:20:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 z0n-kg_YKhxz for <ipv6@ietfa.amsl.com>; Wed, 16 Jan 2019 09:20:27 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 40437124BAA for <ipv6@ietf.org>; Wed, 16 Jan 2019 09:20:27 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id t13so3090772pgr.11 for <ipv6@ietf.org>; Wed, 16 Jan 2019 09:20:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=UrRDbhlFooJYlcCmYYOsaNNisIb+qcGGT1wJ2uSvw8M=; b=u/0zHzg4YyUSbGcxeJOAYDQelBzweS3TDMlMN47LF4Z37eq7aqcnVeAhT0rjt5X5DA HImdiwwVBcRoNZ52O1h1a2tU665ssqEHuAeBCee3tat9e1TBu8wL/UJsePxInUPPjdrG Mh7i5pi8ge26RdpOYRTK21+Y+OjO5ny5NLI5MtItG6yGOPuSXEnDnYanlqU02Cs4JSuD wsLR3fErjFNxFTmOkzTrUUl/0wOWItZIr5omIdeLFc6w783BvDgHOUFH1+Ip9DpwxQTh EmgGiJzbJjtWUTqzpVeRfQncGnFBDZKFozwOqbo7bBXDHCETdtml7qYl2dleyMIDyDUY 0jsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=UrRDbhlFooJYlcCmYYOsaNNisIb+qcGGT1wJ2uSvw8M=; b=L35FZc/tAwTvQvtbYMKC2pOQ+nq4BsEhoXMipDLkj3HitqN1cXaMx0oDz04Bkm5urn 6SMVL1n6RxrvKIUH9vGq1xxnlY3O3/KDvtSt37YGMJjMZ8Ro/UHh6sliyMgkk5Y6U02M 6DMX9gXH6kwnJHqnEN8TRuH7rNsg2iHNcovXaQoI+EzO/2vGOdgmtMyGlO/x0MqWGqO9 PNYWowNkChDRldD4ifHNdi7wMDDe5xl6YknF/QmSnKY7zZP8z1L4xKGo7Tja2cZtQnmr pgT298xWUFtFDQQqefrfyTtkPcif9Izsfi9dAXdQcYgCXAq6LohV7hZOCm0ag4NjmkkH 6u1g==
X-Gm-Message-State: AJcUukcTFgsh/lJ3HiYUrBHhC/i7FlIpe7BetjuTgBY2SDwBKK05Gx1L +ehrBz60Axv7SZXpbO23/Ow=
X-Google-Smtp-Source: ALg8bN6N6O8oRO7zoIVxfrxOEpMrctuk5T9TquwowGSPqwxuyLTahT7S5nw3EXTKdDQe6nPDPuk32Q==
X-Received: by 2002:a63:4246:: with SMTP id p67mr9736110pga.335.1547659226730; Wed, 16 Jan 2019 09:20:26 -0800 (PST)
Received: from [172.20.10.3] ([172.56.40.32]) by smtp.gmail.com with ESMTPSA id z127sm9773426pfb.80.2019.01.16.09.20.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Jan 2019 09:20:25 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <770921FA-0CAC-44D4-8ABF-7E3EF62098AB@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_92A135C8-F92F-4F5A-B2EA-13405F2C9FDE"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: Non-Last Small IPv6 Fragments
Date: Wed, 16 Jan 2019 09:20:23 -0800
In-Reply-To: <439f1c88-f7ee-8ef6-9721-d431de015c6f@si6networks.com>
Cc: Warren Kumari <warren@kumari.net>, Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>, Fernando Gont <fernando@gont.com.ar>, ek@loon.co
To: Fernando Gont <fgont@si6networks.com>
References: <CAOSSMjV0Vazum5OKztWhAhJrjLjXc5w5YGxdzHgbzi7YVSk7rg@mail.gmail.com> <CALx6S37TJr++fC=pVoeS=mrO1fHc4gL_Wtu-XkVTswzs2XxXCA@mail.gmail.com> <CALx6S36V7vrVyoTP0G6+S5XeFNB3KWS5UaNnVi20xogRERdCfg@mail.gmail.com> <973A1649-55F6-4D97-A97F-CEF555A4D397@employees.org> <CALx6S34YbBe8xBod3VsWVO33TpZcdxh2uV1vaO8Z_NKnVXp66g@mail.gmail.com> <A3C3F9C0-0A07-41AF-9671-B9E486CB8246@employees.org> <AEA47E27-C0CB-4ABE-8ADE-51E9D599EF8F@gmail.com> <6aae7888-46a4-342d-1d76-10f8b50cebc4@gmail.com> <EC9CC5FE-5215-4105-8A34-B3F123D574B9@employees.org> <4c56f504-7cd7-6323-b14a-d34050d13f4e@foobar.org> <9E6D4A6E-8ABA-4BAB-BEC5-969078323C96@employees.org> <CAAedzxpdF+yhBXfnwUcaQb-HkgdaqXRU3L+S7v8sS1F0OkwM9A@mail.gmail.com> <78a8a0e0-8808-364c-41f7-f81f90362432@gont.com.ar> <CAAedzxpjxhP0nOZVU0CTwA1u3fsPFthrJASjDEfnLcRNvr2gBQ@mail.gmail.com> <c9be798e-5a32-7c3e-a948-9ca2fab30411@si6networks.com> <CAHw9_i+M2-420pykp99LcgMNSG=eeDqsZK8+hN20t_uUdANHfA@mail.gmail.com> <439f1c88-f7ee-8ef6-9721-d431de015c6f@si6networks.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ezOwybl9JQE-C8U1Mw9AGl-28cs>
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, 16 Jan 2019 17:20:35 -0000


> On Jan 15, 2019, at 11:42 PM, Fernando Gont <fgont@si6networks.com> wrote:
> 
> On 15/1/19 21:31, Warren Kumari wrote:
> 
>>> [Silly Idea #2]
>>> Separate, even sillier idea: everyone converges on using 16 bits of
>>> the flow ID to encode the lowest MTU encountered along the path.  Here
>>> again, TCP MSS clamping style behaviour would be applied to this
>> 
>> 
>> https://media.giphy.com/media/3o6ZthnDqxfAOFIhdC/giphy.gif
>> Because there are deployed systems already, I don't think that this can
>> be deployed **and fully relied upon**, but Ido think that it might
>> actually be really useful. If the first 2 bits of the flow label are
>> '11' or '10' or something, then it could mean that the next N (13?) bits
> 
> Next question is: This of course implies that, since using this would
> make the FL take a few deterministic values, it cannot be used for e.g.
> ECMP. Hence processing the EH chain becomes a requirement (well, in
> practice it already is).

If you want to monkey with the Flow Label, I'd suggest you get Brian Carpenter into the conversation.

v2.23.0 | Report a Bug | By Email