Re: [v4v6interim] Comparison document
"Dan Wing" <dwing@cisco.com> Sun, 21 September 2008 17:02 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 686F53A6BD2; Sun, 21 Sep 2008 10:02:05 -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 CC80928C112 for <v4v6interim@core3.amsl.com>; Sun, 21 Sep 2008 09:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.053
X-Spam-Level:
X-Spam-Status: No, score=-6.053 tagged_above=-999 required=5 tests=[AWL=0.546, 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 D6PMC0IlxNxX for <v4v6interim@core3.amsl.com>; Sun, 21 Sep 2008 09:24:07 -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 EFA143A67EC for <v4v6interim@ietf.org>; Sun, 21 Sep 2008 09:24:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,441,1217808000"; d="scan'208";a="159702358"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 21 Sep 2008 16:24:03 +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 m8LGO3Sk019966; Sun, 21 Sep 2008 09:24:03 -0700
Received: from dwingwxp01 ([10.32.240.194]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8LGO2IM014302; Sun, 21 Sep 2008 16:24:03 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Mikael Lind' <mikael.lind@hexago.com>, v4v6interim@ietf.org
References: <079901c91813$31733990$b3736b80@cisco.com> <004301c91a9e$edfa0430$c9ee0c90$@lind@hexago.com> <053d01c91aa2$9e7a0230$c2f0200a@cisco.com> <1A2228D7D4EF42FA80C8C96B9027D4C5@Maxi>
Date: Sun, 21 Sep 2008 09:24:03 -0700
Message-ID: <0d9001c91c06$761774c0$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AckcAV+HOvtcXiVETsGvL9+vtrZMVAAAxXng
In-Reply-To: <1A2228D7D4EF42FA80C8C96B9027D4C5@Maxi>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2718; t=1222014243; x=1222878243; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[v4v6interim]=20Comparison=20document |Sender:=20; bh=HB0TmdUPscQz2fJLJRjtesWdJuwKsMKAl4goZ1Uck+k=; b=VCZQ7J7gOTbEVk0oyj3B2iCl1s6TOZVsce4+340P4U+Zr6xxpnX20M0nir UVRdd6MFfKJZ6Cb2OlX100c/8ntJhtVN3IvOhu6pbwtsUbcMXQ9x/8ByN1hs s/ouX9w9DB;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Mailman-Approved-At: Sun, 21 Sep 2008 10:02:05 -0700
Subject: Re: [v4v6interim] Comparison document
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
> -----Original Message----- > From: Mikael Lind [mailto:mikael.lind@hexago.com] > Sent: Sunday, September 21, 2008 8:47 AM > To: Dan Wing; v4v6interim@ietf.org > Subject: Re: [v4v6interim] Comparison document > > The client side might be more or less identical, at least for > ip in ip > tunnels, but the concentrator will be quite different. The DS-lite > concentrator doesn't need any establishment or preexisting > states in order > to receive and translate packets, as it is all done per > session, while the > SNAT has to to establish and maintain tunnels for all clients > at all time. I am not an expert in tunnels, but it is my understanding that tunnel establishment is trivial; RFC2003 doesn't require messages to be exchanged to establish a tunnel. As for tunnel maintenance, the problem described in Section 5 of RFC2003 is due to routers along the tunnel path returning short ICMP errors. Since RFC2003 was written, it is my understanding that most routers return longer ICMP errors. If I am wrong, I know someone will correct me. Any such drawbacks should be described in draft-touch-intarea-tunnels-00.txt and we will certainly discuss such drawbacks at the interim meeting and I expect the revised SNAT+DS-Lite draft will discuss the positive and negative aspects of using IPv4-over-IPv6 versus IPv4-over-tunnel. -d > >> 3.1.2 describes the two proposals Dual-stack lite and SNAT as > >> more or less > >> the same. Even if there is discussion about merging them I > >> still think it > >> would be worth pointing out in the document that there is a > >> big difference > >> between the two proposals. > >> DS-lite doesn't require a tunnel to be set up in order to > >> function as it > >> keeps the IPv6 source address as part of the NAT state, much > >> like a NAT-PT. > >> In the case of SNAT there has to exist a tunnel per user > >> before traffic is > >> sent as tunnelling and NAT are more or less separate. > > > > The 3 authors of SNAT and DS-Lite all told me to collapse the > > text of their proposals because they are consolidating the two > > proposals. > > > > SNAT uses the tunnel identifier to distinguish each subscriber; > > DS-Lite uses the IPv6 address to distinguish each subscriber. > > This is a pretty minor distinction in the overall scheme of > > things. In both cases, the concentration endpoint must be > > configured (or otherwise learned, e.g., via a DHCP option) > > and in both cases the NAT44 function needs to differentiate > > each subscriber (such as VLANs, tunnel ID, or IPv6 > > interface) so that subscribers can be given overlapping > > IPv4 addresses. > > > > -d > > _______________________________________________ v4v6interim mailing list v4v6interim@ietf.org https://www.ietf.org/mailman/listinfo/v4v6interim
- [v4v6interim] Comparison document Dan Wing
- Re: [v4v6interim] Comparison document Rémi Després
- Re: [v4v6interim] Comparison document Dan Wing
- Re: [v4v6interim] Comparison document Mikael Lind
- Re: [v4v6interim] Comparison document Dan Wing
- [v4v6interim] scenarios Jari Arkko
- Re: [v4v6interim] Comparison document Mikael Lind
- Re: [v4v6interim] Comparison document Dan Wing
- Re: [v4v6interim] scenarios teemu.savolainen
- Re: [v4v6interim] Comparison document Iljitsch van Beijnum