
From despres.remi@laposte.net  Fri Mar  1 05:16:57 2013
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 1089821F8C87 for <softwires@ietfa.amsl.com>; Fri,  1 Mar 2013 05:16:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxkMA6+7a4ir for <softwires@ietfa.amsl.com>; Fri,  1 Mar 2013 05:16:55 -0800 (PST)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.13]) by ietfa.amsl.com (Postfix) with ESMTP id E27D821F8C5C for <softwires@ietf.org>; Fri,  1 Mar 2013 05:16:54 -0800 (PST)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2217.sfr.fr (SMTP Server) with ESMTP id 17EF370000FC; Fri,  1 Mar 2013 14:16:53 +0100 (CET)
Received: from [192.168.0.21] (unknown [78.193.136.169]) by msfrf2217.sfr.fr (SMTP Server) with ESMTP id 28A8E70000FA; Fri,  1 Mar 2013 14:16:52 +0100 (CET)
X-SFR-UUID: 20130301131652166.28A8E70000FA@msfrf2217.sfr.fr
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: =?iso-8859-1?q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CAH3bfACWgMcfhdYq=5K6=YXKwhtrLmr6vrQJPoDXkgX8doYb_w@mail.gmail.com>
Date: Fri, 1 Mar 2013 14:16:51 +0100
Message-Id: <34C3F453-319D-4201-B4AF-CED608444D7D@laposte.net>
References: <20130225120814.5403.6554.idtracker@ietfa.amsl.com> <CAFUBMqU5D5kWrnRAEdi2DBbrk0c+k_LRQyPe1jJc9k6smR27VA@mail.gmail.com> <CAH3bfACWgMcfhdYq=5K6=YXKwhtrLmr6vrQJPoDXkgX8doYb_w@mail.gmail.com>
To: Softwires WG <softwires@ietf.org>
X-Mailer: Apple Mail (2.1499)
Content-Type: multipart/alternative; boundary="Apple-Mail=_CA652504-786C-490A-802F-4171669A947C"
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>, Ole Troan <ot@cisco.com>
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-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: Fri, 01 Mar 2013 13:16:57 -0000

--Apple-Mail=_CA652504-786C-490A-802F-4171669A947C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

2013-02-28  15:34, Qiong <bingxuere@gmail.com> :

> ...
> Currently, the title of this draft is still MAP only, as we have not =
found a good term to call MAP-E, MAP-T and 4rd-u. So we would like to =
get advice from the working group to address this problem.

Thanks to Qiong for raising this question in a more general context than =
that of MAP-E issue # 18 =
(http://trac.tools.ietf.org/wg/softwire/trac/ticket/18)

AFAIK, Alain's intention before he left was to move from =
MAP-E/MAP-T/4rd-U to 4rd-E/4rd-T/4rd-H (with H for Hybrid). IMHO, this =
does make sense because:
- "IPv4 Residual Deployment" better reflects the solution scope than =
"Address and Port Mapping".
- This nicely conveys that there is commonality with 6rd.
=20
The fact that "MAP" has been used for some time for both MAP-E and MAP-T =
can be considered an impediment, but:
- Now is a good time for making a consistent choice for the future.
- Editorial updates for this are essentially trivial.
NB: The original acronym for MAP-E was 4rd (and that of MAP-T was =
4via6).

This is my 2-cents contribution on this naming issue (after so many =
contributions to build and improve the solution).=20

Best regards,
RD


--Apple-Mail=_CA652504-786C-490A-802F-4171669A947C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div =
style=3D"margin: 0px; font-size: 12px; "><div style=3D"margin: 0px; =
">2013-02-28 &nbsp;15:34, Qiong &lt;<a =
href=3D"mailto:bingxuere@gmail.com">bingxuere@gmail.com</a>&gt; =
:</div></div><div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div>...</div><div style=3D"">Currently, =
the title of this draft is still MAP only, as we have not found a good =
term to call&nbsp;MAP-E, MAP-T and 4rd-u. So we would like to get advice =
from the working group to address this =
problem.</div></div></blockquote></div><br><div><div style=3D"margin: =
0px; font-size: 12px; ">Thanks to Qiong for raising this question in a =
more general context than that of MAP-E issue # 18 (<a =
href=3D"http://trac.tools.ietf.org/wg/softwire/trac/ticket/18">http://trac=
.tools.ietf.org/wg/softwire/trac/ticket/18</a>)</div><div style=3D"margin:=
 0px; font-size: 12px; min-height: 14px; "><br></div><div style=3D"margin:=
 0px; font-size: 12px; ">AFAIK, Alain's intention before he left was to =
move from MAP-E/MAP-T/4rd-U to 4rd-E/4rd-T/4rd-H (with H for =
Hybrid).&nbsp;IMHO, this does make sense because:</div><div =
style=3D"font-size: 12px; margin: 0px; ">- "IPv4 Residual Deployment" =
better reflects the solution scope than "Address and Port =
Mapping".</div><div style=3D"margin: 0px; font-size: 12px; ">- This =
nicely conveys that there is commonality with 6rd.</div><div =
style=3D"margin: 0px; font-size: 12px; ">&nbsp;</div><div style=3D"margin:=
 0px; font-size: 12px; ">The fact that "MAP" has been used for some =
time&nbsp;for both MAP-E and MAP-T can be considered an impediment, =
but:</div><div style=3D"margin: 0px; font-size: 12px; ">- Now is a good =
time for making a consistent choice for the future.</div><div =
style=3D"margin: 0px; font-size: 12px; ">- Editorial updates for this =
are essentially trivial.</div><div style=3D"margin: 0px; font-size: =
12px; ">NB:&nbsp;The original acronym for MAP-E was 4rd (and that of =
MAP-T was 4via6).</div><div style=3D"margin: 0px; font-size: 12px; =
min-height: 14px; "><br></div><div style=3D"margin: 0px; font-size: =
12px; ">This is my 2-cents contribution on this naming issue (after so =
many contributions to build and improve the solution).&nbsp;</div><div =
style=3D"margin: 0px; font-size: 12px; "><br></div><div style=3D"margin: =
0px; font-size: 12px; min-height: 14px; ">Best regards,</div><div =
style=3D"margin: 0px; font-size: 12px; =
">RD</div></div><div><br></div></body></html>=

--Apple-Mail=_CA652504-786C-490A-802F-4171669A947C--

From despres.remi@laposte.net  Fri Mar  1 06:21:21 2013
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 6701221F9182 for <softwires@ietfa.amsl.com>; Fri,  1 Mar 2013 06:21:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2VSfb1Cf5sV2 for <softwires@ietfa.amsl.com>; Fri,  1 Mar 2013 06:21:20 -0800 (PST)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.82]) by ietfa.amsl.com (Postfix) with ESMTP id DB3AE21F9178 for <softwires@ietf.org>; Fri,  1 Mar 2013 06:21:19 -0800 (PST)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2409.sfr.fr (SMTP Server) with ESMTP id BD3E97000122; Fri,  1 Mar 2013 15:21:18 +0100 (CET)
Received: from [192.168.0.21] (unknown [78.193.136.169]) by msfrf2409.sfr.fr (SMTP Server) with ESMTP id 6278C700011E; Fri,  1 Mar 2013 15:21:17 +0100 (CET)
X-SFR-UUID: 20130301142118403.6278C700011E@msfrf2409.sfr.fr
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: =?iso-8859-1?q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <34C3F453-319D-4201-B4AF-CED608444D7D@laposte.net>
Date: Fri, 1 Mar 2013 15:21:17 +0100
Message-Id: <FA2F2707-03BA-49A3-B085-68FC3068CBD4@laposte.net>
References: <20130225120814.5403.6554.idtracker@ietfa.amsl.com> <CAFUBMqU5D5kWrnRAEdi2DBbrk0c+k_LRQyPe1jJc9k6smR27VA@mail.gmail.com> <CAH3bfACWgMcfhdYq=5K6=YXKwhtrLmr6vrQJPoDXkgX8doYb_w@mail.gmail.com> <34C3F453-319D-4201-B4AF-CED608444D7D@laposte.net>
To: Qiong Sun <sunqiong@ctbri.com.cn>, Suresh Krishnan <suresh.krishnan@ericsson.com>, Alain Durand <adurand@juniper.net>
X-Mailer: Apple Mail (2.1499)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-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: Fri, 01 Mar 2013 14:21:21 -0000

You were in the CC list of the mail below but, for some reason I don't =
know, your names disappeared  in the mail forwarded to the WG, and =
stored in the archive.
Sorry for that.
RD


Le 2013-03-01 =E0 14:16, R=E9mi Despr=E9s <despres.remi@laposte.net> a =
=E9crit :

> 2013-02-28  15:34, Qiong <bingxuere@gmail.com> :
>=20
>> ...
>> Currently, the title of this draft is still MAP only, as we have not =
found a good term to call MAP-E, MAP-T and 4rd-u. So we would like to =
get advice from the working group to address this problem.
>=20
> Thanks to Qiong for raising this question in a more general context =
than that of MAP-E issue # 18 =
(http://trac.tools.ietf.org/wg/softwire/trac/ticket/18)
>=20
> AFAIK, Alain's intention before he left was to move from =
MAP-E/MAP-T/4rd-U to 4rd-E/4rd-T/4rd-H (with H for Hybrid). IMHO, this =
does make sense because:
> - "IPv4 Residual Deployment" better reflects the solution scope than =
"Address and Port Mapping".
> - This nicely conveys that there is commonality with 6rd.
> =20
> The fact that "MAP" has been used for some time for both MAP-E and =
MAP-T can be considered an impediment, but:
> - Now is a good time for making a consistent choice for the future.
> - Editorial updates for this are essentially trivial.
> NB: The original acronym for MAP-E was 4rd (and that of MAP-T was =
4via6).
>=20
> This is my 2-cents contribution on this naming issue (after so many =
contributions to build and improve the solution).=20
>=20
> Best regards,
> RD
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From sarikaya2012@gmail.com  Fri Mar  1 10:00:51 2013
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 38C7D21F90F9 for <softwires@ietfa.amsl.com>; Fri,  1 Mar 2013 10:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.382
X-Spam-Level: 
X-Spam-Status: No, score=-3.382 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XsGtYl8SulX for <softwires@ietfa.amsl.com>; Fri,  1 Mar 2013 10:00:50 -0800 (PST)
Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169]) by ietfa.amsl.com (Postfix) with ESMTP id EF3BE21F9034 for <softwires@ietf.org>; Fri,  1 Mar 2013 10:00:49 -0800 (PST)
Received: by mail-lb0-f169.google.com with SMTP id m4so2472058lbo.0 for <softwires@ietf.org>; Fri, 01 Mar 2013 10:00:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dp91FI/nq+RlmkASgDclbsSdnOdUFyME8JhmEZxnKhI=; b=VowlyXxz8PWNHFlqwRx2CnYuREQEyBaSXRBw9wwb4xj33kewTdxL8l0Wk1oax952OZ rouhBgvMw06D7tU0xM9KB4lDn+yiwXaSC8Sx24vn187gYWwZkeYEAxFKy6fEAzg4PqQe kKnrju8Iq92VfGZ3nt4a9ZhsPgVPrCGejSQAmp6587ELCo5wGWFHjvngkvhWGlBfjcML UMmFxatpw4OjdpkY2FQO4S5ssa5Fq1qHC45/OgvQzCkIB9EHQyE7F0wMcU37EbvJlfx6 OqYqZhQBWdHH4q37LSTRJAPZzNcr/wQWSUp1W0ndY+TySLYVEGTXT/LN/UnxqWx7XFJb Lt7g==
MIME-Version: 1.0
X-Received: by 10.112.87.66 with SMTP id v2mr1103929lbz.130.1362160848861; Fri, 01 Mar 2013 10:00:48 -0800 (PST)
Received: by 10.114.28.168 with HTTP; Fri, 1 Mar 2013 10:00:48 -0800 (PST)
In-Reply-To: <34C3F453-319D-4201-B4AF-CED608444D7D@laposte.net>
References: <20130225120814.5403.6554.idtracker@ietfa.amsl.com> <CAFUBMqU5D5kWrnRAEdi2DBbrk0c+k_LRQyPe1jJc9k6smR27VA@mail.gmail.com> <CAH3bfACWgMcfhdYq=5K6=YXKwhtrLmr6vrQJPoDXkgX8doYb_w@mail.gmail.com> <34C3F453-319D-4201-B4AF-CED608444D7D@laposte.net>
Date: Fri, 1 Mar 2013 12:00:48 -0600
Message-ID: <CAC8QAcfhmVxN9=OcTS1Kh0d-=3_=dz-nwkf-eNTryvSorU9L9A@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary=f46d040169ff8604e804d6e0c98e
Cc: Softwires WG <softwires@ietf.org>, Ole Troan <ot@cisco.com>, Yong Cui <cuiyong@tsinghua.edu.cn>
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-deployment-01.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: Fri, 01 Mar 2013 18:00:51 -0000

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

On Fri, Mar 1, 2013 at 7:16 AM, R=E9mi Despr=E9s <despres.remi@laposte.net>=
wrote:

> 2013-02-28  15:34, Qiong <bingxuere@gmail.com> :
>
> ...
> Currently, the title of this draft is still MAP only, as we have not foun=
d
> a good term to call MAP-E, MAP-T and 4rd-u. So we would like to get advic=
e
> from the working group to address this problem.
>
>
> Thanks to Qiong for raising this question in a more general context than
> that of MAP-E issue # 18 (
> http://trac.tools.ietf.org/wg/softwire/trac/ticket/18)
>
> AFAIK, Alain's intention before he left was to move from MAP-E/MAP-T/4rd-=
U
> to 4rd-E/4rd-T/4rd-H (with H for Hybrid). IMHO, this does make sense
> because:
> - "IPv4 Residual Deployment" better reflects the solution scope than
> "Address and Port Mapping".
> - This nicely conveys that there is commonality with 6rd.
>
> The fact that "MAP" has been used for some time for both MAP-E and MAP-T
> can be considered an impediment, but:
> - Now is a good time for making a consistent choice for the future.
> - Editorial updates for this are essentially trivial.
> NB: The original acronym for MAP-E was 4rd (and that of MAP-T was 4via6).
>
> This is my 2-cents contribution on this naming issue (after so many
> contributions to build and improve the solution).
>
>
I support this. I had the same problem in my multicast draft.
I think that using a unifying name like 4rd would be helpful.

Behcet

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

<br><br><div class=3D"gmail_quote">On Fri, Mar 1, 2013 at 7:16 AM, R=E9mi D=
espr=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><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 style=3D"margin:0px;font-size:12px=
"><div style=3D"margin:0px"><a href=3D"tel:2013-02-28%20%C2%A015" value=3D"=
+12013022815" target=3D"_blank">2013-02-28 =A015</a>:34, Qiong &lt;<a href=
=3D"mailto:bingxuere@gmail.com" target=3D"_blank">bingxuere@gmail.com</a>&g=
t; :</div>
</div><div><br><blockquote type=3D"cite"><div dir=3D"ltr"><div>...</div><di=
v class=3D"im"><div>Currently, the title of this draft is still MAP only, a=
s we have not found a good term to call=A0MAP-E, MAP-T and 4rd-u. So we wou=
ld like to get advice from the working group to address this problem.</div>
</div></div></blockquote></div><br><div><div style=3D"margin:0px;font-size:=
12px">Thanks to Qiong for raising this question in a more general context t=
han that of MAP-E issue # 18 (<a href=3D"http://trac.tools.ietf.org/wg/soft=
wire/trac/ticket/18" target=3D"_blank">http://trac.tools.ietf.org/wg/softwi=
re/trac/ticket/18</a>)</div>
<div style=3D"margin:0px;font-size:12px;min-height:14px"><br></div><div sty=
le=3D"margin:0px;font-size:12px">AFAIK, Alain&#39;s intention before he lef=
t was to move from MAP-E/MAP-T/4rd-U to 4rd-E/4rd-T/4rd-H (with H for Hybri=
d).=A0IMHO, this does make sense because:</div>
<div style=3D"font-size:12px;margin:0px">- &quot;IPv4 Residual Deployment&q=
uot; better reflects the solution scope than &quot;Address and Port Mapping=
&quot;.</div><div style=3D"margin:0px;font-size:12px">- This nicely conveys=
 that there is commonality with 6rd.</div>
<div style=3D"margin:0px;font-size:12px">=A0</div><div style=3D"margin:0px;=
font-size:12px">The fact that &quot;MAP&quot; has been used for some time=
=A0for both MAP-E and MAP-T can be considered an impediment, but:</div><div=
 style=3D"margin:0px;font-size:12px">
- Now is a good time for making a consistent choice for the future.</div><d=
iv style=3D"margin:0px;font-size:12px">- Editorial updates for this are ess=
entially trivial.</div><div style=3D"margin:0px;font-size:12px">NB:=A0The o=
riginal acronym for MAP-E was 4rd (and that of MAP-T was 4via6).</div>
<div style=3D"margin:0px;font-size:12px;min-height:14px"><br></div><div sty=
le=3D"margin:0px;font-size:12px">This is my 2-cents contribution on this na=
ming issue (after so many contributions to build and improve the solution).=
=A0</div>
<div style=3D"margin:0px;font-size:12px"><br></div></div></div></blockquote=
><div><br>I support this. I had the same problem in my multicast draft.<br>=
I think that using a unifying name like 4rd would be helpful.<br><br>Behcet=
 <br>
</div></div><br>

--f46d040169ff8604e804d6e0c98e--

From suresh.krishnan@ericsson.com  Sun Mar  3 22:56:51 2013
Return-Path: <suresh.krishnan@ericsson.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 45E2721F859B for <softwires@ietfa.amsl.com>; Sun,  3 Mar 2013 22:56:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[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 xeJNcomcNNTi for <softwires@ietfa.amsl.com>; Sun,  3 Mar 2013 22:56:50 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id C957121F859D for <softwires@ietf.org>; Sun,  3 Mar 2013 22:56:47 -0800 (PST)
X-AuditID: c618062d-b7f0d6d00000097e-b8-513445ae34fd
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 7A.60.02430.EA544315; Mon,  4 Mar 2013 07:56:46 +0100 (CET)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC007.ericsson.se (147.117.188.93) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 4 Mar 2013 01:56:46 -0500
Received: from [164.48.125.52] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 4 Mar 2013 01:56:45 -0500
Message-ID: <5134450F.7020406@ericsson.com>
Date: Mon, 4 Mar 2013 01:54:07 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Softwires WG <softwires@ietf.org>, <draft-ietf-softwire-mesh-mib@tools.ietf.org>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFJMWRmVeSWpSXmKPExsUyuXRPrO46V5NAg8PrrCxWtixgszi8bCuT A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJXR9W4NS8FU1or3Z48wNjDOZeli5OSQEDCR WPviIDOELSZx4d56ti5GLg4hgSOMEgdnbWKGcHYzSjycehwqs4VRYumNnewgLbwC2hJrbt0D s1kEVCR6H88AG8UGNHbDzs9MILaoQJhE7+tzjBD1ghInZz4BWy0CFL/26zqYLSxgKdF17ymQ zQF0hrjEmjccIGFmAT2JKVdbGCFseYntb+eAjRcS0JTYuuY76wRGgVlIps5C0jILScsCRuZV jBylxalluelGBpsYgeF3TIJNdwfjnpeWhxilOViUxHmDXC8ECAmkJ5akZqemFqQWxReV5qQW H2Jk4uCUamBs2FwjZSPZ2BggdERg+fWpGz3W3vVrnb/u+/67t7Q+pb7acL2v2PaYeZ5gZl1B 6d7Q+jC1+TlP3i84JVJpOeXbBstDMpd2iXf0+8Y9WtITttr9o0v8naknc+Z9W7yzOfI9hz83 D7OVqMWa0+pfxXabGO6VLppiUn56YtCv8H+qS5UfM2wvWuKmxFKckWioxVxUnAgAP3qQJw0C AAA=
Subject: [Softwires] Chair review of  draft-ietf-softwire-mesh-mib-02
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, 04 Mar 2013 06:56:51 -0000

Hi authors,
  I reviewed this document and it has some minor MIB issues (warnings)
that need to be fixed before advancement. Specifically

* swmEncapsEIPDst should be not-accessible (as it is index element of
swmEncapsEntry)
* swmEncapsEIPMask should be not-accessible (as it is index element of
swmEncapsEntry)
* swmBGPNeighborInetAddress should be not-accessible (as it is index
element of swmBGPNeighborEntry)
* Please check if all the InetAddress objects have an accompanying
(preceding) InetAdressType object.

Please fix these issues when you get a chance and submit a new revision
so that we can advance this document.

Thanks
Suresh


From pengwu.thu@gmail.com  Mon Mar  4 01:57:27 2013
Return-Path: <pengwu.thu@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 865FE21F8948 for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 01:57:27 -0800 (PST)
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 MMDn4swe0htM for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 01:57:27 -0800 (PST)
Received: from mail-oa0-f47.google.com (mail-oa0-f47.google.com [209.85.219.47]) by ietfa.amsl.com (Postfix) with ESMTP id 0C88F21F8945 for <softwires@ietf.org>; Mon,  4 Mar 2013 01:57:26 -0800 (PST)
Received: by mail-oa0-f47.google.com with SMTP id o17so8927528oag.34 for <softwires@ietf.org>; Mon, 04 Mar 2013 01:57:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=GKYvCCY9oFjVeo/Zhm3mzgjzRDWyvbnNtRticgI9RyA=; b=aTBWgtdtN4gxyWyK+LbwbaFTU1lvurP6hLgRRPk9+Mdt2xLp/23z+YYrUFrNm1GJKr jlFV9vL8Jl+NRgepcb0fQzJ1jxXdDtxkjXDfyt6qAItXG7FRNkC2D/7gsPgKvAjolzgK gyZyjiNFc9MG+pxqdJM1IqYLF0kMAXn/upxJgIppXHWb1YeMSyJYulfYITGz+Ivmm1hw ShARNAZ5Ek4D9UaM5ZJmGF2NuyNw37QquupC5ihJ2ESJqkM/K+cxGPCk3KbIAM8WCrlp MJ5RGYfTFUOrFe5vOfv7g2uf5kYITm/aOkMQNBfVAS1MYSh1Qc1GrNcYvq80DQnGXhgJ t0sg==
MIME-Version: 1.0
X-Received: by 10.60.169.212 with SMTP id ag20mr14843650oec.102.1362391046676;  Mon, 04 Mar 2013 01:57:26 -0800 (PST)
Received: by 10.60.146.170 with HTTP; Mon, 4 Mar 2013 01:57:26 -0800 (PST)
In-Reply-To: <5134450F.7020406@ericsson.com>
References: <5134450F.7020406@ericsson.com>
Date: Mon, 4 Mar 2013 17:57:26 +0800
Message-ID: <CAC16W0BrmjdM-uscnT=PO8fku+ryWPngH65s=yYaBaTpJGaXxA@mail.gmail.com>
From: Peng Wu <pengwu.thu@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Softwires WG <softwires@ietf.org>, draft-ietf-softwire-mesh-mib@tools.ietf.org
Subject: Re: [Softwires] Chair review of draft-ietf-softwire-mesh-mib-02
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, 04 Mar 2013 09:57:27 -0000

Dear Suresh,

Many thanks for your valuable comments on the draft.
We will revise the document and fix all the issues. Once the
submission system is available again, we will submit a new version
asap.

Best Regards,
Peng

On Mon, Mar 4, 2013 at 2:54 PM, Suresh Krishnan
<suresh.krishnan@ericsson.com> wrote:
> Hi authors,
>   I reviewed this document and it has some minor MIB issues (warnings)
> that need to be fixed before advancement. Specifically
>
> * swmEncapsEIPDst should be not-accessible (as it is index element of
> swmEncapsEntry)
> * swmEncapsEIPMask should be not-accessible (as it is index element of
> swmEncapsEntry)
> * swmBGPNeighborInetAddress should be not-accessible (as it is index
> element of swmBGPNeighborEntry)
> * Please check if all the InetAddress objects have an accompanying
> (preceding) InetAdressType object.
>
> Please fix these issues when you get a chance and submit a new revision
> so that we can advance this document.
>
> Thanks
> Suresh
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From shtsuchi@cisco.com  Mon Mar  4 09:09:01 2013
Return-Path: <shtsuchi@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 69FE821F8630 for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 09:09:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.349
X-Spam-Level: 
X-Spam-Status: No, score=-9.349 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, J_CHICKENPOX_61=0.6, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_HI=-8]
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 3N6PM4qMZJpM for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 09:08:57 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id B1D4421F8621 for <softwires@ietf.org>; Mon,  4 Mar 2013 09:08:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3418; q=dns/txt; s=iport; t=1362416936; x=1363626536; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=V7iQ0cleAIiGpZ8HAiV7XBN2o2pSfJItRl7nUVT2vc0=; b=WUo+tkerYPMcqBnLkV98DbfNonSa1xyZQu2BjJbY+fttUXvZl1FlSr5r tnJ2hddwgmKu3Qd9b1cpXNXbkAsvN4hOpIOUgy2+M1mCuRZlVkVqSkQY7 HKCSXgI4sVl6DJlbz+qmsPRTxqivt0EeX3cU1xjomqQDs5StRcMGqXoNL o=;
X-IronPort-AV: E=Sophos;i="4.84,781,1355097600"; d="scan'208";a="26697528"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 04 Mar 2013 17:08:52 +0000
Received: from tky-shtsuchi-8913.cisco.com (tky-shtsuchi-8913.cisco.com [10.71.44.84]) by bgl-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r24H8qJm005634; Mon, 4 Mar 2013 17:08:52 GMT
Message-ID: <5134D525.4070601@cisco.com>
Date: Tue, 05 Mar 2013 02:08:53 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: leo.liubing@huawei.com
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6D882D@nkgeml506-mbx.china.huawei.com> <87C876FC-6B2D-4570-8B7E-CC6D5FC73C8C@cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6D8A7F@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6D8A7F@nkgeml506-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org
Subject: Re: [Softwires] MAP-MIB request for comments
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, 04 Mar 2013 17:09:01 -0000

Bing
I agree ISP would like to know status of MAP deployment/usage sometimes.
But I can not agree that MIB provides this function.

I think this MIB targets provisioning/monitoring for CE/BR.
If so ,is it enough to check MIB object of CE ISP to know MAP deployment?

And I don't know why this oid needs for MAP-E.
mapStatisticConnections
mapStatisticSpecificIP
mapTunnelNumAlarm
mapBRPortUsageOfSpecificIpAlarm

Some static could be provided by usig IP-MIB(RFC4293) and IP-FORWARD-MIB(RFC4292).
But we may need new object for MAP-E security check statics because MAP-E checks consistency of IPv4/IPv6 src address.
Because most of vendors already supports security mechanism,and they has static counter for  inconsistency of packet.
http://tools.ietf.org/html/draft-janog-softwire-report-01#section-2.2
The counter would be new object for MAP/6rd.

If it is needed,I will let's add our 6rd mib also.

Regards,
-Shishio





(2013/02/08 15:56), Liubing (Leo) wrote:
> Hi, Ole
> 
> Thanks for your quick reply.
> 
> In order to do the statistics, the BR need a bit more codes to extract the CE IPv6 addresses when doing de-encapsulation.
> That is what we said in the last mail the operation might slightly impact the performance, so we defined this MIB function as optional.
> 
> All the best,
> Bing
> 
>> -----Original Message-----
>> From: Ole Troan [mailto:ot@cisco.com]
>> Sent: Thursday, February 07, 2013 8:49 PM
>> To: Liubing (Leo)
>> Cc: Softwires WG; townsley@cisco.com; Yong Cui
>> Subject: Re: [Softwires] MAP-MIB request for comments
>>
>>> The MAP-MIB draft has been updated as -03 version.
>>>
>>> In IETF85@Atlanta, we had a brief discussion, and the main comment was
>> from Mark Townsley. He pointed out that the tunnel table defined in the
>> draft would make the BR recording every CEs' addresses connected to it. This
>> operation would somewhat counterbalance the benefit of stateless design.
>>> Basically, Mark's comment is a real issue, but not that serious. The tunnel
>> table needs the translation/encapsulation application to provide CE address
>> to the MIB agent, that might slightly impact the forwarding performance,
>> but it is far from the weight of "stateful", because the the BR tunnel table is
>> not for real-time look up, it is just a kind of logging. In the worst situation,
>> even the MIB crash, the packet forwarding won't be bothered.
>>>
>>> The purpose we defined a tunnel table is to add some statistics of CE
>> connecting BR. For example, the ISP might want to know how many/what
>> CEs had been connected to a certain BR.  This might be useful for service
>> analysis and management, e.g. to static percentage of MAP enabled and the
>> traffic, so that the ISP could learn the status of MAP deployment/usage, then
>> might make some policies.
>>> Considering the tunnel table might still more or less bring some additional
>> complexity, we defined it as an optional object in the MIB. We defined two
>> map-MIB-Compliance, one is basic compliance only containing the rule table,
>> the other is full compliance containing rule table and tunnel table.
>>
>> how is the BR supposed to learn the CE addresses?
>>
>> cheers,
>> Ole
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
> .
> 

.


From leo.liubing@huawei.com  Mon Mar  4 18:12:04 2013
Return-Path: <leo.liubing@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 3730211E80EE for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 18:12:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.759
X-Spam-Level: 
X-Spam-Status: No, score=-5.759 tagged_above=-999 required=5 tests=[AWL=-0.360, BAYES_00=-2.599, J_CHICKENPOX_61=0.6, J_CHICKENPOX_93=0.6, 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 iSARUl4E-IEI for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 18:12:03 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E882411E80E8 for <softwires@ietf.org>; Mon,  4 Mar 2013 18:12:02 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APA66522; Tue, 05 Mar 2013 02:12:01 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Mar 2013 02:11:54 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Mar 2013 02:12:00 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.42]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.01.0323.007; Tue, 5 Mar 2013 10:11:49 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Shishio Tsuchiya <shtsuchi@cisco.com>
Thread-Topic: [Softwires] MAP-MIB request for comments
Thread-Index: AQHOBTAtcJOhmhsaCEqJm/2ZvK5A3pht0n+AgAGyB7CAJeDigIABGoAw
Date: Tue, 5 Mar 2013 02:11:48 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6E6176@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6D882D@nkgeml506-mbx.china.huawei.com> <87C876FC-6B2D-4570-8B7E-CC6D5FC73C8C@cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6D8A7F@nkgeml506-mbx.china.huawei.com> <5134D525.4070601@cisco.com>
In-Reply-To: <5134D525.4070601@cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] MAP-MIB request for comments
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, 05 Mar 2013 02:12:04 -0000

Hi, Shishio

Thanks for your review. Please see inline.

> -----Original Message-----
> From: Shishio Tsuchiya [mailto:shtsuchi@cisco.com]
> Sent: Tuesday, March 05, 2013 1:09 AM
> To: Liubing (Leo)
> Cc: shtsuchi@cisco.com; softwires@ietf.org
> Subject: Re: [Softwires] MAP-MIB request for comments
>=20
> Bing
> I agree ISP would like to know status of MAP deployment/usage sometimes.
> But I can not agree that MIB provides this function.
>=20
> I think this MIB targets provisioning/monitoring for CE/BR.
> If so ,is it enough to check MIB object of CE ISP to know MAP deployment?

[Bing] It is enough for knowing whether MAP is deployed or not. But if we w=
ant know more detailed information, e.g. how many CEs have been connected t=
o a certain BR in a period, we need to do it with MAP-specific MIB, because=
 MAP itself is stateless, there's no entries of the MAP "tunnels" exist in =
CE/BR, we need the CE/BR to provide the information when it does MAP encaps=
ulation/de-encapsulation.=20
Considering some ISPs might not have strong requirement of these kind of de=
tailed statistic information, we made the MAP-MIB compliance as two levels,=
 one is basic which only contains MAP rules, the other is full-function con=
taining both rules and statistic information.

> And I don't know why this oid needs for MAP-E.
> mapStatisticConnections
> mapStatisticSpecificIP
> mapTunnelNumAlarm
> mapBRPortUsageOfSpecificIpAlarm

[Bing] mapStatisticConnections & mapStatisticSpecificIP are just explained =
as abovementioned. But the latter two should be removed in this version, th=
anks for finding the bugs.

> Some static could be provided by usig IP-MIB(RFC4293) and
> IP-FORWARD-MIB(RFC4292).

[Bing] They can provide some common static, but MAP-specific static, as men=
tioned above, could not be provided by them, because they could not identif=
y which packets are MAP and which are just normal IPv6 packets.

> But we may need new object for MAP-E security check statics because
> MAP-E checks consistency of IPv4/IPv6 src address.
> Because most of vendors already supports security mechanism,and they has
> static counter for  inconsistency of packet.
> http://tools.ietf.org/html/draft-janog-softwire-report-01#section-2.2
> The counter would be new object for MAP/6rd.

[Bing] I think it is a good point worth to be considered. And I'd like to h=
ear others' comments on this. Thank you.

Best regards,
Bing

> If it is needed,I will let's add our 6rd mib also.
>=20
> Regards,
> -Shishio
>=20
>=20
>=20
>=20
>=20
> (2013/02/08 15:56), Liubing (Leo) wrote:
> > Hi, Ole
> >
> > Thanks for your quick reply.
> >
> > In order to do the statistics, the BR need a bit more codes to extract =
the CE
> IPv6 addresses when doing de-encapsulation.
> > That is what we said in the last mail the operation might slightly impa=
ct the
> performance, so we defined this MIB function as optional.
> >
> > All the best,
> > Bing
> >
> >> -----Original Message-----
> >> From: Ole Troan [mailto:ot@cisco.com]
> >> Sent: Thursday, February 07, 2013 8:49 PM
> >> To: Liubing (Leo)
> >> Cc: Softwires WG; townsley@cisco.com; Yong Cui
> >> Subject: Re: [Softwires] MAP-MIB request for comments
> >>
> >>> The MAP-MIB draft has been updated as -03 version.
> >>>
> >>> In IETF85@Atlanta, we had a brief discussion, and the main comment
> was
> >> from Mark Townsley. He pointed out that the tunnel table defined in th=
e
> >> draft would make the BR recording every CEs' addresses connected to it=
.
> This
> >> operation would somewhat counterbalance the benefit of stateless
> design.
> >>> Basically, Mark's comment is a real issue, but not that serious. The
> tunnel
> >> table needs the translation/encapsulation application to provide CE
> address
> >> to the MIB agent, that might slightly impact the forwarding performanc=
e,
> >> but it is far from the weight of "stateful", because the the BR tunnel=
 table
> is
> >> not for real-time look up, it is just a kind of logging. In the worst =
situation,
> >> even the MIB crash, the packet forwarding won't be bothered.
> >>>
> >>> The purpose we defined a tunnel table is to add some statistics of CE
> >> connecting BR. For example, the ISP might want to know how many/what
> >> CEs had been connected to a certain BR.  This might be useful for serv=
ice
> >> analysis and management, e.g. to static percentage of MAP enabled and
> the
> >> traffic, so that the ISP could learn the status of MAP deployment/usag=
e,
> then
> >> might make some policies.
> >>> Considering the tunnel table might still more or less bring some
> additional
> >> complexity, we defined it as an optional object in the MIB. We defined
> two
> >> map-MIB-Compliance, one is basic compliance only containing the rule
> table,
> >> the other is full compliance containing rule table and tunnel table.
> >>
> >> how is the BR supposed to learn the CE addresses?
> >>
> >> cheers,
> >> Ole
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires
> > .
> >
>=20
> .


From shtsuchi@cisco.com  Mon Mar  4 21:00:27 2013
Return-Path: <shtsuchi@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 031F021F8600 for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 21:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.766
X-Spam-Level: 
X-Spam-Status: No, score=-8.766 tagged_above=-999 required=5 tests=[AWL=-0.567, BAYES_00=-2.599, J_CHICKENPOX_61=0.6, J_CHICKENPOX_63=0.6, J_CHICKENPOX_81=0.6, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_HI=-8]
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 dkY2AG8JlU52 for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 21:00:25 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 9197321F85E0 for <softwires@ietf.org>; Mon,  4 Mar 2013 21:00:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6234; q=dns/txt; s=iport; t=1362459625; x=1363669225; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=kolau4uRJOTDRYCovQWhddGEI7haRXl+ToQB35+2/zg=; b=kDI4hDGK8FEkECXs1TyB/wMLAWD586jQAFeRnU5vbCGINb/82urh5KiN mVmRHRqpiS4h8WmaeyIGElYDnEvEcJgNuUVvbzWaTQ4JJo3yjPvd5EpQR dN8vsR2B9Ds78nrVjyuPxUM3bg1Dhpvs+QbONMVl38erG/DYokL0Sn0Ax w=;
X-IronPort-AV: E=Sophos;i="4.84,785,1355097600"; d="scan'208";a="26729865"
Received: from vla196-nat.cisco.com (HELO bgl-core-3.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 05 Mar 2013 05:00:21 +0000
Received: from dhcp-10-141-41-180.cisco.com (dhcp-10-141-41-180.cisco.com [10.141.41.180]) by bgl-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2550K7c024608; Tue, 5 Mar 2013 05:00:20 GMT
Message-ID: <51357BE4.8080709@cisco.com>
Date: Tue, 05 Mar 2013 14:00:20 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: leo.liubing@huawei.com
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6D882D@nkgeml506-mbx.china.huawei.com> <87C876FC-6B2D-4570-8B7E-CC6D5FC73C8C@cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6D8A7F@nkgeml506-mbx.china.huawei.com> <5134D525.4070601@cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6E6176@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6E6176@nkgeml506-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org
Subject: Re: [Softwires] MAP-MIB request for comments
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, 05 Mar 2013 05:00:27 -0000

Bing
Thanks for your reply.
And I read 03 latest revision again.
I understood.
The draft provides two function.
-Provisioning: similar with IP TunnelMIB.
-Statics: count of each of CE traffic

As you mentions,I felt statics from CE is not so difficult.
But I have never seen similar implementation even though it is CLI.
Indeed,the statics which will be provide by this mib is NOT state of tunnel.
I would like to hear wg opinion.


I think it is not need "mapTunnelStatus",  because we can not find Status of each of CE.

BTW, this MIB not mentions relationship with NAT-MIB.
Especially MAP-E CE uses A+P technology,and latest nat mib defines A+P as new feature.
http://tools.ietf.org/html/draft-ietf-behave-nat-mib

I'm not sure whether the draft should write relationship with NAT-MIB.
And NAT-MIB does not be directly effect to this draft.
But MAP-E CE is using A+P, so we should check it.

Regards,
-Shishio




(2013/03/05 11:11), Liubing (Leo) wrote:
> Hi, Shishio
> 
> Thanks for your review. Please see inline.
> 
>> -----Original Message-----
>> From: Shishio Tsuchiya [mailto:shtsuchi@cisco.com]
>> Sent: Tuesday, March 05, 2013 1:09 AM
>> To: Liubing (Leo)
>> Cc: shtsuchi@cisco.com; softwires@ietf.org
>> Subject: Re: [Softwires] MAP-MIB request for comments
>>
>> Bing
>> I agree ISP would like to know status of MAP deployment/usage sometimes.
>> But I can not agree that MIB provides this function.
>>
>> I think this MIB targets provisioning/monitoring for CE/BR.
>> If so ,is it enough to check MIB object of CE ISP to know MAP deployment?
> 
> [Bing] It is enough for knowing whether MAP is deployed or not. But if we want know more detailed information, e.g. how many CEs have been connected to a certain BR in a period, we need to do it with MAP-specific MIB, because MAP itself is stateless, there's no entries of the MAP "tunnels" exist in CE/BR, we need the CE/BR to provide the information when it does MAP encapsulation/de-encapsulation.
> Considering some ISPs might not have strong requirement of these kind of detailed statistic information, we made the MAP-MIB compliance as two levels, one is basic which only contains MAP rules, the other is full-function containing both rules and statistic information.
> 
>> And I don't know why this oid needs for MAP-E.
>> mapStatisticConnections
>> mapStatisticSpecificIP
>> mapTunnelNumAlarm
>> mapBRPortUsageOfSpecificIpAlarm
> 
> [Bing] mapStatisticConnections & mapStatisticSpecificIP are just explained as abovementioned. But the latter two should be removed in this version, thanks for finding the bugs.
> 
>> Some static could be provided by usig IP-MIB(RFC4293) and
>> IP-FORWARD-MIB(RFC4292).
> 
> [Bing] They can provide some common static, but MAP-specific static, as mentioned above, could not be provided by them, because they could not identify which packets are MAP and which are just normal IPv6 packets.
> 
>> But we may need new object for MAP-E security check statics because
>> MAP-E checks consistency of IPv4/IPv6 src address.
>> Because most of vendors already supports security mechanism,and they has
>> static counter for  inconsistency of packet.
>> http://tools.ietf.org/html/draft-janog-softwire-report-01#section-2.2
>> The counter would be new object for MAP/6rd.
> 
> [Bing] I think it is a good point worth to be considered. And I'd like to hear others' comments on this. Thank you.
> 
> Best regards,
> Bing
> 
>> If it is needed,I will let's add our 6rd mib also.
>>
>> Regards,
>> -Shishio
>>
>>
>>
>>
>>
>> (2013/02/08 15:56), Liubing (Leo) wrote:
>>> Hi, Ole
>>>
>>> Thanks for your quick reply.
>>>
>>> In order to do the statistics, the BR need a bit more codes to extract the CE
>> IPv6 addresses when doing de-encapsulation.
>>> That is what we said in the last mail the operation might slightly impact the
>> performance, so we defined this MIB function as optional.
>>>
>>> All the best,
>>> Bing
>>>
>>>> -----Original Message-----
>>>> From: Ole Troan [mailto:ot@cisco.com]
>>>> Sent: Thursday, February 07, 2013 8:49 PM
>>>> To: Liubing (Leo)
>>>> Cc: Softwires WG; townsley@cisco.com; Yong Cui
>>>> Subject: Re: [Softwires] MAP-MIB request for comments
>>>>
>>>>> The MAP-MIB draft has been updated as -03 version.
>>>>>
>>>>> In IETF85@Atlanta, we had a brief discussion, and the main comment
>> was
>>>> from Mark Townsley. He pointed out that the tunnel table defined in the
>>>> draft would make the BR recording every CEs' addresses connected to it.
>> This
>>>> operation would somewhat counterbalance the benefit of stateless
>> design.
>>>>> Basically, Mark's comment is a real issue, but not that serious. The
>> tunnel
>>>> table needs the translation/encapsulation application to provide CE
>> address
>>>> to the MIB agent, that might slightly impact the forwarding performance,
>>>> but it is far from the weight of "stateful", because the the BR tunnel table
>> is
>>>> not for real-time look up, it is just a kind of logging. In the worst situation,
>>>> even the MIB crash, the packet forwarding won't be bothered.
>>>>>
>>>>> The purpose we defined a tunnel table is to add some statistics of CE
>>>> connecting BR. For example, the ISP might want to know how many/what
>>>> CEs had been connected to a certain BR.  This might be useful for service
>>>> analysis and management, e.g. to static percentage of MAP enabled and
>> the
>>>> traffic, so that the ISP could learn the status of MAP deployment/usage,
>> then
>>>> might make some policies.
>>>>> Considering the tunnel table might still more or less bring some
>> additional
>>>> complexity, we defined it as an optional object in the MIB. We defined
>> two
>>>> map-MIB-Compliance, one is basic compliance only containing the rule
>> table,
>>>> the other is full compliance containing rule table and tunnel table.
>>>>
>>>> how is the BR supposed to learn the CE addresses?
>>>>
>>>> cheers,
>>>> Ole
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>> .
>>>
>>
>> .
> 
> .
> 



From leo.liubing@huawei.com  Mon Mar  4 22:56:43 2013
Return-Path: <leo.liubing@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 4CA8C21F867E for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 22:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-0.900, BAYES_00=-2.599, J_CHICKENPOX_61=0.6, J_CHICKENPOX_63=0.6, J_CHICKENPOX_81=0.6, J_CHICKENPOX_93=0.6, 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 RBrwP2gMhwnY for <softwires@ietfa.amsl.com>; Mon,  4 Mar 2013 22:56:42 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9FA4121F862B for <softwires@ietf.org>; Mon,  4 Mar 2013 22:56:41 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APA82838; Tue, 05 Mar 2013 06:56:40 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Mar 2013 06:56:32 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Mar 2013 06:56:39 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.42]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Tue, 5 Mar 2013 14:56:31 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Shishio Tsuchiya <shtsuchi@cisco.com>
Thread-Topic: [Softwires] MAP-MIB request for comments
Thread-Index: AQHOBTAtcJOhmhsaCEqJm/2ZvK5A3pht0n+AgAGyB7CAJeDigIABGoAw//+sRwCAAJMEwA==
Date: Tue, 5 Mar 2013 06:56:31 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6E6269@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6D882D@nkgeml506-mbx.china.huawei.com> <87C876FC-6B2D-4570-8B7E-CC6D5FC73C8C@cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6D8A7F@nkgeml506-mbx.china.huawei.com> <5134D525.4070601@cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6E6176@nkgeml506-mbx.china.huawei.com> <51357BE4.8080709@cisco.com>
In-Reply-To: <51357BE4.8080709@cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] MAP-MIB request for comments
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, 05 Mar 2013 06:56:43 -0000

Hi, Shishio

> -----Original Message-----
> From: Shishio Tsuchiya [mailto:shtsuchi@cisco.com]
> Sent: Tuesday, March 05, 2013 1:00 PM
> To: Liubing (Leo)
> Cc: shtsuchi@cisco.com; softwires@ietf.org; Fuyu (Eleven)
> Subject: Re: [Softwires] MAP-MIB request for comments
>=20
> Bing
> Thanks for your reply.
> And I read 03 latest revision again.
> I understood.
> The draft provides two function.
> -Provisioning: similar with IP TunnelMIB.
> -Statics: count of each of CE traffic

[Bing] We defined two subtrees. One is mapRule, which only contains the Map=
ping Rules; the other is mapTunnel, in fact it is quite different with IP T=
unnelMIB, because the "Tunnels" in MAP is only an implicit correlation betw=
een a certain BR and CEs, no entries there to record the tunnel itself. So =
we just define some static information to present the implicit "Tunnels".
With current definition, we couldn't count per CE traffic in BR, only the t=
otal MAP traffic. Because we thought it might be too complex to maintain a =
counter for each CE address in BR. If we really care about per CE traffic, =
we can get it on CE by mapTunnel subtree. (I realized the mapTunnel definit=
ion was only in BR perspective in this draft, we'll modify it later.)

>=20
> As you mentions,I felt statics from CE is not so difficult.
> But I have never seen similar implementation even though it is CLI.
> Indeed,the statics which will be provide by this mib is NOT state of tunn=
el.
> I would like to hear wg opinion.
>=20
>=20
> I think it is not need "mapTunnelStatus",  because we can not find Status=
 of
> each of CE.

[Bing] Thanks, we'll consider it in the next version.

>=20
> BTW, this MIB not mentions relationship with NAT-MIB.
> Especially MAP-E CE uses A+P technology,and latest nat mib defines A+P as
> new feature.
> http://tools.ietf.org/html/draft-ietf-behave-nat-mib
>=20
> I'm not sure whether the draft should write relationship with NAT-MIB.
> And NAT-MIB does not be directly effect to this draft.
> But MAP-E CE is using A+P, so we should check it.

[Bing] Thanks for the information. I've had a quick review, but I think it'=
s better NOT to include it in MAP-MIB, if we need those information, we can=
 implement the latest NAT-MIB in the CE. We treated the NAT-MIB as a separa=
ted common building block in MAP system, we thought it was better NOT to mi=
x them together.

Best regards,
Bing

> Regards,
> -Shishio
>=20
>=20
>=20
>=20
> (2013/03/05 11:11), Liubing (Leo) wrote:
> > Hi, Shishio
> >
> > Thanks for your review. Please see inline.
> >
> >> -----Original Message-----
> >> From: Shishio Tsuchiya [mailto:shtsuchi@cisco.com]
> >> Sent: Tuesday, March 05, 2013 1:09 AM
> >> To: Liubing (Leo)
> >> Cc: shtsuchi@cisco.com; softwires@ietf.org
> >> Subject: Re: [Softwires] MAP-MIB request for comments
> >>
> >> Bing
> >> I agree ISP would like to know status of MAP deployment/usage
> sometimes.
> >> But I can not agree that MIB provides this function.
> >>
> >> I think this MIB targets provisioning/monitoring for CE/BR.
> >> If so ,is it enough to check MIB object of CE ISP to know MAP
> deployment?
> >
> > [Bing] It is enough for knowing whether MAP is deployed or not. But if =
we
> want know more detailed information, e.g. how many CEs have been
> connected to a certain BR in a period, we need to do it with MAP-specific
> MIB, because MAP itself is stateless, there's no entries of the MAP "tunn=
els"
> exist in CE/BR, we need the CE/BR to provide the information when it does
> MAP encapsulation/de-encapsulation.
> > Considering some ISPs might not have strong requirement of these kind o=
f
> detailed statistic information, we made the MAP-MIB compliance as two
> levels, one is basic which only contains MAP rules, the other is full-fun=
ction
> containing both rules and statistic information.
> >
> >> And I don't know why this oid needs for MAP-E.
> >> mapStatisticConnections
> >> mapStatisticSpecificIP
> >> mapTunnelNumAlarm
> >> mapBRPortUsageOfSpecificIpAlarm
> >
> > [Bing] mapStatisticConnections & mapStatisticSpecificIP are just explai=
ned
> as abovementioned. But the latter two should be removed in this version,
> thanks for finding the bugs.
> >
> >> Some static could be provided by usig IP-MIB(RFC4293) and
> >> IP-FORWARD-MIB(RFC4292).
> >
> > [Bing] They can provide some common static, but MAP-specific static, as
> mentioned above, could not be provided by them, because they could not
> identify which packets are MAP and which are just normal IPv6 packets.
> >
> >> But we may need new object for MAP-E security check statics because
> >> MAP-E checks consistency of IPv4/IPv6 src address.
> >> Because most of vendors already supports security mechanism,and they
> has
> >> static counter for  inconsistency of packet.
> >> http://tools.ietf.org/html/draft-janog-softwire-report-01#section-2.2
> >> The counter would be new object for MAP/6rd.
> >
> > [Bing] I think it is a good point worth to be considered. And I'd like =
to hear
> others' comments on this. Thank you.
> >
> > Best regards,
> > Bing
> >
> >> If it is needed,I will let's add our 6rd mib also.
> >>
> >> Regards,
> >> -Shishio
> >>
> >>
> >>
> >>
> >>
> >> (2013/02/08 15:56), Liubing (Leo) wrote:
> >>> Hi, Ole
> >>>
> >>> Thanks for your quick reply.
> >>>
> >>> In order to do the statistics, the BR need a bit more codes to extrac=
t the
> CE
> >> IPv6 addresses when doing de-encapsulation.
> >>> That is what we said in the last mail the operation might slightly im=
pact
> the
> >> performance, so we defined this MIB function as optional.
> >>>
> >>> All the best,
> >>> Bing
> >>>
> >>>> -----Original Message-----
> >>>> From: Ole Troan [mailto:ot@cisco.com]
> >>>> Sent: Thursday, February 07, 2013 8:49 PM
> >>>> To: Liubing (Leo)
> >>>> Cc: Softwires WG; townsley@cisco.com; Yong Cui
> >>>> Subject: Re: [Softwires] MAP-MIB request for comments
> >>>>
> >>>>> The MAP-MIB draft has been updated as -03 version.
> >>>>>
> >>>>> In IETF85@Atlanta, we had a brief discussion, and the main comment
> >> was
> >>>> from Mark Townsley. He pointed out that the tunnel table defined in
> the
> >>>> draft would make the BR recording every CEs' addresses connected to
> it.
> >> This
> >>>> operation would somewhat counterbalance the benefit of stateless
> >> design.
> >>>>> Basically, Mark's comment is a real issue, but not that serious. Th=
e
> >> tunnel
> >>>> table needs the translation/encapsulation application to provide CE
> >> address
> >>>> to the MIB agent, that might slightly impact the forwarding
> performance,
> >>>> but it is far from the weight of "stateful", because the the BR tunn=
el
> table
> >> is
> >>>> not for real-time look up, it is just a kind of logging. In the wors=
t
> situation,
> >>>> even the MIB crash, the packet forwarding won't be bothered.
> >>>>>
> >>>>> The purpose we defined a tunnel table is to add some statistics of =
CE
> >>>> connecting BR. For example, the ISP might want to know how
> many/what
> >>>> CEs had been connected to a certain BR.  This might be useful for
> service
> >>>> analysis and management, e.g. to static percentage of MAP enabled
> and
> >> the
> >>>> traffic, so that the ISP could learn the status of MAP
> deployment/usage,
> >> then
> >>>> might make some policies.
> >>>>> Considering the tunnel table might still more or less bring some
> >> additional
> >>>> complexity, we defined it as an optional object in the MIB. We defin=
ed
> >> two
> >>>> map-MIB-Compliance, one is basic compliance only containing the rule
> >> table,
> >>>> the other is full compliance containing rule table and tunnel table.
> >>>>
> >>>> how is the BR supposed to learn the CE addresses?
> >>>>
> >>>> cheers,
> >>>> Ole
> >>> _______________________________________________
> >>> Softwires mailing list
> >>> Softwires@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/softwires
> >>> .
> >>>
> >>
> >> .
> >
> > .
> >
>=20


From iesg-secretary@ietf.org  Wed Mar  6 13:05:23 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2828521F8CD2; Wed,  6 Mar 2013 13:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 Vh74qYooahMM; Wed,  6 Mar 2013 13:05:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2A1411E8136; Wed,  6 Mar 2013 13:05:13 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.41
Message-ID: <20130306210513.19608.62251.idtracker@ietfa.amsl.com>
Date: Wed, 06 Mar 2013 13:05:13 -0800
Cc: softwire mailing list <softwires@ietf.org>, softwire chair <softwire-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Softwires] Protocol Action: 'RADIUS Attribute for 6rd' to Proposed Standard	(draft-ietf-softwire-6rd-radius-attrib-11.txt)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 21:05:23 -0000

The IESG has approved the following document:
- 'RADIUS Attribute for 6rd'
  (draft-ietf-softwire-6rd-radius-attrib-11.txt) as Proposed Standard

This document is the product of the Softwires Working Group.

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/




Technical Summary 

  IPv6 Rapid Deployment (6rd) provides IPv6 connectivity over legacy
  IPv4-only infrastructure. 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 AAA servers, while users may be configured by Broadband
  Network Gateway (BNG) through DHCP. This document defines a RADIUS
  attribute that carries 6rd configuration information from AAA server
  to BNG.


Working Group Summary 
 
  This document was discussed in depth and well-reviewed. The document
  was also presented and reviewed in wg radext.  WG consensus is
  strong to publish this document.  The authors also revised the
  document based on the review comments given by IESG on a similar
  document, RADIUS Extensions for Dual-Stack Lite, RFC 6519.


Document Quality 

  As far as we know, there is no existing implementation yet.  A
  couple of vendors may have the plan to implement.  This may not be
  counted as a significant number, yet.

Personnel

  Softwire co-chair, Yong Cui, is the Document Shepherd.   Ralph
  Droms is the Responsible AD. 




From iesg-secretary@ietf.org  Wed Mar  6 13:05:23 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA5621F8CD8 for <softwires@ietfa.amsl.com>; Wed,  6 Mar 2013 13:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 fItHfSUUSilB; Wed,  6 Mar 2013 13:05:23 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB72E11E813A; Wed,  6 Mar 2013 13:05:13 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IANA <drafts-approval@icann.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.41
X-IETF-Draft-string: draft-ietf-softwire-6rd-radius-attrib
X-IETF-Draft-revision: 11
Message-ID: <20130306210513.19608.5815.idtracker@ietfa.amsl.com>
Date: Wed, 06 Mar 2013 13:05:13 -0800
Cc: softwire mailing list <softwires@ietf.org>, softwire chair <softwire-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Softwires] Protocol Action: 'RADIUS Attribute for 6rd' to Proposed Standard	(draft-ietf-softwire-6rd-radius-attrib-11.txt)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: noreply@ietf.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, 06 Mar 2013 21:05:23 -0000

The IESG has approved the following document:
- 'RADIUS Attribute for 6rd'
  (draft-ietf-softwire-6rd-radius-attrib-11.txt) as Proposed Standard

This document is the product of the Softwires Working Group.

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/




Technical Summary 

  IPv6 Rapid Deployment (6rd) provides IPv6 connectivity over legacy
  IPv4-only infrastructure. 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 AAA servers, while users may be configured by Broadband
  Network Gateway (BNG) through DHCP. This document defines a RADIUS
  attribute that carries 6rd configuration information from AAA server
  to BNG.


Working Group Summary 
 
  This document was discussed in depth and well-reviewed. The document
  was also presented and reviewed in wg radext.  WG consensus is
  strong to publish this document.  The authors also revised the
  document based on the review comments given by IESG on a similar
  document, RADIUS Extensions for Dual-Stack Lite, RFC 6519.


Document Quality 

  As far as we know, there is no existing implementation yet.  A
  couple of vendors may have the plan to implement.  This may not be
  counted as a significant number, yet.

Personnel

  Softwire co-chair, Yong Cui, is the Document Shepherd.   Ralph
  Droms is the Responsible AD. 




From cuiyong@tsinghua.edu.cn  Wed Mar  6 18:01:17 2013
Return-Path: <cuiyong@tsinghua.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 9699621F8652 for <softwires@ietfa.amsl.com>; Wed,  6 Mar 2013 18:01:17 -0800 (PST)
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 WFuPKgF7XLEn for <softwires@ietfa.amsl.com>; Wed,  6 Mar 2013 18:01:17 -0800 (PST)
Received: from smtp.tsinghua.edu.cn (smtp01.tsinghua.edu.cn [166.111.8.80]) by ietfa.amsl.com (Postfix) with ESMTP id CDD4221F8650 for <softwires@ietf.org>; Wed,  6 Mar 2013 18:01:13 -0800 (PST)
Received: from [59.66.24.32] by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from <cuiyong@tsinghua.edu.cn>) id 1UDQ8s-0004Ad-Hn; Thu, 07 Mar 2013 10:01:10 +0800
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Thu, 07 Mar 2013 10:01:10 +0800
From: Yong Cui <cuiyong@tsinghua.edu.cn>
Sender: Yong Cui <yong@csnet1.cs.tsinghua.edu.cn>
To: Softwires WG <softwires@ietf.org>
Message-ID: <CD5E1269.3583F%yong@csnet1.cs.tsinghua.edu.cn>
Thread-Topic: [Softwires] Call for agenda in IETF 86
In-Reply-To: <CD415AB3.33C2C%yong@csnet1.cs.tsinghua.edu.cn>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>
Subject: Re: [Softwires] Call for agenda in IETF 86
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, 07 Mar 2013 02:01:17 -0000

Dear all,

We have our Softwire Agenda here:
https://datatracker.ietf.org/meeting/86/agenda/softwire/

If we missed any request, please let us know.

Please send your slides to the chairs by 3/9 Saturday:
softwire-chairs@tools.ietf.org

Thanks,

Yong & Suresh


-----Original Message-----
From: Yong Cui <cuiyong@tsinghua.edu.cn>
Date: Wed, 13 Feb 2013 15:20:06 +0800
To: Softwires WG <softwires@ietf.org>
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>
Subject: [Softwires] Call for agenda in IETF 86

>Hi folks,
>
>
>We will have two sessions in the coming IETF meeting
>in Orlando according to the preliminary agenda:
>1) Morning Session on March 11, Monday (2.5h);
>2) Morning Session on March 13, Wednesday (2.5h).
>
>If you would like to have a time slot, please reply this
>email and send your request to Suresh and me in the
>following format by Feb. 21:
>
>(name, title, link to IETF datatracker, minutes requested).
>
>
>Thanks,
>
>Yong & Suresh
>
>
>_______________________________________________
>Softwires mailing list
>Softwires@ietf.org
>https://www.ietf.org/mailman/listinfo/softwires
>



From kristian.poscic@alcatel-lucent.com  Fri Mar  8 13:58:23 2013
Return-Path: <kristian.poscic@alcatel-lucent.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 EF5EE21F85E2 for <softwires@ietfa.amsl.com>; Fri,  8 Mar 2013 13:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.248
X-Spam-Level: 
X-Spam-Status: No, score=-10.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 WV+U05LMgYe4 for <softwires@ietfa.amsl.com>; Fri,  8 Mar 2013 13:58:23 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 276AA21F85D9 for <softwires@ietf.org>; Fri,  8 Mar 2013 13:58:23 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r28Lvvmm012466 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <softwires@ietf.org>; Fri, 8 Mar 2013 22:58:21 +0100
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (135.120.45.63) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 8 Mar 2013 22:58:03 +0100
Received: from US70UWXCHMBA06.zam.alcatel-lucent.com ([169.254.11.15]) by US70UWXCHHUB02.zam.alcatel-lucent.com ([135.5.2.49]) with mapi id 14.02.0247.003; Fri, 8 Mar 2013 16:58:01 -0500
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: softwire-map-04
Thread-Index: Ac4cRzx4k9a2n2iJSeKTM9VpqoT93A==
Date: Fri, 8 Mar 2013 21:58:00 +0000
Message-ID: <7921F977B17D5B49B8DCC955A339D2F02AA85646@US70UWXCHMBA06.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: multipart/alternative; boundary="_000_7921F977B17D5B49B8DCC955A339D2F02AA85646US70UWXCHMBA06z_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Subject: [Softwires] softwire-map-04
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, 08 Mar 2013 21:58:24 -0000

--_000_7921F977B17D5B49B8DCC955A339D2F02AA85646US70UWXCHMBA06z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think the following needs to be corrected in the softwire-map draft:


MAP Configuration



   For a given MAP domain, the BR and CE MUST be configured with the

   following MAP elements.  The configured values for these elements are

   identical for all CEs and BRs within a given MAP domain.



   o  The End-User IPv6 prefix (Part of the normal IPv6 provisioning).



   o  The Basic Mapping Rule and optionally the Forwarding Mapping

      Rules, including the Rule IPv6 prefix, Rule IPv4 prefix, and

      Length of EA bits



   o  The IPv6 address of the MAP BR.



   o  Hub and spoke mode or Mesh mode.  (If all traffic should be sent

      to the BR, or if direct CE to CE traffic should be supported).


The end-user IPv6 prefix is not identical for all CEs. On the contrary, it =
must be unique per CE. For example uniqueness is reflected in EA bits in ca=
se of shared IPv4 address.
Kris.


--_000_7921F977B17D5B49B8DCC955A339D2F02AA85646US70UWXCHMBA06z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I think the following needs to be corrected in the s=
oftwire-map draft:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre><span style=3D"color:black">MAP Configuration<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; For a given MAP domain, the B=
R and CE MUST be configured with the<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; following MAP elements.&nbsp;=
 The configured values for these elements are<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; identical for all CEs and BRs=
 within a given MAP domain.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; o&nbsp; The End-User IPv6 pre=
fix (Part of the normal IPv6 provisioning).<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; o&nbsp; The Basic Mapping Rul=
e and optionally the Forwarding Mapping<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Rules, incl=
uding the Rule IPv6 prefix, Rule IPv4 prefix, and<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length of E=
A bits<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; o&nbsp; The IPv6 address of t=
he MAP BR.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; o&nbsp; Hub and spoke mode or=
 Mesh mode.&nbsp; (If all traffic should be sent<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the BR, =
or if direct CE to CE traffic should be supported).<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The end-user IPv6 prefix is not identical for all CE=
s. On the contrary, it must be unique per CE. For example uniqueness is ref=
lected in EA bits in case of shared IPv4 address.<o:p></o:p></p>
<p class=3D"MsoNormal">Kris.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7921F977B17D5B49B8DCC955A339D2F02AA85646US70UWXCHMBA06z_--

From rajiva@cisco.com  Fri Mar  8 14:04:50 2013
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 D54BD21F858C for <softwires@ietfa.amsl.com>; Fri,  8 Mar 2013 14:04:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.448
X-Spam-Level: 
X-Spam-Status: No, score=-10.448 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 gFDftSu5fkbK for <softwires@ietfa.amsl.com>; Fri,  8 Mar 2013 14:04:50 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id DDB3221F8573 for <softwires@ietf.org>; Fri,  8 Mar 2013 14:04:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6469; q=dns/txt; s=iport; t=1362780290; x=1363989890; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=o6izCzNPdApkiak+irAm1+XRbaPIfdAux0qmXKylzvk=; b=hFBhhxP8SdUXZJ6+mfZCi+yeIb+qDm+r1RVKmh9UxiPv/ZYha9g5Kc6d YUbrwW6YMJRnxrmqSVbV3TK0StmTd/sqt9FWe8em09vQIH9pl8+j+Rc3g qOAzIxzT0N3vXGQcXvg+YKFlmd+jqUUQVgORi2FgEOlZy7Uyif0evsjQj 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAPJfOlGtJXG8/2dsb2JhbABDhBXAOoFdFnSCLQEBBAEBASpBCxACAQg/BycLFBECBA4FiBMMu3cEjwgEB4JfYQOWU5Bygwo
X-IronPort-AV: E=Sophos;i="4.84,810,1355097600";  d="scan'208,217";a="182511701"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-9.cisco.com with ESMTP; 08 Mar 2013 22:04:49 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r28M4nkO004729 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 8 Mar 2013 22:04:49 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.72]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Fri, 8 Mar 2013 16:04:49 -0600
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
Thread-Topic: [Softwires] softwire-map-04
Thread-Index: AQHOHEjzbrpD4Lbsg0uewJO7Kw7r1g==
Date: Fri, 8 Mar 2013 22:04:48 +0000
Message-ID: <6CBC7F3C-315C-4FEE-B223-F6A347E5BF17@cisco.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA85646@US70UWXCHMBA06.zam.alcatel-lucent.com>
In-Reply-To: <7921F977B17D5B49B8DCC955A339D2F02AA85646@US70UWXCHMBA06.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_6CBC7F3C315C4FEEB223F6A347E5BF17ciscocom_"
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] softwire-map-04
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, 08 Mar 2013 22:04:51 -0000

--_000_6CBC7F3C315C4FEEB223F6A347E5BF17ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Good catch, indeed. Needs to be updated.

Cheers,
Rajiv

Sent from my Phone

On Mar 8, 2013, at 4:58 PM, "Poscic, Kristian (Kristian)" <kristian.poscic@=
alcatel-lucent.com<mailto:kristian.poscic@alcatel-lucent.com>> wrote:

I think the following needs to be corrected in the softwire-map draft:


MAP Configuration



   For a given MAP domain, the BR and CE MUST be configured with the

   following MAP elements.  The configured values for these elements are

   identical for all CEs and BRs within a given MAP domain.



   o  The End-User IPv6 prefix (Part of the normal IPv6 provisioning).



   o  The Basic Mapping Rule and optionally the Forwarding Mapping

      Rules, including the Rule IPv6 prefix, Rule IPv4 prefix, and

      Length of EA bits



   o  The IPv6 address of the MAP BR.



   o  Hub and spoke mode or Mesh mode.  (If all traffic should be sent

      to the BR, or if direct CE to CE traffic should be supported).


The end-user IPv6 prefix is not identical for all CEs. On the contrary, it =
must be unique per CE. For example uniqueness is reflected in EA bits in ca=
se of shared IPv4 address.
Kris.

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

--_000_6CBC7F3C315C4FEEB223F6A347E5BF17ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Good catch, indeed. Needs to be updated.<br>
<br>
Cheers,
<div>Rajiv</div>
<div><br>
</div>
<div>Sent from my Phone</div>
</div>
<div><br>
On Mar 8, 2013, at 4:58 PM, &quot;Poscic, Kristian (Kristian)&quot; &lt;<a =
href=3D"mailto:kristian.poscic@alcatel-lucent.com">kristian.poscic@alcatel-=
lucent.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I think the following needs to be corrected in the s=
oftwire-map draft:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre><span style=3D"color:black">MAP Configuration<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; For a given MAP domain, the B=
R and CE MUST be configured with the<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; following MAP elements.&nbsp;=
 The configured values for these elements are<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; identical for all CEs and BRs=
 within a given MAP domain.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; o&nbsp; The End-User IPv6 pre=
fix (Part of the normal IPv6 provisioning).<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; o&nbsp; The Basic Mapping Rul=
e and optionally the Forwarding Mapping<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Rules, incl=
uding the Rule IPv6 prefix, Rule IPv4 prefix, and<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length of E=
A bits<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; o&nbsp; The IPv6 address of t=
he MAP BR.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; o&nbsp; Hub and spoke mode or=
 Mesh mode.&nbsp; (If all traffic should be sent<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the BR, =
or if direct CE to CE traffic should be supported).<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The end-user IPv6 prefix is not identical for all CE=
s. On the contrary, it must be unique per CE. For example uniqueness is ref=
lected in EA bits in case of shared IPv4 address.<o:p></o:p></p>
<p class=3D"MsoNormal">Kris.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>Softwires mailing list</span><br>
<span><a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a></span><b=
r>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/softwires">https://w=
ww.ietf.org/mailman/listinfo/softwires</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_6CBC7F3C315C4FEEB223F6A347E5BF17ciscocom_--

From yong@csnet1.cs.tsinghua.edu.cn  Sun Mar 10 13:36:46 2013
Return-Path: <yong@csnet1.cs.tsinghua.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 6023111E80FF for <softwires@ietfa.amsl.com>; Sun, 10 Mar 2013 13:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.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 2lqC2b+TFUFI for <softwires@ietfa.amsl.com>; Sun, 10 Mar 2013 13:36:45 -0700 (PDT)
Received: from mail.csnet1.cs.tsinghua.edu.cn (unknown [211.151.89.50]) by ietfa.amsl.com (Postfix) with ESMTP id 534A411E80FC for <softwires@ietf.org>; Sun, 10 Mar 2013 13:36:13 -0700 (PDT)
Received: from [172.16.239.218] (unknown [205.204.29.187]) by mail.csnet1.cs.tsinghua.edu.cn (Tsinghua University (Postfix)) with ESMTPA id 82D9D14A80D1; Mon, 11 Mar 2013 04:23:41 +0800 (CST)
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Mon, 11 Mar 2013 04:35:22 +0800
From: Yong Cui <yong@csnet1.cs.tsinghua.edu.cn>
To: Yong Cui <cuiyong@tsinghua.edu.cn>, Softwires WG <softwires@ietf.org>
Message-ID: <CD630EAD.35EEA%yong@csnet1.cs.tsinghua.edu.cn>
Thread-Topic: [Softwires] Call for agenda in IETF 86
In-Reply-To: <CD5E1269.3583F%yong@csnet1.cs.tsinghua.edu.cn>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [Softwires] Call for agenda in IETF 86
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, 10 Mar 2013 20:36:46 -0000

Hi all,

I would like to remind the speakers in softwire sessions.
If you haven't send your slides, please send to the chairs asap.
Softwire sessions start from the very beginning, Monday morning.

Yong

-----Original Message-----
From: Yong Cui <cuiyong@tsinghua.edu.cn>
Date: Thu, 07 Mar 2013 10:01:10 +0800
To: Softwires WG <softwires@ietf.org>
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>
Subject: Re: [Softwires] Call for agenda in IETF 86

>Dear all,
>
>We have our Softwire Agenda here:
>https://datatracker.ietf.org/meeting/86/agenda/softwire/
>
>If we missed any request, please let us know.
>
>Please send your slides to the chairs by 3/9 Saturday:
>softwire-chairs@tools.ietf.org
>
>Thanks,
>
>Yong & Suresh
>
>
>-----Original Message-----
>From: Yong Cui <cuiyong@tsinghua.edu.cn>
>Date: Wed, 13 Feb 2013 15:20:06 +0800
>To: Softwires WG <softwires@ietf.org>
>Cc: Yong Cui <cuiyong@tsinghua.edu.cn>
>Subject: [Softwires] Call for agenda in IETF 86
>
>>Hi folks,
>>
>>
>>We will have two sessions in the coming IETF meeting
>>in Orlando according to the preliminary agenda:
>>1) Morning Session on March 11, Monday (2.5h);
>>2) Morning Session on March 13, Wednesday (2.5h).
>>
>>If you would like to have a time slot, please reply this
>>email and send your request to Suresh and me in the
>>following format by Feb. 21:
>>
>>(name, title, link to IETF datatracker, minutes requested).
>>
>>
>>Thanks,
>>
>>Yong & Suresh
>>
>>
>>_______________________________________________
>>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 internet-drafts@ietf.org  Sun Mar 10 18:34:35 2013
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 E096321F8895; Sun, 10 Mar 2013 18:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 7AtfKAooIsWI; Sun, 10 Mar 2013 18:34:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5460A21F858E; Sun, 10 Mar 2013 18:34:35 -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: 4.42
Message-ID: <20130311013435.19992.64028.idtracker@ietfa.amsl.com>
Date: Sun, 10 Mar 2013 18:34:35 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-unified-cpe-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: Mon, 11 Mar 2013 01:34:36 -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           : Unified IPv4-in-IPv6 Softwire CPE
	Author(s)       : Mohamed Boucadair
                          Ian Farrer
	Filename        : draft-ietf-softwire-unified-cpe-00.txt
	Pages           : 13
	Date            : 2013-03-10

Abstract:
   Transporting IPv4 packets encapsulated in IPv6 is a common solution
   to the problem of IPv4 service continuity over IPv6-only provider
   networks.  A number of differing functional approaches have been
   developed for this, each having their own specific characteristics.
   As these approaches share a similar functional architecture and use
   the same data plane mechanisms, this memo describes a specification
   whereby a single CPE can interwork with all of the standardized and
   proposed approaches to providing encapsulated IPv4 in IPv6 services.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-softwire-unified-cpe

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-softwire-unified-cpe-00


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


From tom.taylor.stds@gmail.com  Sun Mar 10 18:55:06 2013
Return-Path: <tom.taylor.stds@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 8408821F85E2 for <softwires@ietfa.amsl.com>; Sun, 10 Mar 2013 18:55:06 -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 8OCoOlSwNTPO for <softwires@ietfa.amsl.com>; Sun, 10 Mar 2013 18:55:05 -0700 (PDT)
Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) by ietfa.amsl.com (Postfix) with ESMTP id 4434721F898A for <softwires@ietf.org>; Sun, 10 Mar 2013 18:55:05 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id uo15so3136179pbc.5 for <softwires@ietf.org>; Sun, 10 Mar 2013 18:55:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=LvBVjN7m00YaYI6Xm7Sp3hDO1Z62ZZOk+eF/dEipS3g=; b=b6EmYSkvHeb94+BzU0IXRT6VAmNottkTFedowCtzBvoxKH06CTeQ7njgeYARif+O8u cenqOV1AArrbfEBUSYm9tsDAN0XsnGiGQnRweryN3z/54XhkgjhISwFzBv/f2x15MNU3 vgOcDvkw8ybIrADuj8WG/0Faq8HlmJe4Ulk6RODoLM8jPth6ctlm2mgPiTIW6WmzUkaC RL7spQBtdDe0tS8BEgtOrHYLriYJGWb/9mYca4sqVb1+ZdlHYsAMk2Ar/dVUoqbvCgH5 FtXb3O7wgTCDF0ThYUxOG26cZoC0URCAdkhaduvmS2WBkxj2jjUoff7dsobguuFbP0GU aQaQ==
MIME-Version: 1.0
X-Received: by 10.69.1.101 with SMTP id bf5mr23589555pbd.208.1362966904832; Sun, 10 Mar 2013 18:55:04 -0700 (PDT)
Received: by 10.68.158.44 with HTTP; Sun, 10 Mar 2013 18:55:04 -0700 (PDT)
In-Reply-To: <20130311014504.23752.5927.idtracker@ietfa.amsl.com>
References: <20130311014504.23752.5927.idtracker@ietfa.amsl.com>
Date: Sun, 10 Mar 2013 21:55:04 -0400
Message-ID: <CAPeToO2yX6iYKbEB-v7beXQr=UbiAwQMeJt1ChktpR5unx6QdA@mail.gmail.com>
From: Tom Taylor <tom.taylor.stds@gmail.com>
To: softwires@ietf.org
Content-Type: multipart/alternative; boundary=047d7b2e0e713507ce04d79c763c
Subject: [Softwires] Fwd: New Version Notification for draft-zhou-dime-4over6-provisioning-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: Mon, 11 Mar 2013 01:55:06 -0000

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

The draft described by this notice is concerned with Diameter provisioning
of the required configuration for all methods covered by the universal CPE
draft. The contents were determined independently of that draft. I will
compare the results with what the universal CPE draft proposes in a
separate E-mail.

Tom Taylor

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Sun, Mar 10, 2013 at 9:45 PM
Subject: New Version Notification for
draft-zhou-dime-4over6-provisioning-00.txt
To: tom.taylor.stds@gmail.com
Cc: cathy.zhou@huawei.com

A new version of I-D, draft-zhou-dime-4over6-provisioning-00.txt
has been successfully submitted by T. Taylor and posted to the
IETF repository.

Filename:        draft-zhou-dime-4over6-provisioning
Revision:        00
Title:           Attribute-Value Pairs For Provisioning Customer Equipment
Supporting IPv4-Over-IPv6 Transitional Solutions
Creation date:   2013-03-11
Group:           Individual Submission
Number of pages: 11
URL:
http://www.ietf.org/internet-drafts/draft-zhou-dime-4over6-provisioning-00.txt
Status:
http://datatracker.ietf.org/doc/draft-zhou-dime-4over6-provisioning
Htmlized:
http://tools.ietf.org/html/draft-zhou-dime-4over6-provisioning-00


Abstract:
   During the transition from IPv4 to IPv6, customer equipment may have
   to support one of the various transition methods that have been or
   are currently being defined for carrying IPv4 packets over IPv6.
   Work is currently in progress to enumerate the information that needs
   to be provisioned on a customer edge router to support a list of
   transition techniques based on tunneling IPv4 in IPv6, with a view to
   defining reusable components for a reasonable transition path between
   these techniques.  To the extent that the provisioning is done
   dynamically, AAA support is needed to provide the information to the
   network server responsible for passing the information to the
   customer equipment.  This document specifies Diameter attribute-value
   pairs to be used for that purpose.




The IETF Secretariat

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

The draft described by this notice is concerned with Diameter provisioning =
of the required configuration for all methods covered by the universal CPE =
draft. The contents were determined independently of that draft. I will com=
pare the results with what the universal CPE draft proposes in a separate E=
-mail.<br>
<br>Tom Taylor<br><br><div class=3D"gmail_quote">---------- Forwarded messa=
ge ----------<br>From: <b class=3D"gmail_sendername"></b> <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</=
a>&gt;</span><br>
Date: Sun, Mar 10, 2013 at 9:45 PM<br>Subject: New Version Notification for=
 draft-zhou-dime-4over6-provisioning-00.txt<br>To: <a href=3D"mailto:tom.ta=
ylor.stds@gmail.com">tom.taylor.stds@gmail.com</a><br>Cc: <a href=3D"mailto=
:cathy.zhou@huawei.com">cathy.zhou@huawei.com</a><br>
<br>
A new version of I-D, draft-zhou-dime-4over6-provisioning-00.txt<br>
has been successfully submitted by T. Taylor and posted to the<br>
IETF repository.<br>
<br>
Filename: =A0 =A0 =A0 =A0draft-zhou-dime-4over6-provisioning<br>
Revision: =A0 =A0 =A0 =A000<br>
Title: =A0 =A0 =A0 =A0 =A0 Attribute-Value Pairs For Provisioning Customer =
Equipment Supporting IPv4-Over-IPv6 Transitional Solutions<br>
Creation date: =A0 2013-03-11<br>
Group: =A0 =A0 =A0 =A0 =A0 Individual Submission<br>
Number of pages: 11<br>
URL: =A0 =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.ietf.org/internet-drafts=
/draft-zhou-dime-4over6-provisioning-00.txt" target=3D"_blank">http://www.i=
etf.org/internet-drafts/draft-zhou-dime-4over6-provisioning-00.txt</a><br>
Status: =A0 =A0 =A0 =A0 =A0<a href=3D"http://datatracker.ietf.org/doc/draft=
-zhou-dime-4over6-provisioning" target=3D"_blank">http://datatracker.ietf.o=
rg/doc/draft-zhou-dime-4over6-provisioning</a><br>
Htmlized: =A0 =A0 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-zhou-d=
ime-4over6-provisioning-00" target=3D"_blank">http://tools.ietf.org/html/dr=
aft-zhou-dime-4over6-provisioning-00</a><br>
<br>
<br>
Abstract:<br>
=A0 =A0During the transition from IPv4 to IPv6, customer equipment may have=
<br>
=A0 =A0to support one of the various transition methods that have been or<b=
r>
=A0 =A0are currently being defined for carrying IPv4 packets over IPv6.<br>
=A0 =A0Work is currently in progress to enumerate the information that need=
s<br>
=A0 =A0to be provisioned on a customer edge router to support a list of<br>
=A0 =A0transition techniques based on tunneling IPv4 in IPv6, with a view t=
o<br>
=A0 =A0defining reusable components for a reasonable transition path betwee=
n<br>
=A0 =A0these techniques. =A0To the extent that the provisioning is done<br>
=A0 =A0dynamically, AAA support is needed to provide the information to the=
<br>
=A0 =A0network server responsible for passing the information to the<br>
=A0 =A0customer equipment. =A0This document specifies Diameter attribute-va=
lue<br>
=A0 =A0pairs to be used for that purpose.<br>
<br>
<br>
<br>
<br>
The IETF Secretariat<br>
<br>
</div><br>

--047d7b2e0e713507ce04d79c763c--

From internet-drafts@ietf.org  Sun Mar 10 20:27:22 2013
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 25D6C21F89CB; Sun, 10 Mar 2013 20:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 7iUFLY92ttCa; Sun, 10 Mar 2013 20:27:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE7421F87C4; Sun, 10 Mar 2013 20:27:21 -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: 4.42
Message-ID: <20130311032721.7727.46863.idtracker@ietfa.amsl.com>
Date: Sun, 10 Mar 2013 20:27:21 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-mesh-mib-03.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, 11 Mar 2013 03:27:22 -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 Management Information Base (MIB)
	Author(s)       : Yong Cui
                          Jiang Dong
                          Peng Wu
                          Mingwei Xu
	Filename        : draft-ietf-softwire-mesh-mib-03.txt
	Pages           : 15
	Date            : 2013-03-10

Abstract:
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular it defines objects for managing softwire mesh
   [RFC5565].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-softwire-mesh-mib

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-softwire-mesh-mib-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-mesh-mib-03


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


From ot@cisco.com  Mon Mar 11 11:29:00 2013
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 DB02421F8D68 for <softwires@ietfa.amsl.com>; Mon, 11 Mar 2013 11:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 lhqQY6QmnE4v for <softwires@ietfa.amsl.com>; Mon, 11 Mar 2013 11:28:58 -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 2DBD321F8D6A for <softwires@ietf.org>; Mon, 11 Mar 2013 11:28:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1838; q=dns/txt; s=iport; t=1363026538; x=1364236138; h=from:content-transfer-encoding:subject:message-id:date: to:mime-version; bh=6v6YIfKT8cmR/mlCx4QwZImLQGO8Ot6v0HZvrrbVLhc=; b=WtgXjYpgHRJfA9HbNJqteBIGZSJAVcF8pnOWaFmmaIevxe8LqKS0iXez YO3LQOsA0DPkMNv5csm1qzYiMJVmKKzaKJKEk2CJknRsWm/HdcCxxT4wm zF1MFI+Ttfrndkkssnd9rv82Xi2RppTxjsccaH0Yxz/kLBACP46Dw/oSH k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAEQhPlGQ/khR/2dsb2JhbABDxkEWdIJqgX2IJp1foR6NZ4QNYQOIco1jkHWDKB4
X-IronPort-AV: E=Sophos;i="4.84,825,1355097600"; d="scan'208";a="81157964"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 11 Mar 2013 18:28:56 +0000
Received: from dhcp-10-61-102-101.cisco.com (dhcp-10-61-102-101.cisco.com [10.61.102.101]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2BISslm005642 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <softwires@ietf.org>; Mon, 11 Mar 2013 18:28:56 GMT
From: Ole Troan <ot@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>
Date: Mon, 11 Mar 2013 13:28:54 -0500
To: Softwires WG <softwires@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [Softwires] MAP tracker issues
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, 11 Mar 2013 18:29:00 -0000

hi,

as agreed in the meeting here is the summary of the discussion of the =
MAP open issues.
the plan is to leave these open for discussion for a week (until next =
Monday),
then issue revision -05, that we will ask to be last called in the WG.

#18     Title and file name of the MAP-E draft need to be updated      =20=

          No-one in the room objected to keeping name as is.
          Close ticket.

#19     IPv4 address superfluous in MAP-E Interface IDs map-e            =
      =20
          No one in the room objected to keeping interface-id as is in =
revision 04.
          Close ticket.

#21     Fragmentation must not be handled according to RFC 2473 map-e    =
      =20
          It is an issue, but it is a generic problem that should be =
fixed in a RFC2473bis.
          Have descriptive text in the MAP document describing the issue =
and referencing RFC4459.

          Current proposed text:
          "Multiple BRs using the same anycast source address could send
   fragmented packets to the same CE at the same time.  If the
   fragmented packets from different BRs happen to use the same fragment
   ID, incorrect reassembly might occur.  See [RFC4459] for an analysis
   of the problem.  Section 3.4 suggests solving the problem by=20
   fragmenting the inner packet."

          Close ticket with above text.
          Chairs to consider RFC2473bis
        =20
#25     Maintain or remove MAP1:1 Mode?
          Remove section 7.4 (Address Independence). Rename 1:1 example.

- Offset 4 versus 6.
  Discussion on value of wasting 3000 port versus simplicity of nibble =
alignment.
  No objection to moving default offset to 6 (from 4 in revision 04)

- Updated text for appendix B
  Tom Taylor to propose updates to appendix B (GMA appendix).

cheers,
Ole




From satoru.matsushima@gmail.com  Wed Mar 13 01:39:31 2013
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 72F1721F85D8 for <softwires@ietfa.amsl.com>; Wed, 13 Mar 2013 01:39:31 -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 3OIRT6PfNAPA for <softwires@ietfa.amsl.com>; Wed, 13 Mar 2013 01:39:31 -0700 (PDT)
Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFF921F85C0 for <softwires@ietf.org>; Wed, 13 Mar 2013 01:39:31 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id um15so799017pbc.14 for <softwires@ietf.org>; Wed, 13 Mar 2013 01:39:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=tuX3B9IVI6lQCzm3WNa6ntLyc8Bigs2bHy1oty4EEok=; b=d4QdeKnBia37T+NIso9lpwm4XgTl+ntDtUCI6HvYuzOnz8PIUFngoxAxEpkyeY0oS6 Vy/WoalHQ4CQdPlvknIhe4DmvwcCsheKxIz48Y+AGOC1HcnpacorJZch6degp8kfEprY sIhiLi6IP2ANpyrHvk4Tgi029qIIomA1DOEYYe1OLl3B/eCh44zBBleYEDRZs1CH235d y93z7DlBDeldRV7jmFzgzsVSfBrZwSYc9yJacmf6FuBnfEhjcAojdIZZR5nRijnnxzay YeYBNACOyIGmNvn9w7TstWzwnk70HqyC1Ai5FfcujJ//0sWLibaQyfZyGqbS5eyqyJzZ cO6g==
X-Received: by 10.68.91.66 with SMTP id cc2mr44539967pbb.51.1363163970693; Wed, 13 Mar 2013 01:39:30 -0700 (PDT)
Received: from ?IPv6:2001:df8::64:e03b:5b20:a418:2a3e? ([2001:df8:0:64:e03b:5b20:a418:2a3e]) by mx.google.com with ESMTPS id ql7sm13092279pbb.2.2013.03.13.01.39.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Mar 2013 01:39:28 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>
Date: Wed, 13 Mar 2013 17:39:25 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com>
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP tracker issues
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, 13 Mar 2013 08:39:31 -0000

Hi, I couldn't make comment during meeting but,

On 2013/03/12, at 3:28, Ole Troan <ot@cisco.com> wrote:

> - Offset 4 versus 6.
>  Discussion on value of wasting 3000 port versus simplicity of nibble =
alignment.
>  No objection to moving default offset to 6 (from 4 in revision 04)

Does anyone have a evaluated result of NAT performance difference in the =
number of derived port range?=20
ie. 63 port ranges (6 bits offset) vs 15 port ranges (4 bit offset) on a =
CPE.

It would be better to see the result which show it could be negligible =
with the updated text.

cheers,
--satoru=

From ot@cisco.com  Wed Mar 13 06:52:24 2013
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 7BEDA21F8D22 for <softwires@ietfa.amsl.com>; Wed, 13 Mar 2013 06:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 BlOzRqh+G7kO for <softwires@ietfa.amsl.com>; Wed, 13 Mar 2013 06:52:23 -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 A612C21F8D28 for <softwires@ietf.org>; Wed, 13 Mar 2013 06:52:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1231; q=dns/txt; s=iport; t=1363182741; x=1364392341; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=b1gpFXkodPX299GB/Vpw5m03xk75PrjnMh1OyGNcWfs=; b=ERxuqUkbmh2+IYY3Zh5R41ZL1d8eOp9BEApj6iJKyed1CGtEp2OR6rEq JEmimsBa43/jOS8VFCFn8UEchiH7WFUst8OXKV8BhxjbLCL4HQWbIbNDV fTtyYifE+noINScdGUnuAnYAqZSS5cxdisTtuGeIP7t+RDpnC5sCqVV2g U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEmEQFGQ/khL/2dsb2JhbABDxHuBVhZ0gikBAQEDATo/BQsLRlcGiCEGwhQXjlozB4JfYQOWVpB2gyYg
X-IronPort-AV: E=Sophos;i="4.84,837,1355097600"; d="scan'208";a="81234643"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 13 Mar 2013 13:51:58 +0000
Received: from dhcp-10-61-103-142.cisco.com (dhcp-10-61-103-142.cisco.com [10.61.103.142]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2DDpvGE023966 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 13 Mar 2013 13:51:58 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ole Troan <ot@cisco.com>
In-Reply-To: <7921F977B17D5B49B8DCC955A339D2F02AA85646@US70UWXCHMBA06.zam.alcatel-lucent.com>
Date: Wed, 13 Mar 2013 09:51:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6F56389-4E78-4452-B9B5-36441C1C522C@cisco.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA85646@US70UWXCHMBA06.zam.alcatel-lucent.com>
To: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1499)
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] softwire-map-04
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, 13 Mar 2013 13:52:24 -0000

Kris,

> I think the following needs to be corrected in the softwire-map draft:
> =20
> MAP Configuration
> =20
>    For a given MAP domain, the BR and CE MUST be configured with the
>    following MAP elements.  The configured values for these elements =
are
>    identical for all CEs and BRs within a given MAP domain.
> =20
>    o  The End-User IPv6 prefix (Part of the normal IPv6 provisioning).
> =20
>    o  The Basic Mapping Rule and optionally the Forwarding Mapping
>       Rules, including the Rule IPv6 prefix, Rule IPv4 prefix, and
>       Length of EA bits
> =20
>    o  The IPv6 address of the MAP BR.
> =20
>    o  Hub and spoke mode or Mesh mode.  (If all traffic should be sent
>       to the BR, or if direct CE to CE traffic should be supported).
> =20
> =20
> The end-user IPv6 prefix is not identical for all CEs. On the =
contrary, it must be unique per CE. For example uniqueness is reflected =
in EA bits in case of shared IPv4 address.

I have read through section 7 again, and I think that we can remove the =
first bullet.
the requirement for the End-User prefix is described separately already =
in 7.1

is that acceptable as a resolution to you?

Best regards,
Ole


From kristian.poscic@alcatel-lucent.com  Wed Mar 13 06:54:15 2013
Return-Path: <kristian.poscic@alcatel-lucent.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 A117E21F84DF for <softwires@ietfa.amsl.com>; Wed, 13 Mar 2013 06:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 ES4X42r6lOOo for <softwires@ietfa.amsl.com>; Wed, 13 Mar 2013 06:54:15 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id E8C0D21F8454 for <softwires@ietf.org>; Wed, 13 Mar 2013 06:54:14 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r2DDrMKh017933 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 13 Mar 2013 14:54:12 +0100
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (135.5.2.48) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 13 Mar 2013 14:53:57 +0100
Received: from US70UWXCHMBA06.zam.alcatel-lucent.com ([169.254.11.15]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.02.0247.003; Wed, 13 Mar 2013 09:53:55 -0400
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: Ole Troan <ot@cisco.com>
Thread-Topic: [Softwires] softwire-map-04
Thread-Index: Ac4cRzx4k9a2n2iJSeKTM9VpqoT93ADzDdYAAAhSJVA=
Date: Wed, 13 Mar 2013 13:53:55 +0000
Message-ID: <7921F977B17D5B49B8DCC955A339D2F02AA8C3D2@US70UWXCHMBA06.zam.alcatel-lucent.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA85646@US70UWXCHMBA06.zam.alcatel-lucent.com> <D6F56389-4E78-4452-B9B5-36441C1C522C@cisco.com>
In-Reply-To: <D6F56389-4E78-4452-B9B5-36441C1C522C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] softwire-map-04
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, 13 Mar 2013 13:54:15 -0000

Sure. That will work.

-----Original Message-----
From: Ole Troan [mailto:ot@cisco.com]=20
Sent: Wednesday, March 13, 2013 6:52 AM
To: Poscic, Kristian (Kristian)
Cc: softwires@ietf.org
Subject: Re: [Softwires] softwire-map-04

Kris,

> I think the following needs to be corrected in the softwire-map draft:
> =20
> MAP Configuration
> =20
>    For a given MAP domain, the BR and CE MUST be configured with the
>    following MAP elements.  The configured values for these elements are
>    identical for all CEs and BRs within a given MAP domain.
> =20
>    o  The End-User IPv6 prefix (Part of the normal IPv6 provisioning).
> =20
>    o  The Basic Mapping Rule and optionally the Forwarding Mapping
>       Rules, including the Rule IPv6 prefix, Rule IPv4 prefix, and
>       Length of EA bits
> =20
>    o  The IPv6 address of the MAP BR.
> =20
>    o  Hub and spoke mode or Mesh mode.  (If all traffic should be sent
>       to the BR, or if direct CE to CE traffic should be supported).
> =20
> =20
> The end-user IPv6 prefix is not identical for all CEs. On the contrary, i=
t must be unique per CE. For example uniqueness is reflected in EA bits in =
case of shared IPv4 address.

I have read through section 7 again, and I think that we can remove the fir=
st bullet.
the requirement for the End-User prefix is described separately already in =
7.1

is that acceptable as a resolution to you?

Best regards,
Ole


From kristian.poscic@alcatel-lucent.com  Fri Mar 15 09:57:32 2013
Return-Path: <kristian.poscic@alcatel-lucent.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 5800021F8556 for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 09:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 vYUXZ7UAuaoA for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 09:57:29 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id C7BED21F8640 for <softwires@ietf.org>; Fri, 15 Mar 2013 09:57:21 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r2FGvHM6014654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <softwires@ietf.org>; Fri, 15 Mar 2013 11:57:17 -0500 (CDT)
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id r2FGvHAF032736 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <softwires@ietf.org>; Fri, 15 Mar 2013 12:57:17 -0400
Received: from US70UWXCHMBA06.zam.alcatel-lucent.com ([169.254.11.15]) by US70TWXCHHUB03.zam.alcatel-lucent.com ([135.5.2.35]) with mapi id 14.02.0247.003; Fri, 15 Mar 2013 12:57:17 -0400
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: map domain ; mesh BMR =>DHCP flag F
Thread-Index: Ac4hmnuNR9q7j+yYTbu7rpFJdjtw/A==
Date: Fri, 15 Mar 2013 16:57:16 +0000
Message-ID: <7921F977B17D5B49B8DCC955A339D2F02AA8F0EB@US70UWXCHMBA06.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: multipart/alternative; boundary="_000_7921F977B17D5B49B8DCC955A339D2F02AA8F0EBUS70UWXCHMBA06z_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: [Softwires] map domain ; mesh BMR =>DHCP flag F
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, 15 Mar 2013 16:57:32 -0000

--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F0EBUS70UWXCHMBA06z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

1)      The MAP domain definition should be consolidated across the three d=
rafts (map-e, map-t and map-deployment).

For example the map-e draft defines under the terminology section the MAP d=
omain as:

MAP domain:             One or more MAP CEs and BRs connected to the
                           same virtual link.  A service provider may
                           deploy a single MAP domain, or may utilize
                           multiple MAP domains.


Map-t draft defines is as (under terminology section):

MAP domain:             One or more MAP CEs and BRs connected to the
                           same IPv6 network.  A service provider may
                           deploy a single MAP domain, or may utilize
                           multiple MAP domains.


While map-deployment draft (sec 4.2 Building the Map Domain) says:

One MAP domain shares a common BR and has the same set of
   BMRs, FMRs and DMR, and it can be further divided into multiple sub-
   domains when multiple IPv4 subnets are deployed in one MAP domain.


So we go from virtual link and the 'same IPv6 network' concept with multipl=
e BRs per MAP domain (in map-e/t drafts) to a common BR per map domain and =
subdomains concepts in map-deployment draft.
What does 'same IPv6 network'  mean in the map-t draft? In other  words doe=
s this mean that multiple MAP domains cannot co-exists within the boundary =
of an IPv6 network and that an operator should construct a separate IPv6 ne=
twork for another MAP domain? I don't think this is what 'same IPv6 network=
' means but it may come out as such.

Then the map-deployment draft says that the MAP domain should share common =
BR - which I don't think is correct (for redundancy and load sharing purpos=
es).
And then the subdomains that are referred to in the map-deployment draft, t=
hey correspond simply to BMRs. But if this is so, then we should define sub=
domain as such (subdomain =3D BMR). Or keep referring to BMRs instead of su=
bdomains.

Rather than trying to answer the question' what is the MAP domain?' I'm try=
ing to ask myself 'what do I need in order to create multiple MAP domains?'=
 I think the answer is that I need multiple (sets) of BRs (and correspondin=
g CEs) on the same IPv6 or different IPv6 network, each such set of BRs  mu=
st contain distinct BMR and FMR rules (i.e. no overlapping of BMR/FMR rules=
 between the sets of BRs to which MAP domains are tied to).



2)      Mesh topology is implicitly enabled in cases where FMRs are provisi=
oned (configured). But the mesh topology can be also explicitly configured =
in case that we have only BMR.  Map-dhcp draft talks about this. Section 4.=
3 says this:
o  F-Flag: 1 bit field that specifies whether the rule is to be used
      for forwarding (FMR). 0x0 =3D This rule is NOT used as a FMR. 0x1 =3D
      This rule is also a FMR.

Maybe I missed this, but I think that map-e/t drafts do not talk about this=
 very much.  Shouldn't this be specified as part of the optional MAP rule. =
We talk about the first 4bits (by default) of the port range being set to 0=
 (to exclude ports 0 - 4K-1) but we do not talk about this mesh bit in map-=
e/t

Thanks,
Kris


--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F0EBUS70UWXCHMBA06z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1906794723;
	mso-list-type:hybrid;
	mso-list-template-ids:-2091995636 67698705 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The MAP domain definition should be consolidated ac=
ross the three drafts (map-e, map-t and map-deployment).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For example the map-e draft defines under the termin=
ology section the MAP domain as:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">MAP domain:&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; One or more MAP CEs =
and BRs connected to the<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same virtual link.&nbs=
p; A service provider may<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; deploy a single MAP do=
main, or may utilize<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multiple MAP domains.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Map-t draft defines is as (under terminology section=
):<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">MAP domain:&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; One or more MAP CEs =
and BRs connected to the<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same IPv6 network.&nbs=
p; A service provider may<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; deploy a single MAP do=
main, or may utilize<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multiple MAP domains.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While map-deployment draft (sec 4.2 Building the Map=
 Domain) says:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">One MAP domain shares a commo=
n BR and has the same set of<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; BMRs, FMRs and D=
MR, and it can be further divided into multiple sub-<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; domains when mul=
tiple IPv4 subnets are deployed in one MAP domain.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So we go from virtual link and the &#8216;same IPv6 =
network&#8217; concept with multiple BRs per MAP domain (in map-e/t drafts)=
 to a common BR per map domain and subdomains concepts in map-deployment dr=
aft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal">What does &#8216;same IPv6 network&#8217;&nbsp; mean=
 in the map-t draft? In other&nbsp; words does this mean that multiple MAP =
domains cannot co-exists within the boundary of an IPv6 network and that an=
 operator should construct a separate IPv6 network for another
 MAP domain? I don&#8217;t think this is what &#8216;same IPv6 network&#821=
7; means but it may come out as such.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Then the map-deployment draft says that the MAP doma=
in should share common BR &#8211; which I don&#8217;t think is correct (for=
 redundancy and load sharing purposes).<o:p></o:p></p>
<p class=3D"MsoNormal">And then the subdomains that are referred to in the =
map-deployment draft, they correspond simply to BMRs. But if this is so, th=
en we should define subdomain as such (subdomain =3D BMR). Or keep referrin=
g to BMRs instead of subdomains.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Rather than trying to answer the question&#8217; wha=
t is the MAP domain?&#8217; I&#8217;m trying to ask myself &#8216;what do I=
 need in order to create multiple MAP domains?&#8217; I think the answer is=
 that I need multiple (sets) of BRs (and corresponding CEs) on the
 same IPv6 or different IPv6 network, each such set of BRs &nbsp;must conta=
in distinct BMR and FMR rules (i.e. no overlapping of BMR/FMR rules between=
 the sets of BRs to which MAP domains are tied to).
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Mesh topology is implicitly enabled in cases where =
FMRs are provisioned (configured). But the mesh topology can be also explic=
itly configured in case that we have only BMR.&nbsp; Map-dhcp draft talks a=
bout this. Section 4.3 says this:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in;line-height:14.4pt"><span=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">o&nbsp; F-F=
lag: 1 bit field that specifies whether the rule is to be used<o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in;line-height:14.4pt"><span=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; for forwarding (FMR). 0x0 =3D This rule is NOT used as =
a FMR. 0x1 =3D<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"font-size=
:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 This rule is also a FMR.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"font-size=
:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in">Maybe I missed this, but=
 I think that map-e/t drafts do not talk about this very much. &nbsp;Should=
n&#8217;t this be specified as part of the optional MAP rule. We talk about=
 the first 4bits (by default) of the port range
 being set to 0 (to exclude ports 0 - 4K-1) but we do not talk about this m=
esh bit in map-e/t
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in">Kris <o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F0EBUS70UWXCHMBA06z_--

From kristian.poscic@alcatel-lucent.com  Fri Mar 15 10:03:38 2013
Return-Path: <kristian.poscic@alcatel-lucent.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 1F77C21F85AD for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 10:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 ZdzEFabggkd9 for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 10:03:35 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 3905921F858B for <softwires@ietf.org>; Fri, 15 Mar 2013 10:03:30 -0700 (PDT)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r2FH3SK7021332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <softwires@ietf.org>; Fri, 15 Mar 2013 12:03:29 -0500 (CDT)
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id r2FH3SaU027256 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <softwires@ietf.org>; Fri, 15 Mar 2013 13:03:28 -0400
Received: from US70UWXCHMBA06.zam.alcatel-lucent.com ([169.254.11.15]) by US70TWXCHHUB03.zam.alcatel-lucent.com ([135.5.2.35]) with mapi id 14.02.0247.003; Fri, 15 Mar 2013 13:03:28 -0400
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: map domain ; mesh BMR =>DHCP flag F
Thread-Index: Ac4hmnuNR9q7j+yYTbu7rpFJdjtw/AAA9TmQ
Date: Fri, 15 Mar 2013 17:03:27 +0000
Message-ID: <7921F977B17D5B49B8DCC955A339D2F02AA8F11E@US70UWXCHMBA06.zam.alcatel-lucent.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA8F0EB@US70UWXCHMBA06.zam.alcatel-lucent.com>
In-Reply-To: <7921F977B17D5B49B8DCC955A339D2F02AA8F0EB@US70UWXCHMBA06.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: multipart/alternative; boundary="_000_7921F977B17D5B49B8DCC955A339D2F02AA8F11EUS70UWXCHMBA06z_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [Softwires] map domain ; mesh BMR =>DHCP flag F
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, 15 Mar 2013 17:03:38 -0000

--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F11EUS70UWXCHMBA06z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

BTW - section 3 of the map-dhcp draft says:

A Basic Mapping Rule (BMR).  This rule governs the MAP
      configuration of the CE, including that of completing the CE's MAP
      IPv6 address, as well as deriving the CEs IPv4 parameters.  Key
      parameters of a BMR include: i) The IPv4 Prefix - Used to derive
      the CE's IPv4 address; ii) The Embedded Address bit length - Used
      to derive how many, if any, of the CE's IPv6 address is mapped to
      the IPv4 address. iii) The IPv6 prefix - used to determine the
      CE's IPv6 MAP domain prefix that is to form the base for the CE's
      MAP address.  The BMR is an optional rule for a MAP CE.

Last sentence is not correct. It should state 'mandatory'.

From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On Beh=
alf Of Poscic, Kristian (Kristian)
Sent: Friday, March 15, 2013 9:57 AM
To: softwires@ietf.org
Subject: [Softwires] map domain ; mesh BMR =3D>DHCP flag F


1)      The MAP domain definition should be consolidated across the three d=
rafts (map-e, map-t and map-deployment).

For example the map-e draft defines under the terminology section the MAP d=
omain as:

MAP domain:             One or more MAP CEs and BRs connected to the
                           same virtual link.  A service provider may
                           deploy a single MAP domain, or may utilize
                           multiple MAP domains.


Map-t draft defines is as (under terminology section):

MAP domain:             One or more MAP CEs and BRs connected to the
                           same IPv6 network.  A service provider may
                           deploy a single MAP domain, or may utilize
                           multiple MAP domains.


While map-deployment draft (sec 4.2 Building the Map Domain) says:

One MAP domain shares a common BR and has the same set of
   BMRs, FMRs and DMR, and it can be further divided into multiple sub-
   domains when multiple IPv4 subnets are deployed in one MAP domain.


So we go from virtual link and the 'same IPv6 network' concept with multipl=
e BRs per MAP domain (in map-e/t drafts) to a common BR per map domain and =
subdomains concepts in map-deployment draft.

What does 'same IPv6 network'  mean in the map-t draft? In other  words doe=
s this mean that multiple MAP domains cannot co-exists within the boundary =
of an IPv6 network and that an operator should construct a separate IPv6 ne=
twork for another MAP domain? I don't think this is what 'same IPv6 network=
' means but it may come out as such.

Then the map-deployment draft says that the MAP domain should share common =
BR - which I don't think is correct (for redundancy and load sharing purpos=
es).
And then the subdomains that are referred to in the map-deployment draft, t=
hey correspond simply to BMRs. But if this is so, then we should define sub=
domain as such (subdomain =3D BMR). Or keep referring to BMRs instead of su=
bdomains.

Rather than trying to answer the question' what is the MAP domain?' I'm try=
ing to ask myself 'what do I need in order to create multiple MAP domains?'=
 I think the answer is that I need multiple (sets) of BRs (and correspondin=
g CEs) on the same IPv6 or different IPv6 network, each such set of BRs  mu=
st contain distinct BMR and FMR rules (i.e. no overlapping of BMR/FMR rules=
 between the sets of BRs to which MAP domains are tied to).



2)      Mesh topology is implicitly enabled in cases where FMRs are provisi=
oned (configured). But the mesh topology can be also explicitly configured =
in case that we have only BMR.  Map-dhcp draft talks about this. Section 4.=
3 says this:
o  F-Flag: 1 bit field that specifies whether the rule is to be used
      for forwarding (FMR). 0x0 =3D This rule is NOT used as a FMR. 0x1 =3D
      This rule is also a FMR.

Maybe I missed this, but I think that map-e/t drafts do not talk about this=
 very much.  Shouldn't this be specified as part of the optional MAP rule. =
We talk about the first 4bits (by default) of the port range being set to 0=
 (to exclude ports 0 - 4K-1) but we do not talk about this mesh bit in map-=
e/t

Thanks,
Kris


--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F11EUS70UWXCHMBA06z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1906794723;
	mso-list-type:hybrid;
	mso-list-template-ids:-2091995636 67698705 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">BTW &#8211; section 3 =
of the map-dhcp draft says:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">A Basic Mapping Rule (BMR).&n=
bsp; This rule governs the MAP<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; configuration of the CE, including that of completing the CE's MAP<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; IPv6 address, as well as deriving the CEs IPv4 parameters.&nbsp; Key<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; parameters of a BMR include: i) The IPv4 Prefix - Used to derive<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; the CE's IPv4 address; ii) The Embedded Address bit length - Used<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; to derive how many, if any, of the CE's IPv6 address is mapped to<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; the IPv4 address. iii) The IPv6 prefix - used to determine the<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; CE's IPv6 MAP domain prefix that is to form the base for the CE's<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; MAP address.&nbsp; The BMR is an optional rule for a MAP CE.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Last sentence is not c=
orrect. It should state &#8216;mandatory&#8217;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> softwire=
s-bounces@ietf.org [mailto:softwires-bounces@ietf.org]
<b>On Behalf Of </b>Poscic, Kristian (Kristian)<br>
<b>Sent:</b> Friday, March 15, 2013 9:57 AM<br>
<b>To:</b> softwires@ietf.org<br>
<b>Subject:</b> [Softwires] map domain ; mesh BMR =3D&gt;DHCP flag F<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The MAP domain definition should be consolidated ac=
ross the three drafts (map-e, map-t and map-deployment).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For example the map-e draft defines under the termin=
ology section the MAP domain as:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">MAP domain:&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; One or more MAP CEs =
and BRs connected to the<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same virtual link.&nbs=
p; A service provider may<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; deploy a single MAP do=
main, or may utilize<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multiple MAP domains.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Map-t draft defines is as (under terminology section=
):<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">MAP domain:&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; One or more MAP CEs =
and BRs connected to the<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same IPv6 network.&nbs=
p; A service provider may<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; deploy a single MAP do=
main, or may utilize<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multiple MAP domains.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While map-deployment draft (sec 4.2 Building the Map=
 Domain) says:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">One MAP domain shares a commo=
n BR and has the same set of<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; BMRs, FMRs and D=
MR, and it can be further divided into multiple sub-<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; domains when mul=
tiple IPv4 subnets are deployed in one MAP domain.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So we go from virtual link and the &#8216;same IPv6 =
network&#8217; concept with multiple BRs per MAP domain (in map-e/t drafts)=
 to a common BR per map domain and subdomains concepts in map-deployment dr=
aft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">What does &#8216;same IPv6 network&#8217;&nbsp; mean=
 in the map-t draft? In other&nbsp; words does this mean that multiple MAP =
domains cannot co-exists within the boundary of an IPv6 network and that an=
 operator should construct a separate IPv6 network for another
 MAP domain? I don&#8217;t think this is what &#8216;same IPv6 network&#821=
7; means but it may come out as such.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Then the map-deployment draft says that the MAP doma=
in should share common BR &#8211; which I don&#8217;t think is correct (for=
 redundancy and load sharing purposes).<o:p></o:p></p>
<p class=3D"MsoNormal">And then the subdomains that are referred to in the =
map-deployment draft, they correspond simply to BMRs. But if this is so, th=
en we should define subdomain as such (subdomain =3D BMR). Or keep referrin=
g to BMRs instead of subdomains.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Rather than trying to answer the question&#8217; wha=
t is the MAP domain?&#8217; I&#8217;m trying to ask myself &#8216;what do I=
 need in order to create multiple MAP domains?&#8217; I think the answer is=
 that I need multiple (sets) of BRs (and corresponding CEs) on the
 same IPv6 or different IPv6 network, each such set of BRs &nbsp;must conta=
in distinct BMR and FMR rules (i.e. no overlapping of BMR/FMR rules between=
 the sets of BRs to which MAP domains are tied to).
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Mesh topology is implicitly enabled in cases where =
FMRs are provisioned (configured). But the mesh topology can be also explic=
itly configured in case that we have only BMR.&nbsp; Map-dhcp draft talks a=
bout this. Section 4.3 says this:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in;line-height:14.4pt"><span=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">o&nbsp; F-F=
lag: 1 bit field that specifies whether the rule is to be used<o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in;line-height:14.4pt"><span=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; for forwarding (FMR). 0x0 =3D This rule is NOT used as =
a FMR. 0x1 =3D<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"font-size=
:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 This rule is also a FMR.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"font-size=
:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in">Maybe I missed this, but=
 I think that map-e/t drafts do not talk about this very much. &nbsp;Should=
n&#8217;t this be specified as part of the optional MAP rule. We talk about=
 the first 4bits (by default) of the port range
 being set to 0 (to exclude ports 0 - 4K-1) but we do not talk about this m=
esh bit in map-e/t
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in">Kris <o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F11EUS70UWXCHMBA06z_--

From satoru.matsushima@gmail.com  Fri Mar 15 10:33:05 2013
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 0C4CC21F88B1 for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 10:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GobqDhCFDZc5 for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 10:33:04 -0700 (PDT)
Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by ietfa.amsl.com (Postfix) with ESMTP id 04DFC21F882F for <softwires@ietf.org>; Fri, 15 Mar 2013 10:33:03 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id gm6so2932855lbb.26 for <softwires@ietf.org>; Fri, 15 Mar 2013 10:33:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=E2jrH8iyr3AtXvurKq6MLKLTFDZu5l6icFSnzh8mA74=; b=jj6NCP9ugf9EbyR5r2tMZ5Eccvl9Giw9poGNLMUF+QEoUiURtRW87+dXX/FDJ2P3fc k8k/7tueelq7zmRIzpxoREfxxS3oMXRwbxOAnQbua/JHWTG5w0ScVahsyw8rQ0qB0JNy BbgBftPCEOX7FVLizVXmuZu+I4/TCazy8BHbxcqa3L6D/eocR/eroUvnrhaLwvmxHqTm dF6EYU+QMGCvEZi0fNDySTaLXPpNtfNWlUEWpv2Y4tdMPQUopsZRaWqvSVH2LG64tKHx B/1k/DyEzj2R3W0DmW2zlz8nkefayehF0+fBcJrCkLcJumqpwFXE9wPMQ7N/fmV3qTnR Wv1w==
MIME-Version: 1.0
X-Received: by 10.152.46.131 with SMTP id v3mr6424147lam.57.1363368782943; Fri, 15 Mar 2013 10:33:02 -0700 (PDT)
Received: by 10.112.81.168 with HTTP; Fri, 15 Mar 2013 10:33:02 -0700 (PDT)
In-Reply-To: <7921F977B17D5B49B8DCC955A339D2F02AA8F0EB@US70UWXCHMBA06.zam.alcatel-lucent.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA8F0EB@US70UWXCHMBA06.zam.alcatel-lucent.com>
Date: Sat, 16 Mar 2013 02:33:02 +0900
Message-ID: <CAFwJXX73v3cJg2r6m6fJs_+G_EJ-oGNVr=dMbYCgaP=wB2QaHg@mail.gmail.com>
From: Satoru Matsushima <satoru.matsushima@gmail.com>
To: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] map domain ; mesh BMR =>DHCP flag F
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, 15 Mar 2013 17:33:05 -0000

In my view, the MAP-E text, which should be followed by other MAP
related document.

cheers,
--satoru

On Sat, Mar 16, 2013 at 1:57 AM, Poscic, Kristian (Kristian)
<kristian.poscic@alcatel-lucent.com> wrote:
> 1)      The MAP domain definition should be consolidated across the three
> drafts (map-e, map-t and map-deployment).
>
>
>
> For example the map-e draft defines under the terminology section the MAP
> domain as:
>
>
>
> MAP domain:             One or more MAP CEs and BRs connected to the
>
>                            same virtual link.  A service provider may
>
>                            deploy a single MAP domain, or may utilize
>
>                            multiple MAP domains.
>
>
>
>
>
> Map-t draft defines is as (under terminology section):
>
>
>
> MAP domain:             One or more MAP CEs and BRs connected to the
>
>                            same IPv6 network.  A service provider may
>
>                            deploy a single MAP domain, or may utilize
>
>                            multiple MAP domains.
>
>
>
>
>
> While map-deployment draft (sec 4.2 Building the Map Domain) says:
>
>
>
> One MAP domain shares a common BR and has the same set of
>
>    BMRs, FMRs and DMR, and it can be further divided into multiple sub-
>
>    domains when multiple IPv4 subnets are deployed in one MAP domain.
>
>
>
>
>
> So we go from virtual link and the =91same IPv6 network=92 concept with m=
ultiple
> BRs per MAP domain (in map-e/t drafts) to a common BR per map domain and
> subdomains concepts in map-deployment draft.
>
> What does =91same IPv6 network=92  mean in the map-t draft? In other  wor=
ds does
> this mean that multiple MAP domains cannot co-exists within the boundary =
of
> an IPv6 network and that an operator should construct a separate IPv6
> network for another MAP domain? I don=92t think this is what =91same IPv6
> network=92 means but it may come out as such.
>
>
>
> Then the map-deployment draft says that the MAP domain should share commo=
n
> BR =96 which I don=92t think is correct (for redundancy and load sharing
> purposes).
>
> And then the subdomains that are referred to in the map-deployment draft,
> they correspond simply to BMRs. But if this is so, then we should define
> subdomain as such (subdomain =3D BMR). Or keep referring to BMRs instead =
of
> subdomains.
>
>
>
> Rather than trying to answer the question=92 what is the MAP domain?=92 I=
=92m
> trying to ask myself =91what do I need in order to create multiple MAP
> domains?=92 I think the answer is that I need multiple (sets) of BRs (and
> corresponding CEs) on the same IPv6 or different IPv6 network, each such =
set
> of BRs  must contain distinct BMR and FMR rules (i.e. no overlapping of
> BMR/FMR rules between the sets of BRs to which MAP domains are tied to).
>
>
>
>
>
> 2)      Mesh topology is implicitly enabled in cases where FMRs are
> provisioned (configured). But the mesh topology can be also explicitly
> configured in case that we have only BMR.  Map-dhcp draft talks about thi=
s.
> Section 4.3 says this:
>
> o  F-Flag: 1 bit field that specifies whether the rule is to be used
>
>       for forwarding (FMR). 0x0 =3D This rule is NOT used as a FMR. 0x1 =
=3D
>
>       This rule is also a FMR.
>
>
>
> Maybe I missed this, but I think that map-e/t drafts do not talk about th=
is
> very much.  Shouldn=92t this be specified as part of the optional MAP rul=
e. We
> talk about the first 4bits (by default) of the port range being set to 0 =
(to
> exclude ports 0 - 4K-1) but we do not talk about this mesh bit in map-e/t
>
>
>
> Thanks,
>
> Kris
>
>
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

From kristian.poscic@alcatel-lucent.com  Fri Mar 15 13:05:00 2013
Return-Path: <kristian.poscic@alcatel-lucent.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 BA9A221F86BA for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 13:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 NAt9tzIkXn6N for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 13:04:57 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 23ECA21F86B2 for <softwires@ietf.org>; Fri, 15 Mar 2013 13:04:52 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r2FK4pod026217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <softwires@ietf.org>; Fri, 15 Mar 2013 15:04:51 -0500 (CDT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id r2FK4om3019516 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <softwires@ietf.org>; Fri, 15 Mar 2013 16:04:51 -0400
Received: from US70UWXCHMBA06.zam.alcatel-lucent.com ([169.254.11.15]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.02.0247.003; Fri, 15 Mar 2013 16:04:50 -0400
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: map-deployment-01 draft
Thread-Index: Ac4htPYUxs81ID+jTCGeFOahVlm/Cw==
Date: Fri, 15 Mar 2013 20:04:50 +0000
Message-ID: <7921F977B17D5B49B8DCC955A339D2F02AA8F562@US70UWXCHMBA06.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: multipart/alternative; boundary="_000_7921F977B17D5B49B8DCC955A339D2F02AA8F562US70UWXCHMBA06z_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: [Softwires] map-deployment-01 draft
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, 15 Mar 2013 20:05:00 -0000

--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F562US70UWXCHMBA06z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


I was able to follow section 5.1 of this draft somewhat but then got comple=
tely lost at step B3.
It would really help if you can also describe the reason why are you perfor=
ming each step - in other words put more context around it. Otherwise, it w=
ill be very hard for the operators to follow this.

Maybe we can start from a more comprehensive example and you can include it=
 the draft along with your steps.
Here is my example and logic that I follow:


1)      Example requirement:

-          There are about 22,000 residual IPv4 addresses that needs to be =
translated via MAP.

-          Each  such address should have 4K ports available. Therefore, th=
e IP address sharing ratio is 16:1

-          The public IPv4 addresses that are available to the operator for=
 this translation are four  /24 subnets (11.11.11.0/24 , 12.12.12..0/24, 13=
.13.13.0/24 and 14.14.14.0/24)  and one /22 subnet (15.15.0.0/22).

-          The IPv6 prefix that is delegated to the operator is 2001:db8::/=
32 .

-          4K users (or CPEs corresponding to the residual IP addresses) wi=
ll get PD /56, the rest of the users will get PD /60.

-          The end-user-prefix and the rules will be delegated via DHCPv6 s=
erver

22,000 residual IP addresses in 16:1 sharing scenario could be covered with=
 two /24 subnets and one /22 subnet  =3D> (2 * 2^8 * 16 + 2^10 * 16 =3D 24,=
 576).

So Rule IPv4 prefix and EA bits length  will be:


1)      11.11.11.0/24    EA length: 12 bits  (8 bits for the IPv4 suffix an=
d 4 bits for PSID)    =3D> these users will get PD /56 (arbitrarily determi=
ned by the operator and in conformance with the requirement)

2)      12.12.12.0/24    EA length: 12 bits                                =
                                                              =3D> these us=
ers will get PD /60 (arbitrarily determined by the operator and in conforma=
nce with the requirement)

3)      15.15.0.0/22      EA length: 14 bits  (10 bits for IPv4 suffix and =
4 bits for PSID)          =3D> these users will get PD/60 (arbitrarily dete=
rmined by the operator and in conformance with the requirement)

That was the easy part. What we need to do now is to determine:

-          Rule IPv6 Prefix  (to complete BMR/FMR)

-          How will the end user DHCPv6 prefix (PD) be carved out by DHCP s=
erver (assumption is that DHCPv6 server delegates v6 prefix and Rules).

We will represents the bits in v6 address via the following graph (we will =
ignore irrelevant parts of the v6 addresses for this discussion and instead=
 consider only the bits /32 to /64):

                /32         /36         /40         /44         /48        =
 /52         /56         /60         /64
xxxx       xxxx       xxxx       xxxx       xxxx       xxxx       xxxx     =
  xxxx       xxxx
                                                                | |        =
  |                              |              |
                                                                |< --------=
EA=3D12-------->|              |                             1) this will c=
over subnet 1) ; EA bits extend from the PD length (/56) to the Rule IPv6 p=
refix length (/44)
                                                                    |      =
    |< ---------EA=3D12------ >|                              2) this will =
cover subnet 2);  EA bits extend from the PD length (/60) to the Rule IPv6 =
prefix length (/48)
                                                                    |< ----=
------------EA=3D14------ >|                               3) this will cov=
er subnet 3) ; EA bits extend from the PD length (/60) to the Rule IPv6 pre=
fix length (/46)

Now we have determined IPv6 Rule Prefix length for each of the three rules =
that we need to create.
The IPv4 Prefix Rule lengths are /44, /48 and /46 for the cases 1), 2) and =
3) respectively.

Now we need to determine how can each end user prefix be uniquely allocated=
 across all users (CEs). The only way to ensure this uniqueness is to ensur=
e that the portion of the IPv6 Rule prefix up to /44 (smallest Rule IPv6 pr=
efix length between all the rules in the MAP domain) is unique amongst all =
the rules.
So, the IPv6 Rule prefixes for our three cases will be (changing the part a=
bove /44):

1)      2001:db8:0000::/44

2)      2001:db8:0010::/48

3)      2001:db8:0020::/46

The last step is to ensure that the DHCPv6 server hands out proper end-user=
 prefixes (and along with the prefixes, the Rules are delegated as well).
So the DHCPv6 can be configured so that it is carving the prefixes from thr=
ee ranges:


1)      2001:db8:000x:xxyy::  (where x denotes carving part from /44 to /56=
 - the EA bits; 'y' denotes further subneting that is done on the CPE -> yy=
=3D00 for MAP prefix, the remaining combinations are reserved for CPE deleg=
ation to its clients)

2)      2001:db8:0100:xxxy::  (where x denotes carving part from /48 to /60=
 - the EA bits; 'y' denotes further subneting that is done on the CPE -> y=
=3D0 for MAP prefix, the remaining combinations are reserved for CPE delega=
tion to its clients)

3)      2001:db8:020w:xxxy::  (where x and two lower bits of 'w' denote car=
ving part from /46 to /60 - the EA bits; 'y' denotes further subneting that=
 is done on the CPE -> y=3D0 for MAP prefix, the remaining combinations are=
 reserved for CPE delegation to its clients)

Along with each user end prefix a BMR and a DMR will be delegated to the en=
d-users (so we will have a hub and spoke topology)

Also note that to cover the holes between the /48 and /44 for case 2) we ca=
n easily add 15 more /24 IPv4 prefixes by creating new IPv6 Rule by changin=
g bits between /44 and /48.
Similarly for case 3), we can create 3 more IPv6 rule prefixes (and add 3 m=
ore /22 IPv4 subnets) by changing bits between /46 and /48. This would allo=
w us to expand the coverage for residual IPs (although the purpose of NAT i=
s to minimize their use over time not to expand :)).





--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F562US70UWXCHMBA06z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:334115038;
	mso-list-type:hybrid;
	mso-list-template-ids:1626121252 251178834 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:636106870;
	mso-list-type:hybrid;
	mso-list-template-ids:1169455604 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:821850492;
	mso-list-type:hybrid;
	mso-list-template-ids:2124588226 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l3
	{mso-list-id:1118766342;
	mso-list-type:hybrid;
	mso-list-template-ids:-802666864 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l3:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l3:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l3:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l4
	{mso-list-id:1656254145;
	mso-list-type:hybrid;
	mso-list-template-ids:-845226590 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l4:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l4:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l4:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I was able to follow section 5.1 of this draft somew=
hat but then got completely lost at step B3.
<o:p></o:p></p>
<p class=3D"MsoNormal">It would really help if you can also describe the re=
ason why are you performing each step &#8211; in other words put more conte=
xt around it. Otherwise, it will be very hard for the operators to follow t=
his.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Maybe we can start from a more comprehensive example=
 and you can include it the draft along with your steps.
<o:p></o:p></p>
<p class=3D"MsoNormal">Here is my example and logic that I follow:<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l4 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Example requirement:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>There are about 22,000 residual IPv4 addresses that=
 needs to be translated via MAP.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>Each &nbsp;such address should have 4K ports availa=
ble. Therefore, the IP address sharing ratio is 16:1<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>The public IPv4 addresses that are available to the=
 operator for this translation are four &nbsp;/24 subnets (11.11.11.0/24 , =
12.12.12..0/24, 13.13.13.0/24 and 14.14.14.0/24) &nbsp;and one /22 subnet (=
15.15.0.0/22).<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>The IPv6 prefix that is delegated to the operator i=
s 2001:db8::/32 .<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>4K users (or CPEs corresponding to the residual IP =
addresses) will get PD /56, the rest of the users will get PD /60.<o:p></o:=
p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>The end-user-prefix and the rules will be delegated=
 via DHCPv6 server &nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">22,000 residual IP addresses in 16:1 sharing scenari=
o could be covered with two /24 subnets and one /22 subnet&nbsp; =3D&gt; (2=
 * 2^8 * 16 &#43; 2^10 * 16 =3D 24, 576).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So Rule IPv4 prefix and EA bits length &nbsp;will be=
:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo3"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>11.11.11.0/24&nbsp;&nbsp;&nbsp; EA length: 12 bits&=
nbsp; (8 bits for the IPv4 suffix and 4 bits for PSID)&nbsp;&nbsp;&nbsp; =
=3D&gt; these users will get PD /56 (arbitrarily determined by the operator=
 and in conformance with the requirement)<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo3"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>12.12.12.0/24&nbsp; &nbsp;&nbsp;EA length: 12 bits&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&gt; these users will get PD /60 (arbit=
rarily determined by the operator and in conformance with the requirement)<=
o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo3"><![if !supportLists]><span style=3D"mso-list:Ignore">3)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>15.15.0.0/22 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;EA lengt=
h: 14 bits&nbsp; (10 bits for IPv4 suffix and 4 bits for PSID)&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&gt; these users will get PD/6=
0 (arbitrarily determined by the operator and in conformance with the requi=
rement)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">That was the easy part. What we need to do now is to=
 determine:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>Rule IPv6 Prefix&nbsp; (to complete BMR/FMR)<o:p></=
o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>How will the end user DHCPv6 prefix (PD) be carved =
out by DHCP server (assumption is that DHCPv6 server delegates v6 prefix an=
d Rules).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We will represents the bits in v6 address via the fo=
llowing graph (we will ignore irrelevant parts of the v6 addresses for this=
 discussion and instead consider only the bits /32 to /64):<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; /36&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /40&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /44&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; /48&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /=
52&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /56&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; /60&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; /64<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">xxxx &nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xx=
xx &nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; | |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&lt; --------EA=3D12--------&gt;|&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; 1) this will cover subnet 1) ; EA bits extend from the PD length =
(/56) to the Rule IPv6 prefix length
 (/44)<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&lt; ---------EA=3D12------ &gt;|&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; 2) this will cover subnet 2); &nbsp;EA bits extend from the PD l=
ength (/60) to the Rule IPv6 prefix length
 (/48)<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; |&lt; ----------------EA=3D14=
------ &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3) this will cover subnet 3) ; E=
A bits extend from the PD length (/60) to the Rule IPv6 prefix length (/46)=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Now we have determined IPv6 Rule Prefix length for e=
ach of the three rules that we need to create.
<o:p></o:p></p>
<p class=3D"MsoNormal">The IPv4 Prefix Rule lengths are /44, /48 and /46 fo=
r the cases 1), 2) and 3) respectively.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Now we need to determine how can each end user prefi=
x be uniquely allocated across all users (CEs). The only way to ensure this=
 uniqueness is to ensure that the portion of the IPv6 Rule prefix up to /44=
 (smallest Rule IPv6 prefix length
 between all the rules in the MAP domain) is unique amongst all the rules.<=
o:p></o:p></p>
<p class=3D"MsoNormal">So, the IPv6 Rule prefixes for our three cases will =
be (changing the part above /44):<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo4"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>2001:db8:0000::/44<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo4"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>2001:db8:0010::/48<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo4"><![if !supportLists]><span style=3D"mso-list:Ignore">3)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>2001:db8:0020::/46<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The last step is to ensure that the DHCPv6 server ha=
nds out proper end-user prefixes (and along with the prefixes, the Rules ar=
e delegated as well).<o:p></o:p></p>
<p class=3D"MsoNormal">So the DHCPv6 can be configured so that it is carvin=
g the prefixes from three ranges:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo5"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>2001:db8:000x:xxyy::&nbsp; (where x denotes carving=
 part from /44 to /56 &#8211; the EA bits; &#8216;y&#8217; denotes further =
subneting that is done on the CPE -&gt; yy=3D00 for MAP prefix, the remaini=
ng combinations are reserved for CPE delegation to its clients)<o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo5"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>2001:db8:0100:xxxy::&nbsp; (where x denotes carving=
 part from /48 to /60 &#8211; the EA bits; &#8216;y&#8217; denotes further =
subneting that is done on the CPE -&gt; y=3D0 for MAP prefix, the remaining=
 combinations are reserved for CPE delegation to its clients)<o:p></o:p></p=
>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo5"><![if !supportLists]><span style=3D"mso-list:Ignore">3)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>2001:db8:020w:xxxy::&nbsp; (where x and two lower b=
its of &#8216;w&#8217; denote carving part from /46 to /60 &#8211; the EA b=
its; &#8216;y&#8217; denotes further subneting that is done on the CPE -&gt=
; y=3D0 for MAP prefix, the remaining combinations are reserved for CPE
 delegation to its clients)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Along with each user end prefix a BMR and a DMR will=
 be delegated to the end-users (so we will have a hub and spoke topology)<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Also note that to cover the holes between the /48 an=
d /44 for case 2) we can easily add 15 more /24 IPv4 prefixes by creating n=
ew IPv6 Rule by changing bits between /44 and /48.<o:p></o:p></p>
<p class=3D"MsoNormal">Similarly for case 3), we can create 3 more IPv6 rul=
e prefixes (and add 3 more /22 IPv4 subnets) by changing bits between /46 a=
nd /48. This would allow us to expand the coverage for residual IPs (althou=
gh the purpose of NAT is to minimize
 their use over time not to expand <span style=3D"font-family:Wingdings">J<=
/span>).
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7921F977B17D5B49B8DCC955A339D2F02AA8F562US70UWXCHMBA06z_--

From fibrib@gmail.com  Fri Mar 15 17:45:58 2013
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 3D7C521F86EA for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 17:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.597
X-Spam-Level: 
X-Spam-Status: No, score=-3.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=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 R-C7Aqow3dr8 for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 17:45:57 -0700 (PDT)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id C0B5E21F86E8 for <softwires@ietf.org>; Fri, 15 Mar 2013 17:45:56 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i18so4081388oag.15 for <softwires@ietf.org>; Fri, 15 Mar 2013 17:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=SZeuCwDZP7yZ5p1sdFnEHaOeE/neR6Y31qUpUPonZSo=; b=f20C0CgFlHT071gE/9uCwGEgvVSOk9LYVARGzZ4ouTZdNMN7b1eB/t7+RpoZpQCHUH YCenD9NjqjWDLEFDjlG/AFzPMiaG5oEecsXSI4jUuxFELXAsrPfu44MASM9YeEOGg1an kSNh0d6BAff60DOYMVgVXMPaM98UP2TDfqb96phmGu66zBnJmlQwBpqEa2+2YYuPSdAr Id4OSpFkKDPaLB8aJmkjHgsVZZqZ6zdp2Tv99OOdAqDJz0OibXdOKo2EsR/fYf5WyOki 5t7WQWUa8gneLrqLmu06qn4Or0poBRJSuvy6l0BAzBElat4HLjWgqcgHGKyHWqTnuYKb S+qQ==
MIME-Version: 1.0
X-Received: by 10.60.133.75 with SMTP id pa11mr1938097oeb.70.1363394756343; Fri, 15 Mar 2013 17:45:56 -0700 (PDT)
Received: by 10.76.81.129 with HTTP; Fri, 15 Mar 2013 17:45:56 -0700 (PDT)
In-Reply-To: <7921F977B17D5B49B8DCC955A339D2F02AA8F562@US70UWXCHMBA06.zam.alcatel-lucent.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA8F562@US70UWXCHMBA06.zam.alcatel-lucent.com>
Date: Sat, 16 Mar 2013 09:45:56 +0900
Message-ID: <CAFUBMqVSdpgwEzs9sjG9NJMKTnEi+yursJLMg1WYmezePJwZFw@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=047d7b471fe024012904d8001429
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] map-deployment-01 draft
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, 16 Mar 2013 00:45:58 -0000

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

hi Kristian,

thanks a lot for the comments! i totally agree with you that there should
be a comprehensive example for the step-by-step guideline. (i remember that
we put such an example in early sketch but later some said it might not
necessary. :P) i would like to ask the wg (and other authors) for the
consensus of adding the example into the draft.
2013/3/16 Poscic, Kristian (Kristian) <kristian.poscic@alcatel-lucent.com>

>  ** **
>
> I was able to follow section 5.1 of this draft somewhat but then got
> completely lost at step B3. ****
>
> It would really help if you can also describe the reason why are you
> performing each step =96 in other words put more context around it.
> Otherwise, it will be very hard for the operators to follow this.****
>
> ** **
>
> Maybe we can start from a more comprehensive example and you can include
> it the draft along with your steps. ****
>
> Here is my example and logic that I follow:****
>
> ** **
>
> **1)      **Example requirement:****
>
> **-          **There are about 22,000 residual IPv4 addresses that needs
> to be translated via MAP.****
>
> **-          **Each  such address should have 4K ports available.
> Therefore, the IP address sharing ratio is 16:1****
>
> **-          **The public IPv4 addresses that are available to the
> operator for this translation are four  /24 subnets (11.11.11.0/24 ,
> 12.12.12..0/24, 13.13.13.0/24 and 14.14.14.0/24)  and one /22 subnet (
> 15.15.0.0/22).****
>
> **-          **The IPv6 prefix that is delegated to the operator is
> 2001:db8::/32 .****
>
> **-          **4K users (or CPEs corresponding to the residual IP
> addresses) will get PD /56, the rest of the users will get PD /60.****
>
> **-          **The end-user-prefix and the rules will be delegated via
> DHCPv6 server
>

 i like this start of example! some further considerations sould be
included (as the example for the remarks)

#1 the public IPv4 addresses might be quite bad aggregated;
#2 the IPv6 common prefix for the MAP deployment might be not exist -- MAP
can be deployed cross autonomous systems where delegated prefices are not
aggregateable at all. (this is a typical case where 1:1 mode is needed)
#3 DHCPv6 is not the only way for the provisioning, and at least manual
configuraton MUST be supported. therefore we cannot put anything that needs
DHCPv6 as prerequisite for deployment and implementation.

>
>
> ** **
>
> 22,000 residual IP addresses in 16:1 sharing scenario could be covered
> with two /24 subnets and one /22 subnet  =3D> (2 * 2^8 * 16 + 2^10 * 16 =
=3D 24,
> 576).****
>
> ** **
>
> So Rule IPv4 prefix and EA bits length  will be:****
>
> ** **
>
> **1)      **11.11.11.0/24    EA length: 12 bits  (8 bits for the IPv4
> suffix and 4 bits for PSID)    =3D> these users will get PD /56 (arbitrar=
ily
> determined by the operator and in conformance with the requirement)****
>
> **2)      **12.12.12.0/24    EA length: 12
> bits
> =3D> these users will get PD /60 (arbitrarily determined by the operator =
and
> in conformance with the requirement)****
>
> **3)      **15.15.0.0/22      EA length: 14 bits  (10 bits for IPv4
> suffix and 4 bits for PSID)          =3D> these users will get PD/60
> (arbitrarily determined by the operator and in conformance with the
> requirement)****
>
> ** **
>
> That was the easy part. What we need to do now is to determine:****
>
> **-          **Rule IPv6 Prefix  (to complete BMR/FMR)****
>
> **-          **How will the end user DHCPv6 prefix (PD) be carved out by
> DHCP server (assumption is that DHCPv6 server delegates v6 prefix and
> Rules).****
>
> ** **
>
> We will represents the bits in v6 address via the following graph (we wil=
l
> ignore irrelevant parts of the v6 addresses for this discussion and inste=
ad
> consider only the bits /32 to /64):****
>
> ** **
>
>                 /32         /36         /40         /44
> /48         /52         /56         /60         /64****
>
> xxxx       xxxx       xxxx       xxxx       xxxx       xxxx
> xxxx       xxxx       xxxx  ****
>
>                                                                 |
> |          |                              |              |****
>
>                                                                 |<
> --------EA=3D12-------->|              |                             1) t=
his
> will cover subnet 1) ; EA bits extend from the PD length (/56) to the Rul=
e
> IPv6 prefix length (/44)****
>
>
> |          |< ---------EA=3D12------ >|                              2) t=
his
> will cover subnet 2);  EA bits extend from the PD length (/60) to the Rul=
e
> IPv6 prefix length (/48)****
>
>                                                                     |<
> ----------------EA=3D14------ >|                               3) this wi=
ll
> cover subnet 3) ; EA bits extend from the PD length (/60) to the Rule IPv=
6
> prefix length (/46)       ****
>
> ** **
>
> Now we have determined IPv6 Rule Prefix length for each of the three rule=
s
> that we need to create. ****
>
> The IPv4 Prefix Rule lengths are /44, /48 and /46 for the cases 1), 2) an=
d
> 3) respectively.****
>
> ** **
>
> Now we need to determine how can each end user prefix be uniquely
> allocated across all users (CEs). The only way to ensure this uniqueness =
is
> to ensure that the portion of the IPv6 Rule prefix up to /44 (smallest Ru=
le
> IPv6 prefix length between all the rules in the MAP domain) is unique
> amongst all the rules.****
>
> So, the IPv6 Rule prefixes for our three cases will be (changing the part
> above /44):****
>
> **1)      **2001:db8:0000::/44****
>
> **2)      **2001:db8:0010::/48****
>
> **3)      **2001:db8:0020::/46****
>
> ** **
>
> The last step is to ensure that the DHCPv6 server hands out proper
> end-user prefixes (and along with the prefixes, the Rules are delegated a=
s
> well).****
>
> So the DHCPv6 can be configured so that it is carving the prefixes from
> three ranges:****
>
> ** **
>
> **1)      **2001:db8:000x:xxyy::  (where x denotes carving part from /44
> to /56 =96 the EA bits; =91y=92 denotes further subneting that is done on=
 the CPE
> -> yy=3D00 for MAP prefix, the remaining combinations are reserved for CP=
E
> delegation to its clients)****
>
> **2)      **2001:db8:0100:xxxy::  (where x denotes carving part from /48
> to /60 =96 the EA bits; =91y=92 denotes further subneting that is done on=
 the CPE
> -> y=3D0 for MAP prefix, the remaining combinations are reserved for CPE
> delegation to its clients)****
>
> **3)      **2001:db8:020w:xxxy::  (where x and two lower bits of =91w=92
> denote carving part from /46 to /60 =96 the EA bits; =91y=92 denotes furt=
her
> subneting that is done on the CPE -> y=3D0 for MAP prefix, the remaining
> combinations are reserved for CPE delegation to its clients)****
>
> ** **
>
> Along with each user end prefix a BMR and a DMR will be delegated to the
> end-users (so we will have a hub and spoke topology)****
>
> ** **
>
> Also note that to cover the holes between the /48 and /44 for case 2) we
> can easily add 15 more /24 IPv4 prefixes by creating new IPv6 Rule by
> changing bits between /44 and /48.****
>
> Similarly for case 3), we can create 3 more IPv6 rule prefixes (and add 3
> more /22 IPv4 subnets) by changing bits between /46 and /48. This would
> allow us to expand the coverage for residual IPs (although the purpose of
> NAT is to minimize their use over time not to expand J).
>
>
>

>> co-authors: we may compose the 5.1 again based on Kristian's proposed
example and includes the #1 ~ #3 above and submit for wg review. agree?

- maoke


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

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

<div>hi Kristian, </div><div>=A0</div><div>thanks a lot for the comments!=
=A0i totally agree with you that there should be a comprehensive example fo=
r the step-by-step guideline. (i remember that we put such an example in ea=
rly sketch but later some said it might not necessary. :P) i would like to =
ask the wg=A0(and other authors) for the consensus of adding the example in=
to the draft. <br>
</div><div class=3D"gmail_quote">2013/3/16 Poscic, Kristian (Kristian) <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:kristian.poscic@alcatel-lucent.com" tar=
get=3D"_blank">kristian.poscic@alcatel-lucent.com</a>&gt;</span><br><blockq=
uote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:r=
gb(204,204,204);border-left-width:1px;border-left-style:solid" class=3D"gma=
il_quote">






<div lang=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">I was able to follow section 5.1 of this draft somew=
hat but then got completely lost at step B3.
<u></u><u></u></p>
<p class=3D"MsoNormal">It would really help if you can also describe the re=
ason why are you performing each step =96 in other words put more context a=
round it. Otherwise, it will be very hard for the operators to follow this.=
<u></u><u></u></p>

<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Maybe we can start from a more comprehensive example=
 and you can include it the draft along with your steps.
<u></u><u></u></p>
<p class=3D"MsoNormal">Here is my example and logic that I follow:<u></u><u=
></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p><u></u><span>1)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u>Example requirement:<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fo=
nt-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span><u></u>There are about 22,000 residual IPv4 addresses that ne=
eds to be translated via MAP.<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fo=
nt-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span><u></u>Each =A0such address should have 4K ports available. T=
herefore, the IP address sharing ratio is 16:1<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fo=
nt-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span><u></u>The public IPv4 addresses that are available to the op=
erator for this translation are four =A0/24 subnets (<a href=3D"http://11.1=
1.11.0/24" target=3D"_blank">11.11.11.0/24</a> , 12.12.12..0/24, <a href=3D=
"http://13.13.13.0/24" target=3D"_blank">13.13.13.0/24</a> and <a href=3D"h=
ttp://14.14.14.0/24" target=3D"_blank">14.14.14.0/24</a>) =A0and one /22 su=
bnet (<a href=3D"http://15.15.0.0/22" target=3D"_blank">15.15.0.0/22</a>).<=
u></u><u></u></p>

<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fo=
nt-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span><u></u>The IPv6 prefix that is delegated to the operator is 2=
001:db8::/32 .<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fo=
nt-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span><u></u>4K users (or CPEs corresponding to the residual IP add=
resses) will get PD /56, the rest of the users will get PD /60.<u></u><u></=
u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fo=
nt-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span><u></u>The end-user-prefix and the rules will be delegated vi=
a DHCPv6 server=A0=A0</p></div></div></blockquote><div>=A0</div><div>=A0i l=
ike this start of example! some further considerations sould be included (a=
s the example for the remarks)=A0</div>
<div>=A0</div><div>#1 the public IPv4 addresses might be quite bad aggregat=
ed; </div><div>#2 the IPv6 common prefix for the MAP deployment might be no=
t exist -- MAP can be deployed cross autonomous systems where delegated pre=
fices are not aggregateable at all. (this is a typical case where 1:1 mode =
is needed)</div>
<div>#3 DHCPv6 is not the only way for the provisioning, and at least manua=
l configuraton MUST be supported. therefore we cannot put anything that nee=
ds DHCPv6 as prerequisite for deployment and implementation. </div><blockqu=
ote style=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"gmai=
l_quote">
<div lang=3D"EN-US" vlink=3D"purple" link=3D"blue"><div><p style=3D"margin-=
left:0.75in">=A0</p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">22,000 residual IP addresses in 16:1 sharing scenari=
o could be covered with two /24 subnets and one /22 subnet=A0 =3D&gt; (2 * =
2^8 * 16 + 2^10 * 16 =3D 24, 576).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">So Rule IPv4 prefix and EA bits length =A0will be:<u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p><u></u><span>1)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u><a href=3D"http://11.11.11.0/24" target=3D"_blank">11.=
11.11.0/24</a>=A0=A0=A0 EA length: 12 bits=A0 (8 bits for the IPv4 suffix a=
nd 4 bits for PSID)=A0=A0=A0 =3D&gt; these users will get PD /56 (arbitrari=
ly determined by the operator and in conformance with the requirement)<u></=
u><u></u></p>

<p><u></u><span>2)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u><a href=3D"http://12.12.12.0/24" target=3D"_blank">12.=
12.12.0/24</a>=A0 =A0=A0EA length: 12 bits=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 =3D&gt; these users will get PD /60 (arbitrarily dete=
rmined by the operator and in conformance with the requirement)<u></u><u></=
u></p>

<p><u></u><span>3)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u><a href=3D"http://15.15.0.0/22" target=3D"_blank">15.1=
5.0.0/22</a> =A0=A0=A0=A0=A0EA length: 14 bits=A0 (10 bits for IPv4 suffix =
and 4 bits for PSID)=A0=A0=A0=A0=A0=A0=A0=A0=A0 =3D&gt; these users will ge=
t PD/60 (arbitrarily determined by the operator and in conformance with the=
 requirement)<u></u><u></u></p>

<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">That was the easy part. What we need to do now is to=
 determine:<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fo=
nt-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span><u></u>Rule IPv6 Prefix=A0 (to complete BMR/FMR)<u></u><u></u=
></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fo=
nt-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span><u></u>How will the end user DHCPv6 prefix (PD) be carved out=
 by DHCP server (assumption is that DHCPv6 server delegates v6 prefix and R=
ules).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">We will represents the bits in v6 address via the fo=
llowing graph (we will ignore irrelevant parts of the v6 addresses for this=
 discussion and instead consider only the bits /32 to /64):<u></u><u></u></=
p>

<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /32=A0=
=A0=A0=A0=A0=A0=A0=A0 /36=A0=A0=A0=A0=A0=A0=A0=A0 /40=A0=A0=A0=A0=A0=A0=A0=
=A0 /44=A0=A0=A0=A0=A0=A0=A0=A0 /48=A0=A0=A0=A0=A0=A0=A0=A0 /52=A0=A0=A0=A0=
=A0=A0=A0=A0 /56=A0=A0=A0=A0=A0=A0=A0=A0 /60=A0=A0=A0=A0=A0=A0=A0=A0 /64<u>=
</u><u></u></p>
<p style=3D"text-indent:0.5in" class=3D"MsoNormal">xxxx =A0=A0=A0=A0=A0 xxx=
x=A0=A0=A0=A0=A0=A0 xxxx=A0=A0=A0=A0=A0=A0 xxxx=A0=A0=A0=A0=A0=A0 xxxx=A0=
=A0=A0=A0=A0=A0 xxxx=A0=A0=A0=A0=A0=A0 xxxx=A0=A0=A0=A0=A0=A0 xxxx=A0=A0=A0=
=A0=A0=A0 xxxx =A0<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | |=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 |<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |&lt; -----=
---EA=3D12--------&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=A0=A0=A0=A0=A0=A0=A0=A0=
 1) this will cover subnet 1) ; EA bits extend from the PD length (/56) to =
the Rule IPv6 prefix length
 (/44)<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0 |=
=A0=A0=A0=A0=A0=A0=A0=A0=A0 |&lt; ---------EA=3D12------ &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=
 2) this will cover subnet 2); =A0EA bits extend from the PD length (/60) t=
o the Rule IPv6 prefix length
 (/48)<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0 |=
&lt; ----------------EA=3D14------ &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 3) this will cove=
r subnet 3) ; EA bits extend from the PD length (/60) to the Rule IPv6 pref=
ix length (/46)=A0=A0=A0=A0=A0=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Now we have determined IPv6 Rule Prefix length for e=
ach of the three rules that we need to create.
<u></u><u></u></p>
<p class=3D"MsoNormal">The IPv4 Prefix Rule lengths are /44, /48 and /46 fo=
r the cases 1), 2) and 3) respectively.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Now we need to determine how can each end user prefi=
x be uniquely allocated across all users (CEs). The only way to ensure this=
 uniqueness is to ensure that the portion of the IPv6 Rule prefix up to /44=
 (smallest Rule IPv6 prefix length
 between all the rules in the MAP domain) is unique amongst all the rules.<=
u></u><u></u></p>
<p class=3D"MsoNormal">So, the IPv6 Rule prefixes for our three cases will =
be (changing the part above /44):<u></u><u></u></p>
<p><u></u><span>1)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u>2001:db8:0000::/44<u></u><u></u></p>
<p><u></u><span>2)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u>2001:db8:0010::/48<u></u><u></u></p>
<p><u></u><span>3)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u>2001:db8:0020::/46<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">The last step is to ensure that the DHCPv6 server ha=
nds out proper end-user prefixes (and along with the prefixes, the Rules ar=
e delegated as well).<u></u><u></u></p>
<p class=3D"MsoNormal">So the DHCPv6 can be configured so that it is carvin=
g the prefixes from three ranges:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p><u></u><span>1)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u>2001:db8:000x:xxyy::=A0 (where x denotes carving part =
from /44 to /56 =96 the EA bits; =91y=92 denotes further subneting that is =
done on the CPE -&gt; yy=3D00 for MAP prefix, the remaining combinations ar=
e reserved for CPE delegation to its clients)<u></u><u></u></p>

<p><u></u><span>2)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u>2001:db8:0100:xxxy::=A0 (where x denotes carving part =
from /48 to /60 =96 the EA bits; =91y=92 denotes further subneting that is =
done on the CPE -&gt; y=3D0 for MAP prefix, the remaining combinations are =
reserved for CPE delegation to its clients)<u></u><u></u></p>

<p><u></u><span>3)<span style=3D"font:7pt/normal &quot;Times New Roman&quot=
;;font-size-adjust:none;font-stretch:normal">=A0=A0=A0=A0=A0
</span></span><u></u>2001:db8:020w:xxxy::=A0 (where x and two lower bits of=
 =91w=92 denote carving part from /46 to /60 =96 the EA bits; =91y=92 denot=
es further subneting that is done on the CPE -&gt; y=3D0 for MAP prefix, th=
e remaining combinations are reserved for CPE
 delegation to its clients)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Along with each user end prefix a BMR and a DMR will=
 be delegated to the end-users (so we will have a hub and spoke topology)<u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Also note that to cover the holes between the /48 an=
d /44 for case 2) we can easily add 15 more /24 IPv4 prefixes by creating n=
ew IPv6 Rule by changing bits between /44 and /48.<u></u><u></u></p>
<p class=3D"MsoNormal">Similarly for case 3), we can create 3 more IPv6 rul=
e prefixes (and add 3 more /22 IPv4 subnets) by changing bits between /46 a=
nd /48. This would allow us to expand the coverage for residual IPs (althou=
gh the purpose of NAT is to minimize
 their use over time not to expand <span style=3D"font-family:Wingdings">J<=
/span>).
</p><p class=3D"MsoNormal">=A0</p></div></div></blockquote><div>=A0</div><d=
iv>&gt;&gt; co-authors: we=A0may compose the 5.1 again based on Kristian&#3=
9;s proposed example and includes the #1 ~ #3 above and submit=A0for wg=A0r=
eview. agree?</div>
<div>=A0</div><div>- maoke</div><div>=A0</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 lang=3D=
"EN-US" vlink=3D"purple" link=3D"blue">
<div><p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>

<br>_______________________________________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/softwires</a><br>
<br></blockquote></div><br>

--047d7b471fe024012904d8001429--

From yiu_lee@cable.comcast.com  Fri Mar 15 18:37:56 2013
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 942B011E811F for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 18:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.499
X-Spam-Level: 
X-Spam-Status: No, score=-99.499 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396, NORMAL_HTTP_TO_IP=0.001, 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 Ef6C6Z1ALSTJ for <softwires@ietfa.amsl.com>; Fri, 15 Mar 2013 18:37:52 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id 07A3911E8109 for <softwires@ietf.org>; Fri, 15 Mar 2013 18:37:48 -0700 (PDT)
Received: from ([24.40.56.114]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.46569867; Fri, 15 Mar 2013 21:36:04 -0400
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.236]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Fri, 15 Mar 2013 21:37:44 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Maoke <fibrib@gmail.com>, "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
Thread-Topic: [Softwires] map-deployment-01 draft
Thread-Index: AQHOIebaH4AMXU8DLkKHyy2OKraXnA==
Date: Sat, 16 Mar 2013 01:37:43 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD471F96DB@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <CAFUBMqVSdpgwEzs9sjG9NJMKTnEi+yursJLMg1WYmezePJwZFw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [24.40.55.73]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3446228261_1180444"
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] map-deployment-01 draft
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, 16 Mar 2013 01:37:56 -0000

--B_3446228261_1180444
Content-type: multipart/alternative;
	boundary="B_3446228260_1127346"


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

+1. Adding an example will definitely help.

From:  Maoke <fibrib@gmail.com>
Date:  Friday, March 15, 2013 8:45 PM
To:  "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
Cc:  "softwires@ietf.org" <softwires@ietf.org>
Subject:  Re: [Softwires] map-deployment-01 draft

hi Kristian,=20
=20
thanks a lot for the comments! i totally agree with you that there should b=
e
a comprehensive example for the step-by-step guideline. (i remember that we
put such an example in early sketch but later some said it might not
necessary. :P) i would like to ask the wg (and other authors) for the
consensus of adding the example into the draft.
2013/3/16 Poscic, Kristian (Kristian) <kristian.poscic@alcatel-lucent.com>
> =20
> I was able to follow section 5.1 of this draft somewhat but then got
> completely lost at step B3.
> It would really help if you can also describe the reason why are you
> performing each step =AD in other words put more context around it. Otherwi=
se,
> it will be very hard for the operators to follow this.
> =20
> Maybe we can start from a more comprehensive example and you can include =
it
> the draft along with your steps.
> Here is my example and logic that I follow:
> =20
> 1)     Example requirement:
>=20
> -         There are about 22,000 residual IPv4 addresses that needs to be
> translated via MAP.
>=20
> -         Each  such address should have 4K ports available. Therefore, t=
he IP
> address sharing ratio is 16:1
>=20
> -         The public IPv4 addresses that are available to the operator fo=
r
> this translation are four  /24 subnets (11.11.11.0/24 <http://11.11.11.0/=
24>
> , 12.12.12..0/24, 13.13.13.0/24 <http://13.13.13.0/24>  and 14.14.14.0/24
> <http://14.14.14.0/24> )  and one /22 subnet (15.15.0.0/22
> <http://15.15.0.0/22> ).
>=20
> -         The IPv6 prefix that is delegated to the operator is 2001:db8::=
/32 .
>=20
> -         4K users (or CPEs corresponding to the residual IP addresses) w=
ill
> get PD /56, the rest of the users will get PD /60.
>=20
> -         The end-user-prefix and the rules will be delegated via DHCPv6
> server =20

=20
 i like this start of example! some further considerations sould be include=
d
(as the example for the remarks)
=20
#1 the public IPv4 addresses might be quite bad aggregated;
#2 the IPv6 common prefix for the MAP deployment might be not exist -- MAP
can be deployed cross autonomous systems where delegated prefices are not
aggregateable at all. (this is a typical case where 1:1 mode is needed)
#3 DHCPv6 is not the only way for the provisioning, and at least manual
configuraton MUST be supported. therefore we cannot put anything that needs
DHCPv6 as prerequisite for deployment and implementation.
> =20
>=20
> =20
> 22,000 residual IP addresses in 16:1 sharing scenario could be covered wi=
th
> two /24 subnets and one /22 subnet  =3D> (2 * 2^8 * 16 + 2^10 * 16 =3D 24, 57=
6).
> =20
> So Rule IPv4 prefix and EA bits length  will be:
> =20
> 1)     11.11.11.0/24 <http://11.11.11.0/24>     EA length: 12 bits  (8 bi=
ts
> for the IPv4 suffix and 4 bits for PSID)    =3D> these users will get PD /5=
6
> (arbitrarily determined by the operator and in conformance with the
> requirement)
>=20
> 2)     12.12.12.0/24 <http://12.12.12.0/24>     EA length: 12 bits
> =3D> these users will get PD /60 (arbitrarily determined by the operator an=
d in
> conformance with the requirement)
>=20
> 3)     15.15.0.0/22 <http://15.15.0.0/22>       EA length: 14 bits  (10 b=
its
> for IPv4 suffix and 4 bits for PSID)          =3D> these users will get PD/=
60
> (arbitrarily determined by the operator and in conformance with the
> requirement)
>=20
> =20
> That was the easy part. What we need to do now is to determine:
> -         Rule IPv6 Prefix  (to complete BMR/FMR)
>=20
> -         How will the end user DHCPv6 prefix (PD) be carved out by DHCP
> server (assumption is that DHCPv6 server delegates v6 prefix and Rules).
>=20
> =20
> We will represents the bits in v6 address via the following graph (we wil=
l
> ignore irrelevant parts of the v6 addresses for this discussion and inste=
ad
> consider only the bits /32 to /64):
> =20
>                 /32         /36         /40         /44         /48
> /52         /56         /60         /64
> xxxx       xxxx       xxxx       xxxx       xxxx       xxxx       xxxx
> xxxx       xxxx =20
>                                                                 | |      =
    |
> |              |
>                                                                 |<
> --------EA=3D12-------->|              |                             1) thi=
s
> will cover subnet 1) ; EA bits extend from the PD length (/56) to the Rul=
e
> IPv6 prefix length (/44)
>                                                                     |
> |< ---------EA=3D12------ >|                              2) this will cove=
r
> subnet 2);  EA bits extend from the PD length (/60) to the Rule IPv6 pref=
ix
> length (/48)
>                                                                     |<
> ----------------EA=3D14------ >|                               3) this will
> cover subnet 3) ; EA bits extend from the PD length (/60) to the Rule IPv=
6
> prefix length (/46)
> =20
> Now we have determined IPv6 Rule Prefix length for each of the three rule=
s
> that we need to create.
> The IPv4 Prefix Rule lengths are /44, /48 and /46 for the cases 1), 2) an=
d 3)
> respectively.
> =20
> Now we need to determine how can each end user prefix be uniquely allocat=
ed
> across all users (CEs). The only way to ensure this uniqueness is to ensu=
re
> that the portion of the IPv6 Rule prefix up to /44 (smallest Rule IPv6 pr=
efix
> length between all the rules in the MAP domain) is unique amongst all the
> rules.
> So, the IPv6 Rule prefixes for our three cases will be (changing the part
> above /44):
> 1)     2001:db8:0000::/44
>=20
> 2)     2001:db8:0010::/48
>=20
> 3)     2001:db8:0020::/46
>=20
> =20
> The last step is to ensure that the DHCPv6 server hands out proper end-us=
er
> prefixes (and along with the prefixes, the Rules are delegated as well).
> So the DHCPv6 can be configured so that it is carving the prefixes from t=
hree
> ranges:
> =20
> 1)     2001:db8:000x:xxyy::  (where x denotes carving part from /44 to /5=
6 =AD
> the EA bits; =8Cy=B9 denotes further subneting that is done on the CPE -> yy=3D=
00
> for MAP prefix, the remaining combinations are reserved for CPE delegatio=
n to
> its clients)
>=20
> 2)     2001:db8:0100:xxxy::  (where x denotes carving part from /48 to /6=
0 =AD
> the EA bits; =8Cy=B9 denotes further subneting that is done on the CPE -> y=3D0=
 for
> MAP prefix, the remaining combinations are reserved for CPE delegation to=
 its
> clients)
>=20
> 3)     2001:db8:020w:xxxy::  (where x and two lower bits of =8Cw=B9 denote ca=
rving
> part from /46 to /60 =AD the EA bits; =8Cy=B9 denotes further subneting that is=
 done
> on the CPE -> y=3D0 for MAP prefix, the remaining combinations are reserved=
 for
> CPE delegation to its clients)
>=20
> =20
> Along with each user end prefix a BMR and a DMR will be delegated to the
> end-users (so we will have a hub and spoke topology)
> =20
> Also note that to cover the holes between the /48 and /44 for case 2) we =
can
> easily add 15 more /24 IPv4 prefixes by creating new IPv6 Rule by changin=
g
> bits between /44 and /48.
> Similarly for case 3), we can create 3 more IPv6 rule prefixes (and add 3=
 more
> /22 IPv4 subnets) by changing bits between /46 and /48. This would allow =
us to
> expand the coverage for residual IPs (although the purpose of NAT is to
> minimize their use over time not to expand J).
> =20
=20
>> co-authors: we may compose the 5.1 again based on Kristian's proposed ex=
ample
and includes the #1 ~ #3 above and submit for wg review. agree?
=20
- maoke
=20
> =20
> =20
> =20
> =20
> =20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>=20




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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>+1. Adding an example will d=
efinitely help.</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div sty=
le=3D"font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDE=
R-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDIN=
G-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT=
: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: </span=
> Maoke &lt;<a href=3D"mailto:fibrib@gmail.com">fibrib@gmail.com</a>&gt;<br><s=
pan style=3D"font-weight:bold">Date: </span> Friday, March 15, 2013 8:45 PM<br=
><span style=3D"font-weight:bold">To: </span> "Poscic, Kristian (Kristian)" &l=
t;<a href=3D"mailto:kristian.poscic@alcatel-lucent.com">kristian.poscic@alcate=
l-lucent.com</a>&gt;<br><span style=3D"font-weight:bold">Cc: </span> "<a href=3D=
"mailto:softwires@ietf.org">softwires@ietf.org</a>" &lt;<a href=3D"mailto:soft=
wires@ietf.org">softwires@ietf.org</a>&gt;<br><span style=3D"font-weight:bold"=
>Subject: </span> Re: [Softwires] map-deployment-01 draft<br></div><div><br>=
</div><div><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8=
"><div><div>hi Kristian, </div><div>&nbsp;</div><div>thanks a lot for the co=
mments!&nbsp;i totally agree with you that there should be a comprehensive e=
xample for the step-by-step guideline. (i remember that we put such an examp=
le in early sketch but later some said it might not necessary. :P) i would l=
ike to
 ask the wg&nbsp;(and other authors) for the consensus of adding the exampl=
e into the draft.
<br></div><div class=3D"gmail_quote">2013/3/16 Poscic, Kristian (Kristian) <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:kristian.poscic@alcatel-lucent.com" target=
=3D"_blank">kristian.poscic@alcatel-lucent.com</a>&gt;</span><br><blockquote s=
tyle=3D"margin: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"><d=
iv lang=3D"EN-US" vlink=3D"purple" link=3D"blue"><div><p class=3D"MsoNormal"><u></u>=
&nbsp;<u></u></p><p class=3D"MsoNormal">I was able to follow section 5.1 of th=
is draft somewhat but then got completely lost at step B3.
<u></u><u></u></p><p class=3D"MsoNormal">It would really help if you can also=
 describe the reason why are you performing each step &#8211; in other words=
 put more context around it. Otherwise, it will be very hard for the operato=
rs to follow this.<u></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u=
></p><p class=3D"MsoNormal">Maybe we can start from a more comprehensive examp=
le and you can include it the draft along with your steps.
<u></u><u></u></p><p class=3D"MsoNormal">Here is my example and logic that I =
follow:<u></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><p><u>=
</u><span>1)<span style=3D"font-style: normal; font-variant: normal; font-weig=
ht: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Rom=
an'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>Example requirement:<u></u><u></u></p><p style=3D"margin=
-left:0.75in"><u></u><span>-<span style=3D"font-style: normal; font-variant: n=
ormal; font-weight: normal; font-size: 7pt; line-height: normal; font-family=
: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
</span></span><u></u>There are about 22,000 residual IPv4 addresses that ne=
eds to be translated via MAP.<u></u><u></u></p><p style=3D"margin-left:0.75in"=
><u></u><span>-<span style=3D"font-style: normal; font-variant: normal; font-w=
eight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New =
Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>Each &nbsp;such address should have 4K ports available=
. Therefore, the IP address sharing ratio is 16:1<u></u><u></u></p><p style=3D=
"margin-left:0.75in"><u></u><span>-<span style=3D"font-style: normal; font-var=
iant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font=
-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><u></u>The public IPv4 addresses that are available to the op=
erator for this translation are four &nbsp;/24 subnets (<a href=3D"http://11.1=
1.11.0/24" target=3D"_blank">11.11.11.0/24</a> , 12.12.12..0/24,
<a href=3D"http://13.13.13.0/24" target=3D"_blank">13.13.13.0/24</a> and <a hre=
f=3D"http://14.14.14.0/24" target=3D"_blank">
14.14.14.0/24</a>) &nbsp;and one /22 subnet (<a href=3D"http://15.15.0.0/22" =
target=3D"_blank">15.15.0.0/22</a>).<u></u><u></u></p><p style=3D"margin-left:0.=
75in"><u></u><span>-<span style=3D"font-style: normal; font-variant: normal; f=
ont-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times=
 New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>The IPv6 prefix that is delegated to the operator is 2=
001:db8::/32 .<u></u><u></u></p><p style=3D"margin-left:0.75in"><u></u><span>-=
<span style=3D"font-style: normal; font-variant: normal; font-weight: normal; =
font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; ">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>4K users (or CPEs corresponding to the residual IP add=
resses) will get PD /56, the rest of the users will get PD /60.<u></u><u></u=
></p><p style=3D"margin-left:0.75in"><u></u><span>-<span style=3D"font-style: no=
rmal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height=
: normal; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>The end-user-prefix and the rules will be delegated vi=
a DHCPv6 server&nbsp;&nbsp;</p></div></div></blockquote><div>&nbsp;</div><di=
v>&nbsp;i like this start of example! some further considerations sould be i=
ncluded (as the example for the remarks)&nbsp;</div><div>&nbsp;</div><div>#1=
 the public IPv4 addresses might be quite bad aggregated; </div><div>#2 the =
IPv6 common prefix for the MAP deployment might be not exist -- MAP can be d=
eployed cross autonomous systems where delegated prefices are not aggregatea=
ble at all. (this is a typical case where 1:1 mode is needed)</div><div>#3 D=
HCPv6 is not the only way for the provisioning, and at least manual configur=
aton MUST be supported. therefore we cannot put anything that needs DHCPv6 a=
s prerequisite for deployment and implementation.
</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:solid" cl=
ass=3D"gmail_quote"><div lang=3D"EN-US" vlink=3D"purple" link=3D"blue"><div><p style=
=3D"margin-left:0.75in">&nbsp;</p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p=
><p class=3D"MsoNormal">22,000 residual IP addresses in 16:1 sharing scenario =
could be covered with two /24 subnets and one /22 subnet&nbsp; =3D&gt; (2 * 2^=
8 * 16 + 2^10 * 16 =3D 24, 576).<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=
&nbsp;<u></u></p><p class=3D"MsoNormal">So Rule IPv4 prefix and EA bits length=
 &nbsp;will be:<u></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></=
p><p><u></u><span>1)<span style=3D"font-style: normal; font-variant: normal; f=
ont-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times=
 New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u><a href=3D"http://11.11.11.0/24" target=3D"_blank">11.11.1=
1.0/24</a>&nbsp;&nbsp;&nbsp; EA length: 12 bits&nbsp; (8 bits for the IPv4 s=
uffix and 4 bits for PSID)&nbsp;&nbsp;&nbsp; =3D&gt; these users will get PD /=
56 (arbitrarily determined by the operator and in conformance with the
 requirement)<u></u><u></u></p><p><u></u><span>2)<span style=3D"font-style: n=
ormal; font-variant: normal; font-weight: normal; font-size: 7pt; line-heigh=
t: normal; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u><a href=3D"http://12.12.12.0/24" target=3D"_blank">12.12.1=
2.0/24</a>&nbsp; &nbsp;&nbsp;EA length: 12 bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&=
gt; these users will get PD /60 (arbitrarily determined by
 the operator and in conformance with the requirement)<u></u><u></u></p><p>=
<u></u><span>3)<span style=3D"font-style: normal; font-variant: normal; font-w=
eight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New =
Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u><a href=3D"http://15.15.0.0/22" target=3D"_blank">15.15.0.=
0/22</a> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;EA length: 14 bits&nbsp; (10 bits for=
 IPv4 suffix and 4 bits for PSID)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; =3D&gt; these users will get PD/60 (arbitrarily determined by the =
operator and in conformance with
 the requirement)<u></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u=
></p><p class=3D"MsoNormal">That was the easy part. What we need to do now is =
to determine:<u></u><u></u></p><p style=3D"margin-left:0.75in"><u></u><span>-<=
span style=3D"font-style: normal; font-variant: normal; font-weight: normal; f=
ont-size: 7pt; line-height: normal; font-family: 'Times New Roman'; ">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>Rule IPv6 Prefix&nbsp; (to complete BMR/FMR)<u></u><u>=
</u></p><p style=3D"margin-left:0.75in"><u></u><span>-<span style=3D"font-style:=
 normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-hei=
ght: normal; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>How will the end user DHCPv6 prefix (PD) be carved out=
 by DHCP server (assumption is that DHCPv6 server delegates v6 prefix and Ru=
les).<u></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><p class=
=3D"MsoNormal">We will represents the bits in v6 address via the following gra=
ph (we will ignore irrelevant parts of the v6 addresses for this discussion =
and instead consider only the bits /32 to /64):<u></u><u></u></p><p class=3D"M=
soNormal"><u></u>&nbsp;<u></u></p><p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /32&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /36&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; /40&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /4=
4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /48&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; /52&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; /56&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /60&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /64<u></u><u></u></p><p style=3D"text-indent:0.5=
in" class=3D"MsoNormal">xxxx &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx &nbsp;<u></u><u></u></p><p cla=
ss=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; | |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; |<u></u><u></u></p><p class=3D"MsoNormal">&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&lt; -------=
-EA=3D12--------&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &n=
bsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1) this will cover subnet 1) ; EA bi=
ts extend from the PD length (/56) to the Rule IPv6 prefix length
 (/44)<u></u><u></u></p><p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&lt; ---------EA=3D12------ &gt;|=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; 2) this will cover subnet 2); &nbsp;EA bits extend fr=
om the PD length (/60) to the Rule IPv6 prefix length
 (/48)<u></u><u></u></p><p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; |&lt; ------=
----------EA=3D14------ &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; 3) this will cover s=
ubnet 3) ; EA bits extend from the PD length (/60) to the Rule IPv6 prefix l=
ength (/46)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<u></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><p class=3D"Ms=
oNormal">Now we have determined IPv6 Rule Prefix length for each of the thre=
e rules that we need to create.
<u></u><u></u></p><p class=3D"MsoNormal">The IPv4 Prefix Rule lengths are /44=
, /48 and /46 for the cases 1), 2) and 3) respectively.<u></u><u></u></p><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><p class=3D"MsoNormal">Now we need t=
o determine how can each end user prefix be uniquely allocated across all us=
ers (CEs). The only way to ensure this uniqueness is to ensure that the port=
ion of the IPv6 Rule prefix up to /44 (smallest Rule IPv6 prefix length
 between all the rules in the MAP domain) is unique amongst all the rules.<=
u></u><u></u></p><p class=3D"MsoNormal">So, the IPv6 Rule prefixes for our thr=
ee cases will be (changing the part above /44):<u></u><u></u></p><p><u></u><=
span>1)<span style=3D"font-style: normal; font-variant: normal; font-weight: n=
ormal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:0000::/44<u></u><u></u></p><p><u></u><span>2)=
<span style=3D"font-style: normal; font-variant: normal; font-weight: normal; =
font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; ">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:0010::/48<u></u><u></u></p><p><u></u><span>3)=
<span style=3D"font-style: normal; font-variant: normal; font-weight: normal; =
font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; ">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:0020::/46<u></u><u></u></p><p class=3D"MsoNorma=
l"><u></u>&nbsp;<u></u></p><p class=3D"MsoNormal">The last step is to ensure t=
hat the DHCPv6 server hands out proper end-user prefixes (and along with the=
 prefixes, the Rules are delegated as well).<u></u><u></u></p><p class=3D"MsoN=
ormal">So the DHCPv6 can be configured so that it is carving the prefixes fr=
om three ranges:<u></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u><=
/p><p><u></u><span>1)<span style=3D"font-style: normal; font-variant: normal; =
font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Time=
s New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:000x:xxyy::&nbsp; (where x denotes carving pa=
rt from /44 to /56 &#8211; the EA bits; &#8216;y&#8217; denotes further subn=
eting that is done on the CPE -&gt; yy=3D00 for MAP prefix, the remaining comb=
inations are reserved for CPE delegation to its clients)<u></u><u></u></p><p=
><u></u><span>2)<span style=3D"font-style: normal; font-variant: normal; font-=
weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New=
 Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:0100:xxxy::&nbsp; (where x denotes carving pa=
rt from /48 to /60 &#8211; the EA bits; &#8216;y&#8217; denotes further subn=
eting that is done on the CPE -&gt; y=3D0 for MAP prefix, the remaining combin=
ations are reserved for CPE delegation to its clients)<u></u><u></u></p><p><=
u></u><span>3)<span style=3D"font-style: normal; font-variant: normal; font-we=
ight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New R=
oman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:020w:xxxy::&nbsp; (where x and two lower bits=
 of &#8216;w&#8217; denote carving part from /46 to /60 &#8211; the EA bits;=
 &#8216;y&#8217; denotes further subneting that is done on the CPE -&gt; y=3D0=
 for MAP prefix, the remaining combinations are reserved for CPE delegation
 to its clients)<u></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u>=
</p><p class=3D"MsoNormal">Along with each user end prefix a BMR and a DMR wil=
l be delegated to the end-users (so we will have a hub and spoke topology)<u=
></u><u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><p class=3D"MsoNo=
rmal">Also note that to cover the holes between the /48 and /44 for case 2) =
we can easily add 15 more /24 IPv4 prefixes by creating new IPv6 Rule by cha=
nging bits between /44 and /48.<u></u><u></u></p><p class=3D"MsoNormal">Simila=
rly for case 3), we can create 3 more IPv6 rule prefixes (and add 3 more /22=
 IPv4 subnets) by changing bits between /46 and /48. This would allow us to =
expand the coverage for residual IPs (although the purpose of NAT is to mini=
mize
 their use over time not to expand <span style=3D"font-family:Wingdings">J</s=
pan>).
</p><p class=3D"MsoNormal">&nbsp;</p></div></div></blockquote><div>&nbsp;</di=
v><div>&gt;&gt; co-authors: we&nbsp;may compose the 5.1 again based on Krist=
ian's proposed example and includes the #1 ~ #3 above and submit&nbsp;for wg=
&nbsp;review. agree?</div><div>&nbsp;</div><div>- maoke</div><div>&nbsp;</di=
v><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-c=
olor:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=3D"=
gmail_quote"><div lang=3D"EN-US" vlink=3D"purple" link=3D"blue"><div><p class=3D"Mso=
Normal">&nbsp;</p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><p class=3D"Mso=
Normal"><u></u>&nbsp;<u></u></p><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p=
><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div></div><br>
_______________________________________________<br>
Softwires mailing list<br><a href=3D"mailto:Softwires@ietf.org">Softwires@iet=
f.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/softwires" targe=
t=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><br><br></bloc=
kquote></div><br></div></div></span></body></html>

--B_3446228260_1127346--

--B_3446228261_1180444
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFHqV
JnO1freHfK4VRGC6HInQ+o0pMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEzMDMxNjAxMzc0MFowDQYJKoZIhvcNAQEBBQAEggEABjyDx5cCIB5sKIEO0xTi
1A2baCo5WaHQ/HnmsGVRBDLiwgfmHc+lbkpNaoPFG948jWawqBPszHDgHlkXn1DROh+eD2wI
RqlDGxZPRsBP3Y9oibLUoj7VWvllcNIBfO1ahYRao2ABfUC9W0jkw4pltuBVI1tZ7/x5DMVm
pwc4bC0Ur5xcp5rtFM/bdxBQA4xFyh6QWeN11SqWfGMJrgqBjf3IA2dbYdU2GCbIFvr8c6fv
VyYHgqSJ984ftIl/S1ULELJNjvjzqn04W2p9PygnHwvk9jxDv8u/odJPkMyAW0/DRZUXKiin
6ZLU8/VTF+DFAHZAaBFvH2xzp2zvIxP6iA==

--B_3446228261_1180444--

From satoru.matsushima@gmail.com  Sat Mar 16 08:34:36 2013
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 91A2521F88E5 for <softwires@ietfa.amsl.com>; Sat, 16 Mar 2013 08:34:36 -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 pFk3jJuvsdcE for <softwires@ietfa.amsl.com>; Sat, 16 Mar 2013 08:34:36 -0700 (PDT)
Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by ietfa.amsl.com (Postfix) with ESMTP id 10DA021F8895 for <softwires@ietf.org>; Sat, 16 Mar 2013 08:34:36 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id um15so5117730pbc.28 for <softwires@ietf.org>; Sat, 16 Mar 2013 08:34:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=TczlUHde6BgnvqsUCcOgrpc1/nSSH1h2w8P7KhwqZKw=; b=RTPmEnWw/O8yHkTf2wZb9xJU5CPc25XNdGEJPYRFGwRG9EcdxQR6ACeLEBVTsGLF3g 7dwESfp6iXVSJ+AQ0AIVZX+Ck/89SHLlLobMYPujyZ0X5BKe8TxsnOkHjmgukIA6I5En hxnkK0jc15w0dLdTlabEpfqRo2I0OEuGl64mMnpwsOKQ8E8HzAbuC9viOt7Nm6+UvAxz XfgWK4YRjl6NYcv2udgCZvq0YIvcWfDdp+zDZ0lPv3VSO5cu2xK88WNb9iqiOluVVlIz AlGKE7tFVODrzpkw3TkPQR3SgQqaVP+6aAJ+CdtXFma7Ebdc9zMuUSRblz6+DJ7P9Wa/ 4rjQ==
X-Received: by 10.66.219.1 with SMTP id pk1mr1851497pac.120.1363448075910; Sat, 16 Mar 2013 08:34:35 -0700 (PDT)
Received: from ?IPv6:2001:df8::128:397d:d4ff:cf07:1940? ([2001:df8:0:128:397d:d4ff:cf07:1940]) by mx.google.com with ESMTPS id xz5sm13859280pbb.25.2013.03.16.08.34.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Mar 2013 08:34:32 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com>
Date: Sun, 17 Mar 2013 00:34:27 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1E72F77-4E0B-4749-98D1-C2CB7AC7729C@gmail.com>
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com> <27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com>
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP tracker issues
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, 16 Mar 2013 15:34:36 -0000

As each implementation has its own, but I heard at least two =
implementors confirm that it is negligible difference between 15 to 63, =
done.

cheers,
--satoru

On 2013/03/13, at 17:39, Satoru Matsushima <satoru.matsushima@gmail.com> =
wrote:

> Hi, I couldn't make comment during meeting but,
>=20
> On 2013/03/12, at 3:28, Ole Troan <ot@cisco.com> wrote:
>=20
>> - Offset 4 versus 6.
>> Discussion on value of wasting 3000 port versus simplicity of nibble =
alignment.
>> No objection to moving default offset to 6 (from 4 in revision 04)
>=20
> Does anyone have a evaluated result of NAT performance difference in =
the number of derived port range?=20
> ie. 63 port ranges (6 bits offset) vs 15 port ranges (4 bit offset) on =
a CPE.
>=20
> It would be better to see the result which show it could be negligible =
with the updated text.
>=20
> cheers,
> --satoru


From xing@cernet.edu.cn  Sat Mar 16 11:19:41 2013
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 8357721F8650 for <softwires@ietfa.amsl.com>; Sat, 16 Mar 2013 11:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=1.207, 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 RPF7NfDqZRMX for <softwires@ietfa.amsl.com>; Sat, 16 Mar 2013 11:19:40 -0700 (PDT)
Received: from cernet.edu.cn (mail.cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with ESMTP id 242A821F8548 for <softwires@ietf.org>; Sat, 16 Mar 2013 11:19:39 -0700 (PDT)
Received: from [127.0.0.1] (unknown [130.129.48.15]) by centos (Coremail) with SMTP id AQAAf3A7jQRgt0RRPoURAA--.45408S5; Sun, 17 Mar 2013 02:18:13 +0800 (CST)
Message-ID: <5144B7AC.8000404@cernet.edu.cn>
Date: Sun, 17 Mar 2013 02:19:24 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Satoru Matsushima <satoru.matsushima@gmail.com>
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>	<27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com> <F1E72F77-4E0B-4749-98D1-C2CB7AC7729C@gmail.com>
In-Reply-To: <F1E72F77-4E0B-4749-98D1-C2CB7AC7729C@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CM-TRANSID: AQAAf3A7jQRgt0RRPoURAA--.45408S5
X-Coremail-Antispam: 1UD129KBjvdXoW7GryrKw43XF4UZr43JryUAwb_yoWkXrc_ur Wjy3WxCrWUGr12gwsrJrWfKrZxGrs8Wr15J34ktr1qq340y398AFn5KrWruw4UJryxJrnr ZFna9ryFkw1a9jkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbj8YjsxI4VWxJwAYFVCjjxCrM7AC8VAFwI0_Gr0_Xr1l1xkIjI8I 6I8E6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM2 8EF7xvwVC0I7IYx2IY67AKxVWUJVWUCwA2z4x0Y4vE2Ix0cI8IcVCY1x0267AKxVWUJVW8 JwA2z4x0Y4vEx4A2jsIE14v26r1j6r4UM28EF7xvwVC2z280aVCY1x0267AKxVW8JVW8Jr 1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IEw4CE5I8CrVC2j2WlYx0Ex4A2 jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvEwIxGrwCY02Avz4vEIx C_XwCF04k20xvY0x0EwIxGrwC20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v2 6r106r1rMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67 AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IY s7xG6rWUJVWrZr1UMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI 0_Jr0_GrUvcSsGvfC2KfnxnUUI43ZEXa7IU8CAp5UUUUU==
X-CM-SenderInfo: p0lqwqxfhu0vvwohv3gofq/
Cc: Softwires WG <softwires@ietf.org>, Ole Troan <ot@cisco.com>
Subject: Re: [Softwires] MAP tracker issues
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, 16 Mar 2013 18:19:41 -0000

Satoru Matsushima 写道:
> As each implementation has its own, but I heard at least two implementors confirm that it is negligible difference between 15 to 63, done.
>   
there is no performance impact for cernet's map cpe. xing
> cheers,
> --satoru
>
> On 2013/03/13, at 17:39, Satoru Matsushima <satoru.matsushima@gmail.com> wrote:
>
>   
>> Hi, I couldn't make comment during meeting but,
>>
>> On 2013/03/12, at 3:28, Ole Troan <ot@cisco.com> wrote:
>>
>>     
>>> - Offset 4 versus 6.
>>> Discussion on value of wasting 3000 port versus simplicity of nibble alignment.
>>> No objection to moving default offset to 6 (from 4 in revision 04)
>>>       
>> Does anyone have a evaluated result of NAT performance difference in the number of derived port range? 
>> ie. 63 port ranges (6 bits offset) vs 15 port ranges (4 bit offset) on a CPE.
>>
>> It would be better to see the result which show it could be negligible with the updated text.
>>
>> cheers,
>> --satoru
>>     
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>
>   




From shtsuchi@cisco.com  Sun Mar 17 02:13:04 2013
Return-Path: <shtsuchi@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 A824921F87D7 for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 02:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.399
X-Spam-Level: 
X-Spam-Status: No, score=-9.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_HI=-8]
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 2rFAvi63hJj7 for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 02:13:04 -0700 (PDT)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7AB21F87C4 for <softwires@ietf.org>; Sun, 17 Mar 2013 02:13:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1735; q=dns/txt; s=iport; t=1363511582; x=1364721182; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=oJGD+FdneGts5CP1Somr95XEryKXyReee03JoJbYhsM=; b=ebDsAN6O/vdhkVnInv6nOe0vJAfd4HVHFQmzgcur2SKg/C/XzjLNaoaN LsB6mOxGtA/0FQYk/+FBIYYM/77YBX8ahKUjAPoZKfS0FtbFNo9TUwJk6 z53SvmyeaFj+KuybHV+zZtIlAB8pSIOkz/Ru+TvlL2PQauHVEg44OmQ2N o=;
X-IronPort-AV: E=Sophos;i="4.84,859,1355097600"; d="scan'208";a="27660227"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 17 Mar 2013 09:13:00 +0000
Received: from Shishio-no-MacBook-Air.local ([10.70.233.48]) by bgl-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2H9Cu0t014356; Sun, 17 Mar 2013 09:12:58 GMT
Message-ID: <51458917.6040908@cisco.com>
Date: Sun, 17 Mar 2013 05:12:55 -0400
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: xing@cernet.edu.cn
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>	<27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com> <F1E72F77-4E0B-4749-98D1-C2CB7AC7729C@gmail.com> <5144B7AC.8000404@cernet.edu.cn>
In-Reply-To: <5144B7AC.8000404@cernet.edu.cn>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org, ot@cisco.com
Subject: Re: [Softwires] MAP tracker issues
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, 17 Mar 2013 09:13:05 -0000

I know 3 Geeks who lived in IPv4 15 port and IPv6 internet environment.
They reported it was comfortable for home network.

And JANOG tested 15port of MAP-E.
http://tools.ietf.org/html/draft-janog-softwire-report-01#section-4.9
MAP-E provides IPv6 to CPE,so CPE can use DNS resolver proxy.

There is no performance impact,if they supported DNS proxy.

Regards,
-Shishio


(2013/03/16 14:19), Xing Li wrote:
> Satoru Matsushima $B<LF;(B:
>> As each implementation has its own, but I heard at least two implementors confirm that it is negligible difference between 15 to 63, done.
> there is no performance impact for cernet's map cpe. xing
>> cheers,
>> --satoru
>>
>> On 2013/03/13, at 17:39, Satoru Matsushima <satoru.matsushima@gmail.com> wrote:
>>
>>> Hi, I couldn't make comment during meeting but,
>>>
>>> On 2013/03/12, at 3:28, Ole Troan <ot@cisco.com> wrote:
>>>
>>>> - Offset 4 versus 6.
>>>> Discussion on value of wasting 3000 port versus simplicity of nibble alignment.
>>>> No objection to moving default offset to 6 (from 4 in revision 04)
>>> Does anyone have a evaluated result of NAT performance difference in the number of derived port range? ie. 63 port ranges (6 bits offset) vs 15 port ranges (4 bit offset) on a CPE.
>>>
>>> It would be better to see the result which show it could be negligible with the updated text.
>>>
>>> cheers,
>>> --satoru
>>
>> _______________________________________________
>> 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 Ted.Lemon@nominum.com  Sun Mar 17 04:52:35 2013
Return-Path: <Ted.Lemon@nominum.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 6632521F8771 for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 04:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mtIP8bAH+mdz for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 04:52:34 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id D162621F855A for <softwires@ietf.org>; Sun, 17 Mar 2013 04:52:34 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUUWugmoyv1jCmV8F/bXTP/7agSuuhCpA@postini.com; Sun, 17 Mar 2013 04:52:34 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 50C591B8ECD for <softwires@ietf.org>; Sun, 17 Mar 2013 04:52:34 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 48709190043; Sun, 17 Mar 2013 04:52:34 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Sun, 17 Mar 2013 04:52:34 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Shishio Tsuchiya <shtsuchi@cisco.com>
Thread-Topic: [Softwires] MAP tracker issues
Thread-Index: AQHOHoZW6z1bduibG02GX5FmyVfDw5ijxNSAgAUq9ICAAC4WAIAA+aaAgAAsnIA=
Date: Sun, 17 Mar 2013 11:52:33 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775110D7D@mbx-01.win.nominum.com>
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com> <27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com> <F1E72F77-4E0B-4749-98D1-C2CB7AC7729C@gmail.com> <5144B7AC.8000404@cernet.edu.cn> <51458917.6040908@cisco.com>
In-Reply-To: <51458917.6040908@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-2022-jp"
Content-ID: <D90A9EC76ADD52458A8E7BBF226348B6@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<softwires@ietf.org>" <softwires@ietf.org>, "<ot@cisco.com>" <ot@cisco.com>
Subject: Re: [Softwires] MAP tracker issues
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, 17 Mar 2013 11:52:35 -0000

On Mar 17, 2013, at 5:12 AM, Shishio Tsuchiya <shtsuchi@cisco.com> wrote:
> I know 3 Geeks who lived in IPv4 15 port and IPv6 internet environment.
> They reported it was comfortable for home network.

Wow.   Do you have any idea what traffic remained on IPv6 while they were d=
oing this?


From tom.taylor.stds@gmail.com  Sun Mar 17 17:03:45 2013
Return-Path: <tom.taylor.stds@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 7429F21F8804 for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 17:03:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, J_CHICKENPOX_62=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 i7-gzF2X6tlE for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 17:03:45 -0700 (PDT)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by ietfa.amsl.com (Postfix) with ESMTP id E96C121F8800 for <softwires@ietf.org>; Sun, 17 Mar 2013 17:03:44 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id j8so1352721qah.6 for <softwires@ietf.org>; Sun, 17 Mar 2013 17:03:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=nzl3rbIX6HkWWjzWwieiTvsZQnz4BYVk4excLzY0z/E=; b=ladnyqWT85m3QBAlT3fbWzZjbCfYHnuKAWRh5a85XKlzsX7vCFc+Y4Cy+wRNLf5J+P LC2PBbS8bGSIh/W01BJyVxqbAlslRSzZIxKkOoUwt9AIOvw/4BmIiQagvjf40UUG0Xzu 3Q8DsCLlHiCeo8Frloix4CWt5cdqMMMDsy5pTHO5FIGMm14IaaC+GnbNVftfYiGrVS1T helQ2jzdH/WSWK7eY5nrebN330DZic42qFPV1/+EojF1P6nfrQnbLuYMY+9KIBTaq9SG mLmN4HRxzhEHl2crBz6+eOKH6fIuYic90fJrDx6n6a228LF5xZstuFsfWQfoClNUNgq9 LHqA==
X-Received: by 10.229.177.142 with SMTP id bi14mr4028329qcb.1.1363565024482; Sun, 17 Mar 2013 17:03:44 -0700 (PDT)
Received: from [127.0.0.1] (fl-69-34-239-45.sta.embarqhsd.net. [69.34.239.45]) by mx.google.com with ESMTPS id q6sm26891244qeu.1.2013.03.17.17.03.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Mar 2013 17:03:43 -0700 (PDT)
Message-ID: <514659DD.1060100@gmail.com>
Date: Sun, 17 Mar 2013 20:03:41 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Shishio Tsuchiya <shtsuchi@cisco.com>
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>	<27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com> <F1E72F77-4E0B-4749-98D1-C2CB7AC7729C@gmail.com> <5144B7AC.8000404@cernet.edu.cn> <51458917.6040908@cisco.com>
In-Reply-To: <51458917.6040908@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org, ot@cisco.com
Subject: Re: [Softwires] MAP tracker issues
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, 18 Mar 2013 00:03:45 -0000

I would think the number of blocks through which the ports are scattered 
has very little relevance to the user experience. Surely the key factor 
is the sharing ratio?

Tom Taylor

On 17/03/2013 5:12 AM, Shishio Tsuchiya wrote:
> I know 3 Geeks who lived in IPv4 15 port and IPv6 internet environment.
> They reported it was comfortable for home network.
>
> And JANOG tested 15port of MAP-E.
> http://tools.ietf.org/html/draft-janog-softwire-report-01#section-4.9
> MAP-E provides IPv6 to CPE,so CPE can use DNS resolver proxy.
>
> There is no performance impact,if they supported DNS proxy.
>
> Regards,
> -Shishio
>
...

From shtsuchi@cisco.com  Sun Mar 17 19:31:30 2013
Return-Path: <shtsuchi@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 B58B021F8C9F for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 19:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.399
X-Spam-Level: 
X-Spam-Status: No, score=-9.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_55=0.6, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_HI=-8]
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 XMJcF-15Hees for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 19:31:30 -0700 (PDT)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 8496B21F8C9D for <softwires@ietf.org>; Sun, 17 Mar 2013 19:31:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=797; q=dns/txt; s=iport; t=1363573889; x=1364783489; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ax3H+6uuxlkujL8SPTaT73JihjyJ4F2xItnYmC51Lmo=; b=SGSMomDbTK3VNAlwdSuQowDpNCiRihS+aTasbRkgQA6vwhiaR6EltRcu un5kHNWUXlsJy9aFFnb4ftwa3JxH4v1x/tsCaTXQJTanakF+CwXHK3iQJ pEVgx5BSqkyLGyeY59Rya6hyEoiIvQ7YzRojrVex2ujpz9j1gdZsXrC8B I=;
X-IronPort-AV: E=Sophos;i="4.84,861,1355097600"; d="scan'208";a="27708415"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 18 Mar 2013 02:31:27 +0000
Received: from dhcp-10-141-41-17.cisco.com (dhcp-10-141-41-17.cisco.com [10.141.41.17]) by bgl-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2I2VQpc032270; Mon, 18 Mar 2013 02:31:26 GMT
Message-ID: <51467C7E.8030607@cisco.com>
Date: Mon, 18 Mar 2013 11:31:26 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ted.Lemon@nominum.com
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com> <27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com> <F1E72F77-4E0B-4749-98D1-C2CB7AC7729C@gmail.com> <5144B7AC.8000404@cernet.edu.cn> <51458917.6040908@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775110D7D@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775110D7D@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org, ot@cisco.com
Subject: Re: [Softwires] MAP tracker issues
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, 18 Mar 2013 02:31:30 -0000

(2013/03/17 7:52), Ted Lemon wrote:
> On Mar 17, 2013, at 5:12 AM, Shishio Tsuchiya <shtsuchi@cisco.com> wrote:
>> I know 3 Geeks who lived in IPv4 15 port and IPv6 internet environment.
>> They reported it was comfortable for home network.
> 
> Wow.   Do you have any idea what traffic remained on IPv6 while they were doing this?
> 
> 

I'm not sure in detail,but they might be enough to live if they can access to facebook,google,ietf and JANOG.:-)
I think,there are some reasons to comfortable.
-Hyper Giants and technical site are already enabled IPv6.
-All of DNS query send to IPv6 DNS server.
-The CPE implementation was completely made to provide A+P function.(not reuse existing NAT implementation)
-Web communication improvement(SPDY or Websocket?)

Regards,
-Shishio




From shtsuchi@cisco.com  Sun Mar 17 20:14:53 2013
Return-Path: <shtsuchi@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 E329F21F89A5 for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 20:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.799
X-Spam-Level: 
X-Spam-Status: No, score=-8.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_HI=-8]
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 IcjkcwXtL7j8 for <softwires@ietfa.amsl.com>; Sun, 17 Mar 2013 20:14:52 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 09E2E21F8995 for <softwires@ietf.org>; Sun, 17 Mar 2013 20:14:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1022; q=dns/txt; s=iport; t=1363576491; x=1364786091; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Wg5UdS7WgBhbdOQwWc9bZ3wr0nAqgWps55tAAttQ7oU=; b=fNgu6GPj1FedCZTO0buRg21XoSh0y5cTAnOfieZdoPRpbMb8DAtuFtbi ZnG4njtdUxFHBq7iXjo2m9z8Nn8G8aupUuLSuQTABT6u7z8YvEBuGx68q DfENvN3Bs7+Fhr64lz2b4z6t81bVVSav47az+m7e8+F2cOXKFz2yQf14Q w=;
X-IronPort-AV: E=Sophos;i="4.84,861,1355097600"; d="scan'208";a="72771160"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 18 Mar 2013 03:14:50 +0000
Received: from dhcp-10-141-41-17.cisco.com (dhcp-10-141-41-17.cisco.com [10.141.41.17]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2I3EnDO025386; Mon, 18 Mar 2013 03:14:49 GMT
Message-ID: <514686A8.1080505@cisco.com>
Date: Mon, 18 Mar 2013 12:14:48 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: tom.taylor.stds@gmail.com
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>	<27CE5820-6934-4378-82D1-C1D1ABC50BD3@gmail.com> <F1E72F77-4E0B-4749-98D1-C2CB7AC7729C@gmail.com> <5144B7AC.8000404@cernet.edu.cn> <51458917.6040908@cisco.com> <514659DD.1060100@gmail.com>
In-Reply-To: <514659DD.1060100@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org, ot@cisco.com
Subject: Re: [Softwires] MAP tracker issues
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, 18 Mar 2013 03:14:53 -0000

Tom
I misunderstood original question.
- Offset 4 versus 6.
  Discussion on value of wasting 3000 port versus simplicity of nibble alignment.
  No objection to moving default offset to 6 (from 4 in revision 04)

I think,this is NOT impact for user experience and implementations.

Regards,
-Shishio

(2013/03/18 9:03), Tom Taylor wrote:
> I would think the number of blocks through which the ports are scattered has very little relevance to the user experience. Surely the key factor is the sharing ratio?
> 
> Tom Taylor
> 
> On 17/03/2013 5:12 AM, Shishio Tsuchiya wrote:
>> I know 3 Geeks who lived in IPv4 15 port and IPv6 internet environment.
>> They reported it was comfortable for home network.
>>
>> And JANOG tested 15port of MAP-E.
>> http://tools.ietf.org/html/draft-janog-softwire-report-01#section-4.9
>> MAP-E provides IPv6 to CPE,so CPE can use DNS resolver proxy.
>>
>> There is no performance impact,if they supported DNS proxy.
>>
>> Regards,
>> -Shishio
>>
> ...
> .
> 



From internet-drafts@ietf.org  Mon Mar 18 05:07:20 2013
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 418EE21F8D1F; Mon, 18 Mar 2013 05:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 KhirRZf0s4uO; Mon, 18 Mar 2013 05:07:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D2F1321F8D12; Mon, 18 Mar 2013 05:07:19 -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: 4.43
Message-ID: <20130318120719.4075.33717.idtracker@ietfa.amsl.com>
Date: Mon, 18 Mar 2013 05:07:19 -0700
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-map-05.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, 18 Mar 2013 12:07:20 -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           : Mapping of Address and Port with Encapsulation (MAP)
	Author(s)       : Ole Troan
                          Wojciech Dec
                          Xing Li
                          Congxiao Bao
                          Satoru Matsushima
                          Tetsuya Murakami
	Filename        : draft-ietf-softwire-map-05.txt
	Pages           : 27
	Date            : 2013-03-18

Abstract:
   This document describes a mechanism for transporting IPv4 packets
   across an IPv6 network using IP encapsulation, and a generic
   mechanism for mapping between IPv6 addresses and IPv4 addresses and
   transport layer ports.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-softwire-map

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-softwire-map-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-map-05


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


From ot@cisco.com  Mon Mar 18 05:13:48 2013
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 7F80C21F8651 for <softwires@ietfa.amsl.com>; Mon, 18 Mar 2013 05:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 h4+gnrEuzPCU for <softwires@ietfa.amsl.com>; Mon, 18 Mar 2013 05:13:47 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA5721F85B0 for <softwires@ietf.org>; Mon, 18 Mar 2013 05:13:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2670; q=dns/txt; s=iport; t=1363608828; x=1364818428; h=mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to; bh=PdbpZEoi+M3uYtlHj/0g8e4f5GhpGyYRuzhPM6sv0TY=; b=OgPVbeGkkVudlfr1ucQuacuzcPPmv+ht61TGKmVsAr31u9frrXr+adbG MNv11KlZGSMG/n/1aJICoYBIx0Vnmj22+A74ETDPe4EIYb/rDKMPBvfuy 7pDR1/BNR8tvgv9FeYCAShMRQi09rDaX5PgyuHsOXNID4sc2tN45MvfHo A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAB0ER1GQ/khM/2dsb2JhbABDhUy/W4FZFnSCJAEBAQMBAQEBNzQQCwtGJzAGEwmIBQYHBcE7jW9zOoJfYQOWXoEfj2ODCzs
X-IronPort-AV: E=Sophos;i="4.84,865,1355097600"; d="scan'208";a="12252457"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 18 Mar 2013 12:13:47 +0000
Received: from dhcp-lys02-vla252-10-147-116-76.cisco.com (dhcp-lys02-vla252-10-147-116-76.cisco.com [10.147.116.76]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2ICDihK002912 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <softwires@ietf.org>; Mon, 18 Mar 2013 12:13:45 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ole Troan <ot@cisco.com>
In-Reply-To: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>
Date: Mon, 18 Mar 2013 13:13:44 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6662E72E-3FEB-4A43-BD3D-0B171622B662@cisco.com>
References: <83188A08-6144-4973-A06B-3FDC8B1736A1@cisco.com>
To: Softwires WG <softwires@ietf.org>
X-Mailer: Apple Mail (2.1499)
Subject: Re: [Softwires] MAP tracker issues
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, 18 Mar 2013 12:13:48 -0000

all,

I have posted a new revision which implements all the agreed resolutions =
in
Orlando. including renaming the example sections referring to 1:1.

new draft and diffs are available here:

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-softwire-map-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-map-05

I have also closed the tickets as agreed in Orlando. please do not =
reopen them.

this draft should now be ready for a WGLC.

Best regards,
Ole





> hi,
>=20
> as agreed in the meeting here is the summary of the discussion of the =
MAP open issues.
> the plan is to leave these open for discussion for a week (until next =
Monday),
> then issue revision -05, that we will ask to be last called in the WG.
>=20
> #18     Title and file name of the MAP-E draft need to be updated      =
=20
>          No-one in the room objected to keeping name as is.
>          Close ticket.
>=20
> #19     IPv4 address superfluous in MAP-E Interface IDs map-e          =
        =20
>          No one in the room objected to keeping interface-id as is in =
revision 04.
>          Close ticket.
>=20
> #21     Fragmentation must not be handled according to RFC 2473 map-e  =
        =20
>          It is an issue, but it is a generic problem that should be =
fixed in a RFC2473bis.
>          Have descriptive text in the MAP document describing the =
issue and referencing RFC4459.
>=20
>          Current proposed text:
>          "Multiple BRs using the same anycast source address could =
send
>   fragmented packets to the same CE at the same time.  If the
>   fragmented packets from different BRs happen to use the same =
fragment
>   ID, incorrect reassembly might occur.  See [RFC4459] for an analysis
>   of the problem.  Section 3.4 suggests solving the problem by=20
>   fragmenting the inner packet."
>=20
>          Close ticket with above text.
>          Chairs to consider RFC2473bis
>=20
> #25     Maintain or remove MAP1:1 Mode?
>          Remove section 7.4 (Address Independence). Rename 1:1 =
example.
>=20
> - Offset 4 versus 6.
>  Discussion on value of wasting 3000 port versus simplicity of nibble =
alignment.
>  No objection to moving default offset to 6 (from 4 in revision 04)
>=20
> - Updated text for appendix B
>  Tom Taylor to propose updates to appendix B (GMA appendix).
>=20
> cheers,
> Ole
>=20
>=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From suresh.krishnan@ericsson.com  Tue Mar 19 10:16:01 2013
Return-Path: <suresh.krishnan@ericsson.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 7F4BE21F8F22 for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 10:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 sfpjmxn0oqqT for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 10:16:01 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id EABD921F8F18 for <softwires@ietf.org>; Tue, 19 Mar 2013 10:16:00 -0700 (PDT)
X-AuditID: c618062d-b7f0d6d00000097e-c5-51489d50ae6f
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id A8.99.02430.05D98415; Tue, 19 Mar 2013 18:16:00 +0100 (CET)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC002.ericsson.se (147.117.188.78) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 19 Mar 2013 13:15:59 -0400
Received: from [142.133.112.81] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 19 Mar 2013 13:15:59 -0400
Message-ID: <51489CBC.4050508@ericsson.com>
Date: Tue, 19 Mar 2013 13:13:32 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Softwires WG <softwires@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrIJMWRmVeSWpSXmKPExsUyuXSPn27AXI9Ag1k7lS0OL9vK5MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujJZdVxkLbrBUfG/5z9TA+Iy5i5GTQ0LAROL3hE52CFtM4sK9 9WxdjFwcQgJHGCWezVvFCOHsYZTYt+AJK4SzjVFi5bJPYO28AtoSPW+/sIDYLAKqEt2ND8BG sQGN3bDzMxOILSoQJtH7+hwjRL2gxMmZT8DqRYDqn+x8wAZiCwukSpz53MIEcYakxJYX7WBz mAX0JKZcbWGEsOUltr+dA7ZXSEBTYuua76wTGAVmIRk7C0nLLCQtCxiZVzFylBanluWmGxls YgQG2zEJNt0djHteWh5ilOZgURLnDXK9ECAkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBcZOs UWH/Kh2Dc0lLNJ1+np/NcmaV0OZZh2T31f9h9jAKcc+cWPqgY5mhx9tw4zXGWxzNL/rUzL6x R7Dq9JF//KkbGi+x9N51DCz59nDJ9zV3tiR4PFOwqpuqaiJstYdFwquxRkdn3vcPAo3z2j6/ 9Ts7e9b6Pz4rLvLkT57Fc3+z/AkN8+sHC5VYijMSDbWYi4oTASTl+T8EAgAA
Subject: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 19 Mar 2013 17:16:01 -0000

Hi all,
  This draft was presented during the softwire WG meeting at IETF86 and
a subsequent poll of the room indicated that there was strong support
for adopting this draft as a WG document.

This call is being initiated to confirm whether there is WG consensus
towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
softwire WG draft. Please state whether or not you're in favor of the
adoption by replying to this email. If you are not in favor, please also
state your objections in your response. This adoption call will complete
on 2013-04-02.

Regards
Suresh & Yong

From tom.taylor.stds@gmail.com  Tue Mar 19 11:15:36 2013
Return-Path: <tom.taylor.stds@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 4987421F8CE0 for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 11:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.048
X-Spam-Level: 
X-Spam-Status: No, score=0.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.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 GNx8aCtqpjwi for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 11:15:35 -0700 (PDT)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id AD3A421F8D51 for <softwires@ietf.org>; Tue, 19 Mar 2013 11:15:35 -0700 (PDT)
Received: by mail-ie0-f171.google.com with SMTP id 10so1028184ied.30 for <softwires@ietf.org>; Tue, 19 Mar 2013 11:15:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-antivirus:x-antivirus-status; bh=ZRr0DVqZnRMWCMctjZwdWLRo/trUG1OTdM84RMe4sVQ=; b=BiqJJpZG0Eo+MfPvAons0s+XCf7kY+7TLiJwpi7svcPsKTSuZq0R8wrAAa6f6OIiCg R0UqgrU9HiOd4DDndbBlz0J5IGW9tyYGE5BaoLTFDA99kxoRSo88NOCIEG3JUqYmLc7D izh34kpVKCS4ajLqC4WR5H/NzXBb9Ogtvv39Bz4LLQ03n/fHNF1DNq93kPW0bg6bfMqM jTOCg2TdLxXYumdGOWzC+BnXDQc7idH1qi9iqsAp17XnTz2W5f0V1rH1dnSl1+XIrHoG SNzsiJsH8Wm5zyaULRYlc12yM35vFzzjQNaA6VA/by3wINykAOv5PvcL2WvO7lTomrsu MXIw==
X-Received: by 10.50.13.228 with SMTP id k4mr2650233igc.30.1363716935152; Tue, 19 Mar 2013 11:15:35 -0700 (PDT)
Received: from [127.0.0.1] (dsl-173-206-3-59.tor.primus.ca. [173.206.3.59]) by mx.google.com with ESMTPS id xc3sm1418382igb.10.2013.03.19.11.15.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Mar 2013 11:15:34 -0700 (PDT)
Message-ID: <5148AB45.1090707@gmail.com>
Date: Tue, 19 Mar 2013 14:15:33 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <51489CBC.4050508@ericsson.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130319-0, 19/03/2013), Outbound message
X-Antivirus-Status: Clean
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 19 Mar 2013 18:15:36 -0000

Support.

On 19/03/2013 1:13 PM, Suresh Krishnan wrote:
> Hi all,
>    This draft was presented during the softwire WG meeting at IETF86 and
> a subsequent poll of the room indicated that there was strong support
> for adopting this draft as a WG document.
>
> This call is being initiated to confirm whether there is WG consensus
> towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
> softwire WG draft. Please state whether or not you're in favor of the
> adoption by replying to this email. If you are not in favor, please also
> state your objections in your response. This adoption call will complete
> on 2013-04-02.
>
> Regards
> Suresh & Yong
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

From leo.liubing@huawei.com  Tue Mar 19 18:45:11 2013
Return-Path: <leo.liubing@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 9301B21F8D46 for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 18:45:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNEHbgDAxBpf for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 18:45:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9501F21F8D00 for <softwires@ietf.org>; Tue, 19 Mar 2013 18:45:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APO58736; Wed, 20 Mar 2013 01:45:09 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 20 Mar 2013 01:43:51 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 20 Mar 2013 01:44:42 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.42]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Wed, 20 Mar 2013 09:44:36 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Softwires WG <softwires@ietf.org>
Thread-Topic: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
Thread-Index: AQHOJMVx+8CpgxLhkkOAkTtgRxwvtpitzwfA
Date: Wed, 20 Mar 2013 01:44:35 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6EACA8@nkgeml506-mbx.china.huawei.com>
References: <51489CBC.4050508@ericsson.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 01:45:11 -0000

I am in favor of adoption.

> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
> Behalf Of Suresh Krishnan
> Sent: Wednesday, March 20, 2013 1:14 AM
> To: Softwires WG
> Subject: [Softwires] Call for confirming the adoption of
> draft-cui-softwire-b4-translated-ds-lite-11 as WG item
>=20
> Hi all,
>   This draft was presented during the softwire WG meeting at IETF86 and
> a subsequent poll of the room indicated that there was strong support
> for adopting this draft as a WG document.
>=20
> This call is being initiated to confirm whether there is WG consensus
> towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
> softwire WG draft. Please state whether or not you're in favor of the
> adoption by replying to this email. If you are not in favor, please also
> state your objections in your response. This adoption call will complete
> on 2013-04-02.
>=20
> Regards
> Suresh & Yong
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From jiangsheng@huawei.com  Tue Mar 19 18:59:15 2013
Return-Path: <jiangsheng@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 70C4221F8E13 for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 18:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  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 2ZedJi73avoE for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 18:59:15 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8573F21F8DEF for <softwires@ietf.org>; Tue, 19 Mar 2013 18:59:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQV58675; Wed, 20 Mar 2013 01:59:10 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 20 Mar 2013 01:58:18 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 20 Mar 2013 01:59:10 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.21]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Wed, 20 Mar 2013 09:59:06 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Softwires WG <softwires@ietf.org>
Thread-Topic: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
Thread-Index: AQHOJMVyl/X/2UbuyEaNdJIEARDB6Zit00cQ
Date: Wed, 20 Mar 2013 01:59:05 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AA02CB7@nkgeml512-mbx.china.huawei.com>
References: <51489CBC.4050508@ericsson.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 01:59:15 -0000

U3VwcG9ydC4gSXQgaXMgYW4gdXNlZnVsIGRvY3VtZW50Lg0KDQpTaGVuZw0KDQo+LS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBzb2Z0d2lyZXMtYm91bmNlc0BpZXRmLm9yZyBbbWFp
bHRvOnNvZnR3aXJlcy1ib3VuY2VzQGlldGYub3JnXSBPbg0KPkJlaGFsZiBPZiBTdXJlc2ggS3Jp
c2huYW4NCj5TZW50OiBXZWRuZXNkYXksIE1hcmNoIDIwLCAyMDEzIDE6MTQgQU0NCj5UbzogU29m
dHdpcmVzIFdHDQo+U3ViamVjdDogW1NvZnR3aXJlc10gQ2FsbCBmb3IgY29uZmlybWluZyB0aGUg
YWRvcHRpb24gb2YNCj5kcmFmdC1jdWktc29mdHdpcmUtYjQtdHJhbnNsYXRlZC1kcy1saXRlLTEx
IGFzIFdHIGl0ZW0NCj4NCj5IaSBhbGwsDQo+ICBUaGlzIGRyYWZ0IHdhcyBwcmVzZW50ZWQgZHVy
aW5nIHRoZSBzb2Z0d2lyZSBXRyBtZWV0aW5nIGF0IElFVEY4NiBhbmQNCj5hIHN1YnNlcXVlbnQg
cG9sbCBvZiB0aGUgcm9vbSBpbmRpY2F0ZWQgdGhhdCB0aGVyZSB3YXMgc3Ryb25nIHN1cHBvcnQN
Cj5mb3IgYWRvcHRpbmcgdGhpcyBkcmFmdCBhcyBhIFdHIGRvY3VtZW50Lg0KPg0KPlRoaXMgY2Fs
bCBpcyBiZWluZyBpbml0aWF0ZWQgdG8gY29uZmlybSB3aGV0aGVyIHRoZXJlIGlzIFdHIGNvbnNl
bnN1cw0KPnRvd2FyZHMgYWRvcHRpb24gb2YgZHJhZnQtY3VpLXNvZnR3aXJlLWI0LXRyYW5zbGF0
ZWQtZHMtbGl0ZS0xMSBhcyBhDQo+c29mdHdpcmUgV0cgZHJhZnQuIFBsZWFzZSBzdGF0ZSB3aGV0
aGVyIG9yIG5vdCB5b3UncmUgaW4gZmF2b3Igb2YgdGhlDQo+YWRvcHRpb24gYnkgcmVwbHlpbmcg
dG8gdGhpcyBlbWFpbC4gSWYgeW91IGFyZSBub3QgaW4gZmF2b3IsIHBsZWFzZSBhbHNvDQo+c3Rh
dGUgeW91ciBvYmplY3Rpb25zIGluIHlvdXIgcmVzcG9uc2UuIFRoaXMgYWRvcHRpb24gY2FsbCB3
aWxsIGNvbXBsZXRlDQo+b24gMjAxMy0wNC0wMi4NCj4NCj5SZWdhcmRzDQo+U3VyZXNoICYgWW9u
Zw0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+U29m
dHdpcmVzIG1haWxpbmcgbGlzdA0KPlNvZnR3aXJlc0BpZXRmLm9yZw0KPmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vc29mdHdpcmVzDQo=

From cathy.zhou@huawei.com  Tue Mar 19 19:49:39 2013
Return-Path: <cathy.zhou@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 89BEF21F87A4 for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 19:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X+79O+U5NapJ for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 19:49:38 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D070D21F86B7 for <softwires@ietf.org>; Tue, 19 Mar 2013 19:49:37 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQX00175; Wed, 20 Mar 2013 02:49:36 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 20 Mar 2013 02:48:18 +0000
Received: from SZXEML462-HUB.china.huawei.com (10.82.67.205) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 20 Mar 2013 02:49:09 +0000
Received: from SZXEML513-MBS.china.huawei.com ([169.254.8.177]) by szxeml462-hub.china.huawei.com ([10.82.67.205]) with mapi id 14.01.0323.007; Wed, 20 Mar 2013 10:49:04 +0800
From: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
Thread-Index: AQHOJMV0fZIDpGmDFU25PNniPPuJP5isy9aAgAEVQlA=
Date: Wed, 20 Mar 2013 02:49:03 +0000
Message-ID: <A6A061BEE5DDC94A9692D9D81AF776DF2DF29614@szxeml513-mbs.china.huawei.com>
References: <51489CBC.4050508@ericsson.com> <5148AB45.1090707@gmail.com>
In-Reply-To: <5148AB45.1090707@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.76.105]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 02:49:39 -0000

+1 support.

> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
> Behalf Of Tom Taylor
> Sent: Wednesday, March 20, 2013 2:16 AM
> To: Suresh Krishnan
> Cc: Softwires WG
> Subject: Re: [Softwires] Call for confirming the adoption of
> draft-cui-softwire-b4-translated-ds-lite-11 as WG item
>=20
> Support.
>=20
> On 19/03/2013 1:13 PM, Suresh Krishnan wrote:
> > Hi all,
> >    This draft was presented during the softwire WG meeting at IETF86
> and
> > a subsequent poll of the room indicated that there was strong support
> > for adopting this draft as a WG document.
> >
> > This call is being initiated to confirm whether there is WG consensus
> > towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
> > softwire WG draft. Please state whether or not you're in favor of the
> > adoption by replying to this email. If you are not in favor, please als=
o
> > state your objections in your response. This adoption call will complet=
e
> > on 2013-04-02.
> >
> > Regards
> > Suresh & Yong
> > _______________________________________________
> > 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 chenycmx@gmail.com  Tue Mar 19 20:34:42 2013
Return-Path: <chenycmx@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 072FF21F8A3F for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 20:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.706
X-Spam-Level: 
X-Spam-Status: No, score=0.706 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RDNS_NONE=0.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 S5OAlPrRw4fa for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 20:34:41 -0700 (PDT)
Received: from mail-da0-x236.google.com (mail-da0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 81CB521F8A38 for <softwires@ietf.org>; Tue, 19 Mar 2013 20:34:41 -0700 (PDT)
Received: by mail-da0-f54.google.com with SMTP id p1so705367dad.13 for <softwires@ietf.org>; Tue, 19 Mar 2013 20:34:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:reply-to:subject:references:x-priority :x-guid:x-has-attach:x-mailer:mime-version:message-id:content-type; bh=O/FLZ3eMfLQgU+RKHdmzY/1mbd2z3IVUjRvxsq2YOCM=; b=l27SKo5HZqOEteMly+tEmhy2MDIHN92HRfYerInwwasONQsrNe78y/9JwwVtTrhV3U g/mtfGthzxaPdUupSbPX3QFPXwhlbic0rf5unQvxd7am+BEk6/x5NbD6bTtYG79za9/P Uzh9S6jyaNt11Xb05CpcDn7DuRZjkSj1hTvwujPOPFxuF/G11glA4y8sJvZdPsTDx4lD RmpBavYg5eQtklzgtRVE2N9J6Idtq1ZUYUeirXzzAPcAHW0lEUQPNGLzo5uw1EC2FpW1 1WsGrbIBDDHxF2or8Hy6f4OznFv2+KMyyKNsqo6vrXwDW8Nz1lWbojgPdhPDW5+Vw5QA mSvw==
X-Received: by 10.68.231.42 with SMTP id td10mr6627045pbc.174.1363750481233; Tue, 19 Mar 2013 20:34:41 -0700 (PDT)
Received: from user-902eaffedc ([114.255.40.13]) by mx.google.com with ESMTPS id xc4sm349495pbc.41.2013.03.19.20.34.33 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 19 Mar 2013 20:34:39 -0700 (PDT)
Date: Wed, 20 Mar 2013 11:34:36 +0800
From: "Yuchi Chen" <chenycmx@gmail.com>
To: "Suresh Krishnan" <suresh.krishnan@ericsson.com>,  "softwires WG" <softwires@ietf.org>
References: <51489CBC.4050508@ericsson.com>
X-Priority: 3
X-GUID: BAA99380-AA20-40F3-8AC8-03B8778AF3BE
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.88[cn]
Mime-Version: 1.0
Message-ID: <201303201134303590730@gmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart507507105886_=----"
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: chenycmx <chenycmx@gmail.com>
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, 20 Mar 2013 03:34:42 -0000

This is a multi-part message in MIME format.

------=_001_NextPart507507105886_=----
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGkgYWxsLA0KDQorMSBTdXBwb3J0Lg0KDQpCZXN0IHJlZ2FyZHMhDQoNCg0KDQpZdWNoaSBDaGVu
IA0KDQpGcm9tOiBTdXJlc2ggS3Jpc2huYW4NCkRhdGU6IDIwMTMtMDMtMjAgMDE6MTMNClRvOiBT
b2Z0d2lyZXMgV0cNClN1YmplY3Q6IFtTb2Z0d2lyZXNdIENhbGwgZm9yIGNvbmZpcm1pbmcgdGhl
IGFkb3B0aW9uIG9mIGRyYWZ0LWN1aS1zb2Z0d2lyZS1iNC10cmFuc2xhdGVkLWRzLWxpdGUtMTEg
YXMgV0cgaXRlbQ0KSGkgYWxsLA0KICBUaGlzIGRyYWZ0IHdhcyBwcmVzZW50ZWQgZHVyaW5nIHRo
ZSBzb2Z0d2lyZSBXRyBtZWV0aW5nIGF0IElFVEY4NiBhbmQNCmEgc3Vic2VxdWVudCBwb2xsIG9m
IHRoZSByb29tIGluZGljYXRlZCB0aGF0IHRoZXJlIHdhcyBzdHJvbmcgc3VwcG9ydA0KZm9yIGFk
b3B0aW5nIHRoaXMgZHJhZnQgYXMgYSBXRyBkb2N1bWVudC4NCg0KVGhpcyBjYWxsIGlzIGJlaW5n
IGluaXRpYXRlZCB0byBjb25maXJtIHdoZXRoZXIgdGhlcmUgaXMgV0cgY29uc2Vuc3VzDQp0b3dh
cmRzIGFkb3B0aW9uIG9mIGRyYWZ0LWN1aS1zb2Z0d2lyZS1iNC10cmFuc2xhdGVkLWRzLWxpdGUt
MTEgYXMgYQ0Kc29mdHdpcmUgV0cgZHJhZnQuIFBsZWFzZSBzdGF0ZSB3aGV0aGVyIG9yIG5vdCB5
b3UncmUgaW4gZmF2b3Igb2YgdGhlDQphZG9wdGlvbiBieSByZXBseWluZyB0byB0aGlzIGVtYWls
LiBJZiB5b3UgYXJlIG5vdCBpbiBmYXZvciwgcGxlYXNlIGFsc28NCnN0YXRlIHlvdXIgb2JqZWN0
aW9ucyBpbiB5b3VyIHJlc3BvbnNlLiBUaGlzIGFkb3B0aW9uIGNhbGwgd2lsbCBjb21wbGV0ZQ0K
b24gMjAxMy0wNC0wMi4NCg0KUmVnYXJkcw0KU3VyZXNoICYgWW9uZw0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClNvZnR3aXJlcyBtYWlsaW5nIGxpc3QN
ClNvZnR3aXJlc0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9zb2Z0d2lyZXM=

------=_001_NextPart507507105886_=----
Content-Type: text/html;
	charset="gb2312"
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=3Dgb2312">
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	FONT-SIZE: 10pt; COLOR: #000000; LINE-HEIGHT: 1.5; FONT-FAMILY: verdana
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>

<META content=3D"MSHTML 6.00.2900.6182" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV style=3D"FONT-FAMILY: Verdana">Hi all,</DIV>
<DIV style=3D"FONT-FAMILY: Verdana">&nbsp;</DIV>
<DIV style=3D"FONT-FAMILY: Verdana">+1 Support.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best regards!</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV style=3D"FONT-FAMILY: Verdana"><SPAN><SPAN=20
style=3D"FONT-SIZE: 10.5pt; COLOR: #000000; FONT-FAMILY: =CB=CE=CC=E5">Yuc=
hi=20
Chen&nbsp;</SPAN></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4d=
f 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium n=
one; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<DIV=20
style=3D"PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px; BACKGROUN=
D: #efefef; PADDING-BOTTOM: 8px; COLOR: #000000; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:suresh.krishnan@ericsson.com">Sur=
esh=20
Krishnan</A></DIV>
<DIV><B>Date:</B>&nbsp;2013-03-20&nbsp;01:13</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:softwires@ietf.org">Softwires WG</A=
></DIV>
<DIV><B>Subject:</B>&nbsp;[Softwires] Call for confirming the adoption of=20
draft-cui-softwire-b4-translated-ds-lite-11 as WG item</DIV></DIV></DIV>
<DIV>
<DIV>Hi&nbsp;all,</DIV>
<DIV>&nbsp;&nbsp;This&nbsp;draft&nbsp;was&nbsp;presented&nbsp;during&nbsp;=
the&nbsp;softwire&nbsp;WG&nbsp;meeting&nbsp;at&nbsp;IETF86&nbsp;and</DIV>
<DIV>a&nbsp;subsequent&nbsp;poll&nbsp;of&nbsp;the&nbsp;room&nbsp;indicated=
&nbsp;that&nbsp;there&nbsp;was&nbsp;strong&nbsp;support</DIV>
<DIV>for&nbsp;adopting&nbsp;this&nbsp;draft&nbsp;as&nbsp;a&nbsp;WG&nbsp;do=
cument.</DIV>
<DIV>&nbsp;</DIV>
<DIV>This&nbsp;call&nbsp;is&nbsp;being&nbsp;initiated&nbsp;to&nbsp;confirm=
&nbsp;whether&nbsp;there&nbsp;is&nbsp;WG&nbsp;consensus</DIV>
<DIV>towards&nbsp;adoption&nbsp;of&nbsp;draft-cui-softwire-b4-translated-d=
s-lite-11&nbsp;as&nbsp;a</DIV>
<DIV>softwire&nbsp;WG&nbsp;draft.&nbsp;Please&nbsp;state&nbsp;whether&nbsp=
;or&nbsp;not&nbsp;you're&nbsp;in&nbsp;favor&nbsp;of&nbsp;the</DIV>
<DIV>adoption&nbsp;by&nbsp;replying&nbsp;to&nbsp;this&nbsp;email.&nbsp;If&=
nbsp;you&nbsp;are&nbsp;not&nbsp;in&nbsp;favor,&nbsp;please&nbsp;also</DIV>
<DIV>state&nbsp;your&nbsp;objections&nbsp;in&nbsp;your&nbsp;response.&nbsp=
;This&nbsp;adoption&nbsp;call&nbsp;will&nbsp;complete</DIV>
<DIV>on&nbsp;2013-04-02.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards</DIV>
<DIV>Suresh&nbsp;&amp;&nbsp;Yong</DIV>
<DIV>_______________________________________________</DIV>
<DIV>Softwires&nbsp;mailing&nbsp;list</DIV>
<DIV>Softwires@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/softwires</DIV></DIV></BODY></H=
TML>

------=_001_NextPart507507105886_=------


From xiechf01@gmail.com  Tue Mar 19 20:45:52 2013
Return-Path: <xiechf01@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 6606121F8D00 for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 20:45:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.706
X-Spam-Level: 
X-Spam-Status: No, score=0.706 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RDNS_NONE=0.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 4SE7QPKI3bUh for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 20:45:50 -0700 (PDT)
Received: from mail-da0-x235.google.com (mail-da0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3E721F8BB6 for <softwires@ietf.org>; Tue, 19 Mar 2013 20:45:49 -0700 (PDT)
Received: by mail-da0-f53.google.com with SMTP id n34so711795dal.12 for <softwires@ietf.org>; Tue, 19 Mar 2013 20:45:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:reply-to:subject:references:x-priority :x-has-attach:x-mailer:mime-version:message-id:content-type; bh=7J8TRl7fbERvMzmVApzsdVHBIc7wTL72YNztHajbXQw=; b=yz07aVgV4SPui+JrvMAPb/q2OxZctvEFcNq1H/dweVr8n3IhCy8lje65rD2/sK3Ztr PNxoDWNUk6SoC0mW0BIAByju/nBv0+IMbP1li/neOH6nAIuElgBdXZ15RmtuP/j8g3XX NQflbUsZlwFo2tT4DO7dnAgyJGkavi1PDMbGM34CK/0TQyNdzCaC6f/QmACnPNPWWb5X UOxUyffdUwdxnZvj3r20NAReTSZelcavhBO55Hl60+8I4fD0CzArQ3aq7Wj0y5fQDQ0b oXSNI/US+G7oxJJbhLwxZgB65bA/8TYVouWOEu2/WwR4OGAPNizJEIVh8Xi3HXIo/zqx 1/9g==
X-Received: by 10.68.39.195 with SMTP id r3mr6845584pbk.53.1363751149561; Tue, 19 Mar 2013 20:45:49 -0700 (PDT)
Received: from xiechf-PC2 ([219.142.69.78]) by mx.google.com with ESMTPS id ab1sm388172pbd.37.2013.03.19.20.45.46 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 19 Mar 2013 20:45:48 -0700 (PDT)
Date: Wed, 20 Mar 2013 11:45:42 +0800
From: xiechf01-Gmail <xiechf01@gmail.com>
To: "Suresh Krishnan" <suresh.krishnan@ericsson.com>,  "Softwires WG" <softwires@ietf.org>
References: <51489CBC.4050508@ericsson.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <201303201145392784423@gmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart116357003513_=----"
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: xiechf01 <xiechf01@gmail.com>
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, 20 Mar 2013 03:45:52 -0000

This is a multi-part message in MIME format.

------=_001_NextPart116357003513_=----
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

DQpIaSwgYWxsDQogICAgICAgKzEsIHN1cHBvcnQuIA0KDQpDaG9uZ2ZlbmcNCg0KDQpGcm9tOiBT
dXJlc2ggS3Jpc2huYW4NCkRhdGU6IDIwMTMtMDMtMjAgMDE6MTMNClRvOiBTb2Z0d2lyZXMgV0cN
ClN1YmplY3Q6IFtTb2Z0d2lyZXNdIENhbGwgZm9yIGNvbmZpcm1pbmcgdGhlIGFkb3B0aW9uIG9m
IGRyYWZ0LWN1aS1zb2Z0d2lyZS1iNC10cmFuc2xhdGVkLWRzLWxpdGUtMTEgYXMgV0cgaXRlbQ0K
SGkgYWxsLA0KICBUaGlzIGRyYWZ0IHdhcyBwcmVzZW50ZWQgZHVyaW5nIHRoZSBzb2Z0d2lyZSBX
RyBtZWV0aW5nIGF0IElFVEY4NiBhbmQNCmEgc3Vic2VxdWVudCBwb2xsIG9mIHRoZSByb29tIGlu
ZGljYXRlZCB0aGF0IHRoZXJlIHdhcyBzdHJvbmcgc3VwcG9ydA0KZm9yIGFkb3B0aW5nIHRoaXMg
ZHJhZnQgYXMgYSBXRyBkb2N1bWVudC4NCg0KVGhpcyBjYWxsIGlzIGJlaW5nIGluaXRpYXRlZCB0
byBjb25maXJtIHdoZXRoZXIgdGhlcmUgaXMgV0cgY29uc2Vuc3VzDQp0b3dhcmRzIGFkb3B0aW9u
IG9mIGRyYWZ0LWN1aS1zb2Z0d2lyZS1iNC10cmFuc2xhdGVkLWRzLWxpdGUtMTEgYXMgYQ0Kc29m
dHdpcmUgV0cgZHJhZnQuIFBsZWFzZSBzdGF0ZSB3aGV0aGVyIG9yIG5vdCB5b3UncmUgaW4gZmF2
b3Igb2YgdGhlDQphZG9wdGlvbiBieSByZXBseWluZyB0byB0aGlzIGVtYWlsLiBJZiB5b3UgYXJl
IG5vdCBpbiBmYXZvciwgcGxlYXNlIGFsc28NCnN0YXRlIHlvdXIgb2JqZWN0aW9ucyBpbiB5b3Vy
IHJlc3BvbnNlLiBUaGlzIGFkb3B0aW9uIGNhbGwgd2lsbCBjb21wbGV0ZQ0Kb24gMjAxMy0wNC0w
Mi4NCg0KUmVnYXJkcw0KU3VyZXNoICYgWW9uZw0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NClNvZnR3aXJlcyBtYWlsaW5nIGxpc3QNClNvZnR3aXJlc0Bp
ZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zb2Z0d2lyZXM=

------=_001_NextPart116357003513_=----
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3DGB2312" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =CE=A2=C8=ED=D1=C5=BA=DA; COLOR: #000080; =
FONT-SIZE: 10.5pt
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 9.00.8112.16470"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>&nbsp;</DIV>
<DIV>Hi, all</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+1, support. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Chongfeng</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:suresh.krishnan@ericsson.com">Sur=
esh=20
Krishnan</A></DIV>
<DIV><B>Date:</B>&nbsp;2013-03-20&nbsp;01:13</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:softwires@ietf.org">Softwires WG</A=
></DIV>
<DIV><B>Subject:</B>&nbsp;[Softwires] Call for confirming the adoption of=20
draft-cui-softwire-b4-translated-ds-lite-11 as WG item</DIV></DIV></DIV>
<DIV>
<DIV>Hi&nbsp;all,</DIV>
<DIV>&nbsp;&nbsp;This&nbsp;draft&nbsp;was&nbsp;presented&nbsp;during&nbsp;=
the&nbsp;softwire&nbsp;WG&nbsp;meeting&nbsp;at&nbsp;IETF86&nbsp;and</DIV>
<DIV>a&nbsp;subsequent&nbsp;poll&nbsp;of&nbsp;the&nbsp;room&nbsp;indicated=
&nbsp;that&nbsp;there&nbsp;was&nbsp;strong&nbsp;support</DIV>
<DIV>for&nbsp;adopting&nbsp;this&nbsp;draft&nbsp;as&nbsp;a&nbsp;WG&nbsp;do=
cument.</DIV>
<DIV>&nbsp;</DIV>
<DIV>This&nbsp;call&nbsp;is&nbsp;being&nbsp;initiated&nbsp;to&nbsp;confirm=
&nbsp;whether&nbsp;there&nbsp;is&nbsp;WG&nbsp;consensus</DIV>
<DIV>towards&nbsp;adoption&nbsp;of&nbsp;draft-cui-softwire-b4-translated-d=
s-lite-11&nbsp;as&nbsp;a</DIV>
<DIV>softwire&nbsp;WG&nbsp;draft.&nbsp;Please&nbsp;state&nbsp;whether&nbsp=
;or&nbsp;not&nbsp;you're&nbsp;in&nbsp;favor&nbsp;of&nbsp;the</DIV>
<DIV>adoption&nbsp;by&nbsp;replying&nbsp;to&nbsp;this&nbsp;email.&nbsp;If&=
nbsp;you&nbsp;are&nbsp;not&nbsp;in&nbsp;favor,&nbsp;please&nbsp;also</DIV>
<DIV>state&nbsp;your&nbsp;objections&nbsp;in&nbsp;your&nbsp;response.&nbsp=
;This&nbsp;adoption&nbsp;call&nbsp;will&nbsp;complete</DIV>
<DIV>on&nbsp;2013-04-02.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards</DIV>
<DIV>Suresh&nbsp;&amp;&nbsp;Yong</DIV>
<DIV>_______________________________________________</DIV>
<DIV>Softwires&nbsp;mailing&nbsp;list</DIV>
<DIV>Softwires@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/softwires</DIV></DIV></BODY></H=
TML>

------=_001_NextPart116357003513_=------


From yiu_lee@cable.comcast.com  Tue Mar 19 20:48:50 2013
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 AFEAB21F845E for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 20:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.365
X-Spam-Level: 
X-Spam-Status: No, score=-102.365 tagged_above=-999 required=5 tests=[AWL=2.866, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, 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 jd-gTHno2NI0 for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 20:48:50 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 2BE3721F8454 for <softwires@ietf.org>; Tue, 19 Mar 2013 20:48:50 -0700 (PDT)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.61787113; Tue, 19 Mar 2013 21:47:53 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.236]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Tue, 19 Mar 2013 23:48:46 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Softwires WG <softwires@ietf.org>
Thread-Topic: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
Thread-Index: AQHOJR3S4sTC1ALkRU6M7xPTnX+YCQ==
Date: Wed, 20 Mar 2013 03:48:44 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD47200D5F@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [24.40.55.73]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3446581724_1350713"
MIME-Version: 1.0
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 03:48:50 -0000

--B_3446581724_1350713
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

+1

On 3/19/13 1:13 PM, "Suresh Krishnan" <suresh.krishnan@ericsson.com> wrote:

>Hi all,
>  This draft was presented during the softwire WG meeting at IETF86 and
>a subsequent poll of the room indicated that there was strong support
>for adopting this draft as a WG document.
>
>This call is being initiated to confirm whether there is WG consensus
>towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
>softwire WG draft. Please state whether or not you're in favor of the
>adoption by replying to this email. If you are not in favor, please also
>state your objections in your response. This adoption call will complete
>on 2013-04-02.
>
>Regards
>Suresh & Yong
>_______________________________________________
>Softwires mailing list
>Softwires@ietf.org
>https://www.ietf.org/mailman/listinfo/softwires

--B_3446581724_1350713
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFKqW
qKjpNfM+5QAwWFz/bXMwUcTBMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEzMDMyMDAzNDg0M1owDQYJKoZIhvcNAQEBBQAEggEAINHTB5sPKt/M1eHbWwHQ
YFf2Cd26dYRDptzpXIVUvvtjUEa8E3k9X3CcCWPLX6hNxCJs0FqcYfi0KJUkyri4dOQ81ZKL
xzDRShW1qnfIe9+Xi4cjkKJkqVxBjKMHJp7/tcksbmU9XYJKoxWh7C/rmy/OWaDKKHVSyozC
KTvxXn3al4OofxciPau1dtpj0dmXjdCFWYOtMlOoQTKKZpbYhQ0biukK5R/z34LSPxL+QiMB
K/agRV5LbYX6IAbR08HWmxvFQLjGlh3HI/6cNApXqB82pJmR3V38+Qfwxbok3x5jqzLrcS1d
DMTVjdzA/Tj2Ijl5eYeisMiD1ARXDp+jsw==

--B_3446581724_1350713--

From sumanshailesh@gmail.com  Tue Mar 19 23:39:38 2013
Return-Path: <sumanshailesh@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 3E1E821F8E16 for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 23:39:38 -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, HTML_MESSAGE=0.001, 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 RWHATc5z+XdY for <softwires@ietfa.amsl.com>; Tue, 19 Mar 2013 23:39:37 -0700 (PDT)
Received: from mail-vb0-x231.google.com (mail-vb0-x231.google.com [IPv6:2607:f8b0:400c:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 0466D21F8D7A for <softwires@ietf.org>; Tue, 19 Mar 2013 23:39:36 -0700 (PDT)
Received: by mail-vb0-f49.google.com with SMTP id s24so878083vbi.22 for <softwires@ietf.org>; Tue, 19 Mar 2013 23:39:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=bo579uyER2kYpQFQ8sTCl66nXqT6/NE/B1QBWgz6jPk=; b=ODKgKTelu2Pk9jzmmx0npmIAzsgVeZMKAT8NdeWInLgkz8xar5ickdrRNsKOoJUhyE hQToAiTykadZpTHb6P3QmzH6vL/PKo8BDF8eQVUbXmf8yTJYyHbZiJBAeJXjw5c6fxrM XtFMphJ3dXST4j3cGLTJrv6nj58v9N3iSEiWk9gPWBH2XsPx4ONRDlTsiEucTi5TNEBk W1wbxPi7HYYuOZtwuimdPogrxCqk/s7HD/nGi2hpBoXyCTpyI1kwafM4JNYuv+kfXjvo NKMyvX9/FaBTn+GOnssbuPbYVCc3HWKx2vOnD1SN+nqXIHFjz9W1FRebroIvHoJTcMNu hgpQ==
MIME-Version: 1.0
X-Received: by 10.220.176.73 with SMTP id bd9mr6356286vcb.63.1363761576396; Tue, 19 Mar 2013 23:39:36 -0700 (PDT)
Received: by 10.59.3.197 with HTTP; Tue, 19 Mar 2013 23:39:36 -0700 (PDT)
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD47200D5F@PACDCEXMB05.cable.comcast.com>
References: <51489CBC.4050508@ericsson.com> <E3FAB1F4F41F3A45B287E8D9C53522FD47200D5F@PACDCEXMB05.cable.comcast.com>
Date: Wed, 20 Mar 2013 12:09:36 +0530
Message-ID: <CAAiZvaDo0wgm1xbkE1PX79ZYJoB1_sRJVLCj5iuvXzwGkFiW2A@mail.gmail.com>
From: Shailesh Suman <sumanshailesh@gmail.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c1baa851cf4e04d8557c4f
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 06:39:38 -0000

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

Hi all,

   +1 support. This Lw4o6 is considered useful for unicast traffic
transition solution.

In addition, I think we should also address Multicast transition solution
(MLDv2<->IGMPv3 and Multicast-v6<->Multicast-v4 in WG.

Regards..
-Shailesh


On Wed, Mar 20, 2013 at 9:18 AM, Lee, Yiu <Yiu_Lee@cable.comcast.com> wrote:

> +1
>
> On 3/19/13 1:13 PM, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
> wrote:
>
> >Hi all,
> >  This draft was presented during the softwire WG meeting at IETF86 and
> >a subsequent poll of the room indicated that there was strong support
> >for adopting this draft as a WG document.
> >
> >This call is being initiated to confirm whether there is WG consensus
> >towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
> >softwire WG draft. Please state whether or not you're in favor of the
> >adoption by replying to this email. If you are not in favor, please also
> >state your objections in your response. This adoption call will complete
> >on 2013-04-02.
> >
> >Regards
> >Suresh & Yong
> >_______________________________________________
> >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
>
>

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

<div dir=3D"ltr"><div><div><div>Hi all,<br><br></div>=A0=A0 +1 support. Thi=
s Lw4o6 is considered useful for unicast traffic transition solution.<br><b=
r></div><div>In addition, I think we should also address Multicast transiti=
on solution (MLDv2&lt;-&gt;IGMPv3 and Multicast-v6&lt;-&gt;Multicast-v4 in =
WG. <br>
</div><div><br></div>Regards..<br></div>-Shailesh<br></div><div class=3D"gm=
ail_extra"><br><br><div class=3D"gmail_quote">On Wed, Mar 20, 2013 at 9:18 =
AM, Lee, Yiu <span dir=3D"ltr">&lt;<a href=3D"mailto:Yiu_Lee@cable.comcast.=
com" target=3D"_blank">Yiu_Lee@cable.comcast.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">+1<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 3/19/13 1:13 PM, &quot;Suresh Krishnan&quot; &lt;<a href=3D"mailto:sures=
h.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a>&gt; wrote:<br>
<br>
&gt;Hi all,<br>
&gt; =A0This draft was presented during the softwire WG meeting at IETF86 a=
nd<br>
&gt;a subsequent poll of the room indicated that there was strong support<b=
r>
&gt;for adopting this draft as a WG document.<br>
&gt;<br>
&gt;This call is being initiated to confirm whether there is WG consensus<b=
r>
&gt;towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a<br=
>
&gt;softwire WG draft. Please state whether or not you&#39;re in favor of t=
he<br>
&gt;adoption by replying to this email. If you are not in favor, please als=
o<br>
&gt;state your objections in your response. This adoption call will complet=
e<br>
&gt;on 2013-04-02.<br>
&gt;<br>
&gt;Regards<br>
&gt;Suresh &amp; Yong<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" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/softwires</a><br>
</div></div><br>_______________________________________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/softwires</a><br>
<br></blockquote></div><br></div>

--001a11c1baa851cf4e04d8557c4f--

From Olaf.Bonness@telekom.de  Wed Mar 20 03:12:47 2013
Return-Path: <Olaf.Bonness@telekom.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 428B521F8AC8 for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 03:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 i7TEa7tZS1Zq for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 03:12:46 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id 281FB21F8AC2 for <softwires@ietf.org>; Wed, 20 Mar 2013 03:12:45 -0700 (PDT)
Received: from he113414.emea1.cds.t-internal.com ([10.125.65.80]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 11:12:44 +0100
Received: from HE113605.emea1.cds.t-internal.com ([169.254.1.201]) by HE113414.emea1.cds.t-internal.com ([2002:7cd:4150::7cd:4150]) with mapi; Wed, 20 Mar 2013 11:12:43 +0100
From: <Olaf.Bonness@telekom.de>
To: <softwires@ietf.org>
Date: Wed, 20 Mar 2013 11:12:42 +0100
Thread-Topic: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
Thread-Index: Ac4kxXNBgzO42hv0TXy14rQHad29gwAjc8vQ
Message-ID: <FFD91DE61362694C94B174BB03CFDCDDEDC8A005AA@HE113605.emea1.cds.t-internal.com>
References: <51489CBC.4050508@ericsson.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 10:12:47 -0000

+1 support for adopting as WG item. Very useful work and already in good sh=
ape.

-----Urspr=FCngliche Nachricht-----
Von: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] Im Auft=
rag von Suresh Krishnan
Gesendet: Dienstag, 19. M=E4rz 2013 18:14
An: Softwires WG
Betreff: [Softwires] Call for confirming the adoption of draft-cui-softwire=
-b4-translated-ds-lite-11 as WG item

Hi all,
  This draft was presented during the softwire WG meeting at IETF86 and a s=
ubsequent poll of the room indicated that there was strong support for adop=
ting this draft as a WG document.

This call is being initiated to confirm whether there is WG consensus towar=
ds adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a softwire WG=
 draft. Please state whether or not you're in favor of the adoption by repl=
ying to this email. If you are not in favor, please also state your objecti=
ons in your response. This adoption call will complete on 2013-04-02.

Regards
Suresh & Yong
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

From Branimir.Rajtar@t.ht.hr  Wed Mar 20 04:06:02 2013
Return-Path: <Branimir.Rajtar@t.ht.hr>
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 14EA321F8733 for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 04:06:02 -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 3MqVSSMyVA3M for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 04:06:01 -0700 (PDT)
Received: from mx01.t.ht.hr (mx01.t.ht.hr [195.29.161.88]) by ietfa.amsl.com (Postfix) with SMTP id 82FEA21F874E for <softwires@ietf.org>; Wed, 20 Mar 2013 04:06:00 -0700 (PDT)
Received: from no.name.available by mx01.t.ht.hr via smtpd (for mail.ietf.org [12.22.58.30]) with ESMTP; Wed, 20 Mar 2013 11:33:54 +0100
Received: from (unknown [172.17.66.76]) by scmg1.t.ht.hr with smtp id 5b40_83c6_23d9c3c6_914e_11e2_821c_00221951415f; Wed, 20 Mar 2013 12:05:56 +0100
Received: (private information removed) Wed, 20 Mar 2013 12:05:57 +0100
Received: (private information removed) S2010EXCHCA2.ad.local ([::1]) with mapi id 14.02.0328.009; Wed, 20 Mar 2013 12:05:56 +0100
From: Branimir Rajtar <Branimir.Rajtar@t.ht.hr>
To: "Olaf.Bonness@telekom.de" <Olaf.Bonness@telekom.de>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
Thread-Index: Ac4kxXNBgzO42hv0TXy14rQHad29gwAjc8vQAAHjl/A=
Date: Wed, 20 Mar 2013 11:05:56 +0000
Message-ID: <786F13AA11E69F4DB2CCA23F7400C2FB014156F5@S2010EXCH1.ad.local>
References: <51489CBC.4050508@ericsson.com> <FFD91DE61362694C94B174BB03CFDCDDEDC8A005AA@HE113605.emea1.cds.t-internal.com>
In-Reply-To: <FFD91DE61362694C94B174BB03CFDCDDEDC8A005AA@HE113605.emea1.cds.t-internal.com>
Accept-Language: en-US, hr-HR
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.5.13]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Mar 2013 11:05:57.0061 (UTC) FILETIME=[E5A82750:01CE255A]
X-NAIMIME-Disclaimer: 1
X-NAIMIME-Modified: 1
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 11:06:02 -0000

KzEgYXMgd2VsbAoKQlIsCkJyYW5pbWlyCgoKLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KRnJv
bTogc29mdHdpcmVzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpzb2Z0d2lyZXMtYm91bmNlc0Bp
ZXRmLm9yZ10gT24gQmVoYWxmIE9mIE9sYWYuQm9ubmVzc0B0ZWxla29tLmRlClNlbnQ6IFdlZG5l
c2RheSwgTWFyY2ggMjAsIDIwMTMgMTE6MTMgQU0KVG86IHNvZnR3aXJlc0BpZXRmLm9yZwpTdWJq
ZWN0OiBSZTogW1NvZnR3aXJlc10gQ2FsbCBmb3IgY29uZmlybWluZyB0aGUgYWRvcHRpb24gb2Yg
ZHJhZnQtY3VpLXNvZnR3aXJlLWI0LXRyYW5zbGF0ZWQtZHMtbGl0ZS0xMSBhcyBXRyBpdGVtCgor
MSBzdXBwb3J0IGZvciBhZG9wdGluZyBhcyBXRyBpdGVtLiBWZXJ5IHVzZWZ1bCB3b3JrIGFuZCBh
bHJlYWR5IGluIGdvb2Qgc2hhcGUuCgotLS0tLVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0t
ClZvbjogc29mdHdpcmVzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpzb2Z0d2lyZXMtYm91bmNl
c0BpZXRmLm9yZ10gSW0gQXVmdHJhZyB2b24gU3VyZXNoIEtyaXNobmFuCkdlc2VuZGV0OiBEaWVu
c3RhZywgMTkuIE3DpHJ6IDIwMTMgMTg6MTQKQW46IFNvZnR3aXJlcyBXRwpCZXRyZWZmOiBbU29m
dHdpcmVzXSBDYWxsIGZvciBjb25maXJtaW5nIHRoZSBhZG9wdGlvbiBvZiBkcmFmdC1jdWktc29m
dHdpcmUtYjQtdHJhbnNsYXRlZC1kcy1saXRlLTExIGFzIFdHIGl0ZW0KCkhpIGFsbCwKICBUaGlz
IGRyYWZ0IHdhcyBwcmVzZW50ZWQgZHVyaW5nIHRoZSBzb2Z0d2lyZSBXRyBtZWV0aW5nIGF0IElF
VEY4NiBhbmQgYSBzdWJzZXF1ZW50IHBvbGwgb2YgdGhlIHJvb20gaW5kaWNhdGVkIHRoYXQgdGhl
cmUgd2FzIHN0cm9uZyBzdXBwb3J0IGZvciBhZG9wdGluZyB0aGlzIGRyYWZ0IGFzIGEgV0cgZG9j
dW1lbnQuCgpUaGlzIGNhbGwgaXMgYmVpbmcgaW5pdGlhdGVkIHRvIGNvbmZpcm0gd2hldGhlciB0
aGVyZSBpcyBXRyBjb25zZW5zdXMgdG93YXJkcyBhZG9wdGlvbiBvZiBkcmFmdC1jdWktc29mdHdp
cmUtYjQtdHJhbnNsYXRlZC1kcy1saXRlLTExIGFzIGEgc29mdHdpcmUgV0cgZHJhZnQuIFBsZWFz
ZSBzdGF0ZSB3aGV0aGVyIG9yIG5vdCB5b3UncmUgaW4gZmF2b3Igb2YgdGhlIGFkb3B0aW9uIGJ5
IHJlcGx5aW5nIHRvIHRoaXMgZW1haWwuIElmIHlvdSBhcmUgbm90IGluIGZhdm9yLCBwbGVhc2Ug
YWxzbyBzdGF0ZSB5b3VyIG9iamVjdGlvbnMgaW4geW91ciByZXNwb25zZS4gVGhpcyBhZG9wdGlv
biBjYWxsIHdpbGwgY29tcGxldGUgb24gMjAxMy0wNC0wMi4KClJlZ2FyZHMKU3VyZXNoICYgWW9u
ZwpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTb2Z0d2ly
ZXMgbWFpbGluZyBsaXN0ClNvZnR3aXJlc0BpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3NvZnR3aXJlcwpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwpTb2Z0d2lyZXMgbWFpbGluZyBsaXN0ClNvZnR3aXJlc0BpZXRmLm9y
ZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NvZnR3aXJlcwoKCjxIVE1M
PjxQPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9Izk5OTk5OSBzaXplPTE+DQoNCklaSkFWQSBPIE9E
UklDQU5KVSBPREdPVk9STk9TVEk6IFNhZHLFvmFqIG92ZSBwb3J1a2UgaSBldmVudHVhbG5vIHBy
aWxvxb5lbmloIGRhdG90ZWthIGplIHBvdmplcmxqaXYgaSBuYW1pamVuamVuIGplIHNhbW8gb3Nv
YmFtYSBpbGkgc3ViamVrdGltYSBrb2ppIHN1IG5hdmVkZW5pIHUgYWRyZXNpLiBVa29saWtvIHN0
ZSBwcmltaWxpIG92dSBwb3J1a3UgZ3JlxaFrb20sIG1vbGltbyBWYXMsIG9iYXZpamVzdGl0ZSBw
b8WhaWxqYXRlbGphLCBhIHBvcnVrdSBpIHN2ZSBuamVuZSBwcml2aXRrZSBvZG1haCwgYmV6IMSN
aXRhbmphLCB0cmFqbm8gdWtsb25pdGUgcyByYcSNdW5hbGEuIEJpbG8ga2Frdm8gcHJlbm/FoWVu
amUsIGtvcGlyYW5qZSBpbGkgZGlzdHJpYnVjaWphIGluZm9ybWFjaWphIHNhZHLFvmFuaWggdSBw
b3J1Y2kgdHJlxIdpbSBvc29iYW1hIGplIHphYnJhbmplbm8gaSBtb8W+ZSBiaXRpIHpha29uc2tp
IGthxb5uaml2by4gU2FkcsW+YWosIHN0YXZvdmkgaSBtacWhbGplbmphIGl6bmVzZW5pIHUgcG9y
dWNpIHN1IGF1dG9yb3ZpIGkgbmUgcHJlZHN0YXZsamFqdSBudcW+bm8gc3Rhdm92ZSBIVCAtIEhy
dmF0c2tpaCB0ZWxla29tdW5pa2FjaWphIGQuZC4gSFQgbmUgcHJpaHZhxIdhIG5pa2FrdnUgb2Rn
b3Zvcm5vc3QgemEgZXZlbnR1YWxudSDFoXRldHUgbmFzdGFsdSBwcmltaXRrb20gb3ZlIHBvcnVr
ZSBpIHByaWxvZ2Egc2FkcsW+YW5paCB1IHBvcnVjaS4NCg0KPC9GT05UPjwvUD48UD48Rk9OVCBm
YWNlPUFyaWFsIGNvbG9yPSM5OTk5OTkgc2l6ZT0xPg0KDQogRElTQ0xBSU1FUjpUaGUgY29udGVu
dHMgb2YgdGhpcyBlbWFpbCBhcyB3ZWxsIGFzIGFueSBmaWxlcyBhdHRhY2hlZCB0byBpdCBhcmUg
Y29uZmlkZW50aWFsIGFuZCBpbnRlbmRlZCBzb2xlbHkgZm9yIGluZGl2aWR1YWxzIG9yIGVudGl0
aWVzIHdoaWNoIHRoZXkgYXJlIGFkZHJlc3NlZCB0by4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhp
cyBlbWFpbCBtZXNzYWdlIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIHBl
cm1hbmVudGx5IHJlbW92ZSB0aGUgbWVzc2FnZSBhbmQgYWxsIGF0dGFjaGVkIGZpbGVzIGZyb20g
dGhlIGNvbXB1dGVyLiBBbnkgZGlzY2xvc3VyZSwgY29weWluZyBvciBkaXN0cmlidXRpb24gb2Yg
YWxsIG9yIGEgcGFydCBvZiBpbmZvcm1hdGlvbiBjb250YWluZWQgaGVyZWluIHRvIG9yIGJ5IHRo
aXJkIHBhcnRpZXMgaXMgcHJvaGliaXRlZCBhbmQgbWF5IGJlIHVubGF3ZnVsLiBQbGVhc2Ugbm90
ZSB0aGF0IGFueSB2aWV3cyBvciBvcGluaW9ucyBwcmVzZW50ZWQgaW4gdGhpcyBtZXNzYWdlIGFy
ZSBzb2xlbHkgdGhvc2Ugb2YgdGhlIGF1dGhvciBhbmQgZG8gbm90IG5lY2Vzc2FyaWx5IHJlcHJl
c2VudCB0aGUgdmlld3MgYW5kIG9waW5pb25zIG9mIENyb2F0aWFuIFRlbGVjb20gSW5jLiBDcm9h
dGlhbiBUZWxlY29tIEluYy4gYWNjZXB0cyBubyBsaWFiaWxpdHkgZm9yIGFueSBwb3RlbnRpYWwg
ZGFtYWdlIGNhdXNlZCBieSB0aGlzIG1lc3NhZ2UgYW5kIGZpbGVzIGF0dGFjaGVkIHRvIGl0Lg0K
DQo8L0ZPTlQ+PC9QPjwvSFRNTD4K

From ales.vizdal@t-mobile.cz  Wed Mar 20 04:07:31 2013
Return-Path: <ales.vizdal@t-mobile.cz>
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 920E621F8735 for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 04:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.95
X-Spam-Level: 
X-Spam-Status: No, score=-1.95 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, 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 WxioZMOys8+b for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 04:07:31 -0700 (PDT)
Received: from mailhub1.t-mobile.cz (mailhub1.t-mobile.cz [62.141.0.149]) by ietfa.amsl.com (Postfix) with ESMTP id E159F21F8733 for <softwires@ietf.org>; Wed, 20 Mar 2013 04:07:30 -0700 (PDT)
Received: from srvhk504.rdm.cz (unknown [10.254.92.81]) by mailhub1.t-mobile.cz (Postfix) with ESMTP id C0637285809; Wed, 20 Mar 2013 12:07:29 +0100 (CET)
Received: from SRVHKE02.rdm.cz ([fe80::2cec:9ace:94f2:601a]) by srvhk504.rdm.cz ([fe80::506:b9a6:d353:9494%12]) with mapi; Wed, 20 Mar 2013 12:07:29 +0100
From: =?iso-8859-2?Q?V=EDzdal_Ale=B9?= <ales.vizdal@t-mobile.cz>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Softwires WG <softwires@ietf.org>
Date: Wed, 20 Mar 2013 12:06:44 +0100
Thread-Topic: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
Thread-Index: Ac4kxXIIMCOAnwZ3Rvm1G0V8fzQWSwAlWBKA
Message-ID: <1808340F7EC362469DDFFB112B37E2FCC74B5849B3@SRVHKE02.rdm.cz>
References: <51489CBC.4050508@ericsson.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forwarded
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 11:07:31 -0000

I support adoption of this document.

> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On B=
ehalf Of
> Suresh Krishnan
> Sent: Tuesday, March 19, 2013 6:14 PM
> To: Softwires WG
> Subject: [Softwires] Call for confirming the adoption of draft-cui-softwi=
re-b4-
> translated-ds-lite-11 as WG item
>=20
> Hi all,
>   This draft was presented during the softwire WG meeting at IETF86 and
> a subsequent poll of the room indicated that there was strong support
> for adopting this draft as a WG document.
>=20
> This call is being initiated to confirm whether there is WG consensus
> towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
> softwire WG draft. Please state whether or not you're in favor of the
> adoption by replying to this email. If you are not in favor, please also
> state your objections in your response. This adoption call will complete
> on 2013-04-02.
>=20
> Regards
> Suresh & Yong
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From sunqi.thu7@gmail.com  Wed Mar 20 08:16:07 2013
Return-Path: <sunqi.thu7@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 1B23C21F8839 for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 08:16:07 -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 Fp7d-hqH1kRV for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 08:16:06 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id A80DF21F8825 for <softwires@ietf.org>; Wed, 20 Mar 2013 08:16:06 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id w10so649323pde.17 for <softwires@ietf.org>; Wed, 20 Mar 2013 08:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=ViB9g06gPMmt8aP17+G1XHTpIr4xL7V2ilL5iKzWrRw=; b=NWglPaoHHV9WAy0hfJDPRGBbRjdcuZbB2xK1vtPRhnrpxsSwclmZZVAz8g9uvQzgjN y7qoFrmGDjAWMCack6YgrOlY+2OYKx6A84tsJXYD1sryAvIaOBxNTCWQge4MB9YyjQft c0mLfAl2Ldt3e3tCVPUasOt0IST7yfZOjPIifcS/K42+OCCn0WFDqZhu9D0h9LLi8WFj qg60TtW2I6ryA+uXnYcOHeOwu2ZQh2CnYdt62S1jdgCJ4yqh5tXbw/UkcLWIRRwWrF0U MHFZCa7YHHtV78xzgdfAbhmtNpvig3aqKLdGWJJSKhTOQpwhZyChvk8Ot9q6FUW58Yow UEHA==
X-Received: by 10.68.83.38 with SMTP id n6mr9540351pby.28.1363792566470; Wed, 20 Mar 2013 08:16:06 -0700 (PDT)
Received: from [192.168.0.106] ([114.255.40.13]) by mx.google.com with ESMTPS id i9sm2612943paa.7.2013.03.20.08.16.03 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Mar 2013 08:16:05 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=utf-8
From: Qi Sun <sunqi.thu7@gmail.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Date: Wed, 20 Mar 2013 23:15:59 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B073587-A13C-4C5C-A7D0-4CE743F04D82@gmail.com>
References: <51489CBC.4050508@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 20 Mar 2013 15:16:07 -0000

+1 support.

Qi

On 2013-3-20, at =E4=B8=8A=E5=8D=881:13, Suresh Krishnan wrote:

> Hi all,
>  This draft was presented during the softwire WG meeting at IETF86 and
> a subsequent poll of the room indicated that there was strong support
> for adopting this draft as a WG document.
>=20
> This call is being initiated to confirm whether there is WG consensus
> towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
> softwire WG draft. Please state whether or not you're in favor of the
> adoption by replying to this email. If you are not in favor, please =
also
> state your objections in your response. This adoption call will =
complete
> on 2013-04-02.
>=20
> Regards
> Suresh & Yong
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From eleven.fuyu@huawei.com  Wed Mar 20 17:48:15 2013
Return-Path: <eleven.fuyu@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 855AA11E8115 for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 17:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMWSHHBqQo+K for <softwires@ietfa.amsl.com>; Wed, 20 Mar 2013 17:48:14 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A6AEB11E8110 for <softwires@ietf.org>; Wed, 20 Mar 2013 17:48:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQX86011; Thu, 21 Mar 2013 00:48:12 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 21 Mar 2013 00:47:12 +0000
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 21 Mar 2013 00:48:10 +0000
Received: from NKGEML505-MBX.china.huawei.com ([169.254.1.98]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Thu, 21 Mar 2013 08:48:03 +0800
From: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Softwires WG <softwires@ietf.org>
Thread-Topic: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
Thread-Index: AQHOJMVyWFUnScGj3EW/Hd4EsYUv55ivUZ0Q
Date: Thu, 21 Mar 2013 00:48:02 +0000
Message-ID: <EF6A204047BD994A860EE26D5F23BF58403CD272@nkgeml505-mbx.china.huawei.com>
References: <51489CBC.4050508@ericsson.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.137]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 21 Mar 2013 00:48:15 -0000

+1 support for adoption this work as WG item

Cheers
Yu

-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On Beh=
alf Of Suresh Krishnan
Sent: Wednesday, March 20, 2013 1:14 AM
To: Softwires WG
Subject: [Softwires] Call for confirming the adoption of draft-cui-softwire=
-b4-translated-ds-lite-11 as WG item

Hi all,
  This draft was presented during the softwire WG meeting at IETF86 and
a subsequent poll of the room indicated that there was strong support
for adopting this draft as a WG document.

This call is being initiated to confirm whether there is WG consensus
towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
softwire WG draft. Please state whether or not you're in favor of the
adoption by replying to this email. If you are not in favor, please also
state your objections in your response. This adoption call will complete
on 2013-04-02.

Regards
Suresh & Yong
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

From ot@cisco.com  Thu Mar 21 01:22:49 2013
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 1EF0A21F8F2F for <softwires@ietfa.amsl.com>; Thu, 21 Mar 2013 01:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.524
X-Spam-Level: 
X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 HRJspcAs8pDd for <softwires@ietfa.amsl.com>; Thu, 21 Mar 2013 01:22:44 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB0321F8F35 for <softwires@ietf.org>; Thu, 21 Mar 2013 01:22:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=758; q=dns/txt; s=iport; t=1363854163; x=1365063763; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=5+zAnZX9i5BDNQY/oOtMFtSUgjCDh6jnEVLeUOxJAlE=; b=G1MSKwI7OgQhFLRWxbYM+AtL3L/1hsbqR2v6AxWJFuO8QOWNUgIM2vSz yg+GffOE4uduLyCV516f27kEs6HyT9VYg6uvQ2x0GpIFs7gwWdle6So+s MpWQINXBedPCAmsKyH6pPVqeTUyFZtjJq/Rw1WLxNCpijJAZMRcU2tXtc Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHnBSlGQ/khM/2dsb2JhbABExTeBWBZ0giQBAQEDAR0dPwULCzsLVwaIIQbCY41QgUAHgl9hA5ZgkQKBVIE3O4E3
X-IronPort-AV: E=Sophos;i="4.84,884,1355097600"; d="scan'208";a="152028704"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 21 Mar 2013 08:22:41 +0000
Received: from dhcp-10-61-96-130.cisco.com (dhcp-10-61-96-130.cisco.com [10.61.96.130]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2L8MgwH002314 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 21 Mar 2013 08:22:42 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ole Troan <ot@cisco.com>
In-Reply-To: <51489CBC.4050508@ericsson.com>
Date: Thu, 21 Mar 2013 09:22:42 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <F6F3D633-E910-4442-8CF9-9DF12C6905FA@cisco.com>
References: <51489CBC.4050508@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1499)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Call for confirming the adoption of draft-cui-softwire-b4-translated-ds-lite-11 as WG item
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, 21 Mar 2013 08:22:49 -0000

Suresh,

>  This draft was presented during the softwire WG meeting at IETF86 and
> a subsequent poll of the room indicated that there was strong support
> for adopting this draft as a WG document.
> 
> This call is being initiated to confirm whether there is WG consensus
> towards adoption of draft-cui-softwire-b4-translated-ds-lite-11 as a
> softwire WG draft. Please state whether or not you're in favor of the
> adoption by replying to this email. If you are not in favor, please also
> state your objections in your response. This adoption call will complete
> on 2013-04-02.

I support adoption of this draft on the condition that it by default uses
the MAP port mapping algorithm, and the same provisioning mechanism.

cheers,
Ole

From bingxuere@gmail.com  Thu Mar 21 23:47:45 2013
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 6F37111E80AE for <softwires@ietfa.amsl.com>; Thu, 21 Mar 2013 23:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.201
X-Spam-Level: 
X-Spam-Status: No, score=-1.201 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, NORMAL_HTTP_TO_IP=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 D+wwwt4Y5qa7 for <softwires@ietfa.amsl.com>; Thu, 21 Mar 2013 23:47:44 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id ECAA711E809C for <softwires@ietf.org>; Thu, 21 Mar 2013 23:47:43 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id q10so1447614pdj.40 for <softwires@ietf.org>; Thu, 21 Mar 2013 23:47:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=iRCJxgKRhgUuiFlpJjPgu202yg5cRMwqcqK6vLdRvhw=; b=d/4yiB/y957lV6Lq04n7atmJZ2GESrR5Kt3/om+2B+RlxkUfHkQhG592x9NqJOF4xq ITYnFHexrftRQMHvZYXIOHrcdVceCpWm8OouP+X5IUOmj6Z3pAY3wUbWtU4zp25YBSrR EhI9KONsemm8QH96PaJz/ATr0UbMXHb1tPTtHeakhUZ6blzVTwTh+4jYJhQ6d1PjKnZZ 03c6gkTwZv60f50meZ5aojZkhm09G4k7Gk2qCahylo9xxqFv9pEaCj/iHINTg+fG9MuS kj0X8ncaJMKHvZwMCTTW+snzqMgFcRCOfsfGKc8BnjrLAnV6MtclGN3M7Wj2q0GU62OK yaoA==
X-Received: by 10.68.37.6 with SMTP id u6mr974464pbj.78.1363934863650; Thu, 21 Mar 2013 23:47:43 -0700 (PDT)
Received: from [10.9.53.118] ([219.142.69.77]) by mx.google.com with ESMTPS id m18sm1772591pad.17.2013.03.21.23.47.37 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Mar 2013 23:47:42 -0700 (PDT)
References: <7921F977B17D5B49B8DCC955A339D2F02AA8F562@US70UWXCHMBA06.zam.alcatel-lucent.com> <CAFUBMqVSdpgwEzs9sjG9NJMKTnEi+yursJLMg1WYmezePJwZFw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAFUBMqVSdpgwEzs9sjG9NJMKTnEi+yursJLMg1WYmezePJwZFw@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-A6012CC3-34B7-4A57-A4B9-65989788B602
Content-Transfer-Encoding: 7bit
Message-Id: <DA1265E7-4581-4DA7-921E-45A58BCFB56B@gmail.com>
X-Mailer: iPad Mail (10A8500)
From: "bingxuere@gmail.com" <bingxuere@gmail.com>
Date: Fri, 22 Mar 2013 14:47:33 +0800
To: Maoke <fibrib@gmail.com>
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] map-deployment-01 draft
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, 22 Mar 2013 06:47:45 -0000

--Apple-Mail-A6012CC3-34B7-4A57-A4B9-65989788B602
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Maoke, Kristian,

Thanks for your comments! I totally agree with you that we should add an exa=
mple for step-by-step guideline. Please see some further comments inline.

On 2013-3-16, at 8:45, Maoke <fibrib@gmail.com> wrote:

> hi Kristian,
> =20
> thanks a lot for the comments! i totally agree with you that there should b=
e a comprehensive example for the step-by-step guideline. (i remember that w=
e put such an example in early sketch but later some said it might not neces=
sary. :P) i would like to ask the wg (and other authors) for the consensus o=
f adding the example into the draft.=20
> 2013/3/16 Poscic, Kristian (Kristian) <kristian.poscic@alcatel-lucent.com>=

>> =20
>>=20
>> I was able to follow section 5.1 of this draft somewhat but then got comp=
letely lost at step B3.
>>=20
>> It would really help if you can also describe the reason why are you perf=
orming each step =E2=80=93 in other words put more context around it. Otherw=
ise, it will be very hard for the operators to follow this.
>>=20
>> =20
>>=20
>> Maybe we can start from a more comprehensive example and you can include i=
t the draft along with your steps.
>>=20
>> Here is my example and logic that I follow:
>>=20
>> =20
>>=20
>> 1)      Example requirement:
>>=20
>> -          There are about 22,000 residual IPv4 addresses that needs to b=
e translated via MAP.
>>=20
>> -          Each  such address should have 4K ports available. Therefore, t=
he IP address sharing ratio is 16:1
>>=20
>> -          The public IPv4 addresses that are available to the operator f=
or this translation are four  /24 subnets (11.11.11.0/24 , 12.12.12..0/24, 1=
3.13.13.0/24 and 14.14.14.0/24)  and one /22 subnet (15.15.0.0/22).
>>=20
>> -          The IPv6 prefix that is delegated to the operator is 2001:db8:=
:/32 .
>>=20
>> -          4K users (or CPEs corresponding to the residual IP addresses) w=
ill get PD /56, the rest of the users will get PD /60.
>>=20
>> -          The end-user-prefix and the rules will be delegated via DHCPv6=
 server =20
>>=20
> =20
>  i like this start of example! some further considerations sould be includ=
ed (as the example for the remarks)=20
> =20
> #1 the public IPv4 addresses might be quite bad aggregated;
I agree we should take this feature into consideration. However, in this cas=
e, as the number of mapping rules will increase accordingly, more careful co=
nsiderations should be taken on MAP domain planning and rule planning. I thi=
nk it might be useful to give a recommended maximum number of rules for whic=
h a domain would have, especially for mesh mode.
> #2 the IPv6 common prefix for the MAP deployment might be not exist -- MAP=
 can be deployed cross autonomous systems where delegated prefices are not a=
ggregateable at all. (this is a typical case where 1:1 mode is needed)
For EA bit =3D 0 case, we already have some text on section 5.2. Are you sug=
gesting to improve this paragraph by explaining more clearly about the scena=
rio requirement?
> #3 DHCPv6 is not the only way for the provisioning, and at least manual co=
nfiguraton MUST be supported. therefore we cannot put anything that needs DH=
CPv6 as prerequisite for deployment and implementation.
Agree. For DHCP based solution, as the finally conclusion has not come out y=
et, I think we should wait for dhc's decision and also be consistent with un=
ified CPE draft for provisioning.=20

Thoughts ?

Best wishes
Qigong
>> =20
>>=20
>> =20
>>=20
>> 22,000 residual IP addresses in 16:1 sharing scenario could be covered wi=
th two /24 subnets and one /22 subnet  =3D> (2 * 2^8 * 16 + 2^10 * 16 =3D 24=
, 576).
>>=20
>> =20
>>=20
>> So Rule IPv4 prefix and EA bits length  will be:
>>=20
>> =20
>>=20
>> 1)      11.11.11.0/24    EA length: 12 bits  (8 bits for the IPv4 suffix a=
nd 4 bits for PSID)    =3D> these users will get PD /56 (arbitrarily determi=
ned by the operator and in conformance with the requirement)
>>=20
>> 2)      12.12.12.0/24    EA length: 12 bits                              =
                                                                =3D> these u=
sers will get PD /60 (arbitrarily determined by the operator and in conforma=
nce with the requirement)
>>=20
>> 3)      15.15.0.0/22      EA length: 14 bits  (10 bits for IPv4 suffix an=
d 4 bits for PSID)          =3D> these users will get PD/60 (arbitrarily det=
ermined by the operator and in conformance with the requirement)
>>=20
>> =20
>>=20
>> That was the easy part. What we need to do now is to determine:
>>=20
>> -          Rule IPv6 Prefix  (to complete BMR/FMR)
>>=20
>> -          How will the end user DHCPv6 prefix (PD) be carved out by DHCP=
 server (assumption is that DHCPv6 server delegates v6 prefix and Rules).
>>=20
>> =20
>>=20
>> We will represents the bits in v6 address via the following graph (we wil=
l ignore irrelevant parts of the v6 addresses for this discussion and instea=
d consider only the bits /32 to /64):
>>=20
>> =20
>>=20
>>                 /32         /36         /40         /44         /48      =
   /52         /56         /60         /64
>>=20
>> xxxx       xxxx       xxxx       xxxx       xxxx       xxxx       xxxx   =
    xxxx       xxxx =20
>>=20
>>                                                                 | |      =
    |                              |              |
>>=20
>>                                                                 |< ------=
--EA=3D12-------->|              |                             1) this will c=
over subnet 1) ; EA bits extend from the PD length (/56) to the Rule IPv6 pr=
efix length (/44)
>>=20
>>                                                                     |    =
      |< ---------EA=3D12------ >|                              2) this will=
 cover subnet 2);  EA bits extend from the PD length (/60) to the Rule IPv6 p=
refix length (/48)
>>=20
>>                                                                     |< --=
--------------EA=3D14------ >|                               3) this will co=
ver subnet 3) ; EA bits extend from the PD length (/60) to the Rule IPv6 pre=
fix length (/46)     =20
>>=20
>> =20
>>=20
>> Now we have determined IPv6 Rule Prefix length for each of the three rule=
s that we need to create.
>>=20
>> The IPv4 Prefix Rule lengths are /44, /48 and /46 for the cases 1), 2) an=
d 3) respectively.
>>=20
>> =20
>>=20
>> Now we need to determine how can each end user prefix be uniquely allocat=
ed across all users (CEs). The only way to ensure this uniqueness is to ensu=
re that the portion of the IPv6 Rule prefix up to /44 (smallest Rule IPv6 pr=
efix length between all the rules in the MAP domain) is unique amongst all t=
he rules.
>>=20
>> So, the IPv6 Rule prefixes for our three cases will be (changing the part=
 above /44):
>>=20
>> 1)      2001:db8:0000::/44
>>=20
>> 2)      2001:db8:0010::/48
>>=20
>> 3)      2001:db8:0020::/46
>>=20
>> =20
>>=20
>> The last step is to ensure that the DHCPv6 server hands out proper end-us=
er prefixes (and along with the prefixes, the Rules are delegated as well).
>>=20
>> So the DHCPv6 can be configured so that it is carving the prefixes from t=
hree ranges:
>>=20
>> =20
>>=20
>> 1)      2001:db8:000x:xxyy::  (where x denotes carving part from /44 to /=
56 =E2=80=93 the EA bits; =E2=80=98y=E2=80=99 denotes further subneting that=
 is done on the CPE -> yy=3D00 for MAP prefix, the remaining combinations ar=
e reserved for CPE delegation to its clients)
>>=20
>> 2)      2001:db8:0100:xxxy::  (where x denotes carving part from /48 to /=
60 =E2=80=93 the EA bits; =E2=80=98y=E2=80=99 denotes further subneting that=
 is done on the CPE -> y=3D0 for MAP prefix, the remaining combinations are r=
eserved for CPE delegation to its clients)
>>=20
>> 3)      2001:db8:020w:xxxy::  (where x and two lower bits of =E2=80=98w=E2=
=80=99 denote carving part from /46 to /60 =E2=80=93 the EA bits; =E2=80=98y=
=E2=80=99 denotes further subneting that is done on the CPE -> y=3D0 for MAP=
 prefix, the remaining combinations are reserved for CPE delegation to its c=
lients)
>>=20
>> =20
>>=20
>> Along with each user end prefix a BMR and a DMR will be delegated to the e=
nd-users (so we will have a hub and spoke topology)
>>=20
>> =20
>>=20
>> Also note that to cover the holes between the /48 and /44 for case 2) we c=
an easily add 15 more /24 IPv4 prefixes by creating new IPv6 Rule by changin=
g bits between /44 and /48.
>>=20
>> Similarly for case 3), we can create 3 more IPv6 rule prefixes (and add 3=
 more /22 IPv4 subnets) by changing bits between /46 and /48. This would all=
ow us to expand the coverage for residual IPs (although the purpose of NAT i=
s to minimize their use over time not to expand J).
>>=20
> =20
> >> co-authors: we may compose the 5.1 again based on Kristian's proposed e=
xample and includes the #1 ~ #3 above and submit for wg review. agree?
> =20
> - maoke
> =20
>> =20
>>=20
>> =20
>>=20
>> =20
>>=20
>> =20
>>=20
>> =20
>>=20
>>=20
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

--Apple-Mail-A6012CC3-34B7-4A57-A4B9-65989788B602
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Hi Maoke, Kristian,</div><div><br></di=
v><div>Thanks for your comments! I totally agree with you that we should add=
 an example for step-by-step guideline. Please see some further comments inl=
ine.</div><div><br></div><div>On 2013-3-16, at 8:45, Maoke &lt;<a href=3D"ma=
ilto:fibrib@gmail.com">fibrib@gmail.com</a>&gt; wrote:<br><br></div><blockqu=
ote type=3D"cite"><div><div>hi Kristian, </div><div>&nbsp;</div><div>thanks a=
 lot for the comments!&nbsp;i totally agree with you that there should be a c=
omprehensive example for the step-by-step guideline. (i remember that we put=
 such an example in early sketch but later some said it might not necessary.=
 :P) i would like to ask the wg&nbsp;(and other authors) for the consensus o=
f adding the example into the draft. <br>
</div><div class=3D"gmail_quote">2013/3/16 Poscic, Kristian (Kristian) <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:kristian.poscic@alcatel-lucent.com" targe=
t=3D"_blank">kristian.poscic@alcatel-lucent.com</a>&gt;</span><br><blockquot=
e style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(2=
04,204,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_qu=
ote">






<div lang=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">I was able to follow section 5.1 of this draft somewh=
at but then got completely lost at step B3.
<u></u><u></u></p>
<p class=3D"MsoNormal">It would really help if you can also describe the rea=
son why are you performing each step =E2=80=93 in other words put more conte=
xt around it. Otherwise, it will be very hard for the operators to follow th=
is.<u></u><u></u></p>

<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Maybe we can start from a more comprehensive example a=
nd you can include it the draft along with your steps.
<u></u><u></u></p>
<p class=3D"MsoNormal">Here is my example and logic that I follow:<u></u><u>=
</u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p><u></u><span>1)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>Example requirement:<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fon=
t-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><u></u>There are about 22,000 residual IPv4 addresses that nee=
ds to be translated via MAP.<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fon=
t-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><u></u>Each &nbsp;such address should have 4K ports available.=
 Therefore, the IP address sharing ratio is 16:1<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fon=
t-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><u></u>The public IPv4 addresses that are available to the ope=
rator for this translation are four &nbsp;/24 subnets (<a href=3D"http://11.=
11.11.0/24" target=3D"_blank">11.11.11.0/24</a> , 12.12.12..0/24, <a href=3D=
"http://13.13.13.0/24" target=3D"_blank">13.13.13.0/24</a> and <a href=3D"ht=
tp://14.14.14.0/24" target=3D"_blank">14.14.14.0/24</a>) &nbsp;and one /22 s=
ubnet (<a href=3D"http://15.15.0.0/22" target=3D"_blank">15.15.0.0/22</a>).<=
u></u><u></u></p>

<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fon=
t-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><u></u>The IPv6 prefix that is delegated to the operator is 20=
01:db8::/32 .<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fon=
t-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><u></u>4K users (or CPEs corresponding to the residual IP addr=
esses) will get PD /56, the rest of the users will get PD /60.<u></u><u></u>=
</p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fon=
t-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><u></u>The end-user-prefix and the rules will be delegated via=
 DHCPv6 server&nbsp;&nbsp;</p></div></div></blockquote><div>&nbsp;</div><div=
>&nbsp;i like this start of example! some further considerations sould be in=
cluded (as the example for the remarks)&nbsp;</div>
<div>&nbsp;</div><div>#1 the public IPv4 addresses might be quite bad aggreg=
ated; </div></div></div></blockquote>I agree we should take this feature int=
o consideration. However, in this case, as the number of mapping rules will i=
ncrease accordingly, more careful considerations should be taken on MAP doma=
in planning and rule planning. I think it might be useful to give a recommen=
ded maximum number of rules for which a domain would have, especially for me=
sh mode.<br><blockquote type=3D"cite"><div><div class=3D"gmail_quote"><div>#=
2 the IPv6 common prefix for the MAP deployment might be not exist -- MAP ca=
n be deployed cross autonomous systems where delegated prefices are not aggr=
egateable at all. (this is a typical case where 1:1 mode is needed)</div></d=
iv></div></blockquote>For EA bit =3D 0 case, we already have some text on se=
ction 5.2. Are you suggesting to improve this paragraph by explaining more c=
learly about the scenario requirement?<br><blockquote type=3D"cite"><div><di=
v class=3D"gmail_quote">
<div>#3 DHCPv6 is not the only way for the provisioning, and at least manual=
 configuraton MUST be supported. therefore we cannot put anything that needs=
 DHCPv6 as prerequisite for deployment and implementation. </div></div></div=
></blockquote>Agree. For DHCP based solution, as the finally conclusion has n=
ot come out yet, I think we should wait for dhc's decision and also be consi=
stent with unified CPE draft for provisioning.&nbsp;<div><br></div><div>Thou=
ghts ?</div><div><br></div><div>Best wishes</div><div>Qigong<br><blockquote t=
ype=3D"cite"><div><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-le=
ft-width:1px;border-left-style:solid" class=3D"gmail_quote">
<div lang=3D"EN-US" vlink=3D"purple" link=3D"blue"><div><p style=3D"margin-l=
eft:0.75in">&nbsp;</p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">22,000 residual IP addresses in 16:1 sharing scenario=
 could be covered with two /24 subnets and one /22 subnet&nbsp; =3D&gt; (2 *=
 2^8 * 16 + 2^10 * 16 =3D 24, 576).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">So Rule IPv4 prefix and EA bits length &nbsp;will be:=
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p><u></u><span>1)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u><a href=3D"http://11.11.11.0/24" target=3D"_blank">11.1=
1.11.0/24</a>&nbsp;&nbsp;&nbsp; EA length: 12 bits&nbsp; (8 bits for the IPv=
4 suffix and 4 bits for PSID)&nbsp;&nbsp;&nbsp; =3D&gt; these users will get=
 PD /56 (arbitrarily determined by the operator and in conformance with the r=
equirement)<u></u><u></u></p>

<p><u></u><span>2)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u><a href=3D"http://12.12.12.0/24" target=3D"_blank">12.1=
2.12.0/24</a>&nbsp; &nbsp;&nbsp;EA length: 12 bits&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =3D&gt; these users will get PD /60 (arbitrarily determined by the operator=
 and in conformance with the requirement)<u></u><u></u></p>

<p><u></u><span>3)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u><a href=3D"http://15.15.0.0/22" target=3D"_blank">15.15=
.0.0/22</a> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;EA length: 14 bits&nbsp; (10 bits f=
or IPv4 suffix and 4 bits for PSID)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; =3D&gt; these users will get PD/60 (arbitrarily determined by t=
he operator and in conformance with the requirement)<u></u><u></u></p>

<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">That was the easy part. What we need to do now is to d=
etermine:<u></u><u></u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fon=
t-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><u></u>Rule IPv6 Prefix&nbsp; (to complete BMR/FMR)<u></u><u><=
/u></p>
<p style=3D"margin-left:0.75in">
<u></u><span>-<span style=3D"font:7pt/normal &quot;Times New Roman&quot;;fon=
t-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><u></u>How will the end user DHCPv6 prefix (PD) be carved out b=
y DHCP server (assumption is that DHCPv6 server delegates v6 prefix and Rule=
s).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">We will represents the bits in v6 address via the fol=
lowing graph (we will ignore irrelevant parts of the v6 addresses for this d=
iscussion and instead consider only the bits /32 to /64):<u></u><u></u></p>

<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; /36&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /40&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /44&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; /48&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /52&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /56&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; /60&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /6=
4<u></u><u></u></p>
<p style=3D"text-indent:0.5in" class=3D"MsoNormal">xxxx &nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxxx &=
nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; | |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; |&lt; --------EA=3D12--------&gt;|&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 1) this will cover subnet 1) ; EA bits extend from the PD length (/56) to t=
he Rule IPv6 prefix length
 (/44)<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; |&lt; ---------EA=3D12------ &gt;|&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; 2) this will cover subnet 2); &nbsp;EA bits extend from the PD length (/60=
) to the Rule IPv6 prefix length
 (/48)<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; |&lt; ----------------EA=3D14------=
 &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3) this will cover subnet 3) ; EA bits ex=
tend from the PD length (/60) to the Rule IPv6 prefix length (/46)&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Now we have determined IPv6 Rule Prefix length for ea=
ch of the three rules that we need to create.
<u></u><u></u></p>
<p class=3D"MsoNormal">The IPv4 Prefix Rule lengths are /44, /48 and /46 for=
 the cases 1), 2) and 3) respectively.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Now we need to determine how can each end user prefix=
 be uniquely allocated across all users (CEs). The only way to ensure this u=
niqueness is to ensure that the portion of the IPv6 Rule prefix up to /44 (s=
mallest Rule IPv6 prefix length
 between all the rules in the MAP domain) is unique amongst all the rules.<u=
></u><u></u></p>
<p class=3D"MsoNormal">So, the IPv6 Rule prefixes for our three cases will b=
e (changing the part above /44):<u></u><u></u></p>
<p><u></u><span>1)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:0000::/44<u></u><u></u></p>
<p><u></u><span>2)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:0010::/48<u></u><u></u></p>
<p><u></u><span>3)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:0020::/46<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">The last step is to ensure that the DHCPv6 server han=
ds out proper end-user prefixes (and along with the prefixes, the Rules are d=
elegated as well).<u></u><u></u></p>
<p class=3D"MsoNormal">So the DHCPv6 can be configured so that it is carving=
 the prefixes from three ranges:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p><u></u><span>1)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:000x:xxyy::&nbsp; (where x denotes carving par=
t from /44 to /56 =E2=80=93 the EA bits; =E2=80=98y=E2=80=99 denotes further=
 subneting that is done on the CPE -&gt; yy=3D00 for MAP prefix, the remaini=
ng combinations are reserved for CPE delegation to its clients)<u></u><u></u=
></p>

<p><u></u><span>2)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:0100:xxxy::&nbsp; (where x denotes carving par=
t from /48 to /60 =E2=80=93 the EA bits; =E2=80=98y=E2=80=99 denotes further=
 subneting that is done on the CPE -&gt; y=3D0 for MAP prefix, the remaining=
 combinations are reserved for CPE delegation to its clients)<u></u><u></u><=
/p>

<p><u></u><span>3)<span style=3D"font:7pt/normal &quot;Times New Roman&quot;=
;font-size-adjust:none;font-stretch:normal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>2001:db8:020w:xxxy::&nbsp; (where x and two lower bits o=
f =E2=80=98w=E2=80=99 denote carving part from /46 to /60 =E2=80=93 the EA b=
its; =E2=80=98y=E2=80=99 denotes further subneting that is done on the CPE -=
&gt; y=3D0 for MAP prefix, the remaining combinations are reserved for CPE
 delegation to its clients)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Along with each user end prefix a BMR and a DMR will b=
e delegated to the end-users (so we will have a hub and spoke topology)<u></=
u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Also note that to cover the holes between the /48 and=
 /44 for case 2) we can easily add 15 more /24 IPv4 prefixes by creating new=
 IPv6 Rule by changing bits between /44 and /48.<u></u><u></u></p>
<p class=3D"MsoNormal">Similarly for case 3), we can create 3 more IPv6 rule=
 prefixes (and add 3 more /22 IPv4 subnets) by changing bits between /46 and=
 /48. This would allow us to expand the coverage for residual IPs (although t=
he purpose of NAT is to minimize
 their use over time not to expand <span style=3D"font-family:Wingdings">J</=
span>).
</p><p class=3D"MsoNormal">&nbsp;</p></div></div></blockquote><div>&nbsp;</d=
iv><div>&gt;&gt; co-authors: we&nbsp;may compose the 5.1 again based on Kris=
tian's proposed example and includes the #1 ~ #3 above and submit&nbsp;for w=
g&nbsp;review. agree?</div>
<div>&nbsp;</div><div>- maoke</div><div>&nbsp;</div><blockquote style=3D"mar=
gin: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 lang=
=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div><p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div>

<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>
<br></blockquote></div><br>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>Softwires mailing list</span><br=
><span><a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a></span><b=
r><span><a href=3D"https://www.ietf.org/mailman/listinfo/softwires">https://=
www.ietf.org/mailman/listinfo/softwires</a></span><br></div></blockquote></d=
iv></body></html>=

--Apple-Mail-A6012CC3-34B7-4A57-A4B9-65989788B602--

From bingxuere@gmail.com  Sun Mar 24 19:10:15 2013
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 AD0B221F8CEB for <softwires@ietfa.amsl.com>; Sun, 24 Mar 2013 19:10:15 -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, HTML_MESSAGE=0.001, 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 KTo79iT-rfqo for <softwires@ietfa.amsl.com>; Sun, 24 Mar 2013 19:10:14 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id EEE8D21F8C93 for <softwires@ietf.org>; Sun, 24 Mar 2013 19:10:13 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id ef5so2923270obb.13 for <softwires@ietf.org>; Sun, 24 Mar 2013 19:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=8mnQob8hsvj9lCaqWmAXNwc9lAHifKskjrtQd6u4Ca4=; b=JFF097A8FbYt2l+2r32u7c/aCSEHDmmgsR5a9Yz5A7LdhqgacOCwe39fzeELQ0JLwq 17sbvakaclw5wZdHVNlhmh8cNFlJx0JEXRhLt6H0kSjMEjUATFvI38xEXUHud9UrBeej i4wc4OJSIMECdvqza/tJMItnBCUFdyzPbpBnGX17pkmS/xOCquq757Nz7aoAFoYbg4or Nck2zUQxCT8dtN8RfiT5Zd9EJuFmnR3EDR7BMo1cWfJxSHO2X4oNU+DYKV7DhlqIh3me yzj6/Su3ecYPWk6CIH/Yv4r9H3sKtziCG+O7xdXyYY38vyGgzzyG/0gGBiQ8HXDWZC1f bsVQ==
X-Received: by 10.60.13.162 with SMTP id i2mr9628291oec.121.1364177413509; Sun, 24 Mar 2013 19:10:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.143.162 with HTTP; Sun, 24 Mar 2013 19:09:33 -0700 (PDT)
In-Reply-To: <2ACBDE7E-42B4-43DA-ACBC-C17EE65445BC@huawei.com>
References: <20130201174904.9314.39378.idtracker@ietfa.amsl.com> <2ACBDE7E-42B4-43DA-ACBC-C17EE65445BC@huawei.com>
From: Qiong <bingxuere@gmail.com>
Date: Mon, 25 Mar 2013 10:09:33 +0800
Message-ID: <CAH3bfABkkEgWuH3SuAcyHy0C+2AC0kihRRoTQQrM-=nE=CdjkQ@mail.gmail.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Content-Type: multipart/alternative; boundary=e89a8fb2011824a40b04d8b64e69
Cc: "Softwires@Ietf. Org" <softwires@ietf.org>
Subject: Re: [Softwires] Fwd: New Version Notification for draft-tsou-softwire-bfd-ds-lite-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: Mon, 25 Mar 2013 02:10:15 -0000

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

Hi authors,

Thanks for your work on this failover mechanism. I think it is in good
shape.

For the scope of this draft, does it only apply to DS-Lite ? I think it is
also helpful for lw4over6 scenario.

Best wishes
Qiong


On Sat, Feb 2, 2013 at 1:50 AM, Tina TSOU <Tina.Tsou.Zouting@huawei.com>wrote:

>  Dear all,
> For your comments.
>
>  Thank you,
> Tina
>
> Begin forwarded message:
>
>  *From:* <internet-drafts@ietf.org>
> *Date:* February 1, 2013 9:49:04 AM PST
> *To:* <tina.tsou.zouting@huawei.com>
> *Cc:* <brandon.lijian@huawei.com>, <repenno@cisco.com>, <
> cathy.zhou@huawei.com>, <mohamed.boucadair@orange.com>, <
> j.schoenwaelder@jacobs-university.de>
> *Subject:* *New Version Notification for
> draft-tsou-softwire-bfd-ds-lite-04.txt*
>
>
> A new version of I-D, draft-tsou-softwire-bfd-ds-lite-04.txt
> has been successfully submitted by Tina Tsou and posted to the
> IETF repository.
>
> Filename:     draft-tsou-softwire-bfd-ds-lite
> Revision:     04
> Title:         DS-Lite Failure Detection and Failover
> Creation date:     2013-02-01
> WG ID:         Individual Submission
> Number of pages: 10
> URL:
> http://www.ietf.org/internet-drafts/draft-tsou-softwire-bfd-ds-lite-04.txt
> Status:
> http://datatracker.ietf.org/doc/draft-tsou-softwire-bfd-ds-lite
> Htmlized:
> http://tools.ietf.org/html/draft-tsou-softwire-bfd-ds-lite-04
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-tsou-softwire-bfd-ds-lite-04
>
> Abstract:
>   In DS-Lite, the tunnel is stateless, not associated with any state
>   information, and no failure detection and failover mechanism is
>   available.  This makes it difficult to manage and diagnose if there
>   is a problem.  This draft analyzes the applicability of some of the
>   possible solutions.
>
>
>
>
> The IETF Secretariat
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>


-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/ *
===============================================

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

<div dir=3D"ltr">Hi authors,<div><br></div><div style>Thanks for your work =
on this failover mechanism. I think it is in good shape.</div><div style><b=
r></div><div style>For the scope of this draft, does it only apply to DS-Li=
te ? I think it is also helpful for lw4over6 scenario.=C2=A0</div>

<div style><br></div><div style>Best wishes</div><div style>Qiong =C2=A0</d=
iv><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, Fe=
b 2, 2013 at 1:50 AM, Tina TSOU <span dir=3D"ltr">&lt;<a href=3D"mailto:Tin=
a.Tsou.Zouting@huawei.com" target=3D"_blank">Tina.Tsou.Zouting@huawei.com</=
a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">



<div bgcolor=3D"#FFFFFF">
<div><span>Dear all,</span></div>
<div><span>For your comments.<br>
</span>
<div><br>
</div>
<div>Thank you,</div>
Tina</div>
<div><br>
Begin forwarded message:<br>
<br>
</div>
<blockquote type=3D"cite">
<div><b>From:</b> &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D=
"_blank">internet-drafts@ietf.org</a>&gt;<br>
<b>Date:</b> February 1, 2013 9:49:04 AM PST<br>
<b>To:</b> &lt;<a href=3D"mailto:tina.tsou.zouting@huawei.com" target=3D"_b=
lank">tina.tsou.zouting@huawei.com</a>&gt;<br>
<b>Cc:</b> &lt;<a href=3D"mailto:brandon.lijian@huawei.com" target=3D"_blan=
k">brandon.lijian@huawei.com</a>&gt;, &lt;<a href=3D"mailto:repenno@cisco.c=
om" target=3D"_blank">repenno@cisco.com</a>&gt;, &lt;<a href=3D"mailto:cath=
y.zhou@huawei.com" target=3D"_blank">cathy.zhou@huawei.com</a>&gt;, &lt;<a =
href=3D"mailto:mohamed.boucadair@orange.com" target=3D"_blank">mohamed.bouc=
adair@orange.com</a>&gt;,
 &lt;<a href=3D"mailto:j.schoenwaelder@jacobs-university.de" target=3D"_bla=
nk">j.schoenwaelder@jacobs-university.de</a>&gt;<br>
<b>Subject:</b> <b>New Version Notification for draft-tsou-softwire-bfd-ds-=
lite-04.txt</b><br>
<br>
</div>
</blockquote>
<div></div>
<blockquote type=3D"cite">
<div><span></span><br>
<span>A new version of I-D, draft-tsou-softwire-bfd-ds-lite-04.txt</span><b=
r>
<span>has been successfully submitted by Tina Tsou and posted to the</span>=
<br>
<span>IETF repository.</span><br>
<span></span><br>
<span>Filename: =C2=A0 =C2=A0 draft-tsou-softwire-bfd-ds-lite</span><br>
<span>Revision: =C2=A0 =C2=A0 04</span><br>
<span>Title: =C2=A0 =C2=A0 =C2=A0 =C2=A0 DS-Lite Failure Detection and Fail=
over</span><br>
<span>Creation date: =C2=A0 =C2=A0 2013-02-01</span><br>
<span>WG ID: =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission</span><br>
<span>Number of pages: 10</span><br>
<span>URL: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0<a href=3D"http://www.ietf.org/internet-drafts/draft-tsou-softwire=
-bfd-ds-lite-04.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/=
draft-tsou-softwire-bfd-ds-lite-04.txt</a></span><br>
<span>Status: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<a href=
=3D"http://datatracker.ietf.org/doc/draft-tsou-softwire-bfd-ds-lite" target=
=3D"_blank">http://datatracker.ietf.org/doc/draft-tsou-softwire-bfd-ds-lite=
</a></span><br>
<span>Htmlized: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<a href=3D"http:/=
/tools.ietf.org/html/draft-tsou-softwire-bfd-ds-lite-04" target=3D"_blank">=
http://tools.ietf.org/html/draft-tsou-softwire-bfd-ds-lite-04</a></span><br=
>
<span>Diff: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-tsou-softwire-bfd-ds=
-lite-04" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-tsou-s=
oftwire-bfd-ds-lite-04</a></span><br>
<span></span><br>
<span>Abstract:</span><br>
<span>=C2=A0=C2=A0In DS-Lite, the tunnel is stateless, not associated with =
any state</span><br>
<span>=C2=A0=C2=A0information, and no failure detection and failover mechan=
ism is</span><br>
<span>=C2=A0=C2=A0available. =C2=A0This makes it difficult to manage and di=
agnose if there</span><br>
<span>=C2=A0=C2=A0is a problem. =C2=A0This draft analyzes the applicability=
 of some of the</span><br>
<span>=C2=A0=C2=A0possible solutions.</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>The IETF Secretariat</span><br>
<span></span><br>
</div>
</blockquote>
</div>

<br>_______________________________________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/softwires</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Qiong Sun<br>C=
hina Telecom Beijing Research Institude<br><br><br>Open source code:<br>lig=
htweight 4over6: <i><a href=3D"http://sourceforge.net/projects/laft6/" targ=
et=3D"_blank">http://sourceforge.net/projects/laft6/</a></i><br>

PCP-natcoord:<i> <a href=3D"http://sourceforge.net/projects/pcpportsetdemo/=
" target=3D"_blank">http://sourceforge.net/projects/pcpportsetdemo/</a> </i=
><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
><br>
</div></div>

--e89a8fb2011824a40b04d8b64e69--

From xuxiaohu@huawei.com  Sun Mar 24 20:37:33 2013
Return-Path: <xuxiaohu@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 2D9EB21F88F1 for <softwires@ietfa.amsl.com>; Sun, 24 Mar 2013 20:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[AWL=2.401,  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 7T-bgoReRee4 for <softwires@ietfa.amsl.com>; Sun, 24 Mar 2013 20:37:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 342DB21F85D7 for <softwires@ietf.org>; Sun, 24 Mar 2013 20:37:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARB23426; Mon, 25 Mar 2013 03:37:30 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Mar 2013 03:35:52 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Mar 2013 03:36:04 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.50]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.01.0323.007; Mon, 25 Mar 2013 11:35:52 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: Motivation for the IP-in-UDP draft
Thread-Index: Ac4pCdjqtA1goQJnQeSuJf39uDZuYA==
Date: Mon, 25 Mar 2013 03:35:51 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F574E3@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [Softwires] Motivation for the IP-in-UDP draft
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, 25 Mar 2013 03:37:33 -0000

Hi all,

As suggested by WG co-chairs at IETF86, I would clarify the motivation for =
the IP-in-UDP draft (http://tools.ietf.org/html/draft-xu-softwire-ip-in-udp=
-01) as follows:

In a Softwire Mesh network, distinct customer (i.e. E-IP) traffic flows bet=
ween a given AFBR pair would be encapsulated with the same IP-based tunnel =
headers prior to traversing the I-IP transit core. As such, it would be har=
d for transit routers to achieve a fine-grained load balancing of these tun=
neled traffic flows across the transit core due to the lack of adequate ent=
ropy information.

[RFC5640] describes a method for improving the load balancing efficiency in=
 a network carrying Softwire Mesh service [RFC5565] over Layer Two Tunnelin=
g Protocol - Version 3 (L2TPv3) [RFC3931] and Generic Routing Encapsulation=
 (GRE)[RFC2784] encapsulations. However, this method requires core routers =
to perform hash calculation on the "load-balancing" field contained in tunn=
el encapsulation headers (i.e., the Session ID field in L2TPv3 headers or t=
he Key field in GRE headers), which is not widely supported by existing cor=
e routers. This situation has been affirmed by co-authors of the same RFC i=
n a new draft (http://tools.ietf.org/html/draft-kumar-softwire-uet-00) (see=
 below):

   "...[RFC5565] explains how routing information in BGP and data packets i=
n
   L2TPv3 or GRE are tunneled from one edge of an IPv4 network, over
   IPv6, to another IPv4 network or from one edge of an IPv6 network,
   over IPv4, to another IPv6 network.  [RFC5640] describes how to
   encode and load-balance specific flows by utilizing the L2TPv3
   Session ID or GRE Key field.  While implementations and deployments
   exist, not as many routers support the per-hop behavior described in
   [RFC5640] compared to routers that support load-balancing based on
   UDP ports..."

Since most existing core routers already support balancing IP traffic flows=
 based on the hash of the five-tuple of UDP packets, by encapsulating Softw=
ire service traffic into UDP tunnels with the source port field being used =
as an entropy field, it will enable existing core routers to perform effici=
ent load-balancing of the Softwire service traffic without requiring any ch=
ange to them. This is the motivation for the IP-in-UDP draft (http://tools.=
ietf.org/html/draft-xu-softwire-ip-in-udp-01). =20

Any comments and suggestions are welcome.=20

Best regards,
Xiaohu

From wwwrun@rfc-editor.org  Mon Mar 25 15:33:14 2013
Return-Path: <wwwrun@rfc-editor.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 4CDD821F882C; Mon, 25 Mar 2013 15:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 E4bf9KaQ9cjR; Mon, 25 Mar 2013 15:33:13 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id B82B421F8650; Mon, 25 Mar 2013 15:33:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7C260B1E002; Mon, 25 Mar 2013 15:32:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130325223249.7C260B1E002@rfc-editor.org>
Date: Mon, 25 Mar 2013 15:32:48 -0700 (PDT)
Cc: softwires@ietf.org, rfc-editor@rfc-editor.org
Subject: [Softwires] RFC 6908 on Deployment Considerations for Dual-Stack 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: Mon, 25 Mar 2013 22:33:14 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6908

        Title:      Deployment Considerations for Dual-Stack Lite 
        Author:     Y. Lee, R. Maglione,
                    C. Williams, C. Jacquenet,
                    M. Boucadair
        Status:     Informational
        Stream:     IETF
        Date:       March 2013
        Mailbox:    yiu_lee@cable.comcast.com, 
                    robmgl@cisco.com, 
                    carlw@mcsr-labs.org,
                    christian.jacquenet@orange.com, 
                    mohamed.boucadair@orange.com
        Pages:      14
        Characters: 35359
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-dslite-deployment-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6908.txt

This document discusses the deployment issues of and the requirements
for the deployment and operation of Dual-Stack Lite (DS-Lite).  This
document describes the various deployment considerations and
applicability of the DS-Lite architecture.

This document is a product of the Softwires Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From suresh.krishnan@ericsson.com  Mon Mar 25 21:26:04 2013
Return-Path: <suresh.krishnan@ericsson.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 F0A6421F8910 for <softwires@ietfa.amsl.com>; Mon, 25 Mar 2013 21:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 Q0t2k5ON0PHV for <softwires@ietfa.amsl.com>; Mon, 25 Mar 2013 21:26:03 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 623B021F88F1 for <softwires@ietf.org>; Mon, 25 Mar 2013 21:26:01 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-cb-515123580fdf
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id C1.2B.02411.95321515; Tue, 26 Mar 2013 05:26:01 +0100 (CET)
Received: from eusaamw0711.eamcs.ericsson.se (147.117.20.178) by EUSAAHC005.ericsson.se (147.117.188.87) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 26 Mar 2013 00:26:00 -0400
Received: from [164.48.125.25] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 26 Mar 2013 00:25:59 -0400
Message-ID: <515122BF.9070905@ericsson.com>
Date: Tue, 26 Mar 2013 00:23:27 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Softwires WG <softwires@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOLMWRmVeSWpSXmKPExsUyuXRPuG6kcmCgwdNGMYsfW5It3iydw25x eNlWJout3bEOLB5Tfm9k9Viy5CeTx+sD81k9jn9+yxzAEsVlk5Kak1mWWqRvl8CVsWRvQcFE torzz7YyNjD2sHYxcnJICJhIHHxwmxHCFpO4cG89WxcjF4eQwBFGiXWLNrBDOHsYJc5fmwvl bGWUaFnTyA7SwiugLbFq7XQmEJtFQFXi4+mrzCA2G9DYDTs/g8VFBcIkel+fY4SoF5Q4OfMJ C4gtAlT/ZOcDNhCbWSBbYt2J90D1HBzCAvYSk67EQ1wkKbHlRTs7RImexJSrLYwQtrzE9rdz wFYJCWhKbF3znXUCo+AsJBtmIWmZhaRlASPzKkaO0uLUstx0I8NNjMDAPSbB5riDccEny0OM 0hwsSuK8oa4XAoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUw1nOaa62ofpvp53RP5tKdtz0m f+Pvva7d9lXJTm/xuYS7NpNdfgbZ7i6cGsHvK/5gQljj7knyTid2KNl2fz7gorx+x9KTpuIO xhHVTpbPsi6q5RjwKGsbCnyVFCo2qXgzIbyay1fc3lp+U55fpcaWnseHN+ziuv1EO3Lv8SkP 99qkdM7auO2mEktxRqKhFnNRcSIAvIMOHyoCAAA=
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: [Softwires] Working group last call for draft-ietf-softwire-map-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: Tue, 26 Mar 2013 04:26:04 -0000

Hi all,
  This message starts a two week softwire working group last call on
advancing the draft about providing Mapping of Address and Port with
Encapsulation as a Standards Track RFC. The authors believe that this
version has addressed all the issues raised on the document. The latest
version of the draft is available at

http://www.ietf.org/id/draft-ietf-softwire-map-05.txt
http://tools.ietf.org/html/draft-ietf-softwire-map-05

Substantive comments and statements of support/opposition for advancing
this document should be directed to the mailing list. Editorial
suggestions can be sent directly to the authors. The chairs will send in
their comments as well during the last call period. This last call will
conclude on April 9, 2013.

Regards,
Suresh & Yong

From suresh.krishnan@ericsson.com  Mon Mar 25 21:30:12 2013
Return-Path: <suresh.krishnan@ericsson.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 BC54221F88F1 for <softwires@ietfa.amsl.com>; Mon, 25 Mar 2013 21:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 K6R2SS72EhHZ for <softwires@ietfa.amsl.com>; Mon, 25 Mar 2013 21:30:10 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id B03CB21F88D1 for <softwires@ietf.org>; Mon, 25 Mar 2013 21:30:09 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-f0-515124519428
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 98.2B.02411.15421515; Tue, 26 Mar 2013 05:30:09 +0100 (CET)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC007.ericsson.se (147.117.188.93) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 26 Mar 2013 00:30:08 -0400
Received: from [164.48.125.25] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 26 Mar 2013 00:30:08 -0400
Message-ID: <515123B7.2010303@ericsson.com>
Date: Tue, 26 Mar 2013 00:27:35 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Softwires WG <softwires@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJLMWRmVeSWpSXmKPExsUyuXRPrG6gSmCgwZqvMhY/tiRbvFk6h93i 8LKtTBZbu2MdWDym/N7I6rFkyU8mj9cH5rN6HP/8ljmAJYrLJiU1J7MstUjfLoEr493lPsaC 02wV03/9YmpgPMLaxcjJISFgItE65TwbhC0mceHeeiCbi0NI4AijxMY7j1ghnD2MEnPf97FD OFsZJT4+XMwM0sIroC1x7OZSFhCbRUBVYsP5pYwgNhvQ2A07PzOB2KICYRK9r88xQtQLSpyc +QSsXgSo/snOB2CrmQWyJdadeA9WLywQLLFl4URGiJMkJba8aGeHqNGTmHK1hRHClpfY/nYO 2A1CApoSW9d8Z53AKDgLyYpZSFpmIWlZwMi8ipGjtDi1LDfdyHATIzB4j0mwOe5gXPDJ8hCj NAeLkjhvqOuFACGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2MkX+XejnaJc2bqW+Qsmtfy87A 8JdR5p3eZlu/VLXfbstfvkv/nGSn56W1i7gY1BuvTlx/Q0JgppvEw5XxxjFWs+ROvOHZ7rd/ rctyM4Nu7jt9liLP+EINuMLf/6qbofClaelqmY+zv/KpaC1uLkxaPWPJs7sRQfPLFQX/M0n/ ytP6yF2sZ7JXiaU4I9FQi7moOBEAfplmyCwCAAA=
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: [Softwires] Working group last call for draft-ietf-softwire-multicast-prefix-option-03
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, 26 Mar 2013 04:30:12 -0000

Hi all,
  This message starts a two week softwire working group last call on
advancing the draft defining the DHCPv6 Option for IPv4-Embedded
Multicast and Unicast IPv6 Prefixes as a Standards Track RFC. The
authors believe that this version has addressed all the issues raised on
the document. The latest version of the draft is available at

http://www.ietf.org/id/draft-ietf-softwire-multicast-prefix-option-03.txt
http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-03

Substantive comments and statements of support/opposition for advancing
this document should be directed to the mailing list. Editorial
suggestions can be sent directly to the authors. The chairs will send in
their comments as well during the last call period. This last call will
conclude on April 9, 2013.

Regards,
Suresh & Yong

From suresh.krishnan@ericsson.com  Mon Mar 25 21:40:26 2013
Return-Path: <suresh.krishnan@ericsson.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 D561821F8939 for <softwires@ietfa.amsl.com>; Mon, 25 Mar 2013 21:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 eopHlLdXJK0n for <softwires@ietfa.amsl.com>; Mon, 25 Mar 2013 21:40:25 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id BAA3821F88EA for <softwires@ietf.org>; Mon, 25 Mar 2013 21:40:24 -0700 (PDT)
X-AuditID: c618062d-b7f0d6d00000097e-76-515126b7bf2f
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 8A.35.02430.8B621515; Tue, 26 Mar 2013 05:40:24 +0100 (CET)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC005.ericsson.se (147.117.188.87) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 26 Mar 2013 00:40:23 -0400
Received: from [164.48.125.25] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 26 Mar 2013 00:40:19 -0400
Message-ID: <51512618.8070704@ericsson.com>
Date: Tue, 26 Mar 2013 00:37:44 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Softwires WG <softwires@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAJMWRmVeSWpSXmKPExsUyuXRPuO4OtcBAgx3rRSwOL9vK5MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujAUn+QoeMVUsmnWFvYFxHlMXIyeHhICJxK4Jp9ghbDGJC/fW s3UxcnEICRxhlLhz5ROUs4dR4sThsywQzlZGiaknjzCDtPAKaEvMvHofrJ1FQFViy6mlrCA2 G9DYDTs/g60QFQiT6H19jhGiXlDi5MwnLCC2CFD9k50P2EBsYQFFiUffPrNAnCEpseVFO9hM ZgE9iSlXWxghbHmJ7W/ngO0VEtCU2LrmO+sERoFZSMbOQtIyC0nLAkbmVYwcpcWpZbnpRgab GIGhdkyCTXcH456XlocYpTlYlMR5g1wvBAgJpCeWpGanphakFsUXleakFh9iZOLglGpgdOxq 2clyR3XCGXW1+IIpO7UvXlZ6t77uwKL5aou8soxvcWtPmmg4zT7t0Qr/qXlanWcdmM2+r4j8 y+7KGfn7u2Lb1TebxSXaKrZGL8pPXF4muGrCOjvH+eZ5z+clWPvsNpLhWF1o/m/7zxPZk2Mf m63liF32Ie7K/QPiIRkBJYHpP4y/Re7eqcRSnJFoqMVcVJwIAGnH5tUDAgAA
Subject: [Softwires] IETF86 minutes available
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, 26 Mar 2013 04:40:26 -0000

Hi all,
  The draft minutes from both the Orlando softwire sessions are now
available at

http://www.ietf.org/proceedings/86/minutes/minutes-86-softwire

Please review these minutes and send us changes/additions by April 27,
2013.

We would like to thank Ole Troan, Tom Taylor, and Ian Farrer for taking
the minutes.

Regards
Suresh & Yong

From tomasz.mrugalski@gmail.com  Tue Mar 26 04:29:04 2013
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 9321D21F8A4E; Tue, 26 Mar 2013 04:29: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 ss6cyTcXq-7S; Tue, 26 Mar 2013 04:29:04 -0700 (PDT)
Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47]) by ietfa.amsl.com (Postfix) with ESMTP id BE87921F8A3F; Tue, 26 Mar 2013 04:28:53 -0700 (PDT)
Received: by mail-ee0-f47.google.com with SMTP id t10so701773eei.6 for <multiple recipients>; Tue, 26 Mar 2013 04:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-tagtoolbar-keys :x-forwarded-message-id:content-type:content-transfer-encoding; bh=PzOP7Mf9rfhmWYDUSlprk4hhyrBssBoac0px/11dHY8=; b=Q+N1jLD6aAMWWiyUBHckiQyLS6h8DCCXork7S2cUUtU0+hBGHnA2WYD0hL/POtZfCs o0h313JxrFsN7aC+kYMGFT6XlKZKpl3I19Bmcn3RerfCer21pHHwVr/n8oEqSyrWCoK3 5i4QV7VcjDex5pt2La2xlHuuByXQ3NEUBdy8SgFaRlMgbV+bf9Q7/d8NeIR/46AqhKjr guoCaH4ca6tgppIuLb9sZFgyJCfRi6wXjA7dW3HGhobuvZfsTDnWWC7oYH61WotXpApA CIt33y4Iz7MlAnfE1CSInmZ3A8cpP3EjWAkUOsvwSazIEtdG1O0t7ZMhYinMtH36+FRZ pRoQ==
X-Received: by 10.14.0.73 with SMTP id 49mr44370775eea.21.1364297332840; Tue, 26 Mar 2013 04:28:52 -0700 (PDT)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id t4sm24476616eel.0.2013.03.26.04.28.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Mar 2013 04:28:51 -0700 (PDT)
Message-ID: <5151866D.8010500@gmail.com>
Date: Tue, 26 Mar 2013 12:28:45 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
References: <515123B7.2010303@ericsson.com>
In-Reply-To: <515123B7.2010303@ericsson.com>
X-TagToolbar-Keys: D20130326122845900
X-Forwarded-Message-Id: <515123B7.2010303@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Softwires-wg <softwires@ietf.org>
Subject: [Softwires] Softwires WG last call for draft-ietf-softwire-multicast-prefix-option-03
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, 26 Mar 2013 11:29:04 -0000

Hi,
I just wanted to bring up this draft to DHC WG attention. There's a
draft that started WGLC in Softwires today. Please comment on it.

Tomek

-------- Original Message --------
Subject: [Softwires] Working group last call for
draft-ietf-softwire-multicast-prefix-option-03
Date: Tue, 26 Mar 2013 00:27:35 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Softwires WG <softwires@ietf.org>
CC: Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>

Hi all,
  This message starts a two week softwire working group last call on
advancing the draft defining the DHCPv6 Option for IPv4-Embedded
Multicast and Unicast IPv6 Prefixes as a Standards Track RFC. The
authors believe that this version has addressed all the issues raised on
the document. The latest version of the draft is available at

http://www.ietf.org/id/draft-ietf-softwire-multicast-prefix-option-03.txt
http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-03

Substantive comments and statements of support/opposition for advancing
this document should be directed to the mailing list. Editorial
suggestions can be sent directly to the authors. The chairs will send in
their comments as well during the last call period. This last call will
conclude on April 9, 2013.

Regards,
Suresh & Yong
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires



From Tina.Tsou.Zouting@huawei.com  Tue Mar 26 14:59:02 2013
Return-Path: <Tina.Tsou.Zouting@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 3F69221F863B for <softwires@ietfa.amsl.com>; Tue, 26 Mar 2013 14:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 MadI8PqxR5oi for <softwires@ietfa.amsl.com>; Tue, 26 Mar 2013 14:59:00 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id CD20221F8678 for <softwires@ietf.org>; Tue, 26 Mar 2013 14:58:59 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APU87669; Tue, 26 Mar 2013 21:58:57 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 26 Mar 2013 21:58:44 +0000
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 26 Mar 2013 21:58:55 +0000
Received: from DFWEML513-MBS.china.huawei.com ([169.254.4.86]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.01.0323.007; Tue, 26 Mar 2013 14:58:48 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Qiong <bingxuere@gmail.com>
Thread-Topic: [Softwires] Fwd: New Version Notification for draft-tsou-softwire-bfd-ds-lite-04.txt
Thread-Index: AQHOKP3tHsueSwzFpkaVm1395t9jGpi4iDPD
Date: Tue, 26 Mar 2013 21:58:47 +0000
Message-ID: <57D4BF36-D59F-4D7C-8906-7789046A1D9E@huawei.com>
References: <20130201174904.9314.39378.idtracker@ietfa.amsl.com> <2ACBDE7E-42B4-43DA-ACBC-C17EE65445BC@huawei.com>, <CAH3bfABkkEgWuH3SuAcyHy0C+2AC0kihRRoTQQrM-=nE=CdjkQ@mail.gmail.com>
In-Reply-To: <CAH3bfABkkEgWuH3SuAcyHy0C+2AC0kihRRoTQQrM-=nE=CdjkQ@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_57D4BF36D59F4D7C89067789046A1D9Ehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Softwires@Ietf. Org" <softwires@ietf.org>
Subject: Re: [Softwires] Fwd: New Version Notification for draft-tsou-softwire-bfd-ds-lite-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: Tue, 26 Mar 2013 21:59:02 -0000

--_000_57D4BF36D59F4D7C89067789046A1D9Ehuaweicom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear Qiong,
Thank you for your helpful review.
Co-authors and I agree to expand the scope to include LW4o6, as it is exten=
sion to DS-Lite.
We will address it in next version.

Thank you,
Tina

On Mar 24, 2013, at 7:10 PM, "Qiong" <bingxuere@gmail.com<mailto:bingxuere@=
gmail.com>> wrote:

Hi authors,

Thanks for your work on this failover mechanism. I think it is in good shap=
e.

For the scope of this draft, does it only apply to DS-Lite ? I think it is =
also helpful for lw4over6 scenario.

Best wishes
Qiong


On Sat, Feb 2, 2013 at 1:50 AM, Tina TSOU <Tina.Tsou.Zouting@huawei.com<mai=
lto:Tina.Tsou.Zouting@huawei.com>> wrote:
Dear all,
For your comments.

Thank you,
Tina

Begin forwarded message:

From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: February 1, 2013 9:49:04 AM PST
To: <tina.tsou.zouting@huawei.com<mailto:tina.tsou.zouting@huawei.com>>
Cc: <brandon.lijian@huawei.com<mailto:brandon.lijian@huawei.com>>, <repenno=
@cisco.com<mailto:repenno@cisco.com>>, <cathy.zhou@huawei.com<mailto:cathy.=
zhou@huawei.com>>, <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@o=
range.com>>, <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@j=
acobs-university.de>>
Subject: New Version Notification for draft-tsou-softwire-bfd-ds-lite-04.tx=
t


A new version of I-D, draft-tsou-softwire-bfd-ds-lite-04.txt
has been successfully submitted by Tina Tsou and posted to the
IETF repository.

Filename:     draft-tsou-softwire-bfd-ds-lite
Revision:     04
Title:         DS-Lite Failure Detection and Failover
Creation date:     2013-02-01
WG ID:         Individual Submission
Number of pages: 10
URL:             http://www.ietf.org/internet-drafts/draft-tsou-softwire-bf=
d-ds-lite-04.txt
Status:          http://datatracker.ietf.org/doc/draft-tsou-softwire-bfd-ds=
-lite
Htmlized:        http://tools.ietf.org/html/draft-tsou-softwire-bfd-ds-lite=
-04
Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-tsou-softwire-bfd=
-ds-lite-04

Abstract:
  In DS-Lite, the tunnel is stateless, not associated with any state
  information, and no failure detection and failover mechanism is
  available.  This makes it difficult to manage and diagnose if there
  is a problem.  This draft analyzes the applicability of some of the
  possible solutions.




The IETF Secretariat


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




--
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: http://sourceforge.net/projects/laft6/
PCP-natcoord: http://sourceforge.net/projects/pcpportsetdemo/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


--_000_57D4BF36D59F4D7C89067789046A1D9Ehuaweicom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body bgcolor=3D"#FFFFFF">
<div><span class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color:=
 rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192,=
 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.2304=
69); ">Dear Qiong,</span></div>
<div><span class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color:=
 rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192,=
 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.2304=
69); ">Thank you for your helpful review.</span></div>
<div><span class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color:=
 rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192,=
 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.2304=
69);">Co-authors and I agree to expand
 the scope to include LW4o6, as it is extension to DS-Lite.<br>
</span></div>
<div>
<div><span class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color:=
 rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192,=
 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.2304=
69);">We will address it in next version.</span></div>
<div><span class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color:=
 rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192,=
 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.2304=
69);"><br>
</span></div>
<div>Thank you,</div>
Tina</div>
<div><br>
On Mar 24, 2013, at 7:10 PM, &quot;Qiong&quot; &lt;<a href=3D"mailto:bingxu=
ere@gmail.com">bingxuere@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<div></div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">Hi authors,
<div><br>
</div>
<div style=3D"">Thanks for your work on this failover mechanism. I think it=
 is in good shape.</div>
<div style=3D""><br>
</div>
<div style=3D"">For the scope of this draft, does it only apply to DS-Lite =
? I think it is also helpful for lw4over6 scenario.&nbsp;</div>
<div style=3D""><br>
</div>
<div style=3D"">Best wishes</div>
<div style=3D"">Qiong &nbsp;</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Sat, Feb 2, 2013 at 1:50 AM, Tina TSOU <span =
dir=3D"ltr">
&lt;<a href=3D"mailto:Tina.Tsou.Zouting@huawei.com" target=3D"_blank">Tina.=
Tsou.Zouting@huawei.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<div bgcolor=3D"#FFFFFF">
<div><span>Dear all,</span></div>
<div><span>For your comments.<br>
</span>
<div><br>
</div>
<div>Thank you,</div>
Tina</div>
<div><br>
Begin forwarded message:<br>
<br>
</div>
<blockquote type=3D"cite">
<div><b>From:</b> &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D=
"_blank">internet-drafts@ietf.org</a>&gt;<br>
<b>Date:</b> February 1, 2013 9:49:04 AM PST<br>
<b>To:</b> &lt;<a href=3D"mailto:tina.tsou.zouting@huawei.com" target=3D"_b=
lank">tina.tsou.zouting@huawei.com</a>&gt;<br>
<b>Cc:</b> &lt;<a href=3D"mailto:brandon.lijian@huawei.com" target=3D"_blan=
k">brandon.lijian@huawei.com</a>&gt;, &lt;<a href=3D"mailto:repenno@cisco.c=
om" target=3D"_blank">repenno@cisco.com</a>&gt;, &lt;<a href=3D"mailto:cath=
y.zhou@huawei.com" target=3D"_blank">cathy.zhou@huawei.com</a>&gt;,
 &lt;<a href=3D"mailto:mohamed.boucadair@orange.com" target=3D"_blank">moha=
med.boucadair@orange.com</a>&gt;, &lt;<a href=3D"mailto:j.schoenwaelder@jac=
obs-university.de" target=3D"_blank">j.schoenwaelder@jacobs-university.de</=
a>&gt;<br>
<b>Subject:</b> <b>New Version Notification for draft-tsou-softwire-bfd-ds-=
lite-04.txt</b><br>
<br>
</div>
</blockquote>
<div></div>
<blockquote type=3D"cite">
<div><span></span><br>
<span>A new version of I-D, draft-tsou-softwire-bfd-ds-lite-04.txt</span><b=
r>
<span>has been successfully submitted by Tina Tsou and posted to the</span>=
<br>
<span>IETF repository.</span><br>
<span></span><br>
<span>Filename: &nbsp; &nbsp; draft-tsou-softwire-bfd-ds-lite</span><br>
<span>Revision: &nbsp; &nbsp; 04</span><br>
<span>Title: &nbsp; &nbsp; &nbsp; &nbsp; DS-Lite Failure Detection and Fail=
over</span><br>
<span>Creation date: &nbsp; &nbsp; 2013-02-01</span><br>
<span>WG ID: &nbsp; &nbsp; &nbsp; &nbsp; Individual Submission</span><br>
<span>Number of pages: 10</span><br>
<span>URL: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<a href=3D"http://www.ietf.org/internet-drafts/draft-tsou-softwire-=
bfd-ds-lite-04.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/d=
raft-tsou-softwire-bfd-ds-lite-04.txt</a></span><br>
<span>Status: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=
=3D"http://datatracker.ietf.org/doc/draft-tsou-softwire-bfd-ds-lite" target=
=3D"_blank">http://datatracker.ietf.org/doc/draft-tsou-softwire-bfd-ds-lite=
</a></span><br>
<span>Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http:/=
/tools.ietf.org/html/draft-tsou-softwire-bfd-ds-lite-04" target=3D"_blank">=
http://tools.ietf.org/html/draft-tsou-softwire-bfd-ds-lite-04</a></span><br=
>
<span>Diff: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-tsou-softwire-bfd-ds=
-lite-04" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-tsou-s=
oftwire-bfd-ds-lite-04</a></span><br>
<span></span><br>
<span>Abstract:</span><br>
<span>&nbsp;&nbsp;In DS-Lite, the tunnel is stateless, not associated with =
any state</span><br>
<span>&nbsp;&nbsp;information, and no failure detection and failover mechan=
ism is</span><br>
<span>&nbsp;&nbsp;available. &nbsp;This makes it difficult to manage and di=
agnose if there</span><br>
<span>&nbsp;&nbsp;is a problem. &nbsp;This draft analyzes the applicability=
 of some of the</span><br>
<span>&nbsp;&nbsp;possible solutions.</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>The IETF Secretariat</span><br>
<span></span><br>
</div>
</blockquote>
</div>
<br>
_______________________________________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/softwires</a><br>
<br>
</blockquote>
</div>
<br>
<br clear=3D"all">
<div><br>
</div>
-- <br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Qiong Sun<br>
China Telecom Beijing Research Institude<br>
<br>
<br>
Open source code:<br>
lightweight 4over6: <i><a href=3D"http://sourceforge.net/projects/laft6/" t=
arget=3D"_blank">http://sourceforge.net/projects/laft6/</a></i><br>
PCP-natcoord:<i> <a href=3D"http://sourceforge.net/projects/pcpportsetdemo/=
" target=3D"_blank">
http://sourceforge.net/projects/pcpportsetdemo/</a> </i><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_57D4BF36D59F4D7C89067789046A1D9Ehuaweicom_--

From phdgang@gmail.com  Tue Mar 26 18:53:13 2013
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 6B70621F8501 for <softwires@ietfa.amsl.com>; Tue, 26 Mar 2013 18:53:13 -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 Lplhw5EajJVs for <softwires@ietfa.amsl.com>; Tue, 26 Mar 2013 18:53:12 -0700 (PDT)
Received: from mail-qe0-f53.google.com (mail-qe0-f53.google.com [209.85.128.53]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE1C21F84D6 for <softwires@ietf.org>; Tue, 26 Mar 2013 18:53:12 -0700 (PDT)
Received: by mail-qe0-f53.google.com with SMTP id q19so2034687qeb.26 for <softwires@ietf.org>; Tue, 26 Mar 2013 18:53:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=en9tbkCfH5aG0nNAMwQDb1Hr280g3rtHn0/WQpjlEnY=; b=KfENnxgffLCDB7imwf/QwWpmnM6CEZhtqngAAjjnxkakB7Wv+nSXuRHbH2IP38iqSK 1n8VGvTrMh+/ILtukbZIpMUkyef3UdWiX0vl4u3Ec2CtrO/H9fRrGX0HaeUdA++GH7gn GZTjtQ21cTRCxKdov8V+J0NoLFZCSkPoNuiHa+6ZKy4AN6Lpykc78ovAcPPd0h9ao5UL /cquWstidlE4odNAjlsPGWXjzOJnimpNOnGD9zchwm48v6RDtXfdmkwmYTayGG0H56OU eiS0Lf6GbkslMmCu8Atg1OClJXOZUyjV76Rl49xJLyh5UYZonjOrpfe7bwWM2R0fDvKo 6Yhw==
MIME-Version: 1.0
X-Received: by 10.49.118.137 with SMTP id km9mr11713014qeb.34.1364349192060; Tue, 26 Mar 2013 18:53:12 -0700 (PDT)
Received: by 10.49.71.18 with HTTP; Tue, 26 Mar 2013 18:53:11 -0700 (PDT)
In-Reply-To: <2ACBDE7E-42B4-43DA-ACBC-C17EE65445BC@huawei.com>
References: <20130201174904.9314.39378.idtracker@ietfa.amsl.com> <2ACBDE7E-42B4-43DA-ACBC-C17EE65445BC@huawei.com>
Date: Wed, 27 Mar 2013 09:53:11 +0800
Message-ID: <CAM+vMEQqXwYCFnkS2s8cygyK2sS983GpoycbrwC47ah8psphMA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Softwires@Ietf. Org" <softwires@ietf.org>
Subject: Re: [Softwires] Fwd: New Version Notification for draft-tsou-softwire-bfd-ds-lite-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, 27 Mar 2013 01:53:13 -0000

Dear Authors,

I read the document. Very interested idea to apply BFD.
It would be good you could discuss some specific needs from Softwires
technologies to BFD.
Otherwise, it seems BFD is orthogonal to Softwire solution.

Many thanks

Gang

2013/2/2, Tina TSOU <Tina.Tsou.Zouting@huawei.com>:
> Dear all,
> For your comments.
>
> Thank you,
> Tina
>
> Begin forwarded message:
>
> From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
> Date: February 1, 2013 9:49:04 AM PST
> To: <tina.tsou.zouting@huawei.com<mailto:tina.tsou.zouting@huawei.com>>
> Cc: <brandon.lijian@huawei.com<mailto:brandon.lijian@huawei.com>>,
> <repenno@cisco.com<mailto:repenno@cisco.com>>,
> <cathy.zhou@huawei.com<mailto:cathy.zhou@huawei.com>>,
> <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>,
> <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>>
> Subject: New Version Notification for
> draft-tsou-softwire-bfd-ds-lite-04.txt
>
>
> A new version of I-D, draft-tsou-softwire-bfd-ds-lite-04.txt
> has been successfully submitted by Tina Tsou and posted to the
> IETF repository.
>
> Filename:     draft-tsou-softwire-bfd-ds-lite
> Revision:     04
> Title:         DS-Lite Failure Detection and Failover
> Creation date:     2013-02-01
> WG ID:         Individual Submission
> Number of pages: 10
> URL:
> http://www.ietf.org/internet-drafts/draft-tsou-softwire-bfd-ds-lite-04.txt
> Status:
> http://datatracker.ietf.org/doc/draft-tsou-softwire-bfd-ds-lite
> Htmlized:
> http://tools.ietf.org/html/draft-tsou-softwire-bfd-ds-lite-04
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-tsou-softwire-bfd-ds-lite-04
>
> Abstract:
>   In DS-Lite, the tunnel is stateless, not associated with any state
>   information, and no failure detection and failover mechanism is
>   available.  This makes it difficult to manage and diagnose if there
>   is a problem.  This draft analyzes the applicability of some of the
>   possible solutions.
>
>
>
>
> The IETF Secretariat
>
>

From christian.jacquenet@orange.com  Wed Mar 27 06:11:59 2013
Return-Path: <christian.jacquenet@orange.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 10B6F21F900B for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 06:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=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 OCPmDlFFREV6 for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 06:11:58 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 4211521F8EA5 for <softwires@ietf.org>; Wed, 27 Mar 2013 06:11:58 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 48BBD3244F2; Wed, 27 Mar 2013 14:11:57 +0100 (CET)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 2869E4C015; Wed, 27 Mar 2013 14:11:57 +0100 (CET)
Received: from PUEXCB1C.nanterre.francetelecom.fr ([10.233.200.25]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Wed, 27 Mar 2013 14:11:57 +0100
From: <christian.jacquenet@orange.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Softwires WG <softwires@ietf.org>
Date: Wed, 27 Mar 2013 14:11:56 +0100
Thread-Topic: [Softwires] Working group last call for draft-ietf-softwire-multicast-prefix-option-03
Thread-Index: Ac4p2p9CFaHig4ywRJiiWmTQeRtgJgBEeX5Q
Message-ID: <8052_1364389917_5152F01D_8052_57_1_983A1D8DA0DA5F4EB747BF34CBEE5CD15A7889E786@PUEXCB1C.nanterre.francetelecom.fr>
References: <515123B7.2010303@ericsson.com>
In-Reply-To: <515123B7.2010303@ericsson.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.25.85421
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] Working group last call for	draft-ietf-softwire-multicast-prefix-option-03
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, 27 Mar 2013 13:11:59 -0000

WG,

I'm in favor of advancing this document whose latest version looks fine to =
me.

Cheers,

Christian.=20

-----Message d'origine-----
De : softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] De la p=
art de Suresh Krishnan
Envoy=E9 : mardi 26 mars 2013 05:28
=C0 : Softwires WG
Cc : Yong Cui; Ralph Droms
Objet : [Softwires] Working group last call for draft-ietf-softwire-multica=
st-prefix-option-03

Hi all,
  This message starts a two week softwire working group last call on advanc=
ing the draft defining the DHCPv6 Option for IPv4-Embedded Multicast and Un=
icast IPv6 Prefixes as a Standards Track RFC. The authors believe that this=
 version has addressed all the issues raised on the document. The latest ve=
rsion of the draft is available at

http://www.ietf.org/id/draft-ietf-softwire-multicast-prefix-option-03.txt
http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-03

Substantive comments and statements of support/opposition for advancing thi=
s document should be directed to the mailing list. Editorial suggestions ca=
n be sent directly to the authors. The chairs will send in their comments a=
s well during the last call period. This last call will conclude on April 9=
, 2013.

Regards,
Suresh & Yong
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From tom.taylor.stds@gmail.com  Wed Mar 27 08:59:21 2013
Return-Path: <tom.taylor.stds@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 64BEC21F905C for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 08:59:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.171
X-Spam-Level: 
X-Spam-Status: No, score=-0.171 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877,  RDNS_NONE=0.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 AlMycfklJ940 for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 08:59:21 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id DA45221F9052 for <softwires@ietf.org>; Wed, 27 Mar 2013 08:59:20 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id k11so10453786iea.10 for <softwires@ietf.org>; Wed, 27 Mar 2013 08:59:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=Z1OtrxTQ1nCb3Ay1frMlzMW9AiFoNJ6Z1reu4Qdn/dc=; b=KFGVRC3O08jhMB+JQi9YnPa9Ux/v+gqt7nP77bucQ6IUUxq8sRLE2DW9BUPBMIqvtJ 4Wku5Egx8nwLr2eYvHNMUXrmfstduvhkooMXprVuRQtLpblmvQ50PIpKMGV84NYkDT+O 9MKPuOIvRno/M7PmKzJ8B8LOLVp/IpVZKpa0h07mv/0WWCeMEzLqL9Bk04OQNRkQOjVl Bd8xh0QJaS3bJViXQOtFjE51ec/FG5ClGSeaKMkytofDI6rLt+wOLLCZJ5a4PZTbrnNy mI9l/6OzCYxY1LdFTt6c7p+b8OOeIMZMHbpod63U2Py6VbizpZsiyIzlhQ8gHXGwW8fg pBfQ==
X-Received: by 10.42.215.196 with SMTP id hf4mr11987020icb.23.1364399960499; Wed, 27 Mar 2013 08:59:20 -0700 (PDT)
Received: from [127.0.0.1] ([64.56.244.88]) by mx.google.com with ESMTPS id y5sm7667647igg.7.2013.03.27.08.59.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 27 Mar 2013 08:59:19 -0700 (PDT)
Message-ID: <51531757.8000707@gmail.com>
Date: Wed, 27 Mar 2013 11:59:19 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: softwires@ietf.org
References: <51512618.8070704@ericsson.com>
In-Reply-To: <51512618.8070704@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130327-0, 27/03/2013), Outbound message
X-Antivirus-Status: Clean
Subject: [Softwires] The port mapping issue
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, 27 Mar 2013 15:59:21 -0000

The meeting minutes record a disagreement over what port mapping 
algorithm to use. This affects both MAP-E and LW 4over6. As I understand it:

- either of these two technologies will work with either contiguous 
ports or ports scattered according to the GMA algorithm

- the real objection to GMA comes from Alain Durand, who wants to set up 
simple min-port, max-port filters on his network equipment.


We all agree that port scattering offers negligible security advantage.

The reason that I heard given for preferring GMA for MAP-E is that it 
eliminates a restriction on the End-User Ipv6 address because the PSID 
is free to range from 0 upwards rather than from some higher number 
upwards. I don't follow this argument for two reasons:

- you now have a restriction that the offset field A must range from 1 
upwards

- the PSID field has an upper limit 2^k-1 imposed by the sharing ratio, 
imposing a further restriction on the End-User IPv6 address value.

Could someone spell out more clearly why the GMA was seen as necessary 
for MAP-E?

From stig@venaas.com  Wed Mar 27 12:06:06 2013
Return-Path: <stig@venaas.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 A4CB521F893B for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 12:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.49
X-Spam-Level: 
X-Spam-Status: No, score=-101.49 tagged_above=-999 required=5 tests=[AWL=-1.110, BAYES_00=-2.599, TVD_SPACE_RATIO=2.219, 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 ttRyrMJnuerv for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 12:06:05 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 80A6B21F871C for <softwires@ietf.org>; Wed, 27 Mar 2013 12:06:05 -0700 (PDT)
Received: from [10.21.81.103] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 732C280B4 for <softwires@ietf.org>; Wed, 27 Mar 2013 20:06:01 +0100 (CET)
Message-ID: <515343F5.7020901@venaas.com>
Date: Wed, 27 Mar 2013 12:09:41 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: softwires@ietf.org
References: <515123B7.2010303@ericsson.com>
In-Reply-To: <515123B7.2010303@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Softwires] Working group last call for draft-ietf-softwire-multicast-prefix-option-03
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, 27 Mar 2013 19:06:06 -0000

Support

Stig

From wdec.ietf@gmail.com  Wed Mar 27 13:09:52 2013
Return-Path: <wdec.ietf@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 4B68E21F89B2 for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 13:09:52 -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 EQpPh3DVDmgC for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 13:09:51 -0700 (PDT)
Received: from mail-qa0-f52.google.com (mail-qa0-f52.google.com [209.85.216.52]) by ietfa.amsl.com (Postfix) with ESMTP id 93DBA21F84FD for <softwires@ietf.org>; Wed, 27 Mar 2013 13:09:51 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id bs12so1134146qab.18 for <softwires@ietf.org>; Wed, 27 Mar 2013 13:09:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=9cnfAPemUjcuVVF6pVxTBG5TDUKzeCMsxxCyCoxwSOY=; b=oIkwRIZ17vRUAsHYhk6sDg/mMl79k+IBrardCP+43nF238wlHvgA1ABiBgLIZj2UWU VOjGViyGgG21otaVxr3tm9CaddrP5N8iYBwkmhJsDAvBWRd4BlMfBUsVLAFOgpZ0OVeG Cajfrzmif8glXaw2U6WbZLZkt/N+SVwa5hZ1bt+aRHviRFu9UvKPrcdQmwjGsoj0K0qc MTRbSlYmkSQ90C6wLbIvvE455q3rHKlz2+sRLYSPGtZdCLo/2tR/KUFEYHPtcyCJVgDB YzNdN+NAHPUslOOvycf8v/ohYbPpJkjkEDXl8I3FADY+qR6hQzia9lafEe7xr/JQxsmC Lupw==
MIME-Version: 1.0
X-Received: by 10.49.52.70 with SMTP id r6mr17788275qeo.20.1364414991089; Wed, 27 Mar 2013 13:09:51 -0700 (PDT)
Received: by 10.49.12.84 with HTTP; Wed, 27 Mar 2013 13:09:51 -0700 (PDT)
In-Reply-To: <51531757.8000707@gmail.com>
References: <51512618.8070704@ericsson.com> <51531757.8000707@gmail.com>
Date: Wed, 27 Mar 2013 21:09:51 +0100
Message-ID: <CAFFjW4iDp269jsMEX8gZA028sv-dyaqcvNemEDBZoSCN+H8chA@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: softwires@ietf.org
Subject: Re: [Softwires] The port mapping issue
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, 27 Mar 2013 20:09:52 -0000

On 27 March 2013 16:59, Tom Taylor <tom.taylor.stds@gmail.com> wrote:
> The meeting minutes record a disagreement over what port mapping algorithm
> to use. This affects both MAP-E and LW 4over6. As I understand it:
>
> - either of these two technologies will work with either contiguous ports or
> ports scattered according to the GMA algorithm
>
> - the real objection to GMA comes from Alain Durand, who wants to set up
> simple min-port, max-port filters on his network equipment.
>
>
> We all agree that port scattering offers negligible security advantage.
>
> The reason that I heard given for preferring GMA for MAP-E is that it
> eliminates a restriction on the End-User Ipv6 address because the PSID is
> free to range from 0 upwards rather than from some higher number upwards. I
> don't follow this argument for two reasons:
>
> - you now have a restriction that the offset field A must range from 1
> upwards
>
> - the PSID field has an upper limit 2^k-1 imposed by the sharing ratio,
> imposing a further restriction on the End-User IPv6 address value.
>
> Could someone spell out more clearly why the GMA was seen as necessary for
> MAP-E?

GMA codifies (power of 2) logic that translates easily into hardware
based longest match lookups. Furthermore, it is actually trivially
simple to implement on any platform (not hardware restricted thus):
Something like 2 lines of C code, in optimized form. Lastly, it is
very efficient in terms of info encoding: a PSID conveys a code-point
that maps the entire port space or port range. Finally, embedding a
explicit port-range in an IPv6 address is not an option (the N:1 rule
case).

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

From meng.wei2@zte.com.cn  Wed Mar 27 18:29:58 2013
Return-Path: <meng.wei2@zte.com.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22DB921F88E3 for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 18:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.395
X-Spam-Level: 
X-Spam-Status: No, score=-98.395 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, 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 EJr9tk9QJkxb for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 18:29:56 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 57B8A21F88D8 for <softwires@ietf.org>; Wed, 27 Mar 2013 18:29:56 -0700 (PDT)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 5C8D31261D6B; Thu, 28 Mar 2013 09:29:31 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id r2S1TMh2090408; Thu, 28 Mar 2013 09:29:22 +0800 (GMT-8) (envelope-from meng.wei2@zte.com.cn)
In-Reply-To: <515123B7.2010303@ericsson.com>
To: softwires@ietf.org
MIME-Version: 1.0
X-KeepSent: 308C1E1D:FE301C65-48257B3C:0007B224; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF308C1E1D.FE301C65-ON48257B3C.0007B224-48257B3C.0008344F@zte.com.cn>
From: meng.wei2@zte.com.cn
Date: Thu, 28 Mar 2013 09:29:21 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-03-28 09:29:04, Serialize complete at 2013-03-28 09:29:04
Content-Type: multipart/alternative; boundary="=_alternative 0008344C48257B3C_="
X-MAIL: mse02.zte.com.cn r2S1TMh2090408
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>
Subject: Re: [Softwires] Working group last call for draft-ietf-softwire-multicast-prefix-option-03
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, 28 Mar 2013 01:29:58 -0000

This is a multipart message in MIME format.
--=_alternative 0008344C48257B3C_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

U3VwcG9ydCENCg0KUkFESVVTIEV4dGVuc2lvbnMgb2YgbXVsdGljYXN0LXByZWZpeC1vcHRpb24g
aXMgd29ydGh5IG9mIGF0dGVudGlvbiB0b28uIA0KVGhhbmtzLg0KDQpXZWkNCg0KDQoNCg0Kc29m
dHdpcmVzLWJvdW5jZXNAaWV0Zi5vcmcg0LTT2iAyMDEzLTAzLTI2IDEyOjI3OjM1Og0KDQo+IEhp
IGFsbCwNCj4gICBUaGlzIG1lc3NhZ2Ugc3RhcnRzIGEgdHdvIHdlZWsgc29mdHdpcmUgd29ya2lu
ZyBncm91cCBsYXN0IGNhbGwgb24NCj4gYWR2YW5jaW5nIHRoZSBkcmFmdCBkZWZpbmluZyB0aGUg
REhDUHY2IE9wdGlvbiBmb3IgSVB2NC1FbWJlZGRlZA0KPiBNdWx0aWNhc3QgYW5kIFVuaWNhc3Qg
SVB2NiBQcmVmaXhlcyBhcyBhIFN0YW5kYXJkcyBUcmFjayBSRkMuIFRoZQ0KPiBhdXRob3JzIGJl
bGlldmUgdGhhdCB0aGlzIHZlcnNpb24gaGFzIGFkZHJlc3NlZCBhbGwgdGhlIGlzc3VlcyByYWlz
ZWQgb24NCj4gdGhlIGRvY3VtZW50LiBUaGUgbGF0ZXN0IHZlcnNpb24gb2YgdGhlIGRyYWZ0IGlz
IGF2YWlsYWJsZSBhdA0KPiANCj4gDQpodHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWlldGYt
c29mdHdpcmUtbXVsdGljYXN0LXByZWZpeC1vcHRpb24tMDMudHh0DQo+IA0KaHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1zb2Z0d2lyZS1tdWx0aWNhc3QtcHJlZml4LW9wdGlv
bi0wMw0KPiANCj4gU3Vic3RhbnRpdmUgY29tbWVudHMgYW5kIHN0YXRlbWVudHMgb2Ygc3VwcG9y
dC9vcHBvc2l0aW9uIGZvciBhZHZhbmNpbmcNCj4gdGhpcyBkb2N1bWVudCBzaG91bGQgYmUgZGly
ZWN0ZWQgdG8gdGhlIG1haWxpbmcgbGlzdC4gRWRpdG9yaWFsDQo+IHN1Z2dlc3Rpb25zIGNhbiBi
ZSBzZW50IGRpcmVjdGx5IHRvIHRoZSBhdXRob3JzLiBUaGUgY2hhaXJzIHdpbGwgc2VuZCBpbg0K
PiB0aGVpciBjb21tZW50cyBhcyB3ZWxsIGR1cmluZyB0aGUgbGFzdCBjYWxsIHBlcmlvZC4gVGhp
cyBsYXN0IGNhbGwgd2lsbA0KPiBjb25jbHVkZSBvbiBBcHJpbCA5LCAyMDEzLg0KPiANCj4gUmVn
YXJkcywNCj4gU3VyZXNoICYgWW9uZw0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPiBTb2Z0d2lyZXMgbWFpbGluZyBsaXN0DQo+IFNvZnR3aXJlc0Bp
ZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NvZnR3aXJl
cw0KDQo=
--=_alternative 0008344C48257B3C_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlN1cHBvcnQhPC9mb250Pg0KPGJy
Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5SQURJVVMgRXh0ZW5zaW9ucyBv
ZiBtdWx0aWNhc3QtcHJlZml4LW9wdGlvbg0KaXMgd29ydGh5IG9mIGF0dGVudGlvbiB0b28uIFRo
YW5rcy48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPldl
aTwvZm9udD4NCjxicj4NCjxicj4NCjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPnNv
ZnR3aXJlcy1ib3VuY2VzQGlldGYub3JnINC009ogMjAxMy0wMy0yNiAxMjoyNzozNTo8YnI+DQo8
YnI+DQomZ3Q7IEhpIGFsbCw8YnI+DQomZ3Q7ICZuYnNwOyBUaGlzIG1lc3NhZ2Ugc3RhcnRzIGEg
dHdvIHdlZWsgc29mdHdpcmUgd29ya2luZyBncm91cCBsYXN0DQpjYWxsIG9uPGJyPg0KJmd0OyBh
ZHZhbmNpbmcgdGhlIGRyYWZ0IGRlZmluaW5nIHRoZSBESENQdjYgT3B0aW9uIGZvciBJUHY0LUVt
YmVkZGVkPGJyPg0KJmd0OyBNdWx0aWNhc3QgYW5kIFVuaWNhc3QgSVB2NiBQcmVmaXhlcyBhcyBh
IFN0YW5kYXJkcyBUcmFjayBSRkMuIFRoZTxicj4NCiZndDsgYXV0aG9ycyBiZWxpZXZlIHRoYXQg
dGhpcyB2ZXJzaW9uIGhhcyBhZGRyZXNzZWQgYWxsIHRoZSBpc3N1ZXMgcmFpc2VkDQpvbjxicj4N
CiZndDsgdGhlIGRvY3VtZW50LiBUaGUgbGF0ZXN0IHZlcnNpb24gb2YgdGhlIGRyYWZ0IGlzIGF2
YWlsYWJsZSBhdDxicj4NCiZndDsgPGJyPg0KJmd0OyBodHRwOi8vd3d3LmlldGYub3JnL2lkL2Ry
YWZ0LWlldGYtc29mdHdpcmUtbXVsdGljYXN0LXByZWZpeC1vcHRpb24tMDMudHh0PGJyPg0KJmd0
OyBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXNvZnR3aXJlLW11bHRpY2Fz
dC1wcmVmaXgtb3B0aW9uLTAzPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFN1YnN0YW50aXZlIGNvbW1l
bnRzIGFuZCBzdGF0ZW1lbnRzIG9mIHN1cHBvcnQvb3Bwb3NpdGlvbiBmb3IgYWR2YW5jaW5nPGJy
Pg0KJmd0OyB0aGlzIGRvY3VtZW50IHNob3VsZCBiZSBkaXJlY3RlZCB0byB0aGUgbWFpbGluZyBs
aXN0LiBFZGl0b3JpYWw8YnI+DQomZ3Q7IHN1Z2dlc3Rpb25zIGNhbiBiZSBzZW50IGRpcmVjdGx5
IHRvIHRoZSBhdXRob3JzLiBUaGUgY2hhaXJzIHdpbGwgc2VuZA0KaW48YnI+DQomZ3Q7IHRoZWly
IGNvbW1lbnRzIGFzIHdlbGwgZHVyaW5nIHRoZSBsYXN0IGNhbGwgcGVyaW9kLiBUaGlzIGxhc3Qg
Y2FsbA0Kd2lsbDxicj4NCiZndDsgY29uY2x1ZGUgb24gQXByaWwgOSwgMjAxMy48YnI+DQomZ3Q7
IDxicj4NCiZndDsgUmVnYXJkcyw8YnI+DQomZ3Q7IFN1cmVzaCAmYW1wOyBZb25nPGJyPg0KJmd0
OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZn
dDsgU29mdHdpcmVzIG1haWxpbmcgbGlzdDxicj4NCiZndDsgU29mdHdpcmVzQGlldGYub3JnPGJy
Pg0KJmd0OyBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NvZnR3aXJlczxi
cj4NCjwvZm9udD48L3R0Pg0K
--=_alternative 0008344C48257B3C_=--

From cathy.zhou@huawei.com  Wed Mar 27 18:46:59 2013
Return-Path: <cathy.zhou@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 84CCC21F93CF for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 18:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOaSvfo14SbL for <softwires@ietfa.amsl.com>; Wed, 27 Mar 2013 18:46:59 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB8521F93CB for <softwires@ietf.org>; Wed, 27 Mar 2013 18:46:58 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APV85506; Thu, 28 Mar 2013 01:46:56 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 28 Mar 2013 01:46:33 +0000
Received: from SZXEML453-HUB.china.huawei.com (10.82.67.196) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 28 Mar 2013 01:46:55 +0000
Received: from SZXEML513-MBS.china.huawei.com ([169.254.8.13]) by SZXEML453-HUB.china.huawei.com ([10.82.67.196]) with mapi id 14.01.0323.007; Thu, 28 Mar 2013 09:46:48 +0800
From: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Softwires WG <softwires@ietf.org>
Thread-Topic: [Softwires] Working group last call for draft-ietf-softwire-multicast-prefix-option-03
Thread-Index: AQHOKdqgPZgRYcgPQku56/h0JyIPM5i6WAow
Date: Thu, 28 Mar 2013 01:46:47 +0000
Message-ID: <A6A061BEE5DDC94A9692D9D81AF776DF325FCF87@szxeml513-mbs.china.huawei.com>
References: <515123B7.2010303@ericsson.com>
In-Reply-To: <515123B7.2010303@ericsson.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.76.105]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] Working group last call for	draft-ietf-softwire-multicast-prefix-option-03
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, 28 Mar 2013 01:46:59 -0000

Support advancing this document.

Best Regards,
Cathy


> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
> Behalf Of Suresh Krishnan
> Sent: Tuesday, March 26, 2013 12:28 PM
> To: Softwires WG
> Cc: Yong Cui; Ralph Droms
> Subject: [Softwires] Working group last call for
> draft-ietf-softwire-multicast-prefix-option-03
>=20
> Hi all,
>   This message starts a two week softwire working group last call on
> advancing the draft defining the DHCPv6 Option for IPv4-Embedded
> Multicast and Unicast IPv6 Prefixes as a Standards Track RFC. The
> authors believe that this version has addressed all the issues raised on
> the document. The latest version of the draft is available at
>=20
> http://www.ietf.org/id/draft-ietf-softwire-multicast-prefix-option-03.txt
> http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-03
>=20
> Substantive comments and statements of support/opposition for advancing
> this document should be directed to the mailing list. Editorial
> suggestions can be sent directly to the authors. The chairs will send in
> their comments as well during the last call period. This last call will
> conclude on April 9, 2013.
>=20
> Regards,
> Suresh & Yong
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From tom.taylor.stds@gmail.com  Thu Mar 28 07:12:24 2013
Return-Path: <tom.taylor.stds@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 022C221F8EB4 for <softwires@ietfa.amsl.com>; Thu, 28 Mar 2013 07:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.171
X-Spam-Level: 
X-Spam-Status: No, score=-0.171 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877,  RDNS_NONE=0.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 5R731in6hnvW for <softwires@ietfa.amsl.com>; Thu, 28 Mar 2013 07:12:23 -0700 (PDT)
Received: from mail-ia0-x22e.google.com (mail-ia0-x22e.google.com [IPv6:2607:f8b0:4001:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 6919E21F8D2E for <softwires@ietf.org>; Thu, 28 Mar 2013 07:12:23 -0700 (PDT)
Received: by mail-ia0-f174.google.com with SMTP id b35so8193182iac.5 for <softwires@ietf.org>; Thu, 28 Mar 2013 07:12:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-antivirus:x-antivirus-status; bh=W9JkwqfSmDDluRhWZb3C7pijcngR6ThE1Xl2oKbfYxY=; b=IGqguUyUTpB268u2NhW2I71qtJcCcL93rXtve64mGVndqC4oBGDV+nWnvE5aYve5Dq K0xrVF5ZA5RNEWEPSI069jC9x0duFZB0gXsQlt3PonwxxnCbrHvgwZzbZLTYdc2buvzD YGgMx1f5RJrO7XLK+E8GskFkxzNvtWgN4iQdUenZoowSjJrlmA0SFKNgClaTdybak6mh q6vgpS4u/TnGe9MVie4HF8UGzXZQyfWtElaSzYDI0aLroLrtNMj7P+eAAtHgTuxm4pW4 sb1VqwCpY8KvWlwN7QhIBCNjwBz6qf+0M35soNiFuDKRCApnujo+uKry+VNfVm9PZNVI DbDQ==
X-Received: by 10.50.150.167 with SMTP id uj7mr7331409igb.1.1364479943016; Thu, 28 Mar 2013 07:12:23 -0700 (PDT)
Received: from [127.0.0.1] ([64.56.244.88]) by mx.google.com with ESMTPS id vb15sm11917361igb.9.2013.03.28.07.12.21 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Mar 2013 07:12:22 -0700 (PDT)
Message-ID: <51544FC6.4000508@gmail.com>
Date: Thu, 28 Mar 2013 10:12:22 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Wojciech Dec <wdec.ietf@gmail.com>
References: <51512618.8070704@ericsson.com> <51531757.8000707@gmail.com> <CAFFjW4iDp269jsMEX8gZA028sv-dyaqcvNemEDBZoSCN+H8chA@mail.gmail.com>
In-Reply-To: <CAFFjW4iDp269jsMEX8gZA028sv-dyaqcvNemEDBZoSCN+H8chA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130328-0, 28/03/2013), Outbound message
X-Antivirus-Status: Clean
Cc: softwires@ietf.org
Subject: Re: [Softwires] The port mapping issue
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, 28 Mar 2013 14:12:24 -0000

On 27/03/2013 4:09 PM, Wojciech Dec wrote:
> On 27 March 2013 16:59, Tom Taylor <tom.taylor.stds@gmail.com> wrote:
>> The meeting minutes record a disagreement over what port mapping algorithm
>> to use. This affects both MAP-E and LW 4over6. As I understand it:
>>
>> - either of these two technologies will work with either contiguous ports or
>> ports scattered according to the GMA algorithm
>>
>> - the real objection to GMA comes from Alain Durand, who wants to set up
>> simple min-port, max-port filters on his network equipment.
>>
>>
>> We all agree that port scattering offers negligible security advantage.
>>
>> The reason that I heard given for preferring GMA for MAP-E is that it
>> eliminates a restriction on the End-User Ipv6 address because the PSID is
>> free to range from 0 upwards rather than from some higher number upwards. I
>> don't follow this argument for two reasons:
>>
>> - you now have a restriction that the offset field A must range from 1
>> upwards
>>
>> - the PSID field has an upper limit 2^k-1 imposed by the sharing ratio,
>> imposing a further restriction on the End-User IPv6 address value.
>>
>> Could someone spell out more clearly why the GMA was seen as necessary for
>> MAP-E?
>
> GMA codifies (power of 2) logic that translates easily into hardware
> based longest match lookups. Furthermore, it is actually trivially
> simple to implement on any platform (not hardware restricted thus):
> Something like 2 lines of C code, in optimized form. Lastly, it is
> very efficient in terms of info encoding: a PSID conveys a code-point
> that maps the entire port space or port range. Finally, embedding a
> explicit port-range in an IPv6 address is not an option (the N:1 rule
> case).
>
> Regards,
> Woj.

Thanks, Woj. I think I started off in the wrong direction, and should 
focus specifically on Suresh's proposal: GMA for both Light-Weight 4 
over 6 and MAP-E, with default a=0 for the former and a=6 for the latter.

When a=0, the GMA algorithm does degenerate to assigning ports as a 
single contiguous range per CPE. Min_port for a given PSID is given by 
the formula PSID * range size, or, in the notation of MAP-E section 5.1, 
PSID * 2^m. Max_port is given by Min_port + range size - 1.

With MAP-E, range size is inferred indirectly from the combination of 
the IPv4 prefix length in the Basic Map Rule and the number of EA bits. 
This information is not available for Light-Weight 4 over 6. Hence I 
believe the proposal to use GMA with a=0 for the latter amounts to 
explicit provisioning of PSID and range size to both the BR and the CPE.





From sunqi.csnet.thu@gmail.com  Thu Mar 28 19:04:04 2013
Return-Path: <sunqi.csnet.thu@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 A543F21F88C6 for <softwires@ietfa.amsl.com>; Thu, 28 Mar 2013 19:04: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 UIinnOlb8NaL for <softwires@ietfa.amsl.com>; Thu, 28 Mar 2013 19:04:04 -0700 (PDT)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id 3282D21F86BA for <softwires@ietf.org>; Thu, 28 Mar 2013 19:04:04 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id rl6so153345pac.33 for <softwires@ietf.org>; Thu, 28 Mar 2013 19:04:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=eoKJZVBcxdPeHwFi4ihh1VjtgaJSgJUsjluQibcKPwA=; b=tkBjUCFE6KuqpYO6hJrnxq9MmTDql3lqKnTasWgXhXgr7WAfzu6OfKnIvDWNwDMGkP JvbVaebnYapZYbnrZqv1r6vH8TRXJWnpJbPSfYzKi+susFxH4RPUQOGVBA69qszCnNzD OTg7JIXPX0C3e+G0J4IUg3xtNxKXjHX0GO291wRfC0w898VmtRsK7HXW9doXbcYSyUQ1 kxcHZaIT/Ua/TtEoKE93sz9G8k5I1oC5EXVht+Mzb6wIsm660MZRlFgkk4/6wPqW6qMX KXvSX7JcWDOEsw22xSnIlJJO3iah98q4zIKNdFaxOBx5pe393vUbfzxF88h6UT9t/XAv YDGw==
X-Received: by 10.68.231.164 with SMTP id th4mr1060796pbc.198.1364522640057; Thu, 28 Mar 2013 19:04:00 -0700 (PDT)
Received: from [192.168.1.170] ([166.111.68.233]) by mx.google.com with ESMTPS id 4sm897246pbn.23.2013.03.28.19.03.56 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Mar 2013 19:03:59 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <51544FC6.4000508@gmail.com>
Date: Fri, 29 Mar 2013 10:03:51 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F47F3D43-4800-4E3F-A34D-D1D9514E63E6@gmail.com>
References: <51512618.8070704@ericsson.com> <51531757.8000707@gmail.com> <CAFFjW4iDp269jsMEX8gZA028sv-dyaqcvNemEDBZoSCN+H8chA@mail.gmail.com> <51544FC6.4000508@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: softwires@ietf.org
Subject: Re: [Softwires] The port mapping issue
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, 29 Mar 2013 02:04:04 -0000

Dear Tom,

Thanks for bringing this up. I think Suresh's proposal (as is described =
in your mail) is fair enough. IMHO, for Lightweight 4 over 6 contiguous =
is enough (a =3D 0). While for MAP-E, considering PSID is required for =
the construction of IPv6 prefix, arbitrary value is necessary for that =
use.

Best Regards,
Qi
>=20
> Thanks, Woj. I think I started off in the wrong direction, and should =
focus specifically on Suresh's proposal: GMA for both Light-Weight 4 =
over 6 and MAP-E, with default a=3D0 for the former and a=3D6 for the =
latter.
>=20
> When a=3D0, the GMA algorithm does degenerate to assigning ports as a =
single contiguous range per CPE. Min_port for a given PSID is given by =
the formula PSID * range size, or, in the notation of MAP-E section 5.1, =
PSID * 2^m. Max_port is given by Min_port + range size - 1.
>=20
> With MAP-E, range size is inferred indirectly from the combination of =
the IPv4 prefix length in the Basic Map Rule and the number of EA bits. =
This information is not available for Light-Weight 4 over 6. Hence I =
believe the proposal to use GMA with a=3D0 for the latter amounts to =
explicit provisioning of PSID and range size to both the BR and the CPE.
>=20
>=20
>=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From tom.taylor.stds@gmail.com  Fri Mar 29 08:55:12 2013
Return-Path: <tom.taylor.stds@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 7D29521F9444 for <softwires@ietfa.amsl.com>; Fri, 29 Mar 2013 08:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.171
X-Spam-Level: 
X-Spam-Status: No, score=-0.171 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877,  RDNS_NONE=0.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 KcBUvaIhHLF1 for <softwires@ietfa.amsl.com>; Fri, 29 Mar 2013 08:55:11 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 4F9E221F85C9 for <softwires@ietf.org>; Fri, 29 Mar 2013 08:55:11 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id bn7so670478ieb.9 for <softwires@ietf.org>; Fri, 29 Mar 2013 08:55:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-antivirus:x-antivirus-status; bh=es7BotGp+ece64eXjpW4MqEjMtOLlB7c7SrfIMEuVbo=; b=XE6VpjXDnsqgis/INcLBlGnyr6vUx2LQlkidmaztng1+E6yBp1qGIwuYRsMKIEmOCN JGijyyPqx/IRDsUQ75/AmrBkjzGCTCI/hKaxCLwcCKcJVo+RBrdEFQWJlV0a4y8cSDLw m2ixUPvXM7caNuGAJgLjZBV4AtEh77dVSXhITzXlSnNLbODUEOlHTaWmawItORctQKaj 6uXvIdnqNbjTa81t0++DN5QVqzxuGpWdeUhk+uKDsjMWIEl2U9nF3xyIliPOQ2XTu4Dw B0dTbJDCPdCWG4qzWYql8q56AxRAPFx6UfeiUq1JC4d95y3ofExjAM0STM0IQclhXryM wELA==
X-Received: by 10.50.70.9 with SMTP id i9mr9909849igu.60.1364572510976; Fri, 29 Mar 2013 08:55:10 -0700 (PDT)
Received: from [127.0.0.1] ([64.56.244.88]) by mx.google.com with ESMTPS id dy5sm40638igc.1.2013.03.29.08.55.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 29 Mar 2013 08:55:10 -0700 (PDT)
Message-ID: <5155B95D.8070107@gmail.com>
Date: Fri, 29 Mar 2013 11:55:09 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <515123B7.2010303@ericsson.com>
In-Reply-To: <515123B7.2010303@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130329-0, 29/03/2013), Outbound message
X-Antivirus-Status: Clean
Cc: Softwires WG <softwires@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] Working group last call for draft-ietf-softwire-multicast-prefix-option-03
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, 29 Mar 2013 15:55:12 -0000

Support.

On 26/03/2013 12:27 AM, Suresh Krishnan wrote:
> Hi all,
>    This message starts a two week softwire working group last call on
> advancing the draft defining the DHCPv6 Option for IPv4-Embedded
> Multicast and Unicast IPv6 Prefixes as a Standards Track RFC. The
> authors believe that this version has addressed all the issues raised on
> the document. The latest version of the draft is available at
>
> http://www.ietf.org/id/draft-ietf-softwire-multicast-prefix-option-03.txt
> http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-03
>
> Substantive comments and statements of support/opposition for advancing
> this document should be directed to the mailing list. Editorial
> suggestions can be sent directly to the authors. The chairs will send in
> their comments as well during the last call period. This last call will
> conclude on April 9, 2013.
>
> Regards,
> Suresh & Yong
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>

From tom.taylor.stds@gmail.com  Fri Mar 29 09:05:18 2013
Return-Path: <tom.taylor.stds@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 80BC121F946D for <softwires@ietfa.amsl.com>; Fri, 29 Mar 2013 09:05:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.171
X-Spam-Level: 
X-Spam-Status: No, score=-0.171 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877,  RDNS_NONE=0.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 x514dml3WiV4 for <softwires@ietfa.amsl.com>; Fri, 29 Mar 2013 09:05:18 -0700 (PDT)
Received: from mail-ia0-x231.google.com (mail-ia0-x231.google.com [IPv6:2607:f8b0:4001:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id E871721F9456 for <softwires@ietf.org>; Fri, 29 Mar 2013 09:05:17 -0700 (PDT)
Received: by mail-ia0-f177.google.com with SMTP id w33so504833iag.22 for <softwires@ietf.org>; Fri, 29 Mar 2013 09:05:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-antivirus :x-antivirus-status; bh=H0BI79SIbufhZNOItlDsxutBdfVe1yLD7we5slpIobU=; b=vDcNFbr1s4zIfilnzPTYhwulC4ZFAyX7tMjHNI1/ksrc+rNbCpnOVsBnFU2N1hXfkS Ck7Svgcn2lUBPz+lD9mynOgrqoPcP4vFgFsBoc31+vx6uJh6cZnR4mqQTNWEIDaeBAtO jxyv0hIw3LFiZixPkSJsexuR8mOdQro7cvdpDUnjoxDNMSTih+EfKZJrQhoukiH0I11i OsNYFhsEOdtcQcXId3C1L/IFqwUFN6NJQdZ0Bo3IDEHOP73ccnx00KnfXqkjllrAwUSC EQVCt2WQwYcBv+PifpYmEv2nJ5r37VjAiLLLneqdDW+t0S6JYlpFQ4UMRzTBWMBLXZuf dhGA==
X-Received: by 10.50.50.71 with SMTP id a7mr57184igo.14.1364573108132; Fri, 29 Mar 2013 09:05:08 -0700 (PDT)
Received: from [127.0.0.1] ([64.56.244.88]) by mx.google.com with ESMTPS id xd4sm64318igb.3.2013.03.29.09.05.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 29 Mar 2013 09:05:07 -0700 (PDT)
Message-ID: <5155BBB3.1090304@gmail.com>
Date: Fri, 29 Mar 2013 12:05:07 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Softwires <softwires@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130329-0, 29/03/2013), Outbound message
X-Antivirus-Status: Clean
Subject: [Softwires] MUST or must for /96 in draft-ietf-softwire-multicast-prefix-option-03?
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, 29 Mar 2013 16:05:18 -0000

I actually have two questions about the prefix-length fields in the option.

First, in section 4, there is the statement:

    When ASM_PREFIX64 and SSM_PREFIX64 are configured, the length of
    these prefixes must be /96.

Is that meant to be a MUST?

The second question is whether the absence of a particular prefix from a 
particular option is indicated by a prefix length of zero. If so, should 
that be mentioned somewhere in section 3, or is it covered by standard 
DHCP practice?

Tom Taylor

From tom.taylor.stds@gmail.com  Fri Mar 29 09:11:47 2013
Return-Path: <tom.taylor.stds@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 66DA321F94A8 for <softwires@ietfa.amsl.com>; Fri, 29 Mar 2013 09:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.171
X-Spam-Level: 
X-Spam-Status: No, score=-0.171 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877,  RDNS_NONE=0.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 j7NIswaaQAjj for <softwires@ietfa.amsl.com>; Fri, 29 Mar 2013 09:11:47 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id C96F821F9499 for <softwires@ietf.org>; Fri, 29 Mar 2013 09:11:46 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id k11so673152iea.10 for <softwires@ietf.org>; Fri, 29 Mar 2013 09:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=ypxf7AnfEYP7olDj4ibomL4T56Klqjah7rrSjB90IOo=; b=KDyYPUlV3aYD0mxISl+TNGFlRsl9ImqPY4VfPx0To+xvibiH5Tv7uM7TwaqBSM+8L9 TlHyHs9M0qzExq7+OSBgN7x8pci8TPPtLqYyNaKnHfhD+v9fyelq5qJ6enep7z7z/GeT 1dr6spUNFwtbxIvpFw6YhxKXsuM7TgzujT9rxuqBPr3yhAXlrGKlizT0MbHFg7CxsBap ayxpuza0M9FmvFqztyFJVTXKnawvT/6mWhcGRbIUVG17xh+eNuOhxVe6V/bZ5ooR0JSF 8foUFXX3s1yBLNPaUoWWjFHZsTPEEkIAqd+IGaZZocoRMzgm+JlJaRq3WwHtIyZAOs0y vjJw==
X-Received: by 10.50.154.105 with SMTP id vn9mr79801igb.8.1364573506339; Fri, 29 Mar 2013 09:11:46 -0700 (PDT)
Received: from [127.0.0.1] ([64.56.244.88]) by mx.google.com with ESMTPS id y5sm56721igg.7.2013.03.29.09.11.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 29 Mar 2013 09:11:45 -0700 (PDT)
Message-ID: <5155BD41.2040705@gmail.com>
Date: Fri, 29 Mar 2013 12:11:45 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Softwires <softwires@ietf.org>
References: <5155BBB3.1090304@gmail.com>
In-Reply-To: <5155BBB3.1090304@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130329-0, 29/03/2013), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [Softwires] MUST or must for /96 in draft-ietf-softwire-multicast-prefix-option-03?
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, 29 Mar 2013 16:11:47 -0000

Apologies, that second question is covered thoroughly by client 
behaviour, section 5.

On 29/03/2013 12:05 PM, Tom Taylor wrote:
> I actually have two questions about the prefix-length fields in the option.
>
> First, in section 4, there is the statement:
>
>     When ASM_PREFIX64 and SSM_PREFIX64 are configured, the length of
>     these prefixes must be /96.
>
> Is that meant to be a MUST?
>
> The second question is whether the absence of a particular prefix from a
> particular option is indicated by a prefix length of zero. If so, should
> that be mentioned somewhere in section 3, or is it covered by standard
> DHCP practice?
>
> Tom Taylor

From kristian.poscic@alcatel-lucent.com  Sun Mar 31 05:22:04 2013
Return-Path: <kristian.poscic@alcatel-lucent.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 A19CE21F8573; Sun, 31 Mar 2013 05:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 D4DWBZq-zgDM; Sun, 31 Mar 2013 05:22:02 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id B5F3221F849C; Sun, 31 Mar 2013 05:22:02 -0700 (PDT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (h135-5-2-65.lucent.com [135.5.2.65]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r2VCLw9a028340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 31 Mar 2013 07:21:59 -0500 (CDT)
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id r2VCLvAX024753 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 31 Mar 2013 08:21:58 -0400
Received: from US70UWXCHMBA06.zam.alcatel-lucent.com ([169.254.11.15]) by US70TWXCHHUB03.zam.alcatel-lucent.com ([135.5.2.35]) with mapi id 14.02.0247.003; Sun, 31 Mar 2013 08:21:57 -0400
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: "behave@ietf.org" <behave@ietf.org>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: packet reordering in MAP
Thread-Index: Ac4uB4uRFRGCdwgZTzy7vxCW8THBdQ==
Date: Sun, 31 Mar 2013 12:21:56 +0000
Message-ID: <7921F977B17D5B49B8DCC955A339D2F02AA9B897@US70UWXCHMBA06.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.17]
Content-Type: multipart/alternative; boundary="_000_7921F977B17D5B49B8DCC955A339D2F02AA9B897US70UWXCHMBA06z_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: [Softwires] packet reordering in MAP
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, 31 Mar 2013 12:22:04 -0000

--_000_7921F977B17D5B49B8DCC955A339D2F02AA9B897US70UWXCHMBA06z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Can someone share some history and research backed data behind this stateme=
nt at the very bottom of section 4 in RFC 6145 (IP/ICMP Translation Algorit=
hm).

The translator SHOULD make sure that the packets belonging to the
   same flow leave the translator in the same order in which they
   arrived.

I'm wondering why would be acceptable for a box to reorder packets of the s=
ame flow (SHOULD vs MUST)?

While TCP can cope with reordering well (seq numbers plus TCP has MSS mecha=
nism to avoid fragmentation all together if the nodes in the path also supp=
ort MSS), I would think that (at least some)  apps using UDP transport woul=
d not tolerate packet reordering.
So I was hoping that someone can offer some references of real research bac=
ked data rather than opinions  (I would like to her opinions as well but th=
ey often differ).
Even if you have ECMP in the network and if all the nodes in the end-to-end=
 path are performing per flow load balancing over ECMP links (which should =
be the norm), packet reordering should not happen.
If nodes are performing per-packet load balancing over ECMP links then pack=
et reordering can occur but I would consider this bad practice (I know that=
 some old platforms would do per packet load balancing on ECMP links though=
).

The reason I ask this is in the context of implementing fragmentation/reass=
embly for MAP-E/T (although the issue extends beyond MAP).
For example in distributed platforms it would make sense to implement MAP t=
ranslation function in-line (in the forwarding cards) but the reassembly fu=
nction in the service cards since the reassembly function adds additional c=
omplexity and buffering requirements (I understand that the fragmented traf=
fic is small percentage of all traffic, but still...).
Let say that a v6 packet arrives to a BR (from the CPE).
The BR will process this packet in-line and send it out as v4.
Then another number of fragmented packets of the same flow arrive -> the BR=
 process those in service blades (not in-line).
While service blade is processing the fragments (reassembling them), anothe=
r non-fragmented packet of the same flow arrives on the BR.
This packet is processed in-line and sent out before the previously receive=
d fragments are reassembled in service blade.
Now the BR has caused packet re-ordering.
Why is this, according to RFC 6145) acceptable?

Any feedback appreciated.
Kris



--_000_7921F977B17D5B49B8DCC955A339D2F02AA9B897US70UWXCHMBA06z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Can someone share some history and research backed d=
ata behind this statement at the very bottom of section 4 in RFC 6145 (IP/I=
CMP Translation Algorithm).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">The transla=
tor SHOULD make sure that the packets belonging to the<o:p></o:p></span></p=
>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; same flow leave the translator in the same order in which they<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; arrived.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I&#8217;m wondering why would be acceptable for a bo=
x to reorder packets of the same flow (SHOULD vs MUST)?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While TCP can cope with reordering well (seq numbers=
 plus TCP has MSS mechanism to avoid fragmentation all together if the node=
s in the path also support MSS), I would think that (at least some) &nbsp;a=
pps using UDP transport would not tolerate
 packet reordering.<o:p></o:p></p>
<p class=3D"MsoNormal">So I was hoping that someone can offer some referenc=
es of real research backed data rather than opinions &nbsp;(I would like to=
 her opinions as well but they often differ).
<o:p></o:p></p>
<p class=3D"MsoNormal">Even if you have ECMP in the network and if all the =
nodes in the end-to-end path are performing per flow load balancing over EC=
MP links (which should be the norm), packet reordering should not happen.
<o:p></o:p></p>
<p class=3D"MsoNormal">If nodes are performing per-packet load balancing ov=
er ECMP links then packet reordering can occur but I would consider this ba=
d practice (I know that some old platforms would do per packet load balanci=
ng on ECMP links though).
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The reason I ask this is in the context of implement=
ing fragmentation/reassembly for MAP-E/T (although the issue extends beyond=
 MAP).<o:p></o:p></p>
<p class=3D"MsoNormal">For example in distributed platforms it would make s=
ense to implement MAP translation function in-line (in the forwarding cards=
) but the reassembly function in the service cards since the reassembly fun=
ction adds additional complexity and
 buffering requirements (I understand that the fragmented traffic is small =
percentage of all traffic, but still&#8230;).<o:p></o:p></p>
<p class=3D"MsoNormal">Let say that a v6 packet arrives to a BR (from the C=
PE). <o:p>
</o:p></p>
<p class=3D"MsoNormal">The BR will process this packet in-line and send it =
out as v4.<o:p></o:p></p>
<p class=3D"MsoNormal">Then another number of fragmented packets of the sam=
e flow arrive -&gt; the BR process those in service blades (not in-line).<o=
:p></o:p></p>
<p class=3D"MsoNormal">While service blade is processing the fragments (rea=
ssembling them), another non-fragmented packet of the same flow arrives on =
the BR.<o:p></o:p></p>
<p class=3D"MsoNormal">This packet is processed in-line and sent out before=
 the previously received fragments are reassembled in service blade.<o:p></=
o:p></p>
<p class=3D"MsoNormal">Now the BR has caused packet re-ordering.<o:p></o:p>=
</p>
<p class=3D"MsoNormal">Why is this, according to RFC 6145) acceptable? <o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Any feedback appreciated.<o:p></o:p></p>
<p class=3D"MsoNormal">Kris<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;<o:p></o:p></p>
</div>
</body>
</html>

--_000_7921F977B17D5B49B8DCC955A339D2F02AA9B897US70UWXCHMBA06z_--

From brian.e.carpenter@gmail.com  Sun Mar 31 05:45:15 2013
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 3FB7021F845A; Sun, 31 Mar 2013 05:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.844
X-Spam-Level: 
X-Spam-Status: No, score=-99.844 tagged_above=-999 required=5 tests=[AWL=-0.923, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.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 MmQ-3agFUO0t; Sun, 31 Mar 2013 05:45:14 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4425821F8319; Sun, 31 Mar 2013 05:45:14 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id hj8so935922wib.7 for <multiple recipients>; Sun, 31 Mar 2013 05:45:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KrHuaBdGefY8jnl7bK3GNcL4kOxkxagqLh+CYltTv6M=; b=dC0R0/ZG9ZjUl9xjOwN9By7b0wHhsHv2bqPXBg/0PRNMPcPhf0AdRPd8pMOLk8DE1F gITZRc2VxAde78QgPX1RDoh8BhQQ3hKzGp8cxqrVqxAQ1XO1+F5s+U1EkoDHU27gAHm8 HmOj2yaHcd5PMtEeOjn9uQAeBAGEr3HIXVUYCEpNxtgBG0lEsdboYBXOTohfOK7S030X JKsPfrIvhNvjO5t5DjbdkNj3RPQnbj75IMlTEyNBdQ9zh5oeKWNovC4+0TeU6vZJHW3D PhyltyWMK4QqoR5A3IP8j/bYn03JD05lUAHzCwrHVPjrkLvdO2/zrXG8I88eXbjLex4D WiVw==
X-Received: by 10.180.92.229 with SMTP id cp5mr5731883wib.20.1364733913355; Sun, 31 Mar 2013 05:45:13 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-177.as13285.net. [2.102.218.177]) by mx.google.com with ESMTPS id dp5sm8178471wib.1.2013.03.31.05.45.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 05:45:12 -0700 (PDT)
Message-ID: <51582FD6.9060503@gmail.com>
Date: Sun, 31 Mar 2013 13:45:10 +0100
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: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA9B897@US70UWXCHMBA06.zam.alcatel-lucent.com>
In-Reply-To: <7921F977B17D5B49B8DCC955A339D2F02AA9B897@US70UWXCHMBA06.zam.alcatel-lucent.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "softwires@ietf.org" <softwires@ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [Softwires] [BEHAVE] packet reordering in MAP
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, 31 Mar 2013 12:45:15 -0000

Have a look at section 3.1.8 in RFC 6250, and there is a reference:
Bennett, J., Partridge, C., and N. Shectman, "Packet
reordering is not pathological network behavior", IEEE/ACM
Transactions on Networking, Vol. 7, No. 6, December 1999.

A UDP application that cannot tolerate reordering is broken.

Since the Internet does not and cannot guarantee the order of
delivery, I think the SHOULD is appropriate.

For example, if a translator is almost out of memory, surely it is
better to send a packet out of order than to drop it?

   Brian

On 31/03/2013 13:21, Poscic, Kristian (Kristian) wrote:
> Can someone share some history and research backed data behind this statement at the very bottom of section 4 in RFC 6145 (IP/ICMP Translation Algorithm).
> 
> The translator SHOULD make sure that the packets belonging to the
>    same flow leave the translator in the same order in which they
>    arrived.
> 
> I'm wondering why would be acceptable for a box to reorder packets of the same flow (SHOULD vs MUST)?
> 
> While TCP can cope with reordering well (seq numbers plus TCP has MSS mechanism to avoid fragmentation all together if the nodes in the path also support MSS), I would think that (at least some)  apps using UDP transport would not tolerate packet reordering.
> So I was hoping that someone can offer some references of real research backed data rather than opinions  (I would like to her opinions as well but they often differ).
> Even if you have ECMP in the network and if all the nodes in the end-to-end path are performing per flow load balancing over ECMP links (which should be the norm), packet reordering should not happen.
> If nodes are performing per-packet load balancing over ECMP links then packet reordering can occur but I would consider this bad practice (I know that some old platforms would do per packet load balancing on ECMP links though).
> 
> The reason I ask this is in the context of implementing fragmentation/reassembly for MAP-E/T (although the issue extends beyond MAP).
> For example in distributed platforms it would make sense to implement MAP translation function in-line (in the forwarding cards) but the reassembly function in the service cards since the reassembly function adds additional complexity and buffering requirements (I understand that the fragmented traffic is small percentage of all traffic, but still...).
> Let say that a v6 packet arrives to a BR (from the CPE).
> The BR will process this packet in-line and send it out as v4.
> Then another number of fragmented packets of the same flow arrive -> the BR process those in service blades (not in-line).
> While service blade is processing the fragments (reassembling them), another non-fragmented packet of the same flow arrives on the BR.
> This packet is processed in-line and sent out before the previously received fragments are reassembled in service blade.
> Now the BR has caused packet re-ordering.
> Why is this, according to RFC 6145) acceptable?
> 
> Any feedback appreciated.
> Kris
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From kristian.poscic@alcatel-lucent.com  Sun Mar 31 05:48:05 2013
Return-Path: <kristian.poscic@alcatel-lucent.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 157E121F8496; Sun, 31 Mar 2013 05:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 tHsnDgsK9s1k; Sun, 31 Mar 2013 05:48:04 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 44FF921F845D; Sun, 31 Mar 2013 05:48:04 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r2VCm2eO014977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 31 Mar 2013 07:48:02 -0500 (CDT)
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id r2VCm25U014225 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 31 Mar 2013 08:48:02 -0400
Received: from US70UWXCHMBA06.zam.alcatel-lucent.com ([169.254.11.15]) by US70TWXCHHUB03.zam.alcatel-lucent.com ([135.5.2.35]) with mapi id 14.02.0247.003; Sun, 31 Mar 2013 08:48:02 -0400
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [BEHAVE] packet reordering in MAP
Thread-Index: Ac4uB4uRFRGCdwgZTzy7vxCW8THBdQAJ4/sAAAhXG0A=
Date: Sun, 31 Mar 2013 12:48:01 +0000
Message-ID: <7921F977B17D5B49B8DCC955A339D2F02AA9B924@US70UWXCHMBA06.zam.alcatel-lucent.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA9B897@US70UWXCHMBA06.zam.alcatel-lucent.com> <51582FD6.9060503@gmail.com>
In-Reply-To: <51582FD6.9060503@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.17]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: "softwires@ietf.org" <softwires@ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [Softwires] [BEHAVE] packet reordering in MAP
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, 31 Mar 2013 12:48:05 -0000

T2ssIHRoaXMgaXMgZXhhY3RseSB3aGF0IEkgd2FzIGxvb2tpbmcgZm9yLiBMZXQgbWUgdGFrZSBh
IGxvb2sgYXQgdGhpcy4gVGhhbmtzIQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogQnJpYW4gRSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21d
IA0KU2VudDogU3VuZGF5LCBNYXJjaCAzMSwgMjAxMyA1OjQ1IEFNDQpUbzogUG9zY2ljLCBLcmlz
dGlhbiAoS3Jpc3RpYW4pDQpDYzogYmVoYXZlQGlldGYub3JnOyBzb2Z0d2lyZXNAaWV0Zi5vcmcN
ClN1YmplY3Q6IFJlOiBbQkVIQVZFXSBwYWNrZXQgcmVvcmRlcmluZyBpbiBNQVANCg0KSGF2ZSBh
IGxvb2sgYXQgc2VjdGlvbiAzLjEuOCBpbiBSRkMgNjI1MCwgYW5kIHRoZXJlIGlzIGEgcmVmZXJl
bmNlOg0KQmVubmV0dCwgSi4sIFBhcnRyaWRnZSwgQy4sIGFuZCBOLiBTaGVjdG1hbiwgIlBhY2tl
dCByZW9yZGVyaW5nIGlzIG5vdCBwYXRob2xvZ2ljYWwgbmV0d29yayBiZWhhdmlvciIsIElFRUUv
QUNNIFRyYW5zYWN0aW9ucyBvbiBOZXR3b3JraW5nLCBWb2wuIDcsIE5vLiA2LCBEZWNlbWJlciAx
OTk5Lg0KDQpBIFVEUCBhcHBsaWNhdGlvbiB0aGF0IGNhbm5vdCB0b2xlcmF0ZSByZW9yZGVyaW5n
IGlzIGJyb2tlbi4NCg0KU2luY2UgdGhlIEludGVybmV0IGRvZXMgbm90IGFuZCBjYW5ub3QgZ3Vh
cmFudGVlIHRoZSBvcmRlciBvZiBkZWxpdmVyeSwgSSB0aGluayB0aGUgU0hPVUxEIGlzIGFwcHJv
cHJpYXRlLg0KDQpGb3IgZXhhbXBsZSwgaWYgYSB0cmFuc2xhdG9yIGlzIGFsbW9zdCBvdXQgb2Yg
bWVtb3J5LCBzdXJlbHkgaXQgaXMgYmV0dGVyIHRvIHNlbmQgYSBwYWNrZXQgb3V0IG9mIG9yZGVy
IHRoYW4gdG8gZHJvcCBpdD8NCg0KICAgQnJpYW4NCg0KT24gMzEvMDMvMjAxMyAxMzoyMSwgUG9z
Y2ljLCBLcmlzdGlhbiAoS3Jpc3RpYW4pIHdyb3RlOg0KPiBDYW4gc29tZW9uZSBzaGFyZSBzb21l
IGhpc3RvcnkgYW5kIHJlc2VhcmNoIGJhY2tlZCBkYXRhIGJlaGluZCB0aGlzIHN0YXRlbWVudCBh
dCB0aGUgdmVyeSBib3R0b20gb2Ygc2VjdGlvbiA0IGluIFJGQyA2MTQ1IChJUC9JQ01QIFRyYW5z
bGF0aW9uIEFsZ29yaXRobSkuDQo+IA0KPiBUaGUgdHJhbnNsYXRvciBTSE9VTEQgbWFrZSBzdXJl
IHRoYXQgdGhlIHBhY2tldHMgYmVsb25naW5nIHRvIHRoZQ0KPiAgICBzYW1lIGZsb3cgbGVhdmUg
dGhlIHRyYW5zbGF0b3IgaW4gdGhlIHNhbWUgb3JkZXIgaW4gd2hpY2ggdGhleQ0KPiAgICBhcnJp
dmVkLg0KPiANCj4gSSdtIHdvbmRlcmluZyB3aHkgd291bGQgYmUgYWNjZXB0YWJsZSBmb3IgYSBi
b3ggdG8gcmVvcmRlciBwYWNrZXRzIG9mIHRoZSBzYW1lIGZsb3cgKFNIT1VMRCB2cyBNVVNUKT8N
Cj4gDQo+IFdoaWxlIFRDUCBjYW4gY29wZSB3aXRoIHJlb3JkZXJpbmcgd2VsbCAoc2VxIG51bWJl
cnMgcGx1cyBUQ1AgaGFzIE1TUyBtZWNoYW5pc20gdG8gYXZvaWQgZnJhZ21lbnRhdGlvbiBhbGwg
dG9nZXRoZXIgaWYgdGhlIG5vZGVzIGluIHRoZSBwYXRoIGFsc28gc3VwcG9ydCBNU1MpLCBJIHdv
dWxkIHRoaW5rIHRoYXQgKGF0IGxlYXN0IHNvbWUpICBhcHBzIHVzaW5nIFVEUCB0cmFuc3BvcnQg
d291bGQgbm90IHRvbGVyYXRlIHBhY2tldCByZW9yZGVyaW5nLg0KPiBTbyBJIHdhcyBob3Bpbmcg
dGhhdCBzb21lb25lIGNhbiBvZmZlciBzb21lIHJlZmVyZW5jZXMgb2YgcmVhbCByZXNlYXJjaCBi
YWNrZWQgZGF0YSByYXRoZXIgdGhhbiBvcGluaW9ucyAgKEkgd291bGQgbGlrZSB0byBoZXIgb3Bp
bmlvbnMgYXMgd2VsbCBidXQgdGhleSBvZnRlbiBkaWZmZXIpLg0KPiBFdmVuIGlmIHlvdSBoYXZl
IEVDTVAgaW4gdGhlIG5ldHdvcmsgYW5kIGlmIGFsbCB0aGUgbm9kZXMgaW4gdGhlIGVuZC10by1l
bmQgcGF0aCBhcmUgcGVyZm9ybWluZyBwZXIgZmxvdyBsb2FkIGJhbGFuY2luZyBvdmVyIEVDTVAg
bGlua3MgKHdoaWNoIHNob3VsZCBiZSB0aGUgbm9ybSksIHBhY2tldCByZW9yZGVyaW5nIHNob3Vs
ZCBub3QgaGFwcGVuLg0KPiBJZiBub2RlcyBhcmUgcGVyZm9ybWluZyBwZXItcGFja2V0IGxvYWQg
YmFsYW5jaW5nIG92ZXIgRUNNUCBsaW5rcyB0aGVuIHBhY2tldCByZW9yZGVyaW5nIGNhbiBvY2N1
ciBidXQgSSB3b3VsZCBjb25zaWRlciB0aGlzIGJhZCBwcmFjdGljZSAoSSBrbm93IHRoYXQgc29t
ZSBvbGQgcGxhdGZvcm1zIHdvdWxkIGRvIHBlciBwYWNrZXQgbG9hZCBiYWxhbmNpbmcgb24gRUNN
UCBsaW5rcyB0aG91Z2gpLg0KPiANCj4gVGhlIHJlYXNvbiBJIGFzayB0aGlzIGlzIGluIHRoZSBj
b250ZXh0IG9mIGltcGxlbWVudGluZyBmcmFnbWVudGF0aW9uL3JlYXNzZW1ibHkgZm9yIE1BUC1F
L1QgKGFsdGhvdWdoIHRoZSBpc3N1ZSBleHRlbmRzIGJleW9uZCBNQVApLg0KPiBGb3IgZXhhbXBs
ZSBpbiBkaXN0cmlidXRlZCBwbGF0Zm9ybXMgaXQgd291bGQgbWFrZSBzZW5zZSB0byBpbXBsZW1l
bnQgTUFQIHRyYW5zbGF0aW9uIGZ1bmN0aW9uIGluLWxpbmUgKGluIHRoZSBmb3J3YXJkaW5nIGNh
cmRzKSBidXQgdGhlIHJlYXNzZW1ibHkgZnVuY3Rpb24gaW4gdGhlIHNlcnZpY2UgY2FyZHMgc2lu
Y2UgdGhlIHJlYXNzZW1ibHkgZnVuY3Rpb24gYWRkcyBhZGRpdGlvbmFsIGNvbXBsZXhpdHkgYW5k
IGJ1ZmZlcmluZyByZXF1aXJlbWVudHMgKEkgdW5kZXJzdGFuZCB0aGF0IHRoZSBmcmFnbWVudGVk
IHRyYWZmaWMgaXMgc21hbGwgcGVyY2VudGFnZSBvZiBhbGwgdHJhZmZpYywgYnV0IHN0aWxsLi4u
KS4NCj4gTGV0IHNheSB0aGF0IGEgdjYgcGFja2V0IGFycml2ZXMgdG8gYSBCUiAoZnJvbSB0aGUg
Q1BFKS4NCj4gVGhlIEJSIHdpbGwgcHJvY2VzcyB0aGlzIHBhY2tldCBpbi1saW5lIGFuZCBzZW5k
IGl0IG91dCBhcyB2NC4NCj4gVGhlbiBhbm90aGVyIG51bWJlciBvZiBmcmFnbWVudGVkIHBhY2tl
dHMgb2YgdGhlIHNhbWUgZmxvdyBhcnJpdmUgLT4gdGhlIEJSIHByb2Nlc3MgdGhvc2UgaW4gc2Vy
dmljZSBibGFkZXMgKG5vdCBpbi1saW5lKS4NCj4gV2hpbGUgc2VydmljZSBibGFkZSBpcyBwcm9j
ZXNzaW5nIHRoZSBmcmFnbWVudHMgKHJlYXNzZW1ibGluZyB0aGVtKSwgYW5vdGhlciBub24tZnJh
Z21lbnRlZCBwYWNrZXQgb2YgdGhlIHNhbWUgZmxvdyBhcnJpdmVzIG9uIHRoZSBCUi4NCj4gVGhp
cyBwYWNrZXQgaXMgcHJvY2Vzc2VkIGluLWxpbmUgYW5kIHNlbnQgb3V0IGJlZm9yZSB0aGUgcHJl
dmlvdXNseSByZWNlaXZlZCBmcmFnbWVudHMgYXJlIHJlYXNzZW1ibGVkIGluIHNlcnZpY2UgYmxh
ZGUuDQo+IE5vdyB0aGUgQlIgaGFzIGNhdXNlZCBwYWNrZXQgcmUtb3JkZXJpbmcuDQo+IFdoeSBp
cyB0aGlzLCBhY2NvcmRpbmcgdG8gUkZDIDYxNDUpIGFjY2VwdGFibGU/DQo+IA0KPiBBbnkgZmVl
ZGJhY2sgYXBwcmVjaWF0ZWQuDQo+IEtyaXMNCj4gDQo+IA0KPiANCj4gDQo+IA0KPiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQo+IC0tDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPiBCZWhhdmUgbWFpbGluZyBsaXN0DQo+IEJlaGF2ZUBpZXRmLm9yZw0KPiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JlaGF2ZQ0K

From Ted.Lemon@nominum.com  Sun Mar 31 06:30:41 2013
Return-Path: <Ted.Lemon@nominum.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 4CD0D21F87B7; Sun, 31 Mar 2013 06:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-mw6IEvBy5A; Sun, 31 Mar 2013 06:30:40 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 67F0D21F85C9; Sun, 31 Mar 2013 06:30:40 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKUVg6gA8hWjrFXi5bfI+Wo3nIYCLSwiGG@postini.com; Sun, 31 Mar 2013 06:30:40 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4EE24128240; Sun, 31 Mar 2013 06:30:38 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D93E519005C; Sun, 31 Mar 2013 06:30:38 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 31 Mar 2013 06:30:38 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Softwires] [BEHAVE] packet reordering in MAP
Thread-Index: Ac4uB4uRFRGCdwgZTzy7vxCW8THBdQAQLU4AAAGW9IA=
Date: Sun, 31 Mar 2013 13:30:39 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775129E38@mbx-01.win.nominum.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA9B897@US70UWXCHMBA06.zam.alcatel-lucent.com> <51582FD6.9060503@gmail.com>
In-Reply-To: <51582FD6.9060503@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6A465DDD2FCAC543AC3C1EDC5D1F05B0@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [Softwires] [BEHAVE] packet reordering in MAP
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, 31 Mar 2013 13:30:41 -0000

On Mar 31, 2013, at 8:45 AM, Brian E Carpenter <brian.e.carpenter@gmail.com=
> wrote:
> For example, if a translator is almost out of memory, surely it is
> better to send a packet out of order than to drop it?

Almost surely it is already too late to fix the brokenness that began when =
the translator allowed its buffer to get so full.   The internet is *suppos=
ed* to drop packets in the face of congestion!

(Sorry, I realize that's off-topic, but I couldn't let this pass unremarked=
.)


From brian.e.carpenter@gmail.com  Sun Mar 31 07:51:33 2013
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 0770521F857E; Sun, 31 Mar 2013 07:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.614
X-Spam-Level: 
X-Spam-Status: No, score=-99.614 tagged_above=-999 required=5 tests=[AWL=-0.693, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.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 UqSo7VTytHyl; Sun, 31 Mar 2013 07:51:32 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 2B02F21F8564; Sun, 31 Mar 2013 07:51:31 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id hi18so974016wib.9 for <multiple recipients>; Sun, 31 Mar 2013 07:51:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=OfBYkKj6hCtUVPIfPgD5nypvL51IN856sc32W8b2iKA=; b=E7GVTLB6Gjg/pHNLVonVqNZ9GIrjgbsBBmHUX7pYmmD3nGgK6eejbTyA/kWCnPy/zB Vj0XBAuhdPR7Jojxv25uWLd7SG8yAcFXvmdA+VREOhYHBFjfsomOPCEU+srchHjrTX/q vuP1DsqGRuZdJgFWERouwb2whiIsyoLMDo+ey3F7dKZGzJLYxYnI7uLlxckfKz6XEJly ivucvkYUmo/BVxPdJYZtcBwgfiyzoVO47AFHGmnCx4WvClbzmEUb1Rrkf3xHDVwqFHtm QK0tuzYDTcaPuljMPpi+lGET5h0cEQ+1Iq+Cq/YPMHoMzSvKG61WUYudtFevKpjoiddU saYw==
X-Received: by 10.180.182.36 with SMTP id eb4mr6100312wic.8.1364741491347; Sun, 31 Mar 2013 07:51:31 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-177.as13285.net. [2.102.218.177]) by mx.google.com with ESMTPS id fg6sm9605430wib.10.2013.03.31.07.51.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 07:51:30 -0700 (PDT)
Message-ID: <51584D70.8010103@gmail.com>
Date: Sun, 31 Mar 2013 15:51:28 +0100
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: Ted Lemon <Ted.Lemon@nominum.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA9B897@US70UWXCHMBA06.zam.alcatel-lucent.com> <51582FD6.9060503@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775129E38@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775129E38@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "softwires@ietf.org" <softwires@ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [Softwires] [BEHAVE] packet reordering in MAP
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, 31 Mar 2013 14:51:33 -0000

Ted

On 31/03/2013 14:30, Ted Lemon wrote:
> On Mar 31, 2013, at 8:45 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> For example, if a translator is almost out of memory, surely it is
>> better to send a packet out of order than to drop it?
> 
> Almost surely it is already too late to fix the brokenness that began when the translator allowed its buffer to get so full.   The internet is *supposed* to drop packets in the face of congestion!
> 
> (Sorry, I realize that's off-topic, but I couldn't let this pass unremarked.)

Yes, there is certainly an interesting question about the trade-offs between
reordering and drops under congestion, but as far as this spec goes, the point
is that both can happen anyway, so imposing a MUST would be unreasonable.

    Brian

From Ted.Lemon@nominum.com  Sun Mar 31 07:56:15 2013
Return-Path: <Ted.Lemon@nominum.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 3FAC021F85C0; Sun, 31 Mar 2013 07:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id apL-z0-21Hqa; Sun, 31 Mar 2013 07:56:14 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id ADD4221F85B8; Sun, 31 Mar 2013 07:56:14 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUVhOjm25H+krVHNyJNdh/GK3eePLC1PR@postini.com; Sun, 31 Mar 2013 07:56:14 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4ACE2128279; Sun, 31 Mar 2013 07:56:14 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2B6B819005C; Sun, 31 Mar 2013 07:56:14 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 31 Mar 2013 07:56:08 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Softwires] [BEHAVE] packet reordering in MAP
Thread-Index: Ac4uB4uRFRGCdwgZTzy7vxCW8THBdQAQLU4AAAGW9IAAAtJCAAAAKgYA
Date: Sun, 31 Mar 2013 14:56:08 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775129FF6@mbx-01.win.nominum.com>
References: <7921F977B17D5B49B8DCC955A339D2F02AA9B897@US70UWXCHMBA06.zam.alcatel-lucent.com> <51582FD6.9060503@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775129E38@mbx-01.win.nominum.com> <51584D70.8010103@gmail.com>
In-Reply-To: <51584D70.8010103@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <83B2ECE492DBBC4DA793B10F525D7247@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [Softwires] [BEHAVE] packet reordering in MAP
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, 31 Mar 2013 14:56:15 -0000

On Mar 31, 2013, at 10:51 AM, Brian E Carpenter <brian.e.carpenter@gmail.co=
m>
 wrote:
> Yes, there is certainly an interesting question about the trade-offs betw=
een
> reordering and drops under congestion, but as far as this spec goes, the =
point
> is that both can happen anyway, so imposing a MUST would be unreasonable.

Indeed so.

