
From nobody Thu Jun  2 11:09:18 2016
Return-Path: <touch@isi.edu>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF6A312B04C; Thu,  2 Jun 2016 11:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 068xYN7sL5jT; Thu,  2 Jun 2016 11:09:06 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 111AC12B022; Thu,  2 Jun 2016 11:09:06 -0700 (PDT)
Received: from [128.9.184.178] ([128.9.184.178]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u52I8JFa001915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 2 Jun 2016 11:08:21 -0700 (PDT)
To: otroan@employees.org, Xuxiaohu <xuxiaohu@huawei.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <57507611.5010801@isi.edu>
Date: Thu, 2 Jun 2016 11:08:17 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org>
Content-Type: text/plain; charset=windows-1252
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/KsEYrCr5J7l1eXFRgO6HI7Eu7D0>
Cc: Softwires WG <softwires@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 02 Jun 2016 18:09:08 -0000

On 5/27/2016 3:50 AM, otroan@employees.org wrote:
> It is not possible to implement reassembly complying with IETF RFCs.

a) ATM does this at ridiculously high fragment rates. Granted IP frags
can come out of order, but the fragments are generally much larger.

b) What is the alternative, given we have minimum MTU requirements?

If you're limiting yourself to IPv4 payloads where DF=0, sure, there
there is an alternative. But you've just disabled IPv6 and IPv4 with DF=1.

I.e., it's not possible to NOT implement this and comply with IETF RFCs.

Joe




From nobody Thu Jun  2 14:17:06 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E87C212D8AA; Thu,  2 Jun 2016 14:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 LbeKeLPLCmaK; Thu,  2 Jun 2016 14:17:00 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 9A6DD12D8A2; Thu,  2 Jun 2016 14:17:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u52LHBJa011253; Thu, 2 Jun 2016 14:17:11 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (xch15-05-05.nw.nos.boeing.com [137.137.100.80]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u52LH6TG011226 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 2 Jun 2016 14:17:06 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) by XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 2 Jun 2016 14:16:53 -0700
Received: from XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) by XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) with mapi id 15.00.1178.000;  Thu, 2 Jun 2016 14:16:53 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, "otroan@employees.org" <otroan@employees.org>,  Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [Int-area] [nvo3] [Softwires] Is it feasible to perform fragmentation on UDP encapsulated packets.
Thread-Index: AQHRvPnkfjHsPaf//UOpMMLUhxA5mJ/Wra5A
Date: Thu, 2 Jun 2016 21:16:53 +0000
Message-ID: <d8b48fc193e644fe91c4e3db10eed3ed@XCH15-05-05.nw.nos.boeing.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org> <57507611.5010801@isi.edu>
In-Reply-To: <57507611.5010801@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.137.12.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/oRTFfsLf5Imq4nCAsYuytMhw670>
Cc: Softwires WG <softwires@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [Int-area] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 02 Jun 2016 21:17:03 -0000

Agree with Joe, and also just to mention that RFC4459 discusses tunnel MTU
and fragmentation considerations.

Thanks - Fred

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Joe Touch
> Sent: Thursday, June 02, 2016 11:08 AM
> To: otroan@employees.org; Xuxiaohu <xuxiaohu@huawei.com>
> Cc: Softwires WG <softwires@ietf.org>; nvo3@ietf.org; int-area@ietf.org; =
lisp@ietf.org; tsvwg@ietf.org
> Subject: Re: [Int-area] [nvo3] [Softwires] Is it feasible to perform frag=
mentation on UDP encapsulated packets.
>=20
>=20
>=20
> On 5/27/2016 3:50 AM, otroan@employees.org wrote:
> > It is not possible to implement reassembly complying with IETF RFCs.
>=20
> a) ATM does this at ridiculously high fragment rates. Granted IP frags
> can come out of order, but the fragments are generally much larger.
>=20
> b) What is the alternative, given we have minimum MTU requirements?
>=20
> If you're limiting yourself to IPv4 payloads where DF=3D0, sure, there
> there is an alternative. But you've just disabled IPv6 and IPv4 with DF=
=3D1.
>=20
> I.e., it's not possible to NOT implement this and comply with IETF RFCs.
>=20
> Joe
>=20
>=20
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area



From nobody Thu Jun  2 19:54:07 2016
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5465912D131; Thu,  2 Jun 2016 19:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 B7Jyu9rhZXhE; Thu,  2 Jun 2016 19:53:49 -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 741A9128874; Thu,  2 Jun 2016 19:53:46 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLH32864; Fri, 03 Jun 2016 02:53:44 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 3 Jun 2016 03:53:43 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.169]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Fri, 3 Jun 2016 10:53:38 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Joe Touch <touch@isi.edu>, "otroan@employees.org" <otroan@employees.org>
Thread-Topic: [nvo3] [Softwires] Is it feasible to perform fragmentation on UDP encapsulated packets.
Thread-Index: AQHRvPncHcsWng18N0qPKCUQaW4bNp/W96xA
Date: Fri, 3 Jun 2016 02:53:37 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B2A4@NKGEML515-MBS.china.huawei.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org> <57507611.5010801@isi.edu>
In-Reply-To: <57507611.5010801@isi.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.5750F138.01B3, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.5.169, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: b6ae068aa12793195ecad703a67f441c
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/t3VNTVaG2a_6dO_El49F_Oz6qeU>
Cc: Softwires WG <softwires@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 02:53:52 -0000

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Friday, June 03, 2016 2:08 AM
> To: otroan@employees.org; Xuxiaohu
> Cc: Softwires WG; nvo3@ietf.org; int-area@ietf.org; lisp@ietf.org;
> tsvwg@ietf.org
> Subject: Re: [nvo3] [Softwires] Is it feasible to perform fragmentation o=
n UDP
> encapsulated packets.
>=20
>=20
>=20
> On 5/27/2016 3:50 AM, otroan@employees.org wrote:
> > It is not possible to implement reassembly complying with IETF RFCs.
>=20
> a) ATM does this at ridiculously high fragment rates. Granted IP frags ca=
n come
> out of order, but the fragments are generally much larger.

As pointed in RFC4459,

     "At the time of reassembly, all the information (i.e., all the
      fragments) is normally not available; when the first fragment
      arrives to be reassembled, a buffer of the maximum possible size
      may have to be allocated because the total length of the
      reassembled datagram is not known at that time. Furthermore, as
      fragments might get lost, or be reordered or delayed, the
      reassembly engine has to wait with the partial packet for some
      time (e.g., 60 seconds [9]).  When this would have to be done at
      the line rate, with, for example 10 Gbit/s speed, the length of
      the buffers that reassembly might require would be prohibitive. "

Have you heard the wide adoption of 622M (STM-1) beyond ATM interfaces betw=
een ATM switches in the previous ATM networks? If not, the highest non-ATM =
interface in the past ATM networks was the FE interface which is 100M bps (=
around the year of 2000), If I remembered it correctly. Furthermore, have y=
ou heard the reordering issue with ATM cells? If no, that means once an ATM=
 cell of a given ALL PDU gets lost, all the received ATM cells of that AAL =
PDU would be dropped and therefore the reassembly buffer for that AAL datag=
ram would be released. In other words, there is no need to wait for the los=
t or reordered fragment for a certain period of time before releasing the r=
eassembly buffer. Such behavior is not possible for IP fragmentation and re=
assembly. Last but not least, there is no need to assign a reassembly buffe=
r per AAL PDU (as opposed to per IP datagram in the IP fragmentation and re=
assembly case), instead, only one reassembly buffer per VC since all cells =
within a given VC would be received in order. Since the SAR is only needed =
on the edge of the ATM networks, the number of VCs is very limited. In a wo=
rd, there are significant differences between IP fragmentation and ATM SAR.=
=20

Best regards,
Xiaohu

> b) What is the alternative, given we have minimum MTU requirements?
>=20
> If you're limiting yourself to IPv4 payloads where DF=3D0, sure, there th=
ere is an
> alternative. But you've just disabled IPv6 and IPv4 with DF=3D1.
>=20
> I.e., it's not possible to NOT implement this and comply with IETF RFCs.
>=20
> Joe
>=20
>=20


From nobody Thu Jun  2 21:35:12 2016
Return-Path: <touch@isi.edu>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3854B12D1A0; Thu,  2 Jun 2016 21:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 a3Tat0PeYypF; Thu,  2 Jun 2016 21:34:55 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB5E312D15C; Thu,  2 Jun 2016 21:34:55 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u534YTp3015947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 2 Jun 2016 21:34:31 -0700 (PDT)
To: Xuxiaohu <xuxiaohu@huawei.com>, "otroan@employees.org" <otroan@employees.org>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org> <57507611.5010801@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B2A4@NKGEML515-MBS.china.huawei.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <575108D3.3010506@isi.edu>
Date: Thu, 2 Jun 2016 21:34:27 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B2A4@NKGEML515-MBS.china.huawei.com>
Content-Type: text/plain; charset=windows-1252
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/4prAyGPBz1W6POqPBqOBwXah20Y>
Cc: Softwires WG <softwires@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 04:34:57 -0000

On 6/2/2016 7:53 PM, Xuxiaohu wrote:
>
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Friday, June 03, 2016 2:08 AM
>> To: otroan@employees.org; Xuxiaohu
>> Cc: Softwires WG; nvo3@ietf.org; int-area@ietf.org; lisp@ietf.org;
>> tsvwg@ietf.org
>> Subject: Re: [nvo3] [Softwires] Is it feasible to perform fragmentation on UDP
>> encapsulated packets.
>>
>>
>>
>> On 5/27/2016 3:50 AM, otroan@employees.org wrote:
>>> It is not possible to implement reassembly complying with IETF RFCs.
>> a) ATM does this at ridiculously high fragment rates. Granted IP frags can come
>> out of order, but the fragments are generally much larger.
> As pointed in RFC4459,
>
>      "At the time of reassembly, all the information (i.e., all the
>       fragments) is normally not available; when the first fragment
>       arrives to be reassembled, a buffer of the maximum possible size
>       may have to be allocated because the total length of the
>       reassembled datagram is not known at that time. Furthermore, as
>       fragments might get lost, or be reordered or delayed, the
>       reassembly engine has to wait with the partial packet for some
>       time (e.g., 60 seconds [9]).  When this would have to be done at
>       the line rate, with, for example 10 Gbit/s speed, the length of
>       the buffers that reassembly might require would be prohibitive. "

Yes, but the alternative of declaring that you don't reassemble has a
cost in terms of dropped segments too.

Taking that drop into account, buffering for a smaller amount of
potential reordering and accounting for reasonable reassembly sizes (for
IPv6, the smallest "max" that's required is 1500) need not be prohibitive.

> Have you heard the wide adoption of 622M (STM-1) beyond ATM interfaces between ATM switches in the previous ATM networks? If not, the highest non-ATM interface in the past ATM networks was the FE interface which is 100M bps (around the year of 2000), If I remembered it correctly. 

OC12 ATM NICs were commonly available in 1998. That was back when
ethernet was pushing 100M and the only other near-gigabit tech was
Myricom (a spin-off of USC/ISI and Caltech). I.e., with the tech
available at that time,  600Mbps SAR was possible.

> Furthermore, have you heard the reordering issue with ATM cells? If no, that means once an ATM cell of a given ALL PDU gets lost, all the received ATM cells of that AAL PDU would be dropped and therefore the reassembly buffer for that AAL datagram would be released. In other words, there is no need to wait for the lost or reordered fragment for a certain period of time before releasing the reassembly buffer.
Reordered no, but just because they arrive in order does not mean they
are required to arrive *adjacent*. The same requirement applies in terms
of needing reassembly buffers for a number of interleaved segments.

>  Such behavior is not possible for IP fragmentation and reassembly. Last but not least, there is no need to assign a reassembly buffer per AAL PDU (as opposed to per IP datagram in the IP fragmentation and reassembly case), instead, only one reassembly buffer per VC since all cells within a given VC would be received in order. Since the SAR is only needed on the edge of the ATM networks, the number of VCs is very limited. 
You could easily decide to allocate a fixed number of reassembly buffers
per IP flow to conserve resources too. The amount of reordering,
together with the number of flows supported would determine your ability
to avoid packet drops -- but recall that drops at high load are not
unusual for IP.

Joe


From nobody Fri Jun  3 00:38:54 2016
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB7512D670; Fri,  3 Jun 2016 00:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 R3Qiwwov-_9K; Fri,  3 Jun 2016 00:38:49 -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 16A9012D0DE; Fri,  3 Jun 2016 00:38:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLH62853; Fri, 03 Jun 2016 07:38:43 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 3 Jun 2016 08:38:42 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.169]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Fri, 3 Jun 2016 15:38:40 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Joe Touch <touch@isi.edu>, "otroan@employees.org" <otroan@employees.org>
Thread-Topic: [nvo3] [Softwires] Is it feasible to perform fragmentation on UDP encapsulated packets.
Thread-Index: AQHRvPncHcsWng18N0qPKCUQaW4bNp/W96xA//+qsICAAKCTIA==
Date: Fri, 3 Jun 2016 07:38:40 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B37B@NKGEML515-MBS.china.huawei.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org> <57507611.5010801@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B2A4@NKGEML515-MBS.china.huawei.com> <575108D3.3010506@isi.edu>
In-Reply-To: <575108D3.3010506@isi.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.57513404.004D, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.5.169, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: b6ae068aa12793195ecad703a67f441c
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/8fmXbvE7_UKo7VDFZIc1fAbCFc8>
Cc: Softwires WG <softwires@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 07:38:51 -0000

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Friday, June 03, 2016 12:34 PM
> To: Xuxiaohu; otroan@employees.org
> Cc: Softwires WG; nvo3@ietf.org; int-area@ietf.org; lisp@ietf.org;
> tsvwg@ietf.org
> Subject: Re: [nvo3] [Softwires] Is it feasible to perform fragmentation o=
n UDP
> encapsulated packets.
>=20
>=20
>=20
> On 6/2/2016 7:53 PM, Xuxiaohu wrote:
> >
> >> -----Original Message-----
> >> From: Joe Touch [mailto:touch@isi.edu]
> >> Sent: Friday, June 03, 2016 2:08 AM
> >> To: otroan@employees.org; Xuxiaohu
> >> Cc: Softwires WG; nvo3@ietf.org; int-area@ietf.org; lisp@ietf.org;
> >> tsvwg@ietf.org
> >> Subject: Re: [nvo3] [Softwires] Is it feasible to perform
> >> fragmentation on UDP encapsulated packets.
> >>
> >>
> >>
> >> On 5/27/2016 3:50 AM, otroan@employees.org wrote:
> >>> It is not possible to implement reassembly complying with IETF RFCs.
> >> a) ATM does this at ridiculously high fragment rates. Granted IP
> >> frags can come out of order, but the fragments are generally much larg=
er.
> > As pointed in RFC4459,
> >
> >      "At the time of reassembly, all the information (i.e., all the
> >       fragments) is normally not available; when the first fragment
> >       arrives to be reassembled, a buffer of the maximum possible size
> >       may have to be allocated because the total length of the
> >       reassembled datagram is not known at that time. Furthermore, as
> >       fragments might get lost, or be reordered or delayed, the
> >       reassembly engine has to wait with the partial packet for some
> >       time (e.g., 60 seconds [9]).  When this would have to be done at
> >       the line rate, with, for example 10 Gbit/s speed, the length of
> >       the buffers that reassembly might require would be prohibitive. "
>=20
> Yes, but the alternative of declaring that you don't reassemble has a cos=
t in
> terms of dropped segments too.

The alternative is to configure the MTU of the core large enough to accommo=
date the added encapsulation header. This is a feasible and proven approach=
 in well-managed SP networks. No packet loss and no forwarding performance =
degradation.

> Taking that drop into account, buffering for a smaller amount of potentia=
l
> reordering and accounting for reasonable reassembly sizes (for IPv6, the
> smallest "max" that's required is 1500) need not be prohibitive.

In the IPv6-in-IPv4 Software network case, assume the MTU of the core is no=
t large enough than 1280+20, all the IPv6 traffic across the tunnels would =
have to be fragmented and then reassembled. Not a small amount.

> > Have you heard the wide adoption of 622M (STM-1) beyond ATM interfaces
> between ATM switches in the previous ATM networks? If not, the highest
> non-ATM interface in the past ATM networks was the FE interface which is =
100M
> bps (around the year of 2000), If I remembered it correctly.
>=20
> OC12 ATM NICs were commonly available in 1998. That was back when

Sorry, there was a spelling mistake ( s/STM-1/STM-4).

OC12/STM-4=3D622M. My question is have you heard the wide adoption of 622M =
(STM-4) BEYOND ATM interfaces (e.g., STM-16/OC48) at that time?

> ethernet was pushing 100M and the only other near-gigabit tech was Myrico=
m
> (a spin-off of USC/ISI and Caltech). I.e., with the tech available at tha=
t time,
> 600Mbps SAR was possible.

Was that 600Mbps SAR capability proved in real networks? And for what servi=
ce?

> > Furthermore, have you heard the reordering issue with ATM cells? If no,=
 that
> means once an ATM cell of a given ALL PDU gets lost, all the received ATM=
 cells
> of that AAL PDU would be dropped and therefore the reassembly buffer for =
that
> AAL datagram would be released. In other words, there is no need to wait =
for
> the lost or reordered fragment for a certain period of time before releas=
ing the
> reassembly buffer.
> Reordered no, but just because they arrive in order does not mean they ar=
e
> required to arrive *adjacent*. The same requirement applies in terms of
> needing reassembly buffers for a number of interleaved segments.

However, the reassembly buffer requirement is limited due to the fact that =
only one buffer is needed per VC and the total number of VCs is not large o=
n the edge of ATM networks. In contrast, the number of IP flows is uncontro=
llable.

> >  Such behavior is not possible for IP fragmentation and reassembly. Las=
t but
> not least, there is no need to assign a reassembly buffer per AAL PDU (as
> opposed to per IP datagram in the IP fragmentation and reassembly case),
> instead, only one reassembly buffer per VC since all cells within a given=
 VC would
> be received in order. Since the SAR is only needed on the edge of the ATM
> networks, the number of VCs is very limited.
> You could easily decide to allocate a fixed number of reassembly buffers =
per IP
> flow to conserve resources too. The amount of reordering, together with t=
he

What about in the DDoS attack case? Do you believe that SPs would allow the=
 existence of that obvious DDoS attack risk in their networks and afford th=
e significant forwarding performance degradation? especially when there has=
 been a feasible and proven solution to the MTU issue (i.e., configure the =
MTU of the core large enough)?

Best regards,
Xiaohu

> number of flows supported would determine your ability to avoid packet dr=
ops
> -- but recall that drops at high load are not unusual for IP.
>=20
> Joe


From nobody Fri Jun  3 05:48:22 2016
Return-Path: <despres.remi@laposte.net>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3325E12D146; Fri,  3 Jun 2016 05:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.617
X-Spam-Level: 
X-Spam-Status: No, score=-2.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 W_zYmls8QhWz; Fri,  3 Jun 2016 05:48:16 -0700 (PDT)
Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [212.27.42.3]) (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 4343612D127; Fri,  3 Jun 2016 05:48:15 -0700 (PDT)
Received: from [192.168.0.29] (unknown [78.193.136.169]) by smtp3-g21.free.fr (Postfix) with ESMTPS id 4646A13F6B0; Fri,  3 Jun 2016 12:50:21 +0200 (CEST)
Content-Type: multipart/alternative; boundary=Apple-Mail-A1535E92-481B-4573-B233-780626C5AB2B
Mime-Version: 1.0 (1.0)
From: =?utf-8?Q?R=C3=A9mi_Despr=C3=A9s?= <despres.remi@laposte.net>
X-Mailer: iPad Mail (13E238)
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B37B@NKGEML515-MBS.china.huawei.com>
Date: Fri, 3 Jun 2016 14:48:04 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <7C3B0012-D5B9-4857-BE5E-9579265C76DF@laposte.net>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org> <57507611.5010801@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B2A4@NKGEML515-MBS.china.huawei.com> <575108D3.3010506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B37B@NKGEML515-MBS.china.huawei.com>
To: Softwires WG <softwires@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/0FTtZkmefedtrs8EMK5UAXQtrbo>
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 12:48:20 -0000

--Apple-Mail-A1535E92-481B-4573-B233-780626C5AB2B
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable


> 2016-06-03 09:38, Xuxiaohu <xuxiaohu@huawei.com> :
>=20
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Friday, June 03, 2016 12:34 PM
...
>> Yes, but the alternative of declaring that you don't reassemble has a cos=
t in
>> terms of dropped segments too.
>=20
> The alternative is to configure the MTU of the core large enough to accomm=
odate the added encapsulation header. This is a feasible and proven approach=
 in well-managed SP networks. No packet loss and no forwarding performance d=
egradation.

Just for information on this subject, an earlier analysis is a available in h=
ttps://tools.ietf.org/html/rfc6751#section-6.4.
(No plan to participate again in IETF technical debates.)

Regards to all,
RD

--Apple-Mail-A1535E92-481B-4573-B233-780626C5AB2B
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><br></div><div>2016-06-03 09:38, Xuxia=
ohu &lt;<a href=3D"mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>&gt; :=
<br></div><blockquote type=3D"cite"><span></span><br><blockquote type=3D"cit=
e"><span>-----Original Message-----</span><br></blockquote><blockquote type=3D=
"cite"><span>From: Joe Touch [<a href=3D"mailto:touch@isi.edu">mailto:touch@=
isi.edu</a>]</span><br></blockquote><blockquote type=3D"cite"><span>Sent: Fri=
day, June 03, 2016 12:34 PM</span></blockquote></blockquote>...<br><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><span><=
/span></blockquote></blockquote><blockquote type=3D"cite"><span>Yes, but the=
 alternative of declaring that you don't reassemble has a cost in</span><br>=
</blockquote><blockquote type=3D"cite"><span>terms of dropped segments too.<=
/span><br></blockquote><span></span><br><span>The alternative is to configur=
e the MTU of the core large enough to accommodate the added encapsulation he=
ader. This is a feasible and proven approach in well-managed SP networks. No=
 packet loss and no forwarding performance degradation.</span><br></blockquo=
te><br><div>Just <b>for information</b> on this subject, an earlier analysis=
 is a available in&nbsp;<b><a href=3D"https://tools.ietf.org/html/rfc6751#se=
ction-6">https://tools.ietf.org/html/rfc6751#section-6</a>.</b>4.</div><div>=
(No plan to participate again in IETF technical debates.)</div><div><br></di=
v><div>Regards to all,</div><div>RD<br><blockquote type=3D"cite"><div><span>=
</span></div></blockquote></div></body></html>=

--Apple-Mail-A1535E92-481B-4573-B233-780626C5AB2B--


From nobody Fri Jun  3 09:27:22 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0043112D702; Fri,  3 Jun 2016 09:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Oy5WGvqFclwk; Fri,  3 Jun 2016 09:27:13 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 64A6F12D5AC; Fri,  3 Jun 2016 09:27:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u53GRODW011554; Fri, 3 Jun 2016 09:27:25 -0700
Received: from XCH15-05-06.nw.nos.boeing.com (xch15-05-06.nw.nos.boeing.com [137.137.100.84]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u53GRJlP011406 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 3 Jun 2016 09:27:19 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) by XCH15-05-06.nw.nos.boeing.com (2002:8989:6454::8989:6454) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 3 Jun 2016 09:27:06 -0700
Received: from XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) by XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) with mapi id 15.00.1178.000;  Fri, 3 Jun 2016 09:27:06 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, Joe Touch <touch@isi.edu>, "otroan@employees.org" <otroan@employees.org>
Thread-Topic: [nvo3] [Softwires] Is it feasible to perform fragmentation on UDP encapsulated packets.
Thread-Index: AQHRvWr/d3+tgL34oUSVk+7sP6lEoZ/X6QAw
Date: Fri, 3 Jun 2016 16:27:06 +0000
Message-ID: <528400d44d934332bf7382e062f13d73@XCH15-05-05.nw.nos.boeing.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org> <57507611.5010801@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B2A4@NKGEML515-MBS.china.huawei.com> <575108D3.3010506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B37B@NKGEML515-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B37B@NKGEML515-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.137.12.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/LsjtrqcYEMsWlUZGSnuxvldrvw8>
Cc: Softwires WG <softwires@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 16:27:16 -0000

> The alternative is to configure the MTU of the core large enough to accom=
modate the added encapsulation header.

But what if you can't do that? All it takes is one link with a small and/or
misconfigured MTU...

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Xuxiaohu
> Sent: Friday, June 03, 2016 12:39 AM
> To: Joe Touch <touch@isi.edu>; otroan@employees.org
> Cc: Softwires WG <softwires@ietf.org>; nvo3@ietf.org; int-area@ietf.org; =
lisp@ietf.org; tsvwg@ietf.org
> Subject: Re: [Int-area] [nvo3] [Softwires] Is it feasible to perform frag=
mentation on UDP encapsulated packets.
>=20
>=20
>=20
> > -----Original Message-----
> > From: Joe Touch [mailto:touch@isi.edu]
> > Sent: Friday, June 03, 2016 12:34 PM
> > To: Xuxiaohu; otroan@employees.org
> > Cc: Softwires WG; nvo3@ietf.org; int-area@ietf.org; lisp@ietf.org;
> > tsvwg@ietf.org
> > Subject: Re: [nvo3] [Softwires] Is it feasible to perform fragmentation=
 on UDP
> > encapsulated packets.
> >
> >
> >
> > On 6/2/2016 7:53 PM, Xuxiaohu wrote:
> > >
> > >> -----Original Message-----
> > >> From: Joe Touch [mailto:touch@isi.edu]
> > >> Sent: Friday, June 03, 2016 2:08 AM
> > >> To: otroan@employees.org; Xuxiaohu
> > >> Cc: Softwires WG; nvo3@ietf.org; int-area@ietf.org; lisp@ietf.org;
> > >> tsvwg@ietf.org
> > >> Subject: Re: [nvo3] [Softwires] Is it feasible to perform
> > >> fragmentation on UDP encapsulated packets.
> > >>
> > >>
> > >>
> > >> On 5/27/2016 3:50 AM, otroan@employees.org wrote:
> > >>> It is not possible to implement reassembly complying with IETF RFCs=
.
> > >> a) ATM does this at ridiculously high fragment rates. Granted IP
> > >> frags can come out of order, but the fragments are generally much la=
rger.
> > > As pointed in RFC4459,
> > >
> > >      "At the time of reassembly, all the information (i.e., all the
> > >       fragments) is normally not available; when the first fragment
> > >       arrives to be reassembled, a buffer of the maximum possible siz=
e
> > >       may have to be allocated because the total length of the
> > >       reassembled datagram is not known at that time. Furthermore, as
> > >       fragments might get lost, or be reordered or delayed, the
> > >       reassembly engine has to wait with the partial packet for some
> > >       time (e.g., 60 seconds [9]).  When this would have to be done a=
t
> > >       the line rate, with, for example 10 Gbit/s speed, the length of
> > >       the buffers that reassembly might require would be prohibitive.=
 "
> >
> > Yes, but the alternative of declaring that you don't reassemble has a c=
ost in
> > terms of dropped segments too.
>=20
> The alternative is to configure the MTU of the core large enough to accom=
modate the added encapsulation header. This is a feasible
> and proven approach in well-managed SP networks. No packet loss and no fo=
rwarding performance degradation.
>=20
> > Taking that drop into account, buffering for a smaller amount of potent=
ial
> > reordering and accounting for reasonable reassembly sizes (for IPv6, th=
e
> > smallest "max" that's required is 1500) need not be prohibitive.
>=20
> In the IPv6-in-IPv4 Software network case, assume the MTU of the core is =
not large enough than 1280+20, all the IPv6 traffic across
> the tunnels would have to be fragmented and then reassembled. Not a small=
 amount.
>=20
> > > Have you heard the wide adoption of 622M (STM-1) beyond ATM interface=
s
> > between ATM switches in the previous ATM networks? If not, the highest
> > non-ATM interface in the past ATM networks was the FE interface which i=
s 100M
> > bps (around the year of 2000), If I remembered it correctly.
> >
> > OC12 ATM NICs were commonly available in 1998. That was back when
>=20
> Sorry, there was a spelling mistake ( s/STM-1/STM-4).
>=20
> OC12/STM-4=3D622M. My question is have you heard the wide adoption of 622=
M (STM-4) BEYOND ATM interfaces (e.g., STM-16/OC48)
> at that time?
>=20
> > ethernet was pushing 100M and the only other near-gigabit tech was Myri=
com
> > (a spin-off of USC/ISI and Caltech). I.e., with the tech available at t=
hat time,
> > 600Mbps SAR was possible.
>=20
> Was that 600Mbps SAR capability proved in real networks? And for what ser=
vice?
>=20
> > > Furthermore, have you heard the reordering issue with ATM cells? If n=
o, that
> > means once an ATM cell of a given ALL PDU gets lost, all the received A=
TM cells
> > of that AAL PDU would be dropped and therefore the reassembly buffer fo=
r that
> > AAL datagram would be released. In other words, there is no need to wai=
t for
> > the lost or reordered fragment for a certain period of time before rele=
asing the
> > reassembly buffer.
> > Reordered no, but just because they arrive in order does not mean they =
are
> > required to arrive *adjacent*. The same requirement applies in terms of
> > needing reassembly buffers for a number of interleaved segments.
>=20
> However, the reassembly buffer requirement is limited due to the fact tha=
t only one buffer is needed per VC and the total number of
> VCs is not large on the edge of ATM networks. In contrast, the number of =
IP flows is uncontrollable.
>=20
> > >  Such behavior is not possible for IP fragmentation and reassembly. L=
ast but
> > not least, there is no need to assign a reassembly buffer per AAL PDU (=
as
> > opposed to per IP datagram in the IP fragmentation and reassembly case)=
,
> > instead, only one reassembly buffer per VC since all cells within a giv=
en VC would
> > be received in order. Since the SAR is only needed on the edge of the A=
TM
> > networks, the number of VCs is very limited.
> > You could easily decide to allocate a fixed number of reassembly buffer=
s per IP
> > flow to conserve resources too. The amount of reordering, together with=
 the
>=20
> What about in the DDoS attack case? Do you believe that SPs would allow t=
he existence of that obvious DDoS attack risk in their
> networks and afford the significant forwarding performance degradation? e=
specially when there has been a feasible and proven
> solution to the MTU issue (i.e., configure the MTU of the core large enou=
gh)?
>=20
> Best regards,
> Xiaohu
>=20
> > number of flows supported would determine your ability to avoid packet =
drops
> > -- but recall that drops at high load are not unusual for IP.
> >
> > Joe
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area



From nobody Fri Jun  3 09:45:26 2016
Return-Path: <tom@herbertland.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DF412D72D for <softwires@ietfa.amsl.com>; Fri,  3 Jun 2016 09:44:57 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 dvtBor1mPoxm for <softwires@ietfa.amsl.com>; Fri,  3 Jun 2016 09:44:56 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D021C12D727 for <softwires@ietf.org>; Fri,  3 Jun 2016 09:44:41 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id z123so2937557itg.0 for <softwires@ietf.org>; Fri, 03 Jun 2016 09:44:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=diFCe03zfS80dDcGfVJMpj9HUrKCetL0y9rfjiTu5PE=; b=GsWtyA+LbeeB5aqaNW1fel3aGmlKNMT/rj0Mi6+/W2cQ0QdDqGqvVLk0373lS/PG3b ZL/KK4J5UFvbbtQcesm0zbudw/R3WKA7SLNvX47V4tVhks0DzwkvP8Ksp/yNLDKuOBik lwPcZkpXFxrqGfYOpR1xPtEs4+Q67tdbI9AxnPmzSA2woS84atbKeTmhplU9BE04TpP8 NE8PlgN8kglUIJcW6kjpxVFsI5CuepdGlhHHODXg+3ihKBNfHDdIkS4aTDQZrEbpub0l mfm1Q6RRY2WJdlaBTAIX68CqTq40Oj0p7HFVdyKuIrUZ4+VVLWqw8wPJjQiOfImq1FO3 6twg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=diFCe03zfS80dDcGfVJMpj9HUrKCetL0y9rfjiTu5PE=; b=JsCgBucgpRKH4nAgKp0+ppLzYQ5KJb9jJMa6C9Rp2vSx75L7YyHG8FL0hPqYVsXEsU pMew4AQjsfAFlCjRy6i1nJZP+dGdN1Gxf4Y/oPJZkC3H6ZL+XnWChchzWHxbhojm13kN KZrDox23/J717JHM9YkW/nXRbJ82zrxdTgcMGmqnpMgXffQwdwHJRo6M8Pk4SLD0P9s2 yZREezpC6oqvi79pNlpcQXB4QXE7EpeAGDQ1JYFq/XG7TMBy8vPagD9TdtrrXG4kFYAb lCyiDJJhDsy4NjLl1jawoqhdlxn7f0i3gYZd876to4qHJwxsPDhvggaMHkyHYYpldfum OxQA==
X-Gm-Message-State: ALyK8tI6tXFwib+xpCFZq4kfmsF9wCkAlVQGga4cpOndXsqW8WOzP5clI0zjKcNxXJr3baLQUFIyJJ7dt1ui2g==
MIME-Version: 1.0
X-Received: by 10.36.66.68 with SMTP id i65mr676252itb.91.1464972281013; Fri, 03 Jun 2016 09:44:41 -0700 (PDT)
Received: by 10.107.11.20 with HTTP; Fri, 3 Jun 2016 09:44:40 -0700 (PDT)
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B37B@NKGEML515-MBS.china.huawei.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org> <57507611.5010801@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B2A4@NKGEML515-MBS.china.huawei.com> <575108D3.3010506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B37B@NKGEML515-MBS.china.huawei.com>
Date: Fri, 3 Jun 2016 09:44:40 -0700
Message-ID: <CALx6S34fodntzDOagKOsfey9hfAZpsAS_xg6Rjw767B=gacvVQ@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/Jx0bxI6QYvQS4ZvkwOIAJh1hP50>
Cc: "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, Joe Touch <touch@isi.edu>, "nvo3@ietf.org" <nvo3@ietf.org>, Softwires WG <softwires@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [Int-area] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 16:44:58 -0000

On Fri, Jun 3, 2016 at 12:38 AM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>
>
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Friday, June 03, 2016 12:34 PM
>> To: Xuxiaohu; otroan@employees.org
>> Cc: Softwires WG; nvo3@ietf.org; int-area@ietf.org; lisp@ietf.org;
>> tsvwg@ietf.org
>> Subject: Re: [nvo3] [Softwires] Is it feasible to perform fragmentation =
on UDP
>> encapsulated packets.
>>
>>
>>
>> On 6/2/2016 7:53 PM, Xuxiaohu wrote:
>> >
>> >> -----Original Message-----
>> >> From: Joe Touch [mailto:touch@isi.edu]
>> >> Sent: Friday, June 03, 2016 2:08 AM
>> >> To: otroan@employees.org; Xuxiaohu
>> >> Cc: Softwires WG; nvo3@ietf.org; int-area@ietf.org; lisp@ietf.org;
>> >> tsvwg@ietf.org
>> >> Subject: Re: [nvo3] [Softwires] Is it feasible to perform
>> >> fragmentation on UDP encapsulated packets.
>> >>
>> >>
>> >>
>> >> On 5/27/2016 3:50 AM, otroan@employees.org wrote:
>> >>> It is not possible to implement reassembly complying with IETF RFCs.
>> >> a) ATM does this at ridiculously high fragment rates. Granted IP
>> >> frags can come out of order, but the fragments are generally much lar=
ger.
>> > As pointed in RFC4459,
>> >
>> >      "At the time of reassembly, all the information (i.e., all the
>> >       fragments) is normally not available; when the first fragment
>> >       arrives to be reassembled, a buffer of the maximum possible size
>> >       may have to be allocated because the total length of the
>> >       reassembled datagram is not known at that time. Furthermore, as
>> >       fragments might get lost, or be reordered or delayed, the
>> >       reassembly engine has to wait with the partial packet for some
>> >       time (e.g., 60 seconds [9]).  When this would have to be done at
>> >       the line rate, with, for example 10 Gbit/s speed, the length of
>> >       the buffers that reassembly might require would be prohibitive. =
"
>>
>> Yes, but the alternative of declaring that you don't reassemble has a co=
st in
>> terms of dropped segments too.
>
> The alternative is to configure the MTU of the core large enough to accom=
modate the added encapsulation header. This is a feasible and proven approa=
ch in well-managed SP networks. No packet loss and no forwarding performanc=
e degradation.
>
>> Taking that drop into account, buffering for a smaller amount of potenti=
al
>> reordering and accounting for reasonable reassembly sizes (for IPv6, the
>> smallest "max" that's required is 1500) need not be prohibitive.
>
> In the IPv6-in-IPv4 Software network case, assume the MTU of the core is =
not large enough than 1280+20, all the IPv6 traffic across the tunnels woul=
d have to be fragmented and then reassembled. Not a small amount.
>
>> > Have you heard the wide adoption of 622M (STM-1) beyond ATM interfaces
>> between ATM switches in the previous ATM networks? If not, the highest
>> non-ATM interface in the past ATM networks was the FE interface which is=
 100M
>> bps (around the year of 2000), If I remembered it correctly.
>>
>> OC12 ATM NICs were commonly available in 1998. That was back when
>
> Sorry, there was a spelling mistake ( s/STM-1/STM-4).
>
> OC12/STM-4=3D622M. My question is have you heard the wide adoption of 622=
M (STM-4) BEYOND ATM interfaces (e.g., STM-16/OC48) at that time?
>
>> ethernet was pushing 100M and the only other near-gigabit tech was Myric=
om
>> (a spin-off of USC/ISI and Caltech). I.e., with the tech available at th=
at time,
>> 600Mbps SAR was possible.
>
> Was that 600Mbps SAR capability proved in real networks? And for what ser=
vice?
>
>> > Furthermore, have you heard the reordering issue with ATM cells? If no=
, that
>> means once an ATM cell of a given ALL PDU gets lost, all the received AT=
M cells
>> of that AAL PDU would be dropped and therefore the reassembly buffer for=
 that
>> AAL datagram would be released. In other words, there is no need to wait=
 for
>> the lost or reordered fragment for a certain period of time before relea=
sing the
>> reassembly buffer.
>> Reordered no, but just because they arrive in order does not mean they a=
re
>> required to arrive *adjacent*. The same requirement applies in terms of
>> needing reassembly buffers for a number of interleaved segments.
>
> However, the reassembly buffer requirement is limited due to the fact tha=
t only one buffer is needed per VC and the total number of VCs is not large=
 on the edge of ATM networks. In contrast, the number of IP flows is uncont=
rollable.
>
>> >  Such behavior is not possible for IP fragmentation and reassembly. La=
st but
>> not least, there is no need to assign a reassembly buffer per AAL PDU (a=
s
>> opposed to per IP datagram in the IP fragmentation and reassembly case),
>> instead, only one reassembly buffer per VC since all cells within a give=
n VC would
>> be received in order. Since the SAR is only needed on the edge of the AT=
M
>> networks, the number of VCs is very limited.
>> You could easily decide to allocate a fixed number of reassembly buffers=
 per IP
>> flow to conserve resources too. The amount of reordering, together with =
the
>
> What about in the DDoS attack case? Do you believe that SPs would allow t=
he existence of that obvious DDoS attack risk in their networks and afford =
the significant forwarding performance degradation? especially when there h=
as been a feasible and proven solution to the MTU issue (i.e., configure th=
e MTU of the core large enough)?
>
That is precisely solution #3 in RFC4459:

"Ensure that in the specific environment, the encapsulated packets
will fit in all the paths in the network, e.g., by using MTU bigger
than 1500 in the backbone used for encapsulation."

If you're able to implement this in you network that's great, but it
is not feasible in all situations and hence can't be the standard. We
may not control all the underlay networks (definitely not over the
Internet) and hence not be able to set all the MTUs large enough. Also
an MTU greater than 1500 require jumbo frames, not all networks
enabled those.

One other point, when a device sources or sinks IP packets like in
tunneling it is taking on the role of a host and so we expect host
requirements apply. For instance, routers may perform fragmentation in
IPv4, but they do not perform fragmentation for IPv6 or reassembly
(those are hosts functionalities). There has been at least one attempt
to carve out exceptions in applying host requirements to devices that
perform tunneling, that is an allowance to send a zero UDP checksum in
in IPv6. Documenting this took two RFCs and we still needed a whole
lot of description in at least GRE/UDP on requirements that to use the
non-zero checksum. I don't think standardizing exceptions in
fragmentation for tunnels would be any easier.

Tom

> Best regards,
> Xiaohu
>
>> number of flows supported would determine your ability to avoid packet d=
rops
>> -- but recall that drops at high load are not unusual for IP.
>>
>> Joe
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From nobody Mon Jun  6 13:38:23 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D1C812D90F; Mon,  6 Jun 2016 13:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 8cCpSW4nSNCq; Mon,  6 Jun 2016 13:38:14 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 DEF9C12D919; Mon,  6 Jun 2016 13:38:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u56Kc32B042972; Mon, 6 Jun 2016 13:38:03 -0700
Received: from XCH15-05-07.nw.nos.boeing.com (xch15-05-07.nw.nos.boeing.com [137.136.239.209]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u56KbxHG042832 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Mon, 6 Jun 2016 13:38:00 -0700
Received: from XCH15-05-11.nw.nos.boeing.com (2002:8988:efd5::8988:efd5) by XCH15-05-07.nw.nos.boeing.com (2002:8988:efd1::8988:efd1) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 6 Jun 2016 13:37:58 -0700
Received: from XCH15-05-11.nw.nos.boeing.com ([137.136.239.213]) by XCH15-05-11.nw.nos.boeing.com ([137.136.239.213]) with mapi id 15.00.1178.000; Mon, 6 Jun 2016 13:37:59 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Tom Herbert <tom@herbertland.com>, Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [tsvwg] [Int-area] [nvo3] [Softwires] Is it feasible to perform fragmentation on UDP encapsulated packets.
Thread-Index: AQHRvbdPveimCbx8+kiS+Bdydthih5/c6X4w
Date: Mon, 6 Jun 2016 20:37:58 +0000
Message-ID: <3d29bcbfc1f04033aee4285e4dae31f4@XCH15-05-11.nw.nos.boeing.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <8790AF6F-CCD6-43AC-A50E-957B037643F1@employees.org> <57507611.5010801@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B2A4@NKGEML515-MBS.china.huawei.com> <575108D3.3010506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55B37B@NKGEML515-MBS.china.huawei.com> <CALx6S34fodntzDOagKOsfey9hfAZpsAS_xg6Rjw767B=gacvVQ@mail.gmail.com>
In-Reply-To: <CALx6S34fodntzDOagKOsfey9hfAZpsAS_xg6Rjw767B=gacvVQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.137.12.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/9TEepAk9vVL-az9QNNaPbIBAjFg>
Cc: "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, Joe Touch <touch@isi.edu>, "nvo3@ietf.org" <nvo3@ietf.org>, Softwires WG <softwires@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [tsvwg] [Int-area] [nvo3] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 20:38:17 -0000

SGkgVG9tLA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHRzdndnIFtt
YWlsdG86dHN2d2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFRvbSBIZXJiZXJ0DQo+
IFNlbnQ6IEZyaWRheSwgSnVuZSAwMywgMjAxNiA5OjQ1IEFNDQo+IFRvOiBYdXhpYW9odSA8eHV4
aWFvaHVAaHVhd2VpLmNvbT4NCj4gQ2M6IGludC1hcmVhQGlldGYub3JnOyBsaXNwQGlldGYub3Jn
OyBKb2UgVG91Y2ggPHRvdWNoQGlzaS5lZHU+OyBudm8zQGlldGYub3JnOyBvdHJvYW5AZW1wbG95
ZWVzLm9yZzsgU29mdHdpcmVzIFdHDQo+IDxzb2Z0d2lyZXNAaWV0Zi5vcmc+OyB0c3Z3Z0BpZXRm
Lm9yZw0KPiBTdWJqZWN0OiBSZTogW3RzdndnXSBbSW50LWFyZWFdIFtudm8zXSBbU29mdHdpcmVz
XSBJcyBpdCBmZWFzaWJsZSB0byBwZXJmb3JtIGZyYWdtZW50YXRpb24gb24gVURQIGVuY2Fwc3Vs
YXRlZCBwYWNrZXRzLg0KPiANCj4gT24gRnJpLCBKdW4gMywgMjAxNiBhdCAxMjozOCBBTSwgWHV4
aWFvaHUgPHh1eGlhb2h1QGh1YXdlaS5jb20+IHdyb3RlOg0KPiA+DQo+ID4NCj4gPj4gLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogSm9lIFRvdWNoIFttYWlsdG86dG91Y2hA
aXNpLmVkdV0NCj4gPj4gU2VudDogRnJpZGF5LCBKdW5lIDAzLCAyMDE2IDEyOjM0IFBNDQo+ID4+
IFRvOiBYdXhpYW9odTsgb3Ryb2FuQGVtcGxveWVlcy5vcmcNCj4gPj4gQ2M6IFNvZnR3aXJlcyBX
RzsgbnZvM0BpZXRmLm9yZzsgaW50LWFyZWFAaWV0Zi5vcmc7IGxpc3BAaWV0Zi5vcmc7DQo+ID4+
IHRzdndnQGlldGYub3JnDQo+ID4+IFN1YmplY3Q6IFJlOiBbbnZvM10gW1NvZnR3aXJlc10gSXMg
aXQgZmVhc2libGUgdG8gcGVyZm9ybSBmcmFnbWVudGF0aW9uIG9uIFVEUA0KPiA+PiBlbmNhcHN1
bGF0ZWQgcGFja2V0cy4NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4gT24gNi8yLzIwMTYgNzo1MyBQ
TSwgWHV4aWFvaHUgd3JvdGU6DQo+ID4+ID4NCj4gPj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4gPj4gPj4gRnJvbTogSm9lIFRvdWNoIFttYWlsdG86dG91Y2hAaXNpLmVkdV0NCj4g
Pj4gPj4gU2VudDogRnJpZGF5LCBKdW5lIDAzLCAyMDE2IDI6MDggQU0NCj4gPj4gPj4gVG86IG90
cm9hbkBlbXBsb3llZXMub3JnOyBYdXhpYW9odQ0KPiA+PiA+PiBDYzogU29mdHdpcmVzIFdHOyBu
dm8zQGlldGYub3JnOyBpbnQtYXJlYUBpZXRmLm9yZzsgbGlzcEBpZXRmLm9yZzsNCj4gPj4gPj4g
dHN2d2dAaWV0Zi5vcmcNCj4gPj4gPj4gU3ViamVjdDogUmU6IFtudm8zXSBbU29mdHdpcmVzXSBJ
cyBpdCBmZWFzaWJsZSB0byBwZXJmb3JtDQo+ID4+ID4+IGZyYWdtZW50YXRpb24gb24gVURQIGVu
Y2Fwc3VsYXRlZCBwYWNrZXRzLg0KPiA+PiA+Pg0KPiA+PiA+Pg0KPiA+PiA+Pg0KPiA+PiA+PiBP
biA1LzI3LzIwMTYgMzo1MCBBTSwgb3Ryb2FuQGVtcGxveWVlcy5vcmcgd3JvdGU6DQo+ID4+ID4+
PiBJdCBpcyBub3QgcG9zc2libGUgdG8gaW1wbGVtZW50IHJlYXNzZW1ibHkgY29tcGx5aW5nIHdp
dGggSUVURiBSRkNzLg0KPiA+PiA+PiBhKSBBVE0gZG9lcyB0aGlzIGF0IHJpZGljdWxvdXNseSBo
aWdoIGZyYWdtZW50IHJhdGVzLiBHcmFudGVkIElQDQo+ID4+ID4+IGZyYWdzIGNhbiBjb21lIG91
dCBvZiBvcmRlciwgYnV0IHRoZSBmcmFnbWVudHMgYXJlIGdlbmVyYWxseSBtdWNoIGxhcmdlci4N
Cj4gPj4gPiBBcyBwb2ludGVkIGluIFJGQzQ0NTksDQo+ID4+ID4NCj4gPj4gPiAgICAgICJBdCB0
aGUgdGltZSBvZiByZWFzc2VtYmx5LCBhbGwgdGhlIGluZm9ybWF0aW9uIChpLmUuLCBhbGwgdGhl
DQo+ID4+ID4gICAgICAgZnJhZ21lbnRzKSBpcyBub3JtYWxseSBub3QgYXZhaWxhYmxlOyB3aGVu
IHRoZSBmaXJzdCBmcmFnbWVudA0KPiA+PiA+ICAgICAgIGFycml2ZXMgdG8gYmUgcmVhc3NlbWJs
ZWQsIGEgYnVmZmVyIG9mIHRoZSBtYXhpbXVtIHBvc3NpYmxlIHNpemUNCj4gPj4gPiAgICAgICBt
YXkgaGF2ZSB0byBiZSBhbGxvY2F0ZWQgYmVjYXVzZSB0aGUgdG90YWwgbGVuZ3RoIG9mIHRoZQ0K
PiA+PiA+ICAgICAgIHJlYXNzZW1ibGVkIGRhdGFncmFtIGlzIG5vdCBrbm93biBhdCB0aGF0IHRp
bWUuIEZ1cnRoZXJtb3JlLCBhcw0KPiA+PiA+ICAgICAgIGZyYWdtZW50cyBtaWdodCBnZXQgbG9z
dCwgb3IgYmUgcmVvcmRlcmVkIG9yIGRlbGF5ZWQsIHRoZQ0KPiA+PiA+ICAgICAgIHJlYXNzZW1i
bHkgZW5naW5lIGhhcyB0byB3YWl0IHdpdGggdGhlIHBhcnRpYWwgcGFja2V0IGZvciBzb21lDQo+
ID4+ID4gICAgICAgdGltZSAoZS5nLiwgNjAgc2Vjb25kcyBbOV0pLiAgV2hlbiB0aGlzIHdvdWxk
IGhhdmUgdG8gYmUgZG9uZSBhdA0KPiA+PiA+ICAgICAgIHRoZSBsaW5lIHJhdGUsIHdpdGgsIGZv
ciBleGFtcGxlIDEwIEdiaXQvcyBzcGVlZCwgdGhlIGxlbmd0aCBvZg0KPiA+PiA+ICAgICAgIHRo
ZSBidWZmZXJzIHRoYXQgcmVhc3NlbWJseSBtaWdodCByZXF1aXJlIHdvdWxkIGJlIHByb2hpYml0
aXZlLiAiDQo+ID4+DQo+ID4+IFllcywgYnV0IHRoZSBhbHRlcm5hdGl2ZSBvZiBkZWNsYXJpbmcg
dGhhdCB5b3UgZG9uJ3QgcmVhc3NlbWJsZSBoYXMgYSBjb3N0IGluDQo+ID4+IHRlcm1zIG9mIGRy
b3BwZWQgc2VnbWVudHMgdG9vLg0KPiA+DQo+ID4gVGhlIGFsdGVybmF0aXZlIGlzIHRvIGNvbmZp
Z3VyZSB0aGUgTVRVIG9mIHRoZSBjb3JlIGxhcmdlIGVub3VnaCB0byBhY2NvbW1vZGF0ZSB0aGUg
YWRkZWQgZW5jYXBzdWxhdGlvbiBoZWFkZXIuIFRoaXMgaXMgYSBmZWFzaWJsZQ0KPiBhbmQgcHJv
dmVuIGFwcHJvYWNoIGluIHdlbGwtbWFuYWdlZCBTUCBuZXR3b3Jrcy4gTm8gcGFja2V0IGxvc3Mg
YW5kIG5vIGZvcndhcmRpbmcgcGVyZm9ybWFuY2UgZGVncmFkYXRpb24uDQo+ID4NCj4gPj4gVGFr
aW5nIHRoYXQgZHJvcCBpbnRvIGFjY291bnQsIGJ1ZmZlcmluZyBmb3IgYSBzbWFsbGVyIGFtb3Vu
dCBvZiBwb3RlbnRpYWwNCj4gPj4gcmVvcmRlcmluZyBhbmQgYWNjb3VudGluZyBmb3IgcmVhc29u
YWJsZSByZWFzc2VtYmx5IHNpemVzIChmb3IgSVB2NiwgdGhlDQo+ID4+IHNtYWxsZXN0ICJtYXgi
IHRoYXQncyByZXF1aXJlZCBpcyAxNTAwKSBuZWVkIG5vdCBiZSBwcm9oaWJpdGl2ZS4NCj4gPg0K
PiA+IEluIHRoZSBJUHY2LWluLUlQdjQgU29mdHdhcmUgbmV0d29yayBjYXNlLCBhc3N1bWUgdGhl
IE1UVSBvZiB0aGUgY29yZSBpcyBub3QgbGFyZ2UgZW5vdWdoIHRoYW4gMTI4MCsyMCwgYWxsIHRo
ZSBJUHY2IHRyYWZmaWMgYWNyb3NzDQo+IHRoZSB0dW5uZWxzIHdvdWxkIGhhdmUgdG8gYmUgZnJh
Z21lbnRlZCBhbmQgdGhlbiByZWFzc2VtYmxlZC4gTm90IGEgc21hbGwgYW1vdW50Lg0KPiA+DQo+
ID4+ID4gSGF2ZSB5b3UgaGVhcmQgdGhlIHdpZGUgYWRvcHRpb24gb2YgNjIyTSAoU1RNLTEpIGJl
eW9uZCBBVE0gaW50ZXJmYWNlcw0KPiA+PiBiZXR3ZWVuIEFUTSBzd2l0Y2hlcyBpbiB0aGUgcHJl
dmlvdXMgQVRNIG5ldHdvcmtzPyBJZiBub3QsIHRoZSBoaWdoZXN0DQo+ID4+IG5vbi1BVE0gaW50
ZXJmYWNlIGluIHRoZSBwYXN0IEFUTSBuZXR3b3JrcyB3YXMgdGhlIEZFIGludGVyZmFjZSB3aGlj
aCBpcyAxMDBNDQo+ID4+IGJwcyAoYXJvdW5kIHRoZSB5ZWFyIG9mIDIwMDApLCBJZiBJIHJlbWVt
YmVyZWQgaXQgY29ycmVjdGx5Lg0KPiA+Pg0KPiA+PiBPQzEyIEFUTSBOSUNzIHdlcmUgY29tbW9u
bHkgYXZhaWxhYmxlIGluIDE5OTguIFRoYXQgd2FzIGJhY2sgd2hlbg0KPiA+DQo+ID4gU29ycnks
IHRoZXJlIHdhcyBhIHNwZWxsaW5nIG1pc3Rha2UgKCBzL1NUTS0xL1NUTS00KS4NCj4gPg0KPiA+
IE9DMTIvU1RNLTQ9NjIyTS4gTXkgcXVlc3Rpb24gaXMgaGF2ZSB5b3UgaGVhcmQgdGhlIHdpZGUg
YWRvcHRpb24gb2YgNjIyTSAoU1RNLTQpIEJFWU9ORCBBVE0gaW50ZXJmYWNlcyAoZS5nLiwgU1RN
LQ0KPiAxNi9PQzQ4KSBhdCB0aGF0IHRpbWU/DQo+ID4NCj4gPj4gZXRoZXJuZXQgd2FzIHB1c2hp
bmcgMTAwTSBhbmQgdGhlIG9ubHkgb3RoZXIgbmVhci1naWdhYml0IHRlY2ggd2FzIE15cmljb20N
Cj4gPj4gKGEgc3Bpbi1vZmYgb2YgVVNDL0lTSSBhbmQgQ2FsdGVjaCkuIEkuZS4sIHdpdGggdGhl
IHRlY2ggYXZhaWxhYmxlIGF0IHRoYXQgdGltZSwNCj4gPj4gNjAwTWJwcyBTQVIgd2FzIHBvc3Np
YmxlLg0KPiA+DQo+ID4gV2FzIHRoYXQgNjAwTWJwcyBTQVIgY2FwYWJpbGl0eSBwcm92ZWQgaW4g
cmVhbCBuZXR3b3Jrcz8gQW5kIGZvciB3aGF0IHNlcnZpY2U/DQo+ID4NCj4gPj4gPiBGdXJ0aGVy
bW9yZSwgaGF2ZSB5b3UgaGVhcmQgdGhlIHJlb3JkZXJpbmcgaXNzdWUgd2l0aCBBVE0gY2VsbHM/
IElmIG5vLCB0aGF0DQo+ID4+IG1lYW5zIG9uY2UgYW4gQVRNIGNlbGwgb2YgYSBnaXZlbiBBTEwg
UERVIGdldHMgbG9zdCwgYWxsIHRoZSByZWNlaXZlZCBBVE0gY2VsbHMNCj4gPj4gb2YgdGhhdCBB
QUwgUERVIHdvdWxkIGJlIGRyb3BwZWQgYW5kIHRoZXJlZm9yZSB0aGUgcmVhc3NlbWJseSBidWZm
ZXIgZm9yIHRoYXQNCj4gPj4gQUFMIGRhdGFncmFtIHdvdWxkIGJlIHJlbGVhc2VkLiBJbiBvdGhl
ciB3b3JkcywgdGhlcmUgaXMgbm8gbmVlZCB0byB3YWl0IGZvcg0KPiA+PiB0aGUgbG9zdCBvciBy
ZW9yZGVyZWQgZnJhZ21lbnQgZm9yIGEgY2VydGFpbiBwZXJpb2Qgb2YgdGltZSBiZWZvcmUgcmVs
ZWFzaW5nIHRoZQ0KPiA+PiByZWFzc2VtYmx5IGJ1ZmZlci4NCj4gPj4gUmVvcmRlcmVkIG5vLCBi
dXQganVzdCBiZWNhdXNlIHRoZXkgYXJyaXZlIGluIG9yZGVyIGRvZXMgbm90IG1lYW4gdGhleSBh
cmUNCj4gPj4gcmVxdWlyZWQgdG8gYXJyaXZlICphZGphY2VudCouIFRoZSBzYW1lIHJlcXVpcmVt
ZW50IGFwcGxpZXMgaW4gdGVybXMgb2YNCj4gPj4gbmVlZGluZyByZWFzc2VtYmx5IGJ1ZmZlcnMg
Zm9yIGEgbnVtYmVyIG9mIGludGVybGVhdmVkIHNlZ21lbnRzLg0KPiA+DQo+ID4gSG93ZXZlciwg
dGhlIHJlYXNzZW1ibHkgYnVmZmVyIHJlcXVpcmVtZW50IGlzIGxpbWl0ZWQgZHVlIHRvIHRoZSBm
YWN0IHRoYXQgb25seSBvbmUgYnVmZmVyIGlzIG5lZWRlZCBwZXIgVkMgYW5kIHRoZSB0b3RhbCBu
dW1iZXINCj4gb2YgVkNzIGlzIG5vdCBsYXJnZSBvbiB0aGUgZWRnZSBvZiBBVE0gbmV0d29ya3Mu
IEluIGNvbnRyYXN0LCB0aGUgbnVtYmVyIG9mIElQIGZsb3dzIGlzIHVuY29udHJvbGxhYmxlLg0K
PiA+DQo+ID4+ID4gIFN1Y2ggYmVoYXZpb3IgaXMgbm90IHBvc3NpYmxlIGZvciBJUCBmcmFnbWVu
dGF0aW9uIGFuZCByZWFzc2VtYmx5LiBMYXN0IGJ1dA0KPiA+PiBub3QgbGVhc3QsIHRoZXJlIGlz
IG5vIG5lZWQgdG8gYXNzaWduIGEgcmVhc3NlbWJseSBidWZmZXIgcGVyIEFBTCBQRFUgKGFzDQo+
ID4+IG9wcG9zZWQgdG8gcGVyIElQIGRhdGFncmFtIGluIHRoZSBJUCBmcmFnbWVudGF0aW9uIGFu
ZCByZWFzc2VtYmx5IGNhc2UpLA0KPiA+PiBpbnN0ZWFkLCBvbmx5IG9uZSByZWFzc2VtYmx5IGJ1
ZmZlciBwZXIgVkMgc2luY2UgYWxsIGNlbGxzIHdpdGhpbiBhIGdpdmVuIFZDIHdvdWxkDQo+ID4+
IGJlIHJlY2VpdmVkIGluIG9yZGVyLiBTaW5jZSB0aGUgU0FSIGlzIG9ubHkgbmVlZGVkIG9uIHRo
ZSBlZGdlIG9mIHRoZSBBVE0NCj4gPj4gbmV0d29ya3MsIHRoZSBudW1iZXIgb2YgVkNzIGlzIHZl
cnkgbGltaXRlZC4NCj4gPj4gWW91IGNvdWxkIGVhc2lseSBkZWNpZGUgdG8gYWxsb2NhdGUgYSBm
aXhlZCBudW1iZXIgb2YgcmVhc3NlbWJseSBidWZmZXJzIHBlciBJUA0KPiA+PiBmbG93IHRvIGNv
bnNlcnZlIHJlc291cmNlcyB0b28uIFRoZSBhbW91bnQgb2YgcmVvcmRlcmluZywgdG9nZXRoZXIg
d2l0aCB0aGUNCj4gPg0KPiA+IFdoYXQgYWJvdXQgaW4gdGhlIEREb1MgYXR0YWNrIGNhc2U/IERv
IHlvdSBiZWxpZXZlIHRoYXQgU1BzIHdvdWxkIGFsbG93IHRoZSBleGlzdGVuY2Ugb2YgdGhhdCBv
YnZpb3VzIEREb1MgYXR0YWNrIHJpc2sgaW4gdGhlaXINCj4gbmV0d29ya3MgYW5kIGFmZm9yZCB0
aGUgc2lnbmlmaWNhbnQgZm9yd2FyZGluZyBwZXJmb3JtYW5jZSBkZWdyYWRhdGlvbj8gZXNwZWNp
YWxseSB3aGVuIHRoZXJlIGhhcyBiZWVuIGEgZmVhc2libGUgYW5kIHByb3Zlbg0KPiBzb2x1dGlv
biB0byB0aGUgTVRVIGlzc3VlIChpLmUuLCBjb25maWd1cmUgdGhlIE1UVSBvZiB0aGUgY29yZSBs
YXJnZSBlbm91Z2gpPw0KPiA+DQo+IFRoYXQgaXMgcHJlY2lzZWx5IHNvbHV0aW9uICMzIGluIFJG
QzQ0NTk6DQo+IA0KPiAiRW5zdXJlIHRoYXQgaW4gdGhlIHNwZWNpZmljIGVudmlyb25tZW50LCB0
aGUgZW5jYXBzdWxhdGVkIHBhY2tldHMNCj4gd2lsbCBmaXQgaW4gYWxsIHRoZSBwYXRocyBpbiB0
aGUgbmV0d29yaywgZS5nLiwgYnkgdXNpbmcgTVRVIGJpZ2dlcg0KPiB0aGFuIDE1MDAgaW4gdGhl
IGJhY2tib25lIHVzZWQgZm9yIGVuY2Fwc3VsYXRpb24uIg0KPiANCj4gSWYgeW91J3JlIGFibGUg
dG8gaW1wbGVtZW50IHRoaXMgaW4geW91IG5ldHdvcmsgdGhhdCdzIGdyZWF0LCBidXQgaXQNCj4g
aXMgbm90IGZlYXNpYmxlIGluIGFsbCBzaXR1YXRpb25zIGFuZCBoZW5jZSBjYW4ndCBiZSB0aGUg
c3RhbmRhcmQuIFdlDQoNCkkgYWdyZWUuIFNvIHRoZW4sIHdoYXQgKnNob3VsZCogYmUgdGhlIHN0
YW5kYXJkIGlzIEdVRSBwbHVzIGZyYWdtZW50YXRpb24NCnBsdXMgZGlyZWN0IElQIGVuY2Fwc3Vs
YXRpb24uIEkgdGhpbmsgdGhhdCBzaG91bGQgY292ZXIgYWxsIHVzZSBjYXNlcywgcmlnaHQ/DQoN
ClRoYW5rcyAtIEZyZWQNCg0KPiBtYXkgbm90IGNvbnRyb2wgYWxsIHRoZSB1bmRlcmxheSBuZXR3
b3JrcyAoZGVmaW5pdGVseSBub3Qgb3ZlciB0aGUNCj4gSW50ZXJuZXQpIGFuZCBoZW5jZSBub3Qg
YmUgYWJsZSB0byBzZXQgYWxsIHRoZSBNVFVzIGxhcmdlIGVub3VnaC4gQWxzbw0KPiBhbiBNVFUg
Z3JlYXRlciB0aGFuIDE1MDAgcmVxdWlyZSBqdW1ibyBmcmFtZXMsIG5vdCBhbGwgbmV0d29ya3MN
Cj4gZW5hYmxlZCB0aG9zZS4NCj4gDQo+IE9uZSBvdGhlciBwb2ludCwgd2hlbiBhIGRldmljZSBz
b3VyY2VzIG9yIHNpbmtzIElQIHBhY2tldHMgbGlrZSBpbg0KPiB0dW5uZWxpbmcgaXQgaXMgdGFr
aW5nIG9uIHRoZSByb2xlIG9mIGEgaG9zdCBhbmQgc28gd2UgZXhwZWN0IGhvc3QNCj4gcmVxdWly
ZW1lbnRzIGFwcGx5LiBGb3IgaW5zdGFuY2UsIHJvdXRlcnMgbWF5IHBlcmZvcm0gZnJhZ21lbnRh
dGlvbiBpbg0KPiBJUHY0LCBidXQgdGhleSBkbyBub3QgcGVyZm9ybSBmcmFnbWVudGF0aW9uIGZv
ciBJUHY2IG9yIHJlYXNzZW1ibHkNCj4gKHRob3NlIGFyZSBob3N0cyBmdW5jdGlvbmFsaXRpZXMp
LiBUaGVyZSBoYXMgYmVlbiBhdCBsZWFzdCBvbmUgYXR0ZW1wdA0KPiB0byBjYXJ2ZSBvdXQgZXhj
ZXB0aW9ucyBpbiBhcHBseWluZyBob3N0IHJlcXVpcmVtZW50cyB0byBkZXZpY2VzIHRoYXQNCj4g
cGVyZm9ybSB0dW5uZWxpbmcsIHRoYXQgaXMgYW4gYWxsb3dhbmNlIHRvIHNlbmQgYSB6ZXJvIFVE
UCBjaGVja3N1bSBpbg0KPiBpbiBJUHY2LiBEb2N1bWVudGluZyB0aGlzIHRvb2sgdHdvIFJGQ3Mg
YW5kIHdlIHN0aWxsIG5lZWRlZCBhIHdob2xlDQo+IGxvdCBvZiBkZXNjcmlwdGlvbiBpbiBhdCBs
ZWFzdCBHUkUvVURQIG9uIHJlcXVpcmVtZW50cyB0aGF0IHRvIHVzZSB0aGUNCj4gbm9uLXplcm8g
Y2hlY2tzdW0uIEkgZG9uJ3QgdGhpbmsgc3RhbmRhcmRpemluZyBleGNlcHRpb25zIGluDQo+IGZy
YWdtZW50YXRpb24gZm9yIHR1bm5lbHMgd291bGQgYmUgYW55IGVhc2llci4NCj4gDQo+IFRvbQ0K
PiANCj4gPiBCZXN0IHJlZ2FyZHMsDQo+ID4gWGlhb2h1DQo+ID4NCj4gPj4gbnVtYmVyIG9mIGZs
b3dzIHN1cHBvcnRlZCB3b3VsZCBkZXRlcm1pbmUgeW91ciBhYmlsaXR5IHRvIGF2b2lkIHBhY2tl
dCBkcm9wcw0KPiA+PiAtLSBidXQgcmVjYWxsIHRoYXQgZHJvcHMgYXQgaGlnaCBsb2FkIGFyZSBu
b3QgdW51c3VhbCBmb3IgSVAuDQo+ID4+DQo+ID4+IEpvZQ0KPiA+DQo+ID4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBJbnQtYXJlYSBtYWlsaW5n
IGxpc3QNCj4gPiBJbnQtYXJlYUBpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vaW50LWFyZWENCj4gDQoNCg==


From nobody Wed Jun  8 06:22:43 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B339D12D0DA; Wed,  8 Jun 2016 06:22:39 -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: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160608132239.19935.92809.idtracker@ietfa.amsl.com>
Date: Wed, 08 Jun 2016 06:22:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/94XfYWHNgLl5p6r6dvneLNHVyeY>
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-dslite-multicast-12.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 08 Jun 2016 13:22:40 -0000

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

        Title           : Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network
        Authors         : Jacni Qin
                          Mohamed Boucadair
                          Christian Jacquenet
                          Yiu L. Lee
                          Qian Wang
	Filename        : draft-ietf-softwire-dslite-multicast-12.txt
	Pages           : 19
	Date            : 2016-06-08

Abstract:
   This document specifies a solution for the delivery of IPv4 multicast
   services to IPv4 clients over an IPv6 multicast network.  The
   solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme
   and uses the IPv6 multicast distribution tree to deliver IPv4
   multicast traffic.  The solution is particularly useful for the
   delivery of multicast service offerings to DS-Lite serviced
   customers.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-softwire-dslite-multicast-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-dslite-multicast-12


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 Jun  8 07:50:58 2016
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6873212D79D for <softwires@ietfa.amsl.com>; Wed,  8 Jun 2016 07:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level: 
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=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 nsmAvsnQFohO for <softwires@ietfa.amsl.com>; Wed,  8 Jun 2016 07:50:55 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB31B12D5CA for <softwires@ietf.org>; Wed,  8 Jun 2016 07:50:53 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id E6A9918CA55; Wed,  8 Jun 2016 16:50:51 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.60]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id B013C4C063; Wed,  8 Jun 2016 16:50:51 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0294.000; Wed, 8 Jun 2016 16:50:51 +0200
From: <mohamed.boucadair@orange.com>
To: ian Farrer <ianfarrer@gmx.com>, "softwires@ietf.org" <softwires@ietf.org>,  Jacni Qin <jacni@jacni.com>, "dxhbupt@gmail.com" <dxhbupt@gmail.com>
Thread-Topic: Problem in draft-ietf-softwire-multicast-prefix-option
Thread-Index: AQHRwY+pjD8GiTRpEkWX2QNRUGBtGZ/fo66g
Date: Wed, 8 Jun 2016 14:50:51 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <trinity-fbc98ae4-0413-4cea-8842-a5959c4e303a-1465395089242@3capp-mailcom-bs12>
In-Reply-To: <trinity-fbc98ae4-0413-4cea-8842-a5959c4e303a-1465395089242@3capp-mailcom-bs12>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933008DAECE0OPEXCLILMA3corp_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.8.132415
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/eI5VckALqU34jefkcDtM-zxtkR0>
Cc: "dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
Subject: Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 08 Jun 2016 14:50:56 -0000

--_000_787AE7BB302AE849A7480A190F8B933008DAECE0OPEXCLILMA3corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSWFuLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4NCg0KQ2hlZXJzLA0KTWVkDQoNCkRlIDogaWFu
IEZhcnJlciBbbWFpbHRvOmlhbmZhcnJlckBnbXguY29tXQ0KRW52b3nDqSA6IG1lcmNyZWRpIDgg
anVpbiAyMDE2IDE2OjExDQrDgCA6IHNvZnR3aXJlc0BpZXRmLm9yZzsgQk9VQ0FEQUlSIE1vaGFt
ZWQgSU1UL09MTjsgSmFjbmkgUWluOyBkeGhidXB0QGdtYWlsLmNvbQ0KQ2MgOiBkaGN3Zy1jaGFp
cnNAaWV0Zi5vcmcNCk9iamV0IDogUHJvYmxlbSBpbiBkcmFmdC1pZXRmLXNvZnR3aXJlLW11bHRp
Y2FzdC1wcmVmaXgtb3B0aW9uDQoNCkhpLA0KDQpPbiByZXZpZXdpbmcgdGhpcyBkcmFmdCBJIHdv
dWxkIGxpa2UgdG8gcmFpc2UgYSBwcm9ibGVtIHdpdGggc2VjdGlvbiA1IG9mIHRoZSBkcmFmdC4g
VGhlIHRleHQgaXM6DQoNCiJJZiBhbGwgdGhlIGVuY2xvc2VkIElQdjQtZW1iZWRkZWQgSVB2NiBt
dWx0aWNhc3QgcHJlZml4ZXMgaGF2ZSB0aGUgc2FtZSBzY29wZSwgdGhlIGZpcnN0IGluc3RhbmNl
IG9mIHRoZSBvcHRpb24gTVVTVCBiZSB1c2VkLiINCg0KVGhlIHByb2JsZW0gaXMgdGhhdCB0aGlz
IGNvbnRyYXZlbmVzIHNlY3Rpb24gMTcgb2YgUkZDNzIyNzoNCg0KT3B0aW9uIG9yZGVyLCBlaXRo
ZXIgdGhlIG9yZGVyIGFtb25nIG1hbnkgREhDUHY2IG9wdGlvbnMgb3IgdGhlIG9yZGVyDQoNCiAg
IG9mIG11bHRpcGxlIGluc3RhbmNlcyBvZiB0aGUgc2FtZSBvcHRpb24sIFNIT1VMRCBOT1QgYmUg
c2lnbmlmaWNhbnQuDQoNCiAgIE5ldyBkb2N1bWVudHMgTVVTVCBOT1QgYXNzdW1lIGFueSBzcGVj
aWZpYyBvcHRpb24gcHJvY2Vzc2luZyBvcmRlci4NCg0KDQoNCltNZWRdIFRoYXQgc2VudGVuY2Ug
ZG9lcyBub3QgYXNzdW1lIGFueSAocHJlZmVyZW5jZSkgb3JkZXIuIEl0IGRvZXMgb25seSBwcm92
aWRlIG9uZSB3YXkgdG8gc2VsZWN0IG9uZSBpbnN0YW5jZSBhbW9uZyB0aGF0IGxpc3QuIEFzIGEg
cmVtaW5kZXIsIHRoZSBzZXJ2ZXIgaXMgc3VwcG9zZWQgdG8gcmV0dXJuIG9uZSBpbnN0YW5jZSAo
cGVyIHNjb3BlKS4NCg0KDQpJIHJhaXNlZCB0aGlzIHdpdGggdGhlIERIQyBXRyBjaGFpcnMsIGFu
ZCB0aGV5IGhhdmUgYSBjb3VwbGUgb2Ygc3VnZ2VzdGlvbnM6DQoNCjEuIERlZmluZSBhbiBlbmNh
cHN1bGF0aW5nIG9wdGlvbiAtIGFzIHRoZSBkYXRhIGluc2lkZSBhbiBvcHRpb24gY2FuIGJlIG9y
ZGVyIGRlcGVuZGVudC4NCjIuIEFkZCBhIOKAnHByZWZlcmVuY2XigJ0gKG9jdGV0PykgYW5kIHRo
ZW4gYSBjbGllbnQgY2FuIHNvcnQgdGhlbSBiYXNlZCBvbiB0aGlzIHByZWZlcmVuY2UuDQoNClRo
YW5rcywNCklhbg0K

--_000_787AE7BB302AE849A7480A190F8B933008DAECE0OPEXCLILMA3corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg
MiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VmVyZGFuYTsNCglwYW5vc2Ut
MToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29O
b3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdp
bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1l
cyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7
fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUHLDqWZv
cm1hdMOpIEhUTUwgQ2FyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsN
Cglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5Q
cmZvcm1hdEhUTUxDYXINCgl7bXNvLXN0eWxlLW5hbWU6IlByw6lmb3JtYXTDqSBIVE1MIENhciI7
DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQcsOpZm9ybWF0w6kg
SFRNTCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsN
Cgljb2xvcjpibGFjazsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7
fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1z
aXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7
DQoJbWFyZ2luOjcwLjg1cHQgNzAuODVwdCA3MC44NXB0IDcwLjg1cHQ7fQ0KZGl2LldvcmRTZWN0
aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4N
CjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlv
dXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286
c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJGUiIg
bGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkhpIElhbiw8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPlBsZWFzZSBzZWUgaW5saW5lLg0KPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj5DaGVlcnMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmll
ciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPk1lZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBj
bSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij5EZSZuYnNwOzo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4g
aWFuIEZhcnJlciBbbWFpbHRvOmlhbmZhcnJlckBnbXguY29tXQ0KPGJyPg0KPGI+RW52b3nDqSZu
YnNwOzo8L2I+IG1lcmNyZWRpIDgganVpbiAyMDE2IDE2OjExPGJyPg0KPGI+w4AmbmJzcDs6PC9i
PiBzb2Z0d2lyZXNAaWV0Zi5vcmc7IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE47IEphY25pIFFp
bjsgZHhoYnVwdEBnbWFpbC5jb208YnI+DQo8Yj5DYyZuYnNwOzo8L2I+IGRoY3dnLWNoYWlyc0Bp
ZXRmLm9yZzxicj4NCjxiPk9iamV0Jm5ic3A7OjwvYj4gUHJvYmxlbSBpbiBkcmFmdC1pZXRmLXNv
ZnR3aXJlLW11bHRpY2FzdC1wcmVmaXgtb3B0aW9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+SGksDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJk
YW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij5PbiByZXZpZXdpbmcgdGhpcyBkcmFmdCBJIHdvdWxkIGxpa2UgdG8gcmFp
c2UgYSBwcm9ibGVtIHdpdGggc2VjdGlvbiA1IG9mIHRoZSBkcmFmdC4gVGhlIHRleHQgaXM6PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij4mcXVvdDtJZiBhbGwgdGhlIGVuY2xvc2VkIElQdjQtZW1iZWRkZWQgSVB2NiBtdWx0
aWNhc3QgcHJlZml4ZXMgaGF2ZSB0aGUgc2FtZSBzY29wZSwgdGhlIGZpcnN0IGluc3RhbmNlIG9m
IHRoZSBvcHRpb24gTVVTVCBiZSB1c2VkLiZxdW90OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+VGhlIHByb2JsZW0gaXMg
dGhhdCB0aGlzIGNvbnRyYXZlbmVzIHNlY3Rpb24gMTcgb2YgUkZDNzIyNzo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cHJlPk9wdGlvbiBvcmRlciwgZWl0aGVyIHRoZSBv
cmRlciBhbW9uZyBtYW55IERIQ1B2NiBvcHRpb25zIG9yIHRoZSBvcmRlcjxvOnA+PC9vOnA+PC9w
cmU+DQo8cHJlPiZuYnNwOyZuYnNwOyBvZiBtdWx0aXBsZSBpbnN0YW5jZXMgb2YgdGhlIHNhbWUg
b3B0aW9uLCBTSE9VTEQgTk9UIGJlIHNpZ25pZmljYW50LjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJl
PiZuYnNwOyZuYnNwOyBOZXcgZG9jdW1lbnRzIE1VU1QgTk9UIGFzc3VtZSBhbnkgc3BlY2lmaWMg
b3B0aW9uIHByb2Nlc3Npbmcgb3JkZXIuPG86cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
cmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPltNZWRdIFRo
YXQgc2VudGVuY2UgZG9lcyBub3QgYXNzdW1lIGFueSAocHJlZmVyZW5jZSkgb3JkZXIuIEl0IGRv
ZXMgb25seSBwcm92aWRlIG9uZSB3YXkgdG8gc2VsZWN0IG9uZSBpbnN0YW5jZSBhbW9uZyB0aGF0
IGxpc3QuIEFzIGEgcmVtaW5kZXIsIHRoZSBzZXJ2ZXIgaXMgc3VwcG9zZWQgdG8gcmV0dXJuIG9u
ZSBpbnN0YW5jZSAocGVyIHNjb3BlKS4gJm5ic3A7Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9w
cmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcHJlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Zl
cmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+SSByYWlzZWQgdGhpcyB3aXRoIHRo
ZSBESEMgV0cgY2hhaXJzLCBhbmQgdGhleSBoYXZlIGEgY291cGxlIG9mIHN1Z2dlc3Rpb25zOjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Jm5ic3A7PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTom
cXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjEuIERlZmluZSBhbiBl
bmNhcHN1bGF0aW5nIG9wdGlvbiAtIGFzIHRoZSBkYXRhIGk8L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPm5zaWRlIGFuIG9wdGlvbiBjYW4gYmUgb3JkZXIgZGVwZW5kZW50LjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4yLiBBZGQgYSDigJxwcmVmZXJlbmNl4oCdIChvY3Rl
dD8pIGFuZCB0aGVuIGEgY2xpZW50IGNhbiBzb3J0IHRoZW0gYmFzZWQgb24mbmJzcDt0aGlzIHBy
ZWZlcmVuY2UuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVv
dDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5UaGFua3MsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBw
dDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PklhbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_787AE7BB302AE849A7480A190F8B933008DAECE0OPEXCLILMA3corp_--


From nobody Wed Jun  8 10:09:49 2016
Return-Path: <ianfarrer@gmx.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC1A12D75B for <softwires@ietfa.amsl.com>; Wed,  8 Jun 2016 10:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level: 
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 TC2VfZy5B-9A for <softwires@ietfa.amsl.com>; Wed,  8 Jun 2016 10:09:45 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 DF75612D512 for <softwires@ietf.org>; Wed,  8 Jun 2016 10:09:44 -0700 (PDT)
Received: from ians-mbp.lan ([62.225.30.139]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0M4nM5-1bN88012ab-00ywVF; Wed, 08 Jun 2016 19:09:41 +0200
From: Ian Farrer <ianfarrer@gmx.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2F89F692-11F8-4825-B5DA-BFD113213456"
Message-Id: <D5ABB288-99F9-4038-9E13-A9FC2ADAC0EF@gmx.com>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Date: Wed, 8 Jun 2016 19:09:39 +0200
References: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
To: mohamed Boucadair <mohamed.boucadair@orange.com>, Softwires WG <softwires@ietf.org>
X-Mailer: Apple Mail (2.2104)
X-Provags-ID: V03:K0:NLTMWFtSsbyGX0B9/zAj0drGugYpAq4ytzrhOcJHnhwZuOgkQ31 qM08DmNQmSUXNTaZurhoQYJpk6KoHX/QfP4Zrp6Qb+jlaHS8eoBZYPNBIzDztcEo2GX+ziG pJD30cHRpzIs32+gU5FRwgaqsyvC8t2B5jeknKU9EorZ7LI2YUGVdbBmi0N2K4QFJCwOPSb T5I++GhS0ifYsdtHxEj2Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:1Xowt35OzTw=:j6mO0SudvBOmkJG+GEngqZ G6S1DvDnEhtYX/MSlfnMMWYasuU88ib+qA3A586rYV2H0U/+1e+qU+/xGiJJAMqWa/bqlb+4m VqFwVSCJMbnPxeuBPOewXOuqW2KZA8NC+Z/mP8MBXjIzYbZMGl0RUFXuYvbe8ady6gxqfQDyt zsHkZkZIC+S7SRmOz0vow4dqIDCF2WIBawIf7KaLnC3qqBoXUEl+JvbcjdkABS3HL2rnfg0NL wQRYjMTOSZUDcWILIzxrq5AJs194AsIHYiDzz5zuVtyWP92sSGy5WqTOhI+q60FTt+U381FZr tUgyRnUO6rd3lgn8v0J6TaqFN1MLslkVImSmIWVw6s6GSu+J7fIfojg+btbPygV9J8xpzmLnV b/Mx9MXsBJYzzhEHRQ3JJC5lvRX67AGjOC6X+nZ3cFNSHy5UEQaz9GnWln9Tjj8NzqigblpZa 42Y7uwXj2EbVYAs71UAy7hTQWWLSgLZ9/La6cRe4C8iSe94byDnb2a5/HXArczLOnr43+gZwl bwTuZLMtO03Db8SVzV733gCvLlfzi+3wSyOrlB5BzWGZQf1hjsCE8XvOJ2wh95XPNcnOPePQs NmGEWriYuR4qY8ibPhS1ow86rqMCNcchE8RmScwHdHSwttnCGNP4tRssGydVD3EiAnLWR+2y5 bhzS1TkMII2IBKSDTXwX5BCWqvjnt0+wijfWMBo7jQtHJMZaBfsaeMGUEl+ynu9K85xxkMGia 5W1kL6dkPRKe8MIsiQIZbh6fzF5vhmZCwyQRMzmSeqQhqml/+45bPeCICq8B4nThPEorFmZOa AozX7Ee
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/oxS5h71W9K_YM3gyRCX5oJLmZ6E>
Cc: dhcwg-chairs@ietf.org
Subject: [Softwires] Fwd: Problem in draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 08 Jun 2016 17:09:48 -0000

--Apple-Mail=_2F89F692-11F8-4825-B5DA-BFD113213456
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Med,

Forwarding this to the list (the left group mailing addresses were not =
working earlier).

Please see inline below.

Thanks,
Ian

> Begin forwarded message:
>=20
> From: <mohamed.boucadair@orange.com>
> Subject: RE: Problem in draft-ietf-softwire-multicast-prefix-option
> Date: 8 June 2016 16:50:51 CEST
> To: ian Farrer <ianfarrer@gmx.com>, "softwires@ietf.org" =
<softwires@ietf.org>, Jacni Qin <jacni@jacni.com>, "dxhbupt@gmail.com" =
<dxhbupt@gmail.com>
> Cc: "dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
>=20
> Hi Ian,
> =20
> Please see inline.
> =20
> Cheers,
> Med
> =20
> De : ian Farrer [mailto:ianfarrer@gmx.com <mailto:ianfarrer@gmx.com>]=20=

> Envoy=C3=A9 : mercredi 8 juin 2016 16:11
> =C3=80 : softwires@ietf.org <mailto:softwires@ietf.org>; BOUCADAIR =
Mohamed IMT/OLN; Jacni Qin; dxhbupt@gmail.com <mailto:dxhbupt@gmail.com>
> Cc : dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>
> Objet : Problem in draft-ietf-softwire-multicast-prefix-option
> =20
> Hi,
> =20
> On reviewing this draft I would like to raise a problem with section 5 =
of the draft. The text is:
> =20
> "If all the enclosed IPv4-embedded IPv6 multicast prefixes have the =
same scope, the first instance of the option MUST be used."
> =20
> The problem is that this contravenes section 17 of RFC7227:
> Option order, either the order among many DHCPv6 options or the order
>    of multiple instances of the same option, SHOULD NOT be =
significant.
>    New documents MUST NOT assume any specific option processing order.
> =20
> [Med] That sentence does not assume any (preference) order. It does =
only provide one way to select one instance among that list. As a =
reminder, the server is supposed to return one instance (per scope).

[if - If the client is taking the first occurrence within the option and =
attempting to configure it, then it is preferring this option over other =
instances based on the order in which it occurs in the message.

The current text which describes the server behaviour (section 4) does =
not mention scope at all and does not specify any limitations on the =
number of instances or criteria for which they may be included - see =
RFC7227 sec 16.

If the server is meant to only return a single instance of the option =
per scope, but it is sending more than one, then this is a server =
configuration error. A quasi-random mechanism for the client to try and =
work around this just means that the configuration error may get masked.

As a suggestion, wouldn=E2=80=99t it be better to specify what the valid =
cases for the server including multiple option instances are and are not =
(with normative language). The client=E2=80=99s behaviour can then be =
defined to discard the options if they do not meet this criteria?]

> =20
> =20
> I raised this with the DHC WG chairs, and they have a couple of =
suggestions:
> =20
> 1. Define an encapsulating option - as the data inside an option can =
be order dependent.
> 2. Add a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can =
sort them based on this preference.
> =20
> Thanks,
> Ian


--Apple-Mail=_2F89F692-11F8-4825-B5DA-BFD113213456
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Med,<div class=3D""><br class=3D""></div><div =
class=3D"">Forwarding this to the list (the left group mailing addresses =
were not working earlier).</div><div class=3D""><br class=3D""></div><div =
class=3D"">Please see inline below.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Ian</div><div class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">Begin forwarded =
message:</div><br class=3D"Apple-interchange-newline"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">&lt;<a =
href=3D"mailto:mohamed.boucadair@orange.com" =
class=3D"">mohamed.boucadair@orange.com</a>&gt;<br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">RE: Problem in =
draft-ietf-softwire-multicast-prefix-option</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">8 June 2016 16:50:51 CEST<br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">ian Farrer &lt;<a =
href=3D"mailto:ianfarrer@gmx.com" class=3D"">ianfarrer@gmx.com</a>&gt;, =
"<a href=3D"mailto:softwires@ietf.org" class=3D"">softwires@ietf.org</a>" =
&lt;<a href=3D"mailto:softwires@ietf.org" =
class=3D"">softwires@ietf.org</a>&gt;, Jacni Qin &lt;<a =
href=3D"mailto:jacni@jacni.com" class=3D"">jacni@jacni.com</a>&gt;, "<a =
href=3D"mailto:dxhbupt@gmail.com" class=3D"">dxhbupt@gmail.com</a>" =
&lt;<a href=3D"mailto:dxhbupt@gmail.com" =
class=3D"">dxhbupt@gmail.com</a>&gt;<br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Cc: </b></span><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif;" class=3D"">"<a href=3D"mailto:dhcwg-chairs@ietf.org" =
class=3D"">dhcwg-chairs@ietf.org</a>" &lt;<a =
href=3D"mailto:dhcwg-chairs@ietf.org" =
class=3D"">dhcwg-chairs@ietf.org</a>&gt;<br class=3D""></span></div><br =
class=3D""><div class=3D""><div class=3D"WordSection1" style=3D"page: =
WordSection1; font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span style=3D"font-size: 10pt; =
font-family: 'Courier New';" class=3D"">Hi Ian,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" class=3D"">Please =
see inline.<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Cheers,<o:p class=3D""></o:p></span></div><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span style=3D"font-size: 10pt; font-family: 'Courier =
New';" class=3D"">Med<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span style=3D"font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;</span></div><div =
style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0cm 0cm 0cm 4pt;" class=3D""><div =
class=3D""><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0cm 0cm;" class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><b =
class=3D""><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;" class=3D"">De&nbsp;:</span></b><span style=3D"font-size: =
10pt; font-family: Tahoma, sans-serif;" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>ian Farrer [<a =
href=3D"mailto:ianfarrer@gmx.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">mailto:ianfarrer@gmx.com</a>]<span=
 class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><b =
class=3D"">Envoy=C3=A9&nbsp;:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>mercredi 8 juin 2016 =
16:11<br class=3D""><b class=3D"">=C3=80&nbsp;:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:softwires@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">softwires@ietf.org</a>; =
BOUCADAIR Mohamed IMT/OLN; Jacni Qin;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dxhbupt@gmail.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">dxhbupt@gmail.com</a><br =
class=3D""><b class=3D"">Cc&nbsp;:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">dhcwg-chairs@ietf.org</a><br =
class=3D""><b class=3D"">Objet&nbsp;:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Problem in =
draft-ietf-softwire-multicast-prefix-option<o:p =
class=3D""></o:p></span></div></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">Hi,<o:p class=3D""></o:p></span></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span style=3D"font-size: 9pt; =
font-family: Verdana, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span style=3D"font-size: 9pt; font-family: Verdana, =
sans-serif;" class=3D"">On reviewing this draft I would like to raise a =
problem with section 5 of the draft. The text is:<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span style=3D"font-size: 9pt; font-family: Verdana, =
sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span style=3D"font-size: 9pt; font-family: Verdana, =
sans-serif;" class=3D"">"If all the enclosed IPv4-embedded IPv6 =
multicast prefixes have the same scope, the first instance of the option =
MUST be used."<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">&nbsp;<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" class=3D"">The=
 problem is that this contravenes section 17 of RFC7227:<o:p =
class=3D""></o:p></span></div></div><div class=3D""><pre style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Option order, either the order among many DHCPv6 options or =
the order<o:p class=3D""></o:p></pre><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp; of multiple instances of the same option, SHOULD =
NOT be significant.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp; New documents MUST NOT assume any specific =
option processing order.<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D""><span lang=3D"EN-US" style=3D"" =
class=3D"">&nbsp;</span></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D""><span =
lang=3D"EN-US" style=3D"" class=3D"">[Med] That sentence does not assume =
any (preference) order. It does only provide one way to select one =
instance among that list. As a reminder, the server is supposed to =
return one instance (per =
scope).</span></pre></div></div></div></div></div></div></blockquote><div>=
<br class=3D""></div>[if - If the client is taking the first occurrence =
within the option and attempting to configure it, then it is preferring =
this option over other instances based on the order in which it occurs =
in the message.</div><div><br class=3D""></div><div>The current text =
which describes the server behaviour (section 4) does not mention scope =
at all and does not specify any limitations on the number of instances =
or criteria for which they may be included - see RFC7227 sec =
16.</div><div><br class=3D""></div><div>If the server is meant to only =
return a single instance of the option per scope, but it is sending more =
than one, then this is a server configuration error. A quasi-random =
mechanism for the client to try and work around this just means that the =
configuration error may get masked.</div><div><br class=3D""></div><div>As=
 a suggestion, wouldn=E2=80=99t it be better to specify what the valid =
cases for the server including multiple option instances are and are not =
(with normative language). The client=E2=80=99s behaviour can then be =
defined to discard the options if they do not meet this =
criteria?]</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"WordSection1" style=3D"page: =
WordSection1; font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div =
style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0cm 0cm 0cm 4pt;" class=3D""><div =
class=3D""><div class=3D""><div class=3D""><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D""><span =
lang=3D"EN-US" style=3D"" class=3D"">&nbsp;<o:p =
class=3D""></o:p></span></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D""><span =
lang=3D"EN-US" style=3D"" class=3D"">&nbsp;</span></pre><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" class=3D"">I =
raised this with the DHC WG chairs, and they have a couple of =
suggestions:<o:p class=3D""></o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
9pt; font-family: Verdana, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></span></div></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
9pt; font-family: Verdana, sans-serif;" class=3D"">1. Define an =
encapsulating option - as the data i</span><span style=3D"font-size: =
9pt; font-family: Verdana, sans-serif;" class=3D"">nside an option can =
be order dependent.<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" class=3D"">2. =
Add a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can sort =
them based on&nbsp;this preference.<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span style=3D"font-size: 9pt; font-family: Verdana, =
sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span style=3D"font-size: 9pt; font-family: Verdana, =
sans-serif;" class=3D"">Thanks,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span style=3D"font-size: 9pt; font-family: Verdana, =
sans-serif;" class=3D"">Ian<o:p =
class=3D""></o:p></span></div></div></div></div></div></div></div></blockq=
uote></div><br class=3D""></div></body></html>=

--Apple-Mail=_2F89F692-11F8-4825-B5DA-BFD113213456--


From nobody Wed Jun  8 23:49:17 2016
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B8E12D125 for <softwires@ietfa.amsl.com>; Wed,  8 Jun 2016 23:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.344
X-Spam-Level: 
X-Spam-Status: No, score=-3.344 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=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 XQExlRuChTiJ for <softwires@ietfa.amsl.com>; Wed,  8 Jun 2016 23:49:13 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFBDA12B043 for <softwires@ietf.org>; Wed,  8 Jun 2016 23:49:12 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 71475209D5; Thu,  9 Jun 2016 08:49:11 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.66]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 3E4DB1A0062; Thu,  9 Jun 2016 08:49:11 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA1.corporate.adroot.infra.ftgroup ([fe80::95e2:eb4b:3053:fabf%19]) with mapi id 14.03.0294.000; Thu, 9 Jun 2016 08:49:11 +0200
From: <mohamed.boucadair@orange.com>
To: Ian Farrer <ianfarrer@gmx.com>, Softwires WG <softwires@ietf.org>
Thread-Topic: Problem in draft-ietf-softwire-multicast-prefix-option
Thread-Index: AQHRwaiKjD8GiTRpEkWX2QNRUGBtGZ/grLvA
Date: Thu, 9 Jun 2016 06:49:09 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008DAF3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D5ABB288-99F9-4038-9E13-A9FC2ADAC0EF@gmx.com>
In-Reply-To: <D5ABB288-99F9-4038-9E13-A9FC2ADAC0EF@gmx.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: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933008DAF3A6OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/eklqcSod22YfQNgau1JqAWVvyK4>
Cc: "dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
Subject: Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 06:49:16 -0000

--_000_787AE7BB302AE849A7480A190F8B933008DAF3A6OPEXCLILMA3corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSWFuLA0KDQpUaGVyZSBhcmUgdHdvIG9wdGlvbnM6DQoNCigxKQ0KDQpNYWludGFpbiB0aGUg
Y3VycmVudCB0ZXh0IGluIHRoZSBkcmFmdCBidXQgYWRkIHRoZSBmb2xsb3dpbmcgdGV4dCB0byBT
ZWN0aW9uIDQ6DQoNCiAgIFNlcnZlcnMgU0hPVUxEIE5PVCBzZW5kIG1vcmUgdGhhbiBvbmUgaW5z
dGFuY2Ugb2YgT1BUSU9OX1Y2X1BSRUZJWDY0LA0KICAgZXhjZXB0IGlmIGRpc3RpbmN0IElQdjYg
bXVsdGljYXN0IHByZWZpeGVzIHdpdGggZGlzdGluY3Qgc2NvcGVzIGFyZQ0KICAgY29uZmlndXJl
ZC4NCg0KVGhpcyBpcyB0aGUgYmVoYXZpb3IgZGVmaW5lZCBpbiBodHRwczovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvcmZjNjMzNCNzZWN0aW9uLTUvLg0KDQooMikNCg0KQWRkIHRoaXMgdGV4dCBpbiBT
ZWN0aW9uIDQ6DQoNCiAgIFNlcnZlcnMgTVVTVCBOT1Qgc2VuZCBtb3JlIHRoYW4gb25lIGluc3Rh
bmNlIG9mIE9QVElPTl9WNl9QUkVGSVg2NCwNCiAgIGV4Y2VwdCBpZiBkaXN0aW5jdCBJUHY2IG11
bHRpY2FzdCBwcmVmaXhlcyB3aXRoIGRpc3RpbmN0IHNjb3BlcyBhcmUNCiAgIGNvbmZpZ3VyZWQu
DQoNCkFuZCBtb2RpZnkgdGhlIHRleHQgaW4gU2VjdGlvbiA1IHRvIGluZGljYXRlIHRoYXQgdGhl
IGNsaWVudCBtdXN0IGRpc2NhcmQgdGhlIG9wdGlvbnMgaWYgYWxsIGVuY2xvc2VkIGFkZHJlc3Nl
cyBhcmUgb2YgdGhlIHNhbWUgc2NvcGUuDQoNCkkgYWdyZWUgd2l0aCB5b3UgdGhhdCAoMikgd2ls
bCBoZWxwIHRvIGlkZW50aWZ5IGEgc2VydmVyIGVycm9yLCBidXQgd2l0aCBhIHJpc2sgdG8gaW5k
dWNlIHNlcnZpY2UgZGlzcnVwdGlvbnMuDQoNCldoaWNoIG9uZSBkbyB5b3UgcHJlZmVyIHRvIGJl
IGltcGxlbWVudGVkIGluIHRoZSBkcmFmdD8NCg0KVGhhbmsgeW91Lg0KDQpDaGVlcnMsDQpNZWQN
Cg0KRGUgOiBJYW4gRmFycmVyIFttYWlsdG86aWFuZmFycmVyQGdteC5jb21dDQpFbnZvecOpIDog
bWVyY3JlZGkgOCBqdWluIDIwMTYgMTk6MTANCsOAIDogQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09M
TjsgU29mdHdpcmVzIFdHDQpDYyA6IGRoY3dnLWNoYWlyc0BpZXRmLm9yZw0KT2JqZXQgOiBGd2Q6
IFByb2JsZW0gaW4gZHJhZnQtaWV0Zi1zb2Z0d2lyZS1tdWx0aWNhc3QtcHJlZml4LW9wdGlvbg0K
DQpIaSBNZWQsDQoNCkZvcndhcmRpbmcgdGhpcyB0byB0aGUgbGlzdCAodGhlIGxlZnQgZ3JvdXAg
bWFpbGluZyBhZGRyZXNzZXMgd2VyZSBub3Qgd29ya2luZyBlYXJsaWVyKS4NCg0KUGxlYXNlIHNl
ZSBpbmxpbmUgYmVsb3cuDQoNClRoYW5rcywNCklhbg0KDQoNCkJlZ2luIGZvcndhcmRlZCBtZXNz
YWdlOg0KDQpGcm9tOiA8bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbTxtYWlsdG86bW9oYW1l
ZC5ib3VjYWRhaXJAb3JhbmdlLmNvbT4+DQpTdWJqZWN0OiBSRTogUHJvYmxlbSBpbiBkcmFmdC1p
ZXRmLXNvZnR3aXJlLW11bHRpY2FzdC1wcmVmaXgtb3B0aW9uDQpEYXRlOiA4IEp1bmUgMjAxNiAx
Njo1MDo1MSBDRVNUDQpUbzogaWFuIEZhcnJlciA8aWFuZmFycmVyQGdteC5jb208bWFpbHRvOmlh
bmZhcnJlckBnbXguY29tPj4sICJzb2Z0d2lyZXNAaWV0Zi5vcmc8bWFpbHRvOnNvZnR3aXJlc0Bp
ZXRmLm9yZz4iIDxzb2Z0d2lyZXNAaWV0Zi5vcmc8bWFpbHRvOnNvZnR3aXJlc0BpZXRmLm9yZz4+
LCBKYWNuaSBRaW4gPGphY25pQGphY25pLmNvbTxtYWlsdG86amFjbmlAamFjbmkuY29tPj4sICJk
eGhidXB0QGdtYWlsLmNvbTxtYWlsdG86ZHhoYnVwdEBnbWFpbC5jb20+IiA8ZHhoYnVwdEBnbWFp
bC5jb208bWFpbHRvOmR4aGJ1cHRAZ21haWwuY29tPj4NCkNjOiAiZGhjd2ctY2hhaXJzQGlldGYu
b3JnPG1haWx0bzpkaGN3Zy1jaGFpcnNAaWV0Zi5vcmc+IiA8ZGhjd2ctY2hhaXJzQGlldGYub3Jn
PG1haWx0bzpkaGN3Zy1jaGFpcnNAaWV0Zi5vcmc+Pg0KDQpIaSBJYW4sDQoNClBsZWFzZSBzZWUg
aW5saW5lLg0KDQpDaGVlcnMsDQpNZWQNCg0KRGUgOiBpYW4gRmFycmVyIFttYWlsdG86aWFuZmFy
cmVyQGdteC5jb21dDQpFbnZvecOpIDogbWVyY3JlZGkgOCBqdWluIDIwMTYgMTY6MTENCsOAIDog
c29mdHdpcmVzQGlldGYub3JnPG1haWx0bzpzb2Z0d2lyZXNAaWV0Zi5vcmc+OyBCT1VDQURBSVIg
TW9oYW1lZCBJTVQvT0xOOyBKYWNuaSBRaW47IGR4aGJ1cHRAZ21haWwuY29tPG1haWx0bzpkeGhi
dXB0QGdtYWlsLmNvbT4NCkNjIDogZGhjd2ctY2hhaXJzQGlldGYub3JnPG1haWx0bzpkaGN3Zy1j
aGFpcnNAaWV0Zi5vcmc+DQpPYmpldCA6IFByb2JsZW0gaW4gZHJhZnQtaWV0Zi1zb2Z0d2lyZS1t
dWx0aWNhc3QtcHJlZml4LW9wdGlvbg0KDQpIaSwNCg0KT24gcmV2aWV3aW5nIHRoaXMgZHJhZnQg
SSB3b3VsZCBsaWtlIHRvIHJhaXNlIGEgcHJvYmxlbSB3aXRoIHNlY3Rpb24gNSBvZiB0aGUgZHJh
ZnQuIFRoZSB0ZXh0IGlzOg0KDQoiSWYgYWxsIHRoZSBlbmNsb3NlZCBJUHY0LWVtYmVkZGVkIElQ
djYgbXVsdGljYXN0IHByZWZpeGVzIGhhdmUgdGhlIHNhbWUgc2NvcGUsIHRoZSBmaXJzdCBpbnN0
YW5jZSBvZiB0aGUgb3B0aW9uIE1VU1QgYmUgdXNlZC4iDQoNClRoZSBwcm9ibGVtIGlzIHRoYXQg
dGhpcyBjb250cmF2ZW5lcyBzZWN0aW9uIDE3IG9mIFJGQzcyMjc6DQoNCk9wdGlvbiBvcmRlciwg
ZWl0aGVyIHRoZSBvcmRlciBhbW9uZyBtYW55IERIQ1B2NiBvcHRpb25zIG9yIHRoZSBvcmRlcg0K
DQogICBvZiBtdWx0aXBsZSBpbnN0YW5jZXMgb2YgdGhlIHNhbWUgb3B0aW9uLCBTSE9VTEQgTk9U
IGJlIHNpZ25pZmljYW50Lg0KDQogICBOZXcgZG9jdW1lbnRzIE1VU1QgTk9UIGFzc3VtZSBhbnkg
c3BlY2lmaWMgb3B0aW9uIHByb2Nlc3Npbmcgb3JkZXIuDQoNCg0KDQpbTWVkXSBUaGF0IHNlbnRl
bmNlIGRvZXMgbm90IGFzc3VtZSBhbnkgKHByZWZlcmVuY2UpIG9yZGVyLiBJdCBkb2VzIG9ubHkg
cHJvdmlkZSBvbmUgd2F5IHRvIHNlbGVjdCBvbmUgaW5zdGFuY2UgYW1vbmcgdGhhdCBsaXN0LiBB
cyBhIHJlbWluZGVyLCB0aGUgc2VydmVyIGlzIHN1cHBvc2VkIHRvIHJldHVybiBvbmUgaW5zdGFu
Y2UgKHBlciBzY29wZSkuDQoNCltpZiAtIElmIHRoZSBjbGllbnQgaXMgdGFraW5nIHRoZSBmaXJz
dCBvY2N1cnJlbmNlIHdpdGhpbiB0aGUgb3B0aW9uIGFuZCBhdHRlbXB0aW5nIHRvIGNvbmZpZ3Vy
ZSBpdCwgdGhlbiBpdCBpcyBwcmVmZXJyaW5nIHRoaXMgb3B0aW9uIG92ZXIgb3RoZXIgaW5zdGFu
Y2VzIGJhc2VkIG9uIHRoZSBvcmRlciBpbiB3aGljaCBpdCBvY2N1cnMgaW4gdGhlIG1lc3NhZ2Uu
DQoNClRoZSBjdXJyZW50IHRleHQgd2hpY2ggZGVzY3JpYmVzIHRoZSBzZXJ2ZXIgYmVoYXZpb3Vy
IChzZWN0aW9uIDQpIGRvZXMgbm90IG1lbnRpb24gc2NvcGUgYXQgYWxsIGFuZCBkb2VzIG5vdCBz
cGVjaWZ5IGFueSBsaW1pdGF0aW9ucyBvbiB0aGUgbnVtYmVyIG9mIGluc3RhbmNlcyBvciBjcml0
ZXJpYSBmb3Igd2hpY2ggdGhleSBtYXkgYmUgaW5jbHVkZWQgLSBzZWUgUkZDNzIyNyBzZWMgMTYu
DQoNCklmIHRoZSBzZXJ2ZXIgaXMgbWVhbnQgdG8gb25seSByZXR1cm4gYSBzaW5nbGUgaW5zdGFu
Y2Ugb2YgdGhlIG9wdGlvbiBwZXIgc2NvcGUsIGJ1dCBpdCBpcyBzZW5kaW5nIG1vcmUgdGhhbiBv
bmUsIHRoZW4gdGhpcyBpcyBhIHNlcnZlciBjb25maWd1cmF0aW9uIGVycm9yLiBBIHF1YXNpLXJh
bmRvbSBtZWNoYW5pc20gZm9yIHRoZSBjbGllbnQgdG8gdHJ5IGFuZCB3b3JrIGFyb3VuZCB0aGlz
IGp1c3QgbWVhbnMgdGhhdCB0aGUgY29uZmlndXJhdGlvbiBlcnJvciBtYXkgZ2V0IG1hc2tlZC4N
Cg0KQXMgYSBzdWdnZXN0aW9uLCB3b3VsZG7igJl0IGl0IGJlIGJldHRlciB0byBzcGVjaWZ5IHdo
YXQgdGhlIHZhbGlkIGNhc2VzIGZvciB0aGUgc2VydmVyIGluY2x1ZGluZyBtdWx0aXBsZSBvcHRp
b24gaW5zdGFuY2VzIGFyZSBhbmQgYXJlIG5vdCAod2l0aCBub3JtYXRpdmUgbGFuZ3VhZ2UpLiBU
aGUgY2xpZW504oCZcyBiZWhhdmlvdXIgY2FuIHRoZW4gYmUgZGVmaW5lZCB0byBkaXNjYXJkIHRo
ZSBvcHRpb25zIGlmIHRoZXkgZG8gbm90IG1lZXQgdGhpcyBjcml0ZXJpYT9dDQoNCg0KDQoNCg0K
DQpJIHJhaXNlZCB0aGlzIHdpdGggdGhlIERIQyBXRyBjaGFpcnMsIGFuZCB0aGV5IGhhdmUgYSBj
b3VwbGUgb2Ygc3VnZ2VzdGlvbnM6DQoNCjEuIERlZmluZSBhbiBlbmNhcHN1bGF0aW5nIG9wdGlv
biAtIGFzIHRoZSBkYXRhIGluc2lkZSBhbiBvcHRpb24gY2FuIGJlIG9yZGVyIGRlcGVuZGVudC4N
CjIuIEFkZCBhIOKAnHByZWZlcmVuY2XigJ0gKG9jdGV0PykgYW5kIHRoZW4gYSBjbGllbnQgY2Fu
IHNvcnQgdGhlbSBiYXNlZCBvbiB0aGlzIHByZWZlcmVuY2UuDQoNClRoYW5rcywNCklhbg0KDQo=

--_000_787AE7BB302AE849A7480A190F8B933008DAF3A6OPEXCLILMA3corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlZl
cmRhbmE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgltc28tc3R5bGUtbGluazoiUHLDqWZvcm1hdMOpIEhUTUwgQ2FyIjsNCgltYXJnaW46
MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYu
TXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlRl
eHRlIGRlIGJ1bGxlcyBDYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0
Ow0KCWZvbnQtc2l6ZTo4LjBwdDsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7
fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBh
cmFncmFwaA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJbWFyZ2luLXRvcDowY207DQoJbWFy
Z2luLXJpZ2h0OjBjbTsNCgltYXJnaW4tYm90dG9tOjBjbTsNCgltYXJnaW4tbGVmdDozNi4wcHQ7
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1p
bHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpzcGFuLmFwcGxlLWNvbnZlcnRlZC1zcGFj
ZQ0KCXttc28tc3R5bGUtbmFtZTphcHBsZS1jb252ZXJ0ZWQtc3BhY2U7fQ0Kc3Bhbi5QcmZvcm1h
dEhUTUxDYXINCgl7bXNvLXN0eWxlLW5hbWU6IlByw6lmb3JtYXTDqSBIVE1MIENhciI7DQoJbXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQcsOpZm9ybWF0w6kgSFRNTCI7
DQoJZm9udC1mYW1pbHk6IkNvbnNvbGFzIiwic2VyaWYiO30NCnNwYW4uVGV4dGVkZWJ1bGxlc0Nh
cg0KCXttc28tc3R5bGUtbmFtZToiVGV4dGUgZGUgYnVsbGVzIENhciI7DQoJbXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJUZXh0ZSBkZSBidWxsZXMiOw0KCWZvbnQtZmFt
aWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUyMg0KCXttc28tc3R5
bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ291cmllciBOZXciOw0KCWNv
bG9yOmJsYWNrOw0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0eWxlOm5vcm1hbDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6
MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCglt
YXJnaW46NzAuODVwdCA3MC44NXB0IDcwLjg1cHQgNzAuODVwdDt9DQpkaXYuV29yZFNlY3Rpb24x
DQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4
bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94
bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2
OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFw
ZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkZSIiBsaW5r
PSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+SGkgSWFuLA0KPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+VGhlcmUgYXJlIHR3byBvcHRpb25zOg0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPigxKTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5NYWludGFpbiB0
aGUgY3VycmVudCB0ZXh0IGluIHRoZSBkcmFmdCBidXQgYWRkIHRoZSBmb2xsb3dpbmcgdGV4dCB0
byBTZWN0aW9uIDQ6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNw
OyZuYnNwOyBTZXJ2ZXJzIFNIT1VMRCBOT1Qgc2VuZCBtb3JlIHRoYW4gb25lIGluc3RhbmNlIG9m
IE9QVElPTl9WNl9QUkVGSVg2NCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBleGNlcHQgaWYgZGlz
dGluY3QgSVB2NiBtdWx0aWNhc3QgcHJlZml4ZXMgd2l0aCBkaXN0aW5jdCBzY29wZXMgYXJlPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7Ij4mbmJzcDsmbmJzcDsgY29uZmlndXJlZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+VGhpcyBpcyB0aGUgYmVoYXZpb3IgZGVmaW5lZCBp
bg0KPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzYzMzQjc2VjdGlvbi01
LyI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzYzMzQjc2VjdGlvbi01LzwvYT4uPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPigyKTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5BZGQgdGhpcyB0
ZXh0IGluIFNlY3Rpb24gNDo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+
Jm5ic3A7Jm5ic3A7IFNlcnZlcnMgTVVTVCBOT1Qgc2VuZCBtb3JlIHRoYW4gb25lIGluc3RhbmNl
IG9mIE9QVElPTl9WNl9QUkVGSVg2NCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBleGNlcHQgaWYg
ZGlzdGluY3QgSVB2NiBtdWx0aWNhc3QgcHJlZml4ZXMgd2l0aCBkaXN0aW5jdCBzY29wZXMgYXJl
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7Ij4mbmJzcDsmbmJzcDsNCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Y29uZmlndXJlZC48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+QW5kIG1vZGlm
eSB0aGUgdGV4dCBpbiBTZWN0aW9uIDUgdG8gaW5kaWNhdGUgdGhhdCB0aGUgY2xpZW50IG11c3Qg
ZGlzY2FyZCB0aGUgb3B0aW9ucyBpZiBhbGwgZW5jbG9zZWQgYWRkcmVzc2VzIGFyZSBvZiB0aGUg
c2FtZSBzY29wZS4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj5JIGFncmVlIHdpdGggeW91IHRoYXQgKDIpIHdpbGwgaGVscCB0byBpZGVudGlmeSBh
IHNlcnZlciBlcnJvciwgYnV0IHdpdGggYSByaXNrIHRvIGluZHVjZSBzZXJ2aWNlIGRpc3J1cHRp
b25zLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5X
aGljaCBvbmUgZG8geW91IHByZWZlciB0byBiZSBpbXBsZW1lbnRlZCBpbiB0aGUgZHJhZnQ/PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPlRoYW5rIHlv
dS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmll
ciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Q2hl
ZXJzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+TWVkPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
bGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4N
CjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtw
YWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5EZSZuYnNwOzo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij4gSWFuIEZhcnJlciBbbWFpbHRvOmlhbmZhcnJlckBnbXguY29tXQ0KPGJy
Pg0KPGI+RW52b3nDqSZuYnNwOzo8L2I+IG1lcmNyZWRpIDgganVpbiAyMDE2IDE5OjEwPGJyPg0K
PGI+w4AmbmJzcDs6PC9iPiBCT1VDQURBSVIgTW9oYW1lZCBJTVQvT0xOOyBTb2Z0d2lyZXMgV0c8
YnI+DQo8Yj5DYyZuYnNwOzo8L2I+IGRoY3dnLWNoYWlyc0BpZXRmLm9yZzxicj4NCjxiPk9iamV0
Jm5ic3A7OjwvYj4gRndkOiBQcm9ibGVtIGluIGRyYWZ0LWlldGYtc29mdHdpcmUtbXVsdGljYXN0
LXByZWZpeC1vcHRpb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5IaSBNZWQsPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5Gb3J3YXJkaW5nIHRoaXMgdG8gdGhlIGxpc3QgKHRoZSBsZWZ0IGdyb3VwIG1haWxpbmcgYWRk
cmVzc2VzIHdlcmUgbm90IHdvcmtpbmcgZWFybGllcikuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBsZWFzZSBzZWUgaW5saW5lIGJlbG93Ljxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFu
a3MsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5J
YW48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5CZWdpbiBmb3J3YXJkZWQgbWVzc2FnZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOiA8L3NwYW4+DQo8L2I+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7Ij4mbHQ7PGEgaHJlZj0ibWFpbHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20iPm1v
aGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb208L2E+Jmd0Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+U3Vi
amVjdDogUkU6IFByb2JsZW0gaW4gZHJhZnQtaWV0Zi1zb2Z0d2lyZS1tdWx0aWNhc3QtcHJlZml4
LW9wdGlvbjwvc3Bhbj48L2I+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkRhdGU6IDwvc3Bhbj4NCjwvYj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPjggSnVuZSAyMDE2IDE2OjUwOjUxIENFU1Q8L3NwYW4+PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPlRvOiA8
L3NwYW4+DQo8L2I+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5pYW4gRmFycmVyICZsdDs8YSBocmVmPSJtYWlsdG86
aWFuZmFycmVyQGdteC5jb20iPmlhbmZhcnJlckBnbXguY29tPC9hPiZndDssICZxdW90OzxhIGhy
ZWY9Im1haWx0bzpzb2Z0d2lyZXNAaWV0Zi5vcmciPnNvZnR3aXJlc0BpZXRmLm9yZzwvYT4mcXVv
dDsgJmx0OzxhIGhyZWY9Im1haWx0bzpzb2Z0d2lyZXNAaWV0Zi5vcmciPnNvZnR3aXJlc0BpZXRm
Lm9yZzwvYT4mZ3Q7LCBKYWNuaSBRaW4NCiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmphY25pQGphY25p
LmNvbSI+amFjbmlAamFjbmkuY29tPC9hPiZndDssICZxdW90OzxhIGhyZWY9Im1haWx0bzpkeGhi
dXB0QGdtYWlsLmNvbSI+ZHhoYnVwdEBnbWFpbC5jb208L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJt
YWlsdG86ZHhoYnVwdEBnbWFpbC5jb20iPmR4aGJ1cHRAZ21haWwuY29tPC9hPiZndDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPkNjOiA8L3NwYW4+DQo8L2I+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mcXVvdDs8YSBocmVm
PSJtYWlsdG86ZGhjd2ctY2hhaXJzQGlldGYub3JnIj5kaGN3Zy1jaGFpcnNAaWV0Zi5vcmc8L2E+
JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86ZGhjd2ctY2hhaXJzQGlldGYub3JnIj5kaGN3Zy1j
aGFpcnNAaWV0Zi5vcmc8L2E+Jmd0Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij5IaSBJYW4sPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7Ij5QbGVhc2Ugc2VlIGlubGluZS48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7PC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDsiPkNoZWVycyw8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+TWVkPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOzwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGlu
ZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkRlJm5ic3A7Ojwvc3Bhbj48L2I+PHNwYW4gY2xhc3M9
ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNw
Ozwvc3Bhbj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPmlhbg0KIEZhcnJlciBb
PGEgaHJlZj0ibWFpbHRvOmlhbmZhcnJlckBnbXguY29tIj48c3BhbiBzdHlsZT0iY29sb3I6cHVy
cGxlIj5tYWlsdG86aWFuZmFycmVyQGdteC5jb208L3NwYW4+PC9hPl08c3BhbiBjbGFzcz0iYXBw
bGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGJyPg0KPGI+RW52b3nDqSZuYnNwOzo8
L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPm1lcmNy
ZWRpIDgganVpbiAyMDE2IDE2OjExPGJyPg0KPGI+w4AmbmJzcDs6PC9iPjxzcGFuIGNsYXNzPSJh
cHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWlsdG86c29mdHdp
cmVzQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5zb2Z0d2lyZXNAaWV0Zi5v
cmc8L3NwYW4+PC9hPjsgQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTjsgSmFjbmkgUWluOzxzcGFu
IGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWls
dG86ZHhoYnVwdEBnbWFpbC5jb20iPjxzcGFuIHN0eWxlPSJjb2xvcjpwdXJwbGUiPmR4aGJ1cHRA
Z21haWwuY29tPC9zcGFuPjwvYT48YnI+DQo8Yj5DYyZuYnNwOzo8L2I+PHNwYW4gY2xhc3M9ImFw
cGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpkaGN3Zy1j
aGFpcnNAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjpwdXJwbGUiPmRoY3dnLWNoYWlyc0Bp
ZXRmLm9yZzwvc3Bhbj48L2E+PGJyPg0KPGI+T2JqZXQmbmJzcDs6PC9iPjxzcGFuIGNsYXNzPSJh
cHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5Qcm9ibGVtIGluIGRyYWZ0LWlldGYt
c29mdHdpcmUtbXVsdGljYXN0LXByZWZpeC1vcHRpb248L3NwYW4+PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5IaSw8L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij5PbiByZXZpZXdpbmcgdGhpcyBkcmFmdCBJIHdvdWxkIGxpa2UgdG8g
cmFpc2UgYSBwcm9ibGVtIHdpdGggc2VjdGlvbiA1IG9mIHRoZSBkcmFmdC4gVGhlIHRleHQgaXM6
PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWls
eTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mcXVvdDtJZiBhbGwgdGhl
IGVuY2xvc2VkIElQdjQtZW1iZWRkZWQgSVB2NiBtdWx0aWNhc3QgcHJlZml4ZXMgaGF2ZSB0aGUg
c2FtZSBzY29wZSwgdGhlIGZpcnN0IGluc3RhbmNlIG9mIHRoZSBvcHRpb24gTVVTVCBiZSB1c2Vk
LiZxdW90Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+VGhlIHByb2Js
ZW0gaXMgdGhhdCB0aGlzIGNvbnRyYXZlbmVzIHNlY3Rpb24gMTcgb2YgUkZDNzIyNzo8L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwcmU+T3B0aW9uIG9yZGVy
LCBlaXRoZXIgdGhlIG9yZGVyIGFtb25nIG1hbnkgREhDUHY2IG9wdGlvbnMgb3IgdGhlIG9yZGVy
PG86cD48L286cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7IG9mIG11bHRpcGxlIGluc3RhbmNl
cyBvZiB0aGUgc2FtZSBvcHRpb24sIFNIT1VMRCBOT1QgYmUgc2lnbmlmaWNhbnQuPG86cD48L286
cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7IE5ldyBkb2N1bWVudHMgTVVTVCBOT1QgYXNzdW1l
IGFueSBzcGVjaWZpYyBvcHRpb24gcHJvY2Vzc2luZyBvcmRlci48bzpwPjwvbzpwPjwvcHJlPg0K
PHByZT48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8
cHJlPjxzcGFuIGxhbmc9IkVOLVVTIj5bTWVkXSBUaGF0IHNlbnRlbmNlIGRvZXMgbm90IGFzc3Vt
ZSBhbnkgKHByZWZlcmVuY2UpIG9yZGVyLiBJdCBkb2VzIG9ubHkgcHJvdmlkZSBvbmUgd2F5IHRv
IHNlbGVjdCBvbmUgaW5zdGFuY2UgYW1vbmcgdGhhdCBsaXN0LiBBcyBhIHJlbWluZGVyLCB0aGUg
c2VydmVyIGlzIHN1cHBvc2VkIHRvIHJldHVybiBvbmUgaW5zdGFuY2UgKHBlciBzY29wZSkuPC9z
cGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5baWYgLSBJZiB0aGUgY2xpZW50IGlzIHRha2lu
ZyB0aGUgZmlyc3Qgb2NjdXJyZW5jZSB3aXRoaW4gdGhlIG9wdGlvbiBhbmQgYXR0ZW1wdGluZyB0
byBjb25maWd1cmUgaXQsIHRoZW4gaXQgaXMgcHJlZmVycmluZyB0aGlzIG9wdGlvbiBvdmVyIG90
aGVyIGluc3RhbmNlcyBiYXNlZCBvbiB0aGUgb3JkZXIgaW4gd2hpY2ggaXQgb2NjdXJzIGluIHRo
ZSBtZXNzYWdlLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5UaGUgY3VycmVudCB0ZXh0IHdoaWNoIGRlc2NyaWJlcyB0aGUgc2VydmVyIGJlaGF2
aW91ciAoc2VjdGlvbiA0KSBkb2VzIG5vdCBtZW50aW9uIHNjb3BlIGF0IGFsbCBhbmQgZG9lcyBu
b3Qgc3BlY2lmeSBhbnkgbGltaXRhdGlvbnMgb24gdGhlIG51bWJlciBvZiBpbnN0YW5jZXMgb3Ig
Y3JpdGVyaWEgZm9yIHdoaWNoIHRoZXkgbWF5IGJlIGluY2x1ZGVkIC0gc2VlIFJGQzcyMjcgc2Vj
IDE2LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5JZiB0aGUgc2VydmVyIGlzIG1lYW50IHRvIG9ubHkgcmV0dXJuIGEgc2luZ2xlIGluc3RhbmNl
IG9mIHRoZSBvcHRpb24gcGVyIHNjb3BlLCBidXQgaXQgaXMgc2VuZGluZyBtb3JlIHRoYW4gb25l
LCB0aGVuIHRoaXMgaXMgYSBzZXJ2ZXIgY29uZmlndXJhdGlvbiBlcnJvci4gQSBxdWFzaS1yYW5k
b20gbWVjaGFuaXNtIGZvciB0aGUgY2xpZW50IHRvIHRyeSBhbmQgd29yayBhcm91bmQgdGhpcyBq
dXN0IG1lYW5zDQogdGhhdCB0aGUgY29uZmlndXJhdGlvbiBlcnJvciBtYXkgZ2V0IG1hc2tlZC48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMg
YSBzdWdnZXN0aW9uLCB3b3VsZG7igJl0IGl0IGJlIGJldHRlciB0byBzcGVjaWZ5IHdoYXQgdGhl
IHZhbGlkIGNhc2VzIGZvciB0aGUgc2VydmVyIGluY2x1ZGluZyBtdWx0aXBsZSBvcHRpb24gaW5z
dGFuY2VzIGFyZSBhbmQgYXJlIG5vdCAod2l0aCBub3JtYXRpdmUgbGFuZ3VhZ2UpLiBUaGUgY2xp
ZW504oCZcyBiZWhhdmlvdXIgY2FuIHRoZW4gYmUgZGVmaW5lZCB0byBkaXNjYXJkIHRoZSBvcHRp
b25zIGlmIHRoZXkNCiBkbyBub3QgbWVldCB0aGlzIGNyaXRlcmlhP108bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxvOnA+PC9v
OnA+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
IGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3By
ZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcHJl
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPkkgcmFpc2VkIHRoaXMgd2l0aCB0aGUgREhDIFdHIGNoYWly
cywgYW5kIHRoZXkgaGF2ZSBhIGNvdXBsZSBvZiBzdWdnZXN0aW9uczo8L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTom
cXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6OS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij4xLiBEZWZpbmUgYW4gZW5jYXBzdWxhdGluZyBvcHRpb24gLSBhcyB0aGUgZGF0YSBpPC9zcGFu
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5uc2lkZSBhbiBvcHRpb24gY2FuIGJlIG9yZGVy
IGRlcGVuZGVudC48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
Mi4gQWRkIGEg4oCccHJlZmVyZW5jZeKAnSAob2N0ZXQ/KSBhbmQgdGhlbiBhIGNsaWVudCBjYW4g
c29ydCB0aGVtIGJhc2VkIG9uJm5ic3A7dGhpcyBwcmVmZXJlbmNlLjwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+VGhhbmtzLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5JYW48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9ib2R5Pg0KPC9odG1sPg0K

--_000_787AE7BB302AE849A7480A190F8B933008DAF3A6OPEXCLILMA3corp_--


From nobody Thu Jun  9 00:44:48 2016
Return-Path: <ianfarrer@gmx.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADE5612D147 for <softwires@ietfa.amsl.com>; Thu,  9 Jun 2016 00:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 GI5A-62V9PPt for <softwires@ietfa.amsl.com>; Thu,  9 Jun 2016 00:44:45 -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 87C7F12B035 for <softwires@ietf.org>; Thu,  9 Jun 2016 00:44:44 -0700 (PDT)
Received: from ians-mbp.lan ([62.225.30.139]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LrqNe-1bazEU2ws2-013h3a; Thu, 09 Jun 2016 09:44:40 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_AAD1DC0F-BCCD-40E2-B6FD-829FF74B6EEB"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Ian Farrer <ianfarrer@gmx.com>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008DAF3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Date: Thu, 9 Jun 2016 09:44:39 +0200
Message-Id: <0B27AECD-13CD-4B05-A34C-70E901807D40@gmx.com>
References: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D5ABB288-99F9-4038-9E13-A9FC2ADAC0EF@gmx.com> <787AE7BB302AE849A7480A190F8B933008DAF3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.2104)
X-Provags-ID: V03:K0:58CtmtxOZqWLRfLVaeQa3iv02SZHFRaGtWTE15rE7IcXMVPoQvl pLeGFxRML4w7oTjbl65hcjyr2FPoHXLnJUVHcZd7/g236CfCStaN7xvYmZLkW1lX2I7y/jm AxBVdEGvrYdp0avajiZfXy6n0NwxqwgiPocV7Xrni5jhNgBarJMW82l0sFcFtG7PYqWs9QQ yaM30zvuOanmBc0iq0dng==
X-UI-Out-Filterresults: notjunk:1;V01:K0:89GrfwyV0Cw=:ekzRF9QupbIcok/Qo4tDoi uBCYsm4pm7YIwtnmxlo18qns4Z0yDmoV/awtBfSUgD5u7ATXTkFT+jr3g+sqY1yz+CSyIz1uF qDfyZ5Knab943+Twll6JUlfRWFDnMUXede8nN3vh0bXKPdntKbORBby7pfLa0erZji/6ASHip wipQtudT5LzoOD6Yo+HZel911gh03fdorSjwQrX7YKasl/O7UIr0az2FpgVx7yyoogiDeqUIT ZJJ7GDdthooEROYkEzjeU21G/f1VRJId0+JkrU21hXfncz3kD6UWD669C7nuvUWhdA54W9LUk lMJbCDG3AjXFTLKzxrOlB5zbmAw94PB89QSKh5wfYpt+EGeNftOY6l7Gz3hFp2Aqseiu1wA+T OCb8oG42XJ78OD1S2mHgNOG5PFmYVcbe4OcNjKzvXjizOz6TBQZ2+lsaCHoWOp2+PyC8C2DJ5 fbt47c3Z75KFEdsP6aGwB2E/XssOKzlwNPJH3QUBPQ9DcKapaxoVFY6YlSpb91zCCGzJETjbz pHmurmFkSqUcKLfYQyWz2iFZpkjOX63Jv5czJX6YYmyyi/aMcNNvPvYKPpFy2vt1tf4VQRtlW 5faKPF1ZZXFTrgyLZybSNXui8pQusHl8J/pNiyVXEddv+A8k3KkKFwR5MOJSozzRnegCbQcX5 tb1opq9hWTqv/ka9YdcO5rV4qRGOGBAXafJxRlifgtZuHfr8mXQ0q6P3C6xhFE+iwGw3dkv0/ 7B98+vpylaXhdGWam0o3aqWvLxzylP+RtgddP0sSZW11KQR+/SqdkeO4KT57+0m8ChMIJObmZ Vid0cuA
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/hXCWRFEHyuoDIQ10VEhCu7jBC08>
Cc: Softwires WG <softwires@ietf.org>, "dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
Subject: Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 07:44:48 -0000

--Apple-Mail=_AAD1DC0F-BCCD-40E2-B6FD-829FF74B6EEB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Med,

To be clear, both of the suggestions include the modification to the =
Section 5 client text? I think this is necessary. But is the error =
condition that all of the enclosed options are the same scope, or that =
two or more are?

Between the two, I would prefer (1) - a MUST NOT with an exception is a =
SHOULD NOT. An alternative wording that tries to get the best of both:

A server MUST NOT send more than on one instance of OPTION_V6_PREFIX64 =
per scope. Servers MAY send one instance of OPTION_V6_PREFIX64 for each =
distinct IPv6 multicast prefix with a distinct scope.=20

Thanks,
Ian

> On 9 Jun 2016, at 08:49, mohamed.boucadair@orange.com =
<mailto:mohamed.boucadair@orange.com> wrote:
>=20
> Hi Ian,
> =20
> There are two options:
> =20
> (1)
> =20
> Maintain the current text in the draft but add the following text to =
Section 4:
> =20
>    Servers SHOULD NOT send more than one instance of =
OPTION_V6_PREFIX64,
>    except if distinct IPv6 multicast prefixes with distinct scopes are
>    configured.
> =20
> This is the behavior defined in =
https://tools.ietf.org/html/rfc6334#section-5/ =
<https://tools.ietf.org/html/rfc6334#section-5/>.
> =20
> (2)
> =20
> Add this text in Section 4:
> =20
>    Servers MUST NOT send more than one instance of OPTION_V6_PREFIX64,
>    except if distinct IPv6 multicast prefixes with distinct scopes are
>    configured.
> =20
> And modify the text in Section 5 to indicate that the client must =
discard the options if all enclosed addresses are of the same scope.
> =20
> I agree with you that (2) will help to identify a server error, but =
with a risk to induce service disruptions.
> =20
> Which one do you prefer to be implemented in the draft?
> =20
> Thank you.
> =20
> Cheers,
> Med
> =20
> De : Ian Farrer [mailto:ianfarrer@gmx.com <mailto:ianfarrer@gmx.com>]=20=

> Envoy=C3=A9 : mercredi 8 juin 2016 19:10
> =C3=80 : BOUCADAIR Mohamed IMT/OLN; Softwires WG
> Cc : dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>
> Objet : Fwd: Problem in draft-ietf-softwire-multicast-prefix-option
> =20
> Hi Med,
> =20
> Forwarding this to the list (the left group mailing addresses were not =
working earlier).
> =20
> Please see inline below.
> =20
> Thanks,
> Ian
>=20
>=20
> Begin forwarded message:
> =20
> From: <mohamed.boucadair@orange.com =
<mailto:mohamed.boucadair@orange.com>>
> Subject: RE: Problem in draft-ietf-softwire-multicast-prefix-option
> Date: 8 June 2016 16:50:51 CEST
> To: ian Farrer <ianfarrer@gmx.com <mailto:ianfarrer@gmx.com>>, =
"softwires@ietf.org <mailto:softwires@ietf.org>" <softwires@ietf.org =
<mailto:softwires@ietf.org>>, Jacni Qin <jacni@jacni.com =
<mailto:jacni@jacni.com>>, "dxhbupt@gmail.com =
<mailto:dxhbupt@gmail.com>" <dxhbupt@gmail.com =
<mailto:dxhbupt@gmail.com>>
> Cc: "dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>" =
<dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>>
> =20
> Hi Ian,
> =20
> Please see inline.
> =20
> Cheers,
> Med
> =20
> De : ian Farrer [mailto:ianfarrer@gmx.com <mailto:ianfarrer@gmx.com>]=20=

> Envoy=C3=A9 : mercredi 8 juin 2016 16:11
> =C3=80 : softwires@ietf.org <mailto:softwires@ietf.org>; BOUCADAIR =
Mohamed IMT/OLN; Jacni Qin; dxhbupt@gmail.com <mailto:dxhbupt@gmail.com>
> Cc : dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>
> Objet : Problem in draft-ietf-softwire-multicast-prefix-option
> =20
> Hi,
> =20
> On reviewing this draft I would like to raise a problem with section 5 =
of the draft. The text is:
> =20
> "If all the enclosed IPv4-embedded IPv6 multicast prefixes have the =
same scope, the first instance of the option MUST be used."
> =20
> The problem is that this contravenes section 17 of RFC7227:
> Option order, either the order among many DHCPv6 options or the order
>    of multiple instances of the same option, SHOULD NOT be =
significant.
>    New documents MUST NOT assume any specific option processing order.
> =20
> [Med] That sentence does not assume any (preference) order. It does =
only provide one way to select one instance among that list. As a =
reminder, the server is supposed to return one instance (per scope).
> =20
> [if - If the client is taking the first occurrence within the option =
and attempting to configure it, then it is preferring this option over =
other instances based on the order in which it occurs in the message.
> =20
> The current text which describes the server behaviour (section 4) does =
not mention scope at all and does not specify any limitations on the =
number of instances or criteria for which they may be included - see =
RFC7227 sec 16.
> =20
> If the server is meant to only return a single instance of the option =
per scope, but it is sending more than one, then this is a server =
configuration error. A quasi-random mechanism for the client to try and =
work around this just means that the configuration error may get masked.
> =20
> As a suggestion, wouldn=E2=80=99t it be better to specify what the =
valid cases for the server including multiple option instances are and =
are not (with normative language). The client=E2=80=99s behaviour can =
then be defined to discard the options if they do not meet this =
criteria?]
>=20
>=20
> =20
> =20
> I raised this with the DHC WG chairs, and they have a couple of =
suggestions:
> =20
> 1. Define an encapsulating option - as the data inside an option can =
be order dependent.
> 2. Add a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can =
sort them based on this preference.
> =20
> Thanks,
> Ian


--Apple-Mail=_AAD1DC0F-BCCD-40E2-B6FD-829FF74B6EEB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Hi Med,</div><div class=3D""><br =
class=3D""></div><div class=3D"">To be clear, both of the suggestions =
include the modification to the Section 5 client text? I think this is =
necessary. But is the error condition that all of the enclosed options =
are the same scope, or that two or more are?</div><div class=3D""><br =
class=3D""></div><div class=3D"">Between the two, I would prefer (1) - a =
MUST NOT with an exception is a SHOULD NOT. An alternative wording that =
tries to get the best of both:</div><div class=3D""><br =
class=3D""></div><div class=3D"">A server MUST NOT send more than on one =
instance of OPTION_V6_PREFIX64 per scope. Servers MAY send one instance =
of OPTION_V6_PREFIX64 for each distinct IPv6 multicast prefix with a =
distinct scope.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">Ian</div><br class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 9 Jun =
2016, at 08:49, <a href=3D"mailto:mohamed.boucadair@orange.com" =
class=3D"">mohamed.boucadair@orange.com</a> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" class=3D"">Hi =
Ian,<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">There are two options:<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">(1)<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Maintain the current text in the draft but add the following =
text to Section 4:<o:p class=3D""></o:p></span></div><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">&nbsp;&nbsp; Servers =
SHOULD NOT send more than one instance of OPTION_V6_PREFIX64,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp; except if distinct IPv6 multicast prefixes with =
distinct scopes are<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">&nbsp;&nbsp; =
configured.<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
'Courier New';" class=3D"">This is the behavior defined in<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://tools.ietf.org/html/rfc6334#section-5/" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">https://tools.ietf.org/html/rfc6334#section-5/</a>.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">(2)<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">Add this text in Section =
4:<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp; Servers MUST NOT send more than =
one instance of OPTION_V6_PREFIX64,<o:p class=3D""></o:p></span></div><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">&nbsp;&nbsp; except if =
distinct IPv6 multicast prefixes with distinct scopes are<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">configured.<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">And modify the text in =
Section 5 to indicate that the client must discard the options if all =
enclosed addresses are of the same scope.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">I agree with you that (2) will help to identify a server =
error, but with a risk to induce service disruptions.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Which one do you prefer to be implemented in the draft?<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Thank you.<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">Cheers,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Med<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;</span></div><div =
style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0cm 0cm 0cm 4pt;" class=3D""><div =
class=3D""><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0cm 0cm;" class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><b =
class=3D""><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;" class=3D"">De&nbsp;:</span></b><span style=3D"font-size: =
10pt; font-family: Tahoma, sans-serif;" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>Ian Farrer [<a =
href=3D"mailto:ianfarrer@gmx.com" =
class=3D"">mailto:ianfarrer@gmx.com</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><b =
class=3D"">Envoy=C3=A9&nbsp;:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>mercredi 8 juin 2016 =
19:10<br class=3D""><b class=3D"">=C3=80&nbsp;:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>BOUCADAIR Mohamed IMT/OLN; =
Softwires WG<br class=3D""><b class=3D"">Cc&nbsp;:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dhcwg-chairs@ietf.org" =
class=3D"">dhcwg-chairs@ietf.org</a><br class=3D""><b =
class=3D"">Objet&nbsp;:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Fwd: Problem in =
draft-ietf-softwire-multicast-prefix-option<o:p =
class=3D""></o:p></span></div></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">Hi Med,<o:p class=3D""></o:p></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">Forwarding this to the list (the left group mailing =
addresses were not working earlier).<o:p class=3D""></o:p></div></div><div=
 class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">Please see inline below.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">Thanks,<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">Ian<o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">Begin forwarded message:<o:p =
class=3D""></o:p></div></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><b class=3D""><span style=3D"font-family: Helvetica, =
sans-serif;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-family: Helvetica, sans-serif;" class=3D"">&lt;<a =
href=3D"mailto:mohamed.boucadair@orange.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">mohamed.boucadair@orange.com</a>&gt;</span><o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><b class=3D""><span style=3D"font-family: Helvetica, =
sans-serif;" class=3D"">Subject: RE: Problem in =
draft-ietf-softwire-multicast-prefix-option</span></b><o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><b class=3D""><span style=3D"font-family: Helvetica, =
sans-serif;" class=3D"">Date:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-family: Helvetica, sans-serif;" class=3D"">8 June 2016 =
16:50:51 CEST</span><o:p class=3D""></o:p></div></div><div class=3D""><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><b class=3D""><span style=3D"font-family: =
Helvetica, sans-serif;" class=3D"">To:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-family: Helvetica, sans-serif;" class=3D"">ian Farrer =
&lt;<a href=3D"mailto:ianfarrer@gmx.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">ianfarrer@gmx.com</a>&gt;, "<a =
href=3D"mailto:softwires@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">softwires@ietf.org</a>" &lt;<a =
href=3D"mailto:softwires@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">softwires@ietf.org</a>&gt;, =
Jacni Qin &lt;<a href=3D"mailto:jacni@jacni.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">jacni@jacni.com</a>&gt;, "<a =
href=3D"mailto:dxhbupt@gmail.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">dxhbupt@gmail.com</a>" &lt;<a =
href=3D"mailto:dxhbupt@gmail.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">dxhbupt@gmail.com</a>&gt;</span><o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><b class=3D""><span style=3D"font-family: Helvetica, =
sans-serif;" class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-family: Helvetica, sans-serif;" class=3D"">"<a =
href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">dhcwg-chairs@ietf.org</a>" =
&lt;<a href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">dhcwg-chairs@ietf.org</a>&gt;</span><o:p =
class=3D""></o:p></div></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span style=3D"font-size: 10pt; =
font-family: 'Courier New';" class=3D"">Hi Ian,</span><o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" class=3D"">Please =
see inline.</span><o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span style=3D"font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;</span><o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Cheers,</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Med</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></div></div><div =
style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0cm 0cm 0cm 4pt;" class=3D""><div =
class=3D""><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0cm 0cm;" class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><b class=3D""><span style=3D"font-size: 10pt; font-family: =
Tahoma, sans-serif;" class=3D"">De&nbsp;:</span></b><span =
class=3D"apple-converted-space"><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif;" class=3D"">&nbsp;</span></span><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;" class=3D"">ian=
 Farrer [<a href=3D"mailto:ianfarrer@gmx.com" style=3D"color: purple; =
text-decoration: underline;" class=3D""><span style=3D"color: purple;" =
class=3D"">mailto:ianfarrer@gmx.com</span></a>]<span =
class=3D"apple-converted-space">&nbsp;</span><br class=3D""><b =
class=3D"">Envoy=C3=A9&nbsp;:</b><span =
class=3D"apple-converted-space">&nbsp;</span>mercredi 8 juin 2016 =
16:11<br class=3D""><b class=3D"">=C3=80&nbsp;:</b><span =
class=3D"apple-converted-space">&nbsp;</span><a =
href=3D"mailto:softwires@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D""><span style=3D"color: purple;" =
class=3D"">softwires@ietf.org</span></a>; BOUCADAIR Mohamed IMT/OLN; =
Jacni Qin;<span class=3D"apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dxhbupt@gmail.com" style=3D"color: purple; =
text-decoration: underline;" class=3D""><span style=3D"color: purple;" =
class=3D"">dxhbupt@gmail.com</span></a><br class=3D""><b =
class=3D"">Cc&nbsp;:</b><span =
class=3D"apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D""><span style=3D"color: purple;" =
class=3D"">dhcwg-chairs@ietf.org</span></a><br class=3D""><b =
class=3D"">Objet&nbsp;:</b><span =
class=3D"apple-converted-space">&nbsp;</span>Problem in =
draft-ietf-softwire-multicast-prefix-option</span><o:p =
class=3D""></o:p></div></div></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">Hi,</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></div></div></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" class=3D"">On =
reviewing this draft I would like to raise a problem with section 5 of =
the draft. The text is:</span><o:p class=3D""></o:p></div></div></div><div=
 class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></div></div></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" class=3D"">"If=
 all the enclosed IPv4-embedded IPv6 multicast prefixes have the same =
scope, the first instance of the option MUST be used."</span><o:p =
class=3D""></o:p></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span style=3D"font-size: 9pt; =
font-family: Verdana, sans-serif;" class=3D"">&nbsp;</span><o:p =
class=3D""></o:p></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span style=3D"font-size: 9pt; =
font-family: Verdana, sans-serif;" class=3D"">The problem is that this =
contravenes section 17 of RFC7227:</span><o:p =
class=3D""></o:p></div></div></div><div class=3D""><pre style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Option order, either the order among many DHCPv6 options or =
the order<o:p class=3D""></o:p></pre><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp; of multiple instances of the same option, SHOULD =
NOT be significant.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp; New documents MUST NOT assume any specific =
option processing order.<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D""><span lang=3D"EN-US" class=3D"">&nbsp;</span><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D""><span =
lang=3D"EN-US" class=3D"">[Med] That sentence does not assume any =
(preference) order. It does only provide one way to select one instance =
among that list. As a reminder, the server is supposed to return one =
instance (per scope).</span><o:p =
class=3D""></o:p></pre></div></div></div></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">[if - If the client is taking the first occurrence within the =
option and attempting to configure it, then it is preferring this option =
over other instances based on the order in which it occurs in the =
message.<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">The current text which describes the server behaviour =
(section 4) does not mention scope at all and does not specify any =
limitations on the number of instances or criteria for which they may be =
included - see RFC7227 sec 16.<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">If the server is meant to only return a single =
instance of the option per scope, but it is sending more than one, then =
this is a server configuration error. A quasi-random mechanism for the =
client to try and work around this just means that the configuration =
error may get masked.<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">As a suggestion, wouldn=E2=80=99t it be better to =
specify what the valid cases for the server including multiple option =
instances are and are not (with normative language). The client=E2=80=99s =
behaviour can then be defined to discard the options if they do not meet =
this criteria?]<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><div class=3D""><div style=3D"border-style: none =
none none solid; border-left-color: blue; border-left-width: 1.5pt; =
padding: 0cm 0cm 0cm 4pt;" class=3D""><div class=3D""><div class=3D""><div=
 class=3D""><pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D""><span lang=3D"EN-US" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></pre><pre style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D""><span lang=3D"EN-US" class=3D"">&nbsp;</span><o:p =
class=3D""></o:p></pre><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
9pt; font-family: Verdana, sans-serif;" class=3D"">I raised this with =
the DHC WG chairs, and they have a couple of suggestions:</span><o:p =
class=3D""></o:p></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
9pt; font-family: Verdana, sans-serif;" class=3D"">&nbsp;</span><o:p =
class=3D""></o:p></div></div></div></div><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" class=3D"">1. =
Define an encapsulating option - as the data i</span><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">nside an option can be order dependent.</span><o:p =
class=3D""></o:p></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><span style=3D"font-size: 9pt; =
font-family: Verdana, sans-serif;" class=3D"">2. Add a =E2=80=9Cpreference=
=E2=80=9D (octet?) and then a client can sort them based on&nbsp;this =
preference.</span><o:p class=3D""></o:p></div></div></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></div></div></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">Thanks,</span><o:p class=3D""></o:p></div></div></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 9pt; font-family: Verdana, sans-serif;" =
class=3D"">Ian</span></div></div></div></div></div></div></div></div></div=
></div></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_AAD1DC0F-BCCD-40E2-B6FD-829FF74B6EEB--


From nobody Thu Jun  9 05:35:00 2016
Return-Path: <mellon@fugue.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C85D612D0DE for <softwires@ietfa.amsl.com>; Thu,  9 Jun 2016 05:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 Ico463XJPyZY for <softwires@ietfa.amsl.com>; Thu,  9 Jun 2016 05:34:54 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8FF312D549 for <softwires@ietf.org>; Thu,  9 Jun 2016 05:34:53 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id j7so1608226lfg.1 for <softwires@ietf.org>; Thu, 09 Jun 2016 05:34:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6s67/AZqanWb7ktHdgmn+sGY7cdqkoCsuMllBv6rDM0=; b=iAzGgte+564kYPWgjgBTJ6gcfe8P9/GIiUBxM7QFZO4ZrLRrUMMOI7+dUwkZISYDFJ RZsoDsFmnIDVlRuHAbXqAcUMESs43l6xrhEOCgbKUVtbC0NaPaHfp7EUSDbQJD6M8FVj jPbOB3brykI0OpNQ1MaQKGj6mJiEVo0rlznhw5HECIWFburoK5fXtEDOQV4Pgj//dXeS bD6cuynPkLnxvipbTI2tf+MAFcJEhIh5EHMx0c+FYG/mjC9wyG0ftXCqIswIqVbPUVnt AFjO8RywGCUOMCs2imwdJ4APfH2zfYgx4WqAbha3PT5flqsQRwEpZPgj6najrhiIts9d wvcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6s67/AZqanWb7ktHdgmn+sGY7cdqkoCsuMllBv6rDM0=; b=ArSHI5PMdVFyYItLexiRaBQ4B9z8XAsdlDm0JWWaPE4FhIatEIx6wnnQ41Fnsa1XGj 8aZfPRVELkwqEnX6oNVg2HYq5n+khCS2qZYHgClOQdyhih2so1H/IBcUErZ/dztc8c3z 93WFJFOzo/p3MNW64UFmtcZV1nfeFTMUWbH0ZY62uoyn00i8yA20Pukhyj7aPLKAm3v+ ifAr1whLueOHDUtix2A7/ckdi3Mo1L8HXQJHmYvRTegGOthFt/v58u3mj+hS9qeJ3RAB 9WrT/GSMj3WJKlOBmijMkSEhB+8n9O97nDyh0t61baIgMljy8dgKmjm0ETfJviptaeuq 2GCQ==
X-Gm-Message-State: ALyK8tIsY4+hkkUHfLtAls3tcHUqRLdd25bUGoQqmblittaE1BCaxi03sBWRehIDo7xUCLRg/pn/uJRu+jvldA==
X-Received: by 10.25.91.76 with SMTP id p73mr931136lfb.181.1465475691772; Thu, 09 Jun 2016 05:34:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Thu, 9 Jun 2016 05:34:12 -0700 (PDT)
In-Reply-To: <0B27AECD-13CD-4B05-A34C-70E901807D40@gmx.com>
References: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D5ABB288-99F9-4038-9E13-A9FC2ADAC0EF@gmx.com> <787AE7BB302AE849A7480A190F8B933008DAF3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0B27AECD-13CD-4B05-A34C-70E901807D40@gmx.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 9 Jun 2016 08:34:12 -0400
Message-ID: <CAPt1N1=ZGhkG4jU1+iZGqjiCg6M2j0GOSogADNj4=pK8cxYwHg@mail.gmail.com>
To: Ian Farrer <ianfarrer@gmx.com>
Content-Type: multipart/alternative; boundary=001a11411536090ab10534d7a6fd
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/6vvn4jgTsRb3GdvFh5qjrplpG4U>
Cc: Softwires WG <softwires@ietf.org>, "dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
Subject: Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 12:34:59 -0000

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

Actually, this is a classic example of what we try to avoid: special server
behavior for options.   Options are just payload, not protocol, unless they
are intended to affect the flow of the protocol.   It should not be
necessary for the server to have special code to support a different
payload, any more than the TCP stack should have to be modified in order to
support new extensions to HTTP.

So you could make an operational note about how servers ought to be
configured, but you should not require that the server check to make sure
it is configured that way.   You should not require that the server
understand the semantics of the option--what it means for there to be two
of them, or what order they should occur in, or what meaning that ordering
has.

If you have two different uses for an option, with different semantics, you
should define two different options, each of which has only one semantics.

On Thu, Jun 9, 2016 at 3:44 AM, Ian Farrer <ianfarrer@gmx.com> wrote:

> Hi Med,
>
> To be clear, both of the suggestions include the modification to the
> Section 5 client text? I think this is necessary. But is the error
> condition that all of the enclosed options are the same scope, or that tw=
o
> or more are?
>
> Between the two, I would prefer (1) - a MUST NOT with an exception is a
> SHOULD NOT. An alternative wording that tries to get the best of both:
>
> A server MUST NOT send more than on one instance of OPTION_V6_PREFIX64 pe=
r
> scope. Servers MAY send one instance of OPTION_V6_PREFIX64 for each
> distinct IPv6 multicast prefix with a distinct scope.
>
> Thanks,
> Ian
>
> On 9 Jun 2016, at 08:49, mohamed.boucadair@orange.com wrote:
>
> Hi Ian,
>
> There are two options:
>
> (1)
>
> Maintain the current text in the draft but add the following text to
> Section 4:
>
>    Servers SHOULD NOT send more than one instance of OPTION_V6_PREFIX64,
>    except if distinct IPv6 multicast prefixes with distinct scopes are
>    configured.
>
> This is the behavior defined in
> https://tools.ietf.org/html/rfc6334#section-5/.
>
> (2)
>
> Add this text in Section 4:
>
>    Servers MUST NOT send more than one instance of OPTION_V6_PREFIX64,
>    except if distinct IPv6 multicast prefixes with distinct scopes are
>    configured.
>
> And modify the text in Section 5 to indicate that the client must discard
> the options if all enclosed addresses are of the same scope.
>
> I agree with you that (2) will help to identify a server error, but with =
a
> risk to induce service disruptions.
>
> Which one do you prefer to be implemented in the draft?
>
> Thank you.
>
> Cheers,
> Med
>
> *De :* Ian Farrer [mailto:ianfarrer@gmx.com <ianfarrer@gmx.com>]
> *Envoy=C3=A9 :* mercredi 8 juin 2016 19:10
> *=C3=80 :* BOUCADAIR Mohamed IMT/OLN; Softwires WG
> *Cc :* dhcwg-chairs@ietf.org
> *Objet :* Fwd: Problem in draft-ietf-softwire-multicast-prefix-option
>
> Hi Med,
>
> Forwarding this to the list (the left group mailing addresses were not
> working earlier).
>
> Please see inline below.
>
> Thanks,
> Ian
>
>
> Begin forwarded message:
>
> *From: *<mohamed.boucadair@orange.com>
> *Subject: RE: Problem in draft-ietf-softwire-multicast-prefix-option*
> *Date: *8 June 2016 16:50:51 CEST
> *To: *ian Farrer <ianfarrer@gmx.com>, "softwires@ietf.org" <
> softwires@ietf.org>, Jacni Qin <jacni@jacni.com>, "dxhbupt@gmail.com" <
> dxhbupt@gmail.com>
> *Cc: *"dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
>
> Hi Ian,
>
> Please see inline.
>
> Cheers,
> Med
>
> *De :* ian Farrer [mailto:ianfarrer@gmx.com <ianfarrer@gmx.com>]
> *Envoy=C3=A9 :* mercredi 8 juin 2016 16:11
> *=C3=80 :* softwires@ietf.org; BOUCADAIR Mohamed IMT/OLN; Jacni Qin;
> dxhbupt@gmail.com
> *Cc :* dhcwg-chairs@ietf.org
> *Objet :* Problem in draft-ietf-softwire-multicast-prefix-option
>
> Hi,
>
> On reviewing this draft I would like to raise a problem with section 5 of
> the draft. The text is:
>
> "If all the enclosed IPv4-embedded IPv6 multicast prefixes have the same
> scope, the first instance of the option MUST be used."
>
> The problem is that this contravenes section 17 of RFC7227:
>
> Option order, either the order among many DHCPv6 options or the order
>
>    of multiple instances of the same option, SHOULD NOT be significant.
>
>    New documents MUST NOT assume any specific option processing order.
>
>
>
> [Med] That sentence does not assume any (preference) order. It does only =
provide one way to select one instance among that list. As a reminder, the =
server is supposed to return one instance (per scope).
>
>
> [if - If the client is taking the first occurrence within the option and
> attempting to configure it, then it is preferring this option over other
> instances based on the order in which it occurs in the message.
>
> The current text which describes the server behaviour (section 4) does no=
t
> mention scope at all and does not specify any limitations on the number o=
f
> instances or criteria for which they may be included - see RFC7227 sec 16=
.
>
> If the server is meant to only return a single instance of the option per
> scope, but it is sending more than one, then this is a server configurati=
on
> error. A quasi-random mechanism for the client to try and work around thi=
s
> just means that the configuration error may get masked.
>
> As a suggestion, wouldn=E2=80=99t it be better to specify what the valid =
cases for
> the server including multiple option instances are and are not (with
> normative language). The client=E2=80=99s behaviour can then be defined t=
o discard
> the options if they do not meet this criteria?]
>
>
>
>
>
>
> I raised this with the DHC WG chairs, and they have a couple of
> suggestions:
>
> 1. Define an encapsulating option - as the data inside an option can be
> order dependent.
> 2. Add a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can sort=
 them based
> on this preference.
>
> Thanks,
> Ian
>
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>

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

<div dir=3D"ltr">Actually, this is a classic example of what we try to avoi=
d: special server behavior for options. =C2=A0 Options are just payload, no=
t protocol, unless they are intended to affect the flow of the protocol. =
=C2=A0 It should not be necessary for the server to have special code to su=
pport a different payload, any more than the TCP stack should have to be mo=
dified in order to support new extensions to HTTP.<div><br></div><div>So yo=
u could make an operational note about how servers ought to be configured, =
but you should not require that the server check to make sure it is configu=
red that way. =C2=A0 You should not require that the server understand the =
semantics of the option--what it means for there to be two of them, or what=
 order they should occur in, or what meaning that ordering has.</div><div><=
br></div><div>If you have two different uses for an option, with different =
semantics, you should define two different options, each of which has only =
one semantics.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Thu, Jun 9, 2016 at 3:44 AM, Ian Farrer <span dir=3D"ltr">&lt;<=
a href=3D"mailto:ianfarrer@gmx.com" target=3D"_blank">ianfarrer@gmx.com</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wra=
p:break-word"><div>Hi Med,</div><div><br></div><div>To be clear, both of th=
e suggestions include the modification to the Section 5 client text? I thin=
k this is necessary. But is the error condition that all of the enclosed op=
tions are the same scope, or that two or more are?</div><div><br></div><div=
>Between the two, I would prefer (1) - a MUST NOT with an exception is a SH=
OULD NOT. An alternative wording that tries to get the best of both:</div><=
div><br></div><div>A server MUST NOT send more than on one instance of OPTI=
ON_V6_PREFIX64 per scope. Servers MAY send one instance of OPTION_V6_PREFIX=
64 for each distinct IPv6 multicast prefix with a distinct scope.=C2=A0</di=
v><div><br></div><div>Thanks,</div><div>Ian</div><div><div class=3D"h5"><br=
><div><blockquote type=3D"cite"><div>On 9 Jun 2016, at 08:49, <a href=3D"ma=
ilto:mohamed.boucadair@orange.com" target=3D"_blank">mohamed.boucadair@oran=
ge.com</a> wrote:</div><br><div><div style=3D"font-family:Helvetica;font-si=
ze:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spa=
cing:normal;line-height:normal;text-align:start;text-indent:0px;text-transf=
orm:none;white-space:normal;word-spacing:0px"><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span =
style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">Hi Ian,<u></u><u=
></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font=
-family:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:10pt;font=
-family:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><s=
pan lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39=
;">There are two options:<u></u><u></u></span></div><div style=3D"margin:0c=
m 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">=
<span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#=
39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12p=
t;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=
=3D"font-size:10pt;font-family:&#39;Courier New&#39;">(1)<u></u><u></u></sp=
an></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&=
#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10p=
t;font-family:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier N=
ew&#39;">Maintain the current text in the draft but add the following text =
to Section 4:<u></u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001=
pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=
=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=
=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-f=
amily:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-s=
ize:10pt;font-family:&#39;Courier New&#39;">=C2=A0=C2=A0 Servers SHOULD NOT=
 send more than one instance of OPTION_V6_PREFIX64,<u></u><u></u></span></d=
iv><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Ti=
mes New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font=
-family:&#39;Courier New&#39;">=C2=A0=C2=A0 except if distinct IPv6 multica=
st prefixes with distinct scopes are<u></u><u></u></span></div><div style=
=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman=
&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;=
Courier New&#39;">=C2=A0=C2=A0 configured.<u></u><u></u></span></div><div s=
tyle=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New R=
oman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&=
#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.000=
1pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=
=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">This =
is the behavior defined in<span>=C2=A0</span><a href=3D"https://tools.ietf.=
org/html/rfc6334#section-5/" style=3D"color:purple;text-decoration:underlin=
e" target=3D"_blank">https://tools.ietf.org/html/rfc6334#section-5/</a>.<u>=
</u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12p=
t;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=
=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0</span></div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times N=
ew Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-fami=
ly:&#39;Courier New&#39;">(2)<u></u><u></u></span></div><div style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier N=
ew&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size=
:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" sty=
le=3D"font-size:10pt;font-family:&#39;Courier New&#39;">Add this text in Se=
ction 4:<u></u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;fo=
nt-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-=
US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0</span=
></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#3=
9;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;=
font-family:&#39;Courier New&#39;">=C2=A0=C2=A0 Servers MUST NOT send more =
than one instance of OPTION_V6_PREFIX64,<u></u><u></u></span></div><div sty=
le=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Rom=
an&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#3=
9;Courier New&#39;">=C2=A0=C2=A0 except if distinct IPv6 multicast prefixes=
 with distinct scopes are<u></u><u></u></span></div><div style=3D"margin:0c=
m 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">=
<span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#=
39;">=C2=A0=C2=A0<span>=C2=A0</span></span><span style=3D"font-size:10pt;fo=
nt-family:&#39;Courier New&#39;">configured.<u></u><u></u></span></div><div=
 style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New=
 Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family=
:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.0=
001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lan=
g=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">And =
modify the text in Section 5 to indicate that the client must discard the o=
ptions if all enclosed addresses are of the same scope.<u></u><u></u></span=
></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#3=
9;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;=
font-family:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:=
0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif=
"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New=
&#39;">I agree with you that (2) will help to identify a server error, but =
with a risk to induce service disruptions.<u></u><u></u></span></div><div s=
tyle=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New R=
oman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&=
#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.000=
1pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=
=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">Which=
 one do you prefer to be implemented in the draft?<u></u><u></u></span></di=
v><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Tim=
es New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-=
family:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0=
cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><sp=
an lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;=
">Thank you.<u></u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001p=
t;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D=
"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0</=
span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family=
:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:1=
0pt;font-family:&#39;Courier New&#39;">Cheers,<u></u><u></u></span></div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times N=
ew Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-fami=
ly:&#39;Courier New&#39;">Med<u></u><u></u></span></div><div style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier N=
ew&#39;">=C2=A0</span></div><div style=3D"border-style:none none none solid=
;border-left-color:blue;border-left-width:1.5pt;padding:0cm 0cm 0cm 4pt"><d=
iv><div style=3D"border-style:solid none none;border-top-color:rgb(181,196,=
223);border-top-width:1pt;padding:3pt 0cm 0cm"><div style=3D"margin:0cm 0cm=
 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><b><s=
pan style=3D"font-size:10pt;font-family:Tahoma,sans-serif">De=C2=A0:</span>=
</b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif"><span>=C2=
=A0</span>Ian Farrer [<a href=3D"mailto:ianfarrer@gmx.com" target=3D"_blank=
">mailto:ianfarrer@gmx.com</a>]<span>=C2=A0</span><br><b>Envoy=C3=A9=C2=A0:=
</b><span>=C2=A0</span>mercredi 8 juin 2016 19:10<br><b>=C3=80=C2=A0:</b><s=
pan>=C2=A0</span>BOUCADAIR Mohamed IMT/OLN; Softwires WG<br><b>Cc=C2=A0:</b=
><span>=C2=A0</span><a href=3D"mailto:dhcwg-chairs@ietf.org" target=3D"_bla=
nk">dhcwg-chairs@ietf.org</a><br><b>Objet=C2=A0:</b><span>=C2=A0</span>Fwd:=
 Problem in draft-ietf-softwire-multicast-prefix-option<u></u><u></u></span=
></div></div></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fon=
t-family:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div><div st=
yle=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Ro=
man&#39;,serif">Hi Med,<u></u><u></u></div><div><div style=3D"margin:0cm 0c=
m 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u><=
/u>=C2=A0<u></u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font=
-size:12pt;font-family:&#39;Times New Roman&#39;,serif">Forwarding this to =
the list (the left group mailing addresses were not working earlier).<u></u=
><u></u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12=
pt;font-family:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div><=
/div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:=
&#39;Times New Roman&#39;,serif">Please see inline below.<u></u><u></u></di=
v></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fami=
ly:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div></div><div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times N=
ew Roman&#39;,serif">Thanks,<u></u><u></u></div></div><div><div style=3D"ma=
rgin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,=
serif">Ian<u></u><u></u></div></div><div><div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><br><b=
r><u></u><u></u></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:=
12pt;font-family:&#39;Times New Roman&#39;,serif">Begin forwarded message:<=
u></u><u></u></div></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12=
pt;font-family:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div><=
div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;T=
imes New Roman&#39;,serif"><b><span style=3D"font-family:Helvetica,sans-ser=
if">From:<span>=C2=A0</span></span></b><span style=3D"font-family:Helvetica=
,sans-serif">&lt;<a href=3D"mailto:mohamed.boucadair@orange.com" style=3D"c=
olor:purple;text-decoration:underline" target=3D"_blank">mohamed.boucadair@=
orange.com</a>&gt;</span><u></u><u></u></div></div><div><div style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if"><b><span style=3D"font-family:Helvetica,sans-serif">Subject: RE: Proble=
m in draft-ietf-softwire-multicast-prefix-option</span></b><u></u><u></u></=
div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fa=
mily:&#39;Times New Roman&#39;,serif"><b><span style=3D"font-family:Helveti=
ca,sans-serif">Date:<span>=C2=A0</span></span></b><span style=3D"font-famil=
y:Helvetica,sans-serif">8 June 2016 16:50:51 CEST</span><u></u><u></u></div=
></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-famil=
y:&#39;Times New Roman&#39;,serif"><b><span style=3D"font-family:Helvetica,=
sans-serif">To:<span>=C2=A0</span></span></b><span style=3D"font-family:Hel=
vetica,sans-serif">ian Farrer &lt;<a href=3D"mailto:ianfarrer@gmx.com" styl=
e=3D"color:purple;text-decoration:underline" target=3D"_blank">ianfarrer@gm=
x.com</a>&gt;, &quot;<a href=3D"mailto:softwires@ietf.org" style=3D"color:p=
urple;text-decoration:underline" target=3D"_blank">softwires@ietf.org</a>&q=
uot; &lt;<a href=3D"mailto:softwires@ietf.org" style=3D"color:purple;text-d=
ecoration:underline" target=3D"_blank">softwires@ietf.org</a>&gt;, Jacni Qi=
n &lt;<a href=3D"mailto:jacni@jacni.com" style=3D"color:purple;text-decorat=
ion:underline" target=3D"_blank">jacni@jacni.com</a>&gt;, &quot;<a href=3D"=
mailto:dxhbupt@gmail.com" style=3D"color:purple;text-decoration:underline" =
target=3D"_blank">dxhbupt@gmail.com</a>&quot; &lt;<a href=3D"mailto:dxhbupt=
@gmail.com" style=3D"color:purple;text-decoration:underline" target=3D"_bla=
nk">dxhbupt@gmail.com</a>&gt;</span><u></u><u></u></div></div><div><div sty=
le=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Rom=
an&#39;,serif"><b><span style=3D"font-family:Helvetica,sans-serif">Cc:<span=
>=C2=A0</span></span></b><span style=3D"font-family:Helvetica,sans-serif">&=
quot;<a href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color:purple;text-de=
coration:underline" target=3D"_blank">dhcwg-chairs@ietf.org</a>&quot; &lt;<=
a href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color:purple;text-decorati=
on:underline" target=3D"_blank">dhcwg-chairs@ietf.org</a>&gt;</span><u></u>=
<u></u></div></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fon=
t-family:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div><div><d=
iv><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Ti=
mes New Roman&#39;,serif"><span style=3D"font-size:10pt;font-family:&#39;Co=
urier New&#39;">Hi Ian,</span><u></u><u></u></div></div><div><div style=3D"=
margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39=
;,serif"><span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=
=C2=A0</span><u></u><u></u></div></div><div><div style=3D"margin:0cm 0cm 0.=
0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span st=
yle=3D"font-size:10pt;font-family:&#39;Courier New&#39;">Please see inline.=
</span><u></u><u></u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt=
;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span style=3D=
"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0</span><u></u><u><=
/u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fo=
nt-family:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:10pt;fo=
nt-family:&#39;Courier New&#39;">Cheers,</span><u></u><u></u></div></div><d=
iv><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Ti=
mes New Roman&#39;,serif"><span style=3D"font-size:10pt;font-family:&#39;Co=
urier New&#39;">Med</span><u></u><u></u></div></div><div><div style=3D"marg=
in:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,se=
rif"><span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=
=A0</span><u></u><u></u></div></div><div style=3D"border-style:none none no=
ne solid;border-left-color:blue;border-left-width:1.5pt;padding:0cm 0cm 0cm=
 4pt"><div><div style=3D"border-style:solid none none;border-top-color:rgb(=
181,196,223);border-top-width:1pt;padding:3pt 0cm 0cm"><div><div style=3D"m=
argin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;=
,serif"><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif">De=
=C2=A0:</span></b><span><span style=3D"font-size:10pt;font-family:Tahoma,sa=
ns-serif">=C2=A0</span></span><span style=3D"font-size:10pt;font-family:Tah=
oma,sans-serif">ian Farrer [<a href=3D"mailto:ianfarrer@gmx.com" style=3D"c=
olor:purple;text-decoration:underline" target=3D"_blank"><span style=3D"col=
or:purple">mailto:ianfarrer@gmx.com</span></a>]<span>=C2=A0</span><br><b>En=
voy=C3=A9=C2=A0:</b><span>=C2=A0</span>mercredi 8 juin 2016 16:11<br><b>=C3=
=80=C2=A0:</b><span>=C2=A0</span><a href=3D"mailto:softwires@ietf.org" styl=
e=3D"color:purple;text-decoration:underline" target=3D"_blank"><span style=
=3D"color:purple">softwires@ietf.org</span></a>; BOUCADAIR Mohamed IMT/OLN;=
 Jacni Qin;<span>=C2=A0</span><a href=3D"mailto:dxhbupt@gmail.com" style=3D=
"color:purple;text-decoration:underline" target=3D"_blank"><span style=3D"c=
olor:purple">dxhbupt@gmail.com</span></a><br><b>Cc=C2=A0:</b><span>=C2=A0</=
span><a href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color:purple;text-de=
coration:underline" target=3D"_blank"><span style=3D"color:purple">dhcwg-ch=
airs@ietf.org</span></a><br><b>Objet=C2=A0:</b><span>=C2=A0</span>Problem i=
n draft-ietf-softwire-multicast-prefix-option</span><u></u><u></u></div></d=
iv></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fo=
nt-family:&#39;Times New Roman&#39;,serif">=C2=A0<u></u><u></u></div></div>=
<div><div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fa=
mily:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:9pt;font-fam=
ily:Verdana,sans-serif">Hi,</span><u></u><u></u></div></div><div><div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New =
Roman&#39;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-ser=
if">=C2=A0</span><u></u><u></u></div></div></div><div><div><div style=3D"ma=
rgin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,=
serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">On revi=
ewing this draft I would like to raise a problem with section 5 of the draf=
t. The text is:</span><u></u><u></u></div></div></div><div><div><div style=
=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman=
&#39;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">=
=C2=A0</span><u></u><u></u></div></div></div><div><div><div style=3D"margin=
:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,seri=
f"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">&quot;If al=
l the enclosed IPv4-embedded IPv6 multicast prefixes have the same scope, t=
he first instance of the option MUST be used.&quot;</span><u></u><u></u></d=
iv></div></div><div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12=
pt;font-family:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:9p=
t;font-family:Verdana,sans-serif">=C2=A0</span><u></u><u></u></div></div></=
div><div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fam=
ily:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:9pt;font-fami=
ly:Verdana,sans-serif">The problem is that this contravenes section 17 of R=
FC7227:</span><u></u><u></u></div></div></div><div><pre style=3D"margin:0cm=
 0cm 0.0001pt;font-size:10pt;font-family:&#39;Courier New&#39;">Option orde=
r, either the order among many DHCPv6 options or the order<u></u><u></u></p=
re><pre style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:&#39;Co=
urier New&#39;">=C2=A0=C2=A0 of multiple instances of the same option, SHOU=
LD NOT be significant.<u></u><u></u></pre><pre style=3D"margin:0cm 0cm 0.00=
01pt;font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0=C2=A0 New doc=
uments MUST NOT assume any specific option processing order.<u></u><u></u><=
/pre><pre style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:&#39;=
Courier New&#39;"><span lang=3D"EN-US">=C2=A0</span><u></u><u></u></pre><pr=
e style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:&#39;Courier =
New&#39;"><span lang=3D"EN-US">[Med] That sentence does not assume any (pre=
ference) order. It does only provide one way to select one instance among t=
hat list. As a reminder, the server is supposed to return one instance (per=
 scope).</span><u></u><u></u></pre></div></div></div></div></div><div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New =
Roman&#39;,serif"><u></u>=C2=A0<u></u></div></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">[i=
f - If the client is taking the first occurrence within the option and atte=
mpting to configure it, then it is preferring this option over other instan=
ces based on the order in which it occurs in the message.<u></u><u></u></di=
v></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fami=
ly:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div></div><div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times N=
ew Roman&#39;,serif">The current text which describes the server behaviour =
(section 4) does not mention scope at all and does not specify any limitati=
ons on the number of instances or criteria for which they may be included -=
 see RFC7227 sec 16.<u></u><u></u></div></div><div><div style=3D"margin:0cm=
 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><=
u></u>=C2=A0<u></u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;f=
ont-size:12pt;font-family:&#39;Times New Roman&#39;,serif">If the server is=
 meant to only return a single instance of the option per scope, but it is =
sending more than one, then this is a server configuration error. A quasi-r=
andom mechanism for the client to try and work around this just means that =
the configuration error may get masked.<u></u><u></u></div></div><div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New =
Roman&#39;,serif"><u></u>=C2=A0<u></u></div></div><div><div style=3D"margin=
:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,seri=
f">As a suggestion, wouldn=E2=80=99t it be better to specify what the valid=
 cases for the server including multiple option instances are and are not (=
with normative language). The client=E2=80=99s behaviour can then be define=
d to discard the options if they do not meet this criteria?]<u></u><u></u><=
/div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-f=
amily:&#39;Times New Roman&#39;,serif"><br><br><u></u><u></u></div><div><di=
v style=3D"border-style:none none none solid;border-left-color:blue;border-=
left-width:1.5pt;padding:0cm 0cm 0cm 4pt"><div><div><div><pre style=3D"marg=
in:0cm 0cm 0.0001pt;font-size:10pt;font-family:&#39;Courier New&#39;"><span=
 lang=3D"EN-US">=C2=A0</span><u></u><u></u></pre><pre style=3D"margin:0cm 0=
cm 0.0001pt;font-size:10pt;font-family:&#39;Courier New&#39;"><span lang=3D=
"EN-US">=C2=A0</span><u></u><u></u></pre><div><div><div style=3D"margin:0cm=
 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><=
span lang=3D"EN-US" style=3D"font-size:9pt;font-family:Verdana,sans-serif">=
I raised this with the DHC WG chairs, and they have a couple of suggestions=
:</span><u></u><u></u></div></div></div><div><div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><s=
pan lang=3D"EN-US" style=3D"font-size:9pt;font-family:Verdana,sans-serif">=
=C2=A0</span><u></u><u></u></div></div></div></div><div><div><div style=3D"=
margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39=
;,serif"><span lang=3D"EN-US" style=3D"font-size:9pt;font-family:Verdana,sa=
ns-serif">1. Define an encapsulating option - as the data i</span><span sty=
le=3D"font-size:9pt;font-family:Verdana,sans-serif">nside an option can be =
order dependent.</span><u></u><u></u></div></div></div><div><div><div style=
=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman=
&#39;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">2=
. Add a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can sort th=
em based on=C2=A0this preference.</span><u></u><u></u></div></div></div><di=
v><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#3=
9;Times New Roman&#39;,serif"><span style=3D"font-size:9pt;font-family:Verd=
ana,sans-serif">=C2=A0</span><u></u><u></u></div></div></div><div><div><div=
 style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New=
 Roman&#39;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-se=
rif">Thanks,</span><u></u><u></u></div></div></div><div><div><div style=3D"=
margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39=
;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">Ian</=
span></div></div></div></div></div></div></div></div></div></div></div></di=
v></blockquote></div><br></div></div></div><br>____________________________=
___________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org">Softwires@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" rel=3D"noreferr=
er" target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><b=
r>
<br></blockquote></div><br></div>

--001a11411536090ab10534d7a6fd--


From nobody Thu Jun  9 06:08:44 2016
Return-Path: <ianfarrer@gmx.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 116F312D60A for <softwires@ietfa.amsl.com>; Thu,  9 Jun 2016 06:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 x8qHvktsjF7x for <softwires@ietfa.amsl.com>; Thu,  9 Jun 2016 06:08:36 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 C30D112D5FF for <softwires@ietf.org>; Thu,  9 Jun 2016 06:08:35 -0700 (PDT)
Received: from ians-mbp.lan ([62.225.30.3]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MUpI8-1awbYI3mmq-00YBxk; Thu, 09 Jun 2016 15:08:31 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_50E33E49-D4EC-41D3-9597-F1E59862F46F"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Ian Farrer <ianfarrer@gmx.com>
In-Reply-To: <CAPt1N1=ZGhkG4jU1+iZGqjiCg6M2j0GOSogADNj4=pK8cxYwHg@mail.gmail.com>
Date: Thu, 9 Jun 2016 15:08:29 +0200
Message-Id: <2CDDF3C1-1F18-4621-8223-9CD5ADCBDDD1@gmx.com>
References: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D5ABB288-99F9-4038-9E13-A9FC2ADAC0EF@gmx.com> <787AE7BB302AE849A7480A190F8B933008DAF3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0B27AECD-13CD-4B05-A34C-70E901807D40@gmx.com> <CAPt1N1=ZGhkG4jU1+iZGqjiCg6M2j0GOSogADNj4=pK8cxYwHg@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.2104)
X-Provags-ID: V03:K0:9fWe3SwiixYtKm7J3NOnuaPX3I8TrTWloyDXUU5v8GrzNrXFTP0 v7uyPP35mzCsGSxtk8SHSl0H79e0jTQxfGy1Pw3D0ZCSC0Qn0JnQQ7Z3BMAftOpL9oZBJWw xmhShEUuuCoBp7G+oKhZTkD3cBHnttKEyke+rLe8j4rDTUIJBKuZcYhCOhC0YW0R+tYxxRA H6mXj5Ahgs2STMDVO5LLg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:yzppK9KeN7Q=:EHlPf3Hs+DSYax1+OJON2y f8h4zrwg0rIAjViweBqTATFHw5qEuleNBgp8FQryM+KVzdG8SuhFTjqUsG7OVsnBfxW+7QvwQ w/swWP8gN9iKkGTqhx+ZZDUxHEHImZXulT18gR3ahrX/p/ryGjlxce/XKPxYAJDrXQDMaX6QI eDiOuzvYS0YfugzST6LQMW74t6agVJyelzyuTuZkp/TjBR26VLsNeu4fj28sN858zcDcsib/z 4MBJxW5JuKXoTS3BLBrwrzVnTbpeguyMi4ibAjQZ954yu34kxN52nAH91SnJnMvzQzFMqb2sK 3EZwWDjzPqFR15+HUmfyUuPtMN3Sh8E7DjrotXWzvPWp3lonIAuQ/plOHWh/D7yBv0UktflM9 z+Q1Wf/jLmQspkQlC3aX3MizaaXz6Jij2EbMQZPjfeWmU/3YwqoENbuhFnxdn9baS4s/fnBPF aNZjFxC8qWWj4tuYyAMkmEl4IB4koWp18/1FfZzP2Lv0wlnj0xH/YmqWAOF3gfhSTj1RRW1iR kmLhWx3ar+ncBHzyxz56es0kp1VkJXdiyqrV+9WnsdOeaqY/sNMr9pLzrcss9mV8sprO/HLQA vYPVUdlKjSfPfA2oTUy7flIj+hgDJKOZRqBewLE3qYX3WN0XenB53WXe6cDv+8JvCgODBIimm dcIor1W/ffIgqUaPMhYr63zq5V44fRRmUsenf/V4FvXA/Lqh59KnEF4SSY5X6EkgXIitFlemb 4G2etVovGzInM+vllm5DEI6E95mKN4ONAn5g6ZAYAbeLH9yWlKLKquckzYDUIn1ISllEeHmKJ 1njcaJY
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/P3W8ZLhxc4JAn1ZKUSsier_4bXg>
Cc: Softwires WG <softwires@ietf.org>, "dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
Subject: Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 13:08:41 -0000

--Apple-Mail=_50E33E49-D4EC-41D3-9597-F1E59862F46F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

HI Ted,

Cheers,
Ian

> On 9 Jun 2016, at 14:34, Ted Lemon <mellon@fugue.com> wrote:
>=20
> Actually, this is a classic example of what we try to avoid: special =
server behavior for options.   Options are just payload, not protocol, =
unless they are intended to affect the flow of the protocol.   It should =
not be necessary for the server to have special code to support a =
different payload, any more than the TCP stack should have to be =
modified in order to support new extensions to HTTP.
>=20
> So you could make an operational note about how servers ought to be =
configured, but you should not require that the server check to make =
sure it is configured that way.   You should not require that the server =
understand the semantics of the option--what it means for there to be =
two of them, or what order they should occur in, or what meaning that =
ordering has.

[if - So, for the original reason that the point was raised, do you =
suggest that enforcing this only in the client (i.e. if it receives an =
invalid option combination/content then drop all instances) in addition =
to the operation guidance for server config?]


>=20
> If you have two different uses for an option, with different =
semantics, you should define two different options, each of which has =
only one semantics.
>=20
> On Thu, Jun 9, 2016 at 3:44 AM, Ian Farrer <ianfarrer@gmx.com =
<mailto:ianfarrer@gmx.com>> wrote:
> Hi Med,
>=20
> To be clear, both of the suggestions include the modification to the =
Section 5 client text? I think this is necessary. But is the error =
condition that all of the enclosed options are the same scope, or that =
two or more are?
>=20
> Between the two, I would prefer (1) - a MUST NOT with an exception is =
a SHOULD NOT. An alternative wording that tries to get the best of both:
>=20
> A server MUST NOT send more than on one instance of OPTION_V6_PREFIX64 =
per scope. Servers MAY send one instance of OPTION_V6_PREFIX64 for each =
distinct IPv6 multicast prefix with a distinct scope.=20
>=20
> Thanks,
> Ian
>=20
>> On 9 Jun 2016, at 08:49, mohamed.boucadair@orange.com =
<mailto:mohamed.boucadair@orange.com> wrote:
>>=20
>> Hi Ian,
>> =20
>> There are two options:
>> =20
>> (1)
>> =20
>> Maintain the current text in the draft but add the following text to =
Section 4:
>> =20
>>    Servers SHOULD NOT send more than one instance of =
OPTION_V6_PREFIX64,
>>    except if distinct IPv6 multicast prefixes with distinct scopes =
are
>>    configured.
>> =20
>> This is the behavior defined in =
https://tools.ietf.org/html/rfc6334#section-5/ =
<https://tools.ietf.org/html/rfc6334#section-5/>.
>> =20
>> (2)
>> =20
>> Add this text in Section 4:
>> =20
>>    Servers MUST NOT send more than one instance of =
OPTION_V6_PREFIX64,
>>    except if distinct IPv6 multicast prefixes with distinct scopes =
are
>>    configured.
>> =20
>> And modify the text in Section 5 to indicate that the client must =
discard the options if all enclosed addresses are of the same scope.
>> =20
>> I agree with you that (2) will help to identify a server error, but =
with a risk to induce service disruptions.
>> =20
>> Which one do you prefer to be implemented in the draft?
>> =20
>> Thank you.
>> =20
>> Cheers,
>> Med
>> =20
>> De : Ian Farrer [mailto:ianfarrer@gmx.com <mailto:ianfarrer@gmx.com>]=20=

>> Envoy=C3=A9 : mercredi 8 juin 2016 19:10
>> =C3=80 : BOUCADAIR Mohamed IMT/OLN; Softwires WG
>> Cc : dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>
>> Objet : Fwd: Problem in draft-ietf-softwire-multicast-prefix-option
>> =20
>> Hi Med,
>> =20
>> Forwarding this to the list (the left group mailing addresses were =
not working earlier).
>> =20
>> Please see inline below.
>> =20
>> Thanks,
>> Ian
>>=20
>>=20
>> Begin forwarded message:
>> =20
>> From: <mohamed.boucadair@orange.com =
<mailto:mohamed.boucadair@orange.com>>
>> Subject: RE: Problem in draft-ietf-softwire-multicast-prefix-option
>> Date: 8 June 2016 16:50:51 CEST
>> To: ian Farrer <ianfarrer@gmx.com <mailto:ianfarrer@gmx.com>>, =
"softwires@ietf.org <mailto:softwires@ietf.org>" <softwires@ietf.org =
<mailto:softwires@ietf.org>>, Jacni Qin <jacni@jacni.com =
<mailto:jacni@jacni.com>>, "dxhbupt@gmail.com =
<mailto:dxhbupt@gmail.com>" <dxhbupt@gmail.com =
<mailto:dxhbupt@gmail.com>>
>> Cc: "dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>" =
<dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>>
>> =20
>> Hi Ian,
>> =20
>> Please see inline.
>> =20
>> Cheers,
>> Med
>> =20
>> De : ian Farrer [mailto:ianfarrer@gmx.com <mailto:ianfarrer@gmx.com>]=20=

>> Envoy=C3=A9 : mercredi 8 juin 2016 16:11
>> =C3=80 : softwires@ietf.org <mailto:softwires@ietf.org>; BOUCADAIR =
Mohamed IMT/OLN; Jacni Qin; dxhbupt@gmail.com <mailto:dxhbupt@gmail.com>
>> Cc : dhcwg-chairs@ietf.org <mailto:dhcwg-chairs@ietf.org>
>> Objet : Problem in draft-ietf-softwire-multicast-prefix-option
>> =20
>> Hi,
>> =20
>> On reviewing this draft I would like to raise a problem with section =
5 of the draft. The text is:
>> =20
>> "If all the enclosed IPv4-embedded IPv6 multicast prefixes have the =
same scope, the first instance of the option MUST be used."
>> =20
>> The problem is that this contravenes section 17 of RFC7227:
>> Option order, either the order among many DHCPv6 options or the order
>>    of multiple instances of the same option, SHOULD NOT be =
significant.
>>    New documents MUST NOT assume any specific option processing =
order.
>> =20
>> [Med] That sentence does not assume any (preference) order. It does =
only provide one way to select one instance among that list. As a =
reminder, the server is supposed to return one instance (per scope).
>> =20
>> [if - If the client is taking the first occurrence within the option =
and attempting to configure it, then it is preferring this option over =
other instances based on the order in which it occurs in the message.
>> =20
>> The current text which describes the server behaviour (section 4) =
does not mention scope at all and does not specify any limitations on =
the number of instances or criteria for which they may be included - see =
RFC7227 sec 16.
>> =20
>> If the server is meant to only return a single instance of the option =
per scope, but it is sending more than one, then this is a server =
configuration error. A quasi-random mechanism for the client to try and =
work around this just means that the configuration error may get masked.
>> =20
>> As a suggestion, wouldn=E2=80=99t it be better to specify what the =
valid cases for the server including multiple option instances are and =
are not (with normative language). The client=E2=80=99s behaviour can =
then be defined to discard the options if they do not meet this =
criteria?]
>>=20
>>=20
>> =20
>> =20
>> I raised this with the DHC WG chairs, and they have a couple of =
suggestions:
>> =20
>> 1. Define an encapsulating option - as the data inside an option can =
be order dependent.
>> 2. Add a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can =
sort them based on this preference.
>> =20
>> Thanks,
>> Ian
>=20
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org <mailto:Softwires@ietf.org>
> https://www.ietf.org/mailman/listinfo/softwires =
<https://www.ietf.org/mailman/listinfo/softwires>
>=20
>=20


--Apple-Mail=_50E33E49-D4EC-41D3-9597-F1E59862F46F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">HI Ted,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Cheers,</div><div class=3D"">Ian</div><br=
 class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
9 Jun 2016, at 14:34, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com" =
class=3D"">mellon@fugue.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">Actually, this is a classic example of what we try to avoid: =
special server behavior for options. &nbsp; Options are just payload, =
not protocol, unless they are intended to affect the flow of the =
protocol. &nbsp; It should not be necessary for the server to have =
special code to support a different payload, any more than the TCP stack =
should have to be modified in order to support new extensions to =
HTTP.<div class=3D""><br class=3D""></div><div class=3D"">So you could =
make an operational note about how servers ought to be configured, but =
you should not require that the server check to make sure it is =
configured that way. &nbsp; You should not require that the server =
understand the semantics of the option--what it means for there to be =
two of them, or what order they should occur in, or what meaning that =
ordering has.</div></div></div></blockquote><div><br =
class=3D""></div><div>[if - So, for the original reason that the point =
was raised, do you suggest that enforcing this only in the client (i.e. =
if it receives an invalid option combination/content then drop all =
instances) in addition to the operation guidance for server =
config?]</div><div><br class=3D""></div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D""><br class=3D""></div><div class=3D"">If you have two =
different uses for an option, with different semantics, you should =
define two different options, each of which has only one =
semantics.</div></div><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Thu, Jun 9, 2016 at 3:44 AM, Ian Farrer <span =
dir=3D"ltr" class=3D"">&lt;<a href=3D"mailto:ianfarrer@gmx.com" =
target=3D"_blank" class=3D"">ianfarrer@gmx.com</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word" class=3D""><div class=3D"">Hi =
Med,</div><div class=3D""><br class=3D""></div><div class=3D"">To be =
clear, both of the suggestions include the modification to the Section 5 =
client text? I think this is necessary. But is the error condition that =
all of the enclosed options are the same scope, or that two or more =
are?</div><div class=3D""><br class=3D""></div><div class=3D"">Between =
the two, I would prefer (1) - a MUST NOT with an exception is a SHOULD =
NOT. An alternative wording that tries to get the best of =
both:</div><div class=3D""><br class=3D""></div><div class=3D"">A server =
MUST NOT send more than on one instance of OPTION_V6_PREFIX64 per scope. =
Servers MAY send one instance of OPTION_V6_PREFIX64 for each distinct =
IPv6 multicast prefix with a distinct scope.&nbsp;</div><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Ian</div><div class=3D""><div class=3D"h5"><br class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 9 Jun =
2016, at 08:49, <a href=3D"mailto:mohamed.boucadair@orange.com" =
target=3D"_blank" class=3D"">mohamed.boucadair@orange.com</a> =
wrote:</div><br class=3D""><div class=3D""><div =
style=3D"font-family:Helvetica;font-size:12px;font-style:normal;font-varia=
nt:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text=
-align:start;text-indent:0px;text-transform:none;white-space:normal;word-s=
pacing:0px" class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">Hi Ian,<u class=3D""></u><u class=3D""></u></span></div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">There are =
two options:<u class=3D""></u><u class=3D""></u></span></div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">(1)<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">Maintain =
the current text in the draft but add the following text to Section 4:<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">&nbsp;&nbsp;=
 Servers SHOULD NOT send more than one instance of OPTION_V6_PREFIX64,<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">&nbsp;&nbsp;=
 except if distinct IPv6 multicast prefixes with distinct scopes are<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">&nbsp;&nbsp;=
 configured.<u class=3D""></u><u class=3D""></u></span></div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">This is =
the behavior defined in<span class=3D"">&nbsp;</span><a =
href=3D"https://tools.ietf.org/html/rfc6334#section-5/" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/rfc6334#section-5/</a>.<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">(2)<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">Add this =
text in Section 4:<u class=3D""></u><u class=3D""></u></span></div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">&nbsp;&nbsp;=
 Servers MUST NOT send more than one instance of OPTION_V6_PREFIX64,<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">&nbsp;&nbsp;=
 except if distinct IPv6 multicast prefixes with distinct scopes are<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;&nbsp;<span class=3D"">&nbsp;</span></span><span =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">configured.<u class=3D""></u><u =
class=3D""></u></span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">And modify =
the text in Section 5 to indicate that the client must discard the =
options if all enclosed addresses are of the same scope.<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">I agree =
with you that (2) will help to identify a server error, but with a risk =
to induce service disruptions.<u class=3D""></u><u =
class=3D""></u></span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">Which one =
do you prefer to be implemented in the draft?<u class=3D""></u><u =
class=3D""></u></span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">Thank =
you.<u class=3D""></u><u class=3D""></u></span></div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">Cheers,<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" class=3D"">Med<u =
class=3D""></u><u class=3D""></u></span></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span></div><div style=3D"border-style:none none none =
solid;border-left-color:blue;border-left-width:1.5pt;padding:0cm 0cm 0cm =
4pt" class=3D""><div class=3D""><div style=3D"border-style:solid none =
none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt =
0cm 0cm" class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><b=
 class=3D""><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" =
class=3D"">De&nbsp;:</span></b><span =
style=3D"font-size:10pt;font-family:Tahoma,sans-serif" class=3D""><span =
class=3D"">&nbsp;</span>Ian Farrer [<a href=3D"mailto:ianfarrer@gmx.com" =
target=3D"_blank" class=3D"">mailto:ianfarrer@gmx.com</a>]<span =
class=3D"">&nbsp;</span><br class=3D""><b =
class=3D"">Envoy=C3=A9&nbsp;:</b><span class=3D"">&nbsp;</span>mercredi =
8 juin 2016 19:10<br class=3D""><b class=3D"">=C3=80&nbsp;:</b><span =
class=3D"">&nbsp;</span>BOUCADAIR Mohamed IMT/OLN; Softwires WG<br =
class=3D""><b class=3D"">Cc&nbsp;:</b><span class=3D"">&nbsp;</span><a =
href=3D"mailto:dhcwg-chairs@ietf.org" target=3D"_blank" =
class=3D"">dhcwg-chairs@ietf.org</a><br class=3D""><b =
class=3D"">Objet&nbsp;:</b><span class=3D"">&nbsp;</span>Fwd: Problem in =
draft-ietf-softwire-multicast-prefix-option<u class=3D""></u><u =
class=3D""></u></span></div></div></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D"">Hi Med,<u class=3D""></u><u class=3D""></u></div><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D"">Forwarding this to the list (the left group =
mailing addresses were not working earlier).<u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D"">Please see inline below.<u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D"">Thanks,<u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D"">Ian<u class=3D""></u><u class=3D""></u></div></div><div =
class=3D""><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><br class=3D""><br class=3D""><u class=3D""></u><u =
class=3D""></u></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D"">Begin forwarded message:<u class=3D""></u><u =
class=3D""></u></div></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><b class=3D""><span =
style=3D"font-family:Helvetica,sans-serif" class=3D"">From:<span =
class=3D"">&nbsp;</span></span></b><span =
style=3D"font-family:Helvetica,sans-serif" class=3D"">&lt;<a =
href=3D"mailto:mohamed.boucadair@orange.com" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">mohamed.boucadair@orange.com</a>&gt;</span><u class=3D""></u><u=
 class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><b=
 class=3D""><span style=3D"font-family:Helvetica,sans-serif" =
class=3D"">Subject: RE: Problem in =
draft-ietf-softwire-multicast-prefix-option</span></b><u class=3D""></u><u=
 class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><b=
 class=3D""><span style=3D"font-family:Helvetica,sans-serif" =
class=3D"">Date:<span class=3D"">&nbsp;</span></span></b><span =
style=3D"font-family:Helvetica,sans-serif" class=3D"">8 June 2016 =
16:50:51 CEST</span><u class=3D""></u><u class=3D""></u></div></div><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><b=
 class=3D""><span style=3D"font-family:Helvetica,sans-serif" =
class=3D"">To:<span class=3D"">&nbsp;</span></span></b><span =
style=3D"font-family:Helvetica,sans-serif" class=3D"">ian Farrer &lt;<a =
href=3D"mailto:ianfarrer@gmx.com" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">ianfarrer@gmx.com</a>&gt;, "<a =
href=3D"mailto:softwires@ietf.org" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">softwires@ietf.org</a>" &lt;<a =
href=3D"mailto:softwires@ietf.org" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">softwires@ietf.org</a>&gt;, Jacni Qin &lt;<a =
href=3D"mailto:jacni@jacni.com" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">jacni@jacni.com</a>&gt;, "<a href=3D"mailto:dxhbupt@gmail.com" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">dxhbupt@gmail.com</a>" &lt;<a href=3D"mailto:dxhbupt@gmail.com"=
 style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">dxhbupt@gmail.com</a>&gt;</span><u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><b=
 class=3D""><span style=3D"font-family:Helvetica,sans-serif" =
class=3D"">Cc:<span class=3D"">&nbsp;</span></span></b><span =
style=3D"font-family:Helvetica,sans-serif" class=3D"">"<a =
href=3D"mailto:dhcwg-chairs@ietf.org" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">dhcwg-chairs@ietf.org</a>" &lt;<a =
href=3D"mailto:dhcwg-chairs@ietf.org" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D"">dhcwg-chairs@ietf.org</a>&gt;</span><u class=3D""></u><u =
class=3D""></u></div></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div><div class=3D""><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">Hi Ian,</span><u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">Please see inline.</span><u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">Cheers,</span><u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">Med</span><u class=3D""></u><u class=3D""></u></div></div><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:10pt;font-family:'Courier New'" =
class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></div></div><div style=3D"border-style:none none none =
solid;border-left-color:blue;border-left-width:1.5pt;padding:0cm 0cm 0cm =
4pt" class=3D""><div class=3D""><div style=3D"border-style:solid none =
none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt =
0cm 0cm" class=3D""><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><b=
 class=3D""><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" =
class=3D"">De&nbsp;:</span></b><span class=3D""><span =
style=3D"font-size:10pt;font-family:Tahoma,sans-serif" =
class=3D"">&nbsp;</span></span><span =
style=3D"font-size:10pt;font-family:Tahoma,sans-serif" class=3D"">ian =
Farrer [<a href=3D"mailto:ianfarrer@gmx.com" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D""><span style=3D"color:purple" =
class=3D"">mailto:ianfarrer@gmx.com</span></a>]<span =
class=3D"">&nbsp;</span><br class=3D""><b =
class=3D"">Envoy=C3=A9&nbsp;:</b><span class=3D"">&nbsp;</span>mercredi =
8 juin 2016 16:11<br class=3D""><b class=3D"">=C3=80&nbsp;:</b><span =
class=3D"">&nbsp;</span><a href=3D"mailto:softwires@ietf.org" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D""><span style=3D"color:purple" =
class=3D"">softwires@ietf.org</span></a>; BOUCADAIR Mohamed IMT/OLN; =
Jacni Qin;<span class=3D"">&nbsp;</span><a =
href=3D"mailto:dxhbupt@gmail.com" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D""><span style=3D"color:purple" =
class=3D"">dxhbupt@gmail.com</span></a><br class=3D""><b =
class=3D"">Cc&nbsp;:</b><span class=3D"">&nbsp;</span><a =
href=3D"mailto:dhcwg-chairs@ietf.org" =
style=3D"color:purple;text-decoration:underline" target=3D"_blank" =
class=3D""><span style=3D"color:purple" =
class=3D"">dhcwg-chairs@ietf.org</span></a><br class=3D""><b =
class=3D"">Objet&nbsp;:</b><span class=3D"">&nbsp;</span>Problem in =
draft-ietf-softwire-multicast-prefix-option</span><u class=3D""></u><u =
class=3D""></u></div></div></div></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D"">&nbsp;<u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div class=3D""><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:9pt;font-family:Verdana,sans-serif" =
class=3D"">Hi,</span><u class=3D""></u><u class=3D""></u></div></div><div =
class=3D""><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:9pt;font-family:Verdana,sans-serif" =
class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" class=3D"">On =
reviewing this draft I would like to raise a problem with section 5 of =
the draft. The text is:</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" =
class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" class=3D"">"If =
all the enclosed IPv4-embedded IPv6 multicast prefixes have the same =
scope, the first instance of the option MUST be used."</span><u =
class=3D""></u><u class=3D""></u></div></div></div><div class=3D""><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span style=3D"font-size:9pt;font-family:Verdana,sans-serif" =
class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" class=3D"">The =
problem is that this contravenes section 17 of RFC7227:</span><u =
class=3D""></u><u class=3D""></u></div></div></div><div class=3D""><pre =
style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:'Courier =
New'" class=3D"">Option order, either the order among many DHCPv6 =
options or the order<u class=3D""></u><u class=3D""></u></pre><pre =
style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:'Courier =
New'" class=3D"">&nbsp;&nbsp; of multiple instances of the same option, =
SHOULD NOT be significant.<u class=3D""></u><u class=3D""></u></pre><pre =
style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:'Courier =
New'" class=3D"">&nbsp;&nbsp; New documents MUST NOT assume any specific =
option processing order.<u class=3D""></u><u class=3D""></u></pre><pre =
style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:'Courier =
New'" class=3D""><span lang=3D"EN-US" class=3D"">&nbsp;</span><u =
class=3D""></u><u class=3D""></u></pre><pre style=3D"margin:0cm 0cm =
0.0001pt;font-size:10pt;font-family:'Courier New'" class=3D""><span =
lang=3D"EN-US" class=3D"">[Med] That sentence does not assume any =
(preference) order. It does only provide one way to select one instance =
among that list. As a reminder, the server is supposed to return one =
instance (per scope).</span><u class=3D""></u><u =
class=3D""></u></pre></div></div></div></div></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><u class=3D""></u>&nbsp;<u =
class=3D""></u></div></div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D"">[if - If the client is taking the first occurrence within the =
option and attempting to configure it, then it is preferring this option =
over other instances based on the order in which it occurs in the =
message.<u class=3D""></u><u class=3D""></u></div></div><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D"">The current text which describes the server =
behaviour (section 4) does not mention scope at all and does not specify =
any limitations on the number of instances or criteria for which they =
may be included - see RFC7227 sec 16.<u class=3D""></u><u =
class=3D""></u></div></div><div class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D"">If the server is meant to only return a single =
instance of the option per scope, but it is sending more than one, then =
this is a server configuration error. A quasi-random mechanism for the =
client to try and work around this just means that the configuration =
error may get masked.<u class=3D""></u><u class=3D""></u></div></div><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" class=3D""><u=
 class=3D""></u>&nbsp;<u class=3D""></u></div></div><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D"">As a suggestion, wouldn=E2=80=99t it be better =
to specify what the valid cases for the server including multiple option =
instances are and are not (with normative language). The client=E2=80=99s =
behaviour can then be defined to discard the options if they do not meet =
this criteria?]<u class=3D""></u><u class=3D""></u></div></div><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><br class=3D""><br class=3D""><u class=3D""></u><u =
class=3D""></u></div><div class=3D""><div style=3D"border-style:none =
none none =
solid;border-left-color:blue;border-left-width:1.5pt;padding:0cm 0cm 0cm =
4pt" class=3D""><div class=3D""><div class=3D""><div class=3D""><pre =
style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:'Courier =
New'" class=3D""><span lang=3D"EN-US" class=3D"">&nbsp;</span><u =
class=3D""></u><u class=3D""></u></pre><pre style=3D"margin:0cm 0cm =
0.0001pt;font-size:10pt;font-family:'Courier New'" class=3D""><span =
lang=3D"EN-US" class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></pre><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" class=3D"">I =
raised this with the DHC WG chairs, and they have a couple of =
suggestions:</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" =
class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></div></div></div></div><div class=3D""><div =
class=3D""><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:'Times New Roman',serif" =
class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" class=3D"">1. =
Define an encapsulating option - as the data i</span><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" class=3D"">nside =
an option can be order dependent.</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" class=3D"">2. Add =
a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can sort them =
based on&nbsp;this preference.</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" =
class=3D"">&nbsp;</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" =
class=3D"">Thanks,</span><u class=3D""></u><u =
class=3D""></u></div></div></div><div class=3D""><div class=3D""><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:'Times New =
Roman',serif" class=3D""><span =
style=3D"font-size:9pt;font-family:Verdana,sans-serif" =
class=3D"">Ian</span></div></div></div></div></div></div></div></div></div=
></div></div></div></blockquote></div><br class=3D""></div></div></div><br=
 class=3D"">_______________________________________________<br class=3D"">=

Softwires mailing list<br class=3D"">
<a href=3D"mailto:Softwires@ietf.org" class=3D"">Softwires@ietf.org</a><br=
 class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/softwires</a><br =
class=3D"">
<br class=3D""></blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_50E33E49-D4EC-41D3-9597-F1E59862F46F--


From nobody Thu Jun  9 06:37:33 2016
Return-Path: <mellon@fugue.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12A7E12D751 for <softwires@ietfa.amsl.com>; Thu,  9 Jun 2016 06:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 cu2heeMRzwTL for <softwires@ietfa.amsl.com>; Thu,  9 Jun 2016 06:37:26 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 349DF12D0A9 for <softwires@ietf.org>; Thu,  9 Jun 2016 06:37:26 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id j5so26429555lfb.3 for <softwires@ietf.org>; Thu, 09 Jun 2016 06:37:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wVjzZC+djdtdhZkV+l52XIGVzvmA6t4Wbrt/E2fa/NU=; b=WpteQ2yzYQ9a5iVuY5EhMIuCOxenOD92FMcO+uFxoZATrSNCztYZD+IpNTv9mGIA9G RHp6tFdvjn0BGiYRhV7oPst9in6AoWsPHYq2P3eG0NvbNj3quAbS0Y4vhdyTB7DvXAAS sjWYBim9JwGcPSFsYJ/LyDCfD7VKyRHFMyXNq4nqmmtYC9U8WpLxX5x5yOpo3fdgHdBk uxl6fmcgFtpnEyDQzm3WUMH+b3ybBOV36NK8rbed3e1jb9zwRfsiapt286G2Ioxo9WGc dgV1zQFDgsFQSdCGa0uLjBHiLnyZOBjRv3x74dDr0QSJph08kBIfTF60fftLObADkvqf p9dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wVjzZC+djdtdhZkV+l52XIGVzvmA6t4Wbrt/E2fa/NU=; b=TE5828+N1qOONnqjmBxaLdOfpfciEq84qR4mCByZDrMxYfWtk53u/qTU5T+61keNdE wkswCu7vhQKu1xrLhFLiuMVrqWtNVEWyY0EEywDIXvkBukVFe+oln4mob2TURqLN58y+ bI9Wk6j9bnxO77mLbDgiE9yoeQ9Nb2UuaF0VL2Y4b9nqdhO1xJE0TtcEif2DrDeyJxPd OKwfFMapNWP7EQXNSX/rF4qXJ6HZ4NznIg5rHGykePPWb0nCm/kuWamRwYc+Sw0vRsFN rA8ckRksiS1KBPvA1No+AuB6t5yzQGJklQb8NH0PJNndETUir8I/p4QngoM5kEgcKmgr razA==
X-Gm-Message-State: ALyK8tJBm65/5K8davVV8dpny9atu2HKw8+pgpHaPw9F7Bz8lkEkXNK7IPBIxYUwVO7/BwRpflc0sscfUjYtzA==
X-Received: by 10.25.210.205 with SMTP id j196mr6036209lfg.139.1465479444171;  Thu, 09 Jun 2016 06:37:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Thu, 9 Jun 2016 06:36:44 -0700 (PDT)
In-Reply-To: <2CDDF3C1-1F18-4621-8223-9CD5ADCBDDD1@gmx.com>
References: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D5ABB288-99F9-4038-9E13-A9FC2ADAC0EF@gmx.com> <787AE7BB302AE849A7480A190F8B933008DAF3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0B27AECD-13CD-4B05-A34C-70E901807D40@gmx.com> <CAPt1N1=ZGhkG4jU1+iZGqjiCg6M2j0GOSogADNj4=pK8cxYwHg@mail.gmail.com> <2CDDF3C1-1F18-4621-8223-9CD5ADCBDDD1@gmx.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 9 Jun 2016 09:36:44 -0400
Message-ID: <CAPt1N1ktcG6AQpWKyDEBjAOOq4BHvVZ2gkPwAyQDtnAaaa-OQQ@mail.gmail.com>
To: Ian Farrer <ianfarrer@gmx.com>
Content-Type: multipart/alternative; boundary=001a11403562b3f2e90534d885ac
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/ksAksIkjYtIHEOcVEoPZnyy7J-E>
Cc: Softwires WG <softwires@ietf.org>, "dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
Subject: Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 13:37:31 -0000

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

I would suggest:

   - Two options, with different semantics
   - Option format is one IP address per option
   - This means that servers can't send two IP addresses, because that's
   not the format of the option
   - Clients silently discard malformed options (don't need to specify
   this--it's just what clients should do in general)
   - Define the semantics for the case where the client receives both
   options.


On Thu, Jun 9, 2016 at 9:08 AM, Ian Farrer <ianfarrer@gmx.com> wrote:

> HI Ted,
>
> Cheers,
> Ian
>
> On 9 Jun 2016, at 14:34, Ted Lemon <mellon@fugue.com> wrote:
>
> Actually, this is a classic example of what we try to avoid: special
> server behavior for options.   Options are just payload, not protocol,
> unless they are intended to affect the flow of the protocol.   It should
> not be necessary for the server to have special code to support a differe=
nt
> payload, any more than the TCP stack should have to be modified in order =
to
> support new extensions to HTTP.
>
> So you could make an operational note about how servers ought to be
> configured, but you should not require that the server check to make sure
> it is configured that way.   You should not require that the server
> understand the semantics of the option--what it means for there to be two
> of them, or what order they should occur in, or what meaning that orderin=
g
> has.
>
>
> [if - So, for the original reason that the point was raised, do you
> suggest that enforcing this only in the client (i.e. if it receives an
> invalid option combination/content then drop all instances) in addition t=
o
> the operation guidance for server config?]
>
>
>
> If you have two different uses for an option, with different semantics,
> you should define two different options, each of which has only one
> semantics.
>
> On Thu, Jun 9, 2016 at 3:44 AM, Ian Farrer <ianfarrer@gmx.com> wrote:
>
>> Hi Med,
>>
>> To be clear, both of the suggestions include the modification to the
>> Section 5 client text? I think this is necessary. But is the error
>> condition that all of the enclosed options are the same scope, or that t=
wo
>> or more are?
>>
>> Between the two, I would prefer (1) - a MUST NOT with an exception is a
>> SHOULD NOT. An alternative wording that tries to get the best of both:
>>
>> A server MUST NOT send more than on one instance of OPTION_V6_PREFIX64
>> per scope. Servers MAY send one instance of OPTION_V6_PREFIX64 for each
>> distinct IPv6 multicast prefix with a distinct scope.
>>
>> Thanks,
>> Ian
>>
>> On 9 Jun 2016, at 08:49, mohamed.boucadair@orange.com wrote:
>>
>> Hi Ian,
>>
>> There are two options:
>>
>> (1)
>>
>> Maintain the current text in the draft but add the following text to
>> Section 4:
>>
>>    Servers SHOULD NOT send more than one instance of OPTION_V6_PREFIX64,
>>    except if distinct IPv6 multicast prefixes with distinct scopes are
>>    configured.
>>
>> This is the behavior defined in
>> https://tools.ietf.org/html/rfc6334#section-5/.
>>
>> (2)
>>
>> Add this text in Section 4:
>>
>>    Servers MUST NOT send more than one instance of OPTION_V6_PREFIX64,
>>    except if distinct IPv6 multicast prefixes with distinct scopes are
>>    configured.
>>
>> And modify the text in Section 5 to indicate that the client must discar=
d
>> the options if all enclosed addresses are of the same scope.
>>
>> I agree with you that (2) will help to identify a server error, but with
>> a risk to induce service disruptions.
>>
>> Which one do you prefer to be implemented in the draft?
>>
>> Thank you.
>>
>> Cheers,
>> Med
>>
>> *De :* Ian Farrer [mailto:ianfarrer@gmx.com <ianfarrer@gmx.com>]
>> *Envoy=C3=A9 :* mercredi 8 juin 2016 19:10
>> *=C3=80 :* BOUCADAIR Mohamed IMT/OLN; Softwires WG
>> *Cc :* dhcwg-chairs@ietf.org
>> *Objet :* Fwd: Problem in draft-ietf-softwire-multicast-prefix-option
>>
>> Hi Med,
>>
>> Forwarding this to the list (the left group mailing addresses were not
>> working earlier).
>>
>> Please see inline below.
>>
>> Thanks,
>> Ian
>>
>>
>> Begin forwarded message:
>>
>> *From: *<mohamed.boucadair@orange.com>
>> *Subject: RE: Problem in draft-ietf-softwire-multicast-prefix-option*
>> *Date: *8 June 2016 16:50:51 CEST
>> *To: *ian Farrer <ianfarrer@gmx.com>, "softwires@ietf.org" <
>> softwires@ietf.org>, Jacni Qin <jacni@jacni.com>, "dxhbupt@gmail.com" <
>> dxhbupt@gmail.com>
>> *Cc: *"dhcwg-chairs@ietf.org" <dhcwg-chairs@ietf.org>
>>
>> Hi Ian,
>>
>> Please see inline.
>>
>> Cheers,
>> Med
>>
>> *De :* ian Farrer [mailto:ianfarrer@gmx.com <ianfarrer@gmx.com>]
>> *Envoy=C3=A9 :* mercredi 8 juin 2016 16:11
>> *=C3=80 :* softwires@ietf.org; BOUCADAIR Mohamed IMT/OLN; Jacni Qin;
>> dxhbupt@gmail.com
>> *Cc :* dhcwg-chairs@ietf.org
>> *Objet :* Problem in draft-ietf-softwire-multicast-prefix-option
>>
>> Hi,
>>
>> On reviewing this draft I would like to raise a problem with section 5 o=
f
>> the draft. The text is:
>>
>> "If all the enclosed IPv4-embedded IPv6 multicast prefixes have the same
>> scope, the first instance of the option MUST be used."
>>
>> The problem is that this contravenes section 17 of RFC7227:
>>
>> Option order, either the order among many DHCPv6 options or the order
>>
>>    of multiple instances of the same option, SHOULD NOT be significant.
>>
>>    New documents MUST NOT assume any specific option processing order.
>>
>>
>>
>> [Med] That sentence does not assume any (preference) order. It does only=
 provide one way to select one instance among that list. As a reminder, the=
 server is supposed to return one instance (per scope).
>>
>>
>> [if - If the client is taking the first occurrence within the option and
>> attempting to configure it, then it is preferring this option over other
>> instances based on the order in which it occurs in the message.
>>
>> The current text which describes the server behaviour (section 4) does
>> not mention scope at all and does not specify any limitations on the num=
ber
>> of instances or criteria for which they may be included - see RFC7227 se=
c
>> 16.
>>
>> If the server is meant to only return a single instance of the option pe=
r
>> scope, but it is sending more than one, then this is a server configurat=
ion
>> error. A quasi-random mechanism for the client to try and work around th=
is
>> just means that the configuration error may get masked.
>>
>> As a suggestion, wouldn=E2=80=99t it be better to specify what the valid=
 cases
>> for the server including multiple option instances are and are not (with
>> normative language). The client=E2=80=99s behaviour can then be defined =
to discard
>> the options if they do not meet this criteria?]
>>
>>
>>
>>
>>
>>
>> I raised this with the DHC WG chairs, and they have a couple of
>> suggestions:
>>
>> 1. Define an encapsulating option - as the data inside an option can be
>> order dependent.
>> 2. Add a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can sor=
t them based
>> on this preference.
>>
>> Thanks,
>> Ian
>>
>>
>>
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>
>>
>
>

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

<div dir=3D"ltr">I would suggest:<div><ul><li>Two options, with different s=
emantics</li><li>Option format is one IP address per option</li><li>This me=
ans that servers can&#39;t send two IP addresses, because that&#39;s not th=
e format of the option</li><li>Clients silently discard malformed options (=
don&#39;t need to specify this--it&#39;s just what clients should do in gen=
eral)</li><li>Define the semantics for the case where the client receives b=
oth options.</li></ul></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Jun 9, 2016 at 9:08 AM, Ian Farrer <span dir=3D"lt=
r">&lt;<a href=3D"mailto:ianfarrer@gmx.com" target=3D"_blank">ianfarrer@gmx=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"=
word-wrap:break-word"><div>HI Ted,</div><div><br></div><div>Cheers,</div><d=
iv>Ian</div><br><div><span class=3D""><blockquote type=3D"cite"><div>On 9 J=
un 2016, at 14:34, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com" target=
=3D"_blank">mellon@fugue.com</a>&gt; wrote:</div><br><div><div dir=3D"ltr">=
Actually, this is a classic example of what we try to avoid: special server=
 behavior for options. =C2=A0 Options are just payload, not protocol, unles=
s they are intended to affect the flow of the protocol. =C2=A0 It should no=
t be necessary for the server to have special code to support a different p=
ayload, any more than the TCP stack should have to be modified in order to =
support new extensions to HTTP.<div><br></div><div>So you could make an ope=
rational note about how servers ought to be configured, but you should not =
require that the server check to make sure it is configured that way. =C2=
=A0 You should not require that the server understand the semantics of the =
option--what it means for there to be two of them, or what order they shoul=
d occur in, or what meaning that ordering has.</div></div></div></blockquot=
e><div><br></div></span><div>[if - So, for the original reason that the poi=
nt was raised, do you suggest that enforcing this only in the client (i.e. =
if it receives an invalid option combination/content then drop all instance=
s) in addition to the operation guidance for server config?]</div><div><div=
 class=3D"h5"><div><br></div><br><blockquote type=3D"cite"><div><div dir=3D=
"ltr"><div><br></div><div>If you have two different uses for an option, wit=
h different semantics, you should define two different options, each of whi=
ch has only one semantics.</div></div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Thu, Jun 9, 2016 at 3:44 AM, Ian Farrer <span dir=
=3D"ltr">&lt;<a href=3D"mailto:ianfarrer@gmx.com" target=3D"_blank">ianfarr=
er@gmx.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div sty=
le=3D"word-wrap:break-word"><div>Hi Med,</div><div><br></div><div>To be cle=
ar, both of the suggestions include the modification to the Section 5 clien=
t text? I think this is necessary. But is the error condition that all of t=
he enclosed options are the same scope, or that two or more are?</div><div>=
<br></div><div>Between the two, I would prefer (1) - a MUST NOT with an exc=
eption is a SHOULD NOT. An alternative wording that tries to get the best o=
f both:</div><div><br></div><div>A server MUST NOT send more than on one in=
stance of OPTION_V6_PREFIX64 per scope. Servers MAY send one instance of OP=
TION_V6_PREFIX64 for each distinct IPv6 multicast prefix with a distinct sc=
ope.=C2=A0</div><div><br></div><div>Thanks,</div><div>Ian</div><div><div><b=
r><div><blockquote type=3D"cite"><div>On 9 Jun 2016, at 08:49, <a href=3D"m=
ailto:mohamed.boucadair@orange.com" target=3D"_blank">mohamed.boucadair@ora=
nge.com</a> wrote:</div><br><div><div style=3D"font-family:Helvetica;font-s=
ize:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-sp=
acing:normal;line-height:normal;text-align:start;text-indent:0px;text-trans=
form:none;white-space:normal;word-spacing:0px"><div style=3D"margin:0cm 0cm=
 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span=
 style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">Hi Ian,<u></u><=
u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fon=
t-family:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:10pt;fon=
t-family:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm=
 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><=
span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#3=
9;">There are two options:<u></u><u></u></span></div><div style=3D"margin:0=
cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"=
><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&=
#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12=
pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=
=3D"font-size:10pt;font-family:&#39;Courier New&#39;">(1)<u></u><u></u></sp=
an></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&=
#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10p=
t;font-family:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier N=
ew&#39;">Maintain the current text in the draft but add the following text =
to Section 4:<u></u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001=
pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=
=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=
=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-f=
amily:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-s=
ize:10pt;font-family:&#39;Courier New&#39;">=C2=A0=C2=A0 Servers SHOULD NOT=
 send more than one instance of OPTION_V6_PREFIX64,<u></u><u></u></span></d=
iv><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Ti=
mes New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font=
-family:&#39;Courier New&#39;">=C2=A0=C2=A0 except if distinct IPv6 multica=
st prefixes with distinct scopes are<u></u><u></u></span></div><div style=
=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman=
&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;=
Courier New&#39;">=C2=A0=C2=A0 configured.<u></u><u></u></span></div><div s=
tyle=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New R=
oman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&=
#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.000=
1pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=
=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">This =
is the behavior defined in<span>=C2=A0</span><a href=3D"https://tools.ietf.=
org/html/rfc6334#section-5/" style=3D"color:purple;text-decoration:underlin=
e" target=3D"_blank">https://tools.ietf.org/html/rfc6334#section-5/</a>.<u>=
</u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12p=
t;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=
=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0</span></div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times N=
ew Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-fami=
ly:&#39;Courier New&#39;">(2)<u></u><u></u></span></div><div style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier N=
ew&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size=
:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" sty=
le=3D"font-size:10pt;font-family:&#39;Courier New&#39;">Add this text in Se=
ction 4:<u></u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;fo=
nt-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-=
US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0</span=
></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#3=
9;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;=
font-family:&#39;Courier New&#39;">=C2=A0=C2=A0 Servers MUST NOT send more =
than one instance of OPTION_V6_PREFIX64,<u></u><u></u></span></div><div sty=
le=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Rom=
an&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#3=
9;Courier New&#39;">=C2=A0=C2=A0 except if distinct IPv6 multicast prefixes=
 with distinct scopes are<u></u><u></u></span></div><div style=3D"margin:0c=
m 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">=
<span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#=
39;">=C2=A0=C2=A0<span>=C2=A0</span></span><span style=3D"font-size:10pt;fo=
nt-family:&#39;Courier New&#39;">configured.<u></u><u></u></span></div><div=
 style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New=
 Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family=
:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.0=
001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lan=
g=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">And =
modify the text in Section 5 to indicate that the client must discard the o=
ptions if all enclosed addresses are of the same scope.<u></u><u></u></span=
></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#3=
9;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;=
font-family:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:=
0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif=
"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New=
&#39;">I agree with you that (2) will help to identify a server error, but =
with a risk to induce service disruptions.<u></u><u></u></span></div><div s=
tyle=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New R=
oman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&=
#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0cm 0.000=
1pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=
=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">Which=
 one do you prefer to be implemented in the draft?<u></u><u></u></span></di=
v><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Tim=
es New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-=
family:&#39;Courier New&#39;">=C2=A0</span></div><div style=3D"margin:0cm 0=
cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><sp=
an lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;=
">Thank you.<u></u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001p=
t;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span lang=3D=
"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0</=
span></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family=
:&#39;Times New Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:1=
0pt;font-family:&#39;Courier New&#39;">Cheers,<u></u><u></u></span></div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times N=
ew Roman&#39;,serif"><span lang=3D"EN-US" style=3D"font-size:10pt;font-fami=
ly:&#39;Courier New&#39;">Med<u></u><u></u></span></div><div style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&#39;Courier N=
ew&#39;">=C2=A0</span></div><div style=3D"border-style:none none none solid=
;border-left-color:blue;border-left-width:1.5pt;padding:0cm 0cm 0cm 4pt"><d=
iv><div style=3D"border-style:solid none none;border-top-color:rgb(181,196,=
223);border-top-width:1pt;padding:3pt 0cm 0cm"><div style=3D"margin:0cm 0cm=
 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><b><s=
pan style=3D"font-size:10pt;font-family:Tahoma,sans-serif">De=C2=A0:</span>=
</b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif"><span>=C2=
=A0</span>Ian Farrer [<a href=3D"mailto:ianfarrer@gmx.com" target=3D"_blank=
">mailto:ianfarrer@gmx.com</a>]<span>=C2=A0</span><br><b>Envoy=C3=A9=C2=A0:=
</b><span>=C2=A0</span>mercredi 8 juin 2016 19:10<br><b>=C3=80=C2=A0:</b><s=
pan>=C2=A0</span>BOUCADAIR Mohamed IMT/OLN; Softwires WG<br><b>Cc=C2=A0:</b=
><span>=C2=A0</span><a href=3D"mailto:dhcwg-chairs@ietf.org" target=3D"_bla=
nk">dhcwg-chairs@ietf.org</a><br><b>Objet=C2=A0:</b><span>=C2=A0</span>Fwd:=
 Problem in draft-ietf-softwire-multicast-prefix-option<u></u><u></u></span=
></div></div></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fon=
t-family:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div><div st=
yle=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Ro=
man&#39;,serif">Hi Med,<u></u><u></u></div><div><div style=3D"margin:0cm 0c=
m 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u><=
/u>=C2=A0<u></u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font=
-size:12pt;font-family:&#39;Times New Roman&#39;,serif">Forwarding this to =
the list (the left group mailing addresses were not working earlier).<u></u=
><u></u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12=
pt;font-family:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div><=
/div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:=
&#39;Times New Roman&#39;,serif">Please see inline below.<u></u><u></u></di=
v></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fami=
ly:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div></div><div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times N=
ew Roman&#39;,serif">Thanks,<u></u><u></u></div></div><div><div style=3D"ma=
rgin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,=
serif">Ian<u></u><u></u></div></div><div><div><div style=3D"margin:0cm 0cm =
0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><br><b=
r><u></u><u></u></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:=
12pt;font-family:&#39;Times New Roman&#39;,serif">Begin forwarded message:<=
u></u><u></u></div></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12=
pt;font-family:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div><=
div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;T=
imes New Roman&#39;,serif"><b><span style=3D"font-family:Helvetica,sans-ser=
if">From:<span>=C2=A0</span></span></b><span style=3D"font-family:Helvetica=
,sans-serif">&lt;<a href=3D"mailto:mohamed.boucadair@orange.com" style=3D"c=
olor:purple;text-decoration:underline" target=3D"_blank">mohamed.boucadair@=
orange.com</a>&gt;</span><u></u><u></u></div></div><div><div style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if"><b><span style=3D"font-family:Helvetica,sans-serif">Subject: RE: Proble=
m in draft-ietf-softwire-multicast-prefix-option</span></b><u></u><u></u></=
div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fa=
mily:&#39;Times New Roman&#39;,serif"><b><span style=3D"font-family:Helveti=
ca,sans-serif">Date:<span>=C2=A0</span></span></b><span style=3D"font-famil=
y:Helvetica,sans-serif">8 June 2016 16:50:51 CEST</span><u></u><u></u></div=
></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-famil=
y:&#39;Times New Roman&#39;,serif"><b><span style=3D"font-family:Helvetica,=
sans-serif">To:<span>=C2=A0</span></span></b><span style=3D"font-family:Hel=
vetica,sans-serif">ian Farrer &lt;<a href=3D"mailto:ianfarrer@gmx.com" styl=
e=3D"color:purple;text-decoration:underline" target=3D"_blank">ianfarrer@gm=
x.com</a>&gt;, &quot;<a href=3D"mailto:softwires@ietf.org" style=3D"color:p=
urple;text-decoration:underline" target=3D"_blank">softwires@ietf.org</a>&q=
uot; &lt;<a href=3D"mailto:softwires@ietf.org" style=3D"color:purple;text-d=
ecoration:underline" target=3D"_blank">softwires@ietf.org</a>&gt;, Jacni Qi=
n &lt;<a href=3D"mailto:jacni@jacni.com" style=3D"color:purple;text-decorat=
ion:underline" target=3D"_blank">jacni@jacni.com</a>&gt;, &quot;<a href=3D"=
mailto:dxhbupt@gmail.com" style=3D"color:purple;text-decoration:underline" =
target=3D"_blank">dxhbupt@gmail.com</a>&quot; &lt;<a href=3D"mailto:dxhbupt=
@gmail.com" style=3D"color:purple;text-decoration:underline" target=3D"_bla=
nk">dxhbupt@gmail.com</a>&gt;</span><u></u><u></u></div></div><div><div sty=
le=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Rom=
an&#39;,serif"><b><span style=3D"font-family:Helvetica,sans-serif">Cc:<span=
>=C2=A0</span></span></b><span style=3D"font-family:Helvetica,sans-serif">&=
quot;<a href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color:purple;text-de=
coration:underline" target=3D"_blank">dhcwg-chairs@ietf.org</a>&quot; &lt;<=
a href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color:purple;text-decorati=
on:underline" target=3D"_blank">dhcwg-chairs@ietf.org</a>&gt;</span><u></u>=
<u></u></div></div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fon=
t-family:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div><div><d=
iv><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Ti=
mes New Roman&#39;,serif"><span style=3D"font-size:10pt;font-family:&#39;Co=
urier New&#39;">Hi Ian,</span><u></u><u></u></div></div><div><div style=3D"=
margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39=
;,serif"><span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=
=C2=A0</span><u></u><u></u></div></div><div><div style=3D"margin:0cm 0cm 0.=
0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span st=
yle=3D"font-size:10pt;font-family:&#39;Courier New&#39;">Please see inline.=
</span><u></u><u></u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt=
;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span style=3D=
"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0</span><u></u><u><=
/u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fo=
nt-family:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:10pt;fo=
nt-family:&#39;Courier New&#39;">Cheers,</span><u></u><u></u></div></div><d=
iv><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Ti=
mes New Roman&#39;,serif"><span style=3D"font-size:10pt;font-family:&#39;Co=
urier New&#39;">Med</span><u></u><u></u></div></div><div><div style=3D"marg=
in:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,se=
rif"><span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;">=C2=
=A0</span><u></u><u></u></div></div><div style=3D"border-style:none none no=
ne solid;border-left-color:blue;border-left-width:1.5pt;padding:0cm 0cm 0cm=
 4pt"><div><div style=3D"border-style:solid none none;border-top-color:rgb(=
181,196,223);border-top-width:1pt;padding:3pt 0cm 0cm"><div><div style=3D"m=
argin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;=
,serif"><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif">De=
=C2=A0:</span></b><span><span style=3D"font-size:10pt;font-family:Tahoma,sa=
ns-serif">=C2=A0</span></span><span style=3D"font-size:10pt;font-family:Tah=
oma,sans-serif">ian Farrer [<a href=3D"mailto:ianfarrer@gmx.com" style=3D"c=
olor:purple;text-decoration:underline" target=3D"_blank"><span style=3D"col=
or:purple">mailto:ianfarrer@gmx.com</span></a>]<span>=C2=A0</span><br><b>En=
voy=C3=A9=C2=A0:</b><span>=C2=A0</span>mercredi 8 juin 2016 16:11<br><b>=C3=
=80=C2=A0:</b><span>=C2=A0</span><a href=3D"mailto:softwires@ietf.org" styl=
e=3D"color:purple;text-decoration:underline" target=3D"_blank"><span style=
=3D"color:purple">softwires@ietf.org</span></a>; BOUCADAIR Mohamed IMT/OLN;=
 Jacni Qin;<span>=C2=A0</span><a href=3D"mailto:dxhbupt@gmail.com" style=3D=
"color:purple;text-decoration:underline" target=3D"_blank"><span style=3D"c=
olor:purple">dxhbupt@gmail.com</span></a><br><b>Cc=C2=A0:</b><span>=C2=A0</=
span><a href=3D"mailto:dhcwg-chairs@ietf.org" style=3D"color:purple;text-de=
coration:underline" target=3D"_blank"><span style=3D"color:purple">dhcwg-ch=
airs@ietf.org</span></a><br><b>Objet=C2=A0:</b><span>=C2=A0</span>Problem i=
n draft-ietf-softwire-multicast-prefix-option</span><u></u><u></u></div></d=
iv></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fo=
nt-family:&#39;Times New Roman&#39;,serif">=C2=A0<u></u><u></u></div></div>=
<div><div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fa=
mily:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:9pt;font-fam=
ily:Verdana,sans-serif">Hi,</span><u></u><u></u></div></div><div><div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New =
Roman&#39;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-ser=
if">=C2=A0</span><u></u><u></u></div></div></div><div><div><div style=3D"ma=
rgin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,=
serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">On revi=
ewing this draft I would like to raise a problem with section 5 of the draf=
t. The text is:</span><u></u><u></u></div></div></div><div><div><div style=
=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman=
&#39;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">=
=C2=A0</span><u></u><u></u></div></div></div><div><div><div style=3D"margin=
:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,seri=
f"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">&quot;If al=
l the enclosed IPv4-embedded IPv6 multicast prefixes have the same scope, t=
he first instance of the option MUST be used.&quot;</span><u></u><u></u></d=
iv></div></div><div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12=
pt;font-family:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:9p=
t;font-family:Verdana,sans-serif">=C2=A0</span><u></u><u></u></div></div></=
div><div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fam=
ily:&#39;Times New Roman&#39;,serif"><span style=3D"font-size:9pt;font-fami=
ly:Verdana,sans-serif">The problem is that this contravenes section 17 of R=
FC7227:</span><u></u><u></u></div></div></div><div><pre style=3D"margin:0cm=
 0cm 0.0001pt;font-size:10pt;font-family:&#39;Courier New&#39;">Option orde=
r, either the order among many DHCPv6 options or the order<u></u><u></u></p=
re><pre style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:&#39;Co=
urier New&#39;">=C2=A0=C2=A0 of multiple instances of the same option, SHOU=
LD NOT be significant.<u></u><u></u></pre><pre style=3D"margin:0cm 0cm 0.00=
01pt;font-size:10pt;font-family:&#39;Courier New&#39;">=C2=A0=C2=A0 New doc=
uments MUST NOT assume any specific option processing order.<u></u><u></u><=
/pre><pre style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:&#39;=
Courier New&#39;"><span lang=3D"EN-US">=C2=A0</span><u></u><u></u></pre><pr=
e style=3D"margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:&#39;Courier =
New&#39;"><span lang=3D"EN-US">[Med] That sentence does not assume any (pre=
ference) order. It does only provide one way to select one instance among t=
hat list. As a reminder, the server is supposed to return one instance (per=
 scope).</span><u></u><u></u></pre></div></div></div></div></div><div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New =
Roman&#39;,serif"><u></u>=C2=A0<u></u></div></div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">[i=
f - If the client is taking the first occurrence within the option and atte=
mpting to configure it, then it is preferring this option over other instan=
ces based on the order in which it occurs in the message.<u></u><u></u></di=
v></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fami=
ly:&#39;Times New Roman&#39;,serif"><u></u>=C2=A0<u></u></div></div><div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times N=
ew Roman&#39;,serif">The current text which describes the server behaviour =
(section 4) does not mention scope at all and does not specify any limitati=
ons on the number of instances or criteria for which they may be included -=
 see RFC7227 sec 16.<u></u><u></u></div></div><div><div style=3D"margin:0cm=
 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><=
u></u>=C2=A0<u></u></div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;f=
ont-size:12pt;font-family:&#39;Times New Roman&#39;,serif">If the server is=
 meant to only return a single instance of the option per scope, but it is =
sending more than one, then this is a server configuration error. A quasi-r=
andom mechanism for the client to try and work around this just means that =
the configuration error may get masked.<u></u><u></u></div></div><div><div =
style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New =
Roman&#39;,serif"><u></u>=C2=A0<u></u></div></div><div><div style=3D"margin=
:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,seri=
f">As a suggestion, wouldn=E2=80=99t it be better to specify what the valid=
 cases for the server including multiple option instances are and are not (=
with normative language). The client=E2=80=99s behaviour can then be define=
d to discard the options if they do not meet this criteria?]<u></u><u></u><=
/div></div><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-f=
amily:&#39;Times New Roman&#39;,serif"><br><br><u></u><u></u></div><div><di=
v style=3D"border-style:none none none solid;border-left-color:blue;border-=
left-width:1.5pt;padding:0cm 0cm 0cm 4pt"><div><div><div><pre style=3D"marg=
in:0cm 0cm 0.0001pt;font-size:10pt;font-family:&#39;Courier New&#39;"><span=
 lang=3D"EN-US">=C2=A0</span><u></u><u></u></pre><pre style=3D"margin:0cm 0=
cm 0.0001pt;font-size:10pt;font-family:&#39;Courier New&#39;"><span lang=3D=
"EN-US">=C2=A0</span><u></u><u></u></pre><div><div><div style=3D"margin:0cm=
 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><=
span lang=3D"EN-US" style=3D"font-size:9pt;font-family:Verdana,sans-serif">=
I raised this with the DHC WG chairs, and they have a couple of suggestions=
:</span><u></u><u></u></div></div></div><div><div><div style=3D"margin:0cm =
0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><s=
pan lang=3D"EN-US" style=3D"font-size:9pt;font-family:Verdana,sans-serif">=
=C2=A0</span><u></u><u></u></div></div></div></div><div><div><div style=3D"=
margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39=
;,serif"><span lang=3D"EN-US" style=3D"font-size:9pt;font-family:Verdana,sa=
ns-serif">1. Define an encapsulating option - as the data i</span><span sty=
le=3D"font-size:9pt;font-family:Verdana,sans-serif">nside an option can be =
order dependent.</span><u></u><u></u></div></div></div><div><div><div style=
=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman=
&#39;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">2=
. Add a =E2=80=9Cpreference=E2=80=9D (octet?) and then a client can sort th=
em based on=C2=A0this preference.</span><u></u><u></u></div></div></div><di=
v><div><div style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#3=
9;Times New Roman&#39;,serif"><span style=3D"font-size:9pt;font-family:Verd=
ana,sans-serif">=C2=A0</span><u></u><u></u></div></div></div><div><div><div=
 style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New=
 Roman&#39;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-se=
rif">Thanks,</span><u></u><u></u></div></div></div><div><div><div style=3D"=
margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39=
;,serif"><span style=3D"font-size:9pt;font-family:Verdana,sans-serif">Ian</=
span></div></div></div></div></div></div></div></div></div></div></div></di=
v></blockquote></div><br></div></div></div><br>____________________________=
___________________<br>
Softwires mailing list<br>
<a href=3D"mailto:Softwires@ietf.org" target=3D"_blank">Softwires@ietf.org<=
/a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/softwires" rel=3D"noreferr=
er" target=3D"_blank">https://www.ietf.org/mailman/listinfo/softwires</a><b=
r>
<br></blockquote></div><br></div>
</div></blockquote></div></div></div><br></div></blockquote></div><br></div=
>

--001a11403562b3f2e90534d885ac--


From nobody Thu Jun  9 23:07:20 2016
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18EA12DAA8; Thu,  9 Jun 2016 23:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level: 
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=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 1xizZcT0VFVF; Thu,  9 Jun 2016 23:07:16 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCE2612D1A2; Thu,  9 Jun 2016 23:07:15 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 1B03018C814; Fri, 10 Jun 2016 08:07:14 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.57]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id E254B27C06F; Fri, 10 Jun 2016 08:07:13 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0294.000; Fri, 10 Jun 2016 08:07:13 +0200
From: <mohamed.boucadair@orange.com>
To: Ted Lemon <mellon@fugue.com>, Ian Farrer <ianfarrer@gmx.com>
Thread-Topic: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
Thread-Index: AQHRwlQQhAAP6utZe0OknJXCUR55T5/iLi6g
Date: Fri, 10 Jun 2016 06:07:13 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008DAFC9A@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D5ABB288-99F9-4038-9E13-A9FC2ADAC0EF@gmx.com> <787AE7BB302AE849A7480A190F8B933008DAF3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0B27AECD-13CD-4B05-A34C-70E901807D40@gmx.com> <CAPt1N1=ZGhkG4jU1+iZGqjiCg6M2j0GOSogADNj4=pK8cxYwHg@mail.gmail.com> <2CDDF3C1-1F18-4621-8223-9CD5ADCBDDD1@gmx.com> <CAPt1N1ktcG6AQpWKyDEBjAOOq4BHvVZ2gkPwAyQDtnAaaa-OQQ@mail.gmail.com>
In-Reply-To: <CAPt1N1ktcG6AQpWKyDEBjAOOq4BHvVZ2gkPwAyQDtnAaaa-OQQ@mail.gmail.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: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933008DAFC9AOPEXCLILMA3corp_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.7.90315
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/xF-yKPJDz0frbdAdfKKZINil3-A>
Cc: Softwires WG <softwires@ietf.org>, "dhc-chairs@ietf.org" <dhc-chairs@ietf.org>
Subject: Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2016 06:07:18 -0000

--_000_787AE7BB302AE849A7480A190F8B933008DAFC9AOPEXCLILMA3corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgVGVkLCBJYW4sDQoNCldoYXQgSSB1bmRlcnN0YW5kIGZyb20gVGVk4oCZcyBjb21tZW50IGlz
IGhlIGlzIG9iamVjdGluZyB0byBhZGQgcmVzdHJpY3Rpb25zIHRvIHRoZSBzZXJ2ZXLigJlzIGJl
aGF2aW9yIHByb3Bvc2VkIGJ5IElhbi4NCg0KSW4gb3JkZXIgdG8gYWRkcmVzcyB0aGUgaW5pdGlh
bCBjb21tZW50IGZyb20gSWFuLCBJIHN1Z2dlc3QgdGhpcyB0ZXh0Og0KDQogICBJZiBkaXN0aW5j
dCBtdWx0aWNhc3QgUFJFRklYNjRzIHBlciBzY29wZSBhcmUgY29uZmlndXJlZCwgdGhlIERIQ1AN
CiAgIHNlcnZlciByZXR1cm5zIG11bHRpcGxlIE9QVElPTl9WNl9QUkVGSVg2NHM7IGVhY2ggaW5z
dGFuY2UgaXMNCiAgIGVuY2xvc2luZyBkaXN0aW5jdCBBU01fUFJFRklYNjQgYW5kIFNTTV9QUkVG
SVg2NCBwZXIgc2NvcGUuICBSZWZlciB0bw0KICAgU2VjdGlvbiA4IG9mIFtSRkMyMzY1XSBmb3Ig
YSBtYXBwaW5nIGJldHdlZW4gSVB2NCBtdWx0aWNhc3QgcHJlZml4ZXMNCiAgIHRvIElQdjYgbXVs
dGljYXN0IGFkZHJlc3Mgc2NvcGVzIFtSRkM3MzQ2XS4NCg0KQ29tbWVudHM/DQoNCkNoZWVycywN
Ck1lZA0KDQpEZSA6IFRlZCBMZW1vbiBbbWFpbHRvOm1lbGxvbkBmdWd1ZS5jb21dDQpFbnZvecOp
IDogamV1ZGkgOSBqdWluIDIwMTYgMTU6MzcNCsOAIDogSWFuIEZhcnJlcg0KQ2MgOiBCT1VDQURB
SVIgTW9oYW1lZCBJTVQvT0xOOyBTb2Z0d2lyZXMgV0c7IGRoY3dnLWNoYWlyc0BpZXRmLm9yZw0K
T2JqZXQgOiBSZTogW1NvZnR3aXJlc10gUHJvYmxlbSBpbiBkcmFmdC1pZXRmLXNvZnR3aXJlLW11
bHRpY2FzdC1wcmVmaXgtb3B0aW9uDQoNCkkgd291bGQgc3VnZ2VzdDoNCg0KICAqICAgVHdvIG9w
dGlvbnMsIHdpdGggZGlmZmVyZW50IHNlbWFudGljcw0KICAqICAgT3B0aW9uIGZvcm1hdCBpcyBv
bmUgSVAgYWRkcmVzcyBwZXIgb3B0aW9uDQogICogICBUaGlzIG1lYW5zIHRoYXQgc2VydmVycyBj
YW4ndCBzZW5kIHR3byBJUCBhZGRyZXNzZXMsIGJlY2F1c2UgdGhhdCdzIG5vdCB0aGUgZm9ybWF0
IG9mIHRoZSBvcHRpb24NCiAgKiAgIENsaWVudHMgc2lsZW50bHkgZGlzY2FyZCBtYWxmb3JtZWQg
b3B0aW9ucyAoZG9uJ3QgbmVlZCB0byBzcGVjaWZ5IHRoaXMtLWl0J3MganVzdCB3aGF0IGNsaWVu
dHMgc2hvdWxkIGRvIGluIGdlbmVyYWwpDQogICogICBEZWZpbmUgdGhlIHNlbWFudGljcyBmb3Ig
dGhlIGNhc2Ugd2hlcmUgdGhlIGNsaWVudCByZWNlaXZlcyBib3RoIG9wdGlvbnMuDQoNCk9uIFRo
dSwgSnVuIDksIDIwMTYgYXQgOTowOCBBTSwgSWFuIEZhcnJlciA8aWFuZmFycmVyQGdteC5jb208
bWFpbHRvOmlhbmZhcnJlckBnbXguY29tPj4gd3JvdGU6DQpISSBUZWQsDQoNCkNoZWVycywNCklh
bg0KDQpPbiA5IEp1biAyMDE2LCBhdCAxNDozNCwgVGVkIExlbW9uIDxtZWxsb25AZnVndWUuY29t
PG1haWx0bzptZWxsb25AZnVndWUuY29tPj4gd3JvdGU6DQoNCkFjdHVhbGx5LCB0aGlzIGlzIGEg
Y2xhc3NpYyBleGFtcGxlIG9mIHdoYXQgd2UgdHJ5IHRvIGF2b2lkOiBzcGVjaWFsIHNlcnZlciBi
ZWhhdmlvciBmb3Igb3B0aW9ucy4gICBPcHRpb25zIGFyZSBqdXN0IHBheWxvYWQsIG5vdCBwcm90
b2NvbCwgdW5sZXNzIHRoZXkgYXJlIGludGVuZGVkIHRvIGFmZmVjdCB0aGUgZmxvdyBvZiB0aGUg
cHJvdG9jb2wuICAgSXQgc2hvdWxkIG5vdCBiZSBuZWNlc3NhcnkgZm9yIHRoZSBzZXJ2ZXIgdG8g
aGF2ZSBzcGVjaWFsIGNvZGUgdG8gc3VwcG9ydCBhIGRpZmZlcmVudCBwYXlsb2FkLCBhbnkgbW9y
ZSB0aGFuIHRoZSBUQ1Agc3RhY2sgc2hvdWxkIGhhdmUgdG8gYmUgbW9kaWZpZWQgaW4gb3JkZXIg
dG8gc3VwcG9ydCBuZXcgZXh0ZW5zaW9ucyB0byBIVFRQLg0KDQpTbyB5b3UgY291bGQgbWFrZSBh
biBvcGVyYXRpb25hbCBub3RlIGFib3V0IGhvdyBzZXJ2ZXJzIG91Z2h0IHRvIGJlIGNvbmZpZ3Vy
ZWQsIGJ1dCB5b3Ugc2hvdWxkIG5vdCByZXF1aXJlIHRoYXQgdGhlIHNlcnZlciBjaGVjayB0byBt
YWtlIHN1cmUgaXQgaXMgY29uZmlndXJlZCB0aGF0IHdheS4gICBZb3Ugc2hvdWxkIG5vdCByZXF1
aXJlIHRoYXQgdGhlIHNlcnZlciB1bmRlcnN0YW5kIHRoZSBzZW1hbnRpY3Mgb2YgdGhlIG9wdGlv
bi0td2hhdCBpdCBtZWFucyBmb3IgdGhlcmUgdG8gYmUgdHdvIG9mIHRoZW0sIG9yIHdoYXQgb3Jk
ZXIgdGhleSBzaG91bGQgb2NjdXIgaW4sIG9yIHdoYXQgbWVhbmluZyB0aGF0IG9yZGVyaW5nIGhh
cy4NCg0KW2lmIC0gU28sIGZvciB0aGUgb3JpZ2luYWwgcmVhc29uIHRoYXQgdGhlIHBvaW50IHdh
cyByYWlzZWQsIGRvIHlvdSBzdWdnZXN0IHRoYXQgZW5mb3JjaW5nIHRoaXMgb25seSBpbiB0aGUg
Y2xpZW50IChpLmUuIGlmIGl0IHJlY2VpdmVzIGFuIGludmFsaWQgb3B0aW9uIGNvbWJpbmF0aW9u
L2NvbnRlbnQgdGhlbiBkcm9wIGFsbCBpbnN0YW5jZXMpIGluIGFkZGl0aW9uIHRvIHRoZSBvcGVy
YXRpb24gZ3VpZGFuY2UgZm9yIHNlcnZlciBjb25maWc/XQ0KDQoNCg0KDQpJZiB5b3UgaGF2ZSB0
d28gZGlmZmVyZW50IHVzZXMgZm9yIGFuIG9wdGlvbiwgd2l0aCBkaWZmZXJlbnQgc2VtYW50aWNz
LCB5b3Ugc2hvdWxkIGRlZmluZSB0d28gZGlmZmVyZW50IG9wdGlvbnMsIGVhY2ggb2Ygd2hpY2gg
aGFzIG9ubHkgb25lIHNlbWFudGljcy4NCg0KT24gVGh1LCBKdW4gOSwgMjAxNiBhdCAzOjQ0IEFN
LCBJYW4gRmFycmVyIDxpYW5mYXJyZXJAZ214LmNvbTxtYWlsdG86aWFuZmFycmVyQGdteC5jb20+
PiB3cm90ZToNCkhpIE1lZCwNCg0KVG8gYmUgY2xlYXIsIGJvdGggb2YgdGhlIHN1Z2dlc3Rpb25z
IGluY2x1ZGUgdGhlIG1vZGlmaWNhdGlvbiB0byB0aGUgU2VjdGlvbiA1IGNsaWVudCB0ZXh0PyBJ
IHRoaW5rIHRoaXMgaXMgbmVjZXNzYXJ5LiBCdXQgaXMgdGhlIGVycm9yIGNvbmRpdGlvbiB0aGF0
IGFsbCBvZiB0aGUgZW5jbG9zZWQgb3B0aW9ucyBhcmUgdGhlIHNhbWUgc2NvcGUsIG9yIHRoYXQg
dHdvIG9yIG1vcmUgYXJlPw0KDQpCZXR3ZWVuIHRoZSB0d28sIEkgd291bGQgcHJlZmVyICgxKSAt
IGEgTVVTVCBOT1Qgd2l0aCBhbiBleGNlcHRpb24gaXMgYSBTSE9VTEQgTk9ULiBBbiBhbHRlcm5h
dGl2ZSB3b3JkaW5nIHRoYXQgdHJpZXMgdG8gZ2V0IHRoZSBiZXN0IG9mIGJvdGg6DQoNCkEgc2Vy
dmVyIE1VU1QgTk9UIHNlbmQgbW9yZSB0aGFuIG9uIG9uZSBpbnN0YW5jZSBvZiBPUFRJT05fVjZf
UFJFRklYNjQgcGVyIHNjb3BlLiBTZXJ2ZXJzIE1BWSBzZW5kIG9uZSBpbnN0YW5jZSBvZiBPUFRJ
T05fVjZfUFJFRklYNjQgZm9yIGVhY2ggZGlzdGluY3QgSVB2NiBtdWx0aWNhc3QgcHJlZml4IHdp
dGggYSBkaXN0aW5jdCBzY29wZS4NCg0KVGhhbmtzLA0KSWFuDQo=

--_000_787AE7BB302AE849A7480A190F8B933008DAFC9AOPEXCLILMA3corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3Nl
LTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25z
b2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0
aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJn
aW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dl
ZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5
bGUtbGluazoiUHLDqWZvcm1hdMOpIEhUTUwgQ2FyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVy
IE5ldyI7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlRleHRlIGRlIGJ1bGxlcyBD
YXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTo4
LjBwdDsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5QcmZvcm1h
dEhUTUxDYXINCgl7bXNvLXN0eWxlLW5hbWU6IlByw6lmb3JtYXTDqSBIVE1MIENhciI7DQoJbXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQcsOpZm9ybWF0w6kgSFRNTCI7
DQoJZm9udC1mYW1pbHk6IkNvbnNvbGFzIiwic2VyaWYiOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdl
OkZSO30NCnNwYW4uVGV4dGVkZWJ1bGxlc0Nhcg0KCXttc28tc3R5bGUtbmFtZToiVGV4dGUgZGUg
YnVsbGVzIENhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJU
ZXh0ZSBkZSBidWxsZXMiOw0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjsNCglt
c28tZmFyZWFzdC1sYW5ndWFnZTpGUjt9DQpzcGFuLkVtYWlsU3R5bGUyMQ0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ291cmllciBOZXciOw0KCWNvbG9y
OmJsYWNrOw0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0eWxlOm5vcm1hbDt9DQouTXNv
Q2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToi
Q2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCkBw
YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzAuODVw
dCA3MC44NXB0IDcwLjg1cHQgNzAuODVwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29y
ZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0
LWlkOjE0NjUyNzQyNjc7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjIwNzg0MTk0MjI7fQ0KQGxp
c3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2
ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjM2LjBwdDsNCgltc28tbGV2ZWwtbnVt
YmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250
LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDINCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNv
LWxldmVsLXRhYi1zdG9wOjcyLjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7
DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5l
dyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjEwOC4wcHQ7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7
DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0K
QGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjE0NC4wcHQ7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2kt
Zm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2
ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrv
gqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjE4MC4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEw
LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1s
ZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxl
dmVsLXRhYi1zdG9wOjIxNi4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0K
CXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250
LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9w
OjI1Mi4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5n
ZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjI4OC4wcHQ7DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJ
bXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxp
c3QgbDA6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2
ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjMyNC4wcHQ7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9u
dC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0Kb2wNCgl7bWFyZ2luLWJv
dHRvbTowY207fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KLS0+PC9zdHlsZT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9
IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIx
IiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkg
bGFuZz0iRlIiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNl
Y3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+SGkgVGVkLCBJYW4sPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPldoYXQgSSB1bmRlcnN0YW5kIGZyb20gVGVk4oCZcyBjb21tZW50IGlz
IGhlIGlzIG9iamVjdGluZyB0byBhZGQgcmVzdHJpY3Rpb25zIHRvIHRoZSBzZXJ2ZXLigJlzIGJl
aGF2aW9yIHByb3Bvc2VkIGJ5IElhbi4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj5JbiBvcmRlciB0byBhZGRyZXNzIHRoZSBpbml0aWFsIGNvbW1l
bnQgZnJvbSBJYW4sIEkgc3VnZ2VzdCB0aGlzIHRleHQ6DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7IElmIGRpc3RpbmN0IG11bHRpY2FzdCBQUkVG
SVg2NHMgcGVyIHNjb3BlIGFyZSBjb25maWd1cmVkLCB0aGUgREhDUDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7
Jm5ic3A7IHNlcnZlciByZXR1cm5zIG11bHRpcGxlIE9QVElPTl9WNl9QUkVGSVg2NHM7IGVhY2gg
aW5zdGFuY2UgaXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBlbmNsb3NpbmcgZGlzdGluY3QgQVNN
X1BSRUZJWDY0IGFuZCBTU01fUFJFRklYNjQgcGVyIHNjb3BlLiZuYnNwOyBSZWZlciB0bzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90OyI+Jm5ic3A7Jm5ic3A7IFNlY3Rpb24gOCBvZiBbUkZDMjM2NV0gZm9yIGEgbWFwcGluZyBi
ZXR3ZWVuIElQdjQgbXVsdGljYXN0IHByZWZpeGVzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDsmbmJzcDsgdG8g
SVB2NiBtdWx0aWNhc3QgYWRkcmVzcyBzY29wZXMgW1JGQzczNDZdLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7Ij5Db21tZW50cz88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Q2hlZXJzLDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90OyI+TWVkPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNt
IDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10
b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5EZSZuYnNwOzo8
L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gVGVkIExlbW9uIFttYWlsdG86
bWVsbG9uQGZ1Z3VlLmNvbV0NCjxicj4NCjxiPkVudm95w6kmbmJzcDs6PC9iPiBqZXVkaSA5IGp1
aW4gMjAxNiAxNTozNzxicj4NCjxiPsOAJm5ic3A7OjwvYj4gSWFuIEZhcnJlcjxicj4NCjxiPkNj
Jm5ic3A7OjwvYj4gQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTjsgU29mdHdpcmVzIFdHOyBkaGN3
Zy1jaGFpcnNAaWV0Zi5vcmc8YnI+DQo8Yj5PYmpldCZuYnNwOzo8L2I+IFJlOiBbU29mdHdpcmVz
XSBQcm9ibGVtIGluIGRyYWZ0LWlldGYtc29mdHdpcmUtbXVsdGljYXN0LXByZWZpeC1vcHRpb248
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSB3
b3VsZCBzdWdnZXN0OjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjx1bCB0eXBlPSJkaXNjIj4NCjxs
aSBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG87bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPg0KVHdvIG9wdGlv
bnMsIHdpdGggZGlmZmVyZW50IHNlbWFudGljczxvOnA+PC9vOnA+PC9saT48bGkgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj4NCk9wdGlvbiBmb3JtYXQgaXMgb25l
IElQIGFkZHJlc3MgcGVyIG9wdGlvbjxvOnA+PC9vOnA+PC9saT48bGkgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj4NClRoaXMgbWVhbnMgdGhhdCBzZXJ2ZXJzIGNh
bid0IHNlbmQgdHdvIElQIGFkZHJlc3NlcywgYmVjYXVzZSB0aGF0J3Mgbm90IHRoZSBmb3JtYXQg
b2YgdGhlIG9wdGlvbjxvOnA+PC9vOnA+PC9saT48bGkgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21zby1s
aXN0OmwwIGxldmVsMSBsZm8xIj4NCkNsaWVudHMgc2lsZW50bHkgZGlzY2FyZCBtYWxmb3JtZWQg
b3B0aW9ucyAoZG9uJ3QgbmVlZCB0byBzcGVjaWZ5IHRoaXMtLWl0J3MganVzdCB3aGF0IGNsaWVu
dHMgc2hvdWxkIGRvIGluIGdlbmVyYWwpPG86cD48L286cD48L2xpPjxsaSBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG87bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPg0KRGVmaW5lIHRoZSBzZW1hbnRpY3MgZm9y
IHRoZSBjYXNlIHdoZXJlIHRoZSBjbGllbnQgcmVjZWl2ZXMgYm90aCBvcHRpb25zLjxvOnA+PC9v
OnA+PC9saT48L3VsPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBU
aHUsIEp1biA5LCAyMDE2IGF0IDk6MDggQU0sIElhbiBGYXJyZXIgJmx0OzxhIGhyZWY9Im1haWx0
bzppYW5mYXJyZXJAZ214LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmlhbmZhcnJlckBnbXguY29tPC9h
PiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPkhJIFRlZCw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+SWFuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJt
YXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPk9uIDkgSnVuIDIwMTYsIGF0IDE0OjM0LCBUZWQgTGVtb24gJmx0OzxhIGhyZWY9
Im1haWx0bzptZWxsb25AZnVndWUuY29tIiB0YXJnZXQ9Il9ibGFuayI+bWVsbG9uQGZ1Z3VlLmNv
bTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+QWN0dWFsbHksIHRoaXMgaXMgYSBjbGFzc2ljIGV4YW1wbGUgb2Ygd2hhdCB3ZSB0cnkg
dG8gYXZvaWQ6IHNwZWNpYWwgc2VydmVyIGJlaGF2aW9yIGZvciBvcHRpb25zLiAmbmJzcDsgT3B0
aW9ucyBhcmUganVzdCBwYXlsb2FkLCBub3QgcHJvdG9jb2wsIHVubGVzcyB0aGV5IGFyZSBpbnRl
bmRlZCB0byBhZmZlY3QgdGhlIGZsb3cgb2YgdGhlIHByb3RvY29sLiAmbmJzcDsgSXQgc2hvdWxk
IG5vdCBiZSBuZWNlc3NhcnkgZm9yIHRoZQ0KIHNlcnZlciB0byBoYXZlIHNwZWNpYWwgY29kZSB0
byBzdXBwb3J0IGEgZGlmZmVyZW50IHBheWxvYWQsIGFueSBtb3JlIHRoYW4gdGhlIFRDUCBzdGFj
ayBzaG91bGQgaGF2ZSB0byBiZSBtb2RpZmllZCBpbiBvcmRlciB0byBzdXBwb3J0IG5ldyBleHRl
bnNpb25zIHRvIEhUVFAuPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5TbyB5b3UgY291bGQgbWFrZSBhbiBvcGVyYXRpb25hbCBub3RlIGFib3V0IGhvdyBzZXJ2
ZXJzIG91Z2h0IHRvIGJlIGNvbmZpZ3VyZWQsIGJ1dCB5b3Ugc2hvdWxkIG5vdCByZXF1aXJlIHRo
YXQgdGhlIHNlcnZlciBjaGVjayB0byBtYWtlIHN1cmUgaXQgaXMgY29uZmlndXJlZCB0aGF0IHdh
eS4gJm5ic3A7IFlvdSBzaG91bGQgbm90IHJlcXVpcmUgdGhhdCB0aGUgc2VydmVyIHVuZGVyc3Rh
bmQgdGhlIHNlbWFudGljcyBvZg0KIHRoZSBvcHRpb24tLXdoYXQgaXQgbWVhbnMgZm9yIHRoZXJl
IHRvIGJlIHR3byBvZiB0aGVtLCBvciB3aGF0IG9yZGVyIHRoZXkgc2hvdWxkIG9jY3VyIGluLCBv
ciB3aGF0IG1lYW5pbmcgdGhhdCBvcmRlcmluZyBoYXMuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5baWYgLSBTbywgZm9yIHRoZSBvcmlnaW5hbCByZWFzb24gdGhhdCB0aGUgcG9pbnQgd2Fz
IHJhaXNlZCwgZG8geW91IHN1Z2dlc3QgdGhhdCBlbmZvcmNpbmcgdGhpcyBvbmx5IGluIHRoZSBj
bGllbnQgKGkuZS4gaWYgaXQgcmVjZWl2ZXMgYW4gaW52YWxpZCBvcHRpb24gY29tYmluYXRpb24v
Y29udGVudCB0aGVuIGRyb3AgYWxsIGluc3RhbmNlcykgaW4gYWRkaXRpb24gdG8gdGhlIG9wZXJh
dGlvbiBndWlkYW5jZQ0KIGZvciBzZXJ2ZXIgY29uZmlnP108bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxvOnA+
PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5J
ZiB5b3UgaGF2ZSB0d28gZGlmZmVyZW50IHVzZXMgZm9yIGFuIG9wdGlvbiwgd2l0aCBkaWZmZXJl
bnQgc2VtYW50aWNzLCB5b3Ugc2hvdWxkIGRlZmluZSB0d28gZGlmZmVyZW50IG9wdGlvbnMsIGVh
Y2ggb2Ygd2hpY2ggaGFzIG9ubHkgb25lIHNlbWFudGljcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVGh1LCBKdW4gOSwgMjAxNiBhdCAz
OjQ0IEFNLCBJYW4gRmFycmVyICZsdDs8YSBocmVmPSJtYWlsdG86aWFuZmFycmVyQGdteC5jb20i
IHRhcmdldD0iX2JsYW5rIj5pYW5mYXJyZXJAZ214LmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9v
OnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBNZWQsPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRvIGJlIGNs
ZWFyLCBib3RoIG9mIHRoZSBzdWdnZXN0aW9ucyBpbmNsdWRlIHRoZSBtb2RpZmljYXRpb24gdG8g
dGhlIFNlY3Rpb24gNSBjbGllbnQgdGV4dD8gSSB0aGluayB0aGlzIGlzIG5lY2Vzc2FyeS4gQnV0
IGlzIHRoZSBlcnJvciBjb25kaXRpb24gdGhhdCBhbGwgb2YgdGhlIGVuY2xvc2VkIG9wdGlvbnMg
YXJlIHRoZSBzYW1lIHNjb3BlLCBvciB0aGF0IHR3byBvciBtb3JlIGFyZT88bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QmV0d2VlbiB0aGUgdHdv
LCBJIHdvdWxkIHByZWZlciAoMSkgLSBhIE1VU1QgTk9UIHdpdGggYW4gZXhjZXB0aW9uIGlzIGEg
U0hPVUxEIE5PVC4gQW4gYWx0ZXJuYXRpdmUgd29yZGluZyB0aGF0IHRyaWVzIHRvIGdldCB0aGUg
YmVzdCBvZiBib3RoOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5BIHNlcnZlciBNVVNUIE5PVCBzZW5kIG1vcmUgdGhhbiBvbiBvbmUgaW5zdGFu
Y2Ugb2YgT1BUSU9OX1Y2X1BSRUZJWDY0IHBlciBzY29wZS4gU2VydmVycyBNQVkgc2VuZCBvbmUg
aW5zdGFuY2Ugb2YgT1BUSU9OX1Y2X1BSRUZJWDY0IGZvciBlYWNoIGRpc3RpbmN0IElQdjYgbXVs
dGljYXN0IHByZWZpeCB3aXRoIGEgZGlzdGluY3Qgc2NvcGUuJm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyw8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPklhbjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jv
ZHk+DQo8L2h0bWw+DQo=

--_000_787AE7BB302AE849A7480A190F8B933008DAFC9AOPEXCLILMA3corp_--


From nobody Mon Jun 13 06:11:03 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7910D12D607; Mon, 13 Jun 2016 06:11:02 -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: 6.21.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160613131102.12478.17226.idtracker@ietfa.amsl.com>
Date: Mon, 13 Jun 2016 06:11:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/Hpkn6ZFRT9TAjDm5_lA-Ybd2DT8>
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-multicast-prefix-option-11.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 13:11:02 -0000

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

        Title           : DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 Prefixes
        Authors         : Mohamed Boucadair
                          Jacni Qin
                          Tina Tsou
                          Xiaohong Deng
	Filename        : draft-ietf-softwire-multicast-prefix-option-11.txt
	Pages           : 8
	Date            : 2016-06-13

Abstract:
   This document defines a Dynamic Host Configuration Protocol version 6
   (DHCPv6) Option for multicast IPv4 service continuity solutions,
   which is used to carry the IPv6 prefixes to be used to build unicast
   and multicast IPv4-embedded IPv6 addresses.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-multicast-prefix-option-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 Jun 13 09:29:27 2016
Return-Path: <tom@herbertland.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0563512D87E for <softwires@ietfa.amsl.com>; Mon, 13 Jun 2016 09:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 nJPt0tMC-5Ap for <softwires@ietfa.amsl.com>; Mon, 13 Jun 2016 09:29:12 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0658812D583 for <softwires@ietf.org>; Mon, 13 Jun 2016 09:29:07 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id h190so46856111ith.1 for <softwires@ietf.org>; Mon, 13 Jun 2016 09:29:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=du4m1CiAht/rWn4Pu541Szj3Q9nuu59Dq4Mqrbk8uQE=; b=bJbvuLN8iv02D9MyVIThRticmNUVLQpNOCfGrMOvmgUzjeD5sK5T2eRSUE8K1rl1Uu RWC1v3P8Jj5DUAN4PuDTHx4eNiwO0NT8A/OmyBAH+6nMdAgn1GagGhJrmN5z1XN+68he 6fQHMHth/W0He/YSnWWF7Z0kPhIqMlGfZIP/fBW8ebsn1qZ0S5ELgvc6bTx1aV6UTbnp 1YTmVryS1b0ut8XkYeY1SRAJ/I/npqNZlBJ7kcmvSkBOW0/FrkzsJDIiNETVEXpv9tX6 klra8rK7AaiyKcjYH5r0ASt1woSosj1t7vgSIlTDK5FyhfsoFB1BUrUsm7ojLJAhKozl Btww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=du4m1CiAht/rWn4Pu541Szj3Q9nuu59Dq4Mqrbk8uQE=; b=IYdtIrVkUK5zKshtdXD6n6ASYo98ywFTxiKjRx6Py2fygaK571YwWX8vvBB7qfpU16 Tm4YWkeiJMae49EhLVI4jVQmT747n3HNtjxHnC1dxwbKNbgnGCtyur8oKoetMpeGeCNH fLJNPxw+aSOHQYOyssvpI+mEYfjLRlnVPvRgJkoN1iz2nSiB+F/FQz0X5wg/AXCyheNE 55NPaPYs2HXGxlMgsIE16NztQzOwtz9bBmHroC0hhKDlh39tvu5Hzue4vWHD9js9SMOg vn1PMGslCElTmF3mvyGiZv6+SsxqCYJ73VMZCqxOuH40xywjQD82od4krTAGd1ZGFDkS +NkQ==
X-Gm-Message-State: ALyK8tLRM5Xl8tHFbHGcauEHdgna2EQdUtVG0U4plpCNIDOUkwM2spj4JskR/aM++wngMTdO2CH82SgyjyLAow==
MIME-Version: 1.0
X-Received: by 10.36.73.219 with SMTP id e88mr841383itd.88.1465835346137; Mon, 13 Jun 2016 09:29:06 -0700 (PDT)
Received: by 10.107.31.202 with HTTP; Mon, 13 Jun 2016 09:29:05 -0700 (PDT)
In-Reply-To: <974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com>
Date: Mon, 13 Jun 2016 09:29:05 -0700
Message-ID: <CALx6S362S-n6qqEX-qLTubKqGpvP95O1t_Bvp3UMmAAUpe9teQ@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/65jqAMzoHWnGg0CQnrm77Jclqlo>
Cc: "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, Softwires WG <softwires@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Softwires] [tsvwg] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 16:29:14 -0000

On Sat, Jun 11, 2016 at 10:11 PM, Lloyd Wood <lloyd.wood@yahoo.co.uk> wrote:
> Fragmentation should be strongly discouraged.
>
> if you've designed a tunnelling solution and you have fragmentation
> happening as a matter of course, you've designed it wrong.
>

As mentioned before we do not always have control of the underlay MTUs
to be able to set Jumbo Frames to make MTU larger than 1500 to account
for tunnel fragmentation. At Facebook for instance, we run IP tunnels
between L4 load balancers and backend servers. In certain POPs we
cannot get more than 1500 MTU in the path. The ingress MTU into the
load balancer is 1500 so it is possible to receive packets from the
Internet that are greater than the tunnel MTU. In this case we will
fragment. Since the tunnel is behind a firewall and our devices and
the path from load balancers to backends is low loss there is little
concern of being DOSed.

Tom

> Lloyd Wood
> lloyd.wood@yahoo.co.uk
>
> On Friday, May 27, 2016, 8:10 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>
> <Note that I have changed the subject of the email hence it has nothing to
> do with the WG adoption call now. It's just a discussion on a particular
> issue which is related to those WGs which are working on UDP tunnels. The
> reason for containing the old email is to use it as a background which may
> be useful for better understanding of this particular issue>
>
> The possible side-effect of performing fragmentation on UDP encapsulated
> packets is to worsen the reassembly burden on tunnel egress since fragments
> of UDP encapsulated packets are more likely to be forwarded across different
> paths towards the tunnel egress than those of IP or GRE encapsulated
> packets.
>
> It seems that most X-over-UDP proposals choose to prohibit the tunnel
> ingress from performing fragmentation on UDP encapsulated packets. See the
> following quoted text regarding fragmentation from those X-over-UDP drafts:
>
> LISP:
>
> When an ITR receives a packet from a site-facing interface and adds H
>   octets worth of encapsulation to yield a packet size greater than L
>   octets, it resolves the MTU issue by first splitting the original
>   packet into 2 equal-sized fragments.  A LISP header is then prepended
>   to each fragment.
>
> VXLAN:
>
> VTEPs MUST NOT fragment VXLAN packets.  Intermediate routers may
>   fragment encapsulated VXLAN packets due to the larger frame size.
>   The destination VTEP MAY silently discard such VXLAN fragments.
>
> VXLAN-GPE:
>
> VTEPs MUST never fragment an encapsulated VXLAN GPE packet, and when
>   the outer IP header is IPv4, VTEPs MUST set the DF bit in the outer
>   IPv4 header.
>
> GEVENE:
>
>   To prevent fragmentation and maximize performance, the best practice
>   when using Geneve is to ensure that the MTU of the physical network
>   is greater than or equal to the MTU of the encapsulated network plus
>   tunnel headers.
>
> GUE:
>
>     If a packet is fragmented before encapsulation in GUE, all the
>     related fragments must be encapsulated using the same source port
>     (inner flow identifier). An operator may set MTU to account for
>     encapsulation overhead and reduce the likelihood of fragmentation.
>
> GRE/UDP
>
> Regarding packet fragmentation, an encapsulator/decapsulator SHOULD
>   be compliant with [RFC7588] and perform fragmentation before the
>   encapsulation.
>
> However, the above choice seems conflict with the requirements as described
> in https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02
>
>
> I wonder whether the IETF should reach a consensus on whether or not the
> fragmentation on UDP encapsulated packets should be allowed.
>
> Best regards,
> Xiaohu
>
>> -----Original Message-----
>> From: Xuxiaohu
>> Sent: Thursday, May 26, 2016 4:35 PM
>> To: 'Joe Touch'; Fred Baker (fred); Wassim Haddad
>> Cc: int-area@ietf.org
>> Subject: RE: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03
>>
>>
>>
>> > -----Original Message-----
>> > From: Joe Touch [mailto:touch@isi.edu]
>> > Sent: Thursday, May 26, 2016 2:11 AM
>> > To: Xuxiaohu; Fred Baker (fred); Wassim Haddad
>> > Cc: int-area@ietf.org
>> > Subject: Re: [Int-area] Call for adoption of
>> > draft-xu-intarea-ip-in-udp-03
>> >
>> >
>> >
>> > On 5/24/2016 7:24 PM, Xuxiaohu wrote:
>> > > Hi Joe,
>> > >
>> > > I wonder whether you want to tell me the following truth by the
>> > > example that you gave: no matter whatever improvements we had done
>> > > with this draft, those persons who dislike it by the light of nature
>> > > would dislike it in the end.
>> >
>> > The only improvements that would make this doc useful would be to add
>> > capabilities already in GRE/UDP or GUE/UDP, which we already have.
>>
>> Let's go over the four things you mentioned earlier in GRE/UDP and
>> GUE/UDP:
>>
>>     - stronger checksums
>>
>> In GRE/UDP, in order to use UDP-zero-checksum, it gave the following
>> restrictions:
>> " 6. UDP Checksum Handling
>>
>>    6.1. UDP Checksum with IPv4
>>
>>    For UDP in IPv4, the UDP checksum MUST be processed as specified in
>>    [RFC768] and [RFC1122] for both transmit and receive. The IPv4
>>
>>
>>
>> Yong, Crabber, Xu, Herbert                                    [Page 12]
>>
>> --------------------------------------------------------------------------------
>>
>> Internet-Draft          GRE-in-UDP Encapsulation            March 2016
>>
>>    header includes a checksum which protects against mis-delivery of
>>    the packet due to corruption of IP addresses. The UDP checksum
>>    potentially provides protection against corruption of the UDP header,
>>    GRE header, and GRE payload. Disabling the use of checksums is a
>>    deployment consideration that should take into account the risk and
>>    effects of packet corruption.
>>
>>    When a decapsulator receives a packet, the UDP checksum field MUST
>>    be processed. If the UDP checksum is non-zero, the decapsulator MUST
>>    verify the checksum before accepting the packet. By default a
>>    decapsulator SHOULD accept UDP packets with a zero checksum. A node
>>    MAY be configured to disallow zero checksums per [RFC1122]; this may
>>    be done selectively, for instance disallowing zero checksums from
>>    certain hosts that are known to be sending over paths subject to
>>    packet corruption. If verification of a non-zero checksum fails, a
>>    decapsulator lacks the capability to verify a non-zero checksum, or
>>    a packet with a zero-checksum was received and the decapsulator is
>>    configured to disallow, the packet MUST be dropped and an event MAY
>>    be logged.
>>
>>    6.2. UDP Checksum with IPv6
>>
>>    For UDP in IPv6, the UDP checksum MUST be processed as specified in
>>    [RFC768] and [RFC2460] for both transmit and receive.
>>
>>    When UDP is used over IPv6, the UDP checksum is relied upon to
>>    protect both the IPv6 and UDP headers from corruption. As such, A
>>    default GRE-in-UDP Tunnel MUST perform UDP checksum; A TMCE GRE-in-
>>    UDP Tunnel MAY be configured with the UDP zero-checksum mode if the
>>    traffic-managed controlled environment or a set of closely
>>    cooperating traffic-managed controlled environments (such as by
>>    network operators who have agreed to work together in order to
>>    jointly provide specific services) meet at least one of following
>>    conditions:
>>
>>    a. It is known (perhaps through knowledge of equipment types and
>>      lower layer checks) that packet corruption is exceptionally
>>      unlikely and where the operator is willing to take the risk of
>>      undetected packet corruption.
>>
>>    b. It is judged through observational measurements (perhaps of
>>      historic or current traffic flows that use a non-zero checksum)
>>      that the level of packet corruption is tolerably low and where
>>      the operator is willing to take the risk of undetected packet
>>      corruption.
>>
>>
>>
>>
>>
>> Yong, Crabber, Xu, Herbert                                    [Page 13]
>>
>> --------------------------------------------------------------------------------
>>
>> Internet-Draft          GRE-in-UDP Encapsulation            March 2016
>>
>>    c. Carrying applications that are tolerant of mis-delivered or
>>      corrupted packets (perhaps through higher layer checksum,
>>      validation, and retransmission or transmission redundancy) where
>>      the operator is willing to rely on the applications using the
>>      tunnel to survive any corrupt packets.
>>
>>    The following requirements apply to a TMCE GRE-in-UDP tunnel that
>>    use UDP zero-checksum mode:
>>
>>      a. Use of the UDP checksum with IPv6 MUST be the default
>>        configuration of all GRE-in-UDP tunnels.
>>
>>      b. The GRE-in-UDP tunnel implementation MUST comply with all
>>        requirements specified in Section 4 of [RFC6936] and with
>>        requirement 1 specified in Section 5 of [RFC6936].
>>
>>      c. The tunnel decapsulator SHOULD only allow the use of UDP zero-
>>        checksum mode for IPv6 on a single received UDP Destination
>>        Port regardless of the encapsulator. The motivation for this
>>        requirement is possible corruption of the UDP Destination Port,
>>        which may cause packet delivery to the wrong UDP port. If that
>>        other UDP port requires the UDP checksum, the mis-delivered
>>        packet will be discarded.
>>
>>      d. It is RECOMMENDED that the UDP zero-checksum mode for IPv6 is
>>        only enabled for certain selected source addresses. The tunnel
>>        decapsulator MUST check that the source and destination IPv6
>>        addresses are valid for the GRE-in-UDP tunnel on which the
>>        packet was received if that tunnel uses UDP zero-checksum mode
>>        and discard any packet for which this check fails.
>>
>>      e. The tunnel encapsulator SHOULD use different IPv6 addresses for
>>        each GRE-in-UDP tunnel that uses UDP zero-checksum mode
>>        regardless of the decapsulator in order to strengthen the
>>        decapsulator's check of the IPv6 source address (i.e., the same
>>        IPv6 source address SHOULD NOT be used with more than one IPv6
>>        destination address, independent of whether that destination
>>        address is a unicast or multicast address). When this is not
>>        possible, it is RECOMMENDED to use each source IPv6 address for
>>        as few UDP zero-checksum mode GRE-in-UDP tunnels as is feasible.
>>
>>      f. When any middlebox exists on the path of a GRE-in-UDP tunnel,
>>        it is RECOMMENDED to use the default mode, i.e. use UDP
>>        checksum, to reduce the chance that the encapsulated packets to
>>        be dropped.
>>
>>
>>
>>
>>
>> Yong, Crabber, Xu, Herbert                                    [Page 14]
>>
>> --------------------------------------------------------------------------------
>>
>> Internet-Draft          GRE-in-UDP Encapsulation            March 2016
>>
>>      g. Any middlebox that allows the UDP zero-checksum mode for IPv6
>>        MUST comply with requirement 1 and 8-10 in Section 5 of
>>        [RFC6936].
>>
>>      h. Measures SHOULD be taken to prevent IPv6 traffic with zero UDP
>>        checksums from "escaping" to the general Internet; see Section
>>        8 for examples of such measures.
>>
>>      i. IPv6 traffic with zero UDP checksums MUST be actively monitored
>>        for errors by the network operator. For example, the operator
>>        may monitor Ethernet layer packet error rates.
>>
>>      j. If a packet with a non-zero checksum is received, the checksum
>>        MUST be verified before accepting the packet. This is
>>        regardless of whether the tunnel encapsulator and decapsulator
>>        have been configured with UDP zero-checksum mode.
>>
>>    The above requirements do not change either the requirements
>>    specified in [RFC2460] as modified by [RFC6935] or the requirements
>>    specified in [RFC6936].
>>
>>    The requirement to check the source IPv6 address in addition to the
>>    destination IPv6 address, plus the strong recommendation against
>>    reuse of source IPv6 addresses among GRE-in-UDP tunnels collectively
>>    provide some mitigation for the absence of UDP checksum coverage of
>>    the IPv6 header. A traffic-managed controlled environment that
>>    satisfies at least one of three conditions listed above in this
>>    section provides additional assurance.
>>
>>    A GRE-in-UDP tunnel is suitable for transmission over lower layers
>>    in the traffic-managed controlled environments that are allowed by
>>    the exceptions stated above and the rate of corruption of the inner
>>    IP packet on such networks is not expected to increase by comparison
>>    to GRE traffic that is not encapsulated in UDP.  For these reasons,
>>    GRE-in-UDP does not provide an additional integrity check except
>>    when GRE checksum is used when UDP zero-checksum mode is used with
>>    IPv6, and this design is in accordance with requirements 2, 3 and 5
>>    specified in Section 5 of [RFC6936].
>>
>>    Generic Router Encapsulation (GRE) does not accumulate incorrect
>>    state as a consequence of GRE header corruption. A corrupt GRE
>>    packet may result in either packet discard or forwarding of the
>>    packet without accumulation of GRE state. Active monitoring of GRE-
>>    in-UDP traffic for errors is REQUIRED as occurrence of errors will
>>    result in some accumulation of error information outside the
>>    protocol for operational and management purposes. This design is in
>>    accordance with requirement 4 specified in Section 5 of [RFC6936].
>>
>>
>>
>> Yong, Crabber, Xu, Herbert                                    [Page 15]
>>
>> --------------------------------------------------------------------------------
>>
>> Internet-Draft          GRE-in-UDP Encapsulation            March 2016
>>
>>    The remaining requirements specified in Section 5 of [RFC6936] are
>>    not applicable to GRE-in-UDP.  Requirements 6 and 7 do not apply
>>    because GRE does not include a control feedback mechanism.
>>    Requirements 8-10 are middlebox requirements that do not apply to
>>    GRE-in-UDP tunnel endpoints (see Section 7.1 for further middlebox
>>    discussion).
>>
>>    It is worth mentioning that the use of a zero UDP checksum should
>>    present the equivalent risk of undetected packet corruption when
>>    sending similar packet using GRE-in-IPv6 without UDP [RFC7676] and
>>    without GRE checksums.
>>
>>    In summary, a TMCE GRE-in-UDP Tunnel is allowed to use UDP-zero-
>>    checksum mode for IPv6 when the conditions and requirements stated
>>    above are met. Otherwise the UDP checksum need to be used for IPv6
>>    as specified in [RFC768] and [RFC2460]. Use of GRE checksum is
>>    RECOMMENED when the UDP checksum is not used.
>> "
>>
>> In GUE, to support UDP-checksum-zero, it said
>>
>> " Therefore, when GUE is used over
>>    IPv6, either the UDP checksum must be enabled or the GUE header
>>    checksum must be used.  An encapsulator MAY set a zero UDP checksum
>>    for performance or implementation reasons, in which case the GUE
>>    header checksum MUST be used or applicable requirements for using
>>    zero UDP checksums in [GREUDP] MUST be met. If the UDP checksum is
>>    enabled, then the GUE header checksum should not be used since it is
>>    mostly redundant."
>>
>> It's easy for me to add the similar words to the IP-in-UDP draft like "the
>> applicable requirements for using zero UDP checksum in [GREUDP] MUST be
>> met when zero UDP checksum is used by the tunnel ingress". However, the
>> major goal for disabling the UDP checksum is to improve the performance.
>> When GUE header checksum is used and/or the bunch of applicable
>> requirements as described in GRE/UDP are verified, is the goal of
>> improving
>> performance still achievable? If not, why not directly enable the
>> UDP-checksum
>> instead?
>>
>>     - fragmentation support
>>
>> In GRE/UDP, it said
>>
>> " 4.1. MTU and Fragmentation
>>
>>    Regarding packet fragmentation, an encapsulator/decapsulator SHOULD
>>    be compliant with [RFC7588] and perform fragmentation before the
>>    encapsulation. The size of fragments SHOULD be less or equal to the
>>    PMTU associated with the path between the GRE ingress and the GRE
>>    egress tunnel endpoints minus the GRE and UDP overhead ..."
>>
>> in GUE, it said
>>
>> " 4.9. MTU and fragmentation
>>
>>    Standard conventions for handling of MTU (Maximum Transmission Unit)
>>    and fragmentation in conjunction with networking tunnels
>>    (encapsulation of layer 2 or layer 3 packets) should be followed.
>>    Details are described in MTU and Fragmentation Issues with In-the-
>>    Network Tunneling [RFC4459]... "
>>
>> It seems that the only missing thing in the IP-in-UDP draft is to allow
>> the outer
>> fragmentation. However, as it said in
>> (https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02#page-13), "
>> ...IPsec
>> performs only Outer Fragmentation; this distinguishes it from IP-in-IP,
>> which
>> performs only Inner Fragmentation. " Note that IP-in-IP is the dominant
>> encapsulation choice within Softwires networks. In other words, performing
>> only inner fragmentation works very well in practice. Furthermore, the
>> outer
>> fragmentation issue (e.g., reassembly cost for the egress) would become
>> even
>> worse since the fragments of X-in-UDP packets are more likely to be
>> forwarded
>> across different paths than those of X-in-IP and X-in-GRE packets. Hence,
>> I'm
>> wondering whether it's worthwhile to support the outer fragmentation on
>> UDP
>> encapsulated packets which seems useless in practice.
>>
>>     - signalling support (e.g., to test whether a tunnel is up or
>>     to measure MTUs)
>>
>> I haven't found any description of this in both GRE/UDP and GUE. Did you?
>>
>>     - support for robust ID fields (related to fragmentation,
>>     e.g., to overcome the limits of IPv4 ID as per RFC 6864)
>>
>> I haven't found any description of this in both GRE/UDP and GUE. Did you?
>>
>> Xiaohu
>>
>> > It is not our obligation to find a way for your document to proceed -
>> > that onus is on you.
>> >
>> > Joe


From nobody Wed Jun 15 14:00:46 2016
Return-Path: <lloyd.wood@yahoo.co.uk>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7683F12B009 for <softwires@ietfa.amsl.com>; Sat, 11 Jun 2016 22:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.co.uk
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 er6Y1QBBei8A for <softwires@ietfa.amsl.com>; Sat, 11 Jun 2016 22:12:04 -0700 (PDT)
Received: from nm37-vm9.bullet.mail.ir2.yahoo.com (nm37-vm9.bullet.mail.ir2.yahoo.com [212.82.97.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C81E12D0BA for <softwires@ietf.org>; Sat, 11 Jun 2016 22:12:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1465708321; bh=7Se32ZYrkdGNcXAih3GRNcv6HBs9n7Jmp92OGL8H46c=;  h=Date:From:To:In-Reply-To:References:Subject:From:Subject; b=TYIoXWagL6xDy3Dk9kwxVG4YylXaIowdbAb21ZpWyuXwQPj9abMMZWvAIz+AOn6x/TdPRquxHalJ/+Lgg4ciow+7jAKroYKCnXmf3cX7IrFaW8Jo4Q+NsQ7fmE9yr6h6XOEuN8JWzJDeDTc8PwfRU7Ig6o0xetUtGQudcYW010UBFRtmfTsBpNHBYhR+BZnBp3wl0FaFjIZDiuhHvs3qAaXjtprZpox4wn8BmGzkS2ndOHWqgEWbmYDetYQd64SPppW0omwr4SFh103mp/n03PiDQ+pmFQ6o+MKTgQ5DRdwVfyVdTaZoJE9b5G5oaI/D20lTiu6ec8nKbfzOAjianQ==
Received: from [212.82.98.60] by nm37.bullet.mail.ir2.yahoo.com with NNFMP; 12 Jun 2016 05:12:01 -0000
Received: from [212.82.98.74] by tm13.bullet.mail.ir2.yahoo.com with NNFMP; 12 Jun 2016 05:12:01 -0000
Received: from [127.0.0.1] by omp1011.mail.ir2.yahoo.com with NNFMP; 12 Jun 2016 05:12:01 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 386946.51620.bm@omp1011.mail.ir2.yahoo.com
X-YMail-OSG: Mr0y7sAVM1nNjVny5KH7JBLwqtJyjHkK9jJ7I2ykKiZRSnGHz_uneCAabFPpgvT a8pqlD5KR3faKXGnd2RJu.A9.ubxxkR_4NTkEjPowc7X44s3nQLtPl6kSwVIeItkvKUv.lOPa3wf FH5AKoAgOnbAI_ScLr1WmnIykD2sJ8OcY3fDHuO5h7BCzuGzN6T.ndTTcPB97K3VQiZCqoCzqheD _o_obru7Pa53Gojoa_6goZhJnWrynhHH2jzyqFuOnDyHhepneFa4IixhF_b_jDm_PEqR_DEyMEBs 8hrzm3i9Pu0QQhSGJxnIviQdxTVrhqKo9ilaFuBk7QnFNmmDWiqJYAPZyzAGsM6HgcpRDQjiNQYf owO2dvt9oH.zGCRvi0eJAgFe26xA6CWLwLmQWak63UDhjqueCuteqt19Otm47xVHBR7wmtFGMMcJ 68bT1TNVagFb1PXtlj7HUKGGQeQ1xK9flLX1bFP08b_d9N1mHeNYMbHB8vpNW5r8Bf0oRLBHAlWg .vRp0cYY6htUpMukwmg0Ok30avsh6v06EC.4VmyXxdw--
Received: from jws11172.mail.ir2.yahoo.com by sendmailws161.mail.ir2.yahoo.com;  Sun, 12 Jun 2016 05:12:00 +0000; 1465708320.697
Date: Sun, 12 Jun 2016 05:11:48 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: Softwires WG <softwires@ietf.org>,  "int-area@ietf.org" <int-area@ietf.org>,  "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>,  Xuxiaohu <xuxiaohu@huawei.com>, "nvo3@ietf.org" <nvo3@ietf.org>
Message-ID: <974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_2492240_1136524516.1465708308517"
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/bsXPreSF4p37EwHLeU4mazpivlM>
X-Mailman-Approved-At: Wed, 15 Jun 2016 14:00:44 -0700
Subject: Re: [Softwires] [tsvwg] Is it feasible to perform fragmentation on UDP encapsulated	packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 12 Jun 2016 05:12:07 -0000

------=_Part_2492240_1136524516.1465708308517
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

 blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px =
#715FFA solid !important; padding-left:1ex !important; background-color:whi=
te !important; }  Fragmentation should be strongly discouraged.
if you've designed a tunnelling solution and you have fragmentation happeni=
ng as a matter of course, you've designed it wrong.=C2=A0

Lloyd Woodlloyd.wood@yahoo.co.uk

On Friday, May 27, 2016, 8:10 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:

<Note that I have changed the subject of the email hence it has nothing to =
do with the WG adoption call now. It's just a discussion on a particular is=
sue which is related to those WGs which are working on UDP tunnels. The rea=
son for containing the old email is to use it as a background which may be =
useful for better understanding of this particular issue>

The possible side-effect of performing fragmentation on UDP encapsulated pa=
ckets is to worsen the reassembly burden on tunnel egress since fragments o=
f UDP encapsulated packets are more likely to be forwarded across different=
 paths towards the tunnel egress than those of IP or GRE encapsulated packe=
ts.

It seems that most X-over-UDP proposals choose to prohibit the tunnel ingre=
ss from performing fragmentation on UDP encapsulated packets. See the follo=
wing quoted text regarding fragmentation from those X-over-UDP drafts:

LISP:

When an ITR receives a packet from a site-facing interface and adds H
=C2=A0 octets worth of encapsulation to yield a packet size greater than L
=C2=A0 octets, it resolves the MTU issue by first splitting the original
=C2=A0 packet into 2 equal-sized fragments.=C2=A0 A LISP header is then pre=
pended
=C2=A0 to each fragment.

VXLAN:

VTEPs MUST NOT fragment VXLAN packets.=C2=A0 Intermediate routers may
=C2=A0 fragment encapsulated VXLAN packets due to the larger frame size.
=C2=A0 The destination VTEP MAY silently discard such VXLAN fragments.

VXLAN-GPE:

VTEPs MUST never fragment an encapsulated VXLAN GPE packet, and when
=C2=A0 the outer IP header is IPv4, VTEPs MUST set the DF bit in the outer
=C2=A0 IPv4 header.

GEVENE:

=C2=A0 To prevent fragmentation and maximize performance, the best practice
=C2=A0 when using Geneve is to ensure that the MTU of the physical network
=C2=A0 is greater than or equal to the MTU of the encapsulated network plus
=C2=A0 tunnel headers.

GUE:

=C2=A0 =C2=A0 If a packet is fragmented before encapsulation in GUE, all th=
e
=C2=A0 =C2=A0 related fragments must be encapsulated using the same source =
port
=C2=A0 =C2=A0 (inner flow identifier). An operator may set MTU to account f=
or
=C2=A0 =C2=A0 encapsulation overhead and reduce the likelihood of fragmenta=
tion.

GRE/UDP

Regarding packet fragmentation, an encapsulator/decapsulator SHOULD
=C2=A0 be compliant with [RFC7588] and perform fragmentation before the
=C2=A0 encapsulation.

However, the above choice seems conflict with the requirements as described=
 in https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02


I wonder whether the IETF should reach a consensus on whether or not the fr=
agmentation on UDP encapsulated packets should be allowed.
=C2=A0=20
Best regards,
Xiaohu

> -----Original Message-----
> From: Xuxiaohu
> Sent: Thursday, May 26, 2016 4:35 PM
> To: 'Joe Touch'; Fred Baker (fred); Wassim Haddad
> Cc: int-area@ietf.org
> Subject: RE: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-0=
3
>=20
>=20
>=20
> > -----Original Message-----
> > From: Joe Touch [mailto:touch@isi.edu]
> > Sent: Thursday, May 26, 2016 2:11 AM
> > To: Xuxiaohu; Fred Baker (fred); Wassim Haddad
> > Cc: int-area@ietf.org
> > Subject: Re: [Int-area] Call for adoption of
> > draft-xu-intarea-ip-in-udp-03
> >
> >
> >
> > On 5/24/2016 7:24 PM, Xuxiaohu wrote:
> > > Hi Joe,
> > >
> > > I wonder whether you want to tell me the following truth by the
> > > example that you gave: no matter whatever improvements we had done
> > > with this draft, those persons who dislike it by the light of nature
> > > would dislike it in the end.
> >
> > The only improvements that would make this doc useful would be to add
> > capabilities already in GRE/UDP or GUE/UDP, which we already have.
>=20
> Let's go over the four things you mentioned earlier in GRE/UDP and GUE/UD=
P:
>=20
> =C2=A0=C2=A0=C2=A0 - stronger checksums
>=20
> In GRE/UDP, in order to use UDP-zero-checksum, it gave the following
> restrictions:
> " 6. UDP Checksum Handling
>=20
>=C2=A0 =C2=A0 6.1. UDP Checksum with IPv4
>=20
>=C2=A0 =C2=A0 For UDP in IPv4, the UDP checksum MUST be processed as speci=
fied in
>=C2=A0 =C2=A0 [RFC768] and [RFC1122] for both transmit and receive. The IP=
v4
>=20
>=20
>=20
> Yong, Crabber, Xu, Herbert=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 [Page 12]
> -------------------------------------------------------------------------=
-------
>=20
> Internet-Draft=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 GRE-in-UDP Encapsulation=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 March 2016
>=20
>=C2=A0 =C2=A0 header includes a checksum which protects against mis-delive=
ry of
>=C2=A0 =C2=A0 the packet due to corruption of IP addresses. The UDP checks=
um
>=C2=A0 =C2=A0 potentially provides protection against corruption of the UD=
P header,
>=C2=A0 =C2=A0 GRE header, and GRE payload. Disabling the use of checksums =
is a
>=C2=A0 =C2=A0 deployment consideration that should take into account the r=
isk and
>=C2=A0 =C2=A0 effects of packet corruption.
>=20
>=C2=A0 =C2=A0 When a decapsulator receives a packet, the UDP checksum fiel=
d MUST
>=C2=A0 =C2=A0 be processed. If the UDP checksum is non-zero, the decapsula=
tor MUST
>=C2=A0 =C2=A0 verify the checksum before accepting the packet. By default =
a
>=C2=A0 =C2=A0 decapsulator SHOULD accept UDP packets with a zero checksum.=
 A node
>=C2=A0 =C2=A0 MAY be configured to disallow zero checksums per [RFC1122]; =
this may
>=C2=A0 =C2=A0 be done selectively, for instance disallowing zero checksums=
 from
>=C2=A0 =C2=A0 certain hosts that are known to be sending over paths subjec=
t to
>=C2=A0 =C2=A0 packet corruption. If verification of a non-zero checksum fa=
ils, a
>=C2=A0 =C2=A0 decapsulator lacks the capability to verify a non-zero check=
sum, or
>=C2=A0 =C2=A0 a packet with a zero-checksum was received and the decapsula=
tor is
>=C2=A0 =C2=A0 configured to disallow, the packet MUST be dropped and an ev=
ent MAY
>=C2=A0 =C2=A0 be logged.
>=20
>=C2=A0 =C2=A0 6.2. UDP Checksum with IPv6
>=20
>=C2=A0 =C2=A0 For UDP in IPv6, the UDP checksum MUST be processed as speci=
fied in
>=C2=A0 =C2=A0 [RFC768] and [RFC2460] for both transmit and receive.
>=20
>=C2=A0 =C2=A0 When UDP is used over IPv6, the UDP checksum is relied upon =
to
>=C2=A0 =C2=A0 protect both the IPv6 and UDP headers from corruption. As su=
ch, A
>=C2=A0 =C2=A0 default GRE-in-UDP Tunnel MUST perform UDP checksum; A TMCE =
GRE-in-
>=C2=A0 =C2=A0 UDP Tunnel MAY be configured with the UDP zero-checksum mode=
 if the
>=C2=A0 =C2=A0 traffic-managed controlled environment or a set of closely
>=C2=A0 =C2=A0 cooperating traffic-managed controlled environments (such as=
 by
>=C2=A0 =C2=A0 network operators who have agreed to work together in order =
to
>=C2=A0 =C2=A0 jointly provide specific services) meet at least one of foll=
owing
>=C2=A0 =C2=A0 conditions:
>=20
>=C2=A0 =C2=A0 a. It is known (perhaps through knowledge of equipment types=
 and
>=C2=A0 =C2=A0 =C2=A0 lower layer checks) that packet corruption is excepti=
onally
>=C2=A0 =C2=A0 =C2=A0 unlikely and where the operator is willing to take th=
e risk of
>=C2=A0 =C2=A0 =C2=A0 undetected packet corruption.
>=20
>=C2=A0 =C2=A0 b. It is judged through observational measurements (perhaps =
of
>=C2=A0 =C2=A0 =C2=A0 historic or current traffic flows that use a non-zero=
 checksum)
>=C2=A0 =C2=A0 =C2=A0 that the level of packet corruption is tolerably low =
and where
>=C2=A0 =C2=A0 =C2=A0 the operator is willing to take the risk of undetecte=
d packet
>=C2=A0 =C2=A0 =C2=A0 corruption.
>=20
>=20
>=20
>=20
>=20
> Yong, Crabber, Xu, Herbert=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 [Page 13]
> -------------------------------------------------------------------------=
-------
>=20
> Internet-Draft=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 GRE-in-UDP Encapsulation=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 March 2016
>=20
>=C2=A0 =C2=A0 c. Carrying applications that are tolerant of mis-delivered =
or
>=C2=A0 =C2=A0 =C2=A0 corrupted packets (perhaps through higher layer check=
sum,
>=C2=A0 =C2=A0 =C2=A0 validation, and retransmission or transmission redund=
ancy) where
>=C2=A0 =C2=A0 =C2=A0 the operator is willing to rely on the applications u=
sing the
>=C2=A0 =C2=A0 =C2=A0 tunnel to survive any corrupt packets.
>=20
>=C2=A0 =C2=A0 The following requirements apply to a TMCE GRE-in-UDP tunnel=
 that
>=C2=A0 =C2=A0 use UDP zero-checksum mode:
>=20
>=C2=A0 =C2=A0 =C2=A0 a. Use of the UDP checksum with IPv6 MUST be the defa=
ult
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 configuration of all GRE-in-UDP tunnels.
>=20
>=C2=A0 =C2=A0 =C2=A0 b. The GRE-in-UDP tunnel implementation MUST comply w=
ith all
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 requirements specified in Section 4 of [RFC693=
6] and with
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 requirement 1 specified in Section 5 of [RFC69=
36].
>=20
>=C2=A0 =C2=A0 =C2=A0 c. The tunnel decapsulator SHOULD only allow the use =
of UDP zero-
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 checksum mode for IPv6 on a single received UD=
P Destination
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Port regardless of the encapsulator. The motiv=
ation for this
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 requirement is possible corruption of the UDP =
Destination Port,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 which may cause packet delivery to the wrong U=
DP port. If that
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 other UDP port requires the UDP checksum, the =
mis-delivered
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 packet will be discarded.
>=20
>=C2=A0 =C2=A0 =C2=A0 d. It is RECOMMENDED that the UDP zero-checksum mode =
for IPv6 is
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 only enabled for certain selected source addre=
sses. The tunnel
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 decapsulator MUST check that the source and de=
stination IPv6
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 addresses are valid for the GRE-in-UDP tunnel =
on which the
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 packet was received if that tunnel uses UDP ze=
ro-checksum mode
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 and discard any packet for which this check fa=
ils.
>=20
>=C2=A0 =C2=A0 =C2=A0 e. The tunnel encapsulator SHOULD use different IPv6 =
addresses for
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 each GRE-in-UDP tunnel that uses UDP zero-chec=
ksum mode
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 regardless of the decapsulator in order to str=
engthen the
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 decapsulator's check of the IPv6 source addres=
s (i.e., the same
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 IPv6 source address SHOULD NOT be used with mo=
re than one IPv6
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 destination address, independent of whether th=
at destination
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 address is a unicast or multicast address). Wh=
en this is not
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 possible, it is RECOMMENDED to use each source=
 IPv6 address for
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 as few UDP zero-checksum mode GRE-in-UDP tunne=
ls as is feasible.
>=20
>=C2=A0 =C2=A0 =C2=A0 f. When any middlebox exists on the path of a GRE-in-=
UDP tunnel,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 it is RECOMMENDED to use the default mode, i.e=
. use UDP
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 checksum, to reduce the chance that the encaps=
ulated packets to
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 be dropped.
>=20
>=20
>=20
>=20
>=20
> Yong, Crabber, Xu, Herbert=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 [Page 14]
> -------------------------------------------------------------------------=
-------
>=20
> Internet-Draft=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 GRE-in-UDP Encapsulation=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 March 2016
>=20
>=C2=A0 =C2=A0 =C2=A0 g. Any middlebox that allows the UDP zero-checksum mo=
de for IPv6
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 MUST comply with requirement 1 and 8-10 in Sec=
tion 5 of
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 [RFC6936].
>=20
>=C2=A0 =C2=A0 =C2=A0 h. Measures SHOULD be taken to prevent IPv6 traffic w=
ith zero UDP
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 checksums from "escaping" to the general Inter=
net; see Section
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 8 for examples of such measures.
>=20
>=C2=A0 =C2=A0 =C2=A0 i. IPv6 traffic with zero UDP checksums MUST be activ=
ely monitored
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 for errors by the network operator. For exampl=
e, the operator
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 may monitor Ethernet layer packet error rates.
>=20
>=C2=A0 =C2=A0 =C2=A0 j. If a packet with a non-zero checksum is received, =
the checksum
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 MUST be verified before accepting the packet. =
This is
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 regardless of whether the tunnel encapsulator =
and decapsulator
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 have been configured with UDP zero-checksum mo=
de.
>=20
>=C2=A0 =C2=A0 The above requirements do not change either the requirements
>=C2=A0 =C2=A0 specified in [RFC2460] as modified by [RFC6935] or the requi=
rements
>=C2=A0 =C2=A0 specified in [RFC6936].
>=20
>=C2=A0 =C2=A0 The requirement to check the source IPv6 address in addition=
 to the
>=C2=A0 =C2=A0 destination IPv6 address, plus the strong recommendation aga=
inst
>=C2=A0 =C2=A0 reuse of source IPv6 addresses among GRE-in-UDP tunnels coll=
ectively
>=C2=A0 =C2=A0 provide some mitigation for the absence of UDP checksum cove=
rage of
>=C2=A0 =C2=A0 the IPv6 header. A traffic-managed controlled environment th=
at
>=C2=A0 =C2=A0 satisfies at least one of three conditions listed above in t=
his
>=C2=A0 =C2=A0 section provides additional assurance.
>=20
>=C2=A0 =C2=A0 A GRE-in-UDP tunnel is suitable for transmission over lower =
layers
>=C2=A0 =C2=A0 in the traffic-managed controlled environments that are allo=
wed by
>=C2=A0 =C2=A0 the exceptions stated above and the rate of corruption of th=
e inner
>=C2=A0 =C2=A0 IP packet on such networks is not expected to increase by co=
mparison
>=C2=A0 =C2=A0 to GRE traffic that is not encapsulated in UDP.=C2=A0 For th=
ese reasons,
>=C2=A0 =C2=A0 GRE-in-UDP does not provide an additional integrity check ex=
cept
>=C2=A0 =C2=A0 when GRE checksum is used when UDP zero-checksum mode is use=
d with
>=C2=A0 =C2=A0 IPv6, and this design is in accordance with requirements 2, =
3 and 5
>=C2=A0 =C2=A0 specified in Section 5 of [RFC6936].
>=20
>=C2=A0 =C2=A0 Generic Router Encapsulation (GRE) does not accumulate incor=
rect
>=C2=A0 =C2=A0 state as a consequence of GRE header corruption. A corrupt G=
RE
>=C2=A0 =C2=A0 packet may result in either packet discard or forwarding of =
the
>=C2=A0 =C2=A0 packet without accumulation of GRE state. Active monitoring =
of GRE-
>=C2=A0 =C2=A0 in-UDP traffic for errors is REQUIRED as occurrence of error=
s will
>=C2=A0 =C2=A0 result in some accumulation of error information outside the
>=C2=A0 =C2=A0 protocol for operational and management purposes. This desig=
n is in
>=C2=A0 =C2=A0 accordance with requirement 4 specified in Section 5 of [RFC=
6936].
>=20
>=20
>=20
> Yong, Crabber, Xu, Herbert=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 [Page 15]
> -------------------------------------------------------------------------=
-------
>=20
> Internet-Draft=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 GRE-in-UDP Encapsulation=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 March 2016
>=20
>=C2=A0 =C2=A0 The remaining requirements specified in Section 5 of [RFC693=
6] are
>=C2=A0 =C2=A0 not applicable to GRE-in-UDP.=C2=A0 Requirements 6 and 7 do =
not apply
>=C2=A0 =C2=A0 because GRE does not include a control feedback mechanism.
>=C2=A0 =C2=A0 Requirements 8-10 are middlebox requirements that do not app=
ly to
>=C2=A0 =C2=A0 GRE-in-UDP tunnel endpoints (see Section 7.1 for further mid=
dlebox
>=C2=A0 =C2=A0 discussion).
>=20
>=C2=A0 =C2=A0 It is worth mentioning that the use of a zero UDP checksum s=
hould
>=C2=A0 =C2=A0 present the equivalent risk of undetected packet corruption =
when
>=C2=A0 =C2=A0 sending similar packet using GRE-in-IPv6 without UDP [RFC767=
6] and
>=C2=A0 =C2=A0 without GRE checksums.
>=20
>=C2=A0 =C2=A0 In summary, a TMCE GRE-in-UDP Tunnel is allowed to use UDP-z=
ero-
>=C2=A0 =C2=A0 checksum mode for IPv6 when the conditions and requirements =
stated
>=C2=A0 =C2=A0 above are met. Otherwise the UDP checksum need to be used fo=
r IPv6
>=C2=A0 =C2=A0 as specified in [RFC768] and [RFC2460]. Use of GRE checksum =
is
>=C2=A0 =C2=A0 RECOMMENED when the UDP checksum is not used.
> "
>=20
> In GUE, to support UDP-checksum-zero, it said
>=20
> " Therefore, when GUE is used over
>=C2=A0 =C2=A0 IPv6, either the UDP checksum must be enabled or the GUE hea=
der
>=C2=A0 =C2=A0 checksum must be used.=C2=A0 An encapsulator MAY set a zero =
UDP checksum
>=C2=A0 =C2=A0 for performance or implementation reasons, in which case the=
 GUE
>=C2=A0 =C2=A0 header checksum MUST be used or applicable requirements for =
using
>=C2=A0 =C2=A0 zero UDP checksums in [GREUDP] MUST be met. If the UDP check=
sum is
>=C2=A0 =C2=A0 enabled, then the GUE header checksum should not be used sin=
ce it is
>=C2=A0 =C2=A0 mostly redundant."
>=20
> It's easy for me to add the similar words to the IP-in-UDP draft like "th=
e
> applicable requirements for using zero UDP checksum in [GREUDP] MUST be
> met when zero UDP checksum is used by the tunnel ingress". However, the
> major goal for disabling the UDP checksum is to improve the performance.
> When GUE header checksum is used and/or the bunch of applicable
> requirements as described in GRE/UDP are verified, is the goal of improvi=
ng
> performance still achievable? If not, why not directly enable the UDP-che=
cksum
> instead?
>=20
> =C2=A0=C2=A0=C2=A0 - fragmentation support
>=20
> In GRE/UDP, it said
>=20
> " 4.1. MTU and Fragmentation
>=20
>=C2=A0 =C2=A0 Regarding packet fragmentation, an encapsulator/decapsulator=
 SHOULD
>=C2=A0 =C2=A0 be compliant with [RFC7588] and perform fragmentation before=
 the
>=C2=A0 =C2=A0 encapsulation. The size of fragments SHOULD be less or equal=
 to the
>=C2=A0 =C2=A0 PMTU associated with the path between the GRE ingress and th=
e GRE
>=C2=A0 =C2=A0 egress tunnel endpoints minus the GRE and UDP overhead ..."
>=20
> in GUE, it said
>=20
> " 4.9. MTU and fragmentation
>=20
>=C2=A0 =C2=A0 Standard conventions for handling of MTU (Maximum Transmissi=
on Unit)
>=C2=A0 =C2=A0 and fragmentation in conjunction with networking tunnels
>=C2=A0 =C2=A0 (encapsulation of layer 2 or layer 3 packets) should be foll=
owed.
>=C2=A0 =C2=A0 Details are described in MTU and Fragmentation Issues with I=
n-the-
>=C2=A0 =C2=A0 Network Tunneling [RFC4459]... "
>=20
> It seems that the only missing thing in the IP-in-UDP draft is to allow t=
he outer
> fragmentation. However, as it said in
> (https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02#page-13), " ..=
.IPsec
> performs only Outer Fragmentation; this distinguishes it from IP-in-IP, w=
hich
> performs only Inner Fragmentation. " Note that IP-in-IP is the dominant
> encapsulation choice within Softwires networks. In other words, performin=
g
> only inner fragmentation works very well in practice. Furthermore, the ou=
ter
> fragmentation issue (e.g., reassembly cost for the egress) would become e=
ven
> worse since the fragments of X-in-UDP packets are more likely to be forwa=
rded
> across different paths than those of X-in-IP and X-in-GRE packets. Hence,=
 I'm
> wondering whether it's worthwhile to support the outer fragmentation on U=
DP
> encapsulated packets which seems useless in practice.
>=20
> =C2=A0=C2=A0=C2=A0 - signalling support (e.g., to test whether a tunnel i=
s up or
> =C2=A0=C2=A0=C2=A0 to measure MTUs)
>=20
> I haven't found any description of this in both GRE/UDP and GUE. Did you?
>=20
> =C2=A0=C2=A0=C2=A0 - support for robust ID fields (related to fragmentati=
on,
> =C2=A0=C2=A0=C2=A0 e.g., to overcome the limits of IPv4 ID as per RFC 686=
4)
>=20
> I haven't found any description of this in both GRE/UDP and GUE. Did you?
>=20
> Xiaohu
>=20
> > It is not our obligation to find a way for your document to proceed -
> > that onus is on you.
> >
> > Joe

=20


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

<html xmlns=3D"http://www.w3.org/1999/xhtml" xmlns:v=3D"urn:schemas-microso=
ft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office"><head><!--[=
if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>=
96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]--></head><bo=
dy>
<style type=3D"text/css" scoped> blockquote, div.yahoo_quoted { margin-left=
: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex =
!important; background-color:white !important; } </style>
                Fragmentation should be strongly discouraged.<div><br></div=
><div>if you've designed a tunnelling solution and you have fragmentation h=
appening as a matter of course, you've designed it wrong.&nbsp;<br><br>Lloy=
d Wood<div>lloyd.wood@yahoo.co.uk</div><br><p class=3D"yahoo-quoted-begin" =
style=3D"font-size: 15px; color: #715FFA; padding-top: 15px; margin-top: 0"=
>On Friday, May 27, 2016, 8:10 PM, Xuxiaohu &lt;xuxiaohu@huawei.com&gt; wro=
te:</p><blockquote class=3D"iosymail"><div id=3D"msgSandbox_AMhLyAoAAG2BnV0=
gc2BwILcOkyXZc_TEXT" class=3D"msgSandbox" style=3D"padding: 1.5em 0.5em 0.5=
em 1.2em; word-wrap: break-word;">&lt;Note that I have changed the subject =
of the email hence it has nothing to do with the WG adoption call now. It's=
 just a discussion on a particular issue which is related to those WGs whic=
h are working on UDP tunnels. The reason for containing the old email is to=
 use it as a background which may be useful for better understanding of thi=
s particular issue&gt;<br><br>The possible side-effect of performing fragme=
ntation on UDP encapsulated packets is to worsen the reassembly burden on t=
unnel egress since fragments of UDP encapsulated packets are more likely to=
 be forwarded across different paths towards the tunnel egress than those o=
f IP or GRE encapsulated packets.<br><br>It seems that most X-over-UDP prop=
osals choose to prohibit the tunnel ingress from performing fragmentation o=
n UDP encapsulated packets. See the following quoted text regarding fragmen=
tation from those X-over-UDP drafts:<br><br>LISP:<br><br>When an ITR receiv=
es a packet from a site-facing interface and adds H<br>&nbsp;  octets worth=
 of encapsulation to yield a packet size greater than L<br>&nbsp;  octets, =
it resolves the MTU issue by first splitting the original<br>&nbsp;  packet=
 into 2 equal-sized fragments.&nbsp; A LISP header is then prepended<br>&nb=
sp;  to each fragment.<br><br>VXLAN:<br><br>VTEPs MUST NOT fragment VXLAN p=
ackets.&nbsp; Intermediate routers may<br>&nbsp;  fragment encapsulated VXL=
AN packets due to the larger frame size.<br>&nbsp;  The destination VTEP MA=
Y silently discard such VXLAN fragments.<br><br>VXLAN-GPE:<br><br>VTEPs MUS=
T never fragment an encapsulated VXLAN GPE packet, and when<br>&nbsp;  the =
outer IP header is IPv4, VTEPs MUST set the DF bit in the outer<br>&nbsp;  =
IPv4 header.<br><br>GEVENE:<br><br>&nbsp;  To prevent fragmentation and max=
imize performance, the best practice<br>&nbsp;  when using Geneve is to ens=
ure that the MTU of the physical network<br>&nbsp;  is greater than or equa=
l to the MTU of the encapsulated network plus<br>&nbsp;  tunnel headers.<br=
><br>GUE:<br><br>&nbsp; &nbsp; If a packet is fragmented before encapsulati=
on in GUE, all the<br>&nbsp; &nbsp; related fragments must be encapsulated =
using the same source port<br>&nbsp; &nbsp; (inner flow identifier). An ope=
rator may set MTU to account for<br>&nbsp; &nbsp; encapsulation overhead an=
d reduce the likelihood of fragmentation.<br><br>GRE/UDP<br><br>Regarding p=
acket fragmentation, an encapsulator/decapsulator SHOULD<br>&nbsp;  be comp=
liant with [RFC7588] and perform fragmentation before the<br>&nbsp;  encaps=
ulation.<br><br>However, the above choice seems conflict with the requireme=
nts as described in <a href=3D"https://tools.ietf.org/html/draft-ietf-intar=
ea-tunnels-02" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-int=
area-tunnels-02</a><br><br><br>I wonder whether the IETF should reach a con=
sensus on whether or not the fragmentation on UDP encapsulated packets shou=
ld be allowed.<br>&nbsp; <br>Best regards,<br>Xiaohu<br><br>&gt; -----Origi=
nal Message-----<br>&gt; From: Xuxiaohu<br>&gt; Sent: Thursday, May 26, 201=
6 4:35 PM<br>&gt; To: 'Joe Touch'; Fred Baker (fred); Wassim Haddad<br>&gt;=
 Cc: <a ymailto=3D"mailto:int-area@ietf.org" href=3D"javascript:return">int=
-area@ietf.org</a><br>&gt; Subject: RE: [Int-area] Call for adoption of dra=
ft-xu-intarea-ip-in-udp-03<br>&gt; <br>&gt; <br>&gt; <br>&gt; &gt; -----Ori=
ginal Message-----<br>&gt; &gt; From: Joe Touch [mailto:<a ymailto=3D"mailt=
o:touch@isi.edu" href=3D"javascript:return">touch@isi.edu</a>]<br>&gt; &gt;=
 Sent: Thursday, May 26, 2016 2:11 AM<br>&gt; &gt; To: Xuxiaohu; Fred Baker=
 (fred); Wassim Haddad<br>&gt; &gt; Cc: <a ymailto=3D"mailto:int-area@ietf.=
org" href=3D"javascript:return">int-area@ietf.org</a><br>&gt; &gt; Subject:=
 Re: [Int-area] Call for adoption of<br>&gt; &gt; draft-xu-intarea-ip-in-ud=
p-03<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt; On 5/24/2016 7:24 =
PM, Xuxiaohu wrote:<br>&gt; &gt; &gt; Hi Joe,<br>&gt; &gt; &gt;<br>&gt; &gt=
; &gt; I wonder whether you want to tell me the following truth by the<br>&=
gt; &gt; &gt; example that you gave: no matter whatever improvements we had=
 done<br>&gt; &gt; &gt; with this draft, those persons who dislike it by th=
e light of nature<br>&gt; &gt; &gt; would dislike it in the end.<br>&gt; &g=
t;<br>&gt; &gt; The only improvements that would make this doc useful would=
 be to add<br>&gt; &gt; capabilities already in GRE/UDP or GUE/UDP, which w=
e already have.<br>&gt; <br>&gt; Let's go over the four things you mentione=
d earlier in GRE/UDP and GUE/UDP:<br>&gt; <br>&gt; &nbsp;&nbsp;&nbsp; - str=
onger checksums<br>&gt; <br>&gt; In GRE/UDP, in order to use UDP-zero-check=
sum, it gave the following<br>&gt; restrictions:<br>&gt; " 6. UDP Checksum =
Handling<br>&gt; <br>&gt;&nbsp; &nbsp; 6.1. UDP Checksum with IPv4<br>&gt; =
<br>&gt;&nbsp; &nbsp; For UDP in IPv4, the UDP checksum MUST be processed a=
s specified in<br>&gt;&nbsp; &nbsp; [RFC768] and [RFC1122] for both transmi=
t and receive. The IPv4<br>&gt; <br>&gt; <br>&gt; <br>&gt; Yong, Crabber, X=
u, Herbert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [Page 12]<br>&=
gt; -----------------------------------------------------------------------=
---------<br>&gt; <br>&gt; Internet-Draft&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 GRE-in-UDP Encapsulation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  March 2=
016<br>&gt; <br>&gt;&nbsp; &nbsp; header includes a checksum which protects=
 against mis-delivery of<br>&gt;&nbsp; &nbsp; the packet due to corruption =
of IP addresses. The UDP checksum<br>&gt;&nbsp; &nbsp; potentially provides=
 protection against corruption of the UDP header,<br>&gt;&nbsp; &nbsp; GRE =
header, and GRE payload. Disabling the use of checksums is a<br>&gt;&nbsp; =
&nbsp; deployment consideration that should take into account the risk and<=
br>&gt;&nbsp; &nbsp; effects of packet corruption.<br>&gt; <br>&gt;&nbsp; &=
nbsp; When a decapsulator receives a packet, the UDP checksum field MUST<br=
>&gt;&nbsp; &nbsp; be processed. If the UDP checksum is non-zero, the decap=
sulator MUST<br>&gt;&nbsp; &nbsp; verify the checksum before accepting the =
packet. By default a<br>&gt;&nbsp; &nbsp; decapsulator SHOULD accept UDP pa=
ckets with a zero checksum. A node<br>&gt;&nbsp; &nbsp; MAY be configured t=
o disallow zero checksums per [RFC1122]; this may<br>&gt;&nbsp; &nbsp; be d=
one selectively, for instance disallowing zero checksums from<br>&gt;&nbsp;=
 &nbsp; certain hosts that are known to be sending over paths subject to<br=
>&gt;&nbsp; &nbsp; packet corruption. If verification of a non-zero checksu=
m fails, a<br>&gt;&nbsp; &nbsp; decapsulator lacks the capability to verify=
 a non-zero checksum, or<br>&gt;&nbsp; &nbsp; a packet with a zero-checksum=
 was received and the decapsulator is<br>&gt;&nbsp; &nbsp; configured to di=
sallow, the packet MUST be dropped and an event MAY<br>&gt;&nbsp; &nbsp; be=
 logged.<br>&gt; <br>&gt;&nbsp; &nbsp; 6.2. UDP Checksum with IPv6<br>&gt; =
<br>&gt;&nbsp; &nbsp; For UDP in IPv6, the UDP checksum MUST be processed a=
s specified in<br>&gt;&nbsp; &nbsp; [RFC768] and [RFC2460] for both transmi=
t and receive.<br>&gt; <br>&gt;&nbsp; &nbsp; When UDP is used over IPv6, th=
e UDP checksum is relied upon to<br>&gt;&nbsp; &nbsp; protect both the IPv6=
 and UDP headers from corruption. As such, A<br>&gt;&nbsp; &nbsp; default G=
RE-in-UDP Tunnel MUST perform UDP checksum; A TMCE GRE-in-<br>&gt;&nbsp; &n=
bsp; UDP Tunnel MAY be configured with the UDP zero-checksum mode if the<br=
>&gt;&nbsp; &nbsp; traffic-managed controlled environment or a set of close=
ly<br>&gt;&nbsp; &nbsp; cooperating traffic-managed controlled environments=
 (such as by<br>&gt;&nbsp; &nbsp; network operators who have agreed to work=
 together in order to<br>&gt;&nbsp; &nbsp; jointly provide specific service=
s) meet at least one of following<br>&gt;&nbsp; &nbsp; conditions:<br>&gt; =
<br>&gt;&nbsp; &nbsp; a. It is known (perhaps through knowledge of equipmen=
t types and<br>&gt;&nbsp; &nbsp; &nbsp;  lower layer checks) that packet co=
rruption is exceptionally<br>&gt;&nbsp; &nbsp; &nbsp;  unlikely and where t=
he operator is willing to take the risk of<br>&gt;&nbsp; &nbsp; &nbsp;  und=
etected packet corruption.<br>&gt; <br>&gt;&nbsp; &nbsp; b. It is judged th=
rough observational measurements (perhaps of<br>&gt;&nbsp; &nbsp; &nbsp;  h=
istoric or current traffic flows that use a non-zero checksum)<br>&gt;&nbsp=
; &nbsp; &nbsp;  that the level of packet corruption is tolerably low and w=
here<br>&gt;&nbsp; &nbsp; &nbsp;  the operator is willing to take the risk =
of undetected packet<br>&gt;&nbsp; &nbsp; &nbsp;  corruption.<br>&gt; <br>&=
gt; <br>&gt; <br>&gt; <br>&gt; <br>&gt; Yong, Crabber, Xu, Herbert&nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [Page 13]<br>&gt; ---------------=
-----------------------------------------------------------------<br>&gt; <=
br>&gt; Internet-Draft&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GRE-in-UDP Encapsu=
lation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  March 2016<br>&gt; <br>&gt=
;&nbsp; &nbsp; c. Carrying applications that are tolerant of mis-delivered =
or<br>&gt;&nbsp; &nbsp; &nbsp;  corrupted packets (perhaps through higher l=
ayer checksum,<br>&gt;&nbsp; &nbsp; &nbsp;  validation, and retransmission =
or transmission redundancy) where<br>&gt;&nbsp; &nbsp; &nbsp;  the operator=
 is willing to rely on the applications using the<br>&gt;&nbsp; &nbsp; &nbs=
p;  tunnel to survive any corrupt packets.<br>&gt; <br>&gt;&nbsp; &nbsp; Th=
e following requirements apply to a TMCE GRE-in-UDP tunnel that<br>&gt;&nbs=
p; &nbsp; use UDP zero-checksum mode:<br>&gt; <br>&gt;&nbsp; &nbsp; &nbsp; =
a. Use of the UDP checksum with IPv6 MUST be the default<br>&gt;&nbsp; &nbs=
p; &nbsp; &nbsp;  configuration of all GRE-in-UDP tunnels.<br>&gt; <br>&gt;=
&nbsp; &nbsp; &nbsp; b. The GRE-in-UDP tunnel implementation MUST comply wi=
th all<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  requirements specified in Sectio=
n 4 of [RFC6936] and with<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  requirement 1=
 specified in Section 5 of [RFC6936].<br>&gt; <br>&gt;&nbsp; &nbsp; &nbsp; =
c. The tunnel decapsulator SHOULD only allow the use of UDP zero-<br>&gt;&n=
bsp; &nbsp; &nbsp; &nbsp;  checksum mode for IPv6 on a single received UDP =
Destination<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  Port regardless of the enca=
psulator. The motivation for this<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  requi=
rement is possible corruption of the UDP Destination Port,<br>&gt;&nbsp; &n=
bsp; &nbsp; &nbsp;  which may cause packet delivery to the wrong UDP port. =
If that<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  other UDP port requires the UDP=
 checksum, the mis-delivered<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  packet wil=
l be discarded.<br>&gt; <br>&gt;&nbsp; &nbsp; &nbsp; d. It is RECOMMENDED t=
hat the UDP zero-checksum mode for IPv6 is<br>&gt;&nbsp; &nbsp; &nbsp; &nbs=
p;  only enabled for certain selected source addresses. The tunnel<br>&gt;&=
nbsp; &nbsp; &nbsp; &nbsp;  decapsulator MUST check that the source and des=
tination IPv6<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  addresses are valid for t=
he GRE-in-UDP tunnel on which the<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  packe=
t was received if that tunnel uses UDP zero-checksum mode<br>&gt;&nbsp; &nb=
sp; &nbsp; &nbsp;  and discard any packet for which this check fails.<br>&g=
t; <br>&gt;&nbsp; &nbsp; &nbsp; e. The tunnel encapsulator SHOULD use diffe=
rent IPv6 addresses for<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  each GRE-in-UDP=
 tunnel that uses UDP zero-checksum mode<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;=
  regardless of the decapsulator in order to strengthen the<br>&gt;&nbsp; &=
nbsp; &nbsp; &nbsp;  decapsulator's check of the IPv6 source address (i.e.,=
 the same<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  IPv6 source address SHOULD NO=
T be used with more than one IPv6<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  desti=
nation address, independent of whether that destination<br>&gt;&nbsp; &nbsp=
; &nbsp; &nbsp;  address is a unicast or multicast address). When this is n=
ot<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  possible, it is RECOMMENDED to use e=
ach source IPv6 address for<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  as few UDP =
zero-checksum mode GRE-in-UDP tunnels as is feasible.<br>&gt; <br>&gt;&nbsp=
; &nbsp; &nbsp; f. When any middlebox exists on the path of a GRE-in-UDP tu=
nnel,<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  it is RECOMMENDED to use the defa=
ult mode, i.e. use UDP<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  checksum, to red=
uce the chance that the encapsulated packets to<br>&gt;&nbsp; &nbsp; &nbsp;=
 &nbsp;  be dropped.<br>&gt; <br>&gt; <br>&gt; <br>&gt; <br>&gt; <br>&gt; Y=
ong, Crabber, Xu, Herbert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 [Page 14]<br>&gt; --------------------------------------------------------=
------------------------<br>&gt; <br>&gt; Internet-Draft&nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; GRE-in-UDP Encapsulation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;  March 2016<br>&gt; <br>&gt;&nbsp; &nbsp; &nbsp; g. Any middlebox th=
at allows the UDP zero-checksum mode for IPv6<br>&gt;&nbsp; &nbsp; &nbsp; &=
nbsp;  MUST comply with requirement 1 and 8-10 in Section 5 of<br>&gt;&nbsp=
; &nbsp; &nbsp; &nbsp;  [RFC6936].<br>&gt; <br>&gt;&nbsp; &nbsp; &nbsp; h. =
Measures SHOULD be taken to prevent IPv6 traffic with zero UDP<br>&gt;&nbsp=
; &nbsp; &nbsp; &nbsp;  checksums from "escaping" to the general Internet; =
see Section<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  8 for examples of such meas=
ures.<br>&gt; <br>&gt;&nbsp; &nbsp; &nbsp; i. IPv6 traffic with zero UDP ch=
ecksums MUST be actively monitored<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  for =
errors by the network operator. For example, the operator<br>&gt;&nbsp; &nb=
sp; &nbsp; &nbsp;  may monitor Ethernet layer packet error rates.<br>&gt; <=
br>&gt;&nbsp; &nbsp; &nbsp; j. If a packet with a non-zero checksum is rece=
ived, the checksum<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  MUST be verified bef=
ore accepting the packet. This is<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp;  regar=
dless of whether the tunnel encapsulator and decapsulator<br>&gt;&nbsp; &nb=
sp; &nbsp; &nbsp;  have been configured with UDP zero-checksum mode.<br>&gt=
; <br>&gt;&nbsp; &nbsp; The above requirements do not change either the req=
uirements<br>&gt;&nbsp; &nbsp; specified in [RFC2460] as modified by [RFC69=
35] or the requirements<br>&gt;&nbsp; &nbsp; specified in [RFC6936].<br>&gt=
; <br>&gt;&nbsp; &nbsp; The requirement to check the source IPv6 address in=
 addition to the<br>&gt;&nbsp; &nbsp; destination IPv6 address, plus the st=
rong recommendation against<br>&gt;&nbsp; &nbsp; reuse of source IPv6 addre=
sses among GRE-in-UDP tunnels collectively<br>&gt;&nbsp; &nbsp; provide som=
e mitigation for the absence of UDP checksum coverage of<br>&gt;&nbsp; &nbs=
p; the IPv6 header. A traffic-managed controlled environment that<br>&gt;&n=
bsp; &nbsp; satisfies at least one of three conditions listed above in this=
<br>&gt;&nbsp; &nbsp; section provides additional assurance.<br>&gt; <br>&g=
t;&nbsp; &nbsp; A GRE-in-UDP tunnel is suitable for transmission over lower=
 layers<br>&gt;&nbsp; &nbsp; in the traffic-managed controlled environments=
 that are allowed by<br>&gt;&nbsp; &nbsp; the exceptions stated above and t=
he rate of corruption of the inner<br>&gt;&nbsp; &nbsp; IP packet on such n=
etworks is not expected to increase by comparison<br>&gt;&nbsp; &nbsp; to G=
RE traffic that is not encapsulated in UDP.&nbsp; For these reasons,<br>&gt=
;&nbsp; &nbsp; GRE-in-UDP does not provide an additional integrity check ex=
cept<br>&gt;&nbsp; &nbsp; when GRE checksum is used when UDP zero-checksum =
mode is used with<br>&gt;&nbsp; &nbsp; IPv6, and this design is in accordan=
ce with requirements 2, 3 and 5<br>&gt;&nbsp; &nbsp; specified in Section 5=
 of [RFC6936].<br>&gt; <br>&gt;&nbsp; &nbsp; Generic Router Encapsulation (=
GRE) does not accumulate incorrect<br>&gt;&nbsp; &nbsp; state as a conseque=
nce of GRE header corruption. A corrupt GRE<br>&gt;&nbsp; &nbsp; packet may=
 result in either packet discard or forwarding of the<br>&gt;&nbsp; &nbsp; =
packet without accumulation of GRE state. Active monitoring of GRE-<br>&gt;=
&nbsp; &nbsp; in-UDP traffic for errors is REQUIRED as occurrence of errors=
 will<br>&gt;&nbsp; &nbsp; result in some accumulation of error information=
 outside the<br>&gt;&nbsp; &nbsp; protocol for operational and management p=
urposes. This design is in<br>&gt;&nbsp; &nbsp; accordance with requirement=
 4 specified in Section 5 of [RFC6936].<br>&gt; <br>&gt; <br>&gt; <br>&gt; =
Yong, Crabber, Xu, Herbert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; [Page 15]<br>&gt; -------------------------------------------------------=
-------------------------<br>&gt; <br>&gt; Internet-Draft&nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; GRE-in-UDP Encapsulation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;  March 2016<br>&gt; <br>&gt;&nbsp; &nbsp; The remaining requirement=
s specified in Section 5 of [RFC6936] are<br>&gt;&nbsp; &nbsp; not applicab=
le to GRE-in-UDP.&nbsp; Requirements 6 and 7 do not apply<br>&gt;&nbsp; &nb=
sp; because GRE does not include a control feedback mechanism.<br>&gt;&nbsp=
; &nbsp; Requirements 8-10 are middlebox requirements that do not apply to<=
br>&gt;&nbsp; &nbsp; GRE-in-UDP tunnel endpoints (see Section 7.1 for furth=
er middlebox<br>&gt;&nbsp; &nbsp; discussion).<br>&gt; <br>&gt;&nbsp; &nbsp=
; It is worth mentioning that the use of a zero UDP checksum should<br>&gt;=
&nbsp; &nbsp; present the equivalent risk of undetected packet corruption w=
hen<br>&gt;&nbsp; &nbsp; sending similar packet using GRE-in-IPv6 without U=
DP [RFC7676] and<br>&gt;&nbsp; &nbsp; without GRE checksums.<br>&gt; <br>&g=
t;&nbsp; &nbsp; In summary, a TMCE GRE-in-UDP Tunnel is allowed to use UDP-=
zero-<br>&gt;&nbsp; &nbsp; checksum mode for IPv6 when the conditions and r=
equirements stated<br>&gt;&nbsp; &nbsp; above are met. Otherwise the UDP ch=
ecksum need to be used for IPv6<br>&gt;&nbsp; &nbsp; as specified in [RFC76=
8] and [RFC2460]. Use of GRE checksum is<br>&gt;&nbsp; &nbsp; RECOMMENED wh=
en the UDP checksum is not used.<br>&gt; "<br>&gt; <br>&gt; In GUE, to supp=
ort UDP-checksum-zero, it said<br>&gt; <br>&gt; " Therefore, when GUE is us=
ed over<br>&gt;&nbsp; &nbsp;  IPv6, either the UDP checksum must be enabled=
 or the GUE header<br>&gt;&nbsp; &nbsp;  checksum must be used.&nbsp; An en=
capsulator MAY set a zero UDP checksum<br>&gt;&nbsp; &nbsp;  for performanc=
e or implementation reasons, in which case the GUE<br>&gt;&nbsp; &nbsp;  he=
ader checksum MUST be used or applicable requirements for using<br>&gt;&nbs=
p; &nbsp;  zero UDP checksums in [GREUDP] MUST be met. If the UDP checksum =
is<br>&gt;&nbsp; &nbsp;  enabled, then the GUE header checksum should not b=
e used since it is<br>&gt;&nbsp; &nbsp;  mostly redundant."<br>&gt; <br>&gt=
; It's easy for me to add the similar words to the IP-in-UDP draft like "th=
e<br>&gt; applicable requirements for using zero UDP checksum in [GREUDP] M=
UST be<br>&gt; met when zero UDP checksum is used by the tunnel ingress". H=
owever, the<br>&gt; major goal for disabling the UDP checksum is to improve=
 the performance.<br>&gt; When GUE header checksum is used and/or the bunch=
 of applicable<br>&gt; requirements as described in GRE/UDP are verified, i=
s the goal of improving<br>&gt; performance still achievable? If not, why n=
ot directly enable the UDP-checksum<br>&gt; instead?<br>&gt; <br>&gt; &nbsp=
;&nbsp;&nbsp; - fragmentation support<br>&gt; <br>&gt; In GRE/UDP, it said<=
br>&gt; <br>&gt; " 4.1. MTU and Fragmentation<br>&gt; <br>&gt;&nbsp; &nbsp;=
 Regarding packet fragmentation, an encapsulator/decapsulator SHOULD<br>&gt=
;&nbsp; &nbsp; be compliant with [RFC7588] and perform fragmentation before=
 the<br>&gt;&nbsp; &nbsp; encapsulation. The size of fragments SHOULD be le=
ss or equal to the<br>&gt;&nbsp; &nbsp; PMTU associated with the path betwe=
en the GRE ingress and the GRE<br>&gt;&nbsp; &nbsp; egress tunnel endpoints=
 minus the GRE and UDP overhead ..."<br>&gt; <br>&gt; in GUE, it said<br>&g=
t; <br>&gt; " 4.9. MTU and fragmentation<br>&gt; <br>&gt;&nbsp; &nbsp;  Sta=
ndard conventions for handling of MTU (Maximum Transmission Unit)<br>&gt;&n=
bsp; &nbsp;  and fragmentation in conjunction with networking tunnels<br>&g=
t;&nbsp; &nbsp;  (encapsulation of layer 2 or layer 3 packets) should be fo=
llowed.<br>&gt;&nbsp; &nbsp;  Details are described in MTU and Fragmentatio=
n Issues with In-the-<br>&gt;&nbsp; &nbsp;  Network Tunneling [RFC4459]... =
"<br>&gt; <br>&gt; It seems that the only missing thing in the IP-in-UDP dr=
aft is to allow the outer<br>&gt; fragmentation. However, as it said in<br>=
&gt; (<a href=3D"https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02#=
page-13" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-intarea-t=
unnels-02#page-13</a>), " ...IPsec<br>&gt; performs only Outer Fragmentatio=
n; this distinguishes it from IP-in-IP, which<br>&gt; performs only Inner F=
ragmentation. " Note that IP-in-IP is the dominant<br>&gt; encapsulation ch=
oice within Softwires networks. In other words, performing<br>&gt; only inn=
er fragmentation works very well in practice. Furthermore, the outer<br>&gt=
; fragmentation issue (e.g., reassembly cost for the egress) would become e=
ven<br>&gt; worse since the fragments of X-in-UDP packets are more likely t=
o be forwarded<br>&gt; across different paths than those of X-in-IP and X-i=
n-GRE packets. Hence, I'm<br>&gt; wondering whether it's worthwhile to supp=
ort the outer fragmentation on UDP<br>&gt; encapsulated packets which seems=
 useless in practice.<br>&gt; <br>&gt; &nbsp;&nbsp;&nbsp; - signalling supp=
ort (e.g., to test whether a tunnel is up or<br>&gt; &nbsp;&nbsp;&nbsp; to =
measure MTUs)<br>&gt; <br>&gt; I haven't found any description of this in b=
oth GRE/UDP and GUE. Did you?<br>&gt; <br>&gt; &nbsp;&nbsp;&nbsp; - support=
 for robust ID fields (related to fragmentation,<br>&gt; &nbsp;&nbsp;&nbsp;=
 e.g., to overcome the limits of IPv4 ID as per RFC 6864)<br>&gt; <br>&gt; =
I haven't found any description of this in both GRE/UDP and GUE. Did you?<b=
r>&gt; <br>&gt; Xiaohu<br>&gt; <br>&gt; &gt; It is not our obligation to fi=
nd a way for your document to proceed -<br>&gt; &gt; that onus is on you.<b=
r>&gt; &gt;<br>&gt; &gt; Joe<br></div><blockquote>
            </blockquote></blockquote></div>
</body></html>
------=_Part_2492240_1136524516.1465708308517--


From nobody Wed Jun 15 14:00:50 2016
Return-Path: <sadikshi@cisco.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A822A128E19; Sat, 11 Jun 2016 23:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level: 
X-Spam-Status: No, score=-15.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 ymAnrPgA0aM5; Sat, 11 Jun 2016 23:25:51 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0CF812B032; Sat, 11 Jun 2016 23:25:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=45990; q=dns/txt; s=iport; t=1465712751; x=1466922351; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=di5l6+f5gqYQnykPUrLFrCOeeS4V5drp4Rpky/CeWbE=; b=Nt032ABlguuXJ+iCqgw6OZcGxbbfgfaViDfqDPki4h7zo99tBKjFhlmV lM8aKpQZj1JTZEH4mV2kirgwPhlAt+smLbvSv2RbhDWYuEf802zUNBKdr 8GsPeEmWujQVRK0dYiWzHvVTqZfGvqSRjZMI7v0noknJeGwJmI+Of20j2 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AQAgDh/lxX/4QNJK1dgnBOVn0Grx2MA?= =?us-ascii?q?IF5IoV1AoEhOBQBAQEBAQEBZSeESgEBAQMBGgECEFEHBAIBCBEDAQEBARULAQY?= =?us-ascii?q?HMhQJCAIEARIbh3sDDwgOvSgBAQEBAQEBAQEBAQEBAQEBAQEBAQEXAQQLhhyDS?= =?us-ascii?q?oEDgkOBTxEBIwcSGAeFHAWGRQyBO5AhNAGGA4J4gziBdI8giAGHbAEeNoIHHBa?= =?us-ascii?q?BNW6IRg0XBxh/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,460,1459814400";  d="scan'208,217";a="283770831"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Jun 2016 06:25:48 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u5C6PmSk000872 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 12 Jun 2016 06:25:48 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sun, 12 Jun 2016 01:25:47 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1104.009; Sun, 12 Jun 2016 01:25:47 -0500
From: "Saumya Dikshit (sadikshi)" <sadikshi@cisco.com>
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>, Softwires WG <softwires@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Xuxiaohu <xuxiaohu@huawei.com>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [nvo3] [tsvwg] Is it feasible to perform fragmentation on UDP encapsulated packets.
Thread-Index: AQHRxHNBx0FCT/ugokeOCF2M3CVw6A==
Date: Sun, 12 Jun 2016 06:25:47 +0000
Message-ID: <D382FCD5.6783C%sadikshi@cisco.com>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.85.139]
Content-Type: multipart/alternative; boundary="_000_D382FCD56783Csadikshiciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/Yw14ktlf0SqHdwdnd1d0pSLBYm0>
X-Mailman-Approved-At: Wed, 15 Jun 2016 14:00:44 -0700
Subject: Re: [Softwires] [nvo3] [tsvwg] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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, 12 Jun 2016 06:25:55 -0000

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

In case of typical datacenter brownfield deployments,
the underlay and overlay may be completely disconnected operationally,
hence there can be cases where the mtu mismatch in underlay network may not
be notified to overlay endpoints and subsequently to end hosts.

From: Lloyd Wood <lloyd.wood@yahoo.co.uk<mailto:lloyd.wood@yahoo.co.uk>>
Date: Sunday, June 12, 2016 at 10:41 AM
To: Softwires WG <softwires@ietf.org<mailto:softwires@ietf.org>>, "int-area=
@ietf.org<mailto:int-area@ietf.org>" <int-area@ietf.org<mailto:int-area@iet=
f.org>>, "lisp@ietf.org<mailto:lisp@ietf.org>" <lisp@ietf.org<mailto:lisp@i=
etf.org>>, "tsvwg@ietf.org<mailto:tsvwg@ietf.org>" <tsvwg@ietf.org<mailto:t=
svwg@ietf.org>>, Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>=
, "nvo3@ietf.org<mailto:nvo3@ietf.org>" <nvo3@ietf.org<mailto:nvo3@ietf.org=
>>
Subject: Re: [nvo3] [tsvwg] Is it feasible to perform fragmentation on UDP =
encapsulated packets.

Fragmentation should be strongly discouraged.

if you've designed a tunnelling solution and you have fragmentation happeni=
ng as a matter of course, you've designed it wrong.

Lloyd Wood
lloyd.wood@yahoo.co.uk<mailto:lloyd.wood@yahoo.co.uk>


On Friday, May 27, 2016, 8:10 PM, Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxi=
aohu@huawei.com>> wrote:

<Note that I have changed the subject of the email hence it has nothing to =
do with the WG adoption call now. It's just a discussion on a particular is=
sue which is related to those WGs which are working on UDP tunnels. The rea=
son for containing the old email is to use it as a background which may be =
useful for better understanding of this particular issue>

The possible side-effect of performing fragmentation on UDP encapsulated pa=
ckets is to worsen the reassembly burden on tunnel egress since fragments o=
f UDP encapsulated packets are more likely to be forwarded across different=
 paths towards the tunnel egress than those of IP or GRE encapsulated packe=
ts.

It seems that most X-over-UDP proposals choose to prohibit the tunnel ingre=
ss from performing fragmentation on UDP encapsulated packets. See the follo=
wing quoted text regarding fragmentation from those X-over-UDP drafts:

LISP:

When an ITR receives a packet from a site-facing interface and adds H
  octets worth of encapsulation to yield a packet size greater than L
  octets, it resolves the MTU issue by first splitting the original
  packet into 2 equal-sized fragments.  A LISP header is then prepended
  to each fragment.

VXLAN:

VTEPs MUST NOT fragment VXLAN packets.  Intermediate routers may
  fragment encapsulated VXLAN packets due to the larger frame size.
  The destination VTEP MAY silently discard such VXLAN fragments.

VXLAN-GPE:

VTEPs MUST never fragment an encapsulated VXLAN GPE packet, and when
  the outer IP header is IPv4, VTEPs MUST set the DF bit in the outer
  IPv4 header.

GEVENE:

  To prevent fragmentation and maximize performance, the best practice
  when using Geneve is to ensure that the MTU of the physical network
  is greater than or equal to the MTU of the encapsulated network plus
  tunnel headers.

GUE:

    If a packet is fragmented before encapsulation in GUE, all the
    related fragments must be encapsulated using the same source port
    (inner flow identifier). An operator may set MTU to account for
    encapsulation overhead and reduce the likelihood of fragmentation.

GRE/UDP

Regarding packet fragmentation, an encapsulator/decapsulator SHOULD
  be compliant with [RFC7588] and perform fragmentation before the
  encapsulation.

However, the above choice seems conflict with the requirements as described=
 in https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02


I wonder whether the IETF should reach a consensus on whether or not the fr=
agmentation on UDP encapsulated packets should be allowed.

Best regards,
Xiaohu

> -----Original Message-----
> From: Xuxiaohu
> Sent: Thursday, May 26, 2016 4:35 PM
> To: 'Joe Touch'; Fred Baker (fred); Wassim Haddad
> Cc: int-area@ietf.org<javascript:return>
> Subject: RE: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-0=
3
>
>
>
> > -----Original Message-----
> > From: Joe Touch [mailto:touch@isi.edu<javascript:return>]
> > Sent: Thursday, May 26, 2016 2:11 AM
> > To: Xuxiaohu; Fred Baker (fred); Wassim Haddad
> > Cc: int-area@ietf.org<javascript:return>
> > Subject: Re: [Int-area] Call for adoption of
> > draft-xu-intarea-ip-in-udp-03
> >
> >
> >
> > On 5/24/2016 7:24 PM, Xuxiaohu wrote:
> > > Hi Joe,
> > >
> > > I wonder whether you want to tell me the following truth by the
> > > example that you gave: no matter whatever improvements we had done
> > > with this draft, those persons who dislike it by the light of nature
> > > would dislike it in the end.
> >
> > The only improvements that would make this doc useful would be to add
> > capabilities already in GRE/UDP or GUE/UDP, which we already have.
>
> Let's go over the four things you mentioned earlier in GRE/UDP and GUE/UD=
P:
>
>     - stronger checksums
>
> In GRE/UDP, in order to use UDP-zero-checksum, it gave the following
> restrictions:
> " 6. UDP Checksum Handling
>
>    6.1. UDP Checksum with IPv4
>
>    For UDP in IPv4, the UDP checksum MUST be processed as specified in
>    [RFC768] and [RFC1122] for both transmit and receive. The IPv4
>
>
>
> Yong, Crabber, Xu, Herbert                                    [Page 12]
> -------------------------------------------------------------------------=
-------
>
> Internet-Draft          GRE-in-UDP Encapsulation            March 2016
>
>    header includes a checksum which protects against mis-delivery of
>    the packet due to corruption of IP addresses. The UDP checksum
>    potentially provides protection against corruption of the UDP header,
>    GRE header, and GRE payload. Disabling the use of checksums is a
>    deployment consideration that should take into account the risk and
>    effects of packet corruption.
>
>    When a decapsulator receives a packet, the UDP checksum field MUST
>    be processed. If the UDP checksum is non-zero, the decapsulator MUST
>    verify the checksum before accepting the packet. By default a
>    decapsulator SHOULD accept UDP packets with a zero checksum. A node
>    MAY be configured to disallow zero checksums per [RFC1122]; this may
>    be done selectively, for instance disallowing zero checksums from
>    certain hosts that are known to be sending over paths subject to
>    packet corruption. If verification of a non-zero checksum fails, a
>    decapsulator lacks the capability to verify a non-zero checksum, or
>    a packet with a zero-checksum was received and the decapsulator is
>    configured to disallow, the packet MUST be dropped and an event MAY
>    be logged.
>
>    6.2. UDP Checksum with IPv6
>
>    For UDP in IPv6, the UDP checksum MUST be processed as specified in
>    [RFC768] and [RFC2460] for both transmit and receive.
>
>    When UDP is used over IPv6, the UDP checksum is relied upon to
>    protect both the IPv6 and UDP headers from corruption. As such, A
>    default GRE-in-UDP Tunnel MUST perform UDP checksum; A TMCE GRE-in-
>    UDP Tunnel MAY be configured with the UDP zero-checksum mode if the
>    traffic-managed controlled environment or a set of closely
>    cooperating traffic-managed controlled environments (such as by
>    network operators who have agreed to work together in order to
>    jointly provide specific services) meet at least one of following
>    conditions:
>
>    a. It is known (perhaps through knowledge of equipment types and
>      lower layer checks) that packet corruption is exceptionally
>      unlikely and where the operator is willing to take the risk of
>      undetected packet corruption.
>
>    b. It is judged through observational measurements (perhaps of
>      historic or current traffic flows that use a non-zero checksum)
>      that the level of packet corruption is tolerably low and where
>      the operator is willing to take the risk of undetected packet
>      corruption.
>
>
>
>
>
> Yong, Crabber, Xu, Herbert                                    [Page 13]
> -------------------------------------------------------------------------=
-------
>
> Internet-Draft          GRE-in-UDP Encapsulation            March 2016
>
>    c. Carrying applications that are tolerant of mis-delivered or
>      corrupted packets (perhaps through higher layer checksum,
>      validation, and retransmission or transmission redundancy) where
>      the operator is willing to rely on the applications using the
>      tunnel to survive any corrupt packets.
>
>    The following requirements apply to a TMCE GRE-in-UDP tunnel that
>    use UDP zero-checksum mode:
>
>      a. Use of the UDP checksum with IPv6 MUST be the default
>        configuration of all GRE-in-UDP tunnels.
>
>      b. The GRE-in-UDP tunnel implementation MUST comply with all
>        requirements specified in Section 4 of [RFC6936] and with
>        requirement 1 specified in Section 5 of [RFC6936].
>
>      c. The tunnel decapsulator SHOULD only allow the use of UDP zero-
>        checksum mode for IPv6 on a single received UDP Destination
>        Port regardless of the encapsulator. The motivation for this
>        requirement is possible corruption of the UDP Destination Port,
>        which may cause packet delivery to the wrong UDP port. If that
>        other UDP port requires the UDP checksum, the mis-delivered
>        packet will be discarded.
>
>      d. It is RECOMMENDED that the UDP zero-checksum mode for IPv6 is
>        only enabled for certain selected source addresses. The tunnel
>        decapsulator MUST check that the source and destination IPv6
>        addresses are valid for the GRE-in-UDP tunnel on which the
>        packet was received if that tunnel uses UDP zero-checksum mode
>        and discard any packet for which this check fails.
>
>      e. The tunnel encapsulator SHOULD use different IPv6 addresses for
>        each GRE-in-UDP tunnel that uses UDP zero-checksum mode
>        regardless of the decapsulator in order to strengthen the
>        decapsulator's check of the IPv6 source address (i.e., the same
>        IPv6 source address SHOULD NOT be used with more than one IPv6
>        destination address, independent of whether that destination
>        address is a unicast or multicast address). When this is not
>        possible, it is RECOMMENDED to use each source IPv6 address for
>        as few UDP zero-checksum mode GRE-in-UDP tunnels as is feasible.
>
>      f. When any middlebox exists on the path of a GRE-in-UDP tunnel,
>        it is RECOMMENDED to use the default mode, i.e. use UDP
>        checksum, to reduce the chance that the encapsulated packets to
>        be dropped.
>
>
>
>
>
> Yong, Crabber, Xu, Herbert                                    [Page 14]
> -------------------------------------------------------------------------=
-------
>
> Internet-Draft          GRE-in-UDP Encapsulation            March 2016
>
>      g. Any middlebox that allows the UDP zero-checksum mode for IPv6
>        MUST comply with requirement 1 and 8-10 in Section 5 of
>        [RFC6936].
>
>      h. Measures SHOULD be taken to prevent IPv6 traffic with zero UDP
>        checksums from "escaping" to the general Internet; see Section
>        8 for examples of such measures.
>
>      i. IPv6 traffic with zero UDP checksums MUST be actively monitored
>        for errors by the network operator. For example, the operator
>        may monitor Ethernet layer packet error rates.
>
>      j. If a packet with a non-zero checksum is received, the checksum
>        MUST be verified before accepting the packet. This is
>        regardless of whether the tunnel encapsulator and decapsulator
>        have been configured with UDP zero-checksum mode.
>
>    The above requirements do not change either the requirements
>    specified in [RFC2460] as modified by [RFC6935] or the requirements
>    specified in [RFC6936].
>
>    The requirement to check the source IPv6 address in addition to the
>    destination IPv6 address, plus the strong recommendation against
>    reuse of source IPv6 addresses among GRE-in-UDP tunnels collectively
>    provide some mitigation for the absence of UDP checksum coverage of
>    the IPv6 header. A traffic-managed controlled environment that
>    satisfies at least one of three conditions listed above in this
>    section provides additional assurance.
>
>    A GRE-in-UDP tunnel is suitable for transmission over lower layers
>    in the traffic-managed controlled environments that are allowed by
>    the exceptions stated above and the rate of corruption of the inner
>    IP packet on such networks is not expected to increase by comparison
>    to GRE traffic that is not encapsulated in UDP.  For these reasons,
>    GRE-in-UDP does not provide an additional integrity check except
>    when GRE checksum is used when UDP zero-checksum mode is used with
>    IPv6, and this design is in accordance with requirements 2, 3 and 5
>    specified in Section 5 of [RFC6936].
>
>    Generic Router Encapsulation (GRE) does not accumulate incorrect
>    state as a consequence of GRE header corruption. A corrupt GRE
>    packet may result in either packet discard or forwarding of the
>    packet without accumulation of GRE state. Active monitoring of GRE-
>    in-UDP traffic for errors is REQUIRED as occurrence of errors will
>    result in some accumulation of error information outside the
>    protocol for operational and management purposes. This design is in
>    accordance with requirement 4 specified in Section 5 of [RFC6936].
>
>
>
> Yong, Crabber, Xu, Herbert                                    [Page 15]
> -------------------------------------------------------------------------=
-------
>
> Internet-Draft          GRE-in-UDP Encapsulation            March 2016
>
>    The remaining requirements specified in Section 5 of [RFC6936] are
>    not applicable to GRE-in-UDP.  Requirements 6 and 7 do not apply
>    because GRE does not include a control feedback mechanism.
>    Requirements 8-10 are middlebox requirements that do not apply to
>    GRE-in-UDP tunnel endpoints (see Section 7.1 for further middlebox
>    discussion).
>
>    It is worth mentioning that the use of a zero UDP checksum should
>    present the equivalent risk of undetected packet corruption when
>    sending similar packet using GRE-in-IPv6 without UDP [RFC7676] and
>    without GRE checksums.
>
>    In summary, a TMCE GRE-in-UDP Tunnel is allowed to use UDP-zero-
>    checksum mode for IPv6 when the conditions and requirements stated
>    above are met. Otherwise the UDP checksum need to be used for IPv6
>    as specified in [RFC768] and [RFC2460]. Use of GRE checksum is
>    RECOMMENED when the UDP checksum is not used.
> "
>
> In GUE, to support UDP-checksum-zero, it said
>
> " Therefore, when GUE is used over
>    IPv6, either the UDP checksum must be enabled or the GUE header
>    checksum must be used.  An encapsulator MAY set a zero UDP checksum
>    for performance or implementation reasons, in which case the GUE
>    header checksum MUST be used or applicable requirements for using
>    zero UDP checksums in [GREUDP] MUST be met. If the UDP checksum is
>    enabled, then the GUE header checksum should not be used since it is
>    mostly redundant."
>
> It's easy for me to add the similar words to the IP-in-UDP draft like "th=
e
> applicable requirements for using zero UDP checksum in [GREUDP] MUST be
> met when zero UDP checksum is used by the tunnel ingress". However, the
> major goal for disabling the UDP checksum is to improve the performance.
> When GUE header checksum is used and/or the bunch of applicable
> requirements as described in GRE/UDP are verified, is the goal of improvi=
ng
> performance still achievable? If not, why not directly enable the UDP-che=
cksum
> instead?
>
>     - fragmentation support
>
> In GRE/UDP, it said
>
> " 4.1. MTU and Fragmentation
>
>    Regarding packet fragmentation, an encapsulator/decapsulator SHOULD
>    be compliant with [RFC7588] and perform fragmentation before the
>    encapsulation. The size of fragments SHOULD be less or equal to the
>    PMTU associated with the path between the GRE ingress and the GRE
>    egress tunnel endpoints minus the GRE and UDP overhead ..."
>
> in GUE, it said
>
> " 4.9. MTU and fragmentation
>
>    Standard conventions for handling of MTU (Maximum Transmission Unit)
>    and fragmentation in conjunction with networking tunnels
>    (encapsulation of layer 2 or layer 3 packets) should be followed.
>    Details are described in MTU and Fragmentation Issues with In-the-
>    Network Tunneling [RFC4459]... "
>
> It seems that the only missing thing in the IP-in-UDP draft is to allow t=
he outer
> fragmentation. However, as it said in
> (https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02#page-13), " ..=
.IPsec
> performs only Outer Fragmentation; this distinguishes it from IP-in-IP, w=
hich
> performs only Inner Fragmentation. " Note that IP-in-IP is the dominant
> encapsulation choice within Softwires networks. In other words, performin=
g
> only inner fragmentation works very well in practice. Furthermore, the ou=
ter
> fragmentation issue (e.g., reassembly cost for the egress) would become e=
ven
> worse since the fragments of X-in-UDP packets are more likely to be forwa=
rded
> across different paths than those of X-in-IP and X-in-GRE packets. Hence,=
 I'm
> wondering whether it's worthwhile to support the outer fragmentation on U=
DP
> encapsulated packets which seems useless in practice.
>
>     - signalling support (e.g., to test whether a tunnel is up or
>     to measure MTUs)
>
> I haven't found any description of this in both GRE/UDP and GUE. Did you?
>
>     - support for robust ID fields (related to fragmentation,
>     e.g., to overcome the limits of IPv4 ID as per RFC 6864)
>
> I haven't found any description of this in both GRE/UDP and GUE. Did you?
>
> Xiaohu
>
> > It is not our obligation to find a way for your document to proceed -
> > that onus is on you.
> >
> > Joe

--_000_D382FCD56783Csadikshiciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <04F0D63D812CC047A453F2C38A078610@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>In case of typical datacenter brownfield deployments,&nbsp;</div>
<div>the underlay and overlay may be completely disconnected operationally,=
&nbsp;</div>
<div>hence there can be cases where the mtu mismatch in underlay network ma=
y not</div>
<div>be notified to overlay endpoints and subsequently to end hosts.</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Lloyd Wood &lt;<a href=3D"mai=
lto:lloyd.wood@yahoo.co.uk">lloyd.wood@yahoo.co.uk</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Sunday, June 12, 2016 at 10:4=
1 AM<br>
<span style=3D"font-weight:bold">To: </span>Softwires WG &lt;<a href=3D"mai=
lto:softwires@ietf.org">softwires@ietf.org</a>&gt;, &quot;<a href=3D"mailto=
:int-area@ietf.org">int-area@ietf.org</a>&quot; &lt;<a href=3D"mailto:int-a=
rea@ietf.org">int-area@ietf.org</a>&gt;, &quot;<a href=3D"mailto:lisp@ietf.=
org">lisp@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:lisp@ietf.org">lisp@ietf.org</a>&gt;, &quot;<a href=
=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:t=
svwg@ietf.org">tsvwg@ietf.org</a>&gt;, Xuxiaohu &lt;<a href=3D"mailto:xuxia=
ohu@huawei.com">xuxiaohu@huawei.com</a>&gt;, &quot;<a href=3D"mailto:nvo3@i=
etf.org">nvo3@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [nvo3] [tsvwg] Is it f=
easible to perform fragmentation on UDP encapsulated packets.<br>
</div>
<div><br>
</div>
<div xmlns=3D"http://www.w3.org/1999/xhtml" xmlns:v=3D"urn:schemas-microsof=
t-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office">
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPer=
Inch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
<div><style type=3D"text/css" scoped=3D""> blockquote, div.yahoo_quoted { m=
argin-left: 0 !important; border-left:1px #715FFA solid !important; padding=
-left:1ex !important; background-color:white !important; } </style>Fragment=
ation should be strongly discouraged.
<div><br>
</div>
<div>if you've designed a tunnelling solution and you have fragmentation ha=
ppening as a matter of course, you've designed it wrong.&nbsp;<br>
<br>
Lloyd Wood
<div><a href=3D"mailto:lloyd.wood@yahoo.co.uk">lloyd.wood@yahoo.co.uk</a></=
div>
<br>
<p class=3D"yahoo-quoted-begin" style=3D"font-size: 15px; color: #715FFA; p=
adding-top: 15px; margin-top: 0">
On Friday, May 27, 2016, 8:10 PM, Xuxiaohu &lt;<a href=3D"mailto:xuxiaohu@h=
uawei.com">xuxiaohu@huawei.com</a>&gt; wrote:</p>
<blockquote class=3D"iosymail">
<div id=3D"msgSandbox_AMhLyAoAAG2BnV0gc2BwILcOkyXZc_TEXT" class=3D"msgSandb=
ox" style=3D"padding: 1.5em 0.5em 0.5em 1.2em; word-wrap: break-word;">
&lt;Note that I have changed the subject of the email hence it has nothing =
to do with the WG adoption call now. It's just a discussion on a particular=
 issue which is related to those WGs which are working on UDP tunnels. The =
reason for containing the old email
 is to use it as a background which may be useful for better understanding =
of this particular issue&gt;<br>
<br>
The possible side-effect of performing fragmentation on UDP encapsulated pa=
ckets is to worsen the reassembly burden on tunnel egress since fragments o=
f UDP encapsulated packets are more likely to be forwarded across different=
 paths towards the tunnel egress
 than those of IP or GRE encapsulated packets.<br>
<br>
It seems that most X-over-UDP proposals choose to prohibit the tunnel ingre=
ss from performing fragmentation on UDP encapsulated packets. See the follo=
wing quoted text regarding fragmentation from those X-over-UDP drafts:<br>
<br>
LISP:<br>
<br>
When an ITR receives a packet from a site-facing interface and adds H<br>
&nbsp; octets worth of encapsulation to yield a packet size greater than L<=
br>
&nbsp; octets, it resolves the MTU issue by first splitting the original<br=
>
&nbsp; packet into 2 equal-sized fragments.&nbsp; A LISP header is then pre=
pended<br>
&nbsp; to each fragment.<br>
<br>
VXLAN:<br>
<br>
VTEPs MUST NOT fragment VXLAN packets.&nbsp; Intermediate routers may<br>
&nbsp; fragment encapsulated VXLAN packets due to the larger frame size.<br=
>
&nbsp; The destination VTEP MAY silently discard such VXLAN fragments.<br>
<br>
VXLAN-GPE:<br>
<br>
VTEPs MUST never fragment an encapsulated VXLAN GPE packet, and when<br>
&nbsp; the outer IP header is IPv4, VTEPs MUST set the DF bit in the outer<=
br>
&nbsp; IPv4 header.<br>
<br>
GEVENE:<br>
<br>
&nbsp; To prevent fragmentation and maximize performance, the best practice=
<br>
&nbsp; when using Geneve is to ensure that the MTU of the physical network<=
br>
&nbsp; is greater than or equal to the MTU of the encapsulated network plus=
<br>
&nbsp; tunnel headers.<br>
<br>
GUE:<br>
<br>
&nbsp; &nbsp; If a packet is fragmented before encapsulation in GUE, all th=
e<br>
&nbsp; &nbsp; related fragments must be encapsulated using the same source =
port<br>
&nbsp; &nbsp; (inner flow identifier). An operator may set MTU to account f=
or<br>
&nbsp; &nbsp; encapsulation overhead and reduce the likelihood of fragmenta=
tion.<br>
<br>
GRE/UDP<br>
<br>
Regarding packet fragmentation, an encapsulator/decapsulator SHOULD<br>
&nbsp; be compliant with [RFC7588] and perform fragmentation before the<br>
&nbsp; encapsulation.<br>
<br>
However, the above choice seems conflict with the requirements as described=
 in <a href=3D"https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02" t=
arget=3D"_blank">
https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02</a><br>
<br>
<br>
I wonder whether the IETF should reach a consensus on whether or not the fr=
agmentation on UDP encapsulated packets should be allowed.<br>
&nbsp; <br>
Best regards,<br>
Xiaohu<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Xuxiaohu<br>
&gt; Sent: Thursday, May 26, 2016 4:35 PM<br>
&gt; To: 'Joe Touch'; Fred Baker (fred); Wassim Haddad<br>
&gt; Cc: <a ymailto=3D"mailto:int-area@ietf.org" href=3D"javascript:return"=
>int-area@ietf.org</a><br>
&gt; Subject: RE: [Int-area] Call for adoption of draft-xu-intarea-ip-in-ud=
p-03<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: Joe Touch [mailto:<a ymailto=3D"mailto:touch@isi.edu" href=
=3D"javascript:return">touch@isi.edu</a>]<br>
&gt; &gt; Sent: Thursday, May 26, 2016 2:11 AM<br>
&gt; &gt; To: Xuxiaohu; Fred Baker (fred); Wassim Haddad<br>
&gt; &gt; Cc: <a ymailto=3D"mailto:int-area@ietf.org" href=3D"javascript:re=
turn">int-area@ietf.org</a><br>
&gt; &gt; Subject: Re: [Int-area] Call for adoption of<br>
&gt; &gt; draft-xu-intarea-ip-in-udp-03<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On 5/24/2016 7:24 PM, Xuxiaohu wrote:<br>
&gt; &gt; &gt; Hi Joe,<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I wonder whether you want to tell me the following truth by =
the<br>
&gt; &gt; &gt; example that you gave: no matter whatever improvements we ha=
d done<br>
&gt; &gt; &gt; with this draft, those persons who dislike it by the light o=
f nature<br>
&gt; &gt; &gt; would dislike it in the end.<br>
&gt; &gt;<br>
&gt; &gt; The only improvements that would make this doc useful would be to=
 add<br>
&gt; &gt; capabilities already in GRE/UDP or GUE/UDP, which we already have=
.<br>
&gt; <br>
&gt; Let's go over the four things you mentioned earlier in GRE/UDP and GUE=
/UDP:<br>
&gt; <br>
&gt; &nbsp;&nbsp;&nbsp; - stronger checksums<br>
&gt; <br>
&gt; In GRE/UDP, in order to use UDP-zero-checksum, it gave the following<b=
r>
&gt; restrictions:<br>
&gt; &quot; 6. UDP Checksum Handling<br>
&gt; <br>
&gt;&nbsp; &nbsp; 6.1. UDP Checksum with IPv4<br>
&gt; <br>
&gt;&nbsp; &nbsp; For UDP in IPv4, the UDP checksum MUST be processed as sp=
ecified in<br>
&gt;&nbsp; &nbsp; [RFC768] and [RFC1122] for both transmit and receive. The=
 IPv4<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Yong, Crabber, Xu, Herbert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; [Page 12]<br>
&gt; ----------------------------------------------------------------------=
----------<br>
&gt; <br>
&gt; Internet-Draft&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GRE-in-UDP Encapsulat=
ion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; March 2016<br>
&gt; <br>
&gt;&nbsp; &nbsp; header includes a checksum which protects against mis-del=
ivery of<br>
&gt;&nbsp; &nbsp; the packet due to corruption of IP addresses. The UDP che=
cksum<br>
&gt;&nbsp; &nbsp; potentially provides protection against corruption of the=
 UDP header,<br>
&gt;&nbsp; &nbsp; GRE header, and GRE payload. Disabling the use of checksu=
ms is a<br>
&gt;&nbsp; &nbsp; deployment consideration that should take into account th=
e risk and<br>
&gt;&nbsp; &nbsp; effects of packet corruption.<br>
&gt; <br>
&gt;&nbsp; &nbsp; When a decapsulator receives a packet, the UDP checksum f=
ield MUST<br>
&gt;&nbsp; &nbsp; be processed. If the UDP checksum is non-zero, the decaps=
ulator MUST<br>
&gt;&nbsp; &nbsp; verify the checksum before accepting the packet. By defau=
lt a<br>
&gt;&nbsp; &nbsp; decapsulator SHOULD accept UDP packets with a zero checks=
um. A node<br>
&gt;&nbsp; &nbsp; MAY be configured to disallow zero checksums per [RFC1122=
]; this may<br>
&gt;&nbsp; &nbsp; be done selectively, for instance disallowing zero checks=
ums from<br>
&gt;&nbsp; &nbsp; certain hosts that are known to be sending over paths sub=
ject to<br>
&gt;&nbsp; &nbsp; packet corruption. If verification of a non-zero checksum=
 fails, a<br>
&gt;&nbsp; &nbsp; decapsulator lacks the capability to verify a non-zero ch=
ecksum, or<br>
&gt;&nbsp; &nbsp; a packet with a zero-checksum was received and the decaps=
ulator is<br>
&gt;&nbsp; &nbsp; configured to disallow, the packet MUST be dropped and an=
 event MAY<br>
&gt;&nbsp; &nbsp; be logged.<br>
&gt; <br>
&gt;&nbsp; &nbsp; 6.2. UDP Checksum with IPv6<br>
&gt; <br>
&gt;&nbsp; &nbsp; For UDP in IPv6, the UDP checksum MUST be processed as sp=
ecified in<br>
&gt;&nbsp; &nbsp; [RFC768] and [RFC2460] for both transmit and receive.<br>
&gt; <br>
&gt;&nbsp; &nbsp; When UDP is used over IPv6, the UDP checksum is relied up=
on to<br>
&gt;&nbsp; &nbsp; protect both the IPv6 and UDP headers from corruption. As=
 such, A<br>
&gt;&nbsp; &nbsp; default GRE-in-UDP Tunnel MUST perform UDP checksum; A TM=
CE GRE-in-<br>
&gt;&nbsp; &nbsp; UDP Tunnel MAY be configured with the UDP zero-checksum m=
ode if the<br>
&gt;&nbsp; &nbsp; traffic-managed controlled environment or a set of closel=
y<br>
&gt;&nbsp; &nbsp; cooperating traffic-managed controlled environments (such=
 as by<br>
&gt;&nbsp; &nbsp; network operators who have agreed to work together in ord=
er to<br>
&gt;&nbsp; &nbsp; jointly provide specific services) meet at least one of f=
ollowing<br>
&gt;&nbsp; &nbsp; conditions:<br>
&gt; <br>
&gt;&nbsp; &nbsp; a. It is known (perhaps through knowledge of equipment ty=
pes and<br>
&gt;&nbsp; &nbsp; &nbsp; lower layer checks) that packet corruption is exce=
ptionally<br>
&gt;&nbsp; &nbsp; &nbsp; unlikely and where the operator is willing to take=
 the risk of<br>
&gt;&nbsp; &nbsp; &nbsp; undetected packet corruption.<br>
&gt; <br>
&gt;&nbsp; &nbsp; b. It is judged through observational measurements (perha=
ps of<br>
&gt;&nbsp; &nbsp; &nbsp; historic or current traffic flows that use a non-z=
ero checksum)<br>
&gt;&nbsp; &nbsp; &nbsp; that the level of packet corruption is tolerably l=
ow and where<br>
&gt;&nbsp; &nbsp; &nbsp; the operator is willing to take the risk of undete=
cted packet<br>
&gt;&nbsp; &nbsp; &nbsp; corruption.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Yong, Crabber, Xu, Herbert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; [Page 13]<br>
&gt; ----------------------------------------------------------------------=
----------<br>
&gt; <br>
&gt; Internet-Draft&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GRE-in-UDP Encapsulat=
ion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; March 2016<br>
&gt; <br>
&gt;&nbsp; &nbsp; c. Carrying applications that are tolerant of mis-deliver=
ed or<br>
&gt;&nbsp; &nbsp; &nbsp; corrupted packets (perhaps through higher layer ch=
ecksum,<br>
&gt;&nbsp; &nbsp; &nbsp; validation, and retransmission or transmission red=
undancy) where<br>
&gt;&nbsp; &nbsp; &nbsp; the operator is willing to rely on the application=
s using the<br>
&gt;&nbsp; &nbsp; &nbsp; tunnel to survive any corrupt packets.<br>
&gt; <br>
&gt;&nbsp; &nbsp; The following requirements apply to a TMCE GRE-in-UDP tun=
nel that<br>
&gt;&nbsp; &nbsp; use UDP zero-checksum mode:<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; a. Use of the UDP checksum with IPv6 MUST be the d=
efault<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; configuration of all GRE-in-UDP tunnels.<br=
>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; b. The GRE-in-UDP tunnel implementation MUST compl=
y with all<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; requirements specified in Section 4 of [RFC=
6936] and with<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; requirement 1 specified in Section 5 of [RF=
C6936].<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; c. The tunnel decapsulator SHOULD only allow the u=
se of UDP zero-<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; checksum mode for IPv6 on a single received=
 UDP Destination<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; Port regardless of the encapsulator. The mo=
tivation for this<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; requirement is possible corruption of the U=
DP Destination Port,<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; which may cause packet delivery to the wron=
g UDP port. If that<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; other UDP port requires the UDP checksum, t=
he mis-delivered<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; packet will be discarded.<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; d. It is RECOMMENDED that the UDP zero-checksum mo=
de for IPv6 is<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; only enabled for certain selected source ad=
dresses. The tunnel<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; decapsulator MUST check that the source and=
 destination IPv6<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; addresses are valid for the GRE-in-UDP tunn=
el on which the<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; packet was received if that tunnel uses UDP=
 zero-checksum mode<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; and discard any packet for which this check=
 fails.<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; e. The tunnel encapsulator SHOULD use different IP=
v6 addresses for<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; each GRE-in-UDP tunnel that uses UDP zero-c=
hecksum mode<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; regardless of the decapsulator in order to =
strengthen the<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; decapsulator's check of the IPv6 source add=
ress (i.e., the same<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; IPv6 source address SHOULD NOT be used with=
 more than one IPv6<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; destination address, independent of whether=
 that destination<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; address is a unicast or multicast address).=
 When this is not<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; possible, it is RECOMMENDED to use each sou=
rce IPv6 address for<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; as few UDP zero-checksum mode GRE-in-UDP tu=
nnels as is feasible.<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; f. When any middlebox exists on the path of a GRE-=
in-UDP tunnel,<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; it is RECOMMENDED to use the default mode, =
i.e. use UDP<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; checksum, to reduce the chance that the enc=
apsulated packets to<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; be dropped.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Yong, Crabber, Xu, Herbert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; [Page 14]<br>
&gt; ----------------------------------------------------------------------=
----------<br>
&gt; <br>
&gt; Internet-Draft&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GRE-in-UDP Encapsulat=
ion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; March 2016<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; g. Any middlebox that allows the UDP zero-checksum=
 mode for IPv6<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; MUST comply with requirement 1 and 8-10 in =
Section 5 of<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; [RFC6936].<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; h. Measures SHOULD be taken to prevent IPv6 traffi=
c with zero UDP<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; checksums from &quot;escaping&quot; to the =
general Internet; see Section<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; 8 for examples of such measures.<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; i. IPv6 traffic with zero UDP checksums MUST be ac=
tively monitored<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; for errors by the network operator. For exa=
mple, the operator<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; may monitor Ethernet layer packet error rat=
es.<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; j. If a packet with a non-zero checksum is receive=
d, the checksum<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; MUST be verified before accepting the packe=
t. This is<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; regardless of whether the tunnel encapsulat=
or and decapsulator<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; have been configured with UDP zero-checksum=
 mode.<br>
&gt; <br>
&gt;&nbsp; &nbsp; The above requirements do not change either the requireme=
nts<br>
&gt;&nbsp; &nbsp; specified in [RFC2460] as modified by [RFC6935] or the re=
quirements<br>
&gt;&nbsp; &nbsp; specified in [RFC6936].<br>
&gt; <br>
&gt;&nbsp; &nbsp; The requirement to check the source IPv6 address in addit=
ion to the<br>
&gt;&nbsp; &nbsp; destination IPv6 address, plus the strong recommendation =
against<br>
&gt;&nbsp; &nbsp; reuse of source IPv6 addresses among GRE-in-UDP tunnels c=
ollectively<br>
&gt;&nbsp; &nbsp; provide some mitigation for the absence of UDP checksum c=
overage of<br>
&gt;&nbsp; &nbsp; the IPv6 header. A traffic-managed controlled environment=
 that<br>
&gt;&nbsp; &nbsp; satisfies at least one of three conditions listed above i=
n this<br>
&gt;&nbsp; &nbsp; section provides additional assurance.<br>
&gt; <br>
&gt;&nbsp; &nbsp; A GRE-in-UDP tunnel is suitable for transmission over low=
er layers<br>
&gt;&nbsp; &nbsp; in the traffic-managed controlled environments that are a=
llowed by<br>
&gt;&nbsp; &nbsp; the exceptions stated above and the rate of corruption of=
 the inner<br>
&gt;&nbsp; &nbsp; IP packet on such networks is not expected to increase by=
 comparison<br>
&gt;&nbsp; &nbsp; to GRE traffic that is not encapsulated in UDP.&nbsp; For=
 these reasons,<br>
&gt;&nbsp; &nbsp; GRE-in-UDP does not provide an additional integrity check=
 except<br>
&gt;&nbsp; &nbsp; when GRE checksum is used when UDP zero-checksum mode is =
used with<br>
&gt;&nbsp; &nbsp; IPv6, and this design is in accordance with requirements =
2, 3 and 5<br>
&gt;&nbsp; &nbsp; specified in Section 5 of [RFC6936].<br>
&gt; <br>
&gt;&nbsp; &nbsp; Generic Router Encapsulation (GRE) does not accumulate in=
correct<br>
&gt;&nbsp; &nbsp; state as a consequence of GRE header corruption. A corrup=
t GRE<br>
&gt;&nbsp; &nbsp; packet may result in either packet discard or forwarding =
of the<br>
&gt;&nbsp; &nbsp; packet without accumulation of GRE state. Active monitori=
ng of GRE-<br>
&gt;&nbsp; &nbsp; in-UDP traffic for errors is REQUIRED as occurrence of er=
rors will<br>
&gt;&nbsp; &nbsp; result in some accumulation of error information outside =
the<br>
&gt;&nbsp; &nbsp; protocol for operational and management purposes. This de=
sign is in<br>
&gt;&nbsp; &nbsp; accordance with requirement 4 specified in Section 5 of [=
RFC6936].<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Yong, Crabber, Xu, Herbert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; [Page 15]<br>
&gt; ----------------------------------------------------------------------=
----------<br>
&gt; <br>
&gt; Internet-Draft&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GRE-in-UDP Encapsulat=
ion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; March 2016<br>
&gt; <br>
&gt;&nbsp; &nbsp; The remaining requirements specified in Section 5 of [RFC=
6936] are<br>
&gt;&nbsp; &nbsp; not applicable to GRE-in-UDP.&nbsp; Requirements 6 and 7 =
do not apply<br>
&gt;&nbsp; &nbsp; because GRE does not include a control feedback mechanism=
.<br>
&gt;&nbsp; &nbsp; Requirements 8-10 are middlebox requirements that do not =
apply to<br>
&gt;&nbsp; &nbsp; GRE-in-UDP tunnel endpoints (see Section 7.1 for further =
middlebox<br>
&gt;&nbsp; &nbsp; discussion).<br>
&gt; <br>
&gt;&nbsp; &nbsp; It is worth mentioning that the use of a zero UDP checksu=
m should<br>
&gt;&nbsp; &nbsp; present the equivalent risk of undetected packet corrupti=
on when<br>
&gt;&nbsp; &nbsp; sending similar packet using GRE-in-IPv6 without UDP [RFC=
7676] and<br>
&gt;&nbsp; &nbsp; without GRE checksums.<br>
&gt; <br>
&gt;&nbsp; &nbsp; In summary, a TMCE GRE-in-UDP Tunnel is allowed to use UD=
P-zero-<br>
&gt;&nbsp; &nbsp; checksum mode for IPv6 when the conditions and requiremen=
ts stated<br>
&gt;&nbsp; &nbsp; above are met. Otherwise the UDP checksum need to be used=
 for IPv6<br>
&gt;&nbsp; &nbsp; as specified in [RFC768] and [RFC2460]. Use of GRE checks=
um is<br>
&gt;&nbsp; &nbsp; RECOMMENED when the UDP checksum is not used.<br>
&gt; &quot;<br>
&gt; <br>
&gt; In GUE, to support UDP-checksum-zero, it said<br>
&gt; <br>
&gt; &quot; Therefore, when GUE is used over<br>
&gt;&nbsp; &nbsp; IPv6, either the UDP checksum must be enabled or the GUE =
header<br>
&gt;&nbsp; &nbsp; checksum must be used.&nbsp; An encapsulator MAY set a ze=
ro UDP checksum<br>
&gt;&nbsp; &nbsp; for performance or implementation reasons, in which case =
the GUE<br>
&gt;&nbsp; &nbsp; header checksum MUST be used or applicable requirements f=
or using<br>
&gt;&nbsp; &nbsp; zero UDP checksums in [GREUDP] MUST be met. If the UDP ch=
ecksum is<br>
&gt;&nbsp; &nbsp; enabled, then the GUE header checksum should not be used =
since it is<br>
&gt;&nbsp; &nbsp; mostly redundant.&quot;<br>
&gt; <br>
&gt; It's easy for me to add the similar words to the IP-in-UDP draft like =
&quot;the<br>
&gt; applicable requirements for using zero UDP checksum in [GREUDP] MUST b=
e<br>
&gt; met when zero UDP checksum is used by the tunnel ingress&quot;. Howeve=
r, the<br>
&gt; major goal for disabling the UDP checksum is to improve the performanc=
e.<br>
&gt; When GUE header checksum is used and/or the bunch of applicable<br>
&gt; requirements as described in GRE/UDP are verified, is the goal of impr=
oving<br>
&gt; performance still achievable? If not, why not directly enable the UDP-=
checksum<br>
&gt; instead?<br>
&gt; <br>
&gt; &nbsp;&nbsp;&nbsp; - fragmentation support<br>
&gt; <br>
&gt; In GRE/UDP, it said<br>
&gt; <br>
&gt; &quot; 4.1. MTU and Fragmentation<br>
&gt; <br>
&gt;&nbsp; &nbsp; Regarding packet fragmentation, an encapsulator/decapsula=
tor SHOULD<br>
&gt;&nbsp; &nbsp; be compliant with [RFC7588] and perform fragmentation bef=
ore the<br>
&gt;&nbsp; &nbsp; encapsulation. The size of fragments SHOULD be less or eq=
ual to the<br>
&gt;&nbsp; &nbsp; PMTU associated with the path between the GRE ingress and=
 the GRE<br>
&gt;&nbsp; &nbsp; egress tunnel endpoints minus the GRE and UDP overhead ..=
.&quot;<br>
&gt; <br>
&gt; in GUE, it said<br>
&gt; <br>
&gt; &quot; 4.9. MTU and fragmentation<br>
&gt; <br>
&gt;&nbsp; &nbsp; Standard conventions for handling of MTU (Maximum Transmi=
ssion Unit)<br>
&gt;&nbsp; &nbsp; and fragmentation in conjunction with networking tunnels<=
br>
&gt;&nbsp; &nbsp; (encapsulation of layer 2 or layer 3 packets) should be f=
ollowed.<br>
&gt;&nbsp; &nbsp; Details are described in MTU and Fragmentation Issues wit=
h In-the-<br>
&gt;&nbsp; &nbsp; Network Tunneling [RFC4459]... &quot;<br>
&gt; <br>
&gt; It seems that the only missing thing in the IP-in-UDP draft is to allo=
w the outer<br>
&gt; fragmentation. However, as it said in<br>
&gt; (<a href=3D"https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02#=
page-13" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-intarea-t=
unnels-02#page-13</a>), &quot; ...IPsec<br>
&gt; performs only Outer Fragmentation; this distinguishes it from IP-in-IP=
, which<br>
&gt; performs only Inner Fragmentation. &quot; Note that IP-in-IP is the do=
minant<br>
&gt; encapsulation choice within Softwires networks. In other words, perfor=
ming<br>
&gt; only inner fragmentation works very well in practice. Furthermore, the=
 outer<br>
&gt; fragmentation issue (e.g., reassembly cost for the egress) would becom=
e even<br>
&gt; worse since the fragments of X-in-UDP packets are more likely to be fo=
rwarded<br>
&gt; across different paths than those of X-in-IP and X-in-GRE packets. Hen=
ce, I'm<br>
&gt; wondering whether it's worthwhile to support the outer fragmentation o=
n UDP<br>
&gt; encapsulated packets which seems useless in practice.<br>
&gt; <br>
&gt; &nbsp;&nbsp;&nbsp; - signalling support (e.g., to test whether a tunne=
l is up or<br>
&gt; &nbsp;&nbsp;&nbsp; to measure MTUs)<br>
&gt; <br>
&gt; I haven't found any description of this in both GRE/UDP and GUE. Did y=
ou?<br>
&gt; <br>
&gt; &nbsp;&nbsp;&nbsp; - support for robust ID fields (related to fragment=
ation,<br>
&gt; &nbsp;&nbsp;&nbsp; e.g., to overcome the limits of IPv4 ID as per RFC =
6864)<br>
&gt; <br>
&gt; I haven't found any description of this in both GRE/UDP and GUE. Did y=
ou?<br>
&gt; <br>
&gt; Xiaohu<br>
&gt; <br>
&gt; &gt; It is not our obligation to find a way for your document to proce=
ed -<br>
&gt; &gt; that onus is on you.<br>
&gt; &gt;<br>
&gt; &gt; Joe<br>
</div>
<blockquote></blockquote>
</blockquote>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D382FCD56783Csadikshiciscocom_--


From nobody Wed Jun 15 14:00:54 2016
Return-Path: <touch@isi.edu>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5808912DB4D; Wed, 15 Jun 2016 13:13:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.325
X-Spam-Level: 
X-Spam-Status: No, score=-8.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 242GUliZqxNX; Wed, 15 Jun 2016 13:13:43 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ACA612DB3F; Wed, 15 Jun 2016 13:13:43 -0700 (PDT)
Received: from [128.9.184.95] ([128.9.184.95]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u5FKCVX2010402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Jun 2016 13:12:32 -0700 (PDT)
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>, Softwires WG <softwires@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Xuxiaohu <xuxiaohu@huawei.com>, "nvo3@ietf.org" <nvo3@ietf.org>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D555482@NKGEML515-MBS.china.huawei.com> <57448C14.2060203@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5557DE@NKGEML515-MBS.china.huawei.com> <9c462520-eb8e-fcd0-0a08-228f80fbc779@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5596E0@NKGEML515-MBS.china.huawei.com> <974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <5761B6AF.8030107@isi.edu>
Date: Wed, 15 Jun 2016 13:12:31 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com>
Content-Type: multipart/alternative; boundary="------------030502040200010703010909"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/llfytsqcSnRRPrm9cys2jL3vsak>
X-Mailman-Approved-At: Wed, 15 Jun 2016 14:00:44 -0700
Subject: Re: [Softwires] [tsvwg] Is it feasible to perform fragmentation on UDP encapsulated packets.
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 20:13:47 -0000

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



On 6/11/2016 10:11 PM, Lloyd Wood wrote:
> Fragmentation should be strongly discouraged.

Avoided where possible for sure.
>
> if you've designed a tunnelling solution and you have fragmentation
> happening as a matter of course, you've designed it wrong.

If you have a solution that recurses (X over X, with some intervening
layers or not), and X has a required minimum message size, then you
either have a solution that - in at least some non-trivial situations -
will fragment as a matter of course or a fantasy that cannot exist.

The only reason we avoid this in typical operation is by avoiding X over
X. Once you have a tunnel, that might not be avoidable (or even
detectable, depending on encryption).

Joe

>
> Lloyd Wood
> lloyd.wood@yahoo.co.uk
>
> On Friday, May 27, 2016, 8:10 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>
>     <Note that I have changed the subject of the email hence it has
>     nothing to do with the WG adoption call now. It's just a
>     discussion on a particular issue which is related to those WGs
>     which are working on UDP tunnels. The reason for containing the
>     old email is to use it as a background which may be useful for
>     better understanding of this particular issue>
>
>     The possible side-effect of performing fragmentation on UDP
>     encapsulated packets is to worsen the reassembly burden on tunnel
>     egress since fragments of UDP encapsulated packets are more likely
>     to be forwarded across different paths towards the tunnel egress
>     than those of IP or GRE encapsulated packets.
>
>     It seems that most X-over-UDP proposals choose to prohibit the
>     tunnel ingress from performing fragmentation on UDP encapsulated
>     packets. See the following quoted text regarding fragmentation
>     from those X-over-UDP drafts:
>
>     LISP:
>
>     When an ITR receives a packet from a site-facing interface and adds H
>       octets worth of encapsulation to yield a packet size greater than L
>       octets, it resolves the MTU issue by first splitting the original
>       packet into 2 equal-sized fragments.  A LISP header is then
>     prepended
>       to each fragment.
>
>     VXLAN:
>
>     VTEPs MUST NOT fragment VXLAN packets.  Intermediate routers may
>       fragment encapsulated VXLAN packets due to the larger frame size.
>       The destination VTEP MAY silently discard such VXLAN fragments.
>
>     VXLAN-GPE:
>
>     VTEPs MUST never fragment an encapsulated VXLAN GPE packet, and when
>       the outer IP header is IPv4, VTEPs MUST set the DF bit in the outer
>       IPv4 header.
>
>     GEVENE:
>
>       To prevent fragmentation and maximize performance, the best practice
>       when using Geneve is to ensure that the MTU of the physical network
>       is greater than or equal to the MTU of the encapsulated network plus
>       tunnel headers.
>
>     GUE:
>
>         If a packet is fragmented before encapsulation in GUE, all the
>         related fragments must be encapsulated using the same source port
>         (inner flow identifier). An operator may set MTU to account for
>         encapsulation overhead and reduce the likelihood of fragmentation.
>
>     GRE/UDP
>
>     Regarding packet fragmentation, an encapsulator/decapsulator SHOULD
>       be compliant with [RFC7588] and perform fragmentation before the
>       encapsulation.
>
>     However, the above choice seems conflict with the requirements as
>     described in https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02
>
>
>     I wonder whether the IETF should reach a consensus on whether or
>     not the fragmentation on UDP encapsulated packets should be allowed.
>      
>     Best regards,
>     Xiaohu
>
>     > -----Original Message-----
>     > From: Xuxiaohu
>     > Sent: Thursday, May 26, 2016 4:35 PM
>     > To: 'Joe Touch'; Fred Baker (fred); Wassim Haddad
>     > Cc: int-area@ietf.org <javascript:return>
>     > Subject: RE: [Int-area] Call for adoption of
>     draft-xu-intarea-ip-in-udp-03
>     >
>     >
>     >
>     > > -----Original Message-----
>     > > From: Joe Touch [mailto:touch@isi.edu <javascript:return>]
>     > > Sent: Thursday, May 26, 2016 2:11 AM
>     > > To: Xuxiaohu; Fred Baker (fred); Wassim Haddad
>     > > Cc: int-area@ietf.org <javascript:return>
>     > > Subject: Re: [Int-area] Call for adoption of
>     > > draft-xu-intarea-ip-in-udp-03
>     > >
>     > >
>     > >
>     > > On 5/24/2016 7:24 PM, Xuxiaohu wrote:
>     > > > Hi Joe,
>     > > >
>     > > > I wonder whether you want to tell me the following truth by the
>     > > > example that you gave: no matter whatever improvements we
>     had done
>     > > > with this draft, those persons who dislike it by the light
>     of nature
>     > > > would dislike it in the end.
>     > >
>     > > The only improvements that would make this doc useful would be
>     to add
>     > > capabilities already in GRE/UDP or GUE/UDP, which we already have.
>     >
>     > Let's go over the four things you mentioned earlier in GRE/UDP
>     and GUE/UDP:
>     >
>     >     - stronger checksums
>     >
>     > In GRE/UDP, in order to use UDP-zero-checksum, it gave the following
>     > restrictions:
>     > " 6. UDP Checksum Handling
>     >
>     >    6.1. UDP Checksum with IPv4
>     >
>     >    For UDP in IPv4, the UDP checksum MUST be processed as
>     specified in
>     >    [RFC768] and [RFC1122] for both transmit and receive. The IPv4
>     >
>     >
>     >
>     > Yong, Crabber, Xu, Herbert                                   
>     [Page 12]
>     >
>     --------------------------------------------------------------------------------
>     >
>     > Internet-Draft          GRE-in-UDP Encapsulation           
>     March 2016
>     >
>     >    header includes a checksum which protects against mis-delivery of
>     >    the packet due to corruption of IP addresses. The UDP checksum
>     >    potentially provides protection against corruption of the UDP
>     header,
>     >    GRE header, and GRE payload. Disabling the use of checksums is a
>     >    deployment consideration that should take into account the
>     risk and
>     >    effects of packet corruption.
>     >
>     >    When a decapsulator receives a packet, the UDP checksum field
>     MUST
>     >    be processed. If the UDP checksum is non-zero, the
>     decapsulator MUST
>     >    verify the checksum before accepting the packet. By default a
>     >    decapsulator SHOULD accept UDP packets with a zero checksum.
>     A node
>     >    MAY be configured to disallow zero checksums per [RFC1122];
>     this may
>     >    be done selectively, for instance disallowing zero checksums from
>     >    certain hosts that are known to be sending over paths subject to
>     >    packet corruption. If verification of a non-zero checksum
>     fails, a
>     >    decapsulator lacks the capability to verify a non-zero
>     checksum, or
>     >    a packet with a zero-checksum was received and the
>     decapsulator is
>     >    configured to disallow, the packet MUST be dropped and an
>     event MAY
>     >    be logged.
>     >
>     >    6.2. UDP Checksum with IPv6
>     >
>     >    For UDP in IPv6, the UDP checksum MUST be processed as
>     specified in
>     >    [RFC768] and [RFC2460] for both transmit and receive.
>     >
>     >    When UDP is used over IPv6, the UDP checksum is relied upon to
>     >    protect both the IPv6 and UDP headers from corruption. As such, A
>     >    default GRE-in-UDP Tunnel MUST perform UDP checksum; A TMCE
>     GRE-in-
>     >    UDP Tunnel MAY be configured with the UDP zero-checksum mode
>     if the
>     >    traffic-managed controlled environment or a set of closely
>     >    cooperating traffic-managed controlled environments (such as by
>     >    network operators who have agreed to work together in order to
>     >    jointly provide specific services) meet at least one of following
>     >    conditions:
>     >
>     >    a. It is known (perhaps through knowledge of equipment types and
>     >      lower layer checks) that packet corruption is exceptionally
>     >      unlikely and where the operator is willing to take the risk of
>     >      undetected packet corruption.
>     >
>     >    b. It is judged through observational measurements (perhaps of
>     >      historic or current traffic flows that use a non-zero checksum)
>     >      that the level of packet corruption is tolerably low and where
>     >      the operator is willing to take the risk of undetected packet
>     >      corruption.
>     >
>     >
>     >
>     >
>     >
>     > Yong, Crabber, Xu, Herbert                                   
>     [Page 13]
>     >
>     --------------------------------------------------------------------------------
>     >
>     > Internet-Draft          GRE-in-UDP Encapsulation           
>     March 2016
>     >
>     >    c. Carrying applications that are tolerant of mis-delivered or
>     >      corrupted packets (perhaps through higher layer checksum,
>     >      validation, and retransmission or transmission redundancy)
>     where
>     >      the operator is willing to rely on the applications using the
>     >      tunnel to survive any corrupt packets.
>     >
>     >    The following requirements apply to a TMCE GRE-in-UDP tunnel that
>     >    use UDP zero-checksum mode:
>     >
>     >      a. Use of the UDP checksum with IPv6 MUST be the default
>     >        configuration of all GRE-in-UDP tunnels.
>     >
>     >      b. The GRE-in-UDP tunnel implementation MUST comply with all
>     >        requirements specified in Section 4 of [RFC6936] and with
>     >        requirement 1 specified in Section 5 of [RFC6936].
>     >
>     >      c. The tunnel decapsulator SHOULD only allow the use of UDP
>     zero-
>     >        checksum mode for IPv6 on a single received UDP Destination
>     >        Port regardless of the encapsulator. The motivation for this
>     >        requirement is possible corruption of the UDP Destination
>     Port,
>     >        which may cause packet delivery to the wrong UDP port. If
>     that
>     >        other UDP port requires the UDP checksum, the mis-delivered
>     >        packet will be discarded.
>     >
>     >      d. It is RECOMMENDED that the UDP zero-checksum mode for
>     IPv6 is
>     >        only enabled for certain selected source addresses. The
>     tunnel
>     >        decapsulator MUST check that the source and destination IPv6
>     >        addresses are valid for the GRE-in-UDP tunnel on which the
>     >        packet was received if that tunnel uses UDP zero-checksum
>     mode
>     >        and discard any packet for which this check fails.
>     >
>     >      e. The tunnel encapsulator SHOULD use different IPv6
>     addresses for
>     >        each GRE-in-UDP tunnel that uses UDP zero-checksum mode
>     >        regardless of the decapsulator in order to strengthen the
>     >        decapsulator's check of the IPv6 source address (i.e.,
>     the same
>     >        IPv6 source address SHOULD NOT be used with more than one
>     IPv6
>     >        destination address, independent of whether that destination
>     >        address is a unicast or multicast address). When this is not
>     >        possible, it is RECOMMENDED to use each source IPv6
>     address for
>     >        as few UDP zero-checksum mode GRE-in-UDP tunnels as is
>     feasible.
>     >
>     >      f. When any middlebox exists on the path of a GRE-in-UDP
>     tunnel,
>     >        it is RECOMMENDED to use the default mode, i.e. use UDP
>     >        checksum, to reduce the chance that the encapsulated
>     packets to
>     >        be dropped.
>     >
>     >
>     >
>     >
>     >
>     > Yong, Crabber, Xu, Herbert                                   
>     [Page 14]
>     >
>     --------------------------------------------------------------------------------
>     >
>     > Internet-Draft          GRE-in-UDP Encapsulation           
>     March 2016
>     >
>     >      g. Any middlebox that allows the UDP zero-checksum mode for
>     IPv6
>     >        MUST comply with requirement 1 and 8-10 in Section 5 of
>     >        [RFC6936].
>     >
>     >      h. Measures SHOULD be taken to prevent IPv6 traffic with
>     zero UDP
>     >        checksums from "escaping" to the general Internet; see
>     Section
>     >        8 for examples of such measures.
>     >
>     >      i. IPv6 traffic with zero UDP checksums MUST be actively
>     monitored
>     >        for errors by the network operator. For example, the operator
>     >        may monitor Ethernet layer packet error rates.
>     >
>     >      j. If a packet with a non-zero checksum is received, the
>     checksum
>     >        MUST be verified before accepting the packet. This is
>     >        regardless of whether the tunnel encapsulator and
>     decapsulator
>     >        have been configured with UDP zero-checksum mode.
>     >
>     >    The above requirements do not change either the requirements
>     >    specified in [RFC2460] as modified by [RFC6935] or the
>     requirements
>     >    specified in [RFC6936].
>     >
>     >    The requirement to check the source IPv6 address in addition
>     to the
>     >    destination IPv6 address, plus the strong recommendation against
>     >    reuse of source IPv6 addresses among GRE-in-UDP tunnels
>     collectively
>     >    provide some mitigation for the absence of UDP checksum
>     coverage of
>     >    the IPv6 header. A traffic-managed controlled environment that
>     >    satisfies at least one of three conditions listed above in this
>     >    section provides additional assurance.
>     >
>     >    A GRE-in-UDP tunnel is suitable for transmission over lower
>     layers
>     >    in the traffic-managed controlled environments that are
>     allowed by
>     >    the exceptions stated above and the rate of corruption of the
>     inner
>     >    IP packet on such networks is not expected to increase by
>     comparison
>     >    to GRE traffic that is not encapsulated in UDP.  For these
>     reasons,
>     >    GRE-in-UDP does not provide an additional integrity check except
>     >    when GRE checksum is used when UDP zero-checksum mode is used
>     with
>     >    IPv6, and this design is in accordance with requirements 2, 3
>     and 5
>     >    specified in Section 5 of [RFC6936].
>     >
>     >    Generic Router Encapsulation (GRE) does not accumulate incorrect
>     >    state as a consequence of GRE header corruption. A corrupt GRE
>     >    packet may result in either packet discard or forwarding of the
>     >    packet without accumulation of GRE state. Active monitoring
>     of GRE-
>     >    in-UDP traffic for errors is REQUIRED as occurrence of errors
>     will
>     >    result in some accumulation of error information outside the
>     >    protocol for operational and management purposes. This design
>     is in
>     >    accordance with requirement 4 specified in Section 5 of
>     [RFC6936].
>     >
>     >
>     >
>     > Yong, Crabber, Xu, Herbert                                   
>     [Page 15]
>     >
>     --------------------------------------------------------------------------------
>     >
>     > Internet-Draft          GRE-in-UDP Encapsulation           
>     March 2016
>     >
>     >    The remaining requirements specified in Section 5 of
>     [RFC6936] are
>     >    not applicable to GRE-in-UDP.  Requirements 6 and 7 do not apply
>     >    because GRE does not include a control feedback mechanism.
>     >    Requirements 8-10 are middlebox requirements that do not apply to
>     >    GRE-in-UDP tunnel endpoints (see Section 7.1 for further
>     middlebox
>     >    discussion).
>     >
>     >    It is worth mentioning that the use of a zero UDP checksum should
>     >    present the equivalent risk of undetected packet corruption when
>     >    sending similar packet using GRE-in-IPv6 without UDP
>     [RFC7676] and
>     >    without GRE checksums.
>     >
>     >    In summary, a TMCE GRE-in-UDP Tunnel is allowed to use UDP-zero-
>     >    checksum mode for IPv6 when the conditions and requirements
>     stated
>     >    above are met. Otherwise the UDP checksum need to be used for
>     IPv6
>     >    as specified in [RFC768] and [RFC2460]. Use of GRE checksum is
>     >    RECOMMENED when the UDP checksum is not used.
>     > "
>     >
>     > In GUE, to support UDP-checksum-zero, it said
>     >
>     > " Therefore, when GUE is used over
>     >    IPv6, either the UDP checksum must be enabled or the GUE header
>     >    checksum must be used.  An encapsulator MAY set a zero UDP
>     checksum
>     >    for performance or implementation reasons, in which case the GUE
>     >    header checksum MUST be used or applicable requirements for using
>     >    zero UDP checksums in [GREUDP] MUST be met. If the UDP
>     checksum is
>     >    enabled, then the GUE header checksum should not be used
>     since it is
>     >    mostly redundant."
>     >
>     > It's easy for me to add the similar words to the IP-in-UDP draft
>     like "the
>     > applicable requirements for using zero UDP checksum in [GREUDP]
>     MUST be
>     > met when zero UDP checksum is used by the tunnel ingress".
>     However, the
>     > major goal for disabling the UDP checksum is to improve the
>     performance.
>     > When GUE header checksum is used and/or the bunch of applicable
>     > requirements as described in GRE/UDP are verified, is the goal
>     of improving
>     > performance still achievable? If not, why not directly enable
>     the UDP-checksum
>     > instead?
>     >
>     >     - fragmentation support
>     >
>     > In GRE/UDP, it said
>     >
>     > " 4.1. MTU and Fragmentation
>     >
>     >    Regarding packet fragmentation, an encapsulator/decapsulator
>     SHOULD
>     >    be compliant with [RFC7588] and perform fragmentation before the
>     >    encapsulation. The size of fragments SHOULD be less or equal
>     to the
>     >    PMTU associated with the path between the GRE ingress and the GRE
>     >    egress tunnel endpoints minus the GRE and UDP overhead ..."
>     >
>     > in GUE, it said
>     >
>     > " 4.9. MTU and fragmentation
>     >
>     >    Standard conventions for handling of MTU (Maximum
>     Transmission Unit)
>     >    and fragmentation in conjunction with networking tunnels
>     >    (encapsulation of layer 2 or layer 3 packets) should be followed.
>     >    Details are described in MTU and Fragmentation Issues with
>     In-the-
>     >    Network Tunneling [RFC4459]... "
>     >
>     > It seems that the only missing thing in the IP-in-UDP draft is
>     to allow the outer
>     > fragmentation. However, as it said in
>     >
>     (https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02#page-13),
>     " ...IPsec
>     > performs only Outer Fragmentation; this distinguishes it from
>     IP-in-IP, which
>     > performs only Inner Fragmentation. " Note that IP-in-IP is the
>     dominant
>     > encapsulation choice within Softwires networks. In other words,
>     performing
>     > only inner fragmentation works very well in practice.
>     Furthermore, the outer
>     > fragmentation issue (e.g., reassembly cost for the egress) would
>     become even
>     > worse since the fragments of X-in-UDP packets are more likely to
>     be forwarded
>     > across different paths than those of X-in-IP and X-in-GRE
>     packets. Hence, I'm
>     > wondering whether it's worthwhile to support the outer
>     fragmentation on UDP
>     > encapsulated packets which seems useless in practice.
>     >
>     >     - signalling support (e.g., to test whether a tunnel is up or
>     >     to measure MTUs)
>     >
>     > I haven't found any description of this in both GRE/UDP and GUE.
>     Did you?
>     >
>     >     - support for robust ID fields (related to fragmentation,
>     >     e.g., to overcome the limits of IPv4 ID as per RFC 6864)
>     >
>     > I haven't found any description of this in both GRE/UDP and GUE.
>     Did you?
>     >
>     > Xiaohu
>     >
>     > > It is not our obligation to find a way for your document to
>     proceed -
>     > > that onus is on you.
>     > >
>     > > Joe
>


--------------030502040200010703010909
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <br>
    <div class="moz-cite-prefix">On 6/11/2016 10:11 PM, Lloyd Wood
      wrote:<br>
    </div>
    <blockquote
      cite="mid:974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com"
      type="cite"><!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
      <style type="text/css" scoped=""> blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; } </style>
      Fragmentation should be strongly discouraged.</blockquote>
    <br>
    Avoided where possible for sure.<br>
    <blockquote
      cite="mid:974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com"
      type="cite">
      <div><br>
      </div>
      <div>if you've designed a tunnelling solution and you have
        fragmentation happening as a matter of course, you've designed
        it wrong. <br>
      </div>
    </blockquote>
    <br>
    If you have a solution that recurses (X over X, with some
    intervening layers or not), and X has a required minimum message
    size, then you either have a solution that - in at least some
    non-trivial situations - will fragment as a matter of course or a
    fantasy that cannot exist.<br>
    <br>
    The only reason we avoid this in typical operation is by avoiding X
    over X. Once you have a tunnel, that might not be avoidable (or even
    detectable, depending on encryption).<br>
    <br>
    Joe<br>
    <br>
    <blockquote
      cite="mid:974977917.2492241.1465708308527.JavaMail.yahoo@mail.yahoo.com"
      type="cite">
      <div><br>
        Lloyd Wood
        <div><a class="moz-txt-link-abbreviated" href="mailto:lloyd.wood@yahoo.co.uk">lloyd.wood@yahoo.co.uk</a></div>
        <br>
        <p class="yahoo-quoted-begin" style="font-size: 15px; color:
          #715FFA; padding-top: 15px; margin-top: 0">On Friday, May 27,
          2016, 8:10 PM, Xuxiaohu <a class="moz-txt-link-rfc2396E" href="mailto:xuxiaohu@huawei.com">&lt;xuxiaohu@huawei.com&gt;</a> wrote:</p>
        <blockquote class="iosymail">
          <div id="msgSandbox_AMhLyAoAAG2BnV0gc2BwILcOkyXZc_TEXT"
            class="msgSandbox" style="padding: 1.5em 0.5em 0.5em 1.2em;
            word-wrap: break-word;">&lt;Note that I have changed the
            subject of the email hence it has nothing to do with the WG
            adoption call now. It's just a discussion on a particular
            issue which is related to those WGs which are working on UDP
            tunnels. The reason for containing the old email is to use
            it as a background which may be useful for better
            understanding of this particular issue&gt;<br>
            <br>
            The possible side-effect of performing fragmentation on UDP
            encapsulated packets is to worsen the reassembly burden on
            tunnel egress since fragments of UDP encapsulated packets
            are more likely to be forwarded across different paths
            towards the tunnel egress than those of IP or GRE
            encapsulated packets.<br>
            <br>
            It seems that most X-over-UDP proposals choose to prohibit
            the tunnel ingress from performing fragmentation on UDP
            encapsulated packets. See the following quoted text
            regarding fragmentation from those X-over-UDP drafts:<br>
            <br>
            LISP:<br>
            <br>
            When an ITR receives a packet from a site-facing interface
            and adds H<br>
              octets worth of encapsulation to yield a packet size
            greater than L<br>
              octets, it resolves the MTU issue by first splitting the
            original<br>
              packet into 2 equal-sized fragments.  A LISP header is
            then prepended<br>
              to each fragment.<br>
            <br>
            VXLAN:<br>
            <br>
            VTEPs MUST NOT fragment VXLAN packets.  Intermediate routers
            may<br>
              fragment encapsulated VXLAN packets due to the larger
            frame size.<br>
              The destination VTEP MAY silently discard such VXLAN
            fragments.<br>
            <br>
            VXLAN-GPE:<br>
            <br>
            VTEPs MUST never fragment an encapsulated VXLAN GPE packet,
            and when<br>
              the outer IP header is IPv4, VTEPs MUST set the DF bit in
            the outer<br>
              IPv4 header.<br>
            <br>
            GEVENE:<br>
            <br>
              To prevent fragmentation and maximize performance, the
            best practice<br>
              when using Geneve is to ensure that the MTU of the
            physical network<br>
              is greater than or equal to the MTU of the encapsulated
            network plus<br>
              tunnel headers.<br>
            <br>
            GUE:<br>
            <br>
                If a packet is fragmented before encapsulation in GUE,
            all the<br>
                related fragments must be encapsulated using the same
            source port<br>
                (inner flow identifier). An operator may set MTU to
            account for<br>
                encapsulation overhead and reduce the likelihood of
            fragmentation.<br>
            <br>
            GRE/UDP<br>
            <br>
            Regarding packet fragmentation, an encapsulator/decapsulator
            SHOULD<br>
              be compliant with [RFC7588] and perform fragmentation
            before the<br>
              encapsulation.<br>
            <br>
            However, the above choice seems conflict with the
            requirements as described in <a moz-do-not-send="true"
              href="https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02"
              target="_blank">https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02</a><br>
            <br>
            <br>
            I wonder whether the IETF should reach a consensus on
            whether or not the fragmentation on UDP encapsulated packets
            should be allowed.<br>
              <br>
            Best regards,<br>
            Xiaohu<br>
            <br>
            &gt; -----Original Message-----<br>
            &gt; From: Xuxiaohu<br>
            &gt; Sent: Thursday, May 26, 2016 4:35 PM<br>
            &gt; To: 'Joe Touch'; Fred Baker (fred); Wassim Haddad<br>
            &gt; Cc: <a moz-do-not-send="true"
              ymailto="mailto:int-area@ietf.org"
              href="javascript:return">int-area@ietf.org</a><br>
            &gt; Subject: RE: [Int-area] Call for adoption of
            draft-xu-intarea-ip-in-udp-03<br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; &gt; -----Original Message-----<br>
            &gt; &gt; From: Joe Touch [mailto:<a moz-do-not-send="true"
              ymailto="mailto:touch@isi.edu" href="javascript:return">touch@isi.edu</a>]<br>
            &gt; &gt; Sent: Thursday, May 26, 2016 2:11 AM<br>
            &gt; &gt; To: Xuxiaohu; Fred Baker (fred); Wassim Haddad<br>
            &gt; &gt; Cc: <a moz-do-not-send="true"
              ymailto="mailto:int-area@ietf.org"
              href="javascript:return">int-area@ietf.org</a><br>
            &gt; &gt; Subject: Re: [Int-area] Call for adoption of<br>
            &gt; &gt; draft-xu-intarea-ip-in-udp-03<br>
            &gt; &gt;<br>
            &gt; &gt;<br>
            &gt; &gt;<br>
            &gt; &gt; On 5/24/2016 7:24 PM, Xuxiaohu wrote:<br>
            &gt; &gt; &gt; Hi Joe,<br>
            &gt; &gt; &gt;<br>
            &gt; &gt; &gt; I wonder whether you want to tell me the
            following truth by the<br>
            &gt; &gt; &gt; example that you gave: no matter whatever
            improvements we had done<br>
            &gt; &gt; &gt; with this draft, those persons who dislike it
            by the light of nature<br>
            &gt; &gt; &gt; would dislike it in the end.<br>
            &gt; &gt;<br>
            &gt; &gt; The only improvements that would make this doc
            useful would be to add<br>
            &gt; &gt; capabilities already in GRE/UDP or GUE/UDP, which
            we already have.<br>
            &gt; <br>
            &gt; Let's go over the four things you mentioned earlier in
            GRE/UDP and GUE/UDP:<br>
            &gt; <br>
            &gt;     - stronger checksums<br>
            &gt; <br>
            &gt; In GRE/UDP, in order to use UDP-zero-checksum, it gave
            the following<br>
            &gt; restrictions:<br>
            &gt; " 6. UDP Checksum Handling<br>
            &gt; <br>
            &gt;    6.1. UDP Checksum with IPv4<br>
            &gt; <br>
            &gt;    For UDP in IPv4, the UDP checksum MUST be processed
            as specified in<br>
            &gt;    [RFC768] and [RFC1122] for both transmit and
            receive. The IPv4<br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; Yong, Crabber, Xu, Herbert                             
                  [Page 12]<br>
            &gt;
--------------------------------------------------------------------------------<br>
            &gt; <br>
            &gt; Internet-Draft          GRE-in-UDP Encapsulation       
                March 2016<br>
            &gt; <br>
            &gt;    header includes a checksum which protects against
            mis-delivery of<br>
            &gt;    the packet due to corruption of IP addresses. The
            UDP checksum<br>
            &gt;    potentially provides protection against corruption
            of the UDP header,<br>
            &gt;    GRE header, and GRE payload. Disabling the use of
            checksums is a<br>
            &gt;    deployment consideration that should take into
            account the risk and<br>
            &gt;    effects of packet corruption.<br>
            &gt; <br>
            &gt;    When a decapsulator receives a packet, the UDP
            checksum field MUST<br>
            &gt;    be processed. If the UDP checksum is non-zero, the
            decapsulator MUST<br>
            &gt;    verify the checksum before accepting the packet. By
            default a<br>
            &gt;    decapsulator SHOULD accept UDP packets with a zero
            checksum. A node<br>
            &gt;    MAY be configured to disallow zero checksums per
            [RFC1122]; this may<br>
            &gt;    be done selectively, for instance disallowing zero
            checksums from<br>
            &gt;    certain hosts that are known to be sending over
            paths subject to<br>
            &gt;    packet corruption. If verification of a non-zero
            checksum fails, a<br>
            &gt;    decapsulator lacks the capability to verify a
            non-zero checksum, or<br>
            &gt;    a packet with a zero-checksum was received and the
            decapsulator is<br>
            &gt;    configured to disallow, the packet MUST be dropped
            and an event MAY<br>
            &gt;    be logged.<br>
            &gt; <br>
            &gt;    6.2. UDP Checksum with IPv6<br>
            &gt; <br>
            &gt;    For UDP in IPv6, the UDP checksum MUST be processed
            as specified in<br>
            &gt;    [RFC768] and [RFC2460] for both transmit and
            receive.<br>
            &gt; <br>
            &gt;    When UDP is used over IPv6, the UDP checksum is
            relied upon to<br>
            &gt;    protect both the IPv6 and UDP headers from
            corruption. As such, A<br>
            &gt;    default GRE-in-UDP Tunnel MUST perform UDP checksum;
            A TMCE GRE-in-<br>
            &gt;    UDP Tunnel MAY be configured with the UDP
            zero-checksum mode if the<br>
            &gt;    traffic-managed controlled environment or a set of
            closely<br>
            &gt;    cooperating traffic-managed controlled environments
            (such as by<br>
            &gt;    network operators who have agreed to work together
            in order to<br>
            &gt;    jointly provide specific services) meet at least one
            of following<br>
            &gt;    conditions:<br>
            &gt; <br>
            &gt;    a. It is known (perhaps through knowledge of
            equipment types and<br>
            &gt;      lower layer checks) that packet corruption is
            exceptionally<br>
            &gt;      unlikely and where the operator is willing to take
            the risk of<br>
            &gt;      undetected packet corruption.<br>
            &gt; <br>
            &gt;    b. It is judged through observational measurements
            (perhaps of<br>
            &gt;      historic or current traffic flows that use a
            non-zero checksum)<br>
            &gt;      that the level of packet corruption is tolerably
            low and where<br>
            &gt;      the operator is willing to take the risk of
            undetected packet<br>
            &gt;      corruption.<br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; Yong, Crabber, Xu, Herbert                             
                  [Page 13]<br>
            &gt;
--------------------------------------------------------------------------------<br>
            &gt; <br>
            &gt; Internet-Draft          GRE-in-UDP Encapsulation       
                March 2016<br>
            &gt; <br>
            &gt;    c. Carrying applications that are tolerant of
            mis-delivered or<br>
            &gt;      corrupted packets (perhaps through higher layer
            checksum,<br>
            &gt;      validation, and retransmission or transmission
            redundancy) where<br>
            &gt;      the operator is willing to rely on the
            applications using the<br>
            &gt;      tunnel to survive any corrupt packets.<br>
            &gt; <br>
            &gt;    The following requirements apply to a TMCE
            GRE-in-UDP tunnel that<br>
            &gt;    use UDP zero-checksum mode:<br>
            &gt; <br>
            &gt;      a. Use of the UDP checksum with IPv6 MUST be the
            default<br>
            &gt;        configuration of all GRE-in-UDP tunnels.<br>
            &gt; <br>
            &gt;      b. The GRE-in-UDP tunnel implementation MUST
            comply with all<br>
            &gt;        requirements specified in Section 4 of [RFC6936]
            and with<br>
            &gt;        requirement 1 specified in Section 5 of
            [RFC6936].<br>
            &gt; <br>
            &gt;      c. The tunnel decapsulator SHOULD only allow the
            use of UDP zero-<br>
            &gt;        checksum mode for IPv6 on a single received UDP
            Destination<br>
            &gt;        Port regardless of the encapsulator. The
            motivation for this<br>
            &gt;        requirement is possible corruption of the UDP
            Destination Port,<br>
            &gt;        which may cause packet delivery to the wrong UDP
            port. If that<br>
            &gt;        other UDP port requires the UDP checksum, the
            mis-delivered<br>
            &gt;        packet will be discarded.<br>
            &gt; <br>
            &gt;      d. It is RECOMMENDED that the UDP zero-checksum
            mode for IPv6 is<br>
            &gt;        only enabled for certain selected source
            addresses. The tunnel<br>
            &gt;        decapsulator MUST check that the source and
            destination IPv6<br>
            &gt;        addresses are valid for the GRE-in-UDP tunnel on
            which the<br>
            &gt;        packet was received if that tunnel uses UDP
            zero-checksum mode<br>
            &gt;        and discard any packet for which this check
            fails.<br>
            &gt; <br>
            &gt;      e. The tunnel encapsulator SHOULD use different
            IPv6 addresses for<br>
            &gt;        each GRE-in-UDP tunnel that uses UDP
            zero-checksum mode<br>
            &gt;        regardless of the decapsulator in order to
            strengthen the<br>
            &gt;        decapsulator's check of the IPv6 source address
            (i.e., the same<br>
            &gt;        IPv6 source address SHOULD NOT be used with more
            than one IPv6<br>
            &gt;        destination address, independent of whether that
            destination<br>
            &gt;        address is a unicast or multicast address). When
            this is not<br>
            &gt;        possible, it is RECOMMENDED to use each source
            IPv6 address for<br>
            &gt;        as few UDP zero-checksum mode GRE-in-UDP tunnels
            as is feasible.<br>
            &gt; <br>
            &gt;      f. When any middlebox exists on the path of a
            GRE-in-UDP tunnel,<br>
            &gt;        it is RECOMMENDED to use the default mode, i.e.
            use UDP<br>
            &gt;        checksum, to reduce the chance that the
            encapsulated packets to<br>
            &gt;        be dropped.<br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; Yong, Crabber, Xu, Herbert                             
                  [Page 14]<br>
            &gt;
--------------------------------------------------------------------------------<br>
            &gt; <br>
            &gt; Internet-Draft          GRE-in-UDP Encapsulation       
                March 2016<br>
            &gt; <br>
            &gt;      g. Any middlebox that allows the UDP zero-checksum
            mode for IPv6<br>
            &gt;        MUST comply with requirement 1 and 8-10 in
            Section 5 of<br>
            &gt;        [RFC6936].<br>
            &gt; <br>
            &gt;      h. Measures SHOULD be taken to prevent IPv6
            traffic with zero UDP<br>
            &gt;        checksums from "escaping" to the general
            Internet; see Section<br>
            &gt;        8 for examples of such measures.<br>
            &gt; <br>
            &gt;      i. IPv6 traffic with zero UDP checksums MUST be
            actively monitored<br>
            &gt;        for errors by the network operator. For example,
            the operator<br>
            &gt;        may monitor Ethernet layer packet error rates.<br>
            &gt; <br>
            &gt;      j. If a packet with a non-zero checksum is
            received, the checksum<br>
            &gt;        MUST be verified before accepting the packet.
            This is<br>
            &gt;        regardless of whether the tunnel encapsulator
            and decapsulator<br>
            &gt;        have been configured with UDP zero-checksum
            mode.<br>
            &gt; <br>
            &gt;    The above requirements do not change either the
            requirements<br>
            &gt;    specified in [RFC2460] as modified by [RFC6935] or
            the requirements<br>
            &gt;    specified in [RFC6936].<br>
            &gt; <br>
            &gt;    The requirement to check the source IPv6 address in
            addition to the<br>
            &gt;    destination IPv6 address, plus the strong
            recommendation against<br>
            &gt;    reuse of source IPv6 addresses among GRE-in-UDP
            tunnels collectively<br>
            &gt;    provide some mitigation for the absence of UDP
            checksum coverage of<br>
            &gt;    the IPv6 header. A traffic-managed controlled
            environment that<br>
            &gt;    satisfies at least one of three conditions listed
            above in this<br>
            &gt;    section provides additional assurance.<br>
            &gt; <br>
            &gt;    A GRE-in-UDP tunnel is suitable for transmission
            over lower layers<br>
            &gt;    in the traffic-managed controlled environments that
            are allowed by<br>
            &gt;    the exceptions stated above and the rate of
            corruption of the inner<br>
            &gt;    IP packet on such networks is not expected to
            increase by comparison<br>
            &gt;    to GRE traffic that is not encapsulated in UDP.  For
            these reasons,<br>
            &gt;    GRE-in-UDP does not provide an additional integrity
            check except<br>
            &gt;    when GRE checksum is used when UDP zero-checksum
            mode is used with<br>
            &gt;    IPv6, and this design is in accordance with
            requirements 2, 3 and 5<br>
            &gt;    specified in Section 5 of [RFC6936].<br>
            &gt; <br>
            &gt;    Generic Router Encapsulation (GRE) does not
            accumulate incorrect<br>
            &gt;    state as a consequence of GRE header corruption. A
            corrupt GRE<br>
            &gt;    packet may result in either packet discard or
            forwarding of the<br>
            &gt;    packet without accumulation of GRE state. Active
            monitoring of GRE-<br>
            &gt;    in-UDP traffic for errors is REQUIRED as occurrence
            of errors will<br>
            &gt;    result in some accumulation of error information
            outside the<br>
            &gt;    protocol for operational and management purposes.
            This design is in<br>
            &gt;    accordance with requirement 4 specified in Section 5
            of [RFC6936].<br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; Yong, Crabber, Xu, Herbert                             
                  [Page 15]<br>
            &gt;
--------------------------------------------------------------------------------<br>
            &gt; <br>
            &gt; Internet-Draft          GRE-in-UDP Encapsulation       
                March 2016<br>
            &gt; <br>
            &gt;    The remaining requirements specified in Section 5 of
            [RFC6936] are<br>
            &gt;    not applicable to GRE-in-UDP.  Requirements 6 and 7
            do not apply<br>
            &gt;    because GRE does not include a control feedback
            mechanism.<br>
            &gt;    Requirements 8-10 are middlebox requirements that do
            not apply to<br>
            &gt;    GRE-in-UDP tunnel endpoints (see Section 7.1 for
            further middlebox<br>
            &gt;    discussion).<br>
            &gt; <br>
            &gt;    It is worth mentioning that the use of a zero UDP
            checksum should<br>
            &gt;    present the equivalent risk of undetected packet
            corruption when<br>
            &gt;    sending similar packet using GRE-in-IPv6 without UDP
            [RFC7676] and<br>
            &gt;    without GRE checksums.<br>
            &gt; <br>
            &gt;    In summary, a TMCE GRE-in-UDP Tunnel is allowed to
            use UDP-zero-<br>
            &gt;    checksum mode for IPv6 when the conditions and
            requirements stated<br>
            &gt;    above are met. Otherwise the UDP checksum need to be
            used for IPv6<br>
            &gt;    as specified in [RFC768] and [RFC2460]. Use of GRE
            checksum is<br>
            &gt;    RECOMMENED when the UDP checksum is not used.<br>
            &gt; "<br>
            &gt; <br>
            &gt; In GUE, to support UDP-checksum-zero, it said<br>
            &gt; <br>
            &gt; " Therefore, when GUE is used over<br>
            &gt;    IPv6, either the UDP checksum must be enabled or the
            GUE header<br>
            &gt;    checksum must be used.  An encapsulator MAY set a
            zero UDP checksum<br>
            &gt;    for performance or implementation reasons, in which
            case the GUE<br>
            &gt;    header checksum MUST be used or applicable
            requirements for using<br>
            &gt;    zero UDP checksums in [GREUDP] MUST be met. If the
            UDP checksum is<br>
            &gt;    enabled, then the GUE header checksum should not be
            used since it is<br>
            &gt;    mostly redundant."<br>
            &gt; <br>
            &gt; It's easy for me to add the similar words to the
            IP-in-UDP draft like "the<br>
            &gt; applicable requirements for using zero UDP checksum in
            [GREUDP] MUST be<br>
            &gt; met when zero UDP checksum is used by the tunnel
            ingress". However, the<br>
            &gt; major goal for disabling the UDP checksum is to improve
            the performance.<br>
            &gt; When GUE header checksum is used and/or the bunch of
            applicable<br>
            &gt; requirements as described in GRE/UDP are verified, is
            the goal of improving<br>
            &gt; performance still achievable? If not, why not directly
            enable the UDP-checksum<br>
            &gt; instead?<br>
            &gt; <br>
            &gt;     - fragmentation support<br>
            &gt; <br>
            &gt; In GRE/UDP, it said<br>
            &gt; <br>
            &gt; " 4.1. MTU and Fragmentation<br>
            &gt; <br>
            &gt;    Regarding packet fragmentation, an
            encapsulator/decapsulator SHOULD<br>
            &gt;    be compliant with [RFC7588] and perform
            fragmentation before the<br>
            &gt;    encapsulation. The size of fragments SHOULD be less
            or equal to the<br>
            &gt;    PMTU associated with the path between the GRE
            ingress and the GRE<br>
            &gt;    egress tunnel endpoints minus the GRE and UDP
            overhead ..."<br>
            &gt; <br>
            &gt; in GUE, it said<br>
            &gt; <br>
            &gt; " 4.9. MTU and fragmentation<br>
            &gt; <br>
            &gt;    Standard conventions for handling of MTU (Maximum
            Transmission Unit)<br>
            &gt;    and fragmentation in conjunction with networking
            tunnels<br>
            &gt;    (encapsulation of layer 2 or layer 3 packets) should
            be followed.<br>
            &gt;    Details are described in MTU and Fragmentation
            Issues with In-the-<br>
            &gt;    Network Tunneling [RFC4459]... "<br>
            &gt; <br>
            &gt; It seems that the only missing thing in the IP-in-UDP
            draft is to allow the outer<br>
            &gt; fragmentation. However, as it said in<br>
            &gt; (<a moz-do-not-send="true"
              href="https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02#page-13"
              target="_blank">https://tools.ietf.org/html/draft-ietf-intarea-tunnels-02#page-13</a>),
            " ...IPsec<br>
            &gt; performs only Outer Fragmentation; this distinguishes
            it from IP-in-IP, which<br>
            &gt; performs only Inner Fragmentation. " Note that IP-in-IP
            is the dominant<br>
            &gt; encapsulation choice within Softwires networks. In
            other words, performing<br>
            &gt; only inner fragmentation works very well in practice.
            Furthermore, the outer<br>
            &gt; fragmentation issue (e.g., reassembly cost for the
            egress) would become even<br>
            &gt; worse since the fragments of X-in-UDP packets are more
            likely to be forwarded<br>
            &gt; across different paths than those of X-in-IP and
            X-in-GRE packets. Hence, I'm<br>
            &gt; wondering whether it's worthwhile to support the outer
            fragmentation on UDP<br>
            &gt; encapsulated packets which seems useless in practice.<br>
            &gt; <br>
            &gt;     - signalling support (e.g., to test whether a
            tunnel is up or<br>
            &gt;     to measure MTUs)<br>
            &gt; <br>
            &gt; I haven't found any description of this in both GRE/UDP
            and GUE. Did you?<br>
            &gt; <br>
            &gt;     - support for robust ID fields (related to
            fragmentation,<br>
            &gt;     e.g., to overcome the limits of IPv4 ID as per RFC
            6864)<br>
            &gt; <br>
            &gt; I haven't found any description of this in both GRE/UDP
            and GUE. Did you?<br>
            &gt; <br>
            &gt; Xiaohu<br>
            &gt; <br>
            &gt; &gt; It is not our obligation to find a way for your
            document to proceed -<br>
            &gt; &gt; that onus is on you.<br>
            &gt; &gt;<br>
            &gt; &gt; Joe<br>
          </div>
          <blockquote> </blockquote>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------030502040200010703010909--


From nobody Wed Jun 15 15:21:55 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE5F12D843; Wed, 15 Jun 2016 15:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.628
X-Spam-Level: 
X-Spam-Status: No, score=-105.628 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 iL2zxO1vmIEO; Wed, 15 Jun 2016 15:21:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EA3A12DC15; Wed, 15 Jun 2016 15:21:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8FBB4B812B5; Wed, 15 Jun 2016 15:21:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160615222139.8FBB4B812B5@rfc-editor.org>
Date: Wed, 15 Jun 2016 15:21:39 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/r5qfw7Zu16axwVqJ2TCdUoqHmOE>
Cc: softwires@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [Softwires] RFC 7870 on Dual-Stack Lite (DS-Lite) Management Information Base (MIB) for Address Family Transition Routers (AFTRs)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 22:21:47 -0000

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

        
        RFC 7870

        Title:      Dual-Stack Lite (DS-Lite) Management Information 
                    Base (MIB) for Address Family Transition 
                    Routers (AFTRs) 
        Author:     Y. Fu, S. Jiang,
                    J. Dong, Y. Chen
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2016
        Mailbox:    fuyu@cnnic.cn, 
                    jiangsheng@huawei.com, 
                    knight.dongjiang@gmail.com,
                    flashfoxmx@gmail.com
        Pages:      27
        Characters: 53247
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-dslite-mib-15.txt

        URL:        https://www.rfc-editor.org/info/rfc7870

        DOI:        http://dx.doi.org/10.17487/RFC7870

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines managed objects for Address Family
Transition Routers (AFTRs) of Dual-Stack Lite (DS-Lite).

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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


The RFC Editor Team
Association Management Solutions, LLC



From nobody Fri Jun 17 02:22:11 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B02A112B034; Fri, 17 Jun 2016 02:22:06 -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: 6.22.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160617092206.19092.51001.idtracker@ietfa.amsl.com>
Date: Fri, 17 Jun 2016 02:22:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/DNSmgX-Ao-JMlzb-dCneNjDg-6U>
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-map-mib-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2016 09:22:07 -0000

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

        Title           : Definitions of Managed Objects for MAP-E
        Authors         : Yu Fu
                          Sheng Jiang
                          Bing Liu
                          Jiang Dong
                          Yuchi Chen
	Filename        : draft-ietf-softwire-map-mib-06.txt
	Pages           : 15
	Date            : 2016-06-17

Abstract:
   This memo defines a portion of the Management Information Base (MIB)
   for using with network management protocols in the Internet
   community.  In particular, it defines managed objects for MAP
   encapsulation (MAP-E) mode.


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

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-mib-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 Fri Jun 17 02:39:21 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C9B12B059; Fri, 17 Jun 2016 02:39:17 -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: 6.22.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160617093917.19171.95998.idtracker@ietfa.amsl.com>
Date: Fri, 17 Jun 2016 02:39:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/ulOK9FAOfLL7ZjiIAuxiwTgclAQ>
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-map-radius-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2016 09:39:17 -0000

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

        Title           : RADIUS Attribute for MAP
        Authors         : Sheng Jiang
                          Yu Fu
                          Bing Liu
                          Peter Deacon
                          Chongfeng Xie
                          Tianxiang Li
	Filename        : draft-ietf-softwire-map-radius-06.txt
	Pages           : 20
	Date            : 2016-06-17

Abstract:
   IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6
   connectivity services simultaneously during the IPv4/IPv6 co-existing
   period.  The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
   options have been defined to configure Customer Edge (CE) in MAP-E,
   MAP-T, and Lightweight 4over6.  However, in many networks, the
   configuration information may be stored in Authentication
   Authorization and Accounting (AAA) servers while user configuration
   is mainly from Broadband Network Gateway (BNG) through DHCPv6
   protocol.  This document defines a Remote Authentication Dial In User
   Service (RADIUS) attribute that carries CE configuration information
   from AAA server to BNG.


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

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-radius-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 Fri Jun 17 03:02:13 2016
Return-Path: <fuyu@cnnic.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9354B12B05F for <softwires@ietfa.amsl.com>; Fri, 17 Jun 2016 03:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.317
X-Spam-Level: 
X-Spam-Status: No, score=-3.317 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=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 3EY242zkL9zT for <softwires@ietfa.amsl.com>; Fri, 17 Jun 2016 03:02:08 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0E512B04C for <softwires@ietf.org>; Fri, 17 Jun 2016 03:02:01 -0700 (PDT)
Received: from LIUXD (unknown [218.241.103.86]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0Dp8EyXymNXhAreCQ--.57877S3;  Fri, 17 Jun 2016 18:01:59 +0800 (CST)
From: "Yu Fu" <fuyu@cnnic.cn>
To: <softwires@ietf.org>
Date: Fri, 17 Jun 2016 18:02:03 +0800
Message-ID: <008301d1c87f$4c985af0$e5c910d0$@cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0084_01D1C8C2.5ABB9AF0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdHIf0wciNEi8P75QuaayAaXOwRuzg==
Content-Language: zh-cn
X-CM-TRANSID: AQAAf0Dp8EyXymNXhAreCQ--.57877S3
X-Coremail-Antispam: 1UD129KBjvJXoWxury5Zw45trW8Zw47urWfKrg_yoW5Ar43pa yfZ3W3Gw1xJr1kG3ykGr1ruw1vv3s5ArWfAFnxGr10vayUA3Wvyr1v9F95ArZrXrZ8Gr4j vr4Y934Ygan5XrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUQab7Iv0xC_Zr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4 A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG67k08I80 eVWrJVW7JwAqx4xG6c804VAFz4xC04v7Mc02F40Ew4AK048IF2xKxVWUJVW8JwAqx4xG6x AIxVCFxsxG0wAqx4xG6I80eVA0xI0YY7vIx2IE14AGzxvEb7x7McIj6xIIjxv20xvE14v2 6r106r15McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2 Ij64vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxkIecxEwVAFwVW8twCF04k20xvY0x0EwIxG rwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r106r1rMI8I3I0E7480Y4 vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jr0_JrylIxkGc2Ij64vIr41lIxAIcVC0I7IY x2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26c xKx2IYs7xG6rWUJVWrZr1UMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7Cj xVAFwI0_Gr0_Gr1UYxBIdaVFxhVjvjDU0xZFpf9x07jwyCJUUUUU=
X-CM-SenderInfo: pix13q5fqqxugofq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/2c7wVeTgoUehPC_plwRiiYssrCI>
Subject: [Softwires] FW: I-D Action: draft-ietf-softwire-map-radius-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2016 10:02:12 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0084_01D1C8C2.5ABB9AF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all, 

 

As I had a presentation on IETF 94 meeting for
draft-ietf-softwire-map-radius-05, the softwire WG had a conclusion that
this draft should have the radius configuration solutions for MAP-E, MAP-T,
Lightweight4o6 all together in one draft as DHCP does. Please refer to the
minutes of the IETF 94 meeting as below: 

https://www.ietf.org/proceedings/94/minutes/minutes-94-softwire

 

So we had a discussion with the authors of the
draft-sun-softwire-lw4over6-radext-01. We have merged
draft-ietf-softwire-map-radius-05 and draft-sun-softwire-lw4over6-radext-01
into draft-ietf-softwire-map-radius-06.

 

Your comments are appreciated for us.

Thanks 

Yu

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

Yu Fu

fuyu@cnnic.cn

 

 

 

-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of internet-drafts@ietf.org
Sent: Friday, June 17, 2016 5:39 PM
To: i-d-announce@ietf.org
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-map-radius-06.txt

 

 

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

This draft is a work item of the Softwires of the IETF.

 

        Title           : RADIUS Attribute for MAP

        Authors         : Sheng Jiang

                          Yu Fu

                          Bing Liu

                          Peter Deacon

                          Chongfeng Xie

                          Tianxiang Li

         Filename        : draft-ietf-softwire-map-radius-06.txt

         Pages           : 20

         Date            : 2016-06-17

 

Abstract:

   IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6

   connectivity services simultaneously during the IPv4/IPv6 co-existing

   period.  The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

   options have been defined to configure Customer Edge (CE) in MAP-E,

   MAP-T, and Lightweight 4over6.  However, in many networks, the

   configuration information may be stored in Authentication

   Authorization and Accounting (AAA) servers while user configuration

   is mainly from Broadband Network Gateway (BNG) through DHCPv6

   protocol.  This document defines a Remote Authentication Dial In User

   Service (RADIUS) attribute that carries CE configuration information

   from AAA server to BNG.

 

 

The IETF datatracker status page for this draft is:

 <https://datatracker.ietf.org/doc/draft-ietf-softwire-map-radius/>
https://datatracker.ietf.org/doc/draft-ietf-softwire-map-radius/

 

There's also a htmlized version available at:

 <https://tools.ietf.org/html/draft-ietf-softwire-map-radius-06>
https://tools.ietf.org/html/draft-ietf-softwire-map-radius-06

 

A diff from the previous version is available at:

 <https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-radius-06>
https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-radius-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/> ftp://ftp.ietf.org/internet-drafts/

 

_______________________________________________

Softwires mailing list

 <mailto:Softwires@ietf.org> Softwires@ietf.org

 <https://www.ietf.org/mailman/listinfo/softwires>
https://www.ietf.org/mailman/listinfo/softwires

 


------=_NextPart_000_0084_01D1C8C2.5ABB9AF0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoPlainText><span lang=3DEN-US>Hi all, =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>As I had a presentation on IETF 94 meeting for =
draft-ietf-softwire-map-radius-05, the softwire WG had a conclusion that =
this draft should have the radius configuration solutions for MAP-E, =
MAP-T, Lightweight4o6 all together in one draft as DHCP does. Please =
refer to the minutes of the IETF 94 meeting as below: =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US><a =
href=3D"https://www.ietf.org/proceedings/94/minutes/minutes-94-softwire">=
https://www.ietf.org/proceedings/94/minutes/minutes-94-softwire</a><o:p><=
/o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>So we had a discussion with the authors of the =
draft-sun-softwire-lw4over6-radext-01. We have merged =
draft-ietf-softwire-map-radius-05 and =
draft-sun-softwire-lw4over6-radext-01 into =
draft-ietf-softwire-map-radius-06.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Your comments are appreciated for =
us.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>Thanks =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Yu<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>-------------------------------------------<o:p></o:p></span=
></p><p class=3DMsoNormal><span lang=3DEN-US>Yu =
Fu<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>fuyu@cnnic.cn<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>-----Original =
Message-----<br>From: softwires-bounces@ietf.org =
[mailto:softwires-bounces@ietf.org] On Behalf Of =
internet-drafts@ietf.org<br>Sent: Friday, June 17, 2016 5:39 PM<br>To: =
i-d-announce@ietf.org<br>Cc: softwires@ietf.org<br>Subject: [Softwires] =
I-D Action: =
draft-ietf-softwire-map-radius-06.txt<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>A New Internet-Draft is =
available from the on-line Internet-Drafts =
directories.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>This draft is a work item of the Softwires of the =
IETF.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
RADIUS Attribute for MAP<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Authors&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Sheng =
Jiang<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; Yu Fu<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; Bing Liu<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; Peter Deacon<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; Chongfeng Xie<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; Tianxiang Li<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-ietf-softwire-map-radius-06.txt<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
20<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
2016-06-17<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Abstract:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; IPv4-over-IPv6 =
transition mechanisms provide both IPv4 and IPv6<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; connectivity =
services simultaneously during the IPv4/IPv6 =
co-existing<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; period.&nbsp; The Dynamic Host Configuration =
Protocol for IPv6 (DHCPv6)<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; options have been =
defined to configure Customer Edge (CE) in =
MAP-E,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; MAP-T, and Lightweight 4over6.&nbsp; However, =
in many networks, the<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; configuration information may be stored in =
Authentication<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; Authorization and Accounting (AAA) servers =
while user configuration<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; is mainly from =
Broadband Network Gateway (BNG) through DHCPv6<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; protocol.&nbsp; =
This document defines a Remote Authentication Dial In =
User<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; Service (RADIUS) attribute that carries CE =
configuration information<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; from AAA server to =
BNG.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>The IETF datatracker status page for this draft =
is:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-softwire-map-radius/"=
><span =
style=3D'color:windowtext;text-decoration:none'>https://datatracker.ietf.=
org/doc/draft-ietf-softwire-map-radius/</span></a><o:p></o:p></span></p><=
p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>There's also a htmlized version =
available at:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><a =
href=3D"https://tools.ietf.org/html/draft-ietf-softwire-map-radius-06"><s=
pan =
style=3D'color:windowtext;text-decoration:none'>https://tools.ietf.org/ht=
ml/draft-ietf-softwire-map-radius-06</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>A diff from the previous version =
is available at:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-map-radiu=
s-06"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/rfcd=
iff?url2=3Ddraft-ietf-softwire-map-radius-06</span></a><o:p></o:p></span>=
</p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>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.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Internet-Drafts are also available by anonymous FTP =
at:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><a =
href=3D"ftp://ftp.ietf.org/internet-drafts/"><span =
style=3D'color:windowtext;text-decoration:none'>ftp://ftp.ietf.org/intern=
et-drafts/</span></a><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>_______________________________________________<o:p></o:p></=
span></p><p class=3DMsoPlainText><span lang=3DEN-US>Softwires mailing =
list<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><a =
href=3D"mailto:Softwires@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>Softwires@ietf.org</span>=
</a><o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><a =
href=3D"https://www.ietf.org/mailman/listinfo/softwires"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/softwires</span></a><o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0084_01D1C8C2.5ABB9AF0--



From nobody Mon Jun 20 19:45:24 2016
Return-Path: <xmw@cernet.edu.cn>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A126B12D8A3; Mon, 20 Jun 2016 19:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.922
X-Spam-Level: 
X-Spam-Status: No, score=-0.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=no autolearn_force=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 hjV7AuQFXRPm; Mon, 20 Jun 2016 19:45:21 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp38.tsinghua.edu.cn [166.111.204.62]) by ietfa.amsl.com (Postfix) with ESMTP id 2686212D888; Mon, 20 Jun 2016 19:45:16 -0700 (PDT)
Received: from win7-PC (unknown [166.111.71.59]) by app1 (Coremail) with SMTP id CsxvpgDHzEAxqmhX+XyRAA--.29683S2; Tue, 21 Jun 2016 10:45:05 +0800 (CST)
Date: Tue, 21 Jun 2016 10:45:05 +0800
From: "=?utf-8?B?TWluZ3dlaSBYdQ==?=" <xmw@cernet.edu.cn>
To: "=?utf-8?B?SWFuIEZhcnJlcg==?=" <ianfarrer@gmx.com>, "=?utf-8?B?ZHJhZnQtaWV0Zi1zb2Z0d2lyZS1tZXNoLW11bHRpY2FzdA==?=" <draft-ietf-softwire-mesh-multicast@ietf.org>,  "=?utf-8?B?c29mdHdpcmVz?=" <softwires@ietf.org>
References: <B5E05CB1-D4ED-457C-B383-824A52C99650@gmx.com>
Message-ID: <201606211045044291264@cernet.edu.cn>
X-mailer: Foxmail 6, 15, 201, 26 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-CM-TRANSID: CsxvpgDHzEAxqmhX+XyRAA--.29683S2
X-Coremail-Antispam: 1UD129KBjvJXoW3Gr1Uuw45XF17Aw1rWF1rWFg_yoW3Zw4rpF Z8KFnFkr4kJrW8A3W8Aw1j9F1Fvw4fGF9rWFy5Jw1UZ398Wry0qry0939IqFsrGr4rAFyj vw4a9FW5XF1kZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUvvb7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_JFI_Gr1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_ Cr1l84ACjcxK6I8E87Iv67AKxVWxJVW8Jr1l84ACjcxK6I8E87Iv6xkF7I0E14v26r4UJV WxJr1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IEw4CE5I8CrVC2j2WlYx0E 2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJV W8JwACjcxG0xvY0x0EwIxGrwACjcxG0xvY0x0EwIxGrVCF72vEw4AK0wACY4xI67k04243 AVAKzVAKj4xxMxkIecxEwVAFwVW8JwCF04k20xvY0x0EwIxGrwC20s026c02F40E14v26r 1j6r18MI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij 64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr 0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI0_Gr0_Cr1l IxAIcVC2z280aVCY1x0267AKxVW8JVW8Jr1l6VACY4xI67k04243AbIYCTnIWIevJa73Uj IFyTuYvj7UU6GPUUUUU
X-CM-SenderInfo: x0pzquphuqv3oohg3hdfq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/5DLqtXuhhzCg1_1It5aP9VYUCsg>
Subject: Re: [Softwires] =?utf-8?q?Call_for_reviewers_draft-ietf-softwire-mesh?= =?utf-8?q?-multicast?=
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: xmw@cernet.edu.cn
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@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 Jun 2016 02:45:24 -0000

RGVhciBJYW4sDQoNClRoYW5rIHlvdSBmb3IgeW91ciBzdWdnZXN0aW9ucywgd2UgaGF2ZSBtb2Rp
ZmllZCB0aGUgZHJhZnQgYW5kIHBvc3RlZCBhIG5ldyB2ZXJzaW9uIGluIHRoZSBXRywgZHJhZnQt
aWV0Zi1zb2Z0d2lyZS1tZXNoLW11bHRpY2FzdC0xMy4gVGhlIGZvbGxvd2luZyBpcyB0aGUgcmVw
bHkgdG8gdGhlIHJldmlldyBzdWdnZXN0aW9ucy4NCg0KMS4gUGcgNSAtIHN0YXRlcyBhICdkdWFs
LXN0YWNrJyByb3V0ZXIuIFRoZSBBRkJSIGlzIG5vdCByZWFsbHkgZHVhbC1zdGFjayBoZXJlLiBJ
dCBoYXMgdHdvIHNpbmdsZSBzdGFjayBpbnRlcmZhY2VzIGFuZCBpbXBsZW1lbnRzIGEgdHJhbnNp
dGlvbiB0ZWNobm9sb2d5LiBTdWdnZXN0IHJlbW92YWwgb2YgZHVhbC1zdGFjay4NCg0KQW5zd2Vy
OiBXZSBoYXZlIHJlbW92ZWQgdGhlICdkdWFsLXN0YWNrJy4NCg0KMi4gU2VjdGlvbiA0LjENClRo
ZSB0cmFuc2xhdGlvbiBiZXR3ZWVuIHRoZSBJUHY0IGFuZCBJUHY2IFBJTSBtZXNzYWdlcyBzZWVt
cyB1bmRlcnNwZWNpZmllZC4gSXQgd291bGQgYmUgdXNlZnVsIHRvIHByb3ZpZGUgc29tZSBleGFt
cGxlcyBzaG93aW5nIGhvdyB0aGUgbmV3IGFkZHJlc3NlcyBhcmUgdXNlZCBpbiB0aGUgZGlmZmVy
ZW50IHRyYW5zbGF0aW9ucyBpbnRvIHRoZSBQSU0gbWVzc2FnZSBmb3JtYXRzIChSRkM3NzQxIFNl
Y3Rpb24gNC4xKS4NCg0KQW5zd2VyOiBXZSBoYXZlIGFkZGVkIHNvbWUgZXhhbXBsZXMgaW4gU2Vj
dGlvbiA4Lg0KDQozLiBTZWN0aW9uIDQuMg0KVGhlIHRlcm0g4oCYTVBSRUZJWDY04oCZIGlzIG5v
dCBkZWZpbmVkIGluIFJGQzczNzEuIEFzIHRoZXJlIGFyZSBhIG51bWJlciBvZiBkaWZmZXJlbnQg
Zm9ybWF0cyBmb3IgbXVsdGljYXN0IHByZWZpeGVzIGluIFJGQzczNzEsIGl0IHdvdWxkIGJlIHVz
ZWZ1bCB0byBwb2ludCB0byB0aGUgcmVsZXZhbnQgc2VjdGlvbiB0byBhdm9pZCBjb25mdXNpb24u
DQpXaHkgd2FzIHRoZSBuYW1lIE1QUkVGSVg2NCBjaG9zZW4gZm9yIDRpbjYgbXVsdGljYXN0PyBJ
biBvdGhlciBTb2Z0d2lyZSBkb2NzIChlLmcuIFJGQzc1OTgpLCDigJk0NuKAmSBpcyB1c2VkIHRv
IGRlbm90ZSA0IGluIDYgZnVuY3Rpb25zIGFuZCA2NCBmb3IgNiBpbiA0LiBBcyB0aGUgYWRkcmVz
c2luZyBhbmQgbWVjaGFuaXNtIGZvciA0aW42IGRpZmZlcnMgZm9yIDZpbjQsIGl0IHdvdWxkIG1h
a2Ugc2Vuc2UgdG8gZGlmZmVyZW50aWF0ZSB0aGlzIGluIHRoZSBuYW1pbmcgb2YgdGhlIGZpZWxk
cyAoaS5lLiB1c2UgTVBSRUZJWDQ2LCB1UHJlZml4NDYgZm9yIDRpbjYgYW5kIHVQcmVmaXg2NCBm
b3IgNmluNCkuDQoNCkFuc3dlcjogV2UgaGF2ZSByZW5hbWVkIHRoZW0sIHVzaW5nIHVQcmVmaXg0
NiwgdVByZWZpeDY0IGFuZCBtUHJlZml4NjQsIGFzIGRlbm90ZWQgaW4gU2VjdGlvbiAyLg0KDQo0
LiBTZWN0aW9uIDYuMw0KU2VjdGlvbiA2IG92ZXJhbGwgZGVmaW5lcyByZXF1aXJlbWVudHMgZm9y
IHRoZSBjb250cm9sIHBsYW5lLiBTZWN0aW9ucyA2LjEuIGFuZCA2LjIgYXJlIE1VU1QgcmVxdWly
ZW1lbnRzLiA2LjMgdXNlcyDigJhzaG91bGTigJkgaW4gZGVmaW5pbmcgdGhlIGJlaGF2aW91ci4g
Q2FuIHRoZSBtZWNoYW5pc20gd29yayB3aXRob3V0IGltcGxlbWVudGluZyBzZWMgNi4zIGFuZCBp
biB3aGljaCBzaXR1YXRpb25zIGlzIGl0IGFjY2VwdGFibGUgbm90IHRvPw0KDQpBbnN3ZXI6IE5v
LCB0aGUgbWVjaGFuaXNtIGNhbiBub3Qgd29yayB3aXRob3V0IGltcGxlbWVudGluZyBTZWMgNi4z
LiBXZSBoYXZlIGFscmVhZHkgY2hhbmdlZCB0aGUgJ3Nob3VsZCcgdG8gJ01VU1QnLiBUaGFuayB5
b3UgZm9yIHlvdXIgc3VnZ2VzdGlvbnMuDQoNCjUuIFNlY3Rpb24gNi41DQpUaGlzIGludHJvZHVj
ZXMgdGhlIGVuY2Fwc3VsYXRpb24gb2YgbWVzc2FnZXMsIGJ1dCBkb2VzbuKAmXQgcHJvdmlkZSBh
bnkgaW5mb3JtYXRpb24gYWJvdXQgd2hhdCB0eXBlIG9mIGVuY2Fwc3VsYXRpb24gaXMgdXNlZC4g
RmlndXJlIDcgc2hvd3MgVURQLiBJcyB0aGlzIHBhcnQgb2YgdGhlIGVuY2Fwc3VsYXRpb24/IEFz
IHRoaXMgaXMgbmVjZXNzYXJ5IGZvciB0aGUgbWVjaGFuaXNtIHRvIHdvcmsgYW5kIG5lZWRzIHRv
IGJlIGltcGxlbWVudGVkIG9uIHRoZSBBRkJScywgdGhlcmUgbmVlZHMgdG8gYmUgcmVmZXJlbmNl
cyBhbmQgcmVxdWlyZW1lbnRzIGxhbmd1YWdlIG9uIHdoYXQgbmVlZHMgdG8gYmUgaW1wbGVtZW50
ZWQuDQoNCkFuc3dlcjogSW4gU2VjdGlvbiA2LjUsIHdlIGhhdmUgYWRkZWQgc29tZSB3b3JkcyB0
byBpbGx1c3RyYXRlIHRoYXQgd2UgdGFrZSBVRFAgYXMgYW4gZXhhbXBsZSBmb3IgZW5jYXBzdWxh
dGlvbi4NCg0KNi4gU2VjdGlvbiA3LjINCkFyZSB0aGVyZSBvcHRpb25zIG9uIHRoZSBraW5kIG9m
IHR1bm5lbCBlbmNhcHN1bGF0aW9uIHRoYXQgY2FuIGJlIHVzZWQ/IEl0IHdvdWxkIGJlIHVzZWZ1
bCB0byBlbnVtZXJhdGUgc29tZSBvZiB0aGVzZSBhbmQgZm9yIGludGVyb3BlcmFiaWxpdHkgb25l
IG9mIHRoZW0gbmVlZHMgdG8gYmUgbWFuZGF0b3J5IHRvIGltcGxlbWVudC4NCg0KQW5zd2VyOiBX
ZSBoYXZlIGFkZGVkIGFuIHBhcmFncmFwaCBpbiBhIG5ldyBTZWN0aW9uIChTZWMuIDkpLCB0byBz
dGF0ZSB0aGF0IHRoZSBtZWNoYW5pc20gc2hvdWxkIGFjY29tbW9kYXRlIGEgdmFyaWV0eSBvZiBl
bmNhcHN1bGF0aW9uIG1lY2hhbmlzbSBtZW50aW9uZWQgaW4gUkZDIDQ5MjUgKFNlYyAzLjUpLg0K
DQo3LiBSZWZlcmVuY2VzDQpSRkMyMTE5IE5lZWRzIHRvIGhhdmUgYSBub3JtYXRpdmUgcmVmZXJl
bmNlDQpSRkM0NjAxIGhhcyBiZWVuIG9ic29sZXRlZCBieSBSRkM3NzYxDQoNCkFuc3dlcjogV2Ug
aGF2ZSBtb2RpZmllZCB0aGUgdGV4dC4NCg0KOC4gR2VuZXJhbCAtIA0KVGhlIGRvY3VtZW50IGRv
ZXNu4oCZdCBjb250YWluIHRoZSDigJhDb252ZW50aW9ucy9SZXF1aXJlbWVudHMgTGFuZ3VhZ2Xi
gJkgYm9pbGVycGxhdGUgcG9pbnRpbmcgdG8gUkZDMjExOSB0aGF0IG5lZWRzIHRvIGJlIGluIGEg
c3RhbmRhcmRzIHRyYWNrIGRvY3VtZW50LiAoVGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNUIE5P
VOKAnSwg4oCmKQ0KDQpBbnN3ZXI6IFdlIGhhdmUgY29udGFpbmVkIHRoZSDigJhDb252ZW50aW9u
cy9SZXF1aXJlbWVudHMgTGFuZ3VhZ2XigJkgYm9pbGVycGxhdGUgcG9pbnRpbmcgdG8gUkZDMjEx
OSBpbiB0aGUgbmV3IHZlcnNpb24uDQoNCjkuIFRoZSB1c2Ugb2YgUkZDMjExOSBsYW5ndWFnZSBh
bmQgdGhlIGNhc2Ugb2YgdGhlIHdvcmRzIHRocm91Z2hvdXQgdGhlIGRvY3VtZW50IGlzIG5vdCBj
b25zaXN0ZW50ICh0aGVyZSBhcmUgYSBudW1iZXIgb2YgbG93ZXIgY2FzZSDigJhtdXN04oCZIGV0
YywgdGhhdCBwcm9iYWJseSBzaG91bGQgYmUgdXBwZXJjYXNlKS4NClRoZSB0ZXJtIOKAmHNob3Vs
ZOKAmSAobG93ZXIgY2FzZSkgaXMgdXNlZCBpbiBhIG51bWJlciBvZiBwbGFjZXMgdGhhdCBtYWtl
IHRoZSBmdW5jdGlvbmFsaXR5IG9mIHRoZSBtZWNoYW5pc20gc2VlbSB1bmNlcnRhaW4gKGUuZy4g
RmlndXJlIDEgLSAnTXVsdGljYXN0IHBhY2tldHMgc2hvdWxkIGdldCBhY3Jvc3MgdGhlIEktSVAg
dHJhbnNpdCBjb3JlJy4gU2VjIDQuMSAnaXQgc2hvdWxkIGJlIHRyYW5zbGF0ZWQgYmFja+KAmSku
DQpUaGVyZSBhcmUgc29tZSBwb2ludHMgdGhhdCB3b3VsZCBzZWVtIHRvIG5lZWQgTVVTVCByZXF1
aXJlbWVudHMgdGhhdCBhcmUgbWlzc2luZyAtIGUuZy4gU2VjdGlvbiA0LjQgJ2V2ZXJ5IHVQcmVm
aXg2NCB0aGF0IEFGQlIgYW5ub3VuY2VzIHNob3VsZCBiZSBkaWZmZXJlbnQgZWl0aGVyLCBhbmQg
dW5pcXVlbHkgaWRlbnRpZmllcyBlYWNoIEFGQlLigJkuIElmIHR3byBBRkJScyBhcmUgYW5ub3Vu
Y2luZyB0aGUgc2FtZSB1UHJlZml4NjQsIHN1cmVseSB0aGVyZSB3aWxsIGJlIHByb2JsZW1zLg0K
U3VnZ2VzdCB0aGF0IHRoZSB1c2Ugb2YgUkZDMjExOSBsYW5ndWFnZSBpcyByZXZpc2VkIHRocm91
Z2hvdXQgdGhlIGRvY3VtZW50IHRvIGF2b2lkIHRoZXNlIHByb2JsZW1zIGFuZCB0byB0aWdodGVu
IHVwIHRoZSBzcGVjaWZpY2F0aW9uIGFzIGEgd2hvbGUuDQoNCkFuc3dlcjogV2UgcmV2aXNlZCB0
aHJvdWdob3V0IHRoZSBkb2N1bWVudCB0byBtYWtlIHRoZSDigJhDb252ZW50aW9ucy9SZXF1aXJl
bWVudHMnIHdvcmRzIGNvbnNpc3RlbnQuDQoNCjEwLiBUaGUgZG9jdW1lbnQgbmVlZHMgdGhlIGxh
bmd1YWdlIGFuZCBncmFtbWFyIGNoZWNraW5nIHRocm91Z2hvdXQuDQoNCkFuc3dlcjogV2UgaGF2
ZSBjaGVja2VkIHRocm91Z2hvdXQgdGhlIGRvY3VtZW50IGFuZCByZS1lZGl0ZWQgdGhlIGxhbmd1
YWdlIGFuZCBncmFtbWFyLg0KDQoNCkJlc3QgcmVnYXJkcywNCg0KTWluZ3dlaQ0KDQoNCg0K5Y+R
5Lu25Lq677yaIElhbiBGYXJyZXIgDQrlj5HpgIHml7bpl7TvvJogMjAxNi0wNC0yMCAgMDM6NTM6
MTMgDQrmlLbku7bkurrvvJogZHJhZnQtaWV0Zi1zb2Z0d2lyZS1tZXNoLW11bHRpY2FzdDsgc29m
dHdpcmVzIA0K5oqE6YCB77yaIA0K5Li76aKY77yaIFJlOiBbU29mdHdpcmVzXSBDYWxsIGZvciBy
ZXZpZXdlcnMgZHJhZnQtaWV0Zi1zb2Z0d2lyZS1tZXNoLW11bHRpY2FzdCANCkhpLA0KDQoNCkhl
cmUgaXMgbXkgcmV2aWV3IG9mIHRoZSBkcmFmdC4NCg0KDQpCZXN0IHJlZ2FyZHMsDQpJYW4NCg0K
DQpQZyA1IC0gc3RhdGVzIGEgJ2R1YWwtc3RhY2snIHJvdXRlci4gVGhlIEFGQlIgaXMgbm90IHJl
YWxseSBkdWFsLXN0YWNrIGhlcmUuIEl0IGhhcyB0d28gc2luZ2xlIHN0YWNrIGludGVyZmFjZXMg
YW5kIGltcGxlbWVudHMgYSB0cmFuc2l0aW9uIHRlY2hub2xvZ3kuIFN1Z2dlc3QgcmVtb3ZhbCBv
ZiBkdWFsLXN0YWNrLg0KDQoNClNlY3Rpb24gNC4xDQpUaGUgdHJhbnNsYXRpb24gYmV0d2VlbiB0
aGUgSVB2NCBhbmQgSVB2NiBQSU0gbWVzc2FnZXMgc2VlbXMgdW5kZXJzcGVjaWZpZWQuIEl0IHdv
dWxkIGJlIHVzZWZ1bCB0byBwcm92aWRlIHNvbWUgZXhhbXBsZXMgc2hvd2luZyBob3cgdGhlIG5l
dyBhZGRyZXNzZXMgYXJlIHVzZWQgaW4gdGhlIGRpZmZlcmVudCB0cmFuc2xhdGlvbnMgaW50byB0
aGUgUElNIG1lc3NhZ2UgZm9ybWF0cyAoUkZDNzc0MSBTZWN0aW9uIDQuMSkuDQoNCg0KU2VjdGlv
biA0LjINClRoZSB0ZXJtIOKAmE1QUkVGSVg2NOKAmSBpcyBub3QgZGVmaW5lZCBpbiBSRkM3Mzcx
LiBBcyB0aGVyZSBhcmUgYSBudW1iZXIgb2YgZGlmZmVyZW50IGZvcm1hdHMgZm9yIG11bHRpY2Fz
dCBwcmVmaXhlcyBpbiBSRkM3MzcxLCBpdCB3b3VsZCBiZSB1c2VmdWwgdG8gcG9pbnQgdG8gdGhl
IHJlbGV2YW50IHNlY3Rpb24gdG8gYXZvaWQgY29uZnVzaW9uLg0KDQoNCldoeSB3YXMgdGhlIG5h
bWUgTVBSRUZJWDY0IGNob3NlbiBmb3IgNGluNiBtdWx0aWNhc3Q/IEluIG90aGVyIFNvZnR3aXJl
IGRvY3MgKGUuZy4gUkZDNzU5OCksIOKAmTQ24oCZIGlzIHVzZWQgdG8gZGVub3RlIDQgaW4gNiBm
dW5jdGlvbnMgYW5kIDY0IGZvciA2IGluIDQuIEFzIHRoZSBhZGRyZXNzaW5nIGFuZCBtZWNoYW5p
c20gZm9yIDRpbjYgZGlmZmVycyBmb3IgNmluNCwgaXQgd291bGQgbWFrZSBzZW5zZSB0byBkaWZm
ZXJlbnRpYXRlIHRoaXMgaW4gdGhlIG5hbWluZyBvZiB0aGUgZmllbGRzIChpLmUuIHVzZSBNUFJF
RklYNDYsIHVQcmVmaXg0NiBmb3IgNGluNiBhbmQgdVByZWZpeDY0IGZvciA2aW40KS4NCg0KDQpT
ZWN0aW9uIDYuMw0KU2VjdGlvbiA2IG92ZXJhbGwgZGVmaW5lcyByZXF1aXJlbWVudHMgZm9yIHRo
ZSBjb250cm9sIHBsYW5lLiBTZWN0aW9ucyA2LjEuIGFuZCA2LjIgYXJlIE1VU1QgcmVxdWlyZW1l
bnRzLiA2LjMgdXNlcyDigJhzaG91bGTigJkgaW4gZGVmaW5pbmcgdGhlIGJlaGF2aW91ci4gQ2Fu
IHRoZSBtZWNoYW5pc20gd29yayB3aXRob3V0IGltcGxlbWVudGluZyBzZWMgNi4zIGFuZCBpbiB3
aGljaCBzaXR1YXRpb25zIGlzIGl0IGFjY2VwdGFibGUgbm90IHRvPw0KDQoNClNlY3Rpb24gNi41
DQpUaGlzIGludHJvZHVjZXMgdGhlIGVuY2Fwc3VsYXRpb24gb2YgbWVzc2FnZXMsIGJ1dCBkb2Vz
buKAmXQgcHJvdmlkZSBhbnkgaW5mb3JtYXRpb24gYWJvdXQgd2hhdCB0eXBlIG9mIGVuY2Fwc3Vs
YXRpb24gaXMgdXNlZC4gRmlndXJlIDcgc2hvd3MgVURQLiBJcyB0aGlzIHBhcnQgb2YgdGhlIGVu
Y2Fwc3VsYXRpb24/IEFzIHRoaXMgaXMgbmVjZXNzYXJ5IGZvciB0aGUgbWVjaGFuaXNtIHRvIHdv
cmsgYW5kIG5lZWRzIHRvIGJlIGltcGxlbWVudGVkIG9uIHRoZSBBRkJScywgdGhlcmUgbmVlZHMg
dG8gYmUgcmVmZXJlbmNlcyBhbmQgcmVxdWlyZW1lbnRzIGxhbmd1YWdlIG9uIHdoYXQgbmVlZHMg
dG8gYmUgaW1wbGVtZW50ZWQuDQoNCg0Kcy93ZSBkbyBpbnN1cmUvaXQgaXMgZW5zdXJlZC8NCg0K
DQpTZWN0aW9uIDcuMg0KQXJlIHRoZXJlIG9wdGlvbnMgb24gdGhlIGtpbmQgb2YgdHVubmVsIGVu
Y2Fwc3VsYXRpb24gdGhhdCBjYW4gYmUgdXNlZD8gSXQgd291bGQgYmUgdXNlZnVsIHRvIGVudW1l
cmF0ZSBzb21lIG9mIHRoZXNlIGFuZCBmb3IgaW50ZXJvcGVyYWJpbGl0eSBvbmUgb2YgdGhlbSBu
ZWVkcyB0byBiZSBtYW5kYXRvcnkgdG8gaW1wbGVtZW50Lg0KDQoNClJlZmVyZW5jZXMNClJGQzIx
MTkgTmVlZHMgdG8gaGF2ZSBhIG5vcm1hdGl2ZSByZWZlcmVuY2UNClJGQzQ2MDEgaGFzIGJlZW4g
b2Jzb2xldGVkIGJ5IFJGQzc3NjENCg0KDQpHZW5lcmFsIC0gDQpUaGUgZG9jdW1lbnQgZG9lc27i
gJl0IGNvbnRhaW4gdGhlIOKAmENvbnZlbnRpb25zL1JlcXVpcmVtZW50cyBMYW5ndWFnZeKAmSBi
b2lsZXJwbGF0ZSBwb2ludGluZyB0byBSRkMyMTE5IHRoYXQgbmVlZHMgdG8gYmUgaW4gYSBzdGFu
ZGFyZHMgdHJhY2sgZG9jdW1lbnQuIChUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9U4oCd
LCDigKYpDQoNCg0KVGhlIHVzZSBvZiBSRkMyMTE5IGxhbmd1YWdlIGFuZCB0aGUgY2FzZSBvZiB0
aGUgd29yZHMgdGhyb3VnaG91dCB0aGUgZG9jdW1lbnQgaXMgbm90IGNvbnNpc3RlbnQgKHRoZXJl
IGFyZSBhIG51bWJlciBvZiBsb3dlciBjYXNlIOKAmG11c3TigJkgZXRjLCB0aGF0IHByb2JhYmx5
IHNob3VsZCBiZSB1cHBlcmNhc2UpLg0KDQoNClRoZSB0ZXJtIOKAmHNob3VsZOKAmSAobG93ZXIg
Y2FzZSkgaXMgdXNlZCBpbiBhIG51bWJlciBvZiBwbGFjZXMgdGhhdCBtYWtlIHRoZSBmdW5jdGlv
bmFsaXR5IG9mIHRoZSBtZWNoYW5pc20gc2VlbSB1bmNlcnRhaW4gKGUuZy4gRmlndXJlIDEgLSAn
TXVsdGljYXN0IHBhY2tldHMgc2hvdWxkIGdldCBhY3Jvc3MgdGhlIEktSVAgdHJhbnNpdCBjb3Jl
Jy4gU2VjIDQuMSAnaXQgc2hvdWxkIGJlIHRyYW5zbGF0ZWQgYmFja+KAmSkuDQoNCg0KVGhlcmUg
YXJlIHNvbWUgcG9pbnRzIHRoYXQgd291bGQgc2VlbSB0byBuZWVkIE1VU1QgcmVxdWlyZW1lbnRz
IHRoYXQgYXJlIG1pc3NpbmcgLSBlLmcuIFNlY3Rpb24gNC40ICdldmVyeSB1UHJlZml4NjQgdGhh
dCBBRkJSIGFubm91bmNlcyBzaG91bGQgYmUgZGlmZmVyZW50IGVpdGhlciwgYW5kIHVuaXF1ZWx5
IGlkZW50aWZpZXMgZWFjaCBBRkJS4oCZLiBJZiB0d28gQUZCUnMgYXJlIGFubm91bmNpbmcgdGhl
IHNhbWUgdVByZWZpeDY0LCBzdXJlbHkgdGhlcmUgd2lsbCBiZSBwcm9ibGVtcy4NCg0KDQpTdWdn
ZXN0IHRoYXQgdGhlIHVzZSBvZiBSRkMyMTE5IGxhbmd1YWdlIGlzIHJldmlzZWQgdGhyb3VnaG91
dCB0aGUgZG9jdW1lbnQgdG8gYXZvaWQgdGhlc2UgcHJvYmxlbXMgYW5kIHRvIHRpZ2h0ZW4gdXAg
dGhlIHNwZWNpZmljYXRpb24gYXMgYSB3aG9sZS4NCg0KDQpUaGUgZG9jdW1lbnQgbmVlZHMgdGhl
IGxhbmd1YWdlIGFuZCBncmFtbWFyIGNoZWNraW5nIHRocm91Z2hvdXQuDQoNCg0KDQoNCk9uIDcg
QXByIDIwMTYsIGF0IDE2OjU4LCBJYW4gRmFycmVyIDxpYW5mYXJyZXJAZ214LmNvbT4gd3JvdGU6
DQoNCg0KSGksDQoNClRoaXMgZG9jdW1lbnQgaGFzIGJlZW4gYXJvdW5kIGZvciBzb21lIHRpbWUs
IGJ1dCBoYXMgbm90IHJlY2VpdmVkIGFueSBzdWJzdGFudGl2ZSByZXZpZXdzLiBDYW4gSSBhc2sg
Zm9yIHZvbHVudGVlcnMgd2hvIGFyZSB3aWxsaW5nIHRvIHByb3ZpZGUgcmV2aWV3cz8NCg0KVGhh
bmtzLA0KSWFuDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NClNvZnR3aXJlcyBtYWlsaW5nIGxpc3QNClNvZnR3aXJlc0BpZXRmLm9yZw0KaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zb2Z0d2lyZXMNCg==


