Re: [EXTERNAL] Re: Transmission of IPv6 Jumbograms as Atomic Fragments
David Farmer <farmer@umn.edu> Wed, 17 November 2021 23:27 UTC
Return-Path: <farmer@umn.edu>
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 453933A084B for <ipv6@ietfa.amsl.com>; Wed, 17 Nov 2021 15:27:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=umn.edu
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 lecQIx5IzqV9 for <ipv6@ietfa.amsl.com>; Wed, 17 Nov 2021 15:27:17 -0800 (PST)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AE093A0848 for <ipv6@ietf.org>; Wed, 17 Nov 2021 15:27:17 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id 4HvfGW40N1z9vBv2 for <ipv6@ietf.org>; Wed, 17 Nov 2021 23:27:15 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1nszN2WuoIE for <ipv6@ietf.org>; Wed, 17 Nov 2021 17:27:15 -0600 (CST)
Received: from mail-yb1-f197.google.com (mail-yb1-f197.google.com [209.85.219.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 4HvfGW1SkGz9vBtf for <ipv6@ietf.org>; Wed, 17 Nov 2021 17:27:15 -0600 (CST)
DMARC-Filter: OpenDMARC Filter v1.3.2 mta-p5.oit.umn.edu 4HvfGW1SkGz9vBtf
DKIM-Filter: OpenDKIM Filter v2.11.0 mta-p5.oit.umn.edu 4HvfGW1SkGz9vBtf
Received: by mail-yb1-f197.google.com with SMTP id v133-20020a25c58b000000b005c20153475dso6636011ybe.17 for <ipv6@ietf.org>; Wed, 17 Nov 2021 15:27:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VaNjUcYnPrdl2CMda3adnV9nbmp3KgoWcubQsxII0Ig=; b=n/vTaiH8Y0FEJz5YPq0LwQZZZTA3zWPZWjuN+NlRD5xdOKsE6+Vg/uOLTd285rrDFw CqsMgTOMbCLSejdl/1FH+bU67n6B7w4l/CKN1iKtzynZmdTVza2qv/R99gukzJFEj4qj rbVSb5CWt8pM7lPikiB254Ccrex/YzmScKzHoEYUKMtKl/EmWs7rhiT1QYYl765O11ai qn8eKd+uJe3m3hMuTasopcNMHhGLHNzgyg4Knlk3izEj3w3jqzkUxyE9bBB9wq4cLMos 3S1Bh7cdUMcBaFrcRFr0KQXdKgTp05dy2uTza2xLnozuwOdETfAfrhECxgkxDeA/gxvy IZQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VaNjUcYnPrdl2CMda3adnV9nbmp3KgoWcubQsxII0Ig=; b=PEGwzUoWruKMiVwci6RjOmqK8h4py0n7TLuLszHpCmM8yOP49JKMFi4XdkYgRo5WRp 9XoQmduEOnhXinvWN1TvZ5jUDDwp3Nj9jG/SVhz3ysOf6mcppxD4lUmiXmYV0j9HBJre zrCpD0Pxdszo4JOO8EzVLCyV8hGpZgaMlohJFAtm6yMw6+3y/0bl15gXXPpq8NgZj0vj Zp6zOBtbRB3bsibu8J52pGa1FSKGjtufdBZ/10YDVS6u4Nzuth6sS9NOFgaYerMPUUuP L21xAZyVXOsop3JQKAukkDs/J8/RNdQ2kx5hW8X95nm77JcLxK0TS9EObRZVAl3Sl1SP ta7g==
X-Gm-Message-State: AOAM5324adfVwED0WUUxtBaFrVEwk7IHPIDKV3E3g1q0x4iS40Q5wxQY ta+upV7EdlR5m80IkdRNnX6ZYnioG39gH7uaxlamOVJ5E8VcbcUra9621ISuVK+6z7yPKUAF0DS wHHZRq1PMLYaUKWZweTG2YLSH
X-Received: by 2002:a25:d652:: with SMTP id n79mr24379503ybg.398.1637191634386; Wed, 17 Nov 2021 15:27:14 -0800 (PST)
X-Google-Smtp-Source: ABdhPJzd10QWejjKmMhKMEdBlsWOAaVjB5TBl9UNkbDsAHzu6sUAdQXVMOnXGRsW7IhRnNkD3ACgFOHkcTKzjSCtp2w=
X-Received: by 2002:a25:d652:: with SMTP id n79mr24379469ybg.398.1637191634006; Wed, 17 Nov 2021 15:27:14 -0800 (PST)
MIME-Version: 1.0
References: <70478e56165a4ca5868d28b9672ab177@boeing.com> <7825b454-6b16-23c4-5b01-e170680286bf@gmail.com> <006b94ecb82547328503428eb5847da3@boeing.com>
In-Reply-To: <006b94ecb82547328503428eb5847da3@boeing.com>
From: David Farmer <farmer@umn.edu>
Date: Wed, 17 Nov 2021 17:27:03 -0600
Message-ID: <CAN-Dau38nLYu0mya6Z6eugY=-x1OgGdJ=6B1c1wSwq4-LtCtcw@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: Transmission of IPv6 Jumbograms as Atomic Fragments
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000c6490f05d1046150"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bZO6SNTn49gLkfp8zFqcAVuVCmc>
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, 17 Nov 2021 23:27:22 -0000
While I see no reason to depreciate RFC2675, without evidence of actual active use of jumbograms or at least an intent to use them, but for the issue you describe prevents it, I see no reason to advance the update you propose. Even in the R&E networking community where we make regular use of data grams larger than 1500 bytes, I’m not aware of the use of, or even a desire to use, jumbograms. Thanks On Wed, Nov 17, 2021 at 16:45 Templin (US), Fred L < Fred.L.Templin@boeing.com> wrote: > Brian, I came through the supercomputer lab at NASA Ames in Mt View CA in > 1996/7 > where HiPPI was heavily used. I didn't spend much time there, but enough > to get a > rough read that large packets are plausible. > > At some time not long after that, I had the good fortune to meet Dave > Borman and > asked him about RFC2675 with a "YMBK" pre-disposition toward the concept. > Dave > assured me that the document was serious, and I do not see evidence that > it has > been deprecated. > > So, do I know of any such mega-links? Not offhand, but AFAICT RFC2675 is > still part > of the IPv6 architecture and needs to be honored as such. > > Thanks - Fred > > > -----Original Message----- > > From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] > > Sent: Wednesday, November 17, 2021 1:39 PM > > To: Templin (US), Fred L <Fred.L.Templin@boeing.com>; 6man < > ipv6@ietf.org> > > Subject: [EXTERNAL] Re: Transmission of IPv6 Jumbograms as Atomic > Fragments > > > > EXT email: be mindful of links/attachments. > > > > > > > > Fred, > > > > Is there any evidence of usage of jumbograms? To my knowledge, even the > high energy phsyics community, one of the main proponents of > > jumbograms back in the days when HIPPI seemed important, doesn't use > them, despite extensive use of IPv6 for bulk data. > > > > Regards > > Brian > > > > On 18-Nov-21 06:54, Templin (US), Fred L wrote: > > > Here is a new draft that may be of interest. It is a quick read > (~2pgs) and proposes to > > > update RFC2675 by permitting transmission of IPv6 jumbograms as atomic > fragments. > > > > > > Please post comments to the list. > > > > > > Fred > > > > > > -----Original Message----- > > > From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf > Of internet-drafts@ietf.org > > > Sent: Wednesday, November 17, 2021 9:09 AM > > > To: i-d-announce@ietf.org > > > Subject: I-D Action: draft-templin-6man-jumbofrag-00.txt > > > > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > > > > > > > Title : Transmission of IPv6 Jumbograms as Atomic > Fragments > > > Author : Fred L. Templin > > > Filename : draft-templin-6man-jumbofrag-00.txt > > > Pages : 4 > > > Date : 2021-11-17 > > > > > > Abstract: > > > Internet Protocol, Version 6 (IPv6) provides a service for > > > transmission of IPv6 packets larger than 65,535 octets known as > > > "jumbograms". Such large packets are not eligible for > fragmentation, > > > and the current specification forbids the inclusion of a fragment > > > header of any kind. However, some implementations may wish to > > > include an Identification value with each jumbogram; hence this > > > document proposes the transmission of IPv6 jumbograms as "atomic > > > fragments". > > > > > > > > > The IETF datatracker status page for this draft is: > > > https://datatracker.ietf.org/doc/draft-templin-6man-jumbofrag/ > > > > > > There is also an htmlized version available at: > > > https://datatracker.ietf.org/doc/html/draft-templin-6man-jumbofrag-00 > > > > > > > > > Internet-Drafts are also available by anonymous FTP at: > > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > > > > _______________________________________________ > > > I-D-Announce mailing list > > > I-D-Announce@ietf.org > > > https://www.ietf.org/mailman/listinfo/i-d-announce > > > Internet-Draft directories: http://www.ietf.org/shadow.html > > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > -------------------------------------------------------------------- > > > IETF IPv6 working group mailing list > > > ipv6@ietf.org > > > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > > > -------------------------------------------------------------------- > > > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================
- Transmission of IPv6 Jumbograms as Atomic Fragmen… Templin (US), Fred L
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Brian E Carpenter
- RE: [EXTERNAL] Re: Transmission of IPv6 Jumbogram… Templin (US), Fred L
- Re: [EXTERNAL] Re: Transmission of IPv6 Jumbogram… David Farmer
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Templin (US), Fred L
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Michael Richardson
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Bob Hinden
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Justin Iurman
- RE: Transmission of IPv6 Jumbograms as Atomic Fra… Templin (US), Fred L
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Bob Hinden
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Justin Iurman
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Philip Homburg
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Nick Hilliard
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Templin (US), Fred L
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Mark Smith
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Brian E Carpenter
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Justin Iurman
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Templin (US), Fred L
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Tom Herbert
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Mark Smith
- RE: [EXTERNAL] Re: Transmission of IPv6 Jumbogram… Templin (US), Fred L
- Re: [EXTERNAL] Re: Transmission of IPv6 Jumbogram… David Farmer
- RE: [EXTERNAL] Re: Transmission of IPv6 Jumbogram… Templin (US), Fred L
- Re: [EXTERNAL] Re: Transmission of IPv6 Jumbogram… Mark Smith
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Carsten Bormann
- RE: [EXTERNAL] Re: Transmission of IPv6 Jumbogram… Templin (US), Fred L
- Re: [EXTERNAL] Re: Transmission of IPv6 Jumbogram… Nick Hilliard
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Brian E Carpenter
- Re: Transmission of IPv6 Jumbograms as Atomic Fra… Templin (US), Fred L
- RE: Transmission of IPv6 Jumbograms as Atomic Fra… Templin (US), Fred L