Re: [v4v6interim] You have been dugg!

"Turchanyi Geza" <turchanyi.geza@gmail.com> Fri, 10 October 2008 07:08 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 746A93A6AA5; Fri, 10 Oct 2008 00:08:40 -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 A1C783A6800 for <v4v6interim@core3.amsl.com>; Fri, 10 Oct 2008 00:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 lSlaZ73q5nP8 for <v4v6interim@core3.amsl.com>; Fri, 10 Oct 2008 00:08:38 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by core3.amsl.com (Postfix) with ESMTP id 3A2AE3A67D8 for <v4v6interim@ietf.org>; Fri, 10 Oct 2008 00:08:38 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id q7so1062678uge.15 for <v4v6interim@ietf.org>; Fri, 10 Oct 2008 00:09:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=QJSF93ZcU9qNoC5oW5gtlZnj+ou17ulSTeDndxhDeAc=; b=BN/hhOnXUewNorfdslRCzBQXrlwNRngcpuhl/2AlBTcr4F0oL7vJ5psO/TTPFPjHue HEk6R0DHOzLC/7mb23aItJprtk5mPAKVRdWDu+Hb66Q+PfYbMSVpqgUss1gKjJi0at3g 8nQ0F4ABXSocQVnuhwk8DytFChwLDQCgQBlJ8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=i4xWnSnFhLLO4OtAqk3SqCbUGRbSdf47gCnGroQpDGDTFTdL1n8E0Lv9n+3W1Kb5JQ EhWzOylQqibriJ87TNpEa8h+zftZd2OkP54eseZTWIc5TXly8pFMldh0weTCUgL7JGks iltw9F7R6CH09cqUhQVFvU/qNqyPf0XvB3THc=
Received: by 10.103.241.5 with SMTP id t5mr771384mur.72.1223622545251; Fri, 10 Oct 2008 00:09:05 -0700 (PDT)
Received: by 10.103.249.10 with HTTP; Fri, 10 Oct 2008 00:09:05 -0700 (PDT)
Message-ID: <f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
Date: Fri, 10 Oct 2008 09:09:05 +0200
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Rémi Després <remi.despres@free.fr>
In-Reply-To: <48EC5D76.5080109@free.fr>
MIME-Version: 1.0
Content-Disposition: inline
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com> <48EC5D76.5080109@free.fr>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Hello,

Well, SAM is an interesting idea.

HOWEVER: if we can implement new software (almost)everywhere, than why
not to use IPv6 everywhere?

I missed the point: what can be kept unchanged in the SAM scenario?

Thanks,

Geza

On Wed, Oct 8, 2008 at 9:12 AM, Rémi Després <remi.despres@free.fr> wrote:
> Iljitsch van Beijnum   (m/j/a) 10/7/08 3:46 PM:
>>
>>
>> http://digg.com/tech_news/IETF_working_on_making_IPv6_and_IPv4_talk_to_each_other
>
> Very clear article, and very nice reading :-).
>
> It would have been more accurate, though, if the A+P and SAM approaches
> would at least have been listed. (Having NAT64, DS Lite and IVI as the
> complete list of solutions discussed "to make the IPv4 world talk to the
> (future) IPv6 world" is missing something.)
>
> Worth being remembered: SAM has more potential than other solutions for
> IPv4-only clients to reach an IPv6 capable server that only has a shared
> IPv4 address (with a restricted port range, accessible via tunnels).
>
> In particular, in draft-despres-SAM-v4v6coexistenceScenarios-00,
> scenario C is as follows (simplified to have encapsulation in IPv6 only,
> and complemented to show on it supports connections both ways).
>
>
>
> +------+                                    +--------+   Global
> | SAM  |           +---------+              |  SAM   |  Internet
> | host |--site v6--| SAM CPE |-- ISP v6 ----| ISP GW |<--- v4 -->
> +------+           +---------+              +--------+
>
>  SAM <--- v4/v6 -->SAM1 SAM2<---- v4/v6 ---> SAM <----- v4 ---->
>    :                    :                      :
>    '- Port restricted   '- Stateless CPE       '--- Stateless GW
>          socket interface
>
>
>        <---- transparency to global v4 packets ----->
>             (outgoing AND incoming connections)
>
>
> Regards,
>
> RD
>
>
> _______________________________________________
> 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