
From behcetsarikaya@yahoo.com  Mon May  2 08:18:11 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A40FBE06EA for <softwires@ietfa.amsl.com>; Mon,  2 May 2011 08:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.023
X-Spam-Level: 
X-Spam-Status: No, score=-2.023 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vtBZ9c2RuKie for <softwires@ietfa.amsl.com>; Mon,  2 May 2011 08:18:11 -0700 (PDT)
Received: from nm30.bullet.mail.sp2.yahoo.com (nm30.bullet.mail.sp2.yahoo.com [98.139.91.100]) by ietfa.amsl.com (Postfix) with SMTP id 774B3E06E4 for <softwires@ietf.org>; Mon,  2 May 2011 08:18:11 -0700 (PDT)
Received: from [98.139.91.66] by nm30.bullet.mail.sp2.yahoo.com with NNFMP; 02 May 2011 15:18:08 -0000
Received: from [98.139.91.50] by tm6.bullet.mail.sp2.yahoo.com with NNFMP; 02 May 2011 15:18:08 -0000
Received: from [127.0.0.1] by omp1050.mail.sp2.yahoo.com with NNFMP; 02 May 2011 15:18:08 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 515391.48027.bm@omp1050.mail.sp2.yahoo.com
Received: (qmail 66071 invoked by uid 60001); 2 May 2011 15:18:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1304349488; bh=AB0bmy9g9Oww5w7+KAmvXrynpF8+q7S5YpInNJZ3CHc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=mwUVMOeSp2yRZb6vTH4Xa3iEX2d7elsNp8BTLUs6NL6eLk0BO0XYl9V5uvZ0uGFyTiFifl8sZvXuTMhds2i+FTQ97Ky23UowrtTP8iZf9yCgJuumnyv89MfPLJzlI4xroQOd64NNHThSajo2Cij/EQYRF+fw6hpm1hASktOsrfc=
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:Content-Transfer-Encoding; b=agjIKtXgesKRd/Kb89xirexsbpRGbqVP94CDa2D15d/huyIAndLzL8ande73YTA0LOi7CbpWZ0zlCvQ+4gfA2e0swAj1gSlzoBo0JKwe/jKMUJxY2x2BVju4zKMWK7F07nwPu1txXWZHznP6H6Kon+kmGAYVKIGCykSesBY8RH8=;
Message-ID: <192669.64705.qm@web111411.mail.gq1.yahoo.com>
X-YMail-OSG: ilHuOiwVM1kozxmbgfpRp4M2fZ5zcl7liKHhWXwwP.5C8xH ShhzN8Ha9l0ZjIYCbYsQFHN6VLXOmNkvIVPdElQSVHhdAJBbYo1.9PzOIpT8 pSKdlpXj05M_BVP7huNNHAOjkfcSRg3P9cewdsSsi37UvwmRKjskVJ4_XR02 y9CE_PtrUYrBPumYJbFOtrxjpSU7aFK9WcShGT.nFW.0wbJczU5qqa2s6gr7 uq3KH8UBbgbCEYwGJiuUipQc7TT9AzSNebI4F8Nx3A9WGQUkR.r1EjdXdT6X tlBUAWUfXTsmc4ufwuWK4JjRHdT3AC06z5GsOM8Fyw3s9_gtpQQ8O8a5E8JC Eiczz2mbMBOtyWzKpb7DhGl7tYl08_FhYdQaW7Pd4YVkYz85z9StYfKbfbtz sslIqCSt7SAkTovCas4xFEEKhMU2jqgaUFrpMvdmy2w--
Received: from [206.16.17.212] by web111411.mail.gq1.yahoo.com via HTTP; Mon, 02 May 2011 08:18:08 PDT
X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.110.299900
References: <4DB95962.5090407@gmail.com> <EA2B6487-5506-4FC0-9124-61CF6AD86F82@muada.com>
Date: Mon, 2 May 2011 08:18:08 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>, buptnoc <buptnoc@gmail.com>
In-Reply-To: <EA2B6487-5506-4FC0-9124-61CF6AD86F82@muada.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: softwires@ietf.org, behave@ietf.org
Subject: Re: [Softwires] =?utf-8?q?=5BBEHAVE=5D_***SPAM***_5=2E548_=285=29_Is_?= =?utf-8?q?nat46_worth_researching=EF=BC=9F?=
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2011 15:18:11 -0000

This is good point.=0ABut maybe this should be discussed in Softwires list.=
=0A=0ARegards,=0A=0ABehcet=0A=0A> On 28 apr 2011, at 14:11, buptnoc wrote:=
=0A=0A> =0A> >     As described  in draft-ietf-behave-v6v4-framework-10#sec=
tion-2.4 =EF=BC=8C we =0A>need nat46 translator. =0A>=0A> >     But, do we =
really need this scenario=EF=BC=9FIs it worth to  deploy this =0A>scenario?=
=0A> =0A> >     In fact, this scenario appears  when we have v4-only client=
 and v6-only =0A>servers=0A> =0A> My opinion is: no, this  is not worth the=
 trouble. We know that NAT46 is a hard =0A>problem, and it's  unlikely a so=
lution would be very robust. Because of lack of =0A>IPv4 addresses, a  rela=
tively small pool of v4 addresses would have to map to =0A>all possible v6 =
 addresses, which means that the mappings have to be highly =0A>dynamic. Bu=
t  addresses are cached in many places, including often for a long =0A>time=
 in  applications. Having different applications react differently to NAT46=
 =0A>would be  a big deployment problem.=0A> =0A> I would recommend (apart =
from upgrading to  IPv6) deploying HTTP and HTTPS =0A>proxies, as those wil=
l allow HTTP and HTTPS from  IPv4-only clients to IPv6-only =0A>servers (or=
 the other way around!) and in  principle, it's possible to modify =0A>any =
TCP-based application to work through an  HTTPS proxy, as those are =0A>bas=
ically TCP relays.=0A> =0A> It should be possible to  make an automatic pro=
xy configuration so that a =0A>browser only uses the proxy to  reach IPv6 d=
estinations and connects to IPv4 =0A>destinations directly. However, I  hav=
en't tried this myself  yet.=0A> =0A> =0A> ________________________________=
_______________=0A> Behave  mailing list=0A> Behave@ietf.org=0A> https://ww=
w.ietf.org/mailman/listinfo/behave=0A> 

From iljitsch@muada.com  Mon May  2 09:37:53 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B7BDE06CB; Mon,  2 May 2011 09:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.342
X-Spam-Level: 
X-Spam-Status: No, score=-102.342 tagged_above=-999 required=5 tests=[AWL=-0.194, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XNl6cu2YJpmi; Mon,  2 May 2011 09:37:52 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4D5E067E; Mon,  2 May 2011 09:37:52 -0700 (PDT)
Received: from [IPv6:2001:470:1f0b:1289:223:12ff:fe56:36b2] ([IPv6:2001:470:1f0b:1289:223:12ff:fe56:36b2]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p42Gd2Rb080781 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 2 May 2011 18:39:04 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <192669.64705.qm@web111411.mail.gq1.yahoo.com>
Date: Mon, 2 May 2011 18:37:43 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <6941A4D4-9744-441E-9FE9-D7C4A591109E@muada.com>
References: <4DB95962.5090407@gmail.com> <EA2B6487-5506-4FC0-9124-61CF6AD86F82@muada.com> <192669.64705.qm@web111411.mail.gq1.yahoo.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
X-Mailer: Apple Mail (2.1084)
Cc: softwires@ietf.org, behave@ietf.org
Subject: Re: [Softwires] =?utf-8?q?=5BBEHAVE=5D_***SPAM***_5=2E548_=285=29_Is_?= =?utf-8?q?nat46_worth_researching=EF=BC=9F?=
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2011 16:37:53 -0000

On 2 mei 2011, at 17:18, Behcet Sarikaya wrote:

> This is good point.
> But maybe this should be discussed in Softwires list.

Is softwires doing anything related to NAT46 then?


From Internet-Drafts@ietf.org  Mon May  2 10:30:10 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14548E0776; Mon,  2 May 2011 10:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D64ObbLPCcYe; Mon,  2 May 2011 10:30:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 367A0E0790; Mon,  2 May 2011 10:30:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.52
Message-ID: <20110502173002.28039.23095.idtracker@ietfa.amsl.com>
Date: Mon, 02 May 2011 10:30:02 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action:draft-ietf-softwire-dual-stack-lite-08.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2011 17:30:10 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Softwires Working Group of the IETF.


	Title           : Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
	Author(s)       : A. Durand, et al.
	Filename        : draft-ietf-softwire-dual-stack-lite-08.txt
	Pages           : 33
	Date            : 2011-05-02

This document revisits the dual-stack model and introduces the dual-
stack lite technology aimed at better aligning the costs and benefits
of deploying IPv6 in service provider networks.  Dual-stack lite
enables a broadband service provider to share IPv4 addresses among
customers by combining two well-known technologies: IP in IP (IPv4-
in-IPv6) and Network Address Translation (NAT).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-dual-stack-lite-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-softwire-dual-stack-lite-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-05-02102444.I-D@ietf.org>


--NextPart--

From dwing@cisco.com  Mon May  2 22:30:14 2011
Return-Path: <dwing@cisco.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E00DE06F1; Mon,  2 May 2011 22:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.233
X-Spam-Level: 
X-Spam-Status: No, score=-110.233 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TUQlv-ZCjZWD; Mon,  2 May 2011 22:30:13 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 35809E069C; Mon,  2 May 2011 22:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2613; q=dns/txt; s=iport; t=1304400613; x=1305610213; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=iTM0l96rYG+m3gGEc99R2t8aDOGl6cEPSmIgCR32HG8=; b=BdWoPHyWKBStKd7KJMdiEoXnDAM3wGzv1d8Txh0rzp4AnmOS+xOKoia/ DdtrDDhkYQj2N7++xMWqyzjFV7Doa43B+UxgHay+1ZARQu2fENAQsHSYa b1CWPoU3MHpWXBKl/qtLdnRyz5dMZqvPdBPDtmmau8n9TQLg5beI1hphv s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjsBAMORv02rRDoJ/2dsb2JhbACEUZM1gWOMJ3eIcp8qi2WQaoEqg1WBAQSGDpcz
X-IronPort-AV: E=Sophos;i="4.64,307,1301875200"; d="scan'208";a="307040752"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 03 May 2011 05:29:17 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p435TH6m007320; Tue, 3 May 2011 05:29:17 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behcet Sarikaya'" <sarikaya@ieee.org>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>, "'buptnoc'" <buptnoc@gmail.com>
References: <4DB95962.5090407@gmail.com>	<EA2B6487-5506-4FC0-9124-61CF6AD86F82@muada.com> <192669.64705.qm@web111411.mail.gq1.yahoo.com>
In-Reply-To: <192669.64705.qm@web111411.mail.gq1.yahoo.com>
Date: Mon, 2 May 2011 22:29:17 -0700
Message-ID: <01df01cc0953$0c23a560$246af020$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwI3C+FjgR2wVypQceDg2U5kI+1sQAdXdQw
Content-Language: en-us
Cc: softwires@ietf.org, behave@ietf.org
Subject: Re: [Softwires] =?utf-8?q?=5BBEHAVE=5D_***SPAM***_5=2E548_=285=29_Is_?= =?utf-8?q?nat46_worth_researching=EF=BC=9F?=
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 05:30:14 -0000

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Behcet Sarikaya
> Sent: Monday, May 02, 2011 8:18 AM
> To: Iljitsch van Beijnum; buptnoc
> Cc: softwires@ietf.org; behave@ietf.org
> Subject: Re: [BEHAVE] ***SPAM*** 5.548 (5) Is nat46 worth =
researching=EF=BC=9F
>=20
> This is good point.
> But maybe this should be discussed in Softwires list.

NAT46 is in scope of BEHAVE, and is not in scope of SOFTWIRE.  The
BEHAVE charter is clear on that.

But I have not yet understood how or where we would see an IPv4-only
client needing to access an IPv6-only server (that is, a server
with only an IPv6 address).

-d

> Regards,
>=20
> Behcet
>=20
> > On 28 apr 2011, at 14:11, buptnoc wrote:
>=20
> >
> > >     As described  in draft-ietf-behave-v6v4-framework-10#section-
> 2.4 =EF=BC=8C we
> >need nat46 translator.
> >
> > >     But, do we really need this scenario=EF=BC=9FIs it worth to  =
deploy
> this
> >scenario?
> >
> > >     In fact, this scenario appears  when we have v4-only client =
and
> v6-only
> >servers
> >
> > My opinion is: no, this  is not worth the trouble. We know that =
NAT46
> is a hard
> >problem, and it's  unlikely a solution would be very robust. Because
> of lack of
> >IPv4 addresses, a  relatively small pool of v4 addresses would have =
to
> map to
> >all possible v6  addresses, which means that the mappings have to be
> highly
> >dynamic. But  addresses are cached in many places, including often =
for
> a long
> >time in  applications. Having different applications react =
differently
> to NAT46
> >would be  a big deployment problem.
> >
> > I would recommend (apart from upgrading to  IPv6) deploying HTTP and
> HTTPS
> >proxies, as those will allow HTTP and HTTPS from  IPv4-only clients =
to
> IPv6-only
> >servers (or the other way around!) and in  principle, it's possible =
to
> modify
> >any TCP-based application to work through an  HTTPS proxy, as those
> are
> >basically TCP relays.
> >
> > It should be possible to  make an automatic proxy configuration so
> that a
> >browser only uses the proxy to  reach IPv6 destinations and connects
> to IPv4
> >destinations directly. However, I  haven't tried this myself  yet.
> >
> >
> > _______________________________________________
> > Behave  mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> >
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From dr@cluenet.de  Tue May  3 13:15:22 2011
Return-Path: <dr@cluenet.de>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35072E0680 for <softwires@ietfa.amsl.com>; Tue,  3 May 2011 13:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WFyemuPQKcM8 for <softwires@ietfa.amsl.com>; Tue,  3 May 2011 13:15:21 -0700 (PDT)
Received: from mail1.cluenet.de (mail1.cluenet.de [IPv6:2001:1440:201:101::5]) by ietfa.amsl.com (Postfix) with ESMTP id 632D3E067E for <softwires@ietf.org>; Tue,  3 May 2011 13:15:14 -0700 (PDT)
Received: by mail1.cluenet.de (Postfix, from userid 500) id 078B01080B5; Tue,  3 May 2011 22:15:13 +0200 (CEST)
Date: Tue, 3 May 2011 22:15:13 +0200
From: Daniel Roesen <dr@cluenet.de>
To: softwires@ietf.org
Message-ID: <20110503201513.GB14380@srv03.cluenet.de>
Mail-Followup-To: softwires@ietf.org
References: <20110502173002.28039.23095.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110502173002.28039.23095.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Subject: Re: [Softwires] I-D	Action:draft-ietf-softwire-dual-stack-lite-08.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 20:15:22 -0000

On Mon, May 02, 2011 at 10:30:02AM -0700, Internet-Drafts@ietf.org wrote:
> 	Title           : Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
> 	Author(s)       : A. Durand, et al.
> 	Filename        : draft-ietf-softwire-dual-stack-lite-08.txt

7.2.  VPN

   Dual-stack lite implementations MUST NOT interfere with the
   functioning of IPv4 or IPv6 VPNs.

This "MUST NOT" was "SHOULD NOT" in -07. What's the motivation for that
change?

Is there a specific problem/scenario which is supposed to be solved? How
is a DS-Lite implementation supposed to not interfere e.g. with
IPSEC-AH (and other VPN types having inherent problems with NAPT44)?

Best regards,
Daniel

-- 
CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0

From yiu_lee@cable.comcast.com  Tue May  3 15:15:53 2011
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78E37E073C for <softwires@ietfa.amsl.com>; Tue,  3 May 2011 15:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.735
X-Spam-Level: 
X-Spam-Status: No, score=-101.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id veglw-o56ok2 for <softwires@ietfa.amsl.com>; Tue,  3 May 2011 15:15:53 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfa.amsl.com (Postfix) with ESMTP id CBB20E06A1 for <softwires@ietf.org>; Tue,  3 May 2011 15:15:52 -0700 (PDT)
Received: from ([24.40.55.40]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.36799042; Tue, 03 May 2011 16:19:22 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0289.001; Tue, 3 May 2011 18:15:32 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Daniel Roesen <dr@cluenet.de>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: [Softwires] I-D Action:draft-ietf-softwire-dual-stack-lite-08.txt
Thread-Index: AQHMCd+dKyYZ9kqO2kmNe3N8GINoJA==
Date: Tue, 3 May 2011 22:15:31 +0000
Message-ID: <C9E5F3DF.DBC5%yiu_lee@cable.comcast.com>
In-Reply-To: <20110503201513.GB14380@srv03.cluenet.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
x-originating-ip: [68.82.21.189]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1AC7C713032489458A5029D292EC9684@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Softwires] I-D Action:draft-ietf-softwire-dual-stack-lite-08.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 22:15:53 -0000

Hi Daniel,

This change is to address a comment from IESG. Our goal here is to ensure
dslite which is a NAPT44 solution should work like what NAPT44 is supposed
to do today. The word "interfere" should be interpreted that dslite must
not change any existing VPN solutions for NAPT44. It doesn't mean dslite
MUST NOT modify the packet. For example: what defined in RFC3947 and
RFC3948 must not be interfered by dslite.

Best regards,
Yiu


On 5/3/11 4:15 PM, "Daniel Roesen" <dr@cluenet.de> wrote:

>On Mon, May 02, 2011 at 10:30:02AM -0700, Internet-Drafts@ietf.org wrote:
>>     Title           : Dual-Stack Lite Broadband Deployments Following
>>IPv4 Exhaustion
>>     Author(s)       : A. Durand, et al.
>>     Filename        : draft-ietf-softwire-dual-stack-lite-08.txt
>
>7.2.  VPN
>
>   Dual-stack lite implementations MUST NOT interfere with the
>   functioning of IPv4 or IPv6 VPNs.
>
>This "MUST NOT" was "SHOULD NOT" in -07. What's the motivation for that
>change?
>
>Is there a specific problem/scenario which is supposed to be solved? How
>is a DS-Lite implementation supposed to not interfere e.g. with
>IPSEC-AH (and other VPN types having inherent problems with NAPT44)?
>
>Best regards,
>Daniel
>
>--=20
>CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
>_______________________________________________
>Softwires mailing list
>Softwires@ietf.org
>https://www.ietf.org/mailman/listinfo/softwires


From dr@cluenet.de  Tue May  3 15:35:54 2011
Return-Path: <dr@cluenet.de>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B7BE073B for <softwires@ietfa.amsl.com>; Tue,  3 May 2011 15:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vovcu70v9eR for <softwires@ietfa.amsl.com>; Tue,  3 May 2011 15:35:53 -0700 (PDT)
Received: from mail1.cluenet.de (mail1.cluenet.de [IPv6:2001:1440:201:101::5]) by ietfa.amsl.com (Postfix) with ESMTP id 151F7E072E for <softwires@ietf.org>; Tue,  3 May 2011 15:35:52 -0700 (PDT)
Received: by mail1.cluenet.de (Postfix, from userid 500) id A1D3D1080CD; Wed,  4 May 2011 00:35:50 +0200 (CEST)
Date: Wed, 4 May 2011 00:35:50 +0200
From: Daniel Roesen <dr@cluenet.de>
To: softwires@ietf.org
Message-ID: <20110503223550.GA8353@srv03.cluenet.de>
Mail-Followup-To: softwires@ietf.org
References: <20110503201513.GB14380@srv03.cluenet.de> <C9E5F3DF.DBC5%yiu_lee@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C9E5F3DF.DBC5%yiu_lee@cable.comcast.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Subject: Re: [Softwires] I-D	Action:draft-ietf-softwire-dual-stack-lite-08.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 22:35:54 -0000

Hi Yiu,

On Tue, May 03, 2011 at 10:15:31PM +0000, Lee, Yiu wrote:
> This change is to address a comment from IESG. Our goal here is to ensure
> dslite which is a NAPT44 solution should work like what NAPT44 is supposed
> to do today. The word "interfere" should be interpreted that dslite must
> not change any existing VPN solutions for NAPT44. It doesn't mean dslite
> MUST NOT modify the packet. For example: what defined in RFC3947 and
> RFC3948 must not be interfered by dslite.

Thanks. Shouldn't 7.2 then go under chapter 8 "NAT considerations"?
Aren't VPNs traversing the DS-Lite NAPT44 function covered via 8.2
anyway, implicitly?

DS-Lite specific properties and working except the NAPT44 function are
clearly defined, so where's the room for implementors to infer with
VPNs? Unless I'm missing something, 7.2 is quite redundant to 8.2

BTW, are we talking about CPE-terminated IPv4 VPN tunnels, or IPv4 VPN
tunnels traversing a B4 CPE (read: host behind B4 CPE trying to
establish a VPN tunnel to some VPN hub "out there")?

Best regards,
Daniel

-- 
CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0

From yiu_lee@cable.comcast.com  Thu May  5 07:25:53 2011
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A39A2E08B4 for <softwires@ietfa.amsl.com>; Thu,  5 May 2011 07:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.024
X-Spam-Level: 
X-Spam-Status: No, score=-105.024 tagged_above=-999 required=5 tests=[AWL=-3.289, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ai39Mgl+l7XI for <softwires@ietfa.amsl.com>; Thu,  5 May 2011 07:25:52 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfa.amsl.com (Postfix) with ESMTP id AEEDCE08AE for <softwires@ietf.org>; Thu,  5 May 2011 07:25:52 -0700 (PDT)
Received: from ([24.40.55.42]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.37048217; Thu, 05 May 2011 08:29:22 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0289.001; Thu, 5 May 2011 10:25:34 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Daniel Roesen <dr@cluenet.de>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: [Softwires] I-D Action:draft-ietf-softwire-dual-stack-lite-08.txt
Thread-Index: AQHMCzBLb3Cvv689T0G0WHsa0L/zDg==
Date: Thu, 5 May 2011 14:25:34 +0000
Message-ID: <C9E829AD.DDAA%yiu_lee@cable.comcast.com>
In-Reply-To: <20110503223550.GA8353@srv03.cluenet.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
x-originating-ip: [24.40.55.72]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <59E40C7B682B894C92AE427AB1102F09@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Softwires] I-D Action:draft-ietf-softwire-dual-stack-lite-08.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2011 14:25:53 -0000

Hi Daniel,

There are two parts of considerations in dslite, the tunnel part and the
NAPT part. Section 7.2 is on the tunnel consideration. The network must
not interference the VPN packets. Section 8.2 is on the NAPT in the AFTR.
AFTR must support all the requirements in rfc4787 and rfc5382.

We are talking about the host behind B4 element trying to establish a VPN
tunnel.  =20

Regards,
Yiu


On 5/3/11 6:35 PM, "Daniel Roesen" <dr@cluenet.de> wrote:

>Hi Yiu,
>
>On Tue, May 03, 2011 at 10:15:31PM +0000, Lee, Yiu wrote:
>> This change is to address a comment from IESG. Our goal here is to
>>ensure
>> dslite which is a NAPT44 solution should work like what NAPT44 is
>>supposed
>> to do today. The word "interfere" should be interpreted that dslite must
>> not change any existing VPN solutions for NAPT44. It doesn't mean dslite
>> MUST NOT modify the packet. For example: what defined in RFC3947 and
>> RFC3948 must not be interfered by dslite.
>
>Thanks. Shouldn't 7.2 then go under chapter 8 "NAT considerations"?
>Aren't VPNs traversing the DS-Lite NAPT44 function covered via 8.2
>anyway, implicitly?
>
>DS-Lite specific properties and working except the NAPT44 function are
>clearly defined, so where's the room for implementors to infer with
>VPNs? Unless I'm missing something, 7.2 is quite redundant to 8.2
>
>BTW, are we talking about CPE-terminated IPv4 VPN tunnels, or IPv4 VPN
>tunnels traversing a B4 CPE (read: host behind B4 CPE trying to
>establish a VPN tunnel to some VPN hub "out there")?
>
>Best regards,
>Daniel
>
>--=20
>CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
>_______________________________________________
>Softwires mailing list
>Softwires@ietf.org
>https://www.ietf.org/mailman/listinfo/softwires


From satoru.matsushima@gmail.com  Fri May  6 03:40:00 2011
Return-Path: <satoru.matsushima@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 230EFE06FF for <softwires@ietfa.amsl.com>; Fri,  6 May 2011 03:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7Y5k0XbfAg6 for <softwires@ietfa.amsl.com>; Fri,  6 May 2011 03:39:58 -0700 (PDT)
Received: from mail-px0-f179.google.com (mail-px0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id ADD85E06FD for <softwires@ietf.org>; Fri,  6 May 2011 03:39:58 -0700 (PDT)
Received: by pxi2 with SMTP id 2so1904620pxi.38 for <softwires@ietf.org>; Fri, 06 May 2011 03:39:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version:x-mailer; bh=ciSt/2ggA8AvhJPCrO/YziYFN5ChFhh30zIlP/n1PyI=; b=Cko6+zW8BQAu0u02dPh52NLlYCDlOB0znxou+E7n/DMfjes2dIe7/IYdmmalB72nCr mietdE7M6+fmYVemh/oTjR5VaogGywuGDMIt6ABK8vN8AmT0kuCLFvN67ieS+TFneJwF sTtq0m1jGlARWXp3T44x5O25hooD0eQq1uZw4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=Ji1KgWfsuguMMfoU3vuzfrQV8+CmH1GiQxxBV9WhB8xWGvcZitE8a07tamuxP/kZKS Xa3cFNE/sqyDBkmcRvzb7DW4OgaCYHDnnfKnYJL/70XeFnAw5xmjr0SVYSJOpQw7fx8S UtAyL38RSjFy4BkYbM/do8GgxXLumJ/JRDjJc=
Received: by 10.142.207.20 with SMTP id e20mr1952231wfg.129.1304678398073; Fri, 06 May 2011 03:39:58 -0700 (PDT)
Received: from [10.201.80.162] ([202.45.12.174]) by mx.google.com with ESMTPS id x11sm4025337wfd.1.2011.05.06.03.39.56 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 May 2011 03:39:57 -0700 (PDT)
From: Satoru Matsushima <satoru.matsushima@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 May 2011 19:39:55 +0900
Message-Id: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com>
To: Softwires-wg <softwires@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 May 2011 10:40:00 -0000

Dear colleague,=20

We've uploaded an I-D to express our motivation of stateless IPv4 over =
IPv6 as an IPv6 transition solution. Since the outcome of recharter =
session in last softwires wg meeting, ADs required the motivation draft =
to standardize stateless v4 over v6 solution at IETF.

We, authors of the draft, have been trying to clearly explain our =
motivation, scope, and current open questions for stateless solution as =
much as possible in this draft. We believe that it should be helpful to =
understand what our motivation is.

Please find it out from following url:
=
http://www.ietf.org/id/draft-operators-softwire-stateless-4v6-motivation-0=
0.txt

We'd like to have your kind review, and comments, also welcome to =
discuss about the motivation in the softwires mailing list.

Best regards,
--satoru=

From fy@huawei.com  Sun May  8 19:26:59 2011
Return-Path: <fy@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFE56E07AC for <softwires@ietfa.amsl.com>; Sun,  8 May 2011 19:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.335
X-Spam-Level: 
X-Spam-Status: No, score=-5.335 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.263, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id orF2f1STW8JZ for <softwires@ietfa.amsl.com>; Sun,  8 May 2011 19:26:55 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 77158E0684 for <softwires@ietf.org>; Sun,  8 May 2011 19:26:55 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKW00GDVPGTH2@szxga04-in.huawei.com> for softwires@ietf.org; Mon, 09 May 2011 10:26:53 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKW00E6ZPGTYH@szxga04-in.huawei.com> for softwires@ietf.org; Mon, 09 May 2011 10:26:53 +0800 (CST)
Received: from F00171927 ([10.110.98.70]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LKW00L5UPGSM0@szxml04-in.huawei.com> for softwires@ietf.org; Mon, 09 May 2011 10:26:53 +0800 (CST)
Date: Mon, 09 May 2011 10:26:52 +0800
From: fuyu <fy@huawei.com>
To: softwires@ietf.org
Message-id: <006601cc0df0$8f2bdb70$ad839250$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_1EL5rSI1RD8egNnxv5D8Kw)"
Content-language: zh-cn
Thread-index: AcwN8I7pA4bxxQc1SguBZatisXkazQ==
Subject: [Softwires] DS-Lite Management Information Base (MIB)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 02:26:59 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_1EL5rSI1RD8egNnxv5D8Kw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Dear all, 

 

An new I-D has been submitted to softwire wg. It describes the DS-Lite MIB.

 

This draft clearly defines the MIB objects of DS-Lite specifically. The
authors believe that it is helpful for configuration and monitoring the
devices in the Dual-Stack Lite scenario.

 

Please find it out from following url:

http://www.ietf.org/id/draft-fu-softwire-dslite-mib-00.txt

 

Any comments are welcome.

 

Best regards

 

Yu


--Boundary_(ID_1EL5rSI1RD8egNnxv5D8Kw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ZH-CN link=blue vlink=purple style='text-justify-trim:punctuation'><div class=WordSection1><p class=MsoPlainText><span lang=EN-US>Dear all, <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span lang=EN-US>An new I-D has been submitted to softwire wg. It describes the DS-Lite MIB.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span lang=EN-US>This draft clearly defines the MIB objects of DS-Lite specifically. The authors believe that it is helpful for configuration and monitoring the devices in the Dual-Stack Lite scenario.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span lang=EN-US>Please find it out from following url:<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><a href="http://www.ietf.org/id/draft-fu-softwire-dslite
 -mib-00.
id/draft-fu-softwire-dslite-mib-00.txt</a><o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span lang=EN-US>Any comments are welcome.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US>Best regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US>Yu<o:p></o:p></span></p></div></body></html>

--Boundary_(ID_1EL5rSI1RD8egNnxv5D8Kw)--

From matthias.hhs@gmail.com  Mon May  9 01:08:51 2011
Return-Path: <matthias.hhs@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE9B6E07CD for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 01:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pq3hZp3k6Tj8 for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 01:08:51 -0700 (PDT)
Received: from mail-px0-f179.google.com (mail-px0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id 28E66E07CC for <softwires@ietf.org>; Mon,  9 May 2011 01:08:46 -0700 (PDT)
Received: by pxi2 with SMTP id 2so3076503pxi.38 for <softwires@ietf.org>; Mon, 09 May 2011 01:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=EAdj4FbrWd4KCcf0wm3k9uz0B9ATjypPczjcb6jA1dE=; b=czPLOVak9yliFXGKMQEtwZ4hMC9qUvZKCuNTZ3Zeg7GsWM37f0gqFFlJbYZ8VILSQC 9CXoXctUhT5DQthsNEkhz0NheeZoRBLSBZoNZs556qbtkdXdYD3jUZNb2kC7qQxLDZHi fwVCfcIqg70veF3cpRws96Rm9eEe4/MTCbGxk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=awYrHigtY15yH1DFZUwgtcts22oZIUmC3b3mjhIX1gHbAIiQ/kzLbAyXyfTFnew76s qHLhj7iW1GqLuUxQZd4kNZ3DWJya1vbzUzxRdeYOQp+2VZ0N4ea1DJmnA9jfLJdGmPI2 NFmQL8XQb9kAezI5dayN0wYkTMvZJJKkSUZFw=
MIME-Version: 1.0
Received: by 10.142.126.18 with SMTP id y18mr3564699wfc.361.1304928525442; Mon, 09 May 2011 01:08:45 -0700 (PDT)
Received: by 10.142.81.3 with HTTP; Mon, 9 May 2011 01:08:45 -0700 (PDT)
Date: Mon, 9 May 2011 10:08:45 +0200
Message-ID: <BANLkTi=Y-EMGqnDJSqCynG55Cuq2nPC5gw@mail.gmail.com>
From: Matthias van der Heide <matthias.hhs@gmail.com>
To: softwires@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd30bd437614f04a2d359f7
Subject: [Softwires] Tunnel MTU and fragmentation in draft-ietf-softwire-dual-stack-lite-08
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 08:08:51 -0000

--000e0cd30bd437614f04a2d359f7
Content-Type: text/plain; charset=ISO-8859-1

After reading the latest version of the Dual-Stack Lite draft, the issue of
Tunnel MTU and fragmentation got me confused.

Tunneling according to RFC2473 dictates that IPv4 packets exceeding the
Tunnel MTU (Link MTU - size of Tunnel Headers) with the Don't Fragment bit
set should be dropped and answered with an ICMP that carries the Tunnel MTU.

Packets with the Don't Fragment bit cleared that exceed the Tunnel MTU must
be encapsulated and then fragmented.

However, this distinction isn't mentioned in the Dual-Stack Lite draft.
Instead it says (section 5.3):

> However, as not all service providers will be able to increase their
>   link MTU, the B4 element MUST perform fragmentation and reassembly if
>   the outgoing link MTU cannot accommodate for the extra IPv6 header.
>   The original IPv4 packet is not oversized.  The packet is oversized
>   after the IPv6 encapsulation.  The inner IPv4 packet MUST not be
>   fragmented.  Fragmentation MUST happen after the encapsulation on the
>   IPv6 packet.  Reassembly MUST happen before the decapsulation of the
>   IPv6 header.  Detailed procedure has been specified in [RFC2473]
>   Section 7.2.

So although it refers to RFC2473 for the detailed procedures, it modifies
these procedures by removing the distinction between packets
with and without the Don't Fragment bit set.

Is it true that tunneling in Dual-Stack Lite differs from tunneling
described in RFC2473?

If so, what should be used as the MTU value for the link on which a DS-Lite
interface is enabled? Should it be the Link MTU (for instance
1500 in Ethernet), or the Tunnel MTU (Link MTU - 40 or more bytes)? Perhaps
the draft could be extended with an example of a fragmented
flow.

If not, I think the text should be clarified.

In both cases, I hope this helps the draft to become a robust, stable
standard, and I'm willing to contribute.

  - Matthias van der Heide

--000e0cd30bd437614f04a2d359f7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

After reading the latest version of the Dual-Stack Lite draft, the issue of=
 Tunnel MTU and fragmentation got me confused.<br><br>Tunneling according t=
o RFC2473 dictates that IPv4 packets exceeding the Tunnel MTU (Link MTU - s=
ize of Tunnel Headers) with the Don&#39;t Fragment bit set should be droppe=
d and answered with an ICMP that carries the Tunnel MTU.<br>
<br>Packets with the Don&#39;t Fragment bit cleared that exceed the Tunnel =
MTU must be encapsulated and then fragmented.<br><br>However, this distinct=
ion isn&#39;t mentioned in the Dual-Stack Lite draft. Instead it says (sect=
ion 5.3):<br>
<br>&gt; However, as not all service providers will be able to increase the=
ir<br>&gt; =A0 link MTU, the B4 element MUST perform fragmentation and reas=
sembly if<br>&gt; =A0 the outgoing link MTU cannot accommodate for the extr=
a IPv6 header.<br>
&gt; =A0 The original IPv4 packet is not oversized. =A0The packet is oversi=
zed<br>&gt; =A0 after the IPv6 encapsulation. =A0The inner IPv4 packet MUST=
 not be<br>&gt; =A0 fragmented. =A0Fragmentation MUST happen after the enca=
psulation on the<br>
&gt; =A0 IPv6 packet. =A0Reassembly MUST happen before the decapsulation of=
 the<br>&gt; =A0 IPv6 header. =A0Detailed procedure has been specified in [=
RFC2473]<br>&gt; =A0 Section 7.2.<br><br>So although it refers to RFC2473 f=
or the detailed procedures, it modifies these procedures by removing the di=
stinction between packets<br>
with and without the Don&#39;t Fragment bit set.<br><br>Is it true that tun=
neling in Dual-Stack Lite differs from tunneling described in RFC2473?<br><=
br>If so, what should be used as the MTU value for the link on which a DS-L=
ite interface is enabled? Should it be the Link MTU (for instance<br>
1500 in Ethernet), or the Tunnel MTU (Link MTU - 40 or more bytes)? Perhaps=
 the draft could be extended with an example of a fragmented<br>flow.<br><b=
r>If not, I think the text should be clarified. <br><br>In both cases, I ho=
pe this helps the draft to become a robust, stable<br>
standard, and I&#39;m willing to contribute.<br><br>=A0 - Matthias van der =
Heide<br>

--000e0cd30bd437614f04a2d359f7--

From jacniq@gmail.com  Mon May  9 02:29:58 2011
Return-Path: <jacniq@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA0A5E0685 for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 02:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.281
X-Spam-Level: 
X-Spam-Status: No, score=-3.281 tagged_above=-999 required=5 tests=[AWL=0.317,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dnz++MWm6mDt for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 02:29:57 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7E7C1E0679 for <softwires@ietf.org>; Mon,  9 May 2011 02:29:57 -0700 (PDT)
Received: by vxg33 with SMTP id 33so6795553vxg.31 for <softwires@ietf.org>; Mon, 09 May 2011 02:29:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7QWHvRF25rjK7qhOyGqqI4uwl7/Kz5Dh7wJou3mFTQc=; b=OyMIC0Qnb9d+aRu23wbKqX+Xo5S/cj/IAcQSquZJFOTGFpbsbejBtbZ8Jf07hLf++T q9ZDXO0hccZpIqJR0vxTg5plMDHa6oq+L80QL1GtB8YTWY2sEV8sbb2pKVPmGRfZ7Gct As/R7nbl1RizpvC8E6le/TDF1NMXF8vLWSxX4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pmjkqn+WXx1g0CR0jYSdyyXyX/ryfVr1BXSgLB8SMCoVUVqn2mZwhba/Ea65miSnUl 8oQpxpBALOjEz3aatYq6p9OUvW3cDuyC028ABoAGrq0RG+dz0ien/F4iqWvtDS1hSKvJ RF2UU7PuHAXuRc/Bi553Ga8z4OACcMM+YBMN0=
MIME-Version: 1.0
Received: by 10.52.96.33 with SMTP id dp1mr3123608vdb.43.1304933396997; Mon, 09 May 2011 02:29:56 -0700 (PDT)
Received: by 10.52.186.227 with HTTP; Mon, 9 May 2011 02:29:56 -0700 (PDT)
In-Reply-To: <BANLkTi=Y-EMGqnDJSqCynG55Cuq2nPC5gw@mail.gmail.com>
References: <BANLkTi=Y-EMGqnDJSqCynG55Cuq2nPC5gw@mail.gmail.com>
Date: Mon, 9 May 2011 17:29:56 +0800
Message-ID: <BANLkTinnSWEfC7xgJU+bMM6MyHj9=TWtcw@mail.gmail.com>
From: Jacni Qin <jacniq@gmail.com>
To: Matthias van der Heide <matthias.hhs@gmail.com>
Content-Type: multipart/alternative; boundary=20cf307c9d2695677804a2d47b3a
Cc: softwires@ietf.org
Subject: Re: [Softwires] Tunnel MTU and fragmentation in draft-ietf-softwire-dual-stack-lite-08
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 09:29:59 -0000

--20cf307c9d2695677804a2d47b3a
Content-Type: text/plain; charset=ISO-8859-1

hi,

On Mon, May 9, 2011 at 4:08 PM, Matthias van der Heide <
matthias.hhs@gmail.com> wrote:

> After reading the latest version of the Dual-Stack Lite draft, the issue of
> Tunnel MTU and fragmentation got me confused.
>
> Tunneling according to RFC2473 dictates that IPv4 packets exceeding the
> Tunnel MTU (Link MTU - size of Tunnel Headers) with the Don't Fragment bit
> set should be dropped and answered with an ICMP that carries the Tunnel MTU.
>
> Packets with the Don't Fragment bit cleared that exceed the Tunnel MTU must
> be encapsulated and then fragmented.
>
> However, this distinction isn't mentioned in the Dual-Stack Lite draft.
> Instead it says (section 5.3):
>
> > However, as not all service providers will be able to increase their
> >   link MTU, the B4 element MUST perform fragmentation and reassembly if
> >   the outgoing link MTU cannot accommodate for the extra IPv6 header.
> >   The original IPv4 packet is not oversized.  The packet is oversized
> >   after the IPv6 encapsulation.  The inner IPv4 packet MUST not be
> >   fragmented.  Fragmentation MUST happen after the encapsulation on the
> >   IPv6 packet.  Reassembly MUST happen before the decapsulation of the
> >   IPv6 header.  Detailed procedure has been specified in [RFC2473]
> >   Section 7.2.
>
> So although it refers to RFC2473 for the detailed procedures, it modifies
> these procedures by removing the distinction between packets
> with and without the Don't Fragment bit set.
>

Jacni>: It just says "Fragmentation MUST happen after the encapsulation on
the IPv6 packet" , seems to be not in conflict with RFC2473?


Cheers,
Jacni


> Is it true that tunneling in Dual-Stack Lite differs from tunneling
> described in RFC2473?
>
> If so, what should be used as the MTU value for the link on which a DS-Lite
> interface is enabled? Should it be the Link MTU (for instance
> 1500 in Ethernet), or the Tunnel MTU (Link MTU - 40 or more bytes)? Perhaps
> the draft could be extended with an example of a fragmented
> flow.
>
> If not, I think the text should be clarified.
>
> In both cases, I hope this helps the draft to become a robust, stable
> standard, and I'm willing to contribute.
>
>   - Matthias van der Heide
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>

--20cf307c9d2695677804a2d47b3a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<font face=3D"verdana,sans-serif">hi,<br></font><br><div class=3D"gmail_quo=
te">On Mon, May 9, 2011 at 4:08 PM, Matthias van der Heide <span dir=3D"ltr=
">&lt;<a href=3D"mailto:matthias.hhs@gmail.com">matthias.hhs@gmail.com</a>&=
gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">After reading the latest version of the Dua=
l-Stack Lite draft, the issue of Tunnel MTU and fragmentation got me confus=
ed.<br>
<br>Tunneling according to RFC2473 dictates that IPv4 packets exceeding the=
 Tunnel MTU (Link MTU - size of Tunnel Headers) with the Don&#39;t Fragment=
 bit set should be dropped and answered with an ICMP that carries the Tunne=
l MTU.<br>

<br>Packets with the Don&#39;t Fragment bit cleared that exceed the Tunnel =
MTU must be encapsulated and then fragmented.<br><br>However, this distinct=
ion isn&#39;t mentioned in the Dual-Stack Lite draft. Instead it says (sect=
ion 5.3):<br>

<br>&gt; However, as not all service providers will be able to increase the=
ir<br>&gt; =A0 link MTU, the B4 element MUST perform fragmentation and reas=
sembly if<br>&gt; =A0 the outgoing link MTU cannot accommodate for the extr=
a IPv6 header.<br>

&gt; =A0 The original IPv4 packet is not oversized. =A0The packet is oversi=
zed<br>&gt; =A0 after the IPv6 encapsulation. =A0The inner IPv4 packet MUST=
 not be<br>&gt; =A0 fragmented. =A0Fragmentation MUST happen after the enca=
psulation on the<br>

&gt; =A0 IPv6 packet. =A0Reassembly MUST happen before the decapsulation of=
 the<br>&gt; =A0 IPv6 header. =A0Detailed procedure has been specified in [=
RFC2473]<br>&gt; =A0 Section 7.2.<br><br>So although it refers to RFC2473 f=
or the detailed procedures, it modifies these procedures by removing the di=
stinction between packets<br>

with and without the Don&#39;t Fragment bit set.<br></blockquote><div><br><=
font face=3D"verdana,sans-serif">Jacni&gt;: It just says &quot;Fragmentatio=
n MUST happen after the encapsulation on the IPv6 packet&quot; , seems to b=
e not in conflict with RFC2473?<br>
<br><br>Cheers,<br>Jacni<br><br></font></div><blockquote class=3D"gmail_quo=
te" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204=
, 204); padding-left: 1ex;"><br>Is it true that tunneling in Dual-Stack Lit=
e differs from tunneling described in RFC2473?<br>
<br>If so, what should be used as the MTU value for the link on which a DS-=
Lite interface is enabled? Should it be the Link MTU (for instance<br>
1500 in Ethernet), or the Tunnel MTU (Link MTU - 40 or more bytes)? Perhaps=
 the draft could be extended with an example of a fragmented<br>flow.<br><b=
r>If not, I think the text should be clarified. <br><br>In both cases, I ho=
pe this helps the draft to become a robust, stable<br>

standard, and I&#39;m willing to contribute.<br><font color=3D"#888888"><br=
>=A0 - Matthias van der Heide<br>
</font><br>_______________________________________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/softwires</a><br>
<br></blockquote></div><br>

--20cf307c9d2695677804a2d47b3a--

From matthias.hhs@gmail.com  Mon May  9 02:56:28 2011
Return-Path: <matthias.hhs@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B64CE0685 for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 02:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p47sQdddaOzm for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 02:56:27 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id B80BDE0651 for <softwires@ietf.org>; Mon,  9 May 2011 02:56:27 -0700 (PDT)
Received: by pzk5 with SMTP id 5so3088180pzk.31 for <softwires@ietf.org>; Mon, 09 May 2011 02:56:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4C82vx1NVGIqwclfAs86J7KBFmKou6cw1WS6lP5AOqE=; b=Gelz1u0bc/Ik/Sx0ZvyMo2t8SFXFFwmMUwVd4TkIcYYFhX7ky2/GpbxyhCK1AVWpF8 T06VUV8EK/eWOAd6qghJRz7uOZlDvtyLp7f6F/3HmTUofkYQyIP+onDwvCeOatWIavdV bjYTmXV6nrhu+AUq3axqepky/hEZLSmYNBKAk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kJrZnpEDRGXDiCwC9TYWJ01dR3VGRK5hqJ1mTOYZYYN2omYLaWO+hYAa4WWTo3255x vaKXiFuIKt8QwrMqyYfIWgf5kknAmVVl6S5xGBD66qYqAwOLWj21Fuozt+i8gkN2HaYR yKS3VZcxOitKf+exBNsBojBWW+hqtXHWeo0SY=
MIME-Version: 1.0
Received: by 10.142.253.20 with SMTP id a20mr3864368wfi.190.1304934987451; Mon, 09 May 2011 02:56:27 -0700 (PDT)
Received: by 10.142.81.3 with HTTP; Mon, 9 May 2011 02:56:27 -0700 (PDT)
In-Reply-To: <BANLkTinnSWEfC7xgJU+bMM6MyHj9=TWtcw@mail.gmail.com>
References: <BANLkTi=Y-EMGqnDJSqCynG55Cuq2nPC5gw@mail.gmail.com> <BANLkTinnSWEfC7xgJU+bMM6MyHj9=TWtcw@mail.gmail.com>
Date: Mon, 9 May 2011 11:56:27 +0200
Message-ID: <BANLkTikaSvy6NrgR7c7ThsBqAhr0bssv2A@mail.gmail.com>
From: Matthias van der Heide <matthias.hhs@gmail.com>
To: Jacni Qin <jacniq@gmail.com>
Content-Type: multipart/alternative; boundary=00504502ccd861cdc504a2d4da64
Cc: softwires@ietf.org
Subject: Re: [Softwires] Tunnel MTU and fragmentation in draft-ietf-softwire-dual-stack-lite-08
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 09:56:28 -0000

--00504502ccd861cdc504a2d4da64
Content-Type: text/plain; charset=ISO-8859-1

The Dual-Stack Lite draft doesn't mention a different treatment for packets
with the Don't Fragment bit set. RFC 2473 does.

So the procedure in the draft is either incomplete (and should be ammended)
or different from RFC 2473 (so it should state how and why it is different).

Example:

If a packet of 1500 bytes and the Don't Fragment bit set is passed into a
DS-Lite tunnel with a Tunnel MTU of 1460 (1500 - 40 bytes for headers) ,
according to the draft it should be encapsulated, and fragmented in IPv6,
since it's the tunnel headers that cause it to be too big.

In a RFC 2473 compliant tunnel, such packets would be dropped (they are too
large for the Tunnel MTU, and can't be fragmented) and an ICMP Unreachable,
Packet Too Big should be sent.

2011/5/9 Jacni Qin <jacniq@gmail.com>

>
>
> Jacni>: It just says "Fragmentation MUST happen after the encapsulation on
> the IPv6 packet" , seems to be not in conflict with RFC2473?
>
>
> Cheers,
> Jacni
>
>
>

--00504502ccd861cdc504a2d4da64
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The Dual-Stack Lite draft doesn&#39;t mention a different treatment for pac=
kets with the Don&#39;t Fragment bit set. RFC 2473 does.<br><br>So the proc=
edure in the draft is either incomplete (and should be ammended) or differe=
nt from RFC 2473 (so it should state how and why it is different).<br>
<br>Example:<br><br>If a packet of 1500 bytes and the Don&#39;t Fragment bi=
t set is passed into a DS-Lite tunnel with a Tunnel MTU of 1460 (1500 - 40 =
bytes for headers) , according to the draft it should be encapsulated, and =
fragmented in IPv6, since it&#39;s the tunnel headers that cause it to be t=
oo big.<br>
<br>In a RFC 2473 compliant tunnel, such packets would be dropped (they are=
 too large for the Tunnel MTU, and can&#39;t be fragmented) and an ICMP Unr=
eachable, Packet Too Big should be sent.<br><br><div class=3D"gmail_quote">
2011/5/9 Jacni Qin <span dir=3D"ltr">&lt;<a href=3D"mailto:jacniq@gmail.com=
">jacniq@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font =
face=3D"verdana,sans-serif"></font><div class=3D"gmail_quote">
<br><div><br><font face=3D"verdana,sans-serif">Jacni&gt;: It just says &quo=
t;Fragmentation MUST happen after the encapsulation on the IPv6 packet&quot=
; , seems to be not in conflict with RFC2473?<br>
<br><br>Cheers,<br>Jacni<br><br></font></div><br></div></blockquote></div><=
br>

--00504502ccd861cdc504a2d4da64--

From mohamed.boucadair@orange-ftgroup.com  Mon May  9 04:38:21 2011
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E82ECE068D for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 04:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x3Tr3N-qskhe for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 04:38:21 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id DBC47E0685 for <softwires@ietf.org>; Mon,  9 May 2011 04:38:20 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id C3A381B8168; Mon,  9 May 2011 13:38:18 +0200 (CEST)
Received: from PUEXCH41.nanterre.francetelecom.fr (unknown [10.101.44.30]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id A375738405A; Mon,  9 May 2011 13:38:18 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH41.nanterre.francetelecom.fr ([10.101.44.30]) with mapi; Mon, 9 May 2011 13:38:18 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>, Satoru Matsushima <satoru.matsushima@gmail.com>, Yiu Lee <Yiu_Lee@Cable.Comcast.com>, Olaf Bonness <Olaf.Bonness@telekom.de>, Isabel Borges <Isabel@ptinovacao.pt>
Date: Mon, 9 May 2011 13:38:16 +0200
Thread-Topic: [Softwires] Motivation draft for stateless v4 over v6 solution
Thread-Index: AcwOKTTdQAxI8KdISX+yOrJ8yinItAAEbVNw
Message-ID: <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr>
In-Reply-To: <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.9.65415
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 11:38:22 -0000

Hi R=E9mi,

Thank you for the comments.

Please see inline.

Cheers,
Med=20

-----Message d'origine-----
De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
Envoy=E9 : lundi 9 mai 2011 11:10
=C0 : Satoru Matsushima; BOUCADAIR Mohamed OLNC/NAD/TIP; Yiu Lee; Olaf Bonn=
ess; Isabel Borges
Cc : Softwires-wg
Objet : Re: [Softwires] Motivation draft for stateless v4 over v6 solution

Satoru-san, Med, all authors,

Congratulation for this important I-D, and for the quick convergence among =
all of you.=20

Here are, after a detailed review, some remarks:

1. Sec 2 - Terminology (and some other instances of "port range")

"Port space", as used in sec. 5.3, or "port set", would be more appropriate=
 than "port range" in a motivation document because:
- A port range is a particular case of port set or port space, but not the =
reverse.
- At least one documented solution uses port sets that contain several port=
 ranges.

Med: I don't see much the difference between a port range and a port set. I=
MO, what is important is to use consistent terminology in the document. Do =
you have any pointer (other that the solution document you are referring to=
) where "port set" is defined? If needed, I can update the text to state th=
at both "port range" and "port set" are used interchangeably.


2. Sec 3. IPv4 Service Use case

While the "Host based model is out of scope", it would be IMHO good to note=
 that:
"The model can however apply to any host that includes a CPE function".

Med: I prefer having the explicit statement to say the host-based model is =
out of scope.


5.1. Dependency Between IPv4 and IPv6 Address Assignments

The I-D says "Providing two IPv6 prefixes avoids the complexity related to =
the adaptation of the IPv6 addressing scheme to the IPv4 addressing scheme"=
.
But some solutions don't require to adapt the IPv6 addressing scheme to tha=
t of IPv4.
(A particular example is described in sec 3.2 of draft-despres-softwire-sam=
-01. With it, several IPv4 prefixes are supported without any impact on the=
 IPv6 addressing scheme)
Suggestion: after "complexity", add "that may be".

Med: Done. FWIW, I also updated that section with a comment received from R=
. Maglione:

"For Service Providers requiring to apply specific policies on per Address-=
Family (e.g., IPv4, IPv6), some provisioning tools (e.g., DHCPv6 option) ma=
y be required to derive in a deterministic way the IPv6 address to be used =
for the IPv4 traffic based on the IPv6 prefix delegated to the home network=
. "


5.3. Port Randomization

The I-D says "Other means than the (IPv4) source port randomization to prov=
ide protection against attacks should be used (e.g., use
[I-D.vixie-dnsext-dns0x20] to protect against DNS attacks, [RFC5961] to imp=
rove the robustness of TCP against Blind In-Window Attacks)".

However:
- The solution cited as example is from an expired  I-D.
- Another solution is that the DNS server of the operator be accessible in =
IPv6, and that the CPE translates IPv4 DNS queries to send them to this ser=
ver. In this case, no port-set restriction applies.
Suggestion:=20
- Delete the paragraph, or,
- Note that IPv6 DNS servers is a solution (and avoid the reference to I-D.=
vixie-dnsext-dns0x20).

Med: I updated the text to mention that using IPv6 is one of the solutions.


I think this I-D should become asap a WG draft.
(This would preferably be with some improvements like those proposed above,=
 but this isn't IMHO a prerequisite.)

The sooner it reaches RFC status, the better.=20

Regards,
RD






Le 6 mai 2011 =E0 12:39, Satoru Matsushima a =E9crit :

> Dear colleague,=20
>=20
> We've uploaded an I-D to express our motivation of stateless IPv4 over IP=
v6 as an IPv6 transition solution. Since the outcome of recharter session i=
n last softwires wg meeting, ADs required the motivation draft to standardi=
ze stateless v4 over v6 solution at IETF.
>=20
> We, authors of the draft, have been trying to clearly explain our motivat=
ion, scope, and current open questions for stateless solution as much as po=
ssible in this draft. We believe that it should be helpful to understand wh=
at our motivation is.
>=20
> Please find it out from following url:
> http://www.ietf.org/id/draft-operators-softwire-stateless-4v6-motivation-=
00.txt
>=20
> We'd like to have your kind review, and comments, also welcome to discuss=
 about the motivation in the softwires mailing list.
>=20
> Best regards,
> --satoru
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires



From mohamed.boucadair@orange-ftgroup.com  Mon May  9 06:55:08 2011
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E243E075C for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 06:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.963
X-Spam-Level: 
X-Spam-Status: No, score=-1.963 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYk11mrUbihO for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 06:55:07 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by ietfa.amsl.com (Postfix) with ESMTP id DBC6EE075B for <softwires@ietf.org>; Mon,  9 May 2011 06:55:06 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id 443D1C01D6; Mon,  9 May 2011 15:37:25 +0200 (CEST)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 1EAA6384066; Mon,  9 May 2011 15:37:25 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Mon, 9 May 2011 15:37:24 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Mon, 9 May 2011 15:37:24 +0200
Thread-Topic: [Softwires] Motivation draft for stateless v4 over v6 solution
Thread-Index: AcwORneyyQ7gYmT6SiKP1HnWxI3rhwABpFMQ
Message-ID: <94C682931C08B048B7A8645303FDC9F33E4C8082EE@PUEXCB1B.nanterre.francetelecom.fr>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <DFD2D5E7-C5EB-473C-933B-74A47D928654@free.fr>
In-Reply-To: <DFD2D5E7-C5EB-473C-933B-74A47D928654@free.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.9.114215
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 13:55:08 -0000

Re-,

Please see inline.

Cheers,
Med=20

-----Message d'origine-----
De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
Envoy=E9 : lundi 9 mai 2011 14:42
=C0 : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : Satoru Matsushima; Yiu Lee; Olaf Bonness; Isabel Borges; Softwires-wg
Objet : Re: [Softwires] Motivation draft for stateless v4 over v6 solution

Med,

Thank you for the quick reaction.
More in line.
=20
Le 9 mai 2011 =E0 13:38, <mohamed.boucadair@orange-ftgroup.com> a =E9crit :

> Hi R=E9mi,
>=20
> Thank you for the comments.
>=20
> Please see inline.
>=20
> Cheers,
> Med=20
>=20
> -----Message d'origine-----
> De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
> Envoy=E9 : lundi 9 mai 2011 11:10
> =C0 : Satoru Matsushima; BOUCADAIR Mohamed OLNC/NAD/TIP; Yiu Lee; Olaf Bo=
nness; Isabel Borges
> Cc : Softwires-wg
> Objet : Re: [Softwires] Motivation draft for stateless v4 over v6 solutio=
n
>=20
> Satoru-san, Med, all authors,
>=20
> Congratulation for this important I-D, and for the quick convergence amon=
g all of you.=20
>=20
> Here are, after a detailed review, some remarks:
>=20
> 1. Sec 2 - Terminology (and some other instances of "port range")
>=20
> "Port space", as used in sec. 5.3, or "port set", would be more appropria=
te than "port range" in a motivation document because:
> - A port range is a particular case of port set or port space, but not th=
e reverse.
> - At least one documented solution uses port sets that contain several po=
rt ranges.
>=20
> Med: I don't see much the difference between a port range and a port set.

A range is between two limits.
A set of ports defined by several non-overlapping prefixes cannot therefore=
 be called a range.=20
=20
> IMO, what is important is to use consistent terminology in the document.

Same view.

> Do you have any pointer (other that the solution document you are referri=
ng to) where "port set" is defined?

Not that I know, but a port set is self explanatory (nothing more than a se=
t of ports).=20

> If needed, I can update the text to state that both "port range" and "por=
t set" are used interchangeably.

New suggestion, hopefully better: replace, throughout the document, "port r=
ange" by "port range or port set".

Med: For the sake of easing the readability of the document, I added "Withi=
n this document "port set" and "port range" are used interchangeably." inst=
ead of repeating each time both terms.

> 2. Sec 3. IPv4 Service Use case
>=20
> While the "Host based model is out of scope", it would be IMHO good to no=
te that:
> "The model can however apply to any host that includes a CPE function".
>=20
> Med: I prefer having the explicit statement to say the host-based model i=
s out of scope.

Same view.
The intended proposal wasn't to delete this sentence (sorry if it wasn't cl=
ear enough).
It is just to add the new sentence after it.

Med: One can consider a host embedding a CPE function as a router, no?

> 5.1. Dependency Between IPv4 and IPv6 Address Assignments
>=20
> The I-D says "Providing two IPv6 prefixes avoids the complexity related t=
o the adaptation of the IPv6 addressing scheme to the IPv4 addressing schem=
e".
> But some solutions don't require to adapt the IPv6 addressing scheme to t=
hat of IPv4.
> (A particular example is described in sec 3.2 of draft-despres-softwire-s=
am-01. With it, several IPv4 prefixes are supported without any impact on t=
he IPv6 addressing scheme)
> Suggestion: after "complexity", add "that may be".
>=20
> Med: Done.

Thanks.

> FWIW, I also updated that section with a comment received from R. Maglion=
e:
>=20
> "For Service Providers requiring to apply specific policies on per Addres=
s-Family (e.g., IPv4, IPv6), some provisioning tools (e.g., DHCPv6 option) =
may be required to derive in a deterministic way the IPv6 address to be use=
d for the IPv4 traffic based on the IPv6 prefix delegated to the home netwo=
rk. "
>=20
>=20
> 5.3. Port Randomization
>=20
> The I-D says "Other means than the (IPv4) source port randomization to pr=
ovide protection against attacks should be used (e.g., use
> [I-D.vixie-dnsext-dns0x20] to protect against DNS attacks, [RFC5961] to i=
mprove the robustness of TCP against Blind In-Window Attacks)".
>=20
> However:
> - The solution cited as example is from an expired  I-D.
> - Another solution is that the DNS server of the operator be accessible i=
n IPv6, and that the CPE translates IPv4 DNS queries to send them to this s=
erver. In this case, no port-set restriction applies.
> Suggestion:=20
> - Delete the paragraph, or,
> - Note that IPv6 DNS servers is a solution (and avoid the reference to I-=
D.vixie-dnsext-dns0x20).
>=20
> Med: I updated the text to mention that using IPv6 is one of the solution=
s.

Thanks.

> I think this I-D should become asap a WG draft.
> (This would preferably be with some improvements like those proposed abov=
e, but this isn't IMHO a prerequisite.)
>=20
> The sooner it reaches RFC status, the better.=20
>=20
> Regards,
> RD
>=20
>=20
>=20
>=20
>=20
>=20
> Le 6 mai 2011 =E0 12:39, Satoru Matsushima a =E9crit :
>=20
>> Dear colleague,=20
>>=20
>> We've uploaded an I-D to express our motivation of stateless IPv4 over I=
Pv6 as an IPv6 transition solution. Since the outcome of recharter session =
in last softwires wg meeting, ADs required the motivation draft to standard=
ize stateless v4 over v6 solution at IETF.
>>=20
>> We, authors of the draft, have been trying to clearly explain our motiva=
tion, scope, and current open questions for stateless solution as much as p=
ossible in this draft. We believe that it should be helpful to understand w=
hat our motivation is.
>>=20
>> Please find it out from following url:
>> http://www.ietf.org/id/draft-operators-softwire-stateless-4v6-motivation=
-00.txt
>>=20
>> We'd like to have your kind review, and comments, also welcome to discus=
s about the motivation in the softwires mailing list.
>>=20
>> Best regards,
>> --satoru
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20
>=20



From satoru.matsushima@gmail.com  Mon May  9 07:32:23 2011
Return-Path: <satoru.matsushima@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0C7E0726 for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 07:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGzxCvsuMhms for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 07:32:22 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id E3ABAE071C for <softwires@ietf.org>; Mon,  9 May 2011 07:32:22 -0700 (PDT)
Received: by pwi5 with SMTP id 5so3217402pwi.31 for <softwires@ietf.org>; Mon, 09 May 2011 07:32:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=HuuDkgN8j+uf+ev4QxAd4EPGmE5F/qnlSIQDfPifE/U=; b=pPjQztyq1BQtY/nbEGRlGnhKVeIsYbisZ9oEQYLerBbOnjjGkIe700XSe99Fl99BBH 6BXoOus+mklehwWz2Fbe/kC8Ye96xmpYtwdXr7wZ7N1Fj2qy8E8IR2fL+sq6PRpHvWXT QvXzLLc7iEE3NUEj5v14HZUgf5xAljDwUhB/A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=yGpxnAMviccgt813B2wa7K8tdbAU42QKR+tqLS9mkQKgfFMd2qfiipi3YFf7hvYArq uK87A0kKVk1BLKndoiIytSOdW7Zt3Sj3fNeHyRMFEQDWx0SWFgrBODLsUfnPdMpKra2I V5U+JsWYB0/hZSEOlMGuI2YInXnvj8hQpc+Ig=
Received: by 10.142.151.4 with SMTP id y4mr4008290wfd.133.1304948221831; Mon, 09 May 2011 06:37:01 -0700 (PDT)
Received: from [192.168.3.3] (softbank221038134212.bbtec.net [221.38.134.212]) by mx.google.com with ESMTPS id n7sm8143328wfl.23.2011.05.09.06.36.58 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2011 06:37:00 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <DFD2D5E7-C5EB-473C-933B-74A47D928654@free.fr>
Date: Mon, 9 May 2011 22:36:51 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BF766E4-69E3-4234-9120-192484A846C8@gmail.com>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <DFD2D5E7-C5EB-473C-933B-74A47D928654@free.fr>
To: =?utf-8?Q?R=C3=A9mi_Despr=C3=A9s?= <remi.despres@free.fr>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 14:32:23 -0000

Hi Remi-san,

Thanks, I'd like to clarify about:

On 2011/05/09, at 21:41, R=E9mi Despr=E9s wrote:

>> 2. Sec 3. IPv4 Service Use case
>>=20
>> While the "Host based model is out of scope", it would be IMHO good =
to note that:
>> "The model can however apply to any host that includes a CPE =
function".
>>=20
>> Med: I prefer having the explicit statement to say the host-based =
model is out of scope.
>=20
> Same view.
> The intended proposal wasn't to delete this sentence (sorry if it =
wasn't clear enough).
> It is just to add the new sentence after it.

Since CPE is acronym of "Customer Premised Equipment", which means that =
specifying where the equipment installed. It sounds different term from =
what we've discussed about deployment model. Remi-san seem to point out =
a function of customer edge. Is that correct?

Best regards,
--satoru=

From mohamed.boucadair@orange-ftgroup.com  Mon May  9 22:57:08 2011
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E55E8E06D6 for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 22:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level: 
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AReXcSAb+wyQ for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 22:57:08 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7CEE06BD for <softwires@ietf.org>; Mon,  9 May 2011 22:57:07 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id BC8083B42DA; Tue, 10 May 2011 07:57:05 +0200 (CEST)
Received: from PUEXCH21.nanterre.francetelecom.fr (unknown [10.101.44.28]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 93F8715803E; Tue, 10 May 2011 07:57:05 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH21.nanterre.francetelecom.fr ([10.101.44.28]) with mapi; Tue, 10 May 2011 07:57:05 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Tue, 10 May 2011 07:57:03 +0200
Thread-Topic: [Softwires] Motivation draft for stateless v4 over v6 solution
Thread-Index: AcwOZ0j5oWyrSxb9TqSmswfshDLFUQAbXOzQ
Message-ID: <94C682931C08B048B7A8645303FDC9F33E4C808459@PUEXCB1B.nanterre.francetelecom.fr>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <DFD2D5E7-C5EB-473C-933B-74A47D928654@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C8082EE@PUEXCB1B.nanterre.francetelecom.fr> <93E72D52-A316-4F86-867C-EC0045731BAF@free.fr>
In-Reply-To: <93E72D52-A316-4F86-867C-EC0045731BAF@free.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.10.45414
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2011 05:57:09 -0000

Hi R=E9mi,

I understand your point but, and speaking as individual author of the draft=
, my organization does not recommend for the mobile context for instance an=
y transition solution requiring specific functions in the host (this is als=
o the position of the 3GPP IPv6 SI). The main reason is, unlike the CPE cas=
e, we don't control the host.

Cheers,
Med=20

-----Message d'origine-----
De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
Envoy=E9 : lundi 9 mai 2011 18:37
=C0 : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : Satoru Matsushima; Yiu Lee; Olaf Bonness; Isabel Borges; Softwires-wg
Objet : Re: [Softwires] Motivation draft for stateless v4 over v6 solution


Le 9 mai 2011 =E0 15:37, <mohamed.boucadair@orange-ftgroup.com> <mohamed.bo=
ucadair@orange-ftgroup.com> a =E9crit :
> ...
>=20
> Med: For the sake of easing the readability of the document, I added "Wit=
hin this document "port set" and "port range" are used interchangeably." in=
stead of repeating each time both terms.

"Port set" throughout would IMHO have been better, but what you added is go=
od enough.
Thanks.

>> 2. Sec 3. IPv4 Service Use case
>>=20
>> While the "Host based model is out of scope", it would be IMHO good to n=
ote that:
>> "The model can however apply to any host that includes a CPE function".
>>=20
>> Med: I prefer having the explicit statement to say the host-based model =
is out of scope.
>=20
> Same view.
> The intended proposal wasn't to delete this sentence (sorry if it wasn't =
clear enough).
> It is just to add the new sentence after it.
>=20
> Med: One can consider a host embedding a CPE function as a router, no?

Some clarification may be needed for a common understanding.
In the DS-lite draft, we have, concerning the host-based architecture:
"This architecture is targeted at new, large scale deployments of dual-stac=
k capable devices implementing a dual-stack lite interface."

I don't see why the stateless solution couldn't have a host-based variant "=
targeted at new, large scale deployments of dual-stack capable devices impl=
ementing" the CPE router function.

Just saying "host-based models are out of scope" seems to me more negative =
than needed.


The host-based DS-lite architecture is illustrated by:
"              +-------------------+
               |                   |
               |  Host 192.0.0.2   |
               |+--------+--------+|
               ||        B4       ||
               |+--------+--------+|
               +--------|||--------+
                        |||2001:db8:0:1::1
                        |||
                        |||<-IPv4-in-IPv6 softwire
                        |||
                 -------|||-------
               /        |||        \
              |   ISP core network  |
               \        |||        /
                 -------|||-------
                        |||
                        |||2001:db8:0:2::1
               +--------|||--------+
               |       AFTR        |
               |+--------+--------+|
               ||  Concentrator   ||
               |+--------+--------+|
               |       |NAT|       |
               |       +-+-+       |
               +---------|---------+
                         |192.0.2.1
                         |
                 --------|--------
               /         |         \
              |       Internet      |
               \         |         /
                 --------|--------
                         |
                         |198.51.100.1
                   +-----+-----+
                   | IPv4 Host |
                   +-----------+          "

The host-based stateless-IPv4/IPv6 architecture can similarly be illustrate=
d by.
"              +-------------------+
               |       Host        |
               | RFC 1918 address  |
               |+--------+--------+|
               || Stateless v4/v6 ||
               ||  CPE function   ||
               || (incl. NAPT44)  ||
               |+--------+--------+|
               +--------|||--------+
                        |||2001:db8:0:1::1
                        |||
                        |||<-IPv4-in-IPv6 stateless
                        |||
                 -------|||-------
               /        |||        \
              |   ISP core network  |
               \        |||        /
                 -------|||-------
                        |||
                        |||2001:db8:0:2::1=20
               +--------|||--------+
               |     Stateless     |
               |    IPv4/IPv6      |
               |  interconnection  |
               |     function      |
               +---------|---------+
                         |192.0.2.1
                         |
                 --------|--------
               /         |         \
              |       Internet      |
               \         |         /
                 --------|--------
                         |
                         |198.51.100.1
                   +-----+-----+
                   | IPv4 Host |
                   +-----------+          "

Am I missing something?

Regards,
RD=20





From satoru.matsushima@gmail.com  Mon May  9 23:28:05 2011
Return-Path: <satoru.matsushima@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D1FE0669 for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 23:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlAtG7WqsvOd for <softwires@ietfa.amsl.com>; Mon,  9 May 2011 23:28:04 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfa.amsl.com (Postfix) with ESMTP id 92F5BE06A0 for <softwires@ietf.org>; Mon,  9 May 2011 23:28:04 -0700 (PDT)
Received: by pvh1 with SMTP id 1so3628252pvh.31 for <softwires@ietf.org>; Mon, 09 May 2011 23:28:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=W6/49b6/1uPTWMcpSGUsEA4YTT8PGLK91aGiij+fEQQ=; b=Hsdu3PERVn+WUkRv0URpVnYoVA8mzEW09NBQNNlMqzuzRbN9JgWC7WlZSP7UZ69QGt /Knrchmm7dRUVawPWA+eZKPsx7mIPwihLoWiSPDTE9GqK/Y7XfxfkL2o+FPzwy2kNlT/ mXC93OJ7uwRFEapMlNf8XH/a+fvRPYwphb0WE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=s0Hxk/iBPLIm0oBKTfCz849Uzx+lI247HwWgG/5oV61iDA/zg0Kk07bSxeMqcSwgJ6 M5aCxzVvlZYGDzvvYChf9nCW3mNpFIGO2u2EY4rIBoeAUtuLfebyfrwtkWc2Ys1CGCMV XZOx/vJNFWGz/Ne3Mc59Zb47qcyYnbLJLiMqg=
Received: by 10.68.43.100 with SMTP id v4mr504630pbl.432.1305008883753; Mon, 09 May 2011 23:28:03 -0700 (PDT)
Received: from [10.201.80.162] ([202.45.12.174]) by mx.google.com with ESMTPS id 5sm4606751pbn.25.2011.05.09.23.28.00 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2011 23:28:02 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F33E4C808459@PUEXCB1B.nanterre.francetelecom.fr>
Date: Tue, 10 May 2011 15:27:56 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BD5DE38-965B-4362-9700-9931B3E958C4@gmail.com>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <DFD2D5E7-C5EB-473C-933B-74A47D928654@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C8082EE@PUEXCB1B.nanterre.francetelecom.fr> <93E72D52-A316-4F86-867C-EC0045731BAF@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C808459@PUEXCB1B.nanterre.francetelecom.fr>
To: <mohamed.boucadair@orange-ftgroup.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2011 06:28:05 -0000

Remi-san has simply pointed out that the service use case section of the =
draft assumes same implication in the ds-lite draft. I think that it =
would be no problem, and better to just remove the use case section, =
because the draft already expressed it as target space table in the =
introduction.

Best regards,
--satoru


On 2011/05/10, at 14:57, <mohamed.boucadair@orange-ftgroup.com> wrote:

> Hi R=E9mi,
>=20
> I understand your point but, and speaking as individual author of the =
draft, my organization does not recommend for the mobile context for =
instance any transition solution requiring specific functions in the =
host (this is also the position of the 3GPP IPv6 SI). The main reason =
is, unlike the CPE case, we don't control the host.
>=20
> Cheers,
> Med=20
>=20
> -----Message d'origine-----
> De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
> Envoy=E9 : lundi 9 mai 2011 18:37
> =C0 : BOUCADAIR Mohamed OLNC/NAD/TIP
> Cc : Satoru Matsushima; Yiu Lee; Olaf Bonness; Isabel Borges; =
Softwires-wg
> Objet : Re: [Softwires] Motivation draft for stateless v4 over v6 =
solution
>=20
>=20
> Le 9 mai 2011 =E0 15:37, <mohamed.boucadair@orange-ftgroup.com> =
<mohamed.boucadair@orange-ftgroup.com> a =E9crit :
>> ...
>>=20
>> Med: For the sake of easing the readability of the document, I added =
"Within this document "port set" and "port range" are used =
interchangeably." instead of repeating each time both terms.
>=20
> "Port set" throughout would IMHO have been better, but what you added =
is good enough.
> Thanks.
>=20
>>> 2. Sec 3. IPv4 Service Use case
>>>=20
>>> While the "Host based model is out of scope", it would be IMHO good =
to note that:
>>> "The model can however apply to any host that includes a CPE =
function".
>>>=20
>>> Med: I prefer having the explicit statement to say the host-based =
model is out of scope.
>>=20
>> Same view.
>> The intended proposal wasn't to delete this sentence (sorry if it =
wasn't clear enough).
>> It is just to add the new sentence after it.
>>=20
>> Med: One can consider a host embedding a CPE function as a router, =
no?
>=20
> Some clarification may be needed for a common understanding.
> In the DS-lite draft, we have, concerning the host-based architecture:
> "This architecture is targeted at new, large scale deployments of =
dual-stack capable devices implementing a dual-stack lite interface."
>=20
> I don't see why the stateless solution couldn't have a host-based =
variant "targeted at new, large scale deployments of dual-stack capable =
devices implementing" the CPE router function.
>=20
> Just saying "host-based models are out of scope" seems to me more =
negative than needed.
>=20
>=20
> The host-based DS-lite architecture is illustrated by:
> "              +-------------------+
>               |                   |
>               |  Host 192.0.0.2   |
>               |+--------+--------+|
>               ||        B4       ||
>               |+--------+--------+|
>               +--------|||--------+
>                        |||2001:db8:0:1::1
>                        |||
>                        |||<-IPv4-in-IPv6 softwire
>                        |||
>                 -------|||-------
>               /        |||        \
>              |   ISP core network  |
>               \        |||        /
>                 -------|||-------
>                        |||
>                        |||2001:db8:0:2::1
>               +--------|||--------+
>               |       AFTR        |
>               |+--------+--------+|
>               ||  Concentrator   ||
>               |+--------+--------+|
>               |       |NAT|       |
>               |       +-+-+       |
>               +---------|---------+
>                         |192.0.2.1
>                         |
>                 --------|--------
>               /         |         \
>              |       Internet      |
>               \         |         /
>                 --------|--------
>                         |
>                         |198.51.100.1
>                   +-----+-----+
>                   | IPv4 Host |
>                   +-----------+          "
>=20
> The host-based stateless-IPv4/IPv6 architecture can similarly be =
illustrated by.
> "              +-------------------+
>               |       Host        |
>               | RFC 1918 address  |
>               |+--------+--------+|
>               || Stateless v4/v6 ||
>               ||  CPE function   ||
>               || (incl. NAPT44)  ||
>               |+--------+--------+|
>               +--------|||--------+
>                        |||2001:db8:0:1::1
>                        |||
>                        |||<-IPv4-in-IPv6 stateless
>                        |||
>                 -------|||-------
>               /        |||        \
>              |   ISP core network  |
>               \        |||        /
>                 -------|||-------
>                        |||
>                        |||2001:db8:0:2::1=20
>               +--------|||--------+
>               |     Stateless     |
>               |    IPv4/IPv6      |
>               |  interconnection  |
>               |     function      |
>               +---------|---------+
>                         |192.0.2.1
>                         |
>                 --------|--------
>               /         |         \
>              |       Internet      |
>               \         |         /
>                 --------|--------
>                         |
>                         |198.51.100.1
>                   +-----+-----+
>                   | IPv4 Host |
>                   +-----------+          "
>=20
> Am I missing something?
>=20
> Regards,
> RD=20
>=20
>=20
>=20
>=20


From jacniq@gmail.com  Tue May 10 00:55:12 2011
Return-Path: <jacniq@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B0A3E0780 for <softwires@ietfa.amsl.com>; Tue, 10 May 2011 00:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.361
X-Spam-Level: 
X-Spam-Status: No, score=-3.361 tagged_above=-999 required=5 tests=[AWL=0.237,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSuAnBfCWQKJ for <softwires@ietfa.amsl.com>; Tue, 10 May 2011 00:55:11 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6B416E0686 for <softwires@ietf.org>; Tue, 10 May 2011 00:55:10 -0700 (PDT)
Received: by vws12 with SMTP id 12so405092vws.31 for <softwires@ietf.org>; Tue, 10 May 2011 00:55:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=eMnKaeQ44sCB94Xig6i7cR/LbD7ZDPSfU6jbD9x1nzw=; b=UYHNxBrQEZH2E8+Cv2iIJRYafxTN0rbU6hPJpWv3FFq8qk0uL01kB5OLkOUtNFmBO1 MGO5q94o5E9BWNmW5BbwF8ZjaeIQ1Bz51qZiGOw5EhdBDXxBx3LCfFQMxIeumjsRD8WG UmStpBXZBgrHBgIaBFnzGAQomy+UokUVoaceo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DlcQGKvga0c9ICB/1r2W06DcopcYDsd3/fB+vfx+5RW5sRNe4y0bLscHQx3zKntrqu VJIFwj+0z0ieOidGhDjHjghAy+xhAFRkp5QG27oVGCrbMaFzs7O6IyuRgVJafMWHSeYr e2t+WvVvuBEfJPgrlKVOUXXkbu3ezwhU6CtPg=
MIME-Version: 1.0
Received: by 10.52.68.202 with SMTP id y10mr6140017vdt.203.1305014110283; Tue, 10 May 2011 00:55:10 -0700 (PDT)
Received: by 10.52.186.227 with HTTP; Tue, 10 May 2011 00:55:10 -0700 (PDT)
In-Reply-To: <6BD5DE38-965B-4362-9700-9931B3E958C4@gmail.com>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <DFD2D5E7-C5EB-473C-933B-74A47D928654@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C8082EE@PUEXCB1B.nanterre.francetelecom.fr> <93E72D52-A316-4F86-867C-EC0045731BAF@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C808459@PUEXCB1B.nanterre.francetelecom.fr> <6BD5DE38-965B-4362-9700-9931B3E958C4@gmail.com>
Date: Tue, 10 May 2011 15:55:10 +0800
Message-ID: <BANLkTikFWbaa6Z3wFuVUfRWJPZFiekp8Hw@mail.gmail.com>
From: Jacni Qin <jacniq@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Content-Type: multipart/alternative; boundary=20cf307f324e78668a04a2e746f6
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2011 07:55:12 -0000

--20cf307f324e78668a04a2e746f6
Content-Type: text/plain; charset=ISO-8859-1

Re-,

Just to confirm it, only 4-4 and 6-6 are covered, no 4-6, right?


Cheers,
Jacni


On Tue, May 10, 2011 at 2:27 PM, Satoru Matsushima <
satoru.matsushima@gmail.com> wrote:

> Remi-san has simply pointed out that the service use case section of the
> draft assumes same implication in the ds-lite draft. I think that it would
> be no problem, and better to just remove the use case section, because the
> draft already expressed it as target space table in the introduction.
>
> Best regards,
> --satoru
>
>

--20cf307f324e78668a04a2e746f6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<font face=3D"verdana,sans-serif">Re-,<br><br>Just to confirm it, only 4-4 =
and 6-6 are covered, no 4-6, right?<br><br><br>Cheers,<br>Jacni<br><br></fo=
nt><br><div class=3D"gmail_quote">On Tue, May 10, 2011 at 2:27 PM, Satoru M=
atsushima <span dir=3D"ltr">&lt;<a href=3D"mailto:satoru.matsushima@gmail.c=
om">satoru.matsushima@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Remi-san has simply pointed out that the se=
rvice use case section of the draft assumes same implication in the ds-lite=
 draft. I think that it would be no problem, and better to just remove the =
use case section, because the draft already expressed it as target space ta=
ble in the introduction.<br>

<br>
Best regards,<br>
<font color=3D"#888888">--satoru<br>
</font><div><div></div><div class=3D"h5"><br>
</div></div></blockquote></div><br>

--20cf307f324e78668a04a2e746f6--

From satoru.matsushima@gmail.com  Tue May 10 00:58:22 2011
Return-Path: <satoru.matsushima@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C10FFE0780 for <softwires@ietfa.amsl.com>; Tue, 10 May 2011 00:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DF77NpJ+r5GN for <softwires@ietfa.amsl.com>; Tue, 10 May 2011 00:58:22 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id ECFD1E0686 for <softwires@ietf.org>; Tue, 10 May 2011 00:58:21 -0700 (PDT)
Received: by pwi5 with SMTP id 5so3669787pwi.31 for <softwires@ietf.org>; Tue, 10 May 2011 00:58:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=DqI5xlyVjVa42gg2gvW2zoLF55t92k8ByEtIfmwKBcQ=; b=cF2kbNL6UaYi/wvscPRczgyiA9Tjjow/eFnZuh/h9oBXOPEPBiW2mmXNwNgXoTf1aj JB80Oe8Jck9s3gTQHUj+/8ouZ/WMxGFvTXzVnhbh07PCifIGlBV/tqi/PzHRSbeDiCkd Rw7JNcILnVcoM4wrdejKXWYHHCcZKV1seJBI4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=rmJ51Vi5HxPgJC4fRQDKRiPrUAYrofahCGzPd8dgGaJ/pIUAAXXISzMUu4K9wBz1zg VrzJp01IamXY34QzjfomiTtB+0xbCoe6Hvstdwc0k/SAVAv+f9FUWdPcnUukoCEzjCoa n6gLjswvhSoZ1cKmnCs2Sy/UHsHwXVERanT8U=
Received: by 10.68.60.164 with SMTP id i4mr11680683pbr.0.1305014301659; Tue, 10 May 2011 00:58:21 -0700 (PDT)
Received: from [10.201.80.162] ([202.45.12.174]) by mx.google.com with ESMTPS id l7sm4651102pbo.44.2011.05.10.00.58.19 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 May 2011 00:58:20 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <BANLkTikFWbaa6Z3wFuVUfRWJPZFiekp8Hw@mail.gmail.com>
Date: Tue, 10 May 2011 16:58:17 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <01A42FF8-E45C-4022-BD7A-4A3A2D4DB95E@gmail.com>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <DFD2D5E7-C5EB-473C-933B-74A47D928654@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C8082EE@PUEXCB1B.nanterre.francetelecom.fr> <93E72D52-A316-4F86-867C-EC0045731BAF@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C808459@PUEXCB1B.nanterre.francetelecom.fr> <6BD5DE38-965B-4362-9700-9931B3E958C4@gmail.com> <BANLkTikFWbaa6Z3wFuVUfRWJPZFiekp8Hw@mail.gmail.com>
To: Jacni Qin <jacniq@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2011 07:58:22 -0000

Hi,

This is a draft submitted to softwires. Why not?

--satoru

On 2011/05/10, at 16:55, Jacni Qin wrote:

> Re-,
>=20
> Just to confirm it, only 4-4 and 6-6 are covered, no 4-6, right?
>=20
>=20
> Cheers,
> Jacni
>=20
>=20
> On Tue, May 10, 2011 at 2:27 PM, Satoru Matsushima =
<satoru.matsushima@gmail.com> wrote:
> Remi-san has simply pointed out that the service use case section of =
the draft assumes same implication in the ds-lite draft. I think that it =
would be no problem, and better to just remove the use case section, =
because the draft already expressed it as target space table in the =
introduction.
>=20
> Best regards,
> --satoru
>=20
>=20


From internet-drafts@ietf.org  Thu May 12 06:45:42 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF70E07C2; Thu, 12 May 2011 06:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bCv-Ddx6+3cc; Thu, 12 May 2011 06:45:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E030E07BF; Thu, 12 May 2011 06:45:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.54
Message-ID: <20110512134538.6742.90745.idtracker@ietfa.amsl.com>
Date: Thu, 12 May 2011 06:45:38 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-dual-stack-lite-09.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2011 13:45:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Softwires Working Group of the IETF.

	Title           : Dual-Stack Lite Broadband Deployments Following IPv4 Exh=
austion
	Author(s)       : Alain Durand
                          Ralph Droms
                          James Woodyatt
                          Yiu L. Lee
	Filename        : draft-ietf-softwire-dual-stack-lite-09.txt
	Pages           : 33
	Date            : 2011-05-12

   This document revisits the dual-stack model and introduces the Dual-
   Stack Lite technology aimed at better aligning the costs and benefits
   of deploying IPv6 in service provider networks.  Dual-Stack Lite
   enables a broadband service provider to share IPv4 addresses among
   customers by combining two well-known technologies: IP in IP (IPv4-
   in-IPv6) and Network Address Translation (NAT).


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-dual-stack-lite-09.=
txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-softwire-dual-stack-lite-09.t=
xt

From internet-drafts@ietf.org  Fri May 13 07:34:52 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F79E074F; Fri, 13 May 2011 07:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6azvxzFvWziT; Fri, 13 May 2011 07:34:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFD09E0675; Fri, 13 May 2011 07:34:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.54
Message-ID: <20110513143451.7685.7389.idtracker@ietfa.amsl.com>
Date: Fri, 13 May 2011 07:34:51 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-dual-stack-lite-10.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2011 14:34:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Softwires Working Group of the IETF.

	Title           : Dual-Stack Lite Broadband Deployments Following IPv4 Exh=
austion
	Author(s)       : Alain Durand
                          Ralph Droms
                          James Woodyatt
                          Yiu L. Lee
	Filename        : draft-ietf-softwire-dual-stack-lite-10.txt
	Pages           : 33
	Date            : 2011-05-13

   This document revisits the dual-stack model and introduces the Dual-
   Stack Lite technology aimed at better aligning the costs and benefits
   of deploying IPv6 in service provider networks.  Dual-Stack Lite
   enables a broadband service provider to share IPv4 addresses among
   customers by combining two well-known technologies: IP in IP (IPv4-
   in-IPv6) and Network Address Translation (NAT).


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-dual-stack-lite-10.=
txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-softwire-dual-stack-lite-10.t=
xt

From phdgang@gmail.com  Sun May 15 04:30:54 2011
Return-Path: <phdgang@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D89D7E069A for <softwires@ietfa.amsl.com>; Sun, 15 May 2011 04:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiTDqY8mltNx for <softwires@ietfa.amsl.com>; Sun, 15 May 2011 04:30:54 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 78BFEE067B for <softwires@ietf.org>; Sun, 15 May 2011 04:30:54 -0700 (PDT)
Received: by pzk5 with SMTP id 5so2434012pzk.31 for <softwires@ietf.org>; Sun, 15 May 2011 04:30:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=M71sjwTwyqFBAo+AUcnYCPwWOU9/Tek/XjxKNjRkn74=; b=w4nQP5lPzDlA3b6tQIQmCTT3VrOrps7vr4vAd0EKHQ+cdFLNDEPyqi2Yy43P75Wve1 WFB8CGbzUEmGtKYTT7SWTlVYHwg2EjFeAzv+vW5Niyv1jNJyR3C8CNCYzmtRDVWA2noK shgdIR2AXCPAfAVqHmMeexnm27d9ObmsXFm8s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=rDceFB2pitqdqIKKSFXQJ2MeIC27Y+BamtDfautMxMO+D5cnNnDWDoQ4zG0zD1+0WQ 74nLODRIyIIrBq/Eq5AqLCAOxmRhen1t6suaAmj5xJkKLJx3QhiXq78j1EPpB37vNptr lSggocKgWiz8zQAJ6KXhwX3b4kmmxOMXbysWE=
MIME-Version: 1.0
Received: by 10.68.7.167 with SMTP id k7mr5203471pba.238.1305459053933; Sun, 15 May 2011 04:30:53 -0700 (PDT)
Received: by 10.68.71.136 with HTTP; Sun, 15 May 2011 04:30:53 -0700 (PDT)
Date: Sun, 15 May 2011 19:30:53 +0800
Message-ID: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: softwires@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Softwires]  Motivation Analysis for 4via6 Stateless Solutions
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2011 11:30:54 -0000

Dear all,

Last IETF meeting, ADs required volunteers to draft the motivation for
stateless 4via6 mechanism.
We have updated a draft to state the motivation mostly from
operational perspectives.
We believe the concrete solution shall be decided by business
requirements, so it is essential to analyze 4via6 motivations from
network operations.

Please find the draft from the below link:
http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.txt

Any comments are welcome.
Many thanks

Gang

From tena@huawei.com  Tue May 17 19:20:34 2011
Return-Path: <tena@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC06AE06E2 for <softwires@ietfa.amsl.com>; Tue, 17 May 2011 19:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dltrRfxyTF0C for <softwires@ietfa.amsl.com>; Tue, 17 May 2011 19:20:34 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by ietfa.amsl.com (Postfix) with ESMTP id E329FE0696 for <softwires@ietf.org>; Tue, 17 May 2011 19:20:33 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LLD0076HD6802@usaga04-in.huawei.com> for softwires@ietf.org; Tue, 17 May 2011 21:20:33 -0500 (CDT)
Received: from TingZousc1 ([10.193.34.188]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LLD004SBD66P1@usaga04-in.huawei.com> for softwires@ietf.org; Tue, 17 May 2011 21:20:32 -0500 (CDT)
Date: Tue, 17 May 2011 19:20:31 -0700
From: Tina Tsou <tena@huawei.com>
In-reply-to: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com>
To: 'GangChen' <phdgang@gmail.com>, softwires@ietf.org
Message-id: <00b001cc1502$2a3d4c80$7eb7e580$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcwS85ab5l23EV2wQpahjhG4nBwxOgCDjAdA
References: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com>
Subject: Re: [Softwires] Motivation Analysis for 4via6 Stateless Solutions
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2011 02:20:35 -0000

Hi Gang,
I read the draft. It is clear from an operator's analysis. It provides
another angle from the operational point of view.


We keep our promises with one another - no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html


-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of GangChen
Sent: Sunday, May 15, 2011 4:31 AM
To: softwires@ietf.org
Subject: [Softwires] Motivation Analysis for 4via6 Stateless Solutions

Dear all,

Last IETF meeting, ADs required volunteers to draft the motivation for
stateless 4via6 mechanism.
We have updated a draft to state the motivation mostly from
operational perspectives.
We believe the concrete solution shall be decided by business
requirements, so it is essential to analyze 4via6 motivations from
network operations.

Please find the draft from the below link:
http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.tx
t

Any comments are welcome.
Many thanks

Gang
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires


From fy@huawei.com  Tue May 17 20:22:26 2011
Return-Path: <fy@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8AF2E0681 for <softwires@ietfa.amsl.com>; Tue, 17 May 2011 20:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oqdCysszAcdN for <softwires@ietfa.amsl.com>; Tue, 17 May 2011 20:22:26 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0C264E064E for <softwires@ietf.org>; Tue, 17 May 2011 20:22:26 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LLD0090LG0QFF@szxga03-in.huawei.com> for softwires@ietf.org; Wed, 18 May 2011 11:22:02 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LLD004VFG0QQM@szxga03-in.huawei.com> for softwires@ietf.org; Wed, 18 May 2011 11:22:02 +0800 (CST)
Received: from F00171927 ([10.110.98.70]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LLD00KUJG0QH5@szxml06-in.huawei.com> for softwires@ietf.org; Wed, 18 May 2011 11:22:02 +0800 (CST)
Date: Wed, 18 May 2011 11:22:02 +0800
From: fuyu <fy@huawei.com>
In-reply-to: <mailman.47.1305486007.13446.softwires@ietf.org>
To: softwires@ietf.org, phdgang@gmail.com
Message-id: <003a01cc150a$c169bb90$443d32b0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=Windows-1252
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcwTMmrrr5IPuoDlQMeOZTr+FXkHsAB1bGDw
References: <mailman.47.1305486007.13446.softwires@ietf.org>
Subject: Re: [Softwires] Motivation Analysis for 4via6 Stateless
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2011 03:22:27 -0000

Hi Gang,

I think this draft is useful. 

It discusses some motivations for 4via6 stateless solution from the
operator's view.  
Some operational considerations for seeking solution during the IPv6
transition period is also include in this draft.

Best regards

YU


----------------------------------------------------------------------

Message: 1
Date: Sun, 15 May 2011 19:30:53 +0800
From: GangChen <phdgang@gmail.com>
To: softwires@ietf.org
Subject: [Softwires]  Motivation Analysis for 4via6 Stateless
	Solutions
Message-ID: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Dear all,

Last IETF meeting, ADs required volunteers to draft the motivation for
stateless 4via6 mechanism.
We have updated a draft to state the motivation mostly from
operational perspectives.
We believe the concrete solution shall be decided by business
requirements, so it is essential to analyze 4via6 motivations from
network operations.

Please find the draft from the below link:
http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.tx
t

Any comments are welcome.
Many thanks

Gang


------------------------------

_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires


End of Softwires Digest, Vol 66, Issue 11
*****************************************


From ma.gaofeng@zte.com.cn  Wed May 18 03:14:21 2011
Return-Path: <ma.gaofeng@zte.com.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9797AE0736 for <softwires@ietfa.amsl.com>; Wed, 18 May 2011 03:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oFf-N2wCL67z for <softwires@ietfa.amsl.com>; Wed, 18 May 2011 03:14:20 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 5D450E0724 for <softwires@ietf.org>; Wed, 18 May 2011 03:14:20 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 1834271095904; Wed, 18 May 2011 18:07:50 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 17487.271095904; Wed, 18 May 2011 17:48:22 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p4I9mPe8097062 for <softwires@ietf.org>; Wed, 18 May 2011 17:48:25 +0800 (GMT-8) (envelope-from ma.gaofeng@zte.com.cn)
To: softwires@ietf.org
MIME-Version: 1.0
X-KeepSent: 570D96EC:234ACD89-48257894:0035274D; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF570D96EC.234ACD89-ON48257894.0035274D-48257894.0035DFAA@zte.com.cn>
From: ma.gaofeng@zte.com.cn
Date: Wed, 18 May 2011 17:48:04 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-05-18 17:48:27, Serialize complete at 2011-05-18 17:48:27
Content-Type: multipart/alternative; boundary="=_alternative 0035DFA648257894_="
X-MAIL: mse01.zte.com.cn p4I9mPe8097062
Subject: Re: [Softwires] Motivation Analysis for 4via6 Stateless Solutions
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2011 10:14:21 -0000

This is a multipart message in MIME format.
--=_alternative 0035DFA648257894_=
Content-Type: text/plain; charset="US-ASCII"

Hi ,Gang
 
 I read through the draft. It's   great  to understand 4via6 motivations 
from operational views. 

Thanks,Best Regards 
Gaofeng

-----Original Message-----
From: softwires-bounces at ietf.org [mailto:softwires-bounces at ietf.org] 
On
Behalf Of GangChen
Sent: Sunday, May 15, 2011 4:31 AM
To: softwires at ietf.org
Subject: [Softwires] Motivation Analysis for 4via6 Stateless Solutions

Dear all,

Last IETF meeting, ADs required volunteers to draft the motivation for
stateless 4via6 mechanism.
We have updated a draft to state the motivation mostly from
operational perspectives.
We believe the concrete solution shall be decided by business
requirements, so it is essential to analyze 4via6 motivations from
network operations.

Please find the draft from the below link:
http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.tx

t

Any comments are welcome.
Many thanks

Gang
_______________________________________________
Softwires mailing list
Softwires at ietf.org
https://www.ietf.org/mailman/listinfo/softwires



--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 0035DFA648257894_=
Content-Type: text/html; charset="US-ASCII"


<div>
<br><font size=2 face="Times New Roman">Hi ,Gang</font>
<br><font size=2 face="Times New Roman">&nbsp; </font>
<br><font size=2 face="Times New Roman">&nbsp;I read through the draft.
It's &nbsp; great &nbsp;to understand 4via6 motivations from operational
views. </font>
<br>
<br><font size=2 face="Times New Roman">Thanks,Best Regards </font>
<br><font size=2 face="Times New Roman">Gaofeng</font>
<br>
<br><tt><font size=3>-----Original Message-----<br>
From: softwires-bounces at ietf.org [</font></tt><a href="mailto:softwires-bounces"><tt><font size=3 color=blue><u>mailto:softwires-bounces</u></font></tt></a><tt><font size=3>
at ietf.org] On<br>
Behalf Of GangChen<br>
Sent: Sunday, May 15, 2011 4:31 AM<br>
To: softwires at ietf.org<br>
Subject: [Softwires] Motivation Analysis for 4via6 Stateless Solutions<br>
<br>
Dear all,<br>
<br>
Last IETF meeting, ADs required volunteers to draft the motivation for<br>
stateless 4via6 mechanism.<br>
We have updated a draft to state the motivation mostly from<br>
operational perspectives.<br>
We believe the concrete solution shall be decided by business<br>
requirements, so it is essential to analyze 4via6 motivations from<br>
network operations.<br>
<br>
Please find the draft from the below link:<br>
</font></tt><a href="http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.tx"><tt><font size=3 color=blue><u>http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.tx</u></font></tt></a><tt><font size=3><br>
t<br>
<br>
Any comments are welcome.<br>
Many thanks<br>
<br>
Gang<br>
_______________________________________________<br>
Softwires mailing list<br>
Softwires at ietf.org<br>
</font></tt><a href=https://www.ietf.org/mailman/listinfo/softwires><tt><font size=3 color=blue><u>https://www.ietf.org/mailman/listinfo/softwires</u></font></tt></a><tt><font size=3><br>
<br>
</font></tt></div><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 0035DFA648257894_=--


From behcetsarikaya@yahoo.com  Mon May 23 09:20:38 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42317E0776 for <softwires@ietfa.amsl.com>; Mon, 23 May 2011 09:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[AWL=-0.999, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6myTcqHH3lJ for <softwires@ietfa.amsl.com>; Mon, 23 May 2011 09:20:37 -0700 (PDT)
Received: from nm15.bullet.mail.sp2.yahoo.com (nm15.bullet.mail.sp2.yahoo.com [98.139.91.85]) by ietfa.amsl.com (Postfix) with SMTP id 99B7BE0679 for <softwires@ietf.org>; Mon, 23 May 2011 09:20:37 -0700 (PDT)
Received: from [98.139.91.62] by nm15.bullet.mail.sp2.yahoo.com with NNFMP; 23 May 2011 16:20:33 -0000
Received: from [98.139.91.21] by tm2.bullet.mail.sp2.yahoo.com with NNFMP; 23 May 2011 16:20:33 -0000
Received: from [127.0.0.1] by omp1021.mail.sp2.yahoo.com with NNFMP; 23 May 2011 16:20:33 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 874748.87992.bm@omp1021.mail.sp2.yahoo.com
Received: (qmail 22933 invoked by uid 60001); 23 May 2011 16:20:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1306167633; bh=FbXRVhN1db8cYOnTICpuJTCNG8ZvjGVpPJfk+DKDVoo=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=NGw8Vqt0qrWgNJgLpdMWfr9Mh1AcTA1u9S95knjztGWS8sF32tqC8BIAd9HlgHDgApaeEz+NUDHayyECW2csDrNqGws+mzcho4N3OFfCYUU9WSUMr1kLGI9SHiPzAliceCt1OxKkiqpyf1r/DqEO+QUnJ0OxX5enfBAuZgW1mbs=
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:In-Reply-To:MIME-Version:Content-Type; b=sSvN6Cz27FUNKITEiLsSDmqLvNaXRUcE8Y60xRdGvyLtfezkk8wguKtggNfH19D/1TpjaPqMm9/lgZnmCVLowYdV5x8sIW0SaXdTSR+RjfLuuEwTArli6RHciY5MzyZQUnPGAGCUvL53afGoYVC85uU4Z88zbgQYQj4eFIYdTkg=;
Message-ID: <265164.67718.qm@web111411.mail.gq1.yahoo.com>
X-YMail-OSG: w_NwFNoVM1kJO2LcfL0M3TiZNePomzMhk_QcRm43P0A6mPe 1QWwQ40YxejT2LbobyK_1yLLwFrxnC6qth1FYUj8SHNyle2CPAHOd4NpaPtY ZodSTWiIZNJmfgf55ayeiLD9sAfoCfvTN4esgvtrNx7lPbrqLoXjoMtdpNY0 Tq1LcF9XhQAtQqMnwTrRmAISWU8lFp.b60X5tMPTxzQQHayHIQtijx7VcdXc 4DSOS5Y0ybacoW0XH1CLjL04nG4qtTTu40uyak0WiHEtnV5NZmNulJZG_5PX bNhCiQavLBl8bOEHEjtDSOx_8z.w7JWiTtZ1Djrv9jvXPgrcWdXilYGzumDs vaoC3HhX_LaWUsMoA.K4Oo3EF1puCtGBk7HC7NFBZlLL4b4yG2WSCVMyrBbL n3if9R0M9w4ukhA--
Received: from [206.16.17.212] by web111411.mail.gq1.yahoo.com via HTTP; Mon, 23 May 2011 09:20:33 PDT
X-Mailer: YahooMailRC/567 YahooMailWebService/0.8.111.303096
References: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com>
Date: Mon, 23 May 2011 09:20:33 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: GangChen <phdgang@gmail.com>, softwires@ietf.org
In-Reply-To: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [Softwires] Motivation Analysis for 4via6 Stateless Solutions
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2011 16:20:38 -0000

I support this draft.

Having said that I saw 
draft-operators-softwire-stateless-4v6-motivation-01

which covers very similar scenarios.

I suggest the authors work together and possibly merge their documents.

Regards,

Behcet


> Dear all,
> 
> Last IETF meeting, ADs required volunteers to draft the  motivation for
> stateless 4via6 mechanism.
> We have updated a draft to state  the motivation mostly from
> operational perspectives.
> We believe the  concrete solution shall be decided by business
> requirements, so it is  essential to analyze 4via6 motivations from
> network operations.
> 
> Please  find the draft from the below  link:
> http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.txt
> 
> Any  comments are welcome.
> Many  thanks
> 
> Gang
> _______________________________________________
> Softwires  mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
> 

From ichiroumakino@gmail.com  Tue May 24 01:24:02 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79BF9E06EE for <softwires@ietfa.amsl.com>; Tue, 24 May 2011 01:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Snyx6eJgQmYi for <softwires@ietfa.amsl.com>; Tue, 24 May 2011 01:24:02 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id A9398E0675 for <softwires@ietf.org>; Tue, 24 May 2011 01:24:01 -0700 (PDT)
Received: by bwz13 with SMTP id 13so6263433bwz.31 for <softwires@ietf.org>; Tue, 24 May 2011 01:24:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=qEK+lK2XfTJml0b83m53sFveFdJ4IbxGh65rcOq8KHI=; b=PnudObc2LfxeSlhlsAYy/+ZwrUoeEiV4XpDsopqaw47v7Dre+upFUQcTKCdEruHkIV tNvdDpjRbvY43/jS6pr+aV0Fj6HXx/1ueJXiPBP/XDv//2A7UaIJNBEVQfWZEv32HK9Y yaNx2xbY45Zo9FAYvLr4Yme8Cd6rNdrHbnFtI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=s2XZtw8hD1b05zf1NEaL32uw6tn/bUUHc4Zzfg4wSQAfZw9QuDEnXNzwEtzQthkMOJ zDJ1jq/nUBajcT/d+CVt2ukR69RYwgQ3WNmr221WWdwCETbZRedZoXRIRcZMvpWnAoQQ Y2Bw4UiUGJS+0+DY6XZt4rSRgAvvfq2fstUu8=
Received: by 10.204.46.98 with SMTP id i34mr2748684bkf.95.1306225439923; Tue, 24 May 2011 01:23:59 -0700 (PDT)
Received: from ams3-vpn-dhcp4890.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id d34sm320802bks.3.2011.05.24.01.23.58 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2011 01:23:59 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <265164.67718.qm@web111411.mail.gq1.yahoo.com>
Date: Tue, 24 May 2011 10:23:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C19A921-B086-4893-AC06-6E213AE85031@employees.org>
References: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com> <265164.67718.qm@web111411.mail.gq1.yahoo.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
X-Mailer: Apple Mail (2.1084)
Cc: softwires@ietf.org
Subject: Re: [Softwires] Motivation Analysis for 4via6 Stateless Solutions
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2011 08:24:02 -0000

> Having said that I saw=20
> draft-operators-softwire-stateless-4v6-motivation-01
>=20
> which covers very similar scenarios.
>=20
> I suggest the authors work together and possibly merge their =
documents.

+1.

I would suggest incorporating the motivational parts of this document =
into stateless-4v6-motivation and the stateless issues part of the draft =
into draft-dec-stateless-4v6-01

one motivation analysis document is enough.

cheers,
Ole

>=20
>> Dear all,
>>=20
>> Last IETF meeting, ADs required volunteers to draft the  motivation =
for
>> stateless 4via6 mechanism.
>> We have updated a draft to state  the motivation mostly from
>> operational perspectives.
>> We believe the  concrete solution shall be decided by business
>> requirements, so it is  essential to analyze 4via6 motivations from
>> network operations.
>>=20
>> Please  find the draft from the below  link:
>> =
http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.=
txt
>>=20
>> Any  comments are welcome.
>> Many  thanks
>>=20
>> Gang
>> _______________________________________________
>> Softwires  mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From mark@townsley.net  Tue May 24 01:35:34 2011
Return-Path: <mark@townsley.net>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0BD3E06D4 for <softwires@ietfa.amsl.com>; Tue, 24 May 2011 01:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.902
X-Spam-Level: 
X-Spam-Status: No, score=-2.902 tagged_above=-999 required=5 tests=[AWL=0.698,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKsuQga6hW5J for <softwires@ietfa.amsl.com>; Tue, 24 May 2011 01:35:34 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id D9529E06C2 for <softwires@ietf.org>; Tue, 24 May 2011 01:35:33 -0700 (PDT)
Received: by bwz13 with SMTP id 13so6272095bwz.31 for <softwires@ietf.org>; Tue, 24 May 2011 01:35:32 -0700 (PDT)
Received: by 10.204.38.88 with SMTP id a24mr2829825bke.130.1306226132638; Tue, 24 May 2011 01:35:32 -0700 (PDT)
Received: from ams-townsley-8716.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id l1sm4394882bkl.1.2011.05.24.01.35.28 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2011 01:35:29 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <9C19A921-B086-4893-AC06-6E213AE85031@employees.org>
Date: Tue, 24 May 2011 10:35:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <156B213D-54C6-4317-9E36-201ABD9702F7@townsley.net>
References: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com> <265164.67718.qm@web111411.mail.gq1.yahoo.com> <9C19A921-B086-4893-AC06-6E213AE85031@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: softwires@ietf.org
Subject: Re: [Softwires] Motivation Analysis for 4via6 Stateless Solutions
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2011 08:35:34 -0000

On May 24, 2011, at 10:23 AM, Ole Troan wrote:

>> Having said that I saw=20
>> draft-operators-softwire-stateless-4v6-motivation-01
>>=20
>> which covers very similar scenarios.
>>=20
>> I suggest the authors work together and possibly merge their =
documents.
>=20
> +1.
>=20
> I would suggest incorporating the motivational parts of this document =
into stateless-4v6-motivation and the stateless issues part of the draft =
into draft-dec-stateless-4v6-01

Excellent idea.=20

> one motivation analysis document is enough.

One is already more than enough. So, yes, let's absolutely avoid having =
two.

- Mark

>=20
> cheers,
> Ole
>=20
>>=20
>>> Dear all,
>>>=20
>>> Last IETF meeting, ADs required volunteers to draft the  motivation =
for
>>> stateless 4via6 mechanism.
>>> We have updated a draft to state  the motivation mostly from
>>> operational perspectives.
>>> We believe the  concrete solution shall be decided by business
>>> requirements, so it is  essential to analyze 4via6 motivations from
>>> network operations.
>>>=20
>>> Please  find the draft from the below  link:
>>> =
http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.=
txt
>>>=20
>>> Any  comments are welcome.
>>> Many  thanks
>>>=20
>>> Gang
>>> _______________________________________________
>>> Softwires  mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From phdgang@gmail.com  Tue May 24 10:07:46 2011
Return-Path: <phdgang@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3751E073D for <softwires@ietfa.amsl.com>; Tue, 24 May 2011 10:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKEDgVBOYkOc for <softwires@ietfa.amsl.com>; Tue, 24 May 2011 10:07:46 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF75E073C for <softwires@ietf.org>; Tue, 24 May 2011 10:07:46 -0700 (PDT)
Received: by gyf3 with SMTP id 3so3355951gyf.31 for <softwires@ietf.org>; Tue, 24 May 2011 10:07:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=a+nuYjAteb7Nix3lDFJGYulKxe9CBJhOymtfUqNoqFA=; b=SKchGONlfOZ8aWg3so/R2mPAO5qfLErlEYp/CmRRTPoOSd/3t/woucIw1/v6xlFfUh Z8QJfBwRvQ/pimtja3fpIkjWb6eII7ZWjZNeIG3sbvxOqlogoeE6wbIwngPpFpAz2rHN yiz5JWArtI9LXEl8SKKCB/RZtCEf/elzMRFxo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QYLCheh3qzUr8urVh3FS9rGFf0GGAq3llJOCeOPZbrGLLmzmndwE2hGHpK55e000wC 7iroIVwFySrB+H4XbfYItmErSorTi8OCXCdIsDqY70Z74/LDdLIAByPNb1B2bhynq+tr my7SENCiENBNSdaYRHaA6s3LngtXY9TE0ulYc=
MIME-Version: 1.0
Received: by 10.151.79.14 with SMTP id g14mr4191659ybl.187.1306256865758; Tue, 24 May 2011 10:07:45 -0700 (PDT)
Received: by 10.151.107.13 with HTTP; Tue, 24 May 2011 10:07:45 -0700 (PDT)
In-Reply-To: <9C19A921-B086-4893-AC06-6E213AE85031@employees.org>
References: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com> <265164.67718.qm@web111411.mail.gq1.yahoo.com> <9C19A921-B086-4893-AC06-6E213AE85031@employees.org>
Date: Wed, 25 May 2011 01:07:45 +0800
Message-ID: <BANLkTinDY5zrCPSfqF+sqcg12UsuoQ85Tg@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: softwires@ietf.org
Subject: Re: [Softwires] Motivation Analysis for 4via6 Stateless Solutions
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2011 17:07:47 -0000

2011/5/24, Ole Troan <otroan@employees.org>:
>
> I would suggest incorporating the motivational parts of this document into
> stateless-4v6-motivation

If we are supposed to converge these two drafts, the below is my
proposal to reorganize the draft

1. Introduction

2. Operational Motivations Analysis

2.1 Improving Network Efficiency
Note: This section states the benefits for off-loading traffic
processing,  e.g. reduction of logging information, efficient
transmission of data packages, etc..

2.1.1 NAT Logging Consideration
2.1.2 Avoiding Centralized Traffic Bottleneck
2.1.3 Optimizing Encap/Decap and Translation
2.1.4 xxxxx

2.2 Simplifying Network Maintenance

Note: This section states the consideration for reducing subsequent
efforts of network maintenance.

2.2.1 High Availability(HA) Consideration
2.2.2 Relief Qualification Procedures
2.2.3 xxxxx

2.3 Decreasing Transition costs
Note: This section makes costs comparison analysis.
2.3.1 Transition Costs Consideration

2.4 Facilitating Service Evolution
Note: This section states the cooperation between stateless 4via6 and
service provisioning, e.g. the subsection "Implicit Host
Identification" and "No Organizational Impact" in
draft-operators-softwire-stateless-4v6-motivation-01.
2.4.1 xxxx
2.4.2 xxxx

3 Conclusions
Note: I suggest to give the explicit conclusion, which approach is
preferred and which has high-priority considering particular demands
from operators.


> and the stateless issues part of the draft into draft-dec-stateless-4v6-01

I support this idea.

From tetsuya@ipinfusion.com  Wed May 25 01:22:26 2011
Return-Path: <tetsuya@ipinfusion.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6007E06F0 for <softwires@ietfa.amsl.com>; Wed, 25 May 2011 01:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.691
X-Spam-Level: 
X-Spam-Status: No, score=-1.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUXRfq4EQBOW for <softwires@ietfa.amsl.com>; Wed, 25 May 2011 01:22:26 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2891CE06D5 for <softwires@ietf.org>; Wed, 25 May 2011 01:22:26 -0700 (PDT)
Received: by pzk5 with SMTP id 5so4418592pzk.31 for <softwires@ietf.org>; Wed, 25 May 2011 01:22:25 -0700 (PDT)
Received: by 10.68.21.231 with SMTP id y7mr3378114pbe.493.1306311745569; Wed, 25 May 2011 01:22:25 -0700 (PDT)
Received: from [192.168.1.106] (EM1-112-122-22.pool.e-mobile.ne.jp [1.112.122.22]) by mx.google.com with ESMTPS id i9sm5539037pbd.38.2011.05.25.01.22.21 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 May 2011 01:22:23 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Tetsuya Murakami <tetsuya@ipinfusion.com>
In-Reply-To: <9C19A921-B086-4893-AC06-6E213AE85031@employees.org>
Date: Wed, 25 May 2011 01:22:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C99C80F-7791-44D0-B868-97A33CB64FE9@ipinfusion.com>
References: <BANLkTi=URC1w97fC9K5vw0WEGYYkKmLWBA@mail.gmail.com> <265164.67718.qm@web111411.mail.gq1.yahoo.com> <9C19A921-B086-4893-AC06-6E213AE85031@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: softwires@ietf.org
Subject: Re: [Softwires] Motivation Analysis for 4via6 Stateless Solutions
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2011 08:22:27 -0000

Hi,=20

+1.
One motivation draft should be fine.

On 2011/05/24, at 1:23, Ole Troan wrote:

>> Having said that I saw=20
>> draft-operators-softwire-stateless-4v6-motivation-01
>>=20
>> which covers very similar scenarios.
>>=20
>> I suggest the authors work together and possibly merge their =
documents.
>=20
> +1.
>=20
> I would suggest incorporating the motivational parts of this document =
into stateless-4v6-motivation and the stateless issues part of the draft =
into draft-dec-stateless-4v6-01
>=20
> one motivation analysis document is enough.
>=20
> cheers,
> Ole
>=20
>>=20
>>> Dear all,
>>>=20
>>> Last IETF meeting, ADs required volunteers to draft the  motivation =
for
>>> stateless 4via6 mechanism.
>>> We have updated a draft to state  the motivation mostly from
>>> operational perspectives.
>>> We believe the  concrete solution shall be decided by business
>>> requirements, so it is  essential to analyze 4via6 motivations from
>>> network operations.
>>>=20
>>> Please  find the draft from the below  link:
>>> =
http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-motivation-00.=
txt
>>>=20
>>> Any  comments are welcome.
>>> Many  thanks
>>>=20
>>> Gang
>>> _______________________________________________
>>> Softwires  mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From ichiroumakino@gmail.com  Thu May 26 01:36:21 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0E3E06B7 for <softwires@ietfa.amsl.com>; Thu, 26 May 2011 01:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jJ0qLPb8YKnS for <softwires@ietfa.amsl.com>; Thu, 26 May 2011 01:36:20 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3D27AE067B for <softwires@ietf.org>; Thu, 26 May 2011 01:36:20 -0700 (PDT)
Received: by wyb29 with SMTP id 29so353942wyb.31 for <softwires@ietf.org>; Thu, 26 May 2011 01:36:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=i6LN1XJe5ImlTjIZGXCYBEk+2BETyRfpFkYGE725OfQ=; b=FNSC6X6PiU+riuvGXvkKOmljnugczYlLdlBIRgQTfKZjkjYZcUtubVS8xRcN2jAcMD LitIkiVyl/2mAdltPFWqf3kgNR7Ahuj5OzHRjSBfhZPM6Bn7LHpFixEWqVPFi6UOnGhD PQv7IjO2+5cIkV7yl93k6Q5nBWgaSuyEKvzCE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=FgRS56xAl88RjC9FGBX/7JjChcWrsVseClirSt9qXhGZkR0Dce3UAtYkbmjUnc3T/r 009qUzuFJLcaGn/DeFu3B8x20ETvdXyYIVJGZLve5riRB9196T2UzUIroeLxvFaAA3kr VOYm6jYrUZuoRofuZKX/hxmhV03GRi1k5CwSU=
Received: by 10.227.11.143 with SMTP id t15mr543618wbt.56.1306398979384; Thu, 26 May 2011 01:36:19 -0700 (PDT)
Received: from dhcp-osl-vl300-64-103-53-213.cisco.com (dhcp-osl-vl300-64-103-53-213.cisco.com [64.103.53.213]) by mx.google.com with ESMTPS id et5sm304012wbb.50.2011.05.26.01.36.15 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 May 2011 01:36:16 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr>
Date: Thu, 26 May 2011 10:36:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr>
To: <mohamed.boucadair@orange-ftgroup.com> <mohamed.boucadair@orange-ftgroup.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 08:36:21 -0000

I like the draft and I think it covers the motivational points well.

as a general comment, I do think the document is too wordy. could the =
authors make the next revision terser or do you want me to propose text =
changes?

I would also suggest that you reference the sections in rfc1958 on =
state.
we don't have a good success record in gleaning state in the middle of =
the network (NAT, N:1 VLANs, DHCP...), since the protocols we 'glean' =
from aren't designed to maintain softstate in the network.

I see no reason why this document shouldn't be adopted as a working =
group document immediately.

cheers,
Ole=

From mark@townsley.net  Thu May 26 02:42:03 2011
Return-Path: <mark@townsley.net>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2D6DE0671 for <softwires@ietfa.amsl.com>; Thu, 26 May 2011 02:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.134
X-Spam-Level: 
X-Spam-Status: No, score=-3.134 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cX11L8vr-ZUO for <softwires@ietfa.amsl.com>; Thu, 26 May 2011 02:42:02 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 28F4EE0664 for <softwires@ietf.org>; Thu, 26 May 2011 02:42:01 -0700 (PDT)
Received: by wyb29 with SMTP id 29so400756wyb.31 for <softwires@ietf.org>; Thu, 26 May 2011 02:42:01 -0700 (PDT)
Received: by 10.227.196.209 with SMTP id eh17mr599524wbb.92.1306402920863; Thu, 26 May 2011 02:42:00 -0700 (PDT)
Received: from ams-townsley-8716.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id 14sm339113wbw.32.2011.05.26.02.41.58 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 May 2011 02:41:59 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org>
Date: Thu, 26 May 2011 11:41:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E0C1043-C98C-497E-ADA8-200C6FF43AF6@townsley.net>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 09:42:03 -0000

On May 26, 2011, at 10:36 AM, Ole Troan wrote:

> I like the draft and I think it covers the motivational points well.
>=20
> as a general comment, I do think the document is too wordy. could the =
authors make the next revision terser or do you want me to propose text =
changes?
>=20
> I would also suggest that you reference the sections in rfc1958 on =
state.
> we don't have a good success record in gleaning state in the middle of =
the network (NAT, N:1 VLANs, DHCP...), since the protocols we 'glean' =
from aren't designed to maintain softstate in the network.
>=20
> I see no reason why this document shouldn't be adopted as a working =
group document immediately.

I support this becoming a WG document, and agree with Ole that the next =
version should cut back on text. We want to give the IESG something as =
clear and concise as possible.

If there is reasonable consensus (not that the document is complete, but =
that it will be the basis for the final document), all it takes is an OK =
by the chairs and a submission by the authors with the WG title.=20

- Mark=20

>=20
> cheers,
> Ole
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From mohamed.boucadair@orange-ftgroup.com  Thu May 26 04:25:16 2011
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41573E06DC for <softwires@ietfa.amsl.com>; Thu, 26 May 2011 04:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OB3BCLRZSvYi for <softwires@ietfa.amsl.com>; Thu, 26 May 2011 04:25:15 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id 711DEE06D9 for <softwires@ietf.org>; Thu, 26 May 2011 04:25:15 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id 12C0FC0548; Thu, 26 May 2011 13:25:14 +0200 (CEST)
Received: from PUEXCH11.nanterre.francetelecom.fr (unknown [10.101.44.27]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id CF1D5384066; Thu, 26 May 2011 13:25:13 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH11.nanterre.francetelecom.fr ([10.101.44.27]) with mapi; Thu, 26 May 2011 13:25:13 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: Ole Troan <otroan@employees.org>
Date: Thu, 26 May 2011 13:25:12 +0200
Thread-Topic: [Softwires] Motivation draft for stateless v4 over v6 solution
Thread-Index: Acwbf/yvaIXVKua7QwelPBeWvnCf6AAFrS7A
Message-ID: <94C682931C08B048B7A8645303FDC9F33E4E407A32@PUEXCB1B.nanterre.francetelecom.fr>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org>
In-Reply-To: <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.26.104515
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 11:25:16 -0000

Dear Ole,

For sure, the text can be shortened whenever possible.=20

If you point me to sections you think it need to be re-worded, this would b=
e appreciated.

Thank you.

Cheers,
Med=20

-----Message d'origine-----
De : Ole Troan [mailto:ichiroumakino@gmail.com] De la part de Ole Troan
Envoy=E9 : jeudi 26 mai 2011 10:36
=C0 : BOUCADAIR Mohamed OLNC/NAD/TIP
Cc : R=E9mi Despr=E9s; Satoru Matsushima; Yiu Lee; Olaf Bonness; Isabel Bor=
ges; Softwires-wg
Objet : Re: [Softwires] Motivation draft for stateless v4 over v6 solution

I like the draft and I think it covers the motivational points well.

as a general comment, I do think the document is too wordy. could the autho=
rs make the next revision terser or do you want me to propose text changes?

I would also suggest that you reference the sections in rfc1958 on state.
we don't have a good success record in gleaning state in the middle of the =
network (NAT, N:1 VLANs, DHCP...), since the protocols we 'glean' from aren=
't designed to maintain softstate in the network.

I see no reason why this document shouldn't be adopted as a working group d=
ocument immediately.

cheers,
Ole=

From behcetsarikaya@yahoo.com  Thu May 26 11:19:32 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D002013004F for <softwires@ietfa.amsl.com>; Thu, 26 May 2011 11:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[AWL=0.497,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEUF10uQqd2K for <softwires@ietfa.amsl.com>; Thu, 26 May 2011 11:19:29 -0700 (PDT)
Received: from nm12.bullet.mail.sp2.yahoo.com (nm12.bullet.mail.sp2.yahoo.com [98.139.91.82]) by ietfa.amsl.com (Postfix) with SMTP id 77D58130041 for <softwires@ietf.org>; Thu, 26 May 2011 11:19:29 -0700 (PDT)
Received: from [98.139.91.66] by nm12.bullet.mail.sp2.yahoo.com with NNFMP; 26 May 2011 18:19:24 -0000
Received: from [98.139.91.7] by tm6.bullet.mail.sp2.yahoo.com with NNFMP; 26 May 2011 18:19:24 -0000
Received: from [127.0.0.1] by omp1007.mail.sp2.yahoo.com with NNFMP; 26 May 2011 18:19:24 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 453793.22685.bm@omp1007.mail.sp2.yahoo.com
Received: (qmail 72332 invoked by uid 60001); 26 May 2011 18:19:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1306433964; bh=1G7ILwnxqyKhWuPvwMFI93ORCirSfLSpR7H5IT/4PCE=; 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=VFsyCEfYovGKJgJNuqS6zuJ/MW73TyIIMJAofMKGgudJNECN+mJVdVe0wnCvhGhNsg5lS5jwBRq9RO3Zy1PWG48drJzvN25k6mi+tdw8e/INygyMKq4BawjN1jZlddYdHvabhYAG8pDbbhwqc9U7PlSjwMvO9e3L+9akVqJCIVU=
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=JcQHYZToCbmL4tUqizHojb/GUeCj5j93J7RTU/FHP5UoDiye1Wn3/eS6w8hTTsQ7p4vsFCP6+daME+QyxrYXV5iBakoHSAkrRXt4QS6rQlk4IzmAwOMdUxaAReRpC5lPyOIIJ2EpXvVnTcL6zxDWruZjH0QxAno1BM+jdOxrZCA=;
Message-ID: <151831.43722.qm@web111407.mail.gq1.yahoo.com>
X-YMail-OSG: dR77kzMVM1nt_gglHbnixdBLC.ZTm3QVGmzNAPOi5rJ8KtG IhLnSj22pMgF_mo8qn_LuGP2yDGMF82WAUx15norhS8BZr7__o0z7lV7ykwZ 7ahBN2boo2Qf6i4oX6uZ3KLADZ3qU742sR9OE5eE0l2cJKK3wNlEm2hmIK99 FHo8nEqjqfiaz4IsiD4T9ZGXawsdka3v.6KCU8AwYZhSxHD9EGsBvJuuQcAj jT0kLrJ45Etf.sT_mItPg5wNfHZ5vjzdAUZiu9aJhd_lIKvg3r5UG3U8Ec1W Njc8qnclYQraXx5zE6n9iH2gk5GMiVfVyUNpQAiba3LBkripFYc2lGBBlfmy hfsbDHp.RTQf2NYt.ZCj7w3HefEV0SHCwfucE1WvWkha2K2V1hIkv7gkGHpj s2T981a0GnoMlYg--
Received: from [206.16.17.212] by web111407.mail.gq1.yahoo.com via HTTP; Thu, 26 May 2011 11:19:23 PDT
X-Mailer: YahooMailRC/567 YahooMailWebService/0.8.111.303096
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org> <1E0C1043-C98C-497E-ADA8-200C6FF43AF6@townsley.net>
Date: Thu, 26 May 2011 11:19:23 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Mark Townsley <mark@townsley.net>, Ole Troan <otroan@employees.org>
In-Reply-To: <1E0C1043-C98C-497E-ADA8-200C6FF43AF6@townsley.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 18:19:32 -0000

> On May 26, 2011, at 10:36 AM, Ole Troan wrote:
> 
> > I like the draft  and I think it covers the motivational points well.
> > 
> > as a  general comment, I do think the document is too wordy. could the 
>authors make  the next revision terser or do you want me to propose text 
>changes?
> > 
> > I would also suggest that you reference the sections in rfc1958 on  state.
> > we don't have a good success record in gleaning state in the  middle of the 
>network (NAT, N:1 VLANs, DHCP...), since the protocols we 'glean'  from aren't 
>designed to maintain softstate in the network.
> > 
> > I  see no reason why this document shouldn't be adopted as a working group 
>document  immediately.
> 
> I support this becoming a WG document, and agree with Ole  that the next 
>version should cut back on text. We want to give the IESG  something as clear 
>and concise as possible.
> 
> If there is reasonable  consensus (not that the document is complete, but that 
>it will be the basis for  the final document), all it takes is an OK by the 
>chairs and a submission by the  authors with the WG title. 
>
> 

You mean after merging with draft-chen-softwire-4v6-motivation-00.txt?

then +1 from me.

Behcet


From jacniq@gmail.com  Fri May 27 01:54:38 2011
Return-Path: <jacniq@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BE00E07B9 for <softwires@ietfa.amsl.com>; Fri, 27 May 2011 01:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvIrlHQdNyZT for <softwires@ietfa.amsl.com>; Fri, 27 May 2011 01:54:38 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id CB3A3E07B5 for <softwires@ietf.org>; Fri, 27 May 2011 01:54:37 -0700 (PDT)
Received: by vxg33 with SMTP id 33so1495590vxg.31 for <softwires@ietf.org>; Fri, 27 May 2011 01:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8mKXweB+9VIk7Io28ppX8PWzHPJ1OBWB4Emb8gPMYrI=; b=vjCFkejJz/5ADe0JntI7HfEoi5yWtW6Y7UDF9S8673xjWbRBSYIE9nX8zR7pfk8btA VQ60ERtCBsuoGfSH/knhYxtM5RaAr9GL9cKg/W5a2k5mXM+w800gxrQDMRD+q5k1yScr Mq/0iIwRVOHXzE19tLu9b2jy5XyaAX4dqO0vI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ClZy4oBNQZt6gYCBqh7RR5etzmuIKGU59BBpuUWc/75b8A+iU6Q54Qlv6DRRIfkVIM 0mHDmok1h+X8KnZozf4sDkqfDo6IjdecscTjPj3UlTtC5CvJg85X7KljjgjKuqcAIH61 kFqdpts7rEJxgixkqZxBCLS+R0FNGa3GTvwvA=
MIME-Version: 1.0
Received: by 10.52.176.74 with SMTP id cg10mr2639370vdc.242.1306486477009; Fri, 27 May 2011 01:54:37 -0700 (PDT)
Received: by 10.52.186.198 with HTTP; Fri, 27 May 2011 01:54:36 -0700 (PDT)
In-Reply-To: <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org>
Date: Fri, 27 May 2011 16:54:36 +0800
Message-ID: <BANLkTikp93EWE8RK_mB9qUurgudiPViX+g@mail.gmail.com>
From: Jacni Qin <jacniq@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=20cf307f34c25db4dd04a43e16ef
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2011 08:54:38 -0000

--20cf307f34c25db4dd04a43e16ef
Content-Type: text/plain; charset=ISO-8859-1

On Thu, May 26, 2011 at 4:36 PM, Ole Troan <otroan@employees.org> wrote:

> I like the draft and I think it covers the motivational points well.
>
> as a general comment, I do think the document is too wordy. could the
> authors make the next revision terser or do you want me to propose text
> changes?
>

Jacni>: Yes, a little. Too many operational issues, is there any order of
priority? Or just point out what you concern the most?
I felt lost after reading it. :-)


> I would also suggest that you reference the sections in rfc1958 on state.
> we don't have a good success record in gleaning state in the middle of the
> network (NAT, N:1 VLANs, DHCP...), since the protocols we 'glean' from
> aren't designed to maintain softstate in the network.
>
> I see no reason why this document shouldn't be adopted as a working group
> document immediately.
>

Jacni>: +1


Cheers,
Jacni


>
> cheers,
> Ole
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

--20cf307f34c25db4dd04a43e16ef
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<font face=3D"verdana,sans-serif"></font><br><div class=3D"gmail_quote">On =
Thu, May 26, 2011 at 4:36 PM, Ole Troan <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:otroan@employees.org">otroan@employees.org</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex;">
I like the draft and I think it covers the motivational points well.<br>
<br>
as a general comment, I do think the document is too wordy. could the autho=
rs make the next revision terser or do you want me to propose text changes?=
<br></blockquote><div><br><font face=3D"verdana,sans-serif">Jacni&gt;: Yes,=
 a little. Too many operational issues, is there any order of priority? Or =
just point out what you concern the most?<br>
I felt lost after reading it. :-)<br><br></font></div><blockquote class=3D"=
gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb=
(204, 204, 204); padding-left: 1ex;">
<br>
I would also suggest that you reference the sections in rfc1958 on state.<b=
r>
we don&#39;t have a good success record in gleaning state in the middle of =
the network (NAT, N:1 VLANs, DHCP...), since the protocols we &#39;glean&#3=
9; from aren&#39;t designed to maintain softstate in the network.<br>
<br>
I see no reason why this document shouldn&#39;t be adopted as a working gro=
up document immediately.<br></blockquote><div><br><font face=3D"verdana,san=
s-serif">Jacni&gt;: +1<br><br><br>Cheers,<br>Jacni<br></font>=A0<br></div>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
cheers,<br>
<font color=3D"#888888">Ole<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</div></div></blockquote></div><br>

--20cf307f34c25db4dd04a43e16ef--

From internet-drafts@ietf.org  Fri May 27 16:37:59 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B17CE0767; Fri, 27 May 2011 16:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GbafUKsgKuEq; Fri, 27 May 2011 16:37:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09068E06D6; Fri, 27 May 2011 16:37:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <20110527233759.12521.9023.idtracker@ietfa.amsl.com>
Date: Fri, 27 May 2011 16:37:59 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-dual-stack-lite-11.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2011 23:37:59 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Softwires Working Group of the IETF.

	Title           : Dual-Stack Lite Broadband Deployments Following IPv4 Exh=
austion
	Author(s)       : Alain Durand
                          Ralph Droms
                          James Woodyatt
                          Yiu L. Lee
	Filename        : draft-ietf-softwire-dual-stack-lite-11.txt
	Pages           : 33
	Date            : 2011-05-27

   This document revisits the dual-stack model and introduces the Dual-
   Stack Lite technology aimed at better aligning the costs and benefits
   of deploying IPv6 in service provider networks.  Dual-Stack Lite
   enables a broadband service provider to share IPv4 addresses among
   customers by combining two well-known technologies: IP in IP (IPv4-
   in-IPv6) and Network Address Translation (NAT).


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-dual-stack-lite-11.=
txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-softwire-dual-stack-lite-11.t=
xt

From dr@cluenet.de  Sat May 28 05:42:39 2011
Return-Path: <dr@cluenet.de>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 969CDE0693 for <softwires@ietfa.amsl.com>; Sat, 28 May 2011 05:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z83z43IAq5P2 for <softwires@ietfa.amsl.com>; Sat, 28 May 2011 05:42:39 -0700 (PDT)
Received: from mail1.cluenet.de (mail1.cluenet.de [IPv6:2001:1440:201:101::5]) by ietfa.amsl.com (Postfix) with ESMTP id ABAD9E0662 for <softwires@ietf.org>; Sat, 28 May 2011 05:42:38 -0700 (PDT)
Received: by mail1.cluenet.de (Postfix, from userid 500) id 88D3410812D; Sat, 28 May 2011 14:42:36 +0200 (CEST)
Date: Sat, 28 May 2011 14:42:36 +0200
From: Daniel Roesen <dr@cluenet.de>
To: softwires@ietf.org
Message-ID: <20110528124236.GB24079@srv03.cluenet.de>
Mail-Followup-To: softwires@ietf.org
References: <20110527233759.12521.9023.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110527233759.12521.9023.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Subject: Re: [Softwires] I-D Action:	draft-ietf-softwire-dual-stack-lite-11.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 May 2011 12:42:39 -0000

Hi,

maybe just nitpicking, but...

A.3.  High availability
[...]
   An important element in the design of the Dual-Stack Lite technology
   is the simplicity of implementation on the customer side.  An IP4-in-
   IPv6 tunnel and a default route over it in the B4 element are all is
   needed to get IPv4 connectivity.  It is assumed that high
   availability is the responsibility of the service provider, not the
   customer devices implementing Dual-Stack Lite.  As such, a single
   IPv6 address of the tunnel end-point is provided in the DHCPv6 option
   defined in [I-D.ietf-softwire-ds-lite-tunnel-option].
[...]

This ain't strictly correct.

Unfortunately[1], the DHCPv6 option was changed to provide an FQDN which
then has to be resolved to AAAAs by the B4 chosing one of them in an
unspecified way.

Best regards,
Daniel

[1] now you need working IPv6 DNS resolution to get IPv4 connectivity up
and running (ARGH!), adding unnecessary complexity in B4 initialization
and nondeterministic B4 behaviour in regard of AAAA choice, making any
load balancing mechanism based on returning multiple AAAA infeasible due
to possible biassing. While load balancing could have been achieved via
plain IPv6 address DHCPv6 option just fine, leaving it up to the DHCPv6
server issuing AFTR addresses in a balanced fashion.

-- 
CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0

From yiu_lee@cable.comcast.com  Sat May 28 12:20:16 2011
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8045CE077B for <softwires@ietfa.amsl.com>; Sat, 28 May 2011 12:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.099
X-Spam-Level: 
X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=3.364, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZ0tsP+dlVrY for <softwires@ietfa.amsl.com>; Sat, 28 May 2011 12:20:16 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by ietfa.amsl.com (Postfix) with ESMTP id C7879E06EE for <softwires@ietf.org>; Sat, 28 May 2011 12:20:15 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.127527575; Sat, 28 May 2011 15:20:08 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0289.001; Sat, 28 May 2011 15:20:08 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Daniel Roesen <dr@cluenet.de>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: [Softwires] I-D Action: draft-ietf-softwire-dual-stack-lite-11.txt
Thread-Index: AQHMHWw9KESUs0+x2km26PXcfntqFw==
Date: Sat, 28 May 2011 19:20:07 +0000
Message-ID: <CA06C1B1.F38B%yiu_lee@cable.comcast.com>
In-Reply-To: <20110528124236.GB24079@srv03.cluenet.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
x-originating-ip: [68.82.20.172]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <63FAF0AA67AD5840A9F52A9BC1893D20@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-dual-stack-lite-11.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 May 2011 19:20:16 -0000

Hi Daniel,

Actually, there was a long discussion in the mailing list to argue to use
FQDN or AAAA address. I personally support to use only AAAA record in the
dhcpv6 option, but some operators prefer to use FQDN for more flexibility.
As you pointed out, this flexibility does come with cost. We leave the
AAAA selection process undefined because each ISP may have slightly
different requirement for LB. However, this also causes undefined behavior
for off-the-shelf home gateway with ds-lite. If an ISP decided to use
plain IPv6 address, it must make sure each FQDN only returns one AAAA
record.

B.R.,
Yiu


On 5/28/11 8:42 AM, "Daniel Roesen" <dr@cluenet.de> wrote:

>[1] now you need working IPv6 DNS resolution to get IPv4 connectivity up
>and running (ARGH!), adding unnecessary complexity in B4 initialization
>and nondeterministic B4 behaviour in regard of AAAA choice, making any
>load balancing mechanism based on returning multiple AAAA infeasible due
>to possible biassing. While load balancing could have been achieved via
>plain IPv6 address DHCPv6 option just fine, leaving it up to the DHCPv6
>server issuing AFTR addresses in a balanced fashion.


From satoru.matsushima@gmail.com  Mon May 30 08:48:53 2011
Return-Path: <satoru.matsushima@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC440E07E5 for <softwires@ietfa.amsl.com>; Mon, 30 May 2011 08:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIENRIvjVCEa for <softwires@ietfa.amsl.com>; Mon, 30 May 2011 08:48:53 -0700 (PDT)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by ietfa.amsl.com (Postfix) with ESMTP id 75F2CE07F6 for <softwires@ietf.org>; Mon, 30 May 2011 08:48:52 -0700 (PDT)
Received: by pxi20 with SMTP id 20so2559104pxi.27 for <softwires@ietf.org>; Mon, 30 May 2011 08:48:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=kIZVOFgZIhegV/6QmxQL6Pnflgz+smaJq2HwYQuoe0w=; b=ZXN0a0A7sTs+ru7NO68hSbJaI+qWM0fvf/tCogNOy3+DT+asFAJoLp3abMxGNMEOED 6Q3lbbyx5P3Dv0292uI1utQjHYRYQgXDeIFDB2xysAfo9CR3/8eKXaSdWo+wnH8blKmp Q8xBE2tXPz+titj1sByfg0FNHcGkQ4yhexHSY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=gGH96NdGbnZwtMAqF5ieasi6OjLm/zOk7d4h5O3LweVt8uDwmpFzaA8WIjR/OHkzN2 fn+3LSea4r/AY7GnHDMgq02dLONpxTxL2T0W/HUdQrFToMrleoLElHeRTZ4WSHehbMfe 1rKuq3vjDbu5D6GR4tBIPgvubLA543+Kohyzs=
Received: by 10.68.60.66 with SMTP id f2mr2015299pbr.0.1306770532199; Mon, 30 May 2011 08:48:52 -0700 (PDT)
Received: from [192.168.3.8] (softbank221038134212.bbtec.net [221.38.134.212]) by mx.google.com with ESMTPS id p5sm2962775pbd.28.2011.05.30.08.48.49 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 May 2011 08:48:51 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <151831.43722.qm@web111407.mail.gq1.yahoo.com>
Date: Tue, 31 May 2011 00:48:47 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5A5437D-5787-4BCF-8A74-809591D7FFBA@gmail.com>
References: <1A842077-42BE-4354-BEB0-8A0F19A9CBF6@gmail.com> <434330BF-E21E-41E0-A34F-FBC2D0415BE0@free.fr> <94C682931C08B048B7A8645303FDC9F33E4C80821D@PUEXCB1B.nanterre.francetelecom.fr> <B0972E52-A663-4DA4-9F9D-6D0C9D8C7F2F@employees.org> <1E0C1043-C98C-497E-ADA8-200C6FF43AF6@townsley.net> <151831.43722.qm@web111407.mail.gq1.yahoo.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Isabel Borges <Isabel@ptinovacao.pt>
Subject: Re: [Softwires] Motivation draft for stateless v4 over v6 solution
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2011 15:48:54 -0000

Hi,

On 2011/05/27, at 3:19, Behcet Sarikaya wrote:
> You mean after merging with draft-chen-softwire-4v6-motivation-00.txt?
>=20
> then +1 from me.

The authors of both drafts are now co-working to integrate unified =
version so we'll submit it soon. We would like to invite your comments. =
Any feedback for current version of both draft are also welcome.

Best regards,
--satoru=

From iesg-secretary@ietf.org  Tue May 31 06:18:11 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2D7E080B; Tue, 31 May 2011 06:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WeEujRjvnj+K; Tue, 31 May 2011 06:18:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E540E085C; Tue, 31 May 2011 06:17:28 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <20110531131728.28186.25990.idtracker@ietfa.amsl.com>
Date: Tue, 31 May 2011 06:17:28 -0700
Cc: softwire mailing list <softwires@ietf.org>, softwire chair <softwire-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Softwires] Protocol Action: 'Dual-Stack Lite Broadband Deployments Following	IPv4 Exhaustion' to Proposed Standard	(draft-ietf-softwire-dual-stack-lite-11.txt)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2011 13:18:11 -0000

The IESG has approved the following document:
- 'Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion'
  (draft-ietf-softwire-dual-stack-lite-11.txt) as a Proposed Standard

This document is the product of the Softwires Working Group.

The IESG contact persons are Jari Arkko and Ralph Droms.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-softwire-dual-stack-lite/




Technical Summary

   This document revisits the dual-stack model and introduces the dual-
   stack lite technology aimed at better aligning the costs and benefits
   of deploying IPv6. Dual-stack lite enables a broadband service
   provider to share IPv4 addresses among customers by combining two
   well-known technologies: IP in IP (IPv4-in-IPv6) and Network Address
   Translation (NAT).

Working Group Summary

   This document was discussed in depth and well-reviewed. There is some
   disagreement over small details, but overall WG consensus is strong to
   publish this document.

Document Quality

   There are multiple, independent, interoperable implementations of this
   protocol today. Several service providers have announced plans to deploy
   or interest in deploying. 

Personnel

   The responsible Area Director is Jari Arkko, as the normal
   sponsor for the SOFTWIRE WG, Ralph Droms, is one of the
   authors of this document.



From iesg-secretary@ietf.org  Tue May 31 07:47:08 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A639E07C0; Tue, 31 May 2011 07:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.203
X-Spam-Level: 
X-Spam-Status: No, score=-102.203 tagged_above=-999 required=5 tests=[AWL=-0.204, BAYES_00=-2.599, J_CHICKENPOX_83=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f8EYerZj4sL1; Tue, 31 May 2011 07:47:03 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93543E07CA; Tue, 31 May 2011 07:46:59 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <20110531144659.28781.15362.idtracker@ietfa.amsl.com>
Date: Tue, 31 May 2011 07:46:59 -0700
Cc: softwire mailing list <softwires@ietf.org>, softwire chair <softwire-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Softwires] Protocol Action: 'xCal: The XML format for iCalendar' to Proposed	Standard (draft-daboo-et-al-icalendar-in-xml-10.txt)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2011 14:47:08 -0000

The IESG has approved the following document:
- 'xCal: The XML format for iCalendar'
  (draft-daboo-et-al-icalendar-in-xml-10.txt) as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Peter Saint-Andre.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-daboo-et-al-icalendar-in-xml/




Technical Summary

   This specification defines "xCal", an XML representation of the
   iCalendar data format specified in RFC 5545.  iCalendar is a 
   widely deployed interchange format for calendaring and scheduling 
   data.  While many applications and services consume and generate 
   calendar data, iCalendar is a specialized format that requires its own 
   parser/generator.  In contrast, XML-based formats are widely used 
   for interoperability between applications, and the many tools that 
   generate, parse, and manipulate XML make it easier to work with 
   than iCalendar.  xCal is defined as a straightforward mapping into
   XML from iCalendar, so that iCalendar data can be converted to XML,
   and then back to iCalendar, without losing any semantic meaning in
   the data.  Anyone creating xCal calendar data according to this
   specification will know that their data can be converted to a valid
   iCalendar representation as well.

Working Group Summary

   This document is not the product of an IETF Working Group.

Document Quality

   The document has been reviewed on the calsify@ietf.org list, and 
   also on the vcarddav@ietf.org list to ensure consistency with the 
   XML representation of vCard.  The calendar+xml media type 
   registration was first posted to the media type review list on 
   2010-09-02 and all feedback was incorporated.  There are
   several implementations completed or in progress.  In addition, 
   OASIS is making this specification the basis of their WS-Calendar 
   work, which is expected to induce further implementations.

Personnel

   The Document Shepherd / Responsible Area Director is 
   Peter Saint-Andre.

From wwwrun@ietfa.amsl.com  Tue May 31 10:23:05 2011
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id A1927E085C; Tue, 31 May 2011 10:23:05 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110531172305.A1927E085C@ietfa.amsl.com>
Date: Tue, 31 May 2011 10:23:05 -0700 (PDT)
Cc: softwires@ietf.org, cuiyong@tsinghua.edu.cn
Subject: [Softwires] WG Action: RECHARTER: Softwires (softwire)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2011 17:23:05 -0000

The Softwires (softwire) working group in the Internet Area of the IETF 
has been rechartered.  For additional information, please contact the 
Area Directors or the working group Chairs.

Softwires (softwire)
------------------------------
Current Status: Active Working Group

 Chairs:
   Alain Durand <adurand@juniper.net>
   Yong Cui <cuiyong@tsinghua.edu.cn>

 Internet Area Directors:
   Ralph Droms <rdroms.ietf@gmail.com>
   Jari Arkko <jari.arkko@piuha.net>

 Internet Area Advisor:
   Ralph Droms <rdroms.ietf@gmail.com>

 Mailing Lists:
   General Discussion: softwires@ietf.org
   To Subscribe:       softwires-request@ietf.org
   Archive:            http://www.ietf.org/mail-archive/web/softwires/


Description of Working Group:

  The Softwires Working Group is specifying the standardization of
  discovery, control and encapsulation methods for connecting IPv4
  networks across IPv6 networks and IPv6 networks across IPv4 networks
  in a way that will encourage multiple, inter-operable
  implementations.

  For various reasons, native IPv4 and/or IPv6 transport may not be
  available in all cases, and there is a need to tunnel IPv4 in IPv6
  or IPv6 in IPv4 to cross a part of the network which is not IPv4 or
  IPv6 capable. The Softwires Problem Statement, RFC 4925, identifies
  two distinct topological scenarios that the Working Group will
  provide solutions for: "Hubs and Spokes" and "Mesh." In the former
  case (Hubs and Spokes), hosts or "stub" networks are attached via
  individual, point-to-point, IPv4 over IPv6 or IPv6 over IPv4
  softwires to a centralized Softwire Concentrator. In the latter case
  (Mesh), network islands of one Address Family (IPv4 or IPv6) are
  connected over a network of another Address Family via point to
  multi-point softwires among Address Family Border Routers (AFBRs).

  The Softwires Working Group will reuse existing technologies as much
  as possible and only when necessary, create additional protocol
  building blocks.

  For generality, all base softwires encapsulation mechanisms should
  support all combinations of IP versions over one other (IPv4 over
  IPv6, IPv6 over IPv4, IPv4 over IPv4, IPv6 over IPv6). IPv4/IPv6
  translation mechanisms, new addressing schemes, and block address
  assignments are out of scope. DHCP options developed in this working
  group will be reviewed jointly with the DHC Working Group.  RADIUS
  attributes developed in the Softwires Working Group will be reviewed
  jointly with the RADEXT Working Group.  The MIB Doctors directorate
  will be asked to review any MIB modules developed in the Softwires
  Working Group.  BGP and other routing and signaling protocols
  developed in this group will be reviewed jointly with the proper
  working groups and other workings that may take interest (e.g. IDR,
  L3VPN, PIM, LDP, SAAG, etc).

  The specific work areas for this working group are:

  1. Developments for Mesh softwires topology; the Mesh topology work
     will be reviewed in the L3VPN and IDR Working Groups
     - multicast
     - MIB module

  2. Developments for 6rd:
     - multicast
     - operational specification
     - RADIUS attribute for 6rd server
     - MIB module
     - Gateway-initiated 6rd (GI-6rd)

  3. Developments for Dual-Stack Lite (DS-Lite):
     - multicast
     - operational specification
     - RADIUS attribute for AFTR
     - proxy extensions; GI-DS-Lite; No NAT on AFTR
     - MIB module

  4. Developments for stateless legacy IPv4 carried over IPv6
     - develop a solution motivation document to be published as an
       RFC
     - develop a protocol specification response to the solution
       motivation document; this work item will not be taken through
       Working Group last call until the solution motivation document
       has been published or approved for publication

  5. Finalize discovery and configuration mechanisms for a gateway to
     use DS-Lite or 6rd; these discovery and configuration mechanisms
     must take into a account other operating environments such as
     dual-stack and tunneling mechanisms not defined by the Softwires
     Working Group.  Development of new mechanisms will involve the
     DHC and/or V6OPS Working Groups as appropriate

Other work items would require Working Group approval and rechartering.

Goals and Milestones:

Jun 2011 Submit DS-lite RADIUS attribute document for Proposed
         Standard
Jun 2011 Adopt DS-lite operational document as a Working Group
         document 
Jul 2011 Submit 6rd RADIUS attribute document for Proposed Standard
Jul 2011 Submit GI DS-lite document for Proposed Standard
Jul 2011 Adopt DS-Lite without NAT document as a Working Group
         document 
Jul 2011 Adopt DHCPv4 over tunnel document as a Working Group document
Aug 2011 Adopt 6rd operational document as a Working Group document
Aug 2011 Adopt Multicast extensions document as a Working Group
         document 
Aug 2011 Submit DS-lite operational document for Informational
Aug 2011 Adopt stateless legacy IPv4 solution motivation document as a
         Working Group document
Sep 2011 Submit DS-Lite without NAT document for Informational
Sep 2011 Submit DHCPv4 over tunnel document for Proposed Standard
Nov 2011 Submit Multicast extensions document for Informational
Nov 2011 Submit 6rd operational document for Informational
Nov 2011 Adopt 6rd MIB module document as a Working Group document
Nov 2011 Adopt DS-lite MIB module document as a Working Group document
Nov 2011 Adopt Mesh topology MIB module document as a Working Group
         document 
Dec 2011 Submit stateless legacy IPv4 solution motivation document for
         Informational
Dec 2011 Adopt stateless legacy IPv4 specification document as a
         Working Group document
Apr 2012 Submit stateless legacy IPv4 specification document for
         Proposed Standard
Nov 2012 Submit 6rd MIB module document for Proposed Standard
Nov 2012 Submit DS-lite MIB module document for Proposed Standard
Nov 2012 Submit Mesh topology MIB module document for Proposed
         Standard 

