Re: [internet-drafts@ietf.org: New Version Notification for draft-jones-6man-historic-rfc2675-00.txt]
神明達哉 <jinmei@wide.ad.jp> Wed, 08 May 2019 17:07 UTC
Return-Path: <jinmei.tatuya@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 36BDB120180 for <ipv6@ietfa.amsl.com>; Wed, 8 May 2019 10:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.669
X-Spam-Level:
X-Spam-Status: No, score=-0.669 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 zUO7aJJ1ySTw for <ipv6@ietfa.amsl.com>; Wed, 8 May 2019 10:07:35 -0700 (PDT)
Received: from mail-wr1-f45.google.com (mail-wr1-f45.google.com [209.85.221.45]) (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 5FB0A120043 for <ipv6@ietf.org>; Wed, 8 May 2019 10:07:35 -0700 (PDT)
Received: by mail-wr1-f45.google.com with SMTP id v10so2934667wrt.6 for <ipv6@ietf.org>; Wed, 08 May 2019 10:07:35 -0700 (PDT)
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=gfRLEa+24CKIfeS9RGaPiXbbn0Z/ZPJx7K27j6fM+do=; b=ErUTsEsIUZeWeUp4snqriaYMGg5FmtOwC0PwzwIueit8LedD0xVzc8KZ6NeZ2WopsB 9VrvitF1nwixtALYSaov9I+x5QvuyZgGjsbGicUVMEs4q6HcpypFiKOrrXDN7MmqpeSj RCqy6FLC1EsXfhzzc0pWlzXCORdeam2Ik7fvNQh1CwKsrXbVAjKHwEoT85PkN3zErs3Q 9nfPrq/cDR9YTFIfSv7cjoBuc/V4jaQZllVDCWHgdEw6Y05jaP6XzU5EnBHj28VqDpRo 4iK/5cqDADBD50NVU5WI9HxZ7wv6bXpxUqiBY7Cd4AF4YKsyMi+z/x4NbEoCupMZBfaE pYqg==
X-Gm-Message-State: APjAAAVPNNATpOCty0pXyCJjiDpnr7i83NfGPhiSSDV5MvSXb0rQ3tM9 kP9+zb38TdRtj86r36QCh0MKUk59jfF1eFdceKqKneLL
X-Google-Smtp-Source: APXvYqyfXu+5H0CMuc7835/eY2iRM2XnKxW9WbJ+k4F2P1+2m5t86/fL0TeAVhUDdbh37aViCoOsFGeOsk9fYXv0/PY=
X-Received: by 2002:adf:ec06:: with SMTP id x6mr5601989wrn.159.1557335253572; Wed, 08 May 2019 10:07:33 -0700 (PDT)
MIME-Version: 1.0
References: <20190508125743.GA19360@tom-desk.erg.abdn.ac.uk> <19A018DE-280E-4400-95AC-7A3697ABE4B8@employees.org>
In-Reply-To: <19A018DE-280E-4400-95AC-7A3697ABE4B8@employees.org>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Wed, 08 May 2019 10:07:21 -0700
Message-ID: <CAJE_bqd8PP0j63gr9yqW1+7TpZZsQMeviFHGEB1ZTXFgMLbh0g@mail.gmail.com>
Subject: Re: [internet-drafts@ietf.org: New Version Notification for draft-jones-6man-historic-rfc2675-00.txt]
To: Ole Troan <otroan@employees.org>
Cc: Tom Jones <tom@erg.abdn.ac.uk>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000095e28b0588635e60"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1akVztQJtQQMqwKFP6detXN-SCs>
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:07:37 -0000
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 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
- [internet-drafts@ietf.org: New Version Notificati… Tom Jones
- Re: [internet-drafts@ietf.org: New Version Notifi… Nick Hilliard
- Re: [internet-drafts@ietf.org: New Version Notifi… Mikael Abrahamsson
- Re: [internet-drafts@ietf.org: New Version Notifi… Loganaden Velvindron
- Re: [internet-drafts@ietf.org: New Version Notifi… Ole Troan
- Re: [internet-drafts@ietf.org: New Version Notifi… 神明達哉
- Re: [internet-drafts@ietf.org: New Version Notifi… Bob Hinden
- Re: [internet-drafts@ietf.org: New Version Notifi… Bjoern A. Zeeb
- Re: [internet-drafts@ietf.org: New Version Notifi… Brian E Carpenter
- Re: [internet-drafts@ietf.org: New Version Notifi… Dale W. Carder
- Re: [internet-drafts@ietf.org: New Version Notifi… Brian E Carpenter
- Re: [internet-drafts@ietf.org: New Version Notifi… Mark Smith
- Re: [internet-drafts@ietf.org: New Version Notifi… Tom Jones
- Re: [internet-drafts@ietf.org: New Version Notifi… Alexandre Petrescu
- Re: [internet-drafts@ietf.org: New Version Notifi… Tom Jones
- Re: [internet-drafts@ietf.org: New Version Notifi… Ole Troan
- Re: [internet-drafts@ietf.org: New Version Notifi… Alexandre Petrescu
- Re: [internet-drafts@ietf.org: New Version Notifi… Dale W. Carder
- Re: [internet-drafts@ietf.org: New Version Notifi… Brian E Carpenter
- Re: [internet-drafts@ietf.org: New Version Notifi… Gyan Mishra
- Re: [internet-drafts@ietf.org: New Version Notifi… Gyan Mishra
- Re: [internet-drafts@ietf.org: New Version Notifi… Doug Barton
- Re: [internet-drafts@ietf.org: New Version Notifi… Tim Chown
- Re: [internet-drafts@ietf.org: New Version Notifi… Gyan Mishra
- Re: [internet-drafts@ietf.org: New Version Notifi… Nick Hilliard
- Re: [internet-drafts@ietf.org: New Version Notifi… Brian E Carpenter
- Re: [internet-drafts@ietf.org: New Version Notifi… Erik Kline
- Re: [internet-drafts@ietf.org: New Version Notifi… Gyan Mishra