
From bingxuere@gmail.com  Sat Oct  1 17:56:17 2011
Return-Path: <bingxuere@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 772CF21F8E87 for <softwires@ietfa.amsl.com>; Sat,  1 Oct 2011 17:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.526
X-Spam-Level: 
X-Spam-Status: No, score=-3.526 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zKpUWUFpv2Ya for <softwires@ietfa.amsl.com>; Sat,  1 Oct 2011 17:56:17 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id E7E0821F8E83 for <softwires@ietf.org>; Sat,  1 Oct 2011 17:56:16 -0700 (PDT)
Received: by iaby26 with SMTP id y26so4291496iab.31 for <softwires@ietf.org>; Sat, 01 Oct 2011 17:59:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=QilvfZJ+rpLWozn5VTIODw9gEFGXPAqdcQN13vpbjxs=; b=yAWeg/M166grmZ9ycw2IqgvB65ht6bVJ3kelVESQOwPK5/vqDuEFj4gL3BxB5Nek2e 8qAMtQv93JFyVg1/zeK/OrZ/h31sl+ocqFZQgaKFgSDnZoAIQfpNxpq5HOzHPiUZFAP/ BORAeZeXIRAb+orW7uAIo6DhAXyg4qpo61oQo=
Received: by 10.42.197.8 with SMTP id ei8mr5146683icb.207.1317517153068; Sat, 01 Oct 2011 17:59:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Sat, 1 Oct 2011 17:58:52 -0700 (PDT)
In-Reply-To: <05DF0672-BE68-4DA2-8094-7B314E416A1A@employees.org>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <B3D5FABA-72BA-4C35-A068-D823CC0A4682@laposte.net> <CAM+vMERSbGuraAC9snvGUgPBOY40m5p0SX46qfVqJaB6bHmvCw@mail.gmail.com> <D8B8F1D1-1FE7-44E1-A6C6-E1480BD91C0A@ipinfusion.com> <4E82C970.8060801@jacni.com> <3580FD83-1FD6-4A5D-9AB1-046FBE47AFBB@employees.org> <823C69D6-D040-4959-8A5A-3B1B2CAF7734@free.fr> <C1DB0E47-C4F8-4AAF-B754-379B9B47BB95@employees.org> <EC5F7306-8EA6-4707-A8EF-D8D2BEC5E3B9@free.fr> <593B5458-3276-43D7-AF32-2FB8EF899AE7@employees.org> <332BEE87-D2F4-496B-8D73-16AC7FFA2B71@free.fr> <CC3E5BBD-3C75-48F2-90E7-AFAE365AAF2F@employees.org> <F0D8CC93-E84B-4565-8A78-3D166BA88FA7@laposte.net> <05DF0672-BE68-4DA2-8094-7B314E416A1A@employees.org>
From: Qiong <bingxuere@gmail.com>
Date: Sun, 2 Oct 2011 08:58:52 +0800
Message-ID: <CAH3bfACG52APJNa2RxEmyyvG7QoEaQMo9i31gA-ZNco7w2ASTw@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=20cf303ea63ae4e69904ae465d71
Cc: Softwires-wg <softwires@ietf.org>, Wojciech Dec <wdec@cisco.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 02 Oct 2011 00:56:17 -0000

--20cf303ea63ae4e69904ae465d71
Content-Type: text/plain; charset=UTF-8

Hi Ole and Remi,

> This is my answer to your first (double) question.
> > If it is not enough, as suggested below, please explain what you don't
> understand.
>
> I specifically do not want a solution that changes forwarding behaviour for
> _all_ IPv6 packets.
> e.g. looking at 24 bits in the middle of an IPv6 address is such a change.
>
> I don't understand what requirements you are basing this 'solution' on.
> if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out of
> the delegated prefix. then why do you need any of that?
>

Qiong : I agree that routing lookup for a provisioned /64 prefix would be
better that extracting certain bits for each IPv6 address in CE. This would
bring less change to existing routing model.

Best wishes

Qiong

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

--20cf303ea63ae4e69904ae465d71
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ole and Remi,<br><br><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex;"><div class=3D"im">&gt; This is my answer to your first (double) que=
stion.<br>


&gt; If it is not enough, as suggested below, please explain what you don&#=
39;t understand.<br>
<br>
</div>I specifically do not want a solution that changes forwarding behavio=
ur for _all_ IPv6 packets.<br>
e.g. looking at 24 bits in the middle of an IPv6 address is such a change.<=
br>
<br>
I don&#39;t understand what requirements you are basing this &#39;solution&=
#39; on.<br>
if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out of =
the delegated prefix. then why do you need any of that?<br></blockquote><di=
v>=C2=A0</div><div>Qiong : I agree that routing lookup for a=C2=A0provision=
ed=C2=A0/64 prefix would be better that extracting certain bits for each IP=
v6 address in CE. This would bring less change to existing routing model.</=
div>

<div><br></div><div>Best wishes</div><div><br></div><div>Qiong=C2=A0</div><=
div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><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>

--20cf303ea63ae4e69904ae465d71--

From despres.remi@laposte.net  Mon Oct  3 00:28:00 2011
Return-Path: <despres.remi@laposte.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 4164F21F87E2 for <softwires@ietfa.amsl.com>; Mon,  3 Oct 2011 00:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.862
X-Spam-Level: 
X-Spam-Status: No, score=-1.862 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8TkQgkzoUWLK for <softwires@ietfa.amsl.com>; Mon,  3 Oct 2011 00:27:59 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.19]) by ietfa.amsl.com (Postfix) with ESMTP id 4EABD21F87C9 for <softwires@ietf.org>; Mon,  3 Oct 2011 00:27:59 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2321.sfr.fr (SMTP Server) with ESMTP id E783170000B2; Mon,  3 Oct 2011 09:30:59 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2321.sfr.fr (SMTP Server) with ESMTP id 05B4870000A6; Mon,  3 Oct 2011 09:30:58 +0200 (CEST)
X-SFR-UUID: 20111003073059234.05B4870000A6@msfrf2321.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-1--4159665
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAH3bfACG52APJNa2RxEmyyvG7QoEaQMo9i31gA-ZNco7w2ASTw@mail.gmail.com>
Date: Mon, 3 Oct 2011 09:30:56 +0800
Message-Id: <F2CDA7C1-29C6-4F20-B59D-2B79C292C48F@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <B3D5FABA-72BA-4C35-A068-D823CC0A4682@laposte.net> <CAM+vMERSbGuraAC9snvGUgPBOY40m5p0SX46qfVqJaB6bHmvCw@mail.gmail.com> <D8B8F1D1-1FE7-44E1-A6C6-E1480BD91C0A@ipinfusion.com> <4E82C970.8060801@jacni.com> <3580FD83-1FD6-4A5D-9AB1-046FBE47AFBB@employees.org> <823C69D6-D040-4959-8A5A-3B1B2CAF7734@free.fr> <C1DB0E47-C4F8-4AAF-B754-379B9B47BB95@employees.org> <EC5F7306-8EA6-4707-A8EF-D8D2BEC5E3B9@free.fr> <593B5458-3276-43D7-AF32-2FB8EF899AE7@employees.org> <332BEE87-D2F4-496B-8D73-16AC7FFA2B71@free.fr> <CC3E5BBD-3C75-48F2-90E7-AFAE365AAF2F@employees.org> <F0D8CC93-E84B-4565-8A78-3D166BA88FA7@laposte.net> <05DF0672-BE68-4DA2-8094-7B314E416A1A@employees.org> <CAH3bfACG52APJNa2RxEmyyvG7QoEaQMo9i31gA-ZNco7w2ASTw@mail.gmail.com>
To: Qiong <bingxuere@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Wojciech Dec <wdec@cisco.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 03 Oct 2011 07:28:00 -0000

--Apple-Mail-1--4159665
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi Congxiao,
Thanks for your comment.
Please sea inline.

Le 2 oct. 2011 =E0 08:58, Qiong a =E9crit :

> Hi Ole and Remi,
>=20
> > This is my answer to your first (double) question.
> > If it is not enough, as suggested below, please explain what you =
don't understand.
>=20
> I specifically do not want a solution that changes forwarding =
behaviour for _all_ IPv6 packets.
> e.g. looking at 24 bits in the middle of an IPv6 address is such a =
change.

Having a recognizable field in the IID doesn't imply any change of =
forwarding behavior (still done on up to /64s).
=20
>=20
> I don't understand what requirements you are basing this 'solution' =
on.
> if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix =
out of the delegated prefix. then why do you need any of that?
> =20
> Qiong : I agree that routing lookup for a provisioned /64 prefix would =
be better that extracting certain bits for each IPv6 address in CE. This =
would bring less change to existing routing model.

Having a recognizable field in the IID doesn't change the possibility to =
lookup for a provisioned /64 prefix.
It only opens the ADDITIONAL possibility to recognize IPv4 addresses =
without knowledge of any IPv6 prefix.
This is useful in particular in use cases where:
- some ALGs are enforced by devices that can't do prefix matching
- the same IPv6 prefixes are used for real IPv6 addresses and embedded =
IPv4 addresses.
MORE GENERAL (open to more use cases without excluding any).

Hope it clarifies,

Regards,
RD


>=20
> Best wishes
>=20
> Qiong=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>=20


--Apple-Mail-1--4159665
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Congxiao,<div>Thanks for your comment.</div><div>Please sea =
inline.</div><div><br><div><div>Le 2 oct. 2011 =E0 08:58, Qiong a =E9crit =
:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Hi Ole and Remi,<br><br><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; "><div class=3D"im">&gt; This is my answer to =
your first (double) question.<br>


&gt; If it is not enough, as suggested below, please explain what you =
don't understand.<br>
<br>
</div>I specifically do not want a solution that changes forwarding =
behaviour for _all_ IPv6 packets.<br>
e.g. looking at 24 bits in the middle of an IPv6 address is such a =
change.<br></blockquote></div></blockquote><div><br></div>Having a =
recognizable field in the IID doesn't imply any change of forwarding =
behavior (still done on up to /64s).</div><div>&nbsp;<br><blockquote =
type=3D"cite"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; ">
<br>
I don't understand what requirements you are basing this 'solution' =
on.<br>
if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out =
of the delegated prefix. then why do you need any of =
that?<br></blockquote><div>&nbsp;</div><div>Qiong : I agree that routing =
lookup for a&nbsp;provisioned&nbsp;/64 prefix would be better that =
extracting certain bits for each IPv6 address in CE. This would bring =
less change to existing routing =
model.</div></div></blockquote><div><br></div></div><div>Having a =
recognizable field in the IID doesn't change the possibility to lookup =
for a provisioned /64 prefix.</div><div>It only opens the ADDITIONAL =
possibility to recognize IPv4 addresses without knowledge of any IPv6 =
prefix.</div><div>This is useful in particular in use cases =
where:</div><div>- some ALGs are enforced by devices that can't do =
prefix matching</div><div>- the same IPv6 prefixes are used for real =
IPv6 addresses and embedded IPv4 addresses.</div><div>MORE GENERAL (open =
to more use cases without excluding any).</div><div><br></div><div>Hope =
it =
clarifies,</div><div><br></div><div>Regards,</div><div>RD</div><div><br></=
div><div><br></div><div><blockquote type=3D"cite"><div =
class=3D"gmail_quote">

<div><br></div><div>Best =
wishes</div><div><br></div><div>Qiong&nbsp;</div><div><br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;"><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"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</div></div></blockquote></div><br>
</blockquote></div><br></div></body></html>=

--Apple-Mail-1--4159665--

From wdec@cisco.com  Mon Oct  3 00:43:05 2011
Return-Path: <wdec@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 3491721F86DD for <softwires@ietfa.amsl.com>; Mon,  3 Oct 2011 00:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.237
X-Spam-Level: 
X-Spam-Status: No, score=-108.237 tagged_above=-999 required=5 tests=[AWL=0.965, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEl1XSl+tNTS for <softwires@ietfa.amsl.com>; Mon,  3 Oct 2011 00:43:03 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id D398621F8672 for <softwires@ietf.org>; Mon,  3 Oct 2011 00:43:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=wdec@cisco.com; l=5181; q=dns/txt; s=iport; t=1317627965; x=1318837565; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=SGVERp4dgkjKqexDRj6gNqnkaafjS76HMO+smcQNq6Y=; b=XhZb1KRZf97zUy9OI9DwdfZ1I9Jh4N06fmfGMonV5D6lem+/xMA8D2s3 C284kCi87dsi6wasX1U7LGYxnmA27JNNa2HX+djJHu24EiUj/oV7duU7W 6fWges4UTlANkL49wMYXtTKg7KtsPGxfKCxCRaau66EUwOK4+O0HsQHR0 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAAhniU6Q/khR/2dsb2JhbABCgk2kWW6BBYFTAQEBAQIBAQEBDwEqMQsFDQEIBGMGMAEBBAENBRsHh1kGm04BnHoDhyEEh0eMGYUuhHCHIg
X-IronPort-AV: E=Sophos;i="4.68,478,1312156800"; d="scan'208,217";a="56954670"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 03 Oct 2011 07:46:03 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p937k3NF030856; Mon, 3 Oct 2011 07:46:03 GMT
Received: from xmb-ams-112.cisco.com ([144.254.74.87]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 3 Oct 2011 09:46:03 +0200
Received: from 10.55.90.116 ([10.55.90.116]) by XMB-AMS-112.cisco.com ([144.254.74.87]) with Microsoft Exchange Server HTTP-DAV ;  Mon,  3 Oct 2011 07:46:03 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Mon, 03 Oct 2011 09:46:00 +0200
From: Wojciech Dec <wdec@cisco.com>
To: Qiong <bingxuere@gmail.com>, Ole Troan <otroan@employees.org>
Message-ID: <CAAF34D8.163B0%wdec@cisco.com>
Thread-Topic: [Softwires] 4rd Address Mapping - version-01
Thread-Index: AcyBoH5D51Qe4VKi7kunNpEUOb2GBQ==
In-Reply-To: <CAH3bfACG52APJNa2RxEmyyvG7QoEaQMo9i31gA-ZNco7w2ASTw@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3400479962_26568776"
X-OriginalArrivalTime: 03 Oct 2011 07:46:03.0498 (UTC) FILETIME=[80592CA0:01CC81A0]
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 03 Oct 2011 07:43:05 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3400479962_26568776
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable




On 02/10/2011 02:58, "Qiong" <bingxuere@gmail.com> wrote:

> Hi Ole and Remi,
>=20
>>> > This is my answer to your first (double) question.
>>> > If it is not enough, as suggested below, please explain what you don'=
t
>>> understand.
>>=20
>> I specifically do not want a solution that changes forwarding behaviour =
for
>> _all_ IPv6 packets.
>> e.g. looking at 24 bits in the middle of an IPv6 address is such a chang=
e.
>>=20
>> Woj> What are you referring to? Routing =B3just works=B2 as normal and is no=
n
>> disaggregated because of the CE-index in the prefix. Classification can/=
is
>> done on a subset of the v6 address, and that is perfectly legit.
>>=20
>> I don't understand what requirements you are basing this 'solution' on.
>> if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out =
of
>> the delegated prefix. then why do you need any of that?
> =A0
> Qiong : I agree that routing lookup for a=A0provisioned=A0/64 prefix would be
> better that extracting certain bits for each IPv6 address in CE. This wou=
ld
> bring less change to existing routing model.
>=20
> Woj> There is no change to the existing destination based routing model. =
Each
> CE is uniquely addressed by the CE bits in the top /64 =AD ie the CE index =
is as
> proposed by all the 4rd and divi-pd drafts. The full v4 source address of=
 each
> CE is however also embedded in the interface-id, as per RFC6052. There ap=
pears
> to be no cost for this operation, and has the upside of the full v4 info
> visible in the header and allowing source based classification (should on=
e
> want to do that).
>=20
> Regards,
> Woj.
>=20
> Best wishes
>=20
> Qiong=A0
>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20
>=20


--B_3400479962_26568776
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Softwires] 4rd Address Mapping - version-01</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'><BR>
<BR>
<BR>
On 02/10/2011 02:58, &quot;Qiong&quot; &lt;<a href=3D"bingxuere@gmail.com">bi=
ngxuere@gmail.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'>Hi Ole and Remi,<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'>&gt; This is my answer to your first (double) qu=
estion.<BR>
&gt; If it is not enough, as suggested below, please explain what you don't=
 understand.<BR>
<BR>
I specifically do not want a solution that changes forwarding behaviour for=
 _all_ IPv6 packets.<BR>
e.g. looking at 24 bits in the middle of an IPv6 address is such a change.<=
BR>
<BR>
Woj&gt; What are you referring to? Routing &#8220;just works&#8221; as norm=
al and is non disaggregated because of the CE-index in the prefix. Classific=
ation can/is done on a subset of the v6 address, and that is perfectly legit=
.<BR>
<BR>
I don't understand what requirements you are basing this 'solution' on.<BR>
if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out of =
the delegated prefix. then why do you need any of that?<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial">=
<SPAN STYLE=3D'font-size:11pt'>=A0<BR>
Qiong : I agree that routing lookup for a=A0provisioned=A0/64 prefix would be b=
etter that extracting certain bits for each IPv6 address in CE. This would b=
ring less change to existing routing model.<BR>
<BR>
Woj&gt; There is no change to the existing destination based routing model.=
 Each CE is uniquely addressed by the CE bits in the top /64 &#8211; ie the =
CE index is as proposed by all the 4rd and divi-pd drafts. The full v4 sourc=
e address of each CE is however also embedded in the interface-id, as per RF=
C6052. There appears to be no cost for this operation, and has the upside of=
 the full v4 info visible in the header and allowing source based classifica=
tion (should one want to do that). <BR>
<BR>
Regards,<BR>
Woj.<BR>
<BR>
Best wishes<BR>
<BR>
Qiong=A0<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'>_______________________________________________<=
BR>
Softwires mailing list<BR>
<a href=3D"Softwires@ietf.org">Softwires@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.=
org/mailman/listinfo/softwires</a><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial">=
<SPAN STYLE=3D'font-size:11pt'><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3400479962_26568776--


From bingxuere@gmail.com  Mon Oct  3 09:11:12 2011
Return-Path: <bingxuere@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 C4E8821F8BDC for <softwires@ietfa.amsl.com>; Mon,  3 Oct 2011 09:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.534
X-Spam-Level: 
X-Spam-Status: No, score=-3.534 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PyFApWzRANHe for <softwires@ietfa.amsl.com>; Mon,  3 Oct 2011 09:11:12 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id DFC1E21F8BDB for <softwires@ietf.org>; Mon,  3 Oct 2011 09:11:11 -0700 (PDT)
Received: by ywm3 with SMTP id 3so1252390ywm.31 for <softwires@ietf.org>; Mon, 03 Oct 2011 09:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=M1osjtou3dk73/75FarnDeqv7tvHkNHTjwfK3mNZyjE=; b=GserulhlJZOlx03UgKSSP0cJcnJHMrL5ZhKS8cbBMJyPdPzRbNcWr+JJo3/vGf93MR kO7vbXq15ntDwMwbc31KVV8Bychn2+Nwz5bZVY0xPgvnIGR0DLDZncTXrsZhvTviFh7E mG+LqFGkufEf5P5ehdjm/CwIKs2p/BeFz6ay0=
Received: by 10.42.134.2 with SMTP id j2mr139648ict.149.1317658454235; Mon, 03 Oct 2011 09:14:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Mon, 3 Oct 2011 09:13:53 -0700 (PDT)
In-Reply-To: <CAAF34D8.163B0%wdec@cisco.com>
References: <CAH3bfACG52APJNa2RxEmyyvG7QoEaQMo9i31gA-ZNco7w2ASTw@mail.gmail.com> <CAAF34D8.163B0%wdec@cisco.com>
From: Qiong <bingxuere@gmail.com>
Date: Tue, 4 Oct 2011 00:13:53 +0800
Message-ID: <CAH3bfAB9-2SwjKQM2+rAGYyBhcHiDP-54GngnKos6cu_N56CzA@mail.gmail.com>
To: Wojciech Dec <wdec@cisco.com>
Content-Type: multipart/alternative; boundary=90e6ba6e8dba199a9904ae6744e6
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 03 Oct 2011 16:11:12 -0000

--90e6ba6e8dba199a9904ae6744e6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Remi and Wojciech,

Thanks for your clarification. I fully agree with you that embedding the
full IPv4 address in the last 64 bits would be quite helpful for some kind
of source address classification and I also suggest that this can be taken
in the same way for encapsulation-based approach. It would be easier for
systems in-the-middle to identify the IPv4 address without packet
decapsulation.

I guess the thing that Ole has mentioned to "look at 24 bits in the middle
of IPv6 address" is for CE to determine whether a downstream IPv6 packet
should be taken for translation or native forwarding. Here, for a dual-stac=
k
host, there would be no difference in the first /64 bits for a native IPv6
packet and a translated packet. What's why the CE should further looking
into the last 64 bits to determine the translation process or native
forwarding. Maybe Ole can clarify for this part again.

However, the situation would still be different in "Hub & Spoke" and "Mesh"
mode. For Hub & Spoke case, since BR will have a default prefix/address, it
would be easily to identify the translated traffic from native IPv6 traffic
by just doing source address routing lookup for a downstream packet. So, th=
e
corresponding mechanics would be different.

Thanks

Best wishes

Qiong

2011/10/3 Wojciech Dec <wdec@cisco.com>

>
>
>
> On 02/10/2011 02:58, "Qiong" <bingxuere@gmail.com> wrote:
>
> Hi Ole and Remi,
>
> > This is my answer to your first (double) question.
> > If it is not enough, as suggested below, please explain what you don't
> understand.
>
> I specifically do not want a solution that changes forwarding behaviour f=
or
> _all_ IPv6 packets.
> e.g. looking at 24 bits in the middle of an IPv6 address is such a change=
.
>
> Woj> What are you referring to? Routing =E2=80=9Cjust works=E2=80=9D as n=
ormal and is non
> disaggregated because of the CE-index in the prefix. Classification can/i=
s
> done on a subset of the v6 address, and that is perfectly legit.
>
>
> I don't understand what requirements you are basing this 'solution' on.
> if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out o=
f
> the delegated prefix. then why do you need any of that?
>
>
> Qiong : I agree that routing lookup for a provisioned /64 prefix would be
> better that extracting certain bits for each IPv6 address in CE. This wou=
ld
> bring less change to existing routing model.
>
> Woj> There is no change to the existing destination based routing model.
> Each CE is uniquely addressed by the CE bits in the top /64 =E2=80=93 ie =
the CE
> index is as proposed by all the 4rd and divi-pd drafts. The full v4 sourc=
e
> address of each CE is however also embedded in the interface-id, as per
> RFC6052. There appears to be no cost for this operation, and has the upsi=
de
> of the full v4 info visible in the header and allowing source based
> classification (should one want to do that).
>
> Regards,
> Woj.
>
> Best wishes
>
> Qiong
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>
>
>

--90e6ba6e8dba199a9904ae6744e6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Remi and=C2=A0Wojciech,<div><br></div><div>Thanks for your clarification=
. I fully agree with you that embedding the full IPv4 address in the last 6=
4 bits would be quite helpful for some kind of source address classificatio=
n and I also suggest that this can be taken in the same way for encapsulati=
on-based approach. It would be easier for systems in-the-middle to identify=
 the IPv4 address without packet decapsulation.=C2=A0</div>

<div><br></div><div>I guess the thing that Ole has mentioned to &quot;look =
at 24 bits in the middle of IPv6 address&quot; is for CE to determine wheth=
er a downstream IPv6 packet should be taken for translation or native forwa=
rding. Here, for a dual-stack host, there would be no difference in the fir=
st /64 bits for a native IPv6 packet and a translated packet. What&#39;s wh=
y the CE should further looking into the last 64 bits to determine the tran=
slation process or native forwarding. Maybe Ole can clarify for this part a=
gain.</div>

<div><br></div><div>However, the situation would still be different in &quo=
t;Hub &amp; Spoke&quot; and &quot;Mesh&quot; mode. For Hub &amp; Spoke case=
, since BR will have a default prefix/address, it would be easily to identi=
fy the translated traffic from native IPv6 traffic by just doing source add=
ress=C2=A0routing lookup for a downstream packet. So, the corresponding=C2=
=A0mechanics=C2=A0would be different.</div>

<div><br></div><div>Thanks=C2=A0</div><div><br></div><div>Best wishes</div>=
<div><br></div><div>Qiong</div><div><br><div class=3D"gmail_quote">2011/10/=
3 Wojciech Dec <span dir=3D"ltr">&lt;<a href=3D"mailto:wdec@cisco.com">wdec=
@cisco.com</a>&gt;</span><br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">



<div><div class=3D"im">
<font face=3D"Calibri, Verdana, Helvetica, Arial"><span style=3D"font-size:=
11pt"><br>
<br>
<br>
On 02/10/2011 02:58, &quot;Qiong&quot; &lt;<a href=3D"http://bingxuere@gmai=
l.com" target=3D"_blank">bingxuere@gmail.com</a>&gt; wrote:<br>
<br>
</span></font></div><blockquote><font face=3D"Calibri, Verdana, Helvetica, =
Arial"><span style=3D"font-size:11pt">Hi Ole and Remi,<br>
<br>
</span></font><blockquote><font face=3D"Calibri, Verdana, Helvetica, Arial"=
><span style=3D"font-size:11pt"><div class=3D"im">&gt; This is my answer to=
 your first (double) question.<br>
&gt; If it is not enough, as suggested below, please explain what you don&#=
39;t understand.<br>
<br>
I specifically do not want a solution that changes forwarding behaviour for=
 _all_ IPv6 packets.<br>
e.g. looking at 24 bits in the middle of an IPv6 address is such a change.<=
br>
<br></div>
Woj&gt; What are you referring to? Routing =E2=80=9Cjust works=E2=80=9D as =
normal and is non disaggregated because of the CE-index in the prefix. Clas=
sification can/is done on a subset of the v6 address, and that is perfectly=
 legit.<div class=3D"im">

<br>
<br>
I don&#39;t understand what requirements you are basing this &#39;solution&=
#39; on.<br>
if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out of =
the delegated prefix. then why do you need any of that?<br>
</div></span></font></blockquote><font face=3D"Calibri, Verdana, Helvetica,=
 Arial"><span style=3D"font-size:11pt"><div class=3D"im">=C2=A0<br>
Qiong : I agree that routing lookup for a=C2=A0provisioned=C2=A0/64 prefix =
would be better that extracting certain bits for each IPv6 address in CE. T=
his would bring less change to existing routing model.<br>
<br></div>
Woj&gt; There is no change to the existing destination based routing model.=
 Each CE is uniquely addressed by the CE bits in the top /64 =E2=80=93 ie t=
he CE index is as proposed by all the 4rd and divi-pd drafts. The full v4 s=
ource address of each CE is however also embedded in the interface-id, as p=
er RFC6052. There appears to be no cost for this operation, and has the ups=
ide of the full v4 info visible in the header and allowing source based cla=
ssification (should one want to do that). <br>


<br>
Regards,<br>
Woj.<br>
<br>
Best wishes<br>
<br>
Qiong=C2=A0<br>
<br>
</span></font><div class=3D"im"><blockquote><font face=3D"Calibri, Verdana,=
 Helvetica, Arial"><span style=3D"font-size:11pt">_________________________=
______________________<br>
Softwires mailing list<br>
<a href=3D"http://Softwires@ietf.org" target=3D"_blank">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>
</span></font></blockquote><font face=3D"Calibri, Verdana, Helvetica, Arial=
"><span style=3D"font-size:11pt"><br>
<br>
</span></font></div></blockquote>
</div>


</blockquote></div><br></div>

--90e6ba6e8dba199a9904ae6744e6--

From despres.remi@laposte.net  Mon Oct  3 09:39:58 2011
Return-Path: <despres.remi@laposte.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 725A421F8BF6 for <softwires@ietfa.amsl.com>; Mon,  3 Oct 2011 09:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.862
X-Spam-Level: 
X-Spam-Status: No, score=-1.862 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68k0nwG+k78T for <softwires@ietfa.amsl.com>; Mon,  3 Oct 2011 09:39:57 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.121]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3F821F8BD3 for <softwires@ietf.org>; Mon,  3 Oct 2011 09:39:56 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2517.sfr.fr (SMTP Server) with ESMTP id 6615F70000F6; Mon,  3 Oct 2011 18:42:58 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2517.sfr.fr (SMTP Server) with ESMTP id 98E6F70000F0; Mon,  3 Oct 2011 18:42:57 +0200 (CEST)
X-SFR-UUID: 20111003164257626.98E6F70000F0@msfrf2517.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-2-28959101
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAH3bfAB9-2SwjKQM2+rAGYyBhcHiDP-54GngnKos6cu_N56CzA@mail.gmail.com>
Date: Mon, 3 Oct 2011 18:42:55 +0800
Message-Id: <BF26931C-CE7A-43A3-95AE-E31330E1532E@laposte.net>
References: <CAH3bfACG52APJNa2RxEmyyvG7QoEaQMo9i31gA-ZNco7w2ASTw@mail.gmail.com> <CAAF34D8.163B0%wdec@cisco.com> <CAH3bfAB9-2SwjKQM2+rAGYyBhcHiDP-54GngnKos6cu_N56CzA@mail.gmail.com>
To: Qiong <bingxuere@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Wojciech Dec <wdec@cisco.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 03 Oct 2011 16:39:58 -0000

--Apple-Mail-2-28959101
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Qiong,

Some fields of a unified address format for double translation and =
encapsulation might be unnecessary for hub and spoke, but using the same =
format should be advantageous for maintenance and training if for =
nothing else (assuming that any added complexity is negligible enough).

Believing that a completely unified format is possible, I mentioned it =
to Alain.
Also, I volunteered to be editor-coordinator for this to happen, but =
decision of who does what is his.

Regards,
RD


Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit :

> Hi Remi and Wojciech,
>=20
> Thanks for your clarification. I fully agree with you that embedding =
the full IPv4 address in the last 64 bits would be quite helpful for =
some kind of source address classification and I also suggest that this =
can be taken in the same way for encapsulation-based approach. It would =
be easier for systems in-the-middle to identify the IPv4 address without =
packet decapsulation.=20
>=20
> I guess the thing that Ole has mentioned to "look at 24 bits in the =
middle of IPv6 address" is for CE to determine whether a downstream IPv6 =
packet should be taken for translation or native forwarding. Here, for a =
dual-stack host, there would be no difference in the first /64 bits for =
a native IPv6 packet and a translated packet. What's why the CE should =
further looking into the last 64 bits to determine the translation =
process or native forwarding. Maybe Ole can clarify for this part again.
>=20
> However, the situation would still be different in "Hub & Spoke" and =
"Mesh" mode. For Hub & Spoke case, since BR will have a default =
prefix/address, it would be easily to identify the translated traffic =
from native IPv6 traffic by just doing source address routing lookup for =
a downstream packet. So, the corresponding mechanics would be different.
>=20
> Thanks=20
>=20
> Best wishes
>=20
> Qiong
>=20
> 2011/10/3 Wojciech Dec <wdec@cisco.com>
>=20
>=20
>=20
> On 02/10/2011 02:58, "Qiong" <bingxuere@gmail.com> wrote:
>=20
> Hi Ole and Remi,
>=20
> > This is my answer to your first (double) question.
> > If it is not enough, as suggested below, please explain what you =
don't understand.
>=20
> I specifically do not want a solution that changes forwarding =
behaviour for _all_ IPv6 packets.
> e.g. looking at 24 bits in the middle of an IPv6 address is such a =
change.
>=20
> Woj> What are you referring to? Routing =93just works=94 as normal and =
is non disaggregated because of the CE-index in the prefix. =
Classification can/is done on a subset of the v6 address, and that is =
perfectly legit.
>=20
>=20
> I don't understand what requirements you are basing this 'solution' =
on.
> if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix =
out of the delegated prefix. then why do you need any of that?
> =20
> Qiong : I agree that routing lookup for a provisioned /64 prefix would =
be better that extracting certain bits for each IPv6 address in CE. This =
would bring less change to existing routing model.
>=20
> Woj> There is no change to the existing destination based routing =
model. Each CE is uniquely addressed by the CE bits in the top /64 =96 =
ie the CE index is as proposed by all the 4rd and divi-pd drafts. The =
full v4 source address of each CE is however also embedded in the =
interface-id, as per RFC6052. There appears to be no cost for this =
operation, and has the upside of the full v4 info visible in the header =
and allowing source based classification (should one want to do that).=20=

>=20
> Regards,
> Woj.
>=20
> Best wishes
>=20
> Qiong=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>=20
>=20
>=20


--Apple-Mail-2-28959101
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Qiong,<div><br></div><div>Some fields of a unified address format for =
double translation and encapsulation might be unnecessary for hub and =
spoke, but using the same format should be advantageous for maintenance =
and training if for nothing else (assuming that any added complexity is =
negligible enough).</div><div><br></div><div>Believing that a completely =
unified format is possible, I&nbsp;mentioned it to =
Alain.</div><div>Also, I volunteered to be editor-coordinator for this =
to happen, but decision of who does what is =
his.</div><div><br></div><div>Regards,</div><div>RD</div><div><br></div><d=
iv><br></div><div><div><div>Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit =
:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Hi Remi and&nbsp;Wojciech,<div><br></div><div>Thanks for =
your clarification. I fully agree with you that embedding the full IPv4 =
address in the last 64 bits would be quite helpful for some kind of =
source address classification and I also suggest that this can be taken =
in the same way for encapsulation-based approach. It would be easier for =
systems in-the-middle to identify the IPv4 address without packet =
decapsulation.&nbsp;</div>

<div><br></div><div>I guess the thing that Ole has mentioned to "look at =
24 bits in the middle of IPv6 address" is for CE to determine whether a =
downstream IPv6 packet should be taken for translation or native =
forwarding. Here, for a dual-stack host, there would be no difference in =
the first /64 bits for a native IPv6 packet and a translated packet. =
What's why the CE should further looking into the last 64 bits to =
determine the translation process or native forwarding. Maybe Ole can =
clarify for this part again.</div>

<div><br></div><div>However, the situation would still be different in =
"Hub &amp; Spoke" and "Mesh" mode. For Hub &amp; Spoke case, since BR =
will have a default prefix/address, it would be easily to identify the =
translated traffic from native IPv6 traffic by just doing source =
address&nbsp;routing lookup for a downstream packet. So, the =
corresponding&nbsp;mechanics&nbsp;would be different.</div>

<div><br></div><div>Thanks&nbsp;</div><div><br></div><div>Best =
wishes</div><div><br></div><div>Qiong</div><div><br><div =
class=3D"gmail_quote">2011/10/3 Wojciech Dec <span dir=3D"ltr">&lt;<a =
href=3D"mailto:wdec@cisco.com">wdec@cisco.com</a>&gt;</span><br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">



<div><div class=3D"im">
<font face=3D"Calibri, Verdana, Helvetica, Arial"><span =
style=3D"font-size:11pt"><br>
<br>
<br>
On 02/10/2011 02:58, "Qiong" &lt;<a href=3D"http://bingxuere@gmail.com/" =
target=3D"_blank">bingxuere@gmail.com</a>&gt; wrote:<br>
<br>
</span></font></div><blockquote><font face=3D"Calibri, Verdana, =
Helvetica, Arial"><span style=3D"font-size:11pt">Hi Ole and Remi,<br>
<br>
</span></font><blockquote><font face=3D"Calibri, Verdana, Helvetica, =
Arial"><span style=3D"font-size:11pt"><div class=3D"im">&gt; This is my =
answer to your first (double) question.<br>
&gt; If it is not enough, as suggested below, please explain what you =
don't understand.<br>
<br>
I specifically do not want a solution that changes forwarding behaviour =
for _all_ IPv6 packets.<br>
e.g. looking at 24 bits in the middle of an IPv6 address is such a =
change.<br>
<br></div>
Woj&gt; What are you referring to? Routing =93just works=94 as normal =
and is non disaggregated because of the CE-index in the prefix. =
Classification can/is done on a subset of the v6 address, and that is =
perfectly legit.<div class=3D"im">

<br>
<br>
I don't understand what requirements you are basing this 'solution' =
on.<br>
if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out =
of the delegated prefix. then why do you need any of that?<br>
</div></span></font></blockquote><font face=3D"Calibri, Verdana, =
Helvetica, Arial"><span style=3D"font-size:11pt"><div =
class=3D"im">&nbsp;<br>
Qiong : I agree that routing lookup for a&nbsp;provisioned&nbsp;/64 =
prefix would be better that extracting certain bits for each IPv6 =
address in CE. This would bring less change to existing routing =
model.<br>
<br></div>
Woj&gt; There is no change to the existing destination based routing =
model. Each CE is uniquely addressed by the CE bits in the top /64 =96 =
ie the CE index is as proposed by all the 4rd and divi-pd drafts. The =
full v4 source address of each CE is however also embedded in the =
interface-id, as per RFC6052. There appears to be no cost for this =
operation, and has the upside of the full v4 info visible in the header =
and allowing source based classification (should one want to do that). =
<br>


<br>
Regards,<br>
Woj.<br>
<br>
Best wishes<br>
<br>
Qiong&nbsp;<br>
<br>
</span></font><div class=3D"im"><blockquote><font face=3D"Calibri, =
Verdana, Helvetica, Arial"><span =
style=3D"font-size:11pt">_______________________________________________<b=
r>
Softwires mailing list<br>
<a href=3D"http://Softwires@ietf.org/" =
target=3D"_blank">Softwires@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</span></font></blockquote><font face=3D"Calibri, Verdana, Helvetica, =
Arial"><span style=3D"font-size:11pt"><br>
<br>
</span></font></div></blockquote>
</div>


</blockquote></div><br></div>
</blockquote></div><br></div></body></html>=

--Apple-Mail-2-28959101--

From dxhbupt@gmail.com  Tue Oct  4 00:22:58 2011
Return-Path: <dxhbupt@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 48E3921F8BF6 for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 00:22:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level: 
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cKsq5PIWsJMX for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 00:22:57 -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 D827821F8BEF for <softwires@ietf.org>; Tue,  4 Oct 2011 00:22:56 -0700 (PDT)
Received: by wyh21 with SMTP id 21so221198wyh.31 for <softwires@ietf.org>; Tue, 04 Oct 2011 00:26:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=KxJ63OfSDKzUi8YZkWHoyzIcg4ciD0vWpsTbVRU7i84=; b=tBoLmsYZxWe++EcXPI8X0paP9Q2FRXwSJoRAepyrV0q7n4NjuQqZ9eBEZbM9RxjgVW 7IFnggI8xmPFOLTj2g9liHSKENpTAOcl/Lu8GXbt4oLUsYyhl/eWhi/FDouiSkqvg3hE ZNXJQ1SWcsA17PXvGl+pBDADCXp7U2lPYsr7s=
MIME-Version: 1.0
Received: by 10.216.132.129 with SMTP id o1mr4808127wei.3.1317713160659; Tue, 04 Oct 2011 00:26:00 -0700 (PDT)
Received: by 10.180.104.202 with HTTP; Tue, 4 Oct 2011 00:26:00 -0700 (PDT)
Date: Tue, 4 Oct 2011 15:26:00 +0800
Message-ID: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com>
From: xiaohong deng <dxhbupt@gmail.com>
To: wdec@cisco.com, despres.remi@laposte.net, otroan@employees.org,  bingxuere@gmail.com, softwires@ietf.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 04 Oct 2011 07:22:58 -0000

Hi Remi, Ole, Woj, and all,

I understand the argument of IID bits is resulted from a last minute
agreement between 4rd and divi-pd people that having full IPv4 address
embedded in the address format helps source based classification, but
before we argue that, shall we first make this agreement also be
accepted by community wide? As far as current time-being concerned, I
don't see a consensus has been reached on this agreement from
community wide.

It IMHO would be helpful if anybody would clarify some details to 1)
first prove source based classification is either a valid or a
non-valid requirement for address mapping; For this regard, I would
begin with that why do we think the source based IPv4 classification
ability instead of the more general five-tuple based IPv4
classification ability should be reserved, when deliver IPv4 over
IPv6?


and 2) then show us how much other efforts are required to achieve so
besides address format definition itself, in other words, if it's a
valid requirement, let's first have feasibility of this requirement
analyzed from both deployment and operational perspectives:

1. For double translation, how does a traditional router perform the
source based IPv4 packet classification on IPv6 (translated from IPv4)
packets? Or does it suggest that using IPv6 classification filters to
filter IPv4 packets? If so, should we also note that this suggests
IPv4 operation and managed are tightly coupled with IPv6 operation and
management? which in turn implies complexity in operational, or put in
other words, OPEX increasing, the last thing among others that
operators would like to see.

2. For encapsulation, even if embedding source IPv4 addresses in the
lower bits of the address formats, where does the router find the
source port without de-capsulation? Are you suggesting also encode 16
bits port in the lower part of address? In either case, it leads to
the concerns of increased OPEX to operators stated above.

Thoughts?

Cheers,
Xiaohong

> Hi Qiong,
>
> Some fields of a unified address format for double translation and
> encapsulation might be unnecessary for hub and spoke, but using the
> same format should be advantageous for maintenance and training if for
> nothing else (assuming that any added complexity is negligible
> enough).
>
> Believing that a completely unified format is possible, I mentioned it to=
 Alain.
> Also, I volunteered to be editor-coordinator for this to happen, but
> decision of who does what is his.
>
> Regards,
> RD
>
>
> Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit :
>
>> Hi Remi and Wojciech,
>>
>> Thanks for your clarification. I fully agree with you that embedding the=
 full IPv4 address in the last 64 bits would be quite helpful for some kind=
 of source address classification and I also suggest that this can be taken=
 in the same way for encapsulation-based approach. It would be easier for s=
ystems in-the-middle to identify the IPv4 address without packet decapsulat=
ion.
>>
>> I guess the thing that Ole has mentioned to "look at 24 bits in the midd=
le of IPv6 address" is for CE to determine whether a downstream IPv6 packet=
 should be taken for translation or native forwarding. Here, for a dual-sta=
ck host, there would be no difference in the first /64 bits for a native IP=
v6 packet and a translated packet. What's why the CE should further looking=
 into the last 64 bits to determine the translation process or native forwa=
rding. Maybe Ole can clarify for this part again.
>>
>> However, the situation would still be different in "Hub & Spoke" and "Me=
sh" mode. For Hub & Spoke case, since BR will have a default prefix/address=
, it would be easily to identify the translated traffic from native IPv6 tr=
affic by just doing source address routing lookup for a downstream packet. =
So, the corresponding mechanics would be different.
>>
>> Thanks
>>
>> Best wishes
>>
>> Qiong
>>
>> 2011/10/3 Wojciech Dec <wdec at cisco.com>
>>
>>
>>
>>
>>     On 02/10/2011 02:58, "Qiong" <bingxuere at gmail.com> wrote:
>>
>>         Hi Ole and Remi,
>>
>>             > This is my answer to your first (double) question.
>>             > If it is not enough, as suggested below, please explain wh=
at you don't understand.
>>
>>             I specifically do not want a solution that changes forwardin=
g behaviour for _all_ IPv6 packets.
>>             e.g. looking at 24 bits in the middle of an IPv6 address is =
such a change.
>>
>>             Woj> What are you referring to? Routing =93just works=94 as =
normal and is non disaggregated because of the CE-index in the prefix. Clas=
sification can/is done on a subset of the v6 address, and that is perfectly=
 legit.
>>
>>
>>             I don't understand what requirements you are basing this 'so=
lution' on.
>>             if the 4rd / dIVI CE takes (a well known or provisioned) /64=
 prefix out of the delegated prefix. then why do you need any of that?
>>
>>
>>         Qiong : I agree that routing lookup for a provisioned /64 prefix=
 would be better that extracting certain bits for each IPv6 address in CE. =
This would bring less change to existing routing model.
>>
>>         Woj> There is no change to the existing destination based routin=
g model. Each CE is uniquely addressed by the CE bits in the top /64 =96 ie=
 the CE index is as proposed by all the 4rd and divi-pd drafts. The full v4=
 source address of each CE is however also embedded in the interface-id, as=
 per RFC6052. There appears to be no cost for this operation, and has the u=
pside of the full v4 info visible in the header and allowing source based c=
lassification (should one want to do that).
>>
>>         Regards,
>>         Woj.
>>
>>         Best wishes
>>
>>         Qiong
>>
>>             _______________________________________________
>>             Softwires mailing list
>>             Softwires at ietf.org
>>             https://www.ietf.org/mailman/listinfo/softwires
>>
>>
>>
>

From despres.remi@laposte.net  Tue Oct  4 01:31:48 2011
Return-Path: <despres.remi@laposte.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 3EEF721F8D51 for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 01:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.863
X-Spam-Level: 
X-Spam-Status: No, score=-1.863 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FO0RjCidmM0F for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 01:31:47 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by ietfa.amsl.com (Postfix) with ESMTP id 10F5021F8D4B for <softwires@ietf.org>; Tue,  4 Oct 2011 01:31:47 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2402.sfr.fr (SMTP Server) with ESMTP id A83757000061; Tue,  4 Oct 2011 10:34:50 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2402.sfr.fr (SMTP Server) with ESMTP id DA8C2700005E; Tue,  4 Oct 2011 10:34:45 +0200 (CEST)
X-SFR-UUID: 20111004083445895.DA8C2700005E@msfrf2402.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com>
Date: Tue, 4 Oct 2011 10:34:44 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D3CDD5C-89EE-4FD0-9689-8DA862E7172F@laposte.net>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com>
To: xiaohong deng <dxhbupt@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: softwires@ietf.org, wdec@cisco.com
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 04 Oct 2011 08:31:48 -0000

Xiaohong,

Thanks for you contribution for this debate.
More below.

Le 4 oct. 2011 =E0 15:26, xiaohong deng a =E9crit :

> Hi Remi, Ole, Woj, and all,
>=20
> I understand the argument of IID bits is resulted from a last minute
> agreement between 4rd and divi-pd people that having full IPv4 address
> embedded in the address format helps source based classification,

The agreement is just between those who participated.
In no way does it commit the group to anything.

Yet I believed it was useful to inform the group that something was =
found possible, in common by some proponents of encapsulation and =
double-translation solutions.

> but
> before we argue that, shall we first make this agreement also be
> accepted by community wide?

No WG agreement can obviously be reached before an open exchange of =
views.
Exchanging arguments is a necessary part of this process.=20

> As far as current time-being concerned, I
> don't see a consensus has been reached on this agreement from
> community wide.

Very clear.

> It IMHO would be helpful if anybody would clarify some details to 1)
> first prove source based classification is either a valid or a
> non-valid requirement for address mapping; For this regard, I would
> begin with that why do we think the source based IPv4 classification
> ability instead of the more general five-tuple based IPv4
> classification ability should be reserved, when deliver IPv4 over
> IPv6?

After having checked details of our common understanding with Xing, =
Congxiao and Wojciech, I will very soon communicate what we found =
promising.
Sorry for the time it took us.

> and 2) then show us how much other efforts are required to achieve so
> besides address format definition itself, in other words, if it's a
> valid requirement, let's first have feasibility of this requirement
> analyzed from both deployment and operational perspectives:
>=20
> 1. For double translation, how does a traditional router perform the
> source based IPv4 packet classification on IPv6 (translated from IPv4)
> packets? Or does it suggest that using IPv6 classification filters to
> filter IPv4 packets?

The latter was my understanding.
With it, filters on IPv4-address, and IPv4-shared-addreses, can be =
exercised in existing devices if having appropriately configured =
IPv6-address filters.
If this can be achieved with negligible capex and opex costs, and =
without obligation to do it, why not?=20
 =20

> If so, should we also note that this suggests
> IPv4 operation and managed are tightly coupled with IPv6 operation and
> management? which in turn implies complexity in operational, or put in
> other words,

> OPEX increasing, the last thing among others that
> operators would like to see.

Indeed, keeping in mind also that a single well chosen standard tends to =
reduce overall costs.

> 2. For encapsulation, even if embedding source IPv4 addresses in the
> lower bits of the address formats, where does the router find the
> source port without de-capsulation? Are you suggesting also encode 16
> bits port in the lower part of address? In either case, it leads to
> the concerns of increased OPEX to operators stated above.
>=20
> Thoughts?

An expectation is that copying an available information into a fixed =
part of an IID shouldn't be expensive at all, and that having IPv4 =
addresses and port-set IDs in clear form in IPv6 addresses should =
facilitate maintenance, even if no filter is configured.

Cheers,
RD


> Cheers,
> Xiaohong
>=20
>> Hi Qiong,
>>=20
>> Some fields of a unified address format for double translation and
>> encapsulation might be unnecessary for hub and spoke, but using the
>> same format should be advantageous for maintenance and training if =
for
>> nothing else (assuming that any added complexity is negligible
>> enough).
>>=20
>> Believing that a completely unified format is possible, I mentioned =
it to Alain.
>> Also, I volunteered to be editor-coordinator for this to happen, but
>> decision of who does what is his.
>>=20
>> Regards,
>> RD
>>=20
>>=20
>> Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit :
>>=20
>>> Hi Remi and Wojciech,
>>>=20
>>> Thanks for your clarification. I fully agree with you that embedding =
the full IPv4 address in the last 64 bits would be quite helpful for =
some kind of source address classification and I also suggest that this =
can be taken in the same way for encapsulation-based approach. It would =
be easier for systems in-the-middle to identify the IPv4 address without =
packet decapsulation.
>>>=20
>>> I guess the thing that Ole has mentioned to "look at 24 bits in the =
middle of IPv6 address" is for CE to determine whether a downstream IPv6 =
packet should be taken for translation or native forwarding. Here, for a =
dual-stack host, there would be no difference in the first /64 bits for =
a native IPv6 packet and a translated packet. What's why the CE should =
further looking into the last 64 bits to determine the translation =
process or native forwarding. Maybe Ole can clarify for this part again.
>>>=20
>>> However, the situation would still be different in "Hub & Spoke" and =
"Mesh" mode. For Hub & Spoke case, since BR will have a default =
prefix/address, it would be easily to identify the translated traffic =
from native IPv6 traffic by just doing source address routing lookup for =
a downstream packet. So, the corresponding mechanics would be different.
>>>=20
>>> Thanks
>>>=20
>>> Best wishes
>>>=20
>>> Qiong
>>>=20
>>> 2011/10/3 Wojciech Dec <wdec at cisco.com>
>>>=20
>>>=20
>>>=20
>>>=20
>>>    On 02/10/2011 02:58, "Qiong" <bingxuere at gmail.com> wrote:
>>>=20
>>>        Hi Ole and Remi,
>>>=20
>>>> This is my answer to your first (double) question.
>>>> If it is not enough, as suggested below, please explain what you =
don't understand.
>>>=20
>>>            I specifically do not want a solution that changes =
forwarding behaviour for _all_ IPv6 packets.
>>>            e.g. looking at 24 bits in the middle of an IPv6 address =
is such a change.
>>>=20
>>>            Woj> What are you referring to? Routing =93just works=94 =
as normal and is non disaggregated because of the CE-index in the =
prefix. Classification can/is done on a subset of the v6 address, and =
that is perfectly legit.
>>>=20
>>>=20
>>>            I don't understand what requirements you are basing this =
'solution' on.
>>>            if the 4rd / dIVI CE takes (a well known or provisioned) =
/64 prefix out of the delegated prefix. then why do you need any of =
that?
>>>=20
>>>=20
>>>        Qiong : I agree that routing lookup for a provisioned /64 =
prefix would be better that extracting certain bits for each IPv6 =
address in CE. This would bring less change to existing routing model.
>>>=20
>>>        Woj> There is no change to the existing destination based =
routing model. Each CE is uniquely addressed by the CE bits in the top =
/64 =96 ie the CE index is as proposed by all the 4rd and divi-pd =
drafts. The full v4 source address of each CE is however also embedded =
in the interface-id, as per RFC6052. There appears to be no cost for =
this operation, and has the upside of the full v4 info visible in the =
header and allowing source based classification (should one want to do =
that).
>>>=20
>>>        Regards,
>>>        Woj.
>>>=20
>>>        Best wishes
>>>=20
>>>        Qiong
>>>=20
>>>            _______________________________________________
>>>            Softwires mailing list
>>>            Softwires at ietf.org
>>>            https://www.ietf.org/mailman/listinfo/softwires
>>>=20
>>>=20
>>>=20
>>=20
>=20

From wdec@cisco.com  Tue Oct  4 01:38:44 2011
Return-Path: <wdec@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 A10BB21F8C65 for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 01:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.325
X-Spam-Level: 
X-Spam-Status: No, score=-108.325 tagged_above=-999 required=5 tests=[AWL=0.878, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FYNcnfGaIKuE for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 01:38:43 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id EAA1921F8C64 for <softwires@ietf.org>; Tue,  4 Oct 2011 01:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=wdec@cisco.com; l=8354; q=dns/txt; s=iport; t=1317717707; x=1318927307; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=QqebdlkB7uzQtIRhpuTXrLf3YPtlxW3z3fMp4+JYUvg=; b=lfbZIFekof9orHLBIoILkrHcqTnPLs3vj8oHCc0CIUjac6xyqd9n4tIo oyY/MZgvtBdtVWLy1IaMLLXRPP0JhtgOWM2Sj2hcSNeJilEohUlGkwacj CLvk0dC5pSXE4v/OqtCE7i3/BaSEhwY6lI7IikPpgwpZgPGmCWvFEiBRw Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAKTFik6Q/khM/2dsb2JhbAA4CqcMbIEFgVMBAQEDAQEBAQ8BKQExEA0BCBhPBjABAQQBEhQHAQaHWgaZfwGeD4N2gywEh0iMHoUwhHCHJA
X-IronPort-AV: E=Sophos;i="4.68,484,1312156800"; d="scan'208";a="57040867"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 04 Oct 2011 08:41:46 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p948fkcV020422; Tue, 4 Oct 2011 08:41:46 GMT
Received: from xmb-ams-112.cisco.com ([144.254.74.87]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 4 Oct 2011 10:41:46 +0200
Received: from 10.55.90.88 ([10.55.90.88]) by XMB-AMS-112.cisco.com ([144.254.74.87]) with Microsoft Exchange Server HTTP-DAV ;  Tue,  4 Oct 2011 08:41:46 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Tue, 04 Oct 2011 10:41:41 +0200
From: Wojciech Dec <wdec@cisco.com>
To: xiaohong deng <dxhbupt@gmail.com>, <despres.remi@laposte.net>, <otroan@employees.org>, <bingxuere@gmail.com>, <softwires@ietf.org>
Message-ID: <CAB09365.1644F%wdec@cisco.com>
Thread-Topic: [Softwires] 4rd Address Mapping - version-01
Thread-Index: AcyCcXARSPwx+qDspkuHRrDj15Diwg==
In-Reply-To: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 04 Oct 2011 08:41:46.0788 (UTC) FILETIME=[73847E40:01CC8271]
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 04 Oct 2011 08:38:44 -0000

Hello Xiaohong,


On 04/10/2011 09:26, "xiaohong deng" <dxhbupt@gmail.com> wrote:

> Hi Remi, Ole, Woj, and all,
>=20
> I understand the argument of IID bits is resulted from a last minute
> agreement between 4rd and divi-pd people that having full IPv4 address
> embedded in the address format helps source based classification, but
> before we argue that, shall we first make this agreement also be
> accepted by community wide? As far as current time-being concerned, I
> don't see a consensus has been reached on this agreement from
> community wide.

Indeed, but we're hopefully close.

>=20
> It IMHO would be helpful if anybody would clarify some details to 1)
> first prove source based classification is either a valid or a
> non-valid requirement for address mapping; For this regard, I would
> begin with that why do we think the source based IPv4 classification
> ability instead of the more general five-tuple based IPv4
> classification ability should be reserved, when deliver IPv4 over
> IPv6?

Could you explain a bit more what you mean by "general five-tuple based IPv=
4
classification should be reserved, when deliver IPv4 over IPv6"?

>From my side, as I think was outlined earlier, the embedding of the source
addresses in the IID is desirable in order to have the full original IPv4 L=
3
at the IPv6 L3 level. If I interpret your five-tuple classification notion,
then this mapping provides exactly such capability for the translation case=
,
and comes at no-cost. At the interim meeting we agreed that the mapping
scheme needs to be unified and work for both encap and translation - this
one does. What is your alternative proposal?

>=20
>=20
> and 2) then show us how much other efforts are required to achieve so
> besides address format definition itself, in other words, if it's a
> valid requirement, let's first have feasibility of this requirement
> analyzed from both deployment and operational perspectives:
>=20
> 1. For double translation, how does a traditional router perform the
> source based IPv4 packet classification on IPv6 (translated from IPv4)
> packets? Or does it suggest that using IPv6 classification filters to
> filter IPv4 packets? If so, should we also note that this suggests
> IPv4 operation and managed are tightly coupled with IPv6 operation and
> management? which in turn implies complexity in operational, or put in
> other words, OPEX increasing, the last thing among others that
> operators would like to see.

This was discussed at the interim meeting - presentations from Hui and Xing
come to mind. I think it is fair to state that there are those operators wh=
o
believe strongly that having an IPv6 mapped representation of IPv4
addressing allows the use of IPv6 only data plane devices and provisioning
tools, which LOWERS the difficulty of deployment and Opex, as opposed to
having to upgrade routers and systems to manage an IPv4 data-plane over IPv=
6
- that would truly be extra opex. Some other operators may care less about
this, but this does not detract from the case of those that do.

>=20
> 2. For encapsulation, even if embedding source IPv4 addresses in the
> lower bits of the address formats, where does the router find the
> source port without de-capsulation? Are you suggesting also encode 16
> bits port in the lower part of address? In either case, it leads to
> the concerns of increased OPEX to operators stated above.

I don't see how this argument applies - the information to derive the
information that needs to be mapped is "automatic" and comes for free with
the algorithms. Perhaps it is useful to note that the "encapsulating router=
"
needs to look at L4 info anyway. Similarly, the full IPv4 address and
port-set-id is available for each packet passed by the router. Placing that
info in the IID, or any other set of bits is, computationally the same.

Regards,
Woj.
>=20
> Thoughts?
>=20
> Cheers,
> Xiaohong
>=20
>> Hi Qiong,
>>=20
>> Some fields of a unified address format for double translation and
>> encapsulation might be unnecessary for hub and spoke, but using the
>> same format should be advantageous for maintenance and training if for
>> nothing else (assuming that any added complexity is negligible
>> enough).
>>=20
>> Believing that a completely unified format is possible, I mentioned it t=
o
>> Alain.
>> Also, I volunteered to be editor-coordinator for this to happen, but
>> decision of who does what is his.
>>=20
>> Regards,
>> RD
>>=20
>>=20
>> Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit :
>>=20
>>> Hi Remi and Wojciech,
>>>=20
>>> Thanks for your clarification. I fully agree with you that embedding th=
e
>>> full IPv4 address in the last 64 bits would be quite helpful for some k=
ind
>>> of source address classification and I also suggest that this can be ta=
ken
>>> in the same way for encapsulation-based approach. It would be easier fo=
r
>>> systems in-the-middle to identify the IPv4 address without packet
>>> decapsulation.
>>>=20
>>> I guess the thing that Ole has mentioned to "look at 24 bits in the mid=
dle
>>> of IPv6 address" is for CE to determine whether a downstream IPv6 packe=
t
>>> should be taken for translation or native forwarding. Here, for a dual-=
stack
>>> host, there would be no difference in the first /64 bits for a native I=
Pv6
>>> packet and a translated packet. What's why the CE should further lookin=
g
>>> into the last 64 bits to determine the translation process or native
>>> forwarding. Maybe Ole can clarify for this part again.
>>>=20
>>> However, the situation would still be different in "Hub & Spoke" and "M=
esh"
>>> mode. For Hub & Spoke case, since BR will have a default prefix/address=
, it
>>> would be easily to identify the translated traffic from native IPv6 tra=
ffic
>>> by just doing source address routing lookup for a downstream packet. So=
, the
>>> corresponding mechanics would be different.
>>>=20
>>> Thanks
>>>=20
>>> Best wishes
>>>=20
>>> Qiong
>>>=20
>>> 2011/10/3 Wojciech Dec <wdec at cisco.com>
>>>=20
>>>=20
>>>=20
>>>=20
>>>     On 02/10/2011 02:58, "Qiong" <bingxuere at gmail.com> wrote:
>>>=20
>>>         Hi Ole and Remi,
>>>=20
>>>> This is my answer to your first (double) question.
>>>> If it is not enough, as suggested below, please explain what you don't
>>>> understand.
>>>=20
>>>             I specifically do not want a solution that changes forwardi=
ng
>>> behaviour for _all_ IPv6 packets.
>>>             e.g. looking at 24 bits in the middle of an IPv6 address is=
 such
>>> a change.
>>>=20
>>>             Woj> What are you referring to? Routing =B3just works=B2 as nor=
mal
>>> and is non disaggregated because of the CE-index in the prefix.
>>> Classification can/is done on a subset of the v6 address, and that is
>>> perfectly legit.
>>>=20
>>>=20
>>>             I don't understand what requirements you are basing this
>>> 'solution' on.
>>>             if the 4rd / dIVI CE takes (a well known or provisioned) /6=
4
>>> prefix out of the delegated prefix. then why do you need any of that?
>>>=20
>>>=20
>>>         Qiong : I agree that routing lookup for a provisioned /64 prefi=
x
>>> would be better that extracting certain bits for each IPv6 address in C=
E.
>>> This would bring less change to existing routing model.
>>>=20
>>>         Woj> There is no change to the existing destination based routi=
ng
>>> model. Each CE is uniquely addressed by the CE bits in the top /64 =AD ie=
 the
>>> CE index is as proposed by all the 4rd and divi-pd drafts. The full v4
>>> source address of each CE is however also embedded in the interface-id,=
 as
>>> per RFC6052. There appears to be no cost for this operation, and has th=
e
>>> upside of the full v4 info visible in the header and allowing source ba=
sed
>>> classification (should one want to do that).
>>>=20
>>>         Regards,
>>>         Woj.
>>>=20
>>>         Best wishes
>>>=20
>>>         Qiong
>>>=20
>>>             _______________________________________________
>>>             Softwires mailing list
>>>             Softwires at ietf.org
>>>             https://www.ietf.org/mailman/listinfo/softwires
>>>=20
>>>=20
>>>=20
>>=20


From dxhbupt@gmail.com  Tue Oct  4 02:30:12 2011
Return-Path: <dxhbupt@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 B61EA21F8CEF for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 02:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.342
X-Spam-Level: 
X-Spam-Status: No, score=-3.342 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xSrrNaOLctBm for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 02:30:11 -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 3599721F8CCC for <softwires@ietf.org>; Tue,  4 Oct 2011 02:30:11 -0700 (PDT)
Received: by wyh21 with SMTP id 21so359047wyh.31 for <softwires@ietf.org>; Tue, 04 Oct 2011 02:33:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=AsBLZ/UdBy+3xXBh0zfgl7VE8y0xOKXucal0fnJ+bgE=; b=gVrbJB3P5zPUwSqUcrGzSWxCjhormuI6ljuJzrSanETUuDq0KWit2dcy4w1WkQVH2x k6MW1WcSQzuo7iQWrPky2vly5r8jsQIh8PO1uUT4QOHESVwfk+Ftood7LJDXaw/mDkHf 7kxbANXQ+jqvqaXrvwa+ihHiDZj6FOt5daBs0=
MIME-Version: 1.0
Received: by 10.227.142.140 with SMTP id q12mr1253380wbu.18.1317720795027; Tue, 04 Oct 2011 02:33:15 -0700 (PDT)
Received: by 10.180.104.202 with HTTP; Tue, 4 Oct 2011 02:33:14 -0700 (PDT)
In-Reply-To: <9D3CDD5C-89EE-4FD0-9689-8DA862E7172F@laposte.net>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com> <9D3CDD5C-89EE-4FD0-9689-8DA862E7172F@laposte.net>
Date: Tue, 4 Oct 2011 17:33:14 +0800
Message-ID: <CANb4Oc=jomZDiPn5ew3yBDo-uKAznE=968mbE2+hgcgsP3s_Zg@mail.gmail.com>
From: xiaohong deng <dxhbupt@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: softwires@ietf.org, wdec@cisco.com
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 04 Oct 2011 09:30:12 -0000

Remi,

Appreciations to you too for your taking initiative.

More inline.

On Tue, Oct 4, 2011 at 10:34 AM, R=E9mi Despr=E9s <despres.remi@laposte.net=
> wrote:
> Xiaohong,
>
> Thanks for you contribution for this debate.
> More below.
>
> Le 4 oct. 2011 =E0 15:26, xiaohong deng a =E9crit :
>
>> Hi Remi, Ole, Woj, and all,
>>
>> I understand the argument of IID bits is resulted from a last minute
>> agreement between 4rd and divi-pd people that having full IPv4 address
>> embedded in the address format helps source based classification,
>
> The agreement is just between those who participated.
> In no way does it commit the group to anything.
>
> Yet I believed it was useful to inform the group that something was found=
 possible, in common by some proponents of encapsulation and double-transla=
tion solutions.

Absolutely.

>
>> but
>> before we argue that, shall we first make this agreement also be
>> accepted by community wide?
>
> No WG agreement can obviously be reached before an open exchange of views=
.
> Exchanging arguments is a necessary part of this process.

Exactly, and that's the reason why I threw this discussion.

>
>> As far as current time-being concerned, I
>> don't see a consensus has been reached on this agreement from
>> community wide.
>
> Very clear.
>
>> It IMHO would be helpful if anybody would clarify some details to 1)
>> first prove source based classification is either a valid or a
>> non-valid requirement for address mapping; For this regard, I would
>> begin with that why do we think the source based IPv4 classification
>> ability instead of the more general five-tuple based IPv4
>> classification ability should be reserved, when deliver IPv4 over
>> IPv6?
>
> After having checked details of our common understanding with Xing, Congx=
iao and Wojciech, I will very soon communicate what we found promising.
> Sorry for the time it took us.

Well. Stay tunned, and expect to hearing more..

>
>> and 2) then show us how much other efforts are required to achieve so
>> besides address format definition itself, in other words, if it's a
>> valid requirement, let's first have feasibility of this requirement
>> analyzed from both deployment and operational perspectives:
>>
>> 1. For double translation, how does a traditional router perform the
>> source based IPv4 packet classification on IPv6 (translated from IPv4)
>> packets? Or does it suggest that using IPv6 classification filters to
>> filter IPv4 packets?
>
> The latter was my understanding.
> With it, filters on IPv4-address, and IPv4-shared-addreses, can be exerci=
sed in existing devices if having appropriately configured IPv6-address fil=
ters.

Share the same understanding with you, yet seems we're still in the
guessing each other's idea stage; However once an agreement of this
requirement reached, I suppose it is fair to state it somewhere
explicitly how this (filtering IPv4 by IPv6 filters) works for the
sake of clarification, and of easing future deployment: for example,
maybe generating IPv6 filters from IPv4 address and/or ports would be
defined/implemented with devices somewhere in future. Just imagine who
could bear with calculating each IPv6 filters manually from IPv4..



> If this can be achieved with negligible capex and opex costs, and without=
 obligation to do it, why not?


Well said.

Since it has been widely aware that migration to IPv6 costs, no matter
at opex or capex cost, and operators can choose approaches at
acceptable costs on both, increased opex should not be an argument
against any approach, yet stating the potential somewhere makes
operators' lives easier.


>
>
>> If so, should we also note that this suggests
>> IPv4 operation and managed are tightly coupled with IPv6 operation and
>> management? which in turn implies complexity in operational, or put in
>> other words,
>
>> OPEX increasing, the last thing among others that
>> operators would like to see.
>
> Indeed, keeping in mind also that a single well chosen standard tends to =
reduce overall costs.

Agreed, as long as it's feasible.

>
>> 2. For encapsulation, even if embedding source IPv4 addresses in the
>> lower bits of the address formats, where does the router find the
>> source port without de-capsulation? Are you suggesting also encode 16
>> bits port in the lower part of address? In either case, it leads to
>> the concerns of increased OPEX to operators stated above.
>>
>> Thoughts?
>
> An expectation is that copying an available information into a fixed part=
 of an IID shouldn't be expensive at all, and that having IPv4 addresses an=
d port-set IDs in clear form in IPv6 addresses should facilitate maintenanc=
e, even if no filter is configured.

Fully agreed with this point, but only question that if the source
address filtering is only what we want to perseve? What about
five-tuple (source address, source port, destination address,
destination port, protocol) filtering?

Cheers,
Xiaohong

>
> Cheers,
> RD
>
>
>> Cheers,
>> Xiaohong
>>
>>> Hi Qiong,
>>>
>>> Some fields of a unified address format for double translation and
>>> encapsulation might be unnecessary for hub and spoke, but using the
>>> same format should be advantageous for maintenance and training if for
>>> nothing else (assuming that any added complexity is negligible
>>> enough).
>>>
>>> Believing that a completely unified format is possible, I mentioned it =
to Alain.
>>> Also, I volunteered to be editor-coordinator for this to happen, but
>>> decision of who does what is his.
>>>
>>> Regards,
>>> RD
>>>
>>>
>>> Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit :
>>>
>>>> Hi Remi and Wojciech,
>>>>
>>>> Thanks for your clarification. I fully agree with you that embedding t=
he full IPv4 address in the last 64 bits would be quite helpful for some ki=
nd of source address classification and I also suggest that this can be tak=
en in the same way for encapsulation-based approach. It would be easier for=
 systems in-the-middle to identify the IPv4 address without packet decapsul=
ation.
>>>>
>>>> I guess the thing that Ole has mentioned to "look at 24 bits in the mi=
ddle of IPv6 address" is for CE to determine whether a downstream IPv6 pack=
et should be taken for translation or native forwarding. Here, for a dual-s=
tack host, there would be no difference in the first /64 bits for a native =
IPv6 packet and a translated packet. What's why the CE should further looki=
ng into the last 64 bits to determine the translation process or native for=
warding. Maybe Ole can clarify for this part again.
>>>>
>>>> However, the situation would still be different in "Hub & Spoke" and "=
Mesh" mode. For Hub & Spoke case, since BR will have a default prefix/addre=
ss, it would be easily to identify the translated traffic from native IPv6 =
traffic by just doing source address routing lookup for a downstream packet=
. So, the corresponding mechanics would be different.
>>>>
>>>> Thanks
>>>>
>>>> Best wishes
>>>>
>>>> Qiong
>>>>
>>>> 2011/10/3 Wojciech Dec <wdec at cisco.com>
>>>>
>>>>
>>>>
>>>>
>>>> =A0 =A0On 02/10/2011 02:58, "Qiong" <bingxuere at gmail.com> wrote:
>>>>
>>>> =A0 =A0 =A0 =A0Hi Ole and Remi,
>>>>
>>>>> This is my answer to your first (double) question.
>>>>> If it is not enough, as suggested below, please explain what you don'=
t understand.
>>>>
>>>> =A0 =A0 =A0 =A0 =A0 =A0I specifically do not want a solution that chan=
ges forwarding behaviour for _all_ IPv6 packets.
>>>> =A0 =A0 =A0 =A0 =A0 =A0e.g. looking at 24 bits in the middle of an IPv=
6 address is such a change.
>>>>
>>>> =A0 =A0 =A0 =A0 =A0 =A0Woj> What are you referring to? Routing =93just=
 works=94 as normal and is non disaggregated because of the CE-index in the=
 prefix. Classification can/is done on a subset of the v6 address, and that=
 is perfectly legit.
>>>>
>>>>
>>>> =A0 =A0 =A0 =A0 =A0 =A0I don't understand what requirements you are ba=
sing this 'solution' on.
>>>> =A0 =A0 =A0 =A0 =A0 =A0if the 4rd / dIVI CE takes (a well known or pro=
visioned) /64 prefix out of the delegated prefix. then why do you need any =
of that?
>>>>
>>>>
>>>> =A0 =A0 =A0 =A0Qiong : I agree that routing lookup for a provisioned /=
64 prefix would be better that extracting certain bits for each IPv6 addres=
s in CE. This would bring less change to existing routing model.
>>>>
>>>> =A0 =A0 =A0 =A0Woj> There is no change to the existing destination bas=
ed routing model. Each CE is uniquely addressed by the CE bits in the top /=
64 =96 ie the CE index is as proposed by all the 4rd and divi-pd drafts. Th=
e full v4 source address of each CE is however also embedded in the interfa=
ce-id, as per RFC6052. There appears to be no cost for this operation, and =
has the upside of the full v4 info visible in the header and allowing sourc=
e based classification (should one want to do that).
>>>>
>>>> =A0 =A0 =A0 =A0Regards,
>>>> =A0 =A0 =A0 =A0Woj.
>>>>
>>>> =A0 =A0 =A0 =A0Best wishes
>>>>
>>>> =A0 =A0 =A0 =A0Qiong
>>>>
>>>> =A0 =A0 =A0 =A0 =A0 =A0_______________________________________________
>>>> =A0 =A0 =A0 =A0 =A0 =A0Softwires mailing list
>>>> =A0 =A0 =A0 =A0 =A0 =A0Softwires at ietf.org
>>>> =A0 =A0 =A0 =A0 =A0 =A0https://www.ietf.org/mailman/listinfo/softwires
>>>>
>>>>
>>>>
>>>
>>
>

From despres.remi@laposte.net  Tue Oct  4 03:19:05 2011
Return-Path: <despres.remi@laposte.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 8737221F8CA9 for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 03:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.864
X-Spam-Level: 
X-Spam-Status: No, score=-1.864 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiXZgsaQyKLi for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 03:19:05 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.118]) by ietfa.amsl.com (Postfix) with ESMTP id B11A021F8CA8 for <softwires@ietf.org>; Tue,  4 Oct 2011 03:19:04 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2502.sfr.fr (SMTP Server) with ESMTP id 75E5970000DD for <softwires@ietf.org>; Tue,  4 Oct 2011 12:22:08 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2502.sfr.fr (SMTP Server) with ESMTP id 4D6DF70000C4 for <softwires@ietf.org>; Tue,  4 Oct 2011 12:22:06 +0200 (CEST)
X-SFR-UUID: 20111004102208317.4D6DF70000C4@msfrf2502.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 4 Oct 2011 12:22:05 +0800
Message-Id: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net>
To: Softwires-wg <softwires@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 04 Oct 2011 10:19:05 -0000

Hi all,

1.
Here is a unified Address Mapping, for both encapsulation and =
double-translation approaches, that is PROPOSED for IPv4 residual =
deployment across IPv6-only routing domains.

It results from an informal meeting among participants having different =
preferences between double-translation and encapsulation solutions (Xing =
Li, Congxiao Bao, Wojciech Dec, myself, at the end of the Beijing =
meeting).

The idea is to have a common format that is good for both types of =
solutions.
In particular:
- It enriches Double translation by introducing a deterministic way to =
distinguish a translated IPv4 packet from a native IPv6 packet.
- It enriches Encapsulation by expressing, in clear format within an =
IPv6 address, an IPv4 address, an IPv4 prefix, or an IPv4 address + =
port-set ID.=20


2.
(a)
The IPv6 Source address of an IPv4 packet from a CE is:

a1- If the CE has an exclusive or shared IPv4 address:

<--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
+-------------+--------+---+---+----------------+------+-----+---+
| IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
+-------------+--------+---+---+----------------+------+-----+---+

a2- If the CE has an IPv4 prefix:

<--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
+-------------+--------+---+---+-------------+---------------+---+
| IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
+-------------+--------+---+---+-------------+---------------+---+

(b)
V is the mark that characterizes IPv6 packets that are in reality IPv4 =
packets.
Its value differs from any permitted value of this octet in IPv6 IIDs  =
(ref RFC 4291).

It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.

An unambiguous mark is fortunately possible because currently permitted =
IIDs have in their first octet either bit6 =3D 0 (the "u" bit"), or bit6 =
=3D 1 and bit7=3D 0 (the "g" bit).
With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction is therefore deterministic.

The proposed V is =3D 00000011.=20
(With other values of this octet, other IID formats can be defined in =
case some would be useful in the future.)

Note that, if and when a consensus is reached in Softwire, an extension =
of RFC 4291 will have to be submitted to 6MAN.=20

(c)                                  =20
A Destination address from a CE to the outside IPv4 Internet is:
<--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
+--------------------------+----+---------------+------------+---+
|     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
+--------------------------+----+---------------+------------+---+

Note that if double-translation CEs are notified to use U instead of V, =
the last octet becomes 0 per RFC  6052.


3.
All comments are most welcome.
 =20
Kind regards to all,
RD



From despres.remi@laposte.net  Tue Oct  4 06:28:10 2011
Return-Path: <despres.remi@laposte.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 9588421F8C3A for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 06:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.889
X-Spam-Level: 
X-Spam-Status: No, score=-0.889 tagged_above=-999 required=5 tests=[AWL=-0.934, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, MANGLED_FROM=2.3, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8soNx-6OGDai for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 06:28:10 -0700 (PDT)
Received: from smtpout.laposte.net (smtpout7.laposte.net [193.253.67.232]) by ietfa.amsl.com (Postfix) with ESMTP id C26B021F8C37 for <softwires@ietf.org>; Tue,  4 Oct 2011 06:28:08 -0700 (PDT)
Received: from [192.168.0.21] ([88.166.221.144]) by mwinf8514-out with ME id gdX71h00537Y3f403dX7DT; Tue, 04 Oct 2011 15:31:12 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com>
Date: Tue, 4 Oct 2011 15:31:07 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <67E4A8C5-B119-45DB-8367-BDF55A380DC4@laposte.net>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com>
To: Xing Li <xing@cernet.edu.cn>, Congxiao Bao <congxiao@cernet.edu.cn>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Xiaohong Deng <dxhbupt@gmail.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 04 Oct 2011 13:28:10 -0000

Hi Xing, Congxiao,

Le 4 oct. 2011 =E0 15:26, xiaohong deng a =E9crit :
...
> It IMHO would be helpful if anybody would clarify some details to 1)
> first prove source based classification is either a valid or a
> non-valid requirement for address mapping; For this regard, I would
> begin with that why do we think the source based IPv4 classification
> ability instead of the more general five-tuple based IPv4
> classification ability should be reserved, when deliver IPv4 over
> IPv6?

What about starting from your conclusion slide in Beijing?

It says:

"dIVI/dIVI-PD can use existing tools for O&M
=96 Null route
=96 ACL
=96 eACL
=96 PBR
=96 QoS
=96 Caching"

Open questions include:
- Which addresses are used for these O&M functions? (source? =
destination?, CE to CE?, CE to BR?, BR to CE?)
- Are ports within IPv6 payloads used, or just addresses?

Thank you if you can share your views on this.

Regards,
RD=20




From cx.cernet@gmail.com  Tue Oct  4 08:34:41 2011
Return-Path: <cx.cernet@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 024C921F8B4B for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 08:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level: 
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[AWL=-1.198, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_FROM=2.3, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZK6PQ1ieFbWJ for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 08:34:40 -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 65CD121F8AD1 for <softwires@ietf.org>; Tue,  4 Oct 2011 08:34:40 -0700 (PDT)
Received: by vcbfo11 with SMTP id fo11so614021vcb.31 for <softwires@ietf.org>; Tue, 04 Oct 2011 08:37:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jF+Geq8ocsXJegO6yGfHoiNFybxVkiSkLqVD3UvwYaw=; b=e7Ogo4K12Z4jD4uLRF9cr7RaCkwPQPpW17lggso3myo8KTMAunxwohPLlHUOY91qXa jfOOR89N7BYcINpTMsyy9ni/c1yV2IS6TT0O9Padg6lUfHoF+gkAwXPbkIl+/fHiblHO SZ+fIQBNRGPbAy8sKj71YmOTvHYRMrmnQaGRw=
MIME-Version: 1.0
Received: by 10.68.15.194 with SMTP id z2mr10370130pbc.47.1317742665136; Tue, 04 Oct 2011 08:37:45 -0700 (PDT)
Received: by 10.142.162.1 with HTTP; Tue, 4 Oct 2011 08:37:44 -0700 (PDT)
In-Reply-To: <67E4A8C5-B119-45DB-8367-BDF55A380DC4@laposte.net>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com> <67E4A8C5-B119-45DB-8367-BDF55A380DC4@laposte.net>
Date: Tue, 4 Oct 2011 23:37:44 +0800
Message-ID: <CABv173VUCzOoKzQtNhKMSs1a2xyFAfHpGvhUX-iS2RcEt3Y43w@mail.gmail.com>
From: Congxiao Bao <cx.cernet@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=bcaec51f995f75fbd304ae7adf62
Cc: Softwires-wg <softwires@ietf.org>, Congxiao Bao <congxiao@cernet.edu.cn>, Xiaohong Deng <dxhbupt@gmail.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 04 Oct 2011 15:34:41 -0000

--bcaec51f995f75fbd304ae7adf62
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Remi,

Ok, we will draft a document on using existing tools for O&M in dIVI/dIVI-P=
D
very soon.

Best,

Congxiao

2011/10/4 R=E9mi Despr=E9s <despres.remi@laposte.net>

> Hi Xing, Congxiao,
>
> Le 4 oct. 2011 =E0 15:26, xiaohong deng a =E9crit :
> ...
> > It IMHO would be helpful if anybody would clarify some details to 1)
> > first prove source based classification is either a valid or a
> > non-valid requirement for address mapping; For this regard, I would
> > begin with that why do we think the source based IPv4 classification
> > ability instead of the more general five-tuple based IPv4
> > classification ability should be reserved, when deliver IPv4 over
> > IPv6?
>
> What about starting from your conclusion slide in Beijing?
>
> It says:
>
> "dIVI/dIVI-PD can use existing tools for O&M
> =96 Null route
> =96 ACL
> =96 eACL
> =96 PBR
> =96 QoS
> =96 Caching"
>
> Open questions include:
> - Which addresses are used for these O&M functions? (source? destination?=
,
> CE to CE?, CE to BR?, BR to CE?)
> - Are ports within IPv6 payloads used, or just addresses?
>
> Thank you if you can share your views on this.
>
> Regards,
> RD
>
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

--bcaec51f995f75fbd304ae7adf62
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Remi, <br><br>Ok, we will draft a document on using existing tools for O=
&amp;M in dIVI/dIVI-PD very soon. <br><br>Best, <br><br>Congxiao <br><br>
<div class=3D"gmail_quote">2011/10/4 R=E9mi Despr=E9s <span dir=3D"ltr">&lt=
;<a href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&g=
t;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">Hi Xing, Congxiao,<br>
<div class=3D"im"><br>Le 4 oct. 2011 =E0 15:26, xiaohong deng a =E9crit :<b=
r></div>...<br>
<div class=3D"im">&gt; It IMHO would be helpful if anybody would clarify so=
me details to 1)<br>&gt; first prove source based classification is either =
a valid or a<br>&gt; non-valid requirement for address mapping; For this re=
gard, I would<br>
&gt; begin with that why do we think the source based IPv4 classification<b=
r>&gt; ability instead of the more general five-tuple based IPv4<br>&gt; cl=
assification ability should be reserved, when deliver IPv4 over<br>&gt; IPv=
6?<br>
<br></div>What about starting from your conclusion slide in Beijing?<br><br=
>It says:<br><br>&quot;dIVI/dIVI-PD can use existing tools for O&amp;M<br>=
=96 Null route<br>=96 ACL<br>=96 eACL<br>=96 PBR<br>=96 QoS<br>=96 Caching&=
quot;<br>
<br>Open questions include:<br>- Which addresses are used for these O&amp;M=
 functions? (source? destination?, CE to CE?, CE to BR?, BR to CE?)<br>- Ar=
e ports within IPv6 payloads used, or just addresses?<br><br>Thank you if y=
ou can share your views on this.<br>
<br>Regards,<br><font color=3D"#888888">RD<br></font>
<div>
<div></div>
<div class=3D"h5"><br><br><br>_____________________________________________=
__<br>Softwires mailing list<br><a href=3D"mailto:Softwires@ietf.org">Softw=
ires@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/softw=
ires" target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a>=
<br>
</div></div></blockquote></div><br>

--bcaec51f995f75fbd304ae7adf62--

From phdgang@gmail.com  Tue Oct  4 10:06:58 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 A2FE321F8AED for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 10:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.424
X-Spam-Level: 
X-Spam-Status: No, score=-3.424 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DI89cFWTo-5s for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 10:06:58 -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 BAADC21F8ADC for <softwires@ietf.org>; Tue,  4 Oct 2011 10:06:57 -0700 (PDT)
Received: by wyh21 with SMTP id 21so895920wyh.31 for <softwires@ietf.org>; Tue, 04 Oct 2011 10:10:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=In/hrtv8zSYKO7zkavsBQ21xypZ6bw/4Wz198i6tG4o=; b=HaFbXXE7b5OhZiZY+X6mCAhVwN3zUtmxWFjergagJdjjXVynWOqo8MpZy1T2zWka+d 7txPvXW1T2rALI4JSH59J0sgaJ2veaG5NNf71/5rbQzJNyBpd/ZShFQalqVeOT0ueiqA J+D8zUCL9ybYhJEUAG99NTMSnj05xoIa1eKOE=
MIME-Version: 1.0
Received: by 10.227.7.159 with SMTP id d31mr1849483wbd.18.1317748202672; Tue, 04 Oct 2011 10:10:02 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Tue, 4 Oct 2011 10:10:02 -0700 (PDT)
In-Reply-To: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net>
Date: Wed, 5 Oct 2011 01:10:02 +0800
Message-ID: <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 04 Oct 2011 17:06:58 -0000

Hello Remi,

I'm trying to put some comments for such unified address mapping.
Regarding the deterministic benefit for double translation, I guess we
only could use V bits to achieve.
There are no necessary to put IPv4 and Port-set ID information in last
64 bits.
If I understand correctly, the encoded IPv4 and Port-set ID could help
to derive a shared/dedicated IPv4 address or IPv4 subnet from the IPv6
prefix.
It may help encapsulation in same cases(e.g. IPv4 based traffic
classification,IPv4 ACL, etc).
However, the translation case is more preferable doing pure IPv6 based
control for the sake of simpler operation reasons (e.g. IPv6 ACL).
It's desirable identifying a customer depending on first 64 bits.

Many thanks



Gang

2011/10/4, R=E9mi Despr=E9s <despres.remi@laposte.net>:
> Hi all,
>
> 1.
> Here is a unified Address Mapping, for both encapsulation and
> double-translation approaches, that is PROPOSED for IPv4 residual deploym=
ent
> across IPv6-only routing domains.
>
> It results from an informal meeting among participants having different
> preferences between double-translation and encapsulation solutions (Xing =
Li,
> Congxiao Bao, Wojciech Dec, myself, at the end of the Beijing meeting).
>
> The idea is to have a common format that is good for both types of
> solutions.
> In particular:
> - It enriches Double translation by introducing a deterministic way to
> distinguish a translated IPv4 packet from a native IPv6 packet.
> - It enriches Encapsulation by expressing, in clear format within an IPv6
> address, an IPv4 address, an IPv4 prefix, or an IPv4 address + port-set I=
D.
>
>
> 2.
> (a)
> The IPv6 Source address of an IPv4 packet from a CE is:
>
> a1- If the CE has an exclusive or shared IPv4 address:
>
> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
> +-------------+--------+---+---+----------------+------+-----+---+
> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
> +-------------+--------+---+---+----------------+------+-----+---+
>
> a2- If the CE has an IPv4 prefix:
>
> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
> +-------------+--------+---+---+-------------+---------------+---+
> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
> +-------------+--------+---+---+-------------+---------------+---+
>
> (b)
> V is the mark that characterizes IPv6 packets that are in reality IPv4
> packets.
> Its value differs from any permitted value of this octet in IPv6 IIDs  (r=
ef
> RFC 4291).
>
> It is understood that, if double Translation coexists with single
> translation, concerned ISPs may notify their CEs to use the U octet of RF=
C
> 6052 instead of V.
>
> An unambiguous mark is fortunately possible because currently permitted I=
IDs
> have in their first octet either bit6 =3D 0 (the "u" bit"), or bit6 =3D 1=
 and
> bit7=3D 0 (the "g" bit).
> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, disti=
nction
> is therefore deterministic.
>
> The proposed V is =3D 00000011.
> (With other values of this octet, other IID formats can be defined in cas=
e
> some would be useful in the future.)
>
> Note that, if and when a consensus is reached in Softwire, an extension o=
f
> RFC 4291 will have to be submitted to 6MAN.
>
> (c)
> A Destination address from a CE to the outside IPv4 Internet is:
> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> +--------------------------+----+---------------+------------+---+
> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
> +--------------------------+----+---------------+------------+---+
>
> Note that if double-translation CEs are notified to use U instead of V, t=
he
> last octet becomes 0 per RFC  6052.
>
>
> 3.
> All comments are most welcome.
>
> Kind regards to all,
> RD
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

From rajiva@cisco.com  Tue Oct  4 12:25:25 2011
Return-Path: <rajiva@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 C627121F8FA5 for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 12:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rAvMpCBO5ru for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 12:25:24 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id D0D6721F8FA1 for <softwires@ietf.org>; Tue,  4 Oct 2011 12:25:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rajiva@cisco.com; l=7341; q=dns/txt; s=iport; t=1317756510; x=1318966110; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=Em8xzghTPf6Xe0ocB/UZRGTiTVtbq5dFJPqNqYcB33w=; b=BnS9E4CKE30VWyq8CbK2sVIDyr6K2EzWjbcVOuZ6nsJQWuSFnbtg2MVA 0VXBOfRfLbpSy7223zJCeRoBrWeGw+th1dgzQhoMl4sczACtexrBAQIPt NecKI1lNUoniClRExNfMKbw8RNJ96nqjkX2Qeq8MBodDlRSWjQOJWS6PN 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArwAALVdi06tJV2d/2dsb2JhbAA4CphxjxSBBYFTAQEBAQIBAQEBDwEdPhAHBAIBCBEEAQEBCgYXAQYBIAYfCQgBAQQBEggMBwEGh1sGmj4BnXmDd4JLYQSHSDCRHoRwh0A
X-IronPort-AV: E=Sophos;i="4.68,486,1312156800"; d="scan'208";a="26027222"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP; 04 Oct 2011 19:28:29 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id p94JSTB0020090;  Tue, 4 Oct 2011 19:28:29 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 4 Oct 2011 14:28:29 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 4 Oct 2011 14:28:27 -0500
Message-ID: <067E6CE33034954AAC05C9EC85E2577C0613BAC1@XMB-RCD-111.cisco.com>
In-Reply-To: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Softwires] 4rd Address Mapping - version-01
Thread-Index: AcyCZuJVi46Dul3mRLi4UWIXD6BOzgAZIhMA
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com>
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "xiaohong deng" <dxhbupt@gmail.com>, "Wojciech Dec (wdec)" <wdec@cisco.com>, <despres.remi@laposte.net>, <otroan@employees.org>, <bingxuere@gmail.com>, <softwires@ietf.org>
X-OriginalArrivalTime: 04 Oct 2011 19:28:29.0094 (UTC) FILETIME=[CB7E8460:01CC82CB]
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 04 Oct 2011 19:25:25 -0000

> ability instead of the more general five-tuple based IPv4
> classification ability should be reserved, when deliver IPv4 over
> IPv6?

How would one get 5-tuple based classification when delivering IPv4 =
"over" IPv6, if the v4 packet is not translated into v6?

The fact of the matter is that "5-tuple" could be a luxury that may not =
always be available.

Cheers,
Rajiv


> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] =
On Behalf
> Of xiaohong deng
> Sent: Tuesday, October 04, 2011 3:26 AM
> To: Wojciech Dec (wdec); despres.remi@laposte.net; =
otroan@employees.org;
> bingxuere@gmail.com; softwires@ietf.org
> Subject: Re: [Softwires] 4rd Address Mapping - version-01
>=20
> Hi Remi, Ole, Woj, and all,
>=20
> I understand the argument of IID bits is resulted from a last minute
> agreement between 4rd and divi-pd people that having full IPv4 address
> embedded in the address format helps source based classification, but
> before we argue that, shall we first make this agreement also be
> accepted by community wide? As far as current time-being concerned, I
> don't see a consensus has been reached on this agreement from
> community wide.
>=20
> It IMHO would be helpful if anybody would clarify some details to 1)
> first prove source based classification is either a valid or a
> non-valid requirement for address mapping; For this regard, I would
> begin with that why do we think the source based IPv4 classification
> ability instead of the more general five-tuple based IPv4
> classification ability should be reserved, when deliver IPv4 over
> IPv6?
>=20
>=20
> and 2) then show us how much other efforts are required to achieve so
> besides address format definition itself, in other words, if it's a
> valid requirement, let's first have feasibility of this requirement
> analyzed from both deployment and operational perspectives:
>=20
> 1. For double translation, how does a traditional router perform the
> source based IPv4 packet classification on IPv6 (translated from IPv4)
> packets? Or does it suggest that using IPv6 classification filters to
> filter IPv4 packets? If so, should we also note that this suggests
> IPv4 operation and managed are tightly coupled with IPv6 operation and
> management? which in turn implies complexity in operational, or put in
> other words, OPEX increasing, the last thing among others that
> operators would like to see.
>=20
> 2. For encapsulation, even if embedding source IPv4 addresses in the
> lower bits of the address formats, where does the router find the
> source port without de-capsulation? Are you suggesting also encode 16
> bits port in the lower part of address? In either case, it leads to
> the concerns of increased OPEX to operators stated above.
>=20
> Thoughts?
>=20
> Cheers,
> Xiaohong
>=20
> > Hi Qiong,
> >
> > Some fields of a unified address format for double translation and
> > encapsulation might be unnecessary for hub and spoke, but using the
> > same format should be advantageous for maintenance and training if =
for
> > nothing else (assuming that any added complexity is negligible
> > enough).
> >
> > Believing that a completely unified format is possible, I mentioned =
it to
> Alain.
> > Also, I volunteered to be editor-coordinator for this to happen, but
> > decision of who does what is his.
> >
> > Regards,
> > RD
> >
> >
> > Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit :
> >
> >> Hi Remi and Wojciech,
> >>
> >> Thanks for your clarification. I fully agree with you that =
embedding the
> full IPv4 address in the last 64 bits would be quite helpful for some =
kind of
> source address classification and I also suggest that this can be =
taken in the
> same way for encapsulation-based approach. It would be easier for =
systems in-
> the-middle to identify the IPv4 address without packet decapsulation.
> >>
> >> I guess the thing that Ole has mentioned to "look at 24 bits in the =
middle
> of IPv6 address" is for CE to determine whether a downstream IPv6 =
packet
> should be taken for translation or native forwarding. Here, for a =
dual-stack
> host, there would be no difference in the first /64 bits for a native =
IPv6
> packet and a translated packet. What's why the CE should further =
looking into
> the last 64 bits to determine the translation process or native =
forwarding.
> Maybe Ole can clarify for this part again.
> >>
> >> However, the situation would still be different in "Hub & Spoke" =
and "Mesh"
> mode. For Hub & Spoke case, since BR will have a default =
prefix/address, it
> would be easily to identify the translated traffic from native IPv6 =
traffic by
> just doing source address routing lookup for a downstream packet. So, =
the
> corresponding mechanics would be different.
> >>
> >> Thanks
> >>
> >> Best wishes
> >>
> >> Qiong
> >>
> >> 2011/10/3 Wojciech Dec <wdec at cisco.com>
> >>
> >>
> >>
> >>
> >>     On 02/10/2011 02:58, "Qiong" <bingxuere at gmail.com> wrote:
> >>
> >>         Hi Ole and Remi,
> >>
> >>             > This is my answer to your first (double) question.
> >>             > If it is not enough, as suggested below, please =
explain what
> you don't understand.
> >>
> >>             I specifically do not want a solution that changes =
forwarding
> behaviour for _all_ IPv6 packets.
> >>             e.g. looking at 24 bits in the middle of an IPv6 =
address is
> such a change.
> >>
> >>             Woj> What are you referring to? Routing "just works" as =
normal
> and is non disaggregated because of the CE-index in the prefix. =
Classification
> can/is done on a subset of the v6 address, and that is perfectly =
legit.
> >>
> >>
> >>             I don't understand what requirements you are basing =
this
> 'solution' on.
> >>             if the 4rd / dIVI CE takes (a well known or =
provisioned) /64
> prefix out of the delegated prefix. then why do you need any of that?
> >>
> >>
> >>         Qiong : I agree that routing lookup for a provisioned /64 =
prefix
> would be better that extracting certain bits for each IPv6 address in =
CE. This
> would bring less change to existing routing model.
> >>
> >>         Woj> There is no change to the existing destination based =
routing
> model. Each CE is uniquely addressed by the CE bits in the top /64 - =
ie the CE
> index is as proposed by all the 4rd and divi-pd drafts. The full v4 =
source
> address of each CE is however also embedded in the interface-id, as =
per
> RFC6052. There appears to be no cost for this operation, and has the =
upside of
> the full v4 info visible in the header and allowing source based
> classification (should one want to do that).
> >>
> >>         Regards,
> >>         Woj.
> >>
> >>         Best wishes
> >>
> >>         Qiong
> >>
> >>             _______________________________________________
> >>             Softwires mailing list
> >>             Softwires at ietf.org
> >>             https://www.ietf.org/mailman/listinfo/softwires
> >>
> >>
> >>
> >
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From xing@cernet.edu.cn  Wed Oct  5 00:12:32 2011
Return-Path: <xing@cernet.edu.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 327B521F8726 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 00:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.399
X-Spam-Level: 
X-Spam-Status: No, score=-99.399 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, FH_HAS_XAIMC=2.696, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kndt8bnZnDRs for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 00:12:31 -0700 (PDT)
Received: from cernet.edu.cn (cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with SMTP id C16EF21F85D1 for <softwires@ietf.org>; Wed,  5 Oct 2011 00:12:29 -0700 (PDT)
Received: from [127.0.0.1]([119.39.249.39]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm74e8c1391; Wed, 05 Oct 2011 15:15:35 +0800
Message-ID: <4E8C040D.8060904@cernet.edu.cn>
Date: Wed, 05 Oct 2011 15:15:25 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15
MIME-Version: 1.0
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com> <067E6CE33034954AAC05C9EC85E2577C0613BAC1@XMB-RCD-111.cisco.com>
In-Reply-To: <067E6CE33034954AAC05C9EC85E2577C0613BAC1@XMB-RCD-111.cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: vb7hVL1B
Cc: xiaohong deng <dxhbupt@gmail.com>, softwires@ietf.org, "Wojciech Dec \(wdec\)" <wdec@cisco.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 05 Oct 2011 07:12:32 -0000

äºŽ 2011/10/5 3:28, Rajiv Asati (rajiva) å†™é�“:
>> ability instead of the more general five-tuple based IPv4
>> classification ability should be reserved, when deliver IPv4 over
>> IPv6?
> How would one get 5-tuple based classification when delivering IPv4 "over" IPv6, if the v4 packet is not translated into v6?

Yes, this is why we need the whole IPv4 address plus port ID in the IPv6 
address. xing

> The fact of the matter is that "5-tuple" could be a luxury that may not always be available.


> Cheers,
> Rajiv
>
>
>> -----Original Message-----
>> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On Behalf
>> Of xiaohong deng
>> Sent: Tuesday, October 04, 2011 3:26 AM
>> To: Wojciech Dec (wdec); despres.remi@laposte.net; otroan@employees.org;
>> bingxuere@gmail.com; softwires@ietf.org
>> Subject: Re: [Softwires] 4rd Address Mapping - version-01
>>
>> Hi Remi, Ole, Woj, and all,
>>
>> I understand the argument of IID bits is resulted from a last minute
>> agreement between 4rd and divi-pd people that having full IPv4 address
>> embedded in the address format helps source based classification, but
>> before we argue that, shall we first make this agreement also be
>> accepted by community wide? As far as current time-being concerned, I
>> don't see a consensus has been reached on this agreement from
>> community wide.
>>
>> It IMHO would be helpful if anybody would clarify some details to 1)
>> first prove source based classification is either a valid or a
>> non-valid requirement for address mapping; For this regard, I would
>> begin with that why do we think the source based IPv4 classification
>> ability instead of the more general five-tuple based IPv4
>> classification ability should be reserved, when deliver IPv4 over
>> IPv6?
>>
>>
>> and 2) then show us how much other efforts are required to achieve so
>> besides address format definition itself, in other words, if it's a
>> valid requirement, let's first have feasibility of this requirement
>> analyzed from both deployment and operational perspectives:
>>
>> 1. For double translation, how does a traditional router perform the
>> source based IPv4 packet classification on IPv6 (translated from IPv4)
>> packets? Or does it suggest that using IPv6 classification filters to
>> filter IPv4 packets? If so, should we also note that this suggests
>> IPv4 operation and managed are tightly coupled with IPv6 operation and
>> management? which in turn implies complexity in operational, or put in
>> other words, OPEX increasing, the last thing among others that
>> operators would like to see.
>>
>> 2. For encapsulation, even if embedding source IPv4 addresses in the
>> lower bits of the address formats, where does the router find the
>> source port without de-capsulation? Are you suggesting also encode 16
>> bits port in the lower part of address? In either case, it leads to
>> the concerns of increased OPEX to operators stated above.
>>
>> Thoughts?
>>
>> Cheers,
>> Xiaohong
>>
>>> Hi Qiong,
>>>
>>> Some fields of a unified address format for double translation and
>>> encapsulation might be unnecessary for hub and spoke, but using the
>>> same format should be advantageous for maintenance and training if for
>>> nothing else (assuming that any added complexity is negligible
>>> enough).
>>>
>>> Believing that a completely unified format is possible, I mentioned it to
>> Alain.
>>> Also, I volunteered to be editor-coordinator for this to happen, but
>>> decision of who does what is his.
>>>
>>> Regards,
>>> RD
>>>
>>>
>>> Le 4 oct. 2011 Ã  00:13, Qiong a Ã©crit :
>>>
>>>> Hi Remi and Wojciech,
>>>>
>>>> Thanks for your clarification. I fully agree with you that embedding the
>> full IPv4 address in the last 64 bits would be quite helpful for some kind of
>> source address classification and I also suggest that this can be taken in the
>> same way for encapsulation-based approach. It would be easier for systems in-
>> the-middle to identify the IPv4 address without packet decapsulation.
>>>> I guess the thing that Ole has mentioned to "look at 24 bits in the middle
>> of IPv6 address" is for CE to determine whether a downstream IPv6 packet
>> should be taken for translation or native forwarding. Here, for a dual-stack
>> host, there would be no difference in the first /64 bits for a native IPv6
>> packet and a translated packet. What's why the CE should further looking into
>> the last 64 bits to determine the translation process or native forwarding.
>> Maybe Ole can clarify for this part again.
>>>> However, the situation would still be different in "Hub&  Spoke" and "Mesh"
>> mode. For Hub&  Spoke case, since BR will have a default prefix/address, it
>> would be easily to identify the translated traffic from native IPv6 traffic by
>> just doing source address routing lookup for a downstream packet. So, the
>> corresponding mechanics would be different.
>>>> Thanks
>>>>
>>>> Best wishes
>>>>
>>>> Qiong
>>>>
>>>> 2011/10/3 Wojciech Dec<wdec at cisco.com>
>>>>
>>>>
>>>>
>>>>
>>>>      On 02/10/2011 02:58, "Qiong"<bingxuere at gmail.com>  wrote:
>>>>
>>>>          Hi Ole and Remi,
>>>>
>>>>              >  This is my answer to your first (double) question.
>>>>              >  If it is not enough, as suggested below, please explain what
>> you don't understand.
>>>>              I specifically do not want a solution that changes forwarding
>> behaviour for _all_ IPv6 packets.
>>>>              e.g. looking at 24 bits in the middle of an IPv6 address is
>> such a change.
>>>>              Woj>  What are you referring to? Routing "just works" as normal
>> and is non disaggregated because of the CE-index in the prefix. Classification
>> can/is done on a subset of the v6 address, and that is perfectly legit.
>>>>
>>>>              I don't understand what requirements you are basing this
>> 'solution' on.
>>>>              if the 4rd / dIVI CE takes (a well known or provisioned) /64
>> prefix out of the delegated prefix. then why do you need any of that?
>>>>
>>>>          Qiong : I agree that routing lookup for a provisioned /64 prefix
>> would be better that extracting certain bits for each IPv6 address in CE. This
>> would bring less change to existing routing model.
>>>>          Woj>  There is no change to the existing destination based routing
>> model. Each CE is uniquely addressed by the CE bits in the top /64 - ie the CE
>> index is as proposed by all the 4rd and divi-pd drafts. The full v4 source
>> address of each CE is however also embedded in the interface-id, as per
>> RFC6052. There appears to be no cost for this operation, and has the upside of
>> the full v4 info visible in the header and allowing source based
>> classification (should one want to do that).
>>>>          Regards,
>>>>          Woj.
>>>>
>>>>          Best wishes
>>>>
>>>>          Qiong
>>>>
>>>>              _______________________________________________
>>>>              Softwires mailing list
>>>>              Softwires at ietf.org
>>>>              https://www.ietf.org/mailman/listinfo/softwires
>>>>
>>>>
>>>>
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>


From despres.remi@laposte.net  Wed Oct  5 00:31:13 2011
Return-Path: <despres.remi@laposte.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 8738021F8B73 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 00:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level: 
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HDQLNE6VPz12 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 00:31:13 -0700 (PDT)
Received: from smtpout.laposte.net (smtpout8.laposte.net [193.253.67.233]) by ietfa.amsl.com (Postfix) with ESMTP id 6882321F8B6B for <softwires@ietf.org>; Wed,  5 Oct 2011 00:31:12 -0700 (PDT)
Received: from [192.168.0.21] ([88.166.221.144]) by mwinf8515-out with ME id gvaH1h00437Y3f403vaHD2; Wed, 05 Oct 2011 09:34:17 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com>
Date: Wed, 5 Oct 2011 09:34:18 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 05 Oct 2011 07:31:13 -0000

Hi Gang,

Thanks for your comments.
More below.


Le 5 oct. 2011 =E0 01:10, GangChen a =E9crit :

> Hello Remi,
>=20
> I'm trying to put some comments for such unified address mapping.
> Regarding the deterministic benefit for double translation, I guess we
> only could use V bits to achieve.

Right.
V is indeed a reliable tool for this.


> There are no necessary to put IPv4 and Port-set ID information in last
> 64 bits.

The CE Pv6 prefix included in the /64 Subnet prefix isn't self =
delimited, so that the length of the CE index can't be determined in =
this part of the address.=20
Having the length of the A or A+P prefix in the IID completes what is =
needed to derive the CE port-set.


> If I understand correctly, the encoded IPv4 and Port-set ID could help
> to derive a shared/dedicated IPv4 address or IPv4 subnet from the IPv6
> prefix.

Yes.
Besides, having the IPv4 address (or prefix) in clear form, and with an =
explicit sharing ratio, facilitates maintenance at essentially no cost.=20=


> It may help encapsulation in same cases(e.g. IPv4 based traffic
> classification,IPv4 ACL, etc).
> However, the translation case is more preferable doing pure IPv6 based
> control for the sake of simpler operation reasons (e.g. IPv6 ACL).
> It's desirable identifying a customer depending on first 64 bits.

A point is that, although some realistic deployments may ignore what is =
made available in IIDs (at least at the beginning), some others would =
take advantage of it.
A standard with a straightforward and unified format is AFAIK better =
than several variants, at least for documentation, training, maintenance =
etc.

Note also that even with a single standard, it remains possible to add =
optional variants if found useful for some deployments.

Hope it clarifies.


Regards,
RD


>=20
> Many thanks
>=20
>=20
>=20
> Gang
>=20
> 2011/10/4, R=E9mi Despr=E9s <despres.remi@laposte.net>:
>> Hi all,
>>=20
>> 1.
>> Here is a unified Address Mapping, for both encapsulation and
>> double-translation approaches, that is PROPOSED for IPv4 residual =
deployment
>> across IPv6-only routing domains.
>>=20
>> It results from an informal meeting among participants having =
different
>> preferences between double-translation and encapsulation solutions =
(Xing Li,
>> Congxiao Bao, Wojciech Dec, myself, at the end of the Beijing =
meeting).
>>=20
>> The idea is to have a common format that is good for both types of
>> solutions.
>> In particular:
>> - It enriches Double translation by introducing a deterministic way =
to
>> distinguish a translated IPv4 packet from a native IPv6 packet.
>> - It enriches Encapsulation by expressing, in clear format within an =
IPv6
>> address, an IPv4 address, an IPv4 prefix, or an IPv4 address + =
port-set ID.
>>=20
>>=20
>> 2.
>> (a)
>> The IPv6 Source address of an IPv4 packet from a CE is:
>>=20
>> a1- If the CE has an exclusive or shared IPv4 address:
>>=20
>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
>> +-------------+--------+---+---+----------------+------+-----+---+
>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>> +-------------+--------+---+---+----------------+------+-----+---+
>>=20
>> a2- If the CE has an IPv4 prefix:
>>=20
>> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
>> +-------------+--------+---+---+-------------+---------------+---+
>> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
>> +-------------+--------+---+---+-------------+---------------+---+
>>=20
>> (b)
>> V is the mark that characterizes IPv6 packets that are in reality =
IPv4
>> packets.
>> Its value differs from any permitted value of this octet in IPv6 IIDs =
 (ref
>> RFC 4291).
>>=20
>> It is understood that, if double Translation coexists with single
>> translation, concerned ISPs may notify their CEs to use the U octet =
of RFC
>> 6052 instead of V.
>>=20
>> An unambiguous mark is fortunately possible because currently =
permitted IIDs
>> have in their first octet either bit6 =3D 0 (the "u" bit"), or bit6 =3D=
 1 and
>> bit7=3D 0 (the "g" bit).
>> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction
>> is therefore deterministic.
>>=20
>> The proposed V is =3D 00000011.
>> (With other values of this octet, other IID formats can be defined in =
case
>> some would be useful in the future.)
>>=20
>> Note that, if and when a consensus is reached in Softwire, an =
extension of
>> RFC 4291 will have to be submitted to 6MAN.
>>=20
>> (c)
>> A Destination address from a CE to the outside IPv4 Internet is:
>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>> +--------------------------+----+---------------+------------+---+
>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>> +--------------------------+----+---------------+------------+---+
>>=20
>> Note that if double-translation CEs are notified to use U instead of =
V, the
>> last octet becomes 0 per RFC  6052.
>>=20
>>=20
>> 3.
>> All comments are most welcome.
>>=20
>> Kind regards to all,
>> RD
>>=20
>>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>=20
>=20


From despres.remi@laposte.net  Wed Oct  5 00:53:23 2011
Return-Path: <despres.remi@laposte.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 C71C321F8AB8 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 00:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level: 
X-Spam-Status: No, score=-1.857 tagged_above=-999 required=5 tests=[AWL=0.048,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHB3LClaYSFN for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 00:53:23 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.19]) by ietfa.amsl.com (Postfix) with ESMTP id 97A4221F8A71 for <softwires@ietf.org>; Wed,  5 Oct 2011 00:53:22 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2318.sfr.fr (SMTP Server) with ESMTP id DB41B7000415; Wed,  5 Oct 2011 09:56:28 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2318.sfr.fr (SMTP Server) with ESMTP id 4801E70000EF; Wed,  5 Oct 2011 09:56:24 +0200 (CEST)
X-SFR-UUID: 20111005075624295.4801E70000EF@msfrf2318.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <067E6CE33034954AAC05C9EC85E2577C0613BAC1@XMB-RCD-111.cisco.com>
Date: Wed, 5 Oct 2011 09:56:25 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B14D2395-3C09-462D-8132-6497180D16B6@laposte.net>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com> <067E6CE33034954AAC05C9EC85E2577C0613BAC1@XMB-RCD-111.cisco.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: softwires@ietf.org, "Wojciech Dec \(wdec\)" <wdec@cisco.com>, xiaohong deng <dxhbupt@gmail.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 05 Oct 2011 07:53:23 -0000

Le 5 oct. 2011 =E0 03:28, Rajiv Asati (rajiva) a =E9crit :

>> ability instead of the more general five-tuple based IPv4
>> classification ability should be reserved, when deliver IPv4 over
>> IPv6?
>=20
> How would one get 5-tuple based classification when delivering IPv4 =
"over" IPv6, if the v4 packet is not translated into v6?
>=20
> The fact of the matter is that "5-tuple" could be a luxury that may =
not always be available.

Questions for clarification about 5-tuple-based actions of intermediate =
nodes that are currently used:
- Do we know whether they generally work with IPv6 packets having =
extension headers?
- If yes, with which ones?
- In particular, are fragment headers always supported (with ports =
available only in first fragments)?

Thanks,
RD


>=20
> Cheers,
> Rajiv
>=20
>=20
>> -----Original Message-----
>> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] =
On Behalf
>> Of xiaohong deng
>> Sent: Tuesday, October 04, 2011 3:26 AM
>> To: Wojciech Dec (wdec); despres.remi@laposte.net; =
otroan@employees.org;
>> bingxuere@gmail.com; softwires@ietf.org
>> Subject: Re: [Softwires] 4rd Address Mapping - version-01
>>=20
>> Hi Remi, Ole, Woj, and all,
>>=20
>> I understand the argument of IID bits is resulted from a last minute
>> agreement between 4rd and divi-pd people that having full IPv4 =
address
>> embedded in the address format helps source based classification, but
>> before we argue that, shall we first make this agreement also be
>> accepted by community wide? As far as current time-being concerned, I
>> don't see a consensus has been reached on this agreement from
>> community wide.
>>=20
>> It IMHO would be helpful if anybody would clarify some details to 1)
>> first prove source based classification is either a valid or a
>> non-valid requirement for address mapping; For this regard, I would
>> begin with that why do we think the source based IPv4 classification
>> ability instead of the more general five-tuple based IPv4
>> classification ability should be reserved, when deliver IPv4 over
>> IPv6?
>>=20
>>=20
>> and 2) then show us how much other efforts are required to achieve so
>> besides address format definition itself, in other words, if it's a
>> valid requirement, let's first have feasibility of this requirement
>> analyzed from both deployment and operational perspectives:
>>=20
>> 1. For double translation, how does a traditional router perform the
>> source based IPv4 packet classification on IPv6 (translated from =
IPv4)
>> packets? Or does it suggest that using IPv6 classification filters to
>> filter IPv4 packets? If so, should we also note that this suggests
>> IPv4 operation and managed are tightly coupled with IPv6 operation =
and
>> management? which in turn implies complexity in operational, or put =
in
>> other words, OPEX increasing, the last thing among others that
>> operators would like to see.
>>=20
>> 2. For encapsulation, even if embedding source IPv4 addresses in the
>> lower bits of the address formats, where does the router find the
>> source port without de-capsulation? Are you suggesting also encode 16
>> bits port in the lower part of address? In either case, it leads to
>> the concerns of increased OPEX to operators stated above.
>>=20
>> Thoughts?
>>=20
>> Cheers,
>> Xiaohong
>>=20
>>> Hi Qiong,
>>>=20
>>> Some fields of a unified address format for double translation and
>>> encapsulation might be unnecessary for hub and spoke, but using the
>>> same format should be advantageous for maintenance and training if =
for
>>> nothing else (assuming that any added complexity is negligible
>>> enough).
>>>=20
>>> Believing that a completely unified format is possible, I mentioned =
it to
>> Alain.
>>> Also, I volunteered to be editor-coordinator for this to happen, but
>>> decision of who does what is his.
>>>=20
>>> Regards,
>>> RD
>>>=20
>>>=20
>>> Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit :
>>>=20
>>>> Hi Remi and Wojciech,
>>>>=20
>>>> Thanks for your clarification. I fully agree with you that =
embedding the
>> full IPv4 address in the last 64 bits would be quite helpful for some =
kind of
>> source address classification and I also suggest that this can be =
taken in the
>> same way for encapsulation-based approach. It would be easier for =
systems in-
>> the-middle to identify the IPv4 address without packet decapsulation.
>>>>=20
>>>> I guess the thing that Ole has mentioned to "look at 24 bits in the =
middle
>> of IPv6 address" is for CE to determine whether a downstream IPv6 =
packet
>> should be taken for translation or native forwarding. Here, for a =
dual-stack
>> host, there would be no difference in the first /64 bits for a native =
IPv6
>> packet and a translated packet. What's why the CE should further =
looking into
>> the last 64 bits to determine the translation process or native =
forwarding.
>> Maybe Ole can clarify for this part again.
>>>>=20
>>>> However, the situation would still be different in "Hub & Spoke" =
and "Mesh"
>> mode. For Hub & Spoke case, since BR will have a default =
prefix/address, it
>> would be easily to identify the translated traffic from native IPv6 =
traffic by
>> just doing source address routing lookup for a downstream packet. So, =
the
>> corresponding mechanics would be different.
>>>>=20
>>>> Thanks
>>>>=20
>>>> Best wishes
>>>>=20
>>>> Qiong
>>>>=20
>>>> 2011/10/3 Wojciech Dec <wdec at cisco.com>
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>    On 02/10/2011 02:58, "Qiong" <bingxuere at gmail.com> wrote:
>>>>=20
>>>>        Hi Ole and Remi,
>>>>=20
>>>>> This is my answer to your first (double) question.
>>>>> If it is not enough, as suggested below, please explain what
>> you don't understand.
>>>>=20
>>>>            I specifically do not want a solution that changes =
forwarding
>> behaviour for _all_ IPv6 packets.
>>>>            e.g. looking at 24 bits in the middle of an IPv6 address =
is
>> such a change.
>>>>=20
>>>>            Woj> What are you referring to? Routing "just works" as =
normal
>> and is non disaggregated because of the CE-index in the prefix. =
Classification
>> can/is done on a subset of the v6 address, and that is perfectly =
legit.
>>>>=20
>>>>=20
>>>>            I don't understand what requirements you are basing this
>> 'solution' on.
>>>>            if the 4rd / dIVI CE takes (a well known or provisioned) =
/64
>> prefix out of the delegated prefix. then why do you need any of that?
>>>>=20
>>>>=20
>>>>        Qiong : I agree that routing lookup for a provisioned /64 =
prefix
>> would be better that extracting certain bits for each IPv6 address in =
CE. This
>> would bring less change to existing routing model.
>>>>=20
>>>>        Woj> There is no change to the existing destination based =
routing
>> model. Each CE is uniquely addressed by the CE bits in the top /64 - =
ie the CE
>> index is as proposed by all the 4rd and divi-pd drafts. The full v4 =
source
>> address of each CE is however also embedded in the interface-id, as =
per
>> RFC6052. There appears to be no cost for this operation, and has the =
upside of
>> the full v4 info visible in the header and allowing source based
>> classification (should one want to do that).
>>>>=20
>>>>        Regards,
>>>>        Woj.
>>>>=20
>>>>        Best wishes
>>>>=20
>>>>        Qiong
>>>>=20
>>>>            _______________________________________________
>>>>            Softwires mailing list
>>>>            Softwires at ietf.org
>>>>            https://www.ietf.org/mailman/listinfo/softwires
>>>>=20
>>>>=20
>>>>=20
>>>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20

From cx.cernet@gmail.com  Wed Oct  5 02:39:45 2011
Return-Path: <cx.cernet@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 776A121F8B58 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 02:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.146
X-Spam-Level: 
X-Spam-Status: No, score=-3.146 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0sxRGyGuqPw for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 02:39:44 -0700 (PDT)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 2A06721F8A64 for <softwires@ietf.org>; Wed,  5 Oct 2011 02:39:44 -0700 (PDT)
Received: by pzk37 with SMTP id 37so3772627pzk.9 for <softwires@ietf.org>; Wed, 05 Oct 2011 02:42:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Sn/fmIKgQh/GHNSMiuQhJ7BsPKNllmAQoBTjgbUAP5M=; b=n2EJ9+CWVZwaVlOww5ovX+aThncvftGXav6BXxSxvxs6X3Cvj9wkKGxZ3kfqVbVKsH YV99YXvdafNt9OG00/CjtzKlxdoOc1zVYowopvtetZL/8F3l1QMW+B/LZ0sYZePAx5px Ve8EXa++vcmm/D2LRbcNYLkYi++RJDspeKK/g=
MIME-Version: 1.0
Received: by 10.68.55.69 with SMTP id q5mr17021586pbp.81.1317807771655; Wed, 05 Oct 2011 02:42:51 -0700 (PDT)
Received: by 10.142.162.1 with HTTP; Wed, 5 Oct 2011 02:42:51 -0700 (PDT)
In-Reply-To: <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net>
Date: Wed, 5 Oct 2011 17:42:51 +0800
Message-ID: <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com>
From: Congxiao Bao <cx.cernet@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=bcaec53961d61c9e9904ae8a08c3
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 05 Oct 2011 09:39:45 -0000

--bcaec53961d61c9e9904ae8a08c3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

2011/10/5 R=E9mi Despr=E9s <despres.remi@laposte.net>

> Hi Gang,
>
> Thanks for your comments.
> More below.
>
>
> Le 5 oct. 2011 =E0 01:10, GangChen a =E9crit :
>
> > Hello Remi,
> >
> > I'm trying to put some comments for such unified address mapping.
> > Regarding the deterministic benefit for double translation, I guess we
> > only could use V bits to achieve.
>
> Right.
> V is indeed a reliable tool for this.
>

If ISP wants to use a single IPv6 prefix for double translation and
Encapsulation, V mark is need.

>
>
> > There are no necessary to put IPv4 and Port-set ID information in last
> > 64 bits.
>
> The CE Pv6 prefix included in the /64 Subnet prefix isn't self delimited,
> so that the length of the CE index can't be determined in this part of th=
e
> address.
> Having the length of the A or A+P prefix in the IID completes what is
> needed to derive the CE port-set.
>


Besides, if a medium or large size ISP can=92t get short enough IPv6 prefix
(ex. /24), the first 64 bits can not contain the whole IPv4 32 bits, which
cannot make the double translation successful.

>
>
> > If I understand correctly, the encoded IPv4 and Port-set ID could help
> > to derive a shared/dedicated IPv4 address or IPv4 subnet from the IPv6
> > prefix.
>
> Yes.
> Besides, having the IPv4 address (or prefix) in clear form, and with an
> explicit sharing ratio, facilitates maintenance at essentially no cost.
>


Agree. Having whole IPv4 address in clear form is very critical for
operation, like IPv6 ACL.


>
> > It may help encapsulation in same cases(e.g. IPv4 based traffic
> > classification,IPv4 ACL, etc).
> > However, the translation case is more preferable doing pure IPv6 based
> > control for the sake of simpler operation reasons (e.g. IPv6 ACL).
> > It's desirable identifying a customer depending on first 64 bits.
>
> A point is that, although some realistic deployments may ignore what is
> made available in IIDs (at least at the beginning), some others would tak=
e
> advantage of it.
> A standard with a straightforward and unified format is AFAIK better than
> several variants, at least for documentation, training, maintenance etc.
>
> Note also that even with a single standard, it remains possible to add
> optional variants if found useful for some deployments.
>


The ISP is not able to achieve per-host traffic control without a standard
defining last 64 bits. If the ISP does, why not use IPv4+psid in suffix
naturally instead of other new bits definition?



Best,



Congxiao

>
> Hope it clarifies.
>
>
> Regards,
> RD
>
>
> >
> > Many thanks
> >
> >
> >
> > Gang
> >
> > 2011/10/4, R=E9mi Despr=E9s <despres.remi@laposte.net>:
> >> Hi all,
> >>
> >> 1.
> >> Here is a unified Address Mapping, for both encapsulation and
> >> double-translation approaches, that is PROPOSED for IPv4 residual
> deployment
> >> across IPv6-only routing domains.
> >>
> >> It results from an informal meeting among participants having differen=
t
> >> preferences between double-translation and encapsulation solutions (Xi=
ng
> Li,
> >> Congxiao Bao, Wojciech Dec, myself, at the end of the Beijing meeting)=
.
> >>
> >> The idea is to have a common format that is good for both types of
> >> solutions.
> >> In particular:
> >> - It enriches Double translation by introducing a deterministic way to
> >> distinguish a translated IPv4 packet from a native IPv6 packet.
> >> - It enriches Encapsulation by expressing, in clear format within an
> IPv6
> >> address, an IPv4 address, an IPv4 prefix, or an IPv4 address + port-se=
t
> ID.
> >>
> >>
> >> 2.
> >> (a)
> >> The IPv6 Source address of an IPv4 packet from a CE is:
> >>
> >> a1- If the CE has an exclusive or shared IPv4 address:
> >>
> >> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
> >> +-------------+--------+---+---+----------------+------+-----+---+
> >> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
> >> +-------------+--------+---+---+----------------+------+-----+---+
> >>
> >> a2- If the CE has an IPv4 prefix:
> >>
> >> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
> >> +-------------+--------+---+---+-------------+---------------+---+
> >> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
> >> +-------------+--------+---+---+-------------+---------------+---+
> >>
> >> (b)
> >> V is the mark that characterizes IPv6 packets that are in reality IPv4
> >> packets.
> >> Its value differs from any permitted value of this octet in IPv6 IIDs
>  (ref
> >> RFC 4291).
> >>
> >> It is understood that, if double Translation coexists with single
> >> translation, concerned ISPs may notify their CEs to use the U octet of
> RFC
> >> 6052 instead of V.
> >>
> >> An unambiguous mark is fortunately possible because currently permitte=
d
> IIDs
> >> have in their first octet either bit6 =3D 0 (the "u" bit"), or bit6 =
=3D 1
> and
> >> bit7=3D 0 (the "g" bit).
> >> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1,
> distinction
> >> is therefore deterministic.
> >>
> >> The proposed V is =3D 00000011.
> >> (With other values of this octet, other IID formats can be defined in
> case
> >> some would be useful in the future.)
> >>
> >> Note that, if and when a consensus is reached in Softwire, an extensio=
n
> of
> >> RFC 4291 will have to be submitted to 6MAN.
> >>
> >> (c)
> >> A Destination address from a CE to the outside IPv4 Internet is:
> >> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> >> +--------------------------+----+---------------+------------+---+
> >> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
> >> +--------------------------+----+---------------+------------+---+
> >>
> >> Note that if double-translation CEs are notified to use U instead of V=
,
> the
> >> last octet becomes 0 per RFC  6052.
> >>
> >>
> >> 3.
> >> All comments are most welcome.
> >>
> >> Kind regards to all,
> >> RD
> >>
> >>
> >> _______________________________________________
> >> Softwires mailing list
> >> Softwires@ietf.org
> >> https://www.ietf.org/mailman/listinfo/softwires
> >>
> >
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

--bcaec53961d61c9e9904ae8a08c3
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>
<div class=3D"gmail_quote">2011/10/5 R=E9mi Despr=E9s <span dir=3D"ltr">&lt=
;<a href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&g=
t;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">Hi Gang,<br><br>Thanks for your =
comments.<br>More below.<br><br><br>Le 5 oct. 2011 =E0 01:10, GangChen a =
=E9crit :<br>

<div class=3D"im"><br>&gt; Hello Remi,<br>&gt;<br>&gt; I&#39;m trying to pu=
t some comments for such unified address mapping.<br>&gt; Regarding the det=
erministic benefit for double translation, I guess we<br>&gt; only could us=
e V bits to achieve.<br>
<br></div>Right.<br>V is indeed a reliable tool for this.<br></blockquote>
<div><span lang=3D"EN-US"><font size=3D"3" face=3D"Times New Roman"></font>=
</span>=A0</div>
<div><span lang=3D"EN-US"><font size=3D"3" face=3D"Times New Roman">If ISP =
wants to use a single IPv6 prefix for double translation and Encapsulation,=
 V mark is need.</font></span></div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div class=3D"im"><br><br>&gt; There are no necessary to put IPv4 and Port-=
set ID information in last<br>&gt; 64 bits.<br><br></div>The CE Pv6 prefix =
included in the /64 Subnet prefix isn&#39;t self delimited, so that the len=
gth of the CE index can&#39;t be determined in this part of the address.<br=
>
Having the length of the A or A+P prefix in the IID completes what is neede=
d to derive the CE port-set.<br></blockquote>
<div>=A0</div>
<div>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman">Besides, if a medium or large size=
 ISP can=92t get short enough IPv6 prefix (ex. /24), the first 64 bits can =
not contain the whole IPv4 32 bits, which cannot make the double translatio=
n successful.</font></span></p>
</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div class=3D"im"><br><br>&gt; If I understand correctly, the encoded IPv4 =
and Port-set ID could help<br>&gt; to derive a shared/dedicated IPv4 addres=
s or IPv4 subnet from the IPv6<br>&gt; prefix.<br><br></div>Yes.<br>Besides=
, having the IPv4 address (or prefix) in clear form, and with an explicit s=
haring ratio, facilitates maintenance at essentially no cost.<br>
</blockquote>
<div>=A0</div>
<div>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman">Agree. Having whole IPv4 address i=
n clear form is very critical for operation, like IPv6 ACL.</font></span></=
p></div>

<div>=A0</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div class=3D"im"><br>&gt; It may help encapsulation in same cases(e.g. IPv=
4 based traffic<br>&gt; classification,IPv4 ACL, etc).<br>&gt; However, the=
 translation case is more preferable doing pure IPv6 based<br>&gt; control =
for the sake of simpler operation reasons (e.g. IPv6 ACL).<br>
&gt; It&#39;s desirable identifying a customer depending on first 64 bits.<=
br><br></div>A point is that, although some realistic deployments may ignor=
e what is made available in IIDs (at least at the beginning), some others w=
ould take advantage of it.<br>
A standard with a straightforward and unified format is AFAIK better than s=
everal variants, at least for documentation, training, maintenance etc.<br>=
<br>Note also that even with a single standard, it remains possible to add =
optional variants if found useful for some deployments.<br>
</blockquote>
<div>=A0</div>
<div>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman">The ISP is not able to achieve per=
-host traffic control without a standard defining last 64 bits. If the ISP =
does, why not use IPv4+psid in suffix naturally instead of other new bits d=
efinition?</font></span></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman"></font></span>=A0</p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman">Best,</font></span></p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman"></font></span>=A0</p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman">Congxiao</font></span></p></div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>Hope it clarifies.<br><br><b=
r>Regards,<br><font color=3D"#888888">RD<br></font>
<div>
<div></div>
<div class=3D"h5"><br><br>&gt;<br>&gt; Many thanks<br>&gt;<br>&gt;<br>&gt;<=
br>&gt; Gang<br>&gt;<br>&gt; 2011/10/4, R=E9mi Despr=E9s &lt;<a href=3D"mai=
lto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;:<br>&gt;&gt;=
 Hi all,<br>
&gt;&gt;<br>&gt;&gt; 1.<br>&gt;&gt; Here is a unified Address Mapping, for =
both encapsulation and<br>&gt;&gt; double-translation approaches, that is P=
ROPOSED for IPv4 residual deployment<br>&gt;&gt; across IPv6-only routing d=
omains.<br>
&gt;&gt;<br>&gt;&gt; It results from an informal meeting among participants=
 having different<br>&gt;&gt; preferences between double-translation and en=
capsulation solutions (Xing Li,<br>&gt;&gt; Congxiao Bao, Wojciech Dec, mys=
elf, at the end of the Beijing meeting).<br>
&gt;&gt;<br>&gt;&gt; The idea is to have a common format that is good for b=
oth types of<br>&gt;&gt; solutions.<br>&gt;&gt; In particular:<br>&gt;&gt; =
- It enriches Double translation by introducing a deterministic way to<br>
&gt;&gt; distinguish a translated IPv4 packet from a native IPv6 packet.<br=
>&gt;&gt; - It enriches Encapsulation by expressing, in clear format within=
 an IPv6<br>&gt;&gt; address, an IPv4 address, an IPv4 prefix, or an IPv4 a=
ddress + port-set ID.<br>
&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; 2.<br>&gt;&gt; (a)<br>&gt;&gt; The IPv6 So=
urce address of an IPv4 packet from a CE is:<br>&gt;&gt;<br>&gt;&gt; a1- If=
 the CE has an exclusive or shared IPv4 address:<br>&gt;&gt;<br>&gt;&gt; &l=
t;--------- 64 ------------&gt;&lt;8 &gt;&lt;------ L &gt;=3D 32 -------&gt=
;&lt;48-L&gt;&lt;8 &gt;<br>
&gt;&gt; +-------------+--------+---+---+----------------+------+-----+---+=
<br>&gt;&gt; | IPv6 prefix |CE index| 0 | V | =A0IPv4 address =A0| PSID | =
=A00 =A0| L |<br>&gt;&gt; +-------------+--------+---+---+----------------+=
------+-----+---+<br>
&gt;&gt;<br>&gt;&gt; a2- If the CE has an IPv4 prefix:<br>&gt;&gt;<br>&gt;&=
gt; &lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;-- L &lt; 32 --&gt;&lt;-=
-- 48-L -----&gt;&lt;8 &gt;<br>&gt;&gt; +-------------+--------+---+---+---=
----------+---------------+---+<br>
&gt;&gt; | IPv6 prefix |CE index| 0 | V | IPv4 prefix | =A0 =A0 =A0 =A0 0 =
=A0 =A0 | L |<br>&gt;&gt; +-------------+--------+---+---+-------------+---=
------------+---+<br>&gt;&gt;<br>&gt;&gt; (b)<br>&gt;&gt; V is the mark tha=
t characterizes IPv6 packets that are in reality IPv4<br>
&gt;&gt; packets.<br>&gt;&gt; Its value differs from any permitted value of=
 this octet in IPv6 IIDs =A0(ref<br>&gt;&gt; RFC 4291).<br>&gt;&gt;<br>&gt;=
&gt; It is understood that, if double Translation coexists with single<br>
&gt;&gt; translation, concerned ISPs may notify their CEs to use the U octe=
t of RFC<br>&gt;&gt; 6052 instead of V.<br>&gt;&gt;<br>&gt;&gt; An unambigu=
ous mark is fortunately possible because currently permitted IIDs<br>&gt;&g=
t; have in their first octet either bit6 =3D 0 (the &quot;u&quot; bit&quot;=
), or bit6 =3D 1 and<br>
&gt;&gt; bit7=3D 0 (the &quot;g&quot; bit).<br>&gt;&gt; With V having &quot=
;u&quot; =3D 1 (signifying Universal scope) AND &quot;g&quot; =3D 1, distin=
ction<br>&gt;&gt; is therefore deterministic.<br>&gt;&gt;<br>&gt;&gt; The p=
roposed V is =3D 00000011.<br>
&gt;&gt; (With other values of this octet, other IID formats can be defined=
 in case<br>&gt;&gt; some would be useful in the future.)<br>&gt;&gt;<br>&g=
t;&gt; Note that, if and when a consensus is reached in Softwire, an extens=
ion of<br>
&gt;&gt; RFC 4291 will have to be submitted to 6MAN.<br>&gt;&gt;<br>&gt;&gt=
; (c)<br>&gt;&gt; A Destination address from a CE to the outside IPv4 Inter=
net is:<br>&gt;&gt; &lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- =
=A0 32 ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;<br>
&gt;&gt; +--------------------------+----+---------------+------------+---+=
<br>&gt;&gt; | =A0 =A0 BR subnet prefix =A0 =A0 | V =A0| =A0IPv4 address | =
=A0 =A0 =A00 =A0 =A0 |32 |<br>&gt;&gt; +--------------------------+----+---=
------------+------------+---+<br>
&gt;&gt;<br>&gt;&gt; Note that if double-translation CEs are notified to us=
e U instead of V, the<br>&gt;&gt; last octet becomes 0 per RFC =A06052.<br>=
&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; 3.<br>&gt;&gt; All comments are most welco=
me.<br>
&gt;&gt;<br>&gt;&gt; Kind regards to all,<br>&gt;&gt; RD<br>&gt;&gt;<br>&gt=
;&gt;<br>&gt;&gt; _______________________________________________<br>&gt;&g=
t; Softwires mailing list<br>&gt;&gt; <a href=3D"mailto:Softwires@ietf.org"=
>Softwires@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>&gt;&gt;=
<br>&gt;<br><br>_______________________________________________<br>Softwire=
s 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"_blank">https://=
www.ietf.org/mailman/listinfo/softwires</a><br></div></div></blockquote></d=
iv>
<br>

--bcaec53961d61c9e9904ae8a08c3--

From bingxuere@gmail.com  Wed Oct  5 07:42:18 2011
Return-Path: <bingxuere@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 8B8EC21F8C56 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 07:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.086
X-Spam-Level: 
X-Spam-Status: No, score=-3.086 tagged_above=-999 required=5 tests=[AWL=-0.388, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DbghkjNcaepy for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 07:42:17 -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 64CF021F8C50 for <softwires@ietf.org>; Wed,  5 Oct 2011 07:42:17 -0700 (PDT)
Received: by gyd12 with SMTP id 12so1990066gyd.31 for <softwires@ietf.org>; Wed, 05 Oct 2011 07:45:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Ee1HIwtIjqWTELqQJCOPXytfaz43AE+fbn+7sHkLKgg=; b=OYpDpHX9OeaeZzZ9pAX1akVPBDU1/5H6brp1n9VONSeEjVEdY9AjceZQ8B5m3pWwR3 NtBM6NjTW9ai5NUEFPnePatJ4s8T9A0X/CbgpU1x7XPI9JHbEPK6CnHvc7C/Mjv3wiP+ Ug3yqQKDMXtJ2x5KZvDwPWV9Ww5N2uttXkvKc=
Received: by 10.43.135.10 with SMTP id ie10mr406586icc.91.1317825920402; Wed, 05 Oct 2011 07:45:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Wed, 5 Oct 2011 07:45:00 -0700 (PDT)
In-Reply-To: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net>
From: Qiong <bingxuere@gmail.com>
Date: Wed, 5 Oct 2011 22:45:00 +0800
Message-ID: <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com>
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=20cf307f3ab6dc86c904ae8e41c8
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 05 Oct 2011 14:42:18 -0000

--20cf307f3ab6dc86c904ae8e41c8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Remi,

Thanks for your effort. I think this is a big progress after the Interim
meeting, and this unified address format is quite clear now. Here, I have
two comments after a quick review. And I will get back to you if I have mor=
e
comments later.

1. With regard to destination address format, if I understand correctly, it
only covers hub&spoke model with a default "BR subnet prefix". Are you
intended to propose another format for mesh one ? Or just cite the "Source
address format" as the destination address in MESH situation. I think it
would be better to declare it separately for "H&S" and "MESH". This would b=
e
more clearer for readers to understand different situations.

2. Still for the destination address format, I suggest to embed PSID as wel=
l
in the lower 64 bits (as in the following).

<--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
+--------------------------+----+---------------+------------+---+
|     BR subnet prefix     | V  |  IPv4 address  | PSID |  0  | L |
+--------------------------+----+---------------+------------+---+

This would make it easier for in-the-middle systems(e.g. BNG) to do prefix
mapping without packet decapsulation. And this is quite similar to the
source address format. What do you think of it?


Best wishes

Qiong


On Tue, Oct 4, 2011 at 12:22 PM, R=C3=A9mi Despr=C3=A9s <despres.remi@lapos=
te.net>wrote:

> Hi all,
>
> 1.
> Here is a unified Address Mapping, for both encapsulation and
> double-translation approaches, that is PROPOSED for IPv4 residual deploym=
ent
> across IPv6-only routing domains.
>
> It results from an informal meeting among participants having different
> preferences between double-translation and encapsulation solutions (Xing =
Li,
> Congxiao Bao, Wojciech Dec, myself, at the end of the Beijing meeting).
>
> The idea is to have a common format that is good for both types of
> solutions.
> In particular:
> - It enriches Double translation by introducing a deterministic way to
> distinguish a translated IPv4 packet from a native IPv6 packet.
> - It enriches Encapsulation by expressing, in clear format within an IPv6
> address, an IPv4 address, an IPv4 prefix, or an IPv4 address + port-set I=
D.
>
>
> 2.
> (a)
> The IPv6 Source address of an IPv4 packet from a CE is:
>
> a1- If the CE has an exclusive or shared IPv4 address:
>
> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
> +-------------+--------+---+---+----------------+------+-----+---+
> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
> +-------------+--------+---+---+----------------+------+-----+---+
>
> a2- If the CE has an IPv4 prefix:
>
> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
> +-------------+--------+---+---+-------------+---------------+---+
> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
> +-------------+--------+---+---+-------------+---------------+---+
>
> (b)
> V is the mark that characterizes IPv6 packets that are in reality IPv4
> packets.
> Its value differs from any permitted value of this octet in IPv6 IIDs  (r=
ef
> RFC 4291).
>
> It is understood that, if double Translation coexists with single
> translation, concerned ISPs may notify their CEs to use the U octet of RF=
C
> 6052 instead of V.
>
> An unambiguous mark is fortunately possible because currently permitted
> IIDs have in their first octet either bit6 =3D 0 (the "u" bit"), or bit6 =
=3D 1
> and bit7=3D 0 (the "g" bit).
> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, disti=
nction
> is therefore deterministic.
>
> The proposed V is =3D 00000011.
> (With other values of this octet, other IID formats can be defined in cas=
e
> some would be useful in the future.)
>
> Note that, if and when a consensus is reached in Softwire, an extension o=
f
> RFC 4291 will have to be submitted to 6MAN.
>
> (c)
> A Destination address from a CE to the outside IPv4 Internet is:
> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> +--------------------------+----+---------------+------------+---+
> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
> +--------------------------+----+---------------+------------+---+
>
> Note that if double-translation CEs are notified to use U instead of V, t=
he
> last octet becomes 0 per RFC  6052.
>
>
> 3.
> All comments are most welcome.
>
> Kind regards to all,
> RD
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

--20cf307f3ab6dc86c904ae8e41c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Remi,<div><br></div><div>Thanks for your effort. I think this is a big =
progress after the Interim meeting, and this unified address format is quit=
e clear now. Here, I have two comments after a quick review. And I will get=
 back to you if I have more comments later.</div>

<div><br></div><div>1. With regard to destination address format, if I unde=
rstand correctly, it only covers hub&amp;spoke model with a default &quot;<=
span class=3D"Apple-style-span" style=3D"font-family: arial, sans-serif; fo=
nt-size: 13px; background-color: rgb(255, 255, 255); ">BR subnet prefix</sp=
an>&quot;. Are you intended to propose another format for mesh one ? Or jus=
t cite the &quot;Source address format&quot; as the destination address in =
MESH situation. I think it would be better to=C2=A0declare=C2=A0it=C2=A0sep=
arately=C2=A0for &quot;H&amp;S&quot; and &quot;MESH&quot;. This would be mo=
re clearer for readers to understand different situations.</div>

<div><br></div><div>2. Still for the=C2=A0destination address format, I sug=
gest to embed PSID as well in the lower 64 bits (as in the following).</div=
><div><br></div><span class=3D"Apple-style-span" style=3D"font-family: aria=
l, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255); ">&lt=
;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- =C2=A0 32 ----&gt;&lt;---=
 16 ----&gt;&lt;8 &gt;<br>

+--------------------------+----+---------------+------------+---+<br>| =C2=
=A0 =C2=A0 BR subnet prefix =C2=A0 =C2=A0 | V =C2=A0| =C2=A0IPv4 address =
=C2=A0| PSID | =C2=A00 =C2=A0| L |<br></span><div><span class=3D"Apple-styl=
e-span" style=3D"font-family: arial, sans-serif; font-size: 13px; backgroun=
d-color: rgb(255, 255, 255); ">+--------------------------+----+-----------=
----+------------+---+</span>=C2=A0</div>

<div><br></div><div>This would make it easier=C2=A0for=C2=A0in-the-middle s=
ystems(e.g. BNG)=C2=A0to do prefix mapping without packet decapsulation. An=
d this is quite similar to the source address format. What do you think of =
it?</div><div>

<br></div><div><br></div><div>Best wishes</div><div><br></div><div>Qiong</d=
iv><div>=C2=A0=C2=A0</div><div><br><div class=3D"gmail_quote">On Tue, Oct 4=
, 2011 at 12:22 PM, R=C3=A9mi Despr=C3=A9s <span dir=3D"ltr">&lt;<a href=3D=
"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;</span> w=
rote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hi all,<br>
<br>
1.<br>
Here is a unified Address Mapping, for both encapsulation and double-transl=
ation approaches, that is PROPOSED for IPv4 residual deployment across IPv6=
-only routing domains.<br>
<br>
It results from an informal meeting among participants having different pre=
ferences between double-translation and encapsulation solutions (Xing Li, C=
ongxiao Bao, Wojciech Dec, myself, at the end of the Beijing meeting).<br>


<br>
The idea is to have a common format that is good for both types of solution=
s.<br>
In particular:<br>
- It enriches Double translation by introducing a deterministic way to dist=
inguish a translated IPv4 packet from a native IPv6 packet.<br>
- It enriches Encapsulation by expressing, in clear format within an IPv6 a=
ddress, an IPv4 address, an IPv4 prefix, or an IPv4 address + port-set ID.<=
br>
<br>
<br>
2.<br>
(a)<br>
The IPv6 Source address of an IPv4 packet from a CE is:<br>
<br>
a1- If the CE has an exclusive or shared IPv4 address:<br>
<br>
&lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;------ L &gt;=3D 32 -------&=
gt;&lt;48-L&gt;&lt;8 &gt;<br>
+-------------+--------+---+---+----------------+------+-----+---+<br>
| IPv6 prefix |CE index| 0 | V | =C2=A0IPv4 address =C2=A0| PSID | =C2=A00 =
=C2=A0| L |<br>
+-------------+--------+---+---+----------------+------+-----+---+<br>
<br>
a2- If the CE has an IPv4 prefix:<br>
<br>
&lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;-- L &lt; 32 --&gt;&lt;--- 4=
8-L -----&gt;&lt;8 &gt;<br>
+-------------+--------+---+---+-------------+---------------+---+<br>
| IPv6 prefix |CE index| 0 | V | IPv4 prefix | =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
0 =C2=A0 =C2=A0 | L |<br>
+-------------+--------+---+---+-------------+---------------+---+<br>
<br>
(b)<br>
V is the mark that characterizes IPv6 packets that are in reality IPv4 pack=
ets.<br>
Its value differs from any permitted value of this octet in IPv6 IIDs =C2=
=A0(ref RFC 4291).<br>
<br>
It is understood that, if double Translation coexists with single translati=
on, concerned ISPs may notify their CEs to use the U octet of RFC 6052 inst=
ead of V.<br>
<br>
An unambiguous mark is fortunately possible because currently permitted IID=
s have in their first octet either bit6 =3D 0 (the &quot;u&quot; bit&quot;)=
, or bit6 =3D 1 and bit7=3D 0 (the &quot;g&quot; bit).<br>
With V having &quot;u&quot; =3D 1 (signifying Universal scope) AND &quot;g&=
quot; =3D 1, distinction is therefore deterministic.<br>
<br>
The proposed V is =3D 00000011.<br>
(With other values of this octet, other IID formats can be defined in case =
some would be useful in the future.)<br>
<br>
Note that, if and when a consensus is reached in Softwire, an extension of =
RFC 4291 will have to be submitted to 6MAN.<br>
<br>
(c)<br>
A Destination address from a CE to the outside IPv4 Internet is:<br>
&lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- =C2=A0 32 ----&gt;&lt;=
--- 16 ----&gt;&lt;8 &gt;<br>
+--------------------------+----+---------------+------------+---+<br>
| =C2=A0 =C2=A0 BR subnet prefix =C2=A0 =C2=A0 | V =C2=A0| =C2=A0IPv4 addre=
ss | =C2=A0 =C2=A0 =C2=A00 =C2=A0 =C2=A0 |32 |<br>
+--------------------------+----+---------------+------------+---+<br>
<br>
Note that if double-translation CEs are notified to use U instead of V, the=
 last octet becomes 0 per RFC =C2=A06052.<br>
<br>
<br>
3.<br>
All comments are most welcome.<br>
<br>
Kind regards to all,<br>
RD<br>
<br>
<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>
</blockquote></div><br></div>

--20cf307f3ab6dc86c904ae8e41c8--

From satoru.matsushima@gmail.com  Wed Oct  5 09:18:42 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 5F9661F0C3B for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 09:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.413
X-Spam-Level: 
X-Spam-Status: No, score=-3.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w-muZRpZTCES for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 09:18:42 -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 CCF321F0C3D for <softwires@ietf.org>; Wed,  5 Oct 2011 09:18:41 -0700 (PDT)
Received: by vws5 with SMTP id 5so1854694vws.31 for <softwires@ietf.org>; Wed, 05 Oct 2011 09:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=LPvYHaxRe6O41YtivZcq/8a/UNETtE3Gh7YHX9KQqGw=; b=PxuZbuTVUNdqeqEWPw8hNoG4IIZC/s3ux2ZduJPmKvTGbNUGJDfWCHX4RgjMT83pjg 0F+/e6ZnArfltuEZd7blVhF/xy4Y1VErVK+KNg9L1Mic+alHSkGfOcyg8afUZUkOa1BI 845WPS5MMbLQVS0kiq7JgRYw/5h87k/i3NXww=
Received: by 10.68.19.196 with SMTP id h4mr19914313pbe.39.1317831708709; Wed, 05 Oct 2011 09:21:48 -0700 (PDT)
Received: from [192.168.10.54] (softbank221038132005.bbtec.net. [221.38.132.5]) by mx.google.com with ESMTPS id i3sm8957258pbg.10.2011.10.05.09.21.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 05 Oct 2011 09:21:46 -0700 (PDT)
From: Satoru Matsushima <satoru.matsushima@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 Oct 2011 01:21:43 +0900
Message-Id: <4AC8DFFB-4B49-43C2-B0C7-6E77A5129290@gmail.com>
To: "softwires@ietf.org list" <softwires@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1244.3)
X-Mailer: Apple Mail (2.1244.3)
Subject: [Softwires] The outcome and minutes of the interim meeting
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, 05 Oct 2011 16:18:42 -0000

Could anyone can share the minutes and an outcome of the interim meeting =
to the list?
In particularly, who is the member of design team of address mapping?

cheers,
--satoru


From phdgang@gmail.com  Wed Oct  5 14:58:57 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 3A00A21F8D36 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 14:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.406
X-Spam-Level: 
X-Spam-Status: No, score=-3.406 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id giFD4alsUIBZ for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 14:58:56 -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 7E55D21F8D15 for <softwires@ietf.org>; Wed,  5 Oct 2011 14:58:56 -0700 (PDT)
Received: by wyh21 with SMTP id 21so2522705wyh.31 for <softwires@ietf.org>; Wed, 05 Oct 2011 15:02:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=fM8R9Nlf2g6C5Ubbk6tGfA0s3zH4hUAT8301UXSg1k8=; b=vydbY/EE/LjqwSUMdqXSG1lQs+x3FKsILXNWp9+TV0qJJvQTuWsJiiSNWT3iC3U+VT GAj2McEBVj+FC97T6jAoxcJkA5DBqNyFMc+tEHg/STjZZN8cEsk/a1CpePafjZmW7ksR 03Z5rUpBpQONyctVRbPt59BpNzjq+9YNsz2IM=
MIME-Version: 1.0
Received: by 10.216.159.1 with SMTP id r1mr160636wek.18.1317852124854; Wed, 05 Oct 2011 15:02:04 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Wed, 5 Oct 2011 15:01:59 -0700 (PDT)
In-Reply-To: <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net>
Date: Thu, 6 Oct 2011 06:01:59 +0800
Message-ID: <CAM+vMEQ4=xxgBgoqDAcd=t_Yx=j+wJm-rP-haJwdSxRSOv5sVQ@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 05 Oct 2011 21:58:57 -0000

Hello Remi,

Thanks for the answers.
Please see my reply inline.

2011/10/5, R=E9mi Despr=E9s <despres.remi@laposte.net>:
>> There are no necessary to put IPv4 and Port-set ID information in last
>> 64 bits.
>
> The CE Pv6 prefix included in the /64 Subnet prefix isn't self delimited,=
 so
> that the length of the CE index can't be determined in this part of the
> address.
> Having the length of the A or A+P prefix in the IID completes what is nee=
ded
> to derive the CE port-set.

I understand such encoded information helps deriving a shared IPv4
address. However, I guess it's not necessary to dig up such
information if we only take traffic contronl on IPv6 data plane (as I
said below)


>> It may help encapsulation in same cases(e.g. IPv4 based traffic
>> classification,IPv4 ACL, etc).
>> However, the translation case is more preferable doing pure IPv6 based
>> control for the sake of simpler operation reasons (e.g. IPv6 ACL).
>> It's desirable identifying a customer depending on first 64 bits.
>
> A point is that, although some realistic deployments may ignore what is m=
ade
> available in IIDs (at least at the beginning), some others would take
> advantage of it.

Yes. I agree with your point here. As you said such IID design may not
be taken effect on some realistic deployments, I would like to suggest
the IID MAY not appeared in double translation cases.


Many thanks

Gang

From phdgang@gmail.com  Wed Oct  5 15:11:45 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 2395721F8BD3 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 15:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.543
X-Spam-Level: 
X-Spam-Status: No, score=-3.543 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktGqkkCKa50t for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 15:11:44 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 503C821F8BB1 for <softwires@ietf.org>; Wed,  5 Oct 2011 15:11:44 -0700 (PDT)
Received: by wwn22 with SMTP id 22so7028105wwn.1 for <softwires@ietf.org>; Wed, 05 Oct 2011 15:14:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=yAo1p2yvE8VrxoTjHZ3z44rB6LbCgQJnh2eg46rLSBo=; b=oLhUzALofMuFZ04wwWia7PaC4oCl5YcuCxJoOtcv6xXpJUmbOdb0RT000rNsQDDpKH hJk09DKqvl/u3LIm53dvgxFTU1II4h8T5BARGGkCtYRRw/RbTVVZ3HzL/m77FYyxnV9H QZySoELKJc/m03OEWb6aC/QGM5IYlKsPmcMMY=
MIME-Version: 1.0
Received: by 10.227.154.66 with SMTP id n2mr13593wbw.3.1317852892500; Wed, 05 Oct 2011 15:14:52 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Wed, 5 Oct 2011 15:14:52 -0700 (PDT)
In-Reply-To: <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com>
Date: Thu, 6 Oct 2011 06:14:52 +0800
Message-ID: <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Congxiao Bao <cx.cernet@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 05 Oct 2011 22:11:45 -0000

Hello Congxiao,

Thanks for the discussion.
Please see my reply inline.

2011/10/5, Congxiao Bao <cx.cernet@gmail.com>:
>> > There are no necessary to put IPv4 and Port-set ID information in last
>> > 64 bits.
>>
>> The CE Pv6 prefix included in the /64 Subnet prefix isn't self delimited=
,
>> so that the length of the CE index can't be determined in this part of t=
he
>> address.
>> Having the length of the A or A+P prefix in the IID completes what is
>> needed to derive the CE port-set.
>
> Besides, if a medium or large size ISP can=92t get short enough IPv6 pref=
ix
> (ex. /24), the first 64 bits can not contain the whole IPv4 32 bits, whic=
h
> cannot make the double translation successful.

I guess that is depending on a specific algorithm. I don't see such
limitation in 4v6
translation(http://tools.ietf.org/html/draft-murakami-softwire-4v6-translat=
ion-00)

>>
>>
>> > If I understand correctly, the encoded IPv4 and Port-set ID could help
>> > to derive a shared/dedicated IPv4 address or IPv4 subnet from the IPv6
>> > prefix.
>>
>> Yes.
>> Besides, having the IPv4 address (or prefix) in clear form, and with an
>> explicit sharing ratio, facilitates maintenance at essentially no cost.

> Agree. Having whole IPv4 address in clear form is very critical for
> operation, like IPv6 ACL.

Could you kindly help elaborating why this is critical for IPv6 ACL?

>> > It may help encapsulation in same cases(e.g. IPv4 based traffic
>> > classification,IPv4 ACL, etc).
>> > However, the translation case is more preferable doing pure IPv6 based
>> > control for the sake of simpler operation reasons (e.g. IPv6 ACL).
>> > It's desirable identifying a customer depending on first 64 bits.
>>
>> A point is that, although some realistic deployments may ignore what is
>> made available in IIDs (at least at the beginning), some others would ta=
ke
>> advantage of it.
>> A standard with a straightforward and unified format is AFAIK better tha=
n
>> several variants, at least for documentation, training, maintenance etc.
>>
>> Note also that even with a single standard, it remains possible to add
>> optional variants if found useful for some deployments.
>>

> The ISP is not able to achieve per-host traffic control without a standar=
d
> defining last 64 bits. If the ISP does, why not use IPv4+psid in suffix
> naturally instead of other new bits definition?

First off, I'm not sure per-host traffic control is a common case for
network operations
Secondly, it could be possible to use first 64 bits differentiating
hosts. Please see Max PSID usage in
http://tools.ietf.org/html/draft-despres-softwire-4rd-addmapping-01#page-15

Many thanks

Gang

From fibrib@gmail.com  Wed Oct  5 19:05:14 2011
Return-Path: <fibrib@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 1A6991F0C67 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 19:05:14 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c32-clqE8uf8 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 19:05:13 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1ED1F0C55 for <softwires@ietf.org>; Wed,  5 Oct 2011 19:05:13 -0700 (PDT)
Received: by qyk32 with SMTP id 32so4391630qyk.10 for <softwires@ietf.org>; Wed, 05 Oct 2011 19:08:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IjcczLCpIzvBA3bgyTM5uuaEHOOVmaZqaHNnSa8Gn3s=; b=R84jMnTuttQ5+N0WFvl6n7IeDokvPo0HKGz5GKbPCCJQ/238wWL347ZXAwMtTzeChr VgyaDOjaEQNAe6KqRyNHn0NgRy/VMRWNh2VNX0z64MkKqYKO+THi7QqZbtwm2XmTyuMM OgdPg4pemxyPHOZ5MaTM7Fgf9358I7QsG5DUY=
MIME-Version: 1.0
Received: by 10.229.199.105 with SMTP id er41mr119735qcb.69.1317866902355; Wed, 05 Oct 2011 19:08:22 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Wed, 5 Oct 2011 19:08:22 -0700 (PDT)
In-Reply-To: <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com>
Date: Thu, 6 Oct 2011 11:08:22 +0900
Message-ID: <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: GangChen <phdgang@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6d2792593802704ae97cc0d
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 02:05:14 -0000

--0016e6d2792593802704ae97cc0d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

hi Gang,

trying to understand your point, may i follow your message inline? sorry if
my questions are trial/naive.

2011/10/6 GangChen <phdgang@gmail.com>

> Hello Congxiao,
>
> Thanks for the discussion.
> Please see my reply inline.
>
> 2011/10/5, Congxiao Bao <cx.cernet@gmail.com>:
> >> > There are no necessary to put IPv4 and Port-set ID information in la=
st
> >> > 64 bits.
> >>
> >> The CE Pv6 prefix included in the /64 Subnet prefix isn't self
> delimited,
> >> so that the length of the CE index can't be determined in this part of
> the
> >> address.
> >> Having the length of the A or A+P prefix in the IID completes what is
> >> needed to derive the CE port-set.
> >
> > Besides, if a medium or large size ISP can=92t get short enough IPv6 pr=
efix
> > (ex. /24), the first 64 bits can not contain the whole IPv4 32 bits,
> which
> > cannot make the double translation successful.
>
> I guess that is depending on a specific algorithm. I don't see such
> limitation in 4v6
> translation(
> http://tools.ietf.org/html/draft-murakami-softwire-4v6-translation-00)
>
>
i couldn't understand why we "don't see such limitation in 4v6 translation"=
.
4via6 translate the private ipv4 address with 4rd mapping rule while the
public ipv4 address with RFC6052 algorithm, right? can the both case work
fine if an ISP can only get a fairly long IPv6 prefix, like /40 or even
longer?


>
> > The ISP is not able to achieve per-host traffic control without a
> standard
> > defining last 64 bits. If the ISP does, why not use IPv4+psid in suffix
> > naturally instead of other new bits definition?
>
> First off, I'm not sure per-host traffic control is a common case for
> network operations
>

i think it is common for, maybe, not any network operators but at least som=
e
operators. especially for those running middle-to-small ISP services (like
my company), the capability of per-host traffic control is definitely
needed. a specific but not rare case is suppressing the pathologically
greedy download/upload behavior of bot-net boxes.

 Secondly, it could be possible to use first 64 bits differentiating

 hosts. Please see Max PSID usage in

http://tools.ietf.org/html/draft-despres-softwire-4rd-addmapping-01#page-15
>

sorry but i may not yet understand the mapping algorithm. is the Rule IPv6
prefix definitely short enough to take all Max CE in the first 64 bits?
again, what if an ISP can only get a fairly long IPv6 prefix?


>
>  Many thanks


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

--0016e6d2792593802704ae97cc0d
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>hi Gang,=A0</div><div><br></div><div>trying to understand your point, =
may i follow your message inline? sorry if my questions are trial/naive.=A0=
</div><br><div class=3D"gmail_quote">2011/10/6 GangChen <span dir=3D"ltr">&=
lt;<a href=3D"mailto:phdgang@gmail.com">phdgang@gmail.com</a>&gt;</span><br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hello Congxiao,<br>
<br>
Thanks for the discussion.<br>
<div class=3D"im">Please see my reply inline.<br>
<br>
</div>2011/10/5, Congxiao Bao &lt;<a href=3D"mailto:cx.cernet@gmail.com">cx=
.cernet@gmail.com</a>&gt;:<br>
<div class=3D"im">&gt;&gt; &gt; There are no necessary to put IPv4 and Port=
-set ID information in last<br>
&gt;&gt; &gt; 64 bits.<br>
&gt;&gt;<br>
&gt;&gt; The CE Pv6 prefix included in the /64 Subnet prefix isn&#39;t self=
 delimited,<br>
&gt;&gt; so that the length of the CE index can&#39;t be determined in this=
 part of the<br>
&gt;&gt; address.<br>
&gt;&gt; Having the length of the A or A+P prefix in the IID completes what=
 is<br>
&gt;&gt; needed to derive the CE port-set.<br>
&gt;<br>
&gt; Besides, if a medium or large size ISP can=92t get short enough IPv6 p=
refix<br>
&gt; (ex. /24), the first 64 bits can not contain the whole IPv4 32 bits, w=
hich<br>
&gt; cannot make the double translation successful.<br>
<br>
</div>I guess that is depending on a specific algorithm. I don&#39;t see su=
ch<br>
limitation in 4v6<br>
translation(<a href=3D"http://tools.ietf.org/html/draft-murakami-softwire-4=
v6-translation-00" target=3D"_blank">http://tools.ietf.org/html/draft-murak=
ami-softwire-4v6-translation-00</a>)<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>i couldn&#39;t=
 understand why we &quot;don&#39;t see such limitation in 4v6 translation&q=
uot;. 4via6 translate the private ipv4 address with 4rd mapping rule while =
the public ipv4 address with RFC6052 algorithm, right? can the both case wo=
rk fine if an ISP can only get a fairly long IPv6 prefix, like /40 or even =
longer?=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"im">=A0<br>
&gt; The ISP is not able to achieve per-host traffic control without a stan=
dard<br>
&gt; defining last 64 bits. If the ISP does, why not use IPv4+psid in suffi=
x<br>
&gt; naturally instead of other new bits definition?<br>
<br>
</div>First off, I&#39;m not sure per-host traffic control is a common case=
 for<br>
network operations<br></blockquote><div><br></div><div>i think it is common=
 for, maybe, not any network operators but at least some operators. especia=
lly for those running middle-to-small ISP services (like my company), the c=
apability of per-host traffic control is definitely needed. a specific but =
not rare case is suppressing the pathologically greedy download/upload beha=
vior of bot-net boxes.=A0</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">=A0Secondly, it could be pos=
sible to use first 64 bits differentiating=A0</blockquote><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
=A0hosts. Please see Max PSID usage in =A0</blockquote><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex;"><a href=3D"http://tools.ietf.org/html/draft-despres-softwire-4r=
d-addmapping-01#page-15" target=3D"_blank">http://tools.ietf.org/html/draft=
-despres-softwire-4rd-addmapping-01#page-15</a><br>
</blockquote><div><br></div><div>sorry but i may not yet understand the map=
ping algorithm. is the Rule IPv6 prefix definitely short enough to take all=
 Max CE in the first 64 bits? again, what if an ISP can only get a fairly l=
ong IPv6 prefix?=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">
<br>=A0Many thanks=A0</blockquote><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Gang<br>
<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>

--0016e6d2792593802704ae97cc0d--

From cx.cernet@gmail.com  Wed Oct  5 23:14:52 2011
Return-Path: <cx.cernet@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 A080A21F8C4F for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 23:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.318
X-Spam-Level: 
X-Spam-Status: No, score=-3.318 tagged_above=-999 required=5 tests=[AWL=0.280,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id abtzk4Qc0rp6 for <softwires@ietfa.amsl.com>; Wed,  5 Oct 2011 23:14:51 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id B98DC21F8C4E for <softwires@ietf.org>; Wed,  5 Oct 2011 23:14:51 -0700 (PDT)
Received: by ywm3 with SMTP id 3so2800206ywm.31 for <softwires@ietf.org>; Wed, 05 Oct 2011 23:18:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jVEgbbeRpzy1IUO4O0/9WRJLxzX+wGbU9tYognzUbpc=; b=WoPQKAdSjgg4HyeBfLdjZzyPS8ptGdQPhqfDvDYXiwUIFyECRGMuFb22oFhMNdyY7Q xt0lKRiXx9WxspSv3gq67RfmETyODxI3QeSB7HWZMIAATzEmMtCdARgEgYkIRgpgAbjj xzrbbXkZEBUUKfJjxyX/8qIjL1+XYwYJPRIzk=
MIME-Version: 1.0
Received: by 10.68.15.194 with SMTP id z2mr3125215pbc.47.1317881879903; Wed, 05 Oct 2011 23:17:59 -0700 (PDT)
Received: by 10.142.162.1 with HTTP; Wed, 5 Oct 2011 23:17:59 -0700 (PDT)
In-Reply-To: <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com>
Date: Thu, 6 Oct 2011 14:17:59 +0800
Message-ID: <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com>
From: Congxiao Bao <cx.cernet@gmail.com>
To: Maoke <fibrib@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec51f995f4ebe6b04ae9b497e
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 06:14:52 -0000

--bcaec51f995f4ebe6b04ae9b497e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi, Gang, Maoke

2011/10/6 Maoke <fibrib@gmail.com>

> hi Gang,
>
> trying to understand your point, may i follow your message inline? sorry =
if
> my questions are trial/naive.
>
>  2011/10/6 GangChen <phdgang@gmail.com>
>
>> Hello Congxiao,
>>
>> Thanks for the discussion.
>> Please see my reply inline.
>>
>> 2011/10/5, Congxiao Bao <cx.cernet@gmail.com>:
>> >> > There are no necessary to put IPv4 and Port-set ID information in
>> last
>> >> > 64 bits.
>> >>
>> >> The CE Pv6 prefix included in the /64 Subnet prefix isn't self
>> delimited,
>> >> so that the length of the CE index can't be determined in this part o=
f
>> the
>> >> address.
>> >> Having the length of the A or A+P prefix in the IID completes what is
>> >> needed to derive the CE port-set.
>> >
>> > Besides, if a medium or large size ISP can=92t get short enough IPv6
>> prefix
>> > (ex. /24), the first 64 bits can not contain the whole IPv4 32 bits,
>> which
>> > cannot make the double translation successful.
>>
>> I guess that is depending on a specific algorithm. I don't see such
>> limitation in 4v6
>> translation(
>> http://tools.ietf.org/html/draft-murakami-softwire-4v6-translation-00)
>>
>>
> i couldn't understand why we "don't see such limitation in 4v6
> translation". 4via6 translate the private ipv4 address with 4rd mapping r=
ule
> while the public ipv4 address with RFC6052 algorithm, right? can the both
> case work fine if an ISP can only get a fairly long IPv6 prefix, like /40=
 or
> even longer?
>

Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 address an=
d
PSID in the first 64 bits?

>
>
>>
>> > The ISP is not able to achieve per-host traffic control without a
>> standard
>> > defining last 64 bits. If the ISP does, why not use IPv4+psid in suffi=
x
>> > naturally instead of other new bits definition?
>>
>> First off, I'm not sure per-host traffic control is a common case for
>> network operations
>>
>
> i think it is common for, maybe, not any network operators but at least
> some operators. especially for those running middle-to-small ISP services
> (like my company), the capability of per-host traffic control is definite=
ly
> needed. a specific but not rare case is suppressing the pathologically
> greedy download/upload behavior of bot-net boxes.
>

Agree.

>
>  Secondly, it could be possible to use first 64 bits differentiating
>
>  hosts. Please see Max PSID usage in
>
> http://tools.ietf.org/html/draft-despres-softwire-4rd-addmapping-01#page-=
15
>>
>
> sorry but i may not yet understand the mapping algorithm. is the Rule IPv=
6
> prefix definitely short enough to take all Max CE in the first 64 bits?
> again, what if an ISP can only get a fairly long IPv6 prefix?
>
>
 For per-host traffic, the prefix length of ACL should be /128. In this
case, you have to specify the value of the suffix. So different ISPs in the
IPv6 data path can implement IPv6 ACL without additional knowledge.



Congxiao

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

--bcaec51f995f4ebe6b04ae9b497e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi, Gang, Maoke<br><br>
<div class=3D"gmail_quote">2011/10/6 Maoke <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fibrib@gmail.com">fibrib@gmail.com</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div>hi Gang,=A0</div>
<div><br></div>
<div>trying to understand your point, may i follow your message inline? sor=
ry if my questions are trial/naive.=A0</div><br>
<div class=3D"gmail_quote">
<div class=3D"im">2011/10/6 GangChen <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:phdgang@gmail.com" target=3D"_blank">phdgang@gmail.com</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">Hello Congxiao,<br><br>Thanks fo=
r the discussion.<br>
<div>Please see my reply inline.<br><br></div>2011/10/5, Congxiao Bao &lt;<=
a href=3D"mailto:cx.cernet@gmail.com" target=3D"_blank">cx.cernet@gmail.com=
</a>&gt;:<br>
<div>&gt;&gt; &gt; There are no necessary to put IPv4 and Port-set ID infor=
mation in last<br>&gt;&gt; &gt; 64 bits.<br>&gt;&gt;<br>&gt;&gt; The CE Pv6=
 prefix included in the /64 Subnet prefix isn&#39;t self delimited,<br>
&gt;&gt; so that the length of the CE index can&#39;t be determined in this=
 part of the<br>&gt;&gt; address.<br>&gt;&gt; Having the length of the A or=
 A+P prefix in the IID completes what is<br>&gt;&gt; needed to derive the C=
E port-set.<br>
&gt;<br>&gt; Besides, if a medium or large size ISP can=92t get short enoug=
h IPv6 prefix<br>&gt; (ex. /24), the first 64 bits can not contain the whol=
e IPv4 32 bits, which<br>&gt; cannot make the double translation successful=
.<br>
<br></div>I guess that is depending on a specific algorithm. I don&#39;t se=
e such<br>limitation in 4v6<br>translation(<a href=3D"http://tools.ietf.org=
/html/draft-murakami-softwire-4v6-translation-00" target=3D"_blank">http://=
tools.ietf.org/html/draft-murakami-softwire-4v6-translation-00</a>)<br>

<div><br></div></blockquote>
<div><br></div></div>
<div>i couldn&#39;t understand why we &quot;don&#39;t see such limitation i=
n 4v6 translation&quot;. 4via6 translate the private ipv4 address with 4rd =
mapping rule while the public ipv4 address with RFC6052 algorithm, right? c=
an the both case work fine if an ISP can only get a fairly long IPv6 prefix=
, like /40 or even longer?=A0</div>
</div></blockquote>
<div>=A0</div>
<div><span style=3D"FONT-FAMILY: &#39;Times New Roman&#39;; FONT-SIZE: 11pt=
; mso-font-kerning: 1.0pt" lang=3D"EN-US">Yes, if ISP has /32 IPv6 address,=
 then how to embed 32 bits IPv4 address and PSID in the first 64 bits?</spa=
n></div>

<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div class=3D"gmail_quote">
<div class=3D"im">
<div>=A0</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div>=A0<br>&gt; The ISP is not able to achieve per-host traffic control wi=
thout a standard<br>&gt; defining last 64 bits. If the ISP does, why not us=
e IPv4+psid in suffix<br>&gt; naturally instead of other new bits definitio=
n?<br>
<br></div>First off, I&#39;m not sure per-host traffic control is a common =
case for<br>network operations<br></blockquote>
<div><br></div></div>
<div>i think it is common for, maybe, not any network operators but at leas=
t some operators. especially for those running middle-to-small ISP services=
 (like my company), the capability of per-host traffic control is definitel=
y needed. a specific but not rare case is suppressing the pathologically gr=
eedy download/upload behavior of bot-net boxes.=A0</div>
</div></blockquote>
<div>=A0</div>
<div>Agree.</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div class=3D"gmail_quote">
<div class=3D"im">
<div><br></div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">=A0Secondly, it could be possibl=
e to use first 64 bits differentiating=A0</blockquote>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">=A0hosts. Please see Max PSID us=
age in =A0</blockquote>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><a href=3D"http://tools.ietf.org=
/html/draft-despres-softwire-4rd-addmapping-01#page-15" target=3D"_blank">h=
ttp://tools.ietf.org/html/draft-despres-softwire-4rd-addmapping-01#page-15<=
/a><br>
</blockquote>
<div><br></div></div>
<div>sorry but i may not yet understand the mapping algorithm. is the Rule =
IPv6 prefix definitely short enough to take all Max CE in the first 64 bits=
? again, what if an ISP can only get a fairly long IPv6 prefix?=A0</div>

<div>=A0</div></div></blockquote>
<div>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"FONT-SI=
ZE: 11pt" lang=3D"EN-US"><font face=3D"Times New Roman">For per-host traffi=
c, the prefix length of ACL should be /128. In this case, you have to speci=
fy the value of the suffix. So different ISPs in the IPv6 data path can imp=
lement IPv6 ACL without additional knowledge.</font></span></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"FONT-SI=
ZE: 11pt" lang=3D"EN-US"><font face=3D"Times New Roman"></font></span>=A0</=
p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span style=3D"FONT-SI=
ZE: 11pt" lang=3D"EN-US"><font face=3D"Times New Roman">Congxiao</font></sp=
an></p></div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div class=3D"gmail_quote">
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>=A0Many thanks=A0</blockquot=
e>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>Gang=20
<div class=3D"im"><br>
<div>
<div>_______________________________________________<br>Softwires mailing l=
ist<br><a href=3D"mailto:Softwires@ietf.org" target=3D"_blank">Softwires@ie=
tf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/softwires" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</div></div></div></blockquote></div><br></blockquote></div><br>

--bcaec51f995f4ebe6b04ae9b497e--

From despres.remi@laposte.net  Thu Oct  6 01:34:31 2011
Return-Path: <despres.remi@laposte.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 6075C21F8C29 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 01:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.557
X-Spam-Level: 
X-Spam-Status: No, score=-1.557 tagged_above=-999 required=5 tests=[AWL=-0.253, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9eraO7FsHQP for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 01:34:30 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by ietfa.amsl.com (Postfix) with ESMTP id 74CF321F8C21 for <softwires@ietf.org>; Thu,  6 Oct 2011 01:34:29 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2307.sfr.fr (SMTP Server) with ESMTP id 3A85D700008E; Thu,  6 Oct 2011 10:37:38 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2307.sfr.fr (SMTP Server) with ESMTP id A1A9B7000163; Thu,  6 Oct 2011 10:37:33 +0200 (CEST)
X-SFR-UUID: 20111006083733662.A1A9B7000163@msfrf2307.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-18-259042095
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com>
Date: Thu, 6 Oct 2011 10:37:38 +0800
Message-Id: <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com>
To: Qiong <bingxuere@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 08:34:31 -0000

--Apple-Mail-18-259042095
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 5 oct. 2011 =E0 22:45, Qiong a =E9crit :

> Hi, Remi,
>=20
> Thanks for your effort. I think this is a big progress after the =
Interim meeting, and this unified address format is quite clear now.

Thanks.

> Here, I have two comments after a quick review. And I will get back to =
you if I have more comments later.
>=20
> 1. With regard to destination address format, if I understand =
correctly, it only covers hub&spoke model with a default "BR subnet =
prefix". Are you intended to propose another format for mesh one ?

The proposed format does cover mesh domains - ref. =
draft-despres-softwire-4rd-addmapping-01 sections 5. and 9., in which =
"BR IPv6 address" should now be replaced by "BR IPv6 prefix" (a /64).
=20
One or several BR IPv6 prefixes can be explicitly advertised to CEs as =
parts of Domain mapping rules, e.g. with DHCPv6.=20


> Or just cite the "Source address format" as the destination address in =
MESH situation. I think it would be better to declare it separately for =
"H&S" and "MESH". This would be more clearer for readers to understand =
different situations.

When time comes to specify the unified format in a new draft, I agree =
that a clarification of how it applies to different topologies will be =
appropriate.
=20
> 2. Still for the destination address format, I suggest to embed PSID =
as well in the lower 64 bits (as in the following).

<--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
+--------------------------+----+---------------+------------+---+
|     BR subnet prefix     | V  |  IPv4 address | PSID |  0  | L |
+--------------------------+----+---------------+------------+---+=20

The reported informal agreement we had in Beijing didn't explicitly =
cover destination addresses, and I just reported what we said, but this =
is AFAIK the implicit direction to go to.
Yet, there is a point to be taken into account:
- It concerns use cases where IPv6 prefixes are assigned without any =
relationship with IPv4 prefixes and where different sharing ratios are =
implicitly expressed by different IPv6 prefix lengths (they aren't the =
only use cases, but are the only ones where a flat IPv6 routing plan can =
be used with differentiated sharing ratios).
- For this, a BR or CE that transmits to a CE destination doesn't know =
the exact PSID length of this CE. It only knows the maximum possible =
length of this PSID, but this is enough for the right CE to be reached =
(ref draft-despres-softwire-4rd-addmapping-01 sec 7.)

Thus, for more generality, the format for a Destination CE would rather =
be:

<--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
+--------------------------+----+---------------+--------+---+---+
|     BR subnet prefix     | V  |  IPv4 address |Max PSID| 0 | L |
+--------------------------+----+---------------+--------+---+---+=20

If the PSID length is known, then the Max PSID is the exact PSID, but =
this isn't the only case.



> This would make it easier for in-the-middle systems(e.g. BNG) to do =
prefix mapping without packet decapsulation.

Exactly, that's the point of using IIDs to insert useful information.

> And this is quite similar to the source address format. What do you =
think of it?

Detailed answer above.

Kind regards,
RD






> Best wishes
>=20
> Qiong
>  =20
>=20
> On Tue, Oct 4, 2011 at 12:22 PM, R=E9mi Despr=E9s =
<despres.remi@laposte.net> wrote:
> Hi all,
>=20
> 1.
> Here is a unified Address Mapping, for both encapsulation and =
double-translation approaches, that is PROPOSED for IPv4 residual =
deployment across IPv6-only routing domains.
>=20
> It results from an informal meeting among participants having =
different preferences between double-translation and encapsulation =
solutions (Xing Li, Congxiao Bao, Wojciech Dec, myself, at the end of =
the Beijing meeting).
>=20
> The idea is to have a common format that is good for both types of =
solutions.
> In particular:
> - It enriches Double translation by introducing a deterministic way to =
distinguish a translated IPv4 packet from a native IPv6 packet.
> - It enriches Encapsulation by expressing, in clear format within an =
IPv6 address, an IPv4 address, an IPv4 prefix, or an IPv4 address + =
port-set ID.
>=20
>=20
> 2.
> (a)
> The IPv6 Source address of an IPv4 packet from a CE is:
>=20
> a1- If the CE has an exclusive or shared IPv4 address:
>=20
> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
> +-------------+--------+---+---+----------------+------+-----+---+
> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
> +-------------+--------+---+---+----------------+------+-----+---+
>=20
> a2- If the CE has an IPv4 prefix:
>=20
> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
> +-------------+--------+---+---+-------------+---------------+---+
> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
> +-------------+--------+---+---+-------------+---------------+---+
>=20
> (b)
> V is the mark that characterizes IPv6 packets that are in reality IPv4 =
packets.
> Its value differs from any permitted value of this octet in IPv6 IIDs  =
(ref RFC 4291).
>=20
> It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.
>=20
> An unambiguous mark is fortunately possible because currently =
permitted IIDs have in their first octet either bit6 =3D 0 (the "u" =
bit"), or bit6 =3D 1 and bit7=3D 0 (the "g" bit).
> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction is therefore deterministic.
>=20
> The proposed V is =3D 00000011.
> (With other values of this octet, other IID formats can be defined in =
case some would be useful in the future.)
>=20
> Note that, if and when a consensus is reached in Softwire, an =
extension of RFC 4291 will have to be submitted to 6MAN.
>=20
> (c)
> A Destination address from a CE to the outside IPv4 Internet is:
> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> +--------------------------+----+---------------+------------+---+
> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
> +--------------------------+----+---------------+------------+---+
>=20
> Note that if double-translation CEs are notified to use U instead of =
V, the last octet becomes 0 per RFC  6052.
>=20
>=20
> 3.
> All comments are most welcome.
>=20
> Kind regards to all,
> RD
>=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>=20


--Apple-Mail-18-259042095
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 5 oct. 2011 =E0 22:45, Qiong a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">Hi, =
Remi,<div><br></div><div>Thanks for your effort. I think this is a big =
progress after the Interim meeting, and this unified address format is =
quite clear now. =
</div></blockquote><div><br></div>Thanks.</div><div><br><blockquote =
type=3D"cite"><div>Here, I have two comments after a quick review. And I =
will get back to you if I have more comments later.</div>

<div><br></div><div>1. With regard to destination address format, if I =
understand correctly, it only covers hub&amp;spoke model with a default =
"<span class=3D"Apple-style-span" style=3D"font-family: arial, =
sans-serif; font-size: 13px; background-color: rgb(255, 255, 255); ">BR =
subnet prefix</span>". Are you intended to propose another format for =
mesh one ?</div></blockquote><div><br></div><div>The proposed format =
does cover mesh domains&nbsp;- ref. =
draft-despres-softwire-4rd-addmapping-01 sections 5. and 9., in which =
"BR IPv6 address" should now be replaced by "BR IPv6 prefix" (a =
/64).</div><div>&nbsp;</div><div>One or several BR IPv6 prefixes can be =
explicitly advertised to CEs as parts of Domain mapping rules, e.g. with =
DHCPv6.&nbsp;</div><div><br></div><br><blockquote type=3D"cite"><div> Or =
just cite the "Source address format" as the destination address in MESH =
situation. I think it would be better =
to&nbsp;declare&nbsp;it&nbsp;separately&nbsp;for "H&amp;S" and "MESH". =
This would be more clearer for readers to understand different =
situations.</div></blockquote><div><br></div>When time comes to specify =
the unified format in a new draft, I agree that a clarification of how =
it applies to different topologies will be =
appropriate.</div><div>&nbsp;<br><blockquote type=3D"cite">

<div>2. Still for the&nbsp;destination address format, I suggest to =
embed PSID as well in the lower 64 bits (as in the =
following).</div></blockquote><br><div><div>&lt;--------- 64 =
------------&gt;&lt; 8 &gt;&lt;---- &nbsp; 32 ----&gt;&lt;--- 16 =
----&gt;&lt;8 =
&gt;</div><div>+--------------------------+----+---------------+----------=
--+---+</div><div>| &nbsp; &nbsp; BR subnet prefix &nbsp; &nbsp; | V =
&nbsp;| &nbsp;IPv4 address | PSID | &nbsp;0 &nbsp;| L =
|</div><div>+--------------------------+----+---------------+------------+=
---+&nbsp;</div></div><div><br></div><div>The reported informal =
agreement we had in Beijing didn't explicitly cover destination =
addresses, and I just reported what we said, but this is AFAIK the =
implicit direction to go to.</div><div>Yet, there is a point to be taken =
into account:</div><div>- It concerns use cases where IPv6 prefixes are =
assigned without any relationship with IPv4 prefixes and where different =
sharing ratios are implicitly expressed by different IPv6 prefix lengths =
(they aren't the only use cases, but are the only ones where a flat IPv6 =
routing plan can be used with differentiated sharing =
ratios).</div><div>- For this, a BR or CE that transmits to a CE =
destination doesn't know the exact PSID length of this CE. It only knows =
the maximum possible length of this PSID, but this is enough for the =
right CE to be reached (ref draft-despres-softwire-4rd-addmapping-01 sec =
7.)</div><div><br></div><div>Thus, for more generality, the format for a =
Destination CE would rather =
be:</div><div><br></div><div><div><div>&lt;--------- 64 =
------------&gt;&lt; 8 &gt;&lt;---- &nbsp; 32 ----&gt;&lt;--- 16 =
----&gt;&lt;8 =
&gt;</div><div>+--------------------------+----+---------------+--------+-=
--+---+</div><div>| &nbsp; &nbsp; BR subnet prefix &nbsp; &nbsp; | V =
&nbsp;| &nbsp;IPv4 address |Max PSID| 0 | L =
|</div><div>+--------------------------+----+---------------+--------+---+=
---+&nbsp;</div></div></div><div><br></div><div>If the PSID length is =
known, then the Max PSID is the exact PSID, but this isn't the only =
case.</div><div><br></div><div><br></div><div><br></div><blockquote =
type=3D"cite"><div>This would make it easier&nbsp;for&nbsp;in-the-middle =
systems(e.g. BNG)&nbsp;to do prefix mapping without packet =
decapsulation. </div></blockquote><div><br></div><div>Exactly, that's =
the point of using IIDs to insert useful =
information.</div><br><blockquote type=3D"cite"><div>And this is quite =
similar to the source address format. What do you think of =
it?</div></blockquote><div><br></div>Detailed answer =
above.</div><div><br></div><div>Kind =
regards,</div><div>RD<br><div><br></div><div><br></div><div><br></div><div=
><br></div><div><br></div><br><blockquote type=3D"cite"><div>Best =
wishes</div><div><br></div><div>Qiong</div><div>&nbsp;&nbsp;</div><div><br=
><div class=3D"gmail_quote">On Tue, Oct 4, 2011 at 12:22 PM, R=E9mi =
Despr=E9s <span dir=3D"ltr">&lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;<=
/span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi all,<br>
<br>
1.<br>
Here is a unified Address Mapping, for both encapsulation and =
double-translation approaches, that is PROPOSED for IPv4 residual =
deployment across IPv6-only routing domains.<br>
<br>
It results from an informal meeting among participants having different =
preferences between double-translation and encapsulation solutions (Xing =
Li, Congxiao Bao, Wojciech Dec, myself, at the end of the Beijing =
meeting).<br>


<br>
The idea is to have a common format that is good for both types of =
solutions.<br>
In particular:<br>
- It enriches Double translation by introducing a deterministic way to =
distinguish a translated IPv4 packet from a native IPv6 packet.<br>
- It enriches Encapsulation by expressing, in clear format within an =
IPv6 address, an IPv4 address, an IPv4 prefix, or an IPv4 address + =
port-set ID.<br>
<br>
<br>
2.<br>
(a)<br>
The IPv6 Source address of an IPv4 packet from a CE is:<br>
<br>
a1- If the CE has an exclusive or shared IPv4 address:<br>
<br>
&lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;------ L &gt;=3D 32 =
-------&gt;&lt;48-L&gt;&lt;8 &gt;<br>
+-------------+--------+---+---+----------------+------+-----+---+<br>
| IPv6 prefix |CE index| 0 | V | &nbsp;IPv4 address &nbsp;| PSID | =
&nbsp;0 &nbsp;| L |<br>
+-------------+--------+---+---+----------------+------+-----+---+<br>
<br>
a2- If the CE has an IPv4 prefix:<br>
<br>
&lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;-- L &lt; 32 =
--&gt;&lt;--- 48-L -----&gt;&lt;8 &gt;<br>
+-------------+--------+---+---+-------------+---------------+---+<br>
| IPv6 prefix |CE index| 0 | V | IPv4 prefix | &nbsp; &nbsp; &nbsp; =
&nbsp; 0 &nbsp; &nbsp; | L |<br>
+-------------+--------+---+---+-------------+---------------+---+<br>
<br>
(b)<br>
V is the mark that characterizes IPv6 packets that are in reality IPv4 =
packets.<br>
Its value differs from any permitted value of this octet in IPv6 IIDs =
&nbsp;(ref RFC 4291).<br>
<br>
It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.<br>
<br>
An unambiguous mark is fortunately possible because currently permitted =
IIDs have in their first octet either bit6 =3D 0 (the "u" bit"), or bit6 =
=3D 1 and bit7=3D 0 (the "g" bit).<br>
With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction is therefore deterministic.<br>
<br>
The proposed V is =3D 00000011.<br>
(With other values of this octet, other IID formats can be defined in =
case some would be useful in the future.)<br>
<br>
Note that, if and when a consensus is reached in Softwire, an extension =
of RFC 4291 will have to be submitted to 6MAN.<br>
<br>
(c)<br>
A Destination address from a CE to the outside IPv4 Internet is:<br>
&lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- &nbsp; 32 =
----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;<br>
+--------------------------+----+---------------+------------+---+<br>
| &nbsp; &nbsp; BR subnet prefix &nbsp; &nbsp; | V &nbsp;| &nbsp;IPv4 =
address | &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp; |32 |<br>
+--------------------------+----+---------------+------------+---+<br>
<br>
Note that if double-translation CEs are notified to use U instead of V, =
the last octet becomes 0 per RFC &nbsp;6052.<br>
<br>
<br>
3.<br>
All comments are most welcome.<br>
<br>
Kind regards to all,<br>
RD<br>
<br>
<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"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</blockquote></div><br></div>
</blockquote></div><br></body></html>=

--Apple-Mail-18-259042095--

From despres.remi@laposte.net  Thu Oct  6 01:48:27 2011
Return-Path: <despres.remi@laposte.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 BD6D221F8CC5 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 01:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uYFVyjXk3lZG for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 01:48:27 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.118]) by ietfa.amsl.com (Postfix) with ESMTP id 11BE021F8C84 for <softwires@ietf.org>; Thu,  6 Oct 2011 01:48:26 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2503.sfr.fr (SMTP Server) with ESMTP id 53FEE7000041; Thu,  6 Oct 2011 10:51:36 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2503.sfr.fr (SMTP Server) with ESMTP id 179E770000BD; Thu,  6 Oct 2011 10:51:32 +0200 (CEST)
X-SFR-UUID: 20111006085132968.179E770000BD@msfrf2503.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAM+vMEQ4=xxgBgoqDAcd=t_Yx=j+wJm-rP-haJwdSxRSOv5sVQ@mail.gmail.com>
Date: Thu, 6 Oct 2011 10:51:36 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <02D4DC4B-EB93-42C6-AE9F-135B0C598F8E@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CAM+vMEQ4=xxgBgoqDAcd=t_Yx=j+wJm-rP-haJwdSxRSOv5sVQ@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 08:48:27 -0000

Le 6 oct. 2011 =E0 06:01, GangChen a =E9crit :

> Hello Remi,
>=20
> Thanks for the answers.
> Please see my reply inline.
>=20
> 2011/10/5, R=E9mi Despr=E9s <despres.remi@laposte.net>:
>>> There are no necessary to put IPv4 and Port-set ID information in =
last
>>> 64 bits.
>>=20
>> The CE Pv6 prefix included in the /64 Subnet prefix isn't self =
delimited, so
>> that the length of the CE index can't be determined in this part of =
the
>> address.
>> Having the length of the A or A+P prefix in the IID completes what is =
needed
>> to derive the CE port-set.
>=20
> I understand such encoded information helps deriving a shared IPv4
> address. However, I guess it's not necessary to dig up such
> information if we only take traffic contronl on IPv6 data plane (as I
> said below)

I agree that it is "not necessary" to exploit this field to filter IPv4 =
traffic.

Yet it MAY be used to facilitate configuration of traffic control =
parameters (IPv4 addresses are expressed in clear form instead of having =
to be derived with the help of mapping rules).
Besides, maintenance is facilitated if IPv4 addresses can be directly =
read in IPv6 addresses.

 =20
>>> It may help encapsulation in same cases(e.g. IPv4 based traffic
>>> classification,IPv4 ACL, etc).
>>> However, the translation case is more preferable doing pure IPv6 =
based
>>> control for the sake of simpler operation reasons (e.g. IPv6 ACL).
>>> It's desirable identifying a customer depending on first 64 bits.
>>=20
>> A point is that, although some realistic deployments may ignore what =
is made
>> available in IIDs (at least at the beginning), some others would take
>> advantage of it.
>=20
> Yes. I agree with your point here. As you said such IID design may not
> be taken effect on some realistic deployments, I would like to suggest
> the IID MAY not appeared in double translation cases.

The point is that:
- Copying the IPv4 address at a fixed place in IIDs has a negligible =
cost.
- Having a SINGLE standard format is cost saving. (I particular, if you =
don't plan to exploit it at first, you may be glad to have it in the =
future, at least for maintenance if for nothing else.)

Regards,
RD







>=20
>=20
> Many thanks
>=20
> Gang
>=20

From dxhbupt@gmail.com  Thu Oct  6 01:55:50 2011
Return-Path: <dxhbupt@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 E18F821F8CD2 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 01:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.333
X-Spam-Level: 
X-Spam-Status: No, score=-3.333 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fiv90g7caY53 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 01:55:50 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 90DEF21F8CC5 for <softwires@ietf.org>; Thu,  6 Oct 2011 01:55:49 -0700 (PDT)
Received: by wwf22 with SMTP id 22so2717747wwf.13 for <softwires@ietf.org>; Thu, 06 Oct 2011 01:58:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=uxB6dVEjEv8br6fgeFMkSvem7VYAatRZcV+cesGg+2A=; b=lutiAMrkKVB2L81vSLvQo9toEqTt0UJYNW3XR6Hc3mBjmldhfBISj3qv7b2D+ZkS7J aMMr/VG02qgpmInE5SrGHX8ZO5RqbuGsVKvIWqD2q2vo8YXFM4YCcMjdy5q1cyr1sWkJ LsSLsNFlZZgFgCr+aewUNN6rpY5BiE1WdN/LM=
MIME-Version: 1.0
Received: by 10.216.132.129 with SMTP id o1mr892147wei.3.1317891539186; Thu, 06 Oct 2011 01:58:59 -0700 (PDT)
Received: by 10.180.104.202 with HTTP; Thu, 6 Oct 2011 01:58:59 -0700 (PDT)
In-Reply-To: <B14D2395-3C09-462D-8132-6497180D16B6@laposte.net>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com> <067E6CE33034954AAC05C9EC85E2577C0613BAC1@XMB-RCD-111.cisco.com> <B14D2395-3C09-462D-8132-6497180D16B6@laposte.net>
Date: Thu, 6 Oct 2011 16:58:59 +0800
Message-ID: <CANb4Oc=m3eBjOpQTKXMFOf-FdnxhLQUjzJxQ7cFzHB5JOXhZUA@mail.gmail.com>
From: xiaohong deng <dxhbupt@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: softwires@ietf.org, "Wojciech Dec \(wdec\)" <wdec@cisco.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 06 Oct 2011 08:55:51 -0000

On Wed, Oct 5, 2011 at 9:56 AM, R=E9mi Despr=E9s <despres.remi@laposte.net>=
 wrote:
>
> Le 5 oct. 2011 =E0 03:28, Rajiv Asati (rajiva) a =E9crit :
>
>>> ability instead of the more general five-tuple based IPv4
>>> classification ability should be reserved, when deliver IPv4 over
>>> IPv6?
>>
>> How would one get 5-tuple based classification when delivering IPv4 "ove=
r" IPv6, if the v4 packet is not translated into v6?
>>
>> The fact of the matter is that "5-tuple" could be a luxury that may not =
always be available.
>
> Questions for clarification about 5-tuple-based actions of intermediate n=
odes that are currently used:
> - Do we know whether they generally work with IPv6 packets having extensi=
on headers?
> - If yes, with which ones?
> - In particular, are fragment headers always supported (with ports availa=
ble only in first fragments)?

Curious and look forward to clarifications to above too.

Thanks,
Xiaohong


>
> Thanks,
> RD
>
>
>>
>> Cheers,
>> Rajiv
>>
>>
>>> -----Original Message-----
>>> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On=
 Behalf
>>> Of xiaohong deng
>>> Sent: Tuesday, October 04, 2011 3:26 AM
>>> To: Wojciech Dec (wdec); despres.remi@laposte.net; otroan@employees.org=
;
>>> bingxuere@gmail.com; softwires@ietf.org
>>> Subject: Re: [Softwires] 4rd Address Mapping - version-01
>>>
>>> Hi Remi, Ole, Woj, and all,
>>>
>>> I understand the argument of IID bits is resulted from a last minute
>>> agreement between 4rd and divi-pd people that having full IPv4 address
>>> embedded in the address format helps source based classification, but
>>> before we argue that, shall we first make this agreement also be
>>> accepted by community wide? As far as current time-being concerned, I
>>> don't see a consensus has been reached on this agreement from
>>> community wide.
>>>
>>> It IMHO would be helpful if anybody would clarify some details to 1)
>>> first prove source based classification is either a valid or a
>>> non-valid requirement for address mapping; For this regard, I would
>>> begin with that why do we think the source based IPv4 classification
>>> ability instead of the more general five-tuple based IPv4
>>> classification ability should be reserved, when deliver IPv4 over
>>> IPv6?
>>>
>>>
>>> and 2) then show us how much other efforts are required to achieve so
>>> besides address format definition itself, in other words, if it's a
>>> valid requirement, let's first have feasibility of this requirement
>>> analyzed from both deployment and operational perspectives:
>>>
>>> 1. For double translation, how does a traditional router perform the
>>> source based IPv4 packet classification on IPv6 (translated from IPv4)
>>> packets? Or does it suggest that using IPv6 classification filters to
>>> filter IPv4 packets? If so, should we also note that this suggests
>>> IPv4 operation and managed are tightly coupled with IPv6 operation and
>>> management? which in turn implies complexity in operational, or put in
>>> other words, OPEX increasing, the last thing among others that
>>> operators would like to see.
>>>
>>> 2. For encapsulation, even if embedding source IPv4 addresses in the
>>> lower bits of the address formats, where does the router find the
>>> source port without de-capsulation? Are you suggesting also encode 16
>>> bits port in the lower part of address? In either case, it leads to
>>> the concerns of increased OPEX to operators stated above.
>>>
>>> Thoughts?
>>>
>>> Cheers,
>>> Xiaohong
>>>
>>>> Hi Qiong,
>>>>
>>>> Some fields of a unified address format for double translation and
>>>> encapsulation might be unnecessary for hub and spoke, but using the
>>>> same format should be advantageous for maintenance and training if for
>>>> nothing else (assuming that any added complexity is negligible
>>>> enough).
>>>>
>>>> Believing that a completely unified format is possible, I mentioned it=
 to
>>> Alain.
>>>> Also, I volunteered to be editor-coordinator for this to happen, but
>>>> decision of who does what is his.
>>>>
>>>> Regards,
>>>> RD
>>>>
>>>>
>>>> Le 4 oct. 2011 =E0 00:13, Qiong a =E9crit :
>>>>
>>>>> Hi Remi and Wojciech,
>>>>>
>>>>> Thanks for your clarification. I fully agree with you that embedding =
the
>>> full IPv4 address in the last 64 bits would be quite helpful for some k=
ind of
>>> source address classification and I also suggest that this can be taken=
 in the
>>> same way for encapsulation-based approach. It would be easier for syste=
ms in-
>>> the-middle to identify the IPv4 address without packet decapsulation.
>>>>>
>>>>> I guess the thing that Ole has mentioned to "look at 24 bits in the m=
iddle
>>> of IPv6 address" is for CE to determine whether a downstream IPv6 packe=
t
>>> should be taken for translation or native forwarding. Here, for a dual-=
stack
>>> host, there would be no difference in the first /64 bits for a native I=
Pv6
>>> packet and a translated packet. What's why the CE should further lookin=
g into
>>> the last 64 bits to determine the translation process or native forward=
ing.
>>> Maybe Ole can clarify for this part again.
>>>>>
>>>>> However, the situation would still be different in "Hub & Spoke" and =
"Mesh"
>>> mode. For Hub & Spoke case, since BR will have a default prefix/address=
, it
>>> would be easily to identify the translated traffic from native IPv6 tra=
ffic by
>>> just doing source address routing lookup for a downstream packet. So, t=
he
>>> corresponding mechanics would be different.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Best wishes
>>>>>
>>>>> Qiong
>>>>>
>>>>> 2011/10/3 Wojciech Dec <wdec at cisco.com>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =A0 =A0On 02/10/2011 02:58, "Qiong" <bingxuere at gmail.com> wrote:
>>>>>
>>>>> =A0 =A0 =A0 =A0Hi Ole and Remi,
>>>>>
>>>>>> This is my answer to your first (double) question.
>>>>>> If it is not enough, as suggested below, please explain what
>>> you don't understand.
>>>>>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0I specifically do not want a solution that cha=
nges forwarding
>>> behaviour for _all_ IPv6 packets.
>>>>> =A0 =A0 =A0 =A0 =A0 =A0e.g. looking at 24 bits in the middle of an IP=
v6 address is
>>> such a change.
>>>>>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0Woj> What are you referring to? Routing "just =
works" as normal
>>> and is non disaggregated because of the CE-index in the prefix. Classif=
ication
>>> can/is done on a subset of the v6 address, and that is perfectly legit.
>>>>>
>>>>>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0I don't understand what requirements you are b=
asing this
>>> 'solution' on.
>>>>> =A0 =A0 =A0 =A0 =A0 =A0if the 4rd / dIVI CE takes (a well known or pr=
ovisioned) /64
>>> prefix out of the delegated prefix. then why do you need any of that?
>>>>>
>>>>>
>>>>> =A0 =A0 =A0 =A0Qiong : I agree that routing lookup for a provisioned =
/64 prefix
>>> would be better that extracting certain bits for each IPv6 address in C=
E. This
>>> would bring less change to existing routing model.
>>>>>
>>>>> =A0 =A0 =A0 =A0Woj> There is no change to the existing destination ba=
sed routing
>>> model. Each CE is uniquely addressed by the CE bits in the top /64 - ie=
 the CE
>>> index is as proposed by all the 4rd and divi-pd drafts. The full v4 sou=
rce
>>> address of each CE is however also embedded in the interface-id, as per
>>> RFC6052. There appears to be no cost for this operation, and has the up=
side of
>>> the full v4 info visible in the header and allowing source based
>>> classification (should one want to do that).
>>>>>
>>>>> =A0 =A0 =A0 =A0Regards,
>>>>> =A0 =A0 =A0 =A0Woj.
>>>>>
>>>>> =A0 =A0 =A0 =A0Best wishes
>>>>>
>>>>> =A0 =A0 =A0 =A0Qiong
>>>>>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0______________________________________________=
_
>>>>> =A0 =A0 =A0 =A0 =A0 =A0Softwires mailing list
>>>>> =A0 =A0 =A0 =A0 =A0 =A0Softwires at ietf.org
>>>>> =A0 =A0 =A0 =A0 =A0 =A0https://www.ietf.org/mailman/listinfo/softwire=
s
>>>>>
>>>>>
>>>>>
>>>>
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>
>

From dxhbupt@gmail.com  Thu Oct  6 02:08:32 2011
Return-Path: <dxhbupt@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 8F22C21F8BE8 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 02:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.327
X-Spam-Level: 
X-Spam-Status: No, score=-2.327 tagged_above=-999 required=5 tests=[AWL=-1.028, BAYES_00=-2.599, MANGLED_FROM=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qBdlGRnjDgaL for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 02:08:32 -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 E52C621F8BD8 for <softwires@ietf.org>; Thu,  6 Oct 2011 02:08:31 -0700 (PDT)
Received: by wyh21 with SMTP id 21so2988455wyh.31 for <softwires@ietf.org>; Thu, 06 Oct 2011 02:11:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2Eb0bsx2RUySbgrMERZTAjXaeZM8Dytb7ArG1yW+N/0=; b=HWuHhA46kAy4xvYcs3rf52AerrGExmfueO7l7YT3VpTPPunNkWDFFMcQZb/fuRTc0E DqYlzlSgUlNrARQB6k8ojSMd6lbsdWLIy0I6duHLwaSFI81CuzGDafqTosctoz9lmckX bpKkYrLbJhLtkh0BM/AHFpf5eCHyD1Kpri57c=
MIME-Version: 1.0
Received: by 10.227.154.66 with SMTP id n2mr725050wbw.3.1317892301402; Thu, 06 Oct 2011 02:11:41 -0700 (PDT)
Received: by 10.180.104.202 with HTTP; Thu, 6 Oct 2011 02:11:41 -0700 (PDT)
In-Reply-To: <CABv173VUCzOoKzQtNhKMSs1a2xyFAfHpGvhUX-iS2RcEt3Y43w@mail.gmail.com>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com> <67E4A8C5-B119-45DB-8367-BDF55A380DC4@laposte.net> <CABv173VUCzOoKzQtNhKMSs1a2xyFAfHpGvhUX-iS2RcEt3Y43w@mail.gmail.com>
Date: Thu, 6 Oct 2011 17:11:41 +0800
Message-ID: <CANb4Ock-4nFsw0JmoCff-4X1dz1qAdEjYzc7eGW4PPz7NNPu+g@mail.gmail.com>
From: xiaohong deng <dxhbupt@gmail.com>
To: Congxiao Bao <cx.cernet@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>, Congxiao Bao <congxiao@cernet.edu.cn>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 06 Oct 2011 09:08:32 -0000

On Tue, Oct 4, 2011 at 11:37 PM, Congxiao Bao <cx.cernet@gmail.com> wrote:
> Hi Remi,
>
> Ok, we will draft a document on using existing tools for O&M in dIVI/dIVI=
-PD
> very soon.

Thanks for sharing and look forward to it.

Cheers,
Xiaohong

>
> Best,
>
> Congxiao
>
> 2011/10/4 R=E9mi Despr=E9s <despres.remi@laposte.net>
>>
>> Hi Xing, Congxiao,
>>
>> Le 4 oct. 2011 =E0 15:26, xiaohong deng a =E9crit :
>> ...
>> > It IMHO would be helpful if anybody would clarify some details to 1)
>> > first prove source based classification is either a valid or a
>> > non-valid requirement for address mapping; For this regard, I would
>> > begin with that why do we think the source based IPv4 classification
>> > ability instead of the more general five-tuple based IPv4
>> > classification ability should be reserved, when deliver IPv4 over
>> > IPv6?
>>
>> What about starting from your conclusion slide in Beijing?
>>
>> It says:
>>
>> "dIVI/dIVI-PD can use existing tools for O&M
>> =96 Null route
>> =96 ACL
>> =96 eACL
>> =96 PBR
>> =96 QoS
>> =96 Caching"
>>
>> Open questions include:
>> - Which addresses are used for these O&M functions? (source? destination=
?,
>> CE to CE?, CE to BR?, BR to CE?)
>> - Are ports within IPv6 payloads used, or just addresses?
>>
>> Thank you if you can share your views on this.
>>
>> Regards,
>> RD
>>
>>
>>
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>
>

From ichiroumakino@gmail.com  Thu Oct  6 03:44:45 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 2095821F8B91 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 03:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.386
X-Spam-Level: 
X-Spam-Status: No, score=-3.386 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NtiK-idlmeud for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 03:44:44 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1474D21F8B73 for <softwires@ietf.org>; Thu,  6 Oct 2011 03:44:43 -0700 (PDT)
Received: by wwf22 with SMTP id 22so2826524wwf.13 for <softwires@ietf.org>; Thu, 06 Oct 2011 03:47:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=xU/HRY9NYpBUNKFkKHUN9XWLoM5FXfWYcm1MVLFa0tc=; b=WUZW1j+2H4I4uvHkK75OnGnwXE7961EkP059K+xpq/0tKFgjguKh4Tcq25DpE0ISJG ljlksivpL1xMvL5yugZvxuve2iOQxbXrsjhBLZtg7+4CXKh2HM6BESUCp9Mvt5SuYbsx iCURMinrZaWS2c4ZCE+4DDQotXSptViE3/tnI=
Received: by 10.216.229.84 with SMTP id g62mr805642weq.23.1317898073836; Thu, 06 Oct 2011 03:47:53 -0700 (PDT)
Received: from dhcp-10-61-97-42.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id n21sm9553307wbp.2.2011.10.06.03.47.51 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 06 Oct 2011 03:47:52 -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: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net>
Date: Thu, 6 Oct 2011 06:47:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 10:44:45 -0000

Remi,

[...]

> 2.
> (a)
> The IPv6 Source address of an IPv4 packet from a CE is:
>=20
> a1- If the CE has an exclusive or shared IPv4 address:
>=20
> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
> +-------------+--------+---+---+----------------+------+-----+---+
> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
> +-------------+--------+---+---+----------------+------+-----+---+

putting the IPv4 address / port information at the end of the interface =
identifier will allow for > /64 support.
what's the L?

you suggest that the first subnet of an allocation should be used for =
this purpose.
the first subnet is convenient to use for e.g. manual addressing (since =
it allows the :: short hand).
I do wonder if this has to be provisioned. e.g. some deployments may use =
the first subnet for the link between
CE and PE. (i.e. a /56 - 1 using the PD exclude option is used).

> a2- If the CE has an IPv4 prefix:
>=20
> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
> +-------------+--------+---+---+-------------+---------------+---+
> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
> +-------------+--------+---+---+-------------+---------------+---+
>=20
> (b)
> V is the mark that characterizes IPv6 packets that are in reality IPv4 =
packets.
> Its value differs from any permitted value of this octet in IPv6 IIDs  =
(ref RFC 4291).
>=20
> It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.
>=20
> An unambiguous mark is fortunately possible because currently =
permitted IIDs have in their first octet either bit6 =3D 0 (the "u" =
bit"), or bit6 =3D 1 and bit7=3D 0 (the "g" bit).
> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction is therefore deterministic.
>=20
> The proposed V is =3D 00000011.=20
> (With other values of this octet, other IID formats can be defined in =
case some would be useful in the future.)
>=20
> Note that, if and when a consensus is reached in Softwire, an =
extension of RFC 4291 will have to be submitted to 6MAN.=20

or rather IEEE?
I am not convinced that "V" is needed.
you could even use the IANA OUI if pretty printing was required.

>=20
> (c)                                  =20
> A Destination address from a CE to the outside IPv4 Internet is:
> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> +--------------------------+----+---------------+------------+---+
> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
> +--------------------------+----+---------------+------------+---+

this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
if we also allow for a BR subnet prefix of /128 I'm OK with this (I =
think).

>=20
> Note that if double-translation CEs are notified to use U instead of =
V, the last octet becomes 0 per RFC  6052.

how would a CE know if it was single or double translating?

e.g we could do:

<--------- 64 ------------><--- 24 ------><----- 32 -------><--8 >
+-------------+--------+---+--------------------+------+-----+---+
| IPv6 prefix |CE index| S | 00-00-5E    |  IPv4 address  | PSID |
+-------------+--------+---+---+----------------+------+-----+---+

we also need to handle the case where IPv6 prefix + CE index > 64. I =
suggest we then just put as much as the interface identifier that will =
fit.

cheers,
Ole


From ichiroumakino@gmail.com  Thu Oct  6 03:50:22 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 0E60D21F8C33 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 03:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.533
X-Spam-Level: 
X-Spam-Status: No, score=-3.533 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9DqozN0tsf7 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 03:50:21 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id D390821F8C1F for <softwires@ietf.org>; Thu,  6 Oct 2011 03:50:20 -0700 (PDT)
Received: by wwn22 with SMTP id 22so7652818wwn.1 for <softwires@ietf.org>; Thu, 06 Oct 2011 03:53:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=cxB8Z/xgFUMu1ZWL4Xkw9JQv4LZquQ48h1K91sMvJyU=; b=MFJX6OGRJZVu48P+UPUn04xa13tWPGS9Xawy6hVKqP8cWtiYH0DtO0wKt1OGqQ49gO a5Xw8069/L9PvOROCh8DfqNea95G7wVsJkI9RPW5iXlc2wNrA+t7XhZl7I4J7I4v4770 rTAeia3TUMjze47msChaj+C7KspQ7bPcYF/1k=
Received: by 10.216.134.168 with SMTP id s40mr951977wei.50.1317898410645; Thu, 06 Oct 2011 03:53:30 -0700 (PDT)
Received: from dhcp-10-61-97-42.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id fj1sm5604029wbb.13.2011.10.06.03.53.28 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 06 Oct 2011 03:53:29 -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: <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com>
Date: Thu, 6 Oct 2011 06:53:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C29CE19-E03A-4AC5-959A-7931FE5B9B04@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com>
To: Congxiao Bao <cx.cernet@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 10:50:22 -0000

> i couldn't understand why we "don't see such limitation in 4v6 =
translation". 4via6 translate the private ipv4 address with 4rd mapping =
rule while the public ipv4 address with RFC6052 algorithm, right? can =
the both case work fine if an ISP can only get a fairly long IPv6 =
prefix, like /40 or even longer?=20
> =20
> Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 =
address and PSID in the first 64 bits?

only part of the IPv4 address would be embedded into the first 64 bits =
(not that I think that boundary should be "hard").
e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. then =
only "1.2.3" would be embedded in the address.
just like what's done for 6rd.

cheers,
Ole=

From cx.cernet@gmail.com  Thu Oct  6 06:54:39 2011
Return-Path: <cx.cernet@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 0DB1621F8B44 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 06:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.053
X-Spam-Level: 
X-Spam-Status: No, score=-3.053 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cso6YpyBNrnj for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 06:54:38 -0700 (PDT)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 89EBF21F8AF7 for <softwires@ietf.org>; Thu,  6 Oct 2011 06:54:38 -0700 (PDT)
Received: by pzk37 with SMTP id 37so7074452pzk.9 for <softwires@ietf.org>; Thu, 06 Oct 2011 06:57:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r+Xs4d0zKusXHBZy9t2rpDan/cdiXKgFC2ENikSlRBY=; b=uSu4mYEadlZmiVebGF+BW/NZ7J05p7Q6khEirvxFMcjZfcFEtCPSmznL6iWSWYPsBp z9OSP0Xc0BJhv2WnCRfbILAUIifmAKwurWrsbJYU+WcsuvQ+QSLgLzUCgbx5c1HQh82N a8/05sHb07WsEBsWck2IlZ8bWvgY7XDjDZt5c=
MIME-Version: 1.0
Received: by 10.68.17.193 with SMTP id q1mr5837204pbd.98.1317909469310; Thu, 06 Oct 2011 06:57:49 -0700 (PDT)
Received: by 10.142.162.1 with HTTP; Thu, 6 Oct 2011 06:57:49 -0700 (PDT)
In-Reply-To: <3C29CE19-E03A-4AC5-959A-7931FE5B9B04@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <3C29CE19-E03A-4AC5-959A-7931FE5B9B04@employees.org>
Date: Thu, 6 Oct 2011 21:57:49 +0800
Message-ID: <CABv173WfM+93wRj+k1JSRdarCwXOr6q-kRrT=8p=dewDn3jn1g@mail.gmail.com>
From: Congxiao Bao <cx.cernet@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=bcaec520ea43c3b29f04aea1b57e
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 13:54:39 -0000

--bcaec520ea43c3b29f04aea1b57e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

2011/10/6 Ole Troan <otroan@employees.org>

> > i couldn't understand why we "don't see such limitation in 4v6
> translation". 4via6 translate the private ipv4 address with 4rd mapping r=
ule
> while the public ipv4 address with RFC6052 algorithm, right? can the both
> case work fine if an ISP can only get a fairly long IPv6 prefix, like /40=
 or
> even longer?
> >
> > Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 addres=
s
> and PSID in the first 64 bits?
>
> only part of the IPv4 address would be embedded into the first 64 bits (n=
ot
> that I think that boundary should be "hard").
> e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. then
> only "1.2.3" would be embedded in the address.
> just like what's done for 6rd.
>


Thanks, Ole. That=92s the point! In this case , you can only have part of t=
he
IPv4 address embedded in the first 64 bits. This embedding does work for
encapsulation or tunneling, but can NOT work for stateless double
translation, which requires the whole IPv4 address+PSID embeded for any IPv=
6
prefix length.



Best,



Congxiao

>
> cheers,
> Ole

--bcaec520ea43c3b29f04aea1b57e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br>
<div class=3D"gmail_quote">2011/10/6 Ole Troan <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:otroan@employees.org">otroan@employees.org</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div class=3D"im">&gt; i couldn&#39;t understand why we &quot;don&#39;t see=
 such limitation in 4v6 translation&quot;. 4via6 translate the private ipv4=
 address with 4rd mapping rule while the public ipv4 address with RFC6052 a=
lgorithm, right? can the both case work fine if an ISP can only get a fairl=
y long IPv6 prefix, like /40 or even longer?<br>
&gt;<br>&gt; Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IP=
v4 address and PSID in the first 64 bits?<br><br></div>only part of the IPv=
4 address would be embedded into the first 64 bits (not that I think that b=
oundary should be &quot;hard&quot;).<br>
e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. then onl=
y &quot;1.2.3&quot; would be embedded in the address.<br>just like what&#39=
;s done for 6rd.<br></blockquote>
<div>=A0</div>
<div>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman">Thanks, Ole. That=92s the point! I=
n this case , you can only have part of the IPv4 address embedded in the fi=
rst 64 bits. This embedding does work for encapsulation or tunneling, but c=
an NOT work for stateless double translation, which requires the whole IPv4=
 address+PSID=A0embeded=A0for=A0any IPv6 prefix length.</font></span></p>

<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman"></font></span>=A0</p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman">Best,</font></span></p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman"></font></span>=A0</p>
<p style=3D"MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><span lang=3D"EN-US"><=
font size=3D"3" face=3D"Times New Roman">Congxiao</font></span></p></div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>cheers,<br><font color=3D"#8=
88888">Ole</font></blockquote></div><br>

--bcaec520ea43c3b29f04aea1b57e--

From ichiroumakino@gmail.com  Thu Oct  6 07:00:11 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 6589A21F8CB0 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 07:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.235
X-Spam-Level: 
X-Spam-Status: No, score=-3.235 tagged_above=-999 required=5 tests=[AWL=-0.236, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gd-Y8q1kmCN0 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 07:00:10 -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 A04CF21F8CAD for <softwires@ietf.org>; Thu,  6 Oct 2011 07:00:10 -0700 (PDT)
Received: by wyh21 with SMTP id 21so3296694wyh.31 for <softwires@ietf.org>; Thu, 06 Oct 2011 07:03:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=5nGZ19gWGcrQGhhZc2QVxiR9cxcBA4KdFixwSn8hQX4=; b=ECcN323UTiSdExcrHybXLvAFeahWA1d3bXSF5+56hLyjtsq0ZHaDd2irN45d8h8yir 1Hvv2ZTO/skRCFsQ66J1i5X0/VsCE0OlRTmMxPr1NavO1Ts9RaoGiOL2SiCHwerJPMJg LInzTyBztk6w2BF+642kwNFCt/aj1bGE8GSCs=
Received: by 10.216.230.218 with SMTP id j68mr1227475weq.66.1317909800923; Thu, 06 Oct 2011 07:03:20 -0700 (PDT)
Received: from dhcp-10-61-97-48.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id p2sm10373834wbo.17.2011.10.06.07.03.19 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 06 Oct 2011 07:03:20 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CABv173WfM+93wRj+k1JSRdarCwXOr6q-kRrT=8p=dewDn3jn1g@mail.gmail.com>
Date: Thu, 6 Oct 2011 10:03:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <845CF8A3-0463-4D52-A5DC-7AE697FA1208@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <3C29CE19-E03A-4AC5-959A-7931FE5B9B04@employees.org> <CABv173WfM+93wRj+k1JSRdarCwXOr6q-kRrT=8p=dewDn3jn1g@mail.gmail.com>
To: Congxiao Bao <cx.cernet@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 14:00:11 -0000

> > i couldn't understand why we "don't see such limitation in 4v6 =
translation". 4via6 translate the private ipv4 address with 4rd mapping =
rule while the public ipv4 address with RFC6052 algorithm, right? can =
the both case work fine if an ISP can only get a fairly long IPv6 =
prefix, like /40 or even longer?
> >
> > Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 =
address and PSID in the first 64 bits?
>=20
> only part of the IPv4 address would be embedded into the first 64 bits =
(not that I think that boundary should be "hard").
> e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. =
then only "1.2.3" would be embedded in the address.
> just like what's done for 6rd.
> =20
> Thanks, Ole. That=92s the point! In this case , you can only have part =
of the IPv4 address embedded in the first 64 bits. This embedding does =
work for encapsulation or tunneling, but can NOT work for stateless =
double translation, which requires the whole IPv4 address+PSID embeded =
for any IPv6 prefix length.

right, for the outside domain traffic.
putting the state into the IPv6 destination address doesn't affect =
routing.
so this works fine with the case where you give a user a /56, where you =
have to have efficient encoding. for the external to the domain traffic =
you need to encode the full IPv4 address.

cheers,
Ole=

From fibrib@gmail.com  Thu Oct  6 07:11:46 2011
Return-Path: <fibrib@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 7D26421F8D3F for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 07:11:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NGKqEbvRx9A3 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 07:11:45 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 9B66721F8D22 for <softwires@ietf.org>; Thu,  6 Oct 2011 07:11:45 -0700 (PDT)
Received: by qyk33 with SMTP id 33so2331556qyk.10 for <softwires@ietf.org>; Thu, 06 Oct 2011 07:14:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0dsr4E60Z5DXRRlvYg4PnxkKMl1RcVUAFVUaBqfSBW4=; b=AdhoUxvblnJFODGkANlp4HJHUSoLmUdwRipI0L2LtDzSxh0puTMgwFdp9pXBfSMRK2 hm8YilVySBLl0kitZqExDfRVQcHx3sgpagf+Mfx6InDPrbYUMLH9939pIgk17wHLF0f3 jyPf095S8OT2yr1XX6Q4ReEsm5Go7fE5hiCfE=
MIME-Version: 1.0
Received: by 10.229.63.169 with SMTP id b41mr562260qci.145.1317910496097; Thu, 06 Oct 2011 07:14:56 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Thu, 6 Oct 2011 07:14:55 -0700 (PDT)
In-Reply-To: <845CF8A3-0463-4D52-A5DC-7AE697FA1208@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <3C29CE19-E03A-4AC5-959A-7931FE5B9B04@employees.org> <CABv173WfM+93wRj+k1JSRdarCwXOr6q-kRrT=8p=dewDn3jn1g@mail.gmail.com> <845CF8A3-0463-4D52-A5DC-7AE697FA1208@employees.org>
Date: Thu, 6 Oct 2011 23:14:55 +0900
Message-ID: <CAFUBMqX=CeULnq3tLY5t+fD2D7sd=wyQJBNGWBa-=2YEtJMpDw@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=0016e65da6eef735a004aea1f295
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 14:11:46 -0000

--0016e65da6eef735a004aea1f295
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

2011/10/6 Ole Troan <otroan@employees.org>

> > > i couldn't understand why we "don't see such limitation in 4v6
> translation". 4via6 translate the private ipv4 address with 4rd mapping r=
ule
> while the public ipv4 address with RFC6052 algorithm, right? can the both
> case work fine if an ISP can only get a fairly long IPv6 prefix, like /40=
 or
> even longer?
> > >
> > > Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4
> address and PSID in the first 64 bits?
> >
> > only part of the IPv4 address would be embedded into the first 64 bits
> (not that I think that boundary should be "hard").
> > e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. then
> only "1.2.3" would be embedded in the address.
> > just like what's done for 6rd.
> >
> > Thanks, Ole. That=92s the point! In this case , you can only have part =
of
> the IPv4 address embedded in the first 64 bits. This embedding does work =
for
> encapsulation or tunneling, but can NOT work for stateless double
> translation, which requires the whole IPv4 address+PSID embeded for any I=
Pv6
> prefix length.
>
> right, for the outside domain traffic.
> putting the state into the IPv6 destination address doesn't affect routin=
g.
> so this works fine with the case where you give a user a /56, where you
> have to have efficient encoding. for the external to the domain traffic y=
ou
> need to encode the full IPv4 address.
>
> cheers,
> Ole


thanks a lot, Ole and Prof. Bao, for the discussion. then i got to fairly
understand the situation. :)

cheers,
maoke

--0016e65da6eef735a004aea1f295
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2011/10/6 Ole Troan <span dir=3D"ltr">&l=
t;<a href=3D"mailto:otroan@employees.org">otroan@employees.org</a>&gt;</spa=
n><br><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; bo=
rder-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-st=
yle: solid;" class=3D"gmail_quote">
<div><div></div><div class=3D"h5">&gt; &gt; i couldn&#39;t understand why w=
e &quot;don&#39;t see such limitation in 4v6 translation&quot;. 4via6 trans=
late the private ipv4 address with 4rd mapping rule while the public ipv4 a=
ddress with RFC6052 algorithm, right? can the both case work fine if an ISP=
 can only get a fairly long IPv6 prefix, like /40 or even longer?<br>

&gt; &gt;<br>
&gt; &gt; Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 =
address and PSID in the first 64 bits?<br>
&gt;<br>
&gt; only part of the IPv4 address would be embedded into the first 64 bits=
 (not that I think that boundary should be &quot;hard&quot;).<br>
&gt; e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. the=
n only &quot;1.2.3&quot; would be embedded in the address.<br>
&gt; just like what&#39;s done for 6rd.<br>
&gt;<br>
&gt; Thanks, Ole. That=92s the point! In this case , you can only have part=
 of the IPv4 address embedded in the first 64 bits. This embedding does wor=
k for encapsulation or tunneling, but can NOT work for stateless double tra=
nslation, which requires the whole IPv4 address+PSID embeded for any IPv6 p=
refix length.<br>

<br></div></div>right, for the outside domain traffic.<br>
putting the state into the IPv6 destination address doesn&#39;t affect rout=
ing.<br>
so this works fine with the case where you give a user a /56, where you hav=
e to have efficient encoding. for the external to the domain traffic you ne=
ed to encode the full IPv4 address.<br>
<br>
cheers,<br>
<font color=3D"#888888">Ole</font></blockquote></div><div><br>thanks a lot,=
 Ole and Prof. Bao, for the discussion. then i got to fairly understand the=
 situation. :)</div><div>=A0</div><div>cheers,</div><div>maoke</div>

--0016e65da6eef735a004aea1f295--

From despres.remi@laposte.net  Thu Oct  6 08:36:44 2011
Return-Path: <despres.remi@laposte.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 15F8921F8DA2 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 08:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level: 
X-Spam-Status: No, score=-1.856 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uSfU33df6b0k for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 08:36:43 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.83]) by ietfa.amsl.com (Postfix) with ESMTP id 401EF21F8DA0 for <softwires@ietf.org>; Thu,  6 Oct 2011 08:36:43 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2411.sfr.fr (SMTP Server) with ESMTP id 6DC6E7000158; Thu,  6 Oct 2011 17:39:53 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2411.sfr.fr (SMTP Server) with ESMTP id 54C087000152; Thu,  6 Oct 2011 17:39:48 +0200 (CEST)
X-SFR-UUID: 20111006153948347.54C087000152@msfrf2411.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <05DF0672-BE68-4DA2-8094-7B314E416A1A@employees.org>
Date: Thu, 6 Oct 2011 17:39:53 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EFC2E1C-ACBB-49FE-94C5-B3A10292B0F8@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <B3D5FABA-72BA-4C35-A068-D823CC0A4682@laposte.net> <CAM+vMERSbGuraAC9snvGUgPBOY40m5p0SX46qfVqJaB6bHmvCw@mail.gmail.com> <D8B8F1D1-1FE7-44E1-A6C6-E1480BD91C0A@ipinfusion.com> <4E82C970.8060801@jacni.com> <3580FD83-1FD6-4A5D-9AB1-046FBE47AFBB@employees.org> <823C69D6-D040-4959-8A5A-3B1B2CAF7734@free.fr> <C1DB0E47-C4F8-4AAF-B754-379B9B47BB95@employees.org> <EC5F7306-8EA6-4707-A8EF-D8D2BEC5E3B9@free.fr> <593B5458-3276-43D7-AF32-2FB8EF899AE7@employees.org> <332BEE87-D2F4-496B-8D73-16AC7FFA2B71@free.fr> <CC3E5BBD-3C75-48F2-90E7-AFAE365AAF2F@employees.org> <F0D8CC93-E84B-4565-8A78-3D166BA88FA7@laposte.net> <05DF0672-BE68-4DA2-8094-7B314E416A1A@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, Wojciech Dec <wdec@cisco.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 06 Oct 2011 15:36:44 -0000

Hi Ole,
I just found I didn't answer this mail directly.
In case other exchanged mails wouldn't have answered the point, please =
see below.

Le 1 oct. 2011 =E0 04:31, Ole Troan a =E9crit :

> Remi,
>=20
>>>>> what are the requirements for a globally unique interface-id? how =
is it going to be used?
>>>>> both for encapsulation and translation?
>>>>=20
>>>> In both cases, the CE node can recognize 4rd packets, and process =
them as such, without preempting any IID value that might be a =
legitimate value for a host behind the CE.
>>=20
>> This is my answer to your first (double) question.
>> If it is not enough, as suggested below, please explain what you =
don't understand.
>=20
> I specifically do not want a solution that changes forwarding =
behaviour for _all_ IPv6 packets.
> e.g. looking at 24 bits in the middle of an IPv6 address is such a =
change.

The proposed solution doesn't impact the forwarding behavior of any =
function that isn't specifically a 4rd function.


> I don't understand what requirements you are basing this 'solution' =
on.

Design objectives are listed in Sec 4.=20
They include:
- Possibility of IPv6 routing plans that have no constraints related to =
IPv4 residual deployment.
- Possibility (even in this case) to assign differentiated sharing =
ratios. This is achieved by having lengths of port-set IDs determined by =
lengths  of CE IPv6 prefixes.=20


> if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix =
out of the delegated prefix. then why do you need any of that?

I don't completely follow the proposal, and what you want to avoid.
In any case, the discussion should now focus on the proposed unified =
address mapping.
Agreed? =20


> note that I'm not arguing against having a defined IID for dIVI/4rd, =
that's nice for pretty printing like what we do for ISATAP.

Good, then.

Cheers,
RD



>=20
> cheers,
> Ole
>=20
>=20

From despres.remi@laposte.net  Thu Oct  6 09:03:45 2011
Return-Path: <despres.remi@laposte.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 8A52E1F0C5C for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 09:03:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level: 
X-Spam-Status: No, score=-1.856 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozdqm-5qz4pU for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 09:03:45 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.83]) by ietfa.amsl.com (Postfix) with ESMTP id B28A71F0C5B for <softwires@ietf.org>; Thu,  6 Oct 2011 09:03:44 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2411.sfr.fr (SMTP Server) with ESMTP id 27CEC700011B; Thu,  6 Oct 2011 18:06:55 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2411.sfr.fr (SMTP Server) with ESMTP id DD4897000118; Thu,  6 Oct 2011 18:06:54 +0200 (CEST)
X-SFR-UUID: 20111006160654906.DD4897000118@msfrf2411.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org>
Date: Thu, 6 Oct 2011 18:06:59 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 16:03:45 -0000

Le 6 oct. 2011 =E0 18:47, Ole Troan a =E9crit :

> Remi,
>=20
> [...]
>=20
>> 2.
>> (a)
>> The IPv6 Source address of an IPv4 packet from a CE is:
>>=20
>> a1- If the CE has an exclusive or shared IPv4 address:
>>=20
>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
>> +-------------+--------+---+---+----------------+------+-----+---+
>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>> +-------------+--------+---+---+----------------+------+-----+---+
>=20
> putting the IPv4 address / port information at the end of the =
interface identifier will allow for > /64 support.

Could you explain more the requirement you have in mind? =20

> what's the L?

On the picture, L is 32 bits + Length(PSID).
Don't see what you found unclear.=20

>=20
> you suggest that the first subnet of an allocation should be used for =
this purpose.

Did I do this?
Please explain because that's not, IMHO,  something to be done.

> the first subnet is convenient to use for e.g. manual addressing =
(since it allows the :: short hand).
> I do wonder if this has to be provisioned. e.g. some deployments may =
use the first subnet for the link between
> CE and PE. (i.e. a /56 - 1 using the PD exclude option is used).

See just above.

>=20
>> a2- If the CE has an IPv4 prefix:
>>=20
>> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
>> +-------------+--------+---+---+-------------+---------------+---+
>> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
>> +-------------+--------+---+---+-------------+---------------+---+
>>=20
>> (b)
>> V is the mark that characterizes IPv6 packets that are in reality =
IPv4 packets.
>> Its value differs from any permitted value of this octet in IPv6 IIDs =
 (ref RFC 4291).
>>=20
>> It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.
>>=20
>> An unambiguous mark is fortunately possible because currently =
permitted IIDs have in their first octet either bit6 =3D 0 (the "u" =
bit"), or bit6 =3D 1 and bit7=3D 0 (the "g" bit).
>> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction is therefore deterministic.
>>=20
>> The proposed V is =3D 00000011.=20
>> (With other values of this octet, other IID formats can be defined in =
case some would be useful in the future.)
>>=20
>> Note that, if and when a consensus is reached in Softwire, an =
extension of RFC 4291 will have to be submitted to 6MAN.=20
>=20
> or rather IEEE?

IMHO, IEEE has nothing to do with a marker that is purposely an escape =
mechanism from the modified EUI-64 format of RFC 4291.

> I am not convinced that "V" is needed.

The point is more, IMHO, whether you have an objection to it (and in =
this case which one).
Reason is that we are working for a consensus, and several are satisfied =
with the explanation that there are use cases where it is useful, and =
none where it is harmful.

> you could even use the IANA OUI if pretty printing was required.

The point is that it takes 32 bits which is too much to have IPv4 =
address + PSID in the IID.


>> (c)                                  =20
>> A Destination address from a CE to the outside IPv4 Internet is:
>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>> +--------------------------+----+---------------+------------+---+
>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>> +--------------------------+----+---------------+------------+---+
>=20
> this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.

Copying an available IPv4 address at a fixed place isn't IMHO a "big =
change".

> if we also allow for a BR subnet prefix of /128 I'm OK with this (I =
think).

I don't understand what you mean by "Subnet prefix of /128".


>> Note that if double-translation CEs are notified to use U instead of =
V, the last octet becomes 0 per RFC  6052.
>=20
> how would a CE know if it was single or double translating?

Presumably with a usual method, e.g. DHCPv6.
Anything problematic with that?


> e.g we could do:
>=20
> <--------- 64 ------------><--- 24 ------><----- 32 -------><--8 >
> +-------------+--------+---+--------------------+------+-----+---+
> | IPv6 prefix |CE index| S | 00-00-5E    |  IPv4 address  | PSID |
> +-------------+--------+---+---+----------------+------+-----+---+
>=20
> we also need to handle the case where IPv6 prefix + CE index > 64.

Please explain more your understanding of this requirement.
(I personally believe we should avoid that.)

> I suggest we then just put as much as the interface identifier that =
will fit.


May I suggest that, to be more constructive, you could first express =
your objections to the proposed unified mapping, rather than making a =
number of new proposals whose justifications are sometimes hard to =
understand,=20

Cheers,
RD=20


>=20
> cheers,
> Ole
>=20
>=20

From ichiroumakino@gmail.com  Thu Oct  6 09:10:13 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 B4F5921F8DF7 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 09:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.378
X-Spam-Level: 
X-Spam-Status: No, score=-3.378 tagged_above=-999 required=5 tests=[AWL=-0.079, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9U2dxBLxxBB for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 09:10:13 -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 EBB7021F8DE9 for <softwires@ietf.org>; Thu,  6 Oct 2011 09:10:12 -0700 (PDT)
Received: by wyh21 with SMTP id 21so3459360wyh.31 for <softwires@ietf.org>; Thu, 06 Oct 2011 09:13:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=VIoTUXEyxT4c+OdqWlvLfIhPmWXcq4nsu0Allj6EwEs=; b=dqKZ0aTHiu21etipD9+XfVjV2gEHYJdGkj59TzZB81ps/YCs9slvYp7+OyRPu0Sbwt 5AOH2kIZBckCwLDqlz8VHk9EI0oMNy1uuSKG5L21d9pgWjrjUDfCUOcgaIVP9ZqcgaEl fDQEL2HUlTRbBzhyRHE3EtbqUUs0MLJbXJPL0=
Received: by 10.216.132.210 with SMTP id o60mr1311022wei.92.1317917591112; Thu, 06 Oct 2011 09:13:11 -0700 (PDT)
Received: from dhcp-10-55-90-44.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id h14sm11013114wbo.7.2011.10.06.09.13.09 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 06 Oct 2011 09:13:10 -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: <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net>
Date: Thu, 6 Oct 2011 12:13:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A6E71822-0DC5-49D6-B113-30701B623FE6@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 16:10:13 -0000

Remi,

> May I suggest that, to be more constructive, you could first express =
your objections to the proposed unified mapping, rather than making a =
number of new proposals whose justifications are sometimes hard to =
understand,=20

I'd rather that we agree on the requirements.
my questions were against what requirements you based parts of your =
proposal on. are these new/different requirements from those I showed on =
the slide in Beijing?

cheers,
Ole


From despres.remi@laposte.net  Thu Oct  6 10:20:42 2011
Return-Path: <despres.remi@laposte.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 A35F321F8CBC for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 10:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.344
X-Spam-Level: 
X-Spam-Status: No, score=-1.344 tagged_above=-999 required=5 tests=[AWL=-0.464, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vyhWThowz7O for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 10:20:42 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.118]) by ietfa.amsl.com (Postfix) with ESMTP id DEBAB21F8CB6 for <softwires@ietf.org>; Thu,  6 Oct 2011 10:20:41 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2519.sfr.fr (SMTP Server) with ESMTP id 587EA700009B; Thu,  6 Oct 2011 19:23:52 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2519.sfr.fr (SMTP Server) with ESMTP id 34A4D7000061; Thu,  6 Oct 2011 19:23:48 +0200 (CEST)
X-SFR-UUID: 20111006172348215.34A4D7000061@msfrf2519.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <A6E71822-0DC5-49D6-B113-30701B623FE6@employees.org>
Date: Thu, 6 Oct 2011 19:16:56 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0CA7D5CF-BFE5-46FB-8948-9A51494CB8B0@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <A6E71822-0DC5-49D6-B113-30701B623FE6@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 17:20:42 -0000

Le 7 oct. 2011 =E0 00:13, Ole Troan a =E9crit :

> Remi,
>=20
>> May I suggest that, to be more constructive, you could first express =
your objections to the proposed unified mapping, rather than making a =
number of new proposals whose justifications are sometimes hard to =
understand,=20
>=20
> I'd rather that we agree on the requirements.
> my questions were against what requirements you based parts of your =
proposal on. are these new/different requirements from those I showed on =
the slide in Beijing?

Please send a copy of the slide you are referring to.
Thanks.
RD


From congxiao@cernet.edu.cn  Tue Oct  4 08:29:31 2011
Return-Path: <congxiao@cernet.edu.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 5A3C221F8D00 for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 08:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.444
X-Spam-Level: 
X-Spam-Status: No, score=-95.444 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_HAS_XAIMC=2.696, MANGLED_FROM=2.3, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5rUMtnM1ySF6 for <softwires@ietfa.amsl.com>; Tue,  4 Oct 2011 08:29:30 -0700 (PDT)
Received: from cernet.edu.cn (mail.cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with SMTP id 3D82921F8CF8 for <softwires@ietf.org>; Tue,  4 Oct 2011 08:29:29 -0700 (PDT)
Received: from [114.250.77.201]([114.250.77.201]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm364e8b368a; Tue, 04 Oct 2011 23:32:31 +0800
Message-ID: <4E8B2708.8000804@cernet.edu.cn>
Date: Tue, 04 Oct 2011 23:32:24 +0800
From: Congxiao Bao <congxiao@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
References: <CANb4Oc=QqdxCJVj+LNaOimZPT_mPPa-MQmwZaBM=92_QVrFiWA@mail.gmail.com> <67E4A8C5-B119-45DB-8367-BDF55A380DC4@laposte.net>
In-Reply-To: <67E4A8C5-B119-45DB-8367-BDF55A380DC4@laposte.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: congxiao
X-AIMC-MAILFROM: congxiao@cernet.edu.cn
X-AIMC-Msg-ID: vCtyGL1B
X-Mailman-Approved-At: Thu, 06 Oct 2011 13:59:29 -0700
Cc: Softwires-wg <softwires@ietf.org>, Xiaohong Deng <dxhbupt@gmail.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 04 Oct 2011 15:29:31 -0000

Hi Remi,

Ok, we will draft a document on using existing tools for O&M in 
dIVI/dIVI-PD very soon.

Best,

Congxiao


RÃ©mi DesprÃ©s å†™é�“:
> Hi Xing, Congxiao,
>
> Le 4 oct. 2011 Ã  15:26, xiaohong deng a Ã©crit :
> ...
>   
>> It IMHO would be helpful if anybody would clarify some details to 1)
>> first prove source based classification is either a valid or a
>> non-valid requirement for address mapping; For this regard, I would
>> begin with that why do we think the source based IPv4 classification
>> ability instead of the more general five-tuple based IPv4
>> classification ability should be reserved, when deliver IPv4 over
>> IPv6?
>>     
>
> What about starting from your conclusion slide in Beijing?
>
> It says:
>
> "dIVI/dIVI-PD can use existing tools for O&M
> â€“ Null route
> â€“ ACL
> â€“ eACL
> â€“ PBR
> â€“ QoS
> â€“ Caching"
>
> Open questions include:
> - Which addresses are used for these O&M functions? (source? destination?, CE to CE?, CE to BR?, BR to CE?)
> - Are ports within IPv6 payloads used, or just addresses?
>
> Thank you if you can share your views on this.
>
> Regards,
> RD 
>
>
>
>
>   


From ot@cisco.com  Thu Oct  6 13:56:53 2011
Return-Path: <ot@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 6564F21F87C5 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 13:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.169
X-Spam-Level: 
X-Spam-Status: No, score=-6.169 tagged_above=-999 required=5 tests=[AWL=-4.430, BAYES_00=-2.599, DC_IMAGE_SPAM_HTML=0.001, DC_IMAGE_SPAM_TEXT=0.001, DC_PNG_UNO_LARGO=0.558, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6b2S5ZmhejSE for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 13:56:52 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 5C5AC21F8C15 for <softwires@ietf.org>; Thu,  6 Oct 2011 13:56:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=235532; q=dns/txt; s=iport; t=1317934800; x=1319144400; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=Xb0hAItZSxrBOPXaiouG+QVAiY3rkzMOXU2GNxaf8H4=; b=SsFpbDwcEPLmw+WvrRhKfQjHloidB/8Eq0A6C0lgiTXTOUktYxvt1xjw fZGt1NfLMVS4U4ERZR6Fn3outPJjTbvQf7I9cZX+dl2lOaSvm3YEO+mSL CWABe0aa9zOo1s76wKIa6XwBxbCYvHDSAYD2ZUpfmFq8A1udxhAjr8FIe 4=;
X-Files: Screen shot 2011-10-06 at 16.56.12 .png : 171392
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAMYVjk6Q/khN/2dsb2JhbABCqDOBBYFTAQEBAwEFAQwBZhALHQEBJwIVAT8GNYdcmlYBngWGS2EEjlGFHZFi
X-IronPort-AV: E=Sophos;i="4.68,498,1312156800";  d="png'150?scan'150,208,150";a="480348"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-4.cisco.com with ESMTP; 06 Oct 2011 20:59:59 +0000
Received: from dhcp-10-55-90-44.cisco.com (dhcp-10-55-90-44.cisco.com [10.55.90.44]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p96Kxv0l009537; Thu, 6 Oct 2011 20:59:57 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/mixed; boundary=Apple-Mail-15-325180960
From: Ole Troan <ot@cisco.com>
In-Reply-To: <0CA7D5CF-BFE5-46FB-8948-9A51494CB8B0@laposte.net>
Date: Thu, 6 Oct 2011 16:59:57 -0400
Message-Id: <FCD9A724-9BA0-470D-BEBF-2799E6D643E4@cisco.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <A6E71822-0DC5-49D6-B113-30701B623FE6@employees.org> <0CA7D5CF-BFE5-46FB-8948-9A51494CB8B0@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Thu, 06 Oct 2011 13:59:29 -0700
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 06 Oct 2011 20:56:53 -0000

--Apple-Mail-15-325180960
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Remi,

>>> May I suggest that, to be more constructive, you could first express =
your objections to the proposed unified mapping, rather than making a =
number of new proposals whose justifications are sometimes hard to =
understand,=20
>>=20
>> I'd rather that we agree on the requirements.
>> my questions were against what requirements you based parts of your =
proposal on. are these new/different requirements from those I showed on =
the slide in Beijing?
>=20
> Please send a copy of the slide you are referring to.

certainly.

cheers,
Ole


--Apple-Mail-15-325180960
Content-Disposition: inline;
	filename="Screen shot 2011-10-06 at 16.56.12 .png"
Content-Type: image/png;
	x-mac-hide-extension=yes;
	x-unix-mode=0644;
	name="Screen shot 2011-10-06 at 16.56.12 .png"
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAAs4AAAIhCAIAAADRnKssAAAXVmlDQ1BJQ0MgUHJvZmlsZQAAeAHV
eWdYFMuzd89sXnaXnNOSc845gySJEpWcM0sOIiAgQUFAEQFFQUVEBVGiJFFQxIOIggoGgkgQFQOC
gvIOes753/e59357v7z9PNv7m6rq6pqp7p6qGgA4V7yjosJgBgDCI2Jp9maGVBdXNypuChAANyAD
MSDp7RsTZWBrawX+1/ZtAkA7zMcyO7r+V7H/mcHo5x/jCwBki7B9/GJ8wxF8AwDY0DeKFgsAagOh
jybERiEYfQ/BLDTEQAS/2MGBf/DqDvb5jTHo3zKO9kYAYDgAwJO8vWmBAJCFETo13jcQ0UM2BgDL
FOEXHAEAswuCdX2DvP0A4CxHZKTDwyN38B0Ei/v8Fz2B/wV7e/v8q9PbO/Bf/OdekJHIxMbBMVFh
3km/L/5fduFhccjz+t2YkJ4UEbZ7xzdsyG/Rz9vYEvnnQX6/osJ++wyRgbj8I/Y4ILQdLB3hs9vm
b6wbQDO1RzAyFrKNijXcwcgzgwKiYm0d/6anJQcZ7UYwCaEf848x+UfPmRBvix2fURB6My3Ofg+C
hRHcFxPvYIJgZEVBb5KDHJ3/lvnq52/8Nx2GA4JNzf/IwEzBseY7c7EgPhcMjbTcsQGZC1YFliAM
+IM4QEP6CCADrIARMP67lwEBwBvhxCO8GBAK3iI4HBkRiYyJRDD1bzmj/0Yx/T0uEBn3f2ukAl9E
Nu7fOf/MRkXm/EdnMPBD8D90b2SOHd6OdTGewZn/mfMfiR19v62Rb5Bfkt/6xya0KFoRrYI2ROug
ddEagIpmQ3MBGbQyWh1tgNZDayE8DWAK3iCaA/+xcUd/eHNAfHlkkqZTEMLduXeff7jA6bd08L/X
/80CEDyy0rbyjwUAxPonIvsAAKPIqCRacGBQLNUA2bn+0lTzCF9ZaaqivILCDvv/m7ZzZv0x9ov9
77MIYnv4H1okcjMaO2fMwf/QvD4A0BaCbFOm/9BE2wCgVwRg6IRvHC3+jz70zh8GEAE9skI5AR8Q
AuLIc1YEqkAL6AMTYAFsgCNwBR7I+glC1iANJIBUkAFyQAE4Co6DClANasFFcAU0gzbQBW6BQTAM
RsE4mALTYB68A6vgG9iEIAgHkSFmiBPih0QgKUgRUod0IRPICrKHXCEvKBCKgOKgVOggVACVQBXQ
WageugZ1QLegIegR9ByagZagz9APGAWTYBaYFxaF5WB12AC2hB3hfXAgHA0nw1lwIVwO18CX4Vb4
FjwMj8PT8Dt4DQVQdCg2lABKBqWOMkLZoNxQASgaKg2VjypD1aCuojpRd1GPUdOoFdR3NBbNjKai
ZZB1ugu9B+2LjkanoQ+jK9AX0a3oO+jH6Bn0KvoXhozhwUhhNDHmGBdMICYBk4Mpw1zAtGAGMOOY
ecw3LBbLhhXDqmF3YV2xIdgU7GHsKWwjtg/7CDuHXcPhcJw4KZwOzgbnjYvF5eBO4i7jenFjuHnc
Bp4Oz49XxJvi3fAR+Ex8Gf4Svgc/hl/AbxIYCCIETYINwY+QRCginCN0Eh4S5gmbREaiGFGH6EgM
IWYQy4lXiQPEF8QvdHR0gnQadHZ0wXTpdOV0TXT36GbovpOYSJIkI9JeUhypkFRH6iM9J30hk8mi
ZH2yGzmWXEiuJ98mvyJvUJgpshRzih/lAKWS0koZo3ygJ9CL0BvQe9An05fRX6d/SL/CQGAQZTBi
8GZIY6hk6GB4yrDGyMyowGjDGM54mPES4xDjIhOOSZTJhMmPKYupluk20xwzilmI2YjZl/kg8znm
AeZ5FiyLGIs5SwhLAcsVlhGWVVYmVmVWJ9ZE1krWbtZpNhSbKJs5WxhbEVsz2wTbD3ZedgN2f/Y8
9qvsY+zrHNwc+hz+HPkcjRzjHD84qZwmnKGcxZxtnC+50FySXHZcCVynuQa4VrhZuLW4fbnzuZu5
J3lgHkkee54UnlqeBzxrvHy8ZrxRvCd5b/Ou8LHx6fOF8B3j6+Fb4mfm1+UP5j/G38u/TGWlGlDD
qOXUO9RVAR6BXQJxAmcFRgQ2BcUE9whmCjYKvhQiCqkLBQgdE+oXWhXmF7YWThVuEJ4UIYioiwSJ
nBC5K7IuKibqLHpItE10UYxDzFwsWaxB7IU4WVxPPFq8RvyJBFZCXSJU4pTEqCQsqSIZJFkp+VAK
llKVCpY6JfVIGiOtIR0hXSP9VIYkYyATL9MgMyPLJmslmynbJvtBTljOTa5Y7q7cL3kV+TD5c/JT
CkwKFgqZCp0KnxUlFX0VKxWfKJGVTJUOKLUrfVKWUvZXPq38TIVZxVrlkEq/yk9VNVWa6lXVJTVh
NS+1KrWn6izqtuqH1e9pYDQMNQ5odGl811TVjNVs1vyoJaMVqnVJa1FbTNtf+5z2nI6gjrfOWZ1p
Xaqul+4Z3Wk9AT1vvRq9WX0hfT/9C/oLBhIGIQaXDT4YyhvSDFsM1400jfYb9RmjjM2M841HTJhM
9phUmLwyFTQNNG0wXTVTMUsx69uF2WW5q3jXU3Nec1/zevNVCzWL/RZ3LEmWDpYVlrNWklY0q05r
2NrCutT6xW6R3RG722yAjblNqc1LWzHbaNubdlg7W7tKu7f2Cvap9ncdmB08HS45fHM0dCxynNoj
viduT78TvdNep3qndWdj5xLnaRc5l/0uw65crsGu7W44Nye3C25r7ibux93n96rszdk7sU9sX+K+
IQ8ujzCPbk96T2/P614YL2evS15b3jbeNd5rPuY+VT6rvka+J3zf+en7HfNb8tfxL/FfCNAJKAlY
DNQJLA1cCtILKgtaCTYKrgj+FLIrpDpkPdQmtC50O8w5rDEcH+4V3hHBFBEacSeSLzIx8lGUVFRO
1HS0ZvTx6FWaJe1CDBSzL6Y9lgUJDh/Eicdlx83E68ZXxm8kOCVcT2RMjEh8kCSZlJe0kGyafD4F
neKb0p8qkJqROrPfYP/ZNCjNJ63/gNCBrAPz6WbpFzOIGaEZf2XKZ5Zkfj3ofLAzizcrPWsu2yy7
IYeSQ8t5ekjrUHUuOjc4dyRPKe9k3q98v/z7BfIFZQVbh30P3z+icKT8yHZhQOFIkWrR6aPYoxFH
J4r1ii+WMJYkl8yVWpe2HqMeyz/29bjn8aEy5bLqE8QTcSemy63K208Knzx6cqsiqGK80rCysYqn
Kq9q/ZTfqbHT+qevVvNWF1T/OBN85tlZs7OtNaI1ZbXY2vjat+eczt09r36+/gLXhYILP+si6qYv
2l+8U69WX3+J51JRA9wQ17B0ee/l0SvGV9qvylw928jWWNAEmuKalq95XZtotmzuv65+/eoNkRtV
Lcwt+a1Qa1LraltQ23S7a/ujDouO/k6tzpabsjfrugS6KrtZu4t6iD1ZPdu9yb1rfVF9K7cCb831
e/ZP3Xa5/eSO3Z2RAcuBe4Omg7fvGtztvadzr2tIc6jjvvr9tmHV4dYHKg9a/lL5q2VEdaT1odrD
9lGN0c5H2o96xvTGbj02fjz4xPzJ8Pju8UcTeyaePd37dPqZ37PF52HPP03GT25Opb/AvMh/yfCy
7BXPq5rXEq8bp1Wnu2eMZx7MOsxOzfnOvXsT82ZrPust+W3ZAv9C/aLiYteS6dLosvvy/Luod5sr
Oe8Z31d9EP9w46P+xwerLqvzn2iftj8f/sL5pe6r8tf+Ndu1V9/Cv22u529wblz8rv797g/nHwub
CVu4rfKfEj87f1n+erEdvr0d5U3z/h0LoJAeDggA4HMdkkO4IrnDKABEyp+c4rcEkq5AiAyCcUik
YIFEAHOQJPLe7oM54Vh4EmWOuo02Qz/BhGMZsf24VLwuAUd4SeygqyIVkesoLxgYGC2Z8piHWBnZ
9rJf5kRzeXN381L5DvNvCPgJTgrvFhkSkxMvlHgnZS5dLfNNzkj+iMKoElnZUCVGtUqtT31a46cW
u7aUjoauiZ69vq9BjGGW0QnjBpNe08dmS7u2LVgtpa2MrN13B9vE22bbldhXOzQ4tiG7fth5zOW5
62u3OffFve/3LXq88Bzx6vVu9Dnte8Qv2T8gwC5QK0g4mBL8LeR16GBYffiRiKhIhyi1aK7oLdqr
mL7Y2rjs+IAE80SpJGLScvKDlKbU8v1ZaQkHotNpGcmZ+QfPZnVnvz5EyNXOi8qvLZg4QizULgo/
erp4pOTnMenj7mX5J1rLpyvoKlWqPE/lnW6unjqLrpGpdTp34PzFC4/qNuqpl6waUi83X/nUqNlU
dO3jdfcbD1tt2p50aHfG3qzvetFD16vU53Qruj/7dvGdsoGyweK7ufcODh26f2T4yIPsv2JHnB/K
Ptwc7XuUMqY69u3x0ycd4xUT+596PjN8LjJJmHw/9ehFy8uKV/tfe00bz0jMMsx+n3v7ZmJ+6O2t
hZuLHUsdy+ffFa7Ev/f4YPJRapVhde3T5OeeL2e/Zq8FfbNcl9tg3lj//uJH32bNVtZP/1/G24Lb
24j/sYALiQ4TwQAS0VlBR6HXsBISe31BeaImkKjpJSYKS8G24fzxXPhJQhUxkM6QpEN2pATRpzOc
YbzFtMTCymrMlsTeyPGRS5abxtPFR8fvRL0ksC1kIJwh0iu6Ja4mESJ5SmpY+rMsq5yS/C4Fd8VA
pWjlJJX9qslqIeruGlaaOlry2oI6rLp43R967/VnDMYN7xv1GF83qTMtN8vdlWAeZOFquctK3Vps
N6sN2uar7azdI/s+hybH03tynWKcPVzMXZXceN2x7h+Qk77bo9Yz3yvS29FH2ZfkO+vX4V8UEBCo
HcQY9Db4ZkhxqH+YZjh9+FxEW2RulGu0FLIuRmLOxNLijOJZ4xcSOhIPJ3kky6fAKU9TG/cXpIUf
2JNunKGZqXFQJ2tXtktOxKFDuefzbufPFPw6wlOoUeR0NKb4aMnl0qFjb8vgEzzlqiftKsIrC6ou
nxo9/e2M4FnbmoO1Hec+XZCti754o369QeNy6pWeRtBkcO1g88ANTItZa27b3Q5cp8nNzK7u7q+9
on0Ot1L6T9++eWd8YGlw/R56iPm+wLDcA52/rEbcHgaNJjzKGTv+uOZJ43jXxNDTiWfzz79OoV6w
vBR5pf7aajpwpnZ26Y3YvNvbnIVLi3eXZpY3VijvRT7ofXRfTf80+kXpa+nal3X7jRs/ODaztzZ+
Jfz2PxowAkmwG6SDPiSu14RioTYYhq3hM/AmygN1H62NbsWoY/qxttg5XAqeG3+XcIToS6dN4ib9
Is9ShulbGM4zljMVMueyZLPmsBWwl3JUczZwtXN383Tz9vD18vdQbwq0CDYInRIuEIkT3SumLy4o
ASSmJNukCqSdZKgyy7ItcunylgpsCjOKDUpxynoqBJXHqqfUgtSV1Tc0ejSztSy1mbQndWp0Q/QU
9bb0Bw2KDfcZSRqtG982KTJ1NxMz+7yrxzzfwslSwPKdVat1+m4rGzabGdsGuxh7LQfY4b5jyR43
J6rTgvNVlzhXLTfYbci9aK/DPrZ9zz0qPfd58Xq99D7ls8+Xx3fSr9zfKYA54GFgQZBJMEDWS3yo
QuhKWF24TwRPxNPI0qjd0fjoW7TkGKWYldjzcR7x7PEPEw4l6iVuJDUlB6dQU56nHtvvmMaZNn+g
Pf1YRlJmwMG9Wa7Z7jn+h+Jys/PK8i8UtB4ePDJeOF/0tRhVwlwqeEz+uGaZ0QmLcruTrhU+lZFV
B06Vnr5cPXzmY41IbdK50QtidWkXJy7JNGRdnrqq0Jjb9KpZ9XrBjdetSm2H2l90Kt3M75rt0e4t
7/vW73i7ZUBs8Nw9maGB4dC/hEdWRu+OXXtSP9H07Nbky5fgtfxM3Zuchfzltg/0n3LXODZatpx3
/P+ntrTzTsCqAnB+DgCnswDYuQNQJwWASCVSNkHqHbZkABw1AGxYBKDnJwFkdvXf98dO5c0UqXEc
QjLHIfAOokAK0B4oGToFdUFT0BaS3+nBPnAOfAl+CH9FcaMMUEGoo6gO1CyaDqkfeCEZWTv6DYYJ
o4eJwJzFjGOJWANsIrYZu4ITxwXi6nBLeFl8HL6XQEdwI1wmQkQXYjMdhS6CboykTjpDxpNp5FcU
C0oHvTh9BQOZIYNhnTESyVd8mV4z+zAvsISzfGPNYKOwnWKXY7/N4c6xxlnMpcD1mDuBh5dnlPcQ
nyE/4L9FzRawFuQUXBS6KVwsEiJqKiYiThJfk5iVHJO6I90pc122Sa5RvlmhXbFPaVj5lconNbQ6
q4aQpoyWgra8jqQuVY9JH9b/aDBl2GtUY5xrEmnqYma4S86cz4LeEmW5YbVqvbx73mbWdsbujf07
hy+OP50IzuwuYq4abtbuvntT9h33aELeY+99KL5Kfq7+BwJqAweC5oJ/hjKFCYRLRshGykRJRAvS
2GIIMT9il+K5EqwTs5J6k3+lmuwvTXuXbp1x86ByVkeO+aG5vEMFAoevFuoXTRcXl7oc1zlhfjKh
cuA09xlKDVz7/fznug/1Kw0rVz42rl37eQPfyt0u12nc5doT3Bffn3YnfXD/vfj7YQ+8RgpG28eW
xwWe7ntePfX2lcJ0xuz4vNRC7tLCitmHS58YvqSsvd8I+LHwM+r3+UEPZIEdUo2qAL3gDUSHVAPc
oSwk4x+GPiLZvSbsBefCTfBzFArJ2V1R2ahrqNdoMnKqhKIr0X8h+bcCxg9ThfidHmuFzcPewxFx
1rgS3CReBE/D9xPYCGGEQaIQMZM4T2dB10mSIlWTWcmHKVhKJj2gz2BAMeQyUhhPMAkyNTLrM4+z
hLNiWWvYDNhm2XM4ZDgmODO45LmmuUt5dvGiefv5DvKbUknUCYEawRghU2E+4Q2RCdE2sTPiJySK
JQulCqVLZCpkL8i1yN9TeKW4rsyqoqnqq1ao3q3xUUtE21OnUndKn8/Az7DRaNPExLTAbNgcY6Fm
6WOVY31h9y2bSdtVe7QDm6PkHn0nV+cYlyLXq24j7p/2sXnoeAZ4FXv3+HzwE/J3CSgKHAz6GaIc
Ghx2OvxRJBylGO1FK4y5GbsYT5+gluiVVJDcnrKwnz3N/MD+9OaM5YNCWfuyK3Ke5bLnueafLnhz
RKYwsWiwmKMksvTBcfmyynLKybxKUtXx02LVd88G15LONV9wu4iub2rwvMJw9XZTYrPc9cWWurbg
DpnOz12dPZl9Vv3st+cGmu6mDlkMcz4YHdnzcO5R8mO+JyMTBc8cJkVfQC9nXw/ONMwVzdMWHJa4
l6tXxN5f+6i7OvLZ88vHtfR1+o2TP/g2q39y/Sr67X92YACikMrRQ7CN+D4AOgkNQF9gQdgeqeG0
wStIrcYF2e9DaBRSQ0xGt6HXMCqYeEw3FoO1wVZil3FauKO4Rbwx/hwBT4givCBaEfvo1BBPG5Ie
kF3Jy5Q0elb6JgYbhk+MZUy6TEvMp1gcWMms99ny2K04mDgmOc9z0bgNeJh53vEO8p3jz6GGCjgK
GggpCouJ8Ityi3GJUyWkJDWkLKW9ZVJlK+S65d8oUpS0lWkqV1U/qqtoZGiOaYvrZOm+1bcyaDOS
Mj5nKmBWay5h0WJlbP3MJsqOZN/k6I7s127XeHflvRsefV5HfDz8VANIgc+DK0LNw5YikiK3omNp
87G2cdcTGBNpSU9SNFPPptEdSExfyHQ5+CDbMKczVzmvtUDn8FCha9G74rRSxmM1ZXInOk7qVvRW
aZ9qrcacsTp7vOb1OcnzCRcGLrLWB1zqvEy54ne1q4n1WlTz8A1xJPN5327X0XaTryun+0Ovc9+t
fqnbx+9sD4bcfTKkf7/hAdtfMSP3R7kfBY1dfrw8LjTh/DTz2cXn9yfnp7ZeMrzify01rTKjOas7
p/9Gf173reaC2qLCkuSy4DvKu6WVjvcJH1Q+rHw8v+r6ifip63PAF4Yv7V/3roG1mm+G32bXD2zw
bHR83/N99cfhTbHN/i2PrY2fpb/kfg1t++34PyZACalDIg0iGSLlx1fb219EkaSiBICfxdvbmzXb
2z9rkWQD+QbSF/bne8WOMBapuVch9P+5/R9//n59pC/JagAAAAlwSFlzAAALEwAACxMBAJqcGAAA
IABJREFUeAHsfQecHMWVd3dPntnZrI3KYRWQVhIoICEEAgMiyucD2ycEBvMZHE/YGPMBNsb4gAPb
B/iwMZw5/IHAAWwjMhgkgiwkggSrvFpplVab88xO7v7eq+quqe6ZXmYVQGtX/aTeV1WvXr36V3W9
11XVPbKmaZIIAgGBgEBAICAQEAgIBI4DAn99/lXlOIgVIgUCAgGBgEBAICAQEAggAtWV5cLVEENB
ICAQEAgIBAQCAoHjiIBwNY4juEK0QEAgIBAQCAgEBALC1RBjQCAgEBAICAQEAgKB44iAcDWOI7hC
tEBAICAQEAgIBAQCwtUQY0AgIBAQCAgEBAICgeOIgPNYyX61NbSpJyrBm7NyhkhIoW/U8oTOpd00
qVSRM8tkCDk+CeGk+st9HVT2d8eVeh0nuu91z74WlaB5TVVpmdt1fFAZBlJ/0XQoDu9pa9pXysqr
PJ4TROP/2t8QU1VQ5srKUdVe3wmilVBDICAQEAh8tggcM1djdXP/Q3u7JXAaqNvAf64DUnQnw/BE
5PTHPL4/EVyNzwyE/lTqlvoWdIVk+brRxSeOq1HXP/DX9p4fj6+yQPPDvU1JSJKlC0oK/pldjdv3
N4ZSYNTVswoKM12NbeHQH9tb7xg7wYLe8Y7esXdnbzIpaeoZhSXC1TjeaAv5AgGBwHBB4Jg+xKPL
AD4EGgD0LdL/IBFsuZGikCggBCknQgB9UJO09/PZKtWbTK3cdfDk93as7wtn0QS1NfDMkv1Pk6QS
EDQYbKaO608mv99QP+uDjW/1dH8GWIA+sKqhpixafQaaiCoFAgIBgcAJg8AxW9UgLUKbXeJ2XDW6
0NRAMORoDiBXRgItJU1CC/8ZLmmklURFTpTwv80dvzzcZu+HERhPFGU/Qz1gHwn+mfwM0GZV6+Ff
HNqHg41sZHza+qHrY/V+Pm0dRH0CAYGAQOAEQ+DYuRrGo3aFz/nz6RUnWDMHVwc9pBMpgPmkKlnt
KCjZcGotTa36Jz6oAThsm3OqSvyMSutBDTjAAcYeQhb0SPpxvNQtPAdXWySt0iMOahxHnIVogYBA
YHghcOxcDWg37MZ8BtP7UQOubyKdSA4Huj7Z9RnjPVGOQB417kclYLTXm708jEC62qE7HNm5jlPq
aF/gOEkWYgUCAgGBwPBF4Ni5GnRhAM32sHM3iMInzsKG7mfAAdthh+SJcCN8lqsaJ0L7hQ4CAYGA
QOBEQ+CYuRowwRum8QgN5O8Pd0dTWHZOoW9G0Hb9uT+Zeqall+L4pcpCv/n11I548o3O/nU94cPR
eGciBavZRS5lUsB7dknwvJJg5lu1WJ/uZJjUjqTUP7R20Vouryh2K1nOz/YlU39u088efqWyJFM4
FO9KJNd097/T238oGu9KplKSVuhwTPR7lxQG4RUSh/kt3xc6etqTiY39YaKS2hSLP9bSDkL8ivKl
shKqzO9a2+n5hGUlRcWuLN0HP9X7t57e13v6dkUiPclUvsMBCyGfK8xfWlTozdYKEPt4WzsoFlCU
L5aWQrQzkfhTZ+ff+/ub43GPooz1eC4oLDy/qMiiLdUn9+v63p4Xujq2hsM9ySS0aLzXt6SwaFnp
iExs/19LE3RcnkO5rKwymko9dPjga52goTQvmH9V5ciJflw5eKL5UJIAcVFp2Qg3rvS83NHWEo+u
7+kiqxpSSyzyWNN+SIcmLK8clann+71dL7S3bOvv7UjE8hzOUV7/uaXl55dWeB2OTGZIefxQI6AE
nJdVjo6BVgd2v9beDDrMLSi+atT4SYF84Fl1aG8CzoTK8oVl1WXZ9lB6E/G1Hc1vd7YcjIQ749Gk
qhW4XOMDwTNKKi6uGOOy6aCs+ohEgYBAQCAwXBCQj9WPyH+jruk3B9DunhR0bz2j5gja/+XN+/8I
PoSmnT8i+NLc8XYSfnuw82vbD4JjMzng2Xn6VMbWnUjeVN/8/w53xcFMgWOAdoi8eYsuBP6fEvA8
etLohYV5rAgQzbFE1dtb8LyqpHWeUcuMN6av20I4ta7FM4uyGfXdA9GajduQR5PiZ8622AlwiW7e
e+i3zR0xXMnX3Rn9L7GRE32e/5k89sxCNFE0nLpp+8YQvHVCNKdXsrBR7XYdmj+b8rje2UhedpU/
mnXSzDzrcv1r3T3/3rgfnAxSmlQKdRE3qdrlumvM6CvLRhi1pf/6N24E12q0x73/lFN+29r63ca9
If5MJQHwJJ9vVc3kWXkm9NIiBqXe6+v91u6dH4T6kQv0Qb3ggDCeqBjp8TxcM+2CEpNWnjdfjavq
OK93x6mLz9383tu9xrskmgreUvvp5+Y5ncE3Xw4lEyBhw9zT5xcUAXHGB+ve7u4g8g20SRUlTnfH
WRcBAwvbQ33f2b55TXe7vtXCOXyjPN6fT5n1xcrRjJkRvlf+EFXV0W7v7rOWnbvxjbe62vQsVfU4
lPZzvxR0ugpe+X1fIgbg/33RBQuLy1hZICKp5G07N/16346BJHhN5NsohprkBKs22h/89cxFF1Zk
qZqXI2iBgEBAIDC8EHjvg4+yPKwfRRvAKNF/RyLj6pFgMNAO/a2rvy2GViRrePxwF9oqRbqqupgx
tMcTCzbW/09TZxysi6yBHat0O8f7XUVOBddaCP/OgejZmxq2hSKslE5ALvKgRTWHrIlpFlKAtBfL
MruBDD2J5GmbdvyquR39DHB4ZK3C7RjvcxeDPmBm4KJIDdHYuVt2fQhrGEYAvSkCujIolso3OOAv
akvYuDRK/uzQ4aXbd6KfAQyK7FOkMV5XEGuEoDUl4l/Zs+c7exuzOJdokvGVjZ81HfpaQ0MolQRa
VlUHpKPPAXYxBV+qOHvrxwdjUVpX7tc/tbUs+uiDD/p78RVQTc1T5Ck+X7XTSaOHIgMX1334+9bD
JoG6Pqkf7dlFvAfy+mgqAcWXFpWAn4HMRBqqR/w2TAECCtIrpDMGfCUkHd7oaF3w7utrulpJWdDH
McUfqHK5afTgQOhLm9f9ZDf1MtOlkMK6EKgf7/r4rY4WPUrwOa+0EvwMnYekIJ5cCCcTS9a98POG
uoFEQlLxwxvlbvd4X6DUSepFDbUD4b5l7778ZnsTV06QAgGBgEDgHwGBLCvwR9YsDewiGDWrzR2C
sM+VBqu9zqYYfgLpjy093xljetKlghoHYut6wTZrsMZ9ZVXa1bix/vCuSAxMrF+Rf1ZTDVseBS59
GRzWHu7b3/ZQUweoB0+lP2ls/tOM8Sa1mIHnUnE/iDaHWmouy0RiWRpMLb+l8dCWCFhlzavI/zlh
5JVlpWxdZG8k+sum1l8ebtVkGYznbfsPvTh9MhXx+ozJYI1/1dz6w32HoC1LCvP/MnUSZKUrSUeI
/0SLkeuTbR0/OHCQss7w++4ZM/qcwkIn+Dia9m4odPP+/W/3w6KC9mBLC6yR/N+RI7miYPigWq0l
od20rxHS/7W4+HvVI+fmBWVZhv2Onx7c/5d2fPm2K5H46YF9j0yawpcdnP441H/lji0J4gHAjskv
Jk65sGQEXf75qL/vazu3fNDXA77Y17bXLcgvHOvzU2ka4W+Lx+47sAd0Pjkvf0lRaW8y/lJH6zXV
YwwediZDV+HF2QuSmvrbQ4031qOjsLCw5MWTTwOCR29PuP8Lm9/pSyQhdaI/7xdTZl0wospJti0a
wv231df9vgkRuH3Xx5P8ecurx+mi9T/oeHXGI7/YswXgml1QfFZpJWyIvNx28JpREw1O4pmZfBvM
uXPX5o3duArilOQ7ps352tippcb2Cjg3v9675ef1H8Gwh2+S3bpt49/P/IIhTfwVCAgEBAL/CAgc
M1eDLEKjeW6NJW7e1aw/1PHTfBa4tJ9MqmBb9XAU4Mrqorsb4XSC9mRLd1ZXA9LJoRDp3JL8Kq/+
We59kdjjLXCuAoy99Pj0sf9ajsvpLEzye389dTSc6HjwUDsYmJc7+8D6ghFlDMYSQjoBKJJNzDnP
aWIhEeDTdwTSeS3x+CPNeMYCJD8yedwV5XgAgoXxPu/9E8d4FPneQ/iV0td7+2CzgIIQdKJ75APL
R6p3yXIhfYJnhYEAlw4ayqkPaeFU6rv79+HygyyfEQy+OHVKwDhwAC1dGAyuOemkK3fXP9XeAQV/
uL/x0pKSiT7uNAyYdlWLy2gh7xoz7uZRo4GgAXZM/jz1pH9RU892wt6E+uf2tt9MnJz1VIpRwvT3
hoYdMVgjkeUaj3fdKafSQxW65GD+mtnzT37v7YbIQFhTf7F/z39PmaEXRn3UMAH2xjET762ZTtMT
sNCS7g7kIThgv0Ogqx1+aDh4TrLshGMxsFZhDtdufa8vHodS0/0Fby88p4hjmBgIPjX7NHix5Z49
26DQt7ZsuLh8pL5WQYXAxpymhtET1r43YfrPT5pHR1ESVoBYd6DmWDuOCiP0J+L3NXyM2kraf81c
9J0JRjMJwyh/3t3TF+Q7Xbds3QAJ73Ye7o5Hi9w279cYMsVfgYBAQCAwjBA4Zq6G0WatI5n6T3AX
0E6QCRd3ASCwyRhokkU8g1smlLu5ZQPYE7m7ER+gN/YONAzEJvqtL3Y+0Ux2T2Tpam73ZHV7L66p
yNLMgM/iZ5Cq8XJFZcmDTWj+Q6kUfI6z0HT2Iq0P40dCVznjEdXEhPUanHrG8509KVJ2ktezwjjO
aSoESzLlpfceBldDgh2f9kSy2sMbRSIT8nToLEVpjTye0v+0tsJ5UlAjT5afqpnI/AxWEiz0/0yY
+G5fb2MsllLVnzcd+s1EXC+hgciC3QF5uj/A+xlGvvSDkaOf7YCHcq0rHjscj4305GQId4VDb3SC
e4fD4JGpM3g/g0oOOp0/GV9z+ZZNoPkzrYdMrgYOD3Wsx3/XxGlMDf40jAxGHVyrzM6BgYdmnl5Z
USQ293ataW+GuuCDq0/OXsj7GYzvzimzn2s+sCPc25OI/e+B3SvHp2vH6rBGFd5ovWfaXOat0kUR
XQL4E7R2JlGSXmk9EIXdH0mq9Pi/Me4kLidNXjlmyi1b10NcU7XDkZBwNdLQCEogIBAY5gjApHhM
XQ384jgN9HGTGEu0Y/CfPYsTu06n4/TDoF6sJuBdWOgnH+TWnmzu+vGESj2D/NnYG64nuyRw4uGS
EQUs69ujRlw8ogBck3yyKsDSeaLaQ5dAsPaIqnFfMyX6oGFjyrNyJMVk01kWEqg+egOkdVzOVytG
nFNU0BCJ+hzw/J+9fBX6FqRS1MdkMEmRTGWMCnR5JoaXu7vpI/7yshFV5HUMgzv9Fx73v11ZecPe
vVDvcx2wOJF2NfBBnKwQXFZSki7AUTMCefrDuiTBb3yMtHqAHCtHPt/RSvpdm+YPnFGUXfKy0opb
xk2c4s+b7M9jq01wTARMLpS9qLTcZMg54agw8lgD+DXoECC01txnmvfRrNOLy2vzTUtfTIpDVq4Y
Of6WHR8iSi37Ta4G1AhAgVYVo2y10t0RkJfuoH+tnrB/6RUNoR44tGNXsNIbIMKhoAwHSJk+ghAI
CAQEAv8ACBw7V0N/BNdGuB3fHs0ds6CGmF1xCqYRQE+GfQQLiLBcsb4vBGb8yRarq/FESyedwZdX
FsMbjKwgPLKP93ngH0vhCTBgcCD02Y4edAvIE3YKHR0uZF88wJObGMy8XDF4fIU8kMmnIQ36jPV6
4J81w4jXRyIvdIE+BAk0iRl1oMwsklFAhgUFNdb19ZB0+dwCzokyqmN/zyssvkFqAL2b47G9kcj4
9B4KaYgmzbR5wQT2JuCIKGwMQFnYxWACByfegzdHyG7C6YXpUzWWIgGn805u3cLIBUjAqEvzC7M7
BMgG4FPkLL0JWaAhAJiR/nd6FFSSTisybWmhNC7MLYRc7JONXa3wQVJutwi9H6h0XiE3vLmCSBpO
G9+lIAHeLoF/Fl4W3RPqeaP1AAqHAAdVMjRnnIIQCAgEBALDEYFj52pA69GWS2Vu520Tj/zD5F+s
KFq5++BAStsdib3XG55XEKCwJlTtD3Agg9jgq6uyPyIDJ/yE99ZQBHyLvVGwprFdA9Ft4UgfWkfq
ZxjLLaa+giyY5VG0OZCpPzPZYMLlB3CVwDDYLF0AI5zD2DoA+kT2xmJ7o9H6aAT06QF9dHNCqjAE
Gn8hEZHUbY+Rqv9FO0oqNaxZbyo1AAcIgF+Tpvm5ExiWgvC6r9+voCWDQ6AS7IOkXQ2w2cSRKKav
UWQUhASHLKWIl0OWp7JxZKQ1RkKok6rVkC9hZOTbJwA42GVS5WBHFnAvI1unAXqQBaXxPx/29vdR
H+KxA/XPN4Nph8B4oBTtSikKYAIakhxOxLviUXZ+E6uDdE2rHOzX4QEeLJu97yQJDnZs6+3Y2d+1
N9S7N9xb39+9taetC9+PzToSePUFLRAQCAgEhisCx87VgNmVWke8HnmATZAvlBWtwgUMeVVLF3M1
Xu7s7YQvYElSbdB3ctCfWcH2cOTOfc2wejHAWyDdD8BzoGgj0SegVpwTgJpnKI2JHI8taesT7I5E
/uNQ0186ukL6OgSIIz4EkSsrELGzLpAOvgj1JzIrxgdu/R/JhC9uYZwIK8o8RsoJgOWWoKT1EqvW
lYinc1BDlIAnUu0C8EDBoVjEXrCg6MHIBY4hDjPUB52AAnvXB18ZBR7kssAISlKILOlSdyJC9WmO
hJuj8B4TFCWctGfwStoIHYRdj8XhbEra1cBOQS+t0GW7XoUnSGxQ2h/uu3PHxj8d2Nkbj6bHGzJj
G3B8Ak2dyKGADGVFEAgIBAQCJzgCQ7QBg7UGpmZid3GaPqpwdWXxKvxSp/bH1q7/mjTSSTZZHm8l
uyeyfHVlliWNR5vbv16/n3w+0rATMp5Dge+EnpIXOKMweHKe/5RN+GYBNSEm/chijClFj1htlYUH
jbNNY59s7/hqwx78yIfOgaIckjbRB/rkLQ4GF+XnT9+8GTMzKzHMD3m2ttQJ5hUqhTLpipGiT9Jg
rDKlmQXAoQxi2zR4DzadA3riczwE+/LIQ9prz5IWSChYQUGBdB3Fkjd4FOtCAwy+kS0j5cnMh0qp
r6m3KC0AP9ZK9DkpWFQAH7QgNGkyGTOoLF0xIkVAsibxB1ERItRKs3fHQABIQc2JWPKXXFY3NSxf
//wAHsIADxK6AFNBzvi8wlOKy08fMerCqgnjnnuIplvKpqUISiAgEBAIDEsEtGPnasDUjPM+sS5H
h8WSoiB8e2p/LN6WTLze3be0pAC+iAUf7Qb5Llm6vNy68f9WT9+19fvoYnqB07Gionhxft70gB8+
x8nepN0Xxa9ukKD/0SNptTOUpllguQwLYOGIoV0hRsOc8V5//1W7G5LEg4EvVq0YMeKMYP50v7/G
52X6tMErlygY6sgmhBjarMIxEU0pLYgV40oG5Zfl7mQi45dO08rBbg79wiaYf/hgeToDrXKWhqQZ
gCJWlnB9EqdRDBUjZrWPX0Excgf7i/pkMdimIqgPWdWwulf6OoEhIV2oyOVqjuKbID+efPJlIyek
M3KksKJP1Aq+0EWcNg6kbT3tX173bBSh0HxO1/JR084sH11bWFaTX+w11nvwc+a6o8OVzFExwSYQ
EAgIBE5sBI6dqwHtpLYZrkcXYDH5K5XFd+zD9xKfbusCV+Pp9m782rMsXVRaMCLjx9N/vP8wsQAq
nMT8++yp5OUOqwbdsAEPgeyi4GqEJcADpjkNG6EvHmhxqzHTC7fDzkVGQcj7yaFD6GeoapXbvX7G
jDHZfoMU9UGPAeu1isc4+2dRFHKoJaM2D3Ph2xsFDkcvPDFr2pZQ/zR4W8QmbA3365VK0jjTgQNi
ns0IZMhAS5mROFjCKK9vA3ygS5J2heGQhG149ECDW5Hhsxa1waKAvmNC3CnbEiQDLXcahDQvKklc
EOp+pTOk0T5/czQE0G7r67xMOgJXQ1/V4ERmkszRSWN117b19GXXErdv3TkrphRkOZTaFYNvyUOL
UOAnr01lVitSBAICAYHACYzAIIvBR6A1zJS2ewpDEveVilJ8bpel57p64YWR37d1EsOvXV1h3T2B
c6Bv9/ahzZalm0ZXZvUzoOqPQgPkjRLcfcDFCCMgiS6FVW03HKYADSBLhtc7iXU3irC/Hw/Afj8K
xKsRwE683tNNrLJ6Q1VVVj8DeD8OkyOTaCxV6xsxIA3PBIC9zFovMbGc1QfPbEF+PuV/pRO+fmEb
4AfJiBlOVbpc1byrQR+pwUJzYq1SqD6ocLqxVh5zfEFBCTGf6jv41mv2AMckv7ft/Ss3vbNw3Utb
+ozfOqErFvoSQvaCtCFkrcXEgHaaoJqp52nF5YRffeHwXlMZc+T11v3LN7x065a/P7p3q/llEKNf
zPymGCLJvA0957XmPaiMpn5z0uysfgbwfdwNENGehfGQzYUyVSMiAgGBgEBgOCFw7FwNYpWx6Wh6
jzbAm6uLC/JAVEcy/ueO7rf6+kFiucd5fon1Zc7ORJL8dAjOzqO9/Iew0jrAGY5ftZBvPIBHokgJ
i0ElborFMsFGjJP6EIr0AboF1gD+we/a2tB0ma1vXyoVB3uD/9RRpg9zpSWAAfvvpkNYEItr+N1u
LuDGBmioZroghIlaMmrSjFL/UlpG/BL4oPuhfZEBI9n0tz+ZfOhQI2W7uLTclAeGUG+IOZmP0d0i
ZONTB6MvLKuiX8jYGe55E340JFt4vvVgXzIGVrbI4TwF3zLFoElk/QBgsfQUzaZX0ATtN3hjJoXw
eAdkqakUQGQOn68aj/yq+mFP2yst+8yZ6diPt67//YGdd23f8PCej7g3XaEeo68H0Qp5TCqB69MF
R1Cxv9RR9u+7PrBjPekCUC+JmykiCAQEAgKBfyAEjp2rAaDAJ7xQnmnqP2Ksrq4spWsV1+/Zj/ZN
lq4oLzEdZiSiS11OD1gXODoqa6/19GZWB3b9e437PgzDL7OTpQtNs3wyi/hGVPN0abBYswJ+VEDT
fn74MHz5O52HadqN+xrrYD8CFEPrm86FMxDwW/UEBPW1Ljjcag1Q9ubGPeRLGMQmqSmLPvgaCBob
7VA045fhQBgxWkR+WvKVFdXlsK+kqRE19eW6D3rJT56msyUJPobxla0fNkXBC4HjOdr1o8fzufib
I/SR2r7v0PxTNnseXibQNXn54G0Qw69eW/f3NtgjMIfueOwH295Dsar61dGT0mcw0Y0gfpiZ3xwz
DL85FT9MjnpqTQP9uMLBhdNHVJ8KCxvobaSufv+1+v4svXPP9o3r4QfPCP4rJ83mShvIf4IfQLQi
xWlZWHPCz3OBSpr62uEGk0Ajclfdmy8dqic86DxFMrrPYBR/BQICAYHAsETgmJ3VIJM6XuA459KP
63E/w2STIMtIwa0RmFIJXrJ0dlH+jaNMXwWlQF46oujbDftC8L0pOBKBJdSrzD8mQtngoOUFJQV/
7ewGnv8+3AK/hP6tynL6gS9wMl7v6b3rYNNb8PPltHKy4tJt+RojZEFAs0R1ooKlL5WU0N89h82O
M7fU3T56DLw8AisicOrz/sMH1/X2wffHfIrckwTDlg5gWpYVl6xqhYd47dHmQ+O87u9Wj/aRM5hg
+db2dN99oBF3WCCAQSVQdJtPTVa4ycsRqrproH/5ts2LCorgsMj1o8bROohbYNXW63A8NnXmhZs3
guOzsbdzzoY375o07eLSCkiH1Zc1XW0/3L39PdiegDZq2o8nnTQ1Lz+tMVDEEJpbb8rHCHpUxFfL
yBkk4b+nz32n4zB8YHR3qHf+W8//50lzllWMhrOQ4Pq81nboe1s2NMAxDhm+2O39Yc0sTg7oCdVx
CRkkflEMPRIKRTq7HH/GDNwUbV+490vvvnhm2Sj4+OYNk0+hHP8795y5r60Cx7ElEpr/2qrbpi9c
MWbaCC++O13f1/WzHRt/u7cOO0XTlowYvXzMtLRcrIe4EZhkrxnygJsIEtJF/2XU5Ad3bYTEZ/Zv
vWVT4S0zzsgzXpdd17r/3i1vPX9oZ/ru0NTuePZ1qbREQQkEBAICgWGFwDFzNdBoEpsdUtVXu/uI
WaLvEFL7BHlk9qV/jRgUKcs45kkBhB/yuKys+LE2+JUvkCDPzQucBMsM2cI9Y0e/2dsHDgSY7hv2
HfjRgYPwTim8bXEwHg+TZX9o5O2jR8KaB/110y0DA4vhcAML6GSY3AWa862KisfbWrfgcogEPsdF
27eQdPq5C/zqxWOTpt118EBPMowacuHOMeNe7epoj0dB71sb9/x0395J/kBSTR6MxeAXWIARln5u
GT0Oflf9lS5sHZzlPL8k/QHK+fkFPlmKgExN/X1LE/yDItdUjoJfDAGC/PYHV5lBnl9a/vDU2m/u
2AynQxsG+r/40QZYmIF3QOCnR/GlCyPcMHbiDydMNWL6X/ikA/F7LMmmKPLgygckmhprYsqIjPUH
/zrv7H/Z8BostOyL9H35gzUOTSp2ueFnWqGD6IApdLhfXLC0kP+eOmSBJ0Fd0gyZNIGMtSy9Nre4
HH4XPoS/OJ96+mD907haoF05Zir1J6bml/xl0bLL1q3uS8Z7UonvbV7zvU1vFLu9sMXWh9/Ror6L
NLu44o+nLQOvka9c/9WVwVuPvQYc9J9e+ke1Z6w+sP3gAJ6Nvbvurf/a+s7EfNgq0g6G+2ilMJZW
Tjvt8EDfn/ZthY7Y0tX8b+N5x4vXQtACAYGAQGD4IXAMN1DAsBqTLEzR+iYCTQRcSBZO3UYKbmcY
/Da4XV0OBhjYsNTVFWljbGGf5PO+MX3qFJ+XChzQ1LqBgZ3RSBifetUl+cGNtdNvHTny9CB8GRpq
lP4KP1JqCuRplT4ic+mwFPHG9OmXlhSjBaLP0GiSwVdQq1zOV0+q/beycpmsxltcDfh10LW1s2vh
J9FJwaia2hLq2xHqxxdN1dSiYP762fN+On7SYviIOD4Eq8+2m84xlLk9/zNlugeNFtlEgBo1WOEw
zouQIvoDPactkF8bOfbNOafPDxKxYGlVtSMexe+IEznT/HkvzF748ynZbBgw0A3RIqMAAAAgAElE
QVQLNJM2wb5emwJ68pLSyg1nLDuP7qTAWoSWao8PxPF9GWzX50oqNy35wmzjlAYtI2vwuhCF2l42
Ik/6hfQp44MfKoOlC/w5OL1RBD1ur+TcirHvnbviYjy3QYpraldsoC8OX/cClVTYjLu+Zs7bZ19O
XRMmFgnkJ2CaUs0RbBTWyKeW+fLWnvfVeSWVmK6lYqnEtu6WbV0tfbB6oaXmFFeuWfq1++ZffGYF
OUqiqav3b+WLC1ogIBAQCAx3BMg3Co9FI7aEBvbF8I3UdDA9E6aTLdRIj3t2nv71cUsW7Di82N2D
IjVpSWF+Hv8pCAsrmEoNz2q82dd7IBaLq/BTLK5pPt95hYU1xi99wKcsNobQYMND5IVFxfSZFV5g
eQ1+q4zovbSoOH1cgJO/YyD8bEd7PfzWeUqFn2BdlF94cUkp/ULGWz1dfeT9lItK4JUZU4NB+de7
O9d2d+6PRmNqqtTlmhrIO7d4BFyp7M5EfD3dSZEkWNWw/BBXcyz6XHszHNeA5ld7fF8og20hNKAv
tDdTf+CM4lL45XFOzTT5YW/Xax2teyMh+NglOEw1/uDZJeULi6wasgIvtTaBeYTo4uKyAu531RkD
EC+2HqRv7iwuKbfj4fkz6W19XS+1HNgd7u2MRvKcrsnBwvMrRs/O9nsiLzY3Qm+ChDNGVOcbew0W
gS83NybRcktwAqMw4/vlrdHwc00NB8J9qqZW+4Ofr55UlXEks6G/69XDe7f1tnfEIuAYl3n8pxRX
Xjyyphi3YLKEl5p2g/cGGYvLxxRk1EgLvHxoF2olSYvKxhZlyHmrZe/rTbsb+7vgNEaJ1z+5oOzc
6kkzivXdw7549K2WPaQfpM9VT/LhR8ZEEAgIBAQCwx6Bje9vPmauxrAHQzRAICAQEAgIBAQCAoFj
jQC4GsdwA+VYayfkCQQEAgIBgYBAQCAw/BEQrsbw70PRAoGAQEAgIBAQCJzACAhX4wTuHKGaQEAg
IBAQCAgEhj8CwtUY/n0oWiAQEAgIBAQCAoETGAHhapzAnSNUEwgIBAQCAgGBwPBHQLgaw78PRQsE
AgIBgYBAQCBwAiMgXI0TuHOEagIBgYBAQCAgEBj+CAhXY/j3oWiBQEAgIBAQCAgETmAEhKtxAneO
UE0gIBAQCAgEBALDHwHhagz/PhQtEAgIBAQCAgGBwAmMgHA1TuDOEaoJBAQCAgGBgEBg+CMgXI3h
34eiBQIBgYBAQCAgEDiBERCuxgncOUI1gYBAQCAgEBAIDH8EhKsx/PtQtEAgIBAQCAgEBAInMALC
1TiBO0eoJhAQCAgEBAICgeGPgHA1hn8fihYIBAQCAgGBgEDgBEZAuBoncOcI1QQCAgGBgEBAIDD8
EXD2DiQcsjz8GyJaIBAQCAgEBAICAYHAZ4lAStO8LofbKUPg9XA+WtfbnDAl8dmCFggIBAQCAgGB
gEBAIJALApUu7YKRrkmVeQ6Hg+d3rh1QXgg7+aSjpTVNAncGrhAoYfZujlb+8S4v9D/eCA8uX+A/
OD7HO1fgf7wRHly+wH9wfI53rsD/6BC+KJC8SEpCUBSFX9jI4awGQA8BrowYXBXqWMCVEYPzH+9c
pjYjBq+Rqc2IwfmPdy5TmxGD18jUZsTg/Mc7l6nNiMFrZGozYnD+453L1GbE4DUytRkxOP/xzmVq
M2LwGpnajBic/3jnMrUZMXiNTG1GDM5/vHOZ2owYvEamNiMG5z/euUxtRgxeI1ObEYPzH+9cpjYj
Bq+Rqc2IwfmPdy5TmxGD18jUZsTg/MchNxaLJxIJjSpsyM9hPcOiMY0a5YfBX6H/Z9tJAn+B/9Eg
IMbP0aB39GUF/keP4dFIGIb4p5JJVVUtrgZZ1QDvYxCPiWUx4miAy70sq44RmWVZFiOOjCez1NGn
MJUYkSmTZTHiyHgySx19ClOJEZkyWRYjjowns9TRpzCVGJEpk2Ux4sh4MksdfQpTiRGZMlkWI46M
J7PU0acwlRiRKZNlMeLIeDJLHX0KU4kRmTJZFiOOjCez1NGnMJUYkSmTZTHiyHgySx19ClOJEZky
WRYjjowns9TRpzCVGJEpk2Ux4sh4MksdfQpTiRGZMlkWIwgPjVnYiasBfpPFdeK5WBYj+FxKs5oY
cWQ8fClWHSP4XEqzLEYcGQ9TmxGZclgWIzJ5+BSmEiP4XEqzLEYcGQ9TiRGZclgWIzJ5+BSmEiP4
XEqzLEYcGQ9TiRGZclgWIzJ5+BSmEiP4XEqzLEYcGQ9TiRGZclgWIzJ5+BSmEiP4XEqzLEYcGQ9T
iRGZclgWIzJ5+BSmEiP4XEqzLEYcGQ9TiRGZclgWIzJ5+BSmEiP4XEqzLEYcGQ9TiRGZclgWIzJ5
+BSmEiP4XEqzLEYcGQ9TiRGZclgWIzJ5+BSmEiP4XEqzLEYcGQ9TiRGZclgWIzJ5+BSmEiP4XEqz
LEYcGQ9TiRGZclgWIzJ5+BSmEiP4XEqzLEZk8hgpOWygGKyD/bXURKOWArnwWIp8atFcdMuF51NT
2FJRLrrlwmMR+6lFc9EtF55PTWFLRbnolguPReynFs1Ft1x4PjWFLRXlolsuPBaxn1o0F91y4fnU
FLZUlItuufBYxH5q0Vx0y4XnU1PYUlEuuuXCYxF7TKOKRA59WmUyxwcIh7wiX4F/y9xWrmMT5+sC
iTQ6iOgs/KihSb0sPINIPLqsodaVC38uPEendbr0UOvKhT8XnrQGR0cNta5c+HPhOTqt06WHWlcu
/LnwpDU4OmqodeXCnwvP0WmdLj3UunLhz4UnrYGVWpanrMjL+QMEQ60rF/5ceKxaH2l8qHXlwp8L
z5Hqay031Lpy4c+Fx6rHkcZZXYq0Ik9Z5srqEHDCGT8juMxBSKeUdUjrHpBj9XzfJWXpt2P7e+P3
vx+9bSD7i6zLRvqene2SJPXh10Nfpzx+19tTlV9siq8eRIVs3pZJVMRcOIP/jtrAj8Yo0bbIBQec
a+aAAqaQTGpt/clHP4zcBnIAHShOMaIElcaXyIWH55dls7ZZAeUKZOjP5RmkHU8uumXjuXak56vB
1Kk7kkYF3F+7ujgWE5kLvx1PNt1MwiGSCw9fxq4unoenc+G348lFt1x4hqrPUPmF/tALEAAH2h08
gBbaDisLG4vmwm/H80ljY1ml54k5niDWpS36W19sRvDfK+hLgtpz6/qXdWNGbZFn4yKPF0mpvyWS
/34CKVojT2BqtmDRLesUDTxuV9t5vhGS1N4UKdtEqgBhn6Q/1pcLD6+XRR/WEIPngZPz/r0aQNBe
ebf//A69pQ/MI8hE4p9/Pbo6U1U7mbnoZuFxOduW+gGHdFCl/lhq+4HYqfVkOrWrK13ATJn45TeW
5J8VlJLh+KVrosRKyo/Veotbo8taiamiRRkmFt1o1Cz+iPF/4BSAFI1Xf2/sirdjtibbpD838Cxq
mKNwGtR+VcPt3HdhHu9nQNlggftHn8v7jd/mbIeDWlnZQ6q5fqJf+5z/9EoHuXMsNZOJAJCCfxDo
lREQpfeXpIsyFWZFDGJuMXJvb0nmp52idAmnU64qcv3oLP/NkMZgYkSacSiUUbWuOdPWkk6jFsFH
w8PUZoRFeLbo0wuCD8/2zMznfCA7HezSebFHw8PUZgQvOXfaTge7dF7y0fAwtRnBS86dttPBLp2X
fDQ8TG1G8JJzp+10sEvnJR8ND1ObEbzk3Gk7HezSeclHw8PUZgQvWZJvrqV+BqbSWdTIl+dU6bPb
hVVO6mdglmIzfzIljfLpvyxL04wp2mmdooHHIdFavPDsRouACKY2I9Jyh0JxOmAxJj9rut5ueekp
vhWMmbRbcslBKOKQqf5FHmOKyyoHyjK1GYHVDxoMHNJMihT0OeZP9vfNd+maD65/uiShTLrJhT5M
dHqwCbX57qYLg1eNcY2jfQ+cjJkKYWozgqYP9crEMgLGm27FwMp7bqsmEmmuRTgrwggLg01UsVvV
eHKefwytO5586oPwLZuje+JUhvKVWdm3Uho748/tjb2yN/YucMryuGJyECQpNWXWzZBiBOUxoo1d
ibQoyGKtAgJ46FVndk3Fgaa930ZHHwpqb4s9vDX61I7oMw0J8iQA96RzWaUxEJHFPhg6pMdlJq+Z
J60t/e4q5DIGWnYw/bNpxYozIlMHuxRWRCeUUcTJSKhcASuPoYNd+mepv6Ebp34aXqYwzWVRRtB0
oT+P3uA0g44RmfwsixGUh0UZQdMF/pkY2qe0t0Svez10X9Q08qvKnbWkyOIR/BMV4aFoQy6DnRG0
Fhv8xxURUUnNOkVD8ZSkL4HCvMHk2+uczmFVMyKdZ1AsixE0h0UZYZTAv27Xf0wBg0Xnfz2jH6KR
xP9rQLuzaq+x+sKKM4KXMzjNilBClSkOyf7E7+qiT+2KvdOWogKCZb636ZoT5YRUS1mWboM/7AC8
36xLQ5n5jipic/W5GoozgbTKXK6sCCMyS7EsRkjSrzeHrns32k6YXU6iB82FFFv9jSZnVpGRQrwB
KgjkAkGle50XFxFeNfndVwfux/TU3c1q1wV+SE645GWa1lfl+3OtKxlJ7owpp8Mmi6q+siNRW+5y
qWrd7vgdNf5vktUYGB+rz3O8Xxc6uxm8Nucf5/imBPD2iEaSf/kocnkHOG7S6oV5SwJSV38yGXRN
8MnR/vg1W7U5higY9LXF7lUzPVODCqqrSt3h5BMfDKwMIQS1xQ70wJLJdbg/QnSWpIOHYl+Hu4e0
a0m/fw1u60h+NzRQlWTH03N8n690EFHapr2RU9LbCvKTJ/u/WI1Z0XDiL4e0c8a5nJHE1W9F+sq9
f57tdqZSD709cBM4Ug7njiXecofcemBg6vZkideR1lZxNJzhL5a01l61uswZVKQ9ewcmbkvePNF7
4yR3EcG7vSN+13vR+2GMuZC5TEq9uic5t8Y7Blw4VXtn+8CquPM/aj0jnNAs9d2dA4v3pmi/3DzB
e2MNJ2Rj5H4Vwbyn1v+NSkdbc+wdyblijBP1j6f+8uHA5e3ay6cH5hPPMFjm7fucC/WXnG/P8y4o
ImBKUnd/cvXHkau7iCfCjwEdS/KHjgp6hQRG0AFDcMZEGgWGoabzdfG0nZyh8gj9KQK54DlUbHOR
KfDPBX+3s4bcqgebE49E6HIF1xkB5+VKtE521VqWIDRtSYXvz7Nc+uwU0ySnKz077UhJ7mz3e7d2
x1TLFB0++zBMj8R3gT41gi/g3HCaZz5ZOW7viH3v3dgqknvzJN93J7hHEIVhk3p/a+yGTXGp0vtY
Lc5xW7eFFx8iD+VBz77T3PmS3Lhn4JTdydoC9x/neE0moJ1USmuE2ulwMmq3/B0zyf/A3tDKOFGS
5SnK3HJnhSJXJ5JSK1ruZWXuB2o9Y3zE0MRT6+ujZzcSi65poDY3D8fuei+G87Bd4HCIhJNX74sT
fGIrxvmfmI7NXDDZJbXEMFFRnp7lPa8SJ3wIMMPf92H0bvJwbjs5o+3T/rg/8cVRjmBPsq7I/Sax
U1D85Jl5baPiX1ofXQsRDhPbdknK03O9F5U5vaT2aFx9vz6yGJqczbZe8Gb0VJMxIiAktbqYVteR
+GrcC306tsIh7eeeTemooFeqElwh0M7Kre+I6csQsazcRcfznt2x+0EiZUglr14b6ouoa6Fv4ICC
Qy4C4+126ftYitSlKVUBaKsMjkesEA0eDUG3UuWVpXzXujO87Dbx+pzLFwQr3us/u1UaWagEnbAq
RYatJHkVTfYaomCFUHG+vMhXZUiDvZWioPPfT/M9+2pkrSyfVYEV9XelVsEIM0agP+CodaglDjnf
7bhhoq5IAoCXlQ2fy5tP1qxQniKfPNHflRcpJvudTy8OXlqgV+MNuJZPJrRCVudcCjZWcugHV9xy
tU+Btvjy0cvOZ9riQ4JS5oMicpGPdDskRNWbTwrcNT79LDKi1H3fUkV6ceB+mTI7LyUDF+tT5NOn
B05HCoPTqUD06c7+y/qkLELOJ0IAMY8j6JaDY7wTaDFIcTuWL/BvfW6gusBQAxric5Y5HDvO8sOz
AQsA5lWLAm2vhtCFgsAGQy7DiDKzIhbCEmXCM9NJzfqFrxeS6DjmGSw0lZYpk5cDuTSaY1k7mXbp
vFi+XkgX+gMIAn86QnIZP/gAQh6K+EGFtGNBKTyKONMzoSEz30WmYjo7QRX87KRpO87Jfr8XZE7R
VD0QywiYgoKu+bQiSRpR6vn1XHXV+wk4nXbXVHx+owE2qSdUe59waPlbU063GybGBeNd0sEY5N4x
0T3GjdPN5p6UVOBed4YvmwkwHnGBj1XN7qO02wPZyjfnuVeuo1MVREnwKJOCuE1fXAQVpZaN8T1b
m9YNZsKzpgfq1FDtfvXm6Xnmedhz31IHzsOGJPzL6qWJ7P7l5sxVjdEfTMmb4ZScAecKOb5KUj48
J+9k3XxhMZjh7zrPWfF6aOWABgpkn5yfD98tKz9f6C2S1N9tSYwrwcd4PSjyiFJHNYOCEIO067EF
gUtLDeOHkz9ajTf6+s7uyGJbzzgp8GOTMcoGArgZPA6gAI0aCup/qYZmPS0sLJr9rEaf0ZXwdVF9
roSaNG11f2ptkqSwDgBJydQ7+xL72+IvGaVimvbyzsgWepxTTb2yK/p0pwZOHxlk2jt14SvWR/aT
ZamzTnLDqiBb24djp7A8tbEhHjKGV0yWl5S76d21ZdfAzJdCr/SSPLfjS+Ss7GkjcAg0temrfbRh
UyYHPr4guOa84LNL/KcHSR8kEw/vU1eM81I/o705esXr4Ve6UFRRhffJgFZb6tH9DDX11PrQvQ1J
JhHX6Ix+xLsHQlKjuei+QGDaAixs4VGSdh6M7+xP/vmw8m3atfHkL9/q/+ku8L3hlnFeTwy+Xoua
+t260C8PMgdbferd0O+aqF8pTy5RJMXBCelLC5lKPBijO9rbotetDW8Mo1JQR41f+/3WGDyrQEiG
k89sjbwhKSAMQ3/srOd6v7sVlUmq8pwS0kIqB67wjw0vy3jieUAOjRKR2S88P9DsH1+W5+HrReSN
f8BPNWEFqSgWZQRN5+XkUhZ4sgZeNyo593qZ8lRzoT8gzOPJolmRp4k8/z82/gFZfwiCZuojh0AQ
V9vJ1DqlwnVzObnfk+phfbLNmH+gBD87eRzp+/35Pu5+l17eOWCeormnWFN3aO9sDV+3Pkp3ooOl
zhWadpb+yAWzVv9Zb0XoDIMHRwbiz3ejSs4C92/g5ITsuKySTDfxxC87pKdnUT9De+fj0BXvRg0T
4KmlXQzF+L4GBHQciDZGk51F3jdKpV42UwKPMeWS7RPlP6dTPwPUHvju5lg/KT1jmnuJdQolMzzM
wzCFZq+Xm3mIEG7+UQcoWqoG8u+Y4ad+RjKc+OW7A6+00Tzlm3PdpB9182CdnL2Qrn3/ndAVL4Wu
Dkmrm6PPwToHCd0d8d9tjsHDMwZdN75d4e9uYu3yLHE4zyV+RhSOc77Ye4uxSD8iDx+DOduaQNva
qH4tbYxs7YgPFoTS+BPT8IlzF9XW/qo/8etNotI57oRq+JusJi6Xkms2hWFlAgK4unqmLK/uTizs
8syAk8NJ9d76+FpJ/pBmxlObo3KNrO2JSGPA9Qi4rnEbHoqUuvvt6N1ExLKRuiT4s7Y5Ij8fubbU
OcGr3DPDPZ+6DnBiFG66hGM2RrVNsApHuyRdLk11t8T+76bYI7L8mzK9vXs71Zp8qa49tRQPlMgz
yhzjVN1r3bhp4PJOTeocGFkSXF5kuBhpYYRKo0G7wchOp0vR7ujUj7BpSyq9PyD5h1uTLT6H1JPs
lnApqJitN4BTsh22MFJSOH71KLwb9+yKXN6ekuKJFdUe1FiVlpS7qtJCnHCr6UJgWQVuNapmMvm9
jeBiS7vrE3TPCByju/fHl03xVLmlSH/issaE5HP9msiRgp41F7n3d6XebYj8eEdiLU2k+rNWMILm
Dn4F/IGf9gIlaHH+apFAsyDRwsPSLfwsasdvl84KDkII/RnsjLCDyw5nu3Q7OXz6Pzf+14/z3T3d
RU5iqmtbdJOjw5NIfRiWlpYpRaXuf1PR1ejvSrYE3HBTw52DPGyWsuAPGexUI9zvF5L7fffAj3cm
1+J9ClO0mp6iM/FH0VK0I4ZL8VLq5DbPdWUyzEXw6LVyU2jlx8odpUpBoevuChc9YYB6yPI9uxPL
54FmyufGKlK7ewqZcfc0whsN8m3MBMSUGkk1TIDzGo+8khoBi/40StSQEsmffKQ9vAAPTJ41yx/v
oakZV6+Cb6sARM2wg4CPUZJLWiKpGzqTUrnHPIXCPOzEeZisTGMZVh0jMDVbYAxYl0wfdwGiu9+K
3AZQdYTe/lz+6T5YEHJeL9GGgSLG5LwrseZkdIboU+tacJqotFjqR/uSl5RiVuPB2NUHjc0smut3
6O1qidLukNx6u9amtOrn+5bkO5YGlPMn+04u1w2ZWW+wrRGwrWCM1pAMYoyy2JG32tX51YqzwNt3
puPudyJ3M5fOLC5LjI0f8+BlnNzLrrRJ5JpvrD/l45le4xlXkh44yTs7kVrVGH/EABDM4G5wd/Vq
DLEQ1WAfhEQVKR/+up3j6PqS2/nv88jo03nlfHqIGqJxdTtcqSg9l0Q15Y0z8s4qYPeTngcLHnCO
BjsgmXoLzm1Q/Unmnt3he7sdP57jpfdAMpV6hEDWhr4o3qvzp/vZqiBE4SQx2GsS1I0d4LUguadX
leixKZpDr6RpfILVxQEGEvpDRKKm5Su65lWjvHeNShcNFruWGUevmEtHFzl6o2T8RVLgMuOqGgjR
3+6RMoQ4l0n62gqc8+gntefznW3oox9WH4j/udlzFX3UUOQxpU74t2ai5+G/9X8dVqEAQ+CnSFKC
FWeK8zyQyGCnRGZZnp+XaZfOKqLCs+pjV9Yu3U6m0B8Qg8D3ix1WPI8dznbpdjIhnSrAiEx97GTa
pdvVdWLrPwU22onm0abISjhvwQcFzryr4GrAcv0Mkr6vLRmeYKzXQ7v4YIlmvd8nke8RRCQvWSKB
LWmcoinyPP5ELE5NBLoYEOBMwHyLJ+Tcry/0kQVlU92QVdcS25J0w+bCmCr36gI61at/3qNKLnsT
AGpQtbP2KW2fS97dHvldh/sqeIL3OZcaT7Xp8UMVMU5xtnXqD5/3N8bIWUN5mfEKXpYpVIuvplXz
rQHalEj0MPQ0LCS+AuPSjbtWD1M+werdLvV0sEyKY6ZX66P6s8mZ2TEKNb2SusbR7gB7BAJZ1ZQw
Vm7aOuAEBkpk7QL6jin+myelTyxACgaqKqXBthLF7I2RcxkB4aYPI9+oDsDjbjBITg7Rj1ZQIfRK
9eHU1jNpClxZA/lScIIoHSWqUP1Wd6WiErrYYyZ4r60fgPUAZPO5rx3vhsTTJ7laXxwwCqLjbAxT
lkbqo1XSxaR46lBSwkORauq5nfE4GE5Fhq/UhFLquwl5Ki1HBrEOMe0eSJflm6f7qZ/R3p14cU+8
rdDzA+P4xbXk/oz2Jx8BTg7Z3oj6SEvykXekyBleUHhEtX9HX2hqg1rm1wfFzr1ReFcclrfyXLB2
oH3crkkluhJjYe2IrMRN4FYdaB7UYXgkHHAMdKqDET2ILgsx2wbG0e74X1pU2Lh0u6AKLZ5QG9Pd
AjaeIoVVuWTY2DK8XYiDTGMUZhMCDFgKZwFaO9/Zhj5M86vf7/+4ynNxpWPGCBc91QUll890f30j
uCw2KxNEfPrCZKaT9HtM7wVgoKIoA+OnhCUKPJZ0Xixj5hN5mi8r9AcEIAAmAn86SIbJ+GmL6E9B
3nLP9XLKdHrAIde3JKPT2Tuu2oct6oQa4x5IN1CDrRPa9caUg9GrPwh9XOm+uNI5Y4Qzfb/XuvB+
p4FOPJn3jlGDfnumo8oj86ifoe08GHt6v3rZqX5cvYAj6qiM9r/7UvdNdDiD7kvAZOG6SPwmsMFJ
NW0CdiXiMFk55DyJmAB4cKWtyNQB0o3ZLB/a8l7kwgvMX7lgWlFC0Wjbi2HfqBEbdn2N76t56pbO
1AZDTpYplNZOrxaBLJE8OdLM2kqPvmMSSdXJsu70qZLf0H8KbF5gUA8mZP0ZmU3OVETmFcqygCiS
rqQpoINDtzjFpQ5Lu/7UodxI/IxkPPX2nvjzPfIdC8hZBdTckEnVAWnMjnTF/9JqNkbAr2nXTmKv
W6t9dDgxrRjBMGEpQBhtZ3XymUATFYCJ8YEU+BeKv9ZLOJ3Ohz/nf6zccfNIT9OZaLYhtB+IrcYi
JAIXoNnVSMNEyuB2fL5UWeHT2umCkSI1tyYuq0+UV7iXjnefN9JVQovTgqS1qIAxLCB5jN5t2t8+
GLj6cGpBpXEfweEj8t5XU3PS0F+v3gXlQUhf/OYGfYBMmep/wC3th4UKEhKJ1OW7YptcjqXjPedO
cM8NyH30yLckXTDHe61Duna094v87oneQ8oZ42AdSP7NdNYfRvOpXKo/ofFsF0QlaXUbLk5gULTf
7o5ddlg6fbznggme2UGpjrUdCK4sMpOySJBgFdKk6ULytLQQyspkmqM+v+P6fOU7Y/zaJQX3zfGO
6I6Vvdo3c12MrqMkUxljAIozHahMuDKCF07Tqf5wpaVYWcqZyU9LDS4TStEagWBiGZEpE7KAH66D
8PAyqXCqg11ZWktmXbQUvdrJ5NOZSozIlGmnA68nL5NPtytLa8msS+ifiYkdhjzOxwf/2z4Ofb6O
2H6n88vwWj7tHaqhIjVFErvpjQopaurZiGasaZAbhJ+dNO03M9jpe/y6oHZxPrnfo2Wv9M5cF9Xv
d929IBXAFF2irICvJUGlgAD8g0CvJN96ged4mtQfn7o5dltcLidTsot+1kLT7t8T1z8xQNje3E3W
wGXOBLTE0QSUUxPghKe8JSXuhsX+htP9d8AJPDsdQL1k4ofGWYS0VrR3MK7BUyKdbIsqvU+XyrV5
rhsnuWZUe5bXehyt5nmYn0Il6TezfPsW+Xec7NYPjjD8DeG+PNdjY1yPjTY+4BIAACAASURBVPes
nh3YOEeH/90d8TpN3UiPDyrO/5jnWaZod0wOXEJfL4DjcZyDYupTqj0VTuuCVhsOgd/vuLbYQd9t
1psZx0MhEIoqPE+XSLUBJ2vXvEIHtcsNeyJnNyR8pfpXUhJJ3djpEkiHrm43QHBov22Ip40RtSOy
smIs6ct48rrnwyvptxugPK8nizKC6Q8E9p1eoeWPEx0CooQ+zqhQOHjx3kDTOf4qYPc5rzJteaTu
204euA2JHlqcXpl4WY7qLVWuWpC3omPg0vrEWfgyj+O6JfnXMbZwAnaDLjWixAk2IsbfTd0pCc9Y
yMvPzv+CBO+m6BklLmVyISihbWavSxkqsU69f3v4C9W4bQZ2/tq5Lt+G2LcnYaNmTA5ok3U5Xqf6
aqu2Voq9E3HjBlvA/fAF6RsZmTStMaQ3Bg6csoJ6+Yw/aVeIZkXiz3d4lpfK3gLPmktwrxGDUz7c
npRktg4H97mxOQe5tPOMvsDoQCy7EFg74ZBHALkoFpQVur7nLPDcd4bnuQ0ROOQBmzIzpuclpsCq
lky1be02j0tU0SZQregV6sIqCO6UoOk2RZGT8Vt4mNqUyJQ5SFmLqMGjVEN65WVSxWi6nQSe38JD
FYZEStArL3OQshZRg0ephvTKy+TrspPA81t4qMKQSAl65WUOUtYiavCo0J9BzQMF59uak921eG/i
a/k6/gaHpn7Yo83QT/8lV0vSbUYO/G0M6499mbPT6k48GZblfoeTYZqWnqIX4hS96l3yzEYla/ry
AExGeM9C0CvBERKmFjToSVzghtdPaAlv0LlCiq8CzeOJl7u9+kG3eOI3sGYMQZZ+uSt+Fq4GZDEB
ywKOCbjboo0Ct8lYbaFiLddHdg+sGEundMzBT3gZkxjWkYw/uDdFXjNRLl0QZJbl8N7o/QPJuVnn
YZhCJWVupWsM1F8g1crxOpCr458WDm/iXMW92AIs0Y7ot+GbnpK0ckf0igofgDyiwvvshdTuQ7L0
3OYYijKCbt0YjOzmMupimwkTJvofHp+44oWBdPFkIt2uhfl8u25tV74j4RujU6bmRSZJXsP8VBQ6
pUNJw8BIWDvUyBujizljBPsyJASI29rflXjEUNv6Vx8MtE+5+Zw1hzXQXJL7hBdtMFzpv2iy+qXw
GrMF6u6K3/Jq+G79JRQqSYP3TZCiV0LR6E27Ysy3jSTl1QcHrtsa15/vkQNePo5+cwO+qawP3AQ5
agC1gyhdGkp+pD6yRncbwc/Q9ncko1hanjvGNQlhTf29D+P64CAkHrvVGyIt3qCfnfYW+1bnJ6pf
j+ykr8YQTvguyMNvhXG5UlMXv20cyYYonPpmjxGyXNcZ414PkQ63xfcTTz0Jb+hQhVGavjBAy+H9
YmBy+buhZ1pM/u2mHeHFzViGhgQsKoAcI6A3SfUnKbQ5KIT/3gscht0eXgyHv41a8MQW8LMo6IO6
qc/sYy2RRvoSV2+MUuVhjiDDUtuyOzwVNlNpQ+iVCmGiIBECXC3/aCLmGfhbGCxREAgpcLX8g+Ks
LkpQBspMhUBK1rJ2PLxM4KEaUlHsShMxT+hvzBACfzr2YEhQKAYZGyyLEWxoZSXsxjCty1gkx9mA
6kCnBJhKZPmNFv0u3teEG536nEnmjbr2iO3sBJ8Fei/jfm8YoPf7TfXp5QeYokEL/gYn0yysI7C7
HvNhksGp8r0IPN9BQD8jmdpJV4udjrPhoY6Ads+OOFUXD4RSKOAFxqZoFhOwkfg3RBoIxBN4tO0Q
IaKwGgj8lP5eVLcjsIYB/CnJUBX1v3tb+N696fcHoej+puiKbfh4fPn6fus8TKdQSQvTRXdsnWHO
gADhSY0KJ0rol2gktXFX2Lc+hivKwNMfP3NddI+xLo5M8dRT8CF58oajXoYcp0Vm2qd0coY8SKEB
iFDyfWYg0/w6/tnaFVmxNSnF4nfv0scG+Bn9vUn6dlJVpXNZNtuKIGTaETBGoICm6W4eA4HpRlVF
/bl/NNHKQ+PWq3zRG50vhPQFuHQmqVVHwSVdSz4R0RpJrYZhR8FNs1IKugcgo52UJuGRegUcxlG1
VeztVUm+lhzPaY2qq4m1NkuykQMrbD5lklvaHVLXwo6goQP8yppf1R7pN8Ypk8XrT5kpdkY6/KAR
HNQdSGir9PGRrhf863IZZd5zSvAHcLQnmfj8yxF4jMDglq/1yjaaU460HATDgITm1bqVU+EgiCpt
6McdPkzkdaNM9GroaeWR5VqXrAsJqWmfl6+Mr9eQU+uWTzVrjngSj3dDXw5yctEtFx5DH56X0JzS
HElHvz4OM8pkS+AKc6SJk9dh6PizsWeS+Un4m5kHiXFKc6SpgNAfELAGDiyOHG7jR6k7H7/WsH9v
eCyYEAh8X1ubnBFPz04AAZmMufmHzJ8Y39BHtlwphjj+yRSdUrkp2lwvf4+Y9aHT74aQVje08Z/d
BDy5ILi8VHr4dTifnkX/dGt5HXjd0hxEf/LjYX54HS+U0k0GMJCysJdyKiw9wDycnkLh6+aupgv8
Vf2xmWvhO2m6KRsa/vBlcbdU6wWTpD4C9o4fhxbdqNqQmE1/tE0OWVfbwgP6s3aFyQeudMmgv3Jt
QB5IqKvgIGcO+qMxsoIABs7RcE5ggiJtqeuv3QcPnwYOQ9H/okDqjurwhKqCQCDgcOiuxYb3NskX
vd75wgB9uCUOGjQeAt+dfDU8NDxPLum8HJ7ORQ7Pn0tdvMwjLfvA3Dz8raN44vOvDOiuBi+K0Xxd
droxZiDseOzSj6YsL5OXw9NCf0AAAo8VjwmPlR1PLum8HJ7m67KTw/Pb8dilH01ZXiYvh6eF/sds
/EgfXpB/sr4AbvxoJYWXB9xC/0PgT5/r+tsi+fRwOrSRbxffZH5M8jx26TmVlTZckD/fKW3c1Hdq
kzEVQEFeJi+Hp4+ZDp+x/TV+1g7btuXj/toD+iI931akeUyytd3O1aAvuxruBXhiUNgiDuNGyCYa
82zTqWa0OPWRBpVv1EP+Eq3QOQQhUAW5As3XpSt8XPT30JdU4TOmRGVDg2GjP+KGoBEn14iQJJpI
Focw3S58xvijWkL/z278C/zJjfGpzj9P7EmePJn6GrKH3rn/HPfvkw2x2pB2066EboAQ+k91/lm9
M7pnIHF5q3lu/GeafzzwXiQNyeTvD7GNgqGPf0OMLs34Q46F0j7luxayYYjTgHDrFgoTsguizEYR
XRTlNgrjPWOYN5RpmEBKsOoYoTsXpD6ZCMGrUTDNZqnUiDKGI9X/65v618Gv3SXVVbTNIHBY6Y9Y
8RgK/T/d8SPwT08cn8X9Oxzxv78+vKbJcXmRUgC/jkG/c8Mm33/o+7euN35+L+kxNm/zc9fxHz93
74WfMiEK4MUwIrwO/9D4gzn+49YBqUTujapPtqZwax6MHRt7Q8KfgcfgJATxoHWIOdF6HaQQXGgO
FqBiyBUTDXcBOKg2Oo9RgI4beuVXI6zdls2DocIzy/K68Srzw4LnOWL949qqOHeWc9jpj91FeioT
Q8SWd/tOSPyF/vQWAxz4sceP7eM6/gX+nwX+daFUXdg46y3u38y5S4x/RIAa5WNpf9eGk2vpL1rA
sIeANsKwIEOaf2hxIoO/6BuDVtEkrvNhfcwUcRGTuaKnYAgEdmV51YGHjiG9DuMPrShDDNEAy3B8
Bsn+WuQzZk5l2j96Y4T+DDpGCPzTw9IYbGL8AAIQLPdXGig2esgNSuGiaQaExp3L4ozgy3JTGyYb
PAJ/gb8+GIwhwcYGN3ys45PxiPHzKY8f1kt878DLSuaoEeO7B0rSKGZSMeSKiYZXxfPYljVKgxiL
lwRRNjIMFewWKdJaMM5MwlYHoT8BS+CfOWb4FDF+AAEI/H1NoyRZ3L8UBturGD9i/NiOgSy2zjqQ
bMsOE/tlbQ/GnfDdFBf9zIdd8+zSs4nDNDt+U7rNE0wuMnkefio0yTfUGEQfXg5P5yRH6E8gE/jz
I4fSYvwMjgmfK8YPj4YYP5loZGLC84jxw6ORiZUtPsfRfoFHIePagTU47631rypKf+DMmi/iAgGB
gEBAICAQEAgIBHJA4HB3tK8vpWVssBpf+c5BhGARCAgEBAICAYGAQEAgMDgCma6GcyCp9cZhnUUE
gYBAQCAgEBAICAQEAkeOAHgUqVRKVR0Wb8P5YEP0wwT58Dl/VBDPe7KXIQlBd1/49FyUsZNpd6DD
lp+vzGYz3K6sXTov0o62LTtEHUzyh1jWVgeT0OwR27JD1MEkfYhlbXUwCc0esS07RB1M0odY1lYH
k9DsEduyQ9TBJH2IZW11MAnNHrEtO0QdTNKHWNZWB5PQ7BHbskPUwSR9iGVtdTAJzR6xLTtEHUzS
h1jWVgeT0OwR27JD1MEkfYhlbXUwCc0esS07RB1M0odY1lYHk9DsEduyQ9TBJP0Typ7iSq7Ih9+N
Mf9kKb6BAgVBIQgmN4L6GUY6MNGtF5PqORy9xOUSKGtoyggjAf+izE/SgW8dKWMIIBpiG4T+pDsQ
B0JQqPEq8DcAoYMFxwqjxPhBOBAPOmyAFuOHznV44xig8PjoeOEfYyCRUSTmT3ozifHzTz5+cJlC
D/QmoVf6tVAYHSToGJmnHn1ezrydyKykFyT3omaMNSQMmbpokElu3Uy3hjLq7Nztzc95Fp7s8yLU
aVRK66fqCP1pFwj82RgT40e/bY2bk96w4v7l3Qsx/4j507g/8K+YP3OeP8HRUBTrMVD6tVAypniv
nNpsZrnTiNu4ArmYdl6mXbflIgenAAjkaieHryutPFBC/0FxE/jzI0eMf0CA3mJ4w5GRQ692950Y
PzxKlBbzTyYmYvz8Q9sv/Jl56GJzIK4Gtd3Y/cR3o9MKHQ1mbmOtghZAPj2fH0ymIjam3cLP7klL
OhNlNzRp/fQq9GcwMtzsXCsLzqygJZ3JEfjrUPADDpLE+Ce4iPEDMIj5hw0D/WZBUNKbUMS66LeM
ZZ5hBS3pTI6Yf3QohsP8Y/UxdNXpKgc0gPxiLL1if7MhQstlKw3dDwGujNBl8n8YNOTxCORn8rPi
jOAFUJoNQUboPJx8zCKtEPqnAeTwQXgF/gQQOooQJQ4fMX7Sw4ZRHD5i/MAIoSNHjB8YIGy6ZgQb
NWlCjB+CBRs2jNAh4vDBrH8M+5Xufp4irgaMFetw4SCQ5RqfPNPvqKE/Mks5eRkWmoliBGVgKDPC
Ll2RZ/qUGq+uW43fMdMjVzuG5O6Y9M9uYi1qsyhTmxF2eg6ezoozglXBCJbFCD1L6J8xJtmwYYTA
nw0bRojxw6BgRLZxMtMrF2RL58575fAoxapghMCfQcGIwXFmtzMjKD8rzggdW+4Py2KEninmz892
/uT6yCDpBgrpGOgt6GzaZ5SQ5Vun+M4sdbCPiYbCiae2R56AXzeGkB4Z8p1z8xe7Etesj9Sb0jk2
QsLli1PyvlNmPTBCMtXfvRd+NKpVF3t/N91Na3zq/fCsWYFp5LvpXd3J4iLnBzv7v9tGhxEnnGoi
K/fOy1ugJK7ZEK2n+qc1NLSFQjSREeboqWWeL3iTPziQMrPJ984PouR3SQNJzcbFyIJKIcntuHeM
44H6WJONfKOU8ZfXMBN/PtesJ5bnc1mUEZn8WCZbyKVej/PeMcoD9XFsFx94HVCO9I2J3s79sT8l
tIllvsemuNL9lakPXxZkWhgsUb5SnXY8vigwTpG27wlf15QyjVtestP5/AKf1BG5eDt5o5uX43KZ
snLBIRc9+dp5fr5qns5er3zfvOAcD88nJZPq3o74PfVxHGk08HVll0OA5bvPAqwlCmJ5mSyq15ft
zyD18sVZRbwMvS4pfX+BNFqKimUSWHELYYkOwo9y9VBT4X+wxvnG5r7b++U7Tw6c7JGSKs2SvYr6
+KbwEzHEYelI38qxrjwyXXX0xB/YGn1TZzME6frbzJ987ifq6XQ8vcBfAYIj8S+/H23i+AsKPc/W
emCmTt9NRv34Nyf85W9M8HTuj/7JchPwGuYkxxgeUC9flkUZwekPaYOFodbLy+J1GKocvizItChs
ifKVWuih1ssX53UYqhy+7Amlf7Y1AVCQs/pMdZ1QHl+YtxT9DO1gT+KDjmSPKuUFXNfOzbvGy3tM
8q21eYt90FUSXD4xeGiFqtYTU7l/WjSh9qfwjv3aBPQzevqT27sS3cUe8DOSidT2ruSHIZTt5/S1
1qVpLockOWQfa4iV45MW/Vyun07xzC0EKdaA9dogmK5Ukx48xb+gzFFKS8PQgQBXRlilmuNMbUaY
8zHGRDEik2eoKaw6RlAJrApZIe1y6u2yk69pV0zLW17lKlHIzKtg8639lZZpgGMn7ZPSayrc4GdA
mFblqoY/oHxW/SUZ5mhcIKNVm8XqWTSRFWeEmRljx07/tGxWHSNoHmldyLhNQinJ6VRqKry/qrW+
sK6LYsUZoWfI6e77NPUfSl36TQQKg/JW/fVm4J+hyOSKWcmzy+AeT73ZL0kuZ22ekudSCj30n+x1
yRTfpRMCt44HP0Nr7Ei2JKXSQvdPZ5tdP4tUpjYjLAwQHUR/Rc6j/D7XpeaZ9JIqF3kihLsp2xzE
qmMElcPVZdyYmQpxKaw4I7hMneRkYgqNZrINKYVVxwhafKh1seKMyFRjqDIzJWSmsOoY8c+ufyZG
mELHMMmDbgCwaGdo2o2z/DCVJyPxm9+PbtDLyrfPzjs7qHy5xvVoXRzSagpct0/1jqK/1gbuuFEW
hVDc9YKcfEJ+XB/6djvnSPJs+NyQ+tXmgVfgb6H3W5K0bXf42x3IcUcjXm2DLH13fR9WTWvPqoNl
NDAlKbMqJSV4diQgsCxSHz4MyFIYr+Ruh1xdvoaVGiEBRlbViLJG65gcRhjM1r9UoFW+mYsKYaIY
kUvZXHj42ri6TO3ieXhalmPkmS+UBIi0htbI6S3E5+B5OJmYfBT6L6/GYRdVJa/PfVUweieYDUug
won/ijmsLsaWYhQhcsHnmOlPnuOlxDUbM9fJOK2Sif+zMcJWkmqKPb+a7vEWeq7xxB+Fx25LsNc/
3X3HTH82/i1KcFG7ujgWgyQ3EegPgV6hLG2OwaH/tZMpyzOLXN8c56mKxC7eHs9eNo2PMqdQTvYl
35SkgoCjUJJCHZHzLYteivOaanBH1KfeDz2Ei7iOpxYHRgXcV7hiT1gWBpiGaflksA1Rf4lMPkSY
PL/CKTXCVESD48xC4nXSGIiFYIcP5aFXDiv9xrTTnPIfpf5UpUF0y0W+jf6YTJvDM1joXORzmJhk
5lI2Fx5eJbu6eB6ezkW+ncxcyubCw+tjVxfPw9NMPhmhfA6lOVeDF+1ynZWPBuNPdczPAH7t9h2x
+fO8EjxdyXK9Jt9U6x0FKxA9yWi+swLZddNSVeR+eKq7rTlyzV52w6RzQZAL7h2DOa2T4nx0rq8G
nxyUby0I/p+4WuDDBYaZU4LPhxM/PSj9ZIpz4/bw7V1Yy7KR3qtGuUuJl4NrmzuibyakG2vzznIk
V27W9zIenO6dGcC7FNZFXto18DMoKMvVJZ7fTnKsOZCcN85TAZmq1tgW/U59otflfHyODx8sSn0v
z4rrQiDKgqasnOKfW+YEyEKR5FNbB8hGknxjbYBUGls+O28O6uP63ULH33fqetLS1aVeqHRntza9
zAmrRG9sDd3eJa2c4rsIo6jD9sPRH+xN9ALtdIAavv5kn8dZE0BMD3bEbt9O1sxRQ29fa7K80l3h
kA4eHli+J3Vqufum8Z5S0o09ffFfbEMcANszK7wrx7lKyfEa0Pa5nZGH+knvaDb1kuZLnfHOgHtO
EAdLTzjxq7rIKwn0L83tkr5R47ug1FlIKo0mUn/fE7m9TV02xvedMix45by889sj3+9xPsr119KR
3utGuw09E7/aFn0FDKCs3DrDf6qSfDukXFCFwEJPvbU7cnuHZZ0apBoDhg4bj3t+QJJi8QcPKt+f
6Fw0xiVtTc+jM0s9N01yj8K2a9vbUiiWCICLXZZNB/mtHYS3EwDoX1riyENLpLX0xH+xNbYBtZJX
TvYtLXbmQX0s3agX/1LN9WEv03Uy8+Mrz63TsJLEXI36rvjmmGeBR/8OX0HAde8U7zQcJIjb67sj
d3bgkoClLQci0uj0sBy4vUtl5rx6hPe3E83DMuy4b6p3ep5CD0r19Cd+uz2yGtwa2+FB9HQ57j3J
NzdfgaaH+hKb4sq8oPbg+wOroRs9ziy3obWh7CaKhuntuT85b7z59qRF2HQGUUCSdMcXR3ouG+Wu
IFNBKIIdcc04z2RQxRKSqQf2JnBjIuiskaT6NhwwU8nuyM42GCBytUtrMgZRdbEL9jIOHogQPwMY
UzfWRS71axsNBotsjJr614ha+LLoT+9KcjWYR5U5qxuTtN8Lil01fFs06dZZgUWyMctJ0tLR/htG
Km9uD9/ZAwvLroeneWoC2BGw3bbtUPTbB5LLxvr1G3N+EG7M5Q3sbjDqo3+PXn8qAaQxgq8hF/k8
/1DpXOQPjj9TmxG8DrnI5/mHSucif1jobxrLaRSIvwwNgH8Q6BWdfQVMYLIv9pDl4SkaP//tvvM3
kcMQkvpBS+K57aGL6wYOmR8Q/W5HoUMen0dkputKU05YMFXg3lbIP0KgIpqxY4qTdQLcfGpxgNA0
LywwKkqlG2WeOtr//fHoZ7T0JVsSZG3zZF+1JI0JKnk+Gadvj+v5+X7wM6KRVH2fCtVdMj14bymu
tQRADkQneCok9WBYBTXGVfj+q4rgoOogQXVpXRnldCwoc0bDyYMRLc/nvHZuYBmcVJXlMbAA68dK
E0appBkNEEArnUMdC1geSUi3nxK8FKKq2tiTDCnytJG+P0x3I/6KXOSSK2B+CUiNXcmOpDyq1Pvw
LLKmq8gjXMrMkehnQAgq0qnVvp/VoJ8BOByMSYX57p/O9y+F7iv0/rQG8JEhvZFou3y2fxk2UR68
3nEVHvAzOvpTIVUqDLhurfXA0TlLu66BXZIKZyEsLHdBpZrX5Th7SuAbXhlGCp3DkqoGBCz2sv5a
NhHWotHPaOnB/irMd926wP9FsA2aVhlQQO1LqpzJWKolJkFPnT3NfwUxG9hIm7B0pBucwpaO5Orm
BKwh5RV7SOsId8B9/zQP+BmwB3cwJk/TMR80S5YDDhwVn9xBmrasJnBpmcOrqfVdsKUIPeW5m/QO
SQfH0ZqevQWyjDZLljrM910ms75CRjMUxzi2hB9wP3OKD/yMaCRZH8IRvnRa3oOVODIsg0011nXI
sCQDGwYqGasB2dJq5fG5/jngMSRS9TAsYQwEXd+f5YU7iw7LjOHhLUD9lQfnBBbQUn1qXr5rMey6
ehxV0Il2tyFrp9F8/c6FjqC358RstyeUorcY0b/A47h1su9vi4PfGY9+RiicfGZ7+Mu4OCEvHOle
UJHxb6SL7gAuLQFDrH3QiS7XSfl4V8yZFnxncfAPC/LfWRi4sRBnmEl+vEYUx32z8tYuyl+7KHhH
sfTA4WT6lAxkQzD0TxM03e7K6Y8sNMozx5IfwCOBJ72HciniqMIkxrgq/fqEg5XCs1O+w+tURsOm
tuR4FIeEAnPU9h7Yb1NmjvU/WGa9MZkcJI65/ibp9pGh1msnaahyPhF/u4os6UOt11KcRYcqZzjr
TxxmNuINotyLfnEUthIGDQ/V0wOieFvyoaEj+vO40huycZ9h52Wc/51xfAkp2hM5py5x3fv99y3I
nyMnv07WjQtKfS9Mc33cEPp2Gx4zNAo4/n0sThZv1IVuB0deku9bAAfoXJd44LwHxCTQ6RuTvbAu
2nggfOU+NPsFxZ5npnsWTPBUd8C32THAxtD170c/hsfcCt+DNa7RxQ7pcOLK96MvL7I5QkhKtRwe
uIw8E6ycHry02LFijGP13hSuTsOsJGl3fhQuBU1k06I3KadfaKURnxL2ef4QQB2ue58swEiOhxcE
phV7bvTHfxane1rac5v7f4abAo5HFwZq8r23BuN3RqktJ1lRZaYk37AAcFCf+jD0EG7tSFfUBK6t
cF4z3rF3AHvk4L7Q8gM4Q32jNri8UJldKL8pec7+hHrVZz4MPQDSXE48pOZxjLW0S3H+dToIV3++
PoTPrJJ0zfTgVcXyrEL5oX0D+V448yvDmvMTqjSxzPAXFOdVVWACWYtg8Sl4SaHj38Y5/1SfQosL
PXVo4EqyAHbrKflLA8qiEuWJlvTcSlj4i/Iv5WAhtDWHkrDG8FqPF1r3r1XK6kNY5NYaL4DCuv7G
WcFLcH0Og20WDHvSiZ/cQYHEiAI0Tq9/GLoTvXDHU4sCozyOGkk+LXu6ZDZOsEQUmO/GfZ9ChMf1
2zmOqCI548kb6FIcpPFBcawc6xmACqFlbscpZU4Y1f+fvTeBs6O47oW7++5zZ9OgfSS0jCQkGUkg
AZIAAUKGSLYjOQ5O/MPgwI8XsP1wMC+x+QgfDsGJsU3yGRJiAzHBz8hOYvMSS3YMsQGJVRJaQAKE
0IIktC+MZubeO3fv/v6nTvfputvoSgzG+N36japPV53lX6dOV1dXV18Z2fzKrHnX2VE8DEhAchjP
6orMO9TfrTRIW46knbvqC0unJfIveGeayCx8hV6PYg7xw4ubJwRMWlmxOSzLwsMaD9eNjM3ChqpU
7qaNFMxThkcfmhpGF0DFAJfhAWVApg7uleuNPwy+9PIsiYfOobF/4+3itr35cO4X+3JP+g9F9j+8
khqF4YtNeDlWE6EQad6wAFaBnlb857rvJjBvLgbjQXTl0pnNxsZEt1rtmDKG1hyxXaY5Yk0ZE/t1
s3mFenGs1KiMAXuwq0wdfNY6KXv1Iee8ltDcEQGDxq7Aog7TSOQ29IemtLoavAEHVwBFbY4ekFSE
hyzacJ/NLdlITWcXdXYEn9xWcmGW4Bh8/CXqa54Mlt3B0lMTaI2KwbI7WHpqwKxZPFh269fj6Hs1
KnC5MwXMvKCR519MsIEKfr+gYK/AOu0AKW/vy6jRXfGELLO7j09NkPJBswAAIABJREFUvkHxujHd
UDAeYzOUe7PAmWlErCFqxUXNM1Di/N2W/vNC9uqscRfOKFkfUavKhhX4wphA2DRzRZPaEgleHjLW
KVXb92V53Nn8bqHHCNGIgqRsB5VRLijNC//krT3evyv7iY5oOy2Cl6xg6OBLZNno/txmuDFt/9E4
DMW0CLBodHiJhcHCyANfyJyE2xW2sGCU7MmqeQbI4j/vK947IXBma8DI0A7HQjKnquzNodAw4jU6
2sK3wCNIyuXNQJWks7Hjm39+RmHLu/lf70guoIVlfP5zUrs5mmcg5Yv788ZI0+G5pNsu0zzgFK9b
kxiPF2CRwLK4NaU5cK5626Jk0DPUzjC4/XHfaGul/aTUoiRqKZDufSt7+dzo0CHBTtd7zrP73Fh7
8VhhcVyBZI3V8raO8HRyRPFNAx9FG7vxANcenDA2MmU/9j1YozAjtQv/oqaYkL53R/Zjc9C9MG2N
akJVkapUSHtVvg03Kso6KID4cbwOMrdmsUxtLj6/5aye/Maj+bte6tuu3H6gRrmvXVFDo9iEaNB7
OpWaYxbRVT/kRrllzT9T1jFIoJAu3Lclc8C0htI6lx+Qmw9n1owLzY8EsHPxaWI0pC14S0XdZxpD
qfv4pYN/6ZVwptOf6c2gs+a1BCbHA12twWEIcJvm7pwyeFNZER4LhtJSyrO7eNKMFxPZ9RPCeMtT
chmODYYdJ+fIZWg+xjdMV3H5ocrlWTr+qPeiSipv7+gprtHiDaWbE0W+usv14twKImaSR931iTe6
CyNizvLX0yvUnPcLZzdf3WFdPi70KMdjofjwKyl6T9oc+fnsSHt75Jbm/P3JKj6sYkiKVLDVO35a
5oaj+eNTQmNHhDoRqENDYw1j66H8wVa+BEVpNaJIq4lGJLxqfuCNY4XnjmQXPOd2nXthYkkYjqoW
A9XUeWWnhN8TGuTje8HwXmQHqxnvBcN7kf1g8JcMLwIBY3aViiMZG1EbDao7JE8svOnFshGh1lxh
ZbfdKzoGICrdpJg370phoaKqHD/myujm8njWCW3ewaQ9qP3H9wdS/F5ToSUBh5VMGBOdUGIDS/rS
XDC7APw7W+XsyMNPFzoGNT4FXSAM7S14nGVTrpnq4FHJppBzQ5ShYEv46hZXkA+MBJ7H3UjSPtrT
FTBoGZy0ZPBErNKUIUF1x7IWT3JnSlze3Bo0Xs88PtS6amigvSV4Cf7GG5lU/s6NaZ6L1LILcdoS
Wy257VLgp50RvWNSWN+pVk3CL+NvBalp3Hbk6g2LEbBwV6NkF9/wvLhDm4BSled/oiGoTq8eo7wT
DH59rua+UOjq9jRmn71QFTNOkIBKORUt5DqnFw/aMYeqGIlb5TKqgxcVtTvo/rfSM89pmhIxJ3SE
8XcVVlAOpj+3M1+9fBfWXRRsNmoaN6/hTcTWAxc2zzIKN7/UX/OmCBG7+OOt2Xdp7mvi061jqcKT
Ke4glWftHQq0ypwNvfb84SYvR6gSry2OuhwcI82t5twXBOVxGuZVE5o+OTzgXxGohCm4nXgQHiVi
fIKJMpj2+VesiwSF3KvVLkNuRRVtXpFA8h6GBLYith9Nf8UuXj8uMj0evGp68Crsdjqc/dd9OTxv
AOoDF7bMKmmD0loo3LwmfbyDXqOsoc0ZSM73tvV/T1Gcfe+t7NL5seaW4KgUtbfneNb9sD+Z/cnx
8I1Dzel4KYyphoDRZGuSzCwiQlQVgFkb71CMxS2hxVbGoB0o9tNHnEiH4qaOqO06u3DX9tw3p4Tx
KnDWaPxFvmTbK19P3UtLvyrBNJMDY3C5vQMzi4gQXv1Ax2rX70D8tereC4b3ItvAzz1yaj6ka6cy
VV6RxNObsnErbW4N3xDKPeLdBqgiFLp5ClZuHWNNouZObOLzUg2ItFAxwDXjSVc/hky6tfI0SHG0
xYI3j7JeP+QDVfciZ+WW1K/y7ie4+IYNsF/LGthNeArJw0+qA9ZYxznAwhYtMGQSFe9u61Pdonac
HN7ff8chu4NuJEjmiIixJ0GzCtKMR2QvDdVaijJZdNmeKGawHpPN3flqLqO6MW0bo2KWkS1uN5wj
21I/CJiXnRG6aGjo3I5ANB7684m5Jwe0qyv3jFccQ6E7poSxjL/veO757uKbJwpdXc3XYRPMAEkt
dWS8fTDMSHjztrsRwXZ4zR9l5b3j+d9Vj1MreCW9TXc27M/JZHdoW3hWi3nRmWGjJ9+Gvq+4I3LB
AFWufu8wUAfl7f+1qa85GFg6LHTeMGypMSeMjn5hX/572UK18gTtduJWQLkQuA2jh71FI89sxdG2
n+6uHWMhmqu5AYntBfSk7/CHmhWK6iq47MwYtqEYtr3hYG5TX3Fdt/Nnc5tnkbOBlQIyyJ8xlyoL
q5nQWCwmuUsL5ixsI1L8A1yGpTpO52zt8Rz+OmPBP50QuXRoYPro6NdHR2mv9M7ioWRxRAjxpam1
jFC+iMnW5cMResUX+e5rWXdMigzN5W/dUxoxBfuV7uJVHcGE9jyjWjRgnGvWTp906BL4xZHC4pbg
pePDBkI9kfsJPiNnjX78+Bb46xI+33M085mjmWntoUVDg+edgV3h1tLp0RUv+dNAX+w3QzFggS3E
b8b6e7fSwH86PvRvXiKNInWPkgIh8vmV3VGsJV4zM7phI+1pUMl9Q4zF8JPOM0YHzWTB8T8DFc2K
yJfeeEorT3Zm03MqPnP/o1COf5HmOnwR0GIM7fPHi16QIXNc1NiMHwNBCoX+c05sqFH8xxdSr55M
vb81tYzTCn5qqLkWm/zxJmIcbUs8XjIS+dy8xuyfV1DPHy9e1xFsb7W2e1/o3HFuy+IWc/O2xM0n
6EbZ3B5ebOSfJEHrT9XblkPYwYq1DT1l7SRWniKB4Xn7J2qUnzWm6Y6JwWR3epgdxRPYmtf7vno4
t+Jwrm147BdTQ3jdM7BdXXdVGu3CfmE0vNCXuRqfFFKylrkvUMgt6j5njsXBvesQx4FeekXV3hH+
Iyv/E9Uby8aS97BjV26TxFeZLGO0ZR4sXWiZNzqM+2umL3vr29oDfMT59dxolEIir1Y1gn860rxZ
fWq7WNmCo5AGqCozXttRqdiU+BSreOdzqe/hd97eyah9MJC2Hrm4uVp5mWL/lL6PUZMwv+hUqH54
MoRmWjfzppZ4+DKaphXf1Dxfpu+kYdmFl3RYrt+evPWoEo2Hu2jepvZZl+nSTt/AC6yO4KUTIp2v
0C/XdXaEL/R2VQ1wGXIkaGpOkzyQLty1tYA3TTecGfnEmBC2TALx326p1Vbrz3HzThVWqzg0AoGL
R4aajcAfvZNkPNd2RRCZPYnic724DINjR0fm7elfS9Csi2kvjrO1lyVPE22dYpuP5Y5PCmI1CPxb
j/hPUCxOE7hgcFHE2E59bc1Xm4RA4ccPsbU8052+4vX82m5I5f/zkqahBnVf1QuTtTXyhgcG2wPV
Z+SYalSv+N7W9OUXN42Mhx+4JLSvp4itF+Pa8d0BUDn/sUMb5TWY3giDLYH0S5G45y3RPkHUGI1Z
U5p/PqFk7hMMGJu2pe54l/dLeI8QJSyegnzhP47aNw63vnR+fNb+fKg9PB/r6Hbh348710xmHufb
u3KXnB2GlR93ZNclzcvG0P0peTyHAWWKp6bKUQ39zR3Rn54TeIS+xvRZ6PI2jPnY5P9O9ngTHhrg
CPs/6Nt3d3OJqjfp/hEMff9888lt6fuxkxz4q3l3++Hs9klBbPZcdX7wqUOFUcMieChHEx7HSyW2
ZAXuuDA+753CqFH0I2ZGKvsd+rkhZUQyu/CL4851QwNfurh5/ju53mjwUnpiM147WFgXLNw4NDT/
7JYH9md32IHL1BuHt/B++qh9ErusXLlds6a1a0dBLXdFHppovJwzL+2M8DcRQbVMdYBe7gQundH8
wP70feDjlM//knZuBr6EVwbv5Ax8oYBNuIazGps6K9rkydDx2qktNw41/nVt4rt+uJmf6qQ2vo6N
JHrK5l9ORy+JWZ/stL7gdn3LI83ZfRiR6ceaOElUVFZ5LN6xdgcVzx9tTGkN/NXcposOFEKtoUtp
icV+17a3JauWexrLj84d6xMjDGd7WTkHTNWwL+F0vr87P39qCBH+w9bsawXr8jG03+j44dxqbMws
4cSJ1n0cluUM7vkufObQEZiCn64K5nJNoStHqy+xg4ELI8bmijushMfa/ZmtZzZPb4ksnx/cnjSm
D3EdHjacb+/MXTKj+mVYBkG0lZXXe2rbj+xJ4099Kl9bKBbEh6P7Dhbc9bB8/plEbGmL9aV58en7
800YSWiAs3+CRY5s4dkU9lAH75nb9NSB4pl8Gabzj79/CwTYHQzgplqFzfM7FJwXny7fH+28knBm
dZhXz45POFIcOSwsHyUdwOddRnhkR+w/zw6s7nGmj6BBD5t78KA4Srswb8YU+bc26fGPC4tPf2vR
VgJr4CefVB+/aKpe6TEqsQufXte/gT6yMse2B2fhKRzbDVP5f1yf8L41L5XDy2Au8PQV+Hbgnbrc
PGZZpvfzfO7v9DUHrTY17aHHNSS+Q6u8X1sC4eWQx7alHj+Or7kCl4yPYnQoZAs/eIUePlxZPL92
Z76yLYcVjbFDI1eNp88sj3dn/x/tV3p0nbjjuSsZ2cJreByyzJGtoQkc6ECi8CvNzuGsOevM6CLs
g7OLj29J8dKOGIXLnsPPCmJNIha8DBvIpRVEUdKMFm9Y37817QRjwcUTo5hncBNWKzaVORkrsGhi
ZDq2sGGbxStZHhx9qIrpka3JHx/FwGGdB1T0gx/O5rdTX33X2X40g/ICdk2OiV51ZgjzIuwnUJtj
BrLrK0fbTd+ZJe0aaj/4DhjxdW70uomRCYHiBvXaezTNHownD+V76InLmnVmZLxCyP31vS3Jlegv
y0J/0TyjYD/NPwOgdZlidzNyFLmd/pU8pYeC07Df0C6sUGtLmojzkwPkeWyma+7O3Pl2HvOcKaMj
mGck8VbJ619ERa0qVlVPB937Rv/mlBOMUMchEoK2/eTrKayuVSl/jcprXV69eWd76XyJMEjYM1F2
7TBKlWOzwp07c1itwQeoS8fg0dzYfTh93XZyAietLRVh6fGUca5+J/1cwqHvZifF6PPj3jx9eGmY
U9oIjR8eSkwP+5teSj6nPinHPON4HxaxwF18JWv0njjJZcgAkGvaqEwDX25XRKoS9KDPTkMuhMc6
7wz67ZZXjvn32ns3p4AcI8kiNZIANr7negxTW9O4a2Py6R5bdTRdhmq3U+aAp2rwj2qxFpjVBm7j
pwepKzN9+Z8osFnVseyWR95KUzNDgfljMM+wt3YTB1XZhb/ZlsWgNxRbiDB04EPoVP6vN9M8Xb8w
Zw0+9FKN4nYhSusHOiuLfz4dSOB9qBPYQtRvpIG/tq/MW156d2Oe5tM1E36JD78bgWsgZ29GxKMD
PpAIqMQXMueFzbTtbOars5IB37LGLSDvztvb+ckYyE+GvxNLE0UHX/dVTaTQdt5MO+6DUSWTZU4J
GEfytRk0kc6INTZopAvOZtmcEQo9gf+z42j/km0F2MJdeTNumwwbglXxW+a8GBZFjDfTpXt16X+t
M2O2sS9tlw2RVexqqKqTeruUxVqe74yYSTRfHMgOR47+ipjporO5bO9ndXvvsdScFUfbnbVVYmOA
qnKj5KiA4WP2/N8Wsaah4ypir1Z5ud7BO6eAxNaZVHkX+xbY//hPExGWBaf3pPGvYrI7Z1eZCflK
faqzPXIffhNvaz9/cY2JL30ia+dvfimN52lODLJ+nZ6cOkr84MzzfwlD/Scqbt9MlV4meC0Ysqap
dwxr6TVlSXI7FJdhyZy3hOckJ4OIX7PUGbPGWkZ32uYPoLQaY0rMwg6wSm+XX5i6zAD0+4N/AIOD
XNXAP8gOPYm6OaHCnwxJdY1ui8fjgYC7xrlm3aY6phon0Xxa1Y3ur+U2nmrUfvdUS+7Uyhv+PzV/
DTb375D/O0fE/m0qflijuHInXuWYvzcheh4+NU9lP7HRXYobbN8Nhr7fIf+/1+nXYLjzlHU0/H/K
LhtUgffT/3NCxT8Zkqycaqj1DBhGqvXE8H7Agi22qI5kujLVY3eweCqtD1zy/uFXr2zV1gcPQT1t
9HjrPb5/+Cu7soG/sld+h/x/4Ghm5fDA0o7A0qlNS7ml2cLf4pVfPf0+WDyVHh645HfI/9TQyosO
hYPl23r0DOztytqG/9kn9fi2Hp5KDw9c8v76H4irJDXVkEgVQud8f2Hplga8PE4b24cLfzb/P9cX
vc0jyjkfLvyl/UlnDfzsk3qGjAF4fnvj37n39eSPY4HL26ywYxzvL67gX9EGYG4ON/+3Fz/jU/mH
0v8N/J4HTjvGBuh3T/d7nbqdNjYWFHEhBBiI32b8Hs4Bd2l4TCc/1uOOweI5OZpT5xgsbPXoORm6
7Won48m4SuvrsTtYPKWWB+dssLDVo2dwEJdqqcfuYPGUWh6cs/eM7UC6+Fja227J2oBMiMFBWVvL
e8bvqq5HT20Up19Tj93B4jl9lLUlBwtbPXpqozj9mnrsDhbP6aOsLTlY2OrRUxvFwDX09WqVhFkS
EnIhqjANUpGYEGJgxcImRCW/VAlRyTNYJWJCiIE1C5sQlfxSJUQlz2CViAkhBtYsbEJU8kuVEJU8
g1UiJoQYWLOwCVHJL1VCVPIMVomYEGJgzcImRCW/VAlRyTNYJWJCiIE1C5sQlfxSJUQlz2CViAkh
BtYsbEJU8kuVEJU8g1UiJoQYWLOwCVHJL1VCVPIMVomYEGJgzcImRCW/VAlRyTNYJWJCiIE1C5sQ
lfxSJUQlz2CViAkhBtYsbEIMzO/V1phqyOxGCBYQ7UJ4ivyjVAnh11WjxIQQ1bj8MmETwq/zKKkS
gmsEkhCehH+UKiH8umqUmBCiGpdfJmxC+HUeJVVCcI1AEsKT8I9SJYRfV40SE0JU4/LLhE0Iv86j
pEoIrhFIQngS/lGqhPDrqlFiQohqXH6ZsAnh13mUVAnBNQJJCE/CP0qVEH5dNUpMCFGNyy8TNiH8
Oo+SKiG4RiAJ4Un4R6kSwq+rRokJIapx+WXCJoRf51FSJQTXCCQhPAn/KFVC+HXVKDEhRDUuv0zY
hPDrPEqqhOAagSSEJ+EfpUoIv64aJSaEqMbllwmbEH6dR0mVEFwjkITwJPyjVAnh11WjxIQQ1bj8
MmETwq/zKKkSgmsEkhCehH+UKiH8umqUmBCiGpdfJmxC+HUeJVVCcI1AEsKT8I9SJYRfV40SE0JU
4/LLhE0Iv24gqsZUQ1AKwUpEOwhUcV7GM5A5r05EhOAaORXCk/CPUiWEX+dRUiUE1zTwsx/ELUIM
XO75lY4iIoRey7RUCcHlDf8P7B9xlxD1+1bnFHEhGv6vxz/iLiF0KaalSoj6eRrxP7APxaVC1O9b
nVPEheDahv9/M/7X+8Kja+zVkC7Re8iTcY+1eGqV6+K1eGqVI2JQxXHDBHNCpxD16K+HhxWKWiHe
i2wDv+49pmv5uVa5rqEWT63yhv917zX8XytOapU34qcRP7oHasVJrfL/2+JH95VHB3f1Oy8k1W/R
1fpf7GqWewsbpAs+Znd6ivmI/66GxYlF+8/o/SURTw7SA/Ccqv5adkvKPdPKsH6ioKishL+Bn68k
3z30H3FV7d+6ynWXN+JHebXWNdKIf3gGqSSuGvGjBs2S21iNMaoRP434qTW2DHb8tMcdY4h2j/BI
7WNXuozVxYw6JtTVTZw+oSjuNr1cZ9KHA5TjtEpijaxNtdX02MRWiQv0YUVTp6lRw5BnDuXcHOYV
nYy8gd/tUeUX8ryJ/2XUdav4quF/cYVPsMe8c++oXOedNOKfI6kRP15ENMZPd2zxD+walTfGH3YG
37D4domSD/H9y7uV+N1NFKYaqFA7Nkq6nO89ygdlQ6fIkzu8WUj5sKJmLcRZykT3eIWjhF+bieu2
wMynpEc9PQ8s28CvXKtc3vA/Qq8RP43rtzH+qBhojJ+4lZSl0tBw71TgofLG+Pkex88yX9OptldD
v/3zTZ3zsiFb7xO+u3P3SF4S1qrPuJt1PSXTAtW7BMYj+OqQU1Vz8qyB3/WbPi1r+P/kgeNyNOKn
ET/sgcb40xj/2QM852jcv+oZREvGzyoCPNUAF9/mvdlcLTG9HNMFOlWyejnpUoWkU3uypG5Tp2yL
e5F4a9wOdX6w+ToV6Q+LXhWVNPCTpzRfNfzvhWIjfjgucJmwSxrXL48hjfGHA6IxfspQ4Y8VjfFT
nOIRPIDwtQNHcdhgbNHjh+5B5QlTDVeI3AuSFTLh1tRW54nSHIKs8rmuSJMl0x5cHQYLuaKKHxc/
EqlkcffEh8rMxKTZ0ki3IS6bhoFKRKevr4HfjYKSYbfhf4owL2C8mGzED3tFcr7KOG/EjwqTxvij
RubSa4cChr0joaOIRvywW36X7l+lPcxnaq+Go3obGbeWarS9Gm6pihLdHbq68ickteChM5BKbYYI
nTw7QbmuswSDNhUoH8K8KpL1bJXINvCXeb/hf0SaimE9Thrxw2HSuH5VaJROEbxBhsYo9XzSiB+6
XtSIXTa6NOKnET/6uFoWHnTqqBcoYCJaDyP2nOu/Zc1mi2Emcs6KPL80UfxlGStBIRMn0cn2ylSw
MONgBmhhDBpnCTQPdjm7zsR1SgPrY2yaSiKlkAnOGYsLoYbOEj0QYxmUlgj7XLqamuw6E6tSCnR+
X6NXxSWMnPMSCDV0lujRDZQI+1y6Go99YbPVmvXCg1h1Jjn1Aoyx+RoVJYVMcF4CoYbOEj0QYxk2
yqclHCXQarLXsKXzl2ptxI/yh+6gks7zvaW7tia7zgRRPv3tiB/LuibmLE8qSB9G/LprG/glLuEK
TkxwDl+xi6hKd5ycsozkzF1FWDhK1NRkr2FL5/c1KoptgmSC8w8Mfxk4OtV+LVQgguC/YGDFBa3p
ZUN+tqj9sUXtP1sypG9h8/0tWJxQbneMZcOjO68Y4iztoL+Pta+dpCYu4iVpJ2uTU8d4dG47RNKX
REkVajk3reegbUnzMjw98AME57r7BBsTUiWEzhAJdy/rSFwQVs0xH53V9K2QMhcKdy/t6Ds/LA2B
NNGcmEDOqDgXkFyu51JFhPf0Myj49bYwLZAc41vntMGHa8ZYLnJU1Y9feSDBHjCNG8fEnpsaVB1x
Ovhnjmh65vL2754VMMKhA8s6HPx9NL6wFPzMYbE8ypd2rB2rAOsOZOSnhF8XhyE0hzv6N+h/P3hO
Db/56EwVh9IE4AetYrXv/JDbC4MRP9+a3Ya+WNtpqfjXLjQxLQQiB3T98SOCIBg/d/dvpf+XjW0m
P+BKYag6+Nr46aKYEnB9AkEk1cZrxscfWzSEwlgKmUlOFRszl+dirgwDNDjW2itwgQx5erhSxAym
sWxMHOA3jqerZikaIpe8aAA7qyXidK5fhu835zTxu2rcQPLwa9i8UBHkVXga+N0wK48c7hTu6DIH
4hSJcyGYpyQ2flP+V3AqMzXVqA49uHNJ29JRQUwH9h7PrTuUP2EbLS3hP7u87cEmAj3zjOjj85q6
YuaJ3tym40UjaM2d3vrmJO/irDSFZiMhD4auHEF2o+3RR6GKC9UxDmnUnJ5b9VZAm3I9phZBhej+
89uuGx8Zrt4XQT+OIZSzIQGmMNTMhE2kmIAAVwnB5QAAQkfFNNgUNjLERP08rFDpj4RwMMhjdPRy
RVbPhE2Ju54BHQ7fPzs2/wzlJp0HqHB6cmzWo3Oihp3/69cKhoXVL5Xiof8R91CoNt4wIaLmoUaT
9K+CQSbEqCdR/ShsuqBX6DcHwsxQL/562ujxQDOrrYahOmwpVVDvv8CLQ9HAgNXHYBSTfCqGTu5/
D5vOCSWOEQ2SySb2O9eKWrHOBBtFPkAiZZ5vdXEuVJV+V4KBHaWjYhqcIDgxUT+PqNUBgEbinNVW
y5t03+riuqyoiqiLYmiAoJb+LX87tS5rzJ0d/zIEBxW/6n3z8guaSbOfCBPCmxqomuBe8tIErmJ+
wQ8C2DgvxU+MDFuIMgaurcojakHof1CF04ETM+hSTOuyOg8A4LR+bDondDbwl3WH7lv2POeD7v8y
u+oUvaGmGpUmDfOnC1q6LKOQyt608sT4l5Lz1ic6ftHzZA+J/Mm5tBpxQ1cUg9i2t/o6nk3OebF3
1ktp/Obo1CmxZdAGLtbJBHLt75oJ0dGGUSigyPr4WXQRSVjg/Yx7CkLXw9oqdeo8kMSpnnK5lpXd
sbU5lGVsZE5f1lNrGHn8l9dsjmqUGPIyu3LKVVVzEReC2XRsjJxzXafOA3GcViYurJTVOaETqdKu
botrOc/mWlZ0x9bkSKRo5A0jza7HaVU9bL0SA566zmyaHTS2bet/GIK2oX53FpR10Zl8i+NGBa8c
piINNVDCGNgQciG4nBkqbXFtZQ5xNIc7GrWsDYSuh7VV6tR5IIjTysSFlbLgZHNCMDZdp8DgKkeL
Q6+EDIJWiWISiat0PWy9EoPOA0GcaknFvFdYKQtOz65LVNpFCZvgqqp5PXrYeiUGVs7l0AOiMnEh
8+h4wIlTTkwwPHAymxDCwwxlOWpRIjx8WvAuCrar5459zxsYUkI3T+GFQAUbDEicK9LPpAoEA2MA
4Ci1645+VuhuLDeCmflZkRJZuSdpruieuccmQfmr0ONWiTlWJTkEuUoIroIeEJWJC5lHREAgcS4E
ToWhkp9rK3MRF6JSD2ur1IkStggCiXNF+plUCTPrBwcITkxwubAJweW18nr0QJX8QQ9rFoKroAdE
ZeJC5hEREEicC4FTYajk59rKXMSFqNTD2ip1ooQtgkDi3IelCr3Mux8IH3OHQr/XAcpe/mLqYehy
k71kfX/fFXEjZC4zzSkRlBaffbvAxrYcKxw1DMwhWhzjspGx/5gTPbI3Oe2NvAvFUwE414/D9ML+
ycv9V1zYPGxM9Muv5u/za31q2ejo/R+JjYsBhrNtT6b3jMjum/GEAAAgAElEQVTIE6nxr+TRnpmt
4eVzmma00N2rkCv8ckty2UEb5QtHN62YGdx6zJnVGcKD9pMbUpNmNocPJv93PvpVLCMbxo1Xti87
mBq/jazEmsNrL2qaOxTlzolE/oEXkl/LKw0zgi/uKczpig6Db2z7mVcT/x6I/t2sCJ7XC4XiLzcm
lh1RlzrhIj2cFnaE75/lQsqkC7/YnPz0UZrdzGwLL5/tQc0qqIcgbq64qG1BKL+uz/ro2BDsZFK5
e1/q7zq75epR9OSS6Ml+7cXUfQVuUWj9/sK5EyJDMPMrFNe8mbpkt3dDB6sXFjeeGfubs4GZ+u9E
d/budan7cuaP5rd+qs3csSc58y0SuXFi/JtTwoW+9EfXF//PIvLMuDeNnYvitBQxqrnv0uwWJzQn
UvyH1YnbaHqGZD19aeuFwcItTyUflvYyQXaI4fbpYYTBT3cXvTjjcmPcmMjCrYVV6mzmiAjez7gJ
gEnWfPSc5mWjg0MU4EyuuPr15JL9uNOaKy5sXRApvp605o8KQiiRyv14Q+rzvSRWpWp96vN9Dl7c
7ODmbM5TDMwI/vf2/IUfiY1G39rOrgOpT23KbVGwKajOLg2qHhVUhEgBRB4O7VwYD3bn342FZrdT
eOw90H/LG/Y3FzRPVdG4a09q0hbM0swVC9oWWrlrn+1foZTfPrX5a13BX73cu+y4Y8TDWy5omtZi
oQmFgr1lV2rOW/m7p7W4cXhF+7JDqfGbMccrSbHWyJZLm2a0WYC990j6lpczK7jeMX90XvOnKKop
Jl/b3X/NG7ktXMWwQRNhPjgrfvWZYVwZmVShO0Ix70aIYdw+OX7rlLCKEOdEd+7edal7YD8U2nl5
3DiaPd4SmasaeyKRu/fF1D2YlCOZ5o/maHb39F/zurLLnYhcMa24qKLLuF9U9Y3jYn/zES0yX07d
B+URstu7PzfyzOjooLF3T2L8FuUNbg5QLYrHTuT7mkJT6TJ39h5S3lB+vnFs7C+nRcbFqHXw7d6D
6T99NbtKQSq/DLckP32YLkNKkMVfOPTmgnhnxFj/at+iA7YRC22cH5/tjSQ/26QuWwTA5XJRZKh/
9faaxop9mV3nhLsmRa/ZnlzOgFm/5Do/2faSwu9Gms6jl2MIHdX89PATi46otwksCgbTuGxU08/n
hF9Y37vkMKqsFec3XzkiGIUbEBLSNUZpqHB5bVsuGFjhhnCu83vY6ajj1HnqKdf16LJ6eS1a59dt
MSSWYuSc6/y6Tl1W56mnXNejy+rltWidX7cFfgYsBJ/q/LpOXVbnqadc16PL6uW1aJ1ftwV+BiwE
nUpRiTq6jN3BCOq8v5ltgRgu4+7M9WlPEOL4S2dbV3a3PpteYThLnu8xV/Z+3r0n4aYYxjzDyDsH
DKM1SreQSRgx9QTlSPHIhVhaz+W/fyz3LO4fVujaM7V3qMLfEXv8vCbMM0705vemjanjY3NbrI6I
akNrdN1lzZhnZFL5bT12MBxcel77RihxjFbLagkH5/KIjAWbojUybA5vMtEIvjnjqZEJ5MGWMOYZ
x3oKCdsc0hK+85KmhUAODZHg4rOiwwz7YMo2LOvy2W0PYZ6RKx5MO8FgYOnc5tvF7+wTnLZEVlzs
Q4rGglfNa3u02TDaousu9cp77WAkuPR8BdUwx7RYQ9oii8eG0qniiYIRjYfvvKId84wTiWICL6ra
I/ech1u40RoAnsDlXZEhheKmowW8DVowo3XjuFLHYg4xqeWhc2K4ixzshrucIR2R7/xey+2G8/3d
+WjEmnFW86PozlD4m2dHhoTN13ZmtwRN9gz1KT9JG06haO/NGtFY6A/H8Voz8IcvabOidnGt9AsI
7kfk+BsSmRM2CpgYwaFcAoZ0bh1Wv2Kh/wEPIJnGFyfQ5HJbtxr0VR8+iPdZZ4aGWM6uIzkAjoYD
i2e3EEjyTADdsWBUMNGT25awW+Lhmy5tvRuIHHNMq1fV61Vd1no3nCHN8Xrwqhmx0Ya9F660zK6x
zf8+UbUIQXW+CqoeLajC/t4jtwmW2RGxxo2KzG43jyWKBcMc1xn/2ZUtU2PGwQRNhrrGNz83gvp+
TKvV0my574wMY9yQYDRoTWhCVfDNhdTv6UT+NfVucfZZLRvHWH4c8vIP6VB+UznFZDw0o83cezx/
AkZHNT2+gKYWYHri8varEdW2vet4PmFZM7qaX5gbcdGy21V+98zWm8ZjnoE3nvl8PIhbuJKm7O5Z
bd+YHsHs+eDx/MGcgQj5xpK2byHEAtTYrrGxuWhsL2IP10LkGxfFZirJJxaW2p3o2RXYRGj9Il2G
flEup8icVRqZVyIyMUc1h4et2RNpnoHUqsYhv0VAFbZGY4baYu46mjtW8L2xcGT8odmYLOLKzW/r
pve2XWfGHz1LaWmuuAznqsuQLCDO4aPQTvRj3MLIdivmGU3h7itbMM/AtAyqMJJcNa/9uVHq4nLn
J7goIFWaqKDw1DHbCIZvHlURPKojSEDk4CIk5EKogupZOvsP22jKVfEahRRiNGi2rE4Mg6b59KJ2
9XYbIVHIICQmNq+cBieYVbpsHj0U+omBMc5aObhPD79vpoLS7VLYeD5hArkwVIiWFAgbi1TNIcBs
IMTtQpSoq/tEt9vAX9XtXFjDo+q6guNK/ybEAwhbPDFQOeQ5L9MuVSDaoivOp4De9GZ6lWGsPJS6
e23iK5vU+jxKWVDxf2tKBMPnrrezq0zju7tonjJ7cmQmmwAD/pBM84lzYgCwC29nVifG/+rEj9UK
gQJpPjGnCRoO7knEnkpMe67n2lfp+Wv2zPiNLAvYqey1K7s/+UzPbSegl9I9byb+P4wshv3o0z2T
8CjpFtuPP39i+HN9rU8k9oIpYrUqZmSFRPaT/9XT+VTPj4/TkJPo7p/1RG/nr3ueTEDSmoL9JQwY
uSIe/EgM95tj+5KxpwnS1/fQDekPzwr7UFG+uufazeVQd+3oa32qt+O/E8eU6U2v93as6m1d3Z/B
RpYzwtd4LcIM79oneues6btyfQY3pNlTY8tglxN4zOBXp9O9/AfPdne+QO76h31FzOFuPju46nD/
t98BGOuaC5u3XBLHf4IDvy066sh7DiObn/RMKoE2Hkp1vJD+7I4s9HeNi9CmTuw87aINFq/tyvKS
gPK/suoBW6biZOd+Wmryaw3nV3sxXKp3KKQnuBhbc3qya3nTPpBboU/RgF78+i97Jq1Ljv/1iYeo
f605wyka1bMt4cSLuWnP9DyERSAjcPM5tF+SV5ipanVy2iqv6tyQ3xwPGMXAz3vGr0J4UIyNH4GX
7l5QbevreE4FFVanOAl4JnAToXL7x8+eGL6q9/rXFCK7+O0nTnQ+03uruhO003Cv3sHBdWzUNLLu
pA2PzhZtRsK8/JnEzBd7r1xP/T52RPCerVoc4iHeix83nJTRlS/0jH8p0YGYBIyO2Ioh5szhscUt
Jlr0yV/0THop0bqi77Wc0TKi6adtyueQYtiR8M3jcXu3f/AM3ngmWp8kDZRgJRj6vKp6/PmezhcT
nU/0PE6BHbgeYeM3tmf4s72tv0ochEgsgKnGzBGe3Z/3THox0bqy77Wsstvuhr3g9/vlOa1fqMu0
yHw+gY52I3NGEBNcRBrQ4ho0n+z5s61aCKE5HqrHX+iZtCY5/Jd92zDNVt744/E0BX/t1Z7hzyWm
Pd87B/smDGMEVvxM48Gz1WX4jroMn/Uuw6m4NCjlo+Etv0cvhY8dSHasySCkHz2Xrghcg7Gn+qa9
0DtrXRrX3YKzYwvz2kXxfNpf0mA/Q5dpPHGA4DdhnqpO3S5ghrIc/kcJ97WecyEzsxLkIfNnbyWf
x5wUr1Gwnx38nFgJ01i+HdWEpSi8N7wJXfNSX2x1P9CM64pePdLrMoSKdNnwpp9Kl8EcEudCMIZa
OZvWkTMNfq5ibZwr9X4GBqRKfhasLNcx1OKBQrElpnXBMlrXwxYr7eo6CbGXwIlUyY8SWKks103X
4oFCsHFiQpeqpHU9bLHSrq7T001HcHIuSli/nAoxsF3UMicIJM6FKJNVLJWZmmpwMXQhIec/WqHw
DIAoU4dTLnSMmUOi3Zc20b32QHLOfjW85ey/OpK/L+0tALIs8Qf/sJOeT3f02MviVmtf4QQsxqO3
8eMvW6fcHILxxM5/GwOMSp/dnMbtUCU8DOGYv9dbfF6+t19dmYH5/ARoGG/uSC93jBUJewsscsIW
OdXQCKZDCgxNpLozn8ZcBDyF4mHcj4LBy0kzpS07sGyjUojEduzh5XdnO9bqcYGzWlFuWOfTyrP9
r3iDqwq/9nri6+v7vvhGsSbUGN9Q7ad2qQYWi28DgJ37zttF0pDIbVXFNLFR6bW30rROaxqrDmWw
co/F58vlQQU8IWu4Yus4I/KjSdEfTY4MVY9ieOCGyG2vJNal8bgcnhE3C4nMNf5My1VuqFa7GxLf
zW6E/nj4c7SpM7CUOqvwr+4ty+PXjiOigGX085OfhxbLSav2ZTF5oncojrGwMzIO94a92X30SyrK
/3bho0+euPbpxPam4N2jwj+dFl/crqp8zfkHuH9N4/Ov0Q0gho6AfuLyqhytSgQ9DBQDKHSM5Ydy
FGOUzCFwGoJKvUvCuRZUqp5lkSsC4fHZHqXhWB4AEsfTt2HKYRqb+1U1kODIqFUBSylF9ABNHRiL
5Je0bZwVW5xNmyu7h2/Igd+NQ/icpVwBOiAmM8fTy7o5JvP37SJ7E9rNz45VPZQ3Pjkxiv59dGIg
T1emedYZ2sUL+aiFVaHMkf7rcamgPpt/iGaZBHLmkNAwpZwCHphN59Ov0AU1bFgYHYSUOY7GKipX
3Ef3bgO1vt0uBFX00QmBPO2vMs/qUHYVO7G6Kf8AT54Mr1+CVklkTgZ4LTJVewu9mU+jvTl7OaKO
FSLnP4Xq0+8qwE7hO9uVN4aYn9/Qg6eIO48Ztw8PPTg59nAXTQtpMuhol6GCRJfhBlyG7hgye3p8
RgRXfT91hOKfiY/pkALBRwlb9Na4SXpiwU9icqLmJ+rqJ5YqSflgDO0z91IZfmmIhAp5XvsDA1eJ
oNLUajiXrOmH/+k1yjADbyYpMaci4Z/JcTK/bbvaIAWqN/M/1yVuXd0/a4wXKhNKu6wsVFhPWS4w
BDkTbFpHzjRquUoEyxTiFAycM+dJ+UWVEEpBXZmIgND/xDQI/Q88J8UDBiSWqocfPEhsnQlVUFem
y7IGzhkkY9Bz1HKVCFaaAQMSS9XDL6qEqNRZq8QXYaqcT7tUtKrd/Vg3VuM7N4ZzYjDvHhduyxQe
OVLkJ90bu+L/dDY9+2Ke4V7DIgJ2GPVlMRmP4KkCRYvntS8mbZzMJVPDBt3ivBQOTJRbKcSRaIwz
Qsi4FWl7sypWmbOm217QaagR0ivVMaCMlYBgDUpJOuttueByXsVVCmiIUSLH+22jzaJTtkvgVSrR
7/TAWYH8M9KCov012jti3QpeQBVmx4PK2rDCL8/B4LRpfOeUx4TNwwDbL2G11hNZf8KePYIWnHuZ
FRszR4TVGr619GyaIEhqOSO8zMmtMO3b38w+M5scunMXrTlREoeA0DEY9r/tLcydHLzyzIBxJDLV
MhJHM/f4+FnY8wbWV7BFH892lGkpYOKOvqbHWdoe+mNEBt0p7Sf22BGeEKEhjjNvZNM3Z0bxLFqS
qEphs419jBCntoNnvCEdoWtwQ6FTYx9kGJJX9VlTXK/p82BTiEMwEpioxmHiwCmSmiG5z7yqQM8o
PBhD1sYdSGLPXfqCBtYPGc+QK47TQv5/bc5+F+/dwoHZ42P4+6pdfHxt36ePsWElwoIsowwhiFqw
WOKlzb1q1o7MJqlge+Q6PJtqqQz5stYATbbpCx8X0trjBQOLGY7BXxe5fmANBTUZCpmdymAeAQeC
0TEE5APYZWbmZHPcL6y8qLrsjNBXRxjVI7MjvMygLkvj+qqaTFrzaEHMeoZ28B5XlIaCX5/bjHlz
iRx1h9ODfrLyzyCnU+C3v4a1TFwgGmuwI/JgLPN5TB4dI690dE1s6tIYoKIV8SwXBdthhewfMDsG
Rkgc+eu2Emk+gRSLKGbftzprLR6UJzL37Ah/Y3IQr1E+yw9MYlpp+Ih6N02jBMMzjYeP0DTpWyqk
q4RKBX4dSBW6FjadtRZPrXLISit0HpTjtDLpPA384jpxVC3/1CqHoCjReVCO08qk85yq/yu1qUcL
9boRdZrqLb1FjO8tHdEHQ5nPy6ULnlDoK+fEsePSeKLnlpzx5bNavqPWJ7dt65vmPSxWs+KWfXEy
DfbHjmTXJG132A8FP4p39p3R2zfk7hFJPFoVDPeTBfEOP7uABzgj7hCprmdzaitB90dpaYjICsHi
ypD7yKJVlUxWBExVgqVcWbMdY2IwOMcyVmD8oULr0emR7DG6+Amqz+xBRTlAFmxavWC0woNTJDml
E3MyHr+wRETl1jl0f7b9tXqs35woZIxwNJ299fl0P1Z0TQPLqWOxpJEpqrWZ4Hdn0jwDaerM5i/v
TdwHivUzIbYUcd/OzNcmN48eHf1pM93LXtzpvW8SEXEvnqvwsny4Rau3qOVyyNhGq2P8dH9+aXv4
o1OjxjDT6MncZhr3owoJbOHwN8+JDjGMvYcyq44UNh/NT53RdhO/I2cedZNjEjnukZme/HLDuBkn
XOVh5qofOcaDwi2Ex+MWZL2gEvwgEFQCu7SclnlYg2Ij2MLJGrkWtGfI/eJD1W7Z33/x/v55Z4Q+
3hmePzw0LBK46oL4sv9KsqiIuKdKCdqSSMqc0ujkSYODDTOE4OCuxBf32HgRpGCYY2LGdnx9DtMe
qt39NvohnfYmDabRydtCwWCRhjS7zuOHOSNrH1Dg/ck0Cr3Upq6og28nvrhb2aVyc0zUs4sz3QNQ
7vkBNdwv3z5h/rUembQApiIzXVxhkn13Ts+CDIyQkmbSgIkIqlR5Z5inpeZzC1pmxIxMIverfblt
PYUnc+FfXqa+mHe8yzBgrIAjKPFlmH1CnRzck3zciv3ZmYGbLmr696f6V8E62XUef6l3Rc7kj+7x
QiRmOGsx9pXNSolRaUGm8EyIoifUjIRhe+VUi+TBJpoZKstZoagVgmTwzje5ZEz7glj4q7PVeWmW
UTMhd9VZVd0+LjovbGfUKqMfKlRV2mVU4MEDXQ/OWvwD4ifLA6QyWZ1T/FDGI+W18JxqeS39Opha
dJmsziY4y3ik/FRx1uKvpV8HU4suk9XZBGcZj5TXwuOXg6qScAF7OkQ1iFzu/9CbbOuGi+PX+FLW
E/Mxz6DlVswzFnbG1TzDfnLdiWnbsXlOBbFrz7wsZM4QhawhEl5E6+TF76xLLXsjvYT/Xk1upDt8
8HMTvacxnJnOftxZrdCtk2k8QnpwJr2FVSacFC4zK3yrbI1si1xJC6HFzf2KFVmZXVWsbrbWONp4
6CUIISHnP6ZVGZVACevhkrJakQJhOPtTYA18EpDo1Fg2tum6ybEbugLYV+pCVeVGuwcVD1W1UqVd
wzh/gjfytYVngSwUnpDHeGjOFGk5JBYclbcf7is+3FM0RsW+MbfldvXVx6Nzm3FMHEmvxH4IK3TP
RRG/vZBiYLjj8uMlTnO5p7FdNx65Cvf+XO5H/CAeNC9TkxiX35Pard4muG+sxV2KWK7eoXR1NWEd
6zVelPeajE3H6E0sZY9/uf/6d3L3Zcxz6A2U1xEQx4Y776fJ7p5KXU+vDNgoqvjXk0zj7mmlVVpz
ynCqUy+o8ENzStWDM1RQeaj8sOGGSHOEoYww1Sp7MPhJ3Kag0LQu7VB68c5oZHzzx4esOy/08JHc
sk3J4U8m8ToJCQ1x49AV8fzPTQPDsMjt4FPabu2iqd6BfueJQ3Tn7BgSWJEqUv/22h8/t+XOua23
qq0tqOK0JaEeD4bHaJ8skmPdPMld+FhF+0yNluGxb6n7IyrvnhIFmEyygC1TlMii9+c1/4mDym57
YEUSRmHa/vg5LXfOa70V+1CEWcSlX6Bc+kWPTNLgReZ097pWtr3Ms8sdAdvRYVHyBiXr1iloi3Mg
4ahAtf/hmeSynbnbjtkLu2jvF2a3NGjwZehtM182hi9D19bh7vwtryTplWw8+s+4JLAKQu0zJzYZ
y8mrxYfTgb+8sPUbFzYvhoRql3tRgKtG/O85QircVIq/fPTwuPyjuK7MmdCDEse+5CV6jeIn5se5
aTyJHeKGMX2CupapJHTrOU1Lp0f36aFS1mVKkNvl5ijR06DgJ+SMXxHQz2pBMH7kZX9SJQQzyKkQ
leWoktTAz/75wP3vd7n0DRHqOgREJIEI2jSuX5+68hMto1sijy0N/c3xwrtFc8IwfDKAOvvfNuNW
af71R/hZ2ZozvbV7plJhGcE0ffvnjImvmB1OHk224DctWK1hfLmLHmQxTbmHY4JMIjn/sjs/d2po
6qTYwrfT6jkDZc6dr2Y+tiA2FZo7893BYBevl0LQcf7+zeyC2ZHZs9p2Dsm8Ugj83sQwxppj+zJ4
WPdXSgHHs0tGTGOvuil+dH77xp3JObupzHWIAsN2I4r2qxQXZdKFXAI24aQS5843sksvjM6Y0baz
LfNKPvCJLpoZPLUj92BTkKCe07azQ4P6TuY+x7iWNXg41c9xKUNSjnuD6b5SaRkR774w+PQJY9Fk
Gli3badvIBcKmEL+Pw7ZN40KfPXj7ZfuyJxoCn20k+4xr+7OLxsbv442KBbu25D+WqFwYFnL6KHx
jWfm5xxiYdUQvO+ArRHxAwtCD+ADyJyxfFfuKvXC5eC+DH/Ld9/stltGmT/41Qn6IklLKxK0oDIe
r1F2ql0mQRVPAUKOj4zW9DpL20AVn3jHf1iH67w1s9iWs42XsuZHJ8S61BQwhIdv/pVMAz+R1Lal
LX2gKbKYvv61H92MQHJncuVVtPHTm4pJv4CAZc4BmAgtqEbnu0NaUJEDPGbRgBIp51q9ikrs9T3O
7BHWdZe0du0vjB4dwc/ZoRhp1bHcQSMyekTz0fnZXx+3Z4yNYKtEIVmAM8dyHM5TcSgLgUoz3T2C
oW8sbpm3qzBlQnQqLq9E+rbjzhYjs21meGpHU35R8Jd7C2NGR2fDq3b+sX3+AgZZzeV+rMLgzsWt
5+/KdY6O4emfEpTncyuOO9cNDXz1Y23nbc/iu6HLaXnE+RW2gzhqOgIer3Xu9MQwVuz17H7Us4tH
BbarFPuZki3vF3RZwagemW97dsv7yIPBjrSC3/h46yXb853jojPQw4nMbd3GwzRiWddfFB++v9A1
JrpAvcILYf0Gg0bVyxCbPOIUHhRdZvGPN2Q2z4t24ZusvT23vkb07HPa94xIv9hrXTGJuilxKH0b
ekJdkO5F8XJqxKzy+L9wBOHARLA0xjT88InEDzeT/eX52XW4nKJWaCaS7msUkivVsOpAZtvsyNS2
WN8l1n8ftM/vigH5iQOZv9hjf3xGaahIl+kaGImorcTJzJXlECkDKaeiU+cZQE9VftbGeT2ytXhq
levYdFs6GJ1nAD26iDhB11mPbC2eWuU6Nt2WDkbnGUCPLjLo+HXlHs1PQN6ZHGG7mO/8VWIdfaBo
jRsanj2C5hmJRO7bT/dej2XgcAjf/iHhI5Vh+DoxZtFfxGrhVV+lJ89vXkBDm2P+Pn3W5ryEr07Q
fiTODePhPRl65ouF/rjJoGUAlbZ0p0PP9x8sOEPaQl1xY9uhvDw+rNiXuvW1bMIwu86MXTUR2xSc
XfuSH8XvbXiJ3v963YDSgnqpcc+eDB7sgkFr9pToNSjUn+NNtuv0edblDXKG1iiNftzLcARgZijF
j/Itx/pv2pxxIXVh6mOv29q35F2nCtR3XKjSUkZN6NWiqNsImCs6si0U5ocMjVw1OTIEjd2TnLaD
nJFV2EgP9k6u7/0BbYm35k5uWtyJH+qwN23tu+RI4Jvn0HRw3aYkfYxq5r+4iVaQ8LXOl9F89gzO
M/lXYckyR3eE6YeY6WcDstuopfavsGsVSMgHSE6VtZhe2sEaHRqBQkpFxeMhxyQSZZnuLI3dZIcU
kW9zuft2oMqc0dV00/RYV6i47gBxduL+50aFcyxtoJbmGYXiyrV9twA4qkhBRRWJas2hM2WFYauv
bejxFFMcCar28qBSQn4GvCzitd1b9TGMPt4DC164fVNyG5bfIsEFXdGumPPaUepCaqCdv21TGu83
hg2PXD09Rh9mJ7JfeTEDbffsLYlDMqmHk20nIqGl02P4AQ/8tspNz6TpTb1TmPZU4rWUg729S6c3
4ac+Cun8Q88l6UVYafr8+r6V9G0tvtbGT7ng01zqRb4crn+x9/FD+C4pcPnUJppnFIpPbuhdhiUr
tSuCGgsY6k+LzGp2n0/epwOGAT6t7BeKNePzL1eNTOobcrIe88TuJe47hJwVXAwHxs1EInvrs+kt
hn3jmn7sXBo2NHLdOfEFQ61t+7LYFhXtCN8dNLYcr3YZYtupSm4MHO1X3zRZn5kd3XKk/6ZNGXTT
uFGxq6fSl8DHjqS/uF4tGKa1i8IdI/X4t5ZgBm/n/xM/oFI1cTFyISrZxI3K7a7/5SWX4r9na/J5
WqpRO/RdP3MoFqc9TSGBr+Kvmh4bFzGOHU3/GW13K3B5lVBhJJUwqpYIbCEq2aril0LmF3EQqOK8
jEdOhaiURQmrqoRRtUS3W0tWzIHQ/8DPVSIIbYyccxFk03IqBJfXg4E5K/N6ZMUcCP0P2rgKhK4H
hb8x/JUtAqhPPHX0F0lvXbUaBxYPr4lb+LGA/rS9HF9fMOKqnJWF0jxUcTu58ZWcXOLx335W883D
7Nte6Me3JJSGNTkXRjNHkvzTn6rIvKbNajKcHb32KnVeM/N0orELo8a7eWeLuvPV5NcrfNl68JvX
tFtNjrOjT0Hy21s3VN20ovHfN/xsdnjd+hPzjpo3Nhs7EvYqddesYFQFAevGZhP3+7VJ2/99J4aB
eh9PFemFeBdedFbxG3f83sAVzUMS6Vmr1K2uCrtf9IBx8S0AACAASURBVOXprd+ZHMTHhzNrfahS
y4cKLb5eWY4NCn6y1i5un2tkL38y1docGGE6D+N+CQ1I+E8ilrTPdbwqw3m4RFDx1LKlKimohtu3
Pd+/XJ1WCyquKM0H1AlW/FdzkwPmkWSRduqUpmUtgRGWcyTjrMh5j7/oBcRhzHg352yp4KeWWtaN
LWY/PsrAEzOb9nQujFmTw6qKN+545WXHmWFrXszsTxfpsw4kHX/IurHJ7C+U+bxMgXaqZBc2KbtZ
e3nG25ChsQCx32Vor+M8zLMVPd4qI7NEQ8VJONy3pNk4kGjdUMA1hT0lZBrJ1TnwBaXV6m3X8ZQY
dPmPpO0VmLYym7K1EIslBWeVTC49qYUj4s/Mixx7JzFce8LxKiuOdWGokOKCk8m6sQfkCDAkj59C
JWT251UU1dBdb7Gnk/hr+rCGslOVPVX+GmZLit+LzlOVPVX+EqA1Tt6LzlOVPVX+apA/0Vy8uzPT
NbotHo8HAu7U4qV1G2kZkAIUqVYYYWDq9QbFWlBqlav4J82chPAK6Fgii+GVVtFHtodGd5jfvdiY
sQ2/IRC6/iP0QnYrHtwZKok5eMNKRymphd/H4KzCgzmzkQLPNCupWu7Lkim/IerMzXz8znK8/lX4
VRW/DqBqgir6dVmd1vHo5fiqAMu5BfvhHg8wN1nnZww29mqUtqtu/KvooQ+vx4NPTIlMHhHGq65N
O/DjoR5ov42lyAzjvjf7vzy5dcZZsYV7U/Tiny3qXDoGXU/RQwtmvRynAbPTMJYnvagTnSDKqspk
6b+bkrcw4n9X/8gOFVQLVFC1hq6fXhpUUH5K+D3+VUnbbTjEkbxykCvoJ7+0hCpKzir9PZTeduBH
J/J3p0BT6v9VGZsCGIkNKdLPPLtbcjZ9ES2JjXKO3TwcRWKUy+UUUp4eUqBqV/Xbq2QjlKgVgsGg
X0xjeaJq/GOZx364V8GuipxV6Xa5JEiwlmPvkSQXp3ZBVcHv1UKKazmXU9HGhKnGNwZWGj+raPe1
qnDtugJfpnfHxUfxgyssxcWV+KUcRBWcWrzp+nU9LMW5KGG1Kq+IPTf+V/UXVxE41uUZ0tFqSlxS
t6vX6hg0la5urq1VrstCJ5/qykGXyA50/ZZ4u0wJK2dVZVU6hhJbnulyDFq5LssmypSXyzbwVzrI
LVFTDYkAIfQu0WXB4HcnHnG8EyYoR9LK9TjSdep62KhrGsMrNJi3bE5+/PKWro7oVy+k+wHSQfxo
B15OD5xcJR5IhqOLgMGDXIJzsPF7Nj0EDEzgedXlR2EQX/GkEKes6X3Gv3BodLH6iSTsEvgL8nY9
+Av/72u5x2ZEvjsxMw2/C8JJ8Je1sA789OkHLVmzLzRF2IbJVVLGLHoOwHTqwRZC8dzy6smCilWx
AtCiRlrBhS6bFue/tfEjyJl4f/C7/UJuGcj/bpeWQdJPXcfSFjJsGQliF1FZF7w/+AmCa/rk+LHp
e2mLsXdHil8L6vA9JSpyGGpJtbLC0csmOWzIuiqlnE78cZXa7ynSSLeMMev5YPlft6UwuRljYYs6
zgZ+1ycnjx/dneW0q+TDHz/lDaPzGqsa3GYJKTfiwQ9XopQvCS2n0JRxQSsnXva+umSggHUSv6eG
ibLyTH7Sf3XfOCw0G29ubGfT8fzD9CDITCC8xI+wyJF0PczosusVvyn8ZXhKwHngcTwZ/hX7+q89
kTqAT0Lctr+/+FftT/1lMTcuYH93f4FewXA3EV7dh3TuJoV/+e7U2HyuHcvmws+e57xE9qT47etX
9cwMGMv9PpX4sa9/RlUJFtXtZerdU+ATNsKqTtK5Sf/17o3Dwn5Q0SKBehDxWIiRaclLFJ0UP8QY
lsrJrOAnxa5+dtSp4neFlR7OThY/ikt3xPuBX3WZZdBrqVrtKvFhHfj78595usfgt04lsu8Hfg92
ffj7+rIPbcp8F5/jE7/C48eq1796FP2W4de838DPXc4BMKj3LyjWL7vSE78Lflfjx2+hR2GU9fdq
1BwmPO7yo+7LWsJ6uS5/irK6Gl1UV1kPj85f0v21hPVyXVgHofPUKK/Foqush0fnb+AnDyDVcpxW
rpElbtP9WQ+Pzl+iqJawXq4L14iTWjp1NbqorrIeHp2/lq2a5bqwDqKWYa1cI0vU6yrr4dH5SxTV
EtbLdeEGft0bitZdpbungtEr0JlqCevlnhwdT1FWV6OL6irr4dH5TxXDe5GtB1s9PO8Fw3uRrQeb
x/OJeLW9Gms38u5q9B5W7YBF5USoYFBHj1I8egXP5ZEL4fLDJhJyIbwCv5inkIqHuNSpEK4sLKJI
2SVIJ8NWDw8BIT5KAlsILvdhEyCvFd4RZWU45VSIBn64zXOzR+Gci7wKcbsQyt1ljvZOvWPD/7V8
S3492TVCHm74H05ojD8UCl4wICQa4z8N3yox4Q403rjjHRvjD3zkDSEeVRo/rhvLD2qqgbGehnte
SVZixObpkztBGQ/Vy9DmRSopUeVul3inxMmANIJMeIKK9E9JjwdJABAqJDKs8jIe79RnUIwiLgqJ
YQC7SnkDv7hLHKjc2fC/G3sUhiqKhOC4asS/64fG9dsYfxrjP99bMVOhcUGl3/n7l9fQ0qO+LZRf
KrNH4A41UoBbPEOS+rtSjcdlVrK8mYPyMn5V4GaaLNupMFtqF2O6h6fEFptgpQ38Df/7YduIH/fS
bVy/NGKUpcb4w2MF3MLDphDsK80/jfhpxA8G01O7/5ZdbnQa7GoKXIz/g7HOhKkZ5hA8QWPCnVLU
kkfgctSCQQtffbpQUq7pOWVbmmwt8pR1NvDzkKQ6/SR9XcvpWnnD/xTtSLXi6r34SpOtRTb83/B/
rdiop7wRP434OVmcqN/KrsKkVjV41lZz9NOmCHyzcW852gpHiax+W+KB9aTDKzMAn6aIrLAJVc6n
1ARVXtnlmmgJi37SwM99rfvEdSkdGv6v5h4t3hrxU81B7vJJI344UuAHLWRKThrx04ifkuDQbloa
WcKin3xY4oeGgvLEUw1cGd5woUj/lCjNBxrpLm+4jSc+8gknLiS6RMA7dZn44BWCE6nkGtU0erzl
Rzapco10NbnMGgaNbOD3fFniFK87uJJ96jFWOWpO10hi9EU1/RrZ8L/nzhKnNPzvuqURP+SIemKj
Hh4v1sqP2kWrkcTV8D95oR7f1sNDuqolzekaSZwfdv9XtFZNNbAsRm3TVyN0Rs0HGkndQFMKJVs+
RRDxEgHffwMtxLEINNTRhQPpqYahBE4Df9V+b/hfIocJLWg0shH/NV6kNuKnET/igZILpjH+e37x
rpH/K+5fbqN5Wyi3vJ5br+crOtYIo4GmCJ64uxbiedxfBfEYBtKv8ZToaeBnzwwwRfNcV+I3Ncv0
arRjrf7VWRSP230N/7NnGv5nPzTixxvftCtGI2v5pxE/jfhBbHAYaPFSTv42x085VpzrG0IFuhAs
gDYjIReCy2vlIi5ELc66y3ndBbkQVUTFnBDMJLCFqCKsFYm4EFrl6ZECW4gqesScEMwksIWoIqwV
ibgQWuXpkQJbiCp6xJwQzCSwhagirBWJuBBa5emRAluIKnrEnBDMJLCFqCKsFYm4EFrl6ZECW4gq
esScEMwksIWoIqwVibgQWuXpkQJbiCp6xJwQzCSwhagirBWJuBBa5emRAluIKnrEnBDMJLCFqCKs
FYm4EFrl6ZECW4gqesScEMwksIWoIqwVibgQWuXpkQJbiCp6xJwQzCSwhagirBWJuBBa5emRAluI
KnrEnBDMJLCFqCKsFYm4EFrl6ZECW4gqek5ijvdqVJHTispU8KlW/xsg63oKr4Wjgb+WZ+oub/jf
f3faiP+6w0YYG/HTiB8JhtMgGvHzIY4f6m98LFvPqsZphMYHIiJTCiE+EBinbVRgC3Haqj4QQYEt
xAcC47SNCmwhTlvVByIosIX4QGCctlGBLcRpq/pABAW2EB8IjNM2KrCFOG1VH4igwBbiA4Fx2kYF
thCnreoDERTYTJRj0Kcasj7jvXTHXJKmk+aUqDkrZk3Bf2Uus0shWKGcEsFSiqBaz3AJj74/gBkq
+F1BVS5qRUl5Q3BeC79mS8SFYD1ySsRp4Id/zDYfsKtUHTSFUC6GmKUk/wDxA8eH2v8N/PBAI368
K5ev4rLrUS49IdyrD5GP1Ij/Rvw04ocvBHVB+JeP5pbya4c5OdfiRy/2aO0FCrTgTQzrYiIQvGNa
02VDA+7/424YyVTux2/0P5ZmpcaUM6J3TY2Nxf/3jKp0/vE3+h9JqevWrWcjJSfXTmu7cQTmN87j
63rup/9XE4kZgg9d1DI9aPQcT/3+67lJI+KPTgtveLP31qMai2jiN0bB0M8vigeP9y95I0dMlfiZ
DS4jgoEpwi2HZU8jE/6pMupmHo9eVkKbU0Y2PXBW6OlXeu/qxf9u6vqwc1j83z4SBuO+dxJX71b/
u7qn6drprTcODxj53A0v9W8XVXXj95zTd+tR/D/vKr03/KyC8loYGLmH3/ebknQzkg18e17rfEu1
i1Uppafq/0kjmlTvcwPFqm5MpzVw7xW/OW945FPRwlffKRqB4M8vblbRlT1V/G5Euxh/o/hLrl83
nt/3+FcNVc18z/5v4CdnloRMyYkbUyUHZmj4v+L+1Yj/imAqCRz3ZLDjB4NAtaR9gQKLNFJ4XGbw
hxe1TKBVD2ffifyRojmpI9QeD994QTC8pveRrGHEIv80I4ZZyPHe/FErML0ldN15zbm1fY9hAkGq
PD1y5HtwgM/NiztD9+/K0wk4TaOtLYR5BlIQsuC0CEcT5epuqnhcnayHwsiEBPFz25hAzkkIt0nq
XB8KPUY6kqzKQeu2SnjUHILsKiYiwErZouEAUlgt8wzFE/cWjMaOCHe+3X/AYwdqzN5IkEr0y4NP
qYYS2/Epdc78rnO8NRJmfg/43eaTnpptrM5Tgb8JrWbkA+CHVFkCs46/soGngQ0atT6qC38w9PVp
seCJfgNTDdOLLr09env1JpTh51Od4TeDn+B5VoVo4GeXnGpsn0b8NPwPV/OFXHGJn/LY0vC/eynz
lazyD8X444883likjkF1t1N3xdJmfOXcZswzCuns7ev617oi1l1zWhe1WJ+ZGn1kS/baiVHMM/bt
S1y9q4AwunZqy40jAriJPnZATQ7YXonOkugbOSzUuatwgDRTbF7VSQsASAUlvfNwasFhLnAVqTuY
0gCdSMjz2SXP5ty7NZfwaKKqKSPNpUkfbkqwwQrBIG426JrVpgKuNtap8RvWeUPMQm9udakp/ywS
virWf3+GRYy2IaGJPAtxjFhNPGylOn7XOYOGnxteYavUEVX8T77SpiYKj5o8GinQlCp0VvBT91HS
/GkaWu97JohH16nxux1XYes08NtGARFYUHO4fG7JarVaRqa9VB9+4gZApJI+ev/xMzxlmM2rXMsa
+N0oen/ip+F/xBpHfiP+Sx3hDXFqTICXeNyreT3qY8WH7fqtHIlVC9RKAl9+aDYIyrFWELq8DYT9
k1f716pi5Tf7rtfTc+c3YSVhiuPsOJ7dHg789zsYnJGcdUnnxhFGX5aG6dFnxB6aFjl6KHnD2wU1
2jKLeNtJ5o3mSOiqaP/9aS60Lj0D8xqnEDSDeOCHhqGxR6aH173ed1e3cces1nlW/rmk9bHOEK0e
5IvPbk/ddaxoBIP/e25z6Gjq6p35zqGx708JrTuQnzUmOhRMtv3cW6mfW+G/OivSTDeP4lNvJv+2
24bIDy+IG4dTn/MWVO44t+1iK3fLpvT2UOiHFzQFe/PdkdCsFswFnH1H0nfttm87Nz4lQi7YfaD/
czsxs1FtcQ/qpC00xTC2H8N8i5C7OXO5uTl3VMh4O8++xaSKnY7KNOuJBL4zrenslkBUTUF6Ernv
v55a4YR/eH5smG2v3Jz4Xj+8ZH5lRsuVrebruxL35iOac9rmBQsbU9alI4NQm0nnH3i1f/zk5qvU
wkkykfvWK6nVhrF4XPOfjwm8+GbfXe8qzCH2Q/Jzuwqdw+C64LoDBc11yZ9bEd91W5N/e4KbhhZ6
RDT00NmxKXGLeqRgv7E/dfNevCRi71h/Orn5os4QZqKqs5J3HcN7JUiaX5gS/9iwYDutRBmZfPHF
nam7jkDKvGNmy7ygfdDA2phVyOYf3lX83FTV+8nQD89vMt7NvRsPn6c6pSeV/6dXU0/muRWBb5/d
dH5bABiSvblNeeuCFueBl5MrigyDwJLyWSXK71uXPDIs9mcTw2Mj5G6A33c8c/tb2QNhOLwJ0WIM
iz8xJ3DLlsIdF8Q5utCstubwt6fFpqulqkK+8NT21N8e01aV9HiAcYoEsu2HBGi9XOcnZm81onr8
QE/5lI5EKGm5fv2SHiUCFgZDLvcMubLqVBWX6NFxlmDzVClFSk5ZL+GpGv8N/Mp1Df9zKDbiR67N
38nrlwaiKknd3DBi0B+GTs6dtmban1HozX4Pz3Uo5BABkc0uWX1iycY0dhisPZq54ZXUTwpGW9ha
NjL2910Y8J1+Nco3hQO4nUxsDvieFCUEw153GBMUa+5IiFDq7IhgBWX74WwPJjmqpClgNVvWKLrH
m6Oarfa2yNLOUCFbPJx1gqHAoo80X4sNIgFreMgcFsWQasQtqxnl46NDDftw2jYs65JpLfdinpFX
IsHA4hnxxcBgmcNC5qgm5QvKzFFxqzlmxVAVMIeErLFDI7NazOOpIiYOY0c0PTKveUoEMxO6HU7o
jH97CH7YA6SCyDnu4mdgPcbZcFztxlA1etbTmz9uGGNHhDpRSh6mSVUhldvqzrFQGvjhBS3n4X6Z
L24/UUjaRntL+C9mxzpzuWd7MSELXj2rCbO+eWc2L+3AXKS44pBd7pyW8KKRwUy62FMworHQX8xv
wzyjJ1WEquaW8B3YL+IYnZjHBK1RYcHPfqDeV64LlrqutcR1M+E6OIjxM2E9cn4c991MqrD1BOZ8
1qzxLQ8Mp46gFAwu6gwZWmf9EU0fjRumt149KtRuObvfze/LOlH017TmLyDOTHRxoL0lhHkGSYeM
Y6bX+yZ1yoSR0fPQKQm0yMQrvDvOibWBz7QeuKBlPvutt9jcFr5kaDAaCYxWO4cIhpvKlZ9ob7p3
WhTzjOOJ/PZeAj9hZNO9ZyJWHX5ZB6y0tGaZEl1Gc/Tx81R704XtCTsYCi7+SNsDo9S1w/GAhoNA
zh7gHADkFAQzMD+qQNSfyv3vGdD1U3TBopoAkS111xejVKXscQ6SASAfgEdEQAibCDbw6/5p+B/e
EIdwbMgpiEb88LUJz4Co9M/vUvy4zSs5aMMlynkQMYwRUfdplUJn4BCxgssvbPuLs6LtEC9k7+im
AW7nsf6/ey3x129hQ4evU4tCc9eRHF6PjB0ZVjdgYzG9PSmuPlykeYbXCySLZBq8Jr97f+KKNX2f
XtP7JO08tS4eahlyc/dgF1LZG17o/fS63sdP0GuYZG/6Ey/2fXpt79NKZALuaurtjNLrZvx4jPs+
qtQsx358Q88frO/78k5l1i7+40s9n17fd+duWrxpw9QHxhmhi9OcNyyAh/ensUOlpNwzks1v6HUM
vENpopLOYZEJWAI5mOtVjkfrOkdE6UVVIr1wTd8NWxJLnuvbDZABa6hhPPJ6YjNQRCLfmx6/YwLQ
OSs3JVd7jfUM0HH33sSSl/t+/6UkpjVIm3f0/f6GviUb+gEq2haaZRg5abjgV5ySVXHdS+Rt13UR
rR8hEwoMB37MOzckbtrcd43altvZEURzOOG1muqsnsfRdiNwCTorEPzEMMgU/+7F3s+9lrx6Tc8P
sMhkWOcMYUeQHKQWrO65eUNqD2tB7ndK7x9s7FuyJomwMSKB8YYxa2TTrJBRSGVueLHvhlf6bngz
y8trObdfPMACab9Svj41Wb2q2/oWFCZveLXvk1soSoe1YZdu/nMv9ycRNsf6f/+V9HY/usy7ptGe
pMMHk1esS9ywqffmt+jFyqzJTfNwqExsEbkQzCPhIcTA5SIuxOnZgjgsIh9Aj65Z2IQYGKc0Rwjm
F3EhdCsD84gqRs75AHp0zcImBNfqOlHCp0LgVBiYX8SF4HI9lyohuFZUgUAV52U8uh6dFjYhKnWi
hE0IgVMukXIRF0K3wrRUCcHlogoEqjgv46nUVr9OcApO3ZZeLuaEqLQoVUIwj64TVQ384li4QpxT
6SthAyEuFYL59VyqhKBaNqDzEa0G+krzio3Hbh9ZVYhF+2e704/vzvbgxhGMPjEjQvwFe8W7hdW4
0SFVtduffzmhbsAxNCm46AzTSOUeSzt0s2fQSlQTt5/dy3CcF4/KTcBj8ky88U4Gyy2UgtSuXbij
4+A4u5LE4d+EcILkSfEZn2Ih537cbXC3fjcP+MkTmZ/QbcXYkZF7NZ36yQrOihnJd/PbAbvE3S5L
0LF/ehDzBXPuCGrc0pGYVNlPHyq6P9PqGAeO9H9mTe+XX8/Naw1eOzJy11kxuiPTuxUk++bNacAZ
OyyMmdzu3Yl7cVIKmydEz+7HiyqwF/fg3M7/84Einfbn31I+U6pI3QCJXMf4xXVkyHMdkZp00SHF
kciqC1sfmBy9KJtesPrEH7wpb5fsp93Xasa6bmIMoUXF4nUv9ty8LrknHFg2LPyVCU2LWryexq4b
0s1SzuZ+3RJVZE5k7lc9aOSL+4nVQYvOU2+Int3hwt5+NL1ezWz9+GE1opzix9mcdh55o/eGdb1/
320s7gjdMCZ611jqF2zPoEQkxw4RbnLMoeg0o/BP2xVMx9h8qH8NbFmBczEDg6BnyONXx8pyt7ri
IGEjBLOIWiEqRH3Tp8EjIkLUb1dHIrCFqF+PmBZC1zywHhERYmD+Ss1cIrCFqF+PmBai0opUCTGw
fmETolKnXiKwhRhYvy4rJoTQawfWIyJCDMxfqZlLBLYQ9esR00JUWpEqIQbWL2xCVOrUSwS2EAPr
12XFhBB67cB6RESIgfkrNXOJwBaifj1iWgiSZUWsxc8xuDKXXwTqSL+NgRlL7lQJQc6JxVw2Ktya
LazsLtJdnJL9yF6aU9x/uPjE/KbmIXiGzm5WFQNk4YCz4nBhaUtoLr757A2PVQ/6hpppVINDN9E3
1DgPnTXv+nxLU1a7MTNosfA7IC5ydfMeAI9UZeTxHxtH3FsPVcaFo5ToPCM81DDWHMn7sMvcGTS3
H8n1TAuPHRlq2+0soElV5ie2M1/Tc9XE+CdH0E4LP/HEBqoSmWcS0aV0Vy7+mDZDVE02phZ+sulO
zInWbKr3u8fhHWk2oJC7rhOPCeFx0tHO3/VW9pt4PxUKzOqM4e9LdnHllsT/z967gMlRXeeiVf3u
np6e92g0owdjCSHJQgOSbD1AIAmMhYMlsIXjy8U+8JFgJ4cY+yTG1+FLQpw4jk1yHBJy/Djm4IsV
PhuIbclcAw4PIV6SEQ9JIMmDZCGkGUmjeT96+l137b2qVq+u6t2qGY2MMLW/0e611/7Xv1at2rVr
d1V16W64ASZ68+Iyh0x+/7gkFZWxoDF65/mR2rKEaGXtYkHCinhO01HkjiocBX7sNIxdg4WV08yt
sMPZ+NGCgT9fXLUwWi4vtJ60OYRmOv9WkdT0JVehRe0kJTN+y9rm2lJP7BNIZP6FFQrlNndinCq0
F78zM17+nTlRabzx48zMe338OLfIvKrh6BhK5mH5EKgJ3yK+z7HTVSB42wWxWxfHNwS0T82ueqAj
tkb2iyqdFY9a+vzL0ASSZRtDhAQBnsw4nhYPMTSH7xTv5cg/cbygmb+D5ThLLhj9lqg661v97BOm
V9sMK0MSd+LN2PCjaCK+0tvCtkOKYJDWiZ+55l8YrAjSsjvkJZzbZkfMRZWm0xMFa2bHN8E6o5Df
dTT5/TdHbtk+LG6a4PkYfgPcEP2Y+e3f/9/lUxfCPXlDIVf4LZ0jKTroIpilLJ7Kwz64IyAuOEy2
vH1y/NPbB7+8Z+zx45leWNH4/BsWxeYhG+wsTDvlH4Rg6E64y+bTjp5KPXhg7K9eHPwhPCvKC+1i
CtsS5HUWDhVySKRIn1lcMegdCdUqBlY/NH70by2JwzojNZZ9/NDYv70+9Gl5m8nObhs2In5xS8sa
G/r5cYEIWRGWmKMSahJKun8nDYwfahLQLYVEgjMc6iLBiTnbGgqbBC/+s51zzk9pJ8HLP8/P2ZYp
7SS8t/JfLj8+HScUW18ms7UPzgS+Gy+KwZ1+66Tlu6sjBqcouKD9o5x2fnOovS68qUVe+QBMdegC
OH/mcs/J69itAT1h4+RNcFrI7oITcFV4PTwmOZJ5iJ93oLfCNEddKHBam0w8pJermXjcL35eA73V
ofl0zj8tG5GAgGDDdyk8ajCW2UYXFUy9BbBMHpWPwa5vh1VY/olusan4jAgIc+QJct9vRr50KP2j
U7nOWGCOCEmHO0twmeffFkVgLbPrUBIe4Khtqvq2eETCOn+AL9wKobJ7RB3VO3vFuiIBj4XKApem
zIsotq2mJm0IUZAAD5nWxx69rPaRDwZ39Ge+fmDsuhfwGREZM8LI3BJqqvzw447cUPKGN8e/cyKz
LaMvwpUBABBD/G4EQ3tzEJKuXz4n0gZ4EVJklUiZLMRZjjkr0l/4378e/fo7mYcGC8vawjCk+UM8
xZUossHDzuJQCP4xPAeK+asOr6kCqQC3jETw6KWcL5PA+UEmJCCGmiS4t+VIMicBezF+qOEPurC2
YTiPSiYTEhBJTRKcDNRFgnuMF3/lPFNKSXCfW44kcxKw18u/l38aEiTwkSNk7LBrAwaOHpte177z
ZnLdZfGWqvC9a4JHB/LwDN/sOvj5AOAKP+0Uq4mH38msXxDqmJ+4rzp1oBC4aqb4cePRrjTc8sfX
WY72jV29N2POzg5+UMAJeH21OK/CY5K2ft6kxYC5CXy4c5xTBqRt69IF+NlmPBrZfLFvT1JfMj0I
578SWmgSPxLaGLgyFpwXgE3ODpXFIFLWu7vTQwjq4wAAIABJREFUvecH4WuxWFTBjjA0cXNHlkPD
Ba3BN29u/M5AOhMLXSV/I6oF/KvC2pr5VfDEaGog+aWj6XmZwH0LQss+GP/U9uFX0VIyEA+GXcyV
xQ9YOAX3FsTub2+vfiCeGQ4EOurkmgvOoAyGrOVrPqp0rWsAnuoNtzRU/ezCwLbBwsKWsNi08Rzc
ODMDQFqoLWFoTFwni9dEvzdH+3VGv3xGtB0edIArZ374UYxRDBtUFBIJLCbi33F0fN9s+NFKZPMl
gc5RfSFuEVxpYGAUi+RiK/SYWGT5/q+LYg09+fbm8EppGJAXSfDFcfGG2MNLAvcdoIs+xg9+m1kJ
Q/2CxAOJ1N6cf93MEAz13uOpbYIP/sliE2xNC1UCrozhJhA5gHEvoFDZFnsnhzkTWx4zl734eTZQ
VuVZpecMbjAc7+WfZ8PL/9keP85sm1fqYSDiLIY14EAoZK9/cWQXvAFT882EJzAaxDoDXkz+bzuH
xWseDPht6tg/Hc6k4H9IaYtuEOsMY9+R0RvkLzXQkXwVkhTL8sOjl93pE6I/98sTBeHRkC9QwvOf
zAV+9RffKbGAEnMEjzwKpXicwvwOKiNPWlcX0vLufhJuGEh98Turkfvm/tSoptXCbyOnByNj8soK
cpJ3yxt8CnIohjaGr2pANqmBakWjuDbwGjymKoMXNVBhDY9kCEu4yiM/jOyL4rcY2pvH5KIKflZj
MW87MrZ9BH7BG1h/fpX4Qe9QZtcI9PkWtsU2wSWTQu7evWng7Dw5Jn9W4795gfjxKpQsbKyBeUAX
UgmV7JUqKRsaPM/Q1TP+ILyJRNPbm8KwzjgxkIMTvwgNwBIvUgeCrpmpw0zC5mCcmCKoUTByf78/
BQ8CNzaEN80Rb5tIjWX+9rUUMJg7C2OwyEWo2cx3j8D+0BfOjN00J9ruz+86Kfy31otfRBd3sRm3
+BApop1iETL+/OeeG9o+JH56CusMeGWteFAkl4coRJAUsDlUJK/QF+7aneyFyOvCN1wQW1nn6zye
gdEHv9PZCMvoVHYv/FjJp7fUhNp91uiCpfCJsb96Kz2q6e3TYaiH4vCSleNjNx2QD+hY2yiy5yxW
2GYvYbgeZPqDCEEujV+w0uaQgL44D2iwSQLSUpME1POaukDgBQnd83jxY/YmmjewQhOefFJ6+adh
T4L7PFMaScB88pq6kJZq3Cle/intJGCKVPmhBDJBv/2FU6+kKzwlIV44Af/XGtwTH08XdtN1/yKF
3hH3wffmo6P5LnIPAWEQRZicLkGJsXI9KhGPhohR6VW2XM9lzmnqMWZjB7x6wlm4X97r5PH5VsS0
/SMFcVXjzOJvC/tmBvX+dKHTmWGnXx6VU64Qf8C3IqKPZwu74U1rVDie+1LpyVDT5kX99X6jP2WU
CZtgnFNkTB/Pwy9BymUeTbhfIgGB88DPhmsj/3JB8Ok3R74zgl3+By5PtBcytz03thuQUDhPqS0Y
yEFrHB0pFF8YL42gaoNHZPNGl7wOJHRFW8tqtGAOdcuk5JP75R1FHq5Vx8l53NiWshZbKtsiolTi
fnmPiofjOUal55wcw/Vc5pxcr5JVnCoejucYlZ775Riu5zLn5HqVrOJU8XA8x6j03C/HcD2XOSfX
q2QVp4qH4zlGped+OYbrucw5uV4lqzhVPBzPMSo998sxXM9lzsn1KlnFqeLheI5R6blfjrH0y0L5
zzaMz2mtqaqq8vvNpcULO3YFxLMa4AAKN+Mu4cQA77CC3vLF2D2CX4FZN4E5D+dnWDaVq2OYYtty
MfOQXMafL+wwz3Ony+Hp4u/KFLrgrhTuCIjETd54wDZZFX9OBmwDq3yp9My8c1wODEASGF1TE8B8
2zFjjKG8qIofadEm5G+JBm64qDr+1vjerO+jc2Jws0kbL7xNGFUMwtwaAOUwXXA5BfRQsC7Gb1nJ
zkqVm/jJvlwMolOlJ8MKGDe2nMcme/FXyC3PlSrPKj23rSB7+ffyj9MO5AEFGhIVhg11EdjNOFRh
VHryAoIbjIU3nw60mtYnxkoRk2D1i0/uhusBjF2g5DwczzHclsvclqg4oILsxpbHw6l4bJyH4zmG
23KZ24IemxxQQXZjy+PhVDw2zsPxHMNtucxtQY9NDqggu7Hl8XAqHhvn4XhxSyi5dVpgQ0Ngw4Lq
DWiezn5917j1G2wrYAqbBO5LJXO/gClry+PhPADGLjJEc47nGG7LZbTCmqg4oILsxpbHw6l4bJyH
4zmG23KZ24IemxxQQXZjy+PhVDw2zsPxHMNtucxtQY9NDqggu7Hl8XAqHhvn4XiO4bZc5ragxyYH
VJDd2PJ4OBWPjfNwPMdwWy5zW9BjkwMqyG5seTycisfGeTieY7gtl7kt6LHJARVkN7Y8Hk7FY+M8
HM8x3JbL3Bb02OSACcpyqUEsJHAWVYi2ULgJ8ahsAUwYzlMBz/lJ5rackwAgqDhtttyEYlPZcl+c
pwKe85PMbTknAUBQcdpsucn7In7j7j1DD8b862r88Cho71huCzxgq8oVTw6XbTmkvHGMitNmy02I
R2ULYMJwngp4zk8yt+WcBABBxWmz5SYUm8qW++I8FfCcn2RuyzkJAIKK02bLTbz4MZmYOp4Zm2zL
IeWNw7z8QwagQHJ4PilXPIeqXPF8cpnbogvei7KK02bLDSk2lS33xXkq4Dk/ydyWcxKACYpfoDCE
OSdS9CRwjCrEiYQi+NzgVb54PFw+E043tlPli/Nw2U0Mqpy4sZ0qX5yHy25imGz8Xcn8j+hhYHB6
Jr54zFw+E043tlPli/Nw2U0Mk80/9yPkM/Fl57LaZ8LpxtbyIz7d4FW54jxcPhNON7ZT5YvzcNlN
DKqcuLGdKl+ch8tuYvDix4ydSa54zsvJ8lmNch0T07kJcWKMavTZ8HU2OFVbcDZ8nQ1OL35VBpx6
L//OnKg0ZyNXZ4PTi1+VAafey78zJyrN2cjV2eCc6vjlK6FUpKaetoOE0xicY90UNgnnWICnCYfC
JuE0BudYN4VNwjkW4GnCobBJOI3BOdZNYZNwjgV4mnAobBJOY3COdVPYJJxjAZ4mHAqbhNMYnGPd
FDYJ51iApwmHwibhNAbnZrebpQZcXYICNQmVt4UyQoITT10kODFTpaGwSajMTCGR4MRTFwlOzFRp
KGwSKjNTSCQ48dRFghMzVRoKm4TKzBQSCU48dZHgxEyVhsImoTIzhUSCE09dJDgxU6WhsEmozEwh
keDEUxcJTsxUaShsEiozU0gkOPHURYITM1UaCpuEyswUEglOPHWR4MRMlYbCJqEyM4VEghNPXSQ4
MVOlobBJqMxMIZHgxFMXCU7MVGkobBIqM1NIJDjx1EWCEzOlGnhdkeQDfxVcUhcJZx4EZY0EJye5
A4H/ARK7SMBeatqoEFwZYzM5bZPCJsFpwv2id2cMHAMM2LRRucHYTE7bpLBJcJpwvyDTHyCxiwTs
oqaNCsGVMTaT0zYpbBKcJtwvenfGwDHAgE0blRuMzeS0TQqbBKcJ9wsy/QESu0jALmraqBBcGWMz
OW2TwibBacL9ondnDBwDDNi0UbnB2ExO26SwSXCacL8g0x8gsYsE7KKmjQrBlTE2k9M2KWwSnCbc
L3p3xsAxwIBNG5UbjM3ktE0KmwSnCfcLMv0BErtIwC5q2qgQXBljMzltk8ImwWnC/aJ3ZwwcAwzY
tFG5wdhMTtuksElwmnC/INMfILGLBOyippNKaPDHrugPDEBAFhR4HJUxKluuLx+B5bQyP7flnDxO
lZ5vhQrjRs9j4LKbGDjejS/O6cUPGatQeK5UueXmKoxK7+Xfy783fvAoUB0jbvQ8h1z2jt/KuX0v
zj98/5py4GAy/7x4Ezac8XXNMEQNBQWobcXNqOCjjpsrbV34nSoeZQxyiSU3Xay1EMadgqy09eKX
mfLGjzd+VPMGP5TO5DhS2nrHrxx8Xv6989e7ff6qjRtaAz/gTZm9wgsXFrS8IKGMlUOFaxKsoZME
1dTAMSq/qlOXypeKxxFsGYWK04vfeeiqcuXln4Y9Cd748cZPmenGoVIdU9748caPY7CUUZxb44em
Px6pwR4LhWENBWoSOBJl2iQSUE8mQoBLI7IGQcBkDQIosSYw2qpqOnWBIGxlXcGWukhwMlPYJCCG
TITgxS+T4uXfGz/iMPGOX2/+sY4EmjZJwB5v/rQyVPx8386fxRSUSGypQaOH5hexNCCtNHMzpACI
RiWOLKVJaa1CbPzFZqlfaglBYesG48UPWaqQQy//lfPjjZ/K+fHGT+X8eOOncn688VM5P++J8WM7
71tNdgPFUslP2iZowdZDE2qopCBqKPCMgqyFzDDFyxeiw7pIAoIbjLQoU3FbpCoDYiorQqFitl78
cp9ZOxSzBCkigaWwRGQ5FHpoVi5e/imlJPAcghKbmEbCqLLKbQHj5R+S4M0/NGxI8MYPZgATgjU7
drz5/3c0/5cZh7jUwJkLdgzuFfiEa4byaUdxRCsee2RwSVxu+lPxmI6kCfpEa+6LY+zLF9qSEmMv
fsqLKXj5L39oUZ688cNTQbIleOPHGz98Ti4ZD8XpVg4XnMGtkYOfJXh2HuFze8khqMB48z/sBSgl
+TyH8186CrDFr2rgWJG12C58ZAEEfWPCV63pI+nClgz1Cr1W/B/okU3WPB2ggGaZIhMnBhDQAACp
JA57QJTqckc670CcNDSh0l1J/ILeLCiYTS9+mQgv/+bgkCMHR5FIDI1/b/xYh0/xkx1I3vjxxk9x
YMgJH1cnqPTmf8gDHC541hI5eR+cv3DXl9Y+nFpLlVbLH9iyon78E00//0jjjz7S8PNrmoavrLkn
LnMlpuXiMxO3zqsxPtH8ynm4JoUeOU1DfmHMmbVMtq7f8+EGQBqfaPyPajCXf4IJ6AJ7Pj4NuvpX
REw9raZJkPhvLhUML82UkcfC25dWrZXxbpgFMUx7aRZ7+gS3Q5BLFyAEI/2faB4RLoTKrIUAbSse
EakyfgGz4ZFc+PBtv7rZ+IOajWAuGKwVOgmoFwTStYhB8slPZQVgAcPwuK0kccYz+fglOfmisEko
E4MXv2M8ePnHcULDhgRv/JQc+6XHbyjUJSbGZmN9Yi0kCkaR+BPz5+Jp1dlPirlxx2y/PN7kVEDz
FR6wYo6ocPzq9y+p/mbIOYd4x693/FrDptL4sU5n4hCWeJk2OeRE5aawEzMYQ0EKUQcPfrxhQ2sQ
TstHTqV2dmcGClp1IvKFqxq+WyUPAwDDwQAlFvnHRWH4DMoDQ2hQDwJEhjUJpkPfmvag6LLK4ubo
hVIRgKPJLCwgQWgefuGgaFT5ofa9ckXt6pnBNsT7pB74i5sgZVCDBmr5B06EC4G1ahIQQ00QKGwS
QKkuVeC9mNHy8Qtr9G7jYfCSTQAwi582pISHNocEJKewSbA5rdRkAQlaa/oDEb3YbBnci9/MDaWd
BFvSKjVZQr38QwZsf5A6GocoIIDrKe0kVEq4re93m/+AXo3+q8J/lLAikWHf8oEwXnyOFecWC1Dp
sxj/PSsbbmqPNgMLJcppWITLCQea+AcmIGBueQ0MyEYC9lITBEo7CaB0W1hAwpE3/5TuBUjJOZv/
crtYjmHcpxA3DimxW/WH19bN8Wm5sfH//sTw902977F1jetr/f9taezz25MWm2/76po62cgCDKms
PpGLIqdcGVldrW2Rtbuzz0BTmvzpB8RiBUoub2UQDWWvxWI2EAl1Vrx7zOiS6q1vD+qHrZ0BGnRN
UBSIgAQbwNZ0xo/HDLALAbrN+HErsmgu1eaGm44QjI3ytqW5UsdfdrtsYVNzgvGrY/DilznlaaAk
VxC8/OOQLzkYvPFfbsTktJyp9l0yK6i9IecSMX6CVzVZX79EczJzSErOk8MpvI7i5b9c/svqvON3
EscvJK1c8YmzC/7BIBaZlRfZwuGP1kOjsHm7XGeAJbg0ClfvGBmBE3zQtxE6oeja1zrqVldpqbSI
SFxukPo10+P9G5v3d4QkyFYBwhgBfDTyR7iMFybBK1v8WtaAg01ccjCMry6oHd/Q+FiLpIP+cOTg
Nc0HO8LiiqJZfI9d0bAc1ifB8C8BOd23pjU+cp00CYUOXtPUdUli/0eaDHnh8e2VVRtF/GZ4ggBp
qsKvfKRRYD45LXtN/cPTZTaoFx2Fwwf/oPGVxdVdG1rgBs3bF4e3rGkavqJ6I/Zq2lcXilC3TLNs
QY85jIVfuZLIGyQ5XA6FP99/LK8f3tAs/F7X3HVp/FYIBv54/pEEXYjUyuAxfqwxfqyhl5okSCNX
FZmAoIoB0y6CF1d0rVr6FU35p7L14q+8GyB7UCrn0Ms/jKLf+/FvjZPZs6JrLXnx9Oj8kuu/vkrz
Tzy85yON2U/A3ZZp2Q2NrywQll9bVHfHDHG59darm99eEvGOX/NYw4MO88yPQa7H3so1t1XNge/D
49eRNPnEAyQI/mAPYK3pi2sDUbjA0J+8edyaBHEqHEsmfnoy8dTIFoE0tPqqr84NaGNjX309JZhx
OtCMRCRYF9Dn1vgloSQHPKRbWEHJv3AU1uy+S2bLY8gw1k6PwhWUA0eSA7ByEAB9dn0wEvS3ReiK
od4c1tuqIVpkAIyRyZtyNiccJ/z+uE+a+H31YV/rtOj8hH7oZPpUVp/dGn9kbZUYYUVrA+779K+v
XZLwp8ayB/pygXBw06qm7W3gEdf+glO484Nr/5K5sVYZGXiZkfBXV/mqcfRoGobaHgM4setaLNp/
tZNcZOBrS+tumBGKavkDJzMDeb11WtW/Xx6TtsX8i1DhH+ac1+BCbAXuL6umgGXI9vhxK4Sh5Ica
I7fiN8M2OVkMckeICgr0Yi1gGIDwIyPBGhrM1otfZkfmTe4mL//e+MEjV3n8iiNMG0/vHISvYeE/
gkfZ5JH7p3Pg61T+QB9c7JUHmq6r55/A/itrL0z4x4cze0/ltKB/yYL6V2b7YArH6yXZgpHzjl9l
/nFmE1kWx653/IoBJ+ZxUSY6/6NVaS3PrOY5TZ4tZIrbY364s5LL5uW5xJorhT92OtEC+y+JB7TC
D7ePPC2enJCBiU99a/fw114c+PLLcv1RDJc8651HxrvhJG0t3v9wTgS8/epIFm9JgkUalxHWlpIl
Ewobt/XtTMM1ltTGX/ZdfVyMDlkMLY//iVzhkW09c58faN7afyCrBeqrttRbEPGp378sAfd9Dv2m
P/p434Jn+zpeHINwVy+OrwX3civk9sBhjgeqYNMfPfWFvWl510YbsRyaoZZwayZ5J5D3L9jGyX1r
GsVW/vLJ3gXP99dv7T9S0AKxwEbhspj/klOUmB2sP4DhXpAhmhGKrZHuocbIsS5qZS8GDDUJUl1S
lfBYtCUIaJA9CGCANQnQlNFiTZGjAHgvfsqfPbFWwiGXtCOcGC//IjulCaKWEEqPXxNZOmxpFNvS
W8JjObFhzl7+haPCr34Lkxp8DYNLwhBNaD1cLh0c3zGKg0ZshXL+CfsBq40nE08OLH6u76qdsMbQ
ZraEvvHGwP88BiuVwv1PnJr7GpDT+AMBXGBNAjS94xcyBwmBPxTkJ08bKLApe4oVWZBQ7COJEwEO
mlCTAM33fv5pW5mAJ3fceNpas9988oChrQQL/HdX1sGVvb27+25OaovlyiCbL8gTiaalc39zHFfS
nBNzCqa6NpJ6cTCxqRbuoQw9MwKHk64Np24fMW5GX+JsJIsQLNlUAWGx4CWQthKMCUidGru+D20z
3/5N5nuLQu11Pg1u/5jFtzghkf7A/RcE4LDO5DXY3kg0eG3YeAaOR7MIjFh1DSav74MbnvpmTb/N
7LIFZlnAp2GR+4hcl+QhID+aNLQqfcNHmw/Cw7ZHU7dvPbFFfmNho01QWE1GK0R0Sq4tATNWzBtZ
QfxIhbbYpF4SJs2Dhli78cXxGJKMwYsfd8WE88Dz6eUfs2EdJSKlbnICMDKUwgSOoynNPwTi0555
J/n5JZHZsyJr38hoM6KzNW3vb1NHG+AqMxTYHPlfYwrZilnIsuTEDWgtGsv+QWhPV+rJd0b1/xzC
noh8ZD4c1jXxiB0YYlpQptpNrvj2kiFQSv0E8ga2vFjbMmEeHo8XP6WRcusmJwAmQylMYD+q8k8B
FAXzOoJUFM0Oj+Vh1EYDdP+CDPSvtUdrUpmfadHPtYqnKpKR6GMdWlWNeCxj5uzqx6rS39qXeobg
5jYgM41vLRwwNh/JbKoNXzIzoPVGZmvagcNwEAgSRUEG6CRBAHExVFw/CJ0AQPDV5mOmQvVWSp7M
zTO60AAMbefMTcxBhVn7E9YzWFJhuhtPgjHGTzkpbk4JgWhUIDf+712DS9bUzo/65kyLwd8Ny7RD
vx2c+xpcUkFftIEkOOhNhZthxDnd4FW+OI/YwHI4Nxhu5yYezukGz/m5zHlA78UPSXCTT543N3ie
cy5zHi//mBlbPqUS1gT5zEuDxobayB/6h7Xz4HJv/rHDuXALmkAawQoLmlst+Myn/8eryf+1JFYd
Diz5QBz+7ijkHnmh//oe5+rEG/+QL1v+HfkUqeXj1g1e2JQrnAf63w/5t6eBLzWKfXuGsnD1rboh
9t3w2OeLX/HF45lfXpKIaIXEHjxT68svgPdsmKWpKbq+yfcf+/C+iaUtfrL8+rUth5OnOsKz22Jb
6sXdk62H4UYC7MuSkqVdEvXDql5cEHRXYKtS43SAaW1BWh8U7fE5kUee692S0eFBCyixkC+qFXbQ
b2uKWLjvCY3yw0U+3c2gUqxInvnDp3oaQsHPzgyvaIMHSnxzPlBz/29ScHFogqV8PGqSieLVTFPT
M9F4JoqfmijVLBONZ6J4teep6ZloPBPFT02UapaJxjNRvNrz1PTY4pGkBQ1+6PrwkcyG2vCVi6q0
Jh3unnxF0+4pekQraJsCn3/2vDNy6TsjK5rDf9AWWdkSbgoHNq1IbNw6WLSeSskWPwWm8jFRvIpn
qvQTjWei+KmKU8Uz0Xgmilf5naS+/FJDS6f+82Thpmn+Wy5LPP9fw5tNct9jl8I6Q0udGr35t6nd
Q/DoqDGeh/VBYfqMxB1zQ4d+M/itY1kJ1teE9L5MYW+FqPJpuXiPbUjA7Ymxr8BVAxbL093ZL7T6
a6KwRBArBriUwjrtpMN2hbyq0RT7qjb+DdHl/9J8uMRhdA0XFx+gHYRLH2H9A1Xa5h5x3RFWUT1X
1DZpuW/9vPeZkusfopMXsYwIhq6NaVvE4sB/eUOZdYyafPB/bWic78t+6T/7bt6X0faN3H/ZtJua
cBBwJ57sZcDLwPs0A5uPJv9nR3jOXPELvb1H7N+wVPPP2umJp1fFUieHos+Pf/84fN8L9XyyvkkT
r+uQV3h9s+Hr2oS/z7xPd4G32VOeATiDw3nOfjkBlDe/NHTVtXWtidiPPhn5+1OZvoLe3hSGpx3g
3P/j15LwsOS/9MDlDrympK2NF+7QtKGxzPcHxekcXty55UOR0ZND1c/z48TmyMDFO+D3/xZvHxSX
XcPw2IemzVnQcLBmfCgYWtIkVxolKwABFlcrgpEt6+t/8fLgT6DNiy/4DxsaLvtNqq09fiEcasPJ
r8CjG8VbNIUv7R7bvapqyZKmt1tGXxjyfWRurEnTRrrloofzFGWMP//yYGHJNN9N6xrmHM20tsXm
RDF7Mh4BBoGTj70wpDPy3AcGjPkNwbs/Vr/2UCpUH70Svrho+Z6STUMSM7dWktFLMRprxwm/aowb
PG7XmfO48TVRjBu8F//kxsZU5W2qeNzs64li3ODPjfj9hpjjfJpYX6Txaxjs1txjh21Tg3L+eaYn
1a3FWqfV9Fwa/K9ThQtniQktN5bZDLe2kzCd+q68pOmVg0NL9xXnbfW84SYnbjDvnfyXPw968fMM
oDzR/W4ylPlGLnvglmG67bH+neJHVr7ZTZEl08Q6Y2R4/Fu/6rlZ/PqC/MHxoCdEEwpOeShr2Qxe
RTCbtl5obj6c7BZW2Z+/A14ED1xeyIrLJNozx0Z+2A33aPQ5rTFYZ3SfysBiJCe9pMWbwrQx8SBq
/skjGZCrq0IfmSXXIsKc3Bkpf3D9ouoLq3QI+0tPD+8R5uIpipxYxxh7jo98btcYvAIVfgp7w4JY
U1A7dXL0T1+CtREyCDCQQy2jAgG3Tv/8y4MHxg0tHFw9t2pOtLD3pLgoIo5liErUAsbIqyzyEUmu
Xf/SwKvDhUA0tGFRYn1rMFDIbX2x/yv8LpVgMn1JAcKAJsbDa1RCTWBhSWEzAfUEI6Gy3tx8Bw9a
Va7JBQhe/JXzzHMFSGyC4OUfUvG+GT95Q9x4Lhgjcr//H/E7FC3Vl/yKnNBSctJLFsShpJx/8pmv
yAmtCZ4AWxS/MOFLDY9/edsoDKRv/Fa8RyAAP3+9oOpG4D194WPSO34xXzwnoMEmCdAkAOLfz8cv
ZqBYizF0zRPdj5Y+V1nsR8nvv7EanmbQk+P5zfJVXRaAhiAoIMvYBNmN3uIQnypbuPDnvzWqJzP5
zeK6X1l+uIPh2xjQDqcLe4gyHB2+plY7NpDYmb6x1q9lCpvFQgDHAYGKhICBZzVOjue2pBHjKv61
1f7z/frJkdwWsTZSxKbpktw4OV7YIlJX5F8c860I6cm8sXnE9q2FR4gy5+e9buLkthzPeaYKwzm5
zPm5nsfDMW70nEdlO1EMx3OZ83O9mzi5LcdznqnCcE4uc36u5/FwjBs951HZThTD8Vzm/FzvJk5u
y/GcZ6ownJPLnJ/reTwc40avVZh/Nlb7p/lpzkGPwK+tjfn6YJ4Uaxd0x4OpIPPYOIzzcIwbPedR
2U4Uw/Fc5vxc7yZObsvxnGeqMJyTy5yf63k8HONGz3lUthPFmPhrqrWvzcrNaa2pqqry+80fWTz/
0su41ABnUHiIplnFD1WIKj0nO5sYXGqcHEyU3L7h3lFWxaDSc4bfJYb75bIqBpXeje3ZwHBOLqvi
VOnd2J4NDOfksipOld6N7dnAcE4uq+JqoDCVAAAgAElEQVRU6d3Yng0M5+SyKk6V3o3t2cBwTi6r
4lTp3dieDQzn5LIqTpXeje3ZwHBOLqviVOnd2J4NDOfksipOld6N7RRgVEsNvO8AiwwsJFiKSp8I
JhMSKtlYfW5sJ4vxi1eOBuRPyS13ZT/d8Jc1BKUb26nCnEkMZ2Lrxa/KHurd5EfF4MZ2qjBnEsOZ
2Hrxq7KHejf5UTG4sZ0qzJnEcCa2Xvyq7KHeTX5UDG5spwojYzD4rz5UUU1Y7ybECZNOwCCZ+vSv
euC+yQRMSqDvdvwlwUyi4cU/iaRNoYmX/ylM5iSovPxPImlTaOLlfwqTOQmqczT/5tOUk9igc9jE
2HL6ByDO4fC90LwMeBnwMuBlwMvA71EGVL9A+T3aRG9TvAx4GfAy4GXAy4CXgXcvA4qlBl2DIQFD
pCYJlfV8w8iEBN5bWSYTEiaHJ3MSkIeaJDj5qYsEJ0alIRMSVEjUE4yEyem5F6IigfdWlsmEhMnh
yZwE5KEmCU5+6iLBiVFpyIQEFRL1BCNhcnruhahI4L2VZTIhYXJ4MicBeahJgpOfukhwYlQaMiFB
hUQ9wUiYnJ57ISoSeG9lmUxImByezElAHmqS4OSnLhKcGJWGTEhQIVFPMBImp+deiIoE3ltZJhMS
JocncxKQh5okOPmpiwQnRqUhExJUSNQTjITJ6bkXoiKB91aWyYSEyvhyvewGCrDgs6uA4w+xYhON
Qe9skgZ7qSmgEyyqGFR+Ob3KFjC2wGxNAjj1nN+NrIrBix+zp8qDSu8m5xzj5R8yAAXyianA5GB6
UU+1U7DB0HZCtZd/L/98XE1o8ADYGz+/B+MHN8Gx6+VSo/LmcRs+FLieT21uMGBL8xrHcx43GDe2
PE6O53ru1w3GTWxuMNwXj4Hb8jg5nuu5rRsM5+d4zuMG48aWx8nxXM/9usG4ic0NhvviMXBbHifH
cz23dYPh/BzPedxg3NjyODme67lfNxg3sbnBcF88Bm7L4+R4rue2bjCcn+M5jxuMG1seJ8dzPffr
BuMmNjcY7ovHwG15nBzP9dzWDYbzczzncYNxY8vj5Hiu537dYNzE5gbDffEYuC2Pk+O5ntu6wXB+
juc8bjBlbYGkXAnMjfov9Ss6yxl4Oi8DXga8DHgZ8DLgZcDLgDMDc0OwABFv0LYVxbMaNpTX9DLg
ZcDLgJcBLwNeBrwMVM6A4sKFt9SonDav18uAlwEvA14GvAx4GXCXAbioUa54S41yWfF0Xga8DHgZ
8DLgZcDLwBRlwFtqTFEiPRovA14GvAx4GfAy4GWgXAYUSw28BgI1CeWMz10dhU3CuRtrucgobBLK
oc5dHYVNwrkba7nIKGwSyqHOXR2FTcK5G2u5yChsEsqhzl0dhU3CuRtrucgobBLKoc5dHYVNwrkb
a7nIKGwSyqHeWzrFUgOf7ICaBNws2nISnJtLXSQ4MWdbQ2GT4MV/tnPO+SntJHj55/k52zKlnQQv
/2c755yf0k6Cl3+en7MtU9pJ8PJ/tnN+On7FUoNWCULQ50X9HTH/vKBeXHnALoQurAl8OmfFfjIh
AfuoSYKmzYv5O8K+Nvkf39eE/R1RfxtEAgCGKTKreUQPjbzfYfxuY+M42jQSsNeLH/NAaSGhst5N
bt1gvPxXzjPtDhJ4VivbciSZk4C9Xv4r55DSRQLPamVbjiRzErDXy3/lHFK6SOBZrWzLkWROAva+
V/LPt8WS2dtCLZX4xE0KBO5cGF/THIxYXaOj6Qf3jvwoKROgaxsvqL2t2Z8qYD7g/233neoZ/uxv
MkUGorIYPvPB+ltb5KrB1BipTOF4f+qf30zuRk0g/IvLE4Gekav3pjR/8HuX1C4MiY7eY0OPBuI3
oW0hfdszwyYeQzXZrA/aJaiYEAbBkdC3PhC4Z3+yS9fmtiTu/2B415t9Xzph/W+xZfnDlokVRfHT
MDQdlkeYNylAU5ZPLaz/s1b/rr19X+qxyEFflr9IJyUVplS/YnrsE9HsHYezJdalGNNdCaK0oY6/
vK0bfhVGpecRucFwvBc/zwbKqhyq9JzBDYbjvfzzbJTNfyj08GU1LdCVHP/0S6Mw7ZhF12rqqn6+
JAYzdXEKmnD+9T+ZX9V3aOQhmAZwIrLmH+/4pTyXCCz/1p5gnxPOv3L+//3MP0sVioZmyKsaMBHA
HxSsTSH4wGV168U6wzjan9rVkxksaPF4+NaVdbeEJd7QFyUCkZCvNuLHv3hIrwvRLpIuiJYEvIxS
MAZTefgbzWmRkL+9pereyxNrACOt4aAKyNXIvJYorDNymey+3vSL/b5NYp1hHB1I73onZa4ziJYE
6ba4ORX0sMXQK2oMFS2x9t27omZlS6ARzWVUMYgcmwAhkyKJXjQBPKYBa8DjgQ01CejHMMJysScm
EihFfulAhGcJFt6EiS6JF7XswxphVAfCf/fBqg/V+h08lkmRRPqCgIF5IvELospxIkA6LIbhMn6A
leeXdCJ49G7F4MXvzDMm0Kkvps5KJmJ47eUfs0GHLQmoV+ZHNW6Z3pZ/ny+OnLHwppi1DyT/hhk4
SWhiCsIiaeTgdzX+P7O4/oYZkQZ4VePZix9DsgK04mTbCypMlxBkP9Tij6YyOfNA05t/MFEiM1YC
MaHUFF2UOiuZiOE1x4Mem0KQIMFAJFM6//MYLBlPcbBvMQ7rm7fm+/LSmnaflkuOf/Wl0R0QkID4
7vpQ/RUJ/6c/GLvv1XFN88+K6Voufduz1gUGJIXtgQFd3CrcLOwz6937+247YeprqsLf+XBiZiB8
+8Lwtv0ZLZu6+qm0wBlG57j4ov/mgYHbTumaL7RO01K9Izfslr0mk4wcT+zCI/lFAXsBagm2I430
DCIi142s8Gz0iso42D20uttaLoAGCnMr9hY0DU2aaMIEC88DJgS9W/3yU0+b1zKsgM28WU0TPNH4
rTwUDHhtWy7HrpcgYbn4S+KChrv4pZWkE5Fbfk3BCtvMl5XDYh4IYKXU5heb0kdJ5cVvpoMlwss/
5oSPW9CItDgKSxsdv3YQ51Efv9JK0p1h/gv0hkXf8ulB7aC8Ngzshn9NPb8MXHRoHlXW/FMhfjnJ
GPC9zlFYIs4wfmQCBzxv2HR4NSNHExfxmyeU4rxBjF78VirOrfxbUbFPudQwd7l8FMOQjVB4XS0I
hYdehXUGLR3yd+0ZXX5pteb3zYN1QNA/KwDn/sxuw2gL+kazhSGTV29tqPreomhP9/Atb2XMIxm6
kEdigj44J5nnv6Gx9A2vJZ9ZGmtsja3/TfpxX/j/XZkI9gz/XIv9casIr2NR06OpnB4KiFV/ffVj
q6t27hu4q1e7fVHimpaQuLlTKOw7NnpHZ3oIQg6EH1gZHz6RmdYabQloR48N3XAgvaIt/pXzo40B
sWmDg+P/vHtkm7if4LtzSd0KX2b7qP9jM0LgKZfJPXtg6K4e7a4P1S0Td23CP1zT8MIbA9/3Vd23
KLRzT/9dfboWDn57UfWihD8ivmEYg8PpH+wZ2ZLS7/pwvTQJocldvQW70z2j2zI46+m3zE9sag3H
fVoqmR0M0TzC8q9rbU3VP5gffPVEbvGMSC2s+XL5lw8N33HUvA9SE498a1F8IVCIsLNPHhj+ek/e
3KJArlsLLEz4c+lcr88vktZc89iHx2//9Ugnzpig0bS25jjwH+g3FokcFp56vf+uUdi0ONu0zA/2
DG1J61ow9MCKaq031RePLEuAR2NwNP3vrww/jhdjA4FvXZT4UI0fEjg6lHo17f9wwrh3x9CWnA4X
rO69KN4RFxsIQf5y39DdvbjTfbDv1jcG47BHCsaJ/vF/fn10h4xKVmyZBXsMZyLoKI7DIlRI/DTA
MSo9ty7BlORfgwNBjBe1X85TInvxy3FekluaQ0oyVbrv3t/5h6FrlZkt4baD2S5owt2Thug8OUnL
Thha+p3L6i71pW//9WinVK3/QM2fzwps2zPw9QFDi4a+tzg+Ly4ORpgx3jwyctvb2Y1zav+sRUwU
n13VcHXPCMyH0g755FiFPQUFBzzO/+K488a//P7jzT9ibEzo+C2OZDnIzEoMQasgAmqjpsoPp/Dc
YPI7KZlpcRjA6NO11PjVT566Wo7ytvognMYijdXPXNn848sbH72y6b55YTF3aEYsHKgN6B+AE6Ew
lFdmnLHi+EbfA+NvihW3vz0Ila85pDdF4Ou+YX4bl4L1zRyURjav37WiYROcIwv5w/2ZUZ9v4azE
jy+Sj5T49aaQv2OWWGdAqfZpK2bX3r0gBuuME4OZoymjtjb6d6tr10Ofrk+P+6G5YUYol8qdSBmB
UOCKxbWfCRpZEbYoOfk9IObT4z7/9DDchvA/sKp2Wa0/kMl1DmRHC3ptIvIXy+JtmmYzKeP0UulU
0zbOr79pBqwz4LZUJhcLYpzSGzo1M1YFTkOBy2ZFanO53b1ZuKW08oK6e8XDsboWjz2yIgHrjFQy
0zmcD4SC6xc33NsWMLcoEYZ1BhAGYENg+SGKSFpxWpeZr/L746HgMlyrabCWCTywqsbcNEip2LSw
2DQIx+erC/naW2PLEnrvcE50xSN3Lo3XCGb/vSvrVsI6AxIymI/XRC6DO26RQGvA0CLhX1xaA+sM
WE5BFwS54aLGbzXDeNM3LqwT+04rdPbCXTm9pTH2jQ9VifDwDwaMiNDMg338mBix+4T/CoWlU6Cw
WQFvIhx+IeE0/oW55RcDwHh47cWPSfbyD8MGR47L8QN5S6V3DYtjZ1PMHIebZoQ1LQ9HkEyqODRg
1orHfFFr/LclgpGAf1YUjqzAfStqFsIRN5rZ15+DGaNjTu2903xpOPylMUwCZa5r4M4SNdthImBr
3vbGP+5HSDgIeKRDtqz8F/Nnk1g6RQ82bZiSJjN4b+e/ZKuoIU/IYsNksYRpMR90pPD0jtM+TrAA
xKamXVgD6wJRRoczPQX/vFr/vFk1D2uD13dmDvaM/FPaPzSSFfsDdw/gSJBW8iCUknBaOJ40OhJa
BtjzMhhd39I5uG0o8eiFkd0H+m+D5zH94cfW1mi9Ix/fk65pjD8a1+HmzudeHJFL+8D3Lqtf2Bj/
ctX43Wm8DlnY+nLf3Ulfh+b788vhAkX+wZ393xkVMXxmYf2traFb5gUf78zjJYLD7wx+thMuV+p3
rmhcH/df2qx/7uWBxssal/nSf/TCSJdhzJ0uNx4u3kyPi5tKw6Nrf52UoQceWFffHtAbtcLXyeT5
4S499MBFltMRsTnSaVA4Pez7oxmwDsg/+GLfd4AjGH5wdc1Msd6TW23lX5LLKpW67YURcd1oWvXm
C6Mdc6rmdY/esCgOq6oTx4aul19QOtoS9y6IdFwQX9E1jIZH3xm8oTPXEdN2Z0KPrUloPSMf3wsT
jrXaQJD0BTn84osj4zG/kaj6P2LTxtb+ekweRYEH1ta1B/yNmtGVN+QoyT+yo/+eUQNifvjympaI
/zzgaa3qgIdpRpOf2yG+Y81rqYarWQCGbP7JwupaTTv89sBnD+XANeyyRy6KrZxX1XYqeQk8O6Jp
T+7o+3oKPoMPrqubGfaL62TQwkJ5cI4f6rIJ2KyAL3uso5WNyorC/FSMf3MAky23ImWFeAiDAtYV
8F78kGE4Sqz55/ct/+Z4KGzrSi9LRJa3wj0UmD9DVzT6tOGxXcnIPDicxFm/IG7U+rRxa/xkzKfy
DVhbiJU8fBvcCTOduCz648WRtsbA428MJiINf9aiP/hS34/M7x7WYOVjT6RXzkJWp/npjX84KjE5
eHhiXihXPIfe8WsOmjIf8iRSRi9U5hKYpxK0VopT6eyJpPHmweG74NK9rs9rin9vcbRlVtX6zszj
ucKWXjaoLROydTjUa8TzpDDQrbEuTabJXRzE/3gWfuAK63a486LrH22Blb6I74qZ0av9eiZvZHOG
FtLn1vm1ExpsUm44efcQUOV3B4NN0ll9beT2einJIzMeE+d7bD97GFY4Ykn0Qk9ufVyun3Qdl1Hw
WGgXgKz4u44Pf3oAFhbaiprg+fHAnJpQExzbBQ2eW4FimmhaV8CndBr2wSoh1Tv2nXF5fTKbfqA7
d+cM5V7Yd3gU1hlA3nVy7M0Loh2h4PKA1ihu7mT+3boQurtr9KX2yMpI4OKILhdPhafehk9jNyxl
5IWeAASJm2BtiAhXls4jY+IB22ReS458enDUsWkGbhpAUv1Jsc6Akssdy2hwRXZc11c3iY1+9jdj
uEroPDH28tzoSuHU/8G43Hm+wJ/MCkC8GbwVHQmtC4x0waWymL5+VeMF/elXTqTueransyDBzkPa
FrYjfhEPL27wlaYDzmXJZ8LpxtbyIz7d4L34ecZQVuXETT45mxu8yhfn4bJLTjTx6btOpHoXRGa2
ROAeitYUnqlp+7pS3TXySKbpkfOTbB5i0WdWB9/sSW8/Prb6SfO7RximTU0LwcEKc95Zih82E5ih
oMC3GmXsEgh14VaAIkNu4cXPs4GyKidu8snZ3OBVvjhPObn8Se5ksgDrjIg4R9mKvrEtkkhnt/bm
th0Z3nYExpY8/RhaZ8/o65noMvg5ScTQxLdVqTe/g8ghaGMqNgUSH64W51DV4URLF0iHvOMfSERv
SBRZQKKNSaXMB0HmNYTEwwqaf/0F1Rwarw3N0+Q9y0LuzSyGarwFZ1yxYIArhxpe8JAnWuxFa33T
3JprW4LkSGhNV4ZlYlRwellcnv3hQQ/rKNoLlzqVSw3j130mO7h5bbjQ0ajLJx/gzJ9/SyQK85/f
NZhf2aLL52IAmHtTPBQiw6ak8Y0vkZFB7CD1pgmDHCzmsJiRi+ursIAAf0fHrS6tgJGAd8xG+6zq
dtMMP3wQ/z37hhcvS8yL+Nobo/C3CS5+HBv67IEUhoz5N+N3O35wK8BFcXNK3PKGm8OJ45UybLXl
VyRADBtZUMCGi3iEmcXjxa/MtrOD5U0k+72ff9gImHHz4h7K+kR4vX9Ya4UVRv6prny4wbn5No2h
5VN37Q/944Io3HjtmAF/VX9WyG99beDuAZpDpIk3/s3M/d6NH3EUQDkn5x+46CbndJjpZIjWlDc0
moXVQrw2ektw7D48aUiEFozctqAa7rJrz/YOt1Z/rE772d7Rx83zGZIADgU7J5tPkYvVdbEPilVG
/jB4xYsDrFOKZhZltEa1/EntiXcG7zxWqPfhiNGmRbS3hyAUsQwICKUw6RyGDYlEUuN/tWssJR4L
1ccLxnS4pJHKdWKchUK/FXCV6RRg3B1uiOhb057Y1BLUCvldx5KvDuZ29hlfuKS+w7EeY06T0qlm
Oc3u9kdhDZdKQZzoQm8Mkz1ouGtwCM+7wPMxOFP4FolHMvNwCUeEEvI1anqXkMRGnS+eDzXkQg1O
/bBFqIcavUBN5MXNESirrGmvqbxpctlJbGhmhETs+swoBIku/B3iMREI2JC70dj6St+vsnpUwiNB
HSbOvQKZ+R87e+PBwIZp4WXTIvPivvYZiT95O/0dsUKFghFiTWGjHpsSNbGK83BL8EKcKowKz+ME
DDZJ8OLneVPl1st/6bApaPDU0qPHM7DUuHxOlVava8OphzTjM2YuIY32Yv2ETejfPjH66RMjC+rC
VzSHlzWGG0P+DR3xLdvMaxvWbMAZvPyX5l/kBjVY83HLc8Vz6EbmPBzPOVUYFZ7HCRhskoBNzsl9
cU43MufheM6pwph4Os9BG4ODWodfnG4VPxbw37g00VHU+++6GNYZcC197EdZ4+LpsYWNseta0Bm8
Zya6CM51hdxr8klSuNWYKDm98Zi0bF6cjfCvLR59sEO8V6K3e+zxknnftknYFEE+d0osf2oTgc5k
bsco/OWvWFj3FxfV/3EDbI4AyCKFdF7ct4wEm7MFgO0YhWuS8Tsvqr19rrx6YSIhEihYc0GDxxa4
fk6NWMfs29f3pc7kj3oyndHgHHF6h1MpZhlkaVJ0iuHlLKfhoWRerOEaqzaKxxWg+G6aba4QrMjB
I22CtkQ8FCabcZneXPa5rJ6E5PnCf9wmlhfiLx5dI+5W5Pabp2pkll3SVj5yAwAMEvVQE0x0sU0b
L900Cyg+AQl/xfLmACyc9MvPr2oTOr2tMbbKeiXAkLj9ps+G50VE2nM70oHbl9bfuTRxiT9437qm
Ry+vPT+Z+c7hkVt2nHqw3xkS2KKSwiaBwCRQFwnYhSRQQ4EurEmQipKKukjAbmqCAMxYk3enL9BA
QT2ZkGAzhCZ1kYAYJJFkXvwiA7b88EzyXIEemxVyy22JlgTs5ZzQBQVqEqSipKIuErCbmiBQSDwA
kKFgLYTdcA9F09pniSfD9h2HS6vIAF2CQSziA6Er4OKxMPGthN+niQJHX+LRtU2PXBjZ0Zv6+r6h
67YPAQnoYaEvpxjfzDCYIxURCoRVqIsE7KEmCOARa/RONSBBxoICdpEJCWRCAnWRgF2cE7qgQE2C
VJRU1EUCdlMTBGDGmrw7fYEGCurJhASbITSpiwTEIIkkK4YNGChYYxfV1EUCdlETBHJnCwOQoMGC
AgLIhASbITSpiwTEcE7oggI1CVJRUlEXCiV90BDnThalbIlK/87e4XVra1vi0XuvDB/tz/YX9Nn1
ITmqCz89IB6KfPBo+ooF4YULGu+rTh4oBK6aFYZVSOehkR0avF6z+v5FkdHeoatfx7MfhC44yVHH
osZfzIUTphYI+MQvHqFkUt/cB08T8oJWoMEtx6aoO7vGOi8Iz6uNP7Mq+GRXdvq0WEcCfjaZeeRE
XgsiDH3BQ6aZR3sKNzUH/mxtw8q3x4cioctbxHG3Fx430MwHMqzAShIUhOM3EPnBKt/jbw79f2ZQ
+iG4atLomzev7s5gMlMVuWqG2GT4pceqiLY7pXMTy2ljqdM0vHzjkZ44xPMXq+svPpKePq1qoaCA
gtuIMtRmMPHGxC+WBLcP65edFxHpPZzs1PI/ODi+clG0Y0HDAzVje3OBdbNEV2/3+DbNgJsRsmAS
YK0oWkDy8LLUfbtHHhe3ipDZAiBc09imjWeqwmzTjN14HaUYIeVN23FkZF97w8JEbPNlwc5RfWE9
DieY2oxvdSYvuyjWsaDxwYaxnSO+NbOj8CDIaM/YQ/ns7GFjXm3wby6tu+RoOlgTuRy+umn5vjzU
FJVNwCYCKH6Otzaj5BOtiIr3kVKFqeCLbN1gOH8FPI+NZG5LShQoBhWmgi+ydYPh/BXwtvB4kOSO
Y0jJ+Tmggi+ydYPh/BXw3DXJ3JaUKFAMKkwFX2RbivHr4uDxaeISYDa1azixHuY0LfdUt3nRWDoG
W+O1YaOj0XfDh+vbT2RbmqPtEYCJ0jWQPqFFWxoTP7souG0gv3B6DI64XDK7WzOmiyujvssvbrj3
yNBt4sXBFMPUxc+mdwV/6faW4HELbLUqNoB58UMSKuSzbH4q4G2Zx+aZ5L8Mobkits5A5qgV+zKf
vv75Abj1DmN0Zn24o1GsM0ZHU/+GP50Q5/vBf3s7ndL0eTOqNoh1hrH7UP8tR8TXXPSDvxSlpjk+
xAIDim6+YDSgpzL5zu6RW7YP7TAHkHzrlICZPOIJClmA2vrJa/aWFwf3JY1ALLz+/HhHwpdLZX74
68Ft0kTCKE3GfXv6HzwBR5d/2XnxK1rg/RmF3W/13yGu2Rji8oAoBBYN6S6/vVuse+Kx0Bp4nY4s
2UJh2+Gh7cPwm9jg+gtq4BV+ucHxXcNA4ZsnlmA5ZhK4b0+fw+mAdKpBPI+Ln6IFr5gDL8bQToyK
IKxtZPlHr5pRWx/dcF6kVjPggYZbjsCG6J0nhv/qN+Ojmt7eGt8wKxKHru6hm/aJVZ21RSACFdzX
yOyFZzl9ekttpN1Pm4mCcJAUywjRZJuWKN00sVqRKaXYuJf857b1bpe/ZYV1Ru9gZlCgxZWtod6R
L7+RhDfMzmyu2jQHXmqi9faO/T97IEj97t2Du0cL8KLZ9edXX9EcDBRyj78+8JD5xAzYoyMZP7TM
Jgi2+GkrVHoVjyC1igrDOQEDTffxuOEE/178kAQ3uXp/5D9fEAdwAR7EFjl5uEvMP6nB8YfEElxL
yyel8Gi9783BTrhyHAqunBVrjxT29cLRCQdyAWbsv39jDI64Rnj+6Xzx0p3U6PjfvgJfC/XHjyXh
wAzAz1/bqzoAXSxe/uEwpIMd8+ImJ4D0jl9IgipXxRFGkv7F7Sd2sXe6UEdR8Ps6oj5Ya4+n87uL
5wPq93XERe/R8VyXtSagvrMttEX8MwP6eK6w23oOVOnR71sBPz0vGPuTeetVY0qs2QFvKvNpJ4uv
JjPV6LQ/ne90ZsNmonZaE/QtCPvG07ndsHgoV+a11Ny3KLJrz6kv9WkrovrR8bwjvTq8tQLu3Rwd
zXeVYyAdvGANNhx+s0oalVBp08rZtNVV/cuC0NN7BsQPiUWBX/82tBdSt20bEj9sEcUMUqYLNWZd
E/EvgH1XKOxm66MShNfwMuBlQJGBtph/pk/vH891OmbdebEAPMHWny6UTlB6W0QXL1p04BUePLWX
gclkYFlY+2xTZk5rTVUVvLzJfFDguRd+DRft4AyEaxPOi0p5csoX4HZ7OQziode8OMDtJyIzXyKS
svFwviK+KwVn2bL4IkZGDhdp4FmNCcaZLzgPY4hDOi0fD3jpFGd0K5/lnQrAUDa/Q7xgS7W9gBEl
BpdUBAnjxA5RG7vLvWq42G9JXfjKdKvp+ERy4VGdT25UxGvhQEssdMOy+viB0b0530fnJuDuMnzD
etvcKYCEIEVdzInFNJTK77DkM/tk8SjzyT24wbvBcM4zkSfqyw3eDeZMYua2E/XlBu8Gw2M4E3mi
vtzg3WDOJGatK0lfMOy+4Am2ctSG+JG5KHa889h0hynnZDI6N/FwXjd4NxjOeSbyRH25wbvBnEnM
3HaiviaKN33BUsM6L3LvppK6SHDjxg2GO0NyckGCikeFPxNObqvyyzFcVsWj4lHhSznxbSL2HaHi
5LZuMByvikfFU8R3nRjZ2hLc0K9eIHcAACAASURBVBjcsKhuA1Km0l9/eXTIHjaaAELFyeNxg+H4
YjxSe1pfKvyZcHJbL37MhioPXv4hM1AgD5giTBfVqrwRwCao8qniUeE5rQqj4uS2bjAcP1FfKvyZ
cHJbL37MhioPbvLP82nK/KoGp+ZQoMYuUHI3HM8x3JbLHM/13JZjuJ5cg6DCcL2K/z0Tf+eJoduG
9F7zehJuGiUBt4Jvry1XfPNJ5nhSIifxc4yNE50CnmMKd79+6sFYaF2dHx4F7R3NbZG/POHspVMq
kmDNeWy+SgnMFsdzALflGK4HPDoFQYXhehU/kmDN8TZf3JxkjiclCNyWY7geYWilwnC9ih8jx5rj
bb64OckcT0oQuC3HcD3C0EqF4XoVP0aONcfbfHFzkjmelCBwW47heoShlQrD9Sp+jBxrjrf54uYk
czwpQeC2HMP1CEMrFYbrVfwYOdYcb/PFzUnmeFKCwG05husRhlYqDNer+DFyrDne5oubk8zxpASB
23IM1yMMrVQYrlfxY+RYc7zNFzcnmeNJCQK35RiuRxhaqTBcz/lNWTz1XK5wNyoKFUalBz9AhYVj
QAPNysUWA/GorDi/zZZMVBiVHgzJL8eAHpqViy0G4lFZwW9n4M4U0JIjpwl1AQnnV+kRhh45BjTQ
rFw4PyBLgulKZn+UxMfaiYfz22zJkQqj0nO/HAN6aFYuthhK4i9nyflttgRXYVR6MCS/HAN6aFYu
thiIR2XF+W22ZKLCqPRgSH45BvTQrFxsMRCPyorz22zJRIVR6cGQ/HIM6KFZudhiIB6VFee32ZKJ
CqPSgyH55RjQQ7NyscVAPCorzm+zJRMVRqUHQ/LLMaCHZuVii4F4VFac32ZLJiqMSg+G5JdjQA/N
ysUWA/GorDi/zZZMVBiVHgzJL8eAHpqViy0G4qlsVdKLN1DQkrmHN8rh+0cBrHoRqS7fSga1WUiw
FPAJOmQFmdFb2yxN7BhwjQxIiDVyoZ4T2Y3NrHnxUwq9/GMqyh9m3vhxHl9mvsSHIj3e8WvOM6oE
efMPDiJv/BSnHTrQ3gfnLzaFkIg3UGhcgCAzIk72dMq3DivQCb1VQ0OsM1DFxpQ4zMDayiwJ0tSq
BMK0RRJasiAf4BhlyXKnpANxyIoeZS1IvPhlWrz8Qxr4ctkbP+Yh5h2/MhHe/IPTpzguoHjzp3f+
sgYCHB84KCY6f0oCWxUwuWxq3rQtHcgADlGIA5cIKJhhWasEToKyOccBgO1OsT3WskDw0OYxHo4X
VOjJAhOt06PAMl8ltl78Mo1e/r3xI447/K8TKh5TlCh+THnjh9LizT+QATEeZO3MBiXKGz+YnAq5
ouzxXAklnfveI+cva0PYsxo4PqwNsQDuhg6OIRpJJHBON2lV8XA95yxGaY1vL37IiZd/HBiUB2/8
UCr4IUNKnh9v/NjSQglBvTf/0BCyJcrWBBjPFfRik8ydAjI4ebiec3IGlb6CX5sjW9OL35YQbKry
THoQyhW51MA+IEK0LcXcjOi4soJcgZMCQgHrCnjuZdK2YIguOFsFuUI8k44B3E3a1ovfljpKJuor
7C++l20k7m0B6Y0fzOSkc0i7jAQv/3xwcrnCePby740fPlTKyu/K+AGn5UrgYDL/vHi7trXOoBFc
Dl1ycQyQNO2qNkml5+QTxXBbLvN4uJ7LKl8T1bvhVGG4nste/LAXoPA8qPYLz9tEMdyWy9wv13NZ
5WuiejecKgzXc9mLH/YCFJ4H1X7heZsohttymfvlei6rfE1U74ZTheF6Lnvxw16AwvOg2i88bxPF
cFsuc79cz2WVr4nq3XCqMFzPZSv+WvgfyJt4hynLZzUAhIUEHrrVKT4tOlNHeBRsTcRTzTk5j8rW
9CE/bBjexWUKgPuyAbALlYS38ZfVc04AEI/K1uYXmkTLu7hMAO7LBiC/nFAVA9dzTtATD8dwTptf
VZcTBhruywYgv5xQFQPXc04vfp5VkjFd0OS5ol4QeN6wib08zyo95+Q8KltkLsvPu7iMVKDhvmwA
7EIl4VUxcD3nBD3xcAzQYpM7JWXZLo4kAPdlA5BfoiWBzG0CNjknaIgHe20m3KmT39ZLTSLhvqgX
ecgvNrFXFQPXc07QEw/HcE5kLsvPu7iMVKDhvmwA8gt6wqti4HrOCXri4RjOafOr6nLCQMN92QDk
lxOqYuB6znm24+cxSxkcsmc1eDcPketBxi6bUrUZHGbjnDQP51TJNl8cNmm/Ns5J8/BgVLLNF4dN
2q+Nc9I8PBiVbPPFYZP2a+OcNA8PRiXbfHHYpP3aOCfNw4NRyTZfHDZpvzbOSfPwYFSyzReHTdqv
jXPSPDwYlWzzxWGT9mvjnDQPD0Yl23xx2KT92jgnzcODUck2Xxw2ab82zknz8GBUss0Xh03ar41z
0jw8mInIiqXGRCgE1s1muOGcKh43vjhmqvxOFQ+PzY08VX6nisdNzBwzVX6niofH5kaeKr9TxeMm
Zo6ZKr9TxcNjcyNPld+p4nETM8dMld+p4uGxuZGnyu9U8biJmWOmyu9U8fDY3MhT5XeqeMrFLP8T
eXBg81EO+rvWUUgkOCOgLhKcmHdLQyGR4IyEukhwYt4tDYVEgjMS6iLBiXm3NBQSCc5IqIsEJ+bd
0lBIJDgjoS4SnJh3S0MhkeCMhLpIcGLeLQ2FRIIzEuoiwYl5tzQUEgnOSKiLBCfm3dJQSCQ4I6Eu
EpyYd0tDIZHgjIS6SHBi3i0NhUSCMxLqIsGJMTWGXGrA7Q9xB8R6/wQIULBWWpZ2kAkJpf2iRV0k
VMZQSCBAwdpmQl0EBvIK/DZzapIJCdRFAnWRQF0kUBcIFBIFSTASqIvAYEgkBDutQCYkOE2oi4TK
GAqJgnTiqYvAQF6B38mAGjIhwYmkLhIqYygkCtKJpy4CA3kFficDasiEBCeSukiojKGQKEgnnroI
DOQV+J0MqCETEpxI6iKhMoZCoiCdeOoiMJBX4HcyoIZMSHAiqYuEyhgKiYJ04qmLwEBegd/JgBoy
IcGJpC4SKmMoJArSiacuAgN5BX4nA2rIhAQnkrpIqIyhkChIJ566CAzkFfidDKghExKcSOoioTKG
QqIgnXjqIjCQV+B3MqCGTEhwIqmLhMoYComCdOKpi8BAjvwOsFxqoBbeCAYFano1GJkpjItsbmw5
Bh0V7S1JhcEAKsfDbQEJzcp4y6f4dGPLMWTCSUgJSAIjwIvflihbk9IFgmrfcQylugIPx3j5tyXK
1uS59fIP2aCEYKK88WMbMLYmpQsEb/x448c2PGQTfoFiLUNolNhx+saEv1rXR9L5LWm8UCIRNKSg
pbRlXCo81zN4CSfwoxeo3eA5j0rmPL+b+IP+G2O+kWx+y7h1jYfH5iYGjmfxb6wJVmcLXdnCMzmO
KJUZviS3XM8teDzvkfyvTQQSNErf7fjXxgJthfzmlJVTnmceG9dbWPHJMe+R/PPwvfhLsuFs8P3O
97UTiRoVnuu5Lef0xg/PTOV8OpGV8V7+MT98vJXLoXwsFAcidNuEYGjLivqr2kIRy3JkKHn/C323
D8sFh6D2b1nTtKElKPoL+Vc7B5buhrMoK7AboGAtQ7ln1fQvzJJ4E2Wk0vmuk6N3vTS8WWjEhRhZ
ly4ppG0xPNO2dDoW1nJFQgI2+VAIx/qvawx29VU/N1YyFZIJMaPgiN90wTlFyPJ2iTBRxr+2tfaX
q6tlJo2HXxu//uLYjh1dK48UzJUTujtt/AgjMPgNRvZc03xhWKhOHTrVvIvObBI0dfHzOL/54ZY7
2oNTE79tkzXt1vaaG+Ppy/bChvi3f7xttT957c96t8DWABLTDjIKuHVW/he31j29urq78+SW1zKa
5rt/ZdONs0JifIuR2b/09fHi8JC5ERXnxKbQ+p66pm1deOzan/YLv9LXxtb4Py+tmROTVwGzuZ37
+1bsz2DX4rqqn6yqnR8XXbl09ue/7rm+W7yo5o51revjmXmPnPjrHB0v8mKbxSnMoVjxC1k9fsxN
lqBiVT5+uV2CDKhLc1W0lL2YRlQimAPQlmruCw29+HlOIFGUQxSw5rni6bXbBnZ8vHV5zHj6ua4r
uuXAkJnf2N7w8+VVr+7qWnqosGF2w5YVsR07u1cezplDVzh1Nf9444fnXsj2/MuDxQbCEW6O89PM
P9JU7Ay5S0qPO5sv8mLTQxMLCli7HT+WLZGD8G7Fz2OwZDl1QkBl/kIHr2vZINYZhSM9yZ1dqYGC
Vl0T+8LHpn+3Cm+y+HZsaBXrjHTm1RPpnM+/ZH7j/nl+yWwdKrj5UMOfSBmcPqSqUBhI5uBvJKtF
woE5s2p/9ImmL0K3SI2shWBlSkoWLTJb/AQDQfVHuxME3QfLnADEQEq0gvEhqPBPOJbuzDEjwqb4
TTyPTW4RggRJ2fi1Oy4W64yBgdTe42NH5BiqglQJvKyRtmxNoYr42R+AdX3j7GpYZ+TSmb3Hx589
mrYin/L4kRBqIYRDYpOrII1nHL+51yj/4dg9y2tWNpk/jBIpghHqKv/B+1dUa4XU38I6wzDuWTnt
JlhnFLJ7u9IpMTKb9l8Ae96M38oSfMrtKkm7vmVty7o4LFD0atTr+uKG6kdW18E6Y2Bg/NWerBYM
LF88bf+CgNgdochjV9XDOmNkKPVqXzYQDm5aPf3hOkF79QuDOS30xZVV7uKXGyniKTt+ZJyu4ncc
CBXHjz3/cv8W88OGtkBCE3OCgxZqURjIix/zw2vX+Q+KuVNfd0njF829gKkV6Q3iqAgIucpnDVpo
iOLl3zHmJ5V/OezpQLOn1hv/ZfIjjndrTuA5l8mzVXKpgScw6AHBLPrDVzbN8Wm50dHP/fjYeU/3
rniup/6hrsdhuaEF/tvyOOR9Y3vd8pimjY6s+/mJpdtOXvXiKJjOPz++GDggAKhJgGbpHnz15eP1
W7vrf3E88dNjHU/0wXd7LRj9yw/jd36EWsFgbIIQpmA7jxlwmfit7YBPno7UaPWP34luGy2OG2ec
FDYJlf0Cv4gNFyuWO/ALSqwxcvFFN3P3Ez2Ln+3/8oFT+o/fWXwoX4IhE2HGCo8fvWAtwjO2jIpb
JnteObF4+6nrT8A1Epb2qY0ftwL4eeHbCHpscgDIFeO3j5OckdW08WwB9SBDERfR0C95536BH5Zc
c2qXBLUDbwx8H5qxqs/MCmiFzN/99Pji53uWPzUEV0jmL6q5sTKPpm1sqX77uhkbmnG5rI1I7xD/
LQuqYe1z4I0T9U+cWvr08Y5nhiHp8xfUbISjYGa8VdNSPQOJx3uW/tfxv+wUF1SumB8T8Q8OP9Rb
qG6r/W709PGffvzw/JfNA0R75vkHZho2JFTOm8y/F78YLGeWfxztmi/ytUtpeYpD0Ky3Hiw3b3j5
h7Rj5s8s/+b5hYY9Cd74F9PCZM+/1hCGb2bWyQAFqKGEoh9thFVIfvPTfd8vzj35q58bHN5QrwX9
GzXtU3NgZWA8sn3gGYhD0555Z+Dvopnm0fQeTVvTWvvTlfGTh3sXvAr3U3CPAYQEIJBu4CCB0+TA
6HnPBrNrE03tia++Mv4NcbU5+PDqxmvwxk0hf+Dw4B++PLbHMNbOqtuyNPzCwfTSedVN8B21kHv6
5VM/8Vf/07J4NVy7zmZ/uaNnY3deRBMN77ikvqMuGBFLKWNgIHnvc31/nYTv45G3PtYYOtY3++Xx
tTMF2xP7xld11LQCrFA4dGTgEzvHIH5WDC0cO3h1fbQ/NRyLzK+Bk1DhSNfw7c8Ni0vrocjBj9UN
HUm2tCdag9qRQyfPezl969yav+9INAXFBg70jn7tuf5/yUf2f6wRzj6wSvvydW23HOv/oxORX6yM
Pv/Cyf65zZ+o9731Vu/iN9KQnlvn1f/jwmhuaPjKp4f2iF0rMyvztrguvnlF7YUiAHEN45ev9G58
J/fND037QnsINEtWzOhfMHbzEwMiqmLx3b+8YeOMSJ0MJpXObHu992q49Kr54Iv7al/qqaHAtXMi
cBIFwidfOXX1O8ZTH21ZFc796xM9XxHXR8C7/6mrpq0KZm5/tFecwrHIXSdEsT/hNO/7j5VNn5gV
FuvEQn7vwYEbX0vCztIiIm9a92hvbXx5HYRtDAwl73667xvADCUc3r66fmVjELyP9I69nA6uqivc
/dTIDVc1wK7U2hqHrxr5zK+GJdR/x4cafzknBvwyzt6r38mZmTFDgkWe/6sXwvk883AnTNfGxtZY
HST/+PBfi2WYsefU8LahxPqa8KUxbTOMARG2rEWn9U0dZD3wj2vqZoNhz/h4Y1QMCXOB458n7k9l
n30LlhGi7DmZ6tESsMKAUEckZmQELqWIrn0p8RGQCQfhm/tHb1id+NRF0c+/WOoYIy/GD1hpz4Mr
wchQAQVFGb+1OYAR21UyfqwNlgxYoUOshQnrKoqgRX+gYo5LYoP8k70K48UPmSktmHBKOwkwrtoa
nmodv0LchiOtENbMrBPzxvMnrhZdgS2XNl41PSSmOHHc9d/4anKP2Ef6f6xqLjkehd7L/wTyz/YT
pB2HNOhQkDze+Md0innGGlooQI1dLIko+koHsxzbhra4NgQzd6535OYkLBhllpEiOZr4yTuJJwa3
aIH5NT4tm8lMr+26bkb2UzPHr5u2YHT8811ZmOYS0VBd0De3Fs4jON+R/7JR6NrJ0T1iSR+YJ86b
wR3XtW6CdUYhd6AnPeLzz5/TsPMjicWalvD7q8Oh9R+sbtJy3aN5zRdYt3z692Cdkc52JwuBYHDD
6qavwtgwQgevmba8IRhIZQRDQa+rq/qrK+vWgnO/vyXsa5Z33JFt08U1rVruyFBO8/nmtDf8BC6z
0zASgq759Pqwv3V61fwa/dDx8VNZ3+y22keuTIj0+X3N4cCSeWKdASXh8926sPl7y2pgndHdmzqS
NOoa49/eOO2rmpEtiJlClLyRzRuJgD/uC7RF9B8cTEXC/gsXNd4PC5FQ1T9eXFUX9u39zaiYMoSF
zBtUdTU7P9oA64zUaPrAQC4QDm1Y1frK3EBasJm0ubzlwor/u5dOv6k9WucvQNhHkoUIpG75NOFI
02fUBCC2TXMiuWSmO2kA4fpV0+4JF95K6ZFY5JNz5PYAsK7qsrpAJJ/bgftNhlM6YHyPrW+7AdYZ
hdwhubMunNf4/GVw+wHy5oO8zWmvWV7nOzWQEXuhpuof1tWKi15a4JWPTVsN64x05kBvtrqxah3s
7lhwJrg1t8LI5eVTLIANhtfPiWkizoKMs+mbMKxKiq41xpfCXaSBpFxb6MOS5PBxXNQA1OgcgjT5
F8LqGbzLvSpqTJiVNs3I7zg89siL3fVP9x41v2DKDdYLVz/Zpf/k+OdxpaFra2fFYJ2hwXO4mral
LwOXTJraG7ZfEPliW/U9F4gR/NY7KTGKDGNP1/gRyOKM6luFYyhYS7FYURcJxT5Toh4QlPFLrLld
peMH/IIhkTjoSxTW+JEHgrvjV9hXdECuQfDiL0l3aSM5+q9viMfd1l3S8EWcf8xhKjIIU5aYN6Kw
uIDHiVrl3W047jJwi/DCeU1bO2BF7Hvs6hn24/HyeHHXe/nHoVia9ZKWN/5L0iEbmDSo3Y4fJ4W4
E05zbbG7vTogvuzieawk9XibAEwKWZiOg+EbLk60hjX5yEVo0+q2He1AqG891ve17T1f3jHGwiyS
SwmdQo1C7tioENKaceMFdcvhkEmOfe6h7gVPn0j87BTcXok01H57GjCLkhsavfY/u9sePfZgjzjN
jvQOdPzseNvWrseHgME/L6atbU+IWz8Dg8GtJxY8fTLxUPchcYPG1wYbYp3JLL/iDtFnHuo+77Gu
z+yC753aeeIRV0qnTHBel6e2/CNPds199lTzf548kNUCjTVbGnVgE1+bNeh6R/9Z9xdeL9yxWHz3
/uETR9qePHne1qP/ejij+cK3LdYWP9q9E0582fFPbu0WV3pwozXjma6Bbx2GPPpvXNe05yP18F28
+1DPFV3iXkuxGPpjK2qBF7qij55Y8ASEKhK7ZEn9sVdPXvqyCPvVV7ubn4T1H/DCn4w/EP1EG1xL
yP7dT0XY52099r3j4nS7tFVsDZ5JD3WejG6F1B3bKlIXWDsz8Pk3R2CL5nygaq0M8ZvzqgC9963R
PRgw0lvRg6/FbTXra3TI4bUPdc+FVP/4xN60Vj299mHYkjy+9D734BNHm584kdjS0w2OY4HFhnHj
3NolsDIYGrn2Z8cXPHn82p3yJhDs/Uxy7i/74LbFSFdv/ZNDW8SGiHKksye69QTE+WCv2JFXzhTX
SGSPGdBGOVwPvi1+2AP6FeIiihYTV84QBtst4LUhXFjTt3AiEb0Avnln3/VwyUQcFKzYxn9tfMsq
WEtpr+4degb4B4a/3wMWgdUXN397dd3ssK4VRpeKS0fgHf7SL0PMvuBKscLjhVyTgL3UJEHqqSUE
Vfycn8m2+EUT/ySVCeQOMG8YP3SD4CwcD73YJMHBXwL34nfkhxIY1H/+Ru9zcEz7ol9bLYZZ2fzD
9V3xOFE6+bmHuuY+fSL6xAAMuNkXJG5og6t3eDyCHo7H4+bxWCuZTLde/lX5R703/h35AQUUUz3B
8SNNoeKzKucTMlygkPQ89TgBidlnTJ4QR3qHrv3xsfqfHf3L/eJL5PKLatfCRzr/N92pf0maoVGM
bEoCEC96HczRslzaIr4X7ny9//vYTo//wz7B3FRthrrnAJxTZZGPUb11CG954DdXsVh55nDvuq3H
bn5u9NbG0D1z448tr2sWpvqIOfsLmQ7g/QeGNgsyffPR5IAURFWcXjEncDN+6P9n703g4yiu/PHu
uQ/NjEbS6LQsybLlA9vCB9gGbHxw2Btis8SQhECWfMgP2PwgwP428CcsbJZswibZXWA3F+yyyYKT
zYKTIEJih4BtzGEbsI0N2I58W5ZknaMZaUYzmqP/79XrrqmZUUsjbMhBF6LmVdU7vvXqdVV1dc/4
2l7qTvwR7KncUIrLF6zEyeAgNsWTGyRLORMuKS/6ySzPT2YVlbHDDA8+6MfXUUGqhjGI2b27undF
JUuRc06RDKvvDW/Rekm2KDeV48OJ+HfegvtnRL7hSJBNRrCAyQ3sUZTVzNbSTL9keNhw2S9P3/ib
7laX7aHJzmebS1aXiGMNClMvvQ8KISlb8X1SlnqHdgNZ5P48ntpY19YB6pH/OQLz2Ojpc3Vw+IWB
cvV07O+PptsSCcBsmo6vOwABfgt/Dt0K/kmQERiFS2rwgcRLe2AccdBbjg/swP0SJHjLEkFaTSLU
1Ob31T3EK2cQp/r0DfnVVIH3eVIUDkJYqmSPzfLZVG7dDwTMYIsE0ACScnluma//yhJ4btJzqm/B
cdi6ybfMLv8yjnpqz8H+x/cP9gAEU1H3RW6mCrXBYQx8QFiyGsq1xnP8yU0AIf5l8LO+YAixPzAP
BCUi8utFncBJRU3oHH+Ktj6e+MGhsldSlm0LwoYbH6NUKBhlmLI8P4193enQgaA6SQbD//fV7rs3
B5vr2JZWvR49wvUIU9C4yfC/Ef/jBskYDGL8jMJGIUhM4GggcNI5PpiE5cUJazlVqNUo/9DUIt9w
7Mn2dDEunsrW3WzhV6SH9/V+dmrNHLt1sUXZCnfNqAZSRieex9KrJdSCRZWC6Rm/awBP8CU5jGtV
clcX5KrtwxHAAosTbKaghq00TLY3mpT8FraiYL363RZUavri+YHrJtuzLi91GWKcqJn+UI5pxg/G
z+ohE/CDeY8dbojV59+HwS7goW8wwjuMWIQErwg48D0DybJ2Xil+aslT5linDLODBGUw02tqBkvJ
+96NbFmEi9ORwwNbybBmC5kISTSxDwuELLWjN7l0sswWMKiBashps8ldriyu9f/TfK9fXLWJE5nh
WGpkj7rBUPZFaD6D+vTPjsUXzbRfAa+AtLtnmKTBzvDDpBlgMDnNM6hDYqdEFn/RTXCMISQrciLu
xAjzOxRVf2JDHOtSJwfVIQGauoMGVK8CG/0RTiasKF0RFKcwYMOBJSjPD+D21IUhhCi3dCbgC9Wh
YdwKMD1q1hNNqVKZUWAKMx2DIogwc5BTI+mAN2mml35vHh7z9JzqLX+DTuxMn66HbaCyeWv7GohY
RbrtSKz7mkBgkvsWKcKWAdmLsOSL4Bnb4UTm/QnUKcY/9gL+1wATAALD6gWS9Wk8WVROzz6yVaIV
6g+zxjOxWusvaxQKuTrHwyDaytU/nmyuLYYaAYmKOPrsagGy1lmoIoeLPhkPg2hLNIv6x5P9IPjB
BqLEv1D44YOub860r7wk8Lk9dJloyBnPefhsWoJHsVhCEemJdnzs8i3d65GpJfYPCz8ByXJ5ViHX
J+P58KP2v4EfIki8eCBcqMg8o5EFzD+cFRRmEoQsNLBE1w/k8OLbwAhErqfM80NH+Db42S5kYXFq
L/rKwhIHHI7/8gytnUO0XMG8Jil4/5aWhmHlZUVSKuSaElYlZLJU4ZmLN7qp1ohSh6/UmWfDiV8X
qETTNeyrlciPavFDI1gpg5+Kyl2zy+BpJTzh2XVkcFfvyJaO9IOfrJ6P3xAj3zENXErVQZqpKRc/
+Cim7SeAo4bdeZMc5FaTioo9tnc7okN3vxSKAmZZAqFar1mKJlpk+T4UGBW5/fvz1ZvgGfMDdx3u
epQx5k5nDlNN5toz0QuqsDNDrZDIM6p/wGmyZHf+00IvbADgJdatnfF9HbEZ86tvncQ2dCSSSoOD
WYIbKZUAo48eGnpwpr261vusF4fk9UPswAE1M7Uqp8rvY+cHHa3dXzqSxAdcyCVPcsmtfeqbm+zg
SYgfxgHbNtgO1nnAQUDAoJgWloCP2c5A7YLWL2hHnCz20CYnsKAl+VBfQqoyw0aCOQ1eE0G2yjKr
dCxGHqpGnKnDA1oXMuqBk3UNBDLxT1YINjYAy12zA4/MxiMc+B7KzPdGNCkT23An9/dBCxuFkTg4
LOCywxOTJ1jvwrixknfDMsE3OQAAIABJREFUV2QxjY6f1TNMiEFbVBCXhiHH/+PgJ3SaLMOvmabO
krzQ9yz9DIMKVXMFQ68pUQvah6DTwA8egIQumaj/yZ1saGT54X09a+omLXW57llE9VmRE2O3BhRS
ZOy+qd7FtnSMHe/h9Xg4WQGXFI4wux57mYB6cTEJ0so41GElwB8cP4UN6DXiJy8Gsq6vP3v/Z8Wq
Gmgwy2NkQBMGpZYDER/+OT7at9y8svQG5GUXgGTetNwPN3HwNOHOWPJFfHfOdPn5LpSF/9mreVIq
eZwZWm4zzSG1PAd3A800JeCsW4v7FcWuE5f44LroOR58WJYOwY8RSNJFc9gBATKbb5+Op4K4hafL
ALQgAX+UBPysYkYpnre8+1bn4j1Dd54aafE4puGiKaNGUQMpUDUxJShOhKaTtQIgR4XnPhW/9e7z
YMlR2kP8ppwpAs2RBH490mWrGkk+MZB4IpiQaou/ubTiPniBQ7SbjfxHlwZmWOHwYOB5cLjJ8fAq
eoeLvceHzoI/BQ8dTK67p7KfdgUTxUVX+KA+sQ/u8qkXHLZGwIu90N9kb3/99uAXDkcfjZjOL2H7
DFQJ/0OinPuEEVAXG3oZvtJc5F5fY5HikZ/g8ZLGA73Ajqgmgdh0GneaJSXWllACu9yf/MSiigeW
Vd4Nb4So6rNtMdk93bhUX3a+bwUqlFZUe/FFUkyq8kSafWs3Y4e1kP+Bi/CrvYAm5Tg7lXHBJhWs
wReAO4dhIKrhZUwybnevYl+n6oZNs6LMtcgr0BPMliIvt8tqoKIs8wpJIR6gsLBicinbZ6Q2b2+b
Cd8VIj+ggjSzbL20VnsLxG7HrxqlR/bBqQcyyPX4DjKc1jDYqF/bbgr40RTpRAxsiSIMlFMr5wFt
wMO0Y4ZFVkJZDlmMH+DRFKEgsDENKKXJkhJShCxaPfJofwAYaAM/OkdzCnxyX50D/2vaUGdq2dZ+
nE8okefVgry5E64gaVYju2wQjOPuhf61c4va+PU4iPPPEwPJT1xY8cDSyrurcHevjvuHiJ+5RfQJ
qwCD+GfED113f/b+V6M09wOWeG0iwmhgMYFVyhde67vi2vJqX9HTn3H+Y3e8LyU3VDjZaXzqZ2/j
aw8P7h+4fWogMDnQbQ2/MmBeNRPPlo8eDLfI0tr6MvhVu6HOXs82+FHOjE5UzNL8RTX9c3Cphucf
HvpmYDzydzvxHvTRd4J3zaysK/OHr7T9ti0xe6oP5+545BF4aFnPhAEnJApfIsAEEezzENxSV5ln
nl/RYh0c8bqumorfk4Q3WFe5lA1sc49cJML4czNq4jqJMNm/+amKZQeGaxp9+NOcofC98Lof7mCE
lBz+RXvq1hrbPetrLj04GHQ7L5uMlt85AidEMntXgzETfkaum1J2UxWse/FHXw89mIi3f7aiurx0
d2Nsgfp6BLGm/2V/ZOli9/yF1UdKQ3sT1iub3KC353j4UVmCbx3nJgZ4/0CCnUsV718gvTFsumxa
MXyNAxJ73pRmYAQc2So2tA6vZw90Ok4ObshuwpIg13I0dGiBa0aZP/FJ+2+OxidN9s6HEEnHnj6W
hK+zMlGal1FM9YCiPHEwePss5xy/78VrHAdD8pxyfPwBCQXYqyeeqtL2y53ffXUg4zRs54aJ4EWp
ZSAek9z1oOcgu9OLRn4bLF3vd33vqsDlxxIXzfbB6U5Haz9+P8Xufu2aMk8icvVG/AXStQ1aoL4S
QfXguoxWCX/CC5P8D+fTVsi8oLmyfyHzr1m2RCM3/jb4L+9Hll7gXrSo5mB5aE/MsmZ6EdgKnsSh
waSYJhXJUiK+A3YeMmnjBjjBOAvPRDUEWLUl4heZBBqne+3uE6pJPMc0aRtHJ/YtR67QogBHBTCO
LUHgY4V/cPDhg254jKI5ljtc2XoqdGixe4a/OHyl9benkhfM8AUg6k6F//ZI8hPz2fV4lf03x+KT
arXrESZPcjIfN1IGlUAY/tdcjJ/kjXF8wv0oShZGC+H85xv/o7iC7XapnruYiNRwzfNdu3phejbX
lbvmV+E+YzAU+fZv2r8QYgEajy7f3HcyIQWqvOtnuv2ScvR479QD7NeamUJ8QxBU4dSmTWpAqIu9
ye+ywB/sM2Lx5KHj/fDj008gM3DG63/dcyiqePzu9XOLZ7hkMPrV3/Ru0C6JKBxvACfcfuNbHfAt
SBo6uJVUiUff690ShC9G2tfOL1s/1ZXojewKglXzTDhSVPAXopKwydGEUJua8Osk8NtRCBgS5IRc
bU/HzPbVzcXw8ibgufvFIH4pg92sqiKsj7dt7/jxKbjRtyya6V89GX6yIrVn35llp/EHqdTXIRhy
MphIWf/pAnx0smtXD66CcuxLu/ANgPkLSu+CD84pyy3He+/eOwT7u8aG4vVNbg9z9WU7+TdZ4I1I
3gsNf2zo0YOw2TDNaSq5tbm40TqyC76BCU9/4K1bOH+hUcjuYxQcCGpkqeVY+BDuA1MvHtLeBgEw
rIlQxZnPI2h0ZOYL3e8OpS1FrrXN/vl+czIae/x33ewZEPMnGILlAbsjax6A1S4xd2P7ll741q4d
9hk9vcP45mhiBF8Ojcbega/DmEzVZa4mMzvOQVn2RwCAEd7nQOTCGPVHD8DPzlYU3UU8inTt5s5X
gylAtX4u/mhKT2fwBnjfFfUo6AXsHSWk1K8iM5iqLahNaz/h5XCy30TBsAn4rBS3frvZAy9hKFLL
kd6v7ovAHnlGQ/H1M4vgGjl5vG/5LhgaBDk34IEfFhvsjmixzdyoIhfwU6QBAA0/6x1nFrrPQar4
hQ/exAlq1Pyfua1EAKyNckEHkgCGckI1OrZs/4/OY+BHR/L4L8j/2fMPPEZ5lX01LwH7VG2w2Pmu
et3hJNnsq7NDhA98GX67RRGux7na9fhiN258QRzynNhgANWMN3GCGoz4Ib+RAyHHPyP+xdBhdE7Y
5Ldf9etTL+CvDkACXnJnFgk3mjd4LS5FiUaTG/C8PJdnnddaYVIODyXxbVBMxAA5JB2dOiyi6Aqv
eZrZ1AUvOoj/xluOTlEg2xb8Y1fT7HJXNNkSYw9rIDhyZAVoWWqyCvDSgzt8TZl0qtv7RuwGeBtr
JLkBvlkzNn6z+Rb4vkwqvTOc2o+sOUnPsFAvkBjWdDMnyTf4rS4pfTiY2goqs3i0IpoSwFkst3hk
2IhsCLPbGmrJZhlFj8vdv7bMHwo1/2agQPwr3JZpNlMUnENvbmZh4/hV0Csqizdc4Hjx9a4v9DPY
kvXIddWNqciNG3vZIYqyAt7oTaW24iuigiKBFLtILHedX/nITPu7b53G32AFOUzKCq9tmllhIUQ1
lI+pCNVlmRX8n92QpcZ0Q4nZpUhdg4mWDGzph8trb60yPf9S27oetj8u0P8afg0HweZ5lmGBR6gX
yMLwC2rynTuKTwT+LFtCfZYeDj7bh1k8giKBNPAzn2qOBc9A0q4M+PcFp1nkrkiyhe64eD1ej3Ab
lt6gbvCZlJplOVfTC21CvUAa/h/D/+jRLF9pRWzQBgNpMekJCPUC+Sfn/6t8poemSI3VPrfbbVa/
Giltf32XjFuNMLvLyyxp4BehrwKZ1W1a/2jPK8rq1YvezqKzDGim4VPvsFcYwiye3CWNqdL0gRFI
heDM0ekoCv9lmdTZ64WfMx89/XHjp+6MjpxqBfxux6ZZ7mnV7kaXvGfX6QXwHATEIQkuzyrk+Cpj
S9ApkOT/FfVlWxa74bHCxt0DexLmdXNLFsHPweHOJog/a6irk9Dm52TAceKzlXXRwZUt/VsRbo4e
LQywQeiMri0BtEBOLH7w3/YL+INBeTMcA46RsgxkgGZhy1R/dPjRVeI1pdcFAz94IMdXgk8EMsuf
WeMr+FmvXs/94lytG9tG/DD3ifGs52e9esP/bFodd/65ymcedavB3tWAAcDElnYMXEjCdEyNqhmB
B6WomC2bVc+uQKZRC/Y8/VmXosaFEJhJFRtDlK8ny5aA7RziN8O/dcT+hTbdS1rzFmL+48PPHVgA
/hXlRaunsq/DhEJ/C/sMPgrUNSxDEgbsA/l/6/H+jXX29VX29Ysr1pPKaPSr8EwKNdO487iiIjEJ
dkVHq9Xxv9sbfXqe5/szBmcewpfm/uDx85OLy/xS6sdv8H3G2PhZH//E40cclj+4/yloVBhYMPxP
LhH88IGuX+bJnOtUmHuzdGqXoeF/tpqxAfg4+J8iLStnWw21hpzBXcKJLAGdgp6s4NaseQjUaPpp
LaQcq7V6valBFeRsOUROUQdvbjVJ5cvCSxaRz/w6Dj9KxgBTd0hYY/4jx6+6HT2rzba6+OHXz76a
itaZU98/HmMLP4nkyFLHte7zcdQdFzIn5ulrt7XD042ry612SekOxR/sYduaXFUgMoH42XCopzbu
LlZ/enQM2bPHL/aF6FF0vnW4r/f92J34D7lALyABz595/LBe8sDQG7tRfKX5h7zESplgoOLYuZ5O
PQyCoT+j6xd99Mc2f6phTw434p8HHr9McoicIg5pAemPMP5zUbMHKOq7Grlto5ShRzxaxKtYZC2E
R+T/KOlCsBXC81FiFm0Vgq0QHlHnR0kXgq0Qno8Ss2irEGyF8Ig6P0q6EGyF8HyUmEVbhWArhEfU
+VHShWArhOejxCzaKgRbITyizo+SLgRbITwfJWbRViHYCuERdZ5rWu8BivANFNEkwIUEOSeoFbYX
kCDn+4x8HuIcO+d3Epwgfm6OE/l6eBMnCucx8Kt+Zr4D5xv+pyjKCSEeWpwgBiN+jPjhIcGJnOCB
Im/ihBE/opf4tMMJauXu4oQodfY8xvWr+pD598Ob//NHDV5CGK2S7SSggQZGJERuPmxUmcOcUxQF
USFrppwXc3jEIjiF3tYhZioSAzck8lMlb+JEITwFyTImAz8Oh+hTjS7Ih4yZi+cQOUVNsfppxE8m
9nJcI3h1HB8KnEDmMOcUc4wY/jf8TxGSHyd69WIIGfHz5x0/4lhrtPgrcsJzPr7Z5AQJ8CIQ4h+0
UpOmV/0U+UUevmkFAvVQDvsJRkCeG6+sDMOTE6O6+vV2bUI92tX+RGxiF3T1MyaEbeDXxk70oa7f
DP9rkYPuMuJHiAcjflhoZGW61xHjMuJH1z8FxBXI8j8x9sQB0NVv+J88oONn0YcabZnqtlyS9Q9p
ai38E1Z38Dit8UTQAIj1OGviNgGFBJLrQCKLX2jR06lXLxrQsyWoz7J7NjoN/BQDhv+N+BevL71r
Sq/eiB8jfoz4watAf60U/SOuO2dzTYl6RP16OvXqx7t+pzphJ0C/1CWawQco7Cwhp9u0bWBHCWyf
AVzMNciWTfAi+Y6Uayy6y3wWBh2domvEbqOsZiALZ2a3o257DPxj+VAYAz6IRFA+lqzhfy1ouet4
TArhacQ/egAdIjwAZWXMIBnXrxE/EAbcCURQbsw/f7rrF7u4czKddzVoKdEWFHEWzZFXi3pThhg6
wMpDStRyNrKiHpE28KseYB/c7ZwQfWX4X/QG0Ub8GPFTyNyVHzlG/EDk0JQCrijEh8b8kx9Ff+rz
T16PoENsq0Edw8jIY4EKvVAQeSfqmo9S1sAvejuf/rDHzvB/vs/FGsP/fNrhhOgfI35Eb+TTRvzw
sOGE6CUjfkRv5NMfdvxoFnVONbRm/DwbKKKePxRt4P9DeZ7sGv43/H82HjDi52y8d/ayhv/P3odn
o+FP3f9a33V+V0NrNj4NDxgeMDxgeMDwgOEBwwMf3APwz3V/cGFD0vCA4QHDA4YHDA8YHjA8MJ4H
jK3GeB4y2g0PGB4wPGB4wPCA4YGz8EAB72pIcpPb7JSk4USqdYQeHJ2FQUG0xmEuM8tSKr0vxv4V
e6HJIA0PGB4wPGB4wPCA4YE/Dw+MudUwW++fW7y8wubQ+jo0NPzTvcGnI7DhMN2/qHy5W8rZJDhM
yf94rfcZ9o94a0KjfK5rLL6pwVVmgZeDWUomtx/qv/90YhTWP2yV1fWrVX5LV/+avcMTAGJz/Wql
X+rq/+SEpCZgoEBW87eXVy4xDd+8pf/82eV3TLK+vf/M3R1ZP67SVF3y5Fxnfn2BBv742RZXe65x
xu85Ol5ETqwnpm8sq1pmi978UrCVCzoc311Y3FxkhopYLP7CO/2PDagb6KZA0d+d52lwsBPEZOrt
o/13H8/Fs7ih9DvTHfveO3P76awB4uoN4s/cAzbHsytLK6GT0chntg+0C731lXifu9ADM/VZXKem
v57l6TsSGndmFswapOGBc+mBMR6g2J5aVb4a9xnptr7ht7tiMHMWFTlvWVpxM249ZJ/T7LCZix30
ZyLCYbPYx4N387zKv53mhn3GwFDs7c7o8WhasliWzS5/qsE6nugfoB2ucItJ2xIVbB+kHBOXKlh9
oYwuGF42wnYrfrh0IOnVF2rmj5bP5vr6XO8FJec2rkz3X1C+zCVJaRmO+rRkfXJZKewzhoZiB4Ip
h8O+fnHgRhs2+oo9jy/wwT5jIBzb15eQLOaF0wNP5oS6w3X/dLyorPjNciN9LD1gMhVRv12O9e4s
D6ytc9Ed4Qe+Tm+cV379ZFfpGJN9lkGjYHjg3HuAYngUvV9ZVNpgkpLRyH3bB3biF15hEjR/7aLy
VV7zZ+YUPfnW0D3bTmu/uQHiticvK2+ySAcO9j2de8PGlaOS5rqSmyrgzi/1/Jtd3+mnxzHK8oay
r093NEwvXn28Z7Nqi0vlEwSGZAEVFXPYzhWPqFZPZ159CmrGSHn8oyww54ZntGMiwpbvN736/I6c
G2zawJ29XX08KSUpSclkzuM5ff5MX1Uen9t++1TfZaXJu7YE90lSU4n7a+cX17I9BOBnJ12If3mT
r8kkxfpCa94aguJ1c8rvqLFeM93+9LvxtQ1uuMZaD3ffjCcrMt2hNjV6mo73tarjbvr2hf5iZpqN
F5nOQMmjJoCfyeaPNaksRI9oXI9fr16UFelC+M8VTyF2C7FViJ6z40ljrLJkXlRjk1r5NGpdXopH
ZVoCtJDEMR0ffxyvAGVInQ7G5y/s2ixEDwOrZnr8evWirEgXwn+ueAqxW4itQvR8GDyF6Pww8It2
VVpnq2FzrfTDHjj1zJt8nwGAkl/bE1q03C9ZTU2SwiZKQglzawnsM2LB0K0nIZyV6oDv8WZ39+n+
mw/FtagFe3B5mK6rw1vB44f7tH0G1m87HtxRW7nEYZpTYtrcn5Yc9keai2f7LOzIWRkID//nnmBL
TKmpKP7P82xbjsYunO6tBHTp9PHO0B3vRkJqX8QPefEk770ziugZzUAw8i97g9tG5DsXVFzlk4+d
7L/1KACTF9f57290JAeHbnprMCRZ75/nXx6wodF06sCpgXsODYuaVzeW/b8G6+v7ur/Ww5Yum/Op
S/xSR//nsY9Sc4X33vOKam3otAOdCXBrUvtBksWTfHlIGFS38/F5xU1FZmROpt4/HrwdUVECX0lN
FcWPNTsPHei9+zTMQsrqprL/N9n63iEo4pzBiuZf7Oj+QUTK6+zANnyrBv4gUc5IzFAzS5zQijbH
k4uLq23Snnd7vi8V5bl64I53VYf4PK5vN3tnsYcFyZGRl94PfqMr2VThY2j7GDx5dVMpQwtFXGJZ
0fyLt0JLFvilnmifx7XQCxOoMjA0/L03g5txXuV4ALD5/gsCi+2JgxHzBRU28M9QNLZxb/+Tg9CE
bKsbim9tpAdwykAw+r29A5tHoB7OGwKLrckOyTrLa07GR3plK94pVpRsumjozjcGqicV39nkKsMx
Uoai8ef39/9gIMc55AoEszjgvmGapxlBwvCkhtGNlnsvLK6VpIG+4ZjfWYlHRCqeWtxOKK8fjjB5
5ZnfD95YU1IWcDVJiUbclyTfaIMhQ+Sh/niv5IFzcqfW33Uzypa4pNiI4rDJ7PgF2Vgi5YQwY0tr
HfuTlFAu6hGlcnQSMzCI/CIPMXC2HCKnOIYeEYMeLdoS8Yj8wENNVMkBiPwij6gTRDi/Xr2eHhGD
Hi3qFPWI/MAzKn6pttpV0xpnz1BkX8ANU6uQzPDk+hLz8J1vhFpZLc1L2/Z0fwNmTpxSfNlTSmxd
U+COKgzjz19auebMwPUHCnkWfDb4xf6KfRR1AhwqciKnCPV6eqBp3CTaEvWIgsAzqv9FfpFH1Al6
qMiJnCLU6+kRMejRoi1Rj8gPPH+0+EWcKg3TLiRAnPXnK7LAeW4yOPSDGO8ndEyWYtE1m9vXvBEW
9hmK5HB9oQaXy6f24i0dJJfdVmwxTfGIm3GoRlU+vGxSr7TB2sItYs092zuWvgjnHPCg2vrUsrKF
fotlJNHaFx9Ky8Ve198u9tVIkttsLrLZ1s70VkqptqGUZDI11Pj/tQ7mZ65KJfDJ92wP7DPOBGNt
MaXY7/768sBqSdp4KgYPfWZNK/lrhyzZnPfPdBXbTAdODIUkePpewZ4WpY73jcRM5ln1pT9oUu9e
AR+kmmKrw2KustMAY18CNlOVmznQU/ToPC/sMwbC8baYaVaVA0/DMSmLG8pGRYLnQBeXwmodG4of
YOfqzdPKvluNqyD/64qnHSbz+ZNhcwaV5pXVDgDAioDBciUW5b4EmMjvbBl0Vidl9GuGcGslSfan
lpc2ucww6N/uSrrNpjxXlzBXS5LHs/FiPyKPxlvDKYvNtnpexXcnmTW08AANnaOhhSKgNalo02a/
zdxQ41noNfWGEzi4Ra77L/T6ECtI8SRXeSzFRc4lFbah8HDrUKrI5bjp4sA6DChl3azy+6fDAzjp
TF/szIgEg3v/yvLrcKyYlNcB+wwoWKxSIk06lWRKcZYUf312UZkNQwKe2YHC6xeDQpVBcwUUTdc1
FD+7suY7C4pxn5FM7jjcf/tWOoFIv90efX5v1yffCuLej3WT5aY5PrCYhkiDWkwjI0cgwE2wn0h/
bVfn0s1dT+JeCltrKpz4PD6Z7sWiIhV77qq3StGhb7wfhWriYTmp0hSyttEyzsa0kc7cnCIW8pw/
EKEmrmQ0C5k6zpZjCzioiRPEwIsZFXmUnk7RxMcJfyz2dhjutTLPUNZPhrkk1RrMvMFT5TEXuUxO
bZRpXpqMz0qtT15ckjelmOOSel4Cp3vawQkfB8P/Zx+rYpyL/hTrucNzCJGfkOTnf3Lxn9NHtUgb
ZugMJOgk9UqqcOGtdixJ8c3docpoH6oL/vo8L9w7njkRfFr9fop8pCv4z3FLaJD2E6pOlLJZ62BJ
GIm/ivegZA5qM3ahUFNdhA9uwqEVb8DGBZpsT11R3mAxlUkyu7PEZzp3bcfT7OZJJd+d7ZpcZpVO
0hXE9di/hE++Uz99vfMHg2j2xjkVt9TYb55hu/bQwL+3O+6osVx3Ycn5kgNOrc+c6r2/B89L8On7
yPBXtvTtBCd4irZe7Kuth1NuugMAzcpI1jE84KeExP1zvOCu48d6Pt+KhyVfWVS51g9rDzSJSLDL
HMnmY6ZymBxikTWvBYGzpsL/s3mumoBd6qAlB5WHBoZbk95ZXsdqKbzZZpvG9i+WIvtyKbzNYZ/h
AC9FnhmxP6V29swP8Kafd9a++RANH9plf9CIDCxRJeTwJyXsrsdXFoPbezv7/3IfAqhgTMzVA8zV
fuZqC7j6a80+AAJ+u/ZADMSbJ2FT86zimS+GGFrnamlws82uoXUslwa3ORwq2rjyBdSc2vj6mcdg
aGz2Z1eWVTqs9ZKyT4s9BknBcxvVCrhUuXle1U0V1i/Otre8J900GTaXqed3nvnOALDIX7mgYm2p
9bPT7c+8S0JS24ne6w+NNLvlfTHbpstLpa7gJ/dGmyaVAnfb4e7rjyLbX19QdX2peV6JuaUHvIRO
YM6xPLKyciHuWpS2nujLp4ae7FF1slblB+/2M07cyhBOlsvsTZhUb4LcC9pUgkUsL8Iuzf2f8/A5
/L7WQXbPantyIURO6qdvhvaW+JlOyPLHiCoFPQXxaPpUZq6W15NCyCFBK9evV09sjF1lzpc9hzxk
iCv8OOCHzqa2nYovnO1cVGNnz1BsqwJmKRx+O+pqwgBBJyRgIjLBZAgJ/a/NS4pkswhTCmxqS2hK
2byvz+usvKNK+umrnU+rOxbuzDHGGg2wRMxcRKvWjYExdHIlHwEPx2ng527nxEfpf3UgaKvBEXAC
m2EBlxVJkdUcangRaEWG/yTFYr8CLgYp+exhfvgPV0OSzeA5/FjETQHe7ZEhzJlOVMV0Sh3twc/0
h8okaXGxbVqRtdFvD8CSnJZonwE8rcfCsPhB2tc9PCC52PrLYTPCZg4whhK/+64ypp69PFHkNkPh
mXd7l5RWLnQ5ZwHooaG7cL2UavGeQGo9GtrJBKXBwft2JxzR5GFFPdggeNTI8oxFWTFXuWQpHf/R
7+Nw9cmK8p0DQ39xMdyow8WvISlx31nGRldDAl/xRVc43FtX2t4/M7y9I7x0My1jqJ6BhjzxWl9q
VoVtqU/a4XCCTzCZbBe4pI4yJ2zvWk8PSzab2tkSV7YJGFl1XlGdDbIcdcb/WNU8HV8VSAZDsM8g
01CExFyNDIKr5TJ0Sfx7zG+gcd/pgR1TXUsc1nkODW2xtMMuoHVLHaUMbfuwzPwZ6xv8tzD+e8Jy
PAFPVypNaTZvZsChbUzx/3o/Bv80KED6rwPhz1T44VDH57OCH2J94e+ozz6Uf94fXrnCX1bqnKQk
2L4g9fIxHNN98DQDzq7wrV7UJbETjtppFb+qiO3viv7uQNfSCN88ctMK2zQAt9I1ENvdl9AGAq8C
SLyIBfAhyEGVpODsn053af5mrSoLCwmkvX7PhsU+GDXYz93egYN/87xSfL3pQA+cHfqYbCKdJhOa
MHxmsLHKnIxac3lEnONcv4ifEie0iuz+ino0VCjCbGWuXwO/5hMWGuCpsefPHP+b5Lc7I72znewZ
yohc4aqVpAOnop3F2W+KZq5fYbCS7PRitCnFzi4BG27RM/yMokHnQ68SNIgEbWL4s9Xr6THiR/PT
n6f/td6JnwptNcQHD1zrAAAgAElEQVQqpLuiKZgLYWaHOINEOSPkdZNc3vjI8z2JEKtvrnKzqX/w
GS2IYa1l0cmjlscxHiyfGJHKbHa4cdyHR8qYSHm137G2SHq5M9aaktdPL726Cp/QZxJM5Rk1DBO2
yVk8GndTmQOf0Evm1bP4nSKWi/yOaXK0VUr+c2v0Z3PhEEM6diLMbi6laXgqAU/k0Qbh39WNy5Vk
VbcaSOcmFZAip0PQF5fSz30VT4IwaMwgmZmLpCnV/7X3Iv80211kszZPhj/vHenk8293fwceuGo+
Ac9sOR27pcLdVOG40g5PIhIbD46sn+meU2EfwgU/9caZZFMZHilhZ3NN2JsU1gXBcbk9yC5b/O6b
HYNPkpDahMs8JNgXZLk6ljyckU2/HUwtqZLAByra8my05RrazqQioz/hPU0adMozmhhF/kcyrXSy
4SAacBX7Hc2nMM5EMBBuuG5bTKUUF+nE+yy0cJrjewlJOtw+sLHCur7CWux1LIO/aVJsKPrAa/3q
5hJtQEo9vKP3/zR5Lq6wL5xWunCa1BuMvnA4/GQ/WoCUC1uNRBm/IWCCzZa0E7ZGLP6JHXIoQr64
ruSbs5CLnxv5AsXs/Wgl6nB9bYbk8sD4SjU1xX/vHP6Po8MQlvrTNNM9ZpaDk/tZr15URvgJNtRz
QuQRaT2dBv4ct4PT9HyV8adJkpPwDEVZ7XWsMSnSJHh4mtrSlrTT/USGbxRKScdGnVL+uU+4DEaR
G6VKD6devajCiB/yxsc5/sV44LQ4afNKKTQ0AjN7kb/oZtvgf8GzPrYxx2ab8/bZfgfsjV/ueDqB
69BV+ChReu8UnrrTrKTgbSjsNviGAOUowb1PFCZtm/nCSsuTp5ICv/Sl88uWOaSFUufT9pL1VTYp
nXj7VGRPcGRXr/LlSyuaYVcO+vjijgS7p9Q0i5+tIQDvcsQiD+wcjFkRB3ydttppluKJw7gLsj80
C/cZkJpmlS4/3bMNtkBsk5GAjjLkkF9Z61lgTb8Aax1LdI0BCTyQI5sdX2dh67LsgwU0qdVj97Hv
0NHDAyqSB3cMDtsQyXBKqoITlDiclyjejuBnOgdm+R0rq5wLA84ym2Xt/OKWl/pbmUXK2nuibZK7
trLoKpNZGon9+ER0+Ux3ba3PAy+vRoc2xpWQ2tmhB3YOxeGuBTsrVztNSjzZiihYyiN4N8mlZ071
PW/23lJjvelC3+btoQ5YHTVXU8dhoFVNRNhMAUXpwKkTY2CaB4YnDT7IRXtyOButxHYaeMyQAUB6
wSILGyhR/GB1GkdLtSzj9iIWih014ZIcY0cUoAT5aecxkupFGTxd6Ec5FRvVscs+/eN93T82m1ZU
OC+qcM2D93+LXP9vRuS6gzExVtsjsa/tjUlmy4313mvgp1/8rpsudN0wNHTjq/RTB2ANdZNa/Dey
cVSTB0Lp5lLZbsKbe8RvstZjSMhOhn95Y9nX2fOk1sM9N7M3fwF5hV19CrNwilfVJkllpa5Vpabn
jkQ136rXEVMLTiPGDAbylYifq+JEIbLicIyhk4IBNOvx69eDWwz84LnRxw79RgOWluCE9NenY6tn
OZc1eST4fmo4/L+ydCMfToEAKSixb5eotSf4lFLpXFiemVKoGSKBhdDoGATFWaQRP9wdRvwzV0ws
frj36HAZixS4kONffPhX+AzbfMOF/rnaAaAim//+gmJcX/sGYZ8BIopswWcH0si2Xgx6mKRo1lNk
U7XVBDOoqJOZSP33EdyUzJoVuLMYBOlPWj21FPYZsI4/35lqLMbdz4H3uu8+NPR010iry87e4We/
YYA2MfEhpyLlGVvDySGoctgqRpK7wokdgwm53PvVhWVfbrIDvNsW4qn1UE94M3TQZL//AjyZfI09
kp8+uUjD77x1dvHq6UXV6t0sdmRXFz4h8tJZpCSvq1W/7A5w8FTD4vw/k+AQCCFe2VjEThokWO8J
SSCZ3DmISJQKQBIAJDUB/wtXTNp4vnNnT/Qb7/b/5ZY+tlLKLvI/Tgq4bslKfBe8EeZyNDik3p7h
kDxyIKpYXLYyk9R2JhoCczEyYS9PJHcM4p+EnQ3c2YRLspq0eQyXRjWRK1WHdgXjT7/b3wqddXke
brRhL9QW9YM7HDDBvk0yOb9Yq21SvZ7lRcCWPDQMyuNvcrTdw2Elno02M3Can1X9bMEW44fVW5w3
VWF8giuunuoBl8JxSHsQnppJRQHPdbhSA5u8bgp6OxYZoQMq7F8mDrEEZyiA/8Z5VS9cUXN/cbql
bfCe3d3r2SspxW5a75kQcw5zuyInkxuO9F3zu9MP7h1gXTDDkQkoAdiUowAkNtzweaAfHt2YLp3m
pH4tqiuCo76hYGy/Aq8B+dk+I/Xy7o4vHuFHRnJr58CDb/Z8883uB3b2PLij699PYHQdP9b3ldcH
3sngV/1D/mem0SwVkRISIIeSij8TP8hMqwUTV/Hn+J8XOUGKRZ2kXDNIwND/rIbjRAKU5OghwAwA
slORCWYy0RaLfIr/jxF+7ot3zkRgNmio98HrUwfa4ZkmjCxduZjjDYXFvgonTPC2dQl+VRATn1J2
9A5/473MlAIHI7Dvhckcjkj4QGBFdjL8nx+3ok/AW1RkbqOAh5wTWM3DnhOMOeP2j4P/qcv5OS4Y
5EHwDhDkIyC+/05wxeVllUXu7652tPWN9KflulJHMUZ16pfvD8JcgMlmqwMFyeRBOBpnFZRNrS75
r2bXUE//mt14nXCdQBxu7/t5reNTfvP6xTWXhWJHIumKEkct+1br8aP9LSlpxUBKCpibZgTutwyN
FDmvmOzEa8piu9iuvERGcSUBKmOQFXGYVVvp2K+7Un9VYb39isrFRyMhl+PSKlx33z0Va6ryX49v
low8vjfUkoqfvyZQWer/7qTYHW3h1rSryevdtMS85UxqXoMXloqBjsFNsvxl1iVQHk3hOWTDtMBT
3mjYYm8uZWcIafBe6tsHhpYtLGqeXfmkd7DN4lgFXxillFKR3HF55RJA4nRcWs2QnBxu70+fkYoq
AyW/WGh/pT85swYXp2RkBJYZEKWOUL+2tY+s9+M3hA93j8hK+s3e5DJ8LzL95uk4jkJymDqbbwLm
ewYR1Gm+0k4OsErwodVskpWRv3ln8IWFngb4ek77mZfVDmhXl+p57Ox//j66pNkFnf3v4sF3k5aV
9fi6TO/pwa1M+db2kU8R2h7Yf6Xf0tDuasenGmrYsA4yC4qKEDcDYlLtLWyufNw32Ol0raoAxuRP
3x+W48qmPv9nS613rKpoPhqRit3LAuiNbcfhRRCtv0wT+pD9ZFlRwP/sIvsvOuLwtvOSBZX/fmLo
SMpyaQOebP2+A9Z+coUQPwwehdO2M4Nbu4Ym2eXTXGfGh/DQTIX9yvHB3mn2sqqyZ03hN+O2v8Cj
vvRvDw7B7vzOmfSU3dw8PfD8eXD9wD9xKFuG4cuKwW19+DCIrSJyjSt1hySFoyO7wkkaLzEGGBvP
MmNHg8jy0fEzGXCter3o6+TKs4jMNSX4hHSSaaALwyCqNfBrl1OWV9hjQRMLqvjw2yFltQ8GLrGl
LQGjAG7W3J54B47QAubrLypv6BiprHQ3sBeSYIg7+qJnJDdMKb9cYN/Wn5pVg4+2YUqB/W71MMxd
5ksXVn73eP8dR2AaycQDaGZFI37EwVBpI/4pNrJdM/71m82vlnDvAA7lPgXVpF1ODl+3teftINzq
mmtLnc0B3GcMDUW/u73z+7B/YNGP9x14rD3SqhapHhSi9qT6Qj7SYnpsZ+d/n4oNwaN3n2NhtQv3
GcnE9ve6P38Y3sJTth7t3x5K41coZ5WsnexMBiNvh/B8ZVqJmS63KN6kgiGwgg/p4Rtc+fif3HPm
fzrwqGFho29VlR1e8t/3++57u833zsF5/+39fc+lAWL8/v14xNI8q+RSOfnFV3oPwHcgfe610+Fr
q3CEEHqA3fgyE9jN9jMDP+3Cm9eGiiLYZ5zpi8MyBT+eAdbDPcEHfh+Fx/RNk72wzxjCp0R4Mw3d
yUJSTUh67ulV4MHqP+4fhB9gLQu4PzXdx76iFvmHN2EPp/kfpwNM8A4jO/BI7O5Jga1tZ4ZReyz2
m4g6Ck/u6fppp9ZZzcS97Mc/8ASCpTh7YRJcp5aFmySoSaQAqxzqDf13F+i2XDOniNppdwUMoqtb
O/sfOBgZkuSGSd619S5gPd7ef9N7MUAOSkS0ILhVRTu8CZZdZMgMGS5SsIEjhLnxQxNrujcmz6r3
4T4jmdz8djf9OtwP3jzzPAyEybpsWjHuM5LJl/d2fQOfmmjauA+HY+8OwdJuqvS7/N1B8FJSMjfX
+z7V6C4zKcdP9d3eiW+NgCD8Ef58/0NNewze1iT8Khu6MS1F1TUAdoCxm3YM9Kalygrv2skOiLcd
73U/Bu+lat/EgSgtK7KyX9S1FNvMRU66E4XhQNiQ4+EgS4QEzEGJciAYj4pTAwxFqlHrgXlUWa6K
MwAbU6jmNBCUc0MERj+nQMrgJ53cBDdKGrhaxsZhc2Ic/4MSUMiVky0OmxNaParVR64iYh9/TPjT
aTzygqBiw/1sG5ZiwQi9Axdnz2fp+n1yf18rfK3aZltSX9TgSB1gJ7JwHSnp+Df2hWlKWT8df/Ym
NhR5aFcY9GxqG4KzQIvF0tzogVNqbRQ4YfgfAgadQJHzJxk/fzT42ZU1Sibfta19d5TurjLN4Gu6
sLHKbGp2sX9uLZ7cH8c1ieaRDHdhlKiTKTfBrzjg7+Cl0jsjuQBqHJZam9wHrx9+oH/gTbVlsSyG
FyPSysFIEl5ihcRnKz3INW5LrXl0u6pOu2Wx3RQbSbwDXzfRdgOaNhP8EoNztO5IZvNi+AWOlHIg
ksRLX0jT3NZSs9IXS4k9FX0l8I6JX98EaRB1jusH0agOLTd7LXAi2xZOtudxiLbExoLtmv91VfVC
KfLZl/td4B8JI0TUiXrsliV2eRj+rb684BEtAl1jM0OMtbPXcTCY4d8OTCltkVFgc0HRFq8EYjz8
hfpkPD2izQ9Cf1D8Y9kSdRr4x/IU2yuQi3LYzsZvOf6vLrJONkl9kcTh3LlTGnVKgeCtcciDiXQ4
jz8HJBRFW2LrOcRPJkTl55A28Oc7U/TJ2YxjvuacmgUu8+crUo3VPrcbfglLfUL9yms7R99q5AiP
W5xoN/T49erHBXCWDBO1q8evV3+W8MYVn6hdPX69+nEBnCVDnl34fYuqhaboHb/r2zea6jx+dfur
Vz+ajnNZN1G7evx69ecS62i6JmpXj1+vfjSb57Juonb1+PXqzyXW0XRN1K4ev179aDbPZd1E7erx
69WfS6yj6ZqoXT1+vfrRbJ7Luona1ePXq58QVr2thvZy34SU5THDLgnqKBeJPEa1Qo9fr15Pz7mq
n6hdPX69+nOFU0/PRO3q8evV69k9V/X5dvH3LXT+cTgwms9PSPTqzxVOPT0TtavHr1evZ/dc1U/U
rh6/Xv25wqmnZ6J29fj16vXsnqv6idrV49erP1c49fRM1K4ev169nt1zVT9Ru3r8evXnCqeenona
1ePXq9ezO6F6ttWgB6/4yBhm8VxxqhuTJVfk3JQLMVwATwEs5wZvrpZCDBfAUwBLruVzUy7EcAE8
BbDk403d/2pngxl+QvQsUiGGC+ApgOUsQI4hWojhAngKYBkDxFk0FWK4AJ4CWM4C5BiihRgugKcA
ljFAnEVTIYYL4CmA5SxAjiFaiOECeApgGQPEWTQVYrgAngJYzgLkGKKFGC6ERzPBXonHd2K0fQYI
wx8kyrW9x5gsGnOerGZFUMh4UDf77QYyQjky8TIQHBIQkCjPZoFKlBgTHJcGgmvldpjqHKVaUW3T
PrgM/eqEgZ95/kPyfziWzH0Jw/A/i0TBDRj5H5L/taAXPgXDSBrxD04w/E8BIsQGVlCRmngu8Bjx
Ax5AJ/x5xg+NNB94JKAKthraGq6zJqOcNq3w1ZoT0IoMBbhMtQOS3BBiyErwUj0k9mq9SqjNaINZ
gh8MYMQoarhaIICf8uxtAW/hhIGfeVbNDP9j2GQHB4aeEf/gBHAL5ZxgFWJmxI8RP+Lci7FBUzcQ
PGw4IYYOo434+bOIHxrg3NE14c86sfVWnFKBi0dIroRWpt9IgBz+gJlykhpdlrflbBe0ImhBnSxH
gukka1khCOagL4xTzFFCWxIYSaK6OTdByClnZlHrKIm3aYABBTpVKyIBPAZ+5rvRfSi41fC/ET94
pWl/GDDG9TvGtUNXFHMXn3Y4QW405h+KJhZKwlwzGmnMPx/S/MMu6VE8ju9q0EIOhoHA2NUItZ4t
7TQw0EQMKg+t+qySy4o8eAEgK8vRgCZPBKtHQU0P41MzqlQDgsnyb8uPi4HAGPgN/xvxI15HcGmN
e+2IPEb8GPFjxI+xfrGf/qFfFsTVebw5hLcjs5oU9gt1dDlBFWchgnJxKwA1fLeAUmyXAIJ6PFn1
2VsWdfw0JPSZG9ZsL4L6GTYq5WKAJo2NAAM/EZRnYdBUIQ9TSrJ6PFn1Bn42SIb/1egy4ofFg5gZ
1y95w5h/Rpl7jfnzYzJ/5v7clDpDWI4MJV8dYL8lyabOUXcA4mySocU1R5TVq89IahsHNR61osgA
dJYeeCwB74OAmeyGLB5NhDGNn+nJ6tWLGifMY+AX3cdoPR/q1YsKJsxj+F90n+F/4Z5DnLtEJ2XF
mBE/omuM+DHiBy4PbcFlJD8P8KXhX4qgX0POihn4RzbBa7DhhGuJEZCjJCuiNK3ulLN6FGf1WAeC
eSzIwBMJ5jFlVTMl+YqyeIT3ThEee9LDARv4wSXkLu54lchyYoYpq9rwvxH/mdDIjqCsQMkwZVUb
8WPETyY0jPgZber9uK1f2VHASha2ROHqzc4MhJMDPEJg9biij/oSh1ivbXBy9ZBaZmrCGQFgsxod
adDLGkI1WsV2A7/h//zwEgLFiB92iagXMlzOdNFkrmsjfoz4YdcLTvssOIz5nyJCdQgVJpR/XOcf
HY/Ba6EUWyy80JM0JwkExRyX5+xE5BRVDVDL9WAVS1TJBbRq5OT8Io9Qr4chS5YscrsaoSdLQDgc
TmTp5CCBELGJ9QLOLB6hXg9Dli0CrMHGJpb0ZA38qoMEPxv+52HDCSN+tAtJ2E+pVezDiB+aasQc
HENFulfkt6DCcmHMP2oQGfEjRg7QWuSIFxn8a39C8SyWUkHLxJfkLOGzKBj4yXkT9cNZuDxLdKJ2
xUtUVDRRPaLs2dATtWvgB4+dw2T4n5w5UT+cqyGYqF0j/o34F2OPx8/obqGtBm/jhKhCjybmUUV4
pRiOUElFUsh5iKC8EH4RjygL9VynyKNH58iKbFxPIXhEPYXw5xvi5jgh8ujRot0cHq6nEDyinkL4
RVuiLNRzuyKPHp0jK7JxPYXgEfUUwp9viJvjhMijR4t2c3i4nkLwiHoK4RdtibJQz+2KPHp0jqzI
xvUUgkfUUwh/viFujhMijx4t2s3h4XoKwSPqKYRftCXKQj23K/Lo0TmyIhvXUwgeUU8h/PmGuDlO
iDx6tGg3h4frKQSPqKcQftGWKAv13K7Io0fnyIpsXE8heEQ9hfDnG+LmOCHy6NGi3RwerqcQPKKe
QvhFW6Is1HO7Io9Kw1YDtI+dJqAuT9FEZQvhH8MdefaxohCdowp+ANlCbBn49bydX1+IP0WpQvgN
/4seG5suxJ+ihkL4Df+LHhubLsSfooZC+A3/ix4bmy7En6KGQvg/bv5X/SO+qyG6TKTldT6LR5IG
48mWGLlSbM2jgYWcCS2iV/MYP2hFIcP5QXWDnIF/HOcZ/h/TQUb8jOmes9v6j6Mamw3/j+Mk4/od
00FG/Izpng98/epsNcjdZlvL0oorah0OzfZgaOhH287cGaZgleaWeP93WWCGB79Em4zHn3uj49rT
SfWUBDYZkPKG7bFL675cZ2NtlCmxeKr9zMDXtgc3CLW5pKhHbNPbykyUP0cnFEX8Lvf2eba/fz24
ldSKzAXSE8VD/Lai/k9XWdu6PFvDqh29/oowCLmG/9GV9XdOMv3w58f+OiqtqCvfsswn8kppZTAW
f+vdnlWtsaz6nEIGv9xy1ZS1JenHf378toj+VjLDn62oMPy3NJbeUBRdtm9YEj1QiGy2tUxpov48
O/xoV/O/utt2sxB6LbiV6jPIxqK+dXHdPVNsu149vvg4u6wAFUtrGytbLvbsfP3YkmMp9RLLUZOP
3+Hpvq4yEA9f/b9dLbJl56caFrlEGSWZSB1pC/5/rw+0EMIc/MALNajW2rKqam21HYXTqT0Huxbs
gTgYL+XjIQlVZ574RPlFBePgF1kLpieKZ6L8AMThbr+2uhqIwdDK57rVOGF65laW7b7cDzP1rteP
Lz6WLBi0wKiYf7SkpHtvz705V7nhf8FJKvknGj+8I38M+DkYgRD+uTWhlk2UziOfqVuL+4z0ya6h
XW3RYFry+Iq+vK7+hzBJwTVgd2/6RAXsMwZD0T29Ixa7ff2KumdLhE0Pv96g8zymTezHPVLpYDQJ
f4MJyWG3NNaVPf2Z6rsAAIhQzglWwfAwJaSK59AKdH6iSs7GCQ4JCPEPNJBFTlArCCqW3Wurl9Y7
a6AGi3l/XIQTxMOLQIAg5RwJEbyJtWcyld8EP4ZiMQsdnygG0KMwhyMheVEXJNX5wWgqpsgel2Pl
otqdjTCVsa5RDoZ4EQgVj3TX+TVrSzBm7FCjVTLW7Iw3ERvPC8Fv9z52UcmSChu6WhY8UIgsh80J
wqXiEbQRJN61bPiZrnHkREwUA0ihCAuhOmcNFaFG/APTUKREBLXC6mPFsXPZtK+aczBmrHfTYEJl
fqJKzg+ERcYbBpPJAzToRwXKILsG6TK0WC0zpgR+doVPBUMYiJn0QA3uUepxnxGL7ekYTprM88+r
PjjTqoc/Uw8aIJEeMadK1piV6fEjhmzvEU4QBoISEVRPzGQRaiYkK+oEQUikR8ypkjVmZXr8Y2Aw
meHkGJOn6ItwOyDgv3mGh12cksvCvttPTTwHEaApEUFNQv1jK+pumuYtBy0ieA5Sk8588qYcftAM
NaRfzAVbKhhqJWZSMlFZUSdogER6xJwqWWNWpsc/UQygh0Q4Qf0SczAMRUpEUKtYr4cHeKhJldc+
9PhBMyEhEzwXbUElFTkziJDUhGRFnSAIifSIOVWyxnEzYYEReWX52dXVjSYpORj6v7/sfoIgSpZN
V9WtLrH81SXFt704sK7OB3vwWFeP98UB8PV9F9Z+c4Zj1XkeaftgxvVZOjOFPTtPLKAbMkmaW+p9
fnVFndX91Yvdj74m3CFxl2XkGEVgIIfEvclKmUyPR6zPcOfpIdMqg5JIA6W0k8Wx7eboRDmxitEi
hrHxx8Oep8NZfRRlRcU5evKNAjMhh7umtu6SrYNq8EnSDy+tu7XOtmCGb+7Rvv05OqEoqvIVPzTX
yViUOHHm2OXiIk6RR6znzECIPEkFfrw2MYJOl8ADT4VV5ISfcpFf1CPSwAOJcqqPadpInFoJEjHw
XMQp2hLrOXO+HtEosmkhBORE8MdSKIxdEBXK0vOtHfJhralA/EkJb4fT0iB1B6QSkXU/79zK1ID+
dbVlP1vhd1SU/tAdwvOq/CRL6xoDeBYyOLDylz1w202HZDOm++Ye6M2KHE0nforIqV70IYEpnEeU
JW2U5+jJVwhsIMvzHH7WkpuRknxVIgY9PXo8Yr1oD/Sk2QBhpfniRqe0e1hrd1xRSTsNVkG90LOr
yeAnIWc5CyQlDEcaXHBsPSJOLgI6xfocW9RElWRaZCBZnos6c9h4kZTkqxIx6OnR4xHruSEgcvTk
GwUekOV5Dj9ryc1ISb4qEYOeHj0esV60l6Mn3yhHTr3I4RdVcZqU5KsSMYyuJ18GlUIQ0w+DZrvb
7rkyADc+qQ0vavsMhJhcs7U3/KlyyWpZh9rw/8GwuugcGMaihd2BLZ9U9otLfF1HO2e+GVWjE9qE
ZIXbMoXmUWl/f7h+iy1xuT8wpeS+nZGHsdr67IrKq+jBTTp16Gjvp3eG1bnM7d69qny+D6+9ZCz2
3I7Oa9vokY3lJ0srP1nj8FhlKZXu6Ar9w0u9T1CXM64xt1wxeak58nLQevU0F6hIxuIvvdW55gT7
XXbRaCp16BgzqsDuavIiPC12/+YzDdteO7WmTYWNvXe4j6wtD50YqmwsrrZKJw+31++I3tJU9o/z
iwMAQ5KCPaGHtnU/SoeWDuf2FeVLymxgN9g18OqwY4U/duPzPS1295F1ldLxM1PfjDBfmVvWTF5h
HrrxhZ4Wm+vw1VW2U2fqdsRarpy01Jo4LdnnlFiS0ejDz7U/6BjNFWA1019tTKES0NIf0GbExkYP
P297M3h9XYXHY//SBZP+qtH6xmunVlEfZelbiyd9ud78wpZT13aDsHXn6oBHSnVETdUu7e4q29aK
hkDLBY4DZ9LN9S6HlNq89eSaNtMoQwkb0/OrH5xpR3+eZv4ET6ITOqful4+sq8Dbu9rK8FWOG38X
+WfVA5EV9YGWCx2/fS960bySarihT6WPnuy55jU1MNbV+x9bUFLngqBVDh0Ohsp9lX1d9bBzZX3F
fkKyuw6vY/7cGcNIsEZ3DVgvm+KEEYkNRr7zYnfjhdXX1+JgD/aHH9zc9WhSQqOLnG8dj89r8vph
550Y2bGve9kBtgzI+ABxwyVlc3x4vJCMx36z68w6iCVcg0GK+aEO/XBiUKrPDiEMkgVakPSGHtrS
/ah6Gck/XFx1/RS3xwyQYv0OjHPsgtgLRVpeH/jVJe7XXgHvyaOE9JtaSMOgkTgQpIEIyFmTelDH
uFpOB9+K+pe6JLe/uHttabSjp367us2dG/C/tKokeuLM68V4nrlxS89WEFGkrSd6vu6Klw8Oj7LP
yLHLTKgZx5DDI9YzeGqIAnJqAn6RR6wX9Yv1Ir/IQ6pyanKKoh6xSdQp8oj1QEOiXI9HrBf1S1Jd
g2fFnuGtTIca+mYAACAASURBVMPcWu8MONukBAoVYX5glfc146X04iun1nWmJJ9n//KymT4LTm6J
5H54vLUv+tD8SffUY4je8qkp60511e+geYYJixhAORWhhZBTrscj1jNlaibWizpFHm4ip1IsinrE
elGnyCPWE3LK9XjEelG/WC/qFHmAJuU5lWJR1CPWizpFHrGelFOuxyPWi/rFelGnyAM0Kc+pFIui
HrFe1CnyiPUiv0bjQSpa5XwgDHOo3wZ3r8me4Bfg/gaaOE8k5H3qsPeF3hZJaumNwRoamFK5fabr
rtrix2biAe3h41Hg9zrtfqtpqp9dIiTOdOhmnaH9uNxbm3BGtu68rn497DNSyUNdw4Mm84xpFbtW
++eCHpe3/5pq2GfALHyoZ8TicKxf0bC9Hn/w9KGLa66vdzqlxKEOeNBjqq72f+8v/Kq5DH55ks/i
L/Otn+ZKRuMdUcXisK9eOukxMnqtYNSsGZWUkZTagQQ73Mjqgtlc7rDMn4H7DEhes3zLnJrHF/lh
n9HREz0ZVfwB3yPXTLoPFCjW3Z+ctLTMJkVj73bF/RXFa+sdHpfFA02gxG6q8ZrV61yWJxVbPB4L
HnRbLJV2UzkelANym7/EDfsMMGSxK612HVdAc6a/iEotMlLNtB5Rcd1kNy7tieTu/pTDarlojnqO
KymOT01xOqzSsRD+8vS3Lq6GLdfJ/Z0bzmibLZASbcmS12TxOByLcJ8BySzFzaMPJUymZQ6wVeOE
HScpISewlVWFpySByHgA3IvK1y8sqZaSJ0NJyWxqnFLxv7PYez/lpRuXlsE+I9g/fDIqzZhWsshn
LnHg9KrqJytmzZ8Ki4QS7+opzuHBeBCe4nncD3yqAfYZwVB8EB4UlngfXu4FaTRqt6+c4fWPxPd0
xCSrbenCSbub2HiX+Hd9ogL2GbHB4UP9SYvdsXZZPTZB/KOUYxHuMyCZ00lyk0QhhEGyWAiSMt8j
n5p0H3JKDy2ZfOs02GfAI8vhhMdBcZXVBabJazYXmaw1TjP8+ucoIb1s0mNgGOKHEhlXIWhDhk3p
dsignprM9kb29kYyPJKwmurqih9i/oPWL50HaE3hvvSMYpOUiI3UlLVf15j43NTh6ybNHIzcdnqE
7OTm3C6Z4DkZJW6Rh09bhDwfP2fOl9XTKdaTVOE5N8eREyHqFHnOCf5oZFd/WnIVfRGijyn/0vQi
mIkP9fBXNLT5QesIXUoN+MKc4+BVlXN8luHQMEwycEM4f27N7imWYUkh4URKJdQR5x2hfp0T/Dk6
eVFDO4FP0beEkHJRp8hj4Cfnij4RfTUB1zNWUQ95nnJRp8jD/Z+ZerJMsq0G1QhiDR4r2xcLi0qW
FCv0BZ/ogonUsnRhzSMrAnUOOE4ILTiKUf38ye6HtrZ/5bVwvtAoNWg3eRoPdiW4tbthZmARTJTR
8K0/PT7zt6e9z3acTEuOQNkj1eYfXRKA7cPR9087f9k2c9PJ5q1B2OssXViyQrIsD+CS85vnT858
qb3kf06fTEkWl21dnjE6vjh6qN258VTNxqPPwyIqWVZMtt4wSzP6E2b0mQ7QgEarpHWbTu0CM4nB
dRvhHj3bISk680xt3HxEfubEl99O3zMPZuvkj399uGZTe/3Pj/zbsbhkdt5+oXNdY9l8h5QMDVyx
sW3ub0/duHOIoA3CB1ep+T/BatAffHrROnLyULv81LEbX+hapesKjVX/01Pq3bSgdNOFZS0LynZe
Ofm5RTCXSUePhP/jSPAo9LrM+xBb8Vc0eBvh3rpr4N64NLeq7G+m2OCFtbXvDDvYgc0o6gk/oB4M
3fjU4atbTvyirEwdylyvmuPZ252Mtlhk6nPd4JbBtq6STb0teR5A5T85Xt9ynHxYX+2A5XbTEtyC
Hd1/uuSF0/Ubj/y0QxCDCwD+IEEuVJNFiCXvL0+VPNvRw8p73j5Z0nLK+6seGHBHwH0DMUEeDd/4
zKkFL7VdsX0AdMw/v2SdZN50SRnEacfhDucvT898AfBgtM+/oPwWTYr74S9/JYaQLStINmpBcoFT
sntunwZhnPxxy9F6inyKDY5f0yx+6oV0ZjkRuUXa5PgHFgYYDJdU93+6Bt9JjA4+FY7+CuPc/okp
LA4k5+pa2HTE/qc1kQBjVuf1C/3gdXzLiu31dxIbjL4WwKoRDpsTovV8motzIp/nw6jh5jhBVjhs
ToxtnYtzYmz+0VuTL7ZGYVa9eCo9qXSuhhO8/vBO2P9qSZ0ftKJ6KYFRu7UCBioa8rachknmilcx
IGsnOR/e0/6vJyBsUz967vhUONLQSxw2J/Q4z209N8cJ0s/dzomx7XJxTozNf65auTlOfMzx60w9
wlYjz/U0i2VXc3cqt5xf8+UKaEzteb/78b0DPTA7mX3dy+CeWJHiib9vizwaocuDRLLV5JZMftip
sHQJTGPwrvXb8PiDCQ4PffM9PK8OFFnn+hhas/1Hc4p/Mqf4bo+MCF3Oqx3JtijaWnv1lCOXlf+k
Ubrzfw/LG7vg6GW0lHppP53VKFtPwpqCKWMUS4oUi3zzfWaUfbmG3cOaarApN+GGrD+IzxdiiQ2S
tZy1l1T4AN5PZnvL2ILq8VpWTsZOHTwY3MoYNrT2vjuac3O1C2XGntqMyFMbQrK+K0AmM0aCAoF0
uVafV7J6hn/tef5FFXikc/JE9zXvgCtiPz8Jd6j2q9ld+xeb8HjjjQPw5o39FyvhBfiRf/tVNxyV
x1in4uqBv6BWIw++378BDr1CiQV8KKkp41UYaw5SE+OfiEiy4i018fAGJEg5EBtODQXVFrMfRFLR
b7/DnmtI0ud29OMejsQhiiiQKFdFJPLnS2yU4eHHMeh9KvLIAXaDHoocYM1MCQq8u78PegRp64n+
/bgNca50SOWIc/g72twNY/oqrhH2JW4V9sH3UaolNLIfvraB0iyEHNlBMsenBYlVcltgeYl19H0h
hNzS8NDjsFWFNBp+rM8kCGmwDSkT0pnGLEpwu9m2lIUBBsMUt98Me8TI1zfBwxHltvfDsDTNbcJz
nRWN3jrc+YUelpQIbYJ7+q9+6mjJM0e+yry3aAHs9UdLHDYnRuOaYB3Hz4l8BbyJE/k8BdRw2Jwo
QGg8Fg6JE9kSJnnrsQHY+OIzFElZUe+pg/BrDbeN9k9lZkvCTJSGUZNcvsR1k3cvKV0d6ZOfOlz+
CjwFUxzsmamdXVm5UhMrc9icyJfnTZzI5ymghrudEwUIjcfCIXEiX4I3cSKfp4AaDpsTBQiNx8Ih
cSJfgjdxIp+ngBoOmxMFCI3BQv/cGjEAMnUNOD44AlHrxPmeV9JWwPRQk9c3PPxkW+rTDfjgdvPv
jq3pRJ7bDg93X1cVqPXeIoWfGN0gVwXNQMMfJdTsZrsIu6SER6A+sesM2Ccw8mG4gZJwj8/mf6lx
RqBRFaQPCzx8+NxrZ+avqZrhMjdW++Dv+oulo4c7p+6gxULVowql4nti1Bdl3yCbOyUlrhqlIjJy
o0CTXfayK6lSNVEXhnECxq6tq2FPIiTL2oW05VDZPIEi+QTshFK723EqYMyJ3f3KnDLyAPcDKtHc
AjT9kRLGk0E+litIYLScKYEZKRT61z2D8AACXtqANwneah/egD+Xgj6592D4b6aUzZnmkQ5El1fA
afnQj9rS37qkEo434AlLfXPZJkmqL4WC/ImLAmXtoc8dhbVZldWQZwDH8dXO9C584KLyaF4FW2gu
u78kCH7SiNxPFT83BPs8pB32KbiRI4XMUAr3nVas4dg4AxOBDFPiJA6Ipjad1jYoabxxNEM9/aXf
aIcQIP2pt/pT86tN8LAMFURH9qniUEzu6E4urZeFPRiJICMLIQX0r6txsQdU+UHivqM4jf3A52UE
Sd7ZGZemwfpAerg2DTBHjoEBklAv7xvkMcbZQFCkgZOpSsV+vL2vGzsiw1J0ZiD6cJ/m+u6B/TH/
/BLvt6T+8iY49FJefx+wm4pxx6RsfROfn0J6ePeZzzY1zHHYF1uUrUmChxg0c0RQPbBzQo9HrGcG
1EzUQ0ooF/lFHlFWpEV+sV6UFXnEeuAno0Do8Yj1evpJCeUiP9mCqIMXgqI7+pW1JUWftnRJUyFY
EptaE/YarhCkIEFOBK+HAIz8zc7Q9xf7PA77/GnwV3JPamTjltPXwjscWSnfbj4eUYCwEY+Y6+kR
ZUVa5BfrRf0ij1gP/GQaCD0esV5Pv4EfvJSTRD+LPhTrQaRg/+dbYAbZdJ1jWpL2B0fgDtETKP6h
I3ibug4xBQ7PVxaXw/okPXOSzTuJ/Xj0zDDFhg9FpYDLscQtPxEhxNAkQqciGSPcGvoq/1ycZROt
EakOXiyVLLP9stRJnFKNHSZfTOzWML3xdydbRkzssTJ8D9DslFI78VAw+ukXjpTanZ9vKFpc55nh
MzdOq/jR/iF81ySDgXUhnepSr1LZqxF21agksW0TiGhGxY6QKsghsS4z77P7b+xIS+9wTCpyREN3
b+qPOnDrFE1KtV4LLEh18ybDLDK30iyxB0wwazfCuxi4IKoJHqNqJBHkGco1DBnkir4riFkTUTsI
ukkt5sPh6L1tMLycB+rIkCT1hXZEy5b6iloW2Kvh6cCJAbgv/yG9nGh1rT2PvI5IG+uLG91xttXA
Yl4ChYrdBk4wz4aHXp1YBJ4aO9tRIo3FBLqAmWY39PBQWUAF9aoUq0R+ITEpLMtSbKQtIQVMOQzq
bkwTgVauDeoYcyJxgNZljSnvkzCYpsHzmQixWs4vwW2XemptN9cQflRomgEnA1LanjFEFrPssjec
PKMGyStmH9hgO1cVSA2+u0wpB79WTZ/pNDzJpIQHEZjAKM9FWaDpD5Amn2uLtGTwc5xAJJ4+Gpt/
nmPNghIvvB4eC/+wG0bKRBumIdzWqMxRWMVMyrC6z2A2R89EDMABxbET6YccUo4sF9Tj0asnVSQu
8kANGeKa84kcDB8SfthnK15JfvZYBLYal80vkWC73z9wr6Q8pnqM2yXAmKtfU2KQ9x/rvuRYz+Iq
9yfqipZUFwUctvXLy9f9jzaTZtzO9eT3lGpE/+T0nYvo8ejVgyC3K/JAPRTHTjkYuB49KVF/jiwX
0ePRqwdBblfkgXoojp1yMHA9elKi/hxZLqLHo1cPgtyuyAP1UBw75WDgekaT0lFmYlZAkusCRpi+
wz/vgFnEcvOV5TcgB7VaN10G+wx4ft9/Z0xhj0dsl9ZpN2EO5wxYiVLxfbi6y8vtpjmjwaC6RIo2
2mh3RannxHL8gZqeY70PS9IheElPki46HxYoaIVkvn2WGz5AZABbTFM88oa++BN9I09E7F+9fNI3
L69cbbEd/NzUfdfVNoeiX3inZ2bLsR93wcyIytkfx08+oBxUkX4kBKNQhGTRjHIeKfvFE6rnORCK
FEngbbHLURVPPIEI49Lk0m+uqLlvnvO1U3i2P4udSKN7fd7zcdVmwNj9safYMZeKpd5ZuOsChQRb
Y4NPrKFc0VwhMVfEn4jYNFcwlrEztJiNHIv0l9rweziKt689D+5lUy8eAFr537favvo7+Dt19+a2
u3996vkuGDtly+unb9wOI81xckJFCGgFr1Kr9fZZ+F4I7Ku2nML1yuei4FEealJ/OYADF/ZevE4k
QCElIBKno4pkdt09Bw4AICk/vLCEnRwQD+ScIBFyI9DkB+4NXiQGKqLsBdMhAqEoS6XeZhidRGwT
xb+56O4miFymv7T4Ch/wjLD4J0O5OYaQfpDsD8dxf19dTO/KsMinvd3Y+EEpMMAfAYacaqiYUw9N
xEA8lOfoh0rp0fdD8HxqznmldfB87egAO8ZIvtgGh1imyxeAd5lIuXcBeCOdPK4CyNHDi5xAzRoA
gEEI83GOUc/FgeBqOYHaC0tcBAjxD6SpiRPUyotAADzKx8AJUqP2i4sDQYby9UsbjoXhDq5xRhmc
Jr57LHvioTsuq/NqnBRB1nJpOVxESK+oLd93/bRdy4ueaBtc91pn+TPtoASSBzb9+GmuQxFIHzp+
MjNmLvadPJDvB5EHlFHRwE/Dxx2S77cxHa82ir4lDfl6RB5uDohx42d0APy2iesiA9IXtnVdcX11
tc/39OeL/rFruC9laqhw4W2blPrZTnxK/i/7h5YuLlp0ccPBquCeYfOaGT7YHQRPBh+VlLWNVfBr
hkMdZzwvwXWiKhTtz7+4oX8erFiyxWrGr6dCig3+3Wv4vPnR3T13nVdbFygLX2X/7cmR2dNLcAcT
Cz9ydGT/yMC+FcXzF9efqAm+HjRdPtMXwKfIwXuT8Sn9yoyA4zvra1f8fshW5rkM7gakkW7azwiG
2WEAL/Mxk/WNwn2mFc8trJ6Wv7T86vWOz6lKQRb6ldGAxeTQL9pSt9ba77m+4VKYqd3uy+rxuc87
v49saIvff0HRDOyU7benlVVzfbgW0klGZKQfpgNP8bY15r2D8gVTilgTNGf5LRt56u63yRUNea7g
glniUJudRPzUEZX/iYMD/zjPBY6VQqFHQii0NRTfGsrwN8ByI6UPt0c34G4BEjeUQyjZXk3Mnu7X
hjIZrscjnca5tUf8gyGbYz57ZUR9dMJmTk91efsa53ffwC3aaCnL8w/sCP7F6pIZ8yb310X7rY5G
9oZNtlQGPw0c8ycBxjy7qNbDQLBHKrD8V/Rf6Xi5V151nhfW1kPvBVsA697w0ou9EI1HyoN7R6xX
zvBAU88xjH/tfWSuXxZDSC9I4P70p21lED8PXDv5goNDNXWlc2ingT3JwU+d48gzxdGGg7Wa2T/i
TKsSsWemDCiDKjJBNFxxoZf7y9eXQGVi8/vqSD+4t+/2aVWB+qpum/OVoAm8AdPHUfQGl1VV533k
4Bf5yUua3VHCKU+ZWqGnk7ud+Lh+UY+erMgj0mPwc/2F2NXXaZZxLjbjzkCKDbFnKGA0vqkVrzch
Jd/qT8+vNt/0icmNJ2LVk32N8M1zlrZ2DnZIvurqyu7LnL/rSs6ZUgxXcXIwtgFeDsUzOfNlq6bs
PnhmwTswzVJ3SO4c4c/oLMQPY/hT6GuGHIPfwA9uAifwMf1D+58PSGb4kGLfNsyuUkvJoZqfn97V
AycJ5rqKovnVuM8YDA1+u+UYvbbW0trx1b3wqzDyjCkl15/ng9aTx7qWv6Z+twKUJPAFiLykLv8m
v8vqh297WuVYLHHoWM/Vz3Q+ofIO17d0HooqnhLP+nmlM1zyYCj81efPwAWzv6371tcHgimprtZ/
/VxfwCr1dPR9if1o97Vb2/eEUhaXc+28wOpahyU18vzW09qv8HLX00kMR6USUXy0r2sU+vHSUVzw
PB7n5Y103wwlVSdcweyFcFXVbVtP/PgEzMvWReeVra6HH2xI7dnbtgzf54/PfO70u9gp7/q5Pn/W
92aH/+71AVjS/AHPyilF/z977wInRXXlj1c/p3u6p7vnyTyYgWEYEBBGAQVMQEA0qAm40biblV3j
x4SYXY2bxNVP+OWl8Wf+ZhN/a9zEx64x+YhJ1jw2mMSwRsW3GEEFFHnDMMwwT+bVPdPTz/8591Td
PlXd1XarqGjdz3D73HPPq7517q1bt6ob73AYv+2mXhLwx6zwO59wM4yXZtUpUHmggF59QU0qI+Il
BmFQmpKEJpQI/wX3LZRdbw7v1HjMNciDQRlhRkJSY5mHQRxVWDJmTuWWI70/64C3GuwtjUFYZ3T1
wLMn+IKICCYy9hp8M8hhr68um2EnBKRtRTMOkvjNPdr82Nnb79rc1xVPl1eUtpQpezrgyZWh0GGm
BJ7QRZmQkcH9MsPCNImvVmglXT4peNmcQLmShneAZu3CS++mg91f2TYMP4XWMq3istPK4Apx8FD3
Kpb/Wqggq0sh8yRRrtnS8UhPTHF5Vs+Dn+tIdw1jTMIOxY9HrYWkHrv67rXkCoK5hrZQSaYwaDw1
mgX1NEmOxtdM/eR1BCDaN3wNaooSHV3+p552eFxVH1LRONQ9HdEw6moK8pMETH1JuVyEma4ZP5cN
I69Y3WLluT8zXT0/maQTRFn3U3iWjOCP3CRSORpHYTqt1zzXBdMjfP9n6WmhltLEri58Owi7EmM3
PX8CpsdqeFntzEr8GvbwyL9uhhsZ5Xt7h+DuEH4Qdv6c0Dpov/X5QiGt6OPM6JrxNb18n8XqFivP
fZvpmvG5rhldrG6x8tyvma4Zn+ua0cXqFiufw6/tk48c+qN4ZiHyT66M2CrS6VgXdML91VgkJt4f
NFhxrKvE3p7hieyvJhpEi2quCLpanfaeSCzr/3izrat0lyqpnkh8k5wE0XR6ns+92GMbS8B3NGCO
BnTgKIorpk6djrVO5XA0ya6+5padzvXws06J1NbhuEF+bbBkkjN530D6mctalrpGL/nlcbE1Dabg
oFxwUPcN4FVPW6K+ZfxmUAgb73VFgFNSsvyBbzGYnUqPc73PMRaNbcSXe3RlBbwgkkhu0X6RQteX
1YAfBLu2LnHTn3thPYqlriZ9fija1e3FTbXCS47417bU/f5jZS89c3DxMdv6oG3/cHyLcRWjnoL9
A/Et+V0ZUsg8SeZ5nIsBlsiEtm+U367szRG/7Ht3CZHGqVxovBM/71387yRKc933NH51TOWadens
9EQM/zumbYXPPjCR3GlMYHlA72n80uu7R1jxv3tYvh1LKv6fLHff0uqEL2f4fD6HQ71pfurZrXyp
wc2bnbZC+NwOv+QUomsmb2aT8zl9Mny9izbht61aFjn4UoMHD/S76ItMnSSbhrBl8z2N/85VrV+u
t4/2Dd79Wlgp9111ZkW1Q3nl+YML4HdCMjdhMjaeY5JpINT417bUw1Jj19ZD8/bRDF3IcXFT3Fch
umbyZjY5n9Mnw9fJsMlj5vTJ8HUybPKYOX0yfJ0MmzxmTp8MXyfDJo+Z0yfD18mwyWPm9MnwdTJs
8phV+pPlrhxLjWdexOeDWik2FNCDmZEKEbKpsfEzJzNbgMTMYuDyZjbNdM343M57HT8+vLfb8LWM
TDGL04wPmhLb9zr+TNQZyixOM/67Fv/1L3ZfvKa+pbr8xvPhfSEsXUe6tXWGhIh6qM7JzBUnfakV
cYZeKERIdQMhm+SF6pzMbAESyxUDl1XpnDbNdM34YEvaIUI2ucuczGwBEsvjK1uFc4A20zXjg4qM
jQjZ5JZzMrMFSCyPr2wVzgHaTNeMDyoyNiJkk1vOycwWILE8vrJVOAdoM10zPqjI2IiQTW45JzNb
gMTy+MpW4RygzXTN+KAiYyNCNrnlnMxsARLL4ytbhXOANtM144OKjI0I2eSWczKzBUgsj69sFc4B
musaurBJSw0QoiIJjYGf/DCYOUaiCDVB3IxvKmTwldNQgTKgm10+gPHHb3jkcIMzvVEHFkR+qsRv
do7ep/gjo9N/uXd9nX8+/N8hyeQr3WPi69YUZHZIZsmaA/9Nh3r/YaCvE59qURYxm4w0TW3uylSI
ZyxX4A4KlMk+WFCkyK343yG28hTksWPhb83/NGwhW6zxK4cMEvQTXtnTkPg/2Ohnwrg8jjLtv2cj
JaphOrNpEHM+CsN/zSVGIAigiKALnXbBtzDH7ajXY7IpjIMLLGhd1FqQ5Ff0qRX2fyDi3xIWL5YT
OKdg/CrOH6T47zse1n7Ag/KB1W87f+Lxjf0sgT4w+fMBxJ/BROS7gb/BqIW/NX9+KOb/D/n4NQxb
0XSKS3nW5Z/WDWpaMz12NWdcsYDALmGHy/CpgfN16cIu/7QOoCUC6qorDVyvQCP7koxMCET4VdcZ
2FbXPVb8CJu2tLLwt/JHlwNsBMNIwS4xjriMlT9iOrHmHzVXeG6w9MHMsfIHALGuX+J6zFND0uIB
iphhtAu2aJhNMcjXLv/SBhE0Jg1M3lQHLWdptNTlMuSo8NjUBYcVv4aq4ZNjm7MLmFzGwp/Q4DgA
h5oGACV02XzJ4dhKJhHUBTSX4X4Lye1CZKz4JdT8FEimhT9lEeZJrlsU5GtZygGUqWtg8ibHlvO5
Lpex8p/Q4DicEvhDwFkFeOIBinpIYtuAdhR0OwRCL/9hY17KByXsoQaHSU1SCoRhxkiR37ns8NC5
TTNdK366g+dYWfhTFnFMrPwBBKBY4zc/DpQ5VFv5AwhAMRs7dCGw5h+OA2UO1R+J/OEHrNLiAYqa
OnCNhwQSY45PPTyndOmlZRuYQlhNdHHtImzqZDQVY0hCkuQxKmEWZcgIstQ1jRqnsC3Y+WJQ1TVh
csJM5tO14rfwt/JHHXdi9AGNY0eOTcwPrVjjVyBgzZ84bUKBJKF5VkuYzLxt5Y/uspbvGnRqzT80
B2gzgvx0Tvc7l9pNOqWURVgIWAhYCFgIWAhYCFgI5EVgOv7PVjkK/U+bOTosloWAhYCFgIWAhYCF
gIXAO0fAWmq8cwwtCxYCFgIWAhYCFgIWAqYIWEsNU2isDgsBCwELAQsBCwELgXeOgMlSg17qgVoS
5Eo2JZE/BCkmiWx52SWJbJliOdKUJMiCbEoiv2UpJolsedkliWyZYjnSlCTIgmxKIr9lKSaJbHnZ
JYlsmWI50pQkyIJsSiK/ZSkmiWx52SWJbJliOdKUJMiCbEoiv2UpJolsedkliWyZYjnSlCTIgmxK
Ir9lKSaJbHnZJYlsmWI50pQkyIJsSiK/ZSkmiWx52SWJbJliOdKUJMiCbEoiv2UpJolsedkliWyZ
YjnSlCTIgmxKIr9lKSaJbHnZJYlsmWI50pQkyIJsSiK/ZSkmiWx52SWJbJliOdKUJMiCbEoiv2Up
JolsedkliWyZd4PD/w8UZo/eE6Ya2AbC0GR6SELEIEBxE5FfnnqzZfLYMXjMbprZNONzC3n8yiC5
vJnNPHa4ek7azKYZnxvJ49eKnwOVhzbD2YzPTVn4Exp5cOBw5aTNcDbjcyN5/JI6FwbazGYeOwYL
2U0zm2Z8biGPXyt+DlQe2gxnMz43ZeFPaOTBgcNVME0/TJ5XnLvkgnDaqAuYXIbzoYvOLlfMI29m
h/O5/PL3HQAAIABJREFUKYMv3iXpQnS5jMGmFb/hfElggTBgxbskzbGVTIMulzHYtPAHrDg+Zhhy
PqcL0eUyFv6ABhSOA8eHY8tlOJ/ThehyGYNNaGYXM/lC+NyawRfvkjS3KZlAcF0uw/kkxrWINpMv
hM+tGXzxLklzm5IJBNflMpxPYlyLaDP5QvjcmsEX75I0tymZQHBdLsP5JMa1iDaTL4TPrRl88a4s
mu1qcDdczmZv9dlLFdtYPLk/Rt+W1rrBExUiDE3o4jazwmr1Oyvt9vFUakeY/oduzWz2J7fPbXJJ
M36W34ySIWBDE+S4TZst4HLMditbI/BfkxdZTOO3tfodKrYTKTV7DLbfvfjVwzHYL6RpGj9T5lgx
tm5IcD7QBsANTRDgNvPgYDCb3bTil9hycCST4wMCkm/hT3BxfDgmHEwzPuhSFxfmZoHm9mUTCG4z
jx2ylqfm9pnNgNs525XaGkmhKuPrLOXxS2ZBmtuXTYPNPHZ0/nI1uH2zOM34efySWRmwoWnFL09F
Ufjr1wjSBv0wuckq3u7acGbV8toSjyYeHo38Ynv/xrBITUVpKA/ctqC82YMvfIQj4799ref+Qb0f
fppZKixvqvzy7ECVXOekkruPnPju7nCnkP9MW8N1je5trx79alcKBwArl7dNvrbRtW370a8eF9d7
6k2nG+qqfrlA/1+yK0oikewfHfvptoHNE47bz2taIg+DGcTIu/u+0OkxqqfS4Vjslf0nvtEeVQdS
Or1+UeOa4Ph1f+y7clXTQoM1kB+PPbe797ae9O2r8vm6aFsYD8rhzoVt38YIrt7Wndmwvt7Fw0yk
UkOjY796te9hENBjwsWMtAn+KCaNaBgiM488dmvlLXTtXzo9NLDvxMMT6ekNNT890ydOpe328xqX
2CNX/6Vvv1RX7TkQMeh6rPcMeeo7FcncD1F5S29vdf5o50in1DUQ1Hx34jefdsELudCQeIvPPPFY
8QN2BELh5+7DjL/jDpxV0s/89eg3etUJFpKttaHq/jP8O3Z1XNeemD655qdniNHUmXxXxu/6syeL
Ca17B5wLzFV73rmr/6Kdyd9dMKlKS/pEKg1T+FBkfNOrvfeP4ESdPQ8nEikQ+N3O/o3D+lspK/8/
rPmv7T9oaaJ+2umXObElh71KlPz8Ew2rcZ2R6uiPbOseH0op/jLf+uUNV3uFciD4wMcqYZ0RHR3f
PRD3+7xXfmzy1aXCD2QtFaNNTMer50++ZR6uM6KR6I6u8L7hhGJ3zJ5W/eC5FQ0gb7OVuHDtUupg
11QyaLO5XWi51A1hw/8lm/FV6hDvt6aS3aMx9S+ScDodteVlG86tblPSY+OJaCwxFE0MaRszYaCj
iXAsNRhPqepKCgXwLwnrC7+nZNncujsmOxAZPBDPmUEl2huBYSkCTPVLX6OxMMj7Slaf1bChwpbP
V0Jcq2zeDLYDHNvJV3uEL/pRNVheUDyxpGK3VwX91y6vX+vSrb0I5gwUDBPsyoW/qiI/pAoQAn/t
eDV1kOQyQMs/2QWE5mvdgobPTvFX2kWccBLxVGJvKZwi+CMx4LLighnLaSvNnHo8myoTqLT9rmU1
Sxo8Vbl0dbG9G/HLA1ED1I7LyGfx62IAPsGFkQsQoJYE1yKaYwti0MyW5zJAy79CfEnXksgfQyE2
uQUemxV/9rmTsEuCo0e0wFDMKrZlC2uWE6TQhSo4gtRBL6YF4y8kvX38vWJCG8N1BhT0lX+eTCoO
O91h0eQZTaQSdluorPTKZfWXuzHtDRMpzK5OJ0xcvvVLm26tsaujgNzJ+u3Hn5n/tfjFURhwlk1J
SNeS4DEAU4d/LptSUQqDCvyBC6oNvsggyfBaqgMhVSRBXmRTEsTnNbcPfGoCIVUkwbWI5rogBk2o
DfJcBmj5l9tXtg/kmLyrYbPfcM6kZruSiIxu2NK/ldwrjm8vnXxe0Pm3bYH7t458aXYI0m6ou28N
3KYryvIZtbfM8F6xIPjrZ4dGKNBcHgM1VVfi/XrqmdeOf+OY+I/UFSUQKPvZsqqqsuD3Z49fsXs8
h5525DFa7kssQJT5CvcOXL4tguoUcKn/4eXVtW7vOf70zc93qGYdvkcurAnFIl94vLdTZSmtk/1A
hrv715C64MOSCEI9o7kscGxoBIKs8jUqyo6uMeiMw7/E2HVP90kLcBXd8LHG1eX2hQ2uT+f1BcHd
8LGaDLbCl6LHlng7dh67rlPs68Dh2N13rahv85RcWOvYdDTrCY6Gj2qMYaJy8nwUomuQ4dayfIlz
lB6Fc2uzHejoXXZUpK9iR9AUBeEzluRXNx8m3ly1C2a9DBPOcRzPe5r/d+4ZG4bYsuJBSYNMRlnr
4hygKX+ghgK61DTI8KbBfs4YuDynC9E1yGSrcw7QVvwGQPI0DdjmPHcGGW4tp/zbwp8GiGL33rjA
95SYVLkfoA8c7Vl21MDTEliGIQkumCv+QFWpmNDEhKkKp9R5EuK3l2bmSZn/bj8+6tZNns5bz528
rMx9QYPz4cPqc3D9ROrcsLh+dZVj2fzqts096rImT2wFx6/ayCn/tvDPXEpy2uQxc9qAbU5dg0y2
OucAfarHbzgc0ZTPMPSdrtKV5XBnmfz11v6t0KPCl7x524lF51XB/War4pwdQIE/v4HrDChP7Rs8
PN3b7HM3K0pvTcW988t6j/Z+3rhusN84Bx9zHN7XLdcZ0BwZGb1uOzzC8DdODS42qtiunltzaWOp
3w67IBNDJSYBYwhwuRfXBiAo4LHwa6NVq4P22SG7EtYuz25VBrYB2UJBry5a978+dGl9NexVwBHB
CFnRAJs5iZd6wQ798KpNbyH1H4fGVy/w+X0swpy+3D4dtsIXIMmwVVkuOByZo8mJP/XE2qa4K4Jw
+2Bcja1tqbqyxV+F7tL9/aM/emXgKbGKW91Stb7VX+VE/tBg+Ccv929Gvn3D4obFruj2Eee5jR4I
NxoZ+/HW/qlzai+tBeNKeDj8/Rf6nkrCdmjlf871vHIsNm+qHyBMJOIv7+2/6XBUxGf/UlvNhXWe
EBpXorHY87v7bj4WW3ta3bX1iM8/ntd04fH+G/q9959Z+tK2zpt7hZLi/PL8urPq0Wk4MvaLl3s3
hmFVYb9hccNK19j1zw6QkKglc+jvlzYsxLhKH1jd+Hp37PTaktd3d331qDqvLZ8xacM09/OvgAtt
25lZeZukhJ301fx/m8beBzUr/vcBdObyneHvr62+tWYs8xhFM1xXV6mNJkh15wbY/6gpwcfX+AB6
4MbdEbgjgtF0/fxJF9d7cPtBx9esaJ9sQtNY8hPi53NXVv6XSkkl8etj0WWzvAltfsUeOQ9jI3Hb
1u6m1Q2znaWfn+y47hiXw+6TUt4Z/iclpKKMnurx5zpYyNMcJRBwQ6YmBofvNlzUxkcv+uPhi549
sR//AxgssLWvlTSuyu12uCD7PO6Q0z4twC66qpC9qgSo+J+OTGha6mfn8RM74Cpod59JT2e07rVz
G66cAusMeIgTTfhKarNNapLZn211lcuDcCFMvjaQiVLRyBy31yn1oMhUa20p7nXACx/YdpwzyaVE
x7eISzgJ6Cx4vd+f4wN+OMJecc3lqwBsybwST+munTMFnifC6s2PKqQoi2fUfW1WGawzugfHu2O2
qqrALcuqGhQFoNsAfKfS3Q98JQTPki5owH1OxVYXcIaC/vMaPdFIbCiheHylXzuvCdYZQ/AkCB6T
Bf0bFuChlzocfrd72TR/KBHb0TuhOF1L5tTd1YTn4OqFkz/b6A3ZU4d7xzqiKY/bfd4ZtV/yKhNK
mo4fnuMC4bM7/HZnnXibBwN2liyp90RHox2RlN9Xuh6eB+GyxDYl5PT74PVYXiQTtjTU85JIpMci
KY/TsbAlEFBlHZdOLYWVy7FRHVbckEVbCJwyCERH79uHcy4+RskKmo0m+60rGsXT7cTh/okoPoCu
ufs0mFvt3z636VJYZ6SAHw0L/q/ONr7EJgznmNB0DnPNXaqA3d7itrd6HfC3vCbwf2bClJ3uH8sz
AGO/P4rzJt47WeWjioC4dNNMjre+MO0jEpNKndARjWvplgOd1PHxdJvbsWRqyf37cN2wuKV8Bq5b
cK1wd3f/D6OuoRG6/WXKbk892I1NvMou2Fp3ehiuoW6bz6WMEguCcfuungJPWxK/fKrjbuCWlD60
alIjXx1RwFDDn6L4a6oeW11J2k673Skkh7oH7zcsmEgiq/aHyr59mgtWS7BdXxXyLqzCy/Lho6O4
+eH1znUr/e2RzEaI0/fj1VM0GzaPuLlXEuP3yV0ZEZImYIItyBDsIMfwJ62ZUyo3+OPwBDeuOGdO
8jX74HiSO/rYUgblPNfNgGVh6omtHTf3w2h33HEBvFzmX+OPnD8F4k8+8nzHD/BdXdsNixvXVLn/
bpb3YVzTYTl84PiVe6KKo/R3F+KrXjve6LzucEzxBx5bXumpKG1Lh9W11Hj4uif6dqSVhvrKBxcE
2k4rb+0MX1wLa4T4Dzcf2wQ+08rVi5qurHG0VTvv3tMdKG28tt72iy0dG5PK9AZcsvDS3d5z+S40
fP3ZTZfWuK+Y6d20O4bPR+zGZysaM3Xb851VF0xZaIdnXvDEynlPi3+2z/8Z7wk8reVlc9ywJh7J
cYrzYquGVIgMj/69pAuJrRCZ9zJm7quQ2AqR4TbfS7qQ2AqRKSpmp33Lvp65TVOXeLw3LvTnfIwC
9mC7cRnc18TGbnysB3edA8Enl1U0TgvOO5E8r8wGT72/uKV/P8ZWcs8F9bNrKm4IjP5gWMwwMhg+
oYEklKz5R8oaCad3wwVTdMzRE9/Ayce07BqBOcfdVOtRjoZNhQwdhWBbiIzB7HvWLCS2QmTes4AN
jgqJrRAZzaxYaojlhbrOAGWtGK5pGps+0z/fO7r67MCMGfWP1o0fTThnl8OaAEoar2MTiU29Wdpo
OZXhUpSoQiU9BA/5YfyIFwmRBVGVOOEqGu0dvBvyE5qxsQc7YhvwCqoVihxqImi42O3yLvqJ7Z03
H8+xrtH0tU86ao/3vOm6TZWOrv7rxEKqrdoH18yXjkdpTUNqgB0cjodWNPDaSkf/l14b7YRIyJok
SFqNUPWo4kBMqgkQ0hVSnnL/6nJVXnwk4AUXhIIXrxNEEoNDuM5A3eQPt3YvdCVf9pR9FqDrHxTr
DOCnf/Da4MpVVVVVvoZ0TGyMJJ85JNaCyYkjMaXKOfZfsM4AC+GxvYnKNnipQot/9/4T8PwIoO08
PvRGLNDm9ixy9H/usfZmeDm3tGRtmbM16D0Tnq9QgZ1Xce9SAumQY6Ua/YlYZ4DsnbuHLq6pDPlx
7Sl1jYTatoncEk+s0onfd8ZmT3GvnFJy/56Jdc1loL+tXQOFY0jxE7ZgRxKqTfFBTKrz6HKVnHQh
uu9Qxoo/J/LEfIfYSst57LwH+IswSpX0TS8OPLqiEh+jVIW/LwcRxEYlrTSKV0P37R/AdQaUkeEN
f415xmKntdZjM6Gsmhq4yAFbzul4HAfk9EqnMpKZekEkM6FBwyz/0VbOkuoYnEgINa/XXQuzbVnl
Q7PjV7wxzqdHrgnf51ebdBTQIqi5ENDvL/5vOzZ5FFb8hKEEhBFiqUFtSgZR90QSeBF1wZcvRCJS
jWK2tU3+sujEI72xzt6B615TvntGIFTmna0o3b0RpcJXm5p4Bm5ZKZNQXMseomMxWIFUud2zHcp+
OYTQLBTH9DK8a49EM8G2BvE5juLNhLGrL6bwpYbQlFW4t++iv+JVp7Uy+MMlFSFFmVHuUI6zGKSo
gRBHnRgdvefNCD5odNrc6dSu3vEdcE0Wx35OPa55nu6HNwQ1zUTki5t790PLXXLHx+oW+mz+ipIq
m9gCkTKSkDAqSs+Yhq1mSf20ZbAlTn/nwM87EyUOvHjH4onneycyeypSN5aC9YJzQqAp3HUOj8Ny
p6EGJfDsynMnnmgoLkeVGlUCvjGXKak0bjVgl3gHk1YO2Ey93AffrKNTmXxtKNlWYyuzp+FWacPp
AbnAyNhRjWunnjpAHbZP4V8sjohREZGHQt5WuZ1hpmsT7+HSK6U2ZfOBkS9PqWpsKgvsSZ8PT9RS
0UfkA2CywO2QL4a/Lie1WPCT6xYiX6wuty/dcSOSacX/0cSfkgGOPTLyowP+DdNL4DHKzl3abgHL
iulBHNmJJIiqZWsv7txeLh41OoNlnw1qHeLTSYJUg520kpnQpCDPT5CU7kDA0ITdlOczb8S3Ta6+
6wx/Y1Ogbfc43p9QYb7A1Jk1eH/Y1Qdf7NMEJKEx8JOYsksSFIDeJtcz6hYiz/W5XzNdLiND5UYk
U4YtCTObXJ3bL0S+WF1uX4bKjUimDFsShcRjsG+wTBcjzCRyQxbxPc0JuID5ywNXu4fvF7fAqqLb
98/zqjxwu/rY0UfSDu/I0Lo/DJTBUiCehGviQ5/yKQmb/om7qocfaDzVDw9bnO7LW0o27Z1QE0s4
DdQEZ8PwScVeHVOma0o94TiseKLjSZmCVeCLCsWsSaqHoDX39w9/6TX3L2EATKu9tb/9Gz3acNUE
8JMOltmJRsYfhhHL+SrWJYur7InByFOkhcpY1COdmPjqlp6HPlnb6Cv73sLoRS9rd9igK42z0zAy
rGHrGr5fu59HcyUZbLEJb632Rjb1iGOnkIgra2K6xNfP4PGNJhPwl147xXV4DBcLUe0tB1RKi5XH
RALWS1gSiYO01KCmEBAdrMIuezMsAccFgDbHnBDgn4g5fBvmBWAl19E98lxv9M3e8ZbTJ1+Jj1Ty
Fcwjp7NRvo1rt8EJjw6N4U5v4QWEx8IvjVadV+a9tkWBp2lDnSNPgXq2EcKfIc/z7S3kC4kHPMpT
zH2Z6ZrJcz7X5Tb5URQiz+2Y0dwO91WsPLfDdblNK36ODNEcN8KKyWx+s2dFQ9MSr+/aMzUuyFNJ
q2/IqROzsLO6KTDflYqK7dzuQz3/pz1RCcMRu2yTPLYj8EIWFDoLyNQmNGmTeoUpcpK3pv1FNf93
dIx0wEzrdMEj5pdyq7kvqMEbjW74rTDyyHODnPJIyAiXocgz8b/VeM8dhp7L/XJfeqlMy0ye8zPS
KjjyyoU9H+34xd0rQEAoUA2gxCN/wK9aOK84p6pNQpl2fHtRJd7d9w9tnFDWtDV8f1nTd+rtndEk
3B+vnlMJV5HwCfqWtq3ObccX90CXatVI6u49+CZG44za2xvd2Cv4sDHys7NRvLtjeKuMIa2MjMVx
xVMTxJcH0ZTjyhbdA45M2FILpKDAbv+xvl/247V02fyaxdBLvqgWIqgrvKtGgJn91hI6VZSQt1lR
DnWJpyegBX+ijJE1tDN+43ZcYfhrq75dDV87FjJkXJWl+EUjxrAlUyjPsNXWHy54loTGNWvkTtbU
lcJdDU9V8HJ83xbLVfNrVk+rOCsxPiSgu5ygSytrWwPwDAi+xYOPeKiQKdkEgv5kr+iaPxVfd8Uw
Av7T4eYkMfGytwRMJQYHrtg2cHd75KmoXSxBSEgRgTgmQ6Jwy6AOxe79m1r4ej1au3xmEIyE8TdS
RVeeinRhjQEERpj+fTtswThXz4KnJ6mtR8ZUiLCL/ZGw8IW2NSM6P+SatKCDmpIgPrdD1qiGXuoi
LanLHYAAlGx5Uszmk0equQwZEcZ0lXQtCeqWTSC4HfKY7Re0SEVnXQMtW57blC6A4H9cBsxCM7uQ
U9KCXmpKgvjcDtDyD3qpi7SkLvcCAlBIhcuTYjYfZOQflyEjwpiuIqekAh3UlATxuR3ymO1XqmSs
J2/aOqDdtQguM/58D74eN3NKmYpA2rt+XuXqWYGu48gPlbv2R2Jbh2NbR+Mr22q/dnbd52vExrA0
Xi4mtE5tj8EsfpI3xC+YeLsCWqJePjMEMz/cgLykTVyKvMMBAYfzhsWTZsBdRSLya7jly8ZEs5NB
PlsG7IOp7AKSUEieCMFADjWBkKECwf9klxQmXV6TU9Li8sChpiSgafiTXUBAoZobBxpUqJaEYOj4
3A7Q8g9UqMugSxaoBgEopMLlSTGbDzLyj8uQEWFMV0nXktB16xqQArlRuHtb/4qLJtWWld31qdKO
/okTKduUKvjGAUgn/+f1EQjokaNj62vLFi5ouOPAyLDfd14tXGISv3gNVxLTG6rhNyLVxxkUMXmB
FUBX/301nvWNriVnNDzaEj0YibtKPOp7HqMjX9k5rqIM8lAmIr/tTlxZ6/7a+fVnHIzU1ZfPxgcq
rIBxKAQZsYkj6Lv/2rfiotpap/fGttJP78DnA1ic4uYeXjOgwJg89etqQDCtrK6Ha21yO7zzIZpM
gJSR23m877eDpZeW289bWPO/fxbvaoGcXfPFdIC8e3v/igsFtp/MwnbXCB6OLDJIOpeSDwR1TYz9
rjOxvsF17cqGeYdGXRWBJfClm9T4wx3hMydXfrbKfe3qyfMOjCihsmW4h5l66iBcmOnVBzKBFsWb
EEioNgUJezZ4acf1StUji0ueGbItm+4H+PftH9454hKbXuX3zFZenrAvmwq/GIuSTjvMaMnOMVjh
Oc5d1HjXwb47CXURKnlZsrDxrgND/X7/ebXASPxuN8TjyASAZtSSYdps+OtGTt9/rqz731d77hxM
7Tg83HE6/ioAfMX/1/jSK2GhfYqw0YokVJNZHySQX4xOuhn+pGsmw/kgSU2KLC0bTEgnY8UvzheD
R3f+OFZmMpzP5SEzPoD46w4PluHqYxSVDfFTSeNbU/tS/hnB8keXOZ/sSp3ZEqyCd8W6hn/Vnlh1
eumM8oonV3gePxqtqw+2Be3whPG38gmjsLC6Tkxo8LU0siktax7wU85dHEOaPN2+/zy/EX6MEPLZ
6XTi21awwXl0FJ6NtiIJd1zVj6yqQMphD8EbXVhSm1/u20GmsPmBxB/CMxR+7OJ4tSnFil8glSd/
DEhiQkEBQAlljnVy7PLHu7cNws6bo7GqtK0G1xnww+T/sUV8GQS2HHoH7muPJhTnwukVuM5IxB55
sRN2O1RTcBmBN5Lk6WExbXzt2G1vjPQn0v4yT1ttGa4z4Pvf7X2ffWqgE4JJKxOgCNc5sTS+f1vX
5n74BkbJeTMrZpelu0dxo2JMPqTUwh6j74UanpMkx//vTvyBmqrGynVw4QKr8JdIw2US1t3qa4/i
2McSqAnfz8wELPiiaV9R54bh+jg8DKWjAFEq8EMr+FsrcMhY3/liXzfw4evj08WLq2AhqfmC70lD
E2r6wnQikhtb+KIN3cjgUWqHSU6hNvyhQUR746udv4VZw+leNqNySZUrEY3+/Nke2By6e+uxR4Bv
dwEf1xmJ+BPbOm8TL4qrX0zT4sedWABAOsKmwAejgJIOVZWtme4PKenD7b2fPzChTIzeewDgsM+e
VnnlrPJmV2wbbPkoSr14Iru5fQQ2VGAOamsNTkV1+NYuAosrECXZPW5rw4QBSGO/hYQB3zbqwgDU
Uw/nF5h0NvEwE88eRft+n+fcRrFpYov+dRC7cYJDEMRZ4PFDHyhSTchTbfjCOpeRKkIvU0mzQPA/
NCi8SIJ6ZVMSxAeLQFCBgKFo+FvxZ06WChD7INAIQ15LeCVBvbIpCeKDSSCofDDxh9hgpMiw4bWk
N3tejGDQ8UzoYjTZ4p9/smc3fGM8WLZmVhA2iPt7B7+5Hea6CeI7faWrZ1W0BR04GzzX/ZRu/mET
GviCArUkBAOrzNwlWIQhTZ4wEj3OkNcZ8sA6Ix2Nxbft7cafXoQxjgsQKDbshT+3Hf5Hhe7B8H1P
H70NdkI+4PjTMTL8MWBqUuRW/G9j/hQJgTnxL08c3R4RT/1wvoZEF0lHBNl1ONp8Dq9iG4/Gd+Av
QRL2mgGHczF8CTOV2or/ZZrQpX5BqgbJjqpIHaje4HU2uuC/W0vuwN/XotPIlTUXsHPvdsz2OMaj
MfyeJhfhcZrFr1fQ9DPGBcWMMpLib/A4q5TEDnzvilLPoEvMfPHrFLh9u63N7/Km04gtnAQ6HPQj
TkQO3LgvbtWmuB2LASIAE/43OBkmWChxLi6h/9OOQAb3hsJt8uDgR1Rr7of/wWRb+1d7bYt9to6I
eJNUijgci0vt4+nUjlF6EszzR2kotY9OJEdweSEVgAZf9raA05tK7Q4nxC8OUTBMhpE6HByOVke6
J5YWWrZbV05d5kv8/H877sdfmicdgy+ynFWb2T9p+YNHgYU75lFZ8Qt8LPwxQ/RpYjoPqPnT4Hc2
2m0D0cR+9XeU1RxTp9Y4zFq0YGf5Bu+Mw4RmS+4YF3c+BDv65eO3+PlHTjo8zd8qfhGWlf8fqvxf
UOr8x3qlpT7o8/kcDvUFvi3PvCA2vygPaUJUp0VxtSM+/M+rcMWARMRCbw+wIZFKboWdBswWcWcJ
ImhBZK1Q0OZZaujqzvFEp+n1Gw2hHayVkXhyawy+XaV/d4GMYb8oZvHrUj8rfjosdGUaf+d4HLdb
aCIgXwXVmfiFcbmMk4cFtw6pHcOwepLHQOgJ6/JEFBg/QoQXdhU3qT6R2IoPcKHQoRJdSK1Ghf/j
TCqxFf47JQP+ieRW/AadZlaPv3iMIrwY40/vGJFLW007L/5qrMnUftzNclw9KzQnVLoQXkEe1L9X
azwmNKpiiyc3F/6goh6lhrzETRLG+EFSHLKOD65M88cYV6FtK36BlA7ntzN+C8XbKHcK4N8ZTnSq
86QuejG1msbfGU10ZtJeU9SP38y8beGvIVTkpyn+clpCg5kTISg57Uji1MOfDtyIFiw1ZAcR4oBV
MOAoaQrmSwfNBAlSjWIaHz9lQ4dTZurnsjp5bpTpIu65YuBxqgdCFgrQ5a54yLp4mB2dfcMBkC1p
peAYPuDxy984+QDh71g2PdiM8Cceem1YOw0fUvzVlDMfgx/w/LHixykBkjPX3EU5a8hcNaEl96M9
/1j5c6rmjzYxs0+2q8G42lpBZrwkdEKsYTYkSFGqS4Kpmk6XhehyO5wuVteKHxCAArgRFEjvP9b1
9roKAAAgAElEQVR/3aCtnzYhsKvwcvLwj93xXPfCgP2N4+Gt6hvv7+TcmR3RyYs/26MVfzYmFv4c
AaIBJUlwxKz84WgQzdEzw41rvRMM34kuj4HTp3r8/FhUmpYaMoM1Aj4JQBDjSOawIFiwckcxoU4E
1IZiapOcUg06kmD6xeqayjObnLTiz8DO8E8mdtD7FKZ4krBU0QhTeQ46o4vBfwd8oXpQpImaYyYx
MPN4cJiWgkVEfl1TeW6U0cXEj2qFxMDMW/EjYnmKhX/O8SsRM81nGhJUg7RGmMpLi3rCwl9ClyEY
RKZ4EuAa7FLXVJ7Z5OQHDX8em0bTN5FEC8KFArWMG4Y3jfD84xy0pJgkhMmiKx4DBUMmpFlJZJvm
uiBGR5FHnluQYpLgvYXTPAbQoiYQ0qwksm1yXRCz4s+G6C05HEMQtvDPk28cTCkmCd5bOG3hDwjA
nzV+C88ZLmnlz4chf/gZzdBiV4NOMH91DgSgmV34aguXYDikUIrr4kiTzyZJQJhipFDRrHN5bofM
khRzpfoUJsWo1nyZ6Wp+8JPb4Q2uy+Phzqz4xanmkFj4W/lfUA7wccfHER9rfAzCUIVmduF2rPFL
+BSCIcfNwp/mMSt/TlL+5Bq44MopABedPGWzBzlx+HQA7+Fj1krDGkFzBNU6mygtVidm1vPw2Vih
RKFaFw9f4piY0slb8ZuglINt4S9AsfIHx/zbKFb+WPljzf/iokVXLqp188mH5fpFh5Y1SZjsauiW
CEwJ+FCoRkLrIkI2Nbb5boeUEETGoN6+lDI7JTweMxlpBAguj02tz4qfkDDgo8Fjeh65vIW/TKe3
xE0KcNiB5nhyGTNsubyZDLfD5dGd1mflPyFhwEeDx8p/FQkDPlb+8LQB2oDPRzN/ct6MpOnXQjle
AJYZXhI4ImBqgwK1JAwC0JSmgJBToUGeIoNaEvntSLMGMe7LTIaryDAkwXuJ5jat+AENCUh+rKCX
JLPFJEfCLgnZJQnpDggLfwBBAiIhkoTskoTsyklI2CWRLSZNAWHhDyBIQPJjBb0kmS0mORJ2Scgu
SUh3QFj4AwgSEAmRJGSXJGRXTkLCLolsMWkKCAt/AEECkg+r7D7kOA+Oxp4dFL/xBEtUuNjLhaqU
JyatA8xkpDAQxcpz3WLpQnwVIsP9FivPdYulC/FViAz3W6w81y2WLsRXITLcb7HyXLdYuhBfhchw
v8XKc91i6UJ8FSLD/RYrz3WLpQvxVYgM91usPNctli7EVyEy3G+x8ly3WLoQX4XIcL/FynPdYulC
fBUiw/0WK891i6UL8VWIDPdbrDzXLZbO5SuE/6OI9p9/MoP0AEVjZK8zoIeYsksSmpLxs1h5o34x
7UJ8FSLDfRYrz3WLpQvxVYgM91usPNctli7EVyEy3G+x8ly3WLoQX4XIcL/FynPdYulCfBUiw/0W
K891i6UL8VWIDPdbrDzXLZYuxFchMtxvsfJct1i6EF+FyHC/xcpz3WLpQnwVIsP9FivPdYulC/FV
iAz3W6w81y2WLsYXfNkVxOkP/JAqfAoi/4ZJZg1CWpquabhSTBJCtCBfzKhOnrZ0wODbsClVJMG8
5CClmCSs+C38IRn0+ZAjc4glxSRh5Y+VP1b+iOHwFtcaNqis+V8FQ04jkmAo5SClmCSEkA5P7dKf
Q11j6eRNxq8mKz/BJf2EF+yDUNEI3eMr8ZiK5lPQoD0TEJfPrgy6EAp1GWXIONXMEPoiF8IQuUaS
yfCnMtwM8G0kJnRRTBQyopqy4ueQEc2wtfCXaSMJK39oQgEcaDjjqOJZZOWPOtFY8w8BoaWHuFZR
2mDKWPkDIwWB0C5nGk40mID/obx+iWM2VLTUEHCw2UMnxNNFN9uYLSl02pkGX4Igl86B7iyo85o6
zVHWZgyoFI8TzhM2hSnO50pW/ISGhb+Kg5Zy0LTyRx1r/JLABw+jrfyx8sea/2m8YCaIiw58slWE
df0SqGjI0HjRararQcsrumxr3fiJU4yogeawwiUcDGNNMjl/SovtKAg5rKDwy79qRMYnCebMMM1l
zjeTseInWArBthAZfrIt/FVsMeURGMphK/8RCJMxbuUPgkNzo6iBZtOVmDmt+RMBUqFAsKBY8z/h
oNU4957K+aMdB70WKs4uHQ9NozSf0km32dcGnWU2ZTSa2DSeUkcL6lM31RoWml31U2dHaKj2GXwZ
U/qhaIRYqBjtMzum8XO/mouM0/cqfod9XZljNJHcFKb/6l0cidkxmuL2/sVPoZ66+Fvxw7njeWWN
X0gJtWgEziFiiCFWJnOLpoOfZjIcZ53N92H8zvM4Km3pLTR18+BPkfgxZD6380M4FfD/KMbPz5FG
066GaNFw0wYdDjmnZ9OKhguavB5NenRo+IEnO68fTCEjM4QcT3xm1krP0CUPHtsEfHH6159We+tZ
ldUubPd1D3z1T90bUUcroAuFam1Y3r6y9cbmkpee3bt4f1yTUxRPsPeKxuqxwUt+2TkyreHJ5eWZ
LqCS6dGJ6MuvdZ335rhh5lSbmvSdK1q/3Kz7Bk4imRwcGn3g6WM3DWlC9MnTN1Qxcmn9kRf2zXtT
/V9EVVEZvz+w/YL6+SGEMRqJ/O6po1d0s5WEZnhFU92jqyoFjOmfPfzGVWGtQ1HWtDZuWhrc+sye
JfsTyOX4Z6RyURn8ea/rmb+dudQxfMlDHZs8oRNXTHYd7Sj7i/zP1jVJGT8wNPy1vrf7SZG/0/jV
/MEsoiIJHpcVP0dDBUp8aLBlEilbkji588fC3wyvt+K/0/x3bf27mYtKmReY3KLRl1/vPu/1COMK
soj8dz1w+cz5rsS9/73nGjDjDzwzv+Tbz/RtMVrUZh4rf/j8DyhZ8092quTkGPI/S0b8d2uQuDx3
QQibvgPrpq/BdUayvXv4paPhwaRSFgp++dOt9/jBqnhJAmvHpotaV5bBVd9WBmdFnJh59ZPuPQfW
Gen2ztH2qK26tuqBS2rmgRKYFaoohoQqT1oeBwZT6hAPYqALhaG24xXaZYdtlYAQAE+Dkbj4S0QV
W1mpd+U5LVtn4KJGPQpJgAXyCDXpwvKCdKMJxeGorgzd+OmWW2AFkiseJRQ8ckk9HBkWaUcXf8mb
lzbBOmN0KLyrN+7x+f7+4ml3Qrh0XKgijsJmv3ERrjMGB8K7Oof2xdmxg4wd/ik+WvIhKQoRUMMf
xw0BBwERBBGC5PH7HHCwqhkAxQl4ZtvJebxoGI1mxa+PgetieHSMwiM0qRCR7beA+NEAhQGEmR0e
A5cnReyV+ZOFIdcF+yQpHaF7c79W/Fn5hnABhlSIQIQt/EUWYYJpGYgg5R2/OP+lR7XJLeGwlfm8
Kxc1n1hZbpwHEGEBuwTcHP843LjFo3tgnZF2bf+bpqXN3gapa+U/QkFI5sJTTguG81gM/vnO3YcV
f8pGfc12NTJjAkC3//pTTS0OJTF64p8f7rpP7XL9+ZLpqytdV55bdc2fBsDO2obKO5fXTxF369Ac
Vd/bsH93cRU0X3lh/4I34cfBvNuvmD6/svqbVb2f6YezKs8eiAga4RaXQ2CoRfBBFgTSCt7sJ5VR
bGIZPdpVgbfpom2z3bOi9YvNJQtml8/b17NTPatqJ4kII6ryKy/sW7BP23Vwerdf1jLf572k2fWt
PXFxiJpfm+OW+Q3/ekZQOzIxdWIwYEfIiPpfzq4/zaFEu48HAA2bcvuy6TdO93x2kf/6p8WuBfrE
+LGgz+i//f7I90SLV4/sabftJZtkXCiQFtVohLpAL+NdGKEmsIUjxD/NdoQ0PzQfmdlBJQ1//v/a
oHctfiDVYDSbOT4pSCFHwqpKUfELR3Q46FTYtOK38Ndlvpb2KpPn/6mcP3CW4yNrf9WxBYckDrCv
tzXetjBY3lz/571DF3ZqsxD2EAKiRuE84zf+H7vCixYpOPUqqThOROlOtJBdxFgjx8K7NuSt8Utw
mODwFvhrOJMNrZXr80OEf67DE0uN7KncE/xEDdwaJzY+2nmfehkD7fiFj3eP/G2D4nKuVdKbFPf/
t7p+Ctysd4+MVwfqQZzsOH1LQjYlGb4X1xlwHsb/3+vhBxf6z51Tpjw9unzKpN+dW9Gzv2PWi6Pq
gNFdTsCLPCcMegxd4+P+BHWhx2te6P/75oaygGeeYqtsrtu0pPR/d4yes7AG40kmDx4+/ulnhnZq
qi7QtSXVOBNjvzkWnT/TU1npVtLi+YgmpviCXz8j6FSSXaP2ethOwaPAhNJqCAabzUHcD3lq2wkR
Xfqml/q+ML2xenL5WiWMD5JI3ul787Km03zQdP3rFadd3X78jWDNUtfEMcU7t9KViIR/tG1i/ccD
z23Zf2F7CgJbP6tOPHgC+8pg74lb/tL574BiSeDApQ3KsaH+8tCiSjhl6cGh4X/7U8f3ouhG8fie
Ob9hSU0JdHR1h/FxF/LlwSj/smDq9+Z4d7x8cPGbsA5BvuB4nnr6wIXthAaNIujhw4kfL3TJIqEA
Y0ImO384Vkwc5TGdMrGpRokh2ZLIwA6CwCVbQDOjhcQgY0eiSF0mbsWv5RUDxcJfzWeTscOgyps/
atI3QJ5r+f+9HR2hSg88Vv7Y3JDSCfOMbV5VaOO5tXPFE9tEdPzRFzvWHoIJwrnpoulL7aNPDLov
memHeSARjT7+YvuFh+KK03fHIn/f3vaNihNuFBfhzVPg0X+cmT32V0yquPPjNXNDuD0cjYz/8cWj
n2nHWXH9jNoN80NTxL5rIp5ob+/9wtMDWxRlxbR6mGx3H0+2Nfs9SmLz4/subFceWjnl080+dJJM
7Np7fN2LwzvVYQssa/wCCFBYQhQydph43vzRhiZ40PJH5+s9xV8cqL4SD1Dw4OUBQZjpeZUlXsjX
3n58q4AGEtTwFx4M3L8r8PueTSif2Hpg6Ddb9lb8qaNDvZUWdjwOvNj1Dd+nedrZPQY7E2Ve3NYP
eL3lLsf0CvG8Aw9e5h/oUqFICC2qtR76TMKbIhnhtc1+fMYRS3Yq6YDTWebxXraopl6Jtw/F4RFJ
y/TJ/z0n84pGHHTp7AoLp5djGANDMKLIINSCiMZePDqw4aHdF76U9ZaDGgsE5joTr/rJ9gjQ8GdT
omP74BrvUMrU4wJR7IrjD7WKkkzDXcXkUEl5ZQDWGcByetLdNqff4Wrw4gJifVvzvedUVbtsXb1h
MFteU/H//m7a1yFgp6PC42yZXrWo0tE3EB1N2spDodsuroXVlaK4t186bSmsM6LRPb0T9bX+ctVZ
5mNHf8Ljci6aWzFP5bn+4bQyj0tpH4DTIiJXa7AmmxSzFrkBH7UJ5gRcWJvrIuBgWLsnY/hr6gY7
sol6JkWGB4R0LQlgSgEyAF1QoJZENl+a0uta8RNUulpCJEEjbGVTCmTjDBw6C5LIq/sRwh+xgjsw
ho9y0yuDMKmUVfrWAruq+qW1k2GdER2N7BmIOz3eNStmbJ8F85ttcsgF08VlM/2JSLQrknZ6PKtX
wMNc2BMOr3pod81zYDUVS9JJUeIx8bJdxpFNCVVu+mQDrDPIssfnvWzV9AdCyoopDfcurYJ1Rt9A
GKYXuMlsmV7/wAJ4o8RGk+0iXGdAcSpR+58vnfX3sM5Ixg92R0YdzrmzG59bXYGdOYpMD5kweXMg
M2wpc6z8yYMDwC3xyQG9YJ1U/HM7hSscFDUFJdEccENHFLfbDEHLzMCLx1VPdwhVWjdodmjZAWmN
sljvHJ6ATPeiqfQjR7puGXcP9sMSBpvMuxpDXJHDQHRmVWWV5X8+u0Rx2GJJZVJ12aJaTPWD+3Gh
jaMRVkCjJ656uGujkl43q+nBc4JTJ5cqr8PCH8vsmXWbQjG3Q4kpzjmNwZYy3LnZ3qFtadAXfSGQ
RHjZY/gQZG0JHT6w4I8Clhwb2IGdnt4odEEhGaTEZIEElkRk3sN7t14xZ5Fj9FLYGlVc26chu333
4akvjq8LKSPVDdhGdd+NC/1g8Geb9lzVj77uPLf1y9N91y7xf+9VmzhP8V9s2ncF7IR6yjqvmFLv
K5kHOyuttfPhnmJo4LLfdG2yKetOb3pwURDf1ciEo2xp790VL59bVv5P/u5rwjZlUsU8UOk9cY14
ziNEKQARCGpmF2Lm7OLCUoBjZRCgLuFWpAd2EyHxz8nPwl8fuXQtCYNfaObsyhbDgCg+3idosGDF
D0gwHFRUJbaS4OARM2dXthhwPpL4ExIAEs//8QRMqB54bwO2Jc6dBJNd196jDc/BLZBt3azJD54T
mr+ofv2bx2jSPbj78PQXYVTbN106e03ItaLZrbwZ2xmlR8bJtX/Yv/WK2Yscw/iMhqOuKPcsroEb
tr4DHTVP40vyt3y89ZszPZfOD064g9Dc9cLeebghqsybUr9jVcWkaljcjNFpx8n2vztHy93Dgeot
IRs0L/vvTpiIlLR357rpcxsm/bpy4DMDdN75OcWD1MYj9VINTiQBtCwGGck3EFKX++IyIKD5RVJc
pKCfCKihmPF1OcnsWPmfAVgAmGnqKGeeM4vvL9AthVTB0yRe+AIO0LIWpFoRn95GVM8IXSnFeY1O
fLtdvfBzJUkH3aBPJkhZ9OBWgfa6hs+/ei5ckjOl/XDnp7ePy/abu3o3iiA3Hhr50TlBLzsKT01o
TY0UBCL+5LOHrqKdC/IJPCJkCMCBQDAWET+lI9pIw1oHntEcE18cQUamSGUgQNMh1mI2fBsLXGKV
2PxKGHo2DilrqrCNxeOm0CpqKx5qgN2mFHy/BthlQRedhejx/iv6YVcG1oDjHVGl3pGGNc3KqfjO
+vZdPTi8FWXj691fmR+cDxQ0KQqg07FfHorOnelZPcurvDx+55xyWLi8tHcQFYyFAiZN8ERNOnxR
G+S5OO+iJDEkDwigvEn+kE+SkTULIRt/7lCjeUBMmZGapPjk4rzDip9OB8ctK/85YBrNAWXKjNQk
xScX5x0W/hx/QAZeVlNsNXhXFfk3XGdASW98s2t9W2ipz7NEnQ4Tj79K31VJbzkytuYMeGpLVuT4
tfOJCG2o+LvOwg3a+C9fUr+M960X25Uu176e8Y3RPX+GBzIJ5etNZVPKvWfAbZs6g6m2cbIFI0Ox
2+cH0GBMuWRu1eVwL5dMxeH9d49jZp1b6Rf3clb+wCgwFBV/A1ebJE/d+TPrgIDhlNnIew+PxuAC
6nVl9abtt8wOBSNj97dHd3IFTgtA4zG6MIssL3Oq+x6ELBcGWoO7BFYnsFqGtCSIkQ+2hLlYErcK
sB/u4E/csW0Yv1HihC+nJF4+Gt5IryxgJxXtJSkbLXFURejrO3z8noOxEgcMAXt0YmJz+/gWTQP9
CPsqIdyqHOBjMFqtefG5YRWB4/w+CI50qYvHL/h0zzEqZZLRV2C5RU2NubapDJ8EKa41ixpUD+Kj
rKZsrQ2PPg6bTIYY0koU90KTb3ZpXfC8BhZA+l0NcPS91wa+PrNhyoyKeX8duLjJpSQjv9pLQWkH
RWFA5EBkxW8IlYendulYxkPLdBrilx3oVNPiMmZ8qQiETsaKX0ADmBAy4jNTcWwzXAOGWpMs5Dwv
proW/gKat4c/ocrPEdhRN1bViVCJTOwAAbUkX+yNL222TRAHZpVxFf8dI+IGiAYyCGvxGCcitSsF
T5sVR+RJOZEmY986JNYH/sB3PzF5Lu7+6gt4JKfwRioQYB+fayvOyorPVeokceYn7yRGWlwEeqkL
mNb8Q8ho54vjhHRBGH4Axq8xbmyLjXk1IzPnfOdAFHYJymoq7/H0XYPpq73K5w3+6zkNcIFXHnrz
epmXWXYhzctr/GuVwU2ia211Ke77hUWeE4gGFcHccyKuNDjxMkkymHY2JejG/YyBsU3p9FqRpuMj
kZuOhHUyMn7KY16jo0y749jwt47E0CwV7RNbnFa79R8kkBGL7RxIzq+14aMmYjq90+A44zZ8kRQK
xY+xUQCZTyWV7CHbauQovalnLKoEPZETX/lD35jXDkpjSaURXk4NRzfhno7icmjzuIwB4ME3YBwt
lQ6F/zIYGed1eOj5oYbVobLvnqFMcSiDh0/8uzQCYpImgupM/CQBRyE6oNJIdoyFyVAiSfx5hOSU
cww0CeQUk0wuY8VPaHAcLPxlqvDskswPQP6I+41McHcuwEcbg70jsG35LWB7nA0yWsV+Gm5QJtXV
CMwqWvwBjVBvG3DkarMQGDGOX3sIJi6XZ4EjvSkhNG3uB84qn+gamb10ylyfEh0aeezA8J6+yOZY
8NG1dRgcSEkXghATkdK1u/2fdscmwfoCvdkm++37usWShVRkDQQvZAo40ibQPG/V+EU3VMb46dBY
ByN1dqz8FxBy7JGWTCKoftv409kw+lDwkoaXXpz9xaUd23CzPPTbTlgwuK6+uGEddpGM+8+r6yAn
o8d7r4f1BxSIhhdowt/EyKtwE+4JXjOZjNuvmY3D5+BR8XgvrSwvsc8lSao1O4fx9Uxl7sLJt5QI
O5gWzic+XiVWQxSAcEZrEdJFGRG2Gr8QwEOAImPL4OeC5xKkAlooosnIJloTfKiRQCms8U/s0zgw
fkGndxyH1ZbjfNg5FOrr51RWw6qodxQf36AdHpuwQzYFSRaEDLVtShjfaFF8pXXRifv6o/f1jytT
Jt22qvnrZ8nJRzMo3KFaOv3cMVzxnTUnRE0lGJgNZwiKzhdIph7aO4JbJgsr4Js1z74xrAZApphB
1Y4hfrQm9ooQEw0igwxgRGchgxpFAjqkzuInj1RDr2yiTc0FEtpZkPiDgOFPqkuCBDj+YMqKXwJC
+Ei4JKHiZuGfNX7fm/yBE6EonSz/v3564z8143X72VdGlHQyghuWga+cJp6owsmqrLwAvuunTOyQ
vwQATCh4HvFTDFUxt8v4BXuEXICYmhLJYyOg4LkE3zDFkbZ2Ru3n5tVcPbc0jlsViR/9tn3tjqGb
uuIr5pTj7ILv4ZEDYQ6qdPrP7WPwWVFVsmk4el/f+H0DsYuXNn9z1bSvTIFoyaqICmPT/wl11RCZ
JQGZrurIteafU2X+VE+m4UM8IqG0wVMrZmRx7q96vPOCK6fUhyoevDpw6/GxgZS9Gb7dgBtpiV+9
AD8jwQ5bzWulDJiom3hg18jKcwKrV7c+8+oJpalqKYyHyIkfHsW0XTOjadOyYLizo2zzkCFfN+3r
feWs4HyP75vr5l7dGxmI26bW+sTW3cQDz5zA746r6a25Rl8iYB4/MHWxCSHMYCEku5CtjTSuYuBD
UxbUVf595azrm2w/+9UbV0Vs/76jb8OZvurmKZ0X9L0w7oWvmcEo/MNW8d1X0KKoRK0+PxJhqLSK
FUSrOUiO/u5o4otNnhs/N+vcnQODZWWrmvE7sq/thmWBeA4KFrX4pZGNb/Z8Z6G/pa5+5FPe/+1K
n3dGBS5MYEqi4Yq2KQ54jWPg1kWBKcCIjv60G35gXsCIAiaFxS+M4PyEoloMSAMDm0iqBDShcGyx
rRWdrnY40GnGB3QQNGGTHOW3r/nBT4qKahGoFb8pzhb+PHOIfu/zB/y6Apv+bmYCE97m9TnprqHr
wNG18JKWTfnh9qGly0LzPzbzwKTeV2OeT8zGH/7pO9D/74ryD9nx86NQ8x92RsFFcNPl0/7wdPsV
PfTUFYZY6pt/PbHmwsq5i2YcqOwDy5+cjRPO46+Olq+CT+dVFzXUHBpvmVa1tA6/zeeCb6/RYIQG
zTM226bdvXsWBU6rqY1fXvro3rHJzVXzYas1GXlwL9xAWuOXJjGRUrqxRlMf4KgR+ec3ne4Hdf4U
Z1sckq4SGw+YiLRQ1dabIBMfbvjV4Zd6IVGcU+oC8xtwnQE/TP793+y5Sn15SGcIntWNape3jbuP
fHcnvAjtXnpm7dJKJ/x6xPf/2AlPQDDlBNpxeLqoXkK0awnqji/4/eFXBjA162v8cxtwnQG/9v2z
Px7EhzU2ZSQJl1AlIR4Kqikuw1YJDGksgWsaYT8NOzP47gIUUY9pX/cSLFZhMNqwIUJ0jpA8DnzR
iyCC8TT8SinaT4yu+uPxvqRS31QNXzODt6eeff7gFYPCFAiisKhhoUUxCIZK4/ES7MiNQ8zwGyGP
7f3ZYbg5cC2aV7u6Gb7Jnnhl28Fl8NMXsHyTB8KNAJ2ITP+fjoPRdFlN+WVnVJTHQTBT4JFVAg5B
jX/0+V6Mo31fP35XGb2LDiLUeMRhkgEWPzKoCQTKixoJ7SgkkW0Hpd+q6GxqLkCJxwAy0FTtW/Fr
yCN07ESo+DAM3wp77EcjElutCRwLf0BAgoAYaeCoOGtn4V3Jf7QOvxDqLve5ymGdAT9MPjq++fkD
DU+PUOZv2t/xlZdOwPuhLdMnXTY7CF+qP3jg2Kqn8NsomRmGTiWagiew2thHw/Av9vh+fG+0rMx3
fiu8Lp9Jm52dnV98vl9YrrlsdgAekb+07eCF3RPrN3fB/FZdV/G5jzUsrXPvOTAEb4V5aoK3qFvN
wgVYRFNjs359ZNdo0lkWWLOwdj5O+5F7/3gElkHoGv5AhmoUtsavljl0Ft6V/AFTaE1LUUL+fcAf
Q8gutk/9bt8fBsTXN8xWTE7HupAL3jweC8c2RsVVPIcZkTqGFZnHtd4PPziavA9fOoLsyiWTbQo4
Tte6kAM9RmMbw8JjIbqFyOR0V2Bspvbt66rcpUpqf39sy7ti3+laH7TDLuXWwQnTd28Njmy2tUHX
JJcNY4Bso1CNMo4nLp+zsix+70N7dO/fGMRyNk2PnUkXIsPEdWQhuoXI6IyyRiG6hcgwkzqyEN1C
ZHRGWaMQ3UJkmEkdWYhuITI6o6xRiG4hMsykjixEtxAZnVHWKES3EBlmUkcWopuRsa+rdJXa0vv7
JkwnHJ11/dzrsK912Q6PJ4xzC9q3rasuwakMLJM7tFPc/LbC52r1OsbGYepmN1hgJhM/LTtotWEI
1KRZiG4hMibmC4rNsg8IQDG9vqjX909Vem4+zdNSH/T5fA4HPgeB8uTTL7ClBvHy1+8E7l7DjSoA
ACAASURBVPyW35vej2j8jnvOrjmjOrCoriTR2+V6pP+9ATuHl48o/jmQeH9YFv7vD+6aVwt/DYn3
59PC/+Tj/qlK782zciw1tI2wAiMw7M9Qs0DdD4LYRzR+16p51S2If+z+Z96/dQb4/4ji/0FIfRGD
hf/7eyos/C383wkCp3L+mCw1xNM0fAQMBR+wiRpoM74QzFEVIl+ITA7TeVlmNs34ZsYKkS9Exsy+
Gd/Mphn/LexEv/OHIx+vsL9yaOi+7J9PK9ammS/ON7Npxue6nC5EvhAZbrMQ2symGd/MZiHyhciY
2Tfjm9k04xdrh8sXa5PrmtFmNs34xdrh8sXa5LpmtJlNM36xdrh8sTa5rhltZtOMX6wdLl+sTa5r
RpvZNOMXa4fLF2uT65rRZjbN+MXa4fLF2uS6RdBpk6WGeCiDiwwqBsLQ1KTUzzyhS0WuQkzZJYk8
drh6TtrMphmfG8njV8bG5c1s5rHD1XPSZjbN+NxILr8be0Y2qj/lwUUFbWYzl50sZROGmU0zPjeT
xy+pc2GgzWzmsWOwkN00s2nG5xby+LXi50Dloc1wNuNzUxb+hEYeHDhcOWkznM343Egev6TOhYE2
s5nHjsFCdtPMphmfW8jj14qfA1UkbbLU4FY49JwPuFMXMLkM50NXztNjJl8I3ywGzuc0t8n5PE4u
w/kgb8UPIHB8zDDkfE4XostlLPwBDSgcB44Px5bLcD6nC9HlMgab0MwuZvKF8Lk1gy/eJWluUzKB
4LpchvNJjGsRbSZfCJ9bM/jiXZLmNiUTCK7LZTifxLgW0WbyhfC5NYMv3iVpblMygeC6XIbzSYxr
EW0mXwifWzP44l2S5jYlEwiuy2U4n8S4FtFm8oXwuTWDL94laW5TMoHgulyG80mMaxFtJl8In1sz
+OJdWTRbanA3XC6POeiiQoShCV3cZh47mhmED0q2Hc7nNqUiEGb8PH4NjgxNg808dmQYZCHbDueb
xWnGz+PX4MjQtOI3AEJNM5zN+KBFXfIsSyKnfeiVfG4zjx2DQaluIKjJbUpFIMz4efzmtG/Fb4BF
AmLhz/NNwiKJbNx4TkIvNQ1GeJMsZNvhfG6T65rx8/g1ODI0wTi3mceODIMsZNvhfG5TKhp8cX4e
vwZHhqbBZh470h1ZyLbD+cXGrxkXSw1QhsJDebvmNLPaZx6b5BQEiSg8BqkiicJ1QZJC0gJ8i08r
fsLWAJNkEkF1HqykOkha+BMabxtDUH/buhb+BugkmMQvJIeliiQK17Xwt/CXaSOJD1/+wKFlFbHU
gAEGxTAMDDmRH44Ch2iWe2Tk0ZUxcJmcRoBpxZ/zPJrBJfkcWzMMuYxUNBBmunQSqeZ2uLwZ3+Ai
ZzOPLjkFLS6T0wgweTzUJEkyQjW3w+XN+Ga+OD+PLjkFYS7DdTnN4wG+1CWCam6Hy5vxuX0zOo+u
jIHLmNnh8VjxS+jM4JJ8jq0ZhlxGKhoIM12KhGpuh8ub8Q0ucjbz6JJT0OIyOY0Ak8dDTZIkI1Rz
O1zejG/mi/Pz6JJTEOYyXJfTPB7gS10iqOZ2uLwZn9s3o/Poyhi4jJkdHk8uGWdLmWspGDIUM9Nv
ZU6Y4ULMECONaWHw/s6b3Be3xkPjfB3NhZghRlrx6wDLbnCseC+HlvN1NBdihhhp4a8DLLvBseK9
HFrO19FciBlipIW/DrDsBseK93JoOV9HcyFmiJEW/jrAshscK97LoeV8Hc2FmCFGWvjrANM3Wvzq
f5uhZ+P/7ArIZhX8/m7OX3MjJqCuL7rTIP5fHPgvS7Cw04Yc+OVUwdfJa4s+EDfjczvCrlZxBY0H
n1b8Fv4s9XR5yNJEn3Csw8ofK3+s/KFfcWDDQrsoiDmc8/k0DJmDTZJhICLHmv85akBz4FjXqT7/
sEMhEg4IlhqUE4ZOYmZ3sdThGjyN1HwCSSgcSqZLnVSDDCEL4jqIGV8NMjsecoGe9MWK38Lfyp/s
8cLGIB8w1vilGcaaf9SssOZPa/58J/Mnn1xUWuxq4ADTrwrMlgg6PjdnmMLoPHEBciBrg7xBUjQh
Kkj4HLExYW4GheXCiTdMhUwMARtUsgsfftxmtqTgWPHT9K2eFYKUnxeOmwFPC3+R+YiWgKIQ2HQy
vMGx5XwL/5xppsFijV9r/Gq5ID5h7EChmo8pwc6uPrr5k3tY0WuhAj6EhhYygCfsdIlaBZeQhQaH
mE1bOrYwAqawsA5GqmsIEhFyaqWT4Xa0U2ywiV5E2OjKil+gyH/n38JfzUMrf7LGoxiEKi6m4451
MNIav2JmA/Cs+UfklS43+LzNOhhp5c+HOX/gROcqYqmBFySac8RGAtC6tODLDupDcRWsHLrCCFz4
oeBI1GzSXEc1daGEvuhkSFHY0cXDbJL3HDGQa2Fct2wCjjCIPUSIGv1qcVLAVvwqIAIfqAAiAgwJ
DStTDLm8lT+YbQigrDkh2Gqlk7HyX6BijV+eFURb+aPiQFOSqJGjzUu6+cqaf2gcsfqk5o9MUeFQ
Vk68WND5Agk6Q7IzP6E7nQXomsnzSzt6pGi0axXFzWtuh0doxU8ocUw4zXHjWFn4E0ocE46bGW2G
Z7HyFv4W/oXknlm+Wflj5c+pkD/0AEWbHSFiedqAoCZPcXUxAizo5RtlmjB2MAX+uhmHg4mot8vS
NVoQpRAZbhOUpBEiqOZ2eGxW/IAMgUYQiVam4rgZcJZCBj4BTjZlze1Y+GfnpAFDiS3HzUzGwCfj
EnlqcjsW/tmYGDC08LfyR70mwaVMJAfW4uJCQwloPqas/BHwqBDhR+4ilhoAHBaOH3FEbbO3+hyl
NttYLLE/RnxhG1fTYrUBPMNlW2rz08DlQUB1isqaa/hkNoEPzczyQRplcfJUMI2fL4kIFSt+C3+R
f1b+4BCzxq82z1jzD5uX1QlXN7db86cYLwCN9mldv4xfbM4go2YQfbBdDZh28aJPySR6HSUbzpq0
vM7j0VTCI6O/eOn4xrBoYwqKSUpx3Hp+y7KSkav/cHw/9MjU9AcfXTXp6GuHrzkcVw3IIKQMdKAR
1x2fmLbQq0qJj3QikTjUNXj7K0NoUzcFiCbJYsDiXKOMFr/Xf/ts94+2n+gkGVqv0JTKlzWZ+PX2
jbGJw1RN0Qc7RvRLTa0rc4w8NlxCTZ9c99OFZdu2HfxqR0KVzhm/Zkn9/MDEr6Qdt69uWWIfvfrR
LjwpUIqK3132yMX1zuPHL9o6CqqLm6r+pnTspr3jaIef35OGv1i5orcMUVT8qMkU3vP8yYStJrMu
nEz+Y5ysfIDyRxsbVvxwfoz5Q3Ng+pmth75xPIG9UNJKa1Pd/QsCO149dN2ReGYCOZZUh4yQUU2h
gphziGCpqgpL2CWhk9HmT1KXtZU/WtriVE+loDlKnAtxGj/S+GuY2cXkCS/OiBdqqEZ0oOn9+Sen
rMZ1Rqqjb3Tb8bGhlOIPlK0/v/lqL0AuVLC2b/jY1GU+RUnaSjWj+Okve2jlJL/KEfKZaVrbrgB3
mMeitoNoOjweHxJ/4YTidLpmNNX8+GNBIaOpgBEchKKW55vs4LCBsJ13rapfMtlTRUcBxrnfTJO5
xhiErhot/xBdqKW3gyoiJCQ0UygDhWrNIAhIYQfGVOrMH7+IF4x8AONXbKVwmhxwEHnwzxO/HRa2
TjscWFpxB25ZUHlWlRvBQXw0uJDiRUIKhFDEWksGVbdg/En3LfInT/wyAAhGc2rFL6EAAgvV2glV
8dFOGZwCC3+EKEf+uHAOtC07u245wkgFJCHrFPH7izaFJhCoccgUP/9Y+Y/I0yjOgb+GOf8EeShQ
S0Vr/hEIwCjOff2lhOUYqrR4LZRoTF9tglBsNyxraLYricjQhr/0boUunCCc314+9byQ628XlN//
3CBwWquC3zlrUmOJamtMtaOsPa3+n2eVqXshZFYVkR9gDQrVdBYVJRH+wubjnepJVVprq368pMJT
XXW1d+j+qHauQYmCkWYNRDoVT6JQv+SDE81DJmHQuRireFx6m6Qo1SWBcrJkxy/QU/OYH5fgixgO
tHcta9f7AnvSvplfoauDSnX1XscPMajbUxgSBZFFZPNl/PGRi/5nWCQSLExTsLGTSCTVJmjR6ZCA
ZNuR2CMBRmUNkZAP4lATaMaXMSCb+aIm1JLI9qvT5a7eB/zVOCVWMmxJWPETAtk4IHayfBDzRx1c
9tIbFwef2josY5XEgSOdy47wyIlmea4OhCw+MDLDwsp/geh7Pv+rkxZk5od7/EKm5SriAUp2hzuw
sgLW2MlfP9uzlTRx6MZv3tq3aPUkxeVsVZT9aedNH5/UqChDfeFopb8Wb3ZF8Qavn1XmVFLdEVut
TyQ9IAslna6rq753Yai3vevzOyMkq9VqdFVKWjz1wOb+7hOvjlcs8SpuoRsIBr+/sHp2AN0kJqKP
7+i6rRPHZkNDzX+2eff0JU+f7PMoyaNhpQmXPv4HPjXt+Zfbb+4WO43CAlSK23v7ktqzKtxw2OET
I69MuM8OJX/8l2MTrQ1fbS1R5VHM//NVdcqxrit3jeGVqbTsrnOq28rw1gJcP/pK5w+66QmI8/qz
6j9R6/HDRkUq1d03dMcLfVvRjSMnv66++v6F/pdeOnLzidKfr6pVeoYHAsGFITii9NDI6E+ePb6Z
XoUxCXITLqHElVJ8QmBrZ0y6cnqwqgQnkv6+oR/9tfcpYWH1jEnrZwarcPskPXRi+Cdbe9Ey7D8t
nbLYOb59xHVukxcQiEbCP362Z2rb5EvrELLw0Mj3nzn+VBIgrf7PttJXjk3Maw6EYLmZiL28u/um
g+MIheZafMJhNlw82YtrylRy9+GeG3eOjii268+ZenHIcehQ5zV78OHI4mm1G2b6EyMDn/vrxF3n
1zs7j1+xWwF4ccerrv7R5cNvKKVtJYn/evLow+qbQM5bVzSd7Yp+67GurWbTgXDPKi0wnFChGJrA
EBxj/MxAHtJM14zPTVnxExqFYMVx47SZrhmf656a+Pvram+tDX8D5i6aOeGIkEjXNdSoE0h3CnY6
NiyuXz7J44F5OjP6IM9zjcpCsOK4cdpM14zPdU9N/DNHYMVPWBRyrjOo5aZwz04t0lw6HQi64fqR
OHHibvEkXZNQlPGhi/5n70Vb+vYjK7H96Mgjfz205rmuY+qCXAjGJl4+Pnjbn/Z/fic+kscCloVx
X0lJyGmfFhDbgdSlq9P9vOnwNMu3N4IVv1lZC+uMaGR831DcWeJZffa0u6ainVKH01/iWYjrDCiO
VBIGIZZEXF5viAG1665VTUtgnTExse9EzF8RWAaPh7yeerfSUOH1OF11OGqpOKpL7HV+2PJJK97g
I5+oh3VGNBIFLXC9ZknL7Q24RFu7oPFSvNDG9/VEhlL22kkVt51bkYfvszv9dvDiUByO8hJHc1PF
wpC9f2ginLKFAoENS6sDoJw2DZIik/Xi05q+NicE64zuE5HuCVtVdfktKyc1QFRnTN0AfKfS3Qd8
JVQR2nDRlMtdgIatrswVCgXOa/JGIxNDCcXj839tdQusM4ZGIAbFHwpsWBQE+wLSkmUtgVB8YkdP
VHG6l8xrIrSld4D62+e14OGn4of7xsN2x+yW+l+dE1LSqd8cjHhKHLNn1X8JTp87uGFeIFRi331g
eMThqHbbq/EZDEyOdHbSiVSyY8Lu8XovnqptjgUD54RcnmR8N4ixnEQtaiJ1EsrJ8HUybJod+snw
dTJsWvGbIQD88aH73sTbsGWL6pbDB+GvEZkJBF6Pu2CaeLoNoy8aFaPv7jkwBZqMSrDwluVknOuT
YdPsQE6Gr5Nh8yMSf9Zhsl0NWkGLepLPhXe98QTmutnKzqbcva1LLLc1I3RiEmM3vYjPUlpdYjND
ukynD3T1/HDcNTQsnrSQZehFQgjZPV+eUzUGz/LhOuQpWTDZHwL2+MgjY/Zvn1MNw6j78LHLXw2D
x7aptXedGWxrm7T4yLEBoQoPer7yWM+Y39UTTn3noukL7SNf2NzdSfFo8bdNrWkrURIjg198vAeW
Sq1Tau9dEILQ4V56AhcoYluGVKgWN8dfWlADYRzed/TK18fAdWBS9W/OqVgyt7LhWP85lbjh8vjj
h24bh71070OXNDV6S1rTjlx8d2taNYrxJtICsvhvnzx85zC8uOB/+OKG2lJ3M3Q1a0E+0bs/nW5t
qoV9IFjyqDf8YIMORym9bhZcyVNPPHfo5j7YuXHccfH0hd7gGv/o+c1wzU488vTBHwyAsP2Gj09b
U13yd3N9D2+Dp1BY8FjeGFfsvt+tnVylKDt2Hr7uYEzxlz92fo2n0teWHlIfhI0PX7e5e0c63dAw
6cFF5W2zK1sP95EFOGWBusrzAjaA/YuPIZiK4rnnoimzJ1XfEBr6QU/vf7T7rp3i/szShjbFB+h1
H+7AWzRES5SJ0Ssfsz26tl7pOr7mpVGlIn3JpMrmqcGGvT2wp3V5SxDA2X1waEQerMjJTCqCDe2c
ojkploePclrhuhoPP8nLyfNVSJw8Ni5viJO6ONOKn6DLxkRixfE0w9mMz81yGQNfnoW340vYcjq2
vHls7tSZS7y+GxcFnnpphO3QafdOOCRr8PW4ifCNj3bi0+1Q5ZMrqxunV8wbSGRGJcbgVUdlcPAH
Q1qsJyt+8TxRc6J+cl9vB5O3ssndgS8oVJ8MXyfD5ocyfjoF/NAEra0SoMGhFH3wGrQ4c+LyRimP
VqgpJAxGjU0hw6tYfFO3uGhySUnb3UtmVHLxRCR857O9nTZnFd7xjv/ktQhl0o4jfS+eFlzi9Zzp
VR4XCvv2DcBFUQnH4aKLex02e1U63alaVuNfWI8bH0/v7N0v+PuP9r88OwQPaLDQWgcJlq/Idc0O
iLtwh+dLMzxumxJL2vDZibd0hTvRNZZSfPbVF7TO7Bt95djId/64d38CfeXgw7MP+AYKehJFeIn2
DeI6A0osemxCqbWn4Rq/TA2yD9YZoLK/o//lORCkgB0kUVEcjtddDguKEwO4zkB+8ofPH1voTrzs
DX4W1oh9Az84oQr/YPvAytWTqqr9DbB0RNHEM/vAj01JRo9MKFWu8H/BOgNKOLw3UdOWVsbAhQhq
955+hNRm6+w68cZEeVtJ6SJ8UiOKzba6UbzyG1dWtZRf5ABY0nE49hL79CqXMhR7+JVji2umLfT5
/3/2vgQwruJI+43mljSjGd33acm3DDZgDLGNbRJMAJkESAI4C84CYXezHMm/sPD/Ibvs/iFklz+B
zR8IyQbnjwkEQ4KdwyYcJuaywQZbPpEsS7LuWxodM9LMaP6qrvd6ao4nRjFJwEwjeqqrq6q/rq7u
16/fm/ECaM8zdOcBaFFbKMEANGFFr5qMwreDwwcms85Jc9Y5eh8ds36mBLYkvudb/KKz1AtqVScX
zlSFeQxjR4SvYvVIJYqvq0tGBH5UZDalHSJkkVuOy4wVIDFdDFxBxye6ukn8kd6LKvGx0/VhpE7c
MdXVTdj/0IhBSTUod7/e+/tP56YXFvx7jue76iltBICSNLwvani/dw+qGJSRwXvfmrSNTc6bX4py
4Vk5rc1KizIiZj9WJ+MnvI6RP2ZaauKOtaomPj468RMXalzmnxU/TIR4SWw1qA5XUZgVKNUzDgca
is0sbvSJRXlI2VDhdngntndPesLmhGnMNEIsyOGLi2qfLf3YEN+xCsVp71N7Bwbg6mNIsRiV/pGJ
nSP0poWo9U7i1RcSKgb2D/hXFKdMhduAXZGKn6bUhOiIwEiUYXIaiEA7fFOX7MADIDSCakKMMnjW
AwTNb6CnyVpFVW4FE4KrpMNkeHh/5+LVRTV2Y0WeC/6uWqY0N3fe8J7n4f1di1cXxvLDBgSAQGA6
YnuHQEKT2DKAVAcCXpehnkK3UV36bTIAZxQmnzh2Ar5B6Rge6zAoRfn4BATf9VX7CMbwBUz4Pk+2
GnOBDvAD2QF+MDShSorXafG9EWp6+p0ecbHHWv+B4cCSPIPDqDkKmOIJiMnluhaPnsIJ4wmR+h86
OvLUMgRzsmkAzipU/EiIJmBfIiiB07+91XtOjX1NmeXRroyaFGWsZ2inikpIUUYBQ71AkDx+NLHT
kRH+JzejOeFvYZcokeu2C53SVIjQXKUhg1rmdl07pyGTxE8D9XH1vxYxEBtjg480OO6tsa9aXlh/
kF7REvFDwQQ3LRl4PxWAs1gQFmlPF/4CwRdmmJWapG4cJuPn4x0/H5n1h5ZoikuWi9cRqI4tf55h
H1zJ0jNdf2se+G/17F4oWTP+4ew8mxJQfndiy6TomzZBRLUYKxowyImQjVGsUx677IJYMPBS9zjd
zUslnBhkyGqC0368aKEFwxwnXNSCFqiSAJCtFYFGvqxDe9YUKBqL4W6cXkAJGWvdMGPxQkwJjkSw
LWjQboYDEJ9oF+e0Mr399ZYXpwx0AmKzGOELwIcm4Go38fVXGh0WW12xY1mRo8ZpqqjI/7v3PY96
xxnfWeM0Cv7oi9QMeQCu/oAnwg+IX9ztC5D4GAMBayDFHgiwgTrkVsAAZy5AUTI4HWlfq7Q2j+Hu
0Af7FfQbCRvw8j/lV7+S4/c3iaMXdZEiA9JvqEMppQKeY3jpxTTTQnzQ5J8iVwmnOgTQ7qaO/3ly
Kkt8Bw/U8uwpLQO0/bP+ay3uMyDVLCm8qPnUq0AJRWRBoxI4lpVXG0eGa+z5RVn/w4E+3ts4yvGr
UMlvlEf4TXOjMBXOyAPMD7OxQ1glYs0qwCb/AwMqsUhVRIleiUztIAqL3QPKC9Ek/oT8QG5Vnat5
nxwu4v8M9L/WSxGxO490rimpWmF3fO0cjU9+w46HpsStENwKqNEFp4zl7qXmoA/eA4PnlTgr/Vl0
n6gY8uwGnJWzi8NPoP+hy8n5qwUbfNLKSTnEXuLxIwOVGQNSnGBDHdoSqyHk8Dfl+U0PXFjM16/K
XxJWMH3rQthnwPn8IO4zIEUtBWQnnGuaZBNKBkOBxShefhSaJIl2NENEhC0IYKFpeFKhpKTfVAFb
C7ClwLuOFzkR5TG43ssEDFAU9cBjpxqqxJE+3BytXpRTBEohOADIugCed4q0twPfY3DCa6Gi6Q0V
uJFBIUNoBK+vKWVpysHhyT0jk3smrLd9qvTeTxVcaLT+ZEPNby8rqR6dePRYz00vnXiqD1DCXxS/
UfBFk2hTJOoFkLK/QAv8R/o1kKIjHCRqUnchDwQBsS0n8wv0AkQotOncovVVOecGJuCZbHqe+wuw
jxHe2DA3AzZXvjEf7tJkonahqBqkD1lEuaWV6eQNJcO5CB5g+X27/ZpzDYbdnegxl9vSODq5Z9i3
Z3hy7dLSb6wovanABB35uwuLa8xwONG/E6IoJfXelZFHH9CaaDAQ1NqdHN4NP9sCz1AKzMrk6PO9
4nZN4KdeqMOqtR/2G3cgdkcYhDzqj+YJ5OT5WP+DvPA/5tSKbAudoSXCC7kkqEa3XQEp1iaXBwtU
lAQUo/6S+FU/i48z1f8YACIYcPT98BgFTyripTe68G5pbgX95hCopN5ydu76Ra7ODuSLWQlTkmZl
iZiVZoyoZPzLaSsJci84B1LUpEOPCWZy/s5u/Ym7dMJZu0yR3n90T/eaDcX5Ttd/fT69rc83OG0o
y0mDrz7CVe7XB+BFALo0auuyKEb8hBdKaIksG5Q5JYXwc5ljPV2ffQN+XwFGUQhwAhiyqGnD6cVP
joysOCdjydkVP8scOOS3rp2DP9rR3zr4KrzdKcVU/Cn4Szhmx48/U/rCvo6HB7TjR0XZ09B7dG7F
Alfmzy+zN3hSFuSoX3mAi/VEEMUq5pf9LMPjMduXUBXwQsHvHhxadYF7ydmVT+YPvj2csrraBYcr
Y52Dz0xPlg6HajLt911aekHTmDnLsToHGg4MBCePc34m8acGwqcnInwlbEHg2YnAv+f93qM1AuRn
o0FGaEyN/ardf0ux5WvrK2obR8zZrhUueJ12/JnW4bNLc6/NsX7tisra94eVzIxVedDN6Vcb8XVa
bAXcSx420O8ChYtkHx4V43kK7lfyt6+07R4yrKrJAG83vD8AB05oAVIo1Njc37AkvSYz55VL7C81
ewuK3UsgOKYnnmsNwO8bXpsHceX90Z7+bUHvWZ8vyc/J/6+KiX/sIGWR4xdxlfT8/GcuSv3pW907
J5VtTaN14oFLd9vQQSmojqkoa7CxAHwqAq3HF0pqJpcSKlORCwDN25LFKBleTKhdoUCW9eT1+Lyt
JH7uDaIT8tvHyv9RfRxVH6OobOgvJXha2jHYMJ1R48r+/VrzKx3Bs+dkwqI03D70dPPUxfFnpXgO
LMNeEppJ/EzGP3lAzyd68abHj7AjTEu3SyJCRhQkBklwGU4n1C6zqSevx+dtEWAJWxIRMlpbcWvV
Uw1oDP4gUS5IJTj2hZ1t+wYhRk0lOelL8nCfAT9M/oMXmx6lL7GSLyAnIjhNlyhpamJaHPORNcg1
3wX8gq8VJV+hXYHkS0X4jY1TXffVD8PVsqIsu26OA263m1u7btwPDFVIbQuLU6+1IpD0tNTVpXCJ
1DoFVYbJW39zcvcgfFfWDvuM/sFxfCnbP/neBEzdnqc64TghpaLQBfuM7r4JuGcPwL9erSienp67
9g3BLXdJQeZV8/FLpP09/ffAD+yElP98s/2gJ2Cyp65flLuuwG6antr55qlnJiP5hRpfew7lx+ep
Idh4wO9XMV8hUlHUAQm3K9RZrctb3m55DjCbrKvm567IsQS8Ez97tX2Pojz6+sntwE+xAB/3GYGp
l/e2fLsX3npR8HAIGxdthcTvcREHGMScnmbnRCFXjquuJgO+wArvoNzUgMcYaEFNvpv+0H50fNqU
lr5+Uc4Sl0kAaHtVsd29FB+d7NvXIX4IZPx/7scfI1qyJP8ig/jZLrIwMXHIE1JSUvIznRXipLex
dagBqwK7Tog4wvESLWn9lbDDhKgPF7V+ETuhXDYhiVg1WSWJmduVYpKYWV7ClkQsJquPOQAAIABJ
REFUBj2ObEISsZKyShIz45FikphZXsKWRCwGPY5sQhKxkrJKEjPjkWKSmFlewpZELAY9jmxCErGS
skoSM+CBNVOKGZSdhzveGkdYfjguJXhA41ngJM2+dFdG3cJM+BFFWJS++Ta8Pqc3K2NhCQ5rC8tU
jJLVk5HukgQpzlZeqksiCsAMRb22uIqejGxOEkn84AHyBnfgDLSeb+OpGO54oWn/mHYZjCcBPwKx
xGGCR+jeiamDU7MCEtfc6TANS1wWuxJqG57id8hxLBqN1UalZyrI3l1VinKzv3d26q69px7FLQYk
68+urKgIjv7jbzrU22iL6fxUo3dq6iC73pIozEJqemBiSvs359QaZ6plgcXgDQYPjvKDC0WPrxmM
//nBIKP0CHNM64oeP0o9XrG6tOi/4d9q2dv49W7D+Y6UttGpDtoFxhMuSrWUQPenAgcn9IXiKQKv
CH5KLRjsoMcoqRnb1xe4PIOXv9TLR01HNclOeiDpAaXIYSkxGsSiFLEyn86sTLo16YHT8cCydMvf
lJqrCjPS0tKMRvWNoZdffYM9QOHmIW5hw0LRC5exIXg9kFd/qDRvixrVbSsEL0wgKolNTz4QbIQL
H+GXMjZrflrqtSvL0g72H54yfWZRHvzyOnw/tln2ZiqwR331UbIkIZqWJUZ4xqf2wH14VFtwHDIh
+ExSJWfG/4EgowzqYdbjR6lDMRaPkEmFbwEFp/ao2zKmFinfMT7VoR5n6cqoTbB6IjvI26lp35rr
qMyH4xPlYMPgrPcZkXj02go3noh8IjJhi6dHzbatROQTkTk91GHt2baViHwiMmEEp0fNtq1E5BOR
OT3UpN0BtwHx2uqYiDcrSSeefDSWRGSidf7U8mzbSkQ+EZk/FW+03mzbSkQ+EZloHH9qebZtzVZe
w6Wz1aCLPeUgKolEmklERmseP/Xa4jKcTkQ+nkzHqe7tJba6PHvdOSV1ZNA79u1dMffQf1X8HwAy
EWyJyMzsT+0bJVwqTMfzbbiWKD2ZeNiKsl3rKhyo5xn8zin4+m4CW0nenl5bXIbTicjrySSCLRGZ
2eKZrXwSP4wCJPADDQd3YBSt56soMVlMRF5PJpHYSERGggFCry0uw+lE5PVkEsGWiMxs8cxWPokf
RgES+IGGgzswitbzVZSYLM5WXlNkWw0eIlo1fnK4vBkuz2W4Lqe5POdzXS7D+VxeT4bzuXzYTvA/
32h6ymFbk221wj8aMuLbNqj9MEdYhmtG0h9sXxtXkISkZ5Pb4TIqP/ifrzOQHg0kSJJNmevZEYJx
Mi7Pq2MwNLZ2/+NgSv+IcA61y+W5nRhdjOyoxGXIGuWanY7Wzm8HHUXGwNZTEzMdaWjyUeYj/Mxl
eLtcR0+G87k8txMPP8pyGa7L6UTscxk9m3oynM/b5XaS+MFLUYn7h/uQ87mKngznc3luJ+n/pP95
nPDY4PwzKX60vrCtBp8GWjV+chdw13B5PRlQJzFukJikQvy4MlyF2wc+FGMTx8NruS68vO3xbRnF
NxzVRFqRMhE7wbjYgEkqZCWujNYCfnL7VOS1RJMRkXeM+baMaSC5Lm+XyUfY5zJgmcSimptZJhg4
CM9NuCLHAKagGJtInmuRDNfl7YblQzvb4Z9p08xyGbBAYlHNJSLDVTgG4H/I+CPHNxFsicgk8ZMH
+NhxvwENiXI9GSkgZMMZt6MnE5aOHF/gJ+NHOi3pf+kKHjBRNI9PqPpExY/mCrHVoJ7z6QffV6Gv
0oKc/E4t+YjENP3wZ1z3JWSHjYNeWxxbuMnIJYDLJNQuN6Qz/AnZSeIXnkz6PzKgsJSMn9i1hXuJ
TR11rwlRlKjfuKHk/BWOTq6fyfjh0+Kvtf5wDBrNTjVoUaAc5j0SNG6c0PSIBzJSRNbw7qEdLqRJ
0yflIfpNca0qbJEUEYdohtuRjTGCBCnHdkmLBKRxJg+8uCaT+FUnkXfIoXrOYv4kQcqT/sewh5SM
f80P8SdbMn6YB4hMrj+qSyByaNmBcnL9iYkTPZd8JOInGi2MpdhqAGhIeiMbAZ3dPcAWAXQwj1HG
dVbwUUTsJKJEohqT8kRgDgbEMg056rJTFixrKUJGC0ioxHZVCNG6wjbqJ/GjjyCxy2HS/5pLkvFD
oZGcv+iH5PpDazK6Av2BKbl+JtdPvesvRUhkjj//qSUKIsjF7yJTHr72wNVbXPXVXFOiT9oQQC4J
4lOAQi6JSD0sSauSUHXFh4AjLockGiVEojEK2JxoFAl5KdXXlbAloZoEdbCUxA8+BEeAA/V9KCTQ
7eR5ypP+T8YPRU4yfmaYO3LZkQSuO2LloRznkVZEiiU5IyVBlUKDpmNy/fyAtUu6XRKqDzW3J/0/
i/nLgpORpqbRydf66IcRIFTBHgUsEcLR4H1wNI0BEeR3ZkWf1LGpqzBbeW5IRzeJP3ZMudsiaB0f
RsjoFXR0k/5P+l8vZCL4yfiJcIco6PgkVlDlzFaeG9LRTc7f5PzlYaJLq/Hjwq2C+i9YcFn4x7Gg
gpLYWOBugxe1rbTcXkhCkxOfOmGqWouxGaHLCzoYcLChSkKVKsTkWkSDgEYQYAlbEtIGEtx+AjYj
dHmBIwG+hiHCfpQ8NS2FpYpGJPGH3aj5hLswgiYBKSYJPr5cAQSS/geHcP8k4BPuwgiaHC7dLglu
nysk0FYy/pPxHxGfyfjhHiCaz68E5lSsAZVDE1ZOW0lw+1w5Xlvxr7DwL7vGrwDTkCCXBG9A0BIV
EvCIQeSSgKIUiFGdPUPaIrsyp0Zj7UnYkoiR4SYlbElQC3rmY4x9EIM3JsFLZqy2hC2JGBmpjUTS
/zH+iWBwZwEt/4TrIiSpIN0uiRghbjLp/xj3RDK4s6TzJTNSFkvS7ZKIkZHaSCTjP8Y/EQzuLKDl
n3BdhCQVpNslESPETSb9H+OeSAZ3lnS+ZEbKYkm6XRIxMlIbiY9a/MegVV8LjeXD/gP6GN6FULeE
B4Dk3ScaLEQRVCRh0gaO1I1tcWYOt8Ml9Wwm8Sf9z+MkGT/kDT5fKEIoh9oogorcb8BJzl8eVOS0
uD5Jrj/J+OGhwucR5+vNqY97/PA+ajT7sqvGwk8KFMo5PxGXcRnuSs7nNvVkOJ+QUM51JdS4zFj5
08FwOrpJ/DRAp+PD09FN+j/p/2T8xK6HyfWT5gV4hsIDijxO9PiklbjuJ2394f7RaPYTXhoLP/Vc
zPlcnlSiOFHFRNzNZfiQc1Mcw2xluC63CTQ1HcXkRY6N87kul5ktNm6T4+R2OJ/LcwxRfFnk2CST
CKoCmsvwdrk8xzBbGa7Lbcqmo5i8yLFxPtflMrPFxm1ynNwO53N5jiGKL4scm2QSQVVAcxneLpfn
GGYrw3W5Tdl0FJMXOTbO57pcZrbYuE2Ok9vhfC7PMUTxZZFjk0wiqApoLsPb5fIcw2xluC63KZuO
YvIix8b5XJfLzBYbt8lxcjucz+U5hii+LHJskkkEVQHNZXi7XJ5jmK0M1+U2ZdNRTF7k2Dif63KZ
2WLjNjlObofzuTzHEMWXRY5NMomgKqC5DG+Xy3MMejJcXqN1fldDq8ZPveb1mtTjc5uc1pPnfC7P
u8dlOJ/LgwwkyrmMnq4en9vktJ4853P5RDBwebADifJEdHm7XJ7b5LSePOdzeW6Ty3A+lwcZSJRz
GT1dPT63yWk9ec7n8olg4PJgBxLliejydrk8t8lpPXnO5/LcJpfhfC4PMpAo5zJ6unp8bpPTevKc
z+UTwcDlwQ4kyhPR5e1yeW6T03rynM/luU0uw/lcHmQgUc5l9HT1+Nwmp/XkOZ/LJ4KBy4MdSJQn
osvb5fLcJqf15Dmfy3ObXIbzuTzIQKKcy+jp6vG5TU7ryXM+l08EA5cHO5AoT0SXt8vluU1O68lz
PpfnNrkM53N5jWYPUEANEuURaikb3Gb4lzdHff5tvulZHzSBKUofDCtlg12BJmrtJsUbqCdFqa6Z
QYQET5rlRBz8UlP0TuoSQfa5Tc4HVRIAYgYZ1kKYJEWprqSssacMeANKqinLH9gV0AQJMNmXeRQG
TVYXwwzYJIAZZKR9TkTj1+pUOykb3eb6ocn6Dw//hkyrIzDd4fWjcyRsSXwQ/jVuq9MrQpSQfgB+
1h0iqSOUgy41p0mpn3oY9PigljD+qKZURakuq3lbwIQiJSIMyhqHtcg/uQX+CZ2ZdXkfuU3OB8vS
yAwyGoSIT1KU6rKO2wEmwZYEFaMwxNXlMtwm54OiBDCDjLTPCVKU6rKK2wEmAZYEFaMwxNXlMtwm
54OiBDCDjLTPCVKU6rKK2wEmAZYEFaMwxNXlMtwm54OiBDCDjLTPCVKU6rKK2wEmAZYEFaMwxNXl
Mtwm54OiBDCDjLTPCVKU6rKK2wEmAZYEFaMwxNXlMtwm54OiBDCDjLTPCVKU6rKK2wEmAZaELEp5
jdB5gALV0IbZvu3iss+Up9k06dGhoSdeaLl9eFpj0Kfp5euWrLUPXvmT5m3ECKU8eEH53y1yO4xY
9nk8P3ux6dbeaYQloUcRIfOOL9Wut/R+9TXlR+tzNm959//ll71ycfZQa3PmjkHUUnVNu69bstI5
9aMth24dpcZ0cmmf19szB2+oMLW2OHcMcLaKSqpIghol94UxCFUpQ0RUEURQ17z7b2pXGoeufOLk
2s8uvK3M8u7+rpJlBTn+oSt/clL1VQQOVpAGGQ9Je9bgjeUKuOX3g+EaEraJqhbhMao7XfxaJIF9
MgVmRVsbFlb+fGXGzuffu7QrKhg0UHr4tfqIT5OjfmPNYhFnAx2jWUWOPbvqVxz3q41C05A4BioK
NuGpLS95ZX1u5+GGba9pYaHXdwL2gfDiCtgyB2+sMLe2OPTjp25e5bY17tniVyMQemTNHNxUYW5p
cewcULsc1fcPwn/XFYvWO701Pzl6n58clEAeZVP2Xc+HBIkMz1Y3Sl4PncSgJ8D5UTal7scIv93V
cWNVIXTK07/2ydZd1DuBv7a0eP9lebBS7321/vxj2qDKPibUd9MTFxX07m2726utwKglVqc07scw
PdrSsuGE85WLM8MsRQn4/a0dvd/Y2U1r18OfWXhbpbw4gGDI5/N3dPT9yx+6t5Dax8j/CF/rqySS
+MED5BlyBdEyx7pEE/u1UDIKuUo4TmxaUIf7jGBr59DeFs9QUHG43bd9aeFj6dqo4JCYtm1YsNap
KEGDQ9O9/6J5dy2BfUawqX3o+FDQ5nR+9aqFj4EMyGsyaisSp8N1sVt59jcdK87O9bW0bBpVnEbc
p5iM4ncqQUvVNaRZgG2wSkVJqLAlflnBiJABZqwZDFMwUQ71erpSjFqnXAozw3FIoZsGbcGfQfFN
CpHgtFgqUuCUKDpJs5KIllBhQxfs4BZIBA8ITQWrTNovwUsBECPklGvCaGGGRMZ1dK+sgiAYf4Hv
M6RZScQa5zahloqKsmFuHuwzAr7xQ+0jewaQi36TAjoYhARl1ifW5SpBz7/KfcYsdDUzErYktJrw
Z8gAv01jgkkjO0J1UgUII86pWeIPtwBjiU3wEIW2wCzlsiGuEYnh0hc7Aor9jk9nxYqEYc+AH9So
FSCkWIIYeJOz1ZVdkwS3RjS3KeEBIVUkESsPVdSLKBmSjM15W4noSrOSmNkm1FITQICKyaiuCc6M
m+T1XQj87UI3zGtIqRBaIDmDfSGmZgz/w59dcOP8rFwIrAjd0PjYlM83NTQ+NeRToYwCPT416gsO
TgWdtMgoIRQApj9oMpuryouevTq/lsRTxOUjGNQEFJvNUlVV9POb5txBIBgGbBqKfxL+hHRl1yTB
vRGLBzhqp5lbonST+MEDNGqUR/mHe3iGKiFGMSxI6VYspWz9XFWVUQl4+v/hydbHRT1co3d8YeH6
LMsN6/Ju3dYDCDaU5jy8rrRM29eOkgUl7br5djjL+NGWI3TwgJvfKtsVSxy3wpVAlYHvAQM0KgjC
5x9SlHXn5zfYFVte8WOOwR1qo+KDYaNdPV24uYhqTLWv2Y6QUEPKH6Sv8oois6xh09HlkiAahV+d
xFHthdR7kJBy9+7WTTXV5vGB/27I/Wb+xJYoQShG2NeKUWLgqoDsYQx+v1alfUZoR9hPEL9mIEIX
sNnPLzQGeoa+r9XjZ7QMr9NoGnPIIYE8FRVl2wiOZ/3rx5c1iqo3RB6VRdiPwL9hUfFSs3L87XYt
UKM0E8MWYV9TibI0OeB4dEBdLhl+3vftR04YjkSpiWKE/Qj8mi+EmE80EWUgQlcHm5Tp7X6mJ/+6
sqLHHAPRJ386/uf4sWUyNRMGffxRWlSU2HgxSjIRmTMYf0DRnqmaL5znUN7UDueUtM8U4d2VmtSh
mZ3/fWh62hNxpAGcwKW/OqSaNWcO3lTh9g1t+H8nd6ksZcM83PLA8QaeK4tUm5vz0lWlOdk5f5va
fTv8xLSYyO/uPrzsuIq9Nidr++fKy8wZ965zff/lYc2S+IwY39nhn3186sTwGRw/4GM1NhjBB+Av
7H/etKDZVoPX2d2X5MGNlX/LdrnPgGr/pTs6PBtLFbN5Q0jZpli/c1lpmaIMdY548zIK6TYUpOxW
k18JeD2/1CbL86cmYauRmQlbktGLKop/tS675/2T81/zqKGK7RoUG27qvcr0FBZjE/iJwoRV2V0n
vlSqnBrsz8xcng079tDQ0NB/bGt+AGaUotyxqOTec7NybHh7OOoZfe6V5k1dARoMu9O1p65oeSFM
YFAZ/sG2k/cJFcXh3PPpkiXZNlSCqv7hH+w8eR/0AhsqGTkxnD83t9CstB5rLH/Vc8ui4n8/PzfH
jLNtqKf//h2t3ycjdsfuS0tX5NnAs52dHjt0Gp6aK6EHL67MCQ59vSP9x2vMe3f1ASsq3TKv+N7z
MsvSoCPioLK56+aX+3YJoY3Vhf/+qdwyhOU/1DQBEnIHo1MFR01zV1om2xX74mxLYNzzwFON99lc
+y8rWerGZQvOD55/temaZjJjfvIzlVeUpjmgL8FgZ1f/v/6Grtmx/DZxLTcoBe55inK8ySM8U2rv
H/WkOea5AVewtaX79h3ifDWu0xbGcdqDF829rQaPcZeuOWvwrIF/OqB8f43r9RePPmYt/vmnMnyD
gzf/qh0PbMHgNaVFxqnHnz5+u1cscrTUKeZ7znVB7GytFwMgoiIGUtc2ELZnQMBEjeM9y8ruPDtL
jGNoqGfgP3a0PuA1v3zN/AssY/c8eVLbS1l3f2nuWcrIl58f+s9rKy3NLWWvwjJqfvLTcfx2UXXJ
bwT+S5uDgDqefeiLWzd0bc5GrYk11SXbPpX2wrueC5YX4PwKBpua2j7/8kA9xrFhQ3X+wyvyy/D8
JHT8WPdIfnZ+36lysb4/+N7Adetzv7Ai89Y/sKdsgAb0ZM4JwZ5Nxv0PelScwQCfvyBMxRnkdao+
GfjL5mSueXN0l/BBbUX2PFwSZDJt+/z8NcbhL29tw5CGADtvzn219j+8cGxDW0BxZ9ZfUjTfbYHF
J+Cfqq9vXfa25/4L5t5VhSZu2Vi7obm1/NWROP63qSNYJNuRBJySaqm+d+D4eGlOmmLFFVINJzMe
walbjfq+gfIddv/leTk1+ffsHn5AXac0/fAn2ZSWJRGWiKSS8SP88XGOf3qAAj2I6ERttg3OJQI9
vZs8gi9/y8vT63x0v/OZtm3ImdrTMPDsS4cytzW18ZDyDpb/ZL/5ybZd4Byh+DdzUoHsaB+DojPV
7jYb52SyByBk3NO//IkDF73UveqX767dfDj6bkxdyyIj0mTMtJmravKWZ5v6+r2jQYPbnfntDcW1
ilJbUvK9lbk5tpTOHk+TJ+BwOm+8suZ+mG4hnBMmtxv2GX3940LF/c3Pl6zBcUw9cW31ctgi+LzH
O8ewKtv9zc+JKqMx12ZZugj3GZCcxpRbllX/aGUeXJ/Afut4yJ2X/b0vz70HO2Ld/6WalWSkx1dY
6HSjBiTD3S8dXvL4yS2jQ5/d/N758BaCmoR7ldCairIfrcmDfUZfv+d4jw82c1U1pU+cl4oOzMl/
4uIC2GcM9Y+1jpsWV2XgKRLq6VShZUNxps2dnQH7DCiYbNMN1qzBjVWwz/B5xsG+yZZ29fra3dXY
n/vX1VxXlW5XJo+3eYamjYXFef/38/kR/HbJL6CLyj0VcGkP7jnphVNfGILC4sx57pSm9pE+v7EM
zldBHWCbEnOaEpqEh0r0vsf0dCAYshvN6UZLUapp2/H+jhRzTl7ewyvAD4aXP19VlWb2dvfdTls6
gEipIGcZPHzpH7xvSjjTGBcSIAdHmKLG8f6LFnz7vOwcM24KO30KjOO3b1zwoN3fHUyxOd1fhjVe
BGdtee5Kt9kenNxmMufbjLnpRuCH/Rb2D/rNqeEHWsc+npbHC90iCF1FNiFMOWCkLigoVKZah6YU
o7GqpvyXS2Bqwm6v8NmLi2CfIaJCmTe/YLnbnJlKVwCl/uRQq6K4y7NuEfipF2BbJYCJfC0XwUQh
hTI8SXVJ8FqiZZUkYmXC85emsJzIavxrrVMxCqdWBLOyCSTOMPzCa+Mje/uDSlrGTbRwhEJ/vygD
VtrjPeIWDHsNU9viyMD39CmV5abazJYKJ/zuc+qxayoWuy3eobFDnV7FbFm6rHr/PDPcv9FGAE5z
A+GBIG3N/+pWQVFvD8nPQsQMN5Ym4waHeYPD+vCK8hVwU+CfeB2vC6QLQpoRMtnWV4/Lm6UG1qmI
8dKKJCbzRGTCsJPxI9yITvsIx78cXEbwU41wxFRkWKHC5xfv5YG0XBnoH0xR/9mU0KaXW4QpcQWW
RsELIEABZFDu+dS8G0tAwPsLuOk0KNubTt0/YR3qG5PiMorq8ZgPWpreFZDtoT/RFBlU29VUA4pA
P/WLZw9f3zcNd70dN84pTLfWwjFGBkJq3X+0/G24Lhme2FB7Y6Hl3GKT0k26/mefP3wNvGdgdrbc
VF1mNzsVZc28fHxg1N9hfqZLNGc78dWFVRZzEbQepE07aB26ZtiyUbH8y42gMbX52UOb8Hgi9PC6
hbfVpH9tleNoX+5SuOwN9V79NO7GNp5V9fML3PiuBqQpf73Av8sb5z3KLy7CpeXQa/W1h3FNqa0o
P7g+Oy/Prhi82y4qhG42HWyYg2eqKVs/v+jqPLNwmjF+FQ0jNqm0Hm4s3z2+MVNZt24xNNB08P05
b6LnayuK967PW7micE1j50X5uHX5/S8Pb8BlxtlyS01Zun2DYlb5Twu+QfLhNCtlVYVd8Q89j+c9
NATCM/jehuPYTXPn5RVuK+zZMCyddviaYdNGxRrpNOXhdQvQaSudRa81PttdcfDizHdfPwonsfBa
JeAQE2ls/m+6/FcWlJ1Vtd/lXwou9w1sinofE97zyMADpOMNw2ogBTkkmI3px24WkAqiIJk3mqz/
ZyNctiX4lK0bFl9daN90gfNicSpQuyBLOd4FUO5E5yn7D/QrAVj3RTJYNL8dEX5zaH5T113Eb3Le
ik8SpX3j1g2LyP7db8rQPXJ9XxAOOfCVwHQbbDXqtUVfnUGw4/f0b3qydQuE0+Kqn690l5emKgcn
d6wuwKjY//6ct2FAQ09eUXtdMR2zi+E3jL7TEyzLs69wKo/DMMn5RDNIziPJxz5pBTndiIdF0WUm
opXFJ9XGykTYYf9kY4QyL4TXH9FivHbPZPzkCv8fjnqWr3JfOC8dn6EYHOuLzUp/154R97w8dYj8
cFhm1PYEijIJj4Mhgf9TrXgSPd7vfLoVGGvmlL/y6ayS0vQHXmhwpdfeVWV44qlDt8t7HGotTq5Z
0wLZllf0/M1FXPDQ661bZAhhRWQEhKbaR0JLs5VJipxk/KCHPmHxz8NFo00ioihWIMiAoAmP9SIs
NR9BxEQlkiVVqiIZ5KvLxP0r531zEWyDQ6/sbLgP3ySA1yN932r2YSOyKSavKpIdsY9AMTlOHAPQ
ApGvs+f6PmHOO9HmUwqNIbxiivW6bNnCwTLPe62Dv9l91DAoeiMujYGe7ms6g2h5ytvtU8psaWtt
oduPN69tb4MpdUuhY2Fmak2+Ixfm7bQyCmJwqwkm+3uv6YKGfFvs6T8U/c0szHmyBN7BhL0I7h4c
LuvadHwQsP9AJ576GAxbDrTfea57KbBEUV48hLbItK7durN+R7pJCaTAgUFZZtpZxWhHILYUZ8Bz
jbEfvAHPmyAFr3mt1391kei7Sa160yP8qVWhP0nXv3OfB+BtGbLdmSn2O8a0J5alwhVpKmAA47a0
9CttU21jQbgTr7t2yYmukb2NA7c/sW+buIP6AvGvk/z92+jYwOxY5lRGm4bEyRZigiEQngFy7Hvv
jf3ovPSKXIsyrDkNXT29xeaIcBpAVJ0GcEIV4gU0M7z1xocYOtLV+cBhJ4TQ0nJEvfn5lm3YVeyg
jJ888QbmRBCfVkh1X2c3QkK3M0hDDJISrC/NzUHwXQI8NDZ9zStd8Hwwp8id9XL3IX/u4rysB83d
d085PwPLfdDz0wa/grsykULSb7VRfqvTRGoLMiLtB6X9NSHc8GHo9oo4nBhXQzei+yLyFOXYwU7Y
Z2A4nRh6ZKXbDn0PGd2whwl6vgv7DFF1/avdV8CTzXAydMLw5RkmwU1CQHqGiWhuBBbzp3CsOn/R
yxDeyIoU0pPHtrRR0GJbqCL+eBg0eFH2hRW13U8IfvQA7CEMuxr6b13lLqvOWvPWqFKdVQZ3IMcG
2vKyRDU6VxCQqQugVoQVSpxepGX7N6XVNw+/9H6X4YfN6HaDwSbml9UaUsTUDqvwMQpzgWINBaea
4JwV5iacF2bAmbSyeM38JwfE3Z2qQhNNg2aA4BQBg1kyfoQrdGP4TI3/iGCiAl3PBc2Wj+aRSbhY
283iABmjTi49Kfcvys4YH/3vZm+9CKQIkxC4mMSyohi3XrHgarzTCu7cceRSeC0gwg7Xwwp1WaF1
DXNl24B4mSkAV3FqXWJAXfkAxj8lrjHAYnNw27HWX1TYriu3u7Oda+FvmfIgkL/RAAAgAElEQVTA
0MDtTzc/LgB6vWJ9BxXCqxic8JqCL+WmC6q+UJXGPALYsS2y7B3zkx82lGWI00tL3QV8cVcceRm2
ZkAbPAbfAEDLADhEtyBaUbNGPRYlNbM5/+2z5YuddACiVUCPQoFhOJdxTverUOFqPgkM8YpIUK0C
cfR8SBmbwiosCgtB77sTwmkh+tqLUrWouEqzLT7NTpNy/SstSz9XOS/NXFWcDX/XrVGajp2c8+rg
9a80L/1cVSx/TbkbrqCvNdDWBzd1DlpZxBg2jsMLnun47qoYDnQaQgttKNd12galXwUllsUIgKHQ
fa913bFoDjgcdg+bBiNigCSXFsJVV7ycDy2JyBGQ4MkgCYdUSPQuMByvqZCULOHs8HADYFqsLaai
kO/5E97F8+11NeYnp7IL4XWcpl4MHnIstGcAv8X6pxn8JvFnCdOYwfQRKopfXAzAvhDSQlcaZfZR
QGghAf0SRUOKijY1VXzHkJ5+ogQghwyHXlUKOdOhZLig1KIcmWTzF2XDSbZM8RMxf4UhmvgSf3gd
CNsQoEFY2GLzV/ofRVX8QotkVZzMTgSfqkUOuvHbVdsU9lFIzAIoESF0P074hSvgiu4feas/VJed
8UUYwLlwnDa145DPWiJqaSAEGZMZQPHrr/X/cGW2w2ZfOh/+Cu4K+p7dcfwaeIeDEjhJ+EnNY0wg
gxyvfQBjtK19DnyvHhQxpTxx6aIbyy1XnONStHdFkR0RPyn09Stcoj9O/v+4x89HBr8aQhgXPIm1
iyIYoxDgYm193wRctBx5OY/Zu27Ftxq1ZMv8p5WlNrhnfuJg9CNzEAnPBPOOaxevd4Mt3+Znj26C
pxtoXAt0MiYBkVYMBmVoEs4n3JnptaFB3NaoyZiBV4iQR5s+4purwpZAjlLYVuDBl449aDRdXeW+
qDLz3OI0mzvrWyv7H38H68NfdsUSJjjru+O8OddVpSlB396jfXu7J15pCdz35YVLoS2CTVqiF9t6
xuCxvm28/85fdU3YcbmfCCglGRZl3Ft2/ny4ManKNimj4hVUCUl2VjQXnshq3427P1e1OE3xDQ3/
oXH4eO/oTp/r91fT6pLiwjN4vJBgQjvYIp4QhbQqZIoG8EsxVAWfcJce7BGAwSF4EVKCz/726DZf
Cr44A9dmm8muBPbgEdDIF595L8ue9jfV7vMr3fB2Z9X8sif2D27yeL649b0sWyR/36CnGp5keF9t
FwMATwlgjLVNGARAkVU0BVZF39HVIoWd9uuuCVuE07bBV5lICLxBDlGLaOThS0vpsbStsOTlysF1
J7WBFz0GweM9k0qxeQKutaAr+ouQxmFfqMabCgmKQiU8+vg6m+KFwxVqVNNVvFMdirJlf98d80vn
zM1/MAj9Db5cD++BqhZUAvwT7bfSJ/YN/BqrRRLf1kb7whWEB+ebsA+fqnN4l4Gr9SuCIKasmvDC
21E5KRpysCCq6NwQ2w4pHvixOCVlfyd+tSecQEx0M8xRqagGtJZImOGPQEW6hD/sQ3UNQcn4bfE+
ioYS19W1SYApB1ga8THCT5DhhDGkbG0Yqct2Xby8AA5plf7eu2EWkKu5P7Uu+tTbIZw79e+f+tTx
U+eXuC6rdK8odeXYbFdfUrbhx03hQSYtTVeNfC1+UIyPNanhd7u1FJr+3vHRG8uz8JAjbAT8zeyW
5tbi4d8U3ox8jPyPXeRdEl1O4pcuEf5QM8mkcY+avxRCXB7oEFy3oIL+QAE9K5Z77+Bz+Kqn5W+v
LN8ooyhk2XFFCUQR3F/eTvuPKKNkR1Eeq5uP+4zx4TsfPbwJfrkrIqVcZDMu5hwyQrocAzy9gOTM
eXy+FYFBgjc/lpfg+9j+8VcAgMZEAv6owyAWCj382SUHb1r6g/zAfYd7Vm0/tnzXELAzM8J2wrpo
F9Xn5eIu/NDuo+e/1nP7idFtbmc1ThgDXedQRqZR3AMpaWkFvsnHe72P93mViqJvX1p9z/nO10/B
Dk05tzZLBeN2L6Aj9yioBJjlePih+B95+sSGfX13n/KtgfdygYHMaTy6MLvuXGjBiQAeWJaDkNCg
VrXIQt2551xRpdbCh0zTw3hwaqzMULYAYPgbtd97+dxvX1653mw/9tWlBzfNXTI0uuntU/OfOrAZ
nneA50M25N84d8ng6Ka9p+Y/fVDlG6xriszK0PCzcCET+OHTVphzD9A4dtY78ZWK6Q54XBUeDgFD
Os07CR4LO205yGuJHKKV4HNNdflt8OgkOPaLtwegvbXrq+9htUQ2e/BBUyp8PUfFgActtoIclEQM
BCmEkEAAErViUHZ1jEBYOEryHoSjN6F7v3Cgb2R8F4h5+t4YCpnyctfDcj8+9MNesCbEhA3FoPkt
2j9Ujfmuds2+tvu6/xwcIN/IBNqXiVBREX2oUrIeCWLK3OBvHwspRued56RRdx5bla9GBVjAXqeU
w7urMI7gGyhBghz+wALl0pSoDNuP4lPtzLlUQeNsDcFGqW2GH2T0/vR0yQbkhJxy2eiZhF/z85aG
/j5FqVpcBG+PHWrQzvy0Wowmc/qVON6QrKvzRXjBr8RWlsOit/fSzMdPDmx46UTuT0+AEXA3CIoz
YHMZUHrOJ3+COIwCjZocO3FgpsWP5cGz4ZVwWprwE5Ifnl1qw7EmN7vlknzYT/c1dD5A1R+Ya7po
RC8GuAzQcf/0dD858UNuAYeTuz7Q8yRAwqSr50MuQ5KxeZRuTOviXQ0QwkQPU4VVg7JpZ+tnbp5T
6M7++d9n/Hvn+MB0SkWB0433gf6nd+OPauDUV39bgtQVB31m5t0Az7YhpaXde33tfeK+1mQ09jY3
z9k1XDe/An5LcaytxfHbfmFEhJfaNOgwDN7BHxwr/OZ82/I1iz3LxloGA84ch/hqn3LoHXgZAtvH
hARR+NtHIhleaR67rdy98tLF+w/3Hg/aPi1eujx6At5pEBc2VRfw0+2+Ag8xD/ZOKSXm+SvmbrP2
Trndl8934cXenLbOEdoC1y5I4BhQhDww/KsW/1fL7XfdXLv6QN+Qw3lxFc77A4eGtrRP/styZ1Vh
ieeq1BfaQ+uWZWMFXLsJIOVoSyaySL9LZt60oSz3hLdqTu7KQtG4HV7/DNz5Zu/B9blLVy0+ltPd
YnGuh6MXSGjKf+cbvQcvhapFx3J6wlVQp/VLiEExoEquXNxS0v3GgOnTtdnwEGS0peduv7eyf3pe
Xtp//M3cNYeHLXmZF+O3Kv29Ad/h/hDyb5i35vBQmJ/mmg9f920d1n42XnTJmPbtm+avetdTNB9/
iUsZ6r0bXhGlr89RRALYaKdlXIw/AqYcOAyXe80v8KmRSJmdT1ycDTLv7j55/bEppdh1XWHafVfl
PfArEX40HPigDQ+ZygvgWyrim/4UDADpZoKULyD13N0JLw6DMdEEtTIxuK2z7MZC+12bFp1zoE/J
zV5bAhLBPxwcEWMdevLYyPoLcGFtOtKzC5ojXfGphLyHyW83RPoNtz2qhOIdiLCfl722mOzDAYlY
r1VBRCNDVwazakYzhp8EG/LQ9Df/2P3ZKwvmnTd/sNIzaEmrokdv2HcB1ADv8cBRvOcteCeEkEs7
mt/QnDp/gRRczEUzcfmkqIkIF5G4aFSbgwI/CUGtRkjkQoNlBJiq2dzHtuixEZMFkoufYfhNITzx
MioO6NfE8Fv903XZcJzg3XEE3mxjbjRMvdMfXFpsvvGa+VWN44WVOVVpojak7Gob7FSyC4vLe69I
f7HTv7gG53hgZHyLopTAIativviy2v31zcv24o2SljSHGmXrwhr5Xwg5yisGbygWpMGRZkaQiv+5
PbABolGD76gvHjwP74pMFjN+YR6Sb+h/vQRBHhlXaFOLCK1ZISMKyfiByRKev8J1wpfoIpm43z66
8R+LGzsA0UzwZSBAEdYgeLFwqOjnDXvxS1bmskLX0mLcZ8APk3/36fpNg9R1sgi5IILT+AalQdkA
b9KrrjHnOC3uNPxzwFcE8VkDGMfkn4L7ZqEnbVCFLArivlePb26ACwn84EX64nIX7jOCU3v3N9Qe
gIsK6AdhAuHvcSEA+AuNY8BDCm071rK5aTygmJcuKrpuSVaOcbrpWNOyY3CYjA/LxRECiGEbQiXo
CSrf33vylf4gfAu07oKKq+e7/D0De/vhumGeXwy3BPAlMcUP/6NnMLt1xxGwD6c+y88qWl/lMCn+
d/ceX9UMv8IzOmdrc5Mv5MjLunpZthu+wqMmUIMklCNyhA22b/ltG3wRIacw58ZVpSsLLccbBuBw
wZbnut8Uqj/ZeufeIZ9igC80wj5j1IMHFAF8p9JQ33xKVKVEVuGdpXQFeaa+ufWru3rh917LyvOv
W4Zf7+xr6/r7Hf0gec3vT7w75DelOeqWl6wvTzMFfdt3Ntztk/z0MH/H+02FLlhr3jmB33oQf+hD
GAhfStr65QWLnSmjQwN3PttWj3OGnCZiCYqh0K2/P8ycBi/BgtPeX4U/PkFGlAntdQqwCMP64Nry
MtgPdbaJgQtd/7uTreiTkt1zTKgBLUAOf73DR+F9zcLsO0BNtcQhGVRIwCNIGDDq36bnjzzb4lWM
trXLSnCf4fftfPHohlN0JBPacqAbWoTl/rmDEzgjsFP41ktAhNk1v2+K6zdsR+AHNJuePxy2D/sM
1T68yqPFIQGW44XFcBPCknALAoYkAz5U39lufr6t0x+Ct5GqnMrxFnqiCPrYtdqCXPhNs9GOgccJ
tszBBvaCktY2eA1JkUsCWfAHwpSLyIcimtd4JCJUY00iBwTURI2SMs9lE5IQtQhSOFwiJwKsnan4
A0E8KYZVFLxmUH56FN+F8vX03+1Hz/hgwYQHtfiwT7n1xZPHx0PwUvfKxblVaf5DbXiSilX+kbt3
dcMczynJvg4mo9vsGxr4p193Qe0DR3phR2+Cr7+elbdRHUIaBc3tgZDWuuZ5FKMDaQOt4W7YZ8AP
gw55Nj9/RFwC4HV1sA3JqC7yZgP89ujxhrYrn2h6HMdeM04tgj0gIptFEUiUS4JUZRElUFnkpC9z
2YQkRNUnMH7AiarftOmMZfAG5X/Z+StGKyozXLH1yG964codlSREuNqaN7pNqYphYnRyC7xQqUKP
kpe9Aj7TDfc2is/VP1A3Bf4hLvg3ACYCwS2DcKHVs89tChmzEf5JsNRAqHHQtwuRQOK6XF7FAP9U
VbXd0DM6tQ17CkkPm6g0W26B/VcgtGfQVx9pf0OmDQA39sp2hbyacQzcfsrGXGuqMt3YO7krAifJ
mDfmQl8Cj+NXacACT6aNuRatCvh69oFvREkl1DPq24YLFCW0X+uwnW9PmQgEtoTtcz55HoIBumzY
0zspfkUK3hzO8WwqV5pOOF/wAHjFO7lllJYnfQxm6y3uFM1pGgRdP3P/cJtSEQjDHRfM/95ZaYd2
w1eFJyMhWeDFCA2SVOF2hH279RaHUYsuEouRiRxfaUv4zQBvimwZhI0sWIMUo6va576VBoDQ6yPn
c3m0f8/yOV8rnrr7uVNbqLnS0tDlub62Fvtv8Lz9sSuWfLXEtP35dzfAWY6ufW6TtxWDP06/ZqvL
5fXsJyLDdbn8Jw7/mkxbtcnQM+TdJvYiPPbE4gNz3C8WMfAMpZQ1jhR41b5efaMHPAmJ+43EKOd+
5jKcz+X1ZPT4s9Xl8hwDt5+IDNfl8twOl9Hjz1aXy+vZT0SG63J5PZx6/NnqcnmOgdtXZa7ITfvX
RelVhRlpaWlG8b4aVLy06w2x1eiBG/SoqOMmuGnVnPhIRCYReR07vFkuwk3qynAFLsSVE5FJRF7H
Dm+Wi3CTujJcgQtx5URkEpHXscOb5SLcpC3b85UKpa3ZuR0PSNSLLArwAjfElRORSUQe7KS3/P28
svH+tT9r3kW7Hw4pCg43yaFxOH9p/IQDkDFAjIyAI/A/fMXS20qMoz29j74zqLhdm87PzzEq775y
cNnxKQX+TcFNVe7+dsMz3UKWG+Kd5x3Wk0lEXscON8lFuEldGa7AhbhyIjKJyOvY4c1yEW5SV4Yr
cCGunIhMIvI6dnizXISb1JXhClyIKycik4i8jh3eLBfhJnVluAIX4sqJyCQir2OHN8tFuEldGa7A
hbhyIjKJyOvY4c1yEW4ynozYajhitxri7WL6kiGqweMisdzBBxBqQbYDBCTKqZZyTVjVFUZQLFKe
Tj7jHIRiS2pb1CjZITCEDeqBiE3EJBnQAoJ0k/j/Mv434/sxdti6kuf/av4f/V9vDitp2T+EX9I0
hQQkeN9ZBAPk8HfGxc/trzY3+eE7Yrl3XT7vrgtxn9HZ1LwMfoU2pDx5SYVb8W9+EU7O1YkkiJj5
iLWQhAySYhYjkZy/5LAzOX5w5CHJqSEniwgHNRiS8SN8JDwFLsG5gbkktArxKRyHIto8ki6VTlbl
2YesksJngP9Z/zgp3vLBkMIVBt1EF3RgACHY+FsFWKSCkEHpyERaqq72FjqIoBHNJpehqkgbWIqQ
IUXRLgEgCGhTk1QhigrU1doiAVU+iV84OsK30oGiSmYRMgn4f3TgS0+PwkMKzfN/Nf9vOdBUMpnp
GvEro4NfenosApKICzWMgT4z4md0aM6P37ml1L0UXggNBt9tH3mcHl0ZlHeOtPbv99wuX7dNzl8e
1URTGMiwlwSXVBcTsYjgeiKWkTMmflQ/0BIpcuT81eavOgJJ/5MHMN7EZQ7j7WN4/VKHM+JDbDUo
3qhv1FW8hIf7KjqtVoS1ExAJCwOlJ497EbiBiAHB8VDjlCcir9sYQ6SHh4lEkHryieA5Y/FPbxuA
lz5E9yAjF6HX9JzFPJqACJPWN6n6P/jAUfhyH4KAH39DRY5HACSYYu/7QfH2V8AP7ogEnQD+x1tp
QyG6p8l/vxG+2yXmFPYi0qYoq9mH7P+YtjQ8KgQCAnki8+Vj4v+IIOP9TeJXg4x96MVbIvEgAvzM
m79nbvywcddIsdWggQRWmBAUHe9giNCZKkiweKH9AclwXS7D1/uIcNGcjIraQSXQmDQQPAQj2mKG
gORfitNUwweDYC+Jn1zK3BY5REn/i7hjoZeMHzFtyCM05bV5SVHEloHk/JUrFiOEm2htTK4/yfXn
k3b90hZU/kmnGjAb9JOem/hWIEobqmJTlHxYBKYlTkfUiJYJCzF7JCyqqD6ulFRI4idXRPs27KCk
/6Uv4hDJ+EnGT0RYJNefeGs1d1Fy/ZdThrtFpT9h8aN5gE41ZgwdipvY6OFLcMRlLHLrAHsIqSsJ
XV2x2yBwpymj9VBtXTYt+br2k/iFj3T9k9gYST+T55P+B4dIJ5ymbxOxk/S/6vDk+iMCj0KOoiIZ
P+AH3TmYXP9FlOj6J7F1jCKN5aYqp2UVHip8aInt2fCkgoofmvU/v6Ek/j+/j2dqIen/mbzz569L
+v/P7+OZWkj6fybv/Pnrkv4/TR/DjiKuBfFl17g1fyoTtheQIJfEn2oprAfDDwlySYTrPmxKwpbE
6bcgYUvi9G3qWZCwJaEnmThfwpZE4rqzlZSwJTFbC7HyErYkYmU+LI6ELYnTtyxhS+L0bepZkLAl
oSeZOF/ClkTiurOVlLAlMVsLsfIStiRiZT4sjoQtidO3LGFL4vRt6lmQsCWhJ5k4X8KWROK6s5WU
sCUxWwux8hK2JGJlPiyOhC2J07csYUviT7DJ/oG+RLTp5A1ySZCWLEpiRmv0vTFhBcFTURKxfOk1
JELinwSIxTBji2qlhCcJqpBFScxoLYkfAyAxX0U4UqpIIun/ZPxHhMiMBRk2kkjGTzJ+ZgyZiEoZ
NpJIxs9fKn7EPych3a09z8NvdcClRFzhNZIKLActkKdERFRR9IHUUVY1iSpAyzyWoFrOB1om+saJ
ho19AQWiJ4mf3KQNhBhD9QcBkv4n3yTjJ3ragl+S81cEh966RJGTjB+9ONHjJ9cfHjmflPiho4+Y
nuNroRAQkBsMYnchFh2DuGxjjhW4RxB7AxDVuZxrMYXyLIFNPISghYwI1aZ4V0vjY6TOzNexqTWb
xC+2XGK4mKtwTJP+5w4BmvskGT/qll1zxAy+UgNp5nlKEzl2XjO7Sf/TWodbXuF2jMmk/2eOq2T8
0E09eEm7Vn5040c7f2CDBqT4p4NpL8+XEtENelCBQmKfEX05F3ywKq5vuLgIL+CH6gTQRK5qPaJd
mmKQowzb4uAkjHClikGblVonaC1D+8hJ4kenJf0PoZCMH7FkJ+evurYk1x+xZCbXT1weo6416oKZ
vH6Fjxg+nPVTeBS8HZXCv6vBlycMTfhPXMgjFNjJhIhhkMGEwrh9EMMpCEGKGlGPGe0hxC4h4tQE
dyOQUDcCA9oRByqiNlJG1RGNqjIRukn86niHfZv0P4uxZPzQ3KbwAG8k529y/YFFk93aJdf/yOtO
cv1MdP2kPQF6LyKZ4BJP6w2/bIuLPsip1yupEXE5j9gKSBHVWhyb4n4L903CejismR2xucFGhIxo
Lbx9UbcUtImhXEgk8YedT76VecSYJv0vwjkZP3HmJosgqo0jk4yfZPzgvZ+2HWHrNguf5PqPFyWx
AiPBbr8/Mdev6F2DGh14qvFBl+2UaofJrsC/YBVonJyW8rEE2VENiw/h7DhbAb7cczu0EaGcjjFo
h5SIHT0Zjkev3Si+VNGzGSVPRdRiy/EnE78jzVJhVPonAx1T02G3aA7V81sUXxPHyIEqyCERwSWJ
pipV5U/yf5Hdkm1UlOlg/Xgwti3VsvjgrfN2o/hS5S+Dn1rXa0uCkYBj/ZbEr3rpT4qfpP+T8ZOM
n/D6Q9dsvu4IWjxAEacXeGAGqzrmmDB6jLZ7lhddVGS3EUtRxjwjT73ZvmUU9y1h04rx39fPX2Ud
vun59kZVMmXjWSXXVjnS8Wc7Qt3dff/7td6DOpcNZgcbvXXlvGvzTb6hnkte6gUUoA4m4mBTG4La
eDLWjO11JabO9sveGBYWVBlNGPsY1S4VVavah5xC118495ZCw+bfHf+pV9m4vPqWEqsmgp+B6eCw
Z/Tpve1bPapZUauDDUBYMp6rK8n2Dt30W/BYPPzYZdlC2E4U/i+cU/21cuu+Pe9/o80fid/8ncvn
rkgZuWl7G4wImdLrrx6f+y1B/3/l/OobyDPTo//4XGu92gNd/AAMWodEBOuyqkkcyvVw6vETwb+8
suCu2qxs+FfnKU0HjjZ0/t0hD5QMIfNDl889B7bY4RQK+AMnO/q/+84AeDWqXRkhT0woG8+vvjlu
hOxpf2YMzfH+RtmhomLlEQLyGCTa3DQ/eJkc3LBvRa3pwcvmqeOeQPwQDImnprTkJ+dl7Hv7/W+0
+qnTf27/JzJGXAY8pxWj/a/6jXBr+ccJv835zBWl+YB8bOjaHR2doguEPyMn/9ers2GlhqH5+ikc
Gho4qo0fP6jOY8N067LcgcNdWyexghSRipDhMRZf5kz2v7g8CZ+EM3LUzH5OzP8f7NvIOf5x9n94
5Ql7EijYC+D7F/BHhAg+kk3dfOWc9bjPCLb1jezrHBueVtKdGTevr/lKKgjQyRDkxntXV69Kh5tC
gx0DF4/XLjmr8uZq2GcEGjpGuicN+fm537s4N0PcMcD5G/wJdcyZHeFco2NNPu5+bO6sW1PlsgIE
JMqBAC3KETkU4+E3gBWT+H0yIQNwo/soAgh7IQnCA/iFTVzLkFKb1T6gtRRhF7YXXj/+TQaUFGO2
y/W1S6rqrKpbhClQAaiQk65qAXz+b2uLs8G0KcWuix9bxuYRACrGxW81I5JUMwiE2yX8qVCjdh+N
QBJux3wm/zM7AnZc/Dr+t7quwusrRItnX8NAfQL4CXZi/v/w8RcWFnx3Ge4zfGPeg50jzR4YR9OC
eaVbzkoTDgsJB4bGaJS9/jG/YjKba8oLfnCRWzpcxo82yuBf8LxOhKyv2mBJxP8sQuLET0gbXIx8
QMJjQ6uCHnxw/MT4H/udaiKbEApY1OL/w/c/IadcdgSK4g9bxubhQz/+sTLR+fuRx59ihEUUU7rj
agdGkfR/3ZwMuiNMNcIqlkj8kA9xHEVYGjZeUH1tpSsLju4wkWNRRrpdEqJWCgjpT4j/sdPkEyS4
/9ELf4H1UxsOAQMapFH4+Ma/8BrLIIbxGyAiESEWGMXwjbVlFSlKYGzw3h0de1UF830XV69zm794
XvZPXx0AX1TnZn3r/EJ5/+YV11RDyHp1NZyDBJ7beeyRUbDW++Mrq2vcmVen9v50AgyRfWiSZoJq
mj5qq7NgXx/wh0xm06cXpj/2zqhWzeVJEe0I5PHwTw5dtpXOM0hGzUVnyRRo69lEPl2YNYIwExaV
Priv4bbWgGAZ4PjnkUvnLLHbLy0ybz9JTBKWebitSxaXrUoXRqYVL7Dj+z8sT6PDxoiqQDEkHmch
AUa0nJbUkHpbChW4sSPMPJcqEuHMBJfnbYGW5v8AyCi+7s6Nr41oYJAzA34BDGU0AhES4Hj+/5Dx
ry3PgOaajzbdeMSLEBSlurjoJyvcJVXZ1QfGxGmTovg9N//2FN1iokBhwQ8uzLbl5H0ldeinE1E+
ESbCkaMc3Pf+ba3wwFGIGe2PXFolIsSy/SQMDtclxXAeESEqm8sbaHDHVc9r/hdFbdzD8rPxv2hM
BMxfwP/QmMAWgV9EAtT8afj/ovHzIeMPhrSFw3ReebrhkDj+wjG1rc6Vx27YJvzP/SOKH5CJhSI0
NglehQQWyL1J/5MronyCzknGvwgVmYXnYwLxQyEqdVUCXgsFK/AXmSyutbgHDmx9VewzqCHFf/+b
PcsvK4Sbu2pFaVQsd60uLFGU4T6PL8uZjzdywo5ROd7iUcwTz6r7hKnuSaXGbLCI+C4oyHtseWZv
y6mbD9BcAiW4MRG5YrymAnb2gW1vdq9eXZxdmrP6ndE/arhWVxbctsiVbQVUobGx8d+8feqx/iAo
rq4sjOYPBBVL+ub1pab29o37PSBTXZzzrbNySuyo23Cyz5OdmTfYuQP6mvcAACAASURBVPGdkcLi
gh8vTX3l2Oh5tbmIfzrYfKrrtneG4DGI1mzsp1plNoo7V+x0SAl6f9fpW1Jly3Sn/tvFheeZx7+9
45SG3PKdSyoXK547XuhsBGFXztfn0U0zWYZHCNrqEW7KeOu5pZcWpbnwuELxTfreONh2f6tP1Kd8
ZVnxVeVOeDIF9+LDVrkGhRRr2ncuLDo3ywqbx+6+MRucL4jDUsXq3HxJoeeUJ688K9+stJ1s3rh/
bHll/l212dnC/vDA4P95o+OPPtEvp+vRC/JrnGYwEvD7jzS233ZkHNt1xPAP05MA6D7iLyzMf/S8
bLwtyy38XV3u3vd6K8/ODzfa1Lzx3bFL5hXdMs8tGg0NDwz/8I32FxCh8Z6Lqs83je8fMa8uT4N2
fWOe//vHzvKzyq8qwgd3Y0PD393V/scgkOQpgRNKqWkPnV+4yG21icAbHvL89xuntsOeweLYvL5I
6RoayHCf4wZ7oWHPyA9fbRNtgZoYL4q3aTQ1MAIgVJuN7T1vjTnONhrmW5TGKZUJ50+dQOJQKI2d
fe95s1fYlZhf+VeFpSkQNhsh3vDdJkwQIV2+JZUQIfZ/u7gqIkJC5u+sr8II2dnRCK24siMjhPRZ
jhMWkuW28yvOLUGPjY15nnq9bcsobWtEJQIOOV3uB5fnL3CCiBKY9L707qkH2tWtSGGW+5vn5C5w
Yvz4vN4/vNv6UKe2S0EDEE7OH68tLLQa3t134pvtdBEkL8T0NDx/hZeoiEZ0UrS86tsIaYFfHRYc
rHgy0QpQjsEWLUO2iKsJR+MRy1GEYmQhWj4etj8Rv9pQSVlG4aEx2uA6CzNr5CzH+pR71lZ/KsVz
x0tiPVGUSxaUfr3G/uqbjQ/0BJV487duccXXSjAGvnzZ/PUdHRv34ZIoln0arw8Rv+bS8ECoPRIf
6JQ4YxTtz7+i/5P4RWDAKM2QoscrNn6kGyOspNAaKnjUAuQGp8uK5xID/Y/R/Z5se3zgsq2HLnux
qxHaUwL7W4a3v/X+hlfbtBUMdZWA76F3Tt38Rl9nirHaYbvt3Ep8vDI59t4E1IZS7XaX2ViZAWu1
ZpQ+IXdmnickn+0denMIjq/TrqqESQYNhZy5hffDWbc1pXtgrHksmJ6efu3ayjqTEp9vNMBmKMdq
zEkzYiNZeY+tyId9xvDQeJtXqanMPcdpcosLVJrRlG61152Vm6/42zx+eA5SUV78EB7JwPGlaBk+
0G/4v0hAqLD9Qe0qIhhzXbgeDHq8fdMGW3rGVWWEXHEWZq1wmmxBfyMasT6yKt+m+J/6Y0e/alDa
gzJZNnzlgppry9NdxmBzt6fNG7RZbevOq7g1FRXqllbdUAn7jGBb73gg3Q5bBy1ZH7mkcgXsMyZ9
DQOT+TnpLrUC3GjMsZqXwHGREHakGJfPq/jushy45IMz27whV1bm/ZdXXgKNG+w//kwJXH58nvGj
fT7FbF6yoOKRMlikbHH45WYNr9pSYJocEgpMw5lKZKPGlLpl1fcuzoSnFbANgq2nK8t9b131NRbw
SUqB0+xyu9aVp/nGfMN+xZbu/MZl82CfMezxjcEzO7fr3gugN+R5ygGrffOlFedQf/vGx6YNLnfG
N9YVFgIWk9FtNVWU55zjNvYPgQWDy+m696ICp2oBHsmCEOZ9fty/nLNi/i9XFn6lOK02FXYG/n/e
cfyS37ZsnxIykCkhHCkaGSBSbBX09gbGP1SKHCkpISIHOYo/CPZl/ITmZuAADHp8WoSo2xVnUbaI
kCncZygWLULatQiBJqjXlBN+2MjYV5SkwUi14XRw3ry+qg7CXiYgXblbP10M+wzf2HjDkN9kta9f
MfcRnFBwRO/+8doiHGhRZbPb6y6svtWhKSNsx+bLy2rSzYGBvv9ogy1IDAaU1ZqjT8gloVoCLUgx
uigmehEtL8vhMYq2Kd0uCdEGa5v8Hzt/yXuUy4aEsixJQrX5l8cP796P7hsKKnbn1bASYvuhq6uc
EEoNA7QRBJYR5kt6OrynT3CVoqxUm9lcmg5rXfz5O6mo5yUwMQPk+aT/z8z4gZD4aMS/OoMiPvDL
rmoC7wNUMQZ56Ra4wvj8AaxFppzLoiCe3imh6cfeaRfyYv1CK2FbUKguL/3JMpgxmLqbevcK+03t
HQ95LSPD4+FlWrN/zTw3XOSbm/rhJvKpxpG681xL5mY5T3bDS3p56bgrbzt6YuMRHzRy65r51+aY
z8o1HrPH5adsh8c7lEIp952TC0LNR0/eiDfohttWzr0Kr7rhSwI8JLpzR0d9SKmtKv2vZRml+Xal
kY4QNCP8k2JUUeZWFdzjnDIbFXiCP7cgowKmuhI42DX1i/Hhqy7MWljlUlr7AOp1VXhKf+A4Atp4
fsUSq9J2vOWxXtsV0qb0Lfk/Je2yIsA7+dCvG7bjpVD5yqr5N+SbluRblI7Uv62Cwwr/UzvffwxO
jCyOLVeUlYizleqyPLAc8AzcCmcn0JGa0v86K4Pe1VCCirgnDWx/5f2Hxky1IfPXN8Cg+J968fhj
Q2h/43nVN5enfeWstBeOmXPBmnfwsp0dwC8sKXlqhauoIE3pVlT+C4JfrPFbhmVsdHZ2X/Vb3++u
KlG6ujbAq7hW9za0rTWaYvnW5bh33f5Kw0Nw5qQYv3FRTV2O7UtLHFvfVl3dfPzkjYfGFaPzuc+X
wUHCwQONtzX4FGf2C+sLbFmOWmWonvwj/F9YnoNP94a6173YJzDYNl9dXWEyZYeUzqCCMaH4n3ux
4ZGhacXm/GVdWb7dUq4o6usj6HDcAbywr2Vpxpz1Wab8/Kwb4E8cIB1u7nuofljcUIpgNtpvW5w3
AVfxYEix2ZaVOnEP5x3Z7oX4gfkicuAIg/DJpgBESGG8CJn8xdjwVZ+CCMlQWvpAQYuQQaA3nl+p
RkgPi5CwWQFJZMDrbmr94rt4AHfbqvlX5duuX5y2/QAdZAEK433L88DjUqa2quS/lrmWnF20/GTz
wrPzIAL6W9quemcEegG7wG9U2a5Y6Hy5C1vy2zIerSsC9/a3tV+1R4QIssFmeH2gsshxJgEGzCER
QQg5HyuommRoBxalm4B9XHmE29FYjP/F85hwQ4IKZx99/IjV/8eTY+csyzivIk2ph/UqbS28uzbU
u380oyZLdCUU8sOWPgWevZJLlSmITEpWa9z5+8KeZmfavK+VGJ7acXyL2P2Gw5WPUSL+ObP9/3GP
n48Ifi0y1bDUPsSyTAVaLCgXHLxEyVhUlw+xRlCXUFKsDqQuSkhqKo3dfduPjqU5MtaV2PMXVH9n
5Pg/w+nH5NT2zil1YZJtIWG/rBSuo6GTQ8Fqh0UZGR9WXK70zBsd3Y/AZVVcdEsWVG8rGKvvHH5p
3/ur8bgYdjOQKSq/a/il/Q2rR4UoWKJkMGYAPT326GHxIMAQemRf7yWXF3HkDe/3wj4DINW3e4aX
ZcACra6YqgXVUtSHLcu1nia/WuHf/fZJ3AGM9R/1Zy3Icl9j7NsaSMe3XKfHnmkLFJYU31xihm/W
bKz3KUaruPyHBCbNMHljemLT9qPlFqOSZq/LsFa70852wyZGJLsZsPm6ex4T3wBSpjw/b/HdW4l4
lxfhoceB4z2wz8CONHQfXJixhLTgiAcu8kP9D/VPK4apektajuC7czJvEw+NFPEcIR18HggiKnvm
yxtSj7R7XmvtWf1MG46U0any64A/IvinxDBTA1puww6Y4KoMn7LRgWklNNWSlw27B19vD+4zEGHw
obd71l5WlJ3nLDT4xP1aYHcD7D4BqLdlUsk2e34Cuz2wM+p5318AHVFfptCa6mxtv7a3K9ugLM9O
q86wV2al5cAmKRgW8/X2PwKvMUOa9LZPKvkpIbSgzgHaH4B1/wOvHHvWlV5XlXl2blpJugkOkM6Z
V/LzPNutL3U3Ulsp1hXzcomkPDDmefiPnbgXwe5q8S/cjgKSgLMgvQgZ1SLE1Lc1qEVIe7CwuEhE
SK+IEFtEhOBlQNvWYDOQxn8oHg4C9ciBvsvWF7hgBNVnZoAtJRunwPgPxV4EoNY3db61wLXCbjvb
bl6Az5X8v66Hl5mwF9sPtiq95pZBr5KD+6gltTA74ESzW91nYDdjEjBZT4UrYmQ4IwK/9D+XIH9q
Oa+hhiCHBCsPFkUh1v+qTALYPpr4oYMpKftaB/uXZZSUuQph513sKlGUoyeHOrPgTeSYFDU0gen4
8xdOU1NQ1AKHiPS2HE6EKGWNEcNWB1r17Rnt/497/HxE8MeGkIhc8c+t0RJMaxnuW5WesSmIWhs8
spdrhODD67B1VW6nd3x7p4+e+GkRGjMNgDEx9tDhUcXQ94Kn8rsL0xbDexhtg7hiQqJQJ9eIQmFJ
FtxIgbV1F85dhxKUjOsWuh55a7ixteO5Iiscqrvc6avgb2GxzzN83wtte1vaI/gLFJVPPQLLFls5
rrnasTPwxZUVD3PU1kUtZFjE761EJNl9EqaikOhv6/pZ6xS8OmI1Gianpt7onBCXH1hGJ3e0+RZU
2j5TZn5hKhPech0+NbDXYHloaSboBSZN95ydZ7Y5cFG3pv/z0tzXGvu3esT2SPX/9PyiwnvPznKh
NyJSdYYNtxWpYlCwxnCox6uIrcYk3ukEG3uFHaxSb320i6vim/Dj2hIKVRc4xEGTef1ZeEWRKT3L
UR1o/df9gw8sy0y32uC9kyVVuV+bntz+WtNDPZ5Ifp7Kh+akf8CQbBxo4MPeAhoVAulGLNI3G9RL
Ji2L4hwCquDK1yF2HIIGU2JnAIXQNN3DhRvS4vDqJWUbSsShlqoj3osQfQRGAB6OQJtY1KqxKGIP
GUCk1GbZC4LeF4bHHtoHO0TAZ6qbk//V2sx0d861uT33w1etIU1PPPVWzwCu1EYY676RsReG4aiP
jJJ1zaZsSOhBJiJkEsJDjZAubye5S5naccq3oCoyQkImLUJSIiMk77WGvq3wJInhx1PEyUl84EIG
JwNwNARTozqEX9PFRAi9k/igU42r4P5+/4oSw5RhegRcnTK2F4+T0KgSmNrehk+MqmkTivqKKcv9
ldS+n45r6sBS7Yj+Cj3Nt6ygJ4P8KP+LZiS8aPt67TK+Orq6/scGdO2LEABIQihc+Kvjh0gLju0b
Cq13O9cbO5SKDJgarzRNWvMJK3SfMIchi0EEZkgJjETOUzl/tZkJvVPVNSu6/mF+jvAJ45+R/te8
q37q+ifK/+BPMUARvmIyyIei5nZtGPTjk/k5wibjf5T9H+VGUaRrq3ABuBXQY654hn2wEKVnZX3F
2vfT8HNruDq6/mEZvK0XULYd2wJ8+EqQ9B6oEZ1iv+/CgoLRvr97Tyx8odCxfril5O9CapIkL5q9
dh5efPu7B/eNBnElhWS2r4ZXFkqyLnlr6AUluHnPic1m00VFGRcUuc7Ot9ucrq+fNfjF98Y3723a
bDReVAz8jLPzUwV/4ItHybQBVmS4hmWLS50wqsLVnlkKHmSauCjDcELX0A+YJEFFLe/oGtneJS6P
IBCOIazefmzgq5VFleXZd0zDZT24uxG+kWFJFb1Kz89aD7sPNZmWVOU5R4e3esT9NzZkUCwZ9y7L
Al+0dfS/3u091jVadXbNDfhIRd3/+SZgEyjgGpRsu+oqhw1OPozlcP7hpcu/1gJ8Cvwm7WSkcXDC
p2TYvIP3vdLns+B2xhsIwdNfZcLXCG/LtHZd29I5Pz9jbZHznAJnttVad0HR9l+3tsTlP39K/ZoG
4VEdBXs40RE64aAqI+L34UmvdLTY1U36+4nhnzoJPiCasKvWqBCdr15UdlWJXZme3Nc0+F7/xN6u
6X+8rHoJ25yJ/lJzkFOSrYuiNeM/1hbbpkdOPqf1IhDYfrwjO999Q66hBN6r6BGDEvS/3DlGZ0Wo
ptpQ/R8R/7JnGvKOruHt/F1LFiTbjw98tQoiJEeLEJgpJi1CsiMjJNc5Ori1EcCE8WPYmf9/e28C
Hkd15YtX74vUre5WS63FkrXYllfZGBtwwmJsBpyQ2MkfMgmETEImJMwkDzLD92DI9x7zhnmTTPI+
/pkw82Y8SSaQiTO8PMMEmyyQAA4GEgw2YBnZxpIsWfvaLfW+9zv3nqrbt6q7ZBnbYMO9n3373HPP
Vr86d+mq6pK1CZ5XleE1Ar7JUFg5HdBNo7GZ/ZKB3gyCppH+ZDJnleh1PotjhVnqyeL4td65xpue
CL1IjhDuuQw+Zaq9o8X++Wvqn/7VKNkelRZ2sNCFcZWR4jtAAZsaW5whTBvZHU5E2AsqGoI2odLM
P2gbLODszJoan8weWuXDVEnyHcQZFwaTQxO0Psv40VJeqigUfnkqAluNq9fUSLUmKTS9G+6sMYc8
QVWUn6GRjvLj9OeneCU1jV5pfZbxM7sXKf4ifoaATLzT/Ae9coV8vZcHMo5bqKGkZ58ar7+lzvLZ
axsPPj3cJQ9dywNX15Nr+JOTu+TfTdEBSEzQQpIViu3SugpPnWl7V2QvnSE3N9Ev0iBG7Ej1NmM0
laNfJKk4uLdWXe0Fv8nv7x9+hkRD7RjMD9Wv3GBz3rzMVlPTfkej+Q8vvfVXfVN7+6bcLYufuqzK
47Lc9uEVhP9y91+dnN7bN+1uaaZ8Gzc1ZccShbXuyi91OA4cJ1cPv3hJDUQTBRdytMBTaJnDTXMY
C9TwD4qMAwkPntJQLHDyxIJBioUOhBu2Vvu3glwi+NgsCKT/5Xcn600FutzCs46+By7zm/PxH/9u
5MVQSt6pUPzdHgeEl50Zu+3laerUut2H28F8OEL3f3X+7aYgeYyjYPl8hwzswfHk5+sqL1nqkcjz
pgZ4/8lyuJYDKxIErIROooVmLAU/HbE7nLXJ1G56/6Zzecs3Ot3R8eEjvc7HrvQlx4dv2B88MBKS
DK4nPtUKa1Vd46IffpjjS64n/pjwHWgQa4oOqYg7bgMKrUJhdCpCbofV+T9lCu6mX7G2r/RB6Mlo
vLiSEeigYI12MH7KRuRl/KV2H7lUdfRgzz0DdIfiraYPsdCQ5ONV1huCAGdBbhDfsLlZaaz66/Wu
216nyQj4mx3rXER+aA72c8rujB0m6rIANfHKTfggxwyy5DdKJGDKgDZvR86QajlD4CFoKaubIfCs
LK+LEBkrP7nIeGAYrnYUPrWa/PZnOgk3yDBE8JiPAzBG95farXf10QTzVG92Q3fqWCzjjRbWeu0f
abPsPZEGY0tb6m5ZXpX1pF4cJOoTM9FdA8lrGpctq/R/c/XsF97C37Cr41f80M+S/MdTyU4ZCKni
55RVMjRtcP4hECpZpNEl0NKCBGsqbAI3CYBiQeyUw78oDBQnj4qkBjblQw1FEwNh0aKSObv40Smx
auiCeyjr3K1LyZeSo6fgiSiIgYZBQs2TrxeWiq2OQg+Zz6xXyG+gMzQ0LCo7fuHlPXBrDfayixwF
SXXLVnOMZxc/cYGFw/Miwl+JnkCNaQAcEf87y/8imEUKlzFs46Ckw6wg7Xx5+NqbWurcvn/8Y/fQ
ZDyYNy6uraRX9bM/PwTrGRR2HnAYSPSFVPA1PvTczKKbqu33bG9fd2zWWVe9qRYWhuxTb8zCKWxf
vPhHl1dFx4du3D9LpwFi5poOP3yPT07NPMOsAlHI/d/e2IZVFcs6ar4Pty0bqzZdufzhnunenO2a
ZXBdUXp7MHpAit0B/A93qPkRqQBzLzEBRv73wcnrtgSWdS7Z0xQNWRz0+U3aSeJXCDJlQCTIUVYp
6KRgkFomiBD9B32KOnwiG+VJM//kycjWdfDouNTfM0N+KgnPJE7H2FutpEgc1ntPJvPiTLL4jZla
Ua4n1f7LJYXXEqarlwbwJw9m+OVkavaJkbrPNwKwS9adCNc3BVbK77I0dJ2c7O+sbIUfmm51Pj+e
v3oVWcjJDy3JmKHuMURo5iK/HMmCka/dtOKK4zNzFa5rmsgFpyN94dHJzLjkq6tb9MTVzhcmMyta
quEBi2w0/uJ4oiy/ixwWX5gjZesGTnECTYZ+PdlwS639a5/s6Dw2I1X7yA9xpNzv3oZv8yb5ygzg
SRA1KE1qDdXhARJCFKeAvpm0VGdetrbtfutM2l11fZub3FqyOD/klLrgqLEo4cgGsal0wm760a7w
d9a5m9pbXmjO9MO72IzW5mp6iyoRehJ+Nyg/VUsVlDCK2oTiTjyJnBaSQjRU0lIOX3ZdjB/OTTFD
emforTepayZGH32lYixDpsnVJjSGn1DjEW3atPzh41PTLs/WRrKv/PlhcvFMOdjsvx0JbbrMu/bS
ZY9WTx7J2LfA7TfYjgxMvSDl3+ia2XaNf+W6jkc90OW4filJ1BeOhmGHSoyTHVLqngPTT13pb13Z
fOfJ4zvJkgaFjx+PkR6Y+ohlVEAcj1o+dqVJDelUnE2tLrPCq3KOOZKkHBnOVEVl58KO30Sv8xkl
8iLENPwOBe6hwFEl4e4JRZIdSfbNUG5tnfmWP1raMhirW1Td6gAxUkYn58qPU/h2Ry6Fmq+5avnD
J4bkn6+jjqoGF4ijcrLQJ8gsJP9RG4UvRvxF/OTcFVPgrMavKq/kBr3oDJkkj0yWXLAQhD/9i/6D
MKdL5qZa99o6ss+AF5P/E/78gaijMNSUyOfJQ9HUzsO/63luMgVT/9bOBrLPyCSeeOEEfZhRHhVZ
8tICVIdP43WL4KnGwqtvw+aDTQck6Q/0TpNNjcO9ZnL4sSEYLua1S+tugnczGAv9fYN3DWR6Bsrz
QRfGVpZ+gQ7PTG59fnQ8U4Cb2fC4yImRKHTRIgcQh5+tkrAhePJcFdFCNIgQBqyMQByK9GkPooUF
haEmhBx/14npIdKf/GUP3DxCR7I7VCIx5OnNDiBkXUqkQv96HPYhppVLGz7fGWg1Jw8OkW8iDXVO
mEB/9HLf01MU2FXwvoT8OLzgEh6JgUiy0S88M9SfKlRWe7av8nngp0NyIfHTg8JDIPWPXn4bwIQ1
ZcPyuq3kxQzZw119fzWSlbKRv3t1Ch6m9Nf5buoMkN9JhmcffH4Sdicl/BDhQ1EdexFzxSkRwQ3c
zhd69o4kJaPt6lUN9Ae/qef+QN8EIBXI929SKIDwgD2QCrQy/nl4dKMYP0i+0D24P5Qz25zb1jVt
b3NnZ0IHQ3CU5qW18PYWPIlF+aJ96oZVB04MPHBoejpTgJ/1tta4l9F9xvTk9L1PDRV3URAJbkCh
ZoRsgp1WPPU0aAREzhCaD0QYginGQ44Utp4npuQMOUGfeZVzoJj/5BRChhBh5ojYgkKPKDueMK6F
Mwj3M/NJGF+7yPtBGJhSz8DQA28Go5KhtSWwfWlVpVToHxi+/VV4wsoQnhi999C00gW7tOzBrr4H
4S01tGTgPlehEB4d/fEIjH3rJy+DDWeZ+JWoiFOiVxI/FcCj1saPjmStoq5iqthNKQY7I2QBZhbx
l/OHdGJIhIIAsNbiT8OjnRdI/DnywI0EsyjUhcLjJ8mVtuRMiF4FNKQgS8lIJ30/OjB4At79Z3Ns
WupvdWSOjhM9OgmUjlM6fqXCM70zMLeaLda1K2o6QZoV1bHzuDEJgJBiCDUj5M73F/7K/EMO7mLM
nws2fiWVDF//9YnXw3SyU1jaT5Op022B78+JeLqLvzGoldO23TbrCnhPcjZ3IEKWj3NQMJJsfiiS
pnegFZN6fNp/w6qWL9al/+65UXn9CDS8cI0/OT50w/6Qon/hfZosl7tNiWyuqxx0bptlhdOUiCe7
lN82sgOAH+/A/ZahkBof1s0T1AX8+ZZjkTRcW+ALvA3FZ84H4/Jf12NdenwmcHrCZrkcItc5rtOr
qyUanNYmmzEYT+NfAVR3nkHL7bSsIK+Gyw+F0/Bb2YunGDu9Vkc2dyyS0ZxB7hCoDBxamZSYp4sz
IMgLEoEGl7XJbITXtPSUZKzOODU2OA1w5xqfQb8gj0kE9X5AYL3b8Sct9vaGqoqKChN5jSEpz+57
aQFbDZS9aOvbrl51R50pOjP96FtzUpX7M501fqN0+NVjcFHkoj0mEbhAQCAgEBAICAQuOAT0thr8
sxoXXNDnJKBdB4euu6Gltdr/tWvgUjAp40NDYp+BUIhaICAQEAgIBAQC5xuB9/9WQ4qHv/DzrssD
7lXwQs9crnsyekC5e3++wRX2BQICAYGAQEAgIBD4AGw16Ek+MBE+MCFOt0BAICAQEAgIBAQC7zYC
3GuP3m3Xwp9AQCAgEBAICAQEAu9/BMRW4/1/jsURCgQEAgIBgYBA4D1EQGw13kPwhWuBgEBAICAQ
EAi8/xEQW433/zkWRygQEAgIBAQCAoH3EAGx1XgPwReuBQICAYGAQEAg8P5HwNwXTu6f0PwRHs1h
wwto8bW+wGfv932XZfgYeNd68fAyvK6e/PmW4e3zsenFw8vwunry51uGt8/HphcPL8Pr6smfbxne
Ph+bXjy8DK+rJ3++ZXj7fGx68fAyvK6e/PmW4e3zsenFw8vwunry51uGt8/HphcPL8Pr6smfbxne
Ph+bXjy8DK+rJ3++ZXj7fGx68fAyvK6e/PmW4e3zsenFw8vwunry51uGt8/HViaeKrJJIH+TSlPw
x65gCAqnBi+Bhzfe46vgkcAX4Kv48K54qiSbRCNyQ+Hp2JE1qQoaQW0SAqigNrKKHbwzxY1WWZZR
xUkPRMTPn0eBv5KgStpDW+S/MqrYp944Evkj8ocbLhQMnKhZ6iBPzP8fyPVLnQXY4m+gIChQ42JP
a1z15bVfWeuhSTjyn+LkuEp6wSdMUrhpwFpjR95NUEPMFCNIL+wPqAsaDrGL0RWp0g6UoHxiSsRP
ERD4s7wgyQOFtRlRwhf5I8YvyQ46C2nSROQPnZ7F/E8XPmURLMXkg5s/OJ1qazO3hGv75DbbMSht
+dMAmwlAmw5EJChJ9gmkiVJwJlgDCSrEkVQeNzegqKyOoE3slOMTw9SILMN8kY4yhbdJupmuiJ+i
pYezHl+FIYVTPtfUWmkl8JcHA5f0HKmb5wJ/zCWRPyJ/dHNABWxl6gAAIABJREFUzD90OSPzCV3O
YMiQeYOtiRfA+qusCNzbQvnpT+kmn6rQ+Q52PArBlhxG8ClC7ChbB7WZYgsVmbqGwKZenHp80CpC
X3RFqLL2eb6IHwFDoAT+iAarRf4wKErzBDhl8dEbp3p8MCLGL4Ip5k/AQS9P9PgifyBt3s38od6I
R3WhWw3s408JyWnlWQ1+r6F3OlXnnzPEkXSfwdkkxw/dNHVYrZKn/XLcvGM0Mr+uiJ/io8JTjYnA
n2Ud5tg8WLG1jk9Dkrus8B2cIY4U+a8MdTF+WdowQuQPhUI1XsT8XzIx8WnCcocQfAcHIke+e/MP
OC1XzGS5xz7N9qK4FBl3+KwuSYok0nuSeTbrqo8Opg+wQw0hAfUCCyghUCCvFwPZ9yj2iVmMWO1A
T5dEQtVRr+iLmiG91DKzjwTyaedpKhE/AiTwF/mvlwNi/MrzDD/XifmHThxi/nyfzZ8wCZQr9FkN
uY/7tkFOv0GyOvdsW3J9SyX75UokNPPIr3runsnJpmSb5uc+f/kW+9QndvbsIR1w0wjTB0jjnlsv
2+7P/uujB++MUPvydMx9w0YjBWn7ymV7rquZ7H078KuZazvan78hoAo4l48k46+9dnJrV1RvvJKd
Cu5CiH/Tnls3Etc/PnRnWLGkmgqpGezBgEkNhY9fZpAPMl3SsIlImfipKIehvIGih1eQvryq+Tb3
3NV/mFMmGNnX9pXL91xX/cqzr206mlHHb9v/pxuuMs184gdvU1SpeeLXtv+LlP/943tk/CEeCvh8
8ZsfuW7x5Mt99yUNO1Z2PLm1+sBzB6/oThGjCv7zx1+UJAgX/uHjG+5uNe585NU/ixi+99FL7lri
oOpylc3lQqHgI8/03Bfk2WrcoKcg3X/Zsvs31rhMRGxqdPybe07+Q0aL//YVmBgnAr+agrPwDx+/
9O4W485HX/uzcOF7H12vdp1PJjMjwxP/41fDu9T4EwcyXBQrebcKLGxCN3fuCA8f+CJ6xcKfd+Ce
Af5nmz8kBhH/+xZ/OtgrionGU5H+3h0nqp6/oYZnZtOZUyNj9zw1hJPA9z6iNxCGdrHMEfnzvs0f
OonNN/+/m/MPBFOmwC9QcLbFCRdrmOuB6e69Y912ss/InRqdOdA/G8pJLm/1XZ+9ZKcbxNAc1OY9
N6/f4pakvNEls5WHciXD1zet2u6HZcRoI+lOMx1qdr5h8cadB9YS+TmM02oE224zPkSSC8VS9F8m
KRldFZVbNne+sspCjwOsYeRYg2/WJC6+vmml7Bo9Yl1cTlj81BhrEaIYP9e3kPg5VDR2HIHvbW3a
1OhUIodPJX4zOeoKMyio4odmBUGO+mWHQOO3AgAWI1xnUvwpn2BD41eR+d7H139hZU0tKIIpWpwm
wFmD/+ntUFW0QMKmCgUJTEGB7QWerGRGMplq/DX3frbzQTs93er4qRYJ9P7Na795Bewzcn0DodG0
VNNQ993PNJNePAr6QYWJfaeVcEn8BeoOCIifosdcR9KS3W5rX9L8kztXfL2MHWIATCg1Axwswz/W
pDFDk4XNCBADmgjTYOSaaxF2afzokPpFUxA5EGeFP1hjAWM8rCnip2dBc47IicP8Ub4nXED452PR
VDJJ5zq4ckxLhI6mSDIXTGfdmOdSHodYJJ0zWy3trc2P39rUCcJwIOoxyA2ElWQgkII1EBQHUrOE
EfmjIERAEuMXk0UHh4XkD4VTU+GKjskHMGPyEbh3f3pFu0nKhie++mjv92Ul669vXb/Nb/v89Q13
Pj4CvB2L6753Q9ti5aJHBAczdKA9X+ODG2EPAiVPvz5TEis27Pkm61fsRPr7fE9NUTaJbedHL/3K
Evula+s6u4e6igcM/SXx+xp0XKMk1kTxwa2X/PdVJnLRBa58KH5le3I8TFhukw+9+LV8RSWbz0hS
JpWl5xAMItTE0N6uo4YuFOPxB5kCqJQU4Kev2Pmywldi0/NL5IhMklyHyocTpI0lk8OLKLRVPHBq
sNhUpOWAIUIoIIME0pQnSa//7tCl3RAy7bJUHvqTzvUVlZ9Yan2gKy1LkA8MmNYW79c6KyUp9eiu
g7cHoatq4K7Vi72B7zlO3c3FqahwNhgJcVJLr//u4KXdgC0pnYHA3puXLLZ6v3GD7x+emUGmAjgf
PxeJHBX0ArNURrFBPnkt1gQ25ZfBjZMh6krRyqPZeezoxcbHoyejOCWfvDxrzuOXkyHqShHxq5BE
VM8G/8xHfnZQBtdSE/yzZd7kzI5/O75PwXvHKnJJAy5vKPMh5Hn9s59uq/EH/tQxdHcCA4AxqDcQ
YICBTGluoyLWZxM/tSDyXzsulPNHkP/g4I9pxo5dJvALIk5BOHEDIgXJUXNDAL5TZ3b9J9tngEL6
I784FQGu1bKDqDv+fgfZZ4RGQ6OwklFLslXa+8rNLS4pMxqDTTr2kQg2t7cG/+yKY5u9St5zGqUk
bNVpOCSkgnTnvmHwbnZX/vnm1Yk7NzzXrvxStyB9e+uaxJ2X7G4AR6BgL3Fdaho4JJ4qJ3zTpxdd
5HGolby2oy385Uue27ws+NUPF+76cObOS/ev91Ahon7/ZUsm79wE/MJdm4KfXnK/fBuBXOkJ3rqy
69YNROVL60ZuXwIXIVyty8K3tlLoIEhaCtLmjrbIVzf8ug32fAB71f5PX5K560OgNXLzsmWwh5O/
4cji9MO8++YN4VvbdkDAjureL1/We0PrK7deJsfwuWVKDEWVB69ac+8SOEzLl2+/bGBrNXY0rVgy
8GUa+Vev6L0hQL4bYXFXH/ocCZtE/uW1u9usBFH4jzX9oCBTaeU4oGEx4ekAVkHKRB4fiAOzuqbq
uVsvS3xh+depOK0c+z93WfhzS77UVtMgSafeePv2IKZm+PY9J/7jpb7nVfuMopqSMCgMfEaAazg6
uXRNTLT8YgT2HTUdi+4HNg3nNPHPL6NYLvnEAKBmRImIisHEGKHq1jYQ2/ljW4iM1i5rszAYwbrK
EkyMEWXFFOZCYluIjGKv5JOFwYgSERWDiTFC1a1tLCS2hcho7bI2C4MRtMshz6SNTJAR5NIFCBP5
ronJ4/Qlz7Zi7qsHwjg/EOYdv3AU5EB0ZJh3LcHCZoRWQt1mYoxQ92taC8F2ITIas8UmC4MRxb5y
FBNjRDkpxltIbAuRYQa1BAuDEVoJdZuJMULdr2ktJLb5ZDTmcBMAruEf7MiwLhQ6ax2waGYnxm5n
Tzmg4tyo++GX3T/t30O2b6lXjk89/szrvsePD+EXcGAq27pv37Dicrt06rW3dw0rX84LZNl0Vzi9
FtOSarsETbDBYuUDY3ZyOWVkkQh3LPWSuwaZ9KGpjN1q+9CGAOmFYnDdtNxtt0onQ2Cz8O3r0fXx
omsqRSolPEqQaOnXfSkcp6EwvyhGtdxmq8vu3NJZ483EXx+MSlb7VVeuOtTpgPjhisg3rwjUWKXR
kdnRpOQNBL55xyXfBuAKxkU+h9fvXeMnN47MtkI2h8eZz+bUewe4VWSyVppsjZWwTtsPfW71VQGH
ORk/PpFoaPDAdkxbSGDGNr/N5ba4ADuzyWe3tHc0XO43TU3HIzmj11vzzZtbOrn4wUJCyuNX/kwO
CPkc1TRUL7ZkTk0n4GZHe8eS/9xEb8i4aoNfWL7ea0uGoxCD2V5588c27l9uJWEg1JqAOGYmmyYy
Coar6bHPhKLjOaPdXf25VdQIpFZ7/VVeiyOXrPQRcBImzyufvjTz1U2Zr27859bCZw9NkwdT1PEr
PimGNIsIB/NH6ZM/UXFgnF5JsS2D2zcQEgbJhVpUYl1AgC7WaKRsDKyLEIgkRwCTCRR9KBRGTsLG
zC+X/0wdCBYSC1KxVPxkXUz4NDEghkrkxJ2In2KAmF4I+CvzJXyt0hSLzbrDbNzhsuxwOb535ZJN
8GxHOv4SuRzLBLnzCynBBgJMSpgqTBAJkT8i/yETWP6ck/zX5JjSxBsotAU3/KDQurXKBh3JVEo7
6UMvRIOSUv7235ygmnQVUXRBoLOl9S87HFJ4Yvsf5v704/ImHbX29vQ9GHOEJucUI9SAZhiAferC
VRv49VVOuA2ZzkqBOu/lDeRZh76jEz94q3Df5ur2QO2DlpEHMtK1HQG415McHbsvIRHXy9F1WHYN
ATMolfgf3Lzq68scybTkdZMvBbd//tJbcpLZKh14rusjvRniHUFnRGzqc/92YpcEvtp+c0P9+iua
dhybunMVxJN5/ImDnxohV27gYsPNDc7br/be94z8N2VOdR1t+V3kNp+0K+wJ/3mH1N/j20sebOQw
pIdPqx2rW9bbpWxo7OafnISd3G2XrvjJldWSUVm9UJDoShnizUBmoqyBnr/Uf/zs9c9O5OEix8gd
yxsqHJ0GQxcX/7de7Pa4Nty7xPjIvx+8OyPtWFVLVMMTtz/aC0e0o3P5k5urGwNwLJFHbmiD/U3f
G28teXEOZDrbWw7c2HjVlc3XHu/Zx6BgBIak1CvXtO+pTlpNUlqyrmrxt7vJVbFDA/Hvzk7e+rH6
ztW10ltDcOx/scYPGocOjS9fVgfE8s5mqOG2tKvCtryzI+G3OXYPl8Ff8UK6sAChkKxT7jWkh8P5
9X4pxYQxaTlMinaYMgpjzcszASCgF7uQyezr6fLyvAxR56JnpEYGmyDLx8PbxDCw5nV5eY2MiF8G
hIHOnQoeQxB7T/CXZys68NXn2h5ofvLPyXhh5ciLZFLiUokeFAubDQQ46SBEanpQfA4wW/yxowDK
M4FS3aIjzi+vy8fP2yc2L1T8Rfya0wrnSg8Tch6Voj2/Cl/5pEtVaUrRbnl7zacL8FkcvHsiz9Zz
139+rNEsJR7e1dMlGZLke7wxBVfFUT6e+OvehGrK1tqhkhhShWfbJXi3ggYE19t7T/5/vw+D+hM9
iXuXOz+xxv7AocSXVpPV6/evT0qFyqLrAjygQF0nIafZ9kiOv8rlcNltLuUpE1eFg36pl2rtysZI
dih/HHltYBeNc9/x4a5r6tfb3Te0ZOH2aXJ06FPDcOkFhnHuU88Mhm9vr1lUfW0hRqHLPH0AbpEa
dkFF1l24vGkqHjgeYNFLYUsbPLgAa/ApesVI2nVo4C8uq14PLC3+io5iITkySvYZ0ExEhpJSgzFf
+n3ITp8as8GXm7S8d+l6dZBMUpK0p2c6srnaAhAV7J0+EqdkqnhkY4XVYEhnjXAg9gr3J5yGfXAG
8dRTHIgYFKCV024P1GwPIBfr1PPPvnX7jCQFx46k69cEar9tHb4v472+2SLlZn/0drZ9MZwdiCf6
8P/tujtYkGobgp9p9TY0/TQw/NlJ3o6aVo6auOZnK8Yn4gYvuQqdK8pg5Hz8Knm1C2wxAS3+yhQJ
AthFHKq3IOXskWDKyvN8XpG3CTR6gVpPntdFMeTwdoCDplAAu5CJZlGlbM375W3yfF6Rl0GnWOvJ
87pAgxgW3g5w0AgKYBcy0SyqlK15v7xNns8r8jLoFGs9eV4XaBDDwtsBDhpBAexCJppFFb06l+ob
T5BHoU1mn9vptUprtq776dShz04qvsgoVmhiXBkI6BTr9yp+3i8e+Pzx8DIoOb+8BjQVDtr5n8jq
xaOxw5p68jyfCQPxAY+fh4LSdKuBp5Dr658jTzA6bLYiXvKZMz64NlAVDf9bX6yLh5LoylPwt29Y
BtcYpHSq5YrWX0tSC/nZg/HGP2rzn5r47FtReaRpTo9sXIkALNOQsqGJ///laTK0LCZ7IfNa/+wu
WPBoue/Nyb9cvngNfEE/NLu5Eb5Khx45mfv2NsX1pnKuFfPweffe1+6m8e/85OVfaZYeffRV7a0i
FJYDy/2+P6VAkX5tMrO+2QjjHIoZBbDO0vsUFksjIpGLvZ5QvkkoF0XRarGmh0mbhmQalt7cMdy4
EFYer16ohkRREwcPmVYyafrb46KpopA87zB4gQAxKmkxm5RZie2uyLOrUNo7W9s5G5JkJZd+4B5T
qQvCkae2qd6BnW8n4WqY3WxMJpNP90X2gREQKMSf7ImvWeXcvsL602QtPJ8R6hn7fqGw00lyL9Q/
SPYZUCZHf9K/6K5Wy5o6hzSZJBwoLHLWZDEQy7JrFgN1B3GayI93JMnGZJBgumgNaj0+EwACQSv6
Uvo0uqXGUZfVvLzGJjOuJ8PzFf/kU4/Py2h8sS6NLjRLCwaGNS+vsYkCoK4nw/N5L3p8Xkbji3Vp
dKFZWjAwrHl5jU0UAHU9GZ7Pe9Hj8zIaX6xLowvN0oKBQU2JyODAkqemiRSxaXoEflbWavv45dUS
XCuVCzWCpqiMPBBklRIXmhgUK6pPYocfa0qnRhedKp3yJw1bHqe8vMYmioGOngzP513o8XkZjS/W
pdGFZmkR8SMCGqwYUHp8JsAR5a9qdE1GYU13BQI7HYN34nqJZ8JR+183t9uljPSDV+/GtYdlibKh
rnLSRdjq2S4/Pkm8tS+pb3fFyVaDyTOiNFzoor2J2dn7+kJctAoJvRNjf4gtvspbveeqCli9RntG
4arDTofimrsWIrvulm9qKCbkJSRFl+kU8VjsKQYp80xLa8xSmD7wULCuI5unVJreu0jAhZNi/JSV
TI2gqVx2gh4FtYEs5TsH4zNCKlQ54FyY2uG3wXP4ZAX6VsY54l+MEQc/GR4Wk2KW9RbNMpZCQJfc
yw4Yxxi5H0FuJkm5x598c0/SSG5WwU9M7WaHlH1ljgozs6WEJA0NTD3Qq/2lETFhMDzw6tjXV7Uv
WbHo2zm4P5N77nAQmC8NRr7S7AvDBSBmjT0EW+QQA6rCuhiB3YgPMIFobugk16tSJzBsIFGYqWgI
1lR5UhrF86tw8BO0sEvNJq2yBpHJuhjB2wcmb5PJIKFpMkeMXxoJcHj7vABo8b40XXwTab0YePsa
mywwPV0Nv9QpcHj7vIDGl6aLbyKt8YVN6OLta2wyGT1dDb/UqcY+L6DxxXfp0eQxeWXYFnLf7Q5/
obUGnrXixNXnVDMQirrMiHpcc4aKJI9PkSvPn8V4NF18E2kNViwY3j4wscmrAK2nq+GXOgUOb58X
0PjSdPFNpDW+sAldvH2NTSajp6vhlzrV2OcFNL40XXwTaY0vbELX+Y5fiYS7qsGHHp96YrDtC822
P7156Uv/3rMLpElktl9/shXm8OTIMNlnyEzFkvL5s/1dp+AhRymfyBqlbP7aq1ZubzQ9/2z3I0O4
2Bs3O4wzydwRdIdG+PRS7JBPetmfZ3B0dlfX7FWbYENDHpj4zRuz0PWz/UdOVcLAK+eaIcuZUMYJ
/gKF79DSGztrpL4xwg3UrgUI0tH/7At+fEuNt7nx2+aJ+7Jk4X/w8jq4C5Ocje7TastteCpT2wMH
LhdYemNfafZsvCQg9Y0QXrV/JXFUMsxkeYq/an8kd5T9IE9gSpbFEB//nK/sXTFVyM2CO7upzSPt
OkxPlrNm8jMdNVL8O//8+r6yF2aIBVSXLHDxqex5BOTDEy+HWrcF6rdBFLGJfx4nKruGY49IvsWr
m7784tHvk/Aqrq2HMHNHhpUrV4Q5b1HQy+TgaVc5jGtrax/5KNy/k6aOn/rWvNqkEwNGO5iQip2i
KnJK+SBRllnU1Kfm8XtGNuexw5yL+BkUjJgHtwsZfzaBkPit397oIwcEj5xDk5ZMtrhxvzYQOP1A
mAcHtAi1yB8GBSPmwe1Czp/3JH7FKd1qMHQYIRVu/0Xv9X++osEb+Mndvv85EpnJGVsbPV6ygc78
n310LVRMsE983GHfTGwf3KGXS6EVVi8p1wP3PuJkWdq+qgNejhkd7HH9fEKZqfGKAiwVuFrIa4Zi
Qffz+2+M/c9NHnhgQgpNfneGaO2biSquoWlQXM/tIhsjtqirDN7960OvuU1d/AKs6peDcTW3B2+u
fG7CsHV9LWwAjh8a3hOP7BlZ8oVG571fuXTD6+OwBdnSDE+E537zOlzhNNPLA5wh+gYeV/OSkc94
/mlvz7fI70Bp4QDf1TX0PzZ52htbw5+pfGYwt3Uj2bgo3/NV8WuNy7bIR0kXKhZOwTt9JMt12zce
OnziQfLEJy1F79jO/MX+scMfq1+/+dKBxSMvT5v/aG0A4I30j9xXdp8BShoLxabsl9oF5HM/7Z7d
diWZGfu6Rveht4mhZ0ON27y+//2lzhu75lpXNa4BZMOTPywmD3FATxzUWLDJWjJ//dYNwSvIpSCz
xeKCV8BBSU7/t2fKXQ9TVOVPDJiFzQiVX5K3evmjsVfSREWMk7Oj8svyH7Q5mRJbZRgqO/zp0PFb
xsT8LB07Kr8ifjy/5wh/s0QmZaNEp1Mef/i1/NLgl1roCYP3GVro3J154uVx+rJgwl5/3cbgpjMZ
CKrzeI7ip/EpFR8/l9sqvyJ/zmn+KNDTz/cKf1UQ2GD36TV9Bikz0/hI94EJuCRuWdzoW99M9hmR
0PR3dr1GnvUrLfmC8jQiAgc1Hid8lc9L5G2YULCGxwv47/esizAz8NwirDhZcmOD/jQU7UCL8FUl
M/PbEbIGHjk83qXqgAbaRNesqRUi7Ux210xKrY6O0K8cMByCtzFw8/par5Tv6357xavkWG9//PXH
++OSybFlYyvZZ6QTTz/95o5TJPIYvS9D7JOw4Wv97JvwQ1yTqSHgX0ZnCNpVrDLZvJSZW/JYT18y
7wrU3Lyxzpvml3cWBlHhjJOnQzJFX3wXix8Iw7e6xmHhNVtt69c3dlC3cfAoF2bE0NXX95Vnx+C1
sItbG2/dSH7HOzU49Od7x6kg2OELU4eNBOFzBqHFzqlM7Do0QoGJP/EGXtwCmfxH/v2Np0dS5gr3
9k1Na9zGZGjqL3b17ZNPNB8/JgbUaE3rGi5/eSts8A/2GfDKxePH+z/xr8e/r7ID7jTxA2eeoo1/
HtGSLnTExw/WmMES8WKXRoa3A1oi/lLoynJ43ABSaF5U+Gfz5EmlPDzcjZGzGrhGzHMv7DPIu/9n
H3380O0zNG3kSaB0IBzjBkJZuMoyWSoyoqxYWeZFjr880OAoGPIXVf5cEPGXSQzDxx87/NSE7pd6
omEx3eazO+HpvkhiF7yPC2DHXNK7iMTzy3hEFjuL0ESLmNML4KtE6CML4HG+wilwpO7Fc3X8O1Yt
f/I6/4GnX7nipOnLPmNPMEFvJXCGnPYvu0zxbA62LFx2ljmua+EplkxmH2yzymKoHMKOakfALPVM
JPbJHM4XRy4wfsUqfBqvdRtnEtkusodRGVKajG+4LeCAMz4Rie8h16IYH7QUWUqqYiB9ZQvniyOZ
bqfbcYXdEE8md83R+VKNf1mLmiCUJsiqHChNNV8lct7zR8RPEeBA50iWAzooIZtT4EiVLnxLxrQB
DZE/ygQt8n+huSfyh6xJUFQDTGmq+SqRMvPnx+vcf7PW295QVVFRYVIeJHp230v0L7tSJ+RieHG4
cl4yuV0T8BfOaCikgucHwRstGB7hYa/SxiYRUcWlNKnumVVoGb1Qm6Ux6MUvL+zz6s4XPwkUno6U
MsnvT+DhqEOPp76vf4NGESXe98XJzSQKZDkMlfj3TMf5kKmC4pccdTnd+eIH16AFJb8vDGs5xYG2
9av8rgm49sBLIk1rvRiU+IlZEFRCVjXK6XaFE/INLJY2jHg/5A9ioQVFH/yyPecRf+JvQfmjOqll
o9RnivgpAuXyX+CvnzasR+TPxZM/uNqwU6cQeDWfdpLpRnnCSG/ZwPUDbcGwIU3a4PmKafIJNtEU
0Fqb4IuKEj7tnUeeCsoVCqMuiQAKrc9T/PKjqcqBQLRQ+Bgu8PgRdgKSZit5keAv4icJxxU+996F
/Bf4c9gTUuCPk+4HZP4X+X+m+S8vzRo1+gSSzCOYsiUfVybswTVJWWJhdmO2igTRlL8bkemPNok2
p4tNNMnXaARr3RjQIApR87IFzpeuLhcDMXBm8e851vu5CePIBP4sAgcZH70SzIUaPz1ZLGxGcIeA
kYv4z0/+CPxpqkF64VBVWnICIpOmpcAfry29v+ZPkf9Kxn9g8p+OZnl8cx/0qgb2qWYDvEovrz/F
rQPCVWpLu8PFh4o5P0Dy9nXtcDOSSgZd0lprR/HF88EZudxyLuJPp3bhY5G8fVVs3GHqyrx38bPo
dGNjEvOcIxE/RUD3vGuu8Ck5yUF7seY/OwSRP2QTUDpGlHPN43MO5x+BP0FAzD8Xz/wDA6FcoX+N
E/tU0yh3aokaNkuHWbGnaBytldrkTUIvukPb2CyaoNRZ2eGdoQ/F5vn1yx2DiJ+lDSPO+3kX+CMC
Iv8pDjjYeTCQPu95yLuESLAp5k8FCYH/afLwYs4fJdm5uZiQOlc1QBqzQSOug4A8lEp96KXU+bCj
54s/hPPhF+yzA9fYZ671YuPl9WSYEeZI466Uz1T0bPJ+mTojmP0zsqPnixkptc8caeJhKno2NfLn
xI6eLxaMiB8hOk84CPxZGrOU08NE5D+PANJ6WDEwz1PeMrOMeGfn8X0TPxxIucK9V4OdPEaUUyjy
0CLUjCj2KRQzBQSIYa2RZ01GKNrFT94OcLFZ7KbUQmR4FeaOEXwv0rxNEIMm1Bp51mTE/HagV8QP
IDC4GDE/biAm8GcJOT9WejnGazHYGcH3Is3cIfICfwbI/FhBL0qWijEOg50RrIsRzB0ij7VGnjUZ
wdQZwdsBJjZZLxILkeFVmDtG8L2lNkFMxM9Anh8r6C17jngtBjsj+F6kmTtEHmuNPGsyYn470Fs2
Nt5XqQXyUjrQAx/zuGFdjCg9DN49E2PE/PKaEMseRrnQCY+5YESpJOtiBMro+WVijJhfXs9OaSSl
HOaCEQuX0fPLTDFCxF+KKnIYRIwolWRdjJgfTybGiPnl9c5jaSSlHOaCEQuX0fPLTDFCxF+KKnIY
RIwolWRdjJgfTybGiPnl9c5jaSSlHOaCEQuX0fPLTDFCxF+KKnIYRIwolWRdjJgfTybGiPnl9c5j
aSSlHOaCEUQGLWqlze1u+9UFfNUciIMQKiFRqqMno8f/JjJYAAAgAElEQVTn/enJ6PF5XZ7Wk9fj
Xwi6F0IMevjo8fmYeVpPXo9/IeheCDHo4aPH52PmaT15Pf6FoHshxKCHjx6fj5mn9eT1+BeC7oUQ
gx4+enw+Zp7Wk9fjXwi6F0IMevjo8fmYeVpPXubDjoKXZjS9qiG3cGMBNT5TTWvGYxrlCSbHCJQD
91CgZvFR+4SJkvBJCagZQXqh8LqsOY88cy3iV7BVYQhMPAsMKAozg50RlC3wJxmqhkoGpswHk2ME
CvE5DF0CfzF+y2QPl2cifxABQIkfO6wp8udiyJ9yMZb7gxzstOK5Zk0gYDUisyXNBiSYDLPOZlSi
SFd98rtTLIxQGPCJFpgdRmineUVXV34BNkX8HEgyqYsnAq7AzraGuvKcaT0ZgT8HksCfIICpooFF
5A8OOzF/smmHEXq5waeQnoyYf3iUkNbD6mzW31Iv9FkNhc1WFiD4f9CPXUCwsIAAJtbYy2QUe9pP
JgYE/4+3z8vwfN6WngzP17Mv4ueRQZrHmceQ5wv8EQGRPyJ/9MYIz+dR4seRyB8eGaR5fHgMeT6O
Pqz1ZHg+WsaatyPw55EpxQc4CBcjKENVsS5GYLemqdIhDe6qBjsNGiEwAV1oCAleEmk9GTCFAhqb
vB09GV6Ftw98DIYXYEZK3fG6vF+UxFpPhpkt9YUqyC91qpHn7UMXNEsLHw/fy+uCDPPLy+vJgJ2y
sfF29GT0YgC+iJ+BhvAK/PlsKaV5fET+8CNX5A8bSqVpwzgif3DK5edtPot4fHgZPWwXIsPAB4K3
j02+F2k+ntLeBb1Xgw9L45K3iFjwHKB5+YXY0ZPh+byLhdjndXl53g6GquEgE9WBXogdPRmez3vh
4+FlFsLn7WCoGg4y0SzQevZ5LT0Zns/LLyROXpeX5+0ADV2lhZdfiB09GZ7Pe1mIfV6Xl+ftAC3i
BxD0sOL5PG48nrzMQvi8HYE/orEQDHncFoKznk3ejsBf4M/niSY3aJO7qoFzJdZ6qcOb0DPNp6+e
HdCFgrVGnva8k0rEj6hp8ERYNIAK/DWAQFPkj8if0qxYOEfkj8ifhWdLqeT7LH9KDpBuNUqXfODA
kct849Iqi6MgJVKZnlS++O1NAw1vGruAo7KjNHlJpJk8b3MhunoyenxwV9aXJiQmM48dXoXJi/gR
gXlwK4sVDyZ/juaxw6uUtbkQXT0ZPT4fG3+u+WB4mXns8CoifgQN4QJ6HtzKYsWDiaaQM48dXqWs
zYXo6sno8fnYRP6wUyDwx8TAtAH6Ys8fdmY5gruqwXHl9djkuP9DizcvcrLfyUbnZh97cWBXOM/L
wl2Yv93eebUt+KXHB3qgA/LGYPnbbR3rnVIWX9ghGe2m9E+ePr4rptbDlgLrbR9edUezjZfI5nOz
c3P/5+WB3WFui8BL6NEF852X1c8cHtqdohIslSXps1ev/vIi46NPdj0Slxqamx+70s/byGZys9HI
zw8M7ArSY9RMB5ydopYcv/nOjdRjWgm1qFsMZmlb2w+v8Bx85cg9JzNFC6VUUZf2lfXLaykYEh4I
YxNpVvOErXrPTYul4f4d+0O6aX2mMYB9Vs5U90zjZ46AOBtd3g5Pi/h5BJAGfBjBYyXw59FAmkdP
DzdeCzC0en52U1sdMKPTtzw1OMpZcAcaf74lADN1+XljQfgrsxPOh7zrsjTnnfSXPe+84oJi0LFz
Nrp8DDwt4ucRYKePETxW5wN/3r5C0xeTQwR8ZHJf5aM3r9hG9hm5oYnZg8OR2bxUWeW542Mrv1ih
aJNP8/1bV15dKUl5I1z5kO1YKzu91kqb1ePEf2a7zWzllXiauTbCQYOd3Gw8Tf6lspLR5Pf6vvax
5dtVOxBOmekygnbedvXKW5b4qnEfRa2SBUkmiu9irzCjhOwxmsqZLeDRc8e2tX/bqLMJ45zLJHV9
21WKR4yEE1MFQ/lOkxIDC5sRnKJMauMvlVBgByPz2FHrweHZMQymwgi15HwtpsKIUunzE3/RD3PN
iGLf6SimwohSDRF/KSY8h0HHCL53fpqpMKJU/gOCv9kEkygplZ6bXUjJ9fZlXpyMivMG38+gYwTf
S+nSKUgWYSqMKNFVpk02f5ZKcNPOPHbK6REeU2GEnmQpn6kwolTmA5I/iOQ8OJQigxymwgg9yVI+
U2FEqYzC0VtQjfdc395qlLLR6W/sHTwgS1se+MjKrV7rp6+o/dFzk8BbWlfz1x9ualL2AQnFqNtb
6YHd+fCpG/fPKLyFfh5+tfuuk1lZ2lzx8Mc61jqdH2m27O2Z9zKA2nyKXE0pRPlLGogFYatFSZyD
5Mu9XGz3b+3YFjBf/aHFnbv7uhTuaT9VHtXSpV2ZnHy1Ry2o09KcxZL4ddTmZec016XmFT7LzvMR
/1mGdEbqIv4zguucC39A8M9KbNa7rK1SejOqAFlxTUD3a5oic5rP0inoNAp89wcEf/6QLyj6Ysdf
AVNnq2HzbvGbJCm7+zm2zwCNzIP7Ry/f0SRZLUslqUey3bulqUmSZifmkjVVdcoXdZBbUU1uuRwf
gNse5gZbfhSe8FBKfWPjzg/5J0/233EIessUi4n4lTuysV+OJtYucfi8DvAuSbZ7rm69Hm/o5LMn
To7c8+oMsWLzPPqxReGBuUBbTZ1FmgomanzkuD63o3Pb0OBtr86WccOz2DUGwkx967me5k+tWGmp
+lKb5a6S2xyXtzX+l87qJiexn81kh4bHvvGHqQ3rln1tcXmP29VdfzNNfDS2Nu+6pKrJZoBLOP2n
hu/6Az0K6KjwPLx50doqMrNkU/FfvdL30EjZDZb5rg+33bi4kqCczx7tGbrvUEjBoVkanZnxVG8g
X4QKs3Ohf3524Bm65epsbrh3Y02TjcB79FQMuhWUwYooAgGBwIWCQFOLr+HN6CgNx91YvczCB2a+
//rlV5rmvv7roR7KvmFN+18ud/zuxePfGs9Kbu+/XNW4rMpKRncm3X188K4jYc0UdPr5kPcmaIHA
OUKA2yBwFt1eOyxj2enJnZqnK2JTN/7H6zf+eoRmeeZQf3DvS907nusfVi+Iq6rJhY4NV65+4dbO
x25a98KnVtxTR1ZiKE6H02MxtXmUKyHI5WrNN/4OD1l3g2FYLW0P3bRqO+wz8ukTE9Go0bxsyeLd
19e5odtsqrFZ13aQfQYUh0FeRLO5/DtaTRNPniQXaCyqLQix3NDY/J0rArDPmA5FTkynJIu5tbXp
O2sqUlIBHZV6LNvlD3iaLJmhUAruELW2Ln54Db0jVVG9Z0cb7DOS0TgYN9uc269Z8/fNqmmGBCGZ
H7hxzU2wz8in+ykOKztaH7u2hvaYvDYIKbDBa5oOJaJ5g6fK943rGglEvrrvXlkH+4zZUHQoblq5
uIo9f0MURREICAQuBATicwdDOcnpuZkMWlJuXgYXiNMnpuERMCyG+iprZaUFvnthafRX2C3WZhd8
haj4wUdbV8IEMhc9OpGQLNa1a5Y83GYpOwUp2uJTIPAuISDvADTeAi4bdCQz6h2ERkjK7/zDAOVp
lkPLOvmKX75/LGqucjc5Hdu3rJKePvJQMN83NPhQwjYXimiNKe2OJYvud6ctJriIYe5o9LZWkm/h
h0dTncvbN8D+JB6898kBckPH5tn1ybYmf8N/rZv+7yHcW2T3/vath8KWTinVsWH11xYbH/vFW7ve
0V7jSAi2Go7mRZVSj+oxqm3LvOD56GtH/ozezXE3Nj91jb/Gb39mX4+7orzHZ95UdS1t84EFuC31
F3sHu+AO1NK2H2701Pth3Y/decUimFT6j574Ar126m5s3H1NYNP6+obBQfx+gwi5G+u3VhnAwp17
B+mGr+JfbupYWd9wj2/qoRi+kS39xNNHH4bHWm30QTOnvUUy3nh5PZxQxTjcHVu93V/+1KMXUQsE
BALvBQKZF3ojGzZ6lHsolVtg4IbGD0W8y5Tn1zNwjdgosbvVaXYz1GathW+O8ekbfzkIkTc0tzx2
pa+xvvKZl1VT0HtxUMKnQIB/W2gJGu9omQYrhaOjkYA799PnT+6lK/Wd166+pd66ZXXVQ/BIRCq1
d0S1fmvc2v2+bcqgol3p/a/07AxLX7yUfPU/+Pow2WdASc3+Y3f0O2sq/bCdD5HDyIYmH5qCUZiC
JbyTXpCwwtbkHR1DBQzlcuVHLx550WmRcsYbGj2NHueqOhISerDpeyzt6n5rDIKE0jMYim700DXf
ttIDmypJMjnvXOWEKznpnJFYdrq22KRdHGA3tFQRsYy0dXntR0wgVshkCpLNtKTWJvWTnuTEJNln
QEnFhlNSnbEAX3DqK+FmTfQR+QZw/qGDkx/d1kBkRBEICAQuHARMxoP909MbPXgPRWr2wR3qo70z
o37yFeU0JUevrTr9z91U0T0092L/2DX/MYAqpVPQaUyJboHAuUag/FfbiQj8/EOyWzSXK8C5cfvS
anc8unckEdYNJbvz5Z6dXO/O3499HK74+6qWSiH6RZzrKyGnTw3/eCANTxTYzIZUKv3ySAy/06fT
sHym35go7h2GYuyiIrGSjM1/DabEkz5jXT25PDk6xp7MUkRt7r/cvHgludByVoW7NcP2NHmMvrVj
UavKtrkSThG31ZDy5DEhs9d/C7nCUizsRMLvdYtcmcrNgYXKAnv2VYqlkmCkRE4wBAICgfcSASM8
ih8+GCps83q2mQeldhjk6ed7Urb6BQSVnf2b16a/tdFfaXPA821rl9R9LZ/a+7u3H4JnOEQRCLzX
CJRfbsKhOCxFlX7/F23jP+LXOZv3qxub7PBN/oku/qu26ijMjvs31vsTwXveVD+PmcloHvxQaSmN
kbHQ3nLPQlqtsCqbO7xGaZx+ZZckv1W15JtVLcXcO/l0XN9AHiUZj2jWbPPf/1HbSqeUnJv73cBs
70z05XTVI9sWvRMP5XToti639/njv00byU4HtnpWE/zS+IgaNZedHOf42yf/W0+KPvwKLWPAYRiA
Z0ck8nO5cjgYquCAyIVXVsgWR8xADA5BCAQuCATyElwp/WV/eJu36uq1dVIALtlO7Zak2/SDo78u
kbsH+odv6R9eEaja0uzd0FDlt9m2X9W8d/dJfW3RIxB4lxCAJQd/TKP2lwo+NQYrkfWz1zV3kh6U
sTywZRE8VpCcGNfdZ4CsyX5lq2fDysZPKduY2zbUwRo4G8TrE4Z6m0n9u3E0LodhMeHvoNXxSFJf
iFzDuKyzVgnG/Pnl5FaC5jFSVLOSgM2LnFCrjGuNYpvd7ISm2XbP1nbyyHdmdveIdi2mi3X2h7/s
+1b3zO7x1IYO+kubHHGheAQSPaJpUpPnWkkw5IMrLDbkFebIZQ3TYpfUFUwcCMYPxOx3bVn2jS0t
HyYwFm2+OEy2Hp5qe08YxOBfasvlS+65ZtmXGksvQaFlok6uasBvapbKMjesrpF/xE9E0DiLp+iL
6auJhcgvREZt9Z23ztTXQuQXIvPOI1ZrnqmvhcgvREYdxTtvnamvhcgvROadR6zWPFNfC5FfiIw6
Cq7V1T8Dv1Rr7WiA1w0c7de+L4CMYUvlVnLzFortihoc1AV4aP2pP163+yrPgZHQt/5w8qYn+sAI
vA0Dvreop6CFxLYQGWL9XJQz9bUQ+YXInIvYiY0z9bUQ+YXIXMjxl4kN1rGyS7th54uD1/5xW12V
/x9v9QxNxIJ54+KAy0O/DP/8tQlqCRQBkaI6fheXUsHnQy3bvbavfXLFiuMzzlr/pgB8p07t7iIX
OdpbW360yRsdO3XjPjaE0AKzwwg0jqAbXnhzeGjlMngO9JcfcT4/mFy+NLAMFu9U8IfwEg5yDUJV
RmKwS7Bcs3nNw8cH7joC90F4myhZNF65qGXPJxoJ12TykN+CQsk9/WJ/l3x07BgN8JwGbBo+s7W5
ejDR0lxLj0sy28lAVjyuVjwCT3YxQu7smK/ZTLr+sXiJgoUEklCy/+vQ1NXX1KzduGpX/cSrIdM1
y/3wyEp0eHI32fAw4UJPz/iJS6uW+Rue217xbF+0vjmw1muC5zCegN/lyjggYlAX6CQEBDO++gfe
iSGLe+tifuODxpkLRsjx0/CAiU0WDBNjBBWUK2SyLkbo2eR1FyLDy5+pLz35s7HJ64r4EQ09HAT+
gAwUwAEhoi0zvaFplBzATM3SeyggkHi+F64vI2JUTMq8GcytrTffsm15y0Csrsnf6pTxHJ2YHZf8
dfUtT1xb+cJkdkVLNUwg2WgU5rF6bgqi8yF6R4O8ceSwXtbFCL1zyhSBWIgMLy/Hr7BO60tPXjFA
PvVkFhLbQmTOxpdebGdjk9e9EOLn45Fp/qoGhAgFavovG/r0np6D5EdW5qZA1dp6ss+AF5P/0y/e
2hkGsOAfOySqmM+zh6If+u2J/aBocWxds2hTwC5l4o89fWxXjIpRH1ny4AX1Qmp0Cus7oeLkGgN2
MRd4bqK3/aL/RLxQ6fVsX1u3zGmIzgW/+YsBuiEg9wKy9OoC6j7TMwX7GjP83GtVgLsqA+bBFN5H
IMZjWfRukN9qajPBq9DHp4M/ePrIt5TbNCQmuaT/Zt/wdF7yB/y3bGzaFLCe6A+ClN3v2W4uPNMz
zXlUxc93LaamuGMkP8fF17eHRwbvfWUKXsnatChw0xq/3yJNj43dv59+M5FRAmUIO3bHUyePRnPm
yqptaxvXes3ZePTHv+l9gcgUrWHIceUWUHhk6IHDoaRkWLakDvYZ0Si5RAQ/zaVwAYk4MEIVf8m4
RWGUYSqMQD5fsy4g8FRCTfBXaiB4GdoqUzEx3jhjogJrAsFcMKelMsBBFUZAU/OPdQHBTDHjKMzL
AF22oCONccZEFdYEgrlgTktlgIMqjICm5h/rAoKZYsZRmJcBumxBRxrjjIkqrAkEc8GclsoAB1UY
AU3NP9YFBDPFjKMwLwN02YKONMYZE1VYEwjmgjktlQEOqjACmpp/rAsIZooZR2EYjVnYU0jKLPp4
L3kWLjk9Q79pSCl49FuZG3/0+5MwDUo256aOmlZn5ugYmXfJlJIN/90rEzCB+Ov9N62tW1llSc4F
H/wtfC008FNQpxyw4vdcxV+0A+GULeQQSsBhTFRhTSAYRAy0Uhk0WMoHdfaPl2GmmHEU42XQWmkN
klCYWUYgk3bKIGAXc8Gclsro6TLjQPAyzBQzjpK8DNUoUzFTvHHGRAXWBIK5YE5LZYCDKoyAJuOg
vFwbvv7Lo6/P4iaBWYc+5gZWbFOn2wp77UQs1cW9jEslQ6yjSlHXbbOtqCDMA0EyiNSFs6/qKGOH
9hf5DW5bk9kYjKXI337j49TGYGioMEVT2TDZT7DYeGd8DLyMHh91jZ0+G6AxFEyOErN8MTZUGODt
5tQj8Hk7GEwmTC5R8IWXwRgMaD8YS/ak0D4fW1G3ocIOLwFLpLJd5BIOL1NqE3qxmDt9Fkc2e4DE
gSpKj/y5QDtMS8+XHp8pAqEno8fX0+X5In4812eK4dngJvAHtKGcDYZnrNvgtjaZTcFwokc1pRA7
S912nzkfjGV7yHMcLDYTnZ1gPuTPl16e6PHPhy5v84xxUGB/t/Hn/Ir4WY6RtFnvcf5JW2V7Q1VF
RYWJvJCTlGf3vQRbjWOvz+JlfS69CgXJYJCghsKxdUcTkWOFU9Czw2SB0MsuXkZFc/b1lPX8LsgX
Z1/PDh/PgmzyCpx9ET+AoS0cPgJ/LTjQ5vAR+SPyR8w/ZBSox4XevLEgrLjxpWeH+pOrBdnkFTj7
78fxS7caFaVbDXhWA88TYIEErckAht0GAmSQDAgnzHKUIDUtsoDckj/I6QFtxQ4255FHI8wUI9An
usJ9D9Sk8B3YpGwRvwyDwJ8CwaeJyB8czGL84hjhazH/yGjgVEtrgomY/3FXz3CgTT5zkBb5o80f
TCQtUmZ5T6Dlc21+66BazullD1z+VdO6shlAG3gmOHuE1JPX48t5T4+Bj0e1hGh8KE1eXsSPqOjh
rMcX+EMWkcLVfO7p4qYzPenJ6/EF/gJ/HLlY6+WJHl/kj8if9yp/FL/cL1DIkqzcNOEv0sJeATOY
6Ki3cLjPKGHLUsDXTX1iq0xRmy/aUYnqCIn4ERjAihECf1XmYEPkj5IfYvxq0kMnNdRSOkJi/lHS
Ssw/csIwQFQJ9H7PH3lXpzpmaJCXNpANARSyz6A14ehsO/T4qj0FtYYV7l1wRtPokoAo6EiQGmOg
roFWyaM5rHE/hLqUI+IX+Iv8EeNXnsi4uULMPzguOEjIrEuYYv4EBBQcxPx5DudPXO5VKUcaZm4H
SnFnqakh5g9Fb0jjJgBr8MYImaJtPV0iryjwMiRsOk7QICaMLMyuynC6aETEj3BBTQoCK/CnqSSD
AR8if+jAweGmTpNi1hQpkT8if+bNAXlkkYwhBZtFal5dIq8oiPn/Ilq/2FkjJ7pY8FkN5YyyXNCe
WkUBrLBpCHjMKBKaJlFCy/OmlK6u4pQ5Yva5HhYy5SkHIuKXIRL4Y15QHET+AAJi/EJG8DhgVrDc
YIQ8gkT+cEDwuCGM2KmLoZh/PpD5w6UMI+kNFNZihCZ1GB+IskORF9CjNTbL2uG3CCDAT4t6Zsvy
Nb54mbJ+eQE9WmOzrB0RP6KnwYqHtCxuvIAerbFZ1o7AX+Av8gdGARQYIGL+LE2GsvNGqVgpR8w/
pZicCcd8abV7lYf7gxhnoixkBQICAYGAQEAgIBAQCCACdpMxy55w4EAxNyZ6wuFwNqt6hxwnIEiB
gEBAICAQEAgIBAQCp0HAbDa73e4qH/xNMfXfVIXHQr1er9VqzefxL4OcxpDoFggIBAQCAgGBgEBA
IFCKgNFohPeRO51O2HMY8EaeImRuaGiASxpnv9WIBifnEjlbhcfvwb/wmpoemUzZqhr97kx4cjxm
rqv3wR8azSdm5+Avpjml4NhY2uGvk4XhbxlOjoZiDm9dXWVhKiLVgMQ7K/lEcE7yec2zoYyn1Eg2
DsarK005k81C/kptmRKfGg4aK02RsORw+dyWvNEYjXPx5DOpvMlm1lFGe3AwcVut15FNRDMmYyJm
8Hnlv3or0QDY0REBW6WDGstkshaLzqMzZcJcCCsfDkadPve5NboQx0JGICAQEAi8/xHIRsdGppJm
16JGfzYctrhPP9lmE6Gx8Vmporqx1l1uFckGx0bBYG2Nl8zbqfBszulxlk7h+UzWmI3zHrOzwXjl
Wc/2sHaNR6S6xlpbueBOe0JhqwGbDIfDYbFYtFsNuKpReMdPyiie54bfnrE6XYZMLhuJSrVttY65
k29Zm5bXzvaFjVXhOXvbYunUrKWzPvHa8XFXx+W2ZJ+hfol/Zihb0dRQYczOnXwj6e68tH3sraPp
uqVeo6HWZ54OJip8Poc5E5qeM7t8LksmOD1nqvJXIQb5VCgYMVZ4qiy5SCSSMbp8VbZsbG42Eopk
qpZXSdMRp88lBSOSr9YrpWKRaLayusqSjWSNUnbsaLJ5vd8aiWRtPm8FhTQfCQYzFpfPEX2jt1BV
E5lwBlp9DthxxCqqLRbJ7zUGQwmHz58dOnQq17KxxU7C8/sdRgzP47IVsyHY2x+ccrV3LJYmYnN2
6/SscXltLfzpxkhoLmt1eY1WiGg6lLI4XFVSfCxvBMJrj751NLZ0bU2cHCxay6cSsXjS6HVJpb4i
wcmMxetzGcBmRjKDJYc5G4sVHMb4dCQPh2zMRGYjsXgk07i8VtnmKGdLfAoEBAICAYHA2SIQO/ra
aGD5uorIyb6weam32lpdlQwGs5YqLyxXkeBc1ub3VqTmpudyDr+PLjSpyUOn8kvWrUsNHAsZF7dX
RJUVKhGLxfIOjyt56kTEvmx5rdfvzc6FQqG5dFVjrS+PS4AlI4tVJofeDjsXe6vt1SAWjOUsPp95
5tSs9yxn+2ywa7Ry5RKpZ9y8rsP3zuCBHQZsOKBotxqw+zjrrUYiXnBX5rOBlW3GVHxqImmxuP0d
l/ilTO+IubrJLC1aVFsvhWMJi7vpklXxQcmUj0j+xX6/bebteN7isYUm4i2rL3HbJPfGK6TU+Ouj
+cL0cMrrj83Y3bHBaJU30T8ak8K5QH3i+HHjurU+sxQ8eTLprJg7MWhrzp4MuTzxnoKzaaJ/tr7G
YLbastGwp8Z6/MRs4yLpeK/UkD85ZG5eU2ux5NMzs1Kd1ZozhN46EayrtYYqltZVGBOTJ4M5Z+bU
8cLK1gpfjds6F7fZY1Ozrian1Zgemc2ZolFzta23e6i12mo1SieP9Duaq46/cbKlam7EUusMh9wd
DcpeY24623zJ0sjYnNRssVktNrvVACBLmZnuYwPNHQ0zs+lMMFLZWHGiO9i5wjg3lTEEe6T2ZqvN
Eu19a6xoLdX76jHIxtCRMY0vowP2aNWuyNFUc8OpY4PNS2pGB02rayaHohWp0bmGBqm7N+dJByvr
K3JGi434FkUgIBAQCAgEzikCqXi+anGTr1LydcKyPN3XLxmnjo/b6uwJWAtOjZlrzJNDKVsw7Gx2
DPXm2lY1VKRmZquWrPBXWqTVGxsz028cDuEK1ZgfmHI1GMdH7M3wxdNiisdgCTsxZa8zGK02A1tu
FrnmQii2yGK2WDKxmKUiOxKWXIlTJw3LbXY7TPZnNdtbPJWF/hO9eVdb8zu2pNlhMMTJ+qjXx4RO
R1hN2UzBLk0PDUtmc7bgpAZjvW+ccKxcC3CPx3MGQyGZLsCflLXAXqcA/UAaTAWDyWKChr3SMpXI
GezmTHB4Kgd95tqGxuGJUNJmyyec7cubzL7QkcOZVYHAbHA8njUYLPmcoRBPpAxWa8HgbG1v9swZ
ZmIJR0NroC48Hk6FwwZfXTrb1B6oM8yODxTctSvbG+1wGFkwbjBbnG5vtSudnJqMWGpJNLDZSkdj
eYPZZK9wuaRaZy5ccBnDUeiCAn8It2DIxRJp+GNV1opKt2SIzJicOVOlx+Za5POMTkUyhjzIUZgy
0xOheNJiys9Ojzc1UH1agQl3YGmLLzs7PRe31LVhvkUAAATgSURBVC2t8cWGe7IFR+vSZk/EEDTD
9RmT31eZKFormJw1bfWWwyNaX/FMvODwWCorpUyB2FzkMXZ3Hxu0tiwzvD1lKphsleZY0tCwNOCL
jb5NDu9050/0CwQEAgIBgcCZIWAywe10Or9GBgZSlSaT3be4KTI8E5Hc8ayldkVTbUNo5KSpqSlQ
5Rg9EjY0VppgfxAFFauUmOwfn3MrK1S+qqZ9cVPSMGh22RyVksWUzKczNU1NTZloOBmJwlJAlxuT
zaqIOaukKnMkBetoIRmN58g0L5czOwa1dGo25em4vMPUfWzWEKhT951t6x3dkNE6NS9q9iRiqUQi
FZtL1zT7oT/Ue2QkYYwMHBtNVzjiA0cOn3IEqqge8ehrqBo7cuTIiLSo1gbNqubmVM/rR7qPvNEb
cVXCX7gvzE3M5G3mfMZYV53q7j5y8HiovjZ75NixoXRFNbkfkI9HyB++T8WC8YIEj7TCm2IMrur8
cHf34ROxQiqUr3S7qlLDbx3rPpKtCViMqmcrrJbU2MjkVChjtUlp+subVDSSliCwTDJJHo+lj8iS
l88YIRYoBbhHk5by2XQetlKm0Fi6ziXB9a503pgOTcUkszGfTc2c6p9JwV5mZCi56rK1HasuaTbO
TGt+1pPPEWvGqoB5ovtY92QiD2GR4Ik/c3Kqf3hyEq3RAAhQWbOn1FdlY60xlYDbP3aHWSI2zYFq
Ywwu3jmqXKZsLBLJOwPV+aEjxw6PpaSCHBjxLIpAQCAgEBAInBsELHVtrtCrh48cPngsW0l+cJGL
zoRSRquUNXpq8iPHjrzxVtRSGeqBmXjEu6gGBCz+Nu/csTe6uw8eHnHU1mhWKFgIjHl86Zlkr6qa
6z1y+MQk/HKDLQHwIASsCkTMJE29fTxWkHKpaCybMxnN+SxdXM7ywCwOc+RUd/dJqeLc33UnX+jP
Mjymns1kzeUfbIRnWCSLarmHVTSTN6sezdQ8F8mskQdgqFlGoEd4mNWssQnbgSzsBqRsHjcX0ISn
VFiAaiKfhaccWATwbCw8z6KW4FtaU1x4GcnCzPAqenRmoPuEVGEMxbyXrNLuHPOZMtbK+GIsrZMi
1Kc7Iq2maAsEBAICAYHAGSEAywg8bldciNi0i2sRbA0YodjNZjJGecnQLiuKCP3kFHXn+zLmVTbO
vFF2CTpzM2qNZ/e9dC63GmrjoqWLQD4Tm4vmXV7XPFsbXWXRIRAQCAgEBAICgYsHAdhqiMXuPThd
RkuF1/se+BUuBQICAYGAQEAg8O4jQB4IEEUgIBAQCAgEBAICAYHAeUJAbDXOE7DCrEBAICAQEAgI
BAQCBAGx1RB5IBAQCAgEBAICAYHAeURAbDXOI7jCtEBAICAQEAgIBAQCYqshckAgIBAQCAgEBAIC
gfOIgNhqnEdwhWmBgEBAICAQEAgIBMRWQ+SAQEAgIBAQCAgEBALnEQGx1TiP4ArTAgGBgEBAICAQ
EAiIrYbIAYGAQEAgIBAQCAgEziMCZnhj6Hk0L0wLBAQCAgGBgEBAIPABRmBgaMT80quvf4AREIcu
EBAICAQEAgIBgcD5RcDssJ37Pxd7fkMW1gUCAgGBgEBAICAQuHgQMFdUui6eaEWkAgGBgEBAICAQ
EAhcZAiYbXb7RRayCFcgIBAQCAgEBAICgYsHgf8HDjQLXSJvsg4AAAAASUVORK5CYII=

--Apple-Mail-15-325180960--

From adurand@juniper.net  Thu Oct  6 17:46:48 2011
Return-Path: <adurand@juniper.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 022F521F8B03 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 17:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.568
X-Spam-Level: 
X-Spam-Status: No, score=-106.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUOGcku-C78A for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 17:46:47 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 262F021F8ACE for <softwires@ietf.org>; Thu,  6 Oct 2011 17:46:47 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP;  Thu, 06 Oct 2011 17:49:59 PDT
Received: from P-EMHUB11-HQ.jnpr.net (172.24.192.58) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.83.0; Thu, 6 Oct 2011 17:48:07 -0700
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB11-HQ.jnpr.net ([::1]) with mapi; Thu, 6 Oct 2011 17:48:07 -0700
From: Alain Durand <adurand@juniper.net>
To: "softwires@ietf.org list" <softwires@ietf.org>
Date: Thu, 6 Oct 2011 17:48:05 -0700
Thread-Topic: Mapping of Addressees and Ports design team
Thread-Index: AcyEiscCWyoVn4rOQEWfrRPpBnwNfQ==
Message-ID: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Ole Troan <ot@cisco.com>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 07 Oct 2011 00:46:48 -0000

During the Softwire interim meeting in Beijing last week, multiple address =
and port mapping technologies were presented for either encapsulation or do=
uble translation.
There was a consensus that those technologies could and should converge. To=
 achieve this, we would like to formally announce the creation of the MAP (=
Mapping of Addresses and Ports) design team.

This design team is tasked to formulate a unified format is to be used eith=
er in an encapsulation or double translation mode, for both hub & spokes an=
d mesh models.

Ole Troan will be leading the effort and will report at the Taipei IETF.

Please send Ole, Yong and Alain a note if you intend to participate.

Alain & Yong, Softwire co-chairs.=

From cx.cernet@gmail.com  Thu Oct  6 18:10:14 2011
Return-Path: <cx.cernet@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 B61E621F8B17 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 18:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.347
X-Spam-Level: 
X-Spam-Status: No, score=-3.347 tagged_above=-999 required=5 tests=[AWL=0.251,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qxQyqNrE2Rt for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 18:10:14 -0700 (PDT)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 2B80921F8B0F for <softwires@ietf.org>; Thu,  6 Oct 2011 18:10:14 -0700 (PDT)
Received: by pzk37 with SMTP id 37so8487929pzk.9 for <softwires@ietf.org>; Thu, 06 Oct 2011 18:13:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d52SkH3mGnCw/qzC0VD32QLo4ZQNIDjbvoHF2kmeQ2U=; b=UJerHc5NX5VyXF3XH+IeO7wgqP8f97SPvT6xDvC1uCIum6tMmi1xLC/5AgzUxKoEdo EkCWgdvs5tpuIxQYh1ZcPFpa2a06Jw5WXdTpB8E5KMrC6FFl1vEoGJY6pKPQZ0bkfRHo neYy9Lto4gamUsr3iVYpMapOgtsBEnyxV1L1Q=
MIME-Version: 1.0
Received: by 10.68.15.65 with SMTP id v1mr801468pbc.132.1317950006181; Thu, 06 Oct 2011 18:13:26 -0700 (PDT)
Received: by 10.142.162.1 with HTTP; Thu, 6 Oct 2011 18:13:26 -0700 (PDT)
In-Reply-To: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
Date: Fri, 7 Oct 2011 09:13:26 +0800
Message-ID: <CABv173VUy=FU+CPXju4vMDcepU+4LHAmEuLP7=W-bk0dLWDt2w@mail.gmail.com>
From: Congxiao Bao <cx.cernet@gmail.com>
To: Alain Durand <adurand@juniper.net>, Ole Troan <ot@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec520e74ff340ba04aeab2514
Cc: "softwires@ietf.org list" <softwires@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 07 Oct 2011 01:10:14 -0000

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

Hi Ole,

I am Congxiao Bao, I would like to be in the design team of MAP, I think I
could contribute my design ideas for stateless double transaltion.Since I
have been working on IVI ,dIVI and dIVI-PD for about three years.

Thansk!

Best,

Congxiao


2011/10/7 Alain Durand <adurand@juniper.net>

> During the Softwire interim meeting in Beijing last week, multiple address
> and port mapping technologies were presented for either encapsulation or
> double translation.
> There was a consensus that those technologies could and should converge. To
> achieve this, we would like to formally announce the creation of the MAP
> (Mapping of Addresses and Ports) design team.
>
> This design team is tasked to formulate a unified format is to be used
> either in an encapsulation or double translation mode, for both hub & spokes
> and mesh models.
>
> Ole Troan will be leading the effort and will report at the Taipei IETF.
>
> Please send Ole, Yong and Alain a note if you intend to participate.
>
> Alain & Yong, Softwire co-chairs.
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

<div>Hi Ole,</div>
<div>=A0</div>
<div>I am Congxiao Bao, I=A0would like to be in the design team of MAP, I t=
hink I could contribute my design ideas for stateless double transaltion.Si=
nce I have=A0been working on IVI ,dIVI and dIVI-PD for about three years.</=
div>

<div>=A0</div>
<div>Thansk!</div>
<div>=A0</div>
<div>Best,</div>
<div>=A0</div>
<div>Congxiao</div>
<div>=A0</div>
<div>=A0</div>
<div class=3D"gmail_quote">2011/10/7 Alain Durand <span dir=3D"ltr">&lt;<a =
href=3D"mailto:adurand@juniper.net">adurand@juniper.net</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">During the Softwire interim meet=
ing in Beijing last week, multiple address and port mapping technologies we=
re presented for either encapsulation or double translation.<br>
There was a consensus that those technologies could and should converge. To=
 achieve this, we would like to formally announce the creation of the MAP (=
Mapping of Addresses and Ports) design team.<br><br>This design team is tas=
ked to formulate a unified format is to be used either in an encapsulation =
or double translation mode, for both hub &amp; spokes and mesh models.<br>
<br>Ole Troan will be leading the effort and will report at the Taipei IETF=
.<br><br>Please send Ole, Yong and Alain a note if you intend to participat=
e.<br><br>Alain &amp; Yong, Softwire co-chairs.<br>________________________=
_______________________<br>
Softwires mailing list<br><a href=3D"mailto:Softwires@ietf.org">Softwires@i=
etf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br></=
blockquote>
</div><br>

--bcaec520e74ff340ba04aeab2514--

From fibrib@gmail.com  Thu Oct  6 18:38:58 2011
Return-Path: <fibrib@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 8221821F8B0D for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 18:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IBu0dyzStBxE for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 18:38:58 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9111321F8B0C for <softwires@ietf.org>; Thu,  6 Oct 2011 18:38:55 -0700 (PDT)
Received: by yxt33 with SMTP id 33so3896801yxt.31 for <softwires@ietf.org>; Thu, 06 Oct 2011 18:42:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=3fIG4fFhpw9iUszu3Pxf6NhKcolFTU7e6+PZGgPapk4=; b=L6wKiGxXOEMTZjR04MaYoN27gI927paWnjwPakJp215Mo+yEMN7yoanijfLKwnXv6O N7NZS+7mI7JEBJm9XxcNG2VC5WU+MxFtgkUSgLBhC8mgbyi6G7jnMF/Fwx/g5CgTgnt9 hKX7xMJLOYkcLxxhr/qpSrF2M0pV3CPNNoLes=
Received: by 10.68.33.164 with SMTP id s4mr10054124pbi.119.1317951727215; Thu, 06 Oct 2011 18:42:07 -0700 (PDT)
Received: from [10.168.37.138] (pw126211002088.37.tik.panda-world.ne.jp. [126.211.2.88]) by mx.google.com with ESMTPS id z1sm25480651pbl.5.2011.10.06.18.42.03 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 06 Oct 2011 18:42:06 -0700 (PDT)
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
In-Reply-To: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
Mime-Version: 1.0 (iPad Mail 8L1)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <49917862-9D9B-4775-8100-53123472476E@gmail.com>
X-Mailer: iPad Mail (8L1)
From: Maoke Chen <fibrib@gmail.com>
Date: Fri, 7 Oct 2011 10:42:02 +0900
To: Alain Durand <adurand@juniper.net>, "ot@cisco.com" <ot@cisco.com>
Cc: "softwires@ietf.org list" <softwires@ietf.org>, Ole Troan <ot@cisco.com>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 07 Oct 2011 01:38:58 -0000

hi Ole, Alain and Yong,

this is Maoke Chen of FreeBit.com. i participated the early design and devel=
opment of IVI and now working in an ISP, doing also ISP service outsourcing t=
o a large number of small administrative domains. i think i may contribute m=
y understanding of stateless transition and  concerns from middle and small o=
perators, into the MAP team.

thanks and regards,
maoke

On 2011/10/07, at 9:48, Alain Durand <adurand@juniper.net> wrote:

> During the Softwire interim meeting in Beijing last week, multiple address=
 and port mapping technologies were presented for either encapsulation or do=
uble translation.
> There was a consensus that those technologies could and should converge. T=
o achieve this, we would like to formally announce the creation of the MAP (=
Mapping of Addresses and Ports) design team.
>=20
> This design team is tasked to formulate a unified format is to be used eit=
her in an encapsulation or double translation mode, for both hub & spokes an=
d mesh models.
>=20
> Ole Troan will be leading the effort and will report at the Taipei IETF.
>=20
> Please send Ole, Yong and Alain a note if you intend to participate.
>=20
> Alain & Yong, Softwire co-chairs.
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From xing@cernet.edu.cn  Thu Oct  6 22:58:34 2011
Return-Path: <xing@cernet.edu.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 D020621F8B47 for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 22:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.695
X-Spam-Level: 
X-Spam-Status: No, score=-99.695 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, FH_HAS_XAIMC=2.696, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qQXU8-mudlRN for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 22:58:34 -0700 (PDT)
Received: from cernet.edu.cn (mail.cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with SMTP id 37BDB21F8B59 for <softwires@ietf.org>; Thu,  6 Oct 2011 22:58:25 -0700 (PDT)
Received: from [127.0.0.1]([59.66.24.37]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm284e8ea53b; Fri, 07 Oct 2011 14:01:36 +0800
Message-ID: <4E8E95BD.5000006@cernet.edu.cn>
Date: Fri, 07 Oct 2011 14:01:33 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
In-Reply-To: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: vKC5DM1B
Cc: "softwires@ietf.org list" <softwires@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 07 Oct 2011 05:58:34 -0000

Hi, Ole and Chairs,

I would like to be in the design team of MAP, since I have design, 
deployment and operation experiences in double translation (dIVI and 
dIVI-PD).

Regards,

xing

äºŽ 2011/10/7 8:48, Alain Durand å†™é�“:
> During the Softwire interim meeting in Beijing last week, multiple address and port mapping technologies were presented for either encapsulation or double translation.
> There was a consensus that those technologies could and should converge. To achieve this, we would like to formally announce the creation of the MAP (Mapping of Addresses and Ports) design team.
>
> This design team is tasked to formulate a unified format is to be used either in an encapsulation or double translation mode, for both hub&  spokes and mesh models.
>
> Ole Troan will be leading the effort and will report at the Taipei IETF.
>
> Please send Ole, Yong and Alain a note if you intend to participate.
>
> Alain&  Yong, Softwire co-chairs.
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>


From xing@cernet.edu.cn  Thu Oct  6 23:49:38 2011
Return-Path: <xing@cernet.edu.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 0941D21F8AEA for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 23:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.624
X-Spam-Level: 
X-Spam-Status: No, score=-98.624 tagged_above=-999 required=5 tests=[AWL=-0.880, BAYES_20=-0.74, FH_HAS_XAIMC=2.696, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MVIlix4wPA-u for <softwires@ietfa.amsl.com>; Thu,  6 Oct 2011 23:49:37 -0700 (PDT)
Received: from cernet.edu.cn (mail.cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with SMTP id 9A18721F8ABC for <softwires@ietf.org>; Thu,  6 Oct 2011 23:49:36 -0700 (PDT)
Received: from [127.0.0.1]([59.66.24.37]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jmb4e8eb138; Fri, 07 Oct 2011 14:52:45 +0800
Message-ID: <4E8EA1B5.8010108@cernet.edu.cn>
Date: Fri, 07 Oct 2011 14:52:37 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net>	<CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com>	<B3D5FABA-72BA-4C35-A068-D823CC0A4682@laposte.net>	<CAM+vMERSbGuraAC9snvGUgPBOY40m5p0SX46qfVqJaB6bHmvCw@mail.gmail.com>	<D8B8F1D1-1FE7-44E1-A6C6-E1480BD91C0A@ipinfusion.com>	<4E82C970.8060801@jacni.com>	<3580FD83-1FD6-4A5D-9AB1-046FBE47AFBB@employees.org>	<823C69D6-D040-4959-8A5A-3B1B2CAF7734@free.fr>	<C1DB0E47-C4F8-4AAF-B754-379B9B47BB95@employees.org>	<EC5F7306-8EA6-4707-A8EF-D8D2BEC5E3B9@free.fr>	<593B5458-3276-43D7-AF32-2FB8EF899AE7@employees.org>	<332BEE87-D2F4-496B-8D73-16AC7FFA2B71@free.fr>	<CC3E5BBD-3C75-48F2-90E7-AFAE365AAF2F@employees.org>	<F0D8CC93-E84B-4565-8A78-3D166BA88FA7@laposte.net>	<05DF0672-BE68-4DA2-8094-7B314E416A1A@employees.org> <5EFC2E1C-ACBB-49FE-94C5-B3A10292B0F8@laposte.net>
In-Reply-To: <5EFC2E1C-ACBB-49FE-94C5-B3A10292B0F8@laposte.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: vO7SEM1B
Cc: Softwires-wg <softwires@ietf.org>, Wojciech Dec <wdec@cisco.com>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 07 Oct 2011 06:49:38 -0000

äºŽ 2011/10/6 17:39, RÃ©mi DesprÃ©s å†™é�“:
> Hi Ole,
> I just found I didn't answer this mail directly.
> In case other exchanged mails wouldn't have answered the point, please see below.
>> if the 4rd / dIVI CE takes (a well known or provisioned) /64 prefix out of the delegated prefix. then why do you need any of that?
> I don't completely follow the proposal, and what you want to avoid.
> In any case, the discussion should now focus on the proposed unified address mapping.
> Agreed?
>
>

In the case of double stateless translation, the IPv6 /128 should 
contains [whole IPv4 address]+[PSID], while the encapsulation may not. xing

>> note that I'm not arguing against having a defined IID for dIVI/4rd, that's nice for pretty printing like what we do for ISATAP.
> Good, then.
>
> Cheers,
> RD
>
>
>
>> cheers,
>> Ole
>>
>>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>


From despres.remi@free.fr  Fri Oct  7 02:04:12 2011
Return-Path: <despres.remi@free.fr>
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 21AB521F8B58 for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 02:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.278
X-Spam-Level: 
X-Spam-Status: No, score=-2.278 tagged_above=-999 required=5 tests=[AWL=0.022,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xs44CdJzhsz8 for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 02:04:11 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 40DDB21F8B56 for <softwires@ietf.org>; Fri,  7 Oct 2011 02:04:09 -0700 (PDT)
Received: from [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb] (unknown [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb]) by smtp1-g21.free.fr (Postfix) with ESMTP id 46F33940303; Fri,  7 Oct 2011 11:07:15 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@free.fr>
In-Reply-To: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
Date: Fri, 7 Oct 2011 11:07:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD415A5A-EFA0-4C8B-A22D-2EF572B8D042@free.fr>
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 07 Oct 2011 09:04:12 -0000

Congratulation, Ole, for having deserved this responsibility.

1.
Because I have no financial compensation for my IETF work, I now have to =
switch to another subject which I had left aside for some time.

As you know, I did volunteer to be coordinator-editor of this unifying =
effort.
My motivation was that, if given this responsibility, it would have been =
such an honor, and such a sign of confidence, that I would have been =
willing to continue unpaid hard work.
The Chairs having decided otherwise, I have complete respect for their =
decision. =20

I hope my past contributions on this subject will substantially help you =
to succeed, in particular:
 - Draft-despres-softwire-4rd-addmapping-01.=20
It is the result of an collaborative work of 4 co-authors having widely =
different origins, and enthusiastic appreciation of the result.=20
Jacni, Simon, and Xiaohong, will be able to comment, and I will also =
remain available if needed and asked to on specific points. =20
 - The "Proposed Unified Address Mapping for encapsulation and =
double-translation" of =
www.ietf.org/mail-archive/web/softwires/current/msg02994.=20
It is the result of common work between dedicated advocates of =
Encapsulation and of Double translation. Xing, Wojciech, and Congxiao, =
will be able to comment, and I will remain available if needed and asked =
to on specific points.

2.
As a recognition of the value of these past contributions, I would be =
glad if your design team could keep the 4rd acronym for "IPv4 Residual =
Deployment".=20
With it, you could have, for instance, 4rd-M for the address mapping, =
4rd-E for encapsulation, and 4rd-T for double translation.

3.
I recently found what I see as a breakthrough approach for a more =
complete unification between 4rd-E and 4rd-T (without impact on the =
address mapping part).=20
Within a few days, I should be able to describe this idea on the WG =
list.
The Softwire WG will then be free to do whatever it likes with it.

4.
FYI, I also have a draft submitted to the RFC editor on "6a44" =
(stateless IPv6 across NAT44; with as co-authors Brian Carpenter, Dan =
Wing, and Sheng Jiang). I plan to pursue this project till its =
conclusion.=20

Best wishes,
RD

=20
Le 7 oct. 2011 =E0 02:48, Alain Durand a =E9crit :

> During the Softwire interim meeting in Beijing last week, multiple =
address and port mapping technologies were presented for either =
encapsulation or double translation.
> There was a consensus that those technologies could and should =
converge. To achieve this, we would like to formally announce the =
creation of the MAP (Mapping of Addresses and Ports) design team.
>=20
> This design team is tasked to formulate a unified format is to be used =
either in an encapsulation or double translation mode, for both hub & =
spokes and mesh models.
>=20
> Ole Troan will be leading the effort and will report at the Taipei =
IETF.

>=20
> Please send Ole, Yong and Alain a note if you intend to participate.
>=20
> Alain & Yong, Softwire co-chairs.
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>=20


From phdgang@gmail.com  Fri Oct  7 08:30:24 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 E358421F8C19 for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 08:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJlD+-wpWR5x for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 08:30:24 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3080C21F87D6 for <softwires@ietf.org>; Fri,  7 Oct 2011 08:30:24 -0700 (PDT)
Received: by wwf22 with SMTP id 22so4304045wwf.13 for <softwires@ietf.org>; Fri, 07 Oct 2011 08:33:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=k90nxtWHq1h9bYFuZwL66jPZ10Iccu5BEWqjDr504GM=; b=PROELm8zLTlO29qdUeW1UH3PR779IKSZBbJzDA+oJK/OHTW5wTehy5WOmzUxvce9rQ /EbZyM1BJz3oyaEK8iRtHU3OaTmBW1i/jzJY2dz/p5o4swKMb2b7B1RWfGIWJCCqlagD uJ/WL6e1h8/smNLde0trCVbizjNgNJG28VOsk=
MIME-Version: 1.0
Received: by 10.227.154.66 with SMTP id n2mr2731234wbw.3.1318001617409; Fri, 07 Oct 2011 08:33:37 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Fri, 7 Oct 2011 08:33:37 -0700 (PDT)
In-Reply-To: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
Date: Fri, 7 Oct 2011 23:33:37 +0800
Message-ID: <CAM+vMEQnGu0QG55wGJS_igtuK9US9+S_=LiUtUFEQfmDa_dY9w@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Alain Durand <adurand@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "softwires@ietf.org list" <softwires@ietf.org>, Ole Troan <ot@cisco.com>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 07 Oct 2011 15:30:25 -0000

Hello Ole, Alain and Yong,

I'm Gang Chen from China Mobile. I also would like to join the design
team to contribute some ideas from an operator perspective.
Personally, I was working on double translation at very early time. I
hope my past design work could help to advance the work.
draft-ietf-softwire-stateless-4v6-motivation
draft-murakami-softwire-4v6-translation-00
draft-chen-softwire-4v6-pd-00

Many thanks

Gang

2011/10/7, Alain Durand <adurand@juniper.net>:
> During the Softwire interim meeting in Beijing last week, multiple address
> and port mapping technologies were presented for either encapsulation or
> double translation.
> There was a consensus that those technologies could and should converge. To
> achieve this, we would like to formally announce the creation of the MAP
> (Mapping of Addresses and Ports) design team.
>
> This design team is tasked to formulate a unified format is to be used
> either in an encapsulation or double translation mode, for both hub & spokes
> and mesh models.
>
> Ole Troan will be leading the effort and will report at the Taipei IETF.
>
> Please send Ole, Yong and Alain a note if you intend to participate.
>
> Alain & Yong, Softwire co-chairs.
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

From sarikaya2012@gmail.com  Fri Oct  7 08:55:21 2011
Return-Path: <sarikaya2012@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 2194721F8C50 for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 08:55:21 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F9pw-C1Jq43B for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 08:55:20 -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 5DD5D21F8C4B for <softwires@ietf.org>; Fri,  7 Oct 2011 08:55:20 -0700 (PDT)
Received: by gyd12 with SMTP id 12so4550098gyd.31 for <softwires@ietf.org>; Fri, 07 Oct 2011 08:58:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=awDKMdymPqUjM9bMNoEFIG2dy+iiBrua0sGGwhuyjwU=; b=kI/kk0ipUw3AuYuypfYM5rxRooPqQ7AXND1sBwI+sWRnAhidNr8Q245XZG+mn1lkaN AfG9pcATvTg5eXQIRj1fqDVzoOxUYB2ONlTRnBxCmiFB4B8jobLLer2CaEAxRvxQ+L5x /zavpktowd+jD8PK2czZTZIoY+VkOWwNTSEcI=
MIME-Version: 1.0
Received: by 10.236.181.35 with SMTP id k23mr10954285yhm.93.1318003114108; Fri, 07 Oct 2011 08:58:34 -0700 (PDT)
Received: by 10.236.108.180 with HTTP; Fri, 7 Oct 2011 08:58:34 -0700 (PDT)
In-Reply-To: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
Date: Fri, 7 Oct 2011 10:58:34 -0500
Message-ID: <CAC8QAceAu-Vrr5mBmHC=8mW2GLdS8fK7_vzEVhFogWrkKuXmgw@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Alain Durand <adurand@juniper.net>, mohamed.boucadair@orange-ftgroup.com
Content-Type: multipart/alternative; boundary=20cf305e25096de57c04aeb783c0
Cc: "softwires@ietf.org list" <softwires@ietf.org>, Ole Troan <ot@cisco.com>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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: Fri, 07 Oct 2011 15:55:21 -0000

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

I hereby nominate Med into the design team.

Regards,

Behcet

On Thu, Oct 6, 2011 at 7:48 PM, Alain Durand <adurand@juniper.net> wrote:

> During the Softwire interim meeting in Beijing last week, multiple address
> and port mapping technologies were presented for either encapsulation or
> double translation.
> There was a consensus that those technologies could and should converge. To
> achieve this, we would like to formally announce the creation of the MAP
> (Mapping of Addresses and Ports) design team.
>
> This design team is tasked to formulate a unified format is to be used
> either in an encapsulation or double translation mode, for both hub & spokes
> and mesh models.
>
> Ole Troan will be leading the effort and will report at the Taipei IETF.
>
> Please send Ole, Yong and Alain a note if you intend to participate.
>
> Alain & Yong, Softwire co-chairs.
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

I hereby nominate Med into the design team.<br><br>Regards,<br><br>Behcet<b=
r><br><div class=3D"gmail_quote">On Thu, Oct 6, 2011 at 7:48 PM, Alain Dura=
nd <span dir=3D"ltr">&lt;<a href=3D"mailto:adurand@juniper.net" target=3D"_=
blank">adurand@juniper.net</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">During the Softwire interim meeting in Beiji=
ng last week, multiple address and port mapping technologies were presented=
 for either encapsulation or double translation.<br>


There was a consensus that those technologies could and should converge. To=
 achieve this, we would like to formally announce the creation of the MAP (=
Mapping of Addresses and Ports) design team.<br>
<br>
This design team is tasked to formulate a unified format is to be used eith=
er in an encapsulation or double translation mode, for both hub &amp; spoke=
s and mesh models.<br>
<br>
Ole Troan will be leading the effort and will report at the Taipei IETF.<br=
>
<br>
Please send Ole, Yong and Alain a note if you intend to participate.<br>
<br>
Alain &amp; Yong, Softwire co-chairs.<br>
_______________________________________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org" target=3D"_blank">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>
</blockquote></div><br>

--20cf305e25096de57c04aeb783c0--

From phdgang@gmail.com  Fri Oct  7 09:15:18 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 1305421F8C70 for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 09:15:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.554
X-Spam-Level: 
X-Spam-Status: No, score=-3.554 tagged_above=-999 required=5 tests=[AWL=0.045,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9oWxB7WKcyT for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 09:15:17 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id D384921F8C6D for <softwires@ietf.org>; Fri,  7 Oct 2011 09:15:16 -0700 (PDT)
Received: by wwf22 with SMTP id 22so4348654wwf.13 for <softwires@ietf.org>; Fri, 07 Oct 2011 09:18:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=dE7nGGesWqBg3deUpVYAsC6ac4wtUBlWa9limsYg+lE=; b=Uc376u9oQ/VeY47/joiusIHDo4wcOr3h+Rp7KTMZ7IvXWG1wVr0rr6ZyMcxaAEnjux fGIXelCcTm6xoZXyWxejks44RCWhStqzLJ3SYbvMWsk6aY0LGR4k4e91m+C96tcfL5F4 ZST5NAv8ouHU+yIxwoLZKXJP8LxHcUBuMYCDQ=
MIME-Version: 1.0
Received: by 10.227.142.140 with SMTP id q12mr2782864wbu.18.1318004308936; Fri, 07 Oct 2011 09:18:28 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Fri, 7 Oct 2011 09:18:28 -0700 (PDT)
In-Reply-To: <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com>
Date: Sat, 8 Oct 2011 00:18:28 +0800
Message-ID: <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Congxiao Bao <cx.cernet@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 07 Oct 2011 16:15:18 -0000

Hello Congxiao, Maoke,

Please see my reply inline.

2011/10/6, Congxiao Bao <cx.cernet@gmail.com>:
> Hi, Gang, Maoke
>
> 2011/10/6 Maoke <fibrib@gmail.com>
>
>> hi Gang,
>>
>> trying to understand your point, may i follow your message inline? sorry
>> if
>> my questions are trial/naive.
>>
>>  2011/10/6 GangChen <phdgang@gmail.com>
>>
>>> Hello Congxiao,
>>>
>>> Thanks for the discussion.
>>> Please see my reply inline.
>>>
>>> 2011/10/5, Congxiao Bao <cx.cernet@gmail.com>:
>>> >> > There are no necessary to put IPv4 and Port-set ID information in
>>> last
>>> >> > 64 bits.
>>> >>
>>> >> The CE Pv6 prefix included in the /64 Subnet prefix isn't self
>>> delimited,
>>> >> so that the length of the CE index can't be determined in this part =
of
>>> the
>>> >> address.
>>> >> Having the length of the A or A+P prefix in the IID completes what i=
s
>>> >> needed to derive the CE port-set.
>>> >
>>> > Besides, if a medium or large size ISP can=92t get short enough IPv6
>>> prefix
>>> > (ex. /24), the first 64 bits can not contain the whole IPv4 32 bits,
>>> which
>>> > cannot make the double translation successful.
>>>
>>> I guess that is depending on a specific algorithm. I don't see such
>>> limitation in 4v6
>>> translation(
>>> http://tools.ietf.org/html/draft-murakami-softwire-4v6-translation-00)
>>>
>>>
>> i couldn't understand why we "don't see such limitation in 4v6
>> translation". 4via6 translate the private ipv4 address with 4rd mapping
>> rule
>> while the public ipv4 address with RFC6052 algorithm, right? can the bot=
h
>> case work fine if an ISP can only get a fairly long IPv6 prefix, like /4=
0
>> or
>> even longer?
>>
>
> Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 address =
and
> PSID in the first 64 bits?
>
4v6 translation doesn=92t need to embed whole 32 bits IPv4 address
according to the algorithm. Please take look EA-bits usage in
http://tools.ietf.org/html/draft-murakami-softwire-4rd-01 for more
details


>>>
>>> > The ISP is not able to achieve per-host traffic control without a
>>> standard
>>> > defining last 64 bits. If the ISP does, why not use IPv4+psid in suff=
ix
>>> > naturally instead of other new bits definition?
>>>
>>> First off, I'm not sure per-host traffic control is a common case for
>>> network operations
>>>
>>
>> i think it is common for, maybe, not any network operators but at least
>> some operators. especially for those running middle-to-small ISP service=
s
>> (like my company), the capability of per-host traffic control is
>> definitely
>> needed. a specific but not rare case is suppressing the pathologically
>> greedy download/upload behavior of bot-net boxes.
>>
>
> Agree.
>
>>
>>  Secondly, it could be possible to use first 64 bits differentiating
>>
>>  hosts. Please see Max PSID usage in
>>
>> http://tools.ietf.org/html/draft-despres-softwire-4rd-addmapping-01#page=
-15
>>>
>>
>> sorry but i may not yet understand the mapping algorithm. is the Rule IP=
v6
>> prefix definitely short enough to take all Max CE in the first 64 bits?

Yes, in padding case.


>> again, what if an ISP can only get a fairly long IPv6 prefix?

Can I interpret your question like how can we configure mapping
parameter if ISP only gets a fairly long IPv6 prefix? Yes. I mean that
could be possible for some ISP. However, I find that is somewhat
contradictory with requirement of prefix delegation deployment. (Note:
there are also some statements for this requirement in
draft-boucadair-softwire-stateless-requirements-00 REQ#1, REQ#4). At
least, I see all current practices are trying to encoding the
information in first 64 bits (e.g.
draft-despres-softwire-4rd-addmapping-01
draft-boucadair-behave-ipv6-portrange-04
draft-murakami-softwire-4rd-00
draft-murakami-softwire-4v6-translation-00
draft-xli-behave-divi-pd-01
draft-chen-softwire-4v6-pd-00)


>  For per-host traffic, the prefix length of ACL should be /128. In this
> case, you have to specify the value of the suffix. So different ISPs in t=
he
> IPv6 data path can implement IPv6 ACL without additional knowledge.

Again. If there is a way to identify each user in first 64 bits, why not us=
e.

Many thanks

Gang

From phdgang@gmail.com  Fri Oct  7 20:22:50 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 CBBF721F8B2A for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 20:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[AWL=-0.109, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3DuzaNBHBK5 for <softwires@ietfa.amsl.com>; Fri,  7 Oct 2011 20:22:50 -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 1854F21F8B21 for <softwires@ietf.org>; Fri,  7 Oct 2011 20:22:49 -0700 (PDT)
Received: by wyg24 with SMTP id 24so1565017wyg.31 for <softwires@ietf.org>; Fri, 07 Oct 2011 20:26:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ETJBpvzLh7FB6lM/xjaXp1abO7Ha5mYh4bV+oJeH7qQ=; b=gBYboj4gysekVczI/yGKMjf+fu1QT/IDBIjU0h5UB0HU765zyRaf+1DTtx0Kxme45w wVyEv1VSAIpY6wLdMgvp5DfeqHeBssikWRKVpGhdGV3aB3WvpoW1sz2KjljkV6gYIVBL h61tVX93Cdn/3SnYSx4qWDruyamWLGtskVjVk=
MIME-Version: 1.0
Received: by 10.216.159.1 with SMTP id r1mr1728482wek.18.1318044364622; Fri, 07 Oct 2011 20:26:04 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Fri, 7 Oct 2011 20:26:04 -0700 (PDT)
In-Reply-To: <02D4DC4B-EB93-42C6-AE9F-135B0C598F8E@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CAM+vMEQ4=xxgBgoqDAcd=t_Yx=j+wJm-rP-haJwdSxRSOv5sVQ@mail.gmail.com> <02D4DC4B-EB93-42C6-AE9F-135B0C598F8E@laposte.net>
Date: Sat, 8 Oct 2011 11:26:04 +0800
Message-ID: <CAM+vMEQipeJ2qnnVw9JcQ2U9OUxV5FYu=PDKn413B9cFXU290w@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 08 Oct 2011 03:22:50 -0000

Hello Remi,

2011/10/6, R=E9mi Despr=E9s <despres.remi@laposte.net>:
>
> Le 6 oct. 2011 =E0 06:01, GangChen a =E9crit :
>
>>
>> I understand such encoded information helps deriving a shared IPv4
>> address. However, I guess it's not necessary to dig up such
>> information if we only take traffic contronl on IPv6 data plane (as I
>> said below)
>
> I agree that it is "not necessary" to exploit this field to filter IPv4
> traffic.
>
> Yet it MAY be used to facilitate configuration of traffic control paramet=
ers
> (IPv4 addresses are expressed in clear form instead of having to be deriv=
ed
> with the help of mapping rules).

May I clarify whether such traffic control parameters are for IPv4 or
IPv6 data plane?

Many thanks

Gang

From leaf.y.yeh@huawei.com  Sat Oct  8 02:46:20 2011
Return-Path: <leaf.y.yeh@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 950FB21F8B13 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 02:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.033
X-Spam-Level: 
X-Spam-Status: No, score=-5.033 tagged_above=-999 required=5 tests=[AWL=1.566,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4EXvqnhTrWVG for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 02:46:20 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id EA26E21F8AC9 for <softwires@ietf.org>; Sat,  8 Oct 2011 02:46:19 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSQ00IWRR9KSO@szxga05-in.huawei.com> for softwires@ietf.org; Sat, 08 Oct 2011 17:48:56 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSQ00EBXR8IZI@szxga05-in.huawei.com> for softwires@ietf.org; Sat, 08 Oct 2011 17:48:56 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEC81754; Sat, 08 Oct 2011 17:48:53 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sat, 08 Oct 2011 17:48:15 +0800
Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.227]) by szxeml411-hub.china.huawei.com ([10.82.67.138]) with mapi id 14.01.0270.001; Sat, 08 Oct 2011 17:48:06 +0800
Date: Sat, 08 Oct 2011 09:48:04 +0000
From: Leaf yeh <leaf.y.yeh@huawei.com>
In-reply-to: <CAM+vMEQnGu0QG55wGJS_igtuK9US9+S_=LiUtUFEQfmDa_dY9w@mail.gmail.com>
X-Originating-IP: [10.70.39.98]
To: Alain Durand <adurand@juniper.net>, Ole Troan <ot@cisco.com>, "tomasz.mrugalski@gmail.com" <tomasz.mrugalski@gmail.com>
Message-id: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05766131@SZXEML510-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: [Softwires] MAP: Mapping of Addressees and Ports design team
Thread-index: AcyEiscCWyoVn4rOQEWfrRPpBnwNfQAOKYKAACken6A=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net> <CAM+vMEQnGu0QG55wGJS_igtuK9US9+S_=LiUtUFEQfmDa_dY9w@mail.gmail.com>
Cc: "softwires@ietf.org list" <softwires@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 08 Oct 2011 09:46:20 -0000

Hi, Ole

If you need, I can help to make efforts on the associated jobs with DHCPv6 options.


Best Regards,
Leaf


-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On Behalf Of GangChen
Sent: Friday, October 07, 2011 11:34 PM
To: Alain Durand
Cc: softwires@ietf.org list; Ole Troan; Yong Cui; Ralph Droms
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team

Hello Ole, Alain and Yong,

I'm Gang Chen from China Mobile. I also would like to join the design
team to contribute some ideas from an operator perspective.
Personally, I was working on double translation at very early time. I
hope my past design work could help to advance the work.
draft-ietf-softwire-stateless-4v6-motivation
draft-murakami-softwire-4v6-translation-00
draft-chen-softwire-4v6-pd-00

Many thanks

Gang

2011/10/7, Alain Durand <adurand@juniper.net>:
> During the Softwire interim meeting in Beijing last week, multiple address
> and port mapping technologies were presented for either encapsulation or
> double translation.
> There was a consensus that those technologies could and should converge. To
> achieve this, we would like to formally announce the creation of the MAP
> (Mapping of Addresses and Ports) design team.
>
> This design team is tasked to formulate a unified format is to be used
> either in an encapsulation or double translation mode, for both hub & spokes
> and mesh models.
>
> Ole Troan will be leading the effort and will report at the Taipei IETF.
>
> Please send Ole, Yong and Alain a note if you intend to participate.
>
> Alain & Yong, Softwire co-chairs.
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

From fibrib@gmail.com  Sat Oct  8 03:08:32 2011
Return-Path: <fibrib@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 003C721F8ABE for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 03:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level: 
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7VALVi8TOZ0m for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 03:08:31 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0BBF821F8ACA for <softwires@ietf.org>; Sat,  8 Oct 2011 03:08:30 -0700 (PDT)
Received: by qyk32 with SMTP id 32so1074758qyk.10 for <softwires@ietf.org>; Sat, 08 Oct 2011 03:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=clo9zsTki4xaNx7Ilktc1Wtwc0O17+yc+dIUlmTh4ro=; b=kParneuN40PG34SwWC3a/adHPn0YmM8JAi9kPZR6ilC/bEnb2ujd2B3gn6DFL8a4Xh k8X21lkxsYJ2fxlWQWKLZ7wyE+rYIhXtZIjM2BocuAlmg9XNiB155CxyAvaZBeI0K6GK 2jyDWOMb+BTGMjDxjFnDWmhIIW21K84vqlxxI=
MIME-Version: 1.0
Received: by 10.229.63.194 with SMTP id c2mr1453310qci.69.1318068706796; Sat, 08 Oct 2011 03:11:46 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Sat, 8 Oct 2011 03:11:46 -0700 (PDT)
In-Reply-To: <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com>
Date: Sat, 8 Oct 2011 19:11:46 +0900
Message-ID: <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: GangChen <phdgang@gmail.com>
Content-Type: multipart/alternative; boundary=0016e64fcd8a0ee6da04aec6c924
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 08 Oct 2011 10:08:32 -0000

--0016e64fcd8a0ee6da04aec6c924
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

hi Gang,

2011/10/8 GangChen <phdgang@gmail.com>

> Hello Congxiao, Maoke,
>
> Please see my reply inline.
>
> 2011/10/6, Congxiao Bao <cx.cernet@gmail.com>:
> > Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 addres=
s
> and
> > PSID in the first 64 bits?
> >
> 4v6 translation doesn=92t need to embed whole 32 bits IPv4 address
> according to the algorithm. Please take look EA-bits usage in
> http://tools.ietf.org/html/draft-murakami-softwire-4rd-01 for more
> details
>
>
i suppose Ole and Congxiao have clarified this point, right? for the double
translation, full ipv4 address is needed.


> >> sorry but i may not yet understand the mapping algorithm. is the Rule
> IPv6
> >> prefix definitely short enough to take all Max CE in the first 64 bits=
?
>
> Yes, in padding case.
>
>
what do you mean with the "yes"? do you mean having a short-enough Rule-IPv=
6
is a prerequisite for deploying 4rd-pd?

for example, a small ISP has its Rule IPv4 prefix such as 10/8, while its
total IPv6 block is a /48 or a /56 prefix only. the ISP is deploying
stateless transition, possibly 4rd-pd. is such an ISP surely able to pad
necessary part of IPv4 address in the first 64 bits?


> >> again, what if an ISP can only get a fairly long IPv6 prefix?
>
> Can I interpret your question like how can we configure mapping
> parameter if ISP only gets a fairly long IPv6 prefix? Yes. I mean that
> could be possible for some ISP.


it *could* be *possible* for *some* ISP but not for any ISP, right?


> However, I find that is somewhat
> contradictory with requirement of prefix delegation deployment. (Note:
> there are also some statements for this requirement in
> draft-boucadair-softwire-stateless-requirements-00 REQ#1, REQ#4). At
> least, I see all current practices are trying to encoding the
> information in first 64 bits (e.g.
> draft-despres-softwire-4rd-addmapping-01
> draft-boucadair-behave-ipv6-portrange-04
> draft-murakami-softwire-4rd-00
> draft-murakami-softwire-4v6-translation-00
> draft-xli-behave-divi-pd-01
> draft-chen-softwire-4v6-pd-00)
>
>
i don't think all current practices are "trying to encode the information i=
n
the first 64bits". to my humble understanding, at least divi-pd encodes the
IPv4 full address information, which identifies a specific user, not in the
first 64 bits.


>
> >  For per-host traffic, the prefix length of ACL should be /128. In this
> > case, you have to specify the value of the suffix. So different ISPs in
> the
> > IPv6 data path can implement IPv6 ACL without additional knowledge.
>
> Again. If there is a way to identify each user in first 64 bits, why not
> use.
>
>
in your proposal draft-chen-softwire-4v6-pd-00, you have

  Delegated IPv6 prefix =3D IPv6 prefix + Add set + Port set

where your Add-set is (32 - IPv4_pref_len) long, right? if the IPv4_pref_le=
n
=3D 8 while the IPv6_prefix_len =3D 48, can your first 64bits identify a us=
er?

thanks and regards,
maoke


> Many thanks
>
> Gang
>

--0016e64fcd8a0ee6da04aec6c924
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

hi Gang,=A0<div><br><div class=3D"gmail_quote">2011/10/8 GangChen <span dir=
=3D"ltr">&lt;<a href=3D"mailto:phdgang@gmail.com">phdgang@gmail.com</a>&gt;=
</span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex;">
Hello Congxiao, Maoke,<br>
<div class=3D"im"><br>
Please see my reply inline.<br>
<br>
</div>2011/10/6, Congxiao Bao &lt;<a href=3D"mailto:cx.cernet@gmail.com">cx=
.cernet@gmail.com</a>&gt;:<br>
<div><div></div><div class=3D"h5">&gt; Yes, if ISP has /32 IPv6 address, th=
en how to embed 32 bits IPv4 address and<br>
&gt; PSID in the first 64 bits?<br>
&gt;<br>
</div></div>4v6 translation doesn=92t need to embed whole 32 bits IPv4 addr=
ess<br>
according to the algorithm. Please take look EA-bits usage in<br>
<a href=3D"http://tools.ietf.org/html/draft-murakami-softwire-4rd-01" targe=
t=3D"_blank">http://tools.ietf.org/html/draft-murakami-softwire-4rd-01</a> =
for more<br>
details<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>i suppose Ole =
and Congxiao have clarified this point, right? for the double translation, =
full ipv4 address is needed.</div><div><br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex;">
<div class=3D"im"><br>
&gt;&gt; sorry but i may not yet understand the mapping algorithm. is the R=
ule IPv6<br>
&gt;&gt; prefix definitely short enough to take all Max CE in the first 64 =
bits?<br>
<br>
</div>Yes, in padding case.<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>what do you me=
an with the &quot;yes&quot;? do you mean having a short-enough Rule-IPv6 is=
 a prerequisite for deploying 4rd-pd?=A0</div><div><br></div><div>for examp=
le, a small ISP has its Rule IPv4 prefix such as 10/8, while its total IPv6=
 block is a /48 or a /56 prefix only. the ISP is deploying stateless transi=
tion, possibly 4rd-pd. is such an ISP surely able to pad necessary part of =
IPv4 address in the first 64 bits?=A0</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"im">
<br>
&gt;&gt; again, what if an ISP can only get a fairly long IPv6 prefix?<br>
<br>
</div>Can I interpret your question like how can we configure mapping<br>
parameter if ISP only gets a fairly long IPv6 prefix? Yes. I mean that<br>
could be possible for some ISP. </blockquote><div><br></div><div>it *could*=
 be *possible* for *some* ISP but not for any ISP, right?=A0</div><div>=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex;">
However, I find that is somewhat<br>
contradictory with requirement of prefix delegation deployment. (Note:<br>
there are also some statements for this requirement in<br>
draft-boucadair-softwire-stateless-requirements-00 REQ#1, REQ#4). At<br>
least, I see all current practices are trying to encoding the<br>
information in first 64 bits (e.g.<br>
draft-despres-softwire-4rd-addmapping-01<br>
draft-boucadair-behave-ipv6-portrange-04<br>
draft-murakami-softwire-4rd-00<br>
draft-murakami-softwire-4v6-translation-00<br>
draft-xli-behave-divi-pd-01<br>
draft-chen-softwire-4v6-pd-00)<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>i don&#39;t th=
ink all current practices are &quot;trying to encode the information in the=
 first 64bits&quot;. to my humble understanding, at least divi-pd encodes t=
he IPv4 full address information, which identifies a specific user, not in =
the first 64 bits.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"im">
<br>
&gt; =A0For per-host traffic, the prefix length of ACL should be /128. In t=
his<br>
&gt; case, you have to specify the value of the suffix. So different ISPs i=
n the<br>
&gt; IPv6 data path can implement IPv6 ACL without additional knowledge.<br=
>
<br>
</div>Again. If there is a way to identify each user in first 64 bits, why =
not use.<br>
<br></blockquote><div><br></div><div>in your proposal draft-chen-softwire-4=
v6-pd-00, you have=A0</div><div><br></div><div>=A0=A0Delegated IPv6 prefix =
=3D IPv6 prefix + Add set + Port set</div><div><br></div><div>where your Ad=
d-set is (32 - IPv4_pref_len) long, right? if the IPv4_pref_len =3D 8 while=
 the IPv6_prefix_len =3D 48, can your first 64bits identify a user?=A0</div=
>
<div><br></div><div>thanks and regards,</div><div>maoke</div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
Many thanks<br>
<br>
Gang<br>
</blockquote></div><br></div>

--0016e64fcd8a0ee6da04aec6c924--

From jacni@jacni.com  Sat Oct  8 03:14:23 2011
Return-Path: <jacni@jacni.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 63FB721F8AD2 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 03:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.621
X-Spam-Level: 
X-Spam-Status: No, score=-0.621 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, SARE_RECV_IP_222064=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pohO8oyav5ee for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 03:14:22 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE2E21F8876 for <softwires@ietf.org>; Sat,  8 Oct 2011 03:14:21 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 41A7938001E for <softwires@ietf.org>; Sat,  8 Oct 2011 06:17:36 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 003D2340110 for <softwires@ietf.org>; Sat,  8 Oct 2011 18:17:33 +0800 (CST)
Received: from [192.168.1.4] (unknown [222.65.34.251]) by app (Coremail) with SMTP id +AWowJBrywM3I5BOUg4VAA--.27738S2; Sat, 08 Oct 2011 18:17:33 +0800 (CST)
Message-ID: <4E9023A1.5050304@jacni.com>
Date: Sat, 08 Oct 2011 18:19:13 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: Alain Durand <adurand@juniper.net>
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
In-Reply-To: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>
Content-Type: multipart/alternative; boundary="------------080101040203090807060109"
X-CM-TRANSID: +AWowJBrywM3I5BOUg4VAA--.27738S2
X-Coremail-Antispam: 1UD129KBjvdXoW7Jr1fGFykXFy8Kry7tw1fJFb_yoWDJrg_uw 48Ka18JrWUAFy7Ka1xCFs8Xwnru3y0g340yrWqqas7Zry8ZFs3tw4vqryj93WxG3y8Ary5 Cr1kur1UCw13WjkaLaAFLSUrUUUUjb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUj5xYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF 6F4UM7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1ln4vEF7Iv6F18KV Aqrcv_GVWUtr1rJF1ln4vEIxkG6c02xx0F6c8GOVWUtr18Jw1lnx0Ec2IEnICE548m6r1D JrWUZwAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64 vIr41lc7I2V7IY0VAS07AlzVAYIcxG8wCY1x0262kKe7AKxVWUAVWUtwCF04k20xvY0x0E wIxGrwCFI7vE0wC2zVAF1VAY17CE14v26r126r1DMIIYrxkI7VAKI48JYxBIdaVFxhVjvj DU0xZFpf9x07jeLvNUUUUU=
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEPEko7lOcqiAAAs9
Cc: "softwires@ietf.org list" <softwires@ietf.org>, Ole Troan <ot@cisco.com>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 08 Oct 2011 10:14:23 -0000

This is a multi-part message in MIME format.
--------------080101040203090807060109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hi Ole and chairs,

I'd like to join, thanks.


Cheers,
Jacni

On 10/7/2011 8:48 AM, Alain Durand wrote:
> During the Softwire interim meeting in Beijing last week, multiple address and port mapping technologies were presented for either encapsulation or double translation.
> There was a consensus that those technologies could and should converge. To achieve this, we would like to formally announce the creation of the MAP (Mapping of Addresses and Ports) design team.
>
> This design team is tasked to formulate a unified format is to be used either in an encapsulation or double translation mode, for both hub&  spokes and mesh models.
>
> Ole Troan will be leading the effort and will report at the Taipei IETF.
>
> Please send Ole, Yong and Alain a note if you intend to participate.
>
> Alain&  Yong, Softwire co-chairs.
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

--------------080101040203090807060109
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi Ole and chairs,<br>
      <br>
      I'd like to join, thanks.<br>
      <br>
      <br>
      Cheers,<br>
      Jacni<br>
    </font><br>
    On 10/7/2011 8:48 AM, Alain Durand wrote:
    <blockquote
      cite="mid:65D270E8-3A87-437A-B403-B873728EB776@juniper.net"
      type="cite">
      <pre wrap="">During the Softwire interim meeting in Beijing last week, multiple address and port mapping technologies were presented for either encapsulation or double translation.
There was a consensus that those technologies could and should converge. To achieve this, we would like to formally announce the creation of the MAP (Mapping of Addresses and Ports) design team.

This design team is tasked to formulate a unified format is to be used either in an encapsulation or double translation mode, for both hub &amp; spokes and mesh models.

Ole Troan will be leading the effort and will report at the Taipei IETF.

Please send Ole, Yong and Alain a note if you intend to participate.

Alain &amp; Yong, Softwire co-chairs.
_______________________________________________
Softwires mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a>

</pre>
    </blockquote>
  </body>
</html>

--------------080101040203090807060109--


From tomasz.mrugalski@gmail.com  Sat Oct  8 05:40:57 2011
Return-Path: <tomasz.mrugalski@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 2E59521F8B27 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 05:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.774
X-Spam-Level: 
X-Spam-Status: No, score=-3.774 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-7T-WwX9Lbv for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 05:40:56 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 54C6E21F8B14 for <softwires@ietf.org>; Sat,  8 Oct 2011 05:40:56 -0700 (PDT)
Received: by wwf22 with SMTP id 22so4991551wwf.13 for <softwires@ietf.org>; Sat, 08 Oct 2011 05:44:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=bzMqddtSUyOGP7+VfvcufbS/FaCsYqGdva2eT6tHgHQ=; b=itGamd09HxrHUf4HKn08fivoRmCJfmAC2MjkYWdXClnXsef0ZqqPxHl3e4IfbVHEUt YpyEzwriuWxEgtN/I1FPkWKqaMqwZtE+LvFciGfdfH0zA3GAyMCHmf8y3BhO2LPEhVrI tA2u7Z+QnDvyeFaUDNo7UC9kV82IY04QAnN28=
Received: by 10.216.138.11 with SMTP id z11mr2071454wei.38.1318077850887; Sat, 08 Oct 2011 05:44:10 -0700 (PDT)
Received: from MacBook-Tomasz-Mrugalski.local (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id fj1sm17561412wbb.13.2011.10.08.05.44.08 (version=SSLv3 cipher=OTHER); Sat, 08 Oct 2011 05:44:09 -0700 (PDT)
Message-ID: <4E904597.5070505@gmail.com>
Date: Sat, 08 Oct 2011 14:44:07 +0200
From: Tomasz Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15
MIME-Version: 1.0
To: Leaf yeh <leaf.y.yeh@huawei.com>
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net>	<CAM+vMEQnGu0QG55wGJS_igtuK9US9+S_=LiUtUFEQfmDa_dY9w@mail.gmail.com> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05766131@SZXEML510-MBS.china.huawei.com>
In-Reply-To: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05766131@SZXEML510-MBS.china.huawei.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ole Troan <ot@cisco.com>, mohamed.boucadair@orange-ftgroup.com, Ralph Droms <rdroms@cisco.com>, Yong Cui <cuiyong@tsinghua.edu.cn>, "softwires@ietf.org list" <softwires@ietf.org>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 08 Oct 2011 12:40:57 -0000

On 11-10-08 11:48, Leaf yeh wrote:
> Hi, Ole
> 
> If you need, I can help to make efforts on the associated jobs with DHCPv6 options.
I would like to join this effort as well, if possible. I have experience
with DHCPv6 (maintaining or developing 3 separate implementations, wrote
several DHCPv6 drafts, one of them published as RFC, others near or
during WGLC).

In fact, I was already discussing DHCPv6 side of things with Med
Boucadair. We are both interested in working on DHCPv6 options.

It is too early to make any decisions, but it seems at least worth
considering to reuse bits and pieces from the following drafts:
draft-boucadair-dhcpv6-shared-address-option-01
draft-mrugalski-dhc-dhcpv6-4rd-00

Of course, the potential for reuse depends on decisions made by the
design team.

Cheers,
Tomek Mrugalski
ISC

> 
> 
> Best Regards,
> Leaf
> 
> 
> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On Behalf Of GangChen
> Sent: Friday, October 07, 2011 11:34 PM
> To: Alain Durand
> Cc: softwires@ietf.org list; Ole Troan; Yong Cui; Ralph Droms
> Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
> 
> Hello Ole, Alain and Yong,
> 
> I'm Gang Chen from China Mobile. I also would like to join the design
> team to contribute some ideas from an operator perspective.
> Personally, I was working on double translation at very early time. I
> hope my past design work could help to advance the work.
> draft-ietf-softwire-stateless-4v6-motivation
> draft-murakami-softwire-4v6-translation-00
> draft-chen-softwire-4v6-pd-00
> 
> Many thanks
> 
> Gang
> 
> 2011/10/7, Alain Durand <adurand@juniper.net>:
>> During the Softwire interim meeting in Beijing last week, multiple address
>> and port mapping technologies were presented for either encapsulation or
>> double translation.
>> There was a consensus that those technologies could and should converge. To
>> achieve this, we would like to formally announce the creation of the MAP
>> (Mapping of Addresses and Ports) design team.
>>
>> This design team is tasked to formulate a unified format is to be used
>> either in an encapsulation or double translation mode, for both hub & spokes
>> and mesh models.
>>
>> Ole Troan will be leading the effort and will report at the Taipei IETF.
>>
>> Please send Ole, Yong and Alain a note if you intend to participate.
>>
>> Alain & Yong, Softwire co-chairs.
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From bingxuere@gmail.com  Sat Oct  8 06:09:03 2011
Return-Path: <bingxuere@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 F11B921F8B38 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 06:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.523
X-Spam-Level: 
X-Spam-Status: No, score=-3.523 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtpGdGMMo-lA for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 06:09:03 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 473EB21F8B18 for <softwires@ietf.org>; Sat,  8 Oct 2011 06:09:03 -0700 (PDT)
Received: by iaby26 with SMTP id y26so6477714iab.31 for <softwires@ietf.org>; Sat, 08 Oct 2011 06:12:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=BY9zVLbEIKhT7xNIu4oUMFK6ESy98k7eaXj1AopLR6U=; b=IExL1BCJMXvXBjrgPSllozUywTixIetVF3MilUnfqdbHSvquNzZVyp1TbisyRr9BCT 6iZSyuiinayIEngvh7WoES1TGDBelMGdOlU/syqQAGgqIOgbv2N44Mt1LwOWCzeh/E2b 6GGt/C6ikjWXUJ1cmfDJGj7msi5Y3waF26guo=
Received: by 10.43.132.201 with SMTP id hv9mr3224734icc.4.1318079538097; Sat, 08 Oct 2011 06:12:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Sat, 8 Oct 2011 06:11:58 -0700 (PDT)
In-Reply-To: <CAH3bfABKF7d1Swt6gCBC1xH4g63DmDW=V3-209X0A-ZLGqif4A@mail.gmail.com>
References: <65D270E8-3A87-437A-B403-B873728EB776@juniper.net> <CAH3bfABKF7d1Swt6gCBC1xH4g63DmDW=V3-209X0A-ZLGqif4A@mail.gmail.com>
From: Qiong <bingxuere@gmail.com>
Date: Sat, 8 Oct 2011 21:11:58 +0800
Message-ID: <CAH3bfADys1_BFCCStVN+Cd-z00_=3sdhGStouqhNk7455_cyOg@mail.gmail.com>
To: Ole Troan <ot@cisco.com>, Alain Durand <adurand@juniper.net>,  Yong Cui <cuiyong@tsinghua.edu.cn>, softwires@ietf.org
Content-Type: multipart/alternative; boundary=20cf307d046aa76ec404aec94eeb
Cc: Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 08 Oct 2011 13:09:04 -0000

--20cf307d046aa76ec404aec94eeb
Content-Type: text/plain; charset=UTF-8

Hi, Ole and Chairs,

This is Qiong Sun from China Telecom. I have participated the design and
deployment of stateless approach for three years, both with encapsulation
and translation experience. I would like to join in the design group and
contribute my understanding and concerns for Hub & Spoke model from large
scale operators.

Several previous work might be helpful:
draft-sun-softwire-stateless-4over6-00
draft-sunq-v6ops-ivi-sp-02
draft-cui-softwire-b4-translated-ds-lite-02


Thanks in advance.

Qiong


>
> On Fri, Oct 7, 2011 at 8:48 AM, Alain Durand <adurand@juniper.net> wrote:
>
>> During the Softwire interim meeting in Beijing last week, multiple address
>> and port mapping technologies were presented for either encapsulation or
>> double translation.
>> There was a consensus that those technologies could and should converge.
>> To achieve this, we would like to formally announce the creation of the MAP
>> (Mapping of Addresses and Ports) design team.
>>
>> This design team is tasked to formulate a unified format is to be used
>> either in an encapsulation or double translation mode, for both hub & spokes
>> and mesh models.
>>
>> Ole Troan will be leading the effort and will report at the Taipei IETF.
>>
>> Please send Ole, Yong and Alain a note if you intend to participate.
>>
>> Alain & Yong, Softwire co-chairs.
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>
>
>

--20cf307d046aa76ec404aec94eeb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Ole and Chairs,<div><br></div><div>This is Qiong Sun from China Telecom=
. I have participated the design and deployment of stateless approach for t=
hree years, both with encapsulation and translation experience. I would lik=
e to join in the design group and contribute my understanding and concerns =
for Hub &amp; Spoke model from large scale operators.=C2=A0</div>

<div><br></div><div>Several previous work might be helpful:</div><div>draft=
-sun-softwire-stateless-4over6-00</div><div>draft-sunq-v6ops-ivi-sp-02</div=
><div>draft-cui-softwire-b4-translated-ds-lite-02</div><div>=C2=A0=C2=A0</d=
iv><div>

<br></div><div>Thanks in advance.</div><div><br></div><div>Qiong<br><br><di=
v class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class=3D"=
h5">

<div><br><br><div class=3D"gmail_quote">On Fri, Oct 7, 2011 at 8:48 AM, Ala=
in Durand <span dir=3D"ltr">&lt;<a href=3D"mailto:adurand@juniper.net" targ=
et=3D"_blank">adurand@juniper.net</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">During the Softwire interim meeting in Beiji=
ng last week, multiple address and port mapping technologies were presented=
 for either encapsulation or double translation.<br>



There was a consensus that those technologies could and should converge. To=
 achieve this, we would like to formally announce the creation of the MAP (=
Mapping of Addresses and Ports) design team.<br>
<br>
This design team is tasked to formulate a unified format is to be used eith=
er in an encapsulation or double translation mode, for both hub &amp; spoke=
s and mesh models.<br>
<br>
Ole Troan will be leading the effort and will report at the Taipei IETF.<br=
>
<br>
Please send Ole, Yong and Alain a note if you intend to participate.<br>
<br>
Alain &amp; Yong, Softwire co-chairs.<br>
_______________________________________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org" target=3D"_blank">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>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--20cf307d046aa76ec404aec94eeb--

From jacni@jacni.com  Sat Oct  8 07:41:52 2011
Return-Path: <jacni@jacni.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 7EF4A21F8B9E for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 07:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.621
X-Spam-Level: 
X-Spam-Status: No, score=-0.621 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, SARE_RECV_IP_222064=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZ4DIL11ZGxs for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 07:41:51 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 0EDFF21F8B95 for <softwires@ietf.org>; Sat,  8 Oct 2011 07:41:50 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id D1BE1380075 for <softwires@ietf.org>; Sat,  8 Oct 2011 10:45:04 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 0C0EC340125 for <softwires@ietf.org>; Sat,  8 Oct 2011 22:45:00 +0800 (CST)
Received: from [192.168.1.4] (unknown [222.65.34.251]) by app (Coremail) with SMTP id +AWowJDbUQLqYZBOqTAVAA--.28594S2; Sat, 08 Oct 2011 22:44:58 +0800 (CST)
Message-ID: <4E906254.8070402@jacni.com>
Date: Sat, 08 Oct 2011 22:46:44 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: Congxiao Bao <cx.cernet@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com>
In-Reply-To: <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090700060800040608020201"
X-CM-TRANSID: +AWowJDbUQLqYZBOqTAVAA--.28594S2
X-Coremail-Antispam: 1UD129KBjvJXoW3WF1UKF13Gr17Cry5trWkJFb_yoWxCFWDpr WfGa13GF4UJr1rCws7Xw4UGr1Yyr4fJw15JF15tr93ur90vr18tw4jkryrG34DXryrJr4U trWUCr4UZan8ZrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUcYb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VWxJwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK64x0aVW7Gw IE548m6rI_Jw1UWr17M2kK6IIYrVAqxI0j4VAqrcv_Jw1UGr1DM2vj6xkI62vS6c8GOVWU tr1rJFylYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UM4x0Y48IcV AKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI 7VAKI48JMxCIbVAxMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr4UvcSsGvfC2Kf nxnUUI43ZEXa7IU0q-e7UUUUU==
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQIPEko7lOc2jAAAsm
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 08 Oct 2011 14:41:52 -0000

This is a multi-part message in MIME format.
--------------090700060800040608020201
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

hi,

Inline please,

On 10/5/2011 5:42 PM, Congxiao Bao wrote:
> Hi,
>
> 2011/10/5 Rémi Després <despres.remi@laposte.net 
> <mailto:despres.remi@laposte.net>>
>
>     ..
>     >
>     > I'm trying to put some comments for such unified address mapping.
>     > Regarding the deterministic benefit for double translation, I
>     guess we
>     > only could use V bits to achieve.
>
>
>     Right.
>     V is indeed a reliable tool for this.
>
> If ISP wants to use a single IPv6 prefix for double translation and 
> Encapsulation, V mark is need.
>
>
Sorry, I don't follow your point here. If there is only one host behind 
the CE, why do we enable both encapsulation and translation modes? Or 
you're talking about the case where a prefix is assigned? Even in this 
case, do we really want parts of the hosts to live on translation, while 
the others live on encapsulation?

>
>     > There are no necessary to put IPv4 and Port-set ID information
>     in last
>     > 64 bits.
>
>     The CE Pv6 prefix included in the /64 Subnet prefix isn't self
>     delimited, so that the length of the CE index can't be determined
>     in this part of the address.
>     Having the length of the A or A+P prefix in the IID completes what
>     is needed to derive the CE port-set.
>
> Besides, if a medium or large size ISP can’t get short enough IPv6 
> prefix (ex. /24), the first 64 bits can not contain the whole IPv4 32 
> bits, which cannot make the double translation successful.
>
>
I guess the figures were not intent to show in detail how could the IPv4 
space be derived, where maybe not the whole 32 bits are needed. Anyway, 
it's true that the original IPv4 address has to be embedded in the 
translated-address if the translation approach is employed.

>
>     > If I understand correctly, the encoded IPv4 and Port-set ID
>     could help
>     > to derive a shared/dedicated IPv4 address or IPv4 subnet from
>     the IPv6
>     > prefix.
>
>     Yes.
>     Besides, having the IPv4 address (or prefix) in clear form, and
>     with an explicit sharing ratio, facilitates maintenance at
>     essentially no cost.
>
> Agree. Having whole IPv4 address in clear form is very critical for 
> operation, like IPv6 ACL.
>
>
>     > It may help encapsulation in same cases(e.g. IPv4 based traffic
>     > classification,IPv4 ACL, etc).
>     > However, the translation case is more preferable doing pure IPv6
>     based
>     > control for the sake of simpler operation reasons (e.g. IPv6 ACL).
>     > It's desirable identifying a customer depending on first 64 bits.
>
If the ACL control is based on the first 64 bits, then that control may 
apply to encapsulation as well.


Cheers,
Jacni

>     A point is that, although some realistic deployments may ignore
>     what is made available in IIDs (at least at the beginning), some
>     others would take advantage of it.
>     A standard with a straightforward and unified format is AFAIK
>     better than several variants, at least for documentation,
>     training, maintenance etc.
>
>     Note also that even with a single standard, it remains possible to
>     add optional variants if found useful for some deployments.
>
> The ISP is not able to achieve per-host traffic control without a 
> standard defining last 64 bits. If the ISP does, why not use IPv4+psid 
> in suffix naturally instead of other new bits definition?
>
> Best,
>
> Congxiao
>
>
>     Hope it clarifies.
>
>
>     Regards,
>     RD
>
>
>     >
>     > Many thanks
>     >
>     >
>     >
>     > Gang
>     >
>     > 2011/10/4, Rémi Després <despres.remi@laposte.net
>     <mailto:despres.remi@laposte.net>>:
>     >> Hi all,
>     >>
>     >> 1.
>     >> Here is a unified Address Mapping, for both encapsulation and
>     >> double-translation approaches, that is PROPOSED for IPv4
>     residual deployment
>     >> across IPv6-only routing domains.
>     >>
>     >> It results from an informal meeting among participants having
>     different
>     >> preferences between double-translation and encapsulation
>     solutions (Xing Li,
>     >> Congxiao Bao, Wojciech Dec, myself, at the end of the Beijing
>     meeting).
>     >>
>     >> The idea is to have a common format that is good for both types of
>     >> solutions.
>     >> In particular:
>     >> - It enriches Double translation by introducing a deterministic
>     way to
>     >> distinguish a translated IPv4 packet from a native IPv6 packet.
>     >> - It enriches Encapsulation by expressing, in clear format
>     within an IPv6
>     >> address, an IPv4 address, an IPv4 prefix, or an IPv4 address +
>     port-set ID.
>     >>
>     >>
>     >> 2.
>     >> (a)
>     >> The IPv6 Source address of an IPv4 packet from a CE is:
>     >>
>     >> a1- If the CE has an exclusive or shared IPv4 address:
>     >>
>     >> <--------- 64 ------------><8 ><------ L >= 32 -------><48-L><8 >
>     >> +-------------+--------+---+---+----------------+------+-----+---+
>     >> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>     >> +-------------+--------+---+---+----------------+------+-----+---+
>     >>
>     >> a2- If the CE has an IPv4 prefix:
>     >>
>     >> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
>     >> +-------------+--------+---+---+-------------+---------------+---+
>     >> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
>     >> +-------------+--------+---+---+-------------+---------------+---+
>     >>
>     >> (b)
>     >> V is the mark that characterizes IPv6 packets that are in
>     reality IPv4
>     >> packets.
>     >> Its value differs from any permitted value of this octet in
>     IPv6 IIDs  (ref
>     >> RFC 4291).
>     >>
>     >> It is understood that, if double Translation coexists with single
>     >> translation, concerned ISPs may notify their CEs to use the U
>     octet of RFC
>     >> 6052 instead of V.
>     >>
>     >> An unambiguous mark is fortunately possible because currently
>     permitted IIDs
>     >> have in their first octet either bit6 = 0 (the "u" bit"), or
>     bit6 = 1 and
>     >> bit7= 0 (the "g" bit).
>     >> With V having "u" = 1 (signifying Universal scope) AND "g" = 1,
>     distinction
>     >> is therefore deterministic.
>     >>
>     >> The proposed V is = 00000011.
>     >> (With other values of this octet, other IID formats can be
>     defined in case
>     >> some would be useful in the future.)
>     >>
>     >> Note that, if and when a consensus is reached in Softwire, an
>     extension of
>     >> RFC 4291 will have to be submitted to 6MAN.
>     >>
>     >> (c)
>     >> A Destination address from a CE to the outside IPv4 Internet is:
>     >> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>     >> +--------------------------+----+---------------+------------+---+
>     >> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>     >> +--------------------------+----+---------------+------------+---+
>     >>
>     >> Note that if double-translation CEs are notified to use U
>     instead of V, the
>     >> last octet becomes 0 per RFC  6052.
>     >>
>     >>
>     >> 3.
>     >> All comments are most welcome.
>     >>
>     >> Kind regards to all,
>     >> RD
>     >>
>     >>
>     >> _______________________________________________
>     >> Softwires mailing list
>     >> Softwires@ietf.org <mailto:Softwires@ietf.org>
>     >> https://www.ietf.org/mailman/listinfo/softwires
>     >>
>     >
>
>     _______________________________________________
>     Softwires mailing list
>     Softwires@ietf.org <mailto:Softwires@ietf.org>
>     https://www.ietf.org/mailman/listinfo/softwires
>
>
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

--------------090700060800040608020201
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,<br>
      <br>
      Inline please,<br>
    </font><br>
    On 10/5/2011 5:42 PM, Congxiao Bao wrote:
    <blockquote
cite="mid:CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com"
      type="cite">Hi,<br>
      <br>
      <div class="gmail_quote">2011/10/5 Rémi Després <span dir="ltr">&lt;<a
            moz-do-not-send="true"
            href="mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;</span><br>
        <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px
          0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">..
          <div class="im">&gt;<br>
            &gt; I'm trying to put some comments for such unified
            address mapping.<br>
            &gt; Regarding the deterministic benefit for double
            translation, I guess we<br>
            &gt; only could use V bits to achieve.<br>
            <br>
          </div>
          <br>
          Right.<br>
          V is indeed a reliable tool for this.<br>
        </blockquote>
        <div><span lang="EN-US"></span> </div>
        <div><span lang="EN-US"><font face="Times New Roman" size="3">If
              ISP wants to use a single IPv6 prefix for double
              translation and Encapsulation, V mark is need.</font></span></div>
        <blockquote style="border-left: 1px solid rgb(204, 204, 204);
          margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"
          class="gmail_quote">
          <div class="im"><br>
          </div>
        </blockquote>
      </div>
    </blockquote>
    Sorry, I don't follow your point here. If there is only one host
    behind the CE, why do we enable both encapsulation and translation
    modes? Or you're talking about the case where a prefix is assigned?
    Even in this case, do we really want parts of the hosts to live on
    translation, while the others live on encapsulation?<br>
    <br>
    <blockquote
cite="mid:CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px
          0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
          <div class="im"><br>
            &gt; There are no necessary to put IPv4 and Port-set ID
            information in last<br>
            &gt; 64 bits.<br>
            <br>
          </div>
          The CE Pv6 prefix included in the /64 Subnet prefix isn't self
          delimited, so that the length of the CE index can't be
          determined in this part of the address.<br>
          Having the length of the A or A+P prefix in the IID completes
          what is needed to derive the CE port-set.<br>
        </blockquote>
        <div> </div>
        <div>
          <p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span
              lang="EN-US"><font face="Times New Roman" size="3">Besides,
                if a medium or large size ISP can’t get short enough
                IPv6 prefix (ex. /24), the first 64 bits can not contain
                the whole IPv4 32 bits, which cannot make the double
                translation successful.</font></span></p>
        </div>
        <blockquote style="border-left: 1px solid rgb(204, 204, 204);
          margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"
          class="gmail_quote">
          <div class="im"><br>
          </div>
        </blockquote>
      </div>
    </blockquote>
    I guess the figures were not intent to show in detail how could the
    IPv4 space be derived, where maybe not the whole 32 bits are needed.
    Anyway, it's true that the original IPv4 address has to be embedded
    in the translated-address if the translation approach is employed.<br>
    <br>
    <blockquote
cite="mid:CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px
          0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
          <div class="im"><br>
            &gt; If I understand correctly, the encoded IPv4 and
            Port-set ID could help<br>
            &gt; to derive a shared/dedicated IPv4 address or IPv4
            subnet from the IPv6<br>
            &gt; prefix.<br>
            <br>
          </div>
          Yes.<br>
          Besides, having the IPv4 address (or prefix) in clear form,
          and with an explicit sharing ratio, facilitates maintenance at
          essentially no cost.<br>
        </blockquote>
        <div> </div>
        <div>
          <p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span
              lang="EN-US"><font face="Times New Roman" size="3">Agree.
                Having whole IPv4 address in clear form is very critical
                for operation, like IPv6 ACL.</font></span></p>
        </div>
        <div> </div>
        <blockquote style="border-left: 1px solid rgb(204, 204, 204);
          margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"
          class="gmail_quote">
          <div class="im"><br>
            &gt; It may help encapsulation in same cases(e.g. IPv4 based
            traffic<br>
            &gt; classification,IPv4 ACL, etc).<br>
            &gt; However, the translation case is more preferable doing
            pure IPv6 based<br>
            &gt; control for the sake of simpler operation reasons (e.g.
            IPv6 ACL).<br>
            &gt; It's desirable identifying a customer depending on
            first 64 bits.<br>
            <br>
          </div>
        </blockquote>
      </div>
    </blockquote>
    If the ACL control is based on the first 64 bits, then that control
    may apply to encapsulation as well.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px
          0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">A point is
          that, although some realistic deployments may ignore what is
          made available in IIDs (at least at the beginning), some
          others would take advantage of it.<br>
          A standard with a straightforward and unified format is AFAIK
          better than several variants, at least for documentation,
          training, maintenance etc.<br>
          <br>
          Note also that even with a single standard, it remains
          possible to add optional variants if found useful for some
          deployments.<br>
        </blockquote>
        <div> </div>
        <div>
          <p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span
              lang="EN-US"><font face="Times New Roman" size="3">The ISP
                is not able to achieve per-host traffic control without
                a standard defining last 64 bits. If the ISP does, why
                not use IPv4+psid in suffix naturally instead of other
                new bits definition?</font></span></p>
          <p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span
              lang="EN-US"></span> </p>
          <p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span
              lang="EN-US"><font face="Times New Roman" size="3">Best,</font></span></p>
          <p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span
              lang="EN-US"></span> </p>
          <p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span
              lang="EN-US"><font face="Times New Roman" size="3">Congxiao</font></span></p>
        </div>
        <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px
          0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><br>
          Hope it clarifies.<br>
          <br>
          <br>
          Regards,<br>
          <font color="#888888">RD<br>
          </font>
          <div>
            <div class="h5"><br>
              <br>
              &gt;<br>
              &gt; Many thanks<br>
              &gt;<br>
              &gt;<br>
              &gt;<br>
              &gt; Gang<br>
              &gt;<br>
              &gt; 2011/10/4, Rémi Després &lt;<a moz-do-not-send="true"
                href="mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;:<br>
              &gt;&gt; Hi all,<br>
              &gt;&gt;<br>
              &gt;&gt; 1.<br>
              &gt;&gt; Here is a unified Address Mapping, for both
              encapsulation and<br>
              &gt;&gt; double-translation approaches, that is PROPOSED
              for IPv4 residual deployment<br>
              &gt;&gt; across IPv6-only routing domains.<br>
              &gt;&gt;<br>
              &gt;&gt; It results from an informal meeting among
              participants having different<br>
              &gt;&gt; preferences between double-translation and
              encapsulation solutions (Xing Li,<br>
              &gt;&gt; Congxiao Bao, Wojciech Dec, myself, at the end of
              the Beijing meeting).<br>
              &gt;&gt;<br>
              &gt;&gt; The idea is to have a common format that is good
              for both types of<br>
              &gt;&gt; solutions.<br>
              &gt;&gt; In particular:<br>
              &gt;&gt; - It enriches Double translation by introducing a
              deterministic way to<br>
              &gt;&gt; distinguish a translated IPv4 packet from a
              native IPv6 packet.<br>
              &gt;&gt; - It enriches Encapsulation by expressing, in
              clear format within an IPv6<br>
              &gt;&gt; address, an IPv4 address, an IPv4 prefix, or an
              IPv4 address + port-set ID.<br>
              &gt;&gt;<br>
              &gt;&gt;<br>
              &gt;&gt; 2.<br>
              &gt;&gt; (a)<br>
              &gt;&gt; The IPv6 Source address of an IPv4 packet from a
              CE is:<br>
              &gt;&gt;<br>
              &gt;&gt; a1- If the CE has an exclusive or shared IPv4
              address:<br>
              &gt;&gt;<br>
              &gt;&gt; &lt;--------- 64 ------------&gt;&lt;8
              &gt;&lt;------ L &gt;= 32 -------&gt;&lt;48-L&gt;&lt;8
              &gt;<br>
              &gt;&gt;
              +-------------+--------+---+---+----------------+------+-----+---+<br>
              &gt;&gt; | IPv6 prefix |CE index| 0 | V |  IPv4 address  |
              PSID |  0  | L |<br>
              &gt;&gt;
              +-------------+--------+---+---+----------------+------+-----+---+<br>
              &gt;&gt;<br>
              &gt;&gt; a2- If the CE has an IPv4 prefix:<br>
              &gt;&gt;<br>
              &gt;&gt; &lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;--
              L &lt; 32 --&gt;&lt;--- 48-L -----&gt;&lt;8 &gt;<br>
              &gt;&gt;
              +-------------+--------+---+---+-------------+---------------+---+<br>
              &gt;&gt; | IPv6 prefix |CE index| 0 | V | IPv4 prefix |  
                    0     | L |<br>
              &gt;&gt;
              +-------------+--------+---+---+-------------+---------------+---+<br>
              &gt;&gt;<br>
              &gt;&gt; (b)<br>
              &gt;&gt; V is the mark that characterizes IPv6 packets
              that are in reality IPv4<br>
              &gt;&gt; packets.<br>
              &gt;&gt; Its value differs from any permitted value of
              this octet in IPv6 IIDs  (ref<br>
              &gt;&gt; RFC 4291).<br>
              &gt;&gt;<br>
              &gt;&gt; It is understood that, if double Translation
              coexists with single<br>
              &gt;&gt; translation, concerned ISPs may notify their CEs
              to use the U octet of RFC<br>
              &gt;&gt; 6052 instead of V.<br>
              &gt;&gt;<br>
              &gt;&gt; An unambiguous mark is fortunately possible
              because currently permitted IIDs<br>
              &gt;&gt; have in their first octet either bit6 = 0 (the
              "u" bit"), or bit6 = 1 and<br>
              &gt;&gt; bit7= 0 (the "g" bit).<br>
              &gt;&gt; With V having "u" = 1 (signifying Universal
              scope) AND "g" = 1, distinction<br>
              &gt;&gt; is therefore deterministic.<br>
              &gt;&gt;<br>
              &gt;&gt; The proposed V is = 00000011.<br>
              &gt;&gt; (With other values of this octet, other IID
              formats can be defined in case<br>
              &gt;&gt; some would be useful in the future.)<br>
              &gt;&gt;<br>
              &gt;&gt; Note that, if and when a consensus is reached in
              Softwire, an extension of<br>
              &gt;&gt; RFC 4291 will have to be submitted to 6MAN.<br>
              &gt;&gt;<br>
              &gt;&gt; (c)<br>
              &gt;&gt; A Destination address from a CE to the outside
              IPv4 Internet is:<br>
              &gt;&gt; &lt;--------- 64 ------------&gt;&lt; 8
              &gt;&lt;----   32 ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;<br>
              &gt;&gt;
              +--------------------------+----+---------------+------------+---+<br>
              &gt;&gt; |     BR subnet prefix     | V  |  IPv4 address |
                   0     |32 |<br>
              &gt;&gt;
              +--------------------------+----+---------------+------------+---+<br>
              &gt;&gt;<br>
              &gt;&gt; Note that if double-translation CEs are notified
              to use U instead of V, the<br>
              &gt;&gt; last octet becomes 0 per RFC  6052.<br>
              &gt;&gt;<br>
              &gt;&gt;<br>
              &gt;&gt; 3.<br>
              &gt;&gt; All comments are most welcome.<br>
              &gt;&gt;<br>
              &gt;&gt; Kind regards to all,<br>
              &gt;&gt; RD<br>
              &gt;&gt;<br>
              &gt;&gt;<br>
              &gt;&gt; _______________________________________________<br>
              &gt;&gt; Softwires mailing list<br>
              &gt;&gt; <a moz-do-not-send="true"
                href="mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
              &gt;&gt; <a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/softwires"
                target="_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
              &gt;&gt;<br>
              &gt;<br>
              <br>
              _______________________________________________<br>
              Softwires mailing list<br>
              <a moz-do-not-send="true" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
              <a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/softwires"
                target="_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Softwires mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a>
</pre>
    </blockquote>
  </body>
</html>

--------------090700060800040608020201--


From jacni@jacni.com  Sat Oct  8 07:56:50 2011
Return-Path: <jacni@jacni.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 66E9B21F8B83 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 07:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.471
X-Spam-Level: 
X-Spam-Status: No, score=-0.471 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SARE_RECV_IP_222064=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4G+TZ+Ib4nYs for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 07:56:38 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB6D21F85A8 for <softwires@ietf.org>; Sat,  8 Oct 2011 07:56:38 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 3E8E438006D for <softwires@ietf.org>; Sat,  8 Oct 2011 10:59:54 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 7F17C340096 for <softwires@ietf.org>; Sat,  8 Oct 2011 22:59:52 +0800 (CST)
Received: from [192.168.1.4] (unknown [222.65.34.251]) by app (Coremail) with SMTP id +AWowJDbPgdTZZBOezIVAA--.18759S2; Sat, 08 Oct 2011 22:59:31 +0800 (CST)
Message-ID: <4E9065BD.3050001@jacni.com>
Date: Sat, 08 Oct 2011 23:01:17 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: =?windows-1252?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net>
In-Reply-To: <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net>
Content-Type: multipart/alternative; boundary="------------030705080805010107040504"
X-CM-TRANSID: +AWowJDbPgdTZZBOezIVAA--.18759S2
X-Coremail-Antispam: 1UD129KBjvJXoW7ur18GFWxXry3Jr48CrWxWFg_yoW8uFyfpF W3tr17JF4DJw18Wr48Jw4UJr1Ykr4rJw15Jr1Dtry8WF4Yvr1Yvw17Kr18J34UXry8Jr1U tr4UJa45Jr15ArJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrn_kYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF6w4k M7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1lnx0Ec2IEnICE548m6r 1DJrWUZwAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY 64vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxk0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2 Ij64vIr41l4IxY624lx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y0x0EwIxGrbIYCTnIWIev Ja73UjIFyTuYvjxUxnN3UUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQAPEko7lOc3DQAAsk
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 08 Oct 2011 14:56:50 -0000

This is a multi-part message in MIME format.
--------------030705080805010107040504
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

hi,

Inline please,

On 10/6/2011 10:37 AM, Rémi Després wrote:
> ...
>
>> 2. Still for the destination address format, I suggest to embed PSID 
>> as well in the lower 64 bits (as in the following).
>
> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> +--------------------------+----+---------------+------------+---+
> |     BR subnet prefix     | V  |  IPv4 address | PSID |  0  | L |
> +--------------------------+----+---------------+------------+---+
>
> The reported informal agreement we had in Beijing didn't explicitly 
> cover destination addresses, and I just reported what we said, but 
> this is AFAIK the implicit direction to go to.
> Yet, there is a point to be taken into account:
> - It concerns use cases where IPv6 prefixes are assigned without any 
> relationship with IPv4 prefixes and where different sharing ratios are 
> implicitly expressed by different IPv6 prefix lengths (they aren't the 
> only use cases, but are the only ones where a flat IPv6 routing plan 
> can be used with differentiated sharing ratios).
> - For this, a BR or CE that transmits to a CE destination doesn't know 
> the exact PSID length of this CE. It only knows the maximum possible 
> length of this PSID, but this is enough for the right CE to be reached 
> (ref draft-despres-softwire-4rd-addmapping-01 sec 7.)
>
> Thus, for more generality, the format for a Destination CE would 
> rather be:
>
> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> +--------------------------+----+---------------+--------+---+---+
> |     BR subnet prefix     | V  |  IPv4 address |Max PSID| 0 | L |
> +--------------------------+----+---------------+--------+---+---+
>
> If the PSID length is known, then the Max PSID is the exact PSID, but 
> this isn't the only case.
>
I understand the "Max" PSID, based on which there will be no problem 
being routed to the destination. While I'm rethinking of it from the 
implementation perspective, the IID part the IPv6 address destined to a 
given CE should be a fixed value (the same as the IID of the "4rd 
interface" for example). Then the variable "max" PSID derived from dst. 
ports may get a problem.


Cheers,
Jacni



--------------030705080805010107040504
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,<br>
      <br>
      Inline please,<br>
    </font><br>
    On 10/6/2011 10:37 AM, Rémi Després wrote:
    <blockquote
      cite="mid:10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net"
      type="cite">...
      <div> <br>
        <blockquote type="cite">
          <div>2. Still for the destination address format, I suggest to
            embed PSID as well in the lower 64 bits (as in the
            following).</div>
        </blockquote>
        <br>
        <div>
          <div>&lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;----   32
            ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;</div>
          <div>+--------------------------+----+---------------+------------+---+</div>
          <div>|     BR subnet prefix     | V  |  IPv4 address | PSID |
             0  | L |</div>
          <div>+--------------------------+----+---------------+------------+---+ </div>
        </div>
        <div><br>
        </div>
        <div>The reported informal agreement we had in Beijing didn't
          explicitly cover destination addresses, and I just reported
          what we said, but this is AFAIK the implicit direction to go
          to.</div>
        <div>Yet, there is a point to be taken into account:</div>
        <div>- It concerns use cases where IPv6 prefixes are assigned
          without any relationship with IPv4 prefixes and where
          different sharing ratios are implicitly expressed by different
          IPv6 prefix lengths (they aren't the only use cases, but are
          the only ones where a flat IPv6 routing plan can be used with
          differentiated sharing ratios).</div>
        <div>- For this, a BR or CE that transmits to a CE destination
          doesn't know the exact PSID length of this CE. It only knows
          the maximum possible length of this PSID, but this is enough
          for the right CE to be reached (ref
          draft-despres-softwire-4rd-addmapping-01 sec 7.)</div>
        <div><br>
        </div>
        <div>Thus, for more generality, the format for a Destination CE
          would rather be:</div>
        <div><br>
        </div>
        <div>
          <div>
            <div>&lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;----  
              32 ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;</div>
            <div>+--------------------------+----+---------------+--------+---+---+</div>
            <div>|     BR subnet prefix     | V  |  IPv4 address |Max
              PSID| 0 | L |</div>
            <div>+--------------------------+----+---------------+--------+---+---+ </div>
          </div>
        </div>
        <div><br>
        </div>
        <div>If the PSID length is known, then the Max PSID is the exact
          PSID, but this isn't the only case.</div>
        <div><br>
        </div>
      </div>
    </blockquote>
    I understand the "Max" PSID, based on which there will be no problem
    being routed to the destination. While I'm rethinking of it from the
    implementation perspective, the IID part the IPv6 address destined
    to a given CE should be a fixed value (the same as the IID of the
    "4rd interface" for example). Then the variable "max" PSID derived
    from dst. ports may get a problem.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <br>
  </body>
</html>

--------------030705080805010107040504--


From jacni@jacni.com  Sat Oct  8 08:04:09 2011
Return-Path: <jacni@jacni.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 535E421F8B81 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 08:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.271
X-Spam-Level: 
X-Spam-Status: No, score=-0.271 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, SARE_RECV_IP_222064=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gG5+EjtfqO+t for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 08:04:08 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 95BB621F8B27 for <softwires@ietf.org>; Sat,  8 Oct 2011 08:04:08 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id B9D0C38006D for <softwires@ietf.org>; Sat,  8 Oct 2011 11:07:24 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id A16B434012C for <softwires@ietf.org>; Sat,  8 Oct 2011 23:07:22 +0800 (CST)
Received: from [192.168.1.4] (unknown [222.65.34.251]) by app (Coremail) with SMTP id +AWowJArCAQpZ5BOfjMVAA--.27818S2; Sat, 08 Oct 2011 23:07:21 +0800 (CST)
Message-ID: <4E906793.2080505@jacni.com>
Date: Sat, 08 Oct 2011 23:09:07 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <3C29CE19-E03A-4AC5-959A-7931FE5B9B04@employees.org> <CABv173WfM+93wRj+k1JSRdarCwXOr6q-kRrT=8p=dewDn3jn1g@mail.gmail.com> <845CF8A3-0463-4D52-A5DC-7AE697FA1208@employees.org>
In-Reply-To: <845CF8A3-0463-4D52-A5DC-7AE697FA1208@employees.org>
Content-Type: multipart/alternative; boundary="------------090505030709020405090905"
X-CM-TRANSID: +AWowJArCAQpZ5BOfjMVAA--.27818S2
X-Coremail-Antispam: 1UD129KBjvJXoW7AFykXry5AFWxGF4UCFy8Xwb_yoW8WF4UpF Z3Grs8GF4DJr18C397Xw40v34FkF1kX3WrJF15trnxCr98Wr4jyr1jk345J3y5Xr1rJw4a vrWUCFWUGay5ZrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUcYb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VWxJwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK64x0aVW7Gw IE548m6rI_Jw1UWr17M2kK6IIYrVAqxI0j4VAqrcv_Jw1UGr1DM2vj6xkI62vS6c8GOVWU tr1rJFylYx0E2Ix0cI8IcVAFwI0_JrI_JrylYx0Ex4A2jsIE14v26r1j6r4UM4x0Y48IcV AKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI 7VAKI48JMxCIbVAxMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr4UvcSsGvfC2Kf nxnUUI43ZEXa7IU038n7UUUUU==
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEPEko7lOc3UAAAs4
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 08 Oct 2011 15:04:09 -0000

This is a multi-part message in MIME format.
--------------090505030709020405090905
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

hi,

Inline please,

On 10/6/2011 10:03 PM, Ole Troan wrote:
>>> i couldn't understand why we "don't see such limitation in 4v6 translation". 4via6 translate the private ipv4 address with 4rd mapping rule while the public ipv4 address with RFC6052 algorithm, right? can the both case work fine if an ISP can only get a fairly long IPv6 prefix, like /40 or even longer?
>>>
>>> Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 address and PSID in the first 64 bits?
>> only part of the IPv4 address would be embedded into the first 64 bits (not that I think that boundary should be "hard").
>> e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. then only "1.2.3" would be embedded in the address.
>> just like what's done for 6rd.
>>
>> Thanks, Ole. That’s the point! In this case , you can only have part of the IPv4 address embedded in the first 64 bits. This embedding does work for encapsulation or tunneling, but can NOT work for stateless double translation, which requires the whole IPv4 address+PSID embeded for any IPv6 prefix length.
> right, for the outside domain traffic.
> putting the state into the IPv6 destination address doesn't affect routing.
> so this works fine with the case where you give a user a /56, where you have to have efficient encoding. for the external to the domain traffic you need to encode the full IPv4 address.
The phase to get v4 space from delegated prefix is different from 
forming IPv6 address for sending traffic.


Cheers,
Jacni

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

--------------090505030709020405090905
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,<br>
      <br>
      Inline please,<br>
    </font><br>
    On 10/6/2011 10:03 PM, Ole Troan wrote:
    <blockquote
      cite="mid:845CF8A3-0463-4D52-A5DC-7AE697FA1208@employees.org"
      type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">i couldn't understand why we "don't see such limitation in 4v6 translation". 4via6 translate the private ipv4 address with 4rd mapping rule while the public ipv4 address with RFC6052 algorithm, right? can the both case work fine if an ISP can only get a fairly long IPv6 prefix, like /40 or even longer?

Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 address and PSID in the first 64 bits?
</pre>
        </blockquote>
        <pre wrap="">
only part of the IPv4 address would be embedded into the first 64 bits (not that I think that boundary should be "hard").
e.g. if the SP has the prefix 10/8. the user the address 10.1.2.3. then only "1.2.3" would be embedded in the address.
just like what's done for 6rd.
 
Thanks, Ole. That’s the point! In this case , you can only have part of the IPv4 address embedded in the first 64 bits. This embedding does work for encapsulation or tunneling, but can NOT work for stateless double translation, which requires the whole IPv4 address+PSID embeded for any IPv6 prefix length.
</pre>
      </blockquote>
      <pre wrap="">
right, for the outside domain traffic.
putting the state into the IPv6 destination address doesn't affect routing.
so this works fine with the case where you give a user a /56, where you have to have efficient encoding. for the external to the domain traffic you need to encode the full IPv4 address.</pre>
    </blockquote>
    The phase to get v4 space from delegated prefix is different from
    forming IPv6 address for sending traffic.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
      cite="mid:845CF8A3-0463-4D52-A5DC-7AE697FA1208@employees.org"
      type="cite">
      <pre wrap="">

cheers,
Ole
_______________________________________________
Softwires mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a>

</pre>
    </blockquote>
  </body>
</html>

--------------090505030709020405090905--


From phdgang@gmail.com  Sat Oct  8 20:14:33 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 9869921F8514 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 20:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W8bihGfs+2kZ for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 20:14:33 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9D92D21F84A7 for <softwires@ietf.org>; Sat,  8 Oct 2011 20:14:24 -0700 (PDT)
Received: by wwf22 with SMTP id 22so5302596wwf.13 for <softwires@ietf.org>; Sat, 08 Oct 2011 20:14:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=fjzt5perK8PqmAplpiNcDPnlfCLiijKSEqQreGTa5/o=; b=gM0/D4lHYEP8hXC65MQbHczVjcK6zchJFB8CZRVI1GV6uNiimfYo2Mhfd7R3v5qTNI YcNb3Ux+wl2IkopIxHmfBEiNvx1k4ZQ/pu/yB+2aZ3qGuK07C2A/PJ5U3y9s6FfgK0AC aZw7srhUpHaXvmGNWTvD2ba6gR1utoZ6cCroY=
MIME-Version: 1.0
Received: by 10.227.7.159 with SMTP id d31mr4632579wbd.18.1318130064142; Sat, 08 Oct 2011 20:14:24 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Sat, 8 Oct 2011 20:14:24 -0700 (PDT)
In-Reply-To: <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com>
Date: Sun, 9 Oct 2011 11:14:24 +0800
Message-ID: <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Maoke <fibrib@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 09 Oct 2011 03:14:33 -0000

Hello Maoke,

Please see my reply inline.

2011/10/8, Maoke <fibrib@gmail.com>:
>> > Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 addre=
ss
>> and
>> > PSID in the first 64 bits?
>> >
>> 4v6 translation doesn=92t need to embed whole 32 bits IPv4 address
>> according to the algorithm. Please take look EA-bits usage in
>> http://tools.ietf.org/html/draft-murakami-softwire-4rd-01 for more
>> details
>>
>>
> i suppose Ole and Congxiao have clarified this point, right? for the doub=
le
> translation, full ipv4 address is needed.

As Ole said, "for the outside domain traffic" (Actually, I never argue
that point for that case)
Thereby, it's worth to be clarified whether need encoding whole IPv4
address, as the below table

+----------+-----------------+--------------------+
|          |source address   | destination address|
+----------+-----------------+--------------------+
|  CE-CE   |      N/A        |        N/A         |
+----------+-----------------+--------------------+
|  CE-BR   |      N/A        |        Yes         |
+----------+-----------------+--------------------+


>
>> >> sorry but i may not yet understand the mapping algorithm. is the Rule
>> IPv6
>> >> prefix definitely short enough to take all Max CE in the first 64 bit=
s?
>>
>> Yes, in padding case.
>>
>>
> what do you mean with the "yes"? do you mean having a short-enough Rule-I=
Pv6
> is a prerequisite for deploying 4rd-pd?
>
> for example, a small ISP has its Rule IPv4 prefix such as 10/8, while its
> total IPv6 block is a /48 or a /56 prefix only. the ISP is deploying
> stateless transition, possibly 4rd-pd. is such an ISP surely able to pad
> necessary part of IPv4 address in the first 64 bits?

I guess I have already put some comments on that. Please see below.

>> >> again, what if an ISP can only get a fairly long IPv6 prefix?
>>
>> Can I interpret your question like how can we configure mapping
>> parameter if ISP only gets a fairly long IPv6 prefix? Yes. I mean that
>> could be possible for some ISP.
>
>
> it *could* be *possible* for *some* ISP but not for any ISP, right?
>
>
>> However, I find that is somewhat
>> contradictory with requirement of prefix delegation deployment. (Note:
>> there are also some statements for this requirement in
>> draft-boucadair-softwire-stateless-requirements-00 REQ#1, REQ#4). At
>> least, I see all current practices are trying to encoding the
>> information in first 64 bits (e.g.
>> draft-despres-softwire-4rd-addmapping-01
>> draft-boucadair-behave-ipv6-portrange-04
>> draft-murakami-softwire-4rd-00
>> draft-murakami-softwire-4v6-translation-00
>> draft-xli-behave-divi-pd-01
>> draft-chen-softwire-4v6-pd-00)
>>
>>
> i don't think all current practices are "trying to encode the information=
 in
> the first 64bits". to my humble understanding, at least divi-pd encodes t=
he
> IPv4 full address information, which identifies a specific user, not in t=
he
> first 64 bits.

Thanks for the clarification. That is why you propose to insert full
IPv4 address?


>> >  For per-host traffic, the prefix length of ACL should be /128. In thi=
s
>> > case, you have to specify the value of the suffix. So different ISPs i=
n
>> the
>> > IPv6 data path can implement IPv6 ACL without additional knowledge.
>>
>> Again. If there is a way to identify each user in first 64 bits, why not
>> use.
>>
>>
> in your proposal draft-chen-softwire-4v6-pd-00, you have
>
>   Delegated IPv6 prefix =3D IPv6 prefix + Add set + Port set
>
> where your Add-set is (32 - IPv4_pref_len) long, right? if the IPv4_pref_=
len
> =3D 8 while the IPv6_prefix_len =3D 48, can your first 64bits identify a =
user?
>
> thanks and regards,
> maoke
>
>
>> Many thanks
>>
>> Gang
>>
>

From bingxuere@gmail.com  Sat Oct  8 20:57:56 2011
Return-Path: <bingxuere@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 57D7221F8B8E for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 20:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHf1U7650sUr for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 20:57:55 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7631D21F8BAE for <softwires@ietf.org>; Sat,  8 Oct 2011 20:57:55 -0700 (PDT)
Received: by iaby26 with SMTP id y26so7252417iab.31 for <softwires@ietf.org>; Sat, 08 Oct 2011 20:57:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Cl+CCy3QeHeBpvjOUsK5aqecr0/6G60L/Z5bm77htTY=; b=Mk29gfP7ZeQsPek/ekbQIC2WuNTV4eRTbmAxvMAm+P9Qb2AXxQQGZfwW17rMRMfTcP KN+I0Oe93lPwbleUfH+lsY1PjwqRMy0O6jcgILCmGIknQ/9MDb+skShpRiiaH3tKYefJ kCZqQxQgpIeD2eYV/ev5x9CLvMJE0tzi92vLA=
Received: by 10.42.157.3 with SMTP id b3mr7104251icx.44.1318132675184; Sat, 08 Oct 2011 20:57:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Sat, 8 Oct 2011 20:57:35 -0700 (PDT)
In-Reply-To: <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
From: Qiong <bingxuere@gmail.com>
Date: Sun, 9 Oct 2011 11:57:35 +0800
Message-ID: <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
Content-Type: multipart/alternative; boundary=90e6ba6135c2df07c204aed5ad62
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 09 Oct 2011 03:57:56 -0000

--90e6ba6135c2df07c204aed5ad62
Content-Type: text/plain; charset=UTF-8

Hi, Gang,

Please see my reply inline.

On Sun, Oct 9, 2011 at 11:14 AM, GangChen <phdgang@gmail.com> wrote:

>
> As Ole said, "for the outside domain traffic" (Actually, I never argue
> that point for that case)
> Thereby, it's worth to be clarified whether need encoding whole IPv4
> address, as the below table
>
> +----------+-----------------+--------------------+
> |          |source address   | destination address|
> +----------+-----------------+--------------------+
> |  CE-CE   |      N/A        |        N/A         |
> +----------+-----------------+--------------------+
> |  CE-BR   |      N/A        |        Yes         |
> +----------+-----------------+--------------------+
>
>
> In case you need to embed the full IPv4 address for destination address in
CE-BR, why not define a unified address format for CE-CE model. I think it
would be easier to implement and easier to achieve further traffic
identification in the same way.

Best wishes

Qiong

--90e6ba6135c2df07c204aed5ad62
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Gang,<div><br></div><div>Please see my reply inline.<br><br><div class=
=3D"gmail_quote">On Sun, Oct 9, 2011 at 11:14 AM, GangChen <span dir=3D"ltr=
">&lt;<a href=3D"mailto:phdgang@gmail.com">phdgang@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;"><div class=3D"im"><br>
</div>As Ole said, &quot;for the outside domain traffic&quot; (Actually, I =
never argue<br>
that point for that case)<br>
Thereby, it&#39;s worth to be clarified whether need encoding whole IPv4<br=
>
address, as the below table<br>
<br>
+----------+-----------------+--------------------+<br>
| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|source address =C2=A0 | destination ad=
dress|<br>
+----------+-----------------+--------------------+<br>
| =C2=A0CE-CE =C2=A0 | =C2=A0 =C2=A0 =C2=A0N/A =C2=A0 =C2=A0 =C2=A0 =C2=A0|=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0N/A =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
+----------+-----------------+--------------------+<br>
| =C2=A0CE-BR =C2=A0 | =C2=A0 =C2=A0 =C2=A0N/A =C2=A0 =C2=A0 =C2=A0 =C2=A0|=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0Yes =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
+----------+-----------------+--------------------+<br>
<div class=3D"im"><br>
<br></div></blockquote><div>In case you need to embed the full IPv4 address=
 for destination address in CE-BR, why not define a unified address format =
for CE-CE model. I think it would be easier to implement and easier to achi=
eve further traffic identification in the same way.</div>

<div><br></div><div>Best wishes</div><div><br></div><div>Qiong</div></div><=
/div>

--90e6ba6135c2df07c204aed5ad62--

From fibrib@gmail.com  Sat Oct  8 21:28:14 2011
Return-Path: <fibrib@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 CB74921F8BC3 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 21:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nmx8p070DTSf for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 21:28:14 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 18D3521F8B5D for <softwires@ietf.org>; Sat,  8 Oct 2011 21:28:14 -0700 (PDT)
Received: by qadb12 with SMTP id b12so4465150qad.31 for <softwires@ietf.org>; Sat, 08 Oct 2011 21:28:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IJpDbTbm27TvcZkHHqoThLe7heUWEy2bEhVjBxqfd6Q=; b=UfMvXTg/wBV9WxPjQJ98l3F8VWp5q170eEENadiqaINd9gCq/8XNfMnXVSGesRC5yN sLD+iLP1Brr8QM2HmbOicv/lx6FbrtzpTRP/IMLSAkYIDsWO7vUKbMT8jGiyG6jiJXue c8XWZ6QjiFt4BLpg6OJY6SW8FAW7Nadi+q8pA=
MIME-Version: 1.0
Received: by 10.229.80.16 with SMTP id r16mr2763342qck.107.1318134493523; Sat, 08 Oct 2011 21:28:13 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Sat, 8 Oct 2011 21:28:13 -0700 (PDT)
In-Reply-To: <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
Date: Sun, 9 Oct 2011 13:28:13 +0900
Message-ID: <CAFUBMqUdZ8dstRYdMjTi183737ms=na2OWpRSF6phqOK0FN9iA@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: GangChen <phdgang@gmail.com>
Content-Type: multipart/alternative; boundary=0016364ee76440b0d004aed61a94
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 09 Oct 2011 04:28:14 -0000

--0016364ee76440b0d004aed61a94
Content-Type: text/plain; charset=ISO-8859-1

hi Gang,

thanks for the reply.

2011/10/9 GangChen <phdgang@gmail.com>

> >> Yes, in padding case.
> >>
> >>
> > what do you mean with the "yes"? do you mean having a short-enough
> Rule-IPv6
> > is a prerequisite for deploying 4rd-pd?
> >
> > for example, a small ISP has its Rule IPv4 prefix such as 10/8, while its
> > total IPv6 block is a /48 or a /56 prefix only. the ISP is deploying
> > stateless transition, possibly 4rd-pd. is such an ISP surely able to pad
> > necessary part of IPv4 address in the first 64 bits?
>
> I guess I have already put some comments on that. Please see below.
>
>
do you mean you *require" every ISP surely having IPv6 prefix shorter than,
e.g., /32? may i beg you answer this question without equivocation. :)
thanks!


> > i don't think all current practices are "trying to encode the information
> in
> > the first 64bits". to my humble understanding, at least divi-pd encodes
> the
> > IPv4 full address information, which identifies a specific user, not in
> the
> > first 64 bits.
>
> Thanks for the clarification. That is why you propose to insert full
> IPv4 address?
>
>
well, i didn't propose anything new. some cases need full IPv4 addresses
while these cases are included in our discussion on the unified address
mapping.


> > in your proposal draft-chen-softwire-4v6-pd-00, you have
> >
> >   Delegated IPv6 prefix = IPv6 prefix + Add set + Port set
> >
> > where your Add-set is (32 - IPv4_pref_len) long, right? if the
> IPv4_pref_len
> > = 8 while the IPv6_prefix_len = 48, can your first 64bits identify a
> user?
> >
>

on the other hand, may you also answer this question?

thanks and regards,
maoke

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

hi Gang,=A0<div><br></div><div>thanks for the reply.=A0<br><br><div class=
=3D"gmail_quote">2011/10/9 GangChen <span dir=3D"ltr">&lt;<a href=3D"mailto=
:phdgang@gmail.com">phdgang@gmail.com</a>&gt;</span><br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
<div class=3D"im">&gt;&gt; Yes, in padding case.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt; what do you mean with the &quot;yes&quot;? do you mean having a short-=
enough Rule-IPv6<br>
&gt; is a prerequisite for deploying 4rd-pd?<br>
&gt;<br>
&gt; for example, a small ISP has its Rule IPv4 prefix such as 10/8, while =
its<br>
&gt; total IPv6 block is a /48 or a /56 prefix only. the ISP is deploying<b=
r>
&gt; stateless transition, possibly 4rd-pd. is such an ISP surely able to p=
ad<br>
&gt; necessary part of IPv4 address in the first 64 bits?<br>
<br>
</div>I guess I have already put some comments on that. Please see below.<b=
r>
<div class=3D"im"><br></div></blockquote><div><br></div><div>do you mean yo=
u *require&quot; every ISP surely having IPv6 prefix shorter than, e.g., /3=
2? may i beg you answer this question without equivocation. :) thanks!</div=
>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"im">&gt; i don&=
#39;t think all current practices are &quot;trying to encode the informatio=
n in<br>

&gt; the first 64bits&quot;. to my humble understanding, at least divi-pd e=
ncodes the<br>
&gt; IPv4 full address information, which identifies a specific user, not i=
n the<br>
&gt; first 64 bits.<br>
<br>
</div>Thanks for the clarification. That is why you propose to insert full<=
br>
IPv4 address?<br>
<div><div></div><div class=3D"h5"><br></div></div></blockquote><div><br></d=
iv><div>well, i didn&#39;t propose anything new. some cases need full IPv4 =
addresses while these cases are included in our discussion on the unified a=
ddress mapping.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div><div class=3D"h5">&gt; i=
n your proposal draft-chen-softwire-4v6-pd-00, you have<br>
&gt;<br>
&gt; =A0 Delegated IPv6 prefix =3D IPv6 prefix + Add set + Port set<br>
&gt;<br>
&gt; where your Add-set is (32 - IPv4_pref_len) long, right? if the IPv4_pr=
ef_len<br>
&gt; =3D 8 while the IPv6_prefix_len =3D 48, can your first 64bits identify=
 a user?<br>
&gt;<br></div></div></blockquote><div><br></div><div>on the other hand, may=
 you also answer this question?</div><div><br></div><div>thanks and regards=
,</div><div>maoke=A0</div></div></div>

--0016364ee76440b0d004aed61a94--

From fibrib@gmail.com  Sat Oct  8 21:31:08 2011
Return-Path: <fibrib@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 471F121F8BC3 for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 21:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EcQqhkjvUPWz for <softwires@ietfa.amsl.com>; Sat,  8 Oct 2011 21:31:07 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id B247921F8B5D for <softwires@ietf.org>; Sat,  8 Oct 2011 21:31:07 -0700 (PDT)
Received: by qyk32 with SMTP id 32so1304719qyk.10 for <softwires@ietf.org>; Sat, 08 Oct 2011 21:31:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5tomrwVDIOAPcwZrHmqYDXXC9FSV6vyx/Bfo2uQfkK8=; b=tBRZVy+JUg/BOXroLiOWz2IPRoPm353WhMo1AR+6oM4UVdcbSmTJOi3mcWbkh3TbLZ C/QsSCgFGQZ6FFN2mDv6VorAmwdUhtICrZg9/WxH9YZBnDi8EBRwy75Ia32dz+5mPCLJ irO9KfGPmReh19Yk26qPBJC9q/C7NH5EmwPsI=
MIME-Version: 1.0
Received: by 10.229.62.195 with SMTP id y3mr2780593qch.31.1318134667177; Sat, 08 Oct 2011 21:31:07 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Sat, 8 Oct 2011 21:31:06 -0700 (PDT)
In-Reply-To: <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@mail.gmail.com>
Date: Sun, 9 Oct 2011 13:31:06 +0900
Message-ID: <CAFUBMqVNScO3RnhabHcLVAHwgdRNFOEZ2=4Dfy534mzfJ=ud5g@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Qiong <bingxuere@gmail.com>
Content-Type: multipart/alternative; boundary=0016e64b1d569a70fd04aed624f0
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 09 Oct 2011 04:31:08 -0000

--0016e64b1d569a70fd04aed624f0
Content-Type: text/plain; charset=ISO-8859-1

hi Qiong,

2011/10/9 Qiong <bingxuere@gmail.com>

> Hi, Gang,
>
> Please see my reply inline.
>
> On Sun, Oct 9, 2011 at 11:14 AM, GangChen <phdgang@gmail.com> wrote:
>
>>
>> As Ole said, "for the outside domain traffic" (Actually, I never argue
>> that point for that case)
>> Thereby, it's worth to be clarified whether need encoding whole IPv4
>> address, as the below table
>>
>> +----------+-----------------+--------------------+
>> |          |source address   | destination address|
>> +----------+-----------------+--------------------+
>> |  CE-CE   |      N/A        |        N/A         |
>> +----------+-----------------+--------------------+
>> |  CE-BR   |      N/A        |        Yes         |
>> +----------+-----------------+--------------------+
>>
>>
>> In case you need to embed the full IPv4 address for destination address in
> CE-BR, why not define a unified address format for CE-CE model. I think it
> would be easier to implement and easier to achieve further traffic
> identification in the same way.
>
>
agree.

best,
maoke

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

hi Qiong,=A0<div><div><br></div><div><div class=3D"gmail_quote">2011/10/9 Q=
iong <span dir=3D"ltr">&lt;<a href=3D"mailto:bingxuere@gmail.com">bingxuere=
@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi, Gang,<div><br></div><div><div class=3D"im">Please see my reply inline.<=
br><br></div><div class=3D"gmail_quote"><div class=3D"im">On Sun, Oct 9, 20=
11 at 11:14 AM, GangChen <span dir=3D"ltr">&lt;<a href=3D"mailto:phdgang@gm=
ail.com" target=3D"_blank">phdgang@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"><div><br>
</div>As Ole said, &quot;for the outside domain traffic&quot; (Actually, I =
never argue<br>
that point for that case)<br>
Thereby, it&#39;s worth to be clarified whether need encoding whole IPv4<br=
>
address, as the below table<br>
<br>
+----------+-----------------+--------------------+<br>
| =A0 =A0 =A0 =A0 =A0|source address =A0 | destination address|<br>
+----------+-----------------+--------------------+<br>
| =A0CE-CE =A0 | =A0 =A0 =A0N/A =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0N/A =A0 =A0=
 =A0 =A0 |<br>
+----------+-----------------+--------------------+<br>
| =A0CE-BR =A0 | =A0 =A0 =A0N/A =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0Yes =A0 =A0=
 =A0 =A0 |<br>
+----------+-----------------+--------------------+<br>
<div><br>
<br></div></blockquote></div><div>In case you need to embed the full IPv4 a=
ddress for destination address in CE-BR, why not define a unified address f=
ormat for CE-CE model. I think it would be easier to implement and easier t=
o achieve further traffic identification in the same way.</div>


<div><br></div></div></div></blockquote><div><br></div><div>agree.=A0</div>=
<div><br></div><div>best,</div><div>maoke=A0</div></div></div></div>

--0016e64b1d569a70fd04aed624f0--

From dxhbupt@gmail.com  Sun Oct  9 02:57:02 2011
Return-Path: <dxhbupt@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 9953C21F8B3A for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 02:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.185
X-Spam-Level: 
X-Spam-Status: No, score=-1.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Azv0v8FLpMdO for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 02:57:02 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id D948F21F8B33 for <softwires@ietf.org>; Sun,  9 Oct 2011 02:57:01 -0700 (PDT)
Received: by wwf22 with SMTP id 22so5412891wwf.13 for <softwires@ietf.org>; Sun, 09 Oct 2011 02:57:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=knIGFKtClX+cskxLm6DOKG52/jutcFIxhmb//dDYeu8=; b=BiQGn2mYFF6lq2fUg1SfLa9fmnmT99OsRVLXa19Gl2tC/WnWQf3QxrrjNHRspJ0ZVZ nQEWW/h1pTuEfLS4Bapn6fE3wMj5ojmUNFLgKj8pBMtv8Iz/rB/V8SntRoSWDNaSl8YH oMH4ZYFe6fnbwKzFebMNCxQ9O+03EjCmFHOiQ=
MIME-Version: 1.0
Received: by 10.227.154.66 with SMTP id n2mr4872694wbw.3.1318154220962; Sun, 09 Oct 2011 02:57:00 -0700 (PDT)
Received: by 10.180.104.202 with HTTP; Sun, 9 Oct 2011 02:57:00 -0700 (PDT)
Date: Sun, 9 Oct 2011 17:57:00 +0800
Message-ID: <CANb4Oc=dRr0B8Gj=mkRDOXXniEv9GAHCC23W3YWiF6-Akxwg3w@mail.gmail.com>
From: xiaohong deng <dxhbupt@gmail.com>
To: ot@cisco.com, adurand@juniper.net, cuiyong@tsinghua.edu.cn,  softwires@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Softwires] MAP: Mapping of Addressees and Ports design team
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, 09 Oct 2011 09:57:02 -0000

Hi Ole, Alain, and Yong,

Count me in as one of volunteers of the design team, and have been a
huge advocates of design team at the first place.

Cheers,
Xiaohong

From zehn.cao@gmail.com  Sun Oct  9 04:25:15 2011
Return-Path: <zehn.cao@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 6E76D21F8492 for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 04:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GeWX7rqtJ4ZC for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 04:25:14 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id C6A7621F8485 for <softwires@ietf.org>; Sun,  9 Oct 2011 04:25:14 -0700 (PDT)
Received: by iaby26 with SMTP id y26so7658953iab.31 for <softwires@ietf.org>; Sun, 09 Oct 2011 04:25:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=0Fyjgz9d7UKqXvFmjoCg8mbRQ95lpGDXKY91ryRTlws=; b=vJuJd6w3PC4AeSUFVtRstSFY5pFdWo6Xo4HyntT7SJ9RDSzXdx45dZWJRz+ZSJgkTM sHyT8gPVkxjdeD+tGSXyiCdt8+EU7YrDcIB9iIFyRlvHkgjtoL1VHnI1pkGV8bDGvE22 gsSclGYokQuqVESvsDGx/7W1AJT0xtCxwKvvY=
MIME-Version: 1.0
Received: by 10.42.159.1 with SMTP id j1mr8975164icx.20.1318159513675; Sun, 09 Oct 2011 04:25:13 -0700 (PDT)
Received: by 10.43.52.196 with HTTP; Sun, 9 Oct 2011 04:25:13 -0700 (PDT)
In-Reply-To: <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
Date: Sun, 9 Oct 2011 19:25:13 +0800
Message-ID: <CAProHAR4_odXQAX2X90-6BhpD5YhDzOCpnPVLV4QGhb88nJOcQ@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: GangChen <phdgang@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 09 Oct 2011 11:25:15 -0000

On Sun, Oct 9, 2011 at 11:14 AM, GangChen <phdgang@gmail.com> wrote:
> Hello Maoke,
>
> Please see my reply inline.
>
> 2011/10/8, Maoke <fibrib@gmail.com>:
>>> > Yes, if ISP has /32 IPv6 address, then how to embed 32 bits IPv4 addr=
ess
>>> and
>>> > PSID in the first 64 bits?
>>> >
>>> 4v6 translation doesn=92t need to embed whole 32 bits IPv4 address
>>> according to the algorithm. Please take look EA-bits usage in
>>> http://tools.ietf.org/html/draft-murakami-softwire-4rd-01 for more
>>> details
>>>
>>>
>> i suppose Ole and Congxiao have clarified this point, right? for the dou=
ble
>> translation, full ipv4 address is needed.
>
> As Ole said, "for the outside domain traffic" (Actually, I never argue
> that point for that case)
> Thereby, it's worth to be clarified whether need encoding whole IPv4
> address, as the below table
>
> +----------+-----------------+--------------------+
> | =A0 =A0 =A0 =A0 =A0|source address =A0 | destination address|
> +----------+-----------------+--------------------+
> | =A0CE-CE =A0 | =A0 =A0 =A0N/A =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0N/A =A0 =
=A0 =A0 =A0 |
> +----------+-----------------+--------------------+
> | =A0CE-BR =A0 | =A0 =A0 =A0N/A =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0Yes =A0 =
=A0 =A0 =A0 |
> +----------+-----------------+--------------------+
>

I like this matrix, very clear for discussion and should serve as the
basis for any arguments regarding the reasons for our choice.

--=20
Best regards,
Zhen

From zehn.cao@gmail.com  Sun Oct  9 04:30:09 2011
Return-Path: <zehn.cao@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 0B76221F84C5 for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 04:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.733
X-Spam-Level: 
X-Spam-Status: No, score=-2.733 tagged_above=-999 required=5 tests=[AWL=0.866,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FLszA0anUHaL for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 04:30:08 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8EDAD21F84A9 for <softwires@ietf.org>; Sun,  9 Oct 2011 04:30:08 -0700 (PDT)
Received: by iaby26 with SMTP id y26so7663374iab.31 for <softwires@ietf.org>; Sun, 09 Oct 2011 04:30:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=F/JHkxnLjSZ49QVg9SfxazYifdq7vM+NH16qnMvYTWg=; b=YLG9eGEAJ1JYdaYv8t25ZRA7g+hWNySEc0XLARQdZ4T9yMbzzGqWbJd4Dsv4jU+1pG MeBzu/oObO4UZRq+zuQu0F03n0L2YaD7GGfTCCTOEjTklyDPGABXz/MetHCu40crQuVN 1sKL056KfItpTurpRP5ZaeKDC7BN7a6GcDKYw=
MIME-Version: 1.0
Received: by 10.42.155.202 with SMTP id v10mr8974638icw.36.1318159808200; Sun, 09 Oct 2011 04:30:08 -0700 (PDT)
Received: by 10.43.52.196 with HTTP; Sun, 9 Oct 2011 04:30:08 -0700 (PDT)
In-Reply-To: <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@mail.gmail.com>
Date: Sun, 9 Oct 2011 19:30:08 +0800
Message-ID: <CAProHARGzsxK9rUtS3p5Rr04pfkL=A4XO-AgQsz3T=smEsGBDg@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Qiong <bingxuere@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 09 Oct 2011 11:30:09 -0000

On Sun, Oct 9, 2011 at 11:57 AM, Qiong <bingxuere@gmail.com> wrote:
> Hi, Gang,
> Please see my reply inline.
>
> On Sun, Oct 9, 2011 at 11:14 AM, GangChen <phdgang@gmail.com> wrote:
>>
>> As Ole said, "for the outside domain traffic" (Actually, I never argue
>> that point for that case)
>> Thereby, it's worth to be clarified whether need encoding whole IPv4
>> address, as the below table
>>
>> +----------+-----------------+--------------------+
>> | =A0 =A0 =A0 =A0 =A0|source address =A0 | destination address|
>> +----------+-----------------+--------------------+
>> | =A0CE-CE =A0 | =A0 =A0 =A0N/A =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0N/A =A0 =
=A0 =A0 =A0 |
>> +----------+-----------------+--------------------+
>> | =A0CE-BR =A0 | =A0 =A0 =A0N/A =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0Yes =A0 =
=A0 =A0 =A0 |
>> +----------+-----------------+--------------------+
>>
>>
> In case you need to embed the full IPv4 address for destination address i=
n
> CE-BR, why not define a unified address format for CE-CE model. I think i=
t
> would be easier to implement and easier to achieve further traffic
> identification in the same way.
> Best wishes
> Qiong

I think this is a different story. For the CE-BR communication, since
the destination node is not within the domain, we can't and do not
need to use the same mapping algorithm as well as the address format
for the destination address part.  The mapping only applies to the
source address part. That's what's discussed during the interim.

--=20
Best regards,
Zhen

From phdgang@gmail.com  Sun Oct  9 04:30:47 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 899C421F8A96 for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 04:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uwh9XgrjEXB1 for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 04:30:47 -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 BF40B21F84C5 for <softwires@ietf.org>; Sun,  9 Oct 2011 04:30:46 -0700 (PDT)
Received: by wyg24 with SMTP id 24so2341686wyg.31 for <softwires@ietf.org>; Sun, 09 Oct 2011 04:30:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QwTl/4DPrbM3R5c3HOOBY2wVWWuGFFyHYbsV1pV8xPM=; b=kgDPvI10xtBsxbOAx+oRecTGwDMGaw66BGaT47/a+mG5Nx1p8EwJm2PWCF5RpB0LmH RKUkLEa3iLeJtgYDIO6fQJb3Nq1wn5uMeyA9cJN3INTApNj2u4vR4fK4maAWlOVYENt7 9W0OtprM2MfrfUaGNObfmu4OPTGPcvk2ua/E0=
MIME-Version: 1.0
Received: by 10.227.7.159 with SMTP id d31mr5006205wbd.18.1318159845935; Sun, 09 Oct 2011 04:30:45 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Sun, 9 Oct 2011 04:30:45 -0700 (PDT)
In-Reply-To: <CAFUBMqUdZ8dstRYdMjTi183737ms=na2OWpRSF6phqOK0FN9iA@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <CAFUBMqUdZ8dstRYdMjTi183737ms=na2OWpRSF6phqOK0FN9iA@mail.gmail.com>
Date: Sun, 9 Oct 2011 19:30:45 +0800
Message-ID: <CAM+vMEQJzPUwLN2w1ZfuC5vy1C5sBBbVjPnjka+eoe_t3bPxKQ@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Maoke <fibrib@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 09 Oct 2011 11:30:47 -0000

Hello Maoke,

Thanks for the discussion.
Please my reply inline.

2011/10/9, Maoke <fibrib@gmail.com>:
> hi Gang,
>
> thanks for the reply.
>
> 2011/10/9 GangChen <phdgang@gmail.com>
>
>> >> Yes, in padding case.
>> >>
>> >>
>> > what do you mean with the "yes"? do you mean having a short-enough
>> Rule-IPv6
>> > is a prerequisite for deploying 4rd-pd?
>> >
>> > for example, a small ISP has its Rule IPv4 prefix such as 10/8, while
>> > its
>> > total IPv6 block is a /48 or a /56 prefix only. the ISP is deploying
>> > stateless transition, possibly 4rd-pd. is such an ISP surely able to pad
>> > necessary part of IPv4 address in the first 64 bits?
>>
>> I guess I have already put some comments on that. Please see below.
>>
>>
> do you mean you *require" every ISP surely having IPv6 prefix shorter than,
> e.g., /32?

I'm not sure what formula you have to deduce this *requirement*.
Different sharing ratios should implicitly be expressed by different
IPv6 prefix lengths when an operator would deploy PD. At this point,
you can't help even you encode whole IPv4 address in suffix. As for
the question you raised, I think that are operational issues more than
technical issues. I take your example as explanation for your better
understanding.

A small ISP has its Rule IPv4 prefix such as 10/8, while its total
IPv6 block has fairly long prefix like /48 or a /56.

Then an operator could strategically pre-config a relatively small
IPv4 subnet to 4v6 domain as rule IPv4 prefix, like 10/24. Then you
could get more space in IPv6 prefix to put PSID information. See that
is quite flexible if you do have a good operational planning.



>may i beg you answer this question without equivocation. :)
> thanks!

Sorry for the confusion. I hope above explanation could help.

>> > i don't think all current practices are "trying to encode the
>> > information
>> in
>> > the first 64bits". to my humble understanding, at least divi-pd encodes
>> the
>> > IPv4 full address information, which identifies a specific user, not in
>> the
>> > first 64 bits.
>>
>> Thanks for the clarification. That is why you propose to insert full
>> IPv4 address?
>>
>>
> well, i didn't propose anything new. some cases need full IPv4 addresses
> while these cases are included in our discussion on the unified address
> mapping.

I only see your one case here.

>
>> > in your proposal draft-chen-softwire-4v6-pd-00, you have
>> >
>> >   Delegated IPv6 prefix = IPv6 prefix + Add set + Port set
>> >
>> > where your Add-set is (32 - IPv4_pref_len) long, right? if the
>> IPv4_pref_len
>> > = 8 while the IPv6_prefix_len = 48, can your first 64bits identify a
>> user?
>> >
>>
>
> on the other hand, may you also answer this question?

See above example. BTW, I have never said the IPv6 prefix in
draft-chen-softwire-4v6-pd-00 could identify each user.
What I said in a previous email is MAX PSID in addrmapping-01 could
help to identify a specific user. Please don't get me wrong.

Many thanks

Gang

From maxpassion@gmail.com  Sun Oct  9 10:10:04 2011
Return-Path: <maxpassion@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 2A53C21F8B37 for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 10:10:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9i-KF32lyjH for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 10:10:03 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 360EB21F8B10 for <softwires@ietf.org>; Sun,  9 Oct 2011 10:09:30 -0700 (PDT)
Received: by iaby26 with SMTP id y26so7961372iab.31 for <softwires@ietf.org>; Sun, 09 Oct 2011 10:09:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AYO6uUdh6BsKV+cMk5PgVfnn4un0pfuFLKMmVT7AKIQ=; b=lUc5xOCdR/R+ykTYcOJaEhvakMkZw/nvq8TdojV8kJ8k7K9YOPIBVGog0DuNdgPT14 6mNhD6PxfTmptGV//4+q8IEqKvdDq75LRL1NPeJDFLljeMfPJu+V0ik9yaDXNLKe1qzl 8k5xhFIy1d9IpaPmr/iJ5x5Osb6xcvuZS0nqQ=
MIME-Version: 1.0
Received: by 10.42.157.3 with SMTP id b3mr10659534icx.44.1318180165666; Sun, 09 Oct 2011 10:09:25 -0700 (PDT)
Received: by 10.42.221.5 with HTTP; Sun, 9 Oct 2011 10:09:25 -0700 (PDT)
In-Reply-To: <CAProHARGzsxK9rUtS3p5Rr04pfkL=A4XO-AgQsz3T=smEsGBDg@mail.gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@mail.gmail.com> <CAProHARGzsxK9rUtS3p5Rr04pfkL=A4XO-AgQsz3T=smEsGBDg@mail.gmail.com>
Date: Mon, 10 Oct 2011 01:09:25 +0800
Message-ID: <CAKcc6Add3j+Ugfk2qtw9yXxZxqwVsk=SFbPVim8mD+Shhvwxqg@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Zhen Cao <zehn.cao@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 09 Oct 2011 17:10:04 -0000

2011/10/9, Zhen Cao <zehn.cao@gmail.com>:
> On Sun, Oct 9, 2011 at 11:57 AM, Qiong <bingxuere@gmail.com> wrote:
>> Hi, Gang,
>> Please see my reply inline.
>>
>> On Sun, Oct 9, 2011 at 11:14 AM, GangChen <phdgang@gmail.com> wrote:
>>>
>>> As Ole said, "for the outside domain traffic" (Actually, I never argue
>>> that point for that case)
>>> Thereby, it's worth to be clarified whether need encoding whole IPv4
>>> address, as the below table
>>>
>>> +----------+-----------------+--------------------+
>>> |          |source address   | destination address|
>>> +----------+-----------------+--------------------+
>>> |  CE-CE   |      N/A        |        N/A         |
>>> +----------+-----------------+--------------------+
>>> |  CE-BR   |      N/A        |        Yes         |
>>> +----------+-----------------+--------------------+
>>>
>>>
>> In case you need to embed the full IPv4 address for destination address in
>> CE-BR, why not define a unified address format for CE-CE model. I think it
>> would be easier to implement and easier to achieve further traffic
>> identification in the same way.
>> Best wishes
>> Qiong
>
> I think this is a different story. For the CE-BR communication, since
> the destination node is not within the domain, we can't and do not
> need to use the same mapping algorithm as well as the address format
> for the destination address part.  The mapping only applies to the
> source address part. That's what's discussed during the interim.

Agree.

Regards,
Dapeng Liu


> --
> Best regards,
> Zhen
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>


-- 

------
Best Regards,
Dapeng Liu

From jacni@jacni.com  Sun Oct  9 21:46:19 2011
Return-Path: <jacni@jacni.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 BFA2A21F85B9 for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 21:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.287
X-Spam-Level: 
X-Spam-Status: No, score=-2.287 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aERr4LwrCTC4 for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 21:46:18 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id D538021F8483 for <softwires@ietf.org>; Sun,  9 Oct 2011 21:46:17 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 8B8453800A5 for <softwires@ietf.org>; Mon, 10 Oct 2011 00:46:16 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 31A0134010C for <softwires@ietf.org>; Mon, 10 Oct 2011 12:46:13 +0800 (CST)
Received: from [172.21.25.30] (unknown [221.11.61.66]) by app (Coremail) with SMTP id +AWowJALkwRzeJJOf6cWAA--.29282S2; Mon, 10 Oct 2011 12:46:10 +0800 (CST)
Message-ID: <4E9278DC.1030004@jacni.com>
Date: Mon, 10 Oct 2011 12:47:24 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: GangChen <phdgang@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <CAFUBMqUdZ8dstRYdMjTi183737ms=na2OWpRSF6phqOK0FN9iA@mail.gmail.com> <CAM+vMEQJzPUwLN2w1ZfuC5vy1C5sBBbVjPnjka+eoe_t3bPxKQ@mail.gmail.com>
In-Reply-To: <CAM+vMEQJzPUwLN2w1ZfuC5vy1C5sBBbVjPnjka+eoe_t3bPxKQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040205000104000407070700"
X-CM-TRANSID: +AWowJALkwRzeJJOf6cWAA--.29282S2
X-Coremail-Antispam: 1UD129KBjvJXoW7ZFyDAr4fKr43uFy8ArWDurg_yoW8try5pF WIq3s3tF1kKF1xZw4kZw429w4rAan0ga1UGrWrK3saywn8GFn2vr4I9w1jva98Xrn7JrnF qrWqkry5Ca1kZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrn_kYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF6w4k M7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1lnx0Ec2IEnICE548m6r 1DJrWUZwAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY 64vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxk0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2 Ij64vIr41l4IxY624lx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y0x0EwIxGrbIYCTnIWIev Ja73UjIFyTuYvjxUxnN3UUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEREko7lOfAjAAAsN
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 04:46:19 -0000

This is a multi-part message in MIME format.
--------------040205000104000407070700
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hi,

One comment on the example you proposed, please see below,

On 10/9/2011 7:30 PM, GangChen wrote:
> ...
> I'm not sure what formula you have to deduce this *requirement*.
> Different sharing ratios should implicitly be expressed by different
> IPv6 prefix lengths when an operator would deploy PD. At this point,
> you can't help even you encode whole IPv4 address in suffix. As for
> the question you raised, I think that are operational issues more than
> technical issues. I take your example as explanation for your better
> understanding.
>
> A small ISP has its Rule IPv4 prefix such as 10/8, while its total
> IPv6 block has fairly long prefix like /48 or a /56.
>
> Then an operator could strategically pre-config a relatively small
> IPv4 subnet to 4v6 domain as rule IPv4 prefix, like 10/24. Then you
> could get more space in IPv6 prefix to put PSID information. See that
> is quite flexible if you do have a good operational planning.
>
I get it, but let me try in another way.
The IPv6 addressing must not be affected, that's one of the basic 
objectives of MAP we'll agree on, right?

So, firstly the IPv6 address planning should be done natively according 
to the service requirements, the expected scale of subscribers, and the 
address space assigned respectively.
For example, if you plan to assign a /60 to each subscriber in a given 
domain with 1M subscribers totally, an IPv6 prefix of "/40" is required 
(probably shorter given the efficiency loss of hierarchical aggregation).
Then, this becomes the assumption (or restriction) on which we've got 20 
bits space to play with our art.

The next step is to decide the sharing ratio, say, 2k ports per 
subscriber, the PSID will be of 5 bits. Here the tradeoff is to use how 
many bits borrowed from ports or from the first 32 bits.
Then in this case, an IPv4 prefix of "/17" is required to accommodate 
the 1M subscribers (through "15+5").
If we're lucky to get a block of "/17", one piece of MAP rule is enough. 
Otherwise, we'll have to face another tradeoff, smaller number of rules 
or smaller number of fragmented blocks used.

ISPs' cases are quite different, while the philosophy of address 
planning is not, and should be kept in mind when we design the MAP.


Cheers,
Jacni

>

--------------040205000104000407070700
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,<br>
      <br>
      One comment on the example you proposed, please see below,<br>
    </font><br>
    On 10/9/2011 7:30 PM, GangChen wrote:
    <blockquote
cite="mid:CAM+vMEQJzPUwLN2w1ZfuC5vy1C5sBBbVjPnjka+eoe_t3bPxKQ@mail.gmail.com"
      type="cite">...
      <pre wrap="">
I'm not sure what formula you have to deduce this *requirement*.
Different sharing ratios should implicitly be expressed by different
IPv6 prefix lengths when an operator would deploy PD. At this point,
you can't help even you encode whole IPv4 address in suffix. As for
the question you raised, I think that are operational issues more than
technical issues. I take your example as explanation for your better
understanding.

A small ISP has its Rule IPv4 prefix such as 10/8, while its total
IPv6 block has fairly long prefix like /48 or a /56.

Then an operator could strategically pre-config a relatively small
IPv4 subnet to 4v6 domain as rule IPv4 prefix, like 10/24. Then you
could get more space in IPv6 prefix to put PSID information. See that
is quite flexible if you do have a good operational planning.

</pre>
    </blockquote>
    I get it, but let me try in another way.<br>
    The IPv6 addressing must not be affected, that's one of the basic
    objectives of MAP we'll agree on, right?<br>
    <br>
    So, firstly the IPv6 address planning should be done natively
    according to the service requirements, the expected scale of
    subscribers, and the address space assigned respectively.<br>
    For example, if you plan to assign a /60 to each subscriber in a
    given domain with 1M subscribers totally, an IPv6 prefix of "/40" is
    required (probably shorter given the efficiency loss of hierarchical
    aggregation).<br>
    Then, this becomes the assumption (or restriction) on which we've
    got 20 bits space to play with our art.<br>
    <br>
    The next step is to decide the sharing ratio, say, 2k ports per
    subscriber, the PSID will be of 5 bits. Here the tradeoff is to use
    how many bits borrowed from ports or from the first 32 bits.<br>
    Then in this case, an IPv4 prefix of "/17" is required to
    accommodate the 1M subscribers (through "15+5").<br>
    If we're lucky to get a block of "/17", one piece of MAP rule is
    enough. Otherwise, we'll have to face another tradeoff, smaller
    number of rules or smaller number of fragmented blocks used.<br>
    <br>
    ISPs' cases are quite different, while the philosophy of address
    planning is not, and should be kept in mind when we design the MAP.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAM+vMEQJzPUwLN2w1ZfuC5vy1C5sBBbVjPnjka+eoe_t3bPxKQ@mail.gmail.com"
      type="cite">
      <pre wrap="">

</pre>
    </blockquote>
  </body>
</html>

--------------040205000104000407070700--


From dxhbupt@gmail.com  Sun Oct  9 23:02:04 2011
Return-Path: <dxhbupt@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 CFC3B21F85F2 for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 23:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=1.207,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWvTO8g07i8C for <softwires@ietfa.amsl.com>; Sun,  9 Oct 2011 23:02:04 -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 2737821F85F7 for <softwires@ietf.org>; Sun,  9 Oct 2011 23:02:03 -0700 (PDT)
Received: by wyg24 with SMTP id 24so2862882wyg.31 for <softwires@ietf.org>; Sun, 09 Oct 2011 23:02:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=MLl4c7hDWGuLN3C+fvcvD9gaxqCNtYKJQE9tYqBcQ28=; b=DJgI6I5WWfVaiqyb6ECnZXZZ+pIaXjYCY09H4R1wkvFZkVK1RA9B8mGC4+/1+4Vydj QhK0b3iDp5hOMk/Qc/P1WnBWxc0uRrGzc6SW3TOngxlL5jTpvQt9OZWmRNkCYqrw98ih HSLsPl5Rmo0P4GUlk5aEO5hY/FJRqo4SaAuiI=
MIME-Version: 1.0
Received: by 10.227.176.70 with SMTP id bd6mr405976wbb.3.1318226523249; Sun, 09 Oct 2011 23:02:03 -0700 (PDT)
Received: by 10.180.104.202 with HTTP; Sun, 9 Oct 2011 23:02:03 -0700 (PDT)
Date: Mon, 10 Oct 2011 14:02:03 +0800
Message-ID: <CANb4Ock6gmucbc5vAj-08sq3UGz=JL9s3wm_fGnu2S+fGPTpLQ@mail.gmail.com>
From: xiaohong deng <dxhbupt@gmail.com>
To: jacni@jacni.com, phdgang@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 06:02:04 -0000

>
> ISPs' cases are quite different, while the philosophy of address
> planning is not, and should be kept in mind when we design the MAP.

Agreed.

Cheers,
Xiaohong

>
>
> Cheers,
> Jacni
>

From despres.remi@laposte.net  Mon Oct 10 00:23:17 2011
Return-Path: <despres.remi@laposte.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 2A75F21F8AF7 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 00:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IYaAGML5VXYH for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 00:23:16 -0700 (PDT)
Received: from smtpout.laposte.net (smtpout5.laposte.net [193.253.67.230]) by ietfa.amsl.com (Postfix) with ESMTP id 75BF421F8A6F for <softwires@ietf.org>; Mon, 10 Oct 2011 00:23:15 -0700 (PDT)
Received: from [192.168.0.21] ([88.166.221.144]) by mwinf8509-out with ME id ivPD1h00337Y3f403vPD6l; Mon, 10 Oct 2011 09:23:13 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAM+vMEQipeJ2qnnVw9JcQ2U9OUxV5FYu=PDKn413B9cFXU290w@mail.gmail.com>
Date: Mon, 10 Oct 2011 09:23:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9108A8B-5FEE-491B-83DE-B2A5397872A5@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CAM+vMEQ4=xxgBgoqDAcd=t_Yx=j+wJm-rP-haJwdSxRSOv5sVQ@mail.gmail.com> <02D4DC4B-EB93-42C6-AE9F-135B0C598F8E@laposte.net> <CAM+vMEQipeJ2qnnVw9JcQ2U9OUxV5FYu=PDKn413B9cFXU290w@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 07:23:17 -0000

Le 8 oct. 2011 =E0 05:26, GangChen a =E9crit :

> Hello Remi,
>=20
> 2011/10/6, R=E9mi Despr=E9s <despres.remi@laposte.net>:
>>=20
>> Le 6 oct. 2011 =E0 06:01, GangChen a =E9crit :
>>=20
>>>=20
>>> I understand such encoded information helps deriving a shared IPv4
>>> address. However, I guess it's not necessary to dig up such
>>> information if we only take traffic contronl on IPv6 data plane (as =
I
>>> said below)
>>=20
>> I agree that it is "not necessary" to exploit this field to filter =
IPv4
>> traffic.
>>=20
>> Yet it MAY be used to facilitate configuration of traffic control =
parameters
>> (IPv4 addresses are expressed in clear form instead of having to be =
derived
>> with the help of mapping rules).
>=20
> May I clarify whether such traffic control parameters are for IPv4 or
> IPv6 data plane?

As I understand it, the objective is to use existing traffic-control =
tools of IPv6 for both IPv6 AND IPv4.
This seems to me a valuable feature.=20

Regards,
RD

=20
>=20
> Many thanks
>=20
> Gang
>=20


From despres.remi@laposte.net  Mon Oct 10 00:26:31 2011
Return-Path: <despres.remi@laposte.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 0875421F853A for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 00:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2e7cvb0kJvAQ for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 00:26:30 -0700 (PDT)
Received: from smtpout.laposte.net (smtpout6.laposte.net [193.253.67.231]) by ietfa.amsl.com (Postfix) with ESMTP id C9A0021F8515 for <softwires@ietf.org>; Mon, 10 Oct 2011 00:26:29 -0700 (PDT)
Received: from [192.168.0.21] ([88.166.221.144]) by mwinf8512-out with ME id ivSP1h00637Y3f403vSPrA; Mon, 10 Oct 2011 09:26:28 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-42-621967171
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <4E9065BD.3050001@jacni.com>
Date: Mon, 10 Oct 2011 09:26:23 +0200
Message-Id: <2904870A-866E-4093-8754-3D75510B82AA@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com>
To: Jacni Qin <jacni@jacni.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 07:26:31 -0000

--Apple-Mail-42-621967171
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 8 oct. 2011 =E0 17:01, Jacni Qin a =E9crit :

> hi,
>=20
> Inline please,
>=20
> On 10/6/2011 10:37 AM, R=E9mi Despr=E9s wrote:
>>=20
>> ...
>> =20
>>> 2. Still for the destination address format, I suggest to embed PSID =
as well in the lower 64 bits (as in the following).
>>=20
>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>> +--------------------------+----+---------------+------------+---+
>> |     BR subnet prefix     | V  |  IPv4 address | PSID |  0  | L |
>> +--------------------------+----+---------------+------------+---+=20
>>=20
>> The reported informal agreement we had in Beijing didn't explicitly =
cover destination addresses, and I just reported what we said, but this =
is AFAIK the implicit direction to go to.
>> Yet, there is a point to be taken into account:
>> - It concerns use cases where IPv6 prefixes are assigned without any =
relationship with IPv4 prefixes and where different sharing ratios are =
implicitly expressed by different IPv6 prefix lengths (they aren't the =
only use cases, but are the only ones where a flat IPv6 routing plan can =
be used with differentiated sharing ratios).
>> - For this, a BR or CE that transmits to a CE destination doesn't =
know the exact PSID length of this CE. It only knows the maximum =
possible length of this PSID, but this is enough for the right CE to be =
reached (ref draft-despres-softwire-4rd-addmapping-01 sec 7.)
>>=20
>> Thus, for more generality, the format for a Destination CE would =
rather be:
>>=20
>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>> +--------------------------+----+---------------+--------+---+---+
>> |     BR subnet prefix     | V  |  IPv4 address |Max PSID| 0 | L |
>> +--------------------------+----+---------------+--------+---+---+=20
>>=20
>> If the PSID length is known, then the Max PSID is the exact PSID, but =
this isn't the only case.
>>=20
> I understand the "Max" PSID, based on which there will be no problem =
being routed to the destination. While I'm rethinking of it from the =
implementation perspective, the IID part the IPv6 address destined     =
to a given CE should be a fixed value (the same as the IID of the "4rd =
interface" for example).

The 4rd function examines ALL packets that reach the CE.
It processes all those that have V in their destination addresses, and =
only those.

The reason why 4rd packets reach the CE is NOT that their destinations =
are the IPv6 address that the CE has on its link to the ISP.=20
It is that their destinations start with the CE delegated prefix. The =
routing information base of the ISP edge router is such that, for such =
destinations, the next hop is the CE.=20


> Then the variable "max" PSID derived from dst. ports may get a =
problem.

Not AFAIK because of the above.

Hope it clarifies.
Cheers,
RD



>=20
>=20
> Cheers,
> Jacni
>=20
>=20


--Apple-Mail-42-621967171
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 8 oct. 2011 =E0 17:01, Jacni Qin a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">
 =20
    <meta content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3D"Content-Type">
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <font face=3D"Calibri">hi,<br>
      <br>
      Inline please,<br>
    </font><br>
    On 10/6/2011 10:37 AM, R=E9mi Despr=E9s wrote:
    <blockquote =
cite=3D"mid:10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net" =
type=3D"cite">...
      <div>&nbsp;<br>
        <blockquote type=3D"cite">
          <div>2. Still for the&nbsp;destination address format, I =
suggest to
            embed PSID as well in the lower 64 bits (as in the
            following).</div>
        </blockquote>
        <br>
        <div>
          <div>&lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- =
&nbsp; 32
            ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;</div>
          =
<div>+--------------------------+----+---------------+------------+---+</d=
iv>
          <div>| &nbsp; &nbsp; BR subnet prefix &nbsp; &nbsp; | V =
&nbsp;| &nbsp;IPv4 address | PSID |
            &nbsp;0 &nbsp;| L |</div>
          =
<div>+--------------------------+----+---------------+------------+---+&nb=
sp;</div>
        </div>
        <div><br>
        </div>
        <div>The reported informal agreement we had in Beijing didn't
          explicitly cover destination addresses, and I just reported
          what we said, but this is AFAIK the implicit direction to go
          to.</div>
        <div>Yet, there is a point to be taken into account:</div>
        <div>- It concerns use cases where IPv6 prefixes are assigned
          without any relationship with IPv4 prefixes and where
          different sharing ratios are implicitly expressed by different
          IPv6 prefix lengths (they aren't the only use cases, but are
          the only ones where a flat IPv6 routing plan can be used with
          differentiated sharing ratios).</div>
        <div>- For this, a BR or CE that transmits to a CE destination
          doesn't know the exact PSID length of this CE. It only knows
          the maximum possible length of this PSID, but this is enough
          for the right CE to be reached (ref
          draft-despres-softwire-4rd-addmapping-01 sec 7.)</div>
        <div><br>
        </div>
        <div>Thus, for more generality, the format for a Destination CE
          would rather be:</div>
        <div><br>
        </div>
        <div>
          <div>
            <div>&lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- =
&nbsp;
              32 ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;</div>
            =
<div>+--------------------------+----+---------------+--------+---+---+</d=
iv>
            <div>| &nbsp; &nbsp; BR subnet prefix &nbsp; &nbsp; | V =
&nbsp;| &nbsp;IPv4 address |Max
              PSID| 0 | L |</div>
            =
<div>+--------------------------+----+---------------+--------+---+---+&nb=
sp;</div>
          </div>
        </div>
        <div><br>
        </div>
        <div>If the PSID length is known, then the Max PSID is the exact
          PSID, but this isn't the only case.</div>
        <div><br>
        </div>
      </div>
    </blockquote>
    I understand the "Max" PSID, based on which there will be no problem
    being routed to the destination. While I'm rethinking of it from the
    implementation perspective, the IID part the IPv6 address destined
    to a given CE should be a fixed value (the same as the IID of the
    "4rd interface" for example). =
</div></blockquote><div><br></div><div>The 4rd function examines ALL =
packets that reach the CE.</div><div>It processes all those that have V =
in their destination addresses, and only =
those.</div><div><br></div><div>The reason why 4rd packets reach the CE =
is NOT that their destinations are the IPv6 address that the CE has on =
its link to the ISP.&nbsp;</div><div>It is that their destinations start =
with the CE delegated prefix. The routing information base of the ISP =
edge router is such that, for such destinations, the next hop is the =
CE.&nbsp;</div><div><br></div><div><br></div><blockquote =
type=3D"cite"><div bgcolor=3D"#FFFFFF" text=3D"#000000">Then the =
variable "max" PSID derived
    from dst. ports may get a =
problem.<br></div></blockquote><div><br></div>Not AFAIK because of the =
above.</div><div><br></div><div>Hope it =
clarifies.</div><div>Cheers,</div><div>RD</div><div><br></div><div><br><br=
><blockquote type=3D"cite"><div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <br>
  </div>

</blockquote></div><br></body></html>=

--Apple-Mail-42-621967171--

From jacni@jacni.com  Mon Oct 10 00:46:43 2011
Return-Path: <jacni@jacni.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 0B20F21F8507 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 00:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.208
X-Spam-Level: 
X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[AWL=-1.079, BAYES_20=-0.74, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhk8inQNbQcM for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 00:46:42 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 952A721F84FA for <softwires@ietf.org>; Mon, 10 Oct 2011 00:46:42 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 24B17380068 for <softwires@ietf.org>; Mon, 10 Oct 2011 03:46:41 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 7776234014A for <softwires@ietf.org>; Mon, 10 Oct 2011 15:46:39 +0800 (CST)
Received: from [172.21.25.30] (unknown [221.11.61.66]) by app (Coremail) with SMTP id +AWowJBrmgPFopJOytcWAA--.30163S2; Mon, 10 Oct 2011 15:46:29 +0800 (CST)
Message-ID: <4E92A32C.30306@jacni.com>
Date: Mon, 10 Oct 2011 15:47:56 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net>
In-Reply-To: <2904870A-866E-4093-8754-3D75510B82AA@laposte.net>
Content-Type: multipart/alternative; boundary="------------030409080005080904000601"
X-CM-TRANSID: +AWowJBrmgPFopJOytcWAA--.30163S2
X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjpYb7IF0VCYb41lb7IF0VCFI7km07C26c804VAK zcIF0wAYjsxI4VWDJwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2 vj6xkI62vS6c8GOVWUtr1rJFylYx0E2Ix0cI8IcVAFwI0_JrI_JrylYx0Ex4A2jsIE14v2 6r1j6r4UM4x0Y48IcVAKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCYjI0SjxkI62AI1cAE67 vIY487MxAIw28IcxkI7VAKI48JMxCIbVAxMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij 64vIr4UvcSsGvfC2KfnxnUUI43ZEXa7IU8t3vUUUUUU==
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQAREko7lOfdJwAAs6
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 07:46:43 -0000

This is a multi-part message in MIME format.
--------------030409080005080904000601
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

hi Remi,

On 10/10/2011 3:26 PM, Rémi Després wrote:
>
> ...
>
>
> The 4rd function examines ALL packets that reach the CE.
> It processes all those that have V in their destination addresses, and 
> only those.
>
This is a big change to the current forwarding behavior of CPE devices, 
doable, but quite different from, for example, some 
encapsulation/decapsulation implementations.


Cheers,
Jacni



--------------030409080005080904000601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi Remi,</font><br>
    <br>
    On 10/10/2011 3:26 PM, R&eacute;mi Despr&eacute;s wrote:
    <blockquote
      cite="mid:2904870A-866E-4093-8754-3D75510B82AA@laposte.net"
      type="cite"><br>
      <div>...
        <div bgcolor="#FFFFFF" text="#000000"><br>
        </div>
        <div><br>
        </div>
        <div>The 4rd function examines ALL packets that reach the CE.</div>
        <div>It processes all those that have V in their destination
          addresses, and only those.</div>
        <div><br>
        </div>
      </div>
    </blockquote>
    This is a big change to the current forwarding behavior of CPE
    devices, doable, but quite different from, for example, some
    encapsulation/decapsulation implementations.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <br>
  </body>
</html>

--------------030409080005080904000601--


From despres.remi@laposte.net  Mon Oct 10 00:58:28 2011
Return-Path: <despres.remi@laposte.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 7277921F8B22 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 00:58:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.123
X-Spam-Level: 
X-Spam-Status: No, score=-2.123 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mco8H0hWk8lx for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 00:58:28 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.10]) by ietfa.amsl.com (Postfix) with ESMTP id BB9E121F8B19 for <softwires@ietf.org>; Mon, 10 Oct 2011 00:58:27 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2203.sfr.fr (SMTP Server) with ESMTP id 2A2FB7000193; Mon, 10 Oct 2011 09:58:26 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2203.sfr.fr (SMTP Server) with ESMTP id 7CDDB7000191; Mon, 10 Oct 2011 09:58:22 +0200 (CEST)
X-SFR-UUID: 20111010075823511.7CDDB7000191@msfrf2203.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-43-623885974
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <4E92A32C.30306@jacni.com>
Date: Mon, 10 Oct 2011 09:58:22 +0200
Message-Id: <97DB1BBC-22A4-4076-8C94-936368B6D3DB@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <4E92A32C.30306@jacni.com>
To: Jacni Qin <jacni@jacni.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 07:58:28 -0000

--Apple-Mail-43-623885974
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 10 oct. 2011 =E0 09:47, Jacni Qin a =E9crit :

> hi Remi,
>=20
> On 10/10/2011 3:26 PM, R=E9mi Despr=E9s wrote:
>>=20
>>=20
>> ...
>>=20
>>=20
>> The 4rd function examines ALL packets that reach the CE.
>> It processes all those that have V in their destination addresses, =
and only those.
>>=20
> This is a big change to the current forwarding behavior of CPE =
devices, doable, but quite different from, for example, some =
encapsulation/decapsulation implementations.

That's new, yes, but in my understanding not so complex once you know =
what you want to do.
This is what permits to use IPv6 delegated prefixes that have no =
relationship with IPv4, and still be able to assign differentiated =
sharing ratios to CEs.

I believe this is a valuable feature of the standard to be specified.
Yet, it will be up to the WG, influenced by the design team, to decide =
to keep this feature or not.
 =20
Cheers,
RD



--Apple-Mail-43-623885974
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 10 oct. 2011 =E0 09:47, Jacni Qin a =E9crit =
:</div><br class=3D"Apple-interchange-newline"><blockquote type=3D"cite">
 =20
    <meta content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3D"Content-Type">
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <font face=3D"Calibri">hi Remi,</font><br>
    <br>
    On 10/10/2011 3:26 PM, R=E9mi Despr=E9s wrote:
    <blockquote =
cite=3D"mid:2904870A-866E-4093-8754-3D75510B82AA@laposte.net" =
type=3D"cite"><br>
      <div>...
        <div bgcolor=3D"#FFFFFF" text=3D"#000000"><br>
        </div>
        <div><br>
        </div>
        <div>The 4rd function examines ALL packets that reach the =
CE.</div>
        <div>It processes all those that have V in their destination
          addresses, and only those.</div>
        <div><br>
        </div>
      </div>
    </blockquote>
    This is a big change to the current forwarding behavior of CPE
    devices, doable, but quite different from, for example, some
    encapsulation/decapsulation =
implementations.<br></div></blockquote><div><br></div><div>That's new, =
yes, but in my understanding not so complex once you know what you want =
to do.</div><div>This is what permits to use IPv6 delegated prefixes =
that have no relationship with IPv4, and still be able to assign =
differentiated sharing ratios to CEs.</div><div><br></div><div>I believe =
this is a valuable feature of the standard to be =
specified.</div><div>Yet, it will be up to the WG, influenced by the =
design team, to decide to keep this feature or =
not.</div><div>&nbsp;&nbsp;</div><div>Cheers,</div><div>RD</div><div><br><=
/div></div><br></body></html>=

--Apple-Mail-43-623885974--

From fibrib@gmail.com  Mon Oct 10 01:40:06 2011
Return-Path: <fibrib@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 90F7621F8B2E for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 01:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G8T1Mes4dbkO for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 01:40:05 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE6221F8B2B for <softwires@ietf.org>; Mon, 10 Oct 2011 01:40:05 -0700 (PDT)
Received: by qyk32 with SMTP id 32so1696125qyk.10 for <softwires@ietf.org>; Mon, 10 Oct 2011 01:40:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rCidgMex/taXkdmIsxPZb2+mn7AKmkSxlBpWn2ycSL8=; b=hHKYFQUKaP4TFP2r1OKHIAR5eTiHjVHWhVogtB9jUjKeTyZLFk74W0L+5OCcCjeU3v rO1OXbQcV0Lh91M5ZuF6MMlIApzVMfRT4YCJoVbejyGbDuhl+GxIss2wzyYxjA7w2TcC /A8jxgJGlJ9D0QZ6r/3BjykypcigQ1o+cE3vA=
MIME-Version: 1.0
Received: by 10.229.63.194 with SMTP id c2mr2809574qci.69.1318236004109; Mon, 10 Oct 2011 01:40:04 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Mon, 10 Oct 2011 01:40:04 -0700 (PDT)
In-Reply-To: <4E9278DC.1030004@jacni.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <CAFUBMqUdZ8dstRYdMjTi183737ms=na2OWpRSF6phqOK0FN9iA@mail.gmail.com> <CAM+vMEQJzPUwLN2w1ZfuC5vy1C5sBBbVjPnjka+eoe_t3bPxKQ@mail.gmail.com> <4E9278DC.1030004@jacni.com>
Date: Mon, 10 Oct 2011 17:40:04 +0900
Message-ID: <CAFUBMqW0JXXh5GDuPv-enbHsMvyOTcZjtuTAHm6TPo+Ey=Od5g@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=0016e64fcd8ac1500704aeedbca2
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 08:40:06 -0000

--0016e64fcd8ac1500704aeedbca2
Content-Type: text/plain; charset=ISO-8859-1

hi Jacni,

thanks for the discussion from the view of address planning. it is clear.
i just would like to add an overview comment on the "philosophy".

to my understanding, the prefix length to a customer depends upon,
essentially, how many end-system identifiers are needed, according to what
we estimate, within the scope of the customer network. in the age of IPv4,
the estimation is typically expressed with a definite prefix length because
we hardly have a shorter one than what we really need. in the age of IPv6,
however, if the prefix length for a customer network in address planning is
not a fixed value but a range with relaxation, the art of address planning
may also change. (e.g., the block assigned to a subscriber is at most
/60 supporting up to 1M subscribers in total, and at least /72 in oder to
support up to 2^56 end-system identifiers within each CE-delegated network).
with this in mind, ISP may have larger room to pick up techniques and
deployment tactics possibly without doing less-necessary tradeoffs.

the same philosophy doesn't imply a unique art of action. MHO. sorry but out
of the scope of this group.

thanks a lot,
maoke

2011/10/10 Jacni Qin <jacni@jacni.com>

>  hi,
>
> One comment on the example you proposed, please see below,
>
> On 10/9/2011 7:30 PM, GangChen wrote:
>
> ...
>
> I'm not sure what formula you have to deduce this *requirement*.
> Different sharing ratios should implicitly be expressed by different
> IPv6 prefix lengths when an operator would deploy PD. At this point,
> you can't help even you encode whole IPv4 address in suffix. As for
> the question you raised, I think that are operational issues more than
> technical issues. I take your example as explanation for your better
> understanding.
>
> A small ISP has its Rule IPv4 prefix such as 10/8, while its total
> IPv6 block has fairly long prefix like /48 or a /56.
>
> Then an operator could strategically pre-config a relatively small
> IPv4 subnet to 4v6 domain as rule IPv4 prefix, like 10/24. Then you
> could get more space in IPv6 prefix to put PSID information. See that
> is quite flexible if you do have a good operational planning.
>
>
>  I get it, but let me try in another way.
> The IPv6 addressing must not be affected, that's one of the basic
> objectives of MAP we'll agree on, right?
>
> So, firstly the IPv6 address planning should be done natively according to
> the service requirements, the expected scale of subscribers, and the address
> space assigned respectively.
> For example, if you plan to assign a /60 to each subscriber in a given
> domain with 1M subscribers totally, an IPv6 prefix of "/40" is required
> (probably shorter given the efficiency loss of hierarchical aggregation).
> Then, this becomes the assumption (or restriction) on which we've got 20
> bits space to play with our art.
>
> The next step is to decide the sharing ratio, say, 2k ports per subscriber,
> the PSID will be of 5 bits. Here the tradeoff is to use how many bits
> borrowed from ports or from the first 32 bits.
> Then in this case, an IPv4 prefix of "/17" is required to accommodate the
> 1M subscribers (through "15+5").
> If we're lucky to get a block of "/17", one piece of MAP rule is enough.
> Otherwise, we'll have to face another tradeoff, smaller number of rules or
> smaller number of fragmented blocks used.
>
>
ISPs' cases are quite different, while the philosophy of address planning is
> not, and should be kept in mind when we design the MAP.
>
>

Cheers,
Jacni

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

<div>hi Jacni, </div><div>=A0</div><div>thanks for the discussion from the =
view of address planning. it is clear. i=A0just would like to add an overvi=
ew=A0comment on the &quot;philosophy&quot;. </div><div>=A0</div><div>to my =
understanding, the prefix length to a=A0customer depends upon, essentially,=
 how many end-system identifiers are needed, according to=A0what we estimat=
e,=A0within the scope of the customer network. in the age of IPv4, the esti=
mation is typically expressed with=A0a definite prefix length because we ha=
rdly have a shorter one than what we really need. in the age of IPv6, howev=
er, if the prefix length for=A0a customer network=A0in address planning is =
not a fixed value but a range with relaxation, the art of address planning =
may also change. (e.g., the=A0block=A0assigned to=A0a subscriber=A0is at mo=
st /60=A0supporting=A0up to=A01M=A0subscribers in total, and at least /72=
=A0in oder to support=A0up to=A02^56 end-system identifiers within each CE-=
delegated network). with this in mind, ISP may have larger room to pick up =
techniques and deployment tactics possibly without doing less-necessary tra=
deoffs.=A0=A0</div>

<div>=A0</div><div>the same philosophy doesn&#39;t imply a unique art of ac=
tion.=A0MHO. sorry but out of the scope of this group. </div><div>=A0</div>=
<div>thanks a lot,</div><div>maoke=A0</div><div class=3D"gmail_quote">=A0</=
div><div class=3D"gmail_quote">
2011/10/10 Jacni Qin <span dir=3D"ltr">&lt;<a href=3D"mailto:jacni@jacni.co=
m" target=3D"_blank">jacni@jacni.com</a>&gt;</span><br>


<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <font face=3D"Calibri">hi,<br>
      <br>
      One comment on the example you proposed, please see below,<br>
    </font><br>
    On 10/9/2011 7:30 PM, GangChen wrote:
    <blockquote type=3D"cite">...
      <div><pre>I&#39;m not sure what formula you have to deduce this *requ=
irement*.
Different sharing ratios should implicitly be expressed by different
IPv6 prefix lengths when an operator would deploy PD. At this point,
you can&#39;t help even you encode whole IPv4 address in suffix. As for
the question you raised, I think that are operational issues more than
technical issues. I take your example as explanation for your better
understanding.

A small ISP has its Rule IPv4 prefix such as 10/8, while its total
IPv6 block has fairly long prefix like /48 or a /56.

Then an operator could strategically pre-config a relatively small
IPv4 subnet to 4v6 domain as rule IPv4 prefix, like 10/24. Then you
could get more space in IPv6 prefix to put PSID information. See that
is quite flexible if you do have a good operational planning.

</pre>
    </div></blockquote>
    I get it, but let me try in another way.<br>
    The IPv6 addressing must not be affected, that&#39;s one of the basic
    objectives of MAP we&#39;ll agree on, right?<br>
    <br>
    So, firstly the IPv6 address planning should be done natively
    according to the service requirements, the expected scale of
    subscribers, and the address space assigned respectively.<br>
    For example, if you plan to assign a /60 to each subscriber in a
    given domain with 1M subscribers totally, an IPv6 prefix of &quot;/40&q=
uot; is
    required (probably shorter given the efficiency loss of hierarchical
    aggregation).<br>
    Then, this becomes the assumption (or restriction) on which we&#39;ve
    got 20 bits space to play with our art.<br>
    <br>
    The next step is to decide the sharing ratio, say, 2k ports per
    subscriber, the PSID will be of 5 bits. Here the tradeoff is to use
    how many bits borrowed from ports or from the first 32 bits.<br>
    Then in this case, an IPv4 prefix of &quot;/17&quot; is required to
    accommodate the 1M subscribers (through &quot;15+5&quot;).<br>
    If we&#39;re lucky to get a block of &quot;/17&quot;, one piece of MAP =
rule is
    enough. Otherwise, we&#39;ll have to face another tradeoff, smaller
    number of rules or smaller number of fragmented blocks used.<br>
=A0=A0=A0=A0</div></blockquote><blockquote style=3D"margin: 0px 0px 0px 0.8=
ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-w=
idth: 1px; border-left-style: solid;" class=3D"gmail_quote"><div text=3D"#0=
00000" bgcolor=3D"#FFFFFF">






    ISPs&#39; cases are quite different, while the philosophy of address
    planning is not, and should be kept in mind when we design the MAP.<br>
=A0=A0=A0=A0=A0</div></blockquote><div><br>
    Cheers,<br>
    Jacni<br>
    <br></div>
    <blockquote type=3D"cite">
      <pre></pre>
    </blockquote>
 =20

</div><br>

--0016e64fcd8ac1500704aeedbca2--

From ichiroumakino@gmail.com  Mon Oct 10 01:58:32 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 44C8521F8B47 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 01:58:32 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4BonSDnS14L for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 01:58:31 -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 7352A21F8B49 for <softwires@ietf.org>; Mon, 10 Oct 2011 01:58:31 -0700 (PDT)
Received: by wyg24 with SMTP id 24so3024169wyg.31 for <softwires@ietf.org>; Mon, 10 Oct 2011 01:58:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=y9MO/ccMMAW5XF/Rqmth4I0agLTfVyc0Af5QKNEYi/Y=; b=IFZWSHMQ3VRYqmz1YzaI7yPWHihE+IoGbK0Eq3kvM5ipsPHGdlEXuXro5pnpWtelsq tjsBT5nPFLv4W6x5BX4ZdNnIXKfo92lSwsnYKtEr1/MzO9CVLNP+h71pqbjbuvRs/HuC z6zGh3l98VawHLRoWhADg8YzbQhRQSVoRCJnw=
Received: by 10.227.127.203 with SMTP id h11mr5962798wbs.64.1318237110599; Mon, 10 Oct 2011 01:58:30 -0700 (PDT)
Received: from dhcp-osl-vl300-64-103-53-235.cisco.com (dhcp-osl-vl300-64-103-53-235.cisco.com. [64.103.53.235]) by mx.google.com with ESMTPS id k26sm31617177wbo.16.2011.10.10.01.58.28 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 10 Oct 2011 01:58:29 -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: <4E92A32C.30306@jacni.com>
Date: Mon, 10 Oct 2011 10:58:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8DEB256-0585-4279-BC8F-96064B4FF606@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <4E92A32C.30306@jacni.com>
To: Jacni Qin <jacni@jacni.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 08:58:32 -0000

>> The 4rd function examines ALL packets that reach the CE.
>> It processes all those that have V in their destination addresses, =
and only those.
>>=20
> This is a big change to the current forwarding behavior of CPE =
devices, doable, but quite different from, for example, some =
encapsulation/decapsulation implementations.

+1.
doable in theory, but I share your concerns.

cheers,
Ole=

From leaf.y.yeh@huawei.com  Mon Oct 10 04:35:22 2011
Return-Path: <leaf.y.yeh@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 DAE3B21F8482 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 04:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xexj8HuW3gyn for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 04:35:22 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id C6EA821F84A5 for <softwires@ietf.org>; Mon, 10 Oct 2011 04:35:21 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSU002R7LIUM0@szxga05-in.huawei.com> for softwires@ietf.org; Mon, 10 Oct 2011 19:35:18 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSU00MXVLITMJ@szxga05-in.huawei.com> for softwires@ietf.org; Mon, 10 Oct 2011 19:35:18 +0800 (CST)
Received: from szxeml206-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEI67376; Mon, 10 Oct 2011 19:35:09 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 10 Oct 2011 19:35:07 +0800
Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.227]) by szxeml403-hub.china.huawei.com ([10.82.67.35]) with mapi id 14.01.0270.001; Mon, 10 Oct 2011 19:35:00 +0800
Date: Mon, 10 Oct 2011 11:34:59 +0000
From: Leaf yeh <leaf.y.yeh@huawei.com>
In-reply-to: <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net>
X-Originating-IP: [10.70.39.98]
To: =?utf-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>, Ole Troan <otroan@employees.org>
Message-id: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
Thread-index: AQHMh0ClppljXMMUk0246OCDrJF2JQ==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net>
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 11:35:23 -0000

UmVtaSAtID4+IGExLSBJZiB0aGUgQ0UgaGFzIGFuIGV4Y2x1c2l2ZSBvciBzaGFyZWQgSVB2NCBh
ZGRyZXNzOg0KPj4gPC0tLS0tLS0tLSA2NCAtLS0tLS0tLS0tLS0+PDggPjwtLS0tLS0gTCA+PSAz
MiAtLS0tLS0tPjw0OC1MPjw4ID4NCj4+ICstLS0tLS0tLS0tLS0tKy0tLS0tLS0tKy0tLSstLS0r
LS0tLS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0rLS0tKw0KPj4gfCBJUHY2IHByZWZpeCB8Q0Ug
aW5kZXh8IDAgfCBWIHwgIElQdjQgYWRkcmVzcyAgfCBQU0lEIHwgIDAgIHwgTCB8DQo+PiArLS0t
LS0tLS0tLS0tLSstLS0tLS0tLSstLS0rLS0tKy0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tKy0tLS0t
Ky0tLSsNCk9sZSAtID4gcHV0dGluZyB0aGUgSVB2NCBhZGRyZXNzIC8gcG9ydCBpbmZvcm1hdGlv
biBhdCB0aGUgZW5kIG9mIHRoZSBpbnRlcmZhY2UgaWRlbnRpZmllciB3aWxsIGFsbG93IGZvciA+
IC82NCBzdXBwb3J0LiA+IHdoYXQncyB0aGUgTD8NClJlbWkgLSBEb24ndCBzZWUgd2hhdCB5b3Ug
Zm91bmQgdW5jbGVhci4NCg0KDQpRdWVzdGlvbjogU3VwcG9zZWQgdGhlIHF1ZXN0aW9uIGlzIG9u
IHRoZSBsYXN0IGZpZWxkLCBuYW1lZCAnTCcsIGluIHRoZSBuZXcgYWRkcmVzcyBmb3JtYXQuDQoN
Cg0KUmVtaSAtID4+IEEgRGVzdGluYXRpb24gYWRkcmVzcyBmcm9tIGEgQ0UgdG8gdGhlIG91dHNp
ZGUgSVB2NCBJbnRlcm5ldCBpczoNCj4+IDwtLS0tLS0tLS0gNjQgLS0tLS0tLS0tLS0tPjwgOCA+
PC0tLS0gICAzMiAtLS0tPjwtLS0gMTYgLS0tLT48OCA+DQo+PiArLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0rLS0tLSstLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKy0tLSsNCj4+IHwgICAg
IEJSIHN1Ym5ldCBwcmVmaXggICAgIHwgViAgfCAgSVB2NCBhZGRyZXNzIHwgICAgICAwICAgICB8
MzIgfA0KPj4gKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0rLS0tLS0tLS0tLS0tLS0t
Ky0tLS0tLS0tLS0tLSstLS0rDQpPbGUgLSB0aGlzIGlzIGEgYmlnIGNoYW5nZSBmb3IgZW5jYXBz
dWxhdGlvbiwgd2hlcmUgcHJpb3IgdG8gdGhpcyBlbmNhcHN1bGF0aW9uIG1lYW5zIHNlbmRpbmcg
dG8gYSBzaW5nbGUgZGVzdGluYXRpb24uDQpSZW1pIC0gQ29weWluZyBhbiBhdmFpbGFibGUgSVB2
NCBhZGRyZXNzIGF0IGEgZml4ZWQgcGxhY2UgaXNuJ3QgSU1ITyBhICJiaWcgY2hhbmdlIi4NCg0K
DQpDb25jZXJuOiBTdXBwb3NlZCB0aGUgcmVwbGFjZW1lbnQgb2YgdGhlIDFzdCA2NGJpdHMgb2Yg
dGhlIEJSIGFkZHJlc3Mgd2l0aCBhIHN1Ym5ldCBwcmVmaXggaXMgbm90IGZvciB0aGUgdHVubmVs
IGNhc2UgaWYgdGhlIGZpZWxkIG9mIElQdjQgYWRkcmVzcyBjYW4gYmUgdmFyaWFibGUsIHJpZ2h0
Pw0KDQpJbiBmYWN0LCBJIGRvdWJ0cyB3ZSBjb3VsZCBoYXZlIHRoZSBzYW1lIGFkZHJlc3MgbWFw
cGluZyBmb3IgYm90aCB0dW5uZWwgYW5kIHRyYW5zbGF0aW9uLiBTdXBwb3NlZCB0aGUgYWRkcmVz
cyBvZiB0dW5uZWwgZW5kLXBvaW50cyBpcyBwcmVmZXJyZWQgdG8gYmUgZml4ZWQsIGJ1dCB0aGUg
YWRkcmVzcyBmb3IgdGhlIHRyYW5zbGF0aW9uIGNvdWxkIGJlIHZhcmlhYmxlLg0KDQoNCkJlc3Qg
UmVnYXJkcywNCkxlYWYNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogc29m
dHdpcmVzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpzb2Z0d2lyZXMtYm91bmNlc0BpZXRmLm9y
Z10gT24gQmVoYWxmIE9mIFLDqW1pIERlc3Byw6lzDQpTZW50OiBUaHVyc2RheSwgT2N0b2JlciAw
NiwgMjAxMSA2OjA3IFBNDQpUbzogT2xlIFRyb2FuDQpDYzogU29mdHdpcmVzLXdnDQpTdWJqZWN0
OiBSZTogW1NvZnR3aXJlc10gUHJvcG9zZWQgVW5pZmllZCBBZGRyZXNzIE1hcHBpbmcgZm9yIGVu
Y2Fwc3VsYXRpb24gYW5kIGRvdWJsZS10cmFuc2xhdGlvbg0KDQoNCkxlIDYgb2N0LiAyMDExIMOg
IDE4OjQ3LCBPbGUgVHJvYW4gYSDDqWNyaXQgOg0KDQo+IFJlbWksDQo+IA0KPiBbLi4uXQ0KPiAN
Cj4+IDIuDQo+PiAoYSkNCj4+IFRoZSBJUHY2IFNvdXJjZSBhZGRyZXNzIG9mIGFuIElQdjQgcGFj
a2V0IGZyb20gYSBDRSBpczoNCj4+IA0KPj4gYTEtIElmIHRoZSBDRSBoYXMgYW4gZXhjbHVzaXZl
IG9yIHNoYXJlZCBJUHY0IGFkZHJlc3M6DQo+PiANCj4+IDwtLS0tLS0tLS0gNjQgLS0tLS0tLS0t
LS0tPjw4ID48LS0tLS0tIEwgPj0gMzIgLS0tLS0tLT48NDgtTD48OCA+DQo+PiArLS0tLS0tLS0t
LS0tLSstLS0tLS0tLSstLS0rLS0tKy0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tKy0tLS0tKy0tLSsN
Cj4+IHwgSVB2NiBwcmVmaXggfENFIGluZGV4fCAwIHwgViB8ICBJUHY0IGFkZHJlc3MgIHwgUFNJ
RCB8ICAwICB8IEwgfA0KPj4gKy0tLS0tLS0tLS0tLS0rLS0tLS0tLS0rLS0tKy0tLSstLS0tLS0t
LS0tLS0tLS0tKy0tLS0tLSstLS0tLSstLS0rDQo+IA0KPiBwdXR0aW5nIHRoZSBJUHY0IGFkZHJl
c3MgLyBwb3J0IGluZm9ybWF0aW9uIGF0IHRoZSBlbmQgb2YgdGhlIGludGVyZmFjZSBpZGVudGlm
aWVyIHdpbGwgYWxsb3cgZm9yID4gLzY0IHN1cHBvcnQuDQoNCkNvdWxkIHlvdSBleHBsYWluIG1v
cmUgdGhlIHJlcXVpcmVtZW50IHlvdSBoYXZlIGluIG1pbmQ/ICANCg0KPiB3aGF0J3MgdGhlIEw/
DQoNCk9uIHRoZSBwaWN0dXJlLCBMIGlzIDMyIGJpdHMgKyBMZW5ndGgoUFNJRCkuDQpEb24ndCBz
ZWUgd2hhdCB5b3UgZm91bmQgdW5jbGVhci4gDQoNCj4gDQo+IHlvdSBzdWdnZXN0IHRoYXQgdGhl
IGZpcnN0IHN1Ym5ldCBvZiBhbiBhbGxvY2F0aW9uIHNob3VsZCBiZSB1c2VkIGZvciB0aGlzIHB1
cnBvc2UuDQoNCkRpZCBJIGRvIHRoaXM/DQpQbGVhc2UgZXhwbGFpbiBiZWNhdXNlIHRoYXQncyBu
b3QsIElNSE8sICBzb21ldGhpbmcgdG8gYmUgZG9uZS4NCg0KPiB0aGUgZmlyc3Qgc3VibmV0IGlz
IGNvbnZlbmllbnQgdG8gdXNlIGZvciBlLmcuIG1hbnVhbCBhZGRyZXNzaW5nIChzaW5jZSBpdCBh
bGxvd3MgdGhlIDo6IHNob3J0IGhhbmQpLg0KPiBJIGRvIHdvbmRlciBpZiB0aGlzIGhhcyB0byBi
ZSBwcm92aXNpb25lZC4gZS5nLiBzb21lIGRlcGxveW1lbnRzIG1heSB1c2UgdGhlIGZpcnN0IHN1
Ym5ldCBmb3IgdGhlIGxpbmsgYmV0d2Vlbg0KPiBDRSBhbmQgUEUuIChpLmUuIGEgLzU2IC0gMSB1
c2luZyB0aGUgUEQgZXhjbHVkZSBvcHRpb24gaXMgdXNlZCkuDQoNClNlZSBqdXN0IGFib3ZlLg0K
DQo+IA0KPj4gYTItIElmIHRoZSBDRSBoYXMgYW4gSVB2NCBwcmVmaXg6DQo+PiANCj4+IDwtLS0t
LS0tLS0gNjQgLS0tLS0tLS0tLS0tPjw4ID48LS0gTCA8IDMyIC0tPjwtLS0gNDgtTCAtLS0tLT48
OCA+DQo+PiArLS0tLS0tLS0tLS0tLSstLS0tLS0tLSstLS0rLS0tKy0tLS0tLS0tLS0tLS0rLS0t
LS0tLS0tLS0tLS0tKy0tLSsNCj4+IHwgSVB2NiBwcmVmaXggfENFIGluZGV4fCAwIHwgViB8IElQ
djQgcHJlZml4IHwgICAgICAgICAwICAgICB8IEwgfA0KPj4gKy0tLS0tLS0tLS0tLS0rLS0tLS0t
LS0rLS0tKy0tLSstLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLSstLS0rDQo+PiANCj4+IChi
KQ0KPj4gViBpcyB0aGUgbWFyayB0aGF0IGNoYXJhY3Rlcml6ZXMgSVB2NiBwYWNrZXRzIHRoYXQg
YXJlIGluIHJlYWxpdHkgSVB2NCBwYWNrZXRzLg0KPj4gSXRzIHZhbHVlIGRpZmZlcnMgZnJvbSBh
bnkgcGVybWl0dGVkIHZhbHVlIG9mIHRoaXMgb2N0ZXQgaW4gSVB2NiBJSURzICAocmVmIFJGQyA0
MjkxKS4NCj4+IA0KPj4gSXQgaXMgdW5kZXJzdG9vZCB0aGF0LCBpZiBkb3VibGUgVHJhbnNsYXRp
b24gY29leGlzdHMgd2l0aCBzaW5nbGUgdHJhbnNsYXRpb24sIGNvbmNlcm5lZCBJU1BzIG1heSBu
b3RpZnkgdGhlaXIgQ0VzIHRvIHVzZSB0aGUgVSBvY3RldCBvZiBSRkMgNjA1MiBpbnN0ZWFkIG9m
IFYuDQo+PiANCj4+IEFuIHVuYW1iaWd1b3VzIG1hcmsgaXMgZm9ydHVuYXRlbHkgcG9zc2libGUg
YmVjYXVzZSBjdXJyZW50bHkgcGVybWl0dGVkIElJRHMgaGF2ZSBpbiB0aGVpciBmaXJzdCBvY3Rl
dCBlaXRoZXIgYml0NiA9IDAgKHRoZSAidSIgYml0IiksIG9yIGJpdDYgPSAxIGFuZCBiaXQ3PSAw
ICh0aGUgImciIGJpdCkuDQo+PiBXaXRoIFYgaGF2aW5nICJ1IiA9IDEgKHNpZ25pZnlpbmcgVW5p
dmVyc2FsIHNjb3BlKSBBTkQgImciID0gMSwgZGlzdGluY3Rpb24gaXMgdGhlcmVmb3JlIGRldGVy
bWluaXN0aWMuDQo+PiANCj4+IFRoZSBwcm9wb3NlZCBWIGlzID0gMDAwMDAwMTEuIA0KPj4gKFdp
dGggb3RoZXIgdmFsdWVzIG9mIHRoaXMgb2N0ZXQsIG90aGVyIElJRCBmb3JtYXRzIGNhbiBiZSBk
ZWZpbmVkIGluIGNhc2Ugc29tZSB3b3VsZCBiZSB1c2VmdWwgaW4gdGhlIGZ1dHVyZS4pDQo+PiAN
Cj4+IE5vdGUgdGhhdCwgaWYgYW5kIHdoZW4gYSBjb25zZW5zdXMgaXMgcmVhY2hlZCBpbiBTb2Z0
d2lyZSwgYW4gZXh0ZW5zaW9uIG9mIFJGQyA0MjkxIHdpbGwgaGF2ZSB0byBiZSBzdWJtaXR0ZWQg
dG8gNk1BTi4gDQo+IA0KPiBvciByYXRoZXIgSUVFRT8NCg0KSU1ITywgSUVFRSBoYXMgbm90aGlu
ZyB0byBkbyB3aXRoIGEgbWFya2VyIHRoYXQgaXMgcHVycG9zZWx5IGFuIGVzY2FwZSBtZWNoYW5p
c20gZnJvbSB0aGUgbW9kaWZpZWQgRVVJLTY0IGZvcm1hdCBvZiBSRkMgNDI5MS4NCg0KPiBJIGFt
IG5vdCBjb252aW5jZWQgdGhhdCAiViIgaXMgbmVlZGVkLg0KDQpUaGUgcG9pbnQgaXMgbW9yZSwg
SU1ITywgd2hldGhlciB5b3UgaGF2ZSBhbiBvYmplY3Rpb24gdG8gaXQgKGFuZCBpbiB0aGlzIGNh
c2Ugd2hpY2ggb25lKS4NClJlYXNvbiBpcyB0aGF0IHdlIGFyZSB3b3JraW5nIGZvciBhIGNvbnNl
bnN1cywgYW5kIHNldmVyYWwgYXJlIHNhdGlzZmllZCB3aXRoIHRoZSBleHBsYW5hdGlvbiB0aGF0
IHRoZXJlIGFyZSB1c2UgY2FzZXMgd2hlcmUgaXQgaXMgdXNlZnVsLCBhbmQgbm9uZSB3aGVyZSBp
dCBpcyBoYXJtZnVsLg0KDQo+IHlvdSBjb3VsZCBldmVuIHVzZSB0aGUgSUFOQSBPVUkgaWYgcHJl
dHR5IHByaW50aW5nIHdhcyByZXF1aXJlZC4NCg0KVGhlIHBvaW50IGlzIHRoYXQgaXQgdGFrZXMg
MzIgYml0cyB3aGljaCBpcyB0b28gbXVjaCB0byBoYXZlIElQdjQgYWRkcmVzcyArIFBTSUQgaW4g
dGhlIElJRC4NCg0KDQo+PiAoYykgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0K
Pj4gQSBEZXN0aW5hdGlvbiBhZGRyZXNzIGZyb20gYSBDRSB0byB0aGUgb3V0c2lkZSBJUHY0IElu
dGVybmV0IGlzOg0KPj4gPC0tLS0tLS0tLSA2NCAtLS0tLS0tLS0tLS0+PCA4ID48LS0tLSAgIDMy
IC0tLS0+PC0tLSAxNiAtLS0tPjw4ID4NCj4+ICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSst
LS0tKy0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0rLS0tKw0KPj4gfCAgICAgQlIgc3VibmV0
IHByZWZpeCAgICAgfCBWICB8ICBJUHY0IGFkZHJlc3MgfCAgICAgIDAgICAgIHwzMiB8DQo+PiAr
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLSstLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0t
LS0tKy0tLSsNCj4gDQo+IHRoaXMgaXMgYSBiaWcgY2hhbmdlIGZvciBlbmNhcHN1bGF0aW9uLCB3
aGVyZSBwcmlvciB0byB0aGlzIGVuY2Fwc3VsYXRpb24gbWVhbnMgc2VuZGluZyB0byBhIHNpbmds
ZSBkZXN0aW5hdGlvbi4NCg0KQ29weWluZyBhbiBhdmFpbGFibGUgSVB2NCBhZGRyZXNzIGF0IGEg
Zml4ZWQgcGxhY2UgaXNuJ3QgSU1ITyBhICJiaWcgY2hhbmdlIi4NCg0KPiBpZiB3ZSBhbHNvIGFs
bG93IGZvciBhIEJSIHN1Ym5ldCBwcmVmaXggb2YgLzEyOCBJJ20gT0sgd2l0aCB0aGlzIChJIHRo
aW5rKS4NCg0KSSBkb24ndCB1bmRlcnN0YW5kIHdoYXQgeW91IG1lYW4gYnkgIlN1Ym5ldCBwcmVm
aXggb2YgLzEyOCIuDQoNCg0KPj4gTm90ZSB0aGF0IGlmIGRvdWJsZS10cmFuc2xhdGlvbiBDRXMg
YXJlIG5vdGlmaWVkIHRvIHVzZSBVIGluc3RlYWQgb2YgViwgdGhlIGxhc3Qgb2N0ZXQgYmVjb21l
cyAwIHBlciBSRkMgIDYwNTIuDQo+IA0KPiBob3cgd291bGQgYSBDRSBrbm93IGlmIGl0IHdhcyBz
aW5nbGUgb3IgZG91YmxlIHRyYW5zbGF0aW5nPw0KDQpQcmVzdW1hYmx5IHdpdGggYSB1c3VhbCBt
ZXRob2QsIGUuZy4gREhDUHY2Lg0KQW55dGhpbmcgcHJvYmxlbWF0aWMgd2l0aCB0aGF0Pw0KDQoN
Cj4gZS5nIHdlIGNvdWxkIGRvOg0KPiANCj4gPC0tLS0tLS0tLSA2NCAtLS0tLS0tLS0tLS0+PC0t
LSAyNCAtLS0tLS0+PC0tLS0tIDMyIC0tLS0tLS0+PC0tOCA+DQo+ICstLS0tLS0tLS0tLS0tKy0t
LS0tLS0tKy0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0rLS0tKw0KPiB8IElQ
djYgcHJlZml4IHxDRSBpbmRleHwgUyB8IDAwLTAwLTVFICAgIHwgIElQdjQgYWRkcmVzcyAgfCBQ
U0lEIHwNCj4gKy0tLS0tLS0tLS0tLS0rLS0tLS0tLS0rLS0tKy0tLSstLS0tLS0tLS0tLS0tLS0t
Ky0tLS0tLSstLS0tLSstLS0rDQo+IA0KPiB3ZSBhbHNvIG5lZWQgdG8gaGFuZGxlIHRoZSBjYXNl
IHdoZXJlIElQdjYgcHJlZml4ICsgQ0UgaW5kZXggPiA2NC4NCg0KUGxlYXNlIGV4cGxhaW4gbW9y
ZSB5b3VyIHVuZGVyc3RhbmRpbmcgb2YgdGhpcyByZXF1aXJlbWVudC4NCihJIHBlcnNvbmFsbHkg
YmVsaWV2ZSB3ZSBzaG91bGQgYXZvaWQgdGhhdC4pDQoNCj4gSSBzdWdnZXN0IHdlIHRoZW4ganVz
dCBwdXQgYXMgbXVjaCBhcyB0aGUgaW50ZXJmYWNlIGlkZW50aWZpZXIgdGhhdCB3aWxsIGZpdC4N
Cg0KDQpNYXkgSSBzdWdnZXN0IHRoYXQsIHRvIGJlIG1vcmUgY29uc3RydWN0aXZlLCB5b3UgY291
bGQgZmlyc3QgZXhwcmVzcyB5b3VyIG9iamVjdGlvbnMgdG8gdGhlIHByb3Bvc2VkIHVuaWZpZWQg
bWFwcGluZywgcmF0aGVyIHRoYW4gbWFraW5nIGEgbnVtYmVyIG9mIG5ldyBwcm9wb3NhbHMgd2hv
c2UganVzdGlmaWNhdGlvbnMgYXJlIHNvbWV0aW1lcyBoYXJkIHRvIHVuZGVyc3RhbmQsIA0KDQpD
aGVlcnMsDQpSRCANCg0KDQo+IA0KPiBjaGVlcnMsDQo+IE9sZQ0KPiANCj4gDQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KU29mdHdpcmVzIG1haWxpbmcg
bGlzdA0KU29mdHdpcmVzQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3NvZnR3aXJlcw0K

From jacni@jacni.com  Mon Oct 10 04:53:29 2011
Return-Path: <jacni@jacni.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 7FB3321F8B52 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 04:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[AWL=0.540,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SaRBlnENFQRW for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 04:53:28 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF2321F8B8A for <softwires@ietf.org>; Mon, 10 Oct 2011 04:53:27 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 37D3138006E for <softwires@ietf.org>; Mon, 10 Oct 2011 07:53:25 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 011DD3400B2 for <softwires@ietf.org>; Mon, 10 Oct 2011 19:53:23 +0800 (CST)
Received: from [172.21.25.30] (unknown [221.11.61.66]) by app (Coremail) with SMTP id +AWowJDbhwmS3JJO7g8XAA--.30663S2; Mon, 10 Oct 2011 19:53:09 +0800 (CST)
Message-ID: <4E92DCFC.8090008@jacni.com>
Date: Mon, 10 Oct 2011 19:54:36 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <CAFUBMqUdZ8dstRYdMjTi183737ms=na2OWpRSF6phqOK0FN9iA@mail.gmail.com> <CAM+vMEQJzPUwLN2w1ZfuC5vy1C5sBBbVjPnjka+eoe_t3bPxKQ@mail.gmail.com> <4E9278DC.1030004@jacni.com> <CAFUBMqW0JXXh5GDuPv-enbHsMvyOTcZjtuTAHm6TPo+Ey=Od5g@mail.gmail.com>
In-Reply-To: <CAFUBMqW0JXXh5GDuPv-enbHsMvyOTcZjtuTAHm6TPo+Ey=Od5g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040801030906090805060800"
X-CM-TRANSID: +AWowJDbhwmS3JJO7g8XAA--.30663S2
X-Coremail-Antispam: 1UD129KBjvJXoWxCryUGFWrWr1UCFWUKw4fuFg_yoWrGrWrpF WSqwnxtF4DKF1xCr4kXw47uw45CFn5GayUJ3y5G3sYywn8G3WIvF1Ikw1Yva43Xrs3JwnI qFWqyry5A3WkZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU7mb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VWkKwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK64x0aVW7Gw IE548m6rI_Jw1UWr17M2vj6xkI62vS6c8GOVWUtr1rJFylYx0E2Ix0cI8IcVAFwI0_Jr0_ Jr4lYx0Ex4A2jsIE14v26r1j6r4UM4x0Y48IcVAKI48JMx8GjcxK6IxK0xIIj40E5I8Crw CYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI7VAKI48JMxCIbVAxMI8E67AF67kF1VAF wI0_Jrv_JF1lIxkGc2Ij64vIr4UvcSsGvfC2KfnxnUUI43ZEXa7IU0S_MDUUUUU==
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEREko7lOf-ywAAs1
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 11:53:29 -0000

This is a multi-part message in MIME format.
--------------040801030906090805060800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hi,

On 10/10/2011 4:40 PM, Maoke wrote:
> hi Jacni,
> thanks for the discussion from the view of address planning. it is 
> clear. i just would like to add an overview comment on the "philosophy".
> to my understanding, the prefix length to a customer depends upon, 
> essentially, how many end-system identifiers are needed, according 
> to what we estimate, within the scope of the customer network. in the 
> age of IPv4, the estimation is typically expressed with a definite 
> prefix length because we hardly have a shorter one than what we really 
> need. in the age of IPv6, however, if the prefix length for a customer 
> network in address planning is not a fixed value but a range with 
> relaxation, the art of address planning may also change. (e.g., 
> the block assigned to a subscriber is at most /60 supporting up 
> to 1M subscribers in total, and at least /72 in oder to support up 
> to 2^56 end-system identifiers within each CE-delegated network). with 
> this in mind, ISP may have larger room to pick up techniques and 
> deployment tactics possibly without doing less-necessary tradeoffs.
Thanks for your comments, I was only guessing based on experiences from 
IPv4. And yes, as you mentioned, something will change in IPv6.
While I think in practice, from ISP's perspective, probably there won't 
be that much flexibility, for example, there can't be too many SLAs.
Anyway, we can only know that after IPv6 comes true. ;-)


Cheers,
Jacni

> the same philosophy doesn't imply a unique art of action. MHO. sorry 
> but out of the scope of this group.
> thanks a lot,
> maoke
> 2011/10/10 Jacni Qin <jacni@jacni.com <mailto:jacni@jacni.com>>
>
>     hi,
>
>     One comment on the example you proposed, please see below,
>
>     On 10/9/2011 7:30 PM, GangChen wrote:
>>     ...
>>     I'm not sure what formula you have to deduce this *requirement*.
>>     Different sharing ratios should implicitly be expressed by different
>>     IPv6 prefix lengths when an operator would deploy PD. At this point,
>>     you can't help even you encode whole IPv4 address in suffix. As for
>>     the question you raised, I think that are operational issues more than
>>     technical issues. I take your example as explanation for your better
>>     understanding.
>>
>>     A small ISP has its Rule IPv4 prefix such as 10/8, while its total
>>     IPv6 block has fairly long prefix like /48 or a /56.
>>
>>     Then an operator could strategically pre-config a relatively small
>>     IPv4 subnet to 4v6 domain as rule IPv4 prefix, like 10/24. Then you
>>     could get more space in IPv6 prefix to put PSID information. See that
>>     is quite flexible if you do have a good operational planning.
>>
>     I get it, but let me try in another way.
>     The IPv6 addressing must not be affected, that's one of the basic
>     objectives of MAP we'll agree on, right?
>
>     So, firstly the IPv6 address planning should be done natively
>     according to the service requirements, the expected scale of
>     subscribers, and the address space assigned respectively.
>     For example, if you plan to assign a /60 to each subscriber in a
>     given domain with 1M subscribers totally, an IPv6 prefix of "/40"
>     is required (probably shorter given the efficiency loss of
>     hierarchical aggregation).
>     Then, this becomes the assumption (or restriction) on which we've
>     got 20 bits space to play with our art.
>
>     The next step is to decide the sharing ratio, say, 2k ports per
>     subscriber, the PSID will be of 5 bits. Here the tradeoff is to
>     use how many bits borrowed from ports or from the first 32 bits.
>     Then in this case, an IPv4 prefix of "/17" is required to
>     accommodate the 1M subscribers (through "15+5").
>     If we're lucky to get a block of "/17", one piece of MAP rule is
>     enough. Otherwise, we'll have to face another tradeoff, smaller
>     number of rules or smaller number of fragmented blocks used.
>
>     ISPs' cases are quite different, while the philosophy of address
>     planning is not, and should be kept in mind when we design the MAP.
>
>
> Cheers,
> Jacni
>
>

--------------040801030906090805060800
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 10/10/2011 4:40 PM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqW0JXXh5GDuPv-enbHsMvyOTcZjtuTAHm6TPo+Ey=Od5g@mail.gmail.com"
      type="cite">
      <div>hi Jacni, </div>
      <div>&nbsp;</div>
      <div>thanks for the discussion from the view of address planning.
        it is clear. i&nbsp;just would like to add an overview&nbsp;comment on the
        "philosophy". </div>
      <div>&nbsp;</div>
      <div>to my understanding, the prefix length to a&nbsp;customer depends
        upon, essentially, how many end-system identifiers are needed,
        according to&nbsp;what we estimate,&nbsp;within the scope of the customer
        network. in the age of IPv4, the estimation is typically
        expressed with&nbsp;a definite prefix length because we hardly have a
        shorter one than what we really need. in the age of IPv6,
        however, if the prefix length for&nbsp;a customer network&nbsp;in address
        planning is not a fixed value but a range with relaxation, the
        art of address planning may also change. (e.g.,
        the&nbsp;block&nbsp;assigned to&nbsp;a subscriber&nbsp;is at most /60&nbsp;supporting&nbsp;up
        to&nbsp;1M&nbsp;subscribers in total, and at least /72&nbsp;in oder to
        support&nbsp;up to&nbsp;2^56 end-system identifiers within each
        CE-delegated network). with this in mind, ISP may have larger
        room to pick up techniques and deployment tactics possibly
        without doing less-necessary tradeoffs.&nbsp;&nbsp;</div>
      <div>&nbsp;</div>
    </blockquote>
    Thanks for your comments, I was only guessing based on experiences
    from IPv4. And yes, as you mentioned, something will change in IPv6.<br>
    While I think in practice, from ISP's perspective, probably there
    won't be that much flexibility, for example, there can't be too many
    SLAs.<br>
    Anyway, we can only know that after IPv6 comes true. ;-)<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAFUBMqW0JXXh5GDuPv-enbHsMvyOTcZjtuTAHm6TPo+Ey=Od5g@mail.gmail.com"
      type="cite">
      <div>the same philosophy doesn't imply a unique art of
        action.&nbsp;MHO. sorry but out of the scope of this group. </div>
      <div>&nbsp;</div>
      <div>thanks a lot,</div>
      <div>maoke&nbsp;</div>
      <div class="gmail_quote">&nbsp;</div>
      <div class="gmail_quote">
        2011/10/10 Jacni Qin <span dir="ltr">&lt;<a
            moz-do-not-send="true" href="mailto:jacni@jacni.com"
            target="_blank">jacni@jacni.com</a>&gt;</span><br>
        <blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex;
          border-left-color: rgb(204, 204, 204); border-left-width: 1px;
          border-left-style: solid;" class="gmail_quote">
          <div text="#000000" bgcolor="#FFFFFF"> <font face="Calibri">hi,<br>
              <br>
              One comment on the example you proposed, please see below,<br>
            </font><br>
            On 10/9/2011 7:30 PM, GangChen wrote:
            <blockquote type="cite">...
              <div>
                <pre>I'm not sure what formula you have to deduce this *requirement*.
Different sharing ratios should implicitly be expressed by different
IPv6 prefix lengths when an operator would deploy PD. At this point,
you can't help even you encode whole IPv4 address in suffix. As for
the question you raised, I think that are operational issues more than
technical issues. I take your example as explanation for your better
understanding.

A small ISP has its Rule IPv4 prefix such as 10/8, while its total
IPv6 block has fairly long prefix like /48 or a /56.

Then an operator could strategically pre-config a relatively small
IPv4 subnet to 4v6 domain as rule IPv4 prefix, like 10/24. Then you
could get more space in IPv6 prefix to put PSID information. See that
is quite flexible if you do have a good operational planning.

</pre>
              </div>
            </blockquote>
            I get it, but let me try in another way.<br>
            The IPv6 addressing must not be affected, that's one of the
            basic objectives of MAP we'll agree on, right?<br>
            <br>
            So, firstly the IPv6 address planning should be done
            natively according to the service requirements, the expected
            scale of subscribers, and the address space assigned
            respectively.<br>
            For example, if you plan to assign a /60 to each subscriber
            in a given domain with 1M subscribers totally, an IPv6
            prefix of "/40" is required (probably shorter given the
            efficiency loss of hierarchical aggregation).<br>
            Then, this becomes the assumption (or restriction) on which
            we've got 20 bits space to play with our art.<br>
            <br>
            The next step is to decide the sharing ratio, say, 2k ports
            per subscriber, the PSID will be of 5 bits. Here the
            tradeoff is to use how many bits borrowed from ports or from
            the first 32 bits.<br>
            Then in this case, an IPv4 prefix of "/17" is required to
            accommodate the 1M subscribers (through "15+5").<br>
            If we're lucky to get a block of "/17", one piece of MAP
            rule is enough. Otherwise, we'll have to face another
            tradeoff, smaller number of rules or smaller number of
            fragmented blocks used.<br>
            &nbsp;&nbsp;&nbsp;&nbsp;</div>
        </blockquote>
        <blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex;
          border-left-color: rgb(204, 204, 204); border-left-width: 1px;
          border-left-style: solid;" class="gmail_quote">
          <div text="#000000" bgcolor="#FFFFFF"> ISPs' cases are quite
            different, while the philosophy of address planning is not,
            and should be kept in mind when we design the MAP.<br>
            &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</div>
        </blockquote>
        <div><br>
          Cheers,<br>
          Jacni<br>
          <br>
        </div>
        <blockquote type="cite"> </blockquote>
      </div>
      <br>
    </blockquote>
  </body>
</html>

--------------040801030906090805060800--


From bingxuere@gmail.com  Mon Oct 10 08:13:03 2011
Return-Path: <bingxuere@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 1C6F721F8C49 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 08:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=0.849,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_61=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-SwQAeaGAKc for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 08:13:02 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7650021F8C36 for <softwires@ietf.org>; Mon, 10 Oct 2011 08:13:02 -0700 (PDT)
Received: by iaby26 with SMTP id y26so9256647iab.31 for <softwires@ietf.org>; Mon, 10 Oct 2011 08:13:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Gd+eJkH7rPKNM+vFH0Q3QgiXmCppA1Pp1m1K3Mo5aJY=; b=pAEXGg9fT5dGvMcCt+ZJhlIDh6WY94YRdk1KHNZ1ML08B4+vNs9dnknN9ysUMqd0Ft vwWJyFA/kw5JzOUg0WxTQXy3LnGgZkO6Su0R6QSFrxdrvyHsbKOAW5is/Q4Zimpmkaxb qMorIyOg5jD1Ug2ckwRg/Sutaj+SLvskPIyLA=
Received: by 10.42.159.1 with SMTP id j1mr17882813icx.20.1318259582075; Mon, 10 Oct 2011 08:13:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Mon, 10 Oct 2011 08:12:41 -0700 (PDT)
In-Reply-To: <2904870A-866E-4093-8754-3D75510B82AA@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net>
From: Qiong <bingxuere@gmail.com>
Date: Mon, 10 Oct 2011 23:12:41 +0800
Message-ID: <CAH3bfABJ=6CHA_QmtxtnoGmS2bSPhrDtdpebm9TwTLeMVdVMSA@mail.gmail.com>
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=90e6ba6e88041c830f04aef33ab4
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 15:13:03 -0000

--90e6ba6e88041c830f04aef33ab4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Remi and Jacni,

Thanks for the discussion.

On Mon, Oct 10, 2011 at 3:26 PM, R=C3=A9mi Despr=C3=A9s <despres.remi@lapos=
te.net>wrote:

>
> The 4rd function examines ALL packets that reach the CE.
> It processes all those that have V in their destination addresses, and on=
ly
> those.
>

Qiong: I think it might be better achieved via routing lookup for prefix+V
bits (e.g. /80 ), rather than extracting V bits before traditional routing.


>
> The reason why 4rd packets reach the CE is NOT that their destinations ar=
e
> the IPv6 address that the CE has on its link to the ISP.
> It is that their destinations start with the CE delegated prefix. The
> routing information base of the ISP edge router is such that, for such
> destinations, the next hop is the CE.
>
>
> Then the variable "max" PSID derived from dst. ports may get a problem.
>
>  Qiong: I think the "max" PSID design might have a problem in virtual
interface implementation. When implementing an virtual
encapsulation/translation interface, the packets can reach the virtual
interface from a downstream physical interface via traditional routing. For
example, identifying a specific address or /80 prefix to the destinated
virtual interface. However, when the "max" PSID is not stable and the lengt=
h
of "Rule IPv6 prefix+ Max PSID" exceeds 64 bit long, how to construct this
kind of internal routing table ? I think it would be too many routing
entries here.

Best wishes

Qiong

Not AFAIK because of the above.
>
> Hope it clarifies.
> Cheers,
> RD
>
>
>
>
>
> Cheers,
> Jacni
>
>
>
>

--90e6ba6e88041c830f04aef33ab4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Remi and Jacni,<div><br></div><div>Thanks for the discussion.<br><br><d=
iv class=3D"gmail_quote">On Mon, Oct 10, 2011 at 3:26 PM, R=C3=A9mi Despr=
=C3=A9s <span dir=3D"ltr">&lt;<a href=3D"mailto:despres.remi@laposte.net">d=
espres.remi@laposte.net</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;"><div style=3D"word-wrap:break-word"><br><di=
v><div>The 4rd function examines ALL packets that reach the CE.</div><div>I=
t processes all those that have V in their destination addresses, and only =
those.</div>

</div></div></blockquote><div><br></div><div>Qiong: I think it might be bet=
ter achieved via routing lookup for prefix+V bits (e.g. /80 ), rather than =
extracting V bits before traditional routing.</div><div>=C2=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div><div><br></div><div>The reason why=
 4rd packets reach the CE is NOT that their destinations are the IPv6 addre=
ss that the CE has on its link to the ISP.=C2=A0</div><div>It is that their=
 destinations start with the CE delegated prefix. The routing information b=
ase of the ISP edge router is such that, for such destinations, the next ho=
p is the CE.=C2=A0</div>

<div class=3D"im"><div><br></div><div><br></div><blockquote type=3D"cite"><=
div bgcolor=3D"#FFFFFF" text=3D"#000000">Then the variable &quot;max&quot; =
PSID derived
    from dst. ports may get a problem.</div></blockquote></div></div></div>=
</blockquote><div>=C2=A0Qiong: I think the &quot;max&quot; PSID design migh=
t have a problem in virtual interface implementation. When implementing an =
virtual encapsulation/translation interface, the packets can reach the virt=
ual interface from a downstream physical interface via traditional routing.=
 For example, identifying a specific address or /80 prefix to the destinate=
d virtual interface. However, when the &quot;max&quot; PSID is not stable a=
nd the length of &quot;Rule IPv6 prefix+ Max PSID&quot; exceeds 64 bit long=
, how to construct this kind of internal routing table ? I think it would b=
e too many routing entries here.</div>

<div><br></div><div>Best wishes</div><div><br></div><div>Qiong</div><div><b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:break-word"=
>
<div>
<div class=3D"im"><div></div></div>Not AFAIK because of the above.</div><di=
v><br></div><div>Hope it clarifies.</div><div>Cheers,</div><div>RD</div><di=
v><br></div><div><br><br><blockquote type=3D"cite"><div bgcolor=3D"#FFFFFF"=
 text=3D"#000000">


    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <br>
  </div>

</blockquote></div><br></div></blockquote></div><br></div>

--90e6ba6e88041c830f04aef33ab4--

From despres.remi@laposte.net  Mon Oct 10 08:17:48 2011
Return-Path: <despres.remi@laposte.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 CFE3F21F8C55 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 08:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.615
X-Spam-Level: 
X-Spam-Status: No, score=-0.615 tagged_above=-999 required=5 tests=[AWL=-1.567, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_61=0.6, MANGLED_FROM=2.3, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NJeEwzSO9kVc for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 08:17:48 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.4]) by ietfa.amsl.com (Postfix) with ESMTP id 0AFD021F8C54 for <softwires@ietf.org>; Mon, 10 Oct 2011 08:17:47 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2114.sfr.fr (SMTP Server) with ESMTP id 5FE0670001F6; Mon, 10 Oct 2011 17:17:46 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2114.sfr.fr (SMTP Server) with ESMTP id 8429470001F4; Mon, 10 Oct 2011 17:17:45 +0200 (CEST)
X-SFR-UUID: 20111010151745541.8429470001F4@msfrf2114.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-47-650248686
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAH3bfABJ=6CHA_QmtxtnoGmS2bSPhrDtdpebm9TwTLeMVdVMSA@mail.gmail.com>
Date: Mon, 10 Oct 2011 17:17:44 +0200
Message-Id: <96BD287F-910B-4E50-B902-4D135D2DFEAE@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <CAH3bfABJ=6CHA_QmtxtnoGmS2bSPhrDtdpebm9TwTLeMVdVMSA@mail.gmail.com>
To: Qiong <bingxuere@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 15:17:48 -0000

--Apple-Mail-47-650248686
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 10 oct. 2011 =E0 17:12, Qiong a =E9crit :

> Hi, Remi and Jacni,
>=20
> Thanks for the discussion.
>=20
> On Mon, Oct 10, 2011 at 3:26 PM, R=E9mi Despr=E9s =
<despres.remi@laposte.net> wrote:
>=20
> The 4rd function examines ALL packets that reach the CE.
> It processes all those that have V in their destination addresses, and =
only those.
>=20
> Qiong: I think it might be better achieved via routing lookup for =
prefix+V bits (e.g. /80 ), rather than extracting V bits before =
traditional routing.
> =20
>=20
> The reason why 4rd packets reach the CE is NOT that their destinations =
are the IPv6 address that the CE has on its link to the ISP.=20
> It is that their destinations start with the CE delegated prefix. The =
routing information base of the ISP edge router is such that, for such =
destinations, the next hop is the CE.=20
>=20
>=20
>> Then the variable "max" PSID derived from dst. ports may get a =
problem.

>  Qiong: I think the "max" PSID design might have a problem in virtual =
interface implementation. When implementing an virtual =
encapsulation/translation interface, the packets can reach the virtual =
interface from a downstream physical interface via traditional routing.

> For example, identifying a specific address or /80 prefix to the =
destinated virtual interface. However, when the "max" PSID is not stable =
and the length of "Rule IPv6 prefix+ Max PSID" exceeds 64 bit long, how =
to construct this kind of internal routing table ? I think it would be =
too many routing entries here.

Routing being only concerned with /64s, and information in IIDs being =
used only by 4rd functions themselves, or for O&M, I don't see the =
problem.

Regards,
RD






>=20
> Best wishes
>=20
> Qiong
>=20
> Not AFAIK because of the above.
>=20
> Hope it clarifies.
> Cheers,
> RD
>=20
>=20
>=20
>>=20
>>=20
>> Cheers,
>> Jacni
>>=20
>>=20
>=20
>=20


--Apple-Mail-47-650248686
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 10 oct. 2011 =E0 17:12, Qiong a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">Hi, Remi =
and Jacni,<div><br></div><div>Thanks for the discussion.<br><br><div =
class=3D"gmail_quote">On Mon, Oct 10, 2011 at 3:26 PM, R=E9mi Despr=E9s =
<span dir=3D"ltr">&lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;<=
/span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"><div =
style=3D"word-wrap:break-word"><br><div><div>The 4rd function examines =
ALL packets that reach the CE.</div><div>It processes all those that =
have V in their destination addresses, and only those.</div>

</div></div></blockquote><div><br></div><div>Qiong: I think it might be =
better achieved via routing lookup for prefix+V bits (e.g. /80 ), rather =
than extracting V bits before traditional =
routing.</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; ">

<div style=3D"word-wrap:break-word"><div><div><br></div><div>The reason =
why 4rd packets reach the CE is NOT that their destinations are the IPv6 =
address that the CE has on its link to the ISP.&nbsp;</div><div>It is =
that their destinations start with the CE delegated prefix. The routing =
information base of the ISP edge router is such that, for such =
destinations, the next hop is the CE.&nbsp;</div>

<div class=3D"im"><div><br></div><div><br></div><blockquote =
type=3D"cite"><div bgcolor=3D"#FFFFFF" text=3D"#000000">Then the =
variable "max" PSID derived
    from dst. ports may get a =
problem.</div></blockquote></div></div></div></blockquote></div></div></bl=
ockquote><br><blockquote type=3D"cite"><div><div =
class=3D"gmail_quote"><div>&nbsp;Qiong: I think the "max" PSID design =
might have a problem in virtual interface implementation. When =
implementing an virtual encapsulation/translation interface, the packets =
can reach the virtual interface from a downstream physical interface via =
traditional routing.</div></div></div></blockquote><br><blockquote =
type=3D"cite"><div><div class=3D"gmail_quote"><div> For example, =
identifying a specific address or /80 prefix to the destinated virtual =
interface. However, when the "max" PSID is not stable and the length of =
"Rule IPv6 prefix+ Max PSID" exceeds 64 bit long, how to construct this =
kind of internal routing table ? I think it would be too many routing =
entries here.</div></div></div></blockquote><div><br></div>Routing being =
only concerned with /64s,&nbsp;and information in IIDs being used only =
by 4rd functions themselves, or for O&amp;M, I don't see the =
problem.</div><div><br></div><div>Regards,</div><div>RD</div><div><br></di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div><br><bl=
ockquote type=3D"cite"><div><div class=3D"gmail_quote">

<div><br></div><div>Best =
wishes</div><div><br></div><div>Qiong</div><div><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;"><div style=3D"word-wrap:break-word">
<div>
<div class=3D"im"><div></div></div>Not AFAIK because of the =
above.</div><div><br></div><div>Hope it =
clarifies.</div><div>Cheers,</div><div>RD</div><div><br></div><div><br><br=
><blockquote type=3D"cite"><div bgcolor=3D"#FFFFFF" text=3D"#000000">


    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <br>
  </div>

</blockquote></div><br></div></blockquote></div><br></div>
</blockquote></div><br></body></html>=

--Apple-Mail-47-650248686--

From bingxuere@gmail.com  Mon Oct 10 08:33:37 2011
Return-Path: <bingxuere@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 A1AC121F8C39 for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 08:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.823
X-Spam-Level: 
X-Spam-Status: No, score=-0.823 tagged_above=-999 required=5 tests=[AWL=-1.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_61=0.6, J_CHICKENPOX_92=0.6, MANGLED_FROM=2.3, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tx+k17qFcIRB for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 08:33:37 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id D303821F8B35 for <softwires@ietf.org>; Mon, 10 Oct 2011 08:33:36 -0700 (PDT)
Received: by qadb12 with SMTP id b12so5236563qad.31 for <softwires@ietf.org>; Mon, 10 Oct 2011 08:33:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+4u7qSTs2D5J7m+LHdqh5vMPN5fgjIa14j6LJhjb2zI=; b=IkB4CzV/9kXrw1WhLs28hVLmdvMKVgMaayySWByeY4IGRsyCmyspJvuxQx7gQARSl8 cycDIo6tNhe5NFtqdMo+i6625+jrgXLIEEu+t9u57sokcaI12rygZoOw/0ReovZ8bH6N P0bXb2sz8GIq4oX6Do6ZqBTMS628I5Aw6hbWc=
Received: by 10.42.159.1 with SMTP id j1mr18023209icx.20.1318260816093; Mon, 10 Oct 2011 08:33:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Mon, 10 Oct 2011 08:33:16 -0700 (PDT)
In-Reply-To: <96BD287F-910B-4E50-B902-4D135D2DFEAE@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <CAH3bfABJ=6CHA_QmtxtnoGmS2bSPhrDtdpebm9TwTLeMVdVMSA@mail.gmail.com> <96BD287F-910B-4E50-B902-4D135D2DFEAE@laposte.net>
From: Qiong <bingxuere@gmail.com>
Date: Mon, 10 Oct 2011 23:33:16 +0800
Message-ID: <CAH3bfADrj2BuQwEM3=ZC6_QCDe7RuEorM1=bAoyNH7JJao2_xQ@mail.gmail.com>
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=90e6ba6e8804aa21b404aef383cb
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 15:33:37 -0000

--90e6ba6e8804aa21b404aef383cb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Qiong,

Please see inline.

> On Mon, Oct 10, 2011 at 3:26 PM, R=C3=A9mi Despr=C3=A9s <despres.remi@lap=
oste.net>wrote:
>
>>
>> The 4rd function examines ALL packets that reach the CE.
>> It processes all those that have V in their destination addresses, and
>> only those.
>>
>
> Qiong: I think it might be better achieved via routing lookup for prefix+=
V
> bits (e.g. /80 ), rather than extracting V bits before traditional routin=
g.
>
>
>>
>> The reason why 4rd packets reach the CE is NOT that their destinations a=
re
>> the IPv6 address that the CE has on its link to the ISP.
>> It is that their destinations start with the CE delegated prefix. The
>> routing information base of the ISP edge router is such that, for such
>> destinations, the next hop is the CE.
>>
>>
>> Then the variable "max" PSID derived from dst. ports may get a problem.
>>
>>
>  Qiong: I think the "max" PSID design might have a problem in virtual
> interface implementation. When implementing an virtual
> encapsulation/translation interface, the packets can reach the virtual
> interface from a downstream physical interface via traditional routing.
>
>
> For example, identifying a specific address or /80 prefix to the destinat=
ed
> virtual interface. However, when the "max" PSID is not stable and the len=
gth
> of "Rule IPv6 prefix+ Max PSID" exceeds 64 bit long, how to construct thi=
s
> kind of internal routing table ? I think it would be too many routing
> entries here.
>
>
> Routing being only concerned with /64s, and information in IIDs being use=
d
> only by 4rd functions themselves, or for O&M, I don't see the problem.
>
> Qiong: My concern is specific for virtual interface implementation. If yo=
u
implement a virtual interface(as most existing encapsulation approaches hav=
e
adopted in CPE ), you still need to do routing within CE (from physical
interface to virtual interface). In traditional encapsulation
implementation, a specific routing entry can be assigned to help forward th=
e
traffic with a tunnel endpoint address. And all the following decapsulation
things can be done in this virtual interface. I think this kind of
implementation can be applied to translation as well, to make use of
traditional routing and implementation translation functionality only on th=
e
virtual interface. And since the first 64 bits will be same for both native
traffic and translated traffic, the lower bits would be needed for internal
routing. That's why I think unstable "max" PSID would make it difficult to
construct internal routing table (not routing procedure from ISP to CE). Bu=
t
anyway, it is only restricted to this kind of implementation (determine the
translated traffic by routing rather than bit extracting).

Hope it is clear now.

Thanks

Qiong

--90e6ba6e8804aa21b404aef383cb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Qiong,<br><br>Please see inline.<br><div class=3D"gmail_quote"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex;"><div style=3D"word-wrap:break-word"><div><div><div =
class=3D"h5">

<blockquote type=3D"cite"><div><div class=3D"gmail_quote">On Mon, Oct 10, 2=
011 at 3:26 PM, R=C3=A9mi Despr=C3=A9s <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:despres.remi@laposte.net" target=3D"_blank">despres.remi@laposte.net</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"><div style=3D"word-wrap:break-word"><br><div=
><div>The 4rd function examines ALL packets that reach the CE.</div><div>It=
 processes all those that have V in their destination addresses, and only t=
hose.</div>



</div></div></blockquote><div><br></div><div>Qiong: I think it might be bet=
ter achieved via routing lookup for prefix+V bits (e.g. /80 ), rather than =
extracting V bits before traditional routing.</div><div>=C2=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;margin-=
bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(20=
4, 204, 204);border-left-style:solid;padding-left:1ex">



<div style=3D"word-wrap:break-word"><div><div><br></div><div>The reason why=
 4rd packets reach the CE is NOT that their destinations are the IPv6 addre=
ss that the CE has on its link to the ISP.=C2=A0</div><div>It is that their=
 destinations start with the CE delegated prefix. The routing information b=
ase of the ISP edge router is such that, for such destinations, the next ho=
p is the CE.=C2=A0</div>



<div><div><br></div><div><br></div><blockquote type=3D"cite"><div bgcolor=
=3D"#FFFFFF" text=3D"#000000">Then the variable &quot;max&quot; PSID derive=
d
    from dst. ports may get a problem.</div></blockquote></div></div></div>=
</blockquote></div></div></blockquote><br><blockquote type=3D"cite"><div><d=
iv class=3D"gmail_quote"><div>=C2=A0Qiong: I think the &quot;max&quot; PSID=
 design might have a problem in virtual interface implementation. When impl=
ementing an virtual encapsulation/translation interface, the packets can re=
ach the virtual interface from a downstream physical interface via traditio=
nal routing.</div>

</div></div></blockquote><br><blockquote type=3D"cite"><div><div class=3D"g=
mail_quote"><div> For example, identifying a specific address or /80 prefix=
 to the destinated virtual interface. However, when the &quot;max&quot; PSI=
D is not stable and the length of &quot;Rule IPv6 prefix+ Max PSID&quot; ex=
ceeds 64 bit long, how to construct this kind of internal routing table ? I=
 think it would be too many routing entries here.</div>

</div></div></blockquote><div><br></div></div></div>Routing being only conc=
erned with /64s,=C2=A0and information in IIDs being used only by 4rd functi=
ons themselves, or for O&amp;M, I don&#39;t see the problem.</div><div><br>
</div>
</div></blockquote><div>Qiong: My concern is specific for virtual interface=
 implementation. If you implement a virtual interface(as most existing enca=
psulation approaches have adopted in CPE ), you still need to do routing wi=
thin CE (from physical interface to virtual interface). In traditional enca=
psulation implementation, a specific routing entry can be assigned to help =
forward the traffic with a tunnel endpoint address. And all the following d=
ecapsulation things can be done in this virtual interface. I think this kin=
d of implementation can be applied to translation as well, to make use of t=
raditional routing and implementation translation functionality only on the=
 virtual interface. And since the first 64 bits will be same for both nativ=
e traffic and translated traffic, the lower bits would be needed for intern=
al routing. That&#39;s why I think unstable &quot;max&quot; PSID would make=
 it difficult to construct internal routing table (not routing procedure fr=
om ISP to CE). But anyway, it is only restricted to this kind of implementa=
tion (determine the translated traffic by routing rather than bit extractin=
g).=C2=A0</div>

<div><br></div><div>Hope it is clear now.</div><div><br></div><div>Thanks=
=C2=A0</div><div><br></div><div>Qiong</div><div><br></div></div>

--90e6ba6e8804aa21b404aef383cb--

From despres.remi@laposte.net  Mon Oct 10 08:44:04 2011
Return-Path: <despres.remi@laposte.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 C3E9721F8C5A for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 08:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.077
X-Spam-Level: 
X-Spam-Status: No, score=0.077 tagged_above=-999 required=5 tests=[AWL=-1.475,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_61=0.6, J_CHICKENPOX_92=0.6, MANGLED_FROM=2.3, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUFHlo0FWdeX for <softwires@ietfa.amsl.com>; Mon, 10 Oct 2011 08:44:04 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.4]) by ietfa.amsl.com (Postfix) with ESMTP id AC78621F8C59 for <softwires@ietf.org>; Mon, 10 Oct 2011 08:44:03 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2114.sfr.fr (SMTP Server) with ESMTP id 2054570001EA; Mon, 10 Oct 2011 17:44:03 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2114.sfr.fr (SMTP Server) with ESMTP id C6F3A7000137; Mon, 10 Oct 2011 17:44:02 +0200 (CEST)
X-SFR-UUID: 20111010154402814.C6F3A7000137@msfrf2114.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-48-651826306
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAH3bfADrj2BuQwEM3=ZC6_QCDe7RuEorM1=bAoyNH7JJao2_xQ@mail.gmail.com>
Date: Mon, 10 Oct 2011 17:44:02 +0200
Message-Id: <69EED6FA-D191-42BD-9254-1FAAFF8025F2@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <CAH3bfABJ=6CHA_QmtxtnoGmS2bSPhrDtdpebm9TwTLeMVdVMSA@mail.gmail.com> <96BD287F-910B-4E50-B902-4D135D2DFEAE@laposte.net> <CAH3bfADrj2BuQwEM3=ZC6_QCDe7RuEorM1=bAoyNH7JJao2_xQ@mail.gmail.com>
To: Qiong <bingxuere@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 10 Oct 2011 15:44:04 -0000

--Apple-Mail-48-651826306
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 10 oct. 2011 =E0 17:33, Qiong a =E9crit :

> Hi, Qiong,
>=20
> Please see inline.
>> On Mon, Oct 10, 2011 at 3:26 PM, R=E9mi Despr=E9s =
<despres.remi@laposte.net> wrote:
>>=20
>> The 4rd function examines ALL packets that reach the CE.
>> It processes all those that have V in their destination addresses, =
and only those.
>>=20
>> Qiong: I think it might be better achieved via routing lookup for =
prefix+V bits (e.g. /80 ), rather than extracting V bits before =
traditional routing.
>> =20
>>=20
>> The reason why 4rd packets reach the CE is NOT that their =
destinations are the IPv6 address that the CE has on its link to the =
ISP.=20
>> It is that their destinations start with the CE delegated prefix. The =
routing information base of the ISP edge router is such that, for such =
destinations, the next hop is the CE.=20
>>=20
>>=20
>>> Then the variable "max" PSID derived from dst. ports may get a =
problem.
>=20
>>  Qiong: I think the "max" PSID design might have a problem in virtual =
interface implementation. When implementing an virtual =
encapsulation/translation interface, the packets can reach the virtual =
interface from a downstream physical interface via traditional routing.
>=20
>> For example, identifying a specific address or /80 prefix to the =
destinated virtual interface. However, when the "max" PSID is not stable =
and the length of "Rule IPv6 prefix+ Max PSID" exceeds 64 bit long, how =
to construct this kind of internal routing table ? I think it would be =
too many routing entries here.
>=20
> Routing being only concerned with /64s, and information in IIDs being =
used only by 4rd functions themselves, or for O&M, I don't see the =
problem.
>=20
> Qiong: My concern is specific for virtual interface implementation. If =
you implement a virtual interface(as most existing encapsulation =
approaches have adopted in CPE ), you still need to do routing within CE =
(from physical interface to virtual interface). In traditional =
encapsulation implementation, a specific routing entry can be assigned =
to help forward the traffic with a tunnel endpoint address. And all the =
following decapsulation things can be done in this virtual interface. I =
think this kind of implementation can be applied to translation as well, =
to make use of traditional routing and implementation translation =
functionality only on the virtual interface. And since the first 64 bits =
will be same for both native traffic and translated traffic, the lower =
bits would be needed for internal routing. That's why I think unstable =
"max" PSID would make it difficult to construct internal routing table =
(not routing procedure from ISP to CE). But anyway, it is only =
restricted to this kind of implementation (determine the translated =
traffic by routing rather than bit extracting).=20
>=20
> Hope it is clear now.

This is an implementation issue about which others may be better placed =
than me to give a quick answer.

I only know it is feasible by putting some simple code at some =
appropriate place(s).
Sorry I can't tell more without some consultancy based on details of =
your implementation.

Regards,
RD



>=20
> Thanks=20
>=20
> Qiong
>=20


--Apple-Mail-48-651826306
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 10 oct. 2011 =E0 17:33, Qiong a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">Hi, =
Qiong,<br><br>Please see inline.<br><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;"><div =
style=3D"word-wrap:break-word"><div><div><div class=3D"h5">

<blockquote type=3D"cite"><div><div class=3D"gmail_quote">On Mon, Oct =
10, 2011 at 3:26 PM, R=E9mi Despr=E9s <span dir=3D"ltr">&lt;<a =
href=3D"mailto:despres.remi@laposte.net" =
target=3D"_blank">despres.remi@laposte.net</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word"><br><div><div>The 4rd function examines =
ALL packets that reach the CE.</div><div>It processes all those that =
have V in their destination addresses, and only those.</div>



</div></div></blockquote><div><br></div><div>Qiong: I think it might be =
better achieved via routing lookup for prefix+V bits (e.g. /80 ), rather =
than extracting V bits before traditional =
routing.</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" =
style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8=
ex;border-left-width:1px;border-left-color:rgb(204, 204, =
204);border-left-style:solid;padding-left:1ex">



<div style=3D"word-wrap:break-word"><div><div><br></div><div>The reason =
why 4rd packets reach the CE is NOT that their destinations are the IPv6 =
address that the CE has on its link to the ISP.&nbsp;</div><div>It is =
that their destinations start with the CE delegated prefix. The routing =
information base of the ISP edge router is such that, for such =
destinations, the next hop is the CE.&nbsp;</div>



<div><div><br></div><div><br></div><blockquote type=3D"cite"><div =
bgcolor=3D"#FFFFFF" text=3D"#000000">Then the variable "max" PSID =
derived
    from dst. ports may get a =
problem.</div></blockquote></div></div></div></blockquote></div></div></bl=
ockquote><br><blockquote type=3D"cite"><div><div =
class=3D"gmail_quote"><div>&nbsp;Qiong: I think the "max" PSID design =
might have a problem in virtual interface implementation. When =
implementing an virtual encapsulation/translation interface, the packets =
can reach the virtual interface from a downstream physical interface via =
traditional routing.</div>

</div></div></blockquote><br><blockquote type=3D"cite"><div><div =
class=3D"gmail_quote"><div> For example, identifying a specific address =
or /80 prefix to the destinated virtual interface. However, when the =
"max" PSID is not stable and the length of "Rule IPv6 prefix+ Max PSID" =
exceeds 64 bit long, how to construct this kind of internal routing =
table ? I think it would be too many routing entries here.</div>

</div></div></blockquote><div><br></div></div></div>Routing being only =
concerned with /64s,&nbsp;and information in IIDs being used only by 4rd =
functions themselves, or for O&amp;M, I don't see the =
problem.</div><div><br>
</div>
</div></blockquote><div>Qiong: My concern is specific for virtual =
interface implementation. If you implement a virtual interface(as most =
existing encapsulation approaches have adopted in CPE ), you still need =
to do routing within CE (from physical interface to virtual interface). =
In traditional encapsulation implementation, a specific routing entry =
can be assigned to help forward the traffic with a tunnel endpoint =
address. And all the following decapsulation things can be done in this =
virtual interface. I think this kind of implementation can be applied to =
translation as well, to make use of traditional routing and =
implementation translation functionality only on the virtual interface. =
And since the first 64 bits will be same for both native traffic and =
translated traffic, the lower bits would be needed for internal routing. =
That's why I think unstable "max" PSID would make it difficult to =
construct internal routing table (not routing procedure from ISP to CE). =
But anyway, it is only restricted to this kind of implementation =
(determine the translated traffic by routing rather than bit =
extracting).&nbsp;</div>

<div><br></div><div>Hope it is clear =
now.</div></div></blockquote><div><br></div><div><div>This is an =
implementation issue about which others may be better placed than me to =
give a quick answer.</div><div><br></div><div>I only know it is feasible =
by putting some simple code at some appropriate =
place(s).</div><div>Sorry I can't tell more without some consultancy =
based on details of your =
implementation.</div><div><br></div><div>Regards,</div><div>RD</div></div>=
<div><br></div><div><br></div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div><br></div><div>Thanks&nbsp;</div><div><br></div=
><div>Qiong</div><div><br></div></div>
</blockquote></div><br></body></html>=

--Apple-Mail-48-651826306--

From jacni@jacni.com  Tue Oct 11 00:35:38 2011
Return-Path: <jacni@jacni.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 1729021F877F for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 00:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.177
X-Spam-Level: 
X-Spam-Status: No, score=-0.177 tagged_above=-999 required=5 tests=[AWL=-1.390, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, J_CHICKENPOX_61=0.6, J_CHICKENPOX_92=0.6, MANGLED_FROM=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mlu0MdlDTjnk for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 00:35:36 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 1034D21F8713 for <softwires@ietf.org>; Tue, 11 Oct 2011 00:35:34 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 4E88E380092 for <softwires@ietf.org>; Tue, 11 Oct 2011 03:35:33 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id A8D0434009F for <softwires@ietf.org>; Tue, 11 Oct 2011 15:35:29 +0800 (CST)
Received: from [172.20.24.150] (unknown [221.11.61.55]) by app (Coremail) with SMTP id +AWowJDbhwm58ZNOxPIXAA--.31825S2; Tue, 11 Oct 2011 15:35:23 +0800 (CST)
Message-ID: <4E93F21B.4060702@jacni.com>
Date: Tue, 11 Oct 2011 15:36:59 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Qiong <bingxuere@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <CAH3bfABJ=6CHA_QmtxtnoGmS2bSPhrDtdpebm9TwTLeMVdVMSA@mail.gmail.com> <96BD287F-910B-4E50-B902-4D135D2DFEAE@laposte.net> <CAH3bfADrj2BuQwEM3=ZC6_QCDe7RuEorM1=bAoyNH7JJao2_xQ@mail.gmail.com>
In-Reply-To: <CAH3bfADrj2BuQwEM3=ZC6_QCDe7RuEorM1=bAoyNH7JJao2_xQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090103040301030203050303"
X-CM-TRANSID: +AWowJDbhwm58ZNOxPIXAA--.31825S2
X-Coremail-Antispam: 1UD129KBjvJXoWxGryDJF47XFyDWFWkXryxZrb_yoW5Aryrpa 1fKr15tanrJw1xuF1fXw1ftr1SgF4kGF4jkr92kw4kWws8JFyftF1xK34Yka43ur1rJ342 qr40yrW8u3yUZrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU7mb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VWkKwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK64x0aVW7Gw IE548m6rI_Jw1UWr17M2vj6xkI62vS6c8GOVWUtr1rJFylYx0E2Ix0cI8IcVAFwI0_Jr0_ Jr4lYx0Ex4A2jsIE14v26r1j6r4UM4x0Y48IcVAKI48JMx8GjcxK6IxK0xIIj40E5I8Crw CYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI7VAKI48JMxCIbVAxMI8E67AF67kF1VAF wI0_Jrv_JF1lIxkGc2Ij64vIr4UvcSsGvfC2KfnxnUUI43ZEXa7IU0S_MDUUUUU==
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQISEko7lOhhXAAAsz
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 07:35:38 -0000

This is a multi-part message in MIME format.
--------------090103040301030203050303
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

hi,

On 10/10/2011 11:33 PM, Qiong wrote:
> Hi, Qiong,
>
> Please see inline.
>
>>     On Mon, Oct 10, 2011 at 3:26 PM, RÃ©mi DesprÃ©s
>>     <despres.remi@laposte.net <mailto:despres.remi@laposte.net>> wrote:
>>
>>
>>         The 4rd function examines ALL packets that reach the CE.
>>         It processes all those that have V in their destination
>>         addresses, and only those.
>>
>>
>>     Qiong: I think it might be better achieved via routing lookup for
>>     prefix+V bits (e.g. /80 ), rather than extracting V bits before
>>     traditional routing.
>>
>>
>>         The reason why 4rd packets reach the CE is NOT that their
>>         destinations are the IPv6 address that the CE has on its link
>>         to the ISP.
>>         It is that their destinations start with the CE delegated
>>         prefix. The routing information base of the ISP edge router
>>         is such that, for such destinations, the next hop is the CE.
>>
>>
>>>         Then the variable "max" PSID derived from dst. ports may get
>>>         a problem.
>>
>
>>      Qiong: I think the "max" PSID design might have a problem in
>>     virtual interface implementation. When implementing an virtual
>>     encapsulation/translation interface, the packets can reach the
>>     virtual interface from a downstream physical interface via
>>     traditional routing.
>
>>     For example, identifying a specific address or /80 prefix to the
>>     destinated virtual interface. However, when the "max" PSID is not
>>     stable and the length of "Rule IPv6 prefix+ Max PSID" exceeds 64
>>     bit long, how to construct this kind of internal routing table ?
>>     I think it would be too many routing entries here.
>
>     Routing being only concerned with /64s, and information in IIDs
>     being used only by 4rd functions themselves, or for O&M, I don't
>     see the problem.
>
> Qiong: My concern is specific for virtual interface implementation. If 
> you implement a virtual interface(as most existing encapsulation 
> approaches have adopted in CPE ), you still need to do routing within 
> CE (from physical interface to virtual interface). In traditional 
> encapsulation implementation, a specific routing entry can be assigned 
> to help forward the traffic with a tunnel endpoint address. And all 
> the following decapsulation things can be done in this virtual 
> interface. I think this kind of implementation can be applied to 
> translation as well, to make use of traditional routing and 
> implementation translation functionality only on the virtual interface.
I doubt whether the two can share the same interface by just switching 
between encapsulation/translation modes, maybe a separated one is needed 
for translation since the implementation is different.


Cheers,
Jacni

> And since the first 64 bits will be same for both native traffic and 
> translated traffic, the lower bits would be needed for internal 
> routing. That's why I think unstable "max" PSID would make it 
> difficult to construct internal routing table (not routing procedure 
> from ISP to CE). But anyway, it is only restricted to this kind of 
> implementation (determine the translated traffic by routing rather 
> than bit extracting).
>
> Hope it is clear now.
>
> Thanks
>
> Qiong
>

--------------090103040301030203050303
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 10/10/2011 11:33 PM, Qiong wrote:
    <blockquote
cite="mid:CAH3bfADrj2BuQwEM3=ZC6_QCDe7RuEorM1=bAoyNH7JJao2_xQ@mail.gmail.com"
      type="cite">Hi, Qiong,<br>
      <br>
      Please see inline.<br>
      <div class="gmail_quote">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div style="word-wrap:break-word">
            <div>
              <div>
                <div class="h5">
                  <blockquote type="cite">
                    <div>
                      <div class="gmail_quote">On Mon, Oct 10, 2011 at
                        3:26 PM, RÃ©mi DesprÃ©s <span dir="ltr">&lt;<a
                            moz-do-not-send="true"
                            href="mailto:despres.remi@laposte.net"
                            target="_blank">despres.remi@laposte.net</a>&gt;</span>
                        wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex">
                          <div style="word-wrap:break-word"><br>
                            <div>
                              <div>The 4rd function examines ALL packets
                                that reach the CE.</div>
                              <div>It processes all those that have V in
                                their destination addresses, and only
                                those.</div>
                            </div>
                          </div>
                        </blockquote>
                        <div><br>
                        </div>
                        <div>Qiong: I think it might be better achieved
                          via routing lookup for prefix+V bits (e.g. /80
                          ), rather than extracting V bits before
                          traditional routing.</div>
                        <div>Â </div>
                        <blockquote class="gmail_quote"
                          style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,
                          204,
                          204);border-left-style:solid;padding-left:1ex">
                          <div style="word-wrap:break-word">
                            <div>
                              <div><br>
                              </div>
                              <div>The reason why 4rd packets reach the
                                CE is NOT that their destinations are
                                the IPv6 address that the CE has on its
                                link to the ISP.Â </div>
                              <div>It is that their destinations start
                                with the CE delegated prefix. The
                                routing information base of the ISP edge
                                router is such that, for such
                                destinations, the next hop is the CE.Â </div>
                              <div>
                                <div><br>
                                </div>
                                <div><br>
                                </div>
                                <blockquote type="cite">
                                  <div bgcolor="#FFFFFF" text="#000000">Then
                                    the variable "max" PSID derived from
                                    dst. ports may get a problem.</div>
                                </blockquote>
                              </div>
                            </div>
                          </div>
                        </blockquote>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                  <blockquote type="cite">
                    <div>
                      <div class="gmail_quote">
                        <div>Â Qiong: I think the "max" PSID design might
                          have a problem in virtual interface
                          implementation. When implementing an virtual
                          encapsulation/translation interface, the
                          packets can reach the virtual interface from a
                          downstream physical interface via traditional
                          routing.</div>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                  <blockquote type="cite">
                    <div>
                      <div class="gmail_quote">
                        <div> For example, identifying a specific
                          address or /80 prefix to the destinated
                          virtual interface. However, when the "max"
                          PSID is not stable and the length of "Rule
                          IPv6 prefix+ Max PSID" exceeds 64 bit long,
                          how to construct this kind of internal routing
                          table ? I think it would be too many routing
                          entries here.</div>
                      </div>
                    </div>
                  </blockquote>
                  <div><br>
                  </div>
                </div>
              </div>
              Routing being only concerned with /64s,Â and information in
              IIDs being used only by 4rd functions themselves, or for
              O&amp;M, I don't see the problem.</div>
            <div><br>
            </div>
          </div>
        </blockquote>
        <div>Qiong: My concern is specific for virtual interface
          implementation. If you implement a virtual interface(as most
          existing encapsulation approaches have adopted in CPE ), you
          still need to do routing within CE (from physical interface to
          virtual interface). In traditional encapsulation
          implementation, a specific routing entry can be assigned to
          help forward the traffic with a tunnel endpoint address. And
          all the following decapsulation things can be done in this
          virtual interface. I think this kind of implementation can be
          applied to translation as well, to make use of traditional
          routing and implementation translation functionality only on
          the virtual interface. </div>
      </div>
    </blockquote>
    I doubt whether the two can share the same interface by just
    switching between encapsulation/translation modes, maybe a separated
    one is needed for translation since the implementation is different.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAH3bfADrj2BuQwEM3=ZC6_QCDe7RuEorM1=bAoyNH7JJao2_xQ@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>And since the first 64 bits will be same for both native
          traffic and translated traffic, the lower bits would be needed
          for internal routing. That's why I think unstable "max" PSID
          would make it difficult to construct internal routing table
          (not routing procedure from ISP to CE). But anyway, it is only
          restricted to this kind of implementation (determine the
          translated traffic by routing rather than bit extracting).Â </div>
        <div><br>
        </div>
        <div>Hope it is clear now.</div>
        <div><br>
        </div>
        <div>ThanksÂ </div>
        <div><br>
        </div>
        <div>Qiong</div>
        <div><br>
        </div>
      </div>
    </blockquote>
  </body>
</html>

--------------090103040301030203050303--


From bingxuere@gmail.com  Tue Oct 11 01:24:25 2011
Return-Path: <bingxuere@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 6C49B21F8D61 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 01:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.082
X-Spam-Level: 
X-Spam-Status: No, score=-2.082 tagged_above=-999 required=5 tests=[AWL=0.917,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_92=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZV8ZOmHJNCOi for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 01:24:24 -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 B10E021F8D68 for <softwires@ietf.org>; Tue, 11 Oct 2011 01:24:24 -0700 (PDT)
Received: by gyd12 with SMTP id 12so7687033gyd.31 for <softwires@ietf.org>; Tue, 11 Oct 2011 01:24:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=q7qTGI556/5ky7oq2xIL1qxLx55hPpxHnBsnCqUkImk=; b=gifAxMV4kdgMzzMkRoiprtbD1VR7N7ZYg1/edV0DAjja9vHaAExIveskLLlF05xj2t dTmkVbXCiR4ipcilIbJoiHI+OXRRnAnmkVHwC8McF8q1fBoo8fZngQFXgi8MHjdpeGJQ +s9tRmhhw0i9l528fFgbAcMukfPhuWtZ00GrY=
Received: by 10.42.163.4 with SMTP id a4mr9370716icy.4.1318321463064; Tue, 11 Oct 2011 01:24:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Tue, 11 Oct 2011 01:24:03 -0700 (PDT)
In-Reply-To: <4E93F21B.4060702@jacni.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <CAH3bfABJ=6CHA_QmtxtnoGmS2bSPhrDtdpebm9TwTLeMVdVMSA@mail.gmail.com> <96BD287F-910B-4E50-B902-4D135D2DFEAE@laposte.net> <CAH3bfADrj2BuQwEM3=ZC6_QCDe7RuEorM1=bAoyNH7JJao2_xQ@mail.gmail.com> <4E93F21B.4060702@jacni.com>
From: Qiong <bingxuere@gmail.com>
Date: Tue, 11 Oct 2011 16:24:03 +0800
Message-ID: <CAH3bfACkMoYhpruiTqYrZUoN7NS2T4YG_1kxz9v=dvAO6BGGBw@mail.gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=90e6ba6e8cfe81778404af01a2b8
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 08:24:25 -0000

--90e6ba6e8cfe81778404af01a2b8
Content-Type: text/plain; charset=UTF-8

Hi, Jacni


>>   Qiong: My concern is specific for virtual interface implementation. If
> you implement a virtual interface(as most existing encapsulation approaches
> have adopted in CPE ), you still need to do routing within CE (from physical
> interface to virtual interface). In traditional encapsulation
> implementation, a specific routing entry can be assigned to help forward the
> traffic with a tunnel endpoint address. And all the following decapsulation
> things can be done in this virtual interface. I think this kind of
> implementation can be applied to translation as well, to make use of
> traditional routing and implementation translation functionality only on the
> virtual interface.
>
> I doubt whether the two can share the same interface by just switching
> between encapsulation/translation modes, maybe a separated one is needed for
> translation since the implementation is different.
>
>
> Agree that separated interfaces might be needed for different
implementation. As long as the traffic can still be differentiated via
routing, different functionality can be applied to different interfaces. So
I think we may need to focus on defining a flexible prefix for routing,
rather than bit extracting. But anyway, I do not think it would be a common
case that translation and encapsulation will be running simultaneous.

Best wishes

Qiong


> Cheers,
> Jacni
>
>
>  And since the first 64 bits will be same for both native traffic and
> translated traffic, the lower bits would be needed for internal routing.
> That's why I think unstable "max" PSID would make it difficult to construct
> internal routing table (not routing procedure from ISP to CE). But anyway,
> it is only restricted to this kind of implementation (determine the
> translated traffic by routing rather than bit extracting).
>
>  Hope it is clear now.
>
>  Thanks
>
>  Qiong
>
>

--90e6ba6e8cfe81778404af01a2b8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Jacni<br><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"=
><div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"im"><blockquote ty=
pe=3D"cite">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"wor=
d-wrap:break-word"><div><br>
            </div>
          </div>
        </blockquote>
        <div>Qiong: My concern is specific for virtual interface
          implementation. If you implement a virtual interface(as most
          existing encapsulation approaches have adopted in CPE ), you
          still need to do routing within CE (from physical interface to
          virtual interface). In traditional encapsulation
          implementation, a specific routing entry can be assigned to
          help forward the traffic with a tunnel endpoint address. And
          all the following decapsulation things can be done in this
          virtual interface. I think this kind of implementation can be
          applied to translation as well, to make use of traditional
          routing and implementation translation functionality only on
          the virtual interface. </div>
      </div>
    </blockquote></div>
    I doubt whether the two can share the same interface by just
    switching between encapsulation/translation modes, maybe a separated
    one is needed for translation since the implementation is different.<br=
>
    <br>
    <br></div></blockquote><div>Agree that separated interfaces might be ne=
eded for different implementation. As long as the traffic can still be diff=
erentiated via routing, different functionality can be applied to different=
 interfaces. So I think we may need to focus on defining a flexible prefix =
for routing, rather than bit extracting. But anyway, I do not think it woul=
d be a common case that translation and encapsulation will be running simul=
taneous.=C2=A0</div>

<div><br></div><div>Best wishes</div><div><br></div><div>Qiong</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex;"><div bgcolor=3D"#FFFFFF" text=
=3D"#000000">


    Cheers,<br><font color=3D"#888888">
    Jacni</font><div class=3D"im"><br>
    <br>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div>And since the first 64 bits will be same for both native
          traffic and translated traffic, the lower bits would be needed
          for internal routing. That&#39;s why I think unstable &quot;max&q=
uot; PSID
          would make it difficult to construct internal routing table
          (not routing procedure from ISP to CE). But anyway, it is only
          restricted to this kind of implementation (determine the
          translated traffic by routing rather than bit extracting).=C2=A0<=
/div>
        <div><br>
        </div>
        <div>Hope it is clear now.</div>
        <div><br>
        </div>
        <div>Thanks=C2=A0</div>
        <div><br>
        </div>
        <div>Qiong</div>
        <div><br>
        </div>
      </div>
    </blockquote>
  </div></div>

</blockquote></div><br>

--90e6ba6e8cfe81778404af01a2b8--

From satoru.matsushima@gmail.com  Tue Oct 11 01:30:54 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 7336B21F8B4A for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 01: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33a+G67V5kJK for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 01:30:53 -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 3410321F84B6 for <softwires@ietf.org>; Tue, 11 Oct 2011 01:30:34 -0700 (PDT)
Received: by gyd12 with SMTP id 12so7692945gyd.31 for <softwires@ietf.org>; Tue, 11 Oct 2011 01:30:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=dvsjOaM5Y/AZxWpEX9urjvF3Q4JkmsxMp7ODf+Bo+lc=; b=tKd+3+ZqA7xLjN0BoBAdJxcA59Tt6wrqguuYzvRUHUFPDN8iL2JBmDBjnW2y3jnHLu sivQkvdubLr4y8CgReAGEF59Gf7XWmU6XU8Xp3m8tJyP/A0G7NSIp3o53hqLyTQb66d6 W/Cp13waOlKccQTIElem0jT6Tn4XaRHcF8/IY=
Received: by 10.68.2.163 with SMTP id 3mr2794239pbv.25.1318321832570; Tue, 11 Oct 2011 01:30:32 -0700 (PDT)
Received: from [10.201.83.217] ([202.45.12.174]) by mx.google.com with ESMTPS id h5sm76877410pbq.11.2011.10.11.01.30.29 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Oct 2011 01:30:31 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=utf-8
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com>
Date: Tue, 11 Oct 2011 17:30:25 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com>
To: Leaf yeh <leaf.y.yeh@huawei.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 08:30:54 -0000

Leaf, thanks for the summary.

On 2011/10/10, at 20:34, Leaf yeh wrote:

> Remi - >> a1- If the CE has an exclusive or shared IPv4 address:
>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
>>> +-------------+--------+---+---+----------------+------+-----+---+
>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>>> +-------------+--------+---+---+----------------+------+-----+---+
> Ole - > putting the IPv4 address / port information at the end of the =
interface identifier will allow for > /64 support. > what's the L?
> Remi - Don't see what you found unclear.
>=20
>=20
> Question: Supposed the question is on the last field, named 'L', in =
the new address format.
>=20

Since Remi's draft doesn't specify 'CE IPv6 prefix length', IPv6 prefix =
can't be self delimiting to extract IPv4 address and port-set ID in the =
case of double translation. That's my understanding. Is that correct?
As '4rd-a', and 4via6(draft-murakami-softwire-4v6-translation), the 'L' =
bits are not necessary because 'CE IPv6 prefix length' is defined =
through a domain, instead of 'L'.


>=20
> Remi - >> A Destination address from a CE to the outside IPv4 Internet =
is:
>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>> +--------------------------+----+---------------+------------+---+
>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>> +--------------------------+----+---------------+------------+---+
> Ole - this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
> Remi - Copying an available IPv4 address at a fixed place isn't IMHO a =
"big change".
>=20
>=20
> Concern: Supposed the replacement of the 1st 64bits of the BR address =
with a subnet prefix is not for the tunnel case if the field of IPv4 =
address can be variable, right?

I think that it could be a case where the BR address with a subnet =
prefix for the tunnel case. My concern rather than the BR address is =
that a CE should pick packets up which have 'V' in IID, even destined =
prefixes are delegated to nodes which are behind of the CE.


>=20
> In fact, I doubts we could have the same address mapping for both =
tunnel and translation. Supposed the address of tunnel end-points is =
preferred to be fixed, but the address for the translation could be =
variable.
>=20

I think we could have it.

cheers,
--satoru


>=20
> Best Regards,
> Leaf
>=20
>=20
> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] =
On Behalf Of R=C3=A9mi Despr=C3=A9s
> Sent: Thursday, October 06, 2011 6:07 PM
> To: Ole Troan
> Cc: Softwires-wg
> Subject: Re: [Softwires] Proposed Unified Address Mapping for =
encapsulation and double-translation
>=20
>=20
> Le 6 oct. 2011 =C3=A0 18:47, Ole Troan a =C3=A9crit :
>=20
>> Remi,
>>=20
>> [...]
>>=20
>>> 2.
>>> (a)
>>> The IPv6 Source address of an IPv4 packet from a CE is:
>>>=20
>>> a1- If the CE has an exclusive or shared IPv4 address:
>>>=20
>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
>>> +-------------+--------+---+---+----------------+------+-----+---+
>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>>> +-------------+--------+---+---+----------------+------+-----+---+
>>=20
>> putting the IPv4 address / port information at the end of the =
interface identifier will allow for > /64 support.
>=20
> Could you explain more the requirement you have in mind? =20
>=20
>> what's the L?
>=20
> On the picture, L is 32 bits + Length(PSID).
> Don't see what you found unclear.=20
>=20
>>=20
>> you suggest that the first subnet of an allocation should be used for =
this purpose.
>=20
> Did I do this?
> Please explain because that's not, IMHO,  something to be done.
>=20
>> the first subnet is convenient to use for e.g. manual addressing =
(since it allows the :: short hand).
>> I do wonder if this has to be provisioned. e.g. some deployments may =
use the first subnet for the link between
>> CE and PE. (i.e. a /56 - 1 using the PD exclude option is used).
>=20
> See just above.
>=20
>>=20
>>> a2- If the CE has an IPv4 prefix:
>>>=20
>>> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
>>> +-------------+--------+---+---+-------------+---------------+---+
>>> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
>>> +-------------+--------+---+---+-------------+---------------+---+
>>>=20
>>> (b)
>>> V is the mark that characterizes IPv6 packets that are in reality =
IPv4 packets.
>>> Its value differs from any permitted value of this octet in IPv6 =
IIDs  (ref RFC 4291).
>>>=20
>>> It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.
>>>=20
>>> An unambiguous mark is fortunately possible because currently =
permitted IIDs have in their first octet either bit6 =3D 0 (the "u" =
bit"), or bit6 =3D 1 and bit7=3D 0 (the "g" bit).
>>> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction is therefore deterministic.
>>>=20
>>> The proposed V is =3D 00000011.=20
>>> (With other values of this octet, other IID formats can be defined =
in case some would be useful in the future.)
>>>=20
>>> Note that, if and when a consensus is reached in Softwire, an =
extension of RFC 4291 will have to be submitted to 6MAN.=20
>>=20
>> or rather IEEE?
>=20
> IMHO, IEEE has nothing to do with a marker that is purposely an escape =
mechanism from the modified EUI-64 format of RFC 4291.
>=20
>> I am not convinced that "V" is needed.
>=20
> The point is more, IMHO, whether you have an objection to it (and in =
this case which one).
> Reason is that we are working for a consensus, and several are =
satisfied with the explanation that there are use cases where it is =
useful, and none where it is harmful.
>=20
>> you could even use the IANA OUI if pretty printing was required.
>=20
> The point is that it takes 32 bits which is too much to have IPv4 =
address + PSID in the IID.
>=20
>=20
>>> (c)                                  =20
>>> A Destination address from a CE to the outside IPv4 Internet is:
>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>> +--------------------------+----+---------------+------------+---+
>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>> +--------------------------+----+---------------+------------+---+
>>=20
>> this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
>=20
> Copying an available IPv4 address at a fixed place isn't IMHO a "big =
change".
>=20
>> if we also allow for a BR subnet prefix of /128 I'm OK with this (I =
think).
>=20
> I don't understand what you mean by "Subnet prefix of /128".
>=20
>=20
>>> Note that if double-translation CEs are notified to use U instead of =
V, the last octet becomes 0 per RFC  6052.
>>=20
>> how would a CE know if it was single or double translating?
>=20
> Presumably with a usual method, e.g. DHCPv6.
> Anything problematic with that?
>=20
>=20
>> e.g we could do:
>>=20
>> <--------- 64 ------------><--- 24 ------><----- 32 -------><--8 >
>> +-------------+--------+---+--------------------+------+-----+---+
>> | IPv6 prefix |CE index| S | 00-00-5E    |  IPv4 address  | PSID |
>> +-------------+--------+---+---+----------------+------+-----+---+
>>=20
>> we also need to handle the case where IPv6 prefix + CE index > 64.
>=20
> Please explain more your understanding of this requirement.
> (I personally believe we should avoid that.)
>=20
>> I suggest we then just put as much as the interface identifier that =
will fit.
>=20
>=20
> May I suggest that, to be more constructive, you could first express =
your objections to the proposed unified mapping, rather than making a =
number of new proposals whose justifications are sometimes hard to =
understand,=20
>=20
> Cheers,
> RD=20
>=20
>=20
>>=20
>> cheers,
>> Ole
>>=20
>>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From satoru.matsushima@gmail.com  Tue Oct 11 01:40:35 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 47AD921F8672 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 01:40:35 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OnCYiMeXVStY for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 01:40:34 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id C2F0C21F8669 for <softwires@ietf.org>; Tue, 11 Oct 2011 01:40:34 -0700 (PDT)
Received: by qyk33 with SMTP id 33so5324447qyk.10 for <softwires@ietf.org>; Tue, 11 Oct 2011 01:40:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=OJoASTizP//fKKWfhOYlu3QhWRrrhrFQlqqWo8BJOrE=; b=Pp1tRRn8IQfdbDCZgcUu2L0U1G78Rc1GsGvMtpcjH9ylxIKqQLejgTJDiY0nPHaVwe QtFBx5DuNF0ZDSGIcz6rwdi7Lao47nlscm1D+1lABMXGzYj3W8RNcCrYEvYjhpm3XEKF GBurzwz4HEqQHGpnXYf8Dm2cWcDvNVIKq1Wy0=
Received: by 10.68.0.5 with SMTP id 5mr44359514pba.118.1318322433846; Tue, 11 Oct 2011 01:40:33 -0700 (PDT)
Received: from [10.201.83.217] ([202.45.12.174]) by mx.google.com with ESMTPS id ml4sm76959898pbc.0.2011.10.11.01.40.31 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Oct 2011 01:40:32 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <B8DEB256-0585-4279-BC8F-96064B4FF606@employees.org>
Date: Tue, 11 Oct 2011 17:40:29 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <B69A4DBE-96D3-46AC-A33A-EACE8534F1FE@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <4E92A32C.30306@jacni.com> <B8DEB256-0585-4279-BC8F-96064B4FF606@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1244.3)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 08:40:35 -0000

On 2011/10/10, at 17:58, Ole Troan wrote:

>>> The 4rd function examines ALL packets that reach the CE.
>>> It processes all those that have V in their destination addresses, =
and only those.
>>>=20
>> This is a big change to the current forwarding behavior of CPE =
devices, doable, but quite different from, for example, some =
encapsulation/decapsulation implementations.
>=20
> +1.
> doable in theory, but I share your concerns.
>=20
> cheers,
> Ole

+1.

cheers,
--satoru


From despres.remi@laposte.net  Tue Oct 11 01:42:28 2011
Return-Path: <despres.remi@laposte.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 C8E9121F8D61 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 01:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Level: 
X-Spam-Status: No, score=-1.554 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eoe4353HruxR for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 01:42:28 -0700 (PDT)
Received: from smtpout.laposte.net (smtpout2.laposte.net [193.253.67.227]) by ietfa.amsl.com (Postfix) with ESMTP id 72D7821F8CCC for <softwires@ietf.org>; Tue, 11 Oct 2011 01:42:27 -0700 (PDT)
Received: from [192.168.0.21] ([88.166.221.144]) by mwinf8503-out with ME id jLiQ1h00337Y3f403LiQej; Tue, 11 Oct 2011 10:42:25 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com>
Date: Tue, 11 Oct 2011 10:42:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <815B27C6-4C23-4634-A619-912FCC37FEAE@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com> <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 08:42:28 -0000

Le 11 oct. 2011 =E0 10:30, Satoru Matsushima a =E9crit :

> Leaf, thanks for the summary.
>=20
> On 2011/10/10, at 20:34, Leaf yeh wrote:
>=20
>> Remi - >> a1- If the CE has an exclusive or shared IPv4 address:
>>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>> Ole - > putting the IPv4 address / port information at the end of the =
interface identifier will allow for > /64 support. > what's the L?
>> Remi - Don't see what you found unclear.
>>=20
>>=20
>> Question: Supposed the question is on the last field, named 'L', in =
the new address format.
>>=20
>=20
> Since Remi's draft doesn't specify 'CE IPv6 prefix length', IPv6 =
prefix can't be self delimiting to extract IPv4 address and port-set ID =
in the case of double translation. That's my understanding. Is that =
correct?

In my understanding, yes.

Now, putting the "CE IPv6 prefix length" back as a rule parameter =
shouldn't be a problem if the idea of linking IPv4 and IPv6 sizes of =
address spaces is abandoned (a choice that, I have to agree, simplifies =
the design).

Cheers,
RD=20


> As '4rd-a', and 4via6(draft-murakami-softwire-4v6-translation), the =
'L' bits are not necessary because 'CE IPv6 prefix length' is defined =
through a domain, instead of 'L'.
>=20
>=20
>>=20
>> Remi - >> A Destination address from a CE to the outside IPv4 =
Internet is:
>>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>>> +--------------------------+----+---------------+------------+---+
>>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>>> +--------------------------+----+---------------+------------+---+
>> Ole - this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
>> Remi - Copying an available IPv4 address at a fixed place isn't IMHO =
a "big change".
>>=20
>>=20
>> Concern: Supposed the replacement of the 1st 64bits of the BR address =
with a subnet prefix is not for the tunnel case if the field of IPv4 =
address can be variable, right?
>=20
> I think that it could be a case where the BR address with a subnet =
prefix for the tunnel case. My concern rather than the BR address is =
that a CE should pick packets up which have 'V' in IID, even destined =
prefixes are delegated to nodes which are behind of the CE.
>=20
>=20
>>=20
>> In fact, I doubts we could have the same address mapping for both =
tunnel and translation. Supposed the address of tunnel end-points is =
preferred to be fixed, but the address for the translation could be =
variable.
>>=20
>=20
> I think we could have it.
>=20
> cheers,
> --satoru
>=20
>=20
>>=20
>> Best Regards,
>> Leaf
>>=20
>>=20
>> -----Original Message-----
>> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] =
On Behalf Of R=E9mi Despr=E9s
>> Sent: Thursday, October 06, 2011 6:07 PM
>> To: Ole Troan
>> Cc: Softwires-wg
>> Subject: Re: [Softwires] Proposed Unified Address Mapping for =
encapsulation and double-translation
>>=20
>>=20
>> Le 6 oct. 2011 =E0 18:47, Ole Troan a =E9crit :
>>=20
>>> Remi,
>>>=20
>>> [...]
>>>=20
>>>> 2.
>>>> (a)
>>>> The IPv6 Source address of an IPv4 packet from a CE is:
>>>>=20
>>>> a1- If the CE has an exclusive or shared IPv4 address:
>>>>=20
>>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>=20
>>> putting the IPv4 address / port information at the end of the =
interface identifier will allow for > /64 support.
>>=20
>> Could you explain more the requirement you have in mind? =20
>>=20
>>> what's the L?
>>=20
>> On the picture, L is 32 bits + Length(PSID).
>> Don't see what you found unclear.=20
>>=20
>>>=20
>>> you suggest that the first subnet of an allocation should be used =
for this purpose.
>>=20
>> Did I do this?
>> Please explain because that's not, IMHO,  something to be done.
>>=20
>>> the first subnet is convenient to use for e.g. manual addressing =
(since it allows the :: short hand).
>>> I do wonder if this has to be provisioned. e.g. some deployments may =
use the first subnet for the link between
>>> CE and PE. (i.e. a /56 - 1 using the PD exclude option is used).
>>=20
>> See just above.
>>=20
>>>=20
>>>> a2- If the CE has an IPv4 prefix:
>>>>=20
>>>> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
>>>> +-------------+--------+---+---+-------------+---------------+---+
>>>> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
>>>> +-------------+--------+---+---+-------------+---------------+---+
>>>>=20
>>>> (b)
>>>> V is the mark that characterizes IPv6 packets that are in reality =
IPv4 packets.
>>>> Its value differs from any permitted value of this octet in IPv6 =
IIDs  (ref RFC 4291).
>>>>=20
>>>> It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.
>>>>=20
>>>> An unambiguous mark is fortunately possible because currently =
permitted IIDs have in their first octet either bit6 =3D 0 (the "u" =
bit"), or bit6 =3D 1 and bit7=3D 0 (the "g" bit).
>>>> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction is therefore deterministic.
>>>>=20
>>>> The proposed V is =3D 00000011.=20
>>>> (With other values of this octet, other IID formats can be defined =
in case some would be useful in the future.)
>>>>=20
>>>> Note that, if and when a consensus is reached in Softwire, an =
extension of RFC 4291 will have to be submitted to 6MAN.=20
>>>=20
>>> or rather IEEE?
>>=20
>> IMHO, IEEE has nothing to do with a marker that is purposely an =
escape mechanism from the modified EUI-64 format of RFC 4291.
>>=20
>>> I am not convinced that "V" is needed.
>>=20
>> The point is more, IMHO, whether you have an objection to it (and in =
this case which one).
>> Reason is that we are working for a consensus, and several are =
satisfied with the explanation that there are use cases where it is =
useful, and none where it is harmful.
>>=20
>>> you could even use the IANA OUI if pretty printing was required.
>>=20
>> The point is that it takes 32 bits which is too much to have IPv4 =
address + PSID in the IID.
>>=20
>>=20
>>>> (c)                                  =20
>>>> A Destination address from a CE to the outside IPv4 Internet is:
>>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>>> +--------------------------+----+---------------+------------+---+
>>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>>> +--------------------------+----+---------------+------------+---+
>>>=20
>>> this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
>>=20
>> Copying an available IPv4 address at a fixed place isn't IMHO a "big =
change".
>>=20
>>> if we also allow for a BR subnet prefix of /128 I'm OK with this (I =
think).
>>=20
>> I don't understand what you mean by "Subnet prefix of /128".
>>=20
>>=20
>>>> Note that if double-translation CEs are notified to use U instead =
of V, the last octet becomes 0 per RFC  6052.
>>>=20
>>> how would a CE know if it was single or double translating?
>>=20
>> Presumably with a usual method, e.g. DHCPv6.
>> Anything problematic with that?
>>=20
>>=20
>>> e.g we could do:
>>>=20
>>> <--------- 64 ------------><--- 24 ------><----- 32 -------><--8 >
>>> +-------------+--------+---+--------------------+------+-----+---+
>>> | IPv6 prefix |CE index| S | 00-00-5E    |  IPv4 address  | PSID |
>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>=20
>>> we also need to handle the case where IPv6 prefix + CE index > 64.
>>=20
>> Please explain more your understanding of this requirement.
>> (I personally believe we should avoid that.)
>>=20
>>> I suggest we then just put as much as the interface identifier that =
will fit.
>>=20
>>=20
>> May I suggest that, to be more constructive, you could first express =
your objections to the proposed unified mapping, rather than making a =
number of new proposals whose justifications are sometimes hard to =
understand,=20
>>=20
>> Cheers,
>> RD=20
>>=20
>>=20
>>>=20
>>> cheers,
>>> Ole
>>>=20
>>>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20
>=20


From satoru.matsushima@gmail.com  Tue Oct 11 02:48:07 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 937F821F8C15 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 02:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q1WyGIj5CZSF for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 02:48:06 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4FD21F8C0D for <softwires@ietf.org>; Tue, 11 Oct 2011 02:48:06 -0700 (PDT)
Received: by qyk32 with SMTP id 32so2660798qyk.10 for <softwires@ietf.org>; Tue, 11 Oct 2011 02:48:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=n3TpR36/yuCfLUxhKJsioQaUfjKT3rhmkfUU/zQFtxo=; b=We5Sl3y2797uzDatdQSozSW2TVR4NOSgAki0Of/0iFMn+K+Y2taribApvLH4KvT9pD 0Gfqu5R5pKM7hp4i8MO76aBsbCbNis1J0qdGhcLVUeAh/yuOauVRrS6eUcHP/vujegpm i/jIFNt5DumBMC4t1KQ2ww5kmn1Hod1OcyLMU=
Received: by 10.68.35.231 with SMTP id l7mr44275090pbj.41.1318326484578; Tue, 11 Oct 2011 02:48:04 -0700 (PDT)
Received: from [10.201.83.217] ([202.45.12.174]) by mx.google.com with ESMTPS id h5sm77480488pbf.4.2011.10.11.02.48.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Oct 2011 02:48:02 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <815B27C6-4C23-4634-A619-912FCC37FEAE@laposte.net>
Date: Tue, 11 Oct 2011 18:47:58 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <9988B501-6929-4C5C-9275-E3E7341823EB@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com> <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com> <815B27C6-4C23-4634-A619-912FCC37FEAE@laposte.net>
To: =?utf-8?Q?R=C3=A9mi_Despr=C3=A9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1244.3)
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 09:48:07 -0000

On 2011/10/11, at 17:42, R=E9mi Despr=E9s wrote:

>=20
> Le 11 oct. 2011 =E0 10:30, Satoru Matsushima a =E9crit :
>=20
>> Leaf, thanks for the summary.
>>=20
>> On 2011/10/10, at 20:34, Leaf yeh wrote:
>>=20
>>> Remi - >> a1- If the CE has an exclusive or shared IPv4 address:
>>>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 =
>
>>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>> Ole - > putting the IPv4 address / port information at the end of =
the interface identifier will allow for > /64 support. > what's the L?
>>> Remi - Don't see what you found unclear.
>>>=20
>>>=20
>>> Question: Supposed the question is on the last field, named 'L', in =
the new address format.
>>>=20
>>=20
>> Since Remi's draft doesn't specify 'CE IPv6 prefix length', IPv6 =
prefix can't be self delimiting to extract IPv4 address and port-set ID =
in the case of double translation. That's my understanding. Is that =
correct?
>=20
> In my understanding, yes.
>=20
> Now, putting the "CE IPv6 prefix length" back as a rule parameter =
shouldn't be a problem if the idea of linking IPv4 and IPv6 sizes of =
address spaces is abandoned (a choice that, I have to agree, simplifies =
the design).
>=20
> Cheers,
> RD=20

I think that it should be exclusive in a domain but it could be coexist =
in the map specification.

cheers,
--satoru


>> As '4rd-a', and 4via6(draft-murakami-softwire-4v6-translation), the =
'L' bits are not necessary because 'CE IPv6 prefix length' is defined =
through a domain, instead of 'L'.
>>=20
>>=20
>>>=20
>>> Remi - >> A Destination address from a CE to the outside IPv4 =
Internet is:
>>>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>>>> +--------------------------+----+---------------+------------+---+
>>>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>>>> +--------------------------+----+---------------+------------+---+
>>> Ole - this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
>>> Remi - Copying an available IPv4 address at a fixed place isn't IMHO =
a "big change".
>>>=20
>>>=20
>>> Concern: Supposed the replacement of the 1st 64bits of the BR =
address with a subnet prefix is not for the tunnel case if the field of =
IPv4 address can be variable, right?
>>=20
>> I think that it could be a case where the BR address with a subnet =
prefix for the tunnel case. My concern rather than the BR address is =
that a CE should pick packets up which have 'V' in IID, even destined =
prefixes are delegated to nodes which are behind of the CE.
>>=20
>>=20
>>>=20
>>> In fact, I doubts we could have the same address mapping for both =
tunnel and translation. Supposed the address of tunnel end-points is =
preferred to be fixed, but the address for the translation could be =
variable.
>>>=20
>>=20
>> I think we could have it.
>>=20
>> cheers,
>> --satoru
>>=20
>>=20
>>>=20
>>> Best Regards,
>>> Leaf
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] =
On Behalf Of R=E9mi Despr=E9s
>>> Sent: Thursday, October 06, 2011 6:07 PM
>>> To: Ole Troan
>>> Cc: Softwires-wg
>>> Subject: Re: [Softwires] Proposed Unified Address Mapping for =
encapsulation and double-translation
>>>=20
>>>=20
>>> Le 6 oct. 2011 =E0 18:47, Ole Troan a =E9crit :
>>>=20
>>>> Remi,
>>>>=20
>>>> [...]
>>>>=20
>>>>> 2.
>>>>> (a)
>>>>> The IPv6 Source address of an IPv4 packet from a CE is:
>>>>>=20
>>>>> a1- If the CE has an exclusive or shared IPv4 address:
>>>>>=20
>>>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 =
>
>>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>>=20
>>>> putting the IPv4 address / port information at the end of the =
interface identifier will allow for > /64 support.
>>>=20
>>> Could you explain more the requirement you have in mind? =20
>>>=20
>>>> what's the L?
>>>=20
>>> On the picture, L is 32 bits + Length(PSID).
>>> Don't see what you found unclear.=20
>>>=20
>>>>=20
>>>> you suggest that the first subnet of an allocation should be used =
for this purpose.
>>>=20
>>> Did I do this?
>>> Please explain because that's not, IMHO,  something to be done.
>>>=20
>>>> the first subnet is convenient to use for e.g. manual addressing =
(since it allows the :: short hand).
>>>> I do wonder if this has to be provisioned. e.g. some deployments =
may use the first subnet for the link between
>>>> CE and PE. (i.e. a /56 - 1 using the PD exclude option is used).
>>>=20
>>> See just above.
>>>=20
>>>>=20
>>>>> a2- If the CE has an IPv4 prefix:
>>>>>=20
>>>>> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
>>>>> +-------------+--------+---+---+-------------+---------------+---+
>>>>> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
>>>>> +-------------+--------+---+---+-------------+---------------+---+
>>>>>=20
>>>>> (b)
>>>>> V is the mark that characterizes IPv6 packets that are in reality =
IPv4 packets.
>>>>> Its value differs from any permitted value of this octet in IPv6 =
IIDs  (ref RFC 4291).
>>>>>=20
>>>>> It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.
>>>>>=20
>>>>> An unambiguous mark is fortunately possible because currently =
permitted IIDs have in their first octet either bit6 =3D 0 (the "u" =
bit"), or bit6 =3D 1 and bit7=3D 0 (the "g" bit).
>>>>> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D =
1, distinction is therefore deterministic.
>>>>>=20
>>>>> The proposed V is =3D 00000011.=20
>>>>> (With other values of this octet, other IID formats can be defined =
in case some would be useful in the future.)
>>>>>=20
>>>>> Note that, if and when a consensus is reached in Softwire, an =
extension of RFC 4291 will have to be submitted to 6MAN.=20
>>>>=20
>>>> or rather IEEE?
>>>=20
>>> IMHO, IEEE has nothing to do with a marker that is purposely an =
escape mechanism from the modified EUI-64 format of RFC 4291.
>>>=20
>>>> I am not convinced that "V" is needed.
>>>=20
>>> The point is more, IMHO, whether you have an objection to it (and in =
this case which one).
>>> Reason is that we are working for a consensus, and several are =
satisfied with the explanation that there are use cases where it is =
useful, and none where it is harmful.
>>>=20
>>>> you could even use the IANA OUI if pretty printing was required.
>>>=20
>>> The point is that it takes 32 bits which is too much to have IPv4 =
address + PSID in the IID.
>>>=20
>>>=20
>>>>> (c)                                  =20
>>>>> A Destination address from a CE to the outside IPv4 Internet is:
>>>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>>>> +--------------------------+----+---------------+------------+---+
>>>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>>>> +--------------------------+----+---------------+------------+---+
>>>>=20
>>>> this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
>>>=20
>>> Copying an available IPv4 address at a fixed place isn't IMHO a "big =
change".
>>>=20
>>>> if we also allow for a BR subnet prefix of /128 I'm OK with this (I =
think).
>>>=20
>>> I don't understand what you mean by "Subnet prefix of /128".
>>>=20
>>>=20
>>>>> Note that if double-translation CEs are notified to use U instead =
of V, the last octet becomes 0 per RFC  6052.
>>>>=20
>>>> how would a CE know if it was single or double translating?
>>>=20
>>> Presumably with a usual method, e.g. DHCPv6.
>>> Anything problematic with that?
>>>=20
>>>=20
>>>> e.g we could do:
>>>>=20
>>>> <--------- 64 ------------><--- 24 ------><----- 32 -------><--8 >
>>>> +-------------+--------+---+--------------------+------+-----+---+
>>>> | IPv6 prefix |CE index| S | 00-00-5E    |  IPv4 address  | PSID |
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>>=20
>>>> we also need to handle the case where IPv6 prefix + CE index > 64.
>>>=20
>>> Please explain more your understanding of this requirement.
>>> (I personally believe we should avoid that.)
>>>=20
>>>> I suggest we then just put as much as the interface identifier that =
will fit.
>>>=20
>>>=20
>>> May I suggest that, to be more constructive, you could first express =
your objections to the proposed unified mapping, rather than making a =
number of new proposals whose justifications are sometimes hard to =
understand,=20
>>>=20
>>> Cheers,
>>> RD=20
>>>=20
>>>=20
>>>>=20
>>>> cheers,
>>>> Ole
>>>>=20
>>>>=20
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>=20
>>=20
>=20


From leaf.y.yeh@huawei.com  Tue Oct 11 04:01:56 2011
Return-Path: <leaf.y.yeh@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 4E3A921F8C09 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 04:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.374
X-Spam-Level: 
X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fKm5+dHUWetM for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 04:01: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 C049F21F8C08 for <softwires@ietf.org>; Tue, 11 Oct 2011 04:01:54 -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 <0LSW00EJQELP4S@szxga04-in.huawei.com> for softwires@ietf.org; Tue, 11 Oct 2011 19:01:01 +0800 (CST)
Received: from szxrg02-dlp.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 <0LSW00IN7ELOY4@szxga04-in.huawei.com> for softwires@ietf.org; Tue, 11 Oct 2011 19:01:01 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEE20945; Tue, 11 Oct 2011 19:00:59 +0800
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 11 Oct 2011 19:00:56 +0800
Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.227]) by szxeml404-hub.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Tue, 11 Oct 2011 19:00:42 +0800
Date: Tue, 11 Oct 2011 11:00:41 +0000
From: Leaf yeh <leaf.y.yeh@huawei.com>
In-reply-to: <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com>
X-Originating-IP: [10.70.39.98]
To: Satoru Matsushima <satoru.matsushima@gmail.com>, =?utf-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
Message-id: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05766BB8@SZXEML510-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
Thread-index: AQHMh0ClppljXMMUk0246OCDrJF2JZV2S26AgACkO2A=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com> <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com>
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 11:01:56 -0000

PiBSZW1pIC0gPj4gQSBEZXN0aW5hdGlvbiBhZGRyZXNzIGZyb20gYSBDRSB0byB0aGUgb3V0c2lk
ZSBJUHY0IEludGVybmV0IGlzOg0KPj4+IDwtLS0tLS0tLS0gNjQgLS0tLS0tLS0tLS0tPjwgOCA+
PC0tLS0gICAzMiAtLS0tPjwtLS0gMTYgLS0tLT48OCA+DQo+Pj4gKy0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tKy0tLS0rLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLSstLS0rDQo+Pj4gfCAg
ICAgQlIgc3VibmV0IHByZWZpeCAgICAgfCBWICB8ICBJUHY0IGFkZHJlc3MgfCAgICAgIDAgICAg
IHwzMiB8DQo+Pj4gKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0rLS0tLS0tLS0tLS0t
LS0tKy0tLS0tLS0tLS0tLSstLS0rDQpMZWFmIC0+IEluIGZhY3QsIEkgZG91YnRzIHdlIGNvdWxk
IGhhdmUgdGhlIHNhbWUgYWRkcmVzcyBtYXBwaW5nIGZvciBib3RoIHR1bm5lbCBhbmQgdHJhbnNs
YXRpb24uIFN1cHBvc2VkIHRoZSBhZGRyZXNzIG9mIHR1bm5lbCBlbmQtcG9pbnRzIGlzIHByZWZl
cnJlZCB0byBiZSBmaXhlZCwgYnV0IHRoZSBhZGRyZXNzIGZvciB0aGUgdHJhbnNsYXRpb24gY291
bGQgYmUgdmFyaWFibGUuDQpTYXRvcnUgLT4gSSB0aGluayB3ZSBjb3VsZCBoYXZlIGl0Lg0KDQpX
aGF0IGlzIHRoZSBkZWZpbml0aW9uIG9mIHRoZSBJUHY0IGFkZHJlc3MgaW4gdGhlIGFib3ZlIGZv
cm1hdD8gSXMgaXQgdGhlIGRlc3RpbmF0aW9uIElQdjQgYWRkcmVzcyBvZiBhbnkgaG9zdHMgb3V0
c2lkZSA0cmQgSVB2NCBkb21haW4gaW4gdGhlIGludGVybmV0Pw0KDQoNCkJlc3QgUmVnYXJkcywN
CkxlYWYNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogU2F0b3J1IE1hdHN1
c2hpbWEgW21haWx0bzpzYXRvcnUubWF0c3VzaGltYUBnbWFpbC5jb21dIA0KU2VudDogVHVlc2Rh
eSwgT2N0b2JlciAxMSwgMjAxMSA0OjMwIFBNDQpUbzogTGVhZiB5ZWgNCkNjOiBTYXRvcnUgTWF0
c3VzaGltYTsgUsOpbWkgRGVzcHLDqXM7IE9sZSBUcm9hbjsgU29mdHdpcmVzLXdnOyBmaW5lX3N6
QGh1YXdlaS5jb20NClN1YmplY3Q6IFJlOiBbU29mdHdpcmVzXSBQcm9wb3NlZCBVbmlmaWVkIEFk
ZHJlc3MgTWFwcGluZyBmb3IgZW5jYXBzdWxhdGlvbiBhbmQgZG91YmxlLXRyYW5zbGF0aW9uDQoN
CkxlYWYsIHRoYW5rcyBmb3IgdGhlIHN1bW1hcnkuDQoNCk9uIDIwMTEvMTAvMTAsIGF0IDIwOjM0
LCBMZWFmIHllaCB3cm90ZToNCg0KPiBSZW1pIC0gPj4gYTEtIElmIHRoZSBDRSBoYXMgYW4gZXhj
bHVzaXZlIG9yIHNoYXJlZCBJUHY0IGFkZHJlc3M6DQo+Pj4gPC0tLS0tLS0tLSA2NCAtLS0tLS0t
LS0tLS0+PDggPjwtLS0tLS0gTCA+PSAzMiAtLS0tLS0tPjw0OC1MPjw4ID4NCj4+PiArLS0tLS0t
LS0tLS0tLSstLS0tLS0tLSstLS0rLS0tKy0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tKy0tLS0tKy0t
LSsNCj4+PiB8IElQdjYgcHJlZml4IHxDRSBpbmRleHwgMCB8IFYgfCAgSVB2NCBhZGRyZXNzICB8
IFBTSUQgfCAgMCAgfCBMIHwNCj4+PiArLS0tLS0tLS0tLS0tLSstLS0tLS0tLSstLS0rLS0tKy0t
LS0tLS0tLS0tLS0tLS0rLS0tLS0tKy0tLS0tKy0tLSsNCj4gT2xlIC0gPiBwdXR0aW5nIHRoZSBJ
UHY0IGFkZHJlc3MgLyBwb3J0IGluZm9ybWF0aW9uIGF0IHRoZSBlbmQgb2YgdGhlIGludGVyZmFj
ZSBpZGVudGlmaWVyIHdpbGwgYWxsb3cgZm9yID4gLzY0IHN1cHBvcnQuID4gd2hhdCdzIHRoZSBM
Pw0KPiBSZW1pIC0gRG9uJ3Qgc2VlIHdoYXQgeW91IGZvdW5kIHVuY2xlYXIuDQo+IA0KPiANCj4g
UXVlc3Rpb246IFN1cHBvc2VkIHRoZSBxdWVzdGlvbiBpcyBvbiB0aGUgbGFzdCBmaWVsZCwgbmFt
ZWQgJ0wnLCBpbiB0aGUgbmV3IGFkZHJlc3MgZm9ybWF0Lg0KPiANCg0KU2luY2UgUmVtaSdzIGRy
YWZ0IGRvZXNuJ3Qgc3BlY2lmeSAnQ0UgSVB2NiBwcmVmaXggbGVuZ3RoJywgSVB2NiBwcmVmaXgg
Y2FuJ3QgYmUgc2VsZiBkZWxpbWl0aW5nIHRvIGV4dHJhY3QgSVB2NCBhZGRyZXNzIGFuZCBwb3J0
LXNldCBJRCBpbiB0aGUgY2FzZSBvZiBkb3VibGUgdHJhbnNsYXRpb24uIFRoYXQncyBteSB1bmRl
cnN0YW5kaW5nLiBJcyB0aGF0IGNvcnJlY3Q/DQpBcyAnNHJkLWEnLCBhbmQgNHZpYTYoZHJhZnQt
bXVyYWthbWktc29mdHdpcmUtNHY2LXRyYW5zbGF0aW9uKSwgdGhlICdMJyBiaXRzIGFyZSBub3Qg
bmVjZXNzYXJ5IGJlY2F1c2UgJ0NFIElQdjYgcHJlZml4IGxlbmd0aCcgaXMgZGVmaW5lZCB0aHJv
dWdoIGEgZG9tYWluLCBpbnN0ZWFkIG9mICdMJy4NCg0KDQo+IA0KPiBSZW1pIC0gPj4gQSBEZXN0
aW5hdGlvbiBhZGRyZXNzIGZyb20gYSBDRSB0byB0aGUgb3V0c2lkZSBJUHY0IEludGVybmV0IGlz
Og0KPj4+IDwtLS0tLS0tLS0gNjQgLS0tLS0tLS0tLS0tPjwgOCA+PC0tLS0gICAzMiAtLS0tPjwt
LS0gMTYgLS0tLT48OCA+DQo+Pj4gKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0rLS0t
LS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLSstLS0rDQo+Pj4gfCAgICAgQlIgc3VibmV0IHByZWZp
eCAgICAgfCBWICB8ICBJUHY0IGFkZHJlc3MgfCAgICAgIDAgICAgIHwzMiB8DQo+Pj4gKy0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0rLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLSst
LS0rDQo+IE9sZSAtIHRoaXMgaXMgYSBiaWcgY2hhbmdlIGZvciBlbmNhcHN1bGF0aW9uLCB3aGVy
ZSBwcmlvciB0byB0aGlzIGVuY2Fwc3VsYXRpb24gbWVhbnMgc2VuZGluZyB0byBhIHNpbmdsZSBk
ZXN0aW5hdGlvbi4NCj4gUmVtaSAtIENvcHlpbmcgYW4gYXZhaWxhYmxlIElQdjQgYWRkcmVzcyBh
dCBhIGZpeGVkIHBsYWNlIGlzbid0IElNSE8gYSAiYmlnIGNoYW5nZSIuDQo+IA0KPiANCj4gQ29u
Y2VybjogU3VwcG9zZWQgdGhlIHJlcGxhY2VtZW50IG9mIHRoZSAxc3QgNjRiaXRzIG9mIHRoZSBC
UiBhZGRyZXNzIHdpdGggYSBzdWJuZXQgcHJlZml4IGlzIG5vdCBmb3IgdGhlIHR1bm5lbCBjYXNl
IGlmIHRoZSBmaWVsZCBvZiBJUHY0IGFkZHJlc3MgY2FuIGJlIHZhcmlhYmxlLCByaWdodD8NCg0K
SSB0aGluayB0aGF0IGl0IGNvdWxkIGJlIGEgY2FzZSB3aGVyZSB0aGUgQlIgYWRkcmVzcyB3aXRo
IGEgc3VibmV0IHByZWZpeCBmb3IgdGhlIHR1bm5lbCBjYXNlLiBNeSBjb25jZXJuIHJhdGhlciB0
aGFuIHRoZSBCUiBhZGRyZXNzIGlzIHRoYXQgYSBDRSBzaG91bGQgcGljayBwYWNrZXRzIHVwIHdo
aWNoIGhhdmUgJ1YnIGluIElJRCwgZXZlbiBkZXN0aW5lZCBwcmVmaXhlcyBhcmUgZGVsZWdhdGVk
IHRvIG5vZGVzIHdoaWNoIGFyZSBiZWhpbmQgb2YgdGhlIENFLg0KDQoNCj4gDQo+IEluIGZhY3Qs
IEkgZG91YnRzIHdlIGNvdWxkIGhhdmUgdGhlIHNhbWUgYWRkcmVzcyBtYXBwaW5nIGZvciBib3Ro
IHR1bm5lbCBhbmQgdHJhbnNsYXRpb24uIFN1cHBvc2VkIHRoZSBhZGRyZXNzIG9mIHR1bm5lbCBl
bmQtcG9pbnRzIGlzIHByZWZlcnJlZCB0byBiZSBmaXhlZCwgYnV0IHRoZSBhZGRyZXNzIGZvciB0
aGUgdHJhbnNsYXRpb24gY291bGQgYmUgdmFyaWFibGUuDQo+IA0KDQpJIHRoaW5rIHdlIGNvdWxk
IGhhdmUgaXQuDQoNCmNoZWVycywNCi0tc2F0b3J1DQoNCg0KPiANCj4gQmVzdCBSZWdhcmRzLA0K
PiBMZWFmDQo+IA0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogc29m
dHdpcmVzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpzb2Z0d2lyZXMtYm91bmNlc0BpZXRmLm9y
Z10gT24gQmVoYWxmIE9mIFLDqW1pIERlc3Byw6lzDQo+IFNlbnQ6IFRodXJzZGF5LCBPY3RvYmVy
IDA2LCAyMDExIDY6MDcgUE0NCj4gVG86IE9sZSBUcm9hbg0KPiBDYzogU29mdHdpcmVzLXdnDQo+
IFN1YmplY3Q6IFJlOiBbU29mdHdpcmVzXSBQcm9wb3NlZCBVbmlmaWVkIEFkZHJlc3MgTWFwcGlu
ZyBmb3IgZW5jYXBzdWxhdGlvbiBhbmQgZG91YmxlLXRyYW5zbGF0aW9uDQo+IA0KPiANCj4gTGUg
NiBvY3QuIDIwMTEgw6AgMTg6NDcsIE9sZSBUcm9hbiBhIMOpY3JpdCA6DQo+IA0KPj4gUmVtaSwN
Cj4+IA0KPj4gWy4uLl0NCj4+IA0KPj4+IDIuDQo+Pj4gKGEpDQo+Pj4gVGhlIElQdjYgU291cmNl
IGFkZHJlc3Mgb2YgYW4gSVB2NCBwYWNrZXQgZnJvbSBhIENFIGlzOg0KPj4+IA0KPj4+IGExLSBJ
ZiB0aGUgQ0UgaGFzIGFuIGV4Y2x1c2l2ZSBvciBzaGFyZWQgSVB2NCBhZGRyZXNzOg0KPj4+IA0K
Pj4+IDwtLS0tLS0tLS0gNjQgLS0tLS0tLS0tLS0tPjw4ID48LS0tLS0tIEwgPj0gMzIgLS0tLS0t
LT48NDgtTD48OCA+DQo+Pj4gKy0tLS0tLS0tLS0tLS0rLS0tLS0tLS0rLS0tKy0tLSstLS0tLS0t
LS0tLS0tLS0tKy0tLS0tLSstLS0tLSstLS0rDQo+Pj4gfCBJUHY2IHByZWZpeCB8Q0UgaW5kZXh8
IDAgfCBWIHwgIElQdjQgYWRkcmVzcyAgfCBQU0lEIHwgIDAgIHwgTCB8DQo+Pj4gKy0tLS0tLS0t
LS0tLS0rLS0tLS0tLS0rLS0tKy0tLSstLS0tLS0tLS0tLS0tLS0tKy0tLS0tLSstLS0tLSstLS0r
DQo+PiANCj4+IHB1dHRpbmcgdGhlIElQdjQgYWRkcmVzcyAvIHBvcnQgaW5mb3JtYXRpb24gYXQg
dGhlIGVuZCBvZiB0aGUgaW50ZXJmYWNlIGlkZW50aWZpZXIgd2lsbCBhbGxvdyBmb3IgPiAvNjQg
c3VwcG9ydC4NCj4gDQo+IENvdWxkIHlvdSBleHBsYWluIG1vcmUgdGhlIHJlcXVpcmVtZW50IHlv
dSBoYXZlIGluIG1pbmQ/ICANCj4gDQo+PiB3aGF0J3MgdGhlIEw/DQo+IA0KPiBPbiB0aGUgcGlj
dHVyZSwgTCBpcyAzMiBiaXRzICsgTGVuZ3RoKFBTSUQpLg0KPiBEb24ndCBzZWUgd2hhdCB5b3Ug
Zm91bmQgdW5jbGVhci4gDQo+IA0KPj4gDQo+PiB5b3Ugc3VnZ2VzdCB0aGF0IHRoZSBmaXJzdCBz
dWJuZXQgb2YgYW4gYWxsb2NhdGlvbiBzaG91bGQgYmUgdXNlZCBmb3IgdGhpcyBwdXJwb3NlLg0K
PiANCj4gRGlkIEkgZG8gdGhpcz8NCj4gUGxlYXNlIGV4cGxhaW4gYmVjYXVzZSB0aGF0J3Mgbm90
LCBJTUhPLCAgc29tZXRoaW5nIHRvIGJlIGRvbmUuDQo+IA0KPj4gdGhlIGZpcnN0IHN1Ym5ldCBp
cyBjb252ZW5pZW50IHRvIHVzZSBmb3IgZS5nLiBtYW51YWwgYWRkcmVzc2luZyAoc2luY2UgaXQg
YWxsb3dzIHRoZSA6OiBzaG9ydCBoYW5kKS4NCj4+IEkgZG8gd29uZGVyIGlmIHRoaXMgaGFzIHRv
IGJlIHByb3Zpc2lvbmVkLiBlLmcuIHNvbWUgZGVwbG95bWVudHMgbWF5IHVzZSB0aGUgZmlyc3Qg
c3VibmV0IGZvciB0aGUgbGluayBiZXR3ZWVuDQo+PiBDRSBhbmQgUEUuIChpLmUuIGEgLzU2IC0g
MSB1c2luZyB0aGUgUEQgZXhjbHVkZSBvcHRpb24gaXMgdXNlZCkuDQo+IA0KPiBTZWUganVzdCBh
Ym92ZS4NCj4gDQo+PiANCj4+PiBhMi0gSWYgdGhlIENFIGhhcyBhbiBJUHY0IHByZWZpeDoNCj4+
PiANCj4+PiA8LS0tLS0tLS0tIDY0IC0tLS0tLS0tLS0tLT48OCA+PC0tIEwgPCAzMiAtLT48LS0t
IDQ4LUwgLS0tLS0+PDggPg0KPj4+ICstLS0tLS0tLS0tLS0tKy0tLS0tLS0tKy0tLSstLS0rLS0t
LS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0rLS0tKw0KPj4+IHwgSVB2NiBwcmVmaXggfENFIGlu
ZGV4fCAwIHwgViB8IElQdjQgcHJlZml4IHwgICAgICAgICAwICAgICB8IEwgfA0KPj4+ICstLS0t
LS0tLS0tLS0tKy0tLS0tLS0tKy0tLSstLS0rLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0r
LS0tKw0KPj4+IA0KPj4+IChiKQ0KPj4+IFYgaXMgdGhlIG1hcmsgdGhhdCBjaGFyYWN0ZXJpemVz
IElQdjYgcGFja2V0cyB0aGF0IGFyZSBpbiByZWFsaXR5IElQdjQgcGFja2V0cy4NCj4+PiBJdHMg
dmFsdWUgZGlmZmVycyBmcm9tIGFueSBwZXJtaXR0ZWQgdmFsdWUgb2YgdGhpcyBvY3RldCBpbiBJ
UHY2IElJRHMgIChyZWYgUkZDIDQyOTEpLg0KPj4+IA0KPj4+IEl0IGlzIHVuZGVyc3Rvb2QgdGhh
dCwgaWYgZG91YmxlIFRyYW5zbGF0aW9uIGNvZXhpc3RzIHdpdGggc2luZ2xlIHRyYW5zbGF0aW9u
LCBjb25jZXJuZWQgSVNQcyBtYXkgbm90aWZ5IHRoZWlyIENFcyB0byB1c2UgdGhlIFUgb2N0ZXQg
b2YgUkZDIDYwNTIgaW5zdGVhZCBvZiBWLg0KPj4+IA0KPj4+IEFuIHVuYW1iaWd1b3VzIG1hcmsg
aXMgZm9ydHVuYXRlbHkgcG9zc2libGUgYmVjYXVzZSBjdXJyZW50bHkgcGVybWl0dGVkIElJRHMg
aGF2ZSBpbiB0aGVpciBmaXJzdCBvY3RldCBlaXRoZXIgYml0NiA9IDAgKHRoZSAidSIgYml0Iiks
IG9yIGJpdDYgPSAxIGFuZCBiaXQ3PSAwICh0aGUgImciIGJpdCkuDQo+Pj4gV2l0aCBWIGhhdmlu
ZyAidSIgPSAxIChzaWduaWZ5aW5nIFVuaXZlcnNhbCBzY29wZSkgQU5EICJnIiA9IDEsIGRpc3Rp
bmN0aW9uIGlzIHRoZXJlZm9yZSBkZXRlcm1pbmlzdGljLg0KPj4+IA0KPj4+IFRoZSBwcm9wb3Nl
ZCBWIGlzID0gMDAwMDAwMTEuIA0KPj4+IChXaXRoIG90aGVyIHZhbHVlcyBvZiB0aGlzIG9jdGV0
LCBvdGhlciBJSUQgZm9ybWF0cyBjYW4gYmUgZGVmaW5lZCBpbiBjYXNlIHNvbWUgd291bGQgYmUg
dXNlZnVsIGluIHRoZSBmdXR1cmUuKQ0KPj4+IA0KPj4+IE5vdGUgdGhhdCwgaWYgYW5kIHdoZW4g
YSBjb25zZW5zdXMgaXMgcmVhY2hlZCBpbiBTb2Z0d2lyZSwgYW4gZXh0ZW5zaW9uIG9mIFJGQyA0
MjkxIHdpbGwgaGF2ZSB0byBiZSBzdWJtaXR0ZWQgdG8gNk1BTi4gDQo+PiANCj4+IG9yIHJhdGhl
ciBJRUVFPw0KPiANCj4gSU1ITywgSUVFRSBoYXMgbm90aGluZyB0byBkbyB3aXRoIGEgbWFya2Vy
IHRoYXQgaXMgcHVycG9zZWx5IGFuIGVzY2FwZSBtZWNoYW5pc20gZnJvbSB0aGUgbW9kaWZpZWQg
RVVJLTY0IGZvcm1hdCBvZiBSRkMgNDI5MS4NCj4gDQo+PiBJIGFtIG5vdCBjb252aW5jZWQgdGhh
dCAiViIgaXMgbmVlZGVkLg0KPiANCj4gVGhlIHBvaW50IGlzIG1vcmUsIElNSE8sIHdoZXRoZXIg
eW91IGhhdmUgYW4gb2JqZWN0aW9uIHRvIGl0IChhbmQgaW4gdGhpcyBjYXNlIHdoaWNoIG9uZSku
DQo+IFJlYXNvbiBpcyB0aGF0IHdlIGFyZSB3b3JraW5nIGZvciBhIGNvbnNlbnN1cywgYW5kIHNl
dmVyYWwgYXJlIHNhdGlzZmllZCB3aXRoIHRoZSBleHBsYW5hdGlvbiB0aGF0IHRoZXJlIGFyZSB1
c2UgY2FzZXMgd2hlcmUgaXQgaXMgdXNlZnVsLCBhbmQgbm9uZSB3aGVyZSBpdCBpcyBoYXJtZnVs
Lg0KPiANCj4+IHlvdSBjb3VsZCBldmVuIHVzZSB0aGUgSUFOQSBPVUkgaWYgcHJldHR5IHByaW50
aW5nIHdhcyByZXF1aXJlZC4NCj4gDQo+IFRoZSBwb2ludCBpcyB0aGF0IGl0IHRha2VzIDMyIGJp
dHMgd2hpY2ggaXMgdG9vIG11Y2ggdG8gaGF2ZSBJUHY0IGFkZHJlc3MgKyBQU0lEIGluIHRoZSBJ
SUQuDQo+IA0KPiANCj4+PiAoYykgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0K
Pj4+IEEgRGVzdGluYXRpb24gYWRkcmVzcyBmcm9tIGEgQ0UgdG8gdGhlIG91dHNpZGUgSVB2NCBJ
bnRlcm5ldCBpczoNCj4+PiA8LS0tLS0tLS0tIDY0IC0tLS0tLS0tLS0tLT48IDggPjwtLS0tICAg
MzIgLS0tLT48LS0tIDE2IC0tLS0+PDggPg0KPj4+ICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LSstLS0tKy0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0rLS0tKw0KPj4+IHwgICAgIEJSIHN1
Ym5ldCBwcmVmaXggICAgIHwgViAgfCAgSVB2NCBhZGRyZXNzIHwgICAgICAwICAgICB8MzIgfA0K
Pj4+ICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tKy0tLS0tLS0tLS0tLS0tLSstLS0t
LS0tLS0tLS0rLS0tKw0KPj4gDQo+PiB0aGlzIGlzIGEgYmlnIGNoYW5nZSBmb3IgZW5jYXBzdWxh
dGlvbiwgd2hlcmUgcHJpb3IgdG8gdGhpcyBlbmNhcHN1bGF0aW9uIG1lYW5zIHNlbmRpbmcgdG8g
YSBzaW5nbGUgZGVzdGluYXRpb24uDQo+IA0KPiBDb3B5aW5nIGFuIGF2YWlsYWJsZSBJUHY0IGFk
ZHJlc3MgYXQgYSBmaXhlZCBwbGFjZSBpc24ndCBJTUhPIGEgImJpZyBjaGFuZ2UiLg0KPiANCj4+
IGlmIHdlIGFsc28gYWxsb3cgZm9yIGEgQlIgc3VibmV0IHByZWZpeCBvZiAvMTI4IEknbSBPSyB3
aXRoIHRoaXMgKEkgdGhpbmspLg0KPiANCj4gSSBkb24ndCB1bmRlcnN0YW5kIHdoYXQgeW91IG1l
YW4gYnkgIlN1Ym5ldCBwcmVmaXggb2YgLzEyOCIuDQo+IA0KPiANCj4+PiBOb3RlIHRoYXQgaWYg
ZG91YmxlLXRyYW5zbGF0aW9uIENFcyBhcmUgbm90aWZpZWQgdG8gdXNlIFUgaW5zdGVhZCBvZiBW
LCB0aGUgbGFzdCBvY3RldCBiZWNvbWVzIDAgcGVyIFJGQyAgNjA1Mi4NCj4+IA0KPj4gaG93IHdv
dWxkIGEgQ0Uga25vdyBpZiBpdCB3YXMgc2luZ2xlIG9yIGRvdWJsZSB0cmFuc2xhdGluZz8NCj4g
DQo+IFByZXN1bWFibHkgd2l0aCBhIHVzdWFsIG1ldGhvZCwgZS5nLiBESENQdjYuDQo+IEFueXRo
aW5nIHByb2JsZW1hdGljIHdpdGggdGhhdD8NCj4gDQo+IA0KPj4gZS5nIHdlIGNvdWxkIGRvOg0K
Pj4gDQo+PiA8LS0tLS0tLS0tIDY0IC0tLS0tLS0tLS0tLT48LS0tIDI0IC0tLS0tLT48LS0tLS0g
MzIgLS0tLS0tLT48LS04ID4NCj4+ICstLS0tLS0tLS0tLS0tKy0tLS0tLS0tKy0tLSstLS0tLS0t
LS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0rLS0tKw0KPj4gfCBJUHY2IHByZWZpeCB8Q0UgaW5k
ZXh8IFMgfCAwMC0wMC01RSAgICB8ICBJUHY0IGFkZHJlc3MgIHwgUFNJRCB8DQo+PiArLS0tLS0t
LS0tLS0tLSstLS0tLS0tLSstLS0rLS0tKy0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tKy0tLS0tKy0t
LSsNCj4+IA0KPj4gd2UgYWxzbyBuZWVkIHRvIGhhbmRsZSB0aGUgY2FzZSB3aGVyZSBJUHY2IHBy
ZWZpeCArIENFIGluZGV4ID4gNjQuDQo+IA0KPiBQbGVhc2UgZXhwbGFpbiBtb3JlIHlvdXIgdW5k
ZXJzdGFuZGluZyBvZiB0aGlzIHJlcXVpcmVtZW50Lg0KPiAoSSBwZXJzb25hbGx5IGJlbGlldmUg
d2Ugc2hvdWxkIGF2b2lkIHRoYXQuKQ0KPiANCj4+IEkgc3VnZ2VzdCB3ZSB0aGVuIGp1c3QgcHV0
IGFzIG11Y2ggYXMgdGhlIGludGVyZmFjZSBpZGVudGlmaWVyIHRoYXQgd2lsbCBmaXQuDQo+IA0K
PiANCj4gTWF5IEkgc3VnZ2VzdCB0aGF0LCB0byBiZSBtb3JlIGNvbnN0cnVjdGl2ZSwgeW91IGNv
dWxkIGZpcnN0IGV4cHJlc3MgeW91ciBvYmplY3Rpb25zIHRvIHRoZSBwcm9wb3NlZCB1bmlmaWVk
IG1hcHBpbmcsIHJhdGhlciB0aGFuIG1ha2luZyBhIG51bWJlciBvZiBuZXcgcHJvcG9zYWxzIHdo
b3NlIGp1c3RpZmljYXRpb25zIGFyZSBzb21ldGltZXMgaGFyZCB0byB1bmRlcnN0YW5kLCANCj4g
DQo+IENoZWVycywNCj4gUkQgDQo+IA0KPiANCj4+IA0KPj4gY2hlZXJzLA0KPj4gT2xlDQo+PiAN
Cj4+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
PiBTb2Z0d2lyZXMgbWFpbGluZyBsaXN0DQo+IFNvZnR3aXJlc0BpZXRmLm9yZw0KPiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NvZnR3aXJlcw0KPiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBTb2Z0d2lyZXMgbWFpbGluZyBs
aXN0DQo+IFNvZnR3aXJlc0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3NvZnR3aXJlcw0KDQo=

From satoru.matsushima@gmail.com  Tue Oct 11 04:25:36 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 49F9321F8AD3 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 04:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPfST7o0TAFt for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 04:25:35 -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 1899421F8466 for <softwires@ietf.org>; Tue, 11 Oct 2011 04:25:35 -0700 (PDT)
Received: by vcbfo11 with SMTP id fo11so6696919vcb.31 for <softwires@ietf.org>; Tue, 11 Oct 2011 04:25:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=Fq1zWQuZchiBKpx2Y5nJkQSBHY7LC5FmLrgQ4l12KuA=; b=Z/oiq/XxrZpXdQafr6zG+U4wlgKM+RjW6uFesAzbjKmBMTqAjCCWue2kJrVeewdVZ0 kCWCnHw+iRRcdFpNwonVSBcpkeC3aeAbLroFU+pZxLRmYeY9T9cuKElDDMiXuu2eXwY/ MO1RNKm72mH6z7XtcH7Zie181RymAderHkyDI=
Received: by 10.68.122.169 with SMTP id lt9mr44699259pbb.114.1318332333528; Tue, 11 Oct 2011 04:25:33 -0700 (PDT)
Received: from [10.201.83.217] ([202.45.12.174]) by mx.google.com with ESMTPS id w4sm15656739pbf.6.2011.10.11.04.25.29 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Oct 2011 04:25:31 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=utf-8
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05766BB8@SZXEML510-MBS.china.huawei.com>
Date: Tue, 11 Oct 2011 20:25:27 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <77E5DB2B-70A2-4797-AE89-5D6A5D8E514F@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com> <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05766BB8@SZXEML510-MBS.china.huawei.com>
To: Leaf yeh <leaf.y.yeh@huawei.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 11:25:36 -0000

On 2011/10/11, at 20:00, Leaf yeh wrote:

>> Remi - >> A Destination address from a CE to the outside IPv4 =
Internet is:
>>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>>> +--------------------------+----+---------------+------------+---+
>>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>>> +--------------------------+----+---------------+------------+---+
> Leaf -> In fact, I doubts we could have the same address mapping for =
both tunnel and translation. Supposed the address of tunnel end-points =
is preferred to be fixed, but the address for the translation could be =
variable.
> Satoru -> I think we could have it.
>=20
> What is the definition of the IPv4 address in the above format? Is it =
the destination IPv4 address of any hosts outside 4rd IPv4 domain in the =
internet?

I believe that the embedded IPv4 address should be an IPv4 address of a =
host on outside the domain.

cheers,
--satoru

>=20
>=20
> Best Regards,
> Leaf
>=20
>=20
> -----Original Message-----
> From: Satoru Matsushima [mailto:satoru.matsushima@gmail.com]=20
> Sent: Tuesday, October 11, 2011 4:30 PM
> To: Leaf yeh
> Cc: Satoru Matsushima; R=C3=A9mi Despr=C3=A9s; Ole Troan; =
Softwires-wg; fine_sz@huawei.com
> Subject: Re: [Softwires] Proposed Unified Address Mapping for =
encapsulation and double-translation
>=20
> Leaf, thanks for the summary.
>=20
> On 2011/10/10, at 20:34, Leaf yeh wrote:
>=20
>> Remi - >> a1- If the CE has an exclusive or shared IPv4 address:
>>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>> Ole - > putting the IPv4 address / port information at the end of the =
interface identifier will allow for > /64 support. > what's the L?
>> Remi - Don't see what you found unclear.
>>=20
>>=20
>> Question: Supposed the question is on the last field, named 'L', in =
the new address format.
>>=20
>=20
> Since Remi's draft doesn't specify 'CE IPv6 prefix length', IPv6 =
prefix can't be self delimiting to extract IPv4 address and port-set ID =
in the case of double translation. That's my understanding. Is that =
correct?
> As '4rd-a', and 4via6(draft-murakami-softwire-4v6-translation), the =
'L' bits are not necessary because 'CE IPv6 prefix length' is defined =
through a domain, instead of 'L'.
>=20
>=20
>>=20
>> Remi - >> A Destination address from a CE to the outside IPv4 =
Internet is:
>>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>>> +--------------------------+----+---------------+------------+---+
>>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>>> +--------------------------+----+---------------+------------+---+
>> Ole - this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
>> Remi - Copying an available IPv4 address at a fixed place isn't IMHO =
a "big change".
>>=20
>>=20
>> Concern: Supposed the replacement of the 1st 64bits of the BR address =
with a subnet prefix is not for the tunnel case if the field of IPv4 =
address can be variable, right?
>=20
> I think that it could be a case where the BR address with a subnet =
prefix for the tunnel case. My concern rather than the BR address is =
that a CE should pick packets up which have 'V' in IID, even destined =
prefixes are delegated to nodes which are behind of the CE.
>=20
>=20
>>=20
>> In fact, I doubts we could have the same address mapping for both =
tunnel and translation. Supposed the address of tunnel end-points is =
preferred to be fixed, but the address for the translation could be =
variable.
>>=20
>=20
> I think we could have it.
>=20
> cheers,
> --satoru
>=20
>=20
>>=20
>> Best Regards,
>> Leaf
>>=20
>>=20
>> -----Original Message-----
>> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] =
On Behalf Of R=C3=A9mi Despr=C3=A9s
>> Sent: Thursday, October 06, 2011 6:07 PM
>> To: Ole Troan
>> Cc: Softwires-wg
>> Subject: Re: [Softwires] Proposed Unified Address Mapping for =
encapsulation and double-translation
>>=20
>>=20
>> Le 6 oct. 2011 =C3=A0 18:47, Ole Troan a =C3=A9crit :
>>=20
>>> Remi,
>>>=20
>>> [...]
>>>=20
>>>> 2.
>>>> (a)
>>>> The IPv6 Source address of an IPv4 packet from a CE is:
>>>>=20
>>>> a1- If the CE has an exclusive or shared IPv4 address:
>>>>=20
>>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
>>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>=20
>>> putting the IPv4 address / port information at the end of the =
interface identifier will allow for > /64 support.
>>=20
>> Could you explain more the requirement you have in mind? =20
>>=20
>>> what's the L?
>>=20
>> On the picture, L is 32 bits + Length(PSID).
>> Don't see what you found unclear.=20
>>=20
>>>=20
>>> you suggest that the first subnet of an allocation should be used =
for this purpose.
>>=20
>> Did I do this?
>> Please explain because that's not, IMHO,  something to be done.
>>=20
>>> the first subnet is convenient to use for e.g. manual addressing =
(since it allows the :: short hand).
>>> I do wonder if this has to be provisioned. e.g. some deployments may =
use the first subnet for the link between
>>> CE and PE. (i.e. a /56 - 1 using the PD exclude option is used).
>>=20
>> See just above.
>>=20
>>>=20
>>>> a2- If the CE has an IPv4 prefix:
>>>>=20
>>>> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
>>>> +-------------+--------+---+---+-------------+---------------+---+
>>>> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
>>>> +-------------+--------+---+---+-------------+---------------+---+
>>>>=20
>>>> (b)
>>>> V is the mark that characterizes IPv6 packets that are in reality =
IPv4 packets.
>>>> Its value differs from any permitted value of this octet in IPv6 =
IIDs  (ref RFC 4291).
>>>>=20
>>>> It is understood that, if double Translation coexists with single =
translation, concerned ISPs may notify their CEs to use the U octet of =
RFC 6052 instead of V.
>>>>=20
>>>> An unambiguous mark is fortunately possible because currently =
permitted IIDs have in their first octet either bit6 =3D 0 (the "u" =
bit"), or bit6 =3D 1 and bit7=3D 0 (the "g" bit).
>>>> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1, =
distinction is therefore deterministic.
>>>>=20
>>>> The proposed V is =3D 00000011.=20
>>>> (With other values of this octet, other IID formats can be defined =
in case some would be useful in the future.)
>>>>=20
>>>> Note that, if and when a consensus is reached in Softwire, an =
extension of RFC 4291 will have to be submitted to 6MAN.=20
>>>=20
>>> or rather IEEE?
>>=20
>> IMHO, IEEE has nothing to do with a marker that is purposely an =
escape mechanism from the modified EUI-64 format of RFC 4291.
>>=20
>>> I am not convinced that "V" is needed.
>>=20
>> The point is more, IMHO, whether you have an objection to it (and in =
this case which one).
>> Reason is that we are working for a consensus, and several are =
satisfied with the explanation that there are use cases where it is =
useful, and none where it is harmful.
>>=20
>>> you could even use the IANA OUI if pretty printing was required.
>>=20
>> The point is that it takes 32 bits which is too much to have IPv4 =
address + PSID in the IID.
>>=20
>>=20
>>>> (c)                                  =20
>>>> A Destination address from a CE to the outside IPv4 Internet is:
>>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
>>>> +--------------------------+----+---------------+------------+---+
>>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
>>>> +--------------------------+----+---------------+------------+---+
>>>=20
>>> this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.
>>=20
>> Copying an available IPv4 address at a fixed place isn't IMHO a "big =
change".
>>=20
>>> if we also allow for a BR subnet prefix of /128 I'm OK with this (I =
think).
>>=20
>> I don't understand what you mean by "Subnet prefix of /128".
>>=20
>>=20
>>>> Note that if double-translation CEs are notified to use U instead =
of V, the last octet becomes 0 per RFC  6052.
>>>=20
>>> how would a CE know if it was single or double translating?
>>=20
>> Presumably with a usual method, e.g. DHCPv6.
>> Anything problematic with that?
>>=20
>>=20
>>> e.g we could do:
>>>=20
>>> <--------- 64 ------------><--- 24 ------><----- 32 -------><--8 >
>>> +-------------+--------+---+--------------------+------+-----+---+
>>> | IPv6 prefix |CE index| S | 00-00-5E    |  IPv4 address  | PSID |
>>> +-------------+--------+---+---+----------------+------+-----+---+
>>>=20
>>> we also need to handle the case where IPv6 prefix + CE index > 64.
>>=20
>> Please explain more your understanding of this requirement.
>> (I personally believe we should avoid that.)
>>=20
>>> I suggest we then just put as much as the interface identifier that =
will fit.
>>=20
>>=20
>> May I suggest that, to be more constructive, you could first express =
your objections to the proposed unified mapping, rather than making a =
number of new proposals whose justifications are sometimes hard to =
understand,=20
>>=20
>> Cheers,
>> RD=20
>>=20
>>=20
>>>=20
>>> cheers,
>>> Ole
>>>=20
>>>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20


From dr@cluenet.de  Tue Oct 11 05:37:32 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 D023221F8CFE for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 05:37:32 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LxH4xgwbOgKP for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 05:37:32 -0700 (PDT)
Received: from mail1.cluenet.de (mail1.cluenet.de [IPv6:2001:1440:201:101::5]) by ietfa.amsl.com (Postfix) with ESMTP id 0883621F8C74 for <softwires@ietf.org>; Tue, 11 Oct 2011 05:37:31 -0700 (PDT)
Received: by mail1.cluenet.de (Postfix, from userid 500) id 366081080DE; Tue, 11 Oct 2011 14:37:27 +0200 (CEST)
Date: Tue, 11 Oct 2011 14:37:27 +0200
From: Daniel Roesen <dr@cluenet.de>
To: softwires@ietf.org
Message-ID: <20111011123727.GA4461@srv03.cluenet.de>
Mail-Followup-To: softwires@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
Subject: [Softwires] DS-Lite fragmentation RFC2473 reference
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, 11 Oct 2011 12:37:32 -0000

Hi,

the DS-Lite spec states:

5.3.  Fragmentation and Reassembly
...
   [...] The inner IPv4 packet MUST NOT be
   fragmented.  Fragmentation MUST happen after the encapsulation of the
   IPv6 packet.  Reassembly MUST happen before the decapsulation of the
   IPv4 packet.  A detailed procedure has been specified in [RFC2473]
   Section 7.2.


The change from "fragment the IPv4 payload" to "fragment the IPv6 tunnel
packet" came between draft-ietf-softwire-dual-stack-lite-00 and -01:

http://tools.ietf.org/rfcdiff?url2=draft-ietf-softwire-dual-stack-lite-01.txt

The probable trigger was:

http://www.ietf.org/mail-archive/web/softwires/current/msg00756.html

No reasoning has been provided on the list, nor was the change in -01
commented.

I'm wondering what the reasoning was to mandate tunnel packet
fragmentation instead of payload. Could anyone give some insights?

Theoretically there should be no adverse impact by AFTR fragmenting the
NATted IPv4 payload packets for transmission into the tunnel to the B4.
Reassembly would be offloaded from the B4 to the endpoint behind the B4.

I've investigated a bit and found reports of SIP implementations having
serious problems with fragmented UDP, as well as Microsoft AD/Kerberos:

http://blog.tmcnet.com/third-screen/2009/03/udp_fragmentation_breaks_sip_in_todays_ip-pbxs.html
http://blogs.technet.com/b/asiasupp/archive/2006/09/19/457413.aspx

Any insight appreciated!

Best regards,
Daniel

PS: yes, fragmenting the tunnel packets is of course the most
transparent way end-to-end, but it comes at a price...

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

From satoru.matsushima@gmail.com  Tue Oct 11 06:40:04 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 12D8B21F8C4F for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 06:40:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xQdDwE-rjcI for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 06:40:03 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0D7D021F8C1A for <softwires@ietf.org>; Tue, 11 Oct 2011 06:40:01 -0700 (PDT)
Received: by qadb12 with SMTP id b12so6182685qad.31 for <softwires@ietf.org>; Tue, 11 Oct 2011 06:39:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=WXGXerBD0jUJROxhN9CxQB3EylPBMuXFdvlZG9IF+pA=; b=DaImK4KgFJANkqJqMPNy/K4JJh6FBbqO2XgD4KrQ23YXjA+gWakSYTSpp2sD8v4WVo /+CO/F7c/0VKH4btWr8QwaRXJMdOtYjd8AlCeZcd7fUattwsY0FhmKih6zGR4QFfkIOQ 1WVT4NrYAWyjL2D6UIIaGRsj5051vAiqJV5aA=
Received: by 10.68.20.226 with SMTP id q2mr45083589pbe.115.1318340390068; Tue, 11 Oct 2011 06:39:50 -0700 (PDT)
Received: from [192.168.10.54] (softbank221038132005.bbtec.net. [221.38.132.5]) by mx.google.com with ESMTPS id ji3sm79404708pbc.2.2011.10.11.06.39.47 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Oct 2011 06:39:49 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <CAFUBMqVNScO3RnhabHcLVAHwgdRNFOEZ2=4Dfy534mzfJ=ud5g@mail.gmail.com>
Date: Tue, 11 Oct 2011 22:39:44 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <9162B706-CCB4-4DED-B01C-9CB4D8C7706D@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <CAH3bfAA3ttXJ88kLQuNi8w1vT-Dpu5Pdv4S+O-=VHUwFGwAtHQ@mail.gmail.com> <CAFUBMqVNScO3RnhabHcLVAHwgdRNFOEZ2=4Dfy534mzfJ=ud5g@mail.gmail.com>
To: Maoke <fibrib@gmail.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 13:40:04 -0000

On 2011/10/09, at 13:31, Maoke wrote:

> ...
> +----------+-----------------+--------------------+
> |          |source address   | destination address|
> +----------+-----------------+--------------------+
> |  CE-CE   |      N/A        |        N/A         |
> +----------+-----------------+--------------------+
> |  CE-BR   |      N/A        |        Yes         |
> +----------+-----------------+--------------------+
>=20
>=20
> In case you need to embed the full IPv4 address for destination =
address in CE-BR, why not define a unified address format for CE-CE =
model. I think it would be easier to implement and easier to achieve =
further traffic identification in the same way.
>=20
>=20
> agree.=20

I'd agree on that it could be appreciable for the hub and spoke =
scenario. I guess that the 'CE-CE' in the table indicates the mesh =
scenario.

cheers,
--satoru=

From sarikaya2012@gmail.com  Tue Oct 11 09:39:27 2011
Return-Path: <sarikaya2012@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 86D8221F8EA6 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 09:39:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wWwFs-H64dVO for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 09:39:27 -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 E35F021F8EA4 for <softwires@ietf.org>; Tue, 11 Oct 2011 09:39:26 -0700 (PDT)
Received: by gyh20 with SMTP id 20so17125gyh.31 for <softwires@ietf.org>; Tue, 11 Oct 2011 09:39:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=9PUrokTMb0d611nCLebdwDYKO8ZfmFtpdlw4KXzh+k4=; b=QQTs1KxXdcrTB6k8tU38FSoAsgAEDPxm3UqyT2hqDqYTWPv7gfgOpKztiKyWbtWnLh urMquWZy9HPAyuMN8eAR5yx98XS3gp7wrUgLH80Xmyk1PkrB5oDVjSLhgSt9Ea4w0QWs jcMIb9ZykfCBkqPsvKhLJyMfV7ykHusNXGcRs=
MIME-Version: 1.0
Received: by 10.236.76.102 with SMTP id a66mr31212949yhe.25.1318351160774; Tue, 11 Oct 2011 09:39:20 -0700 (PDT)
Received: by 10.236.108.180 with HTTP; Tue, 11 Oct 2011 09:39:20 -0700 (PDT)
In-Reply-To: <20111011161955.16174.89412.idtracker@ietfa.amsl.com>
References: <20111011161955.16174.89412.idtracker@ietfa.amsl.com>
Date: Tue, 11 Oct 2011 11:39:20 -0500
Message-ID: <CAC8QAccD-gCLjF56+J_+NHx0F1-mpFO1PRoXK=mTAmoF7QO20A@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Softwires-wg <softwires@ietf.org>
Content-Type: multipart/alternative; boundary=20cf303b4337a0907104af088c7b
Subject: Re: [Softwires] New Version Notification for draft-sarikaya-softwire-6rdmulticast-02.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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: Tue, 11 Oct 2011 16:39:27 -0000

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

On Tue, Oct 11, 2011 at 11:19 AM, <internet-drafts@ietf.org> wrote:

> A new version of I-D, draft-sarikaya-softwire-6rdmulticast-02.txt has been
> successfully submitted by Behcet Sarikaya and posted to the IETF repository.
>
> Filename:        draft-sarikaya-softwire-6rdmulticast
> Revision:        02
> Title:           Multicast Support for 6rd
> Creation date:   2011-10-11
> WG ID:           Individual Submission
> Number of pages: 15
>
> Abstract:
>   This memo specifies modifications required to 6rd so that both IPv6
>   hosts can receive multicast data from IPv6 servers.  In AMT based
>   solution, AMT Gateway at the 6rd Customer Edge router uses AMT
>   protocol to establish a tunnel interface with AMT Relay at the 6rd
>   Border Relay and this tunnel is used to exchange MLD messages to
>   establish multicast state at AMT Relay so that AMT Relay can tunnel
>   IPv6 multicast data to IPv6 hosts connected to AMT Gateway.  In 6rd
>   Proxy Multicast solution, the protocol is based on proxying MLD at
>   the 6rd Customer Edge router and then tunneling MLD messages to 6rd
>   Border Relays where IPv6 multicast routing is supported.  Multicast
>   data received at 6rd Border Relay is tunneled to 6rd Customer Edge
>   node and then delivered to the hosts.  We show that IPv4 multicast
>   and IGMP can be supported in a similar way.
>
>
>
>
> The IETF Secretariat
>

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

<br><br><div class=3D"gmail_quote">On Tue, Oct 11, 2011 at 11:19 AM,  <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-draft=
s@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
A new version of I-D, draft-sarikaya-softwire-6rdmulticast-02.txt has been =
successfully submitted by Behcet Sarikaya and posted to the IETF repository=
.<br>
<br>
Filename: =A0 =A0 =A0 =A0draft-sarikaya-softwire-6rdmulticast<br>
Revision: =A0 =A0 =A0 =A002<br>
Title: =A0 =A0 =A0 =A0 =A0 Multicast Support for 6rd<br>
Creation date: =A0 2011-10-11<br>
WG ID: =A0 =A0 =A0 =A0 =A0 Individual Submission<br>
Number of pages: 15<br>
<br>
Abstract:<br>
 =A0 This memo specifies modifications required to 6rd so that both IPv6<br=
>
 =A0 hosts can receive multicast data from IPv6 servers. =A0In AMT based<br=
>
 =A0 solution, AMT Gateway at the 6rd Customer Edge router uses AMT<br>
 =A0 protocol to establish a tunnel interface with AMT Relay at the 6rd<br>
 =A0 Border Relay and this tunnel is used to exchange MLD messages to<br>
 =A0 establish multicast state at AMT Relay so that AMT Relay can tunnel<br=
>
 =A0 IPv6 multicast data to IPv6 hosts connected to AMT Gateway. =A0In 6rd<=
br>
 =A0 Proxy Multicast solution, the protocol is based on proxying MLD at<br>
 =A0 the 6rd Customer Edge router and then tunneling MLD messages to 6rd<br=
>
 =A0 Border Relays where IPv6 multicast routing is supported. =A0Multicast<=
br>
 =A0 data received at 6rd Border Relay is tunneled to 6rd Customer Edge<br>
 =A0 node and then delivered to the hosts. =A0We show that IPv4 multicast<b=
r>
 =A0 and IGMP can be supported in a similar way.<br>
<br>
<br>
<br>
<br>
The IETF Secretariat<br>
</blockquote></div><br>

--20cf303b4337a0907104af088c7b--

From tetsuya@ipinfusion.com  Tue Oct 11 16:35:11 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 4B63021F8B5C for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 16:35:11 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dLU0Urza9nDu for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 16:35:10 -0700 (PDT)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id CEC8A21F8B64 for <softwires@ietf.org>; Tue, 11 Oct 2011 16:35:10 -0700 (PDT)
Received: by pzk37 with SMTP id 37so263449pzk.9 for <softwires@ietf.org>; Tue, 11 Oct 2011 16:35:10 -0700 (PDT)
Received: by 10.68.19.225 with SMTP id i1mr49571376pbe.63.1318376110449; Tue, 11 Oct 2011 16:35:10 -0700 (PDT)
Received: from [10.70.2.159] ([12.248.239.142]) by mx.google.com with ESMTPS id o6sm954094pbb.1.2011.10.11.16.35.04 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Oct 2011 16:35:05 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Tetsuya Murakami <tetsuya@ipinfusion.com>
In-Reply-To: <B8DEB256-0585-4279-BC8F-96064B4FF606@employees.org>
Date: Tue, 11 Oct 2011 16:35:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C1E96B3-47C4-45A7-9064-03E70612F5AD@ipinfusion.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <4E92A32C.30306@jacni.com> <B8DEB256-0585-4279-BC8F-96064B4FF606@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1244.3)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 11 Oct 2011 23:35:11 -0000

On 2011/10/10, at 1:58, Ole Troan wrote:

>>> The 4rd function examines ALL packets that reach the CE.
>>> It processes all those that have V in their destination addresses, =
and only those.
>>>=20
>> This is a big change to the current forwarding behavior of CPE =
devices, doable, but quite different from, for example, some =
encapsulation/decapsulation implementations.
>=20
> +1.
> doable in theory, but I share your concerns.

+1.

=46rom a developer point of view, I think there is a big impact on the =
current forwarding behavior on every major operating systems. In fact, I =
have never seen a similar implementation of any =
encapsulation/decapsulation so far.

Normally, the decapsulation could be done for the packet having the =
tunnel end-point address as the destination or having the specific IPv6 =
prefix as the destination. There is a big impact on the current =
implementation to look into a specific value in the last 64bit of IPv6 =
destination address. =46rom the developer point of view, I would like to =
utilize the existing implementation as much as possible.

Thanks,
Tetsuya Murakami=

From jacni@jacni.com  Tue Oct 11 19:03:28 2011
Return-Path: <jacni@jacni.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 49B5321F8C33 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 19:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.58
X-Spam-Level: 
X-Spam-Status: No, score=-1.58 tagged_above=-999 required=5 tests=[AWL=0.708,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCLIa1vCP5ac for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 19:03:27 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 483E221F8C2B for <softwires@ietf.org>; Tue, 11 Oct 2011 19:03:26 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id AE2F5380087 for <softwires@ietf.org>; Tue, 11 Oct 2011 22:03:25 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 6070C3400B7 for <softwires@ietf.org>; Wed, 12 Oct 2011 09:51:06 +0800 (CST)
Received: from [172.18.36.70] (unknown [221.11.61.96]) by app (Coremail) with SMTP id +AWowJAbSgN68pROoK8YAA--.33440S2; Wed, 12 Oct 2011 09:51:06 +0800 (CST)
Message-ID: <4E94F2E3.2000606@jacni.com>
Date: Wed, 12 Oct 2011 09:52:35 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Satoru Matsushima <satoru.matsushima@gmail.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com> <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com> <815B27C6-4C23-4634-A619-912FCC37FEAE@laposte.net> <9988B501-6929-4C5C-9275-E3E7341823EB@gmail.com>
In-Reply-To: <9988B501-6929-4C5C-9275-E3E7341823EB@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-CM-TRANSID: +AWowJAbSgN68pROoK8YAA--.33440S2
X-Coremail-Antispam: 1UD129KBjvJXoW7KFy7JF4fZw1xJw4xAr1UKFg_yoW8XF17pF 48ta15tFWvyr1xCrn3Xa1j9w45Zr1kWay7JrWjq34Y9wn0gFs2va1ak3WrZa98Zrs3Jrn2 vrs2vFy8JF45ZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU7qb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VW3JwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK67kvxFCE54 8m6r1fGryUXwAa7VCY0VAaVVAqrcv_Jw1UWr13Mc02F40EFcxC0VAKzVAqx4xG6I80ewAv 7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64vIr41lc7 I2V7IY0VAS07AlzVAYIcxG8wCF04k20xvY0x0EwIxGrwCFI7vE0wC2zVAF1VAY17CE14v2 6r126r1DMIIYrxkI7VAKI48JYxBIdaVFxhVjvjDU0xZFpf9x07jOL05UUUUU=
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQATEko7lOiu6AAAsL
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 12 Oct 2011 02:03:28 -0000

hi Satoru, Remi,

On 10/11/2011 5:47 PM, Satoru Matsushima wrote:
> ...
>>> Since Remi's draft doesn't specify 'CE IPv6 prefix length', IPv6 prefix can't be self delimiting to extract IPv4 address and port-set ID in the case of double translation. That's my understanding. Is that correct?
>> In my understanding, yes.
>>
>> Now, putting the "CE IPv6 prefix length" back as a rule parameter shouldn't be a problem if the idea of linking IPv4 and IPv6 sizes of address spaces is abandoned (a choice that, I have to agree, simplifies the design).
Not "abandoned" actually, just not that tightly :-). L is not necessary 
by a CE when deriving its v4 space, since it would have got the length 
of prefix delegated to it (so, the L in the rule picked should match the 
length of delegated prefix). The sharing ratio is determined together by 
the L (Rule IPv6 prefix), L (Rule IPv4 prefix) and the L (delegated 
prefix). For example, for a given L (delegated prefix), the other two 
"L" can be changed to get different sharing ratios, or to maintain an 
identical sharing ratio within a domain even the L (delegated prefix) is 
variable.

L (in the matching rule based on IPv4 destination address) allows the CE 
to know the exact number of bits to pick from the port when forming the 
IPv6 destination address.

>>
>> Cheers,
>> RD
> I think that it should be exclusive in a domain but it could be coexist in the map specification.
Sorry, I don't quite follow, can you please say a little more?


Cheers,
Jacni

>
> cheers,
> --satoru
>
>


From tetsuya@ipinfusion.com  Tue Oct 11 22:55:16 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 E12E621F8C54 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 22:55:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LTYSTuy3uh1N for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 22:55:16 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 578A721F8C4F for <softwires@ietf.org>; Tue, 11 Oct 2011 22:55:16 -0700 (PDT)
Received: by iaby26 with SMTP id y26so496435iab.31 for <softwires@ietf.org>; Tue, 11 Oct 2011 22:55:15 -0700 (PDT)
Received: by 10.42.148.198 with SMTP id s6mr32362355icv.56.1318398915654; Tue, 11 Oct 2011 22:55:15 -0700 (PDT)
Received: from [192.168.0.6] (c-76-102-170-116.hsd1.ca.comcast.net. [76.102.170.116]) by mx.google.com with ESMTPS id z11sm2735304iba.6.2011.10.11.22.55.12 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Oct 2011 22:55:13 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Tetsuya Murakami <tetsuya@ipinfusion.com>
In-Reply-To: <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
Date: Tue, 11 Oct 2011 22:55:10 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <14AB4609-752F-44E2-BE75-EB414CC2ACFA@ipinfusion.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 12 Oct 2011 05:55:17 -0000

On 2011/10/08, at 20:14, GangChen wrote:

> As Ole said, "for the outside domain traffic" (Actually, I never argue
> that point for that case)
> Thereby, it's worth to be clarified whether need encoding whole IPv4
> address, as the below table
>=20
> +----------+-----------------+--------------------+
> |          |source address   | destination address|
> +----------+-----------------+--------------------+
> |  CE-CE   |      N/A        |        N/A         |
> +----------+-----------------+--------------------+
> |  CE-BR   |      N/A        |        Yes         |
> +----------+-----------------+--------------------+


+1.

The above matrix is very clear to me.

In case of CE-BR, this case represents the traffic to the outside of the =
domain. In this case, I agree the full IPv4 destination address must be =
embedded in IPv6 destination address.

In case of CE-CE, this case represents the mesh communication between =
CEs. In this case, I don't think we need to embed full IPv4 destination =
address to IPv6 destination address. Because IPv6 destination address =
already includes enough information of IPv4 destination address (part of =
IPv4 address and port-set id).

=46rom the implementation point of view, 4rd function checks if the =
destination is existed inside of the domain or outside of the domain at =
the first step. If the destination is inside of the domain, then 4rd =
function generates the IPv6 destination address from the IPv4 =
destination address or both IPv4 destination address and port. If the =
destination is outside of the domain, then 4rd function can generate the =
IPv6 destination address having the full IPv4 destination address. The =
process of the IPv6 address generation is different on each traffic =
case. Hence, I think 4rd function might be having the separated code for =
the destination address generation and either of code can be invoked =
according to the result of the first step check. In fact, our =
implementation is having the separated code for this IPv6 address =
generation.

In addition, if using the unified address format in CE-CE communication =
as well, some additional CPU cycles per packet are required at CE in =
order to embed the full IPv4 address (and port-set id) in the last 64bit =
of the IPv6 address.

Thanks,
Tetsuya Murakami=

From fibrib@gmail.com  Tue Oct 11 23:17:19 2011
Return-Path: <fibrib@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 F119121F8C51 for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 23:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.732
X-Spam-Level: 
X-Spam-Status: No, score=-2.732 tagged_above=-999 required=5 tests=[AWL=0.866,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I8e2UyAxD7Ms for <softwires@ietfa.amsl.com>; Tue, 11 Oct 2011 23:17:19 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2260621F8BEB for <softwires@ietf.org>; Tue, 11 Oct 2011 23:17:19 -0700 (PDT)
Received: by qadb12 with SMTP id b12so353739qad.31 for <softwires@ietf.org>; Tue, 11 Oct 2011 23:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4g9XjdRigDSWbsj0IEIlLRp1mwCz3CW6lEyJaFQLw7c=; b=Zc9eHwkth1uDmjjVup51V3IeVFTjPHGE8lxt7xU2SwFei2lfQxd4ivMOJbVMV3hNAS 5nB9mxdnJpBG8kalqcDpiAEqBpszTv/YSwAXORGYqzoSGde4cJAJpqOhxtJvbGd1vN5q CD7bE/YfCuhI6DGJ5otHUVPaHjk34IEgjRXQ0=
MIME-Version: 1.0
Received: by 10.224.174.199 with SMTP id u7mr16659242qaz.50.1318400238584; Tue, 11 Oct 2011 23:17:18 -0700 (PDT)
Received: by 10.229.40.197 with HTTP; Tue, 11 Oct 2011 23:17:18 -0700 (PDT)
In-Reply-To: <14AB4609-752F-44E2-BE75-EB414CC2ACFA@ipinfusion.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <14AB4609-752F-44E2-BE75-EB414CC2ACFA@ipinfusion.com>
Date: Wed, 12 Oct 2011 15:17:18 +0900
Message-ID: <CAFUBMqVni_GNqmEx-FwzNUKUD1x2hN=xoe7Zc9pre4rfmGBWRw@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Tetsuya Murakami <tetsuya@ipinfusion.com>
Content-Type: multipart/alternative; boundary=20cf30334c89e4852d04af13f979
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 12 Oct 2011 06:17:20 -0000

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

hi Tetsuya,

questions of trying to understand points, inline.

2011/10/12 Tetsuya Murakami <tetsuya@ipinfusion.com>

>
> On 2011/10/08, at 20:14, GangChen wrote:
>
> > As Ole said, "for the outside domain traffic" (Actually, I never argue
> > that point for that case)
> > Thereby, it's worth to be clarified whether need encoding whole IPv4
> > address, as the below table
> >
> > +----------+-----------------+--------------------+
> > |          |source address   | destination address|
> > +----------+-----------------+--------------------+
> > |  CE-CE   |      N/A        |        N/A         |
> > +----------+-----------------+--------------------+
> > |  CE-BR   |      N/A        |        Yes         |
> > +----------+-----------------+--------------------+
>
>
> +1.
>
> The above matrix is very clear to me.
>
> In case of CE-BR, this case represents the traffic to the outside of the
> domain. In this case, I agree the full IPv4 destination address must be
> embedded in IPv6 destination address.
>
> In case of CE-CE, this case represents the mesh communication between CEs.
> In this case, I don't think we need to embed full IPv4 destination address
> to IPv6 destination address. Because IPv6 destination address already
> includes enough information of IPv4 destination address (part of IPv4
> address and port-set id).
>
> From the implementation point of view, 4rd function checks if the
> destination is existed inside of the domain or outside of the domain at the
> first step.


how does 4rd do the check? through routing table(s) or through all the
mapping rules which is either configured or distributed or learned?


> If the destination is inside of the domain, then 4rd function generates the
> IPv6 destination address from the IPv4 destination address or both IPv4
> destination address and port. If the destination is outside of the domain,
> then 4rd function can generate the IPv6 destination address having the full
> IPv4 destination address. The process of the IPv6 address generation is
> different on each traffic case. Hence, I think 4rd function might be having
> the separated code for the destination address generation and either of code
> can be invoked according to the result of the first step check. In fact, our
> implementation is having the separated code for this IPv6 address
> generation.


> In addition, if using the unified address format in CE-CE communication as
> well, some additional CPU cycles per packet are required at CE in order to
> embed the full IPv4 address (and port-set id) in the last 64bit of the IPv6
> address.
>
>
how many additional CPU cycles (or instructions) per packet will cost in
order to put things in the last 64bits?
does it not cost CPU cycles to check whether the destination exists inside
or outside of the domain? or it is not per-packet pace?

Thanks,
> Tetsuya Murakami


thanks and regards,
maoke

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

<div>hi Tetsuya,</div><div><br></div><div>questions of trying to understand=
 points, inline.=A0</div><div><br></div><div class=3D"gmail_quote">2011/10/=
12 Tetsuya Murakami <span dir=3D"ltr">&lt;<a href=3D"mailto:tetsuya@ipinfus=
ion.com">tetsuya@ipinfusion.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im"><br>
On 2011/10/08, at 20:14, GangChen wrote:<br>
<br>
&gt; As Ole said, &quot;for the outside domain traffic&quot; (Actually, I n=
ever argue<br>
&gt; that point for that case)<br>
&gt; Thereby, it&#39;s worth to be clarified whether need encoding whole IP=
v4<br>
&gt; address, as the below table<br>
&gt;<br>
&gt; +----------+-----------------+--------------------+<br>
&gt; | =A0 =A0 =A0 =A0 =A0|source address =A0 | destination address|<br>
&gt; +----------+-----------------+--------------------+<br>
&gt; | =A0CE-CE =A0 | =A0 =A0 =A0N/A =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0N/A =
=A0 =A0 =A0 =A0 |<br>
&gt; +----------+-----------------+--------------------+<br>
&gt; | =A0CE-BR =A0 | =A0 =A0 =A0N/A =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0Yes =
=A0 =A0 =A0 =A0 |<br>
&gt; +----------+-----------------+--------------------+<br>
<br>
<br>
</div>+1.<br>
<br>
The above matrix is very clear to me.<br>
<br>
In case of CE-BR, this case represents the traffic to the outside of the do=
main. In this case, I agree the full IPv4 destination address must be embed=
ded in IPv6 destination address.<br>
<br>
In case of CE-CE, this case represents the mesh communication between CEs. =
In this case, I don&#39;t think we need to embed full IPv4 destination addr=
ess to IPv6 destination address. Because IPv6 destination address already i=
ncludes enough information of IPv4 destination address (part of IPv4 addres=
s and port-set id).<br>

<br>
>From the implementation point of view, 4rd function checks if the destinati=
on is existed inside of the domain or outside of the domain at the first st=
ep. </blockquote><div><br></div><div>how does 4rd do the check? through rou=
ting table(s) or through all the mapping rules which is either configured o=
r distributed or learned?=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">If the destination is inside =
of the domain, then 4rd function generates the IPv6 destination address fro=
m the IPv4 destination address or both IPv4 destination address and port. I=
f the destination is outside of the domain, then 4rd function can generate =
the IPv6 destination address having the full IPv4 destination address. The =
process of the IPv6 address generation is different on each traffic case. H=
ence, I think 4rd function might be having the separated code for the desti=
nation address generation and either of code can be invoked according to th=
e result of the first step check. In fact, our implementation is having the=
 separated code for this IPv6 address generation.=A0</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<br>
In addition, if using the unified address format in CE-CE communication as =
well, some additional CPU cycles per packet are required at CE in order to =
embed the full IPv4 address (and port-set id) in the last 64bit of the IPv6=
 address.<br>

<br>
</blockquote><div><br></div><div>how many additional CPU cycles (or instruc=
tions) per packet will cost in order to put things in the last 64bits?</div=
><div>does it not cost CPU cycles to check whether the destination exists i=
nside or outside of the domain? or it is not per-packet pace?</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">Thanks,<br>
<font color=3D"#888888">Tetsuya Murakami</font></blockquote></div><div><br>=
</div><div>thanks and regards,<br></div><div>maoke</div>

--20cf30334c89e4852d04af13f979--

From leaf.y.yeh@huawei.com  Wed Oct 12 00:41:19 2011
Return-Path: <leaf.y.yeh@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 6090421F8B15 for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 00:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hM76VhfwqmIE for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 00:41:18 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 44D4B21F8A6F for <softwires@ietf.org>; Wed, 12 Oct 2011 00:41:17 -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 <0LSX00KB0Z9T8L@szxga04-in.huawei.com> for softwires@ietf.org; Wed, 12 Oct 2011 15:25:05 +0800 (CST)
Received: from szxrg02-dlp.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 <0LSX00BWVZ9TY3@szxga04-in.huawei.com> for softwires@ietf.org; Wed, 12 Oct 2011 15:25:05 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEE60876; Wed, 12 Oct 2011 15:25:05 +0800
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 12 Oct 2011 15:24:58 +0800
Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.227]) by szxeml409-hub.china.huawei.com ([10.82.67.136]) with mapi id 14.01.0270.001; Wed, 12 Oct 2011 15:24:58 +0800
Date: Wed, 12 Oct 2011 07:24:57 +0000
From: Leaf yeh <leaf.y.yeh@huawei.com>
In-reply-to: <77E5DB2B-70A2-4797-AE89-5D6A5D8E514F@gmail.com>
X-Originating-IP: [10.70.39.98]
To: Satoru Matsushima <satoru.matsushima@gmail.com>, Tetsuya Murakami <tetsuya@ipinfusion.com>
Message-id: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05767E7E@SZXEML510-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
Thread-index: AQHMh0ClppljXMMUk0246OCDrJF2JZV2S26AgACkO2D//4ysgIABxLiA
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com> <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05766BB8@SZXEML510-MBS.china.huawei.com> <77E5DB2B-70A2-4797-AE89-5D6A5D8E514F@gmail.com>
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 12 Oct 2011 07:41:19 -0000

U2F0b3J1IC0+IEkgdGhpbmsgd2UgY291bGQgaGF2ZSBpdC4NClRldHN1eWEgTXVyYWthbWkgLT4g
dGhlIGRlY2Fwc3VsYXRpb24gY291bGQgYmUgZG9uZSBmb3IgdGhlIHBhY2tldCBoYXZpbmcgdGhl
IHR1bm5lbCBlbmQtcG9pbnQgYWRkcmVzcyBhcyB0aGUgZGVzdGluYXRpb24gb3IgaGF2aW5nIHRo
ZSBzcGVjaWZpYyBJUHY2IHByZWZpeCBhcyB0aGUgZGVzdGluYXRpb24uDQoNCkRvZXMgdGhhdCBt
ZWFuIEJSIG5lZWRzIHRvIGluamVjdCBhIHJvdXRlIHBvaW50aW5nIHRvIHRoZSBCUiBzdWJuZXQg
cHJlZml4LCBhbmQgdXNpbmcgb25lIGludGVyZmFjZSBhZGRyZXNzIG9mIEJSIGFzIHRoZSBuZXh0
LWhvcCBvZiB0aGlzIHByZWZpeCBpbiB0aGUgcm91dGU/IFRoYXQgbWVhbnMgcm91dGVzIGNhbiBk
aXJlY3QgdGhlIHBhY2tldHMgZ28gdG8gdGhlIHJpZ2h0IGludGVyZmFjZSBvZiB0aGUgQlIsIHJp
Z2h0Pw0KDQoNCkJlc3QgUmVnYXJkcywNCkxlYWYNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KRnJvbTogU2F0b3J1IE1hdHN1c2hpbWEgW21haWx0bzpzYXRvcnUubWF0c3VzaGltYUBn
bWFpbC5jb21dIA0KU2VudDogVHVlc2RheSwgT2N0b2JlciAxMSwgMjAxMSA3OjI1IFBNDQpUbzog
TGVhZiB5ZWgNCkNjOiBTYXRvcnUgTWF0c3VzaGltYTsgUsOpbWkgRGVzcHLDqXM7IE9sZSBUcm9h
bjsgU29mdHdpcmVzLXdnOyBmaW5lX3N6QGh1YXdlaS5jb20NClN1YmplY3Q6IFJlOiBbU29mdHdp
cmVzXSBQcm9wb3NlZCBVbmlmaWVkIEFkZHJlc3MgTWFwcGluZyBmb3IgZW5jYXBzdWxhdGlvbiBh
bmQgZG91YmxlLXRyYW5zbGF0aW9uDQoNCk9uIDIwMTEvMTAvMTEsIGF0IDIwOjAwLCBMZWFmIHll
aCB3cm90ZToNCg0KPj4gUmVtaSAtID4+IEEgRGVzdGluYXRpb24gYWRkcmVzcyBmcm9tIGEgQ0Ug
dG8gdGhlIG91dHNpZGUgSVB2NCBJbnRlcm5ldCBpczoNCj4+Pj4gPC0tLS0tLS0tLSA2NCAtLS0t
LS0tLS0tLS0+PCA4ID48LS0tLSAgIDMyIC0tLS0+PC0tLSAxNiAtLS0tPjw4ID4NCj4+Pj4gKy0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0rLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0t
LSstLS0rDQo+Pj4+IHwgICAgIEJSIHN1Ym5ldCBwcmVmaXggICAgIHwgViAgfCAgSVB2NCBhZGRy
ZXNzIHwgICAgICAwICAgICB8MzIgfA0KPj4+PiArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0r
LS0tLSstLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKy0tLSsNCj4gTGVhZiAtPiBJbiBmYWN0
LCBJIGRvdWJ0cyB3ZSBjb3VsZCBoYXZlIHRoZSBzYW1lIGFkZHJlc3MgbWFwcGluZyBmb3IgYm90
aCB0dW5uZWwgYW5kIHRyYW5zbGF0aW9uLiBTdXBwb3NlZCB0aGUgYWRkcmVzcyBvZiB0dW5uZWwg
ZW5kLXBvaW50cyBpcyBwcmVmZXJyZWQgdG8gYmUgZml4ZWQsIGJ1dCB0aGUgYWRkcmVzcyBmb3Ig
dGhlIHRyYW5zbGF0aW9uIGNvdWxkIGJlIHZhcmlhYmxlLg0KPiBTYXRvcnUgLT4gSSB0aGluayB3
ZSBjb3VsZCBoYXZlIGl0Lg0KPiANCj4gV2hhdCBpcyB0aGUgZGVmaW5pdGlvbiBvZiB0aGUgSVB2
NCBhZGRyZXNzIGluIHRoZSBhYm92ZSBmb3JtYXQ/IElzIGl0IHRoZSBkZXN0aW5hdGlvbiBJUHY0
IGFkZHJlc3Mgb2YgYW55IGhvc3RzIG91dHNpZGUgNHJkIElQdjQgZG9tYWluIGluIHRoZSBpbnRl
cm5ldD8NCg0KSSBiZWxpZXZlIHRoYXQgdGhlIGVtYmVkZGVkIElQdjQgYWRkcmVzcyBzaG91bGQg
YmUgYW4gSVB2NCBhZGRyZXNzIG9mIGEgaG9zdCBvbiBvdXRzaWRlIHRoZSBkb21haW4uDQoNCmNo
ZWVycywNCi0tc2F0b3J1DQoNCj4gDQo+IA0KPiBCZXN0IFJlZ2FyZHMsDQo+IExlYWYNCj4gDQo+
IA0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBTYXRvcnUgTWF0c3VzaGlt
YSBbbWFpbHRvOnNhdG9ydS5tYXRzdXNoaW1hQGdtYWlsLmNvbV0gDQo+IFNlbnQ6IFR1ZXNkYXks
IE9jdG9iZXIgMTEsIDIwMTEgNDozMCBQTQ0KPiBUbzogTGVhZiB5ZWgNCj4gQ2M6IFNhdG9ydSBN
YXRzdXNoaW1hOyBSw6ltaSBEZXNwcsOpczsgT2xlIFRyb2FuOyBTb2Z0d2lyZXMtd2c7IGZpbmVf
c3pAaHVhd2VpLmNvbQ0KPiBTdWJqZWN0OiBSZTogW1NvZnR3aXJlc10gUHJvcG9zZWQgVW5pZmll
ZCBBZGRyZXNzIE1hcHBpbmcgZm9yIGVuY2Fwc3VsYXRpb24gYW5kIGRvdWJsZS10cmFuc2xhdGlv
bg0KPiANCj4gTGVhZiwgdGhhbmtzIGZvciB0aGUgc3VtbWFyeS4NCj4gDQo+IE9uIDIwMTEvMTAv
MTAsIGF0IDIwOjM0LCBMZWFmIHllaCB3cm90ZToNCj4gDQo+PiBSZW1pIC0gPj4gYTEtIElmIHRo
ZSBDRSBoYXMgYW4gZXhjbHVzaXZlIG9yIHNoYXJlZCBJUHY0IGFkZHJlc3M6DQo+Pj4+IDwtLS0t
LS0tLS0gNjQgLS0tLS0tLS0tLS0tPjw4ID48LS0tLS0tIEwgPj0gMzIgLS0tLS0tLT48NDgtTD48
OCA+DQo+Pj4+ICstLS0tLS0tLS0tLS0tKy0tLS0tLS0tKy0tLSstLS0rLS0tLS0tLS0tLS0tLS0t
LSstLS0tLS0rLS0tLS0rLS0tKw0KPj4+PiB8IElQdjYgcHJlZml4IHxDRSBpbmRleHwgMCB8IFYg
fCAgSVB2NCBhZGRyZXNzICB8IFBTSUQgfCAgMCAgfCBMIHwNCj4+Pj4gKy0tLS0tLS0tLS0tLS0r
LS0tLS0tLS0rLS0tKy0tLSstLS0tLS0tLS0tLS0tLS0tKy0tLS0tLSstLS0tLSstLS0rDQo+PiBP
bGUgLSA+IHB1dHRpbmcgdGhlIElQdjQgYWRkcmVzcyAvIHBvcnQgaW5mb3JtYXRpb24gYXQgdGhl
IGVuZCBvZiB0aGUgaW50ZXJmYWNlIGlkZW50aWZpZXIgd2lsbCBhbGxvdyBmb3IgPiAvNjQgc3Vw
cG9ydC4gPiB3aGF0J3MgdGhlIEw/DQo+PiBSZW1pIC0gRG9uJ3Qgc2VlIHdoYXQgeW91IGZvdW5k
IHVuY2xlYXIuDQo+PiANCj4+IA0KPj4gUXVlc3Rpb246IFN1cHBvc2VkIHRoZSBxdWVzdGlvbiBp
cyBvbiB0aGUgbGFzdCBmaWVsZCwgbmFtZWQgJ0wnLCBpbiB0aGUgbmV3IGFkZHJlc3MgZm9ybWF0
Lg0KPj4gDQo+IA0KPiBTaW5jZSBSZW1pJ3MgZHJhZnQgZG9lc24ndCBzcGVjaWZ5ICdDRSBJUHY2
IHByZWZpeCBsZW5ndGgnLCBJUHY2IHByZWZpeCBjYW4ndCBiZSBzZWxmIGRlbGltaXRpbmcgdG8g
ZXh0cmFjdCBJUHY0IGFkZHJlc3MgYW5kIHBvcnQtc2V0IElEIGluIHRoZSBjYXNlIG9mIGRvdWJs
ZSB0cmFuc2xhdGlvbi4gVGhhdCdzIG15IHVuZGVyc3RhbmRpbmcuIElzIHRoYXQgY29ycmVjdD8N
Cj4gQXMgJzRyZC1hJywgYW5kIDR2aWE2KGRyYWZ0LW11cmFrYW1pLXNvZnR3aXJlLTR2Ni10cmFu
c2xhdGlvbiksIHRoZSAnTCcgYml0cyBhcmUgbm90IG5lY2Vzc2FyeSBiZWNhdXNlICdDRSBJUHY2
IHByZWZpeCBsZW5ndGgnIGlzIGRlZmluZWQgdGhyb3VnaCBhIGRvbWFpbiwgaW5zdGVhZCBvZiAn
TCcuDQo+IA0KPiANCj4+IA0KPj4gUmVtaSAtID4+IEEgRGVzdGluYXRpb24gYWRkcmVzcyBmcm9t
IGEgQ0UgdG8gdGhlIG91dHNpZGUgSVB2NCBJbnRlcm5ldCBpczoNCj4+Pj4gPC0tLS0tLS0tLSA2
NCAtLS0tLS0tLS0tLS0+PCA4ID48LS0tLSAgIDMyIC0tLS0+PC0tLSAxNiAtLS0tPjw4ID4NCj4+
Pj4gKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0rLS0tLS0tLS0tLS0tLS0tKy0tLS0t
LS0tLS0tLSstLS0rDQo+Pj4+IHwgICAgIEJSIHN1Ym5ldCBwcmVmaXggICAgIHwgViAgfCAgSVB2
NCBhZGRyZXNzIHwgICAgICAwICAgICB8MzIgfA0KPj4+PiArLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0rLS0tLSstLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKy0tLSsNCj4+IE9sZSAtIHRo
aXMgaXMgYSBiaWcgY2hhbmdlIGZvciBlbmNhcHN1bGF0aW9uLCB3aGVyZSBwcmlvciB0byB0aGlz
IGVuY2Fwc3VsYXRpb24gbWVhbnMgc2VuZGluZyB0byBhIHNpbmdsZSBkZXN0aW5hdGlvbi4NCj4+
IFJlbWkgLSBDb3B5aW5nIGFuIGF2YWlsYWJsZSBJUHY0IGFkZHJlc3MgYXQgYSBmaXhlZCBwbGFj
ZSBpc24ndCBJTUhPIGEgImJpZyBjaGFuZ2UiLg0KPj4gDQo+PiANCj4+IENvbmNlcm46IFN1cHBv
c2VkIHRoZSByZXBsYWNlbWVudCBvZiB0aGUgMXN0IDY0Yml0cyBvZiB0aGUgQlIgYWRkcmVzcyB3
aXRoIGEgc3VibmV0IHByZWZpeCBpcyBub3QgZm9yIHRoZSB0dW5uZWwgY2FzZSBpZiB0aGUgZmll
bGQgb2YgSVB2NCBhZGRyZXNzIGNhbiBiZSB2YXJpYWJsZSwgcmlnaHQ/DQo+IA0KPiBJIHRoaW5r
IHRoYXQgaXQgY291bGQgYmUgYSBjYXNlIHdoZXJlIHRoZSBCUiBhZGRyZXNzIHdpdGggYSBzdWJu
ZXQgcHJlZml4IGZvciB0aGUgdHVubmVsIGNhc2UuIE15IGNvbmNlcm4gcmF0aGVyIHRoYW4gdGhl
IEJSIGFkZHJlc3MgaXMgdGhhdCBhIENFIHNob3VsZCBwaWNrIHBhY2tldHMgdXAgd2hpY2ggaGF2
ZSAnVicgaW4gSUlELCBldmVuIGRlc3RpbmVkIHByZWZpeGVzIGFyZSBkZWxlZ2F0ZWQgdG8gbm9k
ZXMgd2hpY2ggYXJlIGJlaGluZCBvZiB0aGUgQ0UuDQo+IA0KPiANCj4+IA0KPj4gSW4gZmFjdCwg
SSBkb3VidHMgd2UgY291bGQgaGF2ZSB0aGUgc2FtZSBhZGRyZXNzIG1hcHBpbmcgZm9yIGJvdGgg
dHVubmVsIGFuZCB0cmFuc2xhdGlvbi4gU3VwcG9zZWQgdGhlIGFkZHJlc3Mgb2YgdHVubmVsIGVu
ZC1wb2ludHMgaXMgcHJlZmVycmVkIHRvIGJlIGZpeGVkLCBidXQgdGhlIGFkZHJlc3MgZm9yIHRo
ZSB0cmFuc2xhdGlvbiBjb3VsZCBiZSB2YXJpYWJsZS4NCj4+IA0KPiANCj4gSSB0aGluayB3ZSBj
b3VsZCBoYXZlIGl0Lg0KPiANCj4gY2hlZXJzLA0KPiAtLXNhdG9ydQ0KPiANCj4gDQo+PiANCj4+
IEJlc3QgUmVnYXJkcywNCj4+IExlYWYNCj4+IA0KPj4gDQo+PiAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPj4gRnJvbTogc29mdHdpcmVzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpzb2Z0
d2lyZXMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFLDqW1pIERlc3Byw6lzDQo+PiBT
ZW50OiBUaHVyc2RheSwgT2N0b2JlciAwNiwgMjAxMSA2OjA3IFBNDQo+PiBUbzogT2xlIFRyb2Fu
DQo+PiBDYzogU29mdHdpcmVzLXdnDQo+PiBTdWJqZWN0OiBSZTogW1NvZnR3aXJlc10gUHJvcG9z
ZWQgVW5pZmllZCBBZGRyZXNzIE1hcHBpbmcgZm9yIGVuY2Fwc3VsYXRpb24gYW5kIGRvdWJsZS10
cmFuc2xhdGlvbg0KPj4gDQo+PiANCj4+IExlIDYgb2N0LiAyMDExIMOgIDE4OjQ3LCBPbGUgVHJv
YW4gYSDDqWNyaXQgOg0KPj4gDQo+Pj4gUmVtaSwNCj4+PiANCj4+PiBbLi4uXQ0KPj4+IA0KPj4+
PiAyLg0KPj4+PiAoYSkNCj4+Pj4gVGhlIElQdjYgU291cmNlIGFkZHJlc3Mgb2YgYW4gSVB2NCBw
YWNrZXQgZnJvbSBhIENFIGlzOg0KPj4+PiANCj4+Pj4gYTEtIElmIHRoZSBDRSBoYXMgYW4gZXhj
bHVzaXZlIG9yIHNoYXJlZCBJUHY0IGFkZHJlc3M6DQo+Pj4+IA0KPj4+PiA8LS0tLS0tLS0tIDY0
IC0tLS0tLS0tLS0tLT48OCA+PC0tLS0tLSBMID49IDMyIC0tLS0tLS0+PDQ4LUw+PDggPg0KPj4+
PiArLS0tLS0tLS0tLS0tLSstLS0tLS0tLSstLS0rLS0tKy0tLS0tLS0tLS0tLS0tLS0rLS0tLS0t
Ky0tLS0tKy0tLSsNCj4+Pj4gfCBJUHY2IHByZWZpeCB8Q0UgaW5kZXh8IDAgfCBWIHwgIElQdjQg
YWRkcmVzcyAgfCBQU0lEIHwgIDAgIHwgTCB8DQo+Pj4+ICstLS0tLS0tLS0tLS0tKy0tLS0tLS0t
Ky0tLSstLS0rLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0rLS0tKw0KPj4+IA0KPj4+IHB1
dHRpbmcgdGhlIElQdjQgYWRkcmVzcyAvIHBvcnQgaW5mb3JtYXRpb24gYXQgdGhlIGVuZCBvZiB0
aGUgaW50ZXJmYWNlIGlkZW50aWZpZXIgd2lsbCBhbGxvdyBmb3IgPiAvNjQgc3VwcG9ydC4NCj4+
IA0KPj4gQ291bGQgeW91IGV4cGxhaW4gbW9yZSB0aGUgcmVxdWlyZW1lbnQgeW91IGhhdmUgaW4g
bWluZD8gIA0KPj4gDQo+Pj4gd2hhdCdzIHRoZSBMPw0KPj4gDQo+PiBPbiB0aGUgcGljdHVyZSwg
TCBpcyAzMiBiaXRzICsgTGVuZ3RoKFBTSUQpLg0KPj4gRG9uJ3Qgc2VlIHdoYXQgeW91IGZvdW5k
IHVuY2xlYXIuIA0KPj4gDQo+Pj4gDQo+Pj4geW91IHN1Z2dlc3QgdGhhdCB0aGUgZmlyc3Qgc3Vi
bmV0IG9mIGFuIGFsbG9jYXRpb24gc2hvdWxkIGJlIHVzZWQgZm9yIHRoaXMgcHVycG9zZS4NCj4+
IA0KPj4gRGlkIEkgZG8gdGhpcz8NCj4+IFBsZWFzZSBleHBsYWluIGJlY2F1c2UgdGhhdCdzIG5v
dCwgSU1ITywgIHNvbWV0aGluZyB0byBiZSBkb25lLg0KPj4gDQo+Pj4gdGhlIGZpcnN0IHN1Ym5l
dCBpcyBjb252ZW5pZW50IHRvIHVzZSBmb3IgZS5nLiBtYW51YWwgYWRkcmVzc2luZyAoc2luY2Ug
aXQgYWxsb3dzIHRoZSA6OiBzaG9ydCBoYW5kKS4NCj4+PiBJIGRvIHdvbmRlciBpZiB0aGlzIGhh
cyB0byBiZSBwcm92aXNpb25lZC4gZS5nLiBzb21lIGRlcGxveW1lbnRzIG1heSB1c2UgdGhlIGZp
cnN0IHN1Ym5ldCBmb3IgdGhlIGxpbmsgYmV0d2Vlbg0KPj4+IENFIGFuZCBQRS4gKGkuZS4gYSAv
NTYgLSAxIHVzaW5nIHRoZSBQRCBleGNsdWRlIG9wdGlvbiBpcyB1c2VkKS4NCj4+IA0KPj4gU2Vl
IGp1c3QgYWJvdmUuDQo+PiANCj4+PiANCj4+Pj4gYTItIElmIHRoZSBDRSBoYXMgYW4gSVB2NCBw
cmVmaXg6DQo+Pj4+IA0KPj4+PiA8LS0tLS0tLS0tIDY0IC0tLS0tLS0tLS0tLT48OCA+PC0tIEwg
PCAzMiAtLT48LS0tIDQ4LUwgLS0tLS0+PDggPg0KPj4+PiArLS0tLS0tLS0tLS0tLSstLS0tLS0t
LSstLS0rLS0tKy0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tKy0tLSsNCj4+Pj4gfCBJUHY2
IHByZWZpeCB8Q0UgaW5kZXh8IDAgfCBWIHwgSVB2NCBwcmVmaXggfCAgICAgICAgIDAgICAgIHwg
TCB8DQo+Pj4+ICstLS0tLS0tLS0tLS0tKy0tLS0tLS0tKy0tLSstLS0rLS0tLS0tLS0tLS0tLSst
LS0tLS0tLS0tLS0tLS0rLS0tKw0KPj4+PiANCj4+Pj4gKGIpDQo+Pj4+IFYgaXMgdGhlIG1hcmsg
dGhhdCBjaGFyYWN0ZXJpemVzIElQdjYgcGFja2V0cyB0aGF0IGFyZSBpbiByZWFsaXR5IElQdjQg
cGFja2V0cy4NCj4+Pj4gSXRzIHZhbHVlIGRpZmZlcnMgZnJvbSBhbnkgcGVybWl0dGVkIHZhbHVl
IG9mIHRoaXMgb2N0ZXQgaW4gSVB2NiBJSURzICAocmVmIFJGQyA0MjkxKS4NCj4+Pj4gDQo+Pj4+
IEl0IGlzIHVuZGVyc3Rvb2QgdGhhdCwgaWYgZG91YmxlIFRyYW5zbGF0aW9uIGNvZXhpc3RzIHdp
dGggc2luZ2xlIHRyYW5zbGF0aW9uLCBjb25jZXJuZWQgSVNQcyBtYXkgbm90aWZ5IHRoZWlyIENF
cyB0byB1c2UgdGhlIFUgb2N0ZXQgb2YgUkZDIDYwNTIgaW5zdGVhZCBvZiBWLg0KPj4+PiANCj4+
Pj4gQW4gdW5hbWJpZ3VvdXMgbWFyayBpcyBmb3J0dW5hdGVseSBwb3NzaWJsZSBiZWNhdXNlIGN1
cnJlbnRseSBwZXJtaXR0ZWQgSUlEcyBoYXZlIGluIHRoZWlyIGZpcnN0IG9jdGV0IGVpdGhlciBi
aXQ2ID0gMCAodGhlICJ1IiBiaXQiKSwgb3IgYml0NiA9IDEgYW5kIGJpdDc9IDAgKHRoZSAiZyIg
Yml0KS4NCj4+Pj4gV2l0aCBWIGhhdmluZyAidSIgPSAxIChzaWduaWZ5aW5nIFVuaXZlcnNhbCBz
Y29wZSkgQU5EICJnIiA9IDEsIGRpc3RpbmN0aW9uIGlzIHRoZXJlZm9yZSBkZXRlcm1pbmlzdGlj
Lg0KPj4+PiANCj4+Pj4gVGhlIHByb3Bvc2VkIFYgaXMgPSAwMDAwMDAxMS4gDQo+Pj4+IChXaXRo
IG90aGVyIHZhbHVlcyBvZiB0aGlzIG9jdGV0LCBvdGhlciBJSUQgZm9ybWF0cyBjYW4gYmUgZGVm
aW5lZCBpbiBjYXNlIHNvbWUgd291bGQgYmUgdXNlZnVsIGluIHRoZSBmdXR1cmUuKQ0KPj4+PiAN
Cj4+Pj4gTm90ZSB0aGF0LCBpZiBhbmQgd2hlbiBhIGNvbnNlbnN1cyBpcyByZWFjaGVkIGluIFNv
ZnR3aXJlLCBhbiBleHRlbnNpb24gb2YgUkZDIDQyOTEgd2lsbCBoYXZlIHRvIGJlIHN1Ym1pdHRl
ZCB0byA2TUFOLiANCj4+PiANCj4+PiBvciByYXRoZXIgSUVFRT8NCj4+IA0KPj4gSU1ITywgSUVF
RSBoYXMgbm90aGluZyB0byBkbyB3aXRoIGEgbWFya2VyIHRoYXQgaXMgcHVycG9zZWx5IGFuIGVz
Y2FwZSBtZWNoYW5pc20gZnJvbSB0aGUgbW9kaWZpZWQgRVVJLTY0IGZvcm1hdCBvZiBSRkMgNDI5
MS4NCj4+IA0KPj4+IEkgYW0gbm90IGNvbnZpbmNlZCB0aGF0ICJWIiBpcyBuZWVkZWQuDQo+PiAN
Cj4+IFRoZSBwb2ludCBpcyBtb3JlLCBJTUhPLCB3aGV0aGVyIHlvdSBoYXZlIGFuIG9iamVjdGlv
biB0byBpdCAoYW5kIGluIHRoaXMgY2FzZSB3aGljaCBvbmUpLg0KPj4gUmVhc29uIGlzIHRoYXQg
d2UgYXJlIHdvcmtpbmcgZm9yIGEgY29uc2Vuc3VzLCBhbmQgc2V2ZXJhbCBhcmUgc2F0aXNmaWVk
IHdpdGggdGhlIGV4cGxhbmF0aW9uIHRoYXQgdGhlcmUgYXJlIHVzZSBjYXNlcyB3aGVyZSBpdCBp
cyB1c2VmdWwsIGFuZCBub25lIHdoZXJlIGl0IGlzIGhhcm1mdWwuDQo+PiANCj4+PiB5b3UgY291
bGQgZXZlbiB1c2UgdGhlIElBTkEgT1VJIGlmIHByZXR0eSBwcmludGluZyB3YXMgcmVxdWlyZWQu
DQo+PiANCj4+IFRoZSBwb2ludCBpcyB0aGF0IGl0IHRha2VzIDMyIGJpdHMgd2hpY2ggaXMgdG9v
IG11Y2ggdG8gaGF2ZSBJUHY0IGFkZHJlc3MgKyBQU0lEIGluIHRoZSBJSUQuDQo+PiANCj4+IA0K
Pj4+PiAoYykgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KPj4+PiBBIERlc3Rp
bmF0aW9uIGFkZHJlc3MgZnJvbSBhIENFIHRvIHRoZSBvdXRzaWRlIElQdjQgSW50ZXJuZXQgaXM6
DQo+Pj4+IDwtLS0tLS0tLS0gNjQgLS0tLS0tLS0tLS0tPjwgOCA+PC0tLS0gICAzMiAtLS0tPjwt
LS0gMTYgLS0tLT48OCA+DQo+Pj4+ICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tKy0t
LS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0rLS0tKw0KPj4+PiB8ICAgICBCUiBzdWJuZXQgcHJl
Zml4ICAgICB8IFYgIHwgIElQdjQgYWRkcmVzcyB8ICAgICAgMCAgICAgfDMyIHwNCj4+Pj4gKy0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0rLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0t
LSstLS0rDQo+Pj4gDQo+Pj4gdGhpcyBpcyBhIGJpZyBjaGFuZ2UgZm9yIGVuY2Fwc3VsYXRpb24s
IHdoZXJlIHByaW9yIHRvIHRoaXMgZW5jYXBzdWxhdGlvbiBtZWFucyBzZW5kaW5nIHRvIGEgc2lu
Z2xlIGRlc3RpbmF0aW9uLg0KPj4gDQo+PiBDb3B5aW5nIGFuIGF2YWlsYWJsZSBJUHY0IGFkZHJl
c3MgYXQgYSBmaXhlZCBwbGFjZSBpc24ndCBJTUhPIGEgImJpZyBjaGFuZ2UiLg0KPj4gDQo+Pj4g
aWYgd2UgYWxzbyBhbGxvdyBmb3IgYSBCUiBzdWJuZXQgcHJlZml4IG9mIC8xMjggSSdtIE9LIHdp
dGggdGhpcyAoSSB0aGluaykuDQo+PiANCj4+IEkgZG9uJ3QgdW5kZXJzdGFuZCB3aGF0IHlvdSBt
ZWFuIGJ5ICJTdWJuZXQgcHJlZml4IG9mIC8xMjgiLg0KPj4gDQo+PiANCj4+Pj4gTm90ZSB0aGF0
IGlmIGRvdWJsZS10cmFuc2xhdGlvbiBDRXMgYXJlIG5vdGlmaWVkIHRvIHVzZSBVIGluc3RlYWQg
b2YgViwgdGhlIGxhc3Qgb2N0ZXQgYmVjb21lcyAwIHBlciBSRkMgIDYwNTIuDQo+Pj4gDQo+Pj4g
aG93IHdvdWxkIGEgQ0Uga25vdyBpZiBpdCB3YXMgc2luZ2xlIG9yIGRvdWJsZSB0cmFuc2xhdGlu
Zz8NCj4+IA0KPj4gUHJlc3VtYWJseSB3aXRoIGEgdXN1YWwgbWV0aG9kLCBlLmcuIERIQ1B2Ni4N
Cj4+IEFueXRoaW5nIHByb2JsZW1hdGljIHdpdGggdGhhdD8NCj4+IA0KPj4gDQo+Pj4gZS5nIHdl
IGNvdWxkIGRvOg0KPj4+IA0KPj4+IDwtLS0tLS0tLS0gNjQgLS0tLS0tLS0tLS0tPjwtLS0gMjQg
LS0tLS0tPjwtLS0tLSAzMiAtLS0tLS0tPjwtLTggPg0KPj4+ICstLS0tLS0tLS0tLS0tKy0tLS0t
LS0tKy0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0rLS0tKw0KPj4+IHwgSVB2
NiBwcmVmaXggfENFIGluZGV4fCBTIHwgMDAtMDAtNUUgICAgfCAgSVB2NCBhZGRyZXNzICB8IFBT
SUQgfA0KPj4+ICstLS0tLS0tLS0tLS0tKy0tLS0tLS0tKy0tLSstLS0rLS0tLS0tLS0tLS0tLS0t
LSstLS0tLS0rLS0tLS0rLS0tKw0KPj4+IA0KPj4+IHdlIGFsc28gbmVlZCB0byBoYW5kbGUgdGhl
IGNhc2Ugd2hlcmUgSVB2NiBwcmVmaXggKyBDRSBpbmRleCA+IDY0Lg0KPj4gDQo+PiBQbGVhc2Ug
ZXhwbGFpbiBtb3JlIHlvdXIgdW5kZXJzdGFuZGluZyBvZiB0aGlzIHJlcXVpcmVtZW50Lg0KPj4g
KEkgcGVyc29uYWxseSBiZWxpZXZlIHdlIHNob3VsZCBhdm9pZCB0aGF0LikNCj4+IA0KPj4+IEkg
c3VnZ2VzdCB3ZSB0aGVuIGp1c3QgcHV0IGFzIG11Y2ggYXMgdGhlIGludGVyZmFjZSBpZGVudGlm
aWVyIHRoYXQgd2lsbCBmaXQuDQo+PiANCj4+IA0KPj4gTWF5IEkgc3VnZ2VzdCB0aGF0LCB0byBi
ZSBtb3JlIGNvbnN0cnVjdGl2ZSwgeW91IGNvdWxkIGZpcnN0IGV4cHJlc3MgeW91ciBvYmplY3Rp
b25zIHRvIHRoZSBwcm9wb3NlZCB1bmlmaWVkIG1hcHBpbmcsIHJhdGhlciB0aGFuIG1ha2luZyBh
IG51bWJlciBvZiBuZXcgcHJvcG9zYWxzIHdob3NlIGp1c3RpZmljYXRpb25zIGFyZSBzb21ldGlt
ZXMgaGFyZCB0byB1bmRlcnN0YW5kLCANCj4+IA0KPj4gQ2hlZXJzLA0KPj4gUkQgDQo+PiANCj4+
IA0KPj4+IA0KPj4+IGNoZWVycywNCj4+PiBPbGUNCj4+PiANCj4+PiANCj4+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBTb2Z0d2lyZXMgbWFpbGlu
ZyBsaXN0DQo+PiBTb2Z0d2lyZXNAaWV0Zi5vcmcNCj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vc29mdHdpcmVzDQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPj4gU29mdHdpcmVzIG1haWxpbmcgbGlzdA0KPj4gU29mdHdp
cmVzQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Nv
ZnR3aXJlcw0KPiANCg0K

From despres.remi@laposte.net  Wed Oct 12 02:57:02 2011
Return-Path: <despres.remi@laposte.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 06BB321F8B62 for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 02:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.503
X-Spam-Level: 
X-Spam-Status: No, score=-1.503 tagged_above=-999 required=5 tests=[AWL=0.446,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sZa6GSto0O2S for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 02:57:01 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.118]) by ietfa.amsl.com (Postfix) with ESMTP id 73A6321F8B56 for <softwires@ietf.org>; Wed, 12 Oct 2011 02:57:01 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2503.sfr.fr (SMTP Server) with ESMTP id 4CBE6700004F for <softwires@ietf.org>; Wed, 12 Oct 2011 11:57:00 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2503.sfr.fr (SMTP Server) with ESMTP id 34F7370000BA for <softwires@ietf.org>; Wed, 12 Oct 2011 11:56:57 +0200 (CEST)
X-SFR-UUID: 20111012095700217.34F7370000BA@msfrf2503.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 12 Oct 2011 11:56:57 +0200
Message-Id: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net>
To: Softwires WG <softwires@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [Softwires] Unifying Double Translation and Encapsulation for 4rd (4rd-U)
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, 12 Oct 2011 09:57:02 -0000

Hello all,

The following draft has just been posted:
tools.ietf.org/html/draft-despres-softwire-4rd-u-00.

Hope it will be useful for your continuing work on stateless solutions =
in Softwire.

Clarification questions are most welcome.

Regards,
RD

From phdgang@gmail.com  Wed Oct 12 08:26:23 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 089F321F8BA0 for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 08:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNWwARHJg158 for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 08:26:22 -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 B4E0A21F8B98 for <softwires@ietf.org>; Wed, 12 Oct 2011 08:26:21 -0700 (PDT)
Received: by wyg24 with SMTP id 24so933072wyg.31 for <softwires@ietf.org>; Wed, 12 Oct 2011 08:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=5fyI0Etb6KzQZhZ73df6UZUGcXovDwFPhFxccMuDE6U=; b=mm2iqlsJXxiLNaTOlxNHm+TNprdg0KLW2F1DqLw9icrXLNdJ+oTOvVA7K1UW0UCOMk HJjxdlBk5dosYXrZk2G7Wcs2F52kAzfzn2XHVxBTymPt3J5Wz8kHYrIrIfItutLRGCcg YxIpMcN2NmIu2wGCY8vZV4K694kmG3f+9/ff8=
MIME-Version: 1.0
Received: by 10.216.159.129 with SMTP id s1mr2750322wek.3.1318433179522; Wed, 12 Oct 2011 08:26:19 -0700 (PDT)
Received: by 10.180.84.161 with HTTP; Wed, 12 Oct 2011 08:26:19 -0700 (PDT)
Date: Wed, 12 Oct 2011 23:26:19 +0800
Message-ID: <CAM+vMETWJBAaJBCJvMffa6aRcXMKzae9bWk=VT8Zt-+vAkuHJg@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: softwires <softwires@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Softwires] Design Principles of a Unified Address Format for 4v6
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, 12 Oct 2011 15:26:23 -0000

Dear all,

For 4v6 unified address design, people have actually discussed that
for quite long time on the mailing list.
We would like to wrap some thoughts up to contribute some ideas from
practical deployment point of view. Below is the proposed draft. Hope
that could help the discussion.

http://www.ietf.org/internet-drafts/draft-chen-softwire-4v6-add-format-00.txt

Many thanks

Gang

From sarikaya2012@gmail.com  Wed Oct 12 10:03:14 2011
Return-Path: <sarikaya2012@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 7BD6D21F8C67 for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 10:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level: 
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j78F4NODM84n for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 10:03:14 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id ED67D21F8C5B for <softwires@ietf.org>; Wed, 12 Oct 2011 10:03:12 -0700 (PDT)
Received: by ywm3 with SMTP id 3so252198ywm.31 for <softwires@ietf.org>; Wed, 12 Oct 2011 10:03:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ivjAjLfd9gPjOhCda8a4NJAirBVLFkGO+ktJTemJ0+Y=; b=uO9zbwKHZ2MBpsLusP77i2/wtGNJBCy+aA7XSmr9kxuVCZghcaW2zIpCPJ6w3wWCDQ kWheWTcxJECnnELuV/qRSHBOhepvs+1VZEueyf+mikI4SuAsaZCs2KwhSXPL64sbRko8 PIc1QjMBphYkpEdb3OYJFmpA9D5IwlCVxlXSQ=
MIME-Version: 1.0
Received: by 10.236.131.37 with SMTP id l25mr37514191yhi.76.1318438992594; Wed, 12 Oct 2011 10:03:12 -0700 (PDT)
Received: by 10.236.108.180 with HTTP; Wed, 12 Oct 2011 10:03:12 -0700 (PDT)
In-Reply-To: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net>
References: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net>
Date: Wed, 12 Oct 2011 12:03:12 -0500
Message-ID: <CAC8QAceVfkjN9CoCzQFhCdo4vBrz7Svoa3MYJOJ6032BODnXiA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=20cf3010e9abcfc8a504af1cffc0
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Unifying Double Translation and Encapsulation for 4rd (4rd-U)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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: Wed, 12 Oct 2011 17:03:14 -0000

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

This is interesting proposal in favor of double translation.

Regards,

Behcet

On Wed, Oct 12, 2011 at 4:56 AM, R=E9mi Despr=E9s <despres.remi@laposte.net=
>wrote:

> Hello all,
>
> The following draft has just been posted:
> tools.ietf.org/html/draft-despres-softwire-4rd-u-00.
>
> Hope it will be useful for your continuing work on stateless solutions in
> Softwire.
>
> Clarification questions are most welcome.
>
> Regards,
> RD
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

This is interesting proposal in favor of double translation.<br><br>Regards=
,<br><br>Behcet<br><br><div class=3D"gmail_quote">On Wed, Oct 12, 2011 at 4=
:56 AM, R=E9mi Despr=E9s <span dir=3D"ltr">&lt;<a href=3D"mailto:despres.re=
mi@laposte.net">despres.remi@laposte.net</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;">Hello all,<br>
<br>
The following draft has just been posted:<br>
<a href=3D"http://tools.ietf.org/html/draft-despres-softwire-4rd-u-00" targ=
et=3D"_blank">tools.ietf.org/html/draft-despres-softwire-4rd-u-00</a>.<br>
<br>
Hope it will be useful for your continuing work on stateless solutions in S=
oftwire.<br>
<br>
Clarification questions are most welcome.<br>
<br>
Regards,<br>
RD<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>
</blockquote></div><br>

--20cf3010e9abcfc8a504af1cffc0--

From jacni@jacni.com  Wed Oct 12 19:08:08 2011
Return-Path: <jacni@jacni.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 773EB21F8A7B for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 19:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.721
X-Spam-Level: 
X-Spam-Status: No, score=-1.721 tagged_above=-999 required=5 tests=[AWL=0.566,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rLvcthaMn0sM for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 19:08:07 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id A255A21F8A4E for <softwires@ietf.org>; Wed, 12 Oct 2011 19:08:07 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 4B0893800B7 for <softwires@ietf.org>; Wed, 12 Oct 2011 22:08:06 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id B6B26340106 for <softwires@ietf.org>; Thu, 13 Oct 2011 10:08:02 +0800 (CST)
Received: from [172.19.37.110] (unknown [221.11.61.247]) by app (Coremail) with SMTP id +AWowJBb5wX6R5ZOmsAZAA--.34139S2; Thu, 13 Oct 2011 10:07:57 +0800 (CST)
Message-ID: <4E964863.4060702@jacni.com>
Date: Thu, 13 Oct 2011 10:09:39 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: sarikaya@ieee.org
References: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net> <CAC8QAceVfkjN9CoCzQFhCdo4vBrz7Svoa3MYJOJ6032BODnXiA@mail.gmail.com>
In-Reply-To: <CAC8QAceVfkjN9CoCzQFhCdo4vBrz7Svoa3MYJOJ6032BODnXiA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010502040408070202030107"
X-CM-TRANSID: +AWowJBb5wX6R5ZOmsAZAA--.34139S2
X-Coremail-Antispam: 1UD129KBjvdXoWruFyDWrWDWw48Gw1UJr1rtFb_yoWfCwb_Cr 4xWw18Zr1UA3yUKay8tFyDtrnxZrWUWr1jy34UA347ur1UArn8tws3XrWfWw15GryUCr1D Grn5GryYka45GjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUj5kYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF 6F4UM7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1ln4vEF7Iv6F18KV Aqrcv_GVWUtr1rJF1ln4vEIxkG6c02xx0F6c8GOVWUtr18Jw1lnx0Ec2IEnICE548m6r1D JrWUZwAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64 vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxk0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2Ij 64vIr41l4IxY624lx4CE17CEb7AF67AKxVWUAVWUtwCIc40Y0x0EwIxGrbIYCTnIWIevJa 73UjIFyTuYvjxU2_OzDUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQIAEko7lOkzYgAAsM
Cc: Softwires WG <softwires@ietf.org>, Behcet Sarikaya <sarikaya2012@gmail.com>
Subject: Re: [Softwires] Unifying Double Translation and Encapsulation for 4rd (4rd-U)
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, 13 Oct 2011 02:08:08 -0000

This is a multi-part message in MIME format.
--------------010502040408070202030107
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Re-,

Yes maybe, to some extent. If accepted, the address format, even for 
CE-BR is unified as well.


Cheers,
Jacni

On 10/13/2011 1:03 AM, Behcet Sarikaya wrote:
> This is interesting proposal in favor of double translation.
>
> Regards,
>
> Behcet
>
> On Wed, Oct 12, 2011 at 4:56 AM, Rémi Després 
> <despres.remi@laposte.net <mailto:despres.remi@laposte.net>> wrote:
>
>     Hello all,
>
>     The following draft has just been posted:
>     tools.ietf.org/html/draft-despres-softwire-4rd-u-00
>     <http://tools.ietf.org/html/draft-despres-softwire-4rd-u-00>.
>
>     Hope it will be useful for your continuing work on stateless
>     solutions in Softwire.
>
>     Clarification questions are most welcome.
>
>     Regards,
>     RD
>     _______________________________________________
>     Softwires mailing list
>     Softwires@ietf.org <mailto:Softwires@ietf.org>
>     https://www.ietf.org/mailman/listinfo/softwires
>
>
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

--------------010502040408070202030107
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">Re-,<br>
      <br>
      Yes maybe, to some extent</font>. If accepted, the address format,
    even for CE-BR is unified as well.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    On 10/13/2011 1:03 AM, Behcet Sarikaya wrote:
    <blockquote
cite="mid:CAC8QAceVfkjN9CoCzQFhCdo4vBrz7Svoa3MYJOJ6032BODnXiA@mail.gmail.com"
      type="cite">This is interesting proposal in favor of double
      translation.<br>
      <br>
      Regards,<br>
      <br>
      Behcet<br>
      <br>
      <div class="gmail_quote">On Wed, Oct 12, 2011 at 4:56 AM, R&eacute;mi
        Despr&eacute;s <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello all,<br>
          <br>
          The following draft has just been posted:<br>
          <a moz-do-not-send="true"
            href="http://tools.ietf.org/html/draft-despres-softwire-4rd-u-00"
            target="_blank">tools.ietf.org/html/draft-despres-softwire-4rd-u-00</a>.<br>
          <br>
          Hope it will be useful for your continuing work on stateless
          solutions in Softwire.<br>
          <br>
          Clarification questions are most welcome.<br>
          <br>
          Regards,<br>
          RD<br>
          _______________________________________________<br>
          Softwires mailing list<br>
          <a moz-do-not-send="true" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
          <a moz-do-not-send="true"
            href="https://www.ietf.org/mailman/listinfo/softwires"
            target="_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Softwires mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a>
</pre>
    </blockquote>
  </body>
</html>

--------------010502040408070202030107--


From satoru.matsushima@gmail.com  Wed Oct 12 22:43:06 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 8EB3221F8ADC for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 22:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.412
X-Spam-Level: 
X-Spam-Status: No, score=-3.412 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wR5WM5wssC1B for <softwires@ietfa.amsl.com>; Wed, 12 Oct 2011 22:43:05 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id B844521F8ACA for <softwires@ietf.org>; Wed, 12 Oct 2011 22:43:05 -0700 (PDT)
Received: by iabn5 with SMTP id n5so637105iab.31 for <softwires@ietf.org>; Wed, 12 Oct 2011 22:43:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=wEMJEJMfdvazWxpv5Msfx3/oQdcKne/tI+cJUqjflVw=; b=G0ohWJcTi73kvRUjsZoTRVl1+dJN2biTX9Vf4kDewtL1oTN73jl089HNePRVSl5SoB jMhvAbqXzrzhkZgZD5mG9ES+1H8O+qd0+HcuiWHsb/ykIrrC7Eqi3bd2mvPhUOtXtcLQ rxaGQkNhlrFYTZdEDbVQy7fe7yz9Gzjw5ggdc=
Received: by 10.42.144.198 with SMTP id c6mr4081631icv.45.1318484585376; Wed, 12 Oct 2011 22:43:05 -0700 (PDT)
Received: from [10.201.83.217] ([202.45.12.174]) by mx.google.com with ESMTPS id el2sm11303864ibb.10.2011.10.12.22.43.02 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Oct 2011 22:43:04 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=utf-8
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net>
Date: Thu, 13 Oct 2011 14:43:00 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <1333CAE5-35B8-449A-AA70-306F408BEC15@gmail.com>
References: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net>
To: =?utf-8?Q?R=C3=A9mi_Despr=C3=A9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1244.3)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Unifying Double Translation and Encapsulation for 4rd (4rd-U)
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, 13 Oct 2011 05:43:06 -0000

Hi Remi,

It seems far from to be unified _packet_ format. it doesn't support =
diff-serv tunneling model, pipe and short-pipe.

cheers,
--satoru

On 2011/10/12, at 18:56, R=C3=A9mi Despr=C3=A9s wrote:

> Hello all,
>=20
> The following draft has just been posted:
> tools.ietf.org/html/draft-despres-softwire-4rd-u-00.
>=20
> Hope it will be useful for your continuing work on stateless solutions =
in Softwire.
>=20
> Clarification questions are most welcome.
>=20
> Regards,
> RD
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From despres.remi@laposte.net  Thu Oct 13 02:06:16 2011
Return-Path: <despres.remi@laposte.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 6F76A21F854F for <softwires@ietfa.amsl.com>; Thu, 13 Oct 2011 02:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level: 
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[AWL=0.382,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vnzdnvy5oDKN for <softwires@ietfa.amsl.com>; Thu, 13 Oct 2011 02:06:16 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.22]) by ietfa.amsl.com (Postfix) with ESMTP id BAB4C21F8541 for <softwires@ietf.org>; Thu, 13 Oct 2011 02:06:15 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2301.sfr.fr (SMTP Server) with ESMTP id EAD5E700004E; Thu, 13 Oct 2011 11:06:13 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2301.sfr.fr (SMTP Server) with ESMTP id C3F1670000B5; Thu, 13 Oct 2011 11:06:08 +0200 (CEST)
X-SFR-UUID: 20111013090608802.C3F1670000B5@msfrf2301.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <B8DEB256-0585-4279-BC8F-96064B4FF606@employees.org>
Date: Thu, 13 Oct 2011 11:06:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A00A0B26-90FD-48FC-90CE-51FB0CCC7808@laposte.net>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <4E92A32C.30306@jacni.com> <B8DEB256-0585-4279-BC8F-96064B4FF606@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Internal routing based on the V octet can be easy
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, 13 Oct 2011 09:06:16 -0000

Le 10 oct. 2011 =E0 10:58, Ole Troan a =E9crit :

>>> The 4rd function examines ALL packets that reach the CE.
>>> It processes all those that have V in their destination addresses, =
and only those.
>>>=20
>> This is a big change to the current forwarding behavior of CPE =
devices, doable, but quite different from, for example, some =
encapsulation/decapsulation implementations.
>=20
> +1.
> doable in theory, but I share your concerns.

Well, it wasn't quite right to say, as I did, "the 4rd function examines =
ALL packets that reach the CE".
More exactly, with existing kernel architectures, the 4rd function =
should only see packets that have the V octet in their IPv6 =
destinations.

With Linux, it is feasible AFAIK as follows:
- Before submitting a received packet to the routing function, it is =
submitted to the Netfilter pre-routing function.=20
- Netfilter adds to the packet a mark, specific of 4rd, if it has the V  =
octet (mask + value).
- The routing function, duly configured, then sends packets that have =
this mark to the 4rd-function interface.=20
With BSD, the PF packet filter has a role similar to that of Netfilter.
(Thanks to Francis Dupont for providing this information, hopefully not =
damaged by my transcription.) =20

Useful capabilities of 4rd solutions SHOUDN'T therefore be abandoned for =
the unjustified fear that internal routing based on the V octet might be =
difficult.

Regards,
RD

  =20

From jacni@jacni.com  Thu Oct 13 02:07:40 2011
Return-Path: <jacni@jacni.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 2487221F8AE9 for <softwires@ietfa.amsl.com>; Thu, 13 Oct 2011 02:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.816
X-Spam-Level: 
X-Spam-Status: No, score=-1.816 tagged_above=-999 required=5 tests=[AWL=0.471,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Zdsjo89oOgN for <softwires@ietfa.amsl.com>; Thu, 13 Oct 2011 02:07:39 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 529B321F888A for <softwires@ietf.org>; Thu, 13 Oct 2011 02:07:38 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 9AE6D3800C1 for <softwires@ietf.org>; Thu, 13 Oct 2011 05:07:37 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id B5893860005 for <softwires@ietf.org>; Thu, 13 Oct 2011 17:07:35 +0800 (CST)
Received: from [172.22.109.126] (unknown [221.11.61.172]) by app (Coremail) with SMTP id +AWowJBbOAQzqpZOrisaAA--.26183S2; Thu, 13 Oct 2011 17:07:27 +0800 (CST)
Message-ID: <4E96AAA1.4010402@jacni.com>
Date: Thu, 13 Oct 2011 17:08:49 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Satoru Matsushima <satoru.matsushima@gmail.com>
References: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net> <1333CAE5-35B8-449A-AA70-306F408BEC15@gmail.com>
In-Reply-To: <1333CAE5-35B8-449A-AA70-306F408BEC15@gmail.com>
Content-Type: multipart/alternative; boundary="------------020503050904060405020200"
X-CM-TRANSID: +AWowJBbOAQzqpZOrisaAA--.26183S2
X-Coremail-Antispam: 1UD129KBjvdXoWruFyxWw1kuw4DXrWDAFWkWFg_yoWftrg_Cr 4xGw48Gr4UJrWjg3yftr95trnxZrW5Wr1jy34UAr1kZr1UAw1Dtws3GrW8Gw1UJryUJr1U Grn5GryYk34UGjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUj5kYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF 6F4UM7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1ln4vEF7Iv6F18KV Aqrcv_GVWUtr1rJF1ln4vEIxkG6c02xx0F6c8GOVWUtr18Jw1lnx0Ec2IEnICE548m6r1D JrWUZwAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64 vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxk0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2Ij 64vIr41l4IxY624lx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y0x0EwIxGrbIYCTnIWIevJa 73UjIFyTuYvjxUs0PSUUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQAAEko7lOl8ugAAsZ
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Unifying Double Translation and Encapsulation for 4rd (4rd-U)
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, 13 Oct 2011 09:07:40 -0000

This is a multi-part message in MIME format.
--------------020503050904060405020200
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

On 10/13/2011 1:43 PM, Satoru Matsushima wrote:
> Hi Remi,
>
> It seems far from to be unified _packet_ format. it doesn't support diff-serv tunneling model, pipe and short-pipe.
The type of service can be copied to the IPv6 header. Sorry, what are 
the pipe and short-pipe?


Cheers,
Jacni

> cheers,
> --satoru
>
> On 2011/10/12, at 18:56, Rémi Després wrote:
>
>> Hello all,
>>
>> The following draft has just been posted:
>> tools.ietf.org/html/draft-despres-softwire-4rd-u-00.
>>
>> Hope it will be useful for your continuing work on stateless solutions in Softwire.
>>
>> Clarification questions are most welcome.
>>
>> Regards,
>> RD
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

--------------020503050904060405020200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">Hi,</font><br>
    <br>
    On 10/13/2011 1:43 PM, Satoru Matsushima wrote:
    <blockquote
      cite="mid:1333CAE5-35B8-449A-AA70-306F408BEC15@gmail.com"
      type="cite">
      <pre wrap="">Hi Remi,

It seems far from to be unified _packet_ format. it doesn't support diff-serv tunneling model, pipe and short-pipe.
</pre>
    </blockquote>
    The type of service can be copied to the IPv6 header. Sorry, what
    are the pipe and short-pipe?<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
      cite="mid:1333CAE5-35B8-449A-AA70-306F408BEC15@gmail.com"
      type="cite">
      <pre wrap="">
cheers,
--satoru

On 2011/10/12, at 18:56, R&eacute;mi Despr&eacute;s wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">Hello all,

The following draft has just been posted:
tools.ietf.org/html/draft-despres-softwire-4rd-u-00.

Hope it will be useful for your continuing work on stateless solutions in Softwire.

Clarification questions are most welcome.

Regards,
RD
_______________________________________________
Softwires mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a>
</pre>
      </blockquote>
      <pre wrap="">
_______________________________________________
Softwires mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a>
</pre>
    </blockquote>
  </body>
</html>

--------------020503050904060405020200--


From ichiroumakino@gmail.com  Thu Oct 13 02:08:18 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 39A1021F8B28 for <softwires@ietfa.amsl.com>; Thu, 13 Oct 2011 02:08:18 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F1eSL8u2wu1A for <softwires@ietfa.amsl.com>; Thu, 13 Oct 2011 02:08:16 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8627021F8AE9 for <softwires@ietf.org>; Thu, 13 Oct 2011 02:08:16 -0700 (PDT)
Received: by wwf22 with SMTP id 22so946707wwf.13 for <softwires@ietf.org>; Thu, 13 Oct 2011 02:08:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=MMARSnZD/1nsg/CZFMWdWKh57Di41WRASL28dAx1UtY=; b=pGB+/8w//uIExv/v3DzKIXYvU5gGfOQUMvheoSRhoGbapl3V222ZUBYJYKMMQYYdw4 wdp9SKRZEAhschC/1zNeX468GEk05kb9g1irg1nlJeBQ759rGgFYItTie6I9TCARaj0Z g3Madt7+hYoh8xISO9gPmafrLGOr/dOZYT31U=
Received: by 10.216.229.144 with SMTP id h16mr3667524weq.31.1318496895459; Thu, 13 Oct 2011 02:08:15 -0700 (PDT)
Received: from dhcp-osl-vl300-64-103-53-235.cisco.com (dhcp-osl-vl300-64-103-53-235.cisco.com. [64.103.53.235]) by mx.google.com with ESMTPS id fy13sm4754056wbb.18.2011.10.13.02.08.14 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Oct 2011 02:08:14 -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: <A00A0B26-90FD-48FC-90CE-51FB0CCC7808@laposte.net>
Date: Thu, 13 Oct 2011 11:08:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A79250C9-A9E8-4B1E-9919-6A8AE5C335A9@employees.org>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAH3bfACp_xvzotgrAhBrYhZ9ki47kbBVb-vmSsRtOOoyXxRSrA@mail.gmail.com> <10DF6CE6-394E-4FC9-BB80-9F24D4D2634B@laposte.net> <4E9065BD.3050001@jacni.com> <2904870A-866E-4093-8754-3D75510B82AA@laposte.net> <4E92A32C.30306@jacni.com> <B8DEB256-0585-4279-BC8F-96064B4FF606@employees.org> <A00A0B26-90FD-48FC-90CE-51FB0CCC7808@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Internal routing based on the V octet can be easy
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, 13 Oct 2011 09:08:18 -0000

Remi,

>>>> The 4rd function examines ALL packets that reach the CE.
>>>> It processes all those that have V in their destination addresses, =
and only those.
>>>>=20
>>> This is a big change to the current forwarding behavior of CPE =
devices, doable, but quite different from, for example, some =
encapsulation/decapsulation implementations.
>>=20
>> +1.
>> doable in theory, but I share your concerns.
>=20
> Well, it wasn't quite right to say, as I did, "the 4rd function =
examines ALL packets that reach the CE".
> More exactly, with existing kernel architectures, the 4rd function =
should only see packets that have the V octet in their IPv6 =
destinations.
>=20
> With Linux, it is feasible AFAIK as follows:
> - Before submitting a received packet to the routing function, it is =
submitted to the Netfilter pre-routing function.=20
> - Netfilter adds to the packet a mark, specific of 4rd, if it has the =
V  octet (mask + value).
> - The routing function, duly configured, then sends packets that have =
this mark to the 4rd-function interface.=20
> With BSD, the PF packet filter has a role similar to that of =
Netfilter.
> (Thanks to Francis Dupont for providing this information, hopefully =
not damaged by my transcription.) =20
>=20
> Useful capabilities of 4rd solutions SHOUDN'T therefore be abandoned =
for the unjustified fear that internal routing based on the V octet =
might be difficult.

regardless of implementation, your proposal does add extra processing =
cycles for _all_ IPv6 packets to the site.

cheers,
Ole=

From bingxuere@gmail.com  Thu Oct 13 07:03:55 2011
Return-Path: <bingxuere@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 15B7921F8997 for <softwires@ietfa.amsl.com>; Thu, 13 Oct 2011 07:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[AWL=0.987,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5lpyHUZZpqUv for <softwires@ietfa.amsl.com>; Thu, 13 Oct 2011 07:03:53 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3305721F8AB8 for <softwires@ietf.org>; Thu, 13 Oct 2011 07:03:53 -0700 (PDT)
Received: by qyk32 with SMTP id 32so30223qyk.10 for <softwires@ietf.org>; Thu, 13 Oct 2011 07:03:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=/W5Ph57seO9kaO9+/QM6m9JPXlto+IgEWeFBY7dGZHU=; b=mmz/cNcWIosPXnEIY0PIb9lSW8EvsVyRFFvkYeLDy/POoH1ZsfF9Z1dkcd424FJcbj 4k0xXnRIXIx7sLU5W6vRkY9WPiH9y3enoIQELV2h2t7dpzARkIF22QLzGjO6AmHNl21i 2wRqvsMMJ8tHaclkm33irdxnwLzeMgldkmKus=
Received: by 10.42.155.133 with SMTP id u5mr7796817icw.8.1318514631158; Thu, 13 Oct 2011 07:03:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Thu, 13 Oct 2011 07:03:31 -0700 (PDT)
In-Reply-To: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05767E7E@SZXEML510-MBS.china.huawei.com>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <16C872EF-F79E-4FD8-89B9-21B50129BA70@employees.org> <2118E521-F0CC-46F3-9F63-0EC6893326C6@laposte.net> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA0576663D@SZXEML510-MBS.china.huawei.com> <F0571321-3F33-49DE-9350-1060AEF1532F@gmail.com> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05766BB8@SZXEML510-MBS.china.huawei.com> <77E5DB2B-70A2-4797-AE89-5D6A5D8E514F@gmail.com> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA05767E7E@SZXEML510-MBS.china.huawei.com>
From: Qiong <bingxuere@gmail.com>
Date: Thu, 13 Oct 2011 22:03:31 +0800
Message-ID: <CAH3bfADek8f9ENaaHf9my8QKH70P5OCtHnMkWHpgEB758-P2-g@mail.gmail.com>
To: Leaf yeh <leaf.y.yeh@huawei.com>
Content-Type: multipart/alternative; boundary=90e6ba21241b38aa9904af2e9ca3
Cc: Softwires-wg <softwires@ietf.org>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 13 Oct 2011 14:03:55 -0000

--90e6ba21241b38aa9904af2e9ca3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Leaf:

On Wed, Oct 12, 2011 at 3:24 PM, Leaf yeh <leaf.y.yeh@huawei.com> wrote:

> Satoru -> I think we could have it.
> Tetsuya Murakami -> the decapsulation could be done for the packet having
> the tunnel end-point address as the destination or having the specific IP=
v6
> prefix as the destination.
>
> Does that mean BR needs to inject a route pointing to the BR subnet prefi=
x,
> and using one interface address of BR as the next-hop of this prefix in t=
he
> route? That means routes can direct the packets go to the right interface=
 of
> the BR, right?
>
> Yes. In case of using the specific BR IPv6 prefix, BR needs to inject a
routing and identifying with one interface as the next-hop. And this kind o=
f
prefix can be distributed in a similar way of RFC6334.

>
>
 Best Regards,
> Leaf
>
>
> -----Original Message-----
> From: Satoru Matsushima [mailto:satoru.matsushima@gmail.com]
> Sent: Tuesday, October 11, 2011 7:25 PM
> To: Leaf yeh
> Cc: Satoru Matsushima; R=C3=A9mi Despr=C3=A9s; Ole Troan; Softwires-wg;
> fine_sz@huawei.com
> Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulati=
on
> and double-translation
>
> On 2011/10/11, at 20:00, Leaf yeh wrote:
>
> >> Remi - >> A Destination address from a CE to the outside IPv4 Internet
> is:
> >>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> >>>> +--------------------------+----+---------------+------------+---+
> >>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
> >>>> +--------------------------+----+---------------+------------+---+
> > Leaf -> In fact, I doubts we could have the same address mapping for bo=
th
> tunnel and translation. Supposed the address of tunnel end-points is
> preferred to be fixed, but the address for the translation could be
> variable.
> > Satoru -> I think we could have it.
> >
> > What is the definition of the IPv4 address in the above format? Is it t=
he
> destination IPv4 address of any hosts outside 4rd IPv4 domain in the
> internet?
>
> I believe that the embedded IPv4 address should be an IPv4 address of a
> host on outside the domain.
>
> cheers,
> --satoru
>
> >
> >
> > Best Regards,
> > Leaf
> >
> >
> > -----Original Message-----
> > From: Satoru Matsushima [mailto:satoru.matsushima@gmail.com]
> > Sent: Tuesday, October 11, 2011 4:30 PM
> > To: Leaf yeh
> > Cc: Satoru Matsushima; R=C3=A9mi Despr=C3=A9s; Ole Troan; Softwires-wg;
> fine_sz@huawei.com
> > Subject: Re: [Softwires] Proposed Unified Address Mapping for
> encapsulation and double-translation
> >
> > Leaf, thanks for the summary.
> >
> > On 2011/10/10, at 20:34, Leaf yeh wrote:
> >
> >> Remi - >> a1- If the CE has an exclusive or shared IPv4 address:
> >>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
> >>>> +-------------+--------+---+---+----------------+------+-----+---+
> >>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
> >>>> +-------------+--------+---+---+----------------+------+-----+---+
> >> Ole - > putting the IPv4 address / port information at the end of the
> interface identifier will allow for > /64 support. > what's the L?
> >> Remi - Don't see what you found unclear.
> >>
> >>
> >> Question: Supposed the question is on the last field, named 'L', in th=
e
> new address format.
> >>
> >
> > Since Remi's draft doesn't specify 'CE IPv6 prefix length', IPv6 prefix
> can't be self delimiting to extract IPv4 address and port-set ID in the c=
ase
> of double translation. That's my understanding. Is that correct?
> > As '4rd-a', and 4via6(draft-murakami-softwire-4v6-translation), the 'L'
> bits are not necessary because 'CE IPv6 prefix length' is defined through=
 a
> domain, instead of 'L'.
> >
> >
> >>
> >> Remi - >> A Destination address from a CE to the outside IPv4 Internet
> is:
> >>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> >>>> +--------------------------+----+---------------+------------+---+
> >>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
> >>>> +--------------------------+----+---------------+------------+---+
> >> Ole - this is a big change for encapsulation, where prior to this
> encapsulation means sending to a single destination.
> >> Remi - Copying an available IPv4 address at a fixed place isn't IMHO a
> "big change".
> >>
> >>
> >> Concern: Supposed the replacement of the 1st 64bits of the BR address
> with a subnet prefix is not for the tunnel case if the field of IPv4 addr=
ess
> can be variable, right?
> >
> > I think that it could be a case where the BR address with a subnet pref=
ix
> for the tunnel case. My concern rather than the BR address is that a CE
> should pick packets up which have 'V' in IID, even destined prefixes are
> delegated to nodes which are behind of the CE.
> >
> >
> >>
> >> In fact, I doubts we could have the same address mapping for both tunn=
el
> and translation. Supposed the address of tunnel end-points is preferred t=
o
> be fixed, but the address for the translation could be variable.
> >>
> >
> > I think we could have it.
> >
> > cheers,
> > --satoru
> >
> >
> >>
> >> Best Regards,
> >> Leaf
> >>
> >>
> >> -----Original Message-----
> >> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] O=
n
> Behalf Of R=C3=A9mi Despr=C3=A9s
> >> Sent: Thursday, October 06, 2011 6:07 PM
> >> To: Ole Troan
> >> Cc: Softwires-wg
> >> Subject: Re: [Softwires] Proposed Unified Address Mapping for
> encapsulation and double-translation
> >>
> >>
> >> Le 6 oct. 2011 =C3=A0 18:47, Ole Troan a =C3=A9crit :
> >>
> >>> Remi,
> >>>
> >>> [...]
> >>>
> >>>> 2.
> >>>> (a)
> >>>> The IPv6 Source address of an IPv4 packet from a CE is:
> >>>>
> >>>> a1- If the CE has an exclusive or shared IPv4 address:
> >>>>
> >>>> <--------- 64 ------------><8 ><------ L >=3D 32 -------><48-L><8 >
> >>>> +-------------+--------+---+---+----------------+------+-----+---+
> >>>> | IPv6 prefix |CE index| 0 | V |  IPv4 address  | PSID |  0  | L |
> >>>> +-------------+--------+---+---+----------------+------+-----+---+
> >>>
> >>> putting the IPv4 address / port information at the end of the interfa=
ce
> identifier will allow for > /64 support.
> >>
> >> Could you explain more the requirement you have in mind?
> >>
> >>> what's the L?
> >>
> >> On the picture, L is 32 bits + Length(PSID).
> >> Don't see what you found unclear.
> >>
> >>>
> >>> you suggest that the first subnet of an allocation should be used for
> this purpose.
> >>
> >> Did I do this?
> >> Please explain because that's not, IMHO,  something to be done.
> >>
> >>> the first subnet is convenient to use for e.g. manual addressing (sin=
ce
> it allows the :: short hand).
> >>> I do wonder if this has to be provisioned. e.g. some deployments may
> use the first subnet for the link between
> >>> CE and PE. (i.e. a /56 - 1 using the PD exclude option is used).
> >>
> >> See just above.
> >>
> >>>
> >>>> a2- If the CE has an IPv4 prefix:
> >>>>
> >>>> <--------- 64 ------------><8 ><-- L < 32 --><--- 48-L -----><8 >
> >>>> +-------------+--------+---+---+-------------+---------------+---+
> >>>> | IPv6 prefix |CE index| 0 | V | IPv4 prefix |         0     | L |
> >>>> +-------------+--------+---+---+-------------+---------------+---+
> >>>>
> >>>> (b)
> >>>> V is the mark that characterizes IPv6 packets that are in reality IP=
v4
> packets.
> >>>> Its value differs from any permitted value of this octet in IPv6 IID=
s
>  (ref RFC 4291).
> >>>>
> >>>> It is understood that, if double Translation coexists with single
> translation, concerned ISPs may notify their CEs to use the U octet of RF=
C
> 6052 instead of V.
> >>>>
> >>>> An unambiguous mark is fortunately possible because currently
> permitted IIDs have in their first octet either bit6 =3D 0 (the "u" bit")=
, or
> bit6 =3D 1 and bit7=3D 0 (the "g" bit).
> >>>> With V having "u" =3D 1 (signifying Universal scope) AND "g" =3D 1,
> distinction is therefore deterministic.
> >>>>
> >>>> The proposed V is =3D 00000011.
> >>>> (With other values of this octet, other IID formats can be defined i=
n
> case some would be useful in the future.)
> >>>>
> >>>> Note that, if and when a consensus is reached in Softwire, an
> extension of RFC 4291 will have to be submitted to 6MAN.
> >>>
> >>> or rather IEEE?
> >>
> >> IMHO, IEEE has nothing to do with a marker that is purposely an escape
> mechanism from the modified EUI-64 format of RFC 4291.
> >>
> >>> I am not convinced that "V" is needed.
> >>
> >> The point is more, IMHO, whether you have an objection to it (and in
> this case which one).
> >> Reason is that we are working for a consensus, and several are satisfi=
ed
> with the explanation that there are use cases where it is useful, and non=
e
> where it is harmful.
> >>
> >>> you could even use the IANA OUI if pretty printing was required.
> >>
> >> The point is that it takes 32 bits which is too much to have IPv4
> address + PSID in the IID.
> >>
> >>
> >>>> (c)
> >>>> A Destination address from a CE to the outside IPv4 Internet is:
> >>>> <--------- 64 ------------>< 8 ><----   32 ----><--- 16 ----><8 >
> >>>> +--------------------------+----+---------------+------------+---+
> >>>> |     BR subnet prefix     | V  |  IPv4 address |      0     |32 |
> >>>> +--------------------------+----+---------------+------------+---+
> >>>
> >>> this is a big change for encapsulation, where prior to this
> encapsulation means sending to a single destination.
> >>
> >> Copying an available IPv4 address at a fixed place isn't IMHO a "big
> change".
> >>
> >>> if we also allow for a BR subnet prefix of /128 I'm OK with this (I
> think).
> >>
> >> I don't understand what you mean by "Subnet prefix of /128".
> >>
> >>
> >>>> Note that if double-translation CEs are notified to use U instead of
> V, the last octet becomes 0 per RFC  6052.
> >>>
> >>> how would a CE know if it was single or double translating?
> >>
> >> Presumably with a usual method, e.g. DHCPv6.
> >> Anything problematic with that?
> >>
> >>
> >>> e.g we could do:
> >>>
> >>> <--------- 64 ------------><--- 24 ------><----- 32 -------><--8 >
> >>> +-------------+--------+---+--------------------+------+-----+---+
> >>> | IPv6 prefix |CE index| S | 00-00-5E    |  IPv4 address  | PSID |
> >>> +-------------+--------+---+---+----------------+------+-----+---+
> >>>
> >>> we also need to handle the case where IPv6 prefix + CE index > 64.
> >>
> >> Please explain more your understanding of this requirement.
> >> (I personally believe we should avoid that.)
> >>
> >>> I suggest we then just put as much as the interface identifier that
> will fit.
> >>
> >>
> >> May I suggest that, to be more constructive, you could first express
> your objections to the proposed unified mapping, rather than making a num=
ber
> of new proposals whose justifications are sometimes hard to understand,
> >>
> >> Cheers,
> >> RD
> >>
> >>
> >>>
> >>> cheers,
> >>> Ole
> >>>
> >>>
> >> _______________________________________________
> >> Softwires mailing list
> >> Softwires@ietf.org
> >> https://www.ietf.org/mailman/listinfo/softwires
> >> _______________________________________________
> >> Softwires mailing list
> >> Softwires@ietf.org
> >> https://www.ietf.org/mailman/listinfo/softwires
> >
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

--90e6ba21241b38aa9904af2e9ca3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Leaf:<div><br><div class=3D"gmail_quote">On Wed, Oct 12, 2011 at 3:24 PM=
, Leaf yeh <span dir=3D"ltr">&lt;<a href=3D"mailto:leaf.y.yeh@huawei.com">l=
eaf.y.yeh@huawei.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
;">

<div class=3D"im">Satoru -&gt; I think we could have it.<br>
</div>Tetsuya Murakami -&gt; the decapsulation could be done for the packet=
 having the tunnel end-point address as the destination or having the speci=
fic IPv6 prefix as the destination.<br>
<br>
Does that mean BR needs to inject a route pointing to the BR subnet prefix,=
 and using one interface address of BR as the next-hop of this prefix in th=
e route? That means routes can direct the packets go to the right interface=
 of the BR, right?<br>


<div class=3D"im"><br></div></blockquote><div>Yes. In case of using the spe=
cific BR IPv6 prefix, BR needs to inject a routing and=C2=A0identifying wit=
h one interface as the next-hop. And this kind of prefix can be distributed=
 in a similar way of RFC6334.=C2=A0 =C2=A0=C2=A0</div>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im">=C2=A0</div></blockquote>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">

<div class=3D"im">
Best Regards,<br>
Leaf<br>
<br>
<br>
-----Original Message-----<br>
From: Satoru Matsushima [mailto:<a href=3D"mailto:satoru.matsushima@gmail.c=
om">satoru.matsushima@gmail.com</a>]<br>
</div><div><div></div><div class=3D"h5">Sent: Tuesday, October 11, 2011 7:2=
5 PM<br>
To: Leaf yeh<br>
Cc: Satoru Matsushima; R=C3=A9mi Despr=C3=A9s; Ole Troan; Softwires-wg; <a =
href=3D"mailto:fine_sz@huawei.com">fine_sz@huawei.com</a><br>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation=
 and double-translation<br>
<br>
On 2011/10/11, at 20:00, Leaf yeh wrote:<br>
<br>
&gt;&gt; Remi - &gt;&gt; A Destination address from a CE to the outside IPv=
4 Internet is:<br>
&gt;&gt;&gt;&gt; &lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- =C2=
=A0 32 ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;<br>
&gt;&gt;&gt;&gt; +--------------------------+----+---------------+---------=
---+---+<br>
&gt;&gt;&gt;&gt; | =C2=A0 =C2=A0 BR subnet prefix =C2=A0 =C2=A0 | V =C2=A0|=
 =C2=A0IPv4 address | =C2=A0 =C2=A0 =C2=A00 =C2=A0 =C2=A0 |32 |<br>
&gt;&gt;&gt;&gt; +--------------------------+----+---------------+---------=
---+---+<br>
&gt; Leaf -&gt; In fact, I doubts we could have the same address mapping fo=
r both tunnel and translation. Supposed the address of tunnel end-points is=
 preferred to be fixed, but the address for the translation could be variab=
le.<br>


&gt; Satoru -&gt; I think we could have it.<br>
&gt;<br>
&gt; What is the definition of the IPv4 address in the above format? Is it =
the destination IPv4 address of any hosts outside 4rd IPv4 domain in the in=
ternet?<br>
<br>
I believe that the embedded IPv4 address should be an IPv4 address of a hos=
t on outside the domain.<br>
<br>
cheers,<br>
--satoru<br>
<br>
&gt;<br>
&gt;<br>
&gt; Best Regards,<br>
&gt; Leaf<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Satoru Matsushima [mailto:<a href=3D"mailto:satoru.matsushima@gm=
ail.com">satoru.matsushima@gmail.com</a>]<br>
&gt; Sent: Tuesday, October 11, 2011 4:30 PM<br>
&gt; To: Leaf yeh<br>
&gt; Cc: Satoru Matsushima; R=C3=A9mi Despr=C3=A9s; Ole Troan; Softwires-wg=
; <a href=3D"mailto:fine_sz@huawei.com">fine_sz@huawei.com</a><br>
&gt; Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsul=
ation and double-translation<br>
&gt;<br>
&gt; Leaf, thanks for the summary.<br>
&gt;<br>
&gt; On 2011/10/10, at 20:34, Leaf yeh wrote:<br>
&gt;<br>
&gt;&gt; Remi - &gt;&gt; a1- If the CE has an exclusive or shared IPv4 addr=
ess:<br>
&gt;&gt;&gt;&gt; &lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;------ L &g=
t;=3D 32 -------&gt;&lt;48-L&gt;&lt;8 &gt;<br>
&gt;&gt;&gt;&gt; +-------------+--------+---+---+----------------+------+--=
---+---+<br>
&gt;&gt;&gt;&gt; | IPv6 prefix |CE index| 0 | V | =C2=A0IPv4 address =C2=A0=
| PSID | =C2=A00 =C2=A0| L |<br>
&gt;&gt;&gt;&gt; +-------------+--------+---+---+----------------+------+--=
---+---+<br>
&gt;&gt; Ole - &gt; putting the IPv4 address / port information at the end =
of the interface identifier will allow for &gt; /64 support. &gt; what&#39;=
s the L?<br>
&gt;&gt; Remi - Don&#39;t see what you found unclear.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Question: Supposed the question is on the last field, named &#39;L=
&#39;, in the new address format.<br>
&gt;&gt;<br>
&gt;<br>
&gt; Since Remi&#39;s draft doesn&#39;t specify &#39;CE IPv6 prefix length&=
#39;, IPv6 prefix can&#39;t be self delimiting to extract IPv4 address and =
port-set ID in the case of double translation. That&#39;s my understanding.=
 Is that correct?<br>


&gt; As &#39;4rd-a&#39;, and 4via6(draft-murakami-softwire-4v6-translation)=
, the &#39;L&#39; bits are not necessary because &#39;CE IPv6 prefix length=
&#39; is defined through a domain, instead of &#39;L&#39;.<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Remi - &gt;&gt; A Destination address from a CE to the outside IPv=
4 Internet is:<br>
&gt;&gt;&gt;&gt; &lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- =C2=
=A0 32 ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;<br>
&gt;&gt;&gt;&gt; +--------------------------+----+---------------+---------=
---+---+<br>
&gt;&gt;&gt;&gt; | =C2=A0 =C2=A0 BR subnet prefix =C2=A0 =C2=A0 | V =C2=A0|=
 =C2=A0IPv4 address | =C2=A0 =C2=A0 =C2=A00 =C2=A0 =C2=A0 |32 |<br>
&gt;&gt;&gt;&gt; +--------------------------+----+---------------+---------=
---+---+<br>
&gt;&gt; Ole - this is a big change for encapsulation, where prior to this =
encapsulation means sending to a single destination.<br>
&gt;&gt; Remi - Copying an available IPv4 address at a fixed place isn&#39;=
t IMHO a &quot;big change&quot;.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Concern: Supposed the replacement of the 1st 64bits of the BR addr=
ess with a subnet prefix is not for the tunnel case if the field of IPv4 ad=
dress can be variable, right?<br>
&gt;<br>
&gt; I think that it could be a case where the BR address with a subnet pre=
fix for the tunnel case. My concern rather than the BR address is that a CE=
 should pick packets up which have &#39;V&#39; in IID, even destined prefix=
es are delegated to nodes which are behind of the CE.<br>


&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; In fact, I doubts we could have the same address mapping for both =
tunnel and translation. Supposed the address of tunnel end-points is prefer=
red to be fixed, but the address for the translation could be variable.<br>


&gt;&gt;<br>
&gt;<br>
&gt; I think we could have it.<br>
&gt;<br>
&gt; cheers,<br>
&gt; --satoru<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Best Regards,<br>
&gt;&gt; Leaf<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: <a href=3D"mailto:softwires-bounces@ietf.org">softwires-boun=
ces@ietf.org</a> [mailto:<a href=3D"mailto:softwires-bounces@ietf.org">soft=
wires-bounces@ietf.org</a>] On Behalf Of R=C3=A9mi Despr=C3=A9s<br>
&gt;&gt; Sent: Thursday, October 06, 2011 6:07 PM<br>
&gt;&gt; To: Ole Troan<br>
&gt;&gt; Cc: Softwires-wg<br>
&gt;&gt; Subject: Re: [Softwires] Proposed Unified Address Mapping for enca=
psulation and double-translation<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Le 6 oct. 2011 =C3=A0 18:47, Ole Troan a =C3=A9crit :<br>
&gt;&gt;<br>
&gt;&gt;&gt; Remi,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; [...]<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 2.<br>
&gt;&gt;&gt;&gt; (a)<br>
&gt;&gt;&gt;&gt; The IPv6 Source address of an IPv4 packet from a CE is:<br=
>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; a1- If the CE has an exclusive or shared IPv4 address:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;------ L &g=
t;=3D 32 -------&gt;&lt;48-L&gt;&lt;8 &gt;<br>
&gt;&gt;&gt;&gt; +-------------+--------+---+---+----------------+------+--=
---+---+<br>
&gt;&gt;&gt;&gt; | IPv6 prefix |CE index| 0 | V | =C2=A0IPv4 address =C2=A0=
| PSID | =C2=A00 =C2=A0| L |<br>
&gt;&gt;&gt;&gt; +-------------+--------+---+---+----------------+------+--=
---+---+<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; putting the IPv4 address / port information at the end of the =
interface identifier will allow for &gt; /64 support.<br>
&gt;&gt;<br>
&gt;&gt; Could you explain more the requirement you have in mind?<br>
&gt;&gt;<br>
&gt;&gt;&gt; what&#39;s the L?<br>
&gt;&gt;<br>
&gt;&gt; On the picture, L is 32 bits + Length(PSID).<br>
&gt;&gt; Don&#39;t see what you found unclear.<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; you suggest that the first subnet of an allocation should be u=
sed for this purpose.<br>
&gt;&gt;<br>
&gt;&gt; Did I do this?<br>
&gt;&gt; Please explain because that&#39;s not, IMHO, =C2=A0something to be=
 done.<br>
&gt;&gt;<br>
&gt;&gt;&gt; the first subnet is convenient to use for e.g. manual addressi=
ng (since it allows the :: short hand).<br>
&gt;&gt;&gt; I do wonder if this has to be provisioned. e.g. some deploymen=
ts may use the first subnet for the link between<br>
&gt;&gt;&gt; CE and PE. (i.e. a /56 - 1 using the PD exclude option is used=
).<br>
&gt;&gt;<br>
&gt;&gt; See just above.<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; a2- If the CE has an IPv4 prefix:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &lt;--------- 64 ------------&gt;&lt;8 &gt;&lt;-- L &lt; 3=
2 --&gt;&lt;--- 48-L -----&gt;&lt;8 &gt;<br>
&gt;&gt;&gt;&gt; +-------------+--------+---+---+-------------+------------=
---+---+<br>
&gt;&gt;&gt;&gt; | IPv6 prefix |CE index| 0 | V | IPv4 prefix | =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 | L |<br>
&gt;&gt;&gt;&gt; +-------------+--------+---+---+-------------+------------=
---+---+<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; (b)<br>
&gt;&gt;&gt;&gt; V is the mark that characterizes IPv6 packets that are in =
reality IPv4 packets.<br>
&gt;&gt;&gt;&gt; Its value differs from any permitted value of this octet i=
n IPv6 IIDs =C2=A0(ref RFC 4291).<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; It is understood that, if double Translation coexists with=
 single translation, concerned ISPs may notify their CEs to use the U octet=
 of RFC 6052 instead of V.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; An unambiguous mark is fortunately possible because curren=
tly permitted IIDs have in their first octet either bit6 =3D 0 (the &quot;u=
&quot; bit&quot;), or bit6 =3D 1 and bit7=3D 0 (the &quot;g&quot; bit).<br>
&gt;&gt;&gt;&gt; With V having &quot;u&quot; =3D 1 (signifying Universal sc=
ope) AND &quot;g&quot; =3D 1, distinction is therefore deterministic.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The proposed V is =3D 00000011.<br>
&gt;&gt;&gt;&gt; (With other values of this octet, other IID formats can be=
 defined in case some would be useful in the future.)<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Note that, if and when a consensus is reached in Softwire,=
 an extension of RFC 4291 will have to be submitted to 6MAN.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; or rather IEEE?<br>
&gt;&gt;<br>
&gt;&gt; IMHO, IEEE has nothing to do with a marker that is purposely an es=
cape mechanism from the modified EUI-64 format of RFC 4291.<br>
&gt;&gt;<br>
&gt;&gt;&gt; I am not convinced that &quot;V&quot; is needed.<br>
&gt;&gt;<br>
&gt;&gt; The point is more, IMHO, whether you have an objection to it (and =
in this case which one).<br>
&gt;&gt; Reason is that we are working for a consensus, and several are sat=
isfied with the explanation that there are use cases where it is useful, an=
d none where it is harmful.<br>
&gt;&gt;<br>
&gt;&gt;&gt; you could even use the IANA OUI if pretty printing was require=
d.<br>
&gt;&gt;<br>
&gt;&gt; The point is that it takes 32 bits which is too much to have IPv4 =
address + PSID in the IID.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; (c)<br>
&gt;&gt;&gt;&gt; A Destination address from a CE to the outside IPv4 Intern=
et is:<br>
&gt;&gt;&gt;&gt; &lt;--------- 64 ------------&gt;&lt; 8 &gt;&lt;---- =C2=
=A0 32 ----&gt;&lt;--- 16 ----&gt;&lt;8 &gt;<br>
&gt;&gt;&gt;&gt; +--------------------------+----+---------------+---------=
---+---+<br>
&gt;&gt;&gt;&gt; | =C2=A0 =C2=A0 BR subnet prefix =C2=A0 =C2=A0 | V =C2=A0|=
 =C2=A0IPv4 address | =C2=A0 =C2=A0 =C2=A00 =C2=A0 =C2=A0 |32 |<br>
&gt;&gt;&gt;&gt; +--------------------------+----+---------------+---------=
---+---+<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; this is a big change for encapsulation, where prior to this en=
capsulation means sending to a single destination.<br>
&gt;&gt;<br>
&gt;&gt; Copying an available IPv4 address at a fixed place isn&#39;t IMHO =
a &quot;big change&quot;.<br>
&gt;&gt;<br>
&gt;&gt;&gt; if we also allow for a BR subnet prefix of /128 I&#39;m OK wit=
h this (I think).<br>
&gt;&gt;<br>
&gt;&gt; I don&#39;t understand what you mean by &quot;Subnet prefix of /12=
8&quot;.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; Note that if double-translation CEs are notified to use U =
instead of V, the last octet becomes 0 per RFC =C2=A06052.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; how would a CE know if it was single or double translating?<br=
>
&gt;&gt;<br>
&gt;&gt; Presumably with a usual method, e.g. DHCPv6.<br>
&gt;&gt; Anything problematic with that?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; e.g we could do:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &lt;--------- 64 ------------&gt;&lt;--- 24 ------&gt;&lt;----=
- 32 -------&gt;&lt;--8 &gt;<br>
&gt;&gt;&gt; +-------------+--------+---+--------------------+------+-----+=
---+<br>
&gt;&gt;&gt; | IPv6 prefix |CE index| S | 00-00-5E =C2=A0 =C2=A0| =C2=A0IPv=
4 address =C2=A0| PSID |<br>
&gt;&gt;&gt; +-------------+--------+---+---+----------------+------+-----+=
---+<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; we also need to handle the case where IPv6 prefix + CE index &=
gt; 64.<br>
&gt;&gt;<br>
&gt;&gt; Please explain more your understanding of this requirement.<br>
&gt;&gt; (I personally believe we should avoid that.)<br>
&gt;&gt;<br>
&gt;&gt;&gt; I suggest we then just put as much as the interface identifier=
 that will fit.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; May I suggest that, to be more constructive, you could first expre=
ss your objections to the proposed unified mapping, rather than making a nu=
mber of new proposals whose justifications are sometimes hard to understand=
,<br>


&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; RD<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt; Ole<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Softwires mailing list<br>
&gt;&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Softwires mailing list<br>
&gt;&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;<br>
<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>
</div></div></blockquote></div><br></div>

--90e6ba21241b38aa9904af2e9ca3--

From ietf-ipr@ietf.org  Thu Oct 13 08:15:16 2011
Return-Path: <ietf-ipr@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 28B4F21F8BE9; Thu, 13 Oct 2011 08:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.347
X-Spam-Level: 
X-Spam-Status: No, score=-102.347 tagged_above=-999 required=5 tests=[AWL=0.252, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EMphCuzyCDq1; Thu, 13 Oct 2011 08:15:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1422921F8BE4; Thu, 13 Oct 2011 08:15:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: fbrockne@cisco.com, sgundave@cisco.com, sebastian.speicher@telekom.de, dward@juniper.net, 
X-Test-IDTracker: no
Message-ID: <20111013151501.24829.98700.idtracker@ietfa.amsl.com>
Date: Thu, 13 Oct 2011 08:15:01 -0700
X-Mailman-Approved-At: Thu, 13 Oct 2011 08:45:40 -0700
Cc: cuiyong@tsinghua.edu.cn, softwires@ietf.org, ipr-announce@ietf.org
Subject: [Softwires] IPR Disclosure: Huawei Technologies Co., Ltd's Statement about IPR related to	draft-ietf-softwire-gateway-init-ds-lite-05
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, 13 Oct 2011 15:15:16 -0000

Dear Frank Brockners, Sri Gundavelli, Sebastian Speicher, David Ward:

 An IPR disclosure that pertains to your Internet-Draft entitled "Gateway
Initiated Dual-Stack Lite Deployment" (draft-ietf-softwire-gateway-init-ds-=
lite)
was submitted to the IETF Secretariat on 2011-10-13 and has been posted on =
the
"IETF Page of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/1630/). The title of the IPR disclosure is
"Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-
softwire-gateway-init-ds-lite-05."");

The IETF Secretariat


From fibrib@gmail.com  Fri Oct 14 19:14:59 2011
Return-Path: <fibrib@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 ADDD721F8CD6 for <softwires@ietfa.amsl.com>; Fri, 14 Oct 2011 19:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4YDc1g2uq+gR for <softwires@ietfa.amsl.com>; Fri, 14 Oct 2011 19:14:58 -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 3A57021F8B5C for <softwires@ietf.org>; Fri, 14 Oct 2011 19:14:58 -0700 (PDT)
Received: by wyg24 with SMTP id 24so4027113wyg.31 for <softwires@ietf.org>; Fri, 14 Oct 2011 19:14:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=B7RhdOkdGWEMFDNJsn2u46tcP8UsbQZh3/R+CEhcB3k=; b=t+pwUqfmNR2gbtPeAc0Fg6CiTxWGVoXAvckNgCsDceAH80GAU3/XP/Zg7OljwvUclJ JkmMd44aPPR/HmlBYQv6E5ljc1hqxhBGQ2JVDp9WNUpdxKqYARyFqGW8x8t30a666w1L vq8RkHXRgHgGwlMZ2rh40xL9YfTJm3adB9TGg=
MIME-Version: 1.0
Received: by 10.216.198.146 with SMTP id v18mr497863wen.52.1318644897389; Fri, 14 Oct 2011 19:14:57 -0700 (PDT)
Received: by 10.216.17.200 with HTTP; Fri, 14 Oct 2011 19:14:57 -0700 (PDT)
In-Reply-To: <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com>
Date: Sat, 15 Oct 2011 11:14:57 +0900
Message-ID: <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>,  Softwires-wg <softwires@ietf.org>
Content-Type: multipart/alternative; boundary=0016e6d59e1bb19b4a04af4cf022
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 15 Oct 2011 02:14:59 -0000

--0016e6d59e1bb19b4a04af4cf022
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Remi and all,

a discussion on the address mapping in -01.txt, trying to fully understand
the design. comments are requested.

- what if there are two rules?

  suppose we have 192.32../12 (0xc0200000/12, i think it's not the 0x602 as
Leaf previously mentioned, ;-)
  and we also have 64.32../16 (0x40200000/16). we have a lot of CEs.

Q1. if we use the two as the Rule_IPv4_Prefix_A and _B, can we map them to =
a
single Rule_IPv6_Prefix?

    Rule IPv6 Prefix: 20010db        (2001:db0::/28)
    CE1 IPv4 address:     c02 98765         (192.41.135.101)
            CE1 PSID:              4
        CE1 CE index:         987654
---------------------------------------------------------------
(1)  CE1 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52)
    suppose we happen to have another CE somewhere else:

    Rule IPv6 Prefix: 20010db
    CE2 IPv4 address:    4020 9876          (64.32.152.118)
            CE2 PSID:             54
        CE2 CE index:         987654
---------------------------------------------------------------
(2)  CE2 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52)

ambiguity happens and packet encapsulated with the same CE IPv6 address
cannot be routed to the correct CE. therefore my answer to Q1, is NO, unles=
s
we carefully select IPv4 addresses for CEs with giving up to use some of
them, which have been so precious.

Q2. then it must fine as long as we map them to different Rule IPv6 Prefix.
(?)

    suppose CE1 is the same as (1). for 64.32../16, we use a longer stuff.
    however, there is a CE3:

  Rule IPv6 Prefix B: 20010db8       (2001:db8::/29)
    CE3 IPv4 address:    4020 1876   (64.32.24.118)
            CE3 PSID:             54
        CE3 CE index:         987654
---------------------------------------------------------------
(3)  CE3 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52, woops!)

ambiguity happens. then we may argue: using the ugly Rule_IPv6_Prefix_B is
the root of the problem! we have not to use a prefix covered by another.

Q3. what does the exclusiveness of Rule IPv6 Prefix mean?

    if we have 2001:da0::/28 for the Rule_IPv6_Prefix, everyone will be
happy. however, unfortunately, we have only one /28 IPv6 aggregate. then
what we have to do is splitting the /28 block into mutually exclusive piece=
s
of small blocks. in the above example, if we have the following rule table:

    Rule_IPv4_Prefix Rule_IPv6_Prefix
   -----------------------------------
    192.32../12      2001:db0::/29
    64.32../16       2001:db9::/29
   -----------------------------------

    then it will work fine within the /28 room in total. for 192.32../12, i=
f
the PSID is at least 4bit, then the *shortest* CE IPv6 prefix length is 29 =
+
(32 - 12) + 4 =3D 53 now, rather than 52 in the previous example. if we hav=
e
only or want to use only at most a /44 IPv6 prefix for the residual
deployment, for the above 2 IPv4 networks, we are not able to safely deploy
the CE prefix shorter than /64, no matter how we take the effort!

    Jacni once mentioned that if we have a /x IPv6 prefix while the
"philosophy" of address planning decides to have /y for each CE-delegated
network, then we can play the magic with the bits between the /x and the /y=
.
i would like to point out here, because of the exclusiveness requirement,
there is a hard limit for the power of the magic. if you have N IPv4
residual addresses, you must at least satisfy the condition:

    (4)     y - x >=3D log(N)

    when (4) is not true, cutting the rule into pieces does help almost
nothing. i said "almost" because there is really a little we can achieve:
there is really some IPv4 address seldom used for any routers,
like 192.32.1.0. however, excluding such sort of addresses from the mapping
scatters the mapping table into a huge number of /32-Rule_IPv4_Prefix and
making the table size even longer than today's IPv4 routing table.

just my 2 cents. execuse me if the humble calculation has any
misunderstanding, and please point out without hesitation.

best,
maoke


> 2011/9/22 R=E9mi Despr=E9s <despres.remi@laposte.net>:
>> Alain, all,
>>
>> We have just posted a new version of our I-D on the proposed 4rd Address
Mapping.
>> It is available at
>> www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt
>>
>> Our presentation will be based on THIS version, technically simpler than
version -00.
>> Major differences and their justifications will be briefly explained.
>>
>> Regards,
>> RD
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

<div><font face=3D"courier new,monospace">=A0</font></div><div><font face=
=3D"courier new,monospace">=A0</font></div><div><font face=3D"courier new,m=
onospace">hi Remi and all,</font></div><div><font face=3D"courier new,monos=
pace">=A0</font></div>
<div><font face=3D"courier new,monospace">a discussion on the address mappi=
ng in -01.txt, trying to fully understand the design. comments are requeste=
d. </font></div><div><font face=3D"courier new,monospace">=A0</font></div><=
div>
<font face=3D"courier new,monospace">- what if there are two rules? </font>=
</div><div><font face=3D"courier new,monospace">=A0</font></div><div><font =
face=3D"courier new,monospace">=A0 suppose we have 192.32../12 (0x<font col=
or=3D"#ff0000">c02</font>00000/12, i think it&#39;s not the 0x602 as Leaf p=
reviously mentioned, ;-)</font></div>
<div><font face=3D"courier new,monospace">=A0 and we also have 64.32../16 (=
0x<font color=3D"#ff6666">4020</font>0000/16). we have a lot of CEs. </font=
></div><div><font face=3D"courier new,monospace"></font>=A0</div><div><font=
 face=3D"courier new,monospace">Q1. if we use the two as the Rule_IPv4_Pref=
ix_A and _B, can we map them to a single Rule_IPv6_Prefix? </font></div>
<div><font face=3D"courier new,monospace"></font>=A0</div><div><font face=
=3D"courier new,monospace">=A0=A0=A0 Rule IPv6 Prefix:=A020010db=A0=A0=A0=
=A0=A0=A0=A0 (2001:db0::/28)</font></div><div><font face=3D"courier new,mon=
ospace">=A0=A0=A0 CE1 IPv4 address:=A0=A0=A0=A0 c02=A098765=A0=A0=A0=A0=A0=
=A0=A0=A0=A0(192.41.135.101)</font></div>
<div><font face=3D"courier new,monospace">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0CE1 PSID:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A04=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 </font></div><div><font face=3D"Courier New"=
>=A0=A0=A0=A0=A0=A0=A0 CE1 CE index:=A0=A0=A0=A0=A0=A0=A0=A0 987654</font><=
/div><font face=3D"Courier New"><div><font face=3D"Courier New">-----------=
----------------------------------------------------</font></div>
<div>(1)=A0 CE1 IPv6 prefix: 20010db=A0987654=A0(<font color=3D"#ff0000">20=
01:db9:8765:4000::/52</font>)</div></font><div><font face=3D"courier new,mo=
nospace"></font></div><font face=3D"courier new,monospace"><div><div><font =
face=3D"courier new,monospace">=A0=A0=A0 suppose we happen to have another =
CE somewhere else:</font></div>
<div>=A0</div><div><font face=3D"courier new,monospace">=A0=A0=A0 Rule IPv6=
 Prefix: 20010db</font></div></div></font><div><font face=3D"courier new,mo=
nospace">=A0=A0=A0 CE2 IPv4 address:=A0=A0=A0 4020=A09876=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0(64.32.152.118)</font></div><div>
<div><font face=3D"courier new,monospace">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
 CE2 PSID:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A054=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 </font></div><div><font face=3D"Courier New">=A0=
=A0=A0=A0=A0=A0=A0=A0CE2 CE index:=A0=A0=A0=A0=A0=A0=A0=A0=A0987654</font><=
/div><font face=3D"Courier New"><div><font face=3D"Courier New">-----------=
----------------------------------------------------</font></div>
<div>(2)=A0 CE2 IPv6 prefix: 20010db=A0987654 (<font color=3D"#ff9966">2001=
:db9:8765:4000::/52</font>)</div></font></div><div><font face=3D"courier ne=
w,monospace"></font>=A0</div><div><font face=3D"Courier New">ambiguity happ=
ens and=A0packet encapsulated=A0with the same CE IPv6 address cannot be rou=
ted to the correct CE. therefore my answer to Q1, is NO, </font><font face=
=3D"Courier New">unless we carefully select IPv4 addresses for CEs with giv=
ing up to use some of them, which have been so precious. </font></div>
<div><font face=3D"Courier New"></font>=A0</div><div><font face=3D"Courier =
New">Q2. then it must fine as long as we map them to <font color=3D"#ff0000=
">different</font> Rule IPv6 Prefix. (?)</font></div><div><font face=3D"cou=
rier new,monospace"></font>=A0</div>
<div><font face=3D"Courier New">=A0=A0=A0=A0suppose CE1 is the same as (1).=
 for 64.32../16, we use a longer stuff.</font></div><div><font face=3D"Cour=
ier New">=A0=A0=A0 however, there is a CE3:</font></div><div><font face=3D"=
Courier New"></font><font face=3D"courier new,monospace">=A0</font></div>
<font face=3D"courier new,monospace"><div><div><div><font face=3D"courier n=
ew,monospace">=A0=A0Rule IPv6 Prefix B: 20010db<font color=3D"#ff0000">8</f=
ont>=A0=A0=A0=A0=A0=A0 (2001:db8::/<font color=3D"#ff0000">29</font>)</font=
></div></div></div></font><div>
<div><font face=3D"courier new,monospace">=A0=A0=A0 CE3 IPv4 address:   =A0=
=A0 4020 <font color=3D"#ff0000">1</font><font color=3D"#000000">876</font>=
=A0=A0=A0(64.32.24.118)</font></div><div><div><font face=3D"courier new,mon=
ospace">=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0           CE3 PSID:=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A054=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
</font></div>
<div><font face=3D"Courier New">=A0=A0=A0=A0=A0=A0=A0=A0CE3 CE index:=A0=A0=
=A0=A0=A0=A0=A0=A0=A0<font color=3D"#ff0000">9</font>87654</font></div><fon=
t face=3D"Courier New"><div><font face=3D"Courier New">--------------------=
-------------------------------------------</font></div>
<div>(3)=A0 CE3 IPv6 prefix: 20010db=A0987654 (<font color=3D"#ff9966">2001=
:db9:8765:4000::/52, woops!</font>)</div></font></div></div><div><font face=
=3D"courier new,monospace"></font>=A0</div><div><font face=3D"Courier New">=
ambiguity happens. then=A0we may argue: using the ugly Rule_IPv6_Prefix_B i=
s the root of the problem! we have not to use a prefix covered by another. =
</font></div>
<div><font face=3D"Courier New"></font>=A0</div><div><font face=3D"Courier =
New">Q3. what does the <font color=3D"#ff0000">exclusiveness</font> of Rule=
 IPv6 Prefix mean? </font></div><div><font face=3D"Courier New"></font>=A0<=
/div><div>
<font face=3D"Courier New">=A0=A0=A0 if we have 2001:da0::/28 for the Rule_=
IPv6_Prefix, everyone will be happy. however, unfortunately, we have only o=
ne /28 IPv6 aggregate. then what we have to do is splitting the /28 block i=
nto mutually exclusive pieces of small blocks. in the above example, if we =
have the following rule table:</font></div>
<div><font face=3D"Courier New"></font>=A0</div><div><font face=3D"Courier =
New">=A0=A0=A0=A0Rule_IPv4_Prefix=A0Rule_IPv6_Prefix</font></div><div><font=
 face=3D"Courier New">=A0=A0 -----------------------------------</font></di=
v><div><font face=3D"Courier New">=A0=A0=A0=A0192.32../12=A0=A0=A0=A0=A0 20=
01:db0::/<font color=3D"#ff0000">29</font></font></div>
<div><font face=3D"Courier New">=A0=A0=A0 64.32../16=A0=A0=A0=A0=A0=A0=A020=
01:db9::/<font color=3D"#ff0000">29</font></font></div><div><font face=3D"C=
ourier New">=A0=A0 -----------------------------------</font></div><div><fo=
nt face=3D"Courier New"></font>=A0</div>
<div><font face=3D"Courier New">=A0=A0=A0 then it will work fine within the=
 /28 room in total. for 192.32../12, if the PSID is at least 4bit, then the=
 *shortest* CE IPv6 prefix length is 29 + (32 - 12) + 4 =3D 53 now, rather =
than 52 in the previous example. if we have only or want to use only at mos=
t a /44 IPv6 prefix for the residual deployment, for the above 2 IPv4 netwo=
rks, we are not able to safely deploy the CE prefix shorter than /64, no ma=
tter how we take the effort! </font></div>
<div><font face=3D"Courier New"></font>=A0</div><div><font face=3D"Courier =
New">=A0=A0=A0 Jacni once mentioned that if we have a /x IPv6 prefix while =
the &quot;philosophy&quot; of address planning decides to have /y for each =
CE-delegated network, then we can play the magic with the bits between the =
/x and the /y. i would like to point out here, because of the exclusiveness=
 requirement, there is a hard limit=A0for the power of=A0the magic. if you =
have N IPv4 residual addresses, you must at least=A0satisfy the condition:<=
/font></div>
<div><font face=3D"Courier New"></font>=A0</div><div><font face=3D"Courier =
New">=A0=A0=A0 (4)=A0=A0=A0=A0 y - x &gt;=3D log(N)</font></div><div><font =
face=3D"Courier New"></font>=A0</div><div><font face=3D"Courier New">=A0=A0=
=A0 when (4) is not true, cutting the rule into pieces does help almost not=
hing. i said &quot;almost&quot; because there is really a little we can ach=
ieve: there is really some IPv4 address=A0seldom=A0used for any routers, li=
ke=A0192.32.1.0. however,=A0excluding such sort of addresses from the mappi=
ng scatters the mapping table=A0into a huge number of=A0/32-Rule_IPv4_Prefi=
x and making the table size=A0even longer than today&#39;s IPv4 routing tab=
le. </font></div>
<div><font face=3D"Courier New"></font>=A0</div><div><font face=3D"Courier =
New">just my 2 cents. execuse me if the humble calculation=A0has any misund=
erstanding, and please point out without hesitation.</font></div><div><font=
 face=3D"Courier New"></font>=A0</div>
<div><font face=3D"Courier New">best,</font></div><div><font face=3D"Courie=
r New">maoke</font></div><div><font face=3D"Courier New"></font>=A0</div><d=
iv><font face=3D"Courier New"></font>=A0</div><div><font face=3D"courier ne=
w,monospace">&gt; 2011/9/22 R=E9mi Despr=E9s &lt;<a href=3D"mailto:despres.=
remi@laposte.net">despres.remi@laposte.net</a>&gt;:</font></div>
<div><font face=3D"courier new,monospace">&gt;&gt; Alain, all,</font></div>=
<div><font face=3D"courier new,monospace">&gt;&gt;</font></div><div><font f=
ace=3D"courier new,monospace">&gt;&gt; We have just posted a new version of=
 our I-D on the proposed 4rd Address Mapping.</font></div>
<div><font face=3D"courier new,monospace">&gt;&gt; It is available at</font=
></div><div><font face=3D"courier new,monospace">&gt;&gt; <a href=3D"http:/=
/www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt">www.ietf.org=
/id/draft-despres-softwire-4rd-addmapping-01.txt</a></font></div>
<div><font face=3D"courier new,monospace">&gt;&gt;</font></div><div><font f=
ace=3D"courier new,monospace">&gt;&gt; Our presentation will be based on TH=
IS version, technically simpler than version -00.</font></div><div><font fa=
ce=3D"courier new,monospace">&gt;&gt; Major differences and their justifica=
tions will be briefly explained.</font></div>
<div><font face=3D"courier new,monospace">&gt;&gt;</font></div><div><font f=
ace=3D"courier new,monospace">&gt;&gt; Regards,</font></div><div><font face=
=3D"courier new,monospace">&gt;&gt; RD</font></div><div><font face=3D"couri=
er new,monospace">&gt;&gt; _______________________________________________<=
/font></div>
<div><font face=3D"courier new,monospace">&gt;&gt; Softwires mailing list</=
font></div><div><font face=3D"courier new,monospace">&gt;&gt; <a href=3D"ma=
ilto:Softwires@ietf.org">Softwires@ietf.org</a></font></div><div><font face=
=3D"courier new,monospace">&gt;&gt; <a href=3D"https://www.ietf.org/mailman=
/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a></f=
ont></div>
<div><font face=3D"courier new,monospace">&gt;&gt;</font></div><div><font f=
ace=3D"courier new,monospace">&gt; ________________________________________=
_______</font></div><div><font face=3D"courier new,monospace">&gt; Softwire=
s mailing list</font></div>
<div><font face=3D"courier new,monospace">&gt; <a href=3D"mailto:Softwires@=
ietf.org">Softwires@ietf.org</a></font></div><div><font face=3D"courier new=
,monospace">&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires=
">https://www.ietf.org/mailman/listinfo/softwires</a></font></div>
<div><font face=3D"courier new,monospace">&gt;</font></div><div><font face=
=3D"courier new,monospace">=A0</font></div><div><font face=3D"courier new,m=
onospace">=A0</font></div>

--0016e6d59e1bb19b4a04af4cf022--

From fibrib@gmail.com  Fri Oct 14 19:35:40 2011
Return-Path: <fibrib@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 8D33B21F8CE1 for <softwires@ietfa.amsl.com>; Fri, 14 Oct 2011 19:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level: 
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SjCSSVBa4uac for <softwires@ietfa.amsl.com>; Fri, 14 Oct 2011 19:35:40 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 4BEB521F8CBF for <softwires@ietf.org>; Fri, 14 Oct 2011 19:35:34 -0700 (PDT)
Received: by qyk33 with SMTP id 33so2616141qyk.10 for <softwires@ietf.org>; Fri, 14 Oct 2011 19:35:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=m/6UYFcNKcNmMEYbFS7ZMW5R7TzOjzgLH9BrcYWy2FQ=; b=wX/uj+5Zv5WWWgaBkAPvsMOJLoWeaJr9RwnbdW2CDCc0yBTNbTcGbb63alQQmMybx0 WISAgJbPpwZ7roVaLQdr7prvnrl0945XpXxdkJELhxIRB0hScYTRAXKPQ5knd4qmfJjo lMLPaALj8brhz01dMp2SgAUVWDoOfAjoKM51Q=
MIME-Version: 1.0
Received: by 10.229.63.194 with SMTP id c2mr2389427qci.69.1318646133737; Fri, 14 Oct 2011 19:35:33 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Fri, 14 Oct 2011 19:35:33 -0700 (PDT)
In-Reply-To: <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com>
Date: Sat, 15 Oct 2011 11:35:33 +0900
Message-ID: <CAFUBMqV9TiV5d0243ew+bCvFexy4nKoodopNi_7bKL4XtYxXOA@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>,  Softwires-wg <softwires@ietf.org>
Content-Type: multipart/alternative; boundary=0016e64fcd8a62cb1a04af4d3aa8
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 15 Oct 2011 02:35:40 -0000

--0016e64fcd8a62cb1a04af4d3aa8
Content-Type: text/plain; charset=ISO-8859-1

errata:
2011/10/15 Maoke <fibrib@gmail.com>

>  Q2. then it must fine as long as we map them to different Rule IPv6
> Prefix. (?)
>
>     suppose CE1 is the same as (1). for 64.32../16, we use a longer stuff.
>     however, there is a CE3:
>
>   Rule IPv6 Prefix B: 20010db8       (2001:db8::/29)
>     CE3 IPv4 address:    4020 1876   (64.32.24.118)
>             CE3 PSID:             54
>         CE3 CE index:         987654
> ---------------------------------------------------------------
> (3)  CE3 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52, woops!)
>
                                                             ^^53 if PSID
0x54 is 8bit.
but the generated CE3 IPv6 address is as same as CE1,
2001:db9:8765:4000:200:5efe::.


>     Rule_IPv4_Prefix Rule_IPv6_Prefix
>    -----------------------------------
>     192.32../12      2001:db0::/29
>     64.32../16       2001:db9::/29
>
                       ^^^^^^^^^^^^^2001:db8::/29

>
>
   -----------------------------------
>

thanks and regards,
maoke

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

<font face=3D"courier new,monospace">errata:<br></font><div class=3D"gmail_=
quote"><font face=3D"courier new,monospace">2011/10/15 Maoke <span dir=3D"l=
tr">&lt;<a href=3D"mailto:fibrib@gmail.com">fibrib@gmail.com</a>&gt;</span>=
<br></font><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1e=
x; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-le=
ft-style: solid;" class=3D"gmail_quote">
<div><font face=3D"courier new,monospace">=A0Q2. then it must fine as long =
as we map them to <font color=3D"#ff0000">different</font> Rule IPv6 Prefix=
. (?)</font></div><div><font face=3D"courier new,monospace">=A0</font></div=
><font face=3D"courier new,monospace">
</font><div><font face=3D"courier new,monospace">=A0=A0=A0=A0suppose CE1 is=
 the same as (1). for 64.32../16, we use a longer stuff.</font></div><div><=
font face=3D"courier new,monospace">=A0=A0=A0 however, there is a CE3:</fon=
t></div><div>
<font face=3D"courier new,monospace">=A0</font></div><font face=3D"courier =
new,monospace">
</font><div><div><div><font face=3D"courier new,monospace">=A0=A0Rule IPv6 =
Prefix B: 20010db<font color=3D"#ff0000">8</font>=A0=A0=A0=A0=A0=A0 (2001:d=
b8::/<font color=3D"#ff0000">29</font>)</font></div></div></div><div><font =
face=3D"courier new,monospace">
</font><div><font face=3D"courier new,monospace">=A0=A0=A0 CE3 IPv4 address=
:   =A0=A0 4020 <font color=3D"#ff0000">1</font><font color=3D"#000000">876=
</font>=A0=A0=A0(64.32.24.118)</font></div><div><div><font face=3D"courier =
new,monospace">=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0           CE3 PSID:=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A054=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 </font></div>
<font face=3D"courier new,monospace">
</font><div><font face=3D"courier new,monospace">=A0=A0=A0=A0=A0=A0=A0=A0CE=
3 CE index:=A0=A0=A0=A0=A0=A0=A0=A0=A0<font color=3D"#ff0000">9</font>87654=
</font></div><div><font face=3D"courier new,monospace">--------------------=
-------------------------------------------</font></div>
<font face=3D"courier new,monospace">
</font><div><font face=3D"courier new,monospace">(3)=A0 CE3 IPv6 prefix: 20=
010db=A0987654 (<font color=3D"#ff9966">2001:db9:8765:4000::/52, woops!</fo=
nt>)</font></div></div></div></blockquote><div><font face=3D"courier new,mo=
nospace">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ^^53 if PSID 0x54 is 8bit. </font><=
/div>
<div><font face=3D"courier new,monospace">but the generated CE3 IPv6 addres=
s is as same as CE1, 2001:db9:8765:4000:200:5efe::. </font></div><div><font=
 face=3D"courier new,monospace">=A0</font></div><blockquote style=3D"margin=
: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 20=
4); border-left-width: 1px; border-left-style: solid;" class=3D"gmail_quote=
">
<div><font face=3D"courier new,monospace">=A0=A0=A0=A0Rule_IPv4_Prefix=A0Ru=
le_IPv6_Prefix</font></div><div><font face=3D"courier new,monospace">=A0=A0=
 -----------------------------------</font></div><div><font face=3D"courier=
 new,monospace">=A0=A0=A0=A0192.32../12=A0=A0=A0=A0=A0 2001:db0::/<font col=
or=3D"#ff0000">29</font></font></div>
<font face=3D"courier new,monospace">
</font><div><font face=3D"courier new,monospace">=A0=A0=A0 64.32../16=A0=A0=
=A0=A0=A0=A0=A02001:db9::/<font color=3D"#ff0000">29</font></font></div></b=
lockquote><div><font face=3D"courier new,monospace">=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ^^^^^^^^^^^^^2001:db8::/29 </=
font></div>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote"><div><font face=3D"courier new,monospace">=A0<=
/font></div>
</blockquote><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: =
1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-=
left-style: solid;" class=3D"gmail_quote"><div><font face=3D"courier new,mo=
nospace">=A0=A0 -----------------------------------</font></div>
</blockquote></div><div><font face=3D"courier new,monospace"></font>=A0</di=
v><div><font face=3D"courier new,monospace">thanks and regards,</font></div=
><div><font face=3D"Courier New">maoke</font></div><div><font face=3D"couri=
er new,monospace"><br>
</font>=A0</div>

--0016e64fcd8a62cb1a04af4d3aa8--

From kawashimam@vx.jp.nec.com  Sun Oct 16 01:54:42 2011
Return-Path: <kawashimam@vx.jp.nec.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 8F15021F8A64 for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 01:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t5HdFvGuh4H5 for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 01:54:41 -0700 (PDT)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.32.8.206]) by ietfa.amsl.com (Postfix) with ESMTP id 8E81521F8560 for <softwires@ietf.org>; Sun, 16 Oct 2011 01:54:41 -0700 (PDT)
Received: from mailgate4.nec.co.jp ([10.7.69.184]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id p9G8sepj025453 for <softwires@ietf.org>; Sun, 16 Oct 2011 17:54:40 +0900 (JST)
Received: (from root@localhost) by mailgate4.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id p9G8seg25286 for softwires@ietf.org; Sun, 16 Oct 2011 17:54:40 +0900 (JST)
Received: from mail01b.kamome.nec.co.jp (mail01b.kamome.nec.co.jp [10.25.43.2]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id p9G8seAL016512 for <softwires@ietf.org>; Sun, 16 Oct 2011 17:54:40 +0900 (JST)
Received: from zuizan.jp.nec.com ([10.26.220.9] [10.26.220.9]) by mail01b.kamome.nec.co.jp with ESMTP id BT-MMP-354217; Sun, 16 Oct 2011 17:53:59 +0900
Received: from siznecatg159185 ([10.3.159.185] [10.3.159.185]) by mail.jp.nec.com with ESMTPA id BT-MMP-2867; Sun, 16 Oct 2011 17:53:58 +0900
To: softwires@ietf.org
In-reply-to: <20111016084011.28691.24648.idtracker@ietfa.amsl.com>
Message-Id: <20111016175357kawashimam@mail.jp.nec.com>
References: <20111016084011.28691.24648.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
X-Mailer: StarOffice21/MailClient[4.65 Step9]
From: Masanobu Kawashima <kawashimam@vx.jp.nec.com>
Date: Sun, 16 Oct 2011 17:53:57 +0900
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Subject: [Softwires] Fw: I-D Action: draft-mawatari-softwire-464xlat-00.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: Sun, 16 Oct 2011 08:54:42 -0000

Dear all,

I have submitted a draft regarding 464XLAT. 464XLAT is one of the IPv4
over IPv6 solutions that combine stateful and stateless translation.
Japan Internet Exchange(JPIX) is providing 464XLAT trial service since
July 2010.

I would appreciate it if you could comment to our document.

Regards,
Masanobu


>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>	Title           : 464XLAT: Combination of Stateful and Stateless Translation
>	Author(s)       : Masataka Mawatari
>                          Masanobu Kawashima
>	Filename        : draft-mawatari-softwire-464xlat-00.txt
>	Pages           : 8
>	Date            : 2011-10-15
>
>   This document describes a method (464XLAT) for IPv4 connectivity
>   across IPv6 network by combination of stateful translation and
>   stateless translation.  This 464XLAT method is applicable to the
>   access network.
>
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-mawatari-softwire-464xlat-00.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-mawatari-softwire-464xlat-00.txt
>_______________________________________________
>I-D-Announce mailing list
>I-D-Announce@ietf.org
>https://www.ietf.org/mailman/listinfo/i-d-announce
>Internet-Draft directories: http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


$B!q(B(._.)
========================================
 NEC AccessTechnica, Ltd.               
 Product Development Department         
 Masanobu Kawashima                     
 kawashimam@vx.jp.nec.com               
 http://www.necat.co.jp/                
========================================


From jan@go6.si  Sun Oct 16 02:07:51 2011
Return-Path: <jan@go6.si>
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 D773D21F888A for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 02:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQCgA25DYXNR for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 02:07:51 -0700 (PDT)
Received: from ipv6.go6.si (go6.si [IPv6:2a02:e8:0:1::babe:face]) by ietfa.amsl.com (Postfix) with ESMTP id 6509121F8797 for <softwires@ietf.org>; Sun, 16 Oct 2011 02:07:51 -0700 (PDT)
Received: from jan-mac.lan (unknown [46.54.255.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jan) by ipv6.go6.si (Postfix) with ESMTP id 227AB2378048 for <softwires@ietf.org>; Sun, 16 Oct 2011 11:07:49 +0200 (CEST)
Message-ID: <4E9A9EE5.3000602@go6.si>
Date: Sun, 16 Oct 2011 11:07:49 +0200
From: "Jan Zorz @ go6.si" <jan@go6.si>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: softwires@ietf.org
References: <20111016084011.28691.24648.idtracker@ietfa.amsl.com> <20111016175357kawashimam@mail.jp.nec.com>
In-Reply-To: <20111016175357kawashimam@mail.jp.nec.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Softwires] Fw: I-D Action: draft-mawatari-softwire-464xlat-00.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: Sun, 16 Oct 2011 09:07:51 -0000

On 10/16/11 10:53 AM, Masanobu Kawashima wrote:
> 
> Dear all,
> 
> I have submitted a draft regarding 464XLAT. 

Dear Masanobu-san,

Another flavor of CGN? Is this really needed?

Cheers, Jan

From kawashimam@vx.jp.nec.com  Sun Oct 16 05:40:18 2011
Return-Path: <kawashimam@vx.jp.nec.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 7696621F8A7D for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 05:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwT2RI6pD0YS for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 05:40:17 -0700 (PDT)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.32.8.206]) by ietfa.amsl.com (Postfix) with ESMTP id A20E321F8A71 for <softwires@ietf.org>; Sun, 16 Oct 2011 05:40:17 -0700 (PDT)
Received: from mailgate4.nec.co.jp ([10.7.69.184]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id p9GCeCjO000842;  Sun, 16 Oct 2011 21:40:12 +0900 (JST)
Received: (from root@localhost) by mailgate4.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id p9GCeC308985; Sun, 16 Oct 2011 21:40:12 +0900 (JST)
Received: from mail02.kamome.nec.co.jp (mail02.kamome.nec.co.jp [10.25.43.5]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id p9GCeBaj021870; Sun, 16 Oct 2011 21:40:11 +0900 (JST)
Received: from shikibu.jp.nec.com ([10.26.220.2] [10.26.220.2]) by mail03.kamome.nec.co.jp with ESMTP id BT-MMP-1487824; Sun, 16 Oct 2011 21:39:26 +0900
Received: from siznecatg159185 ([10.3.159.185] [10.3.159.185]) by mail.jp.nec.com with ESMTP; Sun, 16 Oct 2011 21:39:25 +0900
To: "Jan Zorz @ go6.si" <jan@go6.si>
In-reply-to: <4E9A9EE5.3000602@go6.si>
References: <4E9A9EE5.3000602@go6.si>
Message-Id: <20111016213925kawashimam@mail.jp.nec.com>
Mime-Version: 1.0
X-Mailer: StarOffice21/MailClient[4.65 Step9]
From: Masanobu Kawashima <kawashimam@vx.jp.nec.com>
Date: Sun, 16 Oct 2011 21:39:24 +0900
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org
Subject: Re: [Softwires] Fw: I-D Action:draft-mawatari-softwire-464xlat-00.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: Sun, 16 Oct 2011 12:40:18 -0000

Hi Jan,

Thank you for your comment.

464XLAT is a similar to DS-Lite. However, it does not need to do
encapsulation. It is a double translation approach like a dIVI.
However, CLAT does not need port mapping algorithm.

CPE is cost sensitive that should be simple for easily deployment.
All CLAT vendors have to do is to comply with RFC6145.

All ISPs do not need deep packet inspection. They can migrate quickly
their operation to an IPv6-only environment.

Regards,
Masanobu


>On 10/16/11 10:53 AM, Masanobu Kawashima wrote:
>> 
>> Dear all,
>> 
>> I have submitted a draft regarding 464XLAT. 
>
>Dear Masanobu-san,
>
>Another flavor of CGN? Is this really needed?
>
>Cheers, Jan
>_______________________________________________
>Softwires mailing list
>Softwires@ietf.org
>https://www.ietf.org/mailman/listinfo/softwires

$B!q(B(._.)
========================================
 NEC AccessTechnica, Ltd.               
 Product Development Department         
 Masanobu Kawashima                     
 kawashimam@vx.jp.nec.com               
 http://www.necat.co.jp/                
========================================


From jacni@jacni.com  Sun Oct 16 20:05:06 2011
Return-Path: <jacni@jacni.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 5EBC211E8081 for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 20:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.883
X-Spam-Level: 
X-Spam-Status: No, score=-1.883 tagged_above=-999 required=5 tests=[AWL=0.404,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QI++7E4qiwP8 for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 20:05:05 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 29A2311E8073 for <softwires@ietf.org>; Sun, 16 Oct 2011 20:05:04 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 1971F380059 for <softwires@ietf.org>; Sun, 16 Oct 2011 23:05:02 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 9DF3C3400D7 for <softwires@ietf.org>; Mon, 17 Oct 2011 11:05:00 +0800 (CST)
Received: from [172.18.50.22] (unknown [221.11.61.30]) by app (Coremail) with SMTP id +AWowJBLKARWm5tOpBcdAA--.30561S2; Mon, 17 Oct 2011 11:04:57 +0800 (CST)
Message-ID: <4E9B9BC5.2090200@jacni.com>
Date: Mon, 17 Oct 2011 11:06:45 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com>
In-Reply-To: <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090802030402020105060002"
X-CM-TRANSID: +AWowJBLKARWm5tOpBcdAA--.30561S2
X-Coremail-Antispam: 1UD129KBjvJXoW3GF1UZF4DJw47Zr1fGF1fCrg_yoWxWr1rpr 1fKr13KF1DJry8A397uw1UWrn8AF95J3yUJr15Jry8Ca45AF10yrsYkr4rZayUJrWfJr4Y qr4qkr18Gan8Z3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUcYb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VWkKwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK64x0aVW7Gw IE548m6rI_Jw1UWr17M2kK6IIYrVAqxI0j4VAqrcv_Jw1UGr1DM2vj6xkI62vS6c8GOVWU tr1rJFylYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UM4x0Y48IcV AKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI 7VAKI48JMxCIbVAxMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr4UvcSsGvfC2Kf nxnUUI43ZEXa7IU0S_MDUUUUU==
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQAEEko7lOqbKAAAsr
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 17 Oct 2011 03:05:06 -0000

This is a multi-part message in MIME format.
--------------090802030402020105060002
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

hi,

Let me try to answer your questions, please see below,

On 10/15/2011 10:14 AM, Maoke wrote:
> hi Remi and all,
> a discussion on the address mapping in -01.txt, trying to fully 
> understand the design. comments are requested.
> - what if there are two rules?
>   suppose we have 192.32../12 (0xc0200000/12, i think it's not the 
> 0x602 as Leaf previously mentioned, ;-)
>   and we also have 64.32../16 (0x40200000/16). we have a lot of CEs.
> Q1. if we use the two as the Rule_IPv4_Prefix_A and _B, can we map 
> them to a single Rule_IPv6_Prefix?
Yes.

>     Rule IPv6 Prefix: 20010db        (2001:db0::/28)
>     CE1 IPv4 address:     c02 98765         (192.41.135.101)
>             CE1 PSID:              4
>         CE1 CE index:         987654
> ---------------------------------------------------------------
> (1)  CE1 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52)
>     suppose we happen to have another CE somewhere else:
>     Rule IPv6 Prefix: 20010db
>     CE2 IPv4 address:    4020 9876          (64.32.152.118)
>             CE2 PSID:             54
>         CE2 CE index:         987654
> ---------------------------------------------------------------
> (2)  CE2 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52)
> ambiguity happens and packet encapsulated with the same CE IPv6 
> address cannot be routed to the correct CE.
This is not gonna happen, since the IPv6 address planing must be done 
natively considering nothing about the IPv4 in the very beginning. In 
your example, I see you get a 2001:db0::/28 and you want to assign a /52 
to each CE, then ok, there will be 24 bits to distinguish CEs and should 
be assigned continuously without any conflict. The next step is to check 
the available IPv4 spaces we have for the given number of subscribers, 
then based on which to design the rules. You made it in an opposite 
direction.

We break the boundary between the IPv4 address and port, use the bits 
(24 bits in the examples above) together to identify the subscribers. 
The only reason I see to employ multiple IPv4 prefixes is we can't get a 
large enough one. Additionally, in the second example above, you changed 
the sharing ratio to make a "24-bit index", then you should change the 
Rule IPv6 prefix to, for example /27, for the two IPv4 prefixes of "same 
size". On the other hand, according to the consensus (if I get it 
correctly) of the interim meeting, more than one sharing ratios for the 
extended address case is not desirable, that flexibility should be 
offered by stateful approaches.

> therefore my answer to Q1, is NO, unless we carefully select IPv4 
> addresses for CEs with giving up to use some of them, which have been 
> so precious.
> Q2. then it must fine as long as we map them to different Rule IPv6 
> Prefix. (?)
>     suppose CE1 is the same as (1). for 64.32../16, we use a longer stuff.
>     however, there is a CE3:
>   Rule IPv6 Prefix B: 20010db8       (2001:db8::/29)
>     CE3 IPv4 address:    4020 1876   (64.32.24.118)
>             CE3 PSID:             54
>         CE3 CE index: 987654
> ---------------------------------------------------------------
> (3)  CE3 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52, woops!)
> ambiguity happens. then we may argue: using the ugly 
> Rule_IPv6_Prefix_B is the root of the problem! we have not to use a 
> prefix covered by another.
No, I think the bits of the same position are not additive. So, it 
should be a delegated prefix of "/53", right?

> Q3. what does the exclusiveness of Rule IPv6 Prefix mean?
>     if we have 2001:da0::/28 for the Rule_IPv6_Prefix, everyone will 
> be happy. however, unfortunately, we have only one /28 IPv6 aggregate. 
> then what we have to do is splitting the /28 block into mutually 
> exclusive pieces of small blocks. in the above example, if we have the 
> following rule table:
>     Rule_IPv4_Prefix Rule_IPv6_Prefix
>    -----------------------------------
>     192.32../12      2001:db0::/29
>     64.32../16       2001:db9::/29
>    -----------------------------------
Yes, the exclusiveness. It's similar to what we do to further divide a 
subnet hierarchically. Hierarchies/exclusiveness avoid conflicts but 
lose the efficiency of addressing. BTW, the /29 example is the same as 
what I propose above. :-)

>     then it will work fine within the /28 room in total. for 
> 192.32../12, if the PSID is at least 4bit, then the *shortest* CE IPv6 
> prefix length is 29 + (32 - 12) + 4 = 53 now, rather than 52 in the 
> previous example. if we have only or want to use only at most a /44 
> IPv6 prefix for the residual deployment, for the above 2 IPv4 
> networks, we are not able to safely deploy the CE prefix shorter than 
> /64, no matter how we take the effort!
>     Jacni once mentioned that if we have a /x IPv6 prefix while the 
> "philosophy" of address planning decides to have /y for each 
> CE-delegated network, then we can play the magic with the bits between 
> the /x and the /y. i would like to point out here, because of the 
> exclusiveness requirement, there is a hard limit for the power of the 
> magic. if you have N IPv4 residual addresses, you must at 
> least satisfy the condition:
Please see my comments above.


Cheers,
Jacni

>     (4)     y - x >= log(N)
>     when (4) is not true, cutting the rule into pieces does help 
> almost nothing. i said "almost" because there is really a little we 
> can achieve: there is really some IPv4 address seldom used for any 
> routers, like 192.32.1.0. however, excluding such sort of addresses 
> from the mapping scatters the mapping table into a huge number 
> of /32-Rule_IPv4_Prefix and making the table size even longer than 
> today's IPv4 routing table.
> just my 2 cents. execuse me if the humble calculation has any 
> misunderstanding, and please point out without hesitation.
> best,
> maoke
> > 2011/9/22 Rémi Després <despres.remi@laposte.net 
> <mailto:despres.remi@laposte.net>>:
> >> Alain, all,
> >>
> >> We have just posted a new version of our I-D on the proposed 4rd 
> Address Mapping.
> >> It is available at
> >> www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt 
> <http://www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt>
> >>
> >> Our presentation will be based on THIS version, technically simpler 
> than version -00.
> >> Major differences and their justifications will be briefly explained.
> >>
> >> Regards,
> >> RD
> >> _______________________________________________
> >> Softwires mailing list
> >> Softwires@ietf.org <mailto:Softwires@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/softwires
> >>
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org <mailto:Softwires@ietf.org>
> > https://www.ietf.org/mailman/listinfo/softwires
> >
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

--------------090802030402020105060002
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,<br>
      <br>
      Let me try to answer your questions, please see below,<br>
    </font><br>
    On 10/15/2011 10:14 AM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com"
      type="cite">
      <div><font face="courier new,monospace">&nbsp;</font></div>
      <div><font face="courier new,monospace">&nbsp;</font></div>
      <div><font face="courier new,monospace">hi Remi and all,</font></div>
      <div><font face="courier new,monospace">&nbsp;</font></div>
      <div><font face="courier new,monospace">a discussion on the
          address mapping in -01.txt, trying to fully understand the
          design. comments are requested. </font></div>
      <div><font face="courier new,monospace">&nbsp;</font></div>
      <div>
        <font face="courier new,monospace">- what if there are two
          rules? </font></div>
      <div><font face="courier new,monospace">&nbsp;</font></div>
      <div><font face="courier new,monospace">&nbsp; suppose we have
          192.32../12 (0x<font color="#ff0000">c02</font>00000/12, i
          think it's not the 0x602 as Leaf previously mentioned, ;-)</font></div>
      <div><font face="courier new,monospace">&nbsp; and we also have
          64.32../16 (0x<font color="#ff6666">4020</font>0000/16). we
          have a lot of CEs. </font></div>
      <div>&nbsp;</div>
      <div><font face="courier new,monospace">Q1. if we use the two as
          the Rule_IPv4_Prefix_A and _B, can we map them to a single
          Rule_IPv6_Prefix? </font></div>
      <div>&nbsp;</div>
    </blockquote>
    Yes.<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com"
      type="cite">
      <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; Rule IPv6
          Prefix:&nbsp;20010db&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (2001:db0::/28)</font></div>
      <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; CE1 IPv4 address:&nbsp;&nbsp;&nbsp;&nbsp;
          c02&nbsp;98765&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(192.41.135.101)</font></div>
      <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CE1
          PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CE1 CE index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 987654</font></div>
      <font face="Courier New">
        <div><font face="Courier New">---------------------------------------------------------------</font></div>
        <div>(1)&nbsp; CE1 IPv6 prefix: 20010db&nbsp;987654&nbsp;(<font color="#ff0000">2001:db9:8765:4000::/52</font>)</div>
      </font><font face="courier new,monospace">
        <div>
          <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; suppose we happen
              to have another CE somewhere else:</font></div>
          <div>&nbsp;</div>
          <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; Rule IPv6 Prefix:
              20010db</font></div>
        </div>
      </font>
      <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; CE2 IPv4 address:&nbsp;&nbsp;&nbsp;
          4020&nbsp;9876&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(64.32.152.118)</font></div>
      <div>
        <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CE2
            PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;54&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></div>
        <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CE2 CE
            index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;987654</font></div>
        <font face="Courier New">
          <div><font face="Courier New">---------------------------------------------------------------</font></div>
          <div>(2)&nbsp; CE2 IPv6 prefix: 20010db&nbsp;987654 (<font
              color="#ff9966">2001:db9:8765:4000::/52</font>)</div>
        </font></div>
      <div>&nbsp;</div>
      <div><font face="Courier New">ambiguity happens and&nbsp;packet
          encapsulated&nbsp;with the same CE IPv6 address cannot be routed to
          the correct CE. </font></div>
    </blockquote>
    This is not gonna happen, since the IPv6 address planing must be
    done natively considering nothing about the IPv4 in the very
    beginning. In your example, I see you get a 2001:db0::/28 and you
    want to assign a /52 to each CE, then ok, there will be 24 bits to
    distinguish CEs and should be assigned continuously without any
    conflict. The next step is to check the available IPv4 spaces we
    have for the given number of subscribers, then based on which to
    design the rules. You made it in an opposite direction.<br>
    <br>
    We break the boundary between the IPv4 address and port, use the
    bits (24 bits in the examples above) together to identify the
    subscribers. The only reason I see to employ multiple IPv4 prefixes
    is we can't get a large enough one. Additionally, in the second
    example above, you changed the sharing ratio to make a "24-bit
    index", then you should change the Rule IPv6 prefix to, for example
    /27, for the two IPv4 prefixes of "same size". On the other hand,
    according to the consensus (if I get it correctly) of the interim
    meeting, more than one sharing ratios for the extended address case
    is not desirable, that flexibility should be offered by stateful
    approaches.<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com"
      type="cite">
      <div><font face="Courier New">therefore my answer to Q1, is NO, </font><font
          face="Courier New">unless we carefully select IPv4 addresses
          for CEs with giving up to use some of them, which have been so
          precious. </font></div>
      <div>&nbsp;</div>
      <div><font face="Courier New">Q2. then it must fine as long as we
          map them to <font color="#ff0000">different</font> Rule IPv6
          Prefix. (?)</font></div>
      <div>&nbsp;</div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;suppose CE1 is the same as (1).
          for 64.32../16, we use a longer stuff.</font></div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp; however, there is a CE3:</font></div>
      <div><font face="courier new,monospace">&nbsp;</font></div>
      <font face="courier new,monospace">
        <div>
          <div>
            <div><font face="courier new,monospace">&nbsp;&nbsp;Rule IPv6 Prefix
                B: 20010db<font color="#ff0000">8</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                (2001:db8::/<font color="#ff0000">29</font>)</font></div>
          </div>
        </div>
      </font>
      <div>
        <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; CE3 IPv4 address: &nbsp;&nbsp;
            4020 <font color="#ff0000">1</font><font color="#000000">876</font>&nbsp;&nbsp;&nbsp;(64.32.24.118)</font></div>
        <div>
          <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; CE3
              PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;54&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></div>
          <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CE3 CE index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font
                color="#ff0000">9</font>87654</font></div>
          <font face="Courier New">
            <div><font face="Courier New">---------------------------------------------------------------</font></div>
            <div>(3)&nbsp; CE3 IPv6 prefix: 20010db&nbsp;987654 (<font
                color="#ff9966">2001:db9:8765:4000::/52, woops!</font>)</div>
          </font></div>
      </div>
      <div>&nbsp;</div>
      <div><font face="Courier New">ambiguity happens. then&nbsp;we may
          argue: using the ugly Rule_IPv6_Prefix_B is the root of the
          problem! we have not to use a prefix covered by another. </font></div>
      <div>&nbsp;</div>
    </blockquote>
    No, I think the bits of the same position are not additive. So, it
    should be a delegated prefix of "/53", right?<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com"
      type="cite">
      <div><font face="Courier New">Q3. what does the <font
            color="#ff0000">exclusiveness</font> of Rule IPv6 Prefix
          mean? </font></div>
      <div>&nbsp;</div>
      <div>
        <font face="Courier New">&nbsp;&nbsp;&nbsp; if we have 2001:da0::/28 for the
          Rule_IPv6_Prefix, everyone will be happy. however,
          unfortunately, we have only one /28 IPv6 aggregate. then what
          we have to do is splitting the /28 block into mutually
          exclusive pieces of small blocks. in the above example, if we
          have the following rule table:</font></div>
      <div>&nbsp;</div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;Rule_IPv4_Prefix&nbsp;Rule_IPv6_Prefix</font></div>
      <div><font face="Courier New">&nbsp;&nbsp;
          -----------------------------------</font></div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;192.32../12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2001:db0::/<font
            color="#ff0000">29</font></font></div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp; 64.32../16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2001:db9::/<font
            color="#ff0000">29</font></font></div>
      <div><font face="Courier New">&nbsp;&nbsp;
          -----------------------------------</font></div>
    </blockquote>
    Yes, the exclusiveness. It's similar to what we do to further divide
    a subnet hierarchically. Hierarchies/exclusiveness avoid conflicts
    but lose the efficiency of addressing. BTW, the /29 example is the
    same as what I propose above. :-)<br>
    &nbsp;<br>
    <blockquote
cite="mid:CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com"
      type="cite">
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp; then it will work fine within
          the /28 room in total. for 192.32../12, if the PSID is at
          least 4bit, then the *shortest* CE IPv6 prefix length is 29 +
          (32 - 12) + 4 = 53 now, rather than 52 in the previous
          example. if we have only or want to use only at most a /44
          IPv6 prefix for the residual deployment, for the above 2 IPv4
          networks, we are not able to safely deploy the CE prefix
          shorter than /64, no matter how we take the effort! </font></div>
      <div>&nbsp;</div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp; Jacni once mentioned that if we
          have a /x IPv6 prefix while the "philosophy" of address
          planning decides to have /y for each CE-delegated network,
          then we can play the magic with the bits between the /x and
          the /y. i would like to point out here, because of the
          exclusiveness requirement, there is a hard limit&nbsp;for the power
          of&nbsp;the magic. if you have N IPv4 residual addresses, you must
          at least&nbsp;satisfy the condition:</font></div>
    </blockquote>
    Please see my comments above.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com"
      type="cite">
      <div>&nbsp;</div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp; (4)&nbsp;&nbsp;&nbsp;&nbsp; y - x &gt;= log(N)</font></div>
      <div>&nbsp;</div>
      <div><font face="Courier New">&nbsp;&nbsp;&nbsp; when (4) is not true, cutting
          the rule into pieces does help almost nothing. i said "almost"
          because there is really a little we can achieve: there is
          really some IPv4 address&nbsp;seldom&nbsp;used for any routers,
          like&nbsp;192.32.1.0. however,&nbsp;excluding such sort of addresses
          from the mapping scatters the mapping table&nbsp;into a huge number
          of&nbsp;/32-Rule_IPv4_Prefix and making the table size&nbsp;even longer
          than today's IPv4 routing table. </font></div>
      <div>&nbsp;</div>
      <div><font face="Courier New">just my 2 cents. execuse me if the
          humble calculation&nbsp;has any misunderstanding, and please point
          out without hesitation.</font></div>
      <div>&nbsp;</div>
      <div><font face="Courier New">best,</font></div>
      <div><font face="Courier New">maoke</font></div>
      <div>&nbsp;</div>
      <div>&nbsp;</div>
      <div><font face="courier new,monospace">&gt; 2011/9/22 R&eacute;mi
          Despr&eacute;s &lt;<a moz-do-not-send="true"
            href="mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;:</font></div>
      <div><font face="courier new,monospace">&gt;&gt; Alain, all,</font></div>
      <div><font face="courier new,monospace">&gt;&gt;</font></div>
      <div><font face="courier new,monospace">&gt;&gt; We have just
          posted a new version of our I-D on the proposed 4rd Address
          Mapping.</font></div>
      <div><font face="courier new,monospace">&gt;&gt; It is available
          at</font></div>
      <div><font face="courier new,monospace">&gt;&gt; <a
            moz-do-not-send="true"
href="http://www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt">www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt</a></font></div>
      <div><font face="courier new,monospace">&gt;&gt;</font></div>
      <div><font face="courier new,monospace">&gt;&gt; Our presentation
          will be based on THIS version, technically simpler than
          version -00.</font></div>
      <div><font face="courier new,monospace">&gt;&gt; Major differences
          and their justifications will be briefly explained.</font></div>
      <div><font face="courier new,monospace">&gt;&gt;</font></div>
      <div><font face="courier new,monospace">&gt;&gt; Regards,</font></div>
      <div><font face="courier new,monospace">&gt;&gt; RD</font></div>
      <div><font face="courier new,monospace">&gt;&gt;
          _______________________________________________</font></div>
      <div><font face="courier new,monospace">&gt;&gt; Softwires mailing
          list</font></div>
      <div><font face="courier new,monospace">&gt;&gt; <a
            moz-do-not-send="true" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a></font></div>
      <div><font face="courier new,monospace">&gt;&gt; <a
            moz-do-not-send="true"
            href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a></font></div>
      <div><font face="courier new,monospace">&gt;&gt;</font></div>
      <div><font face="courier new,monospace">&gt;
          _______________________________________________</font></div>
      <div><font face="courier new,monospace">&gt; Softwires mailing
          list</font></div>
      <div><font face="courier new,monospace">&gt; <a
            moz-do-not-send="true" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a></font></div>
      <div><font face="courier new,monospace">&gt; <a
            moz-do-not-send="true"
            href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a></font></div>
      <div><font face="courier new,monospace">&gt;</font></div>
      <div><font face="courier new,monospace">&nbsp;</font></div>
      <div><font face="courier new,monospace">&nbsp;</font></div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Softwires mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a>
</pre>
    </blockquote>
  </body>
</html>

--------------090802030402020105060002--


From jacni@jacni.com  Sun Oct 16 20:23:28 2011
Return-Path: <jacni@jacni.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 48F0D21F8495 for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 20:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[AWL=0.354,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oFgoMU-xAaTi for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 20:23:27 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id C2C9621F8493 for <softwires@ietf.org>; Sun, 16 Oct 2011 20:23:27 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id CFB7E3800B2 for <softwires@ietf.org>; Sun, 16 Oct 2011 23:23:25 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 6E7F434013D for <softwires@ietf.org>; Mon, 17 Oct 2011 11:13:40 +0800 (CST)
Received: from [172.18.50.22] (unknown [221.11.61.30]) by app (Coremail) with SMTP id +AWowJArWgNTnZtOxxkdAA--.5263S2; Mon, 17 Oct 2011 11:13:33 +0800 (CST)
Message-ID: <4E9B9DB9.70200@jacni.com>
Date: Mon, 17 Oct 2011 11:15:05 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <CAFUBMqV9TiV5d0243ew+bCvFexy4nKoodopNi_7bKL4XtYxXOA@mail.gmail.com>
In-Reply-To: <CAFUBMqV9TiV5d0243ew+bCvFexy4nKoodopNi_7bKL4XtYxXOA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050001010706080008040901"
X-CM-TRANSID: +AWowJArWgNTnZtOxxkdAA--.5263S2
X-Coremail-Antispam: 1UD129KBjvdXoWrZF1DGr4fWF1xGF18XF1DJrb_yoWkGFX_XF yDAFy8Xr1UJrnFgw4xtr18XwnrXr4DXryUW34DJr4fZr17Jry3J3yxJFWUWr15WF98Gr1D Jw1kJr1Utw1jkjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUj5kYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF 6F4UM7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1ln4vEF7Iv6F18KV Aqrcv_GVWUtr1rJF1ln4vEIxkG6c02xx0F6c8GOVWUtr18Jw1lnx0Ec2IEnICE548m6r1D JrWUZwAv7VC0I7IYx2IY67AKxVWUGVWUXwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64 vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxk0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2Ij 64vIr41l4IxY624lx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y0x0EwIxGrbIYCTnIWIevJa 73UjIFyTuYvjxUID7aUUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEEEko7lOqcnAAAsZ
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 17 Oct 2011 03:23:28 -0000

This is a multi-part message in MIME format.
--------------050001010706080008040901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

On 10/15/2011 10:35 AM, Maoke wrote:
> errata:
> 2011/10/15 Maoke <fibrib@gmail.com <mailto:fibrib@gmail.com>>
>
>      Q2. then it must fine as long as we map them to different Rule
>     IPv6 Prefix. (?)
>         suppose CE1 is the same as (1). for 64.32../16, we use a
>     longer stuff.
>         however, there is a CE3:
>       Rule IPv6 Prefix B: 20010db8       (2001:db8::/29)
>         CE3 IPv4 address:    4020 1876   (64.32.24.118)
>                 CE3 PSID:             54
>             CE3 CE index: 987654
>     ---------------------------------------------------------------
>     (3)  CE3 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52, woops!)
>
>                                                              ^^53 if 
> PSID 0x54 is 8bit.
> but the generated CE3 IPv6 address is as same as CE1, 
> 2001:db9:8765:4000:200:5efe::.
I guess, it should be 2001:db8:1876:5400::/53


Cheers,
Jacni

>         Rule_IPv4_Prefix Rule_IPv6_Prefix
>        -----------------------------------
>         192.32../12      2001:db0::/29
>         64.32../16       2001:db9::/29
>
>                        ^^^^^^^^^^^^^2001:db8::/29
>
>        -----------------------------------
>
> thanks and regards,
> maoke
>
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

--------------050001010706080008040901
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">Hi,</font><br>
    <br>
    On 10/15/2011 10:35 AM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqV9TiV5d0243ew+bCvFexy4nKoodopNi_7bKL4XtYxXOA@mail.gmail.com"
      type="cite"><font face="courier new,monospace">errata:<br>
      </font>
      <div class="gmail_quote"><font face="courier new,monospace">2011/10/15
          Maoke <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:fibrib@gmail.com">fibrib@gmail.com</a>&gt;</span><br>
        </font>
        <blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex;
          border-left-color: rgb(204, 204, 204); border-left-width: 1px;
          border-left-style: solid;" class="gmail_quote">
          <div><font face="courier new,monospace">&nbsp;Q2. then it must fine
              as long as we map them to <font color="#ff0000">different</font>
              Rule IPv6 Prefix. (?)</font></div>
          <div><font face="courier new,monospace">&nbsp;</font></div>
          <font face="courier new,monospace">
          </font>
          <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;suppose CE1 is the
              same as (1). for 64.32../16, we use a longer stuff.</font></div>
          <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; however, there is
              a CE3:</font></div>
          <div>
            <font face="courier new,monospace">&nbsp;</font></div>
          <font face="courier new,monospace">
          </font>
          <div>
            <div>
              <div><font face="courier new,monospace">&nbsp;&nbsp;Rule IPv6 Prefix
                  B: 20010db<font color="#ff0000">8</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                  (2001:db8::/<font color="#ff0000">29</font>)</font></div>
            </div>
          </div>
          <div><font face="courier new,monospace">
            </font>
            <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; CE3 IPv4
                address: &nbsp;&nbsp; 4020 <font color="#ff0000">1</font><font
                  color="#000000">876</font>&nbsp;&nbsp;&nbsp;(64.32.24.118)</font></div>
            <div>
              <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; CE3
                  PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;54&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></div>
              <font face="courier new,monospace">
              </font>
              <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CE3 CE
                  index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font color="#ff0000">9</font>87654</font></div>
              <div><font face="courier new,monospace">---------------------------------------------------------------</font></div>
              <font face="courier new,monospace">
              </font>
              <div><font face="courier new,monospace">(3)&nbsp; CE3 IPv6
                  prefix: 20010db&nbsp;987654 (<font color="#ff9966">2001:db9:8765:4000::/52,
                    woops!</font>)</font></div>
            </div>
          </div>
        </blockquote>
        <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            ^^53 if PSID 0x54 is 8bit. </font></div>
        <div><font face="courier new,monospace">but the generated CE3
            IPv6 address is as same as CE1,
            2001:db9:8765:4000:200:5efe::. </font></div>
      </div>
    </blockquote>
    I guess, it should be 2001:db8:1876:5400::/53<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAFUBMqV9TiV5d0243ew+bCvFexy4nKoodopNi_7bKL4XtYxXOA@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div><font face="courier new,monospace">&nbsp;</font></div>
        <blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex;
          border-left-color: rgb(204, 204, 204); border-left-width: 1px;
          border-left-style: solid;" class="gmail_quote">
          <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;Rule_IPv4_Prefix&nbsp;Rule_IPv6_Prefix</font></div>
          <div><font face="courier new,monospace">&nbsp;&nbsp;
              -----------------------------------</font></div>
          <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;192.32../12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              2001:db0::/<font color="#ff0000">29</font></font></div>
          <font face="courier new,monospace">
          </font>
          <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;
              64.32../16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2001:db9::/<font color="#ff0000">29</font></font></div>
        </blockquote>
        <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            ^^^^^^^^^^^^^2001:db8::/29 </font></div>
        <blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex;
          border-left-color: rgb(204, 204, 204); border-left-width: 1px;
          border-left-style: solid;" class="gmail_quote">
          <div><font face="courier new,monospace">&nbsp;</font></div>
        </blockquote>
        <blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex;
          border-left-color: rgb(204, 204, 204); border-left-width: 1px;
          border-left-style: solid;" class="gmail_quote">
          <div><font face="courier new,monospace">&nbsp;&nbsp;
              -----------------------------------</font></div>
        </blockquote>
      </div>
      <div>&nbsp;</div>
      <div><font face="courier new,monospace">thanks and regards,</font></div>
      <div><font face="Courier New">maoke</font></div>
      <div><font face="courier new,monospace"><br>
        </font>&nbsp;</div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Softwires mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Softwires@ietf.org">Softwires@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.org/mailman/listinfo/softwires</a>
</pre>
    </blockquote>
  </body>
</html>

--------------050001010706080008040901--


From fibrib@gmail.com  Sun Oct 16 20:59:25 2011
Return-Path: <fibrib@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 EF89621F84ED for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 20:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.048
X-Spam-Level: 
X-Spam-Status: No, score=-3.048 tagged_above=-999 required=5 tests=[AWL=0.550,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntasog9XDGqN for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 20:59:24 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 36B9B21F84E5 for <softwires@ietf.org>; Sun, 16 Oct 2011 20:59:24 -0700 (PDT)
Received: by qyk34 with SMTP id 34so577234qyk.10 for <softwires@ietf.org>; Sun, 16 Oct 2011 20:59:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HdQIVzD2LZG+Byql+OwS7Tk7+yw2FOIXb7pfGP+JlRk=; b=d48ntlRZwUha9zGrAyQW2QFapFz0Kl9ukXZLchYuFiuc9lJud3NrsSDKkY4gtuLtJa 5WWSua4xmbr+UW7cbX07zwNBaUWTD1kRO/T4xzzcj7hjOEE0q3iW0c/pudPRaeBVD5O8 XYQcNAGuiPwCHQ+vFVB9Fj/kIcv1Y6HwCL5v0=
MIME-Version: 1.0
Received: by 10.229.63.169 with SMTP id b41mr3711657qci.145.1318823963651; Sun, 16 Oct 2011 20:59:23 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Sun, 16 Oct 2011 20:59:23 -0700 (PDT)
In-Reply-To: <4E9B9BC5.2090200@jacni.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com>
Date: Mon, 17 Oct 2011 12:59:23 +0900
Message-ID: <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=0016e65da6eedfef8204af76a17c
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 17 Oct 2011 03:59:26 -0000

--0016e65da6eedfef8204af76a17c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Jacni,

thanks a lot for the reply. please see inline.

2011/10/17 Jacni Qin <jacni@jacni.com>
>
> hi,
>
> Let me try to answer your questions, please see below,
>
> On 10/15/2011 10:14 AM, Maoke wrote:
>
>
>
> hi Remi and all,
>
> a discussion on the address mapping in -01.txt, trying to fully understan=
d
> the design. comments are requested.
>
>  - what if there are two rules?
>
>   suppose we have 192.32../12 (0xc0200000/12, i think it's not the 0x602
> as Leaf previously mentioned, ;-)
>   and we also have 64.32../16 (0x40200000/16). we have a lot of CEs.
>
> Q1. if we use the two as the Rule_IPv4_Prefix_A and _B, can we map them t=
o
> a single Rule_IPv6_Prefix?
>
>
> Yes.
>
>
>      Rule IPv6 Prefix: 20010db        (2001:db0::/28)
>     CE1 IPv4 address:     c02 98765         (192.41.135.101)
>             CE1 PSID:              4
>         CE1 CE index:         987654
>  ---------------------------------------------------------------
> (1)  CE1 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52)
>      suppose we happen to have another CE somewhere else:
>
>     Rule IPv6 Prefix: 20010db
>      CE2 IPv4 address:    4020 9876          (64.32.152.118)
>              CE2 PSID:             54
>         CE2 CE index:         987654
>  ---------------------------------------------------------------
> (2)  CE2 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52)
>
> ambiguity happens and packet encapsulated with the same CE IPv6 address
> cannot be routed to the correct CE.
>
> This is not gonna happen, since the IPv6 address planing must be done
> natively considering nothing about the IPv4 in the very beginning. In you=
r
> example, I see you get a 2001:db0::/28 and you want to assign a /52 to ea=
ch
> CE, then ok, there will be 24 bits to distinguish CEs and should be assig=
ned
> continuously without any conflict. The next step is to check the availabl=
e
> IPv4 spaces we have for the given number of subscribers, then based on wh=
ich
> to design the rules. You made it in an opposite direction.
>
>
i understand what you mean is the following steps of rule_IPv6_prefix
decision:
1. list all the IPv4 addresses we have for the given number of subscribers;
2. aggregate these IPv4 addresses into contiguous blocks, suppose that you
start from the point of minimum waste (no unused IPv4 addresses are involve=
d
in the rules);
3. define the share-ratio and calculate the rule_IPv6_prefix for each
rule_IPv4_prefix defined in the step 2;
4. if your IPv6 space is far bigger to accommodate all the
rule_IPv6_prefixes, then go back to step 2 and try to make some relax
(trade-off), allowing unused IPv4 addresses involved in the rule to some
extent but gaining fewer rules.

my example was, from beginning, making a fixed rule_IPv6_prefix and two
large IPv4 prefixes, where it is possible that a lot of actually unused IPv=
4
addresses contained. does the "opposite direction" in you context mean 1) i
put CE index behind a predefined rule_IPv6_prefix, or 2) i made large IPv4
prefixes as the start point? for the point 2), i may assume that all the
addresses inside these two blocks are potentially used for our IPv4
subscribers and therefore there is not waste, and i actually meant the same
as you did. ;-)


> We break the boundary between the IPv4 address and port, use the bits (24
> bits in the examples above) together to identify the subscribers. The onl=
y
> reason I see to employ multiple IPv4 prefixes is we can't get a large eno=
ugh
> one. Additionally, in the second example above, you changed the sharing
> ratio to make a "24-bit index", then you should change the Rule IPv6 pref=
ix
> to, for example /27, for the two IPv4 prefixes of "same size". On the oth=
er
> hand, according to the consensus (if I get it correctly) of the interim
> meeting, more than one sharing ratios for the extended address case is no=
t
> desirable, that flexibility should be offered by stateful approaches.
>
>
sorry, a little confused. do you mean that, if we have 192.32../12 and
64.32../16 for the rule_IPv4_prefixes and we have the 4-bit PSID (me too,
don't desire to have more than one sharing ratios), then and we need each C=
E
IPv6 prefix as /52, then the rule_IPv6_prefixes for the two rules should be
/28 and /32, respectively, right?


>
>  therefore my answer to Q1, is NO, unless we carefully select IPv4
> addresses for CEs with giving up to use some of them, which have been so
> precious.
>
> Q2. then it must fine as long as we map them to different Rule IPv6
> Prefix. (?)
>
>     suppose CE1 is the same as (1). for 64.32../16, we use a longer stuff=
.
>     however, there is a CE3:
>
>     Rule IPv6 Prefix B: 20010db8       (2001:db8::/29)
>       CE3 IPv4 address:    4020 1876   (64.32.24.118)
>              CE3 PSID:             54
>         CE3 CE index:         987654
>  ---------------------------------------------------------------
> (3)  CE3 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52, woops!)
>
> ambiguity happens. then we may argue: using the ugly Rule_IPv6_Prefix_B i=
s
> the root of the problem! we have not to use a prefix covered by another.
>
>
> No, I think the bits of the same position are not additive. So, it should
> be a delegated prefix of "/53", right?
>

:P sorry for the typo but i have pointed out in the errata. :P however, eve=
n
though this is /53, and you will have, in the route table, both
   2001:db9:8765:4000::/52 =3D> route to CE1
   2001:db9:8765:4000::/53 =3D> route to CE3

but for the packet encapsulated with the destination address
2001:db9:8765:4000::200:5efe, you couldn't decide the route should go to CE=
3
instead of CE1. here the longest-match doesn't work. right?


>
>  Q3. what does the exclusiveness of Rule IPv6 Prefix mean?
>
>      if we have 2001:da0::/28 for the Rule_IPv6_Prefix, everyone will be
> happy. however, unfortunately, we have only one /28 IPv6 aggregate. then
> what we have to do is splitting the /28 block into mutually exclusive pie=
ces
> of small blocks. in the above example, if we have the following rule tabl=
e:
>
>     Rule_IPv4_Prefix Rule_IPv6_Prefix
>    -----------------------------------
>     192.32../12      2001:db0::/29
>     64.32../16       2001:db9::/29
>    -----------------------------------
>
> Yes, the exclusiveness. It's similar to what we do to further divide a
> subnet hierarchically. Hierarchies/exclusiveness avoid conflicts but lose
> the efficiency of addressing. BTW, the /29 example is the same as what I
> propose above. :-)
>
>
ok. the exclusiveness is cleared. thanks a lot for the help! then please
focus on the upper part further.

thanks again and regards,
maoke


>
>
>     then it will work fine within the /28 room in total. for 192.32../12,
> if the PSID is at least 4bit, then the *shortest* CE IPv6 prefix length i=
s
> 29 + (32 - 12) + 4 =3D 53 now, rather than 52 in the previous example. if=
 we
> have only or want to use only at most a /44 IPv6 prefix for the residual
> deployment, for the above 2 IPv4 networks, we are not able to safely depl=
oy
> the CE prefix shorter than /64, no matter how we take the effort!
>
>     Jacni once mentioned that if we have a /x IPv6 prefix while the
> "philosophy" of address planning decides to have /y for each CE-delegated
> network, then we can play the magic with the bits between the /x and the =
/y.
> i would like to point out here, because of the exclusiveness requirement,
> there is a hard limit for the power of the magic. if you have N IPv4
> residual addresses, you must at least satisfy the condition:
>
> Please see my comments above.
>
>
> Cheers,
> Jacni
>
>
>
>     (4)     y - x >=3D log(N)
>
>     when (4) is not true, cutting the rule into pieces does help almost
> nothing. i said "almost" because there is really a little we can achieve:
> there is really some IPv4 address seldom used for any routers,
> like 192.32.1.0. however, excluding such sort of addresses from the mappi=
ng
> scatters the mapping table into a huge number of /32-Rule_IPv4_Prefix and
> making the table size even longer than today's IPv4 routing table.
>
> just my 2 cents. execuse me if the humble calculation has any
> misunderstanding, and please point out without hesitation.
>
> best,
> maoke
>
>
> > 2011/9/22 R=E9mi Despr=E9s <despres.remi@laposte.net>:
> >> Alain, all,
> >>
> >> We have just posted a new version of our I-D on the proposed 4rd Addre=
ss
> Mapping.
> >> It is available at
> >> www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt
> >>
> >> Our presentation will be based on THIS version, technically simpler th=
an
> version -00.
> >> Major differences and their justifications will be briefly explained.
> >>
> >> Regards,
> >> RD
> >> _______________________________________________
> >> Softwires mailing list
> >> Softwires@ietf.org
> >> https://www.ietf.org/mailman/listinfo/softwires
> >>
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires
> >
>
>
>
>
> _______________________________________________
> Softwires mailing listSoftwires@ietf.orghttps://www.ietf.org/mailman/list=
info/softwires
>
>

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

<div>hi Jacni,=A0<br></div><div><br></div><div>thanks a lot for the reply. =
please see inline.=A0</div><br><div class=3D"gmail_quote">2011/10/17 Jacni =
Qin <span dir=3D"ltr">&lt;<a href=3D"mailto:jacni@jacni.com">jacni@jacni.co=
m</a>&gt;</span>=A0<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor=3D"#FFFFFF" text=3D"#000000"><font face=3D"Calibri">hi,<br>
      <br>
      Let me try to answer your questions, please see below,<br>
    </font><div class=3D"im"><br>
    On 10/15/2011 10:14 AM, Maoke wrote:
    <blockquote type=3D"cite">
      <div><font face=3D"courier new,monospace">=A0</font></div>
      <div><font face=3D"courier new,monospace">=A0</font></div>
      <div><font face=3D"courier new,monospace">hi Remi and all,</font></di=
v>
      <div><font face=3D"courier new,monospace">=A0</font></div>
      <div><font face=3D"courier new,monospace">a discussion on the
          address mapping in -01.txt, trying to fully understand the
          design. comments are requested. </font></div>
      <div><font face=3D"courier new,monospace">=A0</font></div>
      <div>
        <font face=3D"courier new,monospace">- what if there are two
          rules? </font></div>
      <div><font face=3D"courier new,monospace">=A0</font></div>
      <div><font face=3D"courier new,monospace">=A0 suppose we have
          192.32../12 (0x<font color=3D"#ff0000">c02</font>00000/12, i
          think it&#39;s not the 0x602 as Leaf previously mentioned, ;-)</f=
ont></div>
      <div><font face=3D"courier new,monospace">=A0 and we also have
          64.32../16 (0x<font color=3D"#ff6666">4020</font>0000/16). we
          have a lot of CEs. </font></div>
      <div>=A0</div>
      <div><font face=3D"courier new,monospace">Q1. if we use the two as
          the Rule_IPv4_Prefix_A and _B, can we map them to a single
          Rule_IPv6_Prefix? </font></div>
      <div>=A0</div>
    </blockquote></div>
    Yes.<div class=3D"im"><br>
    <br>
    <blockquote type=3D"cite">
      <div><font face=3D"courier new,monospace">=A0=A0=A0 Rule IPv6
          Prefix:=A020010db=A0=A0=A0=A0=A0=A0=A0 (2001:db0::/28)</font></di=
v>
      <div><font face=3D"courier new,monospace">=A0=A0=A0 CE1 IPv4 address:=
=A0=A0=A0=A0
          c02=A098765=A0=A0=A0=A0=A0=A0=A0=A0=A0(192.41.135.101)</font></di=
v>
      <div><font face=3D"courier new,monospace">=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0CE1
          PSID:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A04=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 </font></div>
      <div><font face=3D"Courier New">=A0=A0=A0=A0=A0=A0=A0 CE1 CE index:=
=A0=A0=A0=A0=A0=A0=A0=A0 987654</font></div>
      <font face=3D"Courier New">
        <div><font face=3D"Courier New">-----------------------------------=
----------------------------</font></div>
        <div>(1)=A0 CE1 IPv6 prefix: 20010db=A0987654=A0(<font color=3D"#ff=
0000">2001:db9:8765:4000::/52</font>)</div>
      </font><font face=3D"courier new,monospace">
        <div>
          <div><font face=3D"courier new,monospace">=A0=A0=A0 suppose we ha=
ppen
              to have another CE somewhere else:</font></div>
          <div>=A0</div>
          <div><font face=3D"courier new,monospace">=A0=A0=A0 Rule IPv6 Pre=
fix:
              20010db</font></div>
        </div>
      </font>
      <div><font face=3D"courier new,monospace">=A0=A0=A0 CE2 IPv4 address:=
=A0=A0=A0
          4020=A09876=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0(64.32.152.118)</font></=
div>
      <div>
        <div><font face=3D"courier new,monospace">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 CE2
            PSID:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A054=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 </font></div>
        <div><font face=3D"Courier New">=A0=A0=A0=A0=A0=A0=A0=A0CE2 CE
            index:=A0=A0=A0=A0=A0=A0=A0=A0=A0987654</font></div>
        <font face=3D"Courier New">
          <div><font face=3D"Courier New">---------------------------------=
------------------------------</font></div>
          <div>(2)=A0 CE2 IPv6 prefix: 20010db=A0987654 (<font color=3D"#ff=
9966">2001:db9:8765:4000::/52</font>)</div>
        </font></div>
      <div>=A0</div>
      <div><font face=3D"Courier New">ambiguity happens and=A0packet
          encapsulated=A0with the same CE IPv6 address cannot be routed to
          the correct CE. </font></div>
    </blockquote></div>
    This is not gonna happen, since the IPv6 address planing must be
    done natively considering nothing about the IPv4 in the very
    beginning. In your example, I see you get a 2001:db0::/28 and you
    want to assign a /52 to each CE, then ok, there will be 24 bits to
    distinguish CEs and should be assigned continuously without any
    conflict. The next step is to check the available IPv4 spaces we
    have for the given number of subscribers, then based on which to
    design the rules. You made it in an opposite direction.<br>
    <br>
    </div></blockquote><div><br></div><div>i understand what you mean is th=
e following steps of rule_IPv6_prefix decision:=A0</div><div>1. list all th=
e IPv4 addresses we have for the given number of subscribers; </div><div>
2. aggregate these IPv4 addresses into contiguous blocks, suppose that you =
start from the point of minimum waste (no unused IPv4 addresses are involve=
d in the rules);</div><div>3. define the share-ratio and calculate the rule=
_IPv6_prefix for each rule_IPv4_prefix defined in the step 2;=A0</div>
<div>4. if your IPv6 space is far bigger to accommodate all the rule_IPv6_p=
refixes, then go back to step 2 and try to make some relax (trade-off), all=
owing unused IPv4 addresses involved in the rule to some extent but gaining=
 fewer rules.=A0</div>
<div><br></div><div>my example was, from beginning, making a fixed rule_IPv=
6_prefix and two large IPv4 prefixes, where it is possible that a lot of ac=
tually unused IPv4 addresses contained. does the &quot;opposite direction&q=
uot; in you context mean 1) i put CE index behind a predefined rule_IPv6_pr=
efix, or 2) i made large IPv4 prefixes as the start point? for the point 2)=
, i may assume that all the addresses inside these two blocks are potential=
ly used for our IPv4 subscribers and therefore there is not waste, and i ac=
tually meant the same as you did. ;-)=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor=3D"#FFFFFF" text=
=3D"#000000">We break the boundary between the IPv4 address and port, use t=
he
    bits (24 bits in the examples above) together to identify the
    subscribers. The only reason I see to employ multiple IPv4 prefixes
    is we can&#39;t get a large enough one. Additionally, in the second
    example above, you changed the sharing ratio to make a &quot;24-bit
    index&quot;, then you should change the Rule IPv6 prefix to, for exampl=
e
    /27, for the two IPv4 prefixes of &quot;same size&quot;. On the other h=
and,
    according to the consensus (if I get it correctly) of the interim
    meeting, more than one sharing ratios for the extended address case
    is not desirable, that flexibility should be offered by stateful
    approaches.<div class=3D"im"><br></div></div></blockquote><div><br></di=
v><div>sorry, a little confused. do you mean that, if we have 192.32../12 a=
nd 64.32../16 for the rule_IPv4_prefixes and we have the 4-bit PSID (me too=
, don&#39;t desire to have more than one sharing ratios), then and we need =
each CE IPv6 prefix as /52, then the rule_IPv6_prefixes for the two rules s=
hould be /28 and /32, respectively, right?=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor=3D"#FFFFFF" text=
=3D"#000000"><div class=3D"im">
    <br>
    <blockquote type=3D"cite">
      <div><font face=3D"Courier New">therefore my answer to Q1, is NO, </f=
ont><font face=3D"Courier New">unless we carefully select IPv4 addresses
          for CEs with giving up to use some of them, which have been so
          precious. </font></div>
      <div>=A0</div>
      <div><font face=3D"Courier New">Q2. then it must fine as long as we
          map them to <font color=3D"#ff0000">different</font> Rule IPv6
          Prefix. (?)</font></div>
      <div>=A0</div>
      <div><font face=3D"Courier New">=A0=A0=A0=A0suppose CE1 is the same a=
s (1).
          for 64.32../16, we use a longer stuff.</font></div>
      <div><font face=3D"Courier New">=A0=A0=A0 however, there is a CE3:</f=
ont></div>
      <div><font face=3D"courier new,monospace">=A0</font></div>
      <font face=3D"courier new,monospace">
        <div>
          <div>
            <div><font face=3D"courier new,monospace">=A0=A0Rule IPv6 Prefi=
x
                B: 20010db<font color=3D"#ff0000">8</font>=A0=A0=A0=A0=A0=
=A0
                (2001:db8::/<font color=3D"#ff0000">29</font>)</font></div>
          </div>
        </div>
      </font>
      <div>
        <div><font face=3D"courier new,monospace">=A0=A0=A0 CE3 IPv4 addres=
s: =A0=A0
            4020 <font color=3D"#ff0000">1</font><font color=3D"#000000">87=
6</font>=A0=A0=A0(64.32.24.118)</font></div>
        <div>
          <div><font face=3D"courier new,monospace">=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 =A0 CE3
              PSID:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A054=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 </font></div>
          <div><font face=3D"Courier New">=A0=A0=A0=A0=A0=A0=A0=A0CE3 CE in=
dex:=A0=A0=A0=A0=A0=A0=A0=A0=A0<font color=3D"#ff0000">9</font>87654</font>=
</div>
          <font face=3D"Courier New">
            <div><font face=3D"Courier New">-------------------------------=
--------------------------------</font></div>
            <div>(3)=A0 CE3 IPv6 prefix: 20010db=A0987654 (<font color=3D"#=
ff9966">2001:db9:8765:4000::/52, woops!</font>)</div>
          </font></div>
      </div>
      <div>=A0</div>
      <div><font face=3D"Courier New">ambiguity happens. then=A0we may
          argue: using the ugly Rule_IPv6_Prefix_B is the root of the
          problem! we have not to use a prefix covered by another. </font><=
/div>
      <div>=A0</div>
    </blockquote></div>
    No, I think the bits of the same position are not additive. So, it
    should be a delegated prefix of &quot;/53&quot;, right?</div></blockquo=
te><div><br></div><div>:P sorry for the typo but i have pointed out in the =
errata. :P however, even though this is /53, and you will have, in the rout=
e table, both=A0</div>
<div>=A0 =A02001:db9:8765:4000::/52 =3D&gt; route to CE1</div><div>=A0 =A02=
001:db9:8765:4000::/53 =3D&gt; route to CE3</div><div><br></div><div>but fo=
r the packet encapsulated with the destination address 2001:db9:8765:4000::=
200:5efe, you couldn&#39;t decide the route should go to CE3 instead of CE1=
. here the longest-match doesn&#39;t work. right?</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor=3D"#FFFFFF" text=
=3D"#000000"><div class=3D"im"><br>
    <blockquote type=3D"cite">
      <div><font face=3D"Courier New">Q3. what does the <font color=3D"#ff0=
000">exclusiveness</font> of Rule IPv6 Prefix
          mean? </font></div>
      <div>=A0</div>
      <div>
        <font face=3D"Courier New">=A0=A0=A0 if we have 2001:da0::/28 for t=
he
          Rule_IPv6_Prefix, everyone will be happy. however,
          unfortunately, we have only one /28 IPv6 aggregate. then what
          we have to do is splitting the /28 block into mutually
          exclusive pieces of small blocks. in the above example, if we
          have the following rule table:</font></div>
      <div>=A0</div>
      <div><font face=3D"Courier New">=A0=A0=A0=A0Rule_IPv4_Prefix=A0Rule_I=
Pv6_Prefix</font></div>
      <div><font face=3D"Courier New">=A0=A0
          -----------------------------------</font></div>
      <div><font face=3D"Courier New">=A0=A0=A0=A0192.32../12=A0=A0=A0=A0=
=A0 2001:db0::/<font color=3D"#ff0000">29</font></font></div>
      <div><font face=3D"Courier New">=A0=A0=A0 64.32../16=A0=A0=A0=A0=A0=
=A0=A02001:db9::/<font color=3D"#ff0000">29</font></font></div>
      <div><font face=3D"Courier New">=A0=A0
          -----------------------------------</font></div>
    </blockquote></div>
    Yes, the exclusiveness. It&#39;s similar to what we do to further divid=
e
    a subnet hierarchically. Hierarchies/exclusiveness avoid conflicts
    but lose the efficiency of addressing. BTW, the /29 example is the
    same as what I propose above. :-)<div class=3D"im"><br></div></div></bl=
ockquote><div><br></div><div>ok. the exclusiveness is cleared. thanks a lot=
 for the help! then please focus on the upper part further.=A0</div><div><b=
r>
</div><div>thanks again and regards,</div><div>maoke</div><div>=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex;"><div bgcolor=3D"#FFFFFF" text=3D"#000000"><div=
 class=3D"im">

    =A0<br>
    <blockquote type=3D"cite">
      <div><font face=3D"Courier New">=A0=A0=A0 then it will work fine with=
in
          the /28 room in total. for 192.32../12, if the PSID is at
          least 4bit, then the *shortest* CE IPv6 prefix length is 29 +
          (32 - 12) + 4 =3D 53 now, rather than 52 in the previous
          example. if we have only or want to use only at most a /44
          IPv6 prefix for the residual deployment, for the above 2 IPv4
          networks, we are not able to safely deploy the CE prefix
          shorter than /64, no matter how we take the effort! </font></div>
      <div>=A0</div>
      <div><font face=3D"Courier New">=A0=A0=A0 Jacni once mentioned that i=
f we
          have a /x IPv6 prefix while the &quot;philosophy&quot; of address
          planning decides to have /y for each CE-delegated network,
          then we can play the magic with the bits between the /x and
          the /y. i would like to point out here, because of the
          exclusiveness requirement, there is a hard limit=A0for the power
          of=A0the magic. if you have N IPv4 residual addresses, you must
          at least=A0satisfy the condition:</font></div>
    </blockquote></div>
    Please see my comments above.<br>
    <br>
    <br>
    Cheers,<br><font color=3D"#888888">
    Jacni</font><div><div class=3D"h5"><br>
    <br>
    <blockquote type=3D"cite">
      <div>=A0</div>
      <div><font face=3D"Courier New">=A0=A0=A0 (4)=A0=A0=A0=A0 y - x &gt;=
=3D log(N)</font></div>
      <div>=A0</div>
      <div><font face=3D"Courier New">=A0=A0=A0 when (4) is not true, cutti=
ng
          the rule into pieces does help almost nothing. i said &quot;almos=
t&quot;
          because there is really a little we can achieve: there is
          really some IPv4 address=A0seldom=A0used for any routers,
          like=A0192.32.1.0. however,=A0excluding such sort of addresses
          from the mapping scatters the mapping table=A0into a huge number
          of=A0/32-Rule_IPv4_Prefix and making the table size=A0even longer
          than today&#39;s IPv4 routing table. </font></div>
      <div>=A0</div>
      <div><font face=3D"Courier New">just my 2 cents. execuse me if the
          humble calculation=A0has any misunderstanding, and please point
          out without hesitation.</font></div>
      <div>=A0</div>
      <div><font face=3D"Courier New">best,</font></div>
      <div><font face=3D"Courier New">maoke</font></div>
      <div>=A0</div>
      <div>=A0</div>
      <div><font face=3D"courier new,monospace">&gt; 2011/9/22 R=E9mi
          Despr=E9s &lt;<a href=3D"mailto:despres.remi@laposte.net" target=
=3D"_blank">despres.remi@laposte.net</a>&gt;:</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; Alain, all,</font>=
</div>
      <div><font face=3D"courier new,monospace">&gt;&gt;</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; We have just
          posted a new version of our I-D on the proposed 4rd Address
          Mapping.</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; It is available
          at</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; <a href=3D"http://=
www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt" target=3D"_bl=
ank">www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt</a></font=
></div>

      <div><font face=3D"courier new,monospace">&gt;&gt;</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; Our presentation
          will be based on THIS version, technically simpler than
          version -00.</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; Major differences
          and their justifications will be briefly explained.</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt;</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; Regards,</font></d=
iv>
      <div><font face=3D"courier new,monospace">&gt;&gt; RD</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt;
          _______________________________________________</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; Softwires mailing
          list</font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; <a href=3D"mailto:=
Softwires@ietf.org" target=3D"_blank">Softwires@ietf.org</a></font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt; <a href=3D"https:/=
/www.ietf.org/mailman/listinfo/softwires" target=3D"_blank">https://www.iet=
f.org/mailman/listinfo/softwires</a></font></div>
      <div><font face=3D"courier new,monospace">&gt;&gt;</font></div>
      <div><font face=3D"courier new,monospace">&gt;
          _______________________________________________</font></div>
      <div><font face=3D"courier new,monospace">&gt; Softwires mailing
          list</font></div>
      <div><font face=3D"courier new,monospace">&gt; <a href=3D"mailto:Soft=
wires@ietf.org" target=3D"_blank">Softwires@ietf.org</a></font></div>
      <div><font face=3D"courier new,monospace">&gt; <a href=3D"https://www=
.ietf.org/mailman/listinfo/softwires" target=3D"_blank">https://www.ietf.or=
g/mailman/listinfo/softwires</a></font></div>
      <div><font face=3D"courier new,monospace">&gt;</font></div>
      <div><font face=3D"courier new,monospace">=A0</font></div>
      <div><font face=3D"courier new,monospace">=A0</font></div>
      <br>
     =20
      <br>
      <pre>_______________________________________________
Softwires mailing list
<a href=3D"mailto:Softwires@ietf.org" target=3D"_blank">Softwires@ietf.org<=
/a>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/softwires</a>
</pre>    </blockquote>
  </div></div></div>

</blockquote></div><br>

--0016e65da6eedfef8204af76a17c--

From fibrib@gmail.com  Sun Oct 16 22:27:13 2011
Return-Path: <fibrib@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 595AC21F8B22 for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 22:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.99
X-Spam-Level: 
X-Spam-Status: No, score=-2.99 tagged_above=-999 required=5 tests=[AWL=0.308,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exDdEWHdlknj for <softwires@ietfa.amsl.com>; Sun, 16 Oct 2011 22:27:12 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8461621F8B24 for <softwires@ietf.org>; Sun, 16 Oct 2011 22:27:12 -0700 (PDT)
Received: by qyk34 with SMTP id 34so603106qyk.10 for <softwires@ietf.org>; Sun, 16 Oct 2011 22:27:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3gvPlXbEeu28DmV46KR64oTkjarDVxORnDmUVfpchYg=; b=v4RL0VUa1KyHUqAGN2XrIlBPgkM7I2QQe6mixi64a4fPYBJpJIw2LsyLUH9HKNIhLN V7W11jkrt2jtMn76zAQ1VRfkA7Drm34gYMEDXuJeqqkMczqJWmdet+f2gEFjWt1rJMZn 4xFbTDNyOUUk5/gc1odeT+GcefJ9lR6D7XkLk=
MIME-Version: 1.0
Received: by 10.229.80.16 with SMTP id r16mr3781774qck.107.1318829230093; Sun, 16 Oct 2011 22:27:10 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Sun, 16 Oct 2011 22:27:10 -0700 (PDT)
In-Reply-To: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net>
References: <187B1ACE-8FB8-4C8C-8130-03DCF10772CF@laposte.net>
Date: Mon, 17 Oct 2011 14:27:10 +0900
Message-ID: <CAFUBMqXoEGd5RA4zwuZBboZ0C=BGXio9LOAS=bjG2PHTuU++1w@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=0016364ee764c77aa704af77db02
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Unifying Double Translation and Encapsulation for 4rd (4rd-U)
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, 17 Oct 2011 05:27:13 -0000

--0016364ee764c77aa704af77db02
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Remi,

i would like to follow your idea of keeping end-to-end transparency of DF
bit in double translation.

1. keeping DF transparency might be really significant

we noticed that the fragment in IPv4 is rare but it doesn't mean the DF is
fairly useless. in contrast, today's IPv4 has very small percentage of
fragment just because we are favored by the DF bit and the path MTU
discovery functionality based on it. if we observe the percentage of DF=3D1
and DF=3D0 packets, we would see DF is not trivial. forcing DF =3D 0 at the
boundary from IPv6 to IPv4 may disable the PMTU discovery in the destinatio=
n
IPv4 domain; forcing DF =3D 1, though, may bring worse performance for the
applications that do not care of being fragmented but wouldn't like to be
dropped due to packet-too-big.

2. define a reserved bit in IPv6 fragment header for the DF bit of the
IPv4-translated packets

putting is the DF and IPv4 identifier into the fragment header is a good
idea. however, considering the double translation is a case of translation.
it is possible that a src host with an IPv4-translatable IPv6 address
generates a fragment header with a 32-bit identifier happening to have the
first 16 bit as either 0x8000 or 0x0000, making a fake D bit in your curren=
t
proposal. i'd prefer to use one of the reserved bits in the fragment header
for the DF.

how do you and others think?

thanks,
maoke

2011/10/12 R=E9mi Despr=E9s <despres.remi@laposte.net>

> Hello all,
>
> The following draft has just been posted:
> tools.ietf.org/html/draft-despres-softwire-4rd-u-00.
>
> Hope it will be useful for your continuing work on stateless solutions in
> Softwire.
>
> Clarification questions are most welcome.
>
> Regards,
> RD
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

<div>hi Remi,=A0</div><div><br></div><div>i would like to follow your idea =
of keeping end-to-end transparency of DF bit in double translation.=A0</div=
><div><br></div><div>1. keeping DF transparency might be really significant=
</div>
<div><br></div><div>we noticed that the fragment in IPv4 is rare but it doe=
sn&#39;t mean the DF is fairly useless. in contrast, today&#39;s IPv4 has v=
ery small percentage of fragment just because we are favored by the DF bit =
and the path MTU discovery functionality based on it. if we observe the per=
centage of DF=3D1 and DF=3D0 packets, we would see DF is not trivial. forci=
ng DF =3D 0 at the boundary from IPv6 to IPv4 may disable the PMTU discover=
y in the destination IPv4 domain; forcing DF =3D 1, though, may bring worse=
 performance for the applications that do not care of being fragmented but =
wouldn&#39;t like to be dropped due to packet-too-big.=A0</div>
<div><br></div><div>2. define a reserved bit in IPv6 fragment header for th=
e DF bit of the IPv4-translated packets</div><div><br></div><div>putting is=
 the DF and IPv4 identifier into the fragment header is a good idea. howeve=
r, considering the double translation is a case of translation. it is possi=
ble that a src host with an IPv4-translatable IPv6 address generates a frag=
ment header with a 32-bit identifier happening to have the first 16 bit as =
either 0x8000 or 0x0000, making a fake D bit in your current proposal. i&#3=
9;d prefer to use one of the reserved bits in the fragment header for the D=
F.=A0</div>
<div><br></div><div>how do you and others think?=A0</div><div><br></div><di=
v>thanks,=A0</div><div>maoke</div><div><br></div><div class=3D"gmail_quote"=
>2011/10/12 R=E9mi Despr=E9s <span dir=3D"ltr">&lt;<a href=3D"mailto:despre=
s.remi@laposte.net">despres.remi@laposte.net</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hello all,<br>
<br>
The following draft has just been posted:<br>
<a href=3D"http://tools.ietf.org/html/draft-despres-softwire-4rd-u-00" targ=
et=3D"_blank">tools.ietf.org/html/draft-despres-softwire-4rd-u-00</a>.<br>
<br>
Hope it will be useful for your continuing work on stateless solutions in S=
oftwire.<br>
<br>
Clarification questions are most welcome.<br>
<br>
Regards,<br>
RD<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>
</blockquote></div><br>

--0016364ee764c77aa704af77db02--

From jacni@jacni.com  Mon Oct 17 00:56:17 2011
Return-Path: <jacni@jacni.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 E189921F84E5 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 00:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.973
X-Spam-Level: 
X-Spam-Status: No, score=-1.973 tagged_above=-999 required=5 tests=[AWL=0.314,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atIWqAvlVYpg for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 00:56:16 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 5543821F84C3 for <softwires@ietf.org>; Mon, 17 Oct 2011 00:56:15 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 3AD8438008A for <softwires@ietf.org>; Mon, 17 Oct 2011 03:56:14 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id B9C77860004 for <softwires@ietf.org>; Mon, 17 Oct 2011 15:56:10 +0800 (CST)
Received: from [172.18.50.22] (unknown [221.11.61.30]) by app (Coremail) with SMTP id +AWowJDryASS35tO110dAA--.38070S2; Mon, 17 Oct 2011 15:56:05 +0800 (CST)
Message-ID: <4E9BE001.3060202@jacni.com>
Date: Mon, 17 Oct 2011 15:57:53 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com>
In-Reply-To: <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060403010205090909090801"
X-CM-TRANSID: +AWowJDryASS35tO110dAA--.38070S2
X-Coremail-Antispam: 1UD129KBjvJXoW3GF1UZF4DGr1kJF4UCw1DGFg_yoWftF1Upr WftF13KFyDJF18Cws7uw1UWr1rAFZ5J3yUJr98Jry0ka45AF10vrsYkr4rZFWUXrWrJw4a vrWqkry8G3Z8ZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUcYb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VWkKwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK64x0aVW7Gw IE548m6rI_Jw1UWr17M2kK6IIYrVAqxI0j4VAqrcv_Jw1UGr1DM2vj6xkI62vS6c8GOVWU tr1rJFylYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UM4x0Y48IcV AKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI 7VAKI48JMxCIbVAxMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr4UvcSsGvfC2Kf nxnUUI43ZEXa7IU0S_MDUUUUU==
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEEEko7lOrFuwAAsn
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 17 Oct 2011 07:56:18 -0000

This is a multi-part message in MIME format.
--------------060403010205090909090801
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

hi,

On 10/17/2011 11:59 AM, Maoke wrote:
> hi Jacni,
>
> thanks a lot for the reply. please see inline.
>
> 2011/10/17 Jacni Qin <jacni@jacni.com <mailto:jacni@jacni.com>>
>
>     hi,
>
>     Let me try to answer your questions, please see below,
>
>     On 10/15/2011 10:14 AM, Maoke wrote:
>>     hi Remi and all,
>>     a discussion on the address mapping in -01.txt, trying to fully
>>     understand the design. comments are requested.
>>     - what if there are two rules?
>>       suppose we have 192.32../12 (0xc0200000/12, i think it's not
>>     the 0x602 as Leaf previously mentioned, ;-)
>>       and we also have 64.32../16 (0x40200000/16). we have a lot of CEs.
>>     Q1. if we use the two as the Rule_IPv4_Prefix_A and _B, can we
>>     map them to a single Rule_IPv6_Prefix?
>     Yes.
>
>
>>         Rule IPv6 Prefix: 20010db        (2001:db0::/28)
>>         CE1 IPv4 address:     c02 98765         (192.41.135.101)
>>                 CE1 PSID:              4
>>             CE1 CE index:         987654
>>     ---------------------------------------------------------------
>>     (1)  CE1 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52)
>>         suppose we happen to have another CE somewhere else:
>>         Rule IPv6 Prefix: 20010db
>>         CE2 IPv4 address:    4020 9876          (64.32.152.118)
>>                 CE2 PSID:             54
>>             CE2 CE index:         987654
>>     ---------------------------------------------------------------
>>     (2)  CE2 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52)
>>     ambiguity happens and packet encapsulated with the same CE IPv6
>>     address cannot be routed to the correct CE.
>     This is not gonna happen, since the IPv6 address planing must be
>     done natively considering nothing about the IPv4 in the very
>     beginning. In your example, I see you get a 2001:db0::/28 and you
>     want to assign a /52 to each CE, then ok, there will be 24 bits to
>     distinguish CEs and should be assigned continuously without any
>     conflict. The next step is to check the available IPv4 spaces we
>     have for the given number of subscribers, then based on which to
>     design the rules. You made it in an opposite direction.
>
>
> i understand what you mean is the following steps of rule_IPv6_prefix 
> decision:
> 1. list all the IPv4 addresses we have for the given number of 
> subscribers;
> 2. aggregate these IPv4 addresses into contiguous blocks, suppose that 
> you start from the point of minimum waste (no unused IPv4 addresses 
> are involved in the rules);
> 3. define the share-ratio and calculate the rule_IPv6_prefix for each 
> rule_IPv4_prefix defined in the step 2;
> 4. if your IPv6 space is far bigger to accommodate all the 
> rule_IPv6_prefixes, then go back to step 2 and try to make some relax 
> (trade-off), allowing unused IPv4 addresses involved in the rule to 
> some extent but gaining fewer rules.
>
> my example was, from beginning, making a fixed rule_IPv6_prefix and 
> two large IPv4 prefixes, where it is possible that a lot of actually 
> unused IPv4 addresses contained. does the "opposite direction" in you 
> context mean 1) i put CE index behind a predefined rule_IPv6_prefix, 
> or 2) i made large IPv4 prefixes as the start point?
I meant the latter one (not 100% ;-)). You can aggregate these IPv4 
prefixes into contiguous blocks, by for instance as you proposed, 
changing the sharing ratio of the second example (64.32../16), 4-bit 
PSID to 8-bit PSID to make a 24-bit CE index as the first example 
(192.32../12). The aggregation should be done through the design of Rule 
IPv6 prefixes. Pick a /27 which contains two /28, use the first /28 as 
the Rule IPv6 Prefix for 192.32../12, then the second /28 contains two 
/29, preserve the first /29, then the second /29 contains two /30 ..., 
finally pick a /32 as the Rule IPv6 Prefix for 64.32../16. Then the two 
rules share the same /27 and can be aggregated.

> for the point 2), i may assume that all the addresses inside these two 
> blocks are potentially used for our IPv4 subscribers and therefore 
> there is not waste, and i actually meant the same as you did. ;-)
>
>     We break the boundary between the IPv4 address and port, use the
>     bits (24 bits in the examples above) together to identify the
>     subscribers. The only reason I see to employ multiple IPv4
>     prefixes is we can't get a large enough one. Additionally, in the
>     second example above, you changed the sharing ratio to make a
>     "24-bit index", then you should change the Rule IPv6 prefix to,
>     for example /27, for the two IPv4 prefixes of "same size". On the
>     other hand, according to the consensus (if I get it correctly) of
>     the interim meeting, more than one sharing ratios for the extended
>     address case is not desirable, that flexibility should be offered
>     by stateful approaches.
>
>
> sorry, a little confused. do you mean that, if we have 192.32../12 and 
> 64.32../16 for the rule_IPv4_prefixes and we have the 4-bit PSID (me 
> too, don't desire to have more than one sharing ratios), then and we 
> need each CE IPv6 prefix as /52, then the rule_IPv6_prefixes for the 
> two rules should be /28 and /32, respectively, right?
Yes, and please see my comments above.

>
>>     therefore my answer to Q1, is NO, unless we carefully select IPv4
>>     addresses for CEs with giving up to use some of them, which have
>>     been so precious.
>>     Q2. then it must fine as long as we map them to different Rule
>>     IPv6 Prefix. (?)
>>         suppose CE1 is the same as (1). for 64.32../16, we use a
>>     longer stuff.
>>         however, there is a CE3:
>>       Rule IPv6 Prefix B: 20010db8       (2001:db8::/29)
>>         CE3 IPv4 address:    4020 1876   (64.32.24.118)
>>                 CE3 PSID:             54
>>             CE3 CE index: 987654
>>     ---------------------------------------------------------------
>>     (3)  CE3 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52,
>>     woops!)
>>     ambiguity happens. then we may argue: using the ugly
>>     Rule_IPv6_Prefix_B is the root of the problem! we have not to use
>>     a prefix covered by another.
>     No, I think the bits of the same position are not additive. So, it
>     should be a delegated prefix of "/53", right?
>
>
> :P sorry for the typo but i have pointed out in the errata. :P 
> however, even though this is /53, and you will have, in the route 
> table, both
>    2001:db9:8765:4000::/52 => route to CE1
>    2001:db9:8765:4000::/53 => route to CE3
>
> but for the packet encapsulated with the destination address 
> 2001:db9:8765:4000::200:5efe, you couldn't decide the route should go 
> to CE3 instead of CE1. here the longest-match doesn't work. right?
I guess the second delegated prefix should be 2001:db8:1876:5400::/53

>
>>     Q3. what does the exclusiveness of Rule IPv6 Prefix mean?
>>         if we have 2001:da0::/28 for the Rule_IPv6_Prefix, everyone
>>     will be happy. however, unfortunately, we have only one /28 IPv6
>>     aggregate. then what we have to do is splitting the /28 block
>>     into mutually exclusive pieces of small blocks. in the above
>>     example, if we have the following rule table:
>>         Rule_IPv4_Prefix Rule_IPv6_Prefix
>>        -----------------------------------
>>         192.32../12      2001:db0::/29
>>         64.32../16       2001:db9::/29
>>        -----------------------------------
>     Yes, the exclusiveness. It's similar to what we do to further
>     divide a subnet hierarchically. Hierarchies/exclusiveness avoid
>     conflicts but lose the efficiency of addressing. BTW, the /29
>     example is the same as what I propose above. :-)
>
>
> ok. the exclusiveness is cleared. thanks a lot for the help! then 
> please focus on the upper part further.
Great, we're on the same page.


Cheers,
Jacni

>
> thanks again and regards,
> maoke
>
>
>>         then it will work fine within the /28 room in total. for
>>     192.32../12, if the PSID is at least 4bit, then the *shortest* CE
>>     IPv6 prefix length is 29 + (32 - 12) + 4 = 53 now, rather than 52
>>     in the previous example. if we have only or want to use only at
>>     most a /44 IPv6 prefix for the residual deployment, for the above
>>     2 IPv4 networks, we are not able to safely deploy the CE prefix
>>     shorter than /64, no matter how we take the effort!
>>         Jacni once mentioned that if we have a /x IPv6 prefix while
>>     the "philosophy" of address planning decides to have /y for each
>>     CE-delegated network, then we can play the magic with the bits
>>     between the /x and the /y. i would like to point out here,
>>     because of the exclusiveness requirement, there is a hard
>>     limit for the power of the magic. if you have N IPv4 residual
>>     addresses, you must at least satisfy the condition:
>     Please see my comments above.
>
>
>     Cheers,
>     Jacni
>
>
>>         (4)     y - x >= log(N)
>>         when (4) is not true, cutting the rule into pieces does help
>>     almost nothing. i said "almost" because there is really a little
>>     we can achieve: there is really some IPv4 address seldom used for
>>     any routers, like 192.32.1.0. however, excluding such sort of
>>     addresses from the mapping scatters the mapping table into a huge
>>     number of /32-Rule_IPv4_Prefix and making the table size even
>>     longer than today's IPv4 routing table.
>>     just my 2 cents. execuse me if the humble calculation has any
>>     misunderstanding, and please point out without hesitation.
>>     best,
>>     maoke
>>     > 2011/9/22 Rémi Després <despres.remi@laposte.net
>>     <mailto:despres.remi@laposte.net>>:
>>     >> Alain, all,
>>     >>
>>     >> We have just posted a new version of our I-D on the proposed
>>     4rd Address Mapping.
>>     >> It is available at
>>     >> www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt
>>     <http://www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt>
>>     >>
>>     >> Our presentation will be based on THIS version, technically
>>     simpler than version -00.
>>     >> Major differences and their justifications will be briefly
>>     explained.
>>     >>
>>     >> Regards,
>>     >> RD
>>     >> _______________________________________________
>>     >> Softwires mailing list
>>     >> Softwires@ietf.org <mailto:Softwires@ietf.org>
>>     >> https://www.ietf.org/mailman/listinfo/softwires
>>     >>
>>     > _______________________________________________
>>     > Softwires mailing list
>>     > Softwires@ietf.org <mailto:Softwires@ietf.org>
>>     > https://www.ietf.org/mailman/listinfo/softwires
>>     >
>>
>>
>>     _______________________________________________
>>     Softwires mailing list
>>     Softwires@ietf.org  <mailto:Softwires@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/softwires
>
>

--------------060403010205090909090801
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 10/17/2011 11:59 AM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com"
      type="cite">
      <div>hi Jacni,&nbsp;<br>
      </div>
      <div><br>
      </div>
      <div>thanks a lot for the reply. please see inline.&nbsp;</div>
      <br>
      <div class="gmail_quote">2011/10/17 Jacni Qin <span dir="ltr">&lt;<a
            moz-do-not-send="true" href="mailto:jacni@jacni.com">jacni@jacni.com</a>&gt;</span>&nbsp;
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000"><font face="Calibri">hi,<br>
              <br>
              Let me try to answer your questions, please see below,<br>
            </font>
            <div class="im"><br>
              On 10/15/2011 10:14 AM, Maoke wrote:
              <blockquote type="cite">
                <div><font face="courier new,monospace">&nbsp;</font></div>
                <div><font face="courier new,monospace">&nbsp;</font></div>
                <div><font face="courier new,monospace">hi Remi and all,</font></div>
                <div><font face="courier new,monospace">&nbsp;</font></div>
                <div><font face="courier new,monospace">a discussion on
                    the address mapping in -01.txt, trying to fully
                    understand the design. comments are requested. </font></div>
                <div><font face="courier new,monospace">&nbsp;</font></div>
                <div> <font face="courier new,monospace">- what if
                    there are two rules? </font></div>
                <div><font face="courier new,monospace">&nbsp;</font></div>
                <div><font face="courier new,monospace">&nbsp; suppose we
                    have 192.32../12 (0x<font color="#ff0000">c02</font>00000/12,
                    i think it's not the 0x602 as Leaf previously
                    mentioned, ;-)</font></div>
                <div><font face="courier new,monospace">&nbsp; and we also
                    have 64.32../16 (0x<font color="#ff6666">4020</font>0000/16).
                    we have a lot of CEs. </font></div>
                <div>&nbsp;</div>
                <div><font face="courier new,monospace">Q1. if we use
                    the two as the Rule_IPv4_Prefix_A and _B, can we map
                    them to a single Rule_IPv6_Prefix? </font></div>
                <div>&nbsp;</div>
              </blockquote>
            </div>
            Yes.
            <div class="im"><br>
              <br>
              <blockquote type="cite">
                <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; Rule IPv6
                    Prefix:&nbsp;20010db&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (2001:db0::/28)</font></div>
                <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; CE1 IPv4
                    address:&nbsp;&nbsp;&nbsp;&nbsp; c02&nbsp;98765&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(192.41.135.101)</font></div>
                <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CE1
                    PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></div>
                <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CE1 CE
                    index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 987654</font></div>
                <font face="Courier New">
                  <div><font face="Courier New">---------------------------------------------------------------</font></div>
                  <div>(1)&nbsp; CE1 IPv6 prefix: 20010db&nbsp;987654&nbsp;(<font
                      color="#ff0000">2001:db9:8765:4000::/52</font>)</div>
                </font><font face="courier new,monospace">
                  <div>
                    <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; suppose
                        we happen to have another CE somewhere else:</font></div>
                    <div>&nbsp;</div>
                    <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; Rule
                        IPv6 Prefix: 20010db</font></div>
                  </div>
                </font>
                <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; CE2 IPv4
                    address:&nbsp;&nbsp;&nbsp; 4020&nbsp;9876&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(64.32.152.118)</font></div>
                <div>
                  <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                      CE2 PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;54&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></div>
                  <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CE2 CE
                      index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;987654</font></div>
                  <font face="Courier New">
                    <div><font face="Courier New">---------------------------------------------------------------</font></div>
                    <div>(2)&nbsp; CE2 IPv6 prefix: 20010db&nbsp;987654 (<font
                        color="#ff9966">2001:db9:8765:4000::/52</font>)</div>
                  </font></div>
                <div>&nbsp;</div>
                <div><font face="Courier New">ambiguity happens
                    and&nbsp;packet encapsulated&nbsp;with the same CE IPv6
                    address cannot be routed to the correct CE. </font></div>
              </blockquote>
            </div>
            This is not gonna happen, since the IPv6 address planing
            must be done natively considering nothing about the IPv4 in
            the very beginning. In your example, I see you get a
            2001:db0::/28 and you want to assign a /52 to each CE, then
            ok, there will be 24 bits to distinguish CEs and should be
            assigned continuously without any conflict. The next step is
            to check the available IPv4 spaces we have for the given
            number of subscribers, then based on which to design the
            rules. You made it in an opposite direction.<br>
            <br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>i understand what you mean is the following steps of
          rule_IPv6_prefix decision:&nbsp;</div>
        <div>1. list all the IPv4 addresses we have for the given number
          of subscribers; </div>
        <div>
          2. aggregate these IPv4 addresses into contiguous blocks,
          suppose that you start from the point of minimum waste (no
          unused IPv4 addresses are involved in the rules);</div>
        <div>3. define the share-ratio and calculate the
          rule_IPv6_prefix for each rule_IPv4_prefix defined in the step
          2;&nbsp;</div>
        <div>4. if your IPv6 space is far bigger to accommodate all the
          rule_IPv6_prefixes, then go back to step 2 and try to make
          some relax (trade-off), allowing unused IPv4 addresses
          involved in the rule to some extent but gaining fewer rules.&nbsp;</div>
        <div><br>
        </div>
        <div>my example was, from beginning, making a fixed
          rule_IPv6_prefix and two large IPv4 prefixes, where it is
          possible that a lot of actually unused IPv4 addresses
          contained. does the "opposite direction" in you context mean
          1) i put CE index behind a predefined rule_IPv6_prefix, or 2)
          i made large IPv4 prefixes as the start point? </div>
      </div>
    </blockquote>
    I meant the latter one (not 100% ;-)). You can aggregate these IPv4
    prefixes into contiguous blocks, by for instance as you proposed,
    changing the sharing ratio of the second example (64.32../16), 4-bit
    PSID to 8-bit PSID to make a 24-bit CE index as the first example
    (192.32../12). The aggregation should be done through the design of
    Rule IPv6 prefixes. Pick a /27 which contains two /28, use the first
    /28 as the Rule IPv6 Prefix for 192.32../12, then the second /28
    contains two /29, preserve the first /29, then the second /29
    contains two /30 ..., finally pick a /32 as the Rule IPv6 Prefix for
    64.32../16. Then the two rules share the same /27 and can be
    aggregated.<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>for the point 2), i may assume that all the addresses
          inside these two blocks are potentially used for our IPv4
          subscribers and therefore there is not waste, and i actually
          meant the same as you did. ;-)&nbsp;</div>
        <div>&nbsp;</div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000">We break the boundary
            between the IPv4 address and port, use the bits (24 bits in
            the examples above) together to identify the subscribers.
            The only reason I see to employ multiple IPv4 prefixes is we
            can't get a large enough one. Additionally, in the second
            example above, you changed the sharing ratio to make a
            "24-bit index", then you should change the Rule IPv6 prefix
            to, for example /27, for the two IPv4 prefixes of "same
            size". On the other hand, according to the consensus (if I
            get it correctly) of the interim meeting, more than one
            sharing ratios for the extended address case is not
            desirable, that flexibility should be offered by stateful
            approaches.
            <div class="im"><br>
            </div>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>sorry, a little confused. do you mean that, if we have
          192.32../12 and 64.32../16 for the rule_IPv4_prefixes and we
          have the 4-bit PSID (me too, don't desire to have more than
          one sharing ratios), then and we need each CE IPv6 prefix as
          /52, then the rule_IPv6_prefixes for the two rules should be
          /28 and /32, respectively, right?&nbsp;</div>
        <div>&nbsp;</div>
      </div>
    </blockquote>
    Yes, and please see my comments above.<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000">
            <div class="im"> <br>
              <blockquote type="cite">
                <div><font face="Courier New">therefore my answer to Q1,
                    is NO, </font><font face="Courier New">unless we
                    carefully select IPv4 addresses for CEs with giving
                    up to use some of them, which have been so precious.
                  </font></div>
                <div>&nbsp;</div>
                <div><font face="Courier New">Q2. then it must fine as
                    long as we map them to <font color="#ff0000">different</font>
                    Rule IPv6 Prefix. (?)</font></div>
                <div>&nbsp;</div>
                <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;suppose CE1 is the
                    same as (1). for 64.32../16, we use a longer stuff.</font></div>
                <div><font face="Courier New">&nbsp;&nbsp;&nbsp; however, there is a
                    CE3:</font></div>
                <div><font face="courier new,monospace">&nbsp;</font></div>
                <font face="courier new,monospace">
                  <div>
                    <div>
                      <div><font face="courier new,monospace">&nbsp;&nbsp;Rule
                          IPv6 Prefix B: 20010db<font color="#ff0000">8</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

                          (2001:db8::/<font color="#ff0000">29</font>)</font></div>
                    </div>
                  </div>
                </font>
                <div>
                  <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; CE3 IPv4
                      address: &nbsp;&nbsp; 4020 <font color="#ff0000">1</font><font
                        color="#000000">876</font>&nbsp;&nbsp;&nbsp;(64.32.24.118)</font></div>
                  <div>
                    <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;
                        CE3 PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;54&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></div>
                    <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CE3 CE
                        index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font color="#ff0000">9</font>87654</font></div>
                    <font face="Courier New">
                      <div><font face="Courier New">---------------------------------------------------------------</font></div>
                      <div>(3)&nbsp; CE3 IPv6 prefix: 20010db&nbsp;987654 (<font
                          color="#ff9966">2001:db9:8765:4000::/52,
                          woops!</font>)</div>
                    </font></div>
                </div>
                <div>&nbsp;</div>
                <div><font face="Courier New">ambiguity happens. then&nbsp;we
                    may argue: using the ugly Rule_IPv6_Prefix_B is the
                    root of the problem! we have not to use a prefix
                    covered by another. </font></div>
                <div>&nbsp;</div>
              </blockquote>
            </div>
            No, I think the bits of the same position are not additive.
            So, it should be a delegated prefix of "/53", right?</div>
        </blockquote>
        <div><br>
        </div>
        <div>:P sorry for the typo but i have pointed out in the errata.
          :P however, even though this is /53, and you will have, in the
          route table, both&nbsp;</div>
        <div>&nbsp; &nbsp;2001:db9:8765:4000::/52 =&gt; route to CE1</div>
        <div>&nbsp; &nbsp;2001:db9:8765:4000::/53 =&gt; route to CE3</div>
        <div><br>
        </div>
        <div>but for the packet encapsulated with the destination
          address 2001:db9:8765:4000::200:5efe, you couldn't decide the
          route should go to CE3 instead of CE1. here the longest-match
          doesn't work. right?</div>
        <div>&nbsp;</div>
      </div>
    </blockquote>
    I guess the second delegated prefix should be
    2001:db8:1876:5400::/53<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000">
            <div class="im"><br>
              <blockquote type="cite">
                <div><font face="Courier New">Q3. what does the <font
                      color="#ff0000">exclusiveness</font> of Rule IPv6
                    Prefix mean? </font></div>
                <div>&nbsp;</div>
                <div> <font face="Courier New">&nbsp;&nbsp;&nbsp; if we have
                    2001:da0::/28 for the Rule_IPv6_Prefix, everyone
                    will be happy. however, unfortunately, we have only
                    one /28 IPv6 aggregate. then what we have to do is
                    splitting the /28 block into mutually exclusive
                    pieces of small blocks. in the above example, if we
                    have the following rule table:</font></div>
                <div>&nbsp;</div>
                <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;Rule_IPv4_Prefix&nbsp;Rule_IPv6_Prefix</font></div>
                <div><font face="Courier New">&nbsp;&nbsp;
                    -----------------------------------</font></div>
                <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;192.32../12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                    2001:db0::/<font color="#ff0000">29</font></font></div>
                <div><font face="Courier New">&nbsp;&nbsp;&nbsp;
                    64.32../16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2001:db9::/<font color="#ff0000">29</font></font></div>
                <div><font face="Courier New">&nbsp;&nbsp;
                    -----------------------------------</font></div>
              </blockquote>
            </div>
            Yes, the exclusiveness. It's similar to what we do to
            further divide a subnet hierarchically.
            Hierarchies/exclusiveness avoid conflicts but lose the
            efficiency of addressing. BTW, the /29 example is the same
            as what I propose above. :-)
            <div class="im"><br>
            </div>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>ok. the exclusiveness is cleared. thanks a lot for the
          help! then please focus on the upper part further. <br>
        </div>
      </div>
    </blockquote>
    Great, we're on the same page.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div><br>
        </div>
        <div>thanks again and regards,</div>
        <div>maoke</div>
        <div>&nbsp;</div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000">
            <div class="im"> &nbsp;<br>
              <blockquote type="cite">
                <div><font face="Courier New">&nbsp;&nbsp;&nbsp; then it will work fine
                    within the /28 room in total. for 192.32../12, if
                    the PSID is at least 4bit, then the *shortest* CE
                    IPv6 prefix length is 29 + (32 - 12) + 4 = 53 now,
                    rather than 52 in the previous example. if we have
                    only or want to use only at most a /44 IPv6 prefix
                    for the residual deployment, for the above 2 IPv4
                    networks, we are not able to safely deploy the CE
                    prefix shorter than /64, no matter how we take the
                    effort! </font></div>
                <div>&nbsp;</div>
                <div><font face="Courier New">&nbsp;&nbsp;&nbsp; Jacni once mentioned
                    that if we have a /x IPv6 prefix while the
                    "philosophy" of address planning decides to have /y
                    for each CE-delegated network, then we can play the
                    magic with the bits between the /x and the /y. i
                    would like to point out here, because of the
                    exclusiveness requirement, there is a hard limit&nbsp;for
                    the power of&nbsp;the magic. if you have N IPv4 residual
                    addresses, you must at least&nbsp;satisfy the condition:</font></div>
              </blockquote>
            </div>
            Please see my comments above.<br>
            <br>
            <br>
            Cheers,<br>
            <font color="#888888"> Jacni</font>
            <div>
              <div class="h5"><br>
                <br>
                <blockquote type="cite">
                  <div>&nbsp;</div>
                  <div><font face="Courier New">&nbsp;&nbsp;&nbsp; (4)&nbsp;&nbsp;&nbsp;&nbsp; y - x &gt;=
                      log(N)</font></div>
                  <div>&nbsp;</div>
                  <div><font face="Courier New">&nbsp;&nbsp;&nbsp; when (4) is not
                      true, cutting the rule into pieces does help
                      almost nothing. i said "almost" because there is
                      really a little we can achieve: there is really
                      some IPv4 address&nbsp;seldom&nbsp;used for any routers,
                      like&nbsp;192.32.1.0. however,&nbsp;excluding such sort of
                      addresses from the mapping scatters the mapping
                      table&nbsp;into a huge number of&nbsp;/32-Rule_IPv4_Prefix
                      and making the table size&nbsp;even longer than today's
                      IPv4 routing table. </font></div>
                  <div>&nbsp;</div>
                  <div><font face="Courier New">just my 2 cents. execuse
                      me if the humble calculation&nbsp;has any
                      misunderstanding, and please point out without
                      hesitation.</font></div>
                  <div>&nbsp;</div>
                  <div><font face="Courier New">best,</font></div>
                  <div><font face="Courier New">maoke</font></div>
                  <div>&nbsp;</div>
                  <div>&nbsp;</div>
                  <div><font face="courier new,monospace">&gt; 2011/9/22
                      R&eacute;mi Despr&eacute;s &lt;<a moz-do-not-send="true"
                        href="mailto:despres.remi@laposte.net"
                        target="_blank">despres.remi@laposte.net</a>&gt;:</font></div>
                  <div><font face="courier new,monospace">&gt;&gt;
                      Alain, all,</font></div>
                  <div><font face="courier new,monospace">&gt;&gt;</font></div>
                  <div><font face="courier new,monospace">&gt;&gt; We
                      have just posted a new version of our I-D on the
                      proposed 4rd Address Mapping.</font></div>
                  <div><font face="courier new,monospace">&gt;&gt; It is
                      available at</font></div>
                  <div><font face="courier new,monospace">&gt;&gt; <a
                        moz-do-not-send="true"
href="http://www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt"
                        target="_blank">www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt</a></font></div>
                  <div><font face="courier new,monospace">&gt;&gt;</font></div>
                  <div><font face="courier new,monospace">&gt;&gt; Our
                      presentation will be based on THIS version,
                      technically simpler than version -00.</font></div>
                  <div><font face="courier new,monospace">&gt;&gt; Major
                      differences and their justifications will be
                      briefly explained.</font></div>
                  <div><font face="courier new,monospace">&gt;&gt;</font></div>
                  <div><font face="courier new,monospace">&gt;&gt;
                      Regards,</font></div>
                  <div><font face="courier new,monospace">&gt;&gt; RD</font></div>
                  <div><font face="courier new,monospace">&gt;&gt;
                      _______________________________________________</font></div>
                  <div><font face="courier new,monospace">&gt;&gt;
                      Softwires mailing list</font></div>
                  <div><font face="courier new,monospace">&gt;&gt; <a
                        moz-do-not-send="true"
                        href="mailto:Softwires@ietf.org" target="_blank">Softwires@ietf.org</a></font></div>
                  <div><font face="courier new,monospace">&gt;&gt; <a
                        moz-do-not-send="true"
                        href="https://www.ietf.org/mailman/listinfo/softwires"
                        target="_blank">https://www.ietf.org/mailman/listinfo/softwires</a></font></div>
                  <div><font face="courier new,monospace">&gt;&gt;</font></div>
                  <div><font face="courier new,monospace">&gt;
                      _______________________________________________</font></div>
                  <div><font face="courier new,monospace">&gt; Softwires
                      mailing list</font></div>
                  <div><font face="courier new,monospace">&gt; <a
                        moz-do-not-send="true"
                        href="mailto:Softwires@ietf.org" target="_blank">Softwires@ietf.org</a></font></div>
                  <div><font face="courier new,monospace">&gt; <a
                        moz-do-not-send="true"
                        href="https://www.ietf.org/mailman/listinfo/softwires"
                        target="_blank">https://www.ietf.org/mailman/listinfo/softwires</a></font></div>
                  <div><font face="courier new,monospace">&gt;</font></div>
                  <div><font face="courier new,monospace">&nbsp;</font></div>
                  <div><font face="courier new,monospace">&nbsp;</font></div>
                  <br>
                  <br>
                  <pre>_______________________________________________
Softwires mailing list
<a moz-do-not-send="true" href="mailto:Softwires@ietf.org" target="_blank">Softwires@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/softwires" target="_blank">https://www.ietf.org/mailman/listinfo/softwires</a>
</pre>
                </blockquote>
              </div>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
  </body>
</html>

--------------060403010205090909090801--


From fibrib@gmail.com  Mon Oct 17 04:11:45 2011
Return-Path: <fibrib@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 8262921F8B47 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 04:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.184
X-Spam-Level: 
X-Spam-Status: No, score=-3.184 tagged_above=-999 required=5 tests=[AWL=0.414,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mic4WzKDMDrP for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 04:11:40 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id B4B8021F84DA for <softwires@ietf.org>; Mon, 17 Oct 2011 04:11:38 -0700 (PDT)
Received: by qadb12 with SMTP id b12so2528595qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 04:11:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bGMIEZ4RgtxdS11Muq1zKLceWhGhNgGHct8UAA8JQM8=; b=YwAfl6q1DLhJIFn9T6J8hC2XbW+7gJ76IhuXfxKBWlUWHtvK77RoRc1JE4t1k4DRzV BmZt4rfeNBCmgj9qUlyKJemQ8kjyx1m6zUER0yOCfg2EKND9BRj9teO/6dwQinOhdats qfaHgwkv56tf9IySjaT/lQiakd3tofld8yfiQ=
MIME-Version: 1.0
Received: by 10.229.80.16 with SMTP id r16mr4001666qck.107.1318849896475; Mon, 17 Oct 2011 04:11:36 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Mon, 17 Oct 2011 04:11:36 -0700 (PDT)
In-Reply-To: <4E9BE001.3060202@jacni.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com>
Date: Mon, 17 Oct 2011 20:11:36 +0900
Message-ID: <CAFUBMqXi_6-EkuX-rY-qFfP+pd-WXa94OUA43XnH5ZX46Gx5yw@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=0016364ee764976d3804af7cab98
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 17 Oct 2011 11:11:45 -0000

--0016364ee764976d3804af7cab98
Content-Type: text/plain; charset=ISO-8859-1

hi,


 I guess the second delegated prefix should be 2001:db8:1876:5400::/53
>

got it. i was confused. :) but as the exclusiveness has been clarified, it
is not important any more.

thanks,
maoke

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

<div>hi,</div><div>=A0</div><div class=3D"gmail_quote"><blockquote type=3D"=
cite"><div class=3D"gmail_quote">
      </div>
    </blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor=3D"#FFFFFF" t=
ext=3D"#000000">
    I guess the second delegated prefix should be
    2001:db8:1876:5400::/53</div></blockquote></div><div><br></div><div>got=
 it. i was confused. :) but as the exclusiveness has been clarified, it is =
not important any more.=A0<br></div><div><br></div><div>thanks,</div><div>
maoke</div>

--0016364ee764976d3804af7cab98--

From leaf.y.yeh@huawei.com  Mon Oct 17 04:13:20 2011
Return-Path: <leaf.y.yeh@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 77C5E21F8B4F for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 04:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lTyQNU4v7xHQ for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 04:13:19 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB8221F8B4E for <softwires@ietf.org>; Mon, 17 Oct 2011 04:13:19 -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 <0LT7003BBJ5JWV@szxga03-in.huawei.com> for softwires@ietf.org; Mon, 17 Oct 2011 19:12:55 +0800 (CST)
Received: from szxrg01-dlp.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 <0LT7005TDJ4TOO@szxga03-in.huawei.com> for softwires@ietf.org; Mon, 17 Oct 2011 19:12:55 +0800 (CST)
Received: from szxeml206-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEM49076; Mon, 17 Oct 2011 19:12:52 +0800
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 17 Oct 2011 19:12:51 +0800
Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.227]) by szxeml404-hub.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Mon, 17 Oct 2011 19:12:37 +0800
Date: Mon, 17 Oct 2011 11:12:36 +0000
From: Leaf yeh <leaf.y.yeh@huawei.com>
In-reply-to: <14AB4609-752F-44E2-BE75-EB414CC2ACFA@ipinfusion.com>
X-Originating-IP: [10.70.39.98]
To: Tetsuya Murakami <tetsuya@ipinfusion.com>, GangChen <phdgang@gmail.com>
Message-id: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA057696C7@SZXEML510-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
Thread-index: AQHMiKOML2dtJJ66xk2qaokQFlhyYpV4jGbw
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <14AB4609-752F-44E2-BE75-EB414CC2ACFA@ipinfusion.com>
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation	and double-translation
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, 17 Oct 2011 11:13:20 -0000

I'd like to add one more row in the below table, then let it look like as follows.

+----------+-----------------+--------------------+
|          |source address   | destination address|
+----------+-----------------+--------------------+
|  CE-CE   |                 |                    |
+----------+-----------------+--------------------+
|  CE-BR   |                 |        Yes         |
+----------+-----------------+--------------------+
|  BR-CE   |                 |                    |
+----------+-----------------+--------------------+

And one more question for you: Do you think it is really necessary to include the case while CE 4rd prefix (defined in draft-murakami-softwire-4rd-01) or CE generalized IPv4 prefix (defined in draft-despres-softwire-4rd-addmapping-01) is less than 32 bits, which sounds CE has been assigned a IPv4 subnet?


Best Regards,
Leaf



-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On Behalf Of Tetsuya Murakami
Sent: Wednesday, October 12, 2011 1:55 PM
To: GangChen
Cc: Softwires-wg
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation


On 2011/10/08, at 20:14, GangChen wrote:

> As Ole said, "for the outside domain traffic" (Actually, I never argue
> that point for that case)
> Thereby, it's worth to be clarified whether need encoding whole IPv4
> address, as the below table
> 
> +----------+-----------------+--------------------+
> |          |source address   | destination address|
> +----------+-----------------+--------------------+
> |  CE-CE   |      N/A        |        N/A         |
> +----------+-----------------+--------------------+
> |  CE-BR   |      N/A        |        Yes         |
> +----------+-----------------+--------------------+


+1.

The above matrix is very clear to me.

In case of CE-BR, this case represents the traffic to the outside of the domain. In this case, I agree the full IPv4 destination address must be embedded in IPv6 destination address.

In case of CE-CE, this case represents the mesh communication between CEs. In this case, I don't think we need to embed full IPv4 destination address to IPv6 destination address. Because IPv6 destination address already includes enough information of IPv4 destination address (part of IPv4 address and port-set id).

>From the implementation point of view, 4rd function checks if the destination is existed inside of the domain or outside of the domain at the first step. If the destination is inside of the domain, then 4rd function generates the IPv6 destination address from the IPv4 destination address or both IPv4 destination address and port. If the destination is outside of the domain, then 4rd function can generate the IPv6 destination address having the full IPv4 destination address. The process of the IPv6 address generation is different on each traffic case. Hence, I think 4rd function might be having the separated code for the destination address generation and either of code can be invoked according to the result of the first step check. In fact, our implementation is having the separated code for this IPv6 address generation.

In addition, if using the unified address format in CE-CE communication as well, some additional CPU cycles per packet are required at CE in order to embed the full IPv4 address (and port-set id) in the last 64bit of the IPv6 address.

Thanks,
Tetsuya Murakami
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

From c-sun@bb.softbank.co.jp  Mon Oct 17 05:26:40 2011
Return-Path: <c-sun@bb.softbank.co.jp>
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 A170021F8569 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 05:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.995
X-Spam-Level: 
X-Spam-Status: No, score=0.995 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlh-qEXNgth1 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 05:26:40 -0700 (PDT)
Received: from bb.softbank.co.jp (m3.bb.softbank.co.jp [210.146.18.152]) by ietfa.amsl.com (Postfix) with ESMTP id D125921F8558 for <softwires@ietf.org>; Mon, 17 Oct 2011 05:26:31 -0700 (PDT)
Received: from CI-EXHB-02.bb.local (10.241.1.3) by m3.bb.softbank.co.jp (210.146.18.152) with Microsoft SMTP Server (TLS) id 8.2.247.2; Mon, 17 Oct 2011 21:26:29 +0900
Received: from CI-EXMB-09V.bb.local ([fe80::15e:dbec:b8a2:731f]) by CI-EXHB-02.bb.local ([::1]) with mapi; Mon, 17 Oct 2011 21:26:29 +0900
From: <c-sun@bb.softbank.co.jp>
To: <jacni@jacni.com>, <fibrib@gmail.com>
Date: Mon, 17 Oct 2011 21:26:29 +0900
Thread-Topic: [Softwires] 4rd Address Mapping - version-01
Thread-Index: AcyMokRzucxaWx9+SZ+hccb7JN+lpQAJTwDA
Message-ID: <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com>
In-Reply-To: <4E9BE001.3060202@jacni.com>
Accept-Language: zh-CN, ja-JP
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: zh-CN, ja-JP
Content-Type: multipart/alternative; boundary="_000_6CADC58598A4D249AD3B5026CE8CC33906D75AC8CIEXMB09Vbbloca_"
MIME-Version: 1.0
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 17 Oct 2011 12:26:40 -0000

--_000_6CADC58598A4D249AD3B5026CE8CC33906D75AC8CIEXMB09Vbbloca_
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

Hi,

This is my command in line.


therefore my answer to Q1, is NO, unless we carefully select IPv4 addresses=
 for CEs with giving up to use some of them, which have been so precious.

Q2. then it must fine as long as we map them to different Rule IPv6 Prefix.=
 (?)

    suppose CE1 is the same as (1). for 64.32../16, we use a longer stuff.
    however, there is a CE3:

  Rule IPv6 Prefix B: 20010db8       (2001:db8::/29)
    CE3 IPv4 address:    4020 1876   (64.32.24.118)
            CE3 PSID:             54
        CE3 CE index:         987654
---------------------------------------------------------------
(3)  CE3 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52, woops!)

ambiguity happens. then we may argue: using the ugly Rule_IPv6_Prefix_B is =
the root of the problem! we have not to use a prefix covered by another.

No, I think the bits of the same position are not additive. So, it should b=
e a delegated prefix of "/53", right?

:P sorry for the typo but i have pointed out in the errata. :P however, eve=
n though this is /53, and you will have, in the route table, both
   2001:db9:8765:4000::/52 =3D> route to CE1
   2001:db9:8765:4000::/53 =3D> route to CE3

but for the packet encapsulated with the destination address 2001:db9:8765:=
4000::200:5efe, you couldn't decide the route should go to CE3 instead of C=
E1. here the longest-match doesn't work. right?

I guess the second delegated prefix should be 2001:db8:1876:5400::/53

  I guess the second delegated prefix should be 2011:db8:c3b2:a000::/53.
Because the CE3 Rule IPv6 Prefix length is not mulitipe of 4 bits,it need c=
alculate using Binary as follows.

                                 v(/29)
 --elipsis(0x2001 0db)--1000                                            (20=
11:db8::/29)
 --elipsis(0x4020)------    000 1100 0011 1011 0                 (64.32.24.=
118)
                                                                   010 1010=
 0 (PSID 0x54)
--------------------------------------------------------------------------
CE3 IPv6 prefix: 2001:db8:c3b2:a000::/53

If the CE3 IPv4 address is 64.32.48.236, CE3 PSID is 0xa8, calculate as fol=
lows,
                                 v(/29)
 --elipsis(0x2001 0db)--1000                                            (20=
11:db8::/29)
 --elipsis(0x4020)------    001 1000 0111 0110 0                 (64.32.48.=
236)
                                                                   101 0100=
 0 (PSID 0xa8)
--------------------------------------------------------------------------
the CE3 IPv6 prefix is 2001:db9:8765:4000::/53

I think this  should be not gonna happen, since the IPv6 address planing mu=
st be done natively
considering nothing about the IPv4 address. As exclusiveness, each CE has u=
nique CE IPv6 Prefix.

As described in the example Maoke given, since "Rule IPv6 Prefix B" is cont=
ained in the "Rule IPv6 Prefix A",
if the IPv6 addresses under Rule IPv6 Prefix A and the IPv6 address under R=
ule IPv6 prefix B are assigned independently
and have any consideration each other, same CE IPv6 prefix assigning to dif=
ferent CEs may be happen. I think this MUST be
 avoided when designing the mapping rules or setting the IPv6 assigning way=
(such as DHCPv6 etc.).

Cheers

Chunfa




--_000_6CADC58598A4D249AD3B5026CE8CC33906D75AC8CIEXMB09Vbbloca_
Content-Type: text/html; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-2022-jp=
">
<META content=3D"MSHTML 6.00.2900.6148" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"=1B$B#M#S=1B(B =1B$B#P%4%7%C%/=1B=
(B" color=3D#0000ff size=3D2><SPAN=20
class=3D888562212-17102011>Hi,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"=1B$B#M#S=1B(B =1B$B#P%4%7%C%/=1B=
(B" color=3D#0000ff size=3D2><SPAN=20
class=3D888562212-17102011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"=1B$B#M#S=1B(B =1B$B#P%4%7%C%/=1B=
(B" color=3D#0000ff size=3D2><SPAN=20
class=3D888562212-17102011>This is my command in line.</SPAN></FONT></DIV><=
BR>
<BLOCKQUOTE=20
cite=3Dmid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.c=
om=20
type=3D"cite">
  <DIV class=3Dgmail_quote>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
    <DIV text=3D"#000000" bgcolor=3D"#FFFFFF">
    <DIV class=3Dim><BR>
    <BLOCKQUOTE type=3D"cite">
      <DIV><FONT face=3D"Courier New">therefore my answer to Q1, is NO,=20
      </FONT><FONT face=3D"Courier New">unless we carefully select IPv4 add=
resses=20
      for CEs with giving up to use some of them, which have been so precio=
us.=20
      </FONT></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">Q2. then it must fine as long as we m=
ap them=20
      to <FONT color=3D#ff0000>different</FONT> Rule IPv6 Prefix. (?)</FONT=
></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp;suppose CE1 i=
s the=20
      same as (1). for 64.32../16, we use a longer stuff.</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&nbsp;&nbsp;&nbsp; however, there is =
a=20
      CE3:</FONT></DIV>
      <DIV><FONT face=3D"courier new,monospace"></FONT>&nbsp;</DIV><FONT=20
      face=3D"courier new,monospace">
      <DIV>
      <DIV>
      <DIV><FONT face=3D"courier new,monospace">&nbsp;&nbsp;Rule IPv6 Prefi=
x B:=20
      20010db<FONT color=3D#ff0000>8</FONT>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
      (2001:db8::/<FONT color=3D#ff0000>29</FONT>)</FONT></DIV></DIV></DIV>=
</FONT>
      <DIV>
      <DIV><FONT face=3D"courier new,monospace">&nbsp;&nbsp;&nbsp; CE3 IPv4=
=20
      address: &nbsp;&nbsp; 4020 <FONT color=3D#ff0000>1</FONT><FONT=20
      color=3D#000000>876</FONT>&nbsp;&nbsp;&nbsp;(64.32.24.118)</FONT></DI=
V>
      <DIV>
      <DIV><FONT=20
      face=3D"courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
      &nbsp; CE3=20
      PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;54&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      </FONT></DIV>
      <DIV><FONT=20
      face=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
CE3 CE=20
      index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT=20
      color=3D#ff0000>9</FONT>87654</FONT></DIV><FONT face=3D"Courier New">
      <DIV><FONT=20
      face=3D"Courier New">------------------------------------------------=
---------------</FONT></DIV>
      <DIV>(3)&nbsp; CE3 IPv6 prefix: 20010db&nbsp;987654 (<FONT=20
      color=3D#ff9966>2001:db9:8765:4000::/52,=20
      woops!</FONT>)</DIV></FONT></DIV></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">ambiguity happens. then&nbsp;we may a=
rgue:=20
      using the ugly Rule_IPv6_Prefix_B is the root of the problem! we have=
 not=20
      to use a prefix covered by another. </FONT></DIV>
      <DIV>&nbsp;</DIV></BLOCKQUOTE></DIV>No, I think the bits of the same=
=20
    position are not additive. So, it should be a delegated prefix of "/53"=
,=20
    right?</DIV></BLOCKQUOTE>
  <DIV><BR></DIV>
  <DIV>:P sorry for the typo but i have pointed out in the errata. :P howev=
er,=20
  even though this is /53, and you will have, in the route table,=20
  both&nbsp;</DIV>
  <DIV>&nbsp; &nbsp;2001:db9:8765:4000::/52 =3D&gt; route to CE1</DIV>
  <DIV>&nbsp; &nbsp;2001:db9:8765:4000::/53 =3D&gt; route to CE3</DIV>
  <DIV><BR></DIV>
  <DIV>but for the packet encapsulated with the destination address=20
  2001:db9:8765:4000::200:5efe, you couldn't decide the route should go to =
CE3=20
  instead of CE1. here the longest-match doesn't work. right?</DIV>
  <DIV>&nbsp;</DIV></DIV></BLOCKQUOTE>
<DIV>I guess the second delegated prefix should be 2001:db8:1876:5400::/53<=
SPAN=20
class=3D888562212-17102011><FONT face=3D"=1B$B#M#S=1B(B =1B$B#P%4%7%C%/=1B(=
B" color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=3D888562212-17102011></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D888562212-17102011><SPAN class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 13px arial, sans-serif; TEXT-TRANSFORM: n=
one; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACI=
NG: normal; BACKGROUND-COLOR: rgb(255,255,255); orphans: 2; widows: 2; webk=
it-text-decorations-in-effect: none; webkit-text-size-adjust: auto; webkit-=
text-stroke-width: 0px">
<DIV>
<DIV><FONT color=3D#0000ff><SPAN class=3D888562212-17102011><FONT face=3D"=
=1B$B#M#S=1B(B =1B$B#P%4%7%C%/=1B(B"=20
size=3D2>&nbsp;&nbsp;</FONT></SPAN>I guess the second delegated prefix shou=
ld be=20
2011:db8:c3b2:a000::/53.</FONT></DIV>
<DIV><FONT color=3D#0000ff>Because the CE3 Rule IPv6 Prefix length is not m=
ulitipe=20
of 4 bits,it need calculate using Binary as follows.&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff><BR></FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;v(/29)</FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp;--elipsis(0x2001 0db)--1000 &nbsp; &nbsp; =
&nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;(2011:db8::/29)</FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp;--elipsis(0x4020)------ &nbsp; &nbsp;000 1=
100=20
0011 1011 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
(64.32.24.118)</FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp;010 1010 0 (PSID 0x54)</FONT></DIV>
<DIV><FONT=20
color=3D#0000ff>------------------------------<WBR>------------------------=
------<WBR>--------------</FONT></DIV>
<DIV><FONT color=3D#0000ff>CE3 IPv6 prefix: 2001:db8:c3b2:a000::/53</FONT><=
/DIV>
<DIV><FONT color=3D#0000ff><BR></FONT></DIV>
<DIV><FONT color=3D#0000ff>If the CE3 IPv4 address is 64.32.48.236, CE3 PSI=
D is=20
0xa8, calculate as follows,</FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;v(/29)</FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp;--elipsis(0x2001 0db)--1000 &nbsp; &nbsp; =
&nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;(2011:db8::/29)</FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp;--elipsis(0x4020)------ &nbsp; &nbsp;001 1=
000=20
0111 0110 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
(64.32.48.236)</FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp;101 0100 0 (PSID 0xa8)</FONT></DIV>
<DIV><FONT=20
color=3D#0000ff>------------------------------<WBR>------------------------=
------<WBR>--------------</FONT></DIV>
<DIV><FONT color=3D#0000ff>the CE3 IPv6 prefix is 2001:db9:8765:4000::/53=20
&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff><BR></FONT></DIV>
<DIV><FONT color=3D#0000ff>I think this&nbsp;<SPAN class=3D888562212-171020=
11><FONT=20
face=3D"=1B$B#M#S=1B(B =1B$B#P%4%7%C%/=1B(B" size=3D2>&nbsp;should be</FONT=
></SPAN> not gonna happen, since the=20
IPv6 address planing must be done natively&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff>considering nothing about the IPv4 address. As=20
exclusiveness, each CE has unique CE IPv6 Prefix.&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff><BR></FONT></DIV>
<DIV><FONT color=3D#0000ff>As described in the example Maoke given, since "=
Rule=20
IPv6 Prefix B" is contained in the "Rule IPv6 Prefix A",&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff>if the IPv6 addresses under Rule IPv6 Prefix A a=
nd the=20
IPv6 address under Rule IPv6 prefix B are assigned=20
independently&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff>and have any consideration each other, same CE I=
Pv6=20
prefix assigning to different CEs may be happen. I think this MUST=20
be</FONT></DIV>
<DIV><FONT color=3D#0000ff>&nbsp;avoided when designing the mapping rules o=
r=20
setting the IPv6 assigning way(such as DHCPv6 etc.).&nbsp;</FONT></DIV></DI=
V>
<DIV><FONT color=3D#0000ff><BR></FONT></DIV>
<DIV><FONT color=3D#0000ff>Cheers</FONT></DIV>
<DIV><FONT color=3D#0000ff><BR></FONT></DIV>
<DIV><FONT color=3D#0000ff>Chunfa</FONT></DIV></SPAN>&nbsp;</SPAN><BR><BR><=
/DIV>
<BLOCKQUOTE=20
cite=3Dmid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.c=
om=20
type=3D"cite">
  <DIV class=3Dgmail_quote>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
    <DIV text=3D"#000000"=20
bgcolor=3D"#FFFFFF">&nbsp;</DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HT=
ML>

--_000_6CADC58598A4D249AD3B5026CE8CC33906D75AC8CIEXMB09Vbbloca_--

From despres.remi@laposte.net  Mon Oct 17 05:36:33 2011
Return-Path: <despres.remi@laposte.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 AA17321F8772 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 05:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.614
X-Spam-Level: 
X-Spam-Status: No, score=-1.614 tagged_above=-999 required=5 tests=[AWL=0.335,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQxi2bqkDPvb for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 05:36:33 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086BE21F8713 for <softwires@ietf.org>; Mon, 17 Oct 2011 05:36:33 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2103.sfr.fr (SMTP Server) with ESMTP id E7237700016C; Mon, 17 Oct 2011 14:36:31 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2103.sfr.fr (SMTP Server) with ESMTP id B7AEE70001C2; Mon, 17 Oct 2011 14:36:27 +0200 (CEST)
X-SFR-UUID: 20111017123627752.B7AEE70001C2@msfrf2103.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 17 Oct 2011 14:36:27 +0200
Message-Id: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 12:36:33 -0000

Hi Satoru-san,

Thank you for identifying a limitation of the 4rd-U =20
You are right, as currently specified, "it doesn't support diff-serv =
tunneling model, pipe and short-pipe".
All these need e2e transparency to the IPv4 Type of Service.

Fortunately, this is easy to fix: in the Identification field of the =
IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
 =20
The proposed 4r-U packet format becomes:


   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Vers=3D6 |   TrafClass   |            Flow Label                 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Payload Length        |Next Header=3D44 |   Hop Limit   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                                                               +
   |                                                               |
   +                  IPv6 Source Address                          +
   |                                                               |
   +                                                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                                                               +
   |                                                               |
   +                IPv6 Destination Address                       +
   |                                                               |
   +                                                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
   |                        IPv4 Payload                           |
   |                                                               |=20

With this added, I believe that 4rd-U is a real progress over previously =
proposed Double translation and Encapsulation.
It can make IMHO a valuable unified standard.

Yet, I may have missed something else.=20
New justified objections are therefore most welcome..


Regards,
RD=

From internet-drafts@ietf.org  Mon Oct 17 05:42:28 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 85B9521F8B8B; Mon, 17 Oct 2011 05:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level: 
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQloP9nZby1P; Mon, 17 Oct 2011 05:42:28 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2254921F8B85; Mon, 17 Oct 2011 05:42:28 -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.60
Message-ID: <20111017124228.1826.39377.idtracker@ietfa.amsl.com>
Date: Mon, 17 Oct 2011 05:42:28 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-dslite-radius-ext-07.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, 17 Oct 2011 12:42:28 -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           : RADIUS Extensions for Dual-Stack Lite
	Author(s)       : Roberta Maglione
                          Alain Durand
	Filename        : draft-ietf-softwire-dslite-radius-ext-07.txt
	Pages           : 12
	Date            : 2011-10-17

   Dual-Stack Lite is a solution to offer both IPv4 and IPv6
   connectivity to customers which are addressed only with an IPv6
   prefix.  Dual-Stack Lite requires to pre-configure the Dual-Stack
   Lite Address Family Transition Router (AFTR) tunnel information on
   the Basic Bridging BroadBand (B4) element.  In many networks, the
   customer profile information may be stored in Authentication
   Authorization and Accounting (AAA) servers while client
   configurations are mainly provided through Dynamic Host Configuration
   Protocol (DHCP).  This document specifies a new Remote Authentication
   Dial In User Service (RADIUS) attribute to carry Dual-Stack Lite
   Address Family Transition Router Tunnel name; the RADIUS attribute is
   defined based on the equivalent DHCPv6 OPTION_AFTR_NAME option.  This
   RADIUS attribute is meant to be used between the RADIUS Server and
   the Network Access Server (NAS), it is not intended to be used
   directly between the Basic Bridging BroadBand element and the RADIUS
   Server.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-dslite-radius-ext-0=
7.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-dslite-radius-ext-07=
.txt

From satoru.matsushima@gmail.com  Mon Oct 17 06:17:25 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 C8B9321F8B8A for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 06:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VqxvF-7uYxS2 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 06:17:25 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3264A21F8B87 for <softwires@ietf.org>; Mon, 17 Oct 2011 06:17:25 -0700 (PDT)
Received: by qadb12 with SMTP id b12so2664965qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 06:17:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=MEHcXkXZE0nDZrJOtEHKcMSkOviEyQCmrvdBKEZeGzw=; b=WjFYgC4meX8czBGkUKXDRL1+/3n4C7yYz7qfnbs72oDbWdXN2Z2EuUhU4mmArTt84K 2unZ3dC3lYy7YJAPKZdcKsHLPVXKYToMp0osYVDBzLtXOhxGWbgcp9ukkqyZyYqrG2My ipIBpQHPDHAcH22FRSlaraL+wJl8DqgSH9OCc=
Received: by 10.68.39.130 with SMTP id p2mr20892859pbk.104.1318857442515; Mon, 17 Oct 2011 06:17:22 -0700 (PDT)
Received: from [192.168.10.54] (softbank221038132005.bbtec.net. [221.38.132.5]) by mx.google.com with ESMTPS id w4sm58810133pbf.6.2011.10.17.06.17.18 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Oct 2011 06:17:19 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=utf-8
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net>
Date: Mon, 17 Oct 2011 22:17:15 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net>
To: =?utf-8?Q?R=C3=A9mi_Despr=C3=A9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1251.1)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 13:17:25 -0000

Hi Remi-san,

> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> It can make IMHO a valuable unified standard.

Not enough. The original TTL value in IPv4 header must be carried.

cheers,
--satoru


On 2011/10/17, at 21:36, R=C3=A9mi Despr=C3=A9s wrote:

> Hi Satoru-san,
>=20
> Thank you for identifying a limitation of the 4rd-U =20
> You are right, as currently specified, "it doesn't support diff-serv =
tunneling model, pipe and short-pipe".
> All these need e2e transparency to the IPv4 Type of Service.
>=20
> Fortunately, this is easy to fix: in the Identification field of the =
IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
>=20
> The proposed 4r-U packet format becomes:
>=20
>=20
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |Vers=3D6 |   TrafClass   |            Flow Label                 |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |         Payload Length        |Next Header=3D44 |   Hop Limit   |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                                                               |
>   +                                                               +
>   |                                                               |
>   +                  IPv6 Source Address                          +
>   |                                                               |
>   +                                                               +
>   |                                                               |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                                                               |
>   +                                                               +
>   |                                                               |
>   +                IPv6 Destination Address                       +
>   |                                                               |
>   +                                                               +
>   |                                                               |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
>   |                        IPv4 Payload                           |
>   |                                                               |=20
>=20
> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> It can make IMHO a valuable unified standard.
>=20
> Yet, I may have missed something else.=20
> New justified objections are therefore most welcome..
>=20
>=20
> Regards,
> RD


From fibrib@gmail.com  Mon Oct 17 06:30:18 2011
Return-Path: <fibrib@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 C942A21F8B98 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 06:30:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.236
X-Spam-Level: 
X-Spam-Status: No, score=-3.236 tagged_above=-999 required=5 tests=[AWL=0.362,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dyrCsMEiXkp for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 06:30:18 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id F24ED21F8783 for <softwires@ietf.org>; Mon, 17 Oct 2011 06:30:17 -0700 (PDT)
Received: by qadb12 with SMTP id b12so2680918qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 06:30:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mpF0z1hZYcx+qSYTYPu6Ab47mPXaRjcq606CuWFJWqw=; b=uDcvtFdOxhFqZx5wg/HP19fUqwIRHBGXnQZl5Xi+QZmKkMHdFxKlDhDronGJUF2T7c LQoGHTyMYIgBd2WTBbOzTbWdJ75RFBp4soE/wXasm+cd63V5coL9LYlKWznTlzNvRlDu 2YWxiYBYSFlb1ls2dNS/TBlAWKOixacLWE7H4=
MIME-Version: 1.0
Received: by 10.224.9.81 with SMTP id k17mr4009406qak.24.1318858217523; Mon, 17 Oct 2011 06:30:17 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Mon, 17 Oct 2011 06:30:17 -0700 (PDT)
In-Reply-To: <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com>
Date: Mon, 17 Oct 2011 22:30:17 +0900
Message-ID: <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec519617b908a3c04af7e9be4
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 13:30:18 -0000

--bcaec519617b908a3c04af7e9be4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Satoru-san,

may i understand that, as Remi's proposal is applied for the double
translation case, TTL being translated to IPv6 Hop Limit is enough? as is
stated in RFC6145, translator is a "router" and therefore the behavior
should not be as same as the virtual link. right?
regards,
maoke
2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>

> Hi Remi-san,
>
> > With this added, I believe that 4rd-U is a real progress over previousl=
y
> proposed Double translation and Encapsulation.
> > It can make IMHO a valuable unified standard.
>
> Not enough. The original TTL value in IPv4 header must be carried.
>
> cheers,
> --satoru
>
>
> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>
> > Hi Satoru-san,
> >
> > Thank you for identifying a limitation of the 4rd-U
> > You are right, as currently specified, "it doesn't support diff-serv
> tunneling model, pipe and short-pipe".
> > All these need e2e transparency to the IPv4 Type of Service.
> >
> > Fortunately, this is easy to fix: in the Identification field of the IP=
v6
> Fragment header, copy not only the DF bits but also the IPv4 TOS.
> >
> > The proposed 4r-U packet format becomes:
> >
> >
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |Vers=3D6 |   TrafClass   |            Flow Label                 |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |         Payload Length        |Next Header=3D44 |   Hop Limit   |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                                                               |
> >   +                                                               +
> >   |                                                               |
> >   +                  IPv6 Source Address                          +
> >   |                                                               |
> >   +                                                               +
> >   |                                                               |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                                                               |
> >   +                                                               +
> >   |                                                               |
> >   +                IPv6 Destination Address                       +
> >   |                                                               |
> >   +                                                               +
> >   |                                                               |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                        IPv4 Payload                           |
> >   |                                                               |
> >
> > With this added, I believe that 4rd-U is a real progress over previousl=
y
> proposed Double translation and Encapsulation.
> > It can make IMHO a valuable unified standard.
> >
> > Yet, I may have missed something else.
> > New justified objections are therefore most welcome..
> >
> >
> > Regards,
> > RD
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

<div>hi Satoru-san,</div><div>=A0</div><div>may i understand that, as=A0Rem=
i&#39;s proposal is applied for the double translation case, TTL being tran=
slated to IPv6 Hop Limit is enough? as is stated in RFC6145, translator is =
a &quot;router&quot; and therefore the behavior should not be as same as th=
e virtual link. right?<br>
</div><div>regards,</div><div>maoke<br></div><div class=3D"gmail_quote">201=
1/10/17 Satoru Matsushima <span dir=3D"ltr">&lt;<a href=3D"mailto:satoru.ma=
tsushima@gmail.com">satoru.matsushima@gmail.com</a>&gt;</span><br><blockquo=
te style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color=
: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;" cl=
ass=3D"gmail_quote">
Hi Remi-san,<br>
<div class=3D"im"><br>
&gt; With this added, I believe that 4rd-U is a real progress over previous=
ly proposed Double translation and Encapsulation.<br>
&gt; It can make IMHO a valuable unified standard.<br>
<br>
</div>Not enough. The original TTL value in IPv4 header must be carried.<br=
>
<br>
cheers,<br>
<font color=3D"#888888">--satoru<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:<br>
<br>
&gt; Hi Satoru-san,<br>
&gt;<br>
&gt; Thank you for identifying a limitation of the 4rd-U<br>
&gt; You are right, as currently specified, &quot;it doesn&#39;t support di=
ff-serv tunneling model, pipe and short-pipe&quot;.<br>
&gt; All these need e2e transparency to the IPv4 Type of Service.<br>
&gt;<br>
&gt; Fortunately, this is easy to fix: in the Identification field of the I=
Pv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.<br>
&gt;<br>
&gt; The proposed 4r-U packet format becomes:<br>
&gt;<br>
&gt;<br>
&gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=
br>
&gt; =A0 |Vers=3D6 | =A0 TrafClass =A0 | =A0 =A0 =A0 =A0 =A0 =A0Flow Label =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=
br>
&gt; =A0 | =A0 =A0 =A0 =A0 Payload Length =A0 =A0 =A0 =A0|Next Header=3D44 =
| =A0 Hop Limit =A0 |<br>
&gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=
br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv6 Source Address =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0+<br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=
br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv6 Destination Address =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=
br>
&gt; =A0 | =A0Next Header =A0| =A0 =A0Reserved =A0 | IPv6 =A0Fragment Offse=
t =A0 | 0 |M|<br>
&gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=
br>
&gt; =A0 |D| =A0 =A0 =A00 =A0 =A0 =A0| =A0 =A0IPv4 TOS =A0 | =A0 =A0 =A0 IP=
v4 Identification =A0 =A0 |<br>
&gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=
br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv4 Payload =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt;<br>
&gt; With this added, I believe that 4rd-U is a real progress over previous=
ly proposed Double translation and Encapsulation.<br>
&gt; It can make IMHO a valuable unified standard.<br>
&gt;<br>
&gt; Yet, I may have missed something else.<br>
&gt; New justified objections are therefore most welcome..<br>
&gt;<br>
&gt;<br>
&gt; Regards,<br>
&gt; RD<br>
<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>
</div></div></blockquote></div><br>

--bcaec519617b908a3c04af7e9be4--

From satoru.matsushima@gmail.com  Mon Oct 17 06:48:49 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 E9F2F21F8BA9 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 06:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1jxzcMnkFgMh for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 06:48:49 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4E19F21F8B92 for <softwires@ietf.org>; Mon, 17 Oct 2011 06:48:49 -0700 (PDT)
Received: by qadb12 with SMTP id b12so2703215qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 06:48:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=j74AGy3j/Hv9Bb5pttTxQ0cUbo8GkQhCrV5mgpuYW2E=; b=fERfkTs8ot41Z9sju46ffS0c9EXRtggLIf7U3bhkJyoxNr7V9Ichs/L6kZe+wwo1Yl peBrVO6bAbRoBLS0oqiPpMHjzh8pRbH3V/KTyYzTZ32tsbRLTOoYYYcDxN4JcdC7Jsy5 HUsUSpo90tMhu9KrsFid90zI8T8EzB8BGSWNA=
Received: by 10.68.74.227 with SMTP id x3mr15748035pbv.51.1318859328693; Mon, 17 Oct 2011 06:48:48 -0700 (PDT)
Received: from [192.168.10.54] (softbank221038132005.bbtec.net. [221.38.132.5]) by mx.google.com with ESMTPS id h5sm59060322pbq.11.2011.10.17.06.48.44 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Oct 2011 06:48:47 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com>
Date: Mon, 17 Oct 2011 22:48:42 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com>
To: Maoke <fibrib@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 13:48:50 -0000

Hi Maoke-san,

On 2011/10/17, at 22:30, Maoke wrote:

> hi Satoru-san,
> =20
> may i understand that, as Remi's proposal is applied for the double =
translation case, TTL being translated to IPv6 Hop Limit is enough? as =
is stated in RFC6145, translator is a "router" and therefore the =
behavior should not be as same as the virtual link. right?

If so, just double translation is enough for that.

cheers,
--satoru

> regards,
> maoke
> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
> Hi Remi-san,
>=20
> > With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> > It can make IMHO a valuable unified standard.
>=20
> Not enough. The original TTL value in IPv4 header must be carried.
>=20
> cheers,
> --satoru
>=20
>=20
> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>=20
> > Hi Satoru-san,
> >
> > Thank you for identifying a limitation of the 4rd-U
> > You are right, as currently specified, "it doesn't support diff-serv =
tunneling model, pipe and short-pipe".
> > All these need e2e transparency to the IPv4 Type of Service.
> >
> > Fortunately, this is easy to fix: in the Identification field of the =
IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
> >
> > The proposed 4r-U packet format becomes:
> >
> >
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |Vers=3D6 |   TrafClass   |            Flow Label                 =
|
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |         Payload Length        |Next Header=3D44 |   Hop Limit   =
|
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                                                               |
> >   +                                                               +
> >   |                                                               |
> >   +                  IPv6 Source Address                          +
> >   |                                                               |
> >   +                                                               +
> >   |                                                               |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                                                               |
> >   +                                                               +
> >   |                                                               |
> >   +                IPv6 Destination Address                       +
> >   |                                                               |
> >   +                                                               +
> >   |                                                               |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >   |                        IPv4 Payload                           |
> >   |                                                               |
> >
> > With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> > It can make IMHO a valuable unified standard.
> >
> > Yet, I may have missed something else.
> > New justified objections are therefore most welcome..
> >
> >
> > Regards,
> > RD
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>=20


From fibrib@gmail.com  Mon Oct 17 07:46:44 2011
Return-Path: <fibrib@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 1748D21F8C0E for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 07:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.276
X-Spam-Level: 
X-Spam-Status: No, score=-3.276 tagged_above=-999 required=5 tests=[AWL=0.322,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97llEWrO7OFm for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 07:46:43 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id B218B21F8BA8 for <softwires@ietf.org>; Mon, 17 Oct 2011 07:46:42 -0700 (PDT)
Received: by qyk34 with SMTP id 34so986989qyk.10 for <softwires@ietf.org>; Mon, 17 Oct 2011 07:46:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=L8Jloirlc8p0mZKtUFX52aiCWkF42PMA7EuDaFjlab4=; b=wr6I6lw6VtmwpGevyqY2FvOy2kL0NV1aTBJXEtspKca9RnyoY1xDbqPcBGNFi3Go76 eKHQNGgO1ioDuYOHMwI/GDma05W07yifgbVCq8nqV5VRWZYQ58pq+iMaHq/DyatKJUUB W/Z5dXV/F4uB3CFsmO0PVGHjaIoBBWcPOtGrM=
MIME-Version: 1.0
Received: by 10.229.63.169 with SMTP id b41mr4157258qci.145.1318862802112; Mon, 17 Oct 2011 07:46:42 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Mon, 17 Oct 2011 07:46:41 -0700 (PDT)
In-Reply-To: <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com>
Date: Mon, 17 Oct 2011 23:46:41 +0900
Message-ID: <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Content-Type: multipart/alternative; boundary=0016e65da6eed3d2a904af7fac85
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 14:46:44 -0000

--0016e65da6eed3d2a904af7fac85
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Satoru-san,

2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>

> Hi Maoke-san,
>
> On 2011/10/17, at 22:30, Maoke wrote:
>
> > hi Satoru-san,
> >
> > may i understand that, as Remi's proposal is applied for the double
> translation case, TTL being translated to IPv6 Hop Limit is enough? as is
> stated in RFC6145, translator is a "router" and therefore the behavior
> should not be as same as the virtual link. right?
>
> If so, just double translation is enough for that.
>

it sounds nice. what i would like to have is a consistent header processing
for single/double translations and encapsulation.

can we keep the TTL of IPv4 in the IPv6 header (plus fragment header but no=
t
anything more unless really necessary)?

can i understand that the following requirements are exclusive to each
other: (a) we want to keep TTL changed in the IPv6 domain as the behavior o=
f
translation; (b) we want to keep TTL not changed until leaving the IPv6
domain as the behavior of encapsulation (4rd-U)?

RFC6145 has defined TTL<->HopLimit translation. then how about using anothe=
r
reserved bit, say EF, in the fragment header for indicating the mode? if EF
=3D 1, it is encapsulation mode, and therefore the HopLimit in the base hea=
der
keeps unchanged untile being translated back to IPv4; if EF =3D 0, it is
translation mode, and the HopLimit in the base header will decrease 1 for
each hop. btw, previously i suggest using one of the reserved bits for the
DF (e.g., the one before MF) instead of the first bit of the identification
in the ipv6 fragement header, in order to avoid ambiguity caused by an IPv6
host in the single translation.

thus i'd like to suggest that one as follows, based on Remi's complement,
where E is the indicator of encapsulation mode. copying TOS in the fragment
header is fine because it doesn't impact the IPv6 dst (of single
translation) getting the original IPv4 src's relative identification.

       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |Vers=3D6 |   TrafClass   |            Flow Label                 |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |         Payload Length        |Next Header=3D44 |   Hop Limit   |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       +                                                               +
       |                                                               |
       +                  IPv6 Source Address                          +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       +                                                               +
       |                                                               |
       +                IPv6 Destination Address                       +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |  Next Header  |   Reserved    | IPv6  Fragment Offset   |E|D|M|
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |      0        |     TOS       |       IPv4 Identification     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                        IPv4 Payload                           |
       |                                                               |
unfortunately, however, even we free the first bit of IPv6 identification i=
n
the fragment header, we cannot put the TTL here (before the TOS) because
traversing different paths may cause inconsistant IPv6 identification value=
s
in fragments of the same datagram and disable reassemble at the IPv6 dst (i=
n
the single translation mode).

the problem of EF in fragment header is, it requires that the implementatio=
n
process fragment header before descreasing the HopLimit. is it feasible?

how do you think?

cheers,
maoke


> cheers,
> --satoru
>
> > regards,
> > maoke
> > 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
> > Hi Remi-san,
> >
> > > With this added, I believe that 4rd-U is a real progress over
> previously proposed Double translation and Encapsulation.
> > > It can make IMHO a valuable unified standard.
> >
> > Not enough. The original TTL value in IPv4 header must be carried.
> >
> > cheers,
> > --satoru
> >
> >
> > On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
> >
> > > Hi Satoru-san,
> > >
> > > Thank you for identifying a limitation of the 4rd-U
> > > You are right, as currently specified, "it doesn't support diff-serv
> tunneling model, pipe and short-pipe".
> > > All these need e2e transparency to the IPv4 Type of Service.
> > >
> > > Fortunately, this is easy to fix: in the Identification field of the
> IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
> > >
> > > The proposed 4r-U packet format becomes:
> > >
> > >
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |Vers=3D6 |   TrafClass   |            Flow Label                 |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |         Payload Length        |Next Header=3D44 |   Hop Limit   |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                                                               |
> > >   +                                                               +
> > >   |                                                               |
> > >   +                  IPv6 Source Address                          +
> > >   |                                                               |
> > >   +                                                               +
> > >   |                                                               |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                                                               |
> > >   +                                                               +
> > >   |                                                               |
> > >   +                IPv6 Destination Address                       +
> > >   |                                                               |
> > >   +                                                               +
> > >   |                                                               |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
> > >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                        IPv4 Payload                           |
> > >   |                                                               |
> > >
> > > With this added, I believe that 4rd-U is a real progress over
> previously proposed Double translation and Encapsulation.
> > > It can make IMHO a valuable unified standard.
> > >
> > > Yet, I may have missed something else.
> > > New justified objections are therefore most welcome..
> > >
> > >
> > > Regards,
> > > RD
> >
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires
> >
>
>

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

hi Satoru-san,<br><br><div class=3D"gmail_quote">2011/10/17 Satoru Matsushi=
ma <span dir=3D"ltr">&lt;<a href=3D"mailto:satoru.matsushima@gmail.com" tar=
get=3D"_blank">satoru.matsushima@gmail.com</a>&gt;</span><br><blockquote st=
yle=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb=
(204, 204, 204); border-left-width: 1px; border-left-style: solid;" class=
=3D"gmail_quote">

Hi Maoke-san,<br>
<div><br>
On 2011/10/17, at 22:30, Maoke wrote:<br>
<br>
&gt; hi Satoru-san,<br>
&gt;<br>
&gt; may i understand that, as Remi&#39;s proposal is applied for the doubl=
e translation case, TTL being translated to IPv6 Hop Limit is enough? as is=
 stated in RFC6145, translator is a &quot;router&quot; and therefore the be=
havior should not be as same as the virtual link. right?<br>


<br>
</div>If so, just double translation is enough for that.<br>
</blockquote><div>=A0</div><div>it sounds nice. what i would like to have i=
s a consistent header processing for single/double translations and encapsu=
lation. </div><div>=A0</div><div>can we keep the TTL of IPv4 in the IPv6 he=
ader (plus fragment header but not anything more unless really necessary)? =
</div>

<div>=A0</div><div>can i understand that the following requirements are exc=
lusive to each other: (a) we want to keep TTL=A0changed in the IPv6 domain =
as=A0the behavior of translation; (b) we want to keep=A0TTL not changed unt=
il leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?=A0</di=
v>

<div>=A0</div><div>RFC6145 has=A0defined TTL&lt;-&gt;HopLimit translation. =
then how about using another reserved bit, say EF,=A0in the fragment header=
 for=A0indicating=A0the mode? if EF =3D 1, it is encapsulation mode, and th=
erefore the HopLimit in the base header keeps unchanged untile being transl=
ated=A0back to IPv4; if EF =3D=A00, it is translation mode, and the HopLimi=
t in the base header will decrease 1 for each hop.=A0btw, previously i sugg=
est using one of the reserved bits for the DF (e.g., the one before MF)=A0i=
nstead of the first bit of the identification in the ipv6 fragement header,=
 in order to avoid ambiguity caused by an IPv6 host in the single translati=
on. </div>
<div>=A0</div><div>thus i&#39;d like to suggest that one as follows, based =
on Remi&#39;s complement, where E is the indicator of encapsulation mode. c=
opying TOS in the fragment header is fine because it doesn&#39;t impact the=
 IPv6 dst (of single translation)=A0getting the original IPv4 src&#39;s rel=
ative=A0identification. </div>

<div><font face=3D"courier new,monospace"></font>=A0</div><div><font face=
=3D"courier new,monospace">=A0=A0=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=A0=A0=A0=A0=A0=A0 |Vers=3D6 |=A0=
=A0 TrafClass=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Flow Label=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>
=A0=A0=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+<br>=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0 Payload Length=A0=
=A0=A0=A0=A0=A0=A0 |Next Header=3D44 |=A0=A0 Hop Limit=A0=A0 |<br>=A0=A0=A0=
=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>=A0=A0=A0=A0=
=A0=A0 +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 +<br>=A0=A0=A0=A0=A0=A0 |=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>
=A0=A0=A0=A0=A0=A0 +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 IPv=
6 Source Address=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 +<br>=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 |<br>=A0=A0=A0=A0=A0=A0 +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 +<br>
=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>=A0=A0=A0=A0=
=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br=
>=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>
=A0=A0=A0=A0=A0=A0 +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 +<br>=A0=A0=A0=A0=
=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>=A0=A0=A0=A0=A0=A0 +=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 IPv6 Destination Address=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0 +<br>
=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>=A0=A0=A0=A0=
=A0=A0 +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 +<br>=A0=A0=A0=A0=A0=A0 |=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>
=A0=A0=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+<br>=A0=A0=A0=A0=A0=A0 |=A0 Next Header=A0 |=A0=A0=A0Reserved=A0=
=A0=A0 | IPv6=A0 Fragment Offset=A0=A0 |E|D|M|<br>=A0=A0=A0=A0=A0=A0 +-+-+-=
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A00=A0=A0=A0=A0=A0=A0=A0=A0|=A0=A0=A0 =
=A0TOS=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0 IPv4 Identification=A0=A0=A0=
=A0 |<br>=A0=A0=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+<br>=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 IPv4 Payload=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>
=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br></font><font=
 face=3D"courier new,monospace"></font></div><font face=3D"courier new,mono=
space"></font><div>unfortunately, however, even we free the first bit of IP=
v6 identification in the fragment header, we cannot put the TTL here (befor=
e the TOS) because traversing different paths may cause inconsistant IPv6 i=
dentification values in fragments of the same datagram=A0and disable reasse=
mble at the IPv6 dst (in the single translation mode). </div>
<div>=A0</div><div>the problem of EF in fragment header is, it requires tha=
t the implementation process fragment header before=A0descreasing the HopLi=
mit. is it feasible? </div><div>=A0</div><div>how do you think?</div><div>=
=A0</div>
<div>cheers,</div><div>maoke</div><div>=A0</div><blockquote style=3D"margin=
: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 20=
4); border-left-width: 1px; border-left-style: solid;" class=3D"gmail_quote=
">


cheers,<br>
<font color=3D"#888888">--satoru<br>
</font><div><div></div><div><br>
&gt; regards,<br>
&gt; maoke<br>
&gt; 2011/10/17 Satoru Matsushima &lt;<a href=3D"mailto:satoru.matsushima@g=
mail.com" target=3D"_blank">satoru.matsushima@gmail.com</a>&gt;<br>
&gt; Hi Remi-san,<br>
&gt;<br>
&gt; &gt; With this added, I believe that 4rd-U is a real progress over pre=
viously proposed Double translation and Encapsulation.<br>
&gt; &gt; It can make IMHO a valuable unified standard.<br>
&gt;<br>
&gt; Not enough. The original TTL value in IPv4 header must be carried.<br>
&gt;<br>
&gt; cheers,<br>
&gt; --satoru<br>
&gt;<br>
&gt;<br>
&gt; On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:<br>
&gt;<br>
&gt; &gt; Hi Satoru-san,<br>
&gt; &gt;<br>
&gt; &gt; Thank you for identifying a limitation of the 4rd-U<br>
&gt; &gt; You are right, as currently specified, &quot;it doesn&#39;t suppo=
rt diff-serv tunneling model, pipe and short-pipe&quot;.<br>
&gt; &gt; All these need e2e transparency to the IPv4 Type of Service.<br>
&gt; &gt;<br>
&gt; &gt; Fortunately, this is easy to fix: in the Identification field of =
the IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.<=
br>
&gt; &gt;<br>
&gt; &gt; The proposed 4r-U packet format becomes:<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<br>
&gt; &gt; =A0 |Vers=3D6 | =A0 TrafClass =A0 | =A0 =A0 =A0 =A0 =A0 =A0Flow L=
abel =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 Payload Length =A0 =A0 =A0 =A0|Next Header=
=3D44 | =A0 Hop Limit =A0 |<br>
&gt; &gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv6 Source Address =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0+<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv6 Destination Address =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<br>
&gt; &gt; =A0 | =A0Next Header =A0| =A0 =A0Reserved =A0 | IPv6 =A0Fragment =
Offset =A0 | 0 |M|<br>
&gt; &gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<br>
&gt; &gt; =A0 |D| =A0 =A0 =A00 =A0 =A0 =A0| =A0 =A0IPv4 TOS =A0 | =A0 =A0 =
=A0 IPv4 Identification =A0 =A0 |<br>
&gt; &gt; =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv4 Payload=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt;<br>
&gt; &gt; With this added, I believe that 4rd-U is a real progress over pre=
viously proposed Double translation and Encapsulation.<br>
&gt; &gt; It can make IMHO a valuable unified standard.<br>
&gt; &gt;<br>
&gt; &gt; Yet, I may have missed something else.<br>
&gt; &gt; New justified objections are therefore most welcome..<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt; RD<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Softwires mailing list<br>
&gt; <a href=3D"mailto:Softwires@ietf.org" target=3D"_blank">Softwires@ietf=
.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;<br>
<br>
</div></div></blockquote></div><br>

--0016e65da6eed3d2a904af7fac85--

From satoru.matsushima@gmail.com  Mon Oct 17 08:27:54 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 51FA921F8C2D for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 08:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jCEEDWBKAHgm for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 08:27:53 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 458FD21F8BB2 for <softwires@ietf.org>; Mon, 17 Oct 2011 08:27:53 -0700 (PDT)
Received: by qyk31 with SMTP id 31so1093060qyk.10 for <softwires@ietf.org>; Mon, 17 Oct 2011 08:27:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=BqOilnN0Q8pEFreoWrmUa2lHSJnj0MbB1seenu7kEl8=; b=lbOna/xo34ZkRUaqq60Qc/E9NyLwOecqeXO9mTaT7M8cF7JznDMtESr/tCqcRTVvk5 HaHSKRW1NRu/rdKGm7DdsdBFGnzbCj6RsUG7ZYfbf5jE5ScGAOtWl4ol7O6Bv4U11loB aHIZ78BbN6VcHwj8h4DhsAurpVyq/xvQNCE58=
Received: by 10.68.74.33 with SMTP id q1mr38826336pbv.71.1318865272364; Mon, 17 Oct 2011 08:27:52 -0700 (PDT)
Received: from [192.168.10.54] (softbank221038132005.bbtec.net. [221.38.132.5]) by mx.google.com with ESMTPS id y4sm56652666pbe.4.2011.10.17.08.27.48 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Oct 2011 08:27:50 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com>
Date: Tue, 18 Oct 2011 00:27:45 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com>
To: Maoke <fibrib@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 15:27:54 -0000

On 2011/10/17, at 23:46, Maoke wrote:

> hi Satoru-san,
>=20
> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
> Hi Maoke-san,
>=20
> On 2011/10/17, at 22:30, Maoke wrote:
>=20
> > hi Satoru-san,
> >
> > may i understand that, as Remi's proposal is applied for the double =
translation case, TTL being translated to IPv6 Hop Limit is enough? as =
is stated in RFC6145, translator is a "router" and therefore the =
behavior should not be as same as the virtual link. right?
>=20
> If so, just double translation is enough for that.
> =20
> it sounds nice. what i would like to have is a consistent header =
processing for single/double translations and encapsulation.

I think that encapsulation and double translation can't be consistent to =
processing packet at all.

> =20
> can we keep the TTL of IPv4 in the IPv6 header (plus fragment header =
but not anything more unless really necessary)?
> =20
> can i understand that the following requirements are exclusive to each =
other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?=20

I think that these are exclusive.


> =20
> RFC6145 has defined TTL<->HopLimit translation. then how about using =
another reserved bit, say EF, in the fragment header for indicating the =
mode? if EF =3D 1, it is encapsulation mode, and therefore the HopLimit =
in the base header keeps unchanged untile being translated back to IPv4; =
if EF =3D 0, it is translation mode, and the HopLimit in the base header =
will decrease 1 for each hop. btw, previously i suggest using one of the =
reserved bits for the DF (e.g., the one before MF) instead of the first =
bit of the identification in the ipv6 fragement header, in order to =
avoid ambiguity caused by an IPv6 host in the single translation.

It seems that adding new semantics more. Very creative, but is it really =
needed even we already have both encaps and translation? When you want =
to define more new semantics, it would be better you define new protocol =
number for 4rd-U.


> =20
> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
> =20
>        =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
>        =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
>        =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                                                               =
|
>        +                                                               =
+
>        |                                                               =
|
>        +                  IPv6 Source Address                          =
+
>        |                                                               =
|
>        +                                                               =
+
>        |                                                               =
|
>        =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                                                               =
|
>        +                                                               =
+
>        |                                                               =
|
>        +                IPv6 Destination Address                       =
+
>        |                                                               =
|
>        +                                                               =
+
>        |                                                               =
|
>        =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
>        =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |      0        |     TOS       |       IPv4 Identification     =
|
>        =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                        IPv4 Payload                           =
|
>        |                                                               =
|
> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
> =20
> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
> =20
> how do you think?

IMHO, I'm not sure it is good idea to change the semantics of the IPv6 =
fragment. If a router receives 4rd-U packets, which router doesn't =
understand 4rd-U, processing these packets as fragmented packets could =
cause problem that sounds buffer exhaust attack. And I also think that =
if we need to add new semantics even we can utilize IPv6 fragment, it =
would be better to define new protocol number for 4rd-U. However, I =
don't think that we need to request to define it, because existing =
encapsulation and translation can be utilized for each appropriate =
situation.

cheers,
--satoru


> =20
> cheers,
> maoke
> =20
> cheers,
> --satoru
>=20
> > regards,
> > maoke
> > 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
> > Hi Remi-san,
> >
> > > With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> > > It can make IMHO a valuable unified standard.
> >
> > Not enough. The original TTL value in IPv4 header must be carried.
> >
> > cheers,
> > --satoru
> >
> >
> > On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
> >
> > > Hi Satoru-san,
> > >
> > > Thank you for identifying a limitation of the 4rd-U
> > > You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
> > > All these need e2e transparency to the IPv4 Type of Service.
> > >
> > > Fortunately, this is easy to fix: in the Identification field of =
the IPv6 Fragment header, copy not only the DF bits but also the IPv4 =
TOS.
> > >
> > > The proposed 4r-U packet format becomes:
> > >
> > >
> > >   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |Vers=3D6 |   TrafClass   |            Flow Label                =
 |
> > >   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |         Payload Length        |Next Header=3D44 |   Hop Limit  =
 |
> > >   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                                                               =
|
> > >   +                                                               =
+
> > >   |                                                               =
|
> > >   +                  IPv6 Source Address                          =
+
> > >   |                                                               =
|
> > >   +                                                               =
+
> > >   |                                                               =
|
> > >   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                                                               =
|
> > >   +                                                               =
+
> > >   |                                                               =
|
> > >   +                IPv6 Destination Address                       =
+
> > >   |                                                               =
|
> > >   +                                                               =
+
> > >   |                                                               =
|
> > >   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 =
|M|
> > >   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |D|      0      |    IPv4 TOS   |       IPv4 Identification     =
|
> > >   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > >   |                        IPv4 Payload                           =
|
> > >   |                                                               =
|
> > >
> > > With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> > > It can make IMHO a valuable unified standard.
> > >
> > > Yet, I may have missed something else.
> > > New justified objections are therefore most welcome..
> > >
> > >
> > > Regards,
> > > RD
> >
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires
> >
>=20
>=20


From fibrib@gmail.com  Mon Oct 17 08:50:51 2011
Return-Path: <fibrib@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 5009221F8C90 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 08:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.308
X-Spam-Level: 
X-Spam-Status: No, score=-3.308 tagged_above=-999 required=5 tests=[AWL=0.290,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5-oXE2ve93r for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 08:50:50 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6180921F8C8B for <softwires@ietf.org>; Mon, 17 Oct 2011 08:50:50 -0700 (PDT)
Received: by qadb12 with SMTP id b12so2856400qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 08:50:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Jt4824yNaFLLqQE0xZfNudTWDacVQiqt4k2ZyBD4EFI=; b=NQtgPiTs+gLez7+UQszlh3UDu+vKqmZiY6cGavPj+H5EHVaK3RtWkZqV9KRpV6icEp pzOOiWfbY+Y4wB+D6qiLPGUjTnR57ME0G1uHN59oLNEqlWpKJdWvN/dzZobg1dLY/9mZ LG7hB0c1XEeDCfwskxhtn3QSP9QeNWnPABXzo=
MIME-Version: 1.0
Received: by 10.229.63.169 with SMTP id b41mr4223374qci.145.1318866649897; Mon, 17 Oct 2011 08:50:49 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Mon, 17 Oct 2011 08:50:49 -0700 (PDT)
In-Reply-To: <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com>
Date: Tue, 18 Oct 2011 00:50:49 +0900
Message-ID: <CAFUBMqXDSaKGsUUW6f+sfnN64DoEcBGr-TzifXtUgWh=RWUdnQ@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Content-Type: multipart/alternative; boundary=0016e65da6ee2c5bea04af809227
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 15:50:51 -0000

--0016e65da6ee2c5bea04af809227
Content-Type: text/plain; charset=ISO-8859-1

hi Satoru-san,

2011/10/18 Satoru Matsushima <satoru.matsushima@gmail.com>

> > it sounds nice. what i would like to have is a consistent header
> processing for single/double translations and encapsulation.
>
> I think that encapsulation and double translation can't be consistent to
> processing packet at all.
>

thanks for the correction. i meant the behavior similar to encapsulation but
implemented as double translation, but the wording was  wrong. :P


>
> >
> > can we keep the TTL of IPv4 in the IPv6 header (plus fragment header but
> not anything more unless really necessary)?
> >
> > can i understand that the following requirements are exclusive to each
> other: (a) we want to keep TTL changed in the IPv6 domain as the behavior of
> translation; (b) we want to keep TTL not changed until leaving the IPv6
> domain as the behavior of encapsulation (4rd-U)?
>
> I think that these are exclusive.
>
>
> >
> > RFC6145 has defined TTL<->HopLimit translation. then how about using
> another reserved bit, say EF, in the fragment header for indicating the
> mode? if EF = 1, it is encapsulation mode, and therefore the HopLimit in the
> base header keeps unchanged untile being translated back to IPv4; if EF = 0,
> it is translation mode, and the HopLimit in the base header will decrease 1
> for each hop. btw, previously i suggest using one of the reserved bits for
> the DF (e.g., the one before MF) instead of the first bit of the
> identification in the ipv6 fragement header, in order to avoid ambiguity
> caused by an IPv6 host in the single translation.
>
> It seems that adding new semantics more. Very creative, but is it really
> needed even we already have both encaps and translation? When you want to
> define more new semantics, it would be better you define new protocol number
> for 4rd-U.


> ...

>
> > the problem of EF in fragment header is, it requires that the
> implementation process fragment header before descreasing the HopLimit. is
> it feasible?
> >
> > how do you think?
>
> IMHO, I'm not sure it is good idea to change the semantics of the IPv6
> fragment. If a router receives 4rd-U packets, which router doesn't
> understand 4rd-U, processing these packets as fragmented packets could cause
> problem that sounds buffer exhaust attack. And I also think that if we need
> to add new semantics even we can utilize IPv6 fragment, it would be better
> to define new protocol number for 4rd-U. However, I don't think that we need
> to request to define it, because existing encapsulation and translation can
> be utilized for each appropriate situation.
>
>
good point. however, Remi's proposed problem is a real concern. the solution
putting DF as the first bit at IPv6 identification doesn't cause the trouble
on routers but may hurt the single translation behavior. the translator
should not know if the packet will be translated back to IPv4 later or not.

cheers,
maoke


> cheers,
> --satoru
>

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

hi Satoru-san, <br><br><div class=3D"gmail_quote">2011/10/18 Satoru Matsush=
ima <span dir=3D"ltr">&lt;<a href=3D"mailto:satoru.matsushima@gmail.com">sa=
toru.matsushima@gmail.com</a>&gt;</span><br><blockquote style=3D"margin: 0p=
x 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); =
border-left-width: 1px; border-left-style: solid;" class=3D"gmail_quote">
<div class=3D"im">&gt; it sounds nice. what i would like to have is a consi=
stent header processing for single/double translations and encapsulation.<b=
r>
<br>
</div>I think that encapsulation and double translation can&#39;t be consis=
tent to processing packet at all.<br></blockquote><div>=A0</div><div>thanks=
 for the correction. i=A0meant=A0the behavior similar to encapsulation but =
implemented as double translation, but the wording was=A0 wrong. :P</div>
<div>=A0</div><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left:=
 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border=
-left-style: solid;" class=3D"gmail_quote">
<div class=3D"im"><br>
&gt;<br>
&gt; can we keep the TTL of IPv4 in the IPv6 header (plus fragment header b=
ut not anything more unless really necessary)?<br>
&gt;<br>
&gt; can i understand that the following requirements are exclusive to each=
 other: (a) we want to keep TTL changed in the IPv6 domain as the behavior =
of translation; (b) we want to keep TTL not changed until leaving the IPv6 =
domain as the behavior of encapsulation (4rd-U)?<br>

<br>
</div>I think that these are exclusive.<br>
<div class=3D"im"><br><br>
&gt;<br>
&gt; RFC6145 has defined TTL&lt;-&gt;HopLimit translation. then how about u=
sing another reserved bit, say EF, in the fragment header for indicating th=
e mode? if EF =3D 1, it is encapsulation mode, and therefore the HopLimit i=
n the base header keeps unchanged untile being translated back to IPv4; if =
EF =3D 0, it is translation mode, and the HopLimit in the base header will =
decrease 1 for each hop. btw, previously i suggest using one of the reserve=
d bits for the DF (e.g., the one before MF) instead of the first bit of the=
 identification in the ipv6 fragement header, in order to avoid ambiguity c=
aused by an IPv6 host in the single translation.<br>

<br>
</div>It seems that adding new semantics more. Very creative, but is it rea=
lly needed even we already have both encaps and translation? When you want =
to define more new semantics, it would be better you define new protocol nu=
mber for 4rd-U.=A0</blockquote>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote">=A0<br>...=A0</blockquote><blockquote style=3D=
"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, =
204, 204); border-left-width: 1px; border-left-style: solid;" class=3D"gmai=
l_quote">

&gt;<br>
&gt; the problem of EF in fragment header is, it requires that the implemen=
tation process fragment header before descreasing the HopLimit. is it feasi=
ble?<br>
&gt;<br>
&gt; how do you think?<br>
<br>
</blockquote><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: =
1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-=
left-style: solid;" class=3D"gmail_quote">IMHO, I&#39;m not sure it is good=
 idea to change the semantics of the IPv6 fragment. If a router receives 4r=
d-U packets, which router doesn&#39;t understand 4rd-U, processing these pa=
ckets as fragmented packets could cause problem that sounds buffer exhaust =
attack. And I also think that if we need to add new semantics even we can u=
tilize IPv6 fragment, it would be better to define new protocol number for =
4rd-U. However, I don&#39;t think that we need to request to define it, bec=
ause existing encapsulation and translation can be utilized for each approp=
riate situation.<br>

<br></blockquote><div>=A0</div><div>good point.=A0however, Remi&#39;s propo=
sed problem is a real concern. the solution putting DF as the first bit at =
IPv6 identification doesn&#39;t cause the trouble on routers but may hurt t=
he single translation behavior. the translator should not know if the packe=
t will be translated back to IPv4 later or not. </div>
<div>=A0</div><div>cheers,</div><div>maoke</div><div>=A0</div><blockquote s=
tyle=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rg=
b(204, 204, 204); border-left-width: 1px; border-left-style: solid;" class=
=3D"gmail_quote">

cheers,<br>
<font color=3D"#888888">--satoru<br>
</font></blockquote></div>

--0016e65da6ee2c5bea04af809227--

From despres.remi@laposte.net  Mon Oct 17 09:09:15 2011
Return-Path: <despres.remi@laposte.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 6560D21F8D35 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+dpUm492fQi for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:09:14 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 2EDA121F8D2A for <softwires@ietf.org>; Mon, 17 Oct 2011 09:09:12 -0700 (PDT)
Received: from [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb] (unknown [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb]) by smtp1-g21.free.fr (Postfix) with ESMTP id 86C69940509; Mon, 17 Oct 2011 18:09:04 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com>
Date: Mon, 17 Oct 2011 18:09:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 16:09:15 -0000

Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :

> On 2011/10/17, at 23:46, Maoke wrote:
>=20
>> hi Satoru-san,
>>=20
>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>> Hi Maoke-san,
>>=20
>> On 2011/10/17, at 22:30, Maoke wrote:
>>=20
>>> hi Satoru-san,
>>>=20
>>> may i understand that, as Remi's proposal is applied for the double =
translation case, TTL being translated to IPv6 Hop Limit is enough? as =
is stated in RFC6145, translator is a "router" and therefore the =
behavior should not be as same as the virtual link. right?
>>=20
>> If so, just double translation is enough for that.
>>=20
>> it sounds nice. what i would like to have is a consistent header =
processing for single/double translations and encapsulation.
>=20
> I think that encapsulation and double translation can't be consistent =
to processing packet at all.

4rd-u (duly completed with TOS transparency) is neither Double RFC6145 =
translation nor Encapsulation.
It is believed to have advantages over both of them.
Disadvantages has AFAIK still to be identified.


>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment header =
but not anything more unless really necessary)?
>>=20
>> can i understand that the following requirements are exclusive to =
each other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?=20
>=20
> I think that these are exclusive.

Indeed, one cant't do both simultaneously, but AFAIK either choice is =
acceptable.=20
Is there one you prefer, for which reason?

>> RFC6145 has defined TTL<->HopLimit translation. then how about using =
another reserved bit, say EF, in the fragment header for indicating the =
mode? if EF =3D 1, it is encapsulation mode, and therefore the HopLimit =
in the base header keeps unchanged untile being translated back to IPv4; =
if EF =3D 0, it is translation mode, and the HopLimit in the base header =
will decrease 1 for each hop. btw, previously i suggest using one of the =
reserved bits for the DF (e.g., the one before MF) instead of the first =
bit of the identification in the ipv6 fragement header, in order to =
avoid ambiguity caused by an IPv6 host in the single translation.
>=20
> It seems that adding new semantics more. Very creative, but is it =
really needed even we already have both encaps and translation? When you =
want to define more new semantics, it would be better you define new =
protocol number for 4rd-U.

The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.

A key advantage of Double translation over Encapsulation, is that the =
IPv6 next header is the same as the Protocol of the conveyed IPv4 =
packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.

>> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
>>=20
>>       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>       |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
>>       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>       |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
>>       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>       |                                                               =
|
>>       +                                                               =
+
>>       |                                                               =
|
>>       +                  IPv6 Source Address                          =
+
>>       |                                                               =
|
>>       +                                                               =
+
>>       |                                                               =
|
>>       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>       |                                                               =
|
>>       +                                                               =
+
>>       |                                                               =
|
>>       +                IPv6 Destination Address                       =
+
>>       |                                                               =
|
>>       +                                                               =
+
>>       |                                                               =
|
>>       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>       |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
>>       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>       |      0        |     TOS       |       IPv4 Identification     =
|
>>       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>       |                        IPv4 Payload                           =
|
>>       |                                                               =
|
>> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
>>=20
>> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
>>=20
>> how do you think?
>=20
> IMHO, I'm not sure it is good idea to change the semantics of the IPv6 =
fragment. If a router receives 4rd-U packets, which router doesn't =
understand 4rd-U, processing these packets as fragmented packets could =
cause problem that sounds buffer exhaust attack.

I don't see that:
- IPv6 routers are not concerned with fragmentation.
- the 4rd-U endpoint doesn't need to keep anything in a reassembly =
buffer if a conveyed IPv4 packet is completely contained in a single =
IPv6 packet.

> And I also think that if we need to add new semantics even we can =
utilize IPv6 fragment, it would be better to define new protocol number =
for 4rd-U.

See above why a new protocol number wouldn't be workable.

> However, I don't think that we need to request to define it, because =
existing encapsulation and translation can be utilized for each =
appropriate situation.



The point isn't to prevent any ISP from deploy for its own use any =
design that works.

Yet, having only ONE STANDARD for a given need is better than several.=20=

I hope you can agree with that.
(In this case, the need is stateless support of residual IPv4 across =
IPv6-only networks.)

AFAIK, 4rd-U is better for this than double translation (say 4rd-T), and =
better than encapsulation (say 4rd-E), because it combines advantages of =
both (applicability of IPv6 O&M tools (a feature of 4rd-T), AND e2e =
transparency to IPv4 semantics (a feature of 4rd-E). =20
If you still believe this is not right, an explanation will of course be =
welcome.

Cheers,
RD




>=20
> cheers,
> --satoru
>=20
>=20
>>=20
>> cheers,
>> maoke
>>=20
>> cheers,
>> --satoru
>>=20
>>> regards,
>>> maoke
>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>> Hi Remi-san,
>>>=20
>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>> It can make IMHO a valuable unified standard.
>>>=20
>>> Not enough. The original TTL value in IPv4 header must be carried.
>>>=20
>>> cheers,
>>> --satoru
>>>=20
>>>=20
>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>>>=20
>>>> Hi Satoru-san,
>>>>=20
>>>> Thank you for identifying a limitation of the 4rd-U
>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
>>>> All these need e2e transparency to the IPv4 Type of Service.
>>>>=20
>>>> Fortunately, this is easy to fix: in the Identification field of =
the IPv6 Fragment header, copy not only the DF bits but also the IPv4 =
TOS.
>>>>=20
>>>> The proposed 4r-U packet format becomes:
>>>>=20
>>>>=20
>>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>  |Vers=3D6 |   TrafClass   |            Flow Label                 =
|
>>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>  |         Payload Length        |Next Header=3D44 |   Hop Limit   =
|
>>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>  |                                                               |
>>>>  +                                                               +
>>>>  |                                                               |
>>>>  +                  IPv6 Source Address                          +
>>>>  |                                                               |
>>>>  +                                                               +
>>>>  |                                                               |
>>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>  |                                                               |
>>>>  +                                                               +
>>>>  |                                                               |
>>>>  +                IPv6 Destination Address                       +
>>>>  |                                                               |
>>>>  +                                                               +
>>>>  |                                                               |
>>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>  |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
>>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>  |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
>>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>  |                        IPv4 Payload                           |
>>>>  |                                                               |
>>>>=20
>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>> It can make IMHO a valuable unified standard.
>>>>=20
>>>> Yet, I may have missed something else.
>>>> New justified objections are therefore most welcome..
>>>>=20
>>>>=20
>>>> Regards,
>>>> RD
>>>=20
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>>=20
>>=20
>>=20
>=20


From ichiroumakino@gmail.com  Mon Oct 17 09:15:52 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 573E921F8A70 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.337
X-Spam-Level: 
X-Spam-Status: No, score=-3.337 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxMU34-hefD1 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:15:51 -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 EAE6521F86A5 for <softwires@ietf.org>; Mon, 17 Oct 2011 09:15:50 -0700 (PDT)
Received: by wyh22 with SMTP id 22so908003wyh.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 09:15:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=8OUWbWgojS2aSqboZ7Anq039znpY3Qqtpa6vD5dLM5g=; b=AC9SglunuZK20w/HI/44utzDyhqPTavopG49c3c+K54cTe7S59P1FCTqHHWd+VYdKJ 7TIwr/iuZjq5izcwMRnAHh8SZwKympICeBDmBPbp4I77/4o1njTF7Py4D/uj2l7rG9Fl Se5clIxAwJR3Ps9jROmKe2RGqXePW1/+iO06I=
Received: by 10.227.179.14 with SMTP id bo14mr6988492wbb.90.1318868148416; Mon, 17 Oct 2011 09:15:48 -0700 (PDT)
Received: from dhcp-10-61-100-173.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id ff1sm6647156wbb.8.2011.10.17.09.15.44 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Oct 2011 09:15:47 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net>
Date: Mon, 17 Oct 2011 18:15:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 16:15:52 -0000

Remi,

how is 4rd-U different from translation?

cheers,
Ole


On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:

>=20
> Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :
>=20
>> On 2011/10/17, at 23:46, Maoke wrote:
>>=20
>>> hi Satoru-san,
>>>=20
>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>> Hi Maoke-san,
>>>=20
>>> On 2011/10/17, at 22:30, Maoke wrote:
>>>=20
>>>> hi Satoru-san,
>>>>=20
>>>> may i understand that, as Remi's proposal is applied for the double =
translation case, TTL being translated to IPv6 Hop Limit is enough? as =
is stated in RFC6145, translator is a "router" and therefore the =
behavior should not be as same as the virtual link. right?
>>>=20
>>> If so, just double translation is enough for that.
>>>=20
>>> it sounds nice. what i would like to have is a consistent header =
processing for single/double translations and encapsulation.
>>=20
>> I think that encapsulation and double translation can't be consistent =
to processing packet at all.
>=20
> 4rd-u (duly completed with TOS transparency) is neither Double RFC6145 =
translation nor Encapsulation.
> It is believed to have advantages over both of them.
> Disadvantages has AFAIK still to be identified.
>=20
>=20
>>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment header =
but not anything more unless really necessary)?
>>>=20
>>> can i understand that the following requirements are exclusive to =
each other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?=20
>>=20
>> I think that these are exclusive.
>=20
> Indeed, one cant't do both simultaneously, but AFAIK either choice is =
acceptable.=20
> Is there one you prefer, for which reason?
>=20
>>> RFC6145 has defined TTL<->HopLimit translation. then how about using =
another reserved bit, say EF, in the fragment header for indicating the =
mode? if EF =3D 1, it is encapsulation mode, and therefore the HopLimit =
in the base header keeps unchanged untile being translated back to IPv4; =
if EF =3D 0, it is translation mode, and the HopLimit in the base header =
will decrease 1 for each hop. btw, previously i suggest using one of the =
reserved bits for the DF (e.g., the one before MF) instead of the first =
bit of the identification in the ipv6 fragement header, in order to =
avoid ambiguity caused by an IPv6 host in the single translation.
>>=20
>> It seems that adding new semantics more. Very creative, but is it =
really needed even we already have both encaps and translation? When you =
want to define more new semantics, it would be better you define new =
protocol number for 4rd-U.
>=20
> The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.
>=20
> A key advantage of Double translation over Encapsulation, is that the =
IPv6 next header is the same as the Protocol of the conveyed IPv4 =
packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.
>=20
>>> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
>>>=20
>>>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
>>>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
>>>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |                                                               =
|
>>>      +                                                               =
+
>>>      |                                                               =
|
>>>      +                  IPv6 Source Address                          =
+
>>>      |                                                               =
|
>>>      +                                                               =
+
>>>      |                                                               =
|
>>>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |                                                               =
|
>>>      +                                                               =
+
>>>      |                                                               =
|
>>>      +                IPv6 Destination Address                       =
+
>>>      |                                                               =
|
>>>      +                                                               =
+
>>>      |                                                               =
|
>>>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
>>>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |      0        |     TOS       |       IPv4 Identification     =
|
>>>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |                        IPv4 Payload                           =
|
>>>      |                                                               =
|
>>> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
>>>=20
>>> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
>>>=20
>>> how do you think?
>>=20
>> IMHO, I'm not sure it is good idea to change the semantics of the =
IPv6 fragment. If a router receives 4rd-U packets, which router doesn't =
understand 4rd-U, processing these packets as fragmented packets could =
cause problem that sounds buffer exhaust attack.
>=20
> I don't see that:
> - IPv6 routers are not concerned with fragmentation.
> - the 4rd-U endpoint doesn't need to keep anything in a reassembly =
buffer if a conveyed IPv4 packet is completely contained in a single =
IPv6 packet.
>=20
>> And I also think that if we need to add new semantics even we can =
utilize IPv6 fragment, it would be better to define new protocol number =
for 4rd-U.
>=20
> See above why a new protocol number wouldn't be workable.
>=20
>> However, I don't think that we need to request to define it, because =
existing encapsulation and translation can be utilized for each =
appropriate situation.
>=20
>=20
>=20
> The point isn't to prevent any ISP from deploy for its own use any =
design that works.
>=20
> Yet, having only ONE STANDARD for a given need is better than several.=20=

> I hope you can agree with that.
> (In this case, the need is stateless support of residual IPv4 across =
IPv6-only networks.)
>=20
> AFAIK, 4rd-U is better for this than double translation (say 4rd-T), =
and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E). =20
> If you still believe this is not right, an explanation will of course =
be welcome.
>=20
> Cheers,
> RD
>=20
>=20
>=20
>=20
>>=20
>> cheers,
>> --satoru
>>=20
>>=20
>>>=20
>>> cheers,
>>> maoke
>>>=20
>>> cheers,
>>> --satoru
>>>=20
>>>> regards,
>>>> maoke
>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>> Hi Remi-san,
>>>>=20
>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>>> It can make IMHO a valuable unified standard.
>>>>=20
>>>> Not enough. The original TTL value in IPv4 header must be carried.
>>>>=20
>>>> cheers,
>>>> --satoru
>>>>=20
>>>>=20
>>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>>>>=20
>>>>> Hi Satoru-san,
>>>>>=20
>>>>> Thank you for identifying a limitation of the 4rd-U
>>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
>>>>> All these need e2e transparency to the IPv4 Type of Service.
>>>>>=20
>>>>> Fortunately, this is easy to fix: in the Identification field of =
the IPv6 Fragment header, copy not only the DF bits but also the IPv4 =
TOS.
>>>>>=20
>>>>> The proposed 4r-U packet format becomes:
>>>>>=20
>>>>>=20
>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>> |Vers=3D6 |   TrafClass   |            Flow Label                 =
|
>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>> |         Payload Length        |Next Header=3D44 |   Hop Limit   =
|
>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>> |                                                               |
>>>>> +                                                               +
>>>>> |                                                               |
>>>>> +                  IPv6 Source Address                          +
>>>>> |                                                               |
>>>>> +                                                               +
>>>>> |                                                               |
>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>> |                                                               |
>>>>> +                                                               +
>>>>> |                                                               |
>>>>> +                IPv6 Destination Address                       +
>>>>> |                                                               |
>>>>> +                                                               +
>>>>> |                                                               |
>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>> |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>> |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>> |                        IPv4 Payload                           |
>>>>> |                                                               |
>>>>>=20
>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>>> It can make IMHO a valuable unified standard.
>>>>>=20
>>>>> Yet, I may have missed something else.
>>>>> New justified objections are therefore most welcome..
>>>>>=20
>>>>>=20
>>>>> Regards,
>>>>> RD
>>>>=20
>>>> _______________________________________________
>>>> Softwires mailing list
>>>> Softwires@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/softwires
>>>>=20
>>>=20
>>>=20
>>=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From despres.remi@free.fr  Mon Oct 17 09:21:36 2011
Return-Path: <despres.remi@free.fr>
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 26BB321F8B0D for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NlH4+JwCEM3p for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:21:35 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 67A5D21F8797 for <softwires@ietf.org>; Mon, 17 Oct 2011 09:21:26 -0700 (PDT)
Received: from [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb] (unknown [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb]) by smtp1-g21.free.fr (Postfix) with ESMTP id 21E49940525; Mon, 17 Oct 2011 18:21:20 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-3--888620067
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@free.fr>
In-Reply-To: <CAFUBMqVni_GNqmEx-FwzNUKUD1x2hN=xoe7Zc9pre4rfmGBWRw@mail.gmail.com>
Date: Mon, 17 Oct 2011 18:21:19 +0200
Message-Id: <C87E17E8-8686-4D01-939E-E6C7C3E5DF58@free.fr>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <14AB4609-752F-44E2-BE75-EB414CC2ACFA@ipinfusion.com> <CAFUBMqVni_GNqmEx-FwzNUKUD1x2hN=xoe7Zc9pre4rfmGBWRw@mail.gmail.com>
To: Maoke <fibrib@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 17 Oct 2011 16:21:36 -0000

--Apple-Mail-3--888620067
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Maoke,

On 2011/10/12, you wrote:
"... considering the double translation is a case of translation. it is =
possible that a src host with an IPv4-translatable IPv6 address =
generates a fragment header with a 32-bit identifier happening to have =
the first 16 bit as either 0x8000 or 0x0000, making a fake D bit in your =
current proposal."

An important point is that the IP identifier needs to be unique ONLY for =
each <SRC, DST> pair.
If 4rd addresses are deterministically recognizable (with the V octet in =
bits 64-71), there is no risk of confusion with an IP identification =
generated for another purpose than 4rd.

Hope it clarifies.

Cheers,
RD=

--Apple-Mail-3--888620067
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Maoke,<div><br><div><div>On 2011/10/12, you =
wrote:</div></div><div>"...&nbsp;<span class=3D"Apple-style-span" =
style=3D"font-family: monospace; ">considering the double translation is =
a case of translation. it&nbsp;is possible that&nbsp;a src host with an =
IPv4-translatable IPv6 address&nbsp;generates a fragment header with a =
32-bit identifier happening to have&nbsp;the first 16 bit as either =
0x8000 or 0x0000,&nbsp;making a fake D bit in your&nbsp;current =
proposal."</span></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: monospace; "><br></span></div><div><font =
class=3D"Apple-style-span" face=3D"monospace">An important point is that =
the IP identifier needs to be unique ONLY for each &lt;SRC, DST&gt; =
pair.</font></div></div><div><font class=3D"Apple-style-span" =
face=3D"monospace">If 4rd addresses are deterministically recognizable =
(with the V octet in bits 64-71), there is no risk of confusion with an =
IP identification generated for another purpose than =
4rd.</font></div><div><font class=3D"Apple-style-span" =
face=3D"monospace"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"monospace">Hope it clarifies.</font></div><div><font =
class=3D"Apple-style-span" face=3D"monospace"><br></font></div><div><font =
class=3D"Apple-style-span" =
face=3D"monospace">Cheers,</font></div><div><font =
class=3D"Apple-style-span" =
face=3D"monospace">RD</font></div></body></html>=

--Apple-Mail-3--888620067--

From despres.remi@laposte.net  Mon Oct 17 09:26:32 2011
Return-Path: <despres.remi@laposte.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 4782B21F8C56 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level: 
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[AWL=0.297,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jx01mjOB1j6e for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:26:31 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by ietfa.amsl.com (Postfix) with ESMTP id CF9AE21F8C55 for <softwires@ietf.org>; Mon, 17 Oct 2011 09:26:30 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 132227000138; Mon, 17 Oct 2011 18:26:30 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id AC97D7000114; Mon, 17 Oct 2011 18:26:25 +0200 (CEST)
X-SFR-UUID: 20111017162625707.AC97D7000114@msfrf2108.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org>
Date: Mon, 17 Oct 2011 18:26:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 16:26:32 -0000

Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :

> Remi,
>=20
> how is 4rd-U different from translation?

Functionally, full network transparency to DF bit (and TOS with the =
complement that was missing).
Technically, see for instance Figure 1 of the draft.

Cheers,
RD =20


>=20
> cheers,
> Ole
>=20
>=20
> On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:
>=20
>>=20
>> Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :
>>=20
>>> On 2011/10/17, at 23:46, Maoke wrote:
>>>=20
>>>> hi Satoru-san,
>>>>=20
>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>> Hi Maoke-san,
>>>>=20
>>>> On 2011/10/17, at 22:30, Maoke wrote:
>>>>=20
>>>>> hi Satoru-san,
>>>>>=20
>>>>> may i understand that, as Remi's proposal is applied for the =
double translation case, TTL being translated to IPv6 Hop Limit is =
enough? as is stated in RFC6145, translator is a "router" and therefore =
the behavior should not be as same as the virtual link. right?
>>>>=20
>>>> If so, just double translation is enough for that.
>>>>=20
>>>> it sounds nice. what i would like to have is a consistent header =
processing for single/double translations and encapsulation.
>>>=20
>>> I think that encapsulation and double translation can't be =
consistent to processing packet at all.
>>=20
>> 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.
>> It is believed to have advantages over both of them.
>> Disadvantages has AFAIK still to be identified.
>>=20
>>=20
>>>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment =
header but not anything more unless really necessary)?
>>>>=20
>>>> can i understand that the following requirements are exclusive to =
each other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?=20
>>>=20
>>> I think that these are exclusive.
>>=20
>> Indeed, one cant't do both simultaneously, but AFAIK either choice is =
acceptable.=20
>> Is there one you prefer, for which reason?
>>=20
>>>> RFC6145 has defined TTL<->HopLimit translation. then how about =
using another reserved bit, say EF, in the fragment header for =
indicating the mode? if EF =3D 1, it is encapsulation mode, and =
therefore the HopLimit in the base header keeps unchanged untile being =
translated back to IPv4; if EF =3D 0, it is translation mode, and the =
HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.
>>>=20
>>> It seems that adding new semantics more. Very creative, but is it =
really needed even we already have both encaps and translation? When you =
want to define more new semantics, it would be better you define new =
protocol number for 4rd-U.
>>=20
>> The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.
>>=20
>> A key advantage of Double translation over Encapsulation, is that the =
IPv6 next header is the same as the Protocol of the conveyed IPv4 =
packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.
>>=20
>>>> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
>>>>=20
>>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>     |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
>>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>     |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
>>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>     |                                                               =
|
>>>>     +                                                               =
+
>>>>     |                                                               =
|
>>>>     +                  IPv6 Source Address                          =
+
>>>>     |                                                               =
|
>>>>     +                                                               =
+
>>>>     |                                                               =
|
>>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>     |                                                               =
|
>>>>     +                                                               =
+
>>>>     |                                                               =
|
>>>>     +                IPv6 Destination Address                       =
+
>>>>     |                                                               =
|
>>>>     +                                                               =
+
>>>>     |                                                               =
|
>>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>     |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
>>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>     |      0        |     TOS       |       IPv4 Identification     =
|
>>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>     |                        IPv4 Payload                           =
|
>>>>     |                                                               =
|
>>>> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
>>>>=20
>>>> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
>>>>=20
>>>> how do you think?
>>>=20
>>> IMHO, I'm not sure it is good idea to change the semantics of the =
IPv6 fragment. If a router receives 4rd-U packets, which router doesn't =
understand 4rd-U, processing these packets as fragmented packets could =
cause problem that sounds buffer exhaust attack.
>>=20
>> I don't see that:
>> - IPv6 routers are not concerned with fragmentation.
>> - the 4rd-U endpoint doesn't need to keep anything in a reassembly =
buffer if a conveyed IPv4 packet is completely contained in a single =
IPv6 packet.
>>=20
>>> And I also think that if we need to add new semantics even we can =
utilize IPv6 fragment, it would be better to define new protocol number =
for 4rd-U.
>>=20
>> See above why a new protocol number wouldn't be workable.
>>=20
>>> However, I don't think that we need to request to define it, because =
existing encapsulation and translation can be utilized for each =
appropriate situation.
>>=20
>>=20
>>=20
>> The point isn't to prevent any ISP from deploy for its own use any =
design that works.
>>=20
>> Yet, having only ONE STANDARD for a given need is better than =
several.=20
>> I hope you can agree with that.
>> (In this case, the need is stateless support of residual IPv4 across =
IPv6-only networks.)
>>=20
>> AFAIK, 4rd-U is better for this than double translation (say 4rd-T), =
and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E). =20
>> If you still believe this is not right, an explanation will of course =
be welcome.
>>=20
>> Cheers,
>> RD
>>=20
>>=20
>>=20
>>=20
>>>=20
>>> cheers,
>>> --satoru
>>>=20
>>>=20
>>>>=20
>>>> cheers,
>>>> maoke
>>>>=20
>>>> cheers,
>>>> --satoru
>>>>=20
>>>>> regards,
>>>>> maoke
>>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>>> Hi Remi-san,
>>>>>=20
>>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>>>> It can make IMHO a valuable unified standard.
>>>>>=20
>>>>> Not enough. The original TTL value in IPv4 header must be carried.
>>>>>=20
>>>>> cheers,
>>>>> --satoru
>>>>>=20
>>>>>=20
>>>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>>>>>=20
>>>>>> Hi Satoru-san,
>>>>>>=20
>>>>>> Thank you for identifying a limitation of the 4rd-U
>>>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
>>>>>> All these need e2e transparency to the IPv4 Type of Service.
>>>>>>=20
>>>>>> Fortunately, this is easy to fix: in the Identification field of =
the IPv6 Fragment header, copy not only the DF bits but also the IPv4 =
TOS.
>>>>>>=20
>>>>>> The proposed 4r-U packet format becomes:
>>>>>>=20
>>>>>>=20
>>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>> |Vers=3D6 |   TrafClass   |            Flow Label                 =
|
>>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>> |         Payload Length        |Next Header=3D44 |   Hop Limit   =
|
>>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>> |                                                               |
>>>>>> +                                                               +
>>>>>> |                                                               |
>>>>>> +                  IPv6 Source Address                          +
>>>>>> |                                                               |
>>>>>> +                                                               +
>>>>>> |                                                               |
>>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>> |                                                               |
>>>>>> +                                                               +
>>>>>> |                                                               |
>>>>>> +                IPv6 Destination Address                       +
>>>>>> |                                                               |
>>>>>> +                                                               +
>>>>>> |                                                               |
>>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>> |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
>>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>> |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
>>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>> |                        IPv4 Payload                           |
>>>>>> |                                                               |
>>>>>>=20
>>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>>>> It can make IMHO a valuable unified standard.
>>>>>>=20
>>>>>> Yet, I may have missed something else.
>>>>>> New justified objections are therefore most welcome..
>>>>>>=20
>>>>>>=20
>>>>>> Regards,
>>>>>> RD
>>>>>=20
>>>>> _______________________________________________
>>>>> Softwires mailing list
>>>>> Softwires@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/softwires
>>>>>=20
>>>>=20
>>>>=20
>>>=20
>>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20

From sarikaya2012@gmail.com  Mon Oct 17 09:41:14 2011
Return-Path: <sarikaya2012@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 C37AF21F8BDE for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.961
X-Spam-Level: 
X-Spam-Status: No, score=-2.961 tagged_above=-999 required=5 tests=[AWL=0.337,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YHcf8o+c6bnu for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:41:13 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 184EA21F8BDC for <softwires@ietf.org>; Mon, 17 Oct 2011 09:41:13 -0700 (PDT)
Received: by ggnv1 with SMTP id v1so1718202ggn.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 09:41:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=gZr29Zo5LFAEvutU72bT1wisBA5t7MEF6m9boSnvkRg=; b=epTJi/xqGV++HdZf2D8w+2e1UOYpJBkdeWnUfNoQleOzUVUR5PstI0Zd8DwFB/yfgc h2bG0oCVjXR4iy6QvMf5yMjxPIh3VIQLz2rLXEVZeW96gwIhlYpPqOEri+urQJle5jCM OfGqnvx6CZn9GmlpfbdtmY2pC2U0wG8NBAae8=
MIME-Version: 1.0
Received: by 10.236.103.102 with SMTP id e66mr28503460yhg.1.1318869672163; Mon, 17 Oct 2011 09:41:12 -0700 (PDT)
Received: by 10.236.110.39 with HTTP; Mon, 17 Oct 2011 09:41:12 -0700 (PDT)
In-Reply-To: <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net>
Date: Mon, 17 Oct 2011 11:41:12 -0500
Message-ID: <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=20cf303a2fc3507a4404af814657
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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, 17 Oct 2011 16:41:14 -0000

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

the idea of 4rd-U is to map IPv4 headers into IPv6 headers

address translation is called address derivation.

Isn't this translation?

regards,

Behcet

On Mon, Oct 17, 2011 at 11:26 AM, R=E9mi Despr=E9s <despres.remi@laposte.ne=
t>wrote:

>
> Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :
>
> > Remi,
> >
> > how is 4rd-U different from translation?
>
> Functionally, full network transparency to DF bit (and TOS with the
> complement that was missing).
> Technically, see for instance Figure 1 of the draft.
>
> Cheers,
> RD
>
>
> >
> > cheers,
> > Ole
> >
> >
> > On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:
> >
> >>
> >> Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :
> >>
> >>> On 2011/10/17, at 23:46, Maoke wrote:
> >>>
> >>>> hi Satoru-san,
> >>>>
> >>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
> >>>> Hi Maoke-san,
> >>>>
> >>>> On 2011/10/17, at 22:30, Maoke wrote:
> >>>>
> >>>>> hi Satoru-san,
> >>>>>
> >>>>> may i understand that, as Remi's proposal is applied for the double
> translation case, TTL being translated to IPv6 Hop Limit is enough? as is
> stated in RFC6145, translator is a "router" and therefore the behavior
> should not be as same as the virtual link. right?
> >>>>
> >>>> If so, just double translation is enough for that.
> >>>>
> >>>> it sounds nice. what i would like to have is a consistent header
> processing for single/double translations and encapsulation.
> >>>
> >>> I think that encapsulation and double translation can't be consistent
> to processing packet at all.
> >>
> >> 4rd-u (duly completed with TOS transparency) is neither Double RFC6145
> translation nor Encapsulation.
> >> It is believed to have advantages over both of them.
> >> Disadvantages has AFAIK still to be identified.
> >>
> >>
> >>>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment header
> but not anything more unless really necessary)?
> >>>>
> >>>> can i understand that the following requirements are exclusive to ea=
ch
> other: (a) we want to keep TTL changed in the IPv6 domain as the behavior=
 of
> translation; (b) we want to keep TTL not changed until leaving the IPv6
> domain as the behavior of encapsulation (4rd-U)?
> >>>
> >>> I think that these are exclusive.
> >>
> >> Indeed, one cant't do both simultaneously, but AFAIK either choice is
> acceptable.
> >> Is there one you prefer, for which reason?
> >>
> >>>> RFC6145 has defined TTL<->HopLimit translation. then how about using
> another reserved bit, say EF, in the fragment header for indicating the
> mode? if EF =3D 1, it is encapsulation mode, and therefore the HopLimit i=
n the
> base header keeps unchanged untile being translated back to IPv4; if EF =
=3D 0,
> it is translation mode, and the HopLimit in the base header will decrease=
 1
> for each hop. btw, previously i suggest using one of the reserved bits fo=
r
> the DF (e.g., the one before MF) instead of the first bit of the
> identification in the ipv6 fragement header, in order to avoid ambiguity
> caused by an IPv6 host in the single translation.
> >>>
> >>> It seems that adding new semantics more. Very creative, but is it
> really needed even we already have both encaps and translation? When you
> want to define more new semantics, it would be better you define new
> protocol number for 4rd-U.
> >>
> >> The idea is to avoid having two designs, each one with its own
> limitations, while a third design exists that has none of these limitatio=
ns.
> >>
> >> A key advantage of Double translation over Encapsulation, is that the
> IPv6 next header is the same as the Protocol of the conveyed IPv4 packet.
> Having a new protocol number would therefore defeat the objective of havi=
ng
> advantages of both Double translation and encapsulations.
> >>
> >>>> thus i'd like to suggest that one as follows, based on Remi's
> complement, where E is the indicator of encapsulation mode. copying TOS i=
n
> the fragment header is fine because it doesn't impact the IPv6 dst (of
> single translation) getting the original IPv4 src's relative identificati=
on.
> >>>>
> >>>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+
> >>>>     |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
> >>>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+
> >>>>     |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
> >>>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+
> >>>>     |                                                               =
|
> >>>>     +                                                               =
+
> >>>>     |                                                               =
|
> >>>>     +                  IPv6 Source Address                          =
+
> >>>>     |                                                               =
|
> >>>>     +                                                               =
+
> >>>>     |                                                               =
|
> >>>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+
> >>>>     |                                                               =
|
> >>>>     +                                                               =
+
> >>>>     |                                                               =
|
> >>>>     +                IPv6 Destination Address                       =
+
> >>>>     |                                                               =
|
> >>>>     +                                                               =
+
> >>>>     |                                                               =
|
> >>>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+
> >>>>     |  Next Header  |   Reserved    | IPv6  Fragment Offset   |E|D|M=
|
> >>>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+
> >>>>     |      0        |     TOS       |       IPv4 Identification     =
|
> >>>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+
> >>>>     |                        IPv4 Payload                           =
|
> >>>>     |                                                               =
|
> >>>> unfortunately, however, even we free the first bit of IPv6
> identification in the fragment header, we cannot put the TTL here (before
> the TOS) because traversing different paths may cause inconsistant IPv6
> identification values in fragments of the same datagram and disable
> reassemble at the IPv6 dst (in the single translation mode).
> >>>>
> >>>> the problem of EF in fragment header is, it requires that the
> implementation process fragment header before descreasing the HopLimit. i=
s
> it feasible?
> >>>>
> >>>> how do you think?
> >>>
> >>> IMHO, I'm not sure it is good idea to change the semantics of the IPv=
6
> fragment. If a router receives 4rd-U packets, which router doesn't
> understand 4rd-U, processing these packets as fragmented packets could ca=
use
> problem that sounds buffer exhaust attack.
> >>
> >> I don't see that:
> >> - IPv6 routers are not concerned with fragmentation.
> >> - the 4rd-U endpoint doesn't need to keep anything in a reassembly
> buffer if a conveyed IPv4 packet is completely contained in a single IPv6
> packet.
> >>
> >>> And I also think that if we need to add new semantics even we can
> utilize IPv6 fragment, it would be better to define new protocol number f=
or
> 4rd-U.
> >>
> >> See above why a new protocol number wouldn't be workable.
> >>
> >>> However, I don't think that we need to request to define it, because
> existing encapsulation and translation can be utilized for each appropria=
te
> situation.
> >>
> >>
> >>
> >> The point isn't to prevent any ISP from deploy for its own use any
> design that works.
> >>
> >> Yet, having only ONE STANDARD for a given need is better than several.
> >> I hope you can agree with that.
> >> (In this case, the need is stateless support of residual IPv4 across
> IPv6-only networks.)
> >>
> >> AFAIK, 4rd-U is better for this than double translation (say 4rd-T), a=
nd
> better than encapsulation (say 4rd-E), because it combines advantages of
> both (applicability of IPv6 O&M tools (a feature of 4rd-T), AND e2e
> transparency to IPv4 semantics (a feature of 4rd-E).
> >> If you still believe this is not right, an explanation will of course =
be
> welcome.
> >>
> >> Cheers,
> >> RD
> >>
> >>
> >>
> >>
> >>>
> >>> cheers,
> >>> --satoru
> >>>
> >>>
> >>>>
> >>>> cheers,
> >>>> maoke
> >>>>
> >>>> cheers,
> >>>> --satoru
> >>>>
> >>>>> regards,
> >>>>> maoke
> >>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
> >>>>> Hi Remi-san,
> >>>>>
> >>>>>> With this added, I believe that 4rd-U is a real progress over
> previously proposed Double translation and Encapsulation.
> >>>>>> It can make IMHO a valuable unified standard.
> >>>>>
> >>>>> Not enough. The original TTL value in IPv4 header must be carried.
> >>>>>
> >>>>> cheers,
> >>>>> --satoru
> >>>>>
> >>>>>
> >>>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
> >>>>>
> >>>>>> Hi Satoru-san,
> >>>>>>
> >>>>>> Thank you for identifying a limitation of the 4rd-U
> >>>>>> You are right, as currently specified, "it doesn't support diff-se=
rv
> tunneling model, pipe and short-pipe".
> >>>>>> All these need e2e transparency to the IPv4 Type of Service.
> >>>>>>
> >>>>>> Fortunately, this is easy to fix: in the Identification field of t=
he
> IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
> >>>>>>
> >>>>>> The proposed 4r-U packet format becomes:
> >>>>>>
> >>>>>>
> >>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |Vers=3D6 |   TrafClass   |            Flow Label                 =
|
> >>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |         Payload Length        |Next Header=3D44 |   Hop Limit   =
|
> >>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |                                                               |
> >>>>>> +                                                               +
> >>>>>> |                                                               |
> >>>>>> +                  IPv6 Source Address                          +
> >>>>>> |                                                               |
> >>>>>> +                                                               +
> >>>>>> |                                                               |
> >>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |                                                               |
> >>>>>> +                                                               +
> >>>>>> |                                                               |
> >>>>>> +                IPv6 Destination Address                       +
> >>>>>> |                                                               |
> >>>>>> +                                                               +
> >>>>>> |                                                               |
> >>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
> >>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
> >>>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |                        IPv4 Payload                           |
> >>>>>> |                                                               |
> >>>>>>
> >>>>>> With this added, I believe that 4rd-U is a real progress over
> previously proposed Double translation and Encapsulation.
> >>>>>> It can make IMHO a valuable unified standard.
> >>>>>>
> >>>>>> Yet, I may have missed something else.
> >>>>>> New justified objections are therefore most welcome..
> >>>>>>
> >>>>>>
> >>>>>> Regards,
> >>>>>> RD
> >>>>>
> >>>>> _______________________________________________
> >>>>> Softwires mailing list
> >>>>> Softwires@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/softwires
> >>>>>
> >>>>
> >>>>
> >>>
> >>
> >> _______________________________________________
> >> Softwires mailing list
> >> Softwires@ietf.org
> >> https://www.ietf.org/mailman/listinfo/softwires
> >
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

the idea of 4rd-U is to map IPv4 headers into IPv6 headers<br><br>address t=
ranslation is called address derivation.<br><br>Isn&#39;t this translation?=
<br><br>regards,<br><br>Behcet<br><br><div class=3D"gmail_quote">On Mon, Oc=
t 17, 2011 at 11:26 AM, R=E9mi Despr=E9s <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><br>
Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :<br>
<div class=3D"im"><br>
&gt; Remi,<br>
&gt;<br>
&gt; how is 4rd-U different from translation?<br>
<br>
</div>Functionally, full network transparency to DF bit (and TOS with the c=
omplement that was missing).<br>
Technically, see for instance Figure 1 of the draft.<br>
<br>
Cheers,<br>
<font color=3D"#888888">RD<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
&gt;<br>
&gt; cheers,<br>
&gt; Ole<br>
&gt;<br>
&gt;<br>
&gt; On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 2011/10/17, at 23:46, Maoke wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; hi Satoru-san,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 2011/10/17 Satoru Matsushima &lt;<a href=3D"mailto:satoru.=
matsushima@gmail.com">satoru.matsushima@gmail.com</a>&gt;<br>
&gt;&gt;&gt;&gt; Hi Maoke-san,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 2011/10/17, at 22:30, Maoke wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; hi Satoru-san,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; may i understand that, as Remi&#39;s proposal is appli=
ed for the double translation case, TTL being translated to IPv6 Hop Limit =
is enough? as is stated in RFC6145, translator is a &quot;router&quot; and =
therefore the behavior should not be as same as the virtual link. right?<br=
>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; If so, just double translation is enough for that.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; it sounds nice. what i would like to have is a consistent =
header processing for single/double translations and encapsulation.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that encapsulation and double translation can&#39;t be=
 consistent to processing packet at all.<br>
&gt;&gt;<br>
&gt;&gt; 4rd-u (duly completed with TOS transparency) is neither Double RFC=
6145 translation nor Encapsulation.<br>
&gt;&gt; It is believed to have advantages over both of them.<br>
&gt;&gt; Disadvantages has AFAIK still to be identified.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; can we keep the TTL of IPv4 in the IPv6 header (plus fragm=
ent header but not anything more unless really necessary)?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; can i understand that the following requirements are exclu=
sive to each other: (a) we want to keep TTL changed in the IPv6 domain as t=
he behavior of translation; (b) we want to keep TTL not changed until leavi=
ng the IPv6 domain as the behavior of encapsulation (4rd-U)?<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that these are exclusive.<br>
&gt;&gt;<br>
&gt;&gt; Indeed, one cant&#39;t do both simultaneously, but AFAIK either ch=
oice is acceptable.<br>
&gt;&gt; Is there one you prefer, for which reason?<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; RFC6145 has defined TTL&lt;-&gt;HopLimit translation. then=
 how about using another reserved bit, say EF, in the fragment header for i=
ndicating the mode? if EF =3D 1, it is encapsulation mode, and therefore th=
e HopLimit in the base header keeps unchanged untile being translated back =
to IPv4; if EF =3D 0, it is translation mode, and the HopLimit in the base =
header will decrease 1 for each hop. btw, previously i suggest using one of=
 the reserved bits for the DF (e.g., the one before MF) instead of the firs=
t bit of the identification in the ipv6 fragement header, in order to avoid=
 ambiguity caused by an IPv6 host in the single translation.<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; It seems that adding new semantics more. Very creative, but is=
 it really needed even we already have both encaps and translation? When yo=
u want to define more new semantics, it would be better you define new prot=
ocol number for 4rd-U.<br>

&gt;&gt;<br>
&gt;&gt; The idea is to avoid having two designs, each one with its own lim=
itations, while a third design exists that has none of these limitations.<b=
r>
&gt;&gt;<br>
&gt;&gt; A key advantage of Double translation over Encapsulation, is that =
the IPv6 next header is the same as the Protocol of the conveyed IPv4 packe=
t. Having a new protocol number would therefore defeat the objective of hav=
ing advantages of both Double translation and encapsulations.<br>

&gt;&gt;<br>
&gt;&gt;&gt;&gt; thus i&#39;d like to suggest that one as follows, based on=
 Remi&#39;s complement, where E is the indicator of encapsulation mode. cop=
ying TOS in the fragment header is fine because it doesn&#39;t impact the I=
Pv6 dst (of single translation) getting the original IPv4 src&#39;s relativ=
e identification.<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; =A0 =A0 |Vers=3D6 | =A0 TrafClass =A0 | =A0 =A0 =A0 =A0 =
=A0 =A0Flow Label =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 Payload Length =A0 =A0 =A0 =A0|N=
ext Header=3D44 | =A0 Hop Limit =A0 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv6 Source A=
ddress =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0+<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv6 Destination =
Address =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0Next Header =A0| =A0 Reserved =A0 =A0| IPv6 =
=A0Fragment Offset =A0 |E|D|M|<br>
&gt;&gt;&gt;&gt; =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A00 =A0 =A0 =A0 =A0| =A0 =A0 TOS =A0 =
=A0 =A0 | =A0 =A0 =A0 IPv4 Identification =A0 =A0 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0I=
Pv4 Payload =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt;&gt;&gt;&gt; =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt; unfortunately, however, even we free the first bit of IPv6=
 identification in the fragment header, we cannot put the TTL here (before =
the TOS) because traversing different paths may cause inconsistant IPv6 ide=
ntification values in fragments of the same datagram and disable reassemble=
 at the IPv6 dst (in the single translation mode).<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; the problem of EF in fragment header is, it requires that =
the implementation process fragment header before descreasing the HopLimit.=
 is it feasible?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; how do you think?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; IMHO, I&#39;m not sure it is good idea to change the semantics=
 of the IPv6 fragment. If a router receives 4rd-U packets, which router doe=
sn&#39;t understand 4rd-U, processing these packets as fragmented packets c=
ould cause problem that sounds buffer exhaust attack.<br>

&gt;&gt;<br>
&gt;&gt; I don&#39;t see that:<br>
&gt;&gt; - IPv6 routers are not concerned with fragmentation.<br>
&gt;&gt; - the 4rd-U endpoint doesn&#39;t need to keep anything in a reasse=
mbly buffer if a conveyed IPv4 packet is completely contained in a single I=
Pv6 packet.<br>
&gt;&gt;<br>
&gt;&gt;&gt; And I also think that if we need to add new semantics even we =
can utilize IPv6 fragment, it would be better to define new protocol number=
 for 4rd-U.<br>
&gt;&gt;<br>
&gt;&gt; See above why a new protocol number wouldn&#39;t be workable.<br>
&gt;&gt;<br>
&gt;&gt;&gt; However, I don&#39;t think that we need to request to define i=
t, because existing encapsulation and translation can be utilized for each =
appropriate situation.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The point isn&#39;t to prevent any ISP from deploy for its own use=
 any design that works.<br>
&gt;&gt;<br>
&gt;&gt; Yet, having only ONE STANDARD for a given need is better than seve=
ral.<br>
&gt;&gt; I hope you can agree with that.<br>
&gt;&gt; (In this case, the need is stateless support of residual IPv4 acro=
ss IPv6-only networks.)<br>
&gt;&gt;<br>
&gt;&gt; AFAIK, 4rd-U is better for this than double translation (say 4rd-T=
), and better than encapsulation (say 4rd-E), because it combines advantage=
s of both (applicability of IPv6 O&amp;M tools (a feature of 4rd-T), AND e2=
e transparency to IPv4 semantics (a feature of 4rd-E).<br>

&gt;&gt; If you still believe this is not right, an explanation will of cou=
rse be welcome.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; RD<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt; maoke<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; regards,<br>
&gt;&gt;&gt;&gt;&gt; maoke<br>
&gt;&gt;&gt;&gt;&gt; 2011/10/17 Satoru Matsushima &lt;<a href=3D"mailto:sat=
oru.matsushima@gmail.com">satoru.matsushima@gmail.com</a>&gt;<br>
&gt;&gt;&gt;&gt;&gt; Hi Remi-san,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; With this added, I believe that 4rd-U is a real pr=
ogress over previously proposed Double translation and Encapsulation.<br>
&gt;&gt;&gt;&gt;&gt;&gt; It can make IMHO a valuable unified standard.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Not enough. The original TTL value in IPv4 header must=
 be carried.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Satoru-san,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thank you for identifying a limitation of the 4rd-=
U<br>
&gt;&gt;&gt;&gt;&gt;&gt; You are right, as currently specified, &quot;it do=
esn&#39;t support diff-serv tunneling model, pipe and short-pipe&quot;.<br>
&gt;&gt;&gt;&gt;&gt;&gt; All these need e2e transparency to the IPv4 Type o=
f Service.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Fortunately, this is easy to fix: in the Identific=
ation field of the IPv6 Fragment header, copy not only the DF bits but also=
 the IPv4 TOS.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; The proposed 4r-U packet format becomes:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; |Vers=3D6 | =A0 TrafClass =A0 | =A0 =A0 =A0 =A0 =
=A0 =A0Flow Label =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 Payload Length =A0 =A0 =A0 =A0|N=
ext Header=3D44 | =A0 Hop Limit =A0 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv6 Source A=
ddress =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPv6 Destination =
Address =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0Next Header =A0| =A0 =A0Reserved =A0 | IPv6 =
=A0Fragment Offset =A0 | 0 |M|<br>
&gt;&gt;&gt;&gt;&gt;&gt; +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; |D| =A0 =A0 =A00 =A0 =A0 =A0| =A0 =A0IPv4 TOS =A0 =
| =A0 =A0 =A0 IPv4 Identification =A0 =A0 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0I=
Pv4 Payload =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt;&gt;&gt;&gt;&gt;&gt; | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 |<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; With this added, I believe that 4rd-U is a real pr=
ogress over previously proposed Double translation and Encapsulation.<br>
&gt;&gt;&gt;&gt;&gt;&gt; It can make IMHO a valuable unified standard.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Yet, I may have missed something else.<br>
&gt;&gt;&gt;&gt;&gt;&gt; New justified objections are therefore most welcom=
e..<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Regards,<br>
&gt;&gt;&gt;&gt;&gt;&gt; RD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt;&gt; Softwires mailing list<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.o=
rg</a><br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softw=
ires" target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a>=
<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Softwires mailing list<br>
&gt;&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;<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>
</div></div></blockquote></div><br>

--20cf303a2fc3507a4404af814657--

From ichiroumakino@gmail.com  Mon Oct 17 09:54:35 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 3C1BA21F8C64 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:54:35 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yu76rG96G6oC for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 09:54:34 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id D040B21F8C63 for <softwires@ietf.org>; Mon, 17 Oct 2011 09:54:33 -0700 (PDT)
Received: by eyg24 with SMTP id 24so3322649eyg.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 09:54:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=zu9oqehsL3/l04OnXkfwftextIK6F0e6F663a9CgGic=; b=SWc9aHMRk8fSPZMr08YhPRYzcAHD2Ql/uDrCESXGiy7fFJ7j0eWI3Z74Ecnwe/0RcJ MZeIFgaTF7u1o4SYTTt1S0Zaz13s4RhTw36C28CH5n9hTRNP9BfjO9N9Vr1MbDLoJRgy Owa5YheB5bOtCgwEuRVJczFbU5AHQwvxrPoNA=
Received: by 10.14.22.143 with SMTP id t15mr1387400eet.43.1318870472878; Mon, 17 Oct 2011 09:54:32 -0700 (PDT)
Received: from gomlefisk.lan (141.84-48-218.nextgentel.com. [84.48.218.141]) by mx.google.com with ESMTPS id 49sm9594025eec.1.2011.10.17.09.54.31 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Oct 2011 09:54:32 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Ole Troan <otroan@employees.org>
In-Reply-To: <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net>
Date: Mon, 17 Oct 2011 18:54:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <542B93F7-F8E1-4E2B-BEB9-CF8196BAAB45@employees.org>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 16:54:35 -0000

Remi,

>> how is 4rd-U different from translation?
>=20
> Functionally, full network transparency to DF bit (and TOS with the =
complement that was missing).
> Technically, see for instance Figure 1 of the draft.

I thought the dIVI guys presented the DF bit transparency during the =
Beijing meeting?
I don't understand what the difference between "IP data" and Transport =
is in figure 1.
consider me slow, but don't you still either have to update the =
transport checksum, or adjust the checksum with other changes in the =
IPv6 header, e.g. flow.

cheers,
Ole


>>>> On 2011/10/17, at 23:46, Maoke wrote:
>>>>=20
>>>>> hi Satoru-san,
>>>>>=20
>>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>>> Hi Maoke-san,
>>>>>=20
>>>>> On 2011/10/17, at 22:30, Maoke wrote:
>>>>>=20
>>>>>> hi Satoru-san,
>>>>>>=20
>>>>>> may i understand that, as Remi's proposal is applied for the =
double translation case, TTL being translated to IPv6 Hop Limit is =
enough? as is stated in RFC6145, translator is a "router" and therefore =
the behavior should not be as same as the virtual link. right?
>>>>>=20
>>>>> If so, just double translation is enough for that.
>>>>>=20
>>>>> it sounds nice. what i would like to have is a consistent header =
processing for single/double translations and encapsulation.
>>>>=20
>>>> I think that encapsulation and double translation can't be =
consistent to processing packet at all.
>>>=20
>>> 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.
>>> It is believed to have advantages over both of them.
>>> Disadvantages has AFAIK still to be identified.
>>>=20
>>>=20
>>>>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment =
header but not anything more unless really necessary)?
>>>>>=20
>>>>> can i understand that the following requirements are exclusive to =
each other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?=20
>>>>=20
>>>> I think that these are exclusive.
>>>=20
>>> Indeed, one cant't do both simultaneously, but AFAIK either choice =
is acceptable.=20
>>> Is there one you prefer, for which reason?
>>>=20
>>>>> RFC6145 has defined TTL<->HopLimit translation. then how about =
using another reserved bit, say EF, in the fragment header for =
indicating the mode? if EF =3D 1, it is encapsulation mode, and =
therefore the HopLimit in the base header keeps unchanged untile being =
translated back to IPv4; if EF =3D 0, it is translation mode, and the =
HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.
>>>>=20
>>>> It seems that adding new semantics more. Very creative, but is it =
really needed even we already have both encaps and translation? When you =
want to define more new semantics, it would be better you define new =
protocol number for 4rd-U.
>>>=20
>>> The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.
>>>=20
>>> A key advantage of Double translation over Encapsulation, is that =
the IPv6 next header is the same as the Protocol of the conveyed IPv4 =
packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.
>>>=20
>>>>> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
>>>>>=20
>>>>>    =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>    |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
>>>>>    =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>    |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
>>>>>    =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>    |                                                               =
|
>>>>>    +                                                               =
+
>>>>>    |                                                               =
|
>>>>>    +                  IPv6 Source Address                          =
+
>>>>>    |                                                               =
|
>>>>>    +                                                               =
+
>>>>>    |                                                               =
|
>>>>>    =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>    |                                                               =
|
>>>>>    +                                                               =
+
>>>>>    |                                                               =
|
>>>>>    +                IPv6 Destination Address                       =
+
>>>>>    |                                                               =
|
>>>>>    +                                                               =
+
>>>>>    |                                                               =
|
>>>>>    =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>    |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
>>>>>    =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>    |      0        |     TOS       |       IPv4 Identification     =
|
>>>>>    =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>    |                        IPv4 Payload                           =
|
>>>>>    |                                                               =
|
>>>>> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
>>>>>=20
>>>>> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
>>>>>=20
>>>>> how do you think?
>>>>=20
>>>> IMHO, I'm not sure it is good idea to change the semantics of the =
IPv6 fragment. If a router receives 4rd-U packets, which router doesn't =
understand 4rd-U, processing these packets as fragmented packets could =
cause problem that sounds buffer exhaust attack.
>>>=20
>>> I don't see that:
>>> - IPv6 routers are not concerned with fragmentation.
>>> - the 4rd-U endpoint doesn't need to keep anything in a reassembly =
buffer if a conveyed IPv4 packet is completely contained in a single =
IPv6 packet.
>>>=20
>>>> And I also think that if we need to add new semantics even we can =
utilize IPv6 fragment, it would be better to define new protocol number =
for 4rd-U.
>>>=20
>>> See above why a new protocol number wouldn't be workable.
>>>=20
>>>> However, I don't think that we need to request to define it, =
because existing encapsulation and translation can be utilized for each =
appropriate situation.
>>>=20
>>>=20
>>>=20
>>> The point isn't to prevent any ISP from deploy for its own use any =
design that works.
>>>=20
>>> Yet, having only ONE STANDARD for a given need is better than =
several.=20
>>> I hope you can agree with that.
>>> (In this case, the need is stateless support of residual IPv4 across =
IPv6-only networks.)
>>>=20
>>> AFAIK, 4rd-U is better for this than double translation (say 4rd-T), =
and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E). =20
>>> If you still believe this is not right, an explanation will of =
course be welcome.
>>>=20
>>> Cheers,
>>> RD
>>>=20
>>>=20
>>>=20
>>>=20
>>>>=20
>>>> cheers,
>>>> --satoru
>>>>=20
>>>>=20
>>>>>=20
>>>>> cheers,
>>>>> maoke
>>>>>=20
>>>>> cheers,
>>>>> --satoru
>>>>>=20
>>>>>> regards,
>>>>>> maoke
>>>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>>>> Hi Remi-san,
>>>>>>=20
>>>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>>>>> It can make IMHO a valuable unified standard.
>>>>>>=20
>>>>>> Not enough. The original TTL value in IPv4 header must be =
carried.
>>>>>>=20
>>>>>> cheers,
>>>>>> --satoru
>>>>>>=20
>>>>>>=20
>>>>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>>>>>>=20
>>>>>>> Hi Satoru-san,
>>>>>>>=20
>>>>>>> Thank you for identifying a limitation of the 4rd-U
>>>>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
>>>>>>> All these need e2e transparency to the IPv4 Type of Service.
>>>>>>>=20
>>>>>>> Fortunately, this is easy to fix: in the Identification field of =
the IPv6 Fragment header, copy not only the DF bits but also the IPv4 =
TOS.
>>>>>>>=20
>>>>>>> The proposed 4r-U packet format becomes:
>>>>>>>=20
>>>>>>>=20
>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>> |Vers=3D6 |   TrafClass   |            Flow Label                =
 |
>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>> |         Payload Length        |Next Header=3D44 |   Hop Limit  =
 |
>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>> |                                                               =
|
>>>>>>> +                                                               =
+
>>>>>>> |                                                               =
|
>>>>>>> +                  IPv6 Source Address                          =
+
>>>>>>> |                                                               =
|
>>>>>>> +                                                               =
+
>>>>>>> |                                                               =
|
>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>> |                                                               =
|
>>>>>>> +                                                               =
+
>>>>>>> |                                                               =
|
>>>>>>> +                IPv6 Destination Address                       =
+
>>>>>>> |                                                               =
|
>>>>>>> +                                                               =
+
>>>>>>> |                                                               =
|
>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>> |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 =
|M|
>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>> |D|      0      |    IPv4 TOS   |       IPv4 Identification     =
|
>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>> |                        IPv4 Payload                           =
|
>>>>>>> |                                                               =
|
>>>>>>>=20
>>>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>>>>> It can make IMHO a valuable unified standard.
>>>>>>>=20
>>>>>>> Yet, I may have missed something else.
>>>>>>> New justified objections are therefore most welcome..
>>>>>>>=20
>>>>>>>=20
>>>>>>> Regards,
>>>>>>> RD
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> Softwires mailing list
>>>>>> Softwires@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/softwires
>>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>=20


From despres.remi@laposte.net  Mon Oct 17 10:11:06 2011
Return-Path: <despres.remi@laposte.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 3824B21F8772 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 10:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.681
X-Spam-Level: 
X-Spam-Status: No, score=-1.681 tagged_above=-999 required=5 tests=[AWL=0.267,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F3zClJt3pSTd for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 10:11:04 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by ietfa.amsl.com (Postfix) with ESMTP id 5227421F8B36 for <softwires@ietf.org>; Mon, 17 Oct 2011 10:11:03 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 830C6700015A; Mon, 17 Oct 2011 19:11:02 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id D4B0E7000045; Mon, 17 Oct 2011 19:10:59 +0200 (CEST)
X-SFR-UUID: 20111017171101871.D4B0E7000045@msfrf2108.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-4--885640845
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com>
Date: Mon, 17 Oct 2011 19:10:59 +0200
Message-Id: <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com>
To: sarikaya@ieee.org
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 17:11:06 -0000

--Apple-Mail-4--885640845
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi Behcet,

4rd-U translates addresses, but:
- isn't concerned with anything above the IP layer;
- has a way to convey fields of IPv4 that would be lost in IPv6 (DF and, =
for "pipe and short pipe" as discussed by Satoru-san, the TOS).=20
4rd-T translates addresses, AND:
- is concerned with the IPv4 payload (possible checksum adjustment)
- isn't fully transparent to DF, and to the TOS if a specific IPv6 =
Traffic class is needed for IPv6-domain traversal.

Hope it clarifies why, IMHO, calling 4rd-u a double-translation =
solution, like the RFC6145-based double translation, would create =
confusion.
If you look for a name, what about "header mapping"=20

Regards,
RD

 =20

Le 17 oct. 2011 =E0 18:41, Behcet Sarikaya a =E9crit :

> the idea of 4rd-U is to map IPv4 headers into IPv6 headers
>=20
> address translation is called address derivation.
>=20
> Isn't this translation?
>=20
> regards,
>=20
> Behcet
>=20
> On Mon, Oct 17, 2011 at 11:26 AM, R=E9mi Despr=E9s =
<despres.remi@laposte.net> wrote:
>=20
> Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :
>=20
> > Remi,
> >
> > how is 4rd-U different from translation?
>=20
> Functionally, full network transparency to DF bit (and TOS with the =
complement that was missing).
> Technically, see for instance Figure 1 of the draft.
>=20
> Cheers,
> RD
>=20
>=20
> >
> > cheers,
> > Ole
> >
> >
> > On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:
> >
> >>
> >> Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :
> >>
> >>> On 2011/10/17, at 23:46, Maoke wrote:
> >>>
> >>>> hi Satoru-san,
> >>>>
> >>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
> >>>> Hi Maoke-san,
> >>>>
> >>>> On 2011/10/17, at 22:30, Maoke wrote:
> >>>>
> >>>>> hi Satoru-san,
> >>>>>
> >>>>> may i understand that, as Remi's proposal is applied for the =
double translation case, TTL being translated to IPv6 Hop Limit is =
enough? as is stated in RFC6145, translator is a "router" and therefore =
the behavior should not be as same as the virtual link. right?
> >>>>
> >>>> If so, just double translation is enough for that.
> >>>>
> >>>> it sounds nice. what i would like to have is a consistent header =
processing for single/double translations and encapsulation.
> >>>
> >>> I think that encapsulation and double translation can't be =
consistent to processing packet at all.
> >>
> >> 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.
> >> It is believed to have advantages over both of them.
> >> Disadvantages has AFAIK still to be identified.
> >>
> >>
> >>>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment =
header but not anything more unless really necessary)?
> >>>>
> >>>> can i understand that the following requirements are exclusive to =
each other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?
> >>>
> >>> I think that these are exclusive.
> >>
> >> Indeed, one cant't do both simultaneously, but AFAIK either choice =
is acceptable.
> >> Is there one you prefer, for which reason?
> >>
> >>>> RFC6145 has defined TTL<->HopLimit translation. then how about =
using another reserved bit, say EF, in the fragment header for =
indicating the mode? if EF =3D 1, it is encapsulation mode, and =
therefore the HopLimit in the base header keeps unchanged untile being =
translated back to IPv4; if EF =3D 0, it is translation mode, and the =
HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.
> >>>
> >>> It seems that adding new semantics more. Very creative, but is it =
really needed even we already have both encaps and translation? When you =
want to define more new semantics, it would be better you define new =
protocol number for 4rd-U.
> >>
> >> The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.
> >>
> >> A key advantage of Double translation over Encapsulation, is that =
the IPv6 next header is the same as the Protocol of the conveyed IPv4 =
packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.
> >>
> >>>> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
> >>>>
> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>     |Vers=3D6 |   TrafClass   |            Flow Label             =
    |
> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>     |         Payload Length        |Next Header=3D44 |   Hop =
Limit   |
> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>     |                                                             =
  |
> >>>>     +                                                             =
  +
> >>>>     |                                                             =
  |
> >>>>     +                  IPv6 Source Address                        =
  +
> >>>>     |                                                             =
  |
> >>>>     +                                                             =
  +
> >>>>     |                                                             =
  |
> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>     |                                                             =
  |
> >>>>     +                                                             =
  +
> >>>>     |                                                             =
  |
> >>>>     +                IPv6 Destination Address                     =
  +
> >>>>     |                                                             =
  |
> >>>>     +                                                             =
  +
> >>>>     |                                                             =
  |
> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>     |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>     |      0        |     TOS       |       IPv4 Identification   =
  |
> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>     |                        IPv4 Payload                         =
  |
> >>>>     |                                                             =
  |
> >>>> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
> >>>>
> >>>> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
> >>>>
> >>>> how do you think?
> >>>
> >>> IMHO, I'm not sure it is good idea to change the semantics of the =
IPv6 fragment. If a router receives 4rd-U packets, which router doesn't =
understand 4rd-U, processing these packets as fragmented packets could =
cause problem that sounds buffer exhaust attack.
> >>
> >> I don't see that:
> >> - IPv6 routers are not concerned with fragmentation.
> >> - the 4rd-U endpoint doesn't need to keep anything in a reassembly =
buffer if a conveyed IPv4 packet is completely contained in a single =
IPv6 packet.
> >>
> >>> And I also think that if we need to add new semantics even we can =
utilize IPv6 fragment, it would be better to define new protocol number =
for 4rd-U.
> >>
> >> See above why a new protocol number wouldn't be workable.
> >>
> >>> However, I don't think that we need to request to define it, =
because existing encapsulation and translation can be utilized for each =
appropriate situation.
> >>
> >>
> >>
> >> The point isn't to prevent any ISP from deploy for its own use any =
design that works.
> >>
> >> Yet, having only ONE STANDARD for a given need is better than =
several.
> >> I hope you can agree with that.
> >> (In this case, the need is stateless support of residual IPv4 =
across IPv6-only networks.)
> >>
> >> AFAIK, 4rd-U is better for this than double translation (say =
4rd-T), and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E).
> >> If you still believe this is not right, an explanation will of =
course be welcome.
> >>
> >> Cheers,
> >> RD
> >>
> >>
> >>
> >>
> >>>
> >>> cheers,
> >>> --satoru
> >>>
> >>>
> >>>>
> >>>> cheers,
> >>>> maoke
> >>>>
> >>>> cheers,
> >>>> --satoru
> >>>>
> >>>>> regards,
> >>>>> maoke
> >>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
> >>>>> Hi Remi-san,
> >>>>>
> >>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> >>>>>> It can make IMHO a valuable unified standard.
> >>>>>
> >>>>> Not enough. The original TTL value in IPv4 header must be =
carried.
> >>>>>
> >>>>> cheers,
> >>>>> --satoru
> >>>>>
> >>>>>
> >>>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
> >>>>>
> >>>>>> Hi Satoru-san,
> >>>>>>
> >>>>>> Thank you for identifying a limitation of the 4rd-U
> >>>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
> >>>>>> All these need e2e transparency to the IPv4 Type of Service.
> >>>>>>
> >>>>>> Fortunately, this is easy to fix: in the Identification field =
of the IPv6 Fragment header, copy not only the DF bits but also the IPv4 =
TOS.
> >>>>>>
> >>>>>> The proposed 4r-U packet format becomes:
> >>>>>>
> >>>>>>
> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |                                                               =
|
> >>>>>> +                                                               =
+
> >>>>>> |                                                               =
|
> >>>>>> +                  IPv6 Source Address                          =
+
> >>>>>> |                                                               =
|
> >>>>>> +                                                               =
+
> >>>>>> |                                                               =
|
> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |                                                               =
|
> >>>>>> +                                                               =
+
> >>>>>> |                                                               =
|
> >>>>>> +                IPv6 Destination Address                       =
+
> >>>>>> |                                                               =
|
> >>>>>> +                                                               =
+
> >>>>>> |                                                               =
|
> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 =
|M|
> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |D|      0      |    IPv4 TOS   |       IPv4 Identification     =
|
> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>>> |                        IPv4 Payload                           =
|
> >>>>>> |                                                               =
|
> >>>>>>
> >>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> >>>>>> It can make IMHO a valuable unified standard.
> >>>>>>
> >>>>>> Yet, I may have missed something else.
> >>>>>> New justified objections are therefore most welcome..
> >>>>>>
> >>>>>>
> >>>>>> Regards,
> >>>>>> RD
> >>>>>
> >>>>> _______________________________________________
> >>>>> Softwires mailing list
> >>>>> Softwires@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/softwires
> >>>>>
> >>>>
> >>>>
> >>>
> >>
> >> _______________________________________________
> >> Softwires mailing list
> >> Softwires@ietf.org
> >> https://www.ietf.org/mailman/listinfo/softwires
> >
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>=20


--Apple-Mail-4--885640845
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Behcet,<div><br></div><div>4rd-U translates addresses, but:<div>- isn't =
concerned with anything above the IP layer;</div><div>- has a way to =
convey fields of IPv4 that would be lost in IPv6 (DF and, for "pipe and =
short pipe" as discussed by Satoru-san, the =
TOS).&nbsp;</div><div><div>4rd-T translates addresses, AND:</div><div>- =
is concerned with the IPv4 payload (possible checksum =
adjustment)</div><div>- isn't fully transparent to DF, and to the TOS if =
a specific IPv6 Traffic class is needed for IPv6-domain =
traversal.</div><div><br></div><div>Hope it clarifies why, IMHO, calling =
4rd-u a double-translation solution, like the RFC6145-based double =
translation, would create confusion.</div><div>If you look for a name, =
what about "header =
mapping"&nbsp;</div><div><br></div><div>Regards,</div><div>RD</div><div><b=
r></div><div>&nbsp;&nbsp;</div><div><br><div><div>Le 17 oct. 2011 =E0 =
18:41, Behcet Sarikaya a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">the idea =
of 4rd-U is to map IPv4 headers into IPv6 headers<br><br>address =
translation is called address derivation.<br><br>Isn't this =
translation?<br><br>regards,<br><br>Behcet<br><br><div =
class=3D"gmail_quote">On Mon, Oct 17, 2011 at 11:26 AM, R=E9mi Despr=E9s =
<span dir=3D"ltr">&lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :<br>
<div class=3D"im"><br>
&gt; Remi,<br>
&gt;<br>
&gt; how is 4rd-U different from translation?<br>
<br>
</div>Functionally, full network transparency to DF bit (and TOS with =
the complement that was missing).<br>
Technically, see for instance Figure 1 of the draft.<br>
<br>
Cheers,<br>
<font color=3D"#888888">RD<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
&gt;<br>
&gt; cheers,<br>
&gt; Ole<br>
&gt;<br>
&gt;<br>
&gt; On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 2011/10/17, at 23:46, Maoke wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; hi Satoru-san,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 2011/10/17 Satoru Matsushima &lt;<a =
href=3D"mailto:satoru.matsushima@gmail.com">satoru.matsushima@gmail.com</a=
>&gt;<br>
&gt;&gt;&gt;&gt; Hi Maoke-san,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 2011/10/17, at 22:30, Maoke wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; hi Satoru-san,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; may i understand that, as Remi's proposal is =
applied for the double translation case, TTL being translated to IPv6 =
Hop Limit is enough? as is stated in RFC6145, translator is a "router" =
and therefore the behavior should not be as same as the virtual link. =
right?<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; If so, just double translation is enough for that.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; it sounds nice. what i would like to have is a =
consistent header processing for single/double translations and =
encapsulation.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that encapsulation and double translation can't be =
consistent to processing packet at all.<br>
&gt;&gt;<br>
&gt;&gt; 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.<br>
&gt;&gt; It is believed to have advantages over both of them.<br>
&gt;&gt; Disadvantages has AFAIK still to be identified.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; can we keep the TTL of IPv4 in the IPv6 header (plus =
fragment header but not anything more unless really necessary)?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; can i understand that the following requirements are =
exclusive to each other: (a) we want to keep TTL changed in the IPv6 =
domain as the behavior of translation; (b) we want to keep TTL not =
changed until leaving the IPv6 domain as the behavior of encapsulation =
(4rd-U)?<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that these are exclusive.<br>
&gt;&gt;<br>
&gt;&gt; Indeed, one cant't do both simultaneously, but AFAIK either =
choice is acceptable.<br>
&gt;&gt; Is there one you prefer, for which reason?<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; RFC6145 has defined TTL&lt;-&gt;HopLimit translation. =
then how about using another reserved bit, say EF, in the fragment =
header for indicating the mode? if EF =3D 1, it is encapsulation mode, =
and therefore the HopLimit in the base header keeps unchanged untile =
being translated back to IPv4; if EF =3D 0, it is translation mode, and =
the HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; It seems that adding new semantics more. Very creative, but =
is it really needed even we already have both encaps and translation? =
When you want to define more new semantics, it would be better you =
define new protocol number for 4rd-U.<br>

&gt;&gt;<br>
&gt;&gt; The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.<br>
&gt;&gt;<br>
&gt;&gt; A key advantage of Double translation over Encapsulation, is =
that the IPv6 next header is the same as the Protocol of the conveyed =
IPv4 packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.<br>

&gt;&gt;<br>
&gt;&gt;&gt;&gt; thus i'd like to suggest that one as follows, based on =
Remi's complement, where E is the indicator of encapsulation mode. =
copying TOS in the fragment header is fine because it doesn't impact the =
IPv6 dst (of single translation) getting the original IPv4 src's =
relative identification.<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; |Vers=3D6 | &nbsp; TrafClass &nbsp; | =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Flow Label &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; Payload =
Length &nbsp; &nbsp; &nbsp; &nbsp;|Next Header=3D44 | &nbsp; Hop Limit =
&nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;IPv6 Source Address &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;IPv6 Destination Address &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp;Next Header &nbsp;| &nbsp; =
Reserved &nbsp; &nbsp;| IPv6 &nbsp;Fragment Offset &nbsp; |E|D|M|<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp; =
&nbsp; &nbsp;| &nbsp; &nbsp; TOS &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; =
&nbsp; IPv4 Identification &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IPv4 Payload &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; unfortunately, however, even we free the first bit of =
IPv6 identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; the problem of EF in fragment header is, it requires =
that the implementation process fragment header before descreasing the =
HopLimit. is it feasible?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; how do you think?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; IMHO, I'm not sure it is good idea to change the semantics =
of the IPv6 fragment. If a router receives 4rd-U packets, which router =
doesn't understand 4rd-U, processing these packets as fragmented packets =
could cause problem that sounds buffer exhaust attack.<br>

&gt;&gt;<br>
&gt;&gt; I don't see that:<br>
&gt;&gt; - IPv6 routers are not concerned with fragmentation.<br>
&gt;&gt; - the 4rd-U endpoint doesn't need to keep anything in a =
reassembly buffer if a conveyed IPv4 packet is completely contained in a =
single IPv6 packet.<br>
&gt;&gt;<br>
&gt;&gt;&gt; And I also think that if we need to add new semantics even =
we can utilize IPv6 fragment, it would be better to define new protocol =
number for 4rd-U.<br>
&gt;&gt;<br>
&gt;&gt; See above why a new protocol number wouldn't be workable.<br>
&gt;&gt;<br>
&gt;&gt;&gt; However, I don't think that we need to request to define =
it, because existing encapsulation and translation can be utilized for =
each appropriate situation.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The point isn't to prevent any ISP from deploy for its own use =
any design that works.<br>
&gt;&gt;<br>
&gt;&gt; Yet, having only ONE STANDARD for a given need is better than =
several.<br>
&gt;&gt; I hope you can agree with that.<br>
&gt;&gt; (In this case, the need is stateless support of residual IPv4 =
across IPv6-only networks.)<br>
&gt;&gt;<br>
&gt;&gt; AFAIK, 4rd-U is better for this than double translation (say =
4rd-T), and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&amp;M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E).<br>

&gt;&gt; If you still believe this is not right, an explanation will of =
course be welcome.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; RD<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt; maoke<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; regards,<br>
&gt;&gt;&gt;&gt;&gt; maoke<br>
&gt;&gt;&gt;&gt;&gt; 2011/10/17 Satoru Matsushima &lt;<a =
href=3D"mailto:satoru.matsushima@gmail.com">satoru.matsushima@gmail.com</a=
>&gt;<br>
&gt;&gt;&gt;&gt;&gt; Hi Remi-san,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; With this added, I believe that 4rd-U is a real =
progress over previously proposed Double translation and =
Encapsulation.<br>
&gt;&gt;&gt;&gt;&gt;&gt; It can make IMHO a valuable unified =
standard.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Not enough. The original TTL value in IPv4 header =
must be carried.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On 2011/10/17, at 21:36, R=E9mi Despr=E9s =
wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Satoru-san,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thank you for identifying a limitation of the =
4rd-U<br>
&gt;&gt;&gt;&gt;&gt;&gt; You are right, as currently specified, "it =
doesn't support diff-serv tunneling model, pipe and short-pipe".<br>
&gt;&gt;&gt;&gt;&gt;&gt; All these need e2e transparency to the IPv4 =
Type of Service.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Fortunately, this is easy to fix: in the =
Identification field of the IPv6 Fragment header, copy not only the DF =
bits but also the IPv4 TOS.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; The proposed 4r-U packet format becomes:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; |Vers=3D6 | &nbsp; TrafClass &nbsp; | &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Flow Label &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; Payload Length =
&nbsp; &nbsp; &nbsp; &nbsp;|Next Header=3D44 | &nbsp; Hop Limit &nbsp; =
|<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;IPv6 Source Address &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;IPv6 Destination Address &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp;Next Header &nbsp;| &nbsp; =
&nbsp;Reserved &nbsp; | IPv6 &nbsp;Fragment Offset &nbsp; | 0 |M|<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; |D| &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp; &nbsp;| =
&nbsp; &nbsp;IPv4 TOS &nbsp; | &nbsp; &nbsp; &nbsp; IPv4 Identification =
&nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IPv4 Payload &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; With this added, I believe that 4rd-U is a real =
progress over previously proposed Double translation and =
Encapsulation.<br>
&gt;&gt;&gt;&gt;&gt;&gt; It can make IMHO a valuable unified =
standard.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Yet, I may have missed something else.<br>
&gt;&gt;&gt;&gt;&gt;&gt; New justified objections are therefore most =
welcome..<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Regards,<br>
&gt;&gt;&gt;&gt;&gt;&gt; RD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt;&gt; Softwires mailing list<br>
&gt;&gt;&gt;&gt;&gt; <a =
href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Softwires mailing list<br>
&gt;&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;<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"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</div></div></blockquote></div><br>
</blockquote></div><br></div></div></div></body></html>=

--Apple-Mail-4--885640845--

From despres.remi@laposte.net  Mon Oct 17 10:25:45 2011
Return-Path: <despres.remi@laposte.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 EB79B21F8BBD for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 10:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.706
X-Spam-Level: 
X-Spam-Status: No, score=-1.706 tagged_above=-999 required=5 tests=[AWL=0.243,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lz24s+N5JCKi for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 10:25:45 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE5521F8B2A for <softwires@ietf.org>; Mon, 17 Oct 2011 10:25:43 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 9BCB67000105; Mon, 17 Oct 2011 19:25:42 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 3A6757000045; Mon, 17 Oct 2011 19:25:42 +0200 (CEST)
X-SFR-UUID: 20111017172542239.3A6757000045@msfrf2108.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <542B93F7-F8E1-4E2B-BEB9-CF8196BAAB45@employees.org>
Date: Mon, 17 Oct 2011 19:25:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0590740-D4FC-4BF7-8AD6-BB77E2668479@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <542B93F7-F8E1-4E2B-BEB9-CF8196BAAB45@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 17:25:46 -0000

Le 17 oct. 2011 =E0 18:54, Ole Troan a =E9crit :

> Remi,
>=20
>>> how is 4rd-U different from translation?
>>=20
>> Functionally, full network transparency to DF bit (and TOS with the =
complement that was missing).
>> Technically, see for instance Figure 1 of the draft.
>=20
> I thought the dIVI guys presented the DF bit transparency during the =
Beijing meeting?

They did, but AFAIK not as completely as section 1 of my draft.


> I don't understand what the difference between "IP data" and Transport =
is in figure 1.

IP data is, as shown in my Figure 1, everything after the IPv4 header:
             +----------------+  =20
             |   IPv4 Header  |   =20
             +----------------+        =20
             |    IP Data     |        =20
             +----------------+         =20

Transport header is as in Figure 2 of RFC 6145:

              +-------------+                 +-------------+
              |    IPv4     |                 |    IPv6     |
              |   Header    |                 |   Header    |
              +-------------+                 +-------------+
              |  Transport- |                 |  Fragment   |
              |   Layer     |      =3D=3D=3D>       |   Header    |
              |   Header    |                 | (if needed) |
              +-------------+                 +-------------+
              |             |                 |  Transport- |
              ~    Data     ~                 |   Layer     |
              |             |                 |   Header    |
              +-------------+                 +-------------+
                                              |             |
                                              ~    Data     ~
                                              |             |
                                              +-------------+            =
                               =20

May I suggest that you re-read RFC 6145, and thus understand all what =
becomes unnecessary with 4rd-U :-).


> consider me slow, but don't you still either have to update the =
transport checksum, or adjust the checksum with other changes in the =
IPv6 header, e.g. flow.

None of this is needed (this is where 4rd-U has in common with =
4rd-Encap).

Cheers,
RD





>=20
> cheers,
> Ole
>=20
>=20
>>>>> On 2011/10/17, at 23:46, Maoke wrote:
>>>>>=20
>>>>>> hi Satoru-san,
>>>>>>=20
>>>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>>>> Hi Maoke-san,
>>>>>>=20
>>>>>> On 2011/10/17, at 22:30, Maoke wrote:
>>>>>>=20
>>>>>>> hi Satoru-san,
>>>>>>>=20
>>>>>>> may i understand that, as Remi's proposal is applied for the =
double translation case, TTL being translated to IPv6 Hop Limit is =
enough? as is stated in RFC6145, translator is a "router" and therefore =
the behavior should not be as same as the virtual link. right?
>>>>>>=20
>>>>>> If so, just double translation is enough for that.
>>>>>>=20
>>>>>> it sounds nice. what i would like to have is a consistent header =
processing for single/double translations and encapsulation.
>>>>>=20
>>>>> I think that encapsulation and double translation can't be =
consistent to processing packet at all.
>>>>=20
>>>> 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.
>>>> It is believed to have advantages over both of them.
>>>> Disadvantages has AFAIK still to be identified.
>>>>=20
>>>>=20
>>>>>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment =
header but not anything more unless really necessary)?
>>>>>>=20
>>>>>> can i understand that the following requirements are exclusive to =
each other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?=20
>>>>>=20
>>>>> I think that these are exclusive.
>>>>=20
>>>> Indeed, one cant't do both simultaneously, but AFAIK either choice =
is acceptable.=20
>>>> Is there one you prefer, for which reason?
>>>>=20
>>>>>> RFC6145 has defined TTL<->HopLimit translation. then how about =
using another reserved bit, say EF, in the fragment header for =
indicating the mode? if EF =3D 1, it is encapsulation mode, and =
therefore the HopLimit in the base header keeps unchanged untile being =
translated back to IPv4; if EF =3D 0, it is translation mode, and the =
HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.
>>>>>=20
>>>>> It seems that adding new semantics more. Very creative, but is it =
really needed even we already have both encaps and translation? When you =
want to define more new semantics, it would be better you define new =
protocol number for 4rd-U.
>>>>=20
>>>> The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.
>>>>=20
>>>> A key advantage of Double translation over Encapsulation, is that =
the IPv6 next header is the same as the Protocol of the conveyed IPv4 =
packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.
>>>>=20
>>>>>> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
>>>>>>=20
>>>>>>   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>   |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
>>>>>>   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>   |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
>>>>>>   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>   |                                                               =
|
>>>>>>   +                                                               =
+
>>>>>>   |                                                               =
|
>>>>>>   +                  IPv6 Source Address                          =
+
>>>>>>   |                                                               =
|
>>>>>>   +                                                               =
+
>>>>>>   |                                                               =
|
>>>>>>   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>   |                                                               =
|
>>>>>>   +                                                               =
+
>>>>>>   |                                                               =
|
>>>>>>   +                IPv6 Destination Address                       =
+
>>>>>>   |                                                               =
|
>>>>>>   +                                                               =
+
>>>>>>   |                                                               =
|
>>>>>>   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>   |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
>>>>>>   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>   |      0        |     TOS       |       IPv4 Identification     =
|
>>>>>>   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>   |                        IPv4 Payload                           =
|
>>>>>>   |                                                               =
|
>>>>>> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
>>>>>>=20
>>>>>> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
>>>>>>=20
>>>>>> how do you think?
>>>>>=20
>>>>> IMHO, I'm not sure it is good idea to change the semantics of the =
IPv6 fragment. If a router receives 4rd-U packets, which router doesn't =
understand 4rd-U, processing these packets as fragmented packets could =
cause problem that sounds buffer exhaust attack.
>>>>=20
>>>> I don't see that:
>>>> - IPv6 routers are not concerned with fragmentation.
>>>> - the 4rd-U endpoint doesn't need to keep anything in a reassembly =
buffer if a conveyed IPv4 packet is completely contained in a single =
IPv6 packet.
>>>>=20
>>>>> And I also think that if we need to add new semantics even we can =
utilize IPv6 fragment, it would be better to define new protocol number =
for 4rd-U.
>>>>=20
>>>> See above why a new protocol number wouldn't be workable.
>>>>=20
>>>>> However, I don't think that we need to request to define it, =
because existing encapsulation and translation can be utilized for each =
appropriate situation.
>>>>=20
>>>>=20
>>>>=20
>>>> The point isn't to prevent any ISP from deploy for its own use any =
design that works.
>>>>=20
>>>> Yet, having only ONE STANDARD for a given need is better than =
several.=20
>>>> I hope you can agree with that.
>>>> (In this case, the need is stateless support of residual IPv4 =
across IPv6-only networks.)
>>>>=20
>>>> AFAIK, 4rd-U is better for this than double translation (say =
4rd-T), and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E). =20
>>>> If you still believe this is not right, an explanation will of =
course be welcome.
>>>>=20
>>>> Cheers,
>>>> RD
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>>=20
>>>>> cheers,
>>>>> --satoru
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> cheers,
>>>>>> maoke
>>>>>>=20
>>>>>> cheers,
>>>>>> --satoru
>>>>>>=20
>>>>>>> regards,
>>>>>>> maoke
>>>>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>>>>> Hi Remi-san,
>>>>>>>=20
>>>>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>>>>>> It can make IMHO a valuable unified standard.
>>>>>>>=20
>>>>>>> Not enough. The original TTL value in IPv4 header must be =
carried.
>>>>>>>=20
>>>>>>> cheers,
>>>>>>> --satoru
>>>>>>>=20
>>>>>>>=20
>>>>>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>>>>>>>=20
>>>>>>>> Hi Satoru-san,
>>>>>>>>=20
>>>>>>>> Thank you for identifying a limitation of the 4rd-U
>>>>>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
>>>>>>>> All these need e2e transparency to the IPv4 Type of Service.
>>>>>>>>=20
>>>>>>>> Fortunately, this is easy to fix: in the Identification field =
of the IPv6 Fragment header, copy not only the DF bits but also the IPv4 =
TOS.
>>>>>>>>=20
>>>>>>>> The proposed 4r-U packet format becomes:
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>>> |Vers=3D6 |   TrafClass   |            Flow Label               =
  |
>>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>>> |         Payload Length        |Next Header=3D44 |   Hop Limit =
  |
>>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>>> |                                                               =
|
>>>>>>>> +                                                               =
+
>>>>>>>> |                                                               =
|
>>>>>>>> +                  IPv6 Source Address                          =
+
>>>>>>>> |                                                               =
|
>>>>>>>> +                                                               =
+
>>>>>>>> |                                                               =
|
>>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>>> |                                                               =
|
>>>>>>>> +                                                               =
+
>>>>>>>> |                                                               =
|
>>>>>>>> +                IPv6 Destination Address                       =
+
>>>>>>>> |                                                               =
|
>>>>>>>> +                                                               =
+
>>>>>>>> |                                                               =
|
>>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>>> |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 =
|M|
>>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>>> |D|      0      |    IPv4 TOS   |       IPv4 Identification     =
|
>>>>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>>>>> |                        IPv4 Payload                           =
|
>>>>>>>> |                                                               =
|
>>>>>>>>=20
>>>>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>>>>>>>> It can make IMHO a valuable unified standard.
>>>>>>>>=20
>>>>>>>> Yet, I may have missed something else.
>>>>>>>> New justified objections are therefore most welcome..
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Regards,
>>>>>>>> RD
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> Softwires mailing list
>>>>>>> Softwires@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/softwires
>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Softwires mailing list
>>>> Softwires@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/softwires
>>>=20
>=20

From ichiroumakino@gmail.com  Mon Oct 17 10:34:16 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 8199421F8BB6 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 10:34:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cC2unLeKOzMS for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 10:34:16 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id BC08921F8BB5 for <softwires@ietf.org>; Mon, 17 Oct 2011 10:34:15 -0700 (PDT)
Received: by eyg24 with SMTP id 24so3360508eyg.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 10:34:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=pXnor0exNsRecPb23F70KHo8zkYad3ydxSE0OGayNjc=; b=r+P4xvRI+XstGA0oBhE+qkUYXudkC5RxjT613tn2atlz5Rrch2jfi1C7LhH1p4uOyX SAMQmU0wMl3TWgWpvUjvy849rpUJvv5hjrGdeaYJMllXpodeLnxvw7r6ixdL8RfYxYjS 3Q574LltSpp2SoaAbd6JmnBj88m3Tlui/17UY=
Received: by 10.14.9.35 with SMTP id 35mr764950ees.179.1318872854864; Mon, 17 Oct 2011 10:34:14 -0700 (PDT)
Received: from gomlefisk.lan (141.84-48-218.nextgentel.com. [84.48.218.141]) by mx.google.com with ESMTPS id f16sm31307329eec.8.2011.10.17.10.34.13 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Oct 2011 10:34:14 -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: <C0590740-D4FC-4BF7-8AD6-BB77E2668479@laposte.net>
Date: Mon, 17 Oct 2011 19:34:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D30CA78-9268-4CAB-AADE-7DD9E30DE6D8@employees.org>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <542B93F7-F8E1-4E2B-BEB9-CF8196BAAB45@employees.org> <C0590740-D4FC-4BF7-8AD6-BB77E2668479@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 17 Oct 2011 17:34:16 -0000

Remi,

>>>> how is 4rd-U different from translation?
>>>=20
>>> Functionally, full network transparency to DF bit (and TOS with the =
complement that was missing).
>>> Technically, see for instance Figure 1 of the draft.
>>=20
>> I thought the dIVI guys presented the DF bit transparency during the =
Beijing meeting?
>=20
> They did, but AFAIK not as completely as section 1 of my draft.
>=20
>=20
>> I don't understand what the difference between "IP data" and =
Transport is in figure 1.
>=20
> IP data is, as shown in my Figure 1, everything after the IPv4 header:
>             +----------------+  =20
>             |   IPv4 Header  |   =20
>             +----------------+        =20
>             |    IP Data     |        =20
>             +----------------+         =20
>=20
> Transport header is as in Figure 2 of RFC 6145:
>=20
>              +-------------+                 +-------------+
>              |    IPv4     |                 |    IPv6     |
>              |   Header    |                 |   Header    |
>              +-------------+                 +-------------+
>              |  Transport- |                 |  Fragment   |
>              |   Layer     |      =3D=3D=3D>       |   Header    |
>              |   Header    |                 | (if needed) |
>              +-------------+                 +-------------+
>              |             |                 |  Transport- |
>              ~    Data     ~                 |   Layer     |
>              |             |                 |   Header    |
>              +-------------+                 +-------------+
>                                              |             |
>                                              ~    Data     ~
>                                              |             |
>                                              +-------------+           =
                                =20
>=20
> May I suggest that you re-read RFC 6145, and thus understand all what =
becomes unnecessary with 4rd-U :-).
>=20
>=20
>> consider me slow, but don't you still either have to update the =
transport checksum, or adjust the checksum with other changes in the =
IPv6 header, e.g. flow.
>=20
> None of this is needed (this is where 4rd-U has in common with =
4rd-Encap).

I thought we agreed that we didn't want to create packets with invalid =
checksums. this could trivially be made checksum neutral though.
in any case I thought this was exactly what dIVI did already...

cheers,
Ole

cheers,
Ole=

From brian.e.carpenter@gmail.com  Mon Oct 17 13:17:53 2011
Return-Path: <brian.e.carpenter@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 532C021F8C5E for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 13:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.412
X-Spam-Level: 
X-Spam-Status: No, score=-103.412 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gG+pzoskGCoU for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 13:17:52 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 01F2121F8C39 for <softwires@ietf.org>; Mon, 17 Oct 2011 13:17:48 -0700 (PDT)
Received: by qadb12 with SMTP id b12so3157585qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 13:17:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Yq+RfMXmI2/M4R8r8tbUzL7Atgvjsc7yr8bmf/SbuAQ=; b=bNqxBsZUbSTK4m/Y9KANfJpn+CVkNKkC512h+bxIM4c1DclKo3fau4CBFonmeCkFhS kT2ddQlXJIFVxvNm/gC2HQ/UUgYOOldAXhkoZBRVz6UBxxm85cp/iloANi753LjvAgF2 WAwX85GD45OEHahTC/T1fhuyOkYsSQ+N8qRMw=
Received: by 10.229.65.72 with SMTP id h8mr4551476qci.24.1318882659685; Mon, 17 Oct 2011 13:17:39 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id et6sm25337048qab.4.2011.10.17.13.17.36 (version=SSLv3 cipher=OTHER); Mon, 17 Oct 2011 13:17:38 -0700 (PDT)
Message-ID: <4E9C8D5C.4060706@gmail.com>
Date: Tue, 18 Oct 2011 09:17:32 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net>
In-Reply-To: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Softwires WG <softwires@ietf.org>
Subject: [Softwires] ECN [4rd-U complement - e2e transparency to IPv4 TOS]
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, 17 Oct 2011 20:17:53 -0000

On 2011-10-18 01:36, R=C3=A9mi Despr=C3=A9s wrote:
> Hi Satoru-san,
>=20
> Thank you for identifying a limitation of the 4rd-U =20
> You are right, as currently specified, "it doesn't support diff-serv tu=
nneling model, pipe and short-pipe".
> All these need e2e transparency to the IPv4 Type of Service.
>=20
> Fortunately, this is easy to fix: in the Identification field of the IP=
v6 Fragment header, copy not only the DF bits but also the IPv4 TOS.

Will this cause any difficulties for ECN, if ECN is supported on the IPv6=

leg of the journey?

Apart from that, please remember that the DSCP part of the DS Field is no=
t an
end-to-end field; it is mutable. I advise applying the relevant considera=
tions
from Sections 4.1 and 5.1 of RFC 6145.

Regards
   Brian Carpenter




From jacni@jacni.com  Mon Oct 17 18:52:05 2011
Return-Path: <jacni@jacni.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 23FB611E80AE for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 18:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.653
X-Spam-Level: 
X-Spam-Status: No, score=-0.653 tagged_above=-999 required=5 tests=[AWL=-1.069, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, J_CHICKENPOX_42=0.6, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UY4xbPqDkifw for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 18:52:04 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 5B26111E80A2 for <softwires@ietf.org>; Mon, 17 Oct 2011 18:52:03 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id B39123800AC for <softwires@ietf.org>; Mon, 17 Oct 2011 21:52:01 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 407D334010E for <softwires@ietf.org>; Tue, 18 Oct 2011 09:52:00 +0800 (CST)
Received: from [172.22.35.174] (unknown [221.11.61.184]) by app (Coremail) with SMTP id +AWowJCroQa125xOVg0eAA--.6142S2; Tue, 18 Oct 2011 09:51:51 +0800 (CST)
Message-ID: <4E9CDC24.3000202@jacni.com>
Date: Tue, 18 Oct 2011 09:53:40 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: c-sun@bb.softbank.co.jp
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local>
In-Reply-To: <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local>
Content-Type: multipart/alternative; boundary="------------030400000503070008060301"
X-CM-TRANSID: +AWowJCroQa125xOVg0eAA--.6142S2
X-Coremail-Antispam: 1UD129KBjvJXoWxJF4xGF4xZF4rJw15GFyDWrg_yoW5Cryxpr y3tF13Jr4DJr1UAwnagw1DWrs8AF93Ja1UJ3yUKr1xu3W5AF1UZrs5KrZ3XFWUXrWxAw1I qr4qyryrAwn8AaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU4Yb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VW3JwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK64x0aVW7Gw IE548m6rI_Jw1UWr17M2vj6xkI62vS6c8GOVWUtr1rJFyl5I8CrVAYj202j2C_Jr0_Gr1l 5I8CrVAKz4kIr2xC04v26r1j6r4UMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67 AKxVWUJVW8JwACjcxG0xvEwIxGrwCjr7xvwVCIw2I0I7xG6c02F41lc7I2V7IY0VAS07Al zVAYIcxG8wCF04k20xvY0x0EwIxGrwCFI7vE0wC2zVAF1VAY17CE14v26r1Y6r17MIIYrx kI7VAKI48JYxBIdaVFxhVjvjDU0xZFpf9x07jfL05UUUUU=
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQAFEko7lOsNlgAAsD
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 18 Oct 2011 01:52:05 -0000

This is a multi-part message in MIME format.
--------------030400000503070008060301
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

hi

On 10/17/2011 8:26 PM, c-sun@bb.softbank.co.jp wrote:
> Hi,
> This is my command in line.
>
>>
>>>     therefore my answer to Q1, is NO, unless we carefully select
>>>     IPv4 addresses for CEs with giving up to use some of them, which
>>>     have been so precious.
>>>     Q2. then it must fine as long as we map them to different Rule
>>>     IPv6 Prefix. (?)
>>>     suppose CE1 is the same as (1). for 64.32../16, we use a longer
>>>     stuff.
>>>     however, there is a CE3:
>>>     Rule IPv6 Prefix B: 20010db8 (2001:db8::/29)
>>>     CE3 IPv4 address: 4020 1876 (64.32.24.118)
>>>     CE3 PSID: 54
>>>     CE3 CE index: 987654
>>>     ---------------------------------------------------------------
>>>     (3) CE3 IPv6 prefix: 20010db 987654 (2001:db9:8765:4000::/52,
>>>     woops!)
>>>     ambiguity happens. then we may argue: using the ugly
>>>     Rule_IPv6_Prefix_B is the root of the problem! we have not to
>>>     use a prefix covered by another.
>>     No, I think the bits of the same position are not additive. So,
>>     it should be a delegated prefix of "/53", right?
>>
>>
>> :P sorry for the typo but i have pointed out in the errata. :P
>> however, even though this is /53, and you will have, in the route
>> table, both
>> 2001:db9:8765:4000::/52 => route to CE1
>> 2001:db9:8765:4000::/53 => route to CE3
>>
>> but for the packet encapsulated with the destination address
>> 2001:db9:8765:4000::200:5efe, you couldn't decide the route should go
>> to CE3 instead of CE1. here the longest-match doesn't work. right?
> I guess the second delegated prefix should be 2001:db8:1876:5400::/53
> I guess the second delegated prefix should be 2011:db8:c3b2:a000::/53.
Oops, sorry. ;-)

> Because the CE3 Rule IPv6 Prefix length is not mulitipe of 4 bits,it
> need calculate using Binary as follows.
>
> v(/29)
> --elipsis(0x2001 0db)--1000 (2011:db8::/29)
> --elipsis(0x4020)------ 000 1100 0011 1011 0 (64.32.24.118)
> 010 1010 0 (PSID 0x54)
> --------------------------------------------------------------------------
> CE3 IPv6 prefix: 2001:db8:c3b2:a000::/53
>
> If the CE3 IPv4 address is 64.32.48.236, CE3 PSID is 0xa8, calculate
> as follows,
> v(/29)
> --elipsis(0x2001 0db)--1000 (2011:db8::/29)
> --elipsis(0x4020)------ 001 1000 0111 0110 0 (64.32.48.236)
> 101 0100 0 (PSID 0xa8)
> --------------------------------------------------------------------------
> the CE3 IPv6 prefix is 2001:db9:8765:4000::/53
>
> I think this should be not gonna happen, since the IPv6 address
> planing must be done natively
> considering nothing about the IPv4 address. As exclusiveness, each CE
> has unique CE IPv6 Prefix.
>
> As described in the example Maoke given, since "Rule IPv6 Prefix B" is
> contained in the "Rule IPv6 Prefix A",
> if the IPv6 addresses under Rule IPv6 Prefix A and the IPv6 address
> under Rule IPv6 prefix B are assigned independently
> and have any consideration each other, same CE IPv6 prefix assigning
> to different CEs may be happen. I think this MUST be
> avoided when designing the mapping rules or setting the IPv6 assigning
> way(such as DHCPv6 etc.).
>
The address assignment under one given prefix should be done with
considerations to avoid conflicts.


Cheers,
Jacni

> Cheers
>
> Chunfa
>
>

--------------030400000503070008060301
Content-Type: text/html; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-2022-JP"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    hi<br>
    <br>
    On 10/17/2011 8:26 PM, <a class="moz-txt-link-abbreviated" href="mailto:c-sun@bb.softbank.co.jp">c-sun@bb.softbank.co.jp</a> wrote:
    <blockquote
      cite="mid:6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-2022-JP">
      <meta content="MSHTML 6.00.2900.6148" name="GENERATOR">
      <div dir="ltr" align="left"><font color="#0000ff" face="$B#M#S(B $B#P%4%7%C%/(B"
          size="2"><span class="888562212-17102011">Hi,</span></font></div>
      <div dir="ltr" align="left"><font color="#0000ff" face="$B#M#S(B $B#P%4%7%C%/(B"
          size="2"><span class="888562212-17102011"></span></font>&nbsp;</div>
      <div dir="ltr" align="left"><font color="#0000ff" face="$B#M#S(B $B#P%4%7%C%/(B"
          size="2"><span class="888562212-17102011">This is my command
            in line.</span></font></div>
      <br>
      <blockquote
cite="mid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com"
        type="cite">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex;
            MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
            <div text="#000000" bgcolor="#FFFFFF">
              <div class="im"><br>
                <blockquote type="cite">
                  <div><font face="Courier New">therefore my answer to
                      Q1, is NO, </font><font face="Courier New">unless
                      we carefully select IPv4 addresses for CEs with
                      giving up to use some of them, which have been so
                      precious. </font></div>
                  <div>&nbsp;</div>
                  <div><font face="Courier New">Q2. then it must fine as
                      long as we map them to <font color="#ff0000">different</font>
                      Rule IPv6 Prefix. (?)</font></div>
                  <div>&nbsp;</div>
                  <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;suppose CE1 is the
                      same as (1). for 64.32../16, we use a longer
                      stuff.</font></div>
                  <div><font face="Courier New">&nbsp;&nbsp;&nbsp; however, there is a
                      CE3:</font></div>
                  <div>&nbsp;</div>
                  <font face="courier new,monospace">
                    <div>
                      <div>
                        <div><font face="courier new,monospace">&nbsp;&nbsp;Rule
                            IPv6 Prefix B: 20010db<font color="#ff0000">8</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                            (2001:db8::/<font color="#ff0000">29</font>)</font></div>
                      </div>
                    </div>
                  </font>
                  <div>
                    <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp; CE3 IPv4
                        address: &nbsp;&nbsp; 4020 <font color="#ff0000">1</font><font
                          color="#000000">876</font>&nbsp;&nbsp;&nbsp;(64.32.24.118)</font></div>
                    <div>
                      <div><font face="courier new,monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                          &nbsp; CE3 PSID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;54&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></div>
                      <div><font face="Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CE3 CE
                          index:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font color="#ff0000">9</font>87654</font></div>
                      <font face="Courier New">
                        <div><font face="Courier New">---------------------------------------------------------------</font></div>
                        <div>(3)&nbsp; CE3 IPv6 prefix: 20010db&nbsp;987654 (<font
                            color="#ff9966">2001:db9:8765:4000::/52,
                            woops!</font>)</div>
                      </font></div>
                  </div>
                  <div>&nbsp;</div>
                  <div><font face="Courier New">ambiguity happens.
                      then&nbsp;we may argue: using the ugly
                      Rule_IPv6_Prefix_B is the root of the problem! we
                      have not to use a prefix covered by another. </font></div>
                  <div>&nbsp;</div>
                </blockquote>
              </div>
              No, I think the bits of the same position are not
              additive. So, it should be a delegated prefix of "/53",
              right?</div>
          </blockquote>
          <div><br>
          </div>
          <div>:P sorry for the typo but i have pointed out in the
            errata. :P however, even though this is /53, and you will
            have, in the route table, both&nbsp;</div>
          <div>&nbsp; &nbsp;2001:db9:8765:4000::/52 =&gt; route to CE1</div>
          <div>&nbsp; &nbsp;2001:db9:8765:4000::/53 =&gt; route to CE3</div>
          <div><br>
          </div>
          <div>but for the packet encapsulated with the destination
            address 2001:db9:8765:4000::200:5efe, you couldn't decide
            the route should go to CE3 instead of CE1. here the
            longest-match doesn't work. right?</div>
          <div>&nbsp;</div>
        </div>
      </blockquote>
      <div>I guess the second delegated prefix should be
        2001:db8:1876:5400::/53<span class="888562212-17102011"><font
            color="#0000ff" face="$B#M#S(B $B#P%4%7%C%/(B" size="2">&nbsp;</font></span></div>
      <div><span class="888562212-17102011"></span>&nbsp;</div>
      <div><span class="888562212-17102011"><span
            class="Apple-style-span" style="word-spacing: 0px; font:
            13px arial,sans-serif; text-transform: none; color: rgb(0,
            0, 0); text-indent: 0px; white-space: normal;
            letter-spacing: normal; background-color: rgb(255, 255,
            255); orphans: 2; widows: 2;">
            <div>
              <div><font color="#0000ff"><span
                    class="888562212-17102011"><font face="$B#M#S(B $B#P%4%7%C%/(B"
                      size="2">&nbsp;&nbsp;</font></span>I guess the second
                  delegated prefix should be 2011:db8:c3b2:a000::/53.</font></div>
            </div>
          </span></span></div>
    </blockquote>
    <font face="Verdana">Oops, sorry. ;-)</font><br>
    <br>
    <blockquote
      cite="mid:6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local"
      type="cite">
      <div><span class="888562212-17102011"><span
            class="Apple-style-span" style="word-spacing: 0px; font:
            13px arial,sans-serif; text-transform: none; color: rgb(0,
            0, 0); text-indent: 0px; white-space: normal;
            letter-spacing: normal; background-color: rgb(255, 255,
            255); orphans: 2; widows: 2;">
            <div>
              <div><font color="#0000ff">Because the CE3 Rule IPv6
                  Prefix length is not mulitipe of 4 bits,it need
                  calculate using Binary as follows.&nbsp;</font></div>
              <div><font color="#0000ff"><br>
                </font></div>
              <div><font color="#0000ff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                  &nbsp;v(/29)</font></div>
              <div><font color="#0000ff">&nbsp;--elipsis(0x2001 0db)--1000 &nbsp;
                  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                  &nbsp;(2011:db8::/29)</font></div>
              <div><font color="#0000ff">&nbsp;--elipsis(0x4020)------ &nbsp; &nbsp;000
                  1100 0011 1011 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (64.32.24.118)</font></div>
              <div><font color="#0000ff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;010 1010 0 (PSID
                  0x54)</font></div>
              <div><font color="#0000ff">------------------------------<wbr>------------------------------<wbr>--------------</font></div>
              <div><font color="#0000ff">CE3 IPv6 prefix:
                  2001:db8:c3b2:a000::/53</font></div>
              <div><font color="#0000ff"><br>
                </font></div>
              <div><font color="#0000ff">If the CE3 IPv4 address is
                  64.32.48.236, CE3 PSID is 0xa8, calculate as follows,</font></div>
              <div><font color="#0000ff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                  &nbsp;v(/29)</font></div>
              <div><font color="#0000ff">&nbsp;--elipsis(0x2001 0db)--1000 &nbsp;
                  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                  &nbsp;(2011:db8::/29)</font></div>
              <div><font color="#0000ff">&nbsp;--elipsis(0x4020)------ &nbsp; &nbsp;001
                  1000 0111 0110 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (64.32.48.236)</font></div>
              <div><font color="#0000ff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;101 0100 0 (PSID
                  0xa8)</font></div>
              <div><font color="#0000ff">------------------------------<wbr>------------------------------<wbr>--------------</font></div>
              <div><font color="#0000ff">the CE3 IPv6 prefix is
                  2001:db9:8765:4000::/53 &nbsp;</font></div>
              <div><font color="#0000ff"><br>
                </font></div>
              <div><font color="#0000ff">I think this&nbsp;<span
                    class="888562212-17102011"><font face="$B#M#S(B $B#P%4%7%C%/(B"
                      size="2">&nbsp;should be</font></span> not gonna
                  happen, since the IPv6 address planing must be done
                  natively&nbsp;</font></div>
              <div><font color="#0000ff">considering nothing about the
                  IPv4 address. As exclusiveness, each CE has unique CE
                  IPv6 Prefix.&nbsp;</font></div>
              <div><font color="#0000ff"><br>
                </font></div>
              <div><font color="#0000ff">As described in the example
                  Maoke given, since "Rule IPv6 Prefix B" is contained
                  in the "Rule IPv6 Prefix A",&nbsp;</font></div>
              <div><font color="#0000ff">if the IPv6 addresses under
                  Rule IPv6 Prefix A and the IPv6 address under Rule
                  IPv6 prefix B are assigned independently&nbsp;</font></div>
              <div><font color="#0000ff">and have any consideration each
                  other, same CE IPv6 prefix assigning to different CEs
                  may be happen. I think this MUST be</font></div>
              <div><font color="#0000ff">&nbsp;avoided when designing the
                  mapping rules or setting the IPv6 assigning way(such
                  as DHCPv6 etc.).&nbsp;</font></div>
            </div>
            <div><font color="#0000ff"><br>
              </font></div>
          </span></span></div>
    </blockquote>
    <font face="Verdana">The address assignment under one given prefix
      should be done with considerations to avoid conflicts.<br>
      <br>
      <br>
      Cheers,<br>
      Jacni<br>
    </font><br>
    <blockquote
      cite="mid:6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local"
      type="cite">
      <div><span class="888562212-17102011"><span
            class="Apple-style-span" style="WORD-SPACING: 0px; FONT:
            13px arial, sans-serif; TEXT-TRANSFORM: none; COLOR:
            rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal;
            LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(255,255,255);
            orphans: 2; widows: 2; webkit-text-decorations-in-effect:
            none; webkit-text-size-adjust: auto;
            webkit-text-stroke-width: 0px">
            <div><font color="#0000ff">Cheers</font></div>
            <div><font color="#0000ff"><br>
              </font></div>
            <div><font color="#0000ff">Chunfa</font></div>
          </span>&nbsp;</span><br>
        <br>
      </div>
      <blockquote
cite="mid:CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com"
        type="cite">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex;
            MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
            <div text="#000000" bgcolor="#FFFFFF">&nbsp;</div>
          </blockquote>
        </div>
      </blockquote>
    </blockquote>
  </body>
</html>

--------------030400000503070008060301--


From fibrib@gmail.com  Mon Oct 17 19:28:23 2011
Return-Path: <fibrib@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 7820F1F0C53 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 19:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.292
X-Spam-Level: 
X-Spam-Status: No, score=-2.292 tagged_above=-999 required=5 tests=[AWL=-0.778, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKBRQ-9bOkyK for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 19:28:22 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id AB4D41F0C43 for <softwires@ietf.org>; Mon, 17 Oct 2011 19:28:22 -0700 (PDT)
Received: by qadb12 with SMTP id b12so73550qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 19:28:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MjQRN7w4Jx0Ohb1MF8s6ljvuL39W3hlJ+SK9D4Y2CxY=; b=sTey1d5yURVAyJ6gQe/X3z557i/BmdB43ysFk0pZWhKk+zyowy5wrOsgYZF0yiYz3I kIqYXdCdsTVmdA1p6DtE25d0rB6AzooH5+rssX3iD2N12r1IQQRF8CTP7Qa3OM8DUg6H 5pYlmi60yOVo0XN8dUq5rEMBRHcbR0HvkenSA=
MIME-Version: 1.0
Received: by 10.229.80.16 with SMTP id r16mr84146qck.107.1318904901081; Mon, 17 Oct 2011 19:28:21 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Mon, 17 Oct 2011 19:28:20 -0700 (PDT)
In-Reply-To: <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local>
Date: Tue, 18 Oct 2011 11:28:20 +0900
Message-ID: <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: c-sun@bb.softbank.co.jp
Content-Type: multipart/alternative; boundary=0016364ee7641f1cc104af897ac2
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 18 Oct 2011 02:28:23 -0000

--0016364ee7641f1cc104af897ac2
Content-Type: text/plain; charset=ISO-8859-1

hi Chunfa and Jacni,

thanks a lot for the corrections and clarifications. :)

2011/10/17 <c-sun@bb.softbank.co.jp>

>  I guess the second delegated prefix should be 2001:db8:1876:5400::/53
>
>    I guess the second delegated prefix should be 2011:db8:c3b2:a000::/53.
> Because the CE3 Rule IPv6 Prefix length is not mulitipe of 4 bits,it need
> calculate using Binary as follows.
>
>                                  v(/29)
>  --elipsis(0x2001 0db)--1000
>  (2011:db8::/29)
>  --elipsis(0x4020)------    000 1100 0011 1011 0
> (64.32.24.118)
>                                                                    010 1010
> 0 (PSID 0x54)
> --------------------------------------------------------------------------
> CE3 IPv6 prefix: 2001:db8:c3b2:a000::/53
>
> If the CE3 IPv4 address is 64.32.48.236, CE3 PSID is 0xa8, calculate as
> follows,
>                                  v(/29)
>  --elipsis(0x2001 0db)--1000
>  (2011:db8::/29)
>  --elipsis(0x4020)------    001 1000 0111 0110 0
> (64.32.48.236)
>                                                                    101 0100
> 0 (PSID 0xa8)
> --------------------------------------------------------------------------
> the CE3 IPv6 prefix is 2001:db9:8765:4000::/53
>
> I think this  should be not gonna happen, since the IPv6 address planing
> must be done natively
> considering nothing about the IPv4 address. As exclusiveness, each CE has
> unique CE IPv6 Prefix.
>
> As described in the example Maoke given, since "Rule IPv6 Prefix B" is
> contained in the "Rule IPv6 Prefix A",
> if the IPv6 addresses under Rule IPv6 Prefix A and the IPv6 address under
> Rule IPv6 prefix B are assigned independently
> and have any consideration each other, same CE IPv6 prefix assigning to
> different CEs may be happen. I think this MUST be
>  avoided when designing the mapping rules or setting the IPv6 assigning
> way(such as DHCPv6 etc.).
>
>
the consensus is keeping the exclusiveness of IPv4 address blocks in IPv6.
therefore, i understand the logic of address planning for CEs in 4rd could
be the following 4 steps:

1) list all mutually exclusive IPv4 networks to be involved in the residual
deployment, i.e., Rule IPv4 prefixes;
2) calculate IPv6 prefix length for each Rule IPv4 prefix, according to the
length of the prefix and the requirement like the PSID length and the CE
prefix length;
3) allocate the IPv6 address space into exclusive blocks, i.e.
rule_IPv6_prefixes, according to the prefix length requirements in 2), and
get the mapping rules;
4) assigning IPv6 address in each block for the CE.

am i right?

cheers,
maoke


> Cheers
>
> Chunfa
>
>
>
>>
>

--0016364ee7641f1cc104af897ac2
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>hi Chunfa and Jacni,<br></div><div><br></div><div>thanks a lot for the=
 corrections and clarifications. :)</div><div><br></div><div class=3D"gmail=
_quote">2011/10/17  <span dir=3D"ltr">&lt;<a href=3D"mailto:c-sun@bb.softba=
nk.co.jp">c-sun@bb.softbank.co.jp</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">



<div text=3D"#000000" bgcolor=3D"#ffffff">
<div dir=3D"ltr" align=3D"left">I guess the second delegated prefix should =
be 2001:db8:1876:5400::/53<span><font face=3D"=A3=CD=A3=D3 =A3=D0=A5=B4=A5=
=B7=A5=C3=A5=AF" color=3D"#0000ff" size=3D"2">&nbsp;</font></span></div><di=
v class=3D"im">
<div>&nbsp;</div>
</div><div><span><span style=3D"word-spacing:0px;font:13px arial, sans-seri=
f;text-transform:none;color:rgb(0,0,0);text-indent:0px;white-space:normal;l=
etter-spacing:normal;background-color:rgb(255,255,255)">
<div><div class=3D"im">
<div><font color=3D"#0000ff"><span><font face=3D"=A3=CD=A3=D3 =A3=D0=A5=B4=
=A5=B7=A5=C3=A5=AF" size=3D"2">&nbsp;&nbsp;</font></span>I guess the second=
 delegated prefix should be=20
2011:db8:c3b2:a000::/53.</font></div>
<div><font color=3D"#0000ff">Because the CE3 Rule IPv6 Prefix length is not=
 mulitipe=20
of 4 bits,it need calculate using Binary as follows.&nbsp;</font></div>
<div><font color=3D"#0000ff"><br></font></div>
<div><font color=3D"#0000ff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;v(/29)</font></div>
<div><font color=3D"#0000ff">&nbsp;--elipsis(0x2001 0db)--1000 &nbsp; &nbsp=
; &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;(2011:db8::/29)</font></div>
<div><font color=3D"#0000ff">&nbsp;--elipsis(0x4020)------ &nbsp; &nbsp;000=
 1100=20
0011 1011 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
(64.32.24.118)</font></div>
<div><font color=3D"#0000ff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp;010 1010 0 (PSID 0x54)</font></div>
<div><font color=3D"#0000ff">----------------------------------------------=
----------------------------</font></div>
<div><font color=3D"#0000ff">CE3 IPv6 prefix: 2001:db8:c3b2:a000::/53</font=
></div>
<div><font color=3D"#0000ff"><br></font></div>
<div><font color=3D"#0000ff">If the CE3 IPv4 address is 64.32.48.236, CE3 P=
SID is=20
0xa8, calculate as follows,</font></div>
<div><font color=3D"#0000ff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;v(/29)</font></div>
<div><font color=3D"#0000ff">&nbsp;--elipsis(0x2001 0db)--1000 &nbsp; &nbsp=
; &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp;(2011:db8::/29)</font></div>
<div><font color=3D"#0000ff">&nbsp;--elipsis(0x4020)------ &nbsp; &nbsp;001=
 1000=20
0111 0110 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
(64.32.48.236)</font></div>
<div><font color=3D"#0000ff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; &nbsp; &nbsp; &nbsp;101 0100 0 (PSID 0xa8)</font></div>
<div><font color=3D"#0000ff">----------------------------------------------=
----------------------------</font></div>
</div><div><font color=3D"#0000ff">the CE3 IPv6 prefix is 2001:db9:8765:400=
0::/53=20
&nbsp;</font></div>
<div><font color=3D"#0000ff"><br></font></div>
<div><font color=3D"#0000ff">I think this&nbsp;<span><font face=3D"=A3=CD=
=A3=D3 =A3=D0=A5=B4=A5=B7=A5=C3=A5=AF" size=3D"2">&nbsp;should be</font></s=
pan> not gonna happen, since the=20
IPv6 address planing must be done natively&nbsp;</font></div><div class=3D"=
im">
<div><font color=3D"#0000ff">considering nothing about the IPv4 address. As=
=20
exclusiveness, each CE has unique CE IPv6 Prefix.&nbsp;</font></div>
<div><font color=3D"#0000ff"><br></font></div>
<div><font color=3D"#0000ff">As described in the example Maoke given, since=
 &quot;Rule=20
IPv6 Prefix B&quot; is contained in the &quot;Rule IPv6 Prefix A&quot;,&nbs=
p;</font></div>
<div><font color=3D"#0000ff">if the IPv6 addresses under Rule IPv6 Prefix A=
 and the=20
IPv6 address under Rule IPv6 prefix B are assigned=20
independently&nbsp;</font></div>
<div><font color=3D"#0000ff">and have any consideration each other, same CE=
 IPv6=20
prefix assigning to different CEs may be happen. I think this MUST=20
be</font></div>
<div><font color=3D"#0000ff">&nbsp;avoided when designing the mapping rules=
 or=20
setting the IPv6 assigning way(such as DHCPv6 etc.).&nbsp;</font></div></di=
v></div>
<div><font color=3D"#0000ff"><br></font></div></span></span></div></div></b=
lockquote><div><br></div><div>the consensus is keeping the exclusiveness of=
 IPv4 address blocks in IPv6. therefore, i understand the logic of address =
planning for CEs in 4rd could be the following 4 steps:&nbsp;</div>
<div><br></div><div>1) list all mutually exclusive IPv4 networks to be invo=
lved in the residual deployment, i.e., Rule IPv4 prefixes;&nbsp;</div><div>=
2) calculate IPv6 prefix length for each Rule IPv4 prefix, according to the=
 length of the prefix and the requirement like the PSID length and the CE p=
refix length; &nbsp;</div>
<div>3) allocate the IPv6 address space into exclusive blocks, i.e. rule_IP=
v6_prefixes, according to the prefix length requirements in 2), and get the=
 mapping rules;</div><div>4) assigning IPv6 address in each block for the C=
E.&nbsp;</div>
<div><br></div><div>am i right?&nbsp;</div><div><br></div><div>cheers,</div=
><div>maoke</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div te=
xt=3D"#000000" bgcolor=3D"#ffffff">
<div><span><span style=3D"word-spacing:0px;font:13px arial, sans-serif;text=
-transform:none;color:rgb(0,0,0);text-indent:0px;white-space:normal;letter-=
spacing:normal;background-color:rgb(255,255,255)">
<div><font color=3D"#0000ff">Cheers</font></div>
<div><font color=3D"#0000ff"><br></font></div>
<div><font color=3D"#0000ff">Chunfa</font></div></span>&nbsp;</span><br><br=
></div>
<blockquote type=3D"cite">
  <div class=3D"gmail_quote">
  <blockquote class=3D"gmail_quote" style=3D"padding-left:1ex;margin:0px 0p=
x 0px 0.8ex;border-left:#ccc 1px solid">
    <div text=3D"#000000" bgcolor=3D"#FFFFFF">&nbsp;</div></blockquote></di=
v></blockquote></div>
</blockquote></div><br>

--0016364ee7641f1cc104af897ac2--

From fibrib@gmail.com  Mon Oct 17 19:37:57 2011
Return-Path: <fibrib@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 47AE421F84CC for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 19:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.12
X-Spam-Level: 
X-Spam-Status: No, score=-3.12 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UdIqWLaENrlk for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 19:37:56 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3B76921F84CB for <softwires@ietf.org>; Mon, 17 Oct 2011 19:37:56 -0700 (PDT)
Received: by qadb12 with SMTP id b12so76971qad.31 for <softwires@ietf.org>; Mon, 17 Oct 2011 19:37:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1QejftzYeiiYo2m1xhKQsGDJoU5AioEiqA2D0mul8Tg=; b=iJhVA7Z3HH/ktbeoFZ1gJGHy/oPZgNh9oy9dJ/hn/uqwtbi4sr8T+jxbLsBv0i1M9E RCKje2qOKDPdL3bzuNjS75Eq11KkTAI2PIEgE+yTsMkZxpWOB1fQ3RFCp94HVV+qbXIJ wyzvZvNkj5NLir5yYGB3PeeydFlyezXOpj+Hk=
MIME-Version: 1.0
Received: by 10.229.62.195 with SMTP id y3mr95375qch.31.1318905475763; Mon, 17 Oct 2011 19:37:55 -0700 (PDT)
Received: by 10.229.214.212 with HTTP; Mon, 17 Oct 2011 19:37:55 -0700 (PDT)
In-Reply-To: <C87E17E8-8686-4D01-939E-E6C7C3E5DF58@free.fr>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <14AB4609-752F-44E2-BE75-EB414CC2ACFA@ipinfusion.com> <CAFUBMqVni_GNqmEx-FwzNUKUD1x2hN=xoe7Zc9pre4rfmGBWRw@mail.gmail.com> <C87E17E8-8686-4D01-939E-E6C7C3E5DF58@free.fr>
Date: Tue, 18 Oct 2011 11:37:55 +0900
Message-ID: <CAFUBMqWvuWCfU9Gw7YpThAeB2fk1sQ-kV4SD6XEVnHBtdb1W2w@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@free.fr>
Content-Type: multipart/alternative; boundary=0016e64b1d56600d0004af899cc6
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 18 Oct 2011 02:37:57 -0000

--0016e64b1d56600d0004af899cc6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Remi,

2011/10/18 R=E9mi Despr=E9s <despres.remi@free.fr>

> Hi Maoke,
>
> On 2011/10/12, you wrote:
> "... considering the double translation is a case of translation. it is
> possible that a src host with an IPv4-translatable IPv6 address generates=
 a
> fragment header with a 32-bit identifier happening to have the first 16 b=
it
> as either 0x8000 or 0x0000, making a fake D bit in your current proposal.=
"
>
> An important point is that the IP identifier needs to be unique ONLY for
> each <SRC, DST> pair.
> If 4rd addresses are deterministically recognizable (with the V octet in
> bits 64-71), there is no risk of confusion with an IP identification
> generated for another purpose than 4rd.
>

thus i understand. then you didn't try to decouple the header processing
from the mapping algorithm, right? sorry but i was confused here. :P

best,
maoke


>
> Hope it clarifies.
>
> Cheers,
> RD
>

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

<div>hi Remi,=A0</div><br><div class=3D"gmail_quote">2011/10/18 R=E9mi Desp=
r=E9s <span dir=3D"ltr">&lt;<a href=3D"mailto:despres.remi@free.fr">despres=
.remi@free.fr</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word">Hi Maoke,<div><br><div><div>On 2011/10/=
12, you wrote:</div></div><div>&quot;...=A0<span style=3D"font-family:monos=
pace">considering the double translation is a case of translation. it=A0is =
possible that=A0a src host with an IPv4-translatable IPv6 address=A0generat=
es a fragment header with a 32-bit identifier happening to have=A0the first=
 16 bit as either 0x8000 or 0x0000,=A0making a fake D bit in your=A0current=
 proposal.&quot;</span></div>
<div><span style=3D"font-family:monospace"><br></span></div><div><font face=
=3D"monospace">An important point is that the IP identifier needs to be uni=
que ONLY for each &lt;SRC, DST&gt; pair.</font></div></div><div><font face=
=3D"monospace">If 4rd addresses are deterministically recognizable (with th=
e V octet in bits 64-71), there is no risk of confusion with an IP identifi=
cation generated for another purpose than 4rd.</font></div>
</div></blockquote><div><br></div><div>thus i understand. then you didn&#39=
;t try to decouple the header processing from the mapping algorithm, right?=
 sorry but i was confused here. :P</div><div><br></div><div>best,</div>
<div>maoke</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style=3D=
"word-wrap:break-word"><div class=3D"im"><div><font face=3D"monospace"><br>=
</font></div>
<div><font face=3D"monospace">Hope it clarifies.</font></div><div><font fac=
e=3D"monospace"><br></font></div><div><font face=3D"monospace">Cheers,</fon=
t></div><div><font face=3D"monospace">RD</font></div></div></div></blockquo=
te></div>
<br>

--0016e64b1d56600d0004af899cc6--

From jacni@jacni.com  Mon Oct 17 19:52:48 2011
Return-Path: <jacni@jacni.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 C31D11F0C5A for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 19:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level: 
X-Spam-Status: No, score=-1.597 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1zncFmHE9KC for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 19:52:48 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 511731F0C52 for <softwires@ietf.org>; Mon, 17 Oct 2011 19:52:47 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id B949D3800AC for <softwires@ietf.org>; Mon, 17 Oct 2011 22:52:46 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 40A60340100 for <softwires@ietf.org>; Tue, 18 Oct 2011 10:52:45 +0800 (CST)
Received: from [172.22.35.174] (unknown [221.11.61.184]) by app (Coremail) with SMTP id +AWowJA7QAXx6ZxO3R0eAA--.39247S2; Tue, 18 Oct 2011 10:52:41 +0800 (CST)
Message-ID: <4E9CEA60.6040208@jacni.com>
Date: Tue, 18 Oct 2011 10:54:24 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com>
In-Reply-To: <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000903030707020402020608"
X-CM-TRANSID: +AWowJA7QAXx6ZxO3R0eAA--.39247S2
X-Coremail-Antispam: 1UD129KBjvdXoW7Gw45JF4rKF4kJw43AFyrWFg_yoWfZrg_Z3 yvgryUCw4Yyrs5Cay3KrWSqry7AryYyrykWr4qqFZ3A34Fv3yIyw1Syryakr98Gw4Utay5 u3ZxWay8A347WjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTX7k042IEc7kJM7k042IE4IxYO2xFxVAqjxCEw4Av424lb7Iv0xC_Cr1l b4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAa7VCY0VAaVVAqrcv_Jw 1UWr13McIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwACjcxG0xvE wIxGrwCjr7xvwVCIw2I0I7xG6c02F41lc7I2V7IY0VAS07AlzVAYIcxG8wCF04k20xvY0x 0EwIxGrwCFI7vE0wC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48JYxBIdaVFxhVj vjDU0xZFpf9x07j2c_-UUUUU=
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEFEko7lOsZFgAAsW
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 18 Oct 2011 02:52:48 -0000

This is a multi-part message in MIME format.
--------------000903030707020402020608
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit

hi,

On 10/18/2011 10:28 AM, Maoke wrote:
> ...
>
>
> the consensus is keeping the exclusiveness of IPv4 address blocks in
> IPv6. therefore, i understand the logic of address planning for CEs in
> 4rd could be the following 4 steps:
>
> 1) list all mutually exclusive IPv4 networks to be involved in the
> residual deployment, i.e., Rule IPv4 prefixes;
> 2) calculate IPv6 prefix length for each Rule IPv4 prefix,
For clarifications, you mean the "Rule IPv6 Prefix" length, right? since
the length of Delegated Prefix should have been settled before this step.


Cheers,
Jacni


> according to the length of the prefix and the requirement like the
> PSID length and the CE prefix length;
> 3) allocate the IPv6 address space into exclusive blocks, i.e.
> rule_IPv6_prefixes, according to the prefix length requirements in 2),
> and get the mapping rules;
> 4) assigning IPv6 address in each block for the CE.
>
> am i right?
>
> cheers,
> maoke
>
>     Cheers
>
>     Chunfa
>
>
>

--------------000903030707020402020608
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=GB2312" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 10/18/2011 10:28 AM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com"
      type="cite"><font color="#0000ff">...</font>
      <div text="#000000" bgcolor="#ffffff">
        <div><span><span style="word-spacing:0px;font:13px arial,
sans-serif;text-transform:none;color:rgb(0,0,0);text-indent:0px;white-space:normal;letter-spacing:normal;background-color:rgb(255,255,255)">
              <div><font color="#0000ff"><br>
                </font></div>
            </span></span></div>
      </div>
      <div class="gmail_quote">
        <div><br>
        </div>
        <div>the consensus is keeping the exclusiveness of IPv4 address
          blocks in IPv6. therefore, i understand the logic of address
          planning for CEs in 4rd could be the following 4 steps:&nbsp;</div>
        <div><br>
        </div>
        <div>1) list all mutually exclusive IPv4 networks to be involved
          in the residual deployment, i.e., Rule IPv4 prefixes;&nbsp;</div>
        <div>2) calculate IPv6 prefix length for each Rule IPv4 prefix,
        </div>
      </div>
    </blockquote>
    For clarifications, you mean the "Rule IPv6 Prefix" length, right?
    since the length of Delegated Prefix should have been settled before
    this step.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <br>
    <blockquote
cite="mid:CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>according to the length of the prefix and the requirement
          like the PSID length and the CE prefix length; &nbsp;</div>
        <div>3) allocate the IPv6 address space into exclusive blocks,
          i.e. rule_IPv6_prefixes, according to the prefix length
          requirements in 2), and get the mapping rules;</div>
        <div>4) assigning IPv6 address in each block for the CE.&nbsp;</div>
        <div><br>
        </div>
        <div>am i right?&nbsp;</div>
        <div><br>
        </div>
        <div>cheers,</div>
        <div>maoke</div>
        <div>&nbsp;</div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div text="#000000" bgcolor="#ffffff">
            <div><span><span style="word-spacing:0px;font:13px arial,
sans-serif;text-transform:none;color:rgb(0,0,0);text-indent:0px;white-space:normal;letter-spacing:normal;background-color:rgb(255,255,255)">
                  <div><font color="#0000ff">Cheers</font></div>
                  <div><font color="#0000ff"><br>
                    </font></div>
                  <div><font color="#0000ff">Chunfa</font></div>
                </span>&nbsp;</span><br>
              <br>
            </div>
            <blockquote type="cite">
              <div class="gmail_quote">
                <blockquote class="gmail_quote"
                  style="padding-left:1ex;margin:0px 0px 0px
                  0.8ex;border-left:#ccc 1px solid">
                  <div text="#000000" bgcolor="#FFFFFF">&nbsp;</div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
  </body>
</html>

--------------000903030707020402020608--


From despres.remi@laposte.net  Mon Oct 17 23:55:31 2011
Return-Path: <despres.remi@laposte.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 90AAF11E80DB for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 23:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.726
X-Spam-Level: 
X-Spam-Status: No, score=-1.726 tagged_above=-999 required=5 tests=[AWL=0.223,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x8huSoz1SvHt for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 23:55:31 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.21]) by ietfa.amsl.com (Postfix) with ESMTP id 2F73011E8089 for <softwires@ietf.org>; Mon, 17 Oct 2011 23:55:28 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2312.sfr.fr (SMTP Server) with ESMTP id 79EBE7000133; Tue, 18 Oct 2011 08:55:27 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2312.sfr.fr (SMTP Server) with ESMTP id 1770D700010C; Tue, 18 Oct 2011 08:55:25 +0200 (CEST)
X-SFR-UUID: 20111018065525961.1770D700010C@msfrf2312.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <4E9C8D5C.4060706@gmail.com>
Date: Tue, 18 Oct 2011 08:55:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B83FCD09-0563-4DC3-ADDC-92E0DAA32030@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <4E9C8D5C.4060706@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] ECN [4rd-U complement - e2e transparency to IPv4 TOS]
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, 18 Oct 2011 06:55:31 -0000

Le 17 oct. 2011 =E0 22:17, Brian E Carpenter a =E9crit :

> On 2011-10-18 01:36, R=E9mi Despr=E9s wrote:
>> Hi Satoru-san,
>>=20
>> Thank you for identifying a limitation of the 4rd-U =20
>> You are right, as currently specified, "it doesn't support diff-serv =
tunneling model, pipe and short-pipe".
>> All these need e2e transparency to the IPv4 Type of Service.
>>=20
>> Fortunately, this is easy to fix:

*
>> in the Identification field of the IPv6 Fragment header, copy not =
only the DF bits but also the IPv4 TOS.
*

> Will this cause any difficulties for ECN, if ECN is supported on the =
IPv6
> leg of the journey?

Not in my understanding.
Since the IPv4 TOS is copied in the Identification field of the IPv6 =
Fragment header, it will be restored at exit of the IPv6 leg =
independently of any MPLS and ECN that may be used in that leg.
=20
> Apart from that, please remember that the DSCP part of the DS Field is =
not an
> end-to-end field; it is mutable.

> I advise applying the relevant considerations
> from Sections 4.1 and 5.1 of RFC 6145.

This isn't necessary because RFC 6145 is about Translation, while 4rd-U, =
with the above between asterisks, precisely avoids translations between =
IPv4 TOS and IPv6 Traffic.=20
In this respect, is more like 4rd Encapsulation than like 4rd =
Translation.


Regards,
RD




=20
>=20
> Regards
>   Brian Carpenter
>=20
>=20
>=20

From despres.remi@laposte.net  Tue Oct 18 00:15:44 2011
Return-Path: <despres.remi@laposte.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 24EA921F848B for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 00:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.743
X-Spam-Level: 
X-Spam-Status: No, score=-1.743 tagged_above=-999 required=5 tests=[AWL=0.206,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TizqrFgp8Vvd for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 00:15:43 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.21]) by ietfa.amsl.com (Postfix) with ESMTP id B3EA31F0C72 for <softwires@ietf.org>; Tue, 18 Oct 2011 00:15:40 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2312.sfr.fr (SMTP Server) with ESMTP id BC57A7000167; Tue, 18 Oct 2011 09:15:39 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2312.sfr.fr (SMTP Server) with ESMTP id 8027D7000172; Tue, 18 Oct 2011 09:15:39 +0200 (CEST)
X-SFR-UUID: 20111018071539525.8027D7000172@msfrf2312.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <3D30CA78-9268-4CAB-AADE-7DD9E30DE6D8@employees.org>
Date: Tue, 18 Oct 2011 09:15:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF86D754-BF12-4F44-A9DD-93112B0B38DF@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <542B93F7-F8E1-4E2B-BEB9-CF8196BAAB45@employees.org> <C0590740-D4FC-4BF7-8AD6-BB77E2668479@laposte.net> <3D30CA78-9268-4CAB-AADE-7DD9E30DE6D8@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 07:15:44 -0000

Ole,

Le 17 oct. 2011 =E0 19:34, Ole Troan a =E9crit :

> Remi,
>=20
>>>>> how is 4rd-U different from translation?
>>>>=20
>>>> Functionally, full network transparency to DF bit (and TOS with the =
complement that was missing).
>>>> Technically, see for instance Figure 1 of the draft.
>>>=20
>>> I thought the dIVI guys presented the DF bit transparency during the =
Beijing meeting?
>>=20
>> They did, but AFAIK not as completely as section 1 of my draft.
>>=20
>>=20
>>> I don't understand what the difference between "IP data" and =
Transport is in figure 1.
>>=20
>> IP data is, as shown in my Figure 1, everything after the IPv4 =
header:
>>            +----------------+  =20
>>            |   IPv4 Header  |   =20
>>            +----------------+        =20
>>            |    IP Data     |        =20
>>            +----------------+         =20
>>=20
>> Transport header is as in Figure 2 of RFC 6145:
>>=20
>>             +-------------+                 +-------------+
>>             |    IPv4     |                 |    IPv6     |
>>             |   Header    |                 |   Header    |
>>             +-------------+                 +-------------+
>>             |  Transport- |                 |  Fragment   |
>>             |   Layer     |      =3D=3D=3D>       |   Header    |
>>             |   Header    |                 | (if needed) |
>>             +-------------+                 +-------------+
>>             |             |                 |  Transport- |
>>             ~    Data     ~                 |   Layer     |
>>             |             |                 |   Header    |
>>             +-------------+                 +-------------+
>>                                             |             |
>>                                             ~    Data     ~
>>                                             |             |
>>                                             +-------------+           =
                                =20
>>=20
>> May I suggest that you re-read RFC 6145, and thus understand all what =
becomes unnecessary with 4rd-U :-).
>>=20
>>=20
>>> consider me slow, but don't you still either have to update the =
transport checksum, or adjust the checksum with other changes in the =
IPv6 header, e.g. flow.
>>=20
>> None of this is needed (this is where 4rd-U has in common with =
4rd-Encap).
>=20
> I thought we agreed that we didn't want to create packets with invalid =
checksums.

Which agreement, reported where?
In any case, for traversing an IPv6-only ISP network, I can't see why it =
would be a useful constraint.

> this could trivially be made checksum neutral though.

If one more proposal would be documented, we would see what you mean =
but, IMHO, the three approaches on the table are sufficient.

> in any case I thought this was exactly what dIVI did already...

Reality is different from what you thought because dIVI-pd is based on =
RFC 6145 and RFC 6052, and:
- RFC 6052 address formats ar NOT checksum neutral (sec 4.1)
- Sec 4.5 of RFC 6145 says:
"If the address translation algorithm is not checksum neutral (see =
Section 4.1 of [RFC6052]), the recalculation and updating of the =
transport-layer headers that contain pseudo-headers need to be =
performed."=20


Let me now ask whether you challenge any of the following:
a) One standard is better than two.
b) Maintaining network transparency to IPv4 packets is a useful feature
c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with ACLs, =
is a useful feature
d) Encapsulation has b) but not c)
e) Double translation has c) but not b)
f) 4rd-U has both b) and c)

- If you challenge one or several of these, our debate can continue on =
well identified subjects.
- If you don't challenge any of a) to f), we are IMHO on the right track =
to make progress.

Please do answer these questions so that questions you ask me can be =
answered in a clarified context.

Cheers,
RD



RD


>=20
> cheers,
> Ole
>=20
> cheers,
> Ole

From ichiroumakino@gmail.com  Tue Oct 18 00:42:46 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 DEA2721F8B45 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 00:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.329
X-Spam-Level: 
X-Spam-Status: No, score=-3.329 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JvWB3fy02ATP for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 00:42:46 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id C3E3121F86FF for <softwires@ietf.org>; Tue, 18 Oct 2011 00:42:45 -0700 (PDT)
Received: by wwe6 with SMTP id 6so267164wwe.13 for <softwires@ietf.org>; Tue, 18 Oct 2011 00:42:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=WLpQwzbynqjkEmnDddH3cfd3Kbbe9/X9idDcxbMcFfw=; b=u6yjzevWfD4Cqwd1iuNytbrHTHv6xrx47/PS3IQuNK2XJXMjAM4pWSlNrqs7zwymwY wO1YtjeXXjRtAK4zvGwVAwJsxqB/7XpcKlyxvK8+Zzk9epueChTHnOSC5lO2dCZ36sql QJNlTn07fvRUDNmSAMzrWAw4NpRD/n6HvveaQ=
Received: by 10.227.55.5 with SMTP id s5mr428613wbg.92.1318923763656; Tue, 18 Oct 2011 00:42:43 -0700 (PDT)
Received: from dhcp-osl-vl300-64-103-53-235.cisco.com (dhcp-osl-vl300-64-103-53-235.cisco.com. [64.103.53.235]) by mx.google.com with ESMTPS id ek13sm1913491wbb.3.2011.10.18.00.42.42 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Oct 2011 00:42:42 -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: <BF86D754-BF12-4F44-A9DD-93112B0B38DF@laposte.net>
Date: Tue, 18 Oct 2011 09:42:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C036D7AF-9005-4032-AE74-52D5B62570C6@employees.org>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <542B93F7-F8E1-4E2B-BEB9-CF8196BAAB45@employees.org> <C0590740-D4FC-4BF7-8AD6-BB77E2668479@laposte.net> <3D30CA78-9268-4CAB-AADE-7DD9E30DE6D8@employees.org> <BF86D754-BF12-4F44-A9DD-93112B0B38DF@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 07:42:47 -0000

Remi,

> Let me now ask whether you challenge any of the following:
> a) One standard is better than two.
> b) Maintaining network transparency to IPv4 packets is a useful =
feature
> c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with ACLs, =
is a useful feature

I think we need to detail this point more:

c1) apply IPv6 features on the traffic as if it is IPv6. use of 5 tuple =
etc.
c2) apply IPv4 features on the traffic as if it is IPv4.
c3) be able to redirect traffic or communicate with native IPv6 only =
hosts. e.g. web cache, web authentication

if this is useful or not, depends on your world view...
traditionally the whole purpose of a tunnel was to bypass devices in the =
middle mingling with your packets.

_iff_ one wishes that a "legacy" router in the middle of the traffic =
path should be able to apply features and classifiers
based on 5 tuple, then translation supports c1 and c3.
encapsulation supports none.
what I hear on the list is that one don't want to treat this as IPv6 =
traffic, but want to be able to identify it as IPv4 traffic. and =
presumably apply IPv4 features and classifiers on that traffic. if =
that's the case, you need to modify the box in the middle anyway, and I =
would claim it is a lot easier to move a pointer 40 bytes, than to =
recreate the IPv4 header on the fly.

> d) Encapsulation has b) but not c)
> e) Double translation has c) but not b)
> f) 4rd-U has both b) and c)

I disagree. double translation has just as much of b) as 4rd-U has. but =
I will claim that double translation offers less
transparency than encapsulation.

> - If you challenge one or several of these, our debate can continue on =
well identified subjects.
> - If you don't challenge any of a) to f), we are IMHO on the right =
track to make progress.
>=20
> Please do answer these questions so that questions you ask me can be =
answered in a clarified context.

in my view this doesn't change the encapsulation versus translation =
debate.
would an option be to merge your ideas with the new dIVI-pd document =
that will reference the new mapping document?

cheers,
Ole


From despres.remi@free.fr  Tue Oct 18 00:44:07 2011
Return-Path: <despres.remi@free.fr>
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 ACDF821F8B52 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 00:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.149
X-Spam-Level: 
X-Spam-Status: No, score=-1.149 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_FROM=2.3, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BL0Lyi6ZprZA for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 00:44:07 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id D296C21F8B54 for <softwires@ietf.org>; Tue, 18 Oct 2011 00:44:05 -0700 (PDT)
Received: from [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb] (unknown [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb]) by smtp1-g21.free.fr (Postfix) with ESMTP id 53E0A9400B1; Tue, 18 Oct 2011 09:43:58 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-5--833262766
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@free.fr>
In-Reply-To: <CAFUBMqWvuWCfU9Gw7YpThAeB2fk1sQ-kV4SD6XEVnHBtdb1W2w@mail.gmail.com>
Date: Tue, 18 Oct 2011 09:43:57 +0200
Message-Id: <AB772D3A-1BD9-4FE4-B69E-5DEDA294A9B0@free.fr>
References: <F259BF79-B3C9-4434-AAC4-9F84B8D9A0FA@laposte.net> <CAM+vMER2CBTpYOhcu63th7AJejCJ4sv0_GqeiZmwHVHEEeW1WA@mail.gmail.com> <0C2B5428-98D4-4F67-B18D-9ACA946A68E7@laposte.net> <CABv173VeFd5DVLm5XvX5+PTgW2biQpUCnW=Z7EXHj7EDG-5LUg@mail.gmail.com> <CAM+vMERXwqJWobpUsk=Pq6OkubBSCc8QFdNsRgMSyzf+1e8SgQ@mail.gmail.com> <CAFUBMqVkMQ89tffeGcBT5mJpz56mrvabe0pjdiJ-ia7XfoVhYw@mail.gmail.com> <CABv173U4wOBYBjM+kaCfHM1ksNPSk1WW_JvMTf1Y1=b_-X=jrg@mail.gmail.com> <CAM+vMETVf763VWLLCHy072NcHTi0v=cMOyjQ+u2HHa5SwiFF_A@mail.gmail.com> <CAFUBMqX01bLG4Rkn=zvT9o4Q4UF3sGCqEGd7AD0aW-ZkC9AS6w@mail.gmail.com> <CAM+vMET5J4XVbrKR9zdHXN8LqhBYJ=psYMoSXBNFzwZVUkE0YA@mail.gmail.com> <14AB4609-752F-44E2-BE75-EB414CC2ACFA@ipinfusion.com> <CAFUBMqVni_GNqmEx-FwzNUKUD1x2hN=xoe7Zc9pre4rfmGBWRw@mail.gmail.com> <C87E17E8-8686-4D01-939E-E6C7C3E5DF58@free.fr> <CAFUBMqWvuWCfU9Gw7YpThAeB2fk1sQ-kV4SD6XEVnHBtdb1W2w@mail.gmail.com>
To: Maoke <fibrib@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation
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, 18 Oct 2011 07:44:07 -0000

--Apple-Mail-5--833262766
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 18 oct. 2011 =E0 04:37, Maoke a =E9crit :

> hi Remi,=20
>=20
> 2011/10/18 R=E9mi Despr=E9s <despres.remi@free.fr>
> Hi Maoke,
>=20
> On 2011/10/12, you wrote:
> "... considering the double translation is a case of translation. it =
is possible that a src host with an IPv4-translatable IPv6 address =
generates a fragment header with a 32-bit identifier happening to have =
the first 16 bit as either 0x8000 or 0x0000, making a fake D bit in your =
current proposal."
>=20
> An important point is that the IP identifier needs to be unique ONLY =
for each <SRC, DST> pair.
> If 4rd addresses are deterministically recognizable (with the V octet =
in bits 64-71), there is no risk of confusion with an IP identification =
generated for another purpose than 4rd.
>=20
> thus i understand. then you didn't try to decouple the header =
processing from the mapping algorithm, right? sorry but i was confused =
here. :P

The 4rd-U header format builds on a useful property of the address =
mapping algorithm, the fact that <SRC, DST> pairs of 4rd packets are =
distinguishable from those of native IPv6 packets.
Other than that, it doesn't depend on any particular address mapping.=20

With RFC 6052, for instance, addresses that have the well-known or =
network-specific prefixes are recognizable as being IPv4-embedded =
addresses? They are therefore compatible with the 4rd-U header format. =
(It remains that the V octet is AFAIK easier for O&M, and permits to =
have the same CE IPv6 prefix for native IPv6 and embedded IPv4, a useful =
property for some use cases).

I should have made this clearer, thanks for your remark.=20

Cheers,
RD=

--Apple-Mail-5--833262766
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 18 oct. 2011 =E0 04:37, Maoke a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>hi =
Remi,&nbsp;</div><br><div class=3D"gmail_quote">2011/10/18 R=E9mi =
Despr=E9s <span dir=3D"ltr">&lt;<a =
href=3D"mailto:despres.remi@free.fr">despres.remi@free.fr</a>&gt;</span><b=
r><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto; ">
<div style=3D"word-wrap:break-word">Hi Maoke,<div><br><div><div>On =
2011/10/12, you wrote:</div></div><div>"...&nbsp;<span =
style=3D"font-family:monospace">considering the double translation is a =
case of translation. it&nbsp;is possible that&nbsp;a src host with an =
IPv4-translatable IPv6 address&nbsp;generates a fragment header with a =
32-bit identifier happening to have&nbsp;the first 16 bit as either =
0x8000 or 0x0000,&nbsp;making a fake D bit in your&nbsp;current =
proposal."</span></div>
<div><span style=3D"font-family:monospace"><br></span></div><div><font =
face=3D"monospace">An important point is that the IP identifier needs to =
be unique ONLY for each &lt;SRC, DST&gt; =
pair.</font></div></div><div><font face=3D"monospace">If 4rd addresses =
are deterministically recognizable (with the V octet in bits 64-71), =
there is no risk of confusion with an IP identification generated for =
another purpose than 4rd.</font></div>
</div></blockquote><div><br></div><div>thus i understand. then you =
didn't try to decouple the header processing from the mapping algorithm, =
right? sorry but i was confused here. =
:P</div></div></blockquote><br></div><div>The 4rd-U header format builds =
on a useful property of the address mapping algorithm, the fact =
that&nbsp;<span class=3D"Apple-style-span" style=3D"font-family: =
monospace; ">&lt;SRC, DST&gt; pairs</span>&nbsp;of&nbsp;4rd =
packets&nbsp;are distinguishable from those of native IPv6 =
packets.</div><div>Other than that, it doesn't depend on any particular =
address mapping.&nbsp;</div><div><br></div><div>With RFC 6052, for =
instance, addresses that have the&nbsp;well-known =
or&nbsp;network-specific prefixes are recognizable as being =
IPv4-embedded addresses? They are therefore compatible with the 4rd-U =
header format. (It remains that the V octet is AFAIK easier for O&amp;M, =
and permits to have the same CE IPv6 prefix for native IPv6 and embedded =
IPv4, a useful property for some use cases).</div><div><br></div><div>I =
should have made this clearer, thanks for your =
remark.&nbsp;</div><div><br></div><div>Cheers,</div><div>RD</div></body></=
html>=

--Apple-Mail-5--833262766--

From mark@townsley.net  Tue Oct 18 01:22:04 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 2270D21F8BF9 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 01:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level: 
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJopqFMZWTVa for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 01:22:02 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id A7FFA21F8C0B for <softwires@ietf.org>; Tue, 18 Oct 2011 01:22:00 -0700 (PDT)
Received: by wwe6 with SMTP id 6so300453wwe.13 for <softwires@ietf.org>; Tue, 18 Oct 2011 01:21:59 -0700 (PDT)
Received: by 10.227.38.200 with SMTP id c8mr464777wbe.113.1318926119750; Tue, 18 Oct 2011 01:21:59 -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 gd6sm2110142wbb.1.2011.10.18.01.21.55 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Oct 2011 01:21:56 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-50--830985672
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net>
Date: Tue, 18 Oct 2011 10:21:54 +0200
Message-Id: <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 08:22:04 -0000

--Apple-Mail-50--830985672
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


While it is interesting to explore the various design spaces, we do not =
need more ways to munge an IPv4 packet into an IPv6 packet and back to =
an IPv4 packet. Any alternative beyond the simple and obvious =
encap/decap that routers have used for decades is already too much IMHO, =
we certainly don't need a 3rd or 4th method. Let's please curtail new =
the inventions, and get back to the standardization. =20

- Mark

On Oct 17, 2011, at 7:10 PM, R=E9mi Despr=E9s wrote:

> Hi Behcet,
>=20
> 4rd-U translates addresses, but:
> - isn't concerned with anything above the IP layer;
> - has a way to convey fields of IPv4 that would be lost in IPv6 (DF =
and, for "pipe and short pipe" as discussed by Satoru-san, the TOS).=20
> 4rd-T translates addresses, AND:
> - is concerned with the IPv4 payload (possible checksum adjustment)
> - isn't fully transparent to DF, and to the TOS if a specific IPv6 =
Traffic class is needed for IPv6-domain traversal.
>=20
> Hope it clarifies why, IMHO, calling 4rd-u a double-translation =
solution, like the RFC6145-based double translation, would create =
confusion.
> If you look for a name, what about "header mapping"=20
>=20
> Regards,
> RD
>=20
>  =20
>=20
> Le 17 oct. 2011 =E0 18:41, Behcet Sarikaya a =E9crit :
>=20
>> the idea of 4rd-U is to map IPv4 headers into IPv6 headers
>>=20
>> address translation is called address derivation.
>>=20
>> Isn't this translation?
>>=20
>> regards,
>>=20
>> Behcet
>>=20
>> On Mon, Oct 17, 2011 at 11:26 AM, R=E9mi Despr=E9s =
<despres.remi@laposte.net> wrote:
>>=20
>> Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :
>>=20
>> > Remi,
>> >
>> > how is 4rd-U different from translation?
>>=20
>> Functionally, full network transparency to DF bit (and TOS with the =
complement that was missing).
>> Technically, see for instance Figure 1 of the draft.
>>=20
>> Cheers,
>> RD
>>=20
>>=20
>> >
>> > cheers,
>> > Ole
>> >
>> >
>> > On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:
>> >
>> >>
>> >> Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :
>> >>
>> >>> On 2011/10/17, at 23:46, Maoke wrote:
>> >>>
>> >>>> hi Satoru-san,
>> >>>>
>> >>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>> >>>> Hi Maoke-san,
>> >>>>
>> >>>> On 2011/10/17, at 22:30, Maoke wrote:
>> >>>>
>> >>>>> hi Satoru-san,
>> >>>>>
>> >>>>> may i understand that, as Remi's proposal is applied for the =
double translation case, TTL being translated to IPv6 Hop Limit is =
enough? as is stated in RFC6145, translator is a "router" and therefore =
the behavior should not be as same as the virtual link. right?
>> >>>>
>> >>>> If so, just double translation is enough for that.
>> >>>>
>> >>>> it sounds nice. what i would like to have is a consistent header =
processing for single/double translations and encapsulation.
>> >>>
>> >>> I think that encapsulation and double translation can't be =
consistent to processing packet at all.
>> >>
>> >> 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.
>> >> It is believed to have advantages over both of them.
>> >> Disadvantages has AFAIK still to be identified.
>> >>
>> >>
>> >>>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment =
header but not anything more unless really necessary)?
>> >>>>
>> >>>> can i understand that the following requirements are exclusive =
to each other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?
>> >>>
>> >>> I think that these are exclusive.
>> >>
>> >> Indeed, one cant't do both simultaneously, but AFAIK either choice =
is acceptable.
>> >> Is there one you prefer, for which reason?
>> >>
>> >>>> RFC6145 has defined TTL<->HopLimit translation. then how about =
using another reserved bit, say EF, in the fragment header for =
indicating the mode? if EF =3D 1, it is encapsulation mode, and =
therefore the HopLimit in the base header keeps unchanged untile being =
translated back to IPv4; if EF =3D 0, it is translation mode, and the =
HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.
>> >>>
>> >>> It seems that adding new semantics more. Very creative, but is it =
really needed even we already have both encaps and translation? When you =
want to define more new semantics, it would be better you define new =
protocol number for 4rd-U.
>> >>
>> >> The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.
>> >>
>> >> A key advantage of Double translation over Encapsulation, is that =
the IPv6 next header is the same as the Protocol of the conveyed IPv4 =
packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.
>> >>
>> >>>> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
>> >>>>
>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>     |Vers=3D6 |   TrafClass   |            Flow Label            =
     |
>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>     |         Payload Length        |Next Header=3D44 |   Hop =
Limit   |
>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>     |                                                            =
   |
>> >>>>     +                                                            =
   +
>> >>>>     |                                                            =
   |
>> >>>>     +                  IPv6 Source Address                       =
   +
>> >>>>     |                                                            =
   |
>> >>>>     +                                                            =
   +
>> >>>>     |                                                            =
   |
>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>     |                                                            =
   |
>> >>>>     +                                                            =
   +
>> >>>>     |                                                            =
   |
>> >>>>     +                IPv6 Destination Address                    =
   +
>> >>>>     |                                                            =
   |
>> >>>>     +                                                            =
   +
>> >>>>     |                                                            =
   |
>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>     |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>     |      0        |     TOS       |       IPv4 Identification  =
   |
>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>     |                        IPv4 Payload                        =
   |
>> >>>>     |                                                            =
   |
>> >>>> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
>> >>>>
>> >>>> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
>> >>>>
>> >>>> how do you think?
>> >>>
>> >>> IMHO, I'm not sure it is good idea to change the semantics of the =
IPv6 fragment. If a router receives 4rd-U packets, which router doesn't =
understand 4rd-U, processing these packets as fragmented packets could =
cause problem that sounds buffer exhaust attack.
>> >>
>> >> I don't see that:
>> >> - IPv6 routers are not concerned with fragmentation.
>> >> - the 4rd-U endpoint doesn't need to keep anything in a reassembly =
buffer if a conveyed IPv4 packet is completely contained in a single =
IPv6 packet.
>> >>
>> >>> And I also think that if we need to add new semantics even we can =
utilize IPv6 fragment, it would be better to define new protocol number =
for 4rd-U.
>> >>
>> >> See above why a new protocol number wouldn't be workable.
>> >>
>> >>> However, I don't think that we need to request to define it, =
because existing encapsulation and translation can be utilized for each =
appropriate situation.
>> >>
>> >>
>> >>
>> >> The point isn't to prevent any ISP from deploy for its own use any =
design that works.
>> >>
>> >> Yet, having only ONE STANDARD for a given need is better than =
several.
>> >> I hope you can agree with that.
>> >> (In this case, the need is stateless support of residual IPv4 =
across IPv6-only networks.)
>> >>
>> >> AFAIK, 4rd-U is better for this than double translation (say =
4rd-T), and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E).
>> >> If you still believe this is not right, an explanation will of =
course be welcome.
>> >>
>> >> Cheers,
>> >> RD
>> >>
>> >>
>> >>
>> >>
>> >>>
>> >>> cheers,
>> >>> --satoru
>> >>>
>> >>>
>> >>>>
>> >>>> cheers,
>> >>>> maoke
>> >>>>
>> >>>> cheers,
>> >>>> --satoru
>> >>>>
>> >>>>> regards,
>> >>>>> maoke
>> >>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>> >>>>> Hi Remi-san,
>> >>>>>
>> >>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>> >>>>>> It can make IMHO a valuable unified standard.
>> >>>>>
>> >>>>> Not enough. The original TTL value in IPv4 header must be =
carried.
>> >>>>>
>> >>>>> cheers,
>> >>>>> --satoru
>> >>>>>
>> >>>>>
>> >>>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>> >>>>>
>> >>>>>> Hi Satoru-san,
>> >>>>>>
>> >>>>>> Thank you for identifying a limitation of the 4rd-U
>> >>>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
>> >>>>>> All these need e2e transparency to the IPv4 Type of Service.
>> >>>>>>
>> >>>>>> Fortunately, this is easy to fix: in the Identification field =
of the IPv6 Fragment header, copy not only the DF bits but also the IPv4 =
TOS.
>> >>>>>>
>> >>>>>> The proposed 4r-U packet format becomes:
>> >>>>>>
>> >>>>>>
>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>>> |Vers=3D6 |   TrafClass   |            Flow Label              =
   |
>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>>> |         Payload Length        |Next Header=3D44 |   Hop =
Limit   |
>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>>> |                                                              =
 |
>> >>>>>> +                                                              =
 +
>> >>>>>> |                                                              =
 |
>> >>>>>> +                  IPv6 Source Address                         =
 +
>> >>>>>> |                                                              =
 |
>> >>>>>> +                                                              =
 +
>> >>>>>> |                                                              =
 |
>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>>> |                                                              =
 |
>> >>>>>> +                                                              =
 +
>> >>>>>> |                                                              =
 |
>> >>>>>> +                IPv6 Destination Address                      =
 +
>> >>>>>> |                                                              =
 |
>> >>>>>> +                                                              =
 +
>> >>>>>> |                                                              =
 |
>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>>> |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 =
|M|
>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>>> |D|      0      |    IPv4 TOS   |       IPv4 Identification    =
 |
>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> >>>>>> |                        IPv4 Payload                          =
 |
>> >>>>>> |                                                              =
 |
>> >>>>>>
>> >>>>>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>> >>>>>> It can make IMHO a valuable unified standard.
>> >>>>>>
>> >>>>>> Yet, I may have missed something else.
>> >>>>>> New justified objections are therefore most welcome..
>> >>>>>>
>> >>>>>>
>> >>>>>> Regards,
>> >>>>>> RD
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> Softwires mailing list
>> >>>>> Softwires@ietf.org
>> >>>>> https://www.ietf.org/mailman/listinfo/softwires
>> >>>>>
>> >>>>
>> >>>>
>> >>>
>> >>
>> >> _______________________________________________
>> >> Softwires mailing list
>> >> Softwires@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/softwires
>> >
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


--Apple-Mail-50--830985672
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div>While it is interesting to explore the various =
design spaces, we do not need more ways to munge an IPv4 packet into an =
IPv6 packet and back to an IPv4 packet. Any alternative beyond the =
simple and obvious encap/decap that routers have used for decades is =
already too much IMHO, we certainly don't need a 3rd or 4th method. =
Let's please curtail new the inventions, and get back to the =
standardization. &nbsp;</div><div><br></div><div>- =
Mark</div><br><div><div>On Oct 17, 2011, at 7:10 PM, R=E9mi Despr=E9s =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">Hi =
Behcet,<div><br></div><div>4rd-U translates addresses, but:<div>- isn't =
concerned with anything above the IP layer;</div><div>- has a way to =
convey fields of IPv4 that would be lost in IPv6 (DF and, for "pipe and =
short pipe" as discussed by Satoru-san, the =
TOS).&nbsp;</div><div><div>4rd-T translates addresses, AND:</div><div>- =
is concerned with the IPv4 payload (possible checksum =
adjustment)</div><div>- isn't fully transparent to DF, and to the TOS if =
a specific IPv6 Traffic class is needed for IPv6-domain =
traversal.</div><div><br></div><div>Hope it clarifies why, IMHO, calling =
4rd-u a double-translation solution, like the RFC6145-based double =
translation, would create confusion.</div><div>If you look for a name, =
what about "header =
mapping"&nbsp;</div><div><br></div><div>Regards,</div><div>RD</div><div><b=
r></div><div>&nbsp;&nbsp;</div><div><br><div><div>Le 17 oct. 2011 =E0 =
18:41, Behcet Sarikaya a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">the idea =
of 4rd-U is to map IPv4 headers into IPv6 headers<br><br>address =
translation is called address derivation.<br><br>Isn't this =
translation?<br><br>regards,<br><br>Behcet<br><br><div =
class=3D"gmail_quote">On Mon, Oct 17, 2011 at 11:26 AM, R=E9mi Despr=E9s =
<span dir=3D"ltr">&lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :<br>
<div class=3D"im"><br>
&gt; Remi,<br>
&gt;<br>
&gt; how is 4rd-U different from translation?<br>
<br>
</div>Functionally, full network transparency to DF bit (and TOS with =
the complement that was missing).<br>
Technically, see for instance Figure 1 of the draft.<br>
<br>
Cheers,<br>
<font color=3D"#888888">RD<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
&gt;<br>
&gt; cheers,<br>
&gt; Ole<br>
&gt;<br>
&gt;<br>
&gt; On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 2011/10/17, at 23:46, Maoke wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; hi Satoru-san,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 2011/10/17 Satoru Matsushima &lt;<a =
href=3D"mailto:satoru.matsushima@gmail.com">satoru.matsushima@gmail.com</a=
>&gt;<br>
&gt;&gt;&gt;&gt; Hi Maoke-san,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 2011/10/17, at 22:30, Maoke wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; hi Satoru-san,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; may i understand that, as Remi's proposal is =
applied for the double translation case, TTL being translated to IPv6 =
Hop Limit is enough? as is stated in RFC6145, translator is a "router" =
and therefore the behavior should not be as same as the virtual link. =
right?<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; If so, just double translation is enough for that.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; it sounds nice. what i would like to have is a =
consistent header processing for single/double translations and =
encapsulation.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that encapsulation and double translation can't be =
consistent to processing packet at all.<br>
&gt;&gt;<br>
&gt;&gt; 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.<br>
&gt;&gt; It is believed to have advantages over both of them.<br>
&gt;&gt; Disadvantages has AFAIK still to be identified.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; can we keep the TTL of IPv4 in the IPv6 header (plus =
fragment header but not anything more unless really necessary)?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; can i understand that the following requirements are =
exclusive to each other: (a) we want to keep TTL changed in the IPv6 =
domain as the behavior of translation; (b) we want to keep TTL not =
changed until leaving the IPv6 domain as the behavior of encapsulation =
(4rd-U)?<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that these are exclusive.<br>
&gt;&gt;<br>
&gt;&gt; Indeed, one cant't do both simultaneously, but AFAIK either =
choice is acceptable.<br>
&gt;&gt; Is there one you prefer, for which reason?<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; RFC6145 has defined TTL&lt;-&gt;HopLimit translation. =
then how about using another reserved bit, say EF, in the fragment =
header for indicating the mode? if EF =3D 1, it is encapsulation mode, =
and therefore the HopLimit in the base header keeps unchanged untile =
being translated back to IPv4; if EF =3D 0, it is translation mode, and =
the HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; It seems that adding new semantics more. Very creative, but =
is it really needed even we already have both encaps and translation? =
When you want to define more new semantics, it would be better you =
define new protocol number for 4rd-U.<br>

&gt;&gt;<br>
&gt;&gt; The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.<br>
&gt;&gt;<br>
&gt;&gt; A key advantage of Double translation over Encapsulation, is =
that the IPv6 next header is the same as the Protocol of the conveyed =
IPv4 packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.<br>

&gt;&gt;<br>
&gt;&gt;&gt;&gt; thus i'd like to suggest that one as follows, based on =
Remi's complement, where E is the indicator of encapsulation mode. =
copying TOS in the fragment header is fine because it doesn't impact the =
IPv6 dst (of single translation) getting the original IPv4 src's =
relative identification.<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; |Vers=3D6 | &nbsp; TrafClass &nbsp; | =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Flow Label &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; Payload =
Length &nbsp; &nbsp; &nbsp; &nbsp;|Next Header=3D44 | &nbsp; Hop Limit =
&nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;IPv6 Source Address &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;IPv6 Destination Address &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp;Next Header &nbsp;| &nbsp; =
Reserved &nbsp; &nbsp;| IPv6 &nbsp;Fragment Offset &nbsp; |E|D|M|<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp; =
&nbsp; &nbsp;| &nbsp; &nbsp; TOS &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; =
&nbsp; IPv4 Identification &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IPv4 Payload &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; unfortunately, however, even we free the first bit of =
IPv6 identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; the problem of EF in fragment header is, it requires =
that the implementation process fragment header before descreasing the =
HopLimit. is it feasible?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; how do you think?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; IMHO, I'm not sure it is good idea to change the semantics =
of the IPv6 fragment. If a router receives 4rd-U packets, which router =
doesn't understand 4rd-U, processing these packets as fragmented packets =
could cause problem that sounds buffer exhaust attack.<br>

&gt;&gt;<br>
&gt;&gt; I don't see that:<br>
&gt;&gt; - IPv6 routers are not concerned with fragmentation.<br>
&gt;&gt; - the 4rd-U endpoint doesn't need to keep anything in a =
reassembly buffer if a conveyed IPv4 packet is completely contained in a =
single IPv6 packet.<br>
&gt;&gt;<br>
&gt;&gt;&gt; And I also think that if we need to add new semantics even =
we can utilize IPv6 fragment, it would be better to define new protocol =
number for 4rd-U.<br>
&gt;&gt;<br>
&gt;&gt; See above why a new protocol number wouldn't be workable.<br>
&gt;&gt;<br>
&gt;&gt;&gt; However, I don't think that we need to request to define =
it, because existing encapsulation and translation can be utilized for =
each appropriate situation.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The point isn't to prevent any ISP from deploy for its own use =
any design that works.<br>
&gt;&gt;<br>
&gt;&gt; Yet, having only ONE STANDARD for a given need is better than =
several.<br>
&gt;&gt; I hope you can agree with that.<br>
&gt;&gt; (In this case, the need is stateless support of residual IPv4 =
across IPv6-only networks.)<br>
&gt;&gt;<br>
&gt;&gt; AFAIK, 4rd-U is better for this than double translation (say =
4rd-T), and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&amp;M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E).<br>

&gt;&gt; If you still believe this is not right, an explanation will of =
course be welcome.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; RD<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt; maoke<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; regards,<br>
&gt;&gt;&gt;&gt;&gt; maoke<br>
&gt;&gt;&gt;&gt;&gt; 2011/10/17 Satoru Matsushima &lt;<a =
href=3D"mailto:satoru.matsushima@gmail.com">satoru.matsushima@gmail.com</a=
>&gt;<br>
&gt;&gt;&gt;&gt;&gt; Hi Remi-san,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; With this added, I believe that 4rd-U is a real =
progress over previously proposed Double translation and =
Encapsulation.<br>
&gt;&gt;&gt;&gt;&gt;&gt; It can make IMHO a valuable unified =
standard.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Not enough. The original TTL value in IPv4 header =
must be carried.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On 2011/10/17, at 21:36, R=E9mi Despr=E9s =
wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Satoru-san,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thank you for identifying a limitation of the =
4rd-U<br>
&gt;&gt;&gt;&gt;&gt;&gt; You are right, as currently specified, "it =
doesn't support diff-serv tunneling model, pipe and short-pipe".<br>
&gt;&gt;&gt;&gt;&gt;&gt; All these need e2e transparency to the IPv4 =
Type of Service.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Fortunately, this is easy to fix: in the =
Identification field of the IPv6 Fragment header, copy not only the DF =
bits but also the IPv4 TOS.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; The proposed 4r-U packet format becomes:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; |Vers=3D6 | &nbsp; TrafClass &nbsp; | &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Flow Label &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; Payload Length =
&nbsp; &nbsp; &nbsp; &nbsp;|Next Header=3D44 | &nbsp; Hop Limit &nbsp; =
|<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;IPv6 Source Address &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;IPv6 Destination Address &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp;Next Header &nbsp;| &nbsp; =
&nbsp;Reserved &nbsp; | IPv6 &nbsp;Fragment Offset &nbsp; | 0 |M|<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; |D| &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp; &nbsp;| =
&nbsp; &nbsp;IPv4 TOS &nbsp; | &nbsp; &nbsp; &nbsp; IPv4 Identification =
&nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IPv4 Payload &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; With this added, I believe that 4rd-U is a real =
progress over previously proposed Double translation and =
Encapsulation.<br>
&gt;&gt;&gt;&gt;&gt;&gt; It can make IMHO a valuable unified =
standard.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Yet, I may have missed something else.<br>
&gt;&gt;&gt;&gt;&gt;&gt; New justified objections are therefore most =
welcome..<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Regards,<br>
&gt;&gt;&gt;&gt;&gt;&gt; RD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt;&gt; Softwires mailing list<br>
&gt;&gt;&gt;&gt;&gt; <a =
href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Softwires mailing list<br>
&gt;&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;<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"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</div></div></blockquote></div><br>
=
</blockquote></div><br></div></div></div></div>___________________________=
____________________<br>Softwires mailing list<br><a =
href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>https://www.i=
etf.org/mailman/listinfo/softwires<br></blockquote></div><br></body></html=
>=

--Apple-Mail-50--830985672--

From despres.remi@laposte.net  Tue Oct 18 01:29:42 2011
Return-Path: <despres.remi@laposte.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 374C821F8C6F for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 01:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.458
X-Spam-Level: 
X-Spam-Status: No, score=-1.458 tagged_above=-999 required=5 tests=[AWL=-0.109, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_23=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkXGJocpmb3p for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 01:29:41 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.121]) by ietfa.amsl.com (Postfix) with ESMTP id 5513721F8C6C for <softwires@ietf.org>; Tue, 18 Oct 2011 01:29:41 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2517.sfr.fr (SMTP Server) with ESMTP id ED269700062B; Tue, 18 Oct 2011 10:29:39 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2517.sfr.fr (SMTP Server) with ESMTP id B2E077000628; Tue, 18 Oct 2011 10:29:35 +0200 (CEST)
X-SFR-UUID: 20111018082935732.B2E077000628@msfrf2517.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <C036D7AF-9005-4032-AE74-52D5B62570C6@employees.org>
Date: Tue, 18 Oct 2011 10:29:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CAFA423-A79C-44EB-BE08-F26221FFC350@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <542B93F7-F8E1-4E2B-BEB9-CF8196BAAB45@employees.org> <C0590740-D4FC-4BF7-8AD6-BB77E2668479@laposte.net> <3D30CA78-9268-4CAB-AADE-7DD9E30DE6D8@employees.org> <BF86D754-BF12-4F44-A9DD-93112B0B38DF@laposte.net> <C036D7AF-9005-4032-AE74-52D5B62570C6@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 08:29:42 -0000

Olde,

Thanks for the quick answer.
More below.

Le 18 oct. 2011 =E0 09:42, Ole Troan a =E9crit :

> Remi,
>=20
>> Let me now ask whether you challenge any of the following:
>> a) One standard is better than two.
>> b) Maintaining network transparency to IPv4 packets is a useful =
feature
>> c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with =
ACLs, is a useful feature
>=20
> I think we need to detail this point more:
>=20
> c1) apply IPv6 features on the traffic as if it is IPv6. use of 5 =
tuple etc.
> c2) apply IPv4 features on the traffic as if it is IPv4.
> c3) be able to redirect traffic or communicate with native IPv6 only =
hosts. e.g. web cache, web authentication
>=20
> if this is useful or not, depends on your world view...

I see that, but aren't solutions that are compatible with both world =
views better than those that satisfy only one?

=20
> traditionally the whole purpose of a tunnel was to bypass devices in =
the middle mingling with your packets.
>=20
> _iff_ one wishes that a "legacy" router in the middle of the traffic =
path should be able to apply features and classifiers
> based on 5 tuple, then translation supports c1 and c3.
> encapsulation supports none.
> what I hear on the list is that one don't want to treat this as IPv6 =
traffic, but want to be able to identify it as IPv4 traffic. and =
presumably apply IPv4 features and classifiers on that traffic.

> if that's the case, you need to modify the box in the middle anyway,

The point is that you only need to configure the box, without depending =
on a new product release that hasn't been announced yet.
I think promoters of double translation made clearly this point, and it =
is AFAIK a valid one.
 =20
> and I would claim it is a lot easier to move a pointer 40 bytes, than =
to recreate the IPv4 header on the fly.

Recreating an IPv4 header at domain exit isn't a big deal. IMHO, since =
it is the key to combine valuable features of both double translation =
and encapsulation, and to thus have a single standard, it is worth =
doing.
  =20

>> d) Encapsulation has b) but not c)
>> e) Double translation has c) but not b)
>> f) 4rd-U has both b) and c)
>=20
> I disagree. double translation has just as much of b) as 4rd-U has.

In clear, you claim that 4rd-U isn't more transparent to IPv4 than =
double translation!=20
With its DF+TOS copied in the IPv6 fragment header, 4rd-U is fully =
transparent to the TOS and the DF bit of IPv4, which isn't always the =
case with double translation.
Could you explain your understanding?

> but I will claim that double translation offers less
> transparency than encapsulation.

Indeed (and less than 4rd-U by the same token, see above).


>> - If you challenge one or several of these, our debate can continue =
on well identified subjects.
>> - If you don't challenge any of a) to f), we are IMHO on the right =
track to make progress.
>>=20
>> Please do answer these questions so that questions you ask me can be =
answered in a clarified context.
>=20
> in my view this doesn't change the encapsulation versus translation =
debate.
> would an option be to merge your ideas with the new dIVI-pd document =
that will reference the new mapping document?

It is up to you, as leader of the unified-format effort, to see how you =
would like documents to be merged and/or re-written.

My own understanding is that:
- a unified address mapping is possible, e.g. by modifying the =
4rd-addmapping to incorporate the proposed format with the V octet.
- a unified header format is also possible, based on 4rd-U which has =
been designed for that.=20

I hope others will express their view on this.

Cheers,
RD



> cheers,
> Ole
>=20

From despres.remi@laposte.net  Tue Oct 18 01:59:22 2011
Return-Path: <despres.remi@laposte.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 67E3B21F8C08 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 01:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level: 
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2y86I59tv9ir for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 01:59:22 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.121]) by ietfa.amsl.com (Postfix) with ESMTP id B4F5721F8BF7 for <softwires@ietf.org>; Tue, 18 Oct 2011 01:59:21 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2517.sfr.fr (SMTP Server) with ESMTP id E5F66700062A; Tue, 18 Oct 2011 10:59:20 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2517.sfr.fr (SMTP Server) with ESMTP id BA35870001F2; Tue, 18 Oct 2011 10:59:20 +0200 (CEST)
X-SFR-UUID: 20111018085920762.BA35870001F2@msfrf2517.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net>
Date: Tue, 18 Oct 2011 10:59:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8481586C-8F3D-48C8-A9F6-C05BEFF5C067@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 08:59:22 -0000

Le 18 oct. 2011 =E0 10:21, Mark Townsley a =E9crit :

>=20
> While it is interesting to explore the various design spaces, we do =
not need more ways to munge an IPv4 packet into an IPv6 packet and back =
to an IPv4 packet. Any alternative beyond the simple and obvious =
encap/decap that routers have used for decades is already too much IMHO, =
we certainly don't need a 3rd or 4th method.

> Let's please curtail new the inventions, and get back to the =
standardization.

Sorry that you see it that way.

The interim meeting has been useful in that objectives of present =
parties were clarified better than ever before.
Standardization is, and has always been, a process in which =
understanding each other, and finding ways to accommodate all valid =
concerns, are been key to success.
That's what I have been working for: good standardization.=20

Would you please indicate what you personally challenge in this:
a) One standard is better than two.
b) Maintaining network transparency to IPv4 packets is a useful feature
c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with ACLs, =
is a useful feature
d) Encapsulation has b) but not c)
e) Double translation has c) but not b)
f) 4rd-U has both b) and c)
 =20
Regards,
RD



From mark@townsley.net  Tue Oct 18 02:11:52 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 E46CF21F8783 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 02:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.498
X-Spam-Level: 
X-Spam-Status: No, score=-3.498 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8oUFA3BeS6iu for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 02:11:51 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id AA29521F86A4 for <softwires@ietf.org>; Tue, 18 Oct 2011 02:11:47 -0700 (PDT)
Received: by wwe6 with SMTP id 6so343156wwe.13 for <softwires@ietf.org>; Tue, 18 Oct 2011 02:11:47 -0700 (PDT)
Received: by 10.227.26.10 with SMTP id b10mr582873wbc.22.1318929106754; Tue, 18 Oct 2011 02:11:46 -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 fi11sm2312584wbb.9.2011.10.18.02.11.44 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Oct 2011 02:11:45 -0700 (PDT)
From: Mark Townsley <mark@townsley.net>
Content-Type: multipart/alternative; boundary=Apple-Mail-53--827996734
Date: Tue, 18 Oct 2011 11:11:43 +0200
References: <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net>
To: Softwires WG <softwires@ietf.org>
Message-Id: <1BF1A854-AB42-4756-BC5B-86720C57AFBD@townsley.net>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 09:11:52 -0000

--Apple-Mail-53--827996734
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

(resending as this was bounced from softwires due to the message being =
too long - I removed the thread cc'd at the end)

Begin forwarded message:

> From: Mark Townsley <mark@townsley.net>
> Date: October 18, 2011 11:07:34 AM GMT+02:00
> To: R=E9mi Despr=E9s <despres.remi@laposte.net>
> Cc: sarikaya@ieee.org, Softwires WG <softwires@ietf.org>
> Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 =
TOS
>=20
>=20
> On Oct 18, 2011, at 10:38 AM, R=E9mi Despr=E9s wrote:
>=20
>>=20
>> Le 18 oct. 2011 =E0 10:21, Mark Townsley a =E9crit :
>>=20
>>>=20
>>> While it is interesting to explore the various design spaces, we do =
not need more ways to munge an IPv4 packet into an IPv6 packet and back =
to an IPv4 packet. Any alternative beyond the simple and obvious =
encap/decap that routers have used for decades is already too much IMHO, =
we certainly don't need a 3rd or 4th method.
>>=20
>>> Let's please curtail new the inventions, and get back to the =
standardization.
>>=20
>> Sorry that you see it that way.
>>=20
>> The interim meeting has been useful in that objectives of present =
parties were clarified better than ever before.
>> Standardization is, and has always been, a process in which =
understanding each other, and finding ways to accommodate all valid =
concerns, are been key to success.
>> That's what I have been working for: good standardization.=20
>>=20
>> Would you please indicate what you personally challenge in this:
>> a) One standard is better than two.
>=20
> Yes.=20
>=20
>> b) Maintaining network transparency to IPv4 packets is a useful =
feature
>> c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with =
ACLs, is a useful feature
>> d) Encapsulation has b) but not c)
>> e) Double translation has c) but not b)
>> f) 4rd-U has both b) and c)
>=20
> IPv6 packets with incorrect checksums may be incompatible with =
firewalls, website redirects (e.g. I don't see why the web server will =
not just drop the packet if the checksum fails), etc.=20
>=20
> The translation (or header mapping) cases all purport to be helpful to =
various processing or operations along the path between the router =
endpoints. By definition, it is more complicated to weigh relative value =
of the various options in this space as we have to start weaving our way =
through sometimes unknown and certainly non-standard DPI, ACL, =
redirection, O&M, etc. features at multiple places in the network. In =
some cases, I'm afraid that we are optimizing based on speculative =
properties of IPv6 networks that are still in their infancy in terms of =
mainstream deployment. Experience tells me convergence here will be =
difficult, and getting it right will be even more difficult.=20
>=20
> I think we need to get the base case of stateless encap/decap out the =
door so that it can be built into CPE alongside the stateful ds-lite =
encap/decap option that is being built already. Then we can continue in =
the search for the best translation method (which, if we are still =
coming up with new clever alternatives right now, we are not converging =
nearly as fast as we might think we are).
>=20
> - Mark


--Apple-Mail-53--827996734
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">(resending as this was bounced from softwires due to the message being =
too long - I removed the thread cc'd at the end)<br><div><br><div>Begin =
forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">Mark Townsley =
&lt;<a =
href=3D"mailto:mark@townsley.net">mark@townsley.net</a>&gt;<br></span></di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">October 18, 2011 =
11:07:34 AM GMT+02:00<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">R=E9mi Despr=E9s &lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;<=
br></span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>Cc: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><a =
href=3D"mailto:sarikaya@ieee.org">sarikaya@ieee.org</a>, Softwires WG =
&lt;<a =
href=3D"mailto:softwires@ietf.org">softwires@ietf.org</a>&gt;<br></span></=
div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>Re: [Softwires] =
4rd-U complement - e2e transparency to IPv4 =
TOS</b><br></span></div><br><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 18, 2011, at 10:38 AM, R=E9mi Despr=E9s =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><br><div><div>Le 18 oct. =
2011 =E0 10:21, Mark Townsley a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><br></div><div>While it is =
interesting to explore the various design spaces, we do not need more =
ways to munge an IPv4 packet into an IPv6 packet and back to an IPv4 =
packet. Any alternative beyond the simple and obvious encap/decap that =
routers have used for decades is already too much IMHO, we certainly =
don't need a 3rd or 4th method. </div></div></blockquote><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div>Let's please =
curtail new the inventions, and get back to the =
standardization.</div></div></blockquote><div><br></div>Sorry that you =
see it that way.</div><div><br></div><div>The interim meeting has been =
useful in that objectives of present parties were clarified better than =
ever before.</div><div>Standardization is, and has always been, a =
process in which understanding each other, and finding ways to =
accommodate all valid concerns, are been key to =
success.</div><div>That's what I have been working for: good =
standardization.&nbsp;</div><div><br></div><div>Would you please =
indicate what you personally challenge in this:</div><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; ">a) One =
standard is better than two.</span><span class=3D"Apple-style-span" =
style=3D"font-family: monospace; =
"><br></span></div></blockquote><div><br></div><div>Yes.&nbsp;</div><br><b=
lockquote type=3D"cite"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; ">b) =
Maintaining network transparency to IPv4 packets is a useful =
feature</span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; "><br></span><span class=3D"Apple-style-span" =
style=3D"font-family: monospace; ">c) Being able to apply IPv6 O&amp;M =
tools to IPv4 traffic, e.g. with ACLs, is a useful feature</span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; =
"><br></span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; ">d) Encapsulation has b) but not c)</span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; =
"><br></span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; ">e) Double translation has c) but not b)</span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; =
"><br></span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; ">f) 4rd-U has both b) and c)</span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; =
"><br></span></div></blockquote><div><br></div><div>IPv6 packets with =
incorrect checksums may be incompatible with firewalls, website =
redirects (e.g. I don't see why the web server will not just drop the =
packet if the checksum fails), etc.&nbsp;</div><div><br></div><div>The =
translation (or header mapping) cases all purport to be helpful to =
various processing or operations along the path between the router =
endpoints. By definition, it is more complicated to weigh relative value =
of the various options in this space as we have to start weaving our way =
through sometimes unknown and certainly non-standard DPI, ACL, =
redirection, O&amp;M, etc. features at multiple places in the network. =
In some cases,&nbsp;I'm afraid that we are optimizing based on =
speculative properties of IPv6 networks that are still in their infancy =
in terms of mainstream deployment. Experience tells me convergence here =
will be difficult, and getting it right will be even more =
difficult.&nbsp;</div><div><br></div><div>I think we need to get the =
base case of stateless encap/decap out the door so that it can be built =
into CPE alongside the stateful ds-lite encap/decap option that is being =
built already. Then we can continue in the search for the best =
translation method (which, if we are still coming up with new clever =
alternatives right now, we are not converging nearly as fast as we might =
think we are).</div><div><br></div><div>- =
Mark</div></div></div></blockquote></div><br></body></html>=

--Apple-Mail-53--827996734--

From despres.remi@laposte.net  Tue Oct 18 05:31:10 2011
Return-Path: <despres.remi@laposte.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 233BB21F8509 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 05:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41kP6o41QZSS for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 05:31:09 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 4257221F84B2 for <softwires@ietf.org>; Tue, 18 Oct 2011 05:31:07 -0700 (PDT)
Received: from [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb] (unknown [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb]) by smtp1-g21.free.fr (Postfix) with ESMTP id 8F8D8940293; Tue, 18 Oct 2011 14:31:01 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net>
Date: Tue, 18 Oct 2011 14:31:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F044EAF-A653-499B-86B1-993CA77D1071@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net> <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net> <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 12:31:10 -0000

Thanks, Mark, for the quick and detailed response.
More below.

Le 18 oct. 2011 =E0 11:07, Mark Townsley a =E9crit :

>=20
> On Oct 18, 2011, at 10:38 AM, R=E9mi Despr=E9s wrote:
>=20
>>=20
>> Le 18 oct. 2011 =E0 10:21, Mark Townsley a =E9crit :
>>=20
>>>=20
>>> While it is interesting to explore the various design spaces, we do =
not need more ways to munge an IPv4 packet into an IPv6 packet and back =
to an IPv4 packet. Any alternative beyond the simple and obvious =
encap/decap that routers have used for decades is already too much IMHO, =
we certainly don't need a 3rd or 4th method.
>>=20
>>> Let's please curtail new the inventions, and get back to the =
standardization.
>>=20
>> Sorry that you see it that way.
>>=20
>> The interim meeting has been useful in that objectives of present =
parties were clarified better than ever before.
>> Standardization is, and has always been, a process in which =
understanding each other, and finding ways to accommodate all valid =
concerns, are been key to success.
>> That's what I have been working for: good standardization.=20
>>=20
>> Would you please indicate what you personally challenge in this:
>> a) One standard is better than two.
>=20
> Yes.=20

Clearly an important point for this discussion.


>> b) Maintaining network transparency to IPv4 packets is a useful =
feature
>> c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with =
ACLs, is a useful feature
>> d) Encapsulation has b) but not c)
>> e) Double translation has c) but not b)
>> f) 4rd-U has both b) and c)
>=20
> IPv6 packets with incorrect checksums may be incompatible with =
firewalls, website redirects (e.g. I don't see why the web server will =
not just drop the packet if the checksum fails), etc.=20

Thanks for rising the website-redirect issue.
With 4rd-U, some functions that exploit IPv6 packets above the A+P layer =
are not readily possible, but:
- Some other important functions, like ACLs, are readily made possible =
with existing tools.
- Complementing web redirectors so that they recognize 4rd addresses and =
adapt their checksum processing isn't technically difficult. It can be =
done later on.
- With encapsulation, web redirectors need a CE-like decapsulation =
function before processing IPv4 packets. The same can be done with =
4rd-U, with decapsulation replaced by the v6-to-v4 header mapping.=20


> The translation (or header mapping) cases all purport to be helpful to =
various processing or operations along the path between the router =
endpoints. By definition, it is more complicated to weigh relative value =
of the various options in this space as we have to start weaving our way =
through sometimes unknown and certainly non-standard DPI, ACL, =
redirection, O&M, etc. features at multiple places in the network.

Each ISP will decide which functions it can use, depending on its =
deployed tools, as it does for encapsulation.
 =20

> In some cases, I'm afraid that we are optimizing based on speculative =
properties of IPv6 networks that are still in their infancy in terms of =
mainstream deployment.

> Experience tells me convergence here will be difficult, and getting it =
right will be even more difficult.=20

In the particular instance of 4rd-U, I don't see that, because its =
consequences are easily understood.
If I may, it's somewhat like 6rd whose implications were quickly =
understood by Free, in less than one hour, because the specification is =
short and self contained.
(This is unlike double translation, which depends on the the =
sophisticated RFC 6145, and on its operational variants to configured.)


> I think we need to get the base case of stateless encap/decap out the =
door so that it can be built into CPE alongside the stateful ds-lite =
encap/decap option that is being built already.

That's a respectable view, but one that, IMHO, would lead to a missed =
opportunity to have a single standard.

I do understand the inconvenience of having to adapt running codes based =
on encapsulation to a header mapping such as that of 4rd-U.=20
However, I have no doubt that this is technically easy.
That's AFAIK the price to be paid to get a unique standard, with the =
nice bonus that existing IPv6-ACL tools, which weren't usable with =
encapsulation, become usable.=20

> Then we can continue in the search for the best translation method =
(which, if we are still coming up with new clever alternatives right =
now, we are not converging nearly as fast as we might think we are).

It is clear, I hope, that 4rd-U is NOT a double translation technique =
between IPv4 and IPv6 packets.=20
It is a simple header mapping technique that, like encapsulation, =
preserves network transparency to IPv4 packets across IPv6 domains.

Regards,
RD




From mark@townsley.net  Tue Oct 18 06:36: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 4D87721F85A4 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 06:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.374
X-Spam-Level: 
X-Spam-Status: No, score=-3.374 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZBjlteZbhHL for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 06:36:02 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 337CA21F84B0 for <softwires@ietf.org>; Tue, 18 Oct 2011 06:36:01 -0700 (PDT)
Received: by wwe6 with SMTP id 6so581813wwe.13 for <softwires@ietf.org>; Tue, 18 Oct 2011 06:36:01 -0700 (PDT)
Received: by 10.216.47.11 with SMTP id s11mr273707web.24.1318944961049; Tue, 18 Oct 2011 06:36:01 -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 es5sm3588902wbb.11.2011.10.18.06.35.58 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Oct 2011 06:35:59 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <5F044EAF-A653-499B-86B1-993CA77D1071@laposte.net>
Date: Tue, 18 Oct 2011 15:35:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B52D2A1-9938-48A8-A87C-27DE39405263@townsley.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net> <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net> <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net> <5F044EAF-A653-499B-86B1-993CA77D1071@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 13:36:03 -0000

On Oct 18, 2011, at 2:31 PM, R=E9mi Despr=E9s wrote:

> Thanks, Mark, for the quick and detailed response.
> More below.
>=20
> Le 18 oct. 2011 =E0 11:07, Mark Townsley a =E9crit :
>=20
>>=20
>> On Oct 18, 2011, at 10:38 AM, R=E9mi Despr=E9s wrote:
>>=20
>>>=20
>>> Le 18 oct. 2011 =E0 10:21, Mark Townsley a =E9crit :
>>>=20
>>>>=20
>>>> While it is interesting to explore the various design spaces, we do =
not need more ways to munge an IPv4 packet into an IPv6 packet and back =
to an IPv4 packet. Any alternative beyond the simple and obvious =
encap/decap that routers have used for decades is already too much IMHO, =
we certainly don't need a 3rd or 4th method.
>>>=20
>>>> Let's please curtail new the inventions, and get back to the =
standardization.
>>>=20
>>> Sorry that you see it that way.
>>>=20
>>> The interim meeting has been useful in that objectives of present =
parties were clarified better than ever before.
>>> Standardization is, and has always been, a process in which =
understanding each other, and finding ways to accommodate all valid =
concerns, are been key to success.
>>> That's what I have been working for: good standardization.=20
>>>=20
>>> Would you please indicate what you personally challenge in this:
>>> a) One standard is better than two.
>>=20
>> Yes.=20
>=20
> Clearly an important point for this discussion.
>=20
>=20
>>> b) Maintaining network transparency to IPv4 packets is a useful =
feature
>>> c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with =
ACLs, is a useful feature
>>> d) Encapsulation has b) but not c)
>>> e) Double translation has c) but not b)
>>> f) 4rd-U has both b) and c)
>>=20
>> IPv6 packets with incorrect checksums may be incompatible with =
firewalls, website redirects (e.g. I don't see why the web server will =
not just drop the packet if the checksum fails), etc.=20
>=20
> Thanks for rising the website-redirect issue.
> With 4rd-U, some functions that exploit IPv6 packets above the A+P =
layer are not readily possible, but:
> - Some other important functions, like ACLs, are readily made possible =
with existing tools.
> - Complementing web redirectors so that they recognize 4rd addresses =
and adapt their checksum processing isn't technically difficult. It can =
be done later on.
> - With encapsulation, web redirectors need a CE-like decapsulation =
function before processing IPv4 packets. The same can be done with =
4rd-U, with decapsulation replaced by the v6-to-v4 header mapping.=20
>=20
>=20
>> The translation (or header mapping) cases all purport to be helpful =
to various processing or operations along the path between the router =
endpoints. By definition, it is more complicated to weigh relative value =
of the various options in this space as we have to start weaving our way =
through sometimes unknown and certainly non-standard DPI, ACL, =
redirection, O&M, etc. features at multiple places in the network.
>=20
> Each ISP will decide which functions it can use, depending on its =
deployed tools, as it does for encapsulation.

But collectively, the ISPs will ask for fewer alternatives, particularly =
when the CPE vendor is wrestling with all the variations, and the =
interop lab is multiplying the size of its test matrix.=20

>=20
>=20
>> In some cases, I'm afraid that we are optimizing based on speculative =
properties of IPv6 networks that are still in their infancy in terms of =
mainstream deployment.
>=20
>> Experience tells me convergence here will be difficult, and getting =
it right will be even more difficult.=20
>=20
> In the particular instance of 4rd-U, I don't see that, because its =
consequences are easily understood.
> If I may, it's somewhat like 6rd whose implications were quickly =
understood by Free, in less than one hour, because the specification is =
short and self contained.
> (This is unlike double translation, which depends on the the =
sophisticated RFC 6145, and on its operational variants to configured.)
>=20
>=20
>> I think we need to get the base case of stateless encap/decap out the =
door so that it can be built into CPE alongside the stateful ds-lite =
encap/decap option that is being built already.
>=20
> That's a respectable view, but one that, IMHO, would lead to a missed =
opportunity to have a single standard.
>=20
> I do understand the inconvenience of having to adapt running codes =
based on encapsulation to a header mapping such as that of 4rd-U.=20
> However, I have no doubt that this is technically easy.
> That's AFAIK the price to be paid to get a unique standard, with the =
nice bonus that existing IPv6-ACL tools, which weren't usable with =
encapsulation, become usable.=20
>=20
>> Then we can continue in the search for the best translation method =
(which, if we are still coming up with new clever alternatives right =
now, we are not converging nearly as fast as we might think we are).
>=20
> It is clear, I hope, that 4rd-U is NOT a double translation technique =
between IPv4 and IPv6 packets.=20
> It is a simple header mapping technique that, like encapsulation, =
preserves network transparency to IPv4 packets across IPv6 domains.

It's clear to me that 4rd-U is not 4rd-T and not 4rd-E. Bravo, your =
ingenuity has led you to something that lies perfectly in the middle of =
the two warring parties. The problem of course is that the solution has =
the full advantages of neither side, even if it clearly has some of =
both.

Sort of reminds me of a certain 53 byte cell.

- Mark

>=20
> Regards,
> RD
>=20
>=20
>=20


From despres.remi@laposte.net  Tue Oct 18 07:31:43 2011
Return-Path: <despres.remi@laposte.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 C228B21F8B5D for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 07:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.774
X-Spam-Level: 
X-Spam-Status: No, score=-1.774 tagged_above=-999 required=5 tests=[AWL=0.175,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KD6dOdWXDszy for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 07:31:43 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7FE21F8B5A for <softwires@ietf.org>; Tue, 18 Oct 2011 07:31:42 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id 6D59F7000123; Tue, 18 Oct 2011 16:31:41 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id 0AC3B70000FF; Tue, 18 Oct 2011 16:31:36 +0200 (CEST)
X-SFR-UUID: 20111018143137441.0AC3B70000FF@msfrf2419.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <0B52D2A1-9938-48A8-A87C-27DE39405263@townsley.net>
Date: Tue, 18 Oct 2011 16:31:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF8BF1B0-63DB-4F9B-BE96-4D214513C0DC@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net> <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net> <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net> <5F044EAF-A653-499B-86B1-993CA77D1071@laposte.net> <0B52D2A1-9938-48A8-A87C-27DE39405263@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 14:31:43 -0000

Le 18 oct. 2011 =E0 15:35, Mark Townsley a =E9crit :
> On Oct 18, 2011, at 2:31 PM, R=E9mi Despr=E9s wrote:
...

>> I do understand the inconvenience of having to adapt running codes =
based on encapsulation to a header mapping such as that of 4rd-U.=20
>> However, I have no doubt that this is technically easy.
>> That's AFAIK the price to be paid to get a unique standard, with the =
nice bonus that existing IPv6-ACL tools, which weren't usable with =
encapsulation, become usable.=20
...

> Bravo, your ingenuity has led you to something that lies perfectly in =
the middle of the two warring parties. The problem of course is that the =
solution has the full advantages of neither side,

It's not because a design has positive features of two other designs =
that it "lies in the middle".

Could you explain the important advantage of encapsulation that is =
missing in 4rd-U?


RD



From mark@townsley.net  Tue Oct 18 02:08:08 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 E15CD21F8C7E for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 02:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.373
X-Spam-Level: 
X-Spam-Status: No, score=-3.373 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRPUY1ZTXMaQ for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 02:08:06 -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 1180C21F8C7B for <softwires@ietf.org>; Tue, 18 Oct 2011 02:08:05 -0700 (PDT)
Received: by wyh22 with SMTP id 22so393246wyh.31 for <softwires@ietf.org>; Tue, 18 Oct 2011 02:08:05 -0700 (PDT)
Received: by 10.227.138.147 with SMTP id a19mr583971wbu.23.1318928860785; Tue, 18 Oct 2011 02:07:40 -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 g20sm2280632wbp.13.2011.10.18.02.07.35 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Oct 2011 02:07:36 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-52--828245308
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net>
Date: Tue, 18 Oct 2011 11:07:34 +0200
Message-Id: <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net> <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 18 Oct 2011 08:02:21 -0700
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 09:08:09 -0000

--Apple-Mail-52--828245308
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 18, 2011, at 10:38 AM, R=E9mi Despr=E9s wrote:

>=20
> Le 18 oct. 2011 =E0 10:21, Mark Townsley a =E9crit :
>=20
>>=20
>> While it is interesting to explore the various design spaces, we do =
not need more ways to munge an IPv4 packet into an IPv6 packet and back =
to an IPv4 packet. Any alternative beyond the simple and obvious =
encap/decap that routers have used for decades is already too much IMHO, =
we certainly don't need a 3rd or 4th method.
>=20
>> Let's please curtail new the inventions, and get back to the =
standardization.
>=20
> Sorry that you see it that way.
>=20
> The interim meeting has been useful in that objectives of present =
parties were clarified better than ever before.
> Standardization is, and has always been, a process in which =
understanding each other, and finding ways to accommodate all valid =
concerns, are been key to success.
> That's what I have been working for: good standardization.=20
>=20
> Would you please indicate what you personally challenge in this:
> a) One standard is better than two.

Yes.=20

> b) Maintaining network transparency to IPv4 packets is a useful =
feature
> c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with ACLs, =
is a useful feature
> d) Encapsulation has b) but not c)
> e) Double translation has c) but not b)
> f) 4rd-U has both b) and c)

IPv6 packets with incorrect checksums may be incompatible with =
firewalls, website redirects (e.g. I don't see why the web server will =
not just drop the packet if the checksum fails), etc.=20

The translation (or header mapping) cases all purport to be helpful to =
various processing or operations along the path between the router =
endpoints. By definition, it is more complicated to weigh relative value =
of the various options in this space as we have to start weaving our way =
through sometimes unknown and certainly non-standard DPI, ACL, =
redirection, O&M, etc. features at multiple places in the network. In =
some cases, I'm afraid that we are optimizing based on speculative =
properties of IPv6 networks that are still in their infancy in terms of =
mainstream deployment. Experience tells me convergence here will be =
difficult, and getting it right will be even more difficult.=20

I think we need to get the base case of stateless encap/decap out the =
door so that it can be built into CPE alongside the stateful ds-lite =
encap/decap option that is being built already. Then we can continue in =
the search for the best translation method (which, if we are still =
coming up with new clever alternatives right now, we are not converging =
nearly as fast as we might think we are).

- Mark

>  =20
> Regards,
> RD
>=20
>=20
>=20
>> =20
>>=20
>> - Mark
>>=20
>> On Oct 17, 2011, at 7:10 PM, R=E9mi Despr=E9s wrote:
>>=20
>>> Hi Behcet,
>>>=20
>>> 4rd-U translates addresses, but:
>>> - isn't concerned with anything above the IP layer;
>>> - has a way to convey fields of IPv4 that would be lost in IPv6 (DF =
and, for "pipe and short pipe" as discussed by Satoru-san, the TOS).=20
>>> 4rd-T translates addresses, AND:
>>> - is concerned with the IPv4 payload (possible checksum adjustment)
>>> - isn't fully transparent to DF, and to the TOS if a specific IPv6 =
Traffic class is needed for IPv6-domain traversal.
>>>=20
>>> Hope it clarifies why, IMHO, calling 4rd-u a double-translation =
solution, like the RFC6145-based double translation, would create =
confusion.
>>> If you look for a name, what about "header mapping"=20
>>>=20
>>> Regards,
>>> RD
>>>=20
>>>  =20
>>>=20
>>> Le 17 oct. 2011 =E0 18:41, Behcet Sarikaya a =E9crit :
>>>=20
>>>> the idea of 4rd-U is to map IPv4 headers into IPv6 headers
>>>>=20
>>>> address translation is called address derivation.
>>>>=20
>>>> Isn't this translation?
>>>>=20
>>>> regards,
>>>>=20
>>>> Behcet
>>>>=20
>>>> On Mon, Oct 17, 2011 at 11:26 AM, R=E9mi Despr=E9s =
<despres.remi@laposte.net> wrote:
>>>>=20
>>>> Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :
>>>>=20
>>>> > Remi,
>>>> >
>>>> > how is 4rd-U different from translation?
>>>>=20
>>>> Functionally, full network transparency to DF bit (and TOS with the =
complement that was missing).
>>>> Technically, see for instance Figure 1 of the draft.
>>>>=20
>>>> Cheers,
>>>> RD
>>>>=20
>>>>=20
>>>> >
>>>> > cheers,
>>>> > Ole
>>>> >
>>>> >
>>>> > On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:
>>>> >
>>>> >>
>>>> >> Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :
>>>> >>
>>>> >>> On 2011/10/17, at 23:46, Maoke wrote:
>>>> >>>
>>>> >>>> hi Satoru-san,
>>>> >>>>
>>>> >>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>> >>>> Hi Maoke-san,
>>>> >>>>
>>>> >>>> On 2011/10/17, at 22:30, Maoke wrote:
>>>> >>>>
>>>> >>>>> hi Satoru-san,
>>>> >>>>>
>>>> >>>>> may i understand that, as Remi's proposal is applied for the =
double translation case, TTL being translated to IPv6 Hop Limit is =
enough? as is stated in RFC6145, translator is a "router" and therefore =
the behavior should not be as same as the virtual link. right?
>>>> >>>>
>>>> >>>> If so, just double translation is enough for that.
>>>> >>>>
>>>> >>>> it sounds nice. what i would like to have is a consistent =
header processing for single/double translations and encapsulation.
>>>> >>>
>>>> >>> I think that encapsulation and double translation can't be =
consistent to processing packet at all.
>>>> >>
>>>> >> 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.
>>>> >> It is believed to have advantages over both of them.
>>>> >> Disadvantages has AFAIK still to be identified.
>>>> >>
>>>> >>
>>>> >>>> can we keep the TTL of IPv4 in the IPv6 header (plus fragment =
header but not anything more unless really necessary)?
>>>> >>>>
>>>> >>>> can i understand that the following requirements are exclusive =
to each other: (a) we want to keep TTL changed in the IPv6 domain as the =
behavior of translation; (b) we want to keep TTL not changed until =
leaving the IPv6 domain as the behavior of encapsulation (4rd-U)?
>>>> >>>
>>>> >>> I think that these are exclusive.
>>>> >>
>>>> >> Indeed, one cant't do both simultaneously, but AFAIK either =
choice is acceptable.
>>>> >> Is there one you prefer, for which reason?
>>>> >>
>>>> >>>> RFC6145 has defined TTL<->HopLimit translation. then how about =
using another reserved bit, say EF, in the fragment header for =
indicating the mode? if EF =3D 1, it is encapsulation mode, and =
therefore the HopLimit in the base header keeps unchanged untile being =
translated back to IPv4; if EF =3D 0, it is translation mode, and the =
HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.
>>>> >>>
>>>> >>> It seems that adding new semantics more. Very creative, but is =
it really needed even we already have both encaps and translation? When =
you want to define more new semantics, it would be better you define new =
protocol number for 4rd-U.
>>>> >>
>>>> >> The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.
>>>> >>
>>>> >> A key advantage of Double translation over Encapsulation, is =
that the IPv6 next header is the same as the Protocol of the conveyed =
IPv4 packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.
>>>> >>
>>>> >>>> thus i'd like to suggest that one as follows, based on Remi's =
complement, where E is the indicator of encapsulation mode. copying TOS =
in the fragment header is fine because it doesn't impact the IPv6 dst =
(of single translation) getting the original IPv4 src's relative =
identification.
>>>> >>>>
>>>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>     |Vers=3D6 |   TrafClass   |            Flow Label          =
       |
>>>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>     |         Payload Length        |Next Header=3D44 |   Hop =
Limit   |
>>>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>     |                                                          =
     |
>>>> >>>>     +                                                          =
     +
>>>> >>>>     |                                                          =
     |
>>>> >>>>     +                  IPv6 Source Address                     =
     +
>>>> >>>>     |                                                          =
     |
>>>> >>>>     +                                                          =
     +
>>>> >>>>     |                                                          =
     |
>>>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>     |                                                          =
     |
>>>> >>>>     +                                                          =
     +
>>>> >>>>     |                                                          =
     |
>>>> >>>>     +                IPv6 Destination Address                  =
     +
>>>> >>>>     |                                                          =
     |
>>>> >>>>     +                                                          =
     +
>>>> >>>>     |                                                          =
     |
>>>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>     |  Next Header  |   Reserved    | IPv6  Fragment Offset   =
|E|D|M|
>>>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>     |      0        |     TOS       |       IPv4 =
Identification     |
>>>> >>>>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>     |                        IPv4 Payload                      =
     |
>>>> >>>>     |                                                          =
     |
>>>> >>>> unfortunately, however, even we free the first bit of IPv6 =
identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).
>>>> >>>>
>>>> >>>> the problem of EF in fragment header is, it requires that the =
implementation process fragment header before descreasing the HopLimit. =
is it feasible?
>>>> >>>>
>>>> >>>> how do you think?
>>>> >>>
>>>> >>> IMHO, I'm not sure it is good idea to change the semantics of =
the IPv6 fragment. If a router receives 4rd-U packets, which router =
doesn't understand 4rd-U, processing these packets as fragmented packets =
could cause problem that sounds buffer exhaust attack.
>>>> >>
>>>> >> I don't see that:
>>>> >> - IPv6 routers are not concerned with fragmentation.
>>>> >> - the 4rd-U endpoint doesn't need to keep anything in a =
reassembly buffer if a conveyed IPv4 packet is completely contained in a =
single IPv6 packet.
>>>> >>
>>>> >>> And I also think that if we need to add new semantics even we =
can utilize IPv6 fragment, it would be better to define new protocol =
number for 4rd-U.
>>>> >>
>>>> >> See above why a new protocol number wouldn't be workable.
>>>> >>
>>>> >>> However, I don't think that we need to request to define it, =
because existing encapsulation and translation can be utilized for each =
appropriate situation.
>>>> >>
>>>> >>
>>>> >>
>>>> >> The point isn't to prevent any ISP from deploy for its own use =
any design that works.
>>>> >>
>>>> >> Yet, having only ONE STANDARD for a given need is better than =
several.
>>>> >> I hope you can agree with that.
>>>> >> (In this case, the need is stateless support of residual IPv4 =
across IPv6-only networks.)
>>>> >>
>>>> >> AFAIK, 4rd-U is better for this than double translation (say =
4rd-T), and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E).
>>>> >> If you still believe this is not right, an explanation will of =
course be welcome.
>>>> >>
>>>> >> Cheers,
>>>> >> RD
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>>
>>>> >>> cheers,
>>>> >>> --satoru
>>>> >>>
>>>> >>>
>>>> >>>>
>>>> >>>> cheers,
>>>> >>>> maoke
>>>> >>>>
>>>> >>>> cheers,
>>>> >>>> --satoru
>>>> >>>>
>>>> >>>>> regards,
>>>> >>>>> maoke
>>>> >>>>> 2011/10/17 Satoru Matsushima <satoru.matsushima@gmail.com>
>>>> >>>>> Hi Remi-san,
>>>> >>>>>
>>>> >>>>>> With this added, I believe that 4rd-U is a real progress =
over previously proposed Double translation and Encapsulation.
>>>> >>>>>> It can make IMHO a valuable unified standard.
>>>> >>>>>
>>>> >>>>> Not enough. The original TTL value in IPv4 header must be =
carried.
>>>> >>>>>
>>>> >>>>> cheers,
>>>> >>>>> --satoru
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>>>> >>>>>
>>>> >>>>>> Hi Satoru-san,
>>>> >>>>>>
>>>> >>>>>> Thank you for identifying a limitation of the 4rd-U
>>>> >>>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
>>>> >>>>>> All these need e2e transparency to the IPv4 Type of Service.
>>>> >>>>>>
>>>> >>>>>> Fortunately, this is easy to fix: in the Identification =
field of the IPv6 Fragment header, copy not only the DF bits but also =
the IPv4 TOS.
>>>> >>>>>>
>>>> >>>>>> The proposed 4r-U packet format becomes:
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>>> |Vers=3D6 |   TrafClass   |            Flow Label            =
     |
>>>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>>> |         Payload Length        |Next Header=3D44 |   Hop =
Limit   |
>>>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>> +                                                            =
   +
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>> +                  IPv6 Source Address                       =
   +
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>> +                                                            =
   +
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>> +                                                            =
   +
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>> +                IPv6 Destination Address                    =
   +
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>> +                                                            =
   +
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>>> |  Next Header  |    Reserved   | IPv6  Fragment Offset   | =
0 |M|
>>>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>>> |D|      0      |    IPv4 TOS   |       IPv4 Identification  =
   |
>>>> >>>>>> =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> >>>>>> |                        IPv4 Payload                        =
   |
>>>> >>>>>> |                                                            =
   |
>>>> >>>>>>
>>>> >>>>>> With this added, I believe that 4rd-U is a real progress =
over previously proposed Double translation and Encapsulation.
>>>> >>>>>> It can make IMHO a valuable unified standard.
>>>> >>>>>>
>>>> >>>>>> Yet, I may have missed something else.
>>>> >>>>>> New justified objections are therefore most welcome..
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> Regards,
>>>> >>>>>> RD
>>>> >>>>>
>>>> >>>>> _______________________________________________
>>>> >>>>> Softwires mailing list
>>>> >>>>> Softwires@ietf.org
>>>> >>>>> https://www.ietf.org/mailman/listinfo/softwires
>>>> >>>>>
>>>> >>>>
>>>> >>>>
>>>> >>>
>>>> >>
>>>> >> _______________________________________________
>>>> >> Softwires mailing list
>>>> >> Softwires@ietf.org
>>>> >> https://www.ietf.org/mailman/listinfo/softwires
>>>> >
>>>> _______________________________________________
>>>> Softwires mailing list
>>>> Softwires@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/softwires
>>>>=20
>>>=20
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>=20
>=20


--Apple-Mail-52--828245308
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 18, 2011, at 10:38 AM, R=E9mi Despr=E9s =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><br><div><div>Le 18 oct. =
2011 =E0 10:21, Mark Townsley a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><br></div><div>While it is =
interesting to explore the various design spaces, we do not need more =
ways to munge an IPv4 packet into an IPv6 packet and back to an IPv4 =
packet. Any alternative beyond the simple and obvious encap/decap that =
routers have used for decades is already too much IMHO, we certainly =
don't need a 3rd or 4th method. </div></div></blockquote><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div>Let's please =
curtail new the inventions, and get back to the =
standardization.</div></div></blockquote><div><br></div>Sorry that you =
see it that way.</div><div><br></div><div>The interim meeting has been =
useful in that objectives of present parties were clarified better than =
ever before.</div><div>Standardization is, and has always been, a =
process in which understanding each other, and finding ways to =
accommodate all valid concerns, are been key to =
success.</div><div>That's what I have been working for: good =
standardization.&nbsp;</div><div><br></div><div>Would you please =
indicate what you personally challenge in this:</div><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; ">a) One =
standard is better than two.</span><span class=3D"Apple-style-span" =
style=3D"font-family: monospace; =
"><br></span></div></blockquote><div><br></div><div>Yes.&nbsp;</div><br><b=
lockquote type=3D"cite"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; ">b) =
Maintaining network transparency to IPv4 packets is a useful =
feature</span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; "><br></span><span class=3D"Apple-style-span" =
style=3D"font-family: monospace; ">c) Being able to apply IPv6 O&amp;M =
tools to IPv4 traffic, e.g. with ACLs, is a useful feature</span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; =
"><br></span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; ">d) Encapsulation has b) but not c)</span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; =
"><br></span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; ">e) Double translation has c) but not b)</span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; =
"><br></span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; ">f) 4rd-U has both b) and c)</span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; =
"><br></span></div></blockquote><div><br></div><div>IPv6 packets with =
incorrect checksums may be incompatible with firewalls, website =
redirects (e.g. I don't see why the web server will not just drop the =
packet if the checksum fails), etc.&nbsp;</div><div><br></div><div>The =
translation (or header mapping) cases all purport to be helpful to =
various processing or operations along the path between the router =
endpoints. By definition, it is more complicated to weigh relative value =
of the various options in this space as we have to start weaving our way =
through sometimes unknown and certainly non-standard DPI, ACL, =
redirection, O&amp;M, etc. features at multiple places in the network. =
In some cases,&nbsp;I'm afraid that we are optimizing based on =
speculative properties of IPv6 networks that are still in their infancy =
in terms of mainstream deployment. Experience tells me convergence here =
will be difficult, and getting it right will be even more =
difficult.&nbsp;</div><div><br></div><div>I think we need to get the =
base case of stateless encap/decap out the door so that it can be built =
into CPE alongside the stateful ds-lite encap/decap option that is being =
built already. Then we can continue in the search for the best =
translation method (which, if we are still coming up with new clever =
alternatives right now, we are not converging nearly as fast as we might =
think we are).</div><div><br></div><div>- Mark</div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div>&nbsp;&nbsp;</div><div>Regards,</div><div>RD</div><div><br></div><d=
iv><br></div><div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div> &nbsp;</div><div><br></div><div>- =
Mark</div><br><div><div>On Oct 17, 2011, at 7:10 PM, R=E9mi Despr=E9s =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">Hi =
Behcet,<div><br></div><div>4rd-U translates addresses, but:<div>- isn't =
concerned with anything above the IP layer;</div><div>- has a way to =
convey fields of IPv4 that would be lost in IPv6 (DF and, for "pipe and =
short pipe" as discussed by Satoru-san, the =
TOS).&nbsp;</div><div><div>4rd-T translates addresses, AND:</div><div>- =
is concerned with the IPv4 payload (possible checksum =
adjustment)</div><div>- isn't fully transparent to DF, and to the TOS if =
a specific IPv6 Traffic class is needed for IPv6-domain =
traversal.</div><div><br></div><div>Hope it clarifies why, IMHO, calling =
4rd-u a double-translation solution, like the RFC6145-based double =
translation, would create confusion.</div><div>If you look for a name, =
what about "header =
mapping"&nbsp;</div><div><br></div><div>Regards,</div><div>RD</div><div><b=
r></div><div>&nbsp;&nbsp;</div><div><br><div><div>Le 17 oct. 2011 =E0 =
18:41, Behcet Sarikaya a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">the idea =
of 4rd-U is to map IPv4 headers into IPv6 headers<br><br>address =
translation is called address derivation.<br><br>Isn't this =
translation?<br><br>regards,<br><br>Behcet<br><br><div =
class=3D"gmail_quote">On Mon, Oct 17, 2011 at 11:26 AM, R=E9mi Despr=E9s =
<span dir=3D"ltr">&lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Le 17 oct. 2011 =E0 18:15, Ole Troan a =E9crit :<br>
<div class=3D"im"><br>
&gt; Remi,<br>
&gt;<br>
&gt; how is 4rd-U different from translation?<br>
<br>
</div>Functionally, full network transparency to DF bit (and TOS with =
the complement that was missing).<br>
Technically, see for instance Figure 1 of the draft.<br>
<br>
Cheers,<br>
<font color=3D"#888888">RD<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
&gt;<br>
&gt; cheers,<br>
&gt; Ole<br>
&gt;<br>
&gt;<br>
&gt; On Oct 17, 2011, at 18:09 , R=E9mi Despr=E9s wrote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Le 17 oct. 2011 =E0 17:27, Satoru Matsushima a =E9crit :<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 2011/10/17, at 23:46, Maoke wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; hi Satoru-san,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 2011/10/17 Satoru Matsushima &lt;<a =
href=3D"mailto:satoru.matsushima@gmail.com">satoru.matsushima@gmail.com</a=
>&gt;<br>
&gt;&gt;&gt;&gt; Hi Maoke-san,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 2011/10/17, at 22:30, Maoke wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; hi Satoru-san,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; may i understand that, as Remi's proposal is =
applied for the double translation case, TTL being translated to IPv6 =
Hop Limit is enough? as is stated in RFC6145, translator is a "router" =
and therefore the behavior should not be as same as the virtual link. =
right?<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; If so, just double translation is enough for that.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; it sounds nice. what i would like to have is a =
consistent header processing for single/double translations and =
encapsulation.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that encapsulation and double translation can't be =
consistent to processing packet at all.<br>
&gt;&gt;<br>
&gt;&gt; 4rd-u (duly completed with TOS transparency) is neither Double =
RFC6145 translation nor Encapsulation.<br>
&gt;&gt; It is believed to have advantages over both of them.<br>
&gt;&gt; Disadvantages has AFAIK still to be identified.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; can we keep the TTL of IPv4 in the IPv6 header (plus =
fragment header but not anything more unless really necessary)?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; can i understand that the following requirements are =
exclusive to each other: (a) we want to keep TTL changed in the IPv6 =
domain as the behavior of translation; (b) we want to keep TTL not =
changed until leaving the IPv6 domain as the behavior of encapsulation =
(4rd-U)?<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that these are exclusive.<br>
&gt;&gt;<br>
&gt;&gt; Indeed, one cant't do both simultaneously, but AFAIK either =
choice is acceptable.<br>
&gt;&gt; Is there one you prefer, for which reason?<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; RFC6145 has defined TTL&lt;-&gt;HopLimit translation. =
then how about using another reserved bit, say EF, in the fragment =
header for indicating the mode? if EF =3D 1, it is encapsulation mode, =
and therefore the HopLimit in the base header keeps unchanged untile =
being translated back to IPv4; if EF =3D 0, it is translation mode, and =
the HopLimit in the base header will decrease 1 for each hop. btw, =
previously i suggest using one of the reserved bits for the DF (e.g., =
the one before MF) instead of the first bit of the identification in the =
ipv6 fragement header, in order to avoid ambiguity caused by an IPv6 =
host in the single translation.<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; It seems that adding new semantics more. Very creative, but =
is it really needed even we already have both encaps and translation? =
When you want to define more new semantics, it would be better you =
define new protocol number for 4rd-U.<br>

&gt;&gt;<br>
&gt;&gt; The idea is to avoid having two designs, each one with its own =
limitations, while a third design exists that has none of these =
limitations.<br>
&gt;&gt;<br>
&gt;&gt; A key advantage of Double translation over Encapsulation, is =
that the IPv6 next header is the same as the Protocol of the conveyed =
IPv4 packet. Having a new protocol number would therefore defeat the =
objective of having advantages of both Double translation and =
encapsulations.<br>

&gt;&gt;<br>
&gt;&gt;&gt;&gt; thus i'd like to suggest that one as follows, based on =
Remi's complement, where E is the indicator of encapsulation mode. =
copying TOS in the fragment header is fine because it doesn't impact the =
IPv6 dst (of single translation) getting the original IPv4 src's =
relative identification.<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; |Vers=3D6 | &nbsp; TrafClass &nbsp; | =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Flow Label &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; Payload =
Length &nbsp; &nbsp; &nbsp; &nbsp;|Next Header=3D44 | &nbsp; Hop Limit =
&nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;IPv6 Source Address &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;IPv6 Destination Address &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp;Next Header &nbsp;| &nbsp; =
Reserved &nbsp; &nbsp;| IPv6 &nbsp;Fragment Offset &nbsp; |E|D|M|<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp; =
&nbsp; &nbsp;| &nbsp; &nbsp; TOS &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; =
&nbsp; IPv4 Identification &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IPv4 Payload &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt; unfortunately, however, even we free the first bit of =
IPv6 identification in the fragment header, we cannot put the TTL here =
(before the TOS) because traversing different paths may cause =
inconsistant IPv6 identification values in fragments of the same =
datagram and disable reassemble at the IPv6 dst (in the single =
translation mode).<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; the problem of EF in fragment header is, it requires =
that the implementation process fragment header before descreasing the =
HopLimit. is it feasible?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; how do you think?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; IMHO, I'm not sure it is good idea to change the semantics =
of the IPv6 fragment. If a router receives 4rd-U packets, which router =
doesn't understand 4rd-U, processing these packets as fragmented packets =
could cause problem that sounds buffer exhaust attack.<br>

&gt;&gt;<br>
&gt;&gt; I don't see that:<br>
&gt;&gt; - IPv6 routers are not concerned with fragmentation.<br>
&gt;&gt; - the 4rd-U endpoint doesn't need to keep anything in a =
reassembly buffer if a conveyed IPv4 packet is completely contained in a =
single IPv6 packet.<br>
&gt;&gt;<br>
&gt;&gt;&gt; And I also think that if we need to add new semantics even =
we can utilize IPv6 fragment, it would be better to define new protocol =
number for 4rd-U.<br>
&gt;&gt;<br>
&gt;&gt; See above why a new protocol number wouldn't be workable.<br>
&gt;&gt;<br>
&gt;&gt;&gt; However, I don't think that we need to request to define =
it, because existing encapsulation and translation can be utilized for =
each appropriate situation.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The point isn't to prevent any ISP from deploy for its own use =
any design that works.<br>
&gt;&gt;<br>
&gt;&gt; Yet, having only ONE STANDARD for a given need is better than =
several.<br>
&gt;&gt; I hope you can agree with that.<br>
&gt;&gt; (In this case, the need is stateless support of residual IPv4 =
across IPv6-only networks.)<br>
&gt;&gt;<br>
&gt;&gt; AFAIK, 4rd-U is better for this than double translation (say =
4rd-T), and better than encapsulation (say 4rd-E), because it combines =
advantages of both (applicability of IPv6 O&amp;M tools (a feature of =
4rd-T), AND e2e transparency to IPv4 semantics (a feature of 4rd-E).<br>

&gt;&gt; If you still believe this is not right, an explanation will of =
course be welcome.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; RD<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt; maoke<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; regards,<br>
&gt;&gt;&gt;&gt;&gt; maoke<br>
&gt;&gt;&gt;&gt;&gt; 2011/10/17 Satoru Matsushima &lt;<a =
href=3D"mailto:satoru.matsushima@gmail.com">satoru.matsushima@gmail.com</a=
>&gt;<br>
&gt;&gt;&gt;&gt;&gt; Hi Remi-san,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; With this added, I believe that 4rd-U is a real =
progress over previously proposed Double translation and =
Encapsulation.<br>
&gt;&gt;&gt;&gt;&gt;&gt; It can make IMHO a valuable unified =
standard.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Not enough. The original TTL value in IPv4 header =
must be carried.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; cheers,<br>
&gt;&gt;&gt;&gt;&gt; --satoru<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On 2011/10/17, at 21:36, R=E9mi Despr=E9s =
wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Satoru-san,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thank you for identifying a limitation of the =
4rd-U<br>
&gt;&gt;&gt;&gt;&gt;&gt; You are right, as currently specified, "it =
doesn't support diff-serv tunneling model, pipe and short-pipe".<br>
&gt;&gt;&gt;&gt;&gt;&gt; All these need e2e transparency to the IPv4 =
Type of Service.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Fortunately, this is easy to fix: in the =
Identification field of the IPv6 Fragment header, copy not only the DF =
bits but also the IPv4 TOS.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; The proposed 4r-U packet format becomes:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; |Vers=3D6 | &nbsp; TrafClass &nbsp; | &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Flow Label &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; Payload Length =
&nbsp; &nbsp; &nbsp; &nbsp;|Next Header=3D44 | &nbsp; Hop Limit &nbsp; =
|<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;IPv6 Source Address &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;IPv6 Destination Address &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; +<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp;Next Header &nbsp;| &nbsp; =
&nbsp;Reserved &nbsp; | IPv6 &nbsp;Fragment Offset &nbsp; | 0 |M|<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; |D| &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp; &nbsp;| =
&nbsp; &nbsp;IPv4 TOS &nbsp; | &nbsp; &nbsp; &nbsp; IPv4 Identification =
&nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IPv4 Payload &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; With this added, I believe that 4rd-U is a real =
progress over previously proposed Double translation and =
Encapsulation.<br>
&gt;&gt;&gt;&gt;&gt;&gt; It can make IMHO a valuable unified =
standard.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Yet, I may have missed something else.<br>
&gt;&gt;&gt;&gt;&gt;&gt; New justified objections are therefore most =
welcome..<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Regards,<br>
&gt;&gt;&gt;&gt;&gt;&gt; RD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt;&gt; Softwires mailing list<br>
&gt;&gt;&gt;&gt;&gt; <a =
href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Softwires mailing list<br>
&gt;&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;<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"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</div></div></blockquote></div><br>
=
</blockquote></div><br></div></div></div></div>___________________________=
____________________<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">https://www.ietf.=
org/mailman/listinfo/softwires</a><br></blockquote></div><br></div></block=
quote></div><br></div></blockquote></div><br></body></html>=

--Apple-Mail-52--828245308--

From mark@townsley.net  Tue Oct 18 10:44:20 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 C2A9C21F8C4B for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 10:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.359
X-Spam-Level: 
X-Spam-Status: No, score=-3.359 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12-c3g3rk1EW for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 10:44: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 0156E21F8C49 for <softwires@ietf.org>; Tue, 18 Oct 2011 10:44:19 -0700 (PDT)
Received: by wyh22 with SMTP id 22so979789wyh.31 for <softwires@ietf.org>; Tue, 18 Oct 2011 10:44:18 -0700 (PDT)
Received: by 10.216.134.208 with SMTP id s58mr5740729wei.91.1318959858581; Tue, 18 Oct 2011 10:44:18 -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 fo7sm4825598wbb.20.2011.10.18.10.44.16 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Oct 2011 10:44:17 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <DF8BF1B0-63DB-4F9B-BE96-4D214513C0DC@laposte.net>
Date: Tue, 18 Oct 2011 19:44:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <63DB920E-8768-47BD-8185-959C4165977B@townsley.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net> <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net> <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net> <5F044EAF-A653-499B-86B1-993CA77D1071@laposte.net> <0B52D2A1-9938-48A8-A87C-27DE39405263@townsley.net> <DF8BF1B0-63DB-4F9B-BE96-4D214513C0DC@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 17:44:20 -0000

On Oct 18, 2011, at 4:31 PM, R=E9mi Despr=E9s wrote:

>=20
> Le 18 oct. 2011 =E0 15:35, Mark Townsley a =E9crit :
>> On Oct 18, 2011, at 2:31 PM, R=E9mi Despr=E9s wrote:
> ...
>=20
>>> I do understand the inconvenience of having to adapt running codes =
based on encapsulation to a header mapping such as that of 4rd-U.=20
>>> However, I have no doubt that this is technically easy.
>>> That's AFAIK the price to be paid to get a unique standard, with the =
nice bonus that existing IPv6-ACL tools, which weren't usable with =
encapsulation, become usable.=20
> ...
>=20
>> Bravo, your ingenuity has led you to something that lies perfectly in =
the middle of the two warring parties. The problem of course is that the =
solution has the full advantages of neither side,
>=20
> It's not because a design has positive features of two other designs =
that it "lies in the middle".
>=20
> Could you explain the important advantage of encapsulation that is =
missing in 4rd-U?

It's been specified and implemented for years, it is part of other =
softwires specifications, it is being implemented in CPE equipment today =
as part of ds-lite, it doesn't put payloads on the wire with =
mis-matching checksums.... Sure, tunneling doesn't play nice with some =
ACLs that only look at native IPv6, but at least this is a very =
well-understood attribute of tunneling that operators expect and in many =
cases are able to design around. FWIW, my crystal ball says that these =
limitations will will become less and less relevant if and when 4-in-6 =
operation becomes more and more prevalent, but that's just me.

Translation based on what's already defined in the behave WG is less =
conservative than simple encapsulation, but at least it is building on =
something that already exists, is well-specified and deployed, etc. We =
can expect to see IPv4 payloads with IPv6 headers on the network because =
of translators, but at least the checksums will be correct and there is =
a decent chance that a host will be able to digest the packet and get it =
to a working application after passing through one level of translation =
(or being redirected, subjected to DPI, etc).=20

Again, no offense at all to the ingenuity of -U, but I simply have a =
hard time justifying that we need to cast a balance between these =
relatively well-known, specified, and implemented building-blocks with =
something new.=20

If I believed for a microsecond that -U would wipe both encapsulation =
and translation from the planet so that we would have only one mechanism =
here, I would be more supportive. The problem is that the other two =
already exist in other closely related contexts such that there is no =
way that this doesn't become a 3rd method in the network without turning =
back time itself.

- Mark

>=20
>=20
> RD
>=20
>=20


From brian.e.carpenter@gmail.com  Tue Oct 18 13:01:50 2011
Return-Path: <brian.e.carpenter@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 016AC21F8B5A for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 13:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.399
X-Spam-Level: 
X-Spam-Status: No, score=-103.399 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBAUARMq5RcI for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 13:01:49 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 5499021F8B59 for <softwires@ietf.org>; Tue, 18 Oct 2011 13:01:49 -0700 (PDT)
Received: by qyk31 with SMTP id 31so880204qyk.10 for <softwires@ietf.org>; Tue, 18 Oct 2011 13:01:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7FoarAoT4MlGq2s4WOdCPkC1JRoKkhUrf9FBub9vfgM=; b=JzU1hIRFC/9t9v5mduITTs83EboALoT4DEgERN+Up0pxTIHgy51dV706nHerTiezxB HhIH2bb2jBkA8uoU+cUjvDkt3KBTVLbs2CWIyeg+ES4AiUJdAQ425Bsh8MVxa8Sv4YOY d4rRGsXtF96hU+SkzWqk7cl0b2LF3zmtfmkEk=
Received: by 10.229.85.146 with SMTP id o18mr863987qcl.111.1318968108659; Tue, 18 Oct 2011 13:01:48 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id em9sm3675660qab.10.2011.10.18.13.01.45 (version=SSLv3 cipher=OTHER); Tue, 18 Oct 2011 13:01:47 -0700 (PDT)
Message-ID: <4E9DDB22.9000908@gmail.com>
Date: Wed, 19 Oct 2011 09:01:38 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <4E9C8D5C.4060706@gmail.com> <B83FCD09-0563-4DC3-ADDC-92E0DAA32030@laposte.net>
In-Reply-To: <B83FCD09-0563-4DC3-ADDC-92E0DAA32030@laposte.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] ECN [4rd-U complement - e2e transparency to IPv4 TOS]
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, 18 Oct 2011 20:01:50 -0000

On 2011-10-18 19:55, R=C3=A9mi Despr=C3=A9s wrote:
> Le 17 oct. 2011 =C3=A0 22:17, Brian E Carpenter a =C3=A9crit :
>=20
>> On 2011-10-18 01:36, R=C3=A9mi Despr=C3=A9s wrote:
>>> Hi Satoru-san,
>>>
>>> Thank you for identifying a limitation of the 4rd-U =20
>>> You are right, as currently specified, "it doesn't support diff-serv =
tunneling model, pipe and short-pipe".
>>> All these need e2e transparency to the IPv4 Type of Service.
>>>
>>> Fortunately, this is easy to fix:
>=20
> *
>>> in the Identification field of the IPv6 Fragment header, copy not onl=
y the DF bits but also the IPv4 TOS.
> *
>=20
>> Will this cause any difficulties for ECN, if ECN is supported on the I=
Pv6
>> leg of the journey?
>=20
> Not in my understanding.
> Since the IPv4 TOS is copied in the Identification field of the IPv6 Fr=
agment header, it will be restored at exit of the IPv6 leg independently =
of any MPLS and ECN that may be used in that leg.

That's my problem. If the IPv6 leg supports ECN, any change to the ECN bi=
ts
during the IPv6 journey will be lost, so the end systems will not be info=
rmed
about congestion. I think the ECN bits need to be copied to and from the =
IPv6
Traffic Class.

>> Apart from that, please remember that the DSCP part of the DS Field is=
 not an
>> end-to-end field; it is mutable.
>=20
>> I advise applying the relevant considerations
>> from Sections 4.1 and 5.1 of RFC 6145.
>=20
> This isn't necessary because RFC 6145 is about Translation, while 4rd-U=
, with the above between asterisks, precisely avoids translations between=
 IPv4 TOS and IPv6 Traffic.=20
> In this respect, is more like 4rd Encapsulation than like 4rd Translati=
on.

Firstly, that means that any diffserv treatment specified for the IPv4 pa=
cket is
missed during the IPv6 journey. So as for ECN, the IPv4 DSCP value should=
 probably
be copied into the the IPv6 traffic class. Second, as discussed in RFC 61=
45 section 5.1,
the diffserv code point might be rewritten at the exit from IPv6.

Please also see the extensive discussion about diffserv and tunnels in RF=
C 2983.
Actually the treatment in RFC 6145 was supposed to be roughly equivalent =
to RFC 2983.

Regards
   Brian

> Regards,
> RD
>=20
>=20
>=20
>=20
> =20
>> Regards
>>   Brian Carpenter
>>
>>
>>
>=20


From fibrib@gmail.com  Tue Oct 18 15:21:22 2011
Return-Path: <fibrib@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 7E32521F8726 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 15:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.223
X-Spam-Level: 
X-Spam-Status: No, score=-2.223 tagged_above=-999 required=5 tests=[AWL=-1.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8Q0WcrIthbR for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 15:21:21 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 96A1C21F88B6 for <softwires@ietf.org>; Tue, 18 Oct 2011 15:21:20 -0700 (PDT)
Received: by wwe6 with SMTP id 6so1114031wwe.13 for <softwires@ietf.org>; Tue, 18 Oct 2011 15:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JP16dKGvBcB8DZOMge/9BPmrxpQBwKQml6orpFiV9Mw=; b=mnrl7Vl3rlc1xszIBhtEEbZdO3s0tWVZcEKtfMXpLoq6l+Xb/KehxdrpdC10SACLpU qid/09ugRsiALkI58/NPiuPEAq9V8MKcxqTNWBK7Jznjys0H4/fTGIer3jOjCiPVaw4W BHyPFVStozat4f1V798gt4c25lkrY87836WK0=
MIME-Version: 1.0
Received: by 10.216.90.4 with SMTP id d4mr1580661wef.22.1318976478446; Tue, 18 Oct 2011 15:21:18 -0700 (PDT)
Received: by 10.216.17.200 with HTTP; Tue, 18 Oct 2011 15:21:18 -0700 (PDT)
In-Reply-To: <4E9CEA60.6040208@jacni.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com>
Date: Wed, 19 Oct 2011 07:21:18 +0900
Message-ID: <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=0016e6d6481577056404af9a24ef
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 18 Oct 2011 22:21:22 -0000

--0016e6d6481577056404af9a24ef
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

hi Jacni,
=D4=DA 2011=C4=EA10=D4=C218=C8=D5 =C9=CF=CE=E711:54=A3=ACJacni Qin <jacni@j=
acni.com>=D0=B4=B5=C0=A3=BA

>
>
> 1) list all mutually exclusive IPv4 networks to be involved in the residu=
al
> deployment, i.e., Rule IPv4 prefixes;
> 2) calculate IPv6 prefix length for each Rule IPv4 prefix,
>
> For clarifications, you mean the "Rule IPv6 Prefix" length, right? since
> the length of Delegated Prefix should have been settled before this step.
>
>
sure. i meant the Rule IPv6 Prefix length. :)

there is still another issue, the MAX PSID. personally i like the algorithm
of making longest-match for the PSID. however, the position of the PSID is
somehow a problem. in the step 2) (or a little before), when you setting th=
e
delegated prefix length, this length only covers the IPv4 suffix and the
PSID itself, right?

then if the length is, e.g., /64, and the PSID occupies the last 4 bits.
then the MAX PSID for a CE is put at 60 ~ 71 bits. this is fine with the
routing, which can get the encapsulated stuff to the right CE. however, it
may hurt the IID to some extent, for example, we have the PSID=3D0x4, while
for a certain packet, it contains destination port 0xe488, then the MAX PSI=
D
=3D 0x488, and then the IID part for this packet towards the dst CE will be
not 200:5efe:: any more but

           8800:5efe::

right? making the "u" bit destroyed, and the destination CE cannot identify
this is a packet for encapsulation or a packet for direct forwarding. it
also detroys the V-bit in the unified address format.

thus, may i understand that the planning should accommodate the MAX PSID in
the first 64 bits as well? if so, can we really satisfy the requirement R-1
at the Beijing interim, stating "Efficient bit representation.  Address +
Port range in =3D/56", if the PSID is less than 4 bits?

sorry if i made anything, wrong. just try to understand the design, its
strength and limitations.

best,
maoke


>
> Cheers,
> Jacni
>

--0016e6d6481577056404af9a24ef
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

hi Jacni, <br><div class=3D"gmail_quote">=D4=DA 2011=C4=EA10=D4=C218=C8=D5 =
=C9=CF=CE=E711:54=A3=ACJacni Qin <span dir=3D"ltr">&lt;<a href=3D"mailto:ja=
cni@jacni.com" target=3D"_blank">jacni@jacni.com</a>&gt;</span>=D0=B4=B5=C0=
=A3=BA<br><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex=
; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-lef=
t-style: solid;" class=3D"gmail_quote">


 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
&nbsp;&nbsp;&nbsp; <blockquote type=3D"cite"><div><div class=3D"gmail_quote=
"><div>1) list all mutually exclusive IPv4 networks to be involved
          in the residual deployment, i.e., Rule IPv4 prefixes;&nbsp;</div>
        <div>2) calculate IPv6 prefix length for each Rule IPv4 prefix,
        </div>
      </div>
    </div></blockquote>
    For clarifications, you mean the &quot;Rule IPv6 Prefix&quot; length, r=
ight?
    since the length of Delegated Prefix should have been settled before
    this step.<br>
    <br></div></blockquote><div>&nbsp;</div><div>sure. i meant the Rule IPv=
6 Prefix length. :)</div><div>&nbsp;</div><div>there is still another issue=
, the MAX PSID. personally i like the algorithm of making longest-match for=
 the PSID. however, the position of the PSID is somehow a problem. in the s=
tep 2) (or a little before), when you setting the delegated prefix length, =
this length only covers the IPv4 suffix and the PSID itself, right? </div>

<div>&nbsp;</div><div>then if the length is, e.g., /64, and the PSID occupi=
es the last 4 bits. then the MAX PSID for a CE is put at&nbsp;60 ~ 71 bits.=
 this is fine with the routing, which can get the encapsulated stuff to the=
 right CE. however, it may hurt the IID to some extent, for example, we hav=
e the PSID=3D0x4, while for a certain packet, it contains destination port =
0xe488, then the MAX PSID =3D 0x488, and then the IID part for this packet&=
nbsp;towards the&nbsp;dst CE will be not 200:5efe:: any more but&nbsp;</div=
>

<div>&nbsp;</div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; 8800:5efe:: </div><div>&nbsp;</div><div>right? making the &quot;u&q=
uot; bit destroyed, and the destination CE cannot identify this is a packet=
 for encapsulation or a packet for direct forwarding. it also detroys the V=
-bit in the unified address format. </div>

<div>&nbsp;</div><div>thus, may i understand that the planning should accom=
modate the MAX PSID in the first 64 bits as well? if so, can we really sati=
sfy the requirement R-1 at the Beijing interim, stating  &quot;Efficient bi=
t representation.&nbsp; Address + Port range in =3D/56&quot;, if the PSID i=
s less than 4 bits? </div>
<div>&nbsp;</div><div>sorry if i made anything, wrong. just try to understa=
nd the design, its strength and limitations. </div><div>&nbsp;</div><div>be=
st,</div><div>maoke</div><div>&nbsp;</div>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote"><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    Cheers,<br><font color=3D"#888888">
    Jacni</font><br></div></blockquote></div>

--0016e6d6481577056404af9a24ef--

From jacni@jacni.com  Tue Oct 18 18:34:46 2011
Return-Path: <jacni@jacni.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 7CE741F0C48 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 18:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level: 
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[AWL=0.374,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tuyj9JqANnOt for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 18:34:45 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6761F0C46 for <softwires@ietf.org>; Tue, 18 Oct 2011 18:34:44 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id E95F33800B4 for <softwires@ietf.org>; Tue, 18 Oct 2011 21:34:41 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 6B47834012E for <softwires@ietf.org>; Wed, 19 Oct 2011 09:34:38 +0800 (CST)
Received: from [172.16.181.170] (unknown [221.11.61.39]) by app (Coremail) with SMTP id +AWowJAbSgMaKZ5OiwwfAA--.41770S2; Wed, 19 Oct 2011 09:34:26 +0800 (CST)
Message-ID: <4E9E2987.6070407@jacni.com>
Date: Wed, 19 Oct 2011 09:36:07 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com>
In-Reply-To: <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030306060703000104020203"
X-CM-TRANSID: +AWowJAbSgMaKZ5OiwwfAA--.41770S2
X-Coremail-Antispam: 1UD129KBjvJXoW7KrW5Gw4rtF1xuFy8Gw4xCrg_yoW8ZF1Dp3 ySg390yF4kC3y8uFs7Aw4xWry3uF4rJw45Gr45J390k3Z8W3WvgF4xKF1jva9Fgw18J3Z0 yr1qgr9xCa1UAaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU7mb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VWkCwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK64x0aVW7Gw IE548m6rI_Jw1UWr17M2vj6xkI62vS6c8GOVWUtr1rJFylYx0E2Ix0cI8IcVAFwI0_JrI_ JrylYx0Ex4A2jsIE14v26r1j6r4UM4x0Y48IcVAKI48JMx8GjcxK6IxK0xIIj40E5I8Crw CYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI7VAKI48JMxCIbVAxMI8E67AF67kF1VAF wI0_Jrv_JF1lIxkGc2Ij64vIr4UvcSsGvfC2KfnxnUUI43ZEXa7IU0x9N3UUUUU==
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQIGEko7lOuDeAAAsi
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 19 Oct 2011 01:34:46 -0000

This is a multi-part message in MIME format.
--------------030306060703000104020203
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

hi,

On 10/19/2011 6:21 AM, Maoke wrote:
> hi Jacni,
> åœ¨ 2011å¹´10æœˆ18æ—¥ ä¸Šå�ˆ11:54ï¼ŒJacni Qin <jacni@jacni.com 
> <mailto:jacni@jacni.com>>å†™ é�“ï¼š
>
>>     1) list all mutually exclusive IPv4 networks to be involved in
>>     the residual deployment, i.e., Rule IPv4 prefixes;
>>     2) calculate IPv6 prefix length for each Rule IPv4 prefix,
>     For clarifications, you mean the "Rule IPv6 Prefix" length, right?
>     since the length of Delegated Prefix should have been settled
>     before this step.
>
> sure. i meant the Rule IPv6 Prefix length. :)
Ok, good.

> there is still another issue, the MAX PSID. personally i like the 
> algorithm of making longest-match for the PSID. however, the position 
> of the PSID is somehow a problem. in the step 2) (or a little before), 
> when you setting the delegated prefix length, this length only covers 
> the IPv4 suffix and the PSID itself, right?
The Max PSID idea has been dropped by restoring the parameter "L", in 
each rule.


Cheers,
Jacni

> then if the length is, e.g., /64, and the PSID occupies the last 4 
> bits. then the MAX PSID for a CE is put at 60 ~ 71 bits. this is fine 
> with the routing, which can get the encapsulated stuff to the right 
> CE. however, it may hurt the IID to some extent, for example, we have 
> the PSID=0x4, while for a certain packet, it contains destination port 
> 0xe488, then the MAX PSID = 0x488, and then the IID part for this 
> packet towards the dst CE will be not 200:5efe:: any more but
>            8800:5efe::
> right? making the "u" bit destroyed, and the destination CE cannot 
> identify this is a packet for encapsulation or a packet for direct 
> forwarding. it also detroys the V-bit in the unified address format.
> thus, may i understand that the planning should accommodate the MAX 
> PSID in the first 64 bits as well? if so, can we really satisfy the 
> requirement R-1 at the Beijing interim, stating "Efficient bit 
> representation.  Address + Port range in =/56", if the PSID is less 
> than 4 bits?
> sorry if i made anything, wrong. just try to understand the design, 
> its strength and limitations.
> best,
> maoke
>
>
>     Cheers,
>     Jacni
>

--------------030306060703000104020203
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 10/19/2011 6:21 AM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com"
      type="cite">hi Jacni, <br>
      <div class="gmail_quote">åœ¨ 2011å¹´10æœˆ18æ—¥ ä¸Šå�ˆ11:54ï¼ŒJacni Qin <span
          dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:jacni@jacni.com" target="_blank">jacni@jacni.com</a>&gt;</span>å†™
        é�“ï¼š<br>
        <blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex;
          border-left-color: rgb(204, 204, 204); border-left-width: 1px;
          border-left-style: solid;" class="gmail_quote">
          <div text="#000000" bgcolor="#FFFFFF">
            Â Â Â 
            <blockquote type="cite">
              <div>
                <div class="gmail_quote">
                  <div>1) list all mutually exclusive IPv4 networks to
                    be involved in the residual deployment, i.e., Rule
                    IPv4 prefixes;Â </div>
                  <div>2) calculate IPv6 prefix length for each Rule
                    IPv4 prefix, </div>
                </div>
              </div>
            </blockquote>
            For clarifications, you mean the "Rule IPv6 Prefix" length,
            right? since the length of Delegated Prefix should have been
            settled before this step.<br>
            <br>
          </div>
        </blockquote>
        <div>Â </div>
        <div>sure. i meant the Rule IPv6 Prefix length. :)</div>
        <div>Â </div>
      </div>
    </blockquote>
    Ok, good.<br>
    <br>
    <blockquote
cite="mid:CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>there is still another issue, the MAX PSID. personally i
          like the algorithm of making longest-match for the PSID.
          however, the position of the PSID is somehow a problem. in the
          step 2) (or a little before), when you setting the delegated
          prefix length, this length only covers the IPv4 suffix and the
          PSID itself, right? </div>
        <div>Â </div>
      </div>
    </blockquote>
    The Max PSID idea has been dropped by restoring the parameter "L",
    in each rule.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>then if the length is, e.g., /64, and the PSID occupies the
          last 4 bits. then the MAX PSID for a CE is put atÂ 60 ~ 71
          bits. this is fine with the routing, which can get the
          encapsulated stuff to the right CE. however, it may hurt the
          IID to some extent, for example, we have the PSID=0x4, while
          for a certain packet, it contains destination port 0xe488,
          then the MAX PSID = 0x488, and then the IID part for this
          packetÂ towards theÂ dst CE will be not 200:5efe:: any more butÂ </div>
        <div>Â </div>
        <div>Â Â Â Â Â Â Â Â Â Â  8800:5efe:: </div>
        <div>Â </div>
        <div>right? making the "u" bit destroyed, and the destination CE
          cannot identify this is a packet for encapsulation or a packet
          for direct forwarding. it also detroys the V-bit in the
          unified address format. </div>
        <div>Â </div>
        <div>thus, may i understand that the planning should accommodate
          the MAX PSID in the first 64 bits as well? if so, can we
          really satisfy the requirement R-1 at the Beijing interim,
          stating "Efficient bit representation.Â  Address + Port range
          in =/56", if the PSID is less than 4 bits? </div>
        <div>Â </div>
        <div>sorry if i made anything, wrong. just try to understand the
          design, its strength and limitations. </div>
        <div>Â </div>
        <div>best,</div>
        <div>maoke</div>
        <div>Â </div>
        <blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex;
          border-left-color: rgb(204, 204, 204); border-left-width: 1px;
          border-left-style: solid;" class="gmail_quote">
          <div text="#000000" bgcolor="#FFFFFF"> <br>
            Cheers,<br>
            <font color="#888888"> Jacni</font><br>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>

--------------030306060703000104020203--


From fibrib@gmail.com  Tue Oct 18 19:07:14 2011
Return-Path: <fibrib@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 B289A1F0C3D for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 19:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.283
X-Spam-Level: 
X-Spam-Status: No, score=-3.283 tagged_above=-999 required=5 tests=[AWL=0.315,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmtw-WcRmhwB for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 19:07:14 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0331F0C35 for <softwires@ietf.org>; Tue, 18 Oct 2011 19:07:14 -0700 (PDT)
Received: by qyk31 with SMTP id 31so1083027qyk.10 for <softwires@ietf.org>; Tue, 18 Oct 2011 19:07:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=a6IChE4jtdYEk+sTNFAU8u7s+o3NOCtz89kATK6pSjY=; b=QBv5U4LFWo94okPtQipbnfGEH/v+D6sQTIhfSZwqSYG2kQvY5iKFRFHzDuWssuPmib 7fRh2cXuCcdP3HisPrqOQIl+m144FKBbuly8DRRCP/9FHhF6m/H06VFUMEFtoB19oSM6 inJJF8MPvw8SQLUq2g/APZa2SHa+8VCRzP+q0=
MIME-Version: 1.0
Received: by 10.229.63.194 with SMTP id c2mr1056891qci.69.1318989619176; Tue, 18 Oct 2011 19:00:19 -0700 (PDT)
Received: by 10.229.175.205 with HTTP; Tue, 18 Oct 2011 19:00:18 -0700 (PDT)
In-Reply-To: <4E9E2987.6070407@jacni.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com> <4E9E2987.6070407@jacni.com>
Date: Wed, 19 Oct 2011 11:00:18 +0900
Message-ID: <CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=0016e64fcd8ab6a55004af9d33db
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 19 Oct 2011 02:07:14 -0000

--0016e64fcd8ab6a55004af9d33db
Content-Type: text/plain; charset=ISO-8859-1

hi Jacni,

2011/10/19 Jacni Qin <jacni@jacni.com>

>  there is still another issue, the MAX PSID. personally i like the
> algorithm of making longest-match for the PSID. however, the position of the
> PSID is somehow a problem. in the step 2) (or a little before), when you
> setting the delegated prefix length, this length only covers the IPv4 suffix
> and the PSID itself, right?
>
>
>
> The Max PSID idea has been dropped by restoring the parameter "L", in each
> rule.
>

then it is a parameter in configuration or embedded into the address format?
a single value over the domain or possible variable among different shared
IPv4 addresses? (to my understanding, one address should have a common value
of PSID length for all the CEs sharing the address, right?)

thanks and regards,
maoke


>
>
> Cheers,
> Jacni
>

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

<div>hi Jacni,=A0</div><br><div class=3D"gmail_quote">2011/10/19 Jacni Qin =
<span dir=3D"ltr">&lt;<a href=3D"mailto:jacni@jacni.com">jacni@jacni.com</a=
>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    there is still another issue, the MAX PSID. personally i
          like the algorithm of making longest-match for the PSID.
          however, the position of the PSID is somehow a problem. in the
          step 2) (or a little before), when you setting the delegated
          prefix length, this length only covers the IPv4 suffix and the
          PSID itself, right?=A0<div class=3D"im"><blockquote type=3D"cite"=
><div class=3D"gmail_quote">
        <div>=A0</div>
      </div>
    </blockquote></div>
    The Max PSID idea has been dropped by restoring the parameter &quot;L&q=
uot;,
    in each rule.<br></div></blockquote><div><br></div><div>then it is a pa=
rameter in configuration or embedded into the address format? a single valu=
e over the domain or possible variable among different shared IPv4 addresse=
s? (to my understanding, one address should have a common value of PSID len=
gth for all the CEs sharing the address, right?)</div>
<div><br></div><div>thanks and regards,</div><div>maoke</div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    <br>
    Cheers,<br><font color=3D"#888888">
    Jacni</font></div></blockquote></div><br>

--0016e64fcd8ab6a55004af9d33db--

From jacni@jacni.com  Tue Oct 18 20:18:01 2011
Return-Path: <jacni@jacni.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 ACC1521F87C5 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 20:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.942
X-Spam-Level: 
X-Spam-Status: No, score=-1.942 tagged_above=-999 required=5 tests=[AWL=0.345,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eLhJKbc3m2G6 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 20:18:01 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 27C1621F8797 for <softwires@ietf.org>; Tue, 18 Oct 2011 20:18:00 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 831A838006E for <softwires@ietf.org>; Tue, 18 Oct 2011 23:17:59 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 0BA09340115 for <softwires@ietf.org>; Wed, 19 Oct 2011 11:17:56 +0800 (CST)
Received: from [172.16.181.170] (unknown [221.11.61.39]) by app (Coremail) with SMTP id +AWowJAL6QRVQZ5OOCgfAA--.7981S2; Wed, 19 Oct 2011 11:17:54 +0800 (CST)
Message-ID: <4E9E41C5.502@jacni.com>
Date: Wed, 19 Oct 2011 11:19:33 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com> <4E9E2987.6070407@jacni.com> <CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com>
In-Reply-To: <CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060602070203060301020802"
X-CM-TRANSID: +AWowJAL6QRVQZ5OOCgfAA--.7981S2
X-Coremail-Antispam: 1UD129KBjvdXoWrKF4UGr4xWw45GrWDCw1DGFg_yoWDCwbE9a nYg3srKwnrXrWfCa1fKr45Jr9rJayjkryUGry8Wr4xA3409an3Aan7WrySqFyYqayYy3sx GFnaqw4xAry29jkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUjbkYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF 6F4UM7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1ln4vEF7Iv6F18KV Aqrcv_GVWUtr1rJF1lnx0Ec2IEnICE548m6r1DJrWUZwAv7VC0I7IYx2IY67AKxVWUJVWU GwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMx k0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2Ij64vIr41l4IxY624lx4CE17CEb7AF67AK xVWUXVWUAwCIc40Y0x0EwIxGrbIYCTnIWIevJa73UjIFyTuYvjxUs0PSUUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEGEko7lOuVvQAAsy
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 19 Oct 2011 03:18:01 -0000

This is a multi-part message in MIME format.
--------------060602070203060301020802
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hi,

On 10/19/2011 10:00 AM, Maoke wrote:
> hi Jacni,
>
> 2011/10/19 Jacni Qin <jacni@jacni.com <mailto:jacni@jacni.com>>
>
>     there is still another issue, the MAX PSID. personally i like the
>     algorithm of making longest-match for the PSID. however, the
>     position of the PSID is somehow a problem. in the step 2) (or a
>     little before), when you setting the delegated prefix length, this
>     length only covers the IPv4 suffix and the PSID itself, right?
>     The Max PSID idea has been dropped by restoring the parameter "L",
>     in each rule.
>
>
> then it is a parameter in configuration or embedded into the address 
> format?
It's a parameter in the rule.

> a single value over the domain or possible variable among different 
> shared IPv4 addresses? (to my understanding, one address should have a 
> common value of PSID length for all the CEs sharing the address, right?)
The number of L equals the number of Delegated Prefixes of different 
lengths totally within a given domain, which should be determined during 
IPv6 address planning.



Cheers,
Jacni

>
> thanks and regards,
> maoke
>
>
>
>     Cheers,
>     Jacni
>
>

--------------060602070203060301020802
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 10/19/2011 10:00 AM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com"
      type="cite">
      <div>hi Jacni,&nbsp;</div>
      <br>
      <div class="gmail_quote">2011/10/19 Jacni Qin <span dir="ltr">&lt;<a
            moz-do-not-send="true" href="mailto:jacni@jacni.com">jacni@jacni.com</a>&gt;</span><br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000"> there is still another
            issue, the MAX PSID. personally i like the algorithm of
            making longest-match for the PSID. however, the position of
            the PSID is somehow a problem. in the step 2) (or a little
            before), when you setting the delegated prefix length, this
            length only covers the IPv4 suffix and the PSID itself,
            right?&nbsp;
            <div class="im">
              <blockquote type="cite">
                <div class="gmail_quote">
                  <div>&nbsp;</div>
                </div>
              </blockquote>
            </div>
            The Max PSID idea has been dropped by restoring the
            parameter "L", in each rule.<br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>then it is a parameter in configuration or embedded into
          the address format? </div>
      </div>
    </blockquote>
    It's a parameter in the rule.<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>a single value over the domain or possible variable among
          different shared IPv4 addresses? (to my understanding, one
          address should have a common value of PSID length for all the
          CEs sharing the address, right?)</div>
      </div>
    </blockquote>
    The number of L equals the number of Delegated Prefixes of different
    lengths totally within a given domain, which should be determined
    during IPv6 address planning.<br>
    <br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div><br>
        </div>
        <div>thanks and regards,</div>
        <div>maoke</div>
        <div>&nbsp;</div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000"> <br>
            <br>
            Cheers,<br>
            <font color="#888888"> Jacni</font></div>
        </blockquote>
      </div>
      <br>
    </blockquote>
  </body>
</html>

--------------060602070203060301020802--


From fibrib@gmail.com  Tue Oct 18 22:50:33 2011
Return-Path: <fibrib@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 9D4B611E8087 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 22:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.306
X-Spam-Level: 
X-Spam-Status: No, score=-3.306 tagged_above=-999 required=5 tests=[AWL=0.292,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S49fzjT+7J6v for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 22:50:32 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 3D2B911E8080 for <softwires@ietf.org>; Tue, 18 Oct 2011 22:50:32 -0700 (PDT)
Received: by qyk31 with SMTP id 31so1155680qyk.10 for <softwires@ietf.org>; Tue, 18 Oct 2011 22:50:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jdA2J6JlywKBtCVdBayidfVTK1wAHUPWYutHNL+mELs=; b=fInCikrd0wCBYVzUhF/kRL9LFt75OKUGmeoy6HJBSFrO4FcUl+VZbugLjkO6yDyxnz lkVdOHtEuDwgOF0tNzlOhS2UmubqLHsnGjhMBeIU+Qboux5Fi9CMYc/saZhwu39ncBLa CPS6OZUTrKjwKPZa59hLiM+Ef08aIVAPEIlxQ=
MIME-Version: 1.0
Received: by 10.229.67.149 with SMTP id r21mr1145121qci.183.1319003431782; Tue, 18 Oct 2011 22:50:31 -0700 (PDT)
Received: by 10.229.175.205 with HTTP; Tue, 18 Oct 2011 22:50:31 -0700 (PDT)
In-Reply-To: <4E9E41C5.502@jacni.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com> <4E9E2987.6070407@jacni.com> <CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com> <4E9E41C5.502@jacni.com>
Date: Wed, 19 Oct 2011 14:50:31 +0900
Message-ID: <CAFUBMqUHG2PdBa1mfyja=LM9eVKu=LMfgxvGzsMoeyFB8Au+YQ@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=00163628429e024a6304afa06b2c
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 19 Oct 2011 05:50:33 -0000

--00163628429e024a6304afa06b2c
Content-Type: text/plain; charset=ISO-8859-1

hi,

2011/10/19 Jacni Qin <jacni@jacni.com>

>
>  a single value over the domain or possible variable among different
> shared IPv4 addresses? (to my understanding, one address should have a
> common value of PSID length for all the CEs sharing the address, right?)
>
> The number of L equals the number of Delegated Prefixes of different
> lengths totally within a given domain, which should be determined during
> IPv6 address planning.
>
>
they are equal to each other. but which determines which, in or before the
IPv6 address planning? delegated prefix length decides PSID length (sharing
ratio), or inversely? is it not that the sharing ratio is determined by how
many CEs sharing a unique IPv4 address?

best,
maoke


> Cheers,
> Jacni
>

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

hi,=A0<br><br><div class=3D"gmail_quote">2011/10/19 Jacni Qin <span dir=3D"=
ltr">&lt;<a href=3D"mailto:jacni@jacni.com">jacni@jacni.com</a>&gt;</span><=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex;">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div>a single value over the domain or possible variable among
          different shared IPv4 addresses? (to my understanding, one
          address should have a common value of PSID length for all the
          CEs sharing the address, right?)</div>
      </div>
    </blockquote>
    The number of L equals the number of Delegated Prefixes of different
    lengths totally within a given domain, which should be determined
    during IPv6 address planning.<br>
    <br>
    </div></blockquote><div><br></div><div>they are equal to each other. bu=
t which determines which, in or before the IPv6 address planning? delegated=
 prefix length decides PSID length (sharing ratio), or inversely? is it not=
 that the sharing ratio is determined by how many CEs sharing a unique IPv4=
 address?=A0</div>
<div><br></div><div>best,</div><div>maoke</div><div>=A0 =A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex;"><div bgcolor=3D"#FFFFFF" text=3D"#000000">Cheers,<br>=
<font color=3D"#888888">
    Jacni</font></div></blockquote></div><br>

--00163628429e024a6304afa06b2c--

From jacni@jacni.com  Wed Oct 19 00:50:27 2011
Return-Path: <jacni@jacni.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 AB96521F8B32 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 00:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.966
X-Spam-Level: 
X-Spam-Status: No, score=-1.966 tagged_above=-999 required=5 tests=[AWL=0.321,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZCkWSNPBKc4 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 00:50:26 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 235F821F8B27 for <softwires@ietf.org>; Wed, 19 Oct 2011 00:50:25 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id CD2DD3800AD for <softwires@ietf.org>; Wed, 19 Oct 2011 03:50:24 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 2964F340135 for <softwires@ietf.org>; Wed, 19 Oct 2011 15:50:23 +0800 (CST)
Received: from [172.16.181.170] (unknown [221.11.61.39]) by app (Coremail) with SMTP id +AWowJBLKAQ6gZ5OfWQfAA--.33480S2; Wed, 19 Oct 2011 15:50:20 +0800 (CST)
Message-ID: <4E9E81AA.5000009@jacni.com>
Date: Wed, 19 Oct 2011 15:52:10 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com> <4E9E2987.6070407@jacni.com> <CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com> <4E9E41C5.502@jacni.com> <CAFUBMqUHG2PdBa1mfyja=LM9eVKu=LMfgxvGzsMoeyFB8Au+YQ@mail.gmail.com>
In-Reply-To: <CAFUBMqUHG2PdBa1mfyja=LM9eVKu=LMfgxvGzsMoeyFB8Au+YQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040903010409050604090106"
X-CM-TRANSID: +AWowJBLKAQ6gZ5OfWQfAA--.33480S2
X-Coremail-Antispam: 1UD129KBjvdXoWrur4DWF43Ar47WryUJF43Wrg_yoWftFcE93 4Dtw1DG347Jw4UGa13JF4rJry7Aayjyr1UKry09Fs7C34Fkanavr1IgryavrW5JFW5t3sx GFnIqw4xAry29jkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUjbkYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF 6FyUM7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1ln4vEF7Iv6F18KV Aqrcv_GVWUtr1rJF1lnx0Ec2IEnICE548m6r1DJrWUZwAv7VC0I7IYx2IY67AKxVWUGVWU XwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMx k0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2Ij64vIr41l4IxY624lx4CE17CEb7AF67AK xVWUXVWUAwCIc40Y0x0EwIxGrbIYCTnIWIevJa73UjIFyTuYvjxUIcTmDUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQAGEko7lOu6fAAAsd
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 19 Oct 2011 07:50:27 -0000

This is a multi-part message in MIME format.
--------------040903010409050604090106
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

hi,

On 10/19/2011 1:50 PM, Maoke wrote:
> hi,
>
> 2011/10/19 Jacni Qin <jacni@jacni.com <mailto:jacni@jacni.com>>
>
>
>>     a single value over the domain or possible variable among
>>     different shared IPv4 addresses? (to my understanding, one
>>     address should have a common value of PSID length for all the CEs
>>     sharing the address, right?)
>     The number of L equals the number of Delegated Prefixes of
>     different lengths totally within a given domain, which should be
>     determined during IPv6 address planning.
>
>
> they are equal to each other. but which determines which, in or before 
> the IPv6 address planning?
IMHO, I guess the length of Delegated Prefix settled in phase of the 
native IPv6 address planning without considering anything about IPv4 
addressing, determines the L.


Cheers,
Jacni

> delegated prefix length decides PSID length (sharing ratio), or 
> inversely? is it not that the sharing ratio is determined by how many 
> CEs sharing a unique IPv4 address?
>
> best,
> maoke
>
>     Cheers,
>     Jacni
>
>

--------------040903010409050604090106
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 10/19/2011 1:50 PM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqUHG2PdBa1mfyja=LM9eVKu=LMfgxvGzsMoeyFB8Au+YQ@mail.gmail.com"
      type="cite">hi,Â <br>
      <br>
      <div class="gmail_quote">2011/10/19 Jacni Qin <span dir="ltr">&lt;<a
            moz-do-not-send="true" href="mailto:jacni@jacni.com">jacni@jacni.com</a>&gt;</span><br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000"> <br>
            <blockquote type="cite">
              <div class="gmail_quote">
                <div>a single value over the domain or possible variable
                  among different shared IPv4 addresses? (to my
                  understanding, one address should have a common value
                  of PSID length for all the CEs sharing the address,
                  right?)</div>
              </div>
            </blockquote>
            The number of L equals the number of Delegated Prefixes of
            different lengths totally within a given domain, which
            should be determined during IPv6 address planning.<br>
            <br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>they are equal to each other. but which determines which,
          in or before the IPv6 address planning? </div>
      </div>
    </blockquote>
    IMHO, I guess the length of Delegated Prefix settled in phase of the
    native IPv6 address planning without considering anything about IPv4
    addressing, determines the L.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAFUBMqUHG2PdBa1mfyja=LM9eVKu=LMfgxvGzsMoeyFB8Au+YQ@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>delegated prefix length decides PSID length (sharing
          ratio), or inversely? is it not that the sharing ratio is
          determined by how many CEs sharing a unique IPv4 address?Â </div>
        <div><br>
        </div>
        <div>best,</div>
        <div>maoke</div>
        <div>Â  Â </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000">Cheers,<br>
            <font color="#888888"> Jacni</font></div>
        </blockquote>
      </div>
      <br>
    </blockquote>
  </body>
</html>

--------------040903010409050604090106--


From despres.remi@laposte.net  Wed Oct 19 00:51:03 2011
Return-Path: <despres.remi@laposte.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 7A31321F8B3B for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 00:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.784
X-Spam-Level: 
X-Spam-Status: No, score=-1.784 tagged_above=-999 required=5 tests=[AWL=0.165,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYW0iV8i+XGK for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 00:51:02 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.22]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7A421F8B2A for <softwires@ietf.org>; Wed, 19 Oct 2011 00:51:02 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2316.sfr.fr (SMTP Server) with ESMTP id BF3CD70000EB; Wed, 19 Oct 2011 09:50:59 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2316.sfr.fr (SMTP Server) with ESMTP id 42FDC70000E2; Wed, 19 Oct 2011 09:50:57 +0200 (CEST)
X-SFR-UUID: 20111019075057274.42FDC70000E2@msfrf2316.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <4E9DDB22.9000908@gmail.com>
Date: Wed, 19 Oct 2011 09:50:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <50357926-C09B-4BFE-B7AB-976B48C0E704@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <4E9C8D5C.4060706@gmail.com> <B83FCD09-0563-4DC3-ADDC-92E0DAA32030@laposte.net> <4E9DDB22.9000908@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] ECN [4rd-U complement - e2e transparency to IPv4 TOS]
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, 19 Oct 2011 07:51:03 -0000

Le 18 oct. 2011 =E0 22:01, Brian E Carpenter a =E9crit :

> On 2011-10-18 19:55, R=E9mi Despr=E9s wrote:
>> Le 17 oct. 2011 =E0 22:17, Brian E Carpenter a =E9crit :
>>=20
>>> On 2011-10-18 01:36, R=E9mi Despr=E9s wrote:
>>>> Hi Satoru-san,
>>>>=20
>>>> Thank you for identifying a limitation of the 4rd-U =20
>>>> You are right, as currently specified, "it doesn't support =
diff-serv tunneling model, pipe and short-pipe".
>>>> All these need e2e transparency to the IPv4 Type of Service.
>>>>=20
>>>> Fortunately, this is easy to fix:
>>=20
>> *
>>>> in the Identification field of the IPv6 Fragment header, copy not =
only the DF bits but also the IPv4 TOS.
>> *
>>=20
>>> Will this cause any difficulties for ECN, if ECN is supported on the =
IPv6
>>> leg of the journey?
>>=20
>> Not in my understanding.
>> Since the IPv4 TOS is copied in the Identification field of the IPv6 =
Fragment header, it will be restored at exit of the IPv6 leg =
independently of any MPLS and ECN that may be used in that leg.
>=20
> That's my problem. If the IPv6 leg supports ECN, any change to the ECN =
bits
> during the IPv6 journey will be lost, so the end systems will not be =
informed
> about congestion. I think the ECN bits need to be copied to and from =
the IPv6
> Traffic Class.

Thanks for the clarification.
Whether ECN is deployed or not is beyond my current knowledge, but I now =
understand that this issue exists, and is applicable to 4rd-U as it is =
to encapsulation.=20

>>> Apart from that, please remember that the DSCP part of the DS Field =
is not an
>>> end-to-end field; it is mutable.
>>=20
>>> I advise applying the relevant considerations
>>> from Sections 4.1 and 5.1 of RFC 6145.
>>=20
>> This isn't necessary because RFC 6145 is about Translation, while =
4rd-U, with the above between asterisks, precisely avoids translations =
between IPv4 TOS and IPv6 Traffic.=20
>> In this respect, is more like 4rd Encapsulation than like 4rd =
Translation.
>=20
> Firstly, that means that any diffserv treatment specified for the IPv4 =
packet is
> missed during the IPv6 journey. So as for ECN, the IPv4 DSCP value =
should probably
> be copied into the the IPv6 traffic class.

Using the same field for ECN and for QoS differentiation seems to me a =
source of difficulty.
A minimal approach seems to be treating IPv6-domain traversal as just =
one link traversal.  =20


> Second, as discussed in RFC 6145 section 5.1,
> the diffserv code point might be rewritten at the exit from IPv6.

> Please also see the extensive discussion about diffserv and tunnels in =
RFC 2983.
> Actually the treatment in RFC 6145 was supposed to be roughly =
equivalent to RFC 2983.

Thanks for the reference.

Regards,
RD



From despres.remi@laposte.net  Wed Oct 19 01:07:15 2011
Return-Path: <despres.remi@laposte.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 50AC521F851A for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 01:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.163
X-Spam-Level: 
X-Spam-Status: No, score=-1.163 tagged_above=-999 required=5 tests=[AWL=-0.472, BAYES_00=-2.599, FB_YOU_CAN_BECOME=1.258, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMxfK+z7G0T4 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 01:07:14 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.22]) by ietfa.amsl.com (Postfix) with ESMTP id 3D64621F84D8 for <softwires@ietf.org>; Wed, 19 Oct 2011 01:07:14 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2316.sfr.fr (SMTP Server) with ESMTP id 8080770000F1; Wed, 19 Oct 2011 10:07:13 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2316.sfr.fr (SMTP Server) with ESMTP id 3002370000EB; Wed, 19 Oct 2011 10:07:13 +0200 (CEST)
X-SFR-UUID: 20111019080713196.3002370000EB@msfrf2316.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <63DB920E-8768-47BD-8185-959C4165977B@townsley.net>
Date: Wed, 19 Oct 2011 10:07:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D8CC5D14-34F2-4A00-8051-7114F8945134@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net> <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net> <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net> <5F044EAF-A653-499B-86B1-993CA77D1071@laposte.net> <0B52D2A1-9938-48A8-A87C-27DE39405263@townsley.net> <DF8BF1B0-63DB-4F9B-BE96-4D214513C0DC@laposte.net> <63DB920E-8768-47BD-8185-959C4165977B@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Standardizing "4rd-U" vs "4rd-Encapsulation AND Double translation - analysis
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, 19 Oct 2011 08:07:15 -0000

Mark,
More on this debate below.

Le 18 oct. 2011 =E0 19:44, Mark Townsley a =E9crit :
> On Oct 18, 2011, at 4:31 PM, R=E9mi Despr=E9s wrote:
...
>> Could you explain the important advantage of encapsulation that is =
missing in 4rd-U?
>=20
> It's been specified and implemented for years, it is part of other =
softwires specifications, it is being implemented in CPE equipment today =
as part of ds-lite, it doesn't put payloads on the wire with =
mis-matching checksums.... Sure, tunneling doesn't play nice with some =
ACLs that only look at native IPv6, but at least this is a very =
well-understood attribute of tunneling that operators expect and in many =
cases are able to design around. FWIW, my crystal ball says that these =
limitations will will become less and less relevant if and when 4-in-6 =
operation becomes more and more prevalent, but that's just me.


> Translation based on what's already defined in the behave WG is less =
conservative than simple encapsulation, but at least it is building on =
something that already exists, is well-specified and deployed, etc.

Successfully deployed in production, not so sure. (Even IPv6 isn't that =
largely deployed today).
In any case, it has the side effect that it damages network transparency =
to IPv4 packets.

> We can expect to see IPv4 payloads with IPv6 headers on the network =
because of translators, but at least the checksums will be correct

For ISP networks where web redirection with existing IPv6 tools is =
needed, 4rd-U could be completed so that checksums are correct.
This can be done like in dIVI by checksum adjustments at IPv6-domain =
entrance and exit, or (better IMHO) by revising the unified =
address-mapping to make it checksum neutral (something Ole has in my =
understanding suggested).=20

Thanks for pointing out that something was missing to get the best of =
both worlds.

> and there is a decent chance that a host will be able to digest the =
packet and get it to a working application after passing through one =
level of translation (or being redirected, subjected to DPI, etc).=20
>=20
> Again, no offense at all to the ingenuity of -U, but I simply have a =
hard time justifying that we need to cast a balance between these =
relatively well-known, specified, and implemented building-blocks with =
something new.=20

New, yes, but quite simple, and with an immediate operational advantage.
=20
> If I believed for a microsecond that -U would wipe both encapsulation =
and translation from the planet so that we would have only one mechanism =
here, I would be more supportive. The problem is that the other two =
already exist in other closely related contexts such that there is no =
way that this doesn't become a 3rd method in the network without turning =
back time itself.

Assuming that the three solutions would be available in products, I =
don't see why an ISP would prefer to keep double translation or =
encapsulation:
- The fact that translations and encapsulations were first to exist IS =
NOT an operational advantage
- Having both of network transparency to IPv4 AND applicability of IPv6 =
O&M tools IS an operational advantage.=20

I still hope that, with more thoughts on the subject, you can become =
more open. =20

Regards,
RD


From fibrib@gmail.com  Wed Oct 19 04:33:12 2011
Return-Path: <fibrib@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 E9CAB21F8B14 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 04:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.325
X-Spam-Level: 
X-Spam-Status: No, score=-3.325 tagged_above=-999 required=5 tests=[AWL=0.273,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4Ri53NPOo45 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 04:33:12 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id E0F7021F8B0E for <softwires@ietf.org>; Wed, 19 Oct 2011 04:33:11 -0700 (PDT)
Received: by qyk31 with SMTP id 31so1362479qyk.10 for <softwires@ietf.org>; Wed, 19 Oct 2011 04:33:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XN+7fS1R9hDIwat4fmriHNX2IXDcnBtpAAcXO9U8IbE=; b=rUkhHdYh05TZF6wsBmZQWaEHQWQqTvwSZJ3W1cyt5zJWLoC2Hb8uSw+Fvd/N+x2+c2 j3R/jgw1EcpsSLS/QmHd5yATbeatKeepDmaWqzUrqI6T7ZyOmxbiO0eu+zYfXHWZc5hR XTh2A3Q2c4yemlZehoTapGcbz+24U8kaA560M=
MIME-Version: 1.0
Received: by 10.229.62.195 with SMTP id y3mr1370675qch.31.1319023991321; Wed, 19 Oct 2011 04:33:11 -0700 (PDT)
Received: by 10.229.175.205 with HTTP; Wed, 19 Oct 2011 04:33:11 -0700 (PDT)
In-Reply-To: <4E9E81AA.5000009@jacni.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com> <4E9E2987.6070407@jacni.com> <CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com> <4E9E41C5.502@jacni.com> <CAFUBMqUHG2PdBa1mfyja=LM9eVKu=LMfgxvGzsMoeyFB8Au+YQ@mail.gmail.com> <4E9E81AA.5000009@jacni.com>
Date: Wed, 19 Oct 2011 20:33:11 +0900
Message-ID: <CAFUBMqXRJ1obTJD6_6MQ2jGJVua1y5WqfDJ9-Nq8x2KJU7Ys3w@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=0016e64b1d5673f2e104afa5348a
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 19 Oct 2011 11:33:13 -0000

--0016e64b1d5673f2e104afa5348a
Content-Type: text/plain; charset=ISO-8859-1

2011/10/19 Jacni Qin <jacni@jacni.com>


> hi,
>

> On 10/19/2011 1:50 PM, Maoke wrote:
>
> hi,
>
> 2011/10/19 Jacni Qin <jacni@jacni.com>
>
>>
>>  a single value over the domain or possible variable among different
>> shared IPv4 addresses? (to my understanding, one address should have a
>> common value of PSID length for all the CEs sharing the address, right?)
>>
>> The number of L equals the number of Delegated Prefixes of different
>> lengths totally within a given domain, which should be determined during
>> IPv6 address planning.
>>
>>
>  they are equal to each other. but which determines which, in or before
> the IPv6 address planning?
>
> IMHO, I guess the length of Delegated Prefix settled in phase of the native
> IPv6 address planning without considering anything about IPv4 addressing,
> determines the L.
>
>
?? i suppose previously with your clarification you HAVE admitted your
consensus to my 1) ~ 4) as the logic of the operation, but now you said
"without considering anything about IPv4". may you clarify your process with
starting from the following example?

i allocate:
   CE1 2001:db9:8765:4320::/60
   CE2 2001:db8:7654:3210::/60
then the IPv6 address planning is finished according to your statement.

then what information should i use to determine the L for each? you mean the
IPv6 address planning is enough?

thanks,
maoke


> Cheers,
> Jacni
>
>
>  delegated prefix length decides PSID length (sharing ratio), or
> inversely? is it not that the sharing ratio is determined by how many CEs
> sharing a unique IPv4 address?
>
>  best,
> maoke
>
>
>> Cheers,
>>  Jacni
>>
>
>

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

<br><br><div class=3D"gmail_quote">2011/10/19 Jacni Qin <span dir=3D"ltr">&=
lt;<a href=3D"mailto:jacni@jacni.com">jacni@jacni.com</a>&gt;</span><br><di=
v>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor=3D"#FFFFFF" text=3D"#000000"><font face=3D"Calibri">hi,</font>=
=A0</div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor=3D"#FFFF=
FF" text=3D"#000000">
<div class=3D"im">
    <br>
    On 10/19/2011 1:50 PM, Maoke wrote:
    <blockquote type=3D"cite">hi,=A0<br>
      <br>
      <div class=3D"gmail_quote">2011/10/19 Jacni Qin <span dir=3D"ltr">&lt=
;<a href=3D"mailto:jacni@jacni.com" target=3D"_blank">jacni@jacni.com</a>&g=
t;</span><br>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
          <div bgcolor=3D"#FFFFFF" text=3D"#000000"> <br>
            <blockquote type=3D"cite">
              <div class=3D"gmail_quote">
                <div>a single value over the domain or possible variable
                  among different shared IPv4 addresses? (to my
                  understanding, one address should have a common value
                  of PSID length for all the CEs sharing the address,
                  right?)</div>
              </div>
            </blockquote>
            The number of L equals the number of Delegated Prefixes of
            different lengths totally within a given domain, which
            should be determined during IPv6 address planning.<br>
            <br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>they are equal to each other. but which determines which,
          in or before the IPv6 address planning? </div>
      </div>
    </blockquote></div>
    IMHO, I guess the length of Delegated Prefix settled in phase of the
    native IPv6 address planning without considering anything about IPv4
    addressing, determines the L.<br>
    <br>
    </div></blockquote><div><br></div><div>?? i suppose previously with you=
r clarification you HAVE admitted your consensus to my 1) ~ 4) as the logic=
 of the operation, but now you said &quot;without considering anything abou=
t IPv4&quot;. may you clarify your process with starting from the following=
 example?=A0</div>
<div><br></div><div>i allocate:=A0</div><div>=A0 =A0CE1 2001:db9:8765:4320:=
:/60</div><div>=A0 =A0CE2 2001:db8:7654:3210::/60</div><div>then the IPv6 a=
ddress planning is finished according to your statement.=A0</div><div><br><=
/div><div>
then what information should i use to determine the L for each? you mean th=
e IPv6 address planning is enough?=A0</div><div><br></div><div>thanks,</div=
><div>maoke</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor=3D"#FFFFFF" text=3D"#000000">Cheers,<br><font color=3D"#888888=
">
    Jacni</font><div class=3D"im"><br>
    <br>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div>delegated prefix length decides PSID length (sharing
          ratio), or inversely? is it not that the sharing ratio is
          determined by how many CEs sharing a unique IPv4 address?=A0</div=
>
        <div><br>
        </div>
        <div>best,</div>
        <div>maoke</div>
        <div>=A0 =A0</div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
          <div bgcolor=3D"#FFFFFF" text=3D"#000000">Cheers,<br>
            <font color=3D"#888888"> Jacni</font></div>
        </blockquote>
      </div>
      <br>
    </blockquote>
  </div></div>

</blockquote></div><br>

--0016e64b1d5673f2e104afa5348a--

From fibrib@gmail.com  Wed Oct 19 04:38:00 2011
Return-Path: <fibrib@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 6112121F8B40 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 04:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.192
X-Spam-Level: 
X-Spam-Status: No, score=-3.192 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51oB-el1GGMw for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 04:38:00 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id CD99F21F8B3E for <softwires@ietf.org>; Wed, 19 Oct 2011 04:37:59 -0700 (PDT)
Received: by qyk34 with SMTP id 34so2824381qyk.10 for <softwires@ietf.org>; Wed, 19 Oct 2011 04:37:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i9mxDFa8l/Zyf2IvHxmnX/JXVMgR9pZqopkFLt5kya8=; b=Ao/BALjxvLfnA5Dl3sFMl+2yldfHIIHFH4nfuctTl2QWwE41kfoumvLJn1ZK3h+vzB Th6t56YA5qS1JWEaUIZO9NWv/Anqc/K5vc72eiInmiIfY2CHeba3q1RM+KItb/GgtKgC aR8FRscl4Ke37CL3nWPaFvhmhonl7+SyEbYJE=
MIME-Version: 1.0
Received: by 10.229.63.194 with SMTP id c2mr1369283qci.69.1319024279238; Wed, 19 Oct 2011 04:37:59 -0700 (PDT)
Received: by 10.229.175.205 with HTTP; Wed, 19 Oct 2011 04:37:58 -0700 (PDT)
In-Reply-To: <E8946E9A-487A-44B1-98BF-B621834508BE@free.fr>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com> <E8946E9A-487A-44B1-98BF-B621834508BE@free.fr>
Date: Wed, 19 Oct 2011 20:37:58 +0900
Message-ID: <CAFUBMqWdw14Sr76fQScGudK5Zu668GFLrRWySGVY7HTo_L5E_Q@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: multipart/alternative; boundary=0016e64fcd8a9d37a504afa54563
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 19 Oct 2011 11:38:00 -0000

--0016e64fcd8a9d37a504afa54563
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Remi,

2011/10/19 R=E9mi Despr=E9s <remi.despres@free.fr>

> Hi Maoke,
>
> CE PSIDs are never such that CE IPv6 prefixes exceed /64.
> The Max PSID of a CE, as opposed to its exact PSID, is only used to reach
> the CE from a BR or other in which  CE IPv6-prefix length is unknown.
>

for finding the destination CE, even with no knowledge about its PSID
length, right?


>
> As shown in Figure 6-A of the addmapping draft, if the Max CE index that =
is
> derived from the destination A+P is such that Rule IPv6 prefix + Max CE
> index exceeds 64 bit, the Max CE index is truncated to 64 bits. None of t=
he
> 4rd-addmapping addresses has an IPv6 prefix longer than /64.
>
> Hope it clarifies.
>

then "truncated to 64 bits" clarifies. thank you, Remi, for the explanation=
.
:)

best,
maoke


> Regards,
> RD
>
>

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

hi Remi,=A0<br><br><div class=3D"gmail_quote">2011/10/19 R=E9mi Despr=E9s <=
span dir=3D"ltr">&lt;<a href=3D"mailto:remi.despres@free.fr">remi.despres@f=
ree.fr</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word">Hi Maoke,<div><br></div><div>CE PSIDs a=
re never such that CE IPv6 prefixes exceed /64.</div><div>The Max PSID of a=
 CE, as opposed to its exact PSID, is only used to reach the CE from a BR o=
r other in which =A0CE IPv6-prefix length is unknown.</div>
</div></blockquote><div><br></div><div>for finding the destination CE, even=
 with no knowledge about its PSID length, right?=A0</div><div>=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div><br></div><div>As shown in Figure =
6-A of the addmapping draft, if the Max CE index that is derived from the d=
estination A+P is such that Rule IPv6 prefix + Max CE index exceeds 64 bit,=
 the Max CE index is truncated to 64 bits. None of the 4rd-addmapping addre=
sses has an IPv6 prefix longer than /64.</div>
<div><br></div><div>Hope it clarifies.<br></div></div></blockquote><div><br=
></div><div>then &quot;truncated to 64 bits&quot; clarifies. thank you, Rem=
i, for the explanation. :)</div><div><br></div><div>best,</div><div>maoke=
=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:break=
-word"><div>Regards,</div><div>RD</div><div><br></div></div></blockquote></=
div>
<br>

--0016e64fcd8a9d37a504afa54563--

From sarikaya2012@gmail.com  Wed Oct 19 13:05:43 2011
Return-Path: <sarikaya2012@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 7F39321F84ED for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 13:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=-0.549, BAYES_00=-2.599, FB_YOU_CAN_BECOME=1.258, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVORWujjtT5v for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 13:05:42 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7B41621F84D3 for <softwires@ietf.org>; Wed, 19 Oct 2011 13:05:42 -0700 (PDT)
Received: by ggnv1 with SMTP id v1so2473182ggn.31 for <softwires@ietf.org>; Wed, 19 Oct 2011 13:05:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=qS8BU2O4k6LPeSCrCeU2VKTiaKSBjbqeJ7Wel+Iqcb8=; b=gzjQ7hWFlxrAOf8E5LtJ+ifpjAnv0D30hdkyUJuNJPn29AyBnmPNHXNPNlTrxAY4sB W+DMQ4mDGxZJNNO3E8FTU2ekWTq5x0793r4QvZGBv6xicemPkkTRTSPQK+8xRIG7Zg/L 6NgchjA96Gn6+yQTDCyyJ7Ebjzrp6DnIEYito=
MIME-Version: 1.0
Received: by 10.236.78.129 with SMTP id g1mr12288504yhe.52.1319054726499; Wed, 19 Oct 2011 13:05:26 -0700 (PDT)
Received: by 10.236.110.39 with HTTP; Wed, 19 Oct 2011 13:05:26 -0700 (PDT)
In-Reply-To: <D8CC5D14-34F2-4A00-8051-7114F8945134@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net> <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net> <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net> <5F044EAF-A653-499B-86B1-993CA77D1071@laposte.net> <0B52D2A1-9938-48A8-A87C-27DE39405263@townsley.net> <DF8BF1B0-63DB-4F9B-BE96-4D214513C0DC@laposte.net> <63DB920E-8768-47BD-8185-959C4165977B@townsley.net> <D8CC5D14-34F2-4A00-8051-7114F8945134@laposte.net>
Date: Wed, 19 Oct 2011 15:05:26 -0500
Message-ID: <CAC8QAcewMGEk9mg1v1ju=kwWkCdNojusfjAakXv=6LMo_AMzzA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=20cf300fb0c3698c9204afac5cca
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Standardizing "4rd-U" vs "4rd-Encapsulation AND Double translation - analysis
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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: Wed, 19 Oct 2011 20:05:43 -0000

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

I would like to see more details on 4rd-u before. Why is it informational? =
A
-01 would help.

Regards,

Behcet

On Wed, Oct 19, 2011 at 3:07 AM, R=E9mi Despr=E9s <despres.remi@laposte.net=
>wrote:

> Mark,
> More on this debate below.
>
> Le 18 oct. 2011 =E0 19:44, Mark Townsley a =E9crit :
> > On Oct 18, 2011, at 4:31 PM, R=E9mi Despr=E9s wrote:
> ...
> >> Could you explain the important advantage of encapsulation that is
> missing in 4rd-U?
> >
> > It's been specified and implemented for years, it is part of other
> softwires specifications, it is being implemented in CPE equipment today =
as
> part of ds-lite, it doesn't put payloads on the wire with mis-matching
> checksums.... Sure, tunneling doesn't play nice with some ACLs that only
> look at native IPv6, but at least this is a very well-understood attribut=
e
> of tunneling that operators expect and in many cases are able to design
> around. FWIW, my crystal ball says that these limitations will will becom=
e
> less and less relevant if and when 4-in-6 operation becomes more and more
> prevalent, but that's just me.
>
>
> > Translation based on what's already defined in the behave WG is less
> conservative than simple encapsulation, but at least it is building on
> something that already exists, is well-specified and deployed, etc.
>
> Successfully deployed in production, not so sure. (Even IPv6 isn't that
> largely deployed today).
> In any case, it has the side effect that it damages network transparency =
to
> IPv4 packets.
>
> > We can expect to see IPv4 payloads with IPv6 headers on the network
> because of translators, but at least the checksums will be correct
>
> For ISP networks where web redirection with existing IPv6 tools is needed=
,
> 4rd-U could be completed so that checksums are correct.
> This can be done like in dIVI by checksum adjustments at IPv6-domain
> entrance and exit, or (better IMHO) by revising the unified address-mappi=
ng
> to make it checksum neutral (something Ole has in my understanding
> suggested).
>
> Thanks for pointing out that something was missing to get the best of bot=
h
> worlds.
>
> > and there is a decent chance that a host will be able to digest the
> packet and get it to a working application after passing through one leve=
l
> of translation (or being redirected, subjected to DPI, etc).
> >
> > Again, no offense at all to the ingenuity of -U, but I simply have a ha=
rd
> time justifying that we need to cast a balance between these relatively
> well-known, specified, and implemented building-blocks with something new=
.
>
> New, yes, but quite simple, and with an immediate operational advantage.
>
> > If I believed for a microsecond that -U would wipe both encapsulation a=
nd
> translation from the planet so that we would have only one mechanism here=
, I
> would be more supportive. The problem is that the other two already exist=
 in
> other closely related contexts such that there is no way that this doesn'=
t
> become a 3rd method in the network without turning back time itself.
>
> Assuming that the three solutions would be available in products, I don't
> see why an ISP would prefer to keep double translation or encapsulation:
> - The fact that translations and encapsulations were first to exist IS NO=
T
> an operational advantage
> - Having both of network transparency to IPv4 AND applicability of IPv6 O=
&M
> tools IS an operational advantage.
>
> I still hope that, with more thoughts on the subject, you can become more
> open.
>
> Regards,
> RD
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

I would like to see more details on 4rd-u before. Why is it informational? =
A -01 would help.<br><br>Regards,<br><br>Behcet<br><br><div class=3D"gmail_=
quote">On Wed, Oct 19, 2011 at 3:07 AM, R=E9mi Despr=E9s <span dir=3D"ltr">=
&lt;<a href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</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;">Mark,<br>
More on this debate below.<br>
<br>
Le 18 oct. 2011 =E0 19:44, Mark Townsley a =E9crit :<br>
&gt; On Oct 18, 2011, at 4:31 PM, R=E9mi Despr=E9s wrote:<br>
...<br>
&gt;&gt; Could you explain the important advantage of encapsulation that is=
 missing in 4rd-U?<br>
&gt;<br>
&gt; It&#39;s been specified and implemented for years, it is part of other=
 softwires specifications, it is being implemented in CPE equipment today a=
s part of ds-lite, it doesn&#39;t put payloads on the wire with mis-matchin=
g checksums.... Sure, tunneling doesn&#39;t play nice with some ACLs that o=
nly look at native IPv6, but at least this is a very well-understood attrib=
ute of tunneling that operators expect and in many cases are able to design=
 around. FWIW, my crystal ball says that these limitations will will become=
 less and less relevant if and when 4-in-6 operation becomes more and more =
prevalent, but that&#39;s just me.<br>

<br>
<br>
&gt; Translation based on what&#39;s already defined in the behave WG is le=
ss conservative than simple encapsulation, but at least it is building on s=
omething that already exists, is well-specified and deployed, etc.<br>

<br>
Successfully deployed in production, not so sure. (Even IPv6 isn&#39;t that=
 largely deployed today).<br>
In any case, it has the side effect that it damages network transparency to=
 IPv4 packets.<br>
<br>
&gt; We can expect to see IPv4 payloads with IPv6 headers on the network be=
cause of translators, but at least the checksums will be correct<br>
<br>
For ISP networks where web redirection with existing IPv6 tools is needed, =
4rd-U could be completed so that checksums are correct.<br>
This can be done like in dIVI by checksum adjustments at IPv6-domain entran=
ce and exit, or (better IMHO) by revising the unified address-mapping to ma=
ke it checksum neutral (something Ole has in my understanding suggested).<b=
r>

<br>
Thanks for pointing out that something was missing to get the best of both =
worlds.<br>
<br>
&gt; and there is a decent chance that a host will be able to digest the pa=
cket and get it to a working application after passing through one level of=
 translation (or being redirected, subjected to DPI, etc).<br>
&gt;<br>
&gt; Again, no offense at all to the ingenuity of -U, but I simply have a h=
ard time justifying that we need to cast a balance between these relatively=
 well-known, specified, and implemented building-blocks with something new.=
<br>

<br>
New, yes, but quite simple, and with an immediate operational advantage.<br=
>
<br>
&gt; If I believed for a microsecond that -U would wipe both encapsulation =
and translation from the planet so that we would have only one mechanism he=
re, I would be more supportive. The problem is that the other two already e=
xist in other closely related contexts such that there is no way that this =
doesn&#39;t become a 3rd method in the network without turning back time it=
self.<br>

<br>
Assuming that the three solutions would be available in products, I don&#39=
;t see why an ISP would prefer to keep double translation or encapsulation:=
<br>
- The fact that translations and encapsulations were first to exist IS NOT =
an operational advantage<br>
- Having both of network transparency to IPv4 AND applicability of IPv6 O&a=
mp;M tools IS an operational advantage.<br>
<br>
I still hope that, with more thoughts on the subject, you can become more o=
pen.<br>
<br>
Regards,<br>
RD<br>
<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>
</blockquote></div><br>

--20cf300fb0c3698c9204afac5cca--

From jacni@jacni.com  Wed Oct 19 17:58:19 2011
Return-Path: <jacni@jacni.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 D7D0321F852E for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 17:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[AWL=0.299,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QmEHXa+VITc9 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 17:58:19 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 498EA21F8515 for <softwires@ietf.org>; Wed, 19 Oct 2011 17:58:18 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 81D6F38005F for <softwires@ietf.org>; Wed, 19 Oct 2011 20:58:17 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 14F873400FE for <softwires@ietf.org>; Thu, 20 Oct 2011 08:58:14 +0800 (CST)
Received: from [172.17.251.214] (unknown [221.11.61.147]) by app (Coremail) with SMTP id +AWowJB7YgUecp9OjfgfAA--.42687S2; Thu, 20 Oct 2011 08:58:13 +0800 (CST)
Message-ID: <4E9F728C.7050801@jacni.com>
Date: Thu, 20 Oct 2011 08:59:56 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com> <4E9E2987.6070407@jacni.com> <CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com> <4E9E41C5.502@jacni.com> <CAFUBMqUHG2PdBa1mfyja=LM9eVKu=LMfgxvGzsMoeyFB8Au+YQ@mail.gmail.com> <4E9E81AA.5000009@jacni.com> <CAFUBMqXRJ1obTJD6_6MQ2jGJVua1y5WqfDJ9-Nq8x2KJU7Ys3w@mail.gmail.com>
In-Reply-To: <CAFUBMqXRJ1obTJD6_6MQ2jGJVua1y5WqfDJ9-Nq8x2KJU7Ys3w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010408000102050302020202"
X-CM-TRANSID: +AWowJB7YgUecp9OjfgfAA--.42687S2
X-Coremail-Antispam: 1UD129KBjvJXoW7Cr13Aw1ktFykArWkXF1fWFg_yoW8AF4rpF WDt3WUJFs5AF1kJrs7Zw18Wr15AFn5Ja1UJa15G34IkFZ8Xan29F4Uu3y5Z3W3XrWfXw10 vrsFv398u3W5ZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrn_kYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k0a2IF6w1U M7kC6x804xWl1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s1lnx0Ec2IEnICE548m6r 1DJrWUZwAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY 64vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxk0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2 Ij64vIr41l4IxY624lx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y0x0EwIxGrbIYCTnIWIev Ja73UjIFyTuYvjxUxnN3UUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEHEko7lOv2WwAAs2
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 20 Oct 2011 00:58:20 -0000

This is a multi-part message in MIME format.
--------------010408000102050302020202
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hi,

On 10/19/2011 7:33 PM, Maoke wrote:
> ..
>
>>
>>>         a single value over the domain or possible variable among
>>>         different shared IPv4 addresses? (to my understanding, one
>>>         address should have a common value of PSID length for all
>>>         the CEs sharing the address, right?)
>>         The number of L equals the number of Delegated Prefixes of
>>         different lengths totally within a given domain, which should
>>         be determined during IPv6 address planning.
>>
>>
>>     they are equal to each other. but which determines which, in or
>>     before the IPv6 address planning?
>     IMHO, I guess the length of Delegated Prefix settled in phase of
>     the native IPv6 address planning without considering anything
>     about IPv4 addressing, determines the L.
>
>
> ?? i suppose previously with your clarification you HAVE admitted your 
> consensus to my 1) ~ 4) as the logic of the operation, but now you 
> said "without considering anything about IPv4". may you clarify your 
> process with starting from the following example?
>
Sorry, maybe there was some misunderstanding between us.
I mean you don't need to consider IPv4 when try to decide the length of 
delegated prefix to be assigned to customer. Maybe it was appropriate to 
use the word "anything". ;-)
Something should be considered if you need multiple sharing ratios.

> i allocate:
>    CE1 2001:db9:8765:4320::/60
>    CE2 2001:db8:7654:3210::/60
> then the IPv6 address planning is finished according to your statement.
>
> then what information should i use to determine the L for each? you 
> mean the IPv6 address planning is enough?
>
Yes.


Cheers,
Jacni

> thanks,
> maoke
>
>     Cheers,
>     Jacni
>
>
>>     delegated prefix length decides PSID length (sharing ratio), or
>>     inversely? is it not that the sharing ratio is determined by how
>>     many CEs sharing a unique IPv4 address?
>>
>>     best,
>>     maoke
>>
>>         Cheers,
>>         Jacni
>>
>>
>

--------------010408000102050302020202
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 10/19/2011 7:33 PM, Maoke wrote:
    <blockquote
cite="mid:CAFUBMqXRJ1obTJD6_6MQ2jGJVua1y5WqfDJ9-Nq8x2KJU7Ys3w@mail.gmail.com"
      type="cite">..<br>
      <div class="gmail_quote">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000">
            <div class="im">
              <blockquote type="cite">
                <div class="gmail_quote">
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    <div bgcolor="#FFFFFF" text="#000000"> <br>
                      <blockquote type="cite">
                        <div class="gmail_quote">
                          <div>a single value over the domain or
                            possible variable among different shared
                            IPv4 addresses? (to my understanding, one
                            address should have a common value of PSID
                            length for all the CEs sharing the address,
                            right?)</div>
                        </div>
                      </blockquote>
                      The number of L equals the number of Delegated
                      Prefixes of different lengths totally within a
                      given domain, which should be determined during
                      IPv6 address planning.<br>
                      <br>
                    </div>
                  </blockquote>
                  <div><br>
                  </div>
                  <div>they are equal to each other. but which
                    determines which, in or before the IPv6 address
                    planning? </div>
                </div>
              </blockquote>
            </div>
            IMHO, I guess the length of Delegated Prefix settled in
            phase of the native IPv6 address planning without
            considering anything about IPv4 addressing, determines the
            L.<br>
            <br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>?? i suppose previously with your clarification you HAVE
          admitted your consensus to my 1) ~ 4) as the logic of the
          operation, but now you said "without considering anything
          about IPv4". may you clarify your process with starting from
          the following example?&nbsp;</div>
        <div><br>
        </div>
      </div>
    </blockquote>
    Sorry, maybe there was some misunderstanding between us.<br>
    I mean you don't need to consider IPv4 when try to decide the length
    of delegated prefix to be assigned to customer. Maybe it was
    appropriate to use the word "anything". ;-)<br>
    Something should be considered if you need multiple sharing ratios.<br>
    <br>
    <blockquote
cite="mid:CAFUBMqXRJ1obTJD6_6MQ2jGJVua1y5WqfDJ9-Nq8x2KJU7Ys3w@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>i allocate:&nbsp;</div>
        <div>&nbsp; &nbsp;CE1 2001:db9:8765:4320::/60</div>
        <div>&nbsp; &nbsp;CE2 2001:db8:7654:3210::/60</div>
        <div>then the IPv6 address planning is finished according to
          your statement.&nbsp;</div>
        <div><br>
        </div>
        <div>
          then what information should i use to determine the L for
          each? you mean the IPv6 address planning is enough?&nbsp;</div>
        <div><br>
        </div>
      </div>
    </blockquote>
    Yes.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:CAFUBMqXRJ1obTJD6_6MQ2jGJVua1y5WqfDJ9-Nq8x2KJU7Ys3w@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div>thanks,</div>
        <div>maoke</div>
        <div>&nbsp;</div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex;">
          <div bgcolor="#FFFFFF" text="#000000">Cheers,<br>
            <font color="#888888"> Jacni</font>
            <div class="im"><br>
              <br>
              <blockquote type="cite">
                <div class="gmail_quote">
                  <div>delegated prefix length decides PSID length
                    (sharing ratio), or inversely? is it not that the
                    sharing ratio is determined by how many CEs sharing
                    a unique IPv4 address?&nbsp;</div>
                  <div><br>
                  </div>
                  <div>best,</div>
                  <div>maoke</div>
                  <div>&nbsp; &nbsp;</div>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    <div bgcolor="#FFFFFF" text="#000000">Cheers,<br>
                      <font color="#888888"> Jacni</font></div>
                  </blockquote>
                </div>
                <br>
              </blockquote>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
  </body>
</html>

--------------010408000102050302020202--


From yiu_lee@cable.comcast.com  Wed Oct 19 19:11: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 13A1E1F0C44 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 19:11: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yDzaZV9UFq4z for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 19:11: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 5535A1F0C3E for <softwires@ietf.org>; Wed, 19 Oct 2011 19:11:52 -0700 (PDT)
Received: from ([24.40.55.41]) by copdcimo01.cable.comcast.com with ESMTP  id 5503630.57880444; Wed, 19 Oct 2011 20:19:14 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%11]) with mapi id 14.01.0289.001; Wed, 19 Oct 2011 22:11:44 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Daniel Roesen <dr@cluenet.de>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: [Softwires] DS-Lite fragmentation RFC2473 reference
Thread-Index: AQHMjs2dixuAYwMMVEu/hXNYnPO/ng==
Date: Thu, 20 Oct 2011 02:11:44 +0000
Message-ID: <CAC4FAD2.16A5B%yiu_lee@cable.comcast.com>
In-Reply-To: <20111011123727.GA4461@srv03.cluenet.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [147.191.125.13]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8BFEF9715423B74AA6D1DEACC4C080A5@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Softwires] DS-Lite fragmentation RFC2473 reference
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, 20 Oct 2011 02:11:53 -0000

Hi Daniel,

Host behind B4 isn't aware he tunnel between B4 and AFTR. To make the host
transparent to IPv4 fragmentation, we made the decision to mandate B4 (and
AFTR) fragment and reassemble the oversized packet. We agree that there is
a price to pay (i.e., CPU intensive operation in B4 and AFTR), but this
should affect the host least.

/Yiu

On 10/11/11 8:37 AM, "Daniel Roesen" <dr@cluenet.de> wrote:

>Hi,
>
>the DS-Lite spec states:
>
>5.3.  Fragmentation and Reassembly
>...
>   [...] The inner IPv4 packet MUST NOT be
>   fragmented.  Fragmentation MUST happen after the encapsulation of the
>   IPv6 packet.  Reassembly MUST happen before the decapsulation of the
>   IPv4 packet.  A detailed procedure has been specified in [RFC2473]
>   Section 7.2.
>
>
>The change from "fragment the IPv4 payload" to "fragment the IPv6 tunnel
>packet" came between draft-ietf-softwire-dual-stack-lite-00 and -01:
>
>http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-dual-stack-lite-0=
1.
>txt
>
>The probable trigger was:
>
>http://www.ietf.org/mail-archive/web/softwires/current/msg00756.html
>
>No reasoning has been provided on the list, nor was the change in -01
>commented.
>
>I'm wondering what the reasoning was to mandate tunnel packet
>fragmentation instead of payload. Could anyone give some insights?
>
>Theoretically there should be no adverse impact by AFTR fragmenting the
>NATted IPv4 payload packets for transmission into the tunnel to the B4.
>Reassembly would be offloaded from the B4 to the endpoint behind the B4.
>
>I've investigated a bit and found reports of SIP implementations having
>serious problems with fragmented UDP, as well as Microsoft AD/Kerberos:
>
>http://blog.tmcnet.com/third-screen/2009/03/udp_fragmentation_breaks_sip_i
>n_todays_ip-pbxs.html
>http://blogs.technet.com/b/asiasupp/archive/2006/09/19/457413.aspx
>
>Any insight appreciated!
>
>Best regards,
>Daniel
>
>PS: yes, fragmenting the tunnel packets is of course the most
>transparent way end-to-end, but it comes at a price...
>
>--=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 fibrib@gmail.com  Wed Oct 19 21:34:37 2011
Return-Path: <fibrib@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 1C58021F8634 for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 21:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.249,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gz6Mq47B8Vvv for <softwires@ietfa.amsl.com>; Wed, 19 Oct 2011 21:34:36 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 498BF21F862F for <softwires@ietf.org>; Wed, 19 Oct 2011 21:34:36 -0700 (PDT)
Received: by qyk34 with SMTP id 34so3624438qyk.10 for <softwires@ietf.org>; Wed, 19 Oct 2011 21:34:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vT2A3LQe9kkz9lyWq7CUFeKlxz6LRedQQb2DGsO404w=; b=uPE+fmQY4aDdO48zvRAqMvCqGsRWcmZ42grCaET41hl+e9MqZ7A2PivqQz2dVK/GPz QhdVajczeBTck1Urhq2eMlK/N/dp6J19IT47LqJGn4AGQ32i6hOhfN7DWOafp9nlQH1m gca4Om7Fw7MyFjktzrIBP9OKpF/SedG3Wva3c=
MIME-Version: 1.0
Received: by 10.229.62.195 with SMTP id y3mr2015747qch.31.1319085275715; Wed, 19 Oct 2011 21:34:35 -0700 (PDT)
Received: by 10.229.175.205 with HTTP; Wed, 19 Oct 2011 21:34:35 -0700 (PDT)
In-Reply-To: <4E9F728C.7050801@jacni.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <4E9CEA60.6040208@jacni.com> <CAFUBMqXS9tJvs9Oz+NQczUkQvikEuyzRnX_iR4QE1_=tJA7OCA@mail.gmail.com> <4E9E2987.6070407@jacni.com> <CAFUBMqUp8dzW0AR96J9LYPKU4-zWnbQ6hjFgNUNKdFPxPQ=WxA@mail.gmail.com> <4E9E41C5.502@jacni.com> <CAFUBMqUHG2PdBa1mfyja=LM9eVKu=LMfgxvGzsMoeyFB8Au+YQ@mail.gmail.com> <4E9E81AA.5000009@jacni.com> <CAFUBMqXRJ1obTJD6_6MQ2jGJVua1y5WqfDJ9-Nq8x2KJU7Ys3w@mail.gmail.com> <4E9F728C.7050801@jacni.com>
Date: Thu, 20 Oct 2011 13:34:35 +0900
Message-ID: <CAFUBMqW9=mV_2rDHSaM5Frx7YihLvPmrhO8g0taZ5wiCAbqW-w@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Jacni Qin <jacni@jacni.com>
Content-Type: multipart/alternative; boundary=0016e64b1d5649997b04afb37922
Cc: softwires@ietf.org
Subject: Re: [Softwires] 4rd Address Mapping - version-01
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, 20 Oct 2011 04:34:37 -0000

--0016e64b1d5649997b04afb37922
Content-Type: text/plain; charset=ISO-8859-1

2011/10/20 Jacni Qin <jacni@jacni.com>
>
>  ?? i suppose previously with your clarification you HAVE admitted your
> consensus to my 1) ~ 4) as the logic of the operation, but now you said
> "without considering anything about IPv4". may you clarify your process with
> starting from the following example?
>
>   Sorry, maybe there was some misunderstanding between us.
> I mean you don't need to consider IPv4 when try to decide the length of
> delegated prefix to be assigned to customer. Maybe it was appropriate to use
> the word "anything". ;-)
> Something should be considered if you need multiple sharing ratios.
>
>
>  i allocate:
>    CE1 2001:db9:8765:4320::/60
>    CE2 2001:db8:7654:3210::/60
> then the IPv6 address planning is finished according to your statement.
>
>  then what information should i use to determine the L for each? you mean
> the IPv6 address planning is enough?
>
>   Yes.
>
>
your yes is in the case of there is not multiple sharing ratios, right? ;-)

if it is right, i agree with you that the planning is independent of IPv4
knowledge. if there are multiple ratios, i understanding the start of the
PSIDs must be aligned among the delegated IPv6 prefixes.

best,
maoke


> Cheers,
> Jacni
>

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

<br><br><div class=3D"gmail_quote">2011/10/20 Jacni Qin <span dir=3D"ltr">&=
lt;<a href=3D"mailto:jacni@jacni.com">jacni@jacni.com</a>&gt;</span> =A0<bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex;">
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
        <blockquote type=3D"cite"><div class=3D"im"><div class=3D"gmail_quo=
te">
        <div>?? i suppose previously with your clarification you HAVE
          admitted your consensus to my 1) ~ 4) as the logic of the
          operation, but now you said &quot;without considering anything
          about IPv4&quot;. may you clarify your process with starting from
          the following example?=A0</div>
        <div><br>
        </div>
      </div>
    </div></blockquote>
    Sorry, maybe there was some misunderstanding between us.<br>
    I mean you don&#39;t need to consider IPv4 when try to decide the lengt=
h
    of delegated prefix to be assigned to customer. Maybe it was
    appropriate to use the word &quot;anything&quot;. ;-)<br>
    Something should be considered if you need multiple sharing ratios.<div=
 class=3D"im"><br>
    <br>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div>i allocate:=A0</div>
        <div>=A0 =A0CE1 2001:db9:8765:4320::/60</div>
        <div>=A0 =A0CE2 2001:db8:7654:3210::/60</div>
        <div>then the IPv6 address planning is finished according to
          your statement.=A0</div>
        <div><br>
        </div>
        <div>
          then what information should i use to determine the L for
          each? you mean the IPv6 address planning is enough?=A0</div>
        <div><br>
        </div>
      </div>
    </blockquote></div>
    Yes.<br>
    <br>
    </div></blockquote><div><br></div><div>your yes is in the case of there=
 is not multiple sharing ratios, right? ;-)</div><div><br></div><div>if it =
is right, i agree with you that the planning is independent of IPv4 knowled=
ge. if there are multiple ratios, i understanding the start of the PSIDs mu=
st be aligned among the delegated IPv6 prefixes.=A0</div>
<div><br></div><div>best,</div><div>maoke</div><div>=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex;"><div bgcolor=3D"#FFFFFF" text=3D"#000000">Cheers,<br><fon=
t color=3D"#888888">
    Jacni</font></div></blockquote></div><br>

--0016e64b1d5649997b04afb37922--

From dr@cluenet.de  Thu Oct 20 00:42:34 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 B2F9421F8B1C for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 00:42:34 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o+XL9b83bX2C for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 00:42:34 -0700 (PDT)
Received: from mail1.cluenet.de (mail1.cluenet.de [IPv6:2001:1440:201:101::5]) by ietfa.amsl.com (Postfix) with ESMTP id 327B421F8AC3 for <softwires@ietf.org>; Thu, 20 Oct 2011 00:42:33 -0700 (PDT)
Received: by mail1.cluenet.de (Postfix, from userid 500) id D92581080C6; Thu, 20 Oct 2011 09:42:31 +0200 (CEST)
Date: Thu, 20 Oct 2011 09:42:31 +0200
From: Daniel Roesen <dr@cluenet.de>
To: softwires@ietf.org
Message-ID: <20111020074231.GA12499@srv03.cluenet.de>
Mail-Followup-To: softwires@ietf.org
References: <20111011123727.GA4461@srv03.cluenet.de> <CAC4FAD2.16A5B%yiu_lee@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAC4FAD2.16A5B%yiu_lee@cable.comcast.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Subject: Re: [Softwires] DS-Lite fragmentation RFC2473 reference
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, 20 Oct 2011 07:42:34 -0000

Hi Yiu,

On Thu, Oct 20, 2011 at 02:11:44AM +0000, Lee, Yiu wrote:
> Host behind B4 isn't aware he tunnel between B4 and AFTR. To make the host
> transparent to IPv4 fragmentation, we made the decision to mandate B4 (and
> AFTR) fragment and reassemble the oversized packet. We agree that there is
> a price to pay (i.e., CPU intensive operation in B4 and AFTR), but this
> should affect the host least.

Thanks for the clarification. Too bad the vendor landscape (both AFTR
and B4) grossly ignore that normative requirement of RFC6333 and either
fragment the payload instead of the tunnel, or - even worse - resort to
measures like issuing ICMPv4 "frag needed but DF set" even in response
to >1460 bytes IPv4 packets WITHOUT DF bit being set.

They all have significant problems with performance when being asked to
perform proper RFC6333 operation. And then speak of hardening AFTRs
against reassembly resources starvation attacks...

Best regards,
Daniel

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

From despres.remi@laposte.net  Thu Oct 20 01:57:43 2011
Return-Path: <despres.remi@laposte.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 0DA0621F8B1E for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 01:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.139
X-Spam-Level: 
X-Spam-Status: No, score=-1.139 tagged_above=-999 required=5 tests=[AWL=-0.449, BAYES_00=-2.599, FB_YOU_CAN_BECOME=1.258, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6lL5D5Mp7ptQ for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 01:57:42 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC8F21F8B1C for <softwires@ietf.org>; Thu, 20 Oct 2011 01:57:40 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2307.sfr.fr (SMTP Server) with ESMTP id D1F2C7000090; Thu, 20 Oct 2011 10:57:39 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2307.sfr.fr (SMTP Server) with ESMTP id 1E992700008C; Thu, 20 Oct 2011 10:57:36 +0200 (CEST)
X-SFR-UUID: 20111020085739125.1E992700008C@msfrf2307.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-12--656043543
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAC8QAcewMGEk9mg1v1ju=kwWkCdNojusfjAakXv=6LMo_AMzzA@mail.gmail.com>
Date: Thu, 20 Oct 2011 10:57:36 +0200
Message-Id: <1DB06094-22D8-4B0E-AB1C-8043AC72B9DE@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net> <49200DB8-5D14-46B7-A892-79262CFF6968@laposte.net> <C653042D-9AC3-4F2D-9F23-4061A1DD4377@townsley.net> <5F044EAF-A653-499B-86B1-993CA77D1071@laposte.net> <0B52D2A1-9938-48A8-A87C-27DE39405263@townsley.net> <DF8BF1B0-63DB-4F9B-BE96-4D214513C0DC@laposte.net> <63DB920E-8768-47BD-8185-959C4165977B@townsley.net> <D8CC5 D14-34F2-4A00-8051-7114F8945134@laposte.net> <CAC8QAcewMGEk9mg1v1ju=kwWkCdNojusfjAakXv=6LMo_AMzzA@mail.gmail.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Standardizing "4rd-U" vs "4rd-Encapsulation AND Double translation - analysis
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, 20 Oct 2011 08:57:43 -0000

--Apple-Mail-12--656043543
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi Behcet,

Thank you for your interest in understanding 4rd-U.

- The draft is informational because it is, at this stage, just a design =
proposal. The expectation is that it will eventually be included in a =
standard-track document whose form has to be decided in the WG.

- Despite my current attempt to spend less time for IETF, I will try to =
have soon a -01.
It will incorporate what I see as significant improvements resulting =
from the WG debate:
  . TOS copied in the IPv6 fragment header (pipe & short-pipe =
compatibility)=20
  . Use of a checksum-neutral IPv6 addresses (compatibility with web =
redirection in IPv6 domains) =20

Regards,
RD


Le 19 oct. 2011 =E0 22:05, Behcet Sarikaya a =E9crit :

> I would like to see more details on 4rd-u before. Why is it =
informational? A -01 would help.
>=20
> Regards,
>=20
> Behcet
>=20
> On Wed, Oct 19, 2011 at 3:07 AM, R=E9mi Despr=E9s =
<despres.remi@laposte.net> wrote:
> Mark,
> More on this debate below.
>=20
> Le 18 oct. 2011 =E0 19:44, Mark Townsley a =E9crit :
> > On Oct 18, 2011, at 4:31 PM, R=E9mi Despr=E9s wrote:
> ...
> >> Could you explain the important advantage of encapsulation that is =
missing in 4rd-U?
> >
> > It's been specified and implemented for years, it is part of other =
softwires specifications, it is being implemented in CPE equipment today =
as part of ds-lite, it doesn't put payloads on the wire with =
mis-matching checksums.... Sure, tunneling doesn't play nice with some =
ACLs that only look at native IPv6, but at least this is a very =
well-understood attribute of tunneling that operators expect and in many =
cases are able to design around. FWIW, my crystal ball says that these =
limitations will will become less and less relevant if and when 4-in-6 =
operation becomes more and more prevalent, but that's just me.
>=20
>=20
> > Translation based on what's already defined in the behave WG is less =
conservative than simple encapsulation, but at least it is building on =
something that already exists, is well-specified and deployed, etc.
>=20
> Successfully deployed in production, not so sure. (Even IPv6 isn't =
that largely deployed today).
> In any case, it has the side effect that it damages network =
transparency to IPv4 packets.
>=20
> > We can expect to see IPv4 payloads with IPv6 headers on the network =
because of translators, but at least the checksums will be correct
>=20
> For ISP networks where web redirection with existing IPv6 tools is =
needed, 4rd-U could be completed so that checksums are correct.
> This can be done like in dIVI by checksum adjustments at IPv6-domain =
entrance and exit, or (better IMHO) by revising the unified =
address-mapping to make it checksum neutral (something Ole has in my =
understanding suggested).
>=20
> Thanks for pointing out that something was missing to get the best of =
both worlds.
>=20
> > and there is a decent chance that a host will be able to digest the =
packet and get it to a working application after passing through one =
level of translation (or being redirected, subjected to DPI, etc).
> >
> > Again, no offense at all to the ingenuity of -U, but I simply have a =
hard time justifying that we need to cast a balance between these =
relatively well-known, specified, and implemented building-blocks with =
something new.
>=20
> New, yes, but quite simple, and with an immediate operational =
advantage.
>=20
> > If I believed for a microsecond that -U would wipe both =
encapsulation and translation from the planet so that we would have only =
one mechanism here, I would be more supportive. The problem is that the =
other two already exist in other closely related contexts such that =
there is no way that this doesn't become a 3rd method in the network =
without turning back time itself.
>=20
> Assuming that the three solutions would be available in products, I =
don't see why an ISP would prefer to keep double translation or =
encapsulation:
> - The fact that translations and encapsulations were first to exist IS =
NOT an operational advantage
> - Having both of network transparency to IPv4 AND applicability of =
IPv6 O&M tools IS an operational advantage.
>=20
> I still hope that, with more thoughts on the subject, you can become =
more open.
>=20
> Regards,
> RD
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>=20


--Apple-Mail-12--656043543
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Behcet,<div><br></div><div>Thank you for your interest in understanding =
4rd-U.</div><div><br></div><div>- The draft is informational because it =
is, at this stage, just a design proposal. The expectation is that it =
will eventually be included in a standard-track document whose form has =
to be decided in the WG.</div><div><br></div><div>-&nbsp;Despite my =
current attempt to spend less time for IETF,&nbsp;I will try to have =
soon a -01.</div><div>It will incorporate what I see as significant =
improvements resulting from the WG debate:</div><div>&nbsp; . TOS copied =
in the IPv6 fragment header (pipe &amp; short-pipe =
compatibility)&nbsp;</div><div>&nbsp; . Use of a checksum-neutral IPv6 =
addresses (compatibility with web redirection in IPv6 domains) =
&nbsp;</div><div><br></div><div>Regards,</div><div>RD</div><div><br></div>=
<div><br></div><div><div><div>Le 19 oct. 2011 =E0 22:05, Behcet Sarikaya =
a =E9crit :</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">I would like to see more details on 4rd-u before. Why is =
it informational? A -01 would =
help.<br><br>Regards,<br><br>Behcet<br><br><div class=3D"gmail_quote">On =
Wed, Oct 19, 2011 at 3:07 AM, R=E9mi Despr=E9s <span dir=3D"ltr">&lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">Mark,<br>
More on this debate below.<br>
<br>
Le 18 oct. 2011 =E0 19:44, Mark Townsley a =E9crit :<br>
&gt; On Oct 18, 2011, at 4:31 PM, R=E9mi Despr=E9s wrote:<br>
...<br>
&gt;&gt; Could you explain the important advantage of encapsulation that =
is missing in 4rd-U?<br>
&gt;<br>
&gt; It's been specified and implemented for years, it is part of other =
softwires specifications, it is being implemented in CPE equipment today =
as part of ds-lite, it doesn't put payloads on the wire with =
mis-matching checksums.... Sure, tunneling doesn't play nice with some =
ACLs that only look at native IPv6, but at least this is a very =
well-understood attribute of tunneling that operators expect and in many =
cases are able to design around. FWIW, my crystal ball says that these =
limitations will will become less and less relevant if and when 4-in-6 =
operation becomes more and more prevalent, but that's just me.<br>

<br>
<br>
&gt; Translation based on what's already defined in the behave WG is =
less conservative than simple encapsulation, but at least it is building =
on something that already exists, is well-specified and deployed, =
etc.<br>

<br>
Successfully deployed in production, not so sure. (Even IPv6 isn't that =
largely deployed today).<br>
In any case, it has the side effect that it damages network transparency =
to IPv4 packets.<br>
<br>
&gt; We can expect to see IPv4 payloads with IPv6 headers on the network =
because of translators, but at least the checksums will be correct<br>
<br>
For ISP networks where web redirection with existing IPv6 tools is =
needed, 4rd-U could be completed so that checksums are correct.<br>
This can be done like in dIVI by checksum adjustments at IPv6-domain =
entrance and exit, or (better IMHO) by revising the unified =
address-mapping to make it checksum neutral (something Ole has in my =
understanding suggested).<br>

<br>
Thanks for pointing out that something was missing to get the best of =
both worlds.<br>
<br>
&gt; and there is a decent chance that a host will be able to digest the =
packet and get it to a working application after passing through one =
level of translation (or being redirected, subjected to DPI, etc).<br>
&gt;<br>
&gt; Again, no offense at all to the ingenuity of -U, but I simply have =
a hard time justifying that we need to cast a balance between these =
relatively well-known, specified, and implemented building-blocks with =
something new.<br>

<br>
New, yes, but quite simple, and with an immediate operational =
advantage.<br>
<br>
&gt; If I believed for a microsecond that -U would wipe both =
encapsulation and translation from the planet so that we would have only =
one mechanism here, I would be more supportive. The problem is that the =
other two already exist in other closely related contexts such that =
there is no way that this doesn't become a 3rd method in the network =
without turning back time itself.<br>

<br>
Assuming that the three solutions would be available in products, I =
don't see why an ISP would prefer to keep double translation or =
encapsulation:<br>
- The fact that translations and encapsulations were first to exist IS =
NOT an operational advantage<br>
- Having both of network transparency to IPv4 AND applicability of IPv6 =
O&amp;M tools IS an operational advantage.<br>
<br>
I still hope that, with more thoughts on the subject, you can become =
more open.<br>
<br>
Regards,<br>
RD<br>
<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"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</blockquote></div><br>
</blockquote></div><br></div></body></html>=

--Apple-Mail-12--656043543--

From Francis.Dupont@fdupont.fr  Thu Oct 20 02:27:08 2011
Return-Path: <Francis.Dupont@fdupont.fr>
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 CAEC321F8A6F for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 02:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level: 
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id slDto8FWjVuC for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 02:27:08 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 0D31721F8A7B for <softwires@ietf.org>; Thu, 20 Oct 2011 02:27:07 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p9K9R3VA061305; Thu, 20 Oct 2011 11:27:03 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201110200927.p9K9R3VA061305@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Daniel Roesen <dr@cluenet.de>
In-reply-to: Your message of Thu, 20 Oct 2011 09:42:31 +0200. <20111020074231.GA12499@srv03.cluenet.de> 
Date: Thu, 20 Oct 2011 11:27:03 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: softwires@ietf.org
Subject: Re: [Softwires] DS-Lite fragmentation RFC2473 reference
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, 20 Oct 2011 09:27:08 -0000

 In your previous mail you wrote:

   Thanks for the clarification. Too bad the vendor landscape (both AFTR
   and B4) grossly ignore that normative requirement of RFC6333 and either
   fragment the payload instead of the tunnel,

=> there is a feature (not a bug as it is not incorrect) in some Linux
kernels which don't use the right MTU for the encapsulated packets
(there are some lines of code to remove, cf the PS).

Thanks

Francis.Dupont@fdupont.fr

PS: the patch (against an old version but this is not yet fixed in
recent kernels...):

*** /usr/src/linux/net/ipv6/ip6_tunnel.c	2008-07-13 23:51:29.000000000 +0200
--- ip6_tunnel+.c	2008-12-09 01:25:33.000000000 +0100
***************
*** 888,898 ****
  		mtu = IPV6_MIN_MTU;
  	if (skb->dst)
  		skb->dst->ops->update_pmtu(skb->dst, mtu);
- 	if (skb->len > mtu) {
- 		*pmtu = mtu;
- 		err = -EMSGSIZE;
- 		goto tx_err_dst_release;
- 	}
  
  	/*
  	 * Okay, now see if we can stuff it in the buffer as-is.
--- 888,893 ----

From despres.remi@laposte.net  Thu Oct 20 02:32:58 2011
Return-Path: <despres.remi@laposte.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 9796521F8B08 for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 02:32:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[AWL=0.202,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AuOcZhGBzQ4f for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 02:32:58 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by ietfa.amsl.com (Postfix) with ESMTP id DE8A521F8AF9 for <softwires@ietf.org>; Thu, 20 Oct 2011 02:32:57 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2307.sfr.fr (SMTP Server) with ESMTP id 42D53700005F; Thu, 20 Oct 2011 11:32:57 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2307.sfr.fr (SMTP Server) with ESMTP id EA9E27000048; Thu, 20 Oct 2011 11:32:54 +0200 (CEST)
X-SFR-UUID: 20111020093254961.EA9E27000048@msfrf2307.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com>
Date: Thu, 20 Oct 2011 11:32:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A51007D4-4174-4173-9564-40068C2D4544@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 20 Oct 2011 09:32:58 -0000

Satoru-san,
Sorry for the late answer.

Le 17 oct. 2011 =E0 15:17, Satoru Matsushima a =E9crit :

> Hi Remi-san,
>=20
>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>> It can make IMHO a valuable unified standard.
>=20
> Not enough. The original TTL value in IPv4 header must be carried.

It isn't clear to me that mapping the IPv4 TTL into the IPv6 Hop limit =
isn't sufficient.
Have you a reference to suggest about this requirement?

Thanks,
RD


>=20
> cheers,
> --satoru
>=20
>=20
> On 2011/10/17, at 21:36, R=E9mi Despr=E9s wrote:
>=20
>> Hi Satoru-san,
>>=20
>> Thank you for identifying a limitation of the 4rd-U =20
>> You are right, as currently specified, "it doesn't support diff-serv =
tunneling model, pipe and short-pipe".
>> All these need e2e transparency to the IPv4 Type of Service.
>>=20
>> Fortunately, this is easy to fix: in the Identification field of the =
IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
>>=20
>> The proposed 4r-U packet format becomes:
>>=20
>>=20
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |Vers=3D6 |   TrafClass   |            Flow Label                 |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |         Payload Length        |Next Header=3D44 |   Hop Limit   |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |                                                               |
>>  +                                                               +
>>  |                                                               |
>>  +                  IPv6 Source Address                          +
>>  |                                                               |
>>  +                                                               +
>>  |                                                               |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |                                                               |
>>  +                                                               +
>>  |                                                               |
>>  +                IPv6 Destination Address                       +
>>  |                                                               |
>>  +                                                               +
>>  |                                                               |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
>>  |                        IPv4 Payload                           |
>>  |                                                               |=20
>>=20
>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>> It can make IMHO a valuable unified standard.
>>=20
>> Yet, I may have missed something else.=20
>> New justified objections are therefore most welcome..
>>=20
>>=20
>> Regards,
>> RD
>=20

From fibrib@gmail.com  Thu Oct 20 07:48:42 2011
Return-Path: <fibrib@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 272A521F8B87 for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 07:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.212
X-Spam-Level: 
X-Spam-Status: No, score=-3.212 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yqn7s7Gl0sOx for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 07:48:41 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3112821F8BA4 for <softwires@ietf.org>; Thu, 20 Oct 2011 07:48:41 -0700 (PDT)
Received: by qadc10 with SMTP id c10so518283qad.31 for <softwires@ietf.org>; Thu, 20 Oct 2011 07:48:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q5TOwdBFkdcyhM2F4uoPlAm9CyPb4LzhOhSH04NhnFY=; b=UG7NIxUZUkvsphk1XF0geXpDWv7zc4vsJw9ylizTVSYOp/2IauogNWSlpOCS2untxP fEVqHJ7IaNxzAoRyXDupVjzD5pkcT9XFErt6IGPGtXZmU2AwEeMxwZOt7+mGKIFzHihr l7SiAzKBrXn02GI7Kfx42XIvNiuaIJI3wBKqE=
MIME-Version: 1.0
Received: by 10.229.81.3 with SMTP id v3mr2352567qck.297.1319122120277; Thu, 20 Oct 2011 07:48:40 -0700 (PDT)
Received: by 10.229.175.205 with HTTP; Thu, 20 Oct 2011 07:48:40 -0700 (PDT)
In-Reply-To: <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr>
Date: Thu, 20 Oct 2011 23:48:40 +0900
Message-ID: <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: multipart/alternative; boundary=00163646d64a65030304afbc0db8
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 20 Oct 2011 14:48:42 -0000

--00163646d64a65030304afbc0db8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Remi,

thanks a lot for the reply! it is very helpful and my latest understanding
almost approach it. but still some minor clarifications.
2011/10/20 R=E9mi Despr=E9s <remi.despres@free.fr>

> Hi Maoke,
>
> Thank you for your questions concerning relationships between IPv6 and IP=
v4
> addressing plans.
>
> Here are address-planning steps that illustrate how an IPv6 addressing pl=
an
> can be kept independent from IPv4 prefixes used for IPv4 residual
> deployment, even if CEs must be able to have different sharing ratios.
>
>   (A) IPv6 considerations
> (A1) Determine the maximum number N of CEs you want to support, a power o=
f
> 2 (N =3D 2 ^ n).
> (A2) Choose the length x of IPv6 prefixes you want to assign to ordinary
> customers (e.g. x =3D 60)
> (A2) Multiply M by a margin coefficient K, a power of two (K =3D 2 ^ k), =
to
> take into account that:
>
>

here the M should be a typo of "N", right? ;-)


>
>  - Some privileged customers may be assigned IPv6 prefixes of length x',
> shorter than x, to have larger addressing spaces than ordinary customers,
> both in IPv6 and IPv4.
>  - Due to the hierarchy of routable prefixes, many theoretically
> delegatable prefixes may not be actually delegatable (ref: host density
> ratio of RFC 3194).
>
>   (B) IPv4 considerations
> (B1) List all (non overlapping) IPv4 prefixes Hi that are available for
> IPv4 residual deployment.
> (B2) Take enough of them, among the shortest ones, to get a total space
> whose size M is a power of two (M =3D 2 ^ m), and includes a good proport=
ion
> of the available IPv4 space (ref
> www.ietf.org/mail-archive/web/softwires/current/msg02261.html).
> (B3) For each IPv4 prefix Hi of length hi, choose a "Rule index" Ri of
> length ri =3D m - hi. All these indexes must be non overlapping prefixes =
(e.g.
> 0, 10, 110, 111 for one /10, one /11, and two /12).
>
>   (C) After (A) and (B)
> (C1) Derive the length c of the "Common prefix" C that will appear at the
> beginning of all delegatable prefixes (c =3D n + k - m)
> (C2) Take for C any prefix of length c that starts with a RIR-allocated
> IPv6 prefix
> (C3) For each IPv4 prefix Hi, make a rule in which it is the IPv4 prefix,
> and in which the IPv6 prefix is the Common prefix C followed by the Rule
> index Ri.
>
> I hope this can work on your favorite example(s).
> If not, please let me know.
>

it seems you didn't mention the PSID part. my understanding is, after the
above, when we have the, e.g., /60, the PSID is attached after the /60. the=
n
the CE delegated prefix (including IPv4 address suffix and PSID) may have
different lengths if the sharing ratio is variant for different shared IPv4
addresses. but the c + m (or n + k, or x (right?)) , including the common
prefix and the ipv4-address-related bits, is a constant for every
CE-delegated network in the domain, right?

on the other hand, there is a limitation. if c + m > 64, the above address
planning is not deployable, but with our effort of maximum compression, we
believe the undeployable case rarely happens for normal providers, right?


> Note that this is by no means to say that all ISPs should plan addresses
> this way (i.e. with a relationship between lengths of CE IPv6 prefixes an=
d
> sharing ratios). It is just to show that this  is workable.
>
>

sure. but i believe this will helps operators very much, considering up to
now no operators have experienced that.

thanks,
maoke


>
> Regards,
> RD
>
>

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

<div>hi Remi, </div><div>=A0</div><div>thanks a lot for the reply! it is ve=
ry helpful and my latest understanding almost=A0approach it. but still some=
 minor clarifications.<br></div><div class=3D"gmail_quote">2011/10/20 R=E9m=
i Despr=E9s <span dir=3D"ltr">&lt;<a href=3D"mailto:remi.despres@free.fr">r=
emi.despres@free.fr</a>&gt;</span><br>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote"><div style=3D"word-wrap: break-word;"><div>Hi =
Maoke,</div>
<div><br></div><div>Thank you for your questions concerning relationships b=
etween IPv6 and IPv4 addressing plans.</div><div><br></div><div>Here are ad=
dress-planning steps that=A0illustrate how an IPv6 addressing plan can be k=
ept independent from IPv4 prefixes used for IPv4 residual deployment, even =
if CEs must be able to have different sharing ratios.</div>
<div>=A0</div><div><div>=A0 (A) IPv6 considerations</div><div>(A1) Determin=
e the maximum number N of CEs you want to support, a power of 2 (N =3D 2 ^ =
n).</div><div>(A2) Choose the length x of IPv6 prefixes you want to assign =
to ordinary customers (e.g. x =3D 60)</div>
<div>(A2) Multiply M by a margin coefficient K, a power of two (K =3D 2 ^ k=
), to take into account that:</div><div>=A0</div></div></div></blockquote><=
div>=A0</div><div>here the M should be=A0a typo of=A0&quot;N&quot;, right?=
=A0;-)=A0</div>
<div>=A0</div><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left:=
 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border=
-left-style: solid;" class=3D"gmail_quote"><div style=3D"word-wrap: break-w=
ord;">
<div><div>=A0</div><div>=A0- Some privileged customers may be assigned IPv6=
 prefixes of length x&#39;, shorter than x, to have larger addressing space=
s than ordinary customers, both in IPv6 and IPv4. =A0</div><div>=A0- Due to=
 the hierarchy of routable prefixes, many theoretically delegatable prefixe=
s may not be actually delegatable (ref: host density ratio of RFC 3194).</d=
iv>
<div><br></div><div>=A0 (B) IPv4 considerations</div><div>(B1) List all (no=
n overlapping) IPv4 prefixes Hi that are available for IPv4 residual deploy=
ment.</div><div>(B2) Take enough of them, among the shortest ones, to get a=
 total space whose size M is a power of two (M =3D 2 ^ m), and includes a g=
ood proportion of the available IPv4 space (ref <a href=3D"http://www.ietf.=
org/mail-archive/web/softwires/current/msg02261.html" target=3D"_blank">www=
.ietf.org/mail-archive/web/softwires/current/msg02261.html</a>).</div>
<div>(B3)=A0For each IPv4 prefix Hi of length hi, choose a &quot;Rule index=
&quot; Ri of length ri =3D m - hi. All these indexes must be non overlappin=
g prefixes (e.g. 0, 10, 110, 111 for one /10, one /11, and two /12).</div><=
div>
<br></div><div>=A0 (C) After (A) and (B)</div><div>(C1) Derive the length c=
 of the &quot;Common prefix&quot; C that will appear at the beginning of al=
l delegatable prefixes (c =3D n + k - m)</div><div>(C2) Take for C any pref=
ix of length c that starts with a RIR-allocated IPv6 prefix</div>
<div>(C3) For each IPv4 prefix Hi, make a rule in which it is the IPv4 pref=
ix, and in which the=A0IPv6 prefix is the Common prefix C followed by the R=
ule index Ri.</div></div><div><br></div><div>I hope this can work on your f=
avorite example(s).</div>
<div>If not, please let me know.</div></div></blockquote><div>=A0</div><div=
>it seems you didn&#39;t mention the PSID part. my understanding is, after =
the above, when we have the, e.g., /60, the PSID is attached after the /60.=
 then the CE=A0delegated prefix=A0(including IPv4 address suffix and PSID) =
may have different lengths if the sharing ratio is variant for different sh=
ared IPv4 addresses. but the c + m (or n + k, or x (right?)) , including th=
e common prefix and the ipv4-address-related bits, is a constant for every =
CE-delegated network in the domain, right? </div>
<div>=A0</div><div>on the other hand, there is a limitation. if c + m &gt; =
64, the above address planning is not deployable, but with our effort of ma=
ximum compression, we believe the undeployable case rarely happens for norm=
al providers, right? </div>
<div>=A0</div><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left:=
 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border=
-left-style: solid;" class=3D"gmail_quote"><div style=3D"word-wrap: break-w=
ord;">
<div></div><div>Note that this is by no means to say that all ISPs should p=
lan addresses this way (i.e. with a relationship between lengths of CE IPv6=
 prefixes and sharing ratios). It is just to show that this =A0is workable.=
</div>
<div>=A0</div></div></blockquote><div>=A0</div><div>sure. but i believe thi=
s will helps operators very much, considering up to now no operators have e=
xperienced that. </div><div>=A0</div><div>thanks,</div><div>maoke</div><div=
>=A0</div>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote"><div style=3D"word-wrap: break-word;"><div>=A0=
</div>
<div>Regards,</div><div>RD=A0</div><div>=A0</div></div></blockquote></div>

--00163646d64a65030304afbc0db8--

From tetsuya@ipinfusion.com  Thu Oct 20 16:26:55 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 4065111E8096 for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 16:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e0OcZZTa5ZAP for <softwires@ietfa.amsl.com>; Thu, 20 Oct 2011 16:26:54 -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 7E9FD1F0C3F for <softwires@ietf.org>; Thu, 20 Oct 2011 16:26:54 -0700 (PDT)
Received: by gyh20 with SMTP id 20so3985761gyh.31 for <softwires@ietf.org>; Thu, 20 Oct 2011 16:26:52 -0700 (PDT)
Received: by 10.68.35.129 with SMTP id h1mr18424795pbj.92.1319153211738; Thu, 20 Oct 2011 16:26:51 -0700 (PDT)
Received: from [10.70.2.165] ([12.248.239.142]) by mx.google.com with ESMTPS id ki1sm23658913pbb.3.2011.10.20.16.26.49 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Oct 2011 16:26:50 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=utf-8
From: Tetsuya Murakami <tetsuya@ipinfusion.com>
In-Reply-To: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net>
Date: Thu, 20 Oct 2011 16:26:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C19F052-BA22-4A82-9FC7-665459A043A6@ipinfusion.com>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net>
To: =?utf-8?Q?R=C3=A9mi_Despr=C3=A9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1251.1)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 20 Oct 2011 23:26:55 -0000

Hi Remi,

I am not sure if this proposal is good or not... But I think you are =
trying to introduce a new semantics for IPv6 fragmentation header. For =
this, I think the implementation of IPv6 stack must be changed to =
process your new fragmentation header. But I am not sure how to decide =
if the fragmentation header in the packet should be processed as either =
the normal fragmentation header or your new fragmentation header. =
Usually, IPv6 stack decides the processing for the following extension =
header based on the next header type. But you are using the same number =
of the existing fragmentation header for your new fragmentation header. =
If requiring any other information in the packet except the next header =
type, it might be a little bit painful from the implementation point of =
view.

Thanks,
Tetsuya Murakami

On 2011/10/17, at 5:36, R=C3=A9mi Despr=C3=A9s wrote:

> Hi Satoru-san,
>=20
> Thank you for identifying a limitation of the 4rd-U =20
> You are right, as currently specified, "it doesn't support diff-serv =
tunneling model, pipe and short-pipe".
> All these need e2e transparency to the IPv4 Type of Service.
>=20
> Fortunately, this is easy to fix: in the Identification field of the =
IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
>=20
> The proposed 4r-U packet format becomes:
>=20
>=20
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |Vers=3D6 |   TrafClass   |            Flow Label                 |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |         Payload Length        |Next Header=3D44 |   Hop Limit   |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                                                               |
>   +                                                               +
>   |                                                               |
>   +                  IPv6 Source Address                          +
>   |                                                               |
>   +                                                               +
>   |                                                               |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                                                               |
>   +                                                               +
>   |                                                               |
>   +                IPv6 Destination Address                       +
>   |                                                               |
>   +                                                               +
>   |                                                               |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
>   |                        IPv4 Payload                           |
>   |                                                               |=20
>=20
> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
> It can make IMHO a valuable unified standard.
>=20
> Yet, I may have missed something else.=20
> New justified objections are therefore most welcome..
>=20
>=20
> Regards,
> RD
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From despres.remi@laposte.net  Fri Oct 21 03:11:55 2011
Return-Path: <despres.remi@laposte.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 D115A21F8BEE for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 03:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.756
X-Spam-Level: 
X-Spam-Status: No, score=-1.756 tagged_above=-999 required=5 tests=[AWL=0.193,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QU510IhFYDFc for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 03:11:50 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by ietfa.amsl.com (Postfix) with ESMTP id 5627521F8BBB for <softwires@ietf.org>; Fri, 21 Oct 2011 03:11:47 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2109.sfr.fr (SMTP Server) with ESMTP id 655A070001CA; Fri, 21 Oct 2011 12:11:46 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2109.sfr.fr (SMTP Server) with ESMTP id E0502700019C; Fri, 21 Oct 2011 12:11:43 +0200 (CEST)
X-SFR-UUID: 20111021101143918.E0502700019C@msfrf2109.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <0C19F052-BA22-4A82-9FC7-665459A043A6@ipinfusion.com>
Date: Fri, 21 Oct 2011 12:11:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6340EFCC-397B-4059-97C2-FEDDD439D9EB@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <0C19F052-BA22-4A82-9FC7-665459A043A6@ipinfusion.com>
To: Tetsuya Murakami <tetsuya@ipinfusion.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 21 Oct 2011 10:11:56 -0000

Hi Tetsuya-san,
Please see below.

Le 21 oct. 2011 =E0 01:26, Tetsuya Murakami a =E9crit :

> Hi Remi,
>=20
> I am not sure if this proposal is good or not... But I think you are =
trying to introduce a new semantics for IPv6 fragmentation header. For =
this, I think the implementation of IPv6 stack must be changed to =
process your new fragmentation header. But I am not sure how to decide =
if the fragmentation header in the packet should be processed as either =
the normal fragmentation header or your new fragmentation header.

AFAIK, the proposal is a new use of the IPv6 fragmentation function =
which remains compatible with its current specification:
- 4rd sources select Identification-field values in a 4rd-specific way =
which does comply with existing constraints on these values.=20
- 4rd-capable destinations do IPv6 reassembly as usual, with only the =
additional feature that, when addresses are recognized as being 4rd, =
IPv4 specific information is extracted and  passed to the 4rd function. =20=

- 4rd-unable destinations won't receive any 4rd packets because 4rd =
destination addresses are different from others, e.g. with the recently =
proposed 4rd-specific V octet in address bit 64-71. (And even if they =
would receive 4rd packets, their reassembly function could work as =
usual.)

> Usually, IPv6 stack decides the processing for the following extension =
header based on the next header type. But you are using the same number =
of the existing fragmentation header for your new fragmentation header. =
If requiring any other information in the packet except the next header =
type, it might be a little bit painful from the implementation point of =
view.

Having a new header type would defeat the ability to use existing IPv6 =
O&M tools, a key objective of the proposal.
Fortunately, and as explained above, we have here a _new use_ of the =
existing fragmentation header, not a "new fragmentation header".


Regards,
RD


>=20
> Thanks,
> Tetsuya Murakami
>=20
> On 2011/10/17, at 5:36, R=E9mi Despr=E9s wrote:
>=20
>> Hi Satoru-san,
>>=20
>> Thank you for identifying a limitation of the 4rd-U =20
>> You are right, as currently specified, "it doesn't support diff-serv =
tunneling model, pipe and short-pipe".
>> All these need e2e transparency to the IPv4 Type of Service.
>>=20
>> Fortunately, this is easy to fix: in the Identification field of the =
IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
>>=20
>> The proposed 4r-U packet format becomes:
>>=20
>>=20
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |Vers=3D6 |   TrafClass   |            Flow Label                 |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |         Payload Length        |Next Header=3D44 |   Hop Limit   |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |                                                               |
>>  +                                                               +
>>  |                                                               |
>>  +                  IPv6 Source Address                          +
>>  |                                                               |
>>  +                                                               +
>>  |                                                               |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |                                                               |
>>  +                                                               +
>>  |                                                               |
>>  +                IPv6 Destination Address                       +
>>  |                                                               |
>>  +                                                               +
>>  |                                                               |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>  |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
>>  |                        IPv4 Payload                           |
>>  |                                                               |=20
>>=20
>> With this added, I believe that 4rd-U is a real progress over =
previously proposed Double translation and Encapsulation.
>> It can make IMHO a valuable unified standard.
>>=20
>> Yet, I may have missed something else.=20
>> New justified objections are therefore most welcome..
>>=20
>>=20
>> Regards,
>> RD
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20

From despres.remi@laposte.net  Fri Oct 21 03:14:43 2011
Return-Path: <despres.remi@laposte.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 5C0DB21F8C0B for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 03:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.764
X-Spam-Level: 
X-Spam-Status: No, score=-1.764 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g89oVEKFMrhS for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 03:14:42 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by ietfa.amsl.com (Postfix) with ESMTP id 62E0921F8BB1 for <softwires@ietf.org>; Fri, 21 Oct 2011 03:14:41 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2109.sfr.fr (SMTP Server) with ESMTP id D031170001CF; Fri, 21 Oct 2011 12:14:40 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2109.sfr.fr (SMTP Server) with ESMTP id 5F60570001B2; Fri, 21 Oct 2011 12:14:40 +0200 (CEST)
X-SFR-UUID: 20111021101440390.5F60570001B2@msfrf2109.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-4--565019882
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com>
Date: Fri, 21 Oct 2011 12:14:39 +0200
Message-Id: <91111240-FEA5-49F4-B877-197FFA46AE1B@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com>
To: Maoke <fibrib@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 21 Oct 2011 10:14:43 -0000

--Apple-Mail-4--565019882
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Maoke,
Please see below.

Le 20 oct. 2011 =E0 16:48, Maoke a =E9crit :

> hi Remi,
> =20
> thanks a lot for the reply! it is very helpful and my latest =
understanding almost approach it. but still some minor clarifications.
> 2011/10/20 R=E9mi Despr=E9s <remi.despres@free.fr>
> Hi Maoke,
>=20
> Thank you for your questions concerning relationships between IPv6 and =
IPv4 addressing plans.
>=20
> Here are address-planning steps that illustrate how an IPv6 addressing =
plan can be kept independent from IPv4 prefixes used for IPv4 residual =
deployment, even if CEs must be able to have different sharing ratios.
> =20
>   (A) IPv6 considerations
> (A1) Determine the maximum number N of CEs you want to support, a =
power of 2 (N =3D 2 ^ n).
> (A2) Choose the length x of IPv6 prefixes you want to assign to =
ordinary customers (e.g. x =3D 60)
> (A2) Multiply M by a margin coefficient K, a power of two (K =3D 2 ^ =
k), to take into account that:
> =20
> =20
> here the M should be a typo of "N", right? ;-)=20

Yes, thanks.

> =20
> =20
>  - Some privileged customers may be assigned IPv6 prefixes of length =
x', shorter than x, to have larger addressing spaces than ordinary =
customers, both in IPv6 and IPv4. =20
>  - Due to the hierarchy of routable prefixes, many theoretically =
delegatable prefixes may not be actually delegatable (ref: host density =
ratio of RFC 3194).
>=20
>   (B) IPv4 considerations
> (B1) List all (non overlapping) IPv4 prefixes Hi that are available =
for IPv4 residual deployment.
> (B2) Take enough of them, among the shortest ones, to get a total =
space whose size M is a power of two (M =3D 2 ^ m), and includes a good =
proportion of the available IPv4 space (ref =
www.ietf.org/mail-archive/web/softwires/current/msg02261.html).
> (B3) For each IPv4 prefix Hi of length hi, choose a "Rule index" Ri of =
length ri =3D m - hi. All these indexes must be non overlapping prefixes =
(e.g. 0, 10, 110, 111 for one /10, one /11, and two /12).

Oops, another bug :-(.
The right formula for ri is:  ri =3D m - (32 - hi)=20

>=20
>   (C) After (A) and (B)
> (C1) Derive the length c of the "Common prefix" C that will appear at =
the beginning of all delegatable prefixes (c =3D n + k - m)
> (C2) Take for C any prefix of length c that starts with a =
RIR-allocated IPv6 prefix
> (C3) For each IPv4 prefix Hi, make a rule in which it is the IPv4 =
prefix, and in which the IPv6 prefix is the Common prefix C followed by =
the Rule index Ri.
>=20
> I hope this can work on your favorite example(s).
> If not, please let me know.
> =20
> it seems you didn't mention the PSID part. my understanding is, after =
the above, when we have the, e.g., /60, the PSID is attached after the =
/60. then the CE delegated prefix (including IPv4 address suffix and =
PSID) may have different lengths if the sharing ratio is variant for =
different shared IPv4 addresses. but the c + m (or n + k, or x (right?)) =
, including the common prefix and the ipv4-address-related bits, is a =
constant for every CE-delegated network in the domain, right?

The PSID is WITHIN the /60 (at its end).

The IPv6 /64 prefix to be used to reach a CE contains:
1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches the =
IPv4 destination)
2) The IPv4 suffix (that part of the IPv4 destination that follows the =
IPv4 prefix of the matching rule)=20
3) The PSID (whose length is known iff the matching rule specifies a CE =
IPv6-prefix length)=20
4) If the PSID length is unknown, the "PSID complement" that completes =
the Max PSID.  =20
5) A 0 padding if fields 1 to 4 don't reach 64 bits

Note 1: If a Domain-IPv6-suffix option is used, the PSID length is =
necessarily known, and the PSID complement is then replaced by the =
Domain IPv6 suffix found in the matching rule. (ref =
draft-murakami-softwire-4rd-01.

Note 2: If ordinary CE IPv6 prefixes are /60s, the PSID complement has =
typically 4 bits (to fit in the /64).
The only exception is if the sharing ratio needs to exceed 256, so that =
the PSID length exceeds 8. Then, the PSID complement of less than 4 =
bits.  =20

> on the other hand, there is a limitation. if c + m > 64, the above =
address planning is not deployable, but with our effort of maximum =
compression,

> we believe the undeployable case rarely happens for normal providers, =
right?

Yes.

The only impossibility is if the available IPv4 space is so small that =
no sharing ratio can be sufficient for the number of IPv4 shared =
addresses to equal the number of ordinary CE IPv6 prefixes.



If the above is still unclear (or bugged!), thanks for letting me know.

Regards,
RD

=20


> =20
> Note that this is by no means to say that all ISPs should plan =
addresses this way (i.e. with a relationship between lengths of CE IPv6 =
prefixes and sharing ratios). It is just to show that this  is workable.
> =20
> =20
> sure. but i believe this will helps operators very much, considering =
up to now no operators have experienced that.
> =20
> thanks,
> maoke
> =20
> =20
> Regards,
> RD=20
> =20


--Apple-Mail-4--565019882
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Maoke,<div>Please see below.</div><div><br><div><div>Le 20 oct. 2011 =E0=
 16:48, Maoke a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>hi =
Remi, </div><div>&nbsp;</div><div>thanks a lot for the reply! it is very =
helpful and my latest understanding almost&nbsp;approach it. but still =
some minor clarifications.<br></div><div class=3D"gmail_quote">2011/10/20 =
R=E9mi Despr=E9s <span dir=3D"ltr">&lt;<a =
href=3D"mailto:remi.despres@free.fr">remi.despres@free.fr</a>&gt;</span><b=
r>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; =
border-left-color: rgb(204, 204, 204); border-left-width: 1px; =
border-left-style: solid;" class=3D"gmail_quote"><div style=3D"word-wrap: =
break-word;"><div>Hi Maoke,</div>
<div><br></div><div>Thank you for your questions concerning =
relationships between IPv6 and IPv4 addressing =
plans.</div><div><br></div><div>Here are address-planning steps =
that&nbsp;illustrate how an IPv6 addressing plan can be kept independent =
from IPv4 prefixes used for IPv4 residual deployment, even if CEs must =
be able to have different sharing ratios.</div>
<div>&nbsp;</div><div><div>&nbsp; (A) IPv6 considerations</div><div>(A1) =
Determine the maximum number N of CEs you want to support, a power of 2 =
(N =3D 2 ^ n).</div><div>(A2) Choose the length x of IPv6 prefixes you =
want to assign to ordinary customers (e.g. x =3D 60)</div>
<div>(A2) Multiply M by a margin coefficient K, a power of two (K =3D 2 =
^ k), to take into account =
that:</div><div>&nbsp;</div></div></div></blockquote><div>&nbsp;</div><div=
>here the M should be&nbsp;a typo of&nbsp;"N", =
right?&nbsp;;-)&nbsp;</div></div></blockquote><div><br></div>Yes, =
thanks.</div><div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote">
<div>&nbsp;</div><blockquote style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0.8ex; padding-left: 1ex; =
border-left-color: rgb(204, 204, 204); border-left-width: 1px; =
border-left-style: solid; position: static; z-index: auto; " =
class=3D"gmail_quote"><div style=3D"word-wrap: break-word;">
<div><div>&nbsp;</div><div>&nbsp;- Some privileged customers may be =
assigned IPv6 prefixes of length x', shorter than x, to have larger =
addressing spaces than ordinary customers, both in IPv6 and IPv4. =
&nbsp;</div><div>&nbsp;- Due to the hierarchy of routable prefixes, many =
theoretically delegatable prefixes may not be actually delegatable (ref: =
host density ratio of RFC 3194).</div>
<div><br></div><div>&nbsp; (B) IPv4 considerations</div><div>(B1) List =
all (non overlapping) IPv4 prefixes Hi that are available for IPv4 =
residual deployment.</div><div>(B2) Take enough of them, among the =
shortest ones, to get a total space whose size M is a power of two (M =3D =
2 ^ m), and includes a good proportion of the available IPv4 space (ref =
<a =
href=3D"http://www.ietf.org/mail-archive/web/softwires/current/msg02261.ht=
ml" =
target=3D"_blank">www.ietf.org/mail-archive/web/softwires/current/msg02261=
.html</a>).</div>
<div>(B3)&nbsp;For each IPv4 prefix Hi of length hi, choose a "Rule =
index" Ri of length ri =3D m - hi. All these indexes must be non =
overlapping prefixes (e.g. 0, 10, 110, 111 for one /10, one /11, and two =
/12).</div></div></div></blockquote></div></blockquote><div><br></div>Oops=
, another bug :-(.</div><div>The right formula for ri is: &nbsp;ri =3D m =
- (32 - hi)&nbsp;</div><div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><blockquote style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; padding-left: =
1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; =
border-left-style: solid; position: static; z-index: auto; " =
class=3D"gmail_quote"><div style=3D"word-wrap: break-word;"><div><div>
<br></div><div>&nbsp; (C) After (A) and (B)</div><div>(C1) Derive the =
length c of the "Common prefix" C that will appear at the beginning of =
all delegatable prefixes (c =3D n + k - m)</div><div>(C2) Take for C any =
prefix of length c that starts with a RIR-allocated IPv6 prefix</div>
<div>(C3) For each IPv4 prefix Hi, make a rule in which it is the IPv4 =
prefix, and in which the&nbsp;IPv6 prefix is the Common prefix C =
followed by the Rule index Ri.</div></div><div><br></div><div>I hope =
this can work on your favorite example(s).</div>
<div>If not, please let me =
know.</div></div></blockquote><div>&nbsp;</div><div>it seems you didn't =
mention the PSID part. my understanding is, after the above, when we =
have the, e.g., /60, the PSID is attached after the /60. then the =
CE&nbsp;delegated prefix&nbsp;(including IPv4 address suffix and PSID) =
may have different lengths if the sharing ratio is variant for different =
shared IPv4 addresses. but the c + m (or n + k, or x (right?)) , =
including the common prefix and the ipv4-address-related bits, is a =
constant for every CE-delegated network in the domain, right? =
</div></div></blockquote><div><br></div><div>The PSID is WITHIN the /60 =
(at its end).</div><div><br></div><div>The IPv6 /64 prefix to be used to =
reach a CE contains:</div><div>1) The Rule IPv6 prefix (that of the rule =
whose IPv4 prefix matches the IPv4 destination)</div><div>2) The IPv4 =
suffix (that part of the IPv4 destination that follows the IPv4 prefix =
of the matching rule)&nbsp;</div><div>3) The PSID (whose length is known =
iff&nbsp;the matching rule&nbsp;specifies a CE IPv6-prefix =
length)&nbsp;</div><div>4) If the PSID length is unknown, the "PSID =
complement" that completes the Max PSID. &nbsp;&nbsp;</div><div>5) A 0 =
padding if fields 1 to 4 don't reach 64 =
bits</div><div><br></div><div>Note 1: If a Domain-IPv6-suffix option is =
used, the PSID length is necessarily known, and the PSID complement is =
then replaced by the Domain IPv6 suffix found in the matching rule. (ref =
draft-murakami-softwire-4rd-01.</div><div><br></div><div>Note 2: If =
ordinary CE IPv6 prefixes are /60s, the PSID complement has typically 4 =
bits (to fit in the /64).</div><div>The only exception is if the sharing =
ratio needs to exceed 256, so that the PSID length exceeds 8. Then, the =
PSID complement of less than 4 bits. =
&nbsp;&nbsp;</div><div><br></div><blockquote type=3D"cite"><div =
class=3D"gmail_quote">
<div>on the other hand, there is a limitation. if c + m &gt; 64, the =
above address planning is not deployable, but with our effort of maximum =
compression, </div></div></blockquote><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>we believe the undeployable case rarely =
happens for normal providers, right? =
</div></div></blockquote><div><br></div>Yes.</div><div><br></div><div>The =
only impossibility is if the available IPv4 space is so small that no =
sharing ratio can be sufficient for the number of IPv4 shared addresses =
to equal the number of ordinary CE IPv6 =
prefixes.</div><div><br></div><div><br></div><div><br></div><div>If the =
above is still unclear (or bugged!), thanks for letting me =
know.</div><div><br></div><div>Regards,</div><div>RD</div><div><br></div><=
div>&nbsp;</div><div><br></div><div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote">
<div>&nbsp;</div><blockquote style=3D"margin: 0px 0px 0px 0.8ex; =
padding-left: 1ex; border-left-color: rgb(204, 204, 204); =
border-left-width: 1px; border-left-style: solid;" =
class=3D"gmail_quote"><div style=3D"word-wrap: break-word;">
<div></div><div>Note that this is by no means to say that all ISPs =
should plan addresses this way (i.e. with a relationship between lengths =
of CE IPv6 prefixes and sharing ratios). It is just to show that this =
&nbsp;is workable.</div>
<div>&nbsp;</div></div></blockquote><div>&nbsp;</div><div>sure. but i =
believe this will helps operators very much, considering up to now no =
operators have experienced that. =
</div><div>&nbsp;</div><div>thanks,</div><div>maoke</div><div>&nbsp;</div>=

<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; =
border-left-color: rgb(204, 204, 204); border-left-width: 1px; =
border-left-style: solid;" class=3D"gmail_quote"><div style=3D"word-wrap: =
break-word;"><div>&nbsp;</div>
=
<div>Regards,</div><div>RD&nbsp;</div><div>&nbsp;</div></div></blockquote>=
</div>
</blockquote></div><br></div></body></html>=

--Apple-Mail-4--565019882--

From fibrib@gmail.com  Fri Oct 21 04:34:19 2011
Return-Path: <fibrib@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 96FFA21F8BA8 for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 04:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.217
X-Spam-Level: 
X-Spam-Status: No, score=-3.217 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5VBlkGVGVjQI for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 04:34:18 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id A7BAF21F8BA6 for <softwires@ietf.org>; Fri, 21 Oct 2011 04:34:18 -0700 (PDT)
Received: by qyk34 with SMTP id 34so389049qyk.10 for <softwires@ietf.org>; Fri, 21 Oct 2011 04:34:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GZEvSflfR1u5n5xziwTU8bM9tmP43Odg2LZrcoyDiCg=; b=NwLQdTKM+v+PdreKDGadOcmyvdfNuZUBwd/L9yHLfSpIBchX5dgwhSbht5wnkBP2eK EHkTybAEW+YrapKyiAw8A+M9rEjqfCaunHNd14fRe/eQGzanAUNQOaJY1JU5p/bjaHEP lxADOTgbmR4Fk5z/S+wBdwkTlJ87xcAspZtY4=
MIME-Version: 1.0
Received: by 10.229.59.78 with SMTP id k14mr603236qch.69.1319196858066; Fri, 21 Oct 2011 04:34:18 -0700 (PDT)
Received: by 10.229.175.205 with HTTP; Fri, 21 Oct 2011 04:34:18 -0700 (PDT)
In-Reply-To: <91111240-FEA5-49F4-B877-197FFA46AE1B@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com> <91111240-FEA5-49F4-B877-197FFA46AE1B@laposte.net>
Date: Fri, 21 Oct 2011 20:34:18 +0900
Message-ID: <CAFUBMqUN3oZ-ZhDsQHhLzgrW5U9xVmUDiAvcpsG-pUKF3tBb4g@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=0016e6506c161d28f204afcd7406
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 21 Oct 2011 11:34:19 -0000

--0016e6506c161d28f204afcd7406
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Remi,

thanks for the further explanation. let me remove the cleared part and make
the message shorter. :P

2011/10/21 R=E9mi Despr=E9s <despres.remi@laposte.net>

>
>
>
>>   (B) IPv4 considerations
>> (B1) List all (non overlapping) IPv4 prefixes Hi that are available for
>> IPv4 residual deployment.
>> (B2) Take enough of them, among the shortest ones, to get a total space
>> whose size M is a power of two (M =3D 2 ^ m), and includes a good propor=
tion
>> of the available IPv4 space (ref
>> www.ietf.org/mail-archive/web/softwires/current/msg02261.html).
>> (B3) For each IPv4 prefix Hi of length hi, choose a "Rule index" Ri of
>> length ri =3D m - hi. All these indexes must be non overlapping prefixes=
 (e.g.
>> 0, 10, 110, 111 for one /10, one /11, and two /12).
>>
>
> Oops, another bug :-(.
> The right formula for ri is:  ri =3D m - (32 - hi)
>

yeah. :P i didn't discover that.

The PSID is WITHIN the /60 (at its end).
>

to clarify: WITHIN the /60 means within the address block of the /60, not
*within the first 60 bits*, (then at its end =3D starts from 61st bit),
right?


>
> The IPv6 /64 prefix to be used to reach a CE contains:
> 1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches the
> IPv4 destination)
> 2) The IPv4 suffix (that part of the IPv4 destination that follows the IP=
v4
> prefix of the matching rule)
>

the CE IPv6 prefix =3D 1) + 2), right?


> 3) The PSID (whose length is known iff the matching rule specifies a CE
> IPv6-prefix length)
>

the EA bits =3D 2) + 3), right?


>
> 4) If the PSID length is unknown, the "PSID complement" that completes th=
e
> Max PSID.
> 5) A 0 padding if fields 1 to 4 don't reach 64 bits
>
> Note 1: If a Domain-IPv6-suffix option is used, the PSID length is
> necessarily known, and the PSID complement is then replaced by the Domain
> IPv6 suffix found in the matching rule. (ref draft-murakami-softwire-4rd-=
01.
>

it seems to me that the draft-murakami-softwire-4rd-01 hasn't explain how d=
o
we use the "Domain IPv6 suffix", :(


> Note 2: If ordinary CE IPv6 prefixes are /60s, the PSID complement has
> typically 4 bits (to fit in the /64).
> The only exception is if the sharing ratio needs to exceed 256, so that t=
he
> PSID length exceeds 8. Then, the PSID complement of less than 4 bits.
>
> on the other hand, there is a limitation. if c + m > 64, the above addres=
s
> planning is not deployable, but with our effort of maximum compression,
>
> we believe the undeployable case rarely happens for normal providers,
> right?
>
>
> Yes.
>
> The only impossibility is if the available IPv4 space is so small that no
> sharing ratio can be sufficient for the number of IPv4 shared addresses t=
o
> equal the number of ordinary CE IPv6 prefixes.
>

sure. in this case we can help nothing.


> If the above is still unclear (or bugged!), thanks for letting me know.
>
>
Regards,
> RD
>

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

<div>Remi,=A0<br></div><div><br></div><div>thanks for the further explanati=
on. let me remove the cleared part and make the message shorter. :P</div><b=
r><div class=3D"gmail_quote">2011/10/21 R=E9mi Despr=E9s <span dir=3D"ltr">=
&lt;<a href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a=
>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:break-word">=A0<div=
><div><div class=3D"im"><blockquote type=3D"cite"><div class=3D"gmail_quote=
"><blockquote style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;ma=
rgin-left:0.8ex;padding-left:1ex;border-left-color:rgb(204, 204, 204);borde=
r-left-width:1px;border-left-style:solid" class=3D"gmail_quote">
<div style=3D"word-wrap:break-word">
<div><div>=A0<br></div><div>=A0 (B) IPv4 considerations</div><div>(B1) List=
 all (non overlapping) IPv4 prefixes Hi that are available for IPv4 residua=
l deployment.</div><div>(B2) Take enough of them, among the shortest ones, =
to get a total space whose size M is a power of two (M =3D 2 ^ m), and incl=
udes a good proportion of the available IPv4 space (ref <a href=3D"http://w=
ww.ietf.org/mail-archive/web/softwires/current/msg02261.html" target=3D"_bl=
ank">www.ietf.org/mail-archive/web/softwires/current/msg02261.html</a>).</d=
iv>

<div>(B3)=A0For each IPv4 prefix Hi of length hi, choose a &quot;Rule index=
&quot; Ri of length ri =3D m - hi. All these indexes must be non overlappin=
g prefixes (e.g. 0, 10, 110, 111 for one /10, one /11, and two /12).</div>
</div></div></blockquote></div></blockquote><div><br></div></div>Oops, anot=
her bug :-(.</div><div class=3D"im"><div>The right formula for ri is: =A0ri=
 =3D m - (32 - hi)=A0<br></div></div></div></div></blockquote><div><br></di=
v><div>
yeah. :P i didn&#39;t discover that.=A0<br></div><div><br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex;"><div style=3D"word-wrap:break-word"><div><div><div cla=
ss=3D"im">
<div>The PSID is WITHIN the /60 (at its end).</div></div></div></div></div>=
</blockquote><div><br></div><div>to clarify: WITHIN the /60 means within th=
e address block of the /60, not *within the first 60 bits*, (then at its en=
d =3D starts from 61st bit), right?=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:break=
-word"><div><div><div class=3D"im"><div><br></div><div>The IPv6 /64 prefix =
to be used to reach a CE contains:</div>
<div>1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches th=
e IPv4 destination)</div><div>2) The IPv4 suffix (that part of the IPv4 des=
tination that follows the IPv4 prefix of the matching rule)=A0</div></div>
</div></div></div></blockquote><div><br></div><div>the CE IPv6 prefix =3D 1=
) + 2), right?=A0</div><div>=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div s=
tyle=3D"word-wrap:break-word">
<div><div><div class=3D"im"><div>3) The PSID (whose length is known iff=A0t=
he matching rule=A0specifies a CE IPv6-prefix length)</div></div></div></di=
v></div></blockquote><div><br></div><div>the EA bits =3D 2) + 3), right?=A0=
</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:break=
-word"><div><div><div class=3D"im"><div>=A0</div><div>4) If the PSID length=
 is unknown, the &quot;PSID complement&quot; that completes the Max PSID. =
=A0=A0</div>
<div>5) A 0 padding if fields 1 to 4 don&#39;t reach 64 bits</div><div><br>=
</div><div>Note 1: If a Domain-IPv6-suffix option is used, the PSID length =
is necessarily known, and the PSID complement is then replaced by the Domai=
n IPv6 suffix found in the matching rule. (ref draft-murakami-softwire-4rd-=
01.<br>
</div></div></div></div></div></blockquote><div><br></div><div>it seems to =
me that the draft-murakami-softwire-4rd-01 hasn&#39;t explain how do we use=
 the &quot;Domain IPv6 suffix&quot;, :(=A0</div><div>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div><div><div class=3D"im"><div>Note 2=
: If ordinary CE IPv6 prefixes are /60s, the PSID complement has typically =
4 bits (to fit in the /64).</div><div>The only exception is if the sharing =
ratio needs to exceed 256, so that the PSID length exceeds 8. Then, the PSI=
D complement of less than 4 bits. =A0=A0</div>
<div><br></div></div><div class=3D"im"><blockquote type=3D"cite"><div class=
=3D"gmail_quote">
<div>on the other hand, there is a limitation. if c + m &gt; 64, the above =
address planning is not deployable, but with our effort of maximum compress=
ion,</div></div></blockquote><blockquote type=3D"cite"><div class=3D"gmail_=
quote">
<div>we believe the undeployable case rarely happens for normal providers, =
right? </div></div></blockquote><div><br></div></div>Yes.</div><div class=
=3D"im"><div><br></div><div>The only impossibility is if the available IPv4=
 space is so small that no sharing ratio can be sufficient for the number o=
f IPv4 shared addresses to equal the number of ordinary CE IPv6 prefixes.<b=
r>
</div></div></div></div></blockquote><div><br></div><div>sure. in this case=
 we can help nothing.=A0</div><div>=A0<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">
<div style=3D"word-wrap:break-word"><div><div class=3D"im"><div>If the abov=
e is still unclear (or bugged!), thanks for letting me know.</div><div>=A0<=
/div></div></div></div></blockquote><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div><div class=3D"im"><div>Regards,</d=
iv><div>RD</div></div></div></div></blockquote></div><div><br></div>

--0016e6506c161d28f204afcd7406--

From despres.remi@laposte.net  Fri Oct 21 06:20:50 2011
Return-Path: <despres.remi@laposte.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 71D0721F8BAD for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 06:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EJinlPCdIjLw for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 06:20:49 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 0852021F8BA6 for <softwires@ietf.org>; Fri, 21 Oct 2011 06:20:46 -0700 (PDT)
Received: from [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb] (unknown [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb]) by smtp1-g21.free.fr (Postfix) with ESMTP id 27DC594014A; Fri, 21 Oct 2011 15:20:40 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-5--553860130
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAFUBMqUN3oZ-ZhDsQHhLzgrW5U9xVmUDiAvcpsG-pUKF3tBb4g@mail.gmail.com>
Date: Fri, 21 Oct 2011 15:20:39 +0200
Message-Id: <B6A3090B-7704-4DF9-8869-C00445845CF2@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com> <91111240-FEA5-49F4-B877-197FFA46AE1B@laposte.net> <CAFUBMqUN3oZ-ZhDsQHhLzgrW5U9xVmUDiAvcpsG-pUKF3tBb4g@mail.gmail.com>
To: Maoke <fibrib@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 21 Oct 2011 13:20:50 -0000

--Apple-Mail-5--553860130
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 21 oct. 2011 =E0 13:34, Maoke a =E9crit :
...
> 2011/10/21 R=E9mi Despr=E9s <despres.remi@laposte.net>
...
> The PSID is WITHIN the /60 (at its end).
>=20
> to clarify: WITHIN the /60 means within the address block of the /60, =
not *within the first 60 bits*, (then at its end =3D starts from 61st =
bit), right?

It looks like we have a misunderstanding here, the origin of which I =
couldn't find, but which I am sure we can resolve.=20

In the 4rd-addmapping draft:
- The PSID is at the end of the CE Generalized IPv4 prefix (Fig 3)=20
- The CE index is at the end of the CE Generalized IPv4 prefix (Fig 2)
- The CE index is at the end of the CE IPv6 prefix (within it)

Consequently, if CE IPv6 prefixes are /60s, PSIDs are in my =
understanding "within the first 6O bits".

Extracts from the 4rd-addmapping draft:
- In Figure 2:
<----------------- at most 64 bits ------------------>
+-----------------------------------------------------+
|                   CE IPv6 prefix                    |  =20
+-----------------------------------------------------+  =20
:                                                     :  =20
+--------------------------------+--------------------+  =20
|        Rule IPv6 prefix        |     CE index       |  =20
+--------------------------------+--------------------+  =20
                                 :                    : =20
              +------------------+--------------------+ =20
              | Rule IPv4 prefix |     CE index       | =20
              +------------------+--------------------+ =20
              :                                       : =20
              +---------------------------------------+ =20
              |       CE Generalized IPv4 prefix      | =20
              +---------------------------------------+
              <----------- at most 44 bits ---------->
- In Figure 3:
               (C) CE Generalized IPv4 prefix having 33 to 44 bits
+--------------------------------------------------+
|       CE Generalized IPv4 prefix                 |=20
+--------------------------------------------------+=20
:                                                  :=20
+-------------------------------------------+------+=20
|              CE IPv4 address              | PSID |=20
+-------------------------------------------+------+
<----------------- 32 bits -----------------><--.-->
                                                |
                                          max 12 bits




> The IPv6 /64 prefix to be used to reach a CE contains:
> 1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches =
the IPv4 destination)
> 2) The IPv4 suffix (that part of the IPv4 destination that follows the =
IPv4 prefix of the matching rule)=20
>=20
> the CE IPv6 prefix =3D 1) + 2), right?=20
> =20
> 3) The PSID (whose length is known iff the matching rule specifies a =
CE IPv6-prefix length)
>=20
> the EA bits =3D 2) + 3), right?=20

Depending on what you call EA bits, it can be 2+3  or 2+3+4 in case of =
unknown CE-prefix length by sources


> =20
> 4) If the PSID length is unknown, the "PSID complement" that completes =
the Max PSID.  =20
> 5) A 0 padding if fields 1 to 4 don't reach 64 bits
>=20
> Note 1: If a Domain-IPv6-suffix option is used, the PSID length is =
necessarily known, and the PSID complement is then replaced by the =
Domain IPv6 suffix found in the matching rule. (ref =
draft-murakami-softwire-4rd-01.
>=20
> it seems to me that the draft-murakami-softwire-4rd-01 hasn't explain =
how do we use the "Domain IPv6 suffix", :(

Indeed.
That's why I wrote something about it in sec 5.5 of the 4rd-addmapping =
draft version -00 (where it is called the "CPE-cascade" option).
That was based on explanations received privately from Tetsuya Murakami.
However, having received neither approval nor criticism from him, or =
from anyone, I can't be sure it was accurate.
=20
In version -01, we decided to consider the subject out of scope, to be =
documented separately.=20
 =20
=20
>=20
> Note 2: If ordinary CE IPv6 prefixes are /60s, the PSID complement has =
typically 4 bits (to fit in the /64).
> The only exception is if the sharing ratio needs to exceed 256, so =
that the PSID length exceeds 8. Then, the PSID complement of less than 4 =
bits.  =20
>=20
>> on the other hand, there is a limitation. if c + m > 64, the above =
address planning is not deployable, but with our effort of maximum =
compression,
>> we believe the undeployable case rarely happens for normal providers, =
right?
>=20
> Yes.
>=20
> The only impossibility is if the available IPv4 space is so small that =
no sharing ratio can be sufficient for the number of IPv4 shared =
addresses to equal the number of ordinary CE IPv6 prefixes.
>=20
> sure. in this case we can help nothing.=20
> =20
> If the above is still unclear (or bugged!), thanks for letting me =
know.
> =20
> Regards,
> RD
>=20


--Apple-Mail-5--553860130
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 21 oct. 2011 =E0 13:34, Maoke a =E9crit =
:</div><div>...</div><blockquote type=3D"cite"><div =
class=3D"gmail_quote">2011/10/21 R=E9mi Despr=E9s <span dir=3D"ltr">&lt;<a=
 =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt;<=
/span></div></blockquote>...<br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div =
style=3D"word-wrap:break-word"><div><div><div class=3D"im">
<div>The PSID is WITHIN the /60 (at its =
end).</div></div></div></div></div></blockquote><div><br></div><div>to =
clarify: WITHIN the /60 means within the address block of the /60, not =
*within the first 60 bits*, (then at its end =3D starts from 61st bit), =
right?</div></div></blockquote><div><br></div>It looks like we have a =
misunderstanding here, the origin of which I couldn't find, but which I =
am sure we can resolve.&nbsp;</div><div><br></div><div>In the =
4rd-addmapping draft:</div><div>- The PSID is at the end of the CE =
Generalized IPv4 prefix (Fig 3)&nbsp;</div><div>- The CE index is at the =
end of the CE Generalized IPv4 prefix (Fig 2)</div><div>- The CE index =
is at the end of the CE IPv6 prefix (within =
it)</div><div><br></div><div>Consequently, if CE IPv6 prefixes are /60s, =
PSIDs are in my understanding "within the first 6O =
bits".</div><div><br></div><div>Extracts from the 4rd-addmapping =
draft:</div><div>- In Figure 2:</div><div><div>&lt;----------------- at =
most 64 bits =
------------------&gt;</div><div>+----------------------------------------=
-------------+</div><div>| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; CE IPv6 prefix &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| =
&nbsp;&nbsp;</div><div>+--------------------------------------------------=
---+ &nbsp;&nbsp;</div><div>: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : =
&nbsp;&nbsp;</div><div>+--------------------------------+-----------------=
---+ &nbsp;&nbsp;</div><div>| &nbsp; &nbsp; &nbsp; &nbsp;Rule IPv6 =
prefix &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; CE index &nbsp; &nbsp; =
&nbsp; | =
&nbsp;&nbsp;</div><div>+--------------------------------+-----------------=
---+ &nbsp;&nbsp;</div></div><div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;: &nbsp;</div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; +------------------+--------------------+ =
&nbsp;</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Rule =
IPv4 prefix | &nbsp; &nbsp; CE index &nbsp; &nbsp; &nbsp; | =
&nbsp;</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
+------------------+--------------------+ &nbsp;</div><div>&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; : &nbsp;</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; +---------------------------------------+ =
&nbsp;</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; CE Generalized IPv4 prefix &nbsp; &nbsp; &nbsp;| =
&nbsp;</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
+---------------------------------------+</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &lt;----------- at most 44 bits =
----------&gt;</div></div><div>- In Figure 3:</div><div><div>&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(C) CE Generalized IPv4 =
prefix having 33 to 44 =
bits</div><div>+--------------------------------------------------+</div><=
div>| &nbsp; &nbsp; &nbsp; CE Generalized IPv4 prefix &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
|&nbsp;</div><div>+--------------------------------------------------+&nbs=
p;</div><div>: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;:&nbsp;</div><div>+-------------------------------------------+-----=
-+&nbsp;</div><div>| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;CE =
IPv4 address &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| PSID =
|&nbsp;</div><div>+-------------------------------------------+------+</di=
v><div>&lt;----------------- 32 bits =
-----------------&gt;&lt;--.--&gt;</div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
|</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; max 12 =
bits</div></div><div><br></div><div><br></div><div><br></div><div><br></di=
v><div><blockquote type=3D"cite"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; =
border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; position: static; z-index: auto; "><div =
style=3D"word-wrap:break-word"><div><div><div class=3D"im"><div>The IPv6 =
/64 prefix to be used to reach a CE contains:</div>
<div>1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches =
the IPv4 destination)</div><div>2) The IPv4 suffix (that part of the =
IPv4 destination that follows the IPv4 prefix of the matching =
rule)&nbsp;</div></div>
</div></div></div></blockquote><div><br></div><div>the CE IPv6 prefix =3D =
1) + 2), right?&nbsp;</div><div>&nbsp;</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;"><div style=3D"word-wrap:break-word">
<div><div><div class=3D"im"><div>3) The PSID (whose length is known =
iff&nbsp;the matching rule&nbsp;specifies a CE IPv6-prefix =
length)</div></div></div></div></div></blockquote><div><br></div><div>the =
EA bits =3D 2) + 3), =
right?&nbsp;</div></div></blockquote><div><br></div><div>Depending on =
what you call EA bits, it can be 2+3 &nbsp;or 2+3+4 in case of unknown =
CE-prefix length by =
sources</div><div><br></div><div><br></div><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; "><div =
style=3D"word-wrap:break-word"><div><div><div =
class=3D"im"><div>&nbsp;</div><div>4) If the PSID length is unknown, the =
"PSID complement" that completes the Max PSID. &nbsp;&nbsp;</div>
<div>5) A 0 padding if fields 1 to 4 don't reach 64 =
bits</div><div><br></div><div>Note 1: If a Domain-IPv6-suffix option is =
used, the PSID length is necessarily known, and the PSID complement is =
then replaced by the Domain IPv6 suffix found in the matching rule. (ref =
draft-murakami-softwire-4rd-01.<br>
</div></div></div></div></div></blockquote><div><br></div><div>it seems =
to me that the draft-murakami-softwire-4rd-01 hasn't explain how do we =
use the "Domain IPv6 suffix", =
:(</div></div></blockquote><div><br></div>Indeed.</div><div>That's why I =
wrote&nbsp;something about it&nbsp;in sec 5.5 of the 4rd-addmapping =
draft version -00 (where it is called the "CPE-cascade" =
option).</div><div>That was based on explanations received privately =
from Tetsuya Murakami.</div><div>However, having received neither =
approval nor criticism from him, or from anyone, I can't be sure it was =
accurate.</div><div>&nbsp;</div><div>In version -01, we decided to =
consider the subject out of scope, to be documented =
separately.&nbsp;</div><div>&nbsp;&nbsp;</div><div>&nbsp;<blockquote =
type=3D"cite"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div><div><div class=3D"im"><div>Note =
2: If ordinary CE IPv6 prefixes are /60s, the PSID complement has =
typically 4 bits (to fit in the /64).</div><div>The only exception is if =
the sharing ratio needs to exceed 256, so that the PSID length exceeds =
8. Then, the PSID complement of less than 4 bits. &nbsp;&nbsp;</div>
<div><br></div></div><div class=3D"im"><blockquote type=3D"cite"><div =
class=3D"gmail_quote">
<div>on the other hand, there is a limitation. if c + m &gt; 64, the =
above address planning is not deployable, but with our effort of maximum =
compression,</div></div></blockquote><blockquote type=3D"cite"><div =
class=3D"gmail_quote">
<div>we believe the undeployable case rarely happens for normal =
providers, right? =
</div></div></blockquote><div><br></div></div>Yes.</div><div =
class=3D"im"><div><br></div><div>The only impossibility is if the =
available IPv4 space is so small that no sharing ratio can be sufficient =
for the number of IPv4 shared addresses to equal the number of ordinary =
CE IPv6 prefixes.<br>
</div></div></div></div></blockquote><div><br></div><div>sure. in this =
case we can help nothing.&nbsp;</div><div>&nbsp;<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div><div class=3D"im"><div>If the =
above is still unclear (or bugged!), thanks for letting me =
know.</div><div>&nbsp;</div></div></div></div></blockquote><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div><div =
class=3D"im"><div>Regards,</div><div>RD</div></div></div></div></blockquot=
e></div><div><br></div>
</blockquote></div><br></body></html>=

--Apple-Mail-5--553860130--

From washam.fan@gmail.com  Fri Oct 21 07:55:04 2011
Return-Path: <washam.fan@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 7AEE511E8095 for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 07:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJJziypd9Ysx for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 07:55:04 -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 C458521F8C19 for <softwires@ietf.org>; Fri, 21 Oct 2011 07:55:03 -0700 (PDT)
Received: by wyh22 with SMTP id 22so4584817wyh.31 for <softwires@ietf.org>; Fri, 21 Oct 2011 07:55:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Em2QKjln7bhGPU+yJEct2At0Naqi1chhuq+cgWjWK4o=; b=mYgqeQrIyIkc91+cscglFeJjodndC1s8RqRYlYPSBCHTQfVe2oMiz24JFJlfgON02p oTLVJ/smIz2MoJCwx8lBT90DqgvU+Q5WzB22UAYdS8DX+EDUUEi62wBj5lpWRLe812L+ HrEUQi3HhE+DnVIBf3dOZf9pB1kDNrTmYdXao=
MIME-Version: 1.0
Received: by 10.216.163.194 with SMTP id a44mr5616864wel.1.1319208902928; Fri, 21 Oct 2011 07:55:02 -0700 (PDT)
Received: by 10.216.85.4 with HTTP; Fri, 21 Oct 2011 07:55:02 -0700 (PDT)
In-Reply-To: <91111240-FEA5-49F4-B877-197FFA46AE1B@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com> <91111240-FEA5-49F4-B877-197FFA46AE1B@laposte.net>
Date: Fri, 21 Oct 2011 22:55:02 +0800
Message-ID: <CAAuHL_CWV=+262KvMbVGd0yQrfysifonUCMymX-rDpmKvpU2jw@mail.gmail.com>
From: Washam Fan <washam.fan@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 21 Oct 2011 14:55:04 -0000

Hi Remi,

Please see inline.

2011/10/21 R=E9mi Despr=E9s <despres.remi@laposte.net>:


> The PSID is WITHIN the /60 (at its end).
> The IPv6 /64 prefix to be used to reach a CE contains:
> 1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches the I=
Pv4
> destination)
> 2) The IPv4 suffix (that part of the IPv4 destination that follows the IP=
v4
> prefix of the matching rule)
> 3) The PSID (whose length is known iff=A0the matching rule=A0specifies a =
CE
> IPv6-prefix length)
> 4) If the PSID length is unknown, the "PSID complement" that completes th=
e
> Max PSID.
> 5) A 0 padding if fields 1 to 4 don't reach 64 bits

What if fields 1 to 4 exceed 64 bits? truncated, right?
Want to confirm again from you. The max length of CE IPv6 prefix is 64
bits, right?

Thanks,
washam

> Note 1: If a Domain-IPv6-suffix option is used, the PSID length is
> necessarily known, and the PSID complement is then replaced by the Domain
> IPv6 suffix found in the matching rule. (ref draft-murakami-softwire-4rd-=
01.
> Note 2: If ordinary CE IPv6 prefixes are /60s, the PSID complement has
> typically 4 bits (to fit in the /64).
> The only exception is if the sharing ratio needs to exceed 256, so that t=
he
> PSID length exceeds 8. Then, the PSID complement of less than 4 bits.

From despres.remi@laposte.net  Fri Oct 21 08:28:26 2011
Return-Path: <despres.remi@laposte.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 987981F0C6F for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 08:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.772
X-Spam-Level: 
X-Spam-Status: No, score=-1.772 tagged_above=-999 required=5 tests=[AWL=0.177,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U91uCronsm47 for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 08:28:26 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.82]) by ietfa.amsl.com (Postfix) with ESMTP id DFFE51F0C62 for <softwires@ietf.org>; Fri, 21 Oct 2011 08:28:25 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2406.sfr.fr (SMTP Server) with ESMTP id 221DA7000167; Fri, 21 Oct 2011 17:28:24 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2406.sfr.fr (SMTP Server) with ESMTP id BF4677000162; Fri, 21 Oct 2011 17:28:21 +0200 (CEST)
X-SFR-UUID: 20111021152821783.BF4677000162@msfrf2406.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAAuHL_CWV=+262KvMbVGd0yQrfysifonUCMymX-rDpmKvpU2jw@mail.gmail.com>
Date: Fri, 21 Oct 2011 17:28:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C90764A2-9251-495A-9E81-B17DF791B6C2@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com> <91111240-FEA5-49F4-B877-197FFA46AE1B@laposte.net> <CAAuHL_CWV=+262KvMbVGd0yQrfysifonUCMymX-rDpmKvpU2jw@mail.gmail.com>
To: Washam Fan <washam.fan@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 21 Oct 2011 15:28:26 -0000

Hi Washam,
=20
Le 21 oct. 2011 =E0 16:55, Washam Fan a =E9crit :

> Hi Remi,
>=20
> Please see inline.
>=20
> 2011/10/21 R=E9mi Despr=E9s <despres.remi@laposte.net>:
>=20
>=20
>> The PSID is WITHIN the /60 (at its end).
>> The IPv6 /64 prefix to be used to reach a CE contains:
>> 1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches =
the IPv4
>> destination)
>> 2) The IPv4 suffix (that part of the IPv4 destination that follows =
the IPv4
>> prefix of the matching rule)
>> 3) The PSID (whose length is known iff the matching rule specifies a =
CE
>> IPv6-prefix length)
>> 4)=20
>> 5) A 0 padding if fields 1 to 4 don't reach 64 bits
>=20
> What if fields 1 to 4 exceed 64 bits? truncated, right?

Yes.
4) would have better been written "If the PSID length is unknown, the =
"PSID complement" (remainder of the Max PSID, truncated if necessary for =
the subnet prefix not to exceed 64 bits).

> Want to confirm again from you. The max length of CE IPv6 prefix is 64
> bits, right?

Yes.

Regards,
RD



From fibrib@gmail.com  Fri Oct 21 10:30:02 2011
Return-Path: <fibrib@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 8A0B51F0C8C for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 10:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.221
X-Spam-Level: 
X-Spam-Status: No, score=-3.221 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5MLeTdxG1C5 for <softwires@ietfa.amsl.com>; Fri, 21 Oct 2011 10:30:01 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 3689B1F0C87 for <softwires@ietf.org>; Fri, 21 Oct 2011 10:30:01 -0700 (PDT)
Received: by qyk31 with SMTP id 31so3702709qyk.10 for <softwires@ietf.org>; Fri, 21 Oct 2011 10:30:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xZ0pgxs8i3ECGWc9Fyq090wl6DpSuoACVLHxpUeui1w=; b=uv2IYjg9tWzBYLAfHTztn0YMr+zQme8jqkvCjoSa96yvdNagAl3nT6z4pHe7QsIViR +0jFzlr8bWv/FhdMH4xFm7sOynASkBUuPA+jx+JopqRVg55PONniFw4ygTWeQ2Z0KZu8 Nx5DG8AhevnhxhG+d3CUgBVBJrb9LJj9izVvk=
MIME-Version: 1.0
Received: by 10.229.59.78 with SMTP id k14mr856445qch.69.1319218200666; Fri, 21 Oct 2011 10:30:00 -0700 (PDT)
Received: by 10.229.175.205 with HTTP; Fri, 21 Oct 2011 10:30:00 -0700 (PDT)
In-Reply-To: <B6A3090B-7704-4DF9-8869-C00445845CF2@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com> <91111240-FEA5-49F4-B877-197FFA46AE1B@laposte.net> <CAFUBMqUN3oZ-ZhDsQHhLzgrW5U9xVmUDiAvcpsG-pUKF3tBb4g@mail.gmail.com> <B6A3090B-7704-4DF9-8869-C00445845CF2@laposte.net>
Date: Sat, 22 Oct 2011 02:30:00 +0900
Message-ID: <CAFUBMqWq8+uZzmGV=LebK3k1rb=hNhVAJ28dub7pGc6c5Ra04Q@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=0016e6506c163b630304afd26cec
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 21 Oct 2011 17:30:02 -0000

--0016e6506c163b630304afd26cec
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Remi,

thanks for the further explanation.

2011/10/21 R=E9mi Despr=E9s <despres.remi@laposte.net>

>
> Le 21 oct. 2011 =E0 13:34, Maoke a =E9crit :
> ...
>
> 2011/10/21 R=E9mi Despr=E9s <despres.remi@laposte.net>
>
> ...
>
> The PSID is WITHIN the /60 (at its end).
>>
>
> to clarify: WITHIN the /60 means within the address block of the /60, not
> *within the first 60 bits*, (then at its end =3D starts from 61st bit), r=
ight?
>
>
> It looks like we have a misunderstanding here, the origin of which I
> couldn't find, but which I am sure we can resolve.
>
> In the 4rd-addmapping draft:
> - The PSID is at the end of the CE Generalized IPv4 prefix (Fig 3)
> - The CE index is at the end of the CE Generalized IPv4 prefix (Fig 2)
> - The CE index is at the end of the CE IPv6 prefix (within it)
>
> Consequently, if CE IPv6 prefixes are /60s, PSIDs are in my understanding
> "within the first 6O bits".
>
> Extracts from the 4rd-addmapping draft:
> - In Figure 2:
> <----------------- at most 64 bits ------------------>
> +-----------------------------------------------------+
> |                   CE IPv6 prefix                    |
> +-----------------------------------------------------+
> :                                                     :
> +--------------------------------+--------------------+
> |        Rule IPv6 prefix        |     CE index       |
> +--------------------------------+--------------------+
>                                  :                    :
>               +------------------+--------------------+
>               | Rule IPv4 prefix |     CE index       |
>               +------------------+--------------------+
>               :                                       :
>               +---------------------------------------+
>               |       CE Generalized IPv4 prefix      |
>               +---------------------------------------+
>               <----------- at most 44 bits ---------->
> - In Figure 3:
>                (C) CE Generalized IPv4 prefix having 33 to 44 bits
> +--------------------------------------------------+
> |       CE Generalized IPv4 prefix                 |
> +--------------------------------------------------+
> :                                                  :
> +-------------------------------------------+------+
> |              CE IPv4 address              | PSID |
> +-------------------------------------------+------+
> <----------------- 32 bits -----------------><--.-->
>                                                 |
>                                           max 12 bits
>
>
>
>
> The IPv6 /64 prefix to be used to reach a CE contains:
>> 1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches the
>> IPv4 destination)
>> 2) The IPv4 suffix (that part of the IPv4 destination that follows the
>> IPv4 prefix of the matching rule)
>>
>
> the CE IPv6 prefix =3D 1) + 2), right?
>
>
>> 3) The PSID (whose length is known iff the matching rule specifies a CE
>> IPv6-prefix length)
>>
>
> the EA bits =3D 2) + 3), right?
>
>
> Depending on what you call EA bits, it can be 2+3  or 2+3+4 in case of
> unknown CE-prefix length by sources
>
>
after check with some examples i can cautiously say i accept your point, :)
(i was concerning if you wasted some port-set of some IPv4 addresses if the
PSID are in different length but it seems the rough check illustrate no suc=
h
a possibility).

may i understand it as: although variant PSID attached *after* instead of
being inside in the prefixes having a common length is also deployable, but
it is not what the residual deployment means. the purpose is: when deployin=
g
IPv6 network, we try to assign the (not-yet-used) IPv4 addresses and sharin=
g
them, if they are not many enough to support 1:1, for those CEs whose
delegated network may still need IPv4 communications.
therefore, the address planning is always deployable in the sense of IPv6
but if we can provide good IPv4 communicability for these IPv6 CE-delegated
networks depends on how many IPv4 address we have and how small port-set we
can suffer.
is this of my understanding right now?


>
>
>
>> 4) If the PSID length is unknown, the "PSID complement" that completes t=
he
>> Max PSID.
>> 5) A 0 padding if fields 1 to 4 don't reach 64 bits
>>
>> Note 1: If a Domain-IPv6-suffix option is used, the PSID length is
>> necessarily known, and the PSID complement is then replaced by the Domai=
n
>> IPv6 suffix found in the matching rule. (ref draft-murakami-softwire-4rd=
-01.
>>
>
> it seems to me that the draft-murakami-softwire-4rd-01 hasn't explain how
> do we use the "Domain IPv6 suffix", :(
>
>
> Indeed.
> That's why I wrote something about it in sec 5.5 of the 4rd-addmapping
> draft version -00 (where it is called the "CPE-cascade" option).
> That was based on explanations received privately from Tetsuya Murakami.
> However, having received neither approval nor criticism from him, or from
> anyone, I can't be sure it was accurate.
>
> In version -01, we decided to consider the subject out of scope, to be
> documented separately.
>
>
>
> Note 2: If ordinary CE IPv6 prefixes are /60s, the PSID complement has
>> typically 4 bits (to fit in the /64).
>> The only exception is if the sharing ratio needs to exceed 256, so that
>> the PSID length exceeds 8. Then, the PSID complement of less than 4 bits=
.
>>
>> on the other hand, there is a limitation. if c + m > 64, the above addre=
ss
>> planning is not deployable, but with our effort of maximum compression,
>>
>> we believe the undeployable case rarely happens for normal providers,
>> right?
>>
>>
>> Yes.
>>
>> The only impossibility is if the available IPv4 space is so small that n=
o
>> sharing ratio can be sufficient for the number of IPv4 shared addresses =
to
>> equal the number of ordinary CE IPv6 prefixes.
>>
>
> sure. in this case we can help nothing.
>
>
>> If the above is still unclear (or bugged!), thanks for letting me know.
>>
>>
> Regards,
>> RD
>>
>
>
>

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

<div>hi Remi, </div><div>=A0</div><div>thanks for the further explanation. =
<br><br></div><div class=3D"gmail_quote">2011/10/21 R=E9mi Despr=E9s <span =
dir=3D"ltr">&lt;<a href=3D"mailto:despres.remi@laposte.net">despres.remi@la=
poste.net</a>&gt;</span><br>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote"><div style=3D"word-wrap: break-word;"><br><div=
><div>
Le 21 oct. 2011 =E0 13:34, Maoke a =E9crit :</div><div>...</div><blockquote=
 type=3D"cite"><div class=3D"gmail_quote">2011/10/21 R=E9mi Despr=E9s <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:despres.remi@laposte.net" target=3D"_bla=
nk">despres.remi@laposte.net</a>&gt;</span></div>
</blockquote>...<div class=3D"im"><br><blockquote type=3D"cite"><div class=
=3D"gmail_quote"><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-le=
ft: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; bor=
der-left-style: solid;" class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;"><div><div><div>
<div>The PSID is WITHIN the /60 (at its end).</div></div></div></div></div>=
</blockquote><div><br></div><div>to clarify: WITHIN the /60 means within th=
e address block of the /60, not *within the first 60 bits*, (then at its en=
d =3D starts from 61st bit), right?</div>
</div></blockquote><div><br></div></div>It looks like we have a misundersta=
nding here, the origin of which I couldn&#39;t find, but which I am sure we=
 can resolve.=A0</div><div><br></div><div>In the 4rd-addmapping draft:</div=
>
<div>- The PSID is at the end of the CE Generalized IPv4 prefix (Fig 3)=A0<=
/div><div>- The CE index is at the end of the CE Generalized IPv4 prefix (F=
ig 2)</div><div>- The CE index is at the end of the CE IPv6 prefix (within =
it)</div>
<div><br></div><div>Consequently, if CE IPv6 prefixes are /60s, PSIDs are i=
n my understanding &quot;within the first 6O bits&quot;.</div><div><br></di=
v><div>Extracts from the 4rd-addmapping draft:</div><div>- In Figure 2:</di=
v>
<div><div>&lt;----------------- at most 64 bits ------------------&gt;</div=
><div>+-----------------------------------------------------+</div><div>| =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 CE IPv6 prefix =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0| =A0=A0</div><div>+----------------------------------------=
-------------+ =A0=A0</div>
<div>: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 : =A0=A0</div><div>+-------------------=
-------------+--------------------+ =A0=A0</div><div>| =A0 =A0 =A0 =A0Rule =
IPv6 prefix =A0 =A0 =A0 =A0| =A0 =A0 CE index =A0 =A0 =A0 | =A0=A0</div><di=
v>+--------------------------------+--------------------+ =A0=A0</div>
</div><div><div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: =A0</div><div>=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 +------------------+--------------------+ =A0</div><div=
>=A0 =A0 =A0 =A0 =A0 =A0 =A0 | Rule IPv4 prefix | =A0 =A0 CE index =A0 =A0 =
=A0 | =A0</div><div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 +------------------+-------=
-------------+ =A0</div>
<div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 : =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 : =A0</div><div>=A0 =A0 =A0 =A0 =A0 =A0=
 =A0 +---------------------------------------+ =A0</div><div>=A0 =A0 =A0 =
=A0 =A0 =A0 =A0 | =A0 =A0 =A0 CE Generalized IPv4 prefix =A0 =A0 =A0| =A0</=
div><div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 +-------------------------------------=
--+</div>
<div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 &lt;----------- at most 44 bits ----------=
&gt;</div></div><div>- In Figure 3:</div><div><div>=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0(C) CE Generalized IPv4 prefix having 33 to 44 bits</div><div>+-----=
---------------------------------------------+</div>
<div>| =A0 =A0 =A0 CE Generalized IPv4 prefix =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 |=A0</div><div>+--------------------------------------------------+=A0<=
/div><div>: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0:=A0</div><div>+-----------------------=
--------------------+------+=A0</div>
<div>| =A0 =A0 =A0 =A0 =A0 =A0 =A0CE IPv4 address =A0 =A0 =A0 =A0 =A0 =A0 =
=A0| PSID |=A0</div><div>+-------------------------------------------+-----=
-+</div><div>&lt;----------------- 32 bits -----------------&gt;&lt;--.--&g=
t;</div><div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |</div>
<div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 max 12 bits</div></div><div><br></div><div><br></div><div><=
br></div><div><br></div><div><div class=3D"im"><blockquote type=3D"cite"><d=
iv class=3D"gmail_quote"><blockquote style=3D"margin: 0px 0px 0px 0.8ex; pa=
dding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: =
1px; border-left-style: solid;" class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;"><div><div><div><div>The IPv6 /64 pref=
ix to be used to reach a CE contains:</div>
<div>1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches th=
e IPv4 destination)</div><div>2) The IPv4 suffix (that part of the IPv4 des=
tination that follows the IPv4 prefix of the matching rule)=A0</div></div>

</div></div></div></blockquote><div><br></div><div>the CE IPv6 prefix =3D 1=
) + 2), right?=A0</div><div>=A0</div><blockquote style=3D"margin: 0px 0px 0=
px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-=
left-width: 1px; border-left-style: solid;" class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;">
<div><div><div><div>3) The PSID (whose length is known iff=A0the matching r=
ule=A0specifies a CE IPv6-prefix length)</div></div></div></div></div></blo=
ckquote><div><br></div><div>the EA bits =3D 2) + 3), right?=A0</div></div><=
/blockquote>
<div><br></div></div><div>Depending on what you call EA bits, it can be 2+3=
 =A0or 2+3+4 in case of unknown CE-prefix length by sources</div><div class=
=3D"im"><div><br></div></div></div></div></blockquote><div>=A0</div><div><d=
iv>
after check with some examples i can cautiously=A0say i accept your point, =
:) (i was concerning if you wasted some=A0port-set=A0of some IPv4 addresses=
=A0if the PSID are in different length but it seems the rough check illustr=
ate no such a possibility).</div>
<div>=A0</div><div>may i understand it as: although variant PSID attached *=
after* instead of being inside in the prefixes having a common length is al=
so deployable, but it is not what the residual deployment means. the purpos=
e is: when deploying IPv6 network, we try to assign the (not-yet-used) IPv4=
 addresses and sharing them, if they are not many enough to support 1:1, fo=
r those CEs whose delegated network may still need IPv4 communications. </d=
iv>
<div> </div><div>therefore, the address planning is always deployable in th=
e sense of IPv6 but if we can provide good IPv4 communicability for these I=
Pv6 CE-delegated networks depends on how many IPv4 address we have and how =
small port-set we can suffer. </div>
<div> </div><div>is this of my understanding right now? </div></div><div>=
=A0</div><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex;=
 border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left=
-style: solid;" class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;"><div><div class=3D"im"><div>=A0</div>=
<blockquote type=3D"cite"><div class=3D"gmail_quote"><blockquote style=3D"m=
argin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 20=
4, 204); border-left-width: 1px; border-left-style: solid;" class=3D"gmail_=
quote">
<div style=3D"word-wrap: break-word;"><div><div><div><div>=A0</div><div>4) =
If the PSID length is unknown, the &quot;PSID complement&quot; that complet=
es the Max PSID. =A0=A0</div>
<div>5) A 0 padding if fields 1 to 4 don&#39;t reach 64 bits</div><div><br>=
</div><div>Note 1: If a Domain-IPv6-suffix option is used, the PSID length =
is necessarily known, and the PSID complement is then replaced by the Domai=
n IPv6 suffix found in the matching rule. (ref draft-murakami-softwire-4rd-=
01.<br>

</div></div></div></div></div></blockquote><div><br></div><div>it seems to =
me that the draft-murakami-softwire-4rd-01 hasn&#39;t explain how do we use=
 the &quot;Domain IPv6 suffix&quot;, :(</div></div></blockquote><div><br>
</div></div>Indeed.</div><div>That&#39;s why I wrote=A0something about it=
=A0in sec 5.5 of the 4rd-addmapping draft version -00 (where it is called t=
he &quot;CPE-cascade&quot; option).</div><div>That was based on explanation=
s received privately from Tetsuya Murakami.</div>
<div>However, having received neither approval nor criticism from him, or f=
rom anyone, I can&#39;t be sure it was accurate.</div><div>=A0</div><div>In=
 version -01, we decided to consider the subject out of scope, to be docume=
nted separately.=A0</div>
<div class=3D"im"><div>=A0=A0</div><div>=A0<blockquote type=3D"cite"><div c=
lass=3D"gmail_quote"><blockquote style=3D"margin: 0px 0px 0px 0.8ex; paddin=
g-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px;=
 border-left-style: solid;" class=3D"gmail_quote">

<div style=3D"word-wrap: break-word;"><div><div><div><div>Note 2: If ordina=
ry CE IPv6 prefixes are /60s, the PSID complement has typically 4 bits (to =
fit in the /64).</div><div>The only exception is if the sharing ratio needs=
 to exceed 256, so that the PSID length exceeds 8. Then, the PSID complemen=
t of less than 4 bits. =A0=A0</div>

<div><br></div></div><div><blockquote type=3D"cite"><div class=3D"gmail_quo=
te">
<div>on the other hand, there is a limitation. if c + m &gt; 64, the above =
address planning is not deployable, but with our effort of maximum compress=
ion,</div></div></blockquote><blockquote type=3D"cite"><div class=3D"gmail_=
quote">

<div>we believe the undeployable case rarely happens for normal providers, =
right? </div></div></blockquote><div><br></div></div>Yes.</div><div><div><b=
r></div><div>The only impossibility is if the available IPv4 space is so sm=
all that no sharing ratio can be sufficient for the number of IPv4 shared a=
ddresses to equal the number of ordinary CE IPv6 prefixes.<br>

</div></div></div></div></blockquote><div><br></div><div>sure. in this case=
 we can help nothing.=A0</div><div>=A0<br></div><blockquote style=3D"margin=
: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 20=
4); border-left-width: 1px; border-left-style: solid;" class=3D"gmail_quote=
">

<div style=3D"word-wrap: break-word;"><div><div><div>If the above is still =
unclear (or bugged!), thanks for letting me know.</div><div>=A0</div></div>=
</div></div></blockquote><blockquote style=3D"margin: 0px 0px 0px 0.8ex; pa=
dding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: =
1px; border-left-style: solid;" class=3D"gmail_quote">

<div style=3D"word-wrap: break-word;"><div><div><div>Regards,</div><div>RD<=
/div></div></div></div></blockquote></div><div><br></div>
</blockquote></div><br></div></div></blockquote></div><br>

--0016e6506c163b630304afd26cec--

From despres.remi@laposte.net  Sat Oct 22 00:20:35 2011
Return-Path: <despres.remi@laposte.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 19B6511E80B4 for <softwires@ietfa.amsl.com>; Sat, 22 Oct 2011 00:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.78
X-Spam-Level: 
X-Spam-Status: No, score=-1.78 tagged_above=-999 required=5 tests=[AWL=0.169,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aq1QV7sxsYjL for <softwires@ietfa.amsl.com>; Sat, 22 Oct 2011 00:20:34 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by ietfa.amsl.com (Postfix) with ESMTP id 8946611E807F for <softwires@ietf.org>; Sat, 22 Oct 2011 00:20:34 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2309.sfr.fr (SMTP Server) with ESMTP id 6318C700017A; Sat, 22 Oct 2011 09:20:32 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2309.sfr.fr (SMTP Server) with ESMTP id 2CD087000175; Sat, 22 Oct 2011 09:20:31 +0200 (CEST)
X-SFR-UUID: 20111022072032183.2CD087000175@msfrf2309.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sat, 22 Oct 2011 09:20:31 +0200
Message-Id: <2E551C74-6D33-4EE1-A923-6C8C80F59831@laposte.net>
To: Ole Troan <otroan@employees.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: [Softwires] Be on the Address-Mapping mailing list
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, 22 Oct 2011 07:20:35 -0000

Hi Ole,

In view of the ongoing discussion on the Softwire mailing list about the =
possible unification of double-translation and encapsulation packet =
formats (4rd-U), I continue to participate in the current work more than =
I was planning to.
Since there is a relationship between 4rd-U and v4-to-v6 address mapping =
(advantage of having checksum neutrality), I think it would then be =
useful that I also have access to the mailing list you opened for =
address-mapping discussions.
Thanks for adding me to it.

Regards,
RD=

From fibrib@gmail.com  Sun Oct 23 09:25:38 2011
Return-Path: <fibrib@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 9E68221F8AF2 for <softwires@ietfa.amsl.com>; Sun, 23 Oct 2011 09:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.761
X-Spam-Level: 
X-Spam-Status: No, score=-2.761 tagged_above=-999 required=5 tests=[AWL=0.538,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WekxFdQbc0DJ for <softwires@ietfa.amsl.com>; Sun, 23 Oct 2011 09:25:37 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 550BF21F8AF0 for <softwires@ietf.org>; Sun, 23 Oct 2011 09:25:37 -0700 (PDT)
Received: by wwe6 with SMTP id 6so5540111wwe.13 for <softwires@ietf.org>; Sun, 23 Oct 2011 09:25:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZX9Cov+u9fHWF2ZX4WUhQLWz1TqGtHyZVHPwmyyNx1E=; b=RhMwYG52NIfV25Drk8fMtVIK9P1CeOkyM6gW2ST5ewbs3fq/Bz4K92vvTLtFe0XbHL i2lyC8eucme6vBe9jrFTVPreSBN3sXqtP8l5kd0os+woZgvc1/Lp9aN3+OvsDkyurDSq 2+J+SKKn4OyaTTfQPy58oP4qoxdDavSuBFIVY=
MIME-Version: 1.0
Received: by 10.216.221.31 with SMTP id q31mr2088828wep.37.1319387133459; Sun, 23 Oct 2011 09:25:33 -0700 (PDT)
Received: by 10.216.188.204 with HTTP; Sun, 23 Oct 2011 09:25:33 -0700 (PDT)
In-Reply-To: <817DF09F-2196-4A61-BC4C-5A7EE56EEFD1@free.fr>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com> <817DF09F-2196-4A61-BC4C-5A7EE56EEFD1@free.fr>
Date: Mon, 24 Oct 2011 01:25:33 +0900
Message-ID: <CAFUBMqW13cMFSzNYR3yudQJE4q5tv78akT1ikzoBvVRYabdnVA@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: multipart/alternative; boundary=0016e65aeeaa693f4f04aff9c1fc
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 23 Oct 2011 16:25:38 -0000

--0016e65aeeaa693f4f04aff9c1fc
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi Remi,

2011/10/21 R=E9mi Despr=E9s <remi.despres@free.fr>

> Maoke,
> Please see below.
>
> Le 20 oct. 2011 =E0 16:48, Maoke a =E9crit :
>
> hi Remi,
>
> thanks a lot for the reply! it is very helpful and my latest understandin=
g
> almost approach it. but still some minor clarifications.
> 2011/10/20 R=E9mi Despr=E9s <remi.despres@free.fr>
>
>> Hi Maoke,
>>
>> Thank you for your questions concerning relationships between IPv6 and
>> IPv4 addressing plans.
>>
>> Here are address-planning steps that illustrate how an IPv6 addressing
>> plan can be kept independent from IPv4 prefixes used for IPv4 residual
>> deployment, even if CEs must be able to have different sharing ratios.
>>
>>   (A) IPv6 considerations
>> (A1) Determine the maximum number N of CEs you want to support, a power =
of
>> 2 (N =3D 2 ^ n).
>> (A2) Choose the length x of IPv6 prefixes you want to assign to ordinary
>> customers (e.g. x =3D 60)
>> (A2) Multiply M by a margin coefficient K, a power of two (K =3D 2 ^ k),=
 to
>> take into account that:
>>
>>
>
> here the M should be a typo of "N", right? ;-)
>
>
> Yes, thanks.
>
>
>
>>
>>  - Some privileged customers may be assigned IPv6 prefixes of length x',
>> shorter than x, to have larger addressing spaces than ordinary customers=
,
>> both in IPv6 and IPv4.
>>  - Due to the hierarchy of routable prefixes, many theoretically
>> delegatable prefixes may not be actually delegatable (ref: host density
>> ratio of RFC 3194).
>>
>>   (B) IPv4 considerations
>> (B1) List all (non overlapping) IPv4 prefixes Hi that are available for
>> IPv4 residual deployment.
>> (B2) Take enough of them, among the shortest ones, to get a total space
>> whose size M is a power of two (M =3D 2 ^ m), and includes a good propor=
tion
>> of the available IPv4 space (ref
>> www.ietf.org/mail-archive/web/softwires/current/msg02261.html).
>> (B3) For each IPv4 prefix Hi of length hi, choose a "Rule index" Ri of
>> length ri =3D m - hi. All these indexes must be non overlapping prefixes=
 (e.g.
>> 0, 10, 110, 111 for one /10, one /11, and two /12).
>>
>
> Oops, another bug :-(.
> The right formula for ri is:  ri =3D m - (32 - hi)
>
>
>>   (C) After (A) and (B)
>> (C1) Derive the length c of the "Common prefix" C that will appear at th=
e
>> beginning of all delegatable prefixes (c =3D n + k - m)
>>
>>
>
 is this another bug? i think:

|<------------        x       ---------------->|
|            |<---------   n   ----------->|<k>|
+------------+---------+-------------+-----+---+
|Common Pref.|Rule idx | IPv4 suffix |PSID |   |
+------------+---------+-------------+-----+---+
|            |<---------   m  ------>|
|<--- c ---->|<-- ri ->|<--- hi ---->|

and thus c =3D x - (n + k), right? ;-)

cheers,
maoke

>
>> (C2) Take for C any prefix of length c that starts with a RIR-allocated
>> IPv6 prefix
>> (C3) For each IPv4 prefix Hi, make a rule in which it is the IPv4 prefix=
,
>> and in which the IPv6 prefix is the Common prefix C followed by the Rule
>> index Ri.
>>
>> I hope this can work on your favorite example(s).
>> If not, please let me know.
>>
>
> it seems you didn't mention the PSID part. my understanding is, after the
> above, when we have the, e.g., /60, the PSID is attached after the /60. t=
hen
> the CE delegated prefix (including IPv4 address suffix and PSID) may have
> different lengths if the sharing ratio is variant for different shared IP=
v4
> addresses. but the c + m (or n + k, or x (right?)) , including the common
> prefix and the ipv4-address-related bits, is a constant for every
> CE-delegated network in the domain, right?
>
>
> The PSID is WITHIN the /60 (at its end).
>
> The IPv6 /64 prefix to be used to reach a CE contains:
> 1) The Rule IPv6 prefix (that of the rule whose IPv4 prefix matches the
> IPv4 destination)
> 2) The IPv4 suffix (that part of the IPv4 destination that follows the IP=
v4
> prefix of the matching rule)
> 3) The PSID (whose length is known iff the matching rule specifies a CE
> IPv6-prefix length)
> 4) If the PSID length is unknown, the "PSID complement" that completes th=
e
> Max PSID.
> 5) A 0 padding if fields 1 to 4 don't reach 64 bits
>
>
>
>

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

<div>hi Remi, </div><div>=A0</div><div class=3D"gmail_quote">2011/10/21 R=
=E9mi Despr=E9s <span dir=3D"ltr">&lt;<a href=3D"mailto:remi.despres@free.f=
r">remi.despres@free.fr</a>&gt;</span><br><blockquote style=3D"margin: 0px =
0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); bo=
rder-left-width: 1px; border-left-style: solid;" class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;">Maoke,<div>Please see below.</div><di=
v><br><div><div>Le 20 oct. 2011 =E0 16:48, Maoke a =E9crit :</div><div clas=
s=3D"im"><br><blockquote type=3D"cite"><div>hi Remi, </div><div>=A0</div><d=
iv>thanks a lot for the reply! it is very helpful and my latest understandi=
ng almost=A0approach it. but still some minor clarifications.<br>
</div><div class=3D"gmail_quote">2011/10/20 R=E9mi Despr=E9s <span dir=3D"l=
tr">&lt;<a href=3D"mailto:remi.despres@free.fr" target=3D"_blank">remi.desp=
res@free.fr</a>&gt;</span><br>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote"><div style=3D"word-wrap: break-word;"><div>Hi =
Maoke,</div>

<div><br></div><div>Thank you for your questions concerning relationships b=
etween IPv6 and IPv4 addressing plans.</div><div><br></div><div>Here are ad=
dress-planning steps that=A0illustrate how an IPv6 addressing plan can be k=
ept independent from IPv4 prefixes used for IPv4 residual deployment, even =
if CEs must be able to have different sharing ratios.</div>

<div>=A0</div><div><div>=A0 (A) IPv6 considerations</div><div>(A1) Determin=
e the maximum number N of CEs you want to support, a power of 2 (N =3D 2 ^ =
n).</div><div>(A2) Choose the length x of IPv6 prefixes you want to assign =
to ordinary customers (e.g. x =3D 60)</div>

<div>(A2) Multiply M by a margin coefficient K, a power of two (K =3D 2 ^ k=
), to take into account that:</div><div>=A0</div></div></div></blockquote><=
div>=A0</div><div>here the M should be=A0a typo of=A0&quot;N&quot;, right?=
=A0;-)=A0</div>
</div></blockquote><div><br></div></div>Yes, thanks.</div><div><div class=
=3D"im"><br><blockquote type=3D"cite"><div class=3D"gmail_quote">
<div>=A0</div><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left:=
 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border=
-left-style: solid;" class=3D"gmail_quote"><div style=3D"word-wrap: break-w=
ord;">

<div><div>=A0</div><div>=A0- Some privileged customers may be assigned IPv6=
 prefixes of length x&#39;, shorter than x, to have larger addressing space=
s than ordinary customers, both in IPv6 and IPv4. =A0</div><div>=A0- Due to=
 the hierarchy of routable prefixes, many theoretically delegatable prefixe=
s may not be actually delegatable (ref: host density ratio of RFC 3194).</d=
iv>

<div><br></div><div>=A0 (B) IPv4 considerations</div><div>(B1) List all (no=
n overlapping) IPv4 prefixes Hi that are available for IPv4 residual deploy=
ment.</div><div>(B2) Take enough of them, among the shortest ones, to get a=
 total space whose size M is a power of two (M =3D 2 ^ m), and includes a g=
ood proportion of the available IPv4 space (ref <a href=3D"http://www.ietf.=
org/mail-archive/web/softwires/current/msg02261.html" target=3D"_blank">www=
.ietf.org/mail-archive/web/softwires/current/msg02261.html</a>).</div>

<div>(B3)=A0For each IPv4 prefix Hi of length hi, choose a &quot;Rule index=
&quot; Ri of length ri =3D m - hi. All these indexes must be non overlappin=
g prefixes (e.g. 0, 10, 110, 111 for one /10, one /11, and two /12).</div>
</div></div></blockquote></div></blockquote><div><br></div></div>Oops, anot=
her bug :-(.</div><div>The right formula for ri is: =A0ri =3D m - (32 - hi)=
=A0</div><div><div class=3D"im"><br><blockquote type=3D"cite"><div class=3D=
"gmail_quote">
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-l=
eft-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: s=
olid;" class=3D"gmail_quote"><div style=3D"word-wrap: break-word;"><div><di=
v>

<br></div><div>=A0 (C) After (A) and (B)</div><div>(C1) Derive the length c=
 of the &quot;Common prefix&quot; C that will appear at the beginning of al=
l delegatable prefixes (c =3D n + k - m)</div><div>=A0</div></div></div></b=
lockquote>
</div></blockquote></div></div></div></div></blockquote><div>=A0</div><div>=
=A0is this another bug? i think: </div><div>=A0</div><div><font face=3D"cou=
rier new,monospace">|&lt;------------=A0=A0=A0=A0=A0=A0=A0 x=A0=A0=A0=A0=A0=
=A0 ----------------&gt;|</font></div>
<div><font face=3D"Courier New">|=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0|&lt;-=
--------=A0=A0 n=A0=A0 -----------&gt;|&lt;k&gt;|</font></div><div><font fa=
ce=3D"courier new,monospace">+------------+---------+-------------+-----+--=
-+</font></div><div><font face=3D"Courier New">|Common Pref.|Rule idx | IPv=
4 suffix=A0|PSID=A0|=A0=A0 |</font></div>
<div><font face=3D"Courier New">+------------+---------+-------------+-----=
+---+</font></div><div><font face=3D"Courier New">|=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0|&lt;---------=A0=A0 m=A0 ------&gt;|</font></div><div><font fa=
ce=3D"Courier New">|&lt;--- c=A0----&gt;|&lt;-- ri -&gt;|&lt;---=A0hi ----&=
gt;|</font></div>
<div><font face=3D"Courier New"></font>=A0</div><div><font face=3D"Courier =
New">and thus c =3D x - (n + k), right? ;-)</font></div><div><font face=3D"=
Courier New"></font>=A0</div><div><font face=3D"Courier New">cheers,</font>=
</div><div>
<font face=3D"Courier New">maoke</font></div><blockquote style=3D"margin: 0=
px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204);=
 border-left-width: 1px; border-left-style: solid;" class=3D"gmail_quote"><=
div style=3D"word-wrap: break-word;">
<div><div><div class=3D"im"><blockquote type=3D"cite"><div class=3D"gmail_q=
uote"><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; bo=
rder-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-st=
yle: solid;" class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;"><div><div>=A0</div><div>(C2) Take for=
 C any prefix of length c that starts with a RIR-allocated IPv6 prefix</div=
>
<div>(C3) For each IPv4 prefix Hi, make a rule in which it is the IPv4 pref=
ix, and in which the=A0IPv6 prefix is the Common prefix C followed by the R=
ule index Ri.</div></div><div><br></div><div>I hope this can work on your f=
avorite example(s).</div>

<div>If not, please let me know.</div></div></blockquote><div>=A0</div><div=
>it seems you didn&#39;t mention the PSID part. my understanding is, after =
the above, when we have the, e.g., /60, the PSID is attached after the /60.=
 then the CE=A0delegated prefix=A0(including IPv4 address suffix and PSID) =
may have different lengths if the sharing ratio is variant for different sh=
ared IPv4 addresses. but the c + m (or n + k, or x (right?)) , including th=
e common prefix and the ipv4-address-related bits, is a constant for every =
CE-delegated network in the domain, right? </div>
</div></blockquote><div><br></div></div><div>The PSID is WITHIN the /60 (at=
 its end).</div><div><br></div><div>The IPv6 /64 prefix to be used to reach=
 a CE contains:</div><div>1) The Rule IPv6 prefix (that of the rule whose I=
Pv4 prefix matches the IPv4 destination)</div>
<div>2) The IPv4 suffix (that part of the IPv4 destination that follows the=
 IPv4 prefix of the matching rule)=A0</div><div>3) The PSID (whose length i=
s known iff=A0the matching rule=A0specifies a CE IPv6-prefix length)=A0</di=
v><div>
4) If the PSID length is unknown, the &quot;PSID complement&quot; that comp=
letes the Max PSID. =A0=A0</div><div>5) A 0 padding if fields 1 to 4 don&#3=
9;t reach 64 bits</div><div><br><br>=A0</div></div></div></div></blockquote=
></div>

--0016e65aeeaa693f4f04aff9c1fc--

From fibrib@gmail.com  Sun Oct 23 09:39:25 2011
Return-Path: <fibrib@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 ACCFA21F87D9 for <softwires@ietfa.amsl.com>; Sun, 23 Oct 2011 09:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.94
X-Spam-Level: 
X-Spam-Status: No, score=-2.94 tagged_above=-999 required=5 tests=[AWL=0.358,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2BAdn8t9DZhp for <softwires@ietfa.amsl.com>; Sun, 23 Oct 2011 09:39:24 -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 9281021F8669 for <softwires@ietf.org>; Sun, 23 Oct 2011 09:39:24 -0700 (PDT)
Received: by wyh22 with SMTP id 22so6084307wyh.31 for <softwires@ietf.org>; Sun, 23 Oct 2011 09:39:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=331Gg5CGPQy0WXjpFk86mOglo37zfiqH1j4r9edIukc=; b=wcWLKOC/cCMf75Dc5zSkdfxavmMXPCY+bbWiqZjHuDT0YYVqc9mSJ9iThjDMPF8zQY MRuLiSBOXVQg+wJpdHdNb4Al2YKbOjrEJgxSDyWDyMN2XuEX9L8FoyBK+wEYYmjEedt7 Lw22TNKPU+hSBRuBpnze0epBIXyByOfozlc9o=
MIME-Version: 1.0
Received: by 10.216.90.4 with SMTP id d4mr3987070wef.22.1319387963614; Sun, 23 Oct 2011 09:39:23 -0700 (PDT)
Received: by 10.216.188.204 with HTTP; Sun, 23 Oct 2011 09:39:23 -0700 (PDT)
In-Reply-To: <CAFUBMqW13cMFSzNYR3yudQJE4q5tv78akT1ikzoBvVRYabdnVA@mail.gmail.com>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com> <817DF09F-2196-4A61-BC4C-5A7EE56EEFD1@free.fr> <CAFUBMqW13cMFSzNYR3yudQJE4q5tv78akT1ikzoBvVRYabdnVA@mail.gmail.com>
Date: Mon, 24 Oct 2011 01:39:23 +0900
Message-ID: <CAFUBMqUR=iG1gPb15_7i2xXH5fg=SuKM=NNDzyr1z0pHnSvLiw@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: multipart/alternative; boundary=0016e6d64815e467ad04aff9f26c
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 23 Oct 2011 16:39:25 -0000

--0016e6d64815e467ad04aff9f26c
Content-Type: text/plain; charset=ISO-8859-1

sorry, bug-fix on bug-fix. :P it should be (32 - hi) rather than hi in the
pic. - M.

2011/10/24 Maoke fibrib@gmail.com

>   (C) After (A) and (B)
>
>> (C1) Derive the length c of the "Common prefix" C that will appear at the
>>> beginning of all delegatable prefixes (c = n + k - m)
>>>
>>>
>>
>  is this another bug? i think:
>
> |<------------        x       ---------------->|
> |            |<---------   n   ----------->|<k>|
> +------------+---------+-------------+-----+---+
> |Common Pref.|Rule idx | IPv4 suffix |PSID |   |
> +------------+---------+-------------+-----+---+
> |            |<---------   m  ------>|
> |<--- c ---->|<-- ri ->|<- (32-hi) ->|
>
>

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

sorry, bug-fix on bug-fix. :P it should be (32 - hi) rather than hi in the =
pic. - M. <br><br><div class=3D"gmail_quote">2011/10/24 Maoke <span dir=3D"=
ltr"><a href=3D"mailto:fibrib@gmail.com">fibrib@gmail.com</a></span><br><bl=
ockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left=
-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: soli=
d;" class=3D"gmail_quote">
<div>=A0 (C) After (A) and (B)</div><div class=3D"gmail_quote"><div><div cl=
ass=3D"h5"><blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1e=
x; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-le=
ft-style: solid;" class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;"><div><div><div><blockquote type=3D"ci=
te"><div class=3D"gmail_quote"><blockquote style=3D"margin: 0px 0px 0px 0.8=
ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-w=
idth: 1px; border-left-style: solid;" class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;"><div><div>(C1) Derive the length c of=
 the &quot;Common prefix&quot; C that will appear at the beginning of all d=
elegatable prefixes (c =3D n + k - m)</div><div>=A0</div></div></div></bloc=
kquote>

</div></blockquote></div></div></div></div></blockquote><div>=A0</div></div=
></div><div>=A0is this another bug? i think: </div><div>=A0</div><div><font=
 face=3D"courier new,monospace">|&lt;------------=A0=A0=A0=A0=A0=A0=A0 x=A0=
=A0=A0=A0=A0=A0 ----------------&gt;|</font></div>

<div><font face=3D"Courier New">|=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0|&lt;-=
--------=A0=A0 n=A0=A0 -----------&gt;|&lt;k&gt;|</font></div><div><font fa=
ce=3D"courier new,monospace">+------------+---------+-------------+-----+--=
-+</font></div><div><font face=3D"Courier New">|Common Pref.|Rule idx | IPv=
4 suffix=A0|PSID=A0|=A0=A0 |</font></div>

<div><font face=3D"Courier New">+------------+---------+-------------+-----=
+---+</font></div><div><font face=3D"Courier New">|=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0|&lt;---------=A0=A0 m=A0 ------&gt;|</font></div><div><font fa=
ce=3D"Courier New">|&lt;--- c=A0----&gt;|&lt;-- ri -&gt;|&lt;-=A0(32-hi) -&=
gt;|</font></div>

<div><font face=3D"Courier New"></font>=A0</div></div></blockquote></div><b=
r>

--0016e6d64815e467ad04aff9f26c--

From despres.remi@laposte.net  Sun Oct 23 10:22:49 2011
Return-Path: <despres.remi@laposte.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 7026521F8A69 for <softwires@ietfa.amsl.com>; Sun, 23 Oct 2011 10:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.124
X-Spam-Level: 
X-Spam-Status: No, score=-2.124 tagged_above=-999 required=5 tests=[AWL=-0.176, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H9lAvZHLpxiB for <softwires@ietfa.amsl.com>; Sun, 23 Oct 2011 10:22:43 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.4]) by ietfa.amsl.com (Postfix) with ESMTP id 37B4C21F8AE9 for <softwires@ietf.org>; Sun, 23 Oct 2011 10:22:43 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2117.sfr.fr (SMTP Server) with ESMTP id 8F9F37000118; Sun, 23 Oct 2011 19:22:42 +0200 (CEST)
Received: from [192.168.1.73] (17.204.170.89.rev.sfr.net [89.170.204.17]) by msfrf2117.sfr.fr (SMTP Server) with ESMTP id 3675B7000112; Sun, 23 Oct 2011 19:22:42 +0200 (CEST)
X-SFR-UUID: 20111023172242223.3675B7000112@msfrf2117.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-11--366537981
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAFUBMqW13cMFSzNYR3yudQJE4q5tv78akT1ikzoBvVRYabdnVA@mail.gmail.com>
Date: Sun, 23 Oct 2011 19:22:41 +0200
Message-Id: <DF426613-2232-40E2-860F-157D404FCC42@laposte.net>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net> <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com> <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com> <4E9B9BC5.2090200@jacni.com> <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com> <4E9BE001.3060202@jacni.com> <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local> <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com> <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr> <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com> <817DF09F-2196-4A61-BC4C-5A7EE56EEFD1@free.fr> <CAFUBMqW13cMFSzNYR3yudQJE4q5tv78akT1ikzoBvVRYabdnVA@mail.gmail.com>
To: Maoke <fibrib@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-addmapping - Possible independence of the IPv6 addressing plan from IPv4 prefixes
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, 23 Oct 2011 17:22:49 -0000

--Apple-Mail-11--366537981
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 23 oct. 2011 =E0 18:25, Maoke a =E9crit :

> hi Remi,
> =20
> 2011/10/21 R=E9mi Despr=E9s <remi.despres@free.fr>
> Maoke,
> Please see below.
>=20
> Le 20 oct. 2011 =E0 16:48, Maoke a =E9crit :
>=20
>> hi Remi,
>> =20
>> thanks a lot for the reply! it is very helpful and my latest =
understanding almost approach it. but still some minor clarifications.
>> 2011/10/20 R=E9mi Despr=E9s <remi.despres@free.fr>
>> Hi Maoke,
>>=20
>> Thank you for your questions concerning relationships between IPv6 =
and IPv4 addressing plans.
>>=20
>> Here are address-planning steps that illustrate how an IPv6 =
addressing plan can be kept independent from IPv4 prefixes used for IPv4 =
residual deployment, even if CEs must be able to have different sharing =
ratios.
>> =20
>>   (A) IPv6 considerations
>> (A1) Determine the maximum number N of CEs you want to support, a =
power of 2 (N =3D 2 ^ n).
>> (A2) Choose the length x of IPv6 prefixes you want to assign to =
ordinary customers (e.g. x =3D 60)
>> (A2) Multiply M by a margin coefficient K, a power of two (K =3D 2 ^ =
k), to take into account that:
>> =20
>> =20
>> here the M should be a typo of "N", right? ;-)=20
>=20
> Yes, thanks.
>=20
>> =20
>> =20
>>  - Some privileged customers may be assigned IPv6 prefixes of length =
x', shorter than x, to have larger addressing spaces than ordinary =
customers, both in IPv6 and IPv4. =20
>>  - Due to the hierarchy of routable prefixes, many theoretically =
delegatable prefixes may not be actually delegatable (ref: host density =
ratio of RFC 3194).
>>=20
>>   (B) IPv4 considerations
>> (B1) List all (non overlapping) IPv4 prefixes Hi that are available =
for IPv4 residual deployment.
>> (B2) Take enough of them, among the shortest ones, to get a total =
space whose size M is a power of two (M =3D 2 ^ m), and includes a good =
proportion of the available IPv4 space (ref =
www.ietf.org/mail-archive/web/softwires/current/msg02261.html).
>> (B3) For each IPv4 prefix Hi of length hi, choose a "Rule index" Ri =
of length ri =3D m - hi. All these indexes must be non overlapping =
prefixes (e.g. 0, 10, 110, 111 for one /10, one /11, and two /12).
>=20
> Oops, another bug :-(.
> The right formula for ri is:  ri =3D m - (32 - hi)=20
>=20
>>=20
>>   (C) After (A) and (B)
>> (C1) Derive the length c of the "Common prefix" C that will appear at =
the beginning of all delegatable prefixes (c =3D n + k - m)
>> =20
>=20
> =20
>  is this another bug? i think:

> =20
> |<------------        x       ---------------->|
> |            |<---------   n   ----------->|<k>|
> +------------+---------+-------------+-----+---+
> |Common Pref.|Rule idx | IPv4 suffix |PSID |   |
> +------------+---------+-------------+-----+---+
> |            |<---------   m  ------>|
> |<--- c ---->|<-- ri ->|<--- hi ---->|=20

Correct (with the correction made in your next mail: hi replaced by 32 - =
hi)

> and thus c =3D x - (n + k), right? ;-)

Indeed.
Thanks fot the careful review.

Cheers,
RD


--Apple-Mail-11--366537981
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 23 oct. 2011 =E0 18:25, Maoke a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>hi =
Remi, </div><div>&nbsp;</div><div class=3D"gmail_quote">2011/10/21 R=E9mi =
Despr=E9s <span dir=3D"ltr">&lt;<a =
href=3D"mailto:remi.despres@free.fr">remi.despres@free.fr</a>&gt;</span><b=
r><blockquote style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0.8ex; padding-left: 1ex; =
border-left-color: rgb(204, 204, 204); border-left-width: 1px; =
border-left-style: solid; position: static; z-index: auto; " =
class=3D"gmail_quote">
<div style=3D"word-wrap: break-word;">Maoke,<div>Please see =
below.</div><div><br><div><div>Le 20 oct. 2011 =E0 16:48, Maoke a =E9crit =
:</div><div class=3D"im"><br><blockquote type=3D"cite"><div>hi Remi, =
</div><div>&nbsp;</div><div>thanks a lot for the reply! it is very =
helpful and my latest understanding almost&nbsp;approach it. but still =
some minor clarifications.<br>
</div><div class=3D"gmail_quote">2011/10/20 R=E9mi Despr=E9s <span =
dir=3D"ltr">&lt;<a href=3D"mailto:remi.despres@free.fr" =
target=3D"_blank">remi.despres@free.fr</a>&gt;</span><br>
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; =
border-left-color: rgb(204, 204, 204); border-left-width: 1px; =
border-left-style: solid;" class=3D"gmail_quote"><div style=3D"word-wrap: =
break-word;"><div>Hi Maoke,</div>

<div><br></div><div>Thank you for your questions concerning =
relationships between IPv6 and IPv4 addressing =
plans.</div><div><br></div><div>Here are address-planning steps =
that&nbsp;illustrate how an IPv6 addressing plan can be kept independent =
from IPv4 prefixes used for IPv4 residual deployment, even if CEs must =
be able to have different sharing ratios.</div>

<div>&nbsp;</div><div><div>&nbsp; (A) IPv6 considerations</div><div>(A1) =
Determine the maximum number N of CEs you want to support, a power of 2 =
(N =3D 2 ^ n).</div><div>(A2) Choose the length x of IPv6 prefixes you =
want to assign to ordinary customers (e.g. x =3D 60)</div>

<div>(A2) Multiply M by a margin coefficient K, a power of two (K =3D 2 =
^ k), to take into account =
that:</div><div>&nbsp;</div></div></div></blockquote><div>&nbsp;</div><div=
>here the M should be&nbsp;a typo of&nbsp;"N", =
right?&nbsp;;-)&nbsp;</div>
</div></blockquote><div><br></div></div>Yes, thanks.</div><div><div =
class=3D"im"><br><blockquote type=3D"cite"><div class=3D"gmail_quote">
<div>&nbsp;</div><blockquote style=3D"margin: 0px 0px 0px 0.8ex; =
padding-left: 1ex; border-left-color: rgb(204, 204, 204); =
border-left-width: 1px; border-left-style: solid;" =
class=3D"gmail_quote"><div style=3D"word-wrap: break-word;">

<div><div>&nbsp;</div><div>&nbsp;- Some privileged customers may be =
assigned IPv6 prefixes of length x', shorter than x, to have larger =
addressing spaces than ordinary customers, both in IPv6 and IPv4. =
&nbsp;</div><div>&nbsp;- Due to the hierarchy of routable prefixes, many =
theoretically delegatable prefixes may not be actually delegatable (ref: =
host density ratio of RFC 3194).</div>

<div><br></div><div>&nbsp; (B) IPv4 considerations</div><div>(B1) List =
all (non overlapping) IPv4 prefixes Hi that are available for IPv4 =
residual deployment.</div><div>(B2) Take enough of them, among the =
shortest ones, to get a total space whose size M is a power of two (M =3D =
2 ^ m), and includes a good proportion of the available IPv4 space (ref =
<a =
href=3D"http://www.ietf.org/mail-archive/web/softwires/current/msg02261.ht=
ml" =
target=3D"_blank">www.ietf.org/mail-archive/web/softwires/current/msg02261=
.html</a>).</div>

<div>(B3)&nbsp;For each IPv4 prefix Hi of length hi, choose a "Rule =
index" Ri of length ri =3D m - hi. All these indexes must be non =
overlapping prefixes (e.g. 0, 10, 110, 111 for one /10, one /11, and two =
/12).</div>
</div></div></blockquote></div></blockquote><div><br></div></div>Oops, =
another bug :-(.</div><div>The right formula for ri is: &nbsp;ri =3D m - =
(32 - hi)&nbsp;</div><div><div class=3D"im"><br><blockquote =
type=3D"cite"><div class=3D"gmail_quote">
<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1ex; =
border-left-color: rgb(204, 204, 204); border-left-width: 1px; =
border-left-style: solid;" class=3D"gmail_quote"><div style=3D"word-wrap: =
break-word;"><div><div>

<br></div><div>&nbsp; (C) After (A) and (B)</div><div>(C1) Derive the =
length c of the "Common prefix" C that will appear at the beginning of =
all delegatable prefixes (c =3D n + k - =
m)</div><div>&nbsp;</div></div></div></blockquote>
=
</div></blockquote></div></div></div></div></blockquote><div>&nbsp;</div><=
div>&nbsp;is this another bug? i think: =
</div></div></blockquote><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>&nbsp;</div><div><font face=3D"courier =
new,monospace">|&lt;------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 x&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
----------------&gt;|</font></div>
<div><font face=3D"Courier =
New">|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;|&lt;---------&nbsp;&nbsp; n&nbsp;&nbsp; =
-----------&gt;|&lt;k&gt;|</font></div><div><font face=3D"courier =
new,monospace">+------------+---------+-------------+-----+---+</font></di=
v><div><font face=3D"Courier New">|Common Pref.|Rule idx | IPv4 =
suffix&nbsp;|PSID&nbsp;|&nbsp;&nbsp; |</font></div>
<div><font face=3D"Courier =
New">+------------+---------+-------------+-----+---+</font></div><div><fo=
nt face=3D"Courier =
New">|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;|&lt;---------&nbsp;&nbsp; m&nbsp; =
------&gt;|</font></div><div><font face=3D"Courier New">|&lt;--- =
c&nbsp;----&gt;|&lt;-- ri -&gt;|&lt;---&nbsp;hi =
----&gt;|</font>&nbsp;</div></div></blockquote><div><br></div><div>Correct=
 (with the correction made in your next mail: hi replaced by 32 - =
hi)</div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div><font face=3D"Courier New">and thus c =3D x - =
(n + k), right? =
;-)</font></div></div></blockquote><div><br></div><div>Indeed.</div><div>T=
hanks fot the careful =
review.</div><div><br></div><div>Cheers,</div><div>RD</div></div><br></bod=
y></html>=

--Apple-Mail-11--366537981--

From jiangdong345@gmail.com  Tue Oct 25 00:44:45 2011
Return-Path: <jiangdong345@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 1E05921F8BBD for <softwires@ietfa.amsl.com>; Tue, 25 Oct 2011 00:44:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XB+M7yeVgxjb for <softwires@ietfa.amsl.com>; Tue, 25 Oct 2011 00:44:44 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2D66321F8BB9 for <softwires@ietf.org>; Tue, 25 Oct 2011 00:44:44 -0700 (PDT)
Received: by iabn5 with SMTP id n5so346981iab.31 for <softwires@ietf.org>; Tue, 25 Oct 2011 00:44:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:cc:references:subject:message-id:x-mailer:mime-version :content-type:content-transfer-encoding; bh=PB4E9Sgyw4z530QOv52IKxP1KJr1Xrg70+vBh/E9pY0=; b=agBfDvIkYCxGHRFymwul1l8hLVZZ4BrJ2UGPV1Mn7ppG4+3OIU8Sx3B1KAXb4T24c6 FAosfX751laiXLFySXVZKUVih/WBQcZFel4MlI6+aszO5TVBGKR4dv/pOTBl4oleXsao cUnNAAEdc60Hkf1fVIUbgA/w3aUVh1/OOFgSo=
Received: by 10.231.82.2 with SMTP id z2mr2191ibk.67.1319528681291; Tue, 25 Oct 2011 00:44:41 -0700 (PDT)
Received: from DJ-PC ([166.111.68.231]) by mx.google.com with ESMTPS id n30sm1484ibl.4.2011.10.25.00.44.38 (version=SSLv3 cipher=OTHER); Tue, 25 Oct 2011 00:44:39 -0700 (PDT)
Date: Tue, 25 Oct 2011 15:45:20 +0800
From: Jiang Dong <jiangdong345@gmail.com>
To: "Softwires WG" <softwires@ietf.org>
References: <D8334AA7-5001-4A92-B977-CE32931F4197@laposte.net>, <CAAuHL_Cm6WYiM2Cu-fmu=gBLgTYDZ6hr56BfcXMoeS=Af4Q_jw@mail.gmail.com>, <CAFUBMqUvrP-s1yrJ0=ToAA_SvRLWQtq7JCTtpASNiS1GAxdSNQ@mail.gmail.com>, <4E9B9BC5.2090200@jacni.com>, <CAFUBMqUS1cATWr07Os4d6aLUbNaVwuOCcthObOiMPuDv8VfU1g@mail.gmail.com>, <4E9BE001.3060202@jacni.com>, <6CADC58598A4D249AD3B5026CE8CC33906D75AC8@CI-EXMB-09V.bb.local>, <CAFUBMqW7xqxwzToxn1=0y4q48Dr5U8rx3pDoavcWGhPyO-OLpw@mail.gmail.com>, <927947AB-FD61-4CCA-8E42-2DEC1854F2EA@free.fr>, <CAFUBMqX9rrmTpksw7R4_59=rN0qDVkA_6y5B5cBP_7zgaRt=rQ@mail.gmail.com>, <817DF09F-2196-4A61-BC4C-5A7EE56EEFD1@free.fr>, <CAFUBMqW13cMFSzNYR3yudQJE4q5tv78akT1ikzoBvVRYabdnVA@mail.gmail.com>
Message-ID: <201110251545163879196@gmail.com>
X-mailer: Foxmail 6, 15, 201, 22 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Softwires]  requesting comments about the Softwire mesh 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: Tue, 25 Oct 2011 07:44:45 -0000

Hi,Softwirers,

	Since the Softwire Mesh MIB is also on the milestones, I think we need to do something to improve the progress about it.
	
	Following is the link about the mesh MIB draft: http://tools.ietf.org/html/draft-cui-softwire-mesh-mib-02. This version intrduces the relationship between If MIB and IP Tunnel MIB. Since there's no encapsulation message in the IP tunnel MIB, we add an encapsulation table in the softwire mesh MIB.	

	We really appreciate for any valuable comments about this draft. Thank you very much!


From despres.remi@laposte.net  Tue Oct 25 01:24:25 2011
Return-Path: <despres.remi@laposte.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 9B2BD21F8B58 for <softwires@ietfa.amsl.com>; Tue, 25 Oct 2011 01:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nBidiMWM0mNI for <softwires@ietfa.amsl.com>; Tue, 25 Oct 2011 01:24:25 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id B839621F8B1E for <softwires@ietf.org>; Tue, 25 Oct 2011 01:24:22 -0700 (PDT)
Received: from [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb] (unknown [IPv6:2a01:e35:8a6d:d900:129a:ddff:fe6b:c6fb]) by smtp1-g21.free.fr (Postfix) with ESMTP id 1453E9401F7; Tue, 25 Oct 2011 10:24:16 +0200 (CEST)
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2011 10:24:15 +0200
To: Softwires WG <softwires@ietf.org>
Message-Id: <24AD4080-71AF-4BC5-9E8F-9C7B48443472@laposte.net>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [Softwires] 4rd-U version -01 to unify Double translation and encapsulation.
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, 25 Oct 2011 08:24:25 -0000

Hi all,

Version -01 of the 4rd-U "header mapping" has been posted a few hours =
ago.
Ref: www.ietf.org/id/draft-despres-softwire-4rd-u-01.txt

It proposes a unified solution to replace Double translation and =
Encapsulation, so that a single standard can be possible for stateless =
residual deployments of IPv4 across IPv6 networks.=20

Because it has an impact on the IPv4 to IPv6 address mapping (it =
requires checksum neutrality), it is an input not only to the Softwire =
WG in general, but also to the currently active address mapping design =
team.=20

Many details could be added, but the solution is expected to be =
understandable.
(There is in particular nothing on ICMP, but usual logic on the subject =
should apply unchanged.)

All questions are most welcome.

Regards,
RD=

From internet-drafts@ietf.org  Tue Oct 25 20:51:11 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 3CB2A21F8BB1; Tue, 25 Oct 2011 20:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kZFcXgnfY9ri; Tue, 25 Oct 2011 20:51:10 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6A5821F84CD; Tue, 25 Oct 2011 20:51:10 -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.61
Message-ID: <20111026035110.16480.10763.idtracker@ietfa.amsl.com>
Date: Tue, 25 Oct 2011 20:51:10 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-6rd-radius-attrib-04.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: Wed, 26 Oct 2011 03:51:11 -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           : RADIUS Attribute for 6rd
	Author(s)       : Dayong Guo
                          Sheng Jiang
                          Remi Despres
                          Roberta Maglione
	Filename        : draft-ietf-softwire-6rd-radius-attrib-04.txt
	Pages           : 10
	Date            : 2011-10-25

   IPv6 Rapid Deployment (6rd) is one of the most popular methods to
   provide both IPv4 and IPv6 connectivity services simultaneously
   during the IPv4/IPv6 co-existing period. The Dynamic Host
   Configuration Protocol (DHCP) 6rd option has been defined to
   configure 6rd Customer Edge (CE). However, in many networks, the
   configuration information may be stored in Authentication
   Authorization and Accounting (AAA) servers while user configuration
   is mainly from Broadband Network Gateway (BNG) through DHC protocol.
   This document defines a Remote Authentication Dial In User Service
   (RADIUS) attribute that carries 6rd configuration information from
   AAA server to BNG.




A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-6rd-radius-attrib-0=
4.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-6rd-radius-attrib-04=
.txt

From bingxuere@gmail.com  Tue Oct 25 20:57:17 2011
Return-Path: <bingxuere@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 15EC321F8BE9 for <softwires@ietfa.amsl.com>; Tue, 25 Oct 2011 20:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.89
X-Spam-Level: 
X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[AWL=0.708,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzFE4JpHFniq for <softwires@ietfa.amsl.com>; Tue, 25 Oct 2011 20:57:16 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 783B521F8BD5 for <softwires@ietf.org>; Tue, 25 Oct 2011 20:57:13 -0700 (PDT)
Received: by iabn5 with SMTP id n5so1642161iab.31 for <softwires@ietf.org>; Tue, 25 Oct 2011 20:57:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=bs+RiF3vz3o0JKbOu8/fuVRUIZw7rhvHxdn2B/7v5H4=; b=ZcxR3HELz/OPeYUchaJA7TwMgHG43fb8p5P9YM1WhNhEV9gY5kxTFEggY3i9+p/Ts8 FkVRFHmBSSd4r3Aj0K4DzXtoTl9XFxI1Y7UV6uajxSaKvLfBw5W6NXQ58dV6SB//MtHT vAmgoB5gvdN3EuZHU+BNTxyEBNL6KrVCwaM94=
Received: by 10.42.161.70 with SMTP id s6mr48585537icx.40.1319601433103; Tue, 25 Oct 2011 20:57:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Tue, 25 Oct 2011 20:56:33 -0700 (PDT)
From: Qiong <bingxuere@gmail.com>
Date: Wed, 26 Oct 2011 11:56:33 +0800
Message-ID: <CAH3bfAB9XLrnM+8doHQ5n1SJ_DVxtKQVZ3Nicm4O3Q8Ok3Xueg@mail.gmail.com>
To: softwires@ietf.org
Content-Type: multipart/alternative; boundary=90e6ba2123e5aa4eee04b02ba65f
Subject: [Softwires] requesting comments about the "b4-translated-ds-lite"
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, 26 Oct 2011 03:57:17 -0000

--90e6ba2123e5aa4eee04b02ba65f
Content-Type: text/plain; charset=UTF-8

Dear all,

The following is our latest progress on our "bt-translated-ds-lite". It
moves the translation function from tunnel concentrator (AFTR) to initiators
(B4s), and hence reduce the mapping scale on the concentrator to
per-customer level. We have implemented a prototype and deployed it in Hunan
province.

A URL for this Internet-Draft is:
http://www.ietf.org/id/draft-cui-softwire-b4-translated-ds-lite-03.txt

Your comments are more than welcome.

Best wishes

Qiong



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

                  Lightweight 4over6 in access network
              draft-cui-softwire-b4-translated-ds-lite-03

Abstract

   The dual-stack lite mechanism provide an IPv4 access method over IPv6
   ISP network for end users.  Dual-Stack Lite enables an IPv6 provider
   to share IPv4 addresses among customers by combining IPv4-in-IPv6
   tunnel and Carrier Grade NAT.  However, in dual-stack lite, CGN has
   to maintain active NAT sessions, which could become the performance
   bottom-neck due to high dynamic s of NAT entries, memory cost and log
   issue.  This document propose the lightweight 4over6 mechanism which
   moves the translation function from tunnel concentrator (AFTR) to
   initiators (B4s), and hence reduce the mapping scale on the
   concentrator to per-customer level.  For NAT44 translation usage, the
   mechanism will allocate port restricted IPv4 addresses to initiators
   in a flexible way independent of IPv6 network in the middle.

--90e6ba2123e5aa4eee04b02ba65f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Dear all,<div><br></div><div>The following is our latest progress on our &q=
uot;bt-translated-ds-lite&quot;. It moves the translation function from tun=
nel concentrator (AFTR) to=C2=A0initiators (B4s), and hence reduce the mapp=
ing scale on the=C2=A0concentrator to per-customer level. We have implement=
ed a=C2=A0prototype and deployed it in Hunan province.=C2=A0</div>

<div><br></div><div><span class=3D"Apple-style-span" style=3D"font-family: =
arial, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255); "=
>A URL for this Internet-Draft is:</span></div><div><span class=3D"Apple-st=
yle-span" style=3D"font-family: arial, sans-serif; font-size: 13px; backgro=
und-color: rgb(255, 255, 255); "><a href=3D"http://www.ietf.org/id/draft-cu=
i-softwire-b4-translated-ds-lite-03.txt">http://www.ietf.org/id/draft-cui-s=
oftwire-b4-translated-ds-lite-03.txt</a></span></div>

<div><span class=3D"Apple-style-span" style=3D"font-family: arial, sans-ser=
if; font-size: 13px; background-color: rgb(255, 255, 255); "><br></span></d=
iv><div>Your comments are more than welcome. =C2=A0=C2=A0</div><div><br><di=
v>Best wishes</div>

<div><br></div><div>Qiong</div><div><br></div><div><br></div><div><br></div=
><div>---------------------------------------------------------------------=
------------------------------------------------------------------</div>

<div><br></div><div><span class=3D"Apple-style-span" style=3D"font-family: =
Simsun; font-size: medium; "><pre style=3D"word-wrap: break-word; white-spa=
ce: pre-wrap; ">                  Lightweight 4over6 in access network
              draft-cui-softwire-b4-translated-ds-lite-03

Abstract

   The dual-stack lite mechanism provide an IPv4 access method over IPv6
   ISP network for end users.  Dual-Stack Lite enables an IPv6 provider
   to share IPv4 addresses among customers by combining IPv4-in-IPv6
   tunnel and Carrier Grade NAT.  However, in dual-stack lite, CGN has
   to maintain active NAT sessions, which could become the performance
   bottom-neck due to high dynamic s of NAT entries, memory cost and log
   issue.  This document propose the lightweight 4over6 mechanism which
   moves the translation function from tunnel concentrator (AFTR) to
   initiators (B4s), and hence reduce the mapping scale on the
   concentrator to per-customer level.  For NAT44 translation usage, the
   mechanism will allocate port restricted IPv4 addresses to initiators
   in a flexible way independent of IPv6 network in the middle.</pre></span=
></div></div>

--90e6ba2123e5aa4eee04b02ba65f--

From ichiroumakino@gmail.com  Tue Oct 25 23:40:41 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 7470721F858D for <softwires@ietfa.amsl.com>; Tue, 25 Oct 2011 23:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.494
X-Spam-Level: 
X-Spam-Status: No, score=-3.494 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCAHxCfDHCkf for <softwires@ietfa.amsl.com>; Tue, 25 Oct 2011 23:40:41 -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 68A5721F8558 for <softwires@ietf.org>; Tue, 25 Oct 2011 23:40:33 -0700 (PDT)
Received: by wyh22 with SMTP id 22so1525920wyh.31 for <softwires@ietf.org>; Tue, 25 Oct 2011 23:40:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=Untak/U5MxpGYJqgTTbD5bVlb6XcBY5nnk22fuvCxko=; b=gMEGkZ5LobHt8GE54q4X7XzaiWSGssuupPcUGKB8XDLGl9AHAYuU8xLiDbZCHLbqho ATKaNuqr1lrnfUr6OkMYluurJDYFutTX/jUvknF5lZPWsLlRltQpbFEPQo3Rp4DxSupv Or2zSq5SSvPHBPNRVZjHLjRjwWYhbvlP07ehM=
Received: by 10.227.198.77 with SMTP id en13mr7762805wbb.28.1319611232527; Tue, 25 Oct 2011 23:40:32 -0700 (PDT)
Received: from dhcp-10-61-102-64.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id gg13sm1230831wbb.8.2011.10.25.23.40.28 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Oct 2011 23:40:30 -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: <CAH3bfAB9XLrnM+8doHQ5n1SJ_DVxtKQVZ3Nicm4O3Q8Ok3Xueg@mail.gmail.com>
Date: Wed, 26 Oct 2011 08:40:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A16505C2-1F6E-4FBA-B2F2-06606AB70062@employees.org>
References: <CAH3bfAB9XLrnM+8doHQ5n1SJ_DVxtKQVZ3Nicm4O3Q8Ok3Xueg@mail.gmail.com>
To: Qiong <bingxuere@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: softwires@ietf.org
Subject: Re: [Softwires] requesting comments about the "b4-translated-ds-lite"
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, 26 Oct 2011 06:40:41 -0000

> The following is our latest progress on our "bt-translated-ds-lite". =
It moves the translation function from tunnel concentrator (AFTR) to =
initiators (B4s), and hence reduce the mapping scale on the concentrator =
to per-customer level. We have implemented a prototype and deployed it =
in Hunan province.=20
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/id/draft-cui-softwire-b4-translated-ds-lite-03.txt

I think this is a good idea in general and that it fits well with the =
other approaches we've been discussing in softwire for
IPv4 over IPv6 mechanisms. I'll read through again and provide detailed =
comments asap.

with regards to document organization, would it be possible to:
- merge host 4over6 (draft-cui-softwire-host-4over6-06) with lightweight =
4over6 (draft-cui-softwire-b4-translated-ds-lite-03)
- merge stateless 4over6 (draft-sun-softwire-stateless-4over6-00) with =
the MAP effort

then we'll have one 'stateless' version of A+P document and one =
'stateful' A+P aka DS-lite with A+P extensions.
both also handling the case of a full IPv4 address on the B4.

cheers,
Ole

> =
--------------------------------------------------------------------------=
-------------------------------------------------------------
>=20
>                   Lightweight 4over6 in access network
>               draft-cui-softwire-b4-translated-ds-lite-03
>=20
> Abstract
>=20
>    The dual-stack lite mechanism provide an IPv4 access method over =
IPv6
>    ISP network for end users.  Dual-Stack Lite enables an IPv6 =
provider
>    to share IPv4 addresses among customers by combining IPv4-in-IPv6
>    tunnel and Carrier Grade NAT.  However, in dual-stack lite, CGN has
>    to maintain active NAT sessions, which could become the performance
>    bottom-neck due to high dynamic s of NAT entries, memory cost and =
log
>    issue.  This document propose the lightweight 4over6 mechanism =
which
>    moves the translation function from tunnel concentrator (AFTR) to
>    initiators (B4s), and hence reduce the mapping scale on the
>    concentrator to per-customer level.  For NAT44 translation usage, =
the
>    mechanism will allocate port restricted IPv4 addresses to =
initiators
>    in a flexible way independent of IPv6 network in the middle.
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From bingxuere@gmail.com  Wed Oct 26 05:16:59 2011
Return-Path: <bingxuere@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 93A4F21F87C2 for <softwires@ietfa.amsl.com>; Wed, 26 Oct 2011 05:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.991
X-Spam-Level: 
X-Spam-Status: No, score=-2.991 tagged_above=-999 required=5 tests=[AWL=0.607,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ktq7T6emUJld for <softwires@ietfa.amsl.com>; Wed, 26 Oct 2011 05:16:58 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id A8B8E21F869E for <softwires@ietf.org>; Wed, 26 Oct 2011 05:16:47 -0700 (PDT)
Received: by iabn5 with SMTP id n5so2144746iab.31 for <softwires@ietf.org>; Wed, 26 Oct 2011 05:16:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Pd451e7aDjrqVp/UDcrx+BdoxSMNsX65MfMSXikgr6g=; b=slcaupsLtvKvrceOtjMAkOqNfdSUuDG8kUKJT8beWc7aj79XLrj4SlZqsblHBjPXgL zKYjerp1EKN3mjMUXX42dlXh2OWLihxpI+EQky949LZQ0zyjCfk8RJqtLJbKvbkayvUD XuHgraqizyHjZEBeISOgaBv9vDUw/c8UeE3y8=
Received: by 10.42.155.133 with SMTP id u5mr51549898icw.8.1319631407246; Wed, 26 Oct 2011 05:16:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.219.194 with HTTP; Wed, 26 Oct 2011 05:16:07 -0700 (PDT)
In-Reply-To: <A16505C2-1F6E-4FBA-B2F2-06606AB70062@employees.org>
References: <CAH3bfAB9XLrnM+8doHQ5n1SJ_DVxtKQVZ3Nicm4O3Q8Ok3Xueg@mail.gmail.com> <A16505C2-1F6E-4FBA-B2F2-06606AB70062@employees.org>
From: Qiong <bingxuere@gmail.com>
Date: Wed, 26 Oct 2011 20:16:07 +0800
Message-ID: <CAH3bfACqPqfVTwdzx8onXUxxdSpezHJuY_XTOutL6jh=VZeevg@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=90e6ba21241b436b5a04b032a15d
Cc: softwires@ietf.org
Subject: Re: [Softwires] requesting comments about the "b4-translated-ds-lite"
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, 26 Oct 2011 12:16:59 -0000

--90e6ba21241b436b5a04b032a15d
Content-Type: text/plain; charset=UTF-8

Hi Ole,

Thanks a lot for your comments. Please see inline :)

On Wed, Oct 26, 2011 at 2:40 PM, Ole Troan <otroan@employees.org> wrote:

> > The following is our latest progress on our "bt-translated-ds-lite". It
> moves the translation function from tunnel concentrator (AFTR) to initiators
> (B4s), and hence reduce the mapping scale on the concentrator to
> per-customer level. We have implemented a prototype and deployed it in Hunan
> province.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/id/draft-cui-softwire-b4-translated-ds-lite-03.txt
>
> I think this is a good idea in general and that it fits well with the other
> approaches we've been discussing in softwire for
> IPv4 over IPv6 mechanisms. I'll read through again and provide detailed
> comments asap.
>

Qiong: Thanks. We are looking forward to your detailed comments.

with regards to document organization, would it be possible to:
> - merge host 4over6 (draft-cui-softwire-host-4over6-06) with lightweight
> 4over6 (draft-cui-softwire-b4-translated-ds-lite-03)
>

Qiong: I personally think it is a very good suggestion. Both "host 4over6"
and "lightweight 4over6" share the common feature with stateful
per-user-encapsulation, and "lightweight 4over6" is also an address sharing
extension to "host 4over6". I think it would be reasonable to merge these
two documents if the authors of "host 4over6" do not object to it.


> - merge stateless 4over6 (draft-sun-softwire-stateless-4over6-00) with the
> MAP effort
>

Qiong: ok. I will merge it with MAP effort.

Best wishes

Qiong



> then we'll have one 'stateless' version of A+P document and one 'stateful'
> A+P aka DS-lite with A+P extensions.
> both also handling the case of a full IPv4 address on the B4.
>
> cheers,
> Ole
>
> >
> ---------------------------------------------------------------------------------------------------------------------------------------
> >
> >                   Lightweight 4over6 in access network
> >               draft-cui-softwire-b4-translated-ds-lite-03
> >
> > Abstract
> >
> >    The dual-stack lite mechanism provide an IPv4 access method over IPv6
> >    ISP network for end users.  Dual-Stack Lite enables an IPv6 provider
> >    to share IPv4 addresses among customers by combining IPv4-in-IPv6
> >    tunnel and Carrier Grade NAT.  However, in dual-stack lite, CGN has
> >    to maintain active NAT sessions, which could become the performance
> >    bottom-neck due to high dynamic s of NAT entries, memory cost and log
> >    issue.  This document propose the lightweight 4over6 mechanism which
> >    moves the translation function from tunnel concentrator (AFTR) to
> >    initiators (B4s), and hence reduce the mapping scale on the
> >    concentrator to per-customer level.  For NAT44 translation usage, the
> >    mechanism will allocate port restricted IPv4 addresses to initiators
> >    in a flexible way independent of IPv6 network in the middle.
> >
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires
>
>

--90e6ba21241b436b5a04b032a15d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Hi Ole,</div><div><br></div><div>Thanks a lot for your comments. Pleas=
e see inline :)<br><br><div class=3D"gmail_quote">On Wed, Oct 26, 2011 at 2=
:40 PM, Ole Troan <span dir=3D"ltr">&lt;<a href=3D"mailto:otroan@employees.=
org">otroan@employees.org</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;"><div class=3D"im">&gt; The following is our=
 latest progress on our &quot;bt-translated-ds-lite&quot;. It moves the tra=
nslation function from tunnel concentrator (AFTR) to initiators (B4s), and =
hence reduce the mapping scale on the concentrator to per-customer level. W=
e have implemented a prototype and deployed it in Hunan province.<br>


&gt;<br>
&gt; A URL for this Internet-Draft is:<br>
&gt; <a href=3D"http://www.ietf.org/id/draft-cui-softwire-b4-translated-ds-=
lite-03.txt" target=3D"_blank">http://www.ietf.org/id/draft-cui-softwire-b4=
-translated-ds-lite-03.txt</a><br>
<br>
</div>I think this is a good idea in general and that it fits well with the=
 other approaches we&#39;ve been discussing in softwire for<br>
IPv4 over IPv6 mechanisms. I&#39;ll read through again and provide detailed=
 comments asap.<br></blockquote><div><br></div><div>Qiong: Thanks. We are l=
ooking forward to your detailed comments.=C2=A0</div><div><br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">


with regards to document organization, would it be possible to:<br>
- merge host 4over6 (draft-cui-softwire-host-4over6-06) with lightweight 4o=
ver6 (draft-cui-softwire-b4-translated-ds-lite-03)<br></blockquote><div><br=
></div><div>Qiong: I personally think it is a very good suggestion. Both &q=
uot;host 4over6&quot; and &quot;lightweight 4over6&quot; share the common f=
eature with stateful per-user-encapsulation, and &quot;lightweight 4over6&q=
uot; is also an address sharing extension to &quot;host 4over6&quot;. I thi=
nk it would be reasonable to merge these two documents if the authors of &q=
uot;host 4over6&quot; do not object to it. =C2=A0</div>

<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;">
- merge stateless 4over6 (draft-sun-softwire-stateless-4over6-00) with the =
MAP effort<br></blockquote><div><br></div><div>Qiong: ok. I will merge it w=
ith MAP effort.=C2=A0</div><div><br></div><div>Best wishes</div><div><br></=
div>

<div>Qiong</div><div><br></div><div><br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
;">
<br>
then we&#39;ll have one &#39;stateless&#39; version of A+P document and one=
 &#39;stateful&#39; A+P aka DS-lite with A+P extensions.<br>
both also handling the case of a full IPv4 address on the B4.<br><br></bloc=
kquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex;">
cheers,<br>
Ole<br>
<div class=3D"im"><br>
&gt; ----------------------------------------------------------------------=
-----------------------------------------------------------------<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Lightwe=
ight 4over6 in access network<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 draft-cui-softwire-b4=
-translated-ds-lite-03<br>
&gt;<br>
&gt; Abstract<br>
&gt;<br>
&gt; =C2=A0 =C2=A0The dual-stack lite mechanism provide an IPv4 access meth=
od over IPv6<br>
&gt; =C2=A0 =C2=A0ISP network for end users. =C2=A0Dual-Stack Lite enables =
an IPv6 provider<br>
&gt; =C2=A0 =C2=A0to share IPv4 addresses among customers by combining IPv4=
-in-IPv6<br>
&gt; =C2=A0 =C2=A0tunnel and Carrier Grade NAT. =C2=A0However, in dual-stac=
k lite, CGN has<br>
&gt; =C2=A0 =C2=A0to maintain active NAT sessions, which could become the p=
erformance<br>
&gt; =C2=A0 =C2=A0bottom-neck due to high dynamic s of NAT entries, memory =
cost and log<br>
&gt; =C2=A0 =C2=A0issue. =C2=A0This document propose the lightweight 4over6=
 mechanism which<br>
&gt; =C2=A0 =C2=A0moves the translation function from tunnel concentrator (=
AFTR) to<br>
&gt; =C2=A0 =C2=A0initiators (B4s), and hence reduce the mapping scale on t=
he<br>
&gt; =C2=A0 =C2=A0concentrator to per-customer level. =C2=A0For NAT44 trans=
lation usage, the<br>
&gt; =C2=A0 =C2=A0mechanism will allocate port restricted IPv4 addresses to=
 initiators<br>
&gt; =C2=A0 =C2=A0in a flexible way independent of IPv6 network in the midd=
le.<br>
&gt;<br>
</div>&gt; _______________________________________________<br>
&gt; Softwires mailing list<br>
&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
<br>
</blockquote></div><br></div>

--90e6ba21241b436b5a04b032a15d--

From despres.remi@laposte.net  Wed Oct 26 09:22:14 2011
Return-Path: <despres.remi@laposte.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 D3CF321F85D1 for <softwires@ietfa.amsl.com>; Wed, 26 Oct 2011 09:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSkt67IU22vu for <softwires@ietfa.amsl.com>; Wed, 26 Oct 2011 09:22:10 -0700 (PDT)
Received: from smtpout.laposte.net (smtpout7.laposte.net [193.253.67.232]) by ietfa.amsl.com (Postfix) with ESMTP id 9C89D21F85CE for <softwires@ietf.org>; Wed, 26 Oct 2011 09:22:09 -0700 (PDT)
Received: from [192.168.0.21] ([88.166.221.144]) by mwinf8513-out with ME id pUN51h00337Y3f403UN5SR; Wed, 26 Oct 2011 18:22:07 +0200
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 26 Oct 2011 18:22:04 +0200
Message-Id: <2B0CE5DC-6A1C-4FD5-9F2C-F21A2DD141E9@laposte.net>
To: Alain Durand <adurand@juniper.net>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>
Subject: [Softwires] IETF 82 - A Unified stateless solution for IPv4 Residual Deployments
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, 26 Oct 2011 16:22:15 -0000

Hi Alain,

Can you please schedule a time slot for a 4rd-U presentation:

Title	: A Unified stateless solution for IPv4 residual Deployments (4rd-U)
Document: draft-despres-softwire-4rd-u-01
Duration: 20 min (incl questions, expected to be numerous)

Thanks.
RD



From mawatari@jpix.ad.jp  Wed Oct 26 22:44:42 2011
Return-Path: <mawatari@jpix.ad.jp>
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 A69E221F8B36 for <softwires@ietfa.amsl.com>; Wed, 26 Oct 2011 22:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.409
X-Spam-Level: ***
X-Spam-Status: No, score=3.409 tagged_above=-999 required=5 tests=[AWL=3.499,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JaHxBVwg006Y for <softwires@ietfa.amsl.com>; Wed, 26 Oct 2011 22:44:41 -0700 (PDT)
Received: from mx20.jpix.ad.jp (mx20.jpix.ad.jp [210.171.225.78]) by ietfa.amsl.com (Postfix) with ESMTP id C629D21F8B0F for <softwires@ietf.org>; Wed, 26 Oct 2011 22:44:41 -0700 (PDT)
Received: from [10.10.31.134] (eth3-1-bb-fw-34.jpix.ad.jp [210.171.226.102]) by mx20.jpix.ad.jp (Postfix) with ESMTP id 3ACC7FC021; Thu, 27 Oct 2011 14:44:26 +0900 (JST)
Date: Thu, 27 Oct 2011 14:44:29 +0900
From: MAWATARI Masataka <mawatari@jpix.ad.jp>
To: adurand@juniper.net
In-Reply-To: <2B0CE5DC-6A1C-4FD5-9F2C-F21A2DD141E9@laposte.net>
References: <2B0CE5DC-6A1C-4FD5-9F2C-F21A2DD141E9@laposte.net>
Message-Id: <20111027144428.34AD.8FE1F57E@jpix.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.57.03 [ja]
Cc: softwires@ietf.org, cuiyong@tsinghua.edu.cn
Subject: [Softwires] presentation at IETF 82 (Re: IETF 82 - A Unified stateless solution for IPv4 Residual Deployments)
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, 27 Oct 2011 05:44:42 -0000

Greetings Alain-san,


Please let me make a presentation at IETF 82 Meeting.
I would like to introduce the following draft as a v4->v6->v4
translation experience in softwire working group.

---
Topic: "464XLAT: Combination of Stateful and Stateless Translation"
Draft name: draft-mawatari-softwire-464xlat-01
Time needed: 5-10minutes
Presenter's name: Masataka Mawatari
---

This is a simple technique to provide IPv4 access service across
IPv6 network just by using twice IPv4/IPv6 translation standardized
in [RFC6145] and [RFC6146].

http://tools.ietf.org/html/draft-mawatari-softwire-464xlat


Regards,
Masataka MAWATARI


* On Wed, 26 Oct 2011 18:22:04 +0200
* Remi Despres <despres.remi@laposte.net> wrote:

> Hi Alain,
> 
> Can you please schedule a time slot for a 4rd-U presentation:
> 
> Title	: A Unified stateless solution for IPv4 residual Deployments (4rd-U)
> Document: draft-despres-softwire-4rd-u-01
> Duration: 20 min (incl questions, expected to be numerous)
> 
> Thanks.
> RD

-- 
Japan Internet Exchange
MAWATARI Masataka <mawatari@jpix.ad.jp>
tel:+81-3-3243-9579


From cb.list6@gmail.com  Thu Oct 27 13:21:55 2011
Return-Path: <cb.list6@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 EA43221F8B19 for <softwires@ietfa.amsl.com>; Thu, 27 Oct 2011 13:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.616
X-Spam-Level: 
X-Spam-Status: No, score=-2.616 tagged_above=-999 required=5 tests=[AWL=0.983,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RgO70qwOSdfp for <softwires@ietfa.amsl.com>; Thu, 27 Oct 2011 13:21:55 -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 51EB421F8AFE for <softwires@ietf.org>; Thu, 27 Oct 2011 13:21:52 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3400936vcb.31 for <softwires@ietf.org>; Thu, 27 Oct 2011 13:21:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=N7DFigpa+0yeAtpW1WbVSGMDhMnZys98fRAjDNCsTMw=; b=oFApVRn4nvc79mlemxH6LeFQWBD6g2dElLRpfgF4a8POd4bKtXuk5qyT6WoZdNSYY9 MdV4Q62IYDd27/OgfVcNwOh3bixNv21NExPyt+1flmfX2SvjVz5ltNW7Rm9TQJpeAJgj wCb01tcaMWnUz9yFL8vxEXn3L73blWUuP7DLs=
MIME-Version: 1.0
Received: by 10.68.12.104 with SMTP id x8mr38793pbb.79.1319746911268; Thu, 27 Oct 2011 13:21:51 -0700 (PDT)
Received: by 10.142.14.2 with HTTP; Thu, 27 Oct 2011 13:21:51 -0700 (PDT)
Date: Thu, 27 Oct 2011 13:21:51 -0700
Message-ID: <CAD6AjGRPnggjFqthnX5=077Syo0x3HCSzLUz=p=NqQONp-pBDQ@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: softwires@ietf.org, draft-mawatari-softwire-464xlat@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Softwires] comments draft-mawatari-softwire-464xlat-01
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, 27 Oct 2011 20:21:56 -0000

I like the ideas in this draft.  A few comments:

1. I think this idea of NAT464 is very applicable, especially in
mobile networks.  There is already a similar NAT464 deployment here
https://code.google.com/p/n900ipv6/wiki/README ....Running code,
running architecture, running network are all proven today...   I
think it makes sense to think of the CLAT as a mobile phone, or at
least consider it as a use case.

2. If we can consider the mobile network use case, it may make sense
to broaden the scope to not exclude DNS64 and not require DHCPv6.
Mobile networks do not generally use DHCPv6. My ideal case would be to
allow DNS64 to facilitate as much native and single translation
traffic as possible, while minimizing and enabling the double
translation traffic where it is needed (IPv4 sockets, IPv4 literals,
...).

3.  Since DHCPv6 is not used in mobile, it may make sense to add a
scenario to learn the NSP PREF64 of the NAT64/DNS64 from this work
draft-ietf-behave-nat64-discovery-heuristic-03

4.  So, adding a mobile scenario would be to have CLAT in the phone,
DNS64 and NAT64 in the network, and CLAT does
draft-ietf-behave-nat64-discovery-heuristic-03 to discover NSP.  I
believe this solves an important problem for mobile phone and mobile
networks that must go IPv6-only.  Today, NAT64/DNS64 on mobile phones
work well, but there is a small minority of applications that cannot
work, and this N900 code i showed above has proven to overcome these
limitations.  I believe this draft can provide a generic frame work
for mobile as well as fixed-line that works well if we slightly
increase the scope as mentioned above.

5.  Finally, i think this work should be moved to BEHAVE.  AFAIK,
BEHAVE is not closed and BEHAVE is the right space for this
architectural work that uses the BEHAVE standards.

Cameron

From sarikaya2012@gmail.com  Thu Oct 27 15:05:19 2011
Return-Path: <sarikaya2012@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 D0CD421F84DA for <softwires@ietfa.amsl.com>; Thu, 27 Oct 2011 15:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.414
X-Spam-Level: 
X-Spam-Status: No, score=-3.414 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5pF3n0S2TZp3 for <softwires@ietfa.amsl.com>; Thu, 27 Oct 2011 15:05:19 -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 E865521F84A7 for <softwires@ietf.org>; Thu, 27 Oct 2011 15:05:18 -0700 (PDT)
Received: by gyh20 with SMTP id 20so3636870gyh.31 for <softwires@ietf.org>; Thu, 27 Oct 2011 15:05:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/Pb9qwvhiwSRqFguHVjLcC5c7bcweC+Doxv7RMkV1Bo=; b=crKMYTLDdy0cej5+9yg/8UvmJYAh5vVKH9En8laPMR68IrzkBGsXt1qNxg5g3X1FdH wpQgrv4AQ2rJhhhsUs7llE9WO3kSFX7LQPOSvBcG74gj07aRgCas0ds2skbkoXFgl5h3 zGPDgn0/Jn+X9ryFXhfZpqarR/DiWMXbjvmEk=
MIME-Version: 1.0
Received: by 10.236.78.129 with SMTP id g1mr56118170yhe.52.1319753118472; Thu, 27 Oct 2011 15:05:18 -0700 (PDT)
Received: by 10.236.110.39 with HTTP; Thu, 27 Oct 2011 15:05:18 -0700 (PDT)
In-Reply-To: <CAD6AjGRPnggjFqthnX5=077Syo0x3HCSzLUz=p=NqQONp-pBDQ@mail.gmail.com>
References: <CAD6AjGRPnggjFqthnX5=077Syo0x3HCSzLUz=p=NqQONp-pBDQ@mail.gmail.com>
Date: Thu, 27 Oct 2011 17:05:18 -0500
Message-ID: <CAC8QAceLu3gBjEm5+M8WHCV-EeSFS1-s_UvLMCoPSL2m0cfdoA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
Content-Type: multipart/alternative; boundary=20cf300fb0c3d15b2604b04ef7d0
Cc: softwires@ietf.org, draft-mawatari-softwire-464xlat@tools.ietf.org
Subject: Re: [Softwires] comments draft-mawatari-softwire-464xlat-01
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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, 27 Oct 2011 22:05:20 -0000

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

Hi Cameron,

I think draft-mawatari-softwire-464xlat is about 4rd, they don't clearly say
which approach they are taking but it seems like it is from
murakami-softwire-4v6-translation, this draft is in the reference list but
not referenced.

Of course in 4rd you don't DNS64 due to the double translation.

BTW, mobile networks do have DHCPv6, even on the UE itself since Release 10,
you like it or not.

Regards,

Behcet

On Thu, Oct 27, 2011 at 3:21 PM, Cameron Byrne <cb.list6@gmail.com> wrote:

> I like the ideas in this draft.  A few comments:
>
> 1. I think this idea of NAT464 is very applicable, especially in
> mobile networks.  There is already a similar NAT464 deployment here
> https://code.google.com/p/n900ipv6/wiki/README ....Running code,
> running architecture, running network are all proven today...   I
> think it makes sense to think of the CLAT as a mobile phone, or at
> least consider it as a use case.
>
> 2. If we can consider the mobile network use case, it may make sense
> to broaden the scope to not exclude DNS64 and not require DHCPv6.
> Mobile networks do not generally use DHCPv6. My ideal case would be to
> allow DNS64 to facilitate as much native and single translation
> traffic as possible, while minimizing and enabling the double
> translation traffic where it is needed (IPv4 sockets, IPv4 literals,
> ...).
>
> 3.  Since DHCPv6 is not used in mobile, it may make sense to add a
> scenario to learn the NSP PREF64 of the NAT64/DNS64 from this work
> draft-ietf-behave-nat64-discovery-heuristic-03
>
> 4.  So, adding a mobile scenario would be to have CLAT in the phone,
> DNS64 and NAT64 in the network, and CLAT does
> draft-ietf-behave-nat64-discovery-heuristic-03 to discover NSP.  I
> believe this solves an important problem for mobile phone and mobile
> networks that must go IPv6-only.  Today, NAT64/DNS64 on mobile phones
> work well, but there is a small minority of applications that cannot
> work, and this N900 code i showed above has proven to overcome these
> limitations.  I believe this draft can provide a generic frame work
> for mobile as well as fixed-line that works well if we slightly
> increase the scope as mentioned above.
>
> 5.  Finally, i think this work should be moved to BEHAVE.  AFAIK,
> BEHAVE is not closed and BEHAVE is the right space for this
> architectural work that uses the BEHAVE standards.
>
> Cameron
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

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

Hi Cameron,<br><br>I think draft-mawatari-softwire-464xlat is about 4rd, th=
ey don&#39;t clearly say which approach they are taking but it seems like i=
t is from murakami-softwire-4v6-translation, this draft is in the reference=
 list but not referenced.<br>
<br>Of course in 4rd you don&#39;t DNS64 due to the double translation.<br>=
<br>BTW, mobile networks do have DHCPv6, even on the UE itself since Releas=
e 10, you like it or not.<br><br>Regards,<br><br>Behcet<br><br><div class=
=3D"gmail_quote">
On Thu, Oct 27, 2011 at 3:21 PM, Cameron Byrne <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:cb.list6@gmail.com">cb.list6@gmail.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex;">
I like the ideas in this draft. =A0A few comments:<br>
<br>
1. I think this idea of NAT464 is very applicable, especially in<br>
mobile networks. =A0There is already a similar NAT464 deployment here<br>
<a href=3D"https://code.google.com/p/n900ipv6/wiki/README" target=3D"_blank=
">https://code.google.com/p/n900ipv6/wiki/README</a> ....Running code,<br>
running architecture, running network are all proven today... =A0 I<br>
think it makes sense to think of the CLAT as a mobile phone, or at<br>
least consider it as a use case.<br>
<br>
2. If we can consider the mobile network use case, it may make sense<br>
to broaden the scope to not exclude DNS64 and not require DHCPv6.<br>
Mobile networks do not generally use DHCPv6. My ideal case would be to<br>
allow DNS64 to facilitate as much native and single translation<br>
traffic as possible, while minimizing and enabling the double<br>
translation traffic where it is needed (IPv4 sockets, IPv4 literals,<br>
...).<br>
<br>
3. =A0Since DHCPv6 is not used in mobile, it may make sense to add a<br>
scenario to learn the NSP PREF64 of the NAT64/DNS64 from this work<br>
draft-ietf-behave-nat64-discovery-heuristic-03<br>
<br>
4. =A0So, adding a mobile scenario would be to have CLAT in the phone,<br>
DNS64 and NAT64 in the network, and CLAT does<br>
draft-ietf-behave-nat64-discovery-heuristic-03 to discover NSP. =A0I<br>
believe this solves an important problem for mobile phone and mobile<br>
networks that must go IPv6-only. =A0Today, NAT64/DNS64 on mobile phones<br>
work well, but there is a small minority of applications that cannot<br>
work, and this N900 code i showed above has proven to overcome these<br>
limitations. =A0I believe this draft can provide a generic frame work<br>
for mobile as well as fixed-line that works well if we slightly<br>
increase the scope as mentioned above.<br>
<br>
5. =A0Finally, i think this work should be moved to BEHAVE. =A0AFAIK,<br>
BEHAVE is not closed and BEHAVE is the right space for this<br>
architectural work that uses the BEHAVE standards.<br>
<br>
Cameron<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>
</blockquote></div><br>

--20cf300fb0c3d15b2604b04ef7d0--

From cb.list6@gmail.com  Thu Oct 27 15:15:51 2011
Return-Path: <cb.list6@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 931441F0C54 for <softwires@ietfa.amsl.com>; Thu, 27 Oct 2011 15:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[AWL=0.902,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EIK3wZT6-iCQ for <softwires@ietfa.amsl.com>; Thu, 27 Oct 2011 15:15:51 -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 C57431F0C3D for <softwires@ietf.org>; Thu, 27 Oct 2011 15:15:50 -0700 (PDT)
Received: by vws5 with SMTP id 5so3530523vws.31 for <softwires@ietf.org>; Thu, 27 Oct 2011 15:15:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=MkQDYBuclXOjdxwHXZ4yT8YF2wCyvvvcb+uQ/iyPwNo=; b=wfeJJhbKjXoAIoRJsU88SRmACxpwoHnVgyP/fLFls0C/SArTOkBUr/cAV+2L9aGbP9 4QkU3034gsI1bz0GjDRIV9NpvpKGinDO8Iwiu4zK6JdybzWsHS+qIg5wxtelkvngawy5 cCqCObur1/RKcm1hN21syvQcj6PP1b6M6arBQ=
MIME-Version: 1.0
Received: by 10.182.136.68 with SMTP id py4mr6872150obb.39.1319753740842; Thu, 27 Oct 2011 15:15:40 -0700 (PDT)
Received: by 10.182.72.41 with HTTP; Thu, 27 Oct 2011 15:15:40 -0700 (PDT)
In-Reply-To: <CAC8QAceLu3gBjEm5+M8WHCV-EeSFS1-s_UvLMCoPSL2m0cfdoA@mail.gmail.com>
References: <CAD6AjGRPnggjFqthnX5=077Syo0x3HCSzLUz=p=NqQONp-pBDQ@mail.gmail.com> <CAC8QAceLu3gBjEm5+M8WHCV-EeSFS1-s_UvLMCoPSL2m0cfdoA@mail.gmail.com>
Date: Thu, 27 Oct 2011 15:15:40 -0700
Message-ID: <CAD6AjGQyk5xEF2RmxA9NPSG+_t8KLEAQzxKKy1_0ygtx3E6q_A@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: sarikaya@ieee.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: softwires@ietf.org, draft-mawatari-softwire-464xlat@tools.ietf.org
Subject: Re: [Softwires] comments draft-mawatari-softwire-464xlat-01
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, 27 Oct 2011 22:15:51 -0000

On Thu, Oct 27, 2011 at 3:05 PM, Behcet Sarikaya <sarikaya2012@gmail.com> w=
rote:
> Hi Cameron,
>
> I think draft-mawatari-softwire-464xlat is about 4rd, they don't clearly =
say
> which approach they are taking but it seems like it is from
> murakami-softwire-4v6-translation, this draft is in the reference list bu=
t
> not referenced.
>

I don't know why you would think this is 4RD.  The abstract clearly
references a *stateful NAT64 RFC6146* in the abstract.  So AFAIK, it
is NOT stateless 4RD.


> Of course in 4rd you don't DNS64 due to the double translation.
>
> BTW, mobile networks do have DHCPv6, even on the UE itself since Release =
10,
> you like it or not.
>

Behcet, let me be more clear. The mobile network i work on does not
run DHCPv6 and likely never will. I am also not aware of any mobile
networks that run DHCPv6 or that plan to. You may have more exposure
than me in this area, but that is not the point.  I, simply,  am
interested in solutions that are NAT464 and that do not require
DHCPv6.  That is the feedback i provided as a mobile network operator.

Warmest regards,

Cameron

> Regards,
>
> Behcet
>
> On Thu, Oct 27, 2011 at 3:21 PM, Cameron Byrne <cb.list6@gmail.com> wrote=
:
>>
>> I like the ideas in this draft. =A0A few comments:
>>
>> 1. I think this idea of NAT464 is very applicable, especially in
>> mobile networks. =A0There is already a similar NAT464 deployment here
>> https://code.google.com/p/n900ipv6/wiki/README ....Running code,
>> running architecture, running network are all proven today... =A0 I
>> think it makes sense to think of the CLAT as a mobile phone, or at
>> least consider it as a use case.
>>
>> 2. If we can consider the mobile network use case, it may make sense
>> to broaden the scope to not exclude DNS64 and not require DHCPv6.
>> Mobile networks do not generally use DHCPv6. My ideal case would be to
>> allow DNS64 to facilitate as much native and single translation
>> traffic as possible, while minimizing and enabling the double
>> translation traffic where it is needed (IPv4 sockets, IPv4 literals,
>> ...).
>>
>> 3. =A0Since DHCPv6 is not used in mobile, it may make sense to add a
>> scenario to learn the NSP PREF64 of the NAT64/DNS64 from this work
>> draft-ietf-behave-nat64-discovery-heuristic-03
>>
>> 4. =A0So, adding a mobile scenario would be to have CLAT in the phone,
>> DNS64 and NAT64 in the network, and CLAT does
>> draft-ietf-behave-nat64-discovery-heuristic-03 to discover NSP. =A0I
>> believe this solves an important problem for mobile phone and mobile
>> networks that must go IPv6-only. =A0Today, NAT64/DNS64 on mobile phones
>> work well, but there is a small minority of applications that cannot
>> work, and this N900 code i showed above has proven to overcome these
>> limitations. =A0I believe this draft can provide a generic frame work
>> for mobile as well as fixed-line that works well if we slightly
>> increase the scope as mentioned above.
>>
>> 5. =A0Finally, i think this work should be moved to BEHAVE. =A0AFAIK,
>> BEHAVE is not closed and BEHAVE is the right space for this
>> architectural work that uses the BEHAVE standards.
>>
>> Cameron
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>
>

From internet-drafts@ietf.org  Fri Oct 28 23:12:32 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 3303221F848D; Fri, 28 Oct 2011 23:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id evhYwhodq4VS; Fri, 28 Oct 2011 23:12:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD23C21F8486; Fri, 28 Oct 2011 23:12:31 -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.62
Message-ID: <20111029061231.15310.43543.idtracker@ietfa.amsl.com>
Date: Fri, 28 Oct 2011 23:12:31 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-mesh-multicast-01.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, 29 Oct 2011 06:12:32 -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           : Softwire Mesh Multicast
	Author(s)       : Mingwei Xu
                          Yong Cui
                          Shu Yang
                          Jianping Wu
                          Chris Metz
                          Greg Shepherd
	Filename        : draft-ietf-softwire-mesh-multicast-01.txt
	Pages           : 23
	Date            : 2011-10-28

   The Internet needs to support IPv4 and IPv6 packets.  Both address
   families and their attendant protocol suites support multicast of the
   single-source and any-source varieties.  As part of the transition to
   IPv6, there will be scenarios where a backbone network running one IP
   address family internally (referred to as internal IP or I-IP) will
   provide transit services to attached client networks running another
   IP address family (referred to as external IP or E-IP).  It is
   expected that the I-IP backbone will offer unicast and multicast
   transit services to the client E-IP networks.

   Softwires Mesh is a solution to E-IP unicast and multicast support
   across an I-IP backbone.  This document describes the mechanisms for
   supporting Internet-style multicast across a set of E-IP and I-IP
   networks supporting softwires mesh.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-mesh-multicast-01.t=
xt

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-mesh-multicast-01.txt

From mawatari@jpix.ad.jp  Sat Oct 29 04:06:20 2011
Return-Path: <mawatari@jpix.ad.jp>
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 8023821F8A56; Sat, 29 Oct 2011 04:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YszZUtDM1vy5; Sat, 29 Oct 2011 04:06:20 -0700 (PDT)
Received: from mx20.jpix.ad.jp (mx20.jpix.ad.jp [210.171.225.78]) by ietfa.amsl.com (Postfix) with ESMTP id D18FC21F88A0; Sat, 29 Oct 2011 04:06:19 -0700 (PDT)
Received: from [192.168.11.3] (i60-34-9-195.s02.a013.ap.plala.or.jp [60.34.9.195]) by mx20.jpix.ad.jp (Postfix) with ESMTP id B91D7FC021; Sat, 29 Oct 2011 20:06:17 +0900 (JST)
Date: Sat, 29 Oct 2011 20:06:18 +0900
From: MAWATARI Masataka <mawatari@jpix.ad.jp>
To: cb.list6@gmail.com
In-Reply-To: <CAD6AjGRPnggjFqthnX5=077Syo0x3HCSzLUz=p=NqQONp-pBDQ@mail.gmail.com>
References: <CAD6AjGRPnggjFqthnX5=077Syo0x3HCSzLUz=p=NqQONp-pBDQ@mail.gmail.com>
Message-Id: <20111029200617.386A.8FE1F57E@jpix.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.57.03 [ja]
Cc: softwires@ietf.org, behave@ietf.org, draft-mawatari-softwire-464xlat@tools.ietf.org
Subject: Re: [Softwires] comments draft-mawatari-softwire-464xlat-01
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, 29 Oct 2011 11:06:20 -0000

Greetings Cameron-san,


Cross posting to behave.

Thank you very much for your comment and sorry for the delay.


n900ipv6 is interesting. Thank you for good information.

The CLAT necessary for function is simple and easy to implement
so the range of application of CLAT can be expanded.

I agree that 464xlat is applied to mobile network too.
I think that it can utilize a simplicity of implementation on CLAT
and adding a usecase of the mobile network to this draft is possible.


You mentioned that this method in this draft don't require DHCPv6.
I agree with you. But I think that there are other proposals must not
use DHCPv6. please let me know about your mention about this point.


Regards,
Masataka MAWATARI


* On Thu, 27 Oct 2011 13:21:51 -0700
* Cameron Byrne <cb.list6@gmail.com> wrote:

> I like the ideas in this draft.  A few comments:
> 
> 1. I think this idea of NAT464 is very applicable, especially in
> mobile networks.  There is already a similar NAT464 deployment here
> https://code.google.com/p/n900ipv6/wiki/README ....Running code,
> running architecture, running network are all proven today...   I
> think it makes sense to think of the CLAT as a mobile phone, or at
> least consider it as a use case.
> 
> 2. If we can consider the mobile network use case, it may make sense
> to broaden the scope to not exclude DNS64 and not require DHCPv6.
> Mobile networks do not generally use DHCPv6. My ideal case would be to
> allow DNS64 to facilitate as much native and single translation
> traffic as possible, while minimizing and enabling the double
> translation traffic where it is needed (IPv4 sockets, IPv4 literals,
> ...).
> 
> 3.  Since DHCPv6 is not used in mobile, it may make sense to add a
> scenario to learn the NSP PREF64 of the NAT64/DNS64 from this work
> draft-ietf-behave-nat64-discovery-heuristic-03
> 
> 4.  So, adding a mobile scenario would be to have CLAT in the phone,
> DNS64 and NAT64 in the network, and CLAT does
> draft-ietf-behave-nat64-discovery-heuristic-03 to discover NSP.  I
> believe this solves an important problem for mobile phone and mobile
> networks that must go IPv6-only.  Today, NAT64/DNS64 on mobile phones
> work well, but there is a small minority of applications that cannot
> work, and this N900 code i showed above has proven to overcome these
> limitations.  I believe this draft can provide a generic frame work
> for mobile as well as fixed-line that works well if we slightly
> increase the scope as mentioned above.
> 
> 5.  Finally, i think this work should be moved to BEHAVE.  AFAIK,
> BEHAVE is not closed and BEHAVE is the right space for this
> architectural work that uses the BEHAVE standards.
> 
> Cameron

-- 
Japan Internet Exchange
MAWATARI Masataka <mawatari@jpix.ad.jp>
tel:+81-3-3243-9579


From mawatari@jpix.ad.jp  Sat Oct 29 05:43:14 2011
Return-Path: <mawatari@jpix.ad.jp>
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 4D34F21F891D; Sat, 29 Oct 2011 05:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kWOOiq5Mw7R5; Sat, 29 Oct 2011 05:43:13 -0700 (PDT)
Received: from mx20.jpix.ad.jp (mx20.jpix.ad.jp [210.171.225.78]) by ietfa.amsl.com (Postfix) with ESMTP id 9E3FC21F8906; Sat, 29 Oct 2011 05:43:13 -0700 (PDT)
Received: from [192.168.11.3] (i60-34-9-195.s02.a013.ap.plala.or.jp [60.34.9.195]) by mx20.jpix.ad.jp (Postfix) with ESMTP id E2190FC021; Sat, 29 Oct 2011 21:43:09 +0900 (JST)
Date: Sat, 29 Oct 2011 21:43:10 +0900
From: MAWATARI Masataka <mawatari@jpix.ad.jp>
To: cb.list6@gmail.com
In-Reply-To: <20111029200617.386A.8FE1F57E@jpix.ad.jp>
References: <CAD6AjGRPnggjFqthnX5=077Syo0x3HCSzLUz=p=NqQONp-pBDQ@mail.gmail.com> <20111029200617.386A.8FE1F57E@jpix.ad.jp>
Message-Id: <20111029214309.3871.8FE1F57E@jpix.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.57.03 [ja]
Cc: softwires@ietf.org, behave@ietf.org, draft-mawatari-softwire-464xlat@tools.ietf.org
Subject: Re: [Softwires] comments draft-mawatari-softwire-464xlat-01
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, 29 Oct 2011 12:43:14 -0000

Greetings Cameron-san,


* On Sat, 29 Oct 2011 20:06:18 +0900
* MAWATARI Masataka <mawatari@jpix.ad.jp> wrote:

> Greetings Cameron-san,
> 
> 
> Cross posting to behave.
> 
> Thank you very much for your comment and sorry for the delay.
> 
> 
> n900ipv6 is interesting. Thank you for good information.
> 
> The CLAT necessary for function is simple and easy to implement
> so the range of application of CLAT can be expanded.
> 
> I agree that 464xlat is applied to mobile network too.
> I think that it can utilize a simplicity of implementation on CLAT
> and adding a usecase of the mobile network to this draft is possible.
> 
> 
> You mentioned that this method in this draft don't require DHCPv6.
> I agree with you. But I think that there are other proposals must not
> use DHCPv6. please let me know about your mention about this point.


I'm sorry... I made a mistake.
I meant to say "I think that there are other proposals don't require
DHCPv6".


Kind Regards,
Masataka MAWATARI


> * On Thu, 27 Oct 2011 13:21:51 -0700
> * Cameron Byrne <cb.list6@gmail.com> wrote:
> 
> > I like the ideas in this draft.  A few comments:
> > 
> > 1. I think this idea of NAT464 is very applicable, especially in
> > mobile networks.  There is already a similar NAT464 deployment here
> > https://code.google.com/p/n900ipv6/wiki/README ....Running code,
> > running architecture, running network are all proven today...   I
> > think it makes sense to think of the CLAT as a mobile phone, or at
> > least consider it as a use case.
> > 
> > 2. If we can consider the mobile network use case, it may make sense
> > to broaden the scope to not exclude DNS64 and not require DHCPv6.
> > Mobile networks do not generally use DHCPv6. My ideal case would be to
> > allow DNS64 to facilitate as much native and single translation
> > traffic as possible, while minimizing and enabling the double
> > translation traffic where it is needed (IPv4 sockets, IPv4 literals,
> > ...).
> > 
> > 3.  Since DHCPv6 is not used in mobile, it may make sense to add a
> > scenario to learn the NSP PREF64 of the NAT64/DNS64 from this work
> > draft-ietf-behave-nat64-discovery-heuristic-03
> > 
> > 4.  So, adding a mobile scenario would be to have CLAT in the phone,
> > DNS64 and NAT64 in the network, and CLAT does
> > draft-ietf-behave-nat64-discovery-heuristic-03 to discover NSP.  I
> > believe this solves an important problem for mobile phone and mobile
> > networks that must go IPv6-only.  Today, NAT64/DNS64 on mobile phones
> > work well, but there is a small minority of applications that cannot
> > work, and this N900 code i showed above has proven to overcome these
> > limitations.  I believe this draft can provide a generic frame work
> > for mobile as well as fixed-line that works well if we slightly
> > increase the scope as mentioned above.
> > 
> > 5.  Finally, i think this work should be moved to BEHAVE.  AFAIK,
> > BEHAVE is not closed and BEHAVE is the right space for this
> > architectural work that uses the BEHAVE standards.
> > 
> > Cameron

-- 
Japan Internet Exchange
MAWATARI Masataka <mawatari@jpix.ad.jp>
tel:+81-3-3243-9579


From washam.fan@gmail.com  Sun Oct 30 22:36:06 2011
Return-Path: <washam.fan@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 B584B21F8C79 for <softwires@ietfa.amsl.com>; Sun, 30 Oct 2011 22:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gT0lC8xB+Gc for <softwires@ietfa.amsl.com>; Sun, 30 Oct 2011 22:36:05 -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 A330421F8C6D for <softwires@ietf.org>; Sun, 30 Oct 2011 22:36:05 -0700 (PDT)
Received: by wyg30 with SMTP id 30so829134wyg.31 for <softwires@ietf.org>; Sun, 30 Oct 2011 22:36:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=3kjOLXpD3fH+gM2UNxmW9SbTXBo4fJuG3gulehUHrbU=; b=GRA4YECt/H/3WmWkd5a6u9K44g7qmdM8Ih1xgfhHU/Gyi5JRCE/ep49XfzuEkLSwA6 vKefhasAiYtr1htcQoeSNC2yuk9Kbk8ME7Uifk97wXjS+NmInjiNQx5z3amb48Tfvt2w 1oJAcEMKbFc1XNwG3B+m9ZiIkgX3aSforUrU8=
MIME-Version: 1.0
Received: by 10.216.163.194 with SMTP id a44mr3903328wel.1.1320039364838; Sun, 30 Oct 2011 22:36:04 -0700 (PDT)
Received: by 10.216.85.4 with HTTP; Sun, 30 Oct 2011 22:36:04 -0700 (PDT)
Date: Mon, 31 Oct 2011 13:36:04 +0800
Message-ID: <CAAuHL_Cc34o56ytVO4k3cvJT_oi1c5AyoYF7QY1=ZN=yQK1euA@mail.gmail.com>
From: Washam Fan <washam.fan@gmail.com>
To: Softwires <softwires@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Softwires] Comments on divi-pd
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, 31 Oct 2011 05:36:06 -0000

Hi the authors,

I have 2 comments on this draft so far.

1. Appendix A gives an example how to generate a IPv4-translatable
address delegated to a CPE, but miss the part how a CPE derive a IPv4
prefix, address, or shared address from a given delegated
IPv4-translatable address. At least, I think the s bits can not be
derived without extra provisioning.

2. It seems to me native IPv6 addresses and IPv4-translatable
addresses share the same prefix. Then how a CPE identify a IPv6 packet
arriving at the WAN-facing interface is a native one or a translated
one?

Thanks,
washam

From despres.remi@laposte.net  Mon Oct 31 02:25:08 2011
Return-Path: <despres.remi@laposte.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 DD85221F8D5A for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 02:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.124
X-Spam-Level: 
X-Spam-Status: No, score=-2.124 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wil62DqEQ3uF for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 02:25:08 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.121]) by ietfa.amsl.com (Postfix) with ESMTP id 28FA321F8D56 for <softwires@ietf.org>; Mon, 31 Oct 2011 02:25:08 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2516.sfr.fr (SMTP Server) with ESMTP id 05A91700008D; Mon, 31 Oct 2011 10:25:07 +0100 (CET)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2516.sfr.fr (SMTP Server) with ESMTP id 759DE7000088; Mon, 31 Oct 2011 10:25:04 +0100 (CET)
X-SFR-UUID: 20111031092504481.759DE7000088@msfrf2516.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Mon, 31 Oct 2011 10:25:03 +0100
Message-Id: <D97FDCF6-BA79-4363-A237-58369F03C74A@laposte.net>
To: Mawatari Masataka <mawatari@jpix.ad.jp>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: [Softwires] 464XLAT - clarification? - relationship with 4rd-U
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, 31 Oct 2011 09:25:09 -0000

Hi Masataka-san,

1.
Thank you for sharing your interesting experience with the JPIX trial =
service based on 464XLAT.
Could you, for clarification, describe in more details formats of XLAT =
prefixes in this trial?=20

2.
Objectives of 464XLAT and 4rd-U look very similar (ref =
draft-despres-softwire-4rd-u-01).

Indeed:
- Both use "DHCPv6 prefix delegation or another method" to inform =
CLAT/CEs of their IPv6 prefixes.
- Both "can implement traffic engineering based on IPv4 source address =
and IPv4 destination address" (a feature that, as noted in your draft, =
is missing in encapsulation).

OTOH, unless I miss something, 464XLAT doesn't provide incoming =
connectivity of CLATs in case of shared IPv4 addresses (while 4rd-U does =
provide it to CEs). In this respect 4rd-U seems functionally more =
complete.

Thoughts?


Regards,
RD
=20
=20


Le 27 oct. 2011 =E0 07:44, MAWATARI Masataka a =E9crit :

> Greetings Alain-san,
>=20
>=20
> Please let me make a presentation at IETF 82 Meeting.
> I would like to introduce the following draft as a v4->v6->v4
> translation experience in softwire working group.
>=20
> ---
> Topic: "464XLAT: Combination of Stateful and Stateless Translation"
> Draft name: draft-mawatari-softwire-464xlat-01
> Time needed: 5-10minutes
> Presenter's name: Masataka Mawatari
> ---
>=20
> This is a simple technique to provide IPv4 access service across
> IPv6 network just by using twice IPv4/IPv6 translation standardized
> in [RFC6145] and [RFC6146].
>=20
> http://tools.ietf.org/html/draft-mawatari-softwire-464xlat
>=20
>=20
> Regards,
> Masataka MAWATARI
>=20
>=20
> * On Wed, 26 Oct 2011 18:22:04 +0200
> * Remi Despres <despres.remi@laposte.net> wrote:
>=20
>> Hi Alain,
>>=20
>> Can you please schedule a time slot for a 4rd-U presentation:
>>=20
>> Title	: A Unified stateless solution for IPv4 residual =
Deployments (4rd-U)
>> Document: draft-despres-softwire-4rd-u-01
>> Duration: 20 min (incl questions, expected to be numerous)
>>=20
>> Thanks.
>> RD
>=20
> --=20
> Japan Internet Exchange
> MAWATARI Masataka <mawatari@jpix.ad.jp>
> tel:+81-3-3243-9579
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From cb.list6@gmail.com  Mon Oct 31 06:09:17 2011
Return-Path: <cb.list6@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 6493221F84D9 for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 06:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level: 
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[AWL=0.622,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYSKVqxJ435J for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 06:09:16 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7DFA821F84D7 for <softwires@ietf.org>; Mon, 31 Oct 2011 06:09:16 -0700 (PDT)
Received: by qadc10 with SMTP id c10so6287275qad.31 for <softwires@ietf.org>; Mon, 31 Oct 2011 06:09:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xy8iBiJx7MKMQn5av3QufIPIrX63d5aim40Fp1PN/m0=; b=dnlNrmYPmNZ/sDq8wHQonD6JivnWjbwcSh3o3ywuufjLn3ogZsbzrysjT0Y06KpFoE uPE1qTVvBwlriiFKUS+MOGsDpbadltMqYXJtM073yLZ7yzSKFasBQ2n1snb+Tzd0Y0H9 x46nfPJkaIn9ap5vRq+NTLzvytOTIDhR+Kk8s=
MIME-Version: 1.0
Received: by 10.68.44.168 with SMTP id f8mr23899954pbm.11.1320066555487; Mon, 31 Oct 2011 06:09:15 -0700 (PDT)
Received: by 10.142.230.8 with HTTP; Mon, 31 Oct 2011 06:09:15 -0700 (PDT)
Received: by 10.142.230.8 with HTTP; Mon, 31 Oct 2011 06:09:15 -0700 (PDT)
In-Reply-To: <D97FDCF6-BA79-4363-A237-58369F03C74A@laposte.net>
References: <D97FDCF6-BA79-4363-A237-58369F03C74A@laposte.net>
Date: Mon, 31 Oct 2011 06:09:15 -0700
Message-ID: <CAD6AjGQqCnqWq74pT6ETZz_1KerybN7fwVqaO73v8T5X=WRZHg@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=bcaec520f0cd1ea41d04b097f230
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 464XLAT - clarification? - relationship with 4rd-U
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, 31 Oct 2011 13:09:17 -0000

--bcaec520f0cd1ea41d04b097f230
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Oct 31, 2011 2:25 AM, "R=E9mi Despr=E9s" <despres.remi@laposte.net> wrot=
e:
>
> Hi Masataka-san,
>
> 1.
> Thank you for sharing your interesting experience with the JPIX trial
service based on 464XLAT.
> Could you, for clarification, describe in more details formats of XLAT
prefixes in this trial?
>
> 2.
> Objectives of 464XLAT and 4rd-U look very similar (ref
draft-despres-softwire-4rd-u-01).
>
> Indeed:
> - Both use "DHCPv6 prefix delegation or another method" to inform
CLAT/CEs of their IPv6 prefixes.
> - Both "can implement traffic engineering based on IPv4 source address
and IPv4 destination address" (a feature that, as noted in your draft, is
missing in encapsulation).
>
> OTOH, unless I miss something, 464XLAT doesn't provide incoming
connectivity of CLATs in case of shared IPv4 addresses (while 4rd-U does
provide it to CEs). In this respect 4rd-U seems functionally more complete.
>
> Thoughts?
>

The difference, imho, is stateful vs stateless.

Many operators like myself do not have enough ipv4 addresses to
incrementally grow with a stateless solution. It is not possible to
renumber the existing network and flash everyone into a stateless solution,
so I require a more scalable solution ...starting with very few address.

Also, given the very small amount of existing ipv4, the per port
allocations of a stateless solution are not acceptable for me.  Others may
have different starting positions therefore may find stateless helpful.

Cb
>
> Regards,
> RD
>
>
>
>
> Le 27 oct. 2011 =E0 07:44, MAWATARI Masataka a =E9crit :
>
> > Greetings Alain-san,
> >
> >
> > Please let me make a presentation at IETF 82 Meeting.
> > I would like to introduce the following draft as a v4->v6->v4
> > translation experience in softwire working group.
> >
> > ---
> > Topic: "464XLAT: Combination of Stateful and Stateless Translation"
> > Draft name: draft-mawatari-softwire-464xlat-01
> > Time needed: 5-10minutes
> > Presenter's name: Masataka Mawatari
> > ---
> >
> > This is a simple technique to provide IPv4 access service across
> > IPv6 network just by using twice IPv4/IPv6 translation standardized
> > in [RFC6145] and [RFC6146].
> >
> > http://tools.ietf.org/html/draft-mawatari-softwire-464xlat
> >
> >
> > Regards,
> > Masataka MAWATARI
> >
> >
> > * On Wed, 26 Oct 2011 18:22:04 +0200
> > * Remi Despres <despres.remi@laposte.net> wrote:
> >
> >> Hi Alain,
> >>
> >> Can you please schedule a time slot for a 4rd-U presentation:
> >>
> >> Title        : A Unified stateless solution for IPv4 residual
Deployments (4rd-U)
> >> Document: draft-despres-softwire-4rd-u-01
> >> Duration: 20 min (incl questions, expected to be numerous)
> >>
> >> Thanks.
> >> RD
> >
> > --
> > Japan Internet Exchange
> > MAWATARI Masataka <mawatari@jpix.ad.jp>
> > tel:+81-3-3243-9579
> >
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

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

<p><br>
On Oct 31, 2011 2:25 AM, &quot;R=E9mi Despr=E9s&quot; &lt;<a href=3D"mailto=
:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Masataka-san,<br>
&gt;<br>
&gt; 1.<br>
&gt; Thank you for sharing your interesting experience with the JPIX trial =
service based on 464XLAT.<br>
&gt; Could you, for clarification, describe in more details formats of XLAT=
 prefixes in this trial?<br>
&gt;<br>
&gt; 2.<br>
&gt; Objectives of 464XLAT and 4rd-U look very similar (ref draft-despres-s=
oftwire-4rd-u-01).<br>
&gt;<br>
&gt; Indeed:<br>
&gt; - Both use &quot;DHCPv6 prefix delegation or another method&quot; to i=
nform CLAT/CEs of their IPv6 prefixes.<br>
&gt; - Both &quot;can implement traffic engineering based on IPv4 source ad=
dress and IPv4 destination address&quot; (a feature that, as noted in your =
draft, is missing in encapsulation).<br>
&gt;<br>
&gt; OTOH, unless I miss something, 464XLAT doesn&#39;t provide incoming co=
nnectivity of CLATs in case of shared IPv4 addresses (while 4rd-U does prov=
ide it to CEs). In this respect 4rd-U seems functionally more complete.<br>

&gt;<br>
&gt; Thoughts?<br>
&gt;</p>
<p>The difference, imho, is stateful vs stateless.</p>
<p>Many operators like myself do not have enough ipv4 addresses to incremen=
tally grow with a stateless solution. It is not possible to renumber the ex=
isting network and flash everyone into a stateless solution, so I require a=
 more scalable solution ...starting with very few address.</p>

<p>Also, given the very small amount of existing ipv4, the per port allocat=
ions of a stateless solution are not acceptable for me.=A0 Others may have =
different starting positions therefore may find stateless helpful.</p>
<p>Cb<br>
&gt;<br>
&gt; Regards,<br>
&gt; RD<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Le 27 oct. 2011 =E0 07:44, MAWATARI Masataka a =E9crit :<br>
&gt;<br>
&gt; &gt; Greetings Alain-san,<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Please let me make a presentation at IETF 82 Meeting.<br>
&gt; &gt; I would like to introduce the following draft as a v4-&gt;v6-&gt;=
v4<br>
&gt; &gt; translation experience in softwire working group.<br>
&gt; &gt;<br>
&gt; &gt; ---<br>
&gt; &gt; Topic: &quot;464XLAT: Combination of Stateful and Stateless Trans=
lation&quot;<br>
&gt; &gt; Draft name: draft-mawatari-softwire-464xlat-01<br>
&gt; &gt; Time needed: 5-10minutes<br>
&gt; &gt; Presenter&#39;s name: Masataka Mawatari<br>
&gt; &gt; ---<br>
&gt; &gt;<br>
&gt; &gt; This is a simple technique to provide IPv4 access service across<=
br>
&gt; &gt; IPv6 network just by using twice IPv4/IPv6 translation standardiz=
ed<br>
&gt; &gt; in [RFC6145] and [RFC6146].<br>
&gt; &gt;<br>
&gt; &gt; <a href=3D"http://tools.ietf.org/html/draft-mawatari-softwire-464=
xlat">http://tools.ietf.org/html/draft-mawatari-softwire-464xlat</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt; Masataka MAWATARI<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; * On Wed, 26 Oct 2011 18:22:04 +0200<br>
&gt; &gt; * Remi Despres &lt;<a href=3D"mailto:despres.remi@laposte.net">de=
spres.remi@laposte.net</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; Hi Alain,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Can you please schedule a time slot for a 4rd-U presentation:=
<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Title =A0 =A0 =A0 =A0: A Unified stateless solution for IPv4 =
residual Deployments (4rd-U)<br>
&gt; &gt;&gt; Document: draft-despres-softwire-4rd-u-01<br>
&gt; &gt;&gt; Duration: 20 min (incl questions, expected to be numerous)<br=
>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Thanks.<br>
&gt; &gt;&gt; RD<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Japan Internet Exchange<br>
&gt; &gt; MAWATARI Masataka &lt;<a href=3D"mailto:mawatari@jpix.ad.jp">mawa=
tari@jpix.ad.jp</a>&gt;<br>
&gt; &gt; tel:+81-3-3243-9579<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Softwires mailing list<br>
&gt; &gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires">https=
://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt; _______________________________________________<br>
&gt; Softwires mailing list<br>
&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires">https://ww=
w.ietf.org/mailman/listinfo/softwires</a><br>
</p>

--bcaec520f0cd1ea41d04b097f230--

From despres.remi@laposte.net  Mon Oct 31 06:19:09 2011
Return-Path: <despres.remi@laposte.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 5E72A21F8C30 for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 06:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.065
X-Spam-Level: 
X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fi88qSH8DJ2F for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 06:19:08 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.21]) by ietfa.amsl.com (Postfix) with ESMTP id ECD9B21F8C31 for <softwires@ietf.org>; Mon, 31 Oct 2011 06:19:03 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2313.sfr.fr (SMTP Server) with ESMTP id CD4527000247; Mon, 31 Oct 2011 14:19:02 +0100 (CET)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2313.sfr.fr (SMTP Server) with ESMTP id 1200A7000241; Mon, 31 Oct 2011 14:19:00 +0100 (CET)
X-SFR-UUID: 20111031131900738.1200A7000241@msfrf2313.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-33-310039790
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAD6AjGQqCnqWq74pT6ETZz_1KerybN7fwVqaO73v8T5X=WRZHg@mail.gmail.com>
Date: Mon, 31 Oct 2011 14:18:59 +0100
Message-Id: <CB5755DD-C77D-4B06-8BEB-FB30C07B10BD@laposte.net>
References: <D97FDCF6-BA79-4363-A237-58369F03C74A@laposte.net> <CAD6AjGQqCnqWq74pT6ETZz_1KerybN7fwVqaO73v8T5X=WRZHg@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 464XLAT - clarification? - relationship with 4rd-U
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, 31 Oct 2011 13:19:09 -0000

--Apple-Mail-33-310039790
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 31 oct. 2011 =E0 14:09, Cameron Byrne a =E9crit :

>=20
> On Oct 31, 2011 2:25 AM, "R=E9mi Despr=E9s" <despres.remi@laposte.net> =
wrote:
> >
> > Hi Masataka-san,
> >
> > 1.
> > Thank you for sharing your interesting experience with the JPIX =
trial service based on 464XLAT.
> > Could you, for clarification, describe in more details formats of =
XLAT prefixes in this trial?
> >
> > 2.
> > Objectives of 464XLAT and 4rd-U look very similar (ref =
draft-despres-softwire-4rd-u-01).
> >
> > Indeed:
> > - Both use "DHCPv6 prefix delegation or another method" to inform =
CLAT/CEs of their IPv6 prefixes.
> > - Both "can implement traffic engineering based on IPv4 source =
address and IPv4 destination address" (a feature that, as noted in your =
draft, is missing in encapsulation).
> >
> > OTOH, unless I miss something, 464XLAT doesn't provide incoming =
connectivity of CLATs in case of shared IPv4 addresses (while 4rd-U does =
provide it to CEs). In this respect 4rd-U seems functionally more =
complete.
> >
> > Thoughts?
> >
>=20
> The difference, imho, is stateful vs stateless.
>=20
> Many operators like myself do not have enough ipv4 addresses to =
incrementally grow with a stateless solution.
>=20
Sharing the orders of magnitude you have to face would help to =
appreciate this constraint (reminding that hosts that are dual-stack =
don't need as many IPv4 ports as others).

> It is not possible to renumber the existing network and flash everyone =
into a stateless solution, so I require a more scalable solution =
...starting with very few address.
>=20
> Also, given the very small amount of existing ipv4, the per port =
allocations of a stateless solution are not acceptable for me.=20
>=20
Same point as above.

Regards,
RD




> Others may have different starting positions therefore may find =
stateless helpful.
>=20
> Cb
> >
> > Regards,
> > RD
> >
> >
> >
> >
> > Le 27 oct. 2011 =E0 07:44, MAWATARI Masataka a =E9crit :
> >
> > > Greetings Alain-san,
> > >
> > >
> > > Please let me make a presentation at IETF 82 Meeting.
> > > I would like to introduce the following draft as a v4->v6->v4
> > > translation experience in softwire working group.
> > >
> > > ---
> > > Topic: "464XLAT: Combination of Stateful and Stateless =
Translation"
> > > Draft name: draft-mawatari-softwire-464xlat-01
> > > Time needed: 5-10minutes
> > > Presenter's name: Masataka Mawatari
> > > ---
> > >
> > > This is a simple technique to provide IPv4 access service across
> > > IPv6 network just by using twice IPv4/IPv6 translation =
standardized
> > > in [RFC6145] and [RFC6146].
> > >
> > > http://tools.ietf.org/html/draft-mawatari-softwire-464xlat
> > >
> > >
> > > Regards,
> > > Masataka MAWATARI
> > >
> > >
> > > * On Wed, 26 Oct 2011 18:22:04 +0200
> > > * Remi Despres <despres.remi@laposte.net> wrote:
> > >
> > >> Hi Alain,
> > >>
> > >> Can you please schedule a time slot for a 4rd-U presentation:
> > >>
> > >> Title        : A Unified stateless solution for IPv4 residual =
Deployments (4rd-U)
> > >> Document: draft-despres-softwire-4rd-u-01
> > >> Duration: 20 min (incl questions, expected to be numerous)
> > >>
> > >> Thanks.
> > >> RD
> > >
> > > --
> > > Japan Internet Exchange
> > > MAWATARI Masataka <mawatari@jpix.ad.jp>
> > > tel:+81-3-3243-9579
> > >
> > > _______________________________________________
> > > Softwires mailing list
> > > Softwires@ietf.org
> > > https://www.ietf.org/mailman/listinfo/softwires
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires


--Apple-Mail-33-310039790
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 31 oct. 2011 =E0 14:09, Cameron Byrne a =E9crit =
:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><p><br>
On Oct 31, 2011 2:25 AM, "R=E9mi Despr=E9s" &lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt; =
wrote:<br>
&gt;<br>
&gt; Hi Masataka-san,<br>
&gt;<br>
&gt; 1.<br>
&gt; Thank you for sharing your interesting experience with the JPIX =
trial service based on 464XLAT.<br>
&gt; Could you, for clarification, describe in more details formats of =
XLAT prefixes in this trial?<br>
&gt;<br>
&gt; 2.<br>
&gt; Objectives of 464XLAT and 4rd-U look very similar (ref =
draft-despres-softwire-4rd-u-01).<br>
&gt;<br>
&gt; Indeed:<br>
&gt; - Both use "DHCPv6 prefix delegation or another method" to inform =
CLAT/CEs of their IPv6 prefixes.<br>
&gt; - Both "can implement traffic engineering based on IPv4 source =
address and IPv4 destination address" (a feature that, as noted in your =
draft, is missing in encapsulation).<br>
&gt;<br>
&gt; OTOH, unless I miss something, 464XLAT doesn't provide incoming =
connectivity of CLATs in case of shared IPv4 addresses (while 4rd-U does =
provide it to CEs). In this respect 4rd-U seems functionally more =
complete.<br>

&gt;<br>
&gt; Thoughts?<br>
&gt;</p><p>The difference, imho, is stateful vs stateless.</p><p>Many =
operators like myself do not have enough ipv4 addresses to incrementally =
grow with a stateless solution.</p></blockquote><div>Sharing the orders =
of magnitude you have to face would help to appreciate this constraint =
(reminding that hosts that are dual-stack don't need as many IPv4 ports =
as others).</div><div><br></div><blockquote type=3D"cite"><p> It is not =
possible to renumber the existing network and flash everyone into a =
stateless solution, so I require a more scalable solution ...starting =
with very few address.</p></blockquote><blockquote type=3D"cite"><p>Also, =
given the very small amount of existing ipv4, the per port allocations =
of a stateless solution are not acceptable for me.&nbsp; =
</p></blockquote><div>Same point as =
above.</div><div><br></div><div>Regards,</div><div>RD</div><div><br></div>=
<div><br></div><div><br></div><br><blockquote type=3D"cite"><p>Others =
may have different starting positions therefore may find stateless =
helpful.</p><p>Cb<br>
&gt;<br>
&gt; Regards,<br>
&gt; RD<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Le 27 oct. 2011 =E0 07:44, MAWATARI Masataka a =E9crit :<br>
&gt;<br>
&gt; &gt; Greetings Alain-san,<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Please let me make a presentation at IETF 82 Meeting.<br>
&gt; &gt; I would like to introduce the following draft as a =
v4-&gt;v6-&gt;v4<br>
&gt; &gt; translation experience in softwire working group.<br>
&gt; &gt;<br>
&gt; &gt; ---<br>
&gt; &gt; Topic: "464XLAT: Combination of Stateful and Stateless =
Translation"<br>
&gt; &gt; Draft name: draft-mawatari-softwire-464xlat-01<br>
&gt; &gt; Time needed: 5-10minutes<br>
&gt; &gt; Presenter's name: Masataka Mawatari<br>
&gt; &gt; ---<br>
&gt; &gt;<br>
&gt; &gt; This is a simple technique to provide IPv4 access service =
across<br>
&gt; &gt; IPv6 network just by using twice IPv4/IPv6 translation =
standardized<br>
&gt; &gt; in [RFC6145] and [RFC6146].<br>
&gt; &gt;<br>
&gt; &gt; <a =
href=3D"http://tools.ietf.org/html/draft-mawatari-softwire-464xlat">http:/=
/tools.ietf.org/html/draft-mawatari-softwire-464xlat</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt; Masataka MAWATARI<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; * On Wed, 26 Oct 2011 18:22:04 +0200<br>
&gt; &gt; * Remi Despres &lt;<a =
href=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt; =
wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; Hi Alain,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Can you please schedule a time slot for a 4rd-U =
presentation:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Title &nbsp; &nbsp; &nbsp; &nbsp;: A Unified stateless =
solution for IPv4 residual Deployments (4rd-U)<br>
&gt; &gt;&gt; Document: draft-despres-softwire-4rd-u-01<br>
&gt; &gt;&gt; Duration: 20 min (incl questions, expected to be =
numerous)<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Thanks.<br>
&gt; &gt;&gt; RD<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Japan Internet Exchange<br>
&gt; &gt; MAWATARI Masataka &lt;<a =
href=3D"mailto:mawatari@jpix.ad.jp">mawatari@jpix.ad.jp</a>&gt;<br>
&gt; &gt; tel:+81-3-3243-9579<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Softwires mailing list<br>
&gt; &gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>=

&gt; &gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.=
org/mailman/listinfo/softwires</a><br>
&gt; _______________________________________________<br>
&gt; Softwires mailing list<br>
&gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/softwires">https://www.ietf.=
org/mailman/listinfo/softwires</a><br>
</p>
</blockquote></div><br></body></html>=

--Apple-Mail-33-310039790--

From internet-drafts@ietf.org  Mon Oct 31 06:28:45 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 E4AC121F8C80; Mon, 31 Oct 2011 06:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v51xG45zJHmA; Mon, 31 Oct 2011 06:28:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83DBC21F8C54; Mon, 31 Oct 2011 06:28:45 -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.62
Message-ID: <20111031132845.20471.34931.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2011 06:28:45 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-dslite-deployment-01.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, 31 Oct 2011 13:28:46 -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           : Deployment Considerations for Dual-Stack Lite
	Author(s)       : Yiu L. Lee
                          Roberta Maglione
                          Carl Williams
                          Christian Jacquenet
                          Mohamed Boucadair
	Filename        : draft-ietf-softwire-dslite-deployment-01.txt
	Pages           : 14
	Date            : 2011-10-31

   This document discusses the deployment issues and describes
   requirements for the deployment and operation of Dual-Stack Lite.
   This document describes the various deployment considerations and
   applicability of the Dual-Stack Lite architecture.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-dslite-deployment-0=
1.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-dslite-deployment-01=
.txt

From cb.list6@gmail.com  Mon Oct 31 07:34:47 2011
Return-Path: <cb.list6@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 8EC6B21F8B7F for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 07:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.717
X-Spam-Level: 
X-Spam-Status: No, score=-2.717 tagged_above=-999 required=5 tests=[AWL=0.581,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWIp19Ku-59a for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 07:34:46 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF3B21F8B74 for <softwires@ietf.org>; Mon, 31 Oct 2011 07:34:46 -0700 (PDT)
Received: by qadc10 with SMTP id c10so6384171qad.31 for <softwires@ietf.org>; Mon, 31 Oct 2011 07:34:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5LGaHFABrmsXpSL7pgfaYVOwR2JfBlGkiM7dkQB6pbA=; b=akepYD1GTndkVMnLlHw9rbVoUSk6LBzO/rMN8iM/coqxVtPe0cfUugH83lPgSdMZZM Z9bgsFkmXTXvDFcqJBDZDK65kDRmKNaYtQTHYMf57DZs8v7OXLkvqrFTGL0wU+cnfcA1 XDdX2wFMy4JWjEpcCUW4CBpMgex6fcNp0HaYA=
MIME-Version: 1.0
Received: by 10.68.38.100 with SMTP id f4mr23874551pbk.62.1320071685369; Mon, 31 Oct 2011 07:34:45 -0700 (PDT)
Received: by 10.142.230.8 with HTTP; Mon, 31 Oct 2011 07:34:45 -0700 (PDT)
Received: by 10.142.230.8 with HTTP; Mon, 31 Oct 2011 07:34:45 -0700 (PDT)
In-Reply-To: <CB5755DD-C77D-4B06-8BEB-FB30C07B10BD@laposte.net>
References: <D97FDCF6-BA79-4363-A237-58369F03C74A@laposte.net> <CAD6AjGQqCnqWq74pT6ETZz_1KerybN7fwVqaO73v8T5X=WRZHg@mail.gmail.com> <CB5755DD-C77D-4B06-8BEB-FB30C07B10BD@laposte.net>
Date: Mon, 31 Oct 2011 07:34:45 -0700
Message-ID: <CAD6AjGT=Pjou237ct8=rNGB6S6p3dVp3iFudX+bDwfxqvWPTEg@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=bcaec520f053e26d8104b09923a1
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 464XLAT - clarification? - relationship with 4rd-U
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, 31 Oct 2011 14:34:47 -0000

--bcaec520f053e26d8104b09923a1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Oct 31, 2011 6:19 AM, "R=E9mi Despr=E9s" <despres.remi@laposte.net> wrot=
e:
>
>
> Le 31 oct. 2011 =E0 14:09, Cameron Byrne a =E9crit :
>
>>
>> On Oct 31, 2011 2:25 AM, "R=E9mi Despr=E9s" <despres.remi@laposte.net> w=
rote:
>> >
>> > Hi Masataka-san,
>> >
>> > 1.
>> > Thank you for sharing your interesting experience with the JPIX trial
service based on 464XLAT.
>> > Could you, for clarification, describe in more details formats of XLAT
prefixes in this trial?
>> >
>> > 2.
>> > Objectives of 464XLAT and 4rd-U look very similar (ref
draft-despres-softwire-4rd-u-01).
>> >
>> > Indeed:
>> > - Both use "DHCPv6 prefix delegation or another method" to inform
CLAT/CEs of their IPv6 prefixes.
>> > - Both "can implement traffic engineering based on IPv4 source address
and IPv4 destination address" (a feature that, as noted in your draft, is
missing in encapsulation).
>> >
>> > OTOH, unless I miss something, 464XLAT doesn't provide incoming
connectivity of CLATs in case of shared IPv4 addresses (while 4rd-U does
provide it to CEs). In this respect 4rd-U seems functionally more complete.
>> >
>> > Thoughts?
>> >
>>
>> The difference, imho, is stateful vs stateless.
>>
>> Many operators like myself do not have enough ipv4 addresses to
incrementally grow with a stateless solution.
>
> Sharing the orders of magnitude you have to face would help to appreciate
this constraint (reminding that hosts that are dual-stack don't need as
many IPv4 ports as others).
>

I believe the draft is addressing the scenario where the host and access
network are NOT dual stack due to address constraints.

For my use-case, without exposing my own forecasts, you can probably google
for mobile device growth to understand my growth magitude, regarding
available address space ...consider it non-existent within less than 12
months... to the point that adding new stores of ipv4 address is not a
feasible input to strategic planning. Imho, I simply do not believe there
is any *strategic* value in stateless solutions.

Yes, if we completely reinvented the service to use a scheme of stateless
address sharing there may be a path, but you cannot get there from here...
at least not in my case.

I believe we have discussed this before.  I hope my thoughts clarified your
question regarding the draft.

Cb

>> It is not possible to renumber the existing network and flash everyone
into a stateless solution, so I require a more scalable solution
...starting with very few address.
>>
>> Also, given the very small amount of existing ipv4, the per port
allocations of a stateless solution are not acceptable for me.
>
> Same point as above.
>
> Regards,
> RD
>
>
>
>
>> Others may have different starting positions therefore may find
stateless helpful.
>>
>> Cb
>> >
>> > Regards,
>> > RD
>> >
>> >
>> >
>> >
>> > Le 27 oct. 2011 =E0 07:44, MAWATARI Masataka a =E9crit :
>> >
>> > > Greetings Alain-san,
>> > >
>> > >
>> > > Please let me make a presentation at IETF 82 Meeting.
>> > > I would like to introduce the following draft as a v4->v6->v4
>> > > translation experience in softwire working group.
>> > >
>> > > ---
>> > > Topic: "464XLAT: Combination of Stateful and Stateless Translation"
>> > > Draft name: draft-mawatari-softwire-464xlat-01
>> > > Time needed: 5-10minutes
>> > > Presenter's name: Masataka Mawatari
>> > > ---
>> > >
>> > > This is a simple technique to provide IPv4 access service across
>> > > IPv6 network just by using twice IPv4/IPv6 translation standardized
>> > > in [RFC6145] and [RFC6146].
>> > >
>> > > http://tools.ietf.org/html/draft-mawatari-softwire-464xlat
>> > >
>> > >
>> > > Regards,
>> > > Masataka MAWATARI
>> > >
>> > >
>> > > * On Wed, 26 Oct 2011 18:22:04 +0200
>> > > * Remi Despres <despres.remi@laposte.net> wrote:
>> > >
>> > >> Hi Alain,
>> > >>
>> > >> Can you please schedule a time slot for a 4rd-U presentation:
>> > >>
>> > >> Title        : A Unified stateless solution for IPv4 residual
Deployments (4rd-U)
>> > >> Document: draft-despres-softwire-4rd-u-01
>> > >> Duration: 20 min (incl questions, expected to be numerous)
>> > >>
>> > >> Thanks.
>> > >> RD
>> > >
>> > > --
>> > > Japan Internet Exchange
>> > > MAWATARI Masataka <mawatari@jpix.ad.jp>
>> > > tel:+81-3-3243-9579
>> > >
>> > > _______________________________________________
>> > > Softwires mailing list
>> > > Softwires@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/softwires
>> > _______________________________________________
>> > Softwires mailing list
>> > Softwires@ietf.org
>> > https://www.ietf.org/mailman/listinfo/softwires
>
>

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

<p><br>
On Oct 31, 2011 6:19 AM, &quot;R=E9mi Despr=E9s&quot; &lt;<a href=3D"mailto=
:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; Le 31 oct. 2011 =E0 14:09, Cameron Byrne a =E9crit :<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Oct 31, 2011 2:25 AM, &quot;R=E9mi Despr=E9s&quot; &lt;<a href=
=3D"mailto:despres.remi@laposte.net">despres.remi@laposte.net</a>&gt; wrote=
:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Hi Masataka-san,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; 1.<br>
&gt;&gt; &gt; Thank you for sharing your interesting experience with the JP=
IX trial service based on 464XLAT.<br>
&gt;&gt; &gt; Could you, for clarification, describe in more details format=
s of XLAT prefixes in this trial?<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; 2.<br>
&gt;&gt; &gt; Objectives of 464XLAT and 4rd-U look very similar (ref draft-=
despres-softwire-4rd-u-01).<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Indeed:<br>
&gt;&gt; &gt; - Both use &quot;DHCPv6 prefix delegation or another method&q=
uot; to inform CLAT/CEs of their IPv6 prefixes.<br>
&gt;&gt; &gt; - Both &quot;can implement traffic engineering based on IPv4 =
source address and IPv4 destination address&quot; (a feature that, as noted=
 in your draft, is missing in encapsulation).<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; OTOH, unless I miss something, 464XLAT doesn&#39;t provide in=
coming connectivity of CLATs in case of shared IPv4 addresses (while 4rd-U =
does provide it to CEs). In this respect 4rd-U seems functionally more comp=
lete.<br>

&gt;&gt; &gt;<br>
&gt;&gt; &gt; Thoughts?<br>
&gt;&gt; &gt;<br>
&gt;&gt;<br>
&gt;&gt; The difference, imho, is stateful vs stateless.<br>
&gt;&gt;<br>
&gt;&gt; Many operators like myself do not have enough ipv4 addresses to in=
crementally grow with a stateless solution.<br>
&gt;<br>
&gt; Sharing the orders of magnitude you have to face would help to appreci=
ate this constraint (reminding that hosts that are dual-stack don&#39;t nee=
d as many IPv4 ports as others).<br>
&gt;</p>
<p>I believe the draft is addressing the scenario where the host and access=
 network are NOT dual stack due to address constraints.</p>
<p>For my use-case, without exposing my own forecasts, you can probably goo=
gle for mobile device growth to understand my growth magitude, regarding av=
ailable address space ...consider it non-existent within less than 12 month=
s... to the point that adding new stores of ipv4 address is not a feasible =
input to strategic planning. Imho, I simply do not believe there is any *st=
rategic* value in stateless solutions. </p>

<p>Yes, if we completely reinvented the service to use a scheme of stateles=
s address sharing there may be a path, but you cannot get there from here..=
. at least not in my case.</p>
<p>I believe we have discussed this before.=A0 I hope my thoughts clarified=
 your question regarding the draft.</p>
<p>Cb<br></p>
<p>&gt;&gt; It is not possible to renumber the existing network and flash e=
veryone into a stateless solution, so I require a more scalable solution ..=
.starting with very few address.<br>
&gt;&gt;<br>
&gt;&gt; Also, given the very small amount of existing ipv4, the per port a=
llocations of a stateless solution are not acceptable for me.=A0<br>
&gt;<br>
&gt; Same point as above.<br>
&gt;<br>
&gt; Regards,<br>
&gt; RD<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt; Others may have different starting positions therefore may find st=
ateless helpful.<br>
&gt;&gt;<br>
&gt;&gt; Cb<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Regards,<br>
&gt;&gt; &gt; RD<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Le 27 oct. 2011 =E0 07:44, MAWATARI Masataka a =E9crit :<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &gt; Greetings Alain-san,<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; Please let me make a presentation at IETF 82 Meeting.<br=
>
&gt;&gt; &gt; &gt; I would like to introduce the following draft as a v4-&g=
t;v6-&gt;v4<br>
&gt;&gt; &gt; &gt; translation experience in softwire working group.<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; ---<br>
&gt;&gt; &gt; &gt; Topic: &quot;464XLAT: Combination of Stateful and Statel=
ess Translation&quot;<br>
&gt;&gt; &gt; &gt; Draft name: draft-mawatari-softwire-464xlat-01<br>
&gt;&gt; &gt; &gt; Time needed: 5-10minutes<br>
&gt;&gt; &gt; &gt; Presenter&#39;s name: Masataka Mawatari<br>
&gt;&gt; &gt; &gt; ---<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; This is a simple technique to provide IPv4 access servic=
e across<br>
&gt;&gt; &gt; &gt; IPv6 network just by using twice IPv4/IPv6 translation s=
tandardized<br>
&gt;&gt; &gt; &gt; in [RFC6145] and [RFC6146].<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; <a href=3D"http://tools.ietf.org/html/draft-mawatari-sof=
twire-464xlat">http://tools.ietf.org/html/draft-mawatari-softwire-464xlat</=
a><br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; Regards,<br>
&gt;&gt; &gt; &gt; Masataka MAWATARI<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; * On Wed, 26 Oct 2011 18:22:04 +0200<br>
&gt;&gt; &gt; &gt; * Remi Despres &lt;<a href=3D"mailto:despres.remi@lapost=
e.net">despres.remi@laposte.net</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt;&gt; Hi Alain,<br>
&gt;&gt; &gt; &gt;&gt;<br>
&gt;&gt; &gt; &gt;&gt; Can you please schedule a time slot for a 4rd-U pres=
entation:<br>
&gt;&gt; &gt; &gt;&gt;<br>
&gt;&gt; &gt; &gt;&gt; Title =A0 =A0 =A0 =A0: A Unified stateless solution =
for IPv4 residual Deployments (4rd-U)<br>
&gt;&gt; &gt; &gt;&gt; Document: draft-despres-softwire-4rd-u-01<br>
&gt;&gt; &gt; &gt;&gt; Duration: 20 min (incl questions, expected to be num=
erous)<br>
&gt;&gt; &gt; &gt;&gt;<br>
&gt;&gt; &gt; &gt;&gt; Thanks.<br>
&gt;&gt; &gt; &gt;&gt; RD<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; --<br>
&gt;&gt; &gt; &gt; Japan Internet Exchange<br>
&gt;&gt; &gt; &gt; MAWATARI Masataka &lt;<a href=3D"mailto:mawatari@jpix.ad=
.jp">mawatari@jpix.ad.jp</a>&gt;<br>
&gt;&gt; &gt; &gt; tel:+81-3-3243-9579<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; _______________________________________________<br>
&gt;&gt; &gt; &gt; Softwires mailing list<br>
&gt;&gt; &gt; &gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org=
</a><br>
&gt;&gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwir=
es">https://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;&gt; &gt; _______________________________________________<br>
&gt;&gt; &gt; Softwires mailing list<br>
&gt;&gt; &gt; <a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><=
br>
&gt;&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/softwires">h=
ttps://www.ietf.org/mailman/listinfo/softwires</a><br>
&gt;<br>
&gt;<br>
</p>

--bcaec520f053e26d8104b09923a1--

From internet-drafts@ietf.org  Mon Oct 31 12:29: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 73FA41F0C67; Mon, 31 Oct 2011 12:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMTvdncD368W; Mon, 31 Oct 2011 12:29:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AE41F0C3C; Mon, 31 Oct 2011 12:29:09 -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.62
Message-ID: <20111031192909.23485.52653.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2011 12:29:09 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-dslite-multicast-01.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, 31 Oct 2011 19:29:10 -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           : Multicast Extensions to DS-Lite Technique in Broadband D=
eployments
	Author(s)       : Qian Wang
                          Jacni Qin
                          Mohamed Boucadair
                          Christian Jacquenet
                          Yiu L. Lee
	Filename        : draft-ietf-softwire-dslite-multicast-01.txt
	Pages           : 18
	Date            : 2011-10-31

   This document specifies a solution for the delivery of multicast
   service offerings to DS-Lite serviced customers.  The proposed
   solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme
   and uses the IPv6 multicast distribution tree to deliver IPv4
   multicast traffic over an IPv6 multicast-enabled network.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-dslite-multicast-01=
.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-dslite-multicast-01.=
txt

From mawatari@jpix.ad.jp  Mon Oct 31 23:03:27 2011
Return-Path: <mawatari@jpix.ad.jp>
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 24BF411E8138 for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 23:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.534
X-Spam-Level: **
X-Spam-Status: No, score=2.534 tagged_above=-999 required=5 tests=[AWL=2.624,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aVChJh5L30l for <softwires@ietfa.amsl.com>; Mon, 31 Oct 2011 23:03:26 -0700 (PDT)
Received: from mx20.jpix.ad.jp (mx20.jpix.ad.jp [210.171.225.78]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5B811E812F for <softwires@ietf.org>; Mon, 31 Oct 2011 23:03:25 -0700 (PDT)
Received: from [10.10.31.134] (eth3-1-bb-fw-34.jpix.ad.jp [210.171.226.102]) by mx20.jpix.ad.jp (Postfix) with ESMTP id 250DAFC021; Tue,  1 Nov 2011 15:03:24 +0900 (JST)
Date: Tue, 01 Nov 2011 15:03:24 +0900
From: MAWATARI Masataka <mawatari@jpix.ad.jp>
To: despres.remi@laposte.net
In-Reply-To: <D97FDCF6-BA79-4363-A237-58369F03C74A@laposte.net>
References: <D97FDCF6-BA79-4363-A237-58369F03C74A@laposte.net>
Message-Id: <20111101150324.F7BF.8FE1F57E@jpix.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.57.03 [ja]
Cc: softwires@ietf.org
Subject: Re: [Softwires] 464XLAT - clarification? - relationship with 4rd-U
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, 01 Nov 2011 06:03:27 -0000

Dear Remi-san,

Thank you for your comments. Please see inline below.

* On Mon, 31 Oct 2011 10:25:03 +0100
* Remi Despres <despres.remi@laposte.net> wrote:

> Hi Masataka-san,
> 
> 1.
> Thank you for sharing your interesting experience with the JPIX trial service based on 464XLAT.
> Could you, for clarification, describe in more details formats of XLAT prefixes in this trial? 

IPv6 address for translation have IPv4 address embedded in the
low-order 32 bits of the IPv6 address, as you well know.
http://tools.ietf.org/html/draft-mawatari-softwire-464xlat-02#section-6.1

I might not understand what you want to know.
I described 464XLAT address translation chart here.

                                        source IPv4 address
                                        +-----------------------------+
                                        | IPv4 [global] (32bit)       |
                                        | [assigned to IPv4 pool@PLAT]|
                             +--------+ +-----------------------------+
                             |  IPv4  | destination IPv4 address
                             | server | +-----------------------------+
                             +--------+ | IPv4 [global] (32bit)       |
                                 ^      + [assigned to IPv4 server]   |
                                 |      +-----------------------------+
                             +--------+
                             |  PLAT  | Stateful XLATE (v4:v6=1:n)
                             +--------+
                                 ^
                                 |
source IPv6 address         (IPv6 cloud)
 +--------------------------------------+-----------------------------+
 |  XLAT prefix for src (96bit)         | IPv4 [private] (32bit)      |
 |  [assigned to each consumer of ISP]  | [assigned to IPv4 client]   |
 +--------------------------------------+-----------------------------+
destination IPv6 address
 +--------------------------------------+-----------------------------+
 |  XLAT prefix for dst (96bit)         | IPv4 [global] (32bit)       |
 |  [assigned to PLAT]                  | [assiend to IPv4 server]    |
 +--------------------------------------+-----------------------------+
                            (IPv6 cloud)
                                 ^
                                 |
                             +--------+
                             |  CLAT  | Stateless XLATE (v4:v6=1:1)
                             +--------+
                                 ^      source IPv4 address
                                 |      +-----------------------------+
                             +--------+ | IPv4 [private] (32bit)      |
                             |  IPv4  | | [assigned to IPv4 client]   |
                             | client | +-----------------------------+
                             +--------+ destination IPv4 address
                                        +-----------------------------+
                                        | IPv4 [global] (32bit)       |
                                        + [assigned to IPv4 server]   |
                                        +-----------------------------+


additional reference (sorry, a bit outdated)
http://www.apricot.net/apricot2011/media/Masataka_Mawatari_IPv6v4_Exchange_Service_for_sharing_IPv4_address.pdf


> 2.
> Objectives of 464XLAT and 4rd-U look very similar (ref draft-despres-softwire-4rd-u-01).
> 
> Indeed:
> - Both use "DHCPv6 prefix delegation or another method" to inform CLAT/CEs of their IPv6 prefixes.
> - Both "can implement traffic engineering based on IPv4 source address and IPv4 destination address" (a feature that, as noted in your draft, is missing in encapsulation).
> 
> OTOH, unless I miss something, 464XLAT doesn't provide incoming connectivity of CLATs in case of shared IPv4 addresses (while 4rd-U does provide it to CEs). In this respect 4rd-U seems functionally more complete.
> 
> Thoughts?
> 
> 
> Regards,
> RD


Kind Regards,
Masataka MAWATARI


-- 
Japan Internet Exchange
MAWATARI Masataka <mawatari@jpix.ad.jp>
tel:+81-3-3243-9579

