Re: MTU handling and 2461bis
Fred Templin <ftemplin@iprg.nokia.com> Wed, 29 October 2003 01:03 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13364 for <ipv6-archive@odin.ietf.org>; Tue, 28 Oct 2003 20:03:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEek6-00024Z-Uo for ipv6-archive@odin.ietf.org; Tue, 28 Oct 2003 20:03:23 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9T13MDZ007961 for ipv6-archive@odin.ietf.org; Tue, 28 Oct 2003 20:03:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEek6-00024K-QD for ipv6-web-archive@optimus.ietf.org; Tue, 28 Oct 2003 20:03:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13330 for <ipv6-web-archive@ietf.org>; Tue, 28 Oct 2003 20:03:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEek4-0004n2-00 for ipv6-web-archive@ietf.org; Tue, 28 Oct 2003 20:03:20 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEek4-0004mz-00 for ipv6-web-archive@ietf.org; Tue, 28 Oct 2003 20:03:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEejm-0001wd-0C; Tue, 28 Oct 2003 20:03:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEeje-0001vH-B4 for ipv6@optimus.ietf.org; Tue, 28 Oct 2003 20:02:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13290 for <ipv6@ietf.org>; Tue, 28 Oct 2003 20:02:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEeja-0004mB-00 for ipv6@ietf.org; Tue, 28 Oct 2003 20:02:50 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AEeja-0004lc-00 for ipv6@ietf.org; Tue, 28 Oct 2003 20:02:50 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9T12Fp13536; Tue, 28 Oct 2003 17:02:15 -0800
X-mProtect: <200310290102> Nokia Silicon Valley Messaging Protection
Received: from ftemplin.iprg.nokia.com (205.226.2.67, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdCsfDIS; Tue, 28 Oct 2003 17:02:13 PST
Message-ID: <3F9F12D2.4070501@iprg.nokia.com>
Date: Tue, 28 Oct 2003 17:07:30 -0800
From: Fred Templin <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Soliman Hesham <H.Soliman@flarion.com>
CC: "<ipv6@ietf.org>" <ipv6@ietf.org>
Subject: Re: MTU handling and 2461bis
References: <748C6D0A58C0F94CA63C198B6674697A01922E36@ftmail.lab.flarion.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ipv6-admin@ietf.org
Errors-To: ipv6-admin@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Id: IP Version 6 Working Group (ipv6) <ipv6.ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Those interested should perhaps have a look at: http://www.ietf.org/internet-drafts/draft-iesg-vendor-extensions-01.txt before responding to Hesham's question. I am seeing in that document some language that may place the bar for acceptance quite high indeed if we were to adopt Hesham's choice # 2. Thanks - Fred ftemplin@iprg.nokia.com Soliman Hesham wrote: >Folks, > >I've been following this discussion and trying to understand >where people want to solve it. I'm writing my personal >conclusion here and please let me know if you disagree. > >First there is the question of: is this worth solving? >and if it is, can it be entirely solved here or do we >need to involved IEEE? > >There seems to be different opinions here. > >Without getting into the technical issues, which are >discussed in detail, and assuming that people think it's >worth solving, we have two choices in terms of >moving forward: > >1. Add the MTU negotiation between two nodes in 2461 bis >2. Another spec can define those options > >The impression I'm getting is that people are in favour >of (2) above. I'm personally in favour of (2) as well. >This work seems significant enough to have its own spec. >Also, it seems like it will take some time to work out >the details of this optimisation and get concensus >on the details. > >So can we move forward based on this conclusion >and not put this in 2461bis ? > >Thanks, >Hesham > >-------------------------------------------------------------------- >IETF IPv6 working group mailing list >ipv6@ietf.org >Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 >-------------------------------------------------------------------- > > -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- MTU handling and 2461bis Soliman Hesham
- Re: MTU handling and 2461bis Fred Templin
- Re: MTU handling and 2461bis Brian Haberman
- Re: MTU handling and 2461bis JINMEI Tatuya / 神明達哉
- Re: MTU handling and 2461bis Tim Hartrick