
From nobody Sun Feb  2 08:43:08 2020
Return-Path: <prvs=29491c422=anil@csir4pi.in>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D21412008D for <multipathtcp@ietfa.amsl.com>; Sun,  2 Feb 2020 08:43:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 HKUFQ7RwLE0U for <multipathtcp@ietfa.amsl.com>; Sun,  2 Feb 2020 08:43:02 -0800 (PST)
Received: from vastu23.nic.in (vastu23.nic.in [164.100.10.70]) (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 F41AD12003F for <multipathtcp@ietf.org>; Sun,  2 Feb 2020 08:43:00 -0800 (PST)
IronPort-PHdr: =?us-ascii?q?9a23=3ANotzyx8A3wzDAf9uRHKM819IXTAuvvDOBiVQ1K?= =?us-ascii?q?B+0+ofIJqq85mqBkHD//Il1AaPAdyHra4ZwLqL++C4ACpcuM3H6ChDOLV3FD?= =?us-ascii?q?Y9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQk?= =?us-ascii?q?a3OgV6PPn6FZDPhMqrye+y54fTYwJVjzahfL9+Nhq7oRjeu8UMjoZvKqk9xx?= =?us-ascii?q?jJr3BVf+ha2X5kKUickhrh6Mq85oJv/zhVt/k868NOTKL2crgiQ7dFFjomKW?= =?us-ascii?q?c15MPqtRnHUwSC42YXX3sVnBRVHQXL9Qn2UZjtvCT0sOp9wzSaMtbtTb8oQz?= =?us-ascii?q?Si7rxkRwHuhSwaKjM26mDXish3jKJGvBKsogF0zoDIbI2JMvd1Y7jQds0GS2?= =?us-ascii?q?VfQslRVjRBAoKiYIsJE+oBJvtTo43kq1cTsReyGQygCeXywTFKm3D2x7U33e?= =?us-ascii?q?ohHw/Y3wIvHdwOvmnbo9rpNaccVvy1wbLSwjnfdf5bwy3w5JTKfx0nvPqCXa?= =?us-ascii?q?hwcc3UyUQ3GAzOk0mdqYrkPzORy+8DtnWb7+96WuK1lmUqrBt+oj6uxscokY?= =?us-ascii?q?TGmpkVylHe9Sh22IY1JMe0SE99YdO9FpZbqi+UN4xzQsw4QmFovj43yrwYtp?= =?us-ascii?q?6ncigG0pMnxwTQa/GBboOG4QrjWf6MLTtkmH5pYrGyiwqo/US91+HwTMa53V?= =?us-ascii?q?dSoiZYjNXAqGoB2wHR58SaUPdx40Os1SuV2wzN7uxIOV04mbbHJ5I7wbM8io?= =?us-ascii?q?AfvVnCEyPshUn7gqubel059uS09+jreLbrqoOGO4NpiwzyKLoil8OjDek+Lw?= =?us-ascii?q?MARXKU+f6m273m5UD5RbJKgeAonaTBq5DaINgbpra+Aw9IzoYv8xa/ACmi0N?= =?us-ascii?q?QfhXQHI0pFeBWIj4nnJl3CPur0DfG+g1uwijtrxvbGMqXgApXLMHfDjK/sca?= =?us-ascii?q?th50JA0gY+zsxT64hJBr0cOv7+VU78uMTdDhAjMgy0x+jnCM961oMbQW+AGK?= =?us-ascii?q?mZMKLWsVKT+u0vOOiMZJUatTblKvgp/f/ujXkhlV8HYaapxYcXaGy/Hvl+OU?= =?us-ascii?q?qZZWDjgtEbHWcEuQo+VvHlhUaNUT5WfXmyXqY86isnB4KhCIfJXpqtj6CZ3C?= =?us-ascii?q?enAp1WYXhLClaXEXj1bYmEWukDaD6cIsJ6nTwEUKKuS44l1R20qAD6zL9nJP?= =?us-ascii?q?LO+iIErZLjyMR15+rLmBE36Dx0C9id02CVT25ugmMIRyM207xnoUFmy1eMz7?= =?us-ascii?q?R4g/JCGdxU/fNJXVRyCZmJhd19ENDzVB/Ef5+vSU2mQ9mvS3llSMk9hd4Df0?= =?us-ascii?q?hVFNCrjxSF1C2vVew7jbuOUaJ826Td2zDSOsN00T6S3a8gi3EtWcpVaXWnwK?= =?us-ascii?q?95oVuAT7XVmlmUwv75PZ8X2zTAoSLalTKD?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2EMAQCc9jZe/y4LUGRlGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF7gSVTMWxWAR4SKgqECokDhgqCEYlhkUsIBAk?= =?us-ascii?q?BAQIBAQEBASABCgoCAQECg3lFAoIyJDgTAgMBDAEBAQQBAQEBAQUDAQEBAmm?= =?us-ascii?q?Ea0wMgjspAXFxAQEBAQEBAQEBAQEBAQEBAQEBARYCQ1USAQEdAQEBAQMBARg?= =?us-ascii?q?JRAcGBRACAQgNAQMEAQEhBwMCAiEGHwkIAgQKAQgUgxOCSgMtAQUKqll1gTI?= =?us-ascii?q?aAoUuglgNghoGgTiMIBQGggCBEYMTPoEEgRdJAQGBPAcBATIkglqCXgSNVIo?= =?us-ascii?q?pfJVzMkSCRZIWhEWCSIgOhDUDi3qZcJFkOCMqgS5NODuCbFAYjjMDF4UIg1y?= =?us-ascii?q?FRzoBMYEpiyQFDBeBCwGBDwEB?=
X-IPAS-Result: =?us-ascii?q?A2EMAQCc9jZe/y4LUGRlGgEBAQEBAQEBAQMBAQEBEQEBA?= =?us-ascii?q?QICAQEBAYF7gSVTMWxWAR4SKgqECokDhgqCEYlhkUsIBAkBAQIBAQEBASABC?= =?us-ascii?q?goCAQECg3lFAoIyJDgTAgMBDAEBAQQBAQEBAQUDAQEBAmmEa0wMgjspAXFxA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBARYCQ1USAQEdAQEBAQMBARgJRAcGBRACAQgNA?= =?us-ascii?q?QMEAQEhBwMCAiEGHwkIAgQKAQgUgxOCSgMtAQUKqll1gTIaAoUuglgNghoGg?= =?us-ascii?q?TiMIBQGggCBEYMTPoEEgRdJAQGBPAcBATIkglqCXgSNVIopfJVzMkSCRZIWh?= =?us-ascii?q?EWCSIgOhDUDi3qZcJFkOCMqgS5NODuCbFAYjjMDF4UIg1yFRzoBMYEpiyQFD?= =?us-ascii?q?BeBCwGBDwEB?=
X-IronPort-AV: E=McAfee;i="6000,8403,9519"; a="323632610"
X-IronPort-AV: E=Sophos;i="5.70,394,1574101800";  d="scan'208,217";a="323632610"
Received: from unknown (HELO gpogw12.nic.in) ([100.80.11.46]) by vastu10internal.nic.in with ESMTP; 02 Feb 2020 22:12:54 +0530
Received: from gpogw12.nic.in (localhost [127.0.0.1]) by gpogw12.nic.in (Postfix) with ESMTPS id AC8854067299; Sun,  2 Feb 2020 22:12:54 +0530 (IST)
Received: from localhost (localhost [127.0.0.1]) by gpogw12.nic.in (Postfix) with ESMTP id 9F1134067298; Sun,  2 Feb 2020 22:12:54 +0530 (IST)
X-Amavis-Modified: Mail body modified (using disclaimer) - gpogw12.nic.in
Received: from gpogw12.nic.in ([127.0.0.1]) by localhost (gpogw12.nic.in [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id blkOn9fiAfDa; Sun,  2 Feb 2020 22:12:54 +0530 (IST)
Received: from gms281.nic.in (unknown [100.80.16.240]) by gpogw12.nic.in (Postfix) with ESMTP id 7ECE54067297; Sun,  2 Feb 2020 22:12:54 +0530 (IST)
Date: Sun, 2 Feb 2020 22:09:41 +0530 (IST)
From: V Anil Kumar <anil@csir4pi.in>
To: "Yoshifumi Nishida" <nsd.ietf@gmail.com>
Cc: "alan ford" <alan.ford@gmail.com>, "multipathtcp" <multipathtcp@ietf.org>
Message-ID: <146023054.25180934.1580661581660@csir4pi.in>
In-Reply-To: <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="=_92456e92-4e17-4635-acec-5109e21746f3"
X-Originating-IP: [122.171.191.29, 100.80.16.139]
X-Mailer: Zimbra 8.8.9_GA_2044 (ZimbraWebClient - GC49 (Mac)/8.8.9_GA_2044)
Thread-Topic: RFC6824bis edits based on implementation feedback
Thread-Index: CAtnqyNQdXUk9JHpa9eq0qqaBxewlg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/5kYzEKUW4gXnppOuAdYGTmjPz5o>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Feb 2020 16:43:06 -0000

--=_92456e92-4e17-4635-acec-5109e21746f3
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Yoshi,=20

Thanks for this point. In fact, I had initially not thought of a scenario, =
where the map is being delivered through a retransmitted data packet while =
its first transmission did not include the map. Now I am just seeing the do=
cument (RFC 6824-bis) in this context.=20

My understanding is that in scenarios like what I described in my previous =
mail, RST is likely to happen whether we explicitly state so or not. Please=
 see the paragraph containing the below text in RFC 6824-bis.=20

"If a mapping for that subflow-level sequence space does not arrive within =
a receive window of data, that subflow SHOULD be treated as broken, closed =
with a RST, and any unmapped data silently discarded."=20

if we assume that the map is included while retransmitting the data (even t=
hough the first transmission did not contain the map for some reasons), we =
could argue that RST could be avoided provided that the retransmission is t=
riggered within a receive window of data. But the question here would be ho=
w and when will the retransmission take place. In this case, the subflow ma=
y not initiate the retransmission of data by its own (i.e., no retransmissi=
on due to three duplicate ACKs or RTO expiry at subflow level) as there is =
no segment loss at subflow level sequence space. So there could be a high p=
ossibility of RST happening even before the map delivery through retransmis=
sion.=20

With regards,=20

Anil=20

From: "Yoshifumi Nishida" <nsd.ietf@gmail.com>=20
To: "V Anil Kumar" <anil@csir4pi.in>=20
Cc: "alan ford" <alan.ford@gmail.com>, "multipathtcp" <multipathtcp@ietf.or=
g>=20
Sent: Saturday, February 1, 2020 3:39:51 AM=20
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedba=
ck=20

Hi Anil,=20

I have a question about your proposed text.=20
I am actually wondering if we really want to terminate connection here.=20

The packets without proper mappings will be treated as invalid and will be =
discarded.=20
If an implementation failed to attach proper mapping for some reasons (e.g.=
 option space), it might be able to attach the proper one when it retransmi=
ts the packets. This also looks ok to me.=20

I don't have strong preference for this. But, do we have a reason to termin=
ate connection?=20

Thanks,=20
--=20
Yoshi=20

On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar < [ mailto:anil@csir4pi.in | =
anil@csir4pi.in ] > wrote:=20



Hi,=20

I have some points related to the modifications (Change 2) being proposed o=
n data sequence map. Please see them inline. Though I am putting forward th=
e below points, if the consensus is in favour of the proposed change for re=
ducing implementation complexity, I am also OK with that as well.=20


From: "alan ford" < [ mailto:alan.ford@gmail.com | alan.ford@gmail.com ] >=
=20
To: [ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]=20
Sent: Thursday, January 2, 2020 4:21:32 AM=20
Subject: [multipathtcp] RFC6824bis edits based on implementation feedback=
=20

Hi all,=20
We=E2=80=99d love to get this to a state of completion as soon as possible,=
 and to this end I am starting a new thread on this topic. In discussion wi=
th the chairs, it is possible to make the desired changes in AUTH48 as long=
 as there is WG consensus. The discussion so far has been fairly limited in=
 terms of participation.=20

I would ask the chairs please if it was possible to specify a time bound fo=
r this discussion and a default conclusion.=20

Regarding the changes, in summary, there are two areas where changes have b=
een requested by the implementation community. As we are the IETF we obviou=
sly have strong focus on =E2=80=9Crunning code=E2=80=9D and so ease of impl=
ementing standards-compliant code is strongly desirable. However, we do not=
 wish to reduce functionality agreed by the IETF community if it is conside=
red a required feature by the community.=20


Change 1=20

Change the sentence reading:=20

If B has data to send first, then the reliable delivery of the ACK + MP_CAP=
ABLE can be inferred by the receipt of this data with an MPTCP Data Sequenc=
e Signal (DSS) option (Section 3.3).=20

To:=20

If B has data to send first, then the reliable delivery of the ACK + MP_CAP=
ABLE is ensured by the receipt of this data with an MPTCP Data Sequence Sig=
nal (DSS) option (Section 3.3) containing a DATA_ACK for the MP_CAPABLE (wh=
ich is the first octet of the data sequence space).=20

What this means:=20

The current text is concerned only with ensuring a path is MPTCP capable, a=
nd so only cares that DSS option occurs on a data packet. However, the MP_C=
APABLE option is defined to occupy the first octet of data sequence space a=
nd thus, if analogous to TCP, must be acknowledged. >From an implementation=
 point of view it would make sense not to have this hanging around forever =
and instead define it is acknowledged at the connection level as soon as re=
ceived. This change ensures the first data packet also DATA_ACKs this MP_CA=
PABLE octet.=20


Change 2=20

Change the sentence reading:=20

A Data Sequence Mapping does not need to be included in every MPTCP packet,=
 as long as the subflow sequence space in that packet is covered by a mappi=
ng known at the receiver.=20

To:=20

The mapping provided by a Data Sequence Mapping MUST apply to some or all o=
f the subflow sequence space in the TCP segment which carries the option. I=
t does not need to be included in every MPTCP packet, as long as the subflo=
w sequence space in that packet is covered by a mapping known at the receiv=
er.=20

What this means:=20

The current text does not place any restrictions on where a mapping could a=
ppear. In theory a sender could define a thousand different mappings up fro=
nt, send them all, and expect a receiver to store this and reassemble data =
according to these mappings as it arrives. Indeed, this was never explicitl=
y disallowed since it =E2=80=9Cmight have been useful=E2=80=9D. The impleme=
ntation community, however, has expressed concerns over the difficulty of i=
mplementing this open-endedly. How many mappings is it reasonable to store?=
 Is there a DoS risk here? Instead, it has been requested that thee specifi=
cation restricts the placement of the DSS option to being within the subflo=
w sequence space to which it applies.=20

Below are my comments on this. I had shared some of these points in a previ=
ous thread that you had initiated in the same context.=20

Transmitting large number of non-contiguous data sequence maps could be a m=
isbehaviour (map-flooding), though it is not clear whether this can go to t=
he extent of causing a potential DoS to the data receiver. So some sort of =
restriction on this could be useful. One approach could be to insist that t=
he data sender should ensure that the map being transmitted is for in-windo=
w data, as per the receiver advertised window. A receiver should anyhow be =
willing to store the maps for in-window data to deal with packet loss. For =
example, when a window of data segments (say 1 to 64) is transmitted, each =
carrying its corresponding map, and segment-1 is lost, the maps for the rem=
aining 63 need to be stored till the lost segment is retransmitted. Of cour=
se, in this case the maps will be stored at the receiver side along with th=
eir corresponding data. But the need to store multiple maps for in-window d=
ata would still be there.=20

The problem with the proposed change (restriction) is that a data sender ma=
y find it difficult, in case a need arise to slightly delay the map deliver=
y by few segments, i.e., sending some data first without map, and then send=
 the corresponding map in a later segment, as shown below:=20



subflow-1: segment-1 segment-3 segment-4 segment-7=20

bytes:1-100 bytes:201-300 bytes:301-400 bytes:601-700=20

no map map for 1-100 map for 201-400 map for 601-700=20










subflow-2: segment-2 segment-5 segment-6 segment-8=20

bytes: 101-200 bytes:401-500 bytes: 501-600 bytes:701-800=20

map for 101-200 map for 401-600 no map map for 701-800=20





In the above case, segment-1 goes without map and its map is included later=
 in segment-3, the next data segment in the same subflow. Further, in the a=
bove scheduling pattern, the map in segment-3 cannot cover the data in segm=
ent-1 and segment-3, as some data in between (segment-2) is transmitted thr=
ough another subflow. With the proposed change, the map in segment-3 will b=
ecome invalid and this will eventually break subflow-1, though this could b=
e a corner case.=20

The question at this stage is why would segment-1 be transmitted without it=
s map. In the case of bidirectional data transfer, there could be a need to=
 pack both timestamp and SACK options in a data segment, i.e., piggybacking=
 of SACK with data. If we consider that timestamp takes 12 bytes and SACK, =
even with single block, takes another 10 bytes, the remaining 18 bytes opti=
on space is not adequate to carry data sequence signal with map, especially=
 when DSN is 64 bit long. So the delivery of either of the two (SACK or map=
) would be delayed.=20

As far as I understand, RFC 2018 (TCP Selective Acknowledgement Options) im=
plies that SACK should not be delayed. It states "If sent at all, SACK opti=
ons SHOULD be included in all ACKs which do not ACK the highest sequence nu=
mber in the data receiver's queue". It also says "If data receiver generate=
s SACK options under any circumstance, it SHOULD generate them under all pe=
rmitted circumstances". So, as part of meeting the RFC 2018 requirements, i=
f the combination of SACK and timestamp is given preference over DSS, data =
segments could be transmitted without their map.=20

Another case of delaying map could arise if the data sender prefers to send=
 ADD_ADDR option, instead of map, in a data segment. It is nice that ADD_AD=
DR option can be delivered reliably in a pure ACK, but I think this is not =
the case with DSS at present.=20

If we adopt the proposed change, I think it might also be helpful to spell =
out how the receiver is supposed to behave, if it gets maps not meeting the=
 MUST condition in the proposed change. For example termination of the subf=
low with MP_TCPRST option (section 3.6 in RFC 6824-bis) with appropriate re=
ason code and T flag value to intimate the data sender the cause for subflo=
w termination.=20
With regards,=20

Anil=20

Please can members of the WG express whether they are happy with these chan=
ges, or concerned.=20

Best regards,=20
Alan=20


_______________________________________________=20
multipathtcp mailing list=20
[ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]=20
[ https://www.ietf.org/mailman/listinfo/multipathtcp | https://www.ietf.org=
/mailman/listinfo/multipathtcp ]=20



_______________________________________________=20
multipathtcp mailing list=20
[ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]=20
[ https://www.ietf.org/mailman/listinfo/multipathtcp | https://www.ietf.org=
/mailman/listinfo/multipathtcp ]=20





=0A
--=_92456e92-4e17-4635-acec-5109e21746f3
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"font-family: arial, helvetica, sans-serif; font-s=
ize: style=3D" font-size:=3D"" 12pt;=3D"" color:=3D"" #000000"=3D""><div da=
ta-marker=3D"__QUOTED_TEXT__"><div style=3D"font-family:'arial' , 'helvetic=
a' , sans-serif"><div>Hi Yoshi,</div><br><div>Thanks for this point. In fac=
t, I had initially not thought of a scenario, where the map is being delive=
red through a retransmitted data packet while its first transmission did no=
t include the map. Now I am just seeing the document (RFC 6824-bis) in this=
 context.</div><br><div>My understanding is that in scenarios like what I d=
escribed in my previous mail, RST is likely to happen whether we explicitly=
 state so or not. Please see the paragraph containing the below text in RFC=
 6824-bis. &nbsp;</div><br><div>"If a mapping for that subflow-level sequen=
ce space does not arrive within a receive window of data, that subflow SHOU=
LD be treated as broken, closed with a RST, and any unmapped data silently =
discarded."</div><br><div>if we assume that the map is included while retra=
nsmitting the data (even though the first transmission did not contain the =
map for some reasons), &nbsp;we could argue that RST could be avoided provi=
ded that the retransmission is triggered within a receive window of data. B=
ut the question here would be how and when will the retransmission take pla=
ce. In this case, the subflow may not initiate the retransmission of data b=
y its own (i.e., no retransmission due to three duplicate ACKs or RTO expir=
y at subflow level) as there is no segment loss at subflow level sequence s=
pace. So there could be a high possibility of RST happening even before the=
 map delivery through retransmission.&nbsp;</div><br><div>With regards,&nbs=
p;</div><br><div>Anil</div><div>&nbsp;</div><hr id=3D"zwchr"><div><b>From: =
</b>"Yoshifumi Nishida" &lt;nsd.ietf@gmail.com&gt;<br><b>To: </b>"V Anil Ku=
mar" &lt;anil@csir4pi.in&gt;<br><b>Cc: </b>"alan ford" &lt;alan.ford@gmail.=
com&gt;, "multipathtcp" &lt;multipathtcp@ietf.org&gt;<br><b>Sent: </b>Satur=
day, February 1, 2020 3:39:51 AM<br><b>Subject: </b>Re: [multipathtcp] RFC6=
824bis edits based on implementation feedback<br></div><br><div><div dir=3D=
"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><br><div>I have =
a question about your proposed text.</div><div><div>I am actually wondering=
 if we really want to terminate connection here.&nbsp;</div></div><br><div>=
The packets without proper mappings will be treated as invalid and will be =
discarded.&nbsp;</div><div>If an implementation failed to attach proper map=
ping for some reasons (e.g. option space), it might be able to attach the p=
roper one when it retransmits the packets. This also looks ok to me.</div><=
br><div>I don't have strong preference for this. But, do we have a reason t=
o terminate connection?</div><br><div>Thanks,</div><div>--<br></div><div>Yo=
shi</div><br><div><div dir=3D"ltr">On Mon, Jan 13, 2020 at 10:28 AM V Anil =
Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow%20noopener%20n=
oreferrer nofollow noopener noreferrer" target=3D"_blank">anil@csir4pi.in</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1=
ex"><div><div><div><div style=3D"font-family:'arial' , 'helvetica' , sans-s=
erif"><div><span style=3D"font-size:12pt;line-height:1.3">Hi,</span><br></d=
iv><div><div style=3D"font-family:'arial' , 'helvetica' , sans-serif"><div =
style=3D"font-family:'arial' , 'helvetica' , sans-serif"><div style=3D"font=
-family:'arial' , 'helvetica' , sans-serif"><div style=3D"font-family:'aria=
l' , 'helvetica' , sans-serif"><div style=3D"font-family:'arial' , 'helveti=
ca' , sans-serif"><div style=3D"font-family:'arial' , 'helvetica' , sans-se=
rif"><div style=3D"font-family:'arial' , 'helvetica' , sans-serif"><br><div=
>I have some points related to the &nbsp;modifications (Change 2) being pro=
posed on data sequence map. Please see them inline.&nbsp;<span style=3D"col=
or:rgb( 0 , 0 , 0 );font-family:'arial' , 'helvetica' , sans-serif;font-siz=
e:16px;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:=
0px;text-transform:none;white-space:normal;word-spacing:0px;background-colo=
r:rgb( 255 , 255 , 255 );float:none;display:inline">Though I am putting for=
ward the below points, if the consensus is in favour of the proposed change=
 for reducing implementation complexity, I am also OK with that as well.&nb=
sp;</span><br></div><br><hr id=3D"gmail-m_7687184382299596774zwchr"><div><b=
>From: </b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" rel=3D"no=
follow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"_bla=
nk">alan.ford@gmail.com</a>&gt;<br><b>To: </b><a href=3D"mailto:multipathtc=
p@ietf.org" rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noref=
errer" target=3D"_blank">multipathtcp@ietf.org</a><br><b>Sent: </b>Thursday=
, January 2, 2020 4:21:32 AM<br><b>Subject: </b>[multipathtcp] RFC6824bis e=
dits based on implementation feedback<br></div><br><div>Hi all,<br><div>We=
=E2=80=99d love to get this to a state of completion as soon as possible, a=
nd to this end I am starting a new thread on this topic. In discussion with=
 the chairs, it <i>is </i>possible to make the desired changes in AUTH48 as=
 long as there is WG consensus. The discussion so far has been fairly limit=
ed in terms of participation.</div><br><div>I would ask the chairs please i=
f it was possible to specify a time bound for this discussion and a default=
 conclusion.</div><br><div>Regarding the changes, in summary, there are two=
 areas where changes have been requested by the implementation community. A=
s we are the IETF we obviously have strong focus on =E2=80=9Crunning code=
=E2=80=9D and so ease of implementing standards-compliant code is strongly =
desirable. However, we do not wish to reduce functionality agreed by the IE=
TF community if it is considered a required feature by the community.</div>=
<br><br><div><b>Change 1</b></div><div><b><br></b></div><div>Change the sen=
tence reading:<br><br><i>&nbsp; &nbsp;If B has data to send first, then the=
 reliable delivery of the ACK + MP_CAPABLE can be inferred by the receipt o=
f this data with an MPTCP Data Sequence Signal (DSS) option (Section 3.3).&=
nbsp;<br></i><br>To:<br><br><i>&nbsp; &nbsp;If B has data to send first, th=
en the reliable delivery of the ACK + MP_CAPABLE is ensured by the receipt =
of this data with an MPTCP Data Sequence Signal (DSS) option (Section 3.3) =
containing a DATA_ACK for the MP_CAPABLE (which is the first octet of the d=
ata sequence&nbsp;space).<br></i><br></div><div>What this means:</div><br><=
div>The current text is concerned only with ensuring a path is MPTCP capabl=
e, and so only cares that DSS option occurs on a data packet. However, the =
MP_CAPABLE option is defined to occupy the first octet of data sequence spa=
ce and thus, if analogous to TCP, must be acknowledged. &gt;From an impleme=
ntation point of view it would make sense not to have this hanging around f=
orever and instead define it is acknowledged at the connection level as soo=
n as received. This change ensures the first data packet also DATA_ACKs thi=
s MP_CAPABLE octet.</div><br><br><div><b>Change 2</b></div><div><b><br></b>=
</div><div>Change the sentence reading:<br><br><i>&nbsp; &nbsp;A Data Seque=
nce Mapping does not need to be included in every MPTCP packet, as long as =
the subflow sequence space in that packet is covered by a mapping known at =
the receiver.</i><br><br>To:<br><br><i>&nbsp; &nbsp;The mapping provided by=
 a Data Sequence Mapping MUST apply to some or all of the subflow sequence =
space in the TCP segment which carries the option. It does not need to be i=
ncluded in every MPTCP packet, as long as the subflow sequence space in tha=
t packet is covered by a mapping known at the receiver.<br></i><br>What thi=
s means:</div><br><div>The current text does not place any restrictions on =
where a mapping could appear. In theory a sender could define a thousand di=
fferent mappings up front, send them all, and expect a receiver to store th=
is and reassemble data according to these mappings as it arrives. Indeed, t=
his was never explicitly disallowed since it =E2=80=9Cmight have been usefu=
l=E2=80=9D. The implementation community, however, has expressed concerns o=
ver the difficulty of implementing this open-endedly. How many mappings is =
it reasonable to store? Is there a DoS risk here? Instead, it has been requ=
ested that thee specification restricts the placement of the DSS option to =
being within the subflow sequence space to which it applies.</div><br><div>=
Below are my comments on this. I had shared some of these points in a previ=
ous thread that you had initiated in the same context.&nbsp;</div><br><div>=
Transmitting large number of non-contiguous data sequence maps could be a m=
isbehaviour (map-flooding), though it is not clear whether this can go to t=
he extent of causing a potential DoS to the data receiver. So some sort of =
restriction on this could be useful.&nbsp; One approach could be to insist =
that the data sender should ensure that the map being transmitted is for in=
-window data, as per the receiver advertised window. A receiver should anyh=
ow be willing to store the maps for in-window data to deal with packet loss=
. For example, when a window of data segments (say 1 to 64) is transmitted,=
 each carrying its corresponding map, and segment-1 is lost, the maps for t=
he remaining 63 need to be stored till the lost segment is retransmitted. O=
f course, in this case the maps will be stored at the receiver side along w=
ith their corresponding data. But the need to store multiple maps for in-wi=
ndow data would still be there.</div><br><div><span style=3D"color:rgb( 0 ,=
 0 , 0 );font-family:'arial' , 'helvetica' , sans-serif;font-size:16px;font=
-style:normal;font-weight:normal;letter-spacing:normal;line-height:20.8px;t=
ext-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;floa=
t:none;background-color:rgb( 255 , 255 , 255 );display:inline">The problem =
with the proposed change (restriction) is that a data sender may find it di=
fficult, in case a need arise to slightly delay the map delivery by few seg=
ments, i.e., sending some data first without map, and then send the corresp=
onding map in a later segment, as shown below:</span><br></div><br><div><p =
class=3D"MsoNormal" style=3D"color:rgb( 0 , 0 , 0 );font-family:'segoe ui' =
, 'lucida sans' , sans-serif;font-size:14.16px;font-style:normal;font-weigh=
t:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-tran=
sform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:=
rgb( 255 , 255 , 255 )"><span lang=3D"EN-US" style=3D"font-size:10pt">subfl=
ow-1:&nbsp; &nbsp; &nbsp; segment-1&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; segment-3&n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment=
-4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; segment-7</span></p><p class=3D"MsoNormal" style=3D"color:rgb( 0 , 0 ,=
 0 );font-family:'segoe ui' , 'lucida sans' , sans-serif;font-size:14.16px;=
font-style:normal;font-weight:normal;letter-spacing:normal;line-height:norm=
al;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;=
margin:0px;background-color:rgb( 255 , 255 , 255 )"><span lang=3D"EN-US" st=
yle=3D"font-size:10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;=
bytes:1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; bytes:2=
01-300 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;bytes:301-400 &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; bytes:601-700</span></p><=
p class=3D"MsoNormal" style=3D"color:rgb( 0 , 0 , 0 );font-family:'segoe ui=
' , 'lucida sans' , sans-serif;font-size:14.16px;font-style:normal;font-wei=
ght:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-tr=
ansform:none;white-space:normal;word-spacing:0px;margin:0px;background-colo=
r:rgb( 255 , 255 , 255 )"><span lang=3D"EN-US" style=3D"font-size:10pt">&nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&n=
bsp;no map &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp;map for 1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;map for 201-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; map for 601=
-700</span></p><p class=3D"MsoNormal" style=3D"color:rgb( 0 , 0 , 0 );font-=
family:'segoe ui' , 'lucida sans' , sans-serif;font-size:14.16px;font-style=
:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-in=
dent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px=
;background-color:rgb( 255 , 255 , 255 )"><span lang=3D"EN-US" style=3D"fon=
t-size:10pt"><br></span></p><p class=3D"MsoNormal" style=3D"color:rgb( 0 , =
0 , 0 );font-family:'segoe ui' , 'lucida sans' , sans-serif;font-size:14.16=
px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:n=
ormal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0=
px;margin:0px;background-color:rgb( 255 , 255 , 255 )"><span lang=3D"EN-US"=
 style=3D"font-size:10pt"><br></span></p><p class=3D"MsoNormal" style=3D"co=
lor:rgb( 0 , 0 , 0 );font-family:'segoe ui' , 'lucida sans' , sans-serif;fo=
nt-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;=
line-height:normal;text-indent:0px;text-transform:none;white-space:normal;w=
ord-spacing:0px;margin:0px;background-color:rgb( 255 , 255 , 255 )"><br></p=
><p class=3D"MsoNormal" style=3D"color:rgb( 0 , 0 , 0 );font-family:'segoe =
ui' , 'lucida sans' , sans-serif;font-size:14.16px;font-style:normal;font-w=
eight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-=
transform:none;white-space:normal;word-spacing:0px;margin:0px;background-co=
lor:rgb( 255 , 255 , 255 )"><span lang=3D"EN-US" style=3D"font-size:10pt">s=
ubflow-2:&nbsp; &nbsp; &nbsp; &nbsp;segment-2&nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-5 &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-6 &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-8</span></p><p cl=
ass=3D"MsoNormal" style=3D"color:rgb( 0 , 0 , 0 );font-family:'segoe ui' , =
'lucida sans' , sans-serif;font-size:14.16px;font-style:normal;font-weight:=
normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transf=
orm:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rg=
b( 255 , 255 , 255 )"><span lang=3D"EN-US" style=3D"font-size:10pt">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bytes: 101-200 &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; bytes:401-500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bytes: 501-600 &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;bytes:701-800&nbsp;&nbsp;&nbsp;</spa=
n></p><p class=3D"MsoNormal" style=3D"color:rgb( 0 , 0 , 0 );font-family:'s=
egoe ui' , 'lucida sans' , sans-serif;font-size:14.16px;font-style:normal;f=
ont-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;=
text-transform:none;white-space:normal;word-spacing:0px;margin:0px;backgrou=
nd-color:rgb( 255 , 255 , 255 )"><span lang=3D"EN-US" style=3D"font-size:10=
pt">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp;map for 101-200 &nbsp; &nbsp; &nbsp; map for 401-600 &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp;no map &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 701-800=
</span></p><p class=3D"MsoNormal" style=3D"color:rgb( 0 , 0 , 0 );font-fami=
ly:'segoe ui' , 'lucida sans' , sans-serif;font-size:14.16px;font-style:nor=
mal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent=
:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;bac=
kground-color:rgb( 255 , 255 , 255 )"><span lang=3D"EN-US" style=3D"font-si=
ze:10pt"></span><br></p><p class=3D"MsoNormal" style=3D"color:rgb( 0 , 0 , =
0 );font-family:'segoe ui' , 'lucida sans' , sans-serif;font-size:14.16px;f=
ont-style:normal;font-weight:normal;letter-spacing:normal;line-height:norma=
l;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;m=
argin:0px;background-color:rgb( 255 , 255 , 255 )"><span lang=3D"EN-US" sty=
le=3D"font-size:10pt"></span><br></p>In the above case, segment-1 goes with=
out map and its map is included later in segment-3, the next data segment i=
n the same subflow. Further, &nbsp;in the above scheduling pattern, the map=
 in segment-3 cannot cover the &nbsp;data in segment-1 and segment-3, as so=
me &nbsp;data in between (segment-2) is transmitted through another subflow=
.&nbsp; With the proposed change, the map in segment-3 will become invalid =
and this will eventually break subflow-1, though this could be a corner cas=
e.</div><br><div>The question at this stage is why would segment-1 be trans=
mitted without its map. In the case of bidirectional data transfer, there c=
ould be a need to pack both timestamp and SACK &nbsp;options in a data segm=
ent, i.e., piggybacking of &nbsp;SACK with data. If we consider that timest=
amp takes 12 bytes and SACK, even with single block, &nbsp;takes another 10=
 bytes, the remaining 18 bytes option space is not adequate to carry data s=
equence signal with map, especially when DSN is 64 bit long. So the deliver=
y of either of the two (SACK or map) would be delayed.</div><br><div>As far=
 as I understand, RFC 2018 (TCP Selective Acknowledgement Options) implies =
that SACK should not be delayed. It states "If sent at all, SACK options SH=
OULD be included in all ACKs which do not ACK the highest sequence number i=
n the data receiver's queue". It also says "If data receiver generates SACK=
 options under any circumstance, it SHOULD generate them under all permitte=
d circumstances". &nbsp; So, as part of meeting the RFC 2018 requirements, =
if the combination of SACK and timestamp is given preference over DSS, data=
 segments could be transmitted without their map.&nbsp;</div><br><div>Anoth=
er case of delaying map could arise if the data sender prefers to send ADD_=
ADDR option, instead of map, in a data segment. It is nice that ADD_ADDR op=
tion can be delivered reliably in a pure ACK, but I think this is not the c=
ase with DSS at present.</div><br><div>If we adopt the proposed change, I t=
hink it might also be helpful to spell out how the receiver is supposed to =
behave, if it gets maps not meeting the MUST condition in the proposed chan=
ge.&nbsp; For example termination of the subflow with MP_TCPRST option (sec=
tion 3.6 in RFC 6824-bis) with appropriate reason code and T flag value to =
intimate the data sender the cause for subflow termination.&nbsp;&nbsp;</di=
v><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</div></div><div>With regards,</di=
v><br><div>Anil<br><br><div>Please can members of the WG express whether th=
ey are happy with these changes, or concerned.</div><br><div>Best regards,<=
/div><div>Alan</div><br><br>_______________________________________________=
<br>multipathtcp mailing list<br><a href=3D"mailto:multipathtcp@ietf.org" r=
el=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=
=3D"_blank">multipathtcp@ietf.org</a><br><a href=3D"https://www.ietf.org/ma=
ilman/listinfo/multipathtcp" rel=3D"nofollow%20noopener%20noreferrer nofoll=
ow noopener noreferrer" target=3D"_blank">https://www.ietf.org/mailman/list=
info/multipathtcp</a></div></div></div></div></div></div></div></div></div>=
</div><br></div></div></div>
<br>
<br>_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noopener%20noref=
errer nofollow noopener noreferrer" target=3D"_blank">multipathtcp@ietf.org=
</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"noref=
errer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
</blockquote></div></div></div></div></div></div><br></div></div>
<br>=
=0A<br>=
</body></h=
tml>
--=_92456e92-4e17-4635-acec-5109e21746f3--


From nobody Sun Feb  2 09:39:18 2020
Return-Path: <touch@strayalpha.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF4EC1200E5 for <multipathtcp@ietfa.amsl.com>; Sun,  2 Feb 2020 09:39:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level: 
X-Spam-Status: No, score=-1.218 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 BGpfx2v6q64W for <multipathtcp@ietfa.amsl.com>; Sun,  2 Feb 2020 09:39:12 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 99BF3120033 for <multipathtcp@ietf.org>; Sun,  2 Feb 2020 09:39:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=0IwyaZhj+sijoCvjkPGwu9woE2aILcV0jaFMDr2BXbo=; b=HFec+iBp5LScA83SuGiXkWM33 Hz6ddj2l6QK6wzBoXqLZhn2Uxff+Ze7H4UqCp90/bUNZ8PTbhtQkXZvj8Rkd6hvSWJazt3c/9ETJc vB+Y9YwV1prQv6XEpwAlhlsloCVZ16zkTeCxYucNJWG0JdKv8tj8xJXkqhUqk/EyYjs8PdDVl6vlc UY82iFU3cZB1N0b3CbsYyHIVOAWfyCZ3asJ4VnatWW+mCdShsN6mVSqDl+VQFZJMS2RbD4DAxUui5 cMQHBm05C+aEK4JHiarMdcYMKXsKG5xgrwqqFm8w8X2tLwhWRwdHiS9TOkHXUd3ZGdAkcXe5ieWBf snFQZz0EA==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:57674 helo=[192.168.1.8]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iyJD7-000IyE-SX; Sun, 02 Feb 2020 12:39:11 -0500
To: V Anil Kumar <anil@csir4pi.in>, Yoshifumi Nishida <nsd.ietf@gmail.com>
Cc: multipathtcp <multipathtcp@ietf.org>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in>
From: Joe Touch <touch@strayalpha.com>
Message-ID: <121d517b-dfe2-1c25-f0f4-08ec1334f48c@strayalpha.com>
Date: Sun, 2 Feb 2020 09:39:05 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <146023054.25180934.1580661581660@csir4pi.in>
Content-Type: multipart/alternative; boundary="------------225E470ECD052918FE74F6C3"
Content-Language: en-US
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/GsC6HZEpO1B1OZOC4SUksXLD5UE>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Feb 2020 17:39:16 -0000

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

RST doesn't "close" a connection; it aborts it. If a RST is sent, it 
should be sent *consistent with how TCP treats sending a RST* and not 
defined anew for this extension.

Joe

On 2/2/2020 8:39 AM, V Anil Kumar wrote:
> Hi Yoshi,
>
> Thanks for this point. In fact, I had initially not thought of a 
> scenario, where the map is being delivered through a retransmitted 
> data packet while its first transmission did not include the map. Now 
> I am just seeing the document (RFC 6824-bis) in this context.
>
> My understanding is that in scenarios like what I described in my 
> previous mail, RST is likely to happen whether we explicitly state so 
> or not. Please see the paragraph containing the below text in RFC 
> 6824-bis.
>
> "If a mapping for that subflow-level sequence space does not arrive 
> within a receive window of data, that subflow SHOULD be treated as 
> broken, closed with a RST, and any unmapped data silently discarded."
>
> if we assume that the map is included while retransmitting the data 
> (even though the first transmission did not contain the map for some 
> reasons),  we could argue that RST could be avoided provided that the 
> retransmission is triggered within a receive window of data. But the 
> question here would be how and when will the retransmission take 
> place. In this case, the subflow may not initiate the retransmission 
> of data by its own (i.e., no retransmission due to three duplicate 
> ACKs or RTO expiry at subflow level) as there is no segment loss at 
> subflow level sequence space. So there could be a high possibility of 
> RST happening even before the map delivery through retransmission.
>
> With regards,
>
> Anil
> ------------------------------------------------------------------------
> *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>
> *To: *"V Anil Kumar" <anil@csir4pi.in>
> *Cc: *"alan ford" <alan.ford@gmail.com>, "multipathtcp" 
> <multipathtcp@ietf.org>
> *Sent: *Saturday, February 1, 2020 3:39:51 AM
> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation 
> feedback
>
> Hi Anil,
>
> I have a question about your proposed text.
> I am actually wondering if we really want to terminate connection here.
>
> The packets without proper mappings will be treated as invalid and 
> will be discarded.
> If an implementation failed to attach proper mapping for some reasons 
> (e.g. option space), it might be able to attach the proper one when it 
> retransmits the packets. This also looks ok to me.
>
> I don't have strong preference for this. But, do we have a reason to 
> terminate connection?
>
> Thanks,
> --
> Yoshi
>
> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in 
> <mailto:anil@csir4pi.in>> wrote:
>
>     Hi,
>
>     I have some points related to the  modifications (Change 2) being
>     proposed on data sequence map. Please see them inline. Though I am
>     putting forward the below points, if the consensus is in favour of
>     the proposed change for reducing implementation complexity, I am
>     also OK with that as well.
>
>     ------------------------------------------------------------------------
>     *From: *"alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
>     *To: *multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>     *Sent: *Thursday, January 2, 2020 4:21:32 AM
>     *Subject: *[multipathtcp] RFC6824bis edits based on implementation
>     feedback
>
>     Hi all,
>     We’d love to get this to a state of completion as soon as
>     possible, and to this end I am starting a new thread on this
>     topic. In discussion with the chairs, it /is /possible to make the
>     desired changes in AUTH48 as long as there is WG consensus. The
>     discussion so far has been fairly limited in terms of participation.
>
>     I would ask the chairs please if it was possible to specify a time
>     bound for this discussion and a default conclusion.
>
>     Regarding the changes, in summary, there are two areas where
>     changes have been requested by the implementation community. As we
>     are the IETF we obviously have strong focus on “running code” and
>     so ease of implementing standards-compliant code is strongly
>     desirable. However, we do not wish to reduce functionality agreed
>     by the IETF community if it is considered a required feature by
>     the community.
>
>
>     *Change 1*
>     *
>     *
>     Change the sentence reading:
>
>     /   If B has data to send first, then the reliable delivery of the
>     ACK + MP_CAPABLE can be inferred by the receipt of this data with
>     an MPTCP Data Sequence Signal (DSS) option (Section 3.3).
>     /
>     To:
>
>     /   If B has data to send first, then the reliable delivery of the
>     ACK + MP_CAPABLE is ensured by the receipt of this data with an
>     MPTCP Data Sequence Signal (DSS) option (Section 3.3) containing a
>     DATA_ACK for the MP_CAPABLE (which is the first octet of the data
>     sequence space).
>     /
>     What this means:
>
>     The current text is concerned only with ensuring a path is MPTCP
>     capable, and so only cares that DSS option occurs on a data
>     packet. However, the MP_CAPABLE option is defined to occupy the
>     first octet of data sequence space and thus, if analogous to TCP,
>     must be acknowledged. >From an implementation point of view it
>     would make sense not to have this hanging around forever and
>     instead define it is acknowledged at the connection level as soon
>     as received. This change ensures the first data packet also
>     DATA_ACKs this MP_CAPABLE octet.
>
>
>     *Change 2*
>     *
>     *
>     Change the sentence reading:
>
>     /   A Data Sequence Mapping does not need to be included in every
>     MPTCP packet, as long as the subflow sequence space in that packet
>     is covered by a mapping known at the receiver./
>
>     To:
>
>     /   The mapping provided by a Data Sequence Mapping MUST apply to
>     some or all of the subflow sequence space in the TCP segment which
>     carries the option. It does not need to be included in every MPTCP
>     packet, as long as the subflow sequence space in that packet is
>     covered by a mapping known at the receiver.
>     /
>     What this means:
>
>     The current text does not place any restrictions on where a
>     mapping could appear. In theory a sender could define a thousand
>     different mappings up front, send them all, and expect a receiver
>     to store this and reassemble data according to these mappings as
>     it arrives. Indeed, this was never explicitly disallowed since it
>     “might have been useful”. The implementation community, however,
>     has expressed concerns over the difficulty of implementing this
>     open-endedly. How many mappings is it reasonable to store? Is
>     there a DoS risk here? Instead, it has been requested that thee
>     specification restricts the placement of the DSS option to being
>     within the subflow sequence space to which it applies.
>
>     Below are my comments on this. I had shared some of these points
>     in a previous thread that you had initiated in the same context.
>
>     Transmitting large number of non-contiguous data sequence maps
>     could be a misbehaviour (map-flooding), though it is not clear
>     whether this can go to the extent of causing a potential DoS to
>     the data receiver. So some sort of restriction on this could be
>     useful. One approach could be to insist that the data sender
>     should ensure that the map being transmitted is for in-window
>     data, as per the receiver advertised window. A receiver should
>     anyhow be willing to store the maps for in-window data to deal
>     with packet loss.. For example, when a window of data segments
>     (say 1 to 64) is transmitted, each carrying its corresponding map,
>     and segment-1 is lost, the maps for the remaining 63 need to be
>     stored till the lost segment is retransmitted. Of course, in this
>     case the maps will be stored at the receiver side along with their
>     corresponding data. But the need to store multiple maps for
>     in-window data would still be there.
>
>     The problem with the proposed change (restriction) is that a data
>     sender may find it difficult, in case a need arise to slightly
>     delay the map delivery by few segments, i.e., sending some data
>     first without map, and then send the corresponding map in a later
>     segment, as shown below:
>
>     subflow-1:      segment-1 segment-3 segment-4 segment-7
>
>                           bytes:1-100 bytes:201-300  bytes:301-400
>     bytes:601-700
>
>                           no map  map for 1-100            map for
>     201-400         map for 601-700
>
>
>
>
>     subflow-2:       segment-2 segment-5 segment-6 segment-8
>
>                            bytes: 101-200 bytes:401-500         bytes:
>     501-600  bytes:701-800
>
>                            map for 101-200 map for 401-600          
>      no map  map for 701-800
>
>
>
>     In the above case, segment-1 goes without map and its map is
>     included later in segment-3, the next data segment in the same
>     subflow. Further,  in the above scheduling pattern, the map in
>     segment-3 cannot cover the  data in segment-1 and segment-3, as
>     some  data in between (segment-2) is transmitted through another
>     subflow..  With the proposed change, the map in segment-3 will
>     become invalid and this will eventually break subflow-1, though
>     this could be a corner case.
>
>     The question at this stage is why would segment-1 be transmitted
>     without its map. In the case of bidirectional data transfer, there
>     could be a need to pack both timestamp and SACK  options in a data
>     segment, i.e., piggybacking of  SACK with data. If we consider
>     that timestamp takes 12 bytes and SACK, even with single block,
>      takes another 10 bytes, the remaining 18 bytes option space is
>     not adequate to carry data sequence signal with map, especially
>     when DSN is 64 bit long. So the delivery of either of the two
>     (SACK or map) would be delayed.
>
>     As far as I understand, RFC 2018 (TCP Selective Acknowledgement
>     Options) implies that SACK should not be delayed. It states "If
>     sent at all, SACK options SHOULD be included in all ACKs which do
>     not ACK the highest sequence number in the data receiver's queue".
>     It also says "If data receiver generates SACK options under any
>     circumstance, it SHOULD generate them under all permitted
>     circumstances". So, as part of meeting the RFC 2018 requirements,
>     if the combination of SACK and timestamp is given preference over
>     DSS, data segments could be transmitted without their map.
>
>     Another case of delaying map could arise if the data sender
>     prefers to send ADD_ADDR option, instead of map, in a data
>     segment. It is nice that ADD_ADDR option can be delivered reliably
>     in a pure ACK, but I think this is not the case with DSS at present.
>
>     If we adopt the proposed change, I think it might also be helpful
>     to spell out how the receiver is supposed to behave, if it gets
>     maps not meeting the MUST condition in the proposed change.  For
>     example termination of the subflow with MP_TCPRST option (section
>     3.6 in RFC 6824-bis) with appropriate reason code and T flag value
>     to intimate the data sender the cause for subflow termination.
>     With regards,
>
>     Anil
>
>     Please can members of the WG express whether they are happy with
>     these changes, or concerned.
>
>     Best regards,
>     Alan
>
>
>     _______________________________________________
>     multipathtcp mailing list
>     multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>     https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
>
>     _______________________________________________
>     multipathtcp mailing list
>     multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>     https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
>
>
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp

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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>RST doesn't "close" a connection; it aborts it. If a RST is sent,
      it should be sent *consistent with how TCP treats sending a RST*
      and not defined anew for this extension. <br>
    </p>
    <p>Joe<br>
    </p>
    <div class="moz-cite-prefix">On 2/2/2020 8:39 AM, V Anil Kumar
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:146023054.25180934.1580661581660@csir4pi.in">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div style="font-family: arial, helvetica, sans-serif; font-size:
        style=" font-size:="" 12pt;="" color:="" #000000"="">
        <div data-marker="__QUOTED_TEXT__">
          <div style="font-family:'arial' , 'helvetica' , sans-serif">
            <div>Hi Yoshi,</div>
            <br>
            <div>Thanks for this point. In fact, I had initially not
              thought of a scenario, where the map is being delivered
              through a retransmitted data packet while its first
              transmission did not include the map. Now I am just seeing
              the document (RFC 6824-bis) in this context.</div>
            <br>
            <div>My understanding is that in scenarios like what I
              described in my previous mail, RST is likely to happen
              whether we explicitly state so or not. Please see the
              paragraph containing the below text in RFC 6824-bis.  </div>
            <br>
            <div>"If a mapping for that subflow-level sequence space
              does not arrive within a receive window of data, that
              subflow SHOULD be treated as broken, closed with a RST,
              and any unmapped data silently discarded."</div>
            <br>
            <div>if we assume that the map is included while
              retransmitting the data (even though the first
              transmission did not contain the map for some reasons),
               we could argue that RST could be avoided provided that
              the retransmission is triggered within a receive window of
              data. But the question here would be how and when will the
              retransmission take place. In this case, the subflow may
              not initiate the retransmission of data by its own (i.e.,
              no retransmission due to three duplicate ACKs or RTO
              expiry at subflow level) as there is no segment loss at
              subflow level sequence space. So there could be a high
              possibility of RST happening even before the map delivery
              through retransmission. </div>
            <br>
            <div>With regards, </div>
            <br>
            <div>Anil</div>
            <div> </div>
            <hr id="zwchr">
            <div><b>From: </b>"Yoshifumi Nishida"
              <a class="moz-txt-link-rfc2396E" href="mailto:nsd.ietf@gmail.com">&lt;nsd.ietf@gmail.com&gt;</a><br>
              <b>To: </b>"V Anil Kumar" <a class="moz-txt-link-rfc2396E" href="mailto:anil@csir4pi.in">&lt;anil@csir4pi.in&gt;</a><br>
              <b>Cc: </b>"alan ford" <a class="moz-txt-link-rfc2396E" href="mailto:alan.ford@gmail.com">&lt;alan.ford@gmail.com&gt;</a>,
              "multipathtcp" <a class="moz-txt-link-rfc2396E" href="mailto:multipathtcp@ietf.org">&lt;multipathtcp@ietf.org&gt;</a><br>
              <b>Sent: </b>Saturday, February 1, 2020 3:39:51 AM<br>
              <b>Subject: </b>Re: [multipathtcp] RFC6824bis edits based
              on implementation feedback<br>
            </div>
            <br>
            <div>
              <div dir="ltr">
                <div dir="ltr">
                  <div dir="ltr">
                    <div>Hi Anil,</div>
                    <br>
                    <div>I have a question about your proposed text.</div>
                    <div>
                      <div>I am actually wondering if we really want to
                        terminate connection here. </div>
                    </div>
                    <br>
                    <div>The packets without proper mappings will be
                      treated as invalid and will be discarded. </div>
                    <div>If an implementation failed to attach proper
                      mapping for some reasons (e.g. option space), it
                      might be able to attach the proper one when it
                      retransmits the packets. This also looks ok to me.</div>
                    <br>
                    <div>I don't have strong preference for this. But,
                      do we have a reason to terminate connection?</div>
                    <br>
                    <div>Thanks,</div>
                    <div>--<br>
                    </div>
                    <div>Yoshi</div>
                    <br>
                    <div>
                      <div dir="ltr">On Mon, Jan 13, 2020 at 10:28 AM V
                        Anil Kumar &lt;<a href="mailto:anil@csir4pi.in"
                          rel="nofollow%20noopener%20noreferrer nofollow
                          noopener noreferrer" target="_blank"
                          moz-do-not-send="true">anil@csir4pi.in</a>&gt;
                        wrote:<br>
                      </div>
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px 0.8ex;border-left:1px solid rgb( 204 ,
                        204 , 204 );padding-left:1ex">
                        <div>
                          <div>
                            <div>
                              <div style="font-family:'arial' ,
                                'helvetica' , sans-serif">
                                <div><span
                                    style="font-size:12pt;line-height:1.3">Hi,</span><br>
                                </div>
                                <div>
                                  <div style="font-family:'arial' ,
                                    'helvetica' , sans-serif">
                                    <div style="font-family:'arial' ,
                                      'helvetica' , sans-serif">
                                      <div style="font-family:'arial' ,
                                        'helvetica' , sans-serif">
                                        <div style="font-family:'arial'
                                          , 'helvetica' , sans-serif">
                                          <div
                                            style="font-family:'arial' ,
                                            'helvetica' , sans-serif">
                                            <div
                                              style="font-family:'arial'
                                              , 'helvetica' ,
                                              sans-serif">
                                              <div
                                                style="font-family:'arial'
                                                , 'helvetica' ,
                                                sans-serif"><br>
                                                <div>I have some points
                                                  related to the
                                                   modifications (Change
                                                  2) being proposed on
                                                  data sequence map.
                                                  Please see them
                                                  inline. <span
                                                    style="color:rgb( 0
                                                    , 0 , 0
                                                    );font-family:'arial'
                                                    , 'helvetica' ,
sans-serif;font-size:16px;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(
                                                    255 , 255 , 255
                                                    );float:none;display:inline">Though
                                                    I am putting forward
                                                    the below points, if
                                                    the consensus is in
                                                    favour of the
                                                    proposed change for
                                                    reducing
                                                    implementation
                                                    complexity, I am
                                                    also OK with that as
                                                    well. </span><br>
                                                </div>
                                                <br>
                                                <hr
                                                  id="gmail-m_7687184382299596774zwchr">
                                                <div><b>From: </b>"alan
                                                  ford" &lt;<a
                                                    href="mailto:alan.ford@gmail.com"
rel="nofollow%20noopener%20noreferrer nofollow noopener noreferrer"
                                                    target="_blank"
                                                    moz-do-not-send="true">alan.ford@gmail.com</a>&gt;<br>
                                                  <b>To: </b><a
                                                    href="mailto:multipathtcp@ietf.org"
rel="nofollow%20noopener%20noreferrer nofollow noopener noreferrer"
                                                    target="_blank"
                                                    moz-do-not-send="true">multipathtcp@ietf.org</a><br>
                                                  <b>Sent: </b>Thursday,
                                                  January 2, 2020
                                                  4:21:32 AM<br>
                                                  <b>Subject: </b>[multipathtcp]
                                                  RFC6824bis edits based
                                                  on implementation
                                                  feedback<br>
                                                </div>
                                                <br>
                                                <div>Hi all,<br>
                                                  <div>We’d love to get
                                                    this to a state of
                                                    completion as soon
                                                    as possible, and to
                                                    this end I am
                                                    starting a new
                                                    thread on this
                                                    topic. In discussion
                                                    with the chairs, it
                                                    <i>is </i>possible
                                                    to make the desired
                                                    changes in AUTH48 as
                                                    long as there is WG
                                                    consensus. The
                                                    discussion so far
                                                    has been fairly
                                                    limited in terms of
                                                    participation.</div>
                                                  <br>
                                                  <div>I would ask the
                                                    chairs please if it
                                                    was possible to
                                                    specify a time bound
                                                    for this discussion
                                                    and a default
                                                    conclusion.</div>
                                                  <br>
                                                  <div>Regarding the
                                                    changes, in summary,
                                                    there are two areas
                                                    where changes have
                                                    been requested by
                                                    the implementation
                                                    community. As we are
                                                    the IETF we
                                                    obviously have
                                                    strong focus on
                                                    “running code” and
                                                    so ease of
                                                    implementing
                                                    standards-compliant
                                                    code is strongly
                                                    desirable. However,
                                                    we do not wish to
                                                    reduce functionality
                                                    agreed by the IETF
                                                    community if it is
                                                    considered a
                                                    required feature by
                                                    the community.</div>
                                                  <br>
                                                  <br>
                                                  <div><b>Change 1</b></div>
                                                  <div><b><br>
                                                    </b></div>
                                                  <div>Change the
                                                    sentence reading:<br>
                                                    <br>
                                                    <i>   If B has data
                                                      to send first,
                                                      then the reliable
                                                      delivery of the
                                                      ACK + MP_CAPABLE
                                                      can be inferred by
                                                      the receipt of
                                                      this data with an
                                                      MPTCP Data
                                                      Sequence Signal
                                                      (DSS) option
                                                      (Section 3.3). <br>
                                                    </i><br>
                                                    To:<br>
                                                    <br>
                                                    <i>   If B has data
                                                      to send first,
                                                      then the reliable
                                                      delivery of the
                                                      ACK + MP_CAPABLE
                                                      is ensured by the
                                                      receipt of this
                                                      data with an MPTCP
                                                      Data Sequence
                                                      Signal (DSS)
                                                      option (Section
                                                      3.3) containing a
                                                      DATA_ACK for the
                                                      MP_CAPABLE (which
                                                      is the first octet
                                                      of the data
                                                      sequence space).<br>
                                                    </i><br>
                                                  </div>
                                                  <div>What this means:</div>
                                                  <br>
                                                  <div>The current text
                                                    is concerned only
                                                    with ensuring a path
                                                    is MPTCP capable,
                                                    and so only cares
                                                    that DSS option
                                                    occurs on a data
                                                    packet. However, the
                                                    MP_CAPABLE option is
                                                    defined to occupy
                                                    the first octet of
                                                    data sequence space
                                                    and thus, if
                                                    analogous to TCP,
                                                    must be
                                                    acknowledged.
                                                    &gt;From an
                                                    implementation point
                                                    of view it would
                                                    make sense not to
                                                    have this hanging
                                                    around forever and
                                                    instead define it is
                                                    acknowledged at the
                                                    connection level as
                                                    soon as received.
                                                    This change ensures
                                                    the first data
                                                    packet also
                                                    DATA_ACKs this
                                                    MP_CAPABLE octet.</div>
                                                  <br>
                                                  <br>
                                                  <div><b>Change 2</b></div>
                                                  <div><b><br>
                                                    </b></div>
                                                  <div>Change the
                                                    sentence reading:<br>
                                                    <br>
                                                    <i>   A Data
                                                      Sequence Mapping
                                                      does not need to
                                                      be included in
                                                      every MPTCP
                                                      packet, as long as
                                                      the subflow
                                                      sequence space in
                                                      that packet is
                                                      covered by a
                                                      mapping known at
                                                      the receiver.</i><br>
                                                    <br>
                                                    To:<br>
                                                    <br>
                                                    <i>   The mapping
                                                      provided by a Data
                                                      Sequence Mapping
                                                      MUST apply to some
                                                      or all of the
                                                      subflow sequence
                                                      space in the TCP
                                                      segment which
                                                      carries the
                                                      option. It does
                                                      not need to be
                                                      included in every
                                                      MPTCP packet, as
                                                      long as the
                                                      subflow sequence
                                                      space in that
                                                      packet is covered
                                                      by a mapping known
                                                      at the receiver.<br>
                                                    </i><br>
                                                    What this means:</div>
                                                  <br>
                                                  <div>The current text
                                                    does not place any
                                                    restrictions on
                                                    where a mapping
                                                    could appear. In
                                                    theory a sender
                                                    could define a
                                                    thousand different
                                                    mappings up front,
                                                    send them all, and
                                                    expect a receiver to
                                                    store this and
                                                    reassemble data
                                                    according to these
                                                    mappings as it
                                                    arrives. Indeed,
                                                    this was never
                                                    explicitly
                                                    disallowed since it
                                                    “might have been
                                                    useful”. The
                                                    implementation
                                                    community, however,
                                                    has expressed
                                                    concerns over the
                                                    difficulty of
                                                    implementing this
                                                    open-endedly. How
                                                    many mappings is it
                                                    reasonable to store?
                                                    Is there a DoS risk
                                                    here? Instead, it
                                                    has been requested
                                                    that thee
                                                    specification
                                                    restricts the
                                                    placement of the DSS
                                                    option to being
                                                    within the subflow
                                                    sequence space to
                                                    which it applies.</div>
                                                  <br>
                                                  <div>Below are my
                                                    comments on this. I
                                                    had shared some of
                                                    these points in a
                                                    previous thread that
                                                    you had initiated in
                                                    the same context. </div>
                                                  <br>
                                                  <div>Transmitting
                                                    large number of
                                                    non-contiguous data
                                                    sequence maps could
                                                    be a misbehaviour
                                                    (map-flooding),
                                                    though it is not
                                                    clear whether this
                                                    can go to the extent
                                                    of causing a
                                                    potential DoS to the
                                                    data receiver. So
                                                    some sort of
                                                    restriction on this
                                                    could be useful. 
                                                    One approach could
                                                    be to insist that
                                                    the data sender
                                                    should ensure that
                                                    the map being
                                                    transmitted is for
                                                    in-window data, as
                                                    per the receiver
                                                    advertised window. A
                                                    receiver should
                                                    anyhow be willing to
                                                    store the maps for
                                                    in-window data to
                                                    deal with packet
                                                    loss.. For example,
                                                    when a window of
                                                    data segments (say 1
                                                    to 64) is
                                                    transmitted, each
                                                    carrying its
                                                    corresponding map,
                                                    and segment-1 is
                                                    lost, the maps for
                                                    the remaining 63
                                                    need to be stored
                                                    till the lost
                                                    segment is
                                                    retransmitted. Of
                                                    course, in this case
                                                    the maps will be
                                                    stored at the
                                                    receiver side along
                                                    with their
                                                    corresponding data.
                                                    But the need to
                                                    store multiple maps
                                                    for in-window data
                                                    would still be
                                                    there.</div>
                                                  <br>
                                                  <div><span
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'arial'
                                                      , 'helvetica' ,
sans-serif;font-size:16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:20.8px;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;background-color:rgb(
                                                      255 , 255 , 255
                                                      );display:inline">The
                                                      problem with the
                                                      proposed change
                                                      (restriction) is
                                                      that a data sender
                                                      may find it
                                                      difficult, in case
                                                      a need arise to
                                                      slightly delay the
                                                      map delivery by
                                                      few segments,
                                                      i.e., sending some
                                                      data first without
                                                      map, and then send
                                                      the corresponding
                                                      map in a later
                                                      segment, as shown
                                                      below:</span><br>
                                                  </div>
                                                  <br>
                                                  <div>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US">subflow-1:      segment-1   
                                                                      
                                                        segment-3       
                                                                   
                                                        segment-4      
                                                                       
                                                        segment-7</span></p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US">                      bytes:1-100  
                                                                     
                                                        bytes:201-300  
                                                                 
                                                         bytes:301-400  
                                                                     
                                                        bytes:601-700</span></p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US">                      no map        
                                                                     
                                                         map for 1-100  
                                                                   map
                                                        for 201-400    
                                                                map for
                                                        601-700</span></p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US"><br>
                                                      </span></p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US"><br>
                                                      </span></p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><br>
                                                    </p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US">subflow-2:       segment-2         
                                                               
                                                        segment-5      
                                                                     
                                                        segment-6      
                                                                       
                                                        segment-8</span></p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US">                       bytes:
                                                        101-200        
                                                         
                                                        bytes:401-500      
                                                                bytes:
                                                        501-600        
                                                             
                                                         bytes:701-800   </span></p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US">                       map for
                                                        101-200      
                                                        map for 401-600
                                                                   no
                                                        map            
                                                                     
                                                         map for 701-800</span></p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US"></span><br>
                                                    </p>
                                                    <p class="MsoNormal"
                                                      style="color:rgb(
                                                      0 , 0 , 0
                                                      );font-family:'segoe
                                                      ui' , 'lucida
                                                      sans' ,
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(
                                                      255 , 255 , 255 )"><span
style="font-size:10pt" lang="EN-US"></span><br>
                                                    </p>
                                                    In the above case,
                                                    segment-1 goes
                                                    without map and its
                                                    map is included
                                                    later in segment-3,
                                                    the next data
                                                    segment in the same
                                                    subflow. Further,
                                                     in the above
                                                    scheduling pattern,
                                                    the map in segment-3
                                                    cannot cover the
                                                     data in segment-1
                                                    and segment-3, as
                                                    some  data in
                                                    between (segment-2)
                                                    is transmitted
                                                    through another
                                                    subflow..  With the
                                                    proposed change, the
                                                    map in segment-3
                                                    will become invalid
                                                    and this will
                                                    eventually break
                                                    subflow-1, though
                                                    this could be a
                                                    corner case.</div>
                                                  <br>
                                                  <div>The question at
                                                    this stage is why
                                                    would segment-1 be
                                                    transmitted without
                                                    its map. In the case
                                                    of bidirectional
                                                    data transfer, there
                                                    could be a need to
                                                    pack both timestamp
                                                    and SACK  options in
                                                    a data segment,
                                                    i.e., piggybacking
                                                    of  SACK with data.
                                                    If we consider that
                                                    timestamp takes 12
                                                    bytes and SACK, even
                                                    with single block,
                                                     takes another 10
                                                    bytes, the remaining
                                                    18 bytes option
                                                    space is not
                                                    adequate to carry
                                                    data sequence signal
                                                    with map, especially
                                                    when DSN is 64 bit
                                                    long. So the
                                                    delivery of either
                                                    of the two (SACK or
                                                    map) would be
                                                    delayed.</div>
                                                  <br>
                                                  <div>As far as I
                                                    understand, RFC 2018
                                                    (TCP Selective
                                                    Acknowledgement
                                                    Options) implies
                                                    that SACK should not
                                                    be delayed. It
                                                    states "If sent at
                                                    all, SACK options
                                                    SHOULD be included
                                                    in all ACKs which do
                                                    not ACK the highest
                                                    sequence number in
                                                    the data receiver's
                                                    queue". It also says
                                                    "If data receiver
                                                    generates SACK
                                                    options under any
                                                    circumstance, it
                                                    SHOULD generate them
                                                    under all permitted
                                                    circumstances".  
                                                    So, as part of
                                                    meeting the RFC 2018
                                                    requirements, if the
                                                    combination of SACK
                                                    and timestamp is
                                                    given preference
                                                    over DSS, data
                                                    segments could be
                                                    transmitted without
                                                    their map. </div>
                                                  <br>
                                                  <div>Another case of
                                                    delaying map could
                                                    arise if the data
                                                    sender prefers to
                                                    send ADD_ADDR
                                                    option, instead of
                                                    map, in a data
                                                    segment. It is nice
                                                    that ADD_ADDR option
                                                    can be delivered
                                                    reliably in a pure
                                                    ACK, but I think
                                                    this is not the case
                                                    with DSS at present.</div>
                                                  <br>
                                                  <div>If we adopt the
                                                    proposed change, I
                                                    think it might also
                                                    be helpful to spell
                                                    out how the receiver
                                                    is supposed to
                                                    behave, if it gets
                                                    maps not meeting the
                                                    MUST condition in
                                                    the proposed
                                                    change.  For example
                                                    termination of the
                                                    subflow with
                                                    MP_TCPRST option
                                                    (section 3.6 in RFC
                                                    6824-bis) with
                                                    appropriate reason
                                                    code and T flag
                                                    value to intimate
                                                    the data sender the
                                                    cause for subflow
                                                    termination.  </div>
                                                  <div>         </div>
                                                </div>
                                                <div>With regards,</div>
                                                <br>
                                                <div>Anil<br>
                                                  <br>
                                                  <div>Please can
                                                    members of the WG
                                                    express whether they
                                                    are happy with these
                                                    changes, or
                                                    concerned.</div>
                                                  <br>
                                                  <div>Best regards,</div>
                                                  <div>Alan</div>
                                                  <br>
                                                  <br>
_______________________________________________<br>
                                                  multipathtcp mailing
                                                  list<br>
                                                  <a
                                                    href="mailto:multipathtcp@ietf.org"
rel="nofollow%20noopener%20noreferrer nofollow noopener noreferrer"
                                                    target="_blank"
                                                    moz-do-not-send="true">multipathtcp@ietf.org</a><br>
                                                  <a
                                                    href="https://www.ietf.org/mailman/listinfo/multipathtcp"
rel="nofollow%20noopener%20noreferrer nofollow noopener noreferrer"
                                                    target="_blank"
                                                    moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/multipathtcp</a></div>
                                              </div>
                                            </div>
                                          </div>
                                        </div>
                                      </div>
                                    </div>
                                  </div>
                                </div>
                              </div>
                              <br>
                            </div>
                          </div>
                        </div>
                        <br>
                        <br>
                        _______________________________________________<br>
                        multipathtcp mailing list<br>
                        <a href="mailto:multipathtcp@ietf.org"
                          rel="nofollow%20noopener%20noreferrer nofollow
                          noopener noreferrer" target="_blank"
                          moz-do-not-send="true">multipathtcp@ietf.org</a><br>
                        <a
                          href="https://www.ietf.org/mailman/listinfo/multipathtcp"
rel="noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener
                          noreferrer" target="_blank"
                          moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
          <br>
        </div>
      </div>
      <br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
multipathtcp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/multipathtcp">https://www.ietf.org/mailman/listinfo/multipathtcp</a>
</pre>
    </blockquote>
  </body>
</html>

--------------225E470ECD052918FE74F6C3--


From nobody Mon Feb  3 06:24:19 2020
Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C0BC120096 for <multipathtcp@ietfa.amsl.com>; Mon,  3 Feb 2020 06:24:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 z8fy-g-2lv-b for <multipathtcp@ietfa.amsl.com>; Mon,  3 Feb 2020 06:24:13 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B380120026 for <multipathtcp@ietf.org>; Mon,  3 Feb 2020 06:24:12 -0800 (PST)
Received: from tpw09926dag18f.domain1.systemhost.net (10.9.212.26) by RDW083A012ED68.bt.com (10.187.98.38) with Microsoft SMTP Server (TLS) id 14.3.439.0; Mon, 3 Feb 2020 14:21:41 +0000
Received: from tpw09926dag13e.domain1.systemhost.net (10.9.212.13) by tpw09926dag18f.domain1.systemhost.net (10.9.212.26) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 3 Feb 2020 14:24:07 +0000
Received: from bwp09926081.bt.com (10.36.82.112) by tpw09926dag13e.domain1.systemhost.net (10.9.212.13) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 3 Feb 2020 14:24:07 +0000
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.56) by smtpe1.intersmtp.com (10.36.82.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Mon, 3 Feb 2020 14:23:52 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ezM3wUvbfmW0doYBU14WqoiUjnKbZAKSQgTJ2EGcH8aB9I3SV8ivOdVxfdEKREsrS3mfpI7G6EgDRuuy36yPZd5FCSEEZ0AJhZTkqDvP4doLsYsekpvJA67274wQlLRfIDLFq6+hjwb1qIbSzUEuips0NjRPfGY1Rshii3WC6876u2gQlAK5LZmvBGfe6not9IIuIHKohyMd1oW/o8GJ4luo6oezUcnQkOOExBseqYZ4fSxxYXvKnvtc33g6Ncewg222rIr/pPF8eZ4S5WJxTfJgMUdpTKtl2SM/SZOX7XNlon3NMEiQ/eWSI4BCon8gO5liuSjg3EuFSggliZ3teA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GlSNYOmAieGdCB6kEid9P6FC5q6HLreKf40JCF1RV78=; b=MYCVhSbJiB/u+RNNdI5UPn/oFYZj0K8lCyVLZ6u++bPAPGePJ/eVELrjrkqTqyvUnVgXjwTM9xdvHa493qUF9ubk30UQnT5Yec/EjIdGivqpF/lZB4/JdOpwNMSEHgTZntt/T1W9OeZ60CBQtrG4ntRyLed12LsYwv9f61h2eF+TSBTZmyBoxl0akawNMi6lNIqwdABFQdnj+MKU7qxLDq5rPPA6qbcmLfe1K8ssRFi7uijd+VXd59Rp6nk+7jLq9wQzOJxCQHYdISKlFDOFTjtk1+H0/3TzgyudGdQ5vYduzwF2zwLCZ/oUPnF2ErS8eI2QzDz0ZyQ1C6YrRVzODQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GlSNYOmAieGdCB6kEid9P6FC5q6HLreKf40JCF1RV78=; b=w78X9w1OSviUMqxq05eLl3gOnPQ6ZaKMTpO1qBBZBvSI4qGS51DkAMCUwUXkab5jV0YhRTV9L4y0weUcSPEkzDlGpkN076CYsIyZRGIRYBClYxIIkg0a0jfIWttXJ4PG+8FTPE7y0o+NhhW1wt29uZMOV6oOG+u741cth14IvLk=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXP123MB1866.GBRP123.PROD.OUTLOOK.COM (20.176.159.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.29; Mon, 3 Feb 2020 14:24:04 +0000
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c]) by LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c%7]) with mapi id 15.20.2686.031; Mon, 3 Feb 2020 14:24:03 +0000
From: <philip.eardley@bt.com>
To: <touch@strayalpha.com>, <anil@csir4pi.in>, <nsd.ietf@gmail.com>
CC: <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] RFC6824bis edits based on implementation feedback
Thread-Index: AQHV2efjE0t2RY94ZkaZvM9k72KnJ6gIK4SAgAESv0A=
Date: Mon, 3 Feb 2020 14:24:03 +0000
Message-ID: <LNXP123MB2587FEF165A7C4B988799EE8EB000@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <121d517b-dfe2-1c25-f0f4-08ec1334f48c@strayalpha.com>
In-Reply-To: <121d517b-dfe2-1c25-f0f4-08ec1334f48c@strayalpha.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com; 
x-originating-ip: [217.33.61.67]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 242ad0c4-0e68-4e22-4b09-08d7a8b4b854
x-ms-traffictypediagnostic: LNXP123MB1866:
x-microsoft-antispam-prvs: <LNXP123MB186612D90600FE3AA54FD172EB000@LNXP123MB1866.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0302D4F392
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(39860400002)(376002)(346002)(136003)(199004)(189003)(8936002)(4326008)(81166006)(316002)(33656002)(86362001)(81156014)(5660300002)(186003)(8676002)(9686003)(110136005)(966005)(6506007)(478600001)(53546011)(71200400001)(26005)(66476007)(66556008)(64756008)(66946007)(66446008)(52536014)(7696005)(76116006)(30864003)(2906002)(55016002); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXP123MB1866; H:LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: JuQZhryYhtj9HnuoxelRJHBiE+9Qe17i10k2nCof1twQO1Pb0rS4Az2ErDLPS7Ujm4T5+A9gyoqCr9FwnVBAtwvJH7hsuT3MgrqCN1cBvYwkjLq+bHHOFhPONpqw0HjZ9iCxVdHn3ItkNDZU/MKMK9Iugehp9sn+OBQmf7SUodvpemPHjWeCLd8AoWUqB8h0B8UNqkvr9nP8/+tCe5e4kAhUYJI8HZeBDTmi4NHiDl5ydMRQ+YF5wB/+GIih4i0jq5g/V/eScXgAx+ygrUJqZ3tIGgkiwR5uT7bupWzgduaTn0LJX28rT98fPyr+Rgsjw42VHd83vsKeyGJmkze4vIKOISC7YAd2qKXAAnXEyiUSqxfOwD4hjezvzZL1/BSBnCgH6ksAxck0mKvwlknXc4YENQjlU8zMy8dxK/zjhTE7ccWmSFm7LX7ZzLSGLfS8K1mGkHAkrqgDlZZewNRfMIeF0nEmRBwLh1/bo8HpY5LJfhrSM22rjcdzednGIIrB4jPpv3o/2SRq+5jTsfZaqg==
x-ms-exchange-antispam-messagedata: jKJbqrAAJ3Qhak1j08mUSApZmMqUY+CDKcWJrUO0BgYS0b0plwYElfuUjAQBrRd3qs3T3RRlKunTCVzZjlbqfvtheFXvDc+K65THY8aF0B2C9bqkPU+dGQZDv/zi0EMtS+RWVji6iBnfz6v/MkEStw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB2587FEF165A7C4B988799EE8EB000LNXP123MB2587GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 242ad0c4-0e68-4e22-4b09-08d7a8b4b854
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2020 14:24:03.5226 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jJg1TNdikIwTvHbfW0RlttcS69vrcAH93oyv64lx/x9zbXvjpQhPTHWt/9+vaHSVkBA5sAcI5CYLsKrkfaFsbQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB1866
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/0Qa3Lvq8skQMI7LAdNKKHh8ngIU>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2020 14:24:17 -0000

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

PDwgaWYgd2UgYXNzdW1lIHRoYXQgdGhlIG1hcCBpcyBpbmNsdWRlZCB3aGlsZSByZXRyYW5zbWl0
dGluZyB0aGUgZGF0YSAoZXZlbiB0aG91Z2ggdGhlIGZpcnN0IHRyYW5zbWlzc2lvbiBkaWQgbm90
IGNvbnRhaW4gdGhlIG1hcCBmb3Igc29tZSByZWFzb25zKSwgID4+DQpBYm91dCDigJxmb3Igc29t
ZSByZWFzb27igJ0uIElzIHRoaXMgc29tZXRoaW5nIHlvdeKAmXZlIHNlZW4gKG9yIGV4cGVjdCB0
byBzZWUpIHJlZ3VsYXJseSwgb3IgaXMgdGhpcyBzb21ldGhpbmcgdGhhdCB3b3VsZCBiZSByYXJl
Pw0KDQpBcyB5b3Ugc2F5LCB0aGUgY3VycmVudCB3b3JkaW5nIGhhcyBhIFNIT1VMRCwgcmF0aGVy
IHRoYW4gYSBNVVNUIOKAkyB3aGljaCB3b3VsZCBsZWF2ZSBhIGJpdCBvZiByb29tIHRvIGRvIHNv
bWV0aGluZyBkaWZmZXJlbnQgaWYgdGhlcmUgd2VyZSBzcGVjaWZpYyAoYnV0IHVubGlrZWx5KSBj
aXJjdW1zdGFuY2VzIHRoYXQgbWVyaXRlZCBkb2luZyBzb21ldGhpbmcgZGlmZmVyZW50Lg0KDQoN
ClJTVCBmb3JjZXMgdGhlIGltbWVkaWF0ZSBjbG9zdXJlIG9mIGFuIE1QVENQIHN1YmZsb3cuIE1Q
X0ZBU1RDTE9TRSBmb3JjZXMgdGhlIGltbWVkaWF0ZSBjbG9zdXJlIG9mIHRoZSBNUFRDUCBjb25u
ZWN0aW9uICh3aGljaCBjYW4gYWxzbyBiZSBhY2hpZXZlZCBieSBzZW5kaW5nIGEgUlNUIG9uIGFs
bCBzdWJmbG93cykuDQoNCkJlc3Qgd2lzaGVzDQpwaGlsDQoNCkZyb206IG11bHRpcGF0aHRjcCA8
bXVsdGlwYXRodGNwLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBKb2UgVG91Y2gNClNl
bnQ6IDAyIEZlYnJ1YXJ5IDIwMjAgMTc6MzkNClRvOiBWIEFuaWwgS3VtYXIgPGFuaWxAY3NpcjRw
aS5pbj47IFlvc2hpZnVtaSBOaXNoaWRhIDxuc2QuaWV0ZkBnbWFpbC5jb20+DQpDYzogbXVsdGlw
YXRodGNwIDxtdWx0aXBhdGh0Y3BAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW211bHRpcGF0aHRj
cF0gUkZDNjgyNGJpcyBlZGl0cyBiYXNlZCBvbiBpbXBsZW1lbnRhdGlvbiBmZWVkYmFjaw0KDQoN
ClJTVCBkb2Vzbid0ICJjbG9zZSIgYSBjb25uZWN0aW9uOyBpdCBhYm9ydHMgaXQuIElmIGEgUlNU
IGlzIHNlbnQsIGl0IHNob3VsZCBiZSBzZW50ICpjb25zaXN0ZW50IHdpdGggaG93IFRDUCB0cmVh
dHMgc2VuZGluZyBhIFJTVCogYW5kIG5vdCBkZWZpbmVkIGFuZXcgZm9yIHRoaXMgZXh0ZW5zaW9u
Lg0KDQpKb2UNCk9uIDIvMi8yMDIwIDg6MzkgQU0sIFYgQW5pbCBLdW1hciB3cm90ZToNCkhpIFlv
c2hpLA0KDQpUaGFua3MgZm9yIHRoaXMgcG9pbnQuIEluIGZhY3QsIEkgaGFkIGluaXRpYWxseSBu
b3QgdGhvdWdodCBvZiBhIHNjZW5hcmlvLCB3aGVyZSB0aGUgbWFwIGlzIGJlaW5nIGRlbGl2ZXJl
ZCB0aHJvdWdoIGEgcmV0cmFuc21pdHRlZCBkYXRhIHBhY2tldCB3aGlsZSBpdHMgZmlyc3QgdHJh
bnNtaXNzaW9uIGRpZCBub3QgaW5jbHVkZSB0aGUgbWFwLiBOb3cgSSBhbSBqdXN0IHNlZWluZyB0
aGUgZG9jdW1lbnQgKFJGQyA2ODI0LWJpcykgaW4gdGhpcyBjb250ZXh0Lg0KDQpNeSB1bmRlcnN0
YW5kaW5nIGlzIHRoYXQgaW4gc2NlbmFyaW9zIGxpa2Ugd2hhdCBJIGRlc2NyaWJlZCBpbiBteSBw
cmV2aW91cyBtYWlsLCBSU1QgaXMgbGlrZWx5IHRvIGhhcHBlbiB3aGV0aGVyIHdlIGV4cGxpY2l0
bHkgc3RhdGUgc28gb3Igbm90LiBQbGVhc2Ugc2VlIHRoZSBwYXJhZ3JhcGggY29udGFpbmluZyB0
aGUgYmVsb3cgdGV4dCBpbiBSRkMgNjgyNC1iaXMuDQoNCiJJZiBhIG1hcHBpbmcgZm9yIHRoYXQg
c3ViZmxvdy1sZXZlbCBzZXF1ZW5jZSBzcGFjZSBkb2VzIG5vdCBhcnJpdmUgd2l0aGluIGEgcmVj
ZWl2ZSB3aW5kb3cgb2YgZGF0YSwgdGhhdCBzdWJmbG93IFNIT1VMRCBiZSB0cmVhdGVkIGFzIGJy
b2tlbiwgY2xvc2VkIHdpdGggYSBSU1QsIGFuZCBhbnkgdW5tYXBwZWQgZGF0YSBzaWxlbnRseSBk
aXNjYXJkZWQuIg0KDQppZiB3ZSBhc3N1bWUgdGhhdCB0aGUgbWFwIGlzIGluY2x1ZGVkIHdoaWxl
IHJldHJhbnNtaXR0aW5nIHRoZSBkYXRhIChldmVuIHRob3VnaCB0aGUgZmlyc3QgdHJhbnNtaXNz
aW9uIGRpZCBub3QgY29udGFpbiB0aGUgbWFwIGZvciBzb21lIHJlYXNvbnMpLCAgd2UgY291bGQg
YXJndWUgdGhhdCBSU1QgY291bGQgYmUgYXZvaWRlZCBwcm92aWRlZCB0aGF0IHRoZSByZXRyYW5z
bWlzc2lvbiBpcyB0cmlnZ2VyZWQgd2l0aGluIGEgcmVjZWl2ZSB3aW5kb3cgb2YgZGF0YS4gQnV0
IHRoZSBxdWVzdGlvbiBoZXJlIHdvdWxkIGJlIGhvdyBhbmQgd2hlbiB3aWxsIHRoZSByZXRyYW5z
bWlzc2lvbiB0YWtlIHBsYWNlLiBJbiB0aGlzIGNhc2UsIHRoZSBzdWJmbG93IG1heSBub3QgaW5p
dGlhdGUgdGhlIHJldHJhbnNtaXNzaW9uIG9mIGRhdGEgYnkgaXRzIG93biAoaS5lLiwgbm8gcmV0
cmFuc21pc3Npb24gZHVlIHRvIHRocmVlIGR1cGxpY2F0ZSBBQ0tzIG9yIFJUTyBleHBpcnkgYXQg
c3ViZmxvdyBsZXZlbCkgYXMgdGhlcmUgaXMgbm8gc2VnbWVudCBsb3NzIGF0IHN1YmZsb3cgbGV2
ZWwgc2VxdWVuY2Ugc3BhY2UuIFNvIHRoZXJlIGNvdWxkIGJlIGEgaGlnaCBwb3NzaWJpbGl0eSBv
ZiBSU1QgaGFwcGVuaW5nIGV2ZW4gYmVmb3JlIHRoZSBtYXAgZGVsaXZlcnkgdGhyb3VnaCByZXRy
YW5zbWlzc2lvbi4NCg0KV2l0aCByZWdhcmRzLA0KDQpBbmlsDQoNCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQpGcm9tOiAiWW9zaGlmdW1pIE5pc2hpZGEiIDxuc2QuaWV0ZkBnbWFp
bC5jb20+PG1haWx0bzpuc2QuaWV0ZkBnbWFpbC5jb20+DQpUbzogIlYgQW5pbCBLdW1hciIgPGFu
aWxAY3NpcjRwaS5pbj48bWFpbHRvOmFuaWxAY3NpcjRwaS5pbj4NCkNjOiAiYWxhbiBmb3JkIiA8
YWxhbi5mb3JkQGdtYWlsLmNvbT48bWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5jb20+LCAibXVsdGlw
YXRodGNwIiA8bXVsdGlwYXRodGNwQGlldGYub3JnPjxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYu
b3JnPg0KU2VudDogU2F0dXJkYXksIEZlYnJ1YXJ5IDEsIDIwMjAgMzozOTo1MSBBTQ0KU3ViamVj
dDogUmU6IFttdWx0aXBhdGh0Y3BdIFJGQzY4MjRiaXMgZWRpdHMgYmFzZWQgb24gaW1wbGVtZW50
YXRpb24gZmVlZGJhY2sNCg0KSGkgQW5pbCwNCg0KSSBoYXZlIGEgcXVlc3Rpb24gYWJvdXQgeW91
ciBwcm9wb3NlZCB0ZXh0Lg0KSSBhbSBhY3R1YWxseSB3b25kZXJpbmcgaWYgd2UgcmVhbGx5IHdh
bnQgdG8gdGVybWluYXRlIGNvbm5lY3Rpb24gaGVyZS4NCg0KVGhlIHBhY2tldHMgd2l0aG91dCBw
cm9wZXIgbWFwcGluZ3Mgd2lsbCBiZSB0cmVhdGVkIGFzIGludmFsaWQgYW5kIHdpbGwgYmUgZGlz
Y2FyZGVkLg0KSWYgYW4gaW1wbGVtZW50YXRpb24gZmFpbGVkIHRvIGF0dGFjaCBwcm9wZXIgbWFw
cGluZyBmb3Igc29tZSByZWFzb25zIChlLmcuIG9wdGlvbiBzcGFjZSksIGl0IG1pZ2h0IGJlIGFi
bGUgdG8gYXR0YWNoIHRoZSBwcm9wZXIgb25lIHdoZW4gaXQgcmV0cmFuc21pdHMgdGhlIHBhY2tl
dHMuIFRoaXMgYWxzbyBsb29rcyBvayB0byBtZS4NCg0KSSBkb24ndCBoYXZlIHN0cm9uZyBwcmVm
ZXJlbmNlIGZvciB0aGlzLiBCdXQsIGRvIHdlIGhhdmUgYSByZWFzb24gdG8gdGVybWluYXRlIGNv
bm5lY3Rpb24/DQoNClRoYW5rcywNCi0tDQpZb3NoaQ0KDQpPbiBNb24sIEphbiAxMywgMjAyMCBh
dCAxMDoyOCBBTSBWIEFuaWwgS3VtYXIgPGFuaWxAY3NpcjRwaS5pbjxtYWlsdG86YW5pbEBjc2ly
NHBpLmluPj4gd3JvdGU6DQpIaSwNCg0KSSBoYXZlIHNvbWUgcG9pbnRzIHJlbGF0ZWQgdG8gdGhl
ICBtb2RpZmljYXRpb25zIChDaGFuZ2UgMikgYmVpbmcgcHJvcG9zZWQgb24gZGF0YSBzZXF1ZW5j
ZSBtYXAuIFBsZWFzZSBzZWUgdGhlbSBpbmxpbmUuIFRob3VnaCBJIGFtIHB1dHRpbmcgZm9yd2Fy
ZCB0aGUgYmVsb3cgcG9pbnRzLCBpZiB0aGUgY29uc2Vuc3VzIGlzIGluIGZhdm91ciBvZiB0aGUg
cHJvcG9zZWQgY2hhbmdlIGZvciByZWR1Y2luZyBpbXBsZW1lbnRhdGlvbiBjb21wbGV4aXR5LCBJ
IGFtIGFsc28gT0sgd2l0aCB0aGF0IGFzIHdlbGwuDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQpGcm9tOiAiYWxhbiBmb3JkIiA8YWxhbi5mb3JkQGdtYWlsLmNvbTxtYWlsdG86
YWxhbi5mb3JkQGdtYWlsLmNvbT4+DQpUbzogbXVsdGlwYXRodGNwQGlldGYub3JnPG1haWx0bzpt
dWx0aXBhdGh0Y3BAaWV0Zi5vcmc+DQpTZW50OiBUaHVyc2RheSwgSmFudWFyeSAyLCAyMDIwIDQ6
MjE6MzIgQU0NClN1YmplY3Q6IFttdWx0aXBhdGh0Y3BdIFJGQzY4MjRiaXMgZWRpdHMgYmFzZWQg
b24gaW1wbGVtZW50YXRpb24gZmVlZGJhY2sNCg0KSGkgYWxsLA0KV2XigJlkIGxvdmUgdG8gZ2V0
IHRoaXMgdG8gYSBzdGF0ZSBvZiBjb21wbGV0aW9uIGFzIHNvb24gYXMgcG9zc2libGUsIGFuZCB0
byB0aGlzIGVuZCBJIGFtIHN0YXJ0aW5nIGEgbmV3IHRocmVhZCBvbiB0aGlzIHRvcGljLiBJbiBk
aXNjdXNzaW9uIHdpdGggdGhlIGNoYWlycywgaXQgaXMgcG9zc2libGUgdG8gbWFrZSB0aGUgZGVz
aXJlZCBjaGFuZ2VzIGluIEFVVEg0OCBhcyBsb25nIGFzIHRoZXJlIGlzIFdHIGNvbnNlbnN1cy4g
VGhlIGRpc2N1c3Npb24gc28gZmFyIGhhcyBiZWVuIGZhaXJseSBsaW1pdGVkIGluIHRlcm1zIG9m
IHBhcnRpY2lwYXRpb24uDQoNCkkgd291bGQgYXNrIHRoZSBjaGFpcnMgcGxlYXNlIGlmIGl0IHdh
cyBwb3NzaWJsZSB0byBzcGVjaWZ5IGEgdGltZSBib3VuZCBmb3IgdGhpcyBkaXNjdXNzaW9uIGFu
ZCBhIGRlZmF1bHQgY29uY2x1c2lvbi4NCg0KUmVnYXJkaW5nIHRoZSBjaGFuZ2VzLCBpbiBzdW1t
YXJ5LCB0aGVyZSBhcmUgdHdvIGFyZWFzIHdoZXJlIGNoYW5nZXMgaGF2ZSBiZWVuIHJlcXVlc3Rl
ZCBieSB0aGUgaW1wbGVtZW50YXRpb24gY29tbXVuaXR5LiBBcyB3ZSBhcmUgdGhlIElFVEYgd2Ug
b2J2aW91c2x5IGhhdmUgc3Ryb25nIGZvY3VzIG9uIOKAnHJ1bm5pbmcgY29kZeKAnSBhbmQgc28g
ZWFzZSBvZiBpbXBsZW1lbnRpbmcgc3RhbmRhcmRzLWNvbXBsaWFudCBjb2RlIGlzIHN0cm9uZ2x5
IGRlc2lyYWJsZS4gSG93ZXZlciwgd2UgZG8gbm90IHdpc2ggdG8gcmVkdWNlIGZ1bmN0aW9uYWxp
dHkgYWdyZWVkIGJ5IHRoZSBJRVRGIGNvbW11bml0eSBpZiBpdCBpcyBjb25zaWRlcmVkIGEgcmVx
dWlyZWQgZmVhdHVyZSBieSB0aGUgY29tbXVuaXR5Lg0KDQpDaGFuZ2UgMQ0KDQpDaGFuZ2UgdGhl
IHNlbnRlbmNlIHJlYWRpbmc6DQoNCiAgIElmIEIgaGFzIGRhdGEgdG8gc2VuZCBmaXJzdCwgdGhl
biB0aGUgcmVsaWFibGUgZGVsaXZlcnkgb2YgdGhlIEFDSyArIE1QX0NBUEFCTEUgY2FuIGJlIGlu
ZmVycmVkIGJ5IHRoZSByZWNlaXB0IG9mIHRoaXMgZGF0YSB3aXRoIGFuIE1QVENQIERhdGEgU2Vx
dWVuY2UgU2lnbmFsIChEU1MpIG9wdGlvbiAoU2VjdGlvbiAzLjMpLg0KDQpUbzoNCg0KICAgSWYg
QiBoYXMgZGF0YSB0byBzZW5kIGZpcnN0LCB0aGVuIHRoZSByZWxpYWJsZSBkZWxpdmVyeSBvZiB0
aGUgQUNLICsgTVBfQ0FQQUJMRSBpcyBlbnN1cmVkIGJ5IHRoZSByZWNlaXB0IG9mIHRoaXMgZGF0
YSB3aXRoIGFuIE1QVENQIERhdGEgU2VxdWVuY2UgU2lnbmFsIChEU1MpIG9wdGlvbiAoU2VjdGlv
biAzLjMpIGNvbnRhaW5pbmcgYSBEQVRBX0FDSyBmb3IgdGhlIE1QX0NBUEFCTEUgKHdoaWNoIGlz
IHRoZSBmaXJzdCBvY3RldCBvZiB0aGUgZGF0YSBzZXF1ZW5jZSBzcGFjZSkuDQpXaGF0IHRoaXMg
bWVhbnM6DQoNClRoZSBjdXJyZW50IHRleHQgaXMgY29uY2VybmVkIG9ubHkgd2l0aCBlbnN1cmlu
ZyBhIHBhdGggaXMgTVBUQ1AgY2FwYWJsZSwgYW5kIHNvIG9ubHkgY2FyZXMgdGhhdCBEU1Mgb3B0
aW9uIG9jY3VycyBvbiBhIGRhdGEgcGFja2V0LiBIb3dldmVyLCB0aGUgTVBfQ0FQQUJMRSBvcHRp
b24gaXMgZGVmaW5lZCB0byBvY2N1cHkgdGhlIGZpcnN0IG9jdGV0IG9mIGRhdGEgc2VxdWVuY2Ug
c3BhY2UgYW5kIHRodXMsIGlmIGFuYWxvZ291cyB0byBUQ1AsIG11c3QgYmUgYWNrbm93bGVkZ2Vk
LiA+RnJvbSBhbiBpbXBsZW1lbnRhdGlvbiBwb2ludCBvZiB2aWV3IGl0IHdvdWxkIG1ha2Ugc2Vu
c2Ugbm90IHRvIGhhdmUgdGhpcyBoYW5naW5nIGFyb3VuZCBmb3JldmVyIGFuZCBpbnN0ZWFkIGRl
ZmluZSBpdCBpcyBhY2tub3dsZWRnZWQgYXQgdGhlIGNvbm5lY3Rpb24gbGV2ZWwgYXMgc29vbiBh
cyByZWNlaXZlZC4gVGhpcyBjaGFuZ2UgZW5zdXJlcyB0aGUgZmlyc3QgZGF0YSBwYWNrZXQgYWxz
byBEQVRBX0FDS3MgdGhpcyBNUF9DQVBBQkxFIG9jdGV0Lg0KDQpDaGFuZ2UgMg0KDQpDaGFuZ2Ug
dGhlIHNlbnRlbmNlIHJlYWRpbmc6DQoNCiAgIEEgRGF0YSBTZXF1ZW5jZSBNYXBwaW5nIGRvZXMg
bm90IG5lZWQgdG8gYmUgaW5jbHVkZWQgaW4gZXZlcnkgTVBUQ1AgcGFja2V0LCBhcyBsb25nIGFz
IHRoZSBzdWJmbG93IHNlcXVlbmNlIHNwYWNlIGluIHRoYXQgcGFja2V0IGlzIGNvdmVyZWQgYnkg
YSBtYXBwaW5nIGtub3duIGF0IHRoZSByZWNlaXZlci4NCg0KVG86DQoNCiAgIFRoZSBtYXBwaW5n
IHByb3ZpZGVkIGJ5IGEgRGF0YSBTZXF1ZW5jZSBNYXBwaW5nIE1VU1QgYXBwbHkgdG8gc29tZSBv
ciBhbGwgb2YgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2UgaW4gdGhlIFRDUCBzZWdtZW50IHdo
aWNoIGNhcnJpZXMgdGhlIG9wdGlvbi4gSXQgZG9lcyBub3QgbmVlZCB0byBiZSBpbmNsdWRlZCBp
biBldmVyeSBNUFRDUCBwYWNrZXQsIGFzIGxvbmcgYXMgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3Bh
Y2UgaW4gdGhhdCBwYWNrZXQgaXMgY292ZXJlZCBieSBhIG1hcHBpbmcga25vd24gYXQgdGhlIHJl
Y2VpdmVyLg0KDQpXaGF0IHRoaXMgbWVhbnM6DQoNClRoZSBjdXJyZW50IHRleHQgZG9lcyBub3Qg
cGxhY2UgYW55IHJlc3RyaWN0aW9ucyBvbiB3aGVyZSBhIG1hcHBpbmcgY291bGQgYXBwZWFyLiBJ
biB0aGVvcnkgYSBzZW5kZXIgY291bGQgZGVmaW5lIGEgdGhvdXNhbmQgZGlmZmVyZW50IG1hcHBp
bmdzIHVwIGZyb250LCBzZW5kIHRoZW0gYWxsLCBhbmQgZXhwZWN0IGEgcmVjZWl2ZXIgdG8gc3Rv
cmUgdGhpcyBhbmQgcmVhc3NlbWJsZSBkYXRhIGFjY29yZGluZyB0byB0aGVzZSBtYXBwaW5ncyBh
cyBpdCBhcnJpdmVzLiBJbmRlZWQsIHRoaXMgd2FzIG5ldmVyIGV4cGxpY2l0bHkgZGlzYWxsb3dl
ZCBzaW5jZSBpdCDigJxtaWdodCBoYXZlIGJlZW4gdXNlZnVs4oCdLiBUaGUgaW1wbGVtZW50YXRp
b24gY29tbXVuaXR5LCBob3dldmVyLCBoYXMgZXhwcmVzc2VkIGNvbmNlcm5zIG92ZXIgdGhlIGRp
ZmZpY3VsdHkgb2YgaW1wbGVtZW50aW5nIHRoaXMgb3Blbi1lbmRlZGx5LiBIb3cgbWFueSBtYXBw
aW5ncyBpcyBpdCByZWFzb25hYmxlIHRvIHN0b3JlPyBJcyB0aGVyZSBhIERvUyByaXNrIGhlcmU/
IEluc3RlYWQsIGl0IGhhcyBiZWVuIHJlcXVlc3RlZCB0aGF0IHRoZWUgc3BlY2lmaWNhdGlvbiBy
ZXN0cmljdHMgdGhlIHBsYWNlbWVudCBvZiB0aGUgRFNTIG9wdGlvbiB0byBiZWluZyB3aXRoaW4g
dGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2UgdG8gd2hpY2ggaXQgYXBwbGllcy4NCg0KQmVsb3cg
YXJlIG15IGNvbW1lbnRzIG9uIHRoaXMuIEkgaGFkIHNoYXJlZCBzb21lIG9mIHRoZXNlIHBvaW50
cyBpbiBhIHByZXZpb3VzIHRocmVhZCB0aGF0IHlvdSBoYWQgaW5pdGlhdGVkIGluIHRoZSBzYW1l
IGNvbnRleHQuDQoNClRyYW5zbWl0dGluZyBsYXJnZSBudW1iZXIgb2Ygbm9uLWNvbnRpZ3VvdXMg
ZGF0YSBzZXF1ZW5jZSBtYXBzIGNvdWxkIGJlIGEgbWlzYmVoYXZpb3VyIChtYXAtZmxvb2Rpbmcp
LCB0aG91Z2ggaXQgaXMgbm90IGNsZWFyIHdoZXRoZXIgdGhpcyBjYW4gZ28gdG8gdGhlIGV4dGVu
dCBvZiBjYXVzaW5nIGEgcG90ZW50aWFsIERvUyB0byB0aGUgZGF0YSByZWNlaXZlci4gU28gc29t
ZSBzb3J0IG9mIHJlc3RyaWN0aW9uIG9uIHRoaXMgY291bGQgYmUgdXNlZnVsLiAgT25lIGFwcHJv
YWNoIGNvdWxkIGJlIHRvIGluc2lzdCB0aGF0IHRoZSBkYXRhIHNlbmRlciBzaG91bGQgZW5zdXJl
IHRoYXQgdGhlIG1hcCBiZWluZyB0cmFuc21pdHRlZCBpcyBmb3IgaW4td2luZG93IGRhdGEsIGFz
IHBlciB0aGUgcmVjZWl2ZXIgYWR2ZXJ0aXNlZCB3aW5kb3cuIEEgcmVjZWl2ZXIgc2hvdWxkIGFu
eWhvdyBiZSB3aWxsaW5nIHRvIHN0b3JlIHRoZSBtYXBzIGZvciBpbi13aW5kb3cgZGF0YSB0byBk
ZWFsIHdpdGggcGFja2V0IGxvc3MuLiBGb3IgZXhhbXBsZSwgd2hlbiBhIHdpbmRvdyBvZiBkYXRh
IHNlZ21lbnRzIChzYXkgMSB0byA2NCkgaXMgdHJhbnNtaXR0ZWQsIGVhY2ggY2FycnlpbmcgaXRz
IGNvcnJlc3BvbmRpbmcgbWFwLCBhbmQgc2VnbWVudC0xIGlzIGxvc3QsIHRoZSBtYXBzIGZvciB0
aGUgcmVtYWluaW5nIDYzIG5lZWQgdG8gYmUgc3RvcmVkIHRpbGwgdGhlIGxvc3Qgc2VnbWVudCBp
cyByZXRyYW5zbWl0dGVkLiBPZiBjb3Vyc2UsIGluIHRoaXMgY2FzZSB0aGUgbWFwcyB3aWxsIGJl
IHN0b3JlZCBhdCB0aGUgcmVjZWl2ZXIgc2lkZSBhbG9uZyB3aXRoIHRoZWlyIGNvcnJlc3BvbmRp
bmcgZGF0YS4gQnV0IHRoZSBuZWVkIHRvIHN0b3JlIG11bHRpcGxlIG1hcHMgZm9yIGluLXdpbmRv
dyBkYXRhIHdvdWxkIHN0aWxsIGJlIHRoZXJlLg0KDQpUaGUgcHJvYmxlbSB3aXRoIHRoZSBwcm9w
b3NlZCBjaGFuZ2UgKHJlc3RyaWN0aW9uKSBpcyB0aGF0IGEgZGF0YSBzZW5kZXIgbWF5IGZpbmQg
aXQgZGlmZmljdWx0LCBpbiBjYXNlIGEgbmVlZCBhcmlzZSB0byBzbGlnaHRseSBkZWxheSB0aGUg
bWFwIGRlbGl2ZXJ5IGJ5IGZldyBzZWdtZW50cywgaS5lLiwgc2VuZGluZyBzb21lIGRhdGEgZmly
c3Qgd2l0aG91dCBtYXAsIGFuZCB0aGVuIHNlbmQgdGhlIGNvcnJlc3BvbmRpbmcgbWFwIGluIGEg
bGF0ZXIgc2VnbWVudCwgYXMgc2hvd24gYmVsb3c6DQoNCnN1YmZsb3ctMTogICAgICBzZWdtZW50
LTEgICAgICAgICAgICAgICAgICAgc2VnbWVudC0zICAgICAgICAgICAgICAgICAgICBzZWdtZW50
LTQgICAgICAgICAgICAgICAgICAgICAgIHNlZ21lbnQtNw0KICAgICAgICAgICAgICAgICAgICAg
IGJ5dGVzOjEtMTAwICAgICAgICAgICAgICAgICBieXRlczoyMDEtMzAwICAgICAgICAgICAgICBi
eXRlczozMDEtNDAwICAgICAgICAgICAgICAgICBieXRlczo2MDEtNzAwDQogICAgICAgICAgICAg
ICAgICAgICAgbm8gbWFwICAgICAgICAgICAgICAgICAgICAgICAgbWFwIGZvciAxLTEwMCAgICAg
ICAgICAgICAgbWFwIGZvciAyMDEtNDAwICAgICAgICAgICAgIG1hcCBmb3IgNjAxLTcwMA0KDQoN
Cg0Kc3ViZmxvdy0yOiAgICAgICBzZWdtZW50LTIgICAgICAgICAgICAgICAgICBzZWdtZW50LTUg
ICAgICAgICAgICAgICAgICAgICBzZWdtZW50LTYgICAgICAgICAgICAgICAgICAgICAgIHNlZ21l
bnQtOA0KICAgICAgICAgICAgICAgICAgICAgICBieXRlczogMTAxLTIwMCAgICAgICAgICAgYnl0
ZXM6NDAxLTUwMCAgICAgICAgICAgICAgIGJ5dGVzOiA1MDEtNjAwICAgICAgICAgICAgICAgIGJ5
dGVzOjcwMS04MDANCiAgICAgICAgICAgICAgICAgICAgICAgbWFwIGZvciAxMDEtMjAwICAgICAg
IG1hcCBmb3IgNDAxLTYwMCAgICAgICAgICAgIG5vIG1hcCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBtYXAgZm9yIDcwMS04MDANCg0KDQpJbiB0aGUgYWJvdmUgY2FzZSwgc2VnbWVudC0xIGdv
ZXMgd2l0aG91dCBtYXAgYW5kIGl0cyBtYXAgaXMgaW5jbHVkZWQgbGF0ZXIgaW4gc2VnbWVudC0z
LCB0aGUgbmV4dCBkYXRhIHNlZ21lbnQgaW4gdGhlIHNhbWUgc3ViZmxvdy4gRnVydGhlciwgIGlu
IHRoZSBhYm92ZSBzY2hlZHVsaW5nIHBhdHRlcm4sIHRoZSBtYXAgaW4gc2VnbWVudC0zIGNhbm5v
dCBjb3ZlciB0aGUgIGRhdGEgaW4gc2VnbWVudC0xIGFuZCBzZWdtZW50LTMsIGFzIHNvbWUgIGRh
dGEgaW4gYmV0d2VlbiAoc2VnbWVudC0yKSBpcyB0cmFuc21pdHRlZCB0aHJvdWdoIGFub3RoZXIg
c3ViZmxvdy4uICBXaXRoIHRoZSBwcm9wb3NlZCBjaGFuZ2UsIHRoZSBtYXAgaW4gc2VnbWVudC0z
IHdpbGwgYmVjb21lIGludmFsaWQgYW5kIHRoaXMgd2lsbCBldmVudHVhbGx5IGJyZWFrIHN1YmZs
b3ctMSwgdGhvdWdoIHRoaXMgY291bGQgYmUgYSBjb3JuZXIgY2FzZS4NCg0KVGhlIHF1ZXN0aW9u
IGF0IHRoaXMgc3RhZ2UgaXMgd2h5IHdvdWxkIHNlZ21lbnQtMSBiZSB0cmFuc21pdHRlZCB3aXRo
b3V0IGl0cyBtYXAuIEluIHRoZSBjYXNlIG9mIGJpZGlyZWN0aW9uYWwgZGF0YSB0cmFuc2Zlciwg
dGhlcmUgY291bGQgYmUgYSBuZWVkIHRvIHBhY2sgYm90aCB0aW1lc3RhbXAgYW5kIFNBQ0sgIG9w
dGlvbnMgaW4gYSBkYXRhIHNlZ21lbnQsIGkuZS4sIHBpZ2d5YmFja2luZyBvZiAgU0FDSyB3aXRo
IGRhdGEuIElmIHdlIGNvbnNpZGVyIHRoYXQgdGltZXN0YW1wIHRha2VzIDEyIGJ5dGVzIGFuZCBT
QUNLLCBldmVuIHdpdGggc2luZ2xlIGJsb2NrLCAgdGFrZXMgYW5vdGhlciAxMCBieXRlcywgdGhl
IHJlbWFpbmluZyAxOCBieXRlcyBvcHRpb24gc3BhY2UgaXMgbm90IGFkZXF1YXRlIHRvIGNhcnJ5
IGRhdGEgc2VxdWVuY2Ugc2lnbmFsIHdpdGggbWFwLCBlc3BlY2lhbGx5IHdoZW4gRFNOIGlzIDY0
IGJpdCBsb25nLiBTbyB0aGUgZGVsaXZlcnkgb2YgZWl0aGVyIG9mIHRoZSB0d28gKFNBQ0sgb3Ig
bWFwKSB3b3VsZCBiZSBkZWxheWVkLg0KDQpBcyBmYXIgYXMgSSB1bmRlcnN0YW5kLCBSRkMgMjAx
OCAoVENQIFNlbGVjdGl2ZSBBY2tub3dsZWRnZW1lbnQgT3B0aW9ucykgaW1wbGllcyB0aGF0IFNB
Q0sgc2hvdWxkIG5vdCBiZSBkZWxheWVkLiBJdCBzdGF0ZXMgIklmIHNlbnQgYXQgYWxsLCBTQUNL
IG9wdGlvbnMgU0hPVUxEIGJlIGluY2x1ZGVkIGluIGFsbCBBQ0tzIHdoaWNoIGRvIG5vdCBBQ0sg
dGhlIGhpZ2hlc3Qgc2VxdWVuY2UgbnVtYmVyIGluIHRoZSBkYXRhIHJlY2VpdmVyJ3MgcXVldWUi
LiBJdCBhbHNvIHNheXMgIklmIGRhdGEgcmVjZWl2ZXIgZ2VuZXJhdGVzIFNBQ0sgb3B0aW9ucyB1
bmRlciBhbnkgY2lyY3Vtc3RhbmNlLCBpdCBTSE9VTEQgZ2VuZXJhdGUgdGhlbSB1bmRlciBhbGwg
cGVybWl0dGVkIGNpcmN1bXN0YW5jZXMiLiAgIFNvLCBhcyBwYXJ0IG9mIG1lZXRpbmcgdGhlIFJG
QyAyMDE4IHJlcXVpcmVtZW50cywgaWYgdGhlIGNvbWJpbmF0aW9uIG9mIFNBQ0sgYW5kIHRpbWVz
dGFtcCBpcyBnaXZlbiBwcmVmZXJlbmNlIG92ZXIgRFNTLCBkYXRhIHNlZ21lbnRzIGNvdWxkIGJl
IHRyYW5zbWl0dGVkIHdpdGhvdXQgdGhlaXIgbWFwLg0KDQpBbm90aGVyIGNhc2Ugb2YgZGVsYXlp
bmcgbWFwIGNvdWxkIGFyaXNlIGlmIHRoZSBkYXRhIHNlbmRlciBwcmVmZXJzIHRvIHNlbmQgQURE
X0FERFIgb3B0aW9uLCBpbnN0ZWFkIG9mIG1hcCwgaW4gYSBkYXRhIHNlZ21lbnQuIEl0IGlzIG5p
Y2UgdGhhdCBBRERfQUREUiBvcHRpb24gY2FuIGJlIGRlbGl2ZXJlZCByZWxpYWJseSBpbiBhIHB1
cmUgQUNLLCBidXQgSSB0aGluayB0aGlzIGlzIG5vdCB0aGUgY2FzZSB3aXRoIERTUyBhdCBwcmVz
ZW50Lg0KDQpJZiB3ZSBhZG9wdCB0aGUgcHJvcG9zZWQgY2hhbmdlLCBJIHRoaW5rIGl0IG1pZ2h0
IGFsc28gYmUgaGVscGZ1bCB0byBzcGVsbCBvdXQgaG93IHRoZSByZWNlaXZlciBpcyBzdXBwb3Nl
ZCB0byBiZWhhdmUsIGlmIGl0IGdldHMgbWFwcyBub3QgbWVldGluZyB0aGUgTVVTVCBjb25kaXRp
b24gaW4gdGhlIHByb3Bvc2VkIGNoYW5nZS4gIEZvciBleGFtcGxlIHRlcm1pbmF0aW9uIG9mIHRo
ZSBzdWJmbG93IHdpdGggTVBfVENQUlNUIG9wdGlvbiAoc2VjdGlvbiAzLjYgaW4gUkZDIDY4MjQt
YmlzKSB3aXRoIGFwcHJvcHJpYXRlIHJlYXNvbiBjb2RlIGFuZCBUIGZsYWcgdmFsdWUgdG8gaW50
aW1hdGUgdGhlIGRhdGEgc2VuZGVyIHRoZSBjYXVzZSBmb3Igc3ViZmxvdyB0ZXJtaW5hdGlvbi4N
Cg0KV2l0aCByZWdhcmRzLA0KDQpBbmlsDQpQbGVhc2UgY2FuIG1lbWJlcnMgb2YgdGhlIFdHIGV4
cHJlc3Mgd2hldGhlciB0aGV5IGFyZSBoYXBweSB3aXRoIHRoZXNlIGNoYW5nZXMsIG9yIGNvbmNl
cm5lZC4NCg0KQmVzdCByZWdhcmRzLA0KQWxhbg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQptdWx0aXBhdGh0Y3AgbWFpbGluZyBsaXN0DQptdWx0
aXBhdGh0Y3BAaWV0Zi5vcmc8bWFpbHRvOm11bHRpcGF0aHRjcEBpZXRmLm9yZz4NCmh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNwDQoNCg0KDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbXVsdGlwYXRodGNwIG1h
aWxpbmcgbGlzdA0KbXVsdGlwYXRodGNwQGlldGYub3JnPG1haWx0bzptdWx0aXBhdGh0Y3BAaWV0
Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRpcGF0aHRj
cA0KDQoNCg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCg0KbXVsdGlwYXRodGNwIG1haWxpbmcgbGlzdA0KDQptdWx0aXBhdGh0Y3BAaWV0Zi5v
cmc8bWFpbHRvOm11bHRpcGF0aHRjcEBpZXRmLm9yZz4NCg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3ANCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIg
MTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q29uc29sYXM7
DQoJcGFub3NlLTE6MiAxMSA2IDkgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh
bWlseToiU2Vnb2UgVUkiOw0KCXBhbm9zZS0xOjIgMTEgNSAyIDQgMiA0IDIgMiAzO30NCi8qIFN0
eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9y
bWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTox
MS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFu
Lk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtG
b2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQt
ZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglt
c28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCglt
YXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToi
Q291cmllciBOZXciO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1h
bDANCgl7bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRv
Ow0KCW1hcmdpbi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFy
Z2luLWxlZnQ6MGNtOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LHNhbnMtc2VyaWY7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFt
ZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7
fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1m
YW1pbHk6IkFyaWFsIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFp
bFN0eWxlMjINCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWls
eToiQXJpYWwiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBw
YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0
IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVm
YXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxv
OmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwh
W2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tR0IiIGxpbms9ImJsdWUiIHZsaW5r
PSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbHQ7Jmx0Ozwvc3Bhbj48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+IGlmIHdlIGFzc3VtZSB0
aGF0IHRoZSBtYXAgaXMgaW5jbHVkZWQgd2hpbGUgcmV0cmFuc21pdHRpbmcgdGhlIGRhdGEgKGV2
ZW4gdGhvdWdoIHRoZSBmaXJzdCB0cmFuc21pc3Npb24gZGlkIG5vdA0KIGNvbnRhaW4gdGhlIG1h
cCBmb3Igc29tZSByZWFzb25zKSwgJm5ic3A7Jmd0OyZndDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZiI+QWJvdXQg4oCcZm9yIHNvbWUgcmVhc29u4oCdLiBJcyB0aGlz
IHNvbWV0aGluZyB5b3XigJl2ZSBzZWVuIChvciBleHBlY3QgdG8gc2VlKSByZWd1bGFybHksIG9y
IGlzIHRoaXMgc29tZXRoaW5nIHRoYXQgd291bGQgYmUgcmFyZT88bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPkFzIHlvdSBzYXksIHRoZSBjdXJyZW50IHdvcmRpbmcgaGFzIGEgU0hP
VUxELCByYXRoZXIgdGhhbiBhIE1VU1Qg4oCTIHdoaWNoIHdvdWxkIGxlYXZlIGEgYml0IG9mIHJv
b20gdG8gZG8gc29tZXRoaW5nIGRpZmZlcmVudCBpZiB0aGVyZSB3ZXJlIHNwZWNpZmljIChidXQg
dW5saWtlbHkpIGNpcmN1bXN0YW5jZXMgdGhhdCBtZXJpdGVkIGRvaW5nDQogc29tZXRoaW5nIGRp
ZmZlcmVudC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5SU1QgZm9yY2VzIHRoZSBpbW1lZGlh
dGUgY2xvc3VyZSBvZiBhbiBNUFRDUCBzdWJmbG93LiBNUF9GQVNUQ0xPU0UgZm9yY2VzIHRoZSBp
bW1lZGlhdGUgY2xvc3VyZSBvZiB0aGUgTVBUQ1AgY29ubmVjdGlvbiAod2hpY2ggY2FuIGFsc28g
YmUgYWNoaWV2ZWQgYnkgc2VuZGluZyBhIFJTVCBvbiBhbGwgc3ViZmxvd3MpLg0KPC9zcGFuPjxz
cGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1m
YXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkJl
c3Qgd2lzaGVzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPnBoaWw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29s
aWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFu
Zz0iRU4tVVMiPiBtdWx0aXBhdGh0Y3AgJmx0O211bHRpcGF0aHRjcC1ib3VuY2VzQGlldGYub3Jn
Jmd0Ow0KPGI+T24gQmVoYWxmIE9mIDwvYj5Kb2UgVG91Y2g8YnI+DQo8Yj5TZW50OjwvYj4gMDIg
RmVicnVhcnkgMjAyMCAxNzozOTxicj4NCjxiPlRvOjwvYj4gViBBbmlsIEt1bWFyICZsdDthbmls
QGNzaXI0cGkuaW4mZ3Q7OyBZb3NoaWZ1bWkgTmlzaGlkYSAmbHQ7bnNkLmlldGZAZ21haWwuY29t
Jmd0Ozxicj4NCjxiPkNjOjwvYj4gbXVsdGlwYXRodGNwICZsdDttdWx0aXBhdGh0Y3BAaWV0Zi5v
cmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbbXVsdGlwYXRodGNwXSBSRkM2ODI0Ymlz
IGVkaXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHA+UlNUIGRvZXNuJ3QgJnF1b3Q7Y2xvc2UmcXVvdDsgYSBjb25uZWN0aW9uOyBp
dCBhYm9ydHMgaXQuIElmIGEgUlNUIGlzIHNlbnQsIGl0IHNob3VsZCBiZSBzZW50ICpjb25zaXN0
ZW50IHdpdGggaG93IFRDUCB0cmVhdHMgc2VuZGluZyBhIFJTVCogYW5kIG5vdCBkZWZpbmVkIGFu
ZXcgZm9yIHRoaXMgZXh0ZW5zaW9uLg0KPG86cD48L286cD48L3A+DQo8cD5Kb2U8bzpwPjwvbzpw
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiAyLzIvMjAyMCA4OjM5IEFNLCBW
IEFuaWwgS3VtYXIgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0
eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5IaSBZb3NoaSw8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPlRoYW5rcyBmb3IgdGhpcyBwb2lu
dC4gSW4gZmFjdCwgSSBoYWQgaW5pdGlhbGx5IG5vdCB0aG91Z2h0IG9mIGEgc2NlbmFyaW8sIHdo
ZXJlIHRoZSBtYXAgaXMgYmVpbmcgZGVsaXZlcmVkIHRocm91Z2ggYSByZXRyYW5zbWl0dGVkIGRh
dGEgcGFja2V0IHdoaWxlIGl0cyBmaXJzdCB0cmFuc21pc3Npb24gZGlkIG5vdCBpbmNsdWRlIHRo
ZQ0KIG1hcC4gTm93IEkgYW0ganVzdCBzZWVpbmcgdGhlIGRvY3VtZW50IChSRkMgNjgyNC1iaXMp
IGluIHRoaXMgY29udGV4dC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWYiPk15IHVuZGVyc3RhbmRpbmcgaXMgdGhhdCBpbiBzY2VuYXJpb3MgbGlrZSB3aGF0
IEkgZGVzY3JpYmVkIGluIG15IHByZXZpb3VzIG1haWwsIFJTVCBpcyBsaWtlbHkgdG8gaGFwcGVu
IHdoZXRoZXIgd2UgZXhwbGljaXRseSBzdGF0ZSBzbyBvciBub3QuIFBsZWFzZSBzZWUgdGhlIHBh
cmFncmFwaCBjb250YWluaW5nIHRoZSBiZWxvdyB0ZXh0DQogaW4gUkZDIDY4MjQtYmlzLiAmbmJz
cDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPiZxdW90
O0lmIGEgbWFwcGluZyBmb3IgdGhhdCBzdWJmbG93LWxldmVsIHNlcXVlbmNlIHNwYWNlIGRvZXMg
bm90IGFycml2ZSB3aXRoaW4gYSByZWNlaXZlIHdpbmRvdyBvZiBkYXRhLCB0aGF0IHN1YmZsb3cg
U0hPVUxEIGJlIHRyZWF0ZWQgYXMgYnJva2VuLCBjbG9zZWQgd2l0aCBhIFJTVCwgYW5kIGFueSB1
bm1hcHBlZCBkYXRhIHNpbGVudGx5DQogZGlzY2FyZGVkLiZxdW90OzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+aWYgd2UgYXNzdW1lIHRoYXQgdGhlIG1h
cCBpcyBpbmNsdWRlZCB3aGlsZSByZXRyYW5zbWl0dGluZyB0aGUgZGF0YSAoZXZlbiB0aG91Z2gg
dGhlIGZpcnN0IHRyYW5zbWlzc2lvbiBkaWQgbm90IGNvbnRhaW4gdGhlIG1hcCBmb3Igc29tZSBy
ZWFzb25zKSwgJm5ic3A7d2UgY291bGQgYXJndWUgdGhhdCBSU1QgY291bGQgYmUgYXZvaWRlZCBw
cm92aWRlZA0KIHRoYXQgdGhlIHJldHJhbnNtaXNzaW9uIGlzIHRyaWdnZXJlZCB3aXRoaW4gYSBy
ZWNlaXZlIHdpbmRvdyBvZiBkYXRhLiBCdXQgdGhlIHF1ZXN0aW9uIGhlcmUgd291bGQgYmUgaG93
IGFuZCB3aGVuIHdpbGwgdGhlIHJldHJhbnNtaXNzaW9uIHRha2UgcGxhY2UuIEluIHRoaXMgY2Fz
ZSwgdGhlIHN1YmZsb3cgbWF5IG5vdCBpbml0aWF0ZSB0aGUgcmV0cmFuc21pc3Npb24gb2YgZGF0
YSBieSBpdHMgb3duIChpLmUuLCBubyByZXRyYW5zbWlzc2lvbg0KIGR1ZSB0byB0aHJlZSBkdXBs
aWNhdGUgQUNLcyBvciBSVE8gZXhwaXJ5IGF0IHN1YmZsb3cgbGV2ZWwpIGFzIHRoZXJlIGlzIG5v
IHNlZ21lbnQgbG9zcyBhdCBzdWJmbG93IGxldmVsIHNlcXVlbmNlIHNwYWNlLiBTbyB0aGVyZSBj
b3VsZCBiZSBhIGhpZ2ggcG9zc2liaWxpdHkgb2YgUlNUIGhhcHBlbmluZyBldmVuIGJlZm9yZSB0
aGUgbWFwIGRlbGl2ZXJ5IHRocm91Z2ggcmV0cmFuc21pc3Npb24uJm5ic3A7PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5XaXRoIHJlZ2FyZHMsJm5ic3A7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5BbmlsPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPiZu
YnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFs
IiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIiPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4NCjxociBzaXplPSIyIiB3
aWR0aD0iMTAwJSIgYWxpZ249ImNlbnRlciIgaWQ9Inp3Y2hyIj4NCjwvc3Bhbj48L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTogPC9zcGFuPg0KPC9iPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4mcXVvdDtZb3NoaWZ1
bWkgTmlzaGlkYSZxdW90OyA8YSBocmVmPSJtYWlsdG86bnNkLmlldGZAZ21haWwuY29tIj4NCiZs
dDtuc2QuaWV0ZkBnbWFpbC5jb20mZ3Q7PC9hPjxicj4NCjxiPlRvOiA8L2I+JnF1b3Q7ViBBbmls
IEt1bWFyJnF1b3Q7IDxhIGhyZWY9Im1haWx0bzphbmlsQGNzaXI0cGkuaW4iPiZsdDthbmlsQGNz
aXI0cGkuaW4mZ3Q7PC9hPjxicj4NCjxiPkNjOiA8L2I+JnF1b3Q7YWxhbiBmb3JkJnF1b3Q7IDxh
IGhyZWY9Im1haWx0bzphbGFuLmZvcmRAZ21haWwuY29tIj4mbHQ7YWxhbi5mb3JkQGdtYWlsLmNv
bSZndDs8L2E+LCAmcXVvdDttdWx0aXBhdGh0Y3AmcXVvdDsNCjxhIGhyZWY9Im1haWx0bzptdWx0
aXBhdGh0Y3BAaWV0Zi5vcmciPiZsdDttdWx0aXBhdGh0Y3BAaWV0Zi5vcmcmZ3Q7PC9hPjxicj4N
CjxiPlNlbnQ6IDwvYj5TYXR1cmRheSwgRmVicnVhcnkgMSwgMjAyMCAzOjM5OjUxIEFNPGJyPg0K
PGI+U3ViamVjdDogPC9iPlJlOiBbbXVsdGlwYXRodGNwXSBSRkM2ODI0YmlzIGVkaXRzIGJhc2Vk
IG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+SGkgQW5pbCw8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkkgaGF2ZSBh
IHF1ZXN0aW9uIGFib3V0IHlvdXIgcHJvcG9zZWQgdGV4dC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkkgYW0gYWN0dWFsbHkg
d29uZGVyaW5nIGlmIHdlIHJlYWxseSB3YW50IHRvIHRlcm1pbmF0ZSBjb25uZWN0aW9uIGhlcmUu
Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMt
c2VyaWYiPlRoZSBwYWNrZXRzIHdpdGhvdXQgcHJvcGVyIG1hcHBpbmdzIHdpbGwgYmUgdHJlYXRl
ZCBhcyBpbnZhbGlkIGFuZCB3aWxsIGJlIGRpc2NhcmRlZC4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+SWYgYW4gaW1wbGVtZW50
YXRpb24gZmFpbGVkIHRvIGF0dGFjaCBwcm9wZXIgbWFwcGluZyBmb3Igc29tZSByZWFzb25zIChl
LmcuIG9wdGlvbiBzcGFjZSksIGl0IG1pZ2h0IGJlIGFibGUgdG8gYXR0YWNoIHRoZSBwcm9wZXIg
b25lIHdoZW4gaXQgcmV0cmFuc21pdHMgdGhlIHBhY2tldHMuIFRoaXMgYWxzbyBsb29rcyBvayB0
byBtZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkkg
ZG9uJ3QgaGF2ZSBzdHJvbmcgcHJlZmVyZW5jZSBmb3IgdGhpcy4gQnV0LCBkbyB3ZSBoYXZlIGEg
cmVhc29uIHRvIHRlcm1pbmF0ZSBjb25uZWN0aW9uPzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VGhhbmtzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4tLTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5Zb3NoaTxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPk9uIE1vbiwgSmFuIDEzLCAy
MDIwIGF0IDEwOjI4IEFNIFYgQW5pbCBLdW1hciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaWxAY3Np
cjRwaS5pbiIgdGFyZ2V0PSJfYmxhbmsiPmFuaWxAY3NpcjRwaS5pbjwvYT4mZ3Q7IHdyb3RlOjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi1s
ZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY207Ym9yZGVyLWxlZnQ6cmdiKCAyMDQgLA0KICAgICAg
ICAgICAgICAgICAgICAgICAgMjA0ICwgMjA0ICkiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5IaSw8L3NwYW4+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5JIGhhdmUgc29t
ZSBwb2ludHMgcmVsYXRlZCB0byB0aGUgJm5ic3A7bW9kaWZpY2F0aW9ucyAoQ2hhbmdlIDIpIGJl
aW5nIHByb3Bvc2VkIG9uIGRhdGEgc2VxdWVuY2UgbWFwLiBQbGVhc2Ugc2VlIHRoZW0gaW5saW5l
LiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UaG91Z2gNCiBJIGFtIHB1dHRpbmcgZm9yd2Fy
ZCB0aGUgYmVsb3cgcG9pbnRzLCBpZiB0aGUgY29uc2Vuc3VzIGlzIGluIGZhdm91ciBvZiB0aGUg
cHJvcG9zZWQgY2hhbmdlIGZvciByZWR1Y2luZyBpbXBsZW1lbnRhdGlvbiBjb21wbGV4aXR5LCBJ
IGFtIGFsc28gT0sgd2l0aCB0aGF0IGFzIHdlbGwuJm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2IGNsYXNzPSJNc29Ob3JtYWwiIGFsaWduPSJjZW50ZXIiIHN0eWxlPSJ0ZXh0
LWFsaWduOmNlbnRlciI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWYiPg0KPGhyIHNpemU9IjIiIHdpZHRoPSIxMDAlIiBhbGlnbj0iY2VudGVyIiBp
ZD0iZ21haWwtbV83Njg3MTg0MzgyMjk5NTk2Nzc0endjaHIiPg0KPC9zcGFuPjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5Gcm9tOiA8L3NwYW4+DQo8L2I+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPiZxdW90O2FsYW4gZm9y
ZCZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5jb20iIHRhcmdldD0i
X2JsYW5rIj5hbGFuLmZvcmRAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5UbzogPC9iPjxhIGhy
ZWY9Im1haWx0bzptdWx0aXBhdGh0Y3BAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tdWx0aXBh
dGh0Y3BAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+U2VudDogPC9iPlRodXJzZGF5LCBKYW51YXJ5IDIs
IDIwMjAgNDoyMTozMiBBTTxicj4NCjxiPlN1YmplY3Q6IDwvYj5bbXVsdGlwYXRodGNwXSBSRkM2
ODI0YmlzIGVkaXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5IaSBhbGwsPG86cD48L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5XZeKAmWQgbG92ZSB0byBnZXQg
dGhpcyB0byBhIHN0YXRlIG9mIGNvbXBsZXRpb24gYXMgc29vbiBhcyBwb3NzaWJsZSwgYW5kIHRv
IHRoaXMgZW5kIEkgYW0gc3RhcnRpbmcgYSBuZXcgdGhyZWFkIG9uIHRoaXMgdG9waWMuIEluIGRp
c2N1c3Npb24gd2l0aCB0aGUgY2hhaXJzLCBpdA0KPGk+aXMgPC9pPnBvc3NpYmxlIHRvIG1ha2Ug
dGhlIGRlc2lyZWQgY2hhbmdlcyBpbiBBVVRINDggYXMgbG9uZyBhcyB0aGVyZSBpcyBXRyBjb25z
ZW5zdXMuIFRoZSBkaXNjdXNzaW9uIHNvIGZhciBoYXMgYmVlbiBmYWlybHkgbGltaXRlZCBpbiB0
ZXJtcyBvZiBwYXJ0aWNpcGF0aW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssc2Fucy1zZXJpZiI+SSB3b3VsZCBhc2sgdGhlIGNoYWlycyBwbGVhc2UgaWYgaXQgd2FzIHBv
c3NpYmxlIHRvIHNwZWNpZnkgYSB0aW1lIGJvdW5kIGZvciB0aGlzIGRpc2N1c3Npb24gYW5kIGEg
ZGVmYXVsdCBjb25jbHVzaW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZiI+UmVnYXJkaW5nIHRoZSBjaGFuZ2VzLCBpbiBzdW1tYXJ5LCB0aGVyZSBhcmUg
dHdvIGFyZWFzIHdoZXJlIGNoYW5nZXMgaGF2ZSBiZWVuIHJlcXVlc3RlZCBieSB0aGUgaW1wbGVt
ZW50YXRpb24gY29tbXVuaXR5LiBBcyB3ZSBhcmUgdGhlIElFVEYgd2Ugb2J2aW91c2x5IGhhdmUg
c3Ryb25nIGZvY3VzIG9uIOKAnHJ1bm5pbmcgY29kZeKAnSBhbmQNCiBzbyBlYXNlIG9mIGltcGxl
bWVudGluZyBzdGFuZGFyZHMtY29tcGxpYW50IGNvZGUgaXMgc3Ryb25nbHkgZGVzaXJhYmxlLiBI
b3dldmVyLCB3ZSBkbyBub3Qgd2lzaCB0byByZWR1Y2UgZnVuY3Rpb25hbGl0eSBhZ3JlZWQgYnkg
dGhlIElFVEYgY29tbXVuaXR5IGlmIGl0IGlzIGNvbnNpZGVyZWQgYSByZXF1aXJlZCBmZWF0dXJl
IGJ5IHRoZSBjb21tdW5pdHkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkNoYW5nZSAxPC9zcGFu
PjwvYj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJp
ZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkNoYW5nZSB0aGUgc2VudGVu
Y2UgcmVhZGluZzo8YnI+DQo8YnI+DQo8aT4mbmJzcDsgJm5ic3A7SWYgQiBoYXMgZGF0YSB0byBz
ZW5kIGZpcnN0LCB0aGVuIHRoZSByZWxpYWJsZSBkZWxpdmVyeSBvZiB0aGUgQUNLICYjNDM7IE1Q
X0NBUEFCTEUgY2FuIGJlIGluZmVycmVkIGJ5IHRoZSByZWNlaXB0IG9mIHRoaXMgZGF0YSB3aXRo
IGFuIE1QVENQIERhdGEgU2VxdWVuY2UgU2lnbmFsIChEU1MpIG9wdGlvbiAoU2VjdGlvbiAzLjMp
LiZuYnNwOzxicj4NCjwvaT48YnI+DQpUbzo8YnI+DQo8YnI+DQo8aT4mbmJzcDsgJm5ic3A7SWYg
QiBoYXMgZGF0YSB0byBzZW5kIGZpcnN0LCB0aGVuIHRoZSByZWxpYWJsZSBkZWxpdmVyeSBvZiB0
aGUgQUNLICYjNDM7IE1QX0NBUEFCTEUgaXMgZW5zdXJlZCBieSB0aGUgcmVjZWlwdCBvZiB0aGlz
IGRhdGEgd2l0aCBhbiBNUFRDUCBEYXRhIFNlcXVlbmNlIFNpZ25hbCAoRFNTKSBvcHRpb24gKFNl
Y3Rpb24gMy4zKSBjb250YWluaW5nIGEgREFUQV9BQ0sgZm9yIHRoZSBNUF9DQVBBQkxFICh3aGlj
aCBpcyB0aGUgZmlyc3Qgb2N0ZXQgb2YNCiB0aGUgZGF0YSBzZXF1ZW5jZSZuYnNwO3NwYWNlKS48
L2k+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPldoYXQgdGhpcyBtZWFuczo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWYiPlRoZSBjdXJyZW50IHRleHQgaXMgY29uY2VybmVkIG9ubHkgd2l0aCBlbnN1
cmluZyBhIHBhdGggaXMgTVBUQ1AgY2FwYWJsZSwgYW5kIHNvIG9ubHkgY2FyZXMgdGhhdCBEU1Mg
b3B0aW9uIG9jY3VycyBvbiBhIGRhdGEgcGFja2V0LiBIb3dldmVyLCB0aGUgTVBfQ0FQQUJMRSBv
cHRpb24gaXMgZGVmaW5lZCB0byBvY2N1cHkgdGhlIGZpcnN0DQogb2N0ZXQgb2YgZGF0YSBzZXF1
ZW5jZSBzcGFjZSBhbmQgdGh1cywgaWYgYW5hbG9nb3VzIHRvIFRDUCwgbXVzdCBiZSBhY2tub3ds
ZWRnZWQuICZndDtGcm9tIGFuIGltcGxlbWVudGF0aW9uIHBvaW50IG9mIHZpZXcgaXQgd291bGQg
bWFrZSBzZW5zZSBub3QgdG8gaGF2ZSB0aGlzIGhhbmdpbmcgYXJvdW5kIGZvcmV2ZXIgYW5kIGlu
c3RlYWQgZGVmaW5lIGl0IGlzIGFja25vd2xlZGdlZCBhdCB0aGUgY29ubmVjdGlvbiBsZXZlbCBh
cyBzb29uIGFzIHJlY2VpdmVkLg0KIFRoaXMgY2hhbmdlIGVuc3VyZXMgdGhlIGZpcnN0IGRhdGEg
cGFja2V0IGFsc28gREFUQV9BQ0tzIHRoaXMgTVBfQ0FQQUJMRSBvY3RldC48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90
dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZiI+Q2hhbmdlIDI8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkNoYW5nZSB0aGUgc2VudGVuY2Ug
cmVhZGluZzo8YnI+DQo8YnI+DQo8aT4mbmJzcDsgJm5ic3A7QSBEYXRhIFNlcXVlbmNlIE1hcHBp
bmcgZG9lcyBub3QgbmVlZCB0byBiZSBpbmNsdWRlZCBpbiBldmVyeSBNUFRDUCBwYWNrZXQsIGFz
IGxvbmcgYXMgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2UgaW4gdGhhdCBwYWNrZXQgaXMgY292
ZXJlZCBieSBhIG1hcHBpbmcga25vd24gYXQgdGhlIHJlY2VpdmVyLjwvaT48YnI+DQo8YnI+DQpU
bzo8YnI+DQo8YnI+DQo8aT4mbmJzcDsgJm5ic3A7VGhlIG1hcHBpbmcgcHJvdmlkZWQgYnkgYSBE
YXRhIFNlcXVlbmNlIE1hcHBpbmcgTVVTVCBhcHBseSB0byBzb21lIG9yIGFsbCBvZiB0aGUgc3Vi
ZmxvdyBzZXF1ZW5jZSBzcGFjZSBpbiB0aGUgVENQIHNlZ21lbnQgd2hpY2ggY2FycmllcyB0aGUg
b3B0aW9uLiBJdCBkb2VzIG5vdCBuZWVkIHRvIGJlIGluY2x1ZGVkIGluIGV2ZXJ5IE1QVENQIHBh
Y2tldCwgYXMgbG9uZyBhcyB0aGUgc3ViZmxvdyBzZXF1ZW5jZSBzcGFjZSBpbiB0aGF0IHBhY2tl
dA0KIGlzIGNvdmVyZWQgYnkgYSBtYXBwaW5nIGtub3duIGF0IHRoZSByZWNlaXZlci48YnI+DQo8
L2k+PGJyPg0KV2hhdCB0aGlzIG1lYW5zOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFs
JnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZiI+VGhlIGN1cnJlbnQgdGV4dCBkb2VzIG5vdCBwbGFjZSBhbnkgcmVz
dHJpY3Rpb25zIG9uIHdoZXJlIGEgbWFwcGluZyBjb3VsZCBhcHBlYXIuIEluIHRoZW9yeSBhIHNl
bmRlciBjb3VsZCBkZWZpbmUgYSB0aG91c2FuZCBkaWZmZXJlbnQgbWFwcGluZ3MgdXAgZnJvbnQs
IHNlbmQgdGhlbSBhbGwsIGFuZCBleHBlY3QgYSByZWNlaXZlcg0KIHRvIHN0b3JlIHRoaXMgYW5k
IHJlYXNzZW1ibGUgZGF0YSBhY2NvcmRpbmcgdG8gdGhlc2UgbWFwcGluZ3MgYXMgaXQgYXJyaXZl
cy4gSW5kZWVkLCB0aGlzIHdhcyBuZXZlciBleHBsaWNpdGx5IGRpc2FsbG93ZWQgc2luY2UgaXQg
4oCcbWlnaHQgaGF2ZSBiZWVuIHVzZWZ1bOKAnS4gVGhlIGltcGxlbWVudGF0aW9uIGNvbW11bml0
eSwgaG93ZXZlciwgaGFzIGV4cHJlc3NlZCBjb25jZXJucyBvdmVyIHRoZSBkaWZmaWN1bHR5IG9m
IGltcGxlbWVudGluZyB0aGlzDQogb3Blbi1lbmRlZGx5LiBIb3cgbWFueSBtYXBwaW5ncyBpcyBp
dCByZWFzb25hYmxlIHRvIHN0b3JlPyBJcyB0aGVyZSBhIERvUyByaXNrIGhlcmU/IEluc3RlYWQs
IGl0IGhhcyBiZWVuIHJlcXVlc3RlZCB0aGF0IHRoZWUgc3BlY2lmaWNhdGlvbiByZXN0cmljdHMg
dGhlIHBsYWNlbWVudCBvZiB0aGUgRFNTIG9wdGlvbiB0byBiZWluZyB3aXRoaW4gdGhlIHN1YmZs
b3cgc2VxdWVuY2Ugc3BhY2UgdG8gd2hpY2ggaXQgYXBwbGllcy48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkJlbG93IGFyZSBteSBjb21tZW50cyBvbiB0
aGlzLiBJIGhhZCBzaGFyZWQgc29tZSBvZiB0aGVzZSBwb2ludHMgaW4gYSBwcmV2aW91cyB0aHJl
YWQgdGhhdCB5b3UgaGFkIGluaXRpYXRlZCBpbiB0aGUgc2FtZSBjb250ZXh0LiZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VHJhbnNtaXR0aW5n
IGxhcmdlIG51bWJlciBvZiBub24tY29udGlndW91cyBkYXRhIHNlcXVlbmNlIG1hcHMgY291bGQg
YmUgYSBtaXNiZWhhdmlvdXIgKG1hcC1mbG9vZGluZyksIHRob3VnaCBpdCBpcyBub3QgY2xlYXIg
d2hldGhlciB0aGlzIGNhbiBnbyB0byB0aGUgZXh0ZW50IG9mIGNhdXNpbmcgYSBwb3RlbnRpYWwg
RG9TIHRvIHRoZQ0KIGRhdGEgcmVjZWl2ZXIuIFNvIHNvbWUgc29ydCBvZiByZXN0cmljdGlvbiBv
biB0aGlzIGNvdWxkIGJlIHVzZWZ1bC4mbmJzcDsgT25lIGFwcHJvYWNoIGNvdWxkIGJlIHRvIGlu
c2lzdCB0aGF0IHRoZSBkYXRhIHNlbmRlciBzaG91bGQgZW5zdXJlIHRoYXQgdGhlIG1hcCBiZWlu
ZyB0cmFuc21pdHRlZCBpcyBmb3IgaW4td2luZG93IGRhdGEsIGFzIHBlciB0aGUgcmVjZWl2ZXIg
YWR2ZXJ0aXNlZCB3aW5kb3cuIEEgcmVjZWl2ZXIgc2hvdWxkIGFueWhvdyBiZQ0KIHdpbGxpbmcg
dG8gc3RvcmUgdGhlIG1hcHMgZm9yIGluLXdpbmRvdyBkYXRhIHRvIGRlYWwgd2l0aCBwYWNrZXQg
bG9zcy4uIEZvciBleGFtcGxlLCB3aGVuIGEgd2luZG93IG9mIGRhdGEgc2VnbWVudHMgKHNheSAx
IHRvIDY0KSBpcyB0cmFuc21pdHRlZCwgZWFjaCBjYXJyeWluZyBpdHMgY29ycmVzcG9uZGluZyBt
YXAsIGFuZCBzZWdtZW50LTEgaXMgbG9zdCwgdGhlIG1hcHMgZm9yIHRoZSByZW1haW5pbmcgNjMg
bmVlZCB0byBiZSBzdG9yZWQgdGlsbA0KIHRoZSBsb3N0IHNlZ21lbnQgaXMgcmV0cmFuc21pdHRl
ZC4gT2YgY291cnNlLCBpbiB0aGlzIGNhc2UgdGhlIG1hcHMgd2lsbCBiZSBzdG9yZWQgYXQgdGhl
IHJlY2VpdmVyIHNpZGUgYWxvbmcgd2l0aCB0aGVpciBjb3JyZXNwb25kaW5nIGRhdGEuIEJ1dCB0
aGUgbmVlZCB0byBzdG9yZSBtdWx0aXBsZSBtYXBzIGZvciBpbi13aW5kb3cgZGF0YSB3b3VsZCBz
dGlsbCBiZSB0aGVyZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VGhlIHByb2JsZW0gd2l0aCB0aGUgcHJvcG9zZWQgY2hh
bmdlIChyZXN0cmljdGlvbikgaXMgdGhhdCBhIGRhdGEgc2VuZGVyIG1heSBmaW5kIGl0IGRpZmZp
Y3VsdCwgaW4gY2FzZSBhIG5lZWQgYXJpc2UgdG8gc2xpZ2h0bHkgZGVsYXkgdGhlIG1hcCBkZWxp
dmVyeSBieSBmZXcgc2VnbWVudHMsIGkuZS4sDQogc2VuZGluZyBzb21lIGRhdGEgZmlyc3Qgd2l0
aG91dCBtYXAsIGFuZCB0aGVuIHNlbmQgdGhlIGNvcnJlc3BvbmRpbmcgbWFwIGluIGEgbGF0ZXIg
c2VnbWVudCwgYXMgc2hvd24gYmVsb3c6PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImNvbG9yOnJnYigNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDAgLCAwICwgMA0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKTtiYWNrZ3Jv
dW5kLWNvbG9yOnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIDI1NSAsIDI1NSAsIDI1NSApO3dvcmQtc3BhY2luZzowcHgiPg0KPHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Nl
Z29lIFVJJnF1b3Q7LHNhbnMtc2VyaWYiPnN1YmZsb3ctMTombmJzcDsgJm5ic3A7ICZuYnNwOyBz
ZWdtZW50LTEmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHNl
Z21lbnQtMyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50LTQgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50
LTc8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9ImNvbG9yOnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDAgLCAwICwgMA0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKTtiYWNrZ3JvdW5kLWNvbG9y
OnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIDI1NSAsIDI1NSAsIDI1NSApO3dvcmQtc3BhY2luZzowcHgiPg0KPHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1
b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtieXRlczoxLTEwMCAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGJ5dGVzOjIwMS0zMDAgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Ynl0ZXM6MzAxLTQw
MCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IGJ5dGVzOjYwMS03MDA8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImNvbG9yOnJnYigNCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDAgLCAwICwgMA0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKTtiYWNr
Z3JvdW5kLWNvbG9yOnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIDI1NSAsIDI1NSAsIDI1NSApO3dvcmQtc3BhY2luZzowcHgiPg0KPHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsmbmJzcDtubyBt
YXAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDttYXAgZm9yIDEtMTAwICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO21hcCBmb3IgMjAxLTQwMCAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBtYXAgZm9yIDYwMS03MDA8L3NwYW4+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkm
cXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9ImNvbG9yOnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIDAgLCAwICwgMA0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKTtiYWNrZ3JvdW5kLWNvbG9yOnJnYigNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDI1NSAs
IDI1NSAsIDI1NSApO3dvcmQtc3BhY2luZzowcHgiPg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImNvbG9y
OnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIDAgLCAwICwgMA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgKTtiYWNrZ3JvdW5kLWNvbG9yOnJnYigNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDI1NSAsIDI1NSAsIDI1NSApO3dvcmQt
c3BhY2luZzowcHgiPg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImNvbG9yOnJnYigNCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDAgLCAwICwgMA0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKTtiYWNr
Z3JvdW5kLWNvbG9yOnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIDI1NSAsIDI1NSAsIDI1NSApO3dvcmQtc3BhY2luZzowcHgiPg0KPHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVv
dDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9ImNvbG9yOnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIDAgLCAwICwgMA0KICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKTtiYWNrZ3JvdW5kLWNvbG9yOnJnYigN
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDI1
NSAsIDI1NSAsIDI1NSApO3dvcmQtc3BhY2luZzowcHgiPg0KPHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNh
bnMtc2VyaWYiPnN1YmZsb3ctMjombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtzZWdtZW50LTIm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyBzZWdtZW50LTUgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHNlZ21lbnQtNiAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IHNlZ21lbnQtODwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iY29sb3I6cmdiKA0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAsIDAgLCAwDQogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICApO2JhY2tncm91
bmQtY29sb3I6cmdiKA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgMjU1ICwgMjU1ICwgMjU1ICk7d29yZC1zcGFjaW5nOjBweCI+DQo8c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vn
b2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2J5dGVzOiAxMDEtMjAw
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgYnl0ZXM6NDAxLTUwMCZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgYnl0ZXM6IDUwMS02MDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2J5dGVzOjcwMS04MDAmbmJzcDsmbmJzcDsmbmJz
cDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9ImNvbG9yOnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDAgLCAwICwgMA0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKTtiYWNrZ3JvdW5kLWNvbG9y
OnJnYigNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIDI1NSAsIDI1NSAsIDI1NSApO3dvcmQtc3BhY2luZzowcHgiPg0KPHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1
b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7bWFwIGZvciAxMDEtMjAw
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IG1hcCBmb3IgNDAxLTYwMCAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwO25vIG1hcCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7bWFwIGZvciA3MDEtODAwPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJjb2xvcjpyZ2Io
DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAw
ICwgMCAsIDANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICk7YmFja2dyb3VuZC1jb2xvcjpyZ2IoDQogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAyNTUgLCAyNTUgLCAyNTUgKTt3b3JkLXNwYWNp
bmc6MHB4Ij4NCjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90
O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJjb2xvcjpyZ2IoDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAwICwgMCAsIDANCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICk7YmFja2dyb3Vu
ZC1jb2xvcjpyZ2IoDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAyNTUgLCAyNTUgLCAyNTUgKTt3b3JkLXNwYWNpbmc6MHB4Ij4NCjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNh
bnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
Ij5JbiB0aGUgYWJvdmUgY2FzZSwgc2VnbWVudC0xIGdvZXMgd2l0aG91dCBtYXAgYW5kIGl0cyBt
YXAgaXMgaW5jbHVkZWQgbGF0ZXIgaW4gc2VnbWVudC0zLCB0aGUgbmV4dCBkYXRhIHNlZ21lbnQg
aW4gdGhlIHNhbWUgc3ViZmxvdy4gRnVydGhlciwgJm5ic3A7aW4gdGhlIGFib3ZlIHNjaGVkdWxp
bmcgcGF0dGVybiwgdGhlIG1hcCBpbiBzZWdtZW50LTMNCiBjYW5ub3QgY292ZXIgdGhlICZuYnNw
O2RhdGEgaW4gc2VnbWVudC0xIGFuZCBzZWdtZW50LTMsIGFzIHNvbWUgJm5ic3A7ZGF0YSBpbiBi
ZXR3ZWVuIChzZWdtZW50LTIpIGlzIHRyYW5zbWl0dGVkIHRocm91Z2ggYW5vdGhlciBzdWJmbG93
Li4mbmJzcDsgV2l0aCB0aGUgcHJvcG9zZWQgY2hhbmdlLCB0aGUgbWFwIGluIHNlZ21lbnQtMyB3
aWxsIGJlY29tZSBpbnZhbGlkIGFuZCB0aGlzIHdpbGwgZXZlbnR1YWxseSBicmVhayBzdWJmbG93
LTEsIHRob3VnaCB0aGlzIGNvdWxkDQogYmUgYSBjb3JuZXIgY2FzZS48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPlRoZSBxdWVzdGlvbiBhdCB0aGlzIHN0
YWdlIGlzIHdoeSB3b3VsZCBzZWdtZW50LTEgYmUgdHJhbnNtaXR0ZWQgd2l0aG91dCBpdHMgbWFw
LiBJbiB0aGUgY2FzZSBvZiBiaWRpcmVjdGlvbmFsIGRhdGEgdHJhbnNmZXIsIHRoZXJlIGNvdWxk
IGJlIGEgbmVlZCB0byBwYWNrIGJvdGggdGltZXN0YW1wIGFuZCBTQUNLICZuYnNwO29wdGlvbnMg
aW4NCiBhIGRhdGEgc2VnbWVudCwgaS5lLiwgcGlnZ3liYWNraW5nIG9mICZuYnNwO1NBQ0sgd2l0
aCBkYXRhLiBJZiB3ZSBjb25zaWRlciB0aGF0IHRpbWVzdGFtcCB0YWtlcyAxMiBieXRlcyBhbmQg
U0FDSywgZXZlbiB3aXRoIHNpbmdsZSBibG9jaywgJm5ic3A7dGFrZXMgYW5vdGhlciAxMCBieXRl
cywgdGhlIHJlbWFpbmluZyAxOCBieXRlcyBvcHRpb24gc3BhY2UgaXMgbm90IGFkZXF1YXRlIHRv
IGNhcnJ5IGRhdGEgc2VxdWVuY2Ugc2lnbmFsIHdpdGggbWFwLCBlc3BlY2lhbGx5DQogd2hlbiBE
U04gaXMgNjQgYml0IGxvbmcuIFNvIHRoZSBkZWxpdmVyeSBvZiBlaXRoZXIgb2YgdGhlIHR3byAo
U0FDSyBvciBtYXApIHdvdWxkIGJlIGRlbGF5ZWQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj5BcyBmYXIgYXMgSSB1bmRlcnN0YW5kLCBSRkMgMjAxOCAo
VENQIFNlbGVjdGl2ZSBBY2tub3dsZWRnZW1lbnQgT3B0aW9ucykgaW1wbGllcyB0aGF0IFNBQ0sg
c2hvdWxkIG5vdCBiZSBkZWxheWVkLiBJdCBzdGF0ZXMgJnF1b3Q7SWYgc2VudCBhdCBhbGwsIFNB
Q0sgb3B0aW9ucyBTSE9VTEQgYmUgaW5jbHVkZWQgaW4gYWxsIEFDS3Mgd2hpY2gNCiBkbyBub3Qg
QUNLIHRoZSBoaWdoZXN0IHNlcXVlbmNlIG51bWJlciBpbiB0aGUgZGF0YSByZWNlaXZlcidzIHF1
ZXVlJnF1b3Q7LiBJdCBhbHNvIHNheXMgJnF1b3Q7SWYgZGF0YSByZWNlaXZlciBnZW5lcmF0ZXMg
U0FDSyBvcHRpb25zIHVuZGVyIGFueSBjaXJjdW1zdGFuY2UsIGl0IFNIT1VMRCBnZW5lcmF0ZSB0
aGVtIHVuZGVyIGFsbCBwZXJtaXR0ZWQgY2lyY3Vtc3RhbmNlcyZxdW90Oy4gJm5ic3A7IFNvLCBh
cyBwYXJ0IG9mIG1lZXRpbmcgdGhlIFJGQyAyMDE4IHJlcXVpcmVtZW50cywNCiBpZiB0aGUgY29t
YmluYXRpb24gb2YgU0FDSyBhbmQgdGltZXN0YW1wIGlzIGdpdmVuIHByZWZlcmVuY2Ugb3ZlciBE
U1MsIGRhdGEgc2VnbWVudHMgY291bGQgYmUgdHJhbnNtaXR0ZWQgd2l0aG91dCB0aGVpciBtYXAu
Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5B
bm90aGVyIGNhc2Ugb2YgZGVsYXlpbmcgbWFwIGNvdWxkIGFyaXNlIGlmIHRoZSBkYXRhIHNlbmRl
ciBwcmVmZXJzIHRvIHNlbmQgQUREX0FERFIgb3B0aW9uLCBpbnN0ZWFkIG9mIG1hcCwgaW4gYSBk
YXRhIHNlZ21lbnQuIEl0IGlzIG5pY2UgdGhhdCBBRERfQUREUiBvcHRpb24gY2FuIGJlIGRlbGl2
ZXJlZCByZWxpYWJseSBpbiBhDQogcHVyZSBBQ0ssIGJ1dCBJIHRoaW5rIHRoaXMgaXMgbm90IHRo
ZSBjYXNlIHdpdGggRFNTIGF0IHByZXNlbnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OyxzYW5zLXNlcmlmIj5JZiB3ZSBhZG9wdCB0aGUgcHJvcG9zZWQgY2hhbmdlLCBJIHRo
aW5rIGl0IG1pZ2h0IGFsc28gYmUgaGVscGZ1bCB0byBzcGVsbCBvdXQgaG93IHRoZSByZWNlaXZl
ciBpcyBzdXBwb3NlZCB0byBiZWhhdmUsIGlmIGl0IGdldHMgbWFwcyBub3QgbWVldGluZyB0aGUg
TVVTVCBjb25kaXRpb24gaW4gdGhlIHByb3Bvc2VkIGNoYW5nZS4mbmJzcDsNCiBGb3IgZXhhbXBs
ZSB0ZXJtaW5hdGlvbiBvZiB0aGUgc3ViZmxvdyB3aXRoIE1QX1RDUFJTVCBvcHRpb24gKHNlY3Rp
b24gMy42IGluIFJGQyA2ODI0LWJpcykgd2l0aCBhcHByb3ByaWF0ZSByZWFzb24gY29kZSBhbmQg
VCBmbGFnIHZhbHVlIHRvIGludGltYXRlIHRoZSBkYXRhIHNlbmRlciB0aGUgY2F1c2UgZm9yIHN1
YmZsb3cgdGVybWluYXRpb24uJm5ic3A7Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmIj5XaXRoIHJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkFuaWw8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPlBsZWFzZSBj
YW4gbWVtYmVycyBvZiB0aGUgV0cgZXhwcmVzcyB3aGV0aGVyIHRoZXkgYXJlIGhhcHB5IHdpdGgg
dGhlc2UgY2hhbmdlcywgb3IgY29uY2VybmVkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZiI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5BbGFuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PGJyPg0KPGJyPg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQptdWx0aXBhdGh0Y3AgbWFp
bGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm11bHRpcGF0aHRjcEBpZXRmLm9yZyIgdGFy
Z2V0PSJfYmxhbmsiPm11bHRpcGF0aHRjcEBpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRpcGF0aHRjcCIgdGFyZ2V0PSJf
YmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNw
PC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCm11bHRpcGF0aHRjcCBtYWlsaW5n
IGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnIiB0YXJnZXQ9
Il9ibGFuayI+bXVsdGlwYXRodGNwQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNwIiB0YXJnZXQ9Il9ibGFu
ayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3A8L2E+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxwcmU+X19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188bzpwPjwvbzpwPjwvcHJlPg0K
PHByZT5tdWx0aXBhdGh0Y3AgbWFpbGluZyBsaXN0PG86cD48L286cD48L3ByZT4NCjxwcmU+PGEg
aHJlZj0ibWFpbHRvOm11bHRpcGF0aHRjcEBpZXRmLm9yZyI+bXVsdGlwYXRodGNwQGlldGYub3Jn
PC9hPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNwIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL211bHRpcGF0aHRjcDwvYT48bzpwPjwvbzpwPjwvcHJlPg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_LNXP123MB2587FEF165A7C4B988799EE8EB000LNXP123MB2587GBRP_--


From nobody Mon Feb  3 23:39:26 2020
Return-Path: <nsd.ietf@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E3F120129 for <multipathtcp@ietfa.amsl.com>; Mon,  3 Feb 2020 23:39:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 P3H26QVKqk8x for <multipathtcp@ietfa.amsl.com>; Mon,  3 Feb 2020 23:39:20 -0800 (PST)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 07BBA120052 for <multipathtcp@ietf.org>; Mon,  3 Feb 2020 23:38:59 -0800 (PST)
Received: by mail-vs1-xe29.google.com with SMTP id v141so10672910vsv.12 for <multipathtcp@ietf.org>; Mon, 03 Feb 2020 23:38:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k5jEGIgrCz1eFvqW4AghIaLOeoHYKLG5RUAmFjuAXoE=; b=m73CGsyNZ5Hjkn/D+IB3VC/g9/J5hIXAxQLiBUKGokMd5dN4/s2q49fymcEmIhqAW6 psHGqfAhbEz/LiLgD9/5CvA2kgSa0aYo9vDIVnFKnJtNUidPfvqRm8BElL/nLzakOw4J oNemKHNnH5sny7F7yUMpWdqg6pgf42Z9qKZGv3TH1oBJza3222xYDcVu3+u5qaUJIZ1H WxCK4axKZhttMbbTiVp9uBa+Gt9R3EnYfr1U4PfLC2PPvEfyGbrp7HA9EcARnIWN/iuj TKocKObsCluLPoB+VZglfqD6yiXi7z1ihQGNEbBfCHyxKR4DkW8/UzxesB4Vq9ruPWIj 39/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k5jEGIgrCz1eFvqW4AghIaLOeoHYKLG5RUAmFjuAXoE=; b=TN3Xg6Mf1WJMqlACePu03u825GE9FPiPOPpuAxbmKCElebwOA62IqJSPgADAW0sP2g FiqWH5WIt1WSSDTUl1NRF6eHbGi4c3RmaULvUny+k2tKEQ7Q2vXACt9xG7CcvkX0WMtI rrH36eeoRB23W0iS5U4kbHx6CEPDGKPOh1Uz7itt6GMMmR8nXeLdC+RzEZYDwyXjoBbj ay7dw2KU6phc5uBkrUtAbcFDQnuMG312mCuuRQZKdwtHg/FLYI4c6ms7fJQd5Ks/IOrE Nfss3O2qhMmGLfej1yz6203/rEmd/p20i76dR1DMkPK4rXUAzsoLkPyInxaYT82Vch/y m1Ew==
X-Gm-Message-State: APjAAAUUxw434yPDl402YOeFSqOka566pmXKmGcfBgIG/9LifwuAiQkG Vg4SeoIDZzKAiBEKWUs6o6Z/8/OyTnhCn4jFK44=
X-Google-Smtp-Source: APXvYqzzaj9TxN893fuPSUlQw9sf1tnA97xIFu3bdiNc5S9AO04X/bE93YrmW7smbBDr+/MjAd5Q5BfXXvBMpn8DxgA=
X-Received: by 2002:a67:ec88:: with SMTP id h8mr17787665vsp.65.1580801937018;  Mon, 03 Feb 2020 23:38:57 -0800 (PST)
MIME-Version: 1.0
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in>
In-Reply-To: <146023054.25180934.1580661581660@csir4pi.in>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Mon, 3 Feb 2020 23:38:45 -0800
Message-ID: <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com>
To: V Anil Kumar <anil@csir4pi.in>
Cc: alan ford <alan.ford@gmail.com>, multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ea92f9059dbb2193"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Ftm_7H-4LuRTNKGuuTLE-NCKFOo>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2020 07:39:24 -0000

--000000000000ea92f9059dbb2193
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Anil,

Thanks for pointing it out. I overlooked this one.
This looks an interesting point.

It seems to me that whether RST is happen or not depends on the size of
receive window according to the text.
If the receive window size is big enough to accommodate segment 1 and
segment 3, the text "Implementations MAY hold onto such unmapped data for a
short while in the expectation that a mapping will arrive shortly. " can be
applied to the segment 1. As a result, the segment 1 won't be discarded.
However, this might be contradict with the new texts Alan proposed? Or, am
I missing something?

Thanks,
--
Yoshi



On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in> wrote:

> Hi Yoshi,
>
> Thanks for this point. In fact, I had initially not thought of a scenario=
,
> where the map is being delivered through a retransmitted data packet whil=
e
> its first transmission did not include the map. Now I am just seeing the
> document (RFC 6824-bis) in this context.
>
> My understanding is that in scenarios like what I described in my previou=
s
> mail, RST is likely to happen whether we explicitly state so or not. Plea=
se
> see the paragraph containing the below text in RFC 6824-bis.
>
> "If a mapping for that subflow-level sequence space does not arrive withi=
n
> a receive window of data, that subflow SHOULD be treated as broken, close=
d
> with a RST, and any unmapped data silently discarded."
>
> if we assume that the map is included while retransmitting the data (even
> though the first transmission did not contain the map for some reasons),
>  we could argue that RST could be avoided provided that the retransmissio=
n
> is triggered within a receive window of data. But the question here would
> be how and when will the retransmission take place. In this case, the
> subflow may not initiate the retransmission of data by its own (i.e., no
> retransmission due to three duplicate ACKs or RTO expiry at subflow level=
)
> as there is no segment loss at subflow level sequence space. So there cou=
ld
> be a high possibility of RST happening even before the map delivery throu=
gh
> retransmission.
>
> With regards,
>
> Anil
>
> ------------------------------
> *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>
> *To: *"V Anil Kumar" <anil@csir4pi.in>
> *Cc: *"alan ford" <alan.ford@gmail.com>, "multipathtcp" <
> multipathtcp@ietf.org>
> *Sent: *Saturday, February 1, 2020 3:39:51 AM
> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation
> feedback
>
> Hi Anil,
>
> I have a question about your proposed text.
> I am actually wondering if we really want to terminate connection here.
>
> The packets without proper mappings will be treated as invalid and will b=
e
> discarded.
> If an implementation failed to attach proper mapping for some reasons
> (e.g. option space), it might be able to attach the proper one when it
> retransmits the packets. This also looks ok to me.
>
> I don't have strong preference for this. But, do we have a reason to
> terminate connection?
>
> Thanks,
> --
> Yoshi
>
> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in> wrote:
>
>> Hi,
>>
>> I have some points related to the  modifications (Change 2) being
>> proposed on data sequence map. Please see them inline. Though I am
>> putting forward the below points, if the consensus is in favour of the
>> proposed change for reducing implementation complexity, I am also OK wit=
h
>> that as well.
>>
>> ------------------------------
>> *From: *"alan ford" <alan.ford@gmail.com>
>> *To: *multipathtcp@ietf.org
>> *Sent: *Thursday, January 2, 2020 4:21:32 AM
>> *Subject: *[multipathtcp] RFC6824bis edits based on implementation
>> feedback
>>
>> Hi all,
>> We=E2=80=99d love to get this to a state of completion as soon as possib=
le, and
>> to this end I am starting a new thread on this topic. In discussion with
>> the chairs, it *is *possible to make the desired changes in AUTH48 as
>> long as there is WG consensus. The discussion so far has been fairly
>> limited in terms of participation.
>>
>> I would ask the chairs please if it was possible to specify a time bound
>> for this discussion and a default conclusion.
>>
>> Regarding the changes, in summary, there are two areas where changes hav=
e
>> been requested by the implementation community. As we are the IETF we
>> obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so eas=
e of implementing
>> standards-compliant code is strongly desirable. However, we do not wish =
to
>> reduce functionality agreed by the IETF community if it is considered a
>> required feature by the community.
>>
>>
>> *Change 1*
>>
>> Change the sentence reading:
>>
>>
>> *   If B has data to send first, then the reliable delivery of the ACK +
>> MP_CAPABLE can be inferred by the receipt of this data with an MPTCP Dat=
a
>> Sequence Signal (DSS) option (Section 3.3). *
>> To:
>>
>>
>> *   If B has data to send first, then the reliable delivery of the ACK +
>> MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data
>> Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for the
>> MP_CAPABLE (which is the first octet of the data sequence space).*
>> What this means:
>>
>> The current text is concerned only with ensuring a path is MPTCP capable=
,
>> and so only cares that DSS option occurs on a data packet. However, the
>> MP_CAPABLE option is defined to occupy the first octet of data sequence
>> space and thus, if analogous to TCP, must be acknowledged. >From an
>> implementation point of view it would make sense not to have this hangin=
g
>> around forever and instead define it is acknowledged at the connection
>> level as soon as received. This change ensures the first data packet als=
o
>> DATA_ACKs this MP_CAPABLE octet.
>>
>>
>> *Change 2*
>>
>> Change the sentence reading:
>>
>> *   A Data Sequence Mapping does not need to be included in every MPTCP
>> packet, as long as the subflow sequence space in that packet is covered =
by
>> a mapping known at the receiver.*
>>
>> To:
>>
>>
>> *   The mapping provided by a Data Sequence Mapping MUST apply to some o=
r
>> all of the subflow sequence space in the TCP segment which carries the
>> option. It does not need to be included in every MPTCP packet, as long a=
s
>> the subflow sequence space in that packet is covered by a mapping known =
at
>> the receiver.*
>> What this means:
>>
>> The current text does not place any restrictions on where a mapping coul=
d
>> appear. In theory a sender could define a thousand different mappings up
>> front, send them all, and expect a receiver to store this and reassemble
>> data according to these mappings as it arrives. Indeed, this was never
>> explicitly disallowed since it =E2=80=9Cmight have been useful=E2=80=9D.=
 The implementation
>> community, however, has expressed concerns over the difficulty of
>> implementing this open-endedly. How many mappings is it reasonable to
>> store? Is there a DoS risk here? Instead, it has been requested that the=
e
>> specification restricts the placement of the DSS option to being within =
the
>> subflow sequence space to which it applies.
>>
>> Below are my comments on this. I had shared some of these points in a
>> previous thread that you had initiated in the same context.
>>
>> Transmitting large number of non-contiguous data sequence maps could be =
a
>> misbehaviour (map-flooding), though it is not clear whether this can go =
to
>> the extent of causing a potential DoS to the data receiver. So some sort=
 of
>> restriction on this could be useful.  One approach could be to insist th=
at
>> the data sender should ensure that the map being transmitted is for
>> in-window data, as per the receiver advertised window. A receiver should
>> anyhow be willing to store the maps for in-window data to deal with pack=
et
>> loss. For example, when a window of data segments (say 1 to 64) is
>> transmitted, each carrying its corresponding map, and segment-1 is lost,
>> the maps for the remaining 63 need to be stored till the lost segment is
>> retransmitted. Of course, in this case the maps will be stored at the
>> receiver side along with their corresponding data. But the need to store
>> multiple maps for in-window data would still be there.
>>
>> The problem with the proposed change (restriction) is that a data sender
>> may find it difficult, in case a need arise to slightly delay the map
>> delivery by few segments, i.e., sending some data first without map, and
>> then send the corresponding map in a later segment, as shown below:
>>
>> subflow-1:      segment-1                   segment-3
>> segment-4                       segment-7
>>
>>                       bytes:1-100                 bytes:201-300
>>    bytes:301-400                 bytes:601-700
>>
>>                       no map                        map for 1-100
>>      map for 201-400             map for 601-700
>>
>>
>>
>>
>> subflow-2:       segment-2                  segment-5
>> segment-6                       segment-8
>>
>>                        bytes: 101-200           bytes:401-500
>>         bytes: 501-600                bytes:701-800
>>
>>                        map for 101-200       map for 401-600
>>  no map                            map for 701-800
>>
>>
>>
>> In the above case, segment-1 goes without map and its map is included
>> later in segment-3, the next data segment in the same subflow. Further, =
 in
>> the above scheduling pattern, the map in segment-3 cannot cover the  dat=
a
>> in segment-1 and segment-3, as some  data in between (segment-2) is
>> transmitted through another subflow.  With the proposed change, the map =
in
>> segment-3 will become invalid and this will eventually break subflow-1,
>> though this could be a corner case.
>>
>> The question at this stage is why would segment-1 be transmitted without
>> its map. In the case of bidirectional data transfer, there could be a ne=
ed
>> to pack both timestamp and SACK  options in a data segment, i.e.,
>> piggybacking of  SACK with data. If we consider that timestamp takes 12
>> bytes and SACK, even with single block,  takes another 10 bytes, the
>> remaining 18 bytes option space is not adequate to carry data sequence
>> signal with map, especially when DSN is 64 bit long. So the delivery of
>> either of the two (SACK or map) would be delayed.
>>
>> As far as I understand, RFC 2018 (TCP Selective Acknowledgement Options)
>> implies that SACK should not be delayed. It states "If sent at all, SACK
>> options SHOULD be included in all ACKs which do not ACK the highest
>> sequence number in the data receiver's queue". It also says "If data
>> receiver generates SACK options under any circumstance, it SHOULD genera=
te
>> them under all permitted circumstances".   So, as part of meeting the RF=
C
>> 2018 requirements, if the combination of SACK and timestamp is given
>> preference over DSS, data segments could be transmitted without their ma=
p.
>>
>> Another case of delaying map could arise if the data sender prefers to
>> send ADD_ADDR option, instead of map, in a data segment. It is nice that
>> ADD_ADDR option can be delivered reliably in a pure ACK, but I think thi=
s
>> is not the case with DSS at present.
>>
>> If we adopt the proposed change, I think it might also be helpful to
>> spell out how the receiver is supposed to behave, if it gets maps not
>> meeting the MUST condition in the proposed change.  For example terminat=
ion
>> of the subflow with MP_TCPRST option (section 3.6 in RFC 6824-bis) with
>> appropriate reason code and T flag value to intimate the data sender the
>> cause for subflow termination.
>>
>> With regards,
>>
>> Anil
>>
>> Please can members of the WG express whether they are happy with these
>> changes, or concerned.
>>
>> Best regards,
>> Alan
>>
>>
>> _______________________________________________
>> multipathtcp mailing list
>> multipathtcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>
>>
>>
>> _______________________________________________
>> multipathtcp mailing list
>> multipathtcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>
>
>
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><div>=
<br></div><div>Thanks for pointing it out. I overlooked this one.</div><div=
>This looks an interesting point.<br></div><div><br></div><div>It seems to =
me that whether RST is happen or not depends on the size of receive window =
according to the text.<br></div><div>If the receive window size is big enou=
gh to accommodate=C2=A0segment 1 and segment 3, the text &quot;<span style=
=3D"color:rgb(0,0,0);font-size:13.3333px">Implementations MAY hold onto suc=
h unmapped data for a short while in=C2=A0</span><span style=3D"color:rgb(0=
,0,0);font-size:13.3333px">the expectation that a mapping will arrive short=
ly. &quot;=C2=A0</span>can be applied to the segment 1. As a result, the se=
gment 1 won&#39;t be discarded.=C2=A0</div><div>However, this might be cont=
radict with the new texts Alan proposed? Or, am I missing something?</div><=
div><br></div><div>Thanks,</div><div>--</div><div>Yoshi</div><div><br></div=
><div><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar &lt;<a href=3D"mailto=
:anil@csir4pi.in" target=3D"_blank">anil@csir4pi.in</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div><div styl=
e=3D"font-family:arial,helvetica,sans-serif"><div>Hi Yoshi,</div><br><div>T=
hanks for this point. In fact, I had initially not thought of a scenario, w=
here the map is being delivered through a retransmitted data packet while i=
ts first transmission did not include the map. Now I am just seeing the doc=
ument (RFC 6824-bis) in this context.</div><br><div>My understanding is tha=
t in scenarios like what I described in my previous mail, RST is likely to =
happen whether we explicitly state so or not. Please see the paragraph cont=
aining the below text in RFC 6824-bis. =C2=A0</div><br><div>&quot;If a mapp=
ing for that subflow-level sequence space does not arrive within a receive =
window of data, that subflow SHOULD be treated as broken, closed with a RST=
, and any unmapped data silently discarded.&quot;</div><br><div>if we assum=
e that the map is included while retransmitting the data (even though the f=
irst transmission did not contain the map for some reasons), =C2=A0we could=
 argue that RST could be avoided provided that the retransmission is trigge=
red within a receive window of data. But the question here would be how and=
 when will the retransmission take place. In this case, the subflow may not=
 initiate the retransmission of data by its own (i.e., no retransmission du=
e to three duplicate ACKs or RTO expiry at subflow level) as there is no se=
gment loss at subflow level sequence space. So there could be a high possib=
ility of RST happening even before the map delivery through retransmission.=
=C2=A0</div><br><div>With regards,=C2=A0</div><br><div>Anil</div><div>=C2=
=A0</div><hr id=3D"gmail-m_218086596951724501gmail-m_2982267033577902985zwc=
hr"><div><b>From: </b>&quot;Yoshifumi Nishida&quot; &lt;<a href=3D"mailto:n=
sd.ietf@gmail.com" target=3D"_blank">nsd.ietf@gmail.com</a>&gt;<br><b>To: <=
/b>&quot;V Anil Kumar&quot; &lt;<a href=3D"mailto:anil@csir4pi.in" target=
=3D"_blank">anil@csir4pi.in</a>&gt;<br><b>Cc: </b>&quot;alan ford&quot; &lt=
;<a href=3D"mailto:alan.ford@gmail.com" target=3D"_blank">alan.ford@gmail.c=
om</a>&gt;, &quot;multipathtcp&quot; &lt;<a href=3D"mailto:multipathtcp@iet=
f.org" target=3D"_blank">multipathtcp@ietf.org</a>&gt;<br><b>Sent: </b>Satu=
rday, February 1, 2020 3:39:51 AM<br><b>Subject: </b>Re: [multipathtcp] RFC=
6824bis edits based on implementation feedback<br></div><br><div><div dir=
=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><br><div>I ha=
ve a question about your proposed text.</div><div><div>I am actually wonder=
ing if we really want to terminate connection here.=C2=A0</div></div><br><d=
iv>The packets without proper mappings will be treated as invalid and will =
be discarded.=C2=A0</div><div>If an implementation failed to attach proper =
mapping for some reasons (e.g. option space), it might be able to attach th=
e proper one when it retransmits the packets. This also looks ok to me.</di=
v><br><div>I don&#39;t have strong preference for this. But, do we have a r=
eason to terminate connection?</div><br><div>Thanks,</div><div>--<br></div>=
<div>Yoshi</div><br><div><div dir=3D"ltr">On Mon, Jan 13, 2020 at 10:28 AM =
V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow%20noope=
ner%20noreferrer nofollow noopener noreferrer" target=3D"_blank">anil@csir4=
pi.in</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div><div><div><div style=3D"font-family:arial,helvetica,sans-serif"><=
div><span style=3D"font-size:12pt;line-height:1.3">Hi,</span><br></div><div=
><div style=3D"font-family:arial,helvetica,sans-serif"><div style=3D"font-f=
amily:arial,helvetica,sans-serif"><div style=3D"font-family:arial,helvetica=
,sans-serif"><div style=3D"font-family:arial,helvetica,sans-serif"><div sty=
le=3D"font-family:arial,helvetica,sans-serif"><div style=3D"font-family:ari=
al,helvetica,sans-serif"><div style=3D"font-family:arial,helvetica,sans-ser=
if"><br><div>I have some points related to the =C2=A0modifications (Change =
2) being proposed on data sequence map. Please see them inline.=C2=A0<span =
style=3D"color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:=
16px;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0p=
x;text-transform:none;white-space:normal;word-spacing:0px;background-color:=
rgb(255,255,255);float:none;display:inline">Though I am putting forward the=
 below points, if the consensus is in favour of the proposed change for red=
ucing implementation complexity, I am also OK with that as well.=C2=A0</spa=
n><br></div><br><hr id=3D"gmail-m_218086596951724501gmail-m_298226703357790=
2985gmail-m_7687184382299596774zwchr"><div><b>From: </b>&quot;alan ford&quo=
t; &lt;<a href=3D"mailto:alan.ford@gmail.com" rel=3D"nofollow%20noopener%20=
noreferrer nofollow noopener noreferrer" target=3D"_blank">alan.ford@gmail.=
com</a>&gt;<br><b>To: </b><a href=3D"mailto:multipathtcp@ietf.org" rel=3D"n=
ofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"_bl=
ank">multipathtcp@ietf.org</a><br><b>Sent: </b>Thursday, January 2, 2020 4:=
21:32 AM<br><b>Subject: </b>[multipathtcp] RFC6824bis edits based on implem=
entation feedback<br></div><br><div>Hi all,<br><div>We=E2=80=99d love to ge=
t this to a state of completion as soon as possible, and to this end I am s=
tarting a new thread on this topic. In discussion with the chairs, it <i>is=
 </i>possible to make the desired changes in AUTH48 as long as there is WG =
consensus. The discussion so far has been fairly limited in terms of partic=
ipation.</div><br><div>I would ask the chairs please if it was possible to =
specify a time bound for this discussion and a default conclusion.</div><br=
><div>Regarding the changes, in summary, there are two areas where changes =
have been requested by the implementation community. As we are the IETF we =
obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so ease o=
f implementing standards-compliant code is strongly desirable. However, we =
do not wish to reduce functionality agreed by the IETF community if it is c=
onsidered a required feature by the community.</div><br><br><div><b>Change =
1</b></div><div><b><br></b></div><div>Change the sentence reading:<br><br><=
i>=C2=A0 =C2=A0If B has data to send first, then the reliable delivery of t=
he ACK + MP_CAPABLE can be inferred by the receipt of this data with an MPT=
CP Data Sequence Signal (DSS) option (Section 3.3).=C2=A0<br></i><br>To:<br=
><br><i>=C2=A0 =C2=A0If B has data to send first, then the reliable deliver=
y of the ACK + MP_CAPABLE is ensured by the receipt of this data with an MP=
TCP Data Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK f=
or the MP_CAPABLE (which is the first octet of the data sequence=C2=A0space=
).<br></i><br></div><div>What this means:</div><br><div>The current text is=
 concerned only with ensuring a path is MPTCP capable, and so only cares th=
at DSS option occurs on a data packet. However, the MP_CAPABLE option is de=
fined to occupy the first octet of data sequence space and thus, if analogo=
us to TCP, must be acknowledged. &gt;From an implementation point of view i=
t would make sense not to have this hanging around forever and instead defi=
ne it is acknowledged at the connection level as soon as received. This cha=
nge ensures the first data packet also DATA_ACKs this MP_CAPABLE octet.</di=
v><br><br><div><b>Change 2</b></div><div><b><br></b></div><div>Change the s=
entence reading:<br><br><i>=C2=A0 =C2=A0A Data Sequence Mapping does not ne=
ed to be included in every MPTCP packet, as long as the subflow sequence sp=
ace in that packet is covered by a mapping known at the receiver.</i><br><b=
r>To:<br><br><i>=C2=A0 =C2=A0The mapping provided by a Data Sequence Mappin=
g MUST apply to some or all of the subflow sequence space in the TCP segmen=
t which carries the option. It does not need to be included in every MPTCP =
packet, as long as the subflow sequence space in that packet is covered by =
a mapping known at the receiver.<br></i><br>What this means:</div><br><div>=
The current text does not place any restrictions on where a mapping could a=
ppear. In theory a sender could define a thousand different mappings up fro=
nt, send them all, and expect a receiver to store this and reassemble data =
according to these mappings as it arrives. Indeed, this was never explicitl=
y disallowed since it =E2=80=9Cmight have been useful=E2=80=9D. The impleme=
ntation community, however, has expressed concerns over the difficulty of i=
mplementing this open-endedly. How many mappings is it reasonable to store?=
 Is there a DoS risk here? Instead, it has been requested that thee specifi=
cation restricts the placement of the DSS option to being within the subflo=
w sequence space to which it applies.</div><br><div>Below are my comments o=
n this. I had shared some of these points in a previous thread that you had=
 initiated in the same context.=C2=A0</div><br><div>Transmitting large numb=
er of non-contiguous data sequence maps could be a misbehaviour (map-floodi=
ng), though it is not clear whether this can go to the extent of causing a =
potential DoS to the data receiver. So some sort of restriction on this cou=
ld be useful.=C2=A0 One approach could be to insist that the data sender sh=
ould ensure that the map being transmitted is for in-window data, as per th=
e receiver advertised window. A receiver should anyhow be willing to store =
the maps for in-window data to deal with packet loss. For example, when a w=
indow of data segments (say 1 to 64) is transmitted, each carrying its corr=
esponding map, and segment-1 is lost, the maps for the remaining 63 need to=
 be stored till the lost segment is retransmitted. Of course, in this case =
the maps will be stored at the receiver side along with their corresponding=
 data. But the need to store multiple maps for in-window data would still b=
e there.</div><br><div><span style=3D"color:rgb(0,0,0);font-family:arial,he=
lvetica,sans-serif;font-size:16px;font-style:normal;font-weight:normal;lett=
er-spacing:normal;line-height:20.8px;text-indent:0px;text-transform:none;wh=
ite-space:normal;word-spacing:0px;float:none;background-color:rgb(255,255,2=
55);display:inline">The problem with the proposed change (restriction) is t=
hat a data sender may find it difficult, in case a need arise to slightly d=
elay the map delivery by few segments, i.e., sending some data first withou=
t map, and then send the corresponding map in a later segment, as shown bel=
ow:</span><br></div><br><div><p class=3D"MsoNormal" style=3D"color:rgb(0,0,=
0);font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font=
-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;li=
ne-height:normal;text-indent:0px;text-transform:none;white-space:normal;wor=
d-spacing:0px;margin:0px;background-color:rgb(255,255,255)"><span lang=3D"E=
N-US" style=3D"font-size:10pt">subflow-1:=C2=A0 =C2=A0 =C2=A0 segment-1=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 segment-3=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-4 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-7</span></p><p class=
=3D"MsoNormal" style=3D"color:rgb(0,0,0);font-family:&quot;segoe ui&quot;,&=
quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-=
weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text=
-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-c=
olor:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">=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=C2=A0=C2=A0=C2=A0bytes:1-100 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 bytes:201-300 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0bytes:301-400 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 bytes:601-700</span></p><p class=3D"MsoNormal" style=
=3D"color:rgb(0,0,0);font-family:&quot;segoe ui&quot;,&quot;lucida sans&quo=
t;,sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter=
-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;whit=
e-space:normal;word-spacing:0px;margin:0px;background-color:rgb(255,255,255=
)"><span lang=3D"EN-US" style=3D"font-size:10pt">=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0no map =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ma=
p for 1-100 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0map for 201-400=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 map for 601-700</span></p><p cla=
ss=3D"MsoNormal" style=3D"color:rgb(0,0,0);font-family:&quot;segoe ui&quot;=
,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;fon=
t-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;margin:0px;background=
-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt"><br>=
</span></p><p class=3D"MsoNormal" style=3D"color:rgb(0,0,0);font-family:&qu=
ot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;font=
-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal;t=
ext-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;marg=
in:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"fon=
t-size:10pt"><br></span></p><p class=3D"MsoNormal" style=3D"color:rgb(0,0,0=
);font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-=
size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;lin=
e-height:normal;text-indent:0px;text-transform:none;white-space:normal;word=
-spacing:0px;margin:0px;background-color:rgb(255,255,255)"><br></p><p class=
=3D"MsoNormal" style=3D"color:rgb(0,0,0);font-family:&quot;segoe ui&quot;,&=
quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-=
weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text=
-transform:none;white-space:normal;word-spacing:0px;margin:0px;background-c=
olor:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">subflo=
w-2:=C2=A0 =C2=A0 =C2=A0 =C2=A0segment-2=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-5 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-6 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-8</span></p><p cla=
ss=3D"MsoNormal" style=3D"color:rgb(0,0,0);font-family:&quot;segoe ui&quot;=
,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;fon=
t-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;margin:0px;background=
-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">=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=C2=A0=C2=A0=C2=A0=C2=A0bytes: 101-200 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 bytes:401-500=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 bytes: 501-600 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bytes:701-800=C2=A0=C2=A0=C2=
=A0</span></p><p class=3D"MsoNormal" style=3D"color:rgb(0,0,0);font-family:=
&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;f=
ont-style:normal;font-weight:normal;letter-spacing:normal;line-height:norma=
l;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;m=
argin:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"=
font-size:10pt">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0map for 101-200 =C2=A0 =C2=A0 =C2=A0 map for 401-60=
0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0no map =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=A0ma=
p for 701-800</span></p><p class=3D"MsoNormal" style=3D"color:rgb(0,0,0);fo=
nt-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size=
:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-he=
ight:normal;text-indent:0px;text-transform:none;white-space:normal;word-spa=
cing:0px;margin:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US"=
 style=3D"font-size:10pt"></span><br></p><p class=3D"MsoNormal" style=3D"co=
lor:rgb(0,0,0);font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,san=
s-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-spaci=
ng:normal;line-height:normal;text-indent:0px;text-transform:none;white-spac=
e:normal;word-spacing:0px;margin:0px;background-color:rgb(255,255,255)"><sp=
an lang=3D"EN-US" style=3D"font-size:10pt"></span><br></p>In the above case=
, segment-1 goes without map and its map is included later in segment-3, th=
e next data segment in the same subflow. Further, =C2=A0in the above schedu=
ling pattern, the map in segment-3 cannot cover the =C2=A0data in segment-1=
 and segment-3, as some =C2=A0data in between (segment-2) is transmitted th=
rough another subflow.=C2=A0 With the proposed change, the map in segment-3=
 will become invalid and this will eventually break subflow-1, though this =
could be a corner case.</div><br><div>The question at this stage is why wou=
ld segment-1 be transmitted without its map. In the case of bidirectional d=
ata transfer, there could be a need to pack both timestamp and SACK =C2=A0o=
ptions in a data segment, i.e., piggybacking of =C2=A0SACK with data. If we=
 consider that timestamp takes 12 bytes and SACK, even with single block, =
=C2=A0takes another 10 bytes, the remaining 18 bytes option space is not ad=
equate to carry data sequence signal with map, especially when DSN is 64 bi=
t long. So the delivery of either of the two (SACK or map) would be delayed=
.</div><br><div>As far as I understand, RFC 2018 (TCP Selective Acknowledge=
ment Options) implies that SACK should not be delayed. It states &quot;If s=
ent at all, SACK options SHOULD be included in all ACKs which do not ACK th=
e highest sequence number in the data receiver&#39;s queue&quot;. It also s=
ays &quot;If data receiver generates SACK options under any circumstance, i=
t SHOULD generate them under all permitted circumstances&quot;. =C2=A0 So, =
as part of meeting the RFC 2018 requirements, if the combination of SACK an=
d timestamp is given preference over DSS, data segments could be transmitte=
d without their map.=C2=A0</div><br><div>Another case of delaying map could=
 arise if the data sender prefers to send ADD_ADDR option, instead of map, =
in a data segment. It is nice that ADD_ADDR option can be delivered reliabl=
y in a pure ACK, but I think this is not the case with DSS at present.</div=
><br><div>If we adopt the proposed change, I think it might also be helpful=
 to spell out how the receiver is supposed to behave, if it gets maps not m=
eeting the MUST condition in the proposed change.=C2=A0 For example termina=
tion of the subflow with MP_TCPRST option (section 3.6 in RFC 6824-bis) wit=
h appropriate reason code and T flag value to intimate the data sender the =
cause for subflow termination.=C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0</div></div><div>With regards,</div><br><div>Anil<br><br><div>=
Please can members of the WG express whether they are happy with these chan=
ges, or concerned.</div><br><div>Best regards,</div><div>Alan</div><br><br>=
_______________________________________________<br>multipathtcp mailing lis=
t<br><a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noopener%20=
noreferrer nofollow noopener noreferrer" target=3D"_blank">multipathtcp@iet=
f.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp"=
 rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferrer" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a></div><=
/div></div></div></div></div></div></div></div></div><br></div></div></div>
<br>
<br>_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noopener%20noref=
errer nofollow noopener noreferrer" target=3D"_blank">multipathtcp@ietf.org=
</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"noref=
errer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
</blockquote></div></div></div></div></div></div><br></div></div>
<br>
<br></div></blockquote></div></div></div></div>

--000000000000ea92f9059dbb2193--


From nobody Tue Feb  4 04:12:30 2020
Return-Path: <alan.ford@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 396D21200A4 for <multipathtcp@ietfa.amsl.com>; Tue,  4 Feb 2020 04:12:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level: 
X-Spam-Status: No, score=-0.997 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 8ecorLi_1sal for <multipathtcp@ietfa.amsl.com>; Tue,  4 Feb 2020 04:12:23 -0800 (PST)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (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 56F12120020 for <multipathtcp@ietf.org>; Tue,  4 Feb 2020 04:12:22 -0800 (PST)
Received: by mail-wm1-x32f.google.com with SMTP id q9so3020579wmj.5 for <multipathtcp@ietf.org>; Tue, 04 Feb 2020 04:12:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=lhIKVSw9DTFM/OsWIoa8AWIZMlsuMv/G0fOEKmWT0PQ=; b=SRSg3PQPcxy8iI9L+FoR+qdqDDPdslTwvHLa61+72kfW3l87azkSSKqops07aFYq6N 5RI2hrwDiyouQXtakvvPydXwhbTyEDRLdp8iVqBf0UOcdNffkxowf/S/uaUY5hxRkRXC OxxUBun2rWXHAj8l0G8U7jYPQJT0vBYZgHhbS7yDxoCZHtEaRDQ0YImpHw2qAai2cYew whnoMiO9ePUAD3haVJhjtP499E2FvpA7waUtSBu1P9yoM7RKRSxYCVheJKGiaFt5NuYc XGBv677FqmAeuOwCghEEhy9/ca/gt7iaL0eM8gO6WczOegfxVH41oBby8ka37YwuwcTO HKKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=lhIKVSw9DTFM/OsWIoa8AWIZMlsuMv/G0fOEKmWT0PQ=; b=dO/WFsEbjq9rEaam0KATJ0CAGaD8wI6zuyC0lS/2uEsR9+FQhoZ9OXd5hXXx8jWkPi o6dHIe07jFGEN5g58uhIg50gXktrXLe3h+gVs89g1PT37PGssReLjiQkOWsN8Cn652j7 ExYIHI6YQ8szEwZJOYJ+0bTi9agknTCC1V+7HnTAqfe2hW0Ybf5NkreiiWjO8C7wM7Wh CGhXEg8eYK/AI+oInbQ+etZ3Pu8aElui+rN+RzFf9lLP8/IwWYByZdKJC3ZcxxWWNvCB km3pwYdfI2BVkLv1iQFG+jYqmI9SKECl3ecM8V0gb5G+CfKC51B2i7WbJ+s+KH/uwfyk 69aA==
X-Gm-Message-State: APjAAAWOyWNWzP0wk12Q6WT5yy9Ehv9Vxm6NDPS3kT6j9ArSL44OeV47 SKuOZHe8OhIJ9I1B7smdgD3U2FbeTMk=
X-Google-Smtp-Source: APXvYqxBqseq3U1QL3QKEi6U0P/xKYrQ9UcuNzq/+aitiLFP2m0Fz7Rjm9chHJSt/lQnMlK9AiOq6A==
X-Received: by 2002:a1c:a4c3:: with SMTP id n186mr5635982wme.25.1580818339942;  Tue, 04 Feb 2020 04:12:19 -0800 (PST)
Received: from alan-mbp.lan (107.35.115.87.dyn.plus.net. [87.115.35.107]) by smtp.gmail.com with ESMTPSA id e6sm3463360wme.3.2020.02.04.04.12.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Feb 2020 04:12:19 -0800 (PST)
From: Alan Ford <alan.ford@gmail.com>
Message-Id: <83C89953-EDAE-4B0C-B73B-9E88BAF3C927@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B8573F87-69E1-46BF-B86B-A508FF8B28A9"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 4 Feb 2020 12:12:17 +0000
In-Reply-To: <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com>
Cc: V Anil Kumar <anil@csir4pi.in>, multipathtcp <multipathtcp@ietf.org>
To: Yoshifumi Nishida <nsd.ietf@gmail.com>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/5tUVdxrviDmqFs6V_yUWyWIBrmw>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2020 12:12:28 -0000

--Apple-Mail=_B8573F87-69E1-46BF-B86B-A508FF8B28A9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Yoshi,

The proposed new text enforces a mapping to be sent on a packet whose =
subflow sequence number is included within the mapping provided. This =
does not directly contradict with the MAY case. Indeed this scenario =
could easily happen if there is a 20 byte packet followed by a 10 byte =
packet. The first 10 bytes of the first packet are covered by the =
mapping on packet 1, then the remaining 10 bytes and the following 10 =
bytes are covered by the mapping on packet 2. That would be valid.

To re-iterate, the primary purpose of this proposed text is to stop =
people sending mappings before they are needed.

Best regards,
Alan

> On 4 Feb 2020, at 07:38, Yoshifumi Nishida <nsd.ietf@gmail.com> wrote:
>=20
> Hi Anil,
>=20
> Thanks for pointing it out. I overlooked this one.
> This looks an interesting point.
>=20
> It seems to me that whether RST is happen or not depends on the size =
of receive window according to the text.
> If the receive window size is big enough to accommodate segment 1 and =
segment 3, the text "Implementations MAY hold onto such unmapped data =
for a short while in the expectation that a mapping will arrive shortly. =
" can be applied to the segment 1. As a result, the segment 1 won't be =
discarded.=20
> However, this might be contradict with the new texts Alan proposed? =
Or, am I missing something?
>=20
> Thanks,
> --
> Yoshi
>=20
>=20
>=20
> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Yoshi,
>=20
> Thanks for this point. In fact, I had initially not thought of a =
scenario, where the map is being delivered through a retransmitted data =
packet while its first transmission did not include the map. Now I am =
just seeing the document (RFC 6824-bis) in this context.
>=20
> My understanding is that in scenarios like what I described in my =
previous mail, RST is likely to happen whether we explicitly state so or =
not. Please see the paragraph containing the below text in RFC 6824-bis. =
=20
>=20
> "If a mapping for that subflow-level sequence space does not arrive =
within a receive window of data, that subflow SHOULD be treated as =
broken, closed with a RST, and any unmapped data silently discarded."
>=20
> if we assume that the map is included while retransmitting the data =
(even though the first transmission did not contain the map for some =
reasons),  we could argue that RST could be avoided provided that the =
retransmission is triggered within a receive window of data. But the =
question here would be how and when will the retransmission take place. =
In this case, the subflow may not initiate the retransmission of data by =
its own (i.e., no retransmission due to three duplicate ACKs or RTO =
expiry at subflow level) as there is no segment loss at subflow level =
sequence space. So there could be a high possibility of RST happening =
even before the map delivery through retransmission.=20
>=20
> With regards,=20
>=20
> Anil
> =20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, =
"multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> Sent: Saturday, February 1, 2020 3:39:51 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
>=20
> Hi Anil,
>=20
> I have a question about your proposed text.
> I am actually wondering if we really want to terminate connection =
here.=20
>=20
> The packets without proper mappings will be treated as invalid and =
will be discarded.=20
> If an implementation failed to attach proper mapping for some reasons =
(e.g. option space), it might be able to attach the proper one when it =
retransmits the packets. This also looks ok to me.
>=20
> I don't have strong preference for this. But, do we have a reason to =
terminate connection?
>=20
> Thanks,
> --
> Yoshi
>=20
> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi,
>=20
> I have some points related to the  modifications (Change 2) being =
proposed on data sequence map. Please see them inline. Though I am =
putting forward the below points, if the consensus is in favour of the =
proposed change for reducing implementation complexity, I am also OK =
with that as well.=20
>=20
> From: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> To: multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> Sent: Thursday, January 2, 2020 4:21:32 AM
> Subject: [multipathtcp] RFC6824bis edits based on implementation =
feedback
>=20
> Hi all,
> We=E2=80=99d love to get this to a state of completion as soon as =
possible, and to this end I am starting a new thread on this topic. In =
discussion with the chairs, it is possible to make the desired changes =
in AUTH48 as long as there is WG consensus. The discussion so far has =
been fairly limited in terms of participation.
>=20
> I would ask the chairs please if it was possible to specify a time =
bound for this discussion and a default conclusion.
>=20
> Regarding the changes, in summary, there are two areas where changes =
have been requested by the implementation community. As we are the IETF =
we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so =
ease of implementing standards-compliant code is strongly desirable. =
However, we do not wish to reduce functionality agreed by the IETF =
community if it is considered a required feature by the community.
>=20
>=20
> Change 1
>=20
> Change the sentence reading:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).=20
>=20
> To:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data =
Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for the =
MP_CAPABLE (which is the first octet of the data sequence space).
>=20
> What this means:
>=20
> The current text is concerned only with ensuring a path is MPTCP =
capable, and so only cares that DSS option occurs on a data packet. =
However, the MP_CAPABLE option is defined to occupy the first octet of =
data sequence space and thus, if analogous to TCP, must be acknowledged. =
>=46rom an implementation point of view it would make sense not to have =
this hanging around forever and instead define it is acknowledged at the =
connection level as soon as received. This change ensures the first data =
packet also DATA_ACKs this MP_CAPABLE octet.
>=20
>=20
> Change 2
>=20
> Change the sentence reading:
>=20
>    A Data Sequence Mapping does not need to be included in every MPTCP =
packet, as long as the subflow sequence space in that packet is covered =
by a mapping known at the receiver.
>=20
> To:
>=20
>    The mapping provided by a Data Sequence Mapping MUST apply to some =
or all of the subflow sequence space in the TCP segment which carries =
the option. It does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.
>=20
> What this means:
>=20
> The current text does not place any restrictions on where a mapping =
could appear. In theory a sender could define a thousand different =
mappings up front, send them all, and expect a receiver to store this =
and reassemble data according to these mappings as it arrives. Indeed, =
this was never explicitly disallowed since it =E2=80=9Cmight have been =
useful=E2=80=9D. The implementation community, however, has expressed =
concerns over the difficulty of implementing this open-endedly. How many =
mappings is it reasonable to store? Is there a DoS risk here? Instead, =
it has been requested that thee specification restricts the placement of =
the DSS option to being within the subflow sequence space to which it =
applies.
>=20
> Below are my comments on this. I had shared some of these points in a =
previous thread that you had initiated in the same context.=20
>=20
> Transmitting large number of non-contiguous data sequence maps could =
be a misbehaviour (map-flooding), though it is not clear whether this =
can go to the extent of causing a potential DoS to the data receiver. So =
some sort of restriction on this could be useful.  One approach could be =
to insist that the data sender should ensure that the map being =
transmitted is for in-window data, as per the receiver advertised =
window. A receiver should anyhow be willing to store the maps for =
in-window data to deal with packet loss. For example, when a window of =
data segments (say 1 to 64) is transmitted, each carrying its =
corresponding map, and segment-1 is lost, the maps for the remaining 63 =
need to be stored till the lost segment is retransmitted. Of course, in =
this case the maps will be stored at the receiver side along with their =
corresponding data. But the need to store multiple maps for in-window =
data would still be there.
>=20
> The problem with the proposed change (restriction) is that a data =
sender may find it difficult, in case a need arise to slightly delay the =
map delivery by few segments, i.e., sending some data first without map, =
and then send the corresponding map in a later segment, as shown below:
>=20
> subflow-1:      segment-1                   segment-3                  =
  segment-4                       segment-7
>                       bytes:1-100                 bytes:201-300        =
      bytes:301-400                 bytes:601-700
>                       no map                        map for 1-100      =
        map for 201-400             map for 601-700
>=20
>=20
>=20
> subflow-2:       segment-2                  segment-5                  =
   segment-6                       segment-8
>                        bytes: 101-200           bytes:401-500          =
     bytes: 501-600                bytes:701-800  =20
>                        map for 101-200       map for 401-600           =
 no map                            map for 701-800
>=20
>=20
> In the above case, segment-1 goes without map and its map is included =
later in segment-3, the next data segment in the same subflow. Further,  =
in the above scheduling pattern, the map in segment-3 cannot cover the  =
data in segment-1 and segment-3, as some  data in between (segment-2) is =
transmitted through another subflow.  With the proposed change, the map =
in segment-3 will become invalid and this will eventually break =
subflow-1, though this could be a corner case.
>=20
> The question at this stage is why would segment-1 be transmitted =
without its map. In the case of bidirectional data transfer, there could =
be a need to pack both timestamp and SACK  options in a data segment, =
i.e., piggybacking of  SACK with data. If we consider that timestamp =
takes 12 bytes and SACK, even with single block,  takes another 10 =
bytes, the remaining 18 bytes option space is not adequate to carry data =
sequence signal with map, especially when DSN is 64 bit long. So the =
delivery of either of the two (SACK or map) would be delayed.
>=20
> As far as I understand, RFC 2018 (TCP Selective Acknowledgement =
Options) implies that SACK should not be delayed. It states "If sent at =
all, SACK options SHOULD be included in all ACKs which do not ACK the =
highest sequence number in the data receiver's queue". It also says "If =
data receiver generates SACK options under any circumstance, it SHOULD =
generate them under all permitted circumstances".   So, as part of =
meeting the RFC 2018 requirements, if the combination of SACK and =
timestamp is given preference over DSS, data segments could be =
transmitted without their map.=20
>=20
> Another case of delaying map could arise if the data sender prefers to =
send ADD_ADDR option, instead of map, in a data segment. It is nice that =
ADD_ADDR option can be delivered reliably in a pure ACK, but I think =
this is not the case with DSS at present.
>=20
> If we adopt the proposed change, I think it might also be helpful to =
spell out how the receiver is supposed to behave, if it gets maps not =
meeting the MUST condition in the proposed change.  For example =
termination of the subflow with MP_TCPRST option (section 3.6 in RFC =
6824-bis) with appropriate reason code and T flag value to intimate the =
data sender the cause for subflow termination. =20
>         =20
> With regards,
>=20
> Anil
>=20
> Please can members of the WG express whether they are happy with these =
changes, or concerned.
>=20
> Best regards,
> Alan
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
>=20
>=20
>=20


--Apple-Mail=_B8573F87-69E1-46BF-B86B-A508FF8B28A9
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; line-break: after-white-space;" class=3D"">Hi =
Yoshi,<div class=3D""><br class=3D""></div><div class=3D"">The proposed =
new text enforces a mapping to be sent on a packet whose subflow =
sequence number is included within the mapping provided. This does not =
directly contradict with the MAY case. Indeed this scenario could easily =
happen if there is a 20 byte packet followed by a 10 byte packet. The =
first 10 bytes of the first packet are covered by the mapping on packet =
1, then the remaining 10 bytes and the following 10 bytes are covered by =
the mapping on packet 2. That would be valid.</div><div class=3D""><br =
class=3D""></div><div class=3D"">To re-iterate, the primary purpose of =
this proposed text is to stop people sending mappings before they are =
needed.</div><div class=3D""><br class=3D""></div><div class=3D"">Best =
regards,</div><div class=3D"">Alan</div><div class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 4 Feb =
2020, at 07:38, Yoshifumi Nishida &lt;<a =
href=3D"mailto:nsd.ietf@gmail.com" class=3D"">nsd.ietf@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D"">Hi Anil,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks for pointing it out. I =
overlooked this one.</div><div class=3D"">This looks an interesting =
point.<br class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D"">It seems to me that whether RST is happen or not depends on =
the size of receive window according to the text.<br class=3D""></div><div=
 class=3D"">If the receive window size is big enough to =
accommodate&nbsp;segment 1 and segment 3, the text "<span =
style=3D"font-size: 13.3333px;" class=3D"">Implementations MAY hold onto =
such unmapped data for a short while in&nbsp;</span><span =
style=3D"font-size: 13.3333px;" class=3D"">the expectation that a =
mapping will arrive shortly. "&nbsp;</span>can be applied to the segment =
1. As a result, the segment 1 won't be discarded.&nbsp;</div><div =
class=3D"">However, this might be contradict with the new texts Alan =
proposed? Or, am I missing something?</div><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks,</div><div class=3D"">--</div><div=
 class=3D"">Yoshi</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Feb =
2, 2020 at 8:42 AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" =
target=3D"_blank" class=3D"">anil@csir4pi.in</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div class=3D""><div class=3D""><div =
class=3D""><div style=3D"font-family:arial,helvetica,sans-serif" =
class=3D""><div class=3D"">Hi Yoshi,</div><br class=3D""><div =
class=3D"">Thanks for this point. In fact, I had initially not thought =
of a scenario, where the map is being delivered through a retransmitted =
data packet while its first transmission did not include the map. Now I =
am just seeing the document (RFC 6824-bis) in this context.</div><br =
class=3D""><div class=3D"">My understanding is that in scenarios like =
what I described in my previous mail, RST is likely to happen whether we =
explicitly state so or not. Please see the paragraph containing the =
below text in RFC 6824-bis. &nbsp;</div><br class=3D""><div class=3D"">"If=
 a mapping for that subflow-level sequence space does not arrive within =
a receive window of data, that subflow SHOULD be treated as broken, =
closed with a RST, and any unmapped data silently discarded."</div><br =
class=3D""><div class=3D"">if we assume that the map is included while =
retransmitting the data (even though the first transmission did not =
contain the map for some reasons), &nbsp;we could argue that RST could =
be avoided provided that the retransmission is triggered within a =
receive window of data. But the question here would be how and when will =
the retransmission take place. In this case, the subflow may not =
initiate the retransmission of data by its own (i.e., no retransmission =
due to three duplicate ACKs or RTO expiry at subflow level) as there is =
no segment loss at subflow level sequence space. So there could be a =
high possibility of RST happening even before the map delivery through =
retransmission.&nbsp;</div><br class=3D""><div class=3D"">With =
regards,&nbsp;</div><br class=3D""><div class=3D"">Anil</div><div =
class=3D"">&nbsp;</div><hr =
id=3D"gmail-m_218086596951724501gmail-m_2982267033577902985zwchr" =
class=3D""><div class=3D""><b class=3D"">From: </b>"Yoshifumi Nishida" =
&lt;<a href=3D"mailto:nsd.ietf@gmail.com" target=3D"_blank" =
class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: =
</b>"V Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" =
target=3D"_blank" class=3D"">anil@csir4pi.in</a>&gt;<br class=3D""><b =
class=3D"">Cc: </b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
target=3D"_blank" class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" =
&lt;<a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b class=3D"">Sent:=
 </b>Saturday, February 1, 2020 3:39:51 AM<br class=3D""><b =
class=3D"">Subject: </b>Re: [multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></div><br class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"">Hi Anil,</div><br class=3D""><div =
class=3D"">I have a question about your proposed text.</div><div =
class=3D""><div class=3D"">I am actually wondering if we really want to =
terminate connection here.&nbsp;</div></div><br class=3D""><div =
class=3D"">The packets without proper mappings will be treated as =
invalid and will be discarded.&nbsp;</div><div class=3D"">If an =
implementation failed to attach proper mapping for some reasons (e.g. =
option space), it might be able to attach the proper one when it =
retransmits the packets. This also looks ok to me.</div><br =
class=3D""><div class=3D"">I don't have strong preference for this. But, =
do we have a reason to terminate connection?</div><br class=3D""><div =
class=3D"">Thanks,</div><div class=3D"">--<br class=3D""></div><div =
class=3D"">Yoshi</div><br class=3D""><div class=3D""><div dir=3D"ltr" =
class=3D"">On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div class=3D""><div =
class=3D""><div class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
class=3D""><span style=3D"font-size:12pt;line-height:1.3" =
class=3D"">Hi,</span><br class=3D""></div><div class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><br =
class=3D""><div class=3D"">I have some points related to the =
&nbsp;modifications (Change 2) being proposed on data sequence map. =
Please see them inline.&nbsp;<span style=3D"font-family: arial, =
helvetica, sans-serif; font-size: 16px; font-style: normal; font-weight: =
400; letter-spacing: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, =
255); float: none; display: inline;" class=3D"">Though I am putting =
forward the below points, if the consensus is in favour of the proposed =
change for reducing implementation complexity, I am also OK with that as =
well.&nbsp;</span><br class=3D""></div><br class=3D""><hr =
id=3D"gmail-m_218086596951724501gmail-m_2982267033577902985gmail-m_7687184=
382299596774zwchr" class=3D""><div class=3D""><b class=3D"">From: =
</b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" class=3D"">alan.ford@gmail.com</a>&gt;<br class=3D""><b =
class=3D"">To: </b><a href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" class=3D"">multipathtcp@ietf.org</a><br class=3D""><b =
class=3D"">Sent: </b>Thursday, January 2, 2020 4:21:32 AM<br class=3D""><b=
 class=3D"">Subject: </b>[multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></div><br class=3D""><div =
class=3D"">Hi all,<br class=3D""><div class=3D"">We=E2=80=99d love to =
get this to a state of completion as soon as possible, and to this end I =
am starting a new thread on this topic. In discussion with the chairs, =
it <i class=3D"">is </i>possible to make the desired changes in AUTH48 =
as long as there is WG consensus. The discussion so far has been fairly =
limited in terms of participation.</div><br class=3D""><div class=3D"">I =
would ask the chairs please if it was possible to specify a time bound =
for this discussion and a default conclusion.</div><br class=3D""><div =
class=3D"">Regarding the changes, in summary, there are two areas where =
changes have been requested by the implementation community. As we are =
the IETF we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D =
and so ease of implementing standards-compliant code is strongly =
desirable. However, we do not wish to reduce functionality agreed by the =
IETF community if it is considered a required feature by the =
community.</div><br class=3D""><br class=3D""><div class=3D""><b =
class=3D"">Change 1</b></div><div class=3D""><b class=3D""><br =
class=3D""></b></div><div class=3D"">Change the sentence reading:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B has data to =
send first, then the reliable delivery of the ACK + MP_CAPABLE can be =
inferred by the receipt of this data with an MPTCP Data Sequence Signal =
(DSS) option (Section 3.3).&nbsp;<br class=3D""></i><br class=3D"">To:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B has data to =
send first, then the reliable delivery of the ACK + MP_CAPABLE is =
ensured by the receipt of this data with an MPTCP Data Sequence Signal =
(DSS) option (Section 3.3) containing a DATA_ACK for the MP_CAPABLE =
(which is the first octet of the data sequence&nbsp;space).<br =
class=3D""></i><br class=3D""></div><div class=3D"">What this =
means:</div><br class=3D""><div class=3D"">The current text is concerned =
only with ensuring a path is MPTCP capable, and so only cares that DSS =
option occurs on a data packet. However, the MP_CAPABLE option is =
defined to occupy the first octet of data sequence space and thus, if =
analogous to TCP, must be acknowledged. &gt;=46rom an implementation =
point of view it would make sense not to have this hanging around =
forever and instead define it is acknowledged at the connection level as =
soon as received. This change ensures the first data packet also =
DATA_ACKs this MP_CAPABLE octet.</div><br class=3D""><br class=3D""><div =
class=3D""><b class=3D"">Change 2</b></div><div class=3D""><b =
class=3D""><br class=3D""></b></div><div class=3D"">Change the sentence =
reading:<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;A Data =
Sequence Mapping does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.</i><br class=3D""><br class=3D"">To:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;The mapping =
provided by a Data Sequence Mapping MUST apply to some or all of the =
subflow sequence space in the TCP segment which carries the option. It =
does not need to be included in every MPTCP packet, as long as the =
subflow sequence space in that packet is covered by a mapping known at =
the receiver.<br class=3D""></i><br class=3D"">What this means:</div><br =
class=3D""><div class=3D"">The current text does not place any =
restrictions on where a mapping could appear. In theory a sender could =
define a thousand different mappings up front, send them all, and expect =
a receiver to store this and reassemble data according to these mappings =
as it arrives. Indeed, this was never explicitly disallowed since it =
=E2=80=9Cmight have been useful=E2=80=9D. The implementation community, =
however, has expressed concerns over the difficulty of implementing this =
open-endedly. How many mappings is it reasonable to store? Is there a =
DoS risk here? Instead, it has been requested that thee specification =
restricts the placement of the DSS option to being within the subflow =
sequence space to which it applies.</div><br class=3D""><div =
class=3D"">Below are my comments on this. I had shared some of these =
points in a previous thread that you had initiated in the same =
context.&nbsp;</div><br class=3D""><div class=3D"">Transmitting large =
number of non-contiguous data sequence maps could be a misbehaviour =
(map-flooding), though it is not clear whether this can go to the extent =
of causing a potential DoS to the data receiver. So some sort of =
restriction on this could be useful.&nbsp; One approach could be to =
insist that the data sender should ensure that the map being transmitted =
is for in-window data, as per the receiver advertised window. A receiver =
should anyhow be willing to store the maps for in-window data to deal =
with packet loss. For example, when a window of data segments (say 1 to =
64) is transmitted, each carrying its corresponding map, and segment-1 =
is lost, the maps for the remaining 63 need to be stored till the lost =
segment is retransmitted. Of course, in this case the maps will be =
stored at the receiver side along with their corresponding data. But the =
need to store multiple maps for in-window data would still be =
there.</div><br class=3D""><div class=3D""><span style=3D"font-family: =
arial, helvetica, sans-serif; font-size: 16px; font-style: normal; =
font-weight: normal; letter-spacing: normal; line-height: 20.8px; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; float: none; background-color: rgb(255, 255, 255); =
display: inline;" class=3D"">The problem with the proposed change =
(restriction) is that a data sender may find it difficult, in case a =
need arise to slightly delay the map delivery by few segments, i.e., =
sending some data first without map, and then send the corresponding map =
in a later segment, as shown below:</span><br class=3D""></div><br =
class=3D""><div class=3D""><div style=3D"font-family: &quot;segoe =
ui&quot;, &quot;lucida sans&quot;, sans-serif; font-size: 14.16px; =
font-style: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; margin: 0px; background-color: =
rgb(255, 255, 255);" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt" class=3D"">subflow-1:&nbsp; &nbsp; &nbsp; =
segment-1&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; segment-3&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; segment-4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-7</span></div><div =
style=3D"font-family: &quot;segoe ui&quot;, &quot;lucida sans&quot;, =
sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; margin: =
0px; background-color: rgb(255, 255, 255);" class=3D""><span =
lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;bytes:1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; bytes:201-300 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;bytes:301-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; bytes:601-700</span></div><div style=3D"font-family: =
&quot;segoe ui&quot;, &quot;lucida sans&quot;, sans-serif; font-size: =
14.16px; font-style: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; margin: 0px; background-color: =
rgb(255, 255, 255);" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;no map &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map =
for 1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for =
201-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; map for =
601-700</span></div><div style=3D"font-family: &quot;segoe ui&quot;, =
&quot;lucida sans&quot;, sans-serif; font-size: 14.16px; font-style: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: rgb(255, 255, 255);" =
class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" class=3D""><br =
class=3D""></span></div><div style=3D"font-family: &quot;segoe ui&quot;, =
&quot;lucida sans&quot;, sans-serif; font-size: 14.16px; font-style: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: rgb(255, 255, 255);" =
class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" class=3D""><br =
class=3D""></span></div><div style=3D"font-family: &quot;segoe ui&quot;, =
&quot;lucida sans&quot;, sans-serif; font-size: 14.16px; font-style: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: rgb(255, 255, 255);" =
class=3D""><br class=3D""></div><div style=3D"font-family: &quot;segoe =
ui&quot;, &quot;lucida sans&quot;, sans-serif; font-size: 14.16px; =
font-style: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; margin: 0px; background-color: =
rgb(255, 255, 255);" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt" class=3D"">subflow-2:&nbsp; &nbsp; &nbsp; =
&nbsp;segment-2&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; segment-5 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; segment-6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; segment-8</span></div><div =
style=3D"font-family: &quot;segoe ui&quot;, &quot;lucida sans&quot;, =
sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; margin: =
0px; background-color: rgb(255, 255, 255);" class=3D""><span =
lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bytes: 101-200 &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; bytes:401-500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bytes: 501-600 &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;bytes:701-800&nbsp;&nbsp;&nbsp;</span></div><div =
style=3D"font-family: &quot;segoe ui&quot;, &quot;lucida sans&quot;, =
sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; margin: =
0px; background-color: rgb(255, 255, 255);" class=3D""><span =
lang=3D"EN-US" style=3D"font-size:10pt" class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for =
101-200 &nbsp; &nbsp; &nbsp; map for 401-600 &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;no map &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for =
701-800</span></div><div style=3D"font-family: &quot;segoe ui&quot;, =
&quot;lucida sans&quot;, sans-serif; font-size: 14.16px; font-style: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: rgb(255, 255, 255);" =
class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D""></span><br class=3D""></div><div style=3D"font-family: =
&quot;segoe ui&quot;, &quot;lucida sans&quot;, sans-serif; font-size: =
14.16px; font-style: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; margin: 0px; background-color: =
rgb(255, 255, 255);" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:10pt" class=3D""></span><br class=3D""></div>In the =
above case, segment-1 goes without map and its map is included later in =
segment-3, the next data segment in the same subflow. Further, &nbsp;in =
the above scheduling pattern, the map in segment-3 cannot cover the =
&nbsp;data in segment-1 and segment-3, as some &nbsp;data in between =
(segment-2) is transmitted through another subflow.&nbsp; With the =
proposed change, the map in segment-3 will become invalid and this will =
eventually break subflow-1, though this could be a corner case.</div><br =
class=3D""><div class=3D"">The question at this stage is why would =
segment-1 be transmitted without its map. In the case of bidirectional =
data transfer, there could be a need to pack both timestamp and SACK =
&nbsp;options in a data segment, i.e., piggybacking of &nbsp;SACK with =
data. If we consider that timestamp takes 12 bytes and SACK, even with =
single block, &nbsp;takes another 10 bytes, the remaining 18 bytes =
option space is not adequate to carry data sequence signal with map, =
especially when DSN is 64 bit long. So the delivery of either of the two =
(SACK or map) would be delayed.</div><br class=3D""><div class=3D"">As =
far as I understand, RFC 2018 (TCP Selective Acknowledgement Options) =
implies that SACK should not be delayed. It states "If sent at all, SACK =
options SHOULD be included in all ACKs which do not ACK the highest =
sequence number in the data receiver's queue". It also says "If data =
receiver generates SACK options under any circumstance, it SHOULD =
generate them under all permitted circumstances". &nbsp; So, as part of =
meeting the RFC 2018 requirements, if the combination of SACK and =
timestamp is given preference over DSS, data segments could be =
transmitted without their map.&nbsp;</div><br class=3D""><div =
class=3D"">Another case of delaying map could arise if the data sender =
prefers to send ADD_ADDR option, instead of map, in a data segment. It =
is nice that ADD_ADDR option can be delivered reliably in a pure ACK, =
but I think this is not the case with DSS at present.</div><br =
class=3D""><div class=3D"">If we adopt the proposed change, I think it =
might also be helpful to spell out how the receiver is supposed to =
behave, if it gets maps not meeting the MUST condition in the proposed =
change.&nbsp; For example termination of the subflow with MP_TCPRST =
option (section 3.6 in RFC 6824-bis) with appropriate reason code and T =
flag value to intimate the data sender the cause for subflow =
termination.&nbsp;&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;</div></div><div class=3D"">With regards,</div><br =
class=3D""><div class=3D"">Anil<br class=3D""><br class=3D""><div =
class=3D"">Please can members of the WG express whether they are happy =
with these changes, or concerned.</div><br class=3D""><div class=3D"">Best=
 regards,</div><div class=3D"">Alan</div><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a></div></d=
iv></div></div></div></div></div></div></div></div><br =
class=3D""></div></div></div>
<br class=3D"">
<br class=3D"">_______________________________________________<br =
class=3D"">
multipathtcp mailing list<br class=3D"">
<a href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" class=3D"">multipathtcp@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
rel=3D"noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener =
noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br =
class=3D"">
</blockquote></div></div></div></div></div></div><br =
class=3D""></div></div>
<br class=3D"">
<br class=3D""></div></blockquote></div></div></div></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_B8573F87-69E1-46BF-B86B-A508FF8B28A9--


From nobody Tue Feb  4 05:28:52 2020
Return-Path: <matthieu.baerts@tessares.net>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B861200F5 for <multipathtcp@ietfa.amsl.com>; Tue,  4 Feb 2020 05:28:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tessares-net.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 QpwquDylZWK0 for <multipathtcp@ietfa.amsl.com>; Tue,  4 Feb 2020 05:28:48 -0800 (PST)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 956D1120020 for <multipathtcp@ietf.org>; Tue,  4 Feb 2020 05:28:47 -0800 (PST)
Received: by mail-wr1-x42e.google.com with SMTP id k11so23008373wrd.9 for <multipathtcp@ietf.org>; Tue, 04 Feb 2020 05:28:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tessares-net.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=NSZKfXRjeGx3J8zsNYfuG/GhkGnaEDe0NV92aKI50Nk=; b=j2PkukH5L6M7/PgJEp4AHSgw9EfJ6lR3OiEgB1+PEq+boPEKTPx92+UECeOarn/ipL 54lDubFbAr9axkBKwHf+5R8Dy88X6aCjMUh5ceDej1Wt/G5z9nsWdZusy9qvaNEaJt0U koMpsJG0Vjdf6oJVIc6lcH3u6OKwGRv03sTpQbH/Xq0d5ogLjgYiZAPGDRRce8ID6XTT cWQFlsnVTCBXCEsrOZHWu9R/j8DlvXS8SrDxcRxqGhDGKj0c+S/PIcJsAm7fIenafDzq NmKoVnJ3wRda1CxHRcC2gCXfVlVFjnVfIItT33/NF4FdQCY8wA5G/xoiWFBMCzGe6IwD OstQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=NSZKfXRjeGx3J8zsNYfuG/GhkGnaEDe0NV92aKI50Nk=; b=Riy3aErAL3oB/z2nmdHFo+s8uiDEy0GR5YLuQG3JIrfiRs92L/nUxPrIk2/rPHeehZ znHgSrYV1ilZntTuYZWFUZObXfxDBqQ8taQJI6sm60DRrn0R+bmH5QhxpKpjq4qmwo4P jYtNgkVTJcGhtgIWrbLdutNZxikqkpvlxFpmLgWj4Tfj0YeASsAMZ9rUMOVf0TfxcWPj GIr8aY78Hp3aRs3Hvh9oqpDDJesXQZ54h1oPhhB1t4rZUAu+9gvTVrbE5M2m+ELSZlL/ SNMvvoGX+hfrWTs7xMMTqBRAPnhA4gvVpM/7LdGQ/kJy034haKWLO56M6QnAsYsG7P0g B4PQ==
X-Gm-Message-State: APjAAAXuFjg74IF7HIgTYQscGthEcKevowUQcEydA2wmdWf2wAAYLu9/ 6Vp7NKQ17Fz8m6wzudrGgxq44mQaxSnizw==
X-Google-Smtp-Source: APXvYqytajkokx/reU49w0sLajDwGNG2CaXu4XkxVlRC65DFYpDe/JZpFp2P6r9PZNsSEN2wuFP6ig==
X-Received: by 2002:a5d:550f:: with SMTP id b15mr21922381wrv.196.1580822925290;  Tue, 04 Feb 2020 05:28:45 -0800 (PST)
Received: from tsr-lap-08.nix.tessares.net (hag0-main.tessares.net. [87.98.252.165]) by smtp.gmail.com with ESMTPSA id 5sm27404483wrc.75.2020.02.04.05.28.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Feb 2020 05:28:44 -0800 (PST)
To: Alan Ford <alan.ford@gmail.com>, Yoshifumi Nishida <nsd.ietf@gmail.com>
Cc: multipathtcp <multipathtcp@ietf.org>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <83C89953-EDAE-4B0C-B73B-9E88BAF3C927@gmail.com>
From: Matthieu Baerts <matthieu.baerts@tessares.net>
Message-ID: <ec681f60-23f9-c934-b2fc-306584fec645@tessares.net>
Date: Tue, 4 Feb 2020 14:28:44 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <83C89953-EDAE-4B0C-B73B-9E88BAF3C927@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/APOYs2pwx7W3zRIh8DrTqgkyeFs>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2020 13:28:51 -0000

Hi all,

First, thank you all for having contributed all these years to make 
clear MPTCP RFCs.

I'm sorry to interrupt the discussions with my message but because it 
seems there are still some opened questions related to these changes, I 
would like to express my view from the implementer side.

As a maintainer of both the MPTCP Linux out-of-tree implementation and 
the new MPTCP Linux upstream one, I fully endorse both changes.

The first one avoids confusions while the second one avoids senders to 
generate segments that are not supported by the two MPTCP Linux 
implementations and certainly by most/all existing ones. Accepting such 
Data Segment Mappings are not supported and will probably never be 
because it is complex, middleboxes don't seem to modify packets to have 
a situation like that and it can be a source of security issues. 
Avoiding senders to create such mappings would avoid issues if most 
network stacks don't implement this specific support for technical reasons.

Thank you Alan for taking care of this!

Cheers,
Matt

On 04/02/2020 13:12, Alan Ford wrote:
> Hi Yoshi,
> 
> The proposed new text enforces a mapping to be sent on a packet whose 
> subflow sequence number is included within the mapping provided. This 
> does not directly contradict with the MAY case. Indeed this scenario 
> could easily happen if there is a 20 byte packet followed by a 10 byte 
> packet. The first 10 bytes of the first packet are covered by the 
> mapping on packet 1, then the remaining 10 bytes and the following 10 
> bytes are covered by the mapping on packet 2. That would be valid.
> 
> To re-iterate, the primary purpose of this proposed text is to stop 
> people sending mappings before they are needed.
> 
> Best regards,
> Alan
> 
>> On 4 Feb 2020, at 07:38, Yoshifumi Nishida <nsd.ietf@gmail.com 
>> <mailto:nsd.ietf@gmail.com>> wrote:
>>
>> Hi Anil,
>>
>> Thanks for pointing it out. I overlooked this one.
>> This looks an interesting point.
>>
>> It seems to me that whether RST is happen or not depends on the size 
>> of receive window according to the text.
>> If the receive window size is big enough to accommodate segment 1 and 
>> segment 3, the text "Implementations MAY hold onto such unmapped data 
>> for a short while in the expectation that a mapping will arrive 
>> shortly. " can be applied to the segment 1. As a result, the segment 1 
>> won't be discarded.
>> However, this might be contradict with the new texts Alan proposed? 
>> Or, am I missing something?
>>
>> Thanks,
>> --
>> Yoshi
>>
>>
>>
>> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in 
>> <mailto:anil@csir4pi.in>> wrote:
>>
>>     Hi Yoshi,
>>
>>     Thanks for this point. In fact, I had initially not thought of a
>>     scenario, where the map is being delivered through a retransmitted
>>     data packet while its first transmission did not include the map.
>>     Now I am just seeing the document (RFC 6824-bis) in this context.
>>
>>     My understanding is that in scenarios like what I described in my
>>     previous mail, RST is likely to happen whether we explicitly state
>>     so or not. Please see the paragraph containing the below text in
>>     RFC 6824-bis.
>>
>>     "If a mapping for that subflow-level sequence space does not
>>     arrive within a receive window of data, that subflow SHOULD be
>>     treated as broken, closed with a RST, and any unmapped data
>>     silently discarded."
>>
>>     if we assume that the map is included while retransmitting the
>>     data (even though the first transmission did not contain the map
>>     for some reasons),  we could argue that RST could be avoided
>>     provided that the retransmission is triggered within a receive
>>     window of data. But the question here would be how and when will
>>     the retransmission take place. In this case, the subflow may not
>>     initiate the retransmission of data by its own (i.e., no
>>     retransmission due to three duplicate ACKs or RTO expiry at
>>     subflow level) as there is no segment loss at subflow level
>>     sequence space. So there could be a high possibility of RST
>>     happening even before the map delivery through retransmission.
>>
>>     With regards,
>>
>>     Anil
>>     ------------------------------------------------------------------------
>>     *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com
>>     <mailto:nsd.ietf@gmail.com>>
>>     *To: *"V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
>>     *Cc: *"alan ford" <alan.ford@gmail.com
>>     <mailto:alan.ford@gmail.com>>, "multipathtcp"
>>     <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
>>     *Sent: *Saturday, February 1, 2020 3:39:51 AM
>>     *Subject: *Re: [multipathtcp] RFC6824bis edits based on
>>     implementation feedback
>>
>>     Hi Anil,
>>
>>     I have a question about your proposed text.
>>     I am actually wondering if we really want to terminate connection
>>     here.
>>
>>     The packets without proper mappings will be treated as invalid and
>>     will be discarded.
>>     If an implementation failed to attach proper mapping for some
>>     reasons (e.g. option space), it might be able to attach the proper
>>     one when it retransmits the packets. This also looks ok to me.
>>
>>     I don't have strong preference for this. But, do we have a reason
>>     to terminate connection?
>>
>>     Thanks,
>>     --
>>     Yoshi
>>
>>     On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in
>>     <mailto:anil@csir4pi.in>> wrote:
>>
>>         Hi,
>>
>>         I have some points related to the  modifications (Change 2)
>>         being proposed on data sequence map. Please see them inline.
>>         Though I am putting forward the below points, if the consensus
>>         is in favour of the proposed change for reducing
>>         implementation complexity, I am also OK with that as well.
>>
>>         ------------------------------------------------------------------------
>>         *From: *"alan ford" <alan.ford@gmail.com
>>         <mailto:alan.ford@gmail.com>>
>>         *To: *multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>>         *Sent: *Thursday, January 2, 2020 4:21:32 AM
>>         *Subject: *[multipathtcp] RFC6824bis edits based on
>>         implementation feedback
>>
>>         Hi all,
>>         We’d love to get this to a state of completion as soon as
>>         possible, and to this end I am starting a new thread on this
>>         topic. In discussion with the chairs, it /is /possible to make
>>         the desired changes in AUTH48 as long as there is WG
>>         consensus. The discussion so far has been fairly limited in
>>         terms of participation.
>>
>>         I would ask the chairs please if it was possible to specify a
>>         time bound for this discussion and a default conclusion.
>>
>>         Regarding the changes, in summary, there are two areas where
>>         changes have been requested by the implementation community.
>>         As we are the IETF we obviously have strong focus on “running
>>         code” and so ease of implementing standards-compliant code is
>>         strongly desirable. However, we do not wish to reduce
>>         functionality agreed by the IETF community if it is considered
>>         a required feature by the community.
>>
>>
>>         *Change 1*
>>         *
>>         *
>>         Change the sentence reading:
>>
>>         /   If B has data to send first, then the reliable delivery of
>>         the ACK + MP_CAPABLE can be inferred by the receipt of this
>>         data with an MPTCP Data Sequence Signal (DSS) option (Section
>>         3.3).
>>         /
>>         To:
>>
>>         /   If B has data to send first, then the reliable delivery of
>>         the ACK + MP_CAPABLE is ensured by the receipt of this data
>>         with an MPTCP Data Sequence Signal (DSS) option (Section 3.3)
>>         containing a DATA_ACK for the MP_CAPABLE (which is the first
>>         octet of the data sequence space).
>>         /
>>         What this means:
>>
>>         The current text is concerned only with ensuring a path is
>>         MPTCP capable, and so only cares that DSS option occurs on a
>>         data packet. However, the MP_CAPABLE option is defined to
>>         occupy the first octet of data sequence space and thus, if
>>         analogous to TCP, must be acknowledged. >From an
>>         implementation point of view it would make sense not to have
>>         this hanging around forever and instead define it is
>>         acknowledged at the connection level as soon as received. This
>>         change ensures the first data packet also DATA_ACKs this
>>         MP_CAPABLE octet.
>>
>>
>>         *Change 2*
>>         *
>>         *
>>         Change the sentence reading:
>>
>>         /   A Data Sequence Mapping does not need to be included in
>>         every MPTCP packet, as long as the subflow sequence space in
>>         that packet is covered by a mapping known at the receiver./
>>
>>         To:
>>
>>         /   The mapping provided by a Data Sequence Mapping MUST apply
>>         to some or all of the subflow sequence space in the TCP
>>         segment which carries the option. It does not need to be
>>         included in every MPTCP packet, as long as the subflow
>>         sequence space in that packet is covered by a mapping known at
>>         the receiver.
>>         /
>>         What this means:
>>
>>         The current text does not place any restrictions on where a
>>         mapping could appear. In theory a sender could define a
>>         thousand different mappings up front, send them all, and
>>         expect a receiver to store this and reassemble data according
>>         to these mappings as it arrives. Indeed, this was never
>>         explicitly disallowed since it “might have been useful”. The
>>         implementation community, however, has expressed concerns over
>>         the difficulty of implementing this open-endedly. How many
>>         mappings is it reasonable to store? Is there a DoS risk here?
>>         Instead, it has been requested that thee specification
>>         restricts the placement of the DSS option to being within the
>>         subflow sequence space to which it applies.
>>
>>         Below are my comments on this. I had shared some of these
>>         points in a previous thread that you had initiated in the same
>>         context.
>>
>>         Transmitting large number of non-contiguous data sequence maps
>>         could be a misbehaviour (map-flooding), though it is not clear
>>         whether this can go to the extent of causing a potential DoS
>>         to the data receiver. So some sort of restriction on this
>>         could be useful.  One approach could be to insist that the
>>         data sender should ensure that the map being transmitted is
>>         for in-window data, as per the receiver advertised window. A
>>         receiver should anyhow be willing to store the maps for
>>         in-window data to deal with packet loss. For example, when a
>>         window of data segments (say 1 to 64) is transmitted, each
>>         carrying its corresponding map, and segment-1 is lost, the
>>         maps for the remaining 63 need to be stored till the lost
>>         segment is retransmitted. Of course, in this case the maps
>>         will be stored at the receiver side along with their
>>         corresponding data. But the need to store multiple maps for
>>         in-window data would still be there.
>>
>>         The problem with the proposed change (restriction) is that a
>>         data sender may find it difficult, in case a need arise to
>>         slightly delay the map delivery by few segments, i.e., sending
>>         some data first without map, and then send the corresponding
>>         map in a later segment, as shown below:
>>
>>         subflow-1:      segment-1                   segment-3         
>>                   segment-4                       segment-7
>>                               bytes:1-100                
>>         bytes:201-300              bytes:301-400                
>>         bytes:601-700
>>                               no map                        map for
>>         1-100              map for 201-400             map for 601-700
>>
>>
>>
>>         subflow-2:       segment-2                  segment-5        
>>                     segment-6                       segment-8
>>                                bytes: 101-200          
>>         bytes:401-500               bytes: 501-600              
>>          bytes:701-800
>>                                map for 101-200       map for 401-600  
>>                  no map                            map for 701-800
>>
>>
>>         In the above case, segment-1 goes without map and its map is
>>         included later in segment-3, the next data segment in the same
>>         subflow. Further,  in the above scheduling pattern, the map in
>>         segment-3 cannot cover the  data in segment-1 and segment-3,
>>         as some  data in between (segment-2) is transmitted through
>>         another subflow.  With the proposed change, the map in
>>         segment-3 will become invalid and this will eventually break
>>         subflow-1, though this could be a corner case.
>>
>>         The question at this stage is why would segment-1 be
>>         transmitted without its map. In the case of bidirectional data
>>         transfer, there could be a need to pack both timestamp and
>>         SACK  options in a data segment, i.e., piggybacking of  SACK
>>         with data. If we consider that timestamp takes 12 bytes and
>>         SACK, even with single block,  takes another 10 bytes, the
>>         remaining 18 bytes option space is not adequate to carry data
>>         sequence signal with map, especially when DSN is 64 bit long.
>>         So the delivery of either of the two (SACK or map) would be
>>         delayed.
>>
>>         As far as I understand, RFC 2018 (TCP Selective
>>         Acknowledgement Options) implies that SACK should not be
>>         delayed. It states "If sent at all, SACK options SHOULD be
>>         included in all ACKs which do not ACK the highest sequence
>>         number in the data receiver's queue". It also says "If data
>>         receiver generates SACK options under any circumstance, it
>>         SHOULD generate them under all permitted circumstances".   So,
>>         as part of meeting the RFC 2018 requirements, if the
>>         combination of SACK and timestamp is given preference over
>>         DSS, data segments could be transmitted without their map.
>>
>>         Another case of delaying map could arise if the data sender
>>         prefers to send ADD_ADDR option, instead of map, in a data
>>         segment. It is nice that ADD_ADDR option can be delivered
>>         reliably in a pure ACK, but I think this is not the case with
>>         DSS at present.
>>
>>         If we adopt the proposed change, I think it might also be
>>         helpful to spell out how the receiver is supposed to behave,
>>         if it gets maps not meeting the MUST condition in the proposed
>>         change.  For example termination of the subflow with MP_TCPRST
>>         option (section 3.6 in RFC 6824-bis) with appropriate reason
>>         code and T flag value to intimate the data sender the cause
>>         for subflow termination.
>>         With regards,
>>
>>         Anil
>>
>>         Please can members of the WG express whether they are happy
>>         with these changes, or concerned.
>>
>>         Best regards,
>>         Alan
>>
>>
>>         _______________________________________________
>>         multipathtcp mailing list
>>         multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/multipathtcp
>>
>>
>>
>>         _______________________________________________
>>         multipathtcp mailing list
>>         multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/multipathtcp
>>
>>
>>
>>
> 
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
> 

-- 
Matthieu Baerts | R&D Engineer
matthieu.baerts@tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium


From nobody Wed Feb  5 00:51:36 2020
Return-Path: <nsd.ietf@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 788C8120129 for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 00:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dvUfFyzEujPc for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 00:51:28 -0800 (PST)
Received: from mail-ua1-x92d.google.com (mail-ua1-x92d.google.com [IPv6:2607:f8b0:4864:20::92d]) (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 A378C120271 for <multipathtcp@ietf.org>; Wed,  5 Feb 2020 00:51:27 -0800 (PST)
Received: by mail-ua1-x92d.google.com with SMTP id 73so560084uac.6 for <multipathtcp@ietf.org>; Wed, 05 Feb 2020 00:51:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mCeT7j1n4myISutICWKXT3zjdJEZld7TzQttF+35Z5A=; b=aPfO+bj5Glnl7G2yB38otJRZrU/cRN6VzZPjnth5CB0KBJ0yHiWCQpUaH1Mde7yopk L3OFRzolm4YDBWPTPt63HkpobIgpDgWjcEzwuhSaLgv85JxqQZSemHHA4ufndJcuqNIu j6BzvfDwLqSEOJi6LceTQhrm4Cufh5Q/P+GGL1FuQi1+3HgjFSsKfdVGWlA1zaBaZFpG Kdyg7vKr6xxWleAaPWgxp7PpHpL9yS0NYI1BlTJmA5aEVsHUstE9FPAVsaLsEKDWJDf4 fgh9l1rVgow9fLuzdN+4suJLEUlaiIgXT31wAZp0P3w7wom5/hFALZQzfV67I30yPAwn xkAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mCeT7j1n4myISutICWKXT3zjdJEZld7TzQttF+35Z5A=; b=f/7+3beLKBVq0MUvnA/UnHhRDnzOrB71WLd2QxU8peaEby6B8Zbbpb33PFMamABJgI /Qj/QxzKxSe1YLMzQNi9sH6lexUM+pvAT8e/GZ0g4AqTqQDIjL+jCzqZN29pxIPlUdrU vJQQn7jZh1sofKhSbyYB59uYaz8+Du6z0fGQWxKcQEnrTez3fhjMUe0CEALL1g5rMpEm FUBPqIZT3/036HNlLjUCDd8P8LsC5BRm8zhB5oypZxj6YMS09lyE4e2BqtlJRnKoF6iG a9lCZR7QpOk1QUKzQ4acW0GDaTHGPzqkcgnl4bgbmLQxuyzQyr3sMahR4WXSeXZbVFbd Bpyg==
X-Gm-Message-State: APjAAAWi3jRhl9OWtdh+fNgXhkjkN9XyANNSgKcRHZwr049nal4T3sTC bqo+HCNKRDJEOMO1fs+h79fi8XJxh7QsBsIpTk8=
X-Google-Smtp-Source: APXvYqxiS3bslB7eIyz1TmMR8J9d8/5WhBeWrFkQV95H7Dzbne6KJeOnlU3ngztwjDWc8OXlpFyUosbPP1GXry5mQ80=
X-Received: by 2002:ab0:72ce:: with SMTP id g14mr686704uap.101.1580892686606;  Wed, 05 Feb 2020 00:51:26 -0800 (PST)
MIME-Version: 1.0
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <83C89953-EDAE-4B0C-B73B-9E88BAF3C927@gmail.com>
In-Reply-To: <83C89953-EDAE-4B0C-B73B-9E88BAF3C927@gmail.com>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Wed, 5 Feb 2020 00:51:15 -0800
Message-ID: <CAAK044Ti51YDoRH=3PLCZaHLTSUcrt-8BmzJtyBHFEiZC0P-rQ@mail.gmail.com>
To: Alan Ford <alan.ford@gmail.com>
Cc: V Anil Kumar <anil@csir4pi.in>, multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000367e2059dd0430b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/TEOlJd3uX66VM_ENUVrZdpmz3cI>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2020 08:51:32 -0000

--0000000000000367e2059dd0430b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Alan,

Yes, it makes sense. Thanks for the clarification.

BTW, I don't have a strong opinion about whether we should add some texts
to send RST for mapping issue case or the text in the draft Anil pointed
out is already enough.
However, if we want to add new texts, I think SHOULD will be preferable as
it won't contradict with the texts in the draft.
If we settle this, I think the doc is ready to bring it back to AUTH48.

Thanks,
--
Yoshi

On Tue, Feb 4, 2020 at 4:12 AM Alan Ford <alan.ford@gmail.com> wrote:

> Hi Yoshi,
>
> The proposed new text enforces a mapping to be sent on a packet whose
> subflow sequence number is included within the mapping provided. This doe=
s
> not directly contradict with the MAY case. Indeed this scenario could
> easily happen if there is a 20 byte packet followed by a 10 byte packet.
> The first 10 bytes of the first packet are covered by the mapping on pack=
et
> 1, then the remaining 10 bytes and the following 10 bytes are covered by
> the mapping on packet 2. That would be valid.
>
> To re-iterate, the primary purpose of this proposed text is to stop peopl=
e
> sending mappings before they are needed.
>
> Best regards,
> Alan
>
> On 4 Feb 2020, at 07:38, Yoshifumi Nishida <nsd.ietf@gmail.com> wrote:
>
> Hi Anil,
>
> Thanks for pointing it out. I overlooked this one.
> This looks an interesting point.
>
> It seems to me that whether RST is happen or not depends on the size of
> receive window according to the text.
> If the receive window size is big enough to accommodate segment 1 and
> segment 3, the text "Implementations MAY hold onto such unmapped data for
> a short while in the expectation that a mapping will arrive shortly. " ca=
n
> be applied to the segment 1. As a result, the segment 1 won't be discarde=
d.
> However, this might be contradict with the new texts Alan proposed? Or, a=
m
> I missing something?
>
> Thanks,
> --
> Yoshi
>
>
>
> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in> wrote:
>
>> Hi Yoshi,
>>
>> Thanks for this point. In fact, I had initially not thought of a
>> scenario, where the map is being delivered through a retransmitted data
>> packet while its first transmission did not include the map. Now I am ju=
st
>> seeing the document (RFC 6824-bis) in this context.
>>
>> My understanding is that in scenarios like what I described in my
>> previous mail, RST is likely to happen whether we explicitly state so or
>> not. Please see the paragraph containing the below text in RFC 6824-bis.
>>
>> "If a mapping for that subflow-level sequence space does not arrive
>> within a receive window of data, that subflow SHOULD be treated as broke=
n,
>> closed with a RST, and any unmapped data silently discarded."
>>
>> if we assume that the map is included while retransmitting the data (eve=
n
>> though the first transmission did not contain the map for some reasons),
>>  we could argue that RST could be avoided provided that the retransmissi=
on
>> is triggered within a receive window of data. But the question here woul=
d
>> be how and when will the retransmission take place. In this case, the
>> subflow may not initiate the retransmission of data by its own (i.e., no
>> retransmission due to three duplicate ACKs or RTO expiry at subflow leve=
l)
>> as there is no segment loss at subflow level sequence space. So there co=
uld
>> be a high possibility of RST happening even before the map delivery thro=
ugh
>> retransmission.
>>
>> With regards,
>>
>> Anil
>>
>> ------------------------------
>> *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>
>> *To: *"V Anil Kumar" <anil@csir4pi.in>
>> *Cc: *"alan ford" <alan.ford@gmail.com>, "multipathtcp" <
>> multipathtcp@ietf.org>
>> *Sent: *Saturday, February 1, 2020 3:39:51 AM
>> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation
>> feedback
>>
>> Hi Anil,
>>
>> I have a question about your proposed text.
>> I am actually wondering if we really want to terminate connection here.
>>
>> The packets without proper mappings will be treated as invalid and will
>> be discarded.
>> If an implementation failed to attach proper mapping for some reasons
>> (e.g. option space), it might be able to attach the proper one when it
>> retransmits the packets. This also looks ok to me.
>>
>> I don't have strong preference for this. But, do we have a reason to
>> terminate connection?
>>
>> Thanks,
>> --
>> Yoshi
>>
>> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in> wrote:
>>
>>> Hi,
>>>
>>> I have some points related to the  modifications (Change 2) being
>>> proposed on data sequence map. Please see them inline. Though I am
>>> putting forward the below points, if the consensus is in favour of the
>>> proposed change for reducing implementation complexity, I am also OK wi=
th
>>> that as well.
>>>
>>> ------------------------------
>>> *From: *"alan ford" <alan.ford@gmail.com>
>>> *To: *multipathtcp@ietf.org
>>> *Sent: *Thursday, January 2, 2020 4:21:32 AM
>>> *Subject: *[multipathtcp] RFC6824bis edits based on implementation
>>> feedback
>>>
>>> Hi all,
>>> We=E2=80=99d love to get this to a state of completion as soon as possi=
ble, and
>>> to this end I am starting a new thread on this topic. In discussion wit=
h
>>> the chairs, it *is *possible to make the desired changes in AUTH48 as
>>> long as there is WG consensus. The discussion so far has been fairly
>>> limited in terms of participation.
>>>
>>> I would ask the chairs please if it was possible to specify a time boun=
d
>>> for this discussion and a default conclusion.
>>>
>>> Regarding the changes, in summary, there are two areas where changes
>>> have been requested by the implementation community. As we are the IETF=
 we
>>> obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so ea=
se of implementing
>>> standards-compliant code is strongly desirable. However, we do not wish=
 to
>>> reduce functionality agreed by the IETF community if it is considered a
>>> required feature by the community.
>>>
>>>
>>> *Change 1*
>>>
>>> Change the sentence reading:
>>>
>>>
>>> *   If B has data to send first, then the reliable delivery of the ACK =
+
>>> MP_CAPABLE can be inferred by the receipt of this data with an MPTCP Da=
ta
>>> Sequence Signal (DSS) option (Section 3.3). *
>>> To:
>>>
>>>
>>> *   If B has data to send first, then the reliable delivery of the ACK =
+
>>> MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data
>>> Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for th=
e
>>> MP_CAPABLE (which is the first octet of the data sequence space).*
>>> What this means:
>>>
>>> The current text is concerned only with ensuring a path is MPTCP
>>> capable, and so only cares that DSS option occurs on a data packet.
>>> However, the MP_CAPABLE option is defined to occupy the first octet of =
data
>>> sequence space and thus, if analogous to TCP, must be acknowledged. >Fr=
om
>>> an implementation point of view it would make sense not to have this
>>> hanging around forever and instead define it is acknowledged at the
>>> connection level as soon as received. This change ensures the first dat=
a
>>> packet also DATA_ACKs this MP_CAPABLE octet.
>>>
>>>
>>> *Change 2*
>>>
>>> Change the sentence reading:
>>>
>>> *   A Data Sequence Mapping does not need to be included in every MPTCP
>>> packet, as long as the subflow sequence space in that packet is covered=
 by
>>> a mapping known at the receiver.*
>>>
>>> To:
>>>
>>>
>>> *   The mapping provided by a Data Sequence Mapping MUST apply to some
>>> or all of the subflow sequence space in the TCP segment which carries t=
he
>>> option. It does not need to be included in every MPTCP packet, as long =
as
>>> the subflow sequence space in that packet is covered by a mapping known=
 at
>>> the receiver.*
>>> What this means:
>>>
>>> The current text does not place any restrictions on where a mapping
>>> could appear. In theory a sender could define a thousand different mapp=
ings
>>> up front, send them all, and expect a receiver to store this and reasse=
mble
>>> data according to these mappings as it arrives. Indeed, this was never
>>> explicitly disallowed since it =E2=80=9Cmight have been useful=E2=80=9D=
. The implementation
>>> community, however, has expressed concerns over the difficulty of
>>> implementing this open-endedly. How many mappings is it reasonable to
>>> store? Is there a DoS risk here? Instead, it has been requested that th=
ee
>>> specification restricts the placement of the DSS option to being within=
 the
>>> subflow sequence space to which it applies.
>>>
>>> Below are my comments on this. I had shared some of these points in a
>>> previous thread that you had initiated in the same context.
>>>
>>> Transmitting large number of non-contiguous data sequence maps could be
>>> a misbehaviour (map-flooding), though it is not clear whether this can =
go
>>> to the extent of causing a potential DoS to the data receiver. So some =
sort
>>> of restriction on this could be useful.  One approach could be to insis=
t
>>> that the data sender should ensure that the map being transmitted is fo=
r
>>> in-window data, as per the receiver advertised window. A receiver shoul=
d
>>> anyhow be willing to store the maps for in-window data to deal with pac=
ket
>>> loss. For example, when a window of data segments (say 1 to 64) is
>>> transmitted, each carrying its corresponding map, and segment-1 is lost=
,
>>> the maps for the remaining 63 need to be stored till the lost segment i=
s
>>> retransmitted. Of course, in this case the maps will be stored at the
>>> receiver side along with their corresponding data. But the need to stor=
e
>>> multiple maps for in-window data would still be there.
>>>
>>> The problem with the proposed change (restriction) is that a data sende=
r
>>> may find it difficult, in case a need arise to slightly delay the map
>>> delivery by few segments, i.e., sending some data first without map, an=
d
>>> then send the corresponding map in a later segment, as shown below:
>>>
>>> subflow-1:      segment-1                   segment-3
>>> segment-4                       segment-7
>>>                       bytes:1-100                 bytes:201-300
>>>      bytes:301-400                 bytes:601-700
>>>                       no map                        map for 1-100
>>>        map for 201-400             map for 601-700
>>>
>>>
>>>
>>> subflow-2:       segment-2                  segment-5
>>>   segment-6                       segment-8
>>>                        bytes: 101-200           bytes:401-500
>>>         bytes: 501-600                bytes:701-800
>>>                        map for 101-200       map for 401-600
>>>  no map                            map for 701-800
>>>
>>>
>>> In the above case, segment-1 goes without map and its map is included
>>> later in segment-3, the next data segment in the same subflow. Further,=
  in
>>> the above scheduling pattern, the map in segment-3 cannot cover the  da=
ta
>>> in segment-1 and segment-3, as some  data in between (segment-2) is
>>> transmitted through another subflow.  With the proposed change, the map=
 in
>>> segment-3 will become invalid and this will eventually break subflow-1,
>>> though this could be a corner case.
>>>
>>> The question at this stage is why would segment-1 be transmitted withou=
t
>>> its map. In the case of bidirectional data transfer, there could be a n=
eed
>>> to pack both timestamp and SACK  options in a data segment, i.e.,
>>> piggybacking of  SACK with data. If we consider that timestamp takes 12
>>> bytes and SACK, even with single block,  takes another 10 bytes, the
>>> remaining 18 bytes option space is not adequate to carry data sequence
>>> signal with map, especially when DSN is 64 bit long. So the delivery of
>>> either of the two (SACK or map) would be delayed.
>>>
>>> As far as I understand, RFC 2018 (TCP Selective Acknowledgement Options=
)
>>> implies that SACK should not be delayed. It states "If sent at all, SAC=
K
>>> options SHOULD be included in all ACKs which do not ACK the highest
>>> sequence number in the data receiver's queue". It also says "If data
>>> receiver generates SACK options under any circumstance, it SHOULD gener=
ate
>>> them under all permitted circumstances".   So, as part of meeting the R=
FC
>>> 2018 requirements, if the combination of SACK and timestamp is given
>>> preference over DSS, data segments could be transmitted without their m=
ap.
>>>
>>> Another case of delaying map could arise if the data sender prefers to
>>> send ADD_ADDR option, instead of map, in a data segment. It is nice tha=
t
>>> ADD_ADDR option can be delivered reliably in a pure ACK, but I think th=
is
>>> is not the case with DSS at present.
>>>
>>> If we adopt the proposed change, I think it might also be helpful to
>>> spell out how the receiver is supposed to behave, if it gets maps not
>>> meeting the MUST condition in the proposed change.  For example termina=
tion
>>> of the subflow with MP_TCPRST option (section 3.6 in RFC 6824-bis) with
>>> appropriate reason code and T flag value to intimate the data sender th=
e
>>> cause for subflow termination.
>>>
>>> With regards,
>>>
>>> Anil
>>>
>>> Please can members of the WG express whether they are happy with these
>>> changes, or concerned.
>>>
>>> Best regards,
>>> Alan
>>>
>>>
>>> _______________________________________________
>>> multipathtcp mailing list
>>> multipathtcp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>>
>>>
>>>
>>> _______________________________________________
>>> multipathtcp mailing list
>>> multipathtcp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>>
>>
>>
>>
>>
>

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

<div dir=3D"ltr"><div>Hi Alan,</div><div><br></div><div>Yes, it makes sense=
. Thanks for the clarification.</div><div><br></div><div>BTW, I don&#39;t h=
ave a strong opinion about whether=C2=A0we should add some texts to send RS=
T for mapping issue case or the text in the draft Anil pointed out is alrea=
dy enough.</div><div>However, if we want to add new texts, I think SHOULD w=
ill be preferable as it won&#39;t contradict with the texts in the draft.=
=C2=A0</div><div>If we settle this, I think the doc is ready to bring it ba=
ck to AUTH48.</div><div><br></div><div>Thanks,=C2=A0</div><div>--</div><div=
>Yoshi=C2=A0</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Tue, Feb 4, 2020 at 4:12 AM Alan Ford &lt;<a href=3D"mailto:=
alan.ford@gmail.com">alan.ford@gmail.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div style=3D"word-wrap:break-word"=
>Hi Yoshi,<div><br></div><div>The proposed new text enforces a mapping to b=
e sent on a packet whose subflow sequence number is included within the map=
ping provided. This does not directly contradict with the MAY case. Indeed =
this scenario could easily happen if there is a 20 byte packet followed by =
a 10 byte packet. The first 10 bytes of the first packet are covered by the=
 mapping on packet 1, then the remaining 10 bytes and the following 10 byte=
s are covered by the mapping on packet 2. That would be valid.</div><div><b=
r></div><div>To re-iterate, the primary purpose of this proposed text is to=
 stop people sending mappings before they are needed.</div><div><br></div><=
div>Best regards,</div><div>Alan</div><div><div><br><blockquote type=3D"cit=
e"><div>On 4 Feb 2020, at 07:38, Yoshifumi Nishida &lt;<a href=3D"mailto:ns=
d.ietf@gmail.com" target=3D"_blank">nsd.ietf@gmail.com</a>&gt; wrote:</div>=
<br><div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</=
div><div><br></div><div>Thanks for pointing it out. I overlooked this one.<=
/div><div>This looks an interesting point.<br></div><div><br></div><div>It =
seems to me that whether RST is happen or not depends on the size of receiv=
e window according to the text.<br></div><div>If the receive window size is=
 big enough to accommodate=C2=A0segment 1 and segment 3, the text &quot;<sp=
an style=3D"font-size:13.3333px">Implementations MAY hold onto such unmappe=
d data for a short while in=C2=A0</span><span style=3D"font-size:13.3333px"=
>the expectation that a mapping will arrive shortly. &quot;=C2=A0</span>can=
 be applied to the segment 1. As a result, the segment 1 won&#39;t be disca=
rded.=C2=A0</div><div>However, this might be contradict with the new texts =
Alan proposed? Or, am I missing something?</div><div><br></div><div>Thanks,=
</div><div>--</div><div>Yoshi</div><div><br></div><div><br></div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Feb 2, 2=
020 at 8:42 AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" target=
=3D"_blank">anil@csir4pi.in</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div><div><div><div style=3D"font-family:arial,h=
elvetica,sans-serif"><div>Hi Yoshi,</div><br><div>Thanks for this point. In=
 fact, I had initially not thought of a scenario, where the map is being de=
livered through a retransmitted data packet while its first transmission di=
d not include the map. Now I am just seeing the document (RFC 6824-bis) in =
this context.</div><br><div>My understanding is that in scenarios like what=
 I described in my previous mail, RST is likely to happen whether we explic=
itly state so or not. Please see the paragraph containing the below text in=
 RFC 6824-bis. =C2=A0</div><br><div>&quot;If a mapping for that subflow-lev=
el sequence space does not arrive within a receive window of data, that sub=
flow SHOULD be treated as broken, closed with a RST, and any unmapped data =
silently discarded.&quot;</div><br><div>if we assume that the map is includ=
ed while retransmitting the data (even though the first transmission did no=
t contain the map for some reasons), =C2=A0we could argue that RST could be=
 avoided provided that the retransmission is triggered within a receive win=
dow of data. But the question here would be how and when will the retransmi=
ssion take place. In this case, the subflow may not initiate the retransmis=
sion of data by its own (i.e., no retransmission due to three duplicate ACK=
s or RTO expiry at subflow level) as there is no segment loss at subflow le=
vel sequence space. So there could be a high possibility of RST happening e=
ven before the map delivery through retransmission.=C2=A0</div><br><div>Wit=
h regards,=C2=A0</div><br><div>Anil</div><div>=C2=A0</div><hr id=3D"gmail-m=
_4221166682082290047gmail-m_218086596951724501gmail-m_2982267033577902985zw=
chr"><div><b>From: </b>&quot;Yoshifumi Nishida&quot; &lt;<a href=3D"mailto:=
nsd.ietf@gmail.com" target=3D"_blank">nsd.ietf@gmail.com</a>&gt;<br><b>To: =
</b>&quot;V Anil Kumar&quot; &lt;<a href=3D"mailto:anil@csir4pi.in" target=
=3D"_blank">anil@csir4pi.in</a>&gt;<br><b>Cc: </b>&quot;alan ford&quot; &lt=
;<a href=3D"mailto:alan.ford@gmail.com" target=3D"_blank">alan.ford@gmail.c=
om</a>&gt;, &quot;multipathtcp&quot; &lt;<a href=3D"mailto:multipathtcp@iet=
f.org" target=3D"_blank">multipathtcp@ietf.org</a>&gt;<br><b>Sent: </b>Satu=
rday, February 1, 2020 3:39:51 AM<br><b>Subject: </b>Re: [multipathtcp] RFC=
6824bis edits based on implementation feedback<br></div><br><div><div dir=
=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><br><div>I ha=
ve a question about your proposed text.</div><div><div>I am actually wonder=
ing if we really want to terminate connection here.=C2=A0</div></div><br><d=
iv>The packets without proper mappings will be treated as invalid and will =
be discarded.=C2=A0</div><div>If an implementation failed to attach proper =
mapping for some reasons (e.g. option space), it might be able to attach th=
e proper one when it retransmits the packets. This also looks ok to me.</di=
v><br><div>I don&#39;t have strong preference for this. But, do we have a r=
eason to terminate connection?</div><br><div>Thanks,</div><div>--<br></div>=
<div>Yoshi</div><br><div><div dir=3D"ltr">On Mon, Jan 13, 2020 at 10:28 AM =
V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow%20noope=
ner%20noreferrer nofollow noopener noreferrer" target=3D"_blank">anil@csir4=
pi.in</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div><div><div><div style=3D"font-family:arial,helvetica,sans-serif"><=
div><span style=3D"font-size:12pt;line-height:1.3">Hi,</span><br></div><div=
><div style=3D"font-family:arial,helvetica,sans-serif"><div style=3D"font-f=
amily:arial,helvetica,sans-serif"><div style=3D"font-family:arial,helvetica=
,sans-serif"><div style=3D"font-family:arial,helvetica,sans-serif"><div sty=
le=3D"font-family:arial,helvetica,sans-serif"><div style=3D"font-family:ari=
al,helvetica,sans-serif"><div style=3D"font-family:arial,helvetica,sans-ser=
if"><br><div>I have some points related to the =C2=A0modifications (Change =
2) being proposed on data sequence map. Please see them inline.=C2=A0<span =
style=3D"font-family:arial,helvetica,sans-serif;font-size:16px;font-style:n=
ormal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);=
float:none;display:inline">Though I am putting forward the below points, if=
 the consensus is in favour of the proposed change for reducing implementat=
ion complexity, I am also OK with that as well.=C2=A0</span><br></div><br><=
hr id=3D"gmail-m_4221166682082290047gmail-m_218086596951724501gmail-m_29822=
67033577902985gmail-m_7687184382299596774zwchr"><div><b>From: </b>&quot;ala=
n ford&quot; &lt;<a href=3D"mailto:alan.ford@gmail.com" rel=3D"nofollow%20n=
oopener%20noreferrer nofollow noopener noreferrer" target=3D"_blank">alan.f=
ord@gmail.com</a>&gt;<br><b>To: </b><a href=3D"mailto:multipathtcp@ietf.org=
" rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferrer" tar=
get=3D"_blank">multipathtcp@ietf.org</a><br><b>Sent: </b>Thursday, January =
2, 2020 4:21:32 AM<br><b>Subject: </b>[multipathtcp] RFC6824bis edits based=
 on implementation feedback<br></div><br><div>Hi all,<br><div>We=E2=80=99d =
love to get this to a state of completion as soon as possible, and to this =
end I am starting a new thread on this topic. In discussion with the chairs=
, it <i>is </i>possible to make the desired changes in AUTH48 as long as th=
ere is WG consensus. The discussion so far has been fairly limited in terms=
 of participation.</div><br><div>I would ask the chairs please if it was po=
ssible to specify a time bound for this discussion and a default conclusion=
.</div><br><div>Regarding the changes, in summary, there are two areas wher=
e changes have been requested by the implementation community. As we are th=
e IETF we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and=
 so ease of implementing standards-compliant code is strongly desirable. Ho=
wever, we do not wish to reduce functionality agreed by the IETF community =
if it is considered a required feature by the community.</div><br><br><div>=
<b>Change 1</b></div><div><b><br></b></div><div>Change the sentence reading=
:<br><br><i>=C2=A0 =C2=A0If B has data to send first, then the reliable del=
ivery of the ACK + MP_CAPABLE can be inferred by the receipt of this data w=
ith an MPTCP Data Sequence Signal (DSS) option (Section 3.3).=C2=A0<br></i>=
<br>To:<br><br><i>=C2=A0 =C2=A0If B has data to send first, then the reliab=
le delivery of the ACK + MP_CAPABLE is ensured by the receipt of this data =
with an MPTCP Data Sequence Signal (DSS) option (Section 3.3) containing a =
DATA_ACK for the MP_CAPABLE (which is the first octet of the data sequence=
=C2=A0space).<br></i><br></div><div>What this means:</div><br><div>The curr=
ent text is concerned only with ensuring a path is MPTCP capable, and so on=
ly cares that DSS option occurs on a data packet. However, the MP_CAPABLE o=
ption is defined to occupy the first octet of data sequence space and thus,=
 if analogous to TCP, must be acknowledged. &gt;From an implementation poin=
t of view it would make sense not to have this hanging around forever and i=
nstead define it is acknowledged at the connection level as soon as receive=
d. This change ensures the first data packet also DATA_ACKs this MP_CAPABLE=
 octet.</div><br><br><div><b>Change 2</b></div><div><b><br></b></div><div>C=
hange the sentence reading:<br><br><i>=C2=A0 =C2=A0A Data Sequence Mapping =
does not need to be included in every MPTCP packet, as long as the subflow =
sequence space in that packet is covered by a mapping known at the receiver=
.</i><br><br>To:<br><br><i>=C2=A0 =C2=A0The mapping provided by a Data Sequ=
ence Mapping MUST apply to some or all of the subflow sequence space in the=
 TCP segment which carries the option. It does not need to be included in e=
very MPTCP packet, as long as the subflow sequence space in that packet is =
covered by a mapping known at the receiver.<br></i><br>What this means:</di=
v><br><div>The current text does not place any restrictions on where a mapp=
ing could appear. In theory a sender could define a thousand different mapp=
ings up front, send them all, and expect a receiver to store this and reass=
emble data according to these mappings as it arrives. Indeed, this was neve=
r explicitly disallowed since it =E2=80=9Cmight have been useful=E2=80=9D. =
The implementation community, however, has expressed concerns over the diff=
iculty of implementing this open-endedly. How many mappings is it reasonabl=
e to store? Is there a DoS risk here? Instead, it has been requested that t=
hee specification restricts the placement of the DSS option to being within=
 the subflow sequence space to which it applies.</div><br><div>Below are my=
 comments on this. I had shared some of these points in a previous thread t=
hat you had initiated in the same context.=C2=A0</div><br><div>Transmitting=
 large number of non-contiguous data sequence maps could be a misbehaviour =
(map-flooding), though it is not clear whether this can go to the extent of=
 causing a potential DoS to the data receiver. So some sort of restriction =
on this could be useful.=C2=A0 One approach could be to insist that the dat=
a sender should ensure that the map being transmitted is for in-window data=
, as per the receiver advertised window. A receiver should anyhow be willin=
g to store the maps for in-window data to deal with packet loss. For exampl=
e, when a window of data segments (say 1 to 64) is transmitted, each carryi=
ng its corresponding map, and segment-1 is lost, the maps for the remaining=
 63 need to be stored till the lost segment is retransmitted. Of course, in=
 this case the maps will be stored at the receiver side along with their co=
rresponding data. But the need to store multiple maps for in-window data wo=
uld still be there.</div><br><div><span style=3D"font-family:arial,helvetic=
a,sans-serif;font-size:16px;font-style:normal;font-weight:normal;letter-spa=
cing:normal;line-height:20.8px;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;float:none;background-color:rgb(255,255,255);di=
splay:inline">The problem with the proposed change (restriction) is that a =
data sender may find it difficult, in case a need arise to slightly delay t=
he map delivery by few segments, i.e., sending some data first without map,=
 and then send the corresponding map in a later segment, as shown below:</s=
pan><br></div><br><div><div style=3D"font-family:&quot;segoe ui&quot;,&quot=
;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weig=
ht:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;margin:0px;background-color=
:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">subflow-1:=
=C2=A0 =C2=A0 =C2=A0 segment-1=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 segment-3=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-=
4 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 segment-7</span></div><div style=3D"font-family:&quot;segoe ui&quot;,&q=
uot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-w=
eight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-=
transform:none;white-space:normal;word-spacing:0px;margin:0px;background-co=
lor:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">=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=C2=A0=C2=A0=C2=A0bytes:1-100 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 bytes:201-300 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0bytes:301-400 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 bytes:601-700</span></div><div style=3D"font-family:&=
quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;fo=
nt-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal=
;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;ma=
rgin:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"f=
ont-size:10pt">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0=C2=A0no map =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0map for 1-100 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0map for 201-400 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 map for 601-700</span></div><div style=3D"font-family:&quot;sego=
e ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:=
normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-ind=
ent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;=
background-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:=
10pt"><br></span></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot=
;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weig=
ht:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;margin:0px;background-color=
:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt"><br></span=
></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quo=
t;,sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter=
-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;whit=
e-space:normal;word-spacing:0px;margin:0px;background-color:rgb(255,255,255=
)"><br></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sa=
ns&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;=
letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:non=
e;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(255,2=
55,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">subflow-2:=C2=A0 =C2=
=A0 =C2=A0 =C2=A0segment-2=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 segment-5 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 segment-6 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-8</span></div><div style=3D"font=
-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:1=
4.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-heig=
ht:normal;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;margin:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" s=
tyle=3D"font-size:10pt">=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=C2=A0=C2=A0=C2=
=A0=C2=A0bytes: 101-200 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 bytes:401-500=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 bytes: 501-600 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0b=
ytes:701-800=C2=A0=C2=A0=C2=A0</span></div><div style=3D"font-family:&quot;=
segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-st=
yle:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:=
0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-s=
ize:10pt">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0map for 101-200 =C2=A0 =C2=A0 =C2=A0 map for 401-600 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0no map =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=A0map f=
or 701-800</span></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot=
;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weig=
ht:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;margin:0px;background-color=
:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt"></span><br=
></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quo=
t;,sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter=
-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;whit=
e-space:normal;word-spacing:0px;margin:0px;background-color:rgb(255,255,255=
)"><span lang=3D"EN-US" style=3D"font-size:10pt"></span><br></div>In the ab=
ove case, segment-1 goes without map and its map is included later in segme=
nt-3, the next data segment in the same subflow. Further, =C2=A0in the abov=
e scheduling pattern, the map in segment-3 cannot cover the =C2=A0data in s=
egment-1 and segment-3, as some =C2=A0data in between (segment-2) is transm=
itted through another subflow.=C2=A0 With the proposed change, the map in s=
egment-3 will become invalid and this will eventually break subflow-1, thou=
gh this could be a corner case.</div><br><div>The question at this stage is=
 why would segment-1 be transmitted without its map. In the case of bidirec=
tional data transfer, there could be a need to pack both timestamp and SACK=
 =C2=A0options in a data segment, i.e., piggybacking of =C2=A0SACK with dat=
a. If we consider that timestamp takes 12 bytes and SACK, even with single =
block, =C2=A0takes another 10 bytes, the remaining 18 bytes option space is=
 not adequate to carry data sequence signal with map, especially when DSN i=
s 64 bit long. So the delivery of either of the two (SACK or map) would be =
delayed.</div><br><div>As far as I understand, RFC 2018 (TCP Selective Ackn=
owledgement Options) implies that SACK should not be delayed. It states &qu=
ot;If sent at all, SACK options SHOULD be included in all ACKs which do not=
 ACK the highest sequence number in the data receiver&#39;s queue&quot;. It=
 also says &quot;If data receiver generates SACK options under any circumst=
ance, it SHOULD generate them under all permitted circumstances&quot;. =C2=
=A0 So, as part of meeting the RFC 2018 requirements, if the combination of=
 SACK and timestamp is given preference over DSS, data segments could be tr=
ansmitted without their map.=C2=A0</div><br><div>Another case of delaying m=
ap could arise if the data sender prefers to send ADD_ADDR option, instead =
of map, in a data segment. It is nice that ADD_ADDR option can be delivered=
 reliably in a pure ACK, but I think this is not the case with DSS at prese=
nt.</div><br><div>If we adopt the proposed change, I think it might also be=
 helpful to spell out how the receiver is supposed to behave, if it gets ma=
ps not meeting the MUST condition in the proposed change.=C2=A0 For example=
 termination of the subflow with MP_TCPRST option (section 3.6 in RFC 6824-=
bis) with appropriate reason code and T flag value to intimate the data sen=
der the cause for subflow termination.=C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0</div></div><div>With regards,</div><br><div>Anil<br><b=
r><div>Please can members of the WG express whether they are happy with the=
se changes, or concerned.</div><br><div>Best regards,</div><div>Alan</div><=
br><br>_______________________________________________<br>multipathtcp mail=
ing list<br><a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noop=
ener%20noreferrer nofollow noopener noreferrer" target=3D"_blank">multipath=
tcp@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/multip=
athtcp" rel=3D"nofollow%20noopener%20noreferrer nofollow noopener noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a>=
</div></div></div></div></div></div></div></div></div></div><br></div></div=
></div>
<br>
<br>_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noopener%20noref=
errer nofollow noopener noreferrer" target=3D"_blank">multipathtcp@ietf.org=
</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"noref=
errer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
</blockquote></div></div></div></div></div></div><br></div></div>
<br>
<br></div></blockquote></div></div></div></div>
</div></blockquote></div><br></div></div></blockquote></div></div>

--0000000000000367e2059dd0430b--


From nobody Wed Feb  5 04:23:23 2020
Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 859C8120073 for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 04:23:20 -0800 (PST)
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, 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 (1024-bit key) header.d=bt.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 tveN5Z6Vz6mk for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 04:23:17 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E6C2120048 for <multipathtcp@ietf.org>; Wed,  5 Feb 2020 04:23:16 -0800 (PST)
Received: from tpw09926dag08g.domain1.systemhost.net (10.9.202.43) by BWP09926082.bt.com (10.36.82.113) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Wed, 5 Feb 2020 12:23:13 +0000
Received: from tpw09926dag08h.domain1.systemhost.net (10.9.202.47) by tpw09926dag08g.domain1.systemhost.net (10.9.202.43) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 5 Feb 2020 12:23:14 +0000
Received: from bwp09926083.bt.com (10.36.82.114) by tpw09926dag08h.domain1.systemhost.net (10.9.202.47) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 5 Feb 2020 12:23:13 +0000
Received: from GBR01-LO2-obe.outbound.protection.outlook.com (104.47.21.58) by smtpe1.intersmtp.com (10.36.82.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Wed, 5 Feb 2020 12:23:12 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HspLcyS/maF3cCHqsJajiIB3vimNQ7D0sBgoNcOwEW210tp2fpYboXJFnqPwbWsu7apyWzJPMNOLiWPYZTVG+jXXAyLfYEWwNlpN/exyVXSwS9IzPtcYP78Ig5JZkVPOXUa0IT+P6pvu4SA52m7vNUcpOeJSGZnWRxI2OsEcCplepais8LsDZjIvKcej4DxZ7CP7SUSXq74wRHJK9FbS7Qy+LGwD/fAM6l440U6LVglhgn2HZjK6y76LE/mma0CKmiocA+fLJ5wmMEP6GkJz9IgogXNSms/RBD1wL0OJpxtJ0k+na21pBUcAwXk6yuNHfNWuFP9MzrQ18Y2GVhw8dQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0psGdN32CbYhUj80eTDWuz6QgM2ZIItbRJC/j3wm4fE=; b=XpSF7AEik3n2QAbpm30Ifz4fmAJWF6y7LLLprDOj2fxEqHShv5PrIrKgpZAtvq5OcqFeyI6Cj9eVVA1szlCBEWw5jWJw0mFYatzJOMtwrzkK/ppYSdpzmnClHkiK6NGM1Z3iig6Ced+dnn190081Tl6l8oGdRdi/XNUIH0jHA3L+d+bnWR7M80sLebxz1+Z7R+ckGDnQUGwW4zVtvAQSSb3FD0B3gkunzVOULF0z7YKVNavPzJqwqewM0ljcrknvOwRv8H5ThWCJ9bQRnPaFFb5oDc0cRTWQ72JG53uKLqOe8bbcPbhiZwITCTvISFwwi1FgIdTU38W+PZZ9eDFqyA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0psGdN32CbYhUj80eTDWuz6QgM2ZIItbRJC/j3wm4fE=; b=E+JP/kfAp87lqqGfOZQFjA15gCaNv3fqrR8gJdL8TqDNafb0noSsMtYLLWfYzWSZxuuUCWlci1smeQykEgoWxpubvBYNFH2ZkRnAvNQAQLZ/e6dBmGpKEAh5kOCdS4xPnIULe3fesaBnQjY/Eu1c4crKvltRKeeVTSm2CoCA8R0=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXP123MB2057.GBRP123.PROD.OUTLOOK.COM (20.179.131.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.21; Wed, 5 Feb 2020 12:23:12 +0000
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c]) by LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c%7]) with mapi id 15.20.2686.031; Wed, 5 Feb 2020 12:23:12 +0000
From: <philip.eardley@bt.com>
To: <nsd.ietf@gmail.com>, <alan.ford@gmail.com>
CC: <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] RFC6824bis edits based on implementation feedback
Thread-Index: AQHV2efjE0t2RY94ZkaZvM9k72KnJ6gKqHKAgABMbYCAAVoqgIAAOYvg
Date: Wed, 5 Feb 2020 12:23:12 +0000
Message-ID: <LNXP123MB2587401C237F7FF68CF09850EB020@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <83C89953-EDAE-4B0C-B73B-9E88BAF3C927@gmail.com> <CAAK044Ti51YDoRH=3PLCZaHLTSUcrt-8BmzJtyBHFEiZC0P-rQ@mail.gmail.com>
In-Reply-To: <CAAK044Ti51YDoRH=3PLCZaHLTSUcrt-8BmzJtyBHFEiZC0P-rQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com; 
x-originating-ip: [46.233.112.34]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 39a1b83f-f066-44b2-3aff-08d7aa362b23
x-ms-traffictypediagnostic: LNXP123MB2057:
x-microsoft-antispam-prvs: <LNXP123MB2057376E47EC95228528D246EB020@LNXP123MB2057.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0304E36CA3
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(396003)(136003)(39860400002)(376002)(366004)(199004)(189003)(186003)(33656002)(71200400001)(110136005)(86362001)(2906002)(30864003)(4326008)(8936002)(26005)(7696005)(81156014)(53546011)(6506007)(81166006)(8676002)(76116006)(66476007)(66446008)(64756008)(66556008)(66946007)(55016002)(9686003)(52536014)(5660300002)(478600001)(966005)(316002)(66574012); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXP123MB2057; H:LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: DgSDhOjCJr8FUX/5xaUm4MKb7yLoKcpvqtwva6KM45PuJ67lGDjKeqIXj0jqnUDlWtmiOO1yCJWFSWJplfBRkCfHcEZ+AAcPuR55XfeneKFv+ARfakNGeJv7oxNGrnENmCKMPm8BcPGa9Jkg+2xRwLvxI1uI0LgP6n/tuFFfbUZ0brpYtyqHhqWaMPILXDtU2E1nWx8eRN3G8hAjM7Um+5dLfZijKL9TJ/ryU5it/FpYQQimZCEagNa/O9eF0CjBduzeflE3QNLixVPcdzoYOUa04dBFmsNaj4fny+oHFcwuELrJq0yqb1HnzsKkL74+L058w585ThxSWtsfEZ0UU8qiYRM4dzjPEzao4/9aS1mE3CbllewBBQshGnSQp9b5E0axvmTfMN3s+8r/95Poh+KBGrIoKnLUsz8/w3ks6LjWAlzBpmbXZWwN1AIlg8ah9WL6N0PQ25uaGhJsqD4LPGuzt58ODKIeuPqkeAweKtJGvxYxg5nKJjMis7E879NBV1CLzCeb+Ly9PyQECIK/Pg==
x-ms-exchange-antispam-messagedata: PqRHhvKGcJ/52O1HhyRqhQ8P5U8UKKWPBF4DYTH6ovFa73IgwoC4cCbUrA44MSEY4hDG9YQVrG3pFxMBBCvag0obyjkTWKTGf3CjzUvL1Bb8cxf81494EDHfEZh6LCnzLyB8kN+mJxsI90N4aaYQuA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB2587401C237F7FF68CF09850EB020LNXP123MB2587GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 39a1b83f-f066-44b2-3aff-08d7aa362b23
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2020 12:23:12.3790 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: oY7zhmihonByj9oKMsZJPK2X9iGqTYu4yAti3J3x2PTY6v+S07+Tuq3e8fEmeqSk+X2evtt3W/xGm3ejv8HhzQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB2057
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Lez-1EYxz_sgx01bTUMbtnNHUAw>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2020 12:23:21 -0000

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

VHJ5aW5nIHRvIHN1bW1hcmlzZSDigJMgaWYgSSBnZXQgdGhlIGRpc2N1c3Npb24gcmlnaHQsIGl0
IHNlZW1zIHRoYXQgdGhlIOKAnENoYW5nZSAy4oCdIHRleHQgcHJvcG9zZWQgaW4gQWxhbuKAmXMg
ZW1haWwgaXMgT0sgYW5kIHRoYXQgdGhlIHRleHQgdGhlcmUgYW5kIGVsc2V3aGVyZSBpcyBzdWZm
aWNpZW50Lg0KDQpNYXR0IOKAkyB0aGFua3MgZm9yIHlvdXIgZW1haWwsIGl04oCZcyB2ZXJ5IGdv
b2QgdG8ga25vdyB0aGF0IHRoZSBjaGFuZ2VzIGFyZSBpbXBvcnRhbnQgZnJvbSB0aGUgaW1wbGVt
ZW50ZXJzIHBvaW50IG9mIHZpZXcg4oCTIGFuZCB0aGFua3MgZm9yIGFsbCB5b3UgJiB5b3VyIGNv
bGxlYWd1ZXMgZWZmb3J0cyBvbiBib3RoIHRoZSBpbnRlcm5ldCBkcmFmdCBsaW51eCBhbmQgdGhl
IHVwc3RyZWFtIG9uZSAobmVhcmx5IGluIG1haW5saW5lPykNCg0KQmVzdCB3aXNoZXMsDQpwaGls
DQoNCkZyb206IG11bHRpcGF0aHRjcCA8bXVsdGlwYXRodGNwLWJvdW5jZXNAaWV0Zi5vcmc+IE9u
IEJlaGFsZiBPZiBZb3NoaWZ1bWkgTmlzaGlkYQ0KU2VudDogMDUgRmVicnVhcnkgMjAyMCAwODo1
MQ0KVG86IEFsYW4gRm9yZCA8YWxhbi5mb3JkQGdtYWlsLmNvbT4NCkNjOiBtdWx0aXBhdGh0Y3Ag
PG11bHRpcGF0aHRjcEBpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbbXVsdGlwYXRodGNwXSBSRkM2
ODI0YmlzIGVkaXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrDQoNCkhpIEFsYW4s
DQoNClllcywgaXQgbWFrZXMgc2Vuc2UuLiBUaGFua3MgZm9yIHRoZSBjbGFyaWZpY2F0aW9uLg0K
DQpCVFcsIEkgZG9uJ3QgaGF2ZSBhIHN0cm9uZyBvcGluaW9uIGFib3V0IHdoZXRoZXIgd2Ugc2hv
dWxkIGFkZCBzb21lIHRleHRzIHRvIHNlbmQgUlNUIGZvciBtYXBwaW5nIGlzc3VlIGNhc2Ugb3Ig
dGhlIHRleHQgaW4gdGhlIGRyYWZ0IEFuaWwgcG9pbnRlZCBvdXQgaXMgYWxyZWFkeSBlbm91Z2gu
DQpIb3dldmVyLCBpZiB3ZSB3YW50IHRvIGFkZCBuZXcgdGV4dHMsIEkgdGhpbmsgU0hPVUxEIHdp
bGwgYmUgcHJlZmVyYWJsZSBhcyBpdCB3b24ndCBjb250cmFkaWN0IHdpdGggdGhlIHRleHRzIGlu
IHRoZSBkcmFmdC4NCklmIHdlIHNldHRsZSB0aGlzLCBJIHRoaW5rIHRoZSBkb2MgaXMgcmVhZHkg
dG8gYnJpbmcgaXQgYmFjayB0byBBVVRINDguDQoNClRoYW5rcywNCi0tDQpZb3NoaQ0KDQpPbiBU
dWUsIEZlYiA0LCAyMDIwIGF0IDQ6MTIgQU0gQWxhbiBGb3JkIDxhbGFuLmZvcmRAZ21haWwuY29t
PG1haWx0bzphbGFuLmZvcmRAZ21haWwuY29tPj4gd3JvdGU6DQpIaSBZb3NoaSwNCg0KVGhlIHBy
b3Bvc2VkIG5ldyB0ZXh0IGVuZm9yY2VzIGEgbWFwcGluZyB0byBiZSBzZW50IG9uIGEgcGFja2V0
IHdob3NlIHN1YmZsb3cgc2VxdWVuY2UgbnVtYmVyIGlzIGluY2x1ZGVkIHdpdGhpbiB0aGUgbWFw
cGluZyBwcm92aWRlZC4gVGhpcyBkb2VzIG5vdCBkaXJlY3RseSBjb250cmFkaWN0IHdpdGggdGhl
IE1BWSBjYXNlLiBJbmRlZWQgdGhpcyBzY2VuYXJpbyBjb3VsZCBlYXNpbHkgaGFwcGVuIGlmIHRo
ZXJlIGlzIGEgMjAgYnl0ZSBwYWNrZXQgZm9sbG93ZWQgYnkgYSAxMCBieXRlIHBhY2tldC4gVGhl
IGZpcnN0IDEwIGJ5dGVzIG9mIHRoZSBmaXJzdCBwYWNrZXQgYXJlIGNvdmVyZWQgYnkgdGhlIG1h
cHBpbmcgb24gcGFja2V0IDEsIHRoZW4gdGhlIHJlbWFpbmluZyAxMCBieXRlcyBhbmQgdGhlIGZv
bGxvd2luZyAxMCBieXRlcyBhcmUgY292ZXJlZCBieSB0aGUgbWFwcGluZyBvbiBwYWNrZXQgMi4g
VGhhdCB3b3VsZCBiZSB2YWxpZC4NCg0KVG8gcmUtaXRlcmF0ZSwgdGhlIHByaW1hcnkgcHVycG9z
ZSBvZiB0aGlzIHByb3Bvc2VkIHRleHQgaXMgdG8gc3RvcCBwZW9wbGUgc2VuZGluZyBtYXBwaW5n
cyBiZWZvcmUgdGhleSBhcmUgbmVlZGVkLg0KDQpCZXN0IHJlZ2FyZHMsDQpBbGFuDQoNCg0KT24g
NCBGZWIgMjAyMCwgYXQgMDc6MzgsIFlvc2hpZnVtaSBOaXNoaWRhIDxuc2QuaWV0ZkBnbWFpbC5j
b208bWFpbHRvOm5zZC5pZXRmQGdtYWlsLmNvbT4+IHdyb3RlOg0KDQpIaSBBbmlsLA0KDQpUaGFu
a3MgZm9yIHBvaW50aW5nIGl0IG91dC4gSSBvdmVybG9va2VkIHRoaXMgb25lLg0KVGhpcyBsb29r
cyBhbiBpbnRlcmVzdGluZyBwb2ludC4NCg0KSXQgc2VlbXMgdG8gbWUgdGhhdCB3aGV0aGVyIFJT
VCBpcyBoYXBwZW4gb3Igbm90IGRlcGVuZHMgb24gdGhlIHNpemUgb2YgcmVjZWl2ZSB3aW5kb3cg
YWNjb3JkaW5nIHRvIHRoZSB0ZXh0Lg0KSWYgdGhlIHJlY2VpdmUgd2luZG93IHNpemUgaXMgYmln
IGVub3VnaCB0byBhY2NvbW1vZGF0ZSBzZWdtZW50IDEgYW5kIHNlZ21lbnQgMywgdGhlIHRleHQg
IkltcGxlbWVudGF0aW9ucyBNQVkgaG9sZCBvbnRvIHN1Y2ggdW5tYXBwZWQgZGF0YSBmb3IgYSBz
aG9ydCB3aGlsZSBpbiB0aGUgZXhwZWN0YXRpb24gdGhhdCBhIG1hcHBpbmcgd2lsbCBhcnJpdmUg
c2hvcnRseS4gIiBjYW4gYmUgYXBwbGllZCB0byB0aGUgc2VnbWVudCAxLiBBcyBhIHJlc3VsdCwg
dGhlIHNlZ21lbnQgMSB3b24ndCBiZSBkaXNjYXJkZWQuDQpIb3dldmVyLCB0aGlzIG1pZ2h0IGJl
IGNvbnRyYWRpY3Qgd2l0aCB0aGUgbmV3IHRleHRzIEFsYW4gcHJvcG9zZWQ/IE9yLCBhbSBJIG1p
c3Npbmcgc29tZXRoaW5nPw0KDQpUaGFua3MsDQotLQ0KWW9zaGkNCg0KDQoNCk9uIFN1biwgRmVi
IDIsIDIwMjAgYXQgODo0MiBBTSBWIEFuaWwgS3VtYXIgPGFuaWxAY3NpcjRwaS5pbjxtYWlsdG86
YW5pbEBjc2lyNHBpLmluPj4gd3JvdGU6DQpIaSBZb3NoaSwNCg0KVGhhbmtzIGZvciB0aGlzIHBv
aW50LiBJbiBmYWN0LCBJIGhhZCBpbml0aWFsbHkgbm90IHRob3VnaHQgb2YgYSBzY2VuYXJpbywg
d2hlcmUgdGhlIG1hcCBpcyBiZWluZyBkZWxpdmVyZWQgdGhyb3VnaCBhIHJldHJhbnNtaXR0ZWQg
ZGF0YSBwYWNrZXQgd2hpbGUgaXRzIGZpcnN0IHRyYW5zbWlzc2lvbiBkaWQgbm90IGluY2x1ZGUg
dGhlIG1hcC4gTm93IEkgYW0ganVzdCBzZWVpbmcgdGhlIGRvY3VtZW50IChSRkMgNjgyNC1iaXMp
IGluIHRoaXMgY29udGV4dC4NCg0KTXkgdW5kZXJzdGFuZGluZyBpcyB0aGF0IGluIHNjZW5hcmlv
cyBsaWtlIHdoYXQgSSBkZXNjcmliZWQgaW4gbXkgcHJldmlvdXMgbWFpbCwgUlNUIGlzIGxpa2Vs
eSB0byBoYXBwZW4gd2hldGhlciB3ZSBleHBsaWNpdGx5IHN0YXRlIHNvIG9yIG5vdC4gUGxlYXNl
IHNlZSB0aGUgcGFyYWdyYXBoIGNvbnRhaW5pbmcgdGhlIGJlbG93IHRleHQgaW4gUkZDIDY4MjQt
YmlzLg0KDQoiSWYgYSBtYXBwaW5nIGZvciB0aGF0IHN1YmZsb3ctbGV2ZWwgc2VxdWVuY2Ugc3Bh
Y2UgZG9lcyBub3QgYXJyaXZlIHdpdGhpbiBhIHJlY2VpdmUgd2luZG93IG9mIGRhdGEsIHRoYXQg
c3ViZmxvdyBTSE9VTEQgYmUgdHJlYXRlZCBhcyBicm9rZW4sIGNsb3NlZCB3aXRoIGEgUlNULCBh
bmQgYW55IHVubWFwcGVkIGRhdGEgc2lsZW50bHkgZGlzY2FyZGVkLiINCg0KaWYgd2UgYXNzdW1l
IHRoYXQgdGhlIG1hcCBpcyBpbmNsdWRlZCB3aGlsZSByZXRyYW5zbWl0dGluZyB0aGUgZGF0YSAo
ZXZlbiB0aG91Z2ggdGhlIGZpcnN0IHRyYW5zbWlzc2lvbiBkaWQgbm90IGNvbnRhaW4gdGhlIG1h
cCBmb3Igc29tZSByZWFzb25zKSwgIHdlIGNvdWxkIGFyZ3VlIHRoYXQgUlNUIGNvdWxkIGJlIGF2
b2lkZWQgcHJvdmlkZWQgdGhhdCB0aGUgcmV0cmFuc21pc3Npb24gaXMgdHJpZ2dlcmVkIHdpdGhp
biBhIHJlY2VpdmUgd2luZG93IG9mIGRhdGEuIEJ1dCB0aGUgcXVlc3Rpb24gaGVyZSB3b3VsZCBi
ZSBob3cgYW5kIHdoZW4gd2lsbCB0aGUgcmV0cmFuc21pc3Npb24gdGFrZSBwbGFjZS4gSW4gdGhp
cyBjYXNlLCB0aGUgc3ViZmxvdyBtYXkgbm90IGluaXRpYXRlIHRoZSByZXRyYW5zbWlzc2lvbiBv
ZiBkYXRhIGJ5IGl0cyBvd24gKGkuZS4sIG5vIHJldHJhbnNtaXNzaW9uIGR1ZSB0byB0aHJlZSBk
dXBsaWNhdGUgQUNLcyBvciBSVE8gZXhwaXJ5IGF0IHN1YmZsb3cgbGV2ZWwpIGFzIHRoZXJlIGlz
IG5vIHNlZ21lbnQgbG9zcyBhdCBzdWJmbG93IGxldmVsIHNlcXVlbmNlIHNwYWNlLiBTbyB0aGVy
ZSBjb3VsZCBiZSBhIGhpZ2ggcG9zc2liaWxpdHkgb2YgUlNUIGhhcHBlbmluZyBldmVuIGJlZm9y
ZSB0aGUgbWFwIGRlbGl2ZXJ5IHRocm91Z2ggcmV0cmFuc21pc3Npb24uDQoNCldpdGggcmVnYXJk
cywNCg0KQW5pbA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogIllv
c2hpZnVtaSBOaXNoaWRhIiA8bnNkLmlldGZAZ21haWwuY29tPG1haWx0bzpuc2QuaWV0ZkBnbWFp
bC5jb20+Pg0KVG86ICJWIEFuaWwgS3VtYXIiIDxhbmlsQGNzaXI0cGkuaW48bWFpbHRvOmFuaWxA
Y3NpcjRwaS5pbj4+DQpDYzogImFsYW4gZm9yZCIgPGFsYW4uZm9yZEBnbWFpbC5jb208bWFpbHRv
OmFsYW4uZm9yZEBnbWFpbC5jb20+PiwgIm11bHRpcGF0aHRjcCIgPG11bHRpcGF0aHRjcEBpZXRm
Lm9yZzxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnPj4NClNlbnQ6IFNhdHVyZGF5LCBGZWJy
dWFyeSAxLCAyMDIwIDM6Mzk6NTEgQU0NClN1YmplY3Q6IFJlOiBbbXVsdGlwYXRodGNwXSBSRkM2
ODI0YmlzIGVkaXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrDQoNCkhpIEFuaWws
DQoNCkkgaGF2ZSBhIHF1ZXN0aW9uIGFib3V0IHlvdXIgcHJvcG9zZWQgdGV4dC4NCkkgYW0gYWN0
dWFsbHkgd29uZGVyaW5nIGlmIHdlIHJlYWxseSB3YW50IHRvIHRlcm1pbmF0ZSBjb25uZWN0aW9u
IGhlcmUuDQoNClRoZSBwYWNrZXRzIHdpdGhvdXQgcHJvcGVyIG1hcHBpbmdzIHdpbGwgYmUgdHJl
YXRlZCBhcyBpbnZhbGlkIGFuZCB3aWxsIGJlIGRpc2NhcmRlZC4NCklmIGFuIGltcGxlbWVudGF0
aW9uIGZhaWxlZCB0byBhdHRhY2ggcHJvcGVyIG1hcHBpbmcgZm9yIHNvbWUgcmVhc29ucyAoZS5n
LiBvcHRpb24gc3BhY2UpLCBpdCBtaWdodCBiZSBhYmxlIHRvIGF0dGFjaCB0aGUgcHJvcGVyIG9u
ZSB3aGVuIGl0IHJldHJhbnNtaXRzIHRoZSBwYWNrZXRzLiBUaGlzIGFsc28gbG9va3Mgb2sgdG8g
bWUuDQoNCkkgZG9uJ3QgaGF2ZSBzdHJvbmcgcHJlZmVyZW5jZSBmb3IgdGhpcy4gQnV0LCBkbyB3
ZSBoYXZlIGEgcmVhc29uIHRvIHRlcm1pbmF0ZSBjb25uZWN0aW9uPw0KDQpUaGFua3MsDQotLQ0K
WW9zaGkNCg0KT24gTW9uLCBKYW4gMTMsIDIwMjAgYXQgMTA6MjggQU0gViBBbmlsIEt1bWFyIDxh
bmlsQGNzaXI0cGkuaW48bWFpbHRvOmFuaWxAY3NpcjRwaS5pbj4+IHdyb3RlOg0KSGksDQoNCkkg
aGF2ZSBzb21lIHBvaW50cyByZWxhdGVkIHRvIHRoZSAgbW9kaWZpY2F0aW9ucyAoQ2hhbmdlIDIp
IGJlaW5nIHByb3Bvc2VkIG9uIGRhdGEgc2VxdWVuY2UgbWFwLiBQbGVhc2Ugc2VlIHRoZW0gaW5s
aW5lLiBUaG91Z2ggSSBhbSBwdXR0aW5nIGZvcndhcmQgdGhlIGJlbG93IHBvaW50cywgaWYgdGhl
IGNvbnNlbnN1cyBpcyBpbiBmYXZvdXIgb2YgdGhlIHByb3Bvc2VkIGNoYW5nZSBmb3IgcmVkdWNp
bmcgaW1wbGVtZW50YXRpb24gY29tcGxleGl0eSwgSSBhbSBhbHNvIE9LIHdpdGggdGhhdCBhcyB3
ZWxsLg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogImFsYW4gZm9y
ZCIgPGFsYW4uZm9yZEBnbWFpbC5jb208bWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5jb20+Pg0KVG86
IG11bHRpcGF0aHRjcEBpZXRmLm9yZzxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnPg0KU2Vu
dDogVGh1cnNkYXksIEphbnVhcnkgMiwgMjAyMCA0OjIxOjMyIEFNDQpTdWJqZWN0OiBbbXVsdGlw
YXRodGNwXSBSRkM2ODI0YmlzIGVkaXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNr
DQoNCkhpIGFsbCwNCldl4oCZZCBsb3ZlIHRvIGdldCB0aGlzIHRvIGEgc3RhdGUgb2YgY29tcGxl
dGlvbiBhcyBzb29uIGFzIHBvc3NpYmxlLCBhbmQgdG8gdGhpcyBlbmQgSSBhbSBzdGFydGluZyBh
IG5ldyB0aHJlYWQgb24gdGhpcyB0b3BpYy4gSW4gZGlzY3Vzc2lvbiB3aXRoIHRoZSBjaGFpcnMs
IGl0IGlzIHBvc3NpYmxlIHRvIG1ha2UgdGhlIGRlc2lyZWQgY2hhbmdlcyBpbiBBVVRINDggYXMg
bG9uZyBhcyB0aGVyZSBpcyBXRyBjb25zZW5zdXMuIFRoZSBkaXNjdXNzaW9uIHNvIGZhciBoYXMg
YmVlbiBmYWlybHkgbGltaXRlZCBpbiB0ZXJtcyBvZiBwYXJ0aWNpcGF0aW9uLg0KDQpJIHdvdWxk
IGFzayB0aGUgY2hhaXJzIHBsZWFzZSBpZiBpdCB3YXMgcG9zc2libGUgdG8gc3BlY2lmeSBhIHRp
bWUgYm91bmQgZm9yIHRoaXMgZGlzY3Vzc2lvbiBhbmQgYSBkZWZhdWx0IGNvbmNsdXNpb24uLg0K
DQpSZWdhcmRpbmcgdGhlIGNoYW5nZXMsIGluIHN1bW1hcnksIHRoZXJlIGFyZSB0d28gYXJlYXMg
d2hlcmUgY2hhbmdlcyBoYXZlIGJlZW4gcmVxdWVzdGVkIGJ5IHRoZSBpbXBsZW1lbnRhdGlvbiBj
b21tdW5pdHkuIEFzIHdlIGFyZSB0aGUgSUVURiB3ZSBvYnZpb3VzbHkgaGF2ZSBzdHJvbmcgZm9j
dXMgb24g4oCccnVubmluZyBjb2Rl4oCdIGFuZCBzbyBlYXNlIG9mIGltcGxlbWVudGluZyBzdGFu
ZGFyZHMtY29tcGxpYW50IGNvZGUgaXMgc3Ryb25nbHkgZGVzaXJhYmxlLiBIb3dldmVyLCB3ZSBk
byBub3Qgd2lzaCB0byByZWR1Y2UgZnVuY3Rpb25hbGl0eSBhZ3JlZWQgYnkgdGhlIElFVEYgY29t
bXVuaXR5IGlmIGl0IGlzIGNvbnNpZGVyZWQgYSByZXF1aXJlZCBmZWF0dXJlIGJ5IHRoZSBjb21t
dW5pdHkuDQoNCkNoYW5nZSAxDQoNCkNoYW5nZSB0aGUgc2VudGVuY2UgcmVhZGluZzoNCg0KICAg
SWYgQiBoYXMgZGF0YSB0byBzZW5kIGZpcnN0LCB0aGVuIHRoZSByZWxpYWJsZSBkZWxpdmVyeSBv
ZiB0aGUgQUNLICsgTVBfQ0FQQUJMRSBjYW4gYmUgaW5mZXJyZWQgYnkgdGhlIHJlY2VpcHQgb2Yg
dGhpcyBkYXRhIHdpdGggYW4gTVBUQ1AgRGF0YSBTZXF1ZW5jZSBTaWduYWwgKERTUykgb3B0aW9u
IChTZWN0aW9uIDMuMykuDQoNClRvOg0KDQogICBJZiBCIGhhcyBkYXRhIHRvIHNlbmQgZmlyc3Qs
IHRoZW4gdGhlIHJlbGlhYmxlIGRlbGl2ZXJ5IG9mIHRoZSBBQ0sgKyBNUF9DQVBBQkxFIGlzIGVu
c3VyZWQgYnkgdGhlIHJlY2VpcHQgb2YgdGhpcyBkYXRhIHdpdGggYW4gTVBUQ1AgRGF0YSBTZXF1
ZW5jZSBTaWduYWwgKERTUykgb3B0aW9uIChTZWN0aW9uIDMuMykgY29udGFpbmluZyBhIERBVEFf
QUNLIGZvciB0aGUgTVBfQ0FQQUJMRSAod2hpY2ggaXMgdGhlIGZpcnN0IG9jdGV0IG9mIHRoZSBk
YXRhIHNlcXVlbmNlIHNwYWNlKS4NCldoYXQgdGhpcyBtZWFuczoNCg0KVGhlIGN1cnJlbnQgdGV4
dCBpcyBjb25jZXJuZWQgb25seSB3aXRoIGVuc3VyaW5nIGEgcGF0aCBpcyBNUFRDUCBjYXBhYmxl
LCBhbmQgc28gb25seSBjYXJlcyB0aGF0IERTUyBvcHRpb24gb2NjdXJzIG9uIGEgZGF0YSBwYWNr
ZXQuIEhvd2V2ZXIsIHRoZSBNUF9DQVBBQkxFIG9wdGlvbiBpcyBkZWZpbmVkIHRvIG9jY3VweSB0
aGUgZmlyc3Qgb2N0ZXQgb2YgZGF0YSBzZXF1ZW5jZSBzcGFjZSBhbmQgdGh1cywgaWYgYW5hbG9n
b3VzIHRvIFRDUCwgbXVzdCBiZSBhY2tub3dsZWRnZWQuID5Gcm9tIGFuIGltcGxlbWVudGF0aW9u
IHBvaW50IG9mIHZpZXcgaXQgd291bGQgbWFrZSBzZW5zZSBub3QgdG8gaGF2ZSB0aGlzIGhhbmdp
bmcgYXJvdW5kIGZvcmV2ZXIgYW5kIGluc3RlYWQgZGVmaW5lIGl0IGlzIGFja25vd2xlZGdlZCBh
dCB0aGUgY29ubmVjdGlvbiBsZXZlbCBhcyBzb29uIGFzIHJlY2VpdmVkLiBUaGlzIGNoYW5nZSBl
bnN1cmVzIHRoZSBmaXJzdCBkYXRhIHBhY2tldCBhbHNvIERBVEFfQUNLcyB0aGlzIE1QX0NBUEFC
TEUgb2N0ZXQuDQoNCkNoYW5nZSAyDQoNCkNoYW5nZSB0aGUgc2VudGVuY2UgcmVhZGluZzoNCg0K
ICAgQSBEYXRhIFNlcXVlbmNlIE1hcHBpbmcgZG9lcyBub3QgbmVlZCB0byBiZSBpbmNsdWRlZCBp
biBldmVyeSBNUFRDUCBwYWNrZXQsIGFzIGxvbmcgYXMgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3Bh
Y2UgaW4gdGhhdCBwYWNrZXQgaXMgY292ZXJlZCBieSBhIG1hcHBpbmcga25vd24gYXQgdGhlIHJl
Y2VpdmVyLi4NCg0KVG86DQoNCiAgIFRoZSBtYXBwaW5nIHByb3ZpZGVkIGJ5IGEgRGF0YSBTZXF1
ZW5jZSBNYXBwaW5nIE1VU1QgYXBwbHkgdG8gc29tZSBvciBhbGwgb2YgdGhlIHN1YmZsb3cgc2Vx
dWVuY2Ugc3BhY2UgaW4gdGhlIFRDUCBzZWdtZW50IHdoaWNoIGNhcnJpZXMgdGhlIG9wdGlvbi4g
SXQgZG9lcyBub3QgbmVlZCB0byBiZSBpbmNsdWRlZCBpbiBldmVyeSBNUFRDUCBwYWNrZXQsIGFz
IGxvbmcgYXMgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2UgaW4gdGhhdCBwYWNrZXQgaXMgY292
ZXJlZCBieSBhIG1hcHBpbmcga25vd24gYXQgdGhlIHJlY2VpdmVyLg0KDQpXaGF0IHRoaXMgbWVh
bnM6DQoNClRoZSBjdXJyZW50IHRleHQgZG9lcyBub3QgcGxhY2UgYW55IHJlc3RyaWN0aW9ucyBv
biB3aGVyZSBhIG1hcHBpbmcgY291bGQgYXBwZWFyLiBJbiB0aGVvcnkgYSBzZW5kZXIgY291bGQg
ZGVmaW5lIGEgdGhvdXNhbmQgZGlmZmVyZW50IG1hcHBpbmdzIHVwIGZyb250LCBzZW5kIHRoZW0g
YWxsLCBhbmQgZXhwZWN0IGEgcmVjZWl2ZXIgdG8gc3RvcmUgdGhpcyBhbmQgcmVhc3NlbWJsZSBk
YXRhIGFjY29yZGluZyB0byB0aGVzZSBtYXBwaW5ncyBhcyBpdCBhcnJpdmVzLiBJbmRlZWQsIHRo
aXMgd2FzIG5ldmVyIGV4cGxpY2l0bHkgZGlzYWxsb3dlZCBzaW5jZSBpdCDigJxtaWdodCBoYXZl
IGJlZW4gdXNlZnVs4oCdLiBUaGUgaW1wbGVtZW50YXRpb24gY29tbXVuaXR5LCBob3dldmVyLCBo
YXMgZXhwcmVzc2VkIGNvbmNlcm5zIG92ZXIgdGhlIGRpZmZpY3VsdHkgb2YgaW1wbGVtZW50aW5n
IHRoaXMgb3Blbi1lbmRlZGx5LiBIb3cgbWFueSBtYXBwaW5ncyBpcyBpdCByZWFzb25hYmxlIHRv
IHN0b3JlPyBJcyB0aGVyZSBhIERvUyByaXNrIGhlcmU/IEluc3RlYWQsIGl0IGhhcyBiZWVuIHJl
cXVlc3RlZCB0aGF0IHRoZWUgc3BlY2lmaWNhdGlvbiByZXN0cmljdHMgdGhlIHBsYWNlbWVudCBv
ZiB0aGUgRFNTIG9wdGlvbiB0byBiZWluZyB3aXRoaW4gdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3Bh
Y2UgdG8gd2hpY2ggaXQgYXBwbGllcy4NCg0KQmVsb3cgYXJlIG15IGNvbW1lbnRzIG9uIHRoaXMu
IEkgaGFkIHNoYXJlZCBzb21lIG9mIHRoZXNlIHBvaW50cyBpbiBhIHByZXZpb3VzIHRocmVhZCB0
aGF0IHlvdSBoYWQgaW5pdGlhdGVkIGluIHRoZSBzYW1lIGNvbnRleHQuDQoNClRyYW5zbWl0dGlu
ZyBsYXJnZSBudW1iZXIgb2Ygbm9uLWNvbnRpZ3VvdXMgZGF0YSBzZXF1ZW5jZSBtYXBzIGNvdWxk
IGJlIGEgbWlzYmVoYXZpb3VyIChtYXAtZmxvb2RpbmcpLCB0aG91Z2ggaXQgaXMgbm90IGNsZWFy
IHdoZXRoZXIgdGhpcyBjYW4gZ28gdG8gdGhlIGV4dGVudCBvZiBjYXVzaW5nIGEgcG90ZW50aWFs
IERvUyB0byB0aGUgZGF0YSByZWNlaXZlci4gU28gc29tZSBzb3J0IG9mIHJlc3RyaWN0aW9uIG9u
IHRoaXMgY291bGQgYmUgdXNlZnVsLiAgT25lIGFwcHJvYWNoIGNvdWxkIGJlIHRvIGluc2lzdCB0
aGF0IHRoZSBkYXRhIHNlbmRlciBzaG91bGQgZW5zdXJlIHRoYXQgdGhlIG1hcCBiZWluZyB0cmFu
c21pdHRlZCBpcyBmb3IgaW4td2luZG93IGRhdGEsIGFzIHBlciB0aGUgcmVjZWl2ZXIgYWR2ZXJ0
aXNlZCB3aW5kb3cuIEEgcmVjZWl2ZXIgc2hvdWxkIGFueWhvdyBiZSB3aWxsaW5nIHRvIHN0b3Jl
IHRoZSBtYXBzIGZvciBpbi13aW5kb3cgZGF0YSB0byBkZWFsIHdpdGggcGFja2V0IGxvc3MuIEZv
ciBleGFtcGxlLCB3aGVuIGEgd2luZG93IG9mIGRhdGEgc2VnbWVudHMgKHNheSAxIHRvIDY0KSBp
cyB0cmFuc21pdHRlZCwgZWFjaCBjYXJyeWluZyBpdHMgY29ycmVzcG9uZGluZyBtYXAsIGFuZCBz
ZWdtZW50LTEgaXMgbG9zdCwgdGhlIG1hcHMgZm9yIHRoZSByZW1haW5pbmcgNjMgbmVlZCB0byBi
ZSBzdG9yZWQgdGlsbCB0aGUgbG9zdCBzZWdtZW50IGlzIHJldHJhbnNtaXR0ZWQuIE9mIGNvdXJz
ZSwgaW4gdGhpcyBjYXNlIHRoZSBtYXBzIHdpbGwgYmUgc3RvcmVkIGF0IHRoZSByZWNlaXZlciBz
aWRlIGFsb25nIHdpdGggdGhlaXIgY29ycmVzcG9uZGluZyBkYXRhLiBCdXQgdGhlIG5lZWQgdG8g
c3RvcmUgbXVsdGlwbGUgbWFwcyBmb3IgaW4td2luZG93IGRhdGEgd291bGQgc3RpbGwgYmUgdGhl
cmUuDQoNClRoZSBwcm9ibGVtIHdpdGggdGhlIHByb3Bvc2VkIGNoYW5nZSAocmVzdHJpY3Rpb24p
IGlzIHRoYXQgYSBkYXRhIHNlbmRlciBtYXkgZmluZCBpdCBkaWZmaWN1bHQsIGluIGNhc2UgYSBu
ZWVkIGFyaXNlIHRvIHNsaWdodGx5IGRlbGF5IHRoZSBtYXAgZGVsaXZlcnkgYnkgZmV3IHNlZ21l
bnRzLCBpLmUuLCBzZW5kaW5nIHNvbWUgZGF0YSBmaXJzdCB3aXRob3V0IG1hcCwgYW5kIHRoZW4g
c2VuZCB0aGUgY29ycmVzcG9uZGluZyBtYXAgaW4gYSBsYXRlciBzZWdtZW50LCBhcyBzaG93biBi
ZWxvdzoNCg0Kc3ViZmxvdy0xOiAgICAgIHNlZ21lbnQtMSAgICAgICAgICAgICAgICAgICBzZWdt
ZW50LTMgICAgICAgICAgICAgICAgICAgIHNlZ21lbnQtNCAgICAgICAgICAgICAgICAgICAgICAg
c2VnbWVudC03DQogICAgICAgICAgICAgICAgICAgICAgYnl0ZXM6MS0xMDAgICAgICAgICAgICAg
ICAgIGJ5dGVzOjIwMS0zMDAgICAgICAgICAgICAgIGJ5dGVzOjMwMS00MDAgICAgICAgICAgICAg
ICAgIGJ5dGVzOjYwMS03MDANCiAgICAgICAgICAgICAgICAgICAgICBubyBtYXAgICAgICAgICAg
ICAgICAgICAgICAgICBtYXAgZm9yIDEtMTAwICAgICAgICAgICAgICBtYXAgZm9yIDIwMS00MDAg
ICAgICAgICAgICAgbWFwIGZvciA2MDEtNzAwDQoNCg0KDQpzdWJmbG93LTI6ICAgICAgIHNlZ21l
bnQtMiAgICAgICAgICAgICAgICAgIHNlZ21lbnQtNSAgICAgICAgICAgICAgICAgICAgIHNlZ21l
bnQtNiAgICAgICAgICAgICAgICAgICAgICAgc2VnbWVudC04DQogICAgICAgICAgICAgICAgICAg
ICAgIGJ5dGVzOiAxMDEtMjAwICAgICAgICAgICBieXRlczo0MDEtNTAwICAgICAgICAgICAgICAg
Ynl0ZXM6IDUwMS02MDAgICAgICAgICAgICAgICAgYnl0ZXM6NzAxLTgwMA0KICAgICAgICAgICAg
ICAgICAgICAgICBtYXAgZm9yIDEwMS0yMDAgICAgICAgbWFwIGZvciA0MDEtNjAwICAgICAgICAg
ICAgbm8gbWFwICAgICAgICAgICAgICAgICAgICAgICAgICAgIG1hcCBmb3IgNzAxLTgwMA0KDQoN
CkluIHRoZSBhYm92ZSBjYXNlLCBzZWdtZW50LTEgZ29lcyB3aXRob3V0IG1hcCBhbmQgaXRzIG1h
cCBpcyBpbmNsdWRlZCBsYXRlciBpbiBzZWdtZW50LTMsIHRoZSBuZXh0IGRhdGEgc2VnbWVudCBp
biB0aGUgc2FtZSBzdWJmbG93LiBGdXJ0aGVyLCAgaW4gdGhlIGFib3ZlIHNjaGVkdWxpbmcgcGF0
dGVybiwgdGhlIG1hcCBpbiBzZWdtZW50LTMgY2Fubm90IGNvdmVyIHRoZSAgZGF0YSBpbiBzZWdt
ZW50LTEgYW5kIHNlZ21lbnQtMywgYXMgc29tZSAgZGF0YSBpbiBiZXR3ZWVuIChzZWdtZW50LTIp
IGlzIHRyYW5zbWl0dGVkIHRocm91Z2ggYW5vdGhlciBzdWJmbG93LiAgV2l0aCB0aGUgcHJvcG9z
ZWQgY2hhbmdlLCB0aGUgbWFwIGluIHNlZ21lbnQtMyB3aWxsIGJlY29tZSBpbnZhbGlkIGFuZCB0
aGlzIHdpbGwgZXZlbnR1YWxseSBicmVhayBzdWJmbG93LTEsIHRob3VnaCB0aGlzIGNvdWxkIGJl
IGEgY29ybmVyIGNhc2UuDQoNClRoZSBxdWVzdGlvbiBhdCB0aGlzIHN0YWdlIGlzIHdoeSB3b3Vs
ZCBzZWdtZW50LTEgYmUgdHJhbnNtaXR0ZWQgd2l0aG91dCBpdHMgbWFwLiBJbiB0aGUgY2FzZSBv
ZiBiaWRpcmVjdGlvbmFsIGRhdGEgdHJhbnNmZXIsIHRoZXJlIGNvdWxkIGJlIGEgbmVlZCB0byBw
YWNrIGJvdGggdGltZXN0YW1wIGFuZCBTQUNLICBvcHRpb25zIGluIGEgZGF0YSBzZWdtZW50LCBp
LmUuLCBwaWdneWJhY2tpbmcgb2YgIFNBQ0sgd2l0aCBkYXRhLiBJZiB3ZSBjb25zaWRlciB0aGF0
IHRpbWVzdGFtcCB0YWtlcyAxMiBieXRlcyBhbmQgU0FDSywgZXZlbiB3aXRoIHNpbmdsZSBibG9j
aywgIHRha2VzIGFub3RoZXIgMTAgYnl0ZXMsIHRoZSByZW1haW5pbmcgMTggYnl0ZXMgb3B0aW9u
IHNwYWNlIGlzIG5vdCBhZGVxdWF0ZSB0byBjYXJyeSBkYXRhIHNlcXVlbmNlIHNpZ25hbCB3aXRo
IG1hcCwgZXNwZWNpYWxseSB3aGVuIERTTiBpcyA2NCBiaXQgbG9uZy4gU28gdGhlIGRlbGl2ZXJ5
IG9mIGVpdGhlciBvZiB0aGUgdHdvIChTQUNLIG9yIG1hcCkgd291bGQgYmUgZGVsYXllZC4NCg0K
QXMgZmFyIGFzIEkgdW5kZXJzdGFuZCwgUkZDIDIwMTggKFRDUCBTZWxlY3RpdmUgQWNrbm93bGVk
Z2VtZW50IE9wdGlvbnMpIGltcGxpZXMgdGhhdCBTQUNLIHNob3VsZCBub3QgYmUgZGVsYXllZC4g
SXQgc3RhdGVzICJJZiBzZW50IGF0IGFsbCwgU0FDSyBvcHRpb25zIFNIT1VMRCBiZSBpbmNsdWRl
ZCBpbiBhbGwgQUNLcyB3aGljaCBkbyBub3QgQUNLIHRoZSBoaWdoZXN0IHNlcXVlbmNlIG51bWJl
ciBpbiB0aGUgZGF0YSByZWNlaXZlcidzIHF1ZXVlIi4gSXQgYWxzbyBzYXlzICJJZiBkYXRhIHJl
Y2VpdmVyIGdlbmVyYXRlcyBTQUNLIG9wdGlvbnMgdW5kZXIgYW55IGNpcmN1bXN0YW5jZSwgaXQg
U0hPVUxEIGdlbmVyYXRlIHRoZW0gdW5kZXIgYWxsIHBlcm1pdHRlZCBjaXJjdW1zdGFuY2VzIi4g
ICBTbywgYXMgcGFydCBvZiBtZWV0aW5nIHRoZSBSRkMgMjAxOCByZXF1aXJlbWVudHMsIGlmIHRo
ZSBjb21iaW5hdGlvbiBvZiBTQUNLIGFuZCB0aW1lc3RhbXAgaXMgZ2l2ZW4gcHJlZmVyZW5jZSBv
dmVyIERTUywgZGF0YSBzZWdtZW50cyBjb3VsZCBiZSB0cmFuc21pdHRlZCB3aXRob3V0IHRoZWly
IG1hcC4NCg0KQW5vdGhlciBjYXNlIG9mIGRlbGF5aW5nIG1hcCBjb3VsZCBhcmlzZSBpZiB0aGUg
ZGF0YSBzZW5kZXIgcHJlZmVycyB0byBzZW5kIEFERF9BRERSIG9wdGlvbiwgaW5zdGVhZCBvZiBt
YXAsIGluIGEgZGF0YSBzZWdtZW50LiBJdCBpcyBuaWNlIHRoYXQgQUREX0FERFIgb3B0aW9uIGNh
biBiZSBkZWxpdmVyZWQgcmVsaWFibHkgaW4gYSBwdXJlIEFDSywgYnV0IEkgdGhpbmsgdGhpcyBp
cyBub3QgdGhlIGNhc2Ugd2l0aCBEU1MgYXQgcHJlc2VudC4NCg0KSWYgd2UgYWRvcHQgdGhlIHBy
b3Bvc2VkIGNoYW5nZSwgSSB0aGluayBpdCBtaWdodCBhbHNvIGJlIGhlbHBmdWwgdG8gc3BlbGwg
b3V0IGhvdyB0aGUgcmVjZWl2ZXIgaXMgc3VwcG9zZWQgdG8gYmVoYXZlLCBpZiBpdCBnZXRzIG1h
cHMgbm90IG1lZXRpbmcgdGhlIE1VU1QgY29uZGl0aW9uIGluIHRoZSBwcm9wb3NlZCBjaGFuZ2Uu
ICBGb3IgZXhhbXBsZSB0ZXJtaW5hdGlvbiBvZiB0aGUgc3ViZmxvdyB3aXRoIE1QX1RDUFJTVCBv
cHRpb24gKHNlY3Rpb24gMy42IGluIFJGQyA2ODI0LWJpcykgd2l0aCBhcHByb3ByaWF0ZSByZWFz
b24gY29kZSBhbmQgVCBmbGFnIHZhbHVlIHRvIGludGltYXRlIHRoZSBkYXRhIHNlbmRlciB0aGUg
Y2F1c2UgZm9yIHN1YmZsb3cgdGVybWluYXRpb24uDQoNCldpdGggcmVnYXJkcywNCg0KQW5pbA0K
UGxlYXNlIGNhbiBtZW1iZXJzIG9mIHRoZSBXRyBleHByZXNzIHdoZXRoZXIgdGhleSBhcmUgaGFw
cHkgd2l0aCB0aGVzZSBjaGFuZ2VzLCBvciBjb25jZXJuZWQuDQoNCkJlc3QgcmVnYXJkcywNCkFs
YW4NCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
bXVsdGlwYXRodGNwIG1haWxpbmcgbGlzdA0KbXVsdGlwYXRodGNwQGlldGYub3JnPG1haWx0bzpt
dWx0aXBhdGh0Y3BAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL211bHRpcGF0aHRjcA0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCm11bHRpcGF0aHRjcCBtYWlsaW5nIGxpc3QNCm11bHRpcGF0aHRjcEBp
ZXRmLm9yZzxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3ANCg0KDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIg
MTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlNlZ29lIFVJ
IjsNCglwYW5vc2UtMToyIDExIDUgMiA0IDIgNCAyIDIgMzt9DQovKiBTdHlsZSBEZWZpbml0aW9u
cyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46
MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7
bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1h
cmdpbi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxl
ZnQ6MGNtOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMt
c2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJ
Zm9udC1mYW1pbHk6IkFyaWFsIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250
LWZhbWlseToiQXJpYWwiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hw
RGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBX
b3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4w
cHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRz
IHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1h
cCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRp
Zl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVy
cGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0idmVydGljYWwtYWxpZ246YmFzZWxpbmUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5U
cnlpbmcgdG8gc3VtbWFyaXNlIOKAkyBpZiBJIGdldCB0aGUgZGlzY3Vzc2lvbiByaWdodCwgaXQg
c2VlbXMgdGhhdCB0aGUg4oCcQ2hhbmdlIDLigJ0gdGV4dCBwcm9wb3NlZCBpbiBBbGFu4oCZcyBl
bWFpbCBpcyBPSyBhbmQgdGhhdCB0aGUgdGV4dA0KIHRoZXJlIGFuZCBlbHNld2hlcmUgaXMgc3Vm
ZmljaWVudC4gPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9InZlcnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InZl
cnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+TWF0dCDigJMg
dGhhbmtzIGZvciB5b3VyIGVtYWlsLCBpdOKAmXMgdmVyeSBnb29kIHRvIGtub3cgdGhhdCB0aGUg
Y2hhbmdlcyBhcmUgaW1wb3J0YW50IGZyb20gdGhlIGltcGxlbWVudGVycyBwb2ludCBvZiB2aWV3
IOKAkyBhbmQgdGhhbmtzDQogZm9yIGFsbCB5b3UgJmFtcDsgeW91ciBjb2xsZWFndWVzIGVmZm9y
dHMgb24gYm90aCB0aGUgaW50ZXJuZXQgZHJhZnQgbGludXggYW5kIHRoZSB1cHN0cmVhbSBvbmUg
KG5lYXJseSBpbiBtYWlubGluZT8pPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9InZlcnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9InZlcnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+QmVzdCB3aXNoZXMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9InZlcnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+cGhpbDwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjcuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzdGN0Y3RiI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFu
IGxhbmc9IkVOLVVTIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiBtdWx0aXBh
dGh0Y3AgJmx0O211bHRpcGF0aHRjcC1ib3VuY2VzQGlldGYub3JnJmd0Ow0KPGI+T24gQmVoYWxm
IE9mIDwvYj5Zb3NoaWZ1bWkgTmlzaGlkYTxicj4NCjxiPlNlbnQ6PC9iPiAwNSBGZWJydWFyeSAy
MDIwIDA4OjUxPGJyPg0KPGI+VG86PC9iPiBBbGFuIEZvcmQgJmx0O2FsYW4uZm9yZEBnbWFpbC5j
b20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBtdWx0aXBhdGh0Y3AgJmx0O211bHRpcGF0aHRjcEBpZXRm
Lm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFttdWx0aXBhdGh0Y3BdIFJGQzY4MjRi
aXMgZWRpdHMgYmFzZWQgb24gaW1wbGVtZW50YXRpb24gZmVlZGJhY2s8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkgQWxhbiw8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+WWVzLCBpdCBtYWtlcyBzZW5zZS4u
IFRoYW5rcyBmb3IgdGhlIGNsYXJpZmljYXRpb24uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkJUVywgSSBkb24ndCBoYXZlIGEgc3Ryb25nIG9w
aW5pb24gYWJvdXQgd2hldGhlciZuYnNwO3dlIHNob3VsZCBhZGQgc29tZSB0ZXh0cyB0byBzZW5k
IFJTVCBmb3IgbWFwcGluZyBpc3N1ZSBjYXNlIG9yIHRoZSB0ZXh0IGluIHRoZSBkcmFmdCBBbmls
IHBvaW50ZWQgb3V0IGlzIGFscmVhZHkgZW5vdWdoLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SG93ZXZlciwgaWYgd2Ugd2FudCB0byBhZGQgbmV3
IHRleHRzLCBJIHRoaW5rIFNIT1VMRCB3aWxsIGJlIHByZWZlcmFibGUgYXMgaXQgd29uJ3QgY29u
dHJhZGljdCB3aXRoIHRoZSB0ZXh0cyBpbiB0aGUgZHJhZnQuJm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JZiB3ZSBzZXR0bGUgdGhpcywg
SSB0aGluayB0aGUgZG9jIGlzIHJlYWR5IHRvIGJyaW5nIGl0IGJhY2sgdG8gQVVUSDQ4LjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3Ms
Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4tLTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
WW9zaGkmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
Pk9uIFR1ZSwgRmViIDQsIDIwMjAgYXQgNDoxMiBBTSBBbGFuIEZvcmQgJmx0OzxhIGhyZWY9Im1h
aWx0bzphbGFuLmZvcmRAZ21haWwuY29tIj5hbGFuLmZvcmRAZ21haWwuY29tPC9hPiZndDsgd3Jv
dGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4w
cHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+SGkgWW9zaGksPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5UaGUgcHJvcG9zZWQgbmV3IHRleHQgZW5mb3JjZXMgYSBtYXBwaW5nIHRvIGJl
IHNlbnQgb24gYSBwYWNrZXQgd2hvc2Ugc3ViZmxvdyBzZXF1ZW5jZSBudW1iZXIgaXMgaW5jbHVk
ZWQgd2l0aGluIHRoZSBtYXBwaW5nIHByb3ZpZGVkLiBUaGlzIGRvZXMgbm90IGRpcmVjdGx5IGNv
bnRyYWRpY3Qgd2l0aCB0aGUgTUFZIGNhc2UuIEluZGVlZCB0aGlzIHNjZW5hcmlvIGNvdWxkIGVh
c2lseSBoYXBwZW4gaWYgdGhlcmUNCiBpcyBhIDIwIGJ5dGUgcGFja2V0IGZvbGxvd2VkIGJ5IGEg
MTAgYnl0ZSBwYWNrZXQuIFRoZSBmaXJzdCAxMCBieXRlcyBvZiB0aGUgZmlyc3QgcGFja2V0IGFy
ZSBjb3ZlcmVkIGJ5IHRoZSBtYXBwaW5nIG9uIHBhY2tldCAxLCB0aGVuIHRoZSByZW1haW5pbmcg
MTAgYnl0ZXMgYW5kIHRoZSBmb2xsb3dpbmcgMTAgYnl0ZXMgYXJlIGNvdmVyZWQgYnkgdGhlIG1h
cHBpbmcgb24gcGFja2V0IDIuIFRoYXQgd291bGQgYmUgdmFsaWQuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRvIHJlLWl0ZXJhdGUsIHRoZSBw
cmltYXJ5IHB1cnBvc2Ugb2YgdGhpcyBwcm9wb3NlZCB0ZXh0IGlzIHRvIHN0b3AgcGVvcGxlIHNl
bmRpbmcgbWFwcGluZ3MgYmVmb3JlIHRoZXkgYXJlIG5lZWRlZC48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QmVzdCByZWdhcmRzLDxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWxhbjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4N
Cjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4w
cHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24g
NCBGZWIgMjAyMCwgYXQgMDc6MzgsIFlvc2hpZnVtaSBOaXNoaWRhICZsdDs8YSBocmVmPSJtYWls
dG86bnNkLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+bnNkLmlldGZAZ21haWwuY29t
PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBBbmlsLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MgZm9yIHBvaW50aW5nIGl0IG91
dC4gSSBvdmVybG9va2VkIHRoaXMgb25lLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhpcyBsb29rcyBhbiBpbnRlcmVzdGluZyBwb2ludC48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SXQgc2Vl
bXMgdG8gbWUgdGhhdCB3aGV0aGVyIFJTVCBpcyBoYXBwZW4gb3Igbm90IGRlcGVuZHMgb24gdGhl
IHNpemUgb2YgcmVjZWl2ZSB3aW5kb3cgYWNjb3JkaW5nIHRvIHRoZSB0ZXh0LjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SWYgdGhlIHJlY2VpdmUg
d2luZG93IHNpemUgaXMgYmlnIGVub3VnaCB0byBhY2NvbW1vZGF0ZSZuYnNwO3NlZ21lbnQgMSBh
bmQgc2VnbWVudCAzLCB0aGUgdGV4dCAmcXVvdDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dCI+SW1wbGVtZW50YXRpb25zIE1BWSBob2xkIG9udG8gc3VjaCB1bm1hcHBlZCBkYXRhIGZvciBh
IHNob3J0IHdoaWxlIGluJm5ic3A7dGhlIGV4cGVjdGF0aW9uIHRoYXQgYSBtYXBwaW5nIHdpbGwg
YXJyaXZlIHNob3J0bHkuDQogJnF1b3Q7Jm5ic3A7PC9zcGFuPmNhbiBiZSBhcHBsaWVkIHRvIHRo
ZSBzZWdtZW50IDEuIEFzIGEgcmVzdWx0LCB0aGUgc2VnbWVudCAxIHdvbid0IGJlIGRpc2NhcmRl
ZC4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkhvd2V2ZXIsIHRoaXMgbWlnaHQgYmUgY29udHJhZGljdCB3aXRoIHRoZSBuZXcgdGV4dHMg
QWxhbiBwcm9wb3NlZD8gT3IsIGFtIEkgbWlzc2luZyBzb21ldGhpbmc/PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyw8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0tPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Zb3NoaTxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFN1biwgRmViIDIsIDIw
MjAgYXQgODo0MiBBTSBWIEFuaWwgS3VtYXIgJmx0OzxhIGhyZWY9Im1haWx0bzphbmlsQGNzaXI0
cGkuaW4iIHRhcmdldD0iX2JsYW5rIj5hbmlsQGNzaXI0cGkuaW48L2E+Jmd0OyB3cm90ZTo8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJn
aW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkhpIFlvc2hpLDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VGhhbmtzIGZvciB0aGlzIHBvaW50LiBJ
biBmYWN0LCBJIGhhZCBpbml0aWFsbHkgbm90IHRob3VnaHQgb2YgYSBzY2VuYXJpbywgd2hlcmUg
dGhlIG1hcCBpcyBiZWluZyBkZWxpdmVyZWQgdGhyb3VnaCBhIHJldHJhbnNtaXR0ZWQgZGF0YSBw
YWNrZXQgd2hpbGUgaXRzIGZpcnN0IHRyYW5zbWlzc2lvbiBkaWQgbm90IGluY2x1ZGUgdGhlDQog
bWFwLiBOb3cgSSBhbSBqdXN0IHNlZWluZyB0aGUgZG9jdW1lbnQgKFJGQyA2ODI0LWJpcykgaW4g
dGhpcyBjb250ZXh0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMt
c2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZiI+TXkgdW5kZXJzdGFuZGluZyBpcyB0aGF0IGluIHNjZW5hcmlvcyBsaWtlIHdoYXQgSSBk
ZXNjcmliZWQgaW4gbXkgcHJldmlvdXMgbWFpbCwgUlNUIGlzIGxpa2VseSB0byBoYXBwZW4gd2hl
dGhlciB3ZSBleHBsaWNpdGx5IHN0YXRlIHNvIG9yIG5vdC4gUGxlYXNlIHNlZSB0aGUgcGFyYWdy
YXBoIGNvbnRhaW5pbmcgdGhlIGJlbG93IHRleHQNCiBpbiBSRkMgNjgyNC1iaXMuICZuYnNwOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+JnF1b3Q7SWYg
YSBtYXBwaW5nIGZvciB0aGF0IHN1YmZsb3ctbGV2ZWwgc2VxdWVuY2Ugc3BhY2UgZG9lcyBub3Qg
YXJyaXZlIHdpdGhpbiBhIHJlY2VpdmUgd2luZG93IG9mIGRhdGEsIHRoYXQgc3ViZmxvdyBTSE9V
TEQgYmUgdHJlYXRlZCBhcyBicm9rZW4sIGNsb3NlZCB3aXRoIGEgUlNULCBhbmQgYW55IHVubWFw
cGVkIGRhdGEgc2lsZW50bHkNCiBkaXNjYXJkZWQuJnF1b3Q7PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5pZiB3ZSBhc3N1bWUgdGhhdCB0aGUgbWFwIGlz
IGluY2x1ZGVkIHdoaWxlIHJldHJhbnNtaXR0aW5nIHRoZSBkYXRhIChldmVuIHRob3VnaCB0aGUg
Zmlyc3QgdHJhbnNtaXNzaW9uIGRpZCBub3QgY29udGFpbiB0aGUgbWFwIGZvciBzb21lIHJlYXNv
bnMpLCAmbmJzcDt3ZSBjb3VsZCBhcmd1ZSB0aGF0IFJTVCBjb3VsZCBiZSBhdm9pZGVkIHByb3Zp
ZGVkDQogdGhhdCB0aGUgcmV0cmFuc21pc3Npb24gaXMgdHJpZ2dlcmVkIHdpdGhpbiBhIHJlY2Vp
dmUgd2luZG93IG9mIGRhdGEuIEJ1dCB0aGUgcXVlc3Rpb24gaGVyZSB3b3VsZCBiZSBob3cgYW5k
IHdoZW4gd2lsbCB0aGUgcmV0cmFuc21pc3Npb24gdGFrZSBwbGFjZS4gSW4gdGhpcyBjYXNlLCB0
aGUgc3ViZmxvdyBtYXkgbm90IGluaXRpYXRlIHRoZSByZXRyYW5zbWlzc2lvbiBvZiBkYXRhIGJ5
IGl0cyBvd24gKGkuZS4sIG5vIHJldHJhbnNtaXNzaW9uDQogZHVlIHRvIHRocmVlIGR1cGxpY2F0
ZSBBQ0tzIG9yIFJUTyBleHBpcnkgYXQgc3ViZmxvdyBsZXZlbCkgYXMgdGhlcmUgaXMgbm8gc2Vn
bWVudCBsb3NzIGF0IHN1YmZsb3cgbGV2ZWwgc2VxdWVuY2Ugc3BhY2UuIFNvIHRoZXJlIGNvdWxk
IGJlIGEgaGlnaCBwb3NzaWJpbGl0eSBvZiBSU1QgaGFwcGVuaW5nIGV2ZW4gYmVmb3JlIHRoZSBt
YXAgZGVsaXZlcnkgdGhyb3VnaCByZXRyYW5zbWlzc2lvbi4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPldpdGggcmVnYXJkcywmbmJzcDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkFuaWw8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJNc29Ob3JtYWwiIGFs
aWduPSJjZW50ZXIiIHN0eWxlPSJ0ZXh0LWFsaWduOmNlbnRlciI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPg0KPGhyIHNpemU9IjIiIHdpZHRo
PSIxMDAlIiBhbGlnbj0iY2VudGVyIiBpZD0iZ21haWwtbV80MjIxMTY2NjgyMDgyMjkwMDQ3Z21h
aWwtbV8yMTgwODY1OTY5NTE3MjQ1MDFnbWFpbC1tXzI5ODIyNjcwMzM1Nzc5MDI5ODV6d2NociI+
DQo8L3NwYW4+PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206IDwvc3Bh
bj4NCjwvYj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZiI+JnF1b3Q7WW9zaGlmdW1pIE5pc2hpZGEmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpu
c2QuaWV0ZkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5uc2QuaWV0ZkBnbWFpbC5jb208L2E+
Jmd0Ozxicj4NCjxiPlRvOiA8L2I+JnF1b3Q7ViBBbmlsIEt1bWFyJnF1b3Q7ICZsdDs8YSBocmVm
PSJtYWlsdG86YW5pbEBjc2lyNHBpLmluIiB0YXJnZXQ9Il9ibGFuayI+YW5pbEBjc2lyNHBpLmlu
PC9hPiZndDs8YnI+DQo8Yj5DYzogPC9iPiZxdW90O2FsYW4gZm9yZCZxdW90OyAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5hbGFuLmZvcmRA
Z21haWwuY29tPC9hPiZndDssICZxdW90O211bHRpcGF0aHRjcCZxdW90OyAmbHQ7PGEgaHJlZj0i
bWFpbHRvOm11bHRpcGF0aHRjcEBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm11bHRpcGF0aHRj
cEBpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U2VudDogPC9iPlNhdHVyZGF5LCBGZWJydWFyeSAx
LCAyMDIwIDM6Mzk6NTEgQU08YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IFttdWx0aXBhdGh0Y3Bd
IFJGQzY4MjRiaXMgZWRpdHMgYmFzZWQgb24gaW1wbGVtZW50YXRpb24gZmVlZGJhY2s8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmIj5IaSBBbmlsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssc2Fucy1zZXJpZiI+SSBoYXZlIGEgcXVlc3Rpb24gYWJvdXQgeW91ciBwcm9wb3NlZCB0ZXh0
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZiI+SSBhbSBhY3R1YWxseSB3b25kZXJpbmcgaWYgd2UgcmVhbGx5IHdhbnQgdG8gdGVy
bWluYXRlIGNvbm5lY3Rpb24gaGVyZS4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VGhlIHBhY2tldHMgd2l0aG91dCBwcm9wZXIg
bWFwcGluZ3Mgd2lsbCBiZSB0cmVhdGVkIGFzIGludmFsaWQgYW5kIHdpbGwgYmUgZGlzY2FyZGVk
LiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj5JZiBhbiBpbXBsZW1lbnRhdGlvbiBmYWlsZWQgdG8gYXR0YWNoIHByb3BlciBtYXBw
aW5nIGZvciBzb21lIHJlYXNvbnMgKGUuZy4gb3B0aW9uIHNwYWNlKSwgaXQgbWlnaHQgYmUgYWJs
ZSB0byBhdHRhY2ggdGhlIHByb3BlciBvbmUgd2hlbiBpdCByZXRyYW5zbWl0cyB0aGUgcGFja2V0
cy4gVGhpcyBhbHNvIGxvb2tzIG9rIHRvIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZiI+SSBkb24ndCBoYXZlIHN0cm9uZyBwcmVmZXJlbmNlIGZvciB0
aGlzLiBCdXQsIGRvIHdlIGhhdmUgYSByZWFzb24gdG8gdGVybWluYXRlIGNvbm5lY3Rpb24/PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UaGFua3MsPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPi0t
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
Pllvc2hpPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZiI+T24gTW9uLCBKYW4gMTMsIDIwMjAgYXQgMTA6MjggQU0gViBBbmlsIEt1bWFyICZsdDs8
YSBocmVmPSJtYWlsdG86YW5pbEBjc2lyNHBpLmluIiB0YXJnZXQ9Il9ibGFuayI+YW5pbEBjc2ly
NHBpLmluPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBw
dDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdo
dDowY20iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj5IaSw8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj5JIGhhdmUgc29tZSBwb2ludHMgcmVsYXRlZCB0byB0aGUg
Jm5ic3A7bW9kaWZpY2F0aW9ucyAoQ2hhbmdlIDIpIGJlaW5nIHByb3Bvc2VkIG9uIGRhdGEgc2Vx
dWVuY2UgbWFwLiBQbGVhc2Ugc2VlIHRoZW0gaW5saW5lLiZuYnNwOzwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOmJsYWNrO2JhY2tncm91bmQ6d2hpdGUiPlRob3VnaA0KIEkgYW0gcHV0dGluZyBm
b3J3YXJkIHRoZSBiZWxvdyBwb2ludHMsIGlmIHRoZSBjb25zZW5zdXMgaXMgaW4gZmF2b3VyIG9m
IHRoZSBwcm9wb3NlZCBjaGFuZ2UgZm9yIHJlZHVjaW5nIGltcGxlbWVudGF0aW9uIGNvbXBsZXhp
dHksIEkgYW0gYWxzbyBPSyB3aXRoIHRoYXQgYXMgd2VsbC4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXYgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImNlbnRlciIgc3R5bGU9
InRleHQtYWxpZ246Y2VudGVyIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZiI+DQo8aHIgc2l6ZT0iMiIgd2lkdGg9IjEwMCUiIGFsaWduPSJjZW50
ZXIiIGlkPSJnbWFpbC1tXzQyMjExNjY2ODIwODIyOTAwNDdnbWFpbC1tXzIxODA4NjU5Njk1MTcy
NDUwMWdtYWlsLW1fMjk4MjI2NzAzMzU3NzkwMjk4NWdtYWlsLW1fNzY4NzE4NDM4MjI5OTU5Njc3
NHp3Y2hyIj4NCjwvc3Bhbj48L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+RnJv
bTogPC9zcGFuPg0KPC9iPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmIj4mcXVvdDthbGFuIGZvcmQmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzph
bGFuLmZvcmRAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+YWxhbi5mb3JkQGdtYWlsLmNvbTwv
YT4mZ3Q7PGJyPg0KPGI+VG86IDwvYj48YSBocmVmPSJtYWlsdG86bXVsdGlwYXRodGNwQGlldGYu
b3JnIiB0YXJnZXQ9Il9ibGFuayI+bXVsdGlwYXRodGNwQGlldGYub3JnPC9hPjxicj4NCjxiPlNl
bnQ6IDwvYj5UaHVyc2RheSwgSmFudWFyeSAyLCAyMDIwIDQ6MjE6MzIgQU08YnI+DQo8Yj5TdWJq
ZWN0OiA8L2I+W211bHRpcGF0aHRjcF0gUkZDNjgyNGJpcyBlZGl0cyBiYXNlZCBvbiBpbXBsZW1l
bnRhdGlvbiBmZWVkYmFjazxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZiI+SGkgYWxsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZiI+V2XigJlkIGxvdmUgdG8gZ2V0IHRoaXMgdG8gYSBzdGF0ZSBvZiBjb21wbGV0aW9u
IGFzIHNvb24gYXMgcG9zc2libGUsIGFuZCB0byB0aGlzIGVuZCBJIGFtIHN0YXJ0aW5nIGEgbmV3
IHRocmVhZCBvbiB0aGlzIHRvcGljLiBJbiBkaXNjdXNzaW9uIHdpdGggdGhlIGNoYWlycywgaXQN
CjxpPmlzIDwvaT5wb3NzaWJsZSB0byBtYWtlIHRoZSBkZXNpcmVkIGNoYW5nZXMgaW4gQVVUSDQ4
IGFzIGxvbmcgYXMgdGhlcmUgaXMgV0cgY29uc2Vuc3VzLiBUaGUgZGlzY3Vzc2lvbiBzbyBmYXIg
aGFzIGJlZW4gZmFpcmx5IGxpbWl0ZWQgaW4gdGVybXMgb2YgcGFydGljaXBhdGlvbi48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkkgd291bGQgYXNrIHRo
ZSBjaGFpcnMgcGxlYXNlIGlmIGl0IHdhcyBwb3NzaWJsZSB0byBzcGVjaWZ5IGEgdGltZSBib3Vu
ZCBmb3IgdGhpcyBkaXNjdXNzaW9uIGFuZCBhIGRlZmF1bHQgY29uY2x1c2lvbi4uPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5SZWdhcmRpbmcgdGhlIGNo
YW5nZXMsIGluIHN1bW1hcnksIHRoZXJlIGFyZSB0d28gYXJlYXMgd2hlcmUgY2hhbmdlcyBoYXZl
IGJlZW4gcmVxdWVzdGVkIGJ5IHRoZSBpbXBsZW1lbnRhdGlvbiBjb21tdW5pdHkuIEFzIHdlIGFy
ZSB0aGUgSUVURiB3ZSBvYnZpb3VzbHkgaGF2ZSBzdHJvbmcgZm9jdXMgb24g4oCccnVubmluZyBj
b2Rl4oCdIGFuZA0KIHNvIGVhc2Ugb2YgaW1wbGVtZW50aW5nIHN0YW5kYXJkcy1jb21wbGlhbnQg
Y29kZSBpcyBzdHJvbmdseSBkZXNpcmFibGUuIEhvd2V2ZXIsIHdlIGRvIG5vdCB3aXNoIHRvIHJl
ZHVjZSBmdW5jdGlvbmFsaXR5IGFncmVlZCBieSB0aGUgSUVURiBjb21tdW5pdHkgaWYgaXQgaXMg
Y29uc2lkZXJlZCBhIHJlcXVpcmVkIGZlYXR1cmUgYnkgdGhlIGNvbW11bml0eS48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
Ym90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssc2Fucy1zZXJpZiI+Q2hhbmdlIDE8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1i
b3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZiI+Q2hhbmdlIHRoZSBzZW50ZW5jZSByZWFkaW5nOjxicj4NCjxicj4NCjxpPiZu
YnNwOyAmbmJzcDtJZiBCIGhhcyBkYXRhIHRvIHNlbmQgZmlyc3QsIHRoZW4gdGhlIHJlbGlhYmxl
IGRlbGl2ZXJ5IG9mIHRoZSBBQ0sgJiM0MzsgTVBfQ0FQQUJMRSBjYW4gYmUgaW5mZXJyZWQgYnkg
dGhlIHJlY2VpcHQgb2YgdGhpcyBkYXRhIHdpdGggYW4gTVBUQ1AgRGF0YSBTZXF1ZW5jZSBTaWdu
YWwgKERTUykgb3B0aW9uIChTZWN0aW9uIDMuMykuJm5ic3A7PGJyPg0KPC9pPjxicj4NClRvOjxi
cj4NCjxicj4NCjxpPiZuYnNwOyAmbmJzcDtJZiBCIGhhcyBkYXRhIHRvIHNlbmQgZmlyc3QsIHRo
ZW4gdGhlIHJlbGlhYmxlIGRlbGl2ZXJ5IG9mIHRoZSBBQ0sgJiM0MzsgTVBfQ0FQQUJMRSBpcyBl
bnN1cmVkIGJ5IHRoZSByZWNlaXB0IG9mIHRoaXMgZGF0YSB3aXRoIGFuIE1QVENQIERhdGEgU2Vx
dWVuY2UgU2lnbmFsIChEU1MpIG9wdGlvbiAoU2VjdGlvbiAzLjMpIGNvbnRhaW5pbmcgYSBEQVRB
X0FDSyBmb3IgdGhlIE1QX0NBUEFCTEUgKHdoaWNoIGlzIHRoZSBmaXJzdCBvY3RldCBvZg0KIHRo
ZSBkYXRhIHNlcXVlbmNlJm5ic3A7c3BhY2UpLjwvaT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+V2hhdCB0aGlzIG1lYW5zOjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VGhlIGN1cnJlbnQgdGV4
dCBpcyBjb25jZXJuZWQgb25seSB3aXRoIGVuc3VyaW5nIGEgcGF0aCBpcyBNUFRDUCBjYXBhYmxl
LCBhbmQgc28gb25seSBjYXJlcyB0aGF0IERTUyBvcHRpb24gb2NjdXJzIG9uIGEgZGF0YSBwYWNr
ZXQuIEhvd2V2ZXIsIHRoZSBNUF9DQVBBQkxFIG9wdGlvbiBpcyBkZWZpbmVkIHRvIG9jY3VweSB0
aGUgZmlyc3QNCiBvY3RldCBvZiBkYXRhIHNlcXVlbmNlIHNwYWNlIGFuZCB0aHVzLCBpZiBhbmFs
b2dvdXMgdG8gVENQLCBtdXN0IGJlIGFja25vd2xlZGdlZC4gJmd0O0Zyb20gYW4gaW1wbGVtZW50
YXRpb24gcG9pbnQgb2YgdmlldyBpdCB3b3VsZCBtYWtlIHNlbnNlIG5vdCB0byBoYXZlIHRoaXMg
aGFuZ2luZyBhcm91bmQgZm9yZXZlciBhbmQgaW5zdGVhZCBkZWZpbmUgaXQgaXMgYWNrbm93bGVk
Z2VkIGF0IHRoZSBjb25uZWN0aW9uIGxldmVsIGFzIHNvb24gYXMgcmVjZWl2ZWQuDQogVGhpcyBj
aGFuZ2UgZW5zdXJlcyB0aGUgZmlyc3QgZGF0YSBwYWNrZXQgYWxzbyBEQVRBX0FDS3MgdGhpcyBN
UF9DQVBBQkxFIG9jdGV0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5DaGFuZ2UgMjwvc3Bhbj48
L2I+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZiI+Q2hhbmdlIHRoZSBzZW50ZW5jZSByZWFkaW5nOjxicj4NCjxicj4NCjxpPiZuYnNw
OyAmbmJzcDtBIERhdGEgU2VxdWVuY2UgTWFwcGluZyBkb2VzIG5vdCBuZWVkIHRvIGJlIGluY2x1
ZGVkIGluIGV2ZXJ5IE1QVENQIHBhY2tldCwgYXMgbG9uZyBhcyB0aGUgc3ViZmxvdyBzZXF1ZW5j
ZSBzcGFjZSBpbiB0aGF0IHBhY2tldCBpcyBjb3ZlcmVkIGJ5IGEgbWFwcGluZyBrbm93biBhdCB0
aGUgcmVjZWl2ZXIuLjwvaT48YnI+DQo8YnI+DQpUbzo8YnI+DQo8YnI+DQo8aT4mbmJzcDsgJm5i
c3A7VGhlIG1hcHBpbmcgcHJvdmlkZWQgYnkgYSBEYXRhIFNlcXVlbmNlIE1hcHBpbmcgTVVTVCBh
cHBseSB0byBzb21lIG9yIGFsbCBvZiB0aGUgc3ViZmxvdyBzZXF1ZW5jZSBzcGFjZSBpbiB0aGUg
VENQIHNlZ21lbnQgd2hpY2ggY2FycmllcyB0aGUgb3B0aW9uLiBJdCBkb2VzIG5vdCBuZWVkIHRv
IGJlIGluY2x1ZGVkIGluIGV2ZXJ5IE1QVENQIHBhY2tldCwgYXMgbG9uZyBhcyB0aGUgc3ViZmxv
dyBzZXF1ZW5jZSBzcGFjZSBpbiB0aGF0IHBhY2tldA0KIGlzIGNvdmVyZWQgYnkgYSBtYXBwaW5n
IGtub3duIGF0IHRoZSByZWNlaXZlci48YnI+DQo8L2k+PGJyPg0KV2hhdCB0aGlzIG1lYW5zOjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VGhlIGN1cnJl
bnQgdGV4dCBkb2VzIG5vdCBwbGFjZSBhbnkgcmVzdHJpY3Rpb25zIG9uIHdoZXJlIGEgbWFwcGlu
ZyBjb3VsZCBhcHBlYXIuIEluIHRoZW9yeSBhIHNlbmRlciBjb3VsZCBkZWZpbmUgYSB0aG91c2Fu
ZCBkaWZmZXJlbnQgbWFwcGluZ3MgdXAgZnJvbnQsIHNlbmQgdGhlbSBhbGwsIGFuZCBleHBlY3Qg
YSByZWNlaXZlcg0KIHRvIHN0b3JlIHRoaXMgYW5kIHJlYXNzZW1ibGUgZGF0YSBhY2NvcmRpbmcg
dG8gdGhlc2UgbWFwcGluZ3MgYXMgaXQgYXJyaXZlcy4gSW5kZWVkLCB0aGlzIHdhcyBuZXZlciBl
eHBsaWNpdGx5IGRpc2FsbG93ZWQgc2luY2UgaXQg4oCcbWlnaHQgaGF2ZSBiZWVuIHVzZWZ1bOKA
nS4gVGhlIGltcGxlbWVudGF0aW9uIGNvbW11bml0eSwgaG93ZXZlciwgaGFzIGV4cHJlc3NlZCBj
b25jZXJucyBvdmVyIHRoZSBkaWZmaWN1bHR5IG9mIGltcGxlbWVudGluZyB0aGlzDQogb3Blbi1l
bmRlZGx5LiBIb3cgbWFueSBtYXBwaW5ncyBpcyBpdCByZWFzb25hYmxlIHRvIHN0b3JlPyBJcyB0
aGVyZSBhIERvUyByaXNrIGhlcmU/IEluc3RlYWQsIGl0IGhhcyBiZWVuIHJlcXVlc3RlZCB0aGF0
IHRoZWUgc3BlY2lmaWNhdGlvbiByZXN0cmljdHMgdGhlIHBsYWNlbWVudCBvZiB0aGUgRFNTIG9w
dGlvbiB0byBiZWluZyB3aXRoaW4gdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2UgdG8gd2hpY2gg
aXQgYXBwbGllcy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNl
cmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPkJlbG93IGFyZSBteSBjb21tZW50cyBvbiB0aGlzLiBJIGhhZCBzaGFyZWQgc29tZSBvZiB0
aGVzZSBwb2ludHMgaW4gYSBwcmV2aW91cyB0aHJlYWQgdGhhdCB5b3UgaGFkIGluaXRpYXRlZCBp
biB0aGUgc2FtZSBjb250ZXh0LiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFs
JnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZiI+VHJhbnNtaXR0aW5nIGxhcmdlIG51bWJlciBvZiBub24tY29udGln
dW91cyBkYXRhIHNlcXVlbmNlIG1hcHMgY291bGQgYmUgYSBtaXNiZWhhdmlvdXIgKG1hcC1mbG9v
ZGluZyksIHRob3VnaCBpdCBpcyBub3QgY2xlYXIgd2hldGhlciB0aGlzIGNhbiBnbyB0byB0aGUg
ZXh0ZW50IG9mIGNhdXNpbmcgYSBwb3RlbnRpYWwgRG9TIHRvIHRoZQ0KIGRhdGEgcmVjZWl2ZXIu
IFNvIHNvbWUgc29ydCBvZiByZXN0cmljdGlvbiBvbiB0aGlzIGNvdWxkIGJlIHVzZWZ1bC4mbmJz
cDsgT25lIGFwcHJvYWNoIGNvdWxkIGJlIHRvIGluc2lzdCB0aGF0IHRoZSBkYXRhIHNlbmRlciBz
aG91bGQgZW5zdXJlIHRoYXQgdGhlIG1hcCBiZWluZyB0cmFuc21pdHRlZCBpcyBmb3IgaW4td2lu
ZG93IGRhdGEsIGFzIHBlciB0aGUgcmVjZWl2ZXIgYWR2ZXJ0aXNlZCB3aW5kb3cuIEEgcmVjZWl2
ZXIgc2hvdWxkIGFueWhvdyBiZQ0KIHdpbGxpbmcgdG8gc3RvcmUgdGhlIG1hcHMgZm9yIGluLXdp
bmRvdyBkYXRhIHRvIGRlYWwgd2l0aCBwYWNrZXQgbG9zcy4gRm9yIGV4YW1wbGUsIHdoZW4gYSB3
aW5kb3cgb2YgZGF0YSBzZWdtZW50cyAoc2F5IDEgdG8gNjQpIGlzIHRyYW5zbWl0dGVkLCBlYWNo
IGNhcnJ5aW5nIGl0cyBjb3JyZXNwb25kaW5nIG1hcCwgYW5kIHNlZ21lbnQtMSBpcyBsb3N0LCB0
aGUgbWFwcyBmb3IgdGhlIHJlbWFpbmluZyA2MyBuZWVkIHRvIGJlIHN0b3JlZCB0aWxsDQogdGhl
IGxvc3Qgc2VnbWVudCBpcyByZXRyYW5zbWl0dGVkLiBPZiBjb3Vyc2UsIGluIHRoaXMgY2FzZSB0
aGUgbWFwcyB3aWxsIGJlIHN0b3JlZCBhdCB0aGUgcmVjZWl2ZXIgc2lkZSBhbG9uZyB3aXRoIHRo
ZWlyIGNvcnJlc3BvbmRpbmcgZGF0YS4gQnV0IHRoZSBuZWVkIHRvIHN0b3JlIG11bHRpcGxlIG1h
cHMgZm9yIGluLXdpbmRvdyBkYXRhIHdvdWxkIHN0aWxsIGJlIHRoZXJlLjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OmJsYWNrO2JhY2tncm91bmQ6d2hpdGUiPlRoZSBwcm9ibGVtIHdpdGggdGhlIHByb3Bvc2VkIGNo
YW5nZSAocmVzdHJpY3Rpb24pIGlzIHRoYXQgYSBkYXRhIHNlbmRlciBtYXkgZmluZCBpdCBkaWZm
aWN1bHQsIGluIGNhc2UgYSBuZWVkIGFyaXNlIHRvIHNsaWdodGx5IGRlbGF5IHRoZSBtYXAgZGVs
aXZlcnkNCiBieSBmZXcgc2VnbWVudHMsIGkuZS4sIHNlbmRpbmcgc29tZSBkYXRhIGZpcnN0IHdp
dGhvdXQgbWFwLCBhbmQgdGhlbiBzZW5kIHRoZSBjb3JyZXNwb25kaW5nIG1hcCBpbiBhIGxhdGVy
IHNlZ21lbnQsIGFzIHNob3duIGJlbG93Ojwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPnN1YmZsb3ctMTombmJz
cDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50LTEmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IHNlZ21lbnQtMyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50LTQgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyBzZWdtZW50LTc8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJh
Y2tncm91bmQ6d2hpdGUiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Ynl0ZXM6MS0xMDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBieXRlczoyMDEtMzAwICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2J5dGVzOjMwMS00MDAgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBieXRlczo2MDEtNzAw
PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1Nl
Z29lIFVJJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyZuYnNwO25vIG1hcCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO21hcCBmb3IgMS0xMDAgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7bWFwIGZvciAyMDEt
NDAwICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IG1hcCBmb3IgNjAx
LTcwMDwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVv
dDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkm
cXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7
LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5z
LXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPnN1YmZsb3ctMjombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDtzZWdtZW50LTImbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50LTUgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHNlZ21lbnQtNiAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7IHNlZ21lbnQtODwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmIj48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6YmxhY2siPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtieXRlczogMTAxLTIwMCAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGJ5dGVzOjQwMS01MDAmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IGJ5dGVzOiA1MDEtNjAwICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDtieXRlczo3MDEtODAwJm5ic3A7Jm5ic3A7Jm5ic3A7PC9zcGFuPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7
LHNhbnMtc2VyaWYiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDttYXAg
Zm9yIDEwMS0yMDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgbWFwIGZvciA0MDEtNjAwICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7bm8gbWFwICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDttYXAgZm9yIDcwMS04MDA8L3NwYW4+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1z
ZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5JbiB0aGUgYWJv
dmUgY2FzZSwgc2VnbWVudC0xIGdvZXMgd2l0aG91dCBtYXAgYW5kIGl0cyBtYXAgaXMgaW5jbHVk
ZWQgbGF0ZXIgaW4gc2VnbWVudC0zLCB0aGUgbmV4dCBkYXRhIHNlZ21lbnQgaW4gdGhlIHNhbWUg
c3ViZmxvdy4gRnVydGhlciwgJm5ic3A7aW4gdGhlIGFib3ZlIHNjaGVkdWxpbmcgcGF0dGVybiwg
dGhlIG1hcCBpbiBzZWdtZW50LTMNCiBjYW5ub3QgY292ZXIgdGhlICZuYnNwO2RhdGEgaW4gc2Vn
bWVudC0xIGFuZCBzZWdtZW50LTMsIGFzIHNvbWUgJm5ic3A7ZGF0YSBpbiBiZXR3ZWVuIChzZWdt
ZW50LTIpIGlzIHRyYW5zbWl0dGVkIHRocm91Z2ggYW5vdGhlciBzdWJmbG93LiZuYnNwOyBXaXRo
IHRoZSBwcm9wb3NlZCBjaGFuZ2UsIHRoZSBtYXAgaW4gc2VnbWVudC0zIHdpbGwgYmVjb21lIGlu
dmFsaWQgYW5kIHRoaXMgd2lsbCBldmVudHVhbGx5IGJyZWFrIHN1YmZsb3ctMSwgdGhvdWdoIHRo
aXMgY291bGQNCiBiZSBhIGNvcm5lciBjYXNlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZiI+VGhlIHF1ZXN0aW9uIGF0IHRoaXMgc3RhZ2UgaXMgd2h5IHdv
dWxkIHNlZ21lbnQtMSBiZSB0cmFuc21pdHRlZCB3aXRob3V0IGl0cyBtYXAuIEluIHRoZSBjYXNl
IG9mIGJpZGlyZWN0aW9uYWwgZGF0YSB0cmFuc2ZlciwgdGhlcmUgY291bGQgYmUgYSBuZWVkIHRv
IHBhY2sgYm90aCB0aW1lc3RhbXAgYW5kIFNBQ0sgJm5ic3A7b3B0aW9ucyBpbg0KIGEgZGF0YSBz
ZWdtZW50LCBpLmUuLCBwaWdneWJhY2tpbmcgb2YgJm5ic3A7U0FDSyB3aXRoIGRhdGEuIElmIHdl
IGNvbnNpZGVyIHRoYXQgdGltZXN0YW1wIHRha2VzIDEyIGJ5dGVzIGFuZCBTQUNLLCBldmVuIHdp
dGggc2luZ2xlIGJsb2NrLCAmbmJzcDt0YWtlcyBhbm90aGVyIDEwIGJ5dGVzLCB0aGUgcmVtYWlu
aW5nIDE4IGJ5dGVzIG9wdGlvbiBzcGFjZSBpcyBub3QgYWRlcXVhdGUgdG8gY2FycnkgZGF0YSBz
ZXF1ZW5jZSBzaWduYWwgd2l0aCBtYXAsIGVzcGVjaWFsbHkNCiB3aGVuIERTTiBpcyA2NCBiaXQg
bG9uZy4gU28gdGhlIGRlbGl2ZXJ5IG9mIGVpdGhlciBvZiB0aGUgdHdvIChTQUNLIG9yIG1hcCkg
d291bGQgYmUgZGVsYXllZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWYiPkFzIGZhciBhcyBJIHVuZGVyc3RhbmQsIFJGQyAyMDE4IChUQ1AgU2VsZWN0aXZl
IEFja25vd2xlZGdlbWVudCBPcHRpb25zKSBpbXBsaWVzIHRoYXQgU0FDSyBzaG91bGQgbm90IGJl
IGRlbGF5ZWQuIEl0IHN0YXRlcyAmcXVvdDtJZiBzZW50IGF0IGFsbCwgU0FDSyBvcHRpb25zIFNI
T1VMRCBiZSBpbmNsdWRlZCBpbiBhbGwgQUNLcyB3aGljaA0KIGRvIG5vdCBBQ0sgdGhlIGhpZ2hl
c3Qgc2VxdWVuY2UgbnVtYmVyIGluIHRoZSBkYXRhIHJlY2VpdmVyJ3MgcXVldWUmcXVvdDsuIEl0
IGFsc28gc2F5cyAmcXVvdDtJZiBkYXRhIHJlY2VpdmVyIGdlbmVyYXRlcyBTQUNLIG9wdGlvbnMg
dW5kZXIgYW55IGNpcmN1bXN0YW5jZSwgaXQgU0hPVUxEIGdlbmVyYXRlIHRoZW0gdW5kZXIgYWxs
IHBlcm1pdHRlZCBjaXJjdW1zdGFuY2VzJnF1b3Q7LiAmbmJzcDsgU28sIGFzIHBhcnQgb2YgbWVl
dGluZyB0aGUgUkZDIDIwMTggcmVxdWlyZW1lbnRzLA0KIGlmIHRoZSBjb21iaW5hdGlvbiBvZiBT
QUNLIGFuZCB0aW1lc3RhbXAgaXMgZ2l2ZW4gcHJlZmVyZW5jZSBvdmVyIERTUywgZGF0YSBzZWdt
ZW50cyBjb3VsZCBiZSB0cmFuc21pdHRlZCB3aXRob3V0IHRoZWlyIG1hcC4mbmJzcDs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkFub3RoZXIgY2FzZSBv
ZiBkZWxheWluZyBtYXAgY291bGQgYXJpc2UgaWYgdGhlIGRhdGEgc2VuZGVyIHByZWZlcnMgdG8g
c2VuZCBBRERfQUREUiBvcHRpb24sIGluc3RlYWQgb2YgbWFwLCBpbiBhIGRhdGEgc2VnbWVudC4g
SXQgaXMgbmljZSB0aGF0IEFERF9BRERSIG9wdGlvbiBjYW4gYmUgZGVsaXZlcmVkIHJlbGlhYmx5
IGluIGENCiBwdXJlIEFDSywgYnV0IEkgdGhpbmsgdGhpcyBpcyBub3QgdGhlIGNhc2Ugd2l0aCBE
U1MgYXQgcHJlc2VudC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMt
c2VyaWYiPklmIHdlIGFkb3B0IHRoZSBwcm9wb3NlZCBjaGFuZ2UsIEkgdGhpbmsgaXQgbWlnaHQg
YWxzbyBiZSBoZWxwZnVsIHRvIHNwZWxsIG91dCBob3cgdGhlIHJlY2VpdmVyIGlzIHN1cHBvc2Vk
IHRvIGJlaGF2ZSwgaWYgaXQgZ2V0cyBtYXBzIG5vdCBtZWV0aW5nIHRoZSBNVVNUIGNvbmRpdGlv
biBpbiB0aGUgcHJvcG9zZWQgY2hhbmdlLiZuYnNwOw0KIEZvciBleGFtcGxlIHRlcm1pbmF0aW9u
IG9mIHRoZSBzdWJmbG93IHdpdGggTVBfVENQUlNUIG9wdGlvbiAoc2VjdGlvbiAzLjYgaW4gUkZD
IDY4MjQtYmlzKSB3aXRoIGFwcHJvcHJpYXRlIHJlYXNvbiBjb2RlIGFuZCBUIGZsYWcgdmFsdWUg
dG8gaW50aW1hdGUgdGhlIGRhdGEgc2VuZGVyIHRoZSBjYXVzZSBmb3Igc3ViZmxvdyB0ZXJtaW5h
dGlvbi4mbmJzcDsmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPldpdGggcmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+QW5pbDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+UGxlYXNlIGNhbiBtZW1iZXJzIG9m
IHRoZSBXRyBleHByZXNzIHdoZXRoZXIgdGhleSBhcmUgaGFwcHkgd2l0aCB0aGVzZSBjaGFuZ2Vz
LCBvciBjb25jZXJuZWQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj5CZXN0IHJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkFsYW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OyxzYW5zLXNlcmlmIj48YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXzxicj4NCm11bHRpcGF0aHRjcCBtYWlsaW5nIGxpc3Q8YnI+
DQo8YSBocmVmPSJtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+
bXVsdGlwYXRodGNwQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNwIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3A8L2E+PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPjxicj4NCjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPGJyPg0KbXVsdGlwYXRodGNwIG1haWxpbmcgbGlzdDxicj4NCjxh
IGhyZWY9Im1haWx0bzptdWx0aXBhdGh0Y3BAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tdWx0
aXBhdGh0Y3BAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3AiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRpcGF0aHRjcDwvYT48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJv
dHRvbToxMi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_LNXP123MB2587401C237F7FF68CF09850EB020LNXP123MB2587GBRP_--


From nobody Wed Feb  5 07:13:22 2020
Return-Path: <prvs=29710429f=anil@csir4pi.in>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CFB212080B for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 07:13:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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 4E69F1t-s2n3 for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 07:13:05 -0800 (PST)
Received: from relayout78.nic.in (relayout78.nic.in [164.100.14.228]) (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 16849120112 for <multipathtcp@ietf.org>; Wed,  5 Feb 2020 07:12:51 -0800 (PST)
IronPort-PHdr: =?us-ascii?q?9a23=3AETbMIBBGqD3ma+OGIbBZUyQJP3N1i/DPJgcQr6?= =?us-ascii?q?AfoPdwSP37p8mwAkXT6L1XgUPTWs2DsrQY0raQ7vmrBjRIoc7Y9ixbK9oUD1?= =?us-ascii?q?5NoP5VtjRoONSCB0z/IayiRA0BN+MGamVY+WqmO1NeAsf0ag6aiHSz6TkPBk?= =?us-ascii?q?e3blItdaz6FYHIksu4yf259YHNbAVUnjq9Zq55IAmroQnLucQanIRvJrwxxx?= =?us-ascii?q?fUrXdFefhazn5sKV6Pghrw/Mi98INt/ihKp/4t68tMWrjmcqolSrBVEC4oOH?= =?us-ascii?q?0v6s3xshnDQwqP5n8CXWgTjxFFHQvL4gzkU5noqif1ufZz1yecPc3tULA7Qi?= =?us-ascii?q?+i4LtxSB/pkygIKTg0+3zKh8NqjaJbpBWhpwFjw4PRfYqYOuZycr/bcNgHXm?= =?us-ascii?q?dKQNpfWDJdDYO9d4sPDvQOPeBEr4nmulACqQKyCRSwCO/zzzNFgGL9068n3O?= =?us-ascii?q?Q7CQzI0gwuEcwNvnvWotX7KagdXvy0zKfP0TXOdOlZ1Svn5YXSaB0tvfOBUL?= =?us-ascii?q?RtesTR00kvEAbFg02fpof4Iz6V0OUNs2yG5ORlSOKvjnQoqxtsqTWo3MgsjI?= =?us-ascii?q?jJhoYOx1/Y7iV5wZw1KNKgSE56e9KkEZ1QujicOoBrTM0iRGRotzw7yr0AoZ?= =?us-ascii?q?O7fTYFyIgpxxLFbPyHaYeI7xT+X+iSOTd1nG9pdK6jixqo8kWs1vfwWtSp3F?= =?us-ascii?q?pQoSdIkMHAum0P2hDO8MSKS+Zx8l2g1DuLzQze6eJJLVgpmabHN5It2L09mo?= =?us-ascii?q?YJvUjeHyL6glj6gaGSe0k85+Sk9/jrbq/lq5OALYN4lwDzPr4wlsGwHeg1NB?= =?us-ascii?q?UFUXKB9uSmzrLj+FX0QLBNjvIrjKbUqIvaJcEHpq6hBA9Vz5oj5w6/Dzi41N?= =?us-ascii?q?QYmmEKLF1deBKAgIjoNUzCLf7iAfe5glSjjC1nx/HAPrH5A5XNKGbMkKv5cL?= =?us-ascii?q?pg90JQ1BA/wNND655OF70NPej/V0DzudDACx82KQ20w+LpCNVn0YMeXHqCDb?= =?us-ascii?q?WfMKPTtV+F/f4gI/KNZI8Ptzv9M/kl6+TvjX8/gVMdZ7Wm3YMLaHCkGfRrO1?= =?us-ascii?q?+WYX72jdcHC2sKsA0+TPb3h1CZXj5TYmy9X6M45j0hFI2mCoLDTJi3gLOdxC?= =?us-ascii?q?e7AoFWZmdeB1CKCnfnap+IW/YSZyKOLM9siTMEVb27RI8g0RGirhP1y71iLu?= =?us-ascii?q?DM4C0XqYrj1MRp5+3UjRwy8CF0D8CB02GMV2F7hH8IRz8q3K9juUxw0VaD3r?= =?us-ascii?q?Zkg/xWD9BT4OlJUghpfaLbmqZLDMvyWwzce9bBble9QtSqCHt5GtQqz5kPbl?= =?us-ascii?q?pzM9qnhxHHmSGtBulGuaaMAckKuova3ny5BNt4wmyOgKAnjl0OSdBOLzG+h+?= =?us-ascii?q?h+8V6AVMbyj0yFmvPyJuwn1ynX+TLGlDLWsQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2FtAQCZ2jpe/y8LUGRlGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF7gSVTMWwTQwEeEioKhAtviBSGDoIRiWKRVQQ?= =?us-ascii?q?JAQECAQEBAQEgAQoKAgEBAoN5RQKCOyQ4EwIDAQwBAQEEAQEBAQEFAwEBAQJ?= =?us-ascii?q?phGtMDII7KQFxcQEBAQEBAQEBAQEBAQEBAQEBAQEWAkNVEgEBHQEBAQEDAQE?= =?us-ascii?q?YCUQHBgUQAgEIDQEDBAEBIQEGAwICIQYfCQgCBAoBCBSDE4JKAy0BBQqrG3W?= =?us-ascii?q?BMhoChS6CVg2CGgaBOIwiFAaCAIERgxM+gQSBF0kBAYE8BwEBMiSCWoJeBI1?= =?us-ascii?q?Uiit8hzWOQDJEgkSSGYRFgkiID4Q1A4t6mXSRZjgjKoEuTTg7gmxQGI4zAxe?= =?us-ascii?q?FCINchUc6ATGBKYpjBQwXgQsBgQ8BAQ?=
X-IPAS-Result: =?us-ascii?q?A2FtAQCZ2jpe/y8LUGRlGgEBAQEBAQEBAQMBAQEBEQEBA?= =?us-ascii?q?QICAQEBAYF7gSVTMWwTQwEeEioKhAtviBSGDoIRiWKRVQQJAQECAQEBAQEgA?= =?us-ascii?q?QoKAgEBAoN5RQKCOyQ4EwIDAQwBAQEEAQEBAQEFAwEBAQJphGtMDII7KQFxc?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEWAkNVEgEBHQEBAQEDAQEYCUQHBgUQAgEID?= =?us-ascii?q?QEDBAEBIQEGAwICIQYfCQgCBAoBCBSDE4JKAy0BBQqrG3WBMhoChS6CVg2CG?= =?us-ascii?q?gaBOIwiFAaCAIERgxM+gQSBF0kBAYE8BwEBMiSCWoJeBI1Uiit8hzWOQDJEg?= =?us-ascii?q?kSSGYRFgkiID4Q1A4t6mXSRZjgjKoEuTTg7gmxQGI4zAxeFCINchUc6ATGBK?= =?us-ascii?q?YpjBQwXgQsBgQ8BAQ?=
X-IronPort-AV: E=McAfee;i="6000,8403,9521"; a="417987645"
X-IronPort-AV: E=Sophos;i="5.70,406,1574101800";  d="scan'208,217";a="417987645"
Received: from unknown (HELO gpogw13.nic.in) ([100.80.11.47]) by relaysp3internal.nic.in with ESMTP; 05 Feb 2020 20:42:44 +0530
Received: from gpogw13.nic.in (localhost [127.0.0.1]) by gpogw13.nic.in (Postfix) with ESMTPS id 9B1894052281; Wed,  5 Feb 2020 20:42:45 +0530 (IST)
Received: from localhost (localhost [127.0.0.1]) by gpogw13.nic.in (Postfix) with ESMTP id 5B5B04067ADC; Wed,  5 Feb 2020 20:42:45 +0530 (IST)
X-Amavis-Modified: Mail body modified (using disclaimer) - gpogw13.nic.in
Received: from gpogw13.nic.in ([127.0.0.1]) by localhost (gpogw13.nic.in [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DGZzLJ6V-Xd7; Wed,  5 Feb 2020 20:42:45 +0530 (IST)
Received: from gms281.nic.in (unknown [100.80.16.240]) by gpogw13.nic.in (Postfix) with ESMTP id 3EA9A4067ACA; Wed,  5 Feb 2020 20:42:45 +0530 (IST)
Date: Wed, 5 Feb 2020 20:39:25 +0530 (IST)
From: V Anil Kumar <anil@csir4pi.in>
To: "Yoshifumi Nishida" <nsd.ietf@gmail.com>
Cc: "alan ford" <alan.ford@gmail.com>, "multipathtcp" <multipathtcp@ietf.org>
Message-ID: <620489655.29573797.1580915365031@csir4pi.in>
In-Reply-To: <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="=_6184590f-def9-44a6-95c2-01124c52e68f"
X-Originating-IP: [171.61.69.88, 100.80.16.139]
X-Mailer: Zimbra 8.8.9_GA_2044 (ZimbraWebClient - GC49 (Mac)/8.8.9_GA_2044)
Thread-Topic: RFC6824bis edits based on implementation feedback
Thread-Index: 6aX4mmarRCwLBIAFHT5LceMFfq0bog==
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/sPWeq7Mz2H8PBFd-4tlnwHIWREY>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2020 15:13:17 -0000

--=_6184590f-def9-44a6-95c2-01124c52e68f
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Yoshi,=20

Please see in line.=20


From: "Yoshifumi Nishida" <nsd.ietf@gmail.com>=20
To: "V Anil Kumar" <anil@csir4pi.in>=20
Cc: "alan ford" <alan.ford@gmail.com>, "multipathtcp" <multipathtcp@ietf.or=
g>=20
Sent: Tuesday, February 4, 2020 1:08:45 PM=20
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedba=
ck=20

Hi Anil,=20

Thanks for pointing it out. I overlooked this one.=20
This looks an interesting point.=20

It seems to me that whether RST is happen or not depends on the size of rec=
eive window according to the text.=20
If the receive window size is big enough to accommodate segment 1 and segme=
nt 3, the text " Implementations MAY hold onto such unmapped data for a sho=
rt while in the expectation that a mapping will arrive shortly. " can be ap=
plied to the segment 1. As a result, the segment 1 won't be discarded.=20

Yes. So, segment 1 may be kept in the data receiver's buffer in expectation=
 that its mapping will arrive shortly. And in the example that we are refer=
ring to, the data sender will not be able to include the map for the data i=
n segment 1 in segment 3 or any higher segment.=20

Regards,=20

Anil=20

However, this might be contradict with the new texts Alan proposed? Or, am =
I missing something?=20

Thanks,=20
--=20
Yoshi=20



On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar < [ mailto:anil@csir4pi.in | an=
il@csir4pi.in ] > wrote:=20



Hi Yoshi,=20

Thanks for this point. In fact, I had initially not thought of a scenario, =
where the map is being delivered through a retransmitted data packet while =
its first transmission did not include the map. Now I am just seeing the do=
cument (RFC 6824-bis) in this context.=20

My understanding is that in scenarios like what I described in my previous =
mail, RST is likely to happen whether we explicitly state so or not. Please=
 see the paragraph containing the below text in RFC 6824-bis.=20

"If a mapping for that subflow-level sequence space does not arrive within =
a receive window of data, that subflow SHOULD be treated as broken, closed =
with a RST, and any unmapped data silently discarded."=20

if we assume that the map is included while retransmitting the data (even t=
hough the first transmission did not contain the map for some reasons), we =
could argue that RST could be avoided provided that the retransmission is t=
riggered within a receive window of data. But the question here would be ho=
w and when will the retransmission take place. In this case, the subflow ma=
y not initiate the retransmission of data by its own (i.e., no retransmissi=
on due to three duplicate ACKs or RTO expiry at subflow level) as there is =
no segment loss at subflow level sequence space. So there could be a high p=
ossibility of RST happening even before the map delivery through retransmis=
sion.=20

With regards,=20

Anil=20

From: "Yoshifumi Nishida" < [ mailto:nsd.ietf@gmail.com | nsd.ietf@gmail.co=
m ] >=20
To: "V Anil Kumar" < [ mailto:anil@csir4pi.in | anil@csir4pi.in ] >=20
Cc: "alan ford" < [ mailto:alan.ford@gmail.com | alan.ford@gmail.com ] >, "=
multipathtcp" < [ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ] >=
=20
Sent: Saturday, February 1, 2020 3:39:51 AM=20
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedba=
ck=20

Hi Anil,=20

I have a question about your proposed text.=20
I am actually wondering if we really want to terminate connection here.=20

The packets without proper mappings will be treated as invalid and will be =
discarded.=20
If an implementation failed to attach proper mapping for some reasons (e.g.=
 option space), it might be able to attach the proper one when it retransmi=
ts the packets. This also looks ok to me.=20

I don't have strong preference for this. But, do we have a reason to termin=
ate connection?=20

Thanks,=20
--=20
Yoshi=20

On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar < [ mailto:anil@csir4pi.in | =
anil@csir4pi.in ] > wrote:=20

BQ_BEGIN

Hi,=20

I have some points related to the modifications (Change 2) being proposed o=
n data sequence map. Please see them inline. Though I am putting forward th=
e below points, if the consensus is in favour of the proposed change for re=
ducing implementation complexity, I am also OK with that as well.=20


From: "alan ford" < [ mailto:alan.ford@gmail.com | alan.ford@gmail.com ] >=
=20
To: [ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]=20
Sent: Thursday, January 2, 2020 4:21:32 AM=20
Subject: [multipathtcp] RFC6824bis edits based on implementation feedback=
=20

Hi all,=20
We=E2=80=99d love to get this to a state of completion as soon as possible,=
 and to this end I am starting a new thread on this topic. In discussion wi=
th the chairs, it is possible to make the desired changes in AUTH48 as long=
 as there is WG consensus. The discussion so far has been fairly limited in=
 terms of participation.=20

I would ask the chairs please if it was possible to specify a time bound fo=
r this discussion and a default conclusion.=20

Regarding the changes, in summary, there are two areas where changes have b=
een requested by the implementation community. As we are the IETF we obviou=
sly have strong focus on =E2=80=9Crunning code=E2=80=9D and so ease of impl=
ementing standards-compliant code is strongly desirable. However, we do not=
 wish to reduce functionality agreed by the IETF community if it is conside=
red a required feature by the community.=20


Change 1=20

Change the sentence reading:=20

If B has data to send first, then the reliable delivery of the ACK + MP_CAP=
ABLE can be inferred by the receipt of this data with an MPTCP Data Sequenc=
e Signal (DSS) option (Section 3.3).=20

To:=20

If B has data to send first, then the reliable delivery of the ACK + MP_CAP=
ABLE is ensured by the receipt of this data with an MPTCP Data Sequence Sig=
nal (DSS) option (Section 3.3) containing a DATA_ACK for the MP_CAPABLE (wh=
ich is the first octet of the data sequence space).=20

What this means:=20

The current text is concerned only with ensuring a path is MPTCP capable, a=
nd so only cares that DSS option occurs on a data packet. However, the MP_C=
APABLE option is defined to occupy the first octet of data sequence space a=
nd thus, if analogous to TCP, must be acknowledged. >From an implementation=
 point of view it would make sense not to have this hanging around forever =
and instead define it is acknowledged at the connection level as soon as re=
ceived. This change ensures the first data packet also DATA_ACKs this MP_CA=
PABLE octet.=20


Change 2=20

Change the sentence reading:=20

A Data Sequence Mapping does not need to be included in every MPTCP packet,=
 as long as the subflow sequence space in that packet is covered by a mappi=
ng known at the receiver.=20

To:=20

The mapping provided by a Data Sequence Mapping MUST apply to some or all o=
f the subflow sequence space in the TCP segment which carries the option. I=
t does not need to be included in every MPTCP packet, as long as the subflo=
w sequence space in that packet is covered by a mapping known at the receiv=
er.=20

What this means:=20

The current text does not place any restrictions on where a mapping could a=
ppear. In theory a sender could define a thousand different mappings up fro=
nt, send them all, and expect a receiver to store this and reassemble data =
according to these mappings as it arrives. Indeed, this was never explicitl=
y disallowed since it =E2=80=9Cmight have been useful=E2=80=9D. The impleme=
ntation community, however, has expressed concerns over the difficulty of i=
mplementing this open-endedly. How many mappings is it reasonable to store?=
 Is there a DoS risk here? Instead, it has been requested that thee specifi=
cation restricts the placement of the DSS option to being within the subflo=
w sequence space to which it applies.=20

Below are my comments on this. I had shared some of these points in a previ=
ous thread that you had initiated in the same context.=20

Transmitting large number of non-contiguous data sequence maps could be a m=
isbehaviour (map-flooding), though it is not clear whether this can go to t=
he extent of causing a potential DoS to the data receiver. So some sort of =
restriction on this could be useful. One approach could be to insist that t=
he data sender should ensure that the map being transmitted is for in-windo=
w data, as per the receiver advertised window. A receiver should anyhow be =
willing to store the maps for in-window data to deal with packet loss. For =
example, when a window of data segments (say 1 to 64) is transmitted, each =
carrying its corresponding map, and segment-1 is lost, the maps for the rem=
aining 63 need to be stored till the lost segment is retransmitted. Of cour=
se, in this case the maps will be stored at the receiver side along with th=
eir corresponding data. But the need to store multiple maps for in-window d=
ata would still be there.=20

The problem with the proposed change (restriction) is that a data sender ma=
y find it difficult, in case a need arise to slightly delay the map deliver=
y by few segments, i.e., sending some data first without map, and then send=
 the corresponding map in a later segment, as shown below:=20



subflow-1: segment-1 segment-3 segment-4 segment-7=20

bytes:1-100 bytes:201-300 bytes:301-400 bytes:601-700=20

no map map for 1-100 map for 201-400 map for 601-700=20










subflow-2: segment-2 segment-5 segment-6 segment-8=20

bytes: 101-200 bytes:401-500 bytes: 501-600 bytes:701-800=20

map for 101-200 map for 401-600 no map map for 701-800=20





In the above case, segment-1 goes without map and its map is included later=
 in segment-3, the next data segment in the same subflow. Further, in the a=
bove scheduling pattern, the map in segment-3 cannot cover the data in segm=
ent-1 and segment-3, as some data in between (segment-2) is transmitted thr=
ough another subflow. With the proposed change, the map in segment-3 will b=
ecome invalid and this will eventually break subflow-1, though this could b=
e a corner case.=20

The question at this stage is why would segment-1 be transmitted without it=
s map. In the case of bidirectional data transfer, there could be a need to=
 pack both timestamp and SACK options in a data segment, i.e., piggybacking=
 of SACK with data. If we consider that timestamp takes 12 bytes and SACK, =
even with single block, takes another 10 bytes, the remaining 18 bytes opti=
on space is not adequate to carry data sequence signal with map, especially=
 when DSN is 64 bit long. So the delivery of either of the two (SACK or map=
) would be delayed.=20

As far as I understand, RFC 2018 (TCP Selective Acknowledgement Options) im=
plies that SACK should not be delayed. It states "If sent at all, SACK opti=
ons SHOULD be included in all ACKs which do not ACK the highest sequence nu=
mber in the data receiver's queue". It also says "If data receiver generate=
s SACK options under any circumstance, it SHOULD generate them under all pe=
rmitted circumstances". So, as part of meeting the RFC 2018 requirements, i=
f the combination of SACK and timestamp is given preference over DSS, data =
segments could be transmitted without their map.=20

Another case of delaying map could arise if the data sender prefers to send=
 ADD_ADDR option, instead of map, in a data segment. It is nice that ADD_AD=
DR option can be delivered reliably in a pure ACK, but I think this is not =
the case with DSS at present.=20

If we adopt the proposed change, I think it might also be helpful to spell =
out how the receiver is supposed to behave, if it gets maps not meeting the=
 MUST condition in the proposed change. For example termination of the subf=
low with MP_TCPRST option (section 3.6 in RFC 6824-bis) with appropriate re=
ason code and T flag value to intimate the data sender the cause for subflo=
w termination.=20
With regards,=20

Anil=20

Please can members of the WG express whether they are happy with these chan=
ges, or concerned.=20

Best regards,=20
Alan=20


_______________________________________________=20
multipathtcp mailing list=20
[ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]=20
[ https://www.ietf.org/mailman/listinfo/multipathtcp | https://www.ietf.org=
/mailman/listinfo/multipathtcp ]=20



_______________________________________________=20
multipathtcp mailing list=20
[ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]=20
[ https://www.ietf.org/mailman/listinfo/multipathtcp | https://www.ietf.org=
/mailman/listinfo/multipathtcp ]=20






BQ_END



=0A
--=_6184590f-def9-44a6-95c2-01124c52e68f
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"font-family: arial, helvetica, sans-serif; font-s=
ize: style=3D" font-size:=3D"" 12pt;=3D"" color:=3D"" #000000"=3D""><div da=
ta-marker=3D"__QUOTED_TEXT__"><div style=3D"font-family: 'arial' , 'helveti=
ca' , sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , s=
ans-serif;"><div><div style=3D"font-family: 'arial' , 'helvetica' , sans-se=
rif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , sans-serif;"><=
div><div style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" data-mc=
e-style=3D"font-family: 'arial' , 'helvetica' , sans-serif;"><div>Hi Yoshi,=
</div><br><div>Please see in line.</div><br><hr id=3D"zwchr"><div><b>From: =
</b>"Yoshifumi Nishida" &lt;nsd.ietf@gmail.com&gt;<br><b>To: </b>"V Anil Ku=
mar" &lt;anil@csir4pi.in&gt;<br><b>Cc: </b>"alan ford" &lt;alan.ford@gmail.=
com&gt;, "multipathtcp" &lt;multipathtcp@ietf.org&gt;<br><b>Sent: </b>Tuesd=
ay, February 4, 2020 1:08:45 PM<br><b>Subject: </b>Re: [multipathtcp] RFC68=
24bis edits based on implementation feedback<br></div><br><div><div dir=3D"=
ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><br><div>Thanks f=
or pointing it out. I overlooked this one.</div><div>This looks an interest=
ing point.<br></div><br><div>It seems to me that whether RST is happen or n=
ot depends on the size of receive window according to the text.<br></div><d=
iv>If the receive window size is big enough to accommodate&nbsp;segment 1 a=
nd segment 3, the text "<span style=3D"color: #000000; font-size: 13.3333px=
;" data-mce-style=3D"color: #000000; font-size: 13.3333px;">Implementations=
 MAY hold onto such unmapped data for a short while in&nbsp;</span><span st=
yle=3D"color: #000000; font-size: 13.3333px;" data-mce-style=3D"color: #000=
000; font-size: 13.3333px;">the expectation that a mapping will arrive shor=
tly. "&nbsp;</span>can be applied to the segment 1. As a result, the segmen=
t 1 won't be discarded.&nbsp;</div><br><div><em>Yes. &nbsp;So, segment 1 ma=
y be kept in the data receiver's buffer in expectation that its mapping wil=
l arrive shortly. And in the example that we are referring to, the data sen=
der will not be able to include the map for the data in segment 1 in segmen=
t 3 or any higher segment.</em></div><br><div><em>Regards,</em></div><br><d=
iv><em>Anil</em></div><br><div>However, this might be contradict with the n=
ew texts Alan proposed? Or, am I missing something?</div><br><div>Thanks,</=
div><div>--</div><div>Yoshi</div><br><br><br><div><div dir=3D"ltr">On Sun, =
Feb 2, 2020 at 8:42 AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%=
20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"=
_blank" data-mce-href=3D"mailto:anil@csir4pi.in">anil@csir4pi.in</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0p=
x 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;" data-mce-style=
=3D"margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left=
: 1ex;"><div><div><div><div style=3D"font-family: 'arial' , 'helvetica' , s=
ans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , sans-ser=
if;"><div>Hi Yoshi,</div><br><div>Thanks for this point. In fact, I had ini=
tially not thought of a scenario, where the map is being delivered through =
a retransmitted data packet while its first transmission did not include th=
e map. Now I am just seeing the document (RFC 6824-bis) in this context.</d=
iv><br><div>My understanding is that in scenarios like what I described in =
my previous mail, RST is likely to happen whether we explicitly state so or=
 not. Please see the paragraph containing the below text in RFC 6824-bis. &=
nbsp;</div><br><div>"If a mapping for that subflow-level sequence space doe=
s not arrive within a receive window of data, that subflow SHOULD be treate=
d as broken, closed with a RST, and any unmapped data silently discarded."<=
/div><br><div>if we assume that the map is included while retransmitting th=
e data (even though the first transmission did not contain the map for some=
 reasons), &nbsp;we could argue that RST could be avoided provided that the=
 retransmission is triggered within a receive window of data. But the quest=
ion here would be how and when will the retransmission take place. In this =
case, the subflow may not initiate the retransmission of data by its own (i=
.e., no retransmission due to three duplicate ACKs or RTO expiry at subflow=
 level) as there is no segment loss at subflow level sequence space. So the=
re could be a high possibility of RST happening even before the map deliver=
y through retransmission.&nbsp;</div><br><div>With regards,&nbsp;</div><br>=
<div>Anil</div><div>&nbsp;</div><hr id=3D"gmail-m_218086596951724501gmail-m=
_2982267033577902985zwchr"><div><b>From: </b>"Yoshifumi Nishida" &lt;<a hre=
f=3D"mailto:nsd.ietf@gmail.com" rel=3D"nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow=
 noopener noreferrer" target=3D"_blank" data-mce-href=3D"mailto:nsd.ietf@gm=
ail.com">nsd.ietf@gmail.com</a>&gt;<br><b>To: </b>"V Anil Kumar" &lt;<a hre=
f=3D"mailto:anil@csir4pi.in" rel=3D"nofollow%20noopener%20noreferrer%20nofo=
llow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow no=
opener noreferrer" target=3D"_blank" data-mce-href=3D"mailto:anil@csir4pi.i=
n">anil@csir4pi.in</a>&gt;<br><b>Cc: </b>"alan ford" &lt;<a href=3D"mailto:=
alan.ford@gmail.com" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20n=
oopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener n=
oreferrer" target=3D"_blank" data-mce-href=3D"mailto:alan.ford@gmail.com">a=
lan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a href=3D"mailto:multipatht=
cp@ietf.org" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%=
20noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener noreferre=
r" target=3D"_blank" data-mce-href=3D"mailto:multipathtcp@ietf.org">multipa=
thtcp@ietf.org</a>&gt;<br><b>Sent: </b>Saturday, February 1, 2020 3:39:51 A=
M<br><b>Subject: </b>Re: [multipathtcp] RFC6824bis edits based on implement=
ation feedback<br></div><br><div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=
=3D"ltr"><div>Hi Anil,</div><br><div>I have a question about your proposed =
text.</div><div><div>I am actually wondering if we really want to terminate=
 connection here.&nbsp;</div></div><br><div>The packets without proper mapp=
ings will be treated as invalid and will be discarded.&nbsp;</div><div>If a=
n implementation failed to attach proper mapping for some reasons (e.g. opt=
ion space), it might be able to attach the proper one when it retransmits t=
he packets. This also looks ok to me.</div><br><div>I don't have strong pre=
ference for this. But, do we have a reason to terminate connection?</div><b=
r><div>Thanks,</div><div>--<br></div><div>Yoshi</div><br><div><div dir=3D"l=
tr">On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar &lt;<a href=3D"mailto:ani=
l@csir4pi.in" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener=
%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20no=
referrer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" t=
arget=3D"_blank" data-mce-href=3D"mailto:anil@csir4pi.in">anil@csir4pi.in</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0=
px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;" data-=
mce-style=3D"margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; pad=
ding-left: 1ex;"><div><div><div><div style=3D"font-family: 'arial' , 'helve=
tica' , sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' ,=
 sans-serif;"><div><span style=3D"font-size: 12pt; line-height: 1.3;" data-=
mce-style=3D"font-size: 12pt; line-height: 1.3;">Hi,</span><br></div><div><=
div style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" data-mce-sty=
le=3D"font-family: 'arial' , 'helvetica' , sans-serif;"><div style=3D"font-=
family: 'arial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-family:=
 'arial' , 'helvetica' , sans-serif;"><div style=3D"font-family: 'arial' , =
'helvetica' , sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvet=
ica' , sans-serif;"><div style=3D"font-family: 'arial' , 'helvetica' , sans=
-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , sans-serif;=
"><div style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" data-mce-=
style=3D"font-family: 'arial' , 'helvetica' , sans-serif;"><div style=3D"fo=
nt-family: 'arial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-fami=
ly: 'arial' , 'helvetica' , sans-serif;"><div style=3D"font-family: 'arial'=
 , 'helvetica' , sans-serif;" data-mce-style=3D"font-family: 'arial' , 'hel=
vetica' , sans-serif;"><br><div>I have some points related to the &nbsp;mod=
ifications (Change 2) being proposed on data sequence map. Please see them =
inline.&nbsp;<span style=3D"color: #000000; font-family: 'arial' , 'helveti=
ca' , sans-serif; font-size: 16px; font-style: normal; font-weight: 400; le=
tter-spacing: normal; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; background-color: #ffffff; float: none; display:=
 inline;" data-mce-style=3D"color: #000000; font-family: 'arial' , 'helveti=
ca' , sans-serif; font-size: 16px; font-style: normal; font-weight: 400; le=
tter-spacing: normal; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; background-color: #ffffff; float: none; display:=
 inline;">Though I am putting forward the below points, if the consensus is=
 in favour of the proposed change for reducing implementation complexity, I=
 am also OK with that as well.&nbsp;</span><br></div><br><hr id=3D"gmail-m_=
218086596951724501gmail-m_2982267033577902985gmail-m_7687184382299596774zwc=
hr"><div><b>From: </b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com=
" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferre=
r%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"_bl=
ank" data-mce-href=3D"mailto:alan.ford@gmail.com">alan.ford@gmail.com</a>&g=
t;<br><b>To: </b><a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%2=
0noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noop=
ener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%=
20noreferrer nofollow noopener noreferrer" target=3D"_blank" data-mce-href=
=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br><b>Sent: </b=
>Thursday, January 2, 2020 4:21:32 AM<br><b>Subject: </b>[multipathtcp] RFC=
6824bis edits based on implementation feedback<br></div><br><div>Hi all,<br=
><div>We=E2=80=99d love to get this to a state of completion as soon as pos=
sible, and to this end I am starting a new thread on this topic. In discuss=
ion with the chairs, it <i>is </i>possible to make the desired changes in A=
UTH48 as long as there is WG consensus. The discussion so far has been fair=
ly limited in terms of participation.</div><br><div>I would ask the chairs =
please if it was possible to specify a time bound for this discussion and a=
 default conclusion.</div><br><div>Regarding the changes, in summary, there=
 are two areas where changes have been requested by the implementation comm=
unity. As we are the IETF we obviously have strong focus on =E2=80=9Crunnin=
g code=E2=80=9D and so ease of implementing standards-compliant code is str=
ongly desirable. However, we do not wish to reduce functionality agreed by =
the IETF community if it is considered a required feature by the community.=
</div><br><br><div><b>Change 1</b></div><div><b><br></b></div><div>Change t=
he sentence reading:<br><br><i>&nbsp; &nbsp;If B has data to send first, th=
en the reliable delivery of the ACK + MP_CAPABLE can be inferred by the rec=
eipt of this data with an MPTCP Data Sequence Signal (DSS) option (Section =
3.3).&nbsp;<br></i><br>To:<br><br><i>&nbsp; &nbsp;If B has data to send fir=
st, then the reliable delivery of the ACK + MP_CAPABLE is ensured by the re=
ceipt of this data with an MPTCP Data Sequence Signal (DSS) option (Section=
 3.3) containing a DATA_ACK for the MP_CAPABLE (which is the first octet of=
 the data sequence&nbsp;space).<br></i><br></div><div>What this means:</div=
><br><div>The current text is concerned only with ensuring a path is MPTCP =
capable, and so only cares that DSS option occurs on a data packet. However=
, the MP_CAPABLE option is defined to occupy the first octet of data sequen=
ce space and thus, if analogous to TCP, must be acknowledged. &gt;From an i=
mplementation point of view it would make sense not to have this hanging ar=
ound forever and instead define it is acknowledged at the connection level =
as soon as received. This change ensures the first data packet also DATA_AC=
Ks this MP_CAPABLE octet.</div><br><br><div><b>Change 2</b></div><div><b><b=
r></b></div><div>Change the sentence reading:<br><br><i>&nbsp; &nbsp;A Data=
 Sequence Mapping does not need to be included in every MPTCP packet, as lo=
ng as the subflow sequence space in that packet is covered by a mapping kno=
wn at the receiver.</i><br><br>To:<br><br><i>&nbsp; &nbsp;The mapping provi=
ded by a Data Sequence Mapping MUST apply to some or all of the subflow seq=
uence space in the TCP segment which carries the option. It does not need t=
o be included in every MPTCP packet, as long as the subflow sequence space =
in that packet is covered by a mapping known at the receiver.<br></i><br>Wh=
at this means:</div><br><div>The current text does not place any restrictio=
ns on where a mapping could appear. In theory a sender could define a thous=
and different mappings up front, send them all, and expect a receiver to st=
ore this and reassemble data according to these mappings as it arrives. Ind=
eed, this was never explicitly disallowed since it =E2=80=9Cmight have been=
 useful=E2=80=9D. The implementation community, however, has expressed conc=
erns over the difficulty of implementing this open-endedly. How many mappin=
gs is it reasonable to store? Is there a DoS risk here? Instead, it has bee=
n requested that thee specification restricts the placement of the DSS opti=
on to being within the subflow sequence space to which it applies.</div><br=
><div>Below are my comments on this. I had shared some of these points in a=
 previous thread that you had initiated in the same context.&nbsp;</div><br=
><div>Transmitting large number of non-contiguous data sequence maps could =
be a misbehaviour (map-flooding), though it is not clear whether this can g=
o to the extent of causing a potential DoS to the data receiver. So some so=
rt of restriction on this could be useful.&nbsp; One approach could be to i=
nsist that the data sender should ensure that the map being transmitted is =
for in-window data, as per the receiver advertised window. A receiver shoul=
d anyhow be willing to store the maps for in-window data to deal with packe=
t loss. For example, when a window of data segments (say 1 to 64) is transm=
itted, each carrying its corresponding map, and segment-1 is lost, the maps=
 for the remaining 63 need to be stored till the lost segment is retransmit=
ted. Of course, in this case the maps will be stored at the receiver side a=
long with their corresponding data. But the need to store multiple maps for=
 in-window data would still be there.</div><br><div><span style=3D"color: #=
000000; font-family: 'arial' , 'helvetica' , sans-serif; font-size: 16px; f=
ont-style: normal; font-weight: normal; letter-spacing: normal; line-height=
: 20.8px; text-indent: 0px; text-transform: none; white-space: normal; word=
-spacing: 0px; float: none; background-color: #ffffff; display: inline;" da=
ta-mce-style=3D"color: #000000; font-family: 'arial' , 'helvetica' , sans-s=
erif; font-size: 16px; font-style: normal; font-weight: normal; letter-spac=
ing: normal; line-height: 20.8px; text-indent: 0px; text-transform: none; w=
hite-space: normal; word-spacing: 0px; float: none; background-color: #ffff=
ff; display: inline;">The problem with the proposed change (restriction) is=
 that a data sender may find it difficult, in case a need arise to slightly=
 delay the map delivery by few segments, i.e., sending some data first with=
out map, and then send the corresponding map in a later segment, as shown b=
elow:</span><br></div><br><div><p class=3D"MsoNormal" style=3D"color: #0000=
00; font-family: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16p=
x; font-style: normal; font-weight: normal; letter-spacing: normal; line-he=
ight: normal; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: #ffffff;" data-mce-style=
=3D"color: #000000; font-family: 'segoe ui' , 'lucida sans' , sans-serif; f=
ont-size: 14.16px; font-style: normal; font-weight: normal; letter-spacing:=
 normal; line-height: normal; text-indent: 0px; text-transform: none; white=
-space: normal; word-spacing: 0px; margin: 0px; background-color: #ffffff;"=
><span lang=3D"EN-US" style=3D"font-size: 10pt;" data-mce-style=3D"font-siz=
e: 10pt;">subflow-1:&nbsp; &nbsp; &nbsp; segment-1&nbsp;&nbsp;&nbsp; &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; segment-3&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; segment-4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; segment-7</span></p><p class=3D"MsoNormal" style=3D"col=
or: #000000; font-family: 'segoe ui' , 'lucida sans' , sans-serif; font-siz=
e: 14.16px; font-style: normal; font-weight: normal; letter-spacing: normal=
; line-height: normal; text-indent: 0px; text-transform: none; white-space:=
 normal; word-spacing: 0px; margin: 0px; background-color: #ffffff;" data-m=
ce-style=3D"color: #000000; font-family: 'segoe ui' , 'lucida sans' , sans-=
serif; font-size: 14.16px; font-style: normal; font-weight: normal; letter-=
spacing: normal; line-height: normal; text-indent: 0px; text-transform: non=
e; white-space: normal; word-spacing: 0px; margin: 0px; background-color: #=
ffffff;"><span lang=3D"EN-US" style=3D"font-size: 10pt;" data-mce-style=3D"=
font-size: 10pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;bytes=
:1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; bytes:201-30=
0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;bytes:301-400 &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; bytes:601-700</span></p><p cla=
ss=3D"MsoNormal" style=3D"color: #000000; font-family: 'segoe ui' , 'lucida=
 sans' , sans-serif; font-size: 14.16px; font-style: normal; font-weight: n=
ormal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-=
transform: none; white-space: normal; word-spacing: 0px; margin: 0px; backg=
round-color: #ffffff;" data-mce-style=3D"color: #000000; font-family: 'sego=
e ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-style: normal;=
 font-weight: normal; letter-spacing: normal; line-height: normal; text-ind=
ent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; mar=
gin: 0px; background-color: #ffffff;"><span lang=3D"EN-US" style=3D"font-si=
ze: 10pt;" data-mce-style=3D"font-size: 10pt;">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;no map &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map fo=
r 1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 201-400 &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; map for 601-700</span></p><p class=
=3D"MsoNormal" style=3D"color: #000000; font-family: 'segoe ui' , 'lucida s=
ans' , sans-serif; font-size: 14.16px; font-style: normal; font-weight: nor=
mal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-tr=
ansform: none; white-space: normal; word-spacing: 0px; margin: 0px; backgro=
und-color: #ffffff;" data-mce-style=3D"color: #000000; font-family: 'segoe =
ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-style: normal; f=
ont-weight: normal; letter-spacing: normal; line-height: normal; text-inden=
t: 0px; text-transform: none; white-space: normal; word-spacing: 0px; margi=
n: 0px; background-color: #ffffff;"><span lang=3D"EN-US" style=3D"font-size=
: 10pt;" data-mce-style=3D"font-size: 10pt;"><br></span></p><p class=3D"Mso=
Normal" style=3D"color: #000000; font-family: 'segoe ui' , 'lucida sans' , =
sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; le=
tter-spacing: normal; line-height: normal; text-indent: 0px; text-transform=
: none; white-space: normal; word-spacing: 0px; margin: 0px; background-col=
or: #ffffff;" data-mce-style=3D"color: #000000; font-family: 'segoe ui' , '=
lucida sans' , sans-serif; font-size: 14.16px; font-style: normal; font-wei=
ght: normal; letter-spacing: normal; line-height: normal; text-indent: 0px;=
 text-transform: none; white-space: normal; word-spacing: 0px; margin: 0px;=
 background-color: #ffffff;"><span lang=3D"EN-US" style=3D"font-size: 10pt;=
" data-mce-style=3D"font-size: 10pt;"><br></span></p><p class=3D"MsoNormal"=
 style=3D"color: #000000; font-family: 'segoe ui' , 'lucida sans' , sans-se=
rif; font-size: 14.16px; font-style: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; text-indent: 0px; text-transform: none;=
 white-space: normal; word-spacing: 0px; margin: 0px; background-color: #ff=
ffff;" data-mce-style=3D"color: #000000; font-family: 'segoe ui' , 'lucida =
sans' , sans-serif; font-size: 14.16px; font-style: normal; font-weight: no=
rmal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-t=
ransform: none; white-space: normal; word-spacing: 0px; margin: 0px; backgr=
ound-color: #ffffff;"><br></p><p class=3D"MsoNormal" style=3D"color: #00000=
0; font-family: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px=
; font-style: normal; font-weight: normal; letter-spacing: normal; line-hei=
ght: normal; text-indent: 0px; text-transform: none; white-space: normal; w=
ord-spacing: 0px; margin: 0px; background-color: #ffffff;" data-mce-style=
=3D"color: #000000; font-family: 'segoe ui' , 'lucida sans' , sans-serif; f=
ont-size: 14.16px; font-style: normal; font-weight: normal; letter-spacing:=
 normal; line-height: normal; text-indent: 0px; text-transform: none; white=
-space: normal; word-spacing: 0px; margin: 0px; background-color: #ffffff;"=
><span lang=3D"EN-US" style=3D"font-size: 10pt;" data-mce-style=3D"font-siz=
e: 10pt;">subflow-2:&nbsp; &nbsp; &nbsp; &nbsp;segment-2&nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-5 &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-6 &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-8</spa=
n></p><p class=3D"MsoNormal" style=3D"color: #000000; font-family: 'segoe u=
i' , 'lucida sans' , sans-serif; font-size: 14.16px; font-style: normal; fo=
nt-weight: normal; letter-spacing: normal; line-height: normal; text-indent=
: 0px; text-transform: none; white-space: normal; word-spacing: 0px; margin=
: 0px; background-color: #ffffff;" data-mce-style=3D"color: #000000; font-f=
amily: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-st=
yle: normal; font-weight: normal; letter-spacing: normal; line-height: norm=
al; text-indent: 0px; text-transform: none; white-space: normal; word-spaci=
ng: 0px; margin: 0px; background-color: #ffffff;"><span lang=3D"EN-US" styl=
e=3D"font-size: 10pt;" data-mce-style=3D"font-size: 10pt;">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bytes: 101-200 &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; bytes:401-500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bytes: 501-600 &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp;bytes:701-800&nbsp;&nbsp;&nbsp;</span></p><p =
class=3D"MsoNormal" style=3D"color: #000000; font-family: 'segoe ui' , 'luc=
ida sans' , sans-serif; font-size: 14.16px; font-style: normal; font-weight=
: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; te=
xt-transform: none; white-space: normal; word-spacing: 0px; margin: 0px; ba=
ckground-color: #ffffff;" data-mce-style=3D"color: #000000; font-family: 's=
egoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-style: norm=
al; font-weight: normal; letter-spacing: normal; line-height: normal; text-=
indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; =
margin: 0px; background-color: #ffffff;"><span lang=3D"EN-US" style=3D"font=
-size: 10pt;" data-mce-style=3D"font-size: 10pt;">&nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 101-200 &=
nbsp; &nbsp; &nbsp; map for 401-600 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;no map &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp;map for 701-800</span></p><p class=3D"MsoNor=
mal" style=3D"color: #000000; font-family: 'segoe ui' , 'lucida sans' , san=
s-serif; font-size: 14.16px; font-style: normal; font-weight: normal; lette=
r-spacing: normal; line-height: normal; text-indent: 0px; text-transform: n=
one; white-space: normal; word-spacing: 0px; margin: 0px; background-color:=
 #ffffff;" data-mce-style=3D"color: #000000; font-family: 'segoe ui' , 'luc=
ida sans' , sans-serif; font-size: 14.16px; font-style: normal; font-weight=
: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; te=
xt-transform: none; white-space: normal; word-spacing: 0px; margin: 0px; ba=
ckground-color: #ffffff;"><span lang=3D"EN-US" style=3D"font-size: 10pt;" d=
ata-mce-style=3D"font-size: 10pt;"></span><br></p><p class=3D"MsoNormal" st=
yle=3D"color: #000000; font-family: 'segoe ui' , 'lucida sans' , sans-serif=
; font-size: 14.16px; font-style: normal; font-weight: normal; letter-spaci=
ng: normal; line-height: normal; text-indent: 0px; text-transform: none; wh=
ite-space: normal; word-spacing: 0px; margin: 0px; background-color: #fffff=
f;" data-mce-style=3D"color: #000000; font-family: 'segoe ui' , 'lucida san=
s' , sans-serif; font-size: 14.16px; font-style: normal; font-weight: norma=
l; letter-spacing: normal; line-height: normal; text-indent: 0px; text-tran=
sform: none; white-space: normal; word-spacing: 0px; margin: 0px; backgroun=
d-color: #ffffff;"><span lang=3D"EN-US" style=3D"font-size: 10pt;" data-mce=
-style=3D"font-size: 10pt;"></span><br></p>In the above case, segment-1 goe=
s without map and its map is included later in segment-3, the next data seg=
ment in the same subflow. Further, &nbsp;in the above scheduling pattern, t=
he map in segment-3 cannot cover the &nbsp;data in segment-1 and segment-3,=
 as some &nbsp;data in between (segment-2) is transmitted through another s=
ubflow.&nbsp; With the proposed change, the map in segment-3 will become in=
valid and this will eventually break subflow-1, though this could be a corn=
er case.</div><br><div>The question at this stage is why would segment-1 be=
 transmitted without its map. In the case of bidirectional data transfer, t=
here could be a need to pack both timestamp and SACK &nbsp;options in a dat=
a segment, i.e., piggybacking of &nbsp;SACK with data. If we consider that =
timestamp takes 12 bytes and SACK, even with single block, &nbsp;takes anot=
her 10 bytes, the remaining 18 bytes option space is not adequate to carry =
data sequence signal with map, especially when DSN is 64 bit long. So the d=
elivery of either of the two (SACK or map) would be delayed.</div><br><div>=
As far as I understand, RFC 2018 (TCP Selective Acknowledgement Options) im=
plies that SACK should not be delayed. It states "If sent at all, SACK opti=
ons SHOULD be included in all ACKs which do not ACK the highest sequence nu=
mber in the data receiver's queue". It also says "If data receiver generate=
s SACK options under any circumstance, it SHOULD generate them under all pe=
rmitted circumstances". &nbsp; So, as part of meeting the RFC 2018 requirem=
ents, if the combination of SACK and timestamp is given preference over DSS=
, data segments could be transmitted without their map.&nbsp;</div><br><div=
>Another case of delaying map could arise if the data sender prefers to sen=
d ADD_ADDR option, instead of map, in a data segment. It is nice that ADD_A=
DDR option can be delivered reliably in a pure ACK, but I think this is not=
 the case with DSS at present.</div><br><div>If we adopt the proposed chang=
e, I think it might also be helpful to spell out how the receiver is suppos=
ed to behave, if it gets maps not meeting the MUST condition in the propose=
d change.&nbsp; For example termination of the subflow with MP_TCPRST optio=
n (section 3.6 in RFC 6824-bis) with appropriate reason code and T flag val=
ue to intimate the data sender the cause for subflow termination.&nbsp;&nbs=
p;</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</div></div><div>With regard=
s,</div><br><div>Anil<br><br><div>Please can members of the WG express whet=
her they are happy with these changes, or concerned.</div><br><div>Best reg=
ards,</div><div>Alan</div><br><br>_________________________________________=
______<br>multipathtcp mailing list<br><a href=3D"mailto:multipathtcp@ietf.=
org" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20norefe=
rrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%=
20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"=
_blank" data-mce-href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.or=
g</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=
=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofoll=
ow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"_blank" =
data-mce-href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp">https:=
//www.ietf.org/mailman/listinfo/multipathtcp</a></div></div></div></div></d=
iv></div></div></div></div></div><br></div></div></div><br><br>____________=
___________________________________<br>multipathtcp mailing list<br><a href=
=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noopener%20noreferrer%2=
0nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofo=
llow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow no=
opener noreferrer" target=3D"_blank" data-mce-href=3D"mailto:multipathtcp@i=
etf.org">multipathtcp@ietf.org</a><br><a href=3D"https://www.ietf.org/mailm=
an/listinfo/multipathtcp" rel=3D"noreferrer%20nofollow%20noopener%20norefer=
rer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%2=
0nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofoll=
ow noopener noreferrer" target=3D"_blank" data-mce-href=3D"https://www.ietf=
.org/mailman/listinfo/multipathtcp">https://www.ietf.org/mailman/listinfo/m=
ultipathtcp</a><br></blockquote></div></div></div></div></div></div><br></d=
iv></div><br></div></blockquote></div></div></div></div></div></div></div><=
/div></div></div><br></div></div>
<br>=
=0A<br>=
</body></html>
--=_6184590f-def9-44a6-95c2-01124c52e68f--



From nobody Wed Feb  5 13:19:38 2020
Return-Path: <alan.ford@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 864D212011A for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 13:19:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0ut0QVFVRFPc for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 13:19:34 -0800 (PST)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 AFB5D1200A4 for <multipathtcp@ietf.org>; Wed,  5 Feb 2020 13:19:33 -0800 (PST)
Received: by mail-wm1-x332.google.com with SMTP id p17so4568779wma.1 for <multipathtcp@ietf.org>; Wed, 05 Feb 2020 13:19:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=PBK9RPvWmFi5iUzOOWdqfoCN62e5ltTP2iUXy5JyKvY=; b=QkROrI0fZ3b3wZzyCnnDC38GeZ1lio3OgNcKsyW4BEOULRJDUmECk0iW36dmaJ/WAS fbY18D9svHreAE7Mo+jjW+rcX4ge+0iNc+mE+uflqn62I7938wRthMhyCfT8gcAJWFTn zLOErzslFkQYH937px8fQPb1sfYb2MIgQw0wcRaS+xA7Dw3NKJK57oFeQM/GpRGZAfud H0js2hNIxOa8hf8fS4JtPruJk4o8dJ3ussaygfJOHoI4LiubF1ZgJBENTPkWgo+CqFbh qwyq6j4D35/5bEIWn2OsRvpLH97pHbJmOtOmIocWW5Z4E1TuGjDu6fLrLqmicBKrQHoi qWKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=PBK9RPvWmFi5iUzOOWdqfoCN62e5ltTP2iUXy5JyKvY=; b=pK5IQU7+hCQng+d66zZsaT3yuDW2xxMnsxaDy9wsC46MCa9Ybvu8Gk204btDAWgoIV ICOe9WpO+IUpDJ4sRt2x8liQBOZC7fU9QYmqy4Bn1Y9xailYn4Vabn/HcOwHOlnLOjw5 CdCG862prYsCFFhhGShSsY/wqX6vAUHVEa5fj1898jhMGmzzfmuAMcTLRC7PD5piqGza jlkw8ISVD/NERN4QFnPJ9rizrK1TH9PvnWHpC3wiZ3MrR8h9f98abyM1OjOmKwFOCC1h tBDrUuJja4XH0xSeYaPvQaj21CGR0n4C5geOPm153ci8dAPZwVonBTAYhxeCDnyDxFFj fhFw==
X-Gm-Message-State: APjAAAVtsVE+WlVeg/2n28W5KAIn7QKUDFbRZO9zOavywALkm0Aud0vl irJrfL6PfbXH58wy9A5V+aK3lr7dPFQ=
X-Google-Smtp-Source: APXvYqwrspvyCuqoe77vk1xQpQBzKg+GFHq7BUUUFO/qMqQN4haI7K8Vb4aI1iGbwYma+fhPpaiyRA==
X-Received: by 2002:a1c:1d02:: with SMTP id d2mr8186055wmd.185.1580937571928;  Wed, 05 Feb 2020 13:19:31 -0800 (PST)
Received: from alan-mbp.lan (107.35.115.87.dyn.plus.net. [87.115.35.107]) by smtp.gmail.com with ESMTPSA id y7sm8424076wmd.1.2020.02.05.13.19.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Feb 2020 13:19:31 -0800 (PST)
From: Alan Ford <alan.ford@gmail.com>
Message-Id: <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_13CEBEF9-781A-4F5D-9247-70AB9FC5986E"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 5 Feb 2020 21:19:29 +0000
In-Reply-To: <620489655.29573797.1580915365031@csir4pi.in>
Cc: Yoshifumi Nishida <nsd.ietf@gmail.com>, multipathtcp <multipathtcp@ietf.org>
To: V Anil Kumar <anil@csir4pi.in>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/yEsYloq1jz-QcN9IczVyUFX9llY>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2020 21:19:37 -0000

--Apple-Mail=_13CEBEF9-781A-4F5D-9247-70AB9FC5986E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Anil,

This would not be forbidden if the mapping was carried on a pure ACK =
with no data.

I do see the point here: if a packet of 1000 bytes contains 500 bytes of =
one mapping and 500 bytes of another mapping, then only one DSM would =
appear on one packet, leaving the mapping for the second 500 bytes to be =
carried somewhere else - the only option being a pure ACK. But this kind =
of scenario would be extremely rare and I would imagine any =
implementation would just split into two 500 byte segments each with the =
PSH flag set. I don=E2=80=99t think we need to spell this out in the =
spec however.

Regards,
Alan

> On 5 Feb 2020, at 15:09, V Anil Kumar <anil@csir4pi.in> wrote:
>=20
> Hi Yoshi,
>=20
> Please see in line.
>=20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com>
> To: "V Anil Kumar" <anil@csir4pi.in>
> Cc: "alan ford" <alan.ford@gmail.com>, "multipathtcp" =
<multipathtcp@ietf.org>
> Sent: Tuesday, February 4, 2020 1:08:45 PM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
>=20
> Hi Anil,
>=20
> Thanks for pointing it out. I overlooked this one.
> This looks an interesting point.
>=20
> It seems to me that whether RST is happen or not depends on the size =
of receive window according to the text.
> If the receive window size is big enough to accommodate segment 1 and =
segment 3, the text "Implementations MAY hold onto such unmapped data =
for a short while in the expectation that a mapping will arrive shortly. =
" can be applied to the segment 1. As a result, the segment 1 won't be =
discarded.=20
>=20
> Yes.  So, segment 1 may be kept in the data receiver's buffer in =
expectation that its mapping will arrive shortly. And in the example =
that we are referring to, the data sender will not be able to include =
the map for the data in segment 1 in segment 3 or any higher segment.
>=20
> Regards,
>=20
> Anil
>=20
> However, this might be contradict with the new texts Alan proposed? =
Or, am I missing something?
>=20
> Thanks,
> --
> Yoshi
>=20
>=20
>=20
> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Yoshi,
>=20
> Thanks for this point. In fact, I had initially not thought of a =
scenario, where the map is being delivered through a retransmitted data =
packet while its first transmission did not include the map. Now I am =
just seeing the document (RFC 6824-bis) in this context.
>=20
> My understanding is that in scenarios like what I described in my =
previous mail, RST is likely to happen whether we explicitly state so or =
not. Please see the paragraph containing the below text in RFC 6824-bis. =
=20
>=20
> "If a mapping for that subflow-level sequence space does not arrive =
within a receive window of data, that subflow SHOULD be treated as =
broken, closed with a RST, and any unmapped data silently discarded."
>=20
> if we assume that the map is included while retransmitting the data =
(even though the first transmission did not contain the map for some =
reasons),  we could argue that RST could be avoided provided that the =
retransmission is triggered within a receive window of data. But the =
question here would be how and when will the retransmission take place. =
In this case, the subflow may not initiate the retransmission of data by =
its own (i.e., no retransmission due to three duplicate ACKs or RTO =
expiry at subflow level) as there is no segment loss at subflow level =
sequence space. So there could be a high possibility of RST happening =
even before the map delivery through retransmission.=20
>=20
> With regards,=20
>=20
> Anil
> =20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, =
"multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> Sent: Saturday, February 1, 2020 3:39:51 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
>=20
> Hi Anil,
>=20
> I have a question about your proposed text.
> I am actually wondering if we really want to terminate connection =
here.=20
>=20
> The packets without proper mappings will be treated as invalid and =
will be discarded.=20
> If an implementation failed to attach proper mapping for some reasons =
(e.g. option space), it might be able to attach the proper one when it =
retransmits the packets. This also looks ok to me.
>=20
> I don't have strong preference for this. But, do we have a reason to =
terminate connection?
>=20
> Thanks,
> --
> Yoshi
>=20
> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi,
>=20
> I have some points related to the  modifications (Change 2) being =
proposed on data sequence map. Please see them inline. Though I am =
putting forward the below points, if the consensus is in favour of the =
proposed change for reducing implementation complexity, I am also OK =
with that as well.=20
>=20
> From: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> To: multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> Sent: Thursday, January 2, 2020 4:21:32 AM
> Subject: [multipathtcp] RFC6824bis edits based on implementation =
feedback
>=20
> Hi all,
> We=E2=80=99d love to get this to a state of completion as soon as =
possible, and to this end I am starting a new thread on this topic. In =
discussion with the chairs, it is possible to make the desired changes =
in AUTH48 as long as there is WG consensus. The discussion so far has =
been fairly limited in terms of participation.
>=20
> I would ask the chairs please if it was possible to specify a time =
bound for this discussion and a default conclusion.
>=20
> Regarding the changes, in summary, there are two areas where changes =
have been requested by the implementation community. As we are the IETF =
we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so =
ease of implementing standards-compliant code is strongly desirable. =
However, we do not wish to reduce functionality agreed by the IETF =
community if it is considered a required feature by the community.
>=20
>=20
> Change 1
>=20
> Change the sentence reading:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).=20
>=20
> To:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data =
Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for the =
MP_CAPABLE (which is the first octet of the data sequence space).
>=20
> What this means:
>=20
> The current text is concerned only with ensuring a path is MPTCP =
capable, and so only cares that DSS option occurs on a data packet. =
However, the MP_CAPABLE option is defined to occupy the first octet of =
data sequence space and thus, if analogous to TCP, must be acknowledged. =
>=46rom an implementation point of view it would make sense not to have =
this hanging around forever and instead define it is acknowledged at the =
connection level as soon as received. This change ensures the first data =
packet also DATA_ACKs this MP_CAPABLE octet.
>=20
>=20
> Change 2
>=20
> Change the sentence reading:
>=20
>    A Data Sequence Mapping does not need to be included in every MPTCP =
packet, as long as the subflow sequence space in that packet is covered =
by a mapping known at the receiver.
>=20
> To:
>=20
>    The mapping provided by a Data Sequence Mapping MUST apply to some =
or all of the subflow sequence space in the TCP segment which carries =
the option. It does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.
>=20
> What this means:
>=20
> The current text does not place any restrictions on where a mapping =
could appear. In theory a sender could define a thousand different =
mappings up front, send them all, and expect a receiver to store this =
and reassemble data according to these mappings as it arrives. Indeed, =
this was never explicitly disallowed since it =E2=80=9Cmight have been =
useful=E2=80=9D. The implementation community, however, has expressed =
concerns over the difficulty of implementing this open-endedly. How many =
mappings is it reasonable to store? Is there a DoS risk here? Instead, =
it has been requested that thee specification restricts the placement of =
the DSS option to being within the subflow sequence space to which it =
applies.
>=20
> Below are my comments on this. I had shared some of these points in a =
previous thread that you had initiated in the same context.=20
>=20
> Transmitting large number of non-contiguous data sequence maps could =
be a misbehaviour (map-flooding), though it is not clear whether this =
can go to the extent of causing a potential DoS to the data receiver. So =
some sort of restriction on this could be useful.  One approach could be =
to insist that the data sender should ensure that the map being =
transmitted is for in-window data, as per the receiver advertised =
window. A receiver should anyhow be willing to store the maps for =
in-window data to deal with packet loss. For example, when a window of =
data segments (say 1 to 64) is transmitted, each carrying its =
corresponding map, and segment-1 is lost, the maps for the remaining 63 =
need to be stored till the lost segment is retransmitted. Of course, in =
this case the maps will be stored at the receiver side along with their =
corresponding data. But the need to store multiple maps for in-window =
data would still be there.
>=20
> The problem with the proposed change (restriction) is that a data =
sender may find it difficult, in case a need arise to slightly delay the =
map delivery by few segments, i.e., sending some data first without map, =
and then send the corresponding map in a later segment, as shown below:
>=20
> subflow-1:      segment-1                   segment-3                  =
  segment-4                       segment-7
>                       bytes:1-100                 bytes:201-300        =
      bytes:301-400                 bytes:601-700
>                       no map                        map for 1-100      =
        map for 201-400             map for 601-700
>=20
>=20
>=20
> subflow-2:       segment-2                  segment-5                  =
   segment-6                       segment-8
>                        bytes: 101-200           bytes:401-500          =
     bytes: 501-600                bytes:701-800  =20
>                        map for 101-200       map for 401-600           =
 no map                            map for 701-800
>=20
>=20
> In the above case, segment-1 goes without map and its map is included =
later in segment-3, the next data segment in the same subflow. Further,  =
in the above scheduling pattern, the map in segment-3 cannot cover the  =
data in segment-1 and segment-3, as some  data in between (segment-2) is =
transmitted through another subflow.  With the proposed change, the map =
in segment-3 will become invalid and this will eventually break =
subflow-1, though this could be a corner case.
>=20
> The question at this stage is why would segment-1 be transmitted =
without its map. In the case of bidirectional data transfer, there could =
be a need to pack both timestamp and SACK  options in a data segment, =
i.e., piggybacking of  SACK with data. If we consider that timestamp =
takes 12 bytes and SACK, even with single block,  takes another 10 =
bytes, the remaining 18 bytes option space is not adequate to carry data =
sequence signal with map, especially when DSN is 64 bit long. So the =
delivery of either of the two (SACK or map) would be delayed.
>=20
> As far as I understand, RFC 2018 (TCP Selective Acknowledgement =
Options) implies that SACK should not be delayed. It states "If sent at =
all, SACK options SHOULD be included in all ACKs which do not ACK the =
highest sequence number in the data receiver's queue". It also says "If =
data receiver generates SACK options under any circumstance, it SHOULD =
generate them under all permitted circumstances".   So, as part of =
meeting the RFC 2018 requirements, if the combination of SACK and =
timestamp is given preference over DSS, data segments could be =
transmitted without their map.=20
>=20
> Another case of delaying map could arise if the data sender prefers to =
send ADD_ADDR option, instead of map, in a data segment. It is nice that =
ADD_ADDR option can be delivered reliably in a pure ACK, but I think =
this is not the case with DSS at present.
>=20
> If we adopt the proposed change, I think it might also be helpful to =
spell out how the receiver is supposed to behave, if it gets maps not =
meeting the MUST condition in the proposed change.  For example =
termination of the subflow with MP_TCPRST option (section 3.6 in RFC =
6824-bis) with appropriate reason code and T flag value to intimate the =
data sender the cause for subflow termination. =20
>         =20
> With regards,
>=20
> Anil
>=20
> Please can members of the WG express whether they are happy with these =
changes, or concerned.
>=20
> Best regards,
> Alan
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
>=20
>=20
>=20
>=20
>=20


--Apple-Mail=_13CEBEF9-781A-4F5D-9247-70AB9FC5986E
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; line-break: after-white-space;" class=3D"">Hi =
Anil,<div class=3D""><br class=3D""></div><div class=3D"">This would not =
be forbidden if the mapping was carried on a pure ACK with no =
data.</div><div class=3D""><br class=3D""></div><div class=3D"">I do see =
the point here: if a packet of 1000 bytes contains 500 bytes of one =
mapping and 500 bytes of another mapping, then only one DSM would appear =
on one packet, leaving the mapping for the second 500 bytes to be =
carried somewhere else - the only option being a pure ACK. But this kind =
of scenario would be extremely rare and I would imagine any =
implementation would just split into two 500 byte segments each with the =
PSH flag set. I don=E2=80=99t think we need to spell this out in the =
spec however.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Regards,</div><div class=3D"">Alan<br class=3D""><div =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 5 Feb 2020, at 15:09, V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" class=3D"">anil@csir4pi.in</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D""><div style=3D"font-family: arial, helvetica, sans-serif; =
font-size: style=3D" font-size:=3D"" 12pt;=3D"" color:=3D"" #000000"=3D"" =
class=3D""><div data-marker=3D"__QUOTED_TEXT__" class=3D""><div =
style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" =
data-mce-style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" =
class=3D""><div class=3D""><div style=3D"font-family: 'arial' , =
'helvetica' , sans-serif;" data-mce-style=3D"font-family: 'arial' , =
'helvetica' , sans-serif;" class=3D""><div class=3D""><div =
style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" =
data-mce-style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" =
class=3D""><div class=3D"">Hi Yoshi,</div><br class=3D""><div =
class=3D"">Please see in line.</div><br class=3D""><hr id=3D"zwchr" =
class=3D""><div class=3D""><b class=3D"">From: </b>"Yoshifumi Nishida" =
&lt;<a href=3D"mailto:nsd.ietf@gmail.com" =
class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: =
</b>"V Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" =
class=3D"">anil@csir4pi.in</a>&gt;<br class=3D""><b class=3D"">Cc: =
</b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b class=3D"">Sent:=
 </b>Tuesday, February 4, 2020 1:08:45 PM<br class=3D""><b =
class=3D"">Subject: </b>Re: [multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></div><br class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"">Hi Anil,</div><br class=3D""><div =
class=3D"">Thanks for pointing it out. I overlooked this one.</div><div =
class=3D"">This looks an interesting point.<br class=3D""></div><br =
class=3D""><div class=3D"">It seems to me that whether RST is happen or =
not depends on the size of receive window according to the text.<br =
class=3D""></div><div class=3D"">If the receive window size is big =
enough to accommodate&nbsp;segment 1 and segment 3, the text "<span =
style=3D"font-size: 13.3333px;" data-mce-style=3D"color: #000000; =
font-size: 13.3333px;" class=3D"">Implementations MAY hold onto such =
unmapped data for a short while in&nbsp;</span><span style=3D"font-size: =
13.3333px;" data-mce-style=3D"color: #000000; font-size: 13.3333px;" =
class=3D"">the expectation that a mapping will arrive shortly. =
"&nbsp;</span>can be applied to the segment 1. As a result, the segment =
1 won't be discarded.&nbsp;</div><br class=3D""><div class=3D""><em =
class=3D"">Yes. &nbsp;So, segment 1 may be kept in the data receiver's =
buffer in expectation that its mapping will arrive shortly. And in the =
example that we are referring to, the data sender will not be able to =
include the map for the data in segment 1 in segment 3 or any higher =
segment.</em></div><br class=3D""><div class=3D""><em =
class=3D"">Regards,</em></div><br class=3D""><div class=3D""><em =
class=3D"">Anil</em></div><br class=3D""><div class=3D"">However, this =
might be contradict with the new texts Alan proposed? Or, am I missing =
something?</div><br class=3D""><div class=3D"">Thanks,</div><div =
class=3D"">--</div><div class=3D"">Yoshi</div><br class=3D""><br =
class=3D""><br class=3D""><div class=3D""><div dir=3D"ltr" class=3D"">On =
Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:anil@csir4pi.in" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; border-left: =
1px solid #cccccc; padding-left: 1ex;" data-mce-style=3D"margin: 0px 0px =
0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;"><div =
class=3D""><div class=3D""><div class=3D""><div style=3D"font-family: =
'arial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-family: =
'arial' , 'helvetica' , sans-serif;" class=3D""><div class=3D"">Hi =
Yoshi,</div><br class=3D""><div class=3D"">Thanks for this point. In =
fact, I had initially not thought of a scenario, where the map is being =
delivered through a retransmitted data packet while its first =
transmission did not include the map. Now I am just seeing the document =
(RFC 6824-bis) in this context.</div><br class=3D""><div class=3D"">My =
understanding is that in scenarios like what I described in my previous =
mail, RST is likely to happen whether we explicitly state so or not. =
Please see the paragraph containing the below text in RFC 6824-bis. =
&nbsp;</div><br class=3D""><div class=3D"">"If a mapping for that =
subflow-level sequence space does not arrive within a receive window of =
data, that subflow SHOULD be treated as broken, closed with a RST, and =
any unmapped data silently discarded."</div><br class=3D""><div =
class=3D"">if we assume that the map is included while retransmitting =
the data (even though the first transmission did not contain the map for =
some reasons), &nbsp;we could argue that RST could be avoided provided =
that the retransmission is triggered within a receive window of data. =
But the question here would be how and when will the retransmission take =
place. In this case, the subflow may not initiate the retransmission of =
data by its own (i.e., no retransmission due to three duplicate ACKs or =
RTO expiry at subflow level) as there is no segment loss at subflow =
level sequence space. So there could be a high possibility of RST =
happening even before the map delivery through =
retransmission.&nbsp;</div><br class=3D""><div class=3D"">With =
regards,&nbsp;</div><br class=3D""><div class=3D"">Anil</div><div =
class=3D"">&nbsp;</div><hr =
id=3D"gmail-m_218086596951724501gmail-m_2982267033577902985zwchr" =
class=3D""><div class=3D""><b class=3D"">From: </b>"Yoshifumi Nishida" =
&lt;<a href=3D"mailto:nsd.ietf@gmail.com" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:nsd.ietf@gmail.com" =
class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: =
</b>"V Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:anil@csir4pi.in" =
class=3D"">anil@csir4pi.in</a>&gt;<br class=3D""><b class=3D"">Cc: =
</b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:alan.ford@gmail.com" =
class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:multipathtcp@ietf.org" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b class=3D"">Sent:=
 </b>Saturday, February 1, 2020 3:39:51 AM<br class=3D""><b =
class=3D"">Subject: </b>Re: [multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></div><br class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"">Hi Anil,</div><br class=3D""><div =
class=3D"">I have a question about your proposed text.</div><div =
class=3D""><div class=3D"">I am actually wondering if we really want to =
terminate connection here.&nbsp;</div></div><br class=3D""><div =
class=3D"">The packets without proper mappings will be treated as =
invalid and will be discarded.&nbsp;</div><div class=3D"">If an =
implementation failed to attach proper mapping for some reasons (e.g. =
option space), it might be able to attach the proper one when it =
retransmits the packets. This also looks ok to me.</div><br =
class=3D""><div class=3D"">I don't have strong preference for this. But, =
do we have a reason to terminate connection?</div><br class=3D""><div =
class=3D"">Thanks,</div><div class=3D"">--<br class=3D""></div><div =
class=3D"">Yoshi</div><br class=3D""><div class=3D""><div dir=3D"ltr" =
class=3D"">On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:anil@csir4pi.in" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; border-left: =
1px solid #cccccc; padding-left: 1ex;" data-mce-style=3D"margin: 0px 0px =
0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;"><div =
class=3D""><div class=3D""><div class=3D""><div style=3D"font-family: =
'arial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-family: =
'arial' , 'helvetica' , sans-serif;" class=3D""><div class=3D""><span =
style=3D"font-size: 12pt; line-height: 1.3;" data-mce-style=3D"font-size: =
12pt; line-height: 1.3;" class=3D"">Hi,</span><br class=3D""></div><div =
class=3D""><div style=3D"font-family: 'arial' , 'helvetica' , =
sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , =
sans-serif;" class=3D""><div style=3D"font-family: 'arial' , 'helvetica' =
, sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , =
sans-serif;" class=3D""><div style=3D"font-family: 'arial' , 'helvetica' =
, sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , =
sans-serif;" class=3D""><div style=3D"font-family: 'arial' , 'helvetica' =
, sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , =
sans-serif;" class=3D""><div style=3D"font-family: 'arial' , 'helvetica' =
, sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , =
sans-serif;" class=3D""><div style=3D"font-family: 'arial' , 'helvetica' =
, sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , =
sans-serif;" class=3D""><div style=3D"font-family: 'arial' , 'helvetica' =
, sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , =
sans-serif;" class=3D""><br class=3D""><div class=3D"">I have some =
points related to the &nbsp;modifications (Change 2) being proposed on =
data sequence map. Please see them inline.&nbsp;<span =
style=3D"font-family: arial, helvetica, sans-serif; font-size: 16px; =
font-style: normal; font-weight: 400; letter-spacing: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; background-color: rgb(255, 255, 255); float: none; =
display: inline;" data-mce-style=3D"color: #000000; font-family: 'arial' =
, 'helvetica' , sans-serif; font-size: 16px; font-style: normal; =
font-weight: 400; letter-spacing: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
background-color: #ffffff; float: none; display: inline;" =
class=3D"">Though I am putting forward the below points, if the =
consensus is in favour of the proposed change for reducing =
implementation complexity, I am also OK with that as =
well.&nbsp;</span><br class=3D""></div><br class=3D""><hr =
id=3D"gmail-m_218086596951724501gmail-m_2982267033577902985gmail-m_7687184=
382299596774zwchr" class=3D""><div class=3D""><b class=3D"">From: =
</b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:alan.ford@gmail.com" =
class=3D"">alan.ford@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: =
</b><a href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:multipathtcp@ietf.org" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><b class=3D"">Sent: =
</b>Thursday, January 2, 2020 4:21:32 AM<br class=3D""><b =
class=3D"">Subject: </b>[multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></div><br class=3D""><div =
class=3D"">Hi all,<br class=3D""><div class=3D"">We=E2=80=99d love to =
get this to a state of completion as soon as possible, and to this end I =
am starting a new thread on this topic. In discussion with the chairs, =
it <i class=3D"">is </i>possible to make the desired changes in AUTH48 =
as long as there is WG consensus. The discussion so far has been fairly =
limited in terms of participation.</div><br class=3D""><div class=3D"">I =
would ask the chairs please if it was possible to specify a time bound =
for this discussion and a default conclusion.</div><br class=3D""><div =
class=3D"">Regarding the changes, in summary, there are two areas where =
changes have been requested by the implementation community. As we are =
the IETF we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D =
and so ease of implementing standards-compliant code is strongly =
desirable. However, we do not wish to reduce functionality agreed by the =
IETF community if it is considered a required feature by the =
community.</div><br class=3D""><br class=3D""><div class=3D""><b =
class=3D"">Change 1</b></div><div class=3D""><b class=3D""><br =
class=3D""></b></div><div class=3D"">Change the sentence reading:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B has data to =
send first, then the reliable delivery of the ACK + MP_CAPABLE can be =
inferred by the receipt of this data with an MPTCP Data Sequence Signal =
(DSS) option (Section 3.3).&nbsp;<br class=3D""></i><br class=3D"">To:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B has data to =
send first, then the reliable delivery of the ACK + MP_CAPABLE is =
ensured by the receipt of this data with an MPTCP Data Sequence Signal =
(DSS) option (Section 3.3) containing a DATA_ACK for the MP_CAPABLE =
(which is the first octet of the data sequence&nbsp;space).<br =
class=3D""></i><br class=3D""></div><div class=3D"">What this =
means:</div><br class=3D""><div class=3D"">The current text is concerned =
only with ensuring a path is MPTCP capable, and so only cares that DSS =
option occurs on a data packet. However, the MP_CAPABLE option is =
defined to occupy the first octet of data sequence space and thus, if =
analogous to TCP, must be acknowledged. &gt;=46rom an implementation =
point of view it would make sense not to have this hanging around =
forever and instead define it is acknowledged at the connection level as =
soon as received. This change ensures the first data packet also =
DATA_ACKs this MP_CAPABLE octet.</div><br class=3D""><br class=3D""><div =
class=3D""><b class=3D"">Change 2</b></div><div class=3D""><b =
class=3D""><br class=3D""></b></div><div class=3D"">Change the sentence =
reading:<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;A Data =
Sequence Mapping does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.</i><br class=3D""><br class=3D"">To:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;The mapping =
provided by a Data Sequence Mapping MUST apply to some or all of the =
subflow sequence space in the TCP segment which carries the option. It =
does not need to be included in every MPTCP packet, as long as the =
subflow sequence space in that packet is covered by a mapping known at =
the receiver.<br class=3D""></i><br class=3D"">What this means:</div><br =
class=3D""><div class=3D"">The current text does not place any =
restrictions on where a mapping could appear. In theory a sender could =
define a thousand different mappings up front, send them all, and expect =
a receiver to store this and reassemble data according to these mappings =
as it arrives. Indeed, this was never explicitly disallowed since it =
=E2=80=9Cmight have been useful=E2=80=9D. The implementation community, =
however, has expressed concerns over the difficulty of implementing this =
open-endedly. How many mappings is it reasonable to store? Is there a =
DoS risk here? Instead, it has been requested that thee specification =
restricts the placement of the DSS option to being within the subflow =
sequence space to which it applies.</div><br class=3D""><div =
class=3D"">Below are my comments on this. I had shared some of these =
points in a previous thread that you had initiated in the same =
context.&nbsp;</div><br class=3D""><div class=3D"">Transmitting large =
number of non-contiguous data sequence maps could be a misbehaviour =
(map-flooding), though it is not clear whether this can go to the extent =
of causing a potential DoS to the data receiver. So some sort of =
restriction on this could be useful.&nbsp; One approach could be to =
insist that the data sender should ensure that the map being transmitted =
is for in-window data, as per the receiver advertised window. A receiver =
should anyhow be willing to store the maps for in-window data to deal =
with packet loss. For example, when a window of data segments (say 1 to =
64) is transmitted, each carrying its corresponding map, and segment-1 =
is lost, the maps for the remaining 63 need to be stored till the lost =
segment is retransmitted. Of course, in this case the maps will be =
stored at the receiver side along with their corresponding data. But the =
need to store multiple maps for in-window data would still be =
there.</div><br class=3D""><div class=3D""><span style=3D"font-family: =
arial, helvetica, sans-serif; font-size: 16px; font-style: normal; =
font-weight: normal; letter-spacing: normal; line-height: 20.8px; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; float: none; background-color: rgb(255, 255, 255); =
display: inline;" data-mce-style=3D"color: #000000; font-family: 'arial' =
, 'helvetica' , sans-serif; font-size: 16px; font-style: normal; =
font-weight: normal; letter-spacing: normal; line-height: 20.8px; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; float: none; background-color: #ffffff; display: =
inline;" class=3D"">The problem with the proposed change (restriction) =
is that a data sender may find it difficult, in case a need arise to =
slightly delay the map delivery by few segments, i.e., sending some data =
first without map, and then send the corresponding map in a later =
segment, as shown below:</span><br class=3D""></div><br class=3D""><div =
class=3D""><div style=3D"font-family: &quot;segoe ui&quot;, &quot;lucida =
sans&quot;, sans-serif; font-size: 14.16px; font-style: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: rgb(255, 255, 255);" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt;" =
data-mce-style=3D"font-size: 10pt;" class=3D"">subflow-1:&nbsp; &nbsp; =
&nbsp; segment-1&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; segment-3&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; segment-4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-7</span></div><div =
style=3D"font-family: &quot;segoe ui&quot;, &quot;lucida sans&quot;, =
sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; margin: =
0px; background-color: rgb(255, 255, 255);" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt;" data-mce-style=3D"font-size: =
10pt;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;bytes:1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; bytes:201-300 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;bytes:301-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; bytes:601-700</span></div><div style=3D"font-family: =
&quot;segoe ui&quot;, &quot;lucida sans&quot;, sans-serif; font-size: =
14.16px; font-style: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; margin: 0px; background-color: =
rgb(255, 255, 255);" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt;" data-mce-style=3D"font-size: 10pt;" class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;no =
map &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;map for 1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;map for 201-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
map for 601-700</span></div><div style=3D"font-family: &quot;segoe =
ui&quot;, &quot;lucida sans&quot;, sans-serif; font-size: 14.16px; =
font-style: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; margin: 0px; background-color: =
rgb(255, 255, 255);" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt;" data-mce-style=3D"font-size: 10pt;" class=3D""><br =
class=3D""></span></div><div style=3D"font-family: &quot;segoe ui&quot;, =
&quot;lucida sans&quot;, sans-serif; font-size: 14.16px; font-style: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: rgb(255, 255, 255);" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt;" =
data-mce-style=3D"font-size: 10pt;" class=3D""><br =
class=3D""></span></div><div style=3D"font-family: &quot;segoe ui&quot;, =
&quot;lucida sans&quot;, sans-serif; font-size: 14.16px; font-style: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: rgb(255, 255, 255);" =
class=3D""><br class=3D""></div><div style=3D"font-family: &quot;segoe =
ui&quot;, &quot;lucida sans&quot;, sans-serif; font-size: 14.16px; =
font-style: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; margin: 0px; background-color: =
rgb(255, 255, 255);" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt;" data-mce-style=3D"font-size: 10pt;" class=3D"">subflow-2:&nbsp; =
&nbsp; &nbsp; &nbsp;segment-2&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; segment-5 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; segment-6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-8</span></div><div =
style=3D"font-family: &quot;segoe ui&quot;, &quot;lucida sans&quot;, =
sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; margin: =
0px; background-color: rgb(255, 255, 255);" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt;" data-mce-style=3D"font-size: =
10pt;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bytes: 101-200 &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; bytes:401-500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bytes: 501-600 &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;bytes:701-800&nbsp;&nbsp;&nbsp;</span></div><div =
style=3D"font-family: &quot;segoe ui&quot;, &quot;lucida sans&quot;, =
sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; margin: =
0px; background-color: rgb(255, 255, 255);" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt;" data-mce-style=3D"font-size: =
10pt;" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 101-200 &nbsp; &nbsp; &nbsp; =
map for 401-600 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;no map &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;map for 701-800</span></div><div style=3D"font-family:=
 &quot;segoe ui&quot;, &quot;lucida sans&quot;, sans-serif; font-size: =
14.16px; font-style: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; margin: 0px; background-color: =
rgb(255, 255, 255);" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10pt;" data-mce-style=3D"font-size: 10pt;" class=3D""></span><br =
class=3D""></div><div style=3D"font-family: &quot;segoe ui&quot;, =
&quot;lucida sans&quot;, sans-serif; font-size: 14.16px; font-style: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; margin: 0px; background-color: rgb(255, 255, 255);" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt;" =
data-mce-style=3D"font-size: 10pt;" class=3D""></span><br =
class=3D""></div>In the above case, segment-1 goes without map and its =
map is included later in segment-3, the next data segment in the same =
subflow. Further, &nbsp;in the above scheduling pattern, the map in =
segment-3 cannot cover the &nbsp;data in segment-1 and segment-3, as =
some &nbsp;data in between (segment-2) is transmitted through another =
subflow.&nbsp; With the proposed change, the map in segment-3 will =
become invalid and this will eventually break subflow-1, though this =
could be a corner case.</div><br class=3D""><div class=3D"">The question =
at this stage is why would segment-1 be transmitted without its map. In =
the case of bidirectional data transfer, there could be a need to pack =
both timestamp and SACK &nbsp;options in a data segment, i.e., =
piggybacking of &nbsp;SACK with data. If we consider that timestamp =
takes 12 bytes and SACK, even with single block, &nbsp;takes another 10 =
bytes, the remaining 18 bytes option space is not adequate to carry data =
sequence signal with map, especially when DSN is 64 bit long. So the =
delivery of either of the two (SACK or map) would be delayed.</div><br =
class=3D""><div class=3D"">As far as I understand, RFC 2018 (TCP =
Selective Acknowledgement Options) implies that SACK should not be =
delayed. It states "If sent at all, SACK options SHOULD be included in =
all ACKs which do not ACK the highest sequence number in the data =
receiver's queue". It also says "If data receiver generates SACK options =
under any circumstance, it SHOULD generate them under all permitted =
circumstances". &nbsp; So, as part of meeting the RFC 2018 requirements, =
if the combination of SACK and timestamp is given preference over DSS, =
data segments could be transmitted without their map.&nbsp;</div><br =
class=3D""><div class=3D"">Another case of delaying map could arise if =
the data sender prefers to send ADD_ADDR option, instead of map, in a =
data segment. It is nice that ADD_ADDR option can be delivered reliably =
in a pure ACK, but I think this is not the case with DSS at =
present.</div><br class=3D""><div class=3D"">If we adopt the proposed =
change, I think it might also be helpful to spell out how the receiver =
is supposed to behave, if it gets maps not meeting the MUST condition in =
the proposed change.&nbsp; For example termination of the subflow with =
MP_TCPRST option (section 3.6 in RFC 6824-bis) with appropriate reason =
code and T flag value to intimate the data sender the cause for subflow =
termination.&nbsp;&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;</div></div><div class=3D"">With regards,</div><br =
class=3D""><div class=3D"">Anil<br class=3D""><br class=3D""><div =
class=3D"">Please can members of the WG express whether they are happy =
with these changes, or concerned.</div><br class=3D""><div class=3D"">Best=
 regards,</div><div class=3D"">Alan</div><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:multipathtcp@ietf.org" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" =
data-mce-href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a></div></d=
iv></div></div></div></div></div></div></div></div><br =
class=3D""></div></div></div><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer nofollow noopener noreferrer" =
target=3D"_blank" data-mce-href=3D"mailto:multipathtcp@ietf.org" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
rel=3D"noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener=
%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20n=
oreferrer%20nofollow%20noopener%20noreferrer nofollow noopener =
noreferrer" target=3D"_blank" =
data-mce-href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br =
class=3D""></blockquote></div></div></div></div></div></div><br =
class=3D""></div></div><br =
class=3D""></div></blockquote></div></div></div></div></div></div></div></=
div></div></div><br class=3D""></div></div>
<br class=3D"">
<br class=3D""></div></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_13CEBEF9-781A-4F5D-9247-70AB9FC5986E--


From nobody Wed Feb  5 13:59:30 2020
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA0712083D for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 13:59:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.002
X-Spam-Level: 
X-Spam-Status: No, score=-7.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 Zz1U_9QwdmFG for <multipathtcp@ietfa.amsl.com>; Wed,  5 Feb 2020 13:59:25 -0800 (PST)
Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) (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 829571200A4 for <multipathtcp@ietf.org>; Wed,  5 Feb 2020 13:59:25 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id 015LvQoY063992; Wed, 5 Feb 2020 13:59:18 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : date : from : to : cc : subject : message-id : references : in-reply-to; s=20180706; bh=DxD6JpmJ3nvPWt1ccV2KBp7eGh2qHuTQO8193j70YaI=; b=hPW/4jdUIwMZFz+x6DA1AXAZBRYvi84LW9S3FkIWpvP0iqfq4IURDtmPMiuvKPG0cThY Sd0X/bzwIek/sml8yYt7p4bnuNBKiJ3UPgSe35aeGl6Ic6INtzd4jwEk/EEFUblZxJX4 Pb9ukeN9ReHYJOihFhVThap0+Ef883Yarz6AAxn3jpBX8VF2nmZSRVZMLryFDaVK5++/ 3NKr5sufuTz2pi47LKIJbYO6mng5uqo/JBj4p8mO2Do3SImGyYPvkhRNPmj3KccgFYh6 2wCpqKUg0UIffVWdQbnAZcZm22N7CYOocG0pm6aXRd2Bw/iamtoWHq9vnmWN58Oo1D8+ fg== 
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2xykb2waes-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 05 Feb 2020 13:59:18 -0800
Received: from nwk-mmpp-sz11.apple.com (nwk-mmpp-sz11.apple.com [17.128.115.155]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.1.20190704 64bit (built Jul  4 2019)) with ESMTPS id <0Q59001NE12T8CH0@rn-mailsvcp-mta-lapp02.rno.apple.com>;  Wed, 05 Feb 2020 13:59:17 -0800 (PST)
Received: from process_milters-daemon.nwk-mmpp-sz11.apple.com by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May  7 2019)) id <0Q59002000FIT400@nwk-mmpp-sz11.apple.com>; Wed, 05 Feb 2020 13:59:17 -0800 (PST)
X-Va-A: 
X-Va-T-CD: 3617872cb080ac0182d9b2453d56adc6
X-Va-E-CD: ae422271a38913bbedae93e9e9d60fc7
X-Va-R-CD: a5d4677ae470b25e3a5d2ab1ded2428a
X-Va-CD: 0
X-Va-ID: a7e06e1d-2116-4dd5-9fde-fc247969eef8
X-V-A: 
X-V-T-CD: 3617872cb080ac0182d9b2453d56adc6
X-V-E-CD: ae422271a38913bbedae93e9e9d60fc7
X-V-R-CD: a5d4677ae470b25e3a5d2ab1ded2428a
X-V-CD: 0
X-V-ID: 139c962f-aa48-409c-99ca-b95e57152075
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2020-02-05_06:,, signatures=0
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-disposition: inline
Content-type: text/plain; charset=utf-8
Received: from localhost ([17.234.37.1]) by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May  7 2019)) with ESMTPSA id <0Q59001DT12QQA20@nwk-mmpp-sz11.apple.com>; Wed, 05 Feb 2020 13:59:15 -0800 (PST)
Sender: cpaasch@apple.com
Date: Wed, 05 Feb 2020 13:59:14 -0800
From: Christoph Paasch <cpaasch@apple.com>
To: Alan Ford <alan.ford@gmail.com>
Cc: V Anil Kumar <anil@csir4pi.in>, multipathtcp <multipathtcp@ietf.org>
Message-id: <20200205215914.GS33105@MacBook-Pro-64.local>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com>
In-reply-to: <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com>
User-Agent: Mutt/1.12.2 (2019-09-21)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-02-05_06:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/WJtF6GQiw4-PYUTWTIE3Q2PLLCw>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2020 21:59:29 -0000

On 05/02/20 - 21:19:29, Alan Ford wrote:
> Hi Anil,
> 
> This would not be forbidden if the mapping was carried on a pure ACK with no data.
> 
> I do see the point here: if a packet of 1000 bytes contains 500 bytes of one mapping and 500 bytes of another mapping, then only one DSM would appear on one packet, leaving the mapping for the second 500 bytes to be carried somewhere else - the only option being a pure ACK. But this kind of scenario would be extremely rare and I would imagine any implementation would just split into two 500 byte segments each with the PSH flag set. I don’t think we need to spell this out in the spec however.

Yes, an implementation would just send 2 segments each 500 bytes.

Because, if the mapping is sent on a pure ACK, the implementation needs to
retransmit that pure ACK (based on some timer) to make sure that it reaches
the receiver. Which basically means that we are making the pure ACK reliable.
Sure, everything is possible in software but the complexity would be too big.

Thus, easiest solution is to simply send 2 500 byte segments.


Christoph


> 
> Regards,
> Alan
> 
> > On 5 Feb 2020, at 15:09, V Anil Kumar <anil@csir4pi.in> wrote:
> > 
> > Hi Yoshi,
> > 
> > Please see in line.
> > 
> > From: "Yoshifumi Nishida" <nsd.ietf@gmail.com>
> > To: "V Anil Kumar" <anil@csir4pi.in>
> > Cc: "alan ford" <alan.ford@gmail.com>, "multipathtcp" <multipathtcp@ietf.org>
> > Sent: Tuesday, February 4, 2020 1:08:45 PM
> > Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
> > 
> > Hi Anil,
> > 
> > Thanks for pointing it out. I overlooked this one.
> > This looks an interesting point.
> > 
> > It seems to me that whether RST is happen or not depends on the size of receive window according to the text.
> > If the receive window size is big enough to accommodate segment 1 and segment 3, the text "Implementations MAY hold onto such unmapped data for a short while in the expectation that a mapping will arrive shortly. " can be applied to the segment 1. As a result, the segment 1 won't be discarded. 
> > 
> > Yes.  So, segment 1 may be kept in the data receiver's buffer in expectation that its mapping will arrive shortly. And in the example that we are referring to, the data sender will not be able to include the map for the data in segment 1 in segment 3 or any higher segment.
> > 
> > Regards,
> > 
> > Anil
> > 
> > However, this might be contradict with the new texts Alan proposed? Or, am I missing something?
> > 
> > Thanks,
> > --
> > Yoshi
> > 
> > 
> > 
> > On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in <mailto:anil@csir4pi.in>> wrote:
> > Hi Yoshi,
> > 
> > Thanks for this point. In fact, I had initially not thought of a scenario, where the map is being delivered through a retransmitted data packet while its first transmission did not include the map. Now I am just seeing the document (RFC 6824-bis) in this context.
> > 
> > My understanding is that in scenarios like what I described in my previous mail, RST is likely to happen whether we explicitly state so or not. Please see the paragraph containing the below text in RFC 6824-bis.  
> > 
> > "If a mapping for that subflow-level sequence space does not arrive within a receive window of data, that subflow SHOULD be treated as broken, closed with a RST, and any unmapped data silently discarded."
> > 
> > if we assume that the map is included while retransmitting the data (even though the first transmission did not contain the map for some reasons),  we could argue that RST could be avoided provided that the retransmission is triggered within a receive window of data. But the question here would be how and when will the retransmission take place. In this case, the subflow may not initiate the retransmission of data by its own (i.e., no retransmission due to three duplicate ACKs or RTO expiry at subflow level) as there is no segment loss at subflow level sequence space. So there could be a high possibility of RST happening even before the map delivery through retransmission. 
> > 
> > With regards, 
> > 
> > Anil
> >  
> > From: "Yoshifumi Nishida" <nsd.ietf@gmail.com <mailto:nsd.ietf@gmail.com>>
> > To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> > Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, "multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> > Sent: Saturday, February 1, 2020 3:39:51 AM
> > Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
> > 
> > Hi Anil,
> > 
> > I have a question about your proposed text.
> > I am actually wondering if we really want to terminate connection here. 
> > 
> > The packets without proper mappings will be treated as invalid and will be discarded. 
> > If an implementation failed to attach proper mapping for some reasons (e.g. option space), it might be able to attach the proper one when it retransmits the packets. This also looks ok to me.
> > 
> > I don't have strong preference for this. But, do we have a reason to terminate connection?
> > 
> > Thanks,
> > --
> > Yoshi
> > 
> > On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in <mailto:anil@csir4pi.in>> wrote:
> > Hi,
> > 
> > I have some points related to the  modifications (Change 2) being proposed on data sequence map. Please see them inline. Though I am putting forward the below points, if the consensus is in favour of the proposed change for reducing implementation complexity, I am also OK with that as well. 
> > 
> > From: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> > To: multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> > Sent: Thursday, January 2, 2020 4:21:32 AM
> > Subject: [multipathtcp] RFC6824bis edits based on implementation feedback
> > 
> > Hi all,
> > We’d love to get this to a state of completion as soon as possible, and to this end I am starting a new thread on this topic. In discussion with the chairs, it is possible to make the desired changes in AUTH48 as long as there is WG consensus. The discussion so far has been fairly limited in terms of participation.
> > 
> > I would ask the chairs please if it was possible to specify a time bound for this discussion and a default conclusion.
> > 
> > Regarding the changes, in summary, there are two areas where changes have been requested by the implementation community. As we are the IETF we obviously have strong focus on “running code” and so ease of implementing standards-compliant code is strongly desirable. However, we do not wish to reduce functionality agreed by the IETF community if it is considered a required feature by the community.
> > 
> > 
> > Change 1
> > 
> > Change the sentence reading:
> > 
> >    If B has data to send first, then the reliable delivery of the ACK + MP_CAPABLE can be inferred by the receipt of this data with an MPTCP Data Sequence Signal (DSS) option (Section 3.3). 
> > 
> > To:
> > 
> >    If B has data to send first, then the reliable delivery of the ACK + MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for the MP_CAPABLE (which is the first octet of the data sequence space).
> > 
> > What this means:
> > 
> > The current text is concerned only with ensuring a path is MPTCP capable, and so only cares that DSS option occurs on a data packet. However, the MP_CAPABLE option is defined to occupy the first octet of data sequence space and thus, if analogous to TCP, must be acknowledged. >From an implementation point of view it would make sense not to have this hanging around forever and instead define it is acknowledged at the connection level as soon as received. This change ensures the first data packet also DATA_ACKs this MP_CAPABLE octet.
> > 
> > 
> > Change 2
> > 
> > Change the sentence reading:
> > 
> >    A Data Sequence Mapping does not need to be included in every MPTCP packet, as long as the subflow sequence space in that packet is covered by a mapping known at the receiver.
> > 
> > To:
> > 
> >    The mapping provided by a Data Sequence Mapping MUST apply to some or all of the subflow sequence space in the TCP segment which carries the option. It does not need to be included in every MPTCP packet, as long as the subflow sequence space in that packet is covered by a mapping known at the receiver.
> > 
> > What this means:
> > 
> > The current text does not place any restrictions on where a mapping could appear. In theory a sender could define a thousand different mappings up front, send them all, and expect a receiver to store this and reassemble data according to these mappings as it arrives. Indeed, this was never explicitly disallowed since it “might have been useful”. The implementation community, however, has expressed concerns over the difficulty of implementing this open-endedly. How many mappings is it reasonable to store? Is there a DoS risk here? Instead, it has been requested that thee specification restricts the placement of the DSS option to being within the subflow sequence space to which it applies.
> > 
> > Below are my comments on this. I had shared some of these points in a previous thread that you had initiated in the same context. 
> > 
> > Transmitting large number of non-contiguous data sequence maps could be a misbehaviour (map-flooding), though it is not clear whether this can go to the extent of causing a potential DoS to the data receiver. So some sort of restriction on this could be useful.  One approach could be to insist that the data sender should ensure that the map being transmitted is for in-window data, as per the receiver advertised window. A receiver should anyhow be willing to store the maps for in-window data to deal with packet loss. For example, when a window of data segments (say 1 to 64) is transmitted, each carrying its corresponding map, and segment-1 is lost, the maps for the remaining 63 need to be stored till the lost segment is retransmitted. Of course, in this case the maps will be stored at the receiver side along with their corresponding data. But the need to store multiple maps for in-window data would still be there.
> > 
> > The problem with the proposed change (restriction) is that a data sender may find it difficult, in case a need arise to slightly delay the map delivery by few segments, i.e., sending some data first without map, and then send the corresponding map in a later segment, as shown below:
> > 
> > subflow-1:      segment-1                   segment-3                    segment-4                       segment-7
> >                       bytes:1-100                 bytes:201-300              bytes:301-400                 bytes:601-700
> >                       no map                        map for 1-100              map for 201-400             map for 601-700
> > 
> > 
> > 
> > subflow-2:       segment-2                  segment-5                     segment-6                       segment-8
> >                        bytes: 101-200           bytes:401-500               bytes: 501-600                bytes:701-800   
> >                        map for 101-200       map for 401-600            no map                            map for 701-800
> > 
> > 
> > In the above case, segment-1 goes without map and its map is included later in segment-3, the next data segment in the same subflow. Further,  in the above scheduling pattern, the map in segment-3 cannot cover the  data in segment-1 and segment-3, as some  data in between (segment-2) is transmitted through another subflow.  With the proposed change, the map in segment-3 will become invalid and this will eventually break subflow-1, though this could be a corner case.
> > 
> > The question at this stage is why would segment-1 be transmitted without its map. In the case of bidirectional data transfer, there could be a need to pack both timestamp and SACK  options in a data segment, i.e., piggybacking of  SACK with data. If we consider that timestamp takes 12 bytes and SACK, even with single block,  takes another 10 bytes, the remaining 18 bytes option space is not adequate to carry data sequence signal with map, especially when DSN is 64 bit long. So the delivery of either of the two (SACK or map) would be delayed.
> > 
> > As far as I understand, RFC 2018 (TCP Selective Acknowledgement Options) implies that SACK should not be delayed. It states "If sent at all, SACK options SHOULD be included in all ACKs which do not ACK the highest sequence number in the data receiver's queue". It also says "If data receiver generates SACK options under any circumstance, it SHOULD generate them under all permitted circumstances".   So, as part of meeting the RFC 2018 requirements, if the combination of SACK and timestamp is given preference over DSS, data segments could be transmitted without their map. 
> > 
> > Another case of delaying map could arise if the data sender prefers to send ADD_ADDR option, instead of map, in a data segment. It is nice that ADD_ADDR option can be delivered reliably in a pure ACK, but I think this is not the case with DSS at present.
> > 
> > If we adopt the proposed change, I think it might also be helpful to spell out how the receiver is supposed to behave, if it gets maps not meeting the MUST condition in the proposed change.  For example termination of the subflow with MP_TCPRST option (section 3.6 in RFC 6824-bis) with appropriate reason code and T flag value to intimate the data sender the cause for subflow termination.  
> >          
> > With regards,
> > 
> > Anil
> > 
> > Please can members of the WG express whether they are happy with these changes, or concerned.
> > 
> > Best regards,
> > Alan
> > 
> > 
> > _______________________________________________
> > multipathtcp mailing list
> > multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> > https://www.ietf.org/mailman/listinfo/multipathtcp <https://www.ietf.org/mailman/listinfo/multipathtcp>
> > 
> > 
> > _______________________________________________
> > multipathtcp mailing list
> > multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> > https://www.ietf.org/mailman/listinfo/multipathtcp <https://www.ietf.org/mailman/listinfo/multipathtcp>
> > 
> > 
> > 
> > 
> > 
> 

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


From nobody Thu Feb  6 10:10:55 2020
Return-Path: <prvs=2986dd730=anil@csir4pi.in>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29CD112011C for <multipathtcp@ietfa.amsl.com>; Thu,  6 Feb 2020 10:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 nlyxiIHnjHcT for <multipathtcp@ietfa.amsl.com>; Thu,  6 Feb 2020 10:10:49 -0800 (PST)
Received: from vastu64.nic.in (vastu64.nic.in [164.100.2.64]) (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 9294A12010C for <multipathtcp@ietf.org>; Thu,  6 Feb 2020 10:10:47 -0800 (PST)
IronPort-PHdr: =?us-ascii?q?9a23=3AINNBrxOiRl11PrpJn2Ql6mtUPXoX/o7sNwtQ0K?= =?us-ascii?q?IMzox0K/z7psbcNUDSrc9gkEXOFd2Cra4d16yL6Ou5ATVIoc7Y9ixbK9oUD1?= =?us-ascii?q?5NoP5VtjRoONSCB0z/IayiRA0BN+MGamVY+WqmO1NeAsf0ag6aiHSz6TkPBk?= =?us-ascii?q?e3blItdaz6FYHIksu4yf259YHNbAVUnjq9Zq55IAmroQnLucQanIRvJrwxxx?= =?us-ascii?q?bHrXdEZvhayX51Ll6Xgxrw+9288ZF+/yleof4t69JMXaDndKkkULJUCygrPX?= =?us-ascii?q?oo78PxrxnDSgWP5noYUmoIlxdDHhbI4hLnUJrvqyX2ruVy1jWUMs3wVrA0RC?= =?us-ascii?q?+t77x3Rx/yiScILCA2/WfKgcFtlq1boRahpxtiw47IZYyeKfRzcr/Bcd4cWG?= =?us-ascii?q?FMRdhaWTBfDYygbosPF+sBMvher4nhvFsFsB+yCRCxCO/z1jNEg3n71rA43e?= =?us-ascii?q?s8CwHLxAIuEdIQvnrXrtr1OrocXu+pw6nJyjvDc+hb1i3h5IXSaB0su+2AUL?= =?us-ascii?q?B2fMHMyUcvDQTFjlCIpIPqIjiYyuINs2mf7+F9UOyvlmsnpBtrojOywcojkI?= =?us-ascii?q?/JhoMRyl3f6Sp524c1Jce3RU5jYN6oCppQtyeDOoZwX8gsTWZouCMgxb0Hv5?= =?us-ascii?q?62ZCkKx4o7xx7RcfCHdJKI4h3lWe2MIjl4nGpodK+jixqu60StyfHwWtOp3F?= =?us-ascii?q?pXtCZIndrBumgQ2xHR98SLUPpw8lq71TuO0w3f8OJJLEMsmabGN5It3qQ8m5?= =?us-ascii?q?kPvUjZAyP7mV/6gLKYe0gg4uSk9vjrbqn8qpKfK4N4kBzyP6U0lsChDuk0Lg?= =?us-ascii?q?4DVHWB9+umzr3s50j5Ta1Pjv0xj6bWrojXJd8epq6lGw9V1Zsj6wqnAzemzt?= =?us-ascii?q?sYmX4HIUpKeBKfiIjpNF/PLO33APulhVSskStky+rHPr3nGpnNL37Dn6n9fb?= =?us-ascii?q?tl9kJQ1BY/wcpc6p5IEL0NPe//VlX+udHbFhM5Nha7w+fjCNVzzIMeXmePD7?= =?us-ascii?q?eDP6PUsF+I4vkiLPWXZI8UojbwJOAl5//0gX84n18RZbOp0ocPaHCkAvRmJF?= =?us-ascii?q?2UbmDogtgbF2cGpAQ+TOvwiFKfSjNTaHOyULg95jE/Eo6pEYDDRoW1irybwC?= =?us-ascii?q?i7BoFWZnxBCl2UF3fobJiLV+0NaC2MPs9hnCcJVbekS4A71BGusBX2xKZgLu?= =?us-ascii?q?rR4icYr47s1MBp5+3PkhE/7Tl0D9mZ02GRTmF0hnkHRyM23KBjvUN90kyO0a?= =?us-ascii?q?lmjPxEG9xf/fRJUh01Nc2U8+svQfn2UwSJUNCTRBzuFtyiCDd3QNUrz/cBZk?= =?us-ascii?q?98H5OpiRWVjASwBLpAqfSiAp0wuoHB2nHrb5J0zXfC/KI6jkN6WsoJNGvw1f?= =?us-ascii?q?03zBTaG4OcyxbRrK2tb6lJmXeVrGo=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2G9AAAEUDxe/zALUGRmGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBEQEBAQEBAQEBAQEBgXuBJVMxbFYBHhIqCoQLb4gUhhOCEYl?= =?us-ascii?q?ikVUECQEBAgEBAQEBIAEKCgIBAQKDeUUCgj4kOBMCAwEMAQEBBAEBAQEBBQM?= =?us-ascii?q?BAQECaYRrTAyCOykBcXEBAQEBAQEBAQEBAQEBAQEBAQEBFgJDVRIBAR0BAQE?= =?us-ascii?q?BAgEBARgJRAcGBQULAgEIDQQEAQEBIAEGAwICIQYfCQgCBAoBCBSDE4JKAw4?= =?us-ascii?q?fAQUKrAV1gTIaAoUugnENghoGgTiMIxQGggCBEYMTPoEEgRdJAQGBPAcBATI?= =?us-ascii?q?kglqCXgSNWIorfYc1jkAyRIJEkhuERoJIiBCENQOLe5l2kWg4IyqBLk04O4J?= =?us-ascii?q?sUBiOMwMXhQiDXIVHOgExgSmKXgUMF4ELAYEPAQE?=
X-IPAS-Result: =?us-ascii?q?A2G9AAAEUDxe/zALUGRmGQEBAQEBAQEBAQEBAQEBAQEBE?= =?us-ascii?q?QEBAQEBAQEBAQEBgXuBJVMxbFYBHhIqCoQLb4gUhhOCEYlikVUECQEBAgEBA?= =?us-ascii?q?QEBIAEKCgIBAQKDeUUCgj4kOBMCAwEMAQEBBAEBAQEBBQMBAQECaYRrTAyCO?= =?us-ascii?q?ykBcXEBAQEBAQEBAQEBAQEBAQEBAQEBFgJDVRIBAR0BAQEBAgEBARgJRAcGB?= =?us-ascii?q?QULAgEIDQQEAQEBIAEGAwICIQYfCQgCBAoBCBSDE4JKAw4fAQUKrAV1gTIaA?= =?us-ascii?q?oUugnENghoGgTiMIxQGggCBEYMTPoEEgRdJAQGBPAcBATIkglqCXgSNWIorf?= =?us-ascii?q?Yc1jkAyRIJEkhuERoJIiBCENQOLe5l2kWg4IyqBLk04O4JsUBiOMwMXhQiDX?= =?us-ascii?q?IVHOgExgSmKXgUMF4ELAYEPAQE?=
X-IronPort-AV: E=McAfee;i="6000,8403,9523"; a="310094143"
X-IronPort-AV: E=Sophos;i="5.70,410,1574101800";  d="scan'208,217";a="310094143"
Received: from unknown (HELO gpogw14.nic.in) ([100.80.11.48]) by vastu11internal.nic.in with ESMTP; 06 Feb 2020 23:40:42 +0530
Received: from gpogw14.nic.in (localhost [127.0.0.1]) by gpogw14.nic.in (Postfix) with ESMTPS id C6672C096682; Thu,  6 Feb 2020 23:40:42 +0530 (IST)
Received: from localhost (localhost [127.0.0.1]) by gpogw14.nic.in (Postfix) with ESMTP id B88BCC096684; Thu,  6 Feb 2020 23:40:42 +0530 (IST)
X-Amavis-Modified: Mail body modified (using disclaimer) - gpogw14.nic.in
Received: from gpogw14.nic.in ([127.0.0.1]) by localhost (gpogw14.nic.in [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id t7e9tz2kcQWA; Thu,  6 Feb 2020 23:40:42 +0530 (IST)
Received: from gms281.nic.in (unknown [100.80.16.240]) by gpogw14.nic.in (Postfix) with ESMTP id 90D9EC096682; Thu,  6 Feb 2020 23:40:42 +0530 (IST)
Date: Thu, 6 Feb 2020 23:37:19 +0530 (IST)
From: V Anil Kumar <anil@csir4pi.in>
To: "Alan Ford" <alan.ford@gmail.com>
Cc: "Yoshifumi Nishida" <nsd.ietf@gmail.com>, "multipathtcp" <multipathtcp@ietf.org>
Message-ID: <1411057985.31281938.1581012439446@csir4pi.in>
In-Reply-To: <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="=_96570ff3-5078-4507-8307-761246f84160"
X-Originating-IP: [171.61.69.88, 100.80.16.139]
X-Mailer: Zimbra 8.8.9_GA_2044 (ZimbraWebClient - GC49 (Mac)/8.8.9_GA_2044)
Thread-Topic: RFC6824bis edits based on implementation feedback
Thread-Index: Pow9M2q1XFMWXPH0CBlyoEvzViFSuQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/sYp8RizNqXgNa4Nq7LzHorHzpsY>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2020 18:10:54 -0000

--=_96570ff3-5078-4507-8307-761246f84160
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Alan,=20

Thank you for your reply. I have two points to clarify. Please see them in =
line.=20

> From: "Alan Ford" <alan.ford@gmail.com>
> To: "V Anil Kumar" <anil@csir4pi.in>jk
> Cc: "Yoshifumi Nishida" <nsd.ietf@gmail.com>, "multipathtcp"
> <multipathtcp@ietf.org>
> Sent: Thursday, February 6, 2020 2:49:29 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feed=
back

> Hi Anil,

> This would not be forbidden if the mapping was carried on a pure ACK with=
 no
> data.

As far as I understand, delivery of DSM through pure ACK is not in the scop=
e of the current draft. If we intend to do this, we may need an approach si=
milar to the one proposed for delivery of ADD_ADDR option in pure ACK with =
reliability feature. So, packing DSM on pure ACK does not seem to be an opt=
ion at this stage.=20

> I do see the point here: if a packet of 1000 bytes contains 500 bytes of =
one
> mapping and 500 bytes of another mapping, then only one DSM would appear =
on one
> packet, leaving the mapping for the second 500 bytes to be carried somewh=
ere
> else - the only option being a pure ACK. But this kind of scenario would =
be
> extremely rare

Yes, I do agree that the scenario you mentioned above would be extremely ra=
re. In fact, I wonder whether such a situation (i.e., need to cover the byt=
es in a single packet with two different maps) would ever arise. Probably t=
here might be some corner cases, which I don't get it rightly now.=20

More importantly, the scenario that Yoshi and me are referring to is totall=
y different: the one I had given as part of my comments in response to the =
proposed change 2. In this scenario, which you could see in the trailing ma=
il, data segment-1 is transmitted without including its map, something whic=
h is permitted in the mptcp framework (6824 bis). I make this inference fro=
m the below text in 6824 bis:=20

"...even if a mapping does not exist from the subflow space to the data- le=
vel space, the data SHOULD still be ACKed at the subflow (if it is in-windo=
w). This data cannot, however, be acknowledged at the data level (Section 3=
.3.2) because its data sequence numbers are unknown. Implementations MAY ho=
ld onto such unmapped data for a short while in the expectation that a mapp=
ing will arrive shortly."=20

One option the data sender has at this stage is to include the map for data=
 in segment-1, in segment-3 (please see the two-subflow example I gave in r=
esponse to the change 2 you had proposed). But the proposed change does not=
 permit this. What would happen to subflow-1 in this case ?=20

With regards,=20

Anil=20

> and I would imagine any implementation would just split into two 500 byte
> segments each with the PSH flag set. I don=E2=80=99t think we need to spe=
ll this out in
> the spec however.

> Regards,
> Alan

>> On 5 Feb 2020, at 15:09, V Anil Kumar < [ mailto:anil@csir4pi.in |
>> anil@csir4pi.in ] > wrote:
>> Hi Yoshi,

>> Please see in line.

>> From: "Yoshifumi Nishida" < [ mailto:nsd.ietf@gmail.com | nsd.ietf@gmail=
.com ] >
>> To: "V Anil Kumar" < [ mailto:anil@csir4pi.in | anil@csir4pi.in ] >
>> Cc: "alan ford" < [ mailto:alan.ford@gmail.com | alan.ford@gmail.com ] >=
,
>> "multipathtcp" < [ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org =
] >
>> Sent: Tuesday, February 4, 2020 1:08:45 PM
>> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation fee=
dback

>> Hi Anil,

>> Thanks for pointing it out. I overlooked this one.
>> This looks an interesting point.

>> It seems to me that whether RST is happen or not depends on the size of =
receive
>> window according to the text.
>> If the receive window size is big enough to accommodate segment 1 and se=
gment 3,
>> the text " Implementations MAY hold onto such unmapped data for a short =
while
>> in the expectation that a mapping will arrive shortly. " can be applied =
to the
>> segment 1. As a result, the segment 1 won't be discarded.

>> Yes. So, segment 1 may be kept in the data receiver's buffer in expectat=
ion that
>> its mapping will arrive shortly. And in the example that we are referrin=
g to,
>> the data sender will not be able to include the map for the data in segm=
ent 1
>> in segment 3 or any higher segment.

>> Regards,

>> Anil

>> However, this might be contradict with the new texts Alan proposed? Or, =
am I
>> missing something?

>> Thanks,
>> --
>> Yoshi

>> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar < [ mailto:anil@csir4pi.in |
>> anil@csir4pi.in ] > wrote:

>>> Hi Yoshi,

>>> Thanks for this point. In fact, I had initially not thought of a scenar=
io, where
>>> the map is being delivered through a retransmitted data packet while it=
s first
>>> transmission did not include the map. Now I am just seeing the document=
 (RFC
>>> 6824-bis) in this context.

>>> My understanding is that in scenarios like what I described in my previ=
ous mail,
>>> RST is likely to happen whether we explicitly state so or not. Please s=
ee the
>>> paragraph containing the below text in RFC 6824-bis.

>>> "If a mapping for that subflow-level sequence space does not arrive wit=
hin a
>>> receive window of data, that subflow SHOULD be treated as broken, close=
d with a
>>> RST, and any unmapped data silently discarded."

>>> if we assume that the map is included while retransmitting the data (ev=
en though
>>> the first transmission did not contain the map for some reasons), we co=
uld
>>> argue that RST could be avoided provided that the retransmission is tri=
ggered
>>> within a receive window of data. But the question here would be how and=
 when
>>> will the retransmission take place. In this case, the subflow may not i=
nitiate
>>> the retransmission of data by its own (i.e., no retransmission due to t=
hree
>>> duplicate ACKs or RTO expiry at subflow level) as there is no segment l=
oss at
>>> subflow level sequence space. So there could be a high possibility of R=
ST
>>> happening even before the map delivery through retransmission.

>>> With regards,

>>> Anil

>>> From: "Yoshifumi Nishida" < [ mailto:nsd.ietf@gmail.com | nsd.ietf@gmai=
l.com ] >
>>> To: "V Anil Kumar" < [ mailto:anil@csir4pi.in | anil@csir4pi.in ] >
>>> Cc: "alan ford" < [ mailto:alan.ford@gmail.com | alan.ford@gmail.com ] =
>,
>>> "multipathtcp" < [ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org=
 ] >
>>> Sent: Saturday, February 1, 2020 3:39:51 AM
>>> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation fe=
edback

>>> Hi Anil,

>>> I have a question about your proposed text.
>>> I am actually wondering if we really want to terminate connection here.

>>> The packets without proper mappings will be treated as invalid and will=
 be
>>> discarded.
>>> If an implementation failed to attach proper mapping for some reasons (=
e.g.
>>> option space), it might be able to attach the proper one when it retran=
smits
>>> the packets. This also looks ok to me.

>>> I don't have strong preference for this. But, do we have a reason to te=
rminate
>>> connection?

>>> Thanks,
>>> --
>>> Yoshi

>>> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar < [ mailto:anil@csir4pi.i=
n |
>>> anil@csir4pi.in ] > wrote:

>>>> Hi,

>>>> I have some points related to the modifications (Change 2) being propo=
sed on
>>>> data sequence map. Please see them inline. Though I am putting forward=
 the
>>>> below points, if the consensus is in favour of the proposed change for=
 reducing
>>>> implementation complexity, I am also OK with that as well.

>>>> From: "alan ford" < [ mailto:alan.ford@gmail.com | alan.ford@gmail.com=
 ] >
>>>> To: [ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]
>>>> Sent: Thursday, January 2, 2020 4:21:32 AM
>>>> Subject: [multipathtcp] RFC6824bis edits based on implementation feedb=
ack

>>>> Hi all,
>>>> We=E2=80=99d love to get this to a state of completion as soon as poss=
ible, and to this
>>>> end I am starting a new thread on this topic. In discussion with the c=
hairs, it
>>>> is possible to make the desired changes in AUTH48 as long as there is =
WG
>>>> consensus. The discussion so far has been fairly limited in terms of
>>>> participation.

>>>> I would ask the chairs please if it was possible to specify a time bou=
nd for
>>>> this discussion and a default conclusion.

>>>> Regarding the changes, in summary, there are two areas where changes h=
ave been
>>>> requested by the implementation community. As we are the IETF we obvio=
usly have
>>>> strong focus on =E2=80=9Crunning code=E2=80=9D and so ease of implemen=
ting standards-compliant
>>>> code is strongly desirable. However, we do not wish to reduce function=
ality
>>>> agreed by the IETF community if it is considered a required feature by=
 the
>>>> community.

>>>> Change 1

>>>> Change the sentence reading:

>>>> If B has data to send first, then the reliable delivery of the ACK + M=
P_CAPABLE
>>>> can be inferred by the receipt of this data with an MPTCP Data Sequenc=
e Signal
>>>> (DSS) option (Section 3.3).

>>>> To:

>>>> If B has data to send first, then the reliable delivery of the ACK + M=
P_CAPABLE
>>>> is ensured by the receipt of this data with an MPTCP Data Sequence Sig=
nal (DSS)
>>>> option (Section 3.3) containing a DATA_ACK for the MP_CAPABLE (which i=
s the
>>>> first octet of the data sequence space).

>>>> What this means:

>>>> The current text is concerned only with ensuring a path is MPTCP capab=
le, and so
>>>> only cares that DSS option occurs on a data packet. However, the MP_CA=
PABLE
>>>> option is defined to occupy the first octet of data sequence space and=
 thus, if
>>>> analogous to TCP, must be acknowledged. >From an implementation point =
of view
>>>> it would make sense not to have this hanging around forever and instea=
d define
>>>> it is acknowledged at the connection level as soon as received. This c=
hange
>>>> ensures the first data packet also DATA_ACKs this MP_CAPABLE octet.

>>>> Change 2

>>>> Change the sentence reading:

>>>> A Data Sequence Mapping does not need to be included in every MPTCP pa=
cket, as
>>>> long as the subflow sequence space in that packet is covered by a mapp=
ing known
>>>> at the receiver.

>>>> To:

>>>> The mapping provided by a Data Sequence Mapping MUST apply to some or =
all of the
>>>> subflow sequence space in the TCP segment which carries the option. It=
 does not
>>>> need to be included in every MPTCP packet, as long as the subflow sequ=
ence
>>>> space in that packet is covered by a mapping known at the receiver.

>>>> What this means:

>>>> The current text does not place any restrictions on where a mapping co=
uld
>>>> appear. In theory a sender could define a thousand different mappings =
up front,
>>>> send them all, and expect a receiver to store this and reassemble data
>>>> according to these mappings as it arrives. Indeed, this was never expl=
icitly
>>>> disallowed since it =E2=80=9Cmight have been useful=E2=80=9D. The impl=
ementation community,
>>>> however, has expressed concerns over the difficulty of implementing th=
is
>>>> open-endedly. How many mappings is it reasonable to store? Is there a =
DoS risk
>>>> here? Instead, it has been requested that thee specification restricts=
 the
>>>> placement of the DSS option to being within the subflow sequence space=
 to which
>>>> it applies.

>>>> Below are my comments on this. I had shared some of these points in a =
previous
>>>> thread that you had initiated in the same context.

>>>> Transmitting large number of non-contiguous data sequence maps could b=
e a
>>>> misbehaviour (map-flooding), though it is not clear whether this can g=
o to the
>>>> extent of causing a potential DoS to the data receiver. So some sort o=
f
>>>> restriction on this could be useful. One approach could be to insist t=
hat the
>>>> data sender should ensure that the map being transmitted is for in-win=
dow data,
>>>> as per the receiver advertised window. A receiver should anyhow be wil=
ling to
>>>> store the maps for in-window data to deal with packet loss. For exampl=
e, when a
>>>> window of data segments (say 1 to 64) is transmitted, each carrying it=
s
>>>> corresponding map, and segment-1 is lost, the maps for the remaining 6=
3 need to
>>>> be stored till the lost segment is retransmitted. Of course, in this c=
ase the
>>>> maps will be stored at the receiver side along with their correspondin=
g data.
>>>> But the need to store multiple maps for in-window data would still be =
there.

>>>> The problem with the proposed change (restriction) is that a data send=
er may
>>>> find it difficult, in case a need arise to slightly delay the map deli=
very by
>>>> few segments, i.e., sending some data first without map, and then send=
 the
>>>> corresponding map in a later segment, as shown below:

>>>> subflow-1: segment-1 segment-3 segment-4 segment-7
>>>> bytes:1-100 bytes:201-300 bytes:301-400 bytes:601-700
>>>> no map map for 1-100 map for 201-400 map for 601-700

>>>> subflow-2: segment-2 segment-5 segment-6 segment-8
>>>> bytes: 101-200 bytes:401-500 bytes: 501-600 bytes:701-800
>>>> map for 101-200 map for 401-600 no map map for 701-800

>>>> In the above case, segment-1 goes without map and its map is included =
later in
>>>> segment-3, the next data segment in the same subflow. Further, in the =
above
>>>> scheduling pattern, the map in segment-3 cannot cover the data in segm=
ent-1 and
>>>> segment-3, as some data in between (segment-2) is transmitted through =
another
>>>> subflow. With the proposed change, the map in segment-3 will become in=
valid and
>>>> this will eventually break subflow-1, though this could be a corner ca=
se.

>>>> The question at this stage is why would segment-1 be transmitted witho=
ut its
>>>> map. In the case of bidirectional data transfer, there could be a need=
 to pack
>>>> both timestamp and SACK options in a data segment, i.e., piggybacking =
of SACK
>>>> with data. If we consider that timestamp takes 12 bytes and SACK, even=
 with
>>>> single block, takes another 10 bytes, the remaining 18 bytes option sp=
ace is
>>>> not adequate to carry data sequence signal with map, especially when D=
SN is 64
>>>> bit long. So the delivery of either of the two (SACK or map) would be =
delayed.

>>>> As far as I understand, RFC 2018 (TCP Selective Acknowledgement Option=
s) implies
>>>> that SACK should not be delayed. It states "If sent at all, SACK optio=
ns SHOULD
>>>> be included in all ACKs which do not ACK the highest sequence number i=
n the
>>>> data receiver's queue". It also says "If data receiver generates SACK =
options
>>>> under any circumstance, it SHOULD generate them under all permitted
>>>> circumstances". So, as part of meeting the RFC 2018 requirements, if t=
he
>>>> combination of SACK and timestamp is given preference over DSS, data s=
egments
>>>> could be transmitted without their map.

>>>> Another case of delaying map could arise if the data sender prefers to=
 send
>>>> ADD_ADDR option, instead of map, in a data segment. It is nice that AD=
D_ADDR
>>>> option can be delivered reliably in a pure ACK, but I think this is no=
t the
>>>> case with DSS at present.

>>>> If we adopt the proposed change, I think it might also be helpful to s=
pell out
>>>> how the receiver is supposed to behave, if it gets maps not meeting th=
e MUST
>>>> condition in the proposed change. For example termination of the subfl=
ow with
>>>> MP_TCPRST option (section 3.6 in RFC 6824-bis) with appropriate reason=
 code and
>>>> T flag value to intimate the data sender the cause for subflow termina=
tion.
>>>> With regards,

>>>> Anil

>>>> Please can members of the WG express whether they are happy with these=
 changes,
>>>> or concerned.

>>>> Best regards,
>>>> Alan

>>>> _______________________________________________
>>>> multipathtcp mailing list
>>>> [ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]
>>>> [ https://www.ietf.org/mailman/listinfo/multipathtcp |
>>>> https://www.ietf.org/mailman/listinfo/multipathtcp ]

>>>> _______________________________________________
>>>> multipathtcp mailing list
>>>> [ mailto:multipathtcp@ietf.org | multipathtcp@ietf.org ]
>>>> [ https://www.ietf.org/mailman/listinfo/multipathtcp |
>>>> https://www.ietf.org/mailman/listinfo/multipathtcp ]

=0A
--=_96570ff3-5078-4507-8307-761246f84160
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"font-family: arial, helvetica, sans-serif; font-s=
ize: style=3D" font-size:=3D"" 12pt;=3D"" color:=3D"" #000000"=3D""><div>Hi=
 Alan,</div><div><br data-mce-bogus=3D"1"></div><div>Thank you for your rep=
ly. I have two points to clarify. Please see them in line.</div><div><br></=
div><hr id=3D"zwchr" data-marker=3D"__DIVIDER__"><div data-marker=3D"__HEAD=
ERS__"><blockquote style=3D"border-left:2px solid #1010FF;margin-left:5px;p=
adding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decora=
tion:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: =
</b>"Alan Ford" &lt;alan.ford@gmail.com&gt;<br><b>To: </b>"V Anil Kumar" &l=
t;anil@csir4pi.in&gt;jk&nbsp;<br><b>Cc: </b>"Yoshifumi Nishida" &lt;nsd.iet=
f@gmail.com&gt;, "multipathtcp" &lt;multipathtcp@ietf.org&gt;<br><b>Sent: <=
/b>Thursday, February 6, 2020 2:49:29 AM<br><b>Subject: </b>Re: [multipatht=
cp] RFC6824bis edits based on implementation feedback<br></blockquote></div=
><div data-marker=3D"__QUOTED_TEXT__"><blockquote style=3D"border-left: 2px=
 solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weig=
ht: normal; font-style: normal; text-decoration: none; font-family: Helveti=
ca,Arial,sans-serif; font-size: 12pt;" data-mce-style=3D"border-left: 2px s=
olid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight=
: normal; font-style: normal; text-decoration: none; font-family: Helvetica=
,Arial,sans-serif; font-size: 12pt;">Hi Anil,<div><br class=3D""></div><div=
>This would not be forbidden if the mapping was carried on a pure ACK with =
no data.</div></blockquote><div>As far as I understand, delivery of DSM thr=
ough pure ACK is not in the scope of the current draft. If we intend to do =
this, we may need an approach similar to the one proposed for delivery of A=
DD_ADDR option in pure ACK with reliability feature. &nbsp;So, packing DSM =
on pure ACK does not seem to be an option at this stage.</div><blockquote s=
tyle=3D"border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px=
; color: #000; font-weight: normal; font-style: normal; text-decoration: no=
ne; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-sty=
le=3D"border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; =
color: #000; font-weight: normal; font-style: normal; text-decoration: none=
; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div><br class=
=3D""></div><div>I do see the point here: if a packet of 1000 bytes contain=
s 500 bytes of one mapping and 500 bytes of another mapping, then only one =
DSM would appear on one packet, leaving the mapping for the second 500 byte=
s to be carried somewhere else - the only option being a pure ACK. But this=
 kind of scenario would be extremely rare</div></blockquote><div>Yes, I do =
agree that the scenario you mentioned above would be extremely rare. In fac=
t, I wonder whether such a situation (i.e., need to cover the bytes in a si=
ngle packet with two different maps) would ever arise. Probably there might=
 be some corner cases, which I don't get it rightly now.&nbsp;</div><div><b=
r></div><div>More importantly, the scenario that Yoshi and me are referring=
 to is totally different: the one I had given as part of my comments in res=
ponse to the proposed change 2. In this scenario, which you could see in th=
e trailing mail, data segment-1 is transmitted without including its map, s=
omething which is permitted in the &nbsp;mptcp framework (6824 bis). I make=
 this inference from the below text in 6824 bis:</div><div><br data-mce-bog=
us=3D"1"></div><div> "...even if a mapping does not exist from the subflow =
space to the data- level space, the data SHOULD still be ACKed at the subfl=
ow (if it is in-window). This data cannot, however, be acknowledged at the =
data level (Section 3.3.2) because its data sequence numbers are unknown. I=
mplementations MAY hold onto such unmapped data for a short while in the ex=
pectation that a mapping will arrive shortly." </div><div><br data-mce-bogu=
s=3D"1"></div><div>One option the data sender has at this stage is to inclu=
de the map for data in segment-1, in segment-3 (please see the two-subflow =
example I gave in response to the change 2 you had proposed). But the propo=
sed change does not permit this. What would happen to &nbsp;subflow-1 in th=
is case ?</div><div><br data-mce-bogus=3D"1"></div><div>With regards,</div>=
<div><br data-mce-bogus=3D"1"></div><div>Anil &nbsp; &nbsp;</div><blockquot=
e style=3D"border-left: 2px solid #1010FF; margin-left: 5px; padding-left: =
5px; color: #000; font-weight: normal; font-style: normal; text-decoration:=
 none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-=
style=3D"border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5p=
x; color: #000; font-weight: normal; font-style: normal; text-decoration: n=
one; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div>and I =
would imagine any implementation would just split into two 500 byte segment=
s each with the PSH flag set. I don=E2=80=99t think we need to spell this o=
ut in the spec however.</div><div><br class=3D""></div><div>Regards,</div><=
div>Alan<br class=3D""><div><div><br class=3D""><blockquote class=3D""><div=
>On 5 Feb 2020, at 15:09, V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.i=
n" target=3D"_blank" rel=3D"nofollow noopener noreferrer" data-mce-href=3D"=
mailto:anil@csir4pi.in">anil@csir4pi.in</a>&gt; wrote:</div><div><div><div =
style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" data-mce-style=
=3D"font-family: 'arial' , 'helvetica' , sans-serif;"><div><div style=3D"fo=
nt-family: 'arial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-fami=
ly: 'arial' , 'helvetica' , sans-serif;"><div><div style=3D"font-family: 'a=
rial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-family: 'arial' ,=
 'helvetica' , sans-serif;"><div><div style=3D"font-family: 'arial' , 'helv=
etica' , sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' =
, sans-serif;"><div>Hi Yoshi,</div><br class=3D""><div>Please see in line.<=
/div><br class=3D""><hr id=3D"zwchr" class=3D""><div><b class=3D"">From: </=
b>"Yoshifumi Nishida" &lt;<a href=3D"mailto:nsd.ietf@gmail.com" target=3D"_=
blank" rel=3D"nofollow noopener noreferrer" data-mce-href=3D"mailto:nsd.iet=
f@gmail.com">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: </b=
>"V Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" target=3D"_blank" re=
l=3D"nofollow noopener noreferrer" data-mce-href=3D"mailto:anil@csir4pi.in"=
>anil@csir4pi.in</a>&gt;<br class=3D""><b class=3D"">Cc: </b>"alan ford" &l=
t;<a href=3D"mailto:alan.ford@gmail.com" target=3D"_blank" rel=3D"nofollow =
noopener noreferrer" data-mce-href=3D"mailto:alan.ford@gmail.com">alan.ford=
@gmail.com</a>&gt;, "multipathtcp" &lt;<a href=3D"mailto:multipathtcp@ietf.=
org" target=3D"_blank" rel=3D"nofollow noopener noreferrer" data-mce-href=
=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a>&gt;<br class=3D=
""><b class=3D"">Sent: </b>Tuesday, February 4, 2020 1:08:45 PM<br class=3D=
""><b class=3D"">Subject: </b>Re: [multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></div><br class=3D""><div><div dir=3D=
"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><br class=3D""><=
div>Thanks for pointing it out. I overlooked this one.</div><div>This looks=
 an interesting point.<br class=3D""></div><br class=3D""><div>It seems to =
me that whether RST is happen or not depends on the size of receive window =
according to the text.<br class=3D""></div><div>If the receive window size =
is big enough to accommodate&nbsp;segment 1 and segment 3, the text "<span =
style=3D"font-size: 13.3333px;" class=3D"" data-mce-style=3D"font-size: 13.=
3333px;">Implementations MAY hold onto such unmapped data for a short while=
 in&nbsp;</span><span style=3D"font-size: 13.3333px;" class=3D"" data-mce-s=
tyle=3D"font-size: 13.3333px;">the expectation that a mapping will arrive s=
hortly. "&nbsp;</span>can be applied to the segment 1. As a result, the seg=
ment 1 won't be discarded.&nbsp;</div><br class=3D""><div><em class=3D"">Ye=
s. &nbsp;So, segment 1 may be kept in the data receiver's buffer in expecta=
tion that its mapping will arrive shortly. And in the example that we are r=
eferring to, the data sender will not be able to include the map for the da=
ta in segment 1 in segment 3 or any higher segment.</em></div><br class=3D"=
"><div><em class=3D"">Regards,</em></div><br class=3D""><div><em class=3D""=
>Anil</em></div><br class=3D""><div>However, this might be contradict with =
the new texts Alan proposed? Or, am I missing something?</div><br class=3D"=
"><div>Thanks,</div><div>--</div><div>Yoshi</div><br class=3D""><br class=
=3D""><br class=3D""><div><div dir=3D"ltr">On Sun, Feb 2, 2020 at 8:42 AM V=
 Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow%20noopen=
er%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20=
noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer"=
 target=3D"_blank" data-mce-href=3D"mailto:anil@csir4pi.in">anil@csir4pi.in=
</a>&gt; wrote:<br class=3D""></div><blockquote class=3D"gmail_quote" style=
=3D"margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left=
: 1ex;" data-mce-style=3D"margin: 0px 0px 0px 0.8ex; border-left: 1px solid=
 #cccccc; padding-left: 1ex;"><div><div><div><div style=3D"font-family: 'ar=
ial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-family: 'arial' , =
'helvetica' , sans-serif;"><div>Hi Yoshi,</div><br class=3D""><div>Thanks f=
or this point. In fact, I had initially not thought of a scenario, where th=
e map is being delivered through a retransmitted data packet while its firs=
t transmission did not include the map. Now I am just seeing the document (=
RFC 6824-bis) in this context.</div><br class=3D""><div>My understanding is=
 that in scenarios like what I described in my previous mail, RST is likely=
 to happen whether we explicitly state so or not. Please see the paragraph =
containing the below text in RFC 6824-bis. &nbsp;</div><br class=3D""><div>=
"If a mapping for that subflow-level sequence space does not arrive within =
a receive window of data, that subflow SHOULD be treated as broken, closed =
with a RST, and any unmapped data silently discarded."</div><br class=3D"">=
<div>if we assume that the map is included while retransmitting the data (e=
ven though the first transmission did not contain the map for some reasons)=
, &nbsp;we could argue that RST could be avoided provided that the retransm=
ission is triggered within a receive window of data. But the question here =
would be how and when will the retransmission take place. In this case, the=
 subflow may not initiate the retransmission of data by its own (i.e., no r=
etransmission due to three duplicate ACKs or RTO expiry at subflow level) a=
s there is no segment loss at subflow level sequence space. So there could =
be a high possibility of RST happening even before the map delivery through=
 retransmission.&nbsp;</div><br class=3D""><div>With regards,&nbsp;</div><b=
r class=3D""><div>Anil</div><div>&nbsp;</div><hr id=3D"gmail-m_218086596951=
724501gmail-m_2982267033577902985zwchr" class=3D""><div><b class=3D"">From:=
 </b>"Yoshifumi Nishida" &lt;<a href=3D"mailto:nsd.ietf@gmail.com" rel=3D"n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofoll=
ow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noop=
ener noreferrer" target=3D"_blank" data-mce-href=3D"mailto:nsd.ietf@gmail.c=
om">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: </b>"V Anil =
Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow%20noopener%20=
noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noref=
errer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" targ=
et=3D"_blank" data-mce-href=3D"mailto:anil@csir4pi.in">anil@csir4pi.in</a>&=
gt;<br class=3D""><b class=3D"">Cc: </b>"alan ford" &lt;<a href=3D"mailto:a=
lan.ford@gmail.com" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20no=
opener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopene=
r%20noreferrer nofollow noopener noreferrer" target=3D"_blank" data-mce-hre=
f=3D"mailto:alan.ford@gmail.com">alan.ford@gmail.com</a>&gt;, "multipathtcp=
" &lt;<a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noopener%2=
0noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20nore=
ferrer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" tar=
get=3D"_blank" data-mce-href=3D"mailto:multipathtcp@ietf.org">multipathtcp@=
ietf.org</a>&gt;<br class=3D""><b class=3D"">Sent: </b>Saturday, February 1=
, 2020 3:39:51 AM<br class=3D""><b class=3D"">Subject: </b>Re: [multipathtc=
p] RFC6824bis edits based on implementation feedback<br class=3D""></div><b=
r class=3D""><div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>H=
i Anil,</div><br class=3D""><div>I have a question about your proposed text=
.</div><div><div>I am actually wondering if we really want to terminate con=
nection here.&nbsp;</div></div><br class=3D""><div>The packets without prop=
er mappings will be treated as invalid and will be discarded.&nbsp;</div><d=
iv>If an implementation failed to attach proper mapping for some reasons (e=
.g. option space), it might be able to attach the proper one when it retran=
smits the packets. This also looks ok to me.</div><br class=3D""><div>I don=
't have strong preference for this. But, do we have a reason to terminate c=
onnection?</div><br class=3D""><div>Thanks,</div><div>--<br class=3D""></di=
v><div>Yoshi</div><br class=3D""><div><div dir=3D"ltr">On Mon, Jan 13, 2020=
 at 10:28 AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"nof=
ollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow=
%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20no=
opener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener no=
referrer" target=3D"_blank" data-mce-href=3D"mailto:anil@csir4pi.in">anil@c=
sir4pi.in</a>&gt; wrote:<br class=3D""></div><blockquote class=3D"gmail_quo=
te" style=3D"margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; pad=
ding-left: 1ex;" data-mce-style=3D"margin: 0px 0px 0px 0.8ex; border-left: =
1px solid #cccccc; padding-left: 1ex;"><div><div><div><div style=3D"font-fa=
mily: 'arial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-family: '=
arial' , 'helvetica' , sans-serif;"><div><span style=3D"font-size: 12pt; li=
ne-height: 1.3;" class=3D"" data-mce-style=3D"font-size: 12pt; line-height:=
 1.3;">Hi,</span><br class=3D""></div><div><div style=3D"font-family: 'aria=
l' , 'helvetica' , sans-serif;" data-mce-style=3D"font-family: 'arial' , 'h=
elvetica' , sans-serif;"><div style=3D"font-family: 'arial' , 'helvetica' ,=
 sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , sans-s=
erif;"><div style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" data=
-mce-style=3D"font-family: 'arial' , 'helvetica' , sans-serif;"><div style=
=3D"font-family: 'arial' , 'helvetica' , sans-serif;" data-mce-style=3D"fon=
t-family: 'arial' , 'helvetica' , sans-serif;"><div style=3D"font-family: '=
arial' , 'helvetica' , sans-serif;" data-mce-style=3D"font-family: 'arial' =
, 'helvetica' , sans-serif;"><div style=3D"font-family: 'arial' , 'helvetic=
a' , sans-serif;" data-mce-style=3D"font-family: 'arial' , 'helvetica' , sa=
ns-serif;"><div style=3D"font-family: 'arial' , 'helvetica' , sans-serif;" =
data-mce-style=3D"font-family: 'arial' , 'helvetica' , sans-serif;"><br cla=
ss=3D""><div>I have some points related to the &nbsp;modifications (Change =
2) being proposed on data sequence map. Please see them inline.&nbsp;<span =
style=3D"font-family: 'arial' , 'helvetica' , sans-serif; font-size: 16px; =
font-style: normal; font-weight: 400; letter-spacing: normal; text-indent: =
0px; text-transform: none; white-space: normal; word-spacing: 0px; backgrou=
nd-color: #ffffff; float: none; display: inline;" class=3D"" data-mce-style=
=3D"font-family: 'arial' , 'helvetica' , sans-serif; font-size: 16px; font-=
style: normal; font-weight: 400; letter-spacing: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; background-co=
lor: #ffffff; float: none; display: inline;">Though I am putting forward th=
e below points, if the consensus is in favour of the proposed change for re=
ducing implementation complexity, I am also OK with that as well.&nbsp;</sp=
an><br class=3D""></div><br class=3D""><hr id=3D"gmail-m_218086596951724501=
gmail-m_2982267033577902985gmail-m_7687184382299596774zwchr" class=3D""><di=
v><b class=3D"">From: </b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail=
.com" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noref=
errer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofo=
llow noopener noreferrer" target=3D"_blank" data-mce-href=3D"mailto:alan.fo=
rd@gmail.com">alan.ford@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: <=
/b><a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noopener%20no=
referrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20norefer=
rer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%2=
0nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"_=
blank" data-mce-href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org=
</a><br class=3D""><b class=3D"">Sent: </b>Thursday, January 2, 2020 4:21:3=
2 AM<br class=3D""><b class=3D"">Subject: </b>[multipathtcp] RFC6824bis edi=
ts based on implementation feedback<br class=3D""></div><br class=3D""><div=
>Hi all,<br class=3D""><div>We=E2=80=99d love to get this to a state of com=
pletion as soon as possible, and to this end I am starting a new thread on =
this topic. In discussion with the chairs, it <i class=3D"">is </i>possible=
 to make the desired changes in AUTH48 as long as there is WG consensus. Th=
e discussion so far has been fairly limited in terms of participation.</div=
><br class=3D""><div>I would ask the chairs please if it was possible to sp=
ecify a time bound for this discussion and a default conclusion.</div><br c=
lass=3D""><div>Regarding the changes, in summary, there are two areas where=
 changes have been requested by the implementation community. As we are the=
 IETF we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and =
so ease of implementing standards-compliant code is strongly desirable. How=
ever, we do not wish to reduce functionality agreed by the IETF community i=
f it is considered a required feature by the community.</div><br class=3D""=
><br class=3D""><div><b class=3D"">Change 1</b></div><div><b class=3D""><br=
 class=3D""></b></div><div>Change the sentence reading:<br class=3D""><br c=
lass=3D""><i class=3D"">&nbsp; &nbsp;If B has data to send first, then the =
reliable delivery of the ACK + MP_CAPABLE can be inferred by the receipt of=
 this data with an MPTCP Data Sequence Signal (DSS) option (Section 3.3).&n=
bsp;<br class=3D""></i><br class=3D"">To:<br class=3D""><br class=3D""><i c=
lass=3D"">&nbsp; &nbsp;If B has data to send first, then the reliable deliv=
ery of the ACK + MP_CAPABLE is ensured by the receipt of this data with an =
MPTCP Data Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK=
 for the MP_CAPABLE (which is the first octet of the data sequence&nbsp;spa=
ce).<br class=3D""></i><br class=3D""></div><div>What this means:</div><br =
class=3D""><div>The current text is concerned only with ensuring a path is =
MPTCP capable, and so only cares that DSS option occurs on a data packet. H=
owever, the MP_CAPABLE option is defined to occupy the first octet of data =
sequence space and thus, if analogous to TCP, must be acknowledged. &gt;Fro=
m an implementation point of view it would make sense not to have this hang=
ing around forever and instead define it is acknowledged at the connection =
level as soon as received. This change ensures the first data packet also D=
ATA_ACKs this MP_CAPABLE octet.</div><br class=3D""><br class=3D""><div><b =
class=3D"">Change 2</b></div><div><b class=3D""><br class=3D""></b></div><d=
iv>Change the sentence reading:<br class=3D""><br class=3D""><i class=3D"">=
&nbsp; &nbsp;A Data Sequence Mapping does not need to be included in every =
MPTCP packet, as long as the subflow sequence space in that packet is cover=
ed by a mapping known at the receiver.</i><br class=3D""><br class=3D"">To:=
<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;The mapping provid=
ed by a Data Sequence Mapping MUST apply to some or all of the subflow sequ=
ence space in the TCP segment which carries the option. It does not need to=
 be included in every MPTCP packet, as long as the subflow sequence space i=
n that packet is covered by a mapping known at the receiver.<br class=3D"">=
</i><br class=3D"">What this means:</div><br class=3D""><div>The current te=
xt does not place any restrictions on where a mapping could appear. In theo=
ry a sender could define a thousand different mappings up front, send them =
all, and expect a receiver to store this and reassemble data according to t=
hese mappings as it arrives. Indeed, this was never explicitly disallowed s=
ince it =E2=80=9Cmight have been useful=E2=80=9D. The implementation commun=
ity, however, has expressed concerns over the difficulty of implementing th=
is open-endedly. How many mappings is it reasonable to store? Is there a Do=
S risk here? Instead, it has been requested that thee specification restric=
ts the placement of the DSS option to being within the subflow sequence spa=
ce to which it applies.</div><br class=3D""><div>Below are my comments on t=
his. I had shared some of these points in a previous thread that you had in=
itiated in the same context.&nbsp;</div><br class=3D""><div>Transmitting la=
rge number of non-contiguous data sequence maps could be a misbehaviour (ma=
p-flooding), though it is not clear whether this can go to the extent of ca=
using a potential DoS to the data receiver. So some sort of restriction on =
this could be useful.&nbsp; One approach could be to insist that the data s=
ender should ensure that the map being transmitted is for in-window data, a=
s per the receiver advertised window. A receiver should anyhow be willing t=
o store the maps for in-window data to deal with packet loss. For example, =
when a window of data segments (say 1 to 64) is transmitted, each carrying =
its corresponding map, and segment-1 is lost, the maps for the remaining 63=
 need to be stored till the lost segment is retransmitted. Of course, in th=
is case the maps will be stored at the receiver side along with their corre=
sponding data. But the need to store multiple maps for in-window data would=
 still be there.</div><br class=3D""><div><span style=3D"font-family: 'aria=
l' , 'helvetica' , sans-serif; font-size: 16px; font-style: normal; font-we=
ight: normal; letter-spacing: normal; line-height: 20.8px; text-indent: 0px=
; text-transform: none; white-space: normal; word-spacing: 0px; float: none=
; background-color: #ffffff; display: inline;" class=3D"" data-mce-style=3D=
"font-family: 'arial' , 'helvetica' , sans-serif; font-size: 16px; font-sty=
le: normal; font-weight: normal; letter-spacing: normal; line-height: 20.8p=
x; text-indent: 0px; text-transform: none; white-space: normal; word-spacin=
g: 0px; float: none; background-color: #ffffff; display: inline;">The probl=
em with the proposed change (restriction) is that a data sender may find it=
 difficult, in case a need arise to slightly delay the map delivery by few =
segments, i.e., sending some data first without map, and then send the corr=
esponding map in a later segment, as shown below:</span><br class=3D""></di=
v><br class=3D""><div><div style=3D"font-family: 'segoe ui' , 'lucida sans'=
 , sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal;=
 letter-spacing: normal; line-height: normal; text-indent: 0px; text-transf=
orm: none; white-space: normal; word-spacing: 0px; margin: 0px; background-=
color: #ffffff;" data-mce-style=3D"font-family: 'segoe ui' , 'lucida sans' =
, sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-indent: 0px; text-transfo=
rm: none; white-space: normal; word-spacing: 0px; margin: 0px; background-c=
olor: #ffffff;"><span lang=3D"EN-US" style=3D"font-size: 10pt;" class=3D"" =
data-mce-style=3D"font-size: 10pt;">subflow-1:&nbsp; &nbsp; &nbsp; segment-=
1&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; segment-3&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-4 &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-7</span></div><div st=
yle=3D"font-family: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.=
16px; font-style: normal; font-weight: normal; letter-spacing: normal; line=
-height: normal; text-indent: 0px; text-transform: none; white-space: norma=
l; word-spacing: 0px; margin: 0px; background-color: #ffffff;" data-mce-sty=
le=3D"font-family: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.1=
6px; font-style: normal; font-weight: normal; letter-spacing: normal; line-=
height: normal; text-indent: 0px; text-transform: none; white-space: normal=
; word-spacing: 0px; margin: 0px; background-color: #ffffff;"><span lang=3D=
"EN-US" style=3D"font-size: 10pt;" class=3D"" data-mce-style=3D"font-size: =
10pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;bytes:1-100 &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; bytes:201-300 &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;bytes:301-400 &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; bytes:601-700</span></div><div style=3D"f=
ont-family: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; fo=
nt-style: normal; font-weight: normal; letter-spacing: normal; line-height:=
 normal; text-indent: 0px; text-transform: none; white-space: normal; word-=
spacing: 0px; margin: 0px; background-color: #ffffff;" data-mce-style=3D"fo=
nt-family: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; fon=
t-style: normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; text-indent: 0px; text-transform: none; white-space: normal; word-s=
pacing: 0px; margin: 0px; background-color: #ffffff;"><span lang=3D"EN-US" =
style=3D"font-size: 10pt;" class=3D"" data-mce-style=3D"font-size: 10pt;">&=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
&nbsp;no map &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp;map for 1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp;map for 201-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; map for 6=
01-700</span></div><div style=3D"font-family: 'segoe ui' , 'lucida sans' , =
sans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; le=
tter-spacing: normal; line-height: normal; text-indent: 0px; text-transform=
: none; white-space: normal; word-spacing: 0px; margin: 0px; background-col=
or: #ffffff;" data-mce-style=3D"font-family: 'segoe ui' , 'lucida sans' , s=
ans-serif; font-size: 14.16px; font-style: normal; font-weight: normal; let=
ter-spacing: normal; line-height: normal; text-indent: 0px; text-transform:=
 none; white-space: normal; word-spacing: 0px; margin: 0px; background-colo=
r: #ffffff;"><span lang=3D"EN-US" style=3D"font-size: 10pt;" class=3D"" dat=
a-mce-style=3D"font-size: 10pt;"><br class=3D""></span></div><div style=3D"=
font-family: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; f=
ont-style: normal; font-weight: normal; letter-spacing: normal; line-height=
: normal; text-indent: 0px; text-transform: none; white-space: normal; word=
-spacing: 0px; margin: 0px; background-color: #ffffff;" data-mce-style=3D"f=
ont-family: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; fo=
nt-style: normal; font-weight: normal; letter-spacing: normal; line-height:=
 normal; text-indent: 0px; text-transform: none; white-space: normal; word-=
spacing: 0px; margin: 0px; background-color: #ffffff;"><span lang=3D"EN-US"=
 style=3D"font-size: 10pt;" class=3D"" data-mce-style=3D"font-size: 10pt;">=
<br class=3D""></span></div><div style=3D"font-family: 'segoe ui' , 'lucida=
 sans' , sans-serif; font-size: 14.16px; font-style: normal; font-weight: n=
ormal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-=
transform: none; white-space: normal; word-spacing: 0px; margin: 0px; backg=
round-color: #ffffff;" data-mce-style=3D"font-family: 'segoe ui' , 'lucida =
sans' , sans-serif; font-size: 14.16px; font-style: normal; font-weight: no=
rmal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-t=
ransform: none; white-space: normal; word-spacing: 0px; margin: 0px; backgr=
ound-color: #ffffff;"><br class=3D""></div><div style=3D"font-family: 'sego=
e ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-style: normal;=
 font-weight: normal; letter-spacing: normal; line-height: normal; text-ind=
ent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; mar=
gin: 0px; background-color: #ffffff;" data-mce-style=3D"font-family: 'segoe=
 ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-style: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; text-inde=
nt: 0px; text-transform: none; white-space: normal; word-spacing: 0px; marg=
in: 0px; background-color: #ffffff;"><span lang=3D"EN-US" style=3D"font-siz=
e: 10pt;" class=3D"" data-mce-style=3D"font-size: 10pt;">subflow-2:&nbsp; &=
nbsp; &nbsp; &nbsp;segment-2&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; segment-5 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; segment-6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-8</span></div><div style=3D"font-f=
amily: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-st=
yle: normal; font-weight: normal; letter-spacing: normal; line-height: norm=
al; text-indent: 0px; text-transform: none; white-space: normal; word-spaci=
ng: 0px; margin: 0px; background-color: #ffffff;" data-mce-style=3D"font-fa=
mily: 'segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-sty=
le: normal; font-weight: normal; letter-spacing: normal; line-height: norma=
l; text-indent: 0px; text-transform: none; white-space: normal; word-spacin=
g: 0px; margin: 0px; background-color: #ffffff;"><span lang=3D"EN-US" style=
=3D"font-size: 10pt;" class=3D"" data-mce-style=3D"font-size: 10pt;">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bytes: 101-200 &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; bytes:401-500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bytes: 501-600 &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;bytes:701-800&nbsp;&nbsp;&nbsp;</sp=
an></div><div style=3D"font-family: 'segoe ui' , 'lucida sans' , sans-serif=
; font-size: 14.16px; font-style: normal; font-weight: normal; letter-spaci=
ng: normal; line-height: normal; text-indent: 0px; text-transform: none; wh=
ite-space: normal; word-spacing: 0px; margin: 0px; background-color: #fffff=
f;" data-mce-style=3D"font-family: 'segoe ui' , 'lucida sans' , sans-serif;=
 font-size: 14.16px; font-style: normal; font-weight: normal; letter-spacin=
g: normal; line-height: normal; text-indent: 0px; text-transform: none; whi=
te-space: normal; word-spacing: 0px; margin: 0px; background-color: #ffffff=
;"><span lang=3D"EN-US" style=3D"font-size: 10pt;" class=3D"" data-mce-styl=
e=3D"font-size: 10pt;">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp;map for 101-200 &nbsp; &nbsp; &nbsp; map for=
 401-600 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;no map &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;map for 701-800</span></div><div style=3D"font-family: 'segoe ui' , 'lu=
cida sans' , sans-serif; font-size: 14.16px; font-style: normal; font-weigh=
t: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; t=
ext-transform: none; white-space: normal; word-spacing: 0px; margin: 0px; b=
ackground-color: #ffffff;" data-mce-style=3D"font-family: 'segoe ui' , 'luc=
ida sans' , sans-serif; font-size: 14.16px; font-style: normal; font-weight=
: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; te=
xt-transform: none; white-space: normal; word-spacing: 0px; margin: 0px; ba=
ckground-color: #ffffff;"><br class=3D""></div><div style=3D"font-family: '=
segoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-style: nor=
mal; font-weight: normal; letter-spacing: normal; line-height: normal; text=
-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;=
 margin: 0px; background-color: #ffffff;" data-mce-style=3D"font-family: 's=
egoe ui' , 'lucida sans' , sans-serif; font-size: 14.16px; font-style: norm=
al; font-weight: normal; letter-spacing: normal; line-height: normal; text-=
indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; =
margin: 0px; background-color: #ffffff;"><br class=3D""></div>In the above =
case, segment-1 goes without map and its map is included later in segment-3=
, the next data segment in the same subflow. Further, &nbsp;in the above sc=
heduling pattern, the map in segment-3 cannot cover the &nbsp;data in segme=
nt-1 and segment-3, as some &nbsp;data in between (segment-2) is transmitte=
d through another subflow.&nbsp; With the proposed change, the map in segme=
nt-3 will become invalid and this will eventually break subflow-1, though t=
his could be a corner case.</div><br class=3D""><div>The question at this s=
tage is why would segment-1 be transmitted without its map. In the case of =
bidirectional data transfer, there could be a need to pack both timestamp a=
nd SACK &nbsp;options in a data segment, i.e., piggybacking of &nbsp;SACK w=
ith data. If we consider that timestamp takes 12 bytes and SACK, even with =
single block, &nbsp;takes another 10 bytes, the remaining 18 bytes option s=
pace is not adequate to carry data sequence signal with map, especially whe=
n DSN is 64 bit long. So the delivery of either of the two (SACK or map) wo=
uld be delayed.</div><br class=3D""><div>As far as I understand, RFC 2018 (=
TCP Selective Acknowledgement Options) implies that SACK should not be dela=
yed. It states "If sent at all, SACK options SHOULD be included in all ACKs=
 which do not ACK the highest sequence number in the data receiver's queue"=
. It also says "If data receiver generates SACK options under any circumsta=
nce, it SHOULD generate them under all permitted circumstances". &nbsp; So,=
 as part of meeting the RFC 2018 requirements, if the combination of SACK a=
nd timestamp is given preference over DSS, data segments could be transmitt=
ed without their map.&nbsp;</div><br class=3D""><div>Another case of delayi=
ng map could arise if the data sender prefers to send ADD_ADDR option, inst=
ead of map, in a data segment. It is nice that ADD_ADDR option can be deliv=
ered reliably in a pure ACK, but I think this is not the case with DSS at p=
resent.</div><br class=3D""><div>If we adopt the proposed change, I think i=
t might also be helpful to spell out how the receiver is supposed to behave=
, if it gets maps not meeting the MUST condition in the proposed change.&nb=
sp; For example termination of the subflow with MP_TCPRST option (section 3=
.6 in RFC 6824-bis) with appropriate reason code and T flag value to intima=
te the data sender the cause for subflow termination.&nbsp;&nbsp;</div><div=
>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</div></div><div>With regards,</div><br =
class=3D""><div>Anil<br class=3D""><br class=3D""><div>Please can members o=
f the WG express whether they are happy with these changes, or concerned.</=
div><br class=3D""><div>Best regards,</div><div>Alan</div><br class=3D""><b=
r class=3D"">_______________________________________________<br class=3D"">=
multipathtcp mailing list<br class=3D""><a href=3D"mailto:multipathtcp@ietf=
.org" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noref=
errer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofo=
llow noopener noreferrer" target=3D"_blank" data-mce-href=3D"mailto:multipa=
thtcp@ietf.org">multipathtcp@ietf.org</a><br class=3D""><a href=3D"https://=
www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"nofollow%20noopener%20no=
referrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20norefer=
rer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%2=
0nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"_=
blank" data-mce-href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp"=
>https://www.ietf.org/mailman/listinfo/multipathtcp</a></div></div></div></=
div></div></div></div></div></div></div><br class=3D""></div></div></div><b=
r class=3D""><br class=3D"">_______________________________________________=
<br class=3D"">multipathtcp mailing list<br class=3D""><a href=3D"mailto:mu=
ltipathtcp@ietf.org" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20n=
oopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopen=
er%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20=
noreferrer nofollow noopener noreferrer" target=3D"_blank" data-mce-href=3D=
"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br class=3D""><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"noreferre=
r%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofoll=
ow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noop=
ener noreferrer" target=3D"_blank" data-mce-href=3D"https://www.ietf.org/ma=
ilman/listinfo/multipathtcp">https://www.ietf.org/mailman/listinfo/multipat=
htcp</a><br class=3D""></blockquote></div></div></div></div></div></div><br=
 class=3D""></div></div><br class=3D""></div></blockquote></div></div></div=
></div></div></div></div></div></div></div><br class=3D""></div></div><br c=
lass=3D""><br class=3D""></div></div></blockquote></div><br class=3D""></di=
v></div><br></blockquote></div></div>
<br>=
=0A<br>=
</body></html>
--=_96570ff3-5078-4507-8307-761246f84160--


From nobody Tue Feb 11 01:05:57 2020
Return-Path: <nsd.ietf@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC561201DE for <multipathtcp@ietfa.amsl.com>; Tue, 11 Feb 2020 01:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 z4o7xGsEM-oH for <multipathtcp@ietfa.amsl.com>; Tue, 11 Feb 2020 01:05:50 -0800 (PST)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (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 2489312008D for <multipathtcp@ietf.org>; Tue, 11 Feb 2020 01:05:50 -0800 (PST)
Received: by mail-vs1-xe2a.google.com with SMTP id x123so5821718vsc.2 for <multipathtcp@ietf.org>; Tue, 11 Feb 2020 01:05:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bYwneWG/fR5f29mqIbMLKNai/vR809smK8H1US2l9dw=; b=Bz7ntItTS9iyMdGrim6QnBZt4GRu5v22xSkWPV4vxk8zRSGb1n07SI4RH+49lmfZil pmuSy09icyzleheMRN6IQ2HNf48fHYef5r5n0LcZZ2Tu2fEqtDMArFYX0rTnPOWd6+rP JVhq8P3OELGy8abKfDGAhdGKMqLC1f7SZvMwpfGjz/y0aHFmfsio4zMgdW6v3O6sIl7o wk1m+b+aJZh+Y64/wr0Pr7mt3MYRc3/U7m7t+JzV/PR1219gPqhxD5Ro6ZjLTyT5yaXO 0x7koTbwVWc3fbtdx5j/YNEfWQ/C3gnt9UMr47p1JMikqItj94a+oi/NrN68m+pMDO39 zXuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bYwneWG/fR5f29mqIbMLKNai/vR809smK8H1US2l9dw=; b=gffAMJLgPp/RM+8ldk7uKsmMnOs3h8kJtduaZyWESdPblzWCHooWuxCWFwJpgJiJe/ lzzBQNOuVa2ecmw2V+k5Hx4WsiQ9os0WBe9syACxcv10GRFHUl6bjysYy1M+3kcmGxgn 9iSLVesXhwP/HOvlaJTpAQlLEv3x1q27iDn9A2tUoBFXRehO31KXxhBTUHj+jZzo7rPJ gXk3QZRCPf4gLtlXWb+qu4kKME6/qxp9wOInCdtfLAxPt2KV8Bs3EWq2EjXSGsNjtXsF /WpCQUcvTq53gHj8TkEtNmEHZGUaqv7H0nvvs1Fx9QT2bFz/aePwaaFTsy7olrNpAsk7 jjXw==
X-Gm-Message-State: APjAAAWsQ+xf87+JM8ifROM/II+jQzx2ClzrmpgVatJalWpKc9DabSF8 LvigKdB6v1irD8RaIof0hK7hFEDkhYuaq8aCtNg=
X-Google-Smtp-Source: APXvYqw5lXhgTqIr20v7hiI23Rg1S1fEoGgdbsZ/xcSNypcDAomKKQ6zd/++5D3hvxeS1/ZJEdUrJLd3UrmNhUhLBSY=
X-Received: by 2002:a67:f641:: with SMTP id u1mr8651429vso.86.1581411949037; Tue, 11 Feb 2020 01:05:49 -0800 (PST)
MIME-Version: 1.0
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com> <1411057985.31281938.1581012439446@csir4pi.in>
In-Reply-To: <1411057985.31281938.1581012439446@csir4pi.in>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Tue, 11 Feb 2020 01:05:37 -0800
Message-ID: <CAAK044QoFh_eXE+MwggOn5X0uUs3xuzTcw2kdJaKuUnEP745dA@mail.gmail.com>
To: V Anil Kumar <anil@csir4pi.in>
Cc: Alan Ford <alan.ford@gmail.com>, multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000774b0b059e49290e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/2izeDR7Dwwi9HI-UigRek0uLJJ0>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2020 09:05:55 -0000

--000000000000774b0b059e49290e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi folks,
I guess we might want to know the behavior of existing implementations such
as linux.
When an mptcp stack tries to send a data packet and find that there's no
enough option space for data mapping, what it will do?
Split the packet to create more option space?
--
Yoshi

On Thu, Feb 6, 2020 at 10:10 AM V Anil Kumar <anil@csir4pi.in> wrote:

> Hi Alan,
>
> Thank you for your reply. I have two points to clarify. Please see them i=
n
> line.
>
> ------------------------------
>
> *From: *"Alan Ford" <alan.ford@gmail.com>
> *To: *"V Anil Kumar" <anil@csir4pi.in>jk
> *Cc: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>, "multipathtcp" <
> multipathtcp@ietf.org>
> *Sent: *Thursday, February 6, 2020 2:49:29 AM
> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation
> feedback
>
> Hi Anil,
>
> This would not be forbidden if the mapping was carried on a pure ACK with
> no data.
>
> As far as I understand, delivery of DSM through pure ACK is not in the
> scope of the current draft. If we intend to do this, we may need an
> approach similar to the one proposed for delivery of ADD_ADDR option in
> pure ACK with reliability feature.  So, packing DSM on pure ACK does not
> seem to be an option at this stage.
>
>
> I do see the point here: if a packet of 1000 bytes contains 500 bytes of
> one mapping and 500 bytes of another mapping, then only one DSM would
> appear on one packet, leaving the mapping for the second 500 bytes to be
> carried somewhere else - the only option being a pure ACK. But this kind =
of
> scenario would be extremely rare
>
> Yes, I do agree that the scenario you mentioned above would be extremely
> rare. In fact, I wonder whether such a situation (i.e., need to cover the
> bytes in a single packet with two different maps) would ever arise.
> Probably there might be some corner cases, which I don't get it rightly
> now.
>
> More importantly, the scenario that Yoshi and me are referring to is
> totally different: the one I had given as part of my comments in response
> to the proposed change 2. In this scenario, which you could see in the
> trailing mail, data segment-1 is transmitted without including its map,
> something which is permitted in the  mptcp framework (6824 bis). I make
> this inference from the below text in 6824 bis:
>
> "...even if a mapping does not exist from the subflow space to the data-
> level space, the data SHOULD still be ACKed at the subflow (if it is
> in-window). This data cannot, however, be acknowledged at the data level
> (Section 3.3.2) because its data sequence numbers are unknown.
> Implementations MAY hold onto such unmapped data for a short while in the
> expectation that a mapping will arrive shortly."
>
> One option the data sender has at this stage is to include the map for
> data in segment-1, in segment-3 (please see the two-subflow example I gav=
e
> in response to the change 2 you had proposed). But the proposed change do=
es
> not permit this. What would happen to  subflow-1 in this case ?
>
> With regards,
>
> Anil
>
> and I would imagine any implementation would just split into two 500 byte
> segments each with the PSH flag set. I don=E2=80=99t think we need to spe=
ll this
> out in the spec however.
>
> Regards,
> Alan
>
> On 5 Feb 2020, at 15:09, V Anil Kumar <anil@csir4pi.in> wrote:
> Hi Yoshi,
>
> Please see in line.
>
> ------------------------------
> *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>
> *To: *"V Anil Kumar" <anil@csir4pi.in>
> *Cc: *"alan ford" <alan.ford@gmail.com>, "multipathtcp" <
> multipathtcp@ietf.org>
> *Sent: *Tuesday, February 4, 2020 1:08:45 PM
> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation
> feedback
>
> Hi Anil,
>
> Thanks for pointing it out. I overlooked this one.
> This looks an interesting point.
>
> It seems to me that whether RST is happen or not depends on the size of
> receive window according to the text.
> If the receive window size is big enough to accommodate segment 1 and
> segment 3, the text "Implementations MAY hold onto such unmapped data for
> a short while in the expectation that a mapping will arrive shortly. " ca=
n
> be applied to the segment 1. As a result, the segment 1 won't be discarde=
d.
>
> *Yes.  So, segment 1 may be kept in the data receiver's buffer in
> expectation that its mapping will arrive shortly. And in the example that
> we are referring to, the data sender will not be able to include the map
> for the data in segment 1 in segment 3 or any higher segment.*
>
> *Regards,*
>
> *Anil*
>
> However, this might be contradict with the new texts Alan proposed? Or, a=
m
> I missing something?
>
> Thanks,
> --
> Yoshi
>
>
>
> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in> wrote:
>
>> Hi Yoshi,
>>
>> Thanks for this point. In fact, I had initially not thought of a
>> scenario, where the map is being delivered through a retransmitted data
>> packet while its first transmission did not include the map. Now I am ju=
st
>> seeing the document (RFC 6824-bis) in this context.
>>
>> My understanding is that in scenarios like what I described in my
>> previous mail, RST is likely to happen whether we explicitly state so or
>> not. Please see the paragraph containing the below text in RFC 6824-bis.
>>
>> "If a mapping for that subflow-level sequence space does not arrive
>> within a receive window of data, that subflow SHOULD be treated as broke=
n,
>> closed with a RST, and any unmapped data silently discarded."
>>
>> if we assume that the map is included while retransmitting the data (eve=
n
>> though the first transmission did not contain the map for some reasons),
>>  we could argue that RST could be avoided provided that the retransmissi=
on
>> is triggered within a receive window of data. But the question here woul=
d
>> be how and when will the retransmission take place. In this case, the
>> subflow may not initiate the retransmission of data by its own (i.e., no
>> retransmission due to three duplicate ACKs or RTO expiry at subflow leve=
l)
>> as there is no segment loss at subflow level sequence space. So there co=
uld
>> be a high possibility of RST happening even before the map delivery thro=
ugh
>> retransmission.
>>
>> With regards,
>>
>> Anil
>>
>> ------------------------------
>> *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>
>> *To: *"V Anil Kumar" <anil@csir4pi.in>
>> *Cc: *"alan ford" <alan.ford@gmail.com>, "multipathtcp" <
>> multipathtcp@ietf.org>
>> *Sent: *Saturday, February 1, 2020 3:39:51 AM
>> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation
>> feedback
>>
>> Hi Anil,
>>
>> I have a question about your proposed text.
>> I am actually wondering if we really want to terminate connection here.
>>
>> The packets without proper mappings will be treated as invalid and will
>> be discarded.
>> If an implementation failed to attach proper mapping for some reasons
>> (e.g. option space), it might be able to attach the proper one when it
>> retransmits the packets. This also looks ok to me.
>>
>> I don't have strong preference for this. But, do we have a reason to
>> terminate connection?
>>
>> Thanks,
>> --
>> Yoshi
>>
>> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in> wrote:
>>
>>> Hi,
>>>
>>> I have some points related to the  modifications (Change 2) being
>>> proposed on data sequence map. Please see them inline. Though I am
>>> putting forward the below points, if the consensus is in favour of the
>>> proposed change for reducing implementation complexity, I am also OK wi=
th
>>> that as well.
>>>
>>> ------------------------------
>>> *From: *"alan ford" <alan.ford@gmail.com>
>>> *To: *multipathtcp@ietf.org
>>> *Sent: *Thursday, January 2, 2020 4:21:32 AM
>>> *Subject: *[multipathtcp] RFC6824bis edits based on implementation
>>> feedback
>>>
>>> Hi all,
>>> We=E2=80=99d love to get this to a state of completion as soon as possi=
ble, and
>>> to this end I am starting a new thread on this topic. In discussion wit=
h
>>> the chairs, it *is *possible to make the desired changes in AUTH48 as
>>> long as there is WG consensus. The discussion so far has been fairly
>>> limited in terms of participation.
>>>
>>> I would ask the chairs please if it was possible to specify a time boun=
d
>>> for this discussion and a default conclusion.
>>>
>>> Regarding the changes, in summary, there are two areas where changes
>>> have been requested by the implementation community. As we are the IETF=
 we
>>> obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so ea=
se of implementing
>>> standards-compliant code is strongly desirable. However, we do not wish=
 to
>>> reduce functionality agreed by the IETF community if it is considered a
>>> required feature by the community.
>>>
>>>
>>> *Change 1*
>>>
>>> Change the sentence reading:
>>>
>>>
>>> *   If B has data to send first, then the reliable delivery of the ACK =
+
>>> MP_CAPABLE can be inferred by the receipt of this data with an MPTCP Da=
ta
>>> Sequence Signal (DSS) option (Section 3.3). *
>>> To:
>>>
>>>
>>> *   If B has data to send first, then the reliable delivery of the ACK =
+
>>> MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data
>>> Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for th=
e
>>> MP_CAPABLE (which is the first octet of the data sequence space).*
>>> What this means:
>>>
>>> The current text is concerned only with ensuring a path is MPTCP
>>> capable, and so only cares that DSS option occurs on a data packet.
>>> However, the MP_CAPABLE option is defined to occupy the first octet of =
data
>>> sequence space and thus, if analogous to TCP, must be acknowledged. >Fr=
om
>>> an implementation point of view it would make sense not to have this
>>> hanging around forever and instead define it is acknowledged at the
>>> connection level as soon as received. This change ensures the first dat=
a
>>> packet also DATA_ACKs this MP_CAPABLE octet.
>>>
>>>
>>> *Change 2*
>>>
>>> Change the sentence reading:
>>>
>>> *   A Data Sequence Mapping does not need to be included in every MPTCP
>>> packet, as long as the subflow sequence space in that packet is covered=
 by
>>> a mapping known at the receiver.*
>>>
>>> To:
>>>
>>>
>>> *   The mapping provided by a Data Sequence Mapping MUST apply to some
>>> or all of the subflow sequence space in the TCP segment which carries t=
he
>>> option. It does not need to be included in every MPTCP packet, as long =
as
>>> the subflow sequence space in that packet is covered by a mapping known=
 at
>>> the receiver.*
>>> What this means:
>>>
>>> The current text does not place any restrictions on where a mapping
>>> could appear. In theory a sender could define a thousand different mapp=
ings
>>> up front, send them all, and expect a receiver to store this and reasse=
mble
>>> data according to these mappings as it arrives. Indeed, this was never
>>> explicitly disallowed since it =E2=80=9Cmight have been useful=E2=80=9D=
. The implementation
>>> community, however, has expressed concerns over the difficulty of
>>> implementing this open-endedly. How many mappings is it reasonable to
>>> store? Is there a DoS risk here? Instead, it has been requested that th=
ee
>>> specification restricts the placement of the DSS option to being within=
 the
>>> subflow sequence space to which it applies.
>>>
>>> Below are my comments on this. I had shared some of these points in a
>>> previous thread that you had initiated in the same context.
>>>
>>> Transmitting large number of non-contiguous data sequence maps could be
>>> a misbehaviour (map-flooding), though it is not clear whether this can =
go
>>> to the extent of causing a potential DoS to the data receiver. So some =
sort
>>> of restriction on this could be useful.  One approach could be to insis=
t
>>> that the data sender should ensure that the map being transmitted is fo=
r
>>> in-window data, as per the receiver advertised window. A receiver shoul=
d
>>> anyhow be willing to store the maps for in-window data to deal with pac=
ket
>>> loss. For example, when a window of data segments (say 1 to 64) is
>>> transmitted, each carrying its corresponding map, and segment-1 is lost=
,
>>> the maps for the remaining 63 need to be stored till the lost segment i=
s
>>> retransmitted. Of course, in this case the maps will be stored at the
>>> receiver side along with their corresponding data. But the need to stor=
e
>>> multiple maps for in-window data would still be there.
>>>
>>> The problem with the proposed change (restriction) is that a data sende=
r
>>> may find it difficult, in case a need arise to slightly delay the map
>>> delivery by few segments, i.e., sending some data first without map, an=
d
>>> then send the corresponding map in a later segment, as shown below:
>>>
>>> subflow-1:      segment-1                   segment-3
>>> segment-4                       segment-7
>>>                       bytes:1-100                 bytes:201-300
>>>      bytes:301-400                 bytes:601-700
>>>                       no map                        map for 1-100
>>>        map for 201-400             map for 601-700
>>>
>>>
>>>
>>> subflow-2:       segment-2                  segment-5
>>>   segment-6                       segment-8
>>>                        bytes: 101-200           bytes:401-500
>>>         bytes: 501-600                bytes:701-800
>>>                        map for 101-200       map for 401-600
>>>  no map                            map for 701-800
>>>
>>>
>>> In the above case, segment-1 goes without map and its map is included
>>> later in segment-3, the next data segment in the same subflow. Further,=
  in
>>> the above scheduling pattern, the map in segment-3 cannot cover the  da=
ta
>>> in segment-1 and segment-3, as some  data in between (segment-2) is
>>> transmitted through another subflow.  With the proposed change, the map=
 in
>>> segment-3 will become invalid and this will eventually break subflow-1,
>>> though this could be a corner case.
>>>
>>> The question at this stage is why would segment-1 be transmitted withou=
t
>>> its map. In the case of bidirectional data transfer, there could be a n=
eed
>>> to pack both timestamp and SACK  options in a data segment, i.e.,
>>> piggybacking of  SACK with data. If we consider that timestamp takes 12
>>> bytes and SACK, even with single block,  takes another 10 bytes, the
>>> remaining 18 bytes option space is not adequate to carry data sequence
>>> signal with map, especially when DSN is 64 bit long. So the delivery of
>>> either of the two (SACK or map) would be delayed.
>>>
>>> As far as I understand, RFC 2018 (TCP Selective Acknowledgement Options=
)
>>> implies that SACK should not be delayed. It states "If sent at all, SAC=
K
>>> options SHOULD be included in all ACKs which do not ACK the highest
>>> sequence number in the data receiver's queue". It also says "If data
>>> receiver generates SACK options under any circumstance, it SHOULD gener=
ate
>>> them under all permitted circumstances".   So, as part of meeting the R=
FC
>>> 2018 requirements, if the combination of SACK and timestamp is given
>>> preference over DSS, data segments could be transmitted without their m=
ap.
>>>
>>> Another case of delaying map could arise if the data sender prefers to
>>> send ADD_ADDR option, instead of map, in a data segment. It is nice tha=
t
>>> ADD_ADDR option can be delivered reliably in a pure ACK, but I think th=
is
>>> is not the case with DSS at present.
>>>
>>> If we adopt the proposed change, I think it might also be helpful to
>>> spell out how the receiver is supposed to behave, if it gets maps not
>>> meeting the MUST condition in the proposed change.  For example termina=
tion
>>> of the subflow with MP_TCPRST option (section 3.6 in RFC 6824-bis) with
>>> appropriate reason code and T flag value to intimate the data sender th=
e
>>> cause for subflow termination.
>>>
>>> With regards,
>>>
>>> Anil
>>>
>>> Please can members of the WG express whether they are happy with these
>>> changes, or concerned.
>>>
>>> Best regards,
>>> Alan
>>>
>>>
>>> _______________________________________________
>>> multipathtcp mailing list
>>> multipathtcp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>>
>>>
>>>
>>> _______________________________________________
>>> multipathtcp mailing list
>>> multipathtcp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>>
>>
>>
>>
>
>
>
>
>
>
>

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

<div dir=3D"ltr"><div>Hi folks,</div><div>I guess we might want to know the=
 behavior of existing implementations such as linux.</div><div>When an mptc=
p stack tries to send a data packet and find that there&#39;s no enough opt=
ion space for data mapping, what it will do?</div><div>Split the packet to =
create more option space?</div><div>--<br></div><div>Yoshi</div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 6, 20=
20 at 10:10 AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in">anil@csi=
r4pi.in</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div><div><div>Hi Alan,</div><div><br></div><div>Thank you for your =
reply. I have two points to clarify. Please see them in line.</div><div><br=
></div><hr id=3D"gmail-m_8773357439777081590zwchr"><div><blockquote style=
=3D"border-left:2px solid rgb(16,16,255);margin-left:5px;padding-left:5px;c=
olor:rgb(0,0,0);font-weight:normal;font-style:normal;text-decoration:none;f=
ont-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: </b>&quot;Al=
an Ford&quot; &lt;<a href=3D"mailto:alan.ford@gmail.com" target=3D"_blank">=
alan.ford@gmail.com</a>&gt;<br><b>To: </b>&quot;V Anil Kumar&quot; &lt;<a h=
ref=3D"mailto:anil@csir4pi.in" target=3D"_blank">anil@csir4pi.in</a>&gt;jk=
=C2=A0<br><b>Cc: </b>&quot;Yoshifumi Nishida&quot; &lt;<a href=3D"mailto:ns=
d.ietf@gmail.com" target=3D"_blank">nsd.ietf@gmail.com</a>&gt;, &quot;multi=
pathtcp&quot; &lt;<a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank=
">multipathtcp@ietf.org</a>&gt;<br><b>Sent: </b>Thursday, February 6, 2020 =
2:49:29 AM<br><b>Subject: </b>Re: [multipathtcp] RFC6824bis edits based on =
implementation feedback<br></blockquote></div><div><blockquote style=3D"bor=
der-left:2px solid rgb(16,16,255);margin-left:5px;padding-left:5px;color:rg=
b(0,0,0);font-weight:normal;font-style:normal;text-decoration:none;font-fam=
ily:Helvetica,Arial,sans-serif;font-size:12pt">Hi Anil,<div><br></div><div>=
This would not be forbidden if the mapping was carried on a pure ACK with n=
o data.</div></blockquote><div>As far as I understand, delivery of DSM thro=
ugh pure ACK is not in the scope of the current draft. If we intend to do t=
his, we may need an approach similar to the one proposed for delivery of AD=
D_ADDR option in pure ACK with reliability feature.=C2=A0 So, packing DSM o=
n pure ACK does not seem to be an option at this stage.</div><blockquote st=
yle=3D"border-left:2px solid rgb(16,16,255);margin-left:5px;padding-left:5p=
x;color:rgb(0,0,0);font-weight:normal;font-style:normal;text-decoration:non=
e;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div><br></div><di=
v>I do see the point here: if a packet of 1000 bytes contains 500 bytes of =
one mapping and 500 bytes of another mapping, then only one DSM would appea=
r on one packet, leaving the mapping for the second 500 bytes to be carried=
 somewhere else - the only option being a pure ACK. But this kind of scenar=
io would be extremely rare</div></blockquote><div>Yes, I do agree that the =
scenario you mentioned above would be extremely rare. In fact, I wonder whe=
ther such a situation (i.e., need to cover the bytes in a single packet wit=
h two different maps) would ever arise. Probably there might be some corner=
 cases, which I don&#39;t get it rightly now.=C2=A0</div><div><br></div><di=
v>More importantly, the scenario that Yoshi and me are referring to is tota=
lly different: the one I had given as part of my comments in response to th=
e proposed change 2. In this scenario, which you could see in the trailing =
mail, data segment-1 is transmitted without including its map, something wh=
ich is permitted in the =C2=A0mptcp framework (6824 bis). I make this infer=
ence from the below text in 6824 bis:</div><div><br></div><div> &quot;...ev=
en if a mapping does not exist from the subflow space to the data- level sp=
ace, the data SHOULD still be ACKed at the subflow (if it is in-window). Th=
is data cannot, however, be acknowledged at the data level (Section 3.3.2) =
because its data sequence numbers are unknown. Implementations MAY hold ont=
o such unmapped data for a short while in the expectation that a mapping wi=
ll arrive shortly.&quot; </div><div><br></div><div>One option the data send=
er has at this stage is to include the map for data in segment-1, in segmen=
t-3 (please see the two-subflow example I gave in response to the change 2 =
you had proposed). But the proposed change does not permit this. What would=
 happen to =C2=A0subflow-1 in this case ?</div><div><br></div><div>With reg=
ards,</div><div><br></div><div>Anil =C2=A0 =C2=A0</div><blockquote style=3D=
"border-left:2px solid rgb(16,16,255);margin-left:5px;padding-left:5px;colo=
r:rgb(0,0,0);font-weight:normal;font-style:normal;text-decoration:none;font=
-family:Helvetica,Arial,sans-serif;font-size:12pt"><div>and I would imagine=
 any implementation would just split into two 500 byte segments each with t=
he PSH flag set. I don=E2=80=99t think we need to spell this out in the spe=
c however.</div><div><br></div><div>Regards,</div><div>Alan<br><div><div><b=
r><blockquote><div>On 5 Feb 2020, at 15:09, V Anil Kumar &lt;<a href=3D"mai=
lto:anil@csir4pi.in" rel=3D"nofollow noopener noreferrer" target=3D"_blank"=
>anil@csir4pi.in</a>&gt; wrote:</div><div><div><div style=3D"font-family:ar=
ial,helvetica,sans-serif"><div><div style=3D"font-family:arial,helvetica,sa=
ns-serif"><div><div style=3D"font-family:arial,helvetica,sans-serif"><div><=
div style=3D"font-family:arial,helvetica,sans-serif"><div>Hi Yoshi,</div><b=
r><div>Please see in line.</div><br><hr id=3D"gmail-m_8773357439777081590zw=
chr"><div><b>From: </b>&quot;Yoshifumi Nishida&quot; &lt;<a href=3D"mailto:=
nsd.ietf@gmail.com" rel=3D"nofollow noopener noreferrer" target=3D"_blank">=
nsd.ietf@gmail.com</a>&gt;<br><b>To: </b>&quot;V Anil Kumar&quot; &lt;<a hr=
ef=3D"mailto:anil@csir4pi.in" rel=3D"nofollow noopener noreferrer" target=
=3D"_blank">anil@csir4pi.in</a>&gt;<br><b>Cc: </b>&quot;alan ford&quot; &lt=
;<a href=3D"mailto:alan.ford@gmail.com" rel=3D"nofollow noopener noreferrer=
" target=3D"_blank">alan.ford@gmail.com</a>&gt;, &quot;multipathtcp&quot; &=
lt;<a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow noopener norefe=
rrer" target=3D"_blank">multipathtcp@ietf.org</a>&gt;<br><b>Sent: </b>Tuesd=
ay, February 4, 2020 1:08:45 PM<br><b>Subject: </b>Re: [multipathtcp] RFC68=
24bis edits based on implementation feedback<br></div><br><div><div dir=3D"=
ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><br><div>Thanks f=
or pointing it out. I overlooked this one.</div><div>This looks an interest=
ing point.<br></div><br><div>It seems to me that whether RST is happen or n=
ot depends on the size of receive window according to the text.<br></div><d=
iv>If the receive window size is big enough to accommodate=C2=A0segment 1 a=
nd segment 3, the text &quot;<span style=3D"font-size:13.3333px">Implementa=
tions MAY hold onto such unmapped data for a short while in=C2=A0</span><sp=
an style=3D"font-size:13.3333px">the expectation that a mapping will arrive=
 shortly. &quot;=C2=A0</span>can be applied to the segment 1. As a result, =
the segment 1 won&#39;t be discarded.=C2=A0</div><br><div><em>Yes.=C2=A0 So=
, segment 1 may be kept in the data receiver&#39;s buffer in expectation th=
at its mapping will arrive shortly. And in the example that we are referrin=
g to, the data sender will not be able to include the map for the data in s=
egment 1 in segment 3 or any higher segment.</em></div><br><div><em>Regards=
,</em></div><br><div><em>Anil</em></div><br><div>However, this might be con=
tradict with the new texts Alan proposed? Or, am I missing something?</div>=
<br><div>Thanks,</div><div>--</div><div>Yoshi</div><br><br><br><div><div di=
r=3D"ltr">On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar &lt;<a href=3D"mailto=
:anil@csir4pi.in" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noop=
ener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%=
20noreferrer nofollow noopener noreferrer" target=3D"_blank">anil@csir4pi.i=
n</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><div><div><div><div style=3D"font-family:arial,helvetica,sans-serif"><div>=
Hi Yoshi,</div><br><div>Thanks for this point. In fact, I had initially not=
 thought of a scenario, where the map is being delivered through a retransm=
itted data packet while its first transmission did not include the map. Now=
 I am just seeing the document (RFC 6824-bis) in this context.</div><br><di=
v>My understanding is that in scenarios like what I described in my previou=
s mail, RST is likely to happen whether we explicitly state so or not. Plea=
se see the paragraph containing the below text in RFC 6824-bis. =C2=A0</div=
><br><div>&quot;If a mapping for that subflow-level sequence space does not=
 arrive within a receive window of data, that subflow SHOULD be treated as =
broken, closed with a RST, and any unmapped data silently discarded.&quot;<=
/div><br><div>if we assume that the map is included while retransmitting th=
e data (even though the first transmission did not contain the map for some=
 reasons), =C2=A0we could argue that RST could be avoided provided that the=
 retransmission is triggered within a receive window of data. But the quest=
ion here would be how and when will the retransmission take place. In this =
case, the subflow may not initiate the retransmission of data by its own (i=
.e., no retransmission due to three duplicate ACKs or RTO expiry at subflow=
 level) as there is no segment loss at subflow level sequence space. So the=
re could be a high possibility of RST happening even before the map deliver=
y through retransmission.=C2=A0</div><br><div>With regards,=C2=A0</div><br>=
<div>Anil</div><div>=C2=A0</div><hr id=3D"gmail-m_8773357439777081590gmail-=
m_218086596951724501gmail-m_2982267033577902985zwchr"><div><b>From: </b>&qu=
ot;Yoshifumi Nishida&quot; &lt;<a href=3D"mailto:nsd.ietf@gmail.com" rel=3D=
"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofo=
llow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow no=
opener noreferrer" target=3D"_blank">nsd.ietf@gmail.com</a>&gt;<br><b>To: <=
/b>&quot;V Anil Kumar&quot; &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofoll=
ow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noop=
ener noreferrer" target=3D"_blank">anil@csir4pi.in</a>&gt;<br><b>Cc: </b>&q=
uot;alan ford&quot; &lt;<a href=3D"mailto:alan.ford@gmail.com" rel=3D"nofol=
low%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%2=
0noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener=
 noreferrer" target=3D"_blank">alan.ford@gmail.com</a>&gt;, &quot;multipath=
tcp&quot; &lt;<a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20no=
opener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopene=
r%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener norefer=
rer" target=3D"_blank">multipathtcp@ietf.org</a>&gt;<br><b>Sent: </b>Saturd=
ay, February 1, 2020 3:39:51 AM<br><b>Subject: </b>Re: [multipathtcp] RFC68=
24bis edits based on implementation feedback<br></div><br><div><div dir=3D"=
ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><br><div>I have a=
 question about your proposed text.</div><div><div>I am actually wondering =
if we really want to terminate connection here.=C2=A0</div></div><br><div>T=
he packets without proper mappings will be treated as invalid and will be d=
iscarded.=C2=A0</div><div>If an implementation failed to attach proper mapp=
ing for some reasons (e.g. option space), it might be able to attach the pr=
oper one when it retransmits the packets. This also looks ok to me.</div><b=
r><div>I don&#39;t have strong preference for this. But, do we have a reaso=
n to terminate connection?</div><br><div>Thanks,</div><div>--<br></div><div=
>Yoshi</div><br><div><div dir=3D"ltr">On Mon, Jan 13, 2020 at 10:28 AM V An=
il Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow%20noopener%=
20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20nor=
eferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferr=
er%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=
=3D"_blank">anil@csir4pi.in</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div><div><div><div style=3D"font-family:arial,h=
elvetica,sans-serif"><div><span style=3D"font-size:12pt;line-height:1.3">Hi=
,</span><br></div><div><div style=3D"font-family:arial,helvetica,sans-serif=
"><div style=3D"font-family:arial,helvetica,sans-serif"><div style=3D"font-=
family:arial,helvetica,sans-serif"><div style=3D"font-family:arial,helvetic=
a,sans-serif"><div style=3D"font-family:arial,helvetica,sans-serif"><div st=
yle=3D"font-family:arial,helvetica,sans-serif"><div style=3D"font-family:ar=
ial,helvetica,sans-serif"><br><div>I have some points related to the =C2=A0=
modifications (Change 2) being proposed on data sequence map. Please see th=
em inline.=C2=A0<span style=3D"font-family:arial,helvetica,sans-serif;font-=
size:16px;font-style:normal;font-weight:400;letter-spacing:normal;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px;background-c=
olor:rgb(255,255,255);float:none;display:inline">Though I am putting forwar=
d the below points, if the consensus is in favour of the proposed change fo=
r reducing implementation complexity, I am also OK with that as well.=C2=A0=
</span><br></div><br><hr id=3D"gmail-m_8773357439777081590gmail-m_218086596=
951724501gmail-m_2982267033577902985gmail-m_7687184382299596774zwchr"><div>=
<b>From: </b>&quot;alan ford&quot; &lt;<a href=3D"mailto:alan.ford@gmail.co=
m" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferr=
er%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20=
nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollo=
w noopener noreferrer" target=3D"_blank">alan.ford@gmail.com</a>&gt;<br><b>=
To: </b><a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noopener=
%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20no=
referrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20norefer=
rer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=
=3D"_blank">multipathtcp@ietf.org</a><br><b>Sent: </b>Thursday, January 2, =
2020 4:21:32 AM<br><b>Subject: </b>[multipathtcp] RFC6824bis edits based on=
 implementation feedback<br></div><br><div>Hi all,<br><div>We=E2=80=99d lov=
e to get this to a state of completion as soon as possible, and to this end=
 I am starting a new thread on this topic. In discussion with the chairs, i=
t <i>is </i>possible to make the desired changes in AUTH48 as long as there=
 is WG consensus. The discussion so far has been fairly limited in terms of=
 participation.</div><br><div>I would ask the chairs please if it was possi=
ble to specify a time bound for this discussion and a default conclusion.</=
div><br><div>Regarding the changes, in summary, there are two areas where c=
hanges have been requested by the implementation community. As we are the I=
ETF we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so=
 ease of implementing standards-compliant code is strongly desirable. Howev=
er, we do not wish to reduce functionality agreed by the IETF community if =
it is considered a required feature by the community.</div><br><br><div><b>=
Change 1</b></div><div><b><br></b></div><div>Change the sentence reading:<b=
r><br><i>=C2=A0 =C2=A0If B has data to send first, then the reliable delive=
ry of the ACK + MP_CAPABLE can be inferred by the receipt of this data with=
 an MPTCP Data Sequence Signal (DSS) option (Section 3.3).=C2=A0<br></i><br=
>To:<br><br><i>=C2=A0 =C2=A0If B has data to send first, then the reliable =
delivery of the ACK + MP_CAPABLE is ensured by the receipt of this data wit=
h an MPTCP Data Sequence Signal (DSS) option (Section 3.3) containing a DAT=
A_ACK for the MP_CAPABLE (which is the first octet of the data sequence=C2=
=A0space).<br></i><br></div><div>What this means:</div><br><div>The current=
 text is concerned only with ensuring a path is MPTCP capable, and so only =
cares that DSS option occurs on a data packet. However, the MP_CAPABLE opti=
on is defined to occupy the first octet of data sequence space and thus, if=
 analogous to TCP, must be acknowledged. &gt;From an implementation point o=
f view it would make sense not to have this hanging around forever and inst=
ead define it is acknowledged at the connection level as soon as received. =
This change ensures the first data packet also DATA_ACKs this MP_CAPABLE oc=
tet.</div><br><br><div><b>Change 2</b></div><div><b><br></b></div><div>Chan=
ge the sentence reading:<br><br><i>=C2=A0 =C2=A0A Data Sequence Mapping doe=
s not need to be included in every MPTCP packet, as long as the subflow seq=
uence space in that packet is covered by a mapping known at the receiver.</=
i><br><br>To:<br><br><i>=C2=A0 =C2=A0The mapping provided by a Data Sequenc=
e Mapping MUST apply to some or all of the subflow sequence space in the TC=
P segment which carries the option. It does not need to be included in ever=
y MPTCP packet, as long as the subflow sequence space in that packet is cov=
ered by a mapping known at the receiver.<br></i><br>What this means:</div><=
br><div>The current text does not place any restrictions on where a mapping=
 could appear. In theory a sender could define a thousand different mapping=
s up front, send them all, and expect a receiver to store this and reassemb=
le data according to these mappings as it arrives. Indeed, this was never e=
xplicitly disallowed since it =E2=80=9Cmight have been useful=E2=80=9D. The=
 implementation community, however, has expressed concerns over the difficu=
lty of implementing this open-endedly. How many mappings is it reasonable t=
o store? Is there a DoS risk here? Instead, it has been requested that thee=
 specification restricts the placement of the DSS option to being within th=
e subflow sequence space to which it applies.</div><br><div>Below are my co=
mments on this. I had shared some of these points in a previous thread that=
 you had initiated in the same context.=C2=A0</div><br><div>Transmitting la=
rge number of non-contiguous data sequence maps could be a misbehaviour (ma=
p-flooding), though it is not clear whether this can go to the extent of ca=
using a potential DoS to the data receiver. So some sort of restriction on =
this could be useful.=C2=A0 One approach could be to insist that the data s=
ender should ensure that the map being transmitted is for in-window data, a=
s per the receiver advertised window. A receiver should anyhow be willing t=
o store the maps for in-window data to deal with packet loss. For example, =
when a window of data segments (say 1 to 64) is transmitted, each carrying =
its corresponding map, and segment-1 is lost, the maps for the remaining 63=
 need to be stored till the lost segment is retransmitted. Of course, in th=
is case the maps will be stored at the receiver side along with their corre=
sponding data. But the need to store multiple maps for in-window data would=
 still be there.</div><br><div><span style=3D"font-family:arial,helvetica,s=
ans-serif;font-size:16px;font-style:normal;font-weight:normal;letter-spacin=
g:normal;line-height:20.8px;text-indent:0px;text-transform:none;white-space=
:normal;word-spacing:0px;float:none;background-color:rgb(255,255,255);displ=
ay:inline">The problem with the proposed change (restriction) is that a dat=
a sender may find it difficult, in case a need arise to slightly delay the =
map delivery by few segments, i.e., sending some data first without map, an=
d then send the corresponding map in a later segment, as shown below:</span=
><br></div><br><div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lu=
cida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:=
normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transf=
orm:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rg=
b(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">subflow-1:=C2=
=A0 =C2=A0 =C2=A0 segment-1=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 segment-3=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-4 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 segment-7</span></div><div style=3D"font-family:&quot;segoe ui&quot;,&q=
uot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-w=
eight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-=
transform:none;white-space:normal;word-spacing:0px;margin:0px;background-co=
lor:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">=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=C2=A0=C2=A0=C2=A0bytes:1-100 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 bytes:201-300 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0bytes:301-400 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 bytes:601-700</span></div><div style=3D"font-family:&=
quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;fo=
nt-style:normal;font-weight:normal;letter-spacing:normal;line-height:normal=
;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;ma=
rgin:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"f=
ont-size:10pt">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0=C2=A0no map =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0map for 1-100 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0map for 201-400 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 map for 601-700</span></div><div style=3D"font-family:&quot;sego=
e ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:=
normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-ind=
ent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;=
background-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:=
10pt"><br></span></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot=
;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weig=
ht:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;margin:0px;background-color=
:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt"><br></span=
></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quo=
t;,sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter=
-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;whit=
e-space:normal;word-spacing:0px;margin:0px;background-color:rgb(255,255,255=
)"><br></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sa=
ns&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;=
letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:non=
e;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(255,2=
55,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">subflow-2:=C2=A0 =C2=
=A0 =C2=A0 =C2=A0segment-2=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 segment-5 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 segment-6 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-8</span></div><div style=3D"font=
-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:1=
4.16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-heig=
ht:normal;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;margin:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" s=
tyle=3D"font-size:10pt">=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=C2=A0=C2=A0=C2=
=A0=C2=A0bytes: 101-200 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 bytes:401-500=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 bytes: 501-600 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0b=
ytes:701-800=C2=A0=C2=A0=C2=A0</span></div><div style=3D"font-family:&quot;=
segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-st=
yle:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:=
0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-s=
ize:10pt">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0map for 101-200 =C2=A0 =C2=A0 =C2=A0 map for 401-600 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0no map =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=A0map f=
or 701-800</span></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot=
;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weig=
ht:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;margin:0px;background-color=
:rgb(255,255,255)"><br></div><div style=3D"font-family:&quot;segoe ui&quot;=
,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;fon=
t-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;margin:0px;background=
-color:rgb(255,255,255)"><br></div>In the above case, segment-1 goes withou=
t map and its map is included later in segment-3, the next data segment in =
the same subflow. Further, =C2=A0in the above scheduling pattern, the map i=
n segment-3 cannot cover the =C2=A0data in segment-1 and segment-3, as some=
 =C2=A0data in between (segment-2) is transmitted through another subflow.=
=C2=A0 With the proposed change, the map in segment-3 will become invalid a=
nd this will eventually break subflow-1, though this could be a corner case=
.</div><br><div>The question at this stage is why would segment-1 be transm=
itted without its map. In the case of bidirectional data transfer, there co=
uld be a need to pack both timestamp and SACK =C2=A0options in a data segme=
nt, i.e., piggybacking of =C2=A0SACK with data. If we consider that timesta=
mp takes 12 bytes and SACK, even with single block, =C2=A0takes another 10 =
bytes, the remaining 18 bytes option space is not adequate to carry data se=
quence signal with map, especially when DSN is 64 bit long. So the delivery=
 of either of the two (SACK or map) would be delayed.</div><br><div>As far =
as I understand, RFC 2018 (TCP Selective Acknowledgement Options) implies t=
hat SACK should not be delayed. It states &quot;If sent at all, SACK option=
s SHOULD be included in all ACKs which do not ACK the highest sequence numb=
er in the data receiver&#39;s queue&quot;. It also says &quot;If data recei=
ver generates SACK options under any circumstance, it SHOULD generate them =
under all permitted circumstances&quot;. =C2=A0 So, as part of meeting the =
RFC 2018 requirements, if the combination of SACK and timestamp is given pr=
eference over DSS, data segments could be transmitted without their map.=C2=
=A0</div><br><div>Another case of delaying map could arise if the data send=
er prefers to send ADD_ADDR option, instead of map, in a data segment. It i=
s nice that ADD_ADDR option can be delivered reliably in a pure ACK, but I =
think this is not the case with DSS at present.</div><br><div>If we adopt t=
he proposed change, I think it might also be helpful to spell out how the r=
eceiver is supposed to behave, if it gets maps not meeting the MUST conditi=
on in the proposed change.=C2=A0 For example termination of the subflow wit=
h MP_TCPRST option (section 3.6 in RFC 6824-bis) with appropriate reason co=
de and T flag value to intimate the data sender the cause for subflow termi=
nation.=C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</div></div=
><div>With regards,</div><br><div>Anil<br><br><div>Please can members of th=
e WG express whether they are happy with these changes, or concerned.</div>=
<br><div>Best regards,</div><div>Alan</div><br><br>________________________=
_______________________<br>multipathtcp mailing list<br><a href=3D"mailto:m=
ultipathtcp@ietf.org" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20=
noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noope=
ner%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%2=
0noreferrer nofollow noopener noreferrer" target=3D"_blank">multipathtcp@ie=
tf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp=
" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferre=
r%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow=
 noopener noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/multipathtcp</a></div></div></div></div></div></div></div></div></div></=
div><br></div></div></div><br><br>_________________________________________=
______<br>multipathtcp mailing list<br><a href=3D"mailto:multipathtcp@ietf.=
org" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20norefe=
rrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%=
20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofol=
low noopener noreferrer" target=3D"_blank">multipathtcp@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"noreferr=
er%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20=
nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofol=
low%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noo=
pener noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/m=
ultipathtcp</a><br></blockquote></div></div></div></div></div></div><br></d=
iv></div><br></div></blockquote></div></div></div></div></div></div></div><=
/div></div></div><br></div></div><br><br></div></div></blockquote></div><br=
></div></div><br></blockquote></div></div>
<br>
<br></div></blockquote></div></div>

--000000000000774b0b059e49290e--


From nobody Tue Feb 11 07:57:18 2020
Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747661201E3 for <multipathtcp@ietfa.amsl.com>; Tue, 11 Feb 2020 07:57:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 (1024-bit key) header.d=bt.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 gFWtU0LGHf_8 for <multipathtcp@ietfa.amsl.com>; Tue, 11 Feb 2020 07:57:11 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB420120164 for <multipathtcp@ietf.org>; Tue, 11 Feb 2020 07:57:10 -0800 (PST)
Received: from tpw09926dag11e.domain1.systemhost.net (10.9.212.11) by BWP09926082.bt.com (10.36.82.113) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 11 Feb 2020 15:57:08 +0000
Received: from tpw09926dag06e.domain1.systemhost.net (10.9.202.21) by tpw09926dag11e.domain1.systemhost.net (10.9.212.11) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Feb 2020 15:57:08 +0000
Received: from bwp09926077.bt.com (10.36.82.108) by tpw09926dag06e.domain1.systemhost.net (10.9.202.21) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 11 Feb 2020 15:57:08 +0000
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.57) by smtpe1.intersmtp.com (10.36.82.108) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 11 Feb 2020 15:56:55 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VCclZcTVy0j4S5YteFluluN+5qxsqMdn1zvrXNrlZW2x5TCt2rVtm8tC2UhB/eDPObZGKOuL77NDAYYrpmiqv9H7J3sFWiwdZ5pV5XuniJGC3n3FI9dfUxCnF61W8xENjW4uALzOXuWNTU1BkoFoRHMYIuqiNS35uwVVVtRqRJgBphpZxWGawTJ1hLN8SJi/H28zSPbo9ZJBSzZ/fy1j070iHLIL+/ThE7Df/B1Opvvl/duDKZ9+t9bqjo8QwZE6Aac6z87zHSplY58hKYlJvLgb3K8eKpL0G1XdLQmaWWutPj5d9ZKyUHMxrT06gfgPhHrP5fyn/CaXRFm2zQzlBg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ECJeO/OBsUNw6oE4eDipPGP5E4wy6ipjD5YbPQufRt4=; b=dvagbKBiT007nwOx9Qh1ucn2hJbCr5e4W4yYWhHkIi58sc5LvUTmL8bkkK0DPd4tjAafyMU5eOlaMno/KF9vf613dkxMGM2YMYB72IWmHLluyRoqsPIkde+056QrcfdAcL1RI5G+Q3hYLOP3fx1lrbTUGrtSgArQRaGSB30LVz6b+EXpkvkt8JRTo2MPe6hFtHGyRVGixjl8cGzIVfGM18+xHjDgskStfzAVwjXP4PWc7w5UwyNhBL6q2bG9krXXpGObxzS6oFxPwB236YUKcYLbztWNj/Mb0NDYCD2PSW+ZcDX0CZM8uO+EjxQ2S0QkkGtnAZPoS6e9uY4dKL4PRA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ECJeO/OBsUNw6oE4eDipPGP5E4wy6ipjD5YbPQufRt4=; b=kpgKM0PDmgwS8BbKOCYa+zOQyQjQEyTopZV5bP1k0yAyctMKBCv2jj4ev32vAbvwSFFL3Y/SlBUJ3TivbDM5YLfIcpK/Lcx+C/Xi5AJgrhSkFwo4YLQO5NROCy13IOfFLgCq5bWPZQP048sHGZJlmU/P7uCMcpP1xjdbFXsxhj0=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXP123MB1738.GBRP123.PROD.OUTLOOK.COM (20.176.159.74) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.26; Tue, 11 Feb 2020 15:57:03 +0000
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c]) by LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c%7]) with mapi id 15.20.2707.030; Tue, 11 Feb 2020 15:57:03 +0000
From: <philip.eardley@bt.com>
To: <anil@csir4pi.in>, <alan.ford@gmail.com>
CC: <multipathtcp@ietf.org>
Thread-Topic: RFC6824bis edits based on implementation feedback
Thread-Index: AQHV3RjL6VxwEBgdwkqcNWw1sb7yeagWKYYA
Date: Tue, 11 Feb 2020 15:57:03 +0000
Message-ID: <LNXP123MB258719E5B3D9F99B7E715111EB180@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com> <1411057985.31281938.1581012439446@csir4pi.in>
In-Reply-To: <1411057985.31281938.1581012439446@csir4pi.in>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com; 
x-originating-ip: [193.113.37.9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 58056dbb-d3e0-47a5-e814-08d7af0b0968
x-ms-traffictypediagnostic: LNXP123MB1738:
x-microsoft-antispam-prvs: <LNXP123MB17385ECABFCA3E0F12873D37EB180@LNXP123MB1738.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0310C78181
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(366004)(376002)(396003)(39860400002)(189003)(199004)(966005)(316002)(110136005)(76116006)(478600001)(66946007)(2906002)(81166006)(81156014)(8676002)(9686003)(55016002)(8936002)(5660300002)(66556008)(64756008)(7696005)(66446008)(52536014)(66476007)(71200400001)(4326008)(86362001)(30864003)(6506007)(26005)(53546011)(186003)(33656002)(559001)(579004); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXP123MB1738; H:LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 4ZOp5C6iP79iN4KgkCqe/nH7JDbH39CkKFb4VOfWvj+UdiZLnCMC/U8Mto4PTp8nXKy+uczYQe3O7KCUTfurOTb1ru7Lzl0sK95yoL6WX6GpdCuoHdjxvPCQLD4vcIgKRecOHLZCPRrLiVnruirQqvAJvG25zI89Xae0H95GvLuuSJ/yGMf5RVKwRgv3dX3P5tzgNs+mGZSkjU1hoTB1mQTG2KfrLR6MGGjhVhk3zRR8MT2nyK3VSXvNszb6+qnOLV5IwHUBsWwp6A12GIHUIqldruH0sQkDsPsH/GVLQcLQgfwR8ln/8Jrxph9ewO1F6LdC7Mg7NzMrz1xlY/r6j9Koon+mhS3A9kkR2rLAzxmzjUZuaO/QknpO1lSyLCWKDy8hQU10mIO7Ej8v0sBCiEe8cv3/a7rS43+xa7WIGXVr5dDlavBWlFMVBRq8W6zxH23B1BtYJ/FRCOh+NlQrEp4XtnpEHFNbsg2t/eshZjQZbIX3Z4t3pj8Qe1Am1J/Q8TbsOgB9GXG4sJ1Pn48Rmw==
x-ms-exchange-antispam-messagedata: S1qwwdedsTgnihhTYJsO9eRyZz2xvp0oOhb2btMHM2diIx82KNT6DhnQwfhVDN/r/YuPIDBdmjQur2V2UOiiOWTWHgGMUCgGGrjDZ6TlrwrMTbytbT641t/tgf82EM62kbiTU1ghw24+6DGb+0wc6A==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB258719E5B3D9F99B7E715111EB180LNXP123MB2587GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 58056dbb-d3e0-47a5-e814-08d7af0b0968
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Feb 2020 15:57:03.1117 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: r/zohJ21dLIr+kqUpP6VTNys1YYnvpnd0NV2tSv1gP4ZErRZExsmQaLVtAQgsOwsVlLrLE06CqOWEM6ILPFUVA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB1738
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/vC9-DnaDL7P4vi0lv4TaRF00EKY>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2020 15:57:17 -0000

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

U28gY29taW5nIGJhY2sgdG8gQW5pbOKAmXMgKG9yaWdpbmFsKSBxdWVzdGlvbi4NCg0KQSBwYWNr
ZXQgd2l0aCB0aW1lc3RhbXAgYW5kIFNBQ0sgb3B0aW9ucyBsaWtlbHkgd29u4oCZdCBoYXZlIHJv
b20gZm9yIHRoZSBEU1Mgb3B0aW9uLCB0aGVyZWZvcmUgdGhlIERTUyBtYXBwaW5nIHdvdWxkIGJl
IGRlbGF5ZWQuIFRoaXMgbWF5IG1lYW4gdGhlIHRyYW5zbWl0dGVkIHNlZ21lbnQgaXMgbm90IGNv
dmVyZWQgYnkgYSBEU1MgbWFwLiBUaGlzIHdvdWxkIGZhaWwgdGhlIE1VU1QgaW4gQ2hhbmdlIDIg
d2hpY2ggKEkgdGhpbmspIG1lYW5zIHRoZSBzdWJmbG93IGlzIGNsb3NlZCBpbW1lZGlhdGVseS4N
Cg0KU29tZSBvcHRpb25zOg0KDQogICogICBJdOKAmXMgYSByYXJlIGNhc2UgdGhhdCB3ZSBkb27i
gJl0IG5lZWQgdG8gd29ycnkgYWJvdXQuDQogICogICBNYWtlIENoYW5nZSAyIGEgU0hPVUxEIHJh
dGhlciB0aGFuIGEgTVVTVA0KICAqICAgRXh0ZW5kIENoYW5nZSAyIHNvIGl0IHNheXMgc29tZXRo
aW5nIGxpa2U6IFRoZSBtYXBwaW5nIHByb3ZpZGVkIGJ5IGEgRGF0YSBTZXF1ZW5jZSBNYXBwaW5n
IE1VU1QgYXBwbHkgdG8gc29tZSBvciBhbGwgb2YgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2Ug
aW4gdGhlIFRDUCBzZWdtZW50IHdoaWNoIGNhcnJpZXMgdGhlIG9wdGlvbiBbKyBuZXcgdGV4dF0g
b3IgYmUgY292ZXJlZCBieSB0aGUgbmV4dCBzZWdtZW50LiAgT3Ig4oCcd2l0aGluIHRoZSBuZXh0
IGZldyBzZWdtZW50c+KAnQ0KICAqICAgPw0KDQpGb3IgYW55IG9mIHRoZXNlLCBpdCB3b3VsZCBi
ZSB3b3J0aHdoaWxlIGFkZGluZyBhbiBleHBsYW5hdG9yeSBub3RlIHRvIENoYW5nZSAyLg0KDQpJ
dCB3b3VsZCBiZSByZWFsbHkgZ29vZCBpZiB3ZSBjb3VsZCBjb25jbHVkZSBvbiB0aGlzLg0KDQpQ
ZXJzb25hbGx5IEnigJlkIGxpa2Ugc29tZXRoaW5nIHRoYXQgcmVmbGVjdHMgdGhlIGNvbnNlbnN1
cyBpbXBsaWNpdCBpbiB0aGUgaW1wbGVtZW50YXRpb25zLCBidXQgd2l0aG91dCBhbnl0aGluZyBv
dGhlciB0aGFuIHJhcmUgY29ybmVyIGNhc2VzLg0KDQpUaGFua3MNCnBoaWwNCg0KDQpGcm9tOiBt
dWx0aXBhdGh0Y3AgPG11bHRpcGF0aHRjcC1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2Yg
ViBBbmlsIEt1bWFyDQpTZW50OiAwNiBGZWJydWFyeSAyMDIwIDE4OjA3DQpUbzogQWxhbiBGb3Jk
IDxhbGFuLmZvcmRAZ21haWwuY29tPg0KQ2M6IG11bHRpcGF0aHRjcCA8bXVsdGlwYXRodGNwQGll
dGYub3JnPg0KU3ViamVjdDogUmU6IFttdWx0aXBhdGh0Y3BdIFJGQzY4MjRiaXMgZWRpdHMgYmFz
ZWQgb24gaW1wbGVtZW50YXRpb24gZmVlZGJhY2sNCg0KSGkgQWxhbiwNCg0KVGhhbmsgeW91IGZv
ciB5b3VyIHJlcGx5LiBJIGhhdmUgdHdvIHBvaW50cyB0byBjbGFyaWZ5LiBQbGVhc2Ugc2VlIHRo
ZW0gaW4gbGluZS4NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206ICJB
bGFuIEZvcmQiIDxhbGFuLmZvcmRAZ21haWwuY29tPG1haWx0bzphbGFuLmZvcmRAZ21haWwuY29t
Pj4NClRvOiAiViBBbmlsIEt1bWFyIiA8YW5pbEBjc2lyNHBpLmluPG1haWx0bzphbmlsQGNzaXI0
cGkuaW4+PmprDQpDYzogIllvc2hpZnVtaSBOaXNoaWRhIiA8bnNkLmlldGZAZ21haWwuY29tPG1h
aWx0bzpuc2QuaWV0ZkBnbWFpbC5jb20+PiwgIm11bHRpcGF0aHRjcCIgPG11bHRpcGF0aHRjcEBp
ZXRmLm9yZzxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnPj4NClNlbnQ6IFRodXJzZGF5LCBG
ZWJydWFyeSA2LCAyMDIwIDI6NDk6MjkgQU0NClN1YmplY3Q6IFJlOiBbbXVsdGlwYXRodGNwXSBS
RkM2ODI0YmlzIGVkaXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrDQpIaSBBbmls
LA0KDQpUaGlzIHdvdWxkIG5vdCBiZSBmb3JiaWRkZW4gaWYgdGhlIG1hcHBpbmcgd2FzIGNhcnJp
ZWQgb24gYSBwdXJlIEFDSyB3aXRoIG5vIGRhdGEuDQpBcyBmYXIgYXMgSSB1bmRlcnN0YW5kLCBk
ZWxpdmVyeSBvZiBEU00gdGhyb3VnaCBwdXJlIEFDSyBpcyBub3QgaW4gdGhlIHNjb3BlIG9mIHRo
ZSBjdXJyZW50IGRyYWZ0LiBJZiB3ZSBpbnRlbmQgdG8gZG8gdGhpcywgd2UgbWF5IG5lZWQgYW4g
YXBwcm9hY2ggc2ltaWxhciB0byB0aGUgb25lIHByb3Bvc2VkIGZvciBkZWxpdmVyeSBvZiBBRERf
QUREUiBvcHRpb24gaW4gcHVyZSBBQ0sgd2l0aCByZWxpYWJpbGl0eSBmZWF0dXJlLiAgU28sIHBh
Y2tpbmcgRFNNIG9uIHB1cmUgQUNLIGRvZXMgbm90IHNlZW0gdG8gYmUgYW4gb3B0aW9uIGF0IHRo
aXMgc3RhZ2UuDQoNCkkgZG8gc2VlIHRoZSBwb2ludCBoZXJlOiBpZiBhIHBhY2tldCBvZiAxMDAw
IGJ5dGVzIGNvbnRhaW5zIDUwMCBieXRlcyBvZiBvbmUgbWFwcGluZyBhbmQgNTAwIGJ5dGVzIG9m
IGFub3RoZXIgbWFwcGluZywgdGhlbiBvbmx5IG9uZSBEU00gd291bGQgYXBwZWFyIG9uIG9uZSBw
YWNrZXQsIGxlYXZpbmcgdGhlIG1hcHBpbmcgZm9yIHRoZSBzZWNvbmQgNTAwIGJ5dGVzIHRvIGJl
IGNhcnJpZWQgc29tZXdoZXJlIGVsc2UgLSB0aGUgb25seSBvcHRpb24gYmVpbmcgYSBwdXJlIEFD
Sy4gQnV0IHRoaXMga2luZCBvZiBzY2VuYXJpbyB3b3VsZCBiZSBleHRyZW1lbHkgcmFyZQ0KWWVz
LCBJIGRvIGFncmVlIHRoYXQgdGhlIHNjZW5hcmlvIHlvdSBtZW50aW9uZWQgYWJvdmUgd291bGQg
YmUgZXh0cmVtZWx5IHJhcmUuIEluIGZhY3QsIEkgd29uZGVyIHdoZXRoZXIgc3VjaCBhIHNpdHVh
dGlvbiAoaS5lLiwgbmVlZCB0byBjb3ZlciB0aGUgYnl0ZXMgaW4gYSBzaW5nbGUgcGFja2V0IHdp
dGggdHdvIGRpZmZlcmVudCBtYXBzKSB3b3VsZCBldmVyIGFyaXNlLiBQcm9iYWJseSB0aGVyZSBt
aWdodCBiZSBzb21lIGNvcm5lciBjYXNlcywgd2hpY2ggSSBkb24ndCBnZXQgaXQgcmlnaHRseSBu
b3cuDQoNCk1vcmUgaW1wb3J0YW50bHksIHRoZSBzY2VuYXJpbyB0aGF0IFlvc2hpIGFuZCBtZSBh
cmUgcmVmZXJyaW5nIHRvIGlzIHRvdGFsbHkgZGlmZmVyZW50OiB0aGUgb25lIEkgaGFkIGdpdmVu
IGFzIHBhcnQgb2YgbXkgY29tbWVudHMgaW4gcmVzcG9uc2UgdG8gdGhlIHByb3Bvc2VkIGNoYW5n
ZSAyLiBJbiB0aGlzIHNjZW5hcmlvLCB3aGljaCB5b3UgY291bGQgc2VlIGluIHRoZSB0cmFpbGlu
ZyBtYWlsLCBkYXRhIHNlZ21lbnQtMSBpcyB0cmFuc21pdHRlZCB3aXRob3V0IGluY2x1ZGluZyBp
dHMgbWFwLCBzb21ldGhpbmcgd2hpY2ggaXMgcGVybWl0dGVkIGluIHRoZSAgbXB0Y3AgZnJhbWV3
b3JrICg2ODI0IGJpcykuIEkgbWFrZSB0aGlzIGluZmVyZW5jZSBmcm9tIHRoZSBiZWxvdyB0ZXh0
IGluIDY4MjQgYmlzOg0KDQoiLi4uZXZlbiBpZiBhIG1hcHBpbmcgZG9lcyBub3QgZXhpc3QgZnJv
bSB0aGUgc3ViZmxvdyBzcGFjZSB0byB0aGUgZGF0YS0gbGV2ZWwgc3BhY2UsIHRoZSBkYXRhIFNI
T1VMRCBzdGlsbCBiZSBBQ0tlZCBhdCB0aGUgc3ViZmxvdyAoaWYgaXQgaXMgaW4td2luZG93KS4g
VGhpcyBkYXRhIGNhbm5vdCwgaG93ZXZlciwgYmUgYWNrbm93bGVkZ2VkIGF0IHRoZSBkYXRhIGxl
dmVsIChTZWN0aW9uIDMuMy4yKSBiZWNhdXNlIGl0cyBkYXRhIHNlcXVlbmNlIG51bWJlcnMgYXJl
IHVua25vd24uIEltcGxlbWVudGF0aW9ucyBNQVkgaG9sZCBvbnRvIHN1Y2ggdW5tYXBwZWQgZGF0
YSBmb3IgYSBzaG9ydCB3aGlsZSBpbiB0aGUgZXhwZWN0YXRpb24gdGhhdCBhIG1hcHBpbmcgd2ls
bCBhcnJpdmUgc2hvcnRseS4iDQoNCk9uZSBvcHRpb24gdGhlIGRhdGEgc2VuZGVyIGhhcyBhdCB0
aGlzIHN0YWdlIGlzIHRvIGluY2x1ZGUgdGhlIG1hcCBmb3IgZGF0YSBpbiBzZWdtZW50LTEsIGlu
IHNlZ21lbnQtMyAocGxlYXNlIHNlZSB0aGUgdHdvLXN1YmZsb3cgZXhhbXBsZSBJIGdhdmUgaW4g
cmVzcG9uc2UgdG8gdGhlIGNoYW5nZSAyIHlvdSBoYWQgcHJvcG9zZWQpLiBCdXQgdGhlIHByb3Bv
c2VkIGNoYW5nZSBkb2VzIG5vdCBwZXJtaXQgdGhpcy4gV2hhdCB3b3VsZCBoYXBwZW4gdG8gIHN1
YmZsb3ctMSBpbiB0aGlzIGNhc2UgPw0KDQpXaXRoIHJlZ2FyZHMsDQoNCkFuaWwNCmFuZCBJIHdv
dWxkIGltYWdpbmUgYW55IGltcGxlbWVudGF0aW9uIHdvdWxkIGp1c3Qgc3BsaXQgaW50byB0d28g
NTAwIGJ5dGUgc2VnbWVudHMgZWFjaCB3aXRoIHRoZSBQU0ggZmxhZyBzZXQuIEkgZG9u4oCZdCB0
aGluayB3ZSBuZWVkIHRvIHNwZWxsIHRoaXMgb3V0IGluIHRoZSBzcGVjIGhvd2V2ZXIuDQoNClJl
Z2FyZHMsDQpBbGFuDQoNCk9uIDUgRmViIDIwMjAsIGF0IDE1OjA5LCBWIEFuaWwgS3VtYXIgPGFu
aWxAY3NpcjRwaS5pbjxtYWlsdG86YW5pbEBjc2lyNHBpLmluPj4gd3JvdGU6DQpIaSBZb3NoaSwN
Cg0KUGxlYXNlIHNlZSBpbiBsaW5lLg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KRnJvbTogIllvc2hpZnVtaSBOaXNoaWRhIiA8bnNkLmlldGZAZ21haWwuY29tPG1haWx0bzpu
c2QuaWV0ZkBnbWFpbC5jb20+Pg0KVG86ICJWIEFuaWwgS3VtYXIiIDxhbmlsQGNzaXI0cGkuaW48
bWFpbHRvOmFuaWxAY3NpcjRwaS5pbj4+DQpDYzogImFsYW4gZm9yZCIgPGFsYW4uZm9yZEBnbWFp
bC5jb208bWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5jb20+PiwgIm11bHRpcGF0aHRjcCIgPG11bHRp
cGF0aHRjcEBpZXRmLm9yZzxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnPj4NClNlbnQ6IFR1
ZXNkYXksIEZlYnJ1YXJ5IDQsIDIwMjAgMTowODo0NSBQTQ0KU3ViamVjdDogUmU6IFttdWx0aXBh
dGh0Y3BdIFJGQzY4MjRiaXMgZWRpdHMgYmFzZWQgb24gaW1wbGVtZW50YXRpb24gZmVlZGJhY2sN
Cg0KSGkgQW5pbCwNCg0KVGhhbmtzIGZvciBwb2ludGluZyBpdCBvdXQuIEkgb3Zlcmxvb2tlZCB0
aGlzIG9uZS4NClRoaXMgbG9va3MgYW4gaW50ZXJlc3RpbmcgcG9pbnQuDQoNCkl0IHNlZW1zIHRv
IG1lIHRoYXQgd2hldGhlciBSU1QgaXMgaGFwcGVuIG9yIG5vdCBkZXBlbmRzIG9uIHRoZSBzaXpl
IG9mIHJlY2VpdmUgd2luZG93IGFjY29yZGluZyB0byB0aGUgdGV4dC4NCklmIHRoZSByZWNlaXZl
IHdpbmRvdyBzaXplIGlzIGJpZyBlbm91Z2ggdG8gYWNjb21tb2RhdGUgc2VnbWVudCAxIGFuZCBz
ZWdtZW50IDMsIHRoZSB0ZXh0ICJJbXBsZW1lbnRhdGlvbnMgTUFZIGhvbGQgb250byBzdWNoIHVu
bWFwcGVkIGRhdGEgZm9yIGEgc2hvcnQgd2hpbGUgaW4gdGhlIGV4cGVjdGF0aW9uIHRoYXQgYSBt
YXBwaW5nIHdpbGwgYXJyaXZlIHNob3J0bHkuICIgY2FuIGJlIGFwcGxpZWQgdG8gdGhlIHNlZ21l
bnQgMS4gQXMgYSByZXN1bHQsIHRoZSBzZWdtZW50IDEgd29uJ3QgYmUgZGlzY2FyZGVkLg0KDQpZ
ZXMuICBTbywgc2VnbWVudCAxIG1heSBiZSBrZXB0IGluIHRoZSBkYXRhIHJlY2VpdmVyJ3MgYnVm
ZmVyIGluIGV4cGVjdGF0aW9uIHRoYXQgaXRzIG1hcHBpbmcgd2lsbCBhcnJpdmUgc2hvcnRseS4g
QW5kIGluIHRoZSBleGFtcGxlIHRoYXQgd2UgYXJlIHJlZmVycmluZyB0bywgdGhlIGRhdGEgc2Vu
ZGVyIHdpbGwgbm90IGJlIGFibGUgdG8gaW5jbHVkZSB0aGUgbWFwIGZvciB0aGUgZGF0YSBpbiBz
ZWdtZW50IDEgaW4gc2VnbWVudCAzIG9yIGFueSBoaWdoZXIgc2VnbWVudC4NCg0KUmVnYXJkcywN
Cg0KQW5pbA0KDQpIb3dldmVyLCB0aGlzIG1pZ2h0IGJlIGNvbnRyYWRpY3Qgd2l0aCB0aGUgbmV3
IHRleHRzIEFsYW4gcHJvcG9zZWQ/IE9yLCBhbSBJIG1pc3Npbmcgc29tZXRoaW5nPw0KDQpUaGFu
a3MsDQotLQ0KWW9zaGkNCg0KDQpPbiBTdW4sIEZlYiAyLCAyMDIwIGF0IDg6NDIgQU0gViBBbmls
IEt1bWFyIDxhbmlsQGNzaXI0cGkuaW48bWFpbHRvOmFuaWxAY3NpcjRwaS5pbj4+IHdyb3RlOg0K
SGkgWW9zaGksDQoNClRoYW5rcyBmb3IgdGhpcyBwb2ludC4gSW4gZmFjdCwgSSBoYWQgaW5pdGlh
bGx5IG5vdCB0aG91Z2h0IG9mIGEgc2NlbmFyaW8sIHdoZXJlIHRoZSBtYXAgaXMgYmVpbmcgZGVs
aXZlcmVkIHRocm91Z2ggYSByZXRyYW5zbWl0dGVkIGRhdGEgcGFja2V0IHdoaWxlIGl0cyBmaXJz
dCB0cmFuc21pc3Npb24gZGlkIG5vdCBpbmNsdWRlIHRoZSBtYXAuIE5vdyBJIGFtIGp1c3Qgc2Vl
aW5nIHRoZSBkb2N1bWVudCAoUkZDIDY4MjQtYmlzKSBpbiB0aGlzIGNvbnRleHQuDQoNCk15IHVu
ZGVyc3RhbmRpbmcgaXMgdGhhdCBpbiBzY2VuYXJpb3MgbGlrZSB3aGF0IEkgZGVzY3JpYmVkIGlu
IG15IHByZXZpb3VzIG1haWwsIFJTVCBpcyBsaWtlbHkgdG8gaGFwcGVuIHdoZXRoZXIgd2UgZXhw
bGljaXRseSBzdGF0ZSBzbyBvciBub3QuIFBsZWFzZSBzZWUgdGhlIHBhcmFncmFwaCBjb250YWlu
aW5nIHRoZSBiZWxvdyB0ZXh0IGluIFJGQyA2ODI0LWJpcy4NCg0KIklmIGEgbWFwcGluZyBmb3Ig
dGhhdCBzdWJmbG93LWxldmVsIHNlcXVlbmNlIHNwYWNlIGRvZXMgbm90IGFycml2ZSB3aXRoaW4g
YSByZWNlaXZlIHdpbmRvdyBvZiBkYXRhLCB0aGF0IHN1YmZsb3cgU0hPVUxEIGJlIHRyZWF0ZWQg
YXMgYnJva2VuLCBjbG9zZWQgd2l0aCBhIFJTVCwgYW5kIGFueSB1bm1hcHBlZCBkYXRhIHNpbGVu
dGx5IGRpc2NhcmRlZC4iDQoNCmlmIHdlIGFzc3VtZSB0aGF0IHRoZSBtYXAgaXMgaW5jbHVkZWQg
d2hpbGUgcmV0cmFuc21pdHRpbmcgdGhlIGRhdGEgKGV2ZW4gdGhvdWdoIHRoZSBmaXJzdCB0cmFu
c21pc3Npb24gZGlkIG5vdCBjb250YWluIHRoZSBtYXAgZm9yIHNvbWUgcmVhc29ucyksICB3ZSBj
b3VsZCBhcmd1ZSB0aGF0IFJTVCBjb3VsZCBiZSBhdm9pZGVkIHByb3ZpZGVkIHRoYXQgdGhlIHJl
dHJhbnNtaXNzaW9uIGlzIHRyaWdnZXJlZCB3aXRoaW4gYSByZWNlaXZlIHdpbmRvdyBvZiBkYXRh
LiBCdXQgdGhlIHF1ZXN0aW9uIGhlcmUgd291bGQgYmUgaG93IGFuZCB3aGVuIHdpbGwgdGhlIHJl
dHJhbnNtaXNzaW9uIHRha2UgcGxhY2UuIEluIHRoaXMgY2FzZSwgdGhlIHN1YmZsb3cgbWF5IG5v
dCBpbml0aWF0ZSB0aGUgcmV0cmFuc21pc3Npb24gb2YgZGF0YSBieSBpdHMgb3duIChpLmUuLCBu
byByZXRyYW5zbWlzc2lvbiBkdWUgdG8gdGhyZWUgZHVwbGljYXRlIEFDS3Mgb3IgUlRPIGV4cGly
eSBhdCBzdWJmbG93IGxldmVsKSBhcyB0aGVyZSBpcyBubyBzZWdtZW50IGxvc3MgYXQgc3ViZmxv
dyBsZXZlbCBzZXF1ZW5jZSBzcGFjZS4gU28gdGhlcmUgY291bGQgYmUgYSBoaWdoIHBvc3NpYmls
aXR5IG9mIFJTVCBoYXBwZW5pbmcgZXZlbiBiZWZvcmUgdGhlIG1hcCBkZWxpdmVyeSB0aHJvdWdo
IHJldHJhbnNtaXNzaW9uLg0KDQpXaXRoIHJlZ2FyZHMsDQoNCkFuaWwNCg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCkZyb206ICJZb3NoaWZ1bWkgTmlzaGlkYSIgPG5zZC5pZXRm
QGdtYWlsLmNvbTxtYWlsdG86bnNkLmlldGZAZ21haWwuY29tPj4NClRvOiAiViBBbmlsIEt1bWFy
IiA8YW5pbEBjc2lyNHBpLmluPG1haWx0bzphbmlsQGNzaXI0cGkuaW4+Pg0KQ2M6ICJhbGFuIGZv
cmQiIDxhbGFuLmZvcmRAZ21haWwuY29tPG1haWx0bzphbGFuLmZvcmRAZ21haWwuY29tPj4sICJt
dWx0aXBhdGh0Y3AiIDxtdWx0aXBhdGh0Y3BAaWV0Zi5vcmc8bWFpbHRvOm11bHRpcGF0aHRjcEBp
ZXRmLm9yZz4+DQpTZW50OiBTYXR1cmRheSwgRmVicnVhcnkgMSwgMjAyMCAzOjM5OjUxIEFNDQpT
dWJqZWN0OiBSZTogW211bHRpcGF0aHRjcF0gUkZDNjgyNGJpcyBlZGl0cyBiYXNlZCBvbiBpbXBs
ZW1lbnRhdGlvbiBmZWVkYmFjaw0KDQpIaSBBbmlsLA0KDQpJIGhhdmUgYSBxdWVzdGlvbiBhYm91
dCB5b3VyIHByb3Bvc2VkIHRleHQuLg0KSSBhbSBhY3R1YWxseSB3b25kZXJpbmcgaWYgd2UgcmVh
bGx5IHdhbnQgdG8gdGVybWluYXRlIGNvbm5lY3Rpb24gaGVyZS4NCg0KVGhlIHBhY2tldHMgd2l0
aG91dCBwcm9wZXIgbWFwcGluZ3Mgd2lsbCBiZSB0cmVhdGVkIGFzIGludmFsaWQgYW5kIHdpbGwg
YmUgZGlzY2FyZGVkLg0KSWYgYW4gaW1wbGVtZW50YXRpb24gZmFpbGVkIHRvIGF0dGFjaCBwcm9w
ZXIgbWFwcGluZyBmb3Igc29tZSByZWFzb25zIChlLi5nLiBvcHRpb24gc3BhY2UpLCBpdCBtaWdo
dCBiZSBhYmxlIHRvIGF0dGFjaCB0aGUgcHJvcGVyIG9uZSB3aGVuIGl0IHJldHJhbnNtaXRzIHRo
ZSBwYWNrZXRzLiBUaGlzIGFsc28gbG9va3Mgb2sgdG8gbWUuDQoNCkkgZG9uJ3QgaGF2ZSBzdHJv
bmcgcHJlZmVyZW5jZSBmb3IgdGhpcy4gQnV0LCBkbyB3ZSBoYXZlIGEgcmVhc29uIHRvIHRlcm1p
bmF0ZSBjb25uZWN0aW9uPw0KDQpUaGFua3MsDQotLQ0KWW9zaGkNCg0KT24gTW9uLCBKYW4gMTMs
IDIwMjAgYXQgMTA6MjggQU0gViBBbmlsIEt1bWFyIDxhbmlsQGNzaXI0cGkuaW48bWFpbHRvOmFu
aWxAY3NpcjRwaS5pbj4+IHdyb3RlOg0KSGksDQoNCkkgaGF2ZSBzb21lIHBvaW50cyByZWxhdGVk
IHRvIHRoZSAgbW9kaWZpY2F0aW9ucyAoQ2hhbmdlIDIpIGJlaW5nIHByb3Bvc2VkIG9uIGRhdGEg
c2VxdWVuY2UgbWFwLiBQbGVhc2Ugc2VlIHRoZW0gaW5saW5lLiBUaG91Z2ggSSBhbSBwdXR0aW5n
IGZvcndhcmQgdGhlIGJlbG93IHBvaW50cywgaWYgdGhlIGNvbnNlbnN1cyBpcyBpbiBmYXZvdXIg
b2YgdGhlIHByb3Bvc2VkIGNoYW5nZSBmb3IgcmVkdWNpbmcgaW1wbGVtZW50YXRpb24gY29tcGxl
eGl0eSwgSSBhbSBhbHNvIE9LIHdpdGggdGhhdCBhcyB3ZWxsLg0KDQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KRnJvbTogImFsYW4gZm9yZCIgPGFsYW4uZm9yZEBnbWFpbC5jb208
bWFpbHRvOmFsYW4uZm9yZEBnbWFpbC4uY29tPj4NClRvOiBtdWx0aXBhdGh0Y3BAaWV0Zi5vcmc8
bWFpbHRvOm11bHRpcGF0aHRjcEBpZXRmLm9yZz4NClNlbnQ6IFRodXJzZGF5LCBKYW51YXJ5IDIs
IDIwMjAgNDoyMTozMiBBTQ0KU3ViamVjdDogW211bHRpcGF0aHRjcF0gUkZDNjgyNGJpcyBlZGl0
cyBiYXNlZCBvbiBpbXBsZW1lbnRhdGlvbiBmZWVkYmFjaw0KDQpIaSBhbGwsDQpXZeKAmWQgbG92
ZSB0byBnZXQgdGhpcyB0byBhIHN0YXRlIG9mIGNvbXBsZXRpb24gYXMgc29vbiBhcyBwb3NzaWJs
ZSwgYW5kIHRvIHRoaXMgZW5kIEkgYW0gc3RhcnRpbmcgYSBuZXcgdGhyZWFkIG9uIHRoaXMgdG9w
aWMuIEluIGRpc2N1c3Npb24gd2l0aCB0aGUgY2hhaXJzLCBpdCBpcyBwb3NzaWJsZSB0byBtYWtl
IHRoZSBkZXNpcmVkIGNoYW5nZXMgaW4gQVVUSDQ4IGFzIGxvbmcgYXMgdGhlcmUgaXMgV0cgY29u
c2Vuc3VzLiBUaGUgZGlzY3Vzc2lvbiBzbyBmYXIgaGFzIGJlZW4gZmFpcmx5IGxpbWl0ZWQgaW4g
dGVybXMgb2YgcGFydGljaXBhdGlvbi4NCg0KSSB3b3VsZCBhc2sgdGhlIGNoYWlycyBwbGVhc2Ug
aWYgaXQgd2FzIHBvc3NpYmxlIHRvIHNwZWNpZnkgYSB0aW1lIGJvdW5kIGZvciB0aGlzIGRpc2N1
c3Npb24gYW5kIGEgZGVmYXVsdCBjb25jbHVzaW9uLg0KDQpSZWdhcmRpbmcgdGhlIGNoYW5nZXMs
IGluIHN1bW1hcnksIHRoZXJlIGFyZSB0d28gYXJlYXMgd2hlcmUgY2hhbmdlcyBoYXZlIGJlZW4g
cmVxdWVzdGVkIGJ5IHRoZSBpbXBsZW1lbnRhdGlvbiBjb21tdW5pdHkuIEFzIHdlIGFyZSB0aGUg
SUVURiB3ZSBvYnZpb3VzbHkgaGF2ZSBzdHJvbmcgZm9jdXMgb24g4oCccnVubmluZyBjb2Rl4oCd
IGFuZCBzbyBlYXNlIG9mIGltcGxlbWVudGluZyBzdGFuZGFyZHMtY29tcGxpYW50IGNvZGUgaXMg
c3Ryb25nbHkgZGVzaXJhYmxlLiBIb3dldmVyLCB3ZSBkbyBub3Qgd2lzaCB0byByZWR1Y2UgZnVu
Y3Rpb25hbGl0eSBhZ3JlZWQgYnkgdGhlIElFVEYgY29tbXVuaXR5IGlmIGl0IGlzIGNvbnNpZGVy
ZWQgYSByZXF1aXJlZCBmZWF0dXJlIGJ5IHRoZSBjb21tdW5pdHkuDQoNCkNoYW5nZSAxDQoNCkNo
YW5nZSB0aGUgc2VudGVuY2UgcmVhZGluZzoNCg0KICAgSWYgQiBoYXMgZGF0YSB0byBzZW5kIGZp
cnN0LCB0aGVuIHRoZSByZWxpYWJsZSBkZWxpdmVyeSBvZiB0aGUgQUNLICsgTVBfQ0FQQUJMRSBj
YW4gYmUgaW5mZXJyZWQgYnkgdGhlIHJlY2VpcHQgb2YgdGhpcyBkYXRhIHdpdGggYW4gTVBUQ1Ag
RGF0YSBTZXF1ZW5jZSBTaWduYWwgKERTUykgb3B0aW9uIChTZWN0aW9uIDMuMykuDQoNClRvOg0K
DQogICBJZiBCIGhhcyBkYXRhIHRvIHNlbmQgZmlyc3QsIHRoZW4gdGhlIHJlbGlhYmxlIGRlbGl2
ZXJ5IG9mIHRoZSBBQ0sgKyBNUF9DQVBBQkxFIGlzIGVuc3VyZWQgYnkgdGhlIHJlY2VpcHQgb2Yg
dGhpcyBkYXRhIHdpdGggYW4gTVBUQ1AgRGF0YSBTZXF1ZW5jZSBTaWduYWwgKERTUykgb3B0aW9u
IChTZWN0aW9uIDMuMykgY29udGFpbmluZyBhIERBVEFfQUNLIGZvciB0aGUgTVBfQ0FQQUJMRSAo
d2hpY2ggaXMgdGhlIGZpcnN0IG9jdGV0IG9mIHRoZSBkYXRhIHNlcXVlbmNlIHNwYWNlKS4NCldo
YXQgdGhpcyBtZWFuczoNCg0KVGhlIGN1cnJlbnQgdGV4dCBpcyBjb25jZXJuZWQgb25seSB3aXRo
IGVuc3VyaW5nIGEgcGF0aCBpcyBNUFRDUCBjYXBhYmxlLCBhbmQgc28gb25seSBjYXJlcyB0aGF0
IERTUyBvcHRpb24gb2NjdXJzIG9uIGEgZGF0YSBwYWNrZXQuIEhvd2V2ZXIsIHRoZSBNUF9DQVBB
QkxFIG9wdGlvbiBpcyBkZWZpbmVkIHRvIG9jY3VweSB0aGUgZmlyc3Qgb2N0ZXQgb2YgZGF0YSBz
ZXF1ZW5jZSBzcGFjZSBhbmQgdGh1cywgaWYgYW5hbG9nb3VzIHRvIFRDUCwgbXVzdCBiZSBhY2tu
b3dsZWRnZWQuID5Gcm9tIGFuIGltcGxlbWVudGF0aW9uIHBvaW50IG9mIHZpZXcgaXQgd291bGQg
bWFrZSBzZW5zZSBub3QgdG8gaGF2ZSB0aGlzIGhhbmdpbmcgYXJvdW5kIGZvcmV2ZXIgYW5kIGlu
c3RlYWQgZGVmaW5lIGl0IGlzIGFja25vd2xlZGdlZCBhdCB0aGUgY29ubmVjdGlvbiBsZXZlbCBh
cyBzb29uIGFzIHJlY2VpdmVkLiBUaGlzIGNoYW5nZSBlbnN1cmVzIHRoZSBmaXJzdCBkYXRhIHBh
Y2tldCBhbHNvIERBVEFfQUNLcyB0aGlzIE1QX0NBUEFCTEUgb2N0ZXQuDQoNCkNoYW5nZSAyDQoN
CkNoYW5nZSB0aGUgc2VudGVuY2UgcmVhZGluZzoNCg0KICAgQSBEYXRhIFNlcXVlbmNlIE1hcHBp
bmcgZG9lcyBub3QgbmVlZCB0byBiZSBpbmNsdWRlZCBpbiBldmVyeSBNUFRDUCBwYWNrZXQsIGFz
IGxvbmcgYXMgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2UgaW4gdGhhdCBwYWNrZXQgaXMgY292
ZXJlZCBieSBhIG1hcHBpbmcga25vd24gYXQgdGhlIHJlY2VpdmVyLg0KDQpUbzoNCg0KICAgVGhl
IG1hcHBpbmcgcHJvdmlkZWQgYnkgYSBEYXRhIFNlcXVlbmNlIE1hcHBpbmcgTVVTVCBhcHBseSB0
byBzb21lIG9yIGFsbCBvZiB0aGUgc3ViZmxvdyBzZXF1ZW5jZSBzcGFjZSBpbiB0aGUgVENQIHNl
Z21lbnQgd2hpY2ggY2FycmllcyB0aGUgb3B0aW9uLiBJdCBkb2VzIG5vdCBuZWVkIHRvIGJlIGlu
Y2x1ZGVkIGluIGV2ZXJ5IE1QVENQIHBhY2tldCwgYXMgbG9uZyBhcyB0aGUgc3ViZmxvdyBzZXF1
ZW5jZSBzcGFjZSBpbiB0aGF0IHBhY2tldCBpcyBjb3ZlcmVkIGJ5IGEgbWFwcGluZyBrbm93biBh
dCB0aGUgcmVjZWl2ZXIuDQoNCldoYXQgdGhpcyBtZWFuczoNCg0KVGhlIGN1cnJlbnQgdGV4dCBk
b2VzIG5vdCBwbGFjZSBhbnkgcmVzdHJpY3Rpb25zIG9uIHdoZXJlIGEgbWFwcGluZyBjb3VsZCBh
cHBlYXIuIEluIHRoZW9yeSBhIHNlbmRlciBjb3VsZCBkZWZpbmUgYSB0aG91c2FuZCBkaWZmZXJl
bnQgbWFwcGluZ3MgdXAgZnJvbnQsIHNlbmQgdGhlbSBhbGwsIGFuZCBleHBlY3QgYSByZWNlaXZl
ciB0byBzdG9yZSB0aGlzIGFuZCByZWFzc2VtYmxlIGRhdGEgYWNjb3JkaW5nIHRvIHRoZXNlIG1h
cHBpbmdzIGFzIGl0IGFycml2ZXMuIEluZGVlZCwgdGhpcyB3YXMgbmV2ZXIgZXhwbGljaXRseSBk
aXNhbGxvd2VkIHNpbmNlIGl0IOKAnG1pZ2h0IGhhdmUgYmVlbiB1c2VmdWzigJ0uIFRoZSBpbXBs
ZW1lbnRhdGlvbiBjb21tdW5pdHksIGhvd2V2ZXIsIGhhcyBleHByZXNzZWQgY29uY2VybnMgb3Zl
ciB0aGUgZGlmZmljdWx0eSBvZiBpbXBsZW1lbnRpbmcgdGhpcyBvcGVuLWVuZGVkbHkuIEhvdyBt
YW55IG1hcHBpbmdzIGlzIGl0IHJlYXNvbmFibGUgdG8gc3RvcmU/IElzIHRoZXJlIGEgRG9TIHJp
c2sgaGVyZT8gSW5zdGVhZCwgaXQgaGFzIGJlZW4gcmVxdWVzdGVkIHRoYXQgdGhlZSBzcGVjaWZp
Y2F0aW9uIHJlc3RyaWN0cyB0aGUgcGxhY2VtZW50IG9mIHRoZSBEU1Mgb3B0aW9uIHRvIGJlaW5n
IHdpdGhpbiB0aGUgc3ViZmxvdyBzZXF1ZW5jZSBzcGFjZSB0byB3aGljaCBpdCBhcHBsaWVzLg0K
DQpCZWxvdyBhcmUgbXkgY29tbWVudHMgb24gdGhpcy4gSSBoYWQgc2hhcmVkIHNvbWUgb2YgdGhl
c2UgcG9pbnRzIGluIGEgcHJldmlvdXMgdGhyZWFkIHRoYXQgeW91IGhhZCBpbml0aWF0ZWQgaW4g
dGhlIHNhbWUgY29udGV4dC4NCg0KVHJhbnNtaXR0aW5nIGxhcmdlIG51bWJlciBvZiBub24tY29u
dGlndW91cyBkYXRhIHNlcXVlbmNlIG1hcHMgY291bGQgYmUgYSBtaXNiZWhhdmlvdXIgKG1hcC1m
bG9vZGluZyksIHRob3VnaCBpdCBpcyBub3QgY2xlYXIgd2hldGhlciB0aGlzIGNhbiBnbyB0byB0
aGUgZXh0ZW50IG9mIGNhdXNpbmcgYSBwb3RlbnRpYWwgRG9TIHRvIHRoZSBkYXRhIHJlY2VpdmVy
LiBTbyBzb21lIHNvcnQgb2YgcmVzdHJpY3Rpb24gb24gdGhpcyBjb3VsZCBiZSB1c2VmdWwuICBP
bmUgYXBwcm9hY2ggY291bGQgYmUgdG8gaW5zaXN0IHRoYXQgdGhlIGRhdGEgc2VuZGVyIHNob3Vs
ZCBlbnN1cmUgdGhhdCB0aGUgbWFwIGJlaW5nIHRyYW5zbWl0dGVkIGlzIGZvciBpbi13aW5kb3cg
ZGF0YSwgYXMgcGVyIHRoZSByZWNlaXZlciBhZHZlcnRpc2VkIHdpbmRvdy4gQSByZWNlaXZlciBz
aG91bGQgYW55aG93IGJlIHdpbGxpbmcgdG8gc3RvcmUgdGhlIG1hcHMgZm9yIGluLXdpbmRvdyBk
YXRhIHRvIGRlYWwgd2l0aCBwYWNrZXQgbG9zcy4gRm9yIGV4YW1wbGUsIHdoZW4gYSB3aW5kb3cg
b2YgZGF0YSBzZWdtZW50cyAoc2F5IDEgdG8gNjQpIGlzIHRyYW5zbWl0dGVkLCBlYWNoIGNhcnJ5
aW5nIGl0cyBjb3JyZXNwb25kaW5nIG1hcCwgYW5kIHNlZ21lbnQtMSBpcyBsb3N0LCB0aGUgbWFw
cyBmb3IgdGhlIHJlbWFpbmluZyA2MyBuZWVkIHRvIGJlIHN0b3JlZCB0aWxsIHRoZSBsb3N0IHNl
Z21lbnQgaXMgcmV0cmFuc21pdHRlZC4gT2YgY291cnNlLCBpbiB0aGlzIGNhc2UgdGhlIG1hcHMg
d2lsbCBiZSBzdG9yZWQgYXQgdGhlIHJlY2VpdmVyIHNpZGUgYWxvbmcgd2l0aCB0aGVpciBjb3Jy
ZXNwb25kaW5nIGRhdGEuIEJ1dCB0aGUgbmVlZCB0byBzdG9yZSBtdWx0aXBsZSBtYXBzIGZvciBp
bi13aW5kb3cgZGF0YSB3b3VsZCBzdGlsbCBiZSB0aGVyZS4NCg0KVGhlIHByb2JsZW0gd2l0aCB0
aGUgcHJvcG9zZWQgY2hhbmdlIChyZXN0cmljdGlvbikgaXMgdGhhdCBhIGRhdGEgc2VuZGVyIG1h
eSBmaW5kIGl0IGRpZmZpY3VsdCwgaW4gY2FzZSBhIG5lZWQgYXJpc2UgdG8gc2xpZ2h0bHkgZGVs
YXkgdGhlIG1hcCBkZWxpdmVyeSBieSBmZXcgc2VnbWVudHMsIGkuZS4sIHNlbmRpbmcgc29tZSBk
YXRhIGZpcnN0IHdpdGhvdXQgbWFwLCBhbmQgdGhlbiBzZW5kIHRoZSBjb3JyZXNwb25kaW5nIG1h
cCBpbiBhIGxhdGVyIHNlZ21lbnQsIGFzIHNob3duIGJlbG93Og0KDQpzdWJmbG93LTE6ICAgICAg
c2VnbWVudC0xICAgICAgICAgICAgICAgICAgIHNlZ21lbnQtMyAgICAgICAgICAgICAgICAgICAg
c2VnbWVudC00ICAgICAgICAgICAgICAgICAgICAgICBzZWdtZW50LTcNCiAgICAgICAgICAgICAg
ICAgICAgICBieXRlczoxLTEwMCAgICAgICAgICAgICAgICAgYnl0ZXM6MjAxLTMwMCAgICAgICAg
ICAgICAgYnl0ZXM6MzAxLTQwMCAgICAgICAgICAgICAgICAgYnl0ZXM6NjAxLTcwMA0KICAgICAg
ICAgICAgICAgICAgICAgIG5vIG1hcCAgICAgICAgICAgICAgICAgICAgICAgIG1hcCBmb3IgMS0x
MDAgICAgICAgICAgICAgIG1hcCBmb3IgMjAxLTQwMCAgICAgICAgICAgICBtYXAgZm9yIDYwMS03
MDANCg0KDQoNCg0KDQpzdWJmbG93LTI6ICAgICAgIHNlZ21lbnQtMiAgICAgICAgICAgICAgICAg
IHNlZ21lbnQtNSAgICAgICAgICAgICAgICAgICAgIHNlZ21lbnQtNiAgICAgICAgICAgICAgICAg
ICAgICAgc2VnbWVudC04DQogICAgICAgICAgICAgICAgICAgICAgIGJ5dGVzOiAxMDEtMjAwICAg
ICAgICAgICBieXRlczo0MDEtNTAwICAgICAgICAgICAgICAgYnl0ZXM6IDUwMS02MDAgICAgICAg
ICAgICAgICAgYnl0ZXM6NzAxLTgwMA0KICAgICAgICAgICAgICAgICAgICAgICBtYXAgZm9yIDEw
MS0yMDAgICAgICAgbWFwIGZvciA0MDEtNjAwICAgICAgICAgICAgbm8gbWFwICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIG1hcCBmb3IgNzAxLTgwMA0KDQoNCkluIHRoZSBhYm92ZSBjYXNlLCBz
ZWdtZW50LTEgZ29lcyB3aXRob3V0IG1hcCBhbmQgaXRzIG1hcCBpcyBpbmNsdWRlZCBsYXRlciBp
biBzZWdtZW50LTMsIHRoZSBuZXh0IGRhdGEgc2VnbWVudCBpbiB0aGUgc2FtZSBzdWJmbG93LiBG
dXJ0aGVyLCAgaW4gdGhlIGFib3ZlIHNjaGVkdWxpbmcgcGF0dGVybiwgdGhlIG1hcCBpbiBzZWdt
ZW50LTMgY2Fubm90IGNvdmVyIHRoZSAgZGF0YSBpbiBzZWdtZW50LTEgYW5kIHNlZ21lbnQtMywg
YXMgc29tZSAgZGF0YSBpbiBiZXR3ZWVuIChzZWdtZW50LTIpIGlzIHRyYW5zbWl0dGVkIHRocm91
Z2ggYW5vdGhlciBzdWJmbG93LiAgV2l0aCB0aGUgcHJvcG9zZWQgY2hhbmdlLCB0aGUgbWFwIGlu
IHNlZ21lbnQtMyB3aWxsIGJlY29tZSBpbnZhbGlkIGFuZCB0aGlzIHdpbGwgZXZlbnR1YWxseSBi
cmVhayBzdWJmbG93LTEsIHRob3VnaCB0aGlzIGNvdWxkIGJlIGEgY29ybmVyIGNhc2UuDQoNClRo
ZSBxdWVzdGlvbiBhdCB0aGlzIHN0YWdlIGlzIHdoeSB3b3VsZCBzZWdtZW50LTEgYmUgdHJhbnNt
aXR0ZWQgd2l0aG91dCBpdHMgbWFwLiBJbiB0aGUgY2FzZSBvZiBiaWRpcmVjdGlvbmFsIGRhdGEg
dHJhbnNmZXIsIHRoZXJlIGNvdWxkIGJlIGEgbmVlZCB0byBwYWNrIGJvdGggdGltZXN0YW1wIGFu
ZCBTQUNLICBvcHRpb25zIGluIGEgZGF0YSBzZWdtZW50LCBpLmUuLCBwaWdneWJhY2tpbmcgb2Yg
IFNBQ0sgd2l0aCBkYXRhLiBJZiB3ZSBjb25zaWRlciB0aGF0IHRpbWVzdGFtcCB0YWtlcyAxMiBi
eXRlcyBhbmQgU0FDSywgZXZlbiB3aXRoIHNpbmdsZSBibG9jaywgIHRha2VzIGFub3RoZXIgMTAg
Ynl0ZXMsIHRoZSByZW1haW5pbmcgMTggYnl0ZXMgb3B0aW9uIHNwYWNlIGlzIG5vdCBhZGVxdWF0
ZSB0byBjYXJyeSBkYXRhIHNlcXVlbmNlIHNpZ25hbCB3aXRoIG1hcCwgZXNwZWNpYWxseSB3aGVu
IERTTiBpcyA2NCBiaXQgbG9uZy4gU28gdGhlIGRlbGl2ZXJ5IG9mIGVpdGhlciBvZiB0aGUgdHdv
IChTQUNLIG9yIG1hcCkgd291bGQgYmUgZGVsYXllZC4NCg0KQXMgZmFyIGFzIEkgdW5kZXJzdGFu
ZCwgUkZDIDIwMTggKFRDUCBTZWxlY3RpdmUgQWNrbm93bGVkZ2VtZW50IE9wdGlvbnMpIGltcGxp
ZXMgdGhhdCBTQUNLIHNob3VsZCBub3QgYmUgZGVsYXllZC4gSXQgc3RhdGVzICJJZiBzZW50IGF0
IGFsbCwgU0FDSyBvcHRpb25zIFNIT1VMRCBiZSBpbmNsdWRlZCBpbiBhbGwgQUNLcyB3aGljaCBk
byBub3QgQUNLIHRoZSBoaWdoZXN0IHNlcXVlbmNlIG51bWJlciBpbiB0aGUgZGF0YSByZWNlaXZl
cidzIHF1ZXVlIi4uIEl0IGFsc28gc2F5cyAiSWYgZGF0YSByZWNlaXZlciBnZW5lcmF0ZXMgU0FD
SyBvcHRpb25zIHVuZGVyIGFueSBjaXJjdW1zdGFuY2UsIGl0IFNIT1VMRCBnZW5lcmF0ZSB0aGVt
IHVuZGVyIGFsbCBwZXJtaXR0ZWQgY2lyY3Vtc3RhbmNlcyIuICAgU28sIGFzIHBhcnQgb2YgbWVl
dGluZyB0aGUgUkZDIDIwMTggcmVxdWlyZW1lbnRzLCBpZiB0aGUgY29tYmluYXRpb24gb2YgU0FD
SyBhbmQgdGltZXN0YW1wIGlzIGdpdmVuIHByZWZlcmVuY2Ugb3ZlciBEU1MsIGRhdGEgc2VnbWVu
dHMgY291bGQgYmUgdHJhbnNtaXR0ZWQgd2l0aG91dCB0aGVpciBtYXAuDQoNCkFub3RoZXIgY2Fz
ZSBvZiBkZWxheWluZyBtYXAgY291bGQgYXJpc2UgaWYgdGhlIGRhdGEgc2VuZGVyIHByZWZlcnMg
dG8gc2VuZCBBRERfQUREUiBvcHRpb24sIGluc3RlYWQgb2YgbWFwLCBpbiBhIGRhdGEgc2VnbWVu
dC4gSXQgaXMgbmljZSB0aGF0IEFERF9BRERSIG9wdGlvbiBjYW4gYmUgZGVsaXZlcmVkIHJlbGlh
Ymx5IGluIGEgcHVyZSBBQ0ssIGJ1dCBJIHRoaW5rIHRoaXMgaXMgbm90IHRoZSBjYXNlIHdpdGgg
RFNTIGF0IHByZXNlbnQuDQoNCklmIHdlIGFkb3B0IHRoZSBwcm9wb3NlZCBjaGFuZ2UsIEkgdGhp
bmsgaXQgbWlnaHQgYWxzbyBiZSBoZWxwZnVsIHRvIHNwZWxsIG91dCBob3cgdGhlIHJlY2VpdmVy
IGlzIHN1cHBvc2VkIHRvIGJlaGF2ZSwgaWYgaXQgZ2V0cyBtYXBzIG5vdCBtZWV0aW5nIHRoZSBN
VVNUIGNvbmRpdGlvbiBpbiB0aGUgcHJvcG9zZWQgY2hhbmdlLiAgRm9yIGV4YW1wbGUgdGVybWlu
YXRpb24gb2YgdGhlIHN1YmZsb3cgd2l0aCBNUF9UQ1BSU1Qgb3B0aW9uIChzZWN0aW9uIDMuLjYg
aW4gUkZDIDY4MjQtYmlzKSB3aXRoIGFwcHJvcHJpYXRlIHJlYXNvbiBjb2RlIGFuZCBUIGZsYWcg
dmFsdWUgdG8gaW50aW1hdGUgdGhlIGRhdGEgc2VuZGVyIHRoZSBjYXVzZSBmb3Igc3ViZmxvdyB0
ZXJtaW5hdGlvbi4NCg0KV2l0aCByZWdhcmRzLA0KDQpBbmlsDQpQbGVhc2UgY2FuIG1lbWJlcnMg
b2YgdGhlIFdHIGV4cHJlc3Mgd2hldGhlciB0aGV5IGFyZSBoYXBweSB3aXRoIHRoZXNlIGNoYW5n
ZXMsIG9yIGNvbmNlcm5lZC4NCg0KQmVzdCByZWdhcmRzLA0KQWxhbg0KDQoNCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptdWx0aXBhdGh0Y3AgbWFpbGlu
ZyBsaXN0DQptdWx0aXBhdGh0Y3BAaWV0Zi5vcmc8bWFpbHRvOm11bHRpcGF0aHRjcEBpZXRmLi5v
cmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRpcGF0aHRjcA0K
DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm11
bHRpcGF0aHRjcCBtYWlsaW5nIGxpc3QNCm11bHRpcGF0aHRjcEBpZXRmLm9yZzxtYWlsdG86bXVs
dGlwYXRodGNwQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9tdWx0aXBhdGh0Y3ANCg0KDQoNCg0KDQoNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OkhlbHZldGljYTsNCglwYW5vc2UtMToyIDExIDYgNCAyIDIgMiAyIDIg
NDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OldpbmdkaW5nczsNCglwYW5vc2UtMTo1IDAg
MCAwIDAgMCAwIDAgMCAwO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseToiU2Vnb2UgVUkiOw0KCXBhbm9zZS0xOjIgMTEgNSAyIDQgMiA0
IDIgMiAzO30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9y
bWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0
Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
Y29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bh
bi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29MaXN0UGFyYWdyYXBo
LCBsaS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFncmFwaA0KCXttc28tc3R5bGUt
cHJpb3JpdHk6MzQ7DQoJbWFyZ2luLXRvcDowY207DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltYXJn
aW4tYm90dG9tOjBjbTsNCgltYXJnaW4tbGVmdDozNi4wcHQ7DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28t
c3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2lu
LXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDow
Y207DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJp
Zjt9DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsN
Cglmb250LWZhbWlseToiQXJpYWwiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6
MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCglt
YXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7
cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAqLw0KQGxpc3QgbDANCgl7
bXNvLWxpc3QtaWQ6MjAzOTk2NjI5ODsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlz
dC10ZW1wbGF0ZS1pZHM6LTEzMDc2OTY1MCAxMzY2NzIxNjIwIDEzNDgwNzU1NSAxMzQ4MDc1NTcg
MTM0ODA3NTUzIDEzNDgwNzU1NSAxMzQ4MDc1NTcgMTM0ODA3NTUzIDEzNDgwNzU1NSAxMzQ4MDc1
NTc7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1zdGFydC1hdDowOw0KCW1zby1sZXZl
bC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDotOw0KCW1zby1sZXZlbC10
YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWlu
ZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OiJBcmlhbCIsc2Fucy1zZXJpZjsNCgltc28tZmFy
ZWFzdC1mb250LWZhbWlseTpDYWxpYnJpO30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFi
LXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVs
Mw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674Kn
Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246
bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpA
bGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1s
ZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVt
YmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpT
eW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1z
dG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNw0KCXtt
c28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDps
ZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0
Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3
Ijt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZh
bWlseTpXaW5nZGluZ3M7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KdWwNCgl7bWFyZ2lu
LWJvdHRvbTowY207fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRp
Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0Pjwv
eG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tR0IiIGxpbms9ImJsdWUi
IHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVMiPlNvIGNvbWluZyBiYWNrIHRvIEFuaWzigJlzIChvcmlnaW5hbCkgcXVlc3Rpb24u
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InZlcnRp
Y2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InZlcnRpY2FsLWFs
aWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+QSBwYWNrZXQgd2l0aCB0aW1l
c3RhbXAgYW5kIFNBQ0sgb3B0aW9ucyBsaWtlbHkgd29u4oCZdCBoYXZlIHJvb20gZm9yIHRoZSBE
U1Mgb3B0aW9uLCB0aGVyZWZvcmUgdGhlIERTUyBtYXBwaW5nIHdvdWxkIGJlIGRlbGF5ZWQuIFRo
aXMNCiBtYXkgbWVhbiB0aGUgdHJhbnNtaXR0ZWQgc2VnbWVudCBpcyBub3QgY292ZXJlZCBieSBh
IERTUyBtYXAuIFRoaXMgd291bGQgZmFpbCB0aGUgTVVTVCBpbiBDaGFuZ2UgMiB3aGljaCAoSSB0
aGluaykgbWVhbnMgdGhlIHN1YmZsb3cgaXMgY2xvc2VkIGltbWVkaWF0ZWx5LjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpi
YXNlbGluZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMt
c2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGlu
ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlNvbWUgb3B0aW9uczo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8dWwgc3R5bGU9Im1hcmdpbi10b3A6MGNtIiB0eXBlPSJkaXNjIj4NCjxsaSBjbGFz
cz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjBjbTttc28tbGlzdDpsMCBs
ZXZlbDEgbGZvMTt2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+DQo8c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpF
Ti1VUyI+SXTigJlzIGEgcmFyZSBjYXNlIHRoYXQgd2UgZG9u4oCZdCBuZWVkIHRvIHdvcnJ5IGFi
b3V0Lg0KPG86cD48L286cD48L3NwYW4+PC9saT48bGkgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgi
IHN0eWxlPSJtYXJnaW4tbGVmdDowY207bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzE7dmVydGljYWwt
YWxpZ246YmFzZWxpbmUiPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPk1ha2UgQ2hhbmdlIDIg
YSBTSE9VTEQgcmF0aGVyIHRoYW4gYSBNVVNUPG86cD48L286cD48L3NwYW4+PC9saT48bGkgY2xh
c3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDowY207bXNvLWxpc3Q6bDAg
bGV2ZWwxIGxmbzE7dmVydGljYWwtYWxpZ246YmFzZWxpbmUiPg0KPHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPkV4dGVuZCBDaGFuZ2UgMiBzbyBpdCBzYXlzIHNvbWV0aGluZyBsaWtlOg0KPC9zcGFu
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPlRoZSBtYXBwaW5nIHByb3ZpZGVkIGJ5IGEgRGF0
YSBTZXF1ZW5jZSBNYXBwaW5nIE1VU1QgYXBwbHkgdG8gc29tZSBvciBhbGwgb2YgdGhlIHN1YmZs
b3cgc2VxdWVuY2Ugc3BhY2UgaW4gdGhlIFRDUCBzZWdtZW50IHdoaWNoIGNhcnJpZXMgdGhlIG9w
dGlvbiBbJiM0MzsgbmV3IHRleHRdIG9yIGJlIGNvdmVyZWQgYnkNCiB0aGUgbmV4dCBzZWdtZW50
LiZuYnNwOyBPciDigJx3aXRoaW4gdGhlIG5leHQgZmV3IHNlZ21lbnRz4oCdPC9zcGFuPjxzcGFu
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJl
YXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L2xpPjxsaSBjbGFzcz0iTXNv
TGlzdFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjBjbTttc28tbGlzdDpsMCBsZXZlbDEg
bGZvMTt2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+DQo8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij4/PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L2xp
PjwvdWw+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idmVydGljYWwtYWxpZ246YmFzZWxp
bmUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idmVydGljYWwtYWxpZ246YmFzZWxpbmUiPjxz
cGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1m
YXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5Gb3IgYW55IG9mIHRoZXNlLCBpdCB3b3VsZCBiZSB3b3J0
aHdoaWxlIGFkZGluZyBhbiBleHBsYW5hdG9yeSBub3RlIHRvIENoYW5nZSAyLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpi
YXNlbGluZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMt
c2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGlu
ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkl0IHdvdWxkIGJlIHJlYWxseSBnb29kIGlmIHdl
IGNvdWxkIGNvbmNsdWRlIG9uIHRoaXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9InZlcnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5n
dWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9InZlcnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpF
Ti1VUyI+UGVyc29uYWxseSBJ4oCZZCBsaWtlIHNvbWV0aGluZyB0aGF0IHJlZmxlY3RzIHRoZSBj
b25zZW5zdXMgaW1wbGljaXQgaW4gdGhlIGltcGxlbWVudGF0aW9ucywgYnV0IHdpdGhvdXQgYW55
dGhpbmcgb3RoZXIgdGhhbiByYXJlIGNvcm5lcg0KIGNhc2VzLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPlRoYW5rczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPnBoaWw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0idmVydGljYWwtYWxpZ246YmFzZWxpbmUiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6Ny4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
N0Y3RjdGIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtt
c28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAx
LjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PjxzcGFuIGxhbmc9IkVOLVVTIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiBt
dWx0aXBhdGh0Y3AgJmx0O211bHRpcGF0aHRjcC1ib3VuY2VzQGlldGYub3JnJmd0Ow0KPGI+T24g
QmVoYWxmIE9mIDwvYj5WIEFuaWwgS3VtYXI8YnI+DQo8Yj5TZW50OjwvYj4gMDYgRmVicnVhcnkg
MjAyMCAxODowNzxicj4NCjxiPlRvOjwvYj4gQWxhbiBGb3JkICZsdDthbGFuLmZvcmRAZ21haWwu
Y29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gbXVsdGlwYXRodGNwICZsdDttdWx0aXBhdGh0Y3BAaWV0
Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbbXVsdGlwYXRodGNwXSBSRkM2ODI0
YmlzIGVkaXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+SGkgQWxhbiw8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPlRoYW5rIHlvdSBmb3IgeW91ciByZXBseS4gSSBoYXZlIHR3byBwb2ludHMgdG8gY2xhcmlm
eS4gUGxlYXNlIHNlZSB0aGVtIGluIGxpbmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4
dC1hbGlnbjpjZW50ZXIiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmIj4NCjxociBzaXplPSIyIiB3aWR0aD0iMTAwJSIgYWxpZ249ImNlbnRlciIg
aWQ9Inp3Y2hyIj4NCjwvc3Bhbj48L2Rpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgIzEwMTBGRiAxLjVwdDtwYWRkaW5nOjBjbSAwY20g
MGNtIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0
b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6YmxhY2siPkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij4mcXVvdDtBbGFuIEZvcmQmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzphbGFuLmZvcmRAZ21h
aWwuY29tIj5hbGFuLmZvcmRAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5UbzogPC9iPiZxdW90
O1YgQW5pbCBLdW1hciZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaWxAY3NpcjRwaS5pbiI+
YW5pbEBjc2lyNHBpLmluPC9hPiZndDtqayZuYnNwOzxicj4NCjxiPkNjOiA8L2I+JnF1b3Q7WW9z
aGlmdW1pIE5pc2hpZGEmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpuc2QuaWV0ZkBnbWFpbC5j
b20iPm5zZC5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7LCAmcXVvdDttdWx0aXBhdGh0Y3AmcXVvdDsg
Jmx0OzxhIGhyZWY9Im1haWx0bzptdWx0aXBhdGh0Y3BAaWV0Zi5vcmciPm11bHRpcGF0aHRjcEBp
ZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U2VudDogPC9iPlRodXJzZGF5LCBGZWJydWFyeSA2LCAy
MDIwIDI6NDk6MjkgQU08YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IFttdWx0aXBhdGh0Y3BdIFJG
QzY4MjRiaXMgZWRpdHMgYmFzZWQgb24gaW1wbGVtZW50YXRpb24gZmVlZGJhY2s8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgIzEwMTBGRiAxLjVwdDtwYWRkaW5n
OjBjbSAwY20gMGNtIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2siPkhpIEFuaWwsPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRp
Y2EmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+VGhpcyB3b3VsZCBub3QgYmUgZm9yYmlk
ZGVuIGlmIHRoZSBtYXBwaW5nIHdhcyBjYXJyaWVkIG9uIGEgcHVyZSBBQ0sgd2l0aCBubyBkYXRh
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmIj5BcyBmYXIgYXMgSSB1bmRlcnN0YW5kLCBkZWxpdmVyeSBvZiBEU00g
dGhyb3VnaCBwdXJlIEFDSyBpcyBub3QgaW4gdGhlIHNjb3BlIG9mIHRoZSBjdXJyZW50IGRyYWZ0
LiBJZiB3ZSBpbnRlbmQgdG8gZG8gdGhpcywgd2UgbWF5IG5lZWQgYW4gYXBwcm9hY2ggc2ltaWxh
ciB0byB0aGUgb25lIHByb3Bvc2VkIGZvciBkZWxpdmVyeSBvZg0KIEFERF9BRERSIG9wdGlvbiBp
biBwdXJlIEFDSyB3aXRoIHJlbGlhYmlsaXR5IGZlYXR1cmUuICZuYnNwO1NvLCBwYWNraW5nIERT
TSBvbiBwdXJlIEFDSyBkb2VzIG5vdCBzZWVtIHRvIGJlIGFuIG9wdGlvbiBhdCB0aGlzIHN0YWdl
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICMxMDEwRkYgMS41cHQ7cGFkZGluZzowY20gMGNtIDBj
bSA0LjBwdDttYXJnaW4tbGVmdDozLjc1cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9t
OjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkkgZG8g
c2VlIHRoZSBwb2ludCBoZXJlOiBpZiBhIHBhY2tldCBvZiAxMDAwIGJ5dGVzIGNvbnRhaW5zIDUw
MCBieXRlcyBvZiBvbmUgbWFwcGluZyBhbmQgNTAwIGJ5dGVzIG9mIGFub3RoZXIgbWFwcGluZywg
dGhlbiBvbmx5IG9uZSBEU00gd291bGQgYXBwZWFyIG9uIG9uZSBwYWNrZXQsDQogbGVhdmluZyB0
aGUgbWFwcGluZyBmb3IgdGhlIHNlY29uZCA1MDAgYnl0ZXMgdG8gYmUgY2FycmllZCBzb21ld2hl
cmUgZWxzZSAtIHRoZSBvbmx5IG9wdGlvbiBiZWluZyBhIHB1cmUgQUNLLiBCdXQgdGhpcyBraW5k
IG9mIHNjZW5hcmlvIHdvdWxkIGJlIGV4dHJlbWVseSByYXJlPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPlllcywg
SSBkbyBhZ3JlZSB0aGF0IHRoZSBzY2VuYXJpbyB5b3UgbWVudGlvbmVkIGFib3ZlIHdvdWxkIGJl
IGV4dHJlbWVseSByYXJlLiBJbiBmYWN0LCBJIHdvbmRlciB3aGV0aGVyIHN1Y2ggYSBzaXR1YXRp
b24gKGkuZS4sIG5lZWQgdG8gY292ZXIgdGhlIGJ5dGVzIGluIGEgc2luZ2xlIHBhY2tldCB3aXRo
IHR3byBkaWZmZXJlbnQNCiBtYXBzKSB3b3VsZCBldmVyIGFyaXNlLiBQcm9iYWJseSB0aGVyZSBt
aWdodCBiZSBzb21lIGNvcm5lciBjYXNlcywgd2hpY2ggSSBkb24ndCBnZXQgaXQgcmlnaHRseSBu
b3cuJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmIj5Nb3JlIGltcG9ydGFudGx5LCB0aGUgc2NlbmFyaW8gdGhhdCBZb3No
aSBhbmQgbWUgYXJlIHJlZmVycmluZyB0byBpcyB0b3RhbGx5IGRpZmZlcmVudDogdGhlIG9uZSBJ
IGhhZCBnaXZlbiBhcyBwYXJ0IG9mIG15IGNvbW1lbnRzIGluIHJlc3BvbnNlIHRvIHRoZSBwcm9w
b3NlZCBjaGFuZ2UgMi4gSW4gdGhpcyBzY2VuYXJpbywgd2hpY2gNCiB5b3UgY291bGQgc2VlIGlu
IHRoZSB0cmFpbGluZyBtYWlsLCBkYXRhIHNlZ21lbnQtMSBpcyB0cmFuc21pdHRlZCB3aXRob3V0
IGluY2x1ZGluZyBpdHMgbWFwLCBzb21ldGhpbmcgd2hpY2ggaXMgcGVybWl0dGVkIGluIHRoZSAm
bmJzcDttcHRjcCBmcmFtZXdvcmsgKDY4MjQgYmlzKS4gSSBtYWtlIHRoaXMgaW5mZXJlbmNlIGZy
b20gdGhlIGJlbG93IHRleHQgaW4gNjgyNCBiaXM6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4mcXVvdDsuLi5ldmVuIGlmIGEg
bWFwcGluZyBkb2VzIG5vdCBleGlzdCBmcm9tIHRoZSBzdWJmbG93IHNwYWNlIHRvIHRoZSBkYXRh
LSBsZXZlbCBzcGFjZSwgdGhlIGRhdGEgU0hPVUxEIHN0aWxsIGJlIEFDS2VkIGF0IHRoZSBzdWJm
bG93IChpZiBpdCBpcyBpbi13aW5kb3cpLiBUaGlzIGRhdGEgY2Fubm90LCBob3dldmVyLCBiZSBh
Y2tub3dsZWRnZWQNCiBhdCB0aGUgZGF0YSBsZXZlbCAoU2VjdGlvbiAzLjMuMikgYmVjYXVzZSBp
dHMgZGF0YSBzZXF1ZW5jZSBudW1iZXJzIGFyZSB1bmtub3duLiBJbXBsZW1lbnRhdGlvbnMgTUFZ
IGhvbGQgb250byBzdWNoIHVubWFwcGVkIGRhdGEgZm9yIGEgc2hvcnQgd2hpbGUgaW4gdGhlIGV4
cGVjdGF0aW9uIHRoYXQgYSBtYXBwaW5nIHdpbGwgYXJyaXZlIHNob3J0bHkuJnF1b3Q7DQo8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPk9uZSBvcHRpb24gdGhlIGRhdGEgc2VuZGVyIGhhcyBhdCB0aGlzIHN0YWdlIGlzIHRvIGlu
Y2x1ZGUgdGhlIG1hcCBmb3IgZGF0YSBpbiBzZWdtZW50LTEsIGluIHNlZ21lbnQtMyAocGxlYXNl
IHNlZSB0aGUgdHdvLXN1YmZsb3cgZXhhbXBsZSBJIGdhdmUgaW4gcmVzcG9uc2UgdG8gdGhlIGNo
YW5nZSAyIHlvdSBoYWQgcHJvcG9zZWQpLg0KIEJ1dCB0aGUgcHJvcG9zZWQgY2hhbmdlIGRvZXMg
bm90IHBlcm1pdCB0aGlzLiBXaGF0IHdvdWxkIGhhcHBlbiB0byAmbmJzcDtzdWJmbG93LTEgaW4g
dGhpcyBjYXNlID88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFs
JnF1b3Q7LHNhbnMtc2VyaWYiPldpdGggcmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkFuaWwgJm5ic3A7ICZuYnNw
OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICMxMDEwRkYgMS41cHQ7cGFkZGluZzowY20gMGNtIDBj
bSA0LjBwdDttYXJnaW4tbGVmdDozLjc1cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9t
OjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+YW5kIEkgd291bGQgaW1hZ2luZSBhbnkgaW1wbGVtZW50YXRpb24gd291bGQg
anVzdCBzcGxpdCBpbnRvIHR3byA1MDAgYnl0ZSBzZWdtZW50cyBlYWNoIHdpdGggdGhlIFBTSCBm
bGFnIHNldC4gSSBkb27igJl0IHRoaW5rIHdlIG5lZWQgdG8gc3BlbGwgdGhpcyBvdXQgaW4gdGhl
DQogc3BlYyBob3dldmVyLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRp
Y2EmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjpibGFjayI+QWxhbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9w
OjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGlj
YSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5PbiA1IEZlYiAyMDIwLCBhdCAxNTowOSwg
ViBBbmlsIEt1bWFyICZsdDs8YSBocmVmPSJtYWlsdG86YW5pbEBjc2lyNHBpLmluIiB0YXJnZXQ9
Il9ibGFuayI+YW5pbEBjc2lyNHBpLmluPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjpibGFjayI+SGkgWW9zaGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjpibGFjayI+UGxlYXNlIHNlZSBpbiBsaW5lLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpi
bGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFs
IiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6YmxhY2siPg0KPGhyIHNpemU9IjIiIHdpZHRoPSIxMDAlIiBhbGlnbj0iY2VudGVyIiBp
ZD0iendjaHIiPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2siPiZxdW90O1lvc2hpZnVtaSBOaXNoaWRhJnF1b3Q7ICZsdDs8YSBocmVm
PSJtYWlsdG86bnNkLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+bnNkLmlldGZAZ21h
aWwuY29tPC9hPiZndDs8YnI+DQo8Yj5UbzogPC9iPiZxdW90O1YgQW5pbCBLdW1hciZxdW90OyAm
bHQ7PGEgaHJlZj0ibWFpbHRvOmFuaWxAY3NpcjRwaS5pbiIgdGFyZ2V0PSJfYmxhbmsiPmFuaWxA
Y3NpcjRwaS5pbjwvYT4mZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVvdDthbGFuIGZvcmQmcXVvdDsg
Jmx0OzxhIGhyZWY9Im1haWx0bzphbGFuLmZvcmRAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+
YWxhbi5mb3JkQGdtYWlsLmNvbTwvYT4mZ3Q7LCAmcXVvdDttdWx0aXBhdGh0Y3AmcXVvdDsgJmx0
OzxhIGhyZWY9Im1haWx0bzptdWx0aXBhdGh0Y3BAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5t
dWx0aXBhdGh0Y3BAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxiPlNlbnQ6IDwvYj5UdWVzZGF5LCBG
ZWJydWFyeSA0LCAyMDIwIDE6MDg6NDUgUE08YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IFttdWx0
aXBhdGh0Y3BdIFJGQzY4MjRiaXMgZWRpdHMgYmFzZWQgb24gaW1wbGVtZW50YXRpb24gZmVlZGJh
Y2s8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjpibGFjayI+SGkgQW5pbCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5UaGFua3MgZm9yIHBvaW50aW5nIGl0IG91dC4gSSBv
dmVybG9va2VkIHRoaXMgb25lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPlRoaXMgbG9v
a3MgYW4gaW50ZXJlc3RpbmcgcG9pbnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjpibGFjayI+SXQgc2VlbXMgdG8gbWUgdGhhdCB3aGV0aGVyIFJTVCBpcyBoYXBw
ZW4gb3Igbm90IGRlcGVuZHMgb24gdGhlIHNpemUgb2YgcmVjZWl2ZSB3aW5kb3cgYWNjb3JkaW5n
IHRvIHRoZSB0ZXh0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPklmIHRoZSByZWNlaXZl
IHdpbmRvdyBzaXplIGlzIGJpZyBlbm91Z2ggdG8gYWNjb21tb2RhdGUmbmJzcDtzZWdtZW50IDEg
YW5kIHNlZ21lbnQgMywgdGhlIHRleHQgJnF1b3Q7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
YmxhY2siPkltcGxlbWVudGF0aW9ucw0KIE1BWSBob2xkIG9udG8gc3VjaCB1bm1hcHBlZCBkYXRh
IGZvciBhIHNob3J0IHdoaWxlIGluJm5ic3A7dGhlIGV4cGVjdGF0aW9uIHRoYXQgYSBtYXBwaW5n
IHdpbGwgYXJyaXZlIHNob3J0bHkuICZxdW90OyZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOmJsYWNrIj5jYW4gYmUgYXBwbGllZCB0byB0aGUgc2VnbWVudCAxLiBBcyBhIHJlc3VsdCwg
dGhlIHNlZ21lbnQgMSB3b24ndCBiZQ0KIGRpc2NhcmRlZC4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48ZW0+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+WWVzLiAmbmJzcDtTbywgc2Vn
bWVudCAxIG1heSBiZSBrZXB0IGluIHRoZSBkYXRhIHJlY2VpdmVyJ3MgYnVmZmVyIGluIGV4cGVj
dGF0aW9uIHRoYXQgaXRzIG1hcHBpbmcgd2lsbCBhcnJpdmUgc2hvcnRseS4gQW5kIGluIHRoZSBl
eGFtcGxlIHRoYXQgd2UgYXJlIHJlZmVycmluZyB0bywNCiB0aGUgZGF0YSBzZW5kZXIgd2lsbCBu
b3QgYmUgYWJsZSB0byBpbmNsdWRlIHRoZSBtYXAgZm9yIHRoZSBkYXRhIGluIHNlZ21lbnQgMSBp
biBzZWdtZW50IDMgb3IgYW55IGhpZ2hlciBzZWdtZW50Ljwvc3Bhbj48L2VtPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxlbT48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj5SZWdhcmRzLDwvc3Bhbj48L2VtPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxlbT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij5BbmlsPC9zcGFuPjwvZW0+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+SG93ZXZlciwgdGhpcyBtaWdo
dCBiZSBjb250cmFkaWN0IHdpdGggdGhlIG5ldyB0ZXh0cyBBbGFuIHByb3Bvc2VkPyBPciwgYW0g
SSBtaXNzaW5nIHNvbWV0aGluZz88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj5UaGFua3MsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+LS08bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5Zb3NoaTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6YmxhY2siPk9uIFN1biwgRmViIDIsIDIwMjAgYXQgODo0MiBBTSBWIEFuaWwgS3VtYXIgJmx0
OzxhIGhyZWY9Im1haWx0bzphbmlsQGNzaXI0cGkuaW4iIHRhcmdldD0iX2JsYW5rIj5hbmlsQGNz
aXI0cGkuaW48L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEu
MHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJp
Z2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkhpIFlvc2hpLDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPlRoYW5rcyBmb3IgdGhpcyBw
b2ludC4gSW4gZmFjdCwgSSBoYWQgaW5pdGlhbGx5IG5vdCB0aG91Z2h0IG9mIGEgc2NlbmFyaW8s
IHdoZXJlIHRoZSBtYXAgaXMgYmVpbmcgZGVsaXZlcmVkIHRocm91Z2ggYSByZXRyYW5zbWl0dGVk
IGRhdGEgcGFja2V0IHdoaWxlIGl0cyBmaXJzdCB0cmFuc21pc3Npb24NCiBkaWQgbm90IGluY2x1
ZGUgdGhlIG1hcC4gTm93IEkgYW0ganVzdCBzZWVpbmcgdGhlIGRvY3VtZW50IChSRkMgNjgyNC1i
aXMpIGluIHRoaXMgY29udGV4dC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj5NeSB1bmRlcnN0YW5kaW5nIGlzIHRoYXQgaW4gc2NlbmFyaW9zIGxpa2Ug
d2hhdCBJIGRlc2NyaWJlZCBpbiBteSBwcmV2aW91cyBtYWlsLCBSU1QgaXMgbGlrZWx5IHRvIGhh
cHBlbiB3aGV0aGVyIHdlIGV4cGxpY2l0bHkgc3RhdGUgc28gb3Igbm90LiBQbGVhc2Ugc2VlIHRo
ZSBwYXJhZ3JhcGgNCiBjb250YWluaW5nIHRoZSBiZWxvdyB0ZXh0IGluIFJGQyA2ODI0LWJpcy4g
Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+
JnF1b3Q7SWYgYSBtYXBwaW5nIGZvciB0aGF0IHN1YmZsb3ctbGV2ZWwgc2VxdWVuY2Ugc3BhY2Ug
ZG9lcyBub3QgYXJyaXZlIHdpdGhpbiBhIHJlY2VpdmUgd2luZG93IG9mIGRhdGEsIHRoYXQgc3Vi
ZmxvdyBTSE9VTEQgYmUgdHJlYXRlZCBhcyBicm9rZW4sIGNsb3NlZCB3aXRoIGEgUlNULA0KIGFu
ZCBhbnkgdW5tYXBwZWQgZGF0YSBzaWxlbnRseSBkaXNjYXJkZWQuJnF1b3Q7PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+aWYgd2UgYXNzdW1lIHRoYXQg
dGhlIG1hcCBpcyBpbmNsdWRlZCB3aGlsZSByZXRyYW5zbWl0dGluZyB0aGUgZGF0YSAoZXZlbiB0
aG91Z2ggdGhlIGZpcnN0IHRyYW5zbWlzc2lvbiBkaWQgbm90IGNvbnRhaW4gdGhlIG1hcCBmb3Ig
c29tZSByZWFzb25zKSwgJm5ic3A7d2UgY291bGQgYXJndWUNCiB0aGF0IFJTVCBjb3VsZCBiZSBh
dm9pZGVkIHByb3ZpZGVkIHRoYXQgdGhlIHJldHJhbnNtaXNzaW9uIGlzIHRyaWdnZXJlZCB3aXRo
aW4gYSByZWNlaXZlIHdpbmRvdyBvZiBkYXRhLiBCdXQgdGhlIHF1ZXN0aW9uIGhlcmUgd291bGQg
YmUgaG93IGFuZCB3aGVuIHdpbGwgdGhlIHJldHJhbnNtaXNzaW9uIHRha2UgcGxhY2UuIEluIHRo
aXMgY2FzZSwgdGhlIHN1YmZsb3cgbWF5IG5vdCBpbml0aWF0ZSB0aGUgcmV0cmFuc21pc3Npb24g
b2YgZGF0YSBieQ0KIGl0cyBvd24gKGkuZS4sIG5vIHJldHJhbnNtaXNzaW9uIGR1ZSB0byB0aHJl
ZSBkdXBsaWNhdGUgQUNLcyBvciBSVE8gZXhwaXJ5IGF0IHN1YmZsb3cgbGV2ZWwpIGFzIHRoZXJl
IGlzIG5vIHNlZ21lbnQgbG9zcyBhdCBzdWJmbG93IGxldmVsIHNlcXVlbmNlIHNwYWNlLiBTbyB0
aGVyZSBjb3VsZCBiZSBhIGhpZ2ggcG9zc2liaWxpdHkgb2YgUlNUIGhhcHBlbmluZyBldmVuIGJl
Zm9yZSB0aGUgbWFwIGRlbGl2ZXJ5IHRocm91Z2ggcmV0cmFuc21pc3Npb24uJm5ic3A7PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+V2l0aCByZWdhcmRz
LCZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2si
PkFuaWw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImNlbnRlciIgc3R5
bGU9InRleHQtYWxpZ246Y2VudGVyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4NCjxociBz
aXplPSIyIiB3aWR0aD0iMTAwJSIgYWxpZ249ImNlbnRlciIgaWQ9ImdtYWlsLW1fMjE4MDg2NTk2
OTUxNzI0NTAxZ21haWwtbV8yOTgyMjY3MDMzNTc3OTAyOTg1endjaHIiPg0KPC9zcGFuPjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2siPkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZxdW90O1lv
c2hpZnVtaSBOaXNoaWRhJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86bnNkLmlldGZAZ21haWwu
Y29tIiB0YXJnZXQ9Il9ibGFuayI+bnNkLmlldGZAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5U
bzogPC9iPiZxdW90O1YgQW5pbCBLdW1hciZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaWxA
Y3NpcjRwaS5pbiIgdGFyZ2V0PSJfYmxhbmsiPmFuaWxAY3NpcjRwaS5pbjwvYT4mZ3Q7PGJyPg0K
PGI+Q2M6IDwvYj4mcXVvdDthbGFuIGZvcmQmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzphbGFu
LmZvcmRAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+YWxhbi5mb3JkQGdtYWlsLmNvbTwvYT4m
Z3Q7LCAmcXVvdDttdWx0aXBhdGh0Y3AmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzptdWx0aXBh
dGh0Y3BAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tdWx0aXBhdGh0Y3BAaWV0Zi5vcmc8L2E+
Jmd0Ozxicj4NCjxiPlNlbnQ6IDwvYj5TYXR1cmRheSwgRmVicnVhcnkgMSwgMjAyMCAzOjM5OjUx
IEFNPGJyPg0KPGI+U3ViamVjdDogPC9iPlJlOiBbbXVsdGlwYXRodGNwXSBSRkM2ODI0YmlzIGVk
aXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2si
PkhpIEFuaWwsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
Mi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFj
ayI+SSBoYXZlIGEgcXVlc3Rpb24gYWJvdXQgeW91ciBwcm9wb3NlZCB0ZXh0Li48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+SSBhbSBhY3R1YWxseSB3b25kZXJpbmcgaWYgd2Ug
cmVhbGx5IHdhbnQgdG8gdGVybWluYXRlIGNvbm5lY3Rpb24gaGVyZS4mbmJzcDs8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPlRoZSBwYWNr
ZXRzIHdpdGhvdXQgcHJvcGVyIG1hcHBpbmdzIHdpbGwgYmUgdHJlYXRlZCBhcyBpbnZhbGlkIGFu
ZCB3aWxsIGJlIGRpc2NhcmRlZC4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBw
dDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5J
ZiBhbiBpbXBsZW1lbnRhdGlvbiBmYWlsZWQgdG8gYXR0YWNoIHByb3BlciBtYXBwaW5nIGZvciBz
b21lIHJlYXNvbnMgKGUuLmcuIG9wdGlvbiBzcGFjZSksIGl0IG1pZ2h0IGJlIGFibGUgdG8gYXR0
YWNoIHRoZSBwcm9wZXIgb25lIHdoZW4gaXQgcmV0cmFuc21pdHMgdGhlIHBhY2tldHMuDQogVGhp
cyBhbHNvIGxvb2tzIG9rIHRvIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2siPkkgZG9uJ3QgaGF2ZSBzdHJvbmcgcHJlZmVyZW5jZSBmb3IgdGhpcy4g
QnV0LCBkbyB3ZSBoYXZlIGEgcmVhc29uIHRvIHRlcm1pbmF0ZSBjb25uZWN0aW9uPzxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPlRoYW5rcyw8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4tLTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPllv
c2hpPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2siPk9uIE1vbiwgSmFuIDEzLCAyMDIwIGF0IDEwOjI4IEFNIFYgQW5pbCBLdW1hciAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmFuaWxAY3NpcjRwaS5pbiIgdGFyZ2V0PSJfYmxhbmsiPmFuaWxAY3NpcjRw
aS5pbjwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7
cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6
MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+SGksPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2si
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5JIGhhdmUgc29tZSBwb2ludHMgcmVsYXRlZCB0
byB0aGUgJm5ic3A7bW9kaWZpY2F0aW9ucyAoQ2hhbmdlIDIpIGJlaW5nIHByb3Bvc2VkIG9uIGRh
dGEgc2VxdWVuY2UgbWFwLiBQbGVhc2Ugc2VlIHRoZW0gaW5saW5lLiZuYnNwOzxzcGFuIHN0eWxl
PSJiYWNrZ3JvdW5kOndoaXRlIj5UaG91Z2ggSSBhbQ0KIHB1dHRpbmcgZm9yd2FyZCB0aGUgYmVs
b3cgcG9pbnRzLCBpZiB0aGUgY29uc2Vuc3VzIGlzIGluIGZhdm91ciBvZiB0aGUgcHJvcG9zZWQg
Y2hhbmdlIGZvciByZWR1Y2luZyBpbXBsZW1lbnRhdGlvbiBjb21wbGV4aXR5LCBJIGFtIGFsc28g
T0sgd2l0aCB0aGF0IGFzIHdlbGwuJm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFsIiBhbGln
bj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
YmxhY2siPg0KPGhyIHNpemU9IjIiIHdpZHRoPSIxMDAlIiBhbGlnbj0iY2VudGVyIiBpZD0iZ21h
aWwtbV8yMTgwODY1OTY5NTE3MjQ1MDFnbWFpbC1tXzI5ODIyNjcwMzM1Nzc5MDI5ODVnbWFpbC1t
Xzc2ODcxODQzODIyOTk1OTY3NzR6d2NociI+DQo8L3NwYW4+PC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+RnJvbToNCjwvc3Bh
bj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+JnF1b3Q7YWxhbiBmb3JkJnF1b3Q7ICZs
dDs8YSBocmVmPSJtYWlsdG86YWxhbi5mb3JkQGdtYWlsLi5jb20iIHRhcmdldD0iX2JsYW5rIj5h
bGFuLmZvcmRAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5UbzogPC9iPjxhIGhyZWY9Im1haWx0
bzptdWx0aXBhdGh0Y3BAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tdWx0aXBhdGh0Y3BAaWV0
Zi5vcmc8L2E+PGJyPg0KPGI+U2VudDogPC9iPlRodXJzZGF5LCBKYW51YXJ5IDIsIDIwMjAgNDoy
MTozMiBBTTxicj4NCjxiPlN1YmplY3Q6IDwvYj5bbXVsdGlwYXRodGNwXSBSRkM2ODI0YmlzIGVk
aXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+SGkgYWxsLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij5XZeKAmWQgbG92ZSB0byBnZXQgdGhpcyB0byBhIHN0YXRlIG9mIGNvbXBsZXRpb24gYXMgc29v
biBhcyBwb3NzaWJsZSwgYW5kIHRvIHRoaXMgZW5kIEkgYW0gc3RhcnRpbmcgYSBuZXcgdGhyZWFk
IG9uIHRoaXMgdG9waWMuIEluIGRpc2N1c3Npb24gd2l0aCB0aGUgY2hhaXJzLCBpdA0KPGk+aXMg
PC9pPnBvc3NpYmxlIHRvIG1ha2UgdGhlIGRlc2lyZWQgY2hhbmdlcyBpbiBBVVRINDggYXMgbG9u
ZyBhcyB0aGVyZSBpcyBXRyBjb25zZW5zdXMuIFRoZSBkaXNjdXNzaW9uIHNvIGZhciBoYXMgYmVl
biBmYWlybHkgbGltaXRlZCBpbiB0ZXJtcyBvZiBwYXJ0aWNpcGF0aW9uLjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkkgd291bGQgYXNrIHRoZSBjaGFp
cnMgcGxlYXNlIGlmIGl0IHdhcyBwb3NzaWJsZSB0byBzcGVjaWZ5IGEgdGltZSBib3VuZCBmb3Ig
dGhpcyBkaXNjdXNzaW9uIGFuZCBhIGRlZmF1bHQgY29uY2x1c2lvbi48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5SZWdhcmRpbmcgdGhlIGNoYW5nZXMs
IGluIHN1bW1hcnksIHRoZXJlIGFyZSB0d28gYXJlYXMgd2hlcmUgY2hhbmdlcyBoYXZlIGJlZW4g
cmVxdWVzdGVkIGJ5IHRoZSBpbXBsZW1lbnRhdGlvbiBjb21tdW5pdHkuIEFzIHdlIGFyZSB0aGUg
SUVURiB3ZSBvYnZpb3VzbHkgaGF2ZSBzdHJvbmcNCiBmb2N1cyBvbiDigJxydW5uaW5nIGNvZGXi
gJ0gYW5kIHNvIGVhc2Ugb2YgaW1wbGVtZW50aW5nIHN0YW5kYXJkcy1jb21wbGlhbnQgY29kZSBp
cyBzdHJvbmdseSBkZXNpcmFibGUuIEhvd2V2ZXIsIHdlIGRvIG5vdCB3aXNoIHRvIHJlZHVjZSBm
dW5jdGlvbmFsaXR5IGFncmVlZCBieSB0aGUgSUVURiBjb21tdW5pdHkgaWYgaXQgaXMgY29uc2lk
ZXJlZCBhIHJlcXVpcmVkIGZlYXR1cmUgYnkgdGhlIGNvbW11bml0eS48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9t
OjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6YmxhY2siPkNoYW5nZSAxPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBw
dDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRv
bToxMi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkNoYW5nZSB0aGUgc2VudGVuY2Ug
cmVhZGluZzo8YnI+DQo8YnI+DQo8aT4mbmJzcDsgJm5ic3A7SWYgQiBoYXMgZGF0YSB0byBzZW5k
IGZpcnN0LCB0aGVuIHRoZSByZWxpYWJsZSBkZWxpdmVyeSBvZiB0aGUgQUNLICYjNDM7IE1QX0NB
UEFCTEUgY2FuIGJlIGluZmVycmVkIGJ5IHRoZSByZWNlaXB0IG9mIHRoaXMgZGF0YSB3aXRoIGFu
IE1QVENQIERhdGEgU2VxdWVuY2UgU2lnbmFsIChEU1MpIG9wdGlvbiAoU2VjdGlvbiAzLjMpLiZu
YnNwOzxicj4NCjwvaT48YnI+DQpUbzo8YnI+DQo8YnI+DQo8aT4mbmJzcDsgJm5ic3A7SWYgQiBo
YXMgZGF0YSB0byBzZW5kIGZpcnN0LCB0aGVuIHRoZSByZWxpYWJsZSBkZWxpdmVyeSBvZiB0aGUg
QUNLICYjNDM7IE1QX0NBUEFCTEUgaXMgZW5zdXJlZCBieSB0aGUgcmVjZWlwdCBvZiB0aGlzIGRh
dGEgd2l0aCBhbiBNUFRDUCBEYXRhIFNlcXVlbmNlIFNpZ25hbCAoRFNTKSBvcHRpb24gKFNlY3Rp
b24gMy4zKSBjb250YWluaW5nIGEgREFUQV9BQ0sgZm9yIHRoZSBNUF9DQVBBQkxFICh3aGljaCBp
cyB0aGUgZmlyc3Qgb2N0ZXQgb2YNCiB0aGUgZGF0YSBzZXF1ZW5jZSZuYnNwO3NwYWNlKS48L2k+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+V2hhdCB0aGlzIG1lYW5zOjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPlRoZSBjdXJyZW50IHRleHQg
aXMgY29uY2VybmVkIG9ubHkgd2l0aCBlbnN1cmluZyBhIHBhdGggaXMgTVBUQ1AgY2FwYWJsZSwg
YW5kIHNvIG9ubHkgY2FyZXMgdGhhdCBEU1Mgb3B0aW9uIG9jY3VycyBvbiBhIGRhdGEgcGFja2V0
LiBIb3dldmVyLCB0aGUgTVBfQ0FQQUJMRSBvcHRpb24NCiBpcyBkZWZpbmVkIHRvIG9jY3VweSB0
aGUgZmlyc3Qgb2N0ZXQgb2YgZGF0YSBzZXF1ZW5jZSBzcGFjZSBhbmQgdGh1cywgaWYgYW5hbG9n
b3VzIHRvIFRDUCwgbXVzdCBiZSBhY2tub3dsZWRnZWQuICZndDtGcm9tIGFuIGltcGxlbWVudGF0
aW9uIHBvaW50IG9mIHZpZXcgaXQgd291bGQgbWFrZSBzZW5zZSBub3QgdG8gaGF2ZSB0aGlzIGhh
bmdpbmcgYXJvdW5kIGZvcmV2ZXIgYW5kIGluc3RlYWQgZGVmaW5lIGl0IGlzIGFja25vd2xlZGdl
ZCBhdCB0aGUNCiBjb25uZWN0aW9uIGxldmVsIGFzIHNvb24gYXMgcmVjZWl2ZWQuIFRoaXMgY2hh
bmdlIGVuc3VyZXMgdGhlIGZpcnN0IGRhdGEgcGFja2V0IGFsc28gREFUQV9BQ0tzIHRoaXMgTVBf
Q0FQQUJMRSBvY3RldC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkNoYW5nZSAyPC9zcGFuPjwv
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5DaGFuZ2UgdGhlIHNlbnRlbmNl
IHJlYWRpbmc6PGJyPg0KPGJyPg0KPGk+Jm5ic3A7ICZuYnNwO0EgRGF0YSBTZXF1ZW5jZSBNYXBw
aW5nIGRvZXMgbm90IG5lZWQgdG8gYmUgaW5jbHVkZWQgaW4gZXZlcnkgTVBUQ1AgcGFja2V0LCBh
cyBsb25nIGFzIHRoZSBzdWJmbG93IHNlcXVlbmNlIHNwYWNlIGluIHRoYXQgcGFja2V0IGlzIGNv
dmVyZWQgYnkgYSBtYXBwaW5nIGtub3duIGF0IHRoZSByZWNlaXZlci48L2k+PGJyPg0KPGJyPg0K
VG86PGJyPg0KPGJyPg0KPGk+Jm5ic3A7ICZuYnNwO1RoZSBtYXBwaW5nIHByb3ZpZGVkIGJ5IGEg
RGF0YSBTZXF1ZW5jZSBNYXBwaW5nIE1VU1QgYXBwbHkgdG8gc29tZSBvciBhbGwgb2YgdGhlIHN1
YmZsb3cgc2VxdWVuY2Ugc3BhY2UgaW4gdGhlIFRDUCBzZWdtZW50IHdoaWNoIGNhcnJpZXMgdGhl
IG9wdGlvbi4gSXQgZG9lcyBub3QgbmVlZCB0byBiZSBpbmNsdWRlZCBpbiBldmVyeSBNUFRDUCBw
YWNrZXQsIGFzIGxvbmcgYXMgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2UgaW4gdGhhdCBwYWNr
ZXQNCiBpcyBjb3ZlcmVkIGJ5IGEgbWFwcGluZyBrbm93biBhdCB0aGUgcmVjZWl2ZXIuPGJyPg0K
PC9pPjxicj4NCldoYXQgdGhpcyBtZWFuczo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj5UaGUgY3VycmVudCB0ZXh0IGRvZXMgbm90IHBsYWNlIGFueSBy
ZXN0cmljdGlvbnMgb24gd2hlcmUgYSBtYXBwaW5nIGNvdWxkIGFwcGVhci4gSW4gdGhlb3J5IGEg
c2VuZGVyIGNvdWxkIGRlZmluZSBhIHRob3VzYW5kIGRpZmZlcmVudCBtYXBwaW5ncyB1cCBmcm9u
dCwgc2VuZCB0aGVtDQogYWxsLCBhbmQgZXhwZWN0IGEgcmVjZWl2ZXIgdG8gc3RvcmUgdGhpcyBh
bmQgcmVhc3NlbWJsZSBkYXRhIGFjY29yZGluZyB0byB0aGVzZSBtYXBwaW5ncyBhcyBpdCBhcnJp
dmVzLiBJbmRlZWQsIHRoaXMgd2FzIG5ldmVyIGV4cGxpY2l0bHkgZGlzYWxsb3dlZCBzaW5jZSBp
dCDigJxtaWdodCBoYXZlIGJlZW4gdXNlZnVs4oCdLiBUaGUgaW1wbGVtZW50YXRpb24gY29tbXVu
aXR5LCBob3dldmVyLCBoYXMgZXhwcmVzc2VkIGNvbmNlcm5zIG92ZXIgdGhlIGRpZmZpY3VsdHkN
CiBvZiBpbXBsZW1lbnRpbmcgdGhpcyBvcGVuLWVuZGVkbHkuIEhvdyBtYW55IG1hcHBpbmdzIGlz
IGl0IHJlYXNvbmFibGUgdG8gc3RvcmU/IElzIHRoZXJlIGEgRG9TIHJpc2sgaGVyZT8gSW5zdGVh
ZCwgaXQgaGFzIGJlZW4gcmVxdWVzdGVkIHRoYXQgdGhlZSBzcGVjaWZpY2F0aW9uIHJlc3RyaWN0
cyB0aGUgcGxhY2VtZW50IG9mIHRoZSBEU1Mgb3B0aW9uIHRvIGJlaW5nIHdpdGhpbiB0aGUgc3Vi
ZmxvdyBzZXF1ZW5jZSBzcGFjZSB0byB3aGljaCBpdA0KIGFwcGxpZXMuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+QmVsb3cgYXJlIG15IGNvbW1lbnRz
IG9uIHRoaXMuIEkgaGFkIHNoYXJlZCBzb21lIG9mIHRoZXNlIHBvaW50cyBpbiBhIHByZXZpb3Vz
IHRocmVhZCB0aGF0IHlvdSBoYWQgaW5pdGlhdGVkIGluIHRoZSBzYW1lIGNvbnRleHQuJm5ic3A7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+VHJhbnNt
aXR0aW5nIGxhcmdlIG51bWJlciBvZiBub24tY29udGlndW91cyBkYXRhIHNlcXVlbmNlIG1hcHMg
Y291bGQgYmUgYSBtaXNiZWhhdmlvdXIgKG1hcC1mbG9vZGluZyksIHRob3VnaCBpdCBpcyBub3Qg
Y2xlYXIgd2hldGhlciB0aGlzIGNhbiBnbyB0byB0aGUgZXh0ZW50IG9mDQogY2F1c2luZyBhIHBv
dGVudGlhbCBEb1MgdG8gdGhlIGRhdGEgcmVjZWl2ZXIuIFNvIHNvbWUgc29ydCBvZiByZXN0cmlj
dGlvbiBvbiB0aGlzIGNvdWxkIGJlIHVzZWZ1bC4mbmJzcDsgT25lIGFwcHJvYWNoIGNvdWxkIGJl
IHRvIGluc2lzdCB0aGF0IHRoZSBkYXRhIHNlbmRlciBzaG91bGQgZW5zdXJlIHRoYXQgdGhlIG1h
cCBiZWluZyB0cmFuc21pdHRlZCBpcyBmb3IgaW4td2luZG93IGRhdGEsIGFzIHBlciB0aGUgcmVj
ZWl2ZXIgYWR2ZXJ0aXNlZCB3aW5kb3cuDQogQSByZWNlaXZlciBzaG91bGQgYW55aG93IGJlIHdp
bGxpbmcgdG8gc3RvcmUgdGhlIG1hcHMgZm9yIGluLXdpbmRvdyBkYXRhIHRvIGRlYWwgd2l0aCBw
YWNrZXQgbG9zcy4gRm9yIGV4YW1wbGUsIHdoZW4gYSB3aW5kb3cgb2YgZGF0YSBzZWdtZW50cyAo
c2F5IDEgdG8gNjQpIGlzIHRyYW5zbWl0dGVkLCBlYWNoIGNhcnJ5aW5nIGl0cyBjb3JyZXNwb25k
aW5nIG1hcCwgYW5kIHNlZ21lbnQtMSBpcyBsb3N0LCB0aGUgbWFwcyBmb3IgdGhlIHJlbWFpbmlu
Zw0KIDYzIG5lZWQgdG8gYmUgc3RvcmVkIHRpbGwgdGhlIGxvc3Qgc2VnbWVudCBpcyByZXRyYW5z
bWl0dGVkLiBPZiBjb3Vyc2UsIGluIHRoaXMgY2FzZSB0aGUgbWFwcyB3aWxsIGJlIHN0b3JlZCBh
dCB0aGUgcmVjZWl2ZXIgc2lkZSBhbG9uZyB3aXRoIHRoZWlyIGNvcnJlc3BvbmRpbmcgZGF0YS4g
QnV0IHRoZSBuZWVkIHRvIHN0b3JlIG11bHRpcGxlIG1hcHMgZm9yIGluLXdpbmRvdyBkYXRhIHdv
dWxkIHN0aWxsIGJlIHRoZXJlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6YmxhY2s7YmFja2dyb3VuZDp3aGl0ZSI+VGhlIHByb2JsZW0gd2l0aCB0aGUgcHJvcG9z
ZWQgY2hhbmdlIChyZXN0cmljdGlvbikgaXMgdGhhdCBhIGRhdGEgc2VuZGVyIG1heSBmaW5kIGl0
IGRpZmZpY3VsdCwgaW4gY2FzZSBhIG5lZWQgYXJpc2UgdG8gc2xpZ2h0bHkgZGVsYXkgdGhlIG1h
cCBkZWxpdmVyeQ0KIGJ5IGZldyBzZWdtZW50cywgaS5lLiwgc2VuZGluZyBzb21lIGRhdGEgZmly
c3Qgd2l0aG91dCBtYXAsIGFuZCB0aGVuIHNlbmQgdGhlIGNvcnJlc3BvbmRpbmcgbWFwIGluIGEg
bGF0ZXIgc2VnbWVudCwgYXMgc2hvd24gYmVsb3c6PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3
aGl0ZSI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPnN1YmZsb3ct
MTombmJzcDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50LTEmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHNlZ21lbnQtMyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50LTQgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50LTc8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpi
bGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Ynl0ZXM6MS0xMDAgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBieXRlczoyMDEtMzAw
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2J5dGVzOjMw
MS00MDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyBieXRlczo2MDEtNzAwPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyZuYnNwO25vIG1hcCAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwO21hcCBmb3IgMS0xMDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7bWFwIGZvciAyMDEtNDAwICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7IG1hcCBmb3IgNjAxLTcwMDwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxicj4NCjxicj4NCjwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29l
IFVJJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxicj4NCjxicj4NCjwvc3Bhbj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hp
dGUiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5zdWJmbG93LTI6
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7c2VnbWVudC0yJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgc2VnbWVudC01ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBzZWdtZW50LTYgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzZWdtZW50LTg8L3NwYW4+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Ynl0ZXM6IDEwMS0yMDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBieXRl
czo0MDEtNTAwJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBieXRlczogNTAxLTYwMCAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Ynl0ZXM6NzAxLTgw
MCZuYnNwOyZuYnNwOyZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6YmxhY2siPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7bWFwIGZvciAxMDEtMjAwICZu
YnNwOyAmbmJzcDsgJm5ic3A7IG1hcCBmb3IgNDAxLTYwMCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwO25vIG1hcCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7bWFwIGZvciA3MDEtODAwPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJs
YWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5JbiB0aGUgYWJvdmUgY2Fz
ZSwgc2VnbWVudC0xIGdvZXMgd2l0aG91dCBtYXAgYW5kIGl0cyBtYXAgaXMgaW5jbHVkZWQgbGF0
ZXIgaW4gc2VnbWVudC0zLCB0aGUgbmV4dCBkYXRhIHNlZ21lbnQgaW4gdGhlIHNhbWUgc3ViZmxv
dy4gRnVydGhlciwgJm5ic3A7aW4gdGhlIGFib3ZlIHNjaGVkdWxpbmcNCiBwYXR0ZXJuLCB0aGUg
bWFwIGluIHNlZ21lbnQtMyBjYW5ub3QgY292ZXIgdGhlICZuYnNwO2RhdGEgaW4gc2VnbWVudC0x
IGFuZCBzZWdtZW50LTMsIGFzIHNvbWUgJm5ic3A7ZGF0YSBpbiBiZXR3ZWVuIChzZWdtZW50LTIp
IGlzIHRyYW5zbWl0dGVkIHRocm91Z2ggYW5vdGhlciBzdWJmbG93LiZuYnNwOyBXaXRoIHRoZSBw
cm9wb3NlZCBjaGFuZ2UsIHRoZSBtYXAgaW4gc2VnbWVudC0zIHdpbGwgYmVjb21lIGludmFsaWQg
YW5kIHRoaXMgd2lsbCBldmVudHVhbGx5IGJyZWFrDQogc3ViZmxvdy0xLCB0aG91Z2ggdGhpcyBj
b3VsZCBiZSBhIGNvcm5lciBjYXNlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2siPlRoZSBxdWVzdGlvbiBhdCB0aGlzIHN0YWdlIGlzIHdoeSB3b3VsZCBz
ZWdtZW50LTEgYmUgdHJhbnNtaXR0ZWQgd2l0aG91dCBpdHMgbWFwLiBJbiB0aGUgY2FzZSBvZiBi
aWRpcmVjdGlvbmFsIGRhdGEgdHJhbnNmZXIsIHRoZXJlIGNvdWxkIGJlIGEgbmVlZCB0byBwYWNr
IGJvdGggdGltZXN0YW1wDQogYW5kIFNBQ0sgJm5ic3A7b3B0aW9ucyBpbiBhIGRhdGEgc2VnbWVu
dCwgaS5lLiwgcGlnZ3liYWNraW5nIG9mICZuYnNwO1NBQ0sgd2l0aCBkYXRhLiBJZiB3ZSBjb25z
aWRlciB0aGF0IHRpbWVzdGFtcCB0YWtlcyAxMiBieXRlcyBhbmQgU0FDSywgZXZlbiB3aXRoIHNp
bmdsZSBibG9jaywgJm5ic3A7dGFrZXMgYW5vdGhlciAxMCBieXRlcywgdGhlIHJlbWFpbmluZyAx
OCBieXRlcyBvcHRpb24gc3BhY2UgaXMgbm90IGFkZXF1YXRlIHRvIGNhcnJ5IGRhdGEgc2VxdWVu
Y2Ugc2lnbmFsDQogd2l0aCBtYXAsIGVzcGVjaWFsbHkgd2hlbiBEU04gaXMgNjQgYml0IGxvbmcu
IFNvIHRoZSBkZWxpdmVyeSBvZiBlaXRoZXIgb2YgdGhlIHR3byAoU0FDSyBvciBtYXApIHdvdWxk
IGJlIGRlbGF5ZWQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpi
bGFjayI+QXMgZmFyIGFzIEkgdW5kZXJzdGFuZCwgUkZDIDIwMTggKFRDUCBTZWxlY3RpdmUgQWNr
bm93bGVkZ2VtZW50IE9wdGlvbnMpIGltcGxpZXMgdGhhdCBTQUNLIHNob3VsZCBub3QgYmUgZGVs
YXllZC4gSXQgc3RhdGVzICZxdW90O0lmIHNlbnQgYXQgYWxsLCBTQUNLIG9wdGlvbnMgU0hPVUxE
IGJlDQogaW5jbHVkZWQgaW4gYWxsIEFDS3Mgd2hpY2ggZG8gbm90IEFDSyB0aGUgaGlnaGVzdCBz
ZXF1ZW5jZSBudW1iZXIgaW4gdGhlIGRhdGEgcmVjZWl2ZXIncyBxdWV1ZSZxdW90Oy4uIEl0IGFs
c28gc2F5cyAmcXVvdDtJZiBkYXRhIHJlY2VpdmVyIGdlbmVyYXRlcyBTQUNLIG9wdGlvbnMgdW5k
ZXIgYW55IGNpcmN1bXN0YW5jZSwgaXQgU0hPVUxEIGdlbmVyYXRlIHRoZW0gdW5kZXIgYWxsIHBl
cm1pdHRlZCBjaXJjdW1zdGFuY2VzJnF1b3Q7LiAmbmJzcDsgU28sIGFzIHBhcnQgb2YgbWVldGlu
Zw0KIHRoZSBSRkMgMjAxOCByZXF1aXJlbWVudHMsIGlmIHRoZSBjb21iaW5hdGlvbiBvZiBTQUNL
IGFuZCB0aW1lc3RhbXAgaXMgZ2l2ZW4gcHJlZmVyZW5jZSBvdmVyIERTUywgZGF0YSBzZWdtZW50
cyBjb3VsZCBiZSB0cmFuc21pdHRlZCB3aXRob3V0IHRoZWlyIG1hcC4mbmJzcDs8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5Bbm90aGVyIGNhc2Ugb2Yg
ZGVsYXlpbmcgbWFwIGNvdWxkIGFyaXNlIGlmIHRoZSBkYXRhIHNlbmRlciBwcmVmZXJzIHRvIHNl
bmQgQUREX0FERFIgb3B0aW9uLCBpbnN0ZWFkIG9mIG1hcCwgaW4gYSBkYXRhIHNlZ21lbnQuIEl0
IGlzIG5pY2UgdGhhdCBBRERfQUREUiBvcHRpb24gY2FuDQogYmUgZGVsaXZlcmVkIHJlbGlhYmx5
IGluIGEgcHVyZSBBQ0ssIGJ1dCBJIHRoaW5rIHRoaXMgaXMgbm90IHRoZSBjYXNlIHdpdGggRFNT
IGF0IHByZXNlbnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpi
bGFjayI+SWYgd2UgYWRvcHQgdGhlIHByb3Bvc2VkIGNoYW5nZSwgSSB0aGluayBpdCBtaWdodCBh
bHNvIGJlIGhlbHBmdWwgdG8gc3BlbGwgb3V0IGhvdyB0aGUgcmVjZWl2ZXIgaXMgc3VwcG9zZWQg
dG8gYmVoYXZlLCBpZiBpdCBnZXRzIG1hcHMgbm90IG1lZXRpbmcgdGhlIE1VU1QgY29uZGl0aW9u
DQogaW4gdGhlIHByb3Bvc2VkIGNoYW5nZS4mbmJzcDsgRm9yIGV4YW1wbGUgdGVybWluYXRpb24g
b2YgdGhlIHN1YmZsb3cgd2l0aCBNUF9UQ1BSU1Qgb3B0aW9uIChzZWN0aW9uIDMuLjYgaW4gUkZD
IDY4MjQtYmlzKSB3aXRoIGFwcHJvcHJpYXRlIHJlYXNvbiBjb2RlIGFuZCBUIGZsYWcgdmFsdWUg
dG8gaW50aW1hdGUgdGhlIGRhdGEgc2VuZGVyIHRoZSBjYXVzZSBmb3Igc3ViZmxvdyB0ZXJtaW5h
dGlvbi4mbmJzcDsmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJs
YWNrIj5XaXRoIHJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1i
b3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5BbmlsPG86cD48L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6YmxhY2siPlBsZWFzZSBjYW4gbWVtYmVycyBvZiB0aGUgV0cgZXhwcmVzcyB3aGV0aGVyIHRo
ZXkgYXJlIGhhcHB5IHdpdGggdGhlc2UgY2hhbmdlcywgb3IgY29uY2VybmVkLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkJlc3QgcmVnYXJkcyw8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5BbGFuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48YnI+
DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxi
cj4NCm11bHRpcGF0aHRjcCBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86bXVsdGlw
YXRodGNwQGlldGYuLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm11bHRpcGF0aHRjcEBpZXRmLm9yZzwv
YT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211
bHRpcGF0aHRjcCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vbXVsdGlwYXRodGNwPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpi
bGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PGJyPg0K
PGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+
DQptdWx0aXBhdGh0Y3AgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm11bHRpcGF0
aHRjcEBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm11bHRpcGF0aHRjcEBpZXRmLm9yZzwvYT48
YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRp
cGF0aHRjcCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbXVsdGlwYXRodGNwPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxvY2txdW90
ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
Ym90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVs
dmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_LNXP123MB258719E5B3D9F99B7E715111EB180LNXP123MB2587GBRP_--


From nobody Tue Feb 11 14:30:14 2020
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4CB120826 for <multipathtcp@ietfa.amsl.com>; Tue, 11 Feb 2020 14:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 b0q7d15ZVTdE for <multipathtcp@ietfa.amsl.com>; Tue, 11 Feb 2020 14:30:07 -0800 (PST)
Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (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 6102E120825 for <multipathtcp@ietf.org>; Tue, 11 Feb 2020 14:30:07 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id 01BMM5MN012062; Tue, 11 Feb 2020 14:30:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=r0yj33hcSJeGUjTpxGLAeg5A/ZgIf8xCJ7TcKiWhiP4=; b=eXTp7KBZ5/MituPDRpQPWW9wdoVwewgPKNKFPGZTRvwb2WAtI27g4z3Ii1IzwvkQlwFD 1pJ9NfFfYR4aMUO0mK4A7ON9RvcR9DLcTPvfTmep/00clfjJrwGmJxIMpUzXgSAO+AFG OXhEz4hCJD4B24EfwYkAS84hIrKmO0R+dPtQRuCsgoNIjoTtYX7bNQMawiP41z4dqtYe nzYVcA1irMdVqe3tmB3VGHyJ+CKh6FMeBivK7PAKFPQfYC9g6Q1Jgo44esvpBSVMrtwU AQIYV7gr5a4MrFasoyyusQ5/7u6vUlewy61QvxVyt0GO6Mz0uXnTpVaaI/y9uySkV6Sd Yw== 
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 2y1vuycu49-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 11 Feb 2020 14:30:00 -0800
Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.1.20190704 64bit (built Jul  4 2019)) with ESMTPS id <0Q5K0068G6HZGC70@rn-mailsvcp-mta-lapp02.rno.apple.com>;  Tue, 11 Feb 2020 14:29:59 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.1.20190704 64bit (built Jul  4 2019)) id <0Q5K00Z005ZYE900@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Tue, 11 Feb 2020 14:29:59 -0800 (PST)
X-Va-A: 
X-Va-T-CD: 772dd47e94105b6916a0f4f153438e87
X-Va-E-CD: ae422271a38913bbedae93e9e9d60fc7
X-Va-R-CD: a5d4677ae470b25e3a5d2ab1ded2428a
X-Va-CD: 0
X-Va-ID: ced3b9e7-985d-4813-802a-054f021bf0a3
X-V-A: 
X-V-T-CD: 772dd47e94105b6916a0f4f153438e87
X-V-E-CD: ae422271a38913bbedae93e9e9d60fc7
X-V-R-CD: a5d4677ae470b25e3a5d2ab1ded2428a
X-V-CD: 0
X-V-ID: c1dd0200-9774-46e0-87fb-61f58708be21
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-11_07:2020-02-11, 2020-02-11 signatures=0
Received: from [17.230.176.57] by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.1.20190704 64bit (built Jul  4 2019)) with ESMTPSA id <0Q5K009OD6HYU450@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Tue, 11 Feb 2020 14:29:59 -0800 (PST)
Sender: cpaasch@apple.com
From: Christoph Paasch <cpaasch@apple.com>
Message-id: <F3D07C9D-12B2-45A7-B9D0-23E862DDF4BA@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_112EC709-E02F-48FE-8395-1ED071B40A97"
MIME-version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Date: Tue, 11 Feb 2020 14:29:58 -0800
In-reply-to: <CAAK044QoFh_eXE+MwggOn5X0uUs3xuzTcw2kdJaKuUnEP745dA@mail.gmail.com>
Cc: V Anil Kumar <anil@csir4pi.in>, MultiPath TCP - IETF WG <multipathtcp@ietf.org>, mptcp Upstreaming <mptcp@lists.01.org>
To: Yoshifumi Nishida <nsd.ietf@gmail.com>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com> <1411057985.31281938.1581012439446@csir4pi.in> <CAAK044QoFh_eXE+MwggOn5X0uUs3xuzTcw2kdJaKuUnEP745dA@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-02-11_07:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/eEwuAyItzOHpfjma-831zG3hvsc>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2020 22:30:12 -0000

--Apple-Mail=_112EC709-E02F-48FE-8395-1ED071B40A97
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

+MPTCP-upstreaming

> On Feb 11, 2020, at 1:05 AM, Yoshifumi Nishida <nsd.ietf@gmail.com> =
wrote:
>=20
> Hi folks,
> I guess we might want to know the behavior of existing implementations =
such as linux.
> When an mptcp stack tries to send a data packet and find that there's =
no enough option space for data mapping, what it will do?

iOS, multipath-tcp.org <http://multipath-tcp.org/> and Linux 5.6 =
implementation all favor the DSS-option over any other option (except =
TCP Timestamps). And TCP Timestamps and DSS comfortably fit in the TCP =
option-space.

If SACK-blocks should be added, we only add SACK-blocks up to the =
remaining space. SACK is anyways opportunistic as once there are more =
than 3 blocks they don't fit either.


Christoph

> Split the packet to create more option space?
> --
> Yoshi
>=20
> On Thu, Feb 6, 2020 at 10:10 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Alan,
>=20
> Thank you for your reply. I have two points to clarify. Please see =
them in line.
>=20
> From: "Alan Ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>jk=20
> Cc: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>, "multipathtcp" <multipathtcp@ietf.org =
<mailto:multipathtcp@ietf.org>>
> Sent: Thursday, February 6, 2020 2:49:29 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> Hi Anil,
>=20
> This would not be forbidden if the mapping was carried on a pure ACK =
with no data.
> As far as I understand, delivery of DSM through pure ACK is not in the =
scope of the current draft. If we intend to do this, we may need an =
approach similar to the one proposed for delivery of ADD_ADDR option in =
pure ACK with reliability feature.  So, packing DSM on pure ACK does not =
seem to be an option at this stage.
>=20
> I do see the point here: if a packet of 1000 bytes contains 500 bytes =
of one mapping and 500 bytes of another mapping, then only one DSM would =
appear on one packet, leaving the mapping for the second 500 bytes to be =
carried somewhere else - the only option being a pure ACK. But this kind =
of scenario would be extremely rare
> Yes, I do agree that the scenario you mentioned above would be =
extremely rare. In fact, I wonder whether such a situation (i.e., need =
to cover the bytes in a single packet with two different maps) would =
ever arise. Probably there might be some corner cases, which I don't get =
it rightly now.=20
>=20
> More importantly, the scenario that Yoshi and me are referring to is =
totally different: the one I had given as part of my comments in =
response to the proposed change 2. In this scenario, which you could see =
in the trailing mail, data segment-1 is transmitted without including =
its map, something which is permitted in the  mptcp framework (6824 =
bis). I make this inference from the below text in 6824 bis:
>=20
> "...even if a mapping does not exist from the subflow space to the =
data- level space, the data SHOULD still be ACKed at the subflow (if it =
is in-window). This data cannot, however, be acknowledged at the data =
level (Section 3.3.2) because its data sequence numbers are unknown. =
Implementations MAY hold onto such unmapped data for a short while in =
the expectation that a mapping will arrive shortly."
>=20
> One option the data sender has at this stage is to include the map for =
data in segment-1, in segment-3 (please see the two-subflow example I =
gave in response to the change 2 you had proposed). But the proposed =
change does not permit this. What would happen to  subflow-1 in this =
case ?
>=20
> With regards,
>=20
> Anil   =20
> and I would imagine any implementation would just split into two 500 =
byte segments each with the PSH flag set. I don=E2=80=99t think we need =
to spell this out in the spec however.
>=20
> Regards,
> Alan
>=20
> On 5 Feb 2020, at 15:09, V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Yoshi,
>=20
> Please see in line.
>=20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, =
"multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> Sent: Tuesday, February 4, 2020 1:08:45 PM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
>=20
> Hi Anil,
>=20
> Thanks for pointing it out. I overlooked this one.
> This looks an interesting point.
>=20
> It seems to me that whether RST is happen or not depends on the size =
of receive window according to the text.
> If the receive window size is big enough to accommodate segment 1 and =
segment 3, the text "Implementations MAY hold onto such unmapped data =
for a short while in the expectation that a mapping will arrive shortly. =
" can be applied to the segment 1. As a result, the segment 1 won't be =
discarded.=20
>=20
> Yes.  So, segment 1 may be kept in the data receiver's buffer in =
expectation that its mapping will arrive shortly. And in the example =
that we are referring to, the data sender will not be able to include =
the map for the data in segment 1 in segment 3 or any higher segment.
>=20
> Regards,
>=20
> Anil
>=20
> However, this might be contradict with the new texts Alan proposed? =
Or, am I missing something?
>=20
> Thanks,
> --
> Yoshi
>=20
>=20
>=20
> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Yoshi,
>=20
> Thanks for this point. In fact, I had initially not thought of a =
scenario, where the map is being delivered through a retransmitted data =
packet while its first transmission did not include the map. Now I am =
just seeing the document (RFC 6824-bis) in this context.
>=20
> My understanding is that in scenarios like what I described in my =
previous mail, RST is likely to happen whether we explicitly state so or =
not. Please see the paragraph containing the below text in RFC 6824-bis. =
=20
>=20
> "If a mapping for that subflow-level sequence space does not arrive =
within a receive window of data, that subflow SHOULD be treated as =
broken, closed with a RST, and any unmapped data silently discarded."
>=20
> if we assume that the map is included while retransmitting the data =
(even though the first transmission did not contain the map for some =
reasons),  we could argue that RST could be avoided provided that the =
retransmission is triggered within a receive window of data. But the =
question here would be how and when will the retransmission take place. =
In this case, the subflow may not initiate the retransmission of data by =
its own (i..e., no retransmission due to three duplicate ACKs or RTO =
expiry at subflow level) as there is no segment loss at subflow level =
sequence space. So there could be a high possibility of RST happening =
even before the map delivery through retransmission.=20
>=20
> With regards,=20
>=20
> Anil
> =20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, =
"multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> Sent: Saturday, February 1, 2020 3:39:51 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
>=20
> Hi Anil,
>=20
> I have a question about your proposed text.
> I am actually wondering if we really want to terminate connection =
here.=20
>=20
> The packets without proper mappings will be treated as invalid and =
will be discarded.=20
> If an implementation failed to attach proper mapping for some reasons =
(e.g. option space), it might be able to attach the proper one when it =
retransmits the packets. This also looks ok to me.
>=20
> I don't have strong preference for this. But, do we have a reason to =
terminate connection?
>=20
> Thanks,
> --
> Yoshi
>=20
> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi,
>=20
> I have some points related to the  modifications (Change 2) being =
proposed on data sequence map. Please see them inline. Though I am =
putting forward the below points, if the consensus is in favour of the =
proposed change for reducing implementation complexity, I am also OK =
with that as well.=20
>=20
> From: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> To: multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> Sent: Thursday, January 2, 2020 4:21:32 AM
> Subject: [multipathtcp] RFC6824bis edits based on implementation =
feedback
>=20
> Hi all,
> We=E2=80=99d love to get this to a state of completion as soon as =
possible, and to this end I am starting a new thread on this topic. In =
discussion with the chairs, it is possible to make the desired changes =
in AUTH48 as long as there is WG consensus. The discussion so far has =
been fairly limited in terms of participation.
>=20
> I would ask the chairs please if it was possible to specify a time =
bound for this discussion and a default conclusion.
>=20
> Regarding the changes, in summary, there are two areas where changes =
have been requested by the implementation community. As we are the IETF =
we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so =
ease of implementing standards-compliant code is strongly desirable. =
However, we do not wish to reduce functionality agreed by the IETF =
community if it is considered a required feature by the community.
>=20
>=20
> Change 1
>=20
> Change the sentence reading:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).=20
>=20
> To:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data =
Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for the =
MP_CAPABLE (which is the first octet of the data sequence space).
>=20
> What this means:
>=20
> The current text is concerned only with ensuring a path is MPTCP =
capable, and so only cares that DSS option occurs on a data packet. =
However, the MP_CAPABLE option is defined to occupy the first octet of =
data sequence space and thus, if analogous to TCP, must be acknowledged. =
>=46rom an implementation point of view it would make sense not to have =
this hanging around forever and instead define it is acknowledged at the =
connection level as soon as received. This change ensures the first data =
packet also DATA_ACKs this MP_CAPABLE octet.
>=20
>=20
> Change 2
>=20
> Change the sentence reading:
>=20
>    A Data Sequence Mapping does not need to be included in every MPTCP =
packet, as long as the subflow sequence space in that packet is covered =
by a mapping known at the receiver.
>=20
> To:
>=20
>    The mapping provided by a Data Sequence Mapping MUST apply to some =
or all of the subflow sequence space in the TCP segment which carries =
the option. It does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.
>=20
> What this means:
>=20
> The current text does not place any restrictions on where a mapping =
could appear. In theory a sender could define a thousand different =
mappings up front, send them all, and expect a receiver to store this =
and reassemble data according to these mappings as it arrives. Indeed, =
this was never explicitly disallowed since it =E2=80=9Cmight have been =
useful=E2=80=9D. The implementation community, however, has expressed =
concerns over the difficulty of implementing this open-endedly. How many =
mappings is it reasonable to store? Is there a DoS risk here? Instead, =
it has been requested that thee specification restricts the placement of =
the DSS option to being within the subflow sequence space to which it =
applies.
>=20
> Below are my comments on this. I had shared some of these points in a =
previous thread that you had initiated in the same context.=20
>=20
> Transmitting large number of non-contiguous data sequence maps could =
be a misbehaviour (map-flooding), though it is not clear whether this =
can go to the extent of causing a potential DoS to the data receiver. So =
some sort of restriction on this could be useful.  One approach could be =
to insist that the data sender should ensure that the map being =
transmitted is for in-window data, as per the receiver advertised =
window. A receiver should anyhow be willing to store the maps for =
in-window data to deal with packet loss. For example, when a window of =
data segments (say 1 to 64) is transmitted, each carrying its =
corresponding map, and segment-1 is lost, the maps for the remaining 63 =
need to be stored till the lost segment is retransmitted. Of course, in =
this case the maps will be stored at the receiver side along with their =
corresponding data. But the need to store multiple maps for in-window =
data would still be there.
>=20
> The problem with the proposed change (restriction) is that a data =
sender may find it difficult, in case a need arise to slightly delay the =
map delivery by few segments, i.e., sending some data first without map, =
and then send the corresponding map in a later segment, as shown below:
>=20
> subflow-1:      segment-1                   segment-3                  =
  segment-4                       segment-7
>                       bytes:1-100                 bytes:201-300        =
      bytes:301-400                 bytes:601-700
>                       no map                        map for 1-100      =
        map for 201-400             map for 601-700
>=20
>=20
>=20
> subflow-2:       segment-2                  segment-5                  =
   segment-6                       segment-8
>                        bytes: 101-200           bytes:401-500          =
     bytes: 501-600                bytes:701-800  =20
>                        map for 101-200       map for 401-600           =
 no map                            map for 701-800
>=20
>=20
> In the above case, segment-1 goes without map and its map is included =
later in segment-3, the next data segment in the same subflow. Further,  =
in the above scheduling pattern, the map in segment-3 cannot cover the  =
data in segment-1 and segment-3, as some  data in between (segment-2) is =
transmitted through another subflow.  With the proposed change, the map =
in segment-3 will become invalid and this will eventually break =
subflow-1, though this could be a corner case..
>=20
> The question at this stage is why would segment-1 be transmitted =
without its map. In the case of bidirectional data transfer, there could =
be a need to pack both timestamp and SACK  options in a data segment, =
i.e., piggybacking of  SACK with data. If we consider that timestamp =
takes 12 bytes and SACK, even with single block,  takes another 10 =
bytes, the remaining 18 bytes option space is not adequate to carry data =
sequence signal with map, especially when DSN is 64 bit long. So the =
delivery of either of the two (SACK or map) would be delayed.
>=20
> As far as I understand, RFC 2018 (TCP Selective Acknowledgement =
Options) implies that SACK should not be delayed. It states "If sent at =
all, SACK options SHOULD be included in all ACKs which do not ACK the =
highest sequence number in the data receiver's queue". It also says "If =
data receiver generates SACK options under any circumstance, it SHOULD =
generate them under all permitted circumstances".   So, as part of =
meeting the RFC 2018 requirements, if the combination of SACK and =
timestamp is given preference over DSS, data segments could be =
transmitted without their map.=20
>=20
> Another case of delaying map could arise if the data sender prefers to =
send ADD_ADDR option, instead of map, in a data segment. It is nice that =
ADD_ADDR option can be delivered reliably in a pure ACK, but I think =
this is not the case with DSS at present.
>=20
> If we adopt the proposed change, I think it might also be helpful to =
spell out how the receiver is supposed to behave, if it gets maps not =
meeting the MUST condition in the proposed change.  For example =
termination of the subflow with MP_TCPRST option (section 3.6 in RFC =
6824-bis) with appropriate reason code and T flag value to intimate the =
data sender the cause for subflow termination. =20
>         =20
> With regards,
>=20
> Anil
>=20
> Please can members of the WG express whether they are happy with these =
changes, or concerned.
>=20
> Best regards,
> Alan
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


--Apple-Mail=_112EC709-E02F-48FE-8395-1ED071B40A97
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; line-break: after-white-space;" =
class=3D"">+MPTCP-upstreaming<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Feb =
11, 2020, at 1:05 AM, Yoshifumi Nishida &lt;<a =
href=3D"mailto:nsd.ietf@gmail.com" class=3D"">nsd.ietf@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"">Hi folks,</div><div class=3D"">I =
guess we might want to know the behavior of existing implementations =
such as linux.</div></div></div></blockquote><blockquote type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"">When an mptcp stack tries to send a data packet and find that =
there's no enough option space for data mapping, what it will =
do?</div></div></div></blockquote><div><br class=3D""></div><div>iOS, <a =
href=3D"http://multipath-tcp.org" =
class=3D"">multipath-tcp.org</a>&nbsp;and Linux 5.6 implementation all =
favor the DSS-option over any other option (except TCP Timestamps). And =
TCP Timestamps and DSS comfortably fit in the TCP =
option-space.</div><div><br class=3D""></div><div>If SACK-blocks should =
be added, we only add SACK-blocks up to the remaining space. SACK is =
anyways opportunistic as once there are more than 3 blocks they don't =
fit either.</div><div><br class=3D""></div><div><br =
class=3D""></div><div>Christoph</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"">Split the packet to create more option space?</div><div =
class=3D"">--<br class=3D""></div><div class=3D"">Yoshi</div><br =
class=3D""><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Thu, Feb 6, 2020 at 10:10 AM V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" class=3D"">anil@csir4pi.in</a>&gt; =
wrote:<br class=3D""></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div class=3D""><div class=3D""><div =
class=3D"">Hi Alan,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thank you for your reply. I have two points to clarify. =
Please see them in line.</div><div class=3D""><br class=3D""></div><hr =
id=3D"gmail-m_8773357439777081590zwchr" class=3D""><div =
class=3D""><blockquote style=3D"border-left-width: 2px; =
border-left-style: solid; border-left-color: rgb(16, 16, 255); =
margin-left: 5px; padding-left: 5px; font-weight: normal; font-style: =
normal; text-decoration: none; font-family: Helvetica, Arial, =
sans-serif; font-size: 12pt;" class=3D""><b class=3D"">From: </b>"Alan =
Ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" target=3D"_blank" =
class=3D"">alan.ford@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: =
</b>"V Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" =
target=3D"_blank" class=3D"">anil@csir4pi.in</a>&gt;jk&nbsp;<br =
class=3D""><b class=3D"">Cc: </b>"Yoshifumi Nishida" &lt;<a =
href=3D"mailto:nsd.ietf@gmail.com" target=3D"_blank" =
class=3D"">nsd.ietf@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b class=3D"">Sent:=
 </b>Thursday, February 6, 2020 2:49:29 AM<br class=3D""><b =
class=3D"">Subject: </b>Re: [multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></blockquote></div><div =
class=3D""><blockquote style=3D"border-left-width: 2px; =
border-left-style: solid; border-left-color: rgb(16, 16, 255); =
margin-left: 5px; padding-left: 5px; font-weight: normal; font-style: =
normal; text-decoration: none; font-family: Helvetica, Arial, =
sans-serif; font-size: 12pt;" class=3D"">Hi Anil,<div class=3D""><br =
class=3D""></div><div class=3D"">This would not be forbidden if the =
mapping was carried on a pure ACK with no data.</div></blockquote><div =
class=3D"">As far as I understand, delivery of DSM through pure ACK is =
not in the scope of the current draft. If we intend to do this, we may =
need an approach similar to the one proposed for delivery of ADD_ADDR =
option in pure ACK with reliability feature.&nbsp; So, packing DSM on =
pure ACK does not seem to be an option at this stage.</div><blockquote =
style=3D"border-left-width: 2px; border-left-style: solid; =
border-left-color: rgb(16, 16, 255); margin-left: 5px; padding-left: =
5px; font-weight: normal; font-style: normal; text-decoration: none; =
font-family: Helvetica, Arial, sans-serif; font-size: 12pt;" =
class=3D""><div class=3D""><br class=3D""></div><div class=3D"">I do see =
the point here: if a packet of 1000 bytes contains 500 bytes of one =
mapping and 500 bytes of another mapping, then only one DSM would appear =
on one packet, leaving the mapping for the second 500 bytes to be =
carried somewhere else - the only option being a pure ACK. But this kind =
of scenario would be extremely rare</div></blockquote><div class=3D"">Yes,=
 I do agree that the scenario you mentioned above would be extremely =
rare. In fact, I wonder whether such a situation (i.e., need to cover =
the bytes in a single packet with two different maps) would ever arise. =
Probably there might be some corner cases, which I don't get it rightly =
now.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">More =
importantly, the scenario that Yoshi and me are referring to is totally =
different: the one I had given as part of my comments in response to the =
proposed change 2. In this scenario, which you could see in the trailing =
mail, data segment-1 is transmitted without including its map, something =
which is permitted in the &nbsp;mptcp framework (6824 bis). I make this =
inference from the below text in 6824 bis:</div><div class=3D""><br =
class=3D""></div><div class=3D""> "...even if a mapping does not exist =
from the subflow space to the data- level space, the data SHOULD still =
be ACKed at the subflow (if it is in-window). This data cannot, however, =
be acknowledged at the data level (Section 3.3.2) because its data =
sequence numbers are unknown. Implementations MAY hold onto such =
unmapped data for a short while in the expectation that a mapping will =
arrive shortly." </div><div class=3D""><br class=3D""></div><div =
class=3D"">One option the data sender has at this stage is to include =
the map for data in segment-1, in segment-3 (please see the two-subflow =
example I gave in response to the change 2 you had proposed). But the =
proposed change does not permit this. What would happen to =
&nbsp;subflow-1 in this case ?</div><div class=3D""><br =
class=3D""></div><div class=3D"">With regards,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Anil &nbsp; &nbsp;</div><blockquote =
style=3D"border-left-width: 2px; border-left-style: solid; =
border-left-color: rgb(16, 16, 255); margin-left: 5px; padding-left: =
5px; font-weight: normal; font-style: normal; text-decoration: none; =
font-family: Helvetica, Arial, sans-serif; font-size: 12pt;" =
class=3D""><div class=3D"">and I would imagine any implementation would =
just split into two 500 byte segments each with the PSH flag set. I =
don=E2=80=99t think we need to spell this out in the spec =
however.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Regards,</div><div class=3D"">Alan<br class=3D""><div =
class=3D""><div class=3D""><br class=3D""><blockquote class=3D""><div =
class=3D"">On 5 Feb 2020, at 15:09, V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow noopener noreferrer" =
target=3D"_blank" class=3D"">anil@csir4pi.in</a>&gt; wrote:</div><div =
class=3D""><div class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
class=3D""><div style=3D"font-family:arial,helvetica,sans-serif" =
class=3D""><div class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
class=3D""><div style=3D"font-family:arial,helvetica,sans-serif" =
class=3D""><div class=3D"">Hi Yoshi,</div><br class=3D""><div =
class=3D"">Please see in line.</div><br class=3D""><hr =
id=3D"gmail-m_8773357439777081590zwchr" class=3D""><div class=3D""><b =
class=3D"">From: </b>"Yoshifumi Nishida" &lt;<a =
href=3D"mailto:nsd.ietf@gmail.com" rel=3D"nofollow noopener noreferrer" =
target=3D"_blank" class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b =
class=3D"">To: </b>"V Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" =
rel=3D"nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">anil@csir4pi.in</a>&gt;<br class=3D""><b class=3D"">Cc: =
</b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" rel=3D"nofollow=
 noopener noreferrer" target=3D"_blank" =
class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow noopener =
noreferrer" target=3D"_blank" class=3D"">multipathtcp@ietf.org</a>&gt;<br =
class=3D""><b class=3D"">Sent: </b>Tuesday, February 4, 2020 1:08:45 =
PM<br class=3D""><b class=3D"">Subject: </b>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<br class=3D""></div><br =
class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"">Hi Anil,</div><br =
class=3D""><div class=3D"">Thanks for pointing it out. I overlooked this =
one.</div><div class=3D"">This looks an interesting point.<br =
class=3D""></div><br class=3D""><div class=3D"">It seems to me that =
whether RST is happen or not depends on the size of receive window =
according to the text.<br class=3D""></div><div class=3D"">If the =
receive window size is big enough to accommodate&nbsp;segment 1 and =
segment 3, the text "<span style=3D"font-size:13.3333px" =
class=3D"">Implementations MAY hold onto such unmapped data for a short =
while in&nbsp;</span><span style=3D"font-size:13.3333px" class=3D"">the =
expectation that a mapping will arrive shortly. "&nbsp;</span>can be =
applied to the segment 1. As a result, the segment 1 won't be =
discarded.&nbsp;</div><br class=3D""><div class=3D""><em =
class=3D"">Yes.&nbsp; So, segment 1 may be kept in the data receiver's =
buffer in expectation that its mapping will arrive shortly. And in the =
example that we are referring to, the data sender will not be able to =
include the map for the data in segment 1 in segment 3 or any higher =
segment.</em></div><br class=3D""><div class=3D""><em =
class=3D"">Regards,</em></div><br class=3D""><div class=3D""><em =
class=3D"">Anil</em></div><br class=3D""><div class=3D"">However, this =
might be contradict with the new texts Alan proposed? Or, am I missing =
something?</div><br class=3D""><div class=3D"">Thanks,</div><div =
class=3D"">--</div><div class=3D"">Yoshi</div><br class=3D""><br =
class=3D""><br class=3D""><div class=3D""><div dir=3D"ltr" class=3D"">On =
Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div class=3D""><div =
class=3D""><div class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
class=3D"">Hi Yoshi,</div><br class=3D""><div class=3D"">Thanks for this =
point. In fact, I had initially not thought of a scenario, where the map =
is being delivered through a retransmitted data packet while its first =
transmission did not include the map. Now I am just seeing the document =
(RFC 6824-bis) in this context.</div><br class=3D""><div class=3D"">My =
understanding is that in scenarios like what I described in my previous =
mail, RST is likely to happen whether we explicitly state so or not. =
Please see the paragraph containing the below text in RFC 6824-bis. =
&nbsp;</div><br class=3D""><div class=3D"">"If a mapping for that =
subflow-level sequence space does not arrive within a receive window of =
data, that subflow SHOULD be treated as broken, closed with a RST, and =
any unmapped data silently discarded."</div><br class=3D""><div =
class=3D"">if we assume that the map is included while retransmitting =
the data (even though the first transmission did not contain the map for =
some reasons), &nbsp;we could argue that RST could be avoided provided =
that the retransmission is triggered within a receive window of data. =
But the question here would be how and when will the retransmission take =
place. In this case, the subflow may not initiate the retransmission of =
data by its own (i..e., no retransmission due to three duplicate ACKs or =
RTO expiry at subflow level) as there is no segment loss at subflow =
level sequence space. So there could be a high possibility of RST =
happening even before the map delivery through =
retransmission.&nbsp;</div><br class=3D""><div class=3D"">With =
regards,&nbsp;</div><br class=3D""><div class=3D"">Anil</div><div =
class=3D"">&nbsp;</div><hr =
id=3D"gmail-m_8773357439777081590gmail-m_218086596951724501gmail-m_2982267=
033577902985zwchr" class=3D""><div class=3D""><b class=3D"">From: =
</b>"Yoshifumi Nishida" &lt;<a href=3D"mailto:nsd.ietf@gmail.com" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: =
</b>"V Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">anil@csir4pi.in</a>&gt;<br class=3D""><b class=3D"">Cc: =
</b>"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b class=3D"">Sent:=
 </b>Saturday, February 1, 2020 3:39:51 AM<br class=3D""><b =
class=3D"">Subject: </b>Re: [multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></div><br class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"">Hi Anil,</div><br class=3D""><div =
class=3D"">I have a question about your proposed text.</div><div =
class=3D""><div class=3D"">I am actually wondering if we really want to =
terminate connection here.&nbsp;</div></div><br class=3D""><div =
class=3D"">The packets without proper mappings will be treated as =
invalid and will be discarded.&nbsp;</div><div class=3D"">If an =
implementation failed to attach proper mapping for some reasons (e.g. =
option space), it might be able to attach the proper one when it =
retransmits the packets. This also looks ok to me.</div><br =
class=3D""><div class=3D"">I don't have strong preference for this. But, =
do we have a reason to terminate connection?</div><br class=3D""><div =
class=3D"">Thanks,</div><div class=3D"">--<br class=3D""></div><div =
class=3D"">Yoshi</div><br class=3D""><div class=3D""><div dir=3D"ltr" =
class=3D"">On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div class=3D""><div =
class=3D""><div class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
class=3D""><span style=3D"font-size:12pt;line-height:1.3" =
class=3D"">Hi,</span><br class=3D""></div><div class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><div =
style=3D"font-family:arial,helvetica,sans-serif" class=3D""><br =
class=3D""><div class=3D"">I have some points related to the =
&nbsp;modifications (Change 2) being proposed on data sequence map. =
Please see them inline.&nbsp;<span =
style=3D"font-family:arial,helvetica,sans-serif;font-size:16px;font-style:=
normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transfor=
m:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,25=
5);float:none;display:inline" class=3D"">Though I am putting forward the =
below points, if the consensus is in favour of the proposed change for =
reducing implementation complexity, I am also OK with that as =
well.&nbsp;</span><br class=3D""></div><br class=3D""><hr =
id=3D"gmail-m_8773357439777081590gmail-m_218086596951724501gmail-m_2982267=
033577902985gmail-m_7687184382299596774zwchr" class=3D""><div =
class=3D""><b class=3D"">From: </b>"alan ford" &lt;<a =
href=3D"mailto:alan.ford@gmail.com" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">alan.ford@gmail.com</a>&gt;<br class=3D""><b class=3D"">To: =
</b><a href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><b class=3D"">Sent: =
</b>Thursday, January 2, 2020 4:21:32 AM<br class=3D""><b =
class=3D"">Subject: </b>[multipathtcp] RFC6824bis edits based on =
implementation feedback<br class=3D""></div><br class=3D""><div =
class=3D"">Hi all,<br class=3D""><div class=3D"">We=E2=80=99d love to =
get this to a state of completion as soon as possible, and to this end I =
am starting a new thread on this topic. In discussion with the chairs, =
it <i class=3D"">is </i>possible to make the desired changes in AUTH48 =
as long as there is WG consensus. The discussion so far has been fairly =
limited in terms of participation.</div><br class=3D""><div class=3D"">I =
would ask the chairs please if it was possible to specify a time bound =
for this discussion and a default conclusion.</div><br class=3D""><div =
class=3D"">Regarding the changes, in summary, there are two areas where =
changes have been requested by the implementation community. As we are =
the IETF we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D =
and so ease of implementing standards-compliant code is strongly =
desirable. However, we do not wish to reduce functionality agreed by the =
IETF community if it is considered a required feature by the =
community.</div><br class=3D""><br class=3D""><div class=3D""><b =
class=3D"">Change 1</b></div><div class=3D""><b class=3D""><br =
class=3D""></b></div><div class=3D"">Change the sentence reading:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B has data to =
send first, then the reliable delivery of the ACK + MP_CAPABLE can be =
inferred by the receipt of this data with an MPTCP Data Sequence Signal =
(DSS) option (Section 3.3).&nbsp;<br class=3D""></i><br class=3D"">To:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B has data to =
send first, then the reliable delivery of the ACK + MP_CAPABLE is =
ensured by the receipt of this data with an MPTCP Data Sequence Signal =
(DSS) option (Section 3.3) containing a DATA_ACK for the MP_CAPABLE =
(which is the first octet of the data sequence&nbsp;space).<br =
class=3D""></i><br class=3D""></div><div class=3D"">What this =
means:</div><br class=3D""><div class=3D"">The current text is concerned =
only with ensuring a path is MPTCP capable, and so only cares that DSS =
option occurs on a data packet. However, the MP_CAPABLE option is =
defined to occupy the first octet of data sequence space and thus, if =
analogous to TCP, must be acknowledged. &gt;=46rom an implementation =
point of view it would make sense not to have this hanging around =
forever and instead define it is acknowledged at the connection level as =
soon as received. This change ensures the first data packet also =
DATA_ACKs this MP_CAPABLE octet.</div><br class=3D""><br class=3D""><div =
class=3D""><b class=3D"">Change 2</b></div><div class=3D""><b =
class=3D""><br class=3D""></b></div><div class=3D"">Change the sentence =
reading:<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;A Data =
Sequence Mapping does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.</i><br class=3D""><br class=3D"">To:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;The mapping =
provided by a Data Sequence Mapping MUST apply to some or all of the =
subflow sequence space in the TCP segment which carries the option. It =
does not need to be included in every MPTCP packet, as long as the =
subflow sequence space in that packet is covered by a mapping known at =
the receiver.<br class=3D""></i><br class=3D"">What this means:</div><br =
class=3D""><div class=3D"">The current text does not place any =
restrictions on where a mapping could appear. In theory a sender could =
define a thousand different mappings up front, send them all, and expect =
a receiver to store this and reassemble data according to these mappings =
as it arrives. Indeed, this was never explicitly disallowed since it =
=E2=80=9Cmight have been useful=E2=80=9D. The implementation community, =
however, has expressed concerns over the difficulty of implementing this =
open-endedly. How many mappings is it reasonable to store? Is there a =
DoS risk here? Instead, it has been requested that thee specification =
restricts the placement of the DSS option to being within the subflow =
sequence space to which it applies.</div><br class=3D""><div =
class=3D"">Below are my comments on this. I had shared some of these =
points in a previous thread that you had initiated in the same =
context.&nbsp;</div><br class=3D""><div class=3D"">Transmitting large =
number of non-contiguous data sequence maps could be a misbehaviour =
(map-flooding), though it is not clear whether this can go to the extent =
of causing a potential DoS to the data receiver. So some sort of =
restriction on this could be useful.&nbsp; One approach could be to =
insist that the data sender should ensure that the map being transmitted =
is for in-window data, as per the receiver advertised window. A receiver =
should anyhow be willing to store the maps for in-window data to deal =
with packet loss. For example, when a window of data segments (say 1 to =
64) is transmitted, each carrying its corresponding map, and segment-1 =
is lost, the maps for the remaining 63 need to be stored till the lost =
segment is retransmitted. Of course, in this case the maps will be =
stored at the receiver side along with their corresponding data. But the =
need to store multiple maps for in-window data would still be =
there.</div><br class=3D""><div class=3D""><span =
style=3D"font-family:arial,helvetica,sans-serif;font-size:16px;font-style:=
normal;font-weight:normal;letter-spacing:normal;line-height:20.8px;text-in=
dent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:non=
e;background-color:rgb(255,255,255);display:inline" class=3D"">The =
problem with the proposed change (restriction) is that a data sender may =
find it difficult, in case a need arise to slightly delay the map =
delivery by few segments, i.e., sending some data first without map, and =
then send the corresponding map in a later segment, as shown =
below:</span><br class=3D""></div><br class=3D""><div class=3D""><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D"">subflow-1:&nbsp; &nbsp; &nbsp; segment-1&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; segment-3&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; segment-4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-7</span></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;bytes:1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; bytes:201-300 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;bytes:301-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; bytes:601-700</span></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;&nbsp;no map &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 1-100 &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 201-400 &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; map for 601-700</span></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D""><br class=3D""></span></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D""><br class=3D""></span></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><br class=3D""></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D"">subflow-2:&nbsp; &nbsp; &nbsp; &nbsp;segment-2&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-5 &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-6 &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
segment-8</span></div><div style=3D"font-family:&quot;segoe =
ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bytes: 101-200 &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; bytes:401-500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bytes: 501-600 &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;bytes:701-800&nbsp;&nbsp;&nbsp;</span></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><span lang=3D"EN-US" style=3D"font-size:10pt" =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;map for 101-200 &nbsp; &nbsp; &nbsp; map for =
401-600 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;no map &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;map for 701-800</span></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><br class=3D""></div><div =
style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida =
sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(=
255,255,255)" class=3D""><br class=3D""></div>In the above case, =
segment-1 goes without map and its map is included later in segment-3, =
the next data segment in the same subflow. Further, &nbsp;in the above =
scheduling pattern, the map in segment-3 cannot cover the &nbsp;data in =
segment-1 and segment-3, as some &nbsp;data in between (segment-2) is =
transmitted through another subflow.&nbsp; With the proposed change, the =
map in segment-3 will become invalid and this will eventually break =
subflow-1, though this could be a corner case..</div><br class=3D""><div =
class=3D"">The question at this stage is why would segment-1 be =
transmitted without its map. In the case of bidirectional data transfer, =
there could be a need to pack both timestamp and SACK &nbsp;options in a =
data segment, i.e., piggybacking of &nbsp;SACK with data. If we consider =
that timestamp takes 12 bytes and SACK, even with single block, =
&nbsp;takes another 10 bytes, the remaining 18 bytes option space is not =
adequate to carry data sequence signal with map, especially when DSN is =
64 bit long. So the delivery of either of the two (SACK or map) would be =
delayed.</div><br class=3D""><div class=3D"">As far as I understand, RFC =
2018 (TCP Selective Acknowledgement Options) implies that SACK should =
not be delayed. It states "If sent at all, SACK options SHOULD be =
included in all ACKs which do not ACK the highest sequence number in the =
data receiver's queue". It also says "If data receiver generates SACK =
options under any circumstance, it SHOULD generate them under all =
permitted circumstances". &nbsp; So, as part of meeting the RFC 2018 =
requirements, if the combination of SACK and timestamp is given =
preference over DSS, data segments could be transmitted without their =
map.&nbsp;</div><br class=3D""><div class=3D"">Another case of delaying =
map could arise if the data sender prefers to send ADD_ADDR option, =
instead of map, in a data segment. It is nice that ADD_ADDR option can =
be delivered reliably in a pure ACK, but I think this is not the case =
with DSS at present.</div><br class=3D""><div class=3D"">If we adopt the =
proposed change, I think it might also be helpful to spell out how the =
receiver is supposed to behave, if it gets maps not meeting the MUST =
condition in the proposed change.&nbsp; For example termination of the =
subflow with MP_TCPRST option (section 3.6 in RFC 6824-bis) with =
appropriate reason code and T flag value to intimate the data sender the =
cause for subflow termination.&nbsp;&nbsp;</div><div class=3D"">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;</div></div><div class=3D"">With =
regards,</div><br class=3D""><div class=3D"">Anil<br class=3D""><br =
class=3D""><div class=3D"">Please can members of the WG express whether =
they are happy with these changes, or concerned.</div><br class=3D""><div =
class=3D"">Best regards,</div><div class=3D"">Alan</div><br class=3D""><br=
 class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a></div></d=
iv></div></div></div></div></div></div></div></div><br =
class=3D""></div></div></div><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer=
%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer =
nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
rel=3D"noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener=
%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20n=
oreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noref=
errer nofollow noopener noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br =
class=3D""></blockquote></div></div></div></div></div></div><br =
class=3D""></div></div><br =
class=3D""></div></blockquote></div></div></div></div></div></div></div></=
div></div></div><br class=3D""></div></div><br class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""></div></div><br =
class=3D""></blockquote></div></div>
<br class=3D"">
<br class=3D""></div></blockquote></div></div>
_______________________________________________<br class=3D"">multipathtcp=
 mailing list<br class=3D""><a href=3D"mailto:multipathtcp@ietf.org" =
class=3D"">multipathtcp@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp<br =
class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_112EC709-E02F-48FE-8395-1ED071B40A97--


From nobody Tue Feb 11 14:53:58 2020
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C0B120827 for <multipathtcp@ietfa.amsl.com>; Tue, 11 Feb 2020 14:53:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 VZtCaLMfZUmF for <multipathtcp@ietfa.amsl.com>; Tue, 11 Feb 2020 14:53:50 -0800 (PST)
Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (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 6B0A2120826 for <multipathtcp@ietf.org>; Tue, 11 Feb 2020 14:53:50 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id 01BMg71V040363; Tue, 11 Feb 2020 14:53:31 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=KdPpdXWVDen/w6wdZXHGBlftEFhK1WKQvLQlx2HQHPw=; b=N4ObP4b1Wlin/mq88b8IhLfWN+0bzmHErsO1mgukg55I5dfu1dQgb+ZI6dTinat6MdkK LxUpM6yU6ogUhi6FtJyDMy+/FfctxO3XGcxF95MVilbqARml2eNgDb7QjcWzaK5A2vjE FVDRu1nqdmt1R09vuNYdHmRH2FzXTfTb7DRWg5+TZu7S12ozc6WrTbo3X2b+u8FaP5mB xd7tugyjhZyNQNsP2pTj0+bo9917/MexoED4DKsfMHts4Fo3Rr9zBuL9H7BMIMMxmae7 uBh06iHEG/KG0Kq8gMovaR9F8Jt1aTo68wHMrL0brpSzMGH3jNNJysT9PgKR2LbZjkLs PQ== 
Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 2y1vuyd5ae-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 11 Feb 2020 14:53:31 -0800
Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.1.20190704 64bit (built Jul  4 2019)) with ESMTPS id <0Q5K002DT7L6OJ70@rn-mailsvcp-mta-lapp01.rno.apple.com>;  Tue, 11 Feb 2020 14:53:30 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.1.20190704 64bit (built Jul  4 2019)) id <0Q5K00A007FET000@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Tue, 11 Feb 2020 14:53:30 -0800 (PST)
X-Va-A: 
X-Va-T-CD: 858e2f4dae29a6016c98c8320829244c
X-Va-E-CD: ae422271a38913bbedae93e9e9d60fc7
X-Va-R-CD: a5d4677ae470b25e3a5d2ab1ded2428a
X-Va-CD: 0
X-Va-ID: 356d31a9-9fab-4c53-b49e-ef9d29d6e586
X-V-A: 
X-V-T-CD: 858e2f4dae29a6016c98c8320829244c
X-V-E-CD: ae422271a38913bbedae93e9e9d60fc7
X-V-R-CD: a5d4677ae470b25e3a5d2ab1ded2428a
X-V-CD: 0
X-V-ID: c1daafe3-5cea-4d90-aaf2-f11fe5f34c0a
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-11_07:2020-02-11, 2020-02-11 signatures=0
Received: from [17.230.176.57] by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.1.20190704 64bit (built Jul  4 2019)) with ESMTPSA id <0Q5K00KSX7L58W20@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Tue, 11 Feb 2020 14:53:29 -0800 (PST)
Sender: cpaasch@apple.com
From: Christoph Paasch <cpaasch@apple.com>
Message-id: <57F3D993-F36D-4745-A0F4-860184F63D04@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_F9D41F18-A59F-415A-B386-155B07305FEF"
MIME-version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Date: Tue, 11 Feb 2020 14:53:29 -0800
In-reply-to: <LNXP123MB258719E5B3D9F99B7E715111EB180@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
Cc: V Anil Kumar <anil@csir4pi.in>, Alan Ford <alan.ford@gmail.com>, MultiPath TCP - IETF WG <multipathtcp@ietf.org>, mptcp Upstreaming <mptcp@lists.01.org>
To: Philip Eardley <philip.eardley@bt.com>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com> <1411057985.31281938.1581012439446@csir4pi.in> <LNXP123MB258719E5B3D9F99B7E715111EB180@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-02-11_07:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/sQe0IO_moeb9IY0p9hUPB6ap0-c>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2020 22:53:55 -0000

--Apple-Mail=_F9D41F18-A59F-415A-B386-155B07305FEF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

+MPTCP-Upstreaming

> On Feb 11, 2020, at 7:57 AM, philip.eardley@bt.com wrote:
>=20
> So coming back to Anil=E2=80=99s (original) question.
> =20
> A packet with timestamp and SACK options likely won=E2=80=99t have =
room for the DSS option, therefore the DSS mapping would be delayed. =
This may mean the transmitted segment is not covered by a DSS map. This =
would fail the MUST in Change 2 which (I think) means the subflow is =
closed immediately.

This packet should simply reduce the number of SACK-blocks so that the =
DSS-option fits in the TCP-option space. As I mentioned in my other =
mail, SACK is opportunistic in the sense that if there is a large number =
of holes in the sequence-number space today's TCP-option space =
limitation already limits this.

If we go along with this logic, we could argue that TCP-timestamps =
should be omitted in favor of even more SACK-blocks. And even then, 40 =
bytes might not be enough, so one might make the argument to move =
SACK-blocks to the TCP-payload ? (please, no! ;-) )

> Some options:
> It=E2=80=99s a rare case that we don=E2=80=99t need to worry about.

In my opinion it is rare and (AFAIK) there is no running code that =
implements sending or receiving early/late mappings.
Also, there is no data measuring the impact of this kind of =
traffic-pattern and by what percentage throughput/latency will improve =
when early/late mappings are allowed.

> Make Change 2 a SHOULD rather than a MUST

This means that all receivers MUST support receiving early/late mappings =
as they never know when a sender will follow the SHOULD or not. That =
means we have to clearly specify how the receiver stores these mappings, =
how many, how long,...

> Extend Change 2 so it says something like: The mapping provided by a =
Data Sequence Mapping MUST apply to some or all of the subflow sequence =
space in the TCP segment which carries the option [+ new text] or be =
covered by the next segment.  Or =E2=80=9Cwithin the next few =
segments=E2=80=9D

This would simplify some of the problems a receiver could have with late =
mappings.
Nevertheless, without any data as to the prevalence of the problem and =
the potential benefits of the solution my strong opinion is still to not =
allow this for the benefit of reduced implementation complexity.


Christoph

> ?
> =20
> For any of these, it would be worthwhile adding an explanatory note to =
Change 2.
> =20
> It would be really good if we could conclude on this.
> =20
> Personally I=E2=80=99d like something that reflects the consensus =
implicit in the implementations, but without anything other than rare =
corner cases.
> =20
> Thanks
> phil
> =20
> =20
> From: multipathtcp <multipathtcp-bounces@ietf.org =
<mailto:multipathtcp-bounces@ietf.org>> On Behalf Of V Anil Kumar
> Sent: 06 February 2020 18:07
> To: Alan Ford <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> Cc: multipathtcp <multipathtcp@ietf.org =
<mailto:multipathtcp@ietf.org>>
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> =20
> Hi Alan,
> =20
> Thank you for your reply. I have two points to clarify. Please see =
them in line.
> =20
> From: "Alan Ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>jk=20
> Cc: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>, "multipathtcp" <multipathtcp@ietf.org =
<mailto:multipathtcp@ietf.org>>
> Sent: Thursday, February 6, 2020 2:49:29 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> Hi Anil,
> =20
> This would not be forbidden if the mapping was carried on a pure ACK =
with no data.
> As far as I understand, delivery of DSM through pure ACK is not in the =
scope of the current draft. If we intend to do this, we may need an =
approach similar to the one proposed for delivery of ADD_ADDR option in =
pure ACK with reliability feature.  So, packing DSM on pure ACK does not =
seem to be an option at this stage.
> =20
> I do see the point here: if a packet of 1000 bytes contains 500 bytes =
of one mapping and 500 bytes of another mapping, then only one DSM would =
appear on one packet, leaving the mapping for the second 500 bytes to be =
carried somewhere else - the only option being a pure ACK. But this kind =
of scenario would be extremely rare
> Yes, I do agree that the scenario you mentioned above would be =
extremely rare. In fact, I wonder whether such a situation (i.e., need =
to cover the bytes in a single packet with two different maps) would =
ever arise. Probably there might be some corner cases, which I don't get =
it rightly now.=20
> =20
> More importantly, the scenario that Yoshi and me are referring to is =
totally different: the one I had given as part of my comments in =
response to the proposed change 2. In this scenario, which you could see =
in the trailing mail, data segment-1 is transmitted without including =
its map, something which is permitted in the  mptcp framework (6824 =
bis). I make this inference from the below text in 6824 bis:
> =20
> "...even if a mapping does not exist from the subflow space to the =
data- level space, the data SHOULD still be ACKed at the subflow (if it =
is in-window). This data cannot, however, be acknowledged at the data =
level (Section 3.3.2) because its data sequence numbers are unknown. =
Implementations MAY hold onto such unmapped data for a short while in =
the expectation that a mapping will arrive shortly."
> =20
> One option the data sender has at this stage is to include the map for =
data in segment-1, in segment-3 (please see the two-subflow example I =
gave in response to the change 2 you had proposed). But the proposed =
change does not permit this. What would happen to  subflow-1 in this =
case ?
> =20
> With regards,
> =20
> Anil   =20
> and I would imagine any implementation would just split into two 500 =
byte segments each with the PSH flag set. I don=E2=80=99t think we need =
to spell this out in the spec however.
> =20
> Regards,
> Alan
> =20
> On 5 Feb 2020, at 15:09, V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Yoshi,
> =20
> Please see in line.
> =20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, =
"multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> Sent: Tuesday, February 4, 2020 1:08:45 PM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> =20
> Hi Anil,
> =20
> Thanks for pointing it out. I overlooked this one.
> This looks an interesting point.
> =20
> It seems to me that whether RST is happen or not depends on the size =
of receive window according to the text.
> If the receive window size is big enough to accommodate segment 1 and =
segment 3, the text "Implementations MAY hold onto such unmapped data =
for a short while in the expectation that a mapping will arrive shortly. =
" can be applied to the segment 1. As a result, the segment 1 won't be =
discarded.=20
> =20
> Yes.  So, segment 1 may be kept in the data receiver's buffer in =
expectation that its mapping will arrive shortly. And in the example =
that we are referring to, the data sender will not be able to include =
the map for the data in segment 1 in segment 3 or any higher segment.
> =20
> Regards,
> =20
> Anil
> =20
> However, this might be contradict with the new texts Alan proposed? =
Or, am I missing something?
> =20
> Thanks,
> --
> Yoshi
>=20
>=20
>=20
> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Yoshi,
> =20
> Thanks for this point. In fact, I had initially not thought of a =
scenario, where the map is being delivered through a retransmitted data =
packet while its first transmission did not include the map. Now I am =
just seeing the document (RFC 6824-bis) in this context.
> =20
> My understanding is that in scenarios like what I described in my =
previous mail, RST is likely to happen whether we explicitly state so or =
not. Please see the paragraph containing the below text in RFC 6824-bis. =
=20
> =20
> "If a mapping for that subflow-level sequence space does not arrive =
within a receive window of data, that subflow SHOULD be treated as =
broken, closed with a RST, and any unmapped data silently discarded."
> =20
> if we assume that the map is included while retransmitting the data =
(even though the first transmission did not contain the map for some =
reasons),  we could argue that RST could be avoided provided that the =
retransmission is triggered within a receive window of data. But the =
question here would be how and when will the retransmission take place. =
In this case, the subflow may not initiate the retransmission of data by =
its own (i.e., no retransmission due to three duplicate ACKs or RTO =
expiry at subflow level) as there is no segment loss at subflow level =
sequence space. So there could be a high possibility of RST happening =
even before the map delivery through retransmission.=20
> =20
> With regards,=20
> =20
> Anil
> =20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, =
"multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> Sent: Saturday, February 1, 2020 3:39:51 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> =20
> Hi Anil,
> =20
> I have a question about your proposed text..
> I am actually wondering if we really want to terminate connection =
here.=20
> =20
> The packets without proper mappings will be treated as invalid and =
will be discarded.=20
> If an implementation failed to attach proper mapping for some reasons =
(e..g. option space), it might be able to attach the proper one when it =
retransmits the packets. This also looks ok to me.
> =20
> I don't have strong preference for this. But, do we have a reason to =
terminate connection?
> =20
> Thanks,
> --
> Yoshi
> =20
> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi,
> =20
> I have some points related to the  modifications (Change 2) being =
proposed on data sequence map. Please see them inline. Though I am =
putting forward the below points, if the consensus is in favour of the =
proposed change for reducing implementation complexity, I am also OK =
with that as well.=20
> =20
> From: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail..com>>
> To: multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> Sent: Thursday, January 2, 2020 4:21:32 AM
> Subject: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> =20
> Hi all,
> We=E2=80=99d love to get this to a state of completion as soon as =
possible, and to this end I am starting a new thread on this topic. In =
discussion with the chairs, it is possible to make the desired changes =
in AUTH48 as long as there is WG consensus. The discussion so far has =
been fairly limited in terms of participation.
> =20
> I would ask the chairs please if it was possible to specify a time =
bound for this discussion and a default conclusion.
> =20
> Regarding the changes, in summary, there are two areas where changes =
have been requested by the implementation community. As we are the IETF =
we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so =
ease of implementing standards-compliant code is strongly desirable. =
However, we do not wish to reduce functionality agreed by the IETF =
community if it is considered a required feature by the community.
> =20
>=20
> Change 1
> =20
> Change the sentence reading:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).=20
>=20
> To:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data =
Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for the =
MP_CAPABLE (which is the first octet of the data sequence space).
>=20
> What this means:
> =20
> The current text is concerned only with ensuring a path is MPTCP =
capable, and so only cares that DSS option occurs on a data packet. =
However, the MP_CAPABLE option is defined to occupy the first octet of =
data sequence space and thus, if analogous to TCP, must be acknowledged. =
>=46rom an implementation point of view it would make sense not to have =
this hanging around forever and instead define it is acknowledged at the =
connection level as soon as received. This change ensures the first data =
packet also DATA_ACKs this MP_CAPABLE octet.
> =20
>=20
> Change 2
> =20
> Change the sentence reading:
>=20
>    A Data Sequence Mapping does not need to be included in every MPTCP =
packet, as long as the subflow sequence space in that packet is covered =
by a mapping known at the receiver.
>=20
> To:
>=20
>    The mapping provided by a Data Sequence Mapping MUST apply to some =
or all of the subflow sequence space in the TCP segment which carries =
the option. It does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.
>=20
> What this means:
> =20
> The current text does not place any restrictions on where a mapping =
could appear. In theory a sender could define a thousand different =
mappings up front, send them all, and expect a receiver to store this =
and reassemble data according to these mappings as it arrives. Indeed, =
this was never explicitly disallowed since it =E2=80=9Cmight have been =
useful=E2=80=9D. The implementation community, however, has expressed =
concerns over the difficulty of implementing this open-endedly. How many =
mappings is it reasonable to store? Is there a DoS risk here? Instead, =
it has been requested that thee specification restricts the placement of =
the DSS option to being within the subflow sequence space to which it =
applies.
> =20
> Below are my comments on this. I had shared some of these points in a =
previous thread that you had initiated in the same context.=20
> =20
> Transmitting large number of non-contiguous data sequence maps could =
be a misbehaviour (map-flooding), though it is not clear whether this =
can go to the extent of causing a potential DoS to the data receiver. So =
some sort of restriction on this could be useful.  One approach could be =
to insist that the data sender should ensure that the map being =
transmitted is for in-window data, as per the receiver advertised =
window. A receiver should anyhow be willing to store the maps for =
in-window data to deal with packet loss. For example, when a window of =
data segments (say 1 to 64) is transmitted, each carrying its =
corresponding map, and segment-1 is lost, the maps for the remaining 63 =
need to be stored till the lost segment is retransmitted. Of course, in =
this case the maps will be stored at the receiver side along with their =
corresponding data. But the need to store multiple maps for in-window =
data would still be there.
> =20
> The problem with the proposed change (restriction) is that a data =
sender may find it difficult, in case a need arise to slightly delay the =
map delivery by few segments, i.e., sending some data first without map, =
and then send the corresponding map in a later segment, as shown below:
> =20
> subflow-1:      segment-1                   segment-3                  =
  segment-4                       segment-7
>                       bytes:1-100                 bytes:201-300        =
      bytes:301-400                 bytes:601-700
>                       no map                        map for 1-100      =
        map for 201-400             map for 601-700
>=20
>=20
>=20
>=20
> =20
> subflow-2:       segment-2                  segment-5                  =
   segment-6                       segment-8
>                        bytes: 101-200           bytes:401-500          =
     bytes: 501-600                bytes:701-800  =20
>                        map for 101-200       map for 401-600           =
 no map                            map for 701-800
> =20
> =20
> In the above case, segment-1 goes without map and its map is included =
later in segment-3, the next data segment in the same subflow. Further,  =
in the above scheduling pattern, the map in segment-3 cannot cover the  =
data in segment-1 and segment-3, as some  data in between (segment-2) is =
transmitted through another subflow.  With the proposed change, the map =
in segment-3 will become invalid and this will eventually break =
subflow-1, though this could be a corner case.
> =20
> The question at this stage is why would segment-1 be transmitted =
without its map. In the case of bidirectional data transfer, there could =
be a need to pack both timestamp and SACK  options in a data segment, =
i.e., piggybacking of  SACK with data. If we consider that timestamp =
takes 12 bytes and SACK, even with single block,  takes another 10 =
bytes, the remaining 18 bytes option space is not adequate to carry data =
sequence signal with map, especially when DSN is 64 bit long. So the =
delivery of either of the two (SACK or map) would be delayed.
> =20
> As far as I understand, RFC 2018 (TCP Selective Acknowledgement =
Options) implies that SACK should not be delayed. It states "If sent at =
all, SACK options SHOULD be included in all ACKs which do not ACK the =
highest sequence number in the data receiver's queue".. It also says "If =
data receiver generates SACK options under any circumstance, it SHOULD =
generate them under all permitted circumstances".   So, as part of =
meeting the RFC 2018 requirements, if the combination of SACK and =
timestamp is given preference over DSS, data segments could be =
transmitted without their map.=20
> =20
> Another case of delaying map could arise if the data sender prefers to =
send ADD_ADDR option, instead of map, in a data segment. It is nice that =
ADD_ADDR option can be delivered reliably in a pure ACK, but I think =
this is not the case with DSS at present.
> =20
> If we adopt the proposed change, I think it might also be helpful to =
spell out how the receiver is supposed to behave, if it gets maps not =
meeting the MUST condition in the proposed change.  For example =
termination of the subflow with MP_TCPRST option (section 3..6 in RFC =
6824-bis) with appropriate reason code and T flag value to intimate the =
data sender the cause for subflow termination. =20
>         =20
> With regards,
> =20
> Anil
>=20
> Please can members of the WG express whether they are happy with these =
changes, or concerned.
> =20
> Best regards,
> Alan
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf..org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
> =20
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
> =20
> =20
> =20
> =20
>=20
> =20
> =20
> =20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>

--Apple-Mail=_F9D41F18-A59F-415A-B386-155B07305FEF
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; line-break: after-white-space;" =
class=3D"">+MPTCP-Upstreaming<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Feb =
11, 2020, at 7:57 AM, <a href=3D"mailto:philip.eardley@bt.com" =
class=3D"">philip.eardley@bt.com</a> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; vertical-align: =
baseline;" class=3D""><span style=3D"font-family: Arial, sans-serif;" =
class=3D"">So coming back to Anil=E2=80=99s (original) question.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; vertical-align: =
baseline;" class=3D""><span style=3D"font-family: Arial, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
vertical-align: baseline;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">A packet with timestamp and SACK options likely =
won=E2=80=99t have room for the DSS option, therefore the DSS mapping =
would be delayed. This may mean the transmitted segment is not covered =
by a DSS map. This would fail the MUST in Change 2 which (I think) means =
the subflow is closed =
immediately.</span></div></div></div></blockquote><div><br =
class=3D""></div><div>This packet should simply reduce the number of =
SACK-blocks so that the DSS-option fits in the TCP-option space. As I =
mentioned in my other mail, SACK is opportunistic in the sense that if =
there is a large number of holes in the sequence-number space today's =
TCP-option space limitation already limits this.</div><div><br =
class=3D""></div><div>If we go along with this logic, we could argue =
that TCP-timestamps should be omitted in favor of even more SACK-blocks. =
And even then, 40 bytes might not be enough, so one might make the =
argument to move SACK-blocks to the TCP-payload ? (please, no! ;-) =
)</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; vertical-align: =
baseline;" class=3D""><span style=3D"font-family: Arial, sans-serif;" =
class=3D""><o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
vertical-align: baseline;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">Some options:<o:p =
class=3D""></o:p></span></div><ul type=3D"disc" style=3D"margin-bottom: =
0cm; margin-top: 0cm;" class=3D""><li class=3D"MsoListParagraph" =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; vertical-align: baseline;"><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">It=E2=80=99s a rare =
case that we don=E2=80=99t need to worry =
about.</span></li></ul></div></blockquote><div><br =
class=3D""></div><div>In my opinion it is rare and (AFAIK) there is no =
running code that implements sending or receiving early/late =
mappings.</div><div>Also, there is no data measuring the impact of this =
kind of traffic-pattern and by what percentage throughput/latency will =
improve when early/late mappings are allowed.</div><div><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><ul type=3D"disc" style=3D"margin-bottom: 0cm; =
margin-top: 0cm;" class=3D""><li class=3D"MsoListParagraph" =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; vertical-align: baseline;"><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">Make Change 2 a =
SHOULD rather than a =
MUST</span></li></ul></div></div></blockquote><div><br =
class=3D""></div><div>This means that all receivers MUST support =
receiving early/late mappings as they never know when a sender will =
follow the SHOULD or not. That means we have to clearly specify how the =
receiver stores these mappings, how many, how long,...</div><div><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><ul type=3D"disc" style=3D"margin-bottom: 0cm; =
margin-top: 0cm;" class=3D""><li class=3D"MsoListParagraph" =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; vertical-align: baseline;"><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">Extend Change 2 so =
it says something like:<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D"">The =
mapping provided by a Data Sequence Mapping MUST apply to some or all of =
the subflow sequence space in the TCP segment which carries the option =
[+ new text] or be covered by the next segment.&nbsp; Or =E2=80=9Cwithin =
the next few =
segments=E2=80=9D</span></li></ul></div></div></blockquote><div><br =
class=3D""></div><div>This would simplify some of the problems a =
receiver could have with late mappings.</div><div>Nevertheless, without =
any data as to the prevalence of the problem and the potential benefits =
of the solution my strong opinion is still to not allow this for the =
benefit of reduced implementation complexity.</div><div><br =
class=3D""></div><div><br class=3D""></div><div>Christoph</div><div><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><ul type=3D"disc" style=3D"margin-bottom: 0cm; =
margin-top: 0cm;" class=3D""><li class=3D"MsoListParagraph" =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; vertical-align: baseline;"><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">?</span><span =
style=3D"font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></li></ul><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
vertical-align: baseline;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; vertical-align: baseline;" class=3D""><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">For any of these, =
it would be worthwhile adding an explanatory note to Change 2.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; vertical-align: =
baseline;" class=3D""><span style=3D"font-family: Arial, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
vertical-align: baseline;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">It would be really good if we could conclude on =
this.<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
vertical-align: baseline;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; vertical-align: baseline;" class=3D""><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">Personally I=E2=80=99=
d like something that reflects the consensus implicit in the =
implementations, but without anything other than rare corner cases.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; vertical-align: =
baseline;" class=3D""><span style=3D"font-family: Arial, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
vertical-align: baseline;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">Thanks<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; vertical-align: baseline;" class=3D""><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">phil<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; vertical-align: =
baseline;" class=3D""><span style=3D"font-size: 7pt; font-family: Arial, =
sans-serif; color: rgb(127, 127, 127);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div><div class=3D""><div =
style=3D"border-style: solid none none; border-top-width: 1pt; =
border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;" =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><b class=3D""><span =
lang=3D"EN-US" class=3D"">From:</span></b><span lang=3D"EN-US" =
class=3D""><span class=3D"Apple-converted-space">&nbsp;</span>multipathtcp=
 &lt;<a href=3D"mailto:multipathtcp-bounces@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>V Anil Kumar<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>06 February 2020 18:07<br =
class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Alan Ford &lt;<a =
href=3D"mailto:alan.ford@gmail.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">alan.ford@gmail.com</a>&gt;<br =
class=3D""><b class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>multipathtcp &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">multipathtcp@ietf.org</a>&gt;<br =
class=3D""><b class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-family: =
Arial, sans-serif;" class=3D"">Hi Alan,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">Thank you for your reply. I have two points to =
clarify. Please see them in line.<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div></div><div class=3D"MsoNormal" =
align=3D"center" style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; text-align: center;"><span =
style=3D"font-family: Arial, sans-serif;" class=3D""><hr size=3D"2" =
width=3D"100%" align=3D"center" id=3D"zwchr" class=3D""></span></div><div =
class=3D""><blockquote style=3D"border-style: none none none solid; =
border-left-width: 1.5pt; border-left-color: rgb(16, 16, 255); padding: =
0cm 0cm 0cm 4pt; margin-left: 3.75pt; margin-top: 5pt; margin-bottom: =
5pt;" class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><b class=3D""><span =
style=3D"font-size: 12pt; font-family: Helvetica, sans-serif;" =
class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt; font-family: Helvetica, sans-serif;" =
class=3D"">"Alan Ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">alan.ford@gmail.com</a>&gt;<br class=3D""><b =
class=3D"">To:<span class=3D"Apple-converted-space">&nbsp;</span></b>"V =
Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">anil@csir4pi.in</a>&gt;jk&nbsp;<br class=3D""><b =
class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>"Yoshifumi Nishida" =
&lt;<a href=3D"mailto:nsd.ietf@gmail.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">nsd.ietf@gmail.com</a>&gt;, =
"multipathtcp" &lt;<a href=3D"mailto:multipathtcp@ietf.org" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b =
class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Thursday, February 6, =
2020 2:49:29 AM<br class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></blockquote></div><div =
class=3D""><blockquote style=3D"border-style: none none none solid; =
border-left-width: 1.5pt; border-left-color: rgb(16, 16, 255); padding: =
0cm 0cm 0cm 4pt; margin-left: 3.75pt; margin-top: 5pt; margin-bottom: =
5pt;" class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Helvetica, sans-serif;" =
class=3D"">Hi Anil,<o:p class=3D""></o:p></span></div><div class=3D""><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D"">This would not be =
forbidden if the mapping was carried on a pure ACK with no data.<o:p =
class=3D""></o:p></span></div></div></blockquote><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">As far as I understand, delivery of DSM through =
pure ACK is not in the scope of the current draft. If we intend to do =
this, we may need an approach similar to the one proposed for delivery =
of ADD_ADDR option in pure ACK with reliability feature. &nbsp;So, =
packing DSM on pure ACK does not seem to be an option at this stage.<o:p =
class=3D""></o:p></span></div></div><blockquote style=3D"border-style: =
none none none solid; border-left-width: 1.5pt; border-left-color: =
rgb(16, 16, 255); padding: 0cm 0cm 0cm 4pt; margin-left: 3.75pt; =
margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D"">I do see the point here: =
if a packet of 1000 bytes contains 500 bytes of one mapping and 500 =
bytes of another mapping, then only one DSM would appear on one packet, =
leaving the mapping for the second 500 bytes to be carried somewhere =
else - the only option being a pure ACK. But this kind of scenario would =
be extremely rare<o:p =
class=3D""></o:p></span></div></div></blockquote><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">Yes, I do agree that the scenario you mentioned =
above would be extremely rare. In fact, I wonder whether such a =
situation (i.e., need to cover the bytes in a single packet with two =
different maps) would ever arise. Probably there might be some corner =
cases, which I don't get it rightly now.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">More importantly, the scenario that Yoshi and me =
are referring to is totally different: the one I had given as part of my =
comments in response to the proposed change 2. In this scenario, which =
you could see in the trailing mail, data segment-1 is transmitted =
without including its map, something which is permitted in the =
&nbsp;mptcp framework (6824 bis). I make this inference from the below =
text in 6824 bis:<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-family: =
Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">"...even if a mapping does not exist from the =
subflow space to the data- level space, the data SHOULD still be ACKed =
at the subflow (if it is in-window). This data cannot, however, be =
acknowledged at the data level (Section 3.3.2) because its data sequence =
numbers are unknown. Implementations MAY hold onto such unmapped data =
for a short while in the expectation that a mapping will arrive =
shortly."<o:p class=3D""></o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">One option the data sender has at this stage is =
to include the map for data in segment-1, in segment-3 (please see the =
two-subflow example I gave in response to the change 2 you had =
proposed). But the proposed change does not permit this. What would =
happen to &nbsp;subflow-1 in this case ?<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">With regards,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">Anil &nbsp; &nbsp;<o:p =
class=3D""></o:p></span></div></div><blockquote style=3D"border-style: =
none none none solid; border-left-width: 1.5pt; border-left-color: =
rgb(16, 16, 255); padding: 0cm 0cm 0cm 4pt; margin-left: 3.75pt; =
margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D"">and I would imagine any =
implementation would just split into two 500 byte segments each with the =
PSH flag set. I don=E2=80=99t think we need to spell this out in the =
spec however.<o:p class=3D""></o:p></span></div></div><div class=3D""><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D"">Regards,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Helvetica, =
sans-serif;" class=3D"">Alan<o:p class=3D""></o:p></span></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Helvetica, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Helvetica, sans-serif;" class=3D"">On 5 Feb 2020, at =
15:09, V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Hi Yoshi,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Please see in =
line.<o:p class=3D""></o:p></span></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D"MsoNormal" align=3D"center" style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; text-align: =
center;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><hr size=3D"2" width=3D"100%" align=3D"center" =
id=3D"zwchr" class=3D""></span></div><div class=3D""><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D""><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">"Yoshifumi Nishida" &lt;<a href=3D"mailto:nsd.ietf@gmail.com" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To:<span=
 class=3D"Apple-converted-space">&nbsp;</span></b>"V Anil Kumar" &lt;<a =
href=3D"mailto:anil@csir4pi.in" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" class=3D"">anil@csir4pi.in</a>&gt;<br=
 class=3D""><b class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>"alan ford" &lt;<a =
href=3D"mailto:alan.ford@gmail.com" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b =
class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Tuesday, February 4, =
2020 1:08:45 PM<br class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Hi Anil,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Thanks for pointing it =
out. I overlooked this one.<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">This looks an =
interesting point.<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">It seems to me that whether RST is happen or not =
depends on the size of receive window according to the text.<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">If the receive window size is big enough to =
accommodate&nbsp;segment 1 and segment 3, the text "</span><span =
style=3D"font-size: 10pt; font-family: Arial, sans-serif;" =
class=3D"">Implementations MAY hold onto such unmapped data for a short =
while in&nbsp;the expectation that a mapping will arrive shortly. =
"&nbsp;</span><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">can be applied to the segment 1. As a result, =
the segment 1 won't be discarded.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><em class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D"">Yes.=
 &nbsp;So, segment 1 may be kept in the data receiver's buffer in =
expectation that its mapping will arrive shortly. And in the example =
that we are referring to, the data sender will not be able to include =
the map for the data in segment 1 in segment 3 or any higher =
segment.</span></em><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><em class=3D""><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D"">Regards,</span></em><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><em class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">Anil</span></em><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">However, this might be =
contradict with the new texts Alan proposed? Or, am I missing =
something?<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, 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: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">--<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Yoshi<o:p =
class=3D""></o:p></span></div></div><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></p><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">On Sun, Feb 2, 2020 at 8:42 =
AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" target=3D"_blank" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<o:p =
class=3D""></o:p></span></div></div><blockquote style=3D"border-style: =
none none none solid; border-left-width: 1pt; border-left-color: =
rgb(204, 204, 204); padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; =
margin-right: 0cm;" class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">Hi Yoshi,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Thanks for this point. =
In fact, I had initially not thought of a scenario, where the map is =
being delivered through a retransmitted data packet while its first =
transmission did not include the map. Now I am just seeing the document =
(RFC 6824-bis) in this context.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">My understanding is =
that in scenarios like what I described in my previous mail, RST is =
likely to happen whether we explicitly state so or not. Please see the =
paragraph containing the below text in RFC 6824-bis. &nbsp;<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">"If a mapping for that =
subflow-level sequence space does not arrive within a receive window of =
data, that subflow SHOULD be treated as broken, closed with a RST, and =
any unmapped data silently discarded."<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">if we assume that the =
map is included while retransmitting the data (even though the first =
transmission did not contain the map for some reasons), &nbsp;we could =
argue that RST could be avoided provided that the retransmission is =
triggered within a receive window of data. But the question here would =
be how and when will the retransmission take place. In this case, the =
subflow may not initiate the retransmission of data by its own (i.e., no =
retransmission due to three duplicate ACKs or RTO expiry at subflow =
level) as there is no segment loss at subflow level sequence space. So =
there could be a high possibility of RST happening even before the map =
delivery through retransmission.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">With =
regards,&nbsp;<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">Anil<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></span></div></div><div class=3D"MsoNormal" =
align=3D"center" style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; text-align: center;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><hr =
size=3D"2" width=3D"100%" align=3D"center" =
id=3D"gmail-m_218086596951724501gmail-m_2982267033577902985zwchr" =
class=3D""></span></div><div class=3D""><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D""><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">"Yoshifumi Nishida" &lt;<a href=3D"mailto:nsd.ietf@gmail.com" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To:<span=
 class=3D"Apple-converted-space">&nbsp;</span></b>"V Anil Kumar" &lt;<a =
href=3D"mailto:anil@csir4pi.in" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" class=3D"">anil@csir4pi.in</a>&gt;<br=
 class=3D""><b class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>"alan ford" &lt;<a =
href=3D"mailto:alan.ford@gmail.com" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b =
class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Saturday, February 1, =
2020 3:39:51 AM<br class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Hi Anil,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">I have a question =
about your proposed text..<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D"">I =
am actually wondering if we really want to terminate connection =
here.&nbsp;<o:p class=3D""></o:p></span></div></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">The packets without proper mappings will be =
treated as invalid and will be discarded.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">If an implementation failed to attach proper =
mapping for some reasons (e..g. option space), it might be able to =
attach the proper one when it retransmits the packets. This also looks =
ok to me.<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">I don't have strong =
preference for this. But, do we have a reason to terminate =
connection?<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, 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: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">--<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Yoshi<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D"">On =
Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" class=3D"">anil@csir4pi.in</a>&gt; =
wrote:<o:p class=3D""></o:p></span></div></div><blockquote =
style=3D"border-style: none none none solid; border-left-width: 1pt; =
border-left-color: rgb(204, 204, 204); padding: 0cm 0cm 0cm 6pt; =
margin-left: 4.8pt; margin-right: 0cm;" class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Hi,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">I have some points related to the =
&nbsp;modifications (Change 2) being proposed on data sequence map. =
Please see them inline.&nbsp;<span style=3D"background-color: white; =
background-position: initial initial; background-repeat: initial =
initial;" class=3D"">Though I am putting forward the below points, if =
the consensus is in favour of the proposed change for reducing =
implementation complexity, I am also OK with that as =
well.&nbsp;</span><o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"MsoNormal" =
align=3D"center" style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; text-align: center;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><hr =
size=3D"2" width=3D"100%" align=3D"center" =
id=3D"gmail-m_218086596951724501gmail-m_2982267033577902985gmail-m_7687184=
382299596774zwchr" class=3D""></span></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><b class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail..com" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">alan.ford@gmail.com</a>&gt;<br class=3D""><b =
class=3D"">To:<span class=3D"Apple-converted-space">&nbsp;</span></b><a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><b =
class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Thursday, January 2, =
2020 4:21:32 AM<br class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>[multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Hi all,<o:p =
class=3D""></o:p></span></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">We=E2=80=99d love to get this to a state of =
completion as soon as possible, and to this end I am starting a new =
thread on this topic. In discussion with the chairs, it<span =
class=3D"Apple-converted-space">&nbsp;</span><i class=3D"">is<span =
class=3D"Apple-converted-space">&nbsp;</span></i>possible to make the =
desired changes in AUTH48 as long as there is WG consensus. The =
discussion so far has been fairly limited in terms of participation.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">I would ask the chairs =
please if it was possible to specify a time bound for this discussion =
and a default conclusion.<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">Regarding the changes, in summary, there are two =
areas where changes have been requested by the implementation community. =
As we are the IETF we obviously have strong focus on =E2=80=9Crunning =
code=E2=80=9D and so ease of implementing standards-compliant code is =
strongly desirable. However, we do not wish to reduce functionality =
agreed by the IETF community if it is considered a required feature by =
the community.<o:p class=3D""></o:p></span></div></div><p =
class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></p><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D""><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D"">Change 1</span></b><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><p =
class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Change the sentence =
reading:<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B =
has data to send first, then the reliable delivery of the ACK + =
MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).&nbsp;<br =
class=3D""></i><br class=3D"">To:<br class=3D""><br class=3D""><i =
class=3D"">&nbsp; &nbsp;If B has data to send first, then the reliable =
delivery of the ACK + MP_CAPABLE is ensured by the receipt of this data =
with an MPTCP Data Sequence Signal (DSS) option (Section 3.3) containing =
a DATA_ACK for the MP_CAPABLE (which is the first octet of the data =
sequence&nbsp;space).</i><o:p class=3D""></o:p></span></p></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">What this means:<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">The current text is =
concerned only with ensuring a path is MPTCP capable, and so only cares =
that DSS option occurs on a data packet. However, the MP_CAPABLE option =
is defined to occupy the first octet of data sequence space and thus, if =
analogous to TCP, must be acknowledged. &gt;=46rom an implementation =
point of view it would make sense not to have this hanging around =
forever and instead define it is acknowledged at the connection level as =
soon as received. This change ensures the first data packet also =
DATA_ACKs this MP_CAPABLE octet.<o:p =
class=3D""></o:p></span></div></div><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></p><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><b class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">Change 2</span></b><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Change the sentence =
reading:<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;A Data =
Sequence Mapping does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.</i><br class=3D""><br class=3D"">To:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;The mapping =
provided by a Data Sequence Mapping MUST apply to some or all of the =
subflow sequence space in the TCP segment which carries the option. It =
does not need to be included in every MPTCP packet, as long as the =
subflow sequence space in that packet is covered by a mapping known at =
the receiver.<br class=3D""></i><br class=3D"">What this means:<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">The current text does =
not place any restrictions on where a mapping could appear. In theory a =
sender could define a thousand different mappings up front, send them =
all, and expect a receiver to store this and reassemble data according =
to these mappings as it arrives. Indeed, this was never explicitly =
disallowed since it =E2=80=9Cmight have been useful=E2=80=9D. The =
implementation community, however, has expressed concerns over the =
difficulty of implementing this open-endedly. How many mappings is it =
reasonable to store? Is there a DoS risk here? Instead, it has been =
requested that thee specification restricts the placement of the DSS =
option to being within the subflow sequence space to which it =
applies.<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Below are my comments =
on this. I had shared some of these points in a previous thread that you =
had initiated in the same context.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Transmitting large =
number of non-contiguous data sequence maps could be a misbehaviour =
(map-flooding), though it is not clear whether this can go to the extent =
of causing a potential DoS to the data receiver. So some sort of =
restriction on this could be useful.&nbsp; One approach could be to =
insist that the data sender should ensure that the map being transmitted =
is for in-window data, as per the receiver advertised window. A receiver =
should anyhow be willing to store the maps for in-window data to deal =
with packet loss. For example, when a window of data segments (say 1 to =
64) is transmitted, each carrying its corresponding map, and segment-1 =
is lost, the maps for the remaining 63 need to be stored till the lost =
segment is retransmitted. Of course, in this case the maps will be =
stored at the receiver side along with their corresponding data. But the =
need to store multiple maps for in-window data would still be there.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif; background-color: white;" =
class=3D"">The problem with the proposed change (restriction) is that a =
data sender may find it difficult, in case a need arise to slightly =
delay the map delivery by few segments, i.e., sending some data first =
without map, and then send the corresponding map in a later segment, as =
shown below:</span><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; background-color: white;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: &quot;Segoe =
UI&quot;, sans-serif;" class=3D"">subflow-1:&nbsp; &nbsp; &nbsp; =
segment-1&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; segment-3&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; segment-4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-7</span><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; background-color: white;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
&quot;Segoe UI&quot;, sans-serif;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;bytes:1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; bytes:201-300 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;bytes:301-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; bytes:601-700</span><span style=3D"font-size: 10.5pt; =
font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;no map &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 1-100 =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 201-400 &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; map for 601-700</span><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; background-color: white;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
&quot;Segoe UI&quot;, sans-serif;" class=3D""><br class=3D""><br =
class=3D""></span><span style=3D"font-size: 10.5pt; font-family: =
&quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><br class=3D""><br class=3D""></span><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; background-color: white;" =
class=3D""><span style=3D"font-size: 10.5pt; font-family: &quot;Segoe =
UI&quot;, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; background-color: white;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: &quot;Segoe =
UI&quot;, sans-serif;" class=3D"">subflow-2:&nbsp; &nbsp; &nbsp; =
&nbsp;segment-2&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; segment-5 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; segment-6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; segment-8</span><span style=3D"font-size: =
10.5pt; font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bytes: 101-200 &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; bytes:401-500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bytes: 501-600 &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;bytes:701-800&nbsp;&nbsp;&nbsp;</span><span style=3D"font-size: =
10.5pt; font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 101-200 &nbsp; &nbsp; &nbsp; =
map for 401-600 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;no map &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;map for 701-800</span><span style=3D"font-size: =
10.5pt; font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span style=3D"font-size: 10.5pt; =
font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; background-color: white;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">In the above case, segment-1 goes without map =
and its map is included later in segment-3, the next data segment in the =
same subflow. Further, &nbsp;in the above scheduling pattern, the map in =
segment-3 cannot cover the &nbsp;data in segment-1 and segment-3, as =
some &nbsp;data in between (segment-2) is transmitted through another =
subflow.&nbsp; With the proposed change, the map in segment-3 will =
become invalid and this will eventually break subflow-1, though this =
could be a corner case.<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">The question at this stage is why would =
segment-1 be transmitted without its map. In the case of bidirectional =
data transfer, there could be a need to pack both timestamp and SACK =
&nbsp;options in a data segment, i.e., piggybacking of &nbsp;SACK with =
data. If we consider that timestamp takes 12 bytes and SACK, even with =
single block, &nbsp;takes another 10 bytes, the remaining 18 bytes =
option space is not adequate to carry data sequence signal with map, =
especially when DSN is 64 bit long. So the delivery of either of the two =
(SACK or map) would be delayed.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">As far as I =
understand, RFC 2018 (TCP Selective Acknowledgement Options) implies =
that SACK should not be delayed. It states "If sent at all, SACK options =
SHOULD be included in all ACKs which do not ACK the highest sequence =
number in the data receiver's queue".. It also says "If data receiver =
generates SACK options under any circumstance, it SHOULD generate them =
under all permitted circumstances". &nbsp; So, as part of meeting the =
RFC 2018 requirements, if the combination of SACK and timestamp is given =
preference over DSS, data segments could be transmitted without their =
map.&nbsp;<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Another case of =
delaying map could arise if the data sender prefers to send ADD_ADDR =
option, instead of map, in a data segment. It is nice that ADD_ADDR =
option can be delivered reliably in a pure ACK, but I think this is not =
the case with DSS at present.<o:p class=3D""></o:p></span></div></div><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">If we adopt the proposed change, I think it =
might also be helpful to spell out how the receiver is supposed to =
behave, if it gets maps not meeting the MUST condition in the proposed =
change.&nbsp; For example termination of the subflow with MP_TCPRST =
option (section 3..6 in RFC 6824-bis) with appropriate reason code and T =
flag value to intimate the data sender the cause for subflow =
termination.&nbsp;&nbsp;<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<o:p class=3D""></o:p></span></div></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">With regards,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">Anil<o:p class=3D""></o:p></span></p><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Please can members of the WG =
express whether they are happy with these changes, or concerned.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Best regards,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">Alan<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf..org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><o:p =
class=3D""></o:p></span></div></div></div></div></div></div></div></div></=
div></div></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><o:p =
class=3D""></o:p></span></div></blockquote></div></div></div></div></div><=
/div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></blockquote></div></div></div><=
/div></div></div></div></div></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Helvetica, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></p></div></div></blockquote></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Helvetica, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></blockquote></div></div><p =
class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></p></div><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
13px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
13px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">multipathtcp mailing =
list</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 13px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><a href=3D"mailto:multipathtcp@ietf.org" style=3D"color:=
 purple; text-decoration: underline; font-family: Helvetica; font-size: =
13px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">multipathtcp@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
13px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
style=3D"color: purple; text-decoration: underline; font-family: =
Helvetica; font-size: 13px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a></div></b=
lockquote></div><br class=3D""></body></html>=

--Apple-Mail=_F9D41F18-A59F-415A-B386-155B07305FEF--


From nobody Thu Feb 13 01:34:48 2020
Return-Path: <nsd.ietf@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D25941200C4 for <multipathtcp@ietfa.amsl.com>; Thu, 13 Feb 2020 01:34:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 oYqLCq_3_OeE for <multipathtcp@ietfa.amsl.com>; Thu, 13 Feb 2020 01:34:42 -0800 (PST)
Received: from mail-vk1-xa2b.google.com (mail-vk1-xa2b.google.com [IPv6:2607:f8b0:4864:20::a2b]) (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 6A087120045 for <multipathtcp@ietf.org>; Thu, 13 Feb 2020 01:34:42 -0800 (PST)
Received: by mail-vk1-xa2b.google.com with SMTP id b69so1381089vke.9 for <multipathtcp@ietf.org>; Thu, 13 Feb 2020 01:34:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eaI3BXQgonA2WcQ7JZbmVxvqikLAkOu9AdH3DMeP0is=; b=oyCouM0/X1q83JDzTuxbR7SUkYUC2X/q6zAxBlTPPnSG/D1R6a8m3+eKCxPcj2fVuX oAV6SgZ2tkkeE9PbQKl+jMMqr14G5UrBrZK1D4prroxmEvayW+E8qse2DvYMmTBTYgst oa9pO6TcjU4/+F0jlgk3qXB4L2yuHQ5oc9lu4AfGiNNuEESVfpmL/lU3KQXPAI0UukLC oCxkbxbRRr+Kt9DvUHQR6EHwuskVeTEcVO6Y0GhQWTvCh3hne23SKx+0/wOPDjtjC+j9 JEbPHYtfQVcslMV3zYLVKmAidysHCmFz9S596zytFQy8FqWBVNiHXEfwphEUF0uP3oof It0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eaI3BXQgonA2WcQ7JZbmVxvqikLAkOu9AdH3DMeP0is=; b=Od7kWcN9gENLx6oA+H1LCHWtF44JNzn3mUNIKhJBIKLLnryrrlEaV/lyCCq+3C1WQP tNRwE5BwLOUBmmvfaqSMsIW66RyWHNP1dlgbprs2sbL1owroE/ZVvv65VHOcqDsQ+ofo 8a4XoyHAj5LeRK0WtknVRBwRLXellsrX0DfVoXMQzjrDaKQtg5cW2ilf1/7PXVe7cXhC Ub5sFR9LgITq1sMWcLP2AKfMMy89Jt6Hz6pniDCo2Q/mRwVlR8SHNoPi412OKANT+uit PCdO6Q5gdffZaE9mU8fcWxxkLy2Pyv609NBidmszU3yDP1CI5/aucFM+oCcVwbPCKd8K o+Ww==
X-Gm-Message-State: APjAAAXBa+LV+l60hgvUzcwRmFrrJBYfTZTXK7PM8Sf0cXwD7EUc0OUK nTrnmVpFy+i0zLcVLjRpxl2HaeKHkz5JJS7d6fA=
X-Google-Smtp-Source: APXvYqyWaNfRT8uCFGRiwMiET535Fg7ZvOoHwMtxj/CE/+Egkst7zDzDUPQ5d77M8jFT7wSMS6VIqPBe1Cs1JcceuFM=
X-Received: by 2002:a1f:94c1:: with SMTP id w184mr1511033vkd.43.1581586481336;  Thu, 13 Feb 2020 01:34:41 -0800 (PST)
MIME-Version: 1.0
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com> <1411057985.31281938.1581012439446@csir4pi.in> <CAAK044QoFh_eXE+MwggOn5X0uUs3xuzTcw2kdJaKuUnEP745dA@mail.gmail.com> <F3D07C9D-12B2-45A7-B9D0-23E862DDF4BA@apple.com>
In-Reply-To: <F3D07C9D-12B2-45A7-B9D0-23E862DDF4BA@apple.com>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Thu, 13 Feb 2020 01:34:29 -0800
Message-ID: <CAAK044SQb0utvjZToU=+OCg0hB-KX6vs1bFZGsJ=tJ5WvfETog@mail.gmail.com>
To: Christoph Paasch <cpaasch@apple.com>
Cc: V Anil Kumar <anil@csir4pi.in>, MultiPath TCP - IETF WG <multipathtcp@ietf.org>,  mptcp Upstreaming <mptcp@lists.01.org>
Content-Type: multipart/alternative; boundary="00000000000066d519059e71cc99"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/RELTrn9_89wejfVFcyZ439l8rmU>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2020 09:34:47 -0000

--00000000000066d519059e71cc99
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Christoph,

Thanks for the clarification. It seems that there are several ways to deal
with this situation.
I think these are not ideal, but at the same time, it won't be fatal. I
think more thorough solutions can be discussed in future versions.
Given that there're several ways to address it, I guess the draft doesn't
have to specify the behavior for this.
--
Yoshi

On Tue, Feb 11, 2020 at 2:30 PM Christoph Paasch <cpaasch@apple.com> wrote:

> +MPTCP-upstreaming
>
> On Feb 11, 2020, at 1:05 AM, Yoshifumi Nishida <nsd.ietf@gmail.com> wrote=
:
>
> Hi folks,
> I guess we might want to know the behavior of existing implementations
> such as linux.
>
> When an mptcp stack tries to send a data packet and find that there's no
> enough option space for data mapping, what it will do?
>
>
> iOS, multipath-tcp.org and Linux 5.6 implementation all favor the
> DSS-option over any other option (except TCP Timestamps). And TCP
> Timestamps and DSS comfortably fit in the TCP option-space.
>
> If SACK-blocks should be added, we only add SACK-blocks up to the
> remaining space. SACK is anyways opportunistic as once there are more tha=
n
> 3 blocks they don't fit either.
>
>
> Christoph
>
> Split the packet to create more option space?
> --
> Yoshi
>
> On Thu, Feb 6, 2020 at 10:10 AM V Anil Kumar <anil@csir4pi.in> wrote:
>
>> Hi Alan,
>>
>> Thank you for your reply. I have two points to clarify. Please see them
>> in line.
>>
>> ------------------------------
>>
>> *From: *"Alan Ford" <alan.ford@gmail.com>
>> *To: *"V Anil Kumar" <anil@csir4pi.in>jk
>> *Cc: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>, "multipathtcp" <
>> multipathtcp@ietf.org>
>> *Sent: *Thursday, February 6, 2020 2:49:29 AM
>> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation
>> feedback
>>
>> Hi Anil,
>>
>> This would not be forbidden if the mapping was carried on a pure ACK wit=
h
>> no data.
>>
>> As far as I understand, delivery of DSM through pure ACK is not in the
>> scope of the current draft. If we intend to do this, we may need an
>> approach similar to the one proposed for delivery of ADD_ADDR option in
>> pure ACK with reliability feature.  So, packing DSM on pure ACK does not
>> seem to be an option at this stage.
>>
>>
>> I do see the point here: if a packet of 1000 bytes contains 500 bytes of
>> one mapping and 500 bytes of another mapping, then only one DSM would
>> appear on one packet, leaving the mapping for the second 500 bytes to be
>> carried somewhere else - the only option being a pure ACK. But this kind=
 of
>> scenario would be extremely rare
>>
>> Yes, I do agree that the scenario you mentioned above would be extremely
>> rare. In fact, I wonder whether such a situation (i.e., need to cover th=
e
>> bytes in a single packet with two different maps) would ever arise.
>> Probably there might be some corner cases, which I don't get it rightly
>> now.
>>
>> More importantly, the scenario that Yoshi and me are referring to is
>> totally different: the one I had given as part of my comments in respons=
e
>> to the proposed change 2. In this scenario, which you could see in the
>> trailing mail, data segment-1 is transmitted without including its map,
>> something which is permitted in the  mptcp framework (6824 bis). I make
>> this inference from the below text in 6824 bis:
>>
>> "...even if a mapping does not exist from the subflow space to the data-
>> level space, the data SHOULD still be ACKed at the subflow (if it is
>> in-window). This data cannot, however, be acknowledged at the data level
>> (Section 3.3.2) because its data sequence numbers are unknown.
>> Implementations MAY hold onto such unmapped data for a short while in th=
e
>> expectation that a mapping will arrive shortly."
>>
>> One option the data sender has at this stage is to include the map for
>> data in segment-1, in segment-3 (please see the two-subflow example I ga=
ve
>> in response to the change 2 you had proposed). But the proposed change d=
oes
>> not permit this. What would happen to  subflow-1 in this case ?
>>
>> With regards,
>>
>> Anil
>>
>> and I would imagine any implementation would just split into two 500 byt=
e
>> segments each with the PSH flag set. I don=E2=80=99t think we need to sp=
ell this
>> out in the spec however.
>>
>> Regards,
>> Alan
>>
>> On 5 Feb 2020, at 15:09, V Anil Kumar <anil@csir4pi.in> wrote:
>> Hi Yoshi,
>>
>> Please see in line.
>>
>> ------------------------------
>> *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>
>> *To: *"V Anil Kumar" <anil@csir4pi.in>
>> *Cc: *"alan ford" <alan.ford@gmail.com>, "multipathtcp" <
>> multipathtcp@ietf.org>
>> *Sent: *Tuesday, February 4, 2020 1:08:45 PM
>> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation
>> feedback
>>
>> Hi Anil,
>>
>> Thanks for pointing it out. I overlooked this one.
>> This looks an interesting point.
>>
>> It seems to me that whether RST is happen or not depends on the size of
>> receive window according to the text.
>> If the receive window size is big enough to accommodate segment 1 and
>> segment 3, the text "Implementations MAY hold onto such unmapped data
>> for a short while in the expectation that a mapping will arrive shortly.
>> " can be applied to the segment 1. As a result, the segment 1 won't be
>> discarded.
>>
>> *Yes.  So, segment 1 may be kept in the data receiver's buffer in
>> expectation that its mapping will arrive shortly. And in the example tha=
t
>> we are referring to, the data sender will not be able to include the map
>> for the data in segment 1 in segment 3 or any higher segment.*
>>
>> *Regards,*
>>
>> *Anil*
>>
>> However, this might be contradict with the new texts Alan proposed? Or,
>> am I missing something?
>>
>> Thanks,
>> --
>> Yoshi
>>
>>
>>
>> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in> wrote:
>>
>>> Hi Yoshi,
>>>
>>> Thanks for this point. In fact, I had initially not thought of a
>>> scenario, where the map is being delivered through a retransmitted data
>>> packet while its first transmission did not include the map. Now I am j=
ust
>>> seeing the document (RFC 6824-bis) in this context.
>>>
>>> My understanding is that in scenarios like what I described in my
>>> previous mail, RST is likely to happen whether we explicitly state so o=
r
>>> not. Please see the paragraph containing the below text in RFC 6824-bis=
.
>>>
>>> "If a mapping for that subflow-level sequence space does not arrive
>>> within a receive window of data, that subflow SHOULD be treated as brok=
en,
>>> closed with a RST, and any unmapped data silently discarded."
>>>
>>> if we assume that the map is included while retransmitting the data
>>> (even though the first transmission did not contain the map for some
>>> reasons),  we could argue that RST could be avoided provided that the
>>> retransmission is triggered within a receive window of data. But the
>>> question here would be how and when will the retransmission take place.=
 In
>>> this case, the subflow may not initiate the retransmission of data by i=
ts
>>> own (i..e., no retransmission due to three duplicate ACKs or RTO expiry=
 at
>>> subflow level) as there is no segment loss at subflow level sequence sp=
ace.
>>> So there could be a high possibility of RST happening even before the m=
ap
>>> delivery through retransmission.
>>>
>>> With regards,
>>>
>>> Anil
>>>
>>> ------------------------------
>>> *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com>
>>> *To: *"V Anil Kumar" <anil@csir4pi.in>
>>> *Cc: *"alan ford" <alan.ford@gmail.com>, "multipathtcp" <
>>> multipathtcp@ietf.org>
>>> *Sent: *Saturday, February 1, 2020 3:39:51 AM
>>> *Subject: *Re: [multipathtcp] RFC6824bis edits based on implementation
>>> feedback
>>>
>>> Hi Anil,
>>>
>>> I have a question about your proposed text.
>>> I am actually wondering if we really want to terminate connection here.
>>>
>>> The packets without proper mappings will be treated as invalid and will
>>> be discarded.
>>> If an implementation failed to attach proper mapping for some reasons
>>> (e.g. option space), it might be able to attach the proper one when it
>>> retransmits the packets. This also looks ok to me.
>>>
>>> I don't have strong preference for this. But, do we have a reason to
>>> terminate connection?
>>>
>>> Thanks,
>>> --
>>> Yoshi
>>>
>>> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have some points related to the  modifications (Change 2) being
>>>> proposed on data sequence map. Please see them inline. Though I am
>>>> putting forward the below points, if the consensus is in favour of the
>>>> proposed change for reducing implementation complexity, I am also OK w=
ith
>>>> that as well.
>>>>
>>>> ------------------------------
>>>> *From: *"alan ford" <alan.ford@gmail.com>
>>>> *To: *multipathtcp@ietf.org
>>>> *Sent: *Thursday, January 2, 2020 4:21:32 AM
>>>> *Subject: *[multipathtcp] RFC6824bis edits based on implementation
>>>> feedback
>>>>
>>>> Hi all,
>>>> We=E2=80=99d love to get this to a state of completion as soon as poss=
ible, and
>>>> to this end I am starting a new thread on this topic. In discussion wi=
th
>>>> the chairs, it *is *possible to make the desired changes in AUTH48 as
>>>> long as there is WG consensus. The discussion so far has been fairly
>>>> limited in terms of participation.
>>>>
>>>> I would ask the chairs please if it was possible to specify a time
>>>> bound for this discussion and a default conclusion.
>>>>
>>>> Regarding the changes, in summary, there are two areas where changes
>>>> have been requested by the implementation community. As we are the IET=
F we
>>>> obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so e=
ase of implementing
>>>> standards-compliant code is strongly desirable. However, we do not wis=
h to
>>>> reduce functionality agreed by the IETF community if it is considered =
a
>>>> required feature by the community.
>>>>
>>>>
>>>> *Change 1*
>>>>
>>>> Change the sentence reading:
>>>>
>>>>
>>>> *   If B has data to send first, then the reliable delivery of the ACK
>>>> + MP_CAPABLE can be inferred by the receipt of this data with an MPTCP=
 Data
>>>> Sequence Signal (DSS) option (Section 3.3). *
>>>> To:
>>>>
>>>>
>>>> *   If B has data to send first, then the reliable delivery of the ACK
>>>> + MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data
>>>> Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for t=
he
>>>> MP_CAPABLE (which is the first octet of the data sequence space).*
>>>> What this means:
>>>>
>>>> The current text is concerned only with ensuring a path is MPTCP
>>>> capable, and so only cares that DSS option occurs on a data packet.
>>>> However, the MP_CAPABLE option is defined to occupy the first octet of=
 data
>>>> sequence space and thus, if analogous to TCP, must be acknowledged. >F=
rom
>>>> an implementation point of view it would make sense not to have this
>>>> hanging around forever and instead define it is acknowledged at the
>>>> connection level as soon as received. This change ensures the first da=
ta
>>>> packet also DATA_ACKs this MP_CAPABLE octet.
>>>>
>>>>
>>>> *Change 2*
>>>>
>>>> Change the sentence reading:
>>>>
>>>> *   A Data Sequence Mapping does not need to be included in every MPTC=
P
>>>> packet, as long as the subflow sequence space in that packet is covere=
d by
>>>> a mapping known at the receiver.*
>>>>
>>>> To:
>>>>
>>>>
>>>> *   The mapping provided by a Data Sequence Mapping MUST apply to some
>>>> or all of the subflow sequence space in the TCP segment which carries =
the
>>>> option. It does not need to be included in every MPTCP packet, as long=
 as
>>>> the subflow sequence space in that packet is covered by a mapping know=
n at
>>>> the receiver.*
>>>> What this means:
>>>>
>>>> The current text does not place any restrictions on where a mapping
>>>> could appear. In theory a sender could define a thousand different map=
pings
>>>> up front, send them all, and expect a receiver to store this and reass=
emble
>>>> data according to these mappings as it arrives. Indeed, this was never
>>>> explicitly disallowed since it =E2=80=9Cmight have been useful=E2=80=
=9D. The implementation
>>>> community, however, has expressed concerns over the difficulty of
>>>> implementing this open-endedly. How many mappings is it reasonable to
>>>> store? Is there a DoS risk here? Instead, it has been requested that t=
hee
>>>> specification restricts the placement of the DSS option to being withi=
n the
>>>> subflow sequence space to which it applies.
>>>>
>>>> Below are my comments on this. I had shared some of these points in a
>>>> previous thread that you had initiated in the same context.
>>>>
>>>> Transmitting large number of non-contiguous data sequence maps could b=
e
>>>> a misbehaviour (map-flooding), though it is not clear whether this can=
 go
>>>> to the extent of causing a potential DoS to the data receiver. So some=
 sort
>>>> of restriction on this could be useful.  One approach could be to insi=
st
>>>> that the data sender should ensure that the map being transmitted is f=
or
>>>> in-window data, as per the receiver advertised window. A receiver shou=
ld
>>>> anyhow be willing to store the maps for in-window data to deal with pa=
cket
>>>> loss. For example, when a window of data segments (say 1 to 64) is
>>>> transmitted, each carrying its corresponding map, and segment-1 is los=
t,
>>>> the maps for the remaining 63 need to be stored till the lost segment =
is
>>>> retransmitted. Of course, in this case the maps will be stored at the
>>>> receiver side along with their corresponding data. But the need to sto=
re
>>>> multiple maps for in-window data would still be there.
>>>>
>>>> The problem with the proposed change (restriction) is that a data
>>>> sender may find it difficult, in case a need arise to slightly delay t=
he
>>>> map delivery by few segments, i.e., sending some data first without ma=
p,
>>>> and then send the corresponding map in a later segment, as shown below=
:
>>>>
>>>> subflow-1:      segment-1                   segment-3
>>>>   segment-4                       segment-7
>>>>                       bytes:1-100                 bytes:201-300
>>>>      bytes:301-400                 bytes:601-700
>>>>                       no map                        map for 1-100
>>>>        map for 201-400             map for 601-700
>>>>
>>>>
>>>>
>>>> subflow-2:       segment-2                  segment-5
>>>>   segment-6                       segment-8
>>>>                        bytes: 101-200           bytes:401-500
>>>>         bytes: 501-600                bytes:701-800
>>>>                        map for 101-200       map for 401-600
>>>>  no map                            map for 701-800
>>>>
>>>>
>>>> In the above case, segment-1 goes without map and its map is included
>>>> later in segment-3, the next data segment in the same subflow. Further=
,  in
>>>> the above scheduling pattern, the map in segment-3 cannot cover the  d=
ata
>>>> in segment-1 and segment-3, as some  data in between (segment-2) is
>>>> transmitted through another subflow.  With the proposed change, the ma=
p in
>>>> segment-3 will become invalid and this will eventually break subflow-1=
,
>>>> though this could be a corner case..
>>>>
>>>> The question at this stage is why would segment-1 be transmitted
>>>> without its map. In the case of bidirectional data transfer, there cou=
ld be
>>>> a need to pack both timestamp and SACK  options in a data segment, i.e=
.,
>>>> piggybacking of  SACK with data. If we consider that timestamp takes 1=
2
>>>> bytes and SACK, even with single block,  takes another 10 bytes, the
>>>> remaining 18 bytes option space is not adequate to carry data sequence
>>>> signal with map, especially when DSN is 64 bit long. So the delivery o=
f
>>>> either of the two (SACK or map) would be delayed.
>>>>
>>>> As far as I understand, RFC 2018 (TCP Selective Acknowledgement
>>>> Options) implies that SACK should not be delayed. It states "If sent a=
t
>>>> all, SACK options SHOULD be included in all ACKs which do not ACK the
>>>> highest sequence number in the data receiver's queue". It also says "I=
f
>>>> data receiver generates SACK options under any circumstance, it SHOULD
>>>> generate them under all permitted circumstances".   So, as part of mee=
ting
>>>> the RFC 2018 requirements, if the combination of SACK and timestamp is
>>>> given preference over DSS, data segments could be transmitted without =
their
>>>> map.
>>>>
>>>> Another case of delaying map could arise if the data sender prefers to
>>>> send ADD_ADDR option, instead of map, in a data segment. It is nice th=
at
>>>> ADD_ADDR option can be delivered reliably in a pure ACK, but I think t=
his
>>>> is not the case with DSS at present.
>>>>
>>>> If we adopt the proposed change, I think it might also be helpful to
>>>> spell out how the receiver is supposed to behave, if it gets maps not
>>>> meeting the MUST condition in the proposed change.  For example termin=
ation
>>>> of the subflow with MP_TCPRST option (section 3.6 in RFC 6824-bis) wit=
h
>>>> appropriate reason code and T flag value to intimate the data sender t=
he
>>>> cause for subflow termination.
>>>>
>>>> With regards,
>>>>
>>>> Anil
>>>>
>>>> Please can members of the WG express whether they are happy with these
>>>> changes, or concerned.
>>>>
>>>> Best regards,
>>>> Alan
>>>>
>>>>
>>>> _______________________________________________
>>>> multipathtcp mailing list
>>>> multipathtcp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> multipathtcp mailing list
>>>> multipathtcp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi Christoph,<br></div><div dir=3D"ltr"><=
br></div><div>Thanks for the clarification. It seems that there are several=
 ways to deal with this situation.=C2=A0</div><div>I think these are not id=
eal, but at the same time, it won&#39;t be fatal. I think more thorough sol=
utions can be discussed in future versions.=C2=A0</div><div>Given that ther=
e&#39;re several ways to address it, I guess the draft doesn&#39;t have to =
specify the behavior for this.=C2=A0</div><div>--</div><div>Yoshi</div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Fe=
b 11, 2020 at 2:30 PM Christoph Paasch &lt;<a href=3D"mailto:cpaasch@apple.=
com">cpaasch@apple.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div style=3D"overflow-wrap: break-word;">+MPTCP-upst=
reaming<br><div><br><blockquote type=3D"cite"><div>On Feb 11, 2020, at 1:05=
 AM, Yoshifumi Nishida &lt;<a href=3D"mailto:nsd.ietf@gmail.com" target=3D"=
_blank">nsd.ietf@gmail.com</a>&gt; wrote:</div><br><div><div dir=3D"ltr"><d=
iv>Hi folks,</div><div>I guess we might want to know the behavior of existi=
ng implementations such as linux.</div></div></div></blockquote><blockquote=
 type=3D"cite"><div><div dir=3D"ltr"><div>When an mptcp stack tries to send=
 a data packet and find that there&#39;s no enough option space for data ma=
pping, what it will do?</div></div></div></blockquote><div><br></div><div>i=
OS, <a href=3D"http://multipath-tcp.org" target=3D"_blank">multipath-tcp.or=
g</a>=C2=A0and Linux 5.6 implementation all favor the DSS-option over any o=
ther option (except TCP Timestamps). And TCP Timestamps and DSS comfortably=
 fit in the TCP option-space.</div><div><br></div><div>If SACK-blocks shoul=
d be added, we only add SACK-blocks up to the remaining space. SACK is anyw=
ays opportunistic as once there are more than 3 blocks they don&#39;t fit e=
ither.</div><div><br></div><div><br></div><div>Christoph</div><br><blockquo=
te type=3D"cite"><div><div dir=3D"ltr"><div>Split the packet to create more=
 option space?</div><div>--<br></div><div>Yoshi</div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 6, 2020 at 10:10=
 AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" target=3D"_blank">a=
nil@csir4pi.in</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div><div><div>Hi Alan,</div><div><br></div><div>Thank you fo=
r your reply. I have two points to clarify. Please see them in line.</div><=
div><br></div><hr id=3D"gmail-m_-540654355673772201gmail-m_8773357439777081=
590zwchr"><div><blockquote style=3D"border-left:2px solid rgb(16,16,255);ma=
rgin-left:5px;padding-left:5px;font-weight:normal;font-style:normal;text-de=
coration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>Fro=
m: </b>&quot;Alan Ford&quot; &lt;<a href=3D"mailto:alan.ford@gmail.com" tar=
get=3D"_blank">alan.ford@gmail.com</a>&gt;<br><b>To: </b>&quot;V Anil Kumar=
&quot; &lt;<a href=3D"mailto:anil@csir4pi.in" target=3D"_blank">anil@csir4p=
i.in</a>&gt;jk=C2=A0<br><b>Cc: </b>&quot;Yoshifumi Nishida&quot; &lt;<a hre=
f=3D"mailto:nsd.ietf@gmail.com" target=3D"_blank">nsd.ietf@gmail.com</a>&gt=
;, &quot;multipathtcp&quot; &lt;<a href=3D"mailto:multipathtcp@ietf.org" ta=
rget=3D"_blank">multipathtcp@ietf.org</a>&gt;<br><b>Sent: </b>Thursday, Feb=
ruary 6, 2020 2:49:29 AM<br><b>Subject: </b>Re: [multipathtcp] RFC6824bis e=
dits based on implementation feedback<br></blockquote></div><div><blockquot=
e style=3D"border-left:2px solid rgb(16,16,255);margin-left:5px;padding-lef=
t:5px;font-weight:normal;font-style:normal;text-decoration:none;font-family=
:Helvetica,Arial,sans-serif;font-size:12pt">Hi Anil,<div><br></div><div>Thi=
s would not be forbidden if the mapping was carried on a pure ACK with no d=
ata.</div></blockquote><div>As far as I understand, delivery of DSM through=
 pure ACK is not in the scope of the current draft. If we intend to do this=
, we may need an approach similar to the one proposed for delivery of ADD_A=
DDR option in pure ACK with reliability feature.=C2=A0 So, packing DSM on p=
ure ACK does not seem to be an option at this stage.</div><blockquote style=
=3D"border-left:2px solid rgb(16,16,255);margin-left:5px;padding-left:5px;f=
ont-weight:normal;font-style:normal;text-decoration:none;font-family:Helvet=
ica,Arial,sans-serif;font-size:12pt"><div><br></div><div>I do see the point=
 here: if a packet of 1000 bytes contains 500 bytes of one mapping and 500 =
bytes of another mapping, then only one DSM would appear on one packet, lea=
ving the mapping for the second 500 bytes to be carried somewhere else - th=
e only option being a pure ACK. But this kind of scenario would be extremel=
y rare</div></blockquote><div>Yes, I do agree that the scenario you mention=
ed above would be extremely rare. In fact, I wonder whether such a situatio=
n (i.e., need to cover the bytes in a single packet with two different maps=
) would ever arise. Probably there might be some corner cases, which I don&=
#39;t get it rightly now.=C2=A0</div><div><br></div><div>More importantly, =
the scenario that Yoshi and me are referring to is totally different: the o=
ne I had given as part of my comments in response to the proposed change 2.=
 In this scenario, which you could see in the trailing mail, data segment-1=
 is transmitted without including its map, something which is permitted in =
the =C2=A0mptcp framework (6824 bis). I make this inference from the below =
text in 6824 bis:</div><div><br></div><div> &quot;...even if a mapping does=
 not exist from the subflow space to the data- level space, the data SHOULD=
 still be ACKed at the subflow (if it is in-window). This data cannot, howe=
ver, be acknowledged at the data level (Section 3.3.2) because its data seq=
uence numbers are unknown. Implementations MAY hold onto such unmapped data=
 for a short while in the expectation that a mapping will arrive shortly.&q=
uot; </div><div><br></div><div>One option the data sender has at this stage=
 is to include the map for data in segment-1, in segment-3 (please see the =
two-subflow example I gave in response to the change 2 you had proposed). B=
ut the proposed change does not permit this. What would happen to =C2=A0sub=
flow-1 in this case ?</div><div><br></div><div>With regards,</div><div><br>=
</div><div>Anil =C2=A0 =C2=A0</div><blockquote style=3D"border-left:2px sol=
id rgb(16,16,255);margin-left:5px;padding-left:5px;font-weight:normal;font-=
style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;fo=
nt-size:12pt"><div>and I would imagine any implementation would just split =
into two 500 byte segments each with the PSH flag set. I don=E2=80=99t thin=
k we need to spell this out in the spec however.</div><div><br></div><div>R=
egards,</div><div>Alan<br><div><div><br><blockquote><div>On 5 Feb 2020, at =
15:09, V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"nofollow =
noopener noreferrer" target=3D"_blank">anil@csir4pi.in</a>&gt; wrote:</div>=
<div><div><div style=3D"font-family:arial,helvetica,sans-serif"><div><div s=
tyle=3D"font-family:arial,helvetica,sans-serif"><div><div style=3D"font-fam=
ily:arial,helvetica,sans-serif"><div><div style=3D"font-family:arial,helvet=
ica,sans-serif"><div>Hi Yoshi,</div><br><div>Please see in line.</div><br><=
hr id=3D"gmail-m_-540654355673772201gmail-m_8773357439777081590zwchr"><div>=
<b>From: </b>&quot;Yoshifumi Nishida&quot; &lt;<a href=3D"mailto:nsd.ietf@g=
mail.com" rel=3D"nofollow noopener noreferrer" target=3D"_blank">nsd.ietf@g=
mail.com</a>&gt;<br><b>To: </b>&quot;V Anil Kumar&quot; &lt;<a href=3D"mail=
to:anil@csir4pi.in" rel=3D"nofollow noopener noreferrer" target=3D"_blank">=
anil@csir4pi.in</a>&gt;<br><b>Cc: </b>&quot;alan ford&quot; &lt;<a href=3D"=
mailto:alan.ford@gmail.com" rel=3D"nofollow noopener noreferrer" target=3D"=
_blank">alan.ford@gmail.com</a>&gt;, &quot;multipathtcp&quot; &lt;<a href=
=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow noopener noreferrer" targ=
et=3D"_blank">multipathtcp@ietf.org</a>&gt;<br><b>Sent: </b>Tuesday, Februa=
ry 4, 2020 1:08:45 PM<br><b>Subject: </b>Re: [multipathtcp] RFC6824bis edit=
s based on implementation feedback<br></div><br><div><div dir=3D"ltr"><div =
dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</div><br><div>Thanks for pointin=
g it out. I overlooked this one.</div><div>This looks an interesting point.=
<br></div><br><div>It seems to me that whether RST is happen or not depends=
 on the size of receive window according to the text.<br></div><div>If the =
receive window size is big enough to accommodate=C2=A0segment 1 and segment=
 3, the text &quot;<span style=3D"font-size:13.3333px">Implementations MAY =
hold onto such unmapped data for a short while in=C2=A0</span><span style=
=3D"font-size:13.3333px">the expectation that a mapping will arrive shortly=
. &quot;=C2=A0</span>can be applied to the segment 1. As a result, the segm=
ent 1 won&#39;t be discarded.=C2=A0</div><br><div><em>Yes.=C2=A0 So, segmen=
t 1 may be kept in the data receiver&#39;s buffer in expectation that its m=
apping will arrive shortly. And in the example that we are referring to, th=
e data sender will not be able to include the map for the data in segment 1=
 in segment 3 or any higher segment.</em></div><br><div><em>Regards,</em></=
div><br><div><em>Anil</em></div><br><div>However, this might be contradict =
with the new texts Alan proposed? Or, am I missing something?</div><br><div=
>Thanks,</div><div>--</div><div>Yoshi</div><br><br><br><div><div dir=3D"ltr=
">On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar &lt;<a href=3D"mailto:anil@cs=
ir4pi.in" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20n=
oreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20norefe=
rrer nofollow noopener noreferrer" target=3D"_blank">anil@csir4pi.in</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><d=
iv><div><div style=3D"font-family:arial,helvetica,sans-serif"><div>Hi Yoshi=
,</div><br><div>Thanks for this point. In fact, I had initially not thought=
 of a scenario, where the map is being delivered through a retransmitted da=
ta packet while its first transmission did not include the map. Now I am ju=
st seeing the document (RFC 6824-bis) in this context.</div><br><div>My und=
erstanding is that in scenarios like what I described in my previous mail, =
RST is likely to happen whether we explicitly state so or not. Please see t=
he paragraph containing the below text in RFC 6824-bis. =C2=A0</div><br><di=
v>&quot;If a mapping for that subflow-level sequence space does not arrive =
within a receive window of data, that subflow SHOULD be treated as broken, =
closed with a RST, and any unmapped data silently discarded.&quot;</div><br=
><div>if we assume that the map is included while retransmitting the data (=
even though the first transmission did not contain the map for some reasons=
), =C2=A0we could argue that RST could be avoided provided that the retrans=
mission is triggered within a receive window of data. But the question here=
 would be how and when will the retransmission take place. In this case, th=
e subflow may not initiate the retransmission of data by its own (i..e., no=
 retransmission due to three duplicate ACKs or RTO expiry at subflow level)=
 as there is no segment loss at subflow level sequence space. So there coul=
d be a high possibility of RST happening even before the map delivery throu=
gh retransmission.=C2=A0</div><br><div>With regards,=C2=A0</div><br><div>An=
il</div><div>=C2=A0</div><hr id=3D"gmail-m_-540654355673772201gmail-m_87733=
57439777081590gmail-m_218086596951724501gmail-m_2982267033577902985zwchr"><=
div><b>From: </b>&quot;Yoshifumi Nishida&quot; &lt;<a href=3D"mailto:nsd.ie=
tf@gmail.com" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener=
%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20no=
referrer nofollow noopener noreferrer" target=3D"_blank">nsd.ietf@gmail.com=
</a>&gt;<br><b>To: </b>&quot;V Anil Kumar&quot; &lt;<a href=3D"mailto:anil@=
csir4pi.in" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%2=
0noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20nore=
ferrer nofollow noopener noreferrer" target=3D"_blank">anil@csir4pi.in</a>&=
gt;<br><b>Cc: </b>&quot;alan ford&quot; &lt;<a href=3D"mailto:alan.ford@gma=
il.com" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20nor=
eferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferr=
er nofollow noopener noreferrer" target=3D"_blank">alan.ford@gmail.com</a>&=
gt;, &quot;multipathtcp&quot; &lt;<a href=3D"mailto:multipathtcp@ietf.org" =
rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%=
20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofol=
low noopener noreferrer" target=3D"_blank">multipathtcp@ietf.org</a>&gt;<br=
><b>Sent: </b>Saturday, February 1, 2020 3:39:51 AM<br><b>Subject: </b>Re: =
[multipathtcp] RFC6824bis edits based on implementation feedback<br></div><=
br><div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Anil,</d=
iv><br><div>I have a question about your proposed text.</div><div><div>I am=
 actually wondering if we really want to terminate connection here.=C2=A0</=
div></div><br><div>The packets without proper mappings will be treated as i=
nvalid and will be discarded.=C2=A0</div><div>If an implementation failed t=
o attach proper mapping for some reasons (e.g. option space), it might be a=
ble to attach the proper one when it retransmits the packets. This also loo=
ks ok to me.</div><br><div>I don&#39;t have strong preference for this. But=
, do we have a reason to terminate connection?</div><br><div>Thanks,</div><=
div>--<br></div><div>Yoshi</div><br><div><div dir=3D"ltr">On Mon, Jan 13, 2=
020 at 10:28 AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" rel=3D"=
nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofol=
low%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%2=
0noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener=
 noreferrer" target=3D"_blank">anil@csir4pi.in</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div><div style=3D"=
font-family:arial,helvetica,sans-serif"><div><span style=3D"font-size:12pt;=
line-height:1.3">Hi,</span><br></div><div><div style=3D"font-family:arial,h=
elvetica,sans-serif"><div style=3D"font-family:arial,helvetica,sans-serif">=
<div style=3D"font-family:arial,helvetica,sans-serif"><div style=3D"font-fa=
mily:arial,helvetica,sans-serif"><div style=3D"font-family:arial,helvetica,=
sans-serif"><div style=3D"font-family:arial,helvetica,sans-serif"><div styl=
e=3D"font-family:arial,helvetica,sans-serif"><br><div>I have some points re=
lated to the =C2=A0modifications (Change 2) being proposed on data sequence=
 map. Please see them inline.=C2=A0<span style=3D"font-family:arial,helveti=
ca,sans-serif;font-size:16px;font-style:normal;font-weight:400;letter-spaci=
ng:normal;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;background-color:rgb(255,255,255);float:none;display:inline">Though =
I am putting forward the below points, if the consensus is in favour of the=
 proposed change for reducing implementation complexity, I am also OK with =
that as well.=C2=A0</span><br></div><br><hr id=3D"gmail-m_-5406543556737722=
01gmail-m_8773357439777081590gmail-m_218086596951724501gmail-m_298226703357=
7902985gmail-m_7687184382299596774zwchr"><div><b>From: </b>&quot;alan ford&=
quot; &lt;<a href=3D"mailto:alan.ford@gmail.com" rel=3D"nofollow%20noopener=
%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20no=
referrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20norefer=
rer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=
=3D"_blank">alan.ford@gmail.com</a>&gt;<br><b>To: </b><a href=3D"mailto:mul=
tipathtcp@ietf.org" rel=3D"nofollow%20noopener%20noreferrer%20nofollow%20no=
opener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopene=
r%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20n=
oreferrer nofollow noopener noreferrer" target=3D"_blank">multipathtcp@ietf=
.org</a><br><b>Sent: </b>Thursday, January 2, 2020 4:21:32 AM<br><b>Subject=
: </b>[multipathtcp] RFC6824bis edits based on implementation feedback<br><=
/div><br><div>Hi all,<br><div>We=E2=80=99d love to get this to a state of c=
ompletion as soon as possible, and to this end I am starting a new thread o=
n this topic. In discussion with the chairs, it <i>is </i>possible to make =
the desired changes in AUTH48 as long as there is WG consensus. The discuss=
ion so far has been fairly limited in terms of participation.</div><br><div=
>I would ask the chairs please if it was possible to specify a time bound f=
or this discussion and a default conclusion.</div><br><div>Regarding the ch=
anges, in summary, there are two areas where changes have been requested by=
 the implementation community. As we are the IETF we obviously have strong =
focus on =E2=80=9Crunning code=E2=80=9D and so ease of implementing standar=
ds-compliant code is strongly desirable. However, we do not wish to reduce =
functionality agreed by the IETF community if it is considered a required f=
eature by the community.</div><br><br><div><b>Change 1</b></div><div><b><br=
></b></div><div>Change the sentence reading:<br><br><i>=C2=A0 =C2=A0If B ha=
s data to send first, then the reliable delivery of the ACK + MP_CAPABLE ca=
n be inferred by the receipt of this data with an MPTCP Data Sequence Signa=
l (DSS) option (Section 3.3).=C2=A0<br></i><br>To:<br><br><i>=C2=A0 =C2=A0I=
f B has data to send first, then the reliable delivery of the ACK + MP_CAPA=
BLE is ensured by the receipt of this data with an MPTCP Data Sequence Sign=
al (DSS) option (Section 3.3) containing a DATA_ACK for the MP_CAPABLE (whi=
ch is the first octet of the data sequence=C2=A0space).<br></i><br></div><d=
iv>What this means:</div><br><div>The current text is concerned only with e=
nsuring a path is MPTCP capable, and so only cares that DSS option occurs o=
n a data packet. However, the MP_CAPABLE option is defined to occupy the fi=
rst octet of data sequence space and thus, if analogous to TCP, must be ack=
nowledged. &gt;From an implementation point of view it would make sense not=
 to have this hanging around forever and instead define it is acknowledged =
at the connection level as soon as received. This change ensures the first =
data packet also DATA_ACKs this MP_CAPABLE octet.</div><br><br><div><b>Chan=
ge 2</b></div><div><b><br></b></div><div>Change the sentence reading:<br><b=
r><i>=C2=A0 =C2=A0A Data Sequence Mapping does not need to be included in e=
very MPTCP packet, as long as the subflow sequence space in that packet is =
covered by a mapping known at the receiver.</i><br><br>To:<br><br><i>=C2=A0=
 =C2=A0The mapping provided by a Data Sequence Mapping MUST apply to some o=
r all of the subflow sequence space in the TCP segment which carries the op=
tion. It does not need to be included in every MPTCP packet, as long as the=
 subflow sequence space in that packet is covered by a mapping known at the=
 receiver.<br></i><br>What this means:</div><br><div>The current text does =
not place any restrictions on where a mapping could appear. In theory a sen=
der could define a thousand different mappings up front, send them all, and=
 expect a receiver to store this and reassemble data according to these map=
pings as it arrives. Indeed, this was never explicitly disallowed since it =
=E2=80=9Cmight have been useful=E2=80=9D. The implementation community, how=
ever, has expressed concerns over the difficulty of implementing this open-=
endedly. How many mappings is it reasonable to store? Is there a DoS risk h=
ere? Instead, it has been requested that thee specification restricts the p=
lacement of the DSS option to being within the subflow sequence space to wh=
ich it applies.</div><br><div>Below are my comments on this. I had shared s=
ome of these points in a previous thread that you had initiated in the same=
 context.=C2=A0</div><br><div>Transmitting large number of non-contiguous d=
ata sequence maps could be a misbehaviour (map-flooding), though it is not =
clear whether this can go to the extent of causing a potential DoS to the d=
ata receiver. So some sort of restriction on this could be useful.=C2=A0 On=
e approach could be to insist that the data sender should ensure that the m=
ap being transmitted is for in-window data, as per the receiver advertised =
window. A receiver should anyhow be willing to store the maps for in-window=
 data to deal with packet loss. For example, when a window of data segments=
 (say 1 to 64) is transmitted, each carrying its corresponding map, and seg=
ment-1 is lost, the maps for the remaining 63 need to be stored till the lo=
st segment is retransmitted. Of course, in this case the maps will be store=
d at the receiver side along with their corresponding data. But the need to=
 store multiple maps for in-window data would still be there.</div><br><div=
><span style=3D"font-family:arial,helvetica,sans-serif;font-size:16px;font-=
style:normal;font-weight:normal;letter-spacing:normal;line-height:20.8px;te=
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float=
:none;background-color:rgb(255,255,255);display:inline">The problem with th=
e proposed change (restriction) is that a data sender may find it difficult=
, in case a need arise to slightly delay the map delivery by few segments, =
i.e., sending some data first without map, and then send the corresponding =
map in a later segment, as shown below:</span><br></div><br><div><div style=
=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;fon=
t-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;l=
ine-height:normal;text-indent:0px;text-transform:none;white-space:normal;wo=
rd-spacing:0px;margin:0px;background-color:rgb(255,255,255)"><span lang=3D"=
EN-US" style=3D"font-size:10pt">subflow-1:=C2=A0 =C2=A0 =C2=A0 segment-1=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 segment-3=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-4 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-7</span></div><div st=
yle=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;=
font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:norma=
l;line-height:normal;text-indent:0px;text-transform:none;white-space:normal=
;word-spacing:0px;margin:0px;background-color:rgb(255,255,255)"><span lang=
=3D"EN-US" style=3D"font-size:10pt">=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=C2=
=A0=C2=A0=C2=A0bytes:1-100 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 bytes:201-300 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bytes=
:301-400 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 bytes:601-=
700</span></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida=
 sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(25=
5,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0no map =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0map for 1-100 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0map for=
 201-400 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 map for 601-700</span></=
div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,=
sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;letter-sp=
acing:normal;line-height:normal;text-indent:0px;text-transform:none;white-s=
pace:normal;word-spacing:0px;margin:0px;background-color:rgb(255,255,255)">=
<span lang=3D"EN-US" style=3D"font-size:10pt"><br></span></div><div style=
=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;fon=
t-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;l=
ine-height:normal;text-indent:0px;text-transform:none;white-space:normal;wo=
rd-spacing:0px;margin:0px;background-color:rgb(255,255,255)"><span lang=3D"=
EN-US" style=3D"font-size:10pt"><br></span></div><div style=3D"font-family:=
&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.16px;f=
ont-style:normal;font-weight:normal;letter-spacing:normal;line-height:norma=
l;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;m=
argin:0px;background-color:rgb(255,255,255)"><br></div><div style=3D"font-f=
amily:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;font-size:14.=
16px;font-style:normal;font-weight:normal;letter-spacing:normal;line-height=
:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px;margin:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-US" sty=
le=3D"font-size:10pt">subflow-2:=C2=A0 =C2=A0 =C2=A0 =C2=A0segment-2=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-5 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 segment-6 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 segment-8</span></div><div style=3D"font-family:&quot;segoe ui&quot;,&q=
uot;lucida sans&quot;,sans-serif;font-size:14.16px;font-style:normal;font-w=
eight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-=
transform:none;white-space:normal;word-spacing:0px;margin:0px;background-co=
lor:rgb(255,255,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">=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=C2=A0=C2=A0=C2=A0=C2=A0bytes: 101-200 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 bytes:401-500=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 bytes: 501-600 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bytes:701-800=C2=A0=C2=A0=C2=A0</=
span></div><div style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans=
&quot;,sans-serif;font-size:14.16px;font-style:normal;font-weight:normal;le=
tter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;=
white-space:normal;word-spacing:0px;margin:0px;background-color:rgb(255,255=
,255)"><span lang=3D"EN-US" style=3D"font-size:10pt">=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0map for 101-2=
00 =C2=A0 =C2=A0 =C2=A0 map for 401-600 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0no map =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=A0map for 701-800</span></div><div style=
=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-serif;fon=
t-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:normal;l=
ine-height:normal;text-indent:0px;text-transform:none;white-space:normal;wo=
rd-spacing:0px;margin:0px;background-color:rgb(255,255,255)"><br></div><div=
 style=3D"font-family:&quot;segoe ui&quot;,&quot;lucida sans&quot;,sans-ser=
if;font-size:14.16px;font-style:normal;font-weight:normal;letter-spacing:no=
rmal;line-height:normal;text-indent:0px;text-transform:none;white-space:nor=
mal;word-spacing:0px;margin:0px;background-color:rgb(255,255,255)"><br></di=
v>In the above case, segment-1 goes without map and its map is included lat=
er in segment-3, the next data segment in the same subflow. Further, =C2=A0=
in the above scheduling pattern, the map in segment-3 cannot cover the =C2=
=A0data in segment-1 and segment-3, as some =C2=A0data in between (segment-=
2) is transmitted through another subflow.=C2=A0 With the proposed change, =
the map in segment-3 will become invalid and this will eventually break sub=
flow-1, though this could be a corner case..</div><br><div>The question at =
this stage is why would segment-1 be transmitted without its map. In the ca=
se of bidirectional data transfer, there could be a need to pack both times=
tamp and SACK =C2=A0options in a data segment, i.e., piggybacking of =C2=A0=
SACK with data. If we consider that timestamp takes 12 bytes and SACK, even=
 with single block, =C2=A0takes another 10 bytes, the remaining 18 bytes op=
tion space is not adequate to carry data sequence signal with map, especial=
ly when DSN is 64 bit long. So the delivery of either of the two (SACK or m=
ap) would be delayed.</div><br><div>As far as I understand, RFC 2018 (TCP S=
elective Acknowledgement Options) implies that SACK should not be delayed. =
It states &quot;If sent at all, SACK options SHOULD be included in all ACKs=
 which do not ACK the highest sequence number in the data receiver&#39;s qu=
eue&quot;. It also says &quot;If data receiver generates SACK options under=
 any circumstance, it SHOULD generate them under all permitted circumstance=
s&quot;. =C2=A0 So, as part of meeting the RFC 2018 requirements, if the co=
mbination of SACK and timestamp is given preference over DSS, data segments=
 could be transmitted without their map.=C2=A0</div><br><div>Another case o=
f delaying map could arise if the data sender prefers to send ADD_ADDR opti=
on, instead of map, in a data segment. It is nice that ADD_ADDR option can =
be delivered reliably in a pure ACK, but I think this is not the case with =
DSS at present.</div><br><div>If we adopt the proposed change, I think it m=
ight also be helpful to spell out how the receiver is supposed to behave, i=
f it gets maps not meeting the MUST condition in the proposed change.=C2=A0=
 For example termination of the subflow with MP_TCPRST option (section 3.6 =
in RFC 6824-bis) with appropriate reason code and T flag value to intimate =
the data sender the cause for subflow termination.=C2=A0=C2=A0</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</div></div><div>With regards,</div><br><=
div>Anil<br><br><div>Please can members of the WG express whether they are =
happy with these changes, or concerned.</div><br><div>Best regards,</div><d=
iv>Alan</div><br><br>_______________________________________________<br>mul=
tipathtcp mailing list<br><a href=3D"mailto:multipathtcp@ietf.org" rel=3D"n=
ofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofoll=
ow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20=
noopener%20noreferrer%20nofollow%20noopener%20noreferrer nofollow noopener =
noreferrer" target=3D"_blank">multipathtcp@ietf.org</a><br><a href=3D"https=
://www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"nofollow%20noopener%2=
0noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20nore=
ferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferre=
r%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a></div></d=
iv></div></div></div></div></div></div></div></div><br></div></div></div><b=
r><br>_______________________________________________<br>multipathtcp maili=
ng list<br><a href=3D"mailto:multipathtcp@ietf.org" rel=3D"nofollow%20noope=
ner%20noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%2=
0noreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20nore=
ferrer%20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" tar=
get=3D"_blank">multipathtcp@ietf.org</a><br><a href=3D"https://www.ietf.org=
/mailman/listinfo/multipathtcp" rel=3D"noreferrer%20nofollow%20noopener%20n=
oreferrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20norefe=
rrer%20nofollow%20noopener%20noreferrer%20nofollow%20noopener%20noreferrer%=
20nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br></blockqu=
ote></div></div></div></div></div></div><br></div></div><br></div></blockqu=
ote></div></div></div></div></div></div></div></div></div></div><br></div><=
/div><br><br></div></div></blockquote></div><br></div></div><br></blockquot=
e></div></div>
<br>
<br></div></blockquote></div></div>
_______________________________________________<br>multipathtcp mailing lis=
t<br><a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">multipathtc=
p@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/multipat=
htcp" target=3D"_blank">https://www.ietf.org/mailman/listinfo/multipathtcp<=
/a><br></div></blockquote></div><br></div></blockquote></div></div>

--00000000000066d519059e71cc99--


From nobody Tue Feb 18 02:35:15 2020
Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25BFB1202DD for <multipathtcp@ietfa.amsl.com>; Tue, 18 Feb 2020 02:35:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.696
X-Spam-Level: 
X-Spam-Status: No, score=-2.696 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 gpC3AK28jkH8 for <multipathtcp@ietfa.amsl.com>; Tue, 18 Feb 2020 02:34:56 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBDD9120803 for <multipathtcp@ietf.org>; Tue, 18 Feb 2020 02:34:54 -0800 (PST)
Received: from tpw09926dag12h.domain1.systemhost.net (10.9.212.36) by RDW083A009ED65.bt.com (10.187.98.35) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 18 Feb 2020 10:28:53 +0000
Received: from tpw09926dag08g.domain1.systemhost.net (10.9.202.43) by tpw09926dag12h.domain1.systemhost.net (10.9.212.36) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 18 Feb 2020 10:34:50 +0000
Received: from bwp09926079.bt.com (10.36.82.110) by tpw09926dag08g.domain1.systemhost.net (10.9.202.43) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 18 Feb 2020 10:34:50 +0000
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.50) by smtpe1.intersmtp.com (10.36.82.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 18 Feb 2020 10:34:41 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=I0q+GlEuoEjGZBcVtlymlfEu+2Zz+DghBgkb0zjNwOOcFBGM9TTIb8y/iXo1FvxGNsvP+Ityo91/gV5hCHei/ddv4Jjux8r/ZDj+MX0BBXtCaNOYAhViGBXR55ht7uLJYgLMg2BMqllUKqrceg1Dw/dMsZm1/ovryiETQ/v9iqJdEuZGESxLtnP1J5kYrXDHMiaiBI1TzKE2RynYjL4teB044DBCwUyuMBZdIH9VJztlTanyxRXq6C0hJhn8OYagPzps5cQm4BYpVdz2PMsCMRg39BrZv53gUWR9q2iu8ru1kgJ9XoPdDUxwPclG3NflAfxL/hLJ/dU8YyFumOJ2Pg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=H/RgudR16jIC/3RuaEVkYTrjLVrXU5phBOyvUXGwrfc=; b=f5Q83KVvCRoFA6aUgTXCYWW0XSNqtmnDpjLkVU1pCbFxFzRXLT8hTgCy/vNgPPPBZNQJHQj+OG9WCqc5NodsV0vqQhbKkSEXsGpa6VvvjufPb/Vfi5VgQGj4r06hnnUINJY7Tfjt8kkzRIzUKdDrn7Roqk0u8rloXzpis/goV0uyJ3C9e7dgkK0cmK//qo7vKgmdbip7C8WItc6rNVRyVT67enuYeu2DMSPVs0aXOtJ6ucrvG8QfdQ36qS7+w23Tkm5hFy7zNnX5b27FoqEjmELSU1i9IkrAvDAt6uov3cBwtAjv7wgDMqwGmCspSzowMqI8ECe1C4m4vWb1coGPYQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=H/RgudR16jIC/3RuaEVkYTrjLVrXU5phBOyvUXGwrfc=; b=MLZMyFPUdaV7IuAwthjMUi8N3eTPdLl9AnsXq9EriTcInGvor5IfMDP2wE9VgNPLtsLmcvi27xx1l/zFetUNYATw6JU8p9tOPrFZMx1PvW2ZUZF/uc8JHcA0exfKsEF/BTnNwScRUBnGN/Kd/KB43sanhMmpQEWH3+eeBECU9uA=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXP123MB1850.GBRP123.PROD.OUTLOOK.COM (20.176.159.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.27; Tue, 18 Feb 2020 10:34:46 +0000
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c]) by LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c%7]) with mapi id 15.20.2729.025; Tue, 18 Feb 2020 10:34:46 +0000
From: <philip.eardley@bt.com>
To: <nsd.ietf@gmail.com>, <cpaasch@apple.com>
CC: <multipathtcp@ietf.org>, <mptcp@lists.01.org>
Thread-Topic: [multipathtcp] RFC6824bis edits based on implementation feedback
Thread-Index: AQHV3RjL6VxwEBgdwkqcNWw1sb7yeagVuqeAgADgvACAAkv/gIAH6yqw
Date: Tue, 18 Feb 2020 10:34:45 +0000
Message-ID: <LNXP123MB258793AE47D970277BAF3688EB110@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com> <1411057985.31281938.1581012439446@csir4pi.in> <CAAK044QoFh_eXE+MwggOn5X0uUs3xuzTcw2kdJaKuUnEP745dA@mail.gmail.com> <F3D07C9D-12B2-45A7-B9D0-23E862DDF4BA@apple.com> <CAAK044SQb0utvjZToU=+OCg0hB-KX6vs1bFZGsJ=tJ5WvfETog@mail.gmail.com>
In-Reply-To: <CAAK044SQb0utvjZToU=+OCg0hB-KX6vs1bFZGsJ=tJ5WvfETog@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com; 
x-originating-ip: [193.113.37.9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 65973364-fec0-42f4-3723-08d7b45e2c63
x-ms-traffictypediagnostic: LNXP123MB1850:
x-microsoft-antispam-prvs: <LNXP123MB1850C3157F812072FD11AE28EB110@LNXP123MB1850.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 031763BCAF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(39860400002)(346002)(376002)(136003)(396003)(189003)(199004)(6506007)(53546011)(26005)(4326008)(86362001)(71200400001)(33656002)(7696005)(478600001)(55016002)(9686003)(186003)(8936002)(76116006)(52536014)(64756008)(8676002)(66446008)(2906002)(5660300002)(81166006)(66946007)(81156014)(66476007)(66556008)(966005)(316002)(110136005)(54906003)(30864003)(579004); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXP123MB1850; H:LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: WULQ6MhaZGq0TPdjEIs889btbQQ/kwE020manxIpVaDmJfvnMXniQl0mm2voIHwE/HVU0MEelgsZLIy01JvttqBvJ/dojf6z/3mPOGQN0CJjmCwbgMBdgMid7UzN+hE6+g39OznS/sQ00A5WKxOzTszsnt2FhHSRWQOU4Se6s/G3Liu+gpOEdLDR++ahXsbg2ocezhswfE1PmMdLzCY9CmeRm+vZs5OkHALfIoBvIbiPc2lTbIF2Hq/s65oTyCISiUaeOI7OWMIfL1yEqotgoowPTI2pCouwT4nss3niADmH5zNkzz1jKvs6kd0WaTT0bTWfAqaE/Qz4yimTGnOrYqQMwv1mBzbP3SgVAxuRDa5G1K9KgCbbmG3uE3cNhJsP96cGt+eJKu8ibkEm0PPA2+im0JpfeLHp/2r9sU2mAPbq9hEUTj9TznBLNPDUZpF2QbaBk9ZOwoK7vauDntNVcVLEVqHfy8mLAsgtAAvuEIQJOJtLuaY8rUuO64ab0lklfVU5vgmnwcK3KtrBo/5sSg==
x-ms-exchange-antispam-messagedata: YHXOAaxOSXdxgLPOGpO7Yrn3nFZMl/3Bd5LL89KbbF17H9QaWaRHNtPHIq+LjfLPDlXIw8chz93WarmuEq/1FeQUE5YvaeXALOFxA+KuggysWEsBztEjSrpAiJxwy6GFUp5Ec0x7evX0EnHdefmS+Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB258793AE47D970277BAF3688EB110LNXP123MB2587GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 65973364-fec0-42f4-3723-08d7b45e2c63
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2020 10:34:45.9490 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Xugl7S9CrBQA5wSS7mzfd1l1rdMnjK1KkRH6K0pWShtQp2ToLpNSQZjvEDOwpEjg7dcuHjU0WQb048av+AAviA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB1850
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/ZDMlwfwGLdaLESCAbMOjPpanoXo>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2020 10:35:13 -0000

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

QWxhbiwgcGxlYXNlIGdvIGFoZWFkIGFuZCBtYWtlIENoYW5nZSAyIHRvIHRoZSBkb2N1bWVudCAo
YXMgd2VsbCBhcyBDaGFuZ2UgMSkuIFBsZWFzZSBjb3VsZCB5b3UgJi9vciBDaHJpc3RvcGggYWRk
IGEgc21hbGwgbm90ZSBiYXNlZCBvbiB0aGUgZGlzY3Vzc2lvbiB3ZeKAmXZlIGhhZCwgYXMgaXTi
gJlzIGRyYXduIG91dCBhIGNvdXBsZSBvZiB1c2VmdWwgY2xhcmlmaWNhdGlvbnMuDQoNClRoYW5r
cyB0byBldmVyeW9uZSBmb3IgdGhlIGRpc2N1c3Npb24sDQpCZXN0IHdpc2hlcywNClBoaWwgJiBZ
b3NoaS4NCg0KRnJvbTogbXVsdGlwYXRodGNwIDxtdWx0aXBhdGh0Y3AtYm91bmNlc0BpZXRmLm9y
Zz4gT24gQmVoYWxmIE9mIFlvc2hpZnVtaSBOaXNoaWRhDQpTZW50OiAxMyBGZWJydWFyeSAyMDIw
IDA5OjM0DQpUbzogQ2hyaXN0b3BoIFBhYXNjaCA8Y3BhYXNjaEBhcHBsZS5jb20+DQpDYzogTXVs
dGlQYXRoIFRDUCAtIElFVEYgV0cgPG11bHRpcGF0aHRjcEBpZXRmLm9yZz47IG1wdGNwIFVwc3Ry
ZWFtaW5nIDxtcHRjcEBsaXN0cy4wMS5vcmc+DQpTdWJqZWN0OiBSZTogW211bHRpcGF0aHRjcF0g
UkZDNjgyNGJpcyBlZGl0cyBiYXNlZCBvbiBpbXBsZW1lbnRhdGlvbiBmZWVkYmFjaw0KDQpIaSBD
aHJpc3RvcGgsDQoNClRoYW5rcyBmb3IgdGhlIGNsYXJpZmljYXRpb24uIEl0IHNlZW1zIHRoYXQg
dGhlcmUgYXJlIHNldmVyYWwgd2F5cyB0byBkZWFsIHdpdGggdGhpcyBzaXR1YXRpb24uDQpJIHRo
aW5rIHRoZXNlIGFyZSBub3QgaWRlYWwsIGJ1dCBhdCB0aGUgc2FtZSB0aW1lLCBpdCB3b24ndCBi
ZSBmYXRhbC4gSSB0aGluayBtb3JlIHRob3JvdWdoIHNvbHV0aW9ucyBjYW4gYmUgZGlzY3Vzc2Vk
IGluIGZ1dHVyZSB2ZXJzaW9ucy4NCkdpdmVuIHRoYXQgdGhlcmUncmUgc2V2ZXJhbCB3YXlzIHRv
IGFkZHJlc3MgaXQsIEkgZ3Vlc3MgdGhlIGRyYWZ0IGRvZXNuJ3QgaGF2ZSB0byBzcGVjaWZ5IHRo
ZSBiZWhhdmlvciBmb3IgdGhpcy4NCi0tDQpZb3NoaQ0KDQpPbiBUdWUsIEZlYiAxMSwgMjAyMCBh
dCAyOjMwIFBNIENocmlzdG9waCBQYWFzY2ggPGNwYWFzY2hAYXBwbGUuY29tPG1haWx0bzpjcGFh
c2NoQGFwcGxlLmNvbT4+IHdyb3RlOg0KK01QVENQLXVwc3RyZWFtaW5nDQoNCg0KT24gRmViIDEx
LCAyMDIwLCBhdCAxOjA1IEFNLCBZb3NoaWZ1bWkgTmlzaGlkYSA8bnNkLmlldGZAZ21haWwuY29t
PG1haWx0bzpuc2QuaWV0ZkBnbWFpbC5jb20+PiB3cm90ZToNCg0KSGkgZm9sa3MsDQpJIGd1ZXNz
IHdlIG1pZ2h0IHdhbnQgdG8ga25vdyB0aGUgYmVoYXZpb3Igb2YgZXhpc3RpbmcgaW1wbGVtZW50
YXRpb25zIHN1Y2ggYXMgbGludXguDQpXaGVuIGFuIG1wdGNwIHN0YWNrIHRyaWVzIHRvIHNlbmQg
YSBkYXRhIHBhY2tldCBhbmQgZmluZCB0aGF0IHRoZXJlJ3Mgbm8gZW5vdWdoIG9wdGlvbiBzcGFj
ZSBmb3IgZGF0YSBtYXBwaW5nLCB3aGF0IGl0IHdpbGwgZG8/DQoNCmlPUywgbXVsdGlwYXRoLXRj
cC5vcmc8aHR0cDovL211bHRpcGF0aC10Y3Aub3JnPiBhbmQgTGludXggNS42IGltcGxlbWVudGF0
aW9uIGFsbCBmYXZvciB0aGUgRFNTLW9wdGlvbiBvdmVyIGFueSBvdGhlciBvcHRpb24gKGV4Y2Vw
dCBUQ1AgVGltZXN0YW1wcykuIEFuZCBUQ1AgVGltZXN0YW1wcyBhbmQgRFNTIGNvbWZvcnRhYmx5
IGZpdCBpbiB0aGUgVENQIG9wdGlvbi1zcGFjZS4NCg0KSWYgU0FDSy1ibG9ja3Mgc2hvdWxkIGJl
IGFkZGVkLCB3ZSBvbmx5IGFkZCBTQUNLLWJsb2NrcyB1cCB0byB0aGUgcmVtYWluaW5nIHNwYWNl
LiBTQUNLIGlzIGFueXdheXMgb3Bwb3J0dW5pc3RpYyBhcyBvbmNlIHRoZXJlIGFyZSBtb3JlIHRo
YW4gMyBibG9ja3MgdGhleSBkb24ndCBmaXQgZWl0aGVyLg0KDQoNCkNocmlzdG9waA0KDQoNClNw
bGl0IHRoZSBwYWNrZXQgdG8gY3JlYXRlIG1vcmUgb3B0aW9uIHNwYWNlPw0KLS0NCllvc2hpDQoN
Ck9uIFRodSwgRmViIDYsIDIwMjAgYXQgMTA6MTAgQU0gViBBbmlsIEt1bWFyIDxhbmlsQGNzaXI0
cGkuaW48bWFpbHRvOmFuaWxAY3NpcjRwaS5pbj4+IHdyb3RlOg0KSGkgQWxhbiwNCg0KVGhhbmsg
eW91IGZvciB5b3VyIHJlcGx5LiBJIGhhdmUgdHdvIHBvaW50cyB0byBjbGFyaWZ5LiBQbGVhc2Ug
c2VlIHRoZW0gaW4gbGluZS4NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZy
b206ICJBbGFuIEZvcmQiIDxhbGFuLmZvcmRAZ21haWwuY29tPG1haWx0bzphbGFuLmZvcmRAZ21h
aWwuY29tPj4NClRvOiAiViBBbmlsIEt1bWFyIiA8YW5pbEBjc2lyNHBpLmluPG1haWx0bzphbmls
QGNzaXI0cGkuaW4+PmprDQpDYzogIllvc2hpZnVtaSBOaXNoaWRhIiA8bnNkLmlldGZAZ21haWwu
Y29tPG1haWx0bzpuc2QuaWV0ZkBnbWFpbC5jb20+PiwgIm11bHRpcGF0aHRjcCIgPG11bHRpcGF0
aHRjcEBpZXRmLm9yZzxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnPj4NClNlbnQ6IFRodXJz
ZGF5LCBGZWJydWFyeSA2LCAyMDIwIDI6NDk6MjkgQU0NClN1YmplY3Q6IFJlOiBbbXVsdGlwYXRo
dGNwXSBSRkM2ODI0YmlzIGVkaXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrDQpI
aSBBbmlsLA0KDQpUaGlzIHdvdWxkIG5vdCBiZSBmb3JiaWRkZW4gaWYgdGhlIG1hcHBpbmcgd2Fz
IGNhcnJpZWQgb24gYSBwdXJlIEFDSyB3aXRoIG5vIGRhdGEuDQpBcyBmYXIgYXMgSSB1bmRlcnN0
YW5kLCBkZWxpdmVyeSBvZiBEU00gdGhyb3VnaCBwdXJlIEFDSyBpcyBub3QgaW4gdGhlIHNjb3Bl
IG9mIHRoZSBjdXJyZW50IGRyYWZ0LiBJZiB3ZSBpbnRlbmQgdG8gZG8gdGhpcywgd2UgbWF5IG5l
ZWQgYW4gYXBwcm9hY2ggc2ltaWxhciB0byB0aGUgb25lIHByb3Bvc2VkIGZvciBkZWxpdmVyeSBv
ZiBBRERfQUREUiBvcHRpb24gaW4gcHVyZSBBQ0sgd2l0aCByZWxpYWJpbGl0eSBmZWF0dXJlLiAg
U28sIHBhY2tpbmcgRFNNIG9uIHB1cmUgQUNLIGRvZXMgbm90IHNlZW0gdG8gYmUgYW4gb3B0aW9u
IGF0IHRoaXMgc3RhZ2UuDQoNCkkgZG8gc2VlIHRoZSBwb2ludCBoZXJlOiBpZiBhIHBhY2tldCBv
ZiAxMDAwIGJ5dGVzIGNvbnRhaW5zIDUwMCBieXRlcyBvZiBvbmUgbWFwcGluZyBhbmQgNTAwIGJ5
dGVzIG9mIGFub3RoZXIgbWFwcGluZywgdGhlbiBvbmx5IG9uZSBEU00gd291bGQgYXBwZWFyIG9u
IG9uZSBwYWNrZXQsIGxlYXZpbmcgdGhlIG1hcHBpbmcgZm9yIHRoZSBzZWNvbmQgNTAwIGJ5dGVz
IHRvIGJlIGNhcnJpZWQgc29tZXdoZXJlIGVsc2UgLSB0aGUgb25seSBvcHRpb24gYmVpbmcgYSBw
dXJlIEFDSy4gQnV0IHRoaXMga2luZCBvZiBzY2VuYXJpbyB3b3VsZCBiZSBleHRyZW1lbHkgcmFy
ZQ0KWWVzLCBJIGRvIGFncmVlIHRoYXQgdGhlIHNjZW5hcmlvIHlvdSBtZW50aW9uZWQgYWJvdmUg
d291bGQgYmUgZXh0cmVtZWx5IHJhcmUuIEluIGZhY3QsIEkgd29uZGVyIHdoZXRoZXIgc3VjaCBh
IHNpdHVhdGlvbiAoaS5lLiwgbmVlZCB0byBjb3ZlciB0aGUgYnl0ZXMgaW4gYSBzaW5nbGUgcGFj
a2V0IHdpdGggdHdvIGRpZmZlcmVudCBtYXBzKSB3b3VsZCBldmVyIGFyaXNlLiBQcm9iYWJseSB0
aGVyZSBtaWdodCBiZSBzb21lIGNvcm5lciBjYXNlcywgd2hpY2ggSSBkb24ndCBnZXQgaXQgcmln
aHRseSBub3cuDQoNCk1vcmUgaW1wb3J0YW50bHksIHRoZSBzY2VuYXJpbyB0aGF0IFlvc2hpIGFu
ZCBtZSBhcmUgcmVmZXJyaW5nIHRvIGlzIHRvdGFsbHkgZGlmZmVyZW50OiB0aGUgb25lIEkgaGFk
IGdpdmVuIGFzIHBhcnQgb2YgbXkgY29tbWVudHMgaW4gcmVzcG9uc2UgdG8gdGhlIHByb3Bvc2Vk
IGNoYW5nZSAyLiBJbiB0aGlzIHNjZW5hcmlvLCB3aGljaCB5b3UgY291bGQgc2VlIGluIHRoZSB0
cmFpbGluZyBtYWlsLCBkYXRhIHNlZ21lbnQtMSBpcyB0cmFuc21pdHRlZCB3aXRob3V0IGluY2x1
ZGluZyBpdHMgbWFwLCBzb21ldGhpbmcgd2hpY2ggaXMgcGVybWl0dGVkIGluIHRoZSAgbXB0Y3Ag
ZnJhbWV3b3JrICg2ODI0IGJpcykuIEkgbWFrZSB0aGlzIGluZmVyZW5jZSBmcm9tIHRoZSBiZWxv
dyB0ZXh0IGluIDY4MjQgYmlzOg0KDQoiLi4uZXZlbiBpZiBhIG1hcHBpbmcgZG9lcyBub3QgZXhp
c3QgZnJvbSB0aGUgc3ViZmxvdyBzcGFjZSB0byB0aGUgZGF0YS0gbGV2ZWwgc3BhY2UsIHRoZSBk
YXRhIFNIT1VMRCBzdGlsbCBiZSBBQ0tlZCBhdCB0aGUgc3ViZmxvdyAoaWYgaXQgaXMgaW4td2lu
ZG93KS4gVGhpcyBkYXRhIGNhbm5vdCwgaG93ZXZlciwgYmUgYWNrbm93bGVkZ2VkIGF0IHRoZSBk
YXRhIGxldmVsIChTZWN0aW9uIDMuMy4yKSBiZWNhdXNlIGl0cyBkYXRhIHNlcXVlbmNlIG51bWJl
cnMgYXJlIHVua25vd24uIEltcGxlbWVudGF0aW9ucyBNQVkgaG9sZCBvbnRvIHN1Y2ggdW5tYXBw
ZWQgZGF0YSBmb3IgYSBzaG9ydCB3aGlsZSBpbiB0aGUgZXhwZWN0YXRpb24gdGhhdCBhIG1hcHBp
bmcgd2lsbCBhcnJpdmUgc2hvcnRseS4iDQoNCk9uZSBvcHRpb24gdGhlIGRhdGEgc2VuZGVyIGhh
cyBhdCB0aGlzIHN0YWdlIGlzIHRvIGluY2x1ZGUgdGhlIG1hcCBmb3IgZGF0YSBpbiBzZWdtZW50
LTEsIGluIHNlZ21lbnQtMyAocGxlYXNlIHNlZSB0aGUgdHdvLXN1YmZsb3cgZXhhbXBsZSBJIGdh
dmUgaW4gcmVzcG9uc2UgdG8gdGhlIGNoYW5nZSAyIHlvdSBoYWQgcHJvcG9zZWQpLiBCdXQgdGhl
IHByb3Bvc2VkIGNoYW5nZSBkb2VzIG5vdCBwZXJtaXQgdGhpcy4gV2hhdCB3b3VsZCBoYXBwZW4g
dG8gIHN1YmZsb3ctMSBpbiB0aGlzIGNhc2UgPw0KDQpXaXRoIHJlZ2FyZHMsDQoNCkFuaWwNCmFu
ZCBJIHdvdWxkIGltYWdpbmUgYW55IGltcGxlbWVudGF0aW9uIHdvdWxkIGp1c3Qgc3BsaXQgaW50
byB0d28gNTAwIGJ5dGUgc2VnbWVudHMgZWFjaCB3aXRoIHRoZSBQU0ggZmxhZyBzZXQuIEkgZG9u
4oCZdCB0aGluayB3ZSBuZWVkIHRvIHNwZWxsIHRoaXMgb3V0IGluIHRoZSBzcGVjIGhvd2V2ZXIu
DQoNClJlZ2FyZHMsDQpBbGFuDQoNCk9uIDUgRmViIDIwMjAsIGF0IDE1OjA5LCBWIEFuaWwgS3Vt
YXIgPGFuaWxAY3NpcjRwaS5pbjxtYWlsdG86YW5pbEBjc2lyNHBpLmluPj4gd3JvdGU6DQpIaSBZ
b3NoaSwNCg0KUGxlYXNlIHNlZSBpbiBsaW5lLg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KRnJvbTogIllvc2hpZnVtaSBOaXNoaWRhIiA8bnNkLmlldGZAZ21haWwuY29tPG1h
aWx0bzpuc2QuaWV0ZkBnbWFpbC5jb20+Pg0KVG86ICJWIEFuaWwgS3VtYXIiIDxhbmlsQGNzaXI0
cGkuaW48bWFpbHRvOmFuaWxAY3NpcjRwaS5pbj4+DQpDYzogImFsYW4gZm9yZCIgPGFsYW4uZm9y
ZEBnbWFpbC5jb208bWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5jb20+PiwgIm11bHRpcGF0aHRjcCIg
PG11bHRpcGF0aHRjcEBpZXRmLm9yZzxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnPj4NClNl
bnQ6IFR1ZXNkYXksIEZlYnJ1YXJ5IDQsIDIwMjAgMTowODo0NSBQTQ0KU3ViamVjdDogUmU6IFtt
dWx0aXBhdGh0Y3BdIFJGQzY4MjRiaXMgZWRpdHMgYmFzZWQgb24gaW1wbGVtZW50YXRpb24gZmVl
ZGJhY2sNCg0KSGkgQW5pbCwNCg0KVGhhbmtzIGZvciBwb2ludGluZyBpdCBvdXQuIEkgb3Zlcmxv
b2tlZCB0aGlzIG9uZS4NClRoaXMgbG9va3MgYW4gaW50ZXJlc3RpbmcgcG9pbnQuDQoNCkl0IHNl
ZW1zIHRvIG1lIHRoYXQgd2hldGhlciBSU1QgaXMgaGFwcGVuIG9yIG5vdCBkZXBlbmRzIG9uIHRo
ZSBzaXplIG9mIHJlY2VpdmUgd2luZG93IGFjY29yZGluZyB0byB0aGUgdGV4dC4NCklmIHRoZSBy
ZWNlaXZlIHdpbmRvdyBzaXplIGlzIGJpZyBlbm91Z2ggdG8gYWNjb21tb2RhdGUgc2VnbWVudCAx
IGFuZCBzZWdtZW50IDMsIHRoZSB0ZXh0ICJJbXBsZW1lbnRhdGlvbnMgTUFZIGhvbGQgb250byBz
dWNoIHVubWFwcGVkIGRhdGEgZm9yIGEgc2hvcnQgd2hpbGUgaW4gdGhlIGV4cGVjdGF0aW9uIHRo
YXQgYSBtYXBwaW5nIHdpbGwgYXJyaXZlIHNob3J0bHkuLiAiIGNhbiBiZSBhcHBsaWVkIHRvIHRo
ZSBzZWdtZW50IDEuIEFzIGEgcmVzdWx0LCB0aGUgc2VnbWVudCAxIHdvbid0IGJlIGRpc2NhcmRl
ZC4NCg0KWWVzLiAgU28sIHNlZ21lbnQgMSBtYXkgYmUga2VwdCBpbiB0aGUgZGF0YSByZWNlaXZl
cidzIGJ1ZmZlciBpbiBleHBlY3RhdGlvbiB0aGF0IGl0cyBtYXBwaW5nIHdpbGwgYXJyaXZlIHNo
b3J0bHkuIEFuZCBpbiB0aGUgZXhhbXBsZSB0aGF0IHdlIGFyZSByZWZlcnJpbmcgdG8sIHRoZSBk
YXRhIHNlbmRlciB3aWxsIG5vdCBiZSBhYmxlIHRvIGluY2x1ZGUgdGhlIG1hcCBmb3IgdGhlIGRh
dGEgaW4gc2VnbWVudCAxIGluIHNlZ21lbnQgMyBvciBhbnkgaGlnaGVyIHNlZ21lbnQuDQoNClJl
Z2FyZHMsDQoNCkFuaWwNCg0KSG93ZXZlciwgdGhpcyBtaWdodCBiZSBjb250cmFkaWN0IHdpdGgg
dGhlIG5ldyB0ZXh0cyBBbGFuIHByb3Bvc2VkPyBPciwgYW0gSSBtaXNzaW5nIHNvbWV0aGluZz8N
Cg0KVGhhbmtzLA0KLS0NCllvc2hpDQoNCg0KT24gU3VuLCBGZWIgMiwgMjAyMCBhdCA4OjQyIEFN
IFYgQW5pbCBLdW1hciA8YW5pbEBjc2lyNHBpLmluPG1haWx0bzphbmlsQGNzaXI0cGkuaW4+PiB3
cm90ZToNCkhpIFlvc2hpLA0KDQpUaGFua3MgZm9yIHRoaXMgcG9pbnQuIEluIGZhY3QsIEkgaGFk
IGluaXRpYWxseSBub3QgdGhvdWdodCBvZiBhIHNjZW5hcmlvLCB3aGVyZSB0aGUgbWFwIGlzIGJl
aW5nIGRlbGl2ZXJlZCB0aHJvdWdoIGEgcmV0cmFuc21pdHRlZCBkYXRhIHBhY2tldCB3aGlsZSBp
dHMgZmlyc3QgdHJhbnNtaXNzaW9uIGRpZCBub3QgaW5jbHVkZSB0aGUgbWFwLiBOb3cgSSBhbSBq
dXN0IHNlZWluZyB0aGUgZG9jdW1lbnQgKFJGQyA2ODI0LWJpcykgaW4gdGhpcyBjb250ZXh0Lg0K
DQpNeSB1bmRlcnN0YW5kaW5nIGlzIHRoYXQgaW4gc2NlbmFyaW9zIGxpa2Ugd2hhdCBJIGRlc2Ny
aWJlZCBpbiBteSBwcmV2aW91cyBtYWlsLCBSU1QgaXMgbGlrZWx5IHRvIGhhcHBlbiB3aGV0aGVy
IHdlIGV4cGxpY2l0bHkgc3RhdGUgc28gb3Igbm90LiBQbGVhc2Ugc2VlIHRoZSBwYXJhZ3JhcGgg
Y29udGFpbmluZyB0aGUgYmVsb3cgdGV4dCBpbiBSRkMgNjgyNC1iaXMuDQoNCiJJZiBhIG1hcHBp
bmcgZm9yIHRoYXQgc3ViZmxvdy1sZXZlbCBzZXF1ZW5jZSBzcGFjZSBkb2VzIG5vdCBhcnJpdmUg
d2l0aGluIGEgcmVjZWl2ZSB3aW5kb3cgb2YgZGF0YSwgdGhhdCBzdWJmbG93IFNIT1VMRCBiZSB0
cmVhdGVkIGFzIGJyb2tlbiwgY2xvc2VkIHdpdGggYSBSU1QsIGFuZCBhbnkgdW5tYXBwZWQgZGF0
YSBzaWxlbnRseSBkaXNjYXJkZWQuIg0KDQppZiB3ZSBhc3N1bWUgdGhhdCB0aGUgbWFwIGlzIGlu
Y2x1ZGVkIHdoaWxlIHJldHJhbnNtaXR0aW5nIHRoZSBkYXRhIChldmVuIHRob3VnaCB0aGUgZmly
c3QgdHJhbnNtaXNzaW9uIGRpZCBub3QgY29udGFpbiB0aGUgbWFwIGZvciBzb21lIHJlYXNvbnMp
LCAgd2UgY291bGQgYXJndWUgdGhhdCBSU1QgY291bGQgYmUgYXZvaWRlZCBwcm92aWRlZCB0aGF0
IHRoZSByZXRyYW5zbWlzc2lvbiBpcyB0cmlnZ2VyZWQgd2l0aGluIGEgcmVjZWl2ZSB3aW5kb3cg
b2YgZGF0YS4gQnV0IHRoZSBxdWVzdGlvbiBoZXJlIHdvdWxkIGJlIGhvdyBhbmQgd2hlbiB3aWxs
IHRoZSByZXRyYW5zbWlzc2lvbiB0YWtlIHBsYWNlLiBJbiB0aGlzIGNhc2UsIHRoZSBzdWJmbG93
IG1heSBub3QgaW5pdGlhdGUgdGhlIHJldHJhbnNtaXNzaW9uIG9mIGRhdGEgYnkgaXRzIG93biAo
aS4uZS4sIG5vIHJldHJhbnNtaXNzaW9uIGR1ZSB0byB0aHJlZSBkdXBsaWNhdGUgQUNLcyBvciBS
VE8gZXhwaXJ5IGF0IHN1YmZsb3cgbGV2ZWwpIGFzIHRoZXJlIGlzIG5vIHNlZ21lbnQgbG9zcyBh
dCBzdWJmbG93IGxldmVsIHNlcXVlbmNlIHNwYWNlLiBTbyB0aGVyZSBjb3VsZCBiZSBhIGhpZ2gg
cG9zc2liaWxpdHkgb2YgUlNUIGhhcHBlbmluZyBldmVuIGJlZm9yZSB0aGUgbWFwIGRlbGl2ZXJ5
IHRocm91Z2ggcmV0cmFuc21pc3Npb24uDQoNCldpdGggcmVnYXJkcywNCg0KQW5pbA0KDQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogIllvc2hpZnVtaSBOaXNoaWRhIiA8
bnNkLmlldGZAZ21haWwuY29tPG1haWx0bzpuc2QuaWV0ZkBnbWFpbC5jb20+Pg0KVG86ICJWIEFu
aWwgS3VtYXIiIDxhbmlsQGNzaXI0cGkuaW48bWFpbHRvOmFuaWxAY3NpcjRwaS5pbj4+DQpDYzog
ImFsYW4gZm9yZCIgPGFsYW4uZm9yZEBnbWFpbC5jb208bWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5j
b20+PiwgIm11bHRpcGF0aHRjcCIgPG11bHRpcGF0aHRjcEBpZXRmLm9yZzxtYWlsdG86bXVsdGlw
YXRodGNwQGlldGYub3JnPj4NClNlbnQ6IFNhdHVyZGF5LCBGZWJydWFyeSAxLCAyMDIwIDM6Mzk6
NTEgQU0NClN1YmplY3Q6IFJlOiBbbXVsdGlwYXRodGNwXSBSRkM2ODI0YmlzIGVkaXRzIGJhc2Vk
IG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrDQoNCkhpIEFuaWwsDQoNCkkgaGF2ZSBhIHF1ZXN0
aW9uIGFib3V0IHlvdXIgcHJvcG9zZWQgdGV4dC4NCkkgYW0gYWN0dWFsbHkgd29uZGVyaW5nIGlm
IHdlIHJlYWxseSB3YW50IHRvIHRlcm1pbmF0ZSBjb25uZWN0aW9uIGhlcmUuDQoNClRoZSBwYWNr
ZXRzIHdpdGhvdXQgcHJvcGVyIG1hcHBpbmdzIHdpbGwgYmUgdHJlYXRlZCBhcyBpbnZhbGlkIGFu
ZCB3aWxsIGJlIGRpc2NhcmRlZC4NCklmIGFuIGltcGxlbWVudGF0aW9uIGZhaWxlZCB0byBhdHRh
Y2ggcHJvcGVyIG1hcHBpbmcgZm9yIHNvbWUgcmVhc29ucyAoZS5nLiBvcHRpb24gc3BhY2UpLCBp
dCBtaWdodCBiZSBhYmxlIHRvIGF0dGFjaCB0aGUgcHJvcGVyIG9uZSB3aGVuIGl0IHJldHJhbnNt
aXRzIHRoZSBwYWNrZXRzLiBUaGlzIGFsc28gbG9va3Mgb2sgdG8gbWUuDQoNCkkgZG9uJ3QgaGF2
ZSBzdHJvbmcgcHJlZmVyZW5jZSBmb3IgdGhpcy4gQnV0LCBkbyB3ZSBoYXZlIGEgcmVhc29uIHRv
IHRlcm1pbmF0ZSBjb25uZWN0aW9uPw0KDQpUaGFua3MsDQotLQ0KWW9zaGkNCg0KT24gTW9uLCBK
YW4gMTMsIDIwMjAgYXQgMTA6MjggQU0gViBBbmlsIEt1bWFyIDxhbmlsQGNzaXI0cGkuaW48bWFp
bHRvOmFuaWxAY3NpcjRwaS5pbj4+IHdyb3RlOg0KSGksDQoNCkkgaGF2ZSBzb21lIHBvaW50cyBy
ZWxhdGVkIHRvIHRoZSAgbW9kaWZpY2F0aW9ucyAoQ2hhbmdlIDIpIGJlaW5nIHByb3Bvc2VkIG9u
IGRhdGEgc2VxdWVuY2UgbWFwLiBQbGVhc2Ugc2VlIHRoZW0gaW5saW5lLiBUaG91Z2ggSSBhbSBw
dXR0aW5nIGZvcndhcmQgdGhlIGJlbG93IHBvaW50cywgaWYgdGhlIGNvbnNlbnN1cyBpcyBpbiBm
YXZvdXIgb2YgdGhlIHByb3Bvc2VkIGNoYW5nZSBmb3IgcmVkdWNpbmcgaW1wbGVtZW50YXRpb24g
Y29tcGxleGl0eSwgSSBhbSBhbHNvIE9LIHdpdGggdGhhdCBhcyB3ZWxsLg0KDQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogImFsYW4gZm9yZCIgPGFsYW4uZm9yZEBnbWFp
bC5jb208bWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5jb20+Pg0KVG86IG11bHRpcGF0aHRjcEBpZXRm
Li5vcmc8bWFpbHRvOm11bHRpcGF0aHRjcEBpZXRmLm9yZz4NClNlbnQ6IFRodXJzZGF5LCBKYW51
YXJ5IDIsIDIwMjAgNDoyMTozMiBBTQ0KU3ViamVjdDogW211bHRpcGF0aHRjcF0gUkZDNjgyNGJp
cyBlZGl0cyBiYXNlZCBvbiBpbXBsZW1lbnRhdGlvbiBmZWVkYmFjaw0KDQpIaSBhbGwsDQpXZeKA
mWQgbG92ZSB0byBnZXQgdGhpcyB0byBhIHN0YXRlIG9mIGNvbXBsZXRpb24gYXMgc29vbiBhcyBw
b3NzaWJsZSwgYW5kIHRvIHRoaXMgZW5kIEkgYW0gc3RhcnRpbmcgYSBuZXcgdGhyZWFkIG9uIHRo
aXMgdG9waWMuIEluIGRpc2N1c3Npb24gd2l0aCB0aGUgY2hhaXJzLCBpdCBpcyBwb3NzaWJsZSB0
byBtYWtlIHRoZSBkZXNpcmVkIGNoYW5nZXMgaW4gQVVUSDQ4IGFzIGxvbmcgYXMgdGhlcmUgaXMg
V0cgY29uc2Vuc3VzLiBUaGUgZGlzY3Vzc2lvbiBzbyBmYXIgaGFzIGJlZW4gZmFpcmx5IGxpbWl0
ZWQgaW4gdGVybXMgb2YgcGFydGljaXBhdGlvbi4NCg0KSSB3b3VsZCBhc2sgdGhlIGNoYWlycyBw
bGVhc2UgaWYgaXQgd2FzIHBvc3NpYmxlIHRvIHNwZWNpZnkgYSB0aW1lIGJvdW5kIGZvciB0aGlz
IGRpc2N1c3Npb24gYW5kIGEgZGVmYXVsdCBjb25jbHVzaW9uLg0KDQpSZWdhcmRpbmcgdGhlIGNo
YW5nZXMsIGluIHN1bW1hcnksIHRoZXJlIGFyZSB0d28gYXJlYXMgd2hlcmUgY2hhbmdlcyBoYXZl
IGJlZW4gcmVxdWVzdGVkIGJ5IHRoZSBpbXBsZW1lbnRhdGlvbiBjb21tdW5pdHkuIEFzIHdlIGFy
ZSB0aGUgSUVURiB3ZSBvYnZpb3VzbHkgaGF2ZSBzdHJvbmcgZm9jdXMgb24g4oCccnVubmluZyBj
b2Rl4oCdIGFuZCBzbyBlYXNlIG9mIGltcGxlbWVudGluZyBzdGFuZGFyZHMtY29tcGxpYW50IGNv
ZGUgaXMgc3Ryb25nbHkgZGVzaXJhYmxlLiBIb3dldmVyLCB3ZSBkbyBub3Qgd2lzaCB0byByZWR1
Y2UgZnVuY3Rpb25hbGl0eSBhZ3JlZWQgYnkgdGhlIElFVEYgY29tbXVuaXR5IGlmIGl0IGlzIGNv
bnNpZGVyZWQgYSByZXF1aXJlZCBmZWF0dXJlIGJ5IHRoZSBjb21tdW5pdHkuDQoNCkNoYW5nZSAx
DQoNCkNoYW5nZSB0aGUgc2VudGVuY2UgcmVhZGluZzoNCg0KICAgSWYgQiBoYXMgZGF0YSB0byBz
ZW5kIGZpcnN0LCB0aGVuIHRoZSByZWxpYWJsZSBkZWxpdmVyeSBvZiB0aGUgQUNLICsgTVBfQ0FQ
QUJMRSBjYW4gYmUgaW5mZXJyZWQgYnkgdGhlIHJlY2VpcHQgb2YgdGhpcyBkYXRhIHdpdGggYW4g
TVBUQ1AgRGF0YSBTZXF1ZW5jZSBTaWduYWwgKERTUykgb3B0aW9uIChTZWN0aW9uIDMuMykuDQoN
ClRvOg0KDQogICBJZiBCIGhhcyBkYXRhIHRvIHNlbmQgZmlyc3QsIHRoZW4gdGhlIHJlbGlhYmxl
IGRlbGl2ZXJ5IG9mIHRoZSBBQ0sgKyBNUF9DQVBBQkxFIGlzIGVuc3VyZWQgYnkgdGhlIHJlY2Vp
cHQgb2YgdGhpcyBkYXRhIHdpdGggYW4gTVBUQ1AgRGF0YSBTZXF1ZW5jZSBTaWduYWwgKERTUykg
b3B0aW9uIChTZWN0aW9uIDMuMykgY29udGFpbmluZyBhIERBVEFfQUNLIGZvciB0aGUgTVBfQ0FQ
QUJMRSAod2hpY2ggaXMgdGhlIGZpcnN0IG9jdGV0IG9mIHRoZSBkYXRhIHNlcXVlbmNlIHNwYWNl
KS4NCldoYXQgdGhpcyBtZWFuczoNCg0KVGhlIGN1cnJlbnQgdGV4dCBpcyBjb25jZXJuZWQgb25s
eSB3aXRoIGVuc3VyaW5nIGEgcGF0aCBpcyBNUFRDUCBjYXBhYmxlLCBhbmQgc28gb25seSBjYXJl
cyB0aGF0IERTUyBvcHRpb24gb2NjdXJzIG9uIGEgZGF0YSBwYWNrZXQuIEhvd2V2ZXIsIHRoZSBN
UF9DQVBBQkxFIG9wdGlvbiBpcyBkZWZpbmVkIHRvIG9jY3VweSB0aGUgZmlyc3Qgb2N0ZXQgb2Yg
ZGF0YSBzZXF1ZW5jZSBzcGFjZSBhbmQgdGh1cywgaWYgYW5hbG9nb3VzIHRvIFRDUCwgbXVzdCBi
ZSBhY2tub3dsZWRnZWQuID5Gcm9tIGFuIGltcGxlbWVudGF0aW9uIHBvaW50IG9mIHZpZXcgaXQg
d291bGQgbWFrZSBzZW5zZSBub3QgdG8gaGF2ZSB0aGlzIGhhbmdpbmcgYXJvdW5kIGZvcmV2ZXIg
YW5kIGluc3RlYWQgZGVmaW5lIGl0IGlzIGFja25vd2xlZGdlZCBhdCB0aGUgY29ubmVjdGlvbiBs
ZXZlbCBhcyBzb29uIGFzIHJlY2VpdmVkLiBUaGlzIGNoYW5nZSBlbnN1cmVzIHRoZSBmaXJzdCBk
YXRhIHBhY2tldCBhbHNvIERBVEFfQUNLcyB0aGlzIE1QX0NBUEFCTEUgb2N0ZXQuDQoNCkNoYW5n
ZSAyDQoNCkNoYW5nZSB0aGUgc2VudGVuY2UgcmVhZGluZzoNCg0KICAgQSBEYXRhIFNlcXVlbmNl
IE1hcHBpbmcgZG9lcyBub3QgbmVlZCB0byBiZSBpbmNsdWRlZCBpbiBldmVyeSBNUFRDUCBwYWNr
ZXQsIGFzIGxvbmcgYXMgdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2UgaW4gdGhhdCBwYWNrZXQg
aXMgY292ZXJlZCBieSBhIG1hcHBpbmcga25vd24gYXQgdGhlIHJlY2VpdmVyLg0KDQpUbzoNCg0K
ICAgVGhlIG1hcHBpbmcgcHJvdmlkZWQgYnkgYSBEYXRhIFNlcXVlbmNlIE1hcHBpbmcgTVVTVCBh
cHBseSB0byBzb21lIG9yIGFsbCBvZiB0aGUgc3ViZmxvdyBzZXF1ZW5jZSBzcGFjZSBpbiB0aGUg
VENQIHNlZ21lbnQgd2hpY2ggY2FycmllcyB0aGUgb3B0aW9uLiBJdCBkb2VzIG5vdCBuZWVkIHRv
IGJlIGluY2x1ZGVkIGluIGV2ZXJ5IE1QVENQIHBhY2tldCwgYXMgbG9uZyBhcyB0aGUgc3ViZmxv
dyBzZXF1ZW5jZSBzcGFjZSBpbiB0aGF0IHBhY2tldCBpcyBjb3ZlcmVkIGJ5IGEgbWFwcGluZyBr
bm93biBhdCB0aGUgcmVjZWl2ZXIuDQoNCldoYXQgdGhpcyBtZWFuczoNCg0KVGhlIGN1cnJlbnQg
dGV4dCBkb2VzIG5vdCBwbGFjZSBhbnkgcmVzdHJpY3Rpb25zIG9uIHdoZXJlIGEgbWFwcGluZyBj
b3VsZCBhcHBlYXIuIEluIHRoZW9yeSBhIHNlbmRlciBjb3VsZCBkZWZpbmUgYSB0aG91c2FuZCBk
aWZmZXJlbnQgbWFwcGluZ3MgdXAgZnJvbnQsIHNlbmQgdGhlbSBhbGwsIGFuZCBleHBlY3QgYSBy
ZWNlaXZlciB0byBzdG9yZSB0aGlzIGFuZCByZWFzc2VtYmxlIGRhdGEgYWNjb3JkaW5nIHRvIHRo
ZXNlIG1hcHBpbmdzIGFzIGl0IGFycml2ZXMuIEluZGVlZCwgdGhpcyB3YXMgbmV2ZXIgZXhwbGlj
aXRseSBkaXNhbGxvd2VkIHNpbmNlIGl0IOKAnG1pZ2h0IGhhdmUgYmVlbiB1c2VmdWzigJ0uIFRo
ZSBpbXBsZW1lbnRhdGlvbiBjb21tdW5pdHksIGhvd2V2ZXIsIGhhcyBleHByZXNzZWQgY29uY2Vy
bnMgb3ZlciB0aGUgZGlmZmljdWx0eSBvZiBpbXBsZW1lbnRpbmcgdGhpcyBvcGVuLWVuZGVkbHku
IEhvdyBtYW55IG1hcHBpbmdzIGlzIGl0IHJlYXNvbmFibGUgdG8gc3RvcmU/IElzIHRoZXJlIGEg
RG9TIHJpc2sgaGVyZT8gSW5zdGVhZCwgaXQgaGFzIGJlZW4gcmVxdWVzdGVkIHRoYXQgdGhlZSBz
cGVjaWZpY2F0aW9uIHJlc3RyaWN0cyB0aGUgcGxhY2VtZW50IG9mIHRoZSBEU1Mgb3B0aW9uIHRv
IGJlaW5nIHdpdGhpbiB0aGUgc3ViZmxvdyBzZXF1ZW5jZSBzcGFjZSB0byB3aGljaCBpdCBhcHBs
aWVzLg0KDQpCZWxvdyBhcmUgbXkgY29tbWVudHMgb24gdGhpcy4gSSBoYWQgc2hhcmVkIHNvbWUg
b2YgdGhlc2UgcG9pbnRzIGluIGEgcHJldmlvdXMgdGhyZWFkIHRoYXQgeW91IGhhZCBpbml0aWF0
ZWQgaW4gdGhlIHNhbWUgY29udGV4dC4NCg0KVHJhbnNtaXR0aW5nIGxhcmdlIG51bWJlciBvZiBu
b24tY29udGlndW91cyBkYXRhIHNlcXVlbmNlIG1hcHMgY291bGQgYmUgYSBtaXNiZWhhdmlvdXIg
KG1hcC1mbG9vZGluZyksIHRob3VnaCBpdCBpcyBub3QgY2xlYXIgd2hldGhlciB0aGlzIGNhbiBn
byB0byB0aGUgZXh0ZW50IG9mIGNhdXNpbmcgYSBwb3RlbnRpYWwgRG9TIHRvIHRoZSBkYXRhIHJl
Y2VpdmVyLiBTbyBzb21lIHNvcnQgb2YgcmVzdHJpY3Rpb24gb24gdGhpcyBjb3VsZCBiZSB1c2Vm
dWwuICBPbmUgYXBwcm9hY2ggY291bGQgYmUgdG8gaW5zaXN0IHRoYXQgdGhlIGRhdGEgc2VuZGVy
IHNob3VsZCBlbnN1cmUgdGhhdCB0aGUgbWFwIGJlaW5nIHRyYW5zbWl0dGVkIGlzIGZvciBpbi13
aW5kb3cgZGF0YSwgYXMgcGVyIHRoZSByZWNlaXZlciBhZHZlcnRpc2VkIHdpbmRvdy4gQSByZWNl
aXZlciBzaG91bGQgYW55aG93IGJlIHdpbGxpbmcgdG8gc3RvcmUgdGhlIG1hcHMgZm9yIGluLXdp
bmRvdyBkYXRhIHRvIGRlYWwgd2l0aCBwYWNrZXQgbG9zcy4gRm9yIGV4YW1wbGUsIHdoZW4gYSB3
aW5kb3cgb2YgZGF0YSBzZWdtZW50cyAoc2F5IDEgdG8gNjQpIGlzIHRyYW5zbWl0dGVkLCBlYWNo
IGNhcnJ5aW5nIGl0cyBjb3JyZXNwb25kaW5nIG1hcCwgYW5kIHNlZ21lbnQtMSBpcyBsb3N0LCB0
aGUgbWFwcyBmb3IgdGhlIHJlbWFpbmluZyA2MyBuZWVkIHRvIGJlIHN0b3JlZCB0aWxsIHRoZSBs
b3N0IHNlZ21lbnQgaXMgcmV0cmFuc21pdHRlZC4gT2YgY291cnNlLCBpbiB0aGlzIGNhc2UgdGhl
IG1hcHMgd2lsbCBiZSBzdG9yZWQgYXQgdGhlIHJlY2VpdmVyIHNpZGUgYWxvbmcgd2l0aCB0aGVp
ciBjb3JyZXNwb25kaW5nIGRhdGEuIEJ1dCB0aGUgbmVlZCB0byBzdG9yZSBtdWx0aXBsZSBtYXBz
IGZvciBpbi13aW5kb3cgZGF0YSB3b3VsZCBzdGlsbCBiZSB0aGVyZS4NCg0KVGhlIHByb2JsZW0g
d2l0aCB0aGUgcHJvcG9zZWQgY2hhbmdlIChyZXN0cmljdGlvbikgaXMgdGhhdCBhIGRhdGEgc2Vu
ZGVyIG1heSBmaW5kIGl0IGRpZmZpY3VsdCwgaW4gY2FzZSBhIG5lZWQgYXJpc2UgdG8gc2xpZ2h0
bHkgZGVsYXkgdGhlIG1hcCBkZWxpdmVyeSBieSBmZXcgc2VnbWVudHMsIGkuZS4sIHNlbmRpbmcg
c29tZSBkYXRhIGZpcnN0IHdpdGhvdXQgbWFwLCBhbmQgdGhlbiBzZW5kIHRoZSBjb3JyZXNwb25k
aW5nIG1hcCBpbiBhIGxhdGVyIHNlZ21lbnQsIGFzIHNob3duIGJlbG93Og0KDQpzdWJmbG93LTE6
ICAgICAgc2VnbWVudC0xICAgICAgICAgICAgICAgICAgIHNlZ21lbnQtMyAgICAgICAgICAgICAg
ICAgICAgc2VnbWVudC00ICAgICAgICAgICAgICAgICAgICAgICBzZWdtZW50LTcNCiAgICAgICAg
ICAgICAgICAgICAgICBieXRlczoxLTEwMCAgICAgICAgICAgICAgICAgYnl0ZXM6MjAxLTMwMCAg
ICAgICAgICAgICAgYnl0ZXM6MzAxLTQwMCAgICAgICAgICAgICAgICAgYnl0ZXM6NjAxLTcwMA0K
ICAgICAgICAgICAgICAgICAgICAgIG5vIG1hcCAgICAgICAgICAgICAgICAgICAgICAgIG1hcCBm
b3IgMS0xMDAgICAgICAgICAgICAgIG1hcCBmb3IgMjAxLTQwMCAgICAgICAgICAgICBtYXAgZm9y
IDYwMS03MDANCg0KDQoNCnN1YmZsb3ctMjogICAgICAgc2VnbWVudC0yICAgICAgICAgICAgICAg
ICAgc2VnbWVudC01ICAgICAgICAgICAgICAgICAgICAgc2VnbWVudC02ICAgICAgICAgICAgICAg
ICAgICAgICBzZWdtZW50LTgNCiAgICAgICAgICAgICAgICAgICAgICAgYnl0ZXM6IDEwMS0yMDAg
ICAgICAgICAgIGJ5dGVzOjQwMS01MDAgICAgICAgICAgICAgICBieXRlczogNTAxLTYwMCAgICAg
ICAgICAgICAgICBieXRlczo3MDEtODAwDQogICAgICAgICAgICAgICAgICAgICAgIG1hcCBmb3Ig
MTAxLTIwMCAgICAgICBtYXAgZm9yIDQwMS02MDAgICAgICAgICAgICBubyBtYXAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgbWFwIGZvciA3MDEtODAwDQoNCg0KSW4gdGhlIGFib3ZlIGNhc2Us
IHNlZ21lbnQtMSBnb2VzIHdpdGhvdXQgbWFwIGFuZCBpdHMgbWFwIGlzIGluY2x1ZGVkIGxhdGVy
IGluIHNlZ21lbnQtMywgdGhlIG5leHQgZGF0YSBzZWdtZW50IGluIHRoZSBzYW1lIHN1YmZsb3cu
IEZ1cnRoZXIsICBpbiB0aGUgYWJvdmUgc2NoZWR1bGluZyBwYXR0ZXJuLCB0aGUgbWFwIGluIHNl
Z21lbnQtMyBjYW5ub3QgY292ZXIgdGhlICBkYXRhIGluIHNlZ21lbnQtMSBhbmQgc2VnbWVudC0z
LCBhcyBzb21lICBkYXRhIGluIGJldHdlZW4gKHNlZ21lbnQtMikgaXMgdHJhbnNtaXR0ZWQgdGhy
b3VnaCBhbm90aGVyIHN1YmZsb3cuICBXaXRoIHRoZSBwcm9wb3NlZCBjaGFuZ2UsIHRoZSBtYXAg
aW4gc2VnbWVudC0zIHdpbGwgYmVjb21lIGludmFsaWQgYW5kIHRoaXMgd2lsbCBldmVudHVhbGx5
IGJyZWFrIHN1YmZsb3ctMSwgdGhvdWdoIHRoaXMgY291bGQgYmUgYSBjb3JuZXIgY2FzZS4uDQoN
ClRoZSBxdWVzdGlvbiBhdCB0aGlzIHN0YWdlIGlzIHdoeSB3b3VsZCBzZWdtZW50LTEgYmUgdHJh
bnNtaXR0ZWQgd2l0aG91dCBpdHMgbWFwLiBJbiB0aGUgY2FzZSBvZiBiaWRpcmVjdGlvbmFsIGRh
dGEgdHJhbnNmZXIsIHRoZXJlIGNvdWxkIGJlIGEgbmVlZCB0byBwYWNrIGJvdGggdGltZXN0YW1w
IGFuZCBTQUNLICBvcHRpb25zIGluIGEgZGF0YSBzZWdtZW50LCBpLmUuLCBwaWdneWJhY2tpbmcg
b2YgIFNBQ0sgd2l0aCBkYXRhLiBJZiB3ZSBjb25zaWRlciB0aGF0IHRpbWVzdGFtcCB0YWtlcyAx
MiBieXRlcyBhbmQgU0FDSywgZXZlbiB3aXRoIHNpbmdsZSBibG9jaywgIHRha2VzIGFub3RoZXIg
MTAgYnl0ZXMsIHRoZSByZW1haW5pbmcgMTggYnl0ZXMgb3B0aW9uIHNwYWNlIGlzIG5vdCBhZGVx
dWF0ZSB0byBjYXJyeSBkYXRhIHNlcXVlbmNlIHNpZ25hbCB3aXRoIG1hcCwgZXNwZWNpYWxseSB3
aGVuIERTTiBpcyA2NCBiaXQgbG9uZy4gU28gdGhlIGRlbGl2ZXJ5IG9mIGVpdGhlciBvZiB0aGUg
dHdvIChTQUNLIG9yIG1hcCkgd291bGQgYmUgZGVsYXllZC4NCg0KQXMgZmFyIGFzIEkgdW5kZXJz
dGFuZCwgUkZDIDIwMTggKFRDUCBTZWxlY3RpdmUgQWNrbm93bGVkZ2VtZW50IE9wdGlvbnMpIGlt
cGxpZXMgdGhhdCBTQUNLIHNob3VsZCBub3QgYmUgZGVsYXllZC4gSXQgc3RhdGVzICJJZiBzZW50
IGF0IGFsbCwgU0FDSyBvcHRpb25zIFNIT1VMRCBiZSBpbmNsdWRlZCBpbiBhbGwgQUNLcyB3aGlj
aCBkbyBub3QgQUNLIHRoZSBoaWdoZXN0IHNlcXVlbmNlIG51bWJlciBpbiB0aGUgZGF0YSByZWNl
aXZlcidzIHF1ZXVlIi4gSXQgYWxzbyBzYXlzICJJZiBkYXRhIHJlY2VpdmVyIGdlbmVyYXRlcyBT
QUNLIG9wdGlvbnMgdW5kZXIgYW55IGNpcmN1bXN0YW5jZSwgaXQgU0hPVUxEIGdlbmVyYXRlIHRo
ZW0gdW5kZXIgYWxsIHBlcm1pdHRlZCBjaXJjdW1zdGFuY2VzIi4gICBTbywgYXMgcGFydCBvZiBt
ZWV0aW5nIHRoZSBSRkMgMjAxOCByZXF1aXJlbWVudHMsIGlmIHRoZSBjb21iaW5hdGlvbiBvZiBT
QUNLIGFuZCB0aW1lc3RhbXAgaXMgZ2l2ZW4gcHJlZmVyZW5jZSBvdmVyIERTUywgZGF0YSBzZWdt
ZW50cyBjb3VsZCBiZSB0cmFuc21pdHRlZCB3aXRob3V0IHRoZWlyIG1hcC4NCg0KQW5vdGhlciBj
YXNlIG9mIGRlbGF5aW5nIG1hcCBjb3VsZCBhcmlzZSBpZiB0aGUgZGF0YSBzZW5kZXIgcHJlZmVy
cyB0byBzZW5kIEFERF9BRERSIG9wdGlvbiwgaW5zdGVhZCBvZiBtYXAsIGluIGEgZGF0YSBzZWdt
ZW50LiBJdCBpcyBuaWNlIHRoYXQgQUREX0FERFIgb3B0aW9uIGNhbiBiZSBkZWxpdmVyZWQgcmVs
aWFibHkgaW4gYSBwdXJlIEFDSywgYnV0IEkgdGhpbmsgdGhpcyBpcyBub3QgdGhlIGNhc2Ugd2l0
aCBEU1MgYXQgcHJlc2VudC4NCg0KSWYgd2UgYWRvcHQgdGhlIHByb3Bvc2VkIGNoYW5nZSwgSSB0
aGluayBpdCBtaWdodCBhbHNvIGJlIGhlbHBmdWwgdG8gc3BlbGwgb3V0IGhvdyB0aGUgcmVjZWl2
ZXIgaXMgc3VwcG9zZWQgdG8gYmVoYXZlLCBpZiBpdCBnZXRzIG1hcHMgbm90IG1lZXRpbmcgdGhl
IE1VU1QgY29uZGl0aW9uIGluIHRoZSBwcm9wb3NlZCBjaGFuZ2UuICBGb3IgZXhhbXBsZSB0ZXJt
aW5hdGlvbiBvZiB0aGUgc3ViZmxvdyB3aXRoIE1QX1RDUFJTVCBvcHRpb24gKHNlY3Rpb24gMy42
IGluIFJGQyA2ODI0LWJpcykgd2l0aCBhcHByb3ByaWF0ZSByZWFzb24gY29kZSBhbmQgVCBmbGFn
IHZhbHVlIHRvIGludGltYXRlIHRoZSBkYXRhIHNlbmRlciB0aGUgY2F1c2UgZm9yIHN1YmZsb3cg
dGVybWluYXRpb24uDQoNCldpdGggcmVnYXJkcywNCg0KQW5pbA0KUGxlYXNlIGNhbiBtZW1iZXJz
IG9mIHRoZSBXRyBleHByZXNzIHdoZXRoZXIgdGhleSBhcmUgaGFwcHkgd2l0aCB0aGVzZSBjaGFu
Z2VzLCBvciBjb25jZXJuZWQuDQoNCkJlc3QgcmVnYXJkcywNCkFsYW4NCg0KDQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbXVsdGlwYXRodGNwIG1haWxp
bmcgbGlzdA0KbXVsdGlwYXRodGNwQGlldGYub3JnPG1haWx0bzptdWx0aXBhdGh0Y3BAaWV0Zi5v
cmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRpcGF0aHRjcA0K
DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm11
bHRpcGF0aHRjcCBtYWlsaW5nIGxpc3QNCm11bHRpcGF0aHRjcEBpZXRmLm9yZzxtYWlsdG86bXVs
dGlwYXRodGNwQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9tdWx0aXBhdGh0Y3ANCg0KDQoNCg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCm11bHRpcGF0aHRjcCBtYWlsaW5nIGxpc3QNCm11bHRpcGF0
aHRjcEBpZXRmLm9yZzxtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnPg0KaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3ANCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OkhlbHZldGljYTsNCglwYW5vc2UtMToyIDExIDYgNCAyIDIgMiAyIDIg
NDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0x
OjIgNCA1IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJp
Ow0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1m
YW1pbHk6IlNlZ29lIFVJIjsNCglwYW5vc2UtMToyIDExIDUgMiA0IDIgNCAyIDIgMzt9DQovKiBT
dHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05v
cm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6
MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bh
bi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJ
dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5r
Rm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2
Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9w
LWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkFyaWFsIixzYW5zLXNlcmlmOw0KCWNv
bG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0
LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3Qt
bGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIu
MHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0
aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4N
CjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlv
dXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286
c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1H
QiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkFsYW4sIHBs
ZWFzZSBnbyBhaGVhZCBhbmQgbWFrZSBDaGFuZ2UgMiB0byB0aGUgZG9jdW1lbnQgKGFzIHdlbGwg
YXMgQ2hhbmdlIDEpLiBQbGVhc2UgY291bGQgeW91ICZhbXA7L29yIENocmlzdG9waCBhZGQgYSBz
bWFsbCBub3RlIGJhc2VkIG9uIHRoZSBkaXNjdXNzaW9uIHdl4oCZdmUgaGFkLCBhcw0KIGl04oCZ
cyBkcmF3biBvdXQgYSBjb3VwbGUgb2YgdXNlZnVsIGNsYXJpZmljYXRpb25zLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVT
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+VGhhbmtzIHRvIGV2ZXJ5b25lIGZvciB0aGUgZGlzY3Vzc2lv
biw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1s
YW5ndWFnZTpFTi1VUyI+QmVzdCB3aXNoZXMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlBoaWwgJmFtcDsgWW9zaGku
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0i
RU4tVVMiPiBtdWx0aXBhdGh0Y3AgJmx0O211bHRpcGF0aHRjcC1ib3VuY2VzQGlldGYub3JnJmd0
Ow0KPGI+T24gQmVoYWxmIE9mIDwvYj5Zb3NoaWZ1bWkgTmlzaGlkYTxicj4NCjxiPlNlbnQ6PC9i
PiAxMyBGZWJydWFyeSAyMDIwIDA5OjM0PGJyPg0KPGI+VG86PC9iPiBDaHJpc3RvcGggUGFhc2No
ICZsdDtjcGFhc2NoQGFwcGxlLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IE11bHRpUGF0aCBUQ1Ag
LSBJRVRGIFdHICZsdDttdWx0aXBhdGh0Y3BAaWV0Zi5vcmcmZ3Q7OyBtcHRjcCBVcHN0cmVhbWlu
ZyAmbHQ7bXB0Y3BAbGlzdHMuMDEub3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW211
bHRpcGF0aHRjcF0gUkZDNjgyNGJpcyBlZGl0cyBiYXNlZCBvbiBpbXBsZW1lbnRhdGlvbiBmZWVk
YmFjazxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBDaHJp
c3RvcGgsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPlRoYW5rcyBmb3IgdGhlIGNsYXJpZmljYXRpb24uIEl0IHNlZW1zIHRoYXQgdGhlcmUgYXJl
IHNldmVyYWwgd2F5cyB0byBkZWFsIHdpdGggdGhpcyBzaXR1YXRpb24uJm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHRoaW5rIHRoZXNl
IGFyZSBub3QgaWRlYWwsIGJ1dCBhdCB0aGUgc2FtZSB0aW1lLCBpdCB3b24ndCBiZSBmYXRhbC4g
SSB0aGluayBtb3JlIHRob3JvdWdoIHNvbHV0aW9ucyBjYW4gYmUgZGlzY3Vzc2VkIGluIGZ1dHVy
ZSB2ZXJzaW9ucy4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkdpdmVuIHRoYXQgdGhlcmUncmUgc2V2ZXJhbCB3YXlzIHRvIGFkZHJlc3Mg
aXQsIEkgZ3Vlc3MgdGhlIGRyYWZ0IGRvZXNuJ3QgaGF2ZSB0byBzcGVjaWZ5IHRoZSBiZWhhdmlv
ciBmb3IgdGhpcy4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPi0tPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5Zb3NoaTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+T24gVHVlLCBGZWIgMTEsIDIwMjAgYXQgMjozMCBQTSBDaHJpc3RvcGggUGFhc2NoICZs
dDs8YSBocmVmPSJtYWlsdG86Y3BhYXNjaEBhcHBsZS5jb20iPmNwYWFzY2hAYXBwbGUuY29tPC9h
PiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+JiM0MztNUFRDUC11cHN0cmVhbWluZzxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9w
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBw
dCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gRmViIDExLCAyMDIwLCBhdCAxOjA1
IEFNLCBZb3NoaWZ1bWkgTmlzaGlkYSAmbHQ7PGEgaHJlZj0ibWFpbHRvOm5zZC5pZXRmQGdtYWls
LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm5zZC5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIGZv
bGtzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SSBndWVzcyB3ZSBtaWdodCB3YW50IHRvIGtub3cgdGhlIGJlaGF2aW9yIG9mIGV4aXN0aW5nIGlt
cGxlbWVudGF0aW9ucyBzdWNoIGFzIGxpbnV4LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6
NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5XaGVuIGFuIG1wdGNwIHN0YWNrIHRyaWVzIHRvIHNlbmQgYSBkYXRhIHBh
Y2tldCBhbmQgZmluZCB0aGF0IHRoZXJlJ3Mgbm8gZW5vdWdoIG9wdGlvbiBzcGFjZSBmb3IgZGF0
YSBtYXBwaW5nLCB3aGF0IGl0IHdpbGwgZG8/PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5p
T1MsIDxhIGhyZWY9Imh0dHA6Ly9tdWx0aXBhdGgtdGNwLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm11
bHRpcGF0aC10Y3Aub3JnPC9hPiZuYnNwO2FuZCBMaW51eCA1LjYgaW1wbGVtZW50YXRpb24gYWxs
IGZhdm9yIHRoZSBEU1Mtb3B0aW9uIG92ZXIgYW55IG90aGVyIG9wdGlvbiAoZXhjZXB0IFRDUCBU
aW1lc3RhbXBzKS4gQW5kIFRDUCBUaW1lc3RhbXBzIGFuZCBEU1MgY29tZm9ydGFibHkgZml0IGlu
IHRoZSBUQ1Agb3B0aW9uLXNwYWNlLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5JZiBTQUNLLWJsb2NrcyBzaG91bGQgYmUgYWRkZWQsIHdlIG9u
bHkgYWRkIFNBQ0stYmxvY2tzIHVwIHRvIHRoZSByZW1haW5pbmcgc3BhY2UuIFNBQ0sgaXMgYW55
d2F5cyBvcHBvcnR1bmlzdGljIGFzIG9uY2UgdGhlcmUgYXJlIG1vcmUgdGhhbiAzIGJsb2NrcyB0
aGV5IGRvbid0IGZpdCBlaXRoZXIuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2hyaXN0b3BoPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVv
dGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TcGxpdCB0aGUgcGFja2V0IHRvIGNy
ZWF0ZSBtb3JlIG9wdGlvbiBzcGFjZT88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPi0tPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5Zb3NoaTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+T24gVGh1LCBGZWIgNiwgMjAyMCBhdCAxMDoxMCBBTSBWIEFuaWwgS3VtYXIg
Jmx0OzxhIGhyZWY9Im1haWx0bzphbmlsQGNzaXI0cGkuaW4iIHRhcmdldD0iX2JsYW5rIj5hbmls
QGNzaXI0cGkuaW48L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7
cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6
MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIEFsYW4s
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRo
YW5rIHlvdSBmb3IgeW91ciByZXBseS4gSSBoYXZlIHR3byBwb2ludHMgdG8gY2xhcmlmeS4gUGxl
YXNlIHNlZSB0aGVtIGluIGxpbmUuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdiBjbGFz
cz0iTXNvTm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIiPg0K
PGhyIHNpemU9IjIiIHdpZHRoPSIxMDAlIiBhbGlnbj0iY2VudGVyIiBpZD0iZ21haWwtbV8tNTQw
NjU0MzU1NjczNzcyMjAxZ21haWwtbV84NzczMzU3NDM5Nzc3MDgxNTkwendjaHIiPg0KPC9kaXY+
DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICMxMDEwRkYgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDozLjc1
cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5Gcm9tOg0KPC9zcGFuPjwvYj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fu
cy1zZXJpZiI+JnF1b3Q7QWxhbiBGb3JkJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86YWxhbi5m
b3JkQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFsYW4uZm9yZEBnbWFpbC5jb208L2E+Jmd0
Ozxicj4NCjxiPlRvOiA8L2I+JnF1b3Q7ViBBbmlsIEt1bWFyJnF1b3Q7ICZsdDs8YSBocmVmPSJt
YWlsdG86YW5pbEBjc2lyNHBpLmluIiB0YXJnZXQ9Il9ibGFuayI+YW5pbEBjc2lyNHBpLmluPC9h
PiZndDtqayZuYnNwOzxicj4NCjxiPkNjOiA8L2I+JnF1b3Q7WW9zaGlmdW1pIE5pc2hpZGEmcXVv
dDsgJmx0OzxhIGhyZWY9Im1haWx0bzpuc2QuaWV0ZkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5r
Ij5uc2QuaWV0ZkBnbWFpbC5jb208L2E+Jmd0OywgJnF1b3Q7bXVsdGlwYXRodGNwJnF1b3Q7ICZs
dDs8YSBocmVmPSJtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+
bXVsdGlwYXRodGNwQGlldGYub3JnPC9hPiZndDs8YnI+DQo8Yj5TZW50OiA8L2I+VGh1cnNkYXks
IEZlYnJ1YXJ5IDYsIDIwMjAgMjo0OToyOSBBTTxicj4NCjxiPlN1YmplY3Q6IDwvYj5SZTogW211
bHRpcGF0aHRjcF0gUkZDNjgyNGJpcyBlZGl0cyBiYXNlZCBvbiBpbXBsZW1lbnRhdGlvbiBmZWVk
YmFjazxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGRpdj4N
CjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjMTAxMEZG
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxlZnQ6My43NXB0O21hcmdp
bi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2Em
cXVvdDssc2Fucy1zZXJpZiI+SGkgQW5pbCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90Oyxz
YW5zLXNlcmlmIj5UaGlzIHdvdWxkIG5vdCBiZSBmb3JiaWRkZW4gaWYgdGhlIG1hcHBpbmcgd2Fz
IGNhcnJpZWQgb24gYSBwdXJlIEFDSyB3aXRoIG5vIGRhdGEuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMg
ZmFyIGFzIEkgdW5kZXJzdGFuZCwgZGVsaXZlcnkgb2YgRFNNIHRocm91Z2ggcHVyZSBBQ0sgaXMg
bm90IGluIHRoZSBzY29wZSBvZiB0aGUgY3VycmVudCBkcmFmdC4gSWYgd2UgaW50ZW5kIHRvIGRv
IHRoaXMsIHdlIG1heSBuZWVkIGFuIGFwcHJvYWNoIHNpbWlsYXIgdG8gdGhlIG9uZSBwcm9wb3Nl
ZCBmb3IgZGVsaXZlcnkgb2YgQUREX0FERFIgb3B0aW9uIGluIHB1cmUgQUNLIHdpdGggcmVsaWFi
aWxpdHkNCiBmZWF0dXJlLiZuYnNwOyBTbywgcGFja2luZyBEU00gb24gcHVyZSBBQ0sgZG9lcyBu
b3Qgc2VlbSB0byBiZSBhbiBvcHRpb24gYXQgdGhpcyBzdGFnZS48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICMx
MDEwRkYgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDozLjc1cHQ7
bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVv
dDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYi
PkkgZG8gc2VlIHRoZSBwb2ludCBoZXJlOiBpZiBhIHBhY2tldCBvZiAxMDAwIGJ5dGVzIGNvbnRh
aW5zIDUwMCBieXRlcyBvZiBvbmUgbWFwcGluZyBhbmQgNTAwIGJ5dGVzIG9mIGFub3RoZXIgbWFw
cGluZywgdGhlbiBvbmx5IG9uZSBEU00gd291bGQgYXBwZWFyIG9uIG9uZSBwYWNrZXQsIGxlYXZp
bmcNCiB0aGUgbWFwcGluZyBmb3IgdGhlIHNlY29uZCA1MDAgYnl0ZXMgdG8gYmUgY2FycmllZCBz
b21ld2hlcmUgZWxzZSAtIHRoZSBvbmx5IG9wdGlvbiBiZWluZyBhIHB1cmUgQUNLLiBCdXQgdGhp
cyBraW5kIG9mIHNjZW5hcmlvIHdvdWxkIGJlIGV4dHJlbWVseSByYXJlPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+WWVzLCBJIGRvIGFncmVlIHRoYXQgdGhlIHNjZW5hcmlvIHlvdSBtZW50aW9uZWQgYWJvdmUg
d291bGQgYmUgZXh0cmVtZWx5IHJhcmUuIEluIGZhY3QsIEkgd29uZGVyIHdoZXRoZXIgc3VjaCBh
IHNpdHVhdGlvbiAoaS5lLiwgbmVlZCB0byBjb3ZlciB0aGUgYnl0ZXMgaW4gYSBzaW5nbGUgcGFj
a2V0IHdpdGggdHdvIGRpZmZlcmVudCBtYXBzKSB3b3VsZCBldmVyIGFyaXNlLiBQcm9iYWJseSB0
aGVyZSBtaWdodA0KIGJlIHNvbWUgY29ybmVyIGNhc2VzLCB3aGljaCBJIGRvbid0IGdldCBpdCBy
aWdodGx5IG5vdy4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+TW9yZSBpbXBvcnRhbnRseSwgdGhlIHNjZW5hcmlvIHRoYXQgWW9zaGkg
YW5kIG1lIGFyZSByZWZlcnJpbmcgdG8gaXMgdG90YWxseSBkaWZmZXJlbnQ6IHRoZSBvbmUgSSBo
YWQgZ2l2ZW4gYXMgcGFydCBvZiBteSBjb21tZW50cyBpbiByZXNwb25zZSB0byB0aGUgcHJvcG9z
ZWQgY2hhbmdlIDIuIEluIHRoaXMgc2NlbmFyaW8sIHdoaWNoIHlvdSBjb3VsZCBzZWUgaW4gdGhl
IHRyYWlsaW5nIG1haWwsIGRhdGEgc2VnbWVudC0xDQogaXMgdHJhbnNtaXR0ZWQgd2l0aG91dCBp
bmNsdWRpbmcgaXRzIG1hcCwgc29tZXRoaW5nIHdoaWNoIGlzIHBlcm1pdHRlZCBpbiB0aGUgJm5i
c3A7bXB0Y3AgZnJhbWV3b3JrICg2ODI0IGJpcykuIEkgbWFrZSB0aGlzIGluZmVyZW5jZSBmcm9t
IHRoZSBiZWxvdyB0ZXh0IGluIDY4MjQgYmlzOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mcXVvdDsuLi5ldmVuIGlmIGEgbWFwcGluZyBkb2Vz
IG5vdCBleGlzdCBmcm9tIHRoZSBzdWJmbG93IHNwYWNlIHRvIHRoZSBkYXRhLSBsZXZlbCBzcGFj
ZSwgdGhlIGRhdGEgU0hPVUxEIHN0aWxsIGJlIEFDS2VkIGF0IHRoZSBzdWJmbG93IChpZiBpdCBp
cyBpbi13aW5kb3cpLiBUaGlzIGRhdGEgY2Fubm90LCBob3dldmVyLCBiZSBhY2tub3dsZWRnZWQg
YXQgdGhlIGRhdGEgbGV2ZWwgKFNlY3Rpb24gMy4zLjIpIGJlY2F1c2UNCiBpdHMgZGF0YSBzZXF1
ZW5jZSBudW1iZXJzIGFyZSB1bmtub3duLiBJbXBsZW1lbnRhdGlvbnMgTUFZIGhvbGQgb250byBz
dWNoIHVubWFwcGVkIGRhdGEgZm9yIGEgc2hvcnQgd2hpbGUgaW4gdGhlIGV4cGVjdGF0aW9uIHRo
YXQgYSBtYXBwaW5nIHdpbGwgYXJyaXZlIHNob3J0bHkuJnF1b3Q7DQo8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T25lIG9wdGlvbiB0aGUgZGF0
YSBzZW5kZXIgaGFzIGF0IHRoaXMgc3RhZ2UgaXMgdG8gaW5jbHVkZSB0aGUgbWFwIGZvciBkYXRh
IGluIHNlZ21lbnQtMSwgaW4gc2VnbWVudC0zIChwbGVhc2Ugc2VlIHRoZSB0d28tc3ViZmxvdyBl
eGFtcGxlIEkgZ2F2ZSBpbiByZXNwb25zZSB0byB0aGUgY2hhbmdlIDIgeW91IGhhZCBwcm9wb3Nl
ZCkuIEJ1dCB0aGUgcHJvcG9zZWQgY2hhbmdlIGRvZXMgbm90IHBlcm1pdCB0aGlzLg0KIFdoYXQg
d291bGQgaGFwcGVuIHRvICZuYnNwO3N1YmZsb3ctMSBpbiB0aGlzIGNhc2UgPzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaXRoIHJlZ2FyZHMs
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFu
aWwgJm5ic3A7ICZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgIzEwMTBGRiAxLjVwdDtwYWRkaW5nOjBj
bSAwY20gMGNtIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdp
bi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5z
LXNlcmlmIj5hbmQgSSB3b3VsZCBpbWFnaW5lIGFueSBpbXBsZW1lbnRhdGlvbiB3b3VsZCBqdXN0
IHNwbGl0IGludG8gdHdvIDUwMCBieXRlIHNlZ21lbnRzIGVhY2ggd2l0aCB0aGUgUFNIIGZsYWcg
c2V0LiBJIGRvbuKAmXQgdGhpbmsgd2UgbmVlZCB0byBzcGVsbCB0aGlzIG91dCBpbiB0aGUgc3Bl
YyBob3dldmVyLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJp
ZiI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+QWxhbjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4t
dG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZl
dGljYSZxdW90OyxzYW5zLXNlcmlmIj5PbiA1IEZlYiAyMDIwLCBhdCAxNTowOSwgViBBbmlsIEt1
bWFyICZsdDs8YSBocmVmPSJtYWlsdG86YW5pbEBjc2lyNHBpLmluIiB0YXJnZXQ9Il9ibGFuayI+
YW5pbEBjc2lyNHBpLmluPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+SGkg
WW9zaGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+UGxlYXNlIHNlZSBpbiBsaW5lLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFs
IiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
Pg0KPGhyIHNpemU9IjIiIHdpZHRoPSIxMDAlIiBhbGlnbj0iY2VudGVyIiBpZD0iZ21haWwtbV8t
NTQwNjU0MzU1NjczNzcyMjAxZ21haWwtbV84NzczMzU3NDM5Nzc3MDgxNTkwendjaHIiPg0KPC9z
cGFuPjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
PkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPiZxdW90O1lvc2hpZnVtaSBOaXNoaWRh
JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86bnNkLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9i
bGFuayI+bnNkLmlldGZAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5UbzogPC9iPiZxdW90O1Yg
QW5pbCBLdW1hciZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaWxAY3NpcjRwaS5pbiIgdGFy
Z2V0PSJfYmxhbmsiPmFuaWxAY3NpcjRwaS5pbjwvYT4mZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVv
dDthbGFuIGZvcmQmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzphbGFuLmZvcmRAZ21haWwuY29t
IiB0YXJnZXQ9Il9ibGFuayI+YWxhbi5mb3JkQGdtYWlsLmNvbTwvYT4mZ3Q7LCAmcXVvdDttdWx0
aXBhdGh0Y3AmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzptdWx0aXBhdGh0Y3BAaWV0Zi5vcmci
IHRhcmdldD0iX2JsYW5rIj5tdWx0aXBhdGh0Y3BAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxiPlNl
bnQ6IDwvYj5UdWVzZGF5LCBGZWJydWFyeSA0LCAyMDIwIDE6MDg6NDUgUE08YnI+DQo8Yj5TdWJq
ZWN0OiA8L2I+UmU6IFttdWx0aXBhdGh0Y3BdIFJGQzY4MjRiaXMgZWRpdHMgYmFzZWQgb24gaW1w
bGVtZW50YXRpb24gZmVlZGJhY2s8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZiI+SGkgQW5pbCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UaGFu
a3MgZm9yIHBvaW50aW5nIGl0IG91dC4gSSBvdmVybG9va2VkIHRoaXMgb25lLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMt
c2VyaWYiPlRoaXMgbG9va3MgYW4gaW50ZXJlc3RpbmcgcG9pbnQuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZiI+SXQgc2VlbXMgdG8gbWUgdGhhdCB3aGV0aGVyIFJTVCBpcyBoYXBwZW4gb3Igbm90
IGRlcGVuZHMgb24gdGhlIHNpemUgb2YgcmVjZWl2ZSB3aW5kb3cgYWNjb3JkaW5nIHRvIHRoZSB0
ZXh0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPklmIHRoZSByZWNlaXZlIHdpbmRvdyBzaXplIGlzIGJpZyBl
bm91Z2ggdG8gYWNjb21tb2RhdGUmbmJzcDtzZWdtZW50IDEgYW5kIHNlZ21lbnQgMywgdGhlIHRl
eHQgJnF1b3Q7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkltcGxlbWVudGF0aW9ucw0KIE1BWSBob2xk
IG9udG8gc3VjaCB1bm1hcHBlZCBkYXRhIGZvciBhIHNob3J0IHdoaWxlIGluJm5ic3A7dGhlIGV4
cGVjdGF0aW9uIHRoYXQgYSBtYXBwaW5nIHdpbGwgYXJyaXZlIHNob3J0bHkuLiAmcXVvdDsmbmJz
cDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+Y2FuIGJlIGFwcGxpZWQgdG8gdGhlIHNlZ21lbnQgMS4g
QXMgYSByZXN1bHQsIHRoZSBzZWdtZW50IDEgd29uJ3QgYmUgZGlzY2FyZGVkLiZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxlbT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5ZZXMuJm5ic3A7IFNvLCBzZWdtZW50IDEgbWF5IGJl
IGtlcHQgaW4gdGhlIGRhdGEgcmVjZWl2ZXIncyBidWZmZXIgaW4gZXhwZWN0YXRpb24gdGhhdCBp
dHMgbWFwcGluZyB3aWxsIGFycml2ZSBzaG9ydGx5LiBBbmQgaW4gdGhlIGV4YW1wbGUgdGhhdCB3
ZSBhcmUgcmVmZXJyaW5nIHRvLCB0aGUgZGF0YSBzZW5kZXINCiB3aWxsIG5vdCBiZSBhYmxlIHRv
IGluY2x1ZGUgdGhlIG1hcCBmb3IgdGhlIGRhdGEgaW4gc2VnbWVudCAxIGluIHNlZ21lbnQgMyBv
ciBhbnkgaGlnaGVyIHNlZ21lbnQuPC9zcGFuPjwvZW0+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
Mi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PGVtPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPlJlZ2FyZHMsPC9zcGFuPjwvZW0+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGVtPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkFuaWw8L3NwYW4+PC9lbT48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNl
cmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5Ib3dldmVyLCB0aGlzIG1pZ2h0IGJlIGNv
bnRyYWRpY3Qgd2l0aCB0aGUgbmV3IHRleHRzIEFsYW4gcHJvcG9zZWQ/IE9yLCBhbSBJIG1pc3Np
bmcgc29tZXRoaW5nPzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPlRoYW5rcyw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj4tLTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPllvc2hpPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+T24gU3VuLCBGZWIg
MiwgMjAyMCBhdCA4OjQyIEFNIFYgQW5pbCBLdW1hciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaWxA
Y3NpcjRwaS5pbiIgdGFyZ2V0PSJfYmxhbmsiPmFuaWxAY3NpcjRwaS5pbjwvYT4mZ3Q7IHdyb3Rl
OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBj
bSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJp
ZiI+SGkgWW9zaGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VGhhbmtzIGZvciB0aGlzIHBv
aW50LiBJbiBmYWN0LCBJIGhhZCBpbml0aWFsbHkgbm90IHRob3VnaHQgb2YgYSBzY2VuYXJpbywg
d2hlcmUgdGhlIG1hcCBpcyBiZWluZyBkZWxpdmVyZWQgdGhyb3VnaCBhIHJldHJhbnNtaXR0ZWQg
ZGF0YSBwYWNrZXQgd2hpbGUgaXRzIGZpcnN0IHRyYW5zbWlzc2lvbiBkaWQNCiBub3QgaW5jbHVk
ZSB0aGUgbWFwLiBOb3cgSSBhbSBqdXN0IHNlZWluZyB0aGUgZG9jdW1lbnQgKFJGQyA2ODI0LWJp
cykgaW4gdGhpcyBjb250ZXh0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPk15IHVuZGVyc3Rh
bmRpbmcgaXMgdGhhdCBpbiBzY2VuYXJpb3MgbGlrZSB3aGF0IEkgZGVzY3JpYmVkIGluIG15IHBy
ZXZpb3VzIG1haWwsIFJTVCBpcyBsaWtlbHkgdG8gaGFwcGVuIHdoZXRoZXIgd2UgZXhwbGljaXRs
eSBzdGF0ZSBzbyBvciBub3QuIFBsZWFzZSBzZWUgdGhlIHBhcmFncmFwaCBjb250YWluaW5nDQog
dGhlIGJlbG93IHRleHQgaW4gUkZDIDY4MjQtYmlzLiAmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj4mcXVvdDtJZiBhIG1hcHBpbmcgZm9yIHRoYXQgc3ViZmxvdy1sZXZlbCBzZXF1ZW5j
ZSBzcGFjZSBkb2VzIG5vdCBhcnJpdmUgd2l0aGluIGEgcmVjZWl2ZSB3aW5kb3cgb2YgZGF0YSwg
dGhhdCBzdWJmbG93IFNIT1VMRCBiZSB0cmVhdGVkIGFzIGJyb2tlbiwgY2xvc2VkIHdpdGggYSBS
U1QsIGFuZCBhbnkgdW5tYXBwZWQNCiBkYXRhIHNpbGVudGx5IGRpc2NhcmRlZC4mcXVvdDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMt
c2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj5pZiB3ZSBhc3N1bWUgdGhhdCB0aGUgbWFwIGlzIGluY2x1
ZGVkIHdoaWxlIHJldHJhbnNtaXR0aW5nIHRoZSBkYXRhIChldmVuIHRob3VnaCB0aGUgZmlyc3Qg
dHJhbnNtaXNzaW9uIGRpZCBub3QgY29udGFpbiB0aGUgbWFwIGZvciBzb21lIHJlYXNvbnMpLCAm
bmJzcDt3ZSBjb3VsZCBhcmd1ZSB0aGF0IFJTVCBjb3VsZA0KIGJlIGF2b2lkZWQgcHJvdmlkZWQg
dGhhdCB0aGUgcmV0cmFuc21pc3Npb24gaXMgdHJpZ2dlcmVkIHdpdGhpbiBhIHJlY2VpdmUgd2lu
ZG93IG9mIGRhdGEuIEJ1dCB0aGUgcXVlc3Rpb24gaGVyZSB3b3VsZCBiZSBob3cgYW5kIHdoZW4g
d2lsbCB0aGUgcmV0cmFuc21pc3Npb24gdGFrZSBwbGFjZS4gSW4gdGhpcyBjYXNlLCB0aGUgc3Vi
ZmxvdyBtYXkgbm90IGluaXRpYXRlIHRoZSByZXRyYW5zbWlzc2lvbiBvZiBkYXRhIGJ5IGl0cyBv
d24gKGkuLmUuLA0KIG5vIHJldHJhbnNtaXNzaW9uIGR1ZSB0byB0aHJlZSBkdXBsaWNhdGUgQUNL
cyBvciBSVE8gZXhwaXJ5IGF0IHN1YmZsb3cgbGV2ZWwpIGFzIHRoZXJlIGlzIG5vIHNlZ21lbnQg
bG9zcyBhdCBzdWJmbG93IGxldmVsIHNlcXVlbmNlIHNwYWNlLiBTbyB0aGVyZSBjb3VsZCBiZSBh
IGhpZ2ggcG9zc2liaWxpdHkgb2YgUlNUIGhhcHBlbmluZyBldmVuIGJlZm9yZSB0aGUgbWFwIGRl
bGl2ZXJ5IHRocm91Z2ggcmV0cmFuc21pc3Npb24uJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZiI+V2l0aCByZWdhcmRzLCZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkFuaWw8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXYgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImNlbnRlciIgc3R5bGU9InRleHQtYWxpZ246Y2Vu
dGVyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OyxzYW5zLXNlcmlmIj4NCjxociBzaXplPSIyIiB3aWR0aD0iMTAwJSIgYWxpZ249ImNl
bnRlciIgaWQ9ImdtYWlsLW1fLTU0MDY1NDM1NTY3Mzc3MjIwMWdtYWlsLW1fODc3MzM1NzQzOTc3
NzA4MTU5MGdtYWlsLW1fMjE4MDg2NTk2OTUxNzI0NTAxZ21haWwtbV8yOTgyMjY3MDMzNTc3OTAy
OTg1endjaHIiPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPiZxdW90O1lv
c2hpZnVtaSBOaXNoaWRhJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86bnNkLmlldGZAZ21haWwu
Y29tIiB0YXJnZXQ9Il9ibGFuayI+bnNkLmlldGZAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5U
bzogPC9iPiZxdW90O1YgQW5pbCBLdW1hciZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaWxA
Y3NpcjRwaS5pbiIgdGFyZ2V0PSJfYmxhbmsiPmFuaWxAY3NpcjRwaS5pbjwvYT4mZ3Q7PGJyPg0K
PGI+Q2M6IDwvYj4mcXVvdDthbGFuIGZvcmQmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzphbGFu
LmZvcmRAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+YWxhbi5mb3JkQGdtYWlsLmNvbTwvYT4m
Z3Q7LCAmcXVvdDttdWx0aXBhdGh0Y3AmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzptdWx0aXBh
dGh0Y3BAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tdWx0aXBhdGh0Y3BAaWV0Zi5vcmc8L2E+
Jmd0Ozxicj4NCjxiPlNlbnQ6IDwvYj5TYXR1cmRheSwgRmVicnVhcnkgMSwgMjAyMCAzOjM5OjUx
IEFNPGJyPg0KPGI+U3ViamVjdDogPC9iPlJlOiBbbXVsdGlwYXRodGNwXSBSRkM2ODI0YmlzIGVk
aXRzIGJhc2VkIG9uIGltcGxlbWVudGF0aW9uIGZlZWRiYWNrPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkhpIEFuaWwsPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZiI+SSBoYXZlIGEgcXVlc3Rpb24gYWJvdXQgeW91ciBwcm9wb3NlZCB0ZXh0Ljxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj5JIGFtIGFjdHVhbGx5IHdvbmRlcmluZyBpZiB3ZSByZWFs
bHkgd2FudCB0byB0ZXJtaW5hdGUgY29ubmVjdGlvbiBoZXJlLiZuYnNwOzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNl
cmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZiI+VGhlIHBhY2tldHMgd2l0aG91dCBwcm9wZXIgbWFwcGluZ3Mg
d2lsbCBiZSB0cmVhdGVkIGFzIGludmFsaWQgYW5kIHdpbGwgYmUgZGlzY2FyZGVkLiZuYnNwOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPklmIGFuIGltcGxlbWVudGF0aW9uIGZhaWxlZCB0byBhdHRhY2ggcHJv
cGVyIG1hcHBpbmcgZm9yIHNvbWUgcmVhc29ucyAoZS5nLiBvcHRpb24gc3BhY2UpLCBpdCBtaWdo
dCBiZSBhYmxlIHRvIGF0dGFjaCB0aGUgcHJvcGVyIG9uZSB3aGVuIGl0IHJldHJhbnNtaXRzIHRo
ZSBwYWNrZXRzLiBUaGlzIGFsc28NCiBsb29rcyBvayB0byBtZS48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj5JIGRvbid0IGhhdmUgc3Ryb25nIHByZWZlcmVuY2UgZm9yIHRoaXMuIEJ1dCwgZG8g
d2UgaGF2ZSBhIHJlYXNvbiB0byB0ZXJtaW5hdGUgY29ubmVjdGlvbj88bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj5UaGFua3MsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+LS08bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5Z
b3NoaTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5PbiBNb24sIEphbiAxMywgMjAy
MCBhdCAxMDoyOCBBTSBWIEFuaWwgS3VtYXIgJmx0OzxhIGhyZWY9Im1haWx0bzphbmlsQGNzaXI0
cGkuaW4iIHRhcmdldD0iX2JsYW5rIj5hbmlsQGNzaXI0cGkuaW48L2E+Jmd0OyB3cm90ZTo8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4w
cHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkhp
LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+SSBoYXZlIHNvbWUgcG9pbnRzIHJlbGF0ZWQgdG8g
dGhlICZuYnNwO21vZGlmaWNhdGlvbnMgKENoYW5nZSAyKSBiZWluZyBwcm9wb3NlZCBvbiBkYXRh
IHNlcXVlbmNlIG1hcC4gUGxlYXNlIHNlZSB0aGVtIGlubGluZS4mbmJzcDs8c3BhbiBzdHlsZT0i
Y29sb3I6YmxhY2s7YmFja2dyb3VuZDp3aGl0ZSI+VGhvdWdoIEkgYW0NCiBwdXR0aW5nIGZvcndh
cmQgdGhlIGJlbG93IHBvaW50cywgaWYgdGhlIGNvbnNlbnN1cyBpcyBpbiBmYXZvdXIgb2YgdGhl
IHByb3Bvc2VkIGNoYW5nZSBmb3IgcmVkdWNpbmcgaW1wbGVtZW50YXRpb24gY29tcGxleGl0eSwg
SSBhbSBhbHNvIE9LIHdpdGggdGhhdCBhcyB3ZWxsLiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249
ImNlbnRlciIgc3R5bGU9InRleHQtYWxpZ246Y2VudGVyIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4NCjxociBz
aXplPSIyIiB3aWR0aD0iMTAwJSIgYWxpZ249ImNlbnRlciIgaWQ9ImdtYWlsLW1fLTU0MDY1NDM1
NTY3Mzc3MjIwMWdtYWlsLW1fODc3MzM1NzQzOTc3NzA4MTU5MGdtYWlsLW1fMjE4MDg2NTk2OTUx
NzI0NTAxZ21haWwtbV8yOTgyMjY3MDMzNTc3OTAyOTg1Z21haWwtbV83Njg3MTg0MzgyMjk5NTk2
Nzc0endjaHIiPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWYiPkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPiZxdW90O2Fs
YW4gZm9yZCZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFsYW4uZm9yZEBnbWFpbC5jb20iIHRh
cmdldD0iX2JsYW5rIj5hbGFuLmZvcmRAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5UbzogPC9i
PjxhIGhyZWY9Im1haWx0bzptdWx0aXBhdGh0Y3BAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5t
dWx0aXBhdGh0Y3BAaWV0Zi4ub3JnPC9hPjxicj4NCjxiPlNlbnQ6IDwvYj5UaHVyc2RheSwgSmFu
dWFyeSAyLCAyMDIwIDQ6MjE6MzIgQU08YnI+DQo8Yj5TdWJqZWN0OiA8L2I+W211bHRpcGF0aHRj
cF0gUkZDNjgyNGJpcyBlZGl0cyBiYXNlZCBvbiBpbXBsZW1lbnRhdGlvbiBmZWVkYmFjazxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkhpIGFsbCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+V2XigJlkIGxvdmUgdG8gZ2V0
IHRoaXMgdG8gYSBzdGF0ZSBvZiBjb21wbGV0aW9uIGFzIHNvb24gYXMgcG9zc2libGUsIGFuZCB0
byB0aGlzIGVuZCBJIGFtIHN0YXJ0aW5nIGEgbmV3IHRocmVhZCBvbiB0aGlzIHRvcGljLiBJbiBk
aXNjdXNzaW9uIHdpdGggdGhlIGNoYWlycywgaXQNCjxpPmlzIDwvaT5wb3NzaWJsZSB0byBtYWtl
IHRoZSBkZXNpcmVkIGNoYW5nZXMgaW4gQVVUSDQ4IGFzIGxvbmcgYXMgdGhlcmUgaXMgV0cgY29u
c2Vuc3VzLiBUaGUgZGlzY3Vzc2lvbiBzbyBmYXIgaGFzIGJlZW4gZmFpcmx5IGxpbWl0ZWQgaW4g
dGVybXMgb2YgcGFydGljaXBhdGlvbi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5JIHdvdWxk
IGFzayB0aGUgY2hhaXJzIHBsZWFzZSBpZiBpdCB3YXMgcG9zc2libGUgdG8gc3BlY2lmeSBhIHRp
bWUgYm91bmQgZm9yIHRoaXMgZGlzY3Vzc2lvbiBhbmQgYSBkZWZhdWx0IGNvbmNsdXNpb24uPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+UmVnYXJkaW5nIHRoZSBjaGFuZ2VzLCBpbiBzdW1tYXJ5
LCB0aGVyZSBhcmUgdHdvIGFyZWFzIHdoZXJlIGNoYW5nZXMgaGF2ZSBiZWVuIHJlcXVlc3RlZCBi
eSB0aGUgaW1wbGVtZW50YXRpb24gY29tbXVuaXR5LiBBcyB3ZSBhcmUgdGhlIElFVEYgd2Ugb2J2
aW91c2x5IGhhdmUgc3Ryb25nIGZvY3VzIG9uDQog4oCccnVubmluZyBjb2Rl4oCdIGFuZCBzbyBl
YXNlIG9mIGltcGxlbWVudGluZyBzdGFuZGFyZHMtY29tcGxpYW50IGNvZGUgaXMgc3Ryb25nbHkg
ZGVzaXJhYmxlLiBIb3dldmVyLCB3ZSBkbyBub3Qgd2lzaCB0byByZWR1Y2UgZnVuY3Rpb25hbGl0
eSBhZ3JlZWQgYnkgdGhlIElFVEYgY29tbXVuaXR5IGlmIGl0IGlzIGNvbnNpZGVyZWQgYSByZXF1
aXJlZCBmZWF0dXJlIGJ5IHRoZSBjb21tdW5pdHkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5DaGFuZ2UgMTwvc3Bhbj48L2I+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206
MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj5DaGFuZ2UgdGhlIHNlbnRlbmNlIHJlYWRpbmc6PGJyPg0K
PGJyPg0KPGk+Jm5ic3A7ICZuYnNwO0lmIEIgaGFzIGRhdGEgdG8gc2VuZCBmaXJzdCwgdGhlbiB0
aGUgcmVsaWFibGUgZGVsaXZlcnkgb2YgdGhlIEFDSyAmIzQzOyBNUF9DQVBBQkxFIGNhbiBiZSBp
bmZlcnJlZCBieSB0aGUgcmVjZWlwdCBvZiB0aGlzIGRhdGEgd2l0aCBhbiBNUFRDUCBEYXRhIFNl
cXVlbmNlIFNpZ25hbCAoRFNTKSBvcHRpb24gKFNlY3Rpb24gMy4zKS4mbmJzcDs8YnI+DQo8L2k+
PGJyPg0KVG86PGJyPg0KPGJyPg0KPGk+Jm5ic3A7ICZuYnNwO0lmIEIgaGFzIGRhdGEgdG8gc2Vu
ZCBmaXJzdCwgdGhlbiB0aGUgcmVsaWFibGUgZGVsaXZlcnkgb2YgdGhlIEFDSyAmIzQzOyBNUF9D
QVBBQkxFIGlzIGVuc3VyZWQgYnkgdGhlIHJlY2VpcHQgb2YgdGhpcyBkYXRhIHdpdGggYW4gTVBU
Q1AgRGF0YSBTZXF1ZW5jZSBTaWduYWwgKERTUykgb3B0aW9uIChTZWN0aW9uIDMuMykgY29udGFp
bmluZyBhIERBVEFfQUNLIGZvciB0aGUgTVBfQ0FQQUJMRSAod2hpY2ggaXMgdGhlIGZpcnN0IG9j
dGV0IG9mDQogdGhlIGRhdGEgc2VxdWVuY2UmbmJzcDtzcGFjZSkuPC9pPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPldoYXQgdGhpcyBtZWFuczo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UaGUgY3VycmVu
dCB0ZXh0IGlzIGNvbmNlcm5lZCBvbmx5IHdpdGggZW5zdXJpbmcgYSBwYXRoIGlzIE1QVENQIGNh
cGFibGUsIGFuZCBzbyBvbmx5IGNhcmVzIHRoYXQgRFNTIG9wdGlvbiBvY2N1cnMgb24gYSBkYXRh
IHBhY2tldC4gSG93ZXZlciwgdGhlIE1QX0NBUEFCTEUgb3B0aW9uIGlzIGRlZmluZWQNCiB0byBv
Y2N1cHkgdGhlIGZpcnN0IG9jdGV0IG9mIGRhdGEgc2VxdWVuY2Ugc3BhY2UgYW5kIHRodXMsIGlm
IGFuYWxvZ291cyB0byBUQ1AsIG11c3QgYmUgYWNrbm93bGVkZ2VkLiAmZ3Q7RnJvbSBhbiBpbXBs
ZW1lbnRhdGlvbiBwb2ludCBvZiB2aWV3IGl0IHdvdWxkIG1ha2Ugc2Vuc2Ugbm90IHRvIGhhdmUg
dGhpcyBoYW5naW5nIGFyb3VuZCBmb3JldmVyIGFuZCBpbnN0ZWFkIGRlZmluZSBpdCBpcyBhY2tu
b3dsZWRnZWQgYXQgdGhlIGNvbm5lY3Rpb24NCiBsZXZlbCBhcyBzb29uIGFzIHJlY2VpdmVkLiBU
aGlzIGNoYW5nZSBlbnN1cmVzIHRoZSBmaXJzdCBkYXRhIHBhY2tldCBhbHNvIERBVEFfQUNLcyB0
aGlzIE1QX0NBUEFCTEUgb2N0ZXQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmIj5DaGFuZ2UgMjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+Q2hhbmdlIHRoZSBzZW50
ZW5jZSByZWFkaW5nOjxicj4NCjxicj4NCjxpPiZuYnNwOyAmbmJzcDtBIERhdGEgU2VxdWVuY2Ug
TWFwcGluZyBkb2VzIG5vdCBuZWVkIHRvIGJlIGluY2x1ZGVkIGluIGV2ZXJ5IE1QVENQIHBhY2tl
dCwgYXMgbG9uZyBhcyB0aGUgc3ViZmxvdyBzZXF1ZW5jZSBzcGFjZSBpbiB0aGF0IHBhY2tldCBp
cyBjb3ZlcmVkIGJ5IGEgbWFwcGluZyBrbm93biBhdCB0aGUgcmVjZWl2ZXIuPC9pPjxicj4NCjxi
cj4NClRvOjxicj4NCjxicj4NCjxpPiZuYnNwOyAmbmJzcDtUaGUgbWFwcGluZyBwcm92aWRlZCBi
eSBhIERhdGEgU2VxdWVuY2UgTWFwcGluZyBNVVNUIGFwcGx5IHRvIHNvbWUgb3IgYWxsIG9mIHRo
ZSBzdWJmbG93IHNlcXVlbmNlIHNwYWNlIGluIHRoZSBUQ1Agc2VnbWVudCB3aGljaCBjYXJyaWVz
IHRoZSBvcHRpb24uIEl0IGRvZXMgbm90IG5lZWQgdG8gYmUgaW5jbHVkZWQgaW4gZXZlcnkgTVBU
Q1AgcGFja2V0LCBhcyBsb25nIGFzIHRoZSBzdWJmbG93IHNlcXVlbmNlIHNwYWNlIGluIHRoYXQg
cGFja2V0DQogaXMgY292ZXJlZCBieSBhIG1hcHBpbmcga25vd24gYXQgdGhlIHJlY2VpdmVyLjxi
cj4NCjwvaT48YnI+DQpXaGF0IHRoaXMgbWVhbnM6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+
VGhlIGN1cnJlbnQgdGV4dCBkb2VzIG5vdCBwbGFjZSBhbnkgcmVzdHJpY3Rpb25zIG9uIHdoZXJl
IGEgbWFwcGluZyBjb3VsZCBhcHBlYXIuIEluIHRoZW9yeSBhIHNlbmRlciBjb3VsZCBkZWZpbmUg
YSB0aG91c2FuZCBkaWZmZXJlbnQgbWFwcGluZ3MgdXAgZnJvbnQsIHNlbmQgdGhlbSBhbGwsIGFu
ZCBleHBlY3QNCiBhIHJlY2VpdmVyIHRvIHN0b3JlIHRoaXMgYW5kIHJlYXNzZW1ibGUgZGF0YSBh
Y2NvcmRpbmcgdG8gdGhlc2UgbWFwcGluZ3MgYXMgaXQgYXJyaXZlcy4gSW5kZWVkLCB0aGlzIHdh
cyBuZXZlciBleHBsaWNpdGx5IGRpc2FsbG93ZWQgc2luY2UgaXQg4oCcbWlnaHQgaGF2ZSBiZWVu
IHVzZWZ1bOKAnS4gVGhlIGltcGxlbWVudGF0aW9uIGNvbW11bml0eSwgaG93ZXZlciwgaGFzIGV4
cHJlc3NlZCBjb25jZXJucyBvdmVyIHRoZSBkaWZmaWN1bHR5IG9mIGltcGxlbWVudGluZw0KIHRo
aXMgb3Blbi1lbmRlZGx5LiBIb3cgbWFueSBtYXBwaW5ncyBpcyBpdCByZWFzb25hYmxlIHRvIHN0
b3JlPyBJcyB0aGVyZSBhIERvUyByaXNrIGhlcmU/IEluc3RlYWQsIGl0IGhhcyBiZWVuIHJlcXVl
c3RlZCB0aGF0IHRoZWUgc3BlY2lmaWNhdGlvbiByZXN0cmljdHMgdGhlIHBsYWNlbWVudCBvZiB0
aGUgRFNTIG9wdGlvbiB0byBiZWluZyB3aXRoaW4gdGhlIHN1YmZsb3cgc2VxdWVuY2Ugc3BhY2Ug
dG8gd2hpY2ggaXQgYXBwbGllcy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5CZWxvdyBhcmUg
bXkgY29tbWVudHMgb24gdGhpcy4gSSBoYWQgc2hhcmVkIHNvbWUgb2YgdGhlc2UgcG9pbnRzIGlu
IGEgcHJldmlvdXMgdGhyZWFkIHRoYXQgeW91IGhhZCBpbml0aWF0ZWQgaW4gdGhlIHNhbWUgY29u
dGV4dC4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UcmFuc21pdHRpbmcgbGFyZ2Ug
bnVtYmVyIG9mIG5vbi1jb250aWd1b3VzIGRhdGEgc2VxdWVuY2UgbWFwcyBjb3VsZCBiZSBhIG1p
c2JlaGF2aW91ciAobWFwLWZsb29kaW5nKSwgdGhvdWdoIGl0IGlzIG5vdCBjbGVhciB3aGV0aGVy
IHRoaXMgY2FuIGdvIHRvIHRoZSBleHRlbnQgb2YgY2F1c2luZyBhIHBvdGVudGlhbA0KIERvUyB0
byB0aGUgZGF0YSByZWNlaXZlci4gU28gc29tZSBzb3J0IG9mIHJlc3RyaWN0aW9uIG9uIHRoaXMg
Y291bGQgYmUgdXNlZnVsLiZuYnNwOyBPbmUgYXBwcm9hY2ggY291bGQgYmUgdG8gaW5zaXN0IHRo
YXQgdGhlIGRhdGEgc2VuZGVyIHNob3VsZCBlbnN1cmUgdGhhdCB0aGUgbWFwIGJlaW5nIHRyYW5z
bWl0dGVkIGlzIGZvciBpbi13aW5kb3cgZGF0YSwgYXMgcGVyIHRoZSByZWNlaXZlciBhZHZlcnRp
c2VkIHdpbmRvdy4gQSByZWNlaXZlciBzaG91bGQNCiBhbnlob3cgYmUgd2lsbGluZyB0byBzdG9y
ZSB0aGUgbWFwcyBmb3IgaW4td2luZG93IGRhdGEgdG8gZGVhbCB3aXRoIHBhY2tldCBsb3NzLiBG
b3IgZXhhbXBsZSwgd2hlbiBhIHdpbmRvdyBvZiBkYXRhIHNlZ21lbnRzIChzYXkgMSB0byA2NCkg
aXMgdHJhbnNtaXR0ZWQsIGVhY2ggY2FycnlpbmcgaXRzIGNvcnJlc3BvbmRpbmcgbWFwLCBhbmQg
c2VnbWVudC0xIGlzIGxvc3QsIHRoZSBtYXBzIGZvciB0aGUgcmVtYWluaW5nIDYzIG5lZWQgdG8g
YmUNCiBzdG9yZWQgdGlsbCB0aGUgbG9zdCBzZWdtZW50IGlzIHJldHJhbnNtaXR0ZWQuIE9mIGNv
dXJzZSwgaW4gdGhpcyBjYXNlIHRoZSBtYXBzIHdpbGwgYmUgc3RvcmVkIGF0IHRoZSByZWNlaXZl
ciBzaWRlIGFsb25nIHdpdGggdGhlaXIgY29ycmVzcG9uZGluZyBkYXRhLiBCdXQgdGhlIG5lZWQg
dG8gc3RvcmUgbXVsdGlwbGUgbWFwcyBmb3IgaW4td2luZG93IGRhdGEgd291bGQgc3RpbGwgYmUg
dGhlcmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjaztiYWNrZ3JvdW5kOndo
aXRlIj5UaGUgcHJvYmxlbSB3aXRoIHRoZSBwcm9wb3NlZCBjaGFuZ2UgKHJlc3RyaWN0aW9uKSBp
cyB0aGF0IGEgZGF0YSBzZW5kZXIgbWF5IGZpbmQgaXQgZGlmZmljdWx0LCBpbiBjYXNlIGEgbmVl
ZCBhcmlzZSB0byBzbGlnaHRseSBkZWxheSB0aGUgbWFwIGRlbGl2ZXJ5DQogYnkgZmV3IHNlZ21l
bnRzLCBpLmUuLCBzZW5kaW5nIHNvbWUgZGF0YSBmaXJzdCB3aXRob3V0IG1hcCwgYW5kIHRoZW4g
c2VuZCB0aGUgY29ycmVzcG9uZGluZyBtYXAgaW4gYSBsYXRlciBzZWdtZW50LCBhcyBzaG93biBi
ZWxvdzo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+
c3ViZmxvdy0xOiZuYnNwOyAmbmJzcDsgJm5ic3A7IHNlZ21lbnQtMSZuYnNwOyZuYnNwOyZuYnNw
OyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgc2VnbWVudC0zJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHNlZ21l
bnQtNCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHNlZ21lbnQtNzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlm
Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtieXRlczoxLTEwMCAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGJ5dGVzOjIwMS0zMDAgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Ynl0ZXM6MzAxLTQw
MCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IGJ5dGVzOjYwMS03MDA8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91
bmQ6d2hpdGUiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7Jm5ic3A7bm8gbWFwICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7bWFw
IGZvciAxLTEwMCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDttYXAgZm9yIDIwMS00MDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgbWFwIGZvciA2MDEtNzAwPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hp
dGUiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29l
IFVJJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+c3ViZmxvdy0yOiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwO3NlZ21lbnQtMiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHNlZ21lbnQtNSAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgc2VnbWVudC02ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgc2VnbWVudC04PC9zcGFuPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNh
bnMtc2VyaWYiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2J5dGVzOiAxMDEtMjAw
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgYnl0ZXM6NDAxLTUwMCZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgYnl0ZXM6IDUwMS02MDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2J5dGVzOjcwMS04MDAmbmJzcDsmbmJzcDsmbmJz
cDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
U2Vnb2UgVUkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtTZWdvZSBVSSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwO21hcCBmb3IgMTAxLTIwMCAmbmJzcDsgJm5ic3A7ICZuYnNwOyBtYXAgZm9yIDQw
MS02MDAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtubyBtYXAgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO21hcCBmb3IgNzAxLTgwMDwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtTZWdvZSBV
SSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7U2Vnb2UgVUkmcXVvdDssc2Fu
cy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2Vy
aWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZiI+SW4gdGhlIGFib3ZlIGNhc2UsIHNlZ21lbnQtMSBnb2VzIHdp
dGhvdXQgbWFwIGFuZCBpdHMgbWFwIGlzIGluY2x1ZGVkIGxhdGVyIGluIHNlZ21lbnQtMywgdGhl
IG5leHQgZGF0YSBzZWdtZW50IGluIHRoZSBzYW1lIHN1YmZsb3cuIEZ1cnRoZXIsICZuYnNwO2lu
IHRoZSBhYm92ZSBzY2hlZHVsaW5nIHBhdHRlcm4sDQogdGhlIG1hcCBpbiBzZWdtZW50LTMgY2Fu
bm90IGNvdmVyIHRoZSAmbmJzcDtkYXRhIGluIHNlZ21lbnQtMSBhbmQgc2VnbWVudC0zLCBhcyBz
b21lICZuYnNwO2RhdGEgaW4gYmV0d2VlbiAoc2VnbWVudC0yKSBpcyB0cmFuc21pdHRlZCB0aHJv
dWdoIGFub3RoZXIgc3ViZmxvdy4mbmJzcDsgV2l0aCB0aGUgcHJvcG9zZWQgY2hhbmdlLCB0aGUg
bWFwIGluIHNlZ21lbnQtMyB3aWxsIGJlY29tZSBpbnZhbGlkIGFuZCB0aGlzIHdpbGwgZXZlbnR1
YWxseSBicmVhayBzdWJmbG93LTEsDQogdGhvdWdoIHRoaXMgY291bGQgYmUgYSBjb3JuZXIgY2Fz
ZS4uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+VGhlIHF1ZXN0aW9uIGF0IHRoaXMgc3RhZ2Ug
aXMgd2h5IHdvdWxkIHNlZ21lbnQtMSBiZSB0cmFuc21pdHRlZCB3aXRob3V0IGl0cyBtYXAuIElu
IHRoZSBjYXNlIG9mIGJpZGlyZWN0aW9uYWwgZGF0YSB0cmFuc2ZlciwgdGhlcmUgY291bGQgYmUg
YSBuZWVkIHRvIHBhY2sgYm90aCB0aW1lc3RhbXAgYW5kDQogU0FDSyAmbmJzcDtvcHRpb25zIGlu
IGEgZGF0YSBzZWdtZW50LCBpLmUuLCBwaWdneWJhY2tpbmcgb2YgJm5ic3A7U0FDSyB3aXRoIGRh
dGEuIElmIHdlIGNvbnNpZGVyIHRoYXQgdGltZXN0YW1wIHRha2VzIDEyIGJ5dGVzIGFuZCBTQUNL
LCBldmVuIHdpdGggc2luZ2xlIGJsb2NrLCAmbmJzcDt0YWtlcyBhbm90aGVyIDEwIGJ5dGVzLCB0
aGUgcmVtYWluaW5nIDE4IGJ5dGVzIG9wdGlvbiBzcGFjZSBpcyBub3QgYWRlcXVhdGUgdG8gY2Fy
cnkgZGF0YSBzZXF1ZW5jZSBzaWduYWwNCiB3aXRoIG1hcCwgZXNwZWNpYWxseSB3aGVuIERTTiBp
cyA2NCBiaXQgbG9uZy4gU28gdGhlIGRlbGl2ZXJ5IG9mIGVpdGhlciBvZiB0aGUgdHdvIChTQUNL
IG9yIG1hcCkgd291bGQgYmUgZGVsYXllZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5BcyBm
YXIgYXMgSSB1bmRlcnN0YW5kLCBSRkMgMjAxOCAoVENQIFNlbGVjdGl2ZSBBY2tub3dsZWRnZW1l
bnQgT3B0aW9ucykgaW1wbGllcyB0aGF0IFNBQ0sgc2hvdWxkIG5vdCBiZSBkZWxheWVkLiBJdCBz
dGF0ZXMgJnF1b3Q7SWYgc2VudCBhdCBhbGwsIFNBQ0sgb3B0aW9ucyBTSE9VTEQgYmUgaW5jbHVk
ZWQgaW4NCiBhbGwgQUNLcyB3aGljaCBkbyBub3QgQUNLIHRoZSBoaWdoZXN0IHNlcXVlbmNlIG51
bWJlciBpbiB0aGUgZGF0YSByZWNlaXZlcidzIHF1ZXVlJnF1b3Q7LiBJdCBhbHNvIHNheXMgJnF1
b3Q7SWYgZGF0YSByZWNlaXZlciBnZW5lcmF0ZXMgU0FDSyBvcHRpb25zIHVuZGVyIGFueSBjaXJj
dW1zdGFuY2UsIGl0IFNIT1VMRCBnZW5lcmF0ZSB0aGVtIHVuZGVyIGFsbCBwZXJtaXR0ZWQgY2ly
Y3Vtc3RhbmNlcyZxdW90Oy4gJm5ic3A7IFNvLCBhcyBwYXJ0IG9mIG1lZXRpbmcgdGhlIFJGQw0K
IDIwMTggcmVxdWlyZW1lbnRzLCBpZiB0aGUgY29tYmluYXRpb24gb2YgU0FDSyBhbmQgdGltZXN0
YW1wIGlzIGdpdmVuIHByZWZlcmVuY2Ugb3ZlciBEU1MsIGRhdGEgc2VnbWVudHMgY291bGQgYmUg
dHJhbnNtaXR0ZWQgd2l0aG91dCB0aGVpciBtYXAuJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1z
ZXJpZiI+QW5vdGhlciBjYXNlIG9mIGRlbGF5aW5nIG1hcCBjb3VsZCBhcmlzZSBpZiB0aGUgZGF0
YSBzZW5kZXIgcHJlZmVycyB0byBzZW5kIEFERF9BRERSIG9wdGlvbiwgaW5zdGVhZCBvZiBtYXAs
IGluIGEgZGF0YSBzZWdtZW50LiBJdCBpcyBuaWNlIHRoYXQgQUREX0FERFIgb3B0aW9uIGNhbiBi
ZSBkZWxpdmVyZWQNCiByZWxpYWJseSBpbiBhIHB1cmUgQUNLLCBidXQgSSB0aGluayB0aGlzIGlz
IG5vdCB0aGUgY2FzZSB3aXRoIERTUyBhdCBwcmVzZW50LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPklmIHdlIGFkb3B0IHRoZSBwcm9wb3NlZCBjaGFuZ2UsIEkgdGhpbmsgaXQgbWlnaHQgYWxz
byBiZSBoZWxwZnVsIHRvIHNwZWxsIG91dCBob3cgdGhlIHJlY2VpdmVyIGlzIHN1cHBvc2VkIHRv
IGJlaGF2ZSwgaWYgaXQgZ2V0cyBtYXBzIG5vdCBtZWV0aW5nIHRoZSBNVVNUIGNvbmRpdGlvbiBp
biB0aGUgcHJvcG9zZWQNCiBjaGFuZ2UuJm5ic3A7IEZvciBleGFtcGxlIHRlcm1pbmF0aW9uIG9m
IHRoZSBzdWJmbG93IHdpdGggTVBfVENQUlNUIG9wdGlvbiAoc2VjdGlvbiAzLjYgaW4gUkZDIDY4
MjQtYmlzKSB3aXRoIGFwcHJvcHJpYXRlIHJlYXNvbiBjb2RlIGFuZCBUIGZsYWcgdmFsdWUgdG8g
aW50aW1hdGUgdGhlIGRhdGEgc2VuZGVyIHRoZSBjYXVzZSBmb3Igc3ViZmxvdyB0ZXJtaW5hdGlv
bi4mbmJzcDsmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5XaXRoIHJlZ2FyZHMsPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5BbmlsPG86cD48
L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWYiPlBsZWFzZSBjYW4gbWVtYmVycyBvZiB0aGUgV0cgZXhwcmVzcyB3aGV0aGVyIHRoZXkgYXJl
IGhhcHB5IHdpdGggdGhlc2UgY2hhbmdlcywgb3IgY29uY2VybmVkLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWYiPkJlc3QgcmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5BbGFuPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48
YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xzxicj4NCm11bHRpcGF0aHRjcCBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86bXVs
dGlwYXRodGNwQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bXVsdGlwYXRodGNwQGlldGYub3Jn
PC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
bXVsdGlwYXRodGNwIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9tdWx0aXBhdGh0Y3A8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCm11bHRpcGF0aHRjcCBtYWlsaW5n
IGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnIiB0YXJnZXQ9
Il9ibGFuayI+bXVsdGlwYXRodGNwQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNwIiB0YXJnZXQ9Il9ibGFu
ayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3A8L2E+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1i
b3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXzxicj4NCm11bHRpcGF0aHRjcCBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVm
PSJtYWlsdG86bXVsdGlwYXRodGNwQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bXVsdGlwYXRo
dGNwQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vbXVsdGlwYXRodGNwIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3A8L2E+PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_LNXP123MB258793AE47D970277BAF3688EB110LNXP123MB2587GBRP_--


From nobody Tue Feb 18 08:10:57 2020
Return-Path: <Markus.Amend@telekom.de>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0672120815; Tue, 18 Feb 2020 08:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level: 
X-Spam-Status: No, score=-4.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 nF63H_wG-IxA; Tue, 18 Feb 2020 08:10:53 -0800 (PST)
Received: from mailout21.telekom.de (mailout21.telekom.de [194.25.225.215]) (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 10B601200E0; Tue, 18 Feb 2020 08:10:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1582042252; x=1613578252; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=iDoUlsI9RWLXLWmmMLwXHSELoIrrdPAwg01cEiOPLA8=; b=vKnylhfc9y+GT+J/mMdbNtuPNXk4Wcn7iGeF0xC+KKG8uEyUTpJMJBWI ZUQFoCZrR56GTe5Jh4RZQrICNPXYtbKFSLz3MwTjHZaDPRpdkoU9yrnIP G/JFnowGM3/uxdygUm7oh6lSM8CBk/ZbBaZmzZh7VtK9cgrIEN9dV4XM6 vCDxZRobCf762OLv5vLdDtgagUKoQZRoiB3sRVhzM/tw8+pjB65eLGJeQ k9x/E6RKqU10GK6hJP28VDu5bR7LngouVdf19h2XqineLTJSD5u8vuSZy kmGgQ6W1L9DmBki1W6a2u3SsINOoGMU1b74CnQ7a3UJUH4GfoF1RilI8z A==;
IronPort-SDR: SpdgZWJYfL0tugtGzYQFDhiO/y0NXCjQxYA5IjiW3ohNwkHcw99Dh/YNb5I5vKT/E0akruysWV ybtSHP2gEwYQ==
Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT21.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Feb 2020 17:10:49 +0100
IronPort-SDR: R5X8parCu76hHzHOmHqpu5CDkBRlILvzebiwuJAArWBVa/Mhuc9IuAOTZXYSWHsevZroo4h/dv ucq4PO7LHAQdd7J87MKfmoiJisSkCA+x0=
X-IronPort-AV: E=Sophos;i="5.70,456,1574118000"; d="scan'208";a="50212050"
X-MGA-submission: =?us-ascii?q?MDFTuwF+GEKZEIAErx0xV7gKWuM0RBGLKPBHHu?= =?us-ascii?q?LYCadKNC4xoB6YNgW/BfAq983/AKTKkI0onV9jlCjq04sm4anZi5pjFy?= =?us-ascii?q?R02ETlTRivngeyoWoIFZjMqQOlQXQJX78xf9x7/8Gm8HM3CAd7a1oNK2?= =?us-ascii?q?i7j7cCXCdpy76WSBqXgJNy9w=3D=3D?=
Received: from he105867.emea1.cds.t-internal.com ([10.169.119.44]) by qde0ps.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 18 Feb 2020 17:09:47 +0100
Received: from HE199743.EMEA1.cds.t-internal.com (10.169.119.51) by HE105867.emea1.cds.t-internal.com (10.169.119.44) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 18 Feb 2020 17:09:47 +0100
Received: from HE100181.emea1.cds.t-internal.com (10.171.40.15) by HE199743.EMEA1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 18 Feb 2020 17:09:47 +0100
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.21) by O365mail02.telekom.de (172.30.0.235) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 18 Feb 2020 17:09:47 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JS4VhHbtYehM8PT43WGFgNa3p/2E3NW7Or5bhzqPXaE/0J5CoFYAIfhS9fkoz0y6nBtGJAQ4TqRMHhVKtzKN0LMsGWNUkwDYSFlg9+FNDDx8TpguP4HntLtfLiHUAp2ZcJKJ1aK0LZNNHt0M2haR4R5NtYcvG0wMPYnBs/JAlxQ7otbI8t2OtdujVF3Viw8wLUlYq+SCep26JIhbYjmcE6ltvEk//2dJ3V/S0ldvuanzvzpPHoe+n1RZ2ZwZOB5RES8+SgUEBO/Ott5GHGAO0SvkpzPwfCygXzNZc78sRNgXsetpHo6GMsIivnsPFvOdDG0zPcod+32Adj9RgshWUQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iDoUlsI9RWLXLWmmMLwXHSELoIrrdPAwg01cEiOPLA8=; b=PRzYVqwrW2emq4J8aVQrebE3vPlHVJ8PUDI45xA7fxH9DPBZYoPeWFMrfsxf1BMHL9vwyog5husVEdWwGNzO0yG9gjw6ncf9+BfS+CqZNbVzpkv6PavVDlgaQ06SrZIob95e1kWQSNmoo/tOAaZV6V2FrI3wOxiDCCb/6Ic17riD/MDUPmnoFMLwAhWPjhdxsXlYa5g/Nyxx7Qiz3QbQ+bWTQ1H3MKtn+k6S6N801GBSdUFMvDywJ7uoxID/olHk2ACiYdh66T6StKfEDTelXNOCl+YeBgKUkv8lKYE8t51aw7OsqoYa41nHvUz8khSnASBZoz6TtFE1l1Y7F5SmMQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from LEJPR01MB0668.DEUPRD01.PROD.OUTLOOK.DE (10.158.140.136) by LEJPR01MB0875.DEUPRD01.PROD.OUTLOOK.DE (10.158.143.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.27; Tue, 18 Feb 2020 16:09:45 +0000
Received: from LEJPR01MB0668.DEUPRD01.PROD.OUTLOOK.DE ([fe80::5db7:bcde:416d:c264]) by LEJPR01MB0668.DEUPRD01.PROD.OUTLOOK.DE ([fe80::5db7:bcde:416d:c264%8]) with mapi id 15.20.2707.035; Tue, 18 Feb 2020 16:09:45 +0000
From: <Markus.Amend@telekom.de>
To: <hackathon@ietf.org>
CC: <kangjiao@huawei.com>, <multipathtcp@ietf.org>, <tcpm@ietf.org>, <tsvwg@ietf.org>
Thread-Topic: [hackathon] Evaluate MPTCP RobE at IETF107 hackathon
Thread-Index: AdXmcziGDRW63vL7RKSs5c8WW7zaaw==
Date: Tue, 18 Feb 2020 16:09:45 +0000
Message-ID: <LEJPR01MB066820E7805035785C782416FA110@LEJPR01MB0668.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Markus.Amend@telekom.de; 
x-originating-ip: [164.19.3.189]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 63bd034b-bfeb-4399-1589-08d7b48cf89a
x-ms-traffictypediagnostic: LEJPR01MB0875:
x-microsoft-antispam-prvs: <LEJPR01MB08752A8F2A6339C63460278FFA110@LEJPR01MB0875.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 031763BCAF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(376002)(396003)(346002)(136003)(189003)(199004)(966005)(86362001)(8676002)(478600001)(55016002)(2906002)(76116006)(54906003)(9686003)(33656002)(4326008)(64756008)(71200400001)(81166006)(81156014)(186003)(26005)(316002)(8936002)(7696005)(66946007)(5660300002)(6916009)(66476007)(4744005)(66556008)(66446008); DIR:OUT; SFP:1101; SCL:1; SRVR:LEJPR01MB0875; H:LEJPR01MB0668.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vgsEk0Xvhlmu0Dw2G1x0R/mEAItj5DnDIWJNfQvNje9s7r43K9ncmqZwPr5iZM0a5TStu9/7ZVOVBkmxa6//s3HE2+s3J2rX00J5fhKzLCsbz+hbC+YPlN0UKw4Gc1WxwUnWII8ihTWTIQNldF92ogKAM8aRJsu3GImRa1qUdqDDr+zbeYVUnIhC/Kh91vfZmCGlMRZMWik70abDQggs4sjSgiGGsM49ZEo9us7dBx1ASYihEJByvR1VBAbt0QoaUTmXCzkkMMAHYPLo5ZBP6dbIMUt8oLlSNIvUwo6m5FBc/6zkgUNZ/DYHQondzBKM6isx3DFriavQy1GCiBC09BkarMujms+M0NCa1ky49tybNKhDOyAOGvhvwllN03qf/9/TA/S5VvR4qXPzk7a9G9WNYOavgeU6E6lXTZXP/+3USEvq1pu4+cq5hYz78k+jt6zvrc8eXwgVYH8eO1Po0K9HhPk3bxaWBLZaypQIClWpHDTYeGO5MfHJI+dgdyOd+3hNsJlp/3aBMvsvuu8jiw==
x-ms-exchange-antispam-messagedata: tzMFqZMndhsp8nD81AZBjCJ24DrnZdgw89RlZq5LQwHgnTVWAJrUABXa7U7MbgrLJBO1uuP34qDX6xqj+fwgLMFiH5L+Z5Q0NmFBUKxZClddz6eunLD6r+lJr3J8kBVAVkTElxyXJRWYybiKnfvNRg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 63bd034b-bfeb-4399-1589-08d7b48cf89a
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2020 16:09:45.4703 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ogeo+VlrvHrnN/KnnmgDqhxQrslVvFzCutU3X47iWmM4GDPVIdcWI9G5c3bojhPAw5vhZLhA17lOu3fp4SLC8g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEJPR01MB0875
X-TM-SNTS-SMTP: FEAF04C746FABA3EFAB72E4D27755E351AB3AB4A5A41BC3489EA81EDD18CA3552000:8
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/0_yADWbU6INtUzoNohca6dvC08w>
Subject: [multipathtcp] [hackathon] Evaluate MPTCP RobE at IETF107 hackathon
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2020 16:10:55 -0000

Dear all,

I kindly ask anyone who is keen in improving further MPTCP to join us at th=
e IETF 107 hackathon. We focus on improving MPTCP's handshake procedure to =
become robust against link outages on the initially selected path for conne=
ction establishment. This feature we call MPTCP Robust session Establishmen=
t (RobE) which is drafted in [1].

During the Hackathon we provide a testbed [2] for evaluating the different =
solutions from [1] RobE_TIMER, RobE_SIM, RobE_eSIM and RobE_IPS for compari=
ng it with the existing MPTCP [3][4] and its reference implementation [5].

If this matches your interest please don't hesitate to contact Jiao <kangji=
ao@huawei.com> or me <markus.amend@telekom.de>.

Thanks.

BR

Jiao & Markus

[1] https://tools.ietf.org/html/draft-amend-mptcp-robe
[2] https://trac.ietf.org/trac/ietf/meeting/wiki/107hackathon/mptcp-robe/te=
stbed
[3] https://tools.ietf.org/html/rfc6824
[4] https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis
[5] https://github.com/multipath-tcp/mptcp




From nobody Wed Feb 19 07:43:57 2020
Return-Path: <alan.ford@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0BC0120026 for <multipathtcp@ietfa.amsl.com>; Wed, 19 Feb 2020 07:43:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 j6zBimpPe2C6 for <multipathtcp@ietfa.amsl.com>; Wed, 19 Feb 2020 07:43:50 -0800 (PST)
Received: from mail-qk1-x744.google.com (mail-qk1-x744.google.com [IPv6:2607:f8b0:4864:20::744]) (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 50CA4120129 for <multipathtcp@ietf.org>; Wed, 19 Feb 2020 07:43:50 -0800 (PST)
Received: by mail-qk1-x744.google.com with SMTP id c188so517553qkg.4 for <multipathtcp@ietf.org>; Wed, 19 Feb 2020 07:43:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=e1I32vJYz/17Qx2ZJbxUfm6XckB7OLlXLehbQD5nFK8=; b=jayr93uOeTgUHcHGylVeCAczyWdSS10sHyQHrIbzPHuthw/P2ymZsBy75TveuNzy94 iW5xVBSYvarNNE8OY1KkC1GQK0HJnPvD35aZCAwiKyqq2B8VCzlVxWf3tPwwSdl7jZOX U4hs1w+4kePFGnfdCkWR7a3L0saWaK76aJ4aBykgERlPrC+TnOm7/sJfKU1AudYJOJgs 3d05Ch9BbE4GAIA4ONplRhsZVJdLHOATg3RX/Sd0cT+pUiv/AkXzLZlXPA7At9PSP2zB USFJb3S0pLNHoQ3dAMYtfpy81tALs1dDZP9GqsijeTEWsuDi6SqAC1O6L4xILRzNjSDO w/+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=e1I32vJYz/17Qx2ZJbxUfm6XckB7OLlXLehbQD5nFK8=; b=PteRw2BQFyDJEI2ls5EvzWbYsI0P/qQxcBvQwob83o2AYWmJJ8BBuNOnkn2cWvZ+Np 2NewUWP5q5LUHp4Rmts1+urvwUCTlnJkCdjQLOM5rc47N6chCmYnX6zIDY4kmtIyBIHu giqXsAqqRaUxZjsHD4oJnS2ifoMxVWeg36wivviRTw6SopYOD3AdQM5QRF2wEs0lrCC4 UzpBAzu9pcojHtjCvICmevzs9tboXltEBhV4j2Gf5gVbAkUyA/YQHo3jeFKl7NtJ6PU2 2xpSSfn961SH3lEfm3IWQ/hnbPJx2u+1VoJl8sDZRU/5SUFBjjE4+SQXB1VCbtF67wiw nMpw==
X-Gm-Message-State: APjAAAV006+OT0rkQj6AuhYHmM5T23mcC1gX3PUkSRwDg5EvEounCpbt +AuaXRDMlCo+laDqnYyXucI=
X-Google-Smtp-Source: APXvYqyqqu0OYXeYHlNQ0S73jF60kqwpRykGt00VTfhpGaSpJhlmm9/GcV9b0ia/vhjjPNbYvfL0gA==
X-Received: by 2002:a37:54f:: with SMTP id 76mr23919594qkf.157.1582127029200;  Wed, 19 Feb 2020 07:43:49 -0800 (PST)
Received: from [10.215.0.119] (static-108-51-87-186.washdc.fios.verizon.net. [108.51.87.186]) by smtp.gmail.com with ESMTPSA id r3sm132293qtc.85.2020.02.19.07.43.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Feb 2020 07:43:48 -0800 (PST)
From: Alan Ford <alan.ford@gmail.com>
Message-Id: <C5C85022-CA56-4305-A666-934B773A0318@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_63E11F75-5B98-424C-960B-C44F843A9E58"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 19 Feb 2020 15:43:45 +0000
In-Reply-To: <LNXP123MB258793AE47D970277BAF3688EB110@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
Cc: Yoshifumi Nishida <nsd.ietf@gmail.com>, cpaasch@apple.com, multipathtcp@ietf.org, mptcp@lists.01.org
To: Philip Eardley <philip.eardley@bt.com>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <620489655.29573797.1580915365031@csir4pi.in> <DA9790A3-134D-4D44-9532-65EE359B0B69@gmail.com> <1411057985.31281938.1581012439446@csir4pi.in> <CAAK044QoFh_eXE+MwggOn5X0uUs3xuzTcw2kdJaKuUnEP745dA@mail.gmail.com> <F3D07C9D-12B2-45A7-B9D0-23E862DDF4BA@apple.com> <CAAK044SQb0utvjZToU=+OCg0hB-KX6vs1bFZGsJ=tJ5WvfETog@mail.gmail.com> <LNXP123MB258793AE47D970277BAF3688EB110@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/OCd0gyK6LKzejBwDuzekIgO4uYc>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2020 15:43:56 -0000

--Apple-Mail=_63E11F75-5B98-424C-960B-C44F843A9E58
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Phil, all,

I have requested the following changes from the RFC Editor, as agreed:

Change 1

Change the sentence reading:

   If B has data to send first, then the reliable delivery of the ACK + =
MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).=20

To:

   If B has data to send first, then the reliable delivery of the ACK + =
MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data =
Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for the =
MP_CAPABLE (which is the first octet of the data sequence space).


Change 2

Change the sentence reading:

   A Data Sequence Mapping does not need to be included in every MPTCP =
packet, as long as the subflow sequence space in that packet is covered =
by a mapping known at the receiver.

To:

   The mapping provided by a Data Sequence Mapping MUST apply to some or =
all of the subflow sequence space in the TCP segment which carries the =
option. It does not need to be included in every MPTCP packet, as long =
as the subflow sequence space in that packet is covered by a mapping =
known at the receiver.


I have been looking through the thread wondering what in particular =
requires clarification; most of the discussion seemed to have concluded =
on no additional clarifications needed, unless I misunderstood - so =
could you please point to what in particular you feel should be added?

Many thanks,
Alan

> On 18 Feb 2020, at 10:34, philip.eardley@bt.com wrote:
>=20
> Alan, please go ahead and make Change 2 to the document (as well as =
Change 1). Please could you &/or Christoph add a small note based on the =
discussion we=E2=80=99ve had, as it=E2=80=99s drawn out a couple of =
useful clarifications.
> =20
> Thanks to everyone for the discussion,
> Best wishes,
> Phil & Yoshi.
> =20
> From: multipathtcp <multipathtcp-bounces@ietf.org> On Behalf Of =
Yoshifumi Nishida
> Sent: 13 February 2020 09:34
> To: Christoph Paasch <cpaasch@apple.com>
> Cc: MultiPath TCP - IETF WG <multipathtcp@ietf.org>; mptcp Upstreaming =
<mptcp@lists.01.org>
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> =20
> Hi Christoph,
> =20
> Thanks for the clarification. It seems that there are several ways to =
deal with this situation.=20
> I think these are not ideal, but at the same time, it won't be fatal. =
I think more thorough solutions can be discussed in future versions.=20
> Given that there're several ways to address it, I guess the draft =
doesn't have to specify the behavior for this.=20
> --
> Yoshi
> =20
> On Tue, Feb 11, 2020 at 2:30 PM Christoph Paasch <cpaasch@apple.com =
<mailto:cpaasch@apple.com>> wrote:
> +MPTCP-upstreaming
>=20
>=20
> On Feb 11, 2020, at 1:05 AM, Yoshifumi Nishida <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>> wrote:
> =20
> Hi folks,
> I guess we might want to know the behavior of existing implementations =
such as linux.
> When an mptcp stack tries to send a data packet and find that there's =
no enough option space for data mapping, what it will do?
> =20
> iOS, multipath-tcp.org <http://multipath-tcp.org/> and Linux 5.6 =
implementation all favor the DSS-option over any other option (except =
TCP Timestamps). And TCP Timestamps and DSS comfortably fit in the TCP =
option-space.
> =20
> If SACK-blocks should be added, we only add SACK-blocks up to the =
remaining space. SACK is anyways opportunistic as once there are more =
than 3 blocks they don't fit either.
> =20
> =20
> Christoph
>=20
>=20
> Split the packet to create more option space?
> --
> Yoshi
> =20
> On Thu, Feb 6, 2020 at 10:10 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Alan,
> =20
> Thank you for your reply. I have two points to clarify. Please see =
them in line.
> =20
> From: "Alan Ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>jk=20
> Cc: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>, "multipathtcp" <multipathtcp@ietf.org =
<mailto:multipathtcp@ietf.org>>
> Sent: Thursday, February 6, 2020 2:49:29 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> Hi Anil,
> =20
> This would not be forbidden if the mapping was carried on a pure ACK =
with no data.
> As far as I understand, delivery of DSM through pure ACK is not in the =
scope of the current draft. If we intend to do this, we may need an =
approach similar to the one proposed for delivery of ADD_ADDR option in =
pure ACK with reliability feature.  So, packing DSM on pure ACK does not =
seem to be an option at this stage.
> =20
> I do see the point here: if a packet of 1000 bytes contains 500 bytes =
of one mapping and 500 bytes of another mapping, then only one DSM would =
appear on one packet, leaving the mapping for the second 500 bytes to be =
carried somewhere else - the only option being a pure ACK. But this kind =
of scenario would be extremely rare
> Yes, I do agree that the scenario you mentioned above would be =
extremely rare. In fact, I wonder whether such a situation (i.e., need =
to cover the bytes in a single packet with two different maps) would =
ever arise. Probably there might be some corner cases, which I don't get =
it rightly now.=20
> =20
> More importantly, the scenario that Yoshi and me are referring to is =
totally different: the one I had given as part of my comments in =
response to the proposed change 2. In this scenario, which you could see =
in the trailing mail, data segment-1 is transmitted without including =
its map, something which is permitted in the  mptcp framework (6824 =
bis). I make this inference from the below text in 6824 bis:
> =20
> "...even if a mapping does not exist from the subflow space to the =
data- level space, the data SHOULD still be ACKed at the subflow (if it =
is in-window). This data cannot, however, be acknowledged at the data =
level (Section 3.3.2) because its data sequence numbers are unknown. =
Implementations MAY hold onto such unmapped data for a short while in =
the expectation that a mapping will arrive shortly."
> =20
> One option the data sender has at this stage is to include the map for =
data in segment-1, in segment-3 (please see the two-subflow example I =
gave in response to the change 2 you had proposed). But the proposed =
change does not permit this. What would happen to  subflow-1 in this =
case ?
> =20
> With regards,
> =20
> Anil   =20
> and I would imagine any implementation would just split into two 500 =
byte segments each with the PSH flag set. I don=E2=80=99t think we need =
to spell this out in the spec however.
> =20
> Regards,
> Alan
> =20
> On 5 Feb 2020, at 15:09, V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Yoshi,
> =20
> Please see in line.
> =20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, =
"multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> Sent: Tuesday, February 4, 2020 1:08:45 PM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> =20
> Hi Anil,
> =20
> Thanks for pointing it out. I overlooked this one.
> This looks an interesting point.
> =20
> It seems to me that whether RST is happen or not depends on the size =
of receive window according to the text.
> If the receive window size is big enough to accommodate segment 1 and =
segment 3, the text "Implementations MAY hold onto such unmapped data =
for a short while in the expectation that a mapping will arrive =
shortly.. " can be applied to the segment 1. As a result, the segment 1 =
won't be discarded.=20
> =20
> Yes.  So, segment 1 may be kept in the data receiver's buffer in =
expectation that its mapping will arrive shortly. And in the example =
that we are referring to, the data sender will not be able to include =
the map for the data in segment 1 in segment 3 or any higher segment.
> =20
> Regards,
> =20
> Anil
> =20
> However, this might be contradict with the new texts Alan proposed? =
Or, am I missing something?
> =20
> Thanks,
> --
> Yoshi
>=20
>=20
>=20
> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi Yoshi,
> =20
> Thanks for this point. In fact, I had initially not thought of a =
scenario, where the map is being delivered through a retransmitted data =
packet while its first transmission did not include the map. Now I am =
just seeing the document (RFC 6824-bis) in this context.
> =20
> My understanding is that in scenarios like what I described in my =
previous mail, RST is likely to happen whether we explicitly state so or =
not. Please see the paragraph containing the below text in RFC 6824-bis. =
=20
> =20
> "If a mapping for that subflow-level sequence space does not arrive =
within a receive window of data, that subflow SHOULD be treated as =
broken, closed with a RST, and any unmapped data silently discarded."
> =20
> if we assume that the map is included while retransmitting the data =
(even though the first transmission did not contain the map for some =
reasons),  we could argue that RST could be avoided provided that the =
retransmission is triggered within a receive window of data. But the =
question here would be how and when will the retransmission take place. =
In this case, the subflow may not initiate the retransmission of data by =
its own (i..e., no retransmission due to three duplicate ACKs or RTO =
expiry at subflow level) as there is no segment loss at subflow level =
sequence space. So there could be a high possibility of RST happening =
even before the map delivery through retransmission.=20
> =20
> With regards,=20
> =20
> Anil
> =20
> From: "Yoshifumi Nishida" <nsd.ietf@gmail.com =
<mailto:nsd.ietf@gmail.com>>
> To: "V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
> Cc: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>, =
"multipathtcp" <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
> Sent: Saturday, February 1, 2020 3:39:51 AM
> Subject: Re: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> =20
> Hi Anil,
> =20
> I have a question about your proposed text.
> I am actually wondering if we really want to terminate connection =
here.=20
> =20
> The packets without proper mappings will be treated as invalid and =
will be discarded.=20
> If an implementation failed to attach proper mapping for some reasons =
(e.g. option space), it might be able to attach the proper one when it =
retransmits the packets. This also looks ok to me.
> =20
> I don't have strong preference for this. But, do we have a reason to =
terminate connection?
> =20
> Thanks,
> --
> Yoshi
> =20
> On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in =
<mailto:anil@csir4pi.in>> wrote:
> Hi,
> =20
> I have some points related to the  modifications (Change 2) being =
proposed on data sequence map. Please see them inline. Though I am =
putting forward the below points, if the consensus is in favour of the =
proposed change for reducing implementation complexity, I am also OK =
with that as well.=20
> =20
> From: "alan ford" <alan.ford@gmail.com <mailto:alan.ford@gmail.com>>
> To: multipathtcp@ietf..org <mailto:multipathtcp@ietf.org>
> Sent: Thursday, January 2, 2020 4:21:32 AM
> Subject: [multipathtcp] RFC6824bis edits based on implementation =
feedback
> =20
> Hi all,
> We=E2=80=99d love to get this to a state of completion as soon as =
possible, and to this end I am starting a new thread on this topic. In =
discussion with the chairs, it is possible to make the desired changes =
in AUTH48 as long as there is WG consensus. The discussion so far has =
been fairly limited in terms of participation.
> =20
> I would ask the chairs please if it was possible to specify a time =
bound for this discussion and a default conclusion.
> =20
> Regarding the changes, in summary, there are two areas where changes =
have been requested by the implementation community. As we are the IETF =
we obviously have strong focus on =E2=80=9Crunning code=E2=80=9D and so =
ease of implementing standards-compliant code is strongly desirable. =
However, we do not wish to reduce functionality agreed by the IETF =
community if it is considered a required feature by the community.
> =20
>=20
> Change 1
> =20
> Change the sentence reading:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).=20
>=20
> To:
>=20
>    If B has data to send first, then the reliable delivery of the ACK =
+ MP_CAPABLE is ensured by the receipt of this data with an MPTCP Data =
Sequence Signal (DSS) option (Section 3.3) containing a DATA_ACK for the =
MP_CAPABLE (which is the first octet of the data sequence space).
>=20
> What this means:
> =20
> The current text is concerned only with ensuring a path is MPTCP =
capable, and so only cares that DSS option occurs on a data packet. =
However, the MP_CAPABLE option is defined to occupy the first octet of =
data sequence space and thus, if analogous to TCP, must be acknowledged. =
>=46rom an implementation point of view it would make sense not to have =
this hanging around forever and instead define it is acknowledged at the =
connection level as soon as received. This change ensures the first data =
packet also DATA_ACKs this MP_CAPABLE octet.
> =20
>=20
> Change 2
> =20
> Change the sentence reading:
>=20
>    A Data Sequence Mapping does not need to be included in every MPTCP =
packet, as long as the subflow sequence space in that packet is covered =
by a mapping known at the receiver.
>=20
> To:
>=20
>    The mapping provided by a Data Sequence Mapping MUST apply to some =
or all of the subflow sequence space in the TCP segment which carries =
the option. It does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.
>=20
> What this means:
> =20
> The current text does not place any restrictions on where a mapping =
could appear. In theory a sender could define a thousand different =
mappings up front, send them all, and expect a receiver to store this =
and reassemble data according to these mappings as it arrives. Indeed, =
this was never explicitly disallowed since it =E2=80=9Cmight have been =
useful=E2=80=9D. The implementation community, however, has expressed =
concerns over the difficulty of implementing this open-endedly. How many =
mappings is it reasonable to store? Is there a DoS risk here? Instead, =
it has been requested that thee specification restricts the placement of =
the DSS option to being within the subflow sequence space to which it =
applies.
> =20
> Below are my comments on this. I had shared some of these points in a =
previous thread that you had initiated in the same context.=20
> =20
> Transmitting large number of non-contiguous data sequence maps could =
be a misbehaviour (map-flooding), though it is not clear whether this =
can go to the extent of causing a potential DoS to the data receiver. So =
some sort of restriction on this could be useful.  One approach could be =
to insist that the data sender should ensure that the map being =
transmitted is for in-window data, as per the receiver advertised =
window. A receiver should anyhow be willing to store the maps for =
in-window data to deal with packet loss. For example, when a window of =
data segments (say 1 to 64) is transmitted, each carrying its =
corresponding map, and segment-1 is lost, the maps for the remaining 63 =
need to be stored till the lost segment is retransmitted. Of course, in =
this case the maps will be stored at the receiver side along with their =
corresponding data. But the need to store multiple maps for in-window =
data would still be there.
> =20
> The problem with the proposed change (restriction) is that a data =
sender may find it difficult, in case a need arise to slightly delay the =
map delivery by few segments, i.e., sending some data first without map, =
and then send the corresponding map in a later segment, as shown below:
> =20
> subflow-1:      segment-1                   segment-3                  =
  segment-4                       segment-7
>                       bytes:1-100                 bytes:201-300        =
      bytes:301-400                 bytes:601-700
>                       no map                        map for 1-100      =
        map for 201-400             map for 601-700
> =20
> =20
> =20
> subflow-2:       segment-2                  segment-5                  =
   segment-6                       segment-8
>                        bytes: 101-200           bytes:401-500          =
     bytes: 501-600                bytes:701-800  =20
>                        map for 101-200       map for 401-600           =
 no map                            map for 701-800
> =20
> =20
> In the above case, segment-1 goes without map and its map is included =
later in segment-3, the next data segment in the same subflow. Further,  =
in the above scheduling pattern, the map in segment-3 cannot cover the  =
data in segment-1 and segment-3, as some  data in between (segment-2) is =
transmitted through another subflow.  With the proposed change, the map =
in segment-3 will become invalid and this will eventually break =
subflow-1, though this could be a corner case..
> =20
> The question at this stage is why would segment-1 be transmitted =
without its map. In the case of bidirectional data transfer, there could =
be a need to pack both timestamp and SACK  options in a data segment, =
i.e., piggybacking of  SACK with data. If we consider that timestamp =
takes 12 bytes and SACK, even with single block,  takes another 10 =
bytes, the remaining 18 bytes option space is not adequate to carry data =
sequence signal with map, especially when DSN is 64 bit long. So the =
delivery of either of the two (SACK or map) would be delayed.
> =20
> As far as I understand, RFC 2018 (TCP Selective Acknowledgement =
Options) implies that SACK should not be delayed. It states "If sent at =
all, SACK options SHOULD be included in all ACKs which do not ACK the =
highest sequence number in the data receiver's queue". It also says "If =
data receiver generates SACK options under any circumstance, it SHOULD =
generate them under all permitted circumstances".   So, as part of =
meeting the RFC 2018 requirements, if the combination of SACK and =
timestamp is given preference over DSS, data segments could be =
transmitted without their map.=20
> =20
> Another case of delaying map could arise if the data sender prefers to =
send ADD_ADDR option, instead of map, in a data segment. It is nice that =
ADD_ADDR option can be delivered reliably in a pure ACK, but I think =
this is not the case with DSS at present.
> =20
> If we adopt the proposed change, I think it might also be helpful to =
spell out how the receiver is supposed to behave, if it gets maps not =
meeting the MUST condition in the proposed change.  For example =
termination of the subflow with MP_TCPRST option (section 3.6 in RFC =
6824-bis) with appropriate reason code and T flag value to intimate the =
data sender the cause for subflow termination. =20
>         =20
> With regards,
> =20
> Anil
>=20
> Please can members of the WG express whether they are happy with these =
changes, or concerned.
> =20
> Best regards,
> Alan
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
> =20
>=20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
> =20
> =20
> =20
> =20
>=20
> =20
> =20
> =20
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
> =20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


--Apple-Mail=_63E11F75-5B98-424C-960B-C44F843A9E58
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; line-break: after-white-space;" class=3D"">Hi =
Phil, all,<div class=3D""><br class=3D""></div><div class=3D"">I have =
requested the following changes from the RFC Editor, as =
agreed:</div><div class=3D""><br class=3D""></div><div class=3D""><div =
class=3D""><b class=3D"">Change 1</b></div><div class=3D""><b =
class=3D""><br class=3D""></b></div><div class=3D"">Change the sentence =
reading:<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B =
has data to send first, then the reliable delivery of the ACK + =
MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).&nbsp;<br =
class=3D""></i><br class=3D"">To:<br class=3D""><br class=3D""><i =
class=3D"">&nbsp; &nbsp;If B has data to send first, then the reliable =
delivery of the ACK + MP_CAPABLE is ensured by the receipt of this data =
with an MPTCP Data Sequence Signal (DSS) option (Section 3.3) containing =
a DATA_ACK for the MP_CAPABLE (which is the first octet of the data =
sequence&nbsp;space).</i></div><div class=3D""><i class=3D""><br =
class=3D""></i></div><div class=3D""><i class=3D""><br =
class=3D""></i></div><div class=3D""><span class=3D""><b class=3D"">Change=
 2</b></span></div><div class=3D""><i class=3D""><br =
class=3D""></i></div><div class=3D""><i class=3D""><span class=3D"" =
style=3D"font-style: normal;">Change the sentence reading:</span><br =
class=3D"" style=3D"font-style: normal;"><br class=3D"" =
style=3D"font-style: normal;"><i class=3D"">&nbsp; &nbsp;A Data Sequence =
Mapping does not need to be included in every MPTCP packet, as long as =
the subflow sequence space in that packet is covered by a mapping known =
at the receiver.</i><br class=3D"" style=3D"font-style: normal;"><br =
class=3D"" style=3D"font-style: normal;"><span class=3D"" =
style=3D"font-style: normal;">To:</span><br class=3D"" =
style=3D"font-style: normal;"><br class=3D"" style=3D"font-style: =
normal;"><i class=3D"">&nbsp; &nbsp;The mapping provided by a Data =
Sequence Mapping MUST apply to some or all of the subflow sequence space =
in the TCP segment which carries the option. It does not need to be =
included in every MPTCP packet, as long as the subflow sequence space in =
that packet is covered by a mapping known at the =
receiver.</i></i></div><div class=3D""><i class=3D""><br =
class=3D""></i></div><div><br class=3D""></div><div>I have been looking =
through the thread wondering what in particular requires clarification; =
most of the discussion seemed to have concluded on no additional =
clarifications needed, unless I misunderstood - so could you please =
point to what in particular you feel should be added?</div><div><br =
class=3D""></div><div>Many thanks,</div><div>Alan</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 18 =
Feb 2020, at 10:34, <a href=3D"mailto:philip.eardley@bt.com" =
class=3D"">philip.eardley@bt.com</a> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">Alan, please go =
ahead and make Change 2 to the document (as well as Change 1). Please =
could you &amp;/or Christoph add a small note based on the discussion =
we=E2=80=99ve had, as it=E2=80=99s drawn out a couple of useful =
clarifications.<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" =
class=3D"">Thanks to everyone for the discussion,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">Best wishes,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">Phil &amp; =
Yoshi.<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D""><span lang=3D"EN-US" =
class=3D"">From:</span></b><span lang=3D"EN-US" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>multipathtcp &lt;<a =
href=3D"mailto:multipathtcp-bounces@ietf.org" =
class=3D"">multipathtcp-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Yoshifumi =
Nishida<br class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>13 February 2020 09:34<br =
class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Christoph Paasch &lt;<a =
href=3D"mailto:cpaasch@apple.com" class=3D"">cpaasch@apple.com</a>&gt;<br =
class=3D""><b class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>MultiPath TCP - IETF WG =
&lt;<a href=3D"mailto:multipathtcp@ietf.org" =
class=3D"">multipathtcp@ietf.org</a>&gt;; mptcp Upstreaming &lt;<a =
href=3D"mailto:mptcp@lists.01.org" =
class=3D"">mptcp@lists.01.org</a>&gt;<br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Hi Christoph,<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Thanks for the clarification. It seems =
that there are several ways to deal with this situation.&nbsp;<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">I think these are not ideal, but at the same time, it won't =
be fatal. I think more thorough solutions can be discussed in future =
versions.&nbsp;<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Given that there're several ways to =
address it, I guess the draft doesn't have to specify the behavior for =
this.&nbsp;<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">--<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">Yoshi<o:p =
class=3D""></o:p></div></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">On Tue, Feb 11, 2020 at 2:30 PM =
Christoph Paasch &lt;<a href=3D"mailto:cpaasch@apple.com" style=3D"color: =
purple; text-decoration: underline;" class=3D"">cpaasch@apple.com</a>&gt; =
wrote:<o:p class=3D""></o:p></div></div><blockquote style=3D"border-style:=
 none none none solid; border-left-width: 1pt; border-left-color: =
rgb(204, 204, 204); padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; =
margin-right: 0cm;" class=3D""><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">+MPTCP-upstreaming<o:p class=3D""></o:p></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></div><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt;" class=3D""><div class=3D""><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">On Feb 11, 2020, at 1:05 AM, Yoshifumi Nishida &lt;<a =
href=3D"mailto:nsd.ietf@gmail.com" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" class=3D"">nsd.ietf@gmail.com</a>&gt;=
 wrote:<o:p class=3D""></o:p></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Hi =
folks,<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">I guess we might want to know the =
behavior of existing implementations such as linux.<o:p =
class=3D""></o:p></div></div></div></div></blockquote><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">When an mptcp stack tries to send a data packet and find that =
there's no enough option space for data mapping, what it will do?<o:p =
class=3D""></o:p></div></div></div></div></blockquote><div class=3D""><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-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: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">iOS,<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://multipath-tcp.org/" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipath-tcp.org</a>&nbsp;and Linux 5.6 implementation all =
favor the DSS-option over any other option (except TCP Timestamps). And =
TCP Timestamps and DSS comfortably fit in the TCP option-space.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">If SACK-blocks should be added, we only =
add SACK-blocks up to the remaining space. SACK is anyways opportunistic =
as once there are more than 3 blocks they don't fit either.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-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: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Christoph<o:p class=3D""></o:p></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">Split the packet to create =
more option space?<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">--<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">Yoshi<o:p =
class=3D""></o:p></div></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">On Thu, Feb 6, 2020 at 10:10 AM V Anil =
Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" target=3D"_blank" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<o:p =
class=3D""></o:p></div></div><blockquote style=3D"border-style: none =
none none solid; border-left-width: 1pt; border-left-color: rgb(204, =
204, 204); padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; margin-right: =
0cm;" class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Hi Alan,<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Thank you for your reply. I have two =
points to clarify. Please see them in line.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div =
class=3D"MsoNormal" align=3D"center" style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; text-align: =
center;"><hr size=3D"2" width=3D"100%" align=3D"center" =
id=3D"gmail-m_-540654355673772201gmail-m_8773357439777081590zwchr" =
class=3D""></div><div class=3D""><blockquote style=3D"border-style: none =
none none solid; border-left-width: 1.5pt; border-left-color: rgb(16, =
16, 255); padding: 0cm 0cm 0cm 4pt; margin-left: 3.75pt; margin-top: =
5pt; margin-bottom: 5pt;" class=3D""><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D""><span style=3D"font-size: 12pt; font-family: =
Helvetica, sans-serif;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt; font-family: Helvetica, sans-serif;" =
class=3D"">"Alan Ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">alan.ford@gmail.com</a>&gt;<br class=3D""><b =
class=3D"">To:<span class=3D"Apple-converted-space">&nbsp;</span></b>"V =
Anil Kumar" &lt;<a href=3D"mailto:anil@csir4pi.in" target=3D"_blank" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">anil@csir4pi.in</a>&gt;jk&nbsp;<br class=3D""><b =
class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>"Yoshifumi Nishida" =
&lt;<a href=3D"mailto:nsd.ietf@gmail.com" target=3D"_blank" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">nsd.ietf@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b =
class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Thursday, February 6, =
2020 2:49:29 AM<br class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></blockquote></div><div =
class=3D""><blockquote style=3D"border-style: none none none solid; =
border-left-width: 1.5pt; border-left-color: rgb(16, 16, 255); padding: =
0cm 0cm 0cm 4pt; margin-left: 3.75pt; margin-top: 5pt; margin-bottom: =
5pt;" class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Helvetica, sans-serif;" =
class=3D"">Hi Anil,<o:p class=3D""></o:p></span></div><div class=3D""><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D"">This would not be =
forbidden if the mapping was carried on a pure ACK with no data.<o:p =
class=3D""></o:p></span></div></div></blockquote><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">As far as I understand, delivery of DSM =
through pure ACK is not in the scope of the current draft. If we intend =
to do this, we may need an approach similar to the one proposed for =
delivery of ADD_ADDR option in pure ACK with reliability feature.&nbsp; =
So, packing DSM on pure ACK does not seem to be an option at this =
stage.<o:p class=3D""></o:p></div></div><blockquote style=3D"border-style:=
 none none none solid; border-left-width: 1.5pt; border-left-color: =
rgb(16, 16, 255); padding: 0cm 0cm 0cm 4pt; margin-left: 3.75pt; =
margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D"">I do see the point here: =
if a packet of 1000 bytes contains 500 bytes of one mapping and 500 =
bytes of another mapping, then only one DSM would appear on one packet, =
leaving the mapping for the second 500 bytes to be carried somewhere =
else - the only option being a pure ACK. But this kind of scenario would =
be extremely rare<o:p =
class=3D""></o:p></span></div></div></blockquote><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Yes, I do agree that the scenario you =
mentioned above would be extremely rare. In fact, I wonder whether such =
a situation (i.e., need to cover the bytes in a single packet with two =
different maps) would ever arise. Probably there might be some corner =
cases, which I don't get it rightly now.&nbsp;<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">More importantly, the scenario that =
Yoshi and me are referring to is totally different: the one I had given =
as part of my comments in response to the proposed change 2. In this =
scenario, which you could see in the trailing mail, data segment-1 is =
transmitted without including its map, something which is permitted in =
the &nbsp;mptcp framework (6824 bis). I make this inference from the =
below text in 6824 bis:<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-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: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">"...even if a mapping does not exist from the subflow space =
to the data- level space, the data SHOULD still be ACKed at the subflow =
(if it is in-window). This data cannot, however, be acknowledged at the =
data level (Section 3.3.2) because its data sequence numbers are =
unknown. Implementations MAY hold onto such unmapped data for a short =
while in the expectation that a mapping will arrive shortly."<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">One option the data sender has at this =
stage is to include the map for data in segment-1, in segment-3 (please =
see the two-subflow example I gave in response to the change 2 you had =
proposed). But the proposed change does not permit this. What would =
happen to &nbsp;subflow-1 in this case ?<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">With regards,<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-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: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Anil &nbsp; &nbsp;<o:p =
class=3D""></o:p></div></div><blockquote style=3D"border-style: none =
none none solid; border-left-width: 1.5pt; border-left-color: rgb(16, =
16, 255); padding: 0cm 0cm 0cm 4pt; margin-left: 3.75pt; margin-top: =
5pt; margin-bottom: 5pt;" class=3D""><div class=3D""><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Helvetica, =
sans-serif;" class=3D"">and I would imagine any implementation would =
just split into two 500 byte segments each with the PSH flag set. I =
don=E2=80=99t think we need to spell this out in the spec however.<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Helvetica, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D"">Regards,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Helvetica, =
sans-serif;" class=3D"">Alan<o:p class=3D""></o:p></span></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Helvetica, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Helvetica, sans-serif;" class=3D"">On 5 Feb 2020, at =
15:09, V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Hi Yoshi,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Please see in =
line.<o:p class=3D""></o:p></span></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D"MsoNormal" align=3D"center" style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; text-align: =
center;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><hr size=3D"2" width=3D"100%" align=3D"center" =
id=3D"gmail-m_-540654355673772201gmail-m_8773357439777081590zwchr" =
class=3D""></span></div><div class=3D""><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D""><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">"Yoshifumi Nishida" &lt;<a href=3D"mailto:nsd.ietf@gmail.com" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To:<span=
 class=3D"Apple-converted-space">&nbsp;</span></b>"V Anil Kumar" &lt;<a =
href=3D"mailto:anil@csir4pi.in" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" class=3D"">anil@csir4pi.in</a>&gt;<br=
 class=3D""><b class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>"alan ford" &lt;<a =
href=3D"mailto:alan.ford@gmail.com" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b =
class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Tuesday, February 4, =
2020 1:08:45 PM<br class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Hi Anil,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Thanks for pointing it =
out. I overlooked this one.<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">This looks an =
interesting point.<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">It seems to me that whether RST is happen or not =
depends on the size of receive window according to the text.<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">If the receive window size is big enough to =
accommodate&nbsp;segment 1 and segment 3, the text "</span><span =
style=3D"font-size: 10pt; font-family: Arial, sans-serif;" =
class=3D"">Implementations MAY hold onto such unmapped data for a short =
while in&nbsp;the expectation that a mapping will arrive shortly.. =
"&nbsp;</span><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">can be applied to the segment 1. As a result, =
the segment 1 won't be discarded.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><em class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">Yes.&nbsp; So, segment 1 may be kept in the data receiver's =
buffer in expectation that its mapping will arrive shortly. And in the =
example that we are referring to, the data sender will not be able to =
include the map for the data in segment 1 in segment 3 or any higher =
segment.</span></em><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><em class=3D""><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D"">Regards,</span></em><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><em class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">Anil</span></em><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">However, this might be =
contradict with the new texts Alan proposed? Or, am I missing =
something?<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, 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: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">--<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Yoshi<o:p =
class=3D""></o:p></span></div></div><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></p><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">On Sun, Feb 2, 2020 at 8:42 =
AM V Anil Kumar &lt;<a href=3D"mailto:anil@csir4pi.in" target=3D"_blank" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">anil@csir4pi.in</a>&gt; wrote:<o:p =
class=3D""></o:p></span></div></div><blockquote style=3D"border-style: =
none none none solid; border-left-width: 1pt; border-left-color: =
rgb(204, 204, 204); padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; =
margin-right: 0cm;" class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">Hi Yoshi,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Thanks for this point. =
In fact, I had initially not thought of a scenario, where the map is =
being delivered through a retransmitted data packet while its first =
transmission did not include the map. Now I am just seeing the document =
(RFC 6824-bis) in this context.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">My understanding is =
that in scenarios like what I described in my previous mail, RST is =
likely to happen whether we explicitly state so or not. Please see the =
paragraph containing the below text in RFC 6824-bis. &nbsp;<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">"If a mapping for that =
subflow-level sequence space does not arrive within a receive window of =
data, that subflow SHOULD be treated as broken, closed with a RST, and =
any unmapped data silently discarded."<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">if we assume that the =
map is included while retransmitting the data (even though the first =
transmission did not contain the map for some reasons), &nbsp;we could =
argue that RST could be avoided provided that the retransmission is =
triggered within a receive window of data. But the question here would =
be how and when will the retransmission take place. In this case, the =
subflow may not initiate the retransmission of data by its own (i..e., =
no retransmission due to three duplicate ACKs or RTO expiry at subflow =
level) as there is no segment loss at subflow level sequence space. So =
there could be a high possibility of RST happening even before the map =
delivery through retransmission.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">With =
regards,&nbsp;<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">Anil<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></span></div></div><div class=3D"MsoNormal" =
align=3D"center" style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; text-align: center;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><hr =
size=3D"2" width=3D"100%" align=3D"center" =
id=3D"gmail-m_-540654355673772201gmail-m_8773357439777081590gmail-m_218086=
596951724501gmail-m_2982267033577902985zwchr" class=3D""></span></div><div=
 class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><b class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">"Yoshifumi Nishida" &lt;<a href=3D"mailto:nsd.ietf@gmail.com" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">nsd.ietf@gmail.com</a>&gt;<br class=3D""><b class=3D"">To:<span=
 class=3D"Apple-converted-space">&nbsp;</span></b>"V Anil Kumar" &lt;<a =
href=3D"mailto:anil@csir4pi.in" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" class=3D"">anil@csir4pi.in</a>&gt;<br=
 class=3D""><b class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>"alan ford" &lt;<a =
href=3D"mailto:alan.ford@gmail.com" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">alan.ford@gmail.com</a>&gt;, "multipathtcp" &lt;<a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a>&gt;<br class=3D""><b =
class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Saturday, February 1, =
2020 3:39:51 AM<br class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Hi Anil,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">I have a question =
about your proposed text.<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D"">I =
am actually wondering if we really want to terminate connection =
here.&nbsp;<o:p class=3D""></o:p></span></div></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">The packets without proper mappings will be =
treated as invalid and will be discarded.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">If an implementation failed to attach proper =
mapping for some reasons (e.g. option space), it might be able to attach =
the proper one when it retransmits the packets. This also looks ok to =
me.<o:p class=3D""></o:p></span></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">I don't have strong =
preference for this. But, do we have a reason to terminate =
connection?<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, 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: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">--<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Yoshi<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D"">On =
Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar &lt;<a =
href=3D"mailto:anil@csir4pi.in" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" class=3D"">anil@csir4pi.in</a>&gt; =
wrote:<o:p class=3D""></o:p></span></div></div><blockquote =
style=3D"border-style: none none none solid; border-left-width: 1pt; =
border-left-color: rgb(204, 204, 204); padding: 0cm 0cm 0cm 6pt; =
margin-left: 4.8pt; margin-right: 0cm;" class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Hi,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">I have some points related to the =
&nbsp;modifications (Change 2) being proposed on data sequence map. =
Please see them inline.&nbsp;<span style=3D"background-color: white;" =
class=3D"">Though I am putting forward the below points, if the =
consensus is in favour of the proposed change for reducing =
implementation complexity, I am also OK with that as =
well.&nbsp;</span><o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"MsoNormal" =
align=3D"center" style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; text-align: center;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><hr =
size=3D"2" width=3D"100%" align=3D"center" =
id=3D"gmail-m_-540654355673772201gmail-m_8773357439777081590gmail-m_218086=
596951724501gmail-m_2982267033577902985gmail-m_7687184382299596774zwchr" =
class=3D""></span></div><div class=3D""><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D""><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">"alan ford" &lt;<a href=3D"mailto:alan.ford@gmail.com" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">alan.ford@gmail.com</a>&gt;<br class=3D""><b =
class=3D"">To:<span class=3D"Apple-converted-space">&nbsp;</span></b><a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf..org</a><br class=3D""><b =
class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Thursday, January 2, =
2020 4:21:32 AM<br class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>[multipathtcp] =
RFC6824bis edits based on implementation feedback<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Hi all,<o:p =
class=3D""></o:p></span></div><div class=3D""><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">We=E2=80=99d love to get this to a state of =
completion as soon as possible, and to this end I am starting a new =
thread on this topic. In discussion with the chairs, it<span =
class=3D"Apple-converted-space">&nbsp;</span><i class=3D"">is<span =
class=3D"Apple-converted-space">&nbsp;</span></i>possible to make the =
desired changes in AUTH48 as long as there is WG consensus. The =
discussion so far has been fairly limited in terms of participation.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">I would ask the chairs =
please if it was possible to specify a time bound for this discussion =
and a default conclusion.<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">Regarding the changes, in summary, there are two =
areas where changes have been requested by the implementation community. =
As we are the IETF we obviously have strong focus on =E2=80=9Crunning =
code=E2=80=9D and so ease of implementing standards-compliant code is =
strongly desirable. However, we do not wish to reduce functionality =
agreed by the IETF community if it is considered a required feature by =
the community.<o:p class=3D""></o:p></span></div></div><p =
class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></p><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D""><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;" class=3D"">Change 1</span></b><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" class=3D""><o:p=
 class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><p =
class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Change the sentence =
reading:<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;If B =
has data to send first, then the reliable delivery of the ACK + =
MP_CAPABLE can be inferred by the receipt of this data with an MPTCP =
Data Sequence Signal (DSS) option (Section 3.3).&nbsp;<br =
class=3D""></i><br class=3D"">To:<br class=3D""><br class=3D""><i =
class=3D"">&nbsp; &nbsp;If B has data to send first, then the reliable =
delivery of the ACK + MP_CAPABLE is ensured by the receipt of this data =
with an MPTCP Data Sequence Signal (DSS) option (Section 3.3) containing =
a DATA_ACK for the MP_CAPABLE (which is the first octet of the data =
sequence&nbsp;space).</i><o:p class=3D""></o:p></span></p></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">What this means:<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">The current text is =
concerned only with ensuring a path is MPTCP capable, and so only cares =
that DSS option occurs on a data packet. However, the MP_CAPABLE option =
is defined to occupy the first octet of data sequence space and thus, if =
analogous to TCP, must be acknowledged. &gt;=46rom an implementation =
point of view it would make sense not to have this hanging around =
forever and instead define it is acknowledged at the connection level as =
soon as received. This change ensures the first data packet also =
DATA_ACKs this MP_CAPABLE octet.<o:p =
class=3D""></o:p></span></div></div><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></p><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><b class=3D""><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">Change 2</span></b><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Change the sentence =
reading:<br class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;A Data =
Sequence Mapping does not need to be included in every MPTCP packet, as =
long as the subflow sequence space in that packet is covered by a =
mapping known at the receiver.</i><br class=3D""><br class=3D"">To:<br =
class=3D""><br class=3D""><i class=3D"">&nbsp; &nbsp;The mapping =
provided by a Data Sequence Mapping MUST apply to some or all of the =
subflow sequence space in the TCP segment which carries the option. It =
does not need to be included in every MPTCP packet, as long as the =
subflow sequence space in that packet is covered by a mapping known at =
the receiver.<br class=3D""></i><br class=3D"">What this means:<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">The current text does =
not place any restrictions on where a mapping could appear. In theory a =
sender could define a thousand different mappings up front, send them =
all, and expect a receiver to store this and reassemble data according =
to these mappings as it arrives. Indeed, this was never explicitly =
disallowed since it =E2=80=9Cmight have been useful=E2=80=9D. The =
implementation community, however, has expressed concerns over the =
difficulty of implementing this open-endedly. How many mappings is it =
reasonable to store? Is there a DoS risk here? Instead, it has been =
requested that thee specification restricts the placement of the DSS =
option to being within the subflow sequence space to which it =
applies.<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Below are my comments =
on this. I had shared some of these points in a previous thread that you =
had initiated in the same context.&nbsp;<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Transmitting large =
number of non-contiguous data sequence maps could be a misbehaviour =
(map-flooding), though it is not clear whether this can go to the extent =
of causing a potential DoS to the data receiver. So some sort of =
restriction on this could be useful.&nbsp; One approach could be to =
insist that the data sender should ensure that the map being transmitted =
is for in-window data, as per the receiver advertised window. A receiver =
should anyhow be willing to store the maps for in-window data to deal =
with packet loss. For example, when a window of data segments (say 1 to =
64) is transmitted, each carrying its corresponding map, and segment-1 =
is lost, the maps for the remaining 63 need to be stored till the lost =
segment is retransmitted. Of course, in this case the maps will be =
stored at the receiver side along with their corresponding data. But the =
need to store multiple maps for in-window data would still be there.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif; background-color: white;" =
class=3D"">The problem with the proposed change (restriction) is that a =
data sender may find it difficult, in case a need arise to slightly =
delay the map delivery by few segments, i.e., sending some data first =
without map, and then send the corresponding map in a later segment, as =
shown below:</span><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; background-color: white;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: &quot;Segoe =
UI&quot;, sans-serif;" class=3D"">subflow-1:&nbsp; &nbsp; &nbsp; =
segment-1&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; segment-3&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; segment-4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; segment-7</span><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; background-color: white;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
&quot;Segoe UI&quot;, sans-serif;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;bytes:1-100 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; bytes:201-300 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;bytes:301-400 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; bytes:601-700</span><span style=3D"font-size: 10.5pt; =
font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;no map &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 1-100 =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 201-400 &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; map for 601-700</span><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; background-color: white;" =
class=3D""><span style=3D"font-size: 10.5pt; font-family: &quot;Segoe =
UI&quot;, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; background-color: white;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; background-color: white;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; background-color: white;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: &quot;Segoe =
UI&quot;, sans-serif;" class=3D"">subflow-2:&nbsp; &nbsp; &nbsp; =
&nbsp;segment-2&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; segment-5 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; segment-6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; segment-8</span><span style=3D"font-size: =
10.5pt; font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bytes: 101-200 &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; bytes:401-500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bytes: 501-600 &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;bytes:701-800&nbsp;&nbsp;&nbsp;</span><span style=3D"font-size: =
10.5pt; font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;map for 101-200 &nbsp; &nbsp; &nbsp; =
map for 401-600 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;no map &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;map for 701-800</span><span style=3D"font-size: =
10.5pt; font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
background-color: white;" class=3D""><span style=3D"font-size: 10.5pt; =
font-family: &quot;Segoe UI&quot;, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; background-color: white;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: &quot;Segoe UI&quot;, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">In the above case, segment-1 goes without map =
and its map is included later in segment-3, the next data segment in the =
same subflow. Further, &nbsp;in the above scheduling pattern, the map in =
segment-3 cannot cover the &nbsp;data in segment-1 and segment-3, as =
some &nbsp;data in between (segment-2) is transmitted through another =
subflow.&nbsp; With the proposed change, the map in segment-3 will =
become invalid and this will eventually break subflow-1, though this =
could be a corner case..<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">The question at this stage is why would =
segment-1 be transmitted without its map. In the case of bidirectional =
data transfer, there could be a need to pack both timestamp and SACK =
&nbsp;options in a data segment, i.e., piggybacking of &nbsp;SACK with =
data. If we consider that timestamp takes 12 bytes and SACK, even with =
single block, &nbsp;takes another 10 bytes, the remaining 18 bytes =
option space is not adequate to carry data sequence signal with map, =
especially when DSN is 64 bit long. So the delivery of either of the two =
(SACK or map) would be delayed.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">As far as I =
understand, RFC 2018 (TCP Selective Acknowledgement Options) implies =
that SACK should not be delayed. It states "If sent at all, SACK options =
SHOULD be included in all ACKs which do not ACK the highest sequence =
number in the data receiver's queue". It also says "If data receiver =
generates SACK options under any circumstance, it SHOULD generate them =
under all permitted circumstances". &nbsp; So, as part of meeting the =
RFC 2018 requirements, if the combination of SACK and timestamp is given =
preference over DSS, data segments could be transmitted without their =
map.&nbsp;<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Another case of =
delaying map could arise if the data sender prefers to send ADD_ADDR =
option, instead of map, in a data segment. It is nice that ADD_ADDR =
option can be delivered reliably in a pure ACK, but I think this is not =
the case with DSS at present.<o:p class=3D""></o:p></span></div></div><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">If we adopt the proposed change, I think it =
might also be helpful to spell out how the receiver is supposed to =
behave, if it gets maps not meeting the MUST condition in the proposed =
change.&nbsp; For example termination of the subflow with MP_TCPRST =
option (section 3.6 in RFC 6824-bis) with appropriate reason code and T =
flag value to intimate the data sender the cause for subflow =
termination.&nbsp;&nbsp;<o:p class=3D""></o:p></span></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<o:p class=3D""></o:p></span></div></div></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">With regards,<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;" =
class=3D"">Anil<o:p class=3D""></o:p></span></p><div class=3D""><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D"">Please can members of the WG =
express whether they are happy with these changes, or concerned.<o:p =
class=3D""></o:p></span></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D"">Best regards,<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D"">Alan<o:p class=3D""></o:p></span></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><o:p =
class=3D""></o:p></span></div></div></div></div></div></div></div></div></=
div></div></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;" class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><o:p =
class=3D""></o:p></span></div></blockquote></div></div></div></div></div><=
/div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></blockquote></div></div></div><=
/div></div></div></div></div></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Helvetica, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></p></div></div></blockquote></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Helvetica, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Helvetica, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></blockquote></div></div><p =
class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></p></div></blockquote></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" =
class=3D"">_______________________________________________<br =
class=3D"">multipathtcp mailing list<br class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">multipathtcp@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
target=3D"_blank" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><o:p =
class=3D""></o:p></div></div></blockquote></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div></blockquote></div></div></div><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">multipathtcp mailing =
list</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D""><a =
href=3D"mailto:multipathtcp@ietf.org" =
class=3D"">multipathtcp@ietf.org</a></span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a></span></=
div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_63E11F75-5B98-424C-960B-C44F843A9E58--


From nobody Wed Feb 26 00:25:14 2020
Return-Path: <Michael.Scharf@hs-esslingen.de>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4519C3A1080; Wed, 26 Feb 2020 00:25:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.787
X-Spam-Level: 
X-Spam-Status: No, score=-0.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_RP_RNBL=1.31, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hs-esslingen.de
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 uYeSOGmQhLke; Wed, 26 Feb 2020 00:25:10 -0800 (PST)
Received: from mail.hs-esslingen.de (mail.hs-esslingen.de [134.108.32.78]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B6FF3A107D; Wed, 26 Feb 2020 00:25:09 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id 3382525A16; Wed, 26 Feb 2020 09:25:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1582705508; bh=88gWBGxtPO/PwzJQtkYDnKodiD8rKd8SkPM7PST2gUo=; h=From:To:CC:Subject:Date:From; b=iFgBg7cwa6gQSrAW22aDLMMsInWPLSlin5PIXZ8WuPcEwGMUP7Sut6W8eVJwtt44s CzhTvY0u8REX8zP5yNIQe/EmGCqpoAuiirg9mY+hzQpY+rw3vM94mlFc1LMptt11eu Hc0HIk7xxB4XQ5OoBLfMno3J9rEcefuLu6rks58Q=
X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at hs-esslingen.de
Received: from mail.hs-esslingen.de ([127.0.0.1]) by localhost (hs-esslingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vpH6wIDOAagO; Wed, 26 Feb 2020 09:25:04 +0100 (CET)
Received: from rznt8102.rznt.rzdir.fht-esslingen.de (rznt8102.rznt.rzdir.fht-esslingen.de [134.108.29.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS; Wed, 26 Feb 2020 09:25:04 +0100 (CET)
Received: from RZNT8114.rznt.rzdir.fht-esslingen.de ([169.254.3.209]) by rznt8102.rznt.rzdir.fht-esslingen.de ([fe80::f977:d5e6:6b09:56ac%10]) with mapi id 14.03.0468.000; Wed, 26 Feb 2020 09:25:03 +0100
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: tcpm IETF list <tcpm@ietf.org>
CC: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "tcpm-chairs@ietf.org" <tcpm-chairs@ietf.org>
Thread-Topic: TCPM rechartering to add MPTCP maintenance
Thread-Index: AdXsfiYbdxTCvkRaSHGznmUWO5g9GQ==
Date: Wed, 26 Feb 2020 08:25:02 +0000
Message-ID: <6EC6417807D9754DA64F3087E2E2E03E2D99CD22@rznt8114.rznt.rzdir.fht-esslingen.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.108.48.164]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/nlWMRuh-mXdEtLQdmN-Uf-8pG-U>
Subject: [multipathtcp] TCPM rechartering to add MPTCP maintenance
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 08:25:13 -0000

Hi all,

As TCPM shall in future maintain MPTCP, we propose a small addition to the =
TCPM charter.

The chairs and the responsible ADs believe that MPTCP maintenance and minor=
 MPTCP enhancements would formally be possible with the current TCPM charte=
r text, as MPTCP is a TCP extension. Yet, our preference is to state explic=
itly that MPTCP maintenance is in scope of TCPM, in particular also to make=
 this transparent to people outside the IETF.

Therefore, we propose the following small addition to the current TCPM char=
ter (the addition is flagged by <new></new> and the current TCPM charter is=
 fully copied as reference):

<charter>
TCP is currently the Internet's predominant transport protocol. TCPM
is the working group within the IETF that handles small TCP changes,
i.e., minor extensions to TCP algorithms and protocol mechanisms.
The TCPM WG serves several purposes:=20

* The WG mostly focuses on maintenance issues (e.g., bug fixes) and
modest changes to the protocol, algorithms, and interfaces that
maintain TCP's utility.

* The WG is a venue for moving current TCP specifications along the
standards track (as community energy is available for such efforts).=20

<new>
* The WG maintains Multipath TCP (MPTCP) and is a home for minor
MPTCP enhancements including updates to the existing multipath
congestion control.
</new>

* The focus of the working group is TCP. In cases where small
changes are directly applicable to other transports (e.g., SCTP or
DCCP), the mappings to other transports may be specified alongside
that for TCP, but other significant additions and changes to other
transports are not in scope.

TCPM also provides a venue for standardization of incremental
enhancements of TCP's standard congestion control. In addition,
TCPM may document alternative TCP congestion control algorithms
that are known to be widely deployed, and that are considered
safe for large-scale deployment in the Internet. Changes of algorithms
may require additional review by the IRTF Congestion Control
Research Group (ICCRG). Fundamental changes to TCP or its congestion
control algorithms (e.g., departure from loss-based congestion
control) will be handled by other working groups or will require
rechartering.

TCP's congestion control algorithms are the model followed by
alternate transports (e.g., SCTP or DCCP), which are standardized in
other working groups, such as the Transport Area WG (tsvwg). In the
past, the IETF has worked on several documents about algorithms that
are specified for multiple protocols (e.g., TCP and SCTP) in the
same document. Which WG shepherds such documents will be determined
on a case-by-case basis. In any case, the TCPM WG will remain in
close contact with other relevant WGs working on these protocols to
ensure openness and stringent review from all angles.

New TCPM milestones that fall within the scope specified within the
charter can be added after consensus on acceptance in the working
group and approval by the responsible Area Director.
</charter>

We do not plan any other changes to the TCPM charter, i.e., any MPTCP-relat=
ed work would follow the process explained in the last sentence of the char=
ter.

Even if this is only one additional sentence, any re-chartering requires IE=
SG approval. The current plan is to get IESG approval for the new TCPM char=
ter prior to IETF 107. Obviously, the first step is to reach consensus insi=
de TCPM.

I add the MPTCP WG list in CC. Yet, any discussion of the TCPM charter shou=
ld take place at tcpm@ietf.org.

Please review the charter proposal, and please let us know any comments ASA=
P.

Best regards

Michael


From nobody Wed Feb 26 01:39:01 2020
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E0E3A1192; Wed, 26 Feb 2020 01:39:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 hVtG5pzqWWXT; Wed, 26 Feb 2020 01:38:58 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA9F3A1193; Wed, 26 Feb 2020 01:38:57 -0800 (PST)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 5D34C1B00193; Wed, 26 Feb 2020 09:38:51 +0000 (GMT)
To: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>, tcpm IETF list <tcpm@ietf.org>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "tcpm-chairs@ietf.org" <tcpm-chairs@ietf.org>
References: <6EC6417807D9754DA64F3087E2E2E03E2D99CD22@rznt8114.rznt.rzdir.fht-esslingen.de>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <540ca6c0-3a72-2ca1-e9fa-e914ad1ee259@erg.abdn.ac.uk>
Date: Wed, 26 Feb 2020 09:38:50 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <6EC6417807D9754DA64F3087E2E2E03E2D99CD22@rznt8114.rznt.rzdir.fht-esslingen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/ldHR6mRR83MlKcO5iKCSjT3fdbg>
Subject: Re: [multipathtcp] [tcpm] TCPM rechartering to add MPTCP maintenance
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 09:39:00 -0000

See below:

On 26/02/2020 08:25, Scharf, Michael wrote:
> Hi all,
>
> As TCPM shall in future maintain MPTCP, we propose a small addition to the TCPM charter.
>
> The chairs and the responsible ADs believe that MPTCP maintenance and minor MPTCP enhancements would formally be possible with the current TCPM charter text, as MPTCP is a TCP extension. Yet, our preference is to state explicitly that MPTCP maintenance is in scope of TCPM, in particular also to make this transparent to people outside the IETF.
>
> Therefore, we propose the following small addition to the current TCPM charter (the addition is flagged by <new></new> and the current TCPM charter is fully copied as reference):
>
> <charter>
> TCP is currently the Internet's predominant transport protocol. TCPM
> is the working group within the IETF that handles small TCP changes,
> i.e., minor extensions to TCP algorithms and protocol mechanisms.
> The TCPM WG serves several purposes:
>
> * The WG mostly focuses on maintenance issues (e.g., bug fixes) and
> modest changes to the protocol, algorithms, and interfaces that
> maintain TCP's utility.
>
> * The WG is a venue for moving current TCP specifications along the
> standards track (as community energy is available for such efforts).
>
> <new>
> * The WG maintains Multipath TCP (MPTCP) and is a home for minor
> MPTCP enhancements including updates to the existing multipath
> congestion control.
> </new>
I think this seems appropriate. (Deciding on new work will require the 
same judgement as other protocol work for non-TCP transports and so the 
new Charter text works for me.)
> * The focus of the working group is TCP. In cases where small
> changes are directly applicable to other transports (e.g., SCTP or
> DCCP), the mappings to other transports may be specified alongside
> that for TCP, but other significant additions and changes to other
> transports are not in scope.
>
> TCPM also provides a venue for standardization of incremental
> enhancements of TCP's standard congestion control. In addition,
> TCPM may document alternative TCP congestion control algorithms
> that are known to be widely deployed, and that are considered
> safe for large-scale deployment in the Internet. Changes of algorithms
> may require additional review by the IRTF Congestion Control
> Research Group (ICCRG). Fundamental changes to TCP or its congestion
> control algorithms (e.g., departure from loss-based congestion
> control) will be handled by other working groups or will require
> rechartering.
>
> TCP's congestion control algorithms are the model followed by
> alternate

[GF] can we change /alternate/ to /other IETF/ ... I always though that 
word was a slightly odd choice to me.

> transports (e.g., SCTP or DCCP), which are standardized in
> other working groups, such as the Transport Area WG (tsvwg). In the
> past, the IETF has worked on several documents about algorithms that
> are specified for multiple protocols (e.g., TCP and SCTP) in the
> same document. Which WG shepherds such documents will be determined
> on a case-by-case basis. In any case, the TCPM WG will remain in
> close contact with other relevant WGs working on these protocols to
> ensure openness and stringent review from all angles.
>
> New TCPM milestones that fall within the scope specified within the
> charter can be added after consensus on acceptance in the working
> group and approval by the responsible Area Director.
> </charter>
>
> We do not plan any other changes to the TCPM charter, i.e., any MPTCP-related work would follow the process explained in the last sentence of the charter.
>
> Even if this is only one additional sentence, any re-chartering requires IESG approval. The current plan is to get IESG approval for the new TCPM charter prior to IETF 107. Obviously, the first step is to reach consensus inside TCPM.
>
> I add the MPTCP WG list in CC. Yet, any discussion of the TCPM charter should take place at tcpm@ietf.org.
>
> Please review the charter proposal, and please let us know any comments ASAP.
>
> Best regards
>
> Michael
>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
Gorry

