IETF Logo Mail Archive

RE: [Mip6] about DSMIPv6

"Soliman, Hesham" <hsoliman@qualcomm.com> Mon, 20 March 2006 20:19 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLQr2-0003sd-I9; Mon, 20 Mar 2006 15:19:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLQr0-0003mB-Uy for mip6@ietf.org; Mon, 20 Mar 2006 15:19:50 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLQqz-0001c2-Kk for mip6@ietf.org; Mon, 20 Mar 2006 15:19:50 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id k2KKJgL9019833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 20 Mar 2006 12:19:44 -0800
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109]) by sabrina.qualcomm.com (8.13.5/8.12.5/1.0) with ESMTP id k2KKJaJJ011102; Mon, 20 Mar 2006 12:19:41 -0800 (PST)
Received: from NAEX06.na.qualcomm.com ([129.46.135.161]) by NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Mar 2006 12:19:38 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] about DSMIPv6
Date: Mon, 20 Mar 2006 12:19:36 -0800
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF0014A3CEE@NAEX06.na.qualcomm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mip6] about DSMIPv6
Thread-Index: AcZMW1cCh9EA7FAfQcWHGeNPuEyhJQAACLLQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: Koshiro MITSUYA <mitsuya@sfc.wide.ad.jp>, Francis Dupont <Francis.Dupont@point6.net>
X-OriginalArrivalTime: 20 Mar 2006 20:19:38.0471 (UTC) FILETIME=[9CE64770:01C64C5B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Hesham Soliman <H.Soliman@flarion.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 > I've implemented v4traversal-00 draft.
 > 
 > I agree Francis, the IPv4 mapped address has a special meaning by RFC
 > 2553 API.  It is not preferable to use the mapped address in IPv6
 > headers (See the following the drafts)
 > 	draft-itojun-v6ops-v4mapped-harmful
 > 	draft-cmetz-v6ops-v4mapped-api-harmful
 > 
 > In our code based on KAME, the IPv6 implementation discard a IPv6
 > header which has the v4 mapped address for sanity at ip6_input() and
 > ip6_rthadr2().  We also need to add the mapped address in an address
 > list (the list of all addresses which the node has) to receive the
 > header.  This is somehow uncomfortable because the mapped address is
 > actually not routable.

=> No one suggested that it should/would be routable. It's simply
used to keep the packet format. There is no routing based on this 
information. 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

v2.23.0 | Report a Bug | By Email