IETF Logo Mail Archive

[BEHAVE] NAT64 for Mobile IPv6 - Extension header translation ICMP error issue

Behcet Sarikaya <behcetsarikaya@yahoo.com> Thu, 08 July 2010 21:34 UTC

Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A50043A6A9F for <behave@core3.amsl.com>; Thu, 8 Jul 2010 14:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.965
X-Spam-Level:
X-Spam-Status: No, score=-0.965 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 p90TmBDLEVBI for <behave@core3.amsl.com>; Thu, 8 Jul 2010 14:34:29 -0700 (PDT)
Received: from web111409.mail.gq1.yahoo.com (web111409.mail.gq1.yahoo.com [67.195.15.180]) by core3.amsl.com (Postfix) with SMTP id E649C3A63D3 for <behave@ietf.org>; Thu, 8 Jul 2010 14:31:48 -0700 (PDT)
Received: (qmail 12209 invoked by uid 60001); 8 Jul 2010 21:31:34 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1278624694; bh=bcnUH2NXhyWE1CoxxbdceRhE5TNLThprfdVCkolUOA8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=c4ILpLkVzZoHUjxgmhDcPW2/6KTZsJ4OdtLekjAvrLPsNVCbSKykEVS0/vV+UbZHrZgxg0/QCkgTRK2F1K5wikTCLjOvFfP92QRU8eh/ryg6640hxFhxAszs4zqGkwKE+hYld0aGRJEXDkcFIu/LEic7scUT8GInpTzvocQL8oc=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=e7yha7VWwet4UIjfuowFQq7JLiCF/YZ5nHOh4XzNELTKsbLBv3A33cUcC9c1b4zVdqliKqsKW5wWf1s1yU83S3PDAYyhWoE7/LWtFPkw6u6FY9NJ4xmwpHKVhu9PhiEW0zOvmm7DFx4iKMkT0z5qolcMS4tQT1xpCI4fmzSWdkI=;
Message-ID: <500163.11796.qm@web111409.mail.gq1.yahoo.com>
X-YMail-OSG: iEnzOEQVM1k3vSATxfCFNR2xz5KZHg1FOcVzqy1D9pWkhIC lSAlFI4D3rwoH0zp_TuQK_5tZsSzOHVfEdbJRniZf9ahZiPM_LrccPlXj9rb C7BEUTGeLFi9ByR1TXef_Y7E4Iq8swSlMK1ONIme4_aJlE0gvQxhTPcR9MXL 0qJ113HdhI0TSss7QUR.6KK.mFXf3EUyPQ0.aT8PQDx.4EKX9NxkGWOPUURD 3T_0mzeVTOh2hwgl9Z67coWTbMU3IBEpN8YI9VlFYK5UiXM2L3Hdr4kin.Ze maFMA1lS5g5QX8zIXvi_PvpOq10U0lXVYoXC6ntC8gGyyWtC3lrC5.ormERD MxmO_wWGK8gfK
Received: from [206.16.17.212] by web111409.mail.gq1.yahoo.com via HTTP; Thu, 08 Jul 2010 14:31:34 PDT
X-Mailer: YahooMailRC/420.4 YahooMailWebService/0.8.104.274457
References: <141248.37234.qm@web111414.mail.gq1.yahoo.com>
Date: Thu, 08 Jul 2010 14:31:34 -0700
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: behave@ietf.org
In-Reply-To: <141248.37234.qm@web111414.mail.gq1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Charlie Perkins <charliep@computer.org>, Wassim Haddad <wassim.haddad@ericsson.com>, Dan Wing <dwing@cisco.com>
Subject: [BEHAVE] NAT64 for Mobile IPv6 - Extension header translation ICMP error issue
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 21:34:46 -0000

>Dan Wing wrote:
>By the way, I see that both draft-sarikaya-behave-mext-nat64-dsmip-00  and
>draft-haddad-mext-nat64-mobility-harmful-01 state that IPv6  extension
>headers are not translated and will cause the NAT64 to  generate an ICMP
>error.  However, according to  draft-ietf-behave-v6v4-xlate an ICMP error is
>not generated in that  case - draft-ietf-behave-v6v4-xlate says the extension
>header is  simply skipped and the IPv6 packet is translated to an IPv4
>packet.


In order to start route optimization, MN sends Home Test Init (HoTI) message to 
IPv4-only server by tunneling it to HA. HA removes the tunnel header
and the resulting packet goes through NAT64 packet translation. As Dan says 
above, the extension headers are simply skipped but this packet has no payload, 
I think that is the reason for HA generating an ICMP error and sending it to MN.

Regards,

Behcet


----- Original Message ----
> From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
> To: behave@ietf.org
> Cc: mext@ietf.org
> Sent: Tue, July 6, 2010 3:34:22 PM
> Subject: [BEHAVE] NAT64 for Mobile IPv6
> 
> Hi,
>   We submitted a draft entitled NAT64 for Dual Stack Mobile IPv6  which is  
at:
> http://tools.ietf.org/id/draft-sarikaya-behave-mext-nat64-dsmip-00.txt
> 
> This  draft develops a solution to the problems described in  
>draft-haddad-mext-nat64-mobility-harmful by integrating NAT64 operation with the  
>home agent and binding cache.
> 
> We go one step ahead of NAT64 and provide  multicast support as well.
> 
> Regards,
> 
> Behcet
> 
> 
>        
> _______________________________________________
> Behave  mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

v2.23.0 | Report a Bug | By Email