
From nobody Wed Oct  1 02:33:05 2014
Return-Path: <ianfarrer@gmx.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21F951ACD88 for <softwires@ietfa.amsl.com>; Wed,  1 Oct 2014 02:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iMcwNcH1qKN7 for <softwires@ietfa.amsl.com>; Wed,  1 Oct 2014 02:33:02 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EF6B1ACD87 for <softwires@ietf.org>; Wed,  1 Oct 2014 02:33:02 -0700 (PDT)
Received: from ians-mbp.lan ([62.225.30.139]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MIhDo-1XX3Lw1Z28-002Hil; Wed, 01 Oct 2014 11:33:00 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ian Farrer <ianfarrer@gmx.com>
In-Reply-To: <CAC8QAcdtsmG=cYqpTt-spTrvCLFWLFi7EYRzgRt7MjNZaTNfMw@mail.gmail.com>
Date: Wed, 1 Oct 2014 11:32:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA6D7597-362F-4DD8-AD5F-6C1B31ACD805@gmx.com>
References: <CAC8QAcdtsmG=cYqpTt-spTrvCLFWLFi7EYRzgRt7MjNZaTNfMw@mail.gmail.com>
To: sarikaya@ieee.org
X-Mailer: Apple Mail (2.1878.6)
X-Provags-ID: V03:K0:aAlbnZRpx+2DvkolLvL5H72BfUVWmKsFlfwWueZ03XJr+N3cQ9M ucJ813cJli2dfgusZ8R+qZcB2ttrQxT1E3J1mmXjVxI2aVaYZJ64+JaK67BtFQjxn7ClrJz ewzHiZJi/Q36DxezjvLYtP7Tut4V55VouIkTVZJMH0wTvAk8r/4HcLfLtdbuPlUNSrxIUAN 6wTD4SGim/Qzmo3i/E0yg==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/PjqrbPa9Z7kW6mc8I8IaqtAxb5g
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] lw4o6 question
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 01 Oct 2014 09:33:04 -0000

HI Behcet,

Thanks for pointing that out. Actually, I think that RFC2983 is the =
better reference, instead of RFC4213. As RFC2983 is informational, then =
this would move to being an informative reference (the current wording =
doesn=92t use normative language anyway).

Would that work?

Cheers,
Ian


On 24 Sep 2014, at 22:46, Behcet Sarikaya <sarikaya2012@gmail.com> =
wrote:

> Hi all,
>=20
> I noticed that RFC 4213 is referenced in both Section 5.2 and 6.2 =
regarding:
> Covering tunneling and traffic  class mapping between IPv4 and IPv6
>=20
> I am curious as to why RFC 4213 which only deals with tunneling IPv6
> packets in IPv4 would be relevant to lw4o6?
>=20
> Regards,
>=20
> Behcet
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From nobody Wed Oct  1 12:39:39 2014
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50B8F1A8769 for <softwires@ietfa.amsl.com>; Wed,  1 Oct 2014 12:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EeUoaKxvb0Ay for <softwires@ietfa.amsl.com>; Wed,  1 Oct 2014 12:39:36 -0700 (PDT)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D38E81A874A for <softwires@ietf.org>; Wed,  1 Oct 2014 12:39:35 -0700 (PDT)
Received: by mail-lb0-f170.google.com with SMTP id u10so1011041lbd.1 for <softwires@ietf.org>; Wed, 01 Oct 2014 12:39:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=Y7AXDyD401wBOTCtOharPBS17MUGRtF5fJyyApxqKWY=; b=qzSggNvmEglgnWhBytXrHwzG+OQatPYPB0ScjlRDhQRy9eJmVNxGkCwaNq9XQOL45Y p7ww6nkWlyIvhP8ORa8neR0o8deFmH9KuPaP66Yb/a3IamAbgFA9LOdbm1/XJCQKkwJR wajHgwoRQl6pgvQEbN18D1xMu/EzE1gP5iFOH6ApnudiFWzEakD8j6PttdvfSdj4NS5I YqIzS/M37E1qqM913io9Yi+ZCvuHi86rub4PtuK5fVqT8Uzyd2sA9vAwVepqk9kbRskz ASn+iIN6XPbgnDGLJ+wjP43mdVDj6TFXBA6JBj2W24GyJHsde4OSE1E3iNrA3+aE8ivj wPTQ==
MIME-Version: 1.0
X-Received: by 10.112.150.106 with SMTP id uh10mr53839843lbb.11.1412192373865;  Wed, 01 Oct 2014 12:39:33 -0700 (PDT)
Received: by 10.114.77.37 with HTTP; Wed, 1 Oct 2014 12:39:33 -0700 (PDT)
In-Reply-To: <DA6D7597-362F-4DD8-AD5F-6C1B31ACD805@gmx.com>
References: <CAC8QAcdtsmG=cYqpTt-spTrvCLFWLFi7EYRzgRt7MjNZaTNfMw@mail.gmail.com> <DA6D7597-362F-4DD8-AD5F-6C1B31ACD805@gmx.com>
Date: Wed, 1 Oct 2014 14:39:33 -0500
Message-ID: <CAC8QAce0KOMz=TxkaPm50H+wQ1d5R_FheEyhenpQ3QD0C4HxHA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ian Farrer <ianfarrer@gmx.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/BCQMffFu-DFFwvqc6PFgSyFd4CA
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] lw4o6 question
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Oct 2014 19:39:37 -0000

Hi Ian,

On Wed, Oct 1, 2014 at 4:32 AM, Ian Farrer <ianfarrer@gmx.com> wrote:
> HI Behcet,
>
> Thanks for pointing that out. Actually, I think that RFC2983 is the bette=
r reference, instead of RFC4213. As RFC2983 is informational, then this wou=
ld move to being an informative reference (the current wording doesn=E2=80=
=99t use normative language anyway).

Yes, I agree, the tunnel part of RFC 2983 is better.
No offense to Erik.


Regards,

Behcet
>
> Would that work?
>
> Cheers,
> Ian
>
>
> On 24 Sep 2014, at 22:46, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:
>
>> Hi all,
>>
>> I noticed that RFC 4213 is referenced in both Section 5.2 and 6.2 regard=
ing:
>> Covering tunneling and traffic  class mapping between IPv4 and IPv6
>>
>> I am curious as to why RFC 4213 which only deals with tunneling IPv6
>> packets in IPv4 would be relevant to lw4o6?
>>
>> Regards,
>>
>> Behcet
>>
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>


From nobody Sun Oct  5 20:29:56 2014
Return-Path: <sunlinhui@bupt.edu.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB3F21A1A20 for <softwires@ietfa.amsl.com>; Sun,  5 Oct 2014 20:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.013
X-Spam-Level: 
X-Spam-Status: No, score=0.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_SORBS_HTTP=0.001, RCVD_IN_SORBS_SOCKS=1.927, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anHXQ7kYOJ_z for <softwires@ietfa.amsl.com>; Sun,  5 Oct 2014 20:29:52 -0700 (PDT)
Received: from mx2.bupt.edu.cn (mx2.bupt.edu.cn [211.68.68.3]) by ietfa.amsl.com (Postfix) with ESMTP id 168B41A1A14 for <softwires@ietf.org>; Sun,  5 Oct 2014 20:29:51 -0700 (PDT)
Received: from SDWM-20131107EC (unknown [166.111.68.233]) by mx2.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 5125B19F35F; Mon,  6 Oct 2014 11:29:49 +0800 (HKT)
Date: Mon, 6 Oct 2014 11:30:47 +0800
From: "sunlinhui@bupt.edu.cn" <sunlinhui@bupt.edu.cn>
To: draft-ietf-softwire-multicast-prefix-option <draft-ietf-softwire-multicast-prefix-option@tools.ietf.org>
X-Priority: 3
X-GUID: DCA9F1BD-BAC6-4DE3-A8DA-4ED934840DFA
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 140[cn]
Mime-Version: 1.0
Message-ID: <2014100611304706320817@bupt.edu.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart481542058760_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/jvu_uypaw04C5sqgHtwDrfriWzQ
Cc: softwires <softwires@ietf.org>
Subject: [Softwires] Comments on draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 06 Oct 2014 03:29:54 -0000

This is a multi-part message in MIME format.

------=_001_NextPart481542058760_=----
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: base64

IEhpIGF1dGhvcnMsDQogSaGvdmUgc3BlbnQgc29tZSB0aW1lIG9uIHJlYWRpbmcgdGhpcyBkb2N1
bWVudCBhbmQgSSB0aGluayBpdCBpcyBhIGdvb2QgcGllY2Ugb2Ygd29yayB0byBkZWZpbmUgYSBu
ZXcgREhDUHY2IG9wdGlvbiB0byBjYXJyeSB0aGUgSVB2NiBwcmVmaXhlcy4NCiANCiBIZXJlIGFy
ZSBzZXZlcmFsIGNvbW1lbnRzLg0KDQogMS4gICAgICAgQ291bGQgeW91IHBsZWFzZSBleHBsYWlu
IHdoeSB0aGUgoa5ESENQdjYgc2VydmVyIHN1cHBvcnRpbmcgT1BUSU9OX1Y2X1BSRUZJWDY0IHNo
b3VsZCBiZSBjb25maWd1cmVkIHdpdGggVV9QUkVGSVg2NCBhbmQgYXQgbGVhc3Qgb25lIEFTTV9Q
UkVGWDY0IG9yIG9uZSAgICAgU1NNX1BSRUZJWDY0oa8gaW4gc2VjdGlvbiA0Pw0KIFRoaXMgc3Rh
dGVtZW50IGNvbmZ1c2VzIG1lIGJlY2F1c2Ugd2hlbiB0aGUgQVNNIG1vZGUgaXMgc3VwcG9ydGVk
LCB0aGVyZSBpcyBubyBuZWVkIHRvIGNvbmZpZ3VyZSB0aGUgVV9QUkVGSVg2NC4NCiANCiAyLiAg
ICAgICBJIGRvIG5vdCByZWFsbHkgdW5kZXJzdGFuZCB0aGUgZm9sbG93aW5nIHBhcnQgaW4gc2Vj
dGlvbiA0Lg0KICdXaGVuIEFTTV9QUkVGSVg2NCBhbmQgU1NNX1BSRUZJWDY0IGFyZSBjb25maWd1
cmVkLCB0aGUgbGVuZ3RoIG9mIHRoZXNlIHByZWZpeGVzIG11c3QgYmUgLzk2LicNCiAgWW91IGhh
dmUgbWVudGlvbmVkIGluIHRoZSBzZWN0aW9uIDMgdGhhdCB0aG9zZSBwcmVmaXhlcyBhcmUgbGlr
ZWx5IHRvIGJlIC85NiBub3QgbXVzdCBiZS4gQ291bGQgeW91IGRvIG1lIGEgZmF2b3IgdG8gZXhw
bGFpbiBpdCBtb3JlIHNwZWNpZmljYWxseT8NCiANCiAzLiAgICAgICBXb3VsZCB5b3UgcGxlYXNl
IGRlc2NyaWJlIHRoZSBmb2xsb3dpbmcgcGFydCBpbiBzZWN0aW9uIDUgaW4gZGV0YWlsPw0KICdp
ZiBib3RoIFNTTSBhbmQgQVNNIG1vZGVzIGFyZSBzdXBwb3J0ZWQnDQogVGhlIG1vZGVzIGFib3Zl
IGFyZSBzdXBwb3J0ZWQgYnkgdGhlIHNlcnZlciBvciB0aGUgY2xpZW50Pw0KIA0KIDQuICAgICAg
IEl0IHNlZW1zIHRoYXQgdGhlcmUgaXMgbm90IGEgY2xlYXIgcGFydCB0aGF0IGluZGljYXRpbmcg
d2hpY2ggREhDUHY2IG1lc3NhZ2Ugd2lsbCBjYXJyeSB0aGUgbmV3IERIQ1B2NiBvcHRpb24uIERv
IHlvdSB0aGluayBpdCBpcyBtb3JlIGFwcHJvcHJpYXRlIHRvIGFkZCBhIHNlcGFyYXRlIHBhcnQg
dG8gZGlzY3VzcyB0aGlzIGlzc3VlIGVzcGVjaWFsbHkgd2hlbiB0aGUgY2xpZW50IGlzIGF0IHRo
ZSBESENQIHJlbmV3IHN0YWdlPw0KIA0KIDUuICAgICAgIEkgYWxzbyBmaW5kIHRoYXQgdGhlcmUg
aXMgYSBzcGVsbGluZyBtaXN0YWtlIGluIHRoZSBmb2xsb3dpbmcgcGFydCBpbiBzZWN0aW9uIDUu
DQogJ3RoZSBQdjQgbXVsdGljYXN0IGFkZHJlc3MgaXMgaW5zZXJ0ZWQgaW4gdGhlIGxhc3QgMzIg
Yml0cyBvZiB0aGUgSVB2NC1lbWJlZGRlZCBJUHY2IG11bHRpY2FzdCBhZGRyZXNzLicNCiAgV2hl
cmUgdGhlIHNlY29uZCB3b3JkIHNob3VsZCBiZSAnSVB2NCcuDQogDQogQmVzdCByZWdhcmRzLA0K
IExpbmh1aSBTdW4NCg0KDQpzdW5saW5odWlAYnVwdC5lZHUuY24NCg==

------=_001_NextPart481542058760_=----
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DGB2312"><style>body { line-height: 1.5; }body { font-size: 10.5pt; fon=
t-family: =CE=A2=C8=ED=D1=C5=BA=DA; color: rgb(0, 0, 0); line-height: 1.5;=
 }</style></head><body>=0A<div><span></span><div style=3D"font-family: =CE=
=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;Hi authors,</di=
v><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height=
: normal;">&nbsp;I=A1=AFve spent some time on reading this document and I =
think it is a good piece of work to define a new DHCPv6 option to carry th=
e IPv6 prefixes.</div><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA,=
 Tahoma; line-height: normal;">&nbsp;</div><div style=3D"font-family: =CE=
=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;Here are severa=
l comments.</div><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Taho=
ma; line-height: normal;"><br></div><div style=3D"font-family: =CE=A2=C8=
=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;1.&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; Could you please explain why the =A1=AEDHCPv6 server sup=
porting OPTION_V6_PREFIX64 should be configured with U_PREFIX64 and at lea=
st one ASM_PREFX64 or one&nbsp;<span style=3D"background-color: rgba(0, 0,=
 0, 0); font-family: '=CE=A2=C8=ED=D1=C5=BA=DA, Tahoma'; font-size: 10.5pt=
; line-height: 1.5;">&nbsp; &nbsp;&nbsp;</span><span style=3D"font-size: 1=
0.5pt; background-color: window;">SSM_PREFIX64=A1=AF in section 4?</span><=
/div><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-hei=
ght: normal;">&nbsp;This statement confuses me because when the ASM mode i=
s supported, there is no need to configure the U_PREFIX64.</div><div style=
=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&=
nbsp;</div><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; li=
ne-height: normal;">&nbsp;2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I do not =
really understand the following part in section 4.</div><div style=3D"font=
-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;'Wh=
en ASM_PREFIX64 and SSM_PREFIX64 are configured, the length of these prefi=
xes must be /96.'</div><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA=
, Tahoma; line-height: normal;">&nbsp;<span style=3D"background-color: rgb=
a(0, 0, 0, 0); font-family: '=CE=A2=C8=ED=D1=C5=BA=DA, Tahoma'; font-size:=
 10.5pt; line-height: 1.5;">&nbsp;</span><span style=3D"font-size: 10.5pt;=
 background-color: window;">You have mentioned in the section 3 that those=
 prefixes are likely to be /96 not must be. Could you do me a favor to exp=
lain it more specifically?</span></div><div style=3D"font-family: =CE=A2=
=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;</div><div style=
=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&=
nbsp;3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Would you please describe the =
following part in section 5 in detail?</div><div style=3D"font-family: =CE=
=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;'if both SSM an=
d ASM modes are supported'</div><div style=3D"font-family: =CE=A2=C8=ED=D1=
=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;The modes above are support=
ed by the server or the client?</div><div style=3D"font-family: =CE=A2=C8=
=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;</div><div style=3D"f=
ont-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;=
4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It seems that there is not a clear =
part that indicating which DHCPv6 message will carry the new DHCPv6 option=
. Do you think it is more appropriate to add a separate part to discuss th=
is issue especially when the client is at the DHCP renew stage?</div><div =
style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: norma=
l;">&nbsp;</div><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahom=
a; line-height: normal;">&nbsp;5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I al=
so find that there is a spelling mistake in the following part in section =
5.</div><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-=
height: normal;">&nbsp;'the Pv4 multicast address is inserted in the last =
32 bits of the IPv4-embedded IPv6 multicast address.'</div><div style=3D"f=
ont-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;=
 Where the second word should be 'IPv4'.</div><div style=3D"font-family: =
=CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal;">&nbsp;</div><div s=
tyle=3D"font-family: =CE=A2=C8=ED=D1=C5=BA=DA, Tahoma; line-height: normal=
;">&nbsp;Best regards,</div><div style=3D"font-family: =CE=A2=C8=ED=D1=C5=
=BA=DA, Tahoma; line-height: normal;">&nbsp;Linhui Sun</div></div><hr styl=
e=3D"width: 210px; height: 1px;" color=3D"#b5c4df" size=3D"1" align=3D"lef=
t">=0A<div><span><div style=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SI=
ZE: 10pt"><div>sunlinhui@bupt.edu.cn</div></div></span></div>=0A</body></h=
tml>
------=_001_NextPart481542058760_=------


From nobody Sun Oct  5 20:37:59 2014
Return-Path: <sunlinhui@bupt.edu.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5134B1A1B0C for <softwires@ietfa.amsl.com>; Sun,  5 Oct 2014 20:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.712
X-Spam-Level: **
X-Spam-Status: No, score=2.712 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_SORBS_HTTP=0.001, RCVD_IN_SORBS_SOCKS=1.927, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9y4DHZSJ1M-f for <softwires@ietfa.amsl.com>; Sun,  5 Oct 2014 20:37:55 -0700 (PDT)
Received: from mx2.bupt.edu.cn (mx2.bupt.edu.cn [211.68.68.3]) by ietfa.amsl.com (Postfix) with ESMTP id BAA721A1AE4 for <softwires@ietf.org>; Sun,  5 Oct 2014 20:37:53 -0700 (PDT)
Received: from SDWM-20131107EC (unknown [166.111.68.233]) by mx2.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id A13EC19F359; Mon,  6 Oct 2014 11:37:52 +0800 (HKT)
Date: Mon, 6 Oct 2014 11:38:50 +0800
From: "sunlinhui@bupt.edu.cn" <sunlinhui@bupt.edu.cn>
To: draft-hu-softwire-multicast-radius-ext <draft-hu-softwire-multicast-radius-ext@tools.ietf.org>
X-Priority: 3
X-GUID: C2D49BE8-9539-4451-9E4F-EE753DCCB5C6
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 140[cn]
Mime-Version: 1.0
Message-ID: <2014100611385003530021@bupt.edu.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart115820300574_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/-dYbOQEO98G1wPSaBd3drrfWxq4
Cc: softwires <softwires@ietf.org>
Subject: [Softwires] Comments on draft-hu-softwire-multicast-radius-ext
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 06 Oct 2014 03:37:57 -0000

This is a multi-part message in MIME format.

------=_001_NextPart115820300574_=----
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: base64

RGVhciBhdXRob3JzLCANCg0KSSBoYXZlIHJlYWQgdGhpcyBkb2N1bWVudCBhbmQgdGhpbmsgaXQg
aXMgbWVhbmluZ2Z1bCB0byBwcm9wb3NlIGEgbmV3IFJBRElVUyBhdHRyaWJ1dGUgdG8gY2Fycnkg
dGhlIElQdjYgcHJlZml4ZXMgdG9nZXRoZXIgd2l0aCB0aGUgREhDUHY2IG9wdGlvbiBkZWZpbmVk
IGluIGRyYWZ0LWlldGYtc29mdHdpcmUtbXVsdGljYXN0LXByZWZpeC1vcHRpb24tMDcuIA0KDQpI
ZXJlIGFyZSBzb21lIGNvbW1lbnRzIGFib3V0IHRoaXMgZG9jdW1lbnQuIA0KDQoxLiBUaGUgZm9s
bG93aW5nIHBhcmFncmFwaCByZXBlYXRzIHR3aWNlIChzZWN0aW9uIDMgYW5kIHNlY3Rpb24gNCkg
aW4gdGhpcyBkb2N1bWVudC4gDQonSWYgdGhlIE5BUyBkb2VzIG5vdCByZWNlaXZlIHRoZSBNdWx0
aWNhc3QtUHJlZml4ZXMtNjQgYXR0cmlidXRlIGluIHRoZSBBY2Nlc3MtQWNjZXB0IG1lc3NhZ2Us
IGl0IE1BWSBmYWxsIGJhY2sgdG8gYSBwcmUtY29uZmlndXJlZCBkZWZhdWx0IE11bHRpY2FzdC1Q
cmVmaXhlcy02NCwgaWYgYW55LiBJZiB0aGUgTkFTIGRvZXMgbm90IGhhdmUgYW55IHByZS1jb25m
aWd1cmVkLCB0aGUgZGVsaXZlcnkgb2YgbXVsdGljYXN0IHRyYWZmaWMgaXMgbm90IHN1cHBvcnRl
ZC4nIA0KRG8geW91IHRoaW5rIGl0IGlzIG1vcmUgc3VpdGFibGUgdG8gcmVtb3ZlIHRoZSByZXBl
YXRlZCBvbmUgaW4gc2VjdGlvbiAzPyANCg0KMi4gVGhlIGFyY2hpdGVjdHVyZSBvZiB0aGlzIGRv
Y3VtZW50IHNlZW1zIG5vdCB2ZXJ5IHJlYXNvbmFibGUuIERvIHlvdSB0aGluayBpdCBjb3VsZCBi
ZSBvZiBhIGJldHRlciBzdHJ1Y3R1cmU/IEhlcmUgYXJlIG15IHN1Z2dlc3Rpb25zLiANCmEpIFRo
ZSBzZWN0aW9uIDQgaXMgaW50ZW5kZWQgdG8gc3BlY2lmeSB0aGUgbmV3IFJBRElVUyBhdHRyaWJ1
dGUsIGl0IHNlZW1zIHRoYXQgdGhlIG1vc3QgY29udGVudCBvZiB0aGUgc2VjdGlvbiA0LjEgaXMg
ZGVzY3JpYmluZyB0aGUgUkFESVVTIGNsaWVudCBiZWhhdmlvci4gRG8geW91IHRoaW5rIGl0IGlz
IGFwcHJvcHJpYXRlIHRvIHRyZWF0IHRoaXMgcGFydCBhcyBhIHNlcGFyYXRlIHNlY3Rpb24gY2Fs
bGVkIHRoZSBDbGllbnQgQmVoYXZpb3IuIA0KYikgQW5kIEkgdGhpbmsgdGhlIHNlcXVlbmNlIG9m
IHRoZSBzZWN0aW9ucyBjb3VsZCBiZSBtb2RpZmllZCB0byBiZWNvbWUgYmV0dGVyIG9yZ2FuaXpl
ZC4gVGhlIHNlY3Rpb24gUkFESVVTIEF0dHJpYnV0ZSBjb3VsZCBiZSBpbnRyb2R1Y2VkIGZpcnN0
LCB0aGVuIHRoZSBzZWN0aW9uIENsaWVudCBCZWhhdmlvciB3b3VsZCBiZSBkaXNjdXNzZWQgbGF0
ZXIuIFdoaWxlIHRoZSBNdWx0aWNhc3QtUHJlZml4ZXMtNjQgQ29uZmlndXJhdGlvbiB3aXRoIFJB
RElVUyBhbmQgREhDUHY2IHNlY3Rpb24gaXMgbW9yZSBhcHByb3ByaWF0ZSB0byBsb2NhdGUgaW4g
dGhlIHJlYXIgb2YgdGhvc2UgdHdvIHNlY3Rpb25zLiANCg0KMy4gVGhlIKGuREhDUHY2IEFkdmVy
dGlzZW1lbnShryBpbiBGaWd1cmUgMSwyIGNvdWxkIGJlIG1vZGlmaWVkIGFzIKGuREhDUHY2IEFk
dmVydGlzZaGvIGluIGEgbW9yZSBzdGFuZGFyZGl6ZWQgd2F5IGFjY29yZGluZyB0byB0aGUgUkZD
IDMzMTUuIA0KDQo0LiBUaGVyZSBzZWVtcyB0byBiZSBhIGNvbmZsaWN0IGJldHdlZW4gdGhlIGZp
Z3VyZSAxIGFuZCBpdHMgY29ycmVzcG9uZGluZyBkZXNjcmlwdGlvbi4gDQpGcm9tIHRoZSBGaWd1
cmUgMSwgd2UgY2FuIGNvbmNsdWRlIHRoYXQgdGhlIERIQ1B2NiBBZHZlcnRpc2UgbWVzc2FnZSBj
YXJyaWVzIHRoZSBESENQdjYgT1BUSU9OX1BSRUZJWDY0IG9wdGlvbi4gDQpIb3dldmVyLCBpZiB3
ZSByZWZlciB0byB0aGUgY29udGVudCwgaXQgc3RhdGVzIHRoYXQgoa50aGUgTkFTIFNIQUxMIHVz
ZSB0aGUgcHJlZml4ZXMgcmV0dXJuZWQgaW4gdGhlIFJBRElVUyBNdWx0aWNhc3QtUHJlZml4ZXMt
NjQgYXR0cmlidXRlIHRvIHBvcHVsYXRlIHRoZSBESENQdjYgT1BUSU9OX1BSRUZJWDY0IG9wdGlv
biBpbiB0aGUgREhDUHY2IHJlcGx5IG1lc3NhZ2WhryBpbiBzZWN0aW9uIDMuIA0KRG8geW91IHRo
aW5rIGl0IGNvdWxkIGJlIGJldHRlciB0byBrZWVwIHRoZSBjb25zaXN0ZW5jZSBiZXR3ZWVuIHRo
ZSBmaWd1cmUgYW5kIGl0cyBkZXNjcmlwdGlvbi4gDQoNCjUuIENvdWxkIHlvdSBwbGVhc2UgZXhw
bGFpbiB3aHkgdGhlIERIQ1B2NiBSZXF1ZXN0IG1lc3NhZ2UgaW4gdGhlIEZpZ3VyZSAyIGRvZXMg
bm90IGNhcnJ5IGEgREhDUHY2IE9QVElPTl9QUkVGSVg2ND8gDQoNCjYuIERvIHlvdSB0aGluayBp
dCBpcyBuZWNlc3NhcnkgdG8gYWRkIGEgc2VwYXJhdGUgcGFyYWdyYXBoIHRoYXQgZGVmaW5lcyBo
b3cgdGhlIE5BUyB3aWxsIGNvbW11bmljYXRlIHdpdGggdGhlIEFBQSBzZXJ2ZXIgd2hlbiB0aGUg
bUI0IGlzIGF0IGl0cyBESENQIHJlbmV3IHN0YWdlIHRvIG1ha2UgdGhlIGRvY3VtZW50IG1vcmUg
Y29tcHJlaGVuc2l2ZT8gDQoNCkJlc3QgcmVnYXJkcywgDQpMaW5odWkgU3VuIA0KDQoNCg0KDQpz
dW5saW5odWlAYnVwdC5lZHUuY24NCg==

------=_001_NextPart115820300574_=----
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DGB2312"><style>body { line-height: 1.5; }body { font-size: 10.5pt; fon=
t-family: =CE=A2=C8=ED=D1=C5=BA=DA; color: rgb(0, 0, 0); line-height: 1.5;=
 }</style></head><body>=0A<div><span></span><span style=3D"background-colo=
r: rgba(0, 0, 0, 0);">Dear authors,=0A<br>=0A<br>I have read this document=
 and think it is meaningful to propose a new RADIUS attribute to carry the=
 IPv6 prefixes together with the DHCPv6 option defined in draft-ietf-softw=
ire-multicast-prefix-option-07.=0A<br>=0A<br>Here are some comments about =
this document.=0A<br>=0A<br>1.	The following paragraph repeats twice (sect=
ion 3 and section 4) in this document.=0A<br>'If the NAS does not receive =
the Multicast-Prefixes-64 attribute in the Access-Accept message, it MAY f=
all back to a pre-configured default Multicast-Prefixes-64, if any.  If th=
e NAS does not have any pre-configured, the delivery of multicast traffic =
is not supported.'=0A<br>Do you think it is more suitable to remove the re=
peated one in section 3?=0A<br>=0A<br>2.	The architecture of this document=
 seems not very reasonable. Do you think it could be of a better structure=
? Here are my suggestions.=0A<br>a)	The section 4 is intended to specify t=
he new RADIUS attribute, it seems that the most content of the section 4.1=
 is describing the RADIUS client behavior. Do you think it is appropriate =
to treat this part as a separate section called the Client Behavior.=0A<br=
>b)	And I think the sequence of the sections could be modified to become b=
etter organized. The section RADIUS Attribute could be introduced first, t=
hen the section Client Behavior would be discussed later. While the Multic=
ast-Prefixes-64 Configuration with RADIUS and DHCPv6 section is more appro=
priate to locate in the rear of those two sections.=0A<br>=0A<br>3.	The =
=A1=AEDHCPv6 Advertisement=A1=AF in Figure 1,2 could be modified as =A1=AE=
DHCPv6 Advertise=A1=AF in a more standardized way according to the RFC 331=
5.=0A<br>=0A<br>4.	There seems to be a conflict between the figure 1 and i=
ts corresponding description. =0A<br>From the Figure 1, we can conclude th=
at the DHCPv6 Advertise message carries the DHCPv6 OPTION_PREFIX64 option.=
 =0A<br>However, if we refer to the content, it states that =A1=AEthe NAS =
SHALL use the prefixes returned in the RADIUS Multicast-Prefixes-64 attrib=
ute to populate the DHCPv6 OPTION_PREFIX64 option in the DHCPv6 reply mess=
age=A1=AF in section 3.=0A<br>Do you think it could be better to keep the =
consistence between the figure and its description.=0A<br>=0A<br>5.	Could =
you please explain why the DHCPv6 Request message in the Figure 2 does not=
 carry a DHCPv6 OPTION_PREFIX64?=0A<br>=0A<br>6.	Do you think it is necess=
ary to add a separate paragraph that defines how the NAS will communicate =
with the AAA server when the mB4 is at its DHCP renew stage to make the do=
cument more comprehensive?=0A<br>=0A<br>Best regards,=0A<br>Linhui Sun=0A<=
br>=0A<br></span></div>=0A<div><br></div><hr style=3D"width: 210px; height=
: 1px;" color=3D"#b5c4df" size=3D"1" align=3D"left">=0A<div><span><div sty=
le=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt"><div>sunlinhui@=
bupt.edu.cn</div></div></span></div>=0A</body></html>
------=_001_NextPart115820300574_=------


From nobody Mon Oct  6 07:56:50 2014
Return-Path: <sunlinhui@bupt.edu.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32DD51A1A36 for <softwires@ietfa.amsl.com>; Sat,  4 Oct 2014 23:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LB5yCVLCJ6u1 for <softwires@ietfa.amsl.com>; Sat,  4 Oct 2014 23:49:22 -0700 (PDT)
Received: from mx2.bupt.edu.cn (mx2.bupt.edu.cn [211.68.68.3]) by ietfa.amsl.com (Postfix) with ESMTP id 39A4D1A1A39 for <softwires@ietf.org>; Sat,  4 Oct 2014 23:49:21 -0700 (PDT)
Received: from SDWM-20131107EC (unknown [114.245.225.244]) by mx2.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 158AA19F359; Sun,  5 Oct 2014 14:49:08 +0800 (HKT)
Date: Sun, 5 Oct 2014 14:50:07 +0800
From: "sunlinhui@bupt.edu.cn" <sunlinhui@bupt.edu.cn>
To: draft-hu-softwire-multicast-radius-ext <draft-hu-softwire-multicast-radius-ext@tools.ietf.org>
X-Priority: 3
X-GUID: E6212CEC-7338-48D5-9353-5CE006054BC0
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 140[cn]
Mime-Version: 1.0
Message-ID: <201410051450023533181@bupt.edu.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart061672613138_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/-QbWcp3z9IaBkG8kF11b8d372x0
X-Mailman-Approved-At: Mon, 06 Oct 2014 07:56:49 -0700
Cc: softwires <softwires@ietf.org>
Subject: [Softwires] Comments on draft-hu-softwire-multicast-radius-ext
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 05 Oct 2014 06:49:25 -0000

This is a multi-part message in MIME format.

------=_001_NextPart061672613138_=----
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: base64

RGVhciBhdXRob3JzLA0KIA0KSSBoYXZlIHJlYWQgdGhpcyBkb2N1bWVudCBhbmQgdGhpbmsgaXQg
aXMgbWVhbmluZ2Z1bCB0byBwcm9wb3NlIGEgbmV3IFJBRElVUyBhdHRyaWJ1dGUgdG8gY2Fycnkg
dGhlIElQdjYgcHJlZml4ZXMgdG9nZXRoZXIgd2l0aCB0aGUgREhDUHY2IG9wdGlvbiBkZWZpbmVk
IGluIGRyYWZ0LWlldGYtc29mdHdpcmUtbXVsdGljYXN0LXByZWZpeC1vcHRpb24tMDcuDQogDQpI
ZXJlIGFyZSBzb21lIGNvbW1lbnRzIGFib3V0IHRoaXMgZG9jdW1lbnQuDQogDQoxLiAgICAgICBU
aGUgZm9sbG93aW5nIHBhcmFncmFwaCByZXBlYXRzIHR3aWNlIChzZWN0aW9uIDMgYW5kIHNlY3Rp
b24gNCkgaW4gdGhpcyBkb2N1bWVudC4NCklmIHRoZSBOQVMgZG9lcyBub3QgcmVjZWl2ZSB0aGUg
TXVsdGljYXN0LVByZWZpeGVzLTY0IGF0dHJpYnV0ZSBpbiB0aGUgQWNjZXNzLUFjY2VwdCBtZXNz
YWdlLCBpdCBNQVkgZmFsbCBiYWNrIHRvIGEgcHJlLWNvbmZpZ3VyZWQgZGVmYXVsdCBNdWx0aWNh
c3QtUHJlZml4ZXMtNjQsIGlmIGFueS4gIElmIHRoZSBOQVMgZG9lcyBub3QgaGF2ZSBhbnkgcHJl
LWNvbmZpZ3VyZWQsIHRoZSBkZWxpdmVyeSBvZiBtdWx0aWNhc3QgdHJhZmZpYyBpcyBub3Qgc3Vw
cG9ydGVkLg0KRG8geW91IHRoaW5rIGl0IGlzIG1vcmUgc3VpdGFibGUgdG8gcmVtb3ZlIHRoZSBy
ZXBlYXRlZCBvbmUgaW4gc2VjdGlvbiAzPw0KIA0KMi4gICAgICAgVGhlIGFyY2hpdGVjdHVyZSBv
ZiB0aGlzIGRvY3VtZW50IHNlZW1zIG5vdCB2ZXJ5IHJlYXNvbmFibGUuIERvIHlvdSB0aGluayBp
dCBjb3VsZCBiZSBvZiBhIGJldHRlciBzdHJ1Y3R1cmU/IEhlcmUgYXJlIG15IHN1Z2dlc3Rpb25z
Lg0KYSkgICAgICAgICBUaGUgc2VjdGlvbiA0IGlzIGludGVuZGVkIHRvIHNwZWNpZnkgdGhlIG5l
dyBSQURJVVMgYXR0cmlidXRlLCBpdCBzZWVtcyB0aGF0IHRoZSBtb3N0IGNvbnRlbnQgb2YgdGhl
IHNlY3Rpb24gNC4xIGlzIGRlc2NyaWJpbmcgdGhlIFJBRElVUyBjbGllbnQgYmVoYXZpb3IuIERv
IHlvdSB0aGluayBpdCBpcyBhcHByb3ByaWF0ZSB0byB0cmVhdCB0aGlzIHBhcnQgYXMgYSBzZXBh
cmF0ZSBzZWN0aW9uIGNhbGxlZCB0aGUgQ2xpZW50IEJlaGF2aW9yLg0KYikgICAgICAgICBBbmQg
SSB0aGluayB0aGUgc2VxdWVuY2Ugb2YgdGhlIHNlY3Rpb25zIGNvdWxkIGJlIG1vZGlmaWVkIHRv
IGJlY29tZSBiZXR0ZXIgb3JnYW5pemVkLiBUaGUgc2VjdGlvbiBSQURJVVMgQXR0cmlidXRlIGNv
dWxkIGJlIGludHJvZHVjZWQgZmlyc3QsIHRoZW4gdGhlIHNlY3Rpb24gQ2xpZW50IEJlaGF2aW9y
IHdvdWxkIGJlIGRpc2N1c3NlZCBsYXRlci4gV2hpbGUgdGhlIE11bHRpY2FzdC1QcmVmaXhlcy02
NCBDb25maWd1cmF0aW9uIHdpdGggUkFESVVTIGFuZCBESENQdjYgc2VjdGlvbiBpcyBtb3JlIGFw
cHJvcHJpYXRlIHRvIGxvY2F0ZSBpbiB0aGUgcmVhciBvZiB0aG9zZSB0d28gc2VjdGlvbnMuDQog
DQozLiAgICAgICBUaGUgoa5ESENQdjYgQWR2ZXJ0aXNlbWVudKGvIGluIEZpZ3VyZSAxLDIgY291
bGQgYmUgbW9kaWZpZWQgYXMgoa5ESENQdjYgQWR2ZXJ0aXNloa8gaW4gYSBtb3JlIHN0YW5kYXJk
aXplZCB3YXkgYWNjb3JkaW5nIHRvIHRoZSBSRkMgMzMxNS4NCiANCjQuICAgICAgIFRoZXJlIHNl
ZW1zIHRvIGJlIGEgY29uZmxpY3QgYmV0d2VlbiB0aGUgZmlndXJlIDEgYW5kIGl0cyBjb3JyZXNw
b25kaW5nIGRlc2NyaXB0aW9uLiANCkZyb20gdGhlIEZpZ3VyZSAxLCB3ZSBjYW4gY29uY2x1ZGUg
dGhhdCB0aGUgREhDUHY2IEFkdmVydGlzZSBtZXNzYWdlIGNhcnJpZXMgdGhlIERIQ1B2NiBPUFRJ
T05fUFJFRklYNjQgb3B0aW9uLiANCkhvd2V2ZXIsIGlmIHdlIHJlZmVyIHRvIHRoZSBjb250ZW50
LCBpdCBzdGF0ZXMgdGhhdCChrnRoZSBOQVMgU0hBTEwgdXNlIHRoZSBwcmVmaXhlcyByZXR1cm5l
ZCBpbiB0aGUgUkFESVVTIE11bHRpY2FzdC1QcmVmaXhlcy02NCBhdHRyaWJ1dGUgdG8gcG9wdWxh
dGUgdGhlIERIQ1B2NiBPUFRJT05fUFJFRklYNjQgb3B0aW9uIGluIHRoZSBESENQdjYgcmVwbHkg
bWVzc2FnZaGvIGluIHNlY3Rpb24gMy4NCkRvIHlvdSB0aGluayBpdCBjb3VsZCBiZSBiZXR0ZXIg
dG8ga2VlcCB0aGUgY29uc2lzdGVuY2UgYmV0d2VlbiB0aGUgZmlndXJlIGFuZCBpdHMgZGVzY3Jp
cHRpb24uDQogDQo1LiAgICAgICBDb3VsZCB5b3UgcGxlYXNlIGV4cGxhaW4gd2h5IHRoZSBESENQ
djYgUmVxdWVzdCBtZXNzYWdlIGluIHRoZSBGaWd1cmUgMiBkb2VzIG5vdCBjYXJyeSBhIERIQ1B2
NiBPUFRJT05fUFJFRklYNjQ/DQogDQo2LiAgICAgICBEbyB5b3UgdGhpbmsgaXQgaXMgbmVjZXNz
YXJ5IHRvIGFkZCBhIHNlcGFyYXRlIHBhcmFncmFwaCB0aGF0IGRlZmluZXMgaG93IHRoZSBOQVMg
d2lsbCBjb21tdW5pY2F0ZSB3aXRoIHRoZSBBQUEgc2VydmVyIHdoZW4gdGhlIG1CNCBpcyBhdCBp
dHMgREhDUCByZW5ldyBzdGFnZSB0byBtYWtlIHRoZSBkb2N1bWVudCBtb3JlIGNvbXByZWhlbnNp
dmU/DQogDQpCZXN0IHJlZ2FyZHMsDQpMaW5odWkgU3VuDQogDQoNCg0KDQpzdW5saW5odWlAYnVw
dC5lZHUuY24NCg==

------=_001_NextPart061672613138_=----
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DGB2312"><style>body { line-height: 1.5; }body { font-size: 10.5pt; fon=
t-family: =CE=A2=C8=ED=D1=C5=BA=DA; color: rgb(0, 0, 0); line-height: 1.5;=
 }</style></head><body>=0A<div><span></span><!--[if gte mso 9]><xml>=0A <o=
:OfficeDocumentSettings>=0A  <o:AllowPNG></o:AllowPNG>=0A </o:OfficeDocume=
ntSettings>=0A</xml><![endif]-->=0A<!--[if gte mso 9]><xml>=0A <w:WordDocu=
ment>=0A  <w:View>Normal</w:View>=0A  <w:Zoom>0</w:Zoom>=0A  <w:TrackMoves=
></w:TrackMoves>=0A  <w:TrackFormatting></w:TrackFormatting>=0A  <w:Punctu=
ationKerning></w:PunctuationKerning>=0A  <w:DrawingGridVerticalSpacing>7.8=
 =B0=F5</w:DrawingGridVerticalSpacing>=0A  <w:DisplayHorizontalDrawingGrid=
Every>0</w:DisplayHorizontalDrawingGridEvery>=0A  <w:DisplayVerticalDrawin=
gGridEvery>2</w:DisplayVerticalDrawingGridEvery>=0A  <w:ValidateAgainstSch=
emas></w:ValidateAgainstSchemas>=0A  <w:SaveIfXMLInvalid>false</w:SaveIfXM=
LInvalid>=0A  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>=0A  <w:Al=
waysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>=0A  <w:DoNotPr=
omoteQF></w:DoNotPromoteQF>=0A  <w:LidThemeOther>EN-US</w:LidThemeOther>=
=0A  <w:LidThemeAsian>ZH-CN</w:LidThemeAsian>=0A  <w:LidThemeComplexScript=
>X-NONE</w:LidThemeComplexScript>=0A  <w:Compatibility>=0A   <w:SpaceForUL=
></w:SpaceForUL>=0A   <w:BalanceSingleByteDoubleByteWidth></w:BalanceSingl=
eByteDoubleByteWidth>=0A   <w:DoNotLeaveBackslashAlone></w:DoNotLeaveBacks=
lashAlone>=0A   <w:ULTrailSpace></w:ULTrailSpace>=0A   <w:DoNotExpandShift=
Return></w:DoNotExpandShiftReturn>=0A   <w:AdjustLineHeightInTable></w:Adj=
ustLineHeightInTable>=0A   <w:BreakWrappedTables></w:BreakWrappedTables>=
=0A   <w:SnapToGridInCell></w:SnapToGridInCell>=0A   <w:WrapTextWithPunct>=
</w:WrapTextWithPunct>=0A   <w:UseAsianBreakRules></w:UseAsianBreakRules>=
=0A   <w:DontGrowAutofit></w:DontGrowAutofit>=0A   <w:SplitPgBreakAndParaM=
ark></w:SplitPgBreakAndParaMark>=0A   <w:EnableOpenTypeKerning></w:EnableO=
penTypeKerning>=0A   <w:DontFlipMirrorIndents></w:DontFlipMirrorIndents>=
=0A   <w:OverrideTableStyleHps></w:OverrideTableStyleHps>=0A   <w:UseFELay=
out></w:UseFELayout>=0A  </w:Compatibility>=0A  <m:mathPr>=0A   <m:mathFon=
t m:val=3D"Cambria Math"></m:mathFont>=0A   <m:brkBin m:val=3D"before"></m=
:brkBin>=0A   <m:brkBinSub m:val=3D"&#45;-"></m:brkBinSub>=0A   <m:smallFr=
ac m:val=3D"off"></m:smallFrac>=0A   <m:dispDef></m:dispDef>=0A   <m:lMarg=
in m:val=3D"0"></m:lMargin>=0A   <m:rMargin m:val=3D"0"></m:rMargin>=0A   =
<m:defJc m:val=3D"centerGroup"></m:defJc>=0A   <m:wrapIndent m:val=3D"1440=
"></m:wrapIndent>=0A   <m:intLim m:val=3D"subSup"></m:intLim>=0A   <m:nary=
Lim m:val=3D"undOvr"></m:naryLim>=0A  </m:mathPr></w:WordDocument>=0A</xml=
><![endif]--><!--[if gte mso 9]><xml>=0A <w:LatentStyles DefLockedState=3D=
"false" DefUnhideWhenUsed=3D"false"=0A  DefSemiHidden=3D"false" DefQFormat=
=3D"false" DefPriority=3D"99"=0A  LatentStyleCount=3D"371">=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"Normal"></w=
:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=
=3D"true" Name=3D"heading 1"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"9" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true"=
 QFormat=3D"true" Name=3D"heading 2"></w:LsdException>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"=0A   UnhideWhenUsed=
=3D"true" QFormat=3D"true" Name=3D"heading 3"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"=0A   UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 4"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"=0A   =
UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 5"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true=
"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 6"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=
=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 7"=
></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" Sem=
iHidden=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"hea=
ding 8"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"9" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=
=3D"heading 9"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Semi=
Hidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"index 1"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenU=
sed=3D"true"=0A   Name=3D"index 2"></w:LsdException>=0A  <w:LsdException L=
ocked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"i=
ndex 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"index 4"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"index 5"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"inde=
x 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"=
true" UnhideWhenUsed=3D"true"=0A   Name=3D"index 7"></w:LsdException>=0A  =
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"tru=
e"=0A   Name=3D"index 8"></w:LsdException>=0A  <w:LsdException Locked=3D"f=
alse" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"index 9"></=
w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" SemiH=
idden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"toc 1"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true=
"=0A   UnhideWhenUsed=3D"true" Name=3D"toc 2"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"=0A   Unhide=
WhenUsed=3D"true" Name=3D"toc 3"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"t=
rue" Name=3D"toc 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"=
toc 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"=
39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"toc 6"></w:Ls=
dException>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidde=
n=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"toc 7"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"=
=0A   UnhideWhenUsed=3D"true" Name=3D"toc 8"></w:LsdException>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"=0A   UnhideW=
henUsed=3D"true" Name=3D"toc 9"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Norm=
al Indent"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidd=
en=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"footnote text"></w:LsdExc=
eption>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhe=
nUsed=3D"true"=0A   Name=3D"annotation text"></w:LsdException>=0A  <w:LsdE=
xception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A  =
 Name=3D"header"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Se=
miHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"footer"></w:LsdExce=
ption>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhen=
Used=3D"true"=0A   Name=3D"index heading"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"35" SemiHidden=3D"true"=0A   UnhideWhen=
Used=3D"true" QFormat=3D"true" Name=3D"caption"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"table of figures"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"enve=
lope address"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiH=
idden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"envelope return"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unhi=
deWhenUsed=3D"true"=0A   Name=3D"footnote reference"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"tr=
ue"=0A   Name=3D"annotation reference"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"line number"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Se=
miHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"page number"></w:Ls=
dException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unhid=
eWhenUsed=3D"true"=0A   Name=3D"endnote reference"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
"=0A   Name=3D"endnote text"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"table =
of authorities"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Sem=
iHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"macro"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUs=
ed=3D"true"=0A   Name=3D"toa heading"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"List"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidde=
n=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List Bullet"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUs=
ed=3D"true"=0A   Name=3D"List Number"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"List 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHid=
den=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List 3"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"List 4"></w:LsdException>=0A  <w:LsdException Locke=
d=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List =
5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tr=
ue" UnhideWhenUsed=3D"true"=0A   Name=3D"List Bullet 2"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"List Bullet 3"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"List Bullet 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List Bullet 5"></=
w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" U=
nhideWhenUsed=3D"true"=0A   Name=3D"List Number 2"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
"=0A   Name=3D"List Number 3"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List N=
umber 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List Number 5"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" Priority=3D"10" QFormat=3D"true=
" Name=3D"Title"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Se=
miHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Closing"></w:LsdExc=
eption>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhe=
nUsed=3D"true"=0A   Name=3D"Signature"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" Priority=3D"1" SemiHidden=3D"true"=0A   UnhideWhenUsed=
=3D"true" Name=3D"Default Paragraph Font"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Na=
me=3D"Body Text"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Se=
miHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Body Text Indent"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"=0A   Name=3D"List Continue"></w:LsdException>=0A  =
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"tru=
e"=0A   Name=3D"List Continue 2"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Lis=
t Continue 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiH=
idden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List Continue 4"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unhi=
deWhenUsed=3D"true"=0A   Name=3D"List Continue 5"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Message Header"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"11" QFormat=3D"true" Name=3D"Subtitle"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenU=
sed=3D"true"=0A   Name=3D"Salutation"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Date"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidde=
n=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Body Text First Indent"></=
w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" U=
nhideWhenUsed=3D"true"=0A   Name=3D"Body Text First Indent 2"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenU=
sed=3D"true"=0A   Name=3D"Note Heading"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Body Text 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Se=
miHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Body Text 3"></w:Ls=
dException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unhid=
eWhenUsed=3D"true"=0A   Name=3D"Body Text Indent 2"></w:LsdException>=0A  =
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"tru=
e"=0A   Name=3D"Body Text Indent 3"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"=
Block Text"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHid=
den=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Hyperlink"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUs=
ed=3D"true"=0A   Name=3D"FollowedHyperlink"></w:LsdException>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"22" QFormat=3D"true" Name=3D"Strong">=
</w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"20" QFo=
rmat=3D"true" Name=3D"Emphasis"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Docu=
ment Map"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidde=
n=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Plain Text"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUse=
d=3D"true"=0A   Name=3D"E-mail Signature"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Na=
me=3D"HTML Top of Form"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Bottom =
of Form"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Normal (Web)"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUs=
ed=3D"true"=0A   Name=3D"HTML Acronym"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"HTML Address"></w:LsdException>=0A  <w:LsdException Locked=3D"false" S=
emiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Cite"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true"=0A   Name=3D"HTML Code"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Na=
me=3D"HTML Definition"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Keyboard=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tru=
e" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Preformatted"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"HTML Sample"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"=
HTML Typewriter"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Se=
miHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Variable"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unh=
ideWhenUsed=3D"true"=0A   Name=3D"Normal Table"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"annotation subject"></w:LsdException>=0A  <w:LsdException Lo=
cked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"No=
 List"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Outline List 1"></w:LsdExce=
ption>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhen=
Used=3D"true"=0A   Name=3D"Outline List 2"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   N=
ame=3D"Outline List 3"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Simple =
1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tr=
ue" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Simple 2"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"Table Simple 3"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Classic 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Classic 2=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tru=
e" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Classic 3"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"Table Classic 4"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Colorful 1"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Colorful=
 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"t=
rue" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Colorful 3"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUse=
d=3D"true"=0A   Name=3D"Table Columns 1"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Nam=
e=3D"Table Columns 2"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Columns =
3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tr=
ue" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Columns 4"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"Table Columns 5"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Grid 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" S=
emiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Grid 2"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unh=
ideWhenUsed=3D"true"=0A   Name=3D"Table Grid 3"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Table Grid 4"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table =
Grid 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Grid 6"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUs=
ed=3D"true"=0A   Name=3D"Table Grid 7"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Grid 8"></w:LsdException>=0A  <w:LsdException Locked=3D"false" S=
emiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table List 1"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unh=
ideWhenUsed=3D"true"=0A   Name=3D"Table List 2"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Table List 3"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table =
List 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table List 5"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUs=
ed=3D"true"=0A   Name=3D"Table List 6"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table List 7"></w:LsdException>=0A  <w:LsdException Locked=3D"false" S=
emiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table List 8"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unh=
ideWhenUsed=3D"true"=0A   Name=3D"Table 3D effects 1"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"t=
rue"=0A   Name=3D"Table 3D effects 2"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table 3D effects 3"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Contem=
porary"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Elegant"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenU=
sed=3D"true"=0A   Name=3D"Table Professional"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A =
  Name=3D"Table Subtle 1"></w:LsdException>=0A  <w:LsdException Locked=3D"=
false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Subt=
le 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D=
"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Web 1"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"Table Web 2"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"=
Table Web 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHi=
dden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Balloon Text"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"Tabl=
e Grid"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Theme"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Place=
holder Text"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priori=
ty=3D"1" QFormat=3D"true" Name=3D"No Spacing"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"60" Name=3D"Light Shading"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Lig=
ht List"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"62" Name=3D"Light Grid"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"63" Name=3D"Medium Shading 1"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" N=
ame=3D"Medium List 1"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"66" Name=3D"Medium List 2"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium =
Grid 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"69" Name=3D"Medium Grid 3"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"70" Name=3D"Dark List"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"=
Colorful List"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"73" Name=3D"Colorful Grid"></w:LsdException>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"60" Name=3D"Light Shading Accent 1"></w:LsdExc=
eption>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light=
 List Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pri=
ority=3D"62" Name=3D"Light Grid Accent 1"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 Accent 1">=
</w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" Nam=
e=3D"Medium Shading 2 Accent 1"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"65" Name=3D"Medium List 1 Accent 1"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Revi=
sion"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"3=
4" QFormat=3D"true"=0A   Name=3D"List Paragraph"></w:LsdException>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"29" QFormat=3D"true" Name=3D"Quo=
te"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"30"=
 QFormat=3D"true"=0A   Name=3D"Intense Quote"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Accent 1"=
></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" Na=
me=3D"Medium Grid 1 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Accent 1"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Gri=
d 3 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"70" Name=3D"Dark List Accent 1"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading Accent 1"></w=
:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" Name=
=3D"Colorful List Accent 1"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"73" Name=3D"Colorful Grid Accent 1"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shad=
ing Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"61" Name=3D"Light List Accent 2"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent 2"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Med=
ium Shading 1 Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" Priority=3D"64" Name=3D"Medium Shading 2 Accent 2"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List =
1 Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"66" Name=3D"Medium List 2 Accent 2"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Accent 2"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D=
"Medium Grid 2 Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"69" Name=3D"Medium Grid 3 Accent 2"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accen=
t 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"71=
" Name=3D"Colorful Shading Accent 2"></w:LsdException>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Accent 2"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Col=
orful Grid Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"60" Name=3D"Light Shading Accent 3"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent 3=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" N=
ame=3D"Light Grid Accent 3"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 Accent 3"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"65" Name=3D"Medium List 1 Accent 3"></w:LsdException>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Accent=
 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"67"=
 Name=3D"Medium Grid 1 Accent 3"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Accent 3"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium =
Grid 3 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"70" Name=3D"Dark List Accent 3"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading Accent 3">=
</w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" Nam=
e=3D"Colorful List Accent 3"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"73" Name=3D"Colorful Grid Accent 3"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shad=
ing Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"61" Name=3D"Light List Accent 4"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent 4"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Med=
ium Shading 1 Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" Priority=3D"64" Name=3D"Medium Shading 2 Accent 4"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List =
1 Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"66" Name=3D"Medium List 2 Accent 4"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Accent 4"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D=
"Medium Grid 2 Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"69" Name=3D"Medium Grid 3 Accent 4"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accen=
t 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"71=
" Name=3D"Colorful Shading Accent 4"></w:LsdException>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Accent 4"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Col=
orful Grid Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"60" Name=3D"Light Shading Accent 5"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent 5=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" N=
ame=3D"Light Grid Accent 5"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 Accent 5"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"65" Name=3D"Medium List 1 Accent 5"></w:LsdException>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Accent=
 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"67"=
 Name=3D"Medium Grid 1 Accent 5"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Accent 5"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium =
Grid 3 Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"70" Name=3D"Dark List Accent 5"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading Accent 5">=
</w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" Nam=
e=3D"Colorful List Accent 5"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"73" Name=3D"Colorful Grid Accent 5"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shad=
ing Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"61" Name=3D"Light List Accent 6"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent 6"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Med=
ium Shading 1 Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" Priority=3D"64" Name=3D"Medium Shading 2 Accent 6"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List =
1 Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"66" Name=3D"Medium List 2 Accent 6"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Accent 6"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D=
"Medium Grid 2 Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"69" Name=3D"Medium Grid 3 Accent 6"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accen=
t 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"71=
" Name=3D"Colorful Shading Accent 6"></w:LsdException>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Accent 6"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Col=
orful Grid Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"19" QFormat=3D"true"=0A   Name=3D"Subtle Emphasis"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" Priority=3D"21" QFormat=3D"t=
rue"=0A   Name=3D"Intense Emphasis"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"31" QFormat=3D"true"=0A   Name=3D"Subtle Refe=
rence"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"=
32" QFormat=3D"true"=0A   Name=3D"Intense Reference"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"33" QFormat=3D"true" Name=3D=
"Book Title"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priori=
ty=3D"37" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"Bibliog=
raphy"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"=
39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=
=3D"TOC Heading"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"41" Name=3D"Plain Table 1"></w:LsdException>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"42" Name=3D"Plain Table 2"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"43" Name=3D"Plain Table =
3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"44" =
Name=3D"Plain Table 4"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"45" Name=3D"Plain Table 5"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" Priority=3D"40" Name=3D"Grid Table Light"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Gri=
d Table 1 Light"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"47" Name=3D"Grid Table 2"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" N=
ame=3D"Grid Table 5 Dark"></w:LsdException>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"51" Name=3D"Grid Table 6 Colorful"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Co=
lorful"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"46"=0A   Name=3D"Grid Table 1 Light Accent 1"></w:LsdException>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accent 1"=
></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Na=
me=3D"Grid Table 3 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accent 1"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table =
5 Dark Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"51"=0A   Name=3D"Grid Table 6 Colorful Accent 1"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=0A   Name=3D"Grid =
Table 7 Colorful Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"46"=0A   Name=3D"Grid Table 1 Light Accent 2"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Gri=
d Table 2 Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"48" Name=3D"Grid Table 3 Accent 2"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accent 2=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" N=
ame=3D"Grid Table 5 Dark Accent 2"></w:LsdException>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"51"=0A   Name=3D"Grid Table 6 Colorful Accent =
2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=
=0A   Name=3D"Grid Table 7 Colorful Accent 2"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"46"=0A   Name=3D"Grid Table 1 Light=
 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"47" Name=3D"Grid Table 2 Accent 3"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accent 3"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Gr=
id Table 4 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"50" Name=3D"Grid Table 5 Dark Accent 3"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"51"=0A   Name=3D"Grid Table=
 6 Colorful Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"52"=0A   Name=3D"Grid Table 7 Colorful Accent 3"></w:LsdExc=
eption>=0A  <w:LsdException Locked=3D"false" Priority=3D"46"=0A   Name=3D"=
Grid Table 1 Light Accent 4"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accent 4"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table =
3 Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"49" Name=3D"Grid Table 4 Accent 4"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark Accent 4"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"51"=0A  =
 Name=3D"Grid Table 6 Colorful Accent 4"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"52"=0A   Name=3D"Grid Table 7 Colorful A=
ccent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"46"=0A   Name=3D"Grid Table 1 Light Accent 5"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accent=
 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"48"=
 Name=3D"Grid Table 3 Accent 5"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accent 5"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Tabl=
e 5 Dark Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"51"=0A   Name=3D"Grid Table 6 Colorful Accent 5"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=0A   Name=3D"Gri=
d Table 7 Colorful Accent 5"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"46"=0A   Name=3D"Grid Table 1 Light Accent 6"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"=
Grid Table 2 Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"48" Name=3D"Grid Table 3 Accent 6"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"50=
" Name=3D"Grid Table 5 Dark Accent 6"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"51"=0A   Name=3D"Grid Table 6 Colorful Acce=
nt 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"5=
2"=0A   Name=3D"Grid Table 7 Colorful Accent 6"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"47" Name=
=3D"List Table 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"48" Name=3D"List Table 3"></w:LsdException>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"49" Name=3D"List Table 4"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5=
 Dark"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"=
51" Name=3D"List Table 6 Colorful"></w:LsdException>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"52" Name=3D"List Table 7 Colorful"></w:LsdExce=
ption>=0A  <w:LsdException Locked=3D"false" Priority=3D"46"=0A   Name=3D"L=
ist Table 1 Light Accent 1"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"47" Name=3D"List Table 2 Accent 1"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table =
3 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"49" Name=3D"List Table 4 Accent 1"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark Accent 1"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"51"=0A  =
 Name=3D"List Table 6 Colorful Accent 1"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"52"=0A   Name=3D"List Table 7 Colorful A=
ccent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"46"=0A   Name=3D"List Table 1 Light Accent 2"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accent=
 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"48"=
 Name=3D"List Table 3 Accent 2"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"49" Name=3D"List Table 4 Accent 2"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Tabl=
e 5 Dark Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"51"=0A   Name=3D"List Table 6 Colorful Accent 2"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=0A   Name=3D"Lis=
t Table 7 Colorful Accent 2"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"46"=0A   Name=3D"List Table 1 Light Accent 3"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"=
List Table 2 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"48" Name=3D"List Table 3 Accent 3"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"50=
" Name=3D"List Table 5 Dark Accent 3"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"51"=0A   Name=3D"List Table 6 Colorful Acce=
nt 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"5=
2"=0A   Name=3D"List Table 7 Colorful Accent 3"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" Priority=3D"46"=0A   Name=3D"List Table 1 Lig=
ht Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priori=
ty=3D"47" Name=3D"List Table 2 Accent 4"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accent 4"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"=
List Table 4 Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"50" Name=3D"List Table 5 Dark Accent 4"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"51"=0A   Name=3D"List Ta=
ble 6 Colorful Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"52"=0A   Name=3D"List Table 7 Colorful Accent 4"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" Priority=3D"46"=0A   Name=
=3D"List Table 1 Light Accent 5"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accent 5"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Tab=
le 3 Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"49" Name=3D"List Table 4 Accent 5"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark Accent 5=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"51"=
=0A   Name=3D"List Table 6 Colorful Accent 5"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"52"=0A   Name=3D"List Table 7 Color=
ful Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"46"=0A   Name=3D"List Table 1 Light Accent 6"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Acc=
ent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"=
48" Name=3D"List Table 3 Accent 6"></w:LsdException>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accent 6"></w:LsdExce=
ption>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List T=
able 5 Dark Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"51"=0A   Name=3D"List Table 6 Colorful Accent 6"></w:LsdExc=
eption>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=0A   Name=3D"=
List Table 7 Colorful Accent 6"></w:LsdException>=0A </w:LatentStyles>=0A<=
/xml><![endif]-->=0A<!--[if gte mso 10]>=0A<style>=0A /* Style Definitions=
 */=0A table.MsoNormalTable=0A	{mso-style-name:=C6=D5=CD=A8=B1=ED=B8=F1;=
=0A	mso-tstyle-rowband-size:0;=0A	mso-tstyle-colband-size:0;=0A	mso-style-=
noshow:yes;=0A	mso-style-priority:99;=0A	mso-style-parent:"";=0A	mso-paddi=
ng-alt:0cm 5.4pt 0cm 5.4pt;=0A	mso-para-margin:0cm;=0A	mso-para-margin-bot=
tom:.0001pt;=0A	mso-pagination:widow-orphan;=0A	font-size:10.5pt;=0A	mso-b=
idi-font-size:11.0pt;=0A	font-family:"Calibri","sans-serif";=0A	mso-ascii-=
font-family:Calibri;=0A	mso-ascii-theme-font:minor-latin;=0A	mso-hansi-fon=
t-family:Calibri;=0A	mso-hansi-theme-font:minor-latin;=0A	mso-bidi-font-fa=
mily:"Times New Roman";=0A	mso-bidi-theme-font:minor-bidi;=0A	mso-font-ker=
ning:1.0pt;}=0A</style>=0A<![endif]-->=0A<!--StartFragment-->=0A<p class=
=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; fon=
t-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US">De=
ar authors,<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"margin=
: 0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font-family: C=
alibri, sans-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>=0A<=
p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; text-align: justi=
fy; font-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN=
-US">I have read this document and think it is=0Ameaningful to propose a n=
ew RADIUS attribute to carry the IPv6 prefixes=0Atogether with the DHCPv6 =
option defined in draft-ietf-softwire-multicast-prefix-option-07.<o:p></o:=
p></span></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; =
text-align: justify; font-size: 10.5pt; font-family: Calibri, sans-serif;"=
><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"MsoNormal=
" style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5p=
t; font-family: Calibri, sans-serif;"><span lang=3D"EN-US">Here are some c=
omments about this document.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal=
" style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5p=
t; font-family: Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:=
p></span></p>=0A<p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0.0=
001pt; text-indent: 21pt; text-align: justify; font-size: 10.5pt; font-fam=
ily: Calibri, sans-serif;"><!--[if !supportLists]--><span lang=3D"EN-US">1=
.<span style=3D"font-size: 7pt; line-height: normal; font-family: 'Times N=
ew Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=0A</span></span><!--[endi=
f]--><span lang=3D"EN-US">The following paragraph repeats=0Atwice (section=
 3 and section 4) in this document.<o:p></o:p></span></p>=0A<p class=3D"Ms=
oNormal" align=3D"left" style=3D"text-align: justify; line-height: 14.4pt;=
 margin: 0cm 0cm 0.0001pt; font-size: 10.5pt; font-family: Calibri, sans-s=
erif;"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-font-family:=0A=CB=CE=CC=E5;mso-font-kerning:0=
pt">If the NAS does not receive the Multicast-Prefixes-64=0Aattribute in t=
he Access-Accept message, it MAY fall back to a pre-configured default=0AM=
ulticast-Prefixes-64, if any.&nbsp; If the=0ANAS does not have any pre-con=
figured, the delivery of multicast traffic is not=0Asupported.<o:p></o:p><=
/span></p>=0A<p class=3D"MsoNormal" align=3D"left" style=3D"text-align: ju=
stify; line-height: 14.4pt; margin: 0cm 0cm 0.0001pt; font-size: 10.5pt; f=
ont-family: Calibri, sans-serif;"><span lang=3D"EN-US">Do you think it is =
more suitable to remove the repeated one in section 3?</span><span lang=3D=
"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;;mso-=
fareast-font-family:=0A=CB=CE=CC=E5;mso-font-kerning:0pt"><o:p></o:p></spa=
n></p>=0A<p class=3D"MsoNormal" align=3D"left" style=3D"text-align: justif=
y; line-height: 14.4pt; margin: 0cm 0cm 0.0001pt; font-size: 10.5pt; font-=
family: Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span=
></p>=0A<p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0.0001pt; t=
ext-indent: 21pt; text-align: justify; font-size: 10.5pt; font-family: Cal=
ibri, sans-serif;"><!--[if !supportLists]--><span lang=3D"EN-US">2.<span s=
tyle=3D"font-size: 7pt; line-height: normal; font-family: 'Times New Roman=
';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=0A</span></span><!--[endif]--><sp=
an lang=3D"EN-US">The architecture of this=0Adocument seems not very reaso=
nable. Do you think it could be of a better=0Astructure? Here are my sugge=
stions.<o:p></o:p></span></p>=0A<p class=3D"MsoListParagraph" style=3D"mar=
gin: 0cm 0cm 0.0001pt; text-indent: 21pt; text-align: justify; font-size: =
10.5pt; font-family: Calibri, sans-serif;"><!--[if !supportLists]--><span =
lang=3D"EN-US">a)<span style=3D"font-size: 7pt; line-height: normal; font-=
family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=0A</span></span><!--[endif]--><span lang=3D"EN-US">The section 4 is int=
ended to=0Aspecify the new RADIUS attribute, it seems that the most conten=
t of the section=0A4.1 is describing the RADIUS client behavior. Do you th=
ink it is appropriate to=0Atreat this part as a separate section called th=
e <b>Client Behavior.</b><o:p></o:p></span></p>=0A<p class=3D"MsoListParag=
raph" style=3D"margin: 0cm 0cm 0.0001pt; text-indent: 21pt; text-align: ju=
stify; font-size: 10.5pt; font-family: Calibri, sans-serif;"><!--[if !supp=
ortLists]--><span lang=3D"EN-US">b)<span style=3D"font-size: 7pt; line-hei=
ght: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=0A</span></span><!--[endif]--><span lang=3D"EN-US">An=
d I think the sequence of the=0Asections could be modified to become bette=
r organized. The section <b>RADIUS Attribute</b> could be introduced=0Afir=
st, then the section <b>Client Behavior </b>would=0Abe discussed later. Wh=
ile the <b>Multicast-Prefixes-64=0AConfiguration with RADIUS and DHCPv6 </=
b>section is more appropriate to locate=0Ain the rear of those two section=
s.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" align=3D"left" style=3D"=
text-align: justify; line-height: 14.4pt; margin: 0cm 0cm 0.0001pt; font-s=
ize: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>=
&nbsp;</o:p></span></p>=0A<p class=3D"MsoListParagraph" align=3D"left" sty=
le=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; text-indent: 21pt; li=
ne-height: 14.4pt; font-size: 10.5pt; font-family: Calibri, sans-serif;"><=
!--[if !supportLists]--><span lang=3D"EN-US">3.<span style=3D"font-size: 7=
pt; line-height: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span></span><!--[endif]--><span lang=3D"EN-US">The =
=A1=AEDHCPv6 Advertisement=A1=AF in Figure 1,2 could be modified as =A1=AE=
DHCPv6=0AAdvertise=A1=AF in a more standardized way according to the RFC 3=
315.<o:p></o:p></span></p>=0A<p class=3D"MsoListParagraph" align=3D"left" =
style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; text-indent: 21pt;=
 line-height: 14.4pt; font-size: 10.5pt; font-family: Calibri, sans-serif;=
"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"MsoListP=
aragraph" align=3D"left" style=3D"margin: 0cm 0cm 0.0001pt; text-align: ju=
stify; text-indent: 21pt; line-height: 14.4pt; font-size: 10.5pt; font-fam=
ily: Calibri, sans-serif;"><!--[if !supportLists]--><span lang=3D"EN-US">4=
.<span style=3D"font-size: 7pt; line-height: normal; font-family: 'Times N=
ew Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><!--[endif]=
--><span lang=3D"EN-US">There seems to be a conflict between the figure 1 =
and its corresponding=0Adescription. <o:p></o:p></span></p>=0A<p class=3D"=
MsoNormal" align=3D"left" style=3D"margin: 0cm 0cm 0.0001pt; text-align: j=
ustify; line-height: 14.4pt; font-size: 10.5pt; font-family: Calibri, sans=
-serif;"><span lang=3D"EN-US">From the Figure 1, we can conclude that the =
DHCPv6 Advertise message=0Acarries the DHCPv6 OPTION_PREFIX64 option. <o:p=
></o:p></span></p>=0A<p class=3D"MsoListParagraph" align=3D"left" style=3D=
"margin: 0cm 0cm 0.0001pt; text-align: justify; text-indent: 21pt; line-he=
ight: 14.4pt; font-size: 10.5pt; font-family: Calibri, sans-serif;"><span =
lang=3D"EN-US">However, if we refer to the content, it states that =A1=AEt=
he NAS SHALL use the=0Aprefixes returned in the RADIUS Multicast-Prefixes-=
64 attribute to populate the=0ADHCPv6 OPTION_PREFIX64 option in the DHCPv6=
 reply message=A1=AF in section 3.<o:p></o:p></span></p>=0A<p class=3D"Mso=
ListParagraph" align=3D"left" style=3D"margin: 0cm 0cm 0.0001pt; text-alig=
n: justify; text-indent: 21pt; line-height: 14.4pt; font-size: 10.5pt; fon=
t-family: Calibri, sans-serif;"><span lang=3D"EN-US">Do you think it could=
 be better to keep the consistence between the figure=0Aand its descriptio=
n.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" align=3D"left" style=3D"=
text-align: justify; line-height: 14.4pt; margin: 0cm 0cm 0.0001pt; font-s=
ize: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>=
&nbsp;</o:p></span></p>=0A<p class=3D"MsoListParagraph" align=3D"left" sty=
le=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; text-indent: 21pt; li=
ne-height: 14.4pt; font-size: 10.5pt; font-family: Calibri, sans-serif;"><=
!--[if !supportLists]--><span lang=3D"EN-US">5.<span style=3D"font-size: 7=
pt; line-height: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span></span><!--[endif]--><span lang=3D"EN-US">Coul=
d you please explain why the DHCPv6 Request message in the Figure 2=0Adoes=
 not carry a DHCPv6 OPTION_PREFIX64?<o:p></o:p></span></p>=0A<p class=3D"M=
soNormal" align=3D"left" style=3D"text-align: justify; line-height: 14.4pt=
; margin: 0cm 0cm 0.0001pt; font-size: 10.5pt; font-family: Calibri, sans-=
serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"Ms=
oListParagraph" align=3D"left" style=3D"margin: 0cm 0cm 0.0001pt; text-ali=
gn: justify; text-indent: 21pt; line-height: 14.4pt; font-size: 10.5pt; fo=
nt-family: Calibri, sans-serif;"><!--[if !supportLists]--><span lang=3D"EN=
-US">6.<span style=3D"font-size: 7pt; line-height: normal; font-family: 'T=
imes New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><!--[=
endif]--><span lang=3D"EN-US">Do you think it is necessary to add a separa=
te paragraph that defines how=0Athe NAS will communicate with the AAA serv=
er when the mB4 is at its DHCP renew=0Astage to make the document more com=
prehensive?<o:p></o:p></span></p>=0A<p class=3D"MsoListParagraph" style=3D=
"margin: 0cm 0cm 0.0001pt; text-align: justify; text-indent: 21pt; font-si=
ze: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>&=
nbsp;</o:p></span></p>=0A<p class=3D"MsoNormal" align=3D"left" style=3D"te=
xt-align: justify; line-height: 14.4pt; margin: 0cm 0cm 0.0001pt; font-siz=
e: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US">Best re=
gards,<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" align=3D"left" style=
=3D"text-align: justify; line-height: 14.4pt; margin: 0cm 0cm 0.0001pt; fo=
nt-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US">L=
inhui Sun<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" align=3D"left" st=
yle=3D"text-align: justify; line-height: 14.4pt; margin: 0cm 0cm 0.0001pt;=
 font-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US=
"><o:p>&nbsp;</o:p></span></p>=0A<!--EndFragment--></div>=0A<div><br></div=
><hr style=3D"width: 210px; height: 1px;" color=3D"#b5c4df" size=3D"1" ali=
gn=3D"left">=0A<div><span><div style=3D"MARGIN: 10px; FONT-FAMILY: verdana=
; FONT-SIZE: 10pt"><div>sunlinhui@bupt.edu.cn</div></div></span></div>=0A<=
/body></html>
------=_001_NextPart061672613138_=------


From nobody Mon Oct  6 07:56:52 2014
Return-Path: <sunlinhui@bupt.edu.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8991A1A39 for <softwires@ietfa.amsl.com>; Sat,  4 Oct 2014 23:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level: 
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gcn3oPMsmsTL for <softwires@ietfa.amsl.com>; Sat,  4 Oct 2014 23:52:32 -0700 (PDT)
Received: from mx2.bupt.edu.cn (mx2.bupt.edu.cn [211.68.68.3]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1DD1A1A36 for <softwires@ietf.org>; Sat,  4 Oct 2014 23:52:32 -0700 (PDT)
Received: from SDWM-20131107EC (unknown [114.245.225.244]) by mx2.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 2824919F359; Sun,  5 Oct 2014 14:52:19 +0800 (HKT)
Date: Sun, 5 Oct 2014 14:53:18 +0800
From: "sunlinhui@bupt.edu.cn" <sunlinhui@bupt.edu.cn>
To: draft-ietf-softwire-multicast-prefix-option <draft-ietf-softwire-multicast-prefix-option@tools.ietf.org>
X-Priority: 3
X-GUID: EECA6E0A-1E11-42EB-B777-B3C2B48C588C
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 140[cn]
Mime-Version: 1.0
Message-ID: <201410051453173368073@bupt.edu.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart128083652604_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/GnNI-pogTKFNLeZ6_2zIVqzSrBM
X-Mailman-Approved-At: Mon, 06 Oct 2014 07:56:49 -0700
Cc: softwires <softwires@ietf.org>
Subject: [Softwires] Comments on draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 05 Oct 2014 06:52:34 -0000

This is a multi-part message in MIME format.

------=_001_NextPart128083652604_=----
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: base64

SGkgYXV0aG9ycywNCkmhr3ZlIHNwZW50IHNvbWUgdGltZSBvbiByZWFkaW5nIHRoaXMgZG9jdW1l
bnQgYW5kIEkgdGhpbmsgaXQgaXMgYSBnb29kIHBpZWNlIG9mIHdvcmsgdG8gZGVmaW5lIGEgbmV3
IERIQ1B2NiBvcHRpb24gdG8gY2FycnkgdGhlIElQdjYgcHJlZml4ZXMuDQogDQpIZXJlIGFyZSBz
ZXZlcmFsIGNvbW1lbnRzLg0KIA0KMS4gICAgICAgQ291bGQgeW91IHBsZWFzZSBleHBsYWluIHdo
eSB0aGUgoa5ESENQdjYgc2VydmVyIHN1cHBvcnRpbmcgT1BUSU9OX1Y2X1BSRUZJWDY0IHNob3Vs
ZCBiZSBjb25maWd1cmVkIHdpdGggVV9QUkVGSVg2NCBhbmQgYXQgbGVhc3Qgb25lIEFTTV9QUkVG
WDY0IG9yIG9uZSBTU01fUFJFRklYNjShryBpbiBzZWN0aW9uIDQ/IA0KVGhpcyBzdGF0ZW1lbnQg
Y29uZnVzZXMgbWUgYmVjYXVzZSB3aGVuIHRoZSBBU00gbW9kZSBpcyBzdXBwb3J0ZWQsIHRoZXJl
IGlzIG5vIG5lZWQgdG8gY29uZmlndXJlIHRoZSBVX1BSRUZJWDY0Lg0KIA0KMi4gICAgICAgSSBk
byBub3QgcmVhbGx5IHVuZGVyc3RhbmQgdGhlIGZvbGxvd2luZyBwYXJ0IGluIHNlY3Rpb24gNC4N
CldoZW4gQVNNX1BSRUZJWDY0IGFuZCBTU01fUFJFRklYNjQgYXJlIGNvbmZpZ3VyZWQsIHRoZSBs
ZW5ndGggb2YgdGhlc2UgcHJlZml4ZXMgbXVzdCBiZSAvOTYuDQpZb3UgaGF2ZSBtZW50aW9uZWQg
aW4gdGhlIHNlY3Rpb24gMyB0aGF0IHRob3NlIHByZWZpeGVzIGFyZSBsaWtlbHkgdG8gYmUgLzk2
IG5vdCBtdXN0IGJlLiBDb3VsZCB5b3UgZG8gbWUgYSBmYXZvciB0byBleHBsYWluIGl0IG1vcmUg
c3BlY2lmaWNhbGx5Pw0KIA0KMy4gICAgICAgV291bGQgeW91IHBsZWFzZSBkZXNjcmliZSB0aGUg
Zm9sbG93aW5nIHBhcnQgaW4gc2VjdGlvbiA1IGluIGRldGFpbD8NCmlmIGJvdGggU1NNIGFuZCBB
U00gbW9kZXMgYXJlIHN1cHBvcnRlZA0KVGhlIG1vZGVzIGFib3ZlIGFyZSBzdXBwb3J0ZWQgYnkg
dGhlIHNlcnZlciBvciB0aGUgY2xpZW50Pw0KIA0KNC4gICAgICAgSXQgc2VlbXMgdGhhdCB0aGVy
ZSBpcyBub3QgYSBjbGVhciBwYXJ0IHRoYXQgaW5kaWNhdGluZyB3aGljaCBESENQdjYgbWVzc2Fn
ZSB3aWxsIGNhcnJ5IHRoZSBuZXcgREhDUHY2IG9wdGlvbi4gRG8geW91IHRoaW5rIGl0IGlzIG1v
cmUgYXBwcm9wcmlhdGUgdG8gYWRkIGEgc2VwYXJhdGUgcGFydCB0byBkaXNjdXNzIHRoaXMgaXNz
dWUgZXNwZWNpYWxseSB3aGVuIHRoZSBjbGllbnQgaXMgYXQgdGhlIERIQ1AgcmVuZXcgc3RhZ2U/
DQogDQo1LiAgICAgICBJIGFsc28gZmluZCB0aGF0IHRoZXJlIGlzIGEgc3BlbGxpbmcgbWlzdGFr
ZSBpbiB0aGUgZm9sbG93aW5nIHBhcnQgaW4gc2VjdGlvbiA1Lg0KdGhlIFB2NCBtdWx0aWNhc3Qg
YWRkcmVzcyBpcyBpbnNlcnRlZCBpbiB0aGUgbGFzdCAzMiBiaXRzIG9mIHRoZSBJUHY0LWVtYmVk
ZGVkIElQdjYgbXVsdGljYXN0IGFkZHJlc3MuDQogICAgICAgIFdoZXJlIHRoZSBzZWNvbmQgd29y
ZCBzaG91bGQgYmUgSVB2NC4NCiANCkJlc3QgcmVnYXJkcywNCkxpbmh1aSBTdW4NCg0KDQoNCnN1
bmxpbmh1aUBidXB0LmVkdS5jbg0K

------=_001_NextPart128083652604_=----
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DGB2312"><style>body { line-height: 1.5; }p { margin-top: 0px; margin-b=
ottom: 0px; }body { font-size: 10.5pt; font-family: =CE=A2=C8=ED=D1=C5=BA=
=DA; color: rgb(0, 0, 0); line-height: 1.5; }</style></head><body>=0A<div>=
<span></span><!--[if gte mso 9]><xml>=0A <o:OfficeDocumentSettings>=0A  <o=
:AllowPNG></o:AllowPNG>=0A </o:OfficeDocumentSettings>=0A</xml><![endif]--=
>=0A<!--[if gte mso 9]><xml>=0A <w:WordDocument>=0A  <w:View>Normal</w:Vie=
w>=0A  <w:Zoom>0</w:Zoom>=0A  <w:TrackMoves></w:TrackMoves>=0A  <w:TrackFo=
rmatting></w:TrackFormatting>=0A  <w:PunctuationKerning></w:PunctuationKer=
ning>=0A  <w:DrawingGridVerticalSpacing>7.8 =B0=F5</w:DrawingGridVerticalS=
pacing>=0A  <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDra=
wingGridEvery>=0A  <w:DisplayVerticalDrawingGridEvery>2</w:DisplayVertical=
DrawingGridEvery>=0A  <w:ValidateAgainstSchemas></w:ValidateAgainstSchemas=
>=0A  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>=0A  <w:IgnoreMixedCon=
tent>false</w:IgnoreMixedContent>=0A  <w:AlwaysShowPlaceholderText>false</=
w:AlwaysShowPlaceholderText>=0A  <w:DoNotPromoteQF></w:DoNotPromoteQF>=0A =
 <w:LidThemeOther>EN-US</w:LidThemeOther>=0A  <w:LidThemeAsian>ZH-CN</w:Li=
dThemeAsian>=0A  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>=
=0A  <w:Compatibility>=0A   <w:SpaceForUL></w:SpaceForUL>=0A   <w:BalanceS=
ingleByteDoubleByteWidth></w:BalanceSingleByteDoubleByteWidth>=0A   <w:DoN=
otLeaveBackslashAlone></w:DoNotLeaveBackslashAlone>=0A   <w:ULTrailSpace><=
/w:ULTrailSpace>=0A   <w:DoNotExpandShiftReturn></w:DoNotExpandShiftReturn=
>=0A   <w:AdjustLineHeightInTable></w:AdjustLineHeightInTable>=0A   <w:Bre=
akWrappedTables></w:BreakWrappedTables>=0A   <w:SnapToGridInCell></w:SnapT=
oGridInCell>=0A   <w:WrapTextWithPunct></w:WrapTextWithPunct>=0A   <w:UseA=
sianBreakRules></w:UseAsianBreakRules>=0A   <w:DontGrowAutofit></w:DontGro=
wAutofit>=0A   <w:SplitPgBreakAndParaMark></w:SplitPgBreakAndParaMark>=0A =
  <w:EnableOpenTypeKerning></w:EnableOpenTypeKerning>=0A   <w:DontFlipMirr=
orIndents></w:DontFlipMirrorIndents>=0A   <w:OverrideTableStyleHps></w:Ove=
rrideTableStyleHps>=0A   <w:UseFELayout></w:UseFELayout>=0A  </w:Compatibi=
lity>=0A  <m:mathPr>=0A   <m:mathFont m:val=3D"Cambria Math"></m:mathFont>=
=0A   <m:brkBin m:val=3D"before"></m:brkBin>=0A   <m:brkBinSub m:val=3D"&#=
45;-"></m:brkBinSub>=0A   <m:smallFrac m:val=3D"off"></m:smallFrac>=0A   <=
m:dispDef></m:dispDef>=0A   <m:lMargin m:val=3D"0"></m:lMargin>=0A   <m:rM=
argin m:val=3D"0"></m:rMargin>=0A   <m:defJc m:val=3D"centerGroup"></m:def=
Jc>=0A   <m:wrapIndent m:val=3D"1440"></m:wrapIndent>=0A   <m:intLim m:val=
=3D"subSup"></m:intLim>=0A   <m:naryLim m:val=3D"undOvr"></m:naryLim>=0A  =
</m:mathPr></w:WordDocument>=0A</xml><![endif]--><!--[if gte mso 9]><xml>=
=0A <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"false"=
=0A  DefSemiHidden=3D"false" DefQFormat=3D"false" DefPriority=3D"99"=0A  L=
atentStyleCount=3D"371">=0A  <w:LsdException Locked=3D"false" Priority=3D"=
0" QFormat=3D"true" Name=3D"Normal"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 1"></w:Ls=
dException>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=
=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 2"=
></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" Sem=
iHidden=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"hea=
ding 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"9" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=
=3D"heading 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"9" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"tru=
e" Name=3D"heading 5"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"9" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=
=3D"true" Name=3D"heading 6"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"9" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true"=
 QFormat=3D"true" Name=3D"heading 7"></w:LsdException>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"=0A   UnhideWhenUsed=
=3D"true" QFormat=3D"true" Name=3D"heading 8"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"=0A   UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 9"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"tr=
ue"=0A   Name=3D"index 1"></w:LsdException>=0A  <w:LsdException Locked=3D"=
false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"index 2"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"=0A   Name=3D"index 3"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A =
  Name=3D"index 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"index 5"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideW=
henUsed=3D"true"=0A   Name=3D"index 6"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"index 7"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHi=
dden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"index 8"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUse=
d=3D"true"=0A   Name=3D"index 9"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"t=
rue" Name=3D"toc 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"=
toc 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"=
39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"toc 3"></w:Ls=
dException>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidde=
n=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"toc 4"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"=
=0A   UnhideWhenUsed=3D"true" Name=3D"toc 5"></w:LsdException>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"=0A   UnhideW=
henUsed=3D"true" Name=3D"toc 6"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"tr=
ue" Name=3D"toc 7"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"39" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"t=
oc 8"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"3=
9" SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"toc 9"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true"=0A   Name=3D"Normal Indent"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A =
  Name=3D"footnote text"></w:LsdException>=0A  <w:LsdException Locked=3D"f=
alse" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"annotation =
text"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D=
"true" UnhideWhenUsed=3D"true"=0A   Name=3D"header"></w:LsdException>=0A  =
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"tru=
e"=0A   Name=3D"footer"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"index headin=
g"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"35" =
SemiHidden=3D"true"=0A   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"=
caption"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"table of figures"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWh=
enUsed=3D"true"=0A   Name=3D"envelope address"></w:LsdException>=0A  <w:Ls=
dException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A=
   Name=3D"envelope return"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"footno=
te reference"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiH=
idden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"annotation reference">=
</w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true"=
 UnhideWhenUsed=3D"true"=0A   Name=3D"line number"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
"=0A   Name=3D"page number"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"endnot=
e reference"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHi=
dden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"endnote text"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWh=
enUsed=3D"true"=0A   Name=3D"table of authorities"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
"=0A   Name=3D"macro"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"toa heading"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"=0A   Name=3D"List"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   N=
ame=3D"List Bullet"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List Number"></w=
:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Un=
hideWhenUsed=3D"true"=0A   Name=3D"List 2"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   N=
ame=3D"List 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Semi=
Hidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List 4"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUs=
ed=3D"true"=0A   Name=3D"List 5"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Lis=
t Bullet 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHid=
den=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List Bullet 3"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWh=
enUsed=3D"true"=0A   Name=3D"List Bullet 4"></w:LsdException>=0A  <w:LsdEx=
ception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   =
Name=3D"List Bullet 5"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List Number 2=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tru=
e" UnhideWhenUsed=3D"true"=0A   Name=3D"List Number 3"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"List Number 4"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"List Number 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"10" QFormat=3D"true" Name=3D"Title"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Closing"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Signature"></=
w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHi=
dden=3D"true"=0A   UnhideWhenUsed=3D"true" Name=3D"Default Paragraph Font"=
></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true=
" UnhideWhenUsed=3D"true"=0A   Name=3D"Body Text"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Body Text Indent"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List=
 Continue"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidd=
en=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List Continue 2"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideW=
henUsed=3D"true"=0A   Name=3D"List Continue 3"></w:LsdException>=0A  <w:Ls=
dException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A=
   Name=3D"List Continue 4"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"List C=
ontinue 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidd=
en=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Message Header"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" Priority=3D"11" QFormat=3D"t=
rue" Name=3D"Subtitle"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Salutation"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"=0A   Name=3D"Date"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   N=
ame=3D"Body Text First Indent"></w:LsdException>=0A  <w:LsdException Locke=
d=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Body =
Text First Indent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Note Heading"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"=0A   Name=3D"Body Text 2"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Body Text 3"></w:LsdException>=0A  <w:LsdException Locked=3D=
"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Body Text=
 Indent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidd=
en=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Body Text Indent 3"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unhi=
deWhenUsed=3D"true"=0A   Name=3D"Block Text"></w:LsdException>=0A  <w:LsdE=
xception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A  =
 Name=3D"Hyperlink"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"FollowedHyperlin=
k"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"22" =
QFormat=3D"true" Name=3D"Strong"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"20" QFormat=3D"true" Name=3D"Emphasis"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWh=
enUsed=3D"true"=0A   Name=3D"Document Map"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   N=
ame=3D"Plain Text"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"E-mail Signature"=
></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true=
" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Top of Form"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"HTML Bottom of Form"></w:LsdException>=0A  <w:LsdEx=
ception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   =
Name=3D"Normal (Web)"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Acronym">=
</w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true"=
 UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Address"></w:LsdException>=0A  =
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"tru=
e"=0A   Name=3D"HTML Cite"></w:LsdException>=0A  <w:LsdException Locked=3D=
"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Code=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tru=
e" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Definition"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"HTML Keyboard"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"HTML Preformatted"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Sample">=
</w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true"=
 UnhideWhenUsed=3D"true"=0A   Name=3D"HTML Typewriter"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"HTML Variable"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Normal Table"></w:LsdException>=0A  <w:LsdException Locked=3D"false" S=
emiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"annotation subject=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tru=
e" UnhideWhenUsed=3D"true"=0A   Name=3D"No List"></w:LsdException>=0A  <w:=
LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Outline List 1"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Outlin=
e List 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidde=
n=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Outline List 3"></w:LsdExc=
eption>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhe=
nUsed=3D"true"=0A   Name=3D"Table Simple 1"></w:LsdException>=0A  <w:LsdEx=
ception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   =
Name=3D"Table Simple 2"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Simple=
 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"t=
rue" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Classic 1"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"Table Classic 2"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Classic 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Classic 4=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tru=
e" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Colorful 1"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"Table Colorful 2"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Nam=
e=3D"Table Colorful 3"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Columns=
 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"t=
rue" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Columns 2"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"Table Columns 3"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Columns 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Columns 5=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"tru=
e" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Grid 1"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"t=
rue"=0A   Name=3D"Table Grid 2"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Tabl=
e Grid 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidde=
n=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Grid 4"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenU=
sed=3D"true"=0A   Name=3D"Table Grid 5"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Grid 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" S=
emiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Grid 7"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unh=
ideWhenUsed=3D"true"=0A   Name=3D"Table Grid 8"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Table List 1"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table =
List 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=
=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table List 3"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUs=
ed=3D"true"=0A   Name=3D"Table List 4"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table List 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" S=
emiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table List 6"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unh=
ideWhenUsed=3D"true"=0A   Name=3D"Table List 7"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=
=0A   Name=3D"Table List 8"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table =
3D effects 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiH=
idden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table 3D effects 2"></=
w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" U=
nhideWhenUsed=3D"true"=0A   Name=3D"Table 3D effects 3"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=
=3D"true"=0A   Name=3D"Table Contemporary"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   N=
ame=3D"Table Elegant"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Professi=
onal"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D=
"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Subtle 1"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUse=
d=3D"true"=0A   Name=3D"Table Subtle 2"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Web 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Se=
miHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=3D"Table Web 2"></w:Ls=
dException>=0A  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Unhid=
eWhenUsed=3D"true"=0A   Name=3D"Table Web 3"></w:LsdException>=0A  <w:LsdE=
xception Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A  =
 Name=3D"Balloon Text"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"39" Name=3D"Table Grid"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true"=0A   Name=
=3D"Table Theme"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Se=
miHidden=3D"true" Name=3D"Placeholder Text"></w:LsdException>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"1" QFormat=3D"true" Name=3D"No Spacin=
g"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" =
Name=3D"Light Shading"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"61" Name=3D"Light List"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"62" Name=3D"Light Grid"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shadi=
ng 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"6=
4" Name=3D"Medium Shading 2"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"65" Name=3D"Medium List 1"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D=
"Medium Grid 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pri=
ority=3D"68" Name=3D"Medium Grid 2"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" Name=
=3D"Colorful Shading"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"72" Name=3D"Colorful List"></w:LsdException>=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid"></w:LsdExcep=
tion>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light S=
hading Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"61" Name=3D"Light List Accent 1"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent 1"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"=
Medium Shading 1 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"64" Name=3D"Medium Shading 2 Accent 1"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium Lis=
t 1 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" SemiH=
idden=3D"true" Name=3D"Revision"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"34" QFormat=3D"true"=0A   Name=3D"List Paragraph=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"29" Q=
Format=3D"true" Name=3D"Quote"></w:LsdException>=0A  <w:LsdException Locke=
d=3D"false" Priority=3D"30" QFormat=3D"true"=0A   Name=3D"Intense Quote"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" Name=
=3D"Medium List 2 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Accent 1"></w:LsdExceptio=
n>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Gri=
d 2 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"69" Name=3D"Medium Grid 3 Accent 1"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 1"></w:Ls=
dException>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"C=
olorful Shading Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"72" Name=3D"Colorful List Accent 1"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Gri=
d Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"60" Name=3D"Light Shading Accent 2"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent 2"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Li=
ght Grid Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"63" Name=3D"Medium Shading 1 Accent 2"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"65" Name=3D"Medium List 1 Accent 2"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Accent 2"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"=
Medium Grid 1 Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" Priority=3D"68" Name=3D"Medium Grid 2 Accent 2"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Ac=
cent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"70" Name=3D"Dark List Accent 2"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"71" Name=3D"Colorful Shading Accent 2"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colo=
rful List Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"73" Name=3D"Colorful Grid Accent 2"></w:LsdException>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Accent=
 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"61"=
 Name=3D"Light List Accent 3"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"62" Name=3D"Light Grid Accent 3"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shadi=
ng 1 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"64" Name=3D"Medium Shading 2 Accent 3"></w:LsdException>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Accent 3=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" N=
ame=3D"Medium List 2 Accent 3"></w:LsdException>=0A  <w:LsdException Locke=
d=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Accent 3"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Gr=
id 2 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"69" Name=3D"Medium Grid 3 Accent 3"></w:LsdException>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 3"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"=
Colorful Shading Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"72" Name=3D"Colorful List Accent 3"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Gri=
d Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"60" Name=3D"Light Shading Accent 4"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent 4"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Li=
ght Grid Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"63" Name=3D"Medium Shading 1 Accent 4"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"65" Name=3D"Medium List 1 Accent 4"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Accent 4"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"=
Medium Grid 1 Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" Priority=3D"68" Name=3D"Medium Grid 2 Accent 4"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Ac=
cent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"70" Name=3D"Dark List Accent 4"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"71" Name=3D"Colorful Shading Accent 4"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colo=
rful List Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"73" Name=3D"Colorful Grid Accent 4"></w:LsdException>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Accent=
 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"61"=
 Name=3D"Light List Accent 5"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"62" Name=3D"Light Grid Accent 5"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shadi=
ng 1 Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"64" Name=3D"Medium Shading 2 Accent 5"></w:LsdException>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Accent 5=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" N=
ame=3D"Medium List 2 Accent 5"></w:LsdException>=0A  <w:LsdException Locke=
d=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Accent 5"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Gr=
id 2 Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"69" Name=3D"Medium Grid 3 Accent 5"></w:LsdException>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 5"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"=
Colorful Shading Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"72" Name=3D"Colorful List Accent 5"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Gri=
d Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"60" Name=3D"Light Shading Accent 6"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent 6"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Li=
ght Grid Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"63" Name=3D"Medium Shading 1 Accent 6"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"65" Name=3D"Medium List 1 Accent 6"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Accent 6"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"=
Medium Grid 1 Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"fa=
lse" Priority=3D"68" Name=3D"Medium Grid 2 Accent 6"></w:LsdException>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Ac=
cent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"70" Name=3D"Dark List Accent 6"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"71" Name=3D"Colorful Shading Accent 6"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colo=
rful List Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"73" Name=3D"Colorful Grid Accent 6"></w:LsdException>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"19" QFormat=3D"true"=0A   Name=
=3D"Subtle Emphasis"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"21" QFormat=3D"true"=0A   Name=3D"Intense Emphasis"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"31" QFormat=3D"=
true"=0A   Name=3D"Subtle Reference"></w:LsdException>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"32" QFormat=3D"true"=0A   Name=3D"Intense Re=
ference"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"33" QFormat=3D"true" Name=3D"Book Title"></w:LsdException>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"37" SemiHidden=3D"true"=0A   UnhideW=
henUsed=3D"true" Name=3D"Bibliography"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"=0A   UnhideWhenUse=
d=3D"true" QFormat=3D"true" Name=3D"TOC Heading"></w:LsdException>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"41" Name=3D"Plain Table 1"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"42" Name=3D"=
Plain Table 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"43" Name=3D"Plain Table 3"></w:LsdException>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"44" Name=3D"Plain Table 4"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"45" Name=3D"Plain Table =
5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"40" =
Name=3D"Grid Table Light"></w:LsdException>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"46" Name=3D"Grid Table 1 Light"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2"></w:=
LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D=
"Grid Table 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"49" Name=3D"Grid Table 4"></w:LsdException>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table =
6 Colorful"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"52" Name=3D"Grid Table 7 Colorful"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"46"=0A   Name=3D"Grid Table 1 Light Accen=
t 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"47=
" Name=3D"Grid Table 2 Accent 1"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accent 1"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Tab=
le 4 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"50" Name=3D"Grid Table 5 Dark Accent 1"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" Priority=3D"51"=0A   Name=3D"Grid Table 6 Col=
orful Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pri=
ority=3D"52"=0A   Name=3D"Grid Table 7 Colorful Accent 1"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"46"=0A   Name=3D"Grid T=
able 1 Light Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"47" Name=3D"Grid Table 2 Accent 2"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"49=
" Name=3D"Grid Table 4 Accent 2"></w:LsdException>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark Accent 2"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"51"=0A   Name=
=3D"Grid Table 6 Colorful Accent 2"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"52"=0A   Name=3D"Grid Table 7 Colorful Accent=
 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"46"=
=0A   Name=3D"Grid Table 1 Light Accent 3"></w:LsdException>=0A  <w:LsdExc=
eption Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accent 3"></w=
:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Name=
=3D"Grid Table 3 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"49" Name=3D"Grid Table 4 Accent 3"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5=
 Dark Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Pri=
ority=3D"51"=0A   Name=3D"Grid Table 6 Colorful Accent 3"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=0A   Name=3D"Grid T=
able 7 Colorful Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"46"=0A   Name=3D"Grid Table 1 Light Accent 4"></w:LsdEx=
ception>=0A  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid=
 Table 2 Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"48" Name=3D"Grid Table 3 Accent 4"></w:LsdException>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accent 4"=
></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" Na=
me=3D"Grid Table 5 Dark Accent 4"></w:LsdException>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"51"=0A   Name=3D"Grid Table 6 Colorful Accent 4=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=
=0A   Name=3D"Grid Table 7 Colorful Accent 4"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"46"=0A   Name=3D"Grid Table 1 Light=
 Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"47" Name=3D"Grid Table 2 Accent 5"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accent 5"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Gr=
id Table 4 Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"50" Name=3D"Grid Table 5 Dark Accent 5"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"51"=0A   Name=3D"Grid Table=
 6 Colorful Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"52"=0A   Name=3D"Grid Table 7 Colorful Accent 5"></w:LsdExc=
eption>=0A  <w:LsdException Locked=3D"false" Priority=3D"46"=0A   Name=3D"=
Grid Table 1 Light Accent 6"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accent 6"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table =
3 Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"49" Name=3D"Grid Table 4 Accent 6"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark Accent 6"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"51"=0A  =
 Name=3D"Grid Table 6 Colorful Accent 6"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"52"=0A   Name=3D"Grid Table 7 Colorful A=
ccent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"46" Name=3D"List Table 1 Light"></w:LsdException>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"47" Name=3D"List Table 2"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"49" N=
ame=3D"List Table 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"50" Name=3D"List Table 5 Dark"></w:LsdException>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Colorful"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"52" Name=
=3D"List Table 7 Colorful"></w:LsdException>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"46"=0A   Name=3D"List Table 1 Light Accent 1"></w:LsdE=
xception>=0A  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Lis=
t Table 2 Accent 1"></w:LsdException>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"48" Name=3D"List Table 3 Accent 1"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accent 1=
"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" N=
ame=3D"List Table 5 Dark Accent 1"></w:LsdException>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"51"=0A   Name=3D"List Table 6 Colorful Accent =
1"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=
=0A   Name=3D"List Table 7 Colorful Accent 1"></w:LsdException>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"46"=0A   Name=3D"List Table 1 Light=
 Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"47" Name=3D"List Table 2 Accent 2"></w:LsdException>=0A  <w:LsdExcepti=
on Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accent 2"></w:Lsd=
Exception>=0A  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Li=
st Table 4 Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"50" Name=3D"List Table 5 Dark Accent 2"></w:LsdException>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"51"=0A   Name=3D"List Table=
 6 Colorful Accent 2"></w:LsdException>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"52"=0A   Name=3D"List Table 7 Colorful Accent 2"></w:LsdExc=
eption>=0A  <w:LsdException Locked=3D"false" Priority=3D"46"=0A   Name=3D"=
List Table 1 Light Accent 3"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"47" Name=3D"List Table 2 Accent 3"></w:LsdException=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table =
3 Accent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"49" Name=3D"List Table 4 Accent 3"></w:LsdException>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark Accent 3"><=
/w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"51"=0A  =
 Name=3D"List Table 6 Colorful Accent 3"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"52"=0A   Name=3D"List Table 7 Colorful A=
ccent 3"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"46"=0A   Name=3D"List Table 1 Light Accent 4"></w:LsdException>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accent=
 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"48"=
 Name=3D"List Table 3 Accent 4"></w:LsdException>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"49" Name=3D"List Table 4 Accent 4"></w:LsdExcepti=
on>=0A  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Tabl=
e 5 Dark Accent 4"></w:LsdException>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"51"=0A   Name=3D"List Table 6 Colorful Accent 4"></w:LsdExcept=
ion>=0A  <w:LsdException Locked=3D"false" Priority=3D"52"=0A   Name=3D"Lis=
t Table 7 Colorful Accent 4"></w:LsdException>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"46"=0A   Name=3D"List Table 1 Light Accent 5"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"=
List Table 2 Accent 5"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"48" Name=3D"List Table 3 Accent 5"></w:LsdException>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"50=
" Name=3D"List Table 5 Dark Accent 5"></w:LsdException>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"51"=0A   Name=3D"List Table 6 Colorful Acce=
nt 5"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"5=
2"=0A   Name=3D"List Table 7 Colorful Accent 5"></w:LsdException>=0A  <w:L=
sdException Locked=3D"false" Priority=3D"46"=0A   Name=3D"List Table 1 Lig=
ht Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"false" Priori=
ty=3D"47" Name=3D"List Table 2 Accent 6"></w:LsdException>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accent 6"></w:L=
sdException>=0A  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"=
List Table 4 Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"50" Name=3D"List Table 5 Dark Accent 6"></w:LsdException>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"51"=0A   Name=3D"List Ta=
ble 6 Colorful Accent 6"></w:LsdException>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"52"=0A   Name=3D"List Table 7 Colorful Accent 6"></w:Lsd=
Exception>=0A </w:LatentStyles>=0A</xml><![endif]-->=0A<!--[if gte mso 10]=
>=0A<style>=0A /* Style Definitions */=0A table.MsoNormalTable=0A	{mso-sty=
le-name:=C6=D5=CD=A8=B1=ED=B8=F1;=0A	mso-tstyle-rowband-size:0;=0A	mso-tst=
yle-colband-size:0;=0A	mso-style-noshow:yes;=0A	mso-style-priority:99;=0A	=
mso-style-parent:"";=0A	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;=0A	mso-para-m=
argin:0cm;=0A	mso-para-margin-bottom:.0001pt;=0A	mso-pagination:widow-orph=
an;=0A	font-size:10.5pt;=0A	mso-bidi-font-size:11.0pt;=0A	font-family:"Cal=
ibri","sans-serif";=0A	mso-ascii-font-family:Calibri;=0A	mso-ascii-theme-f=
ont:minor-latin;=0A	mso-hansi-font-family:Calibri;=0A	mso-hansi-theme-font=
:minor-latin;=0A	mso-bidi-font-family:"Times New Roman";=0A	mso-bidi-theme=
-font:minor-bidi;=0A	mso-font-kerning:1.0pt;}=0A</style>=0A<![endif]-->=0A=
<!--StartFragment-->=0A<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0=
001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, sans-=
serif;"><span lang=3D"EN-US">Hi authors,<o:p></o:p></span></p>=0A<p class=
=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; fon=
t-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US">I=
=A1=AFve spent some time on reading this=0Adocument and I think it is a go=
od piece of work to define a new DHCPv6 option=0Ato carry the IPv6 prefixe=
s.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm=
 0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, s=
ans-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>=0A<p class=
=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; fon=
t-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US">He=
re are several comments.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" st=
yle=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5pt; f=
ont-family: Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></=
span></p>=0A<p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0.0001p=
t; text-indent: 21pt; text-align: justify; font-size: 10.5pt; font-family:=
 Calibri, sans-serif;"><!--[if !supportLists]--><span lang=3D"EN-US">1.<sp=
an style=3D"font-size: 7pt; line-height: normal; font-family: 'Times New R=
oman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=0A</span></span><!--[endif]--=
><span lang=3D"EN-US">Could you please explain why=0Athe =A1=AEDHCPv6 serv=
er supporting OPTION_V6_PREFIX64 should be configured with=0AU_PREFIX64 an=
d at least one ASM_PREFX64 or one SSM_PREFIX64=A1=AF in section 4? <o:p></=
o:p></span></p>=0A<p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0=
.0001pt; text-indent: 21pt; text-align: justify; font-size: 10.5pt; font-f=
amily: Calibri, sans-serif;"><span lang=3D"EN-US">This statement confuses =
me because when the ASM mode is=0Asupported, there is no need to configure=
 the U_PREFIX64.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"m=
argin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font-fami=
ly: Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p=
>=0A<p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0.0001pt; text-=
indent: 21pt; text-align: justify; font-size: 10.5pt; font-family: Calibri=
, sans-serif;"><!--[if !supportLists]--><span lang=3D"EN-US">2.<span style=
=3D"font-size: 7pt; line-height: normal; font-family: 'Times New Roman';">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=0A</span></span><!--[endif]--><span l=
ang=3D"EN-US">I do not really understand the=0Afollowing part in section 4=
.<o:p></o:p></span></p>=0A<p class=3D"MsoListParagraph" align=3D"left" sty=
le=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; text-indent: 21pt; li=
ne-height: 14.4pt; font-size: 10.5pt; font-family: Calibri, sans-serif;"><=
span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Courier Ne=
w&quot;;mso-fareast-font-family:=0A=CB=CE=CC=E5;mso-font-kerning:0pt">When=
 ASM_PREFIX64 and SSM_PREFIX64 are configured, the=0Alength of these prefi=
xes must be /96.<o:p></o:p></span></p>=0A<p class=3D"MsoListParagraph" sty=
le=3D"margin: 0cm 0cm 0.0001pt; text-indent: 21pt; text-align: justify; fo=
nt-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US">Y=
ou have mentioned in the section 3 that those prefixes are=0Alikely to be =
/96 not must be. Could you do me a favor to explain it more=0Aspecifically=
?<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, sa=
ns-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D=
"MsoListParagraph" style=3D"margin: 0cm 0cm 0.0001pt; text-indent: 21pt; t=
ext-align: justify; font-size: 10.5pt; font-family: Calibri, sans-serif;">=
<!--[if !supportLists]--><span lang=3D"EN-US">3.<span style=3D"font-size: =
7pt; line-height: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=0A</span></span><!--[endif]--><span lang=3D"EN-US">W=
ould you please describe the=0Afollowing part in section 5 in detail?<o:p>=
</o:p></span></p>=0A<p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm=
 0.0001pt; text-indent: 21pt; text-align: justify; font-size: 10.5pt; font=
-family: Calibri, sans-serif;"><span lang=3D"EN-US" style=3D"font-size:12.=
0pt;font-family:&quot;Courier New&quot;">if both=0ASSM and ASM modes are s=
upported<o:p></o:p></span></p>=0A<p class=3D"MsoListParagraph" style=3D"ma=
rgin: 0cm 0cm 0.0001pt; text-indent: 21pt; text-align: justify; font-size:=
 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US">The modes=
 above are supported by the server or the client?<o:p></o:p></span></p>=0A=
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; text-align: just=
ify; font-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"E=
N-US"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"MsoListParagraph" style=
=3D"margin: 0cm 0cm 0.0001pt; text-indent: 21pt; text-align: justify; font=
-size: 10.5pt; font-family: Calibri, sans-serif;"><!--[if !supportLists]--=
><span lang=3D"EN-US">4.<span style=3D"font-size: 7pt; line-height: normal=
; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=0A=
</span></span><!--[endif]--><span lang=3D"EN-US">It seems that there is no=
t a=0Aclear part that indicating which DHCPv6 message will carry the new D=
HCPv6=0Aoption. Do you think it is more appropriate to add a separate part=
 to discuss=0Athis issue especially when the client is at the DHCP renew s=
tage?<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0cm =
0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri=
, sans-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>=0A<p clas=
s=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0.0001pt; text-indent: 21p=
t; text-align: justify; font-size: 10.5pt; font-family: Calibri, sans-seri=
f;"><!--[if !supportLists]--><span lang=3D"EN-US">5.<span style=3D"font-si=
ze: 7pt; line-height: normal; font-family: 'Times New Roman';">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=0A</span></span><!--[endif]--><span lang=3D"EN-U=
S">I also find that there is a=0Aspelling mistake in the following part in=
 section 5.<o:p></o:p></span></p>=0A<p class=3D"MsoListParagraph" align=3D=
"left" style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; text-indent=
: 21pt; line-height: 14.4pt; font-size: 10.5pt; font-family: Calibri, sans=
-serif;"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;=
Courier New&quot;;mso-fareast-font-family:=0A=CB=CE=CC=E5;mso-font-kerning=
:0pt">the Pv4 multicast address is inserted in the last 32=0Abits of the I=
Pv4-embedded IPv6 multicast address.<o:p></o:p></span></p>=0A<p class=3D"M=
soNormal" style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-siz=
e: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"EN-US"><span s=
tyle=3D"background-color: rgba(0, 0, 0, 0); font-family: 'Calibri, sans-se=
rif'; font-size: 10.5pt; line-height: 1.5;">&nbsp; &nbsp;&nbsp;</span></sp=
an><span style=3D"font-family: ''; font-size: 10.5pt; line-height: 1.5; ba=
ckground-color: window;">&nbsp; &nbsp;&nbsp;</span><span style=3D"font-siz=
e: 10.5pt; line-height: 1.5; background-color: window;">Where the second=
=0Aword should be IPv4.</span></p>=0A<p class=3D"MsoNormal" style=3D"margi=
n: 0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font-family: =
Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>=0A=
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; text-align: just=
ify; font-size: 10.5pt; font-family: Calibri, sans-serif;"><span lang=3D"E=
N-US">Best regards,<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=
=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font=
-family: Calibri, sans-serif;"><span lang=3D"EN-US">Linhui Sun<o:p></o:p><=
/span></p>=0A<!--EndFragment--></div>=0A<div><br></div><hr style=3D"width:=
 210px; height: 1px;" color=3D"#b5c4df" size=3D"1" align=3D"left">=0A<div>=
<span><div style=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt"><=
div>sunlinhui@bupt.edu.cn</div></div></span></div>=0A</body></html>
------=_001_NextPart128083652604_=------


From nobody Thu Oct  9 00:43:54 2014
Return-Path: <wang.cui1@zte.com.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 953911A924A for <softwires@ietfa.amsl.com>; Thu,  9 Oct 2014 00:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level: 
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zYLUveGA-dQc for <softwires@ietfa.amsl.com>; Thu,  9 Oct 2014 00:43:48 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5A91A923E for <softwires@ietf.org>; Thu,  9 Oct 2014 00:43:48 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id BABFA126D47F for <softwires@ietf.org>; Thu,  9 Oct 2014 15:43:33 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id D3134716E59; Thu,  9 Oct 2014 15:43:32 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id s997gIDr002140; Thu, 9 Oct 2014 15:42:18 +0800 (GMT-8) (envelope-from wang.cui1@zte.com.cn)
In-Reply-To: <2014100611385003530021@bupt.edu.cn>
References: <2014100611385003530021@bupt.edu.cn>
To: "sunlinhui@bupt.edu.cn" <sunlinhui@bupt.edu.cn>
MIME-Version: 1.0
X-KeepSent: EDFFDB1D:F2462556-48257D6C:00106260; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011
Message-ID: <OFEDFFDB1D.F2462556-ON48257D6C.00106260-48257D6C.002A42DF@zte.com.cn>
From: wang.cui1@zte.com.cn
Date: Thu, 9 Oct 2014 15:42:18 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2014-10-09 15:42:18, Serialize complete at 2014-10-09 15:42:18
Content-Type: multipart/alternative; boundary="=_alternative 002A42DA48257D6C_="
X-MAIL: mse01.zte.com.cn s997gIDr002140
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/QhOcGqtJv3yuiTqxjONBJpSp3tA
Cc: softwires <softwires@ietf.org>, wangqian@ctbri.com.cn
Subject: Re: [Softwires] Comments on draft-hu-softwire-multicast-radius-ext
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 09 Oct 2014 07:43:52 -0000

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

SGksIExpbmh1aSwNCg0KICBUaGFua3MgZm9yIHlvdXIgY29tbWVudHMuIFBsZWFzZSBzZWUgaW5s
aW5lLg0KICBBbmQgYWxsIHlvdXIgY29tbWVudHMgd2Ugd2lsbCB1cGRhdGUgdGhlbSBpbiB0aGUg
bmV4dCB2ZXJzaW9uLg0KDQogIE1hbnkgdGhhbmtzLg0KDQpCUnMNCkxpbmRhIFdhbmcNCg0KInN1
bmxpbmh1aUBidXB0LmVkdS5jbiIgPHN1bmxpbmh1aUBidXB0LmVkdS5jbj4g0LTT2iAyMDE0LTEw
LTA2IDExOjM4OjUwOg0KDQo+ICJzdW5saW5odWlAYnVwdC5lZHUuY24iIDxzdW5saW5odWlAYnVw
dC5lZHUuY24+IA0KPiAyMDE0LTEwLTA2IDExOjM4DQo+IA0KPiDK1bz+yMsNCj4gDQo+IG1lbmcu
d2VpMkB6dGUuY29tLmNuLCBtb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tLCANCj4gd2FuZy5j
dWkxQHp0ZS5jb20uY24sIHdhbmdxaWFuQGN0YnJpLmNvbS5jbiwgDQo+IA0KPiCzrcvNDQo+IA0K
PiBzb2Z0d2lyZXMgPHNvZnR3aXJlc0BpZXRmLm9yZz4NCj4gDQo+INb3zOINCj4gDQo+IENvbW1l
bnRzIG9uIGRyYWZ0LWh1LXNvZnR3aXJlLW11bHRpY2FzdC1yYWRpdXMtZXh0DQo+IA0KPiBEZWFy
IGF1dGhvcnMsIA0KPiANCj4gSSBoYXZlIHJlYWQgdGhpcyBkb2N1bWVudCBhbmQgdGhpbmsgaXQg
aXMgbWVhbmluZ2Z1bCB0byBwcm9wb3NlIGEgDQo+IG5ldyBSQURJVVMgYXR0cmlidXRlIHRvIGNh
cnJ5IHRoZSBJUHY2IHByZWZpeGVzIHRvZ2V0aGVyIHdpdGggdGhlIA0KPiBESENQdjYgb3B0aW9u
IGRlZmluZWQgaW4gZHJhZnQtaWV0Zi1zb2Z0d2lyZS1tdWx0aWNhc3QtcHJlZml4LW9wdGlvbi0w
Ny4gDQoNCj4gDQo+IEhlcmUgYXJlIHNvbWUgY29tbWVudHMgYWJvdXQgdGhpcyBkb2N1bWVudC4g
DQo+IA0KPiAxLiBUaGUgZm9sbG93aW5nIHBhcmFncmFwaCByZXBlYXRzIHR3aWNlIChzZWN0aW9u
IDMgYW5kIHNlY3Rpb24gNCkgDQo+IGluIHRoaXMgZG9jdW1lbnQuIA0KPiAnSWYgdGhlIE5BUyBk
b2VzIG5vdCByZWNlaXZlIHRoZSBNdWx0aWNhc3QtUHJlZml4ZXMtNjQgYXR0cmlidXRlIGluIA0K
PiB0aGUgQWNjZXNzLUFjY2VwdCBtZXNzYWdlLCBpdCBNQVkgZmFsbCBiYWNrIHRvIGEgcHJlLWNv
bmZpZ3VyZWQgDQo+IGRlZmF1bHQgTXVsdGljYXN0LVByZWZpeGVzLTY0LCBpZiBhbnkuIElmIHRo
ZSBOQVMgZG9lcyBub3QgaGF2ZSBhbnkgDQo+IHByZS1jb25maWd1cmVkLCB0aGUgZGVsaXZlcnkg
b2YgbXVsdGljYXN0IHRyYWZmaWMgaXMgbm90IHN1cHBvcnRlZC4nIA0KPiBEbyB5b3UgdGhpbmsg
aXQgaXMgbW9yZSBzdWl0YWJsZSB0byByZW1vdmUgdGhlIHJlcGVhdGVkIG9uZSBpbiBzZWN0aW9u
IA0KMz8gDQovL0xpbmRhOiBJIGRvIGFncmVlIHdpdGggeW91LiBUaGFua3MuDQoNCj4gDQo+IDIu
IFRoZSBhcmNoaXRlY3R1cmUgb2YgdGhpcyBkb2N1bWVudCBzZWVtcyBub3QgdmVyeSByZWFzb25h
YmxlLiBEbyANCj4geW91IHRoaW5rIGl0IGNvdWxkIGJlIG9mIGEgYmV0dGVyIHN0cnVjdHVyZT8g
SGVyZSBhcmUgbXkgc3VnZ2VzdGlvbnMuIA0KPiBhKSBUaGUgc2VjdGlvbiA0IGlzIGludGVuZGVk
IHRvIHNwZWNpZnkgdGhlIG5ldyBSQURJVVMgYXR0cmlidXRlLCBpdA0KPiBzZWVtcyB0aGF0IHRo
ZSBtb3N0IGNvbnRlbnQgb2YgdGhlIHNlY3Rpb24gNC4xIGlzIGRlc2NyaWJpbmcgdGhlIA0KPiBS
QURJVVMgY2xpZW50IGJlaGF2aW9yLiBEbyB5b3UgdGhpbmsgaXQgaXMgYXBwcm9wcmlhdGUgdG8g
dHJlYXQgdGhpcw0KPiBwYXJ0IGFzIGEgc2VwYXJhdGUgc2VjdGlvbiBjYWxsZWQgdGhlIENsaWVu
dCBCZWhhdmlvci4gDQo+IGIpIEFuZCBJIHRoaW5rIHRoZSBzZXF1ZW5jZSBvZiB0aGUgc2VjdGlv
bnMgY291bGQgYmUgbW9kaWZpZWQgdG8gDQo+IGJlY29tZSBiZXR0ZXIgb3JnYW5pemVkLiBUaGUg
c2VjdGlvbiBSQURJVVMgQXR0cmlidXRlIGNvdWxkIGJlIA0KPiBpbnRyb2R1Y2VkIGZpcnN0LCB0
aGVuIHRoZSBzZWN0aW9uIENsaWVudCBCZWhhdmlvciB3b3VsZCBiZSANCj4gZGlzY3Vzc2VkIGxh
dGVyLiBXaGlsZSB0aGUgTXVsdGljYXN0LVByZWZpeGVzLTY0IENvbmZpZ3VyYXRpb24gd2l0aCAN
Cj4gUkFESVVTIGFuZCBESENQdjYgc2VjdGlvbiBpcyBtb3JlIGFwcHJvcHJpYXRlIHRvIGxvY2F0
ZSBpbiB0aGUgcmVhciANCj4gb2YgdGhvc2UgdHdvIHNlY3Rpb25zLiANCi8vTGluZGE6IE9yaWdp
bmFsbHksIHdlIGNvbnNpZGVyZWQgaXQgd291bGQgYmUgY2xlYXJlciB0byBwcmVzZW50IHRoZSAN
CnRoZSB3aG9sZSBtZXNzYWdlIGV4Y2hhbmdlIGZsb3cgZmlyc3QsIHRoZW4gZm9sbG93IHRoaXMg
ZmxvdywgcmVhZGVycyANCmNhbiBjYXRjaCBhIGJldHRlciB1bmRlcnN0YW5kaW5nIG9mIHdoZXJl
IHRoaXMgYXR0cmlidXRlIHdvdWxkIGJlIGJyb3VnaHQNCndpdGggYW5kIGhvdyB0aGlzIGF0dHJp
YnV0ZSB3b3VsZCBiZSB1c2VkLiBBZnRlciB0aGF0LCB3ZSBpbGx1c3RyYXRlZCB0aGUgDQpmb3Jt
YXQgb2YgdGhpcyBhdHRyaWJ1dGUgbmF0dXJhbGx5LiBEbyB5b3UgdGhpbmsgdGhpcyBjYW4gZXhw
bGFpbiANCndoeSB3ZSBwcmVzZW50ZWQgdGhpcyBkcmFmdCBpbiB0aGlzIHN0cnVjdHVyZT8NCkFz
IGZvciB5b3VyIHByb3Bvc2FsIGFib3V0IHNlY3Rpb24gNC4xLCBpbiBmYWN0LCBpbiB0aGlzIHNl
Y3Rpb24gd2Ugd2FudGVkIA0KDQp0byBlbXBoYXNpemUgdGhlIGNoYW5nZWQgZGV0YWlscyB3aGlj
aCB3ZXJlIGNhdXNlZCBieSB0aGlzIG5ldyBhdHRyaWJ1dGUsDQpub3QgZW1waGFzaXplIHRoZSBz
ZXBhcmF0ZWQgY2xpZW50IGJlaGF2aW9yIG9yIHNlcnZlciBiZWhhdmlvci4gU28gd2UgDQppbnRl
Z3JhdGVkIHRoZW0gdG9nZXRoZXIuIA0KQnV0LCB3ZSBzdGlsbCB3aWxsIGNhcmVmdWxseSBjb25z
aWRlciB5b3VyIHByb3Bvc2FsIHN0cnVjdHVyZSBsYXRlci4gDQpUaGFua3MuIA0KDQo+IA0KPiAz
LiBUaGUgoa5ESENQdjYgQWR2ZXJ0aXNlbWVudKGvIGluIEZpZ3VyZSAxLDIgY291bGQgYmUgbW9k
aWZpZWQgYXMgDQo+IKGuREhDUHY2IEFkdmVydGlzZaGvIGluIGEgbW9yZSBzdGFuZGFyZGl6ZWQg
d2F5IGFjY29yZGluZyB0byB0aGUgUkZDIA0KMzMxNS4gDQovL0xpbmRhOiBJIGRvIGFncmVlIHdp
dGggeW91LiBUaGFua3MuDQoNCj4gDQo+IDQuIFRoZXJlIHNlZW1zIHRvIGJlIGEgY29uZmxpY3Qg
YmV0d2VlbiB0aGUgZmlndXJlIDEgYW5kIGl0cyANCj4gY29ycmVzcG9uZGluZyBkZXNjcmlwdGlv
bi4gDQo+IEZyb20gdGhlIEZpZ3VyZSAxLCB3ZSBjYW4gY29uY2x1ZGUgdGhhdCB0aGUgREhDUHY2
IEFkdmVydGlzZSBtZXNzYWdlDQo+IGNhcnJpZXMgdGhlIERIQ1B2NiBPUFRJT05fUFJFRklYNjQg
b3B0aW9uLiANCj4gSG93ZXZlciwgaWYgd2UgcmVmZXIgdG8gdGhlIGNvbnRlbnQsIGl0IHN0YXRl
cyB0aGF0IKGudGhlIE5BUyBTSEFMTCANCj4gdXNlIHRoZSBwcmVmaXhlcyByZXR1cm5lZCBpbiB0
aGUgUkFESVVTIE11bHRpY2FzdC1QcmVmaXhlcy02NCANCj4gYXR0cmlidXRlIHRvIHBvcHVsYXRl
IHRoZSBESENQdjYgT1BUSU9OX1BSRUZJWDY0IG9wdGlvbiBpbiB0aGUgDQo+IERIQ1B2NiByZXBs
eSBtZXNzYWdloa8gaW4gc2VjdGlvbiAzLiANCj4gRG8geW91IHRoaW5rIGl0IGNvdWxkIGJlIGJl
dHRlciB0byBrZWVwIHRoZSBjb25zaXN0ZW5jZSBiZXR3ZWVuIHRoZSANCj4gZmlndXJlIGFuZCBp
dHMgZGVzY3JpcHRpb24uIA0KLy9MaW5kYTogSSBkbyBhZ3JlZSB3aXRoIHlvdS4gVGhhbmtzLg0K
PiANCg0KPiA1LiBDb3VsZCB5b3UgcGxlYXNlIGV4cGxhaW4gd2h5IHRoZSBESENQdjYgUmVxdWVz
dCBtZXNzYWdlIGluIHRoZSANCj4gRmlndXJlIDIgZG9lcyBub3QgY2FycnkgYSBESENQdjYgT1BU
SU9OX1BSRUZJWDY0PyANCi8vTGluZGE6IFllcywgeW91IGFyZSByaWdodC4gVGhlIERIQ1B2NiBS
ZXF1ZXN0IG1lc3NhZ2Ugc2hvdWxkIGNhcnJ5IHRoaXMgDQpvcHRpb24uDQo+IA0KDQo+IDYuIERv
IHlvdSB0aGluayBpdCBpcyBuZWNlc3NhcnkgdG8gYWRkIGEgc2VwYXJhdGUgcGFyYWdyYXBoIHRo
YXQgDQo+IGRlZmluZXMgaG93IHRoZSBOQVMgd2lsbCBjb21tdW5pY2F0ZSB3aXRoIHRoZSBBQUEg
c2VydmVyIHdoZW4gdGhlIA0KPiBtQjQgaXMgYXQgaXRzIERIQ1AgcmVuZXcgc3RhZ2UgdG8gbWFr
ZSB0aGUgZG9jdW1lbnQgbW9yZSBjb21wcmVoZW5zaXZlPyANCi8vTGluZGE6IEluIHRoZSBsYXN0
IHBhcmFncmFwaCBpbiBzZWN0aW9uIDMsIHdlIGV4cGxhaW4gdGhlIERIQ1AgUkVORVcgDQpzdGFn
ZSwgZG8NCnlvdSB0aGluayBpdCBpcyBlbm91Z2ggZm9yIHlvdXIgcXVlc3Rpb24/DQoNCj4gDQo+
IEJlc3QgcmVnYXJkcywgDQo+IExpbmh1aSBTdW4gDQoNCj4gDQo+IHN1bmxpbmh1aUBidXB0LmVk
dS5jbg0K
--=_alternative 002A42DA48257D6C_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpLCBMaW5odWksPC9mb250Pg0KPGJyPg0K
PGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgVGhhbmtzIGZvciB5b3Vy
IGNvbW1lbnRzLiBQbGVhc2UNCnNlZSBpbmxpbmUuPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBm
YWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgQW5kIGFsbCB5b3VyIGNvbW1lbnRzIHdlIHdpbGwNCnVw
ZGF0ZSB0aGVtIGluIHRoZSBuZXh0IHZlcnNpb24uPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNp
emU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgTWFueSB0aGFua3MuPC9mb250Pg0KPGJyPg0K
PGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5CUnM8L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkxpbmRhIFdhbmc8L2ZvbnQ+DQo8YnI+DQo8YnI+PHR0
Pjxmb250IHNpemU9Mj4mcXVvdDtzdW5saW5odWlAYnVwdC5lZHUuY24mcXVvdDsgJmx0O3N1bmxp
bmh1aUBidXB0LmVkdS5jbiZndDsNCtC009ogMjAxNC0xMC0wNiAxMTozODo1MDo8YnI+DQo8YnI+
DQomZ3Q7ICZxdW90O3N1bmxpbmh1aUBidXB0LmVkdS5jbiZxdW90OyAmbHQ7c3VubGluaHVpQGJ1
cHQuZWR1LmNuJmd0OyA8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgMjAx
NC0xMC0wNiAxMTozODwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+
DQomZ3Q7IMrVvP7IyzwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+
DQomZ3Q7IG1lbmcud2VpMkB6dGUuY29tLmNuLCBtb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29t
LCA8YnI+DQomZ3Q7IHdhbmcuY3VpMUB6dGUuY29tLmNuLCB3YW5ncWlhbkBjdGJyaS5jb20uY24s
IDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7ILOty808
L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBzb2Z0d2ly
ZXMgJmx0O3NvZnR3aXJlc0BpZXRmLm9yZyZndDs8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQg
c2l6ZT0yPiZndDsgPGJyPg0KJmd0OyDW98ziPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNp
emU9Mj4mZ3Q7IDxicj4NCiZndDsgQ29tbWVudHMgb24gZHJhZnQtaHUtc29mdHdpcmUtbXVsdGlj
YXN0LXJhZGl1cy1leHQ8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJy
Pg0KJmd0OyBEZWFyIGF1dGhvcnMsIDxicj4NCiZndDsgPGJyPg0KJmd0OyBJIGhhdmUgcmVhZCB0
aGlzIGRvY3VtZW50IGFuZCB0aGluayBpdCBpcyBtZWFuaW5nZnVsIHRvIHByb3Bvc2UgYQ0KPGJy
Pg0KJmd0OyBuZXcgUkFESVVTIGF0dHJpYnV0ZSB0byBjYXJyeSB0aGUgSVB2NiBwcmVmaXhlcyB0
b2dldGhlciB3aXRoIHRoZQ0KPGJyPg0KJmd0OyBESENQdjYgb3B0aW9uIGRlZmluZWQgaW4gZHJh
ZnQtaWV0Zi1zb2Z0d2lyZS1tdWx0aWNhc3QtcHJlZml4LW9wdGlvbi0wNy4NCjxicj4NCiZndDsg
PGJyPg0KJmd0OyBIZXJlIGFyZSBzb21lIGNvbW1lbnRzIGFib3V0IHRoaXMgZG9jdW1lbnQuIDxi
cj4NCiZndDsgPGJyPg0KJmd0OyAxLiBUaGUgZm9sbG93aW5nIHBhcmFncmFwaCByZXBlYXRzIHR3
aWNlIChzZWN0aW9uIDMgYW5kIHNlY3Rpb24gNCkNCjxicj4NCiZndDsgaW4gdGhpcyBkb2N1bWVu
dC4gPGJyPg0KJmd0OyAnSWYgdGhlIE5BUyBkb2VzIG5vdCByZWNlaXZlIHRoZSBNdWx0aWNhc3Qt
UHJlZml4ZXMtNjQgYXR0cmlidXRlIGluDQo8YnI+DQomZ3Q7IHRoZSBBY2Nlc3MtQWNjZXB0IG1l
c3NhZ2UsIGl0IE1BWSBmYWxsIGJhY2sgdG8gYSBwcmUtY29uZmlndXJlZCA8YnI+DQomZ3Q7IGRl
ZmF1bHQgTXVsdGljYXN0LVByZWZpeGVzLTY0LCBpZiBhbnkuIElmIHRoZSBOQVMgZG9lcyBub3Qg
aGF2ZSBhbnkNCjxicj4NCiZndDsgcHJlLWNvbmZpZ3VyZWQsIHRoZSBkZWxpdmVyeSBvZiBtdWx0
aWNhc3QgdHJhZmZpYyBpcyBub3Qgc3VwcG9ydGVkLicNCjxicj4NCiZndDsgRG8geW91IHRoaW5r
IGl0IGlzIG1vcmUgc3VpdGFibGUgdG8gcmVtb3ZlIHRoZSByZXBlYXRlZCBvbmUgaW4gc2VjdGlv
bg0KMz8gPGJyPg0KPC9mb250PjwvdHQ+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWU+Ly9MaW5kYTog
SSBkbyBhZ3JlZSB3aXRoIHlvdS4gVGhhbmtzLjwvZm9udD4NCjxicj4NCjxicj48dHQ+PGZvbnQg
c2l6ZT0yPiZndDsgPGJyPg0KJmd0OyAyLiBUaGUgYXJjaGl0ZWN0dXJlIG9mIHRoaXMgZG9jdW1l
bnQgc2VlbXMgbm90IHZlcnkgcmVhc29uYWJsZS4gRG8NCjxicj4NCiZndDsgeW91IHRoaW5rIGl0
IGNvdWxkIGJlIG9mIGEgYmV0dGVyIHN0cnVjdHVyZT8gSGVyZSBhcmUgbXkgc3VnZ2VzdGlvbnMu
DQo8YnI+DQomZ3Q7IGEpIFRoZSBzZWN0aW9uIDQgaXMgaW50ZW5kZWQgdG8gc3BlY2lmeSB0aGUg
bmV3IFJBRElVUyBhdHRyaWJ1dGUsDQppdDxicj4NCiZndDsgc2VlbXMgdGhhdCB0aGUgbW9zdCBj
b250ZW50IG9mIHRoZSBzZWN0aW9uIDQuMSBpcyBkZXNjcmliaW5nIHRoZSA8YnI+DQomZ3Q7IFJB
RElVUyBjbGllbnQgYmVoYXZpb3IuIERvIHlvdSB0aGluayBpdCBpcyBhcHByb3ByaWF0ZSB0byB0
cmVhdCB0aGlzPGJyPg0KJmd0OyBwYXJ0IGFzIGEgc2VwYXJhdGUgc2VjdGlvbiBjYWxsZWQgdGhl
IENsaWVudCBCZWhhdmlvci4gPGJyPg0KJmd0OyBiKSBBbmQgSSB0aGluayB0aGUgc2VxdWVuY2Ug
b2YgdGhlIHNlY3Rpb25zIGNvdWxkIGJlIG1vZGlmaWVkIHRvIDxicj4NCiZndDsgYmVjb21lIGJl
dHRlciBvcmdhbml6ZWQuIFRoZSBzZWN0aW9uIFJBRElVUyBBdHRyaWJ1dGUgY291bGQgYmUgPGJy
Pg0KJmd0OyBpbnRyb2R1Y2VkIGZpcnN0LCB0aGVuIHRoZSBzZWN0aW9uIENsaWVudCBCZWhhdmlv
ciB3b3VsZCBiZSA8YnI+DQomZ3Q7IGRpc2N1c3NlZCBsYXRlci4gV2hpbGUgdGhlIE11bHRpY2Fz
dC1QcmVmaXhlcy02NCBDb25maWd1cmF0aW9uIHdpdGgNCjxicj4NCiZndDsgUkFESVVTIGFuZCBE
SENQdjYgc2VjdGlvbiBpcyBtb3JlIGFwcHJvcHJpYXRlIHRvIGxvY2F0ZSBpbiB0aGUgcmVhcg0K
PGJyPg0KJmd0OyBvZiB0aG9zZSB0d28gc2VjdGlvbnMuIDwvZm9udD48L3R0Pg0KPGJyPjx0dD48
Zm9udCBzaXplPTIgY29sb3I9Ymx1ZT4vL0xpbmRhOiBPcmlnaW5hbGx5LCB3ZSBjb25zaWRlcmVk
IGl0IHdvdWxkDQpiZSBjbGVhcmVyIHRvIHByZXNlbnQgdGhlIDwvZm9udD48L3R0Pg0KPGJyPjx0
dD48Zm9udCBzaXplPTIgY29sb3I9Ymx1ZT50aGUgd2hvbGUgbWVzc2FnZSBleGNoYW5nZSBmbG93
IGZpcnN0LA0KdGhlbiBmb2xsb3cgdGhpcyBmbG93LCByZWFkZXJzIDwvZm9udD48L3R0Pg0KPGJy
Pjx0dD48Zm9udCBzaXplPTIgY29sb3I9Ymx1ZT5jYW4gY2F0Y2ggYSBiZXR0ZXIgdW5kZXJzdGFu
ZGluZyBvZiB3aGVyZQ0KPC9mb250PjwvdHQ+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWU+dGhpcyBh
dHRyaWJ1dGU8L2ZvbnQ+PHR0Pjxmb250IHNpemU9MiBjb2xvcj1ibHVlPg0Kd291bGQgYmUgYnJv
dWdodDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTIgY29sb3I9Ymx1ZT53aXRoIGFu
ZCBob3cgPC9mb250PjwvdHQ+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWU+dGhpcw0KYXR0cmlidXRl
PC9mb250Pjx0dD48Zm9udCBzaXplPTIgY29sb3I9Ymx1ZT4gd291bGQgYmUgdXNlZC4gQWZ0ZXIg
dGhhdCwNCndlIGlsbHVzdHJhdGVkIHRoZSA8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6
ZT0yIGNvbG9yPWJsdWU+Zm9ybWF0IG9mIHRoaXMgYXR0cmlidXRlIG5hdHVyYWxseS4gRG8NCnlv
dSB0aGluayB0aGlzIGNhbiBleHBsYWluIDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXpl
PTIgY29sb3I9Ymx1ZT53aHkgd2UgcHJlc2VudGVkIHRoaXMgZHJhZnQgaW4gdGhpcyBzdHJ1Y3R1
cmU/PC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9MiBjb2xvcj1ibHVlPkFzIGZvciB5
b3VyIHByb3Bvc2FsIGFib3V0IHNlY3Rpb24gNC4xLA0KaW4gZmFjdCwgaW4gdGhpcyBzZWN0aW9u
IHdlIHdhbnRlZCA8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWU+
dG8gZW1waGFzaXplIHRoZSBjaGFuZ2VkIGRldGFpbHMgd2hpY2gNCndlcmUgY2F1c2VkIGJ5IHRo
aXMgbmV3IGF0dHJpYnV0ZSw8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yIGNvbG9y
PWJsdWU+bm90IGVtcGhhc2l6ZSB0aGUgc2VwYXJhdGVkIGNsaWVudCBiZWhhdmlvcg0Kb3Igc2Vy
dmVyIGJlaGF2aW9yLiBTbyB3ZSA8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yIGNv
bG9yPWJsdWU+aW50ZWdyYXRlZCB0aGVtIHRvZ2V0aGVyLiA8L2ZvbnQ+PC90dD4NCjxicj48dHQ+
PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWU+QnV0LCB3ZSBzdGlsbCB3aWxsIGNhcmVmdWxseSBjb25z
aWRlciB5b3VyDQpwcm9wb3NhbCBzdHJ1Y3R1cmUgbGF0ZXIuIFRoYW5rcy4gPC9mb250PjwvdHQ+
DQo8YnI+PHR0Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7IDxicj4NCiZndDsgMy4gVGhlIKGuREhD
UHY2IEFkdmVydGlzZW1lbnShryBpbiBGaWd1cmUgMSwyIGNvdWxkIGJlIG1vZGlmaWVkDQphcyA8
YnI+DQomZ3Q7IKGuREhDUHY2IEFkdmVydGlzZaGvIGluIGEgbW9yZSBzdGFuZGFyZGl6ZWQgd2F5
IGFjY29yZGluZyB0byB0aGUNClJGQyAzMzE1LiA8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQg
c2l6ZT0yIGNvbG9yPWJsdWU+Ly9MaW5kYTogSSBkbyBhZ3JlZSB3aXRoIHlvdS4gVGhhbmtzLjwv
Zm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDQu
IFRoZXJlIHNlZW1zIHRvIGJlIGEgY29uZmxpY3QgYmV0d2VlbiB0aGUgZmlndXJlIDEgYW5kIGl0
cyA8YnI+DQomZ3Q7IGNvcnJlc3BvbmRpbmcgZGVzY3JpcHRpb24uIDxicj4NCiZndDsgRnJvbSB0
aGUgRmlndXJlIDEsIHdlIGNhbiBjb25jbHVkZSB0aGF0IHRoZSBESENQdjYgQWR2ZXJ0aXNlIG1l
c3NhZ2U8YnI+DQomZ3Q7IGNhcnJpZXMgdGhlIERIQ1B2NiBPUFRJT05fUFJFRklYNjQgb3B0aW9u
LiA8YnI+DQomZ3Q7IEhvd2V2ZXIsIGlmIHdlIHJlZmVyIHRvIHRoZSBjb250ZW50LCBpdCBzdGF0
ZXMgdGhhdCChrnRoZSBOQVMgU0hBTEwNCjxicj4NCiZndDsgdXNlIHRoZSBwcmVmaXhlcyByZXR1
cm5lZCBpbiB0aGUgUkFESVVTIE11bHRpY2FzdC1QcmVmaXhlcy02NCA8YnI+DQomZ3Q7IGF0dHJp
YnV0ZSB0byBwb3B1bGF0ZSB0aGUgREhDUHY2IE9QVElPTl9QUkVGSVg2NCBvcHRpb24gaW4gdGhl
IDxicj4NCiZndDsgREhDUHY2IHJlcGx5IG1lc3NhZ2WhryBpbiBzZWN0aW9uIDMuIDxicj4NCiZn
dDsgRG8geW91IHRoaW5rIGl0IGNvdWxkIGJlIGJldHRlciB0byBrZWVwIHRoZSBjb25zaXN0ZW5j
ZSBiZXR3ZWVuIHRoZQ0KPGJyPg0KJmd0OyBmaWd1cmUgYW5kIGl0cyBkZXNjcmlwdGlvbi4gPC9m
b250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9MiBjb2xvcj1ibHVlPi8vTGluZGE6IEkgZG8g
YWdyZWUgd2l0aCB5b3UuIFRoYW5rcy48L2ZvbnQ+PC90dD48dHQ+PGZvbnQgc2l6ZT0yPjxicj4N
CiZndDsgPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7IDUuIENv
dWxkIHlvdSBwbGVhc2UgZXhwbGFpbiB3aHkgdGhlIERIQ1B2NiBSZXF1ZXN0IG1lc3NhZ2UgaW4g
dGhlDQo8YnI+DQomZ3Q7IEZpZ3VyZSAyIGRvZXMgbm90IGNhcnJ5IGEgREhDUHY2IE9QVElPTl9Q
UkVGSVg2ND8gPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9MiBjb2xvcj1ibHVlPi8v
TGluZGE6IFllcywgeW91IGFyZSByaWdodC4gVGhlIERIQ1B2Ng0KUmVxdWVzdCBtZXNzYWdlIHNo
b3VsZCBjYXJyeSB0aGlzIG9wdGlvbi48L2ZvbnQ+PC90dD48dHQ+PGZvbnQgc2l6ZT0yPjxicj4N
CiZndDsgPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7IDYuIERv
IHlvdSB0aGluayBpdCBpcyBuZWNlc3NhcnkgdG8gYWRkIGEgc2VwYXJhdGUgcGFyYWdyYXBoIHRo
YXQgPGJyPg0KJmd0OyBkZWZpbmVzIGhvdyB0aGUgTkFTIHdpbGwgY29tbXVuaWNhdGUgd2l0aCB0
aGUgQUFBIHNlcnZlciB3aGVuIHRoZQ0KPGJyPg0KJmd0OyBtQjQgaXMgYXQgaXRzIERIQ1AgcmVu
ZXcgc3RhZ2UgdG8gbWFrZSB0aGUgZG9jdW1lbnQgbW9yZSBjb21wcmVoZW5zaXZlPw0KPC9mb250
PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9MiBjb2xvcj1ibHVlPi8vTGluZGE6IEluIHRoZSBs
YXN0IHBhcmFncmFwaCBpbiBzZWN0aW9uDQozLCB3ZSBleHBsYWluIHRoZSBESENQIFJFTkVXIHN0
YWdlLCBkbzwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTIgY29sb3I9Ymx1ZT55b3Ug
dGhpbmsgaXQgaXMgZW5vdWdoIGZvciB5b3VyIHF1ZXN0aW9uPzwvZm9udD48L3R0Pg0KPGJyPjx0
dD48Zm9udCBzaXplPTI+PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEJlc3QgcmVnYXJkcywgPGJyPg0K
Jmd0OyBMaW5odWkgU3VuIDxicj4NCjwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+
Jmd0OyA8YnI+DQomZ3Q7IHN1bmxpbmh1aUBidXB0LmVkdS5jbjwvZm9udD48L3R0Pg0K
--=_alternative 002A42DA48257D6C_=--


From nobody Fri Oct 10 18:19:44 2014
Return-Path: <cuiyong@tsinghua.edu.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5F271A037F for <softwires@ietfa.amsl.com>; Fri, 10 Oct 2014 18:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.688
X-Spam-Level: 
X-Spam-Status: No, score=-2.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AXZcYeUqlbTf for <softwires@ietfa.amsl.com>; Fri, 10 Oct 2014 18:19:40 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp02.tsinghua.edu.cn [166.111.204.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE5F1A036D for <softwires@ietf.org>; Fri, 10 Oct 2014 18:19:38 -0700 (PDT)
Received: from [101.5.96.248] (unknown [101.5.96.248]) by app5 (Coremail) with SMTP id DsxvpgCHjw+ehThUjm02AA--.693S3; Sat, 11 Oct 2014 09:19:26 +0800 (CST)
From: Yong Cui <cuiyong@tsinghua.edu.cn>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sat, 11 Oct 2014 09:19:30 +0800
Message-Id: <FDE4BC4D-C93D-45DE-9188-DEBD75E3007A@tsinghua.edu.cn>
To: Softwires WG <softwires@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-CM-TRANSID: DsxvpgCHjw+ehThUjm02AA--.693S3
X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUU5I7AC8VAFwI0_Jr0_Gr1l1xkIjI8I6I8E 6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM28EF7 xvwVC0I7IYx2IY67AKxVWDJVCq3wA2z4x0Y4vE2Ix0cI8IcVCY1x0267AKxVWxJr0_GcWl 84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_GcCE3s1le2 I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IEw4CE5I8CrVC2j2WlYx0E2Ix0cI8I cVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjc xG0xvY0x0EwIxGrwACjI8F5VA0II8E6IAqYI8I648v4I1l42xK82IYc2Ij64vIr41lx2Iq xVAqx4xG67AKxVWUJVWUGwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r 1Y6r17MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY 6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrJr0_WFyUJwCI42IY6I8E87 Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UYxBIdaVFxhVjvjDU0xZF pf9x0UUjRk7UUUUU=
X-CM-SenderInfo: 5fxl50tqj632xlqjx3vdohv3gofq/
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/lWww88l7tx7Latqr6Tk1fy7QPNY
Cc: =?utf-8?Q?Cui_=E5=B4=94=E5=8B=87?= <cuiyong@tsinghua.edu.cn>
Subject: [Softwires] Call for agenda items at IETF 91
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 11 Oct 2014 01:19:42 -0000

Hi folks,

According to the preliminary agenda, the softwire WG will have a 2 hour =
slot on Tuesday afternoon, November 11, at the Honolulu IETF meeting.
Following please find the preliminary IETF agenda.
https://datatracker.ietf.org/meeting/91/agenda.html

If you'd like to present something in the softwire's slot, please send =
your request to softwire-chairs@tools.ietf.org by Oct. 18 in the =
following format:
<draft name, link, time required, presenter's name>.=20


Thanks

Yong and Suresh



From nobody Fri Oct 10 18:43:26 2014
Return-Path: <sunlinhui@bupt.edu.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C65D11A03A6 for <softwires@ietfa.amsl.com>; Fri, 10 Oct 2014 18:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.464
X-Spam-Level: **
X-Spam-Status: No, score=2.464 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 456KS94sgv6W for <softwires@ietfa.amsl.com>; Fri, 10 Oct 2014 18:43:21 -0700 (PDT)
Received: from mx2.bupt.edu.cn (mx2.bupt.edu.cn [211.68.68.3]) by ietfa.amsl.com (Postfix) with ESMTP id 16E911A03A5 for <softwires@ietf.org>; Fri, 10 Oct 2014 18:43:19 -0700 (PDT)
Received: from SDWM-20131107EC (unknown [221.217.44.176]) by mx2.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 55A6B19F373; Sat, 11 Oct 2014 09:43:17 +0800 (HKT)
Date: Sat, 11 Oct 2014 09:44:16 +0800
From: "sunlinhui@bupt.edu.cn" <sunlinhui@bupt.edu.cn>
To: wang.cui1 <wang.cui1@zte.com.cn>
References: <2014100611385003530021@bupt.edu.cn>,  <OFEDFFDB1D.F2462556-ON48257D6C.00106260-48257D6C.002A42DF@zte.com.cn>
X-Priority: 3
X-GUID: 5703B6F8-F1CD-4AEF-B871-8808F6BF9BA4
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 140[cn]
Mime-Version: 1.0
Message-ID: <201410110944161139749@bupt.edu.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart032158725074_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/yyncRRAcX9Zy8si18nUMIWLWdWc
Cc: softwires <softwires@ietf.org>
Subject: Re: [Softwires] Comments on draft-hu-softwire-multicast-radius-ext
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 11 Oct 2014 01:43:25 -0000

This is a multi-part message in MIME format.

------=_001_NextPart032158725074_=----
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: base64

SGksIExpbmRhLg0KDQogICAgVGhhbmsgeW91IGZvciB5b3VyIHJlcGx5IGFuZCBleHBsYW5uYXRp
b24hDQoNCiAgICBBcyBmb3IgdGhlIHF1ZXN0aW9uIDYsIHRoZSBsYXN0IHBhcmFncmFwaCBpbiBz
ZWN0aW9uIDMgc2VlbXMgdG8gZGVzY3JpYmUgdGhlIGNvbW11bmljYXRpb24gd2hlbiBUMSBleHBp
cmVzLiBEb2VzIGl0IG1lYW4gdGhhdCB3aGVuIHRoZSBtQjQgaXMgcmVzcG9uZGVkIGluIFQxIHRo
ZXJlIGlzIG5vIGNvbW11bmljYXRpb24gYmV0d2VlbiBOQVMgYW5kIEFBQSBzZXJ2ZXI/DQoNCkJl
c3QgcmVnYXJkcywNCkxpbmh1aSBTdW4NCg0KDQoNCnN1bmxpbmh1aUBidXB0LmVkdS5jbg0KIA0K
t6K8/sjLo7ogd2FuZy5jdWkxDQq3osvNyrG85KO6IDIwMTQtMTAtMDkgMTU6NDINCsrVvP7Iy6O6
IHN1bmxpbmh1aUBidXB0LmVkdS5jbg0Ks63LzaO6IG1lbmcud2VpMjsgbW9oYW1lZC5ib3VjYWRh
aXI7IHdhbmcuY3VpMTsgd2FuZ3FpYW47IHNvZnR3aXJlcw0K1vfM4qO6IFJFOkNvbW1lbnRzIG9u
IGRyYWZ0LWh1LXNvZnR3aXJlLW11bHRpY2FzdC1yYWRpdXMtZXh0DQpIaSwgTGluaHVpLCANCg0K
ICBUaGFua3MgZm9yIHlvdXIgY29tbWVudHMuIFBsZWFzZSBzZWUgaW5saW5lLiANCiAgQW5kIGFs
bCB5b3VyIGNvbW1lbnRzIHdlIHdpbGwgdXBkYXRlIHRoZW0gaW4gdGhlIG5leHQgdmVyc2lvbi4g
DQoNCiAgTWFueSB0aGFua3MuIA0KDQpCUnMgDQpMaW5kYSBXYW5nIA0KDQoic3VubGluaHVpQGJ1
cHQuZWR1LmNuIiA8c3VubGluaHVpQGJ1cHQuZWR1LmNuPiDQtNPaIDIwMTQtMTAtMDYgMTE6Mzg6
NTA6DQoNCj4gInN1bmxpbmh1aUBidXB0LmVkdS5jbiIgPHN1bmxpbmh1aUBidXB0LmVkdS5jbj4g
DQo+IDIwMTQtMTAtMDYgMTE6MzggDQo+IA0KPiDK1bz+yMsgDQo+IA0KPiBtZW5nLndlaTJAenRl
LmNvbS5jbiwgbW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSwgDQo+IHdhbmcuY3VpMUB6dGUu
Y29tLmNuLCB3YW5ncWlhbkBjdGJyaS5jb20uY24sIA0KPiANCj4gs63LzSANCj4gDQo+IHNvZnR3
aXJlcyA8c29mdHdpcmVzQGlldGYub3JnPiANCj4gDQo+INb3zOIgDQo+IA0KPiBDb21tZW50cyBv
biBkcmFmdC1odS1zb2Z0d2lyZS1tdWx0aWNhc3QtcmFkaXVzLWV4dCANCj4gDQo+IERlYXIgYXV0
aG9ycywgDQo+IA0KPiBJIGhhdmUgcmVhZCB0aGlzIGRvY3VtZW50IGFuZCB0aGluayBpdCBpcyBt
ZWFuaW5nZnVsIHRvIHByb3Bvc2UgYSANCj4gbmV3IFJBRElVUyBhdHRyaWJ1dGUgdG8gY2Fycnkg
dGhlIElQdjYgcHJlZml4ZXMgdG9nZXRoZXIgd2l0aCB0aGUgDQo+IERIQ1B2NiBvcHRpb24gZGVm
aW5lZCBpbiBkcmFmdC1pZXRmLXNvZnR3aXJlLW11bHRpY2FzdC1wcmVmaXgtb3B0aW9uLTA3LiAN
Cj4gDQo+IEhlcmUgYXJlIHNvbWUgY29tbWVudHMgYWJvdXQgdGhpcyBkb2N1bWVudC4gDQo+IA0K
PiAxLiBUaGUgZm9sbG93aW5nIHBhcmFncmFwaCByZXBlYXRzIHR3aWNlIChzZWN0aW9uIDMgYW5k
IHNlY3Rpb24gNCkgDQo+IGluIHRoaXMgZG9jdW1lbnQuIA0KPiAnSWYgdGhlIE5BUyBkb2VzIG5v
dCByZWNlaXZlIHRoZSBNdWx0aWNhc3QtUHJlZml4ZXMtNjQgYXR0cmlidXRlIGluIA0KPiB0aGUg
QWNjZXNzLUFjY2VwdCBtZXNzYWdlLCBpdCBNQVkgZmFsbCBiYWNrIHRvIGEgcHJlLWNvbmZpZ3Vy
ZWQgDQo+IGRlZmF1bHQgTXVsdGljYXN0LVByZWZpeGVzLTY0LCBpZiBhbnkuIElmIHRoZSBOQVMg
ZG9lcyBub3QgaGF2ZSBhbnkgDQo+IHByZS1jb25maWd1cmVkLCB0aGUgZGVsaXZlcnkgb2YgbXVs
dGljYXN0IHRyYWZmaWMgaXMgbm90IHN1cHBvcnRlZC4nIA0KPiBEbyB5b3UgdGhpbmsgaXQgaXMg
bW9yZSBzdWl0YWJsZSB0byByZW1vdmUgdGhlIHJlcGVhdGVkIG9uZSBpbiBzZWN0aW9uIDM/IA0K
Ly9MaW5kYTogSSBkbyBhZ3JlZSB3aXRoIHlvdS4gVGhhbmtzLiANCg0KPiANCj4gMi4gVGhlIGFy
Y2hpdGVjdHVyZSBvZiB0aGlzIGRvY3VtZW50IHNlZW1zIG5vdCB2ZXJ5IHJlYXNvbmFibGUuIERv
IA0KPiB5b3UgdGhpbmsgaXQgY291bGQgYmUgb2YgYSBiZXR0ZXIgc3RydWN0dXJlPyBIZXJlIGFy
ZSBteSBzdWdnZXN0aW9ucy4gDQo+IGEpIFRoZSBzZWN0aW9uIDQgaXMgaW50ZW5kZWQgdG8gc3Bl
Y2lmeSB0aGUgbmV3IFJBRElVUyBhdHRyaWJ1dGUsIGl0DQo+IHNlZW1zIHRoYXQgdGhlIG1vc3Qg
Y29udGVudCBvZiB0aGUgc2VjdGlvbiA0LjEgaXMgZGVzY3JpYmluZyB0aGUgDQo+IFJBRElVUyBj
bGllbnQgYmVoYXZpb3IuIERvIHlvdSB0aGluayBpdCBpcyBhcHByb3ByaWF0ZSB0byB0cmVhdCB0
aGlzDQo+IHBhcnQgYXMgYSBzZXBhcmF0ZSBzZWN0aW9uIGNhbGxlZCB0aGUgQ2xpZW50IEJlaGF2
aW9yLiANCj4gYikgQW5kIEkgdGhpbmsgdGhlIHNlcXVlbmNlIG9mIHRoZSBzZWN0aW9ucyBjb3Vs
ZCBiZSBtb2RpZmllZCB0byANCj4gYmVjb21lIGJldHRlciBvcmdhbml6ZWQuIFRoZSBzZWN0aW9u
IFJBRElVUyBBdHRyaWJ1dGUgY291bGQgYmUgDQo+IGludHJvZHVjZWQgZmlyc3QsIHRoZW4gdGhl
IHNlY3Rpb24gQ2xpZW50IEJlaGF2aW9yIHdvdWxkIGJlIA0KPiBkaXNjdXNzZWQgbGF0ZXIuIFdo
aWxlIHRoZSBNdWx0aWNhc3QtUHJlZml4ZXMtNjQgQ29uZmlndXJhdGlvbiB3aXRoIA0KPiBSQURJ
VVMgYW5kIERIQ1B2NiBzZWN0aW9uIGlzIG1vcmUgYXBwcm9wcmlhdGUgdG8gbG9jYXRlIGluIHRo
ZSByZWFyIA0KPiBvZiB0aG9zZSB0d28gc2VjdGlvbnMuIA0KLy9MaW5kYTogT3JpZ2luYWxseSwg
d2UgY29uc2lkZXJlZCBpdCB3b3VsZCBiZSBjbGVhcmVyIHRvIHByZXNlbnQgdGhlIA0KdGhlIHdo
b2xlIG1lc3NhZ2UgZXhjaGFuZ2UgZmxvdyBmaXJzdCwgdGhlbiBmb2xsb3cgdGhpcyBmbG93LCBy
ZWFkZXJzIA0KY2FuIGNhdGNoIGEgYmV0dGVyIHVuZGVyc3RhbmRpbmcgb2Ygd2hlcmUgdGhpcyBh
dHRyaWJ1dGUgd291bGQgYmUgYnJvdWdodCANCndpdGggYW5kIGhvdyB0aGlzIGF0dHJpYnV0ZSB3
b3VsZCBiZSB1c2VkLiBBZnRlciB0aGF0LCB3ZSBpbGx1c3RyYXRlZCB0aGUgDQpmb3JtYXQgb2Yg
dGhpcyBhdHRyaWJ1dGUgbmF0dXJhbGx5LiBEbyB5b3UgdGhpbmsgdGhpcyBjYW4gZXhwbGFpbiAN
CndoeSB3ZSBwcmVzZW50ZWQgdGhpcyBkcmFmdCBpbiB0aGlzIHN0cnVjdHVyZT8gDQpBcyBmb3Ig
eW91ciBwcm9wb3NhbCBhYm91dCBzZWN0aW9uIDQuMSwgaW4gZmFjdCwgaW4gdGhpcyBzZWN0aW9u
IHdlIHdhbnRlZCANCnRvIGVtcGhhc2l6ZSB0aGUgY2hhbmdlZCBkZXRhaWxzIHdoaWNoIHdlcmUg
Y2F1c2VkIGJ5IHRoaXMgbmV3IGF0dHJpYnV0ZSwgDQpub3QgZW1waGFzaXplIHRoZSBzZXBhcmF0
ZWQgY2xpZW50IGJlaGF2aW9yIG9yIHNlcnZlciBiZWhhdmlvci4gU28gd2UgDQppbnRlZ3JhdGVk
IHRoZW0gdG9nZXRoZXIuIA0KQnV0LCB3ZSBzdGlsbCB3aWxsIGNhcmVmdWxseSBjb25zaWRlciB5
b3VyIHByb3Bvc2FsIHN0cnVjdHVyZSBsYXRlci4gVGhhbmtzLiANCg0KPiANCj4gMy4gVGhlIKGu
REhDUHY2IEFkdmVydGlzZW1lbnShryBpbiBGaWd1cmUgMSwyIGNvdWxkIGJlIG1vZGlmaWVkIGFz
IA0KPiChrkRIQ1B2NiBBZHZlcnRpc2WhryBpbiBhIG1vcmUgc3RhbmRhcmRpemVkIHdheSBhY2Nv
cmRpbmcgdG8gdGhlIFJGQyAzMzE1LiANCi8vTGluZGE6IEkgZG8gYWdyZWUgd2l0aCB5b3UuIFRo
YW5rcy4gDQoNCj4gDQo+IDQuIFRoZXJlIHNlZW1zIHRvIGJlIGEgY29uZmxpY3QgYmV0d2VlbiB0
aGUgZmlndXJlIDEgYW5kIGl0cyANCj4gY29ycmVzcG9uZGluZyBkZXNjcmlwdGlvbi4gDQo+IEZy
b20gdGhlIEZpZ3VyZSAxLCB3ZSBjYW4gY29uY2x1ZGUgdGhhdCB0aGUgREhDUHY2IEFkdmVydGlz
ZSBtZXNzYWdlDQo+IGNhcnJpZXMgdGhlIERIQ1B2NiBPUFRJT05fUFJFRklYNjQgb3B0aW9uLiAN
Cj4gSG93ZXZlciwgaWYgd2UgcmVmZXIgdG8gdGhlIGNvbnRlbnQsIGl0IHN0YXRlcyB0aGF0IKGu
dGhlIE5BUyBTSEFMTCANCj4gdXNlIHRoZSBwcmVmaXhlcyByZXR1cm5lZCBpbiB0aGUgUkFESVVT
IE11bHRpY2FzdC1QcmVmaXhlcy02NCANCj4gYXR0cmlidXRlIHRvIHBvcHVsYXRlIHRoZSBESENQ
djYgT1BUSU9OX1BSRUZJWDY0IG9wdGlvbiBpbiB0aGUgDQo+IERIQ1B2NiByZXBseSBtZXNzYWdl
oa8gaW4gc2VjdGlvbiAzLiANCj4gRG8geW91IHRoaW5rIGl0IGNvdWxkIGJlIGJldHRlciB0byBr
ZWVwIHRoZSBjb25zaXN0ZW5jZSBiZXR3ZWVuIHRoZSANCj4gZmlndXJlIGFuZCBpdHMgZGVzY3Jp
cHRpb24uIA0KLy9MaW5kYTogSSBkbyBhZ3JlZSB3aXRoIHlvdS4gVGhhbmtzLg0KPiANCg0KPiA1
LiBDb3VsZCB5b3UgcGxlYXNlIGV4cGxhaW4gd2h5IHRoZSBESENQdjYgUmVxdWVzdCBtZXNzYWdl
IGluIHRoZSANCj4gRmlndXJlIDIgZG9lcyBub3QgY2FycnkgYSBESENQdjYgT1BUSU9OX1BSRUZJ
WDY0PyANCi8vTGluZGE6IFllcywgeW91IGFyZSByaWdodC4gVGhlIERIQ1B2NiBSZXF1ZXN0IG1l
c3NhZ2Ugc2hvdWxkIGNhcnJ5IHRoaXMgb3B0aW9uLg0KPiANCg0KPiA2LiBEbyB5b3UgdGhpbmsg
aXQgaXMgbmVjZXNzYXJ5IHRvIGFkZCBhIHNlcGFyYXRlIHBhcmFncmFwaCB0aGF0IA0KPiBkZWZp
bmVzIGhvdyB0aGUgTkFTIHdpbGwgY29tbXVuaWNhdGUgd2l0aCB0aGUgQUFBIHNlcnZlciB3aGVu
IHRoZSANCj4gbUI0IGlzIGF0IGl0cyBESENQIHJlbmV3IHN0YWdlIHRvIG1ha2UgdGhlIGRvY3Vt
ZW50IG1vcmUgY29tcHJlaGVuc2l2ZT8gDQovL0xpbmRhOiBJbiB0aGUgbGFzdCBwYXJhZ3JhcGgg
aW4gc2VjdGlvbiAzLCB3ZSBleHBsYWluIHRoZSBESENQIFJFTkVXIHN0YWdlLCBkbyANCnlvdSB0
aGluayBpdCBpcyBlbm91Z2ggZm9yIHlvdXIgcXVlc3Rpb24/IA0KDQo+IA0KPiBCZXN0IHJlZ2Fy
ZHMsIA0KPiBMaW5odWkgU3VuIA0KDQo+IA0KPiBzdW5saW5odWlAYnVwdC5lZHUuY24gDQo=

------=_001_NextPart032158725074_=----
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DGB2312"><style>body { line-height: 1.5; }blockquote { margin-top: 0px;=
 margin-bottom: 0px; margin-left: 0.5em; }div.foxdiv20141011093304594187 {=
 }body { font-size: 10.5pt; font-family: =CE=A2=C8=ED=D1=C5=BA=DA; color: =
rgb(0, 0, 0); line-height: 1.5; }</style></head><body>=0A<div><span></span=
>Hi, Linda.</div><div><br></div><div><span style=3D"background-color: rgba=
(0, 0, 0, 0);">&nbsp; &nbsp; Thank you for your reply and explannation!</s=
pan></div><div><span style=3D"background-color: rgba(0, 0, 0, 0);"><br></s=
pan></div><div><span style=3D"background-color: rgba(0, 0, 0, 0);">&nbsp; =
&nbsp; As for the question 6, the last paragraph in section 3 seems to des=
cribe the communication when T1 expires. Does it mean that when the mB4 is=
 responded in T1 there is no communication between NAS and AAA server?</sp=
an></div><div><span style=3D"background-color: rgba(0, 0, 0, 0);"><br></sp=
an></div><div><span style=3D"background-color: rgba(0, 0, 0, 0);">Best reg=
ards,</span></div><div>Linhui Sun</div>=0A<div><br></div><hr style=3D"widt=
h: 210px; height: 1px;" color=3D"#b5c4df" size=3D"1" align=3D"left">=0A<di=
v><span><div style=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt"=
><div>sunlinhui@bupt.edu.cn</div></div></span></div>=0A<blockquote style=
=3D"margin-top: 0px; margin-bottom: 0px; margin-left: 0.5em;"><div>&nbsp;<=
/div><div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0p=
t 0cm 0cm 0cm"><div style=3D"PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-S=
IZE: 12px;FONT-FAMILY:tahoma;COLOR:#000000; BACKGROUND: #efefef; PADDING-B=
OTTOM: 8px; PADDING-TOP: 8px"><div><b>=B7=A2=BC=FE=C8=CB=A3=BA</b>&nbsp;<a=
 href=3D"mailto:wang.cui1@zte.com.cn">wang.cui1</a></div><div><b>=B7=A2=CB=
=CD=CA=B1=BC=E4=A3=BA</b>&nbsp;2014-10-09&nbsp;15:42</div><div><b>=CA=D5=
=BC=FE=C8=CB=A3=BA</b>&nbsp;<a href=3D"mailto:sunlinhui@bupt.edu.cn">sunli=
nhui@bupt.edu.cn</a></div><div><b>=B3=AD=CB=CD=A3=BA</b>&nbsp;<a href=3D"m=
ailto:meng.wei2@zte.com.cn">meng.wei2</a>; <a href=3D"mailto:mohamed.bouca=
dair@orange.com">mohamed.boucadair</a>; <a href=3D"mailto:wang.cui1@zte.co=
m.cn">wang.cui1</a>; <a href=3D"mailto:wangqian@ctbri.com.cn">wangqian</a>=
; <a href=3D"mailto:softwires@ietf.org">softwires</a></div><div><b>=D6=F7=
=CC=E2=A3=BA</b>&nbsp;RE:Comments on draft-hu-softwire-multicast-radius-ex=
t</div></div></div><div><div class=3D"FoxDiv20141011093304594187"><font si=
ze=3D"2" face=3D"sans-serif">Hi, Linhui,</font>=0A<br>=0A<br><font size=3D=
"2" face=3D"sans-serif">&nbsp; Thanks for your comments. Please=0Asee inli=
ne.</font>=0A<br><font size=3D"2" face=3D"sans-serif">&nbsp; And all your =
comments we will=0Aupdate them in the next version.</font>=0A<br>=0A<br><f=
ont size=3D"2" face=3D"sans-serif">&nbsp; Many thanks.</font>=0A<br>=0A<br=
><font size=3D"2" face=3D"sans-serif">BRs</font>=0A<br><font size=3D"2" fa=
ce=3D"sans-serif">Linda Wang</font>=0A<br>=0A<br><tt><font size=3D"2">"sun=
linhui@bupt.edu.cn" &lt;sunlinhui@bupt.edu.cn&gt;=0A=D0=B4=D3=DA 2014-10-0=
6 11:38:50:<br>=0A<br>=0A&gt; "sunlinhui@bupt.edu.cn" &lt;sunlinhui@bupt.e=
du.cn&gt; </font></tt>=0A<br><tt><font size=3D"2">&gt; 2014-10-06 11:38</f=
ont></tt>=0A<br><tt><font size=3D"2">&gt; <br>=0A&gt; =CA=D5=BC=FE=C8=CB</=
font></tt>=0A<br><tt><font size=3D"2">&gt; <br>=0A&gt; meng.wei2@zte.com.c=
n, mohamed.boucadair@orange.com, <br>=0A&gt; wang.cui1@zte.com.cn, wangqia=
n@ctbri.com.cn, </font></tt>=0A<br><tt><font size=3D"2">&gt; <br>=0A&gt; =
=B3=AD=CB=CD</font></tt>=0A<br><tt><font size=3D"2">&gt; <br>=0A&gt; softw=
ires &lt;softwires@ietf.org&gt;</font></tt>=0A<br><tt><font size=3D"2">&gt=
; <br>=0A&gt; =D6=F7=CC=E2</font></tt>=0A<br><tt><font size=3D"2">&gt; <br=
>=0A&gt; Comments on draft-hu-softwire-multicast-radius-ext</font></tt>=0A=
<br><tt><font size=3D"2">&gt; <br>=0A&gt; Dear authors, <br>=0A&gt; <br>=
=0A&gt; I have read this document and think it is meaningful to propose a=
=0A<br>=0A&gt; new RADIUS attribute to carry the IPv6 prefixes together wi=
th the=0A<br>=0A&gt; DHCPv6 option defined in draft-ietf-softwire-multicas=
t-prefix-option-07.=0A<br>=0A&gt; <br>=0A&gt; Here are some comments about=
 this document. <br>=0A&gt; <br>=0A&gt; 1. The following paragraph repeats=
 twice (section 3 and section 4)=0A<br>=0A&gt; in this document. <br>=0A&g=
t; 'If the NAS does not receive the Multicast-Prefixes-64 attribute in=0A<=
br>=0A&gt; the Access-Accept message, it MAY fall back to a pre-configured=
 <br>=0A&gt; default Multicast-Prefixes-64, if any. If the NAS does not ha=
ve any=0A<br>=0A&gt; pre-configured, the delivery of multicast traffic is =
not supported.'=0A<br>=0A&gt; Do you think it is more suitable to remove t=
he repeated one in section=0A3? <br>=0A</font></tt><font size=3D"2" color=
=3D"blue">//Linda: I do agree with you. Thanks.</font>=0A<br>=0A<br><tt><f=
ont size=3D"2">&gt; <br>=0A&gt; 2. The architecture of this document seems=
 not very reasonable. Do=0A<br>=0A&gt; you think it could be of a better s=
tructure? Here are my suggestions.=0A<br>=0A&gt; a) The section 4 is inten=
ded to specify the new RADIUS attribute,=0Ait<br>=0A&gt; seems that the mo=
st content of the section 4.1 is describing the <br>=0A&gt; RADIUS client =
behavior. Do you think it is appropriate to treat this<br>=0A&gt; part as =
a separate section called the Client Behavior. <br>=0A&gt; b) And I think =
the sequence of the sections could be modified to <br>=0A&gt; become bette=
r organized. The section RADIUS Attribute could be <br>=0A&gt; introduced =
first, then the section Client Behavior would be <br>=0A&gt; discussed lat=
er. While the Multicast-Prefixes-64 Configuration with=0A<br>=0A&gt; RADIU=
S and DHCPv6 section is more appropriate to locate in the rear=0A<br>=0A&g=
t; of those two sections. </font></tt>=0A<br><tt><font size=3D"2" color=3D=
"blue">//Linda: Originally, we considered it would=0Abe clearer to present=
 the </font></tt>=0A<br><tt><font size=3D"2" color=3D"blue">the whole mess=
age exchange flow first,=0Athen follow this flow, readers </font></tt>=0A<=
br><tt><font size=3D"2" color=3D"blue">can catch a better understanding of=
 where=0A</font></tt><font size=3D"2" color=3D"blue">this attribute</font>=
<tt><font size=3D"2" color=3D"blue">=0Awould be brought</font></tt>=0A<br>=
<tt><font size=3D"2" color=3D"blue">with and how </font></tt><font size=3D=
"2" color=3D"blue">this=0Aattribute</font><tt><font size=3D"2" color=3D"bl=
ue"> would be used. After that,=0Awe illustrated the </font></tt>=0A<br><t=
t><font size=3D"2" color=3D"blue">format of this attribute naturally. Do=
=0Ayou think this can explain </font></tt>=0A<br><tt><font size=3D"2" colo=
r=3D"blue">why we presented this draft in this structure?</font></tt>=0A<b=
r><tt><font size=3D"2" color=3D"blue">As for your proposal about section 4=
.1,=0Ain fact, in this section we wanted </font></tt>=0A<br><tt><font size=
=3D"2" color=3D"blue">to emphasize the changed details which=0Awere caused=
 by this new attribute,</font></tt>=0A<br><tt><font size=3D"2" color=3D"bl=
ue">not emphasize the separated client behavior=0Aor server behavior. So w=
e </font></tt>=0A<br><tt><font size=3D"2" color=3D"blue">integrated them t=
ogether. </font></tt>=0A<br><tt><font size=3D"2" color=3D"blue">But, we st=
ill will carefully consider your=0Aproposal structure later. Thanks. </fon=
t></tt>=0A<br><tt><font size=3D"2"><br>=0A&gt; <br>=0A&gt; 3. The =A1=AEDH=
CPv6 Advertisement=A1=AF in Figure 1,2 could be modified=0Aas <br>=0A&gt; =
=A1=AEDHCPv6 Advertise=A1=AF in a more standardized way according to the=
=0ARFC 3315. </font></tt>=0A<br><tt><font size=3D"2" color=3D"blue">//Lind=
a: I do agree with you. Thanks.</font></tt>=0A<br><tt><font size=3D"2"><br=
>=0A&gt; <br>=0A&gt; 4. There seems to be a conflict between the figure 1 =
and its <br>=0A&gt; corresponding description. <br>=0A&gt; From the Figure=
 1, we can conclude that the DHCPv6 Advertise message<br>=0A&gt; carries t=
he DHCPv6 OPTION_PREFIX64 option. <br>=0A&gt; However, if we refer to the =
content, it states that =A1=AEthe NAS SHALL=0A<br>=0A&gt; use the prefixes=
 returned in the RADIUS Multicast-Prefixes-64 <br>=0A&gt; attribute to pop=
ulate the DHCPv6 OPTION_PREFIX64 option in the <br>=0A&gt; DHCPv6 reply me=
ssage=A1=AF in section 3. <br>=0A&gt; Do you think it could be better to k=
eep the consistence between the=0A<br>=0A&gt; figure and its description. =
</font></tt>=0A<br><tt><font size=3D"2" color=3D"blue">//Linda: I do agree=
 with you. Thanks.</font></tt><tt><font size=3D"2"><br>=0A&gt; </font></tt=
>=0A<br><tt><font size=3D"2"><br>=0A&gt; 5. Could you please explain why t=
he DHCPv6 Request message in the=0A<br>=0A&gt; Figure 2 does not carry a D=
HCPv6 OPTION_PREFIX64? </font></tt>=0A<br><tt><font size=3D"2" color=3D"bl=
ue">//Linda: Yes, you are right. The DHCPv6=0ARequest message should carry=
 this option.</font></tt><tt><font size=3D"2"><br>=0A&gt; </font></tt>=0A<=
br><tt><font size=3D"2"><br>=0A&gt; 6. Do you think it is necessary to add=
 a separate paragraph that <br>=0A&gt; defines how the NAS will communicat=
e with the AAA server when the=0A<br>=0A&gt; mB4 is at its DHCP renew stag=
e to make the document more comprehensive?=0A</font></tt>=0A<br><tt><font =
size=3D"2" color=3D"blue">//Linda: In the last paragraph in section=0A3, w=
e explain the DHCP RENEW stage, do</font></tt>=0A<br><tt><font size=3D"2" =
color=3D"blue">you think it is enough for your question?</font></tt>=0A<br=
><tt><font size=3D"2"><br>=0A&gt; <br>=0A&gt; Best regards, <br>=0A&gt; Li=
nhui Sun <br>=0A</font></tt>=0A<br><tt><font size=3D"2">&gt; <br>=0A&gt; s=
unlinhui@bupt.edu.cn</font></tt>=0A</div></div></blockquote>=0A</body></ht=
ml>
------=_001_NextPart032158725074_=------


From nobody Sat Oct 11 11:45:17 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA80F1A8701; Sat, 11 Oct 2014 11:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVX60tX0NdD7; Sat, 11 Oct 2014 11:45:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F1B5D1A6FC8; Sat, 11 Oct 2014 11:45:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141011184514.422.63351.idtracker@ietfa.amsl.com>
Date: Sat, 11 Oct 2014 11:45:14 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/twR4fSVu7UuwVZBkuQraM5mLj7g
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-map-dhcp-09.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 11 Oct 2014 18:45:15 -0000

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

        Title           : DHCPv6 Options for configuration of Softwire Address and Port Mapped Clients
        Authors         : Tomasz Mrugalski
                          Ole Troan
                          Ian Farrer
                          Simon Perreault
                          Wojciech Dec
                          Congxiao Bao
                          Leaf Y. Yeh
                          Xiaohong Deng
	Filename        : draft-ietf-softwire-map-dhcp-09.txt
	Pages           : 17
	Date            : 2014-10-11

Abstract:
   This document specifies DHCPv6 options, termed Softwire46 options,
   for the provisioning of Softwire46 Customer Edge (CE) devices.
   Softwire46 is a collective term used to refer to architectures based
   on the notion of IPv4 Address+Port (A+P) for providing IPv4
   connectivity across an IPv6 network.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-dhcp-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Sat Oct 11 18:23:44 2014
Return-Path: <david.black@emc.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 559CD1A8827; Sat, 11 Oct 2014 15:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.487
X-Spam-Level: 
X-Spam-Status: No, score=-4.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KdqG7Z-8FaB5; Sat, 11 Oct 2014 15:31:30 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72D771A882A; Sat, 11 Oct 2014 15:31:29 -0700 (PDT)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9BMUhXC029517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Oct 2014 18:30:43 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s9BMUhXC029517
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1413066645; bh=6qPzFBo5nEK2qGP7FwEwrpkGrFE=; h=From:To:CC:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=sS3/ySHXaZcfdCfjpJcD5Cy6fJgQAVoawBqik3Z+1pQFVqQ+CtMLQVsXZy4WyClqs 8+mqlaQeYsQS5A6JvU4ra10T+n3FjjDTcxxBeeSZZaaMQy8WljQdI3aQo50+xpcPe1 AFf0de1djIiC0uH+mHbtq7AhYK2zMtP9BpKxk2ng=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s9BMUhXC029517
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd01.lss.emc.com (RSA Interceptor); Sat, 11 Oct 2014 18:30:15 -0400
Received: from mxhub37.corp.emc.com (mxhub37.corp.emc.com [128.222.70.104]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9BMURg0023438 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 11 Oct 2014 18:30:27 -0400
Received: from MXHUB102.corp.emc.com (10.253.58.15) by mxhub37.corp.emc.com (128.222.70.104) with Microsoft SMTP Server (TLS) id 8.3.327.1; Sat, 11 Oct 2014 18:30:27 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Sat, 11 Oct 2014 18:30:27 -0400
From: "Black, David" <david.black@emc.com>
To: "yong@csnet1.cs.tsinghua.edu.cn" <yong@csnet1.cs.tsinghua.edu.cn>, "sunqiong@ctbri.com.cn" <sunqiong@ctbri.com.cn>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "tena@huawei.com" <tena@huawei.com>, "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>, "ian.farrer@telekom.de" <ian.farrer@telekom.de>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>
Thread-Topic: Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
Thread-Index: Ac/lou8B9zKSJooyTsOMrMdwtE6r4A==
Date: Sat, 11 Oct 2014 22:30:26 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.105.59.98]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: DLM_1, public, GIS Solicitation
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/LcOr34jFpNT5EEMknDN8z7N91l0
X-Mailman-Approved-At: Sat, 11 Oct 2014 18:23:42 -0700
Cc: "softwires@ietf.org" <softwires@ietf.org>, "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 11 Oct 2014 22:31:34 -0000

This is a combined Gen-ART and OPS-DIR review.  Boilerplate for both follow=
s,
and I apologize for it being a day late - United Airlines got me back to
Boston after midnight last night on a plane w/o working WiFi.

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at:

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

I have reviewed this document as part of the Operational directorate's ongo=
ing
effort to review all IETF documents being processed by the IESG.  These com=
ments
were written primarily for the benefit of the operational area directors.
Document editors and WG chairs should treat these comments just like any ot=
her
last call comments.

Document: draft-ietf-softwire-lw4over6-10
Reviewer: David Black
Review Date: October 10, 2014
IETF LC End Date: October 10, 2014
IESG Telechat date: October 16, 2014

Summary: This draft is on the right track, but has open issues
 		described in the review.

This draft describes an extension to Dual-Stack Lite that relocates the NAP=
T
functionality from the centralized tunnel concentrator to the DS-Lite clien=
t
- doing so has significant scalability benefits.  The draft is generally
readable although understanding why some of the processing needs to be done
in the manner specified requires strong familiarity with both DS-Lite and
NAPT.

The draft is generally in good shape - I found three issues that I consider
to be significant, the most important of which are sloppiness in use of
RFC 2119 keywords, particularly in Section 5.1, and omission of what
appears to be a necessary normative reference.

Major issues (2):

[1] There are a number of places where SHOULD is used to refer to requireme=
nt
in another RFC, e.g., the following text in section 5.1:

   The DNS considerations described in Section 5.5 and Section 6.4 of
   [RFC6333] SHOULD be followed.

This has the side effect of weakening any MUST requirement in the reference=
d
RFC(s) to a SHOULD, which was probably not intended, and needs to be explic=
itly
stated if it was intended.  Here's a possible rephrasing:

   The DNS considerations described in Section 5.5 and Section 6.4 of
   [RFC6333] apply to Lightweight 4over6; lw4o6 implementations MUST
   comply with all requirements stated there.

The additional places where this occurs are:

- Section 5.2.1 (twice):

   For TCP and UDP traffic the NAPT44 implemented in the lwB4 SHOULD
   conform with the behaviour and best current practices documented in
   [RFC4787], [RFC5508], and [RFC5382].  If the lwB4 supports DCCP, then
   the requirements in [RFC5597] SHOULD be implemented.

- Section 8.2:

   The lwB4 SHOULD implement the requirements defined in [RFC5508] for
   ICMP forwarding.

[2] Section 4.  Lightweight 4over6 Architecture

   The consequence of this architecture is that the information
   maintained by the provisioning mechanism and the one maintained by
   the lwAFTR MUST be synchronized (See figure 2).  The details of this
   synchronization depend on the exact provisioning mechanism and will
   be discussed in a companion document.

I believe that this "companion document" needs to be cited as a
normative reference.  The above text's vague allusion to the specification
of how to implement a "MUST" requirement is insufficient.

Minor issues (7):

[3] The lack of discussion of management information is an
omission.  See A.2.2 below in the OPS-Dir review section of this email
and the discussion in Section 3.2 of RFC 5706.  A sentence pointing
at an applicable MIB and/or YANG draft or drafts would suffice.

[4] Section 4.  Lightweight 4over6 Architecture

   The solution specified in this document allows the assignment of
   either a full or a shared IPv4 address requesting CPEs.  [RFC7040]
   provides a mechanism for assigning a full IPv4 address only.

Please explain what entities would share the IPv4 address.  For example,
this is needed as a foundation for the statement in Section 8 that
"ICMPv4 does not work in an address sharing environment without
special handling [RFC6269]."

[5] Section 5.1.  Lightweight B4 Provisioning with DHCPv6

   For DHCPv6 based configuration of these parameters, the lwB4 SHOULD
   implement OPTION_S46_CONT_LW

What are the consequences of not doing that?  The could be addressed
by changing that "SHOULD" to a "MUST", although I suspect that what's
wanted here is a forward reference to the alternatives discussed in
Section 7.

[6] Also in Section 5.1

   If stateful IPv4 configuration or additional IPv4 configuration
   information is required, DHCPv4 [RFC2131] must be used.

"must" -> "MUST"

   In the event that the lwB4's encapsulation source address is changed
   for any reason (such as the DHCPv6 lease expiring), the lwB4's
   dynamic provisioning process must be re-initiated.

"must" -> "MUST"

[7] Also in Section 5.1

   Unless an lwB4 is being allocated a full IPv4 address, it is
   RECOMMENDED that PSIDs containing the well-known ports (0-1023) are
   not allocated to lwB4s.

Please explain why.  Also, "well-known ports" is not the right term;
I believe those are the "system ports", e.g., see:

http://www.iana.org/assignments/service-names-port-numbers/service-names-po=
rt-numbers.xhtml


[8] Still in Section 5.1

   In the event that the lwB4 receives an ICMPv6 error message (type 1,
   code 5) originating from the lwAFTR, the lwB4 SHOULD interpret this
   to mean that no matching entry in the lwAFTR's binding table has been
   found.  The lwB4 MAY then re-initiate the dynamic port-restricted
   provisioning process.  The lwB4's re-initiation policy SHOULD be
   configurable.

What happens if the lwB4 ignores the first "SHOULD"?

[9] Section 8.1.  ICMPv4 Processing by the lwAFTR

This describes two approaches to ICMPv4 processing.  Are there any others?
If so, please add some text about them, otherwise, I suggest this change:

OLD
   Additionally, the lwAFTR MAY implement:

   o  Discarding of all inbound ICMP messages.
NEW
   Otherwise the lwAFTR MUST discard all inbound ICMPv4 messages.


Nits/editorial comments:

-- Section 1.  Introduction

   Basic Bridging BroadBand element: A B4 element is a function
                                     implemented on a dual-stack capable
                                     node, either a directly connected
                                     device or a CPE, that creates a
                                     tunnel to an AFTR.

I suggest changing "a tunnel to an AFTR" to "an IPv4-in-IPv6 tunnel
to an AFTR" for consistency with the AFTR definition.

-- Section 5.2.  Lightweight B4 Data Plane Behavior

   Internally connected hosts source IPv4 packets with an [RFC1918]
   address.

Internal to what?  Please explain.

-- Section 6.2.  lwAFTR Data Plane Behavior

   The lwAFTR MUST support hairpinning of traffic between two lwB4s, by
   performing de-capsulation and re-encapsulation of packets.  The
   hairpinning policy MUST be configurable.

Please explain "hairpinning" - it should suffice to add "from one lwB4
that need to be sent to another lwB4 associated with the same AFTR"
after "de-capsulation and re-encapsulation of packets".

-- Section 7.  Additional IPv4 address and Port Set Provisioning Mechanisms

   In a Lightweight 4over6 domain, the binding information MUST be
   aligned between the lwB4s, the lwAFTRs and the provisioning server.

"aligned between" -> "synchronized across" for consistency with use
of forms of "synchronize" elsewhere in this draft.

idnits found a few things to complain about:

- The use of "the well-known range 192.0.0.0/29" in Section 5.1.  This is o=
k,
	as it's describing DS-Lite use of that range that is documented
	elsewhere.  If lw4o6 is using that range, an explanation ought to be
	added to Section 5.1.

- Three references have been updated:

  =3D=3D Outdated reference: A later version (-09) exists of
     draft-ietf-softwire-map-dhcp-07

  =3D=3D Outdated reference: draft-ietf-dhc-dhcpv4-over-dhcpv6 has been pub=
lished
     as RFC 7341

  =3D=3D Outdated reference: A later version (-06) exists of
     draft-ietf-pcp-port-set-05

--- Selected RFC 5706 Appendix A Q&A for OPS-Dir review ---

A.1.1.  Has deployment been discussed?

	Yes, this protocol is intended to improve scalability over the existing
	DS-Lite mechanism.

A.1.2.  Has installation and initial setup been discussed?

	No, there are vague references to a provisioning mechanism and
	synchronization functionality that need to be set up.  See
	major open issue [2] above which calls out a missing normative
	reference that should address these topics.

A.1.3.  Has the migration path been discussed?

	No, but I suspect that this concern is inapplicable, as I think
	a carrier would not migrate from DS-Lite to lw4o6, but would
	deploy lw4o6 instead of DS-Lite.

A.1.4.  Have the Requirements on other protocols and functional
       components been discussed?

	Yes, but major open issue [1] is effectively in this area.

A.1.6.  Have suggestions for verifying correct operation been discussed?

	No, and they probably should be, as this protocol requires state
	synchronization among the lwB4, lwAFTR and the provisioning system,
	and is likely to exhibit problematic behavior if the relevant state
	information gets out of sync.

A.1.9.  Is configuration discussed?

	Yes, the draft does a good job of discussing what needs to be
	configured to set up the protocol (aside from state synchronization)
	and calling out protocol behavior aspects that should be configurable.

A.2 Management

	This is really not discussed, and in particular the lack of discussion
	of management information is notable because this protocol has a
	different operational structure than DS-Lite.  So, specifically:

 A.2.2.  Is management information discussed?

	No, this is minor open issue [3].  A sentence pointing to applicable
	MIB and/or YANG draft(s) would suffice to address this.

A.2.4.  Is configuration management discussed?

	Yes - the discussion is ok, even though specific configuration mechanisms
	are not discussed.

A.3.  Documentation

	The protocol does have significant operational impacts on the Internet.

	The shepherd's writeup indicates that multiple implementations exist
	among which interoperability has been tested.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From nobody Sun Oct 12 18:54:50 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D25DB1A9233; Sun, 12 Oct 2014 18:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAgTVfYwbz5w; Sun, 12 Oct 2014 18:54:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 722261A9166; Sun, 12 Oct 2014 18:54:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141013015447.9195.86899.idtracker@ietfa.amsl.com>
Date: Sun, 12 Oct 2014 18:54:47 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/IyFwbWKFi2t_X2594T6qL28cgDg
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-4rd-09.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 13 Oct 2014 01:54:49 -0000

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

        Title           : IPv4 Residual Deployment via IPv6 - a Stateless Solution (4rd)
        Authors         : Remi Despres
                          Sheng Jiang
                          Reinaldo Penno
                          Yiu Lee
                          Gang Chen
                          Maoke Chen
	Filename        : draft-ietf-softwire-4rd-09.txt
	Pages           : 40
	Date            : 2014-10-12

Abstract:
   For service providers to progressively deploy IPv6-only network
   domains while still offering IPv4 service to customers, this document
   specifies a stateless solution.  Its distinctive property is that
   TCP/UDP IPv4 packets are valid TCP/UDP IPv6 packets during domain
   traversal, and that IPv4 fragmentation rules are fully preserved end-
   to-end.  Each customer can be assigned one public IPv4 address, or
   several, or a shared address with a restricted port set.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-4rd-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Sun Oct 12 19:35:19 2014
Return-Path: <gnocuil@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB1691A923B for <softwires@ietfa.amsl.com>; Sun, 12 Oct 2014 19:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 69V4h8ztEKB2 for <softwires@ietfa.amsl.com>; Sun, 12 Oct 2014 19:35:16 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 031071A7018 for <softwires@ietf.org>; Sun, 12 Oct 2014 19:35:15 -0700 (PDT)
Received: by mail-oi0-f47.google.com with SMTP id a141so12064430oig.20 for <softwires@ietf.org>; Sun, 12 Oct 2014 19:35:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=85wBP9uYh6j9pk7IRNEU0wzqJSzRLnc9sp7Kw9/fhZE=; b=Yopjgv7BWGbaLRbG3076zyz2pcW4YtIUd139tP97C+cgwMeQ2EUV02IlQhC/LMO79R 0ZYDuIXXHfUrgrMoahzHXhyBhLakiFbddLWLkEyMLdaMPhohQsrSi2dkdCaoRefe6wmZ 80j1waFjS8mLfU4janV62ZDkj+cvqUAo95bwIMGv2eHQkNWwls6PTxFozqYUIUUUT9dQ W0xbhsVScWcEeyPA2uf6XYbEmhh4NyL0Cz4myavG2Z9ECIMFEPVrM1REEZhBFVoxaw01 XT9Pd3Lg/ju+wmeCqDJEYaKVs5vSeFoGcBwvPiC+HFI93dA8+EtacWiRfH7WqqbUzdsG Bx0w==
X-Received: by 10.182.104.104 with SMTP id gd8mr18458093obb.17.1413167715151;  Sun, 12 Oct 2014 19:35:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.104.209 with HTTP; Sun, 12 Oct 2014 19:34:55 -0700 (PDT)
In-Reply-To: <20141013014223.2340.69720.idtracker@ietfa.amsl.com>
References: <20141013014223.2340.69720.idtracker@ietfa.amsl.com>
From: Cong Liu <gnocuil@gmail.com>
Date: Mon, 13 Oct 2014 10:34:55 +0800
Message-ID: <CAF+sHxHBfht31FrT7+e+xkjUEcit8UdojRQZnbwJWVtVqL-R5A@mail.gmail.com>
To: softwires <softwires@ietf.org>
Content-Type: multipart/alternative; boundary=089e01160bf8ab7460050544bf0d
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/vf2TOWYpFWX4aoUapFySbdRpNRw
Subject: [Softwires] Fwd: Confirm submission of I-D draft-liu-softwire-lw4over6-dhcp-deployment
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 13 Oct 2014 02:35:17 -0000

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

Dear all,

We have updated the LW4over6 dynamic IPv4 provisioning draft. The major
change is to reference dhcp active lease query for lwAFTR binding table
maintenance.

Please could you review the draft and any comments are more than welcome.

Best Regards,
Cong

---------- Forwarded message ----------
From: IETF I-D Submission Tool <idsubmission@ietf.org>
Date: 2014-10-13 9:42 GMT+08:00
Subject: Confirm submission of I-D
draft-liu-softwire-lw4over6-dhcp-deployment
To: Cong Liu <gnocuil@gmail.com>, Qi Sun <sunqi@csnet1.cs.tsinghua.edu.cn>,
Jianping Wu <jianping@cernet.edu.cn>



Hi,

The IETF datatracker draft submission service has received your draft
draft-liu-softwire-lw4over6-dhcp-deployment-05, and requires a
confirmation step in order to be able to complete the posting of
the draft.

Please follow this link to the page where you can confirm the posting:

http://datatracker.ietf.org/submit/status/63483/confirm/0b20f72639dd8b0ed256dfb65388f1f1/


Best regards,

        The IETF Secretariat
        through the draft submission service

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

<div dir=3D"ltr">Dear all,<div><br></div><div>We have updated the LW4over6 =
dynamic IPv4 provisioning draft. The major change is to reference dhcp acti=
ve lease query for lwAFTR binding table=C2=A0<span style=3D"color:rgb(0,0,0=
);font-size:1em">maintenance.</span></div><div><span style=3D"color:rgb(0,0=
,0);font-size:1em"><br></span></div><div><span style=3D"color:rgb(0,0,0);fo=
nt-size:1em">Please could you review the draft and any comments are more th=
an welcome.</span></div><div><span style=3D"color:rgb(0,0,0);font-size:1em"=
><br></span></div><div><span style=3D"color:rgb(0,0,0);font-size:1em">Best =
Regards,</span></div><div><span style=3D"color:rgb(0,0,0);font-size:1em">Co=
ng</span></div><div><br><div class=3D"gmail_quote">---------- Forwarded mes=
sage ----------<br>From: <b class=3D"gmail_sendername">IETF I-D Submission =
Tool</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:idsubmission@ietf.org">ids=
ubmission@ietf.org</a>&gt;</span><br>Date: 2014-10-13 9:42 GMT+08:00<br>Sub=
ject: Confirm submission of I-D draft-liu-softwire-lw4over6-dhcp-deployment=
<br>To: Cong Liu &lt;<a href=3D"mailto:gnocuil@gmail.com">gnocuil@gmail.com=
</a>&gt;, Qi Sun &lt;<a href=3D"mailto:sunqi@csnet1.cs.tsinghua.edu.cn">sun=
qi@csnet1.cs.tsinghua.edu.cn</a>&gt;, Jianping Wu &lt;<a href=3D"mailto:jia=
nping@cernet.edu.cn">jianping@cernet.edu.cn</a>&gt;<br><br><br><br>
Hi,<br>
<br>
The IETF datatracker draft submission service has received your draft<br>
draft-liu-softwire-lw4over6-dhcp-deployment-05, and requires a<br>
confirmation step in order to be able to complete the posting of<br>
the draft.<br>
<br>
Please follow this link to the page where you can confirm the posting:<br>
<br>
<a href=3D"http://datatracker.ietf.org/submit/status/63483/confirm/0b20f726=
39dd8b0ed256dfb65388f1f1/" target=3D"_blank">http://datatracker.ietf.org/su=
bmit/status/63483/confirm/0b20f72639dd8b0ed256dfb65388f1f1/</a><br>
<br>
<br>
Best regards,<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The IETF Secretariat<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 through the draft submission service<br>
<br>
<br>
</div><br></div></div>

--089e01160bf8ab7460050544bf0d--


From nobody Sun Oct 12 19:37:59 2014
Return-Path: <gnocuil@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA7D21A923C for <softwires@ietfa.amsl.com>; Sun, 12 Oct 2014 19:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jr9TUq2NQqRT for <softwires@ietfa.amsl.com>; Sun, 12 Oct 2014 19:37:54 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F83F1A7018 for <softwires@ietf.org>; Sun, 12 Oct 2014 19:37:53 -0700 (PDT)
Received: by mail-oi0-f48.google.com with SMTP id g201so11829544oib.21 for <softwires@ietf.org>; Sun, 12 Oct 2014 19:37:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=vBCvi87ZOEWXlB3pbr+J46md+Zd7Lu73mcVG0yEYtcI=; b=XM/IqCwqwZDPFSQefe49v8L+Pt+aHEMEDqK520Vs3S95r/oaSr/OkiBzhrGlhiw/NK CE/S945G1Z4g1gjnqo0Dr20oi3PPYGFysDgg6eHCpk6l6vW/z23DrFi7Bh9Hke2jmOMO +89OsaqnYKXLmwh7/egSNll2gCtQnh5e98rkjrBbOCViqwFbfkJoe01t/9dJ1c3SViUd mioAKKHTIxxhrpEQXAd0Iqic94lUgY0+eQD8sYkPvth+fMCpW2/WkrEyvrlwuPJnYUs5 EPV9z5WjU/LOfGWLE4KPF2qTC7d2x3R/Porkyor9HHIBP2gz154O2DZn06jBmtH8/z0c r9Ng==
X-Received: by 10.60.177.231 with SMTP id ct7mr19044898oec.8.1413167872758; Sun, 12 Oct 2014 19:37:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.104.209 with HTTP; Sun, 12 Oct 2014 19:37:32 -0700 (PDT)
In-Reply-To: <20141013014246.4481.28222.idtracker@ietfa.amsl.com>
References: <20141013014246.4481.28222.idtracker@ietfa.amsl.com>
From: Cong Liu <gnocuil@gmail.com>
Date: Mon, 13 Oct 2014 10:37:32 +0800
Message-ID: <CAF+sHxFgp01yKA0GWepDQTK230fG6+z4D1+D+Y1x_wAvHttPnQ@mail.gmail.com>
To: softwires <softwires@ietf.org>
Content-Type: multipart/alternative; boundary=089e01182fc4105c17050544c9c4
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/BLZGbKU761V2aoL7H14Gpcfx8mo
Subject: [Softwires] Fwd: New Version Notification for draft-liu-softwire-lw4over6-dhcp-deployment-05.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 13 Oct 2014 02:37:56 -0000

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

Dear all,

We have updated the LW4over6 dynamic IPv4 provisioning draft. The major
change is to reference dhcp active lease query for lwAFTR binding table
maintenance.

Please could you review the draft and any comments are more than welcome.

Best Regards,
Cong

//Sorry for forwarded the wrong one
---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: 2014-10-13 9:42 GMT+08:00
Subject: New Version Notification for
draft-liu-softwire-lw4over6-dhcp-deployment-05.txt
To: Jianping Wu <jianping@cernet.edu.cn>, Cong Liu <gnocuil@gmail.com>, Qi
Sun <sunqi@csnet1.cs.tsinghua.edu.cn>



A new version of I-D, draft-liu-softwire-lw4over6-dhcp-deployment-05.txt
has been successfully submitted by Cong Liu and posted to the
IETF repository.

Name:           draft-liu-softwire-lw4over6-dhcp-deployment
Revision:       05
Title:          Dynamic IPv4 Provisioning for Lightweight 4over6
Document date:  2014-10-12
Group:          Individual Submission
Pages:          8
URL:
http://www.ietf.org/internet-drafts/draft-liu-softwire-lw4over6-dhcp-deployment-05.txt
Status:
https://datatracker.ietf.org/doc/draft-liu-softwire-lw4over6-dhcp-deployment/
Htmlized:
http://tools.ietf.org/html/draft-liu-softwire-lw4over6-dhcp-deployment-05
Diff:
http://www.ietf.org/rfcdiff?url2=draft-liu-softwire-lw4over6-dhcp-deployment-05

Abstract:
   Lightweight 4over6 [I-D.ietf-softwire-lw4over6] is an IPv4 over IPv6
   hub and spoke mechanism that provides overlay IPv4 services in an
   IPv6-only access network.  Provisioning IPv4 addresses and port set
   to customers is the core function of Lightweight 4over6 control
   plane.  [I-D.ietf-softwire-lw4over6] illustrates how to use DHCPv6
   for deterministic IPv4 provisioning.  This document discusses how to
   provision IPv4 parameters by using dynamic IPv4 provisioning
   protocols such as DHCPv4 over DHCPv6 [RFC7341].  This document
   describes a dynamic IPv4 provisioning mode for Lightweight 4over6
   that uses DHCPv4 over DHCPv6 [RFC7341] for IPv4 address provisioning.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

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

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:14px=
">Dear all,</span><div style=3D"font-family:arial,sans-serif;font-size:14px=
"><br></div><div style=3D"font-family:arial,sans-serif;font-size:14px">We h=
ave updated the LW4over6 dynamic IPv4 provisioning draft. The major change =
is to reference dhcp active lease query for lwAFTR binding table=C2=A0<span=
 style=3D"color:rgb(0,0,0);font-size:1em">maintenance.</span></div><div sty=
le=3D"font-family:arial,sans-serif;font-size:14px"><span style=3D"color:rgb=
(0,0,0);font-size:1em"><br></span></div><div style=3D"font-family:arial,san=
s-serif;font-size:14px"><span style=3D"color:rgb(0,0,0);font-size:1em">Plea=
se could you review the draft and any comments are more than welcome.</span=
></div><div style=3D"font-family:arial,sans-serif;font-size:14px"><span sty=
le=3D"color:rgb(0,0,0);font-size:1em"><br></span></div><div style=3D"font-f=
amily:arial,sans-serif;font-size:14px"><span style=3D"color:rgb(0,0,0);font=
-size:1em">Best Regards,</span></div><div style=3D"font-family:arial,sans-s=
erif;font-size:14px"><span style=3D"color:rgb(0,0,0);font-size:1em">Cong</s=
pan></div><div style=3D"font-family:arial,sans-serif;font-size:14px"><span =
style=3D"color:rgb(0,0,0);font-size:1em"><br></span></div><div style=3D"fon=
t-family:arial,sans-serif;font-size:14px"><span style=3D"color:rgb(0,0,0);f=
ont-size:1em">//Sorry for forwarded the wrong one</span></div><div class=3D=
"gmail_quote">---------- Forwarded message ----------<br>From: <b class=3D"=
gmail_sendername"></b> <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-dra=
fts@ietf.org">internet-drafts@ietf.org</a>&gt;</span><br>Date: 2014-10-13 9=
:42 GMT+08:00<br>Subject: New Version Notification for draft-liu-softwire-l=
w4over6-dhcp-deployment-05.txt<br>To: Jianping Wu &lt;<a href=3D"mailto:jia=
nping@cernet.edu.cn">jianping@cernet.edu.cn</a>&gt;, Cong Liu &lt;<a href=
=3D"mailto:gnocuil@gmail.com">gnocuil@gmail.com</a>&gt;, Qi Sun &lt;<a href=
=3D"mailto:sunqi@csnet1.cs.tsinghua.edu.cn">sunqi@csnet1.cs.tsinghua.edu.cn=
</a>&gt;<br><br><br><br>
A new version of I-D, draft-liu-softwire-lw4over6-dhcp-deployment-05.txt<br=
>
has been successfully submitted by Cong Liu and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-liu-softwire-lw4over6-d=
hcp-deployment<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A005<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Dynamic IPv4 Provisioning for Ligh=
tweight 4over6<br>
Document date:=C2=A0 2014-10-12<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://www.ietf.or=
g/internet-drafts/draft-liu-softwire-lw4over6-dhcp-deployment-05.txt" targe=
t=3D"_blank">http://www.ietf.org/internet-drafts/draft-liu-softwire-lw4over=
6-dhcp-deployment-05.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-liu-softwire-lw4over6-dhcp-deployment/" target=3D"_blank">h=
ttps://datatracker.ietf.org/doc/draft-liu-softwire-lw4over6-dhcp-deployment=
/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://tools.ietf.org/html/d=
raft-liu-softwire-lw4over6-dhcp-deployment-05" target=3D"_blank">http://too=
ls.ietf.org/html/draft-liu-softwire-lw4over6-dhcp-deployment-05</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.ietf.or=
g/rfcdiff?url2=3Ddraft-liu-softwire-lw4over6-dhcp-deployment-05" target=3D"=
_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-liu-softwire-lw4over6-dhcp=
-deployment-05</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0Lightweight 4over6 [I-D.ietf-softwire-lw4over6] is an IPv4 ove=
r IPv6<br>
=C2=A0 =C2=A0hub and spoke mechanism that provides overlay IPv4 services in=
 an<br>
=C2=A0 =C2=A0IPv6-only access network.=C2=A0 Provisioning IPv4 addresses an=
d port set<br>
=C2=A0 =C2=A0to customers is the core function of Lightweight 4over6 contro=
l<br>
=C2=A0 =C2=A0plane.=C2=A0 [I-D.ietf-softwire-lw4over6] illustrates how to u=
se DHCPv6<br>
=C2=A0 =C2=A0for deterministic IPv4 provisioning.=C2=A0 This document discu=
sses how to<br>
=C2=A0 =C2=A0provision IPv4 parameters by using dynamic IPv4 provisioning<b=
r>
=C2=A0 =C2=A0protocols such as DHCPv4 over DHCPv6 [RFC7341].=C2=A0 This doc=
ument<br>
=C2=A0 =C2=A0describes a dynamic IPv4 provisioning mode for Lightweight 4ov=
er6<br>
=C2=A0 =C2=A0that uses DHCPv4 over DHCPv6 [RFC7341] for IPv4 address provis=
ioning.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div>

--089e01182fc4105c17050544c9c4--


From nobody Mon Oct 13 02:37:34 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F9C41A8943; Mon, 13 Oct 2014 02:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X4iqROvSz2UM; Mon, 13 Oct 2014 02:37:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F251A1A8937; Mon, 13 Oct 2014 02:37:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141013093729.26321.32947.idtracker@ietfa.amsl.com>
Date: Mon, 13 Oct 2014 02:37:29 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/-bBsb_o-dSKyhx-PD5mIi161Xag
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-map-11.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 13 Oct 2014 09:37:31 -0000

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

        Title           : Mapping of Address and Port with Encapsulation (MAP)
        Authors         : Ole Troan
                          Wojciech Dec
                          Xing Li
                          Congxiao Bao
                          Satoru Matsushima
                          Tetsuya Murakami
                          Tom Taylor
	Filename        : draft-ietf-softwire-map-11.txt
	Pages           : 32
	Date            : 2014-10-13

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-11

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


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Mon Oct 13 02:40:46 2014
Return-Path: <otroan@employees.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7DA1A8912 for <softwires@ietfa.amsl.com>; Mon, 13 Oct 2014 02:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XUEmPJxNwbzx for <softwires@ietfa.amsl.com>; Mon, 13 Oct 2014 02:40:43 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 870461A890F for <softwires@ietf.org>; Mon, 13 Oct 2014 02:40:42 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqoEAAOdO1StJssW/2dsb2JhbABbg2FTBcsaCoZ5VAKBMQF9hAIBAQEDAQEBATc0EAsLGC4nMAYTCYgtCAgFw2EBAQEBAQEBAQEBAQEBAQEBAQEBAQEXkBI6gy2BHgWWO4g+PIMKkR2DeTsvgkoBAQE
X-IronPort-AV: E=Sophos;i="5.04,709,1406592000"; d="scan'208";a="208856035"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 13 Oct 2014 09:40:41 +0000
Received: from dhcp-10-61-101-249.cisco.com (dhcp-10-61-101-249.cisco.com [10.61.101.249]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s9D9eeHl008305 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <softwires@ietf.org>; Mon, 13 Oct 2014 09:40:40 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <20141013093729.26321.32947.idtracker@ietfa.amsl.com>
Date: Mon, 13 Oct 2014 11:40:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B9C9E32-DF20-4F14-9967-76EAE2A228B2@employees.org>
References: <20141013093729.26321.32947.idtracker@ietfa.amsl.com>
To: Softwires WG <softwires@ietf.org>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/ttpa2nuZlzGJxW3p7jGENsGp0lc
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-11.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 13 Oct 2014 09:40:45 -0000

This is updated with comments from the AD review and directorate reviews =
in preparation for the MAP series of documents being on the IESG =
telechat on the 16th.

Best regards,
Ole


> On 13 Oct 2014, at 11:37 , internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Softwires Working Group of the IETF.
>=20
>        Title           : Mapping of Address and Port with =
Encapsulation (MAP)
>        Authors         : Ole Troan
>                          Wojciech Dec
>                          Xing Li
>                          Congxiao Bao
>                          Satoru Matsushima
>                          Tetsuya Murakami
>                          Tom Taylor
> 	Filename        : draft-ietf-softwire-map-11.txt
> 	Pages           : 32
> 	Date            : 2014-10-13
>=20
> 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.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-softwire-map/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-softwire-map-11
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-map-11
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From nobody Mon Oct 13 02:56:12 2014
Return-Path: <jiangsheng@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC3821A8943 for <softwires@ietfa.amsl.com>; Mon, 13 Oct 2014 02:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K_eQMw2JQMQI for <softwires@ietfa.amsl.com>; Mon, 13 Oct 2014 02:56:09 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA831A8942 for <softwires@ietf.org>; Mon, 13 Oct 2014 02:56:09 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BKM38452; Mon, 13 Oct 2014 09:56:07 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Oct 2014 10:56:07 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.22]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Mon, 13 Oct 2014 17:56:02 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: [Softwires] I-D Action: draft-ietf-softwire-4rd-09.txt
Thread-Index: AQHP5oix3bgvFh2mW0uNuWbk/apaaZwtykIA
Date: Mon, 13 Oct 2014 09:56:01 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AF634C3@nkgeml512-mbx.china.huawei.com>
References: <20141013015447.9195.86899.idtracker@ietfa.amsl.com>
In-Reply-To: <20141013015447.9195.86899.idtracker@ietfa.amsl.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
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/b533ajeQKMq7zEmYMNAVhiRPRDU
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-4rd-09.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 13 Oct 2014 09:56:11 -0000

VGhpcyB1cGRhdGUgdmVyc2lvbiBhZGRyZXNzZXMgdGhlIGNvbW1lbnRzIGZyb20gdGhlIEFEIHJl
dmlldywgSUVURiBMQyBhbmQgSUFOQSwgaW4gcHJlcGFyYXRpb24gZm9yIGJlaW5nIG9uIHRoZSBJ
RVNHIHRlbGVjaGF0IG9uIHRoZSAxNnRoLg0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCj4t
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IFNvZnR3aXJlcyBbbWFpbHRvOnNvZnR3
aXJlcy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YNCj5pbnRlcm5ldC1kcmFmdHNAaWV0
Zi5vcmcNCj5TZW50OiBNb25kYXksIE9jdG9iZXIgMTMsIDIwMTQgOTo1NSBBTQ0KPlRvOiBpLWQt
YW5ub3VuY2VAaWV0Zi5vcmcNCj5DYzogc29mdHdpcmVzQGlldGYub3JnDQo+U3ViamVjdDogW1Nv
ZnR3aXJlc10gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1zb2Z0d2lyZS00cmQtMDkudHh0DQo+DQo+
DQo+QSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50
ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzLg0KPiBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9m
IHRoZSBTb2Z0d2lyZXMgV29ya2luZyBHcm91cCBvZiB0aGUgSUVURi4NCj4NCj4gICAgICAgIFRp
dGxlICAgICAgICAgICA6IElQdjQgUmVzaWR1YWwgRGVwbG95bWVudCB2aWEgSVB2NiAtIGEgU3Rh
dGVsZXNzDQo+U29sdXRpb24gKDRyZCkNCj4gICAgICAgIEF1dGhvcnMgICAgICAgICA6IFJlbWkg
RGVzcHJlcw0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgU2hlbmcgSmlhbmcNCj4gICAgICAg
ICAgICAgICAgICAgICAgICAgIFJlaW5hbGRvIFBlbm5vDQo+ICAgICAgICAgICAgICAgICAgICAg
ICAgICBZaXUgTGVlDQo+ICAgICAgICAgICAgICAgICAgICAgICAgICBHYW5nIENoZW4NCj4gICAg
ICAgICAgICAgICAgICAgICAgICAgIE1hb2tlIENoZW4NCj4JRmlsZW5hbWUgICAgICAgIDogZHJh
ZnQtaWV0Zi1zb2Z0d2lyZS00cmQtMDkudHh0DQo+CVBhZ2VzICAgICAgICAgICA6IDQwDQo+CURh
dGUgICAgICAgICAgICA6IDIwMTQtMTAtMTINCj4NCj5BYnN0cmFjdDoNCj4gICBGb3Igc2Vydmlj
ZSBwcm92aWRlcnMgdG8gcHJvZ3Jlc3NpdmVseSBkZXBsb3kgSVB2Ni1vbmx5IG5ldHdvcmsNCj4g
ICBkb21haW5zIHdoaWxlIHN0aWxsIG9mZmVyaW5nIElQdjQgc2VydmljZSB0byBjdXN0b21lcnMs
IHRoaXMgZG9jdW1lbnQNCj4gICBzcGVjaWZpZXMgYSBzdGF0ZWxlc3Mgc29sdXRpb24uICBJdHMg
ZGlzdGluY3RpdmUgcHJvcGVydHkgaXMgdGhhdA0KPiAgIFRDUC9VRFAgSVB2NCBwYWNrZXRzIGFy
ZSB2YWxpZCBUQ1AvVURQIElQdjYgcGFja2V0cyBkdXJpbmcgZG9tYWluDQo+ICAgdHJhdmVyc2Fs
LCBhbmQgdGhhdCBJUHY0IGZyYWdtZW50YXRpb24gcnVsZXMgYXJlIGZ1bGx5IHByZXNlcnZlZCBl
bmQtDQo+ICAgdG8tZW5kLiAgRWFjaCBjdXN0b21lciBjYW4gYmUgYXNzaWduZWQgb25lIHB1Ymxp
YyBJUHY0IGFkZHJlc3MsIG9yDQo+ICAgc2V2ZXJhbCwgb3IgYSBzaGFyZWQgYWRkcmVzcyB3aXRo
IGEgcmVzdHJpY3RlZCBwb3J0IHNldC4NCj4NCj4NCj5UaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0
dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1pZXRmLXNvZnR3aXJlLTRyZC8NCj4NCj5UaGVyZSdzIGFsc28gYSBodG1saXpl
ZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1pZXRmLXNvZnR3aXJlLTRyZC0wOQ0KPg0KPkEgZGlmZiBmcm9tIHRoZSBwcmV2aW91cyB2ZXJz
aW9uIGlzIGF2YWlsYWJsZSBhdDoNCj5odHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1k
cmFmdC1pZXRmLXNvZnR3aXJlLTRyZC0wOQ0KPg0KPg0KPlBsZWFzZSBub3RlIHRoYXQgaXQgbWF5
IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCj51
bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xz
LmlldGYub3JnLg0KPg0KPkludGVybmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5v
bnltb3VzIEZUUCBhdDoNCj5mdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPg0K
Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+U29mdHdp
cmVzIG1haWxpbmcgbGlzdA0KPlNvZnR3aXJlc0BpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vc29mdHdpcmVzDQo=


From nobody Mon Oct 13 11:00:51 2014
Return-Path: <ayourtch@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B09B31A1BC0 for <softwires@ietfa.amsl.com>; Mon, 13 Oct 2014 11:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2EpSm9zBYwH for <softwires@ietfa.amsl.com>; Mon, 13 Oct 2014 11:00:49 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2613B1A1BB0 for <softwires@ietf.org>; Mon, 13 Oct 2014 11:00:49 -0700 (PDT)
Received: by mail-ig0-f177.google.com with SMTP id a13so11454691igq.4 for <softwires@ietf.org>; Mon, 13 Oct 2014 11:00:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=h7zD8hKYqPwbZw37GRCnFjpuevjLw1uMLK6vQ8ds66c=; b=XRwALFDEIDg3a9Wsp4ptVdcoDzorRzbOsr2Buq+vTKJkn/hB56XU4mJGYBI0qIjlc+ jLDgztz44/NzmcB5tffqr3SnaIvjp6UcAPlUGgfiAezEz3V7FkiijUvaLq4KoHWkykI2 FfxB/mgP2sC5NrE6skQkEK4+WqryDCABQhayWx4wg+5vxx2JIZspLu+EI8rghHMeP0Nh mTxaxWNxxH0V0EpoKdbbmmjz+hRIfZUHvaN2V8fk1marbHXzpsmHUh7wiC7vi/Zbah9s D97GKI5YNwVCywksBvW4EVdi5+6lE7SLyYb0sDVHmsTZ9z09VMusaspibn1WqWJ0IhF3 j7kw==
MIME-Version: 1.0
X-Received: by 10.43.64.210 with SMTP id xj18mr197215icb.46.1413223248563; Mon, 13 Oct 2014 11:00:48 -0700 (PDT)
Received: by 10.107.137.231 with HTTP; Mon, 13 Oct 2014 11:00:48 -0700 (PDT)
In-Reply-To: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com>
Date: Mon, 13 Oct 2014 20:00:48 +0200
Message-ID: <CAPi140PaRF+wLsJ_4FZsTdzoC1kZvzdEj1NBXEUcJ=FADPwW6w@mail.gmail.com>
From: =?UTF-8?B?QW5kcmV3IPCfkb0gIFlvdXJ0Y2hlbmtv?= <ayourtch@gmail.com>
To: softwires <softwires@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/fH4tgquzEliOVx768d-ARwg2pPc
Cc: ot@cisco.com, tetsuya@ipinfusion.com, congxiao@cernet.edu.cn, satoru.matsushima@g.softbank.co.jp, wdec <wdec@cisco.com>
Subject: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 13 Oct 2014 18:00:51 -0000

[ resending the full mail including the softwire maillist, not just
the authors ]

Hello,

In http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-11

A change in "8.3.3. Sending IPv4 fragments to the outside" from
"SHOULD" to "MUST" jumped at me, which caused to think more about this
paragraph.

This paragraph says now:

"If two IPv4 host behind two different MAP CE's with the same IPv4
   address sends fragments to an IPv4 destination host outside the
   domain, those hosts may use the same IPv4 fragmentation identifier,
   resulting in incorrect reassembly of the fragments at the destination
   host.  Given that the IPv4 fragmentation identifier is a 16 bit
   field, it can be used similarly to port ranges.  A MAP CE MUST
   rewrite the IPv4 fragmentation identifier to be within its allocated
   port-set."

I'd argue that setting it to "MUST" tries to solve a corner case but
in return introduces a much worse behavior for the common case.

I'll use a slight hyperbole to illustrate the worst case of such an
impact for a common case.

First, implementation-wise: I assume the CPE would take the frag ID
and apply modN operation where N is the share ratio, and then shift
the frag ID into correct space.

Now, the hyperbole: take a share ratio of 64K. One CPE gets a
single TCP/UDP port, and a single fragment id to peruse.

And, from a host behind one of these CPEs you open a TCP session to
another host on IPv4. You start sending a file. Your TCP window grows
beyond a single segment, and you send 4 fragments - 2 per segment, and
because of the rewriting they all get the same IP ID. As a result the
destination can not reassemble the packets.

Note that this is a typical case - no collision, no two hosts opening
a session. It gets affected.

This is of course a hyperbole to show the problem.

The smaller share ratio makes the problem less acute, but even with
16-bit space and even some years ago [1] there were problems. So given
that the broadband speeds multiplied in the meantime, shrinking the ID
space will make the problem worse.

Since it looks like the fragment value does not affect the interoperability, I'd
request to put this back to "SHOULD" (arguably it even be relaxed to
"MAY", given the severity of the issue above), and let the
implementers themselves consider whether it is worth doing or not.

[1] https://tools.ietf.org/html/draft-mathis-frag-harmful-00

Thanks!

--a

p.s. a cosmetic nit: looks like the following sentence in section 5.2
has an extra "that":

"The Rule IPv6 prefix (which is part of the End-user IPv6 prefix) that
   is common among all CEs using the same Basic Mapping Rule within the
   MAP domain. "


From nobody Mon Oct 13 19:48:34 2014
Return-Path: <sunlinhui@bupt.edu.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 684F61A1A37 for <softwires@ietfa.amsl.com>; Mon, 13 Oct 2014 19:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.014
X-Spam-Level: 
X-Spam-Status: No, score=0.014 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7b00Lt-98gst for <softwires@ietfa.amsl.com>; Mon, 13 Oct 2014 19:48:30 -0700 (PDT)
Received: from mx2.bupt.edu.cn (mx2.bupt.edu.cn [211.68.68.3]) by ietfa.amsl.com (Postfix) with ESMTP id 570671A1B24 for <softwires@ietf.org>; Mon, 13 Oct 2014 19:48:29 -0700 (PDT)
Received: from SDWM-20131107EC (unknown [221.219.227.254]) by mx2.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 6EFA919F362; Tue, 14 Oct 2014 10:48:27 +0800 (HKT)
Date: Tue, 14 Oct 2014 10:49:26 +0800
From: "sunlinhui@bupt.edu.cn" <sunlinhui@bupt.edu.cn>
To: draft-fsc-softwire-dhcp4o6-saddr-opt <draft-fsc-softwire-dhcp4o6-saddr-opt@tools.ietf.org>
X-Priority: 3
X-GUID: 36C11EF2-8535-43B0-8D21-6A98F347348E
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 140[cn]
Mime-Version: 1.0
Message-ID: <2014101410492625781531@bupt.edu.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart472011076166_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/BvccpTAiRV-dWdQQ4-VmvDrlzhs
Cc: softwires <softwires@ietf.org>
Subject: [Softwires] Comments on draft-fsc-softwire-dhcp4o6-saddr-opt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 14 Oct 2014 02:48:32 -0000

This is a multi-part message in MIME format.

------=_001_NextPart472011076166_=----
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: base64

RGVhciBhdXRob3Jzo6wNCiAgICANCkkndmUgcmVhZCB0aGlzIGRvY3VtZW50IGFuZCB0aGluayBp
dCBpcyBhIGdvb2Qgd2F5IHRvIGluZm9ybSB0aGUgc2VydmVyIG9mIGNsaWVudHMnIHNvdXJjZSBh
ZGRyZXNzZXMuIA0KDQpBbHNvLCBJIGhhdmUgYSBjb21tZW50LA0KSW4gc2VjdGlvbiAzLCANCidU
aGVuIHRoZSBPUFRJT05fUzQ2X0NPTlRfREhDUDRPNiBNQVkgYmUgaW5jbHVkZWQgaW4gREhDUHY0
LXF1ZXJ5IGFuZCBESENQdjQtcmVzcG9uc2UgbWVzc2FnZXMuJw0KDQpEbyB5b3UgdGhpbmsgaXQg
aXMgbW9yZSBhcHByb3ByaWF0ZSB0byByZXBsYWNlIHRoZSAnTUFZJyBieSAnU0hPVUxEJz8gQXMg
aW4gdGhlIHNlY3Rpb24gNS4xIG9mIFtJLUQuaWV0Zi1zb2Z0d2lyZS1sdzRvdmVyNl0sIGl0IGRl
c2NyaWJlcyB0aGF0IHRoZSBCb3JkZXIgUm91dGVyJ3MgSVB2NiBhZGRyZXNzIG11c3QgYmUgcHJv
dmlzaW9uZWQgdG8gdGhlIGx3QjQuDQoNCkJlc3QgcmVnYXJkcywNCkxpbmh1aSBTdW4NCg0KDQoN
Cg0KDQpzdW5saW5odWlAYnVwdC5lZHUuY24NCg==

------=_001_NextPart472011076166_=----
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DGB2312"><style>body { line-height: 1.5; }body { font-size: 10.5pt; fon=
t-family: =CE=A2=C8=ED=D1=C5=BA=DA; color: rgb(0, 0, 0); line-height: 1.5;=
 }</style></head><body>=0A<div><span></span>Dear authors=A3=AC</div><div><=
span style=3D"background-color: rgba(0, 0, 0, 0);">&nbsp; &nbsp;&nbsp;</sp=
an></div><div><span style=3D"background-color: rgba(0, 0, 0, 0); font-size=
: 10.5pt; line-height: 1.5;">I've read this document and think it is a goo=
d way to inform the server of clients' source addresses.&nbsp;</span></div=
><div><span style=3D"background-color: rgba(0, 0, 0, 0); font-size: 10.5pt=
; line-height: 1.5;"><br></span></div><div><span style=3D"background-color=
: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">Also, I have a c=
omment,</span></div><div><span style=3D"background-color: rgba(0, 0, 0, 0)=
; font-size: 10.5pt; line-height: 1.5;">In section 3,&nbsp;</span></div><d=
iv><span style=3D"font-size: 10.5pt; line-height: 1.5; background-color: r=
gba(0, 0, 0, 0);">'</span><span style=3D"font-size: 10.5pt; line-height: 1=
.5; background-color: rgba(0, 0, 0, 0);">Then the OPTION_S46_CONT_DHCP4O6&=
nbsp;</span><span style=3D"font-size: 10.5pt; line-height: 1.5; background=
-color: rgba(0, 0, 0, 0);">MAY be included in DHCPv4-query and DHCPv4-resp=
onse messages.'</span></div><div><span style=3D"font-size: 10.5pt; line-he=
ight: 1.5; background-color: rgba(0, 0, 0, 0);"><br></span></div><div><spa=
n style=3D"font-size: 10.5pt; line-height: 1.5; background-color: rgba(0, =
0, 0, 0);">Do you think it is more appropriate to replace the 'MAY' by 'SH=
OULD'? As in the section 5.1 of&nbsp;</span><span style=3D"font-size: 10.5=
pt; line-height: 1.5; background-color: rgba(0, 0, 0, 0);">[I-D.ietf-softw=
ire-lw4over6], it describes that the Border Router's IPv6 address must be&=
nbsp;</span><span style=3D"font-size: 10.5pt; line-height: 1.5; background=
-color: rgba(0, 0, 0, 0);">provisioned to the lwB4.</span></div><div><span=
 style=3D"background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-heig=
ht: 1.5;"><br></span></div><div><span style=3D"background-color: rgba(0, 0=
, 0, 0); font-size: 10.5pt; line-height: 1.5;">Best regards,</span></div><=
div>Linhui Sun</div><div><span style=3D"background-color: rgba(0, 0, 0, 0)=
;"><br></span></div><div><span style=3D"background-color: rgba(0, 0, 0, 0)=
;"><br></span></div>=0A<div><br></div><hr style=3D"width: 210px; height: 1=
px;" color=3D"#b5c4df" size=3D"1" align=3D"left">=0A<div><span><div style=
=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt"><div>sunlinhui@bu=
pt.edu.cn</div></div></span></div>=0A</body></html>
------=_001_NextPart472011076166_=------


From nobody Tue Oct 14 02:27:38 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9878F1A6FEC; Tue, 14 Oct 2014 02:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PywRda13ZpL; Tue, 14 Oct 2014 02:27:11 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 605841A6FEF; Tue, 14 Oct 2014 02:27:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141014092711.29985.16994.idtracker@ietfa.amsl.com>
Date: Tue, 14 Oct 2014 02:27:11 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/YDgrkM-BhGb1q6VRvLa7Qbmnwbc
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-map-t-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 14 Oct 2014 09:27:12 -0000

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

        Title           : Mapping of Address and Port using Translation (MAP-T)
        Authors         : Xing Li
                          Congxiao Bao
                          Wojciech Dec
                          Ole Troan
                          Satoru Matsushima
                          Tetsuya Murakami
	Filename        : draft-ietf-softwire-map-t-06.txt
	Pages           : 24
	Date            : 2014-10-14

Abstract:
   This document specifies the "Mapping of Address and Port" stateless
   IPv6-IPv4 Network Address Translation (NAT64) based solution
   architecture for providing shared or non-shared IPv4 address
   connectivity to and across an IPv6 network.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-t-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Tue Oct 14 03:01:45 2014
Return-Path: <otroan@employees.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7929B1A7018 for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 03:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ragsRYseNAKq for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 03:01:42 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42C141A7015 for <softwires@ietf.org>; Tue, 14 Oct 2014 03:01:42 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkEADrzPFStJssW/2dsb2JhbABRCoNhUwWDBsknh00CgSsBfYQCAQEBAwEjWwsJAhgCAiYCAiE2BhMJiCEDCQgIBZQlnE2OUw2GLgEBAQEBAQEBAQEBAQEBAQEBAQEBAReBLIxngVYLAQEcOoJ3NoEeBZY7hH+DPzyNU4JWg36DeTsvgQ+BOwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,716,1406592000"; d="scan'208";a="206085181"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 14 Oct 2014 10:01:40 +0000
Received: from dhcp-10-61-105-175.cisco.com (dhcp-10-61-105-175.cisco.com [10.61.105.175]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9EA1dxR024754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <softwires@ietf.org>; Tue, 14 Oct 2014 10:01:40 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com>
Date: Tue, 14 Oct 2014 12:01:39 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com>
To: Softwires WG <softwires@ietf.org>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/O18cki1wPRd4zVJcZQnNvLJUMDk
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 14 Oct 2014 10:01:44 -0000

[resending to list, cause mailman whinged about too many in cc]
Andrew,

thank you for the comment. let me top-post my reply.

the scenario we were concerned about was where a number of CPEs would =
share the same IPv4 address, and where many of them would communicate =
with the same destination. if there wasn't a way to coordinate the =
fragment id space used, there would be a chance of the remote =
destination incorrectly reassembling packets. where one fragment would =
come from CPE #1 and the other from CPE #2.

there is a tradeoff between that problem and the problem you identify, =
that is risking fragment collision within one single connection.

splitting the fragment id space so that there is only a single bit per =
CPE sounds like a corner case that should be disallowed. I don't know if =
we have the knowledge to be able to specify exactly how much of the =
fragment id space is safe to split up though.is it 4, 6, or 8 bits?

if changing back to SHOULD from the MUST would lead people to accept =
that we leave the exact recommendations for further study I would be =
happy to do that.

I have cc'ed Ted who brought this up initially in his AD review, and =
I've also included Joe Touch in case he has further insights.

cheers,
Ole



> On 13 Oct 2014, at 19:22 , Andrew =F0=9F=91=BD Yourtchenko =
<ayourtch@gmail.com> wrote:
>=20
> [ resending the full mail including the softwire maillist, not just
> the authors ]
>=20
> Hello,
>=20
> In http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-map-11
>=20
> A change in "8.3.3. Sending IPv4 fragments to the outside" from
> "SHOULD" to "MUST" jumped at me, which caused to think more about this
> paragraph.
>=20
> This paragraph says now:
>=20
> "If two IPv4 host behind two different MAP CE's with the same IPv4
>  address sends fragments to an IPv4 destination host outside the
>  domain, those hosts may use the same IPv4 fragmentation identifier,
>  resulting in incorrect reassembly of the fragments at the destination
>  host.  Given that the IPv4 fragmentation identifier is a 16 bit
>  field, it can be used similarly to port ranges.  A MAP CE MUST
>  rewrite the IPv4 fragmentation identifier to be within its allocated
>  port-set."
>=20
> I'd argue that setting it to "MUST" tries to solve a corner case but
> in return introduces a much worse behavior for the common case, if I
> understand it correctly.
>=20
> First, implementation-wise: I assume the CPE would take the frag ID
> and apply modN operation where N is the share ratio, and then shift
> the frag ID into correct space.
>=20
> Now, the promised hyperbole: take a share ratio of 64K. One CPE gets a
> single port, and a single fragment id to peruse.
>=20
> And, from a host behind one of these CPEs you open a TCP session to
> another host on IPv4. You start sending a file. Your TCP window grows
> beyond a single segment, and you send 4 fragments - 2 per segment, and
> because of the rewriting they all get the same IP ID. As a result the
> destination can not reassemble the packets.
>=20
> Note that this is a typical case - no collision, no two hosts opening
> a session. It gets affected.
>=20
> This is of course a hyperbole to show the problem.
>=20
> The smaller share ratio makes the problem less acute, but even with
> 16-bit space and even some years ago [1] there were problems. So given
> that the broadband speeds multiplied in the meantime, shrinking the ID
> space will make the problem worse.
>=20
> Since it looks like the fragment value does not affect the =
interoperability, I'd
> request to put this back to "SHOULD" (arguably it even be relaxed to
> "MAY", given the severity of the issue above), and let the
> implementers themselves consider whether it is worth doing or not.
>=20
> [1] https://tools.ietf.org/html/draft-mathis-frag-harmful-00
>=20
> Thanks!
>=20
> --a
>=20
> p.s. a cosmetic nit: looks like the following sentence in section 5.2
> has an extra "that":
>=20
> "The Rule IPv6 prefix (which is part of the End-user IPv6 prefix) that
>  is common among all CEs using the same Basic Mapping Rule within the
>  MAP domain. "


From nobody Tue Oct 14 06:32:41 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D84B1A882C for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 06:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PkCw9HyNt54 for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 06:32:38 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EED1F1A8821 for <softwires@ietf.org>; Tue, 14 Oct 2014 06:32:37 -0700 (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 Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D645A1B8415 for <softwires@ietf.org>; Tue, 14 Oct 2014 06:32:37 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id C57E753E079; Tue, 14 Oct 2014 06:32:37 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 06:32:37 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org>
Date: Tue, 14 Oct 2014 08:32:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com> <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/UvgANzIBEJ1hKTdyUBCsgvv-b6Y
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 14 Oct 2014 13:32:39 -0000

On Oct 14, 2014, at 5:01 AM, Ole Troan <otroan@employees.org> wrote:
> splitting the fragment id space so that there is only a single bit per =
CPE sounds like a corner case that should be disallowed. I don't know if =
we have the knowledge to be able to specify exactly how much of the =
fragment id space is safe to split up though.is it 4, 6, or 8 bits?

There's a lot to think about here.  The fragment ID translation =
algorithm probably needs to maintain a cache so that it doesn't =
accidentally overload fragment IDs.   The set of all outstanding =
fragments has the potential to be larger than the set of all ports in =
use, so there is definitely reason to be concerned about shrinking the =
fragment ID space.   However, shrinking the fragment ID space _does_ =
serve the useful purpose of isolating fragment ID collisions to the =
nodes that are supposed to be receiving the fragments.

It may be that the right thing to do is to note that this is a problem, =
make a recommendation, but essentially leave it as future research, =
since we really haven't analyzed the problem in enough depth to make an =
informed recommendation.

> if changing back to SHOULD from the MUST would lead people to accept =
that we leave the exact recommendations for further study I would be =
happy to do that.

So yes, this might be a good way to go.


From nobody Tue Oct 14 07:51:08 2014
Return-Path: <rajiva@cisco.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DACA61A87B1 for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 07:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id myjQukdrObkN for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 07:51:04 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3C621A877F for <softwires@ietf.org>; Tue, 14 Oct 2014 07:51:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2373; q=dns/txt; s=iport; t=1413298264; x=1414507864; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=0sq1DlUsBet2vtK8iflRdDI0oB2KTuxe2gGuFZHWamE=; b=M8AxEO1JZqr4ixgFfiLqIa7P9YWfFQ8pipeXADPlDJjK/CYMcqE2hUte w/+DU3SKFKCdwUnptN8dV733BM0lbRQo0m4GiRlIvaQyVBOyZdD45Kw5n Kbroob7gTFeBTEGv/jX4++TEQ90QdGlze5DMISth+kzZuvFXjKbPVgqvn w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAK03PVStJV2Q/2dsb2JhbABbgw5TWATMKgqGeVQCgRQWAX2EAgEBAQQBAQFrCwwEAgEIEQMBAgEuJwsdCAIEAQ0FiD4Nxk4BAQEBAQEBAQEBAQEBAQEBAQEBAQEXkBorBwaERQWLIIZZhEKHEIFqlCeDd2yBSIECAQEB
X-IronPort-AV: E=Sophos;i="5.04,717,1406592000"; d="scan'208";a="363338160"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-2.cisco.com with ESMTP; 14 Oct 2014 14:51:03 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s9EEp3xt012142 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Oct 2014 14:51:03 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.218]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 09:51:02 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Ole Troan <otroan@employees.org>
Thread-Topic: [Softwires] MAP draft 11 question on fragment ID space reduction
Thread-Index: AQHP55XYMDkTrQLO4kS2LpDbhAWxWJwv60aA///TAQA=
Date: Tue, 14 Oct 2014 14:51:02 +0000
Message-ID: <D0629F4B.20A7A8%rajiva@cisco.com>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com> <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org> <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com>
In-Reply-To: <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.82.226.158]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <AA154AC14FE8C246A503A4E05EA53094@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/nE4J8nu_HpA6JFs3jSa_2hD7bGU
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 14 Oct 2014 14:51:07 -0000

It might be worth understanding why this problem is even worth
addressing/mentioning.

Is the possibility of 2 or more host devices (behind 2 or more MAP CE
routers) sharing the same IPv4 address would be "generating the fragmented
packets" towards the same destination around the same time, not close to
zero due to PMTUD etc.?

AFAIK, RFC6888 doesn=B9t mention such a problem or requirement for CGN?


IMO, there shouldn=B9t be any normative recommendation, if this problem is
mentioned.

--=20
Cheers,
Rajiv Asati
Distinguished Engineer, Cisco





-----Original Message-----
From: Ted Lemon <Ted.Lemon@nominum.com>
Date: Tuesday, October 14, 2014 at 9:32 AM
To: Ole Troan <otroan@employees.org>
Cc: Softwires-wg list <softwires@ietf.org>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space
reduction

>On Oct 14, 2014, at 5:01 AM, Ole Troan <otroan@employees.org> wrote:
>> splitting the fragment id space so that there is only a single bit per
>>CPE sounds like a corner case that should be disallowed. I don't know if
>>we have the knowledge to be able to specify exactly how much of the
>>fragment id space is safe to split up though.is it 4, 6, or 8 bits?
>
>There's a lot to think about here.  The fragment ID translation algorithm
>probably needs to maintain a cache so that it doesn't accidentally
>overload fragment IDs.   The set of all outstanding fragments has the
>potential to be larger than the set of all ports in use, so there is
>definitely reason to be concerned about shrinking the fragment ID space.
> However, shrinking the fragment ID space _does_ serve the useful purpose
>of isolating fragment ID collisions to the nodes that are supposed to be
>receiving the fragments.
>
>It may be that the right thing to do is to note that this is a problem,
>make a recommendation, but essentially leave it as future research, since
>we really haven't analyzed the problem in enough depth to make an
>informed recommendation.
>
>> if changing back to SHOULD from the MUST would lead people to accept
>>that we leave the exact recommendations for further study I would be
>>happy to do that.
>
>So yes, this might be a good way to go.
>
>_______________________________________________
>Softwires mailing list
>Softwires@ietf.org
>https://www.ietf.org/mailman/listinfo/softwires


From nobody Tue Oct 14 07:54:32 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 531C81A88CC for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 07:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQApRDN77vol for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 07:54:22 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61D551A87B1 for <softwires@ietf.org>; Tue, 14 Oct 2014 07:54:22 -0700 (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 Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 35EA31B83C7 for <softwires@ietf.org>; Tue, 14 Oct 2014 07:54:22 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 1B5E453E079; Tue, 14 Oct 2014 07:54:22 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 07:54:22 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <D0629F4B.20A7A8%rajiva@cisco.com>
Date: Tue, 14 Oct 2014 09:54:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <8B98BAD4-A992-4F81-8207-6B4A42F1AC45@nominum.com>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com> <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org> <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com> <D0629F4B.20A7A8%rajiva@cisco.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/fBQ4rtulb6P51v9l2Vp7ciga630
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 14 Oct 2014 14:54:23 -0000

On Oct 14, 2014, at 9:51 AM, Rajiv Asati (rajiva) <rajiva@cisco.com> =
wrote:
> It might be worth understanding why this problem is even worth
> addressing/mentioning.

This was in the document, so I commented on it.   I don't know what the =
original motivation was for adding it.   I would be okay with simply =
removing the text if the authors and WG agree that it's not necessary.


From nobody Tue Oct 14 10:53:16 2014
Return-Path: <touch@isi.edu>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE7F51A90E9 for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 10:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.986
X-Spam-Level: 
X-Spam-Status: No, score=-4.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lEXtOVjLJQsC for <softwires@ietfa.amsl.com>; Tue, 14 Oct 2014 10:41:23 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F35D1A90DE for <softwires@ietf.org>; Tue, 14 Oct 2014 10:41:23 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id s9EHdrMH000602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 14 Oct 2014 10:39:53 -0700 (PDT)
Message-ID: <543D5FE8.6080804@isi.edu>
Date: Tue, 14 Oct 2014 10:39:52 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>, Andrew Yourtchenko <ayourtch@gmail.com>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com> <C51ECE96-003E-41F9-A2B8-1046F041AE99@employees.org>
In-Reply-To: <C51ECE96-003E-41F9-A2B8-1046F041AE99@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/qay-BxuwzTyukXVM0apbCz05_3A
X-Mailman-Approved-At: Tue, 14 Oct 2014 10:53:13 -0700
Cc: Tetsuya Murakami <tetsuya@ipinfusion.com>, =?UTF-8?B?5YyF5Lib?= =?UTF-8?B?56yR?= <congxiao@cernet.edu.cn>, Matsushima Satoru <satoru.matsushima@g.softbank.co.jp>, Softwires WG <softwires@ietf.org>, wdec <wdec@cisco.com>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 14 Oct 2014 17:41:26 -0000

On 10/14/2014 2:58 AM, Ole Troan wrote:
...
> splitting the fragment id space so that there is only a single bit 
> per CPE sounds like a corner case that should be disallowed. I don't
> know if we have the knowledge to be able to specify exactly how much
> of the fragment id space is safe to split up though.is it 4, 6, or 8
> bits?

As per RFC 6864, the IPv4 ID space is small and use of that space needs
to consider the number of current IP packets being reassembled, i.e.,
the reordering likely to occur.

It might be safe to use a space one bit larger than the amount of
reordering, but I'd prefer two.

So the key question is:

	- how much fragment reordering to you expect *within*
	a given IP address pair/transport tuple?

I don't know the answer to that, but log2(reordering) + 2 ought to be a
lower bound on the space that might overlap.

I.e., I doubt you should ever allow 1-2 bits. I would expect a minimum
of 4 bits but the appropriate answer depends on the reordering you're
trying to protect against.

NOTE: I would strongly encourage an encapsulation that includes its own
checksum to protect against incorrect reassembly (if that's not already
included; I haven't checked the draft).

Joe


From nobody Wed Oct 15 06:27:54 2014
Return-Path: <otroan@employees.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF3A01A1B70 for <softwires@ietfa.amsl.com>; Wed, 15 Oct 2014 06:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQFUohhQtuw2 for <softwires@ietfa.amsl.com>; Wed, 15 Oct 2014 06:27:51 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88C461A1B16 for <softwires@ietf.org>; Wed, 15 Oct 2014 06:27:50 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqYEANN0PlStJssW/2dsb2JhbABbg2FYzAOHTQKBKAF9hAIBAQEDATo/BQsLGC5XBhMbiBsIDcg8AQEBAQEBAQEBAQEBAQEBAQEBAQEBF5AbMweDLYEeAQSWQ4h9lC6DeTsvAQGCSAEBAQ
X-IronPort-AV: E=Sophos;i="5.04,724,1406592000"; d="scan'208";a="211656535"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 15 Oct 2014 13:27:48 +0000
Received: from dhcp-10-61-100-153.cisco.com (dhcp-10-61-100-153.cisco.com [10.61.100.153]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s9FDRlch019281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Oct 2014 13:27:48 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com>
Date: Wed, 15 Oct 2014 15:27:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D14390B1-8628-4372-B664-A5EA82BE0327@employees.org>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com> <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org> <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/nAKYcQvehdvpehoHxQj_eabY49k
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 15 Oct 2014 13:27:53 -0000

Ted, et al,

there are good arguments going both ways, so apologies for my changing =
opinion here. ;-)

we could go with the hand-wavy, there is a problem here, we don't have a =
good solution:

        <t>If two IPv4 host behind two different MAP CE's with the
        same IPv4 address sends fragments to an IPv4 destination host
        outside the domain, those hosts may use the same IPv4
        fragmentation identifier, resulting in incorrect reassembly of
        the fragments at the destination host. Given that the IPv4
        fragmentation identifier is a 16 bit field, it could be used
        similarly to port ranges. A MAP CE could rewrite the IPv4
        fragmentation identifier to be within its allocated port-set,
        if the resulting fragment identifier space was large enough
        related to the rate fragments was sent. However, splitting the
        identifier space in this fashion would increase the
        probability of reassembly collision for all connections
        through the CPE. See also <xref target=3D"RFC6864"/></t>

the alternatives are that we could say, since the problem of multiple =
CPEs with same IP address sending fragments to same destination required =
coordination that if the fragment id space was say 10 bits, then =
rewrite. or we could go even further and say that the CPE would have to =
throttle traffic to ensure that the id space didn't cycle within the =
reassembly timeout.
or we could drop the text altogether.

my preference would be the above proposed text. it has the problem =
description but it doesn't prescribe a solution.

any other opinion?

ps: whatever solution we have here should probably also apply to the =
other mechanisms. e.g. =
https://tools.ietf.org/html/draft-ietf-softwire-4rd-09#section-4.6.3

cheers,
Ole



> On 14 Oct 2014, at 15:32 , Ted Lemon <Ted.Lemon@nominum.com> wrote:
>=20
> On Oct 14, 2014, at 5:01 AM, Ole Troan <otroan@employees.org> wrote:
>> splitting the fragment id space so that there is only a single bit =
per CPE sounds like a corner case that should be disallowed. I don't =
know if we have the knowledge to be able to specify exactly how much of =
the fragment id space is safe to split up though.is it 4, 6, or 8 bits?
>=20
> There's a lot to think about here.  The fragment ID translation =
algorithm probably needs to maintain a cache so that it doesn't =
accidentally overload fragment IDs.   The set of all outstanding =
fragments has the potential to be larger than the set of all ports in =
use, so there is definitely reason to be concerned about shrinking the =
fragment ID space.   However, shrinking the fragment ID space _does_ =
serve the useful purpose of isolating fragment ID collisions to the =
nodes that are supposed to be receiving the fragments.
>=20
> It may be that the right thing to do is to note that this is a =
problem, make a recommendation, but essentially leave it as future =
research, since we really haven't analyzed the problem in enough depth =
to make an informed recommendation.
>=20
>> if changing back to SHOULD from the MUST would lead people to accept =
that we leave the exact recommendations for further study I would be =
happy to do that.
>=20
> So yes, this might be a good way to go.


From nobody Wed Oct 15 06:30:50 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5715B1A1B16; Wed, 15 Oct 2014 06:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dT4Ju4aIwHCJ; Wed, 15 Oct 2014 06:30:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0053B1A1AA4; Wed, 15 Oct 2014 06:30:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141015133044.10016.66473.idtracker@ietfa.amsl.com>
Date: Wed, 15 Oct 2014 06:30:44 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/1n1ml77TGnqGz2oRNHYhtvKqe7A
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-11.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 15 Oct 2014 13:30:47 -0000

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

        Title           : Lightweight 4over6: An Extension to the DS-Lite Architecture
        Authors         : Yong Cui
                          Qiong Sun
                          Mohamed Boucadair
                          Tina Tsou
                          Yiu L. Lee
                          Ian Farrer
	Filename        : draft-ietf-softwire-lw4over6-11.txt
	Pages           : 21
	Date            : 2014-10-15

Abstract:
   Dual-Stack Lite (RFC 6333) describes an architecture for transporting
   IPv4 packets over an IPv6 network.  This document specifies an
   extension to DS-Lite called Lightweight 4over6 which moves the
   Network Address and Port Translation (NAPT) function from the
   centralized DS-Lite tunnel concentrator to the tunnel client located
   in the Customer Premises Equipment (CPE).  This removes the
   requirement for a Carrier Grade NAT function in the tunnel
   concentrator and reduces the amount of centralized state that must be
   held to a per-subscriber level.  In order to delegate the NAPT
   function and make IPv4 Address sharing possible, port-restricted IPv4
   addresses are allocated to the CPEs.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-lw4over6-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Wed Oct 15 10:13:31 2014
Return-Path: <ian.farrer@telekom.de>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD881ABC10; Wed, 15 Oct 2014 10:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.26
X-Spam-Level: 
X-Spam-Status: No, score=-3.26 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mt3niE1YHACm; Wed, 15 Oct 2014 10:13:07 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 150CB1A913D; Wed, 15 Oct 2014 10:13:05 -0700 (PDT)
Received: from qdezc2.de.t-internal.com ([10.125.181.10]) by tcmail11.telekom.de with ESMTP; 15 Oct 2014 19:13:03 +0200
X-IronPort-AV: E=Sophos;i="5.04,725,1406584800"; d="scan'208";a="150827819"
Received: from he113676.emea1.cds.t-internal.com ([10.134.99.29]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES128-SHA; 15 Oct 2014 19:13:03 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113676.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 15 Oct 2014 19:13:03 +0200
From: <ian.farrer@telekom.de>
To: <david.black@emc.com>, <gen-art@ietf.org>, <ops-dir@ietf.org>
Date: Wed, 15 Oct 2014 19:12:58 +0200
Thread-Topic: Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
Thread-Index: Ac/om0diLlR/Ui+MQWCorMI86CYPLA==
Message-ID: <D0647743.DE00C%ian.farrer@telekom.de>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.4.140807
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="euc-kr"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/JJJN4RFWor6a6ETLOFSWu0mF_Vc
Cc: softwires@ietf.org, draft-ietf-softwire-lw4over6@tools.ietf.org, ietf@ietf.org
Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 15 Oct 2014 17:13:12 -0000

SGkgRGF2aWQsDQoNCk1hbnkgdGhhbmtzIGZvciB0aGUgcmV2aWV3LiBQbGVhc2Ugc2VlIGNvbW1l
bnRzIGlubGluZS4NCg0KQ2hlZXJzLA0KSWFuDQoNCg0KDQpPbiAxMi8xMC8yMDE0IDAwOjMwLCAi
QmxhY2ssIERhdmlkIiA8ZGF2aWQuYmxhY2tAZW1jLmNvbT4gd3JvdGU6DQoNCj5UaGlzIGlzIGEg
Y29tYmluZWQgR2VuLUFSVCBhbmQgT1BTLURJUiByZXZpZXcuICBCb2lsZXJwbGF0ZSBmb3IgYm90
aA0KPmZvbGxvd3MsDQo+YW5kIEkgYXBvbG9naXplIGZvciBpdCBiZWluZyBhIGRheSBsYXRlIC0g
VW5pdGVkIEFpcmxpbmVzIGdvdCBtZSBiYWNrIHRvDQo+Qm9zdG9uIGFmdGVyIG1pZG5pZ2h0IGxh
c3QgbmlnaHQgb24gYSBwbGFuZSB3L28gd29ya2luZyBXaUZpLg0KPg0KPkkgYW0gdGhlIGFzc2ln
bmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNrZ3JvdW5kIG9uDQo+
R2VuLUFSVCwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0Og0KPg0KPjxodHRwOi8vd2lraS50b29scy5p
ZXRmLm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NCj4NCj5QbGVhc2UgcmVzb2x2
ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBMYXN0IENhbGwgY29tbWVudHMN
Cj55b3UgbWF5IHJlY2VpdmUuDQo+DQo+SSBoYXZlIHJldmlld2VkIHRoaXMgZG9jdW1lbnQgYXMg
cGFydCBvZiB0aGUgT3BlcmF0aW9uYWwgZGlyZWN0b3JhdGUncw0KPm9uZ29pbmcNCj5lZmZvcnQg
dG8gcmV2aWV3IGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cu
ICBUaGVzZQ0KPmNvbW1lbnRzDQo+d2VyZSB3cml0dGVuIHByaW1hcmlseSBmb3IgdGhlIGJlbmVm
aXQgb2YgdGhlIG9wZXJhdGlvbmFsIGFyZWEgZGlyZWN0b3JzLg0KPkRvY3VtZW50IGVkaXRvcnMg
YW5kIFdHIGNoYWlycyBzaG91bGQgdHJlYXQgdGhlc2UgY29tbWVudHMganVzdCBsaWtlIGFueQ0K
Pm90aGVyDQo+bGFzdCBjYWxsIGNvbW1lbnRzLg0KPg0KPkRvY3VtZW50OiBkcmFmdC1pZXRmLXNv
ZnR3aXJlLWx3NG92ZXI2LTEwDQo+UmV2aWV3ZXI6IERhdmlkIEJsYWNrDQo+UmV2aWV3IERhdGU6
IE9jdG9iZXIgMTAsIDIwMTQNCj5JRVRGIExDIEVuZCBEYXRlOiBPY3RvYmVyIDEwLCAyMDE0DQo+
SUVTRyBUZWxlY2hhdCBkYXRlOiBPY3RvYmVyIDE2LCAyMDE0DQo+DQo+U3VtbWFyeTogVGhpcyBk
cmFmdCBpcyBvbiB0aGUgcmlnaHQgdHJhY2ssIGJ1dCBoYXMgb3BlbiBpc3N1ZXMNCj4gCQlkZXNj
cmliZWQgaW4gdGhlIHJldmlldy4NCj4NCj5UaGlzIGRyYWZ0IGRlc2NyaWJlcyBhbiBleHRlbnNp
b24gdG8gRHVhbC1TdGFjayBMaXRlIHRoYXQgcmVsb2NhdGVzIHRoZQ0KPk5BUFQNCj5mdW5jdGlv
bmFsaXR5IGZyb20gdGhlIGNlbnRyYWxpemVkIHR1bm5lbCBjb25jZW50cmF0b3IgdG8gdGhlIERT
LUxpdGUNCj5jbGllbnQNCj4tIGRvaW5nIHNvIGhhcyBzaWduaWZpY2FudCBzY2FsYWJpbGl0eSBi
ZW5lZml0cy4gIFRoZSBkcmFmdCBpcyBnZW5lcmFsbHkNCj5yZWFkYWJsZSBhbHRob3VnaCB1bmRl
cnN0YW5kaW5nIHdoeSBzb21lIG9mIHRoZSBwcm9jZXNzaW5nIG5lZWRzIHRvIGJlDQo+ZG9uZQ0K
PmluIHRoZSBtYW5uZXIgc3BlY2lmaWVkIHJlcXVpcmVzIHN0cm9uZyBmYW1pbGlhcml0eSB3aXRo
IGJvdGggRFMtTGl0ZSBhbmQNCj5OQVBULg0KPg0KPlRoZSBkcmFmdCBpcyBnZW5lcmFsbHkgaW4g
Z29vZCBzaGFwZSAtIEkgZm91bmQgdGhyZWUgaXNzdWVzIHRoYXQgSQ0KPmNvbnNpZGVyDQo+dG8g
YmUgc2lnbmlmaWNhbnQsIHRoZSBtb3N0IGltcG9ydGFudCBvZiB3aGljaCBhcmUgc2xvcHBpbmVz
cyBpbiB1c2Ugb2YNCj5SRkMgMjExOSBrZXl3b3JkcywgcGFydGljdWxhcmx5IGluIFNlY3Rpb24g
NS4xLCBhbmQgb21pc3Npb24gb2Ygd2hhdA0KPmFwcGVhcnMgdG8gYmUgYSBuZWNlc3Nhcnkgbm9y
bWF0aXZlIHJlZmVyZW5jZS4NCj4NCj5NYWpvciBpc3N1ZXMgKDIpOg0KPg0KPlsxXSBUaGVyZSBh
cmUgYSBudW1iZXIgb2YgcGxhY2VzIHdoZXJlIFNIT1VMRCBpcyB1c2VkIHRvIHJlZmVyIHRvDQo+
cmVxdWlyZW1lbnQNCj5pbiBhbm90aGVyIFJGQywgZS5nLiwgdGhlIGZvbGxvd2luZyB0ZXh0IGlu
IHNlY3Rpb24gNS4xOg0KPg0KPiAgIFRoZSBETlMgY29uc2lkZXJhdGlvbnMgZGVzY3JpYmVkIGlu
IFNlY3Rpb24gNS41IGFuZCBTZWN0aW9uIDYuNCBvZg0KPiAgIFtSRkM2MzMzXSBTSE9VTEQgYmUg
Zm9sbG93ZWQuDQo+DQo+VGhpcyBoYXMgdGhlIHNpZGUgZWZmZWN0IG9mIHdlYWtlbmluZyBhbnkg
TVVTVCByZXF1aXJlbWVudCBpbiB0aGUNCj5yZWZlcmVuY2VkDQo+UkZDKHMpIHRvIGEgU0hPVUxE
LCB3aGljaCB3YXMgcHJvYmFibHkgbm90IGludGVuZGVkLCBhbmQgbmVlZHMgdG8gYmUNCj5leHBs
aWNpdGx5DQo+c3RhdGVkIGlmIGl0IHdhcyBpbnRlbmRlZC4gIEhlcmUncyBhIHBvc3NpYmxlIHJl
cGhyYXNpbmc6DQo+DQo+ICAgVGhlIEROUyBjb25zaWRlcmF0aW9ucyBkZXNjcmliZWQgaW4gU2Vj
dGlvbiA1LjUgYW5kIFNlY3Rpb24gNi40IG9mDQo+ICAgW1JGQzYzMzNdIGFwcGx5IHRvIExpZ2h0
d2VpZ2h0IDRvdmVyNjsgbHc0bzYgaW1wbGVtZW50YXRpb25zIE1VU1QNCj4gICBjb21wbHkgd2l0
aCBhbGwgcmVxdWlyZW1lbnRzIHN0YXRlZCB0aGVyZS4NCj4NCj5UaGUgYWRkaXRpb25hbCBwbGFj
ZXMgd2hlcmUgdGhpcyBvY2N1cnMgYXJlOg0KPg0KPi0gU2VjdGlvbiA1LjIuMSAodHdpY2UpOg0K
Pg0KPiAgIEZvciBUQ1AgYW5kIFVEUCB0cmFmZmljIHRoZSBOQVBUNDQgaW1wbGVtZW50ZWQgaW4g
dGhlIGx3QjQgU0hPVUxEDQo+ICAgY29uZm9ybSB3aXRoIHRoZSBiZWhhdmlvdXIgYW5kIGJlc3Qg
Y3VycmVudCBwcmFjdGljZXMgZG9jdW1lbnRlZCBpbg0KPiAgIFtSRkM0Nzg3XSwgW1JGQzU1MDhd
LCBhbmQgW1JGQzUzODJdLiAgSWYgdGhlIGx3QjQgc3VwcG9ydHMgRENDUCwgdGhlbg0KPiAgIHRo
ZSByZXF1aXJlbWVudHMgaW4gW1JGQzU1OTddIFNIT1VMRCBiZSBpbXBsZW1lbnRlZC4NCj4NCj4t
IFNlY3Rpb24gOC4yOg0KPg0KPiAgIFRoZSBsd0I0IFNIT1VMRCBpbXBsZW1lbnQgdGhlIHJlcXVp
cmVtZW50cyBkZWZpbmVkIGluIFtSRkM1NTA4XSBmb3INCj4gICBJQ01QIGZvcndhcmRpbmcuDQoN
CltpZl0gT0sgd2l0aCB0aGUgYWJvdmUgcHJvcG9zYWxzLg0KDQoNCj4NCj5bMl0gU2VjdGlvbiA0
LiAgTGlnaHR3ZWlnaHQgNG92ZXI2IEFyY2hpdGVjdHVyZQ0KPg0KPiAgIFRoZSBjb25zZXF1ZW5j
ZSBvZiB0aGlzIGFyY2hpdGVjdHVyZSBpcyB0aGF0IHRoZSBpbmZvcm1hdGlvbg0KPiAgIG1haW50
YWluZWQgYnkgdGhlIHByb3Zpc2lvbmluZyBtZWNoYW5pc20gYW5kIHRoZSBvbmUgbWFpbnRhaW5l
ZCBieQ0KPiAgIHRoZSBsd0FGVFIgTVVTVCBiZSBzeW5jaHJvbml6ZWQgKFNlZSBmaWd1cmUgMiku
ICBUaGUgZGV0YWlscyBvZiB0aGlzDQo+ICAgc3luY2hyb25pemF0aW9uIGRlcGVuZCBvbiB0aGUg
ZXhhY3QgcHJvdmlzaW9uaW5nIG1lY2hhbmlzbSBhbmQgd2lsbA0KPiAgIGJlIGRpc2N1c3NlZCBp
biBhIGNvbXBhbmlvbiBkb2N1bWVudC4NCj4NCj5JIGJlbGlldmUgdGhhdCB0aGlzICJjb21wYW5p
b24gZG9jdW1lbnQiIG5lZWRzIHRvIGJlIGNpdGVkIGFzIGENCj5ub3JtYXRpdmUgcmVmZXJlbmNl
LiAgVGhlIGFib3ZlIHRleHQncyB2YWd1ZSBhbGx1c2lvbiB0byB0aGUgc3BlY2lmaWNhdGlvbg0K
Pm9mIGhvdyB0byBpbXBsZW1lbnQgYSAiTVVTVCIgcmVxdWlyZW1lbnQgaXMgaW5zdWZmaWNpZW50
Lg0KDQpbaWZdIFRoZSBzeW5jaCBtZWNoYW5pc20gaXMgcmVhbGx5IGRvd24gdG8gaG93IGFuIG9w
ZXJhdG9yIGhhcyBkZXBsb3llZA0KdGhlIHNlcnZpY2UsIHRoZSBzcGVjaWZpYyBwcm92aXNpb25p
bmcgcHJvdG9jb2xzIGluIHVzZSBldGMuIFdoYXQgYWJvdXQNCnRoZSBmb2xsb3dpbmcgd29yZGlu
ZyBjaGFuZ2U/Og0KDQpUaGUgY29uc2VxdWVuY2Ugb2YgdGhpcyBhcmNoaXRlY3R1cmUgaXMgdGhh
dCB0aGUgaW5mb3JtYXRpb24gbWFpbnRhaW5lZCBieQ0KdGhlIHByb3Zpc2lvbmluZyBtZWNoYW5p
c20gYW5kIHRoZSBvbmUgbWFpbnRhaW5lZCBieSB0aGUgbHdBRlRSIE1VU1QgYmUNCnN5bmNocm9u
aXplZCAoU2VlIGZpZ3VyZSAyKS4gIFRoZSBkZXRhaWxzIG9mIHRoaXMgc3luY2hyb25pemF0aW9u
IGRlcGVuZA0Kb24gdGhlIGV4YWN0IHByb3Zpc2lvbmluZyBtZWNoYW5pc20gYW5kIHByb3RvY29s
cyB0aGF0IGFyZSBpbiB1c2UgYnkgdGhlDQpvcGVyYXRvci4gSWYgbm8gYXV0b21hdGVkIHByb2Nl
c3MgZm9yIHRoaXMgc3luY2hyb25pc2F0aW9uIGlzIGluIHVzZSwgdGhlbg0KaW5mb3JtYXRpb24g
aW4gdGhlIHByb3Zpc2lvbmluZyBzeXN0ZW1zIGFuZCB0aGUgbHdBRlRSIE1VU1QgYmUNCnN5bmNo
cm9uaXNlZCBtYW51YWxseSwgZS5nLiBieSBjb3B5aW5nIGFsaWduZWQgY29uZmlndXJhdGlvbiBm
aWxlcyB0byBlYWNoDQpvZiB0aGUgZWxlbWVudHMuDQoNCg0KPg0KPk1pbm9yIGlzc3VlcyAoNyk6
DQo+DQo+WzNdIFRoZSBsYWNrIG9mIGRpc2N1c3Npb24gb2YgbWFuYWdlbWVudCBpbmZvcm1hdGlv
biBpcyBhbg0KPm9taXNzaW9uLiAgU2VlIEEuMi4yIGJlbG93IGluIHRoZSBPUFMtRGlyIHJldmll
dyBzZWN0aW9uIG9mIHRoaXMgZW1haWwNCj5hbmQgdGhlIGRpc2N1c3Npb24gaW4gU2VjdGlvbiAz
LjIgb2YgUkZDIDU3MDYuICBBIHNlbnRlbmNlIHBvaW50aW5nDQo+YXQgYW4gYXBwbGljYWJsZSBN
SUIgYW5kL29yIFlBTkcgZHJhZnQgb3IgZHJhZnRzIHdvdWxkIHN1ZmZpY2UuDQoNCltpZl0gVGhl
cmUgaXMgYSBkcmFmdCBmb3IgYSBzb2Z0d2lyZSBZQU5HIG1vZGVsIHdoaWNoIGlzIGR1ZSB0byBi
ZQ0KcHVibGlzaGVkIHNob3J0bHkuIFdlJ2xsIGFkZCBhbiBpbmZvcm1hdGl2ZSByZWZlcmVuY2Ug
dG8gdGhpcy4NCg0KPg0KPls0XSBTZWN0aW9uIDQuICBMaWdodHdlaWdodCA0b3ZlcjYgQXJjaGl0
ZWN0dXJlDQo+DQo+ICAgVGhlIHNvbHV0aW9uIHNwZWNpZmllZCBpbiB0aGlzIGRvY3VtZW50IGFs
bG93cyB0aGUgYXNzaWdubWVudCBvZg0KPiAgIGVpdGhlciBhIGZ1bGwgb3IgYSBzaGFyZWQgSVB2
NCBhZGRyZXNzIHJlcXVlc3RpbmcgQ1BFcy4gIFtSRkM3MDQwXQ0KPiAgIHByb3ZpZGVzIGEgbWVj
aGFuaXNtIGZvciBhc3NpZ25pbmcgYSBmdWxsIElQdjQgYWRkcmVzcyBvbmx5Lg0KPg0KPlBsZWFz
ZSBleHBsYWluIHdoYXQgZW50aXRpZXMgd291bGQgc2hhcmUgdGhlIElQdjQgYWRkcmVzcy4gIEZv
ciBleGFtcGxlLA0KPnRoaXMgaXMgbmVlZGVkIGFzIGEgZm91bmRhdGlvbiBmb3IgdGhlIHN0YXRl
bWVudCBpbiBTZWN0aW9uIDggdGhhdA0KPiJJQ01QdjQgZG9lcyBub3Qgd29yayBpbiBhbiBhZGRy
ZXNzIHNoYXJpbmcgZW52aXJvbm1lbnQgd2l0aG91dA0KPnNwZWNpYWwgaGFuZGxpbmcgW1JGQzYy
NjldLiINCg0KW2lmXSBPSy4gUmV3b3JkZWQgdmVyc2lvbjoNCg0KVGhlIHNvbHV0aW9uIHNwZWNp
ZmllZCBpbiB0aGlzIGRvY3VtZW50IGFsbG93cyB0aGUgYXNzaWdubWVudCBvZg0KICAgZWl0aGVy
IGEgZnVsbCBJUHY0IGFkZHJlc3MgZm9yIGEgQ1BFLCBvciBhIHNpbmdsZSBJUHY0IGFkZHJlc3Mg
d2hpY2ggaXMNCnNoYXJlZCBiZXR3ZWVuIG11bHRpcGxlIENQRXMuICBbUkZDNzA0MF0NCiAgIHBy
b3ZpZGVzIGEgbWVjaGFuaXNtIGZvciBhc3NpZ25pbmcgYSBmdWxsIElQdjQgYWRkcmVzcyBvbmx5
Lg0KDQoNCj4NCj5bNV0gU2VjdGlvbiA1LjEuICBMaWdodHdlaWdodCBCNCBQcm92aXNpb25pbmcg
d2l0aCBESENQdjYNCj4NCj4gICBGb3IgREhDUHY2IGJhc2VkIGNvbmZpZ3VyYXRpb24gb2YgdGhl
c2UgcGFyYW1ldGVycywgdGhlIGx3QjQgU0hPVUxEDQo+ICAgaW1wbGVtZW50IE9QVElPTl9TNDZf
Q09OVF9MVw0KPg0KPldoYXQgYXJlIHRoZSBjb25zZXF1ZW5jZXMgb2Ygbm90IGRvaW5nIHRoYXQ/
ICBUaGUgY291bGQgYmUgYWRkcmVzc2VkDQo+YnkgY2hhbmdpbmcgdGhhdCAiU0hPVUxEIiB0byBh
ICJNVVNUIiwgYWx0aG91Z2ggSSBzdXNwZWN0IHRoYXQgd2hhdCdzDQo+d2FudGVkIGhlcmUgaXMg
YSBmb3J3YXJkIHJlZmVyZW5jZSB0byB0aGUgYWx0ZXJuYXRpdmVzIGRpc2N1c3NlZCBpbg0KPlNl
Y3Rpb24gNy4NCg0KW2lmXSBSZXdvcmRpbmcgd2l0aDoNCg0KVG8gY29uZmlndXJlIHRoZXNlIHBh
cmFtZXRlcnMgdXNpbmcgREhDUHY2LCB0aGUgbHdCNCBNVVNUIGltcGxlbWVudA0KT1BUSU9OX1M0
Nl9DT05UX0xXLg0KDQoNCj4NCj5bNl0gQWxzbyBpbiBTZWN0aW9uIDUuMQ0KPg0KPiAgIElmIHN0
YXRlZnVsIElQdjQgY29uZmlndXJhdGlvbiBvciBhZGRpdGlvbmFsIElQdjQgY29uZmlndXJhdGlv
bg0KPiAgIGluZm9ybWF0aW9uIGlzIHJlcXVpcmVkLCBESENQdjQgW1JGQzIxMzFdIG11c3QgYmUg
dXNlZC4NCj4NCj4ibXVzdCIgLT4gIk1VU1QiDQo+DQo+ICAgSW4gdGhlIGV2ZW50IHRoYXQgdGhl
IGx3QjQncyBlbmNhcHN1bGF0aW9uIHNvdXJjZSBhZGRyZXNzIGlzIGNoYW5nZWQNCj4gICBmb3Ig
YW55IHJlYXNvbiAoc3VjaCBhcyB0aGUgREhDUHY2IGxlYXNlIGV4cGlyaW5nKSwgdGhlIGx3QjQn
cw0KPiAgIGR5bmFtaWMgcHJvdmlzaW9uaW5nIHByb2Nlc3MgbXVzdCBiZSByZS1pbml0aWF0ZWQu
DQo+DQo+Im11c3QiIC0+ICJNVVNUIg0KDQpbaWZdIE9LDQoNCj4NCj5bN10gQWxzbyBpbiBTZWN0
aW9uIDUuMQ0KPg0KPiAgIFVubGVzcyBhbiBsd0I0IGlzIGJlaW5nIGFsbG9jYXRlZCBhIGZ1bGwg
SVB2NCBhZGRyZXNzLCBpdCBpcw0KPiAgIFJFQ09NTUVOREVEIHRoYXQgUFNJRHMgY29udGFpbmlu
ZyB0aGUgd2VsbC1rbm93biBwb3J0cyAoMC0xMDIzKSBhcmUNCj4gICBub3QgYWxsb2NhdGVkIHRv
IGx3QjRzLg0KPg0KPlBsZWFzZSBleHBsYWluIHdoeS4gIEFsc28sICJ3ZWxsLWtub3duIHBvcnRz
IiBpcyBub3QgdGhlIHJpZ2h0IHRlcm07DQo+SSBiZWxpZXZlIHRob3NlIGFyZSB0aGUgInN5c3Rl
bSBwb3J0cyIsIGUuZy4sIHNlZToNCj4NCj5odHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRz
L3NlcnZpY2UtbmFtZXMtcG9ydC1udW1iZXJzL3NlcnZpY2UtbmFtZXMtcA0KPm9ydC1udW1iZXJz
LnhodG1sDQoNCltpZl0gUmV3b3JkZWQ6DQoNClVubGVzcyBhbiBsd0I0IGlzIGJlaW5nIGFsbG9j
YXRlZCBhIGZ1bGwgSVB2NCBhZGRyZXNzLCBpdCBpcw0KICAgUkVDT01NRU5ERUQgdGhhdCBQU0lE
cyBjb250YWluaW5nIHRoZSBzeXN0ZW0gcG9ydHMgKDAtMTAyMykgYXJlDQogICBub3QgYWxsb2Nh
dGVkIHRvIGx3QjRzLg0KDQoNCj4NCj4NCj5bOF0gU3RpbGwgaW4gU2VjdGlvbiA1LjENCj4NCj4g
ICBJbiB0aGUgZXZlbnQgdGhhdCB0aGUgbHdCNCByZWNlaXZlcyBhbiBJQ01QdjYgZXJyb3IgbWVz
c2FnZSAodHlwZSAxLA0KPiAgIGNvZGUgNSkgb3JpZ2luYXRpbmcgZnJvbSB0aGUgbHdBRlRSLCB0
aGUgbHdCNCBTSE9VTEQgaW50ZXJwcmV0IHRoaXMNCj4gICB0byBtZWFuIHRoYXQgbm8gbWF0Y2hp
bmcgZW50cnkgaW4gdGhlIGx3QUZUUidzIGJpbmRpbmcgdGFibGUgaGFzIGJlZW4NCj4gICBmb3Vu
ZC4gIFRoZSBsd0I0IE1BWSB0aGVuIHJlLWluaXRpYXRlIHRoZSBkeW5hbWljIHBvcnQtcmVzdHJp
Y3RlZA0KPiAgIHByb3Zpc2lvbmluZyBwcm9jZXNzLiAgVGhlIGx3QjQncyByZS1pbml0aWF0aW9u
IHBvbGljeSBTSE9VTEQgYmUNCj4gICBjb25maWd1cmFibGUuDQo+DQo+V2hhdCBoYXBwZW5zIGlm
IHRoZSBsd0I0IGlnbm9yZXMgdGhlIGZpcnN0ICJTSE9VTEQiPw0KDQoNCltpZl0gUmV3b3JkOg0K
Li4udGhlIGx3QjQgaW50ZXJwcmV0cyB0aGlzIHRvIG1lYW4gdGhhdCBubyBtYXRjaGluZyBlbnRy
eSBpbiB0aGUgbHdBRlRSJ3MNCmJpbmRpbmcgdGFibGUgaGFzIGJlZW4gZm91bmQsIHNvIHRoZSBJ
UHY0IHBheWxvYWQgaXMgbm90IGJlaW5nIGZvcndhcmRlZA0KYnkgdGhlIGx3QUZUUi4NCg0KDQoN
Cj4NCj5bOV0gU2VjdGlvbiA4LjEuICBJQ01QdjQgUHJvY2Vzc2luZyBieSB0aGUgbHdBRlRSDQo+
DQo+VGhpcyBkZXNjcmliZXMgdHdvIGFwcHJvYWNoZXMgdG8gSUNNUHY0IHByb2Nlc3NpbmcuICBB
cmUgdGhlcmUgYW55IG90aGVycz8NCj5JZiBzbywgcGxlYXNlIGFkZCBzb21lIHRleHQgYWJvdXQg
dGhlbSwgb3RoZXJ3aXNlLCBJIHN1Z2dlc3QgdGhpcyBjaGFuZ2U6DQo+DQo+T0xEDQo+ICAgQWRk
aXRpb25hbGx5LCB0aGUgbHdBRlRSIE1BWSBpbXBsZW1lbnQ6DQo+DQo+ICAgbyAgRGlzY2FyZGlu
ZyBvZiBhbGwgaW5ib3VuZCBJQ01QIG1lc3NhZ2VzLg0KPk5FVw0KPiAgIE90aGVyd2lzZSB0aGUg
bHdBRlRSIE1VU1QgZGlzY2FyZCBhbGwgaW5ib3VuZCBJQ01QdjQgbWVzc2FnZXMuDQoNCltpZl0g
T0sNCg0KPg0KPg0KPk5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KPg0KPi0tIFNlY3Rpb24gMS4g
IEludHJvZHVjdGlvbg0KPg0KPiAgIEJhc2ljIEJyaWRnaW5nIEJyb2FkQmFuZCBlbGVtZW50OiBB
IEI0IGVsZW1lbnQgaXMgYSBmdW5jdGlvbg0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBpbXBsZW1lbnRlZCBvbiBhIGR1YWwtc3RhY2sgY2FwYWJsZQ0KPiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBub2RlLCBlaXRoZXIgYSBkaXJlY3RseSBjb25uZWN0
ZWQNCj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgZGV2aWNlIG9yIGEgQ1BF
LCB0aGF0IGNyZWF0ZXMgYQ0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0
dW5uZWwgdG8gYW4gQUZUUi4NCj4NCj5JIHN1Z2dlc3QgY2hhbmdpbmcgImEgdHVubmVsIHRvIGFu
IEFGVFIiIHRvICJhbiBJUHY0LWluLUlQdjYgdHVubmVsDQo+dG8gYW4gQUZUUiIgZm9yIGNvbnNp
c3RlbmN5IHdpdGggdGhlIEFGVFIgZGVmaW5pdGlvbi4NCg0KW2lmXSBPSw0KDQo+DQo+LS0gU2Vj
dGlvbiA1LjIuICBMaWdodHdlaWdodCBCNCBEYXRhIFBsYW5lIEJlaGF2aW9yDQo+DQo+ICAgSW50
ZXJuYWxseSBjb25uZWN0ZWQgaG9zdHMgc291cmNlIElQdjQgcGFja2V0cyB3aXRoIGFuIFtSRkMx
OTE4XQ0KPiAgIGFkZHJlc3MuDQoNCltpZl0gUmV3b3JkIHdpdGg6DQoNCkhvc3RzIGNvbm5lY3Rl
ZCB0byB0aGUgY3VzdG9tZXIncyBuZXR3b3JrIGJlaGluZCB0aGUgbHdCNCBzb3VyY2UgSVB2NA0K
cGFja2V0cyB3aXRoIGFuIFtSRkMxOTE4XSBhZGRyZXNzLg0KDQoNCj4NCj5JbnRlcm5hbCB0byB3
aGF0PyAgUGxlYXNlIGV4cGxhaW4uDQo+DQo+LS0gU2VjdGlvbiA2LjIuICBsd0FGVFIgRGF0YSBQ
bGFuZSBCZWhhdmlvcg0KPg0KPiAgIFRoZSBsd0FGVFIgTVVTVCBzdXBwb3J0IGhhaXJwaW5uaW5n
IG9mIHRyYWZmaWMgYmV0d2VlbiB0d28gbHdCNHMsIGJ5DQo+ICAgcGVyZm9ybWluZyBkZS1jYXBz
dWxhdGlvbiBhbmQgcmUtZW5jYXBzdWxhdGlvbiBvZiBwYWNrZXRzLiAgVGhlDQo+ICAgaGFpcnBp
bm5pbmcgcG9saWN5IE1VU1QgYmUgY29uZmlndXJhYmxlLg0KPg0KPlBsZWFzZSBleHBsYWluICJo
YWlycGlubmluZyIgLSBpdCBzaG91bGQgc3VmZmljZSB0byBhZGQgImZyb20gb25lIGx3QjQNCj50
aGF0IG5lZWQgdG8gYmUgc2VudCB0byBhbm90aGVyIGx3QjQgYXNzb2NpYXRlZCB3aXRoIHRoZSBz
YW1lIEFGVFIiDQo+YWZ0ZXIgImRlLWNhcHN1bGF0aW9uIGFuZCByZS1lbmNhcHN1bGF0aW9uIG9m
IHBhY2tldHMiLg0KDQpbaWZdIE9LIHdpdGggdGhlIHN1Z2dlc3RlZCB3b3JkaW5nLg0KDQo+DQo+
LS0gU2VjdGlvbiA3LiAgQWRkaXRpb25hbCBJUHY0IGFkZHJlc3MgYW5kIFBvcnQgU2V0IFByb3Zp
c2lvbmluZw0KPk1lY2hhbmlzbXMNCj4NCj4gICBJbiBhIExpZ2h0d2VpZ2h0IDRvdmVyNiBkb21h
aW4sIHRoZSBiaW5kaW5nIGluZm9ybWF0aW9uIE1VU1QgYmUNCj4gICBhbGlnbmVkIGJldHdlZW4g
dGhlIGx3QjRzLCB0aGUgbHdBRlRScyBhbmQgdGhlIHByb3Zpc2lvbmluZyBzZXJ2ZXIuDQo+DQo+
ImFsaWduZWQgYmV0d2VlbiIgLT4gInN5bmNocm9uaXplZCBhY3Jvc3MiIGZvciBjb25zaXN0ZW5j
eSB3aXRoIHVzZQ0KPm9mIGZvcm1zIG9mICJzeW5jaHJvbml6ZSIgZWxzZXdoZXJlIGluIHRoaXMg
ZHJhZnQuDQoNCltpZl0gT0sNCg0KPg0KPmlkbml0cyBmb3VuZCBhIGZldyB0aGluZ3MgdG8gY29t
cGxhaW4gYWJvdXQ6DQo+DQo+LSBUaGUgdXNlIG9mICJ0aGUgd2VsbC1rbm93biByYW5nZSAxOTIu
MC4wLjAvMjkiIGluIFNlY3Rpb24gNS4xLiAgVGhpcyBpcw0KPm9rLA0KPglhcyBpdCdzIGRlc2Ny
aWJpbmcgRFMtTGl0ZSB1c2Ugb2YgdGhhdCByYW5nZSB0aGF0IGlzIGRvY3VtZW50ZWQNCj4JZWxz
ZXdoZXJlLiAgSWYgbHc0bzYgaXMgdXNpbmcgdGhhdCByYW5nZSwgYW4gZXhwbGFuYXRpb24gb3Vn
aHQgdG8gYmUNCj4JYWRkZWQgdG8gU2VjdGlvbiA1LjEuDQoNCltpZl0gbHc0bzYgZG9lc26p9nQg
dXNlIHRoZXNlDQoNCj4NCj4tIFRocmVlIHJlZmVyZW5jZXMgaGF2ZSBiZWVuIHVwZGF0ZWQ6DQo+
DQo+ICA9PSBPdXRkYXRlZCByZWZlcmVuY2U6IEEgbGF0ZXIgdmVyc2lvbiAoLTA5KSBleGlzdHMg
b2YNCj4gICAgIGRyYWZ0LWlldGYtc29mdHdpcmUtbWFwLWRoY3AtMDcNCj4NCj4gID09IE91dGRh
dGVkIHJlZmVyZW5jZTogZHJhZnQtaWV0Zi1kaGMtZGhjcHY0LW92ZXItZGhjcHY2IGhhcyBiZWVu
DQo+cHVibGlzaGVkDQo+ICAgICBhcyBSRkMgNzM0MQ0KPg0KPiAgPT0gT3V0ZGF0ZWQgcmVmZXJl
bmNlOiBBIGxhdGVyIHZlcnNpb24gKC0wNikgZXhpc3RzIG9mDQo+ICAgICBkcmFmdC1pZXRmLXBj
cC1wb3J0LXNldC0wNQ0KDQpbaWZdIEFsbCBzaG91bGQgbm93IGJlIGZpeGVkIGluIHYxMSAocG9z
dGVkIGVhcmxpZXIgdG9kYXkpDQoNCj4NCj4tLS0gU2VsZWN0ZWQgUkZDIDU3MDYgQXBwZW5kaXgg
QSBRJkEgZm9yIE9QUy1EaXIgcmV2aWV3IC0tLQ0KPg0KPkEuMS4xLiAgSGFzIGRlcGxveW1lbnQg
YmVlbiBkaXNjdXNzZWQ/DQo+DQo+CVllcywgdGhpcyBwcm90b2NvbCBpcyBpbnRlbmRlZCB0byBp
bXByb3ZlIHNjYWxhYmlsaXR5IG92ZXIgdGhlIGV4aXN0aW5nDQo+CURTLUxpdGUgbWVjaGFuaXNt
Lg0KPg0KPkEuMS4yLiAgSGFzIGluc3RhbGxhdGlvbiBhbmQgaW5pdGlhbCBzZXR1cCBiZWVuIGRp
c2N1c3NlZD8NCj4NCj4JTm8sIHRoZXJlIGFyZSB2YWd1ZSByZWZlcmVuY2VzIHRvIGEgcHJvdmlz
aW9uaW5nIG1lY2hhbmlzbSBhbmQNCj4Jc3luY2hyb25pemF0aW9uIGZ1bmN0aW9uYWxpdHkgdGhh
dCBuZWVkIHRvIGJlIHNldCB1cC4gIFNlZQ0KPgltYWpvciBvcGVuIGlzc3VlIFsyXSBhYm92ZSB3
aGljaCBjYWxscyBvdXQgYSBtaXNzaW5nIG5vcm1hdGl2ZQ0KPglyZWZlcmVuY2UgdGhhdCBzaG91
bGQgYWRkcmVzcyB0aGVzZSB0b3BpY3MuDQo+DQo+QS4xLjMuICBIYXMgdGhlIG1pZ3JhdGlvbiBw
YXRoIGJlZW4gZGlzY3Vzc2VkPw0KPg0KPglObywgYnV0IEkgc3VzcGVjdCB0aGF0IHRoaXMgY29u
Y2VybiBpcyBpbmFwcGxpY2FibGUsIGFzIEkgdGhpbmsNCj4JYSBjYXJyaWVyIHdvdWxkIG5vdCBt
aWdyYXRlIGZyb20gRFMtTGl0ZSB0byBsdzRvNiwgYnV0IHdvdWxkDQo+CWRlcGxveSBsdzRvNiBp
bnN0ZWFkIG9mIERTLUxpdGUuDQo+DQo+QS4xLjQuICBIYXZlIHRoZSBSZXF1aXJlbWVudHMgb24g
b3RoZXIgcHJvdG9jb2xzIGFuZCBmdW5jdGlvbmFsDQo+ICAgICAgIGNvbXBvbmVudHMgYmVlbiBk
aXNjdXNzZWQ/DQo+DQo+CVllcywgYnV0IG1ham9yIG9wZW4gaXNzdWUgWzFdIGlzIGVmZmVjdGl2
ZWx5IGluIHRoaXMgYXJlYS4NCj4NCj5BLjEuNi4gIEhhdmUgc3VnZ2VzdGlvbnMgZm9yIHZlcmlm
eWluZyBjb3JyZWN0IG9wZXJhdGlvbiBiZWVuIGRpc2N1c3NlZD8NCj4NCj4JTm8sIGFuZCB0aGV5
IHByb2JhYmx5IHNob3VsZCBiZSwgYXMgdGhpcyBwcm90b2NvbCByZXF1aXJlcyBzdGF0ZQ0KPglz
eW5jaHJvbml6YXRpb24gYW1vbmcgdGhlIGx3QjQsIGx3QUZUUiBhbmQgdGhlIHByb3Zpc2lvbmlu
ZyBzeXN0ZW0sDQo+CWFuZCBpcyBsaWtlbHkgdG8gZXhoaWJpdCBwcm9ibGVtYXRpYyBiZWhhdmlv
ciBpZiB0aGUgcmVsZXZhbnQgc3RhdGUNCj4JaW5mb3JtYXRpb24gZ2V0cyBvdXQgb2Ygc3luYy4N
Cj4NCj5BLjEuOS4gIElzIGNvbmZpZ3VyYXRpb24gZGlzY3Vzc2VkPw0KPg0KPglZZXMsIHRoZSBk
cmFmdCBkb2VzIGEgZ29vZCBqb2Igb2YgZGlzY3Vzc2luZyB3aGF0IG5lZWRzIHRvIGJlDQo+CWNv
bmZpZ3VyZWQgdG8gc2V0IHVwIHRoZSBwcm90b2NvbCAoYXNpZGUgZnJvbSBzdGF0ZSBzeW5jaHJv
bml6YXRpb24pDQo+CWFuZCBjYWxsaW5nIG91dCBwcm90b2NvbCBiZWhhdmlvciBhc3BlY3RzIHRo
YXQgc2hvdWxkIGJlIGNvbmZpZ3VyYWJsZS4NCj4NCj5BLjIgTWFuYWdlbWVudA0KPg0KPglUaGlz
IGlzIHJlYWxseSBub3QgZGlzY3Vzc2VkLCBhbmQgaW4gcGFydGljdWxhciB0aGUgbGFjayBvZiBk
aXNjdXNzaW9uDQo+CW9mIG1hbmFnZW1lbnQgaW5mb3JtYXRpb24gaXMgbm90YWJsZSBiZWNhdXNl
IHRoaXMgcHJvdG9jb2wgaGFzIGENCj4JZGlmZmVyZW50IG9wZXJhdGlvbmFsIHN0cnVjdHVyZSB0
aGFuIERTLUxpdGUuICBTbywgc3BlY2lmaWNhbGx5Og0KPg0KPiBBLjIuMi4gIElzIG1hbmFnZW1l
bnQgaW5mb3JtYXRpb24gZGlzY3Vzc2VkPw0KPg0KPglObywgdGhpcyBpcyBtaW5vciBvcGVuIGlz
c3VlIFszXS4gIEEgc2VudGVuY2UgcG9pbnRpbmcgdG8gYXBwbGljYWJsZQ0KPglNSUIgYW5kL29y
IFlBTkcgZHJhZnQocykgd291bGQgc3VmZmljZSB0byBhZGRyZXNzIHRoaXMuDQo+DQo+QS4yLjQu
ICBJcyBjb25maWd1cmF0aW9uIG1hbmFnZW1lbnQgZGlzY3Vzc2VkPw0KPg0KPglZZXMgLSB0aGUg
ZGlzY3Vzc2lvbiBpcyBvaywgZXZlbiB0aG91Z2ggc3BlY2lmaWMgY29uZmlndXJhdGlvbiBtZWNo
YW5pc21zDQo+CWFyZSBub3QgZGlzY3Vzc2VkLg0KPg0KPkEuMy4gIERvY3VtZW50YXRpb24NCj4N
Cj4JVGhlIHByb3RvY29sIGRvZXMgaGF2ZSBzaWduaWZpY2FudCBvcGVyYXRpb25hbCBpbXBhY3Rz
IG9uIHRoZSBJbnRlcm5ldC4NCj4NCj4JVGhlIHNoZXBoZXJkJ3Mgd3JpdGV1cCBpbmRpY2F0ZXMg
dGhhdCBtdWx0aXBsZSBpbXBsZW1lbnRhdGlvbnMgZXhpc3QNCj4JYW1vbmcgd2hpY2ggaW50ZXJv
cGVyYWJpbGl0eSBoYXMgYmVlbiB0ZXN0ZWQuDQo+DQo+VGhhbmtzLA0KPi0tRGF2aWQNCj4tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+RGF2aWQg
TC4gQmxhY2ssIERpc3Rpbmd1aXNoZWQgRW5naW5lZXINCj5FTUMgQ29ycG9yYXRpb24sIDE3NiBT
b3V0aCBTdC4sIEhvcGtpbnRvbiwgTUEgIDAxNzQ4DQo+KzEgKDUwOCkgMjkzLTc5NTMgICAgICAg
ICAgICAgRkFYOiArMSAoNTA4KSAyOTMtNzc4Ng0KPmRhdmlkLmJsYWNrQGVtYy5jb20gICAgICAg
IE1vYmlsZTogKzEgKDk3OCkgMzk0LTc3NTQNCj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+DQoNCg0K


From nobody Wed Oct 15 11:10:57 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30FC01A902D; Wed, 15 Oct 2014 11:10:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VvN_WgqPkCqt; Wed, 15 Oct 2014 11:10:35 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 411F21A8AFE; Wed, 15 Oct 2014 11:10:35 -0700 (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 Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 19AE51B829E; Wed, 15 Oct 2014 11:10:35 -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 ESMTP id 0D27253E073; Wed, 15 Oct 2014 11:10:35 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 15 Oct 2014 11:10:34 -0700
Content-Type: text/plain; charset="euc-kr"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <D0647743.DE00C%ian.farrer@telekom.de>
Date: Wed, 15 Oct 2014 13:10:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <3D6BF2A4-62B1-4F2C-BE04-57F5DBD3B1D7@nominum.com>
References: <D0647743.DE00C%ian.farrer@telekom.de>
To: <ian.farrer@telekom.de>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/nCpwXxz-zt8CpGpGUrfYY35i_kM
Cc: ops-dir@ietf.org, ietf@ietf.org, david.black@emc.com, draft-ietf-softwire-lw4over6@tools.ietf.org, softwires@ietf.org, gen-art@ietf.org
Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 15 Oct 2014 18:10:38 -0000

On Oct 15, 2014, at 12:12 PM, ian.farrer@telekom.de wrote:
> The consequence of this architecture is that the information =
maintained by
> the provisioning mechanism and the one maintained by the lwAFTR MUST =
be
> synchronized (See figure 2).  The details of this synchronization =
depend
> on the exact provisioning mechanism and protocols that are in use by =
the
> operator. If no automated process for this synchronisation is in use, =
then
> information in the provisioning systems and the lwAFTR MUST be
> synchronised manually, e.g. by copying aligned configuration files to =
each
> of the elements.

It might be better to simply say "the precise mechanism whereby this =
synchronization occurs is out of scope for this document."


From nobody Wed Oct 15 13:29:04 2014
Return-Path: <david.black@emc.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8551A7001; Wed, 15 Oct 2014 13:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.711
X-Spam-Level: 
X-Spam-Status: No, score=-3.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXmaqnCJvY2r; Wed, 15 Oct 2014 13:28:13 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8A271ACC82; Wed, 15 Oct 2014 13:28:12 -0700 (PDT)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9FKRUxA005014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Oct 2014 16:27:30 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com s9FKRUxA005014
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1413404853; bh=vheZlH+NhcdqcBEmC3g/sVp6t14=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=onnj7OcBOjlv82LAaOAgEgZaMh5l/Fol0MWSoMdGaxDnMv17VVwhaPeGOE9hRufD9 bbzlgKLZN1rGqLQ9xjhntDv/BVnL97oYaWRRmlBfgcv8sqxVDBVU0sSieRt/mNRKdt AUanog5gGIgrUig/sFol7ZuUZyhrE4gYwYt415TY=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com s9FKRUxA005014
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd55.lss.emc.com (RSA Interceptor); Wed, 15 Oct 2014 16:26:50 -0400
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9FKR8N2030667 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Oct 2014 16:27:09 -0400
Received: from MXHUB103.corp.emc.com (10.253.50.16) by mxhub09.corp.emc.com (10.254.92.104) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 15 Oct 2014 16:27:08 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB103.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Wed, 15 Oct 2014 16:27:08 -0400
From: "Black, David" <david.black@emc.com>
To: "ian.farrer@telekom.de" <ian.farrer@telekom.de>, "yong@csnet1.cs.tsinghua.edu.cn" <yong@csnet1.cs.tsinghua.edu.cn>, "sunqiong@ctbri.com.cn" <sunqiong@ctbri.com.cn>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "tena@huawei.com" <tena@huawei.com>, "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>
Thread-Topic: Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
Thread-Index: Ac/lou8B9zKSJooyTsOMrMdwtE6r4ADGPF8AAAg3UhA=
Date: Wed, 15 Oct 2014 20:27:06 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com> <D0646F50.DDFC8%ian.farrer@telekom.de>
In-Reply-To: <D0646F50.DDFC8%ian.farrer@telekom.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.122]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: DLM_1, public, GIS Solicitation
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/U2qKszmZdQY3TAjJnvgbs95W4cQ
X-Mailman-Approved-At: Wed, 15 Oct 2014 13:28:59 -0700
Cc: "softwires@ietf.org" <softwires@ietf.org>, "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 15 Oct 2014 20:28:21 -0000

Hi Ian,

Many thanks for the comprehensive response - I've extracted [1], [2]
and [7] for further attention here - your proposals for all of the
other items and nits are fine with me.

I think the only open topic is [7], and I can live w/your proposed
rephrasing for that even though I'd like to see a sentence of
rationale added.

> >[1] There are a number of places where SHOULD is used to refer to
> > requirements in another RFC, e.g., the following text in section 5.1:

[... snip ...]

> [if] OK with the above proposals.

I supplied new text for 5.1 - please also make the corresponding changes
in 5.2.1 (twice) and 8.2, plus check whether this "SHOULD" problem
occurs elsewhere.

> >[2] Section 4.  Lightweight 4over6 Architecture
> >
> >   The consequence of this architecture is that the information
> >   maintained by the provisioning mechanism and the one maintained by
> >   the lwAFTR MUST be synchronized (See figure 2).  The details of this
> >   synchronization depend on the exact provisioning mechanism and will
> >   be discussed in a companion document.
> >
> >I believe that this "companion document" needs to be cited as a
> >normative reference.  The above text's vague allusion to the specificati=
on
> >of how to implement a "MUST" requirement is insufficient.
>
> [if] The synch mechanism is really down to how an operator has deployed
> the service, the specific provisioning protocols in use etc. What about
> the following wording change?:
>=20
> The consequence of this architecture is that the information maintained b=
y
> the provisioning mechanism and the one maintained by the lwAFTR MUST be
> synchronized (See figure 2).  The details of this synchronization depend
> on the exact provisioning mechanism and protocols that are in use by the
> operator. If no automated process for this synchronisation is in use, the=
n
> information in the provisioning systems and the lwAFTR MUST be
> synchronised manually, e.g. by copying aligned configuration files to eac=
h
> of the elements.

That wording change is fine, and I prefer it to Ted's subsequent suggestion
of shorter "out of scope" language.

My primary concern was the reference to a "companion document" which lead
to an obvious "where is that???" question.  The new wording removes that
reference and provides some useful information on how the required
synchronization could be accomplished.

> >[7] Also in Section 5.1
> >
> >   Unless an lwB4 is being allocated a full IPv4 address, it is
> >   RECOMMENDED that PSIDs containing the well-known ports (0-1023) are
> >   not allocated to lwB4s.
> >
> >Please explain why.  Also, "well-known ports" is not the right term;
> >I believe those are the "system ports", e.g., see:
> >
> >http://www.iana.org/assignments/service-names-port-numbers/service-names=
-p
> >ort-numbers.xhtml
>=20
> [if] Reworded:
>=20
> Unless an lwB4 is being allocated a full IPv4 address, it is
>    RECOMMENDED that PSIDs containing the system ports (0-1023) are
>    not allocated to lwB4s.

Why?  Please add a sentence to explain, although I'll be ok if all that
is done is the rewording.

Thanks,
--David

> -----Original Message-----
> From: ian.farrer@telekom.de [mailto:ian.farrer@telekom.de]
> Sent: Wednesday, October 15, 2014 1:06 PM
> To: Black, David; yong@csnet1.cs.tsinghua.edu.cn; sunqiong@ctbri.com.cn;
> mohamed.boucadair@orange.com; tena@huawei.com; yiu_lee@cable.comcast.com;=
 gen-
> art@ietf.org; ops-dir@ietf.org
> Cc: ietf@ietf.org; softwires@ietf.org
> Subject: Re: Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-1=
0
>=20
> Hi David,
>=20
> Many thanks for the review. Please see comments inline.
>=20
> Cheers,
> Ian
>=20
>=20
>=20
> On 12/10/2014 00:30, "Black, David" <david.black@emc.com> wrote:
>=20
> >This is a combined Gen-ART and OPS-DIR review.  Boilerplate for both
> >follows,
> >and I apologize for it being a day late - United Airlines got me back to
> >Boston after midnight last night on a plane w/o working WiFi.
> >
> >I am the assigned Gen-ART reviewer for this draft. For background on
> >Gen-ART, please see the FAQ at:
> >
> ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> >Please resolve these comments along with any other Last Call comments yo=
u may receive.
> >
> >I have reviewed this document as part of the Operational directorate's o=
ngoing
> >effort to review all IETF documents being processed by the IESG.  These =
comments
> >were written primarily for the benefit of the operational area directors=
.
> >Document editors and WG chairs should treat these comments just like any=
 other
> >last call comments.
> >
> >Document: draft-ietf-softwire-lw4over6-10
> >Reviewer: David Black
> >Review Date: October 10, 2014
> >IETF LC End Date: October 10, 2014
> >IESG Telechat date: October 16, 2014
> >
> >Summary: This draft is on the right track, but has open issues
> > 		described in the review.
> >
> >This draft describes an extension to Dual-Stack Lite that relocates the =
NAPT
> >functionality from the centralized tunnel concentrator to the DS-Lite cl=
ient
> >- doing so has significant scalability benefits.  The draft is generally
> >readable although understanding why some of the processing needs to be d=
one
> >in the manner specified requires strong familiarity with both DS-Lite an=
d NAPT.
> >
> >The draft is generally in good shape - I found three issues that I consi=
der
> >to be significant, the most important of which are sloppiness in use of
> >RFC 2119 keywords, particularly in Section 5.1, and omission of what
> >appears to be a necessary normative reference.
> >
> >Major issues (2):
> >
> >[1] There are a number of places where SHOULD is used to refer to requir=
ement
> >in another RFC, e.g., the following text in section 5.1:
> >
> >   The DNS considerations described in Section 5.5 and Section 6.4 of
> >   [RFC6333] SHOULD be followed.
> >
> >This has the side effect of weakening any MUST requirement in the refere=
nced
> >RFC(s) to a SHOULD, which was probably not intended, and needs to be exp=
licitly
> >stated if it was intended.  Here's a possible rephrasing:
> >
> >   The DNS considerations described in Section 5.5 and Section 6.4 of
> >   [RFC6333] apply to Lightweight 4over6; lw4o6 implementations MUST
> >   comply with all requirements stated there.
> >
> >The additional places where this occurs are:
> >
> >- Section 5.2.1 (twice):
> >
> >   For TCP and UDP traffic the NAPT44 implemented in the lwB4 SHOULD
> >   conform with the behaviour and best current practices documented in
> >   [RFC4787], [RFC5508], and [RFC5382].  If the lwB4 supports DCCP, then
> >   the requirements in [RFC5597] SHOULD be implemented.
> >
> >- Section 8.2:
> >
> >   The lwB4 SHOULD implement the requirements defined in [RFC5508] for
> >   ICMP forwarding.
>=20
> [if] OK with the above proposals.
>=20
>=20
> >
> >[2] Section 4.  Lightweight 4over6 Architecture
> >
> >   The consequence of this architecture is that the information
> >   maintained by the provisioning mechanism and the one maintained by
> >   the lwAFTR MUST be synchronized (See figure 2).  The details of this
> >   synchronization depend on the exact provisioning mechanism and will
> >   be discussed in a companion document.
> >
> >I believe that this "companion document" needs to be cited as a
> >normative reference.  The above text's vague allusion to the specificati=
on
> >of how to implement a "MUST" requirement is insufficient.
>=20
> [if] The synch mechanism is really down to how an operator has deployed
> the service, the specific provisioning protocols in use etc. What about
> the following wording change?:
>=20
> The consequence of this architecture is that the information maintained b=
y
> the provisioning mechanism and the one maintained by the lwAFTR MUST be
> synchronized (See figure 2).  The details of this synchronization depend
> on the exact provisioning mechanism and protocols that are in use by the
> operator. If no automated process for this synchronisation is in use, the=
n
> information in the provisioning systems and the lwAFTR MUST be
> synchronised manually, e.g. by copying aligned configuration files to eac=
h
> of the elements.
>=20
>=20
> >
> >Minor issues (7):
> >
> >[3] The lack of discussion of management information is an
> >omission.  See A.2.2 below in the OPS-Dir review section of this email
> >and the discussion in Section 3.2 of RFC 5706.  A sentence pointing
> >at an applicable MIB and/or YANG draft or drafts would suffice.
>=20
> [if] There is a draft for a softwire YANG model which is due to be
> published shortly. We'll add an informative reference to this.
>=20
> >
> >[4] Section 4.  Lightweight 4over6 Architecture
> >
> >   The solution specified in this document allows the assignment of
> >   either a full or a shared IPv4 address requesting CPEs.  [RFC7040]
> >   provides a mechanism for assigning a full IPv4 address only.
> >
> >Please explain what entities would share the IPv4 address.  For example,
> >this is needed as a foundation for the statement in Section 8 that
> >"ICMPv4 does not work in an address sharing environment without
> >special handling [RFC6269]."
>=20
> [if] OK. Reworded version:
>=20
> The solution specified in this document allows the assignment of
>    either a full IPv4 address for a CPE, or a single IPv4 address which i=
s
> shared between multiple CPEs.  [RFC7040]
>    provides a mechanism for assigning a full IPv4 address only.
>=20
>=20
> >
> >[5] Section 5.1.  Lightweight B4 Provisioning with DHCPv6
> >
> >   For DHCPv6 based configuration of these parameters, the lwB4 SHOULD
> >   implement OPTION_S46_CONT_LW
> >
> >What are the consequences of not doing that?  The could be addressed
> >by changing that "SHOULD" to a "MUST", although I suspect that what's
> >wanted here is a forward reference to the alternatives discussed in
> >Section 7.
>=20
> [if] Rewording with:
>=20
> To configure these parameters using DHCPv6, the lwB4 MUST implement
> OPTION_S46_CONT_LW.
>=20
>=20
> >
> >[6] Also in Section 5.1
> >
> >   If stateful IPv4 configuration or additional IPv4 configuration
> >   information is required, DHCPv4 [RFC2131] must be used.
> >
> >"must" -> "MUST"
> >
> >   In the event that the lwB4's encapsulation source address is changed
> >   for any reason (such as the DHCPv6 lease expiring), the lwB4's
> >   dynamic provisioning process must be re-initiated.
> >
> >"must" -> "MUST"
>=20
> [if] OK
>=20
> >
> >[7] Also in Section 5.1
> >
> >   Unless an lwB4 is being allocated a full IPv4 address, it is
> >   RECOMMENDED that PSIDs containing the well-known ports (0-1023) are
> >   not allocated to lwB4s.
> >
> >Please explain why.  Also, "well-known ports" is not the right term;
> >I believe those are the "system ports", e.g., see:
> >
> >http://www.iana.org/assignments/service-names-port-numbers/service-names=
-p
> >ort-numbers.xhtml
>=20
> [if] Reworded:
>=20
> Unless an lwB4 is being allocated a full IPv4 address, it is
>    RECOMMENDED that PSIDs containing the system ports (0-1023) are
>    not allocated to lwB4s.
>=20
>=20
> >
> >
> >[8] Still in Section 5.1
> >
> >   In the event that the lwB4 receives an ICMPv6 error message (type 1,
> >   code 5) originating from the lwAFTR, the lwB4 SHOULD interpret this
> >   to mean that no matching entry in the lwAFTR's binding table has been
> >   found.  The lwB4 MAY then re-initiate the dynamic port-restricted
> >   provisioning process.  The lwB4's re-initiation policy SHOULD be
> >   configurable.
> >
> >What happens if the lwB4 ignores the first "SHOULD"?
>=20
>=20
> [if] Reword:
> ...the lwB4 interprets this to mean that no matching entry in the lwAFTR'=
s
> binding table has been found, so the IPv4 payload is not being forwarded
> by the lwAFTR.
>=20
>=20
>=20
> >
> >[9] Section 8.1.  ICMPv4 Processing by the lwAFTR
> >
> >This describes two approaches to ICMPv4 processing.  Are there any other=
s?
> >If so, please add some text about them, otherwise, I suggest this change=
:
> >
> >OLD
> >   Additionally, the lwAFTR MAY implement:
> >
> >   o  Discarding of all inbound ICMP messages.
> >NEW
> >   Otherwise the lwAFTR MUST discard all inbound ICMPv4 messages.
>=20
> [if] OK
>=20
> >
> >
> >Nits/editorial comments:
> >
> >-- Section 1.  Introduction
> >
> >   Basic Bridging BroadBand element: A B4 element is a function
> >                                     implemented on a dual-stack capable
> >                                     node, either a directly connected
> >                                     device or a CPE, that creates a
> >                                     tunnel to an AFTR.
> >
> >I suggest changing "a tunnel to an AFTR" to "an IPv4-in-IPv6 tunnel
> >to an AFTR" for consistency with the AFTR definition.
>=20
> [if] OK
>=20
> >
> >-- Section 5.2.  Lightweight B4 Data Plane Behavior
> >
> >   Internally connected hosts source IPv4 packets with an [RFC1918]
> >   address.
>=20
> [if] Reword with:
>=20
> Hosts connected to the customer's network behind the lwB4 source IPv4
> packets with an [RFC1918] address.
>=20
>=20
> >
> >Internal to what?  Please explain.
> >
> >-- Section 6.2.  lwAFTR Data Plane Behavior
> >
> >   The lwAFTR MUST support hairpinning of traffic between two lwB4s, by
> >   performing de-capsulation and re-encapsulation of packets.  The
> >   hairpinning policy MUST be configurable.
> >
> >Please explain "hairpinning" - it should suffice to add "from one lwB4
> >that need to be sent to another lwB4 associated with the same AFTR"
> >after "de-capsulation and re-encapsulation of packets".
>=20
> [if] OK with the suggested wording.
>=20
> >
> >-- Section 7.  Additional IPv4 address and Port Set Provisioning
> >Mechanisms
> >
> >   In a Lightweight 4over6 domain, the binding information MUST be
> >   aligned between the lwB4s, the lwAFTRs and the provisioning server.
> >
> >"aligned between" -> "synchronized across" for consistency with use
> >of forms of "synchronize" elsewhere in this draft.
>=20
> [if] OK
>=20
> >
> >idnits found a few things to complain about:
> >
> >- The use of "the well-known range 192.0.0.0/29" in Section 5.1.  This i=
s
> >ok,
> >	as it's describing DS-Lite use of that range that is documented
> >	elsewhere.  If lw4o6 is using that range, an explanation ought to be
> >	added to Section 5.1.
>=20
> [if] lw4o6 doesn=B9t use these
>=20
> >
> >- Three references have been updated:
> >
> >  =3D=3D Outdated reference: A later version (-09) exists of
> >     draft-ietf-softwire-map-dhcp-07
> >
> >  =3D=3D Outdated reference: draft-ietf-dhc-dhcpv4-over-dhcpv6 has been
> >published
> >     as RFC 7341
> >
> >  =3D=3D Outdated reference: A later version (-06) exists of
> >     draft-ietf-pcp-port-set-05
>=20
> [if] All should now be fixed in v11 (posted earlier today)
>=20
> >
> >--- Selected RFC 5706 Appendix A Q&A for OPS-Dir review ---
> >
> >A.1.1.  Has deployment been discussed?
> >
> >	Yes, this protocol is intended to improve scalability over the existing
> >	DS-Lite mechanism.
> >
> >A.1.2.  Has installation and initial setup been discussed?
> >
> >	No, there are vague references to a provisioning mechanism and
> >	synchronization functionality that need to be set up.  See
> >	major open issue [2] above which calls out a missing normative
> >	reference that should address these topics.
> >
> >A.1.3.  Has the migration path been discussed?
> >
> >	No, but I suspect that this concern is inapplicable, as I think
> >	a carrier would not migrate from DS-Lite to lw4o6, but would
> >	deploy lw4o6 instead of DS-Lite.
> >
> >A.1.4.  Have the Requirements on other protocols and functional
> >       components been discussed?
> >
> >	Yes, but major open issue [1] is effectively in this area.
> >
> >A.1.6.  Have suggestions for verifying correct operation been discussed?
> >
> >	No, and they probably should be, as this protocol requires state
> >	synchronization among the lwB4, lwAFTR and the provisioning system,
> >	and is likely to exhibit problematic behavior if the relevant state
> >	information gets out of sync.
> >
> >A.1.9.  Is configuration discussed?
> >
> >	Yes, the draft does a good job of discussing what needs to be
> >	configured to set up the protocol (aside from state synchronization)
> >	and calling out protocol behavior aspects that should be configurable.
> >
> >A.2 Management
> >
> >	This is really not discussed, and in particular the lack of discussion
> >	of management information is notable because this protocol has a
> >	different operational structure than DS-Lite.  So, specifically:
> >
> > A.2.2.  Is management information discussed?
> >
> >	No, this is minor open issue [3].  A sentence pointing to applicable
> >	MIB and/or YANG draft(s) would suffice to address this.
> >
> >A.2.4.  Is configuration management discussed?
> >
> >	Yes - the discussion is ok, even though specific configuration mechanis=
ms
> >	are not discussed.
> >
> >A.3.  Documentation
> >
> >	The protocol does have significant operational impacts on the Internet.
> >
> >	The shepherd's writeup indicates that multiple implementations exist
> >	among which interoperability has been tested.
> >
> >Thanks,
> >--David
> >----------------------------------------------------
> >David L. Black, Distinguished Engineer
> >EMC Corporation, 176 South St., Hopkinton, MA  01748
> >+1 (508) 293-7953             FAX: +1 (508) 293-7786
> >david.black@emc.com        Mobile: +1 (978) 394-7754
> >----------------------------------------------------
> >


From nobody Wed Oct 15 15:10:27 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 649931ACDC3; Wed, 15 Oct 2014 14:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3yB_zQdVXha; Wed, 15 Oct 2014 14:55:19 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C505D1A00E4; Wed, 15 Oct 2014 14:55:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1CC932CCF9; Thu, 16 Oct 2014 00:55:18 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ek9jP3yRQKad; Thu, 16 Oct 2014 00:55:09 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4540D2CC5D; Thu, 16 Oct 2014 00:55:07 +0300 (EEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_79FD7092-F2DB-40C2-9F1A-A262E9B2818C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com>
Date: Wed, 15 Oct 2014 14:55:05 -0700
Message-Id: <03DF5500-847C-42F2-BCF4-B79E2B7B6BCB@piuha.net>
References: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com> <D0646F50.DDFC8%ian.farrer@telekom.de> <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/FPaD7eTPAJ1i6vnr1JoCW0UzVeI
X-Mailman-Approved-At: Wed, 15 Oct 2014 15:10:18 -0700
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "sunqiong@ctbri.com.cn" <sunqiong@ctbri.com.cn>, "softwires@ietf.org" <softwires@ietf.org>, "tena@huawei.com" <tena@huawei.com>
Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 15 Oct 2014 21:55:20 -0000

--Apple-Mail=_79FD7092-F2DB-40C2-9F1A-A262E9B2818C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Thank you for the substantive review, David. And thank you Ian et al for =
the effort to answer the questions in the review. At this point I think =
it looks like you are on your way to address everything that has been =
brought up, at least on the level where I feel that I have no blocking =
comments to make in the IESG review. I plan to ballot No-Objection, but =
keep monitoring this thread.

Jari


--Apple-Mail=_79FD7092-F2DB-40C2-9F1A-A262E9B2818C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJUPu05AAoJEM80gCTQU46qJj4P/0KFNZEBFX/9CG2odEqLpsXv
KFNOgYmJSvGyT61IluVXfGLQbveq5P4hBoTe7Z+8lQXkE+5iqyyLf5CYA7Wv7zjS
gUXvp66IQIqSmCUxz0kQzbgvhn34ckPddpr3vWrH03T9oGzyT8ict/G1mJInI8YF
nFm7pJ2PhxdVmf2in9aAY5hZG1qbVOyN4IRbNo3fBjDrKpFUQHpfYoY20olm4iVf
AcPpgwkXAoKvBMqB2eZTvDK4KvSxdFPTeIDKy8+ItQ09dpCf/IoZn6UmqaWMD9Lz
cDgK5JPgb8+V9vM808OyPaokbCCSA01JZhIMADfJuxcZUQo0yrou/5wFwoRk2zgl
RIy7TPSL/XWGQL4W9DP4ZgYMghZycxyuH85DVH2jxmDRvx0Gh8m1AOx13gVat7KT
LbEZ99wSRGo0nAbhzy0oC4HIAy3Ii0UBFoWzRD4dCXq9iIztpWnZhsf8TXXNo8bV
c+ybb7LYUs/WXFYksFXrZ243hjJtcyNOcvx+SbofwjLojbeqv/C6n+/jYRDVCDaV
SkITGAPOptaKC1baenK+nk3q4UI2HULUin2rsOQESzqM5afUvRnmwgdymFSFrVyK
DdCt2s2Lx0Rhu2FmabAD0fGCc5S8n8JZPh5pjj9OMnZ8ZtmHBqvkUebSw5hdwyki
C89pEWR/XM1W+IIc2vqr
=7Ed4
-----END PGP SIGNATURE-----

--Apple-Mail=_79FD7092-F2DB-40C2-9F1A-A262E9B2818C--


From nobody Thu Oct 16 02:25:06 2014
Return-Path: <despres.remi@laposte.net>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF2371A6FE6 for <softwires@ietfa.amsl.com>; Thu, 16 Oct 2014 02:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.249
X-Spam-Level: 
X-Spam-Status: No, score=-1.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-MkTjefy4L8 for <softwires@ietfa.amsl.com>; Thu, 16 Oct 2014 02:24:52 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07B071A1AB6 for <softwires@ietf.org>; Thu, 16 Oct 2014 02:24:51 -0700 (PDT)
Received: from filter.sfr.fr (localhost [78.193.136.169]) by msfrf2102.sfr.fr (SMTP Server) with ESMTP id 13A7C70000FB; Thu, 16 Oct 2014 11:25:48 +0200 (CEST)
Authentication-Results: sfrmc.priv.atos.fr; dkim=none (no signature); dkim-adsp=none (no policy) header.from=despres.remi@laposte.net
Received: from [192.168.0.21] (unknown [78.193.136.169])	(using TLSv1 with cipher AES128-SHA (128/128 bits))	(No client certificate requested) by msfrf2102.sfr.fr (SMTP Server) with ESMTP id 46E7070000F6; Thu, 16 Oct 2014 11:25:47 +0200 (CEST)
X-SFR-UUID: 20141016092547290.46E7070000F6@msfrf2102.sfr.fr
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: =?iso-8859-1?q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <D14390B1-8628-4372-B664-A5EA82BE0327@employees.org>
Date: Thu, 16 Oct 2014 11:24:48 +0200
Message-Id: <25A95528-FA71-48C6-B238-D5D90B99386B@laposte.net>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com> <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org> <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com> <D14390B1-8628-4372-B664-A5EA82BE0327@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/kuloQ-xY4S9f-rQW-ALC7YdTbeA
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 16 Oct 2014 09:24:58 -0000

Hi, Ole,

FWIW, a look at =
https://tools.ietf.org/html/draft-ietf-softwire-4rd-09#section-4.6.3 =
might be helpful.

Cheers,
RD


Le 15 oct. 2014 =E0 15:27, Ole Troan <otroan@employees.org> a =E9crit :

> Ted, et al,
>=20
> there are good arguments going both ways, so apologies for my changing =
opinion here. ;-)
>=20
> we could go with the hand-wavy, there is a problem here, we don't have =
a good solution:
>=20
>       <t>If two IPv4 host behind two different MAP CE's with the
>       same IPv4 address sends fragments to an IPv4 destination host
>       outside the domain, those hosts may use the same IPv4
>       fragmentation identifier, resulting in incorrect reassembly of
>       the fragments at the destination host. Given that the IPv4
>       fragmentation identifier is a 16 bit field, it could be used
>       similarly to port ranges. A MAP CE could rewrite the IPv4
>       fragmentation identifier to be within its allocated port-set,
>       if the resulting fragment identifier space was large enough
>       related to the rate fragments was sent. However, splitting the
>       identifier space in this fashion would increase the
>       probability of reassembly collision for all connections
>       through the CPE. See also <xref target=3D"RFC6864"/></t>
>=20
> the alternatives are that we could say, since the problem of multiple =
CPEs with same IP address sending fragments to same destination required =
coordination that if the fragment id space was say 10 bits, then =
rewrite. or we could go even further and say that the CPE would have to =
throttle traffic to ensure that the id space didn't cycle within the =
reassembly timeout.
> or we could drop the text altogether.
>=20
> my preference would be the above proposed text. it has the problem =
description but it doesn't prescribe a solution.
>=20
> any other opinion?
>=20
> ps: whatever solution we have here should probably also apply to the =
other mechanisms. e.g. =
https://tools.ietf.org/html/draft-ietf-softwire-4rd-09#section-4.6.3
>=20
> cheers,
> Ole
>=20
>=20
>=20
>> On 14 Oct 2014, at 15:32 , Ted Lemon <Ted.Lemon@nominum.com> wrote:
>>=20
>> On Oct 14, 2014, at 5:01 AM, Ole Troan <otroan@employees.org> wrote:
>>> splitting the fragment id space so that there is only a single bit =
per CPE sounds like a corner case that should be disallowed. I don't =
know if we have the knowledge to be able to specify exactly how much of =
the fragment id space is safe to split up though.is it 4, 6, or 8 bits?
>>=20
>> There's a lot to think about here.  The fragment ID translation =
algorithm probably needs to maintain a cache so that it doesn't =
accidentally overload fragment IDs.   The set of all outstanding =
fragments has the potential to be larger than the set of all ports in =
use, so there is definitely reason to be concerned about shrinking the =
fragment ID space.   However, shrinking the fragment ID space _does_ =
serve the useful purpose of isolating fragment ID collisions to the =
nodes that are supposed to be receiving the fragments.
>>=20
>> It may be that the right thing to do is to note that this is a =
problem, make a recommendation, but essentially leave it as future =
research, since we really haven't analyzed the problem in enough depth =
to make an informed recommendation.
>>=20
>>> if changing back to SHOULD from the MUST would lead people to accept =
that we leave the exact recommendations for further study I would be =
happy to do that.
>>=20
>> So yes, this might be a good way to go.
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From nobody Thu Oct 16 04:12:11 2014
Return-Path: <ayourtch@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 458B61AD047 for <softwires@ietfa.amsl.com>; Thu, 16 Oct 2014 04:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YstCOSahVLKz for <softwires@ietfa.amsl.com>; Thu, 16 Oct 2014 04:12:05 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F8801AD010 for <softwires@ietf.org>; Thu, 16 Oct 2014 04:12:05 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id ar1so3064860iec.24 for <softwires@ietf.org>; Thu, 16 Oct 2014 04:12:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=pIW8AGRafvAXeUiZrVsf/myubajFzMg43E9U967EVCc=; b=wz7Kkbtt0LmEiPZzYQ/a16rWxoqFCVzcLN5W2GkvTTAEhsaUbU08ELuaajrOXs3JlK KLw2t6UjPe1qdEUwK6uKKOP7VH0Rf9enK4aAd+K5lT8rRuumghKoMkOpL5yhiVKsNp+A eLyKhZAnx5kLBKfhDEEDis05YJKEsiW5LMGPqrOxHpoJBnrukS2ZzOkdQaBf3P0fn4VY fOfptN+vdH0UJJjctjFGb9AqAwMTObG/wS/GaRqomOAQCpO6TXhc3mAF1UW5JmKLw9kM JsY0a09MC3HkIqtuTiekIRgE60jklLpjFag8MSzCFi7NsHAXkX4WwxL8rhWsQXv2mkJo y9Eg==
MIME-Version: 1.0
X-Received: by 10.107.27.2 with SMTP id b2mr747581iob.70.1413457924644; Thu, 16 Oct 2014 04:12:04 -0700 (PDT)
Received: by 10.107.137.231 with HTTP; Thu, 16 Oct 2014 04:12:04 -0700 (PDT)
In-Reply-To: <25A95528-FA71-48C6-B238-D5D90B99386B@laposte.net>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com> <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org> <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com> <D14390B1-8628-4372-B664-A5EA82BE0327@employees.org> <25A95528-FA71-48C6-B238-D5D90B99386B@laposte.net>
Date: Thu, 16 Oct 2014 13:12:04 +0200
Message-ID: <CAPi140P5FWm7onve7ibHwYC=d3-k1TEnV0LbZmM1jaY+EWwVPg@mail.gmail.com>
From: =?UTF-8?B?QW5kcmV3IPCfkb0gIFlvdXJ0Y2hlbmtv?= <ayourtch@gmail.com>
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/k1pUVnOqwen_Q1RwCLXA2I5ENTE
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 16 Oct 2014 11:12:07 -0000

Hi Remi,

On 10/16/14, R=C3=A9mi Despr=C3=A9s <despres.remi@laposte.net> wrote:
> Hi, Ole,
>
> FWIW, a look at
> https://tools.ietf.org/html/draft-ietf-softwire-4rd-09#section-4.6.3 migh=
t
> be helpful.

This is exactly the problem. You replace the problem of a highly
visited destination (for whom the natural path is to deploy IPv6
anyway and bypass the whole transition mechanism?) having potential
for reassembly errors with a problem of N-fold increased fragment
collision probability on *all* streams, where N is your share ratio,
and which side of this tradeoff is worse is unclear to me - both are
bad in different ways.

Fortunately, since CGNs provide a higher sharing ratio of addresses
(and they can't possibly rewrite the IDs because they do not have a
deterministic algorithm), and are much more widely deployed than any
of the tech we are discussing, we should have already hit this problem
in real life many times over ? Any feedback on this ?

--a

>
> Cheers,
> RD
>
>
> Le 15 oct. 2014 =C3=A0 15:27, Ole Troan <otroan@employees.org> a =C3=A9cr=
it :
>
>> Ted, et al,
>>
>> there are good arguments going both ways, so apologies for my changing
>> opinion here. ;-)
>>
>> we could go with the hand-wavy, there is a problem here, we don't have a
>> good solution:
>>
>>       <t>If two IPv4 host behind two different MAP CE's with the
>>       same IPv4 address sends fragments to an IPv4 destination host
>>       outside the domain, those hosts may use the same IPv4
>>       fragmentation identifier, resulting in incorrect reassembly of
>>       the fragments at the destination host. Given that the IPv4
>>       fragmentation identifier is a 16 bit field, it could be used
>>       similarly to port ranges. A MAP CE could rewrite the IPv4
>>       fragmentation identifier to be within its allocated port-set,
>>       if the resulting fragment identifier space was large enough
>>       related to the rate fragments was sent. However, splitting the
>>       identifier space in this fashion would increase the
>>       probability of reassembly collision for all connections
>>       through the CPE. See also <xref target=3D"RFC6864"/></t>
>>
>> the alternatives are that we could say, since the problem of multiple CP=
Es
>> with same IP address sending fragments to same destination required
>> coordination that if the fragment id space was say 10 bits, then rewrite=
.
>> or we could go even further and say that the CPE would have to throttle
>> traffic to ensure that the id space didn't cycle within the reassembly
>> timeout.
>> or we could drop the text altogether.
>>
>> my preference would be the above proposed text. it has the problem
>> description but it doesn't prescribe a solution.
>>
>> any other opinion?
>>
>> ps: whatever solution we have here should probably also apply to the oth=
er
>> mechanisms. e.g.
>> https://tools.ietf.org/html/draft-ietf-softwire-4rd-09#section-4.6.3
>>
>> cheers,
>> Ole
>>
>>
>>
>>> On 14 Oct 2014, at 15:32 , Ted Lemon <Ted.Lemon@nominum.com> wrote:
>>>
>>> On Oct 14, 2014, at 5:01 AM, Ole Troan <otroan@employees.org> wrote:
>>>> splitting the fragment id space so that there is only a single bit per
>>>> CPE sounds like a corner case that should be disallowed. I don't know =
if
>>>> we have the knowledge to be able to specify exactly how much of the
>>>> fragment id space is safe to split up though.is it 4, 6, or 8 bits?
>>>
>>> There's a lot to think about here.  The fragment ID translation algorit=
hm
>>> probably needs to maintain a cache so that it doesn't accidentally
>>> overload fragment IDs.   The set of all outstanding fragments has the
>>> potential to be larger than the set of all ports in use, so there is
>>> definitely reason to be concerned about shrinking the fragment ID space=
.
>>>  However, shrinking the fragment ID space _does_ serve the useful purpo=
se
>>> of isolating fragment ID collisions to the nodes that are supposed to b=
e
>>> receiving the fragments.
>>>
>>> It may be that the right thing to do is to note that this is a problem,
>>> make a recommendation, but essentially leave it as future research, sin=
ce
>>> we really haven't analyzed the problem in enough depth to make an
>>> informed recommendation.
>>>
>>>> if changing back to SHOULD from the MUST would lead people to accept
>>>> that we leave the exact recommendations for further study I would be
>>>> happy to do that.
>>>
>>> So yes, this might be a good way to go.
>>
>> _______________________________________________
>> 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 nobody Thu Oct 16 05:45:10 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1AC1A1AF8 for <softwires@ietfa.amsl.com>; Thu, 16 Oct 2014 05:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AyjXSuOxtudA for <softwires@ietfa.amsl.com>; Thu, 16 Oct 2014 05:45:05 -0700 (PDT)
Received: from sjc1-mx02.nominum.com (whiskey.nominum.com [64.89.234.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605161A1AE1 for <softwires@ietf.org>; Thu, 16 Oct 2014 05:45:05 -0700 (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 Certificate Authority - G2" (verified OK)) by sjc1-mx02.nominum.com (Postfix) with ESMTPS id D4842DA0040 for <softwires@ietf.org>; Thu, 16 Oct 2014 12:46:59 +0000 (UTC)
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 ESMTP id 160F353E076; Thu, 16 Oct 2014 05:44:35 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 16 Oct 2014 05:44:34 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <D14390B1-8628-4372-B664-A5EA82BE0327@employees.org>
Date: Thu, 16 Oct 2014 07:44:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <7324540B-8A35-42C6-874E-7AE8A6EE3276@nominum.com>
References: <CAPi140MdbJQBLSRS+g4Jx0G1zm1dx6PLBBQ7oPeALU2z-Vp81g@mail.gmail.com> <A9F4CC49-3409-482E-8DD1-D60770719370@employees.org> <365F683D-89D6-4A42-B9F1-780453D9C1A5@nominum.com> <D14390B1-8628-4372-B664-A5EA82BE0327@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/znWUQzsZW1ifh7a_6UnoXlpMWU4
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] MAP draft 11 question on fragment ID space reduction
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 16 Oct 2014 12:45:06 -0000

On Oct 15, 2014, at 8:27 AM, Ole Troan <otroan@employees.org> wrote:
> my preference would be the above proposed text. it has the problem =
description but it doesn't prescribe a solution.

WFM.


From nobody Sun Oct 19 23:24:09 2014
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE2C01A1BD7; Sun, 19 Oct 2014 23:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.9
X-Spam-Level: *
X-Spam-Status: No, score=1.9 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_21=0.6, J_CHICKENPOX_31=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fPi4XQdD4lsV; Sun, 19 Oct 2014 23:20:00 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A409C1A6FA6; Sun, 19 Oct 2014 23:20:00 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id kx10so4482091pab.23 for <multiple recipients>; Sun, 19 Oct 2014 23:20:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sAmowGo3eR1gT4JkzAbdf7r2+GQGF2rs/l26UAJuNnQ=; b=reyu+yo2oapV2UD9326rqXaZ1yGLnV2GCzqs8J4EjM3XQMR7cDDsLsK254//O2J+4E H2ZhlyijUlgtTLsGd83uF0lSnML1V523qdT+Yo2kankNg9O+BlsA4ZPnX3Le6n6Z0OKo LMQJ+8T8bZTvnBmIHuSY6YshZxXuvk80O/veyvVm9bY6bOXAzOafyGe6Gt1cweT8KigW Jb469l9Q0JPjUk4ZmR8FI/38IcN5neHtGwNlLnVlOH9cSy6tI21KK9I6+uXL7I5iATj3 giLpEIMfVX7WF+bTIfrObXj1rLtGQXR4T4cv4v2sL2yLdQgze7RdED5H9a6Wr/u1eT2g R6gw==
X-Received: by 10.70.129.144 with SMTP id nw16mr25553337pdb.2.1413786000325; Sun, 19 Oct 2014 23:20:00 -0700 (PDT)
Received: from [192.168.11.102] ([166.111.131.15]) by mx.google.com with ESMTPSA id fz1sm1323285pbb.80.2014.10.19.23.19.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Oct 2014 23:19:59 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com>
Date: Mon, 20 Oct 2014 14:19:48 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F384A7F-E2EC-4DEF-A5B7-6A8D65C921E5@gmail.com>
References: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com> <D0646F50.DDFC8%ian.farrer@telekom.de> <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/sV1nvdSp1oC0m5Z99WwwtgWQuHY
X-Mailman-Approved-At: Sun, 19 Oct 2014 23:24:07 -0700
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, sunqiong <sunqiong@ctbri.com.cn>, "softwires@ietf.org" <softwires@ietf.org>, "tena@huawei.com" <tena@huawei.com>
Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 20 Oct 2014 06:20:09 -0000

Dear David,=20

The comments and updates do help to get lw4o6 specification clearer. =
Thanks!=20

But I have some thoughts about the following (minor) issue:

>>> Minor issues (7):
>>>=20
>>> [3] The lack of discussion of management information is an
>>> omission.  See A.2.2 below in the OPS-Dir review section of this =
email
>>> and the discussion in Section 3.2 of RFC 5706.  A sentence pointing
>>> at an applicable MIB and/or YANG draft or drafts would suffice.
>>=20
>> [if] There is a draft for a softwire YANG model which is due to be
>> published shortly. We'll add an informative reference to this.

I=92m feeling it=92s not necessary for such a specification to reference =
the YANG model document. The current lw4o6 specification does work =
without this management YANG model doc. I think the OA&M should be out =
of the scope for this protocol specification. And, I checked the =
RFC6333, where no such pointer exists.=20

Is such a reference required by the OPS-Dir review?=20

Thanks,=20
Qi

On Oct 16, 2014, at 4:27 AM, Black, David <david.black@emc.com> wrote:

> Hi Ian,
>=20
> Many thanks for the comprehensive response - I've extracted [1], [2]
> and [7] for further attention here - your proposals for all of the
> other items and nits are fine with me.
>=20
> I think the only open topic is [7], and I can live w/your proposed
> rephrasing for that even though I'd like to see a sentence of
> rationale added.
>=20
>>> [1] There are a number of places where SHOULD is used to refer to
>>> requirements in another RFC, e.g., the following text in section =
5.1:
>=20
> [... snip ...]
>=20
>> [if] OK with the above proposals.
>=20
> I supplied new text for 5.1 - please also make the corresponding =
changes
> in 5.2.1 (twice) and 8.2, plus check whether this "SHOULD" problem
> occurs elsewhere.
>=20
>>> [2] Section 4.  Lightweight 4over6 Architecture
>>>=20
>>>  The consequence of this architecture is that the information
>>>  maintained by the provisioning mechanism and the one maintained by
>>>  the lwAFTR MUST be synchronized (See figure 2).  The details of =
this
>>>  synchronization depend on the exact provisioning mechanism and will
>>>  be discussed in a companion document.
>>>=20
>>> I believe that this "companion document" needs to be cited as a
>>> normative reference.  The above text's vague allusion to the =
specification
>>> of how to implement a "MUST" requirement is insufficient.
>>=20
>> [if] The synch mechanism is really down to how an operator has =
deployed
>> the service, the specific provisioning protocols in use etc. What =
about
>> the following wording change?:
>>=20
>> The consequence of this architecture is that the information =
maintained by
>> the provisioning mechanism and the one maintained by the lwAFTR MUST =
be
>> synchronized (See figure 2).  The details of this synchronization =
depend
>> on the exact provisioning mechanism and protocols that are in use by =
the
>> operator. If no automated process for this synchronisation is in use, =
then
>> information in the provisioning systems and the lwAFTR MUST be
>> synchronised manually, e.g. by copying aligned configuration files to =
each
>> of the elements.
>=20
> That wording change is fine, and I prefer it to Ted's subsequent =
suggestion
> of shorter "out of scope" language.
>=20
> My primary concern was the reference to a "companion document" which =
lead
> to an obvious "where is that???" question.  The new wording removes =
that
> reference and provides some useful information on how the required
> synchronization could be accomplished.
>=20
>>> [7] Also in Section 5.1
>>>=20
>>>  Unless an lwB4 is being allocated a full IPv4 address, it is
>>>  RECOMMENDED that PSIDs containing the well-known ports (0-1023) are
>>>  not allocated to lwB4s.
>>>=20
>>> Please explain why.  Also, "well-known ports" is not the right term;
>>> I believe those are the "system ports", e.g., see:
>>>=20
>>> =
http://www.iana.org/assignments/service-names-port-numbers/service-names-p=

>>> ort-numbers.xhtml
>>=20
>> [if] Reworded:
>>=20
>> Unless an lwB4 is being allocated a full IPv4 address, it is
>>   RECOMMENDED that PSIDs containing the system ports (0-1023) are
>>   not allocated to lwB4s.
>=20
> Why?  Please add a sentence to explain, although I'll be ok if all =
that
> is done is the rewording.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: ian.farrer@telekom.de [mailto:ian.farrer@telekom.de]
>> Sent: Wednesday, October 15, 2014 1:06 PM
>> To: Black, David; yong@csnet1.cs.tsinghua.edu.cn; =
sunqiong@ctbri.com.cn;
>> mohamed.boucadair@orange.com; tena@huawei.com; =
yiu_lee@cable.comcast.com; gen-
>> art@ietf.org; ops-dir@ietf.org
>> Cc: ietf@ietf.org; softwires@ietf.org
>> Subject: Re: Gen-ART and OPS-Dir review of =
draft-ietf-softwire-lw4over6-10
>>=20
>> Hi David,
>>=20
>> Many thanks for the review. Please see comments inline.
>>=20
>> Cheers,
>> Ian
>>=20
>>=20
>>=20
>> On 12/10/2014 00:30, "Black, David" <david.black@emc.com> wrote:
>>=20
>>> This is a combined Gen-ART and OPS-DIR review.  Boilerplate for both
>>> follows,
>>> and I apologize for it being a day late - United Airlines got me =
back to
>>> Boston after midnight last night on a plane w/o working WiFi.
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at:
>>>=20
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>=20
>>> Please resolve these comments along with any other Last Call =
comments you may receive.
>>>=20
>>> I have reviewed this document as part of the Operational =
directorate's ongoing
>>> effort to review all IETF documents being processed by the IESG.  =
These comments
>>> were written primarily for the benefit of the operational area =
directors.
>>> Document editors and WG chairs should treat these comments just like =
any other
>>> last call comments.
>>>=20
>>> Document: draft-ietf-softwire-lw4over6-10
>>> Reviewer: David Black
>>> Review Date: October 10, 2014
>>> IETF LC End Date: October 10, 2014
>>> IESG Telechat date: October 16, 2014
>>>=20
>>> Summary: This draft is on the right track, but has open issues
>>> 		described in the review.
>>>=20
>>> This draft describes an extension to Dual-Stack Lite that relocates =
the NAPT
>>> functionality from the centralized tunnel concentrator to the =
DS-Lite client
>>> - doing so has significant scalability benefits.  The draft is =
generally
>>> readable although understanding why some of the processing needs to =
be done
>>> in the manner specified requires strong familiarity with both =
DS-Lite and NAPT.
>>>=20
>>> The draft is generally in good shape - I found three issues that I =
consider
>>> to be significant, the most important of which are sloppiness in use =
of
>>> RFC 2119 keywords, particularly in Section 5.1, and omission of what
>>> appears to be a necessary normative reference.
>>>=20
>>> Major issues (2):
>>>=20
>>> [1] There are a number of places where SHOULD is used to refer to =
requirement
>>> in another RFC, e.g., the following text in section 5.1:
>>>=20
>>>  The DNS considerations described in Section 5.5 and Section 6.4 of
>>>  [RFC6333] SHOULD be followed.
>>>=20
>>> This has the side effect of weakening any MUST requirement in the =
referenced
>>> RFC(s) to a SHOULD, which was probably not intended, and needs to be =
explicitly
>>> stated if it was intended.  Here's a possible rephrasing:
>>>=20
>>>  The DNS considerations described in Section 5.5 and Section 6.4 of
>>>  [RFC6333] apply to Lightweight 4over6; lw4o6 implementations MUST
>>>  comply with all requirements stated there.
>>>=20
>>> The additional places where this occurs are:
>>>=20
>>> - Section 5.2.1 (twice):
>>>=20
>>>  For TCP and UDP traffic the NAPT44 implemented in the lwB4 SHOULD
>>>  conform with the behaviour and best current practices documented in
>>>  [RFC4787], [RFC5508], and [RFC5382].  If the lwB4 supports DCCP, =
then
>>>  the requirements in [RFC5597] SHOULD be implemented.
>>>=20
>>> - Section 8.2:
>>>=20
>>>  The lwB4 SHOULD implement the requirements defined in [RFC5508] for
>>>  ICMP forwarding.
>>=20
>> [if] OK with the above proposals.
>>=20
>>=20
>>>=20
>>> [2] Section 4.  Lightweight 4over6 Architecture
>>>=20
>>>  The consequence of this architecture is that the information
>>>  maintained by the provisioning mechanism and the one maintained by
>>>  the lwAFTR MUST be synchronized (See figure 2).  The details of =
this
>>>  synchronization depend on the exact provisioning mechanism and will
>>>  be discussed in a companion document.
>>>=20
>>> I believe that this "companion document" needs to be cited as a
>>> normative reference.  The above text's vague allusion to the =
specification
>>> of how to implement a "MUST" requirement is insufficient.
>>=20
>> [if] The synch mechanism is really down to how an operator has =
deployed
>> the service, the specific provisioning protocols in use etc. What =
about
>> the following wording change?:
>>=20
>> The consequence of this architecture is that the information =
maintained by
>> the provisioning mechanism and the one maintained by the lwAFTR MUST =
be
>> synchronized (See figure 2).  The details of this synchronization =
depend
>> on the exact provisioning mechanism and protocols that are in use by =
the
>> operator. If no automated process for this synchronisation is in use, =
then
>> information in the provisioning systems and the lwAFTR MUST be
>> synchronised manually, e.g. by copying aligned configuration files to =
each
>> of the elements.
>>=20
>>=20
>>>=20
>>> Minor issues (7):
>>>=20
>>> [3] The lack of discussion of management information is an
>>> omission.  See A.2.2 below in the OPS-Dir review section of this =
email
>>> and the discussion in Section 3.2 of RFC 5706.  A sentence pointing
>>> at an applicable MIB and/or YANG draft or drafts would suffice.
>>=20
>> [if] There is a draft for a softwire YANG model which is due to be
>> published shortly. We'll add an informative reference to this.
>>=20
>>>=20
>>> [4] Section 4.  Lightweight 4over6 Architecture
>>>=20
>>>  The solution specified in this document allows the assignment of
>>>  either a full or a shared IPv4 address requesting CPEs.  [RFC7040]
>>>  provides a mechanism for assigning a full IPv4 address only.
>>>=20
>>> Please explain what entities would share the IPv4 address.  For =
example,
>>> this is needed as a foundation for the statement in Section 8 that
>>> "ICMPv4 does not work in an address sharing environment without
>>> special handling [RFC6269]."
>>=20
>> [if] OK. Reworded version:
>>=20
>> The solution specified in this document allows the assignment of
>>   either a full IPv4 address for a CPE, or a single IPv4 address =
which is
>> shared between multiple CPEs.  [RFC7040]
>>   provides a mechanism for assigning a full IPv4 address only.
>>=20
>>=20
>>>=20
>>> [5] Section 5.1.  Lightweight B4 Provisioning with DHCPv6
>>>=20
>>>  For DHCPv6 based configuration of these parameters, the lwB4 SHOULD
>>>  implement OPTION_S46_CONT_LW
>>>=20
>>> What are the consequences of not doing that?  The could be addressed
>>> by changing that "SHOULD" to a "MUST", although I suspect that =
what's
>>> wanted here is a forward reference to the alternatives discussed in
>>> Section 7.
>>=20
>> [if] Rewording with:
>>=20
>> To configure these parameters using DHCPv6, the lwB4 MUST implement
>> OPTION_S46_CONT_LW.
>>=20
>>=20
>>>=20
>>> [6] Also in Section 5.1
>>>=20
>>>  If stateful IPv4 configuration or additional IPv4 configuration
>>>  information is required, DHCPv4 [RFC2131] must be used.
>>>=20
>>> "must" -> "MUST"
>>>=20
>>>  In the event that the lwB4's encapsulation source address is =
changed
>>>  for any reason (such as the DHCPv6 lease expiring), the lwB4's
>>>  dynamic provisioning process must be re-initiated.
>>>=20
>>> "must" -> "MUST"
>>=20
>> [if] OK
>>=20
>>>=20
>>> [7] Also in Section 5.1
>>>=20
>>>  Unless an lwB4 is being allocated a full IPv4 address, it is
>>>  RECOMMENDED that PSIDs containing the well-known ports (0-1023) are
>>>  not allocated to lwB4s.
>>>=20
>>> Please explain why.  Also, "well-known ports" is not the right term;
>>> I believe those are the "system ports", e.g., see:
>>>=20
>>> =
http://www.iana.org/assignments/service-names-port-numbers/service-names-p=

>>> ort-numbers.xhtml
>>=20
>> [if] Reworded:
>>=20
>> Unless an lwB4 is being allocated a full IPv4 address, it is
>>   RECOMMENDED that PSIDs containing the system ports (0-1023) are
>>   not allocated to lwB4s.
>>=20
>>=20
>>>=20
>>>=20
>>> [8] Still in Section 5.1
>>>=20
>>>  In the event that the lwB4 receives an ICMPv6 error message (type =
1,
>>>  code 5) originating from the lwAFTR, the lwB4 SHOULD interpret this
>>>  to mean that no matching entry in the lwAFTR's binding table has =
been
>>>  found.  The lwB4 MAY then re-initiate the dynamic port-restricted
>>>  provisioning process.  The lwB4's re-initiation policy SHOULD be
>>>  configurable.
>>>=20
>>> What happens if the lwB4 ignores the first "SHOULD"?
>>=20
>>=20
>> [if] Reword:
>> ...the lwB4 interprets this to mean that no matching entry in the =
lwAFTR's
>> binding table has been found, so the IPv4 payload is not being =
forwarded
>> by the lwAFTR.
>>=20
>>=20
>>=20
>>>=20
>>> [9] Section 8.1.  ICMPv4 Processing by the lwAFTR
>>>=20
>>> This describes two approaches to ICMPv4 processing.  Are there any =
others?
>>> If so, please add some text about them, otherwise, I suggest this =
change:
>>>=20
>>> OLD
>>>  Additionally, the lwAFTR MAY implement:
>>>=20
>>>  o  Discarding of all inbound ICMP messages.
>>> NEW
>>>  Otherwise the lwAFTR MUST discard all inbound ICMPv4 messages.
>>=20
>> [if] OK
>>=20
>>>=20
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> -- Section 1.  Introduction
>>>=20
>>>  Basic Bridging BroadBand element: A B4 element is a function
>>>                                    implemented on a dual-stack =
capable
>>>                                    node, either a directly connected
>>>                                    device or a CPE, that creates a
>>>                                    tunnel to an AFTR.
>>>=20
>>> I suggest changing "a tunnel to an AFTR" to "an IPv4-in-IPv6 tunnel
>>> to an AFTR" for consistency with the AFTR definition.
>>=20
>> [if] OK
>>=20
>>>=20
>>> -- Section 5.2.  Lightweight B4 Data Plane Behavior
>>>=20
>>>  Internally connected hosts source IPv4 packets with an [RFC1918]
>>>  address.
>>=20
>> [if] Reword with:
>>=20
>> Hosts connected to the customer's network behind the lwB4 source IPv4
>> packets with an [RFC1918] address.
>>=20
>>=20
>>>=20
>>> Internal to what?  Please explain.
>>>=20
>>> -- Section 6.2.  lwAFTR Data Plane Behavior
>>>=20
>>>  The lwAFTR MUST support hairpinning of traffic between two lwB4s, =
by
>>>  performing de-capsulation and re-encapsulation of packets.  The
>>>  hairpinning policy MUST be configurable.
>>>=20
>>> Please explain "hairpinning" - it should suffice to add "from one =
lwB4
>>> that need to be sent to another lwB4 associated with the same AFTR"
>>> after "de-capsulation and re-encapsulation of packets".
>>=20
>> [if] OK with the suggested wording.
>>=20
>>>=20
>>> -- Section 7.  Additional IPv4 address and Port Set Provisioning
>>> Mechanisms
>>>=20
>>>  In a Lightweight 4over6 domain, the binding information MUST be
>>>  aligned between the lwB4s, the lwAFTRs and the provisioning server.
>>>=20
>>> "aligned between" -> "synchronized across" for consistency with use
>>> of forms of "synchronize" elsewhere in this draft.
>>=20
>> [if] OK
>>=20
>>>=20
>>> idnits found a few things to complain about:
>>>=20
>>> - The use of "the well-known range 192.0.0.0/29" in Section 5.1.  =
This is
>>> ok,
>>> 	as it's describing DS-Lite use of that range that is documented
>>> 	elsewhere.  If lw4o6 is using that range, an explanation ought =
to be
>>> 	added to Section 5.1.
>>=20
>> [if] lw4o6 doesn=B9t use these
>>=20
>>>=20
>>> - Three references have been updated:
>>>=20
>>> =3D=3D Outdated reference: A later version (-09) exists of
>>>    draft-ietf-softwire-map-dhcp-07
>>>=20
>>> =3D=3D Outdated reference: draft-ietf-dhc-dhcpv4-over-dhcpv6 has =
been
>>> published
>>>    as RFC 7341
>>>=20
>>> =3D=3D Outdated reference: A later version (-06) exists of
>>>    draft-ietf-pcp-port-set-05
>>=20
>> [if] All should now be fixed in v11 (posted earlier today)
>>=20
>>>=20
>>> --- Selected RFC 5706 Appendix A Q&A for OPS-Dir review ---
>>>=20
>>> A.1.1.  Has deployment been discussed?
>>>=20
>>> 	Yes, this protocol is intended to improve scalability over the =
existing
>>> 	DS-Lite mechanism.
>>>=20
>>> A.1.2.  Has installation and initial setup been discussed?
>>>=20
>>> 	No, there are vague references to a provisioning mechanism and
>>> 	synchronization functionality that need to be set up.  See
>>> 	major open issue [2] above which calls out a missing normative
>>> 	reference that should address these topics.
>>>=20
>>> A.1.3.  Has the migration path been discussed?
>>>=20
>>> 	No, but I suspect that this concern is inapplicable, as I think
>>> 	a carrier would not migrate from DS-Lite to lw4o6, but would
>>> 	deploy lw4o6 instead of DS-Lite.
>>>=20
>>> A.1.4.  Have the Requirements on other protocols and functional
>>>      components been discussed?
>>>=20
>>> 	Yes, but major open issue [1] is effectively in this area.
>>>=20
>>> A.1.6.  Have suggestions for verifying correct operation been =
discussed?
>>>=20
>>> 	No, and they probably should be, as this protocol requires state
>>> 	synchronization among the lwB4, lwAFTR and the provisioning =
system,
>>> 	and is likely to exhibit problematic behavior if the relevant =
state
>>> 	information gets out of sync.
>>>=20
>>> A.1.9.  Is configuration discussed?
>>>=20
>>> 	Yes, the draft does a good job of discussing what needs to be
>>> 	configured to set up the protocol (aside from state =
synchronization)
>>> 	and calling out protocol behavior aspects that should be =
configurable.
>>>=20
>>> A.2 Management
>>>=20
>>> 	This is really not discussed, and in particular the lack of =
discussion
>>> 	of management information is notable because this protocol has a
>>> 	different operational structure than DS-Lite.  So, specifically:
>>>=20
>>> A.2.2.  Is management information discussed?
>>>=20
>>> 	No, this is minor open issue [3].  A sentence pointing to =
applicable
>>> 	MIB and/or YANG draft(s) would suffice to address this.
>>>=20
>>> A.2.4.  Is configuration management discussed?
>>>=20
>>> 	Yes - the discussion is ok, even though specific configuration =
mechanisms
>>> 	are not discussed.
>>>=20
>>> A.3.  Documentation
>>>=20
>>> 	The protocol does have significant operational impacts on the =
Internet.
>>>=20
>>> 	The shepherd's writeup indicates that multiple implementations =
exist
>>> 	among which interoperability has been tested.
>>>=20
>>> Thanks,
>>> --David
>>> ----------------------------------------------------
>>> David L. Black, Distinguished Engineer
>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>> ----------------------------------------------------
>>>=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From nobody Mon Oct 20 06:59:58 2014
Return-Path: <david.black@emc.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 300C41A8764; Mon, 20 Oct 2014 06:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.111
X-Spam-Level: 
X-Spam-Status: No, score=-3.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_21=0.6, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOAYFn5qWl1Y; Mon, 20 Oct 2014 06:45:56 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D513A1A6FE3; Mon, 20 Oct 2014 06:45:23 -0700 (PDT)
Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9KDhxfF013694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Oct 2014 09:44:02 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com s9KDhxfF013694
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1413812646; bh=57TDj/g/9RB2OKbiA5kN7liiIhk=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=XOflClMsF2u1f7vXrTcTAz0zjNjkW23bpFdHalkgwjQHHhfdxR+ceO6XS2rWg0NZn C9tZIE9BXo9K2aJLqvn+FufjZemCN2wEgK0kzpS1tPoW0NHaae2TZIufL6VOZ9Mxlp 8MBGEVdUU0GzWCtRCHSaH4j4QVPazLg70eJmmXUM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com s9KDhxfF013694
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd54.lss.emc.com (RSA Interceptor); Mon, 20 Oct 2014 09:43:37 -0400
Received: from mxhub35.corp.emc.com (mxhub35.corp.emc.com [10.254.93.83]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9KDhh0k022506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Oct 2014 09:43:44 -0400
Received: from MXHUB101.corp.emc.com (10.253.50.15) by mxhub35.corp.emc.com (10.254.93.83) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 20 Oct 2014 09:43:44 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB101.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Mon, 20 Oct 2014 09:43:44 -0400
From: "Black, David" <david.black@emc.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Thread-Topic: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
Thread-Index: Ac/lou8B9zKSJooyTsOMrMdwtE6r4ADGPF8AAAg3UhAA3KikAAAGt0vg
Date: Mon, 20 Oct 2014 13:43:42 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493605F25B@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com> <D0646F50.DDFC8%ian.farrer@telekom.de> <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com> <1F384A7F-E2EC-4DEF-A5B7-6A8D65C921E5@gmail.com>
In-Reply-To: <1F384A7F-E2EC-4DEF-A5B7-6A8D65C921E5@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.106]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: DLM_1, public, GIS Solicitation
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/FIP2hPvbAsW6u0vi08xNWqXyuSw
X-Mailman-Approved-At: Mon, 20 Oct 2014 06:59:49 -0700
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, sunqiong <sunqiong@ctbri.com.cn>, "softwires@ietf.org" <softwires@ietf.org>, "Black, David" <david.black@emc.com>, "tena@huawei.com" <tena@huawei.com>
Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 20 Oct 2014 13:46:02 -0000

Hello Qi,

> I'm feeling it's not necessary for such a specification to reference the =
YANG
> model document. The current lw4o6 specification does work without this
> management YANG model doc. I think the OA&M should be out of the scope fo=
r
> this protocol specification. And, I checked the RFC6333, where no such po=
inter
> exists.

Well, the lw4o6 specification results in significant operational change fro=
m the
current DS-Lite, so that does raise the question of how to manage lw4o6.

That said, I characterized this as a minor issue, and regard such a referen=
ce
as helpful, but not essential.  I'm suggesting an informative reference, no=
t
normative - a sentence observing that the YANG model exists would suffice
(I see no need for a "MUST" or "SHOULD" requirement for YANG in this draft)=
.

> Is such a reference required by the OPS-Dir review?

Whether adding an informative mention of the YANG model rises to the level =
of
"required" would be up to the OPS ADs.  It may help implementers find the Y=
ANG
model, which could be useful.

Thanks,
--David

> -----Original Message-----
> From: Qi Sun [mailto:sunqi.csnet.thu@gmail.com]
> Sent: Monday, October 20, 2014 2:20 AM
> To: Black, David
> Cc: ian.farrer@telekom.de; yong@csnet1.cs.tsinghua.edu.cn; sunqiong;
> mohamed.boucadair@orange.com; tena@huawei.com; Yiu Lee; gen-art@ietf.org;=
 ops-
> dir@ietf.org; softwires@ietf.org; ietf@ietf.org
> Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwir=
e-
> lw4over6-10
>=20
> Dear David,
>=20
> The comments and updates do help to get lw4o6 specification clearer. Than=
ks!
>=20
> But I have some thoughts about the following (minor) issue:
>=20
> >>> Minor issues (7):
> >>>
> >>> [3] The lack of discussion of management information is an
> >>> omission.  See A.2.2 below in the OPS-Dir review section of this emai=
l
> >>> and the discussion in Section 3.2 of RFC 5706.  A sentence pointing
> >>> at an applicable MIB and/or YANG draft or drafts would suffice.
> >>
> >> [if] There is a draft for a softwire YANG model which is due to be
> >> published shortly. We'll add an informative reference to this.
>=20
> I'm feeling it's not necessary for such a specification to reference the =
YANG
> model document. The current lw4o6 specification does work without this
> management YANG model doc. I think the OA&M should be out of the scope fo=
r
> this protocol specification. And, I checked the RFC6333, where no such po=
inter
> exists.
>=20
> Is such a reference required by the OPS-Dir review?
>=20
> Thanks,
> Qi
>=20
> On Oct 16, 2014, at 4:27 AM, Black, David <david.black@emc.com> wrote:
>=20
> > Hi Ian,
> >
> > Many thanks for the comprehensive response - I've extracted [1], [2]
> > and [7] for further attention here - your proposals for all of the
> > other items and nits are fine with me.
> >
> > I think the only open topic is [7], and I can live w/your proposed
> > rephrasing for that even though I'd like to see a sentence of
> > rationale added.
> >
> >>> [1] There are a number of places where SHOULD is used to refer to
> >>> requirements in another RFC, e.g., the following text in section 5.1:
> >
> > [... snip ...]
> >
> >> [if] OK with the above proposals.
> >
> > I supplied new text for 5.1 - please also make the corresponding change=
s
> > in 5.2.1 (twice) and 8.2, plus check whether this "SHOULD" problem
> > occurs elsewhere.
> >
> >>> [2] Section 4.  Lightweight 4over6 Architecture
> >>>
> >>>  The consequence of this architecture is that the information
> >>>  maintained by the provisioning mechanism and the one maintained by
> >>>  the lwAFTR MUST be synchronized (See figure 2).  The details of this
> >>>  synchronization depend on the exact provisioning mechanism and will
> >>>  be discussed in a companion document.
> >>>
> >>> I believe that this "companion document" needs to be cited as a
> >>> normative reference.  The above text's vague allusion to the specific=
ation
> >>> of how to implement a "MUST" requirement is insufficient.
> >>
> >> [if] The synch mechanism is really down to how an operator has deploye=
d
> >> the service, the specific provisioning protocols in use etc. What abou=
t
> >> the following wording change?:
> >>
> >> The consequence of this architecture is that the information maintaine=
d by
> >> the provisioning mechanism and the one maintained by the lwAFTR MUST b=
e
> >> synchronized (See figure 2).  The details of this synchronization depe=
nd
> >> on the exact provisioning mechanism and protocols that are in use by t=
he
> >> operator. If no automated process for this synchronisation is in use, =
then
> >> information in the provisioning systems and the lwAFTR MUST be
> >> synchronised manually, e.g. by copying aligned configuration files to =
each
> >> of the elements.
> >
> > That wording change is fine, and I prefer it to Ted's subsequent sugges=
tion
> > of shorter "out of scope" language.
> >
> > My primary concern was the reference to a "companion document" which le=
ad
> > to an obvious "where is that???" question.  The new wording removes tha=
t
> > reference and provides some useful information on how the required
> > synchronization could be accomplished.
> >
> >>> [7] Also in Section 5.1
> >>>
> >>>  Unless an lwB4 is being allocated a full IPv4 address, it is
> >>>  RECOMMENDED that PSIDs containing the well-known ports (0-1023) are
> >>>  not allocated to lwB4s.
> >>>
> >>> Please explain why.  Also, "well-known ports" is not the right term;
> >>> I believe those are the "system ports", e.g., see:
> >>>
> >>> http://www.iana.org/assignments/service-names-port-numbers/service-na=
mes-p
> >>> ort-numbers.xhtml
> >>
> >> [if] Reworded:
> >>
> >> Unless an lwB4 is being allocated a full IPv4 address, it is
> >>   RECOMMENDED that PSIDs containing the system ports (0-1023) are
> >>   not allocated to lwB4s.
> >
> > Why?  Please add a sentence to explain, although I'll be ok if all that
> > is done is the rewording.
> >
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: ian.farrer@telekom.de [mailto:ian.farrer@telekom.de]
> >> Sent: Wednesday, October 15, 2014 1:06 PM
> >> To: Black, David; yong@csnet1.cs.tsinghua.edu.cn; sunqiong@ctbri.com.c=
n;
> >> mohamed.boucadair@orange.com; tena@huawei.com; yiu_lee@cable.comcast.c=
om;
> gen-
> >> art@ietf.org; ops-dir@ietf.org
> >> Cc: ietf@ietf.org; softwires@ietf.org
> >> Subject: Re: Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over=
6-10
> >>
> >> Hi David,
> >>
> >> Many thanks for the review. Please see comments inline.
> >>
> >> Cheers,
> >> Ian
> >>
> >>
> >>
> >> On 12/10/2014 00:30, "Black, David" <david.black@emc.com> wrote:
> >>
> >>> This is a combined Gen-ART and OPS-DIR review.  Boilerplate for both
> >>> follows,
> >>> and I apologize for it being a day late - United Airlines got me back=
 to
> >>> Boston after midnight last night on a plane w/o working WiFi.
> >>>
> >>> I am the assigned Gen-ART reviewer for this draft. For background on
> >>> Gen-ART, please see the FAQ at:
> >>>
> >>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >>>
> >>> Please resolve these comments along with any other Last Call comments=
 you
> may receive.
> >>>
> >>> I have reviewed this document as part of the Operational directorate'=
s
> ongoing
> >>> effort to review all IETF documents being processed by the IESG.  The=
se
> comments
> >>> were written primarily for the benefit of the operational area direct=
ors.
> >>> Document editors and WG chairs should treat these comments just like =
any
> other
> >>> last call comments.
> >>>
> >>> Document: draft-ietf-softwire-lw4over6-10
> >>> Reviewer: David Black
> >>> Review Date: October 10, 2014
> >>> IETF LC End Date: October 10, 2014
> >>> IESG Telechat date: October 16, 2014
> >>>
> >>> Summary: This draft is on the right track, but has open issues
> >>> 		described in the review.
> >>>
> >>> This draft describes an extension to Dual-Stack Lite that relocates t=
he
> NAPT
> >>> functionality from the centralized tunnel concentrator to the DS-Lite
> client
> >>> - doing so has significant scalability benefits.  The draft is genera=
lly
> >>> readable although understanding why some of the processing needs to b=
e
> done
> >>> in the manner specified requires strong familiarity with both DS-Lite=
 and
> NAPT.
> >>>
> >>> The draft is generally in good shape - I found three issues that I
> consider
> >>> to be significant, the most important of which are sloppiness in use =
of
> >>> RFC 2119 keywords, particularly in Section 5.1, and omission of what
> >>> appears to be a necessary normative reference.
> >>>
> >>> Major issues (2):
> >>>
> >>> [1] There are a number of places where SHOULD is used to refer to
> requirement
> >>> in another RFC, e.g., the following text in section 5.1:
> >>>
> >>>  The DNS considerations described in Section 5.5 and Section 6.4 of
> >>>  [RFC6333] SHOULD be followed.
> >>>
> >>> This has the side effect of weakening any MUST requirement in the
> referenced
> >>> RFC(s) to a SHOULD, which was probably not intended, and needs to be
> explicitly
> >>> stated if it was intended.  Here's a possible rephrasing:
> >>>
> >>>  The DNS considerations described in Section 5.5 and Section 6.4 of
> >>>  [RFC6333] apply to Lightweight 4over6; lw4o6 implementations MUST
> >>>  comply with all requirements stated there.
> >>>
> >>> The additional places where this occurs are:
> >>>
> >>> - Section 5.2.1 (twice):
> >>>
> >>>  For TCP and UDP traffic the NAPT44 implemented in the lwB4 SHOULD
> >>>  conform with the behaviour and best current practices documented in
> >>>  [RFC4787], [RFC5508], and [RFC5382].  If the lwB4 supports DCCP, the=
n
> >>>  the requirements in [RFC5597] SHOULD be implemented.
> >>>
> >>> - Section 8.2:
> >>>
> >>>  The lwB4 SHOULD implement the requirements defined in [RFC5508] for
> >>>  ICMP forwarding.
> >>
> >> [if] OK with the above proposals.
> >>
> >>
> >>>
> >>> [2] Section 4.  Lightweight 4over6 Architecture
> >>>
> >>>  The consequence of this architecture is that the information
> >>>  maintained by the provisioning mechanism and the one maintained by
> >>>  the lwAFTR MUST be synchronized (See figure 2).  The details of this
> >>>  synchronization depend on the exact provisioning mechanism and will
> >>>  be discussed in a companion document.
> >>>
> >>> I believe that this "companion document" needs to be cited as a
> >>> normative reference.  The above text's vague allusion to the specific=
ation
> >>> of how to implement a "MUST" requirement is insufficient.
> >>
> >> [if] The synch mechanism is really down to how an operator has deploye=
d
> >> the service, the specific provisioning protocols in use etc. What abou=
t
> >> the following wording change?:
> >>
> >> The consequence of this architecture is that the information maintaine=
d by
> >> the provisioning mechanism and the one maintained by the lwAFTR MUST b=
e
> >> synchronized (See figure 2).  The details of this synchronization depe=
nd
> >> on the exact provisioning mechanism and protocols that are in use by t=
he
> >> operator. If no automated process for this synchronisation is in use, =
then
> >> information in the provisioning systems and the lwAFTR MUST be
> >> synchronised manually, e.g. by copying aligned configuration files to =
each
> >> of the elements.
> >>
> >>
> >>>
> >>> Minor issues (7):
> >>>
> >>> [3] The lack of discussion of management information is an
> >>> omission.  See A.2.2 below in the OPS-Dir review section of this emai=
l
> >>> and the discussion in Section 3.2 of RFC 5706.  A sentence pointing
> >>> at an applicable MIB and/or YANG draft or drafts would suffice.
> >>
> >> [if] There is a draft for a softwire YANG model which is due to be
> >> published shortly. We'll add an informative reference to this.
> >>
> >>>
> >>> [4] Section 4.  Lightweight 4over6 Architecture
> >>>
> >>>  The solution specified in this document allows the assignment of
> >>>  either a full or a shared IPv4 address requesting CPEs.  [RFC7040]
> >>>  provides a mechanism for assigning a full IPv4 address only.
> >>>
> >>> Please explain what entities would share the IPv4 address.  For examp=
le,
> >>> this is needed as a foundation for the statement in Section 8 that
> >>> "ICMPv4 does not work in an address sharing environment without
> >>> special handling [RFC6269]."
> >>
> >> [if] OK. Reworded version:
> >>
> >> The solution specified in this document allows the assignment of
> >>   either a full IPv4 address for a CPE, or a single IPv4 address which=
 is
> >> shared between multiple CPEs.  [RFC7040]
> >>   provides a mechanism for assigning a full IPv4 address only.
> >>
> >>
> >>>
> >>> [5] Section 5.1.  Lightweight B4 Provisioning with DHCPv6
> >>>
> >>>  For DHCPv6 based configuration of these parameters, the lwB4 SHOULD
> >>>  implement OPTION_S46_CONT_LW
> >>>
> >>> What are the consequences of not doing that?  The could be addressed
> >>> by changing that "SHOULD" to a "MUST", although I suspect that what's
> >>> wanted here is a forward reference to the alternatives discussed in
> >>> Section 7.
> >>
> >> [if] Rewording with:
> >>
> >> To configure these parameters using DHCPv6, the lwB4 MUST implement
> >> OPTION_S46_CONT_LW.
> >>
> >>
> >>>
> >>> [6] Also in Section 5.1
> >>>
> >>>  If stateful IPv4 configuration or additional IPv4 configuration
> >>>  information is required, DHCPv4 [RFC2131] must be used.
> >>>
> >>> "must" -> "MUST"
> >>>
> >>>  In the event that the lwB4's encapsulation source address is changed
> >>>  for any reason (such as the DHCPv6 lease expiring), the lwB4's
> >>>  dynamic provisioning process must be re-initiated.
> >>>
> >>> "must" -> "MUST"
> >>
> >> [if] OK
> >>
> >>>
> >>> [7] Also in Section 5.1
> >>>
> >>>  Unless an lwB4 is being allocated a full IPv4 address, it is
> >>>  RECOMMENDED that PSIDs containing the well-known ports (0-1023) are
> >>>  not allocated to lwB4s.
> >>>
> >>> Please explain why.  Also, "well-known ports" is not the right term;
> >>> I believe those are the "system ports", e.g., see:
> >>>
> >>> http://www.iana.org/assignments/service-names-port-numbers/service-na=
mes-p
> >>> ort-numbers.xhtml
> >>
> >> [if] Reworded:
> >>
> >> Unless an lwB4 is being allocated a full IPv4 address, it is
> >>   RECOMMENDED that PSIDs containing the system ports (0-1023) are
> >>   not allocated to lwB4s.
> >>
> >>
> >>>
> >>>
> >>> [8] Still in Section 5.1
> >>>
> >>>  In the event that the lwB4 receives an ICMPv6 error message (type 1,
> >>>  code 5) originating from the lwAFTR, the lwB4 SHOULD interpret this
> >>>  to mean that no matching entry in the lwAFTR's binding table has bee=
n
> >>>  found.  The lwB4 MAY then re-initiate the dynamic port-restricted
> >>>  provisioning process.  The lwB4's re-initiation policy SHOULD be
> >>>  configurable.
> >>>
> >>> What happens if the lwB4 ignores the first "SHOULD"?
> >>
> >>
> >> [if] Reword:
> >> ...the lwB4 interprets this to mean that no matching entry in the lwAF=
TR's
> >> binding table has been found, so the IPv4 payload is not being forward=
ed
> >> by the lwAFTR.
> >>
> >>
> >>
> >>>
> >>> [9] Section 8.1.  ICMPv4 Processing by the lwAFTR
> >>>
> >>> This describes two approaches to ICMPv4 processing.  Are there any ot=
hers?
> >>> If so, please add some text about them, otherwise, I suggest this cha=
nge:
> >>>
> >>> OLD
> >>>  Additionally, the lwAFTR MAY implement:
> >>>
> >>>  o  Discarding of all inbound ICMP messages.
> >>> NEW
> >>>  Otherwise the lwAFTR MUST discard all inbound ICMPv4 messages.
> >>
> >> [if] OK
> >>
> >>>
> >>>
> >>> Nits/editorial comments:
> >>>
> >>> -- Section 1.  Introduction
> >>>
> >>>  Basic Bridging BroadBand element: A B4 element is a function
> >>>                                    implemented on a dual-stack capabl=
e
> >>>                                    node, either a directly connected
> >>>                                    device or a CPE, that creates a
> >>>                                    tunnel to an AFTR.
> >>>
> >>> I suggest changing "a tunnel to an AFTR" to "an IPv4-in-IPv6 tunnel
> >>> to an AFTR" for consistency with the AFTR definition.
> >>
> >> [if] OK
> >>
> >>>
> >>> -- Section 5.2.  Lightweight B4 Data Plane Behavior
> >>>
> >>>  Internally connected hosts source IPv4 packets with an [RFC1918]
> >>>  address.
> >>
> >> [if] Reword with:
> >>
> >> Hosts connected to the customer's network behind the lwB4 source IPv4
> >> packets with an [RFC1918] address.
> >>
> >>
> >>>
> >>> Internal to what?  Please explain.
> >>>
> >>> -- Section 6.2.  lwAFTR Data Plane Behavior
> >>>
> >>>  The lwAFTR MUST support hairpinning of traffic between two lwB4s, by
> >>>  performing de-capsulation and re-encapsulation of packets.  The
> >>>  hairpinning policy MUST be configurable.
> >>>
> >>> Please explain "hairpinning" - it should suffice to add "from one lwB=
4
> >>> that need to be sent to another lwB4 associated with the same AFTR"
> >>> after "de-capsulation and re-encapsulation of packets".
> >>
> >> [if] OK with the suggested wording.
> >>
> >>>
> >>> -- Section 7.  Additional IPv4 address and Port Set Provisioning
> >>> Mechanisms
> >>>
> >>>  In a Lightweight 4over6 domain, the binding information MUST be
> >>>  aligned between the lwB4s, the lwAFTRs and the provisioning server.
> >>>
> >>> "aligned between" -> "synchronized across" for consistency with use
> >>> of forms of "synchronize" elsewhere in this draft.
> >>
> >> [if] OK
> >>
> >>>
> >>> idnits found a few things to complain about:
> >>>
> >>> - The use of "the well-known range 192.0.0.0/29" in Section 5.1.  Thi=
s is
> >>> ok,
> >>> 	as it's describing DS-Lite use of that range that is documented
> >>> 	elsewhere.  If lw4o6 is using that range, an explanation ought to be
> >>> 	added to Section 5.1.
> >>
> >> [if] lw4o6 doesn=B9t use these
> >>
> >>>
> >>> - Three references have been updated:
> >>>
> >>> =3D=3D Outdated reference: A later version (-09) exists of
> >>>    draft-ietf-softwire-map-dhcp-07
> >>>
> >>> =3D=3D Outdated reference: draft-ietf-dhc-dhcpv4-over-dhcpv6 has been
> >>> published
> >>>    as RFC 7341
> >>>
> >>> =3D=3D Outdated reference: A later version (-06) exists of
> >>>    draft-ietf-pcp-port-set-05
> >>
> >> [if] All should now be fixed in v11 (posted earlier today)
> >>
> >>>
> >>> --- Selected RFC 5706 Appendix A Q&A for OPS-Dir review ---
> >>>
> >>> A.1.1.  Has deployment been discussed?
> >>>
> >>> 	Yes, this protocol is intended to improve scalability over the exist=
ing
> >>> 	DS-Lite mechanism.
> >>>
> >>> A.1.2.  Has installation and initial setup been discussed?
> >>>
> >>> 	No, there are vague references to a provisioning mechanism and
> >>> 	synchronization functionality that need to be set up.  See
> >>> 	major open issue [2] above which calls out a missing normative
> >>> 	reference that should address these topics.
> >>>
> >>> A.1.3.  Has the migration path been discussed?
> >>>
> >>> 	No, but I suspect that this concern is inapplicable, as I think
> >>> 	a carrier would not migrate from DS-Lite to lw4o6, but would
> >>> 	deploy lw4o6 instead of DS-Lite.
> >>>
> >>> A.1.4.  Have the Requirements on other protocols and functional
> >>>      components been discussed?
> >>>
> >>> 	Yes, but major open issue [1] is effectively in this area.
> >>>
> >>> A.1.6.  Have suggestions for verifying correct operation been discuss=
ed?
> >>>
> >>> 	No, and they probably should be, as this protocol requires state
> >>> 	synchronization among the lwB4, lwAFTR and the provisioning system,
> >>> 	and is likely to exhibit problematic behavior if the relevant state
> >>> 	information gets out of sync.
> >>>
> >>> A.1.9.  Is configuration discussed?
> >>>
> >>> 	Yes, the draft does a good job of discussing what needs to be
> >>> 	configured to set up the protocol (aside from state synchronization)
> >>> 	and calling out protocol behavior aspects that should be configurabl=
e.
> >>>
> >>> A.2 Management
> >>>
> >>> 	This is really not discussed, and in particular the lack of discussi=
on
> >>> 	of management information is notable because this protocol has a
> >>> 	different operational structure than DS-Lite.  So, specifically:
> >>>
> >>> A.2.2.  Is management information discussed?
> >>>
> >>> 	No, this is minor open issue [3].  A sentence pointing to applicable
> >>> 	MIB and/or YANG draft(s) would suffice to address this.
> >>>
> >>> A.2.4.  Is configuration management discussed?
> >>>
> >>> 	Yes - the discussion is ok, even though specific configuration
> mechanisms
> >>> 	are not discussed.
> >>>
> >>> A.3.  Documentation
> >>>
> >>> 	The protocol does have significant operational impacts on the Intern=
et.
> >>>
> >>> 	The shepherd's writeup indicates that multiple implementations exist
> >>> 	among which interoperability has been tested.
> >>>
> >>> Thanks,
> >>> --David
> >>> ----------------------------------------------------
> >>> David L. Black, Distinguished Engineer
> >>> EMC Corporation, 176 South St., Hopkinton, MA  01748
> >>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> >>> david.black@emc.com        Mobile: +1 (978) 394-7754
> >>> ----------------------------------------------------
> >>>
> >
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires


From nobody Mon Oct 20 11:06:41 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E50C1A8931; Mon, 20 Oct 2014 10:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wrs9MGF-rEnd; Mon, 20 Oct 2014 10:14:37 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D147B1A8920; Mon, 20 Oct 2014 10:03:40 -0700 (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 Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7749B1B8427; Mon, 20 Oct 2014 10:03:40 -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 ESMTP id 4B16C53E07C; Mon, 20 Oct 2014 10:03:40 -0700 (PDT)
Received: from [10.0.10.40] (71.233.43.215) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 20 Oct 2014 10:03:40 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D2432779493605F25B@MX104CL02.corp.emc.com>
Date: Mon, 20 Oct 2014 13:03:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <5DE78446-2E95-4071-B348-8970E7617259@nominum.com>
References: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com> <D0646F50.DDFC8%ian.farrer@telekom.de> <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com> <1F384A7F-E2EC-4DEF-A5B7-6A8D65C921E5@gmail.com> <CE03DB3D7B45C245BCA0D2432779493605F25B@MX104CL02.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/K6iG4bSCH5d7YGIaXhYoIs01dOg
X-Mailman-Approved-At: Mon, 20 Oct 2014 11:06:34 -0700
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, sunqiong <sunqiong@ctbri.com.cn>, "softwires@ietf.org" <softwires@ietf.org>, "tena@huawei.com" <tena@huawei.com>
Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 20 Oct 2014 17:14:38 -0000

On Oct 20, 2014, at 9:43 AM, Black, David <david.black@emc.com> wrote:
> Whether adding an informative mention of the YANG model rises to the =
level of
> "required" would be up to the OPS ADs.  It may help implementers find =
the YANG
> model, which could be useful.

The problem with this is that the informative reference would wind up =
being to a -00 draft of the yang data model; unless that document makes =
rapid progress, it's unlikely that the reference will be to a version of =
the document that anybody would find useful.   It might be worth asking =
the authors of that document where they think it will be in two or three =
months, since that's about the length of the RFC Editor queue at the =
moment, IIRC.=


From nobody Tue Oct 21 01:24:50 2014
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E431A6FA9; Tue, 21 Oct 2014 00:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.998
X-Spam-Level: **
X-Spam-Status: No, score=2.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MANGLED_PREMTR=2.3, RCVD_IN_SORBS_HTTP=0.001, RCVD_IN_SORBS_SOCKS=1.927, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jpj4CtHEzCxE; Tue, 21 Oct 2014 00:48:29 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38D921AD0A1; Tue, 21 Oct 2014 00:48:29 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id z10so805548pdj.29 for <multiple recipients>; Tue, 21 Oct 2014 00:48:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jvFP3kb6jgF2PlhYPStLzxPYpXiXpkis/4+0BfXyYrU=; b=ARG3wXDojkT0a0QFBB1Q1uJahPj0tAJCRcCPSmieXFTvOtvuwfnM1w+n9A5oOftXhQ fItZE9sg93IpV+ZjKnP8B9htR+ACk71n6Nr3N/JEwVTVbH7aQmD/n6nb0MgYwjgaBr8J EuL4q7hZugVLvqQdmiO0QrVnL97+PMqA9n7GI6cROEAtyw++wRvFAzqY+amfRuZRG8E/ wxtMPeWT5LMWTMTt4OaNJPnkW5bK5LbbCQqqhPHODb78ixC6IvPorjNNfhx9BHOQRHL3 ssgZM3M2KiFPeeig3iI0nedv586vachqAHwFAH/b1t+YpDayVTAKM2vvsSUSoxuPg752 8GCQ==
X-Received: by 10.67.30.34 with SMTP id kb2mr32266458pad.97.1413877708901; Tue, 21 Oct 2014 00:48:28 -0700 (PDT)
Received: from sunqideair.lan ([166.111.68.233]) by mx.google.com with ESMTPSA id iw1sm11213741pac.21.2014.10.21.00.48.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 00:48:28 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <5DE78446-2E95-4071-B348-8970E7617259@nominum.com>
Date: Tue, 21 Oct 2014 15:48:15 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F636FED-96F8-4BB5-9BB1-A76C27D4CFF1@gmail.com>
References: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com> <D0646F50.DDFC8%ian.farrer@telekom.de> <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com> <1F384A7F-E2EC-4DEF-A5B7-6A8D65C921E5@gmail.com> <CE03DB3D7B45C245BCA0D2432779493605F25B@MX104CL02.corp.emc.com> <5DE78446-2E95-4071-B348-8970E7617259@nominum.com>
To: "Black, David" <david.black@emc.com>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/7mMHzrgGkJxzh_oWKMZmaT-YW7Q
X-Mailman-Approved-At: Tue, 21 Oct 2014 01:24:47 -0700
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, sunqiong <sunqiong@ctbri.com.cn>, "softwires@ietf.org" <softwires@ietf.org>, "tena@huawei.com" <tena@huawei.com>
Subject: Re: [Softwires] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 21 Oct 2014 07:48:30 -0000

Dear Ted, David,

As a co-author the the draft-sun-softwire-yang-00, I have to admit this =
draft is pre-mature and needs in-depth discussion before it can go =
forward. We don=92t know how far it will have progressed since this =
original idea as well as the document structure needs feedback from both =
the Softwire WG and the netmod WG. We don=92t hope this draft to be a =
potential blocking point of the doc that has got consensus of the WG, as =
the discussions might be long.=20

Thanks,=20
Qi

On Oct 21, 2014, at 1:03 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Oct 20, 2014, at 9:43 AM, Black, David <david.black@emc.com> wrote:
>> Whether adding an informative mention of the YANG model rises to the =
level of
>> "required" would be up to the OPS ADs.  It may help implementers find =
the YANG
>> model, which could be useful.
>=20
> The problem with this is that the informative reference would wind up =
being to a -00 draft of the yang data model; unless that document makes =
rapid progress, it's unlikely that the reference will be to a version of =
the document that anybody would find useful.   It might be worth asking =
the authors of that document where they think it will be in two or three =
months, since that's about the length of the RFC Editor queue at the =
moment, IIRC.


From nobody Tue Oct 21 06:47:32 2014
Return-Path: <ietfdbh@comcast.net>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07B541A6F24 for <softwires@ietfa.amsl.com>; Tue, 21 Oct 2014 06:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.891
X-Spam-Level: 
X-Spam-Status: No, score=0.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, MANGLED_PREMTR=2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N67gfYSV5WLJ for <softwires@ietfa.amsl.com>; Tue, 21 Oct 2014 06:45:21 -0700 (PDT)
Received: from resqmta-po-12v.sys.comcast.net (resqmta-po-12v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:171]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6BA71A6F2E for <softwires@ietf.org>; Tue, 21 Oct 2014 06:45:17 -0700 (PDT)
Received: from resomta-po-09v.sys.comcast.net ([96.114.154.233]) by resqmta-po-12v.sys.comcast.net with comcast id 5plA1p00452QWKC01plHnx; Tue, 21 Oct 2014 13:45:17 +0000
Received: from [IPv6:2601:6:6f00:495:8849:6cb4:5dec:4f2e] ([IPv6:2601:6:6f00:495:8849:6cb4:5dec:4f2e]) by resomta-po-09v.sys.comcast.net with comcast id 5pl91p00E0aTJ8q01plAJE; Tue, 21 Oct 2014 13:45:14 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_37AF80FC-2CAB-4BA5-891C-F327B21C33DB"
From: David Harrington <ietfdbh@comcast.net>
In-Reply-To: <2F636FED-96F8-4BB5-9BB1-A76C27D4CFF1@gmail.com>
Date: Tue, 21 Oct 2014 09:45:07 -0400
Message-Id: <14016D7F-A563-4114-8433-96C778663D62@comcast.net>
References: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com> <D0646F50.DDFC8%ian.farrer@telekom.de> <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com> <1F384A7F-E2EC-4DEF-A5B7-6A8D65C921E5@gmail.com> <CE03DB3D7B45C245BCA0D2432779493605F25B@MX104CL02.corp.emc.com> <5DE78446-2E95-4071-B348-8970E7617259@nominum.com> <2F636FED-96F8-4BB5-9BB1-A76C27D4CFF1@gmail.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1413899117; bh=dD51SdhW+0Jjw3anrcPEAWP40xDP0LkAQAW7fBe9KRs=; h=Received:Received:Subject:Mime-Version:Content-Type:From:Date: Message-Id:To; b=F3zC/KweuIhHpKVG4aQvGHr+fsrleo3yRmnfNzMPzsU1KAe9s2vqENfwP2IDaBcyk 2pQEP1g1dmYKZq05J2sQTWux3w9K0h3uLi4vRTloQ8CiO3MqU+sJ4NLIi0wNy3r4p9 LBVf7EqV3U72LBR1Z74+9EZ1iqaMK/g9ZqEb/D7FM6UDim82yYzULraVLkT+0RXYms lQpNGHS2qLSiIrtTbJJLZuBIyeVy7QTNOTD2GWMonJvAbMLrPgmEOxmFYCEdRx5yF1 zoZdG5bC35YI236fO7rV8Czevm97jerfb2I7TobSa7HAXjmibH1NA+dEI1JDc8oTeZ oRmrFQb2Wq5rw==
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/ZPeUhmX9RAGBABoFFgTqgZ1RMKY
X-Mailman-Approved-At: Tue, 21 Oct 2014 06:47:24 -0700
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, sunqiong <sunqiong@ctbri.com.cn>, "softwires@ietf.org" <softwires@ietf.org>, Tina Tsou <tena@huawei.com>, "Black, David" <david.black@emc.com>
Subject: Re: [Softwires] [OPS-DIR] Gen-ART and OPS-Dir review of draft-ietf-softwire-lw4over6-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 21 Oct 2014 13:45:24 -0000

--Apple-Mail=_37AF80FC-2CAB-4BA5-891C-F327B21C33DB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

I think there are a few problems with this draft that should be looked =
at more closely.

1) I think there is a problem with having a MUST condition in the spec =
depending on a companion document that will be published later.

"The consequence of this architecture is that the information
   maintained by the provisioning mechanism and the one maintained by
   the lwAFTR MUST be synchronized (See figure 2).  The details of this
   synchronization depend on the exact provisioning mechanism and will
   be discussed in a companion document.
=93

There are additional synchronization requirements specified in 6.1 - =
Binding Table Maintenance.

If the synchronization is that important that it deserves multiple MUSTs =
in the spec, and the details depend on the provisioning mechanism, then =
it sounds reasonable to consider the companion document to be required.

It seems to me that, if synchronization is critical and we want =
interoperability, there should  be a mandatory-to-implement =
synchronization spec defined before this spec is ready for publication.

2) I have a related concern: I don=92t see discussion of how the =
implementation should be operated and monitored, remotely.
Since this implementation is expected to reside in customer premises =
equipment, having a remote monitoring and management capability seems =
important.
And since this is being developed in the IETF, where interoperability is =
important, it would seem an IETF standardized monitoring and management =
solution would be desirable.

A MIB module would provide monitoring capability, but none is defined or =
suggested here. This is an extension to DS-LIte, and there is a DS-Lite =
MIB. There is no discussion of whetherr that DS-Lite MIB module would be =
applicable to lw4o6, or whether that MIB module would require changes to =
be applicable to lw4o6 monitoring.

A YANG solution could address both the monitoring and provisioning =
requirements.

But an operator cannot use it if it isn=92t implemented, so there should =
be a mandatory-to-implement mechanism to allow for monitoring in an =
interoperable manner. (Operators can still choose to deploy different =
non-interoperable solutions fi they choose, but without a =
mandatory-to-implement baseline for interoperability, they cannot choose =
one known to be interoperable across all standard-compliant =
implementations.)

3) I have a concern with section 3.2.1, which is entitled =93Changes to =
RFC2473 and RFC6333 Fragmentation Behavior=94.
The text says to follow the best current practices of a number of other =
documents, but it never actually discusses what the changes to =
fragmentation behavior would be.=20
RFC2473 and RFC6333 are both standards-track. Is this document proposing =
to update those standards? It doesn=92t say so in the I-D heading.
The RFCs containing best current practices cover a lot of ground. This =
feels like hand-waving as a result.

Are all of the best practices needed for this spec to work properly, or =
just some of them?
Are some of these BCPs REQUIRED for this spec to work properly?
This section is about changes in fragmentation behavior. Are there =
specific sections of the BCPs that are important to apply, for the =
changes in fragmentation behavior?
The text specifies following the best current practices as a SHOULD; it =
doesn=92t discuss why this is only a SHOULD and not a MUST.
Under what circumstances would it be acceptable to NOT follow these best =
practices?
What would happen to the network or the users of the network if an lwB4 =
implementation does NOT follow those guidelines?
(This would be easier to discuss if the spec referred to specific best =
practices relevant to fragmentation.)

4) Section 7 suggests a number of additional provisioning mechanisms:

   In addition to the DHCPv6 based mechanism described in section 5.1,
   several other IPv4 provisioning protocols have been suggested.  These
   protocols MAY be implemented.  These alternatives include:

   o  DHCPv4 over DHCPv6: [RFC7341] describes implementing DHCPv4
      messages over an IPv6 only service providers network.  This
      enables leasing of IPv4 addresses and makes DHCPv4 options
      available to the DHCPv4 over DHCPv6 client.

Cui, et al.              Expires April 17, 2015                [Page 12]
Internet-Draft             Lightweight 4over6               October 2014

   o  PCP[RFC6887]: an lwB4 MAY use [I-D.ietf-pcp-port-set] to retrieve
      a restricted IPv4 address and a set of ports.

   In a Lightweight 4over6 domain, the binding information MUST be
   aligned between the lwB4s, the lwAFTRs and the provisioning server.

How do we achieve interoperability if each implementation can choose =
different provisioning mechanisms?
Especially, given that synchronization is critical, and is dependent on =
the provisioning mechanism used?

5) section 7 suggests provisioning mechanisms in addition to DHCPv6, so =
I checked to see if DHCPv6 was required (i.e. mandatory to implement).
That also appears to merely be an option.=20
So there apparently is no mandatory-to-implement way to address these =
MUSTs:
" In lw4o6, a number of lw4o6 specific configuration parameters must be
   provisioned to the lwB4. =93



David Harrington
ietfdbh@comcast.net



On Oct 21, 2014, at 3:48 AM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:

> Dear Ted, David,
>=20
> As a co-author the the draft-sun-softwire-yang-00, I have to admit =
this draft is pre-mature and needs in-depth discussion before it can go =
forward. We don=92t know how far it will have progressed since this =
original idea as well as the document structure needs feedback from both =
the Softwire WG and the netmod WG. We don=92t hope this draft to be a =
potential blocking point of the doc that has got consensus of the WG, as =
the discussions might be long.=20
>=20
> Thanks,=20
> Qi
>=20
> On Oct 21, 2014, at 1:03 AM, Ted Lemon <ted.lemon@nominum.com> wrote:
>=20
>> On Oct 20, 2014, at 9:43 AM, Black, David <david.black@emc.com> =
wrote:
>>> Whether adding an informative mention of the YANG model rises to the =
level of
>>> "required" would be up to the OPS ADs.  It may help implementers =
find the YANG
>>> model, which could be useful.
>>=20
>> The problem with this is that the informative reference would wind up =
being to a -00 draft of the yang data model; unless that document makes =
rapid progress, it's unlikely that the reference will be to a version of =
the document that anybody would find useful.   It might be worth asking =
the authors of that document where they think it will be in two or three =
months, since that's about the length of the RFC Editor queue at the =
moment, IIRC.
>=20
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir


--Apple-Mail=_37AF80FC-2CAB-4BA5-891C-F327B21C33DB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Hi,<div><br></div><div>I think there are a few =
problems with this draft that should be looked at more =
closely.<br><div><br></div><div>1) I think there is a problem with =
having a MUST condition in the spec depending on a companion document =
that will be published later.</div><div><br></div><div>"<span =
style=3D"font-size: 13px; line-height: 1.2em;">The consequence of this =
architecture is that the information</span><pre style=3D"line-height: =
1.2em; margin-top: 0px; margin-bottom: 0px; font-size: 13px;">   =
maintained by the provisioning mechanism and the one maintained by
   the lwAFTR MUST be synchronized (See figure 2).  The details of this
   synchronization depend on the exact provisioning mechanism and will
   be discussed in a companion =
document.</pre><div>=93</div><div><br></div><div>There are additional =
synchronization requirements specified in 6.1 - Binding Table =
Maintenance.</div><div><br></div><div>If the synchronization is that =
important that it deserves multiple MUSTs in the spec, and the details =
depend on the provisioning mechanism, then it sounds reasonable to =
consider the companion document to be =
required.</div><div><br></div><div>It seems to me that, if =
synchronization is critical and we want interoperability, there should =
&nbsp;be a mandatory-to-implement synchronization spec defined before =
this spec is ready for publication.</div><div><br></div><div>2) I have a =
related concern: I don=92t see discussion of how the implementation =
should be operated and monitored, remotely.</div><div>Since this =
implementation is expected to reside in customer premises equipment, =
having a remote monitoring and management capability seems =
important.</div><div>And since this is being developed in the IETF, =
where interoperability is important, it would seem an IETF standardized =
monitoring and management solution would be =
desirable.</div><div><br></div><div>A MIB module would provide =
monitoring capability, but none is defined or suggested here. This is an =
extension to DS-LIte, and there is a DS-Lite MIB. There is no discussion =
of whetherr that DS-Lite MIB module would be applicable to lw4o6, or =
whether that MIB module would require changes to be applicable to lw4o6 =
monitoring.</div><div><br></div><div>A YANG solution could address both =
the monitoring and provisioning =
requirements.</div><div><br></div><div>But an operator cannot use it if =
it isn=92t implemented, so there should be a mandatory-to-implement =
mechanism to allow for monitoring in an interoperable manner. (Operators =
can still choose to deploy different non-interoperable solutions fi they =
choose, but without a mandatory-to-implement baseline for =
interoperability, they cannot choose one known to be interoperable =
across all standard-compliant =
implementations.)</div><div><br></div><div>3) I have a concern with =
section 3.2.1, which is entitled =93Changes to RFC2473 and RFC6333 =
Fragmentation Behavior=94.</div><div>The text says to follow the best =
current practices of a number of other documents, but it never actually =
discusses what the changes to fragmentation behavior would =
be.&nbsp;</div><div>RFC2473 and RFC6333 are both standards-track. Is =
this document proposing to update those standards? It doesn=92t say so =
in the I-D heading.</div><div>The RFCs containing best current practices =
cover a lot of ground. This feels like hand-waving as a =
result.</div><div><br></div><div>Are all of the best practices needed =
for this spec to work properly, or just some of them?</div><div>Are some =
of these BCPs REQUIRED for this spec to work properly?</div><div>This =
section is about changes in fragmentation behavior. Are there specific =
sections of the BCPs that are important to apply, for the changes in =
fragmentation behavior?</div><div>The text specifies following the best =
current practices as a SHOULD; it doesn=92t discuss why this is only a =
SHOULD and not a MUST.</div><div>Under what circumstances would it be =
acceptable to NOT follow these best practices?</div><div>What would =
happen to the network or the users of the network if an lwB4 =
implementation does NOT follow those guidelines?</div><div>(This would =
be easier to discuss if the spec referred to specific best practices =
relevant to fragmentation.)</div><div><br></div><div>4) Section 7 =
suggests a number of additional provisioning mechanisms:</div><div><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-bottom: 0px; =
font-size: 13px;">
   In addition to the DHCPv6 based mechanism described in section 5.1,
   several other IPv4 provisioning protocols have been suggested.  These
   protocols MAY be implemented.  These alternatives include:

   o  DHCPv4 over DHCPv6: [RFC7341] describes implementing DHCPv4
      messages over an IPv6 only service providers network.  This
      enables leasing of IPv4 addresses and makes DHCPv4 options
      available to the DHCPv4 over DHCPv6 client.

<span class=3D"m_ftr" style=3D"color: rgb(128, 128, 128); =
border-bottom-width: 1px; border-bottom-style: solid; =
border-bottom-color: rgb(160, 160, 160);">Cui, et al.              =
Expires April 17, 2015                [Page 12]</span>
<span class=3D"m_hdr" style=3D"color: rgb(128, 128, =
128);">Internet-Draft             Lightweight 4over6               =
October 2014</span>

   o  PCP[RFC6887]: an lwB4 MAY use [I-D.ietf-pcp-port-set] to retrieve
      a restricted IPv4 address and a set of ports.

   In a Lightweight 4over6 domain, the binding information MUST be
   aligned between the lwB4s, the lwAFTRs and the provisioning =
server.</pre><div><br></div></div><div>How do we achieve =
interoperability if each implementation can choose different =
provisioning mechanisms?</div><div>Especially, given that =
synchronization is critical, and is dependent on the provisioning =
mechanism used?</div><div><br></div><div>5) section 7 suggests =
provisioning mechanisms in addition to DHCPv6, so I checked to see if =
DHCPv6 was required (i.e. mandatory to implement).</div><div>That also =
appears to merely be an option.&nbsp;</div><div>So there apparently is =
no mandatory-to-implement way to address these MUSTs:</div><div>"<span =
style=3D"font-size: 13px; line-height: 1.2em;">   In lw4o6, a number of =
lw4o6 specific configuration parameters must be</span></div><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-bottom: 0px; =
font-size: 13px;">   provisioned to the lwB4. =93</pre><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-bottom: 0px; =
font-size: 13px;"><br></pre><div><br></div><div><br></div><div =
apple-content-edited=3D"true">
<div>David Harrington</div><div><a =
href=3D"mailto:ietfdbh@comcast.net">ietfdbh@comcast.net</a></div><div><br>=
</div><br class=3D"Apple-interchange-newline">

</div>
<br><div><div>On Oct 21, 2014, at 3:48 AM, Qi Sun &lt;<a =
href=3D"mailto:sunqi.csnet.thu@gmail.com">sunqi.csnet.thu@gmail.com</a>&gt=
; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Dear Ted, David,<br><br>As a co-author the the =
draft-sun-softwire-yang-00, I have to admit this draft is pre-mature and =
needs in-depth discussion before it can go forward. We don=92t know how =
far it will have progressed since this original idea as well as the =
document structure needs feedback from both the Softwire WG and the =
netmod WG. We don=92t hope this draft to be a potential blocking point =
of the doc that has got consensus of the WG, as the discussions might be =
long. <br><br>Thanks, <br>Qi<br><br>On Oct 21, 2014, at 1:03 AM, Ted =
Lemon &lt;<a =
href=3D"mailto:ted.lemon@nominum.com">ted.lemon@nominum.com</a>&gt; =
wrote:<br><br><blockquote type=3D"cite">On Oct 20, 2014, at 9:43 AM, =
Black, David &lt;<a =
href=3D"mailto:david.black@emc.com">david.black@emc.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Whether adding an informative =
mention of the YANG model rises to the level of<br>"required" would be =
up to the OPS ADs. &nbsp;It may help implementers find the =
YANG<br>model, which could be useful.<br></blockquote><br>The problem =
with this is that the informative reference would wind up being to a -00 =
draft of the yang data model; unless that document makes rapid progress, =
it's unlikely that the reference will be to a version of the document =
that anybody would find useful. &nbsp;&nbsp;It might be worth asking the =
authors of that document where they think it will be in two or three =
months, since that's about the length of the RFC Editor queue at the =
moment, =
IIRC.<br></blockquote><br>_______________________________________________<=
br>OPS-DIR mailing list<br><a =
href=3D"mailto:OPS-DIR@ietf.org">OPS-DIR@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/ops-dir<br></blockquote></div><br></div></div></body>=
</html>=

--Apple-Mail=_37AF80FC-2CAB-4BA5-891C-F327B21C33DB--


From nobody Tue Oct 21 08:10:40 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B021A872A; Tue, 21 Oct 2014 08:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level: 
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_31=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRXfLjzySy2S; Tue, 21 Oct 2014 08:10:20 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DAC31A6F2E; Tue, 21 Oct 2014 08:10:20 -0700 (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 Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id C93F7DA01B3; Tue, 21 Oct 2014 15:12:44 +0000 (UTC)
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 ESMTP id 617DD53E080; Tue, 21 Oct 2014 08:09:49 -0700 (PDT)
Received: from [10.0.10.40] (71.233.43.215) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 21 Oct 2014 08:09:49 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <14016D7F-A563-4114-8433-96C778663D62@comcast.net>
Date: Tue, 21 Oct 2014 11:09:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <DF22672D-3F31-459B-B5AA-DBA855B31CD3@nominum.com>
References: <CE03DB3D7B45C245BCA0D24327794936053381@MX104CL02.corp.emc.com> <D0646F50.DDFC8%ian.farrer@telekom.de> <CE03DB3D7B45C245BCA0D24327794936059BF2@MX104CL02.corp.emc.com> <1F384A7F-E2EC-4DEF-A5B7-6A8D65C921E5@gmail.com> <CE03DB3D7B45C245BCA0D2432779493605F25B@MX104CL02.corp.emc.com> <5DE78446-2E95-4071-B348-8970E7617259@nominum.com> <2F636FED-96F8-4BB5-9BB1-A76C27D4CFF1@gmail.com> <14016D7F-A563-4114-8433-96C778663D62@comcast.net>
To: David Harrington <ietfdbh@comcast.net>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/e1gbnx0iNy8fLnlM9eqf6DuvoXw
Cc: "softwires@ietf.org" <softwires@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "Black, David" <david.black@emc.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
Subject: [Softwires] Action items from David Harrington's opsdir comments
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 21 Oct 2014 15:10:22 -0000

To Softwires:

I've included comments below, but for the benefit of the authors and =
working group, the two actions items I see from this are:

1. map-dhcp should be a MUST, not a SHOULD.
2. the working group should decide whether DHCPv4-over-DHCPv6 is MTI in =
the B4, and whether pcp-port-set is MTI in the B4, because if they are =
not, operators can't deploy them.

To David Harrington:

First, thanks for the thoughtful comments.   I don't agree with =
everything you've said here, but you've definitely pointed out two =
significant problems that need to be dealt with.

On Oct 21, 2014, at 9:45 AM, David Harrington <ietfdbh@comcast.net> =
wrote:
> 1) I think there is a problem with having a MUST condition in the spec =
depending on a companion document that will be published later.
>=20
> "The consequence of this architecture is that the information
>    maintained by the provisioning mechanism and the one maintained by
>    the lwAFTR MUST be synchronized (See figure 2).  The details of =
this
>    synchronization depend on the exact provisioning mechanism and will
>    be discussed in a companion document.
>=20
> =93

I think the authors already have made changes to this text based on =
David Black's review.

> There are additional synchronization requirements specified in 6.1 - =
Binding Table Maintenance.
>=20
> If the synchronization is that important that it deserves multiple =
MUSTs in the spec, and the details depend on the provisioning mechanism, =
then it sounds reasonable to consider the companion document to be =
required.
>=20
> It seems to me that, if synchronization is critical and we want =
interoperability, there should  be a mandatory-to-implement =
synchronization spec defined before this spec is ready for publication.

I would certainly not object if you proposed such a mechanism.   Short =
of that, with all due respect, this is a pretty absurd objection.   This =
would be like saying that since IP requires a mechanism for keeping =
routing tables up to date, RFC 791 should not have been published until =
RFC 1058 was done.

> 2) I have a related concern: I don=92t see discussion of how the =
implementation should be operated and monitored, remotely.
> Since this implementation is expected to reside in customer premises =
equipment, having a remote monitoring and management capability seems =
important.
> And since this is being developed in the IETF, where interoperability =
is important, it would seem an IETF standardized monitoring and =
management solution would be desirable.

Do we require a MIB for existing routers with non-port-shared NATs?   If =
not, then I think this is an example of something that would certainly =
be good to do, but is not a prerequisite.   There is work being done on =
a YANG model, but I don't think anybody's doing a MIB, so again, if this =
is a matter that is of interest to you, I would encourage you to take on =
this work.

> A MIB module would provide monitoring capability, but none is defined =
or suggested here. This is an extension to DS-LIte, and there is a =
DS-Lite MIB. There is no discussion of whetherr that DS-Lite MIB module =
would be applicable to lw4o6, or whether that MIB module would require =
changes to be applicable to lw4o6 monitoring.

The DS-Lite MIB doesn't manage the B4; only the AFTR.

> A YANG solution could address both the monitoring and provisioning =
requirements.

As I mentioned, work is progressing on a YANG data model.   I think this =
is a good observation, but shouldn't block the base spec.

> But an operator cannot use it if it isn=92t implemented, so there =
should be a mandatory-to-implement mechanism to allow for monitoring in =
an interoperable manner. (Operators can still choose to deploy different =
non-interoperable solutions fi they choose, but without a =
mandatory-to-implement baseline for interoperability, they cannot choose =
one known to be interoperable across all standard-compliant =
implementations.)

Do you mean that the operator can't operate an AFTR without a management =
specification, or that an operator can't operate a network with B4s that =
can't be managed?

> 3) I have a concern with section 3.2.1, which is entitled =93Changes =
to RFC2473 and RFC6333 Fragmentation Behavior=94.
> The text says to follow the best current practices of a number of =
other documents, but it never actually discusses what the changes to =
fragmentation behavior would be.=20
> RFC2473 and RFC6333 are both standards-track. Is this document =
proposing to update those standards? It doesn=92t say so in the I-D =
heading.
> The RFCs containing best current practices cover a lot of ground. This =
feels like hand-waving as a result.

We don't know how to solve this problem.   It's being discussed in the =
working group.   The text was added at my request based on similar text =
in the MAP specification; I think the authors will either take the text =
out, or else modify it to make it clear that this is a problem to look =
out for, not something we know how to fix.

> Are all of the best practices needed for this spec to work properly, =
or just some of them?
> Are some of these BCPs REQUIRED for this spec to work properly?
> This section is about changes in fragmentation behavior. Are there =
specific sections of the BCPs that are important to apply, for the =
changes in fragmentation behavior?
> The text specifies following the best current practices as a SHOULD; =
it doesn=92t discuss why this is only a SHOULD and not a MUST.
> Under what circumstances would it be acceptable to NOT follow these =
best practices?
> What would happen to the network or the users of the network if an =
lwB4 implementation does NOT follow those guidelines?
> (This would be easier to discuss if the spec referred to specific best =
practices relevant to fragmentation.)

The conclusion of the working group thus far (which may change) is that =
(a) this probably isn't a very big problem, (b) we don't know how to =
solve it in a way that doesn't possibly make things worse, and therefore =
(c) we mention it so that people can be aware of it, but do not make =
recommendations because we have none to make.   It is worth noting that =
this same issue exists for DS-Lite, and we have not had reports from the =
field that there is evidence of actual operational problems.

> 4) Section 7 suggests a number of additional provisioning mechanisms:
>    In addition to the DHCPv6 based mechanism described in section 5.1,
>    several other IPv4 provisioning protocols have been suggested.  =
These
>    protocols MAY be implemented.  These alternatives include:
>=20
>    o  DHCPv4 over DHCPv6: [RFC7341] describes implementing DHCPv4
>       messages over an IPv6 only service providers network.  This
>       enables leasing of IPv4 addresses and makes DHCPv4 options
>       available to the DHCPv4 over DHCPv6 client.
>=20
>=20
> Cui, et al.              Expires April 17, 2015                [Page =
12]
> Internet-Draft             Lightweight 4over6               October =
2014
>=20
>=20
>    o  PCP[RFC6887]: an lwB4 MAY use [I-D.ietf-pcp-port-set] to =
retrieve
>       a restricted IPv4 address and a set of ports.
>=20
>    In a Lightweight 4over6 domain, the binding information MUST be
>    aligned between the lwB4s, the lwAFTRs and the provisioning server.
>=20
>=20
> How do we achieve interoperability if each implementation can choose =
different provisioning mechanisms?
> Especially, given that synchronization is critical, and is dependent =
on the provisioning mechanism used?

Hm, I think the authors and wg should think about this.   Right now the =
expectation is that the map-dhcp option is mandatory, and these =
mechanisms are not, but if they aren't MTI in the HG, the operator can't =
depend on them working.

> 5) section 7 suggests provisioning mechanisms in addition to DHCPv6, =
so I checked to see if DHCPv6 was required (i.e. mandatory to =
implement).
> That also appears to merely be an option.=20
> So there apparently is no mandatory-to-implement way to address these =
MUSTs:
> " In lw4o6, a number of lw4o6 specific configuration parameters must =
be
>    provisioned to the lwB4. =93

Good catch, I see that the document actually says SHOULD rather than =
MUST for the map-dhcp option.   I think this should be a MUST.


From nobody Thu Oct 23 00:17:59 2014
Return-Path: <wang.cui1@zte.com.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F8021A892B for <softwires@ietfa.amsl.com>; Thu, 23 Oct 2014 00:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.76
X-Spam-Level: 
X-Spam-Status: No, score=-101.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFkqMNZy4UTy for <softwires@ietfa.amsl.com>; Thu, 23 Oct 2014 00:17:49 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB881A8919 for <softwires@ietf.org>; Thu, 23 Oct 2014 00:17:48 -0700 (PDT)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 9A5C9125787A for <softwires@ietf.org>; Thu, 23 Oct 2014 15:17:35 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id s9N7HW3T075570 for <softwires@ietf.org>; Thu, 23 Oct 2014 15:17:32 +0800 (GMT-8) (envelope-from wang.cui1@zte.com.cn)
To: softwires <softwires@ietf.org>
MIME-Version: 1.0
X-KeepSent: BB8041B5:390EEEE5-48257D7A:00278CA8; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011
Message-ID: <OFBB8041B5.390EEEE5-ON48257D7A.00278CA8-48257D7A.0027F878@zte.com.cn>
From: wang.cui1@zte.com.cn
Date: Thu, 23 Oct 2014 15:17:23 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2014-10-23 15:17:31, Serialize complete at 2014-10-23 15:17:31
Content-Type: multipart/alternative; boundary="=_alternative 0027F87248257D7A_="
X-MAIL: mse01.zte.com.cn s9N7HW3T075570
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/n_ZPfC8c4_lx1y_Pg-WC4wq-pUY
Subject: [Softwires] FWD:New Version Notification for draft-hu-softwire-multicast-radius-ext-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 23 Oct 2014 07:17:57 -0000

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

RGVhciBhbGwsDQoNCiAgV2UgaGF2ZSB1cGRhdGVkIHRoZSBWNiB2ZXJzaW9uIG9mIFJBRElVUyBB
dHRyaWJ1dGUgZm9yIA0KTXVsdGljYXN0LVByZWZpeGVzLTY0LiBBbmQgd2UgaGF2ZSBhZG9wdGVk
IGFsbCB0aGUgY29tbWVudHMgZnJvbSB0aGUgDQpvbi1saW5lIGRpc2N1c3Npb24gYW5kIG9mZi1s
aW5lIGRpc2N1c3Npb24uDQoNCiAgUGxlYXNlIGhhdmUgYSByZXZpZXcgb2YgdGhpcyBkcmFmdCBh
bmQgYW55IGNvbW1lbnRzIGFyZSB3ZWxjb21lLg0KDQpCZXN0IFJlZ2FyZHMsDQpMaW5kYSBXYW5n
DQoNCg0KaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnINC009ogMjAxNC0xMC0yMyAxNTowOTowMToN
Cg0KPiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgDQo+IDIwMTQtMTAtMjMgMTU6MDkNCj4gDQo+
IMrVvP7Iyw0KPiANCj4gIkN1aSBXYW5nIiA8d2FuZy5jdWkxQHp0ZS5jb20uY24+LCBDdWkgV2Fu
ZyA8d2FuZy5jdWkxQHp0ZS5jb20uY24+LCANCj4gTW9oYW1lZCBCb3VjYWRhaXIgPG1vaGFtZWQu
Ym91Y2FkYWlyQG9yYW5nZS5jb20+LCAiV2VpIE1lbmciIA0KPiA8bWVuZy53ZWkyQHp0ZS5jb20u
Y24+LCAiUWlhbiBXYW5nIiA8d2FuZ3FpYW5AY3RicmkuY29tLmNuPiwgUWlhbiANCj4gV2FuZyA8
d2FuZ3FpYW5AY3RicmkuY29tLmNuPiwgV2VpIE1lbmcgPG1lbmcud2VpMkB6dGUuY29tLmNuPiwg
DQo+ICJNb2hhbWVkIEJvdWNhZGFpciIgPG1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20+LCAN
Cj4gDQo+ILOty80NCj4gDQo+INb3zOINCj4gDQo+IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBm
b3IgDQpkcmFmdC1odS1zb2Z0d2lyZS1tdWx0aWNhc3QtcmFkaXVzLWV4dC0wNi50eHQNCj4gDQo+
IA0KPiBBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtaHUtc29mdHdpcmUtbXVsdGljYXN0LXJh
ZGl1cy1leHQtMDYudHh0DQo+IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgQ3Vp
IFdhbmcgYW5kIHBvc3RlZCB0byB0aGUNCj4gSUVURiByZXBvc2l0b3J5Lg0KPiANCj4gTmFtZTog
ICAgICBkcmFmdC1odS1zb2Z0d2lyZS1tdWx0aWNhc3QtcmFkaXVzLWV4dA0KPiBSZXZpc2lvbjog
ICAwNg0KPiBUaXRsZTogICAgICBSQURJVVMgRXh0ZW5zaW9ucyBmb3IgSVB2NC1FbWJlZGRlZCBN
dWx0aWNhc3QgYW5kIA0KPiBVbmljYXN0IElQdjYgUHJlZml4ZXMNCj4gRG9jdW1lbnQgZGF0ZTog
ICAyMDE0LTEwLTIzDQo+IEdyb3VwOiAgICAgIEluZGl2aWR1YWwgU3VibWlzc2lvbg0KPiBQYWdl
czogICAgICAxNg0KPiBVUkw6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvZHJhZnQtaHUtDQo+IHNvZnR3aXJlLW11bHRpY2FzdC1yYWRpdXMtZXh0LTA2LnR4
dA0KPiBTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtaHUtc29mdHdpcmUtDQo+IG11bHRpY2FzdC1yYWRpdXMtZXh0Lw0KPiBIdG1saXplZDogICAg
ICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaHUtc29mdHdpcmUtDQo+IG11bHRp
Y2FzdC1yYWRpdXMtZXh0LTA2DQo+IERpZmY6ICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3Jn
L3JmY2RpZmY/dXJsMj1kcmFmdC1odS1zb2Z0d2lyZS0NCj4gbXVsdGljYXN0LXJhZGl1cy1leHQt
MDYNCj4gDQo+IEFic3RyYWN0Og0KPiAgICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBhIG5ldyBS
ZW1vdGUgQXV0aGVudGljYXRpb24gRGlhbC1JbiBVc2VyDQo+ICAgIFNlcnZpY2UgKFJBRElVUykg
YXR0cmlidXRlIHRvIGNhcnJ5IHRoZSBNdWx0aWNhc3QtUHJlZml4ZXMtNjQNCj4gICAgaW5mb3Jt
YXRpb24sIGFpbWluZyB0byBkZWxpdmVyeSB0aGUgTXVsdGljYXN0IGFuZCBVbmljYXN0IElQdjYN
Cj4gICAgUHJlZml4ZXMgdG8gYmUgdXNlZCB0byBidWlsZCBtdWx0aWNhc3QgYW5kIHVuaWNhc3Qg
SVB2NC1FbWJlZGRlZCBJUHY2DQo+ICAgIGFkZHJlc3Nlcy4gdGhpcyBSQURJVVMgYXR0cmlidXRl
IGlzIGRlZmluZWQgYmFzZWQgb24gdGhlIGVxdWl2YWxlbnQNCj4gICAgREhDUHY2IE9QVElPTl92
Nl9QUkVGSVg2NCBvcHRpb24uDQo+IA0KPiAgDQo+IA0KPiANCj4gUGxlYXNlIG5vdGUgdGhhdCBp
dCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2YgDQpzdWJtaXNz
aW9uDQo+IHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUg
YXQgdG9vbHMuaWV0Zi5vcmcuDQo+IA0KPiBUaGUgSUVURiBTZWNyZXRhcmlhdA0KPiANCg0K
--=_alternative 0027F87248257D7A_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkRlYXIgYWxsLDwvZm9udD4NCjxicj4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7IFdlIGhhdmUgdXBkYXRlZCB0
aGUgVjYgdmVyc2lvbg0Kb2YgUkFESVVTIEF0dHJpYnV0ZSBmb3IgTXVsdGljYXN0LVByZWZpeGVz
LTY0LiBBbmQgd2UgaGF2ZSBhZG9wdGVkIGFsbA0KdGhlIGNvbW1lbnRzIGZyb20gdGhlIG9uLWxp
bmUgZGlzY3Vzc2lvbiBhbmQgb2ZmLWxpbmUgZGlzY3Vzc2lvbi48L2ZvbnQ+DQo8YnI+DQo8YnI+
PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyBQbGVhc2UgaGF2ZSBhIHJldmll
dyBvZiB0aGlzDQpkcmFmdCBhbmQgYW55IGNvbW1lbnRzIGFyZSB3ZWxjb21lLjwvZm9udD4NCjxi
cj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+QmVzdCBSZWdhcmRzLDwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+TGluZGEgV2FuZzwvZm9udD4N
Cjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPmludGVybmV0LWRyYWZ0c0BpZXRmLm9y
ZyDQtNPaIDIwMTQtMTAtMjMgMTU6MDk6MDE6PGJyPg0KPGJyPg0KJmd0OyBpbnRlcm5ldC1kcmFm
dHNAaWV0Zi5vcmcgPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mZ3Q7IDIwMTQt
MTAtMjMgMTU6MDk8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0K
Jmd0OyDK1bz+yMs8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0K
Jmd0OyAmcXVvdDtDdWkgV2FuZyZxdW90OyAmbHQ7d2FuZy5jdWkxQHp0ZS5jb20uY24mZ3Q7LCBD
dWkgV2FuZyAmbHQ7d2FuZy5jdWkxQHp0ZS5jb20uY24mZ3Q7LA0KPGJyPg0KJmd0OyBNb2hhbWVk
IEJvdWNhZGFpciAmbHQ7bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSZndDssICZxdW90O1dl
aQ0KTWVuZyZxdW90OyA8YnI+DQomZ3Q7ICZsdDttZW5nLndlaTJAenRlLmNvbS5jbiZndDssICZx
dW90O1FpYW4gV2FuZyZxdW90OyAmbHQ7d2FuZ3FpYW5AY3RicmkuY29tLmNuJmd0OywNClFpYW4g
PGJyPg0KJmd0OyBXYW5nICZsdDt3YW5ncWlhbkBjdGJyaS5jb20uY24mZ3Q7LCBXZWkgTWVuZyAm
bHQ7bWVuZy53ZWkyQHp0ZS5jb20uY24mZ3Q7LA0KPGJyPg0KJmd0OyAmcXVvdDtNb2hhbWVkIEJv
dWNhZGFpciZxdW90OyAmbHQ7bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSZndDssDQo8L2Zv
bnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyCzrcvNPC9mb250
PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mZ3Q7IDxicj4NCiZndDsg1vfM4jwvZm9udD48
L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7IE5ldyBWZXJzaW9uIE5v
dGlmaWNhdGlvbiBmb3IgZHJhZnQtaHUtc29mdHdpcmUtbXVsdGljYXN0LXJhZGl1cy1leHQtMDYu
dHh0PC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mZ3Q7IDxicj4NCiZndDsgPGJy
Pg0KJmd0OyBBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtaHUtc29mdHdpcmUtbXVsdGljYXN0
LXJhZGl1cy1leHQtMDYudHh0PGJyPg0KJmd0OyBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0
dGVkIGJ5IEN1aSBXYW5nIGFuZCBwb3N0ZWQgdG8gdGhlPGJyPg0KJmd0OyBJRVRGIHJlcG9zaXRv
cnkuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IE5hbWU6ICZuYnNwOyAmbmJzcDsgJm5ic3A7ZHJhZnQt
aHUtc29mdHdpcmUtbXVsdGljYXN0LXJhZGl1cy1leHQ8YnI+DQomZ3Q7IFJldmlzaW9uOiAmbmJz
cDsgMDY8YnI+DQomZ3Q7IFRpdGxlOiAmbmJzcDsgJm5ic3A7ICZuYnNwO1JBRElVUyBFeHRlbnNp
b25zIGZvciBJUHY0LUVtYmVkZGVkIE11bHRpY2FzdA0KYW5kIDxicj4NCiZndDsgVW5pY2FzdCBJ
UHY2IFByZWZpeGVzPGJyPg0KJmd0OyBEb2N1bWVudCBkYXRlOiAmbmJzcDsgMjAxNC0xMC0yMzxi
cj4NCiZndDsgR3JvdXA6ICZuYnNwOyAmbmJzcDsgJm5ic3A7SW5kaXZpZHVhbCBTdWJtaXNzaW9u
PGJyPg0KJmd0OyBQYWdlczogJm5ic3A7ICZuYnNwOyAmbmJzcDsxNjxicj4NCiZndDsgVVJMOiAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOzwvZm9udD48L3R0PjxhIGhy
ZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWh1LSI+PHR0Pjxm
b250IHNpemU9Mj5odHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1odS08
L2ZvbnQ+PC90dD48L2E+PHR0Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7IHNvZnR3aXJlLW11bHRp
Y2FzdC1yYWRpdXMtZXh0LTA2LnR4dDxicj4NCiZndDsgU3RhdHVzOiAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgPC9mb250PjwvdHQ+PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9kb2MvZHJhZnQtaHUtc29mdHdpcmUtIj48dHQ+PGZvbnQgc2l6ZT0yPmh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWh1LXNvZnR3aXJlLTwvZm9udD48L3R0PjwvYT48
dHQ+PGZvbnQgc2l6ZT0yPjxicj4NCiZndDsgbXVsdGljYXN0LXJhZGl1cy1leHQvPGJyPg0KJmd0
OyBIdG1saXplZDogJm5ic3A7ICZuYnNwOyAmbmJzcDsgPC9mb250PjwvdHQ+PGEgaHJlZj0iaHR0
cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaHUtc29mdHdpcmUtIj48dHQ+PGZvbnQgc2l6
ZT0yPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWh1LXNvZnR3aXJlLTwvZm9udD48
L3R0PjwvYT48dHQ+PGZvbnQgc2l6ZT0yPjxicj4NCiZndDsgbXVsdGljYXN0LXJhZGl1cy1leHQt
MDY8YnI+DQomZ3Q7IERpZmY6ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgPC9m
b250PjwvdHQ+PGEgaHJlZj0iaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQt
aHUtc29mdHdpcmUtIj48dHQ+PGZvbnQgc2l6ZT0yPmh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlm
Zj91cmwyPWRyYWZ0LWh1LXNvZnR3aXJlLTwvZm9udD48L3R0PjwvYT48dHQ+PGZvbnQgc2l6ZT0y
Pjxicj4NCiZndDsgbXVsdGljYXN0LXJhZGl1cy1leHQtMDY8YnI+DQomZ3Q7IDxicj4NCiZndDsg
QWJzdHJhY3Q6PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7VGhpcyBkb2N1bWVudCBzcGVjaWZpZXMg
YSBuZXcgUmVtb3RlIEF1dGhlbnRpY2F0aW9uIERpYWwtSW4NClVzZXI8YnI+DQomZ3Q7ICZuYnNw
OyAmbmJzcDtTZXJ2aWNlIChSQURJVVMpIGF0dHJpYnV0ZSB0byBjYXJyeSB0aGUgTXVsdGljYXN0
LVByZWZpeGVzLTY0PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7aW5mb3JtYXRpb24sIGFpbWluZyB0
byBkZWxpdmVyeSB0aGUgTXVsdGljYXN0IGFuZCBVbmljYXN0DQpJUHY2PGJyPg0KJmd0OyAmbmJz
cDsgJm5ic3A7UHJlZml4ZXMgdG8gYmUgdXNlZCB0byBidWlsZCBtdWx0aWNhc3QgYW5kIHVuaWNh
c3QgSVB2NC1FbWJlZGRlZA0KSVB2Njxicj4NCiZndDsgJm5ic3A7ICZuYnNwO2FkZHJlc3Nlcy4g
dGhpcyBSQURJVVMgYXR0cmlidXRlIGlzIGRlZmluZWQgYmFzZWQgb24NCnRoZSBlcXVpdmFsZW50
PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7REhDUHY2IE9QVElPTl92Nl9QUkVGSVg2NCBvcHRpb24u
PGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0K
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgUGxlYXNlIG5vdGUg
dGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2YNCnN1
Ym1pc3Npb248YnI+DQomZ3Q7IHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFy
ZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRoZSBJ
RVRGIFNlY3JldGFyaWF0PGJyPg0KJmd0OyA8YnI+DQo8L2ZvbnQ+PC90dD4NCg==
--=_alternative 0027F87248257D7A_=--


From nobody Mon Oct 27 06:18:01 2014
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0CFC1AC41B for <softwires@ietfa.amsl.com>; Mon, 27 Oct 2014 06:17:41 -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=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E-y5PiYLEMUF for <softwires@ietfa.amsl.com>; Mon, 27 Oct 2014 06:17:39 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4924C1AC413 for <softwires@ietf.org>; Mon, 27 Oct 2014 06:17:39 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id 7E1BA374069; Mon, 27 Oct 2014 14:17:37 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.5]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 63A74384078; Mon, 27 Oct 2014 14:17:34 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.240]) by OPEXCLILH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0195.001; Mon, 27 Oct 2014 14:17:34 +0100
From: <mohamed.boucadair@orange.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: I-D Action: draft-vinapamula-softwire-dslite-prefix-binding-03.txt
Thread-Index: AQHP8eXhE1PU/nwNWU2G+CQf8DonXpxD7Hfg
Date: Mon, 27 Oct 2014 13:17:33 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93301BEAAD@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20141027125914.7506.51326.idtracker@ietfa.amsl.com>
In-Reply-To: <20141027125914.7506.51326.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.10.23.30920
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/ovm34dTzNiY2ov_47uNhGY6C3fc
Subject: [Softwires] TR: I-D Action: draft-vinapamula-softwire-dslite-prefix-binding-03.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 27 Oct 2014 13:17:41 -0000

Dear all,

A new version taking into account the comments raised by Ian during the las=
t IETF meeting is available online.=20

Many thanks to Ian for raising this point.

A diff is provided below to track the changes.=20

Cheers,
Med

-----Message d'origine-----
De=A0: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de in=
ternet-drafts@ietf.org
Envoy=E9=A0: lundi 27 octobre 2014 13:59
=C0=A0: i-d-announce@ietf.org
Objet=A0: I-D Action: draft-vinapamula-softwire-dslite-prefix-binding-03.tx=
t


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


        Title           : Recommendation for Prefix Binding in the Softwire=
 DS-Lite Context
        Authors         : Suresh Vinapamula
                          Mohamed Boucadair
	Filename        : draft-vinapamula-softwire-dslite-prefix-binding-03.txt
	Pages           : 6
	Date            : 2014-10-27

Abstract:
   This document discusses issues induced by the change of the Basic
   Bridging BroadBand (B4) IPv6 address and sketches a set of
   recommendations to solve those issues.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-vinapamula-softwire-dslite-prefix-bi=
nding/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-vinapamula-softwire-dslite-prefix-binding-=
03

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


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

