Re: [Int-area] WGLC on draft-ietf-intarea-frag-fragile-05

Tom Herbert <tom@herbertland.com> Mon, 14 January 2019 22:04 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFF571313AD for <int-area@ietfa.amsl.com>; Mon, 14 Jan 2019 14:04:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level:
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 LmavYfDAP2zr for <int-area@ietfa.amsl.com>; Mon, 14 Jan 2019 14:04:16 -0800 (PST)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 309281313AB for <int-area@ietf.org>; Mon, 14 Jan 2019 14:04:16 -0800 (PST)
Received: by mail-qk1-x734.google.com with SMTP id d15so450898qkj.0 for <int-area@ietf.org>; Mon, 14 Jan 2019 14:04:16 -0800 (PST)
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:content-transfer-encoding; bh=nSqoC8/464UC8DdlbqyRl3xlPZcxuRlpII4r3hqroqI=; b=BVOi0wAtqD0lUj6aMn53i64dfGz3I128r6BErwhr+EFY673uHUWdX17LrTyKPJqn5V mEpCpcI/6wLfnlcjdDiEhJ6u3WCUsF2k5DGweHISRxpy4C0EaritqgxyPtmhUO/UQt5q S/LaDevKlfPrNJBbUEma77dZBzMIfuJn+3mcQ/O/3/Kzj7nojoAznm24ujyt6n0Fwtkd h4e6iUotT72RdV55Bd99bvWcdD2vP/sD4hOV9QU5ojXFkxr2yIZBjHwmsS3CPpfa4TyU hoZaYFl/5Ja++R8+IWVB8oP4gdjaRT2RgwEzG2T8nRv38fRjVk4+Le1RtucN3/mx/AQE rVZw==
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:content-transfer-encoding; bh=nSqoC8/464UC8DdlbqyRl3xlPZcxuRlpII4r3hqroqI=; b=IwQ0ItyElqo57Kk+lKW+Aa8faKIPlSup7I5E/lis1BKypJu4kzExXAvSrAHng9qJir 0/hCk+ocWSbTnzj6TxMc/uJfmac63kZMzgQxE4yuydJLEuqOgP67Poiv6G8IxX0Wp6Bf GIH9lTBvxE5MvQ2V7kcbJO7LwFmM8vjMvzvvx+BqtortguwTPxVrfBJ5pcm1NsqmgbF9 gEeLhQ+PfFo964jioPi5I37Hg/OWkzXeJVr5YUVHGNPKeju6eij6Jq+yhcCPWitIigT5 Z6Lzuwzg3WKnBkNplOC9wTYIxtNtXaWaSiUATThkS0RdWJ7ZiSc+/qRzg8TGnpqqIY/k BC+Q==
X-Gm-Message-State: AJcUukdPQutwrl2KP7CWdxdM9mNbzjUZHXCkjqAbNcR1CjFz84/+10Xj GXHVa9yiC+CAJrhEVtWG/HC9ZRtCqZWnCx/UWsuUmA==
X-Google-Smtp-Source: ALg8bN6o8ev4lu/2QWbFAecjgIDMxCdJ2OMhoYRoHbN0+RaY2/aCM3kGj2cVEwzy55QvN5oiJkF3U0qeSzGBgGfdUkU=
X-Received: by 2002:a37:b482:: with SMTP id d124mr514554qkf.168.1547503455039; Mon, 14 Jan 2019 14:04:15 -0800 (PST)
MIME-Version: 1.0
References: <D060DC26-15C7-4D3F-A3C5-641072C75CC5@ericsson.com> <4a283194-98f5-8f38-211a-29cfbc4c9c3e@joelhalpern.com>
In-Reply-To: <4a283194-98f5-8f38-211a-29cfbc4c9c3e@joelhalpern.com>
From: Tom Herbert <tom@herbertland.com>
Date: Mon, 14 Jan 2019 14:04:02 -0800
Message-ID: <CALx6S36btHxs0UTjahSMXEmOgfnQMAD+xYVFam=vKvQQfvOVdQ@mail.gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: "internet-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/O058si8D9GSNNlrzaBvTnCzh93k>
Subject: Re: [Int-area] WGLC on draft-ietf-intarea-frag-fragile-05
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2019 22:04:19 -0000

Hello. I have a couple of comments:

>From the draft:
"Middle boxes SHOULD process IP fragments in a manner that is
compliant with RFC 791 and RFC 8200.  In many cases, middle boxes must
maintain state in order to achieve this goal."

This requirement is confusing to me on several accounts. First of all,
there are a lot of requirements about fragmentation in both RFC791 and
RFC8200, including some MUSTs. This requirement seems to be updating
and possibly relaxing some of those requirements, but is not specific.
This seems ambiguous as a normative requirement.

Secondly, the only specified interaction between fragmentation and
intermediate nodes is that routers can fragment packets in IPv4. Other
than that, a middlebox that complies with RFC791 and RFC8200 does not
process or consider fragmentation of packets. Given that, it's unclear
to me why middle boxes would need to maintain state to be protocol
compliant. It's possible that the implicit exception of the
requirement is that middleboxes might perform "in-network reassembly"
or "virtual reassemlby" which would require state. If that is indeed
the case then the requirements for the mechanisms should be spelled
out.

For stateless load balancing (described in section 4.4), the IPv6 flow
label obviates the need for DPI. It is sufficient to hash over the
three tuple <saddr, daddr, flow label> to get good load balancing. All
major OSes have been updated to set flow labels, and there are devices
that already support this. IMO, the draft should make using flow label
for stateless load balancing a SHOULD.

Tom

On Mon, Jan 14, 2019 at 11:55 AM Joel M. Halpern <jmh@joelhalpern.com> wrote:
>
> I have re-read this document.  I think it is a useful document that
> captures that state of a complex tradeoff and makes effective
> recommendations. I support publishing it as a BCP.
>
> If the authors make further additions, adding a mention of ECMP as a
> particular case of stateless load balancers might further improve the
> document.
>
> Yours,
> Joel
>
> On 1/14/19 1:13 PM, Wassim Haddad wrote:
> > Dear all,
> >
> > This email starts an Int-Area WG Last Call on the latest version of "IP Fragmentation Considered Fragile” draft:
> >
> > https://tools.ietf.org/html/draft-ietf-intarea-frag-fragile-05
> >
> > Please respond to this email to support the document and/or send comments by 2019-01-28.
> >
> > Please indicate if you are personally aware of any IPR that applies to draft-ietf-intarea-frag-fragile-xx?
> > If so, has this IPR been disclosed in compliance with IETF IPR rules?
> >
> >
> > Regards,
> >
> > Juan & Wassim
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area
> >
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area