Re: [v4v6interim] Fragmentation Options in NAT6 presentation
"Wes Beebee (wbeebee)" <wbeebee@cisco.com> Mon, 06 October 2008 16:35 UTC
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DEF623A6932; Mon, 6 Oct 2008 09:35:18 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D66E33A67DD for <v4v6interim@core3.amsl.com>; Mon, 6 Oct 2008 09:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.374
X-Spam-Level:
X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFIu+FyZ9xob for <v4v6interim@core3.amsl.com>; Mon, 6 Oct 2008 09:35:12 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 44A4D3A6932 for <v4v6interim@ietf.org>; Mon, 6 Oct 2008 09:35:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,368,1220227200"; d="scan'208";a="169706707"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 06 Oct 2008 16:34:53 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m96GYrRm026910; Mon, 6 Oct 2008 09:34:53 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m96GYr9g025624; Mon, 6 Oct 2008 16:34:53 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 6 Oct 2008 12:34:52 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 06 Oct 2008 12:34:51 -0400
Message-ID: <BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <48E6AEBD.9090205@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [v4v6interim] Fragmentation Options in NAT6 presentation
Thread-Index: AcklsjnzPqZeDrtMQ5SJhp27VB9nTQCHk2ow
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org> <BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com> <D2FC99B8-A75A-43BE-9717-DCCE2C807AB7@tahi.org> <48E6AEBD.9090205@gmail.com>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Hiroshi MIYATA <miyata@tahi.org>
X-OriginalArrivalTime: 06 Oct 2008 16:34:52.0629 (UTC) FILETIME=[754B5850:01C927D1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3188; t=1223310893; x=1224174893; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=wbeebee@cisco.com; z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co m> |Subject:=20RE=3A=20[v4v6interim]=20Fragmentation=20Options =20in=20NAT6=20presentation |Sender:=20; bh=NNq4yyRDRDMdjgjDntW7QrtlkJ44O1xwbMXM5vvOD70=; b=sCz5xC+gHonAU7/jBawiVJhXr4XNieeU8hlWZV71DvoGWS3T1y/1ciPlpO 1cEIX+Siy/GGktlamKNMw7McRPTuJGtJLgCZfk4yWmGryhSTzdnPjjRHh7O0 QMuPRZDjJB;
Authentication-Results: sj-dkim-3; header.From=wbeebee@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org
I do agree that RFC 4821 is the right solution, and should be used in recommendations in IETF documents. However, how many stacks actually implement RFC 4821? Perhaps by merely publicizing more widely its existence, we might be able to lure more implementors... - Wes -----Original Message----- From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] Sent: Friday, October 03, 2008 7:46 PM To: Hiroshi MIYATA Cc: Wes Beebee (wbeebee); v4v6interim@ietf.org Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation Actually the *correct* solution is to use a method of PMTU discovery that does not depend on ICMP. That's the point of RFC 4821. Brian On 2008-10-04 08:51, Hiroshi MIYATA wrote: > Correct! > > We have met the problem, and, yes, only the way is fragmenting the > packet on the Translator. > We have developed it as a optional behavior. > > It may cause the argument if we state it in document, since it break > the PMTU Discovery semantics. > > But it is the fact. > > Maybe it is not recommended to describe on BEHAVE documents as a > requirement. > But we should give the hint of this issue on the documents as possible > problems and solution and utilization (since it is not recommended to > use this in public service, but possible to be used for controllable > area of the administrator.) > > Regards, > > ....miyata > > > On 2008/10/04, at 3:36, Wes Beebee (wbeebee) wrote: > >> Some SP's may view ICMP as an attack vector and may explicitly block >> ICMP messages. >> >> In this case, the only way to get connectivity for packets that are >> too large is to fragment. >> >> - Wes >> >> -----Original Message----- >> From: v4v6interim-bounces@ietf.org >> [mailto:v4v6interim-bounces@ietf.org] >> On Behalf Of Hiroshi MIYATA >> Sent: Friday, October 03, 2008 5:31 AM >> To: v4v6interim@ietf.org >> Subject: [v4v6interim] Fragmentation Options in NAT6 presentation >> >> Jennings, >> >> >> FYI. >> Though it is already clearly explained by Dave, let me give you the >> pointer. >> The answer for your question of "Fragmentation options" is clearly >> stated in RFC2765(SIIT) as end-to-end path MTU discovery. >> See Section 3 and 4. >> >> And of course RFC1981(PMTUD) is compliant with it. ;-) Chap. 4 >> Note: A node may receive a Packet Too Big message reporting a >> next-hop MTU that is less than the IPv6 minimum link MTU. In >> that >> case, the node is not required to reduce the size of subsequent >> packets sent on the path to less than the IPv6 minimun link MTU, >> but rather must include a Fragment header in those packets [IPv6- >> SPEC]. >> >> It must work well. ;-) >> >> Regards, >> >> ....miyata >> _______________________________________________ >> v4v6interim mailing list >> v4v6interim@ietf.org >> https://www.ietf.org/mailman/listinfo/v4v6interim >> > > _______________________________________________ > v4v6interim mailing list > v4v6interim@ietf.org > https://www.ietf.org/mailman/listinfo/v4v6interim > _______________________________________________ v4v6interim mailing list v4v6interim@ietf.org https://www.ietf.org/mailman/listinfo/v4v6interim
- [v4v6interim] Fragmentation Options in NAT6 prese… Hiroshi MIYATA
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Wes Beebee (wbeebee)
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Eric Vyncke (evyncke)
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Hiroshi MIYATA
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Brian E Carpenter
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Hiroshi MIYATA
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Wes Beebee (wbeebee)
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Eric Vyncke (evyncke)
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Fred Baker
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Rémi Denis-Courmont
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Brian E Carpenter
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Mark Andrews
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Dan Wing
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Magnus Westerlund
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Brian E Carpenter
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Rémi Denis-Courmont
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Iljitsch van Beijnum
- Re: [v4v6interim] Fragmentation Options in NAT6 p… Eric Vyncke (evyncke)