Re: [internet-drafts@ietf.org: New Version Notification for draft-jones-6man-historic-rfc2675-00.txt]

Loganaden Velvindron <loganaden@gmail.com> Wed, 08 May 2019 17:35 UTC

Return-Path: <loganaden@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 73A1912006D for <ipv6@ietfa.amsl.com>; Wed, 8 May 2019 10:35:02 -0700 (PDT)
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 cSvzbpzAV_jL for <ipv6@ietfa.amsl.com>; Wed, 8 May 2019 10:35:00 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 DF195120178 for <ipv6@ietf.org>; Wed, 8 May 2019 10:34:48 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id y6so17794656ior.5 for <ipv6@ietf.org>; Wed, 08 May 2019 10:34:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=tdKEqVE3l1cr67cuxCdDFRu1TX+yN7v4URrOmHS5wjA=; b=jQ+XKLfBBmrB/na0rtBl2LU5h4moDjCKWfDQMZRaxegSWiwtUqtzp01fC4EHxQTvGB o6QVedu8Q0QVQ/40rQ0UBNU995Hflf1wKwu4HrXqaKaHye9cF4VR3n8Y4yB3hjGtYNhO q9/NiitaQckuBTcBAHii5v5wQePQnL8xUfFXK+p3xjYejQyIOvosxmXbnj1FLxTlTAU4 KsTQW8pNn94T2RegOPgJtooiH7/veMFvfSHWS+s0wIxPJbsYzi/OEFfhY0pgpFWQnu22 14s6qVyAsNy/elnmVfUsEhC6KfAVThl28Usnjo2PrkLz1er4bV9KE1PUP5iXfVC2qrMz +znA==
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=tdKEqVE3l1cr67cuxCdDFRu1TX+yN7v4URrOmHS5wjA=; b=X4iwiSqF0m5UEKEyPdE0PgD1oP0GbeBjiqsurOKZx6FbZOWX/kqtjnh78D71l1+9ND 5iv8LrqZwkfYQmedYzmRoXT5xSxb5xP5FVaZmV89mtEJJA6uZDXb2qUo5SHgYeT/WFiG Z3Xc9KtBOBomPQsXnQ+Di44+1jtDPr5nthVYMUsvRIn+zE48isiqqaqUwv7V/7hE9TYL Yah51X99PSLJs92r5xossOqD/f9NDnxQk9uiEYvf1EzRuWO4cecWPgx7ZnHTKwyap5pc LGCejPkMwI04UaF1070aSDVI9xKZFjs35MLIbOvoVvoutKzeZ3RsGFva0qy3yOe0Fcfl xbgA==
X-Gm-Message-State: APjAAAW58FJ1kYc/tnJI8hkb7Cgq/5b642+FAeg+ssfe78HKvKrJQL4T XMuhZe5DN9jCqlkIC5WYAh1NLZcgfQ0P24yNylA=
X-Google-Smtp-Source: APXvYqzXoi7dF+EKUjmnJpXFT3bLZFhakwRSrStayLCDS8wrAGpFP/cQaMJyHw5IA5aCVUqBKxR6u3GE/DI/1uX1CC4=
X-Received: by 2002:a5d:9dd2:: with SMTP id 18mr1506477ioo.7.1557336888204; Wed, 08 May 2019 10:34:48 -0700 (PDT)
MIME-Version: 1.0
References: <20190508125743.GA19360@tom-desk.erg.abdn.ac.uk> <19A018DE-280E-4400-95AC-7A3697ABE4B8@employees.org> <CAJE_bqd8PP0j63gr9yqW1+7TpZZsQMeviFHGEB1ZTXFgMLbh0g@mail.gmail.com>
In-Reply-To: <CAJE_bqd8PP0j63gr9yqW1+7TpZZsQMeviFHGEB1ZTXFgMLbh0g@mail.gmail.com>
From: Loganaden Velvindron <loganaden@gmail.com>
Date: Wed, 08 May 2019 21:34:36 +0400
Message-ID: <CAOp4FwReRs2krw0GUU8hMBxbvWh6rdv62FD=Z0Se0kFZs1jZ9w@mail.gmail.com>
Subject: Re: [internet-drafts@ietf.org: New Version Notification for draft-jones-6man-historic-rfc2675-00.txt]
To: 神明達哉 <jinmei@wide.ad.jp>
Cc: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/U--A-R3ByMNhkn0cXCnaviYERNU>
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, 08 May 2019 17:35:02 -0000

Comment in-line.

On Wed, May 8, 2019 at 9:08 PM 神明達哉 <jinmei@wide.ad.jp> wrote:
>
> At Wed, 8 May 2019 18:07:51 +0200,
> Ole Troan <otroan@employees.org> wrote:
>
> > > We have put this together to change the status of RFC2675 to Historic
> > > and would like to request discussion in the working group.
> >
> > IPv6 jumbograms was intended for some super computer inter connect with a massive MTU.
> > I don't know of any use of it, but is it harmful if the specification is left there in place?
> >
> > I don't expect any implementation supporting it unless they also support data-link layers with an MTU > 64K.
>
> FWIW, (most if not all) BSD variants have been supporting jumbograms
> for many years (admittedly I don't know if it's still working as

Indeed, according to this
https://www.freebsd.org/doc/en/books/developers-handbook/ipv6.html#ipv6-jumbo

You need to re-compile the kernel to get support for it. So it's not
shipped by default.

I think that it's worth mentioning it that in the draft.

> originally implemented, but the code is still there).  When I worked
> on the implementation I confirmed its behavior with a loopback
> interface configured to have an MTU larger than 64KB.  In that sense,
> this statement of the draft is probably too strong:
>
>    This also removes the need for testing Jumbogram support, which
>    otherwise require links with a MTU greater than 65,535 bytes, making
>    testing of implementations impractical without significant effort.
>
> It's not a straightforward effort, but I don't think it requires a
> "significant" one.
>
> In any case, I agree there has been probably no real world deployment
> of jumbograms.  I don't have a strong opinion about whether to
> deprecate it.
>
> --
> JINMEI, Tatuya
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------