IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Wed, 08 May 2019 17:26 UTC

Return-Path: <bob.hinden@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 7EFF2120142 for <ipv6@ietfa.amsl.com>; Wed, 8 May 2019 10:26:57 -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 zmEjsB080YR5 for <ipv6@ietfa.amsl.com>; Wed, 8 May 2019 10:26:55 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 257ED120059 for <ipv6@ietf.org>; Wed, 8 May 2019 10:26:55 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id v11so8115358wru.5 for <ipv6@ietf.org>; Wed, 08 May 2019 10:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/yRU23h2SnnrnaK02ggI5RGkLqx5iM9mH3W/0HJyvys=; b=bFSN6iDppbHQvNr/f6PHK39+2C/ioVRKMcVrWnfZlXXPxqtxIROjwjOYQsh4L8JAkY QeGyS84byUAlqlc/2ufSpL25Rl1g+LokLJVTD9lPprC7pmcHiy+2lYGOSM9vJFrdGdWX CGlcE7fmxZFthKj/rn+fPY7GyFuqwpMmjtazH7t/wsc/J/8ot2tB3V6VSYXUNG8g+PMB Enxr6G4goYjSl+v9pZgtOd+U9HOvc0ckAGKtwfLe0GR+b3xyA8iWTvkgxBozG/xeE7bv sTFewOApu0ybtP1DIXOUiozEdvW85jZhUc8CyB1c8hoPg1lW6tfVI7ZVcpILdAu2cf34 CTXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/yRU23h2SnnrnaK02ggI5RGkLqx5iM9mH3W/0HJyvys=; b=GF6xvsQ+xd3jLIyXwG7evZ14WOcVtQ1v+GmzAyDXcK1Mb5+buUxjnWo4Ta6UpwqgtW csJQF/ZJk2gNb528jLm98R2ZF55kE1wGEZeBB0OXyOU5hy71ioucXq74q2xFWcOoMRij 3ohENOVlCiAb7HgDCrDgpxSS1yx2UGhXLgTHf9js1iPr6uhnueTQsigFR+umnqomj2v/ 1aSUV2JfQM/Mu5tmZd217MAcdnMyHc2PMCCpQ7PQjRAf6H2zv9s96qlZ5VVxXTZW9UVw WHHxzUak52RWWN+4PRLTfQezIe3b742b6HBKGNXwkQbF5SYXe8bDrdbWQdiSjF+c0Cj4 X5rQ==
X-Gm-Message-State: APjAAAWUBq3yX6YRISDCfwvxWacpcw6P61gnYmLoa5t12kOTefzFZJTL ha0Mhjj8A4911ZR7+/o/nzVw/Pat
X-Google-Smtp-Source: APXvYqzyzJQngMGMVK4Pf5hF3qRpUTMqJkEsG9xBkgO9Y6a3G6yfz+WnCuaIDO0L3OBFIeLeOnITCg==
X-Received: by 2002:a5d:4648:: with SMTP id j8mr7440070wrs.53.1557336413385; Wed, 08 May 2019 10:26:53 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:d9b5:e07d:1b22:522f? ([2601:647:5a00:ef0b:d9b5:e07d:1b22:522f]) by smtp.gmail.com with ESMTPSA id o81sm931184wmb.2.2019.05.08.10.26.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 May 2019 10:26:52 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: [internet-drafts@ietf.org: New Version Notification for draft-jones-6man-historic-rfc2675-00.txt]
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <19A018DE-280E-4400-95AC-7A3697ABE4B8@employees.org>
Date: Wed, 08 May 2019 10:26:48 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, Ole Trøan <otroan@employees.org>, Tom Jones <tom@erg.abdn.ac.uk>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6A0FA6B-F59B-4F5E-90A8-6B6500425469@gmail.com>
References: <20190508125743.GA19360@tom-desk.erg.abdn.ac.uk> <19A018DE-280E-4400-95AC-7A3697ABE4B8@employees.org>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FexLYxo1ZSgYyXNB6Mw0QKNsF9E>
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:26:58 -0000

Hi,

> On May 8, 2019, at 9:07 AM, Ole Troan <otroan@employees.org> wrote:
> 
>> Hello 6man,
>> 
>> 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?
> 

Are there any current network interfaces that can support packets larger than 65,535 octets?   As I remember, it was intended for network interfaces like hyperchannel that could support packets larger than 65,535.    Did we every define an IPv6 over Hyperchannel specification?

As a co-author of RFC2675, I am OK with making it historic.   It was very limited in use when first defined, and hasn’t gotten better.   

Thanks,
Bob






> I don't expect any implementation supporting it unless they also support data-link layers with an MTU > 64K.
> Or is that the problem you are trying to solve, that a TCP implementation must handle datagrams larger than 64K?
> Is there any other solution?
> 
> Cheers,
> Ole
> 
> 
>> ----- Forwarded message from internet-drafts@ietf.org -----
>> 
>> Date: Wed, 08 May 2019 05:30:11 -0700
>> From: internet-drafts@ietf.org
>> To: Tom Jones <tom@erg.abdn.ac.uk>, Godred Fairhurst <gorry@erg.abdn.ac.uk>, Gorry Fairhurst
>> 	<gorry@erg.abdn.ac.uk>
>> Subject: New Version Notification for draft-jones-6man-historic-rfc2675-00.txt
>> 
>> 
>> A new version of I-D, draft-jones-6man-historic-rfc2675-00.txt
>> has been successfully submitted by Tom Jones and posted to the
>> IETF repository.
>> 
>> Name:		draft-jones-6man-historic-rfc2675
>> Revision:	00
>> Title:		Change Status of RFC 2675 to Historic
>> Document date:	2019-05-08
>> Group:		Individual Submission
>> Pages:		12
>> URL:            https://www.ietf.org/internet-drafts/draft-jones-6man-historic-rfc2675-00.txt
>> Status:         https://datatracker.ietf.org/doc/draft-jones-6man-historic-rfc2675/
>> Htmlized:       https://tools.ietf.org/html/draft-jones-6man-historic-rfc2675-00
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-jones-6man-historic-rfc2675
>> 
>> 
>> Abstract:
>>  This document changes the status of RFC2675, IPv6 Jumbograms, from
>>  Proposed Standard to Historic.
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> 
>> 
>> ----- End forwarded message -----
>> 
>> --------------------------------------------------------------------
>> 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
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email