Return-Path: owner-ipng@sunroof.eng.sun.com Received: from mailserver1.hrz.tu-darmstadt.de (root@mailserver1.hrz.tu-darmstadt.de [130.83.126.41]) by sun14.hrz.tu-darmstadt.de (8.7.1/8.7.1.2pm+udb) with ESMTP id WAA18741 for ; Tue, 27 Jul 1999 22:55:20 +0200 (MET DST) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by mailserver1.hrz.tu-darmstadt.de (8.9.1a/8.9.1) with ESMTP id WAA21871 for ; Tue, 27 Jul 1999 22:54:12 +0200 (MET DST) Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA08540; Tue, 27 Jul 1999 13:54:14 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id NAA11071; Tue, 27 Jul 1999 13:54:12 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id NAA10942 for ipng-dist; Tue, 27 Jul 1999 13:47:16 -0700 (PDT) Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA10935 for ; Tue, 27 Jul 1999 13:47:04 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id NAA09660 for ; Tue, 27 Jul 1999 13:47:03 -0700 (PDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA00495 for ; Tue, 27 Jul 1999 13:47:02 -0700 (PDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24128; Tue, 27 Jul 1999 16:46:26 -0400 (EDT) Message-Id: <199907272046.QAA24128@ietf.org> To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ipng@sunroof.eng.sun.com From: The IESG Subject: Protocol Action: IPv6 Jumbograms to Proposed Standard Date: Tue, 27 Jul 1999 16:46:26 -0400 Sender: owner-ipng@sunroof.eng.sun.com Precedence: bulk X-Mozilla-Status2: 00000000 The IESG has approved the Internet-Draft 'IPv6 Jumbograms' as a Proposed Standard. This document is the product of the IPNG Working Group. The IESG contact persons are Erik Nordmark and Thomas Narten. Technical Summary A "jumbogram" is an IPv6 packet containing a payload longer than 65,535 octets. This document describes the IPv6 Jumbo Payload option, which provides the means of specifying such large payload lengths. It also describes the changes needed to TCP and UDP to make use of jumbograms. Jumbograms are relevant only to IPv6 nodes that may be attached to links with a link MTU greater than 65,575 octets, and need not be implemented or understood by IPv6 nodes that do not support attachment to links with such large MTUs. Working Group Summary The Jumbo Payload options was originally specified in the base IPv6 specification (RFC 1883). TCP and UDP enhancements to support jumbograms were specified in RFC 2147. At the time the IPv6 base specification was advanced to Draft Standard (RFC 2460), multiple interoperable implementations of jumbograms had not been demonstrated. Consequently, jumbogram support was removed from the IPv6 base document in order to advance the rest of the base spec. This document defines the Jumbo Payload option, combining the definition originally in RFC 1883 with the TCP UDP enhancements defined in 2147. Protocol Quality This protocol has been reviewed for the IESG by Thomas Narten and Erik Nordmark. Note to RFC Editor: 1. The IESG requests that the RFC Editor delete section 1.2 (and remove the reference to 2119 in the references section). 2. The IESG requests the RFC Editor to remove section 9 (change log of draft versions) from the document. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo@sunroof.eng.sun.com --------------------------------------------------------------------