Re: [Int-area] Discussion about Section 6.1 in draft-ietf-intarea-frag-fragile

Bob Hinden <bob.hinden@gmail.com> Sat, 07 September 2019 17:21 UTC

Return-Path: <bob.hinden@gmail.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 A7A4312004F; Sat, 7 Sep 2019 10:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, 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 YrNQ-ZsVn9oO; Sat, 7 Sep 2019 10:21:16 -0700 (PDT)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 D930D120019; Sat, 7 Sep 2019 10:21:15 -0700 (PDT)
Received: by mail-wm1-x32c.google.com with SMTP id q19so9479744wmc.3; Sat, 07 Sep 2019 10:21:15 -0700 (PDT)
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=E7K7LNxLUDecc061c+E0TOEHZ/sFj0Lx1vrFnF2aFiw=; b=PPoKIbIWbAodEqFthwApFzh+vliSsMFh+FgoL193ftWyH8k0kmUDbN/PnqQpClrxTg 1fCgLEim6EvA2XfGw+Qe4a5rL5A7pvncJVF2NPl3uTx1aYS++u/veL2lBoIgug7Us3ul 5O2FCUz4DlPPjPVaWuUTVILpXxSBpeBmYkSkpCiZTQBhknAi7S6bqO3MkAPFGpE7VOkD JCY3yrqQN8C11U9cG4bPqFjvycNX7aWmSuiB69ghzWCrRm5mI5uRdpJysrPSIgowsah6 S8U7tiADF1v7LuTyqBkWN35Tf1Ij1a+5qWjS+5v9yA60k5Vu5gBITvJpxCn+V5OSUUIj BaWQ==
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=E7K7LNxLUDecc061c+E0TOEHZ/sFj0Lx1vrFnF2aFiw=; b=npxQy+aHNOsFp97n+7S3LtoU/p2PBNKDCVhXCaxK0AI255L/uePQY0G9HTVHTQWRcD KQyKnekQhok79UccmWARVx4hnOKq1PN9iz+ZnXJVZd9dqa7Uu7tm8IWkcvRzzFvtjjBh dmUk1ALHGLlCMJzdv36tTcACYQdOFej1Ox5WEnE4oU53FdroQQhjJCGcu50yM5N7SMPc 2Clmeg2+ss74KTtvhk++ZP0Psta/Z5IIP/ETgQ61+HjrV62gXrzEjqOpC6ErQLBmZQin GqSKSqllUzeIUJY9dkkf8veAX5Ex6NuYM0two1TI8NPk0eTJuEljStuBvalN0ZtF1oa9 YXMw==
X-Gm-Message-State: APjAAAW4XuYdMgYUm9V2lfmmEwC4WYL+efZ0cbPm3VAPU2x6D/lcXac+ E++evfAQ4ku2OjfPfJzyQc0=
X-Google-Smtp-Source: APXvYqxaVgo5jxM5/pw2hMyZM24xhaByEQ3H5csZd7Z/pcMcgJg9GAg66M5SU2aQU1M5XLr5OxU9hg==
X-Received: by 2002:a1c:984b:: with SMTP id a72mr12013290wme.149.1567876874374; Sat, 07 Sep 2019 10:21:14 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:15de:4143:383:b9fc? ([2601:647:5a00:ef0b:15de:4143:383:b9fc]) by smtp.gmail.com with ESMTPSA id u22sm18775643wru.72.2019.09.07.10.21.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Sep 2019 10:21:13 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <D9FFECA4-7334-46A1-8460-3FA7FCE16BA7@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A8DED1FC-3521-4817-B037-7AED384426BF"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sat, 7 Sep 2019 10:21:07 -0700
In-Reply-To: <5C51DCDC-4031-47D9-A28E-812D0E66EE35@employees.org>
Cc: Bob Hinden <bob.hinden@gmail.com>, Joe Touch <touch@strayalpha.com>, "int-area@ietf.org" <int-area@ietf.org>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, IESG <iesg@ietf.org>, Joel Halpern <joel.halpern@ericsson.com>, "draft-ietf-intarea-frag-fragile@ietf.org" <draft-ietf-intarea-frag-fragile@ietf.org>, Suresh Krishnan <suresh@kaloom.com>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
To: =?utf-8?Q?Ole_Tr=C3=B8an?= <otroan@employees.org>
References: <efabc7c9f72c4cd9a31f56de24669640@boeing.com> <2EB90A57-9BBD-417C-AEDB-AFBFBB906956@gmail.com> <CAHw9_iKozCAC+8TGS0fSxVZ_3pJW7rnhoKy=Y3AxLqWEXvemcA@mail.gmail.com> <4C8FE1C4-0054-4DA1-BC6E-EBBE78695F1B@gmail.com> <BYAPR05MB5463F112A3FFA8CE6378F3D3AEBB0@BYAPR05MB5463.namprd05.prod.outlook.com> <ab0d5600-d71c-9f0b-2955-64074e040bc6@strayalpha.com> <E770BEF0-D901-4CD0-96E6-C626B560DCD6@gmail.com> <163CD364-2975-467A-8925-F114FFD9C422@employees.org> <E00B6159-2771-42D8-B5E8-7750E0B828DE@strayalpha.com> <3764D860-BC6F-441A-86EF-59E1742D7654@employees.org> <939AFA6F-4C75-4532-82DE-77D14ABC41ED@strayalpha.com> <5C51DCDC-4031-47D9-A28E-812D0E66EE35@employees.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/3svPeaZJB3TYE8BmhEcCpC3PY8U>
X-Mailman-Approved-At: Sat, 07 Sep 2019 12:41:46 -0700
Subject: Re: [Int-area] Discussion about Section 6.1 in draft-ietf-intarea-frag-fragile
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: Sat, 07 Sep 2019 17:21:18 -0000

Ole,

> On Sep 6, 2019, at 9:03 AM, Ole Troan <otroan@employees.org> wrote:
> 
> 
> This document should not recommend IP in UDP in IP encapsulation to achieve end to end IP fragmentation for new applications.

The document doesn’t say that, nor is the document recommending this.  The current text Joe and I proposed to the list was:

   The risks of IP fragmentation can also be mitigated
   through the use of encapsulation, e.g., by transmitting IP fragments
   as payloads.

If this was recommended it would have included the word “recommended” or SHOULD/MUST terminology.

It’s only mentioning this, along with other approaches, as a possible approach for mitigating the problems.

Bob