
From albrecht.schwarz@alcatel-lucent.com  Thu Dec  1 08:21:01 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A66811E81A6; Thu,  1 Dec 2011 08:21:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.649
X-Spam-Level: 
X-Spam-Status: No, score=-5.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZwPwX1ajkX9; Thu,  1 Dec 2011 08:20:59 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 5689711E8121; Thu,  1 Dec 2011 08:20:59 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB1GKnuP032699 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 1 Dec 2011 17:20:51 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.52]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Thu, 1 Dec 2011 17:20:30 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Thu, 1 Dec 2011 17:20:28 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: AcyvyohSZB7NCXKAQDOWghJkAac7vwAdnG+g
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com>
In-Reply-To: <B527BAFA038842A8939A8C2D558074CD@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 16:21:01 -0000

My replies below ...
-Albrecht=20

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]=20
> Sent: Donnerstag, 1. Dezember 2011 02:42
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:=20
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>=20
> Hi,
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"=20
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Thursday, December 01, 2011 1:24 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:=20
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>=20
>=20
> My replies below inline,
> Albrecht=20
>=20
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]=20
> > Sent: Mittwoch, 30. November 2011 04:51
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:=20
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >=20
> > Hi,
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"=20
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Tuesday, November 29, 2011 7:32 PM
> > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D=20
> > Action: draft-ietf-avtcore-monarch-08.txt
> >=20
> >=20
> > > Dear All,
> > >=20
> > > there are different types of monitoring architectures,=20
> > particularily from perspective of QoE related performance=20
> parameters.=20
> > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > >=20
> > > Quality of Experience (QoE):=20
> > > The overall acceptability of an application or service, as=20
> > perceived subjectively by the end-user. =20
> > > NOTE 1 - Quality of experience includes the complete=20
> > end-to-end system effects (client, terminal, network,=20
> > services infrastructure, etc.).=20
> > > NOTE 2 - Overall acceptability may be influenced by user=20
> > expectations and context.=20
> > >=20
> > > Important for MONARCH:
> > > 1st ... perceived by end-user
> > > 2nd QoE includes the complete end-to-end sytem effects ...
> > >=20
> > > That said, present RTP monitoring architecture in MONARCH=20
> > according clause 3 is not specific on the type of monitoring=20
> > architecture. For instance, Fig. 1, it is possibly supposed=20
> > that the "RTP Sender" and "RTP Receiver" entities are equal=20
> > to a terminal/user equipment (UE). This would be an=20
> > end-to-end IP network scenario.
> > >=20
> > > However, the "RTP Sender" and "RTP Receiver" entities may=20
> > be also located at the edge of an IP network, e.g. in a=20
> > gateway for IP-to-non-IP interworking, i.e. an UE located in=20
> > the non-IP network part.=20
> > > Note: such scenarios are considered by MEGACO gateways=20
> > (I've Cc'd megaco list).
> > >=20
> > > An RTP Sender/Receiver located NOT in the UE would question=20
> > the value of RTP/RTCP QoE related performance measurements=20
> > (because the UE is located outside the RTP domain).=20
> > >=20
> > > Conclusions:
> > > - the set of meaningful performance metrics may be=20
> > dependent on the location of the RTP Sender/Receiver, e.g.=20
> > whether in a UE, gateway, ...
> > > - don't see any impact on transport level metrics
> > > - ... but the set of meaningful application level metrics
> > >=20
> > > Proposal for MONARCH:
> > > #1: insert sub-clause title "3.1 End-to-end IP network=20
> > architecture" below clause 3
> > >=20
> > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > >=20
> > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > The location of the RTP Sender/Receiver entity may impact=20
> > the set of meaningful metrics.
> > > For instance: application level metrics for QoE related=20
> > performance metrics are questionable (or doesn't really make=20
> > sense at all) when measured in a network node (terminating=20
> > the RTP) instead of the user equipment."
> > >=20
> > > Something like this would help to avoid confusion.
> > > I even believe that a QoE measurement in a network node=20
> > would violate the QoE definition. Would be rather something=20
> > like QoE* ("remote QoE"):-(
> > >=20
> > > Such information would improve the MONARCH doc in my opinion.
> > > Sorry for that late comment.
> > > Any views?
> >=20
> > [Qin]:=20
> > Albrrecht, if you follow ealry list discussion on=20
> > draft-hunt-avt-monarch-01, you will see the rough consensus=20
> > to position this document was=20
> > this daft should focus on guidelines for defining reporting=20
> > blocks. That is to say the main purpose of MONARCH draft is how to=20
> > provide guidelines for the development of new RTCP XR block=20
> > types in XRBlock working group.
>=20
> [ABS] ... then the title "monitoring architectures" is misleading.
> Proposal: keep title, revise scope section on focus
>=20
> [Qin]: No, the title is *RTP* monitoring architecture, we can=20
> not expand scope into IP monitoring architecture.

[ABS] That's wasn't the intent! Did just focus on the key word.

>=20
> >=20
> > Therefore how and where to collect the metric from RTP=20
> > endpoint is not scope of this document, in my opinion. since=20
> > you may have many ways to do this and different vendors have=20
> > their different appoaches. It will be better to leave this=20
> > beyond the scope. But you are right, it will be more=20
> > reasonable to measure QoE related performance metric at the=20
> > RTP receiver.
>=20
> [ABS] I would disagree. At least your statement should be=20
> conditional, sth like=20
> "QoE related performance metrics may be measured in a RTP=20
> receiver, IF the RTP receiver function is located in user=20
> equipment (e.g. IP terminal), because QoE performance metrics=20
> are tightly coupled to the point of view of a 'user'.
> ... IF NOT, then ..."
>=20
> [Qin]: I am not sure user equipment or IP terminal is the=20
> right term from RTP perspective.
>=20
> Also if you read P.NAMS, P.NAMS model for calculating QoE=20
> related metric can be placed either at the network or at the client.
> So I disagree with what you said.

[ABS] Not convinced at all.
Guess you are referring to the "mid-point" models, right?
The usage of such that models depends on "prior knowledge ..." information.
Thus, the applicability is conditional. You may not make such a general sta=
tement.


>=20
> Also as I said, how and where to collect the metric from RTP=20
>  endpoint is not scope of this document. It depends on the=20
> model you are choosing, e.g., four operation modes specified=20
> in P.NAMS.
> Apparently this should not be specified again in RTP=20
> monitoring architecture document.
>=20
> > =20
> > Another point is it is not clear to me how RTP monitoring has=20
> > to do with architectureend to end IP network architecture .
> > this draft mostly focus on discussing RTP level stuff.=20
> > Therefore I am quite doubt that we should describe anything=20
> > in this document like how
> > RTP entties is mapped into network entities/nodes at the IP layer.
>=20
> [ABS] I don't got any problems to talk about architectural=20
> framework for monitoring in this document. Such information=20
> is required and this is the only IETF AVT doc about it.
> The solution to this issue is rather simple to me:
> - split the MONARCH "monitoring architecture" in
> 1) a functional monitoring architecture (let's call it 'FMA') and
> 2) a physical monitoring architecture (... 'PMA').
>=20
> - the present MONARCH doc would describe the FMA at the level=20
> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP=20
> topology components according RFC 5117)
>=20
> - there are many options of functional-to-physical mappings,=20
> i.e. how a FMA would be mapped on a PMA
> - the mapping is typically dependent on considered network=20
> architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
>=20
> - the present MONARCH doc would describe the FMA-to-PMA=20
> mapping IF all RTP receiver/sender entities would be located=20
> in physical IP terminals (UEs)
> - etc
>=20
> [Qin]: I can understand your point, but you can not do that.=20
> Since this document is only focus on *RTP* monitoring=20
> architecture, that is what it said in AVTCore milestone:
> "
>=20
> Goals and Milestones:
>=20
>   Feb 2011 - Submit Monitoring Architecture for RTP for Informational
>=20
> "

[ABS] If you go back to my first email on this subject, and if you look at =
my proposal: that's not a lot, nothing which violates the charter, goals an=
d milestones.


> Also if you really don't see how to map FMA to PMA, you may=20
> look at the P.NAMS models specifed in ITU-T P.NAMS.=20
> As for how to use RTP monitoring architecture or RTP XR=20
> Report in the IMS network architecture, you may look at:
> http://tools.ietf.org/html/rfc6035

[ABS] That's the SIP reporting interface, i.e., applicable primarily for ph=
ysical IP user equipment with embedded RTP sender/receiver function and SIP=
 UA function.
However, the applicability of RFC 6035 is limited for a SIP-to-PSTN gateway=
 (because the RTP sender/receiver would be located NOT in user equipment. A=
lso the P.NAMS mid-point model fails for such a scenario.

> ITU-T H.248.48.
> But I haven't check the current status of H.248.48.

[ABS] Work is finalized, see http://www.itu.int/md/meetingdoc.asp?lang=3Den=
&parent=3DT09-SG16-111121-TD-PLEN-0419

>=20
> >=20
> > But as the author of this document, I am interested and open=20
> > to other opinions.:-)
>=20
> [ABS] Like to add a further aspect: a "functional monitoring=20
> architecture" may be considered as a network overlay,=20
> something which adds additional capabilities (here:=20
> measurement services, reporting services on top of basic RTP=20
> services).
> Such an overlay concept is nothing new: e.g., the=20
> MultiService Forum did define a "Performance Measurement &=20
> Monitoring (PMM)" overlay network, or IETF RMON may be also=20
> considered as such.
>=20
> >=20
> > > Regards,
> > > Albrecht
> > >=20
> > >=20
> > >=20
> > >=20
> > >> -----Original Message-----
> > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> > >> Behalf Of internet-drafts@ietf.org
> > >> Sent: Dienstag, 29. November 2011 08:56
> > >> To: i-d-announce@ietf.org
> > >> Cc: avt@ietf.org
> > >> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >>=20
> > >>=20
> > >> A New Internet-Draft is available from the on-line=20
> > >> Internet-Drafts directories. This draft is a work item of the=20
> > >> Audio/Video Transport Core Maintenance Working Group of the IETF.
> > >>=20
> > >> Title           : Monitoring Architectures for RTP
> > >> Author(s)       : Qin Wu
> > >>                           Geoff Hunt
> > >>                           Philip Arden
> > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > >> Pages           : 25
> > >> Date            : 2011-11-28
> > >>=20
> > >>    This memo proposes an architecture for extending RTCP with=20
> > >> a new RTCP
> > >>    XR (RFC3611) block type to report new metrics regarding media
> > >>    transmission or reception quality, following RTCP guideline
> > >>    established in RFC5968.  This memo suggests that a new=20
> > block should
> > >>    contain a single metric or a small number of metrics=20
> > relevant to a
> > >>    single parameter of interest or concern, rather than=20
> > containing a
> > >>    number of metrics which attempt to provide full coverage=20
> > >> of all those
> > >>    parameters of concern to a specific application. =20
> > Applications may
> > >>    then "mix and match" to create a set of blocks which=20
> > >> covers their set
> > >>    of concerns.  Where possible, a specific block should be=20
> > >> designed to
> > >>    be re-usable across more than one application, for=20
> > example, for all
> > >>    of voice, streaming audio and video.
> > >>=20
> > >>=20
> > >> A URL for this Internet-Draft is:
> > >>=20
> >=20
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > >>=20
> > >> Internet-Drafts are also available by anonymous FTP at:
> > >> ftp://ftp.ietf.org/internet-drafts/
> > >>=20
> > >> This Internet-Draft can be retrieved at:
> > >>=20
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > >>=20
> > >> _______________________________________________
> > >> Audio/Video Transport Core Maintenance
> > >> avt@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/avt
> > >>=20
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
> =

From bill.wu@huawei.com  Thu Dec  1 17:54:55 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A11201F0C5F; Thu,  1 Dec 2011 17:54:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.137
X-Spam-Level: 
X-Spam-Status: No, score=-6.137 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PrgrVu4hrOVP; Thu,  1 Dec 2011 17:54:54 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id D14471F0C5E; Thu,  1 Dec 2011 17:54:53 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVJ00ARRZZAG9@szxga04-in.huawei.com>; Fri, 02 Dec 2011 09:54:46 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVJ00I4TZZ98A@szxga04-in.huawei.com>; Fri, 02 Dec 2011 09:54:45 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFM49517; Fri, 02 Dec 2011 09:54:43 +0800
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 02 Dec 2011 09:54:38 +0800
Received: from w53375q (10.138.41.130) by szxeml420-hub.china.huawei.com (10.82.67.159) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 02 Dec 2011 09:54:34 +0800
Date: Fri, 02 Dec 2011 09:54:33 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 01:54:55 -0000

Hi, Albrecht:
No offence, I am not really convinced with your proposal on physical monitoring architecture.
 my counterquestion is what does physical monitoring architecture looks like in your mind?
How many components do we have in such physical monitroing architecture? what are they?
Take IMS network architecture as a example, they may have P-CSCF,S-CSCF, SIP PBX, SBC,
why do you believe monitor described in draft-ietf-avtcore-monarch is mapped into P-CSCF,
S-CSCF, SBC, Media Gateway, Media Gateway Controller should be in the scope of IETF RTP 
monitoring archtiecture draft?

Monitor described in  draft-ietf-avtcore-monarch is well defined in the section 3 of RFC3550 as follows:
"

   Monitor: An application that receives RTCP packets sent by
      participants in an RTP session, in particular the reception
      reports, and estimates the current quality of service for
      distribution monitoring, fault diagnosis and long-term statistics.
      The monitor function is likely to be built into the application(s)
      participating in the session, but may also be a separate
      application that does not otherwise participate and does not send
      or receive the RTP data packets (since they are on a separate
      port).  These are called third-party monitors.  It is also
      acceptable for a third-party monitor to receive the RTP data
      packets but not send RTCP packets or otherwise be counted in the
      session.

"
Isn't how to implent monitor into IMS netowork archtiecture a implentation specific issue?
If this issue are really interesting, isn't it a good idea to produce another new document to talk about this?
One good example for this motivation is this draft I like to share with you:
http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonomy-00#section-4.6

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Friday, December 02, 2011 12:20 AM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


My replies below ...
-Albrecht 

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com] 
> Sent: Donnerstag, 1. Dezember 2011 02:42
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE: 
> I-D Action: draft-ietf-avtcore-monarch-08.txt
> 
> Hi,
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)" 
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Thursday, December 01, 2011 1:24 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE: 
> I-D Action: draft-ietf-avtcore-monarch-08.txt
> 
> 
> My replies below inline,
> Albrecht 
> 
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com] 
> > Sent: Mittwoch, 30. November 2011 04:51
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE: 
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > 
> > Hi,
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)" 
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Tuesday, November 29, 2011 7:32 PM
> > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D 
> > Action: draft-ietf-avtcore-monarch-08.txt
> > 
> > 
> > > Dear All,
> > > 
> > > there are different types of monitoring architectures, 
> > particularily from perspective of QoE related performance 
> parameters. 
> > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > 
> > > Quality of Experience (QoE): 
> > > The overall acceptability of an application or service, as 
> > perceived subjectively by the end-user.  
> > > NOTE 1 - Quality of experience includes the complete 
> > end-to-end system effects (client, terminal, network, 
> > services infrastructure, etc.). 
> > > NOTE 2 - Overall acceptability may be influenced by user 
> > expectations and context. 
> > > 
> > > Important for MONARCH:
> > > 1st ... perceived by end-user
> > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > 
> > > That said, present RTP monitoring architecture in MONARCH 
> > according clause 3 is not specific on the type of monitoring 
> > architecture. For instance, Fig. 1, it is possibly supposed 
> > that the "RTP Sender" and "RTP Receiver" entities are equal 
> > to a terminal/user equipment (UE). This would be an 
> > end-to-end IP network scenario.
> > > 
> > > However, the "RTP Sender" and "RTP Receiver" entities may 
> > be also located at the edge of an IP network, e.g. in a 
> > gateway for IP-to-non-IP interworking, i.e. an UE located in 
> > the non-IP network part. 
> > > Note: such scenarios are considered by MEGACO gateways 
> > (I've Cc'd megaco list).
> > > 
> > > An RTP Sender/Receiver located NOT in the UE would question 
> > the value of RTP/RTCP QoE related performance measurements 
> > (because the UE is located outside the RTP domain). 
> > > 
> > > Conclusions:
> > > - the set of meaningful performance metrics may be 
> > dependent on the location of the RTP Sender/Receiver, e.g. 
> > whether in a UE, gateway, ...
> > > - don't see any impact on transport level metrics
> > > - ... but the set of meaningful application level metrics
> > > 
> > > Proposal for MONARCH:
> > > #1: insert sub-clause title "3.1 End-to-end IP network 
> > architecture" below clause 3
> > > 
> > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > 
> > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > The location of the RTP Sender/Receiver entity may impact 
> > the set of meaningful metrics.
> > > For instance: application level metrics for QoE related 
> > performance metrics are questionable (or doesn't really make 
> > sense at all) when measured in a network node (terminating 
> > the RTP) instead of the user equipment."
> > > 
> > > Something like this would help to avoid confusion.
> > > I even believe that a QoE measurement in a network node 
> > would violate the QoE definition. Would be rather something 
> > like QoE* ("remote QoE"):-(
> > > 
> > > Such information would improve the MONARCH doc in my opinion.
> > > Sorry for that late comment.
> > > Any views?
> > 
> > [Qin]: 
> > Albrrecht, if you follow ealry list discussion on 
> > draft-hunt-avt-monarch-01, you will see the rough consensus 
> > to position this document was 
> > this daft should focus on guidelines for defining reporting 
> > blocks. That is to say the main purpose of MONARCH draft is how to 
> > provide guidelines for the development of new RTCP XR block 
> > types in XRBlock working group.
> 
> [ABS] ... then the title "monitoring architectures" is misleading.
> Proposal: keep title, revise scope section on focus
> 
> [Qin]: No, the title is *RTP* monitoring architecture, we can 
> not expand scope into IP monitoring architecture.

[ABS] That's wasn't the intent! Did just focus on the key word.

> 
> > 
> > Therefore how and where to collect the metric from RTP 
> > endpoint is not scope of this document, in my opinion. since 
> > you may have many ways to do this and different vendors have 
> > their different appoaches. It will be better to leave this 
> > beyond the scope. But you are right, it will be more 
> > reasonable to measure QoE related performance metric at the 
> > RTP receiver.
> 
> [ABS] I would disagree. At least your statement should be 
> conditional, sth like 
> "QoE related performance metrics may be measured in a RTP 
> receiver, IF the RTP receiver function is located in user 
> equipment (e.g. IP terminal), because QoE performance metrics 
> are tightly coupled to the point of view of a 'user'.
> ... IF NOT, then ..."
> 
> [Qin]: I am not sure user equipment or IP terminal is the 
> right term from RTP perspective.
> 
> Also if you read P.NAMS, P.NAMS model for calculating QoE 
> related metric can be placed either at the network or at the client.
> So I disagree with what you said.

[ABS] Not convinced at all.
Guess you are referring to the "mid-point" models, right?
The usage of such that models depends on "prior knowledge ..." information.
Thus, the applicability is conditional. You may not make such a general statement.


> 
> Also as I said, how and where to collect the metric from RTP 
>  endpoint is not scope of this document. It depends on the 
> model you are choosing, e.g., four operation modes specified 
> in P.NAMS.
> Apparently this should not be specified again in RTP 
> monitoring architecture document.
> 
> >  
> > Another point is it is not clear to me how RTP monitoring has 
> > to do with architectureend to end IP network architecture .
> > this draft mostly focus on discussing RTP level stuff. 
> > Therefore I am quite doubt that we should describe anything 
> > in this document like how
> > RTP entties is mapped into network entities/nodes at the IP layer.
> 
> [ABS] I don't got any problems to talk about architectural 
> framework for monitoring in this document. Such information 
> is required and this is the only IETF AVT doc about it.
> The solution to this issue is rather simple to me:
> - split the MONARCH "monitoring architecture" in
> 1) a functional monitoring architecture (let's call it 'FMA') and
> 2) a physical monitoring architecture (... 'PMA').
> 
> - the present MONARCH doc would describe the FMA at the level 
> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP 
> topology components according RFC 5117)
> 
> - there are many options of functional-to-physical mappings, 
> i.e. how a FMA would be mapped on a PMA
> - the mapping is typically dependent on considered network 
> architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> 
> - the present MONARCH doc would describe the FMA-to-PMA 
> mapping IF all RTP receiver/sender entities would be located 
> in physical IP terminals (UEs)
> - etc
> 
> [Qin]: I can understand your point, but you can not do that. 
> Since this document is only focus on *RTP* monitoring 
> architecture, that is what it said in AVTCore milestone:
> "
> 
> Goals and Milestones:
> 
>   Feb 2011 - Submit Monitoring Architecture for RTP for Informational
> 
> "

[ABS] If you go back to my first email on this subject, and if you look at my proposal: that's not a lot, nothing which violates the charter, goals and milestones.


> Also if you really don't see how to map FMA to PMA, you may 
> look at the P.NAMS models specifed in ITU-T P.NAMS. 
> As for how to use RTP monitoring architecture or RTP XR 
> Report in the IMS network architecture, you may look at:
> http://tools.ietf.org/html/rfc6035

[ABS] That's the SIP reporting interface, i.e., applicable primarily for physical IP user equipment with embedded RTP sender/receiver function and SIP UA function.
However, the applicability of RFC 6035 is limited for a SIP-to-PSTN gateway (because the RTP sender/receiver would be located NOT in user equipment. Also the P.NAMS mid-point model fails for such a scenario.

> ITU-T H.248.48.
> But I haven't check the current status of H.248.48.

[ABS] Work is finalized, see http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-111121-TD-PLEN-0419

> 
> > 
> > But as the author of this document, I am interested and open 
> > to other opinions.:-)
> 
> [ABS] Like to add a further aspect: a "functional monitoring 
> architecture" may be considered as a network overlay, 
> something which adds additional capabilities (here: 
> measurement services, reporting services on top of basic RTP 
> services).
> Such an overlay concept is nothing new: e.g., the 
> MultiService Forum did define a "Performance Measurement & 
> Monitoring (PMM)" overlay network, or IETF RMON may be also 
> considered as such.
> 
> > 
> > > Regards,
> > > Albrecht
> > > 
> > > 
> > > 
> > > 
> > >> -----Original Message-----
> > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> > >> Behalf Of internet-drafts@ietf.org
> > >> Sent: Dienstag, 29. November 2011 08:56
> > >> To: i-d-announce@ietf.org
> > >> Cc: avt@ietf.org
> > >> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >> 
> > >> 
> > >> A New Internet-Draft is available from the on-line 
> > >> Internet-Drafts directories. This draft is a work item of the 
> > >> Audio/Video Transport Core Maintenance Working Group of the IETF.
> > >> 
> > >> Title           : Monitoring Architectures for RTP
> > >> Author(s)       : Qin Wu
> > >>                           Geoff Hunt
> > >>                           Philip Arden
> > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > >> Pages           : 25
> > >> Date            : 2011-11-28
> > >> 
> > >>    This memo proposes an architecture for extending RTCP with 
> > >> a new RTCP
> > >>    XR (RFC3611) block type to report new metrics regarding media
> > >>    transmission or reception quality, following RTCP guideline
> > >>    established in RFC5968.  This memo suggests that a new 
> > block should
> > >>    contain a single metric or a small number of metrics 
> > relevant to a
> > >>    single parameter of interest or concern, rather than 
> > containing a
> > >>    number of metrics which attempt to provide full coverage 
> > >> of all those
> > >>    parameters of concern to a specific application.  
> > Applications may
> > >>    then "mix and match" to create a set of blocks which 
> > >> covers their set
> > >>    of concerns.  Where possible, a specific block should be 
> > >> designed to
> > >>    be re-usable across more than one application, for 
> > example, for all
> > >>    of voice, streaming audio and video.
> > >> 
> > >> 
> > >> A URL for this Internet-Draft is:
> > >> 
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > >> 
> > >> Internet-Drafts are also available by anonymous FTP at:
> > >> ftp://ftp.ietf.org/internet-drafts/
> > >> 
> > >> This Internet-Draft can be retrieved at:
> > >> 
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > >> 
> > >> _______________________________________________
> > >> Audio/Video Transport Core Maintenance
> > >> avt@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/avt
> > >> 
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
> =

From albrecht.schwarz@alcatel-lucent.com  Mon Dec  5 06:49:26 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124A821F8B5A; Mon,  5 Dec 2011 06:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=-0.021,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QS7QNRGv0+tE; Mon,  5 Dec 2011 06:49:24 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id BCFCF21F8B1D; Mon,  5 Dec 2011 06:49:23 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB5ElIGZ022638 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 5 Dec 2011 15:49:03 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Mon, 5 Dec 2011 15:48:36 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Mon, 5 Dec 2011 15:48:35 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: AcywlWaLArPPa4UIQ9evRggexGLeFQCxJy3A
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com>
In-Reply-To: <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 14:49:26 -0000

Hello Qin,

to 1) Physical monitoring architecture
Of course consideration of generic physical entities (PE), not specific to =
any network reference architectures defined by SDOs (like your refered enti=
ties).
There would be just a few PE types ("given by the limited set of RTP topolo=
gy components (RFC 5117)").

to 2) (RFC 3550) Monitor function
Right, that's a functional entity. The applicability of a monitor may be li=
mited, dependent on ... (like in P.NAMS).

to 3) your IMS network example
Don't see the need to refer from MONARCH to a specific network architecture=
 like IMS.
Please also note that IMS is a functional architecture, not a physical arch=
itecture.

Regards,
Albrecht

PS
There are multiple options for adding the "RTP monitoring architecture" to =
a functional/physical network architecture:
a) integrated approach: extension of existing functional entities or/and ad=
dition of RTP monitoring architectural components, extension or/and additio=
n of signalling/management interfaces for control and configuration of RTP =
monitoring services, and reporting interfaces for measurement data ...
b) overlay approach: separate specification to ...


PSS
BTW: there's a discussion paper with regards to the location of a monitor f=
unction in an IMS H.248 gateway entity:
Measurements and statistics in IMS - Use Cases
http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_58_Kyoto_Japan=
/Docs/C3-100469.zip
This is just fyi.



> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf Of Qin Wu
> Sent: Freitag, 2. Dezember 2011 02:55
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Albrecht:
> No offence, I am not really convinced with your proposal on
> physical monitoring architecture.
>  my counterquestion is what does physical monitoring
> architecture looks like in your mind?
> How many components do we have in such physical monitroing
> architecture? what are they?
> Take IMS network architecture as a example, they may have
> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> described in draft-ietf-avtcore-monarch is mapped into
> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> should be in the scope of IETF RTP monitoring archtiecture draft?
>
> Monitor described in  draft-ietf-avtcore-monarch is well
> defined in the section 3 of RFC3550 as follows:
> "
>
>    Monitor: An application that receives RTCP packets sent by
>       participants in an RTP session, in particular the reception
>       reports, and estimates the current quality of service for
>       distribution monitoring, fault diagnosis and long-term
> statistics.
>       The monitor function is likely to be built into the
> application(s)
>       participating in the session, but may also be a separate
>       application that does not otherwise participate and
> does not send
>       or receive the RTP data packets (since they are on a separate
>       port).  These are called third-party monitors.  It is also
>       acceptable for a third-party monitor to receive the RTP data
>       packets but not send RTCP packets or otherwise be counted in the
>       session.
>
> "
> Isn't how to implent monitor into IMS netowork archtiecture a
> implentation specific issue?
> If this issue are really interesting, isn't it a good idea to
> produce another new document to talk about this?
> One good example for this motivation is this draft I like to
> share with you:
> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> y-00#section-4.6
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Friday, December 02, 2011 12:20 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> My replies below ...
> -Albrecht
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Donnerstag, 1. Dezember 2011 02:42
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi,
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Thursday, December 01, 2011 1:24 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > My replies below inline,
> > Albrecht
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Mittwoch, 30. November 2011 04:51
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi,
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > > Dear All,
> > > >
> > > > there are different types of monitoring architectures,
> > > particularily from perspective of QoE related performance
> > parameters.
> > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > >
> > > > Quality of Experience (QoE):
> > > > The overall acceptability of an application or service, as
> > > perceived subjectively by the end-user.
> > > > NOTE 1 - Quality of experience includes the complete
> > > end-to-end system effects (client, terminal, network,
> > > services infrastructure, etc.).
> > > > NOTE 2 - Overall acceptability may be influenced by user
> > > expectations and context.
> > > >
> > > > Important for MONARCH:
> > > > 1st ... perceived by end-user
> > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > >
> > > > That said, present RTP monitoring architecture in MONARCH
> > > according clause 3 is not specific on the type of monitoring
> > > architecture. For instance, Fig. 1, it is possibly supposed
> > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > to a terminal/user equipment (UE). This would be an
> > > end-to-end IP network scenario.
> > > >
> > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > be also located at the edge of an IP network, e.g. in a
> > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > the non-IP network part.
> > > > Note: such scenarios are considered by MEGACO gateways
> > > (I've Cc'd megaco list).
> > > >
> > > > An RTP Sender/Receiver located NOT in the UE would question
> > > the value of RTP/RTCP QoE related performance measurements
> > > (because the UE is located outside the RTP domain).
> > > >
> > > > Conclusions:
> > > > - the set of meaningful performance metrics may be
> > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > whether in a UE, gateway, ...
> > > > - don't see any impact on transport level metrics
> > > > - ... but the set of meaningful application level metrics
> > > >
> > > > Proposal for MONARCH:
> > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > architecture" below clause 3
> > > >
> > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > >
> > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > The location of the RTP Sender/Receiver entity may impact
> > > the set of meaningful metrics.
> > > > For instance: application level metrics for QoE related
> > > performance metrics are questionable (or doesn't really make
> > > sense at all) when measured in a network node (terminating
> > > the RTP) instead of the user equipment."
> > > >
> > > > Something like this would help to avoid confusion.
> > > > I even believe that a QoE measurement in a network node
> > > would violate the QoE definition. Would be rather something
> > > like QoE* ("remote QoE"):-(
> > > >
> > > > Such information would improve the MONARCH doc in my opinion.
> > > > Sorry for that late comment.
> > > > Any views?
> > >
> > > [Qin]:
> > > Albrrecht, if you follow ealry list discussion on
> > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > to position this document was
> > > this daft should focus on guidelines for defining reporting
> > > blocks. That is to say the main purpose of MONARCH draft
> is how to
> > > provide guidelines for the development of new RTCP XR block
> > > types in XRBlock working group.
> >
> > [ABS] ... then the title "monitoring architectures" is misleading.
> > Proposal: keep title, revise scope section on focus
> >
> > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > not expand scope into IP monitoring architecture.
>
> [ABS] That's wasn't the intent! Did just focus on the key word.
>
> >
> > >
> > > Therefore how and where to collect the metric from RTP
> > > endpoint is not scope of this document, in my opinion. since
> > > you may have many ways to do this and different vendors have
> > > their different appoaches. It will be better to leave this
> > > beyond the scope. But you are right, it will be more
> > > reasonable to measure QoE related performance metric at the
> > > RTP receiver.
> >
> > [ABS] I would disagree. At least your statement should be
> > conditional, sth like
> > "QoE related performance metrics may be measured in a RTP
> > receiver, IF the RTP receiver function is located in user
> > equipment (e.g. IP terminal), because QoE performance metrics
> > are tightly coupled to the point of view of a 'user'.
> > ... IF NOT, then ..."
> >
> > [Qin]: I am not sure user equipment or IP terminal is the
> > right term from RTP perspective.
> >
> > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > related metric can be placed either at the network or at the client.
> > So I disagree with what you said.
>
> [ABS] Not convinced at all.
> Guess you are referring to the "mid-point" models, right?
> The usage of such that models depends on "prior knowledge
> ..." information.
> Thus, the applicability is conditional. You may not make such
> a general statement.
>
>
> >
> > Also as I said, how and where to collect the metric from RTP
> >  endpoint is not scope of this document. It depends on the
> > model you are choosing, e.g., four operation modes specified
> > in P.NAMS.
> > Apparently this should not be specified again in RTP
> > monitoring architecture document.
> >
> > >
> > > Another point is it is not clear to me how RTP monitoring has
> > > to do with architectureend to end IP network architecture .
> > > this draft mostly focus on discussing RTP level stuff.
> > > Therefore I am quite doubt that we should describe anything
> > > in this document like how
> > > RTP entties is mapped into network entities/nodes at the IP layer.
> >
> > [ABS] I don't got any problems to talk about architectural
> > framework for monitoring in this document. Such information
> > is required and this is the only IETF AVT doc about it.
> > The solution to this issue is rather simple to me:
> > - split the MONARCH "monitoring architecture" in
> > 1) a functional monitoring architecture (let's call it 'FMA') and
> > 2) a physical monitoring architecture (... 'PMA').
> >
> > - the present MONARCH doc would describe the FMA at the level
> > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > topology components according RFC 5117)
> >
> > - there are many options of functional-to-physical mappings,
> > i.e. how a FMA would be mapped on a PMA
> > - the mapping is typically dependent on considered network
> > architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> >
> > - the present MONARCH doc would describe the FMA-to-PMA
> > mapping IF all RTP receiver/sender entities would be located
> > in physical IP terminals (UEs)
> > - etc
> >
> > [Qin]: I can understand your point, but you can not do that.
> > Since this document is only focus on *RTP* monitoring
> > architecture, that is what it said in AVTCore milestone:
> > "
> >
> > Goals and Milestones:
> >
> >   Feb 2011 - Submit Monitoring Architecture for RTP for
> Informational
> >
> > "
>
> [ABS] If you go back to my first email on this subject, and
> if you look at my proposal: that's not a lot, nothing which
> violates the charter, goals and milestones.
>
>
> > Also if you really don't see how to map FMA to PMA, you may
> > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > As for how to use RTP monitoring architecture or RTP XR
> > Report in the IMS network architecture, you may look at:
> > http://tools.ietf.org/html/rfc6035
>
> [ABS] That's the SIP reporting interface, i.e., applicable
> primarily for physical IP user equipment with embedded RTP
> sender/receiver function and SIP UA function.
> However, the applicability of RFC 6035 is limited for a
> SIP-to-PSTN gateway (because the RTP sender/receiver would be
> located NOT in user equipment. Also the P.NAMS mid-point
> model fails for such a scenario.
>
> > ITU-T H.248.48.
> > But I haven't check the current status of H.248.48.
>
> [ABS] Work is finalized, see
> http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> 11121-TD-PLEN-0419
>
> >
> > >
> > > But as the author of this document, I am interested and open
> > > to other opinions.:-)
> >
> > [ABS] Like to add a further aspect: a "functional monitoring
> > architecture" may be considered as a network overlay,
> > something which adds additional capabilities (here:
> > measurement services, reporting services on top of basic RTP
> > services).
> > Such an overlay concept is nothing new: e.g., the
> > MultiService Forum did define a "Performance Measurement &
> > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > considered as such.
> >
> > >
> > > > Regards,
> > > > Albrecht
> > > >
> > > >
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > >> Behalf Of internet-drafts@ietf.org
> > > >> Sent: Dienstag, 29. November 2011 08:56
> > > >> To: i-d-announce@ietf.org
> > > >> Cc: avt@ietf.org
> > > >> Subject: [AVTCORE] I-D Action:
> draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >>
> > > >> A New Internet-Draft is available from the on-line
> > > >> Internet-Drafts directories. This draft is a work item of the
> > > >> Audio/Video Transport Core Maintenance Working Group
> of the IETF.
> > > >>
> > > >> Title           : Monitoring Architectures for RTP
> > > >> Author(s)       : Qin Wu
> > > >>                           Geoff Hunt
> > > >>                           Philip Arden
> > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > >> Pages           : 25
> > > >> Date            : 2011-11-28
> > > >>
> > > >>    This memo proposes an architecture for extending RTCP with
> > > >> a new RTCP
> > > >>    XR (RFC3611) block type to report new metrics
> regarding media
> > > >>    transmission or reception quality, following RTCP guideline
> > > >>    established in RFC5968.  This memo suggests that a new
> > > block should
> > > >>    contain a single metric or a small number of metrics
> > > relevant to a
> > > >>    single parameter of interest or concern, rather than
> > > containing a
> > > >>    number of metrics which attempt to provide full coverage
> > > >> of all those
> > > >>    parameters of concern to a specific application.
> > > Applications may
> > > >>    then "mix and match" to create a set of blocks which
> > > >> covers their set
> > > >>    of concerns.  Where possible, a specific block should be
> > > >> designed to
> > > >>    be re-usable across more than one application, for
> > > example, for all
> > > >>    of voice, streaming audio and video.
> > > >>
> > > >>
> > > >> A URL for this Internet-Draft is:
> > > >>
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >> Internet-Drafts are also available by anonymous FTP at:
> > > >> ftp://ftp.ietf.org/internet-drafts/
> > > >>
> > > >> This Internet-Draft can be retrieved at:
> > > >>
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >> _______________________________________________
> > > >> Audio/Video Transport Core Maintenance
> > > >> avt@ietf.org
> > > >> https://www.ietf.org/mailman/listinfo/avt
> > > >>
> > > > _______________________________________________
> > > > Audio/Video Transport Core Maintenance
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > >
> > =3D
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From bill.wu@huawei.com  Mon Dec  5 22:17:45 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92B0321F87FC; Mon,  5 Dec 2011 22:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.14
X-Spam-Level: 
X-Spam-Status: No, score=-6.14 tagged_above=-999 required=5 tests=[AWL=-0.141,  BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GvHvdSBA+N8v; Mon,  5 Dec 2011 22:17:43 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 176DE21F87E2; Mon,  5 Dec 2011 22:17:43 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVR004KCQMZ7K@szxga03-in.huawei.com>; Tue, 06 Dec 2011 14:13:47 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVR005TTQMYM4@szxga03-in.huawei.com>; Tue, 06 Dec 2011 14:13:47 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFK93955; Tue, 06 Dec 2011 14:13:23 +0800
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 06 Dec 2011 14:13:20 +0800
Received: from w53375q (10.138.41.130) by SZXEML414-HUB.china.huawei.com (10.82.67.153) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 06 Dec 2011 14:13:18 +0800
Date: Tue, 06 Dec 2011 14:13:17 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 06:17:45 -0000

If you talk about existing RFC5117 RTP topology components, this has already been covered by the current version of draft-ietf-avtcore-monarch.
In most cases, an RTP system using RTCP XR is architecturally no different from an RTP system which does not use RTCP XR.

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Monday, December 05, 2011 10:48 PM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


Hello Qin,

to 1) Physical monitoring architecture
Of course consideration of generic physical entities (PE), not specific to any network reference architectures defined by SDOs (like your refered entities).
There would be just a few PE types ("given by the limited set of RTP topology components (RFC 5117)").

to 2) (RFC 3550) Monitor function
Right, that's a functional entity. The applicability of a monitor may be limited, dependent on ... (like in P.NAMS).

to 3) your IMS network example
Don't see the need to refer from MONARCH to a specific network architecture like IMS.
Please also note that IMS is a functional architecture, not a physical architecture.

Regards,
Albrecht

PS
There are multiple options for adding the "RTP monitoring architecture" to a functional/physical network architecture:
a) integrated approach: extension of existing functional entities or/and addition of RTP monitoring architectural components, extension or/and addition of signalling/management interfaces for control and configuration of RTP monitoring services, and reporting interfaces for measurement data ...
b) overlay approach: separate specification to ...


PSS
BTW: there's a discussion paper with regards to the location of a monitor function in an IMS H.248 gateway entity:
Measurements and statistics in IMS - Use Cases
http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_58_Kyoto_Japan/Docs/C3-100469.zip
This is just fyi.



> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf Of Qin Wu
> Sent: Freitag, 2. Dezember 2011 02:55
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Albrecht:
> No offence, I am not really convinced with your proposal on
> physical monitoring architecture.
>  my counterquestion is what does physical monitoring
> architecture looks like in your mind?
> How many components do we have in such physical monitroing
> architecture? what are they?
> Take IMS network architecture as a example, they may have
> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> described in draft-ietf-avtcore-monarch is mapped into
> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> should be in the scope of IETF RTP monitoring archtiecture draft?
>
> Monitor described in  draft-ietf-avtcore-monarch is well
> defined in the section 3 of RFC3550 as follows:
> "
>
>    Monitor: An application that receives RTCP packets sent by
>       participants in an RTP session, in particular the reception
>       reports, and estimates the current quality of service for
>       distribution monitoring, fault diagnosis and long-term
> statistics.
>       The monitor function is likely to be built into the
> application(s)
>       participating in the session, but may also be a separate
>       application that does not otherwise participate and
> does not send
>       or receive the RTP data packets (since they are on a separate
>       port).  These are called third-party monitors.  It is also
>       acceptable for a third-party monitor to receive the RTP data
>       packets but not send RTCP packets or otherwise be counted in the
>       session.
>
> "
> Isn't how to implent monitor into IMS netowork archtiecture a
> implentation specific issue?
> If this issue are really interesting, isn't it a good idea to
> produce another new document to talk about this?
> One good example for this motivation is this draft I like to
> share with you:
> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> y-00#section-4.6
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Friday, December 02, 2011 12:20 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> My replies below ...
> -Albrecht
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Donnerstag, 1. Dezember 2011 02:42
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi,
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Thursday, December 01, 2011 1:24 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > My replies below inline,
> > Albrecht
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Mittwoch, 30. November 2011 04:51
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi,
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > > Dear All,
> > > >
> > > > there are different types of monitoring architectures,
> > > particularily from perspective of QoE related performance
> > parameters.
> > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > >
> > > > Quality of Experience (QoE):
> > > > The overall acceptability of an application or service, as
> > > perceived subjectively by the end-user.
> > > > NOTE 1 - Quality of experience includes the complete
> > > end-to-end system effects (client, terminal, network,
> > > services infrastructure, etc.).
> > > > NOTE 2 - Overall acceptability may be influenced by user
> > > expectations and context.
> > > >
> > > > Important for MONARCH:
> > > > 1st ... perceived by end-user
> > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > >
> > > > That said, present RTP monitoring architecture in MONARCH
> > > according clause 3 is not specific on the type of monitoring
> > > architecture. For instance, Fig. 1, it is possibly supposed
> > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > to a terminal/user equipment (UE). This would be an
> > > end-to-end IP network scenario.
> > > >
> > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > be also located at the edge of an IP network, e.g. in a
> > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > the non-IP network part.
> > > > Note: such scenarios are considered by MEGACO gateways
> > > (I've Cc'd megaco list).
> > > >
> > > > An RTP Sender/Receiver located NOT in the UE would question
> > > the value of RTP/RTCP QoE related performance measurements
> > > (because the UE is located outside the RTP domain).
> > > >
> > > > Conclusions:
> > > > - the set of meaningful performance metrics may be
> > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > whether in a UE, gateway, ...
> > > > - don't see any impact on transport level metrics
> > > > - ... but the set of meaningful application level metrics
> > > >
> > > > Proposal for MONARCH:
> > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > architecture" below clause 3
> > > >
> > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > >
> > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > The location of the RTP Sender/Receiver entity may impact
> > > the set of meaningful metrics.
> > > > For instance: application level metrics for QoE related
> > > performance metrics are questionable (or doesn't really make
> > > sense at all) when measured in a network node (terminating
> > > the RTP) instead of the user equipment."
> > > >
> > > > Something like this would help to avoid confusion.
> > > > I even believe that a QoE measurement in a network node
> > > would violate the QoE definition. Would be rather something
> > > like QoE* ("remote QoE"):-(
> > > >
> > > > Such information would improve the MONARCH doc in my opinion.
> > > > Sorry for that late comment.
> > > > Any views?
> > >
> > > [Qin]:
> > > Albrrecht, if you follow ealry list discussion on
> > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > to position this document was
> > > this daft should focus on guidelines for defining reporting
> > > blocks. That is to say the main purpose of MONARCH draft
> is how to
> > > provide guidelines for the development of new RTCP XR block
> > > types in XRBlock working group.
> >
> > [ABS] ... then the title "monitoring architectures" is misleading.
> > Proposal: keep title, revise scope section on focus
> >
> > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > not expand scope into IP monitoring architecture.
>
> [ABS] That's wasn't the intent! Did just focus on the key word.
>
> >
> > >
> > > Therefore how and where to collect the metric from RTP
> > > endpoint is not scope of this document, in my opinion. since
> > > you may have many ways to do this and different vendors have
> > > their different appoaches. It will be better to leave this
> > > beyond the scope. But you are right, it will be more
> > > reasonable to measure QoE related performance metric at the
> > > RTP receiver.
> >
> > [ABS] I would disagree. At least your statement should be
> > conditional, sth like
> > "QoE related performance metrics may be measured in a RTP
> > receiver, IF the RTP receiver function is located in user
> > equipment (e.g. IP terminal), because QoE performance metrics
> > are tightly coupled to the point of view of a 'user'.
> > ... IF NOT, then ..."
> >
> > [Qin]: I am not sure user equipment or IP terminal is the
> > right term from RTP perspective.
> >
> > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > related metric can be placed either at the network or at the client.
> > So I disagree with what you said.
>
> [ABS] Not convinced at all.
> Guess you are referring to the "mid-point" models, right?
> The usage of such that models depends on "prior knowledge
> ..." information.
> Thus, the applicability is conditional. You may not make such
> a general statement.
>
>
> >
> > Also as I said, how and where to collect the metric from RTP
> >  endpoint is not scope of this document. It depends on the
> > model you are choosing, e.g., four operation modes specified
> > in P.NAMS.
> > Apparently this should not be specified again in RTP
> > monitoring architecture document.
> >
> > >
> > > Another point is it is not clear to me how RTP monitoring has
> > > to do with architectureend to end IP network architecture .
> > > this draft mostly focus on discussing RTP level stuff.
> > > Therefore I am quite doubt that we should describe anything
> > > in this document like how
> > > RTP entties is mapped into network entities/nodes at the IP layer.
> >
> > [ABS] I don't got any problems to talk about architectural
> > framework for monitoring in this document. Such information
> > is required and this is the only IETF AVT doc about it.
> > The solution to this issue is rather simple to me:
> > - split the MONARCH "monitoring architecture" in
> > 1) a functional monitoring architecture (let's call it 'FMA') and
> > 2) a physical monitoring architecture (... 'PMA').
> >
> > - the present MONARCH doc would describe the FMA at the level
> > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > topology components according RFC 5117)
> >
> > - there are many options of functional-to-physical mappings,
> > i.e. how a FMA would be mapped on a PMA
> > - the mapping is typically dependent on considered network
> > architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> >
> > - the present MONARCH doc would describe the FMA-to-PMA
> > mapping IF all RTP receiver/sender entities would be located
> > in physical IP terminals (UEs)
> > - etc
> >
> > [Qin]: I can understand your point, but you can not do that.
> > Since this document is only focus on *RTP* monitoring
> > architecture, that is what it said in AVTCore milestone:
> > "
> >
> > Goals and Milestones:
> >
> >   Feb 2011 - Submit Monitoring Architecture for RTP for
> Informational
> >
> > "
>
> [ABS] If you go back to my first email on this subject, and
> if you look at my proposal: that's not a lot, nothing which
> violates the charter, goals and milestones.
>
>
> > Also if you really don't see how to map FMA to PMA, you may
> > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > As for how to use RTP monitoring architecture or RTP XR
> > Report in the IMS network architecture, you may look at:
> > http://tools.ietf.org/html/rfc6035
>
> [ABS] That's the SIP reporting interface, i.e., applicable
> primarily for physical IP user equipment with embedded RTP
> sender/receiver function and SIP UA function.
> However, the applicability of RFC 6035 is limited for a
> SIP-to-PSTN gateway (because the RTP sender/receiver would be
> located NOT in user equipment. Also the P.NAMS mid-point
> model fails for such a scenario.
>
> > ITU-T H.248.48.
> > But I haven't check the current status of H.248.48.
>
> [ABS] Work is finalized, see
> http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> 11121-TD-PLEN-0419
>
> >
> > >
> > > But as the author of this document, I am interested and open
> > > to other opinions.:-)
> >
> > [ABS] Like to add a further aspect: a "functional monitoring
> > architecture" may be considered as a network overlay,
> > something which adds additional capabilities (here:
> > measurement services, reporting services on top of basic RTP
> > services).
> > Such an overlay concept is nothing new: e.g., the
> > MultiService Forum did define a "Performance Measurement &
> > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > considered as such.
> >
> > >
> > > > Regards,
> > > > Albrecht
> > > >
> > > >
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > >> Behalf Of internet-drafts@ietf.org
> > > >> Sent: Dienstag, 29. November 2011 08:56
> > > >> To: i-d-announce@ietf.org
> > > >> Cc: avt@ietf.org
> > > >> Subject: [AVTCORE] I-D Action:
> draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >>
> > > >> A New Internet-Draft is available from the on-line
> > > >> Internet-Drafts directories. This draft is a work item of the
> > > >> Audio/Video Transport Core Maintenance Working Group
> of the IETF.
> > > >>
> > > >> Title           : Monitoring Architectures for RTP
> > > >> Author(s)       : Qin Wu
> > > >>                           Geoff Hunt
> > > >>                           Philip Arden
> > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > >> Pages           : 25
> > > >> Date            : 2011-11-28
> > > >>
> > > >>    This memo proposes an architecture for extending RTCP with
> > > >> a new RTCP
> > > >>    XR (RFC3611) block type to report new metrics
> regarding media
> > > >>    transmission or reception quality, following RTCP guideline
> > > >>    established in RFC5968.  This memo suggests that a new
> > > block should
> > > >>    contain a single metric or a small number of metrics
> > > relevant to a
> > > >>    single parameter of interest or concern, rather than
> > > containing a
> > > >>    number of metrics which attempt to provide full coverage
> > > >> of all those
> > > >>    parameters of concern to a specific application.
> > > Applications may
> > > >>    then "mix and match" to create a set of blocks which
> > > >> covers their set
> > > >>    of concerns.  Where possible, a specific block should be
> > > >> designed to
> > > >>    be re-usable across more than one application, for
> > > example, for all
> > > >>    of voice, streaming audio and video.
> > > >>
> > > >>
> > > >> A URL for this Internet-Draft is:
> > > >>
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >> Internet-Drafts are also available by anonymous FTP at:
> > > >> ftp://ftp.ietf.org/internet-drafts/
> > > >>
> > > >> This Internet-Draft can be retrieved at:
> > > >>
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >> _______________________________________________
> > > >> Audio/Video Transport Core Maintenance
> > > >> avt@ietf.org
> > > >> https://www.ietf.org/mailman/listinfo/avt
> > > >>
> > > > _______________________________________________
> > > > Audio/Video Transport Core Maintenance
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > >
> > =
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From ramesh3184@gmail.com  Tue Dec  6 05:14:29 2011
Return-Path: <ramesh3184@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 886C621F8ACE for <avt@ietfa.amsl.com>; Tue,  6 Dec 2011 05:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6HhNT6rProDP for <avt@ietfa.amsl.com>; Tue,  6 Dec 2011 05:14:29 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 13A9421F8478 for <avt@ietf.org>; Tue,  6 Dec 2011 05:14:29 -0800 (PST)
Received: by iaek3 with SMTP id k3so8695093iae.31 for <avt@ietf.org>; Tue, 06 Dec 2011 05:14:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=I7QdXbEPmLCy4qwHecMqL9erw5hLmGQMtOuazhlRk+g=; b=BIharGqLVC0detNSffINmaDh5SXvW3cF80MRgMndqS6JCDv0m+AbqCpAy/lnMvlB0l /QbBtBqNHb3mJ9130thkd/zdyJLTJ1Z94hn4Zy7Mpl0G7s6psJRkH/4Cr9bUr63RP7c9 Ci1H5G+FO908WRnG172XdQWN1iXjrktUQXp3U=
MIME-Version: 1.0
Received: by 10.43.132.201 with SMTP id hv9mr13957637icc.42.1323177268774; Tue, 06 Dec 2011 05:14:28 -0800 (PST)
Received: by 10.50.100.233 with HTTP; Tue, 6 Dec 2011 05:14:28 -0800 (PST)
Date: Tue, 6 Dec 2011 18:44:28 +0530
Message-ID: <CAFLon=K4m=+zLmANeEOwDj4vAgvJZ6o_qOEbPbR=+xfzUHdC-A@mail.gmail.com>
From: ramesh kumar <ramesh3184@gmail.com>
To: avt@ietf.org
Content-Type: multipart/alternative; boundary=20cf307d046a14882f04b36c37b2
Subject: [AVTCORE] Please help me on solving following Issues related to RTP based IMS VOIP Session.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 13:17:48 -0000

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

Hi,

I am facing following Issues in RTP based IMS VOIP Session:

a) Previous VT/VOIP Call Media Session RTP packets flowing into current
VT/VOIP Call Media Session due to Network Congestion/Delay.

b) Media Packets received have unknown SSRC than the other Media packets
due to eavesdropper in the network.

How to ignore Unknown SSRC Packets/Previous Call Media Packets from playing?

-- 
*Thanks & Regards,
R.Ramesh Kumar
*

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

<div>Hi,</div>
<div>=A0</div>
<div>I am facing following Issues in RTP based IMS VOIP Session:</div>
<div>=A0</div>
<div>a) Previous VT/VOIP Call Media Session RTP packets flowing into curren=
t VT/VOIP Call Media Session due to Network Congestion/Delay.</div>
<div><br>b) Media Packets received have unknown SSRC than the other Media p=
ackets due to eavesdropper in the network.</div>
<div><br>How to ignore Unknown SSRC Packets/Previous Call Media Packets fro=
m playing?</div>
<div><br>-- <br><font style=3D"BACKGROUND-COLOR: #ffffff" color=3D"#000000"=
><em>Thanks &amp; Regards,<br>R.Ramesh Kumar<br></em></font><br></div>

--20cf307d046a14882f04b36c37b2--

From stewe@stewe.org  Wed Dec  7 08:09:11 2011
Return-Path: <stewe@stewe.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A68F021F8B24; Wed,  7 Dec 2011 08:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j27XmSQaNnJY; Wed,  7 Dec 2011 08:09:11 -0800 (PST)
Received: from stewe.org (stewe.org [85.214.122.234]) by ietfa.amsl.com (Postfix) with ESMTP id 458C121F858C; Wed,  7 Dec 2011 08:09:09 -0800 (PST)
Received: from [192.168.1.58] (unverified [71.202.147.60])  by stewe.org (SurgeMail 3.9e) with ESMTP id 4446-1743317  for multiple; Wed, 07 Dec 2011 17:09:07 +0100
User-Agent: Microsoft-MacOutlook/14.13.0.110805
Date: Wed, 07 Dec 2011 08:08:40 -0800
From: Stephan Wenger <stewe@stewe.org>
To: <mmusic@ietf.org>
Message-ID: <CB04CF88.350EA%stewe@stewe.org>
Thread-Topic: Incoming liaison statement from MMUSIC
Mime-version: 1.0
Content-type: multipart/mixed; boundary="B_3406090145_2752175"
X-Originating-IP: 71.202.147.60
X-Authenticated-User: stewe@stewe.org 
X-ORBS-Stamp: Your IP (71.202.147.60) was found in the spamhaus database. http://www.spamhaus.net
Cc: avtext@ietf.org, avt@ietf.org, payload@ietf.org, xrblock@ietf.org
Subject: [AVTCORE] Incoming liaison statement from MMUSIC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 16:09:11 -0000

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

--B_3406090145_2752175
Content-type: multipart/alternative;
	boundary="B_3406090145_2760267"


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

Hi all,
mmusic has received an incoming liaison from MPEG, indicating that they have
started on "codec independent media description code points".  My
understanding of this work is that these code points may be represented in
SDP.
My personal viewpoint is that this may well be sound architectural work, but
it may be better conducted here in mmusic, at least when it comes to SDP
representations and the related IANA work.  However, I know nothing about
this work beyond what's written in the statement, which is why I used "soft"
language.  Perhaps some of you can shed light into what's really going on.
The assorted avt WGs are probably also affected, as some of the proposed
code points sound like they are being described in payload formats, RTP
extensions and perhaps even in xrblock.  Let me suggest to use only the
music list for discussions, as only mmusic is being addressed in the
statement.
As it is short, I have attached the statement in word format to this email.
It will also appear shortly in the IETF liaison database.
Regards,
Stephan



--B_3406090145_2760267
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>Hi all,</div><div>mmusic has=
 received an incoming liaison from MPEG, indicating that they have started o=
n "codec independent media description code points". &nbsp;My understanding =
of this work is that these code points may be represented in SDP.</div><div>=
My personal viewpoint is that this may well be sound architectural work, but=
 it may be better conducted here in mmusic, at least when it comes to SDP re=
presentations and the related IANA work. &nbsp;However,&nbsp;I know nothing =
about this work beyond what's written in the statement, which is why I used =
"soft" language. &nbsp;Perhaps some of you can shed light into what's really=
 going on.</div><div>The assorted avt WGs are probably also affected, as som=
e of the proposed code points sound like they are being described in payload=
 formats, RTP extensions and perhaps even in xrblock. &nbsp;Let me suggest t=
o use only the music list for discussions, as only mmusic is being addressed=
 in the statement.</div><div>As it is short, I have attached the statement i=
n word format to this email. &nbsp;It will also appear shortly in the IETF l=
iaison database.</div><div>Regards,</div><div>Stephan</div></body></html>

--B_3406090145_2760267--


--B_3406090145_2752175
Content-type: application/msword; name="29n124561.doc"
Content-disposition: attachment;
	filename="29n124561.doc"
Content-transfer-encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAOAAAAAAA
AAAAEAAAOgAAAAEAAAD+////AAAAADcAAAD/////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
///////////////////////////////////spcEAJ2AJBAAA8FK/AAAAAAAAEAAAAAAABgAA
7Q4AAA4AYmpiakxVTFUAAAAAAAAAAAAAAAAAAAAAAAARBBYAOB4AAC4/AQAuPwEA3wYAAAAA
AAANAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAD//w8A
AAAAAAAAAAAAAAAAAAAAAKQAAAAAAEAFAAAAAAAAQAUAAEAFAAAAAAAAQAUAAAAAAABABQAA
AAAAAEAFAAAAAAAAQAUAABQAAAAAAAAAAAAAAFQFAAAAAAAAOAsAAAAAAAA4CwAAAAAAADgL
AAA4AAAAcAsAABQAAACECwAAJAAAAFQFAAAAAAAAkhgAAAICAAC0CwAAAAAAALQLAAAAAAAA
tAsAAAAAAAC0CwAAAAAAALQLAAAAAAAACA0AAAAAAAAIDQAAAAAAAAgNAAAAAAAAERgAAAIA
AAATGAAAAAAAABMYAAAAAAAAExgAAAAAAAATGAAAAAAAABMYAAAAAAAAExgAACQAAACUGgAA
aAIAAPwcAACsAAAANxgAABUAAAAAAAAAAAAAAAAAAAAAAAAAQAUAAAAAAABxDwAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAIDQAAAAAAAAgNAAAAAAAAcQ8AAAAAAABxDwAAAAAAADcYAAAAAAAA
AAAAAAAAAABABQAAAAAAAEAFAAAAAAAAtAsAAAAAAAAAAAAAAAAAALQLAABUAQAATBgAABYA
AAAZEQAAAAAAABkRAAAAAAAAGREAAAAAAABxDwAAjgAAAEAFAAAAAAAAtAsAAAAAAABABQAA
AAAAALQLAAAAAAAAERgAAAAAAAAAAAAAAAAAABkRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcQ8AAAAAAAARGAAAAAAAAAAAAAAAAAAA
GREAAAAAAAAZEQAAOgAAAC0WAAAsAAAAQAUAAAAAAABABQAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkRYAAAAAAAC0CwAA
AAAAAKgLAAAMAAAAwMI0ZN+zzAEAAAAAAAAAADgLAAAAAAAA/w8AAFIAAABZFgAACgAAAAAA
AAAAAAAApRcAAGwAAABiGAAAMAAAAJIYAAAAAAAAYxYAAC4AAACoHQAAAAAAAFEQAAB2AAAA
qB0AABQAAACRFgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKgdAAAAAAAAAAAAAAAAAABABQAA
AAAAAJEWAAAUAQAACA0AAGgAAABwDQAASgAAABkRAAAAAAAAug0AADwAAAD2DQAAewEAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACA0AAAAAAAAIDQAAAAAAAAgNAAAAAAAA
NxgAAAAAAAA3GAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAxxAAAFIA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgNAAAAAAAACA0AAAAAAAAIDQAA
AAAAAJIYAAAAAAAAcQ8AAAAAAABxDwAAAAAAAHEPAAAAAAAAcQ8AAAAAAAAAAAAAAAAAAFQF
AAAAAAAAVAUAAAAAAABUBQAA5AUAADgLAAAAAAAAVAUAAAAAAABUBQAAAAAAAFQFAAAAAAAA
OAsAAAAAAABUBQAAAAAAAFQFAAAAAAAAVAUAAAAAAABABQAAAAAAAEAFAAAAAAAAQAUAAAAA
AABABQAAAAAAAEAFAAAAAAAAQAUAAAAAAAD/////AAAAAAIADAEAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAElOVEVSTkFUSU9OQUwgT1JHQU5JU0FUSU9OIEZPUiBT
VEFOREFSRElTQVRJT04NT1JHQU5JU0FUSU9OIElOVEVSTkFUSU9OQUxFIERFIE5PUk1BTElT
QVRJT04NSVNPL0lFQyBKVEMxL1NDMjkvV0cxMQ1DT0RJTkcgT0YgTU9WSU5HIFBJQ1RVUkVT
IEFORCBBVURJTw0NSVNPL0lFQyBKVEMxL1NDMjkvV0cxMSBOMTI0NDgNRGVjZW1iZXIgMjAx
MSwgR2VuZXZhLCBTd2l0emVybGFuZA0NDVNvdXJjZQdDb252ZW5vcgcHVGl0bGUHTGlhaXNv
biBzdGF0ZW1lbnQgdGVtcGxhdGUgb24gY29kZWMgaW5kZXBlbmRlbnQgbWVkaWEgZGVzY3Jp
cHRpb24gY29kZXBvaW50cwcHVG8HBwcNIA1JU08vSUVDIEpUQyAxL1NDIDI5L1dHIDExIChN
UEVHKSBoYXZlIG9ic2VydmVkIHRoYXQgd2UgaGF2ZSBhIG51bWJlciBvZiBjb2RlIHBvaW50
cyB0byBkZXNjcmliZSBtZWRpYSB0aGF0IGFyZSB1c2VkIGluIHNldmVyYWwgc3BlY2lmaWNh
dGlvbnMsIG9mdGVuIGR1cGxpY2F0aW5nIHRleHQ7IHRoZXNlIGNvZGUgcG9pbnRzIGRvY3Vt
ZW50IGFzcGVjdHMgb2YgbWVkaWEgc3RyZWFtcyB0aGF0IGFyZSBpbmRlcGVuZGVudCBvZiB0
aGUgY29tcHJlc3Npb24gZm9ybWF0IHVzZWQuIA0NV2UgaGF2ZSBkZWNpZGVkIHRvIG1ha2Ug
YSBzaW5nbGUgc3BlY2lmaWNhdGlvbiBmb3IgdGhlIGRlZmluaXRpb24gb2YgdGhlc2UgY29k
ZSBwb2ludHMsIGVuYWJsaW5nIG90aGVyIHNwZWNpZmljYXRpb25zIHRvIHJlZmVyIHRvIHRo
aXMuICBXZSBiZWxpZXZlIHRoYXQgdGhpcyBzaG91bGQgaGVscCBub3Qgb25seSBpbiBwcm92
aWRpbmcgYSBjb25zaXN0ZW50IHNldCBvZiB2YWx1ZXMgZm9yIHRoZXNlIChtYW55IG9mIHdo
aWNoIGFyZSBlbnVtZXJhdGlvbnMpIGJ1dCBhbHNvIGNvbnNpc3RlbnQgc2VtYW50aWNzLCBl
bmFibGluZyB0aGVpciBjYXJyaWFnZSBhbmQgY29tcGFyaXNvbiBhY3Jvc3MgYW5kIGJldHdl
ZW4gbXVsdGlwbGUgZm9ybWF0cyBhbmQgc3RyZWFtcy4NDVRoZSBpbml0aWFsIHdvcmtpbmcg
ZHJhZnQgY29udGFpbnMgaW5pdGlhbCBjb2RlIHBvaW50cyBmb3IgdGhlIGZvbGxvd2luZyBt
ZWRpYSBkZXNjcmlwdGlvbnM6DVZpZGVvIENvbG91ciBQcmltYXJpZXMNVmlkZW8gQ29sb3Vy
IFRyYW5zZmVyIENoYXJhY3RlcmlzdGljcw1WaWRlbyBNYXRyaXggQ29sb3VyIENvZWZmaWNp
ZW50cw1TdGVyZW8gVmlkZW8gRnJhbWUgUGFja2luZw1TdGVyZW8gVmlkZW8gVmlldyBBc3Np
Z25tZW50DUF1ZGlvIENoYW5uZWwgQ29uZmlndXJhdGlvbg1BdWRpbyBDaGFubmVsIEFzc2ln
bm1lbnQNQXVkaW8gRGlhbG9nIExldmVsDUF1ZGlvIER5bmFtaWMgUmFuZ2UNDVdlIGFyZSBh
bHNvIGNvbnNpZGVyaW5nIHRoZSBhZGRpdGlvbiBvZiBjb2RlIHBvaW50cyBmb3IgY29kZWMg
bmFtZXMsIGJ1dCBoYXZlIG5vdCByZWFjaGVkIGNvbmNsdXNpb24geWV0IGlmIHRoaXMgd2ls
bCBiZSBzdWl0YWJsZS4NDVlvdXIgY29tbWVudHMgb24gdGhpcyBhcHByb2FjaCBhcmUgd2Vs
Y29tZSwgYW5kIHdlIHdvdWxkIGFsc28gd2VsY29tZSBzdWdnZXN0aW9ucyBmb3IgY29kZSBw
b2ludHMgZm9yIG1lZGlhIGRlc2NyaXB0aW9ucyB5b3UgZmVlbCBzaG91bGQgYmUgY29uc2lk
ZXJlZCBmb3IgaW5jbHVzaW9uIGluIHN1Y2ggYSBzcGVjaWZpY2F0aW9uLCBpZGVhbGx5IHdp
dGggYSBzdWdnZXN0aW9uIGZvciB0aGUgaW5pdGlhbCBkZWZpbml0aW9uIG9yIHBvaW50ZXIg
dG8gc3BlY2lmaWNhdGlvbiB3aGVyZSBzdWNoIGNvZGUgcG9pbnRzIGFyZSBkZWZpbmVkLg0D
DQ0EDQ0DDQ0EDQ0NDQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAYAAC8IAACWCAAArggAAK8IAACwCAAAtQgAALYIAAC+CAAA
wQgAAMMIAADFCAAA2AgAANkIAADaCAAA2wgAAOIIAADqCAAA8ggAAD4JAABACQAAQgkAAEMJ
AABECQAARQkAAEYJAADz7Ofi07+vqp+WjqqEjn11cHVodWN1WExIAAAAAAAAAAAAAAAAAAAA
BhZo5TqxAAAXFWjhHqoAFmjhHqoAbkgRBG8oAXRIEQQUFWjhHqoAFmjhHqoAbkgRBHRIEQQA
CRZolTFDADUIgQ8VaPFs3gAWaPFs3gA1CIEJFmjiVDkANQiBDxVomWNwABZo4R6qADUIgQwV
aLIF3gAWaO5pbwAAEhVoKl2BABZo7mlvADUIgW8oAQAPFWgqXYEAFmjuaW8ANQiBERZoFCtl
ADUIgW5IEQR0SBEEFBZo9kkXADUIgW5IEQRvKAF0SBEEAAkWaBQrZQA1CIEeFWjQJQ0AFmju
aW8ANQiBUEoDAG5IEgRvKAF0SBIEACcVaNAlDQAWaPFs3gA1CIFCKgZQSgMAbkgSBG8oAXBo
/wAAAHRIEgQdFmj2SRcANQiBQioGbkgRBG8oAXBo/wAAAHRIEQQJFmjhHqoANQiBCRZo7mlv
ADUIgQ0WaO5pbwA1CIFDShwAFxVoixjAABZo7mlvADUIgUNKHABhShwAABkABgAALwgAAFwI
AABzCAAAlwgAAJgIAAC2CAAA2QgAANoIAADbCAAA4ggAAOsIAADsCAAA9wAAAAAAAAAAAAAA
APcAAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAOgAAAAAAAAAAAAAAADg
AAAAAAAAAAAAAAAA2AAAAAAAAAAAAAAAANgAAAAAAAAAAAAAAADQAAAAAAAAAAAAAAAAwgAA
AAAAAAAAAAAAAMIAAAAAAAAAAAAAAABrAAAAAAAAAAAAAAAAAAAAAAAAAFYAAGtkAAAAABYk
ARckAUlmAQAAAAKWbAAI1jAAApT/zAP3JAAGOAQAAAAAAAAAAAAAAAAAAAAAAAYrIQAAAAAA
AAAAAAAAAAAAAAAKdAAA4AEU9gEAABU2ARf2AwAAGPYDAAAa1ggAAAD/AAAA/xvWCAAAAP8A
AAD/HNYIAAAA/wAAAP8d1ggAAAD/AAAA/zTWBgABBQMAADTWBgABCgNsAGH2AwAAeXSZY3AA
AA0AAAMkAxYkASokAUlmAQAAAGEkA2dkmWNwAAAHAAASZBD/AABnZO5pbwAABwAAAyQCYSQC
Z2QqXYEAAAcAAAMkAmEkAmdk4R6qAAAOAAADJAENxgUAAQsVABJkEP8AAGEkAWdk7mlvAAAH
AAADJAFhJAFnZO5pbwAADAAGAADfDgAA7A4AAP39AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQAAQEC7AgAAPIIAAA/CQAA
QAkAAEMJAABECQAA8QAAAAAAAAAAAAAAAOMAAAAAAAAAAAAAAACMAAAAAAAAAAAAAAAAgwAA
AAAAAAAAAAAAAHoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAkAABYkAUlmAQAAAGdkFCtlAAkAABYkAUlmAQAAAGdk4R6qAABW
AABrZGUAAAAWJAEXJAFJZgEAAAAClmwACNYwAAKU/8wD9yQABjgEAAAAAAAAAAAAAAAAAAAA
AAAGKyEAAAAAAAAAAAAAAAAAAAAACnQAAOABFPYBAAAVNgEX9gMAABj2AwAAGtYIAAAA/wAA
AP8b1ggAAAD/AAAA/xzWCAAAAP8AAAD/HdYIAAAA/wAAAP801gYAAQUDAAA01gYAAQoDbABh
9gMAAHl0mWNwAAANAAADJAMWJAEqJAFJZgEAAABhJANnZJUxQwAADQAAAyQDFiQBKiQBSWYB
AAAAYSQDZ2SZY3AAAAVECQAARQkAAEYJAABICQAAWQoAAFoKAADXCwAA2AsAADUMAABMDAAA
cgwAAJMMAACuDAAAywwAAOcMAAAADQAAEw0AACcNAACoAAAAAAAAAAAAAAAApgAAAAAAAAAA
AAAAAKAAAAAAAAAAAAAAAACbAAAAAAAAAAAAAAAAmwAAAAAAAAAAAAAAAJsAAAAAAAAAAAAA
AACbAAAAAAAAAAAAAAAAmwAAAAAAAAAAAAAAAJMAAAAAAAAAAAAAAACTAAAAAAAAAAAAAAAA
kwAAAAAAAAAAAAAAAJMAAAAAAAAAAAAAAACTAAAAAAAAAAAAAAAAkwAAAAAAAAAAAAAAAJMA
AAAAAAAAAAAAAACTAAAAAAAAAAAAAAAAkwAAAAAAAAAAAAAAAAAIAAAKJgALRgIAZ2TiVDkA
AAQAAGdkzXH1AAYAAEAmAGdksgXeAAABAAAAVgAAa2TKAAAAFiQBFyQBSWYBAAAAApZsAAjW
MAAClP/MA/ckAAY4BAAAAAAAAAAAAAAAAAAAAAAABishAAAAAAAAAAAAAAAAAAAAAAp0AADg
ART2AQAAFTYBF/YDAAAY9gMAABrWCAAAAP8AAAD/G9YIAAAA/wAAAP8c1ggAAAD/AAAA/x3W
CAAAAP8AAAD/NNYGAAEFAwAANNYGAAEKA2wAYfYDAAB5dJljcAAAEUYJAABHCQAASAkAAFMJ
AABUCQAAWAkAAFkJAABeCQAAXwkAAGkJAACcCQAAsgkAANcLAAD7CwAAAgwAACcNAAAoDQAA
rA0AAA4OAAAlDgAAfw4AAN4OAADfDgAA4A4AAOIOAADjDgAA5Q4AAOYOAADoDgAA6Q4AAOwO
AADtDgAA9uni2eLZ4tni1dHV0c3R1dHV0dXRycG9wb3BvcG9yQAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYWaLh1/AAADwNqAAAA
ABZouHX8AFUIAQYWaLIF3gAABhZoxVOhAAAGFmjiVDkAAAYWaM1x9QAAERZo2T5hAG5IEQRv
KAF0SBEEDBVolTFDABZolTFDAAAYFWiyBd4AFmiyBd4AQ0oWAG1IBwRzSAcEABIWaLIF3gBD
ShYAbUgHBHNIBwQfJw0AACgNAACrDQAArA0AAN8OAADhDgAA4g4AAOQOAADlDgAA5w4AAOgO
AADqDgAA6w4AAOwOAADtDgAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+AAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAAD4AAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAA
APgAAAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA+AAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAAD4
AAAAAAAAAAAAAAAA+AAAAAAAAAAAAAAAAPgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAQAAGdk8WzeAAABAAAABAAAZ2TNcfUAAA42ACZQCQAxkGgBOnDZPmEA
H7CDLiCwyEEhsG4EIrBuBCOQbgQkkIoFJbAAABewxQIYsMUCDJDQAgAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAGMAFiQBFyQBSWYBAAAAAZYAACF2AAJoATXWBQABAzgENdYFAQIDKyEjdgAB
OAQjdgECKyE6VgsAApZsAAp0AADgART2AQAAFTYBGPYDAAA11gUAAQM4BDXWBQECAysheXSZ
Y3AAYwAWJAEXJAFJZgEAAAABlgAAIXYAAmgBNdYFAAEDOAQ11gUBAgMrISN2AAE4BCN2AQIr
ITpWCwAClmwACnQAAOABFPYBAAAVNgEY9gMAADXWBQABAzgENdYFAQIDKyF5dJljcABjABYk
ARckAUlmAQAAAAGWAAAhdgACaAE11gUAAQM4BDXWBQECAyshI3YAATgEI3YBAishOlYLAAKW
bAAKdAAA4AEU9gEAABU2ARj2AwAANdYFAAEDOAQ11gUBAgMrIXl0mWNwAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AACGAhYAEgABAJwADwAEAAAABAAAAAAABAAIAAAACAAAAA4AAAAOAAAADgAAAA4AAAAOAAAA
DgAAAA4AAAAOAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
DgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAA
CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAA4AABA8f8CADgADBAAAO5pbwAAAAIAGWqWbgAAAgAAABgAQ0oYAF9IAQRhShgAbUgJBHNI
CQR0SAkEAAAAAAAAAAAAAAAAAAAAAAAAJABBAPL/oQAkAAwBAAAAAAAAAAAGALVrPYTVMKkw
8zDIMAAAAABCAGlA8/+zAEIADAEAAAAAAAAAAAQAGWqWbm4waIgAABwAF/YDAAA01gYAAQoD
bAA01gYAAQUDAABh9gMAAAIACwAAACQAawD0/8EAJAAAAQAAAAAAAAAABQDqMLkwyDBqMFcw
AAACAAwAAAAAAGIAmgCzAPMAYgAMBAAA4R6qAAAABgBoiCAAKAA8aFBbKQAAADcAOlYPABPW
MAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAACAA8A
AAA8AJlAAQACATwADAQRAIUx/AAAAAQAOVRNMPpRVzAAAAIAEAAYAENKEgBPSgUAUUoFAGFK
EgBtSAAAc0gAAEYA/k/y/xEBRgAMABAAhTH8AAAACwAgACgAh2VXWykAIAAoAIdlV1spADIA
AAAYAENKEgBPSgUAUUoFAF5KBQBhShIAdEgJBDoAH0ABACIBOgAMBBMA8WzeAAAABADYMMMw
wDD8MAAAEAASAA3GCAACoRFCIwECRyQACABtSAAAc0gAADoA/k/y/zEBOgAMABIA8WzeAAAA
CwAgACgAh2VXWykAIAAoAIdlV1spADEAAAAMAENKGABhShgAdEgJBDoAIEABAEIBOgAMBBUA
8WzeAAAABADVMMMwvzD8MAAAEAAUAA3GCAACoRFCIwECRyQACABtSAAAc0gAADgA/k/y/1EB
OAAMABQA8WzeAAAACgAgACgAh2VXWykAIAAoAIdlV1spAAAADABDShgAYUoYAHRICQQAAAAA
7QYAAAUAAB4AAAAA/////wAAAAAvAAAAXAAAAHMAAACXAAAAmAAAALYAAADZAAAA2gAAANsA
AADiAAAA6wAAAOwAAADyAAAAPwEAAEABAABDAQAARAEAAEUBAABGAQAASAEAAFkCAABaAgAA
1wMAANgDAAA1BAAATAQAAHIEAACTBAAArgQAAMsEAADnBAAAAAUAABMFAAAnBQAAKAUAAKsF
AACsBQAA3wYAAOEGAADiBgAA5AYAAOUGAADnBgAA6AYAAOoGAADrBgAA7gYAAJgAAAAAMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
ADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAA
IACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAmQAAAAAwAAAAAAAAAIAAAACAAQAA1AAA
AAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQ
AAAAACAAmQAAAAAwAAAAAAAAAIAAAACAAQAA1AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEA
ANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAmQAAAAAwAAAAAAAAAIAAAACA
AQAA1AAAAAAgAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAAAIAAAAADAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAIgADAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAACIAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAiAAMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAIgADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAACIAAw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAiAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAIg
ADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAACIAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AiAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAqNEAMAAwAAAAAAAAAQAAAAAAAAAAAAAA
AABEB6iRADAAMAAAAAAAAAEAAAAAAAAAAAAAAAAARAeo0QAwADAAAAAAAAABAAAAAAAAAAAA
AAAAAEQHqJEAMAAwAAAAAAAAAQAAAAAAAAAAAAAAAABEB6jRADAAMAAAAAAAAAEAAAAAAAAA
AAAAAAAARAeokQAwADAAAAAAAAABAAAAAAAAAAAAAAAAAEQHqNEAMAAwAAAAAAAAAQAAAAAA
AAAAAAAAAABEB6iRADAAMAAAAAAAAAEAAAAAAAAAAAAAAAAARAeokQAwADAAAAAAAAABAAAA
AAAAAAAAAABcMEQHAAAAAAMAAAAGAAAABgAAAAkAAAAMAAAADAAAAAwAAAAMAAAADAAAAAwA
AAAMAAAADAAAAA8AAAAABgAARgkAAO0OAAAIAAAADQAAAAAGAADsCAAARAkAACcNAADtDgAA
CQAAAAsAAAAMAAAADgAAAAAGAADsDgAACgAAAA8AAPBgAAAAAAAG8CAAAAACDAAAAwAAAAIA
AAACAAAAAQAAAAIAAAACAAAAAQAAAEMAC/AYAAAAgQA3IgEAggC6IgAAgwA3IgEAhAC6IgAA
QAAe8RAAAAD//wAAAAD/AICAgAD3AAAQAQ8AAvBIAAAAIAAI8AgAAAABAAAAAAgAAA8AA/Aw
AAAADwAE8CgAAAABAAnwEAAAAAAAAAAAAAAAAAAAAAAAAAACAArwCAAAAAAIAAAFAAAAAA8A
AvCSAAAAEAAI8AgAAAABAAAAAQQAAA8AA/AwAAAADwAE8CgAAAABAAnwEAAAAAAAAAAAAAAA
AAAAAAAAAAACAArwCAAAAAAEAAAFAAAADwAE8EIAAAASAArwCAAAAAEEAAAADgAAUwAL8B4A
AAC/AQAAEADLAQAAAAD/AQAACAAEAwkAAAA/AwEAAQAAABHwBAAAAAEAAAD//wcAAAAGAD2d
SQEQAAEA3Ap6CQYAPp1JAREAAQBcCnoJBgA/nUkBEQABAJwLegkGAECdSQEQAAEAJJ2ICQYA
QZ1JAREAAQBknYgJBgBCnUkBEQABAKSdiAkGAEOdSQERAAEA5J2ICcUAAADFAAAAzQAAABMF
AAATBQAAGQUAACEFAADuBgAAAQAAAAIAAAAAAAIAAgAAAAIABQAAAAIAAwAAAAIABAAAAAIA
BgAAAAIAywAAANgAAADYAAAAGAUAACAFAAAmBQAAJgUAAO4GAAABAAEAAAAAAAIAAAAEAAEA
BQABAAMAAAAGAAAABQAAAD0AAAABAAAAKoB1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9m
ZmljZTpzbWFydHRhZ3MJgFBsYWNlVHlwZQCAPQAAAAMAAAAqgHVybjpzY2hlbWFzLW1pY3Jv
c29mdC1jb206b2ZmaWNlOnNtYXJ0dGFncwmAUGxhY2VOYW1lAIBCAAAABQAAACqAdXJuOnNj
aGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6c21hcnR0YWdzDoBjb3VudHJ5LXJlZ2lvbgCA
OAAAAAYAAAAqgHVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOnNtYXJ0dGFncwSA
Q2l0eQCAOQAAAAcAAAAqgHVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOnNtYXJ0
dGFncwWAcGxhY2UAgAwAAAGU3W0DAAAAAAcAAAAAAAYAAAAAAAUAAAAAAAcAAAAAAAMAAAAA
AAMAAAAAAAEAAAAAAAAAAADiAAAA6gAAADQBAAA+AQAAOwQAAEEEAABSBAAAWAQAAH8EAACF
BAAA3wYAAN8GAADhBgAA4QYAAOIGAADiBgAA5AYAAOUGAADnBgAA6AYAAOoGAADrBgAA7gYA
AAcAHAAHABwABwAcAAcAHAAHABwABwAEAAcABAACAAQABwAEAAcABAAHAAQAAgAAAAAA3wYA
AN8GAADhBgAA4QYAAOIGAADiBgAA5AYAAOUGAADnBgAA6AYAAOoGAADrBgAA7gYAAAcABAAH
AAQAAgAEAAcABAAHAAQABwAEAAIAAAAAALYAAADyAAAAQAEAAEMBAAA1BAAAKAUAAN8GAADf
BgAA4QYAAOEGAADiBgAA4gYAAOQGAADlBgAA5wYAAOgGAADqBgAA6wYAAO4GAAAHAAUABwAF
AAcABQAHAAQABwAEAAIABAAHAAQABwAEAAcABAACAAAAAADfBgAA3wYAAOEGAADhBgAA4gYA
AOIGAADkBgAA5QYAAOcGAADoBgAA6gYAAOsGAADuBgAABwAEAAcABAACAAQABwAEAAcABAAH
AAQAAgACAB3///8cuPYB/w//D/8P/w//D/8P/w//D/8PAAB/T9M7oESa9P8P/w//D/8P/w//
D/8P/w//DxAAAQAAABcAAAAAAAAAAAAAAAAAAAAAAAAACxgAAA+EAAARhAAAFcYFAAEAAAZe
hAAAYIQAAE9KAQBRSgEAbygAAAABAAAAFwAAAAAAAAAAAAAAAAAAAAAAAAALGAAAD4Q4BBGE
mP4VxgUAAdACBl6EOARghJj+T0oBAFFKAQBvKAABALfwAQAAABcAAAAAAAAAAAAAAAAAAAAA
AAAADxgAAA+ECAcRhJj+FcYFAAGgBQZehAgHYISY/k9KBgBRSgYAXkoGAG8oAAEAbwABAAAA
FwAAAAAAAAAAAAAAAAAAAAAAAAALGAAAD4TYCRGEmP4VxgUAAXAIBl6E2AlghJj+T0oHAFFK
BwBvKAABAKfwAQAAABcAAAAAAAAAAAAAAAAAAAAAAAAACxgAAA+EqAwRhJj+FcYFAAFACwZe
hKgMYISY/k9KBwBRSgcAbygAAQD68AEAAAAXAAAAAAAAAAAAAAAAAAAAAAAAAAsYAAAPhHgP
EYSY/hXGBQABEA4GXoR4D2CEmP5PSgEAUUoBAG8oAAEAt/ABAAAAFwAAAAAAAAAAAAAAAAAA
AAAAAAAPGAAAD4RIEhGEmP4VxgUAAeAQBl6ESBJghJj+T0oGAFFKBgBeSgYAbygAAQBvAAEA
AAAXAAAAAAAAAAAAAAAAAAAAAAAAAAsYAAAPhBgVEYSY/hXGBQABsBMGXoQYFWCEmP5PSgcA
UUoHAG8oAAEAp/ABAAAAFwAAAAAAAAAAAAAAAAAAAAAAAAALGAAAD4ToFxGEmP4VxgUAAYAW
Bl6E6BdghJj+T0oHAFFKBwBvKAABAPrwAQAAABcQAAAAAAAAAAAAAGgBAAAAAAAAFRAAAA+E
0AIRhJj+XoTQAmCEmP5PSgEAUUoBAG8oAIdoAAAAAIhIAAABALfwAQAAABeQAAAAAAAAAAAA
AGgBAAAAAAAAGRAAAA+EoAURhJj+XoSgBWCEmP5PSgYAUUoGAF5KBgBvKACHaAAAAACISAAA
AQBvAAEAAAAXkAAAAAAAAAAAAABoAQAAAAAAABUQAAAPhHAIEYSY/l6EcAhghJj+T0oHAFFK
BwBvKACHaAAAAACISAAAAQCn8AEAAAAXkAAAAAAAAAAAAABoAQAAAAAAABUQAAAPhEALEYSY
/l6EQAtghJj+T0oBAFFKAQBvKACHaAAAAACISAAAAQC38AEAAAAXkAAAAAAAAAAAAABoAQAA
AAAAABkQAAAPhBAOEYSY/l6EEA5ghJj+T0oGAFFKBgBeSgYAbygAh2gAAAAAiEgAAAEAbwAB
AAAAF5AAAAAAAAAAAAAAaAEAAAAAAAAVEAAAD4TgEBGEmP5ehOAQYISY/k9KBwBRSgcAbygA
h2gAAAAAiEgAAAEAp/ABAAAAF5AAAAAAAAAAAAAAaAEAAAAAAAAVEAAAD4SwExGEmP5ehLAT
YISY/k9KAQBRSgEAbygAh2gAAAAAiEgAAAEAt/ABAAAAF5AAAAAAAAAAAAAAaAEAAAAAAAAZ
EAAAD4SAFhGEmP5ehIAWYISY/k9KBgBRSgYAXkoGAG8oAIdoAAAAAIhIAAABAG8AAQAAABeQ
AAAAAAAAAAAAAGgBAAAAAAAAFRAAAA+EUBkRhJj+XoRQGWCEmP5PSgcAUUoHAG8oAIdoAAAA
AIhIAAABAKfwAgAAAB3///8AAAAAAAAAAAAAAAB/T9M7AAAAAAAAAAAAAAAA////////////
/wIAAAAAAAAA//8CAAAAAAASAAEABwQDAAcEBQAHBAEABwQDAAcEBQAHBAEABwQDAAcEBQAH
BD8AAAAEAAAACAAAAOUAAAAAAAAAPgAAAAx1AABpZwUA0CUNAPZJFwAAZxcAlAMlALBfJwDX
TioAHTAsACAQMwByLDkA4lQ5ANQ7PgCVMUMAzGJSAAJSVwDYUFsA2T5hAJB3ZAAUK2UAYEBt
AO5pbwCZY3AA0DdxAAp9cwC3OHQAmSx2AFYkeQDhKXkAtwp9ACpdgQB0YYEAqQ6EABAYjgAp
EpQAzGOXAKd7mQASG5oAX2icAMVToQDdMqQAQlekAOEeqgDlOrEAYnq3AFQkugD7Bb0AeQ29
AIhOvQBcE74AnCDHAGV2zQBYKNoAcX3dALIF3gDxbN4AzXH1ANlQ+AC8RfsAhTH8ALh1/ABX
O/0A2kP/AAAAAADaAAAA2wAAAOIAAADrAAAA7AAAAPIAAAA/AQAAQAEAAEMBAABEAQAARQEA
AN4GAADuBgAAAAAAAHmANQAIAAAAAgEAAAIBAACeAQAAAgEAAAIBAACeAQAAAgEAAAIBAACW
AQAAAQAAAP9AAYABADECAAAxAgAAHExtAwEAAQAxAgAAAAAAADECAACU/8B7AhAAAAAAAAAA
7QYAAFAAABAAQAAA//8BAAAABwBVAG4AawBuAG8AdwBuAP//AQAIAAAAAAAAAAAAAAD//wEA
AAAAAP//AAACAP//AAAAAP//AAACAP//AAAAAAgAAABHFpABAAACAgYDBQQFAgME7zoA4EF4
AMAJAAAAAAAAAP8BAAAAAAAAVABpAG0AZQBzACAATgBlAHcAIABSAG8AbQBhAG4AAAA1FpAB
AgAFBQECAQcGAgUHAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAUwB5AG0AYgBvAGwAAAAzJpAB
AAACCwYEAgICAgIE/zoA4EN4AMAJAAAAAAAAAP8BAAAAAAAAQQByAGkAYQBsAAAAQyaQAYEA
AgsFAwIAAAIABK8CAJD7fNcJEgAAAAAAAAABAAgAAAAAAE0AYQBsAGcAdQBuACAARwBvAHQA
aABpAGMAAABHFZABgAYCAgYJBAIFCAME/wIA4Pv9x2oSAAAAAAAAAJ8AAgAAAAAALf8z/yAA
DmYdZwAATQBTACAATQBpAG4AYwBoAG8AAABDBpABAAACCwYABAUCAgIE7woA4f+hAFAAAAAA
AAAAAL8BAAAAAAAATAB1AGMAaQBkAGEAIABHAHIAYQBuAGQAZQAAAD81kAEAAAIHAwkCAgUC
BAT/OgDgQ3gAwAkAAAAAAAAA/wEAAAAAAABDAG8AdQByAGkAZQByACAATgBlAHcAAAA7BpAB
AgAFAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAVwBpAG4AZwBkAGkAbgBnAHMA
AAAiAAQAMQiIGADw0AIAAGgBAAAAALoT/KbWM/xGAAAAAAQABAAAAAYBAADZBQAAAQADAAAA
BAADEAwAAAAGAQAA2QUAAAEAAwAAAAwAAAAAAAAAwQMA8BAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAbgRuBHgAtACCghI0AAAAAAAAAAAAAAAAAADcBgAA
3AYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAIAAAAAAAAAAAAMMoNxAPAQAAgA//0BAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAEhYAAAAAAnw/w8BAAE/AACkAwAA////f////3////9/////f////3////9/////f+U6
sQAABAAAMgAAAAAAAAAAAAAAAAAAAAAA//8SAAAAAAAAAC4ASQBOAFQARQBSAE4AQQBUAEkA
TwBOAEEATAAgAE8AUgBHAEEATgBJAFMAQQBUAEkATwBOACAARgBPAFIAIABTAFQAQQBOAEQA
QQBSAEQASQBTAEEAVABJAE8ATgAAAAAAAAAFAG8AZwB1AHIAYQAOAFkAbwBrAG8AIABIAGkA
ZwBhAHMAaABpAGQAYQAAAAAAAAAAAAAAAAAAAAAAAAAAABQAAAAGAAAAAgAAAAAADAABAAwA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAD+/wAABgACAAAAAAAAAAAAAAAAAAAAAAABAAAA4IWf8vlPaBCrkQgA
Kyez2TAAAACMAQAAEAAAAAEAAACIAAAAAgAAAJAAAAADAAAAyAAAAAQAAADUAAAABQAAAOQA
AAAHAAAA8AAAAAgAAAAEAQAACQAAABwBAAASAAAAKAEAAAoAAABIAQAADAAAAFQBAAANAAAA
YAEAAA4AAABsAQAADwAAAHQBAAAQAAAAfAEAABMAAACEAQAAAgAAAKQDAAAeAAAAMAAAAElO
VEVSTkFUSU9OQUwgT1JHQU5JU0FUSU9OIEZPUiBTVEFOREFSRElTQVRJT04AAB4AAAAEAAAA
AAAAAB4AAAAIAAAAb2d1cmEAAAAeAAAABAAAAAAAAAAeAAAADAAAAE5vcm1hbC5kb3QAAB4A
AAAQAAAAWW9rbyBIaWdhc2hpZGEAAB4AAAAEAAAANAAAAB4AAAAYAAAATWljcm9zb2Z0IE9m
ZmljZSBXb3JkAAAAQAAAAAAYDY8AAAAAQAAAAADkqli3sMwBQAAAAAB0oFzfs8wBAwAAAAEA
AAADAAAABgEAAAMAAADZBQAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAA/v8AAAYAAgAAAAAAAAAAAAAAAAAAAAAAAQAAAALVzdWcLhsQk5cIACss+a4wAAAA
HAEAAAwAAAABAAAAaAAAAA8AAABwAAAABQAAAIAAAAAGAAAAiAAAABEAAACQAAAAFwAAAJgA
AAALAAAAoAAAABAAAACoAAAAEwAAALAAAAAWAAAAuAAAAA0AAADAAAAADAAAAPsAAAACAAAA
pAMAAB4AAAAIAAAASVRTQ0oAAAADAAAADAAAAAMAAAADAAAAAwAAANwGAAADAAAADycLAAsA
AAAAAAAACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAAHhAAAAEAAAAvAAAASU5URVJOQVRJT05B
TCBPUkdBTklTQVRJT04gRk9SIFNUQU5EQVJESVNBVElPTgAMEAAAAgAAAB4AAAAGAAAAVGl0
bGUAAwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA
AAACAAAAAwAAAAQAAAAFAAAABgAAAAcAAAAIAAAACQAAAAoAAAALAAAADAAAAA0AAAAOAAAA
DwAAAP7///8RAAAAEgAAABMAAAAUAAAAFQAAABYAAAAXAAAA/v///xkAAAAaAAAAGwAAABwA
AAAdAAAAHgAAAB8AAAAgAAAAIQAAACIAAAAjAAAAJAAAACUAAAAmAAAA/v///ygAAAApAAAA
KgAAACsAAAAsAAAALQAAAC4AAAD+////MAAAADEAAAAyAAAAMwAAADQAAAA1AAAANgAAAP7/
///9////OQAAAP7////+/////v//////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////UgBvAG8AdAAgAEUAbgB0AHIAeQAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYABQH//////////wMAAAAGCQIA
AAAAAMAAAAAAAABGAAAAAAAAAAAAAAAAsAw3ZN+zzAE7AAAAgAAAAAAAAABEAGEAdABhAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
CgACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAA
AAAAEAAAAAAAADEAVABhAGIAbABlAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAOAAIBAQAAAAYAAAD/////AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAGAAAALwdAAAAAAAAVwBvAHIAZABEAG8AYwB1AG0AZQBuAHQA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABoAAgECAAAABQAAAP//
//8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOB4AAAAAAAAFAFMA
dQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAKAACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAACcAAAAAEAAAAAAAAAUARABvAGMAdQBtAGUAbgB0AFMAdQBtAG0AYQByAHkASQBuAGYA
bwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAA4AAIBBAAAAP//////////AAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAALwAAAAAQAAAAAAAAAQBDAG8AbQBwAE8AYgBqAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAgD/////
//////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAbQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAD+////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////AQD+/wMK
AAD/////BgkCAAAAAADAAAAAAAAARhsAAABNaWNyb3NvZnQgT2ZmaWNlIFdvcmQglbaPkQAK
AAAATVNXb3JkRG9jABAAAABXb3JkLkRvY3VtZW50LjgA9DmycQAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAA=
--B_3406090145_2752175--



From albrecht.schwarz@alcatel-lucent.com  Wed Dec  7 08:25:01 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 561E321F8C7A; Wed,  7 Dec 2011 08:25:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.668
X-Spam-Level: 
X-Spam-Status: No, score=-5.668 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KJPYPjNh14u9; Wed,  7 Dec 2011 08:24:59 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 2AAC221F8C51; Wed,  7 Dec 2011 08:24:58 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB7GOJ4v023844 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Dec 2011 17:24:27 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 7 Dec 2011 17:24:25 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Wed, 7 Dec 2011 17:24:24 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acyz3rfKeCMWWyKTRsuT81eZDiECHgBHEUng
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com>
In-Reply-To: <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 16:25:01 -0000

Qin,
that's NOT the point.

All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL ENTITIES (FE).
e.g.,
- the RTP Monitor or RTP receiver FE may be located in different PHYSICAL E=
NTITIES (PE), e.g.
        a1) a user equipment
        a2) a RTP-to-PSTN gateway
        a3) an IP-to-IP session border gateway (in a back-to-back RTP endsy=
stem topology)
        a3) ...

- the RTP Monitor may be associated to an RTP transport translator ...
        b1) an IP-to-IP session border gateway

The "RTP monitoring architecture" is IMPACTED by each functional-to-physica=
l mapping because e.g.
* QoE related metrics are questionable in case of a2 ("despite the fact of =
a RTP receiver function")
* application level metrics at the location of a RTP transport translator a=
re a contradiction in itself
* ...

Again, it's not really changing the MONARCH draft because in the very major=
ity of scenarios it is correct. However, there are few cases where the MONA=
RCH description would be "too high level", "not fully correct", "lead to po=
ssible wrong expectations", ...

Regards,
Albrecht



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Dienstag, 6. Dezember 2011 07:13
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> If you talk about existing RFC5117 RTP topology components,
> this has already been covered by the current version of
> draft-ietf-avtcore-monarch.
> In most cases, an RTP system using RTCP XR is architecturally
> no different from an RTP system which does not use RTCP XR.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Monday, December 05, 2011 10:48 PM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Hello Qin,
>
> to 1) Physical monitoring architecture
> Of course consideration of generic physical entities (PE),
> not specific to any network reference architectures defined
> by SDOs (like your refered entities).
> There would be just a few PE types ("given by the limited set
> of RTP topology components (RFC 5117)").
>
> to 2) (RFC 3550) Monitor function
> Right, that's a functional entity. The applicability of a
> monitor may be limited, dependent on ... (like in P.NAMS).
>
> to 3) your IMS network example
> Don't see the need to refer from MONARCH to a specific
> network architecture like IMS.
> Please also note that IMS is a functional architecture, not a
> physical architecture.
>
> Regards,
> Albrecht
>
> PS
> There are multiple options for adding the "RTP monitoring
> architecture" to a functional/physical network architecture:
> a) integrated approach: extension of existing functional
> entities or/and addition of RTP monitoring architectural
> components, extension or/and addition of
> signalling/management interfaces for control and
> configuration of RTP monitoring services, and reporting
> interfaces for measurement data ...
> b) overlay approach: separate specification to ...
>
>
> PSS
> BTW: there's a discussion paper with regards to the location
> of a monitor function in an IMS H.248 gateway entity:
> Measurements and statistics in IMS - Use Cases
> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> 8_Kyoto_Japan/Docs/C3-100469.zip
> This is just fyi.
>
>
>
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf Of Qin Wu
> > Sent: Freitag, 2. Dezember 2011 02:55
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi, Albrecht:
> > No offence, I am not really convinced with your proposal on
> > physical monitoring architecture.
> >  my counterquestion is what does physical monitoring
> > architecture looks like in your mind?
> > How many components do we have in such physical monitroing
> > architecture? what are they?
> > Take IMS network architecture as a example, they may have
> > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > described in draft-ietf-avtcore-monarch is mapped into
> > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > should be in the scope of IETF RTP monitoring archtiecture draft?
> >
> > Monitor described in  draft-ietf-avtcore-monarch is well
> > defined in the section 3 of RFC3550 as follows:
> > "
> >
> >    Monitor: An application that receives RTCP packets sent by
> >       participants in an RTP session, in particular the reception
> >       reports, and estimates the current quality of service for
> >       distribution monitoring, fault diagnosis and long-term
> > statistics.
> >       The monitor function is likely to be built into the
> > application(s)
> >       participating in the session, but may also be a separate
> >       application that does not otherwise participate and
> > does not send
> >       or receive the RTP data packets (since they are on a separate
> >       port).  These are called third-party monitors.  It is also
> >       acceptable for a third-party monitor to receive the RTP data
> >       packets but not send RTCP packets or otherwise be
> counted in the
> >       session.
> >
> > "
> > Isn't how to implent monitor into IMS netowork archtiecture a
> > implentation specific issue?
> > If this issue are really interesting, isn't it a good idea to
> > produce another new document to talk about this?
> > One good example for this motivation is this draft I like to
> > share with you:
> > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > y-00#section-4.6
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Friday, December 02, 2011 12:20 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > My replies below ...
> > -Albrecht
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi,
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Thursday, December 01, 2011 1:24 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > My replies below inline,
> > > Albrecht
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi,
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > > Dear All,
> > > > >
> > > > > there are different types of monitoring architectures,
> > > > particularily from perspective of QoE related performance
> > > parameters.
> > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > >
> > > > > Quality of Experience (QoE):
> > > > > The overall acceptability of an application or service, as
> > > > perceived subjectively by the end-user.
> > > > > NOTE 1 - Quality of experience includes the complete
> > > > end-to-end system effects (client, terminal, network,
> > > > services infrastructure, etc.).
> > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > expectations and context.
> > > > >
> > > > > Important for MONARCH:
> > > > > 1st ... perceived by end-user
> > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > >
> > > > > That said, present RTP monitoring architecture in MONARCH
> > > > according clause 3 is not specific on the type of monitoring
> > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > to a terminal/user equipment (UE). This would be an
> > > > end-to-end IP network scenario.
> > > > >
> > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > be also located at the edge of an IP network, e.g. in a
> > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > the non-IP network part.
> > > > > Note: such scenarios are considered by MEGACO gateways
> > > > (I've Cc'd megaco list).
> > > > >
> > > > > An RTP Sender/Receiver located NOT in the UE would question
> > > > the value of RTP/RTCP QoE related performance measurements
> > > > (because the UE is located outside the RTP domain).
> > > > >
> > > > > Conclusions:
> > > > > - the set of meaningful performance metrics may be
> > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > whether in a UE, gateway, ...
> > > > > - don't see any impact on transport level metrics
> > > > > - ... but the set of meaningful application level metrics
> > > > >
> > > > > Proposal for MONARCH:
> > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > architecture" below clause 3
> > > > >
> > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > >
> > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > The location of the RTP Sender/Receiver entity may impact
> > > > the set of meaningful metrics.
> > > > > For instance: application level metrics for QoE related
> > > > performance metrics are questionable (or doesn't really make
> > > > sense at all) when measured in a network node (terminating
> > > > the RTP) instead of the user equipment."
> > > > >
> > > > > Something like this would help to avoid confusion.
> > > > > I even believe that a QoE measurement in a network node
> > > > would violate the QoE definition. Would be rather something
> > > > like QoE* ("remote QoE"):-(
> > > > >
> > > > > Such information would improve the MONARCH doc in my opinion.
> > > > > Sorry for that late comment.
> > > > > Any views?
> > > >
> > > > [Qin]:
> > > > Albrrecht, if you follow ealry list discussion on
> > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > to position this document was
> > > > this daft should focus on guidelines for defining reporting
> > > > blocks. That is to say the main purpose of MONARCH draft
> > is how to
> > > > provide guidelines for the development of new RTCP XR block
> > > > types in XRBlock working group.
> > >
> > > [ABS] ... then the title "monitoring architectures" is misleading.
> > > Proposal: keep title, revise scope section on focus
> > >
> > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > not expand scope into IP monitoring architecture.
> >
> > [ABS] That's wasn't the intent! Did just focus on the key word.
> >
> > >
> > > >
> > > > Therefore how and where to collect the metric from RTP
> > > > endpoint is not scope of this document, in my opinion. since
> > > > you may have many ways to do this and different vendors have
> > > > their different appoaches. It will be better to leave this
> > > > beyond the scope. But you are right, it will be more
> > > > reasonable to measure QoE related performance metric at the
> > > > RTP receiver.
> > >
> > > [ABS] I would disagree. At least your statement should be
> > > conditional, sth like
> > > "QoE related performance metrics may be measured in a RTP
> > > receiver, IF the RTP receiver function is located in user
> > > equipment (e.g. IP terminal), because QoE performance metrics
> > > are tightly coupled to the point of view of a 'user'.
> > > ... IF NOT, then ..."
> > >
> > > [Qin]: I am not sure user equipment or IP terminal is the
> > > right term from RTP perspective.
> > >
> > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > related metric can be placed either at the network or at
> the client.
> > > So I disagree with what you said.
> >
> > [ABS] Not convinced at all.
> > Guess you are referring to the "mid-point" models, right?
> > The usage of such that models depends on "prior knowledge
> > ..." information.
> > Thus, the applicability is conditional. You may not make such
> > a general statement.
> >
> >
> > >
> > > Also as I said, how and where to collect the metric from RTP
> > >  endpoint is not scope of this document. It depends on the
> > > model you are choosing, e.g., four operation modes specified
> > > in P.NAMS.
> > > Apparently this should not be specified again in RTP
> > > monitoring architecture document.
> > >
> > > >
> > > > Another point is it is not clear to me how RTP monitoring has
> > > > to do with architectureend to end IP network architecture .
> > > > this draft mostly focus on discussing RTP level stuff.
> > > > Therefore I am quite doubt that we should describe anything
> > > > in this document like how
> > > > RTP entties is mapped into network entities/nodes at
> the IP layer.
> > >
> > > [ABS] I don't got any problems to talk about architectural
> > > framework for monitoring in this document. Such information
> > > is required and this is the only IETF AVT doc about it.
> > > The solution to this issue is rather simple to me:
> > > - split the MONARCH "monitoring architecture" in
> > > 1) a functional monitoring architecture (let's call it 'FMA') and
> > > 2) a physical monitoring architecture (... 'PMA').
> > >
> > > - the present MONARCH doc would describe the FMA at the level
> > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > topology components according RFC 5117)
> > >
> > > - there are many options of functional-to-physical mappings,
> > > i.e. how a FMA would be mapped on a PMA
> > > - the mapping is typically dependent on considered network
> > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> > >
> > > - the present MONARCH doc would describe the FMA-to-PMA
> > > mapping IF all RTP receiver/sender entities would be located
> > > in physical IP terminals (UEs)
> > > - etc
> > >
> > > [Qin]: I can understand your point, but you can not do that.
> > > Since this document is only focus on *RTP* monitoring
> > > architecture, that is what it said in AVTCore milestone:
> > > "
> > >
> > > Goals and Milestones:
> > >
> > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > Informational
> > >
> > > "
> >
> > [ABS] If you go back to my first email on this subject, and
> > if you look at my proposal: that's not a lot, nothing which
> > violates the charter, goals and milestones.
> >
> >
> > > Also if you really don't see how to map FMA to PMA, you may
> > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > As for how to use RTP monitoring architecture or RTP XR
> > > Report in the IMS network architecture, you may look at:
> > > http://tools.ietf.org/html/rfc6035
> >
> > [ABS] That's the SIP reporting interface, i.e., applicable
> > primarily for physical IP user equipment with embedded RTP
> > sender/receiver function and SIP UA function.
> > However, the applicability of RFC 6035 is limited for a
> > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > located NOT in user equipment. Also the P.NAMS mid-point
> > model fails for such a scenario.
> >
> > > ITU-T H.248.48.
> > > But I haven't check the current status of H.248.48.
> >
> > [ABS] Work is finalized, see
> > http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> > 11121-TD-PLEN-0419
> >
> > >
> > > >
> > > > But as the author of this document, I am interested and open
> > > > to other opinions.:-)
> > >
> > > [ABS] Like to add a further aspect: a "functional monitoring
> > > architecture" may be considered as a network overlay,
> > > something which adds additional capabilities (here:
> > > measurement services, reporting services on top of basic RTP
> > > services).
> > > Such an overlay concept is nothing new: e.g., the
> > > MultiService Forum did define a "Performance Measurement &
> > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > considered as such.
> > >
> > > >
> > > > > Regards,
> > > > > Albrecht
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > >> Behalf Of internet-drafts@ietf.org
> > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > >> To: i-d-announce@ietf.org
> > > > >> Cc: avt@ietf.org
> > > > >> Subject: [AVTCORE] I-D Action:
> > draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >>
> > > > >> A New Internet-Draft is available from the on-line
> > > > >> Internet-Drafts directories. This draft is a work item of the
> > > > >> Audio/Video Transport Core Maintenance Working Group
> > of the IETF.
> > > > >>
> > > > >> Title           : Monitoring Architectures for RTP
> > > > >> Author(s)       : Qin Wu
> > > > >>                           Geoff Hunt
> > > > >>                           Philip Arden
> > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > >> Pages           : 25
> > > > >> Date            : 2011-11-28
> > > > >>
> > > > >>    This memo proposes an architecture for extending RTCP with
> > > > >> a new RTCP
> > > > >>    XR (RFC3611) block type to report new metrics
> > regarding media
> > > > >>    transmission or reception quality, following RTCP
> guideline
> > > > >>    established in RFC5968.  This memo suggests that a new
> > > > block should
> > > > >>    contain a single metric or a small number of metrics
> > > > relevant to a
> > > > >>    single parameter of interest or concern, rather than
> > > > containing a
> > > > >>    number of metrics which attempt to provide full coverage
> > > > >> of all those
> > > > >>    parameters of concern to a specific application.
> > > > Applications may
> > > > >>    then "mix and match" to create a set of blocks which
> > > > >> covers their set
> > > > >>    of concerns.  Where possible, a specific block should be
> > > > >> designed to
> > > > >>    be re-usable across more than one application, for
> > > > example, for all
> > > > >>    of voice, streaming audio and video.
> > > > >>
> > > > >>
> > > > >> A URL for this Internet-Draft is:
> > > > >>
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > >>
> > > > >> This Internet-Draft can be retrieved at:
> > > > >>
> > > >
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >> _______________________________________________
> > > > >> Audio/Video Transport Core Maintenance
> > > > >> avt@ietf.org
> > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > >>
> > > > > _______________________________________________
> > > > > Audio/Video Transport Core Maintenance
> > > > > avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > > =3D
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >
>

From singer@apple.com  Wed Dec  7 09:29:28 2011
Return-Path: <singer@apple.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF0321F85CE; Wed,  7 Dec 2011 09:29:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9mihU3M89XP; Wed,  7 Dec 2011 09:29:27 -0800 (PST)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 047EA21F8BB1; Wed,  7 Dec 2011 09:29:22 -0800 (PST)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_CtRC7gm2oU3HeqUBm5UV3A)"
Received: from relay17.apple.com ([17.128.113.18]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LVU002JJGKBECE0@mail-out.apple.com>; Wed, 07 Dec 2011 09:29:20 -0800 (PST)
X-AuditID: 11807112-b7b54ae000001626-1a-4edfa270b729
Received: from singda.apple.com (singda.apple.com [17.197.32.11]) by relay17.apple.com (Apple SCV relay) with SMTP id D0.06.05670.072AFDE4; Wed, 07 Dec 2011 09:29:20 -0800 (PST)
From: David Singer <singer@apple.com>
In-reply-to: <CB04CF88.350EA%stewe@stewe.org>
Date: Wed, 07 Dec 2011 09:29:20 -0800
Message-id: <A8C5088D-DBF6-46E4-B932-C8D357697C62@apple.com>
References: <CB04CF88.350EA%stewe@stewe.org>
To: Stephan Wenger <stewe@stewe.org>
X-Mailer: Apple Mail (2.1251.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUieFSBW7dg0X0/g+Z7qhYve1ayW3y8d4PV YuryxywWly6eZbK43riJ3WLKhUcsDmweS5b8ZPJYvP49YwBTFJdNSmpOZllqkb5dAlfG/O2l Bat8Kv5Mns/YwLjIoYuRk0NCwETiyIYFbBC2mMSFe+uBbC4OIYHNjBJfOv+CJYQFbCUeNPxl BLF5BYwl1tx6xwJiMwskSLx4cwjMZhNQlXgw5xhYDaeArsTsA8/BbBYBFYmTB7qYIerjJN7e WskGMcdG4vDUPWC2kICOxOKD+1lBbBGg+kM3f7BAHCQv0fL1DtsERr5ZSFbPQrIawtaWWLbw NfMsRg4gW0di8kJGVGEI++P5I0wLGNlWMQoWpeYkVhqa6yUWFOSk6iXn525iBIVyQ6HQDsb7 u/QOMQpwMCrx8G5wuOcnxJpYVlyZe4hRgoNZSYT3y6z7fkK8KYmVValF+fFFpTmpxYcYpTlY lMR5j2y77ickkJ5YkpqdmlqQWgSTZeLglGpg9E0tV7C3zCux2+fy4H9ibt6Xp6oV56ImPV7O zBG15q9QXsfN+24Mbzv63a5XqauyZs1MDgjbzpO1QiGvKfX6qpklu4pjNhcWX3H5Z3h58TJW bsnX/rmT5xSxLXKca5u1+uMDO8sNGctDr7bo+1x8dMTbQeb1wtsrnqbGrvK14nHqNXPcLn9X iaU4I9FQi7moOBEAaZVXV2ECAAA=
Cc: avtext@ietf.org, xrblock@ietf.org, mmusic@ietf.org, payload@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] Incoming liaison statement from MMUSIC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 17:29:28 -0000

--Boundary_(ID_CtRC7gm2oU3HeqUBm5UV3A)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Hi Stephan

I can explain a bit.  We noticed in systems work at MPEG two things
a) we wanted to say something about the signal that was being compressed (audio or video) that was nothing to do with the compression, and we ended up having to 'pick' a codec document and point at it, because the codes we wanted were always documented with codecs.
b) the codes are also copied from spec. to spec. in many cases (so they happen to have values having the same meanings); in a few cases, each codec has 'invented its own' and the codes needlessly differ from spec. to spec.

Examples: the 'classic three' values used to describe video color: color_primaries, transfer_characteristics, matrix_coefficients.  These are copied from spec. to spec., with the more recent specs having more values. Recently there was a mistake noticed in an equation, and I think it had to be corrected in several places.  Another example is 'frame packing' (stereo packed into a mono video stream); the specs actually don't always align on the definitions here.

The variation of semantics for some points could be a problem; different values for the same semantics is a nuisance, e.g. when wanting to be codec-independent or when transcoding. Different numbers of values for the same code in different specs is a nuisance, and raises questions, and so on.

The basic idea is to collect a whole bunch of these, document them in one place, and remove the definitions from a whole bunch of specs.  So, for example, in a video spec. one might be able to say "this 8-bit field carries a color_primaries value as defined in [[this new spec]]; if absent, the default value is 23".  Correspondingly, in say SDP, one might be able to say "if this field is 0, the video is mono; otherwise, it carries a frame_packing values as defined in [[this new spec]]".

Makes sense?


On Dec 7, 2011, at 8:08 , Stephan Wenger wrote:

> Hi all,
> mmusic has received an incoming liaison from MPEG, indicating that they have started on "codec independent media description code points".  My understanding of this work is that these code points may be represented in SDP.
> My personal viewpoint is that this may well be sound architectural work, but it may be better conducted here in mmusic, at least when it comes to SDP representations and the related IANA work.  However, I know nothing about this work beyond what's written in the statement, which is why I used "soft" language.  Perhaps some of you can shed light into what's really going on.
> The assorted avt WGs are probably also affected, as some of the proposed code points sound like they are being described in payload formats, RTP extensions and perhaps even in xrblock.  Let me suggest to use only the music list for discussions, as only mmusic is being addressed in the statement.
> As it is short, I have attached the statement in word format to this email.  It will also appear shortly in the IETF liaison database.
> Regards,
> Stephan
> <29n124561.doc>_______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

David Singer
Multimedia and Software Standards, Apple Inc.


--Boundary_(ID_CtRC7gm2oU3HeqUBm5UV3A)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Stephan<div><br></div><div>I can explain a bit. &nbsp;We noticed in =
systems work at MPEG two things</div><div>a) we wanted to say something =
about the signal that was being compressed (audio or video) that was =
nothing to do with the compression, and we ended up having to 'pick' a =
codec document and point at it, because the codes we wanted were always =
documented with codecs.</div><div>b) the codes are also copied from =
spec. to spec. in many cases (so they happen to have values having the =
same meanings); in a few cases, each codec has 'invented its own' and =
the codes needlessly differ from spec. to =
spec.</div><div><br></div><div>Examples: the 'classic three' values used =
to describe video color: color_primaries, transfer_characteristics, =
matrix_coefficients. &nbsp;These are copied from spec. to spec., with =
the more recent specs having more values. Recently there was a mistake =
noticed in an equation, and I think it had to be corrected in several =
places. &nbsp;Another example is 'frame packing' (stereo packed into a =
mono video stream); the specs actually don't always align on the =
definitions here.</div><div><br></div><div>The variation of semantics =
for some points could be a problem; different values for the same =
semantics is a nuisance, e.g. when wanting to be codec-independent or =
when transcoding. Different numbers of values for the same code in =
different specs is a nuisance, and raises questions, and so =
on.</div><div><br></div><div>The basic idea is to collect a whole bunch =
of these, document them in one place, and remove the definitions from a =
whole bunch of specs. &nbsp;So, for example, in a video spec. one might =
be able to say "this 8-bit field carries a color_primaries value as =
defined in [[this new spec]]; if absent, the default value is 23". =
&nbsp;Correspondingly, in say SDP, one might be able to say "if this =
field is 0, the video is mono; otherwise, it carries a frame_packing =
values as defined in [[this new spec]]".</div><div><br></div><div>Makes =
sense?</div><div><br></div><div><br><div><div>On Dec 7, 2011, at 8:08 , =
Stephan Wenger wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: =
14px; font-family: Calibri, sans-serif; "><div>Hi all,</div><div>mmusic =
has received an incoming liaison from MPEG, indicating that they have =
started on "codec independent media description code points". &nbsp;My =
understanding of this work is that these code points may be represented =
in SDP.</div><div>My personal viewpoint is that this may well be sound =
architectural work, but it may be better conducted here in mmusic, at =
least when it comes to SDP representations and the related IANA work. =
&nbsp;However,&nbsp;I know nothing about this work beyond what's written =
in the statement, which is why I used "soft" language. &nbsp;Perhaps =
some of you can shed light into what's really going on.</div><div>The =
assorted avt WGs are probably also affected, as some of the proposed =
code points sound like they are being described in payload formats, RTP =
extensions and perhaps even in xrblock. &nbsp;Let me suggest to use only =
the music list for discussions, as only mmusic is being addressed in the =
statement.</div><div>As it is short, I have attached the statement in =
word format to this email. &nbsp;It will also appear shortly in the IETF =
liaison database.</div><div>Regards,</div><div>Stephan</div></div>
=
<span>&lt;29n124561.doc&gt;</span>________________________________________=
_______<br>Audio/Video Transport Core Maintenance<br><a =
href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>https://www.ietf.org/mail=
man/listinfo/avt<br></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div>David Singer</div><div>Multimedia and =
Software Standards, Apple =
Inc.</div></div></div></span></div></span></span>
</div>
<br></div></body></html>=

--Boundary_(ID_CtRC7gm2oU3HeqUBm5UV3A)--

From bill.wu@huawei.com  Wed Dec  7 18:27:46 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6909811E8099; Wed,  7 Dec 2011 18:27:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.08
X-Spam-Level: 
X-Spam-Status: No, score=-6.08 tagged_above=-999 required=5 tests=[AWL=-0.081,  BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6M-rCTwlbIpp; Wed,  7 Dec 2011 18:27:44 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0907C11E80B4; Wed,  7 Dec 2011 18:27:44 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVV00EXG5FCZJ@szxga03-in.huawei.com>; Thu, 08 Dec 2011 10:26:00 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVV00BK25FCZ0@szxga03-in.huawei.com>; Thu, 08 Dec 2011 10:26:00 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFQ35216; Thu, 08 Dec 2011 10:26:00 +0800
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 08 Dec 2011 10:25:54 +0800
Received: from w53375q (10.138.41.130) by szxeml408-hub.china.huawei.com (10.82.67.95) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 08 Dec 2011 10:25:55 +0800
Date: Thu, 08 Dec 2011 10:25:54 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <71112008FBA94D35B07FA6B4916075B6@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 02:27:46 -0000

You reiterate what you propose for physical entities in the early email.
I am still not convicing with that.

Since we have RTP components like RTP end system, RTP mixer, RTP media translator, RTP transport translator,
RTP monitor specified in RFC3550 can be built into these component as a application. also monitor can be disjointed 
from these RTP components as a third party monitor. why we need to specify how to map RTP end system into user equipment,
RTP translator or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP border gateway since we have already mapped monitor
into different RTP components. 
How many PE types you can enumerate? why they should be scope of RTP monitoring architecture?

Also as specified in MONARCH draft, we have end sytem metrics, transport level metric, transport level metric, they can be measured and collected from the different RTP
comoponents specified in RFC3550, RFC5117. Apparently end system metric can only be collected from RTP end system.
transport metric is collected from any RTP system in the RTP monitoring architecture, 
regarding application level metric, apparently they should be measured at the application layer and can not be collected from RTP transport translator, Also RTP transport translator is still 
a functional entity rather than a physical entity. I am not convincing with what you said about "contradiction", "lead to possible wrong expectations".

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Thursday, December 08, 2011 12:24 AM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


Qin,
that's NOT the point.

All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL ENTITIES (FE).
e.g.,
- the RTP Monitor or RTP receiver FE may be located in different PHYSICAL ENTITIES (PE), e.g.
        a1) a user equipment
        a2) a RTP-to-PSTN gateway
        a3) an IP-to-IP session border gateway (in a back-to-back RTP endsystem topology)
        a3) ...

- the RTP Monitor may be associated to an RTP transport translator ...
        b1) an IP-to-IP session border gateway

The "RTP monitoring architecture" is IMPACTED by each functional-to-physical mapping because e.g.
* QoE related metrics are questionable in case of a2 ("despite the fact of a RTP receiver function")
* application level metrics at the location of a RTP transport translator are a contradiction in itself
* ...

Again, it's not really changing the MONARCH draft because in the very majority of scenarios it is correct. However, there are few cases where the MONARCH description would be "too high level", "not fully correct", "lead to possible wrong expectations", ...

Regards,
Albrecht



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Dienstag, 6. Dezember 2011 07:13
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> If you talk about existing RFC5117 RTP topology components,
> this has already been covered by the current version of
> draft-ietf-avtcore-monarch.
> In most cases, an RTP system using RTCP XR is architecturally
> no different from an RTP system which does not use RTCP XR.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Monday, December 05, 2011 10:48 PM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Hello Qin,
>
> to 1) Physical monitoring architecture
> Of course consideration of generic physical entities (PE),
> not specific to any network reference architectures defined
> by SDOs (like your refered entities).
> There would be just a few PE types ("given by the limited set
> of RTP topology components (RFC 5117)").
>
> to 2) (RFC 3550) Monitor function
> Right, that's a functional entity. The applicability of a
> monitor may be limited, dependent on ... (like in P.NAMS).
>
> to 3) your IMS network example
> Don't see the need to refer from MONARCH to a specific
> network architecture like IMS.
> Please also note that IMS is a functional architecture, not a
> physical architecture.
>
> Regards,
> Albrecht
>
> PS
> There are multiple options for adding the "RTP monitoring
> architecture" to a functional/physical network architecture:
> a) integrated approach: extension of existing functional
> entities or/and addition of RTP monitoring architectural
> components, extension or/and addition of
> signalling/management interfaces for control and
> configuration of RTP monitoring services, and reporting
> interfaces for measurement data ...
> b) overlay approach: separate specification to ...
>
>
> PSS
> BTW: there's a discussion paper with regards to the location
> of a monitor function in an IMS H.248 gateway entity:
> Measurements and statistics in IMS - Use Cases
> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> 8_Kyoto_Japan/Docs/C3-100469.zip
> This is just fyi.
>
>
>
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf Of Qin Wu
> > Sent: Freitag, 2. Dezember 2011 02:55
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi, Albrecht:
> > No offence, I am not really convinced with your proposal on
> > physical monitoring architecture.
> >  my counterquestion is what does physical monitoring
> > architecture looks like in your mind?
> > How many components do we have in such physical monitroing
> > architecture? what are they?
> > Take IMS network architecture as a example, they may have
> > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > described in draft-ietf-avtcore-monarch is mapped into
> > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > should be in the scope of IETF RTP monitoring archtiecture draft?
> >
> > Monitor described in  draft-ietf-avtcore-monarch is well
> > defined in the section 3 of RFC3550 as follows:
> > "
> >
> >    Monitor: An application that receives RTCP packets sent by
> >       participants in an RTP session, in particular the reception
> >       reports, and estimates the current quality of service for
> >       distribution monitoring, fault diagnosis and long-term
> > statistics.
> >       The monitor function is likely to be built into the
> > application(s)
> >       participating in the session, but may also be a separate
> >       application that does not otherwise participate and
> > does not send
> >       or receive the RTP data packets (since they are on a separate
> >       port).  These are called third-party monitors.  It is also
> >       acceptable for a third-party monitor to receive the RTP data
> >       packets but not send RTCP packets or otherwise be
> counted in the
> >       session.
> >
> > "
> > Isn't how to implent monitor into IMS netowork archtiecture a
> > implentation specific issue?
> > If this issue are really interesting, isn't it a good idea to
> > produce another new document to talk about this?
> > One good example for this motivation is this draft I like to
> > share with you:
> > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > y-00#section-4.6
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Friday, December 02, 2011 12:20 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > My replies below ...
> > -Albrecht
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi,
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Thursday, December 01, 2011 1:24 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > My replies below inline,
> > > Albrecht
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi,
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > > Dear All,
> > > > >
> > > > > there are different types of monitoring architectures,
> > > > particularily from perspective of QoE related performance
> > > parameters.
> > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > >
> > > > > Quality of Experience (QoE):
> > > > > The overall acceptability of an application or service, as
> > > > perceived subjectively by the end-user.
> > > > > NOTE 1 - Quality of experience includes the complete
> > > > end-to-end system effects (client, terminal, network,
> > > > services infrastructure, etc.).
> > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > expectations and context.
> > > > >
> > > > > Important for MONARCH:
> > > > > 1st ... perceived by end-user
> > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > >
> > > > > That said, present RTP monitoring architecture in MONARCH
> > > > according clause 3 is not specific on the type of monitoring
> > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > to a terminal/user equipment (UE). This would be an
> > > > end-to-end IP network scenario.
> > > > >
> > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > be also located at the edge of an IP network, e.g. in a
> > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > the non-IP network part.
> > > > > Note: such scenarios are considered by MEGACO gateways
> > > > (I've Cc'd megaco list).
> > > > >
> > > > > An RTP Sender/Receiver located NOT in the UE would question
> > > > the value of RTP/RTCP QoE related performance measurements
> > > > (because the UE is located outside the RTP domain).
> > > > >
> > > > > Conclusions:
> > > > > - the set of meaningful performance metrics may be
> > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > whether in a UE, gateway, ...
> > > > > - don't see any impact on transport level metrics
> > > > > - ... but the set of meaningful application level metrics
> > > > >
> > > > > Proposal for MONARCH:
> > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > architecture" below clause 3
> > > > >
> > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > >
> > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > The location of the RTP Sender/Receiver entity may impact
> > > > the set of meaningful metrics.
> > > > > For instance: application level metrics for QoE related
> > > > performance metrics are questionable (or doesn't really make
> > > > sense at all) when measured in a network node (terminating
> > > > the RTP) instead of the user equipment."
> > > > >
> > > > > Something like this would help to avoid confusion.
> > > > > I even believe that a QoE measurement in a network node
> > > > would violate the QoE definition. Would be rather something
> > > > like QoE* ("remote QoE"):-(
> > > > >
> > > > > Such information would improve the MONARCH doc in my opinion.
> > > > > Sorry for that late comment.
> > > > > Any views?
> > > >
> > > > [Qin]:
> > > > Albrrecht, if you follow ealry list discussion on
> > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > to position this document was
> > > > this daft should focus on guidelines for defining reporting
> > > > blocks. That is to say the main purpose of MONARCH draft
> > is how to
> > > > provide guidelines for the development of new RTCP XR block
> > > > types in XRBlock working group.
> > >
> > > [ABS] ... then the title "monitoring architectures" is misleading.
> > > Proposal: keep title, revise scope section on focus
> > >
> > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > not expand scope into IP monitoring architecture.
> >
> > [ABS] That's wasn't the intent! Did just focus on the key word.
> >
> > >
> > > >
> > > > Therefore how and where to collect the metric from RTP
> > > > endpoint is not scope of this document, in my opinion. since
> > > > you may have many ways to do this and different vendors have
> > > > their different appoaches. It will be better to leave this
> > > > beyond the scope. But you are right, it will be more
> > > > reasonable to measure QoE related performance metric at the
> > > > RTP receiver.
> > >
> > > [ABS] I would disagree. At least your statement should be
> > > conditional, sth like
> > > "QoE related performance metrics may be measured in a RTP
> > > receiver, IF the RTP receiver function is located in user
> > > equipment (e.g. IP terminal), because QoE performance metrics
> > > are tightly coupled to the point of view of a 'user'.
> > > ... IF NOT, then ..."
> > >
> > > [Qin]: I am not sure user equipment or IP terminal is the
> > > right term from RTP perspective.
> > >
> > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > related metric can be placed either at the network or at
> the client.
> > > So I disagree with what you said.
> >
> > [ABS] Not convinced at all.
> > Guess you are referring to the "mid-point" models, right?
> > The usage of such that models depends on "prior knowledge
> > ..." information.
> > Thus, the applicability is conditional. You may not make such
> > a general statement.
> >
> >
> > >
> > > Also as I said, how and where to collect the metric from RTP
> > >  endpoint is not scope of this document. It depends on the
> > > model you are choosing, e.g., four operation modes specified
> > > in P.NAMS.
> > > Apparently this should not be specified again in RTP
> > > monitoring architecture document.
> > >
> > > >
> > > > Another point is it is not clear to me how RTP monitoring has
> > > > to do with architectureend to end IP network architecture .
> > > > this draft mostly focus on discussing RTP level stuff.
> > > > Therefore I am quite doubt that we should describe anything
> > > > in this document like how
> > > > RTP entties is mapped into network entities/nodes at
> the IP layer.
> > >
> > > [ABS] I don't got any problems to talk about architectural
> > > framework for monitoring in this document. Such information
> > > is required and this is the only IETF AVT doc about it.
> > > The solution to this issue is rather simple to me:
> > > - split the MONARCH "monitoring architecture" in
> > > 1) a functional monitoring architecture (let's call it 'FMA') and
> > > 2) a physical monitoring architecture (... 'PMA').
> > >
> > > - the present MONARCH doc would describe the FMA at the level
> > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > topology components according RFC 5117)
> > >
> > > - there are many options of functional-to-physical mappings,
> > > i.e. how a FMA would be mapped on a PMA
> > > - the mapping is typically dependent on considered network
> > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> > >
> > > - the present MONARCH doc would describe the FMA-to-PMA
> > > mapping IF all RTP receiver/sender entities would be located
> > > in physical IP terminals (UEs)
> > > - etc
> > >
> > > [Qin]: I can understand your point, but you can not do that.
> > > Since this document is only focus on *RTP* monitoring
> > > architecture, that is what it said in AVTCore milestone:
> > > "
> > >
> > > Goals and Milestones:
> > >
> > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > Informational
> > >
> > > "
> >
> > [ABS] If you go back to my first email on this subject, and
> > if you look at my proposal: that's not a lot, nothing which
> > violates the charter, goals and milestones.
> >
> >
> > > Also if you really don't see how to map FMA to PMA, you may
> > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > As for how to use RTP monitoring architecture or RTP XR
> > > Report in the IMS network architecture, you may look at:
> > > http://tools.ietf.org/html/rfc6035
> >
> > [ABS] That's the SIP reporting interface, i.e., applicable
> > primarily for physical IP user equipment with embedded RTP
> > sender/receiver function and SIP UA function.
> > However, the applicability of RFC 6035 is limited for a
> > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > located NOT in user equipment. Also the P.NAMS mid-point
> > model fails for such a scenario.
> >
> > > ITU-T H.248.48.
> > > But I haven't check the current status of H.248.48.
> >
> > [ABS] Work is finalized, see
> > http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> > 11121-TD-PLEN-0419
> >
> > >
> > > >
> > > > But as the author of this document, I am interested and open
> > > > to other opinions.:-)
> > >
> > > [ABS] Like to add a further aspect: a "functional monitoring
> > > architecture" may be considered as a network overlay,
> > > something which adds additional capabilities (here:
> > > measurement services, reporting services on top of basic RTP
> > > services).
> > > Such an overlay concept is nothing new: e.g., the
> > > MultiService Forum did define a "Performance Measurement &
> > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > considered as such.
> > >
> > > >
> > > > > Regards,
> > > > > Albrecht
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > >> Behalf Of internet-drafts@ietf.org
> > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > >> To: i-d-announce@ietf.org
> > > > >> Cc: avt@ietf.org
> > > > >> Subject: [AVTCORE] I-D Action:
> > draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >>
> > > > >> A New Internet-Draft is available from the on-line
> > > > >> Internet-Drafts directories. This draft is a work item of the
> > > > >> Audio/Video Transport Core Maintenance Working Group
> > of the IETF.
> > > > >>
> > > > >> Title           : Monitoring Architectures for RTP
> > > > >> Author(s)       : Qin Wu
> > > > >>                           Geoff Hunt
> > > > >>                           Philip Arden
> > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > >> Pages           : 25
> > > > >> Date            : 2011-11-28
> > > > >>
> > > > >>    This memo proposes an architecture for extending RTCP with
> > > > >> a new RTCP
> > > > >>    XR (RFC3611) block type to report new metrics
> > regarding media
> > > > >>    transmission or reception quality, following RTCP
> guideline
> > > > >>    established in RFC5968.  This memo suggests that a new
> > > > block should
> > > > >>    contain a single metric or a small number of metrics
> > > > relevant to a
> > > > >>    single parameter of interest or concern, rather than
> > > > containing a
> > > > >>    number of metrics which attempt to provide full coverage
> > > > >> of all those
> > > > >>    parameters of concern to a specific application.
> > > > Applications may
> > > > >>    then "mix and match" to create a set of blocks which
> > > > >> covers their set
> > > > >>    of concerns.  Where possible, a specific block should be
> > > > >> designed to
> > > > >>    be re-usable across more than one application, for
> > > > example, for all
> > > > >>    of voice, streaming audio and video.
> > > > >>
> > > > >>
> > > > >> A URL for this Internet-Draft is:
> > > > >>
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > >>
> > > > >> This Internet-Draft can be retrieved at:
> > > > >>
> > > >
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >> _______________________________________________
> > > > >> Audio/Video Transport Core Maintenance
> > > > >> avt@ietf.org
> > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > >>
> > > > > _______________________________________________
> > > > > Audio/Video Transport Core Maintenance
> > > > > avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > > =
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >
>

From harald@alvestrand.no  Fri Dec  9 03:02:37 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B03421F861E for <avt@ietfa.amsl.com>; Fri,  9 Dec 2011 03:02:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.548
X-Spam-Level: 
X-Spam-Status: No, score=-109.548 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_TOWRITE=1.05, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id owRi5l4nyXlm for <avt@ietfa.amsl.com>; Fri,  9 Dec 2011 03:02:37 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id B649F21F85A1 for <avt@ietf.org>; Fri,  9 Dec 2011 03:02:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C580D39E123 for <avt@ietf.org>; Fri,  9 Dec 2011 12:02:35 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VkDHs767jS+J for <avt@ietf.org>; Fri,  9 Dec 2011 12:02:34 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id BE8AA39E0AF for <avt@ietf.org>; Fri,  9 Dec 2011 12:02:34 +0100 (CET)
Message-ID: <4EE1EACA.5070203@alvestrand.no>
Date: Fri, 09 Dec 2011 12:02:34 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: 'AVT Core WG' <avt@ietf.org>
Content-Type: multipart/alternative; boundary="------------030205080809010602010408"
Subject: [AVTCORE] A longer exposition of why I think the SDP top-level restriction is a Bad Idea
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 11:02:37 -0000

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

Hello all,

in order to get the multiplexing/top-level type discussions focused a 
little more - I decided to write up the argument I have been trying to 
make in a somewhat longer format.

The draft is 10 pages including all boilerplate; I hope it serves as an 
useful clarification of what I'm arguing for and why I'm arguing for it.

All comments welcome!

                      Harald

-------- Original Message --------
Subject: 	New Version Notification for 
draft-alvestrand-rtp-sess-neutral-00.txt
Date: 	Fri, 09 Dec 2011 03:00:27 -0800
From: 	internet-drafts@ietf.org
To: 	harald@alvestrand.no
CC: 	harald@alvestrand.no



A new version of I-D, draft-alvestrand-rtp-sess-neutral-00.txt has been successfully submitted by Harald Alvestrand and posted to the IETF repository.

Filename:	 draft-alvestrand-rtp-sess-neutral
Revision:	 00
Title:		 Why RTP Sessions Should Be Content Neutral
Creation date:	 2011-12-09
WG ID:		 Individual Submission
Number of pages: 10

Abstract:
    This document is not intended for publication as an RFC.

    It gives the underpinning arguments for why the idea that RTP
    sessions and MIME top level types are related is a deeply broken
    paradigm, and that we need to get away from it.

    These arguments are solely the opinion of the listed author.





The IETF Secretariat



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hello all,<br>
    <br>
    in order to get the multiplexing/top-level type discussions focused
    a little more - I decided to write up the argument I have been
    trying to make in a somewhat longer format.<br>
    <br>
    The draft is 10 pages including all boilerplate; I hope it serves as
    an useful clarification of what I'm arguing for and why I'm arguing
    for it.<br>
    <br>
    All comments welcome!<br>
    <br>
    Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Harald<br>
    <br>
    -------- Original Message --------
    <table class="moz-email-headers-table" border="0" cellpadding="0"
      cellspacing="0">
      <tbody>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th>
          <td>New Version Notification for
            draft-alvestrand-rtp-sess-neutral-00.txt</td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
          <td>Fri, 09 Dec 2011 03:00:27 -0800</td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
          <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
          <td><a class="moz-txt-link-abbreviated" href="mailto:harald@alvestrand.no">harald@alvestrand.no</a></td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
          <td><a class="moz-txt-link-abbreviated" href="mailto:harald@alvestrand.no">harald@alvestrand.no</a></td>
        </tr>
      </tbody>
    </table>
    <br>
    <br>
    <pre>A new version of I-D, draft-alvestrand-rtp-sess-neutral-00.txt has been successfully submitted by Harald Alvestrand and posted to the IETF repository.

Filename:	 draft-alvestrand-rtp-sess-neutral
Revision:	 00
Title:		 Why RTP Sessions Should Be Content Neutral
Creation date:	 2011-12-09
WG ID:		 Individual Submission
Number of pages: 10

Abstract:
   This document is not intended for publication as an RFC.

   It gives the underpinning arguments for why the idea that RTP
   sessions and MIME top level types are related is a deeply broken
   paradigm, and that we need to get away from it.

   These arguments are solely the opinion of the listed author.


                                                                                  


The IETF Secretariat

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

--------------030205080809010602010408--

From albrecht.schwarz@alcatel-lucent.com  Fri Dec  9 08:01:56 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E0C21F85FF; Fri,  9 Dec 2011 08:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.666
X-Spam-Level: 
X-Spam-Status: No, score=-5.666 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyn4gaUzR8V5; Fri,  9 Dec 2011 08:01:43 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 526BD21F853E; Fri,  9 Dec 2011 08:01:43 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB9G14Mi011957 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 9 Dec 2011 17:01:04 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Fri, 9 Dec 2011 17:01:01 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Fri, 9 Dec 2011 17:01:00 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acy1UPbzvzXcgax2QjiudJv83KCy2gBOijCg
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com>
In-Reply-To: <71112008FBA94D35B07FA6B4916075B6@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 16:01:56 -0000

How do you explain to a network operator the value of QoE measurements by a=
n RTP receiver / RTP monitor component located in an RTP-to-PSTN gateway?

This would be a monitoring scenario inline with MONARCH, but with valueless=
 QoE results, right?


> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Donnerstag, 8. Dezember 2011 03:26
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> You reiterate what you propose for physical entities in the
> early email.
> I am still not convicing with that.
>
> Since we have RTP components like RTP end system, RTP mixer,
> RTP media translator, RTP transport translator, RTP monitor
> specified in RFC3550 can be built into these component as a
> application. also monitor can be disjointed from these RTP
> components as a third party monitor. why we need to specify
> how to map RTP end system into user equipment, RTP translator
> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> border gateway since we have already mapped monitor into
> different RTP components.
> How many PE types you can enumerate? why they should be scope
> of RTP monitoring architecture?
>
> Also as specified in MONARCH draft, we have end sytem
> metrics, transport level metric, transport level metric, they
> can be measured and collected from the different RTP
> comoponents specified in RFC3550, RFC5117. Apparently end
> system metric can only be collected from RTP end system.
> transport metric is collected from any RTP system in the RTP
> monitoring architecture, regarding application level metric,
> apparently they should be measured at the application layer
> and can not be collected from RTP transport translator, Also
> RTP transport translator is still a functional entity rather
> than a physical entity. I am not convincing with what you
> said about "contradiction", "lead to possible wrong expectations".
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Thursday, December 08, 2011 12:24 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Qin,
> that's NOT the point.
>
> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL ENTITIES (FE).
> e.g.,
> - the RTP Monitor or RTP receiver FE may be located in
> different PHYSICAL ENTITIES (PE), e.g.
>         a1) a user equipment
>         a2) a RTP-to-PSTN gateway
>         a3) an IP-to-IP session border gateway (in a
> back-to-back RTP endsystem topology)
>         a3) ...
>
> - the RTP Monitor may be associated to an RTP transport translator ...
>         b1) an IP-to-IP session border gateway
>
> The "RTP monitoring architecture" is IMPACTED by each
> functional-to-physical mapping because e.g.
> * QoE related metrics are questionable in case of a2
> ("despite the fact of a RTP receiver function")
> * application level metrics at the location of a RTP
> transport translator are a contradiction in itself
> * ...
>
> Again, it's not really changing the MONARCH draft because in
> the very majority of scenarios it is correct. However, there
> are few cases where the MONARCH description would be "too
> high level", "not fully correct", "lead to possible wrong
> expectations", ...
>
> Regards,
> Albrecht
>
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Dienstag, 6. Dezember 2011 07:13
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > If you talk about existing RFC5117 RTP topology components,
> > this has already been covered by the current version of
> > draft-ietf-avtcore-monarch.
> > In most cases, an RTP system using RTCP XR is architecturally
> > no different from an RTP system which does not use RTCP XR.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Monday, December 05, 2011 10:48 PM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > Hello Qin,
> >
> > to 1) Physical monitoring architecture
> > Of course consideration of generic physical entities (PE),
> > not specific to any network reference architectures defined
> > by SDOs (like your refered entities).
> > There would be just a few PE types ("given by the limited set
> > of RTP topology components (RFC 5117)").
> >
> > to 2) (RFC 3550) Monitor function
> > Right, that's a functional entity. The applicability of a
> > monitor may be limited, dependent on ... (like in P.NAMS).
> >
> > to 3) your IMS network example
> > Don't see the need to refer from MONARCH to a specific
> > network architecture like IMS.
> > Please also note that IMS is a functional architecture, not a
> > physical architecture.
> >
> > Regards,
> > Albrecht
> >
> > PS
> > There are multiple options for adding the "RTP monitoring
> > architecture" to a functional/physical network architecture:
> > a) integrated approach: extension of existing functional
> > entities or/and addition of RTP monitoring architectural
> > components, extension or/and addition of
> > signalling/management interfaces for control and
> > configuration of RTP monitoring services, and reporting
> > interfaces for measurement data ...
> > b) overlay approach: separate specification to ...
> >
> >
> > PSS
> > BTW: there's a discussion paper with regards to the location
> > of a monitor function in an IMS H.248 gateway entity:
> > Measurements and statistics in IMS - Use Cases
> > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > 8_Kyoto_Japan/Docs/C3-100469.zip
> > This is just fyi.
> >
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > Behalf Of Qin Wu
> > > Sent: Freitag, 2. Dezember 2011 02:55
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi, Albrecht:
> > > No offence, I am not really convinced with your proposal on
> > > physical monitoring architecture.
> > >  my counterquestion is what does physical monitoring
> > > architecture looks like in your mind?
> > > How many components do we have in such physical monitroing
> > > architecture? what are they?
> > > Take IMS network architecture as a example, they may have
> > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > described in draft-ietf-avtcore-monarch is mapped into
> > > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > > should be in the scope of IETF RTP monitoring archtiecture draft?
> > >
> > > Monitor described in  draft-ietf-avtcore-monarch is well
> > > defined in the section 3 of RFC3550 as follows:
> > > "
> > >
> > >    Monitor: An application that receives RTCP packets sent by
> > >       participants in an RTP session, in particular the reception
> > >       reports, and estimates the current quality of service for
> > >       distribution monitoring, fault diagnosis and long-term
> > > statistics.
> > >       The monitor function is likely to be built into the
> > > application(s)
> > >       participating in the session, but may also be a separate
> > >       application that does not otherwise participate and
> > > does not send
> > >       or receive the RTP data packets (since they are on
> a separate
> > >       port).  These are called third-party monitors.  It is also
> > >       acceptable for a third-party monitor to receive the RTP data
> > >       packets but not send RTCP packets or otherwise be
> > counted in the
> > >       session.
> > >
> > > "
> > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > implentation specific issue?
> > > If this issue are really interesting, isn't it a good idea to
> > > produce another new document to talk about this?
> > > One good example for this motivation is this draft I like to
> > > share with you:
> > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > y-00#section-4.6
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Friday, December 02, 2011 12:20 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > My replies below ...
> > > -Albrecht
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi,
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > My replies below inline,
> > > > Albrecht
> > > >
> > > > > -----Original Message-----
> > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi,
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > > Dear All,
> > > > > >
> > > > > > there are different types of monitoring architectures,
> > > > > particularily from perspective of QoE related performance
> > > > parameters.
> > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > >
> > > > > > Quality of Experience (QoE):
> > > > > > The overall acceptability of an application or service, as
> > > > > perceived subjectively by the end-user.
> > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > end-to-end system effects (client, terminal, network,
> > > > > services infrastructure, etc.).
> > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > expectations and context.
> > > > > >
> > > > > > Important for MONARCH:
> > > > > > 1st ... perceived by end-user
> > > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > > >
> > > > > > That said, present RTP monitoring architecture in MONARCH
> > > > > according clause 3 is not specific on the type of monitoring
> > > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > > to a terminal/user equipment (UE). This would be an
> > > > > end-to-end IP network scenario.
> > > > > >
> > > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > > be also located at the edge of an IP network, e.g. in a
> > > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > > the non-IP network part.
> > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > (I've Cc'd megaco list).
> > > > > >
> > > > > > An RTP Sender/Receiver located NOT in the UE would question
> > > > > the value of RTP/RTCP QoE related performance measurements
> > > > > (because the UE is located outside the RTP domain).
> > > > > >
> > > > > > Conclusions:
> > > > > > - the set of meaningful performance metrics may be
> > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > whether in a UE, gateway, ...
> > > > > > - don't see any impact on transport level metrics
> > > > > > - ... but the set of meaningful application level metrics
> > > > > >
> > > > > > Proposal for MONARCH:
> > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > architecture" below clause 3
> > > > > >
> > > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > > >
> > > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > > The location of the RTP Sender/Receiver entity may impact
> > > > > the set of meaningful metrics.
> > > > > > For instance: application level metrics for QoE related
> > > > > performance metrics are questionable (or doesn't really make
> > > > > sense at all) when measured in a network node (terminating
> > > > > the RTP) instead of the user equipment."
> > > > > >
> > > > > > Something like this would help to avoid confusion.
> > > > > > I even believe that a QoE measurement in a network node
> > > > > would violate the QoE definition. Would be rather something
> > > > > like QoE* ("remote QoE"):-(
> > > > > >
> > > > > > Such information would improve the MONARCH doc in
> my opinion.
> > > > > > Sorry for that late comment.
> > > > > > Any views?
> > > > >
> > > > > [Qin]:
> > > > > Albrrecht, if you follow ealry list discussion on
> > > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > > to position this document was
> > > > > this daft should focus on guidelines for defining reporting
> > > > > blocks. That is to say the main purpose of MONARCH draft
> > > is how to
> > > > > provide guidelines for the development of new RTCP XR block
> > > > > types in XRBlock working group.
> > > >
> > > > [ABS] ... then the title "monitoring architectures" is
> misleading.
> > > > Proposal: keep title, revise scope section on focus
> > > >
> > > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > > not expand scope into IP monitoring architecture.
> > >
> > > [ABS] That's wasn't the intent! Did just focus on the key word.
> > >
> > > >
> > > > >
> > > > > Therefore how and where to collect the metric from RTP
> > > > > endpoint is not scope of this document, in my opinion. since
> > > > > you may have many ways to do this and different vendors have
> > > > > their different appoaches. It will be better to leave this
> > > > > beyond the scope. But you are right, it will be more
> > > > > reasonable to measure QoE related performance metric at the
> > > > > RTP receiver.
> > > >
> > > > [ABS] I would disagree. At least your statement should be
> > > > conditional, sth like
> > > > "QoE related performance metrics may be measured in a RTP
> > > > receiver, IF the RTP receiver function is located in user
> > > > equipment (e.g. IP terminal), because QoE performance metrics
> > > > are tightly coupled to the point of view of a 'user'.
> > > > ... IF NOT, then ..."
> > > >
> > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > right term from RTP perspective.
> > > >
> > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > related metric can be placed either at the network or at
> > the client.
> > > > So I disagree with what you said.
> > >
> > > [ABS] Not convinced at all.
> > > Guess you are referring to the "mid-point" models, right?
> > > The usage of such that models depends on "prior knowledge
> > > ..." information.
> > > Thus, the applicability is conditional. You may not make such
> > > a general statement.
> > >
> > >
> > > >
> > > > Also as I said, how and where to collect the metric from RTP
> > > >  endpoint is not scope of this document. It depends on the
> > > > model you are choosing, e.g., four operation modes specified
> > > > in P.NAMS.
> > > > Apparently this should not be specified again in RTP
> > > > monitoring architecture document.
> > > >
> > > > >
> > > > > Another point is it is not clear to me how RTP monitoring has
> > > > > to do with architectureend to end IP network architecture .
> > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > Therefore I am quite doubt that we should describe anything
> > > > > in this document like how
> > > > > RTP entties is mapped into network entities/nodes at
> > the IP layer.
> > > >
> > > > [ABS] I don't got any problems to talk about architectural
> > > > framework for monitoring in this document. Such information
> > > > is required and this is the only IETF AVT doc about it.
> > > > The solution to this issue is rather simple to me:
> > > > - split the MONARCH "monitoring architecture" in
> > > > 1) a functional monitoring architecture (let's call it
> 'FMA') and
> > > > 2) a physical monitoring architecture (... 'PMA').
> > > >
> > > > - the present MONARCH doc would describe the FMA at the level
> > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > topology components according RFC 5117)
> > > >
> > > > - there are many options of functional-to-physical mappings,
> > > > i.e. how a FMA would be mapped on a PMA
> > > > - the mapping is typically dependent on considered network
> > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> networks)
> > > >
> > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > mapping IF all RTP receiver/sender entities would be located
> > > > in physical IP terminals (UEs)
> > > > - etc
> > > >
> > > > [Qin]: I can understand your point, but you can not do that.
> > > > Since this document is only focus on *RTP* monitoring
> > > > architecture, that is what it said in AVTCore milestone:
> > > > "
> > > >
> > > > Goals and Milestones:
> > > >
> > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > Informational
> > > >
> > > > "
> > >
> > > [ABS] If you go back to my first email on this subject, and
> > > if you look at my proposal: that's not a lot, nothing which
> > > violates the charter, goals and milestones.
> > >
> > >
> > > > Also if you really don't see how to map FMA to PMA, you may
> > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > As for how to use RTP monitoring architecture or RTP XR
> > > > Report in the IMS network architecture, you may look at:
> > > > http://tools.ietf.org/html/rfc6035
> > >
> > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > primarily for physical IP user equipment with embedded RTP
> > > sender/receiver function and SIP UA function.
> > > However, the applicability of RFC 6035 is limited for a
> > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > located NOT in user equipment. Also the P.NAMS mid-point
> > > model fails for such a scenario.
> > >
> > > > ITU-T H.248.48.
> > > > But I haven't check the current status of H.248.48.
> > >
> > > [ABS] Work is finalized, see
> > > http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> > > 11121-TD-PLEN-0419
> > >
> > > >
> > > > >
> > > > > But as the author of this document, I am interested and open
> > > > > to other opinions.:-)
> > > >
> > > > [ABS] Like to add a further aspect: a "functional monitoring
> > > > architecture" may be considered as a network overlay,
> > > > something which adds additional capabilities (here:
> > > > measurement services, reporting services on top of basic RTP
> > > > services).
> > > > Such an overlay concept is nothing new: e.g., the
> > > > MultiService Forum did define a "Performance Measurement &
> > > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > > considered as such.
> > > >
> > > > >
> > > > > > Regards,
> > > > > > Albrecht
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > >> To: i-d-announce@ietf.org
> > > > > >> Cc: avt@ietf.org
> > > > > >> Subject: [AVTCORE] I-D Action:
> > > draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >>
> > > > > >> A New Internet-Draft is available from the on-line
> > > > > >> Internet-Drafts directories. This draft is a work
> item of the
> > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > of the IETF.
> > > > > >>
> > > > > >> Title           : Monitoring Architectures for RTP
> > > > > >> Author(s)       : Qin Wu
> > > > > >>                           Geoff Hunt
> > > > > >>                           Philip Arden
> > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > >> Pages           : 25
> > > > > >> Date            : 2011-11-28
> > > > > >>
> > > > > >>    This memo proposes an architecture for
> extending RTCP with
> > > > > >> a new RTCP
> > > > > >>    XR (RFC3611) block type to report new metrics
> > > regarding media
> > > > > >>    transmission or reception quality, following RTCP
> > guideline
> > > > > >>    established in RFC5968.  This memo suggests that a new
> > > > > block should
> > > > > >>    contain a single metric or a small number of metrics
> > > > > relevant to a
> > > > > >>    single parameter of interest or concern, rather than
> > > > > containing a
> > > > > >>    number of metrics which attempt to provide full coverage
> > > > > >> of all those
> > > > > >>    parameters of concern to a specific application.
> > > > > Applications may
> > > > > >>    then "mix and match" to create a set of blocks which
> > > > > >> covers their set
> > > > > >>    of concerns.  Where possible, a specific block should be
> > > > > >> designed to
> > > > > >>    be re-usable across more than one application, for
> > > > > example, for all
> > > > > >>    of voice, streaming audio and video.
> > > > > >>
> > > > > >>
> > > > > >> A URL for this Internet-Draft is:
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > >>
> > > > > >> This Internet-Draft can be retrieved at:
> > > > > >>
> > > > >
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >> _______________________________________________
> > > > > >> Audio/Video Transport Core Maintenance
> > > > > >> avt@ietf.org
> > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > >>
> > > > > > _______________________________________________
> > > > > > Audio/Video Transport Core Maintenance
> > > > > > avt@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > >
> > > > =3D
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > >
> >
>

From bill.wu@huawei.com  Sun Dec 11 20:06:31 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93CFC21F86B3; Sun, 11 Dec 2011 20:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.716
X-Spam-Level: 
X-Spam-Status: No, score=-5.716 tagged_above=-999 required=5 tests=[AWL=-0.317, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rwb6WCmJzFUS; Sun, 11 Dec 2011 20:06:29 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 2F07521F8672; Sun, 11 Dec 2011 20:06:29 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW200KRCONNCG@szxga05-in.huawei.com>; Mon, 12 Dec 2011 12:04:35 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW200KF5ONKL4@szxga05-in.huawei.com>; Mon, 12 Dec 2011 12:04:35 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFT71892; Mon, 12 Dec 2011 12:04:35 +0800
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 12 Dec 2011 12:04:34 +0800
Received: from w53375q (10.138.41.130) by szxeml412-hub.china.huawei.com (10.82.67.91) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 12 Dec 2011 12:04:32 +0800
Date: Mon, 12 Dec 2011 12:04:31 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 04:06:31 -0000

Hi, Albrecht:
My understanding to QoE measurment is:
The factors that influence the QoE metric include encoding system, transport network, access network,home network and end device.
If the customer(e.g., network operator) doesn't know the original content, the QoE metric should be usually measured at the user device.
If the customer knows the original content, the QoE metric can be measured either in the network or at the user device.
Given the growing popularity of connected devices, these devices may have different capability corresponding to CPU load, processing overhead, storage, batteries.
If the cusomer want to measure QoE without considering connected devices with various capability , the QoE metric can be measured at the point between
access network and home network.

Regarding the monitoring scenario you mentioned, I am not familiar with such scenario with RTP-to-PSTN gateway deployed.
But I am aware that there are scenarios with SIP to PSTN gateway or SIP to H.323 gateway widely deployed,  RFC6035 defines a new SIP event package, vq-rtcpxr
that enable the collection and  reporting of metrics that measure quality for RTP sessions. In such cases, RTCP XR VOIP metric with QoE metric included is measured  
at the user device and mapped into the equivalent SIP vq-rtcpxr parameter since SIP session call is established end to end and RTP media stream is exchanged directly between
one endpoint and the other endpoint.

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Saturday, December 10, 2011 12:01 AM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


How do you explain to a network operator the value of QoE measurements by an RTP receiver / RTP monitor component located in an RTP-to-PSTN gateway?

This would be a monitoring scenario inline with MONARCH, but with valueless QoE results, right?


> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Donnerstag, 8. Dezember 2011 03:26
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> You reiterate what you propose for physical entities in the
> early email.
> I am still not convicing with that.
>
> Since we have RTP components like RTP end system, RTP mixer,
> RTP media translator, RTP transport translator, RTP monitor
> specified in RFC3550 can be built into these component as a
> application. also monitor can be disjointed from these RTP
> components as a third party monitor. why we need to specify
> how to map RTP end system into user equipment, RTP translator
> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> border gateway since we have already mapped monitor into
> different RTP components.
> How many PE types you can enumerate? why they should be scope
> of RTP monitoring architecture?
>
> Also as specified in MONARCH draft, we have end sytem
> metrics, transport level metric, transport level metric, they
> can be measured and collected from the different RTP
> comoponents specified in RFC3550, RFC5117. Apparently end
> system metric can only be collected from RTP end system.
> transport metric is collected from any RTP system in the RTP
> monitoring architecture, regarding application level metric,
> apparently they should be measured at the application layer
> and can not be collected from RTP transport translator, Also
> RTP transport translator is still a functional entity rather
> than a physical entity. I am not convincing with what you
> said about "contradiction", "lead to possible wrong expectations".
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Thursday, December 08, 2011 12:24 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Qin,
> that's NOT the point.
>
> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL ENTITIES (FE).
> e.g.,
> - the RTP Monitor or RTP receiver FE may be located in
> different PHYSICAL ENTITIES (PE), e.g.
>         a1) a user equipment
>         a2) a RTP-to-PSTN gateway
>         a3) an IP-to-IP session border gateway (in a
> back-to-back RTP endsystem topology)
>         a3) ...
>
> - the RTP Monitor may be associated to an RTP transport translator ...
>         b1) an IP-to-IP session border gateway
>
> The "RTP monitoring architecture" is IMPACTED by each
> functional-to-physical mapping because e.g.
> * QoE related metrics are questionable in case of a2
> ("despite the fact of a RTP receiver function")
> * application level metrics at the location of a RTP
> transport translator are a contradiction in itself
> * ...
>
> Again, it's not really changing the MONARCH draft because in
> the very majority of scenarios it is correct. However, there
> are few cases where the MONARCH description would be "too
> high level", "not fully correct", "lead to possible wrong
> expectations", ...
>
> Regards,
> Albrecht
>
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Dienstag, 6. Dezember 2011 07:13
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > If you talk about existing RFC5117 RTP topology components,
> > this has already been covered by the current version of
> > draft-ietf-avtcore-monarch.
> > In most cases, an RTP system using RTCP XR is architecturally
> > no different from an RTP system which does not use RTCP XR.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Monday, December 05, 2011 10:48 PM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > Hello Qin,
> >
> > to 1) Physical monitoring architecture
> > Of course consideration of generic physical entities (PE),
> > not specific to any network reference architectures defined
> > by SDOs (like your refered entities).
> > There would be just a few PE types ("given by the limited set
> > of RTP topology components (RFC 5117)").
> >
> > to 2) (RFC 3550) Monitor function
> > Right, that's a functional entity. The applicability of a
> > monitor may be limited, dependent on ... (like in P.NAMS).
> >
> > to 3) your IMS network example
> > Don't see the need to refer from MONARCH to a specific
> > network architecture like IMS.
> > Please also note that IMS is a functional architecture, not a
> > physical architecture.
> >
> > Regards,
> > Albrecht
> >
> > PS
> > There are multiple options for adding the "RTP monitoring
> > architecture" to a functional/physical network architecture:
> > a) integrated approach: extension of existing functional
> > entities or/and addition of RTP monitoring architectural
> > components, extension or/and addition of
> > signalling/management interfaces for control and
> > configuration of RTP monitoring services, and reporting
> > interfaces for measurement data ...
> > b) overlay approach: separate specification to ...
> >
> >
> > PSS
> > BTW: there's a discussion paper with regards to the location
> > of a monitor function in an IMS H.248 gateway entity:
> > Measurements and statistics in IMS - Use Cases
> > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > 8_Kyoto_Japan/Docs/C3-100469.zip
> > This is just fyi.
> >
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > Behalf Of Qin Wu
> > > Sent: Freitag, 2. Dezember 2011 02:55
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi, Albrecht:
> > > No offence, I am not really convinced with your proposal on
> > > physical monitoring architecture.
> > >  my counterquestion is what does physical monitoring
> > > architecture looks like in your mind?
> > > How many components do we have in such physical monitroing
> > > architecture? what are they?
> > > Take IMS network architecture as a example, they may have
> > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > described in draft-ietf-avtcore-monarch is mapped into
> > > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > > should be in the scope of IETF RTP monitoring archtiecture draft?
> > >
> > > Monitor described in  draft-ietf-avtcore-monarch is well
> > > defined in the section 3 of RFC3550 as follows:
> > > "
> > >
> > >    Monitor: An application that receives RTCP packets sent by
> > >       participants in an RTP session, in particular the reception
> > >       reports, and estimates the current quality of service for
> > >       distribution monitoring, fault diagnosis and long-term
> > > statistics.
> > >       The monitor function is likely to be built into the
> > > application(s)
> > >       participating in the session, but may also be a separate
> > >       application that does not otherwise participate and
> > > does not send
> > >       or receive the RTP data packets (since they are on
> a separate
> > >       port).  These are called third-party monitors.  It is also
> > >       acceptable for a third-party monitor to receive the RTP data
> > >       packets but not send RTCP packets or otherwise be
> > counted in the
> > >       session.
> > >
> > > "
> > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > implentation specific issue?
> > > If this issue are really interesting, isn't it a good idea to
> > > produce another new document to talk about this?
> > > One good example for this motivation is this draft I like to
> > > share with you:
> > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > y-00#section-4.6
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Friday, December 02, 2011 12:20 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > My replies below ...
> > > -Albrecht
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi,
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > My replies below inline,
> > > > Albrecht
> > > >
> > > > > -----Original Message-----
> > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi,
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > > Dear All,
> > > > > >
> > > > > > there are different types of monitoring architectures,
> > > > > particularily from perspective of QoE related performance
> > > > parameters.
> > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > >
> > > > > > Quality of Experience (QoE):
> > > > > > The overall acceptability of an application or service, as
> > > > > perceived subjectively by the end-user.
> > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > end-to-end system effects (client, terminal, network,
> > > > > services infrastructure, etc.).
> > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > expectations and context.
> > > > > >
> > > > > > Important for MONARCH:
> > > > > > 1st ... perceived by end-user
> > > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > > >
> > > > > > That said, present RTP monitoring architecture in MONARCH
> > > > > according clause 3 is not specific on the type of monitoring
> > > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > > to a terminal/user equipment (UE). This would be an
> > > > > end-to-end IP network scenario.
> > > > > >
> > > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > > be also located at the edge of an IP network, e.g. in a
> > > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > > the non-IP network part.
> > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > (I've Cc'd megaco list).
> > > > > >
> > > > > > An RTP Sender/Receiver located NOT in the UE would question
> > > > > the value of RTP/RTCP QoE related performance measurements
> > > > > (because the UE is located outside the RTP domain).
> > > > > >
> > > > > > Conclusions:
> > > > > > - the set of meaningful performance metrics may be
> > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > whether in a UE, gateway, ...
> > > > > > - don't see any impact on transport level metrics
> > > > > > - ... but the set of meaningful application level metrics
> > > > > >
> > > > > > Proposal for MONARCH:
> > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > architecture" below clause 3
> > > > > >
> > > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > > >
> > > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > > The location of the RTP Sender/Receiver entity may impact
> > > > > the set of meaningful metrics.
> > > > > > For instance: application level metrics for QoE related
> > > > > performance metrics are questionable (or doesn't really make
> > > > > sense at all) when measured in a network node (terminating
> > > > > the RTP) instead of the user equipment."
> > > > > >
> > > > > > Something like this would help to avoid confusion.
> > > > > > I even believe that a QoE measurement in a network node
> > > > > would violate the QoE definition. Would be rather something
> > > > > like QoE* ("remote QoE"):-(
> > > > > >
> > > > > > Such information would improve the MONARCH doc in
> my opinion.
> > > > > > Sorry for that late comment.
> > > > > > Any views?
> > > > >
> > > > > [Qin]:
> > > > > Albrrecht, if you follow ealry list discussion on
> > > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > > to position this document was
> > > > > this daft should focus on guidelines for defining reporting
> > > > > blocks. That is to say the main purpose of MONARCH draft
> > > is how to
> > > > > provide guidelines for the development of new RTCP XR block
> > > > > types in XRBlock working group.
> > > >
> > > > [ABS] ... then the title "monitoring architectures" is
> misleading.
> > > > Proposal: keep title, revise scope section on focus
> > > >
> > > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > > not expand scope into IP monitoring architecture.
> > >
> > > [ABS] That's wasn't the intent! Did just focus on the key word.
> > >
> > > >
> > > > >
> > > > > Therefore how and where to collect the metric from RTP
> > > > > endpoint is not scope of this document, in my opinion. since
> > > > > you may have many ways to do this and different vendors have
> > > > > their different appoaches. It will be better to leave this
> > > > > beyond the scope. But you are right, it will be more
> > > > > reasonable to measure QoE related performance metric at the
> > > > > RTP receiver.
> > > >
> > > > [ABS] I would disagree. At least your statement should be
> > > > conditional, sth like
> > > > "QoE related performance metrics may be measured in a RTP
> > > > receiver, IF the RTP receiver function is located in user
> > > > equipment (e.g. IP terminal), because QoE performance metrics
> > > > are tightly coupled to the point of view of a 'user'.
> > > > ... IF NOT, then ..."
> > > >
> > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > right term from RTP perspective.
> > > >
> > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > related metric can be placed either at the network or at
> > the client.
> > > > So I disagree with what you said.
> > >
> > > [ABS] Not convinced at all.
> > > Guess you are referring to the "mid-point" models, right?
> > > The usage of such that models depends on "prior knowledge
> > > ..." information.
> > > Thus, the applicability is conditional. You may not make such
> > > a general statement.
> > >
> > >
> > > >
> > > > Also as I said, how and where to collect the metric from RTP
> > > >  endpoint is not scope of this document. It depends on the
> > > > model you are choosing, e.g., four operation modes specified
> > > > in P.NAMS.
> > > > Apparently this should not be specified again in RTP
> > > > monitoring architecture document.
> > > >
> > > > >
> > > > > Another point is it is not clear to me how RTP monitoring has
> > > > > to do with architectureend to end IP network architecture .
> > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > Therefore I am quite doubt that we should describe anything
> > > > > in this document like how
> > > > > RTP entties is mapped into network entities/nodes at
> > the IP layer.
> > > >
> > > > [ABS] I don't got any problems to talk about architectural
> > > > framework for monitoring in this document. Such information
> > > > is required and this is the only IETF AVT doc about it.
> > > > The solution to this issue is rather simple to me:
> > > > - split the MONARCH "monitoring architecture" in
> > > > 1) a functional monitoring architecture (let's call it
> 'FMA') and
> > > > 2) a physical monitoring architecture (... 'PMA').
> > > >
> > > > - the present MONARCH doc would describe the FMA at the level
> > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > topology components according RFC 5117)
> > > >
> > > > - there are many options of functional-to-physical mappings,
> > > > i.e. how a FMA would be mapped on a PMA
> > > > - the mapping is typically dependent on considered network
> > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> networks)
> > > >
> > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > mapping IF all RTP receiver/sender entities would be located
> > > > in physical IP terminals (UEs)
> > > > - etc
> > > >
> > > > [Qin]: I can understand your point, but you can not do that.
> > > > Since this document is only focus on *RTP* monitoring
> > > > architecture, that is what it said in AVTCore milestone:
> > > > "
> > > >
> > > > Goals and Milestones:
> > > >
> > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > Informational
> > > >
> > > > "
> > >
> > > [ABS] If you go back to my first email on this subject, and
> > > if you look at my proposal: that's not a lot, nothing which
> > > violates the charter, goals and milestones.
> > >
> > >
> > > > Also if you really don't see how to map FMA to PMA, you may
> > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > As for how to use RTP monitoring architecture or RTP XR
> > > > Report in the IMS network architecture, you may look at:
> > > > http://tools.ietf.org/html/rfc6035
> > >
> > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > primarily for physical IP user equipment with embedded RTP
> > > sender/receiver function and SIP UA function.
> > > However, the applicability of RFC 6035 is limited for a
> > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > located NOT in user equipment. Also the P.NAMS mid-point
> > > model fails for such a scenario.
> > >
> > > > ITU-T H.248.48.
> > > > But I haven't check the current status of H.248.48.
> > >
> > > [ABS] Work is finalized, see
> > > http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> > > 11121-TD-PLEN-0419
> > >
> > > >
> > > > >
> > > > > But as the author of this document, I am interested and open
> > > > > to other opinions.:-)
> > > >
> > > > [ABS] Like to add a further aspect: a "functional monitoring
> > > > architecture" may be considered as a network overlay,
> > > > something which adds additional capabilities (here:
> > > > measurement services, reporting services on top of basic RTP
> > > > services).
> > > > Such an overlay concept is nothing new: e.g., the
> > > > MultiService Forum did define a "Performance Measurement &
> > > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > > considered as such.
> > > >
> > > > >
> > > > > > Regards,
> > > > > > Albrecht
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > >> To: i-d-announce@ietf.org
> > > > > >> Cc: avt@ietf.org
> > > > > >> Subject: [AVTCORE] I-D Action:
> > > draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >>
> > > > > >> A New Internet-Draft is available from the on-line
> > > > > >> Internet-Drafts directories. This draft is a work
> item of the
> > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > of the IETF.
> > > > > >>
> > > > > >> Title           : Monitoring Architectures for RTP
> > > > > >> Author(s)       : Qin Wu
> > > > > >>                           Geoff Hunt
> > > > > >>                           Philip Arden
> > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > >> Pages           : 25
> > > > > >> Date            : 2011-11-28
> > > > > >>
> > > > > >>    This memo proposes an architecture for
> extending RTCP with
> > > > > >> a new RTCP
> > > > > >>    XR (RFC3611) block type to report new metrics
> > > regarding media
> > > > > >>    transmission or reception quality, following RTCP
> > guideline
> > > > > >>    established in RFC5968.  This memo suggests that a new
> > > > > block should
> > > > > >>    contain a single metric or a small number of metrics
> > > > > relevant to a
> > > > > >>    single parameter of interest or concern, rather than
> > > > > containing a
> > > > > >>    number of metrics which attempt to provide full coverage
> > > > > >> of all those
> > > > > >>    parameters of concern to a specific application.
> > > > > Applications may
> > > > > >>    then "mix and match" to create a set of blocks which
> > > > > >> covers their set
> > > > > >>    of concerns.  Where possible, a specific block should be
> > > > > >> designed to
> > > > > >>    be re-usable across more than one application, for
> > > > > example, for all
> > > > > >>    of voice, streaming audio and video.
> > > > > >>
> > > > > >>
> > > > > >> A URL for this Internet-Draft is:
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > >>
> > > > > >> This Internet-Draft can be retrieved at:
> > > > > >>
> > > > >
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >> _______________________________________________
> > > > > >> Audio/Video Transport Core Maintenance
> > > > > >> avt@ietf.org
> > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > >>
> > > > > > _______________________________________________
> > > > > > Audio/Video Transport Core Maintenance
> > > > > > avt@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > >
> > > > =
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > >
> >
>

From albrecht.schwarz@alcatel-lucent.com  Mon Dec 12 02:33:27 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 438D321F8A62; Mon, 12 Dec 2011 02:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.364
X-Spam-Level: 
X-Spam-Status: No, score=-5.364 tagged_above=-999 required=5 tests=[AWL=-0.315, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q72NSNBJa6Uv; Mon, 12 Dec 2011 02:33:25 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 6862921F8888; Mon, 12 Dec 2011 02:33:24 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pBCAX3Om022291 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 11:33:15 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Mon, 12 Dec 2011 11:33:09 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Mon, 12 Dec 2011 11:33:08 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acy4g3DuLm8Zu4LZQuq8wu6FtEozXgAM063A
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com>
In-Reply-To: <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 10:33:27 -0000

Hi Qin,

I'm very aware about all that.
It looks like that you are now agreeing that QoE measurements are CONDITION=
AL ("you got a number of IF statements, there might be even more ...").

MONARCH is not talking about such conditions, thus some readers may got the=
 impression that the metrics related to RTP traffic are UNCONDITIONAL (whic=
h is not true as you confirmed).

If you go back to my very first email: I did just propose to indicate the c=
onditional aspect. Don't understand why such kind of valuable info would be=
 not in scope of MONARCH. Hm?

Regards,
Albrecht

PS
I did use the notion of a control plane agnostic "RTP-to-PSTN gateway". You=
 did indicate control plane specific gateway types like SIP-to-PSTN or SIP-=
to-H.323. Now issue to use such signalling protocol specific examples, but =
it doesn't change the underlying issue.
The SIP side reporting capability based on RFC 6035 allows to report the ou=
tlined measurements, but the RFC itself does not specify whether the report=
ed information is meaningful (which is OK because this is not subject of a =
reporting interface spec, it is rather subject of a network monitoring doc =
like MONARCH).
QoE measurements would be conditional in both gateway types (because such a=
 gateway is NOT a user device despite the fact of an embedded SIP user agen=
t entity).
Actually I would even question here the condition of "customer knows the or=
iginal content" in many real network scenarios.



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Montag, 12. Dezember 2011 05:05
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Albrecht:
> My understanding to QoE measurment is:
> The factors that influence the QoE metric include encoding
> system, transport network, access network,home network and end device.
> If the customer(e.g., network operator) doesn't know the
> original content, the QoE metric should be usually measured
> at the user device.
> If the customer knows the original content, the QoE metric
> can be measured either in the network or at the user device.
> Given the growing popularity of connected devices, these
> devices may have different capability corresponding to CPU
> load, processing overhead, storage, batteries.
> If the cusomer want to measure QoE without considering
> connected devices with various capability , the QoE metric
> can be measured at the point between access network and home network.
>
> Regarding the monitoring scenario you mentioned, I am not
> familiar with such scenario with RTP-to-PSTN gateway deployed.
> But I am aware that there are scenarios with SIP to PSTN
> gateway or SIP to H.323 gateway widely deployed,  RFC6035
> defines a new SIP event package, vq-rtcpxr that enable the
> collection and  reporting of metrics that measure quality for
> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
> metric included is measured at the user device and mapped
> into the equivalent SIP vq-rtcpxr parameter since SIP session
> call is established end to end and RTP media stream is
> exchanged directly between one endpoint and the other endpoint.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Saturday, December 10, 2011 12:01 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> How do you explain to a network operator the value of QoE
> measurements by an RTP receiver / RTP monitor component
> located in an RTP-to-PSTN gateway?
>
> This would be a monitoring scenario inline with MONARCH, but
> with valueless QoE results, right?
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Donnerstag, 8. Dezember 2011 03:26
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > You reiterate what you propose for physical entities in the
> > early email.
> > I am still not convicing with that.
> >
> > Since we have RTP components like RTP end system, RTP mixer,
> > RTP media translator, RTP transport translator, RTP monitor
> > specified in RFC3550 can be built into these component as a
> > application. also monitor can be disjointed from these RTP
> > components as a third party monitor. why we need to specify
> > how to map RTP end system into user equipment, RTP translator
> > or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> > border gateway since we have already mapped monitor into
> > different RTP components.
> > How many PE types you can enumerate? why they should be scope
> > of RTP monitoring architecture?
> >
> > Also as specified in MONARCH draft, we have end sytem
> > metrics, transport level metric, transport level metric, they
> > can be measured and collected from the different RTP
> > comoponents specified in RFC3550, RFC5117. Apparently end
> > system metric can only be collected from RTP end system.
> > transport metric is collected from any RTP system in the RTP
> > monitoring architecture, regarding application level metric,
> > apparently they should be measured at the application layer
> > and can not be collected from RTP transport translator, Also
> > RTP transport translator is still a functional entity rather
> > than a physical entity. I am not convincing with what you
> > said about "contradiction", "lead to possible wrong expectations".
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Thursday, December 08, 2011 12:24 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > Qin,
> > that's NOT the point.
> >
> > All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> ENTITIES (FE).
> > e.g.,
> > - the RTP Monitor or RTP receiver FE may be located in
> > different PHYSICAL ENTITIES (PE), e.g.
> >         a1) a user equipment
> >         a2) a RTP-to-PSTN gateway
> >         a3) an IP-to-IP session border gateway (in a
> > back-to-back RTP endsystem topology)
> >         a3) ...
> >
> > - the RTP Monitor may be associated to an RTP transport
> translator ...
> >         b1) an IP-to-IP session border gateway
> >
> > The "RTP monitoring architecture" is IMPACTED by each
> > functional-to-physical mapping because e.g.
> > * QoE related metrics are questionable in case of a2
> > ("despite the fact of a RTP receiver function")
> > * application level metrics at the location of a RTP
> > transport translator are a contradiction in itself
> > * ...
> >
> > Again, it's not really changing the MONARCH draft because in
> > the very majority of scenarios it is correct. However, there
> > are few cases where the MONARCH description would be "too
> > high level", "not fully correct", "lead to possible wrong
> > expectations", ...
> >
> > Regards,
> > Albrecht
> >
> >
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Dienstag, 6. Dezember 2011 07:13
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > If you talk about existing RFC5117 RTP topology components,
> > > this has already been covered by the current version of
> > > draft-ietf-avtcore-monarch.
> > > In most cases, an RTP system using RTCP XR is architecturally
> > > no different from an RTP system which does not use RTCP XR.
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Monday, December 05, 2011 10:48 PM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > Hello Qin,
> > >
> > > to 1) Physical monitoring architecture
> > > Of course consideration of generic physical entities (PE),
> > > not specific to any network reference architectures defined
> > > by SDOs (like your refered entities).
> > > There would be just a few PE types ("given by the limited set
> > > of RTP topology components (RFC 5117)").
> > >
> > > to 2) (RFC 3550) Monitor function
> > > Right, that's a functional entity. The applicability of a
> > > monitor may be limited, dependent on ... (like in P.NAMS).
> > >
> > > to 3) your IMS network example
> > > Don't see the need to refer from MONARCH to a specific
> > > network architecture like IMS.
> > > Please also note that IMS is a functional architecture, not a
> > > physical architecture.
> > >
> > > Regards,
> > > Albrecht
> > >
> > > PS
> > > There are multiple options for adding the "RTP monitoring
> > > architecture" to a functional/physical network architecture:
> > > a) integrated approach: extension of existing functional
> > > entities or/and addition of RTP monitoring architectural
> > > components, extension or/and addition of
> > > signalling/management interfaces for control and
> > > configuration of RTP monitoring services, and reporting
> > > interfaces for measurement data ...
> > > b) overlay approach: separate specification to ...
> > >
> > >
> > > PSS
> > > BTW: there's a discussion paper with regards to the location
> > > of a monitor function in an IMS H.248 gateway entity:
> > > Measurements and statistics in IMS - Use Cases
> > > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > > 8_Kyoto_Japan/Docs/C3-100469.zip
> > > This is just fyi.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > Behalf Of Qin Wu
> > > > Sent: Freitag, 2. Dezember 2011 02:55
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi, Albrecht:
> > > > No offence, I am not really convinced with your proposal on
> > > > physical monitoring architecture.
> > > >  my counterquestion is what does physical monitoring
> > > > architecture looks like in your mind?
> > > > How many components do we have in such physical monitroing
> > > > architecture? what are they?
> > > > Take IMS network architecture as a example, they may have
> > > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > > described in draft-ietf-avtcore-monarch is mapped into
> > > > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > > > should be in the scope of IETF RTP monitoring
> archtiecture draft?
> > > >
> > > > Monitor described in  draft-ietf-avtcore-monarch is well
> > > > defined in the section 3 of RFC3550 as follows:
> > > > "
> > > >
> > > >    Monitor: An application that receives RTCP packets sent by
> > > >       participants in an RTP session, in particular the
> reception
> > > >       reports, and estimates the current quality of service for
> > > >       distribution monitoring, fault diagnosis and long-term
> > > > statistics.
> > > >       The monitor function is likely to be built into the
> > > > application(s)
> > > >       participating in the session, but may also be a separate
> > > >       application that does not otherwise participate and
> > > > does not send
> > > >       or receive the RTP data packets (since they are on
> > a separate
> > > >       port).  These are called third-party monitors.  It is also
> > > >       acceptable for a third-party monitor to receive
> the RTP data
> > > >       packets but not send RTCP packets or otherwise be
> > > counted in the
> > > >       session.
> > > >
> > > > "
> > > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > > implentation specific issue?
> > > > If this issue are really interesting, isn't it a good idea to
> > > > produce another new document to talk about this?
> > > > One good example for this motivation is this draft I like to
> > > > share with you:
> > > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > > y-00#section-4.6
> > > >
> > > > Regards!
> > > > -Qin
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Friday, December 02, 2011 12:20 AM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > My replies below ...
> > > > -Albrecht
> > > >
> > > > > -----Original Message-----
> > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi,
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > My replies below inline,
> > > > > Albrecht
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > > Hi,
> > > > > > ----- Original Message -----
> > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > To: <avt@ietf.org>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > > Subject: [AVTCORE] Types of monitoring
> architectures; RE: I-D
> > > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > >
> > > > > > > Dear All,
> > > > > > >
> > > > > > > there are different types of monitoring architectures,
> > > > > > particularily from perspective of QoE related performance
> > > > > parameters.
> > > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > > >
> > > > > > > Quality of Experience (QoE):
> > > > > > > The overall acceptability of an application or service, as
> > > > > > perceived subjectively by the end-user.
> > > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > > end-to-end system effects (client, terminal, network,
> > > > > > services infrastructure, etc.).
> > > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > > expectations and context.
> > > > > > >
> > > > > > > Important for MONARCH:
> > > > > > > 1st ... perceived by end-user
> > > > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > > > >
> > > > > > > That said, present RTP monitoring architecture in MONARCH
> > > > > > according clause 3 is not specific on the type of monitoring
> > > > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > > > to a terminal/user equipment (UE). This would be an
> > > > > > end-to-end IP network scenario.
> > > > > > >
> > > > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > > > be also located at the edge of an IP network, e.g. in a
> > > > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > > > the non-IP network part.
> > > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > > (I've Cc'd megaco list).
> > > > > > >
> > > > > > > An RTP Sender/Receiver located NOT in the UE
> would question
> > > > > > the value of RTP/RTCP QoE related performance measurements
> > > > > > (because the UE is located outside the RTP domain).
> > > > > > >
> > > > > > > Conclusions:
> > > > > > > - the set of meaningful performance metrics may be
> > > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > > whether in a UE, gateway, ...
> > > > > > > - don't see any impact on transport level metrics
> > > > > > > - ... but the set of meaningful application level metrics
> > > > > > >
> > > > > > > Proposal for MONARCH:
> > > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > > architecture" below clause 3
> > > > > > >
> > > > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > > > >
> > > > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > > > The location of the RTP Sender/Receiver entity may impact
> > > > > > the set of meaningful metrics.
> > > > > > > For instance: application level metrics for QoE related
> > > > > > performance metrics are questionable (or doesn't really make
> > > > > > sense at all) when measured in a network node (terminating
> > > > > > the RTP) instead of the user equipment."
> > > > > > >
> > > > > > > Something like this would help to avoid confusion.
> > > > > > > I even believe that a QoE measurement in a network node
> > > > > > would violate the QoE definition. Would be rather something
> > > > > > like QoE* ("remote QoE"):-(
> > > > > > >
> > > > > > > Such information would improve the MONARCH doc in
> > my opinion.
> > > > > > > Sorry for that late comment.
> > > > > > > Any views?
> > > > > >
> > > > > > [Qin]:
> > > > > > Albrrecht, if you follow ealry list discussion on
> > > > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > > > to position this document was
> > > > > > this daft should focus on guidelines for defining reporting
> > > > > > blocks. That is to say the main purpose of MONARCH draft
> > > > is how to
> > > > > > provide guidelines for the development of new RTCP XR block
> > > > > > types in XRBlock working group.
> > > > >
> > > > > [ABS] ... then the title "monitoring architectures" is
> > misleading.
> > > > > Proposal: keep title, revise scope section on focus
> > > > >
> > > > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > > > not expand scope into IP monitoring architecture.
> > > >
> > > > [ABS] That's wasn't the intent! Did just focus on the key word.
> > > >
> > > > >
> > > > > >
> > > > > > Therefore how and where to collect the metric from RTP
> > > > > > endpoint is not scope of this document, in my opinion. since
> > > > > > you may have many ways to do this and different vendors have
> > > > > > their different appoaches. It will be better to leave this
> > > > > > beyond the scope. But you are right, it will be more
> > > > > > reasonable to measure QoE related performance metric at the
> > > > > > RTP receiver.
> > > > >
> > > > > [ABS] I would disagree. At least your statement should be
> > > > > conditional, sth like
> > > > > "QoE related performance metrics may be measured in a RTP
> > > > > receiver, IF the RTP receiver function is located in user
> > > > > equipment (e.g. IP terminal), because QoE performance metrics
> > > > > are tightly coupled to the point of view of a 'user'.
> > > > > ... IF NOT, then ..."
> > > > >
> > > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > > right term from RTP perspective.
> > > > >
> > > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > > related metric can be placed either at the network or at
> > > the client.
> > > > > So I disagree with what you said.
> > > >
> > > > [ABS] Not convinced at all.
> > > > Guess you are referring to the "mid-point" models, right?
> > > > The usage of such that models depends on "prior knowledge
> > > > ..." information.
> > > > Thus, the applicability is conditional. You may not make such
> > > > a general statement.
> > > >
> > > >
> > > > >
> > > > > Also as I said, how and where to collect the metric from RTP
> > > > >  endpoint is not scope of this document. It depends on the
> > > > > model you are choosing, e.g., four operation modes specified
> > > > > in P.NAMS.
> > > > > Apparently this should not be specified again in RTP
> > > > > monitoring architecture document.
> > > > >
> > > > > >
> > > > > > Another point is it is not clear to me how RTP
> monitoring has
> > > > > > to do with architectureend to end IP network architecture .
> > > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > > Therefore I am quite doubt that we should describe anything
> > > > > > in this document like how
> > > > > > RTP entties is mapped into network entities/nodes at
> > > the IP layer.
> > > > >
> > > > > [ABS] I don't got any problems to talk about architectural
> > > > > framework for monitoring in this document. Such information
> > > > > is required and this is the only IETF AVT doc about it.
> > > > > The solution to this issue is rather simple to me:
> > > > > - split the MONARCH "monitoring architecture" in
> > > > > 1) a functional monitoring architecture (let's call it
> > 'FMA') and
> > > > > 2) a physical monitoring architecture (... 'PMA').
> > > > >
> > > > > - the present MONARCH doc would describe the FMA at the level
> > > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > > topology components according RFC 5117)
> > > > >
> > > > > - there are many options of functional-to-physical mappings,
> > > > > i.e. how a FMA would be mapped on a PMA
> > > > > - the mapping is typically dependent on considered network
> > > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> > networks)
> > > > >
> > > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > > mapping IF all RTP receiver/sender entities would be located
> > > > > in physical IP terminals (UEs)
> > > > > - etc
> > > > >
> > > > > [Qin]: I can understand your point, but you can not do that.
> > > > > Since this document is only focus on *RTP* monitoring
> > > > > architecture, that is what it said in AVTCore milestone:
> > > > > "
> > > > >
> > > > > Goals and Milestones:
> > > > >
> > > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > > Informational
> > > > >
> > > > > "
> > > >
> > > > [ABS] If you go back to my first email on this subject, and
> > > > if you look at my proposal: that's not a lot, nothing which
> > > > violates the charter, goals and milestones.
> > > >
> > > >
> > > > > Also if you really don't see how to map FMA to PMA, you may
> > > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > > As for how to use RTP monitoring architecture or RTP XR
> > > > > Report in the IMS network architecture, you may look at:
> > > > > http://tools.ietf.org/html/rfc6035
> > > >
> > > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > > primarily for physical IP user equipment with embedded RTP
> > > > sender/receiver function and SIP UA function.
> > > > However, the applicability of RFC 6035 is limited for a
> > > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > > located NOT in user equipment. Also the P.NAMS mid-point
> > > > model fails for such a scenario.
> > > >
> > > > > ITU-T H.248.48.
> > > > > But I haven't check the current status of H.248.48.
> > > >
> > > > [ABS] Work is finalized, see
> > > > http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> > > > 11121-TD-PLEN-0419
> > > >
> > > > >
> > > > > >
> > > > > > But as the author of this document, I am interested and open
> > > > > > to other opinions.:-)
> > > > >
> > > > > [ABS] Like to add a further aspect: a "functional monitoring
> > > > > architecture" may be considered as a network overlay,
> > > > > something which adds additional capabilities (here:
> > > > > measurement services, reporting services on top of basic RTP
> > > > > services).
> > > > > Such an overlay concept is nothing new: e.g., the
> > > > > MultiService Forum did define a "Performance Measurement &
> > > > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > > > considered as such.
> > > > >
> > > > > >
> > > > > > > Regards,
> > > > > > > Albrecht
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >> -----Original Message-----
> > > > > > >> From: avt-bounces@ietf.org
> [mailto:avt-bounces@ietf.org] On
> > > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > > >> To: i-d-announce@ietf.org
> > > > > > >> Cc: avt@ietf.org
> > > > > > >> Subject: [AVTCORE] I-D Action:
> > > > draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >>
> > > > > > >> A New Internet-Draft is available from the on-line
> > > > > > >> Internet-Drafts directories. This draft is a work
> > item of the
> > > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > > of the IETF.
> > > > > > >>
> > > > > > >> Title           : Monitoring Architectures for RTP
> > > > > > >> Author(s)       : Qin Wu
> > > > > > >>                           Geoff Hunt
> > > > > > >>                           Philip Arden
> > > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > > >> Pages           : 25
> > > > > > >> Date            : 2011-11-28
> > > > > > >>
> > > > > > >>    This memo proposes an architecture for
> > extending RTCP with
> > > > > > >> a new RTCP
> > > > > > >>    XR (RFC3611) block type to report new metrics
> > > > regarding media
> > > > > > >>    transmission or reception quality, following RTCP
> > > guideline
> > > > > > >>    established in RFC5968.  This memo suggests that a new
> > > > > > block should
> > > > > > >>    contain a single metric or a small number of metrics
> > > > > > relevant to a
> > > > > > >>    single parameter of interest or concern, rather than
> > > > > > containing a
> > > > > > >>    number of metrics which attempt to provide
> full coverage
> > > > > > >> of all those
> > > > > > >>    parameters of concern to a specific application.
> > > > > > Applications may
> > > > > > >>    then "mix and match" to create a set of blocks which
> > > > > > >> covers their set
> > > > > > >>    of concerns.  Where possible, a specific
> block should be
> > > > > > >> designed to
> > > > > > >>    be re-usable across more than one application, for
> > > > > > example, for all
> > > > > > >>    of voice, streaming audio and video.
> > > > > > >>
> > > > > > >>
> > > > > > >> A URL for this Internet-Draft is:
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > > >>
> > > > > > >> This Internet-Draft can be retrieved at:
> > > > > > >>
> > > > > >
> > > >
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >> _______________________________________________
> > > > > > >> Audio/Video Transport Core Maintenance
> > > > > > >> avt@ietf.org
> > > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > > >>
> > > > > > > _______________________________________________
> > > > > > > Audio/Video Transport Core Maintenance
> > > > > > > avt@ietf.org
> > > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > > >
> > > > > =3D
> > > > _______________________________________________
> > > > Audio/Video Transport Core Maintenance
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > >
> >
>

From csp@csperkins.org  Mon Dec 12 08:57:15 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35D5D21F8B7E; Mon, 12 Dec 2011 08:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=-0.194, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EmFtfnF00tWr; Mon, 12 Dec 2011 08:57:13 -0800 (PST)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by ietfa.amsl.com (Postfix) with ESMTP id CC84021F8B75; Mon, 12 Dec 2011 08:57:12 -0800 (PST)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1Ra9Bf-0004n0-Xj; Mon, 12 Dec 2011 16:57:11 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Date: Mon, 12 Dec 2011 16:56:57 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BEF8708-58B8-4AEB-B3A6-702F46E58C12@csperkins.org>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "megaco@ietf.org" <megaco@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 16:57:15 -0000

Albrecht, Qin,

It doesn't seem controversial that some metrics are only meaningful in =
some scenarios, or when measured at certain points in a system. I don't =
see how adding a statement to the monarch draft to recognise that could =
be problematic. Is there anything else being suggested here?

Colin


On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
> Hi Qin,
>=20
> I'm very aware about all that.
> It looks like that you are now agreeing that QoE measurements are =
CONDITIONAL ("you got a number of IF statements, there might be even =
more ...").
>=20
> MONARCH is not talking about such conditions, thus some readers may =
got the impression that the metrics related to RTP traffic are =
UNCONDITIONAL (which is not true as you confirmed).
>=20
> If you go back to my very first email: I did just propose to indicate =
the conditional aspect. Don't understand why such kind of valuable info =
would be not in scope of MONARCH. Hm?
>=20
> Regards,
> Albrecht
>=20
> PS
> I did use the notion of a control plane agnostic "RTP-to-PSTN =
gateway". You did indicate control plane specific gateway types like =
SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol =
specific examples, but it doesn't change the underlying issue.
> The SIP side reporting capability based on RFC 6035 allows to report =
the outlined measurements, but the RFC itself does not specify whether =
the reported information is meaningful (which is OK because this is not =
subject of a reporting interface spec, it is rather subject of a network =
monitoring doc like MONARCH).
> QoE measurements would be conditional in both gateway types (because =
such a gateway is NOT a user device despite the fact of an embedded SIP =
user agent entity).
> Actually I would even question here the condition of "customer knows =
the original content" in many real network scenarios.
>=20
>=20
>=20
>> -----Original Message-----
>> From: Qin Wu [mailto:bill.wu@huawei.com]
>> Sent: Montag, 12. Dezember 2011 05:05
>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>> Cc: megaco@ietf.org
>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>=20
>> Hi, Albrecht:
>> My understanding to QoE measurment is:
>> The factors that influence the QoE metric include encoding
>> system, transport network, access network,home network and end =
device.
>> If the customer(e.g., network operator) doesn't know the
>> original content, the QoE metric should be usually measured
>> at the user device.
>> If the customer knows the original content, the QoE metric
>> can be measured either in the network or at the user device.
>> Given the growing popularity of connected devices, these
>> devices may have different capability corresponding to CPU
>> load, processing overhead, storage, batteries.
>> If the cusomer want to measure QoE without considering
>> connected devices with various capability , the QoE metric
>> can be measured at the point between access network and home network.
>>=20
>> Regarding the monitoring scenario you mentioned, I am not
>> familiar with such scenario with RTP-to-PSTN gateway deployed.
>> But I am aware that there are scenarios with SIP to PSTN
>> gateway or SIP to H.323 gateway widely deployed,  RFC6035
>> defines a new SIP event package, vq-rtcpxr that enable the
>> collection and  reporting of metrics that measure quality for
>> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
>> metric included is measured at the user device and mapped
>> into the equivalent SIP vq-rtcpxr parameter since SIP session
>> call is established end to end and RTP media stream is
>> exchanged directly between one endpoint and the other endpoint.
>>=20
>> Regards!
>> -Qin
>> ----- Original Message -----
>> From: "Schwarz, Albrecht (Albrecht)"
>> <albrecht.schwarz@alcatel-lucent.com>
>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>> Cc: <megaco@ietf.org>
>> Sent: Saturday, December 10, 2011 12:01 AM
>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>=20
>>=20
>> How do you explain to a network operator the value of QoE
>> measurements by an RTP receiver / RTP monitor component
>> located in an RTP-to-PSTN gateway?
>>=20
>> This would be a monitoring scenario inline with MONARCH, but
>> with valueless QoE results, right?
>>=20
>>=20
>>> -----Original Message-----
>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>> Sent: Donnerstag, 8. Dezember 2011 03:26
>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>> Cc: megaco@ietf.org
>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>=20
>>> You reiterate what you propose for physical entities in the
>>> early email.
>>> I am still not convicing with that.
>>>=20
>>> Since we have RTP components like RTP end system, RTP mixer,
>>> RTP media translator, RTP transport translator, RTP monitor
>>> specified in RFC3550 can be built into these component as a
>>> application. also monitor can be disjointed from these RTP
>>> components as a third party monitor. why we need to specify
>>> how to map RTP end system into user equipment, RTP translator
>>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
>>> border gateway since we have already mapped monitor into
>>> different RTP components.
>>> How many PE types you can enumerate? why they should be scope
>>> of RTP monitoring architecture?
>>>=20
>>> Also as specified in MONARCH draft, we have end sytem
>>> metrics, transport level metric, transport level metric, they
>>> can be measured and collected from the different RTP
>>> comoponents specified in RFC3550, RFC5117. Apparently end
>>> system metric can only be collected from RTP end system.
>>> transport metric is collected from any RTP system in the RTP
>>> monitoring architecture, regarding application level metric,
>>> apparently they should be measured at the application layer
>>> and can not be collected from RTP transport translator, Also
>>> RTP transport translator is still a functional entity rather
>>> than a physical entity. I am not convincing with what you
>>> said about "contradiction", "lead to possible wrong expectations".
>>>=20
>>> Regards!
>>> -Qin
>>> ----- Original Message -----
>>> From: "Schwarz, Albrecht (Albrecht)"
>>> <albrecht.schwarz@alcatel-lucent.com>
>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>> Cc: <megaco@ietf.org>
>>> Sent: Thursday, December 08, 2011 12:24 AM
>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>=20
>>>=20
>>> Qin,
>>> that's NOT the point.
>>>=20
>>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
>> ENTITIES (FE).
>>> e.g.,
>>> - the RTP Monitor or RTP receiver FE may be located in
>>> different PHYSICAL ENTITIES (PE), e.g.
>>>        a1) a user equipment
>>>        a2) a RTP-to-PSTN gateway
>>>        a3) an IP-to-IP session border gateway (in a
>>> back-to-back RTP endsystem topology)
>>>        a3) ...
>>>=20
>>> - the RTP Monitor may be associated to an RTP transport
>> translator ...
>>>        b1) an IP-to-IP session border gateway
>>>=20
>>> The "RTP monitoring architecture" is IMPACTED by each
>>> functional-to-physical mapping because e.g.
>>> * QoE related metrics are questionable in case of a2
>>> ("despite the fact of a RTP receiver function")
>>> * application level metrics at the location of a RTP
>>> transport translator are a contradiction in itself
>>> * ...
>>>=20
>>> Again, it's not really changing the MONARCH draft because in
>>> the very majority of scenarios it is correct. However, there
>>> are few cases where the MONARCH description would be "too
>>> high level", "not fully correct", "lead to possible wrong
>>> expectations", ...
>>>=20
>>> Regards,
>>> Albrecht
>>>=20
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>> Sent: Dienstag, 6. Dezember 2011 07:13
>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>> Cc: megaco@ietf.org
>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>=20
>>>> If you talk about existing RFC5117 RTP topology components,
>>>> this has already been covered by the current version of
>>>> draft-ietf-avtcore-monarch.
>>>> In most cases, an RTP system using RTCP XR is architecturally
>>>> no different from an RTP system which does not use RTCP XR.
>>>>=20
>>>> Regards!
>>>> -Qin
>>>> ----- Original Message -----
>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>> Cc: <megaco@ietf.org>
>>>> Sent: Monday, December 05, 2011 10:48 PM
>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>=20
>>>>=20
>>>> Hello Qin,
>>>>=20
>>>> to 1) Physical monitoring architecture
>>>> Of course consideration of generic physical entities (PE),
>>>> not specific to any network reference architectures defined
>>>> by SDOs (like your refered entities).
>>>> There would be just a few PE types ("given by the limited set
>>>> of RTP topology components (RFC 5117)").
>>>>=20
>>>> to 2) (RFC 3550) Monitor function
>>>> Right, that's a functional entity. The applicability of a
>>>> monitor may be limited, dependent on ... (like in P.NAMS).
>>>>=20
>>>> to 3) your IMS network example
>>>> Don't see the need to refer from MONARCH to a specific
>>>> network architecture like IMS.
>>>> Please also note that IMS is a functional architecture, not a
>>>> physical architecture.
>>>>=20
>>>> Regards,
>>>> Albrecht
>>>>=20
>>>> PS
>>>> There are multiple options for adding the "RTP monitoring
>>>> architecture" to a functional/physical network architecture:
>>>> a) integrated approach: extension of existing functional
>>>> entities or/and addition of RTP monitoring architectural
>>>> components, extension or/and addition of
>>>> signalling/management interfaces for control and
>>>> configuration of RTP monitoring services, and reporting
>>>> interfaces for measurement data ...
>>>> b) overlay approach: separate specification to ...
>>>>=20
>>>>=20
>>>> PSS
>>>> BTW: there's a discussion paper with regards to the location
>>>> of a monitor function in an IMS H.248 gateway entity:
>>>> Measurements and statistics in IMS - Use Cases
>>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
>>>> 8_Kyoto_Japan/Docs/C3-100469.zip
>>>> This is just fyi.
>>>>=20
>>>>=20
>>>>=20
>>>>> -----Original Message-----
>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>>>>> Behalf Of Qin Wu
>>>>> Sent: Freitag, 2. Dezember 2011 02:55
>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>> Cc: megaco@ietf.org
>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>=20
>>>>> Hi, Albrecht:
>>>>> No offence, I am not really convinced with your proposal on
>>>>> physical monitoring architecture.
>>>>> my counterquestion is what does physical monitoring
>>>>> architecture looks like in your mind?
>>>>> How many components do we have in such physical monitroing
>>>>> architecture? what are they?
>>>>> Take IMS network architecture as a example, they may have
>>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
>>>>> described in draft-ietf-avtcore-monarch is mapped into
>>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
>>>>> should be in the scope of IETF RTP monitoring
>> archtiecture draft?
>>>>>=20
>>>>> Monitor described in  draft-ietf-avtcore-monarch is well
>>>>> defined in the section 3 of RFC3550 as follows:
>>>>> "
>>>>>=20
>>>>>   Monitor: An application that receives RTCP packets sent by
>>>>>      participants in an RTP session, in particular the
>> reception
>>>>>      reports, and estimates the current quality of service for
>>>>>      distribution monitoring, fault diagnosis and long-term
>>>>> statistics.
>>>>>      The monitor function is likely to be built into the
>>>>> application(s)
>>>>>      participating in the session, but may also be a separate
>>>>>      application that does not otherwise participate and
>>>>> does not send
>>>>>      or receive the RTP data packets (since they are on
>>> a separate
>>>>>      port).  These are called third-party monitors.  It is also
>>>>>      acceptable for a third-party monitor to receive
>> the RTP data
>>>>>      packets but not send RTCP packets or otherwise be
>>>> counted in the
>>>>>      session.
>>>>>=20
>>>>> "
>>>>> Isn't how to implent monitor into IMS netowork archtiecture a
>>>>> implentation specific issue?
>>>>> If this issue are really interesting, isn't it a good idea to
>>>>> produce another new document to talk about this?
>>>>> One good example for this motivation is this draft I like to
>>>>> share with you:
>>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
>>>>> y-00#section-4.6
>>>>>=20
>>>>> Regards!
>>>>> -Qin
>>>>> ----- Original Message -----
>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>> Cc: <megaco@ietf.org>
>>>>> Sent: Friday, December 02, 2011 12:20 AM
>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>=20
>>>>>=20
>>>>> My replies below ...
>>>>> -Albrecht
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>> Cc: megaco@ietf.org
>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>=20
>>>>>> Hi,
>>>>>> ----- Original Message -----
>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>> Cc: <megaco@ietf.org>
>>>>>> Sent: Thursday, December 01, 2011 1:24 AM
>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>=20
>>>>>>=20
>>>>>> My replies below inline,
>>>>>> Albrecht
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>> Sent: Mittwoch, 30. November 2011 04:51
>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>> Cc: megaco@ietf.org
>>>>>>> Subject: Re: [AVTCORE] Types of monitoring
>> architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>=20
>>>>>>> Hi,
>>>>>>> ----- Original Message -----
>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>> To: <avt@ietf.org>
>>>>>>> Cc: <megaco@ietf.org>
>>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
>>>>>>> Subject: [AVTCORE] Types of monitoring
>> architectures; RE: I-D
>>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>=20
>>>>>>>=20
>>>>>>>> Dear All,
>>>>>>>>=20
>>>>>>>> there are different types of monitoring architectures,
>>>>>>> particularily from perspective of QoE related performance
>>>>>> parameters.
>>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
>>>>>>>>=20
>>>>>>>> Quality of Experience (QoE):
>>>>>>>> The overall acceptability of an application or service, as
>>>>>>> perceived subjectively by the end-user.
>>>>>>>> NOTE 1 - Quality of experience includes the complete
>>>>>>> end-to-end system effects (client, terminal, network,
>>>>>>> services infrastructure, etc.).
>>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
>>>>>>> expectations and context.
>>>>>>>>=20
>>>>>>>> Important for MONARCH:
>>>>>>>> 1st ... perceived by end-user
>>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
>>>>>>>>=20
>>>>>>>> That said, present RTP monitoring architecture in MONARCH
>>>>>>> according clause 3 is not specific on the type of monitoring
>>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
>>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
>>>>>>> to a terminal/user equipment (UE). This would be an
>>>>>>> end-to-end IP network scenario.
>>>>>>>>=20
>>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
>>>>>>> be also located at the edge of an IP network, e.g. in a
>>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
>>>>>>> the non-IP network part.
>>>>>>>> Note: such scenarios are considered by MEGACO gateways
>>>>>>> (I've Cc'd megaco list).
>>>>>>>>=20
>>>>>>>> An RTP Sender/Receiver located NOT in the UE
>> would question
>>>>>>> the value of RTP/RTCP QoE related performance measurements
>>>>>>> (because the UE is located outside the RTP domain).
>>>>>>>>=20
>>>>>>>> Conclusions:
>>>>>>>> - the set of meaningful performance metrics may be
>>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
>>>>>>> whether in a UE, gateway, ...
>>>>>>>> - don't see any impact on transport level metrics
>>>>>>>> - ... but the set of meaningful application level metrics
>>>>>>>>=20
>>>>>>>> Proposal for MONARCH:
>>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
>>>>>>> architecture" below clause 3
>>>>>>>>=20
>>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
>>>>>>>>=20
>>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
>>>>>>>> The location of the RTP Sender/Receiver entity may impact
>>>>>>> the set of meaningful metrics.
>>>>>>>> For instance: application level metrics for QoE related
>>>>>>> performance metrics are questionable (or doesn't really make
>>>>>>> sense at all) when measured in a network node (terminating
>>>>>>> the RTP) instead of the user equipment."
>>>>>>>>=20
>>>>>>>> Something like this would help to avoid confusion.
>>>>>>>> I even believe that a QoE measurement in a network node
>>>>>>> would violate the QoE definition. Would be rather something
>>>>>>> like QoE* ("remote QoE"):-(
>>>>>>>>=20
>>>>>>>> Such information would improve the MONARCH doc in
>>> my opinion.
>>>>>>>> Sorry for that late comment.
>>>>>>>> Any views?
>>>>>>>=20
>>>>>>> [Qin]:
>>>>>>> Albrrecht, if you follow ealry list discussion on
>>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
>>>>>>> to position this document was
>>>>>>> this daft should focus on guidelines for defining reporting
>>>>>>> blocks. That is to say the main purpose of MONARCH draft
>>>>> is how to
>>>>>>> provide guidelines for the development of new RTCP XR block
>>>>>>> types in XRBlock working group.
>>>>>>=20
>>>>>> [ABS] ... then the title "monitoring architectures" is
>>> misleading.
>>>>>> Proposal: keep title, revise scope section on focus
>>>>>>=20
>>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
>>>>>> not expand scope into IP monitoring architecture.
>>>>>=20
>>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> Therefore how and where to collect the metric from RTP
>>>>>>> endpoint is not scope of this document, in my opinion. since
>>>>>>> you may have many ways to do this and different vendors have
>>>>>>> their different appoaches. It will be better to leave this
>>>>>>> beyond the scope. But you are right, it will be more
>>>>>>> reasonable to measure QoE related performance metric at the
>>>>>>> RTP receiver.
>>>>>>=20
>>>>>> [ABS] I would disagree. At least your statement should be
>>>>>> conditional, sth like
>>>>>> "QoE related performance metrics may be measured in a RTP
>>>>>> receiver, IF the RTP receiver function is located in user
>>>>>> equipment (e.g. IP terminal), because QoE performance metrics
>>>>>> are tightly coupled to the point of view of a 'user'.
>>>>>> ... IF NOT, then ..."
>>>>>>=20
>>>>>> [Qin]: I am not sure user equipment or IP terminal is the
>>>>>> right term from RTP perspective.
>>>>>>=20
>>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
>>>>>> related metric can be placed either at the network or at
>>>> the client.
>>>>>> So I disagree with what you said.
>>>>>=20
>>>>> [ABS] Not convinced at all.
>>>>> Guess you are referring to the "mid-point" models, right?
>>>>> The usage of such that models depends on "prior knowledge
>>>>> ..." information.
>>>>> Thus, the applicability is conditional. You may not make such
>>>>> a general statement.
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> Also as I said, how and where to collect the metric from RTP
>>>>>> endpoint is not scope of this document. It depends on the
>>>>>> model you are choosing, e.g., four operation modes specified
>>>>>> in P.NAMS.
>>>>>> Apparently this should not be specified again in RTP
>>>>>> monitoring architecture document.
>>>>>>=20
>>>>>>>=20
>>>>>>> Another point is it is not clear to me how RTP
>> monitoring has
>>>>>>> to do with architectureend to end IP network architecture .
>>>>>>> this draft mostly focus on discussing RTP level stuff.
>>>>>>> Therefore I am quite doubt that we should describe anything
>>>>>>> in this document like how
>>>>>>> RTP entties is mapped into network entities/nodes at
>>>> the IP layer.
>>>>>>=20
>>>>>> [ABS] I don't got any problems to talk about architectural
>>>>>> framework for monitoring in this document. Such information
>>>>>> is required and this is the only IETF AVT doc about it.
>>>>>> The solution to this issue is rather simple to me:
>>>>>> - split the MONARCH "monitoring architecture" in
>>>>>> 1) a functional monitoring architecture (let's call it
>>> 'FMA') and
>>>>>> 2) a physical monitoring architecture (... 'PMA').
>>>>>>=20
>>>>>> - the present MONARCH doc would describe the FMA at the level
>>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
>>>>>> topology components according RFC 5117)
>>>>>>=20
>>>>>> - there are many options of functional-to-physical mappings,
>>>>>> i.e. how a FMA would be mapped on a PMA
>>>>>> - the mapping is typically dependent on considered network
>>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
>>> networks)
>>>>>>=20
>>>>>> - the present MONARCH doc would describe the FMA-to-PMA
>>>>>> mapping IF all RTP receiver/sender entities would be located
>>>>>> in physical IP terminals (UEs)
>>>>>> - etc
>>>>>>=20
>>>>>> [Qin]: I can understand your point, but you can not do that.
>>>>>> Since this document is only focus on *RTP* monitoring
>>>>>> architecture, that is what it said in AVTCore milestone:
>>>>>> "
>>>>>>=20
>>>>>> Goals and Milestones:
>>>>>>=20
>>>>>>  Feb 2011 - Submit Monitoring Architecture for RTP for
>>>>> Informational
>>>>>>=20
>>>>>> "
>>>>>=20
>>>>> [ABS] If you go back to my first email on this subject, and
>>>>> if you look at my proposal: that's not a lot, nothing which
>>>>> violates the charter, goals and milestones.
>>>>>=20
>>>>>=20
>>>>>> Also if you really don't see how to map FMA to PMA, you may
>>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
>>>>>> As for how to use RTP monitoring architecture or RTP XR
>>>>>> Report in the IMS network architecture, you may look at:
>>>>>> http://tools.ietf.org/html/rfc6035
>>>>>=20
>>>>> [ABS] That's the SIP reporting interface, i.e., applicable
>>>>> primarily for physical IP user equipment with embedded RTP
>>>>> sender/receiver function and SIP UA function.
>>>>> However, the applicability of RFC 6035 is limited for a
>>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
>>>>> located NOT in user equipment. Also the P.NAMS mid-point
>>>>> model fails for such a scenario.
>>>>>=20
>>>>>> ITU-T H.248.48.
>>>>>> But I haven't check the current status of H.248.48.
>>>>>=20
>>>>> [ABS] Work is finalized, see
>>>>> http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
>>>>> 11121-TD-PLEN-0419
>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> But as the author of this document, I am interested and open
>>>>>>> to other opinions.:-)
>>>>>>=20
>>>>>> [ABS] Like to add a further aspect: a "functional monitoring
>>>>>> architecture" may be considered as a network overlay,
>>>>>> something which adds additional capabilities (here:
>>>>>> measurement services, reporting services on top of basic RTP
>>>>>> services).
>>>>>> Such an overlay concept is nothing new: e.g., the
>>>>>> MultiService Forum did define a "Performance Measurement &
>>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
>>>>>> considered as such.
>>>>>>=20
>>>>>>>=20
>>>>>>>> Regards,
>>>>>>>> Albrecht
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: avt-bounces@ietf.org
>> [mailto:avt-bounces@ietf.org] On
>>>>>>>>> Behalf Of internet-drafts@ietf.org
>>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>> Cc: avt@ietf.org
>>>>>>>>> Subject: [AVTCORE] I-D Action:
>>>>> draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>> Internet-Drafts directories. This draft is a work
>>> item of the
>>>>>>>>> Audio/Video Transport Core Maintenance Working Group
>>>>> of the IETF.
>>>>>>>>>=20
>>>>>>>>> Title           : Monitoring Architectures for RTP
>>>>>>>>> Author(s)       : Qin Wu
>>>>>>>>>                          Geoff Hunt
>>>>>>>>>                          Philip Arden
>>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> Pages           : 25
>>>>>>>>> Date            : 2011-11-28
>>>>>>>>>=20
>>>>>>>>>   This memo proposes an architecture for
>>> extending RTCP with
>>>>>>>>> a new RTCP
>>>>>>>>>   XR (RFC3611) block type to report new metrics
>>>>> regarding media
>>>>>>>>>   transmission or reception quality, following RTCP
>>>> guideline
>>>>>>>>>   established in RFC5968.  This memo suggests that a new
>>>>>>> block should
>>>>>>>>>   contain a single metric or a small number of metrics
>>>>>>> relevant to a
>>>>>>>>>   single parameter of interest or concern, rather than
>>>>>>> containing a
>>>>>>>>>   number of metrics which attempt to provide
>> full coverage
>>>>>>>>> of all those
>>>>>>>>>   parameters of concern to a specific application.
>>>>>>> Applications may
>>>>>>>>>   then "mix and match" to create a set of blocks which
>>>>>>>>> covers their set
>>>>>>>>>   of concerns.  Where possible, a specific
>> block should be
>>>>>>>>> designed to
>>>>>>>>>   be re-usable across more than one application, for
>>>>>>> example, for all
>>>>>>>>>   of voice, streaming audio and video.
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>=20
>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>>=20
>>>>>>>>> This Internet-Draft can be retrieved at:
>>>>>>>>>=20
>>>>>>>=20
>>>>>=20
>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>> avt@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>>=20
>>>>>>>> _______________________________________________
>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>> avt@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>=20
>>>>>> =3D
>>>>> _______________________________________________
>>>>> Audio/Video Transport Core Maintenance
>>>>> avt@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>=20
>>>>=20
>>>=20
>>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



--=20
Colin Perkins
http://csperkins.org/




From albrecht.schwarz@alcatel-lucent.com  Mon Dec 12 02:56:54 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 409B221F8B26; Mon, 12 Dec 2011 02:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cVUKuCpaoWBR; Mon, 12 Dec 2011 02:56:54 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id D5B5121F8B22; Mon, 12 Dec 2011 02:56:39 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pBCAshu7001190 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 11:55:44 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Mon, 12 Dec 2011 11:55:24 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Mon, 12 Dec 2011 11:55:22 +0100
Thread-Topic: Update proposal; RE: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acy4g3DuLm8Zu4LZQuq8wu6FtEozXgAM063AAAFLgHA=
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F5344@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
In-Reply-To: <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: multipart/mixed; boundary="_003_5F7BCCF5541B7444830A2288ABBEBC9621620F5344FRMRSSXCHMBSD_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
X-Mailman-Approved-At: Mon, 12 Dec 2011 09:55:26 -0800
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: [AVTCORE] Update proposal; RE: [Megaco]  Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 10:56:54 -0000

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


Might be more effective by continuing the discussion with a concrete text p=
roposal, see attachments.
Any comments?
Albrecht

> -----Original Message-----
> From: megaco-bounces@ietf.org
> [mailto:megaco-bounces@ietf.org] On Behalf Of Schwarz,
> Albrecht (Albrecht)
> Sent: Montag, 12. Dezember 2011 11:33
> To: Qin Wu; avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] [AVTCORE] Types of monitoring
> architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi Qin,
>
> I'm very aware about all that.
> It looks like that you are now agreeing that QoE measurements
> are CONDITIONAL ("you got a number of IF statements, there
> might be even more ...").
>
> MONARCH is not talking about such conditions, thus some
> readers may got the impression that the metrics related to
> RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
>
> If you go back to my very first email: I did just propose to
> indicate the conditional aspect. Don't understand why such
> kind of valuable info would be not in scope of MONARCH. Hm?
>
> Regards,
> Albrecht
>
> PS
> I did use the notion of a control plane agnostic "RTP-to-PSTN
> gateway". You did indicate control plane specific gateway
> types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such
> signalling protocol specific examples, but it doesn't change
> the underlying issue.
> The SIP side reporting capability based on RFC 6035 allows to
> report the outlined measurements, but the RFC itself does not
> specify whether the reported information is meaningful (which
> is OK because this is not subject of a reporting interface
> spec, it is rather subject of a network monitoring doc like MONARCH).
> QoE measurements would be conditional in both gateway types
> (because such a gateway is NOT a user device despite the fact
> of an embedded SIP user agent entity).
> Actually I would even question here the condition of
> "customer knows the original content" in many real network scenarios.
>
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Montag, 12. Dezember 2011 05:05
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi, Albrecht:
> > My understanding to QoE measurment is:
> > The factors that influence the QoE metric include encoding system,
> > transport network, access network,home network and end device.
> > If the customer(e.g., network operator) doesn't know the original
> > content, the QoE metric should be usually measured at the
> user device.
> > If the customer knows the original content, the QoE metric can be
> > measured either in the network or at the user device.
> > Given the growing popularity of connected devices, these
> devices may
> > have different capability corresponding to CPU load, processing
> > overhead, storage, batteries.
> > If the cusomer want to measure QoE without considering connected
> > devices with various capability , the QoE metric can be measured at
> > the point between access network and home network.
> >
> > Regarding the monitoring scenario you mentioned, I am not familiar
> > with such scenario with RTP-to-PSTN gateway deployed.
> > But I am aware that there are scenarios with SIP to PSTN gateway or
> > SIP to H.323 gateway widely deployed,  RFC6035 defines a
> new SIP event
> > package, vq-rtcpxr that enable the collection and  reporting of
> > metrics that measure quality for RTP sessions. In such
> cases, RTCP XR
> > VOIP metric with QoE metric included is measured at the user device
> > and mapped into the equivalent SIP vq-rtcpxr parameter since SIP
> > session call is established end to end and RTP media stream is
> > exchanged directly between one endpoint and the other endpoint.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Saturday, December 10, 2011 12:01 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > How do you explain to a network operator the value of QoE
> measurements
> > by an RTP receiver / RTP monitor component located in an
> RTP-to-PSTN
> > gateway?
> >
> > This would be a monitoring scenario inline with MONARCH, but with
> > valueless QoE results, right?
> >
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Donnerstag, 8. Dezember 2011 03:26
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > You reiterate what you propose for physical entities in the early
> > > email.
> > > I am still not convicing with that.
> > >
> > > Since we have RTP components like RTP end system, RTP mixer, RTP
> > > media translator, RTP transport translator, RTP monitor
> specified in
> > > RFC3550 can be built into these component as a application. also
> > > monitor can be disjointed from these RTP components as a
> third party
> > > monitor. why we need to specify how to map RTP end system
> into user
> > > equipment, RTP translator or RTP mixer can be mapped into
> RTP-PSTN
> > > gateway, or IP to IP border gateway since we have already mapped
> > > monitor into different RTP components.
> > > How many PE types you can enumerate? why they should be
> scope of RTP
> > > monitoring architecture?
> > >
> > > Also as specified in MONARCH draft, we have end sytem metrics,
> > > transport level metric, transport level metric, they can
> be measured
> > > and collected from the different RTP comoponents specified in
> > > RFC3550, RFC5117. Apparently end system metric can only
> be collected
> > > from RTP end system.
> > > transport metric is collected from any RTP system in the RTP
> > > monitoring architecture, regarding application level metric,
> > > apparently they should be measured at the application
> layer and can
> > > not be collected from RTP transport translator, Also RTP
> transport
> > > translator is still a functional entity rather than a physical
> > > entity. I am not convincing with what you said about
> > > "contradiction", "lead to possible wrong expectations".
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Thursday, December 08, 2011 12:24 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > Qin,
> > > that's NOT the point.
> > >
> > > All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> > ENTITIES (FE).
> > > e.g.,
> > > - the RTP Monitor or RTP receiver FE may be located in different
> > > PHYSICAL ENTITIES (PE), e.g.
> > >         a1) a user equipment
> > >         a2) a RTP-to-PSTN gateway
> > >         a3) an IP-to-IP session border gateway (in a back-to-back
> > > RTP endsystem topology)
> > >         a3) ...
> > >
> > > - the RTP Monitor may be associated to an RTP transport
> > translator ...
> > >         b1) an IP-to-IP session border gateway
> > >
> > > The "RTP monitoring architecture" is IMPACTED by each
> > > functional-to-physical mapping because e.g.
> > > * QoE related metrics are questionable in case of a2
> ("despite the
> > > fact of a RTP receiver function")
> > > * application level metrics at the location of a RTP transport
> > > translator are a contradiction in itself
> > > * ...
> > >
> > > Again, it's not really changing the MONARCH draft because in the
> > > very majority of scenarios it is correct. However, there are few
> > > cases where the MONARCH description would be "too high
> level", "not
> > > fully correct", "lead to possible wrong expectations", ...
> > >
> > > Regards,
> > > Albrecht
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Dienstag, 6. Dezember 2011 07:13
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > If you talk about existing RFC5117 RTP topology
> components, this
> > > > has already been covered by the current version of
> > > > draft-ietf-avtcore-monarch.
> > > > In most cases, an RTP system using RTCP XR is
> architecturally no
> > > > different from an RTP system which does not use RTCP XR.
> > > >
> > > > Regards!
> > > > -Qin
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Monday, December 05, 2011 10:48 PM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > Hello Qin,
> > > >
> > > > to 1) Physical monitoring architecture Of course
> consideration of
> > > > generic physical entities (PE), not specific to any network
> > > > reference architectures defined by SDOs (like your refered
> > > > entities).
> > > > There would be just a few PE types ("given by the
> limited set of
> > > > RTP topology components (RFC 5117)").
> > > >
> > > > to 2) (RFC 3550) Monitor function
> > > > Right, that's a functional entity. The applicability of
> a monitor
> > > > may be limited, dependent on ... (like in P.NAMS).
> > > >
> > > > to 3) your IMS network example
> > > > Don't see the need to refer from MONARCH to a specific network
> > > > architecture like IMS.
> > > > Please also note that IMS is a functional architecture, not a
> > > > physical architecture.
> > > >
> > > > Regards,
> > > > Albrecht
> > > >
> > > > PS
> > > > There are multiple options for adding the "RTP monitoring
> > > > architecture" to a functional/physical network architecture:
> > > > a) integrated approach: extension of existing
> functional entities
> > > > or/and addition of RTP monitoring architectural components,
> > > > extension or/and addition of signalling/management
> interfaces for
> > > > control and configuration of RTP monitoring services, and
> > > > reporting interfaces for measurement data ...
> > > > b) overlay approach: separate specification to ...
> > > >
> > > >
> > > > PSS
> > > > BTW: there's a discussion paper with regards to the
> location of a
> > > > monitor function in an IMS H.248 gateway entity:
> > > > Measurements and statistics in IMS - Use Cases
> > > > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > > > 8_Kyoto_Japan/Docs/C3-100469.zip
> > > > This is just fyi.
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > > Behalf Of Qin Wu
> > > > > Sent: Freitag, 2. Dezember 2011 02:55
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi, Albrecht:
> > > > > No offence, I am not really convinced with your proposal on
> > > > > physical monitoring architecture.
> > > > >  my counterquestion is what does physical monitoring
> > > > > architecture looks like in your mind?
> > > > > How many components do we have in such physical monitroing
> > > > > architecture? what are they?
> > > > > Take IMS network architecture as a example, they may have
> > > > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > > > described in draft-ietf-avtcore-monarch is mapped
> into P-CSCF,
> > > > > S-CSCF, SBC, Media Gateway, Media Gateway Controller
> should be
> > > > > in the scope of IETF RTP monitoring
> > archtiecture draft?
> > > > >
> > > > > Monitor described in  draft-ietf-avtcore-monarch is
> well defined
> > > > > in the section 3 of RFC3550 as follows:
> > > > > "
> > > > >
> > > > >    Monitor: An application that receives RTCP packets sent by
> > > > >       participants in an RTP session, in particular the
> > reception
> > > > >       reports, and estimates the current quality of
> service for
> > > > >       distribution monitoring, fault diagnosis and long-term
> > > > > statistics.
> > > > >       The monitor function is likely to be built into the
> > > > > application(s)
> > > > >       participating in the session, but may also be a separate
> > > > >       application that does not otherwise participate
> and does
> > > > > not send
> > > > >       or receive the RTP data packets (since they are on
> > > a separate
> > > > >       port).  These are called third-party monitors.
> It is also
> > > > >       acceptable for a third-party monitor to receive
> > the RTP data
> > > > >       packets but not send RTCP packets or otherwise be
> > > > counted in the
> > > > >       session.
> > > > >
> > > > > "
> > > > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > > > implentation specific issue?
> > > > > If this issue are really interesting, isn't it a good idea to
> > > > > produce another new document to talk about this?
> > > > > One good example for this motivation is this draft I like to
> > > > > share with you:
> > > > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > > > y-00#section-4.6
> > > > >
> > > > > Regards!
> > > > > -Qin
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Friday, December 02, 2011 12:20 AM
> > > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > My replies below ...
> > > > > -Albrecht
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > > Hi,
> > > > > > ----- Original Message -----
> > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > > > Subject: RE: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > >
> > > > > > My replies below inline,
> > > > > > Albrecht
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: Re: [AVTCORE] Types of monitoring
> > architectures; RE:
> > > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > > >
> > > > > > > Hi,
> > > > > > > ----- Original Message -----
> > > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > > To: <avt@ietf.org>
> > > > > > > Cc: <megaco@ietf.org>
> > > > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > > > Subject: [AVTCORE] Types of monitoring
> > architectures; RE: I-D
> > > > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > > > >
> > > > > > >
> > > > > > > > Dear All,
> > > > > > > >
> > > > > > > > there are different types of monitoring architectures,
> > > > > > > particularily from perspective of QoE related performance
> > > > > > parameters.
> > > > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > > > >
> > > > > > > > Quality of Experience (QoE):
> > > > > > > > The overall acceptability of an application or
> service, as
> > > > > > > perceived subjectively by the end-user.
> > > > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > > > end-to-end system effects (client, terminal, network,
> > > > > > > services infrastructure, etc.).
> > > > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > > > expectations and context.
> > > > > > > >
> > > > > > > > Important for MONARCH:
> > > > > > > > 1st ... perceived by end-user 2nd QoE includes the
> > > > > > > > complete end-to-end sytem effects ...
> > > > > > > >
> > > > > > > > That said, present RTP monitoring architecture
> in MONARCH
> > > > > > > according clause 3 is not specific on the type of
> monitoring
> > > > > > > architecture. For instance, Fig. 1, it is
> possibly supposed
> > > > > > > that the "RTP Sender" and "RTP Receiver" entities
> are equal
> > > > > > > to a terminal/user equipment (UE). This would be an
> > > > > > > end-to-end IP network scenario.
> > > > > > > >
> > > > > > > > However, the "RTP Sender" and "RTP Receiver"
> entities may
> > > > > > > be also located at the edge of an IP network, e.g. in a
> > > > > > > gateway for IP-to-non-IP interworking, i.e. an UE
> located in
> > > > > > > the non-IP network part.
> > > > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > > > (I've Cc'd megaco list).
> > > > > > > >
> > > > > > > > An RTP Sender/Receiver located NOT in the UE
> > would question
> > > > > > > the value of RTP/RTCP QoE related performance
> measurements
> > > > > > > (because the UE is located outside the RTP domain).
> > > > > > > >
> > > > > > > > Conclusions:
> > > > > > > > - the set of meaningful performance metrics may be
> > > > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > > > whether in a UE, gateway, ...
> > > > > > > > - don't see any impact on transport level metrics
> > > > > > > > - ... but the set of meaningful application
> level metrics
> > > > > > > >
> > > > > > > > Proposal for MONARCH:
> > > > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > > > architecture" below clause 3
> > > > > > > >
> > > > > > > > #2: add a sub-clause 3.2 at the end of clause
> 3, sth like
> > > > > > > >
> > > > > > > > "3.2 RTP Sender/Receiver entities located in
> network nodes
> > > > > > > > The location of the RTP Sender/Receiver entity
> may impact
> > > > > > > the set of meaningful metrics.
> > > > > > > > For instance: application level metrics for QoE related
> > > > > > > performance metrics are questionable (or doesn't
> really make
> > > > > > > sense at all) when measured in a network node
> (terminating
> > > > > > > the RTP) instead of the user equipment."
> > > > > > > >
> > > > > > > > Something like this would help to avoid confusion.
> > > > > > > > I even believe that a QoE measurement in a network node
> > > > > > > would violate the QoE definition. Would be rather
> something
> > > > > > > like QoE* ("remote QoE"):-(
> > > > > > > >
> > > > > > > > Such information would improve the MONARCH doc in
> > > my opinion.
> > > > > > > > Sorry for that late comment.
> > > > > > > > Any views?
> > > > > > >
> > > > > > > [Qin]:
> > > > > > > Albrrecht, if you follow ealry list discussion on
> > > > > > > draft-hunt-avt-monarch-01, you will see the rough
> consensus
> > > > > > > to position this document was this daft should focus on
> > > > > > > guidelines for defining reporting blocks. That is
> to say the
> > > > > > > main purpose of MONARCH draft
> > > > > is how to
> > > > > > > provide guidelines for the development of new
> RTCP XR block
> > > > > > > types in XRBlock working group.
> > > > > >
> > > > > > [ABS] ... then the title "monitoring architectures" is
> > > misleading.
> > > > > > Proposal: keep title, revise scope section on focus
> > > > > >
> > > > > > [Qin]: No, the title is *RTP* monitoring
> architecture, we can
> > > > > > not expand scope into IP monitoring architecture.
> > > > >
> > > > > [ABS] That's wasn't the intent! Did just focus on the
> key word.
> > > > >
> > > > > >
> > > > > > >
> > > > > > > Therefore how and where to collect the metric from RTP
> > > > > > > endpoint is not scope of this document, in my
> opinion. since
> > > > > > > you may have many ways to do this and different
> vendors have
> > > > > > > their different appoaches. It will be better to
> leave this
> > > > > > > beyond the scope. But you are right, it will be more
> > > > > > > reasonable to measure QoE related performance
> metric at the
> > > > > > > RTP receiver.
> > > > > >
> > > > > > [ABS] I would disagree. At least your statement should be
> > > > > > conditional, sth like "QoE related performance
> metrics may be
> > > > > > measured in a RTP receiver, IF the RTP receiver function is
> > > > > > located in user equipment (e.g. IP terminal), because QoE
> > > > > > performance metrics are tightly coupled to the
> point of view
> > > > > > of a 'user'.
> > > > > > ... IF NOT, then ..."
> > > > > >
> > > > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > > > right term from RTP perspective.
> > > > > >
> > > > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > > > related metric can be placed either at the network or at
> > > > the client.
> > > > > > So I disagree with what you said.
> > > > >
> > > > > [ABS] Not convinced at all.
> > > > > Guess you are referring to the "mid-point" models, right?
> > > > > The usage of such that models depends on "prior
> knowledge ..."
> > > > > information.
> > > > > Thus, the applicability is conditional. You may not
> make such a
> > > > > general statement.
> > > > >
> > > > >
> > > > > >
> > > > > > Also as I said, how and where to collect the metric
> from RTP
> > > > > > endpoint is not scope of this document. It depends on the
> > > > > > model you are choosing, e.g., four operation modes
> specified
> > > > > > in P.NAMS.
> > > > > > Apparently this should not be specified again in RTP
> > > > > > monitoring architecture document.
> > > > > >
> > > > > > >
> > > > > > > Another point is it is not clear to me how RTP
> > monitoring has
> > > > > > > to do with architectureend to end IP network
> architecture .
> > > > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > > > Therefore I am quite doubt that we should
> describe anything
> > > > > > > in this document like how RTP entties is mapped
> into network
> > > > > > > entities/nodes at
> > > > the IP layer.
> > > > > >
> > > > > > [ABS] I don't got any problems to talk about architectural
> > > > > > framework for monitoring in this document. Such
> information is
> > > > > > required and this is the only IETF AVT doc about it.
> > > > > > The solution to this issue is rather simple to me:
> > > > > > - split the MONARCH "monitoring architecture" in
> > > > > > 1) a functional monitoring architecture (let's call it
> > > 'FMA') and
> > > > > > 2) a physical monitoring architecture (... 'PMA').
> > > > > >
> > > > > > - the present MONARCH doc would describe the FMA at
> the level
> > > > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > > > topology components according RFC 5117)
> > > > > >
> > > > > > - there are many options of functional-to-physical
> mappings,
> > > > > > i.e. how a FMA would be mapped on a PMA
> > > > > > - the mapping is typically dependent on considered network
> > > > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> > > networks)
> > > > > >
> > > > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > > > mapping IF all RTP receiver/sender entities would
> be located
> > > > > > in physical IP terminals (UEs)
> > > > > > - etc
> > > > > >
> > > > > > [Qin]: I can understand your point, but you can not do that.
> > > > > > Since this document is only focus on *RTP* monitoring
> > > > > > architecture, that is what it said in AVTCore milestone:
> > > > > > "
> > > > > >
> > > > > > Goals and Milestones:
> > > > > >
> > > > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > > > Informational
> > > > > >
> > > > > > "
> > > > >
> > > > > [ABS] If you go back to my first email on this
> subject, and if
> > > > > you look at my proposal: that's not a lot, nothing which
> > > > > violates the charter, goals and milestones.
> > > > >
> > > > >
> > > > > > Also if you really don't see how to map FMA to PMA, you may
> > > > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > > > As for how to use RTP monitoring architecture or
> RTP XR Report
> > > > > > in the IMS network architecture, you may look at:
> > > > > > http://tools.ietf.org/html/rfc6035
> > > > >
> > > > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > > > primarily for physical IP user equipment with embedded RTP
> > > > > sender/receiver function and SIP UA function.
> > > > > However, the applicability of RFC 6035 is limited for a
> > > > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > > > located NOT in user equipment. Also the P.NAMS
> mid-point model
> > > > > fails for such a scenario.
> > > > >
> > > > > > ITU-T H.248.48.
> > > > > > But I haven't check the current status of H.248.48.
> > > > >
> > > > > [ABS] Work is finalized, see
> > > > > http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-=
1
> > > > > 11121-TD-PLEN-0419
> > > > >
> > > > > >
> > > > > > >
> > > > > > > But as the author of this document, I am
> interested and open
> > > > > > > to other opinions.:-)
> > > > > >
> > > > > > [ABS] Like to add a further aspect: a "functional
> monitoring
> > > > > > architecture" may be considered as a network overlay,
> > > > > > something which adds additional capabilities (here:
> > > > > > measurement services, reporting services on top of
> basic RTP
> > > > > > services).
> > > > > > Such an overlay concept is nothing new: e.g., the
> MultiService
> > > > > > Forum did define a "Performance Measurement & Monitoring
> > > > > > (PMM)" overlay network, or IETF RMON may be also
> considered as
> > > > > > such.
> > > > > >
> > > > > > >
> > > > > > > > Regards,
> > > > > > > > Albrecht
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >> -----Original Message-----
> > > > > > > >> From: avt-bounces@ietf.org
> > [mailto:avt-bounces@ietf.org] On
> > > > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > > > >> To: i-d-announce@ietf.org
> > > > > > > >> Cc: avt@ietf.org
> > > > > > > >> Subject: [AVTCORE] I-D Action:
> > > > > draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> A New Internet-Draft is available from the on-line
> > > > > > > >> Internet-Drafts directories. This draft is a work
> > > item of the
> > > > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > > > of the IETF.
> > > > > > > >>
> > > > > > > >> Title           : Monitoring Architectures for RTP
> > > > > > > >> Author(s)       : Qin Wu
> > > > > > > >>                           Geoff Hunt
> > > > > > > >>                           Philip Arden
> > > > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > > > >> Pages           : 25
> > > > > > > >> Date            : 2011-11-28
> > > > > > > >>
> > > > > > > >>    This memo proposes an architecture for
> > > extending RTCP with
> > > > > > > >> a new RTCP
> > > > > > > >>    XR (RFC3611) block type to report new metrics
> > > > > regarding media
> > > > > > > >>    transmission or reception quality, following RTCP
> > > > guideline
> > > > > > > >>    established in RFC5968.  This memo suggests
> that a new
> > > > > > > block should
> > > > > > > >>    contain a single metric or a small number of metrics
> > > > > > > relevant to a
> > > > > > > >>    single parameter of interest or concern, rather than
> > > > > > > containing a
> > > > > > > >>    number of metrics which attempt to provide
> > full coverage
> > > > > > > >> of all those
> > > > > > > >>    parameters of concern to a specific application.
> > > > > > > Applications may
> > > > > > > >>    then "mix and match" to create a set of
> blocks which
> > > > > > > >> covers their set
> > > > > > > >>    of concerns.  Where possible, a specific
> > block should be
> > > > > > > >> designed to
> > > > > > > >>    be re-usable across more than one application, for
> > > > > > > example, for all
> > > > > > > >>    of voice, streaming audio and video.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> A URL for this Internet-Draft is:
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > > > >>
> > > > > > > >> This Internet-Draft can be retrieved at:
> > > > > > > >>
> > > > > > >
> > > > >
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >> _______________________________________________
> > > > > > > >> Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > > > >>
> > > > > > > > _______________________________________________
> > > > > > > > Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > > > >
> > > > > > =3D
> > > > > _______________________________________________
> > > > > Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > >
> > > >
> > >
> >
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>

--_003_5F7BCCF5541B7444830A2288ABBEBC9621620F5344FRMRSSXCHMBSD_
Content-Type: application/msword;
	name="draft-ietf-avtcore-monarch-08_CommentsAlbrecht.doc"
Content-Description: draft-ietf-avtcore-monarch-08_CommentsAlbrecht.doc
Content-Disposition: attachment;
	filename="draft-ietf-avtcore-monarch-08_CommentsAlbrecht.doc"; size=197120;
	creation-date="Mon, 12 Dec 2011 10:50:38 GMT";
	modification-date="Mon, 12 Dec 2011 10:50:39 GMT"
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAADAAAAfAEAAAAAAAAA
EAAAfgEAAAEAAAD+////AAAAAHkBAAB6AQAAewEAAP//////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s
pcEAJ2AJBAAA8BK/AAAAAAAAEAAAAAAABgAAca4AAA4AYmpiakxVTFUAAAAAAAAAAAAAAAAAAAAA
AAAJBBYANBwBAC4/AQAuPwEAcaYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA
AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAKQAAAAAAGQFAAAAAAAAZAUAAGQF
AAAAAAAAZAUAAAAAAABkBQAAAAAAAGQFAAAAAAAAZAUAABQAAAAAAAAAAAAAAHgFAAAAAAAAgGQB
AAAAAACAZAEAAAAAAIBkAQAAAAAAgGQBABwAAACcZAEAlAEAAHgFAAAAAAAALp0BANIBAAA8ZgEA
AAAAADxmAQAAAAAAPGYBAAAAAAA8ZgEAAAAAADxmAQAAAAAAF2cBAAAAAAAXZwEAAAAAABdnAQAA
AAAAmZwBAAIAAACbnAEAAAAAAJucAQAAAAAAm5wBAAAAAACbnAEAAAAAAJucAQAAAAAAm5wBACQA
AAAAnwEAaAIAAGihAQC0AAAAv5wBABUAAAAAAAAAAAAAAAAAAAAAAAAAZAUAAAAAAAAXZwEAAAAA
AAAAAAAAAAAAAAAAAAAAAAAXZwEAAAAAABdnAQAAAAAAF2cBAAAAAAAXZwEAAAAAAL+cAQAAAAAA
AAAAAAAAAABkBQAAAAAAAGQFAAAAAAAAPGYBAAAAAAAAAAAAAAAAADxmAQDbAAAA1JwBAB4AAABZ
fwEAAAAAAFl/AQAAAAAAWX8BAAAAAAAXZwEA+gMAAGQFAAAAAAAAPGYBAAAAAABkBQAAAAAAADxm
AQAAAAAAmZwBAAAAAAAAAAAAAAAAAFl/AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAF2cBAAAAAACZnAEAAAAAAAAAAAAAAAAAWX8BAAAAAABZfwEA
OgAAACWFAQBAAAAAZAUAAAAAAABkBQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAeYUBAAAAAAA8ZgEAAAAAADBmAQAMAAAAYFzw4ru4
zAEAAAAAAAAAAIBkAQAAAAAAEWsBACYUAABlhQEACgAAAAAAAAAAAAAAmZwBAAAAAADynAEAPAAA
AC6dAQAAAAAAb4UBAAoAAAAcogEAAAAAADd/AQAiAAAAHKIBABQAAAB5hQEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAByiAQAAAAAAAAAAAAAAAABkBQAAAAAAAHmFAQAgFwAAF2cBAAAAAAAXZwEAAAAAAFl/
AQAAAAAAF2cBAAAAAAAXZwEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF2cB
AAAAAAAXZwEAAAAAABdnAQAAAAAAv5wBAAAAAAC/nAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAWX8BAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABdnAQAA
AAAAF2cBAAAAAAAXZwEAAAAAAC6dAQAAAAAAF2cBAAAAAAAXZwEAAAAAABdnAQAAAAAAF2cBAAAA
AAAAAAAAAAAAAHgFAAAAAAAAeAUAAAAAAAB4BQAAZK8AANy0AACkrwAAeAUAAAAAAAB4BQAAAAAA
AHgFAAAAAAAA3LQAAAAAAAB4BQAAAAAAAHgFAAAAAAAAeAUAAAAAAABkBQAAAAAAAGQFAAAAAAAA
ZAUAAAAAAABkBQAAAAAAAGQFAAAAAAAAZAUAAAAAAAD/////AAAAAAIADAEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0NDUF1
ZGlvL1ZpZGVvIFRyYW5zcG9ydCBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAg
ICAgUS4gV3UsIEVkLg1JbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBIdWF3ZWkNSW50ZW5kZWQgc3RhdHVzOiBJbmZvcm1hdGlv
bmFsICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBHLiBIdW50DUV4cGlyZXM6IEp1
bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFVuYWZmaWxp
YXRlZA0gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgUC4gQXJkZW4NICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEJUDSAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBOb3ZlbWJlciAyOSwgMjAxMQ0NDSAg
ICAgICAgICAgICAgICAgICAgTW9uaXRvcmluZyBBcmNoaXRlY3R1cmVzIGZvciBSVFANICAgICAg
ICAgICAgICAgICAgIGRyYWZ0LWlldGYtYXZ0Y29yZS1tb25hcmNoLTA4LnR4dA0NQWJzdHJhY3QN
DSAgIFRoaXMgbWVtbyBwcm9wb3NlcyBhbiBhcmNoaXRlY3R1cmUgZm9yIGV4dGVuZGluZyBSVENQ
IHdpdGggYSBuZXcgUlRDUA0gICBYUiAoUkZDMzYxMSkgYmxvY2sgdHlwZSB0byByZXBvcnQgbmV3
IG1ldHJpY3MgcmVnYXJkaW5nIG1lZGlhDSAgIHRyYW5zbWlzc2lvbiBvciByZWNlcHRpb24gcXVh
bGl0eSwgZm9sbG93aW5nIFJUQ1AgZ3VpZGVsaW5lDSAgIGVzdGFibGlzaGVkIGluIFJGQzU5Njgu
ICBUaGlzIG1lbW8gc3VnZ2VzdHMgdGhhdCBhIG5ldyBibG9jayBzaG91bGQNICAgY29udGFpbiBh
IHNpbmdsZSBtZXRyaWMgb3IgYSBzbWFsbCBudW1iZXIgb2YgbWV0cmljcyByZWxldmFudCB0byBh
DSAgIHNpbmdsZSBwYXJhbWV0ZXIgb2YgaW50ZXJlc3Qgb3IgY29uY2VybiwgcmF0aGVyIHRoYW4g
Y29udGFpbmluZyBhDSAgIG51bWJlciBvZiBtZXRyaWNzIHdoaWNoIGF0dGVtcHQgdG8gcHJvdmlk
ZSBmdWxsIGNvdmVyYWdlIG9mIGFsbCB0aG9zZQ0gICBwYXJhbWV0ZXJzIG9mIGNvbmNlcm4gdG8g
YSBzcGVjaWZpYyBhcHBsaWNhdGlvbi4gIEFwcGxpY2F0aW9ucyBtYXkNICAgdGhlbiAibWl4IGFu
ZCBtYXRjaCIgdG8gY3JlYXRlIGEgc2V0IG9mIGJsb2NrcyB3aGljaCBjb3ZlcnMgdGhlaXIgc2V0
DSAgIG9mIGNvbmNlcm5zLiAgV2hlcmUgcG9zc2libGUsIGEgc3BlY2lmaWMgYmxvY2sgc2hvdWxk
IGJlIGRlc2lnbmVkIHRvDSAgIGJlIHJlLXVzYWJsZSBhY3Jvc3MgbW9yZSB0aGFuIG9uZSBhcHBs
aWNhdGlvbiwgZm9yIGV4YW1wbGUsIGZvciBhbGwNICAgb2Ygdm9pY2UsIHN0cmVhbWluZyBhdWRp
byBhbmQgdmlkZW8uDQ1TdGF0dXMgb2YgdGhpcyBNZW1vDQ0gICBUaGlzIEludGVybmV0LURyYWZ0
IGlzIHN1Ym1pdHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlDSAgIHByb3Zpc2lvbnMg
b2YgQkNQIDc4IGFuZCBCQ1AgNzkuDQ0gICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9j
dW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0gICBUYXNrIEZvcmNlIChJRVRGKS4g
IE5vdGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZQ0gICB3b3JraW5nIGRv
Y3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBUaGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0
LQ0gICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RyYWZ0cy9jdXJy
ZW50Ly4NDSAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBh
IG1heGltdW0gb2Ygc2l4IG1vbnRocw0gICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBv
ciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0gICB0aW1lLiAgSXQgaXMgaW5h
cHByb3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZQ0gICBtYXRlcmlh
bCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iDQ0gICBU
aGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIEp1bmUgMSwgMjAxMi4NDUNvcHlyaWdo
dCBOb3RpY2UNDSAgIENvcHlyaWdodCAoYykgMjAxMSBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29u
cyBpZGVudGlmaWVkIGFzIHRoZQ0gICBkb2N1bWVudCBhdXRob3JzLiAgQWxsIHJpZ2h0cyByZXNl
cnZlZC4NDQ0NV3UsIGV0IGFsLiAgICAgICAgICAgICAgICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAg
ICAgICAgICAgICAgICAgIFtQYWdlIDFdDQwNSW50ZXJuZXQtRHJhZnQgICAgICAgIFJUUCBNb25p
dG9yaW5nIEFyY2hpdGVjdHVyZXMgICAgICAgICBOb3ZlbWJlciAyMDExDQ0NICAgVGhpcyBkb2N1
bWVudCBpcyBzdWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbA0gICBQ
cm92aXNpb25zIFJlbGF0aW5nIHRvIElFVEYgRG9jdW1lbnRzDSAgIChodHRwOi8vdHJ1c3RlZS5p
ZXRmLm9yZy9saWNlbnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZg0gICBwdWJsaWNh
dGlvbiBvZiB0aGlzIGRvY3VtZW50LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMNICAg
Y2FyZWZ1bGx5LCBhcyB0aGV5IGRlc2NyaWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0cmljdGlvbnMg
d2l0aCByZXNwZWN0DSAgIHRvIHRoaXMgZG9jdW1lbnQuICBDb2RlIENvbXBvbmVudHMgZXh0cmFj
dGVkIGZyb20gdGhpcyBkb2N1bWVudCBtdXN0DSAgIGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGlj
ZW5zZSB0ZXh0IGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDQuZSBvZg0gICB0aGUgVHJ1c3QgTGVn
YWwgUHJvdmlzaW9ucyBhbmQgYXJlIHByb3ZpZGVkIHdpdGhvdXQgd2FycmFudHkgYXMNICAgZGVz
Y3JpYmVkIGluIHRoZSBTaW1wbGlmaWVkIEJTRCBMaWNlbnNlLg0NDVRhYmxlIG9mIENvbnRlbnRz
DQ0gICAxLiAgSW50cm9kdWN0aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gIDMNICAgMi4gIFJlcXVpcmVtZW50cyBub3RhdGlvbiAgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA0DSAgIDMuICBSVFAgbW9uaXRvcmluZyBh
cmNoaXRlY3R1cmUgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNg0gICAgIDMu
MS4gIFJUQ1AgTWV0cmljIEJsb2NrIFJlcG9ydCBhbmQgYXNzb2NpYXRlZCBwYXJhbWV0ZXJzIC4g
LiAuIC4gIDgNICAgNC4gIElzc3VlcyB3aXRoIHJlcG9ydGluZyBtZXRyaWMgYmxvY2sgdXNpbmcg
UlRDUCBYUiBleHRlbnNpb24gLiAuIDEwDSAgIDUuICBHdWlkZWxpbmUgZm9yIHJlcG9ydGluZyBt
ZXRyaWMgYmxvY2sgdXNpbmcgUlRDUCBYUiAuIC4gLiAuIC4gLiAxMg0gICAgIDUuMS4gIFVzaW5n
IHNpbmdsZSBtZXRyaWNzIGJsb2NrcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTIN
ICAgICA1LjIuICBDb3JyZWxhdGluZyBSVENQIFhSIHdpdGggdGhlIG5vbi1SVFAgZGF0YSAgLiAu
IC4gLiAuIC4gLiAuIDEyDSAgICAgNS4zLiAgUmVkdWNpbmcgTWVhc3VyZW1lbnQgaW5mb3JtYXRp
b24gcmVwZXRpdGlvbiAgLiAuIC4gLiAuIC4gLiAxMw0gICAgIDUuNC4gIEV4cGFuZGluZyB0aGUg
UlRDUCBYUiBibG9jayBuYW1lc3BhY2UgIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTMNICAgNi4gIEFu
IGV4YW1wbGUgb2YgYSBtZXRyaWMgYmxvY2sgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIDE0DSAgIDcuICBBcHBsaWNhdGlvbiB0byBSRkMgNTExNyB0b3BvbG9naWVzIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAxNQ0gICAgIDcuMS4gIEFwcGxpY2FiaWxpdHkgdG8gTUNVIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTUNICAgICA3LjIuICBBcHBsaWNh
YmlsaXR5IHRvIFRyYW5zbGF0b3JzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE2DSAg
IDguICBJQU5BIENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAxNw0gICA5LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTgNICAgMTAuIEFja25vd2xlZGdlbWVudCAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE5DSAgIDExLiBJbmZv
cm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAyMA0gICBBcHBlbmRpeCBBLiAgQ2hhbmdlIExvZyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gMjINICAgICBBLjEuICBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJj
aC0wMCAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDIyDSAgICAgQS4yLiAgZHJhZnQtaWV0
Zi1hdnRjb3JlLW1vbmFyY2gtMDEgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAyMg0gICAg
IEEuMy4gIGRyYWZ0LWlldGYtYXZ0Y29yZS1tb25hcmNoLTAyICAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gMjINICAgICBBLjQuICBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wMyAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDIzDSAgICAgQS41LiAgZHJhZnQtaWV0Zi1hdnRjb3Jl
LW1vbmFyY2gtMDQgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAyMw0gICAgIEEuNi4gIGRy
YWZ0LWlldGYtYXZ0Y29yZS1tb25hcmNoLTA1ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
MjMNICAgICBBLjcuICBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wNiAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIDI0DSAgICAgQS44LiAgZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gt
MDcgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAyNA0gICBBdXRob3JzJyBBZGRyZXNzZXMg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjUNDQ0NDQ0N
DQ0NDVd1LCBldCBhbC4gICAgICAgICAgICAgICAgRXhwaXJlcyBKdW5lIDEsIDIwMTIgICAgICAg
ICAgICAgICAgICBbUGFnZSAyXQ0MDUludGVybmV0LURyYWZ0ICAgICAgICBSVFAgTW9uaXRvcmlu
ZyBBcmNoaXRlY3R1cmVzICAgICAgICAgTm92ZW1iZXIgMjAxMQ0NDTEuICBJbnRyb2R1Y3Rpb24N
DSAgIEFzIG1vcmUgdXNlcnMgYW5kIHN1YnNjcmliZXJzIHJlbHkgb24gcmVhbCB0aW1lIGFwcGxp
Y2F0aW9uIHNlcnZpY2VzLA0gICB1bmNlcnRhaW50aWVzIGluIHRoZSBwZXJmb3JtYW5jZSBhbmQg
YXZhaWxhYmlsaXR5IG9mIHRoZXNlIHNlcnZpY2VzDSAgIGFyZSBkcml2aW5nIHRoZSBuZWVkIHRv
IHN1cHBvcnQgbmV3IHN0YW5kYXJkIG1ldGhvZHMgZm9yIGdhdGhlcmluZw0gICBwZXJmb3JtYW5j
ZSBtZXRyaWNzIGZyb20gUlRQIGFwcGxpY2F0aW9ucy4gIFRoZXNlIHJhcGlkbHkgZW1lcmdpbmcN
ICAgc3RhbmRhcmRzLCBzdWNoIGFzIFJUQ1AgWFIgW1JGQzM2MTFdIGFuZCBvdGhlciBSVENQIGV4
dGVuc2lvbiB0bw0gICBTZW5kZXIgUmVwb3J0cyAoU1IpLCBSZWNlaXZlciBSZXBvcnRzIChSUikg
W1JGQzM1NTBdIGFyZSBiZWluZw0gICBkZXZlbG9wZWQgZm9yIHRoZSBwdXJwb3NlIG9mIGNvbGxl
Y3RpbmcgYW5kIHJlcG9ydGluZyBwZXJmb3JtYW5jZQ0gICBtZXRyaWNzIGZyb20gZW5kcG9pbnQg
ZGV2aWNlcyB0aGF0IGNhbiBiZSB1c2VkIHRvIGNvcnJlbGF0ZSB0aGUNICAgbWV0cmljcywgcHJv
dmlkZSBlbmQgdG8gZW5kIHNlcnZpY2UgdmlzaWJpbGl0eSBhbmQgbWVhc3VyZSBhbmQNICAgbW9u
aXRvciBRdWFsaXR5IG9mIEV4cGVyaWVuY2UgKFFvRSkuDQ0gICBIb3dldmVyIHRoZSBwcm9saWZl
cmF0aW9uIG9mIFJUUC9SVENQIHNwZWNpZmljIG1ldHJpY3MgZm9yIHRyYW5zcG9ydA0gICBhbmQg
YXBwbGljYXRpb24gcXVhbGl0eSBtb25pdG9yaW5nIGhhcyBiZWVuIGlkZW50aWZpZWQgYXMgYSBw
b3RlbnRpYWwNICAgcHJvYmxlbSBmb3IgUlRQL1JUQ1AgaW50ZXJvcGVyYWJpbGl0eSwgd2hpY2gg
YXR0ZW1wdCB0byBwcm92aWRlIGZ1bGwNICAgY292ZXJhZ2Ugb2YgYWxsIHRob3NlIHBhcmFtZXRl
cnMgb2YgY29uY2VybiB0byBhIHNwZWNpZmljDSAgIGFwcGxpY2F0aW9uLiAgU2luY2UgZGlmZmVy
ZW50IGFwcGxpY2F0aW9ucyBsYXllcmVkIG9uIFJUUCBtYXkgaGF2ZQ0gICBzb21lIG1vbml0b3Jp
bmcgcmVxdWlyZW1lbnRzIGluIGNvbW1vbiwgdGhlcmVmb3JlIHRoZXNlIG1ldHJpY3MNICAgc2hv
dWxkIGJlIHNhdGlzZmllZCBieSBhIGNvbW1vbiBkZXNpZ24uDQ0gICBUaGUgb2JqZWN0aXZlIG9m
IHRoaXMgZG9jdW1lbnQgaXMgdG8gZGVmaW5lIGFuIGV4dGVuc2libGUgUlRQDSAgIG1vbml0b3Jp
bmcgZnJhbWV3b3JrIHRvIHByb3ZpZGUgYSBzbWFsbCBudW1iZXIgb2YgcmUtdXNhYmxlIFF1YWxp
dHkNICAgb2YgU2VydmljZSAoUW9TKS9Rb0UgbWV0cmljcyB3aGljaCBmYWNpbGl0YXRlIHJlZHVj
ZWQgaW1wbGVtZW50YXRpb24NICAgY29zdHMgYW5kIGhlbHAgbWF4aW1pemUgaW50ZXItb3BlcmFi
aWxpdHkuICBSVENQIEd1aWRlbGluZSBbUkZDNTk2OF0NICAgaGFzIHN0YXRlZCB0aGF0LCB3aGVy
ZSBSVENQIGlzIHRvIGJlIGV4dGVuZGVkIHdpdGggYSBuZXcgbWV0cmljLCB0aGUNICAgcHJlZmVy
cmVkIG1lY2hhbmlzbSBpcyBieSB0aGUgYWRkaXRpb24gb2YgYSBuZXcgUlRDUCBYUiBbUkZDMzYx
MV0NICAgYmxvY2suICBUaGlzIG1lbW8gYXNzdW1lcyB0aGF0IGFueSByZXF1aXJlbWVudCBmb3Ig
YSBuZXcgbWV0cmljIHRvIGJlDSAgIHRyYW5zcG9ydGVkIGluIFJUQ1Agd2lsbCB1c2UgYSBuZXcg
UlRDUCBYUiBibG9jay4NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDVd1LCBldCBhbC4gICAgICAgICAg
ICAgICAgRXhwaXJlcyBKdW5lIDEsIDIwMTIgICAgICAgICAgICAgICAgICBbUGFnZSAzXQ0MDUlu
dGVybmV0LURyYWZ0ICAgICAgICBSVFAgTW9uaXRvcmluZyBBcmNoaXRlY3R1cmVzICAgICAgICAg
Tm92ZW1iZXIgMjAxMQ0NDTIuICBSZXF1aXJlbWVudHMgbm90YXRpb24NDSAgIFRoaXMgbWVtbyBp
cyBpbmZvcm1hdGl2ZSBhbmQgYXMgc3VjaCBjb250YWlucyBubyBub3JtYXRpdmUNICAgcmVxdWly
ZW1lbnRzLg0NICAgSW4gYWRkaXRpb24sIHRoZSBmb2xsb3dpbmcgdGVybXMgYXJlIGRlZmluZWQ6
DQ0gICBUcmFuc3BvcnQgbGV2ZWwgbWV0cmljcw0NICAgICAgQSBzZXQgb2YgbWV0cmljcyB3aGlj
aCBjaGFyYWN0ZXJpc2UgdGhlIHRocmVlIHRyYW5zcG9ydA0gICAgICBpbXBhaXJtZW50cyBvZiBw
YWNrZXQgbG9zcywgcGFja2V0IGRlbGF5LCBhbmQgcGFja2V0IGRlbGF5DSAgICAgIHZhcmlhdGlv
bi4gIFRoZXNlIG1ldHJpY3Mgc2hvdWxkIGJlIHVzYWJsZSBieSBhbnkgYXBwbGljYXRpb24NICAg
ICAgd2hpY2ggdXNlcyBSVFAgdHJhbnNwb3J0Lg0NDSAgIEFwcGxpY2F0aW9uIGxldmVsIG1ldHJp
Y3MNDSAgICAgIE1ldHJpY3MgcmVsYXRpbmcgdG8gUW9FIHJlbGF0ZWQgcGFyYW1ldGVycy4gIFRo
ZXNlIG1ldHJpY3MgYXJlDSAgICAgIG1lYXN1cmVkIGF0IHRoZSBhcHBsaWNhdGlvbiBsZXZlbCBh
bmQgZm9jdXMgb24gcXVhbGl0eSBvZiBjb250ZW50DSAgICAgIHJhdGhlciB0aGFuIG5ldHdvcmsg
cGFyYW1ldGVycy4gIE9uZSBleGFtcGxlIG9mIHN1Y2ggbWV0cmljcyBpcw0gICAgICB0aGUgUW9F
IE1ldHJpYyBzcGVjaWZpZWQgaW4gUW9FIG1ldHJpYyByZXBvcnRpbmcgQmxvY2sgW01RXS4NDQ0g
ICBFbmQgU3lzdGVtIG1ldHJpY3MNDSAgICAgIE1ldHJpY3MgcmVsYXRpbmcgdG8gdGhlIHdheSBh
IHRlcm1pbmFsIGRlYWxzIHdpdGggdHJhbnNwb3J0DSAgICAgIGltcGFpcm1lbnRzIGFmZmVjdGlu
ZyB0aGUgaW5jaWRlbnQgUlRQIHN0cmVhbS4gIFRoZXNlIG1heSBpbmNsdWRlDSAgICAgIGRlLWpp
dHRlciBidWZmZXJpbmcsIHBhY2tldCBsb3NzIGNvbmNlYWxtZW50LCBhbmQgdGhlIHVzZSBvZg0g
ICAgICByZWR1bmRhbnQgc3RyZWFtcyAoaWYgYW55KSBmb3IgY29ycmVjdGlvbiBvZiBlcnJvciBv
ciBsb3NzLg0NDSAgIERpcmVjdCBtZXRyaWNzDQ0gICAgICBNZXRyaWNzIHRoYXQgY2FuIGJlIGRp
cmVjdGx5IG1lYXN1cmVkIG9yIGNhbGN1bGF0ZWQgYW5kIGFyZSBub3QNICAgICAgZGVwZW5kZW50
IG9uIG90aGVyIG1ldHJpYy4NDQ0gICBDb21wb3NlZCBtZXRyaWNzDQ0gICAgICBNZXRyaWNzIHRo
YXQgYXJlIGNhbGN1bGF0ZWQgYmFzZWQgb24gZGlyZWN0IG1ldHJpYyBvciBjb21iaW5hdGlvbg0g
ICAgICBvZiBkaXJlY3QgbWV0cmljIGFuZCBkZXJpdmVkIG1ldHJpY3MuDQ0NICAgSW50ZXJ2YWwg
bWV0cmljcw0NICAgICAgSXQgaXMgcmVmZXJyZWQgdG8gYXMgdGhlIG1ldHJpY3Mgb2Ygd2hpY2gg
dGhlIHJlcG9ydGVkIHZhbHVlcw0gICAgICBhcHBseSB0byB0aGUgbW9zdCByZWNlbnQgbWVhc3Vy
ZW1lbnQgaW50ZXJ2YWwgZHVyYXRpb24gYmV0d2Vlbg0gICAgICBzdWNjZXNzaXZlIG1ldHJpY3Mg
cmVwb3J0cw0NDQ1XdSwgZXQgYWwuICAgICAgICAgICAgICAgIEV4cGlyZXMgSnVuZSAxLCAyMDEy
ICAgICAgICAgICAgICAgICAgW1BhZ2UgNF0NDA1JbnRlcm5ldC1EcmFmdCAgICAgICAgUlRQIE1v
bml0b3JpbmcgQXJjaGl0ZWN0dXJlcyAgICAgICAgIE5vdmVtYmVyIDIwMTENDQ0gICBDdW11bGF0
aXZlIG1ldHJpY3MNDSAgICAgIEl0IGlzIHJlZmVycmVkIHRvIGFzIHRoZSBtZXRyaWNzIG9mIHdo
aWNoIHRoZSByZXBvcnRlZCB2YWx1ZXMNICAgICAgYXBwbHkgdG8gdGhlIGFjY3VtdWxhdGlvbiBw
ZXJpb2QgY2hhcmFjdGVyaXN0aWMgb2YgY3VtdWxhdGl2ZQ0gICAgICBtZWFzdXJlbWVudHMNDQ0g
ICBTYW1wbGVkIG1ldHJpY3MNDSAgICAgIEl0IGlzIHJlZmVycmVkIHRvIGFzIHRoZSBtZXRyaWNz
IG9mIHdoaWNoIHRoZSByZXBvcnRlZCB2YWx1ZXMgb25seQ0gICAgICBhcHBseSB0byB0aGUgdmFs
dWUgb2YgYSBjb250aW51b3VzbHkgbWVhc3VyZWQgb3IgY2FsY3VsYXRlZCB0aGF0DSAgICAgIGhh
cyBiZWVuIHNhbXBsZWQgYXQgZW5kIG9mIHRoZSBpbnRlcnZhbC4NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0N
DQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NV3UsIGV0IGFsLiAgICAgICAgICAgICAgICBFeHBpcmVzIEp1
bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgIFtQYWdlIDVdDQwNSW50ZXJuZXQtRHJhZnQgICAg
ICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVjdHVyZXMgICAgICAgICBOb3ZlbWJlciAyMDExDQ0N
My4gIFJUUCBtb25pdG9yaW5nIGFyY2hpdGVjdHVyZQ0zLjEuICBCYXNpYyBwcmluY2lwbGVzDQ0g
ICBUaGUgUlRQIG1vbml0b3JpbmcgYXJjaGl0ZWN0dXJlIGNvbXByaXNlcyB0aGUgZm9sbG93aW5n
IHR3byBrZXkNICAgZnVuY3Rpb25hbCBjb21wb25lbnRzIHNob3duIGJlbG93Og0NICAgbyAgTW9u
aXRvcg0NICAgbyAgTWV0cmljIEJsb2NrIFN0cnVjdHVyZQ0NICAgTW9uaXRvciBpcyB0aGUgZnVu
Y3Rpb25hbCBjb21wb25lbnQgZGVmaW5lZCBpbiB0aGUgUmVhbC10aW1lDSAgIFRyYW5zcG9ydCBQ
cm90b2NvbCAoUlRQKSBbUkZDMzU1MF0gdGhhdCBhY3RzIGFzIGEgc291cmNlIG9mDSAgIGluZm9y
bWF0aW9uIGdhdGhlcmVkIGZvciBtb25pdG9yaW5nIHB1cnBvc2VzLiAgSXQgbWF5IGdhdGhlciBz
dWNoDSAgIGluZm9ybWF0aW9uIHJlcG9ydGVkIGJ5IFJUQ1AgWFIgb3Igb3RoZXIgUlRDUCBleHRl
bnNpb24gYW5kIGNhbGN1bGF0ZQ0gICBzdGF0aXN0aWNzIGZyb20gbXVsdGlwbGUgc291cmNlLiAg
QWNjb3JkaW5nIHRvIHRoZSBkZWZpbml0aW9uIG9mDSAgIG1vbml0b3IgaW4gdGhlIFJUUCBQcm90
b2NvbCBbUkZDMzU1MF0sIHRoZSBlbmQgc3lzdGVtIHRoYXQgc291cmNlIFJUUA0gICBzdHJlYW1z
LCBhbiBpbnRlcm1lZGlhdGUtc3lzdGVtIHRoYXQgZm9yd2FyZHMgUlRQIHBhY2tldHMgdG8gRW5k
LQ0gICBkZXZpY2VzIG9yIGEgdGhpcmQgcGFydHkgdGhhdCBkb2VzIG5vdCBwYXJ0aWNpcGF0ZSBp
biB0aGUgUlRQIHNlc3Npb24NICAgKGkuZS4sIHRoZSB0aGlyZCBwYXJ0eSBtb25pdG9yIGRlcGlj
dGVkIGluIGZpZ3VyZSAxKSBjYW4gYmUNICAgZW52aXNpb25lZCB0byBhY3QgYXMgdGhlIE1vbml0
b3Igd2l0aGluIHRoZSBSVFAgbW9uaXRvcmluZw0gICBhcmNoaXRlY3R1cmUuDQ0gICBUaGUgTWV0
cmljIEJsb2NrIGV4cG9zZXMgcmVhbCB0aW1lIEFwcGxpY2F0aW9uIFFvUy9Rb0UgbWV0cmljDSAg
IGluZm9ybWF0aW9uIGluIHRoZSBhcHByb3ByaWF0ZSByZXBvcnQgYmxvY2sgZm9ybWF0IHRvIHRo
ZSBtYW5hZ2VtZW50DSAgIHN5c3RlbSB3aXRoaW4gdGhlIFJUUCBtb25pdG9yaW5nIGFyY2hpdGVj
dHVyZS4gIFN1Y2ggaW5mb3JtYXRpb24gY2FuDSAgIGJlIGZvcm11bGF0ZWQgYXM6DQ0gICBvICBU
aGUgZGlyZWN0IG1ldHJpY3MNDSAgIG8gIG9yIHRoZSBjb21wb3NlZCBtZXRyaWNzLg0NICAgb3Ig
Zm9ybXVsYXRlZCBhcw0NICAgbyAgVGhlIEludGVydmFsIG1ldHJpY3MNDSAgIG8gIG9yIGN1bXVs
YXRpdmUgbWV0cmljcw0NICAgbyAgb3Igc2FtcGxlZCBtZXRyaWNzLg0NICAgQm90aCB0aGUgUlRD
UCBvciBSVENQIFhSIGNhbiBiZSBleHRlbmRlZCB0byBjb252ZXkgdGhlc2UgbWV0cmljcy4NICAg
VGhlIGRldGFpbHMgb24gdHJhbnNwb3J0IHByb3RvY29scyBmb3IgbWV0cmljIGJsb2NrcyBhcmUg
ZGVzY3JpYmVkIGluDSAgIFNlY3Rpb24gMy4xLg0NDQ0NDQ0NDQ0NV3UsIGV0IGFsLiAgICAgICAg
ICAgICAgICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgIFtQYWdlIDZdDQwN
SW50ZXJuZXQtRHJhZnQgICAgICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVjdHVyZXMgICAgICAg
ICBOb3ZlbWJlciAyMDExDQ0NICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tLS0tKw0g
ICAgICAgICAgICAgICAgfCBSVFAgU2VuZGVyICAgICAgICB8ICAgICAgICAgICAgICArLS0tLS0t
LS0tLSsNICAgICAgICAgICAgICAgIHwgICArLS0tLS0tLS0tLS0rICAgfCAgICAgICAgICAgICAg
fE1hbmFnZW1lbnR8DSAgIC0tLS0tLS0tLS0tLS0tLS0+fCAgTW9uaXRvciAgfC0tLS0tLS0tLTUt
LS0tLS0tPnwgIFN5c3RlbSAgfA0gICB8ICAgICAgICAgICAgfCAgIHwgICAgICAgICAgIHwgICB8
ICAgICAgICAgICAgICB8ICAgICAgICAgIHwNICAgfCAgICAgICAgICAgIHwgICArLS0tLS0tLS0t
LS0rICAgfCAgICAgICAgICAgICAgKy0tLS0tLS0tLS0rDSAgIHwgICAgICAgICAgICB8Ky0tLS0t
LS0tLS0tLS0tLS0tK3wNICAgfCAgICAgICAgICAgIHx8QXBwbGljYXRpb24gICAgICB8fCAgICAt
LS0tLS0tLS0tLS0tLXwNICAgfCAgICAgICAgICAgIHx8LVN0cmVhbWluZyB2aWRlbyB8fCAgICB8
ICAgICAgICAgICAgIHwNICAgfCAgIHwtLS0tLS0tLS18LVZPSVAgICAgICAgICAgICB8fCAgICB8
ICAgICstLS0tLS0tLVYtLS0tLS0rDSAgIHwgICB8ICAgICAgICB8fC1WaWRlbyBjb25mZXJlbmNl
fHwgICAgLS0tLS0tICBUaGlyZCBQYXJ0eSAgfA0gICB8ICAgfCAgICAgICAgfHwtVGVsZXByZXNl
bmNlICAgIHx8ICAgICAgICAgfCAgICBNb25pdG9yICAgIHwNICAgfCAgIHwgICAgICAgIHx8LUFk
IGluc2VydGlvbiAgICB8fCAgICAgICAgICstLS0tLS0tLS0tLS0tLS0rDSAgIDUgICB8ICAgICAg
ICB8Ky0tLS0tLS0tLS0tLS0tLS0tK3wNICAgfCAgIHwgICAgICAgICstLS0tLS0tLS0tLS0tLS0t
LS0tKw0gICB8ICAgMQ0gICB8ICAgfCArSW50ZXJtZWRpYXRlLS0tLS0tLS0tLS0tKyAgICAgICAg
IHwtLS0tLS0tLS0tLS0tLSAtLS0tIC0tLS0rDSAgIHwgICB8IHwgUlRQIFN5c3RlbSAgICAgICBS
ZXBvcnQgQmxvY2sgICAgfCBSVFAgUmVjZWl2ZXIgPi0tNC18ICAgIHwNICAgfCAgIHwgfCAgICAg
ICstLS0tLS0tLS0tIHRyYW5zcG9ydGVkIG92ZXJ8ICAgICstLS0tLS0tLS0tLSsgIHwgICAgfA0g
ICB8ICAgfCB8ICAgICAgfCAgICAgICAgICAgUlRDUCBleHRlbnNpb24gIHwgICAgfCAgTW9uaXRv
ciAgfDwtLSAgICB8DSAgIHwtLS0tLS0tLS0tLS0tICBNb25pdG9yIHw8LS0tLS0tLS01LS0tLS0t
fC0tLS18ICAgICAgICAgICB8PC0tLS0tLXwNICAgICAgIHwgfCAgICAgIHwgICAgICAgICAgfCAg
IFJlcG9ydCBCbG9jayAgICAgICstLS0tLy0tLS0tLSsgICAgICB8fA0gICAgICAgfCB8ICAgICAg
Ky0tLS0tLS0tLS0rICAgdHJhbnNwb3J0ZWQgb3ZlciAgICAgICB8ICAgICAgICAgICAgIHx8DSAg
ICAgICB8IHwgICAgICAgICAgICAgICAgICAgICBSVENQIFhSICAgICAgfCAgICAgICAgIHwyICAg
ICAgICAgICAgfHwNICAgICAgIHwgfCArLS0tLS0tLS0tLS0tLS0tLS0rICAgIHwgICAgICAgICB8
ICstLS0tLS0tLy0tLS0tLS0tLSsgICB8fA0gICAgICAgfCB8IHxBcHBsaWNhdGlvbiAgICAgIHwg
ICAgfCAgICAgICAgIHwgfEFwcGxpY2F0aW9uICAgICAgfCAgIHx8DSAgICAgICB8IHwgfC1TdHJl
YW1pbmcgdmlkZW8gfCAgICB8ICAgICAgICAgfCB8LVN0cmVhbWluZyB2aWRlbyB8ICAgfHwNICAg
ICAgIHwgfCB8LVZPSVAgICAgICAgICAgICB8ICAgIHwgICAgMSAgICB8IHwtVk9JUCAgICAgICAg
ICAgIHwgICAzfA0gICAgICAgLS0tLT4tVmlkZW8gY29uZmVyZW5jZXwtLS0tLS0tLS0tLS0tLS0+
fC1WaWRlbyBjb25mZXJlbmNlICAgIHx8DSAgICAgICAgIHwgfC1UZWxlcHJlc2VuY2UgICAgfCAg
ICB8ICAgICAgICAgfCB8LVRlbGVwcmVzZW5jZSAgICB8ICAgfHwNICAgICAgICAgfCB8LUFkIGlu
c2VydGlvbiAgICB8ICAgIHwgICAgICAgICB8IHwtQWQgaW5zZXJ0aW9uICAgIHwgICB8fA0gICAg
ICAgICB8ICstLS0tLS0tLS0tLS0tLS0tLSsgICAgfCAgICAgICAgIHwgKy0tLS0tLS0tLS0tLS0t
LS0tKyAgIHx8DSAgICAgICAgIHwgKy0tLS0tLS0tLS0tLS0tLS0tKyAgICB8ICAgICAgICAgfCAr
LS0tLS0tLS0tLS0tLS0tLS0rICAgfHwNICAgICAgICAgfCB8VHJhbnNwb3J0ICAgICAgICB8ICAg
IHwgICAgICAgICB8IHxUcmFuc3BvcnQgICAgICAgIHwgICB8fA0gICAgICAgICB8IHwtSVAvVURQ
L1JUUCAgICAgIHwgICAgfCAgICAgICAgIHwgfC1JUC9VRFAvUlRQICAgICAgPi0tLXx8DSAgICAg
ICAgIHwgfC1JUC9UQ1AvUlRQICAgICAgfCAgICB8ICAgICAgICAgfCB8IC1JUC9UQ1AvUlRQICAg
ICB8ICAgIHwNICAgICAgICAgfCB8LUlQL1RDUC9SVFNQL1JUUCB8ICAgIHwgICAgICAgICB8IHwt
SVAvVENQL1JUU1AvUlRQIHwgICAgfA0gICAgICAgICB8ICstLS0tLS0tLS0tLS0tLS0tLSsgICAg
fCAgICAgICAgIHwgKy0tLS0tLS0tLS0tLS0tLS0tKyAgICB8DSAgICAgICAgICstLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0rICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNDSAgICAg
ICAgICAgICAgICAgICBGaWd1cmUgMTogUlRQIE1vbml0b3JpbmcgQXJjaGl0ZWN0dXJlDQ0gICAx
LiAgUlRQIGNvbW11bmljYXRpb24gYmV0d2VlbiByZWFsIHRpbWUgYXBwbGljYXRpb25zLg0NICAg
Mi4gIEFwcGxpY2F0aW9uIGxldmVsIG1ldHJpY3MgY29sbGVjdGlvbi4NDSAgIDMuICBUcmFuc3Bv
cnQgbGV2ZWwgbWV0cmljcyBjb2xsZWN0aW9uLg0NDQ0NV3UsIGV0IGFsLiAgICAgICAgICAgICAg
ICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgIFtQYWdlIDddDQwNSW50ZXJu
ZXQtRHJhZnQgICAgICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVjdHVyZXMgICAgICAgICBOb3Zl
bWJlciAyMDExDQ0NICAgNC4gIEVuZCBTeXN0ZW0gbWV0cmljcyBjb2xsZWN0aW9uLg0NICAgNS4g
IFJlcG9ydGluZyBTZXNzaW9uLSBtZXRyaWNzIHRyYW5zbWl0dGVkIG92ZXIgc3BlY2lmaWVkIGlu
dGVyZmFjZXMuDQ0zLjIxLiAgUlRDUCBNZXRyaWMgQmxvY2sgUmVwb3J0IGFuZCBhc3NvY2lhdGVk
IHBhcmFtZXRlcnMNDSAgIFRoZSBiYXNpYyBSVENQIFJlY2VwdGlvbiBSZXBvcnQgKFJSKSBbUkZD
MzU1MF0gY29udmV5cyByZWNlcHRpb24NICAgc3RhdGlzdGljcyAoaS5lLiwgdHJhbnNwb3J0IGxl
dmVsIHN0YXRpc3RpY3MpIGluIG1ldHJpYyBibG9jayByZXBvcnQNICAgZm9ybWF0IGZvciBtdWx0
aXBsZSBSVFAgbWVkaWEgc3RyZWFtcyBpbmNsdWRpbmcNDSAgIG8gIHRoZSBmcmFjdGlvbiBvZiBw
YWNrZXQgbG9zdCBzaW5jZSB0aGUgbGFzdCByZXBvcnQNDSAgIG8gIHRoZSBjdW11bGF0aXZlIG51
bWJlciBvZiBwYWNrZXRzIGxvc3QNDSAgIG8gIHRoZSBoaWdoZXN0IHNlcXVlbmNlIG51bWJlciBy
ZWNlaXZlZA0NICAgbyAgYW4gZXN0aW1hdGUgb2YgdGhlIGludGVyLWFycml2YWwgaml0dGVyDQ0g
ICBvICBhbmQgaW5mb3JtYXRpb24gdG8gYWxsb3cgc2VuZGVycyB0byBjYWxjdWxhdGUgdGhlIG5l
dHdvcmsgcm91bmQNICAgICAgdHJpcCB0aW1lLg0NICAgVGhlIFJUQ1AgWFJzIFtSRkMzNjExXSBz
dXBwbGVtZW50IHRoZSBleGlzdGluZyBSVENQIHBhY2tldHMgYW5kDSAgIHByb3ZpZGUgbW9yZSBk
ZXRhaWxlZCBmZWVkYmFjayBvbiByZWNlcHRpb24gcXVhbGl0eSBpbiBzZXZlcmFsDSAgIGNhdGVn
b3JpZXM6DQ0gICBvICBMb3NzIGFuZCBkdXBsaWNhdGUgUkxFIHJlcG9ydHMNDSAgIG8gIFBhY2tl
dC1yZWNlaXB0IHRpbWVzIHJlcG9ydHMNDSAgIG8gIFJvdW5kLXRyaXAgdGltZSByZXBvcnRzDQ0g
ICBvICBTdGF0aXN0aWNzIFN1bW1hcnkgUmVwb3J0cw0NICAgVGhlcmUgYXJlIGFsc28gdmFyaW91
cyBvdGhlciBzY2VuYXJpb3MgaW4gd2hpY2ggaXQgaXMgZGVzaXJhYmxlIHRvDSAgIHNlbmQgUlRD
UCBNZXRyaWMgcmVwb3J0cyBtb3JlIGZyZXF1ZW50bHkuICBGb3IgZXhhbXBsZSwgdGhlIEF1ZGlv
Lw0gICBWaWRlbyBQcm9maWxlIHdpdGggRmVlZGJhY2sgW1JGQzQ1ODVdIGV4dGVuZHMgdGhlIHN0
YW5kYXJkIEEvVg0gICBQcm9maWxlIFtSRkMzNTUxXSB0byBhbGxvdyBSVENQIHJlcG9ydHMgdG8g
YmUgc2VudCBlYXJseSBwcm92aWRlZA0gICBSVENQIGJhbmR3aWR0aCBhbGxvY2F0aW9uIGlzIHJl
c3BlY3RlZC4gIFRoZSBmb2xsb3dpbmcgYXJlIGZvdXIgdXNlDSAgIGNhc2VzIGJ1dCBhcmUgbm90
IGxpbWl0ZWQgdG86DQ0gICBvICBSVENQIE5BQ0sgaXMgdXNlZCB0byBwcm92aWRlIGZlZWRiYWNr
IG9uIHRoZSBSVFAgc2VxdWVuY2UgbnVtYmVyDSAgICAgIG9mIHRoZSBsb3N0IHBhY2tldHMgW1JG
QzQ1ODVdLg0NICAgbyAgUlRDUCBpcyBleHRlbmRlZCB0byBjb252ZXkgcmVxdWVzdHMgZm9yIGZ1
bGwgaW50cmEtY29kZWQgZnJhbWVzIG9yDSAgICAgIHNlbGVjdCB0aGUgcmVmZXJlbmNlIHBpY3R1
cmUsIGFuZCBzaWduYWxjaGFuZ2VzIGluIHRoZSBkZXNpcmVkDSAgICAgIHRlbXBvcmFsL3NwYXRp
YWwgdHJhZGUtb2ZmIGFuZCBtYXhpbXVtIG1lZGlhIGJpdCByYXRlIFtSRkM1MTA0XS4NDQ0NDQ1X
dSwgZXQgYWwuICAgICAgICAgICAgICAgIEV4cGlyZXMgSnVuZSAxLCAyMDEyICAgICAgICAgICAg
ICAgICAgW1BhZ2UgOF0NDA1JbnRlcm5ldC1EcmFmdCAgICAgICAgUlRQIE1vbml0b3JpbmcgQXJj
aGl0ZWN0dXJlcyAgICAgICAgIE5vdmVtYmVyIDIwMTENDQ0gICBvICBSVENQIG9yIFJUQ1AgWFIg
aXMgZXh0ZW5kZWQgdG8gcHJvdmlkZSBmZWVkYmFjayBvbiBFQ04gc3RhdGlzdGljcw0gICAgICBp
bmZvcm1hdGlvbiBbRUNOXS4NDSAgIG8gIFJUQ1AgWFIgaXMgZXh0ZW5kZWQgdG8gcHJvdmlkZSBm
ZWVkYmFjayBvbiBtdWx0aWNhc3QgYWNxdWlzaXRpb24NICAgICAgc3RhdGlzdGljcyBpbmZvcm1h
dGlvbiBhbmQgcGFyYW1ldGVycyBbUkZDNjMzMl0uDQ0NDTMuMy4gIE5ldHdvcmsgYXNwZWN0cyBv
ZiBSVFAgbW9uaXRvcmluZyBhcmNoaXRlY3R1cmVzDVJUUCBTZW5kZXIvUmVjZWl2ZXIgZW50aXRp
ZXMgYXJlIHR5cGljYWxseSBsb2NhdGVkIGluIElQIGhvc3QgZXF1aXBtZW50IGluIGNhc2Ugb2Yg
ZW5kLXRvLWVuZCBJUCBuZXR3b3JrIGFyY2hpdGVjdHVyZXMuDVRoZXJlIG1pZ2h0IGJlIG90aGVy
IHNjZW5hcmlvcyB3aGVyZSBSVFAgU2VuZGVyL1JlY2VpdmVyIGVudGl0aWVzIGNvdWxkIGJlIGxv
Y2F0ZWQgaW4gbmV0d29yayBub2RlcyBpbnN0ZWFkIChlLmcuLCBhIFNJUC10by1QU1ROIGdhdGV3
YXkgb3IgU0lQLXRvLUguMzIzIGdhdGV3YXkpLiBUaGUgbG9jYXRpb24gb2YgdGhlIFJUUCBTZW5k
ZXIvUmVjZWl2ZXIgZW50aXR5IG1heSBpbXBhY3QgdGhlIHNldCBvZiBtZWFuaW5nZnVsIG1ldHJp
Y3MuDUZvciBpbnN0YW5jZTogYXBwbGljYXRpb24gbGV2ZWwgbWV0cmljcyBmb3IgUW9FIHJlbGF0
ZWQgcGVyZm9ybWFuY2UgbWV0cmljcyBhcmUgYmFzaWNhbGx5IGNvbmRpdGlvbmFsICgidXNlciBk
ZXZpY2UgbG9jYXRpb24iLCAiYXdhcmVuZXNzIG9mIGNvbnRlbnQgaW5mb3JtYXRpb24iIGV0Yykg
d2hlbiBtZWFzdXJlZCBpbiBhIG5ldHdvcmsgbm9kZSBpbnN0ZWFkIG9mIHRoZSB1c2VyIGVxdWlw
bWVudC4NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NV3UsIGV0IGFs
LiAgICAgICAgICAgICAgICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgIFtQ
YWdlIDldDQwNSW50ZXJuZXQtRHJhZnQgICAgICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVjdHVy
ZXMgICAgICAgICBOb3ZlbWJlciAyMDExDQ0NNC4gIElzc3VlcyB3aXRoIHJlcG9ydGluZyBtZXRy
aWMgYmxvY2sgdXNpbmcgUlRDUCBYUiBleHRlbnNpb24NDSAgIElzc3VlcyB0aGF0IGhhdmUgY29t
ZSB1cCBpbiB0aGUgcGFzdCB3aXRoIHJlcG9ydGluZyBtZXRyaWMgYmxvY2sNICAgdXNpbmcgUlRD
UCBYUiBleHRlbnNpb25zIGluY2x1ZGUgKGJ1dCBhcmUgcHJvYmFibHkgbm90IGxpbWl0ZWQgdG8p
DSAgIHRoZSBmb2xsb3dpbmc6DQ0gICBvICBVc2luZyBsYXJnZSBibG9jay4gIEEgc2luZ2xlIHJl
cG9ydCBibG9jayBvciBtZXRyaWMgaXMgZGVzaWduZWQgdG8NICAgICAgY29udGFpbiBhIGxhcmdl
IG51bWJlciBvZiBwYXJhbWV0ZXJzIGluIGRpZmZlcmVudCBjbGFzc2VzIGZvciBhDSAgICAgIHNw
ZWNpZmljIGFwcGxpY2F0aW9uLiAgRm9yIGV4YW1wbGUsIHRoZSBSVENQIEV4dGVuZGVkIFJlcG9y
dHMNICAgICAgKFhScykgW1JGQzM2MTFdIGRlZmluZXMgc2V2ZW4gcmVwb3J0IGJsb2NrIGZvcm1h
dHMgZm9yIG5ldHdvcmsNICAgICAgbWFuYWdlbWVudCBhbmQgcXVhbGl0eSBtb25pdG9yaW5nLiAg
U29tZSBvZiB0aGVzZSBibG9jayB0eXBlcw0gICAgICBkZWZpbmVkIGluIHRoZSBSVENQIFhScyBb
UkZDMzYxMV0gYXJlIG9ubHkgc3BlY2lmaWNhbGx5IGRlc2lnbmVkDSAgICAgIGZvciBjb252ZXlp
bmcgbXVsdGljYXN0IGluZmVyZW5jZSBvZiBuZXR3b3JrIGNoYXJhY3RlcmlzdGljcw0gICAgICAo
TUlOQykgb3Igdm9pY2Ugb3ZlciBJUCAoVm9JUCkgbW9uaXRvcmluZy4gIEhvd2V2ZXIgZGlmZmVy
ZW50DSAgICAgIGFwcGxpY2F0aW9ucyBsYXllcmVkIG9uIFJUUCBtYXkgaGF2ZSBkaWZmZXJlbnQg
bW9uaXRvcmluZw0gICAgICByZXF1aXJlbWVudHMuICBEZXNpZ24gbGFyZ2UgYmxvY2sgb25seSBm
b3Igc3BlY2lmaWMgYXBwbGljYXRpb25zDSAgICAgIG1heSBpbmNyZWFzZSBpbXBsZW1lbnRhdGlv
biBjb3N0IGFuZCBtaW5pbWl6ZSBpbnRlcm9wZXJhYmlsaXR5Lg0NICAgbyAgQ29ycmVsYXRpbmcg
UlRDUCBYUiB3aXRoIHRoZSBub24tUlRQIGRhdGEuICBDTkFNRSBkZWZpbmVkIGluIHRoZQ0gICAg
ICBSVFAgUHJvdG9jb2wgW1JGQzM1NTBdIGlzIGFuIGV4YW1wbGUgb2YgZXhpc3RpbmcgdG9vbCB0
aGF0IGFsbG93cw0gICAgICB0byBiaW5kIGFuIFNTUkMgdGhhdCBtYXkgY2hhbmdlIHRvIGEgZml4
ZWQgc291cmNlIG5hbWUgaW4gb25lIFJUUA0gICAgICBzZXNzaW9uLiAgSXQgbWF5IGJlIGFsc28g
Zml4ZWQgYWNyb3NzIG11bHRpcGxlIFJUUCBzZXNzaW9ucyBmcm9tDSAgICAgIHRoZSBzYW1lIHNv
dXJjZS4gIEhvd2V2ZXIgdGhlcmUgbWF5IGJlIHNpdHVhdGlvbnMgd2hlcmUgUlRDUA0gICAgICBy
ZXBvcnRzIGFyZSBzZW50IHRvIG90aGVyIHBhcnRpY2lwYXRpbmcgZW5kcG9pbnRzIHVzaW5nIG5v
bi1SVFANICAgICAgcHJvdG9jb2wgaW4gYSBzZXNzaW9uLiAgRm9yIGV4YW1wbGUsIGFzIGRlc2Ny
aWJlZCBpbiB0aGUgU0lQIFJUQ1ANICAgICAgU3VtbWFyeSBSZXBvcnQgUHJvdG9jb2wgW1JGQzYw
MzVdLCB0aGUgZGF0YSBjb250YWluZWQgaW4gUlRDUCBYUg0gICAgICBWb0lQIG1ldHJpY3MgcmVw
b3J0cyBbUkZDMzYxMV0gYXJlIGZvcndhcmRlZCB0byBhIGNlbnRyYWwNICAgICAgY29sbGVjdGlv
biBzZXJ2ZXIgc3lzdGVtcyB1c2luZyBTSVAuICBJbiBzdWNoIGNhc2UsIHRoZXJlIGlzIGENICAg
ICAgbGFyZ2UgcG9ydGZvbGlvIG9mIHF1YWxpdHkgcGFyYW1ldGVycyB0aGF0IGNhbiBiZSBhc3Nv
Y2lhdGVkIHdpdGgNICAgICAgcmVhbCB0aW1lIGFwcGxpY2F0aW9uLGUuZy4sIFZPSVAgYXBwbGlj
YXRpb24sIGJ1dCBvbmx5IGEgbWluaW1hbA0gICAgICBudW1iZXIgb2YgcGFyYW1ldGVycyBhcmUg
aW5jbHVkZWQgb24gdGhlIFJUQ1AtWFIgcmVwb3J0cy4NICAgICAgVGhlcmVmb3JlIGNvcnJlbGF0
aW9uIGJldHdlZW4gUlRDUCBYUiBhbmQgbm9uLVJUUCBkYXRhIHNob3VsZCBiZQ0gICAgICBjb25j
ZXJuZWQgaWYgYWRtaW5pc3RyYXRpb24gb3IgbWFuYWdlbWVudCBzeXN0ZW1zIG5lZWQgdG8gcmVs
eSBvbg0gICAgICB0aGUgbWFwcGluZyBSVENQIHN0YXRpc3RpY3MgdG8gbm9uLVJUQ1AgbWVhc3Vy
ZW1lbnRzIHRvIGNvbmR1Y3RzDSAgICAgIGRhdGEgYW5hbHlzaXMgYW5kIGNyZWF0ZXMgYWxlcnRz
IHRvIHRoZSB1c2Vycy4gIFdpdGhvdXQgc3VjaA0gICAgICBjb3JyZWxhdGlvbiwgaXQgaXMgaGFy
ZCB0byBwcm92aWRlIGFjY3VyYXRlIG1lYXN1cmVzIG9mIHJlYWwgdGltZQ0gICAgICBhcHBsaWNh
dGlvbiBxdWFsaXR5IHdpdGggYSBtaW5pbWFsIG51bWJlciBvZiBwYXJhbWV0ZXJzIGluY2x1ZGVk
DSAgICAgIG9uIHRoZSBSVENQLVhSIHJlcG9ydHMgaW4gc3VjaCBjYXNlLg0NICAgbyAgTWVhc3Vy
ZW1lbnQgSW5mb3JtYXRpb24gZHVwbGljYXRpb24uICBNZWFzdXJlbWVudCBpbmZvcm1hdGlvbg0g
ICAgICBwcm92aWRlcyBpbmZvcm1hdGlvbiByZWxldmFudCB0byBhIG1lYXN1cmVtZW50IHJlcG9y
dGVkIGluIG9uZSBvcg0gICAgICBtb3JlIG90aGVyIGJsb2NrIHR5cGVzLiAgRm9yIGV4YW1wbGUg
d2UgbWF5IHNldCBhIG1ldHJpYyBpbnRlcnZhbA0gICAgICBmb3IgdGhlIHNlc3Npb24gYW5kIG1v
bml0b3IgUlRQIHBhY2tldHMgd2l0aGluIG9uZSBvciBzZXZlcmFsDSAgICAgIGNvbnNlY3V0aXZl
IG1ldHJpYyBpbnRlcnZhbC4gIEluIHN1Y2ggY2FzZSwgdGhlIGV4dHJhIG1lYXVyZW1lbnQNICAg
ICAgaW5mb3JtYXRpb24gKGUuZy4sIGV4dGVuZGVkIHNlcXVlbmNlIG51bWJlciBvZiAxc3QgcGFj
a2V0LA0gICAgICBtZWFzdXJlbWVudCBwZXJpb2QpIG1heSBiZSBleHBlY3RlZC4gIEhvd2V2ZXIg
aWYgd2UgcHV0IHN1Y2ggZXh0cmENICAgICAgbWVhc3VyZW1lbnQgaW5mb3JtYXRpb24gaW50byBl
YWNoIG1ldHJpYyBibG9jaywgdGhlcmUgbWF5IGJlDSAgICAgIHNpdHVhdGlvbnMgd2hlcmUgYW4g
UlRDUCBYUiBwYWNrZXQgY29udGFpbmluZyBtdWx0aXBsZSBtZXRyaWMNDQ0NV3UsIGV0IGFsLiAg
ICAgICAgICAgICAgICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgW1BhZ2Ug
MTBdDQwNSW50ZXJuZXQtRHJhZnQgICAgICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVjdHVyZXMg
ICAgICAgICBOb3ZlbWJlciAyMDExDQ0NICAgICAgYmxvY2tzLCByZXBvcnRzIG9uIHRoZSBzYW1l
IHN0cmVhbXMgZnJvbSB0aGUgc2FtZSBzb3VyY2UuICBJbg0gICAgICBvdGhlciB3b3JkcywgZHVw
bGljYXRlZCBkYXRhIGZvciB0aGUgbWVhc3VyZW1lbnQgaXMgcHJvdmlkZWQNICAgICAgbXVsdGlw
bGUgdGltZXMsIG9uY2UgaW4gZXZlcnkgbWV0cmljIGJsb2NrLiAgVGhvdWdoIHRoaXMgZGVzaWdu
DSAgICAgIGVuc3VyZXMgaW1tdW5pdHkgdG8gcGFja2V0IGxvc3MsIGl0IG1heSBicmluZyBtb3Jl
IHBhY2tldGl6YXRpb24NICAgICAgY29tcGxleGl0eSBhbmQgdGhlIHByb2Nlc3Npbmcgb3Zlcmhl
YWQgaXMgbm90IGNvbXBsZXRlbHkgdHJpdmlhbA0gICAgICBpbiBzb21lIGNhc2VzLiAgVGhlcmVm
b3JlIGNvbXByb21pc2UgYmV0d2VlbiBwcm9jZXNzaW5nIG92ZXJoZWFkDSAgICAgIGFuZCByZWxp
YWJpbGl0eSBzaG91bGQgYmUgdGFrZW4gaW50byBhY2NvdW50Lg0NICAgbyAgQ29uc3VtcHRpb24g
b2YgWFIgYmxvY2sgY29kZSBwb2ludHMuICBUaGUgUlRDUCBYUiBibG9jayBuYW1lc3BhY2UNICAg
ICAgaXMgbGltaXRlZCBieSB0aGUgOC1iaXQgYmxvY2sgdHlwZSBmaWVsZCBpbiB0aGUgUlRDUCBY
UiBoZWFkZXIuDSAgICAgIFNwYWNlIGV4aGF1c3Rpb24gbWF5IGJlIGEgY29uY2VybiBpbiB0aGUg
ZnV0dXJlLiAgV2UgdGhlcmVmb3JlIG1heQ0gICAgICBuZWVkIGEgd2F5IHRvIGV4dGVuZCB0aGUg
YmxvY2sgdHlwZSBzcGFjZSwgc28gdGhhdCBuZXcNICAgICAgc3BlY2lmaWNhdGlvbnMgbWF5IGNv
bnRpbnVlIHRvIGJlIGRldmVsb3BlZC4NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0N
DQ0NDQ1XdSwgZXQgYWwuICAgICAgICAgICAgICAgIEV4cGlyZXMgSnVuZSAxLCAyMDEyICAgICAg
ICAgICAgICAgICBbUGFnZSAxMV0NDA1JbnRlcm5ldC1EcmFmdCAgICAgICAgUlRQIE1vbml0b3Jp
bmcgQXJjaGl0ZWN0dXJlcyAgICAgICAgIE5vdmVtYmVyIDIwMTENDQ01LiAgR3VpZGVsaW5lIGZv
ciByZXBvcnRpbmcgbWV0cmljIGJsb2NrIHVzaW5nIFJUQ1AgWFINDTUuMS4gIFVzaW5nIHNpbmds
ZSBtZXRyaWNzIGJsb2Nrcw0NICAgRGlmZmVyZW50IGFwcGxpY2F0aW9ucyB1c2luZyBSVFAgZm9y
IG1lZGlhIHRyYW5zcG9ydCBjZXJ0YWlubHkgaGF2ZQ0gICBkaWZmZXJpbmcgcmVxdWlyZW1lbnRz
IGZvciBtZXRyaWNzIHRyYW5zcG9ydGVkIGluIFJUQ1AgdG8gc3VwcG9ydA0gICB0aGVpciBvcGVy
YXRpb24uICBGb3IgbWFueSBhcHBsaWNhdGlvbnMsIHRoZSBiYXNpYyBtZXRyaWNzIGZvcg0gICB0
cmFuc3BvcnQgaW1wYWlybWVudHMgcHJvdmlkZWQgaW4gUlRDUCBTUiBhbmQgUlIgcGFja2V0cyBb
UkZDMzU1MF0NICAgKHRvZ2V0aGVyIHdpdGggc291cmNlIGlkZW50aWZpY2F0aW9uIHByb3ZpZGVk
IGluIFJUQ1AgU0RFUyBwYWNrZXRzKQ0gICBhcmUgc3VmZmljaWVudC4gIEZvciBvdGhlciBhcHBs
aWNhdGlvbnMgYWRkaXRpb25hbCBtZXRyaWNzIG1heSBiZQ0gICByZXF1aXJlZCBvciBhdCBsZWFz
dCBzdWZmaWNpZW50bHkgdXNlZnVsIHRvIGp1c3RpZnkgdGhlIG92ZXJoZWFkcywNICAgYm90aCBv
ZiBwcm9jZXNzaW5nIGluIGVuZHBvaW50cyBhbmQgb2YgaW5jcmVhc2VkIHNlc3Npb24gYmFuZHdp
ZHRoLg0gICBGb3IgZXhhbXBsZSBhbiBJUFRWIGFwcGxpY2F0aW9uIHVzaW5nIEZvcndhcmQgRXJy
b3IgQ29ycmVjdGlvbiAoRkVDKQ0gICBtaWdodCB1c2UgZWl0aGVyIGEgbWV0cmljIG9mIHBvc3Qt
cmVwYWlyIGxvc3Mgb3IgYSBtZXRyaWMgZ2l2aW5nDSAgIGRldGFpbGVkIGluZm9ybWF0aW9uIGFi
b3V0IHByZS1yZXBhaXIgbG9zcyBidXJzdHMgdG8gb3B0aW1pc2UgcGF5bG9hZA0gICBiYW5kd2lk
dGggYW5kIHRoZSBzdHJlbmd0aCBvZiBGRUMgcmVxdWlyZWQgZm9yIGNoYW5naW5nIG5ldHdvcmsN
ICAgY29uZGl0aW9ucy4gIEhvd2V2ZXIgdGhlcmUgYXJlIG1hbnkgbWV0cmljcyBhdmFpbGFibGUu
ICBJdCBpcyBsaWtlbHkNICAgdGhhdCBkaWZmZXJlbnQgYXBwbGljYXRpb25zIG9yIGNsYXNzZXMg
b2YgYXBwbGljYXRpb25zIHdpbGwgd2lzaCB0bw0gICB1c2UgZGlmZmVyZW50IG1ldHJpY3MuICBB
bnkgb25lIGFwcGxpY2F0aW9uIGlzIGxpa2VseSB0byByZXF1aXJlDSAgIG1ldHJpY3MgZm9yIG1v
cmUgdGhhbiBvbmUgcGFyYW1ldGVyIGJ1dCBpZiB0aGlzIGlzIHRoZSBjYXNlLA0gICBkaWZmZXJl
bnQgYXBwbGljYXRpb25zIHdpbGwgYWxtb3N0IGNlcnRhaW5seSByZXF1aXJlIGRpZmZlcmVudA0g
ICBjb21iaW5hdGlvbnMgb2YgbWV0cmljcy4gIElmIGxhcmdlciBibG9ja3MgYXJlIGRlZmluZWQg
Y29udGFpbmluZw0gICBtdWx0aXBsZSBtZXRyaWNzIHRvIGFkZHJlc3MgdGhlIG5lZWRzIG9mIGVh
Y2ggYXBwbGljYXRpb24sIGl0IGJlY29tZXMNICAgbGlrZWx5IHRoYXQgbWFueSBkaWZmZXJlbnQg
c3VjaCBsYXJnZXIgYmxvY2tzIGFyZSBkZWZpbmVkLCB3aGljaA0gICBiZWNvbWVzIGEgZGFuZ2Vy
IHRvIGludGVyb3BlcmFiaWxpdHkuDQ0gICBUbyBhdm9pZCB0aGlzIHBpdGZhbGwsIHRoaXMgbWVt
byBwcm9wb3NlcyB0aGUgdXNlIG9mIHNtYWxsIFJUQ1AgWFINICAgbWV0cmljcyBibG9ja3MgZWFj
aCBjb250YWluaW5nIGEgdmVyeSBzbWFsbCBudW1iZXIgb2YgaW5kaXZpZHVhbA0gICBtZXRyaWNz
IGNoYXJhY3Rlcml6aW5nIG9ubHkgb25lIHBhcmFtZXRlciBvZiBpbnRlcmVzdCB0byBhbg0gICBh
cHBsaWNhdGlvbiBydW5uaW5nIG92ZXIgUlRQLiAgRm9yIGV4YW1wbGUsIGF0IHRoZSBSVFAgdHJh
bnNwb3J0DSAgIGxheWVyLCB0aGUgcGFyYW1ldGVyIG9mIGludGVyZXN0IG1pZ2h0IGJlIHBhY2tl
dCBkZWxheSB2YXJpYXRpb24sIGFuZA0gICBzcGVjaWZpY2FsbHkgdGhlIG1ldHJpYyAiSVBEViIg
ZGVmaW5lZCBieSBbWTE1NDBdLiAgU2VlIFNlY3Rpb24gNiBmb3INICAgYXJjaGl0ZWN0dXJhbCBj
b25zaWRlcmF0aW9ucyBmb3IgYSBtZXRyaWNzIGJsb2NrLCB1c2luZyBhcyBhbiBleGFtcGxlDSAg
IGEgbWV0cmljcyBibG9jayB0byByZXBvcnQgcGFja2V0IGRlbGF5IHZhcmlhdGlvbi4NDTUuMi4g
IENvcnJlbGF0aW5nIFJUQ1AgWFIgd2l0aCB0aGUgbm9uLVJUUCBkYXRhDQ0gICBUaGVyZSBtYXkg
YmUgc2l0dWF0aW9uIHdoZXJlIG1vcmUgdGhhbiBvbmUgbWVkaWEgdHJhbnNwb3J0IHByb3RvY29s
cw0gICBhcmUgdXNlZCBieSBvbmUgYXBwbGljYXRpb24gdG8gaW50ZXJjb25uZWN0IHRvIHRoZSBz
YW1lIHNlc3Npb24gaW4NICAgdGhlIGdhdGV3YXkuICBGb3IgZXhhbXBsZSwgb25lIFJUQ1AgWFIg
UGFja2V0IGlzIHNlbnQgdG8gdGhlDSAgIHBhcnRpY2lwYXRpbmcgZW5kcG9pbnRzIHVzaW5nIG5v
bi0gUlRQLWJhc2VkIG1lZGlhIHRyYW5zcG9ydCAoZS5nLiwNICAgdXNpbmcgU0lQKSBpbiBhIFZP
SVAgc2Vzc2lvbiwgb25lIGNydWNpYWwgZmFjdG9yIGxpZXMgaW4gaG93IHRvDSAgIGhhbmRsZSB0
aGVpciBkaWZmZXJlbnQgaWRlbnRpdGllcyB0aGF0IGFyZSBjb3JyZXNwb25kaW5nIHRvIGRpZmZl
cmVudA0gICBtZWRpYSB0cmFuc3BvcnQuDQ0gICBUaGlzIG1lbW8gcHJvcG9zZXMgYW4gYXBwcm9h
Y2ggdG8gZmFjaWxpdGF0ZSB0aGUgY29ycmVsYXRpb24gb2YgdGhlDSAgIFJUQ1AgU2Vzc2lvbiB3
aXRoIG90aGVyIHNlc3Npb24tcmVsYXRlZCBub24tUlRQIGRhdGEuICBUaGF0IGlzIHRvIHNheQ0g
ICBpZiB0aGVyZSBpcyBhIG5lZWQgdG8gY29ycmVsYXRlIFJUUCBzZXNzaW9ucyB3aXRoIG5vbi1S
VFAgc2Vzc2lvbnMsDQ0NDVd1LCBldCBhbC4gICAgICAgICAgICAgICAgRXhwaXJlcyBKdW5lIDEs
IDIwMTIgICAgICAgICAgICAgICAgIFtQYWdlIDEyXQ0MDUludGVybmV0LURyYWZ0ICAgICAgICBS
VFAgTW9uaXRvcmluZyBBcmNoaXRlY3R1cmVzICAgICAgICAgTm92ZW1iZXIgMjAxMQ0NDSAgIHRo
ZW4gdGhlIGNvcnJlbGF0aW9uIGluZm9ybWF0aW9uIG5lZWRlZCBzaG91bGQgYmUgY29udmV5ZWQg
aW4gYSBuZXcNICAgUlRDUCBTb3VyY2UgRGVzY3JpcHRpb24gKFNERVMpIGl0ZW0gLHNpbmNlIHN1
Y2ggY29ycmVsYXRpb24NICAgaW5mb3JtYXRpb24gZGVzY3JpYmVzIHRoZSBzb3VyY2UsIHJhdGhl
ciB0aGFuIHByb3ZpZGluZyBhIHF1YWxpdHkNICAgcmVwb3J0LiAgQW4gZXhhbXBsZSB1c2UgY2Fz
ZSBpcyBmb3IgYSBwYXJ0aWNpcGFudCBlbmRwb2ludCBtYXkgY29udmV5DSAgIGEgY2FsbCBpZGVu
dGlmaWVyIG9yIGEgZ2xvYmFsIGNhbGwgaWRlbnRpZmllciBhc3NvY2lhdGVkIHdpdGggdGhlDSAg
IFNTUkMgb2YgbWVhc3VyZWQgUlRQIHN0cmVhbSAuICBJbiBzdWNoIGNhc2UsIHRoZSBwYXJ0aWNp
cGFudCBlbmRwb2ludA0gICB1c2VzIHRoZSBTU1JDIG9mIHNvdXJjZSB0byBiaW5kIHRoZSBjYWxs
IGlkZW50aWZpZXIgdXNpbmcgU0RFUyBpdGVtDSAgIGluIHRoZSBTREVTIFJUQ1AgcGFja2V0IGFu
ZCBzZW5kIHN1Y2ggY29ycmVsYXRpb24gdG8gdGhlIG5ldHdvcmsNICAgbWFuYWdlbWVudCBzeXN0
ZW0uICBBIGZsb3cgbWVhc3VyZW1lbnQgdG9vbCB0aGF0IGlzIGNvbmZpZ3VyZWQgd2l0aA0gICB0
aGUgNS10dXBsZSBhbmQgbm90IGNhbGwtYXdhcmUgdGhlbiBmb3J3YXJkIHRoZSBSVENQIFhSIHJl
cG9ydHMgYWxvbmcNICAgd2l0aCB0aGUgU1NSQyBvZiB0aGUgbWVhc3VyZWQgUlRQIHN0cmVhbSB3
aGljaCBpcyBpbmNsdWRlZCBpbiB0aGUgWFINICAgQmxvY2sgaGVhZGVyIGFuZCA1LXR1cGxlIHRv
IHRoZSBuZXR3b3JrIG1hbmFnZW1lbnQgc3lzdGVtLiAgTmV0d29yaw0gICBtYW5hZ2VtZW50IHN5
c3RlbSBjYW4gdGhlbiBjb3JyZWxhdGUgdGhpcyByZXBvcnQgdXNpbmcgU1NSQyB3aXRoDSAgIG90
aGVyIGRpYWdub3N0aWMgaW5mb3JtYXRpb24gc3VjaCBhcyBjYWxsIGRldGFpbCByZWNvcmRzLg0N
NS4zLiAgUmVkdWNpbmcgTWVhc3VyZW1lbnQgaW5mb3JtYXRpb24gcmVwZXRpdGlvbg0NICAgV2hl
biBtdWx0aXBsZSBtZXRyaWMgYmxvY2tzIGFyZSBjYXJyaWVkIGluIG9uZSBSVENQIFhSIHBhY2tl
dCwNICAgcmVwb3J0aW5nIG9uIHRoZSBzYW1lIHN0cmVhbSBmcm9tIHRoZSBzYW1lIHNvdXJjZSBm
b3IgdGhlIHNhbWUgdGltZQ0gICBwZXJpb2QsIFJUQ1Agc2hvdWxkIHVzZSB0aGUgU1NSQyB0byBp
ZGVudGlmeSBhbmQgY29ycmVsYXRlIHRoZQ0gICBtdWx0aXBsZSBtZXRyaWMgYmxvY2tzIGJldHdl
ZW4gbWV0cmljIGJsb2Nrcy4gIFRoaXMgbWVtbyBwcm9wb3NlcyB0bw0gICBkZWZpbmUgYSBuZXcg
WFIgQmxvY2sgdGhhdCB3aWxsIGJlIHVzZWQgdG8gY29udmV5IHRoZSBjb21tb24gdGltZQ0gICBw
ZXJpb2QgYW5kIHRoZSBudW1iZXIgb2YgcGFja2V0cyBzZW50IGR1cmluZyB0aGlzIHBlcmlvZCBb
TUldLiAgSWYNICAgdGhlIG1lYXN1cmVtZW50IGludGVydmFsIGZvciBhIG1ldHJpYyBpcyBkaWZm
ZXJlbnQgZnJvbSB0aGUgUlRDUA0gICByZXBvcnRpbmcgaW50ZXJ2YWwsIHRoZW4gdGhpcyBtZWFz
dXJlbWVudCBkdXJhdGlvbiBpbiB0aGUgW01JXSBTSE9VTEQNICAgYmUgdXNlZCB0byBzcGVjaWZ5
IHRoZSBpbnRlcnZhbC4gIEluIG9yZGVyIHRvIHJlZHVjZSBtZWFzdXJlbWVudA0gICBpbmZvcm1h
dGlvbiByZXBldGl0aW9uIGluIG9uZSBSVENQIFhSIGNvbXBvdW5kIHBhY2tldCBjb250YWluaW5n
DSAgIG11bHRpcGxlIG1ldHJpYyBibG9ja3MsIHRoZSBtZWFzdXJlbWVudCBpbmZvcm1hdGlvbiBz
aGFsbCBiZSBzZW50DSAgIGJlZm9yZSB0aGUgcmVsYXRlZCBtZXRyaWMgYmxvY2tzIHRoYXQgYXJl
IGZyb20gdGhlIHNhbWUgcmVwb3J0aW5nDSAgIGludGVydmFsLiAgTm90ZSB0aGF0IGZvciBwYWNr
ZXQgbG9zcyByb2J1c3RuZXNzIGlmIHRoZSByZXBvcnQgYmxvY2tzDSAgIGZvciB0aGUgc2FtZSBp
bnRlcnZhbCBzcGFuIG92ZXIgbW9yZSB0aGFuIG9uZSBSVENQIHBhY2tldCB0aGVuIGVhY2gNICAg
bXVzdCBoYXZlIHRoZSBtZWFzdXJlbWVudCBpZGVudGl0eSBpbmZvcm1hdGlvbiBldmVuIGlmIHRo
b3VnaCB0aGV5DSAgIHdpbGwgYmUgdGhlIHNhbWUuDQ01LjQuICBFeHBhbmRpbmcgdGhlIFJUQ1Ag
WFIgYmxvY2sgbmFtZXNwYWNlDQ0gICBUaGUgY29uc3VtcHRpb24gb2YgWFIgYmxvY2sgY29kZSBw
b2ludHMgaXNuJ3QgYSBtYWpvciBpc3N1ZS4gIEhvd2V2ZXINICAgaWYgWFIgYmxvY2sgY29kZXMg
cG9pbnRzIGlzIHJlYWxseSBjbG9zZSB0byBydW4gb3V0IG9mIHNwYWNlLCBpdA0gICBtaWdodCBi
ZSBkZXNpcmFibGUgdG8gZGVmaW5lIG5ldyBmaWVsZHMgaW4gdGhlIFhSIHJlcG9ydCBibG9jayBv
cg0gICBkZWZpbmUgb25lIFhSIGJsb2NrIHR5cGUgZm9yIHZlbmRvci1zcGVjaWZpYyBleHRlbnNp
b25zLCB3aXRoIGFuDSAgIGVudGVycHJpc2UgbnVtYmVyIGluY2x1ZGVkIHRvIGlkZW50aWZ5IHRo
ZSB2ZW5kb3IgbWFraW5nIHRoZQ0gICBleHRlbnNpb24uDQ0NDQ0NDQ0NDVd1LCBldCBhbC4gICAg
ICAgICAgICAgICAgRXhwaXJlcyBKdW5lIDEsIDIwMTIgICAgICAgICAgICAgICAgIFtQYWdlIDEz
XQ0MDUludGVybmV0LURyYWZ0ICAgICAgICBSVFAgTW9uaXRvcmluZyBBcmNoaXRlY3R1cmVzICAg
ICAgICAgTm92ZW1iZXIgMjAxMQ0NDTYuICBBbiBleGFtcGxlIG9mIGEgbWV0cmljIGJsb2NrDQ0g
ICBUaGlzIHNlY3Rpb24gdXNlcyB0aGUgZXhhbXBsZSBvZiBhbiBleGlzdGluZyBwcm9wb3NlZCBt
ZXRyaWNzIGJsb2NrDSAgIHRvIGlsbHVzdHJhdGUgdGhlIGFwcGxpY2F0aW9uIG9mIHRoZSBwcmlu
Y2lwbGVzIHNldCBvdXQgaW4NICAgU2VjdGlvbiA1LjEuDQ0gICBUaGUgZXhhbXBsZSBbUERWXSBp
cyBhIGJsb2NrIHRvIGNvbnZleSBpbmZvcm1hdGlvbiBhYm91dCBwYWNrZXQgZGVsYXkNICAgdmFy
aWF0aW9uIChQRFYpIG9ubHksIGNvbnNpc3RlbnQgd2l0aCB0aGUgcHJpbmNpcGxlIHRoYXQgYSBt
ZXRyaWNzDSAgIGJsb2NrIHNob3VsZCBhZGRyZXNzIG9ubHkgb25lIHBhcmFtZXRlciBvZiBpbnRl
cmVzdC4gIE9uZSBzaW1wbGUNICAgbWV0cmljIG9mIFBEViBpcyBhdmFpbGFibGUgaW4gdGhlIFJU
Q1AgUlIgcGFja2V0IGFzIHRoZSAiaW50ZXJhcnJpdmFsDSAgIGppdHRlciIgZmllbGQuICBUaGVy
ZSBhcmUgb3RoZXIgUERWIG1ldHJpY3Mgd2hpY2ggbWF5IGJlIG1vcmUgdXNlZnVsDSAgIHRvIGNl
cnRhaW4gYXBwbGljYXRpb25zLiAgVHdvIHN1Y2ggbWV0cmljcyBhcmUgdGhlIElQRFYgbWV0cmlj
DSAgIChbWTE1NDBdLCBbUkZDMzM5M10pIGFuZCB0aGUgTUFQRFYyIG1ldHJpYyBbRzEwMjBdLiAg
VXNlIG9mIHRoZXNlDSAgIG1ldHJpY3MgaXMgY29uc2lzdGVudCB3aXRoIHRoZSBwcmluY2lwbGUg
aW4gU2VjdGlvbiA1IG9mIFJUQ1ANICAgZ3VpZGVsaW5lIFtSRkM1OTY4XSB0aGF0IG1ldHJpY3Mg
c2hvdWxkIHVzdWFsbHkgYmUgZGVmaW5lZCBlbHNld2hlcmUsDSAgIHNvIHRoYXQgUlRDUCBzdGFu
ZGFyZHMgZGVmaW5lIG9ubHkgdGhlIHRyYW5zcG9ydCBvZiB0aGUgbWV0cmljIHJhdGhlcg0gICB0
aGFuIGl0cyBuYXR1cmUuICBUaGUgcHVycG9zZSBvZiB0aGlzIHNlY3Rpb24gaXMgdG8gaWxsdXN0
cmF0ZSB0aGUNICAgYXJjaGl0ZWN0dXJlIHVzaW5nIHRoZSBleGFtcGxlIG9mIFtQRFZdIHJhdGhl
ciB0aGFuIHRvIGRvY3VtZW50IHRoZQ0gICBkZXNpZ24gb2YgdGhlIFBEViBtZXRyaWNzIGJsb2Nr
IG9yIHRvIHByb3ZpZGUgYSB0dXRvcmlhbCBvbiBQRFYgaW4NICAgZ2VuZXJhbC4NDSAgIEdpdmVu
IHRoZSBhdmFpbGFiaWxpdHkgb2YgYXQgbGVhc3QgdGhyZWUgbWV0cmljcyBmb3IgUERWLCB0aGVy
ZSBhcmUNICAgZGVzaWduIG9wdGlvbnMgZm9yIHRoZSBhbGxvY2F0aW9uIG9mIG1ldHJpY3MgdG8g
UlRDUCBYUiBibG9ja3M6DQ0gICBvICBwcm92aWRlIGFuIFJUQ1AgWFIgYmxvY2sgcGVyIG1ldHJp
Yw0NICAgbyAgcHJvdmlkZSBhIHNpbmdsZSBSVENQIFhSIGJsb2NrIHdoaWNoIGNvbnRhaW5zIGFs
bCB0aHJlZSBtZXRyaWNzDQ0gICBvICBwcm92aWRlIGEgc2luZ2xlIFJUQ1AgYmxvY2sgdG8gY29u
dmV5IGFueSBvbmUgb2YgdGhlIHRocmVlDSAgICAgIG1ldHJpY3MsIHRvZ2V0aGVyIHdpdGggYSBp
ZGVudGlmaWVyIHRvIGluZm9ybSB0aGUgcmVjZWl2aW5nIFJUUA0gICAgICBzeXN0ZW0gb2YgdGhl
IHNwZWNpZmljIG1ldHJpYyBiZWluZyBjb252ZXllZA0NICAgSW4gY2hvb3NpbmcgYmV0d2VlbiB0
aGVzZSBvcHRpb25zLCBleHRlbnNpYmlsaXR5IGlzIGltcG9ydGFudCwNICAgYmVjYXVzZSBhZGRp
dGlvbmFsIG1ldHJpY3Mgb2YgUERWIG1heSB3ZWxsIGJlIHN0YW5kYXJkaXplZCBhbmQNICAgcmVx
dWlyZSBpbmNsdXNpb24gaW4gdGhpcyBmcmFtZXdvcmsuICBUaGUgZmlyc3Qgb3B0aW9uIGlzIGV4
dGVuc2libGUNICAgYnV0IG9ubHkgYnkgdXNlIG9mIGFkZGl0aW9uYWwgUlRDUCBYUiBibG9ja3Ms
IHdoaWNoIG1heSBjb25zdW1lIHRoZQ0gICBsaW1pdGVkIG5hbWVzcGFjZSBmb3IgUlRDUCBYUiBi
bG9ja3MgYXQgYW4gdW5hY2NlcHRhYmxlIHJhdGUuICBUaGUNICAgc2Vjb25kIG9wdGlvbiBpcyBu
b3QgZXh0ZW5zaWJsZSwgc28gY291bGQgYmUgcmVqZWN0ZWQgb24gdGhhdCBiYXNpcywNICAgYnV0
IGluIGFueSBjYXNlIGEgc2luZ2xlIGFwcGxpY2F0aW9uIGlzIHF1aXRlIHVubGlrZWx5IHRvIHJl
cXVpcmUNICAgdHJhbnNwb3J0IG9mIG1vcmUgdGhhbiBvbmUgbWV0cmljIGZvciBQRFYuICBIZW5j
ZSB0aGUgdGhpcmQgb3B0aW9uDSAgIHdhcyBjaG9zZW4uICBUaGlzIGltcGxpZXMgdGhlIGNyZWF0
aW9uIG9mIGEgc3Vic2lkaWFyeSBuYW1lc3BhY2UgdG8NICAgZW51bWVyYXRlIHRoZSBQRFYgbWV0
cmljcyB3aGljaCBtYXkgYmUgdHJhbnNwb3J0ZWQgYnkgdGhpcyBibG9jaywgYXMNICAgZGlzY3Vz
c2VkIGZ1cnRoZXIgaW4gW1BEVl0gLg0NDQ0NDQ0NDVd1LCBldCBhbC4gICAgICAgICAgICAgICAg
RXhwaXJlcyBKdW5lIDEsIDIwMTIgICAgICAgICAgICAgICAgIFtQYWdlIDE0XQ0MDUludGVybmV0
LURyYWZ0ICAgICAgICBSVFAgTW9uaXRvcmluZyBBcmNoaXRlY3R1cmVzICAgICAgICAgTm92ZW1i
ZXIgMjAxMQ0NDTcuICBBcHBsaWNhdGlvbiB0byBSRkMgNTExNyB0b3BvbG9naWVzDQ0gICBUaGUg
dG9wb2xvZ2llcyBzcGVjaWZpZWQgaW4gW1JGQzUxMTddIGZhbGwgaW50byB0d28gY2F0ZWdvcmll
cy4gIFRoZQ0gICBmaXJzdCBjYXRlZ29yeSByZWxhdGVzIHRvIHRoZSBSVFAgc3lzdGVtIG1vZGVs
IHV0aWxpemluZyBtdWx0aWNhc3QNICAgYW5kL29yIHVuaWNhc3QuICBUaGUgdG9wb2xvZ2llcyBp
biB0aGlzIGNhdGVnb3J5IGFyZSBzcGVjaWZpY2FsbHkNICAgVG9wby1Qb2ludC10by1Qb2ludCwg
VG9wby0gTXVsdGljYXN0LCBUb3BvLVRyYW5zbGF0b3IgKGJvdGggdmFyaWFudHMsDSAgIFRvcG8t
VHJuLVRyYW5zbGF0b3IgYW5kIFRvcG8tTWVkaWEtVHJhbnNsYXRvciwgYW5kIGNvbWJpbmF0aW9u
cyBvZg0gICB0aGUgdHdvKSwgYW5kIFRvcG8tTWl4ZXIuICBUaGVzZSB0b3BvbG9naWVzIHVzZSBS
VFAgZW5kIHN5c3RlbXMsIFJUUA0gICBtaXhlcnMgYW5kIFJUUCB0cmFuc2xhdG9ycyBkZWZpbmVk
IGluIHRoZSBSVFAgcHJvdG9jb2wgW1JGQzM1NTBdLg0gICBGb3IgcHVycG9zZXMgb2YgcmVwb3J0
aW5nIGNvbm5lY3Rpb24gcXVhbGl0eSB0byBvdGhlciBSVFAgc3lzdGVtcywNICAgUlRQIG1peGVy
cyBhbmQgUlRQIGVuZCBzeXN0ZW1zIGFyZSB2ZXJ5IHNpbWlsYXIuICBNaXhlcnMNICAgcmVzeW5j
aHJvbml6ZSBwYWNrZXRzIGFuZCBkbyBub3QgcmVsYXkgUlRDUCByZXBvcnRzIHJlY2VpdmVkIGZy
b20gb25lDSAgIGNsb3VkIHRvd2FyZHMgb3RoZXIgY2xvdWQocykuICBUcmFuc2xhdG9ycyBkbyBu
b3QgcmVzeW5jaHJvbml6ZQ0gICBwYWNrZXRzIGFuZCBTSE9VTEQgZm9yd2FyZCBjZXJ0YWluIFJU
Q1AgcmVwb3J0cyBiZXR3ZWVuIGNsb3Vkcy4gIEluDSAgIHRoaXMgY2F0ZWdvcnksIHRoZSBSVFAg
c3lzdGVtIChlbmQgc3lzdGVtLCBtaXhlciBvciB0cmFuc2xhdG9yKSB3aGljaA0gICBvcmlnaW5h
dGVzLCB0ZXJtaW5hdGVzIG9yIGZvcndhcmRzIFJUQ1AgWFIgYmxvY2tzIGlzIGV4cGVjdGVkIHRv
DSAgIGhhbmRsZSBSVENQLCBpbmNsdWRpbmcgUlRDUCBYUiwgYWNjb3JkaW5nIHRvIHRoZSBSVFAg
cHJvdG9jb2wNICAgW1JGQzM1NTBdLiAgUHJvdmlkZWQgdGhpcyBleHBlY3RhdGlvbiBpcyBtZXQs
IGFuIFJUUCBzeXN0ZW0gdXNpbmcNICAgUlRDUCBYUiBpcyBhcmNoaXRlY3R1cmFsbHkgbm8gZGlm
ZmVyZW50IGZyb20gYW4gUlRQIHN5c3RlbSBvZiB0aGUNICAgc2FtZSBjbGFzcyAoZW5kIHN5c3Rl
bSwgbWl4ZXIsIG9yIHRyYW5zbGF0b3IpIHdoaWNoIGRvZXMgbm90IHVzZSBSVENQDSAgIFhSLiAg
VGhlIHNlY29uZCBjYXRlZ29yeSByZWxhdGVzIHRvIGRlcGxveWVkIHN5c3RlbSBtb2RlbHMgdXNl
ZCBpbg0gICBtYW55IEguMzIzIFtIMzIzXSB2aWRlbyBjb25mZXJlbmNlcy4gIFRoZSB0b3BvbG9n
aWVzIGluIHRoaXMgY2F0ZWdvcnkNICAgYXJlIFRvcG8tVmlkZW8tU3dpdGNoLU1DVSBhbmQgVG9w
by1SVENQLXRlcm1pbmF0aW5nLU1DVS4gIFN1Y2gNICAgdG9wb2xvZ2llcyBiYXNlZCBvbiBzeXN0
ZW1zIGRvIG5vdCBiZWhhdmUgYWNjb3JkaW5nIHRvIHRoZSBSVFANICAgcHJvdG9jb2wgW1JGQzM1
NTBdLg0NICAgQ29uc2lkZXJpbmcgdGhlIE1DVSBhbmQgdHJhbnNsYXRvciBhcmUgdHdvIHR5cGlj
YWwgdG9wb2xvZ2llcyBpbiB0aGUNICAgdHdvIGNhdGVnb3JpZXMgbWVudGlvbmVkIGFib3ZlLCB0
aGlzIGRvY3VtZW50IHdpbGwgdGFrZSB0aGVtIGFzIHR3bw0gICB0eXBpY2FsIGV4YW1wbGVzIHRv
IGV4cGxhaW4gaG93IFJUQ1AgWFIgcmVwb3J0IHdvcmtzIGluIGRpZmZlcmVudA0gICBSRkM1MTE3
IHRvcG9sb2dpZXMuDQ03LjEuICBBcHBsaWNhYmlsaXR5IHRvIE1DVQ0NICAgVG9wby1WaWRlby1T
d2l0Y2gtTUNVIGFuZCBUb3BvLVJUQ1AtdGVybWluYXRpbmctTUNVLCBzdWZmZXIgZnJvbSB0aGUN
ICAgZGlmZmljdWx0aWVzIGRlc2NyaWJlZCBpbiBbUkZDNTExN10uICBUaGVzZSBkaWZmaWN1bHRp
ZXMgYXBwbHkgdG8NICAgc3lzdGVtcyBzZW5kaW5nLCBhbmQgZXhwZWN0aW5nIHRvIHJlY2VpdmUs
IFJUQ1AgWFIgYmxvY2tzIGFzIG11Y2ggYXMNICAgdG8gc3lzdGVtcyB1c2luZyBvdGhlciBSVENQ
IHBhY2tldCB0eXBlcy4gIEZvciBleGFtcGxlLCBhIHBhcnRpY2lwYW50DSAgIFJUUCBlbmQgc3lz
dGVtIG1heSBzZW5kIG1lZGlhIHRvIGEgdmlkZW8gc3dpdGNoIE1DVS4gIElmIHRoZSBtZWRpYQ0g
ICBzdHJlYW0gaXMgbm90IHNlbGVjdGVkIGZvciBmb3J3YXJkaW5nIGJ5IHRoZSBzd2l0Y2gsIG5l
aXRoZXIgUlRDUCBSUg0gICBwYWNrZXRzIG5vciBSVENQIFhSIGJsb2NrcyByZWZlcnJpbmcgdG8g
dGhlIGVuZCBzeXN0ZW0ncyBnZW5lcmF0ZWQNICAgc3RyZWFtIHdpbGwgYmUgcmVjZWl2ZWQgYXQg
dGhlIFJUUCBlbmQgc3lzdGVtLiAgU3RyaWN0bHkgdGhlIFJUUCBlbmQNICAgc3lzdGVtIGNhbiBv
bmx5IGNvbmNsdWRlIHRoYXQgaXRzIFJUUCBoYXMgYmVlbiBsb3N0IGluIHRoZSBuZXR3b3JrLA0g
ICB0aG91Z2ggYW4gUlRQIGVuZCBzeXN0ZW0gY29tcGx5aW5nIHdpdGggdGhlIHJvYnVzdG5lc3Mg
cHJpbmNpcGxlIG9mDSAgIFtSRkMxMTIyXSBzaG91bGQgc3Vydml2ZSB3aXRoIGVzc2VudGlhbCBm
dW5jdGlvbnMgKGkuZS4sbWVkaWENICAgZGlzdHJpYnV0aW9uKSB1bmltcGFpcmVkLg0NDQ0NDQ1X
dSwgZXQgYWwuICAgICAgICAgICAgICAgIEV4cGlyZXMgSnVuZSAxLCAyMDEyICAgICAgICAgICAg
ICAgICBbUGFnZSAxNV0NDA1JbnRlcm5ldC1EcmFmdCAgICAgICAgUlRQIE1vbml0b3JpbmcgQXJj
aGl0ZWN0dXJlcyAgICAgICAgIE5vdmVtYmVyIDIwMTENDQ03LjIuICBBcHBsaWNhYmlsaXR5IHRv
IFRyYW5zbGF0b3JzDQ0gICBTZWN0aW9uIDcuMiBvZiB0aGUgUlRQIHByb3RvY29sIFtSRkMzNTUw
XSBkZXNjcmliZXMgcHJvY2Vzc2luZyBvZg0gICBSVENQIGJ5IHRyYW5zbGF0b3JzLiAgUlRDUCBY
UiBpcyB3aXRoaW4gdGhlIHNjb3BlIG9mIHRoZQ0gICByZWNvbW1lbmRhdGlvbnMgb2YgdGhlIFJU
UCBwcm90b2NvbCBbUkZDMzU1MF0uICBTb21lIFJUQ1AgWFIgbWV0cmljcw0gICBibG9ja3MgbWF5
IHVzZWZ1bGx5IGJlIG1lYXN1cmVkIGF0LCBhbmQgcmVwb3J0ZWQgYnksIHRyYW5zbGF0b3JzLiAg
QXMNICAgZGVzY3JpYmVkIGluIHRoZSBSVFAgcHJvdG9jb2wgW1JGQzM1NTBdIHRoaXMgY3JlYXRl
cyBhIHJlcXVpcmVtZW50DSAgIGZvciB0aGUgdHJhbnNsYXRvciB0byBhbGxvY2F0ZSBhbiBTU1JD
IGZvciB0aGUgbW9uaXRvciBjb2xsb2NhdGVkDSAgIHdpdGggaXRzZWxmIHNvIHRoYXQgdGhlIG1v
bml0b3IgbWF5IHBvcHVsYXRlIHRoZSBTU1JDIGluIHRoZSBSVENQIFhSDSAgIHBhY2tldCBoZWFk
ZXIgYXMgcGFja2V0IHNlbmRlciBTU1JDIGFuZCBzZW5kIGl0IG91dChhbHRob3VnaCB0aGUNICAg
dHJhbnNsYXRvciBpcyBub3QgYSBTeW5jaHJvbmlzYXRpb24gU291cmNlIGluIHRoZSBzZW5zZSBv
Zg0gICBvcmlnaW5hdGluZyBSVFAgbWVkaWEgcGFja2V0cykuICBJdCBtdXN0IGFsc28gc3VwcGx5
IHRoaXMgU1NSQyBhbmQNICAgdGhlIGNvcnJlc3BvbmRpbmcgQ05BTUUgaW4gUlRDUCBTREVTIHBh
Y2tldHMuDQ0gICBJbiBSVFAgc2Vzc2lvbnMgd2hlcmUgb25lIG9yIG1vcmUgdHJhbnNsYXRvcnMg
Z2VuZXJhdGUgYW55IFJUQ1ANICAgdHJhZmZpYyB0b3dhcmRzIHRoZWlyIG5leHQtbmVpZ2hib3Vy
IFJUUCBzeXN0ZW0sIG90aGVyIHRyYW5zbGF0b3JzIGluDSAgIHRoZSBzZXNzaW9uIGhhdmUgYSBj
aG9pY2UgYXMgdG8gd2hldGhlciB0aGV5IGZvcndhcmQgYSB0cmFuc2xhdG9yJ3MNICAgUlRDUCBw
YWNrZXRzLiAgRm9yd2FyZGluZyBtYXkgcHJvdmlkZSBhZGRpdGlvbmFsIGluZm9ybWF0aW9uIHRv
IG90aGVyDSAgIFJUUCBzeXN0ZW1zIGluIHRoZSBjb25uZWN0aW9uIGJ1dCBpbmNyZWFzZXMgUlRD
UCBiYW5kd2lkdGggYW5kIG1heSBpbg0gICBzb21lIGNhc2VzIHByZXNlbnQgYSBzZWN1cml0eSBy
aXNrLiAgUlRQIHRyYW5zbGF0b3JzIG1heSBoYXZlDSAgIGZvcndhcmRpbmcgYmVoYXZpb3VyIGJh
c2VkIG9uIGxvY2FsIHBvbGljeSwgd2hpY2ggbWlnaHQgZGlmZmVyDSAgIGJldHdlZW4gZGlmZmVy
ZW50IGludGVyZmFjZXMgb2YgdGhlIHNhbWUgdHJhbnNsYXRvci4NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0N
DQ0NDQ0NDQ0NDQ1XdSwgZXQgYWwuICAgICAgICAgICAgICAgIEV4cGlyZXMgSnVuZSAxLCAyMDEy
ICAgICAgICAgICAgICAgICBbUGFnZSAxNl0NDA1JbnRlcm5ldC1EcmFmdCAgICAgICAgUlRQIE1v
bml0b3JpbmcgQXJjaGl0ZWN0dXJlcyAgICAgICAgIE5vdmVtYmVyIDIwMTENDQ04LiAgSUFOQSBD
b25zaWRlcmF0aW9ucw0NICAgVGhlcmUgaXMgbm8gSUFOQSBhY3Rpb24gaW4gdGhpcyBkb2N1bWVu
dC4NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NV3UsIGV0
IGFsLiAgICAgICAgICAgICAgICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAg
W1BhZ2UgMTddDQwNSW50ZXJuZXQtRHJhZnQgICAgICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVj
dHVyZXMgICAgICAgICBOb3ZlbWJlciAyMDExDQ0NOS4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25z
DQ0gICBUaGlzIGRvY3VtZW50IGZvY3VzZXMgb24gdGhlIFJUQ1AgcmVwb3J0aW5nIGV4dGVuc2lv
biB1c2luZyBSVENQIFhSDSAgIGFuZCBzaG91bGQgbm90IGdpdmUgcmlzZSB0byBhbnkgbmV3IHNl
Y3VyaXR5IHZ1bG5lcmFiaWxpdGllcyBiZXlvbmQNICAgdGhvc2UgZGVzY3JpYmVkIGluIFJUQ1Ag
WFJzIFtSRkMzNjExXS4gIEhvd2V2ZXIgaXQgYWxzbyBkZXNjcmliZXMgdGhlDSAgIGFyY2hpdGVj
dHVyYWwgZnJhbWV3b3JrIHRvIGJlIHVzZWQgZm9yIG1vbml0b3JpbmcgYXQgUlRQIGxheWVyLiAg
VGhlDSAgIHNlY3VyaXR5IGlzc3VlcyB3aXRoIG1vbml0b3JpbmcgbmVlZHMgdG8gYmUgY29uc2lk
ZXJlZC4NDSAgIEluIFJUUCBzZXNzaW9ucywgYSBSVFAgc3lzdGVtIG1heSB1c2UgaXRzIG93biBT
U1JDIHRvIHNlbmQgaXRzDSAgIG1vbml0b3JpbmcgcmVwb3J0cyB0b3dhcmRzIGl0cyBuZXh0LW5l
aWdoYm91ciBSVFAgc3lzdGVtLiAgT3RoZXIgUlRQDSAgIHN5c3RlbSBpbiB0aGUgc2Vzc2lvbiBt
YXkgaGF2ZSBhIGNob2ljZSBhcyB0byB3aGV0aGVyIHRoZXkgZm9yd2FyZA0gICB0aGlzIFJUUCBz
eXN0ZW0ncyBSVENQIHBhY2tldHMuICBUaGlzIHByZXNlbnQgYSBzZWN1cml0eSBpc3N1ZSBzaW5j
ZQ0gICB0aGUgaW5mb3JtYXRpb24gaW4gdGhlIHJlcG9ydCBtYXkgYmUgZXhwb3NlZCBieSB0aGUg
b3RoZXIgUlRQIHN5c3RlbQ0gICB0byBhbnkgbWFsaWNpb3VzIG5vZGUuICBUaGVyZWZvcmUgaWYg
dGhlIGluZm9ybWF0aW9uIGlzIGNvbnNpZGVyZWQgYXMNICAgc2Vuc2l0aXZlLCB0aGUgbW9uaXRv
cmluZyByZXBvcnQgc2hvdWxkIGJlIGVuY3J5cHRlZC4NDSAgIEFsc28gbm90ZSB0aGF0IHRoZSB0
aGlyZCBwYXJ0eSBtb25pdG9ycyBhcmUgbm90IHZpc2libGUgYXQgdGhlIFJUUA0gICBsYXllciBz
aW5jZSB0aGV5IGRvIG5vdCBzZW5kIGFueSBSVENQIHBhY2tldHMuICBJbiBvcmRlciB0byBwcmV2
ZW50DSAgIGFueSBzZW5zaXRpdmUgaW5mb3JtYXRpb24gbGVha2FnZSwgdGhlIG1vbml0b3Jpbmcg
ZnJvbSB0aGUgdGhpcmQNICAgcGFydHkgbW9uaXRvcnMgc2hvdWxkIGJlIHByb2hpYml0ZWQgdW5s
ZXNzIHRoZSBzZWN1cml0eSBpcyBpbiBwbGFjZQ0gICB0byBhdXRoZW50aWNhdGUgdGhlbS4NDQ0N
DQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NV3UsIGV0IGFsLiAgICAgICAgICAgICAgICBFeHBp
cmVzIEp1bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgW1BhZ2UgMThdDQwNSW50ZXJuZXQtRHJh
ZnQgICAgICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVjdHVyZXMgICAgICAgICBOb3ZlbWJlciAy
MDExDQ0NMTAuICBBY2tub3dsZWRnZW1lbnQNDSAgIFRoZSBhdXRob3JzIHdvdWxkIGFsc28gbGlr
ZSB0byB0aGFuayBDb2xpbiBQZXJraW5zLCBHcmFlbWUgR2liYnMsDSAgIERlYmJpZSBHcmVlbnN0
cmVldCwgS2VpdGggRHJhZ2UsIERhbiBSb21hc2NhbnUsIEFsaSBDLiBCZWdlbiwgUm9uaQ0gICBF
dmVuLCBNYWdudXMgV2VzdGVybHVuZGZvciB0aGVpciB2YWx1YWJsZSBjb21tZW50cyBhbmQgc3Vn
Z2VzdGlvbnMgb24NICAgdGhlIGVhcmx5IHZlcnNpb24gb2YgdGhpcyBkb2N1bWVudC4NDQ0NDQ0N
DQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NV3UsIGV0IGFsLiAgICAgICAg
ICAgICAgICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgW1BhZ2UgMTldDQwN
SW50ZXJuZXQtRHJhZnQgICAgICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVjdHVyZXMgICAgICAg
ICBOb3ZlbWJlciAyMDExDQ0NMTEuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzDQ0gICBbRUNOXSAg
ICAgIFdlc3Rlcmx1bmQsIE0uLCBKb2hhbnNzb24sIEkuLCBQZXJraW5zLCBDLiwgTydIYW5sb24s
IFAuLA0gICAgICAgICAgICAgIGFuZCBLLiBDYXJsYmVyZywgIkV4cGxpY2l0IENvbmdlc3Rpb24g
Tm90aWZpY2F0aW9uIChFQ04pDSAgICAgICAgICAgICAgZm9yIFJUUCBvdmVyIFVEUCIsIElEIGRy
YWZ0LWlldGYtYXZ0Y29yZS1lY24tZm9yLXJ0cC0wNCwNICAgICAgICAgICAgICBKdWx5IDIwMTEu
DQ0gICBbRzEwMjBdICAgIElUVS1ULCAiSVRVLVQgUmVjLiBHLjEwMjAsIFBlcmZvcm1hbmNlIHBh
cmFtZXRlcg0gICAgICAgICAgICAgIGRlZmluaXRpb25zIGZvciBxdWFsaXR5IG9mIHNwZWVjaCBh
bmQgb3RoZXIgdm9pY2ViYW5kDSAgICAgICAgICAgICAgYXBwbGljYXRpb25zIHV0aWxpemluZyBJ
UCBuZXR3b3JrcyIsIEp1bHkgMjAwNi4NDSAgIFtIMzIzXSAgICAgSVRVLVQsICJJVFUtVCBSZWMu
IEguMzIzLCBQYWNrZXQtYmFzZWQgbXVsdGltZWRpYQ0gICAgICAgICAgICAgIGNvbW11bmljYXRp
b25zIHN5c3RlbXMiLCBKdW5lIDIwMDYuDQ0gICBbTUldICAgICAgIFd1LCBRLiwgIk1lYXN1cmVt
ZW50IElkZW50aXR5IGFuZCBpbmZvcm1hdGlvbiBSZXBvcnRpbmcNICAgICAgICAgICAgICB1c2lu
ZyBTREVTIGl0ZW0gYW5kIFhSIEJsb2NrIiwNICAgICAgICAgICAgICBJRCBkcmFmdC1pZXRmLXhy
YmxvY2stcnRjcC14ci1tZWFzLWlkZW50aXR5LTAxLA0gICAgICAgICAgICAgIE9jdG9iZXIgMjAx
MS4NDSAgIFtNUV0gICAgICAgV3UsIFEuLCBab3JuLCBHLiwgU2Nob3R0LCBSLiwgYW5kIEsuIExl
ZSwgIlJUQ1AgWFIgQmxvY2tzDSAgICAgICAgICAgICAgZm9yIG11bHRpbWVkaWEgcXVhbGl0eSBt
ZXRyaWMgcmVwb3J0aW5nIiwNICAgICAgICAgICAgICBJRCBkcmFmdC13dS14cmJsb2NrLXJ0Y3At
eHItcXVhbGl0eS1tb25pdG9yaW5nLTAyLA0gICAgICAgICAgICAgIE1heSAyMDExLg0NICAgW1BE
Vl0gICAgICBIdW50LCBHLiwgIlJUQ1AgWFIgUmVwb3J0IEJsb2NrIGZvciBQYWNrZXQgRGVsYXkg
VmFyaWF0aW9uDSAgICAgICAgICAgICAgTWV0cmljIFJlcG9ydGluZyIsIElEIGRyYWZ0LWlldGYt
eHJibG9jay1ydGNwLXhyLXBkdi0wMCwNICAgICAgICAgICAgICBTZXB0ZW1iZXIgMjAxMS4NDSAg
IFtSRkMxMTIyXSAgQnJhZGVuLCBSLiwgIlJlcXVpcmVtZW50cyBmb3IgSW50ZXJuZXQgSG9zdHMg
LS0NICAgICAgICAgICAgICBDb21tdW5pY2F0aW9uIExheWVycyIsIFJGQyAxMTIyLCBPY3RvYmVy
IDE5ODkuDQ0gICBbUkZDMzM5M10gIERlbWljaGVsaXMsIEMuLCAiSVAgUGFja2V0IERlbGF5IFZh
cmlhdGlvbiBNZXRyaWMgZm9yIElQDSAgICAgICAgICAgICAgUGVyZm9ybWFuY2UgTWV0cmljcyAo
SVBQTSkiLCBSRkMgMzM5MywgTm92ZW1iZXIgMjAwMi4NDSAgIFtSRkMzNTUwXSAgU2NodWx6cmlu
bmUsIEguLCAiUlRQOiBBIFRyYW5zcG9ydCBQcm90b2NvbCBmb3IgUmVhbC1UaW1lDSAgICAgICAg
ICAgICAgQXBwbGljYXRpb25zIiwgUkZDIDM1NTAsIEp1bHkgMjAwMy4NDSAgIFtSRkMzNTUxXSAg
U2NodWx6cmlubmUgLCBILiBhbmQgUy4gQ2FzbmVyLCAiRXh0ZW5kZWQgUlRQIFByb2ZpbGUgZm9y
DSAgICAgICAgICAgICAgUmVhbC10aW1lIFRyYW5zcG9ydCBDb250cm9sIFByb3RvY29sIChSVENQ
KS1CYXNlZCBGZWVkYmFjaw0gICAgICAgICAgICAgIChSVFAvQVZQRikiLCBSRkMgMzU1MSwgSnVs
eSAyMDAzLg0NICAgW1JGQzM2MTFdICBGcmllZG1hbiwgVC4sICJSVFAgQ29udHJvbCBQcm90b2Nv
bCBFeHRlbmRlZCBSZXBvcnRzIChSVENQDSAgICAgICAgICAgICAgWFIpIiwgUkZDIDM2MTEsIE5v
dmVtYmVyIDIwMDMuDQ0gICBbUkZDNDU4NV0gIE90dCwgSi4gYW5kIFMuIFdlbmdlciwgIkV4dGVu
ZGVkIFJUUCBQcm9maWxlIGZvciBSZWFsLXRpbWUNICAgICAgICAgICAgICBUcmFuc3BvcnQgQ29u
dHJvbCBQcm90b2NvbCAoUlRDUCktQmFzZWQgRmVlZGJhY2sgKFJUUC8NICAgICAgICAgICAgICBB
VlBGKSIsIFJGQyA0NTg1LCBKdWx5IDIwMDYuDQ0NDQ1XdSwgZXQgYWwuICAgICAgICAgICAgICAg
IEV4cGlyZXMgSnVuZSAxLCAyMDEyICAgICAgICAgICAgICAgICBbUGFnZSAyMF0NDA1JbnRlcm5l
dC1EcmFmdCAgICAgICAgUlRQIE1vbml0b3JpbmcgQXJjaGl0ZWN0dXJlcyAgICAgICAgIE5vdmVt
YmVyIDIwMTENDQ0gICBbUkZDNTEwNF0gIFdlbmdlciwgUy4sIENoYW5kcmEsIFUuLCBXZXN0ZXJs
dW5kLCBNLiwgYW5kIEIuIEJ1cm1hbiwNICAgICAgICAgICAgICAiU2Vzc2lvbiBJbml0aWF0aW9u
IFByb3RvY29sIEV2ZW50IFBhY2thZ2UgZm9yIFZvaWNlDSAgICAgICAgICAgICAgUXVhbGl0eSBS
ZXBvcnRpbmciLCBSRkMgNTEwNCwgRmVicnVhcnkgMjAwOC4NDSAgIFtSRkM1MTE3XSAgV2VzdGVy
bHVuZCwgTS4sICJSVFAgVG9wb2xvZ2llcyIsIFJGQyA1MTE3LCBKYW51YXJ5IDIwMDguDQ0gICBb
UkZDNTk2OF0gIE90dCwgSi4gYW5kIEMuIFBlcmtpbnMsICJHdWlkZWxpbmVzIGZvciBFeHRlbmRp
bmcgdGhlIFJUUA0gICAgICAgICAgICAgIENvbnRyb2wgUHJvdG9jb2wgKFJUQ1ApIiwgUkZDIDU5
NjgsIFNlcHRlbWJlciAyMDEwLg0NICAgW1JGQzYwMzVdICBQZW5kbGV0b24sIEEuLCBDbGFyaywg
QS4sIEpvaG5zdG9uLCBBLiwgYW5kIEguIFNpbm5yZWljaCwNICAgICAgICAgICAgICAiU2Vzc2lv
biBJbml0aWF0aW9uIFByb3RvY29sIEV2ZW50IFBhY2thZ2UgZm9yIFZvaWNlDSAgICAgICAgICAg
ICAgUXVhbGl0eSBSZXBvcnRpbmciLCBSRkMgNjAzNSwgTm92ZW1iZXIgMjAxMC4NDSAgIFtSRkM2
MzMyXSAgQmVnZW4sIEEuIGFuZCBFLiBGcmllZHJpY2gsICJNdWx0aWNhc3QgQWNxdWlzaXRpb24g
UmVwb3J0DSAgICAgICAgICAgICAgQmxvY2sgVHlwZSBmb3IgUlRQIENvbnRyb2wgUHJvdG9jb2wg
KFJUQ1ApIEV4dGVuZGVkDSAgICAgICAgICAgICAgUmVwb3J0cyAoWFJzKSIsIFJGQyA2MzMyLCBK
dWx5IDIwMTEuDQ0gICBbWTE1NDBdICAgIElUVS1ULCAiSVRVLVQgUmVjLiBZLjE1NDAsIElQIHBh
Y2tldCB0cmFuc2ZlciBhbmQNICAgICAgICAgICAgICBhdmFpbGFiaWxpdHkgcGVyZm9ybWFuY2Ug
cGFyYW1ldGVycyIsIE5vdmVtYmVyIDIwMDcuDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0N
DQ0NV3UsIGV0IGFsLiAgICAgICAgICAgICAgICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAgICAg
ICAgICAgICAgW1BhZ2UgMjFdDQwNSW50ZXJuZXQtRHJhZnQgICAgICAgIFJUUCBNb25pdG9yaW5n
IEFyY2hpdGVjdHVyZXMgICAgICAgICBOb3ZlbWJlciAyMDExDQ0NQXBwZW5kaXggQS4gIENoYW5n
ZSBMb2cNDSAgIE5vdGUgdG8gdGhlIFJGQy1FZGl0b3I6IHBsZWFzZSByZW1vdmUgdGhpcyBzZWN0
aW9uIHByaW9yIHRvDSAgIHB1YmxpY2F0aW9uIGFzIGFuIFJGQy4NDUEuMS4gIGRyYWZ0LWlldGYt
YXZ0Y29yZS1tb25hcmNoLTAwDQ0gICBUaGUgZm9sbG93aW5nIGFyZSB0aGUgbWFqb3IgY2hhbmdl
cyBjb21wYXJlZCB0bw0gICBkcmFmdC1odW50LWF2dGNvcmUtbW9uYXJjaC0wMjoNDSAgIG8gIE1v
dmUgR2VvZmYgSHVudCBhbmQgUGhpbGlwIEFyZGVuIHRvIGFja25vd2xlZGdlbWVudCBzZWN0aW9u
Lg0NQS4yLiAgZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gtMDENDSAgIFRoZSBmb2xsb3dpbmcg
YXJlIHRoZSBtYWpvciBjaGFuZ2VzIGNvbXBhcmVkIHRvIDAwOg0NICAgbyAgUmVzdHJ1Y3R1cmUg
dGhlIGRvY3VtZW50IGJ5IG1lcmdpbmcgc2VjdGlvbiA0IGludG8gc2VjdGlvbiAzLg0NICAgbyAg
UmVtb3ZlIHNlY3Rpb24gNC4xLHNlY3Rpb24gNSB0aGF0IGlzIG91dCBvZiBzY29wZSBvZiB0aGlz
DSAgICAgIGRvY3VtZW50Lg0NICAgbyAgUmVtb3ZlIHRoZSBsYXN0IGJ1bGxldCBpbiBzZWN0aW9u
IDYgYW5kIHNlY3Rpb24gNy4zIGJhc2VkIG9uDSAgICAgIGNvbmNsdXNpb24gb2YgbGFzdCBtZWV0
aW5nLg0NICAgbyAgVXBkYXRlIGZpZ3VyZSAxIGFuZCByZWxhdGVkIHRleHQgaW4gc2VjdGlvbiAz
IGFjY29yZGluZyB0byB0aGUNICAgICAgbW9uaXRvciBkZWZpbml0aW9uIGluIFJGQzM1NTAuDQ0g
ICBvICBSZXZpc2Ugc2VjdGlvbiA5IHRvIGFkZHJlc3MgbW9uaXRvciBkZWNsYXJhdGlvbiBpc3N1
ZS4NDSAgIG8gIE1lcmdlIHRoZSBmaXJzdCB0d28gYnVsbGV0IGluIHNlY3Rpb24gNi4NDSAgIG8g
IEFkZCBvbmUgbmV3IGJ1bGxldCB0byBkaXNjdXNzIG1ldHJpYyBibG9jayBhc3NvY2lhdGlvbiBp
biBzZWN0aW9uDSAgICAgIDYuDQ1BLjMuICBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wMg0N
ICAgVGhlIGZvbGxvd2luZyBhcmUgdGhlIG1ham9yIGNoYW5nZXMgY29tcGFyZWQgdG8gMDE6DQ0g
ICBvICBEZWxldGluZyBmaXJzdCBwYXJhZ3JhcGggb2YgU2VjdGlvbiAxLg0NICAgbyAgRGVsZXRp
bmcgU2VjdGlvbiAzLjEsIHNpbmNlIHRoZSBpbnRlcmFjdGlvbiB3aXRoIHRoZSBtYW5hZ2VtZW50
DSAgICAgIGFwcGxpY2F0aW9uIGlzIG91dCBvZiBzY29wZSBvZiB0aGlzIGRyYWZ0Lg0NICAgbyAg
U2VwYXJhdGUgaWRlbnRpdHkgaW5mb3JtYXRpb24gY29ycmVsYXRpb24gZnJvbSBzZWN0aW9uIDUu
MiBhcyBuZXcNICAgICAgc2VjdGlvbiA1LjMuDQ0gICBvICBSZW1vdmUgZmlndXJlIDIgYW5kIHJl
bGF0ZWQgdGV4dCBmcm9tIHNlY3Rpb24gNS4yLg0NDQ0NV3UsIGV0IGFsLiAgICAgICAgICAgICAg
ICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAgICAgICAgICAgICAgW1BhZ2UgMjJdDQwNSW50ZXJu
ZXQtRHJhZnQgICAgICAgIFJUUCBNb25pdG9yaW5nIEFyY2hpdGVjdHVyZXMgICAgICAgICBOb3Zl
bWJlciAyMDExDQ0NICAgbyAgRWRpdG9yaWFsIGNoYW5nZXMgaW4gdGhlIHNlY3Rpb24gNCBhbmQg
dGhlIGZpcnN0IHBhcmFncmFwaCBvZg0gICAgICBzZWN0aW9uIDcuDQ1BLjQuICBkcmFmdC1pZXRm
LWF2dGNvcmUtbW9uYXJjaC0wMw0NICAgVGhlIGZvbGxvd2luZyBhcmUgdGhlIG1ham9yIGNoYW5n
ZXMgY29tcGFyZWQgdG8gMDI6DQ0gICBvICBVcGRhdGUgYnVsbGV0IDIgaW4gc2VjdGlvbiA0IHRv
IGV4cGxhaW4gdGhlIGlsbC1lZmZlY3Qgb2YgSWRlbnRpdHkNICAgICAgSW5mb3JtYXRpb24gZHVw
bGljYXRpb24uDQ0gICBvICBVcGRhdGUgYnVsbGV0IDMgaW4gc2VjdGlvbiA0IHRvIGV4cGxhaW4g
d2h5IENvcnJlbGF0aW5nIFJUQ1AgWFINICAgICAgd2l0aCB0aGUgbm9uLVJUUCBkYXRhIGlzIG5l
ZWRlZC4NDSAgIG8gIFVwZGF0ZSBzZWN0aW9uIDUuMiB0byBmb2N1cyBvbiBob3cgdG8gcmVkdWNl
IHRoZSBpZGVudGl0eQ0gICAgICBpbmZvcm1hdGlvbiByZXBldGl0aW9uDQ0gICBvICBVcGRhdGUg
c2VjdGlvbiA1LjMgdG8gZXhwbGFpbiBob3cgdG8gY29ycmVsYXRlIGlkZW50aXR5DSAgICAgIGlu
Zm9ybWF0aW9uIHdpdGggdGhlIG5vbi1SVFAgZGF0YQ0NQS41LiAgZHJhZnQtaWV0Zi1hdnRjb3Jl
LW1vbmFyY2gtMDQNDSAgIFRoZSBmb2xsb3dpbmcgYXJlIHRoZSBtYWpvciBjaGFuZ2VzIGNvbXBh
cmVkIHRvIDAzOg0NICAgbyAgVXBkYXRlIHNlY3Rpb24gNS4yIHRvIGNsYXJpZnkgdXNpbmcgU0RF
UyBwYWNrZXQgdG8gY2FycnkNICAgICAgY29ycmVsYXRpb24gaW5mb3JtYXRpb24uDQ0gICBvICBS
ZW1vdmUgc2VjdGlvbiA1LjMgc2luY2UgYWRkaXRpb25hbCBpZGVudGl0eSBpbmZvcm1hdGlvbiBn
b2VzIHRvDSAgICAgIFNERVMgcGFja2V0IGFuZCB1c2luZyBTU1JDIHRvIGlkZW50aWZ5IGVhY2gg
YmxvY2sgaXMgc3RhbmRhcmQgUlRQDSAgICAgIGZlYXR1cmUuDQ0gICBvICBTd2FwIHRoZSBsYXN0
IHR3byBwYXJhZ3JhcGhzIGluIHRoZSBzZWN0aW9uIDQgc2luY2UgaWRlbnRpdHkNICAgICAgaW5m
b3JtYXRpb24gZHVwbGljYXRpb24gY2FuIG5vdCBiZWVuIDEwMCUgYXZvaWRlZC4NDSAgIG8gIE90
aGVyIGVkaXRvcmlhbCBjaGFuZ2VzLg0NQS42LiAgZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gt
MDUNDSAgIFRoZSBmb2xsb3dpbmcgYXJlIHRoZSBtYWpvciBjaGFuZ2VzIGNvbXBhcmVkIHRvIDA0
Og0NICAgbyAgUmVwbGFjZSAiY2h1bmsiIHdpdGggIm5ldyBTREVTIGl0ZW0iLg0NICAgbyAgQWRk
IHRleHRzIGluIHNlY3VyaXR5IHNlY3Rpb24gdG8gZGlzY3Vzc2lvbiBwb3RlbnRpYWwgc2VjdXJp
dHkNICAgICAgaXNzdWVzLg0NICAgbyAgQWRkIG5ldyBzdWItc2VjdGlvbiA1LjMgdG8gZGlzY3Vz
cyBSZWR1Y2luZyBNZWFzdXJlbWVudA0gICAgICBpbmZvcm1hdGlvbiByZXBldGl0aW9uLg0NDQ0N
DVd1LCBldCBhbC4gICAgICAgICAgICAgICAgRXhwaXJlcyBKdW5lIDEsIDIwMTIgICAgICAgICAg
ICAgICAgIFtQYWdlIDIzXQ0MDUludGVybmV0LURyYWZ0ICAgICAgICBSVFAgTW9uaXRvcmluZyBB
cmNoaXRlY3R1cmVzICAgICAgICAgTm92ZW1iZXIgMjAxMQ0NDSAgIG8gIE90aGVyIGVkaXRvcmlh
bCBjaGFuZ2VzLg0NQS43LiAgZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gtMDYNDSAgIFRoZSBm
b2xsb3dpbmcgYXJlIHRoZSBtYWpvciBjaGFuZ2VzIGNvbXBhcmVkIHRvIDA1Og0NICAgbyAgU29t
ZSBlZGl0b3JpYWwgY2hhbmdlcy4NDUEuOC4gIGRyYWZ0LWlldGYtYXZ0Y29yZS1tb25hcmNoLTA3
DQ0gICBUaGUgZm9sbG93aW5nIGFyZSB0aGUgbWFqb3IgY2hhbmdlcyBjb21wYXJlZCB0byAwNjoN
DSAgIG8gIENsYXJpZnkgdGhlIFhSIGJsb2NrIGNvZGUgcG9pbnRzIGNvbnN1bXB0aW9uIGlzc3Vl
IGluIHRoZSBzZWN0aW9uDSAgICAgIDQgYW5kIG5ldyBzZWN0aW9uIDUuNC4NDSAgIG8gIE90aGVy
IGVkaXRvcmlhbCBjaGFuZ2VzLg0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDVd1
LCBldCBhbC4gICAgICAgICAgICAgICAgRXhwaXJlcyBKdW5lIDEsIDIwMTIgICAgICAgICAgICAg
ICAgIFtQYWdlIDI0XQ0MDUludGVybmV0LURyYWZ0ICAgICAgICBSVFAgTW9uaXRvcmluZyBBcmNo
aXRlY3R1cmVzICAgICAgICAgTm92ZW1iZXIgMjAxMQ0NDUF1dGhvcnMnIEFkZHJlc3Nlcw0NICAg
UWluIFd1IChlZGl0b3IpDSAgIEh1YXdlaQ0gICAxMDEgU29mdHdhcmUgQXZlbnVlLCBZdWh1YSBE
aXN0cmljdA0gICBOYW5qaW5nLCBKaWFuZ3N1ICAyMTAwMTINICAgQ2hpbmENDSAgIEVtYWlsOiBz
dW5zZWF3cUBodWF3ZWkuY29tDQ0NICAgR2VvZmYgSHVudA0gICBVbmFmZmlsaWF0ZWQNDSAgIEVt
YWlsOiByLmdlb2ZmLmh1bnRAZ21haWwuY29tDQ0NICAgUGhpbGlwIEFyZGVuDSAgIEJUDSAgIE9y
aW9uIDMvNyBQUDQNICAgQWRhc3RyYWwgUGFyaw0gICBNYXJ0bGVzaGFtIEhlYXRoDSAgIElwc3dp
Y2gsIFN1ZmZvbGsgIElQNSAzUkUNICAgVW5pdGVkIEtpbmdkb20NDSAgIFBob25lOiArNDQgMTQ3
MyA2NDQxOTINICAgRW1haWw6IHBoaWxpcC5hcmRlbkBidC5jb20NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0N
DQ0NDQ0NV3UsIGV0IGFsLiAgICAgICAgICAgICAgICBFeHBpcmVzIEp1bmUgMSwgMjAxMiAgICAg
ICAgICAgICAgICAgW1BhZ2UgMjVdDQwNDQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAAADCAAATAgAAN4IAAD2EAAAQREAABsjAABmIwAA
WCkAAJApAAC6KwAABSwAAHAsAAB2LAAAhiwAAIcsAADxMQAAUzIAAC0+AAAuPgAALz4AACJEAABt
RAAAm0UAAJ1FAACeRQAAoUUAANBFAADRRQAA7kUAAPxFAAAERgAASEYAAElGAAD57uPu2O7Y7tju
2O7Hucfu2O65n+7Y7o6AjoCOa1lrWe4AAAAAAAAAAAAjAQiBBEgBAAVo7GL8JhZoPVPJAG1ICQhu
SAcEc0gJCHRIBwQpAQiBBEgBAAVo7GL8JhVom2nPABZoPVPJAG1ICQhuSAcEc0gJCHRIBwQbAQiB
BEgBAAVo6mL8JhZom2nPAG1ICQhzSAkIIQEIgQRIAQAFaOpi/CYVaP9gmAAWaJtpzwBtSAkIc0gJ
CDMACIEVaP9gmAAWaDQ8rwAXaJtpzwBjSAEAZGgAAAAAZGgAAAAAZGjoYvwmbUgJCHNICQgbAQiB
BEgBAAVo6GL8JhZom2nPAG1ICQhzSAkIIQEIgQRIAQAFaOhi/CYVaP9gmAAWaJtpzwBtSAkIc0gJ
CBQVaP9gmAAWaDQ8rwBtSAwEc0gMBAAUFWj/YJgAFmg0PK8AbUgdBHNIHQQAFBVo/2CYABZoNDyv
AG1ICQhzSAkIAAwVaDQ8rwAWaDQ8rwAhAAYAAAEIAAACCAAAAwgAAEwIAACVCAAA3ggAACcJAABw
CQAAuQkAAAIKAAADCgAABAoAADkKAABuCgAAbwoAAHgKAAB5CgAAwgoAAAMLAABCCwAAiQsAAM8L
AAAUDAAAXQwAAKMMAADsDAAANA0AAHsNAACjDQAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAAAAAAABBIAZ2T/YJgAAB0ABgAAca4AAP0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAQEAAEBAaMNAACkDQAAuA0AALkNAAD6DQAAHg4AAB8OAABkDgAApg4A
AO4OAAArDwAALA8AAHUPAAC9DwAA/w8AAD0QAAA+EAAAchAAAHMQAACEEAAAhRAAAMgQAADzEAAA
9BAAAPUQAAD2EAAAPxEAAEERAACKEQAAixEAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAAAAAAAAQSAGdk/2CYAAAdixEAAIwRAADNEQAA9hEAADkSAAB5EgAAwhIAAAoTAABQEwAA
kxMAAL8TAADAEwAAwRMAANMTAADUEwAAHRQAAGYUAACvFAAA+BQAAEEVAACKFQAA0xUAABwWAABl
FgAArhYAAPcWAABAFwAAiRcAANIXAAAbGAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAAAAAAABBIAZ2T/YJgAAB0bGAAAZBgAAK0YAAD2GAAAPxkAAIgZAADRGQAAGhoAAGMaAACs
GgAA9RoAAD4bAACHGwAA0BsAANEbAADSGwAA0xsAANQbAADVGwAA1hsAANcbAADYGwAA2RsAANob
AAAjHAAAJRwAAG4cAABvHAAAcBwAAIEcAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAAAAAAAEEgBnZP9gmAAAHYEcAACCHAAAyxwAABIdAABYHQAAnh0AAOIdAAAkHgAAaR4AAKwe
AADuHgAAFh8AABcfAABfHwAAqB8AAPAfAAAtIAAAcyAAALYgAADhIAAA4iAAACMhAABqIQAAsiEA
APohAABCIgAAhyIAANAiAAAFIwAABiMAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAAAAAAAAQSAGdk/2CYAAAdBiMAAAcjAAAIIwAACSMAAAojAAALIwAADCMAAA0jAAAOIwAADyMA
ABAjAAARIwAAEiMAABMjAAAUIwAAFSMAABYjAAAXIwAAGCMAABkjAAAaIwAAGyMAAGQjAABmIwAA
ryMAALAjAACxIwAAyyMAAMwjAAAKJAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAAAAAAABBIAZ2T/YJgAAB0KJAAAGyQAABwkAABNJAAATiQAAGkkAABqJAAAqCQAAOkkAAAtJQAA
TSUAAE4lAABPJQAAbCUAAG0lAACyJQAA+iUAAEAmAACDJgAAhCYAAIUmAACbJgAAnCYAAN4mAAAm
JwAAaScAAKsnAACsJwAArScAAL8nAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
AAAAAAAEEgBnZP9gmAAAHb8nAADAJwAABigAACcoAAAoKAAAKSgAAD0oAAA+KAAAhigAALIoAACz
KAAAtCgAAMgoAADJKAAADSkAAFIpAABzKQAAdCkAAHUpAAB2KQAAvykAAMEpAAAKKgAACyoAAAwq
AAAiKgAAIyoAAGcqAACrKgAAvioAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
AAAAAAQSAGdk/2CYAAAdvioAAL8qAADAKgAA0yoAANQqAAAdKwAAZCsAAJMrAACUKwAAlSsAAJYr
AACXKwAAmCsAAJkrAACaKwAAmysAAJwrAACdKwAAnisAAJ8rAACgKwAAoSsAAKIrAACjKwAApCsA
AKUrAACmKwAApysAAKgrAACpKwAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAA
AAAABBIAZ2T/YJgAAB2pKwAAqisAAKsrAACsKwAArSsAAK4rAACvKwAAsCsAALErAACyKwAAsysA
ALQrAAC1KwAAtisAALcrAAC4KwAAuSsAALorAAADLAAABSwAAE4sAABPLAAAUCwAAHAsAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAEEgBnZP9gmAAAF3AsAACHLAAAiCwAAMssAADxLAAA8iwAAAAtAAABLQAAHi0AAB8tAABfLQAA
ni0AAOMtAAAsLgAAcC4AALkuAAD+LgAARy8AAIYvAADELwAA1S8AALcAAAAAAAAAAAAAAACyAAAA
AAAAAAAAAAAAsgAAAAAAAAAAAAAAALIAAAAAAAAAAAAAAACyAAAAAAAAAAAAAAAAsgAAAAAAAAAA
AAAAALIAAAAAAAAAAAAAAACyAAAAAAAAAAAAAAAAsgAAAAAAAAAAAAAAALIAAAAAAAAAAAAAAACy
AAAAAAAAAAAAAAAAsgAAAAAAAAAAAAAAALIAAAAAAAAAAAAAAACyAAAAAAAAAAAAAAAAsgAAAAAA
AAAAAAAAALIAAAAAAAAAAAAAAACyAAAAAAAAAAAAAAAAsgAAAAAAAAAAAAAAALIAAAAAAAAAAAAA
AACyAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAABHEgBDJAFFxoAAAAEA6GL8JgAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAGdkm2nPAAAU1S8AANYvAAAXMAAAXzAAAKcwAAC8MAAAvTAAANYwAADXMAAA9jAAAPcwAAAL
MQAADDEAACcxAAAoMQAARDEAAEUxAABfMQAAYDEAAKUxAADuMQAA/jEAAP8xAAAAMgAAATIAAAIy
AAADMgAABDIAAAUyAAAGMgAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAA
BBIAZ2T/YJgAAB0GMgAABzIAAAgyAABRMgAAUzIAAJwyAACdMgAAnjIAAMQyAAAEMwAARDMAAIQz
AADEMwAABDQAACo0AABjNAAAnDQAANw0AAAcNQAAXDUAAJw1AADCNQAA6DUAAPE1AAA4NgAAfzYA
AMY2AAANNwAAVDcAAJs3AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAE
EgBnZP9gmAAAHZs3AADiNwAAKTgAAHA4AAC3OAAA/jgAAEU5AACMOQAA0zkAABo6AABhOgAAqDoA
AO86AAA2OwAAfTsAAMQ7AAALPAAAUjwAAFM8AACMPAAAjTwAAMY8AADHPAAA9DwAAPU8AAAgPQAA
IT0AACI9AAAjPQAAJD0AAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQS
AGdk/2CYAAAdJD0AAG09AABvPQAAuD0AALk9AAC6PQAA4D0AAOE9AAAqPgAAKz4AAGU+AABmPgAA
qj4AAPI+AAAlPwAAJj8AAF4/AABfPwAAiz8AAIw/AAC3PwAAuD8AAOY/AADnPwAALUAAAD5AAAA/
QAAAgkAAAMRAAADTQAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIA
Z2T/YJgAAB3TQAAA1EAAAPlAAAD6QAAAHUEAAB5BAAA8QQAAPUEAAF5BAABfQQAApUEAAOtBAAAt
QgAAckIAALlCAADaQgAA20IAACJDAABHQwAASEMAAJFDAADWQwAAHUQAAB5EAAAfRAAAIEQAACFE
AAAiRAAAa0QAAG1EAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBn
ZP9gmAAAHW1EAAC2RAAAt0QAALhEAAAARQAAGUUAABpFAABhRQAAmEUAAJlFAACaRQAAm0UAANFF
AABJRgAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAACyAAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAEcSAEMkAUXGgAAAAQDqYvwmAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAZ2Sbac8AAAQSAGdk
/2CYAAANSUYAAG1GAACLRgAAlEYAAKxGAADrRgAAlUcAAKxHAACtRwAAwUcAAMJHAADERwAAxUcA
AOVHAADmRwAA6kcAAOtHAADsRwAAK0gAAFVIAACgSAAAkVQAANxUAADjxOPE48SoiW2JbYltiW1R
48RGO0Y7AAAAABQVaP9gmAAWaDQ8rwBtSAwEc0gMBAAUFWj/YJgAFmg0PK8AbUgJCHNICQgANwEI
gQRIAQAFaPFi/CYWaD1TyQBDShQAT0oDAFFKAwBeSgMAYUoUAG1ICQhuSAcEc0gJCHRIBwQ3AQiB
BEgBAAVo8GL8JhZoPVPJAENKFABPSgMAUUoDAF5KAwBhShQAbUgJCG5IBwRzSAkIdEgHBD0BCIEE
SAEABWjxYvwmFWibac8AFmg9U8kAQ0oUAE9KAwBRSgMAXkoDAGFKFABtSAkIbkgHBHNICQh0SAcE
NwEIgQRIAQAFaO9i/CYWaD1TyQBDShQAT0oDAFFKAwBeSgMAYUoUAG1ICQhuSAcEc0gJCHRIBwQ9
AQiBBEgBAAVo7mL8JhVom2nPABZoPVPJAENKFABPSgMAUUoDAF5KAwBhShQAbUgJCG5IBwRzSAkI
dEgHBDcBCIEESAEABWjuYvwmFmg9U8kAQ0oUAE9KAwBRSgMAXkoDAGFKFABtSAkIbkgHBHNICQh0
SAcEABZJRgAARUcAACtIAAAsSAAALUgAAC5IAAAvSAAAMEgAADFIAAAySAAAM0gAADRIAAA1SAAA
NkgAADdIAAA4SAAAOUgAADpIAAA7SAAAPEgAAD1IAACzAAAAAAAAAAAAAAAAswAAAAAAAAAAAAAA
AK4AAAAAAAAAAAAAAACuAAAAAAAAAAAAAAAArgAAAAAAAAAAAAAAAK4AAAAAAAAAAAAAAACuAAAA
AAAAAAAAAAAArgAAAAAAAAAAAAAAAK4AAAAAAAAAAAAAAACuAAAAAAAAAAAAAAAArgAAAAAAAAAA
AAAAAK4AAAAAAAAAAAAAAACuAAAAAAAAAAAAAAAArgAAAAAAAAAAAAAAAK4AAAAAAAAAAAAAAACu
AAAAAAAAAAAAAAAArgAAAAAAAAAAAAAAAK4AAAAAAAAAAAAAAACuAAAAAAAAAAAAAAAArgAAAAAA
AAAAAAAAAAAAAAAABBIAZ2T/YJgATAAANyQAOCQAQyQBRcaAAAABAO5i/CYAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIJABnZD1T
yQAAFD1IAAA+SAAAP0gAAEBIAABBSAAAQkgAAENIAABESAAARUgAAEZIAABHSAAASEgAAElIAABK
SAAAS0gAAExIAABNSAAATkgAAE9IAABQSAAAUUgAAFJIAABTSAAAVEgAAFVIAACeSAAAoEgAAOlI
AADqSAAA60gAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CY
AAAd60gAACpJAAArSQAAb0kAALVJAADHSQAAyEkAABFKAABXSgAAm0oAAOBKAAAkSwAAa0sAAK5L
AADySwAAMkwAAHlMAAC/TAAAwEwAAAdNAABPTQAAl00AAN5NAAAhTgAAZ04AAK9OAAD2TgAANk8A
AHtPAADDTwAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgA
AB3DTwAAClAAAEpQAACRUAAA2VAAACBRAABjUQAAq1EAAPJRAAAdUgAAHlIAAGJSAACqUgAA8lIA
ADZTAAB9UwAAvlMAAAdUAABKVAAAjlQAAI9UAACQVAAAkVQAANpUAADcVAAAJVUAACZVAAAnVQAA
a1UAAK5VAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAA
Ha5VAAD0VQAAO1YAAIJWAADJVgAA/VYAAP5WAABGVwAAjFcAANVXAAASWAAARVgAAEZYAABHWAAA
SFgAAElYAABKWAAAS1gAAExYAABNWAAATlgAAE9YAABQWAAAUVgAAFJYAABTWAAAVFgAAFVYAABW
WAAAV1gAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAd
V1gAAFhYAABZWAAAWlgAAFtYAABcWAAAXVgAAF5YAABfWAAAYFgAAGFYAABiWAAAY1gAAGRYAABl
WAAAZlgAAGdYAABoWAAAaVgAAGpYAABrWAAAtFgAALZYAAD/WAAAAFkAAAFZAAA4WQAAOVkAAFtZ
AABcWQAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB3c
VAAAa1gAALZYAADRYwAAHGQAABZuAAB1bgAAk4IAAP6CAACJiAAA1IgAAJWJAADgiQAAqZAAAPSQ
AAAwmQAAnJkAAKidAADznQAAkKMAANujAACPqQAAxqkAAOOrAAAurAAAXK0AAJStAAAlrgAAca4A
APXq9er16vXq9er16vXq9er16vXq9er16vXf9eoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABQVaP9gmAAWaDQ8
rwBtSB0Ec0gdBAAUFWj/YJgAFmg0PK8AbUgMBHNIDAQAFBVo/2CYABZoNDyvAG1ICQhzSAkIHFxZ
AACjWQAA6FkAACpaAABwWgAAt1oAAPxaAABCWwAAiVsAANFbAAAVXAAAXlwAAKFcAADpXAAAMF0A
AHRdAAC0XQAA9l0AADteAACEXgAAyF4AAPFeAADyXgAAOF8AAHxfAAC7XwAA/18AAEhgAACRYAAA
2mAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAd2mAA
AA9hAAAQYQAAQGEAAEFhAACJYQAAz2EAAA9iAABWYgAAmWIAAOJiAAD2YgAA92IAAD5jAACHYwAA
zmMAAM9jAADQYwAA0WMAABpkAAAcZAAAZWQAAGZkAABnZAAArmQAAO1kAAAyZQAAe2UAAMBlAAAJ
ZgAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB0JZgAA
UGYAAJRmAADbZgAAJGcAAGxnAACzZwAA92cAADRoAAA1aAAAZ2gAAGhoAACqaAAA8WgAADNpAAB7
aQAAwGkAAAZqAABKagAAk2oAANdqAAAbawAAYGsAAKVrAADtawAANGwAAHpsAACPbAAAkGwAALxs
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAHbxsAAC9
bAAABm0AAEptAACPbQAA020AABNuAAAhbgAAIm4AACNuAAAkbgAAJW4AACZuAAAnbgAAKG4AAClu
AAAqbgAAc24AAHVuAAC+bgAAv24AAMBuAADhbgAA4m4AAClvAABnbwAAd28AAHhvAADBbwAAB3AA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAdB3AAAEtw
AACUcAAA3HAAAB5xAABjcQAApHEAAO1xAAA2cgAAfHIAAMNyAAAJcwAAFXMAABZzAABdcwAAoHMA
AKFzAADLcwAAzHMAABJ0AAATdAAAVHQAAJp0AADNdAAAznQAABB1AABSdQAAmnUAAOF1AAAndgAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB0ndgAAb3YA
ALR2AAD6dgAAQXcAAIl3AACpdwAAqncAAKt3AACsdwAArXcAAK53AACvdwAAsHcAALF3AAD6dwAA
/HcAAEV4AABGeAAAR3gAAG54AABveAAAt3gAAP14AABCeQAAi3kAANF5AAAZegAAXnoAAKR6AAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAHaR6AADgegAA
KXsAAGx7AACzewAA/HsAAEB8AACBfAAAxnwAAAt9AABUfQAAmn0AAON9AAAlfgAAZ34AAH5+AAB/
fgAAx34AAA5/AABTfwAAan8AAGt/AACGfwAAh38AAM9/AAAUgAAAXIAAAKWAAADrgAAAM4EAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAdM4EAAHmBAADB
gQAACIIAAE+CAACQggAArYIAAK6CAACvggAAsIIAALGCAACyggAAs4IAAPyCAAD+ggAAR4MAAEiD
AABJgwAAbIMAAG2DAACygwAA7oMAADaEAAB/hAAAxYQAAAqFAABShQAAloUAANSFAAAahgAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB0ahgAAS4YAAEyG
AACPhgAA2IYAAB+HAABohwAAsYcAAPKHAAA0iAAAbIgAAG2IAABuiAAAb4gAAHCIAABxiAAAcogA
AHOIAAB0iAAAdYgAAHaIAAB3iAAAeIgAAHmIAAB6iAAAe4gAAHyIAAB9iAAAfogAAH+IAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAHX+IAACAiAAAgYgA
AIKIAACDiAAAhIgAAIWIAACGiAAAh4gAAIiIAACJiAAA0ogAANSIAAAdiQAAHokAAB+JAAA3iQAA
OIkAAGWJAABmiQAAZ4kAAGiJAABpiQAAaokAAGuJAABsiQAAbYkAAG6JAABviQAAcIkAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAdcIkAAHGJAAByiQAA
c4kAAHSJAAB1iQAAdokAAHeJAAB4iQAAeYkAAHqJAAB7iQAAfIkAAH2JAAB+iQAAf4kAAICJAACB
iQAAgokAAIOJAACEiQAAhYkAAIaJAACHiQAAiIkAAImJAACKiQAAi4kAAIyJAACNiQAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB2NiQAAjokAAI+JAACQ
iQAAkYkAAJKJAACTiQAAlIkAAJWJAADeiQAA4IkAACmKAAAqigAAK4oAAEeKAABIigAAj4oAANaK
AAAfiwAAZ4sAAKKLAACjiwAA5YsAAC2MAABzjAAAu4wAAAONAABMjQAAhY0AAIaNAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAHYaNAADMjQAAE44AAFeO
AACejgAAt44AALiOAAC5jgAAuo4AALuOAAC8jgAAvY4AAL6OAAC/jgAAwI4AAMGOAADCjgAAw44A
AMSOAADFjgAAxo4AAMeOAADIjgAAyY4AAMqOAADLjgAAzI4AAM2OAADOjgAAz44AAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAdz44AANCOAADRjgAA0o4A
ANOOAADUjgAA1Y4AAB6PAAAgjwAAaY8AAGqPAABrjwAAgI8AAIGPAADGjwAADJAAAFWQAAB8kAAA
fZAAAH6QAAB/kAAAgJAAAIGQAACCkAAAg5AAAISQAACFkAAAhpAAAIeQAACIkAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB2IkAAAiZAAAIqQAACLkAAA
jJAAAI2QAACOkAAAj5AAAJCQAACRkAAAkpAAAJOQAACUkAAAlZAAAJaQAACXkAAAmJAAAJmQAACa
kAAAm5AAAJyQAACdkAAAnpAAAJ+QAACgkAAAoZAAAKKQAACjkAAApJAAAKWQAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAHaWQAACmkAAAp5AAAKiQAACp
kAAA8pAAAPSQAAA9kQAAPpEAAD+RAABbkQAAXJEAAKSRAADrkQAAMpIAAEuSAABMkgAAi5IAAM+S
AAANkwAADpMAAE6TAACAkwAAgZMAAMeTAAD0kwAAMpQAAE6UAABPlAAAl5QAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAdl5QAAM+UAAAQlQAAKJUAACmV
AABylQAAuZUAANeVAADYlQAAFpYAAFOWAABUlgAAm5YAAN+WAADglgAAKJcAAFqXAABblwAAo5cA
AOyXAAAcmAAAHZgAAGaYAACTmAAAlJgAAN2YAAAimQAATZkAAE6ZAABPmQAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB1PmQAAUJkAAFGZAACamQAAnJkA
AOWZAADmmQAA55kAAC2aAABwmgAAq5oAAKyaAAD0mgAA9ZoAAD2bAAB/mwAAgJsAAMibAAALnAAA
RpwAAEecAACPnAAA0ZwAAASdAAAFnQAARZ0AAIidAACJnQAAip0AAIudAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAHYudAACMnQAAjZ0AAI6dAACPnQAA
kJ0AAJGdAACSnQAAk50AAJSdAACVnQAAlp0AAJedAACYnQAAmZ0AAJqdAACbnQAAnJ0AAJ2dAACe
nQAAn50AAKCdAAChnQAAop0AAKOdAACknQAApZ0AAKadAACnnQAAqJ0AAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAdqJ0AAPGdAADznQAAPJ4AAD2eAAA+
ngAAVp4AAFeeAACWngAAsJ4AALGeAADVngAA1p4AAAmfAAArnwAALJ8AAG+fAABwnwAAlJ8AAJWf
AADMnwAAzZ8AABGgAAASoAAAUqAAAGKgAABjoAAApqAAAMigAADJoAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB3JoAAADqEAADOhAAA0oQAAcaEAAHKh
AAChoQAAoqEAAOqhAADzoQAA9KEAABiiAAAZogAAUKIAAFGiAAB+ogAAf6IAAMWiAAD2ogAA96IA
AD+jAABSowAAU6MAAIyjAACNowAAjqMAAI+jAACQowAA2aMAANujAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAHdujAAAkpAAAJaQAACakAABqpAAAe6QA
AHykAACgpAAAoaQAANikAADZpAAAIqUAAEGlAABCpQAAiKUAAK+lAACwpQAA8KUAAA2mAAAOpgAA
TKYAAHSmAAB1pgAAmaYAAJqmAADRpgAA0qYAABGnAAAwpwAAMacAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAdMacAAHinAADApwAAz6cAANCnAAATqAAA
TKgAAE2oAABsqAAAbagAAJGoAACSqAAAyagAAMqoAAD2qAAA96gAADypAABKqQAAS6kAAImpAACn
qQAAqKkAAKmpAACqqQAAq6kAAKypAAD1qQAA96kAAECqAABBqgAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB1BqgAAQqoAAGGqAABiqgAAhqoAAIeqAAC+
qgAAv6oAAN2qAADeqgAAAqsAAAOrAAA6qwAAO6sAAIOrAACgqwAAoasAAMCrAADBqwAAwqsAAMOr
AADEqwAAxasAAMarAADHqwAAyKsAAMmrAADKqwAAy6sAAMyrAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAHcyrAADNqwAAzqsAAM+rAADQqwAA0asAANKr
AADTqwAA1KsAANWrAADWqwAA16sAANirAADZqwAA2qsAANurAADcqwAA3asAAN6rAADfqwAA4KsA
AOGrAADiqwAA46sAACysAAAurAAAd6wAAHisAAB5rAAAjKwAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAA
AAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAA
AAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6
AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAA
AAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAAAAAAAAQSAGdk/2CYAAAdjKwAAI2sAACgrAAAqqwAANGsAADtrAAA9qwA
APesAAAVrQAAFq0AABetAAAlrQAANa0AADatAABXrQAAWK0AAFmtAABprQAAb60AAICtAACRrQAA
pa0AAMKtAADUrQAA1a0AAO+tAAANrgAADq4AAA+uAAAQrgAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoA
AAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAA
AAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAA
APoAAAAAAAAAAAAAAAAAAAAABBIAZ2T/YJgAAB0QrgAAEa4AABKuAAATrgAAFK4AABWuAAAWrgAA
F64AABiuAAAZrgAAGq4AABuuAAAcrgAAHa4AAB6uAAAfrgAAIK4AACGuAAAirgAAI64AACSuAAAl
rgAAbq4AAHCuAABxrgAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAA
AAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAA
AAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA
+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA
AAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAEEgBnZP9gmAAAGDIAMZBoATpw/2CYAB+wgi4gsMZBIbCABCKwgAQj
kKAFJJCgBSWwAAAXsMQCGLDEAgyQxAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAIYCEwASAAEAnAAPAAQAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEgAAEDx/wIASAAMAAAAAAAA
AAAABgBOAG8AcgBtAGEAbAAAAAIAAAAgAENKFgBPSgQAUUoEAF9IAQRhShgAbUgHBHNIBwR0SAkE
AAAAAAAAAAAAAAAAAAAAAAAARABBQPL/oQBEAAwBAAAAAAAAAAAWAEQAZQBmAGEAdQBsAHQAIABQ
AGEAcgBhAGcAcgBhAHAAaAAgAEYAbwBuAHQAAAAAAFYAaUDz/7MAVgAMBQAAAAAAAAAADABUAGEA
YgBsAGUAIABOAG8AcgBtAGEAbAAAACAAOlYLABf2AwAANNYGAAEFAwAANNYGAAEKA2wAYfYDAAAC
AAsAAAAoAGsA9P/BACgAAAUAAAAAAAAAAAcATgBvACAATABpAHMAdAAAAAIADAAAAAAAmgD+TwEA
8gCaAAQAAADPfqIAAAAFAFsAQQBCAFMAXQAAAEkADwANxiwADjcCGgNuBKcENAalBsEH3AgTC0oN
gQ+4Ee8TJhYAAAAAAAAAAAAAAAAAABOkPAAUpDwANSQANyQAOCQAOUQCAEgkAAAsAEIqAkNKFABP
SgUAUEoGAFFKBQBhShQAbUgABG5IAARwaAAA/wBzSAkIdQgBYgD+T/EAAgFiAAQAAADPfqIAAAAI
AFsAUgBlAHMAdQBsAHQAXQAAAC0AEAAKJgALRgIADcYhDjcCGgNuBKcENAalBsEH3AgTC0oNgQ+4
Ee8TJhYBUwMAAAkAQioGcGj/AAAAAGwA/k/x/xIBbAAEAAAAz36iAAAADgBGAG8AcgBtAGEAdAB2
AG8AcgBsAGEAZwBlADEAAAAJABEACiYAC0YDAAAsAEIqBk9KBQBQSgYAUUoFAF9IAQRtSAAEbkgA
BHBo/wAAAHNICQh0SAkEdQgBRABaQAEAIgFEAAwEAAB5RCoAAAAKAFAAbABhAGkAbgAgAFQAZQB4
AHQAAAACABIAFABDShQAT0oDAFFKAwBeSgMAYUoUAAAAAABxpgAACAAAHAEABgD/////AAAAAAEA
AAACAAAAAwAAAEwAAACVAAAA3gAAACcBAABwAQAAuQEAAAICAAADAgAABAIAADkCAABuAgAAbwIA
AHgCAAB5AgAAwgIAAAMDAABCAwAAiQMAAM8DAAAUBAAAXQQAAKMEAADsBAAANAUAAHsFAACjBQAA
pAUAALgFAAC5BQAA+gUAAB4GAAAfBgAAZAYAAKYGAADuBgAAKwcAACwHAAB1BwAAvQcAAP8HAAA9
CAAAPggAAHIIAABzCAAAhAgAAIUIAADICAAA8wgAAPQIAAD1CAAA9ggAAD8JAABBCQAAigkAAIsJ
AACMCQAAzQkAAPYJAAA5CgAAeQoAAMIKAAAKCwAAUAsAAJMLAAC/CwAAwAsAAMELAADTCwAA1AsA
AB0MAABmDAAArwwAAPgMAABBDQAAig0AANMNAAAcDgAAZQ4AAK4OAAD3DgAAQA8AAIkPAADSDwAA
GxAAAGQQAACtEAAA9hAAAD8RAACIEQAA0REAABoSAABjEgAArBIAAPUSAAA+EwAAhxMAANATAADR
EwAA0hMAANMTAADUEwAA1RMAANYTAADXEwAA2BMAANkTAADaEwAAIxQAACUUAABuFAAAbxQAAHAU
AACBFAAAghQAAMsUAAASFQAAWBUAAJ4VAADiFQAAJBYAAGkWAACsFgAA7hYAABYXAAAXFwAAXxcA
AKgXAADwFwAALRgAAHMYAAC2GAAA4RgAAOIYAAAjGQAAahkAALIZAAD6GQAAQhoAAIcaAADQGgAA
BRsAAAYbAAAHGwAACBsAAAkbAAAKGwAACxsAAAwbAAANGwAADhsAAA8bAAAQGwAAERsAABIbAAAT
GwAAFBsAABUbAAAWGwAAFxsAABgbAAAZGwAAGhsAABsbAABkGwAAZhsAAK8bAACwGwAAsRsAAMsb
AADMGwAAChwAABscAAAcHAAATRwAAE4cAABpHAAAahwAAKgcAADpHAAALR0AAE0dAABOHQAATx0A
AGwdAABtHQAAsh0AAPodAABAHgAAgx4AAIQeAACFHgAAmx4AAJweAADeHgAAJh8AAGkfAACrHwAA
rB8AAK0fAAC/HwAAwB8AAAYgAAAnIAAAKCAAACkgAAA9IAAAPiAAAIYgAACyIAAAsyAAALQgAADI
IAAAySAAAA0hAABSIQAAcyEAAHQhAAB1IQAAdiEAAL8hAADBIQAACiIAAAsiAAAMIgAAIiIAACMi
AABnIgAAqyIAAL4iAAC/IgAAwCIAANMiAADUIgAAHSMAAGQjAACTIwAAlCMAAJUjAACWIwAAlyMA
AJgjAACZIwAAmiMAAJsjAACcIwAAnSMAAJ4jAACfIwAAoCMAAKEjAACiIwAAoyMAAKQjAAClIwAA
piMAAKcjAACoIwAAqSMAAKojAACrIwAArCMAAK0jAACuIwAAryMAALAjAACxIwAAsiMAALMjAAC0
IwAAtSMAALYjAAC3IwAAuCMAALkjAAC6IwAAAyQAAAUkAABOJAAATyQAAFAkAABwJAAAhyQAAIgk
AADLJAAA8SQAAPIkAAAAJQAAASUAAB4lAAAfJQAAXyUAAJ4lAADjJQAALCYAAHAmAAC5JgAA/iYA
AEcnAACGJwAAxCcAANUnAADWJwAAFygAAF8oAACnKAAAvCgAAL0oAADWKAAA1ygAAPYoAAD3KAAA
CykAAAwpAAAnKQAAKCkAAEQpAABFKQAAXykAAGApAAClKQAA7ikAAP4pAAD/KQAAACoAAAEqAAAC
KgAAAyoAAAQqAAAFKgAABioAAAcqAAAIKgAAUSoAAFMqAACcKgAAnSoAAJ4qAADEKgAABCsAAEQr
AACEKwAAxCsAAAQsAAAqLAAAYywAAJwsAADcLAAAHC0AAFwtAACcLQAAwi0AAOgtAADxLQAAOC4A
AH8uAADGLgAADS8AAFQvAACbLwAA4i8AACkwAABwMAAAtzAAAP4wAABFMQAAjDEAANMxAAAaMgAA
YTIAAKgyAADvMgAANjMAAH0zAADEMwAACzQAAFI0AABTNAAAjDQAAI00AADGNAAAxzQAAPQ0AAD1
NAAAIDUAACE1AAAiNQAAIzUAACQ1AABtNQAAbzUAALg1AAC5NQAAujUAAOA1AADhNQAAKjYAACs2
AABlNgAAZjYAAKo2AADyNgAAJTcAACY3AABeNwAAXzcAAIs3AACMNwAAtzcAALg3AADmNwAA5zcA
AC04AAA+OAAAPzgAAII4AADEOAAA0zgAANQ4AAD5OAAA+jgAAB05AAAeOQAAPDkAAD05AABeOQAA
XzkAAKU5AADrOQAALToAAHI6AAC5OgAA2joAANs6AAAiOwAARzsAAEg7AACROwAA1jsAAB08AAAe
PAAAHzwAACA8AAAhPAAAIjwAAGs8AABtPAAAtjwAALc8AAC4PAAAAD0AABk9AAAaPQAAYT0AAJg9
AACZPQAAmj0AAJs9AADRPQAAST4AACxAAAAtQAAALkAAAC9AAAAwQAAAMUAAADJAAAAzQAAANEAA
ADVAAAA2QAAAN0AAADhAAAA5QAAAOkAAADtAAAA8QAAAPUAAAD5AAAA/QAAAQEAAAEFAAABCQAAA
Q0AAAERAAABFQAAARkAAAEdAAABIQAAASUAAAEpAAABLQAAATEAAAE1AAABOQAAAT0AAAFBAAABR
QAAAUkAAAFNAAABUQAAAVUAAAJ5AAACgQAAA6UAAAOpAAADrQAAAKkEAACtBAABvQQAAtUEAAMdB
AADIQQAAEUIAAFdCAACbQgAA4EIAACRDAABrQwAArkMAAPJDAAAyRAAAeUQAAL9EAADARAAAB0UA
AE9FAACXRQAA3kUAACFGAABnRgAAr0YAAPZGAAA2RwAAe0cAAMNHAAAKSAAASkgAAJFIAADZSAAA
IEkAAGNJAACrSQAA8kkAAB1KAAAeSgAAYkoAAKpKAADySgAANksAAH1LAAC+SwAAB0wAAEpMAACO
TAAAj0wAAJBMAACRTAAA2kwAANxMAAAlTQAAJk0AACdNAABrTQAArk0AAPRNAAA7TgAAgk4AAMlO
AAD9TgAA/k4AAEZPAACMTwAA1U8AABJQAABFUAAARlAAAEdQAABIUAAASVAAAEpQAABLUAAATFAA
AE1QAABOUAAAT1AAAFBQAABRUAAAUlAAAFNQAABUUAAAVVAAAFZQAABXUAAAWFAAAFlQAABaUAAA
W1AAAFxQAABdUAAAXlAAAF9QAABgUAAAYVAAAGJQAABjUAAAZFAAAGVQAABmUAAAZ1AAAGhQAABp
UAAAalAAAGtQAAC0UAAAtlAAAP9QAAAAUQAAAVEAADhRAAA5UQAAW1EAAFxRAACjUQAA6FEAACpS
AABwUgAAt1IAAPxSAABCUwAAiVMAANFTAAAVVAAAXlQAAKFUAADpVAAAMFUAAHRVAAC0VQAA9lUA
ADtWAACEVgAAyFYAAPFWAADyVgAAOFcAAHxXAAC7VwAA/1cAAEhYAACRWAAA2lgAAA9ZAAAQWQAA
QFkAAEFZAACJWQAAz1kAAA9aAABWWgAAmVoAAOJaAAD2WgAA91oAAD5bAACHWwAAzlsAAM9bAADQ
WwAA0VsAABpcAAAcXAAAZVwAAGZcAABnXAAArlwAAO1cAAAyXQAAe10AAMBdAAAJXgAAUF4AAJRe
AADbXgAAJF8AAGxfAACzXwAA918AADRgAAA1YAAAZ2AAAGhgAACqYAAA8WAAADNhAAB7YQAAwGEA
AAZiAABKYgAAk2IAANdiAAAbYwAAYGMAAKVjAADtYwAANGQAAHpkAACPZAAAkGQAALxkAAC9ZAAA
BmUAAEplAACPZQAA02UAABNmAAAhZgAAImYAACNmAAAkZgAAJWYAACZmAAAnZgAAKGYAAClmAAAq
ZgAAc2YAAHVmAAC+ZgAAv2YAAMBmAADhZgAA4mYAAClnAABnZwAAd2cAAHhnAADBZwAAB2gAAEto
AACUaAAA3GgAAB5pAABjaQAApGkAAO1pAAA2agAAfGoAAMNqAAAJawAAFWsAABZrAABdawAAoGsA
AKFrAADLawAAzGsAABJsAAATbAAAVGwAAJpsAADNbAAAzmwAABBtAABSbQAAmm0AAOFtAAAnbgAA
b24AALRuAAD6bgAAQW8AAIlvAACpbwAAqm8AAKtvAACsbwAArW8AAK5vAACvbwAAsG8AALFvAAD6
bwAA/G8AAEVwAABGcAAAR3AAAG5wAABvcAAAt3AAAP1wAABCcQAAi3EAANFxAAAZcgAAXnIAAKRy
AADgcgAAKXMAAGxzAACzcwAA/HMAAEB0AACBdAAAxnQAAAt1AABUdQAAmnUAAON1AAAldgAAZ3YA
AH52AAB/dgAAx3YAAA53AABTdwAAancAAGt3AACGdwAAh3cAAM93AAAUeAAAXHgAAKV4AADreAAA
M3kAAHl5AADBeQAACHoAAE96AACQegAArXoAAK56AACvegAAsHoAALF6AACyegAAs3oAAPx6AAD+
egAAR3sAAEh7AABJewAAbHsAAG17AACyewAA7nsAADZ8AAB/fAAAxXwAAAp9AABSfQAAln0AANR9
AAAafgAAS34AAEx+AACPfgAA2H4AAB9/AABofwAAsX8AAPJ/AAA0gAAAbIAAAG2AAABugAAAb4AA
AHCAAABxgAAAcoAAAHOAAAB0gAAAdYAAAHaAAAB3gAAAeIAAAHmAAAB6gAAAe4AAAHyAAAB9gAAA
foAAAH+AAACAgAAAgYAAAIKAAACDgAAAhIAAAIWAAACGgAAAh4AAAIiAAACJgAAA0oAAANSAAAAd
gQAAHoEAAB+BAAA3gQAAOIEAAGWBAABmgQAAZ4EAAGiBAABpgQAAaoEAAGuBAABsgQAAbYEAAG6B
AABvgQAAcIEAAHGBAABygQAAc4EAAHSBAAB1gQAAdoEAAHeBAAB4gQAAeYEAAHqBAAB7gQAAfIEA
AH2BAAB+gQAAf4EAAICBAACBgQAAgoEAAIOBAACEgQAAhYEAAIaBAACHgQAAiIEAAImBAACKgQAA
i4EAAIyBAACNgQAAjoEAAI+BAACQgQAAkYEAAJKBAACTgQAAlIEAAJWBAADegQAA4IEAACmCAAAq
ggAAK4IAAEeCAABIggAAj4IAANaCAAAfgwAAZ4MAAKKDAACjgwAA5YMAAC2EAABzhAAAu4QAAAOF
AABMhQAAhYUAAIaFAADMhQAAE4YAAFeGAACehgAAt4YAALiGAAC5hgAAuoYAALuGAAC8hgAAvYYA
AL6GAAC/hgAAwIYAAMGGAADChgAAw4YAAMSGAADFhgAAxoYAAMeGAADIhgAAyYYAAMqGAADLhgAA
zIYAAM2GAADOhgAAz4YAANCGAADRhgAA0oYAANOGAADUhgAA1YYAAB6HAAAghwAAaYcAAGqHAABr
hwAAgIcAAIGHAADGhwAADIgAAFWIAAB8iAAAfYgAAH6IAAB/iAAAgIgAAIGIAACCiAAAg4gAAISI
AACFiAAAhogAAIeIAACIiAAAiYgAAIqIAACLiAAAjIgAAI2IAACOiAAAj4gAAJCIAACRiAAAkogA
AJOIAACUiAAAlYgAAJaIAACXiAAAmIgAAJmIAACaiAAAm4gAAJyIAACdiAAAnogAAJ+IAACgiAAA
oYgAAKKIAACjiAAApIgAAKWIAACmiAAAp4gAAKiIAACpiAAA8ogAAPSIAAA9iQAAPokAAD+JAABb
iQAAXIkAAKSJAADriQAAMooAAEuKAABMigAAi4oAAM+KAAANiwAADosAAE6LAACAiwAAgYsAAMeL
AAD0iwAAMowAAE6MAABPjAAAl4wAAM+MAAAQjQAAKI0AACmNAAByjQAAuY0AANeNAADYjQAAFo4A
AFOOAABUjgAAm44AAN+OAADgjgAAKI8AAFqPAABbjwAAo48AAOyPAAAckAAAHZAAAGaQAACTkAAA
lJAAAN2QAAAikQAATZEAAE6RAABPkQAAUJEAAFGRAACakQAAnJEAAOWRAADmkQAA55EAAC2SAABw
kgAAq5IAAKySAAD0kgAA9ZIAAD2TAAB/kwAAgJMAAMiTAAALlAAARpQAAEeUAACPlAAA0ZQAAASV
AAAFlQAARZUAAIiVAACJlQAAipUAAIuVAACMlQAAjZUAAI6VAACPlQAAkJUAAJGVAACSlQAAk5UA
AJSVAACVlQAAlpUAAJeVAACYlQAAmZUAAJqVAACblQAAnJUAAJ2VAACelQAAn5UAAKCVAAChlQAA
opUAAKOVAACklQAApZUAAKaVAACnlQAAqJUAAPGVAADzlQAAPJYAAD2WAAA+lgAAVpYAAFeWAACW
lgAAsJYAALGWAADVlgAA1pYAAAmXAAArlwAALJcAAG+XAABwlwAAlJcAAJWXAADMlwAAzZcAABGY
AAASmAAAUpgAAGKYAABjmAAAppgAAMiYAADJmAAADpkAADOZAAA0mQAAcZkAAHKZAAChmQAAopkA
AOqZAADzmQAA9JkAABiaAAAZmgAAUJoAAFGaAAB+mgAAf5oAAMWaAAD2mgAA95oAAD+bAABSmwAA
U5sAAIybAACNmwAAjpsAAI+bAACQmwAA2ZsAANubAAAknAAAJZwAACacAABqnAAAe5wAAHycAACg
nAAAoZwAANicAADZnAAAIp0AAEGdAABCnQAAiJ0AAK+dAACwnQAA8J0AAA2eAAAOngAATJ4AAHSe
AAB1ngAAmZ4AAJqeAADRngAA0p4AABGfAAAwnwAAMZ8AAHifAADAnwAAz58AANCfAAAToAAATKAA
AE2gAABsoAAAbaAAAJGgAACSoAAAyaAAAMqgAAD2oAAA96AAADyhAABKoQAAS6EAAImhAACnoQAA
qKEAAKmhAACqoQAAq6EAAKyhAAD1oQAA96EAAECiAABBogAAQqIAAGGiAABiogAAhqIAAIeiAAC+
ogAAv6IAAN2iAADeogAAAqMAAAOjAAA6owAAO6MAAIOjAACgowAAoaMAAMCjAADBowAAwqMAAMOj
AADEowAAxaMAAMajAADHowAAyKMAAMmjAADKowAAy6MAAMyjAADNowAAzqMAAM+jAADQowAA0aMA
ANKjAADTowAA1KMAANWjAADWowAA16MAANijAADZowAA2qMAANujAADcowAA3aMAAN6jAADfowAA
4KMAAOGjAADiowAA46MAACykAAAupAAAd6QAAHikAAB5pAAAjKQAAI2kAACgpAAAqqQAANGkAADt
pAAA9qQAAPekAAAVpQAAFqUAABelAAAlpQAANaUAADalAABXpQAAWKUAAFmlAABppQAAb6UAAICl
AACRpQAApaUAAMKlAADUpQAA1aUAAO+lAAANpgAADqYAAA+mAAAQpgAAEaYAABKmAAATpgAAFKYA
ABWmAAAWpgAAF6YAABimAAAZpgAAGqYAABumAAAcpgAAHaYAAB6mAAAfpgAAIKYAACGmAAAipgAA
I6YAACSmAAAlpgAAbqYAAHCmAABzpgAAmAAAABIwAAAAAAAAAIAAAACAAAAA6AAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACaQAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAJAHmgAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgAGYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJoAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgAeYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJpAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAkAeaAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAHmgAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAB5gAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACaAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAHmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
gACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAgACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAIAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAACAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAgAAAAAAAAQAAAAIAAAADAAAATAAAAJUA
AADeAAAAJwEAAHABAAC5AQAAAgIAAAMCAAAEAgAAOQIAAG4CAABvAgAAeAIAAHkCAADCAgAAAwMA
AEIDAACJAwAAzwMAABQEAABdBAAAowQAAOwEAAA0BQAAewUAAKMFAACkBQAAuAUAALkFAAD6BQAA
HgYAAB8GAABkBgAApgYAAO4GAAArBwAALAcAAHUHAAC9BwAA/wcAAD0IAAA+CAAAcggAAHMIAACE
CAAAhQgAAMgIAADzCAAA9AgAAPUIAAD2CAAAPwkAAEEJAACKCQAAiwkAAIwJAADNCQAA9gkAADkK
AAB5CgAAwgoAAAoLAABQCwAAkwsAAL8LAADACwAAwQsAANMLAADUCwAAHQwAAGYMAACvDAAA+AwA
AEENAACKDQAA0w0AABwOAABlDgAArg4AAPcOAABADwAAiQ8AANIPAAAbEAAAZBAAAK0QAAD2EAAA
PxEAAIgRAADREQAAGhIAAGMSAACsEgAA9RIAAD4TAACHEwAA0BMAANETAADSEwAA0xMAANQTAADV
EwAA1hMAANcTAADYEwAA2RMAANoTAAAjFAAAJRQAAG4UAABvFAAAcBQAAIEUAACCFAAAyxQAABIV
AABYFQAAnhUAAOIVAAAkFgAAaRYAAKwWAADuFgAAFhcAABcXAABfFwAAqBcAAPAXAAAtGAAAcxgA
ALYYAADhGAAA4hgAACMZAABqGQAAshkAAPoZAABCGgAAhxoAANAaAAAFGwAABhsAAAcbAAAIGwAA
CRsAAAobAAALGwAADBsAAA0bAAAOGwAADxsAABAbAAARGwAAEhsAABMbAAAUGwAAFRsAABYbAAAX
GwAAGBsAABkbAAAaGwAAGxsAAGQbAABmGwAArxsAALAbAACxGwAAyxsAAMwbAAAKHAAAGxwAABwc
AABNHAAAThwAAGkcAABqHAAAqBwAAOkcAAAtHQAATR0AAE4dAABPHQAAbB0AAG0dAACyHQAA+h0A
AEAeAACDHgAAhB4AAIUeAACbHgAAnB4AAN4eAAAmHwAAaR8AAKsfAACsHwAArR8AAL8fAADAHwAA
BiAAACcgAAAoIAAAKSAAAD0gAAA+IAAAhiAAALIgAACzIAAAtCAAAMggAADJIAAADSEAAFIhAABz
IQAAdCEAAHUhAAB2IQAAvyEAAMEhAAAKIgAACyIAAAwiAAAiIgAAIyIAAGciAACrIgAAviIAAL8i
AADAIgAA0yIAANQiAAAdIwAAZCMAAJMjAACUIwAAlSMAAJYjAACXIwAAmCMAAJkjAACaIwAAmyMA
AJwjAACdIwAAniMAAJ8jAACgIwAAoSMAAKIjAACjIwAApCMAAKUjAACmIwAApyMAAKgjAACpIwAA
qiMAAKsjAACsIwAArSMAAK4jAACvIwAAsCMAALEjAACyIwAAsyMAALQjAAC1IwAAtiMAALcjAAC4
IwAAuSMAALojAAADJAAABSQAAE4kAABPJAAAUCQAAHAkAACHJAAAiCQAAMskAADxJAAA8iQAAAAl
AAABJQAAHiUAAB8lAABfJQAAniUAAOMlAAAsJgAAcCYAALkmAAD+JgAARycAAIYnAADEJwAA1ScA
ANYnAAAXKAAAXygAAKcoAAC8KAAAvSgAANYoAADXKAAA9igAAPcoAAALKQAADCkAACcpAAAoKQAA
RCkAAEUpAABfKQAAYCkAAKUpAADuKQAA/ikAAP8pAAAAKgAAASoAAAIqAAADKgAABCoAAAUqAAAG
KgAAByoAAAgqAABRKgAAUyoAAJwqAACdKgAAnioAAMQqAAAEKwAARCsAAIQrAADEKwAABCwAACos
AABjLAAAnCwAANwsAAAcLQAAXC0AAJwtAADCLQAA6C0AAPEtAAA4LgAAfy4AAMYuAAANLwAAVC8A
AJsvAADiLwAAKTAAAHAwAAC3MAAA/jAAAEUxAACMMQAA0zEAABoyAABhMgAAqDIAAO8yAAA2MwAA
fTMAAMQzAAALNAAAUjQAAFM0AACMNAAAjTQAAMY0AADHNAAA9DQAAPU0AAAgNQAAITUAACI1AAAj
NQAAJDUAAG01AABvNQAAuDUAALk1AAC6NQAA4DUAAOE1AAAqNgAAKzYAAGU2AABmNgAAqjYAAPI2
AAAlNwAAJjcAAF43AABfNwAAizcAAIw3AAC3NwAAuDcAAOY3AADnNwAALTgAAD44AAA/OAAAgjgA
AMQ4AADTOAAA1DgAAPk4AAD6OAAAHTkAAB45AAA8OQAAPTkAAF45AABfOQAApTkAAOs5AAAtOgAA
cjoAALk6AADaOgAA2zoAACI7AABHOwAASDsAAJE7AADWOwAAHTwAAB48AAAfPAAAIDwAACE8AAAi
PAAAazwAAG08AAC2PAAAtzwAALg8AAAAPQAAGT0AABo9AABhPQAAmD0AAJk9AACaPQAAmz0AANE9
AABJPgAART8AACtAAAAsQAAALUAAAC5AAAAvQAAAMEAAADFAAAAyQAAAM0AAADRAAAA1QAAANkAA
ADdAAAA4QAAAOUAAADpAAAA7QAAAPEAAAD1AAAA+QAAAP0AAAEBAAABBQAAAQkAAAENAAABEQAAA
RUAAAEZAAABHQAAASEAAAElAAABKQAAAS0AAAExAAABNQAAATkAAAE9AAABQQAAAUUAAAFJAAABT
QAAAVEAAAFVAAACeQAAAoEAAAOlAAADqQAAA60AAACpBAAArQQAAb0EAALVBAADHQQAAyEEAABFC
AABXQgAAm0IAAOBCAAAkQwAAa0MAAK5DAADyQwAAMkQAAHlEAAC/RAAAwEQAAAdFAABPRQAAl0UA
AN5FAAAhRgAAZ0YAAK9GAAD2RgAANkcAAHtHAADDRwAACkgAAEpIAACRSAAA2UgAACBJAABjSQAA
q0kAAPJJAAAdSgAAHkoAAGJKAACqSgAA8koAADZLAAB9SwAAvksAAAdMAABKTAAAjkwAAI9MAACQ
TAAAkUwAANpMAADcTAAAJU0AACZNAAAnTQAAa00AAK5NAAD0TQAAO04AAIJOAADJTgAA/U4AAP5O
AABGTwAAjE8AANVPAAASUAAARVAAAEZQAABHUAAASFAAAElQAABKUAAAS1AAAExQAABNUAAATlAA
AE9QAABQUAAAUVAAAFJQAABTUAAAVFAAAFVQAABWUAAAV1AAAFhQAABZUAAAWlAAAFtQAABcUAAA
XVAAAF5QAABfUAAAYFAAAGFQAABiUAAAY1AAAGRQAABlUAAAZlAAAGdQAABoUAAAaVAAAGpQAABr
UAAAtFAAALZQAAD/UAAAAFEAAAFRAAA4UQAAOVEAAFtRAABcUQAAo1EAAOhRAAAqUgAAcFIAALdS
AAD8UgAAQlMAAIlTAADRUwAAFVQAAF5UAAChVAAA6VQAADBVAAB0VQAAtFUAAPZVAAA7VgAAhFYA
AMhWAADxVgAA8lYAADhXAAB8VwAAu1cAAP9XAABIWAAAkVgAANpYAAAPWQAAEFkAAEBZAABBWQAA
iVkAAM9ZAAAPWgAAVloAAJlaAADiWgAA9loAAPdaAAA+WwAAh1sAAM5bAADPWwAA0FsAANFbAAAa
XAAAHFwAAGVcAABmXAAAZ1wAAK5cAADtXAAAMl0AAHtdAADAXQAACV4AAFBeAACUXgAA214AACRf
AABsXwAAs18AAPdfAAA0YAAANWAAAGdgAABoYAAAqmAAAPFgAAAzYQAAe2EAAMBhAAAGYgAASmIA
AJNiAADXYgAAG2MAAGBjAAClYwAA7WMAADRkAAB6ZAAAj2QAAJBkAAC8ZAAAvWQAAAZlAABKZQAA
j2UAANNlAAATZgAAIWYAACJmAAAjZgAAJGYAACVmAAAmZgAAJ2YAAChmAAApZgAAKmYAAHNmAAB1
ZgAAvmYAAL9mAADAZgAA4WYAAOJmAAApZwAAZ2cAAHdnAAB4ZwAAwWcAAAdoAABLaAAAlGgAANxo
AAAeaQAAY2kAAKRpAADtaQAANmoAAHxqAADDagAACWsAABVrAAAWawAAXWsAAKBrAAChawAAy2sA
AMxrAAASbAAAE2wAAFRsAACabAAAzWwAAM5sAAAQbQAAUm0AAJptAADhbQAAJ24AAG9uAAC0bgAA
+m4AAEFvAACJbwAAqW8AAKpvAACrbwAArG8AAK1vAACubwAAr28AALBvAACxbwAA+m8AAPxvAABF
cAAARnAAAEdwAABucAAAb3AAALdwAAD9cAAAQnEAAItxAADRcQAAGXIAAF5yAACkcgAA4HIAAClz
AABscwAAs3MAAPxzAABAdAAAgXQAAMZ0AAALdQAAVHUAAJp1AADjdQAAJXYAAGd2AAB+dgAAf3YA
AMd2AAAOdwAAU3cAAGp3AABrdwAAhncAAId3AADPdwAAFHgAAFx4AACleAAA63gAADN5AAB5eQAA
wXkAAAh6AABPegAAkHoAAK16AACuegAAr3oAALB6AACxegAAsnoAALN6AAD8egAA/noAAEd7AABI
ewAASXsAAGx7AABtewAAsnsAAO57AAA2fAAAf3wAAMV8AAAKfQAAUn0AAJZ9AADUfQAAGn4AAEt+
AABMfgAAj34AANh+AAAffwAAaH8AALF/AADyfwAANIAAAGyAAABtgAAAboAAAG+AAABwgAAAcYAA
AHKAAABzgAAAdIAAAHWAAAB2gAAAd4AAAHiAAAB5gAAAeoAAAHuAAAB8gAAAfYAAAH6AAAB/gAAA
gIAAAIGAAACCgAAAg4AAAISAAACFgAAAhoAAAIeAAACIgAAAiYAAANKAAADUgAAAHYEAAB6BAAAf
gQAAN4EAADiBAABlgQAAZoEAAGeBAABogQAAaYEAAGqBAABrgQAAbIEAAG2BAABugQAAb4EAAHCB
AABxgQAAcoEAAHOBAAB0gQAAdYEAAHaBAAB3gQAAeIEAAHmBAAB6gQAAe4EAAHyBAAB9gQAAfoEA
AH+BAACAgQAAgYEAAIKBAACDgQAAhIEAAIWBAACGgQAAh4EAAIiBAACJgQAAioEAAIuBAACMgQAA
jYEAAI6BAACPgQAAkIEAAJGBAACSgQAAk4EAAJSBAACVgQAA3oEAAOCBAAApggAAKoIAACuCAABH
ggAASIIAAI+CAADWggAAH4MAAGeDAACigwAAo4MAAOWDAAAthAAAc4QAALuEAAADhQAATIUAAIWF
AACGhQAAzIUAABOGAABXhgAAnoYAALeGAAC4hgAAuYYAALqGAAC7hgAAvIYAAL2GAAC+hgAAv4YA
AMCGAADBhgAAwoYAAMOGAADEhgAAxYYAAMaGAADHhgAAyIYAAMmGAADKhgAAy4YAAMyGAADNhgAA
zoYAAM+GAADQhgAA0YYAANKGAADThgAA1IYAANWGAAAehwAAIIcAAGmHAABqhwAAa4cAAICHAACB
hwAAxocAAAyIAABViAAAfIgAAH2IAAB+iAAAf4gAAICIAACBiAAAgogAAIOIAACEiAAAhYgAAIaI
AACHiAAAiIgAAImIAACKiAAAi4gAAIyIAACNiAAAjogAAI+IAACQiAAAkYgAAJKIAACTiAAAlIgA
AJWIAACWiAAAl4gAAJiIAACZiAAAmogAAJuIAACciAAAnYgAAJ6IAACfiAAAoIgAAKGIAACiiAAA
o4gAAKSIAACliAAApogAAKeIAACoiAAAqYgAAPKIAAD0iAAAPYkAAD6JAAA/iQAAW4kAAFyJAACk
iQAA64kAADKKAABLigAATIoAAIuKAADPigAADYsAAA6LAABOiwAAgIsAAIGLAADHiwAA9IsAADKM
AABOjAAAT4wAAJeMAADPjAAAEI0AACiNAAApjQAAco0AALmNAADXjQAA2I0AABaOAABTjgAAVI4A
AJuOAADfjgAA4I4AACiPAABajwAAW48AAKOPAADsjwAAHJAAAB2QAABmkAAAk5AAAJSQAADdkAAA
IpEAAE2RAABOkQAAT5EAAFCRAABRkQAAmpEAAJyRAADlkQAA5pEAAOeRAAAtkgAAcJIAAKuSAACs
kgAA9JIAAPWSAAA9kwAAf5MAAICTAADIkwAAC5QAAEaUAABHlAAAj5QAANGUAAAElQAABZUAAEWV
AACIlQAAiZUAAIqVAACLlQAAjJUAAI2VAACOlQAAj5UAAJCVAACRlQAAkpUAAJOVAACUlQAAlZUA
AJaVAACXlQAAmJUAAJmVAACalQAAm5UAAJyVAACdlQAAnpUAAJ+VAACglQAAoZUAAKKVAACjlQAA
pJUAAKWVAACmlQAAp5UAAKiVAADxlQAA85UAADyWAAA9lgAAPpYAAFaWAABXlgAAlpYAALCWAACx
lgAA1ZYAANaWAAAJlwAAK5cAACyXAABvlwAAcJcAAJSXAACVlwAAzJcAAM2XAAARmAAAEpgAAFKY
AABimAAAY5gAAKaYAADImAAAyZgAAA6ZAAAzmQAANJkAAHGZAABymQAAoZkAAKKZAADqmQAA85kA
APSZAAAYmgAAGZoAAFCaAABRmgAAfpoAAH+aAADFmgAA9poAAPeaAAA/mwAAUpsAAFObAACMmwAA
jZsAAI6bAACPmwAAkJsAANmbAADbmwAAJJwAACWcAAAmnAAAapwAAHucAAB8nAAAoJwAAKGcAADY
nAAA2ZwAACKdAABBnQAAQp0AAIidAACvnQAAsJ0AAPCdAAANngAADp4AAEyeAAB0ngAAdZ4AAJme
AACangAA0Z4AANKeAAARnwAAMJ8AADGfAAB4nwAAwJ8AAM+fAADQnwAAE6AAAEygAABNoAAAbKAA
AG2gAACRoAAAkqAAAMmgAADKoAAA9qAAAPegAAA8oQAASqEAAEuhAACJoQAAp6EAAKihAACpoQAA
qqEAAKuhAACsoQAA9aEAAPehAABAogAAQaIAAEKiAABhogAAYqIAAIaiAACHogAAvqIAAL+iAADd
ogAA3qIAAAKjAAADowAAOqMAADujAACDowAAoKMAAKGjAADAowAAwaMAAMKjAADDowAAxKMAAMWj
AADGowAAx6MAAMijAADJowAAyqMAAMujAADMowAAzaMAAM6jAADPowAA0KMAANGjAADSowAA06MA
ANSjAADVowAA1qMAANejAADYowAA2aMAANqjAADbowAA3KMAAN2jAADeowAA36MAAOCjAADhowAA
4qMAAOOjAAAspAAALqQAAHekAAB4pAAAeaQAAIykAACNpAAAoKQAAKqkAADRpAAA7aQAAPakAAD3
pAAAFaUAABalAAAXpQAAJaUAADWlAAA2pQAAV6UAAFilAABZpQAAaaUAAG+lAACApQAAkaUAAKWl
AADCpQAA1KUAANWlAADvpQAADaYAAA6mAAAPpgAAEKYAABGmAAASpgAAE6YAABSmAAAVpgAAFqYA
ABemAAAYpgAAGaYAABqmAAAbpgAAHKYAAB2mAAAepgAAH6YAACCmAAAhpgAAIqYAACOmAAAkpgAA
JaYAAG6mAABwpgAAc6YAAJgAAAASMAAAAAAAAAEAAAAAAAAAAAAAAAAAgACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAQAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAABAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAEACYAAAAADAAAAAAAAAAgAAA
AIAAAAAAAAAAABAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
ABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAA
EjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAS
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAA
AAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAA
AAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAA
AACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAA
mAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
AAAAEjAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAABIwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgA
AAASMAAAAAAAAACAAAAAgAAAAAAAAAAAAAAABgAASUYAANxUAABxrgAAWAAAAGsAAAByAAAAAAYA
AKMNAACLEQAAGxgAAIEcAAAGIwAACiQAAL8nAAC+KgAAqSsAAHAsAADVLwAABjIAAJs3AAAkPQAA
00AAAG1EAABJRgAAPUgAAOtIAADDTwAArlUAAFdYAABcWQAA2mAAAAlmAAC8bAAAB3AAACd2AACk
egAAM4EAABqGAAB/iAAAcIkAAI2JAACGjQAAz44AAIiQAAClkAAAl5QAAE+ZAACLnQAAqJ0AAMmg
AADbowAAMacAAEGqAADMqwAAjKwAABCuAABxrgAAWQAAAFsAAABcAAAAXQAAAF4AAABfAAAAYAAA
AGEAAABiAAAAYwAAAGQAAABlAAAAZgAAAGcAAABoAAAAaQAAAGoAAABsAAAAbQAAAG4AAABvAAAA
cAAAAHEAAABzAAAAdAAAAHUAAAB2AAAAdwAAAHgAAAB5AAAAegAAAHsAAAB8AAAAfQAAAH4AAAB/
AAAAgAAAAIEAAACCAAAAgwAAAIQAAACFAAAAhgAAAIcAAACIAAAAiQAAAIoAAACLAAAAjAAAAI0A
AAAABgAAca4AAFoAAAAPAADwOAAAAAAABvAYAAAAAggAAAIAAAABAAAAAQAAAAEAAAACAAAAQAAe
8RAAAAD//wAAAAD/AICAgAD3AAAQAA8AAvCSAAAAEAAI8AgAAAABAAAAAQQAAA8AA/AwAAAADwAE
8CgAAAABAAnwEAAAAAAAAAAAAAAAAAAAAAAAAAACAArwCAAAAAAEAAAFAAAADwAE8EIAAAASAArw
CAAAAAEEAAAADgAAUwAL8B4AAAC/AQAAEADLAQAAAAD/AQAACAAEAwkAAAA/AwEAAQAAABHwBAAA
AAEAAAAAAAAATAAAAN4AAACZBwAAogcAABgJAAAcCQAAEBcAABMXAAB5GQAAfBkAAH4ZAACBGQAA
PRsAAEEbAACHHQAAih0AAEoeAABNHgAAYh4AAGUeAABjIQAAaiEAANwjAADgIwAACCgAAA8oAAAq
KgAALioAAC8tAAA7LQAAmTEAAKUxAAC8MQAAyDEAAEs4AABOOAAAuTsAAMY7AABEPAAASDwAAHE/
AAB0PwAAd0AAAHtAAACiQgAApUIAAD5DAABBQwAA00cAAOJHAABySwAAfEsAALNMAAC3TAAALU4A
ADpOAACNUAAAkVAAAPNbAAD3WwAATGYAAFBmAACHaAAAk2gAAAdxAAAOcQAARXEAAElxAABacQAA
XnEAAGtxAABvcQAAjnEAAKFxAACmcQAAqnEAAOJxAADmcQAA6nUAAO51AAAEdgAACHYAAIp3AACO
dwAApHcAAKh3AACFegAAj3oAAKF6AACregAA1XoAANl6AACrgAAAr4AAALeBAAC7gQAA8YIAAPSC
AADQhwAA24cAAOOHAADohwAA7ocAAPeHAAAAiAAABYgAAAeIAAALiAAAHIgAACmIAADLiAAAz4gA
AGqJAAB0iQAAuYkAAMGJAADFigAAzooAAGKOAABsjgAA7o4AAPmOAABpjwAAdI8AAIGPAACHjwAA
opAAAKWQAABzkQAAd5EAAA6SAAAYkgAAJZIAACuSAAC6kgAAxJIAAAOTAAAGkwAAvZMAAMaTAABV
lAAAWpQAAOiUAADrlAAAypUAAM6VAACymwAAtpsAAJuhAACloQAABaQAAAmkAACjpAAAqaQAAMKk
AADHpAAAXKUAAGmlAABspQAAb6UAAHKlAACApQAAg6UAAJGlAACUpQAAnqUAAEemAABLpgAAc6YA
AAcABQAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwA
BwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAH
ABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcA
HAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAc
AAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwA
BwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcABQAHAAUABwAFAAcABQAHABwABwAcAAcAAAAA
AEwAAACUAAAAlQAAAN0AAABMAgAAbQIAAI8CAACeAgAABgMAABIDAABFAwAAUAMAAIwDAACTAwAA
0gMAANgDAAAXBAAAHQQAAGAEAABqBAAApgQAAKoEAADvBAAA8QQAADcFAAA5BQAAfgUAAIAFAAD9
BQAABwYAAKkGAACwBgAA8QYAAPoGAAB4BwAAewcAAMAHAADEBwAAAggAAAoIAADLCAAA0wgAADwK
AABHCgAAfAoAAIUKAADFCgAAxwoAAA0LAAAUCwAAUwsAAFYLAACWCwAAnwsAALcMAAC+DAAAMA0A
ADsNAACSDQAAmg0AANsNAADpDQAAJA4AAC8OAABtDgAAeQ4AAEgPAABYDwAAkQ8AAKEPAAD5EAAA
BBEAAEcRAABPEQAAkBEAAJgRAADZEQAA4REAACISAAAqEgAAaxIAAHMSAAC0EgAAvBIAAP0SAAAF
EwAARhMAAE4TAADaEwAA5BMAAM4UAADbFAAAFRUAABgVAABbFQAAZhUAAKEVAACqFQAAGhYAAB0W
AAAnFgAAMBYAAGwWAABzFgAArxYAALYWAADxFgAA+BYAAGIXAABlFwAAqxcAALIXAADzFwAA+xcA
ADAYAAA7GAAAdhgAAHoYAAC5GAAAvxgAACYZAAAwGQAAbRkAAG8ZAAC1GQAAuhkAAP0ZAAAAGgAA
RRoAAE4aAACKGgAAjxoAANMaAADeGgAADRwAABkcAACeHAAApxwAAK4cAAC5HAAA7xwAAPgcAAAz
HQAAOB0AALgdAADAHQAAAB4AAAYeAABGHgAASR4AAOQeAADvHgAALB8AADUfAABvHwAAeB8AAAwg
AAAVIAAAjCAAAI4gAAATIQAAGCEAAFghAABiIQAAbSIAAHIiAACxIgAAvSIAACMjAAAoIwAAaiMA
AG0jAABzJAAAeyQAAM4kAADYJAAA9SQAAP8kAAAEJQAADSUAAKElAACsJQAA5iUAAPElAAAvJgAA
OSYAAHMmAAB6JgAAvCYAAMMmAAABJwAACCcAAIknAACTJwAAxycAANMnAAAaKAAAJSgAAGIoAABo
KAAAqigAAKwoAADAKAAAxigAANooAADfKAAA+igAAPwoAAAPKQAAFSkAACspAAAwKQAASCkAAE0p
AABjKQAAcykAAFgrAABiKwAABS0AABItAAC8LgAAwC4AAOcuAADzLgAAEC8AACcvAAAkNQAALjUA
ADI2AAA2NgAArTYAALc2AAD1NgAA+zYAACk3AAAvNwAAYjcAAGg3AACPNwAAlTcAALs3AADANwAA
6jcAAPA3AAAzOAAANzgAAIU4AACMOAAAxzgAANE4AADXOAAA3jgAAP04AAAGOQAAITkAACk5AABA
OQAATTkAAKg5AACsOQAAtToAALg6AAC8OgAAwToAAN46AADlOgAAKDsAACo7AABLOwAAUjsAAJc7
AACdOwAA3DsAAOw7AAC7PAAAwjwAAAY9AAARPQAAHT0AACQ9AABnPQAAcT0AAJ49AACoPQAAckEA
AHdBAAC4QQAAu0EAAMtBAADTQQAAF0IAAB5CAABdQgAAZUIAAOZCAADwQgAAKkMAADFDAABxQwAA
dEMAALRDAADeQwAA+EMAAAREAAA4RAAAREQAAH9EAACCRAAAw0QAANFEAABVRQAAV0UAAJ1FAACk
RQAA5EUAAOdFAAAnRgAALkYAAG1GAAB1RgAAPEcAAEZHAACBRwAAhkcAAMlHAADNRwAAEEgAABZI
AACXSAAAoEgAAN9IAADiSAAAJkkAACpJAABpSQAAdEkAALFJAAC8SQAA+EkAAPpJAAAhSgAAL0oA
AGhKAABwSgAAsEoAALRKAAD4SgAA+0oAADxLAABHSwAAg0sAAI5LAADESwAAz0sAAA1MAAAYTAAA
UEwAAFpMAAAtTQAAM00AAHFNAAB2TQAAtE0AALxNAAD6TQAAAU4AAEFOAABLTgAAiE4AAIpOAADP
TgAA0k4AAAFPAAAPTwAATE8AAE5PAADbTwAA308AABhQAAAmUAAAPFEAAERRAACmUQAAr1EAAOtR
AADwUQAALVIAADZSAAB0UgAAfFIAALpSAAC9UgAA/1IAAAdTAABFUwAASVMAANRTAADZUwAAGFQA
ACBUAABhVAAAalQAAKRUAACuVAAA7FQAAPBUAAAzVQAANlUAAHdVAAB+VQAAt1UAAMBVAAD5VQAA
BVYAAD5WAABGVgAAh1YAAI1WAADLVgAA0lYAADtXAABCVwAAf1cAAIZXAAC+VwAAyVcAAAJYAAAH
WAAAS1gAAFdYAACUWAAAoVgAAN1YAADeWAAAE1kAACFZAACMWQAAj1kAANJZAADVWQAAEloAAB9a
AABZWgAAXloAAJxaAACiWgAA5VoAAOpaAACKWwAAjFsAAGpcAABuXAAA0FwAANtcAADwXAAA+1wA
ADVdAAA7XQAAfl0AAH9dAADYXQAA4F0AAAxeAAAQXgAAU14AAFVeAACXXgAAoV4AAN5eAADhXgAA
J18AACtfAAC2XwAAwF8AAPpfAAD/XwAAOGAAAENgAACtYAAAtmAAAPRgAAD6YAAANmEAAD5hAAB+
YQAAhGEAAMNhAADJYQAACWIAAAxiAABNYgAAVmIAAJZiAACYYgAA2mIAAOViAAAeYwAAJmMAAGNj
AABpYwAAqGMAALBjAADwYwAA82MAADdkAAA7ZAAAfWQAAIFkAACTZAAAn2QAAAllAAALZQAATWUA
AFJlAACSZQAAmGUAANZlAADgZQAAFmYAAB9mAAAsZwAALmcAAGpnAAB2ZwAAxGcAAM1nAAAKaAAA
D2gAAE5oAABUaAAAl2gAAJ1oAADfaAAA4WgAACFpAABUaQAAZmkAAG1pAACnaQAAsGkAAPBpAADy
aQAAOWoAAD1qAAB/agAAi2oAAMZqAADMagAADGsAABNrAABgawAAZmsAAKRrAACuawAAz2sAANlr
AAAWbAAAIGwAAFpsAABhbAAAoGwAAKZsAAATbQAAGm0AAFVtAABcbQAAnW0AAKBtAADkbQAA620A
ACpuAAAwbgAAcm4AAHVuAAC3bgAAwG4AAP1uAAAAbwAARG8AAE1vAACMbwAAlW8AALFvAAC7bwAA
cnAAALFwAAC6cAAAv3AAAABxAAAGcQAA1HEAANdxAAAccgAAInIAAONyAADwcgAALHMAADFzAABv
cwAAdnMAALZzAAC6cwAA/3MAAAl0AABDdAAASXQAAA51AAASdQAAV3UAAFp1AACddQAAoXUAAOZ1
AADpdQAAKHYAADJ2AABqdgAAcnYAAMp2AADNdgAAEXcAABh3AABWdwAAaXcAAG53AAB+dwAA0ncA
AN53AAAXeAAAHngAAF94AABheAAA7ngAAPR4AAA2eQAAPXkAAHx5AACCeQAAxHkAAMp5AAALegAA
EXoAAIl6AACPegAAk3oAAJ96AABMewAAXHsAALV7AADJewAA8XsAAAB8AAA5fAAAP3wAAIJ8AACL
fAAAyHwAAMt8AAANfQAAEX0AAFV9AABbfQAAmX0AAKN9AADXfQAA4n0AAB1+AAAgfgAAkn4AAJl+
AADbfgAA3n4AACJ/AAAvfwAAtH8AALh/AAD1fwAA/38AADeAAAA+gAAAkoIAAJWCAADZggAA3oIA
ACKDAAAvgwAAaoMAAHKDAADogwAA8oMAADCEAAA2hAAAdoQAAHqEAAC+hAAAwYQAAAaFAAAIhQAA
T4UAAFiFAADPhQAA1IUAABaGAAAZhgAAWoYAAF+GAAChhgAAo4YAANWGAADfhgAAWIgAAFuIAABq
iQAAo4kAALKJAAC1iQAA+YkAAPyJAACZigAApIoAAN2KAADpigAAXIsAAGqLAAC9iwAAxosAANWL
AADaiwAApYwAAKiMAABpjwAAdo8AAH6SAACqkgAAGZQAAEWUAABTlQAAX5UAAD6WAABJlgAAmZYA
AKSWAAC0lgAAvJYAAAyXAAAplwAAL5cAADaXAABzlwAAe5cAANCXAADelwAAFZgAAB6YAABYmAAA
YJgAAGaYAABvmAAArJgAALaYAADMmAAA1ZgAABSZAAAbmQAAN5kAAECZAAB1mQAAfZkAAKWZAACr
mQAA95kAAP+ZAABUmgAAX5oAAIKaAACNmgAAy5oAANaaAAD6mgAABZsAAEWbAABMmwAAVpsAAF+b
AAApnAAANZwAAHCcAAB3nAAAf5wAAIecAADcnAAA5ZwAACidAABAnQAARZ0AAE6dAACOnQAAkp0A
ALOdAAC8nQAA9p0AAAGeAAARngAAGp4AAFKeAABdngAAeJ4AAICeAADVngAA3p4AABefAAAinwAA
NJ8AAD2fAADGnwAAzZ8AANOfAADanwAAGaAAACSgAABQoAAAWKAAAHCgAAB4oAAAzaAAANegAAD6
oAAAAKEAAEKhAABIoQAATqEAAFShAACPoQAAmqEAAEWiAABNogAAZaIAAG2iAADCogAAyaIAAOGi
AADpogAAPqMAAEijAACkowAArKMAAN2kAADspAAAXKUAAGilAABspQAAbqUAAHKlAAB/pQAAg6UA
AJClAACxpQAAvaUAAHOmAAAHAAUABwAFAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcA
MwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAz
AAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcA
MwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAz
AAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcA
MwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAz
AAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcA
MwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAz
AAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcA
MwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAz
AAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcA
MwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAz
AAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcA
MwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAz
AAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAFAAcABQAHAAUABwAFAAcAMwAHAAAAAAB2JAAAiyQAACs2AAAyNgAAc6YAAAcABQAHAAUA
BwACAA1pBCtA6uCiEQD/D/8P/w//D/8P/w//D/8PAAA3U35lis9ctxAA/w//D/8P/w//D/8P/w//
DwAAAQAAAP8QAAAAAAAAAAAAAAAAAAAAAAAALxgAAA+EAAARhAAAFcYFAAGgBQZehAAAYIQAADUI
ADYIAEIqC0NKFABPSgUAUUoFAFkoAGFKFABvKABwaACAAACHaAAAAACISAAACQBbAFIAZQBzAHUA
bAB0AF0AIAABAAAAFhQLDQAAAAAAAAAAAAAAAAAAAAANGAEAD4QAABGEAAAVxgUAAaAFBl6EAABg
hAAAbygAh2gAAAAAiEgAAA0AQQBiAHMAYwBoAG4AaQB0AHQAIAAAAC4AAQABAAAABBACAAAAAAAA
AAAAAAAAAAAAAAANGAIAD4TQAhGEUP4VxgUAAdACBl6E0AJghFD+bygAh2gAAAAAiEgAAAMAKAAC
ACkAAQAAAAISAgAAAAAAAAAAAAAAAAAAAAAADRgDAA+EYAMRhHD/FcYFAAFgAwZehGADYIRw/28o
AIdoAAAAAIhIAAADACgAAwApAAEAAAAAEAEAAAAAAAAAAAAAAAAAAAAAAA0YBAAPhPADEYRQ/hXG
BQAB8AMGXoTwA2CEUP5vKACHaAAAAACISAAAAgAEACkAAQAAAAQQAQAAAAAAAAAAAAAAAAAAAAAA
DRgFAA+EgAQRhFD+FcYFAAGABAZehIAEYIRQ/m8oAIdoAAAAAIhIAAACAAUAKQABAAAAAhIBAAAA
AAAAAAAAAAAAAAAAAAANGAYAD4QQBRGE4P4VxgUAARAFBl6EEAVghOD+bygAh2gAAAAAiEgAAAIA
BgApAAEAAAAEEAEAAAAAAAAAAAAAAAAAAAAAAA0YBwAPhKAFEYRQ/hXGBQABoAUGXoSgBWCEUP5v
KACHaAAAAACISAAAAgAHAC4AAQAAAAISAQAAAAAAAAAAAAAAAAAAAAAADRgIAA+EMAYRhHD/FcYF
AAEwBgZehDAGYIRw/28oAIdoAAAAAIhIAAACAAgALgABAAAA/wAAAAAAAAAAAAAAAAAAAAAAAAAv
GAAAD4QAABGEAAAVxgUAAaAFBl6EAABghAAANQgANggAQioLQ0oUAE9KBQBRSgUAWSgAYUoUAG8o
AHBoAIAAAIdoAAAAAIhIAAAJAFsAUgBlAHMAdQBsAHQAXQAgAAEAAAAWBAsNAAAAAAAAAAAAAAAA
AAAAAA0YAQAPhAAAEYQAABXGBQABoAUGXoQAAGCEAABvKACHaAAAAACISAAADQBBAGIAcwBjAGgA
bgBpAHQAdAAgAAAALgABAAEAAAAEAAIAAAAAAAAAAAAAAAAAAAAAAA0YAgAPhNACEYRQ/hXGBQAB
0AIGXoTQAmCEUP5vKACHaAAAAACISAAAAwAoAAIAKQABAAAAAgICAAAAAAAAAAAAAAAAAAAAAAAN
GAMAD4RgAxGEcP8VxgUAAWADBl6EYANghHD/bygAh2gAAAAAiEgAAAMAKAADACkAAQAAAAAAAQAA
AAAAAAAAAAAAAAAAAAAADRgEAA+E8AMRhFD+FcYFAAHwAwZehPADYIRQ/m8oAIdoAAAAAIhIAAAC
AAQAKQABAAAABAABAAAAAAAAAAAAAAAAAAAAAAANGAUAD4SABBGEUP4VxgUAAYAEBl6EgARghFD+
bygAh2gAAAAAiEgAAAIABQApAAEAAAACAgEAAAAAAAAAAAAAAAAAAAAAAA0YBgAPhBAFEYTg/hXG
BQABEAUGXoQQBWCE4P5vKACHaAAAAACISAAAAgAGACkAAQAAAAQAAQAAAAAAAAAAAAAAAAAAAAAA
DRgHAA+EoAURhFD+FcYFAAGgBQZehKAFYIRQ/m8oAIdoAAAAAIhIAAACAAcALgABAAAAAgIBAAAA
AAAAAAAAAAAAAAAAAAANGAgAD4QwBhGEcP8VxgUAATAGBl6EMAZghHD/bygAh2gAAAAAiEgAAAIA
CAAuAAMAAAA3U35lAAAAAAAAAAAAAAAAN1N+ZQAAAAAAAAAAAAAAAA1pBCsAAAAAAAAAAAAAAAD/
/////////////////wIAAAAAAAAA//8CAAAAAAAAAMIFAAAEAAAACAAAAOUAAAAAAAAAwQUAAGQT
AAD8dwAAnxkBAJcrAQAXMQEAvzEBAH42AQASOwEARzwBAHBbAQBsawEAgnQBAOoCAgCsFAIAkBwC
AHwsAgBhYgIATnECAONyAgA6fwIAHAMDAPIHAwDhJAMAJiYDACk5AwDETQMAPE4DAINTAwC4WQMA
RV0DABtzAwCfGwQA4EEEAEVGBACRSgQA/VkEAAhhBACLbgQAZXkEAHcRBQDbMQUATlgFAIJpBQDH
HAYAACIGAAcnBgA3NgYAeDsGAAVsBgAFEQcAMh8HAA8mBwAPJwcANC0HAJ1WBwBWWAcAu14HAM5p
BwB7BQgAx2MIAFloCADHfQgAyQYJANoPCQDlEwkARxUJAE4oCQCUMwkA7moJALJwCQBKfAkA9BgK
AK1mCgBrBQsA+RgLAKw0CwD4PwsA20ALAIxpCwDCewsAMn0LAAdMDAC2TAwAkVIMAL5nDACDagwA
FnMMAMR+DADYFQ0AW0wNAJZSDQCCdA0AEiEOABpFDgAfTg4A/1QOAElwDgDrAg8A2RQPAOY1DwDA
PA8Av1YPAFNiDwAaZw8AX3MPAPp2DwDofg8AmAsQAFQQEAAJcRAANxIRAP8sEQDjVBEAQ30RABx/
EQA8BBIA4BkSAJklEgA/TBIA4k0SAGZgEgBFZBIAoQITAPYKEwDaCxMAAxMTAI0jEwBhKBMA9kMT
AIpIEwCTThMAO08TAKZhEwC7dhMA4QIUACwWFADEJBQA620UAJN2FABPAhUAjQQVAOcdFQChJRUA
7EcVACtMFQBEAxYA4AsWAJk0FgAgRRYAxEsWAAdVFgBMWhYADm4WALJMFwC3YBcAAmUXAH0bGAD+
SxgAAE8YANMUGQCVHhkAXjQZAP89GQDfBRoAbAoaAKEjGgBLSxoAnkwaAJZtGgDZAhsA7SAbADE1
GwDiXRsAWBQcAFQhHAAcPhwAFkYcAH5HHAB6XhwA1WEcAEZmHABKfxwAoCIdANh3HQDRex0A9hYe
AGYYHgBGMx4ATjUeAGlqHgDzbR4A/nkeAC0LHwCpEh8A6CIfAOAlHwBrLB8AITUfAAREHwBdYh8A
xRIgAH8YIABFXSAAlGAgAK1wIACCOiEAWjshALFuIQDCdCEAqXUhAI0NIgCJESIAQhUiABEbIgDM
KCIAFCkiAMYxIgDZNSIAgjkiAGxcIgBeZiIAwgYjANIIIwDHDyMA7xIjAEQcIwAZMSMAM2AjAIhq
IwA1diMA6nojAFEHJACLFSQAWiMkAAk9JADlTSQAeSQlAJtrJQBpciUA4nklAKEXJgCqUSYAFVgm
AL1gJgB6diYA/XcmAAEMJwBFIScAAgAoAChUKAByNykAJzkpAClLKQBDcCkAKXgpAAx7KQBzISoA
TysqAMo2KgDLXioA62gqAAZ1KgANBCsAoxwrAPRGKwBnSCsA+UgrADNKKwDjeCsA0gIsALsXLADB
ICwAdissALRQLAA/aiwAI3osABsaLQC6Iy0AW0otAERULQCBfi0AVh8uANsoLgC1VS4ACC0vAIs0
LwA8Py8A2FkvAO0fMAB9JTAAJDMwANxTMACeVzAAilgwACBaMAC8ZTAA6GowACVvMADEfzAA/REx
ANodMQB1TjEAo3kxAOYaMgCbUjIAq1syAJRfMgARdTIAEAkzAJ46MwD1UjMAXFYzAKBkMwBKazMA
6g80AB4jNADdNDQAz2I0AD9oNAC6DTUAbxg1AGpsNQCKbDUA3io2AEgzNgA9RzYAcW82ANN+NgDl
FTcAfhk3APQiNwDTMjcAk1g3AM5hNwD3JTgA8jM4AK9QOAARVjgAel84AARhOAA1bjgACXU4APkX
OQBtKjkAowc7AEYeOwDjPzsAHEg7ALlROwCfUzsA/Ww7ABR0OwA2IjwAlUc8ADBMPABjTzwA+Wg8
ADMSPQAfVT0AcFg9AAVrPQDMAT4AIiw+AGwsPgBELT4APDE+AKdjPgAFZT4ARn8+AIQSPwC8UT8A
Sg9AANAPQAD6J0AAP2xAAGh4QADTAUEAAF5BAA8QQgDVKkIAvjJCAHs+QgD/UEIAYgxDALc1QwAM
REMAtUdDANtWQwBlWUMAsAdEAAIdRAAfQ0QAQkxEAKFORAA7AEUALAtFAMgMRQCSE0UAPSlFALly
RQD2dEUA9n5FAEgnRgDkPUYA8UdGAE1RRgCmU0YAkFZGAGFnRgAkbEYA/BBHAGYXRwCjJUcAF2xH
AEpwRwB0GEgARRxIAAgxSAA/M0gAe0xIAKhlSABFbkgAZnNIANUdSQA0b0kAX3hJAJp5SQDyB0oA
qCNKAPo5SgAVYUoAo2FKAKwLSwAfDksAUEFLALBDSwAFUksAwXlLAMcyTACdVEwA1GFMAAgFTQD5
Dk0ACRFNADM2TQB4W00AqmdNAJl+TQC1E04AuR1OAN0iTgBTK04AyzdOALBvTgD5EU8ALRtPAGwr
TwDDc08A2nlPAKxJUAC7XVAAkQBRAFcGUQBBFlEAaxhRAI0kUQCtJVEABjJRAJs0UQBXQFEAFlFR
AM9tUQCeeFEAjgFSAG4cUgDLJFIA4TlSADheUgAja1IAi3lSAEILUwCLLFMA9T1TAAFBUwCoU1MA
UF1TAIMJVABrKlQAHTlUANE/VAAoblQAaH5UAI8JVQDPFVUAtBZVAHccVQALJVUARy1VAL4zVgAb
PVYA5gJXAMwHVwCUNVcAa0ZXADECWADqBVgA8xhYAD4CWQC0GlkAKC5ZAO0zWQAxS1kApXZZAO8G
WgCVCFoAFTJaAIM/WgA+ZFsANAlcAEQMXACpSFwA+WBcAKVhXAD7aFwA125cAHokXQD1Ol0AFV5d
ADBeXQCCa10AHXpdAPQDXgD+I14AaFJeAKhcXgCaY14AuWReAJxoXgBma14A0gVfAFoSXwCwHF8A
8ixfAC1lXwC9bV8AIXNfALwaYAAOIGAABlBgADVRYAA2UmAA6WFgACQCYQAkJ2EA7DJhAFM2YQA/
OGEANT5hAOxCYQDUQ2EADWthAPluYQAJf2EA2xZiAD8hYgCpJ2IAHiliAKNFYgD+c2IAohNjAH0g
YwBIVmMA+1pjAMZkYwAJE2QAnxpkAJYiZABOKmQAwS9kAMJIZABSSWQAxGNkAHd0ZADjNGUASD5l
AEtIZQCuUmUAHXdlAOp4ZQBGC2YAeA5mALMVZgDHG2YAZidmAK89ZgCdSGYAQnRmAIF2ZgAhemYA
hRtnANRjZwDQbWcAv3NnAKANaAANG2gAOShoANc9aAA2Q2gAplBoACtaaACcY2gAmBFpAP8kaQAt
M2kAcEZpANpNaQA/T2kAXWFpAD93aQDoE2oAGEJqAEpGagCxVGoAjXBqAKcBawArBGsAnA1rAP4W
awAUZ2sAU29rAAl1awBPCGwAj0BsAI5GbAC5YGwAAWdsAHECbQBFOm0Au1VtAGJbbQChAW4AGx1u
ANo8bgDrQW4As2xuAOAHbwAUDm8AjSNvAOoobwDEVG8A3W9vAH8GcADGP3AAE1VwAMpVcACIBnEA
8A5xAIYccQANLXEAPDxxAOZIcQACfnEArAVyABUMcgAFMHIAMjVyABVQcgArZnIAegtzANQpcwBA
PXMAgmVzAHkGdAADFHQAgEt0ACJVdADyInUAx1N1AH9ndQDZeXUABn91APQHdgBDF3YApR12ABw1
dgBKX3YAuGl2AN9rdgCMcHYAjwB3AJ4AdwBhBXcAYgp3ALwSdwAtPHcAoGR3ANEFeADZFXgAuhZ4
AF4jeAAHRXgAh2V4AO1meADuZngAzm54AJYEeQA4BXkAlhR5AAYneQBzL3kA5DR5AOlAeQCkZXkA
p2d5AOl8eQDfB3oAFD56ABVFegB4V3oAdGB6ANUUewB3HXsA8i57AKc1ewBLQ3sATXp7ANR/ewDH
AHwANAR8AEsPfAAgEXwAjBd8AIwefACiLnwAZkV8AHhafADrYXwAZ2J8ANIHfQDPSn0ApVV9AHR/
fQDSJH4AKF1+AAsSfwAiNX8A6zp/AFo7fwCNSH8AU0l/AAxrfwDpe38Alnx/AJcJgADLFYAA9ByA
APc0gACORoAAs1OAAIYNgQD9EYEAgGaBAPM7ggBXRYIAyUyCAEl0ggAdA4MAYS2DACRDgwBff4MA
7xuEAPNAhADTX4QAUmmEAG5shADDG4UAWx+FAFwuhQByWYUAmmeFAEsMhgAJFoYAODqGABtBhgAt
bYYA8n+GACkChwDoBIcANgaHANsIhwBMGIcA3V+HALVnhwCJCYgAz0eIAJRQiAAOYogAQGOIACd3
iADjeogAWheJAI4EigDZBIoANxuKAKIrigAwRYoAJ0yKAKEUiwDcF4sAgx+LAAUiiwBiRIsA90+L
AHB/iwB2XIwALXmMANB/jADBF40AGh+NAGRmjQAFcI0A8QGOAOw6jgAZXo4AnXWOAP8ZjwAjHo8A
lSyPABg0jwDmQI8ACk2PANpOjwAPXI8AqxuQAG9ckABbY5AA7mWQAI4BkQCOLZEAwGuRAPwgkgBL
JJIA/zKSAH9HkgD9R5IAGlKSAMoSkwB1IJMAmzmTAPdPkwAtWJMAdGqTAB9xkwB6dpMAeXmTAG8A
lADxAJQAtAiUACtHlACTUZQA1l+UAE5hlABTZJQAG3OUABAHlQAhCZUAJiGVAD88lQCMXZUAMXCV
AIEGlgDbQpYAdUeWAF5VlgCcc5YArnSWAHoNlwAJDpcAlg+XAPUSlwAFGZcANBmXALkklwDYJJcA
4SqXAHBalwDxXJcAKmCXAIJplwDRDJgAMReYANYZmADdKpgA7UqYAP9gmADJY5gAlQuZAFwTmQCf
UpkABlWZANlamQDnb5kACHuZAJ4FmgDfD5oAozeaAKlAmgAUU5oAWGKaAANvmgAHL5sA/TybAIZC
mwBaR5sAh0ubAH9SmwD8dZsAdDmcAD9KnAA7W5wAMSedAJgynQCtRp0AZwSeAFsKngA1H54Aky6e
AMwwngCKM54ANXmeAFEAnwBBC58ACkCfANBAnwDhVZ8A3hOgAB8XoAAYH6AA/i+gAAU4oACFU6AA
2yGhACEqoQBrQqEAEF6hAGhooQAScKEAIHGhAPBxoQCae6EAWQKiAPUEogAYCqIAtRaiAO83ogC/
S6IA8V2iAM9+ogAPB6MA9wmjADQgowC/PKMAO0KjACxeowCeEKQANiakABtLpADjTqQALmOkAKNo
pAAPcaQAfhilAJEcpQDZOqUAvFalAAZgpQDHcKUAjwGmAJUCpgAmR6YAFU+mAC9jpgCidaYAci6n
AC4+pwC2TKcAdlanAMlapwDBYqcAIWynACAOqABwGagASxqoADstqABWMqgAZWGoAD9mqACua6gA
IA2pAIIRqQAeGqkAXUCpAOhJqQBIS6kAgE2pAMNdqQD5aKkA7iGqAAgjqgDdNKoA4DSqAHRRqgDq
HasAESKrAKQ5qwBKXKsA2GSrAM9oqwAvCKwA7iisAMEurABPQqwA5WqsANh4rAAwAa4ANwKuAPwF
rgB8Kq4AsTOuABQ4rgB6Rq4ALGuuADQ8rwDwP68ATVqvAAVmrwDDbq8AWBOwALMvsAA8NbAAfEGw
ABtLsABQUrAAVA6xAJlOsQCRV7EA+WqxAEoLsgBcFrIAqiKyAN15sgAEEbMAux6zAEsfswDNH7MA
tiuzAIRmswB9MbQA9AW1AOEStQBlJrUAejO1AD9itQASZrUA+X21AFAxtgBPMrYA8jO2AMg1tgCd
O7YAvlC2AJlVtgCaXLYAAha3AAkltwBUAbgAKA24AGwVuACVF7gAJzi4AIk4uABPbLgAKG64AEN5
uAC5f7gAqBG5AHNDuQCHSLkAWmW5AF9AugDHQ7oA0ke6AO9augD4WroARWK6AOxmugDKbrsAVXG7
ACt4uwCrebsAwAS8AAsJvAAkHbwAjSm8AOU9vAAMZ7wAd3a8AN5/vAAjFb0AWB+9AG4svQDfM70A
gFy9ABNsvQBmfL0ASQK+AFMRvgBLPb4AGT6+AH5MvgA0ar4Ah2y+ADxvvgC4db4A5Qq/AGEpvwDX
Wr8ASgDAAMINwADGMcAAHTLAAA01wACaRMAAwlLAAHobwQAWMsEAU1DBAGYfwgAwLsIA/zvCAH1M
wgCrTsIAx2jCAMoXwwCxU8MAtmrDAHduwwAwB8QA5g3EAF0QxADLSMQAxmDEAO8dxQB3KMUA6jXF
AAY3xQCcb8UAjwHGAFYJxgCBEsYA0BnGABEjxgBqU8YAkinHAPlVxwBkYccAFg7IANAOyAAXW8gA
xHXIAIMByQCoE8kAwiLJACUyyQCMMskA3zrJAD1TyQB6ZskAmWfJAMErygCKL8oAoTTKANE6ygAQ
UsoAnmzKABl6ygA4J8sA7yjLAOZMywDrA8wAACbMANV1zACYE80AAyrNAKUwzQCfPc0ApF7NAIpq
zQBbc80AURDOAO5pzgDFcc4AvHXOAPQFzwB/JM8AlDLPALc8zwBnP88AgU7PAHxizwCbac8ACRPQ
AHJk0ADEcNAAQQDRAJMS0QD3V9EAmw3SAJ0q0gCiR9IAQlnSALxb0gCkZdIAr27SAJML0wDlFNMA
7inTABor0wB0UdMA6FzTAD9d0wCqGtQACCHUAPYh1ADmfNQA9ADVALIq1QBAQNUAIn3VAH4G1gBc
HNYA0CLWAE0y1gDqW9YAmXfWAJkA1wDEHdcAex7XAFQq1wBVNNcADkLXAM1V1wASaNcAwAjYABYJ
2AC5J9gA5SrYAAAw2ADbTtgAyFnYAFNh2ADxctgAYzfZACNe2QApVNoAl2XaAFtq2gBncdoAm3Pa
AEB22gDMKdsA+SvbAPIx2wDubdsAV3/bAHME3AB6DtwA+jTcAJZW3AB+V9wAe2PcAJoP3QDrGd0A
iizdABU13QBcPd0AdVXdAKlg3QAKbt0AawHeAL0D3gBzEN4AVjLeANky3gBxTt4ADmveAMV63gDs
Qd8AknzfAJx+3wDsft8AYC/gAEtC4ADKWOAA9XXgAD4G4QALJ+EA4TbhAMhG4QCuS+EASF3hAHdh
4QDHZOEAsnfhAEJp4gAObuIAFxXjAOAk4wDFTOMAHG7jANZx4wCJfOMAPCDkAJ0m5QBELeUArUfl
AIgI5gCZJOYAHT3mAB9Z5gCFauYAMATnAD0G5wD1GecAfSrnAPNN5wDYb+cAkX7nANsl6AAbVOgA
K3zoAEEO6QAmNOkAv1vpAPRz6QC2FOoAmCjqANAu6gDXMuoARTXqAKRX6gDgV+oAIBPrAN4W6wAK
G+sA5yLrALgj6wALRusAFUzrAEVY6wCWdOsAW3nrAMAG7ABtDewA6jvsABNO7ACcUuwA+WbsAAEd
7QBwPe0AznXtADlQ7gAiYu4Az3TuAM997gCGG+8Afh7vABtF7wBvSe8ACU7vAGNS7wBUXu8A6Hrv
ANAS8AA8JPAA7yfwACsx8ADSQvAAxFfwAK9/8ACoPfEAMD7xAMBT8QCAWPEAPlvxAGdz8QBxd/EA
zyzyAC5n8gDiBPMAWgXzADc28wA1SPMAY1HzANVU8wBYfvMAWgH0ACct9ABDafQARB31AKsr9QAA
L/UAQzH1ADRn9QAtbfUAYRn2ADEa9gAaJPYAmin2AMov9gBrM/YAbnD2AP8C9wBpF/cAeTb3AFQ5
9wDbaPcA/n/3AHIt+ABxNPgABz34AHFB+ACLTPgAQU/4AI0N+QCnGfkAYVP5AHAb+gCeX/oAgHf6
ALAE+wABHvsAhjH7AOw/+wBTVvsA6Gj7AA92+wBQAvwA8QT8AGk3/ADyV/wAyG/8AH9y/AAldvwA
YHf8AEt5/ABIM/0AQXH9ANpy/QB2DP4AxhX+ANFJ/gADWv4AKmL+ANhk/gAgaf4AzGn+AOty/gA/
Bv8A3wj/AEkj/wAKJf8A9EL/AHV1/wD/QAGAAQCtPwAArT8AAJyfMg4BAAEArT8AAAAAAACtPwAA
AAAAAAIQAAAAAAAAAHGmAACAAAAQAEAAAP//AgAAAAcAVQBuAGsAbgBvAHcAbgADAEEATABVAP//
AgAIAAAAAAAAAAAAAAAAAAAAAAAAAAEA//8CAAAAAAAAAP//AAACAP//AAAAAP//AAACAP//AAAA
AAcAAABHFpABAAACAgYDBQQFAgMEh3oAIAAAAIAIAAAAAAAAAP8BAAAAAAAAVABpAG0AZQBzACAA
TgBlAHcAIABSAG8AbQBhAG4AAAA1FpABAgAFBQECAQcGAgUHAAAAAAAAABAAAAAAAAAAAAAAAIAA
AAAAUwB5AG0AYgBvAGwAAAAzJpABAAACCwYEAgICAgIEh3oAIAAAAIAIAAAAAAAAAP8BAAAAAAAA
QQByAGkAYQBsAAAAPzWQAQAAAgcDCQICBQIEBIc6ACAAAAAAAAAAAAAAAAD/AQAAAAAAAEMAbwB1
AHIAaQBlAHIAIABOAGUAdwAAAEMmkAEAAAILBQICAgQCAwOHAAAAAAAAAAAAAAAAAAAAGwAAAAAA
AABGAHUAdAB1AHIAYQBBACAAQgBrACAAQgBUAAAAQSaQAQAAAgsGAwICAgICBIcCAAAAAAAAAAAA
AAAAAACfAAAAAAAAAFQAcgBlAGIAdQBjAGgAZQB0ACAATQBTAAAAVRGQAYAGAgIGCQQCBQgDBAEA
AAAAAAcIEAAAAAAAAAAAAAIAAAAAAE0AUwAgAD8APwAAAEEAcgBpAGEAbAAgAFUAbgBpAGMAbwBk
AGUAIABNAFMAAAAiAAQAcYiIGADw0AIAAGgBAAAAAOZi/CbyYvwmAAAAAAQAAAAAAMwWAACljwAA
AQBVAAAABAADEDIBAADMFgAApY8AAAEAVQAAADIBAAAAAAAAeBIA8BAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAACAegBbQAtACBgTI0AAAQABkAZAAAABkAAAAcpgAAHKYAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAA
AAABMoMRAPAQAN/fAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEhQAAAAAAzw/w8AAAE/AAAA
AAAAcCQAAP///3////9/////f////3////9/////fzABrgAAAAAAMgAAAAAAAAAAAAAAAAABAAAA
//8SAAAAAAAAAD8AQQB1AGQAaQBvAC8AVgBpAGQAZQBvACAAVAByAGEAbgBzAHAAbwByAHQAIABX
AG8AcgBrAGkAbgBnACAARwByAG8AdQBwACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgAFEAAAAAAAAAAwBBAEwAVQADAEEATABVAAAAAAAAAAAAAAAA
AAAAAAAAAAAAFAAAAAYAAAACAAAAAAAMAAEADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP7/AAAFAQIAAAAAAAAAAAAAAAAA
AAAAAAEAAADghZ/y+U9oEKuRCAArJ7PZMAAAAKABAAARAAAAAQAAAJAAAAACAAAAmAAAAAMAAADg
AAAABAAAAOwAAAAFAAAA+AAAAAYAAAAEAQAABwAAABABAAAIAAAAJAEAAAkAAAAwAQAAEgAAADwB
AAAKAAAAXAEAAAwAAABoAQAADQAAAHQBAAAOAAAAgAEAAA8AAACIAQAAEAAAAJABAAATAAAAmAEA
AAIAAADkBAAAHgAAAEAAAABBdWRpby9WaWRlbyBUcmFuc3BvcnQgV29ya2luZyBHcm91cCAgICAg
ICAgICAgICAgICAgICAgICAgICAgIFEAHgAAAAQAAAAAAAAAHgAAAAQAAABBTFUAHgAAAAQAAAAA
AAAAHgAAAAQAAAAAAAAAHgAAAAwAAABOb3JtYWwuZG90AAAeAAAABAAAAEFMVQAeAAAABAAAADQA
AAAeAAAAGAAAAE1pY3Jvc29mdCBPZmZpY2UgV29yZAAAAEAAAAAAAAAAAAAAAEAAAAAA9GAeurjM
AUAAAAAAPIjLu7jMAQMAAAABAAAAAwAAAMwWAAADAAAApY8AAAMAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAABQECAAAAAAAAAAAAAAAAAAAAAAABAAAA
AtXN1ZwuGxCTlwgAKyz5rjAAAAA0AQAADAAAAAEAAABoAAAADwAAAHAAAAAFAAAAiAAAAAYAAACQ
AAAAEQAAAJgAAAAXAAAAoAAAAAsAAACoAAAAEAAAALAAAAATAAAAuAAAABYAAADAAAAADQAAAMgA
AAAMAAAAFAEAAAIAAADkBAAAHgAAABAAAABBbGNhdGVsLUx1Y2VudAAAAwAAADIBAAADAAAAVQAA
AAMAAAAcpgAAAwAAAA8nCwALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAALAAAAAAAAAB4QAAABAAAA
QAAAAEF1ZGlvL1ZpZGVvIFRyYW5zcG9ydCBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAg
ICAgICAgICAgUQAMEAAAAgAAAB4AAAAGAAAAVGl0bGUAAwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAIAAAADAAAABAAAAAUAAAAGAAAABwAAAAgAAAAJAAAA
CgAAAAsAAAAMAAAADQAAAA4AAAAPAAAAEAAAABEAAAASAAAAEwAAABQAAAAVAAAAFgAAABcAAAAY
AAAAGQAAABoAAAAbAAAAHAAAAB0AAAAeAAAAHwAAACAAAAAhAAAAIgAAACMAAAAkAAAAJQAAACYA
AAAnAAAAKAAAACkAAAAqAAAAKwAAACwAAAAtAAAALgAAAC8AAAAwAAAAMQAAADIAAAAzAAAANAAA
ADUAAAA2AAAANwAAADgAAAA5AAAAOgAAADsAAAA8AAAAPQAAAD4AAAA/AAAAQAAAAEEAAABCAAAA
QwAAAEQAAABFAAAARgAAAEcAAABIAAAASQAAAEoAAABLAAAATAAAAE0AAABOAAAATwAAAFAAAABR
AAAAUgAAAFMAAABUAAAAVQAAAFYAAABXAAAAWAAAAFkAAABaAAAAWwAAAFwAAABdAAAAXgAAAF8A
AABgAAAAYQAAAGIAAABjAAAAZAAAAGUAAABmAAAAZwAAAGgAAABpAAAAagAAAGsAAABsAAAAbQAA
AG4AAABvAAAAcAAAAHEAAAByAAAAcwAAAHQAAAB1AAAAdgAAAHcAAAB4AAAAeQAAAHoAAAB7AAAA
fAAAAH0AAAB+AAAAfwAAAIAAAACBAAAAggAAAIMAAACEAAAAhQAAAIYAAACHAAAAiAAAAIkAAACK
AAAAiwAAAIwAAACNAAAAjgAAAP7///+QAAAAkQAAAJIAAACTAAAAlAAAAJUAAACWAAAA/v///5gA
AACZAAAAmgAAAJsAAACcAAAAnQAAAJ4AAACfAAAAoAAAAKEAAACiAAAAowAAAKQAAAClAAAApgAA
AKcAAACoAAAAqQAAAKoAAACrAAAArAAAAK0AAACuAAAArwAAALAAAACxAAAAsgAAALMAAAC0AAAA
tQAAALYAAAC3AAAAuAAAALkAAAC6AAAAuwAAALwAAAC9AAAAvgAAAL8AAADAAAAAwQAAAMIAAADD
AAAAxAAAAMUAAADGAAAAxwAAAMgAAADJAAAAygAAAMsAAADMAAAAzQAAAM4AAADPAAAA0AAAANEA
AADSAAAA0wAAANQAAADVAAAA1gAAANcAAADYAAAA2QAAANoAAADbAAAA3AAAAN0AAADeAAAA3wAA
AOAAAADhAAAA4gAAAOMAAADkAAAA5QAAAOYAAADnAAAA6AAAAOkAAADqAAAA6wAAAOwAAADtAAAA
7gAAAO8AAADwAAAA8QAAAPIAAADzAAAA9AAAAPUAAAD2AAAA9wAAAPgAAAD5AAAA+gAAAPsAAAD8
AAAA/QAAAP4AAAD/AAAAAAEAAAEBAAACAQAAAwEAAAQBAAAFAQAABgEAAAcBAAAIAQAACQEAAAoB
AAALAQAADAEAAA0BAAAOAQAADwEAABABAAARAQAAEgEAABMBAAAUAQAAFQEAABYBAAAXAQAAGAEA
ABkBAAAaAQAAGwEAABwBAAAdAQAAHgEAAB8BAAAgAQAAIQEAACIBAAAjAQAAJAEAACUBAAAmAQAA
JwEAACgBAAApAQAAKgEAACsBAAAsAQAALQEAAC4BAAAvAQAAMAEAADEBAAAyAQAAMwEAADQBAAA1
AQAANgEAADcBAAA4AQAAOQEAADoBAAA7AQAAPAEAAD0BAAA+AQAAPwEAAEABAABBAQAAQgEAAEMB
AABEAQAARQEAAEYBAABHAQAASAEAAEkBAABKAQAASwEAAEwBAABNAQAATgEAAE8BAABQAQAAUQEA
AFIBAABTAQAAVAEAAFUBAABWAQAAVwEAAFgBAABZAQAAWgEAAFsBAABcAQAAXQEAAF4BAABfAQAA
YAEAAGEBAABiAQAAYwEAAGQBAABlAQAAZgEAAGcBAABoAQAA/v///2oBAABrAQAAbAEAAG0BAABu
AQAAbwEAAHABAAD+////cgEAAHMBAAB0AQAAdQEAAHYBAAB3AQAAeAEAAP7////9/////f////3/
//99AQAA/v////7////+////UgBvAG8AdAAgAEUAbgB0AHIAeQAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYABQH//////////wMAAAAGCQIAAAAAAMAAAAAAAABG
AAAAAAAAAAAAAAAAUBf14ru4zAF/AQAAgAAAAAAAAABEAGEAdABhAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgACAf///////////////wAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI8AAAAAEAAAAAAAADEAVABhAGIAbABl
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOAAIB
AQAAAAYAAAD/////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAlwAAADCiAQAA
AAAAVwBvAHIAZABEAG8AYwB1AG0AZQBuAHQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAABoAAgECAAAABQAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAANBwBAAAAAAAFAFMAdQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKAACAf///////////////wAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAGkBAAAAEAAAAAAAAAUARABvAGMAdQBtAGUAbgB0AFMAdQBtAG0A
YQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAA4AAIBBAAAAP//////////AAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcQEAAAAQAAAAAAAAAQBDAG8AbQBwAE8A
YgBqAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAgD/
//////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAEAAAD+////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////AQD+/wMKAAD/////BgkCAAAAAADAAAAAAAAARh8AAABNaWNyb3NvZnQg
T2ZmaWNlIFdvcmQgRG9jdW1lbnQACgAAAE1TV29yZERvYwAQAAAAV29yZC5Eb2N1bWVudC44APQ5
snEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAA=

--_003_5F7BCCF5541B7444830A2288ABBEBC9621620F5344FRMRSSXCHMBSD_
Content-Type: application/pdf;
	name="draft-ietf-avtcore-monarch-08_CommentsAlbrecht.pdf"
Content-Description: draft-ietf-avtcore-monarch-08_CommentsAlbrecht.pdf
Content-Disposition: attachment;
	filename="draft-ietf-avtcore-monarch-08_CommentsAlbrecht.pdf"; size=66937;
	creation-date="Mon, 12 Dec 2011 10:53:39 GMT";
	modification-date="Mon, 12 Dec 2011 10:53:39 GMT"
Content-Transfer-Encoding: base64

JVBERi0xLjQNJeLjz9MNCjYxIDAgb2JqDTw8L0xpbmVhcml6ZWQgMS9MIDY2OTM3L08gNjMvRSAz
MTY2OS9OIDI3L1QgNjU1OTcvSCBbIDQ3NiAyNDZdPj4NZW5kb2JqDSAgICAgICAgICAgICAgICAg
DQp4cmVmDQo2MSA5DQowMDAwMDAwMDE2IDAwMDAwIG4NCjAwMDAwMDA3MjIgMDAwMDAgbg0KMDAw
MDAwMDgyNCAwMDAwMCBuDQowMDAwMDAxMDIxIDAwMDAwIG4NCjAwMDAwMDE1MjcgMDAwMDAgbg0K
MDAwMDAwMTYyOSAwMDAwMCBuDQowMDAwMDAxODg4IDAwMDAwIG4NCjAwMDAwMDMxODAgMDAwMDAg
bg0KMDAwMDAwMDQ3NiAwMDAwMCBuDQp0cmFpbGVyDQo8PC9TaXplIDcwL1Jvb3QgNjIgMCBSL0lu
Zm8gNjAgMCBSL0lEWzxENjcyNEE5MzE4QTA2N0EzNzQxNzkyNUI1RjdFOTk3Mj48MUI2NTRFRUNF
OTU5NUU0RUEwOEUyOEZCNEMzNjJDNjI+XS9QcmV2IDY1NTg2Pj4NCnN0YXJ0eHJlZg0KMA0KJSVF
T0YNCiAgICAgICAgICAgICAgDQo2OSAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNvZGUvSSAzMDgv
TCAyOTIvTGVuZ3RoIDE1OC9TIDI1NT4+c3RyZWFtDQpo3mJgYGACIicGZgYGxigGfgYE4AeKMTOw
MHA0IMTeuQnwyP8wFdB0eOpY1pLM9o+RReeBSsOGgxZOCazObFnMEmIzRAuaFKYzljVdYprCdoWB
YZKnChQxMLCc9blCBLrAwEE6ZJQgw3FIgA2KGRjSgF7fxxbAwMB5YcrtHQdAQqYMDG8OM4DDisEW
iG0YGP4pAmlGIJIGCDAAhZ9J8g0KZW5kc3RyZWFtDWVuZG9iag02MiAwIG9iag08PC9NZXRhZGF0
YSA1OSAwIFIvUGFnZUxhYmVscyA1MyAwIFIvUGFnZUxheW91dC9PbmVDb2x1bW4vUGFnZXMgNTUg
MCBSL1R5cGUvQ2F0YWxvZz4+DWVuZG9iag02MyAwIG9iag08PC9Db250ZW50cyA2NyAwIFIvQ3Jv
cEJveFswIDAgNTk1LjIyIDg0Ml0vTWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJdL1BhcmVudCA1NiAw
IFIvUmVzb3VyY2VzPDwvRXh0R1N0YXRlPDwvR1MwIDY1IDAgUj4+L0ZvbnQ8PC9UVDAgNjQgMCBS
Pj4vUHJvY1NldFsvUERGL1RleHRdPj4vUm90YXRlIDAvVHlwZS9QYWdlPj4NZW5kb2JqDTY0IDAg
b2JqDTw8L0Jhc2VGb250L09KRUdNQytDb3VyaWVyTmV3UFNNVC9FbmNvZGluZy9XaW5BbnNpRW5j
b2RpbmcvRmlyc3RDaGFyIDMyL0ZvbnREZXNjcmlwdG9yIDY2IDAgUi9MYXN0Q2hhciAxMjQvU3Vi
dHlwZS9UcnVlVHlwZS9UeXBlL0ZvbnQvV2lkdGhzWzYwMCAwIDYwMCAwIDAgNjAwIDAgNjAwIDYw
MCA2MDAgMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2
MDAgNjAwIDYwMCA2MDAgMCA2MDAgMCA2MDAgMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAg
NjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2
MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgMCA2MDAgMCAwIDAgNjAwIDYwMCA2MDAgNjAwIDYw
MCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAw
IDYwMCA2MDAgNjAwIDYwMCA2MDAgNjAwIDYwMCAwIDYwMF0+Pg1lbmRvYmoNNjUgMCBvYmoNPDwv
QkcyL0RlZmF1bHQvT1AgZmFsc2UvT1BNIDEvU0EgZmFsc2UvU00gMC4wMi9UeXBlL0V4dEdTdGF0
ZS9VQ1IyL0RlZmF1bHQvb3AgZmFsc2U+Pg1lbmRvYmoNNjYgMCBvYmoNPDwvQXNjZW50IDgzMi9D
YXBIZWlnaHQgMTAwMC9EZXNjZW50IC0zMDAvRmxhZ3MgMzQvRm9udEJCb3hbLTIxIC02ODAgNjM4
IDEwMjFdL0ZvbnRGYW1pbHkoQ291cmllciBOZXcpL0ZvbnRGaWxlMiA2OCAwIFIvRm9udE5hbWUv
T0pFR01DK0NvdXJpZXJOZXdQU01UL0ZvbnRTdHJldGNoL05vcm1hbC9Gb250V2VpZ2h0IDQwMC9J
dGFsaWNBbmdsZSAwL1N0ZW1WIDQyL1R5cGUvRm9udERlc2NyaXB0b3IvWEhlaWdodCAxMDAwPj4N
ZW5kb2JqDTY3IDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9MZW5ndGggMTIyMT4+c3RyZWFt
DQpIiaxWwXLbNhC9eyb/sOOT05EoyakdJzcncVJ3Jh3XYZvO1D1A5IpETQIsAErW3/ctyNiULCd2
WuoikuDivd33dvEm3Zt8+DSlwu9N0nRKM0oXe7NpMj2kKX7dv6OXyTG9PJomsx+nLyit9w7oefr3
3pTGs2T24pDSd/2TMZZPZ1iSUffy8Di+PG1zbSe/65wtpU4Z31gX6LN119oU9MHZtqGHr18T+tyO
6CxPrp7d3/jcBHaGw/idU4vwlTAPXj+1asW6j53+0IU0Oefkgwqtf03nZmFdrYK2RlWPiPghQVAT
BiHPbhrtGKF+bg3TbESH09nhI/H9ZtRioSutAueDkN9DdXhdJHTqcjYbSe0L9l9jd9ebdFfBvjPY
L3bJ9ZwdHb6K2ZvdxobaYj5uE7MlxYeS9dEaHawTCZ66rNSBs9CiSIRi02V68ai05KK6seawGKtl
yKzjcQ2VIN54epKEm3AH8qt+EZCncx+cysIOXvfppKX2VHNtqXG2sR64lSE1IBJ58I1oWThepm8v
aKVDSYoMr+L9A7X/45KuDi7fv31xjDQ/p3lls2sK64YpWHIc3Sshag5OZx6PCuXiJjXnWu2seRDf
19p7mIgAzHHGjTiK/mlVpcN6BLxVZVe3WIsWDaPS8MtA8gxPzivtS9hTGwLIo1fHJ8kwH74tCizz
FEoVerIdBV/atsqH4TJrgkIcRR77VtxTEoB4VKuqItNG2dnFgG7FS2WCZEMNo/UxGuUU1nYfaelP
gCMhsVuGZjUip0KJ1wBovkAQ2mpnNe4DWJU6QxlD4LqJKCCBJZJFixaAMzjFqYLlCyEQSqjjASfe
QvWyusfX8fINZ3qBXKimqXQWux/yfHp3h3yr9ZA/SBnar/UNpJjjZcjKfQmWOUbzkpgcZJ9YjS80
IlwpFmsnCzZb3B0qj80/I2vIr4WK5hWPhig3KjxnytnrwkAl2P/q2SAi3sGkrYeMAClzCEY1fNtV
w0JuA8Kj3kSqbmQ/uZGU7ioTkC6tzrAKLmZVx4LK4IvJkPLY5AnN4FOcPRI1iLI/irIf3Re2hiKe
+HZeawgmuqaXSTfVkNyuLaACO4lFcflYb6B5A2e+PImc4t9XTyGFaJvQ0LSQ+VV/Esht1tZsQk+b
bxfTmSnQCDg260EtU+Wv6b11oHB1cH6Wvr96nsioCNyZ30abFXLA6MSqKm8p16iQnrdho7PcB6G2
E+ljn2FC/4k6zlrnsPJuVa+07Qz2VFEGYCpDaF5PJrlCgdHtr9klMj4S64pJnCZ+0sed/A+pjREH
nJbotXmnYyTkRtdtLUw8PIu5FUq/ab/Ox2sxTdvkcgIZyQCoVCb/EMXOva1YdDVf9+keJBDt16w3
7Rd0zUjjeVSlNvAaxpeTw404tfV8n4Z03AWML0rdlV40GigDJzPgkW6jY/m57vFEXyPIvlRY5I8d
C7Rkn+w/Lb+7rLXSsBLH0x16x8bxLvm2X9/aZu10UQbRrL6l98AX27zvvr46yDCn5VRE4gIcslsf
YvHERQ36q7gXLcgENEsUS/ktu9+NhC/lQ/PC5HCi+VNwjBtJJTy7Jee7yH31FLYBXs7zcLWqku3z
VH9Q/sY5+c8LmW+zv3qxnqV7/wowAAGhjBUNCmVuZHN0cmVhbQ1lbmRvYmoNNjggMCBvYmoNPDwv
RmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCAyODQwMy9MZW5ndGgxIDQ5MDg0Pj5zdHJlYW0NCmje
rHsJeFRFtv85dW+v6U66O2tn6+50VjqBsIQESEiHJIhEFCRIQkASIAICAgZQcQnq4BJQUGcEhVFn
3EYZtBMWO8EF3zDPFXUUwVHfuAwub5zoqOD4RtL3/ep2J4DjvG/+3/e/lVPLqVNVp845depUCMRE
ZKcNpND0C2aOGGVXSqcB8z7gooUr2lalzEvdQ/TU90S8eeG6Nd6HH277GvUxRKYbLlm1eEW3a+wo
InOYyPDO4uVXXdIx9Z5dRP6niTofWNLetujQD0VXEj33M8w3dgkQcVeLSqL4rWjnLlmx5sq36Mlm
tPcSWS9cvnJhm1g7512iB+cSJe1c0XblKss1Njl+Eei9l7WtaF9kPJhN1PsQ1ntm1cqONeAbX6+c
37vq8vZVTz+wxUPkNmO+bmL1MG8lA2jvNYwG11nRUmmjS4TLYBAmxSKEQagq0fqbN5D+mWU2beVl
KylIXu2U+lnkOiLjY2JxkFjTNNmrfga4kzJQZisLCPxoH8TgY0kt+yMDmiaOgbgxBtGvEekXet7I
06IlLaIjtILuoG3AjebX6DGsnAD8EVKYuIkq6S66gt6mWdrXwProQfqKimkcLdEi5KROivC19CAL
EhhVQW9RO20VlUpA/YKYhnGpsotvoBLM0kh3Uyq9jhmHaVa094gs6EIA/4oy31yslWrf8EH1JW0B
/ZorxVH1CXqV+jlHpciN2iZth7aT4umEkjXwO22ktgKjZlErraVrwMEGuo8Oc7OoEs9pt4KnJvDQ
SU/RKxxQSW0lF10I6p/RduqlZ+l1eoc+YeYELuQN/BYfMdDAocgh7VxtgbaS6ul8mk4b0JvFeVwj
5ihzlN3KsYE/Rz7UsjF3I62jK+lq2kJbaRcdoz/Se6wIq2gUs5TdlEFVNIcWQJp3gafH6CX6gM08
hsdzkG/i34p1qjJwCDajUjIkOEWX/h20AzJ9mJ6kQ/QG/QFzfg2ZKuzmAM/iuXwtb+Tb+ef8MP+W
n+AvYDDvKIpyvfqf6heRo5pVu1d7DOtmUCZ5qQiaqaDzoM/D9BfsbxgXczW/KQKiWGHVNhCJjNbO
0Tq132vHyE8FoK2iOux5Gs0G11fRjXSA/hNjD9Nr9Cn9HVJS2MouyMLLfr6QZ/JacLGbv+IBkQL9
VYjlokccUQLKYXW2+sTA3khypCfyVUTTdmkh7Xfaq7p+x2KdWmhgHq2iDl1j+7DO7+k4/TedxBpG
9oDXKdyA/W7H/B/wKZiTWVwnfis0pUrZqrykutXtkfMjKyLbI3u0Mdo02JaCk+WmMUjjYU2zqBlz
3wBpPkiPQzN7YD1H6UtO42wu5XP5Im7iVl7CK3kVr+ar+RpI9THeywf4KL/HXwpVGEUy5BQQC8UN
4i6xVxwSR8VxhZSZSpOyWrlauUvZq7yhfK461GK1VJ2mtqpXqesNZFCMKeZXT6WeWjGwYODegd9F
hkfqIssimyLPR45GPtbitOe0T8hIpeCxmRaDx2ux/5vodrof9vE4ePyIPqMvoPNvIAuFLZwOjj26
3mrB9zRwPpub+RKkJXwp5L+Bd3EPP80H+Xl+iV/hN/l9/kowuB+ONAGnYJa4BHu4V+wSIfFHpJPi
f5R8pVgZpYxWJiqt2M3Nyi3YzzblfeUTVajJ6kh1ptqpvmBQDIsMdxt2GA4ZXjT8xegwtsR8xGkP
gk95VTyvTlSW0wM0XSjKX8SbopKvFT/woyKLn8dqWcp0ZbqoFRNI8AFY+QpKMu0w+ow+kUQOU6uc
Q9wjSpTZar5iozU4byTmiJtEKz3CT9MPYgosbZ1yWDwg5is71DvViXyMOrEmCTt/RzVUwxOhu7do
NTRUojypviZnNJiVU4YVwq7drH5mEMqb8INVLJSXeQ7383SRAmlNELeTH20H96M8Fyfwj7D8Xp5N
FeqHymYxVbwH3HK6i5/HHg/QcnGAfw29VOA8Xs7Teacykq7j1ZDGOLpU/JxyxCqRA3ueRd/yDZyM
k/sDdJMrLiFVsYuFdEQ0Q+tvsEsM5+tgpytoE3dRMQ/wQXpV3EFjuV159pR7oFDwqX7uVqZQN/+g
vqS+JFTM9DykWQrvEYSFPAgfMQsn06fkw2oqyCCKYf/z4AHPI6c4ydeI5bSUtyv/zQ+LGrqA2pUO
MZnvjpxUa5TRkFgfvEmtcZyZDJWGLHUMNP4ZTYQ1LsbdskT9wHCDrCtvKSe0Zs0XmW+Ij7xP6yGd
KfBum3CWptC7nMIX8wxVEw2qpl1Eu8ST6vtaKtvYR3/QcMIi+7iSczUvr9bieAYs/GLjYwP3qJvU
jepa9RrcTT/Aa95Ed9K99B+4TR7CvVUAOZ4Hac6F71mKO6KURlEZdjeRJsErnYu+6XQR/GkrvOQl
dBmthuf9Jf2WunFDNUAeF2PcJXQp8B24oa6m63D+b6bN8AF30yP0B/G4uF/xiVvE78U6sZTepXeV
F5QgX0RH1FvVTppJuTSDE7FyObTkwbjN2ltYrYgy4P3H4JTC7rUvtKPabwZex3yPgPc7jZPoC2Mt
UbCmMVg9sapywvhxFeVlY0aPGlk6YnhJcWBYUWFBfl6uP8fn9WRnZWaku9NSU5KTEl1OR0K83RZn
tZhNRoOqCKbiev/kVm8ovzWk5vunTCmRbX8bEG1nIFpDXqAmn00T8rbqZN6zKYOgvORHlMEoZXCI
kh3eSqosKfbW+72hw3V+b5jnzGhC/bY6f7M31K/Xp+n1rXrdjrrPhwHe+rQldd4Qt3rrQ5PXLemq
b63DdN1x1lp/bbu1pJi6rXGoxqEWSvWv6ubUiaxXRGr9+G5BZjuYCqX76+pDbn+d5CCk5NW3LQpN
n9FUX5fh8zWXFIe4dqF/QYj8k0IJAZ2EavVlQsbakElfxrtU7oY2ebuLD3ZtDjtoQWvAtsi/qG1u
U0hpa5ZrOANYty6Uuv542ukmJnfVNt18Zm+G0lWfttQrm11dN3tDD8xoOrPXJ/PmZsyBsSJvcmvX
ZCy9GUJsmOnFamJjc1OIN2JJr9yJ3FV0f+3+eolpvdQbsvgn+Zd0XdoK1aR3hejCq3w96enBXu1D
Sq/3djU2+X2h6gx/c1tdZncSdV141R530Os+u6ekuNvhjAq2Oz4hVrHZz6y0D/XpNZ1c1houHJIs
S47858IgQt6FXnDS5MeeKmTWXkFdCytAhq+ZMSq0CBpZGrLUtnY5xku8HB8y5Dn83q6TBAvw9//1
bExbDGPMc5wkWZV2MmRq6B+shwKB0LBh0kRMtdApeJyot8tKiteFxVL/KocXBcRH0yHbtubxIyB+
n08qeFM4SAvQCG2Y0RRte2lBRg8FRwSaQ6JV9hwc7EmeJXs2DPYMDW/1w5L3knx0JIfM+UM/CY6U
xPol40Oc8n90t0f7G2b6G2bMafLWd7XGZNvQeFYr2l8x1BerhRJrm5QMEauJDEXvhVHOHSKWjSZb
SM3Dj1E36kVhkxlWqWPYOznkaJ0SzZutPt+/OSis/U2O0ovTw2JshsYHzm5POKt9Fnu2LgUMq/mi
oXFOV5f1rL7J8EBdXZP93sldrV1tYW3DAr/X4e/qReCR37WqvnVQo2Gtb1NGaPLmZmxiCY+HtQqa
1O3nW2Z0B/mWmXOaeh14St3S2NSDkKa2dVJzdy76mnq98Lk6VgxhZcsrW9TAsPQeRIyyK6M3SLRB
71V1hN5eGGbSceZBHNPCsIjiHDoOX4nUvby3ED0c1o5ob6o/6NZwVvijHpb3pqSQOX/BVkSzxwER
/kjM4xL6mLZyAHfuYcTQn6BnF/0Ocd4hduF19Bkn8mGuwM3VTj/H7XMMb4rZuGvuw6vlfrxklmHE
LkSKGyiNhtMS3L1L0NOL98ZMclAebsSF9Laooj9zJWYmxEtbcXPuwt23AXNdi1vxGdpLz4GbZEQy
d6BvA3pfx93VQhNwt7bj/dfPv0DE9nPQOPUXXJO+0kzMdDrtwrho6oslOdtgaomlU7jpjyMC2sIr
da51sSCmrsY6LvC6AjMtoJ8D5lCIAngJPEofIdbPx7vDgdfAp/wF9nkrbvQDWH8heGnXeVoCcNEd
eHHuQQQywHmYZwc4XwjJm2iZaMRbMBEx0mHI+UPMJd98EpogvWgizEGYU6Y+RCaFgPGCuJv7eAIf
gfQuwpq9kMzb1C8qtQG6HrP/AuuVQHvxvA5vkYUxjUu9XIs5JXUn9inhOu0TcQhrbtXhPrQHsPoG
HTZg5kEYDrlJWAKpNWGcBDnPFmhEwkxIUQK40KETO5QvyH2cgffqG3S19gneXxnYr8A7OwYyRxzY
TvfgrZ0lDRRvsSyZR2HwQ1SepVPr37+q/+tPLB6s6K/7KDwBfecj+lTASQ2FsUuB/d3PCeDbQona
t4J5OB1An+ClvJSegG1IGQ1KblBKUUldOwTLYLvLEPt9Ags+E3bBnpth0XcOyXMDgCBPisk0Ks/1
Q7IchDzYu9TpMX19FyxuOq3CqZT4QUA/7KuSbgH3NtDFUYYwwz4OsJmC2ilYWY32HQ3TjuAdIE9q
O1Z8Wz+lzZCGPKN3QbeLYDeHwMNCrJCFaPITYBZAa5vw/pnNKk1G1Ik4WiTAUmoQV07levD+Mvie
DR3W01ouRO0OwFrdkjuRenU73oV3OgFzBV72i3QOpLeYSk2Ipy+nQqQrQJEGjqJcdIKLYp2PZkSy
KpLU3WxYdwr43QrZXQ27moMyCa3xSFfSaES/y7D6Mt2TPAL+r8A+p9Fk8iE1YPZHEFnn0o0YdTtG
S3/yDDzCXhqtfQmNXYkRy7DydpzwkbRE5PFUvFzPFbn8FNJ23o5ag8gVY2HV20Wlsglvrldh2/fh
zfQgPcBX4C12Jy3hDuhqLx2E19iI85eJd8xBSP0f9Cf6Nf0ecf+reHGup43ofY7+Dv1+Dvpf6PaJ
9xTkJeENPQ3O3A5Pe3rejfqccsah+fgKaGQvML8VtbwZMUsuv8Av4A2KQ4V39TbA+/wg4GV+j//I
i+DZTnAnN3I5XmYmLqC7Qf2pmMp/4G/ZzgXshGZPn7+XBSJ9ofCv+SG8DFfwhcDt5AXcCtvL00ni
yKhTOsCH/LZC8kr0t4pkRZLf4/CUf6NtgL+B6j6cBSRwIv10FL+Nb+S3wflv+GXQZ0EPgaFysP7/
4QPvO/UbjigJp9xKr0BC22D5B/lp/l7nU3cWqMf2xy/yz4b2OoiL7fWfyvt4hgRdBhKMUdkMlT/+
bDH5xEpOh37PKAdlC+s9qpd7cd5lvxkvRln2cI+Oj8CqZftb/pnexn70vTxO6/T2YpzRG+hXtBOe
BCDc0DbsgtroPEjkPdiGHRbwICQxj7xkgB5eRnob2rgRvXKVnbST/8In+STO9zLexyf4z5wvFkJq
IZybGsrnD4H5M3/Jz2PGFyCF+7DWMcQNr9FhvpTXgMPD9DR4rIQt3woLdNKXsPankV7Ai3ot38Tz
kJ5Feprv5Q9OS3tICtJS7otZhdztOUhN9C1e9t9DX6/pN+Yd0m+Ch3twag/xK3wQfvD3sNxeDuBk
pPHFXKdcSy/q4+/nZ/hh/p1+xgN6KtSTNpQOQQJntk+nSaAGDN2f/y6ceXf8FHwCryTvDLmT/xf4
8c1xJizU444oSB7kGv9iDI/gJDoJgC+Ef06CH71Sh2VICzBewnRYdhF86zLcYpPAs5wLUzZqB5WD
PbNGB8MoxuvFnvjcURtkGWfXyx7L6OqaEcpBWgV4EvA6QKX5yDtjGIU8yKsBErtF739AOUAhwEHA
GwCJ6QOmD5g+YPqAqVbCxMpTyv6eXA+W3rvHnTvqq5p0ZQ9pAKHcAaftw9wXx8r5sXILymEot8bK
25RNPRM8CTUWtJm+Qq4BBPa2s+ecC0b16pXySr2yYxCzYw8wnhq3shNc7QRXO8HVTnD1FXLGrDuA
3wH8DuB36PgdxPpUvqLYVLHKzp6ElBgGlRqr0qxcRKMwRVOsnK1c1DPK81xNqzILUz+p5w8ojci3
6Pl8Pb9Azzv13k69vlKvr9Tr1Xq9OlaX+Ygzco+eJ8hcuVCZCV17lBnKVL2crtTjVHqUC9CW5fnK
uXo5TTlHL88DPg1lA+hcKKcqk/X2uWjXoZyCtizPUSb31HlKa1ahPR99iMwUia8DD3XgqQ5Ckpgt
gAcAH+iY+cg7Aa8DFJ2SlTqkWqQapQYjgpgjiJ4gKUoQqRppojIRPVWgrUIeVCr1PVaCqhIrVUJW
lZi5EuqphHoqyaRUIvcqZVQKCAKmA1oBBsxTjHHF4KsYKxQrJYgqPIpPbMZZ8SjeWOkRmygbZbbY
1JPtCdZYxF6aDmgFrAJsEHt7DK6EmiTQSdoRgAsA8wGdgPsBTwLMVB3tCcaJalGtXCAuUFRYd9Ge
yspRejl6bLTMzIqWtvRRCTWXK0UQUxHdD1DAchFYLsJWB1segIDpFNBzgNcBHwCkwAsgjAIIowAb
LMD4Ap3KqNN9BdAACoyoAPOfTWPQR3sAI86YRWILgSlEqxBjCkFbCOwHyFkfIfunA7YAnov15ejG
nKMbZw7mygG3I5BX67UE5B4lp0dYEsKQL49PqCmH3C8AoFPcBmneBrndJi1EyEM8Aj3VMYotgCcB
BqUXqQipAKkQKQfJh+RFggaVbGhvK9IWpNuRbkPajLQJ2kh6MvBcQMwvW1nWWbal7P6yJ8ueKzMd
EG1IraI1aKWUFFwwLqc5vcYhVJpLdv6Hnu/W88v1PKjnqcH0ufbjc+0vzrXfM9f+i7n2prn28+fa
J8+1j5hrD/OCYGrA/l7AvjVgvyhgHxuwlwXsowP2ooC9xsnNPJvs9KyeT9LzUXqeo+dZPLvHTpan
uYV8Zlg8F+z1Xe/5xBdWucdzoy9sRnFDtNUSLSZI5H5PqW+xpziKyY8Wub5nVMxAs/i3ZOJAsNj0
kmm+KWgaZxpuKjEVmgpMfpPHlGR2mR3meLPNbDWbzUazahZmMieFtQ+DuLCZkowOWRhVmat63SFk
LuRtjLCLzQIPg1Ci0iAaZk7ihtDBhdSwwBv6bqY/zNYZc0IG/yQOuRqooXFSWqg80BA2aReGKgIN
Icv0lqZu5tub0QqJW8JMjU1h1iRqY4b8tWkvMRdvvC0jVjY3yzFN3SrfdlszpayrTqt2TXSOm1z3
E1lrLA+c/tICZzbASVbo7oaZTaHHs5pDo2RFy2pugOTkb1l7RYUYW1/XK8pl0dzUa90gKuovlHjr
hrrm03TkBb6ul3yy0OnIK+nI+yO6bFEu6fJkEaXL1umyz6LrrvLV13X7fIM0VTpN1dk0i8+mWazT
LI7RKFEa3xk0pg/Jp9P4TB/+E032v0GT95M0Z0izfVLg//i4Fy/Po9216+WvqFv99e2A1tCmdUvS
QhsWeL29VMtHY7+9zm9dsHCJLNvaw3zU314XqvXXebunrv/n/tB62T3VX9dN6+sbm7rXB9vreqYG
p9b72+qa95zTNmz3WcvdOrhc97C2n5isTU42TK51zu6f6N4tu8+Ra+2Wa+2Wa50TPEdfS7d6mKWZ
JjXXzo2We0ScFQbcmuFrnpTiWDVRt+YJvrTrMvpU4t9QXKA5ZPNPCtkBsqukpqRGduGUya54+S8R
sa606yb4Mvr4N7EuB9BO/yRKq19ah5+Ojljl3/zp6OhYc3HHxR2y1H861qwFSDVRB3WsIeygxqbf
bx54Y+mbNwE26z5a6ehoXkO6TjvWkpxtjcxOTz5UW4uZueNMI6COH3/SMvBK1AHTdaxlUEnCtTGz
6ZDhPaYhyWRsFvnQk795Msg/cFHIRJO7jaYw2/YCa1BlRSGr0YDKfkUR6RaTxO1ncpsvuDotcL7j
ROW0gcrzHd9VTnMMIJCoHKiUMLLU5/Q585DBx9Epr3LwVNBAP5BXPSjXs4pHlefVN3GzO6m1O94Q
FjcFrWy1WOAArccsfeIhihPPBm1e53PO150fOL9yGpx9nEJCPLvHzMcoLB7aV2peCc/6tLgHEdbX
PJ3SAo7v5p3odwx8N6//RD84qXRUgruRpexTjEZ/Tn7B6QrWmmz0ut1eIy/Wq2npXoP6ZiQ93+PJ
50+jJQRyQPtcTVJ/wNsrFa+tcpyrScGGF91szOFl5ug/CwaGFVk8Xl+OPzcvv8BSmJ02zeP/wC/8
/jIlZ5rD/YZbuN3KhPIyraZ8RHK5oiWUW2zlCdin5io3hvmzoKMue6KxcGJFeUIxF2sTy0eFxbdP
1VloRNzCXWkBqq5mx3f9A/P6jzuORyvk6B/ol+AaN2Jev1PP2elKHZc6bmRp7VXBxpJaTq0cM7GQ
xo+tKORgKWqThqPmMLsKKd5qK+QkFbUUgVrV6AmFPK4cWfXImkKqLUHmNCUUsj0OWaIhuZBSGRkN
+Z7ByvXX42pKmdkQypsxpylomZQ5PjMlMz6zssaiHadq7a8UROkAJGnHKwa/Zlo9j5OkEsrGjB09
KsU0Jt+fY0xOShk9aqzBEMWXjy3Pk33JSSaj8i9oxafbll56992XXnp3ZceMGR0S+LxT38Wb4pwm
g0uxxputqHi2Xbp0G4i2VQ0SKd8v3759+fJt25bPXLNmJuCNAdVls1qNxlgZcSzftn2ZJGrsWDPz
wrVrcFN+hNjnC/UzWGtR0GHYj1v6CXEnPbHFrOkGOI0sFOHzowZ4fACb7z/T6D6SBuZLg62pnw18
O8znG4YJxLzIKeVJzJlB04MFRbZhDmFIjU+0ulKMRoMjNSUxeWKiYZrFkvhAfC6RA27DnflyHxso
jd0b5ambN23gRKWj34HVcOBgBONYZlh4Ho9xucoHBSiSk1zyX67BS0G+yBfzKh8vsMW73KbLLr74
MpPbFW/L+02Qv+lgwRf649KcVtvLkfBDD0fCL9msTndcDk+NQAIlkVOiM8ZtkUVY0mHV6ark2OIy
pqY4DEZwa7WCafCbgBBJUHrWQ308bZDf7yS/x8Gwzu5Z3CYJYRpUvKtsjCiIqjs1xZUiOn+S2687
Ilpkd47NDW5f4ikPPcxTXga3aXE5kf3gFm/7WrVKnQY2WoIj3S0eDyH+etTRoj5qTmixWMyZ71OL
ObXF6UxrcTjM3GIymd8vtbHN7TVPvx5HbgTrAtblC5AFtOrQxT1w3CH9itSwM2qbTl/UQH1O3UqT
nb5RurzFHWmJrrTI5uz09GxeI+u8RtaFJzJXxz2UmpiYyr+W9cjFsg674EDkiPgDD4dJjQ6m/Qe9
SR/S3+BB96v8rXie3kxAgClMT/N2stIKzjptcyP6dWH6OCZKPsjOyLGMfLdf4eED74zyu602GV72
CZOaKDrh6dODNjoIPRmEW5We5nz4l09pxDQ5UbKvTE089ajovPJK8HRY+1hh+hrBdCa8dI85Tn0n
zh2/opezSb8BpvXrJp83Orrx6IEVs3Irps8ol9nXF1SMP18C1v9Um638xbACJr0iON5iSWG3Ramg
cZbJfK6lxbLMso6vtNxqvtVyN99jeZgfs+yn/fwCv2Q5yp/yf1u+4+8tqXEWjgvzi/uUuInUYglz
D5hqMT8zQmHlmDPMB7qfhlROzBvALRCTy+p583hIMGOjR0P5cGCuM8PptooH45LinW5D7j+a8twJ
tmTDb1Lj3QlxMOFPsO/PDfKv00bw7j0uYfX3ad+Qop3oKTEXwc19Q4XaCSrQ/k4pgGTt7/sz4y3x
5njRp30Pz/dNT1Z8iRwxTPsm6C8yZMZ74nNcK8zZmS4azgUGe44/3lflKq4yuAwGe3oVbrVX94/M
rYp3l/6qj404OsUbo+KF38c9APODyx+Hg+McFz09cPZzxHBHfpo71Z3iTnYnuQ3GzIysjOwMT4Zq
LMgvzC/KH5avGuNsVpvFZraZbAajkp/jzA2SNzE9yAFjXpBK1BFB9if4gpzhRpZvKw7ScIHstLcf
hi9wPQ06ca4480N8E0x2Zie6q5OynanVTpmlZGe7qnPC2g/BICoFSZlOZBkOZO4EZKnx1X6ZFSSl
2FFDpiSBTsl2xVWXWJGlyFpWktsnJ/lrMBWVhKRUjxzlqRZWh3Niqsz4J2JjyXYzJzt0n1KQj5+y
MofuDlNT8INLpADJnyOScZOkIo0e5SpTPr++/d6pNw7Pqk9IRa3hhuHZdY6Uxtph7sJx59z2QG0g
rXDclM0PiPfeiHx93zUTynx3Vl3U8QY7ZD3nzsqLOq84XOV3+yMfHuy94rWqHHcu+w7K03YcIdXn
6vfwm909LnNGWPs+mOA0ktmSEcyY7pqeoVoS+sRjZOMdQYvDZktwPGsxC4kxAONig0Hws+bYnx6Z
XBlJfeIYOcXip8hgMdvcIumAuB4RVKp4DY/txU4nLyYHO54RqyiTfsWvRS0IDgIuDBGDHhRV90dj
BXIMVCFySGPHyROHzmqMLKV5upYHHdmQfzt9P4ut7JV+a2C57sm8kS+TLAluq9mtfv/D3FS4ujRX
YqpaepHR7Uywm2VUtwuSOIazFGBvt1HUNjY9lREXMKhJRGFu2We1JVXlGOBFqgckcyNL8UJN0f4U
LM7IHTMlYX38TQU3Fd5U9EjhI0UHbHuHWewua0qZrWKYWuQflh1IKsgu9NuS4qSl2P/i6k/5h2sg
RS00D0ry/adigjQ8w8fhWOPYDqfWstdisdrSw/w/e/W1D3ALwjwBvPkjZ1VejV2spBLEPi2UDfo4
sYKK+Y7BU+n47oQ8lMik6+uvhnyPO/o5JkaKihGnM9OT60pLyfPmJ/vSgpTodwY51ZMUZFcustjp
uv76qLzx0WpeHWgu90XjnWR44dzyiaJMj3tMxtgtGfNfRqOJTANio7xYTh1h+mZ1o+eJqy973G20
2BzO1KW9bb/8OL9lXeSdvkafVNLaaz79cuWSCwqXP3LdvDSTNdVR+tDF73aNb+tYE3n/V9JWf6d9
rEJQBMXvWV7BFIbXGj1qVJlzfO65uVPzaisuJ2On76aKX6h3ld1d8XDZIxW9iX2pryS+knQ49b3E
/0r9a+I/UrURTjluX1IOFOcMQ4OZqBSZE+IChU5lBBhJI4M/k9zZ3sL8YjdUv8frdRWH+bY9+VWj
41Huc1UZ/VVjw2wPWpOrlMzMcUr6+BF9UEGmuP6pOPe40Qaj/a99vCGqCBkeSxd5/Pj5jk8h+2kO
GftLbQwcR1NGx9Jd6iaPH2fUaWaOKcvNS0xSDXlj/EEZ5AY5tyw/KMPioIx0WWoF8W0gUDFvdQVV
rOaUaAiVPxScIAaFXvJjwWmq3tK1NHhGokpSEtesPxle/vnwhFSHI2nH7jt/37Z/Xna62z1l9V33
XjP7zmKHM86ZNvuqe+9/dYHYNWbfgm2fzS11uBxpCR1PrWrYOlOeJe5quXhr5ZgkS6qjsGrWcz9r
vBt301F5nhCRZZGP/hC04z73imyfIcuTmQKxfro/K+vZlIRkV5hbg674+GeTvT7fYqEg1lKEz+OF
4J9SFNXgy7Zno95D8bh8cF9lZcpjkEIJwKUkK2FxYzCBDfGLs7I8lJDNOArZfeIy8nFLMA5niN05
qppsw231JtSRO6SO1dPwCFtdiRfYQKVDRk79svKlHkvpz7KBSuc4w83DA9c6DuG04OCcPFI5WCaM
LF3NvjIe7RyMJwYrMUc02un0s6IMvMVvPTnZk57umaznkRdl/sviyGye36YUnHpVyi5yctAb8Xzx
wYAPdn5I2jkkV0x/CubEZVgycyxF7vFphpKi84rmF11WtL3oJfd7aV+kmd3SiFOkESeikuH1m5Mc
3twUTzp7snz0DMs/TGD5a0U+HrRkVamqlfLzEsP856AltcqaXuUwsalPbKQisXwfKBfn5Yb5v55y
uEvyVOugCZ+WGcJNyCj6vpNBpnzX6e88VPRg2TVovWlpmQZLpgH3d5oFWYYxK8huc+ppy8URDgTm
rWbnoKuQsf+PLNefY4pFr1EK7px6S9V9b/9t7xWXnR/MT3M4E7f13HXwkQ033ui1IxCfKl2Iemek
3eP5074Xvy/LK/eluNyu21569Pbd9Y60FFEi/RDcpwvSTYcX8VMpPx60Dc9Jyh2Tkx3I9mXn92nf
yf/aEowvUyeYa9UG8yx1jtmYBwHvgXy9sTJHL/1jcsPakaBVeg+MzjXbwxjZqaqqOUlNMuer+eZh
ieMTGxJbEi9NvCrxlsSNuQcS9+W+G/eu6wt7YhwbzCavMd+dkOvN87V7F/qu8l1V2PG/nHsJnBTV
tfe9t5fpdbqqurq6qrureq9eqtfpZRZmpmsYAcWFcUMQ28ENg+FlmGjcEuMOsii85xIVFVxQ1Cg6
gA6gwjMmJvr5wKfGJCYfmB/i8gUl+ZAnidPz7q3uWUD0l/d05lbdWz0zVN1z/uf/P+dUdnFuU2h7
8re2P1v225hzTZj0UDQTcLJ+l8SJboHi7SEQsduiVtkCc1mUSeEokmhSkga3sdkeyWMfWb8l3aXT
mb3D8P+qnL+LNcS6zHb+Q2MXSFLJQDKX1CdfRm+BFhCBEWBDj78Y6so1w2Yhvx22wRvHKV31VBI7
RqqaWMQBhOz1PrLLBKfqEZDAVDQVCOqdlIN2MA6d0Wa32pExpU+qMOAMDcOfqy4gWzCXi0biJryo
GNIqDDr85IoVRu0xFSSaYipoEDmqU2NyBNcGtYCjsaV66FHghKloloLDDrGVhu2EQ8DFYvo0YTpw
0WnrL1my+5Un/uXlcm8lt+69n5zVxnO0nUl0/aK2Q5AfHVi8dt0lF5zbiZyX/2DPY/ccWbLimf98
6LaFay8JOQTGbWFrz38cfPuFBzauvPnnZ7Zir3xntKb7LfZKF7jhebOOBG4jhq4kMhp16BWzzW6/
1AVYlwu4MJmwua0uG9BREF1qtdAOyqKnbNZt2BMh2rDZbRa4v0yiz/tO1YhPRQMejDtuzZuIMy1t
zijNBIGOiduwFKw/iBI+gWOArrtx5HGCJTpd7VkT18zwRv0iWXOLtUv+8WsPzVMWBqPwx1gzfKxp
hijIw6XqCcwToTfA5+Bzm96jF11K+hzlEmSwNut5bzPLL+fvgveb7rfeGVurPJB+Ej4a24J2WLbZ
tilvWd5QnNfA9UGUZ9OY2Qz5wtLw6J+GcuHMttE/YbHx1WbaFI9HyFoyHto2+hcQHf1sKBYKEhrE
KHHVFO5KJIxil9OQ7TLaw8Pw9yqVSHCU3KX70NNV4WZxiBuGB1RrIdBFfZjqMgstx8gObKKHSC6N
QNF+zVCJnWqmmUvnvX7apTdJTEAFPhbjUKYJa4acAYdRP40RyevCQ9qUVUEeC4wJMUEC6zeVBKjC
6iAY7CWJfWX0k01YDeAb+WQTFgnkqOawRjDweGbg8RkkZ5DX1lhbxcXjj7vImousucjaUdJg7nj8
xhjYOgaFWn6kdVJSyTnpXOdc+P2969bt/f5l5yU73rvnZ+92JOwP/+iKh9deedVa989vuOHnz1x/
/TNoReGJ+Xf/4Q939z9RLLWffuHyXbuWX9jX8emiNQ9cduGdd9aaBh577Ac/3LAB46IT46Ib20UU
FGCfmm4y6ZNNCsg8FdkWMcoEJMMpPDTzeLA3Sy1FWwgPLVwhFUu5CBNzzMt/xBwJ///koYxhB4B5
gpLkp4bJpnN4/z8DLfg5pfFPGdkt+dfy7+T155vsESA322LWuDmJ1R8+s8t4wa53RBJdFgPBM9WS
xYBmCXZxdnkbxiw7ely1RLocnpLnw6au1MtoAyhOQBd1aAQTrcPYND4CdWvYV6nrCVpTpg3gisUy
obDeZW+2NSMjjemMk2IpvdEQTZqxjcSt2EZicsgVIUjlhBk9EZumBF5sxkOYCuL1LSBtzI5j1yTw
AlWFANYgHMcwfK45aWNX3dq+amx5UswDpWJMntje1rJuR8+m8895dP6OdT98qdjbLt953k9vO7fd
w9M2d6zwHmxhSw8u/P4jjyyYcnkhiH51+RUX//tl94/csfSZj4au7LsnWwlRPO22OmHh4+Tv3rxz
8+3LNqmqgvdZy5XoLgR2rPnyqtkxxFlNQ8DIbIccxgQ95LZYrYLgm0iedJ5K1VWEljU8KoXi/LaE
ysSgu7Cvdcpp5Htk1aQsCwA9mB2eirXhzar0vBGazOYIgCwwWwDJskcAjc9NgDbNg8PwqU3AMo/u
McOngAW+hKPWPVhjPg1M8KUh41Y4jJ7GNoJ/p8CAWTfywzCMKYuQhbwWxvYdOIC/gHCIPyBQeFhq
qmMqPvLaCclK0bDhbRA2IopuJWelhdDXh3XmkEBbOTQD/t0m0IKz1lfrc+ITLVc1cRdL1NAO49u2
v9l0R/3rJ9/VPFq7E3xHPVZ8J+QuyN007gSHhqdVG9iaNUIjvpG+H+MbCU6+kZF9/8SNTCSRYMOy
dO9/fYV2KzrL1//VuJWaUbsV+Bx8rn4rCLw/+lOsfmnQBWbA6lZAje7c5JOKzPDoTtXMSEW7iocK
nm3CR2fjyGtHvthLPuXGJ9tML6mIobL2MKX7nikgwq5y+zBsVi3lcksX1M/oPkEc1hlUs5BPNf+x
e56la1inU2l96oQTBIsxkhKsgWfbu8uY+09X7Zylu1SOdM+IgDLEYmvtUE+qaRhmVSvniqS5SLov
BVMvwY/BieB1knQmSQRM4rHmHTlUHSFEFfN66pDGXjAKELmFg8U+LbBqNJ7qBFUNCs6o9EaLBj6p
JJS4ElNkxWB0sgxLsxSrN2blQrRi7okDPsr1A0fO1Q/sLdY47DXgNdXUHYduRegHbKa5H9qKzXE4
1XjCWCliDODHGM1YeaJkHKsYNKgKxgIXzTKFlvGc+HhiiK4nhjgXrcUHY1hnHMMH3Twhyfz4wV88
dduCGRXFl5u26d57TqYpmu+cv6bv1rTvNMp926KHzlh+GcvanfwJt9z9LxfSURZmrHr9vYt+/PwF
P1gZESKV52+ubXm19l8zKJ4KyF1Tiv57Ok5fDPsgeOSmaQ8vHNmJMGVymeFeeNNZpywwkB5fGgD9
Dv2/gSTIwBdUpUzjJ+rtTrWmZzAneU5JTU/3MX1cv6c/1Zf+KulQQDKZykCE0hZqGD2mcvZV9rV2
tMcO7Qnabqdo0UIz4QS51CzLhaQsJ5JiOJky67Qlo7GgESzRjNKCU1viuNkMxzkZUWDokI8snegH
/hv8q/263X7oT3j9fp9XDHk9nlQyKXk9rNfrYWhaQmmsLdORcNiCPRNKiiPjz6BMxiykU7LHKXsE
5NkG54AU7FbZpOxVHeYKoKHD6/fu9R706jGhTr2QQzKdlpltsBvQ2PZpS4Umtk/hzzpoCOhZ9Bf0
KK3Hjp7alJ22CLtwPb01iG3hkGad5HREy3MRxamVxrSCJLbXpQZNbi7F7rz0Oqw6TeM5r79WB7OH
Xpu88D+aaj/dhOkl+a4n4XXHCFbYsMggPOaCThfW6X488rvBh7UqwK/I2AMv/0rLqj0B7+/Rll8n
wnbdnZ/4P4RLa2+NCVrdZ6Rm8I9XxwXuUnTRyIOkhnsOtqG52IZ8IAZa4AL15Y3Jp5VfWX5pfd9i
WJVcrjwYWBNdqzwbNf44cn30cuVH6VWWVeyKyKqo6WzqEup6y2JqMb2YWexsmhk4NXhS5GRlSbOh
xTEl0BHsiFaSU5RpjhmUyZwVAr6gN+pNerNhR1IxXUO9FHk9q5seOCl6ZWBJYHnu7sD6wJaAKWXy
cYICgMghk0GBUDTlAs26cLy5JRATEzIXk02SKOVbWjgT4kzhqMPmt2VtFdssW79twNZkG4Y3q4l0
FGDnQw56Nb2T3k3vpQ/SRtpTjMUlqJXHDpIAVZh5Td0mCKIPNurSVS0ZQRQA3i9NYlP1rFAjDXp0
8kHDLCmSYliL1Skr0SSbTsOoJZyGKSaRBhGrnIZggsmSaubg4GAV/xelxzZZA5kGoDQ22hnE6KNp
pyAW3OV66igIwaBWEKIe/OX6m6/tW3/BiFYs+iVM9M/qOuGuq2qb4JOnX90996EVtf88q77dW669
vz/7wPlnrbiQbDkqh32Xtc669WvuxMva1au7SZfj6B79KfpnQBvYo16dZmEWVMAsoDNwLm62+xL2
Ym5hZjF7ObeY3+y2tPrKuZnczPI897zSZe7vlW713Ze1FPKOgDcEgc7UzLlbWwJhyWEHOsYa3qww
0VbrCr0UVVp1eqSYm2XT/KAsezq8siPvz2fzlbw+L7QvnbQJpx4gbHFkhDx+rX5Rf/oaXWzULN3t
hDli3ghOfs565snPRU4/F2sAH1Y8OMoTWSOO/mULx7l9PDdWQyZSAXv6WJa0IVpjDbRvMuIloHG8
Bt4TxpHRlUpFBq/ofkeeo9tJu5Fh9hV3XTBblafGfJDavOjpPtrFcMoZby2cd/6J5y9rufXjpbv1
/ilkSz71e3jvWT1zFX/6tP7pc+58qfb/zu93cbQ7e1417D3x6X895+mfQNIgSzqz9Vdi3xMx1NnU
4B2WZdbbmGXOZexK1yr/qsDy4O2x5YlVSRuOcrFAwhckbWHm+2JbgqjX5BYJ3lo9CeDxiEB0mxCZ
lwwJLX8tmuiMwy9xnCi5TYpkNiPJhCKywwEdjoADOTyZlCTBAN5tBIT0dtgOTRP5hglnIFQTO4E2
ECX8XYUA7AvFQNLianbYHTaH1aE3ytFYNB5NRPVGJ8MyyBiMJi2RDAy4whkYdSgZGGL8mUYiipSN
GsltHJ8n+wcpu5B9a5pAQs0rCEePaZ4hztAg8LXLNmZmJcQf3nrRTbVOsrIG5i/bWhUiUyMrT6/t
ajjFnLb+y05deMWNfzt3KvGK5f9+/r2ndc3tS52E/WEO3o8s3o8SZFRPv3/AeL1RR1ubFYYRrSGf
vxQOiz6d2Ui4lkOqkKOacggV42yEoyLrcStOp+gpZoiBo7xSKomZWJrkelBSkWUx7R+Gi9ROD4Ky
NRyRPSUgRyUArB5kNYVkhw9+4Rv1IV+PTgZm2GdeZ95t3ms+aDaYS7KcAWkqjdLDOCJy0SgmspL5
DGeW+YI5yOgYoTxzgG/s3IERkkk9RCIZVR08gKGtgWYj9VQq+cLodQBQX1bf7Rw/aSCaNlWUsQvj
66TMA+mxUgM9nlsd2yV6LAUy8ZnGCjwbLSGP/esLyI4Mahimu5ysjDwOtTwg3gUelWp+LY7VNk9E
q9oesvJW7eR+7crnZOzHu7QW79IVeJeK4K/q+fMN0GG2KRQlmoNeqRQKid5C2pHz51BOKRbFNA4j
ZRJGGMGl0LQoyCmQoBIooUSjYioUloUiiEZkAAS8K2YBmU3FaDoqgxSV6kvpUuR5pyKRMIAyFZKB
N+BFfd513t0aDzF4z6ADFATUDdRq6iClp4TS4a3Ej8ZDCn74VGM/SDKbJJZGOif24tinDybvQvU4
mwCrx9bZGlvQ+t178EC9AFfzju2BwyrpHiQPfuS6ozfhKL5gtxx/C/Ae3IAjx604cnRCWW1bGbg/
gLJUhZpF6U6yTY/MtlZtsyOPWx+PvGTcZjPrw+6wbIuF5Ug5YiyD9tWgvR2I5VKWAFbB0QJbypmW
lmxGLFlM/hiVdkLJzePwlC4n/SKlC3o75XJWLi8olfTOYLRZh+nfQjXAsk6UjOrN0oJMJi1BCDzd
Mdlh8puQSehaOnBMWNEazihNgmh4RtjevonwUk+aN1J9R8FctY5z9QkRdpMiT48Fi7O/AMPoIZAa
/Qwk8Hd89LMtES7EhbnxJiYMZyQA0SSyZFAjsLgblbmxeFQvB+GpnsSiMQcz1Gt3+uz8Hf1L37pj
1rLPV765sonkE3mGdkPj2z++YvvpZQg+POWmc+pbBe+SPBQLh2r3lsp9q4eW3b8cGpYP5FmHR3rF
L7jFsxddckf1yvvePhyIw1a8xTx0O+1cE97R72OvGsBe1QtfVW3Mw9yz2U3cjqy+LhWsdqWhEDwB
jflTIhSVoCgGgqIn1aItgSzMJgrZbEtBTHVOJUuUo+KvoIrSW6lM7RU76zrCalQaMqIuIqxcoqEh
lKj2exxxGFci8Xg0IipTSmSpF7TBNqXY1lYqilPCIQlAaBZa5FRKCcieqKwodc3QOWWKBQuKghQp
SpFe1ecvru3d2ItW9e7pRb3DaLvqncZIwSAt5ZCKViPdLLQbIQfqRwNIh15C28EJpFEWaP0g2HMJ
+cNurHRqGRfisZ1EKWickIx0gyIeayrHnX37pPpPzw7V0wpa2jNLkgEOtsKpeMjiQPRisxNP8FBP
YQa/UQZrQPV4mSz4jZVj5cbNI+9ocF37o+b2RSIsjmgIgtKLJY/gP0JWiv1jnxH8i1G5Jh0tOTQg
PwVuHjv/mhu7jm3uIyxAPsU25wfvq+msPmMI2wL2ABtwZX1ZqdtQsOXYnKviq0inGXptKqu6TvbN
EmdJLvIWA7YcW1lrg8CW5NfmvjLw+fxAFOpcyIqRv86FeIbMY64y7XIxtMj7ZYGRBR4h2eSQzWYT
EaH0LApSQmDlHn6cA5Fdx5td0ZIZ/8RWHm+3vtEXEZxE/Enf1zG9EXs1kn+XVkHrnnhYEw+ToO/T
GH034ucmg7+pP/mp7nrntewytFK3yrmc/YozmZGVtbp096MHm55q+pj6iP2IM+qpBdQL1AusvsUk
B8IlLLACgt/3Ac+L/iYHY7XqA37EYDTl3QRKVTtdAaqNquwF8Ab89zxxx4JmyWRqIheayIUbmmCT
EHtwK3yvEe4whSMYu++0hsRudPgeIP17WYytx5NOIYpDRhfH4pE2ODDqOoxNTp07DSkjxmAOMek6
OSSupyQbAqraaKWLNTrodKTSRPTSMU9Wt3HfQ/0vLiKBDZ76s5lnnNQ6r/YiMVi0oP5wRzz37T3n
IljWzPdvM2bEpTtOR/vHHzMEczEi3oef8lR0sVrl03zZ0xMplAqt5RnBeT2XBhf1XBX8Sc9ydXnP
feqano0923veLDgdoFyYVjinqHeElPL0Yk9pdv61yi/UnT0mb8ibXxhamL+ruDH9ZPmT0JH0kbKl
ZSoA+TFrVo6y5mbgg75CABt0QBSSOS1hE0ivTqNcGqbTq/PpdC4vJvOgbuvNwAANhaPM3YoJT93c
E2Ey75Mdsl/OyTpZCZF4IyZCwZ6iWtZXpobygAFSMMQGgyEQzIf0AZiTk2E5mUgI+VAogP0FOwyP
2lrl7krFZKJk1WwCw+jazcEgb24ZhnNeDEydmgdT5ZZtcAMIoWtVt9qXn59fnNeBvJrvy+v25g9i
TtzTuh3OAQFQgWWVPiEYIH4HKHiQuF7vzG3wrAkRoknyzk6BOuQZ4fF00EOaNQjoegQNew/wFc8B
DZZHOjWBovVadpL+AS2sL80opNtMAKrUia3Z14oHoQUP7jQe2Hilnhqcu9Rw3WuA/AA/OU+T/W7E
npzhqQ5+J2g3NVOdnfU2pq0gNLp3kxApEiU3hI/4nzCXwIQmUb8NsoNjAA2PQWxIetTcYzMkx+Ds
NVpzw7oJrg3nk5U16ITzyPG/yFKo1nLpbZXI/IVk5ZFbNi+Fb9SWfxNoRv6BDOMIflHyp1f0HNQa
TBbuSmoMEHvHHOwdQbBIbcMiqUREEqHgGFu8WCR90NBEJaKJkGz1EpnjMEOzB7NpyckIofXXTHol
YH8Vs+N6eWOCA3+DGZNG2onW2eM/J/geymh9TvPJzf7619pT+GgMUOFpJFDVzj8GVCHg8f3sxPfT
hmJqx5/F/RKaDma27QS7wTvwd763xcPgMDwsWqIgJsYkuW2G7xzfBmmr9C54F74rfgY/Ee1zJGjT
PM+5lshsP5bZCafDwThFm1+jNhQI9YVQKCGHQlFZ9Gc1cmNtKZRbWkplMWs1aHNTQW8yGfSi1euq
/zIeOng/j/gEy/MuVvRm4nWPV/oUpCRiihKPiZnh0RWqT4Qg4BNFCSIWklFqA0ASJRYvYW8VVasU
lf1+SfKJMiTzmT6ft60V6VyyF2WysbKczVqtNr1TtpnkWFubKElia1mKqWAX9Mf6YwOxjbEdMUNM
jSWKMZUpOWKrYrtje2MH8dow+lB1iX7YD9EquAsiCPU+nx4hvTiMrlE5Z0CnZ/XSLOcu5x7nF069
U2h/taFZTyVO7BGoAzzdnq1/VQfxtKoogzy136P1/5BVIqBG6j5ODhUCD9qk7vnYckjadul19TKM
4TrqNYX/dmo1+L/jZ4NaXP8h5vSDMAzD30qzIPzWhqQwemh+7WVqjRZ43iDjjBIZ/wN2w/b/0DhV
vUfpTcmLXZchzUjHMoGRFHr3aDql+4x4ZQZb8Y3YilNwQOVMCJp9gg+9jqAVGr1eyHn1VlozsuYE
09xMY4+NKnVjwqQ7kYrHlZQYtei1jzQVdE1Neh2m/Kw2dyvYV1jszBGJzEPBghgMSqIY8SLIQMnn
ZbE1QS9wKnI0KsmRCA5M177gZWXs+T58qlqg1WKBJtEnQSzOVC8AKTVacqRmpfpTA6lVqT0pY8qT
QTqJ8ZKPO5l+54BzlfOgU+9wQqeQ7vj+uKgbJJkOqp6lIlRjf52sdTbIWr0PX9N0jSjggCaM+JCl
fXigvFrFf66W2v8fE7tvknINvoNh+O3GcCyU69GikbvrWP2m1pSmYfUf0aI1BJ3qnGSG3v111zH5
+491v5zggQgAzAMBVuF2IMCv1dHfOH4pIGY/t58/Qh1hDnGHBOPr3O+p3zO/5d7nP6U+ZZo8lIdx
cRyvf535u+OwU/eg+W7bY+hJw5Pmx2xvGN8wmW5GKw23m26wLXMuc92F1hhMrcZWU8HcaeugCkyB
6+BNSaTYslSUiXJZfgpqesmxgxpihpxDrue4Hfw2wfSM41lqPfOI81HXY9xG/inBdI7zdK7Kr6Xu
dt7JPcDfJ5imOae5pnEz+VOEcx3nUmcwpgTf4Sg7W13t/GmOmdQ0xmQ1Wkxeo9eUcMScMRfWxQLU
m5wOux40uTFJpaMWXXOUpPIDIAfWAQO4io02CZs8vdc2XjEgjXGkSD7+phNJvDdy79hzq1VsE1s4
i4+uMMOjhzfhIzU8+tUmhq9wpO26mfVWOJ4TKzwZzDhYb3II5NJn5GgYHv3t+NzKkPmr5GhuHJ3k
iImyi/xc/XhIbcak2RWwM91OCQ+QtKs4hYq9cUTkSLkqtsaRJ10cdtrZDZvxYAuRs+N3rxM7BuS9
GMyJAU0BbIJMUxGRlnWS12b04LYvlr1ZexOW3lz2+bKzP3/5+X/ApvUvf46mb6h9uA7Ohc3QAees
q/35ybfg9Npv/vhZ7X04jdjWJowk8zCShEEaHFR5vUfvbZKA3+ll/FFvyTvNu1WxJJnY8OjnKvUj
zy0eFDMlTXd67vajY/ns8dVYfpyepjQtFgZSlHFEKhEUifBYkiWiDkyAPdk0poiUkDk8USgYS0+T
7DRRF1WgeXhExc8+glUxHqwOooPnNt4v/OflGumqJgnob0mzjTmw1l4dbdRmwkH43LH5Ncw4Pnnm
gxktJ/d1zK4dgbbqoyc/dVPtPbi3dsXRHv1/lp1+U7TN4zzrzKu7L3qIPPfvjdL672GfzoAO+Bu1
f6myJLe8+DPlvuKG+OPJxzIm5rL8wgKyxHSKN8YqbFoGM3O9xd7ySe0nd1Qj50Znx6q5MwtnF89p
ndd+XsfFysX5S4vzW5/NPVpc1/py7oXCUPG51q0dv1J+lQvlbK3Y2l/osORMEXJ6aChvKhBjnavY
YqZEOtFeileSHemO9pMiM5TbIytiNyu3ZG7JLSuviayJ3amsztydu6+8HjyuvKN82v733OHi4fLf
O3zl1vYOfbGQ06XkEMQEJBxiw1huLMA+ioF/9pB1QdMwXKY6dVF3mwzMLdGEO6ELm5sXpMAwrA7B
AwESHvhSNkrSsIFULrUuZUhdVYrKwhTs4cPjLWfYy6nDI/tIWq+SJVk9rD/HiHbT6M4hM1VU5u4T
PuLxukYNmq97bQIRqhNvpcB6N5k6PdwpOCqZiyWmosTxkCEIUZbwUCRDmbyVUiRDWcKfK5O3Uopk
KJO3UopkUFjs8PAYL50Lq4amRmvReJ1J6yyoF6HqKdxWGZWI/xIvdk7yYPTDxWeW55zdGeyY4bMx
botrZls5ede0/ImXdLFmmndvf+IL7NzYwWu7Pxh37+BZdMCdZdxOh5UPCGUbTRt4lqWWJuDMT4jD
1zbU/lr7svYEuniy2yOtAvIK9vo0aIUPbwXB0dfU0wLBboV1893zSgvyP8rrmpSO/Mz8uZ45+SsC
V6SuLt1eWp98Kr9Lfs//TmCP/F76C5l2yOb8NP/04NWpW/3LU//qf8T/dOrXgd8E9yt2afvoV8AM
HMdFiKMF7JQJhPAHkkrQGEqnwv4MKDfUaBpI2Qxx+gzx90zGhIWunEySfI5/G7oWpNE61Q7wjUhU
IeoDMpSxeW253rfKh/kIjONrIdgXWhfaHToY0ocIH3bQKgWz1EEKUULbzEVH14erg/uq+6qUltHX
3rHS+IbWN4CBeEyETq4W/7Ow0wZOfo5p5JSH/LbAttFD+Mkf2qzYSpwfx6ehYiCPY81Y92MjpUxe
CfluydjEHaUOo4VxwDr7mzrx6wffv/WBc2+4XSWzxQ88PVD78qMfbDr9yWtqbyJLbebRsPX6deeu
LXU/8DdNELpfKZ3Vt6jtrHsx/9yKGQmL0esE8IGa7Cqc4p1VqBau4pZwSz3LvCvb75tqOSkwvQcR
k3iyZ8PU99z73V+6m7zkJp18mbTPz1XURNcUD+8wsAC2NrfkwrpMkVSVaasgd3YW6WivdYU+syJW
jAZ7dXocdoJacbk12i8NSEjyTGejal4Oy2rPQOL6xKrE2sTGhCEhTHtwG/RP6qnedwATxfq7pvWK
81jJeYTWXgWpt1bXm+m1GkE+RzpRIaEPx1aT662CEiKlykbT2lhTcKPLsNENHZPHe+t1d9aZHOOG
hkdvWfFY5pT5C57uOWfu/l98cDN5rPUr2x966MXp03L3vn3eee8885y+20d257cSKTAvWXVByxkF
P+0TY8vPX/3mshy59AmpPZ/3s4cWTb1UcnnCJ5546y2vEF2wCvt1pxbN71CTDrOtRApmIZ+/TEqa
yGQokRqZU+DKWMULYQYLD4TdSBiGAy9QFC3hX4FP1QDly/rm+3b59A5fxTfL1+9bjL1po2+Pz+T7
NEoEHcn+HWq8yVHRgu8xRaxvlLS+YcLB8Vdlx07Q6j9oOVIte/GH2gats/oZ8viOTpHW/kSsGl5V
W6Ydw/i+z8T2+BN83zkY2g58GHr8o18N+SkfeenSi5le6CrvPuN+32f+I+hL45fer/z/CJitSG+E
Xqv/Vu8ao5Hh68rdRbmQqyC4XLwgMvV0XDNIw3QCpNM5ICZpS71OkjDb7RazSNdzbjPkQiPXlsPI
FJYTCV5mLDJDIxHz2FBQgnAA7w1ygFmgn7xm2yJ4JJNplrnfPGC+3rzKbDAL+Um6p6qlVYnVVicS
rOOC539VbtDeeNVgpa2RWcVPfLyoOKZhtT63cukYHaMb+csTi5+9dobkabZJddWy5pWbzlx2qaZt
6wv67pGpzx+88PWr0StaSVFTr1NXvHrKQxdpK2P5F6oReRQ4V/U1gSY+B07hZyrzxX+jdotH+COK
ZQPYICIbW68/UQUXRbEu0ebiQkmyhAF+sYyATMnz5d2yXpYTiiwnFTGkAKtWeOIHmiB5I3qgCeva
BGpq0iHRimBQIBdPEsUCL4oCLwZ5twtBKOEbxL7MK5jAuHnW7ebdXFIOCXKQlW062RoKBm02KwLQ
hP/Fipzj+/jn+IO8niclY6sbyVlXv2uHS+fC802jbujeBm8GHNq9KaX1ol1M2qP3Vw9Vta75quYr
Y1kM8n82O5bLOE4LWvZ4CcjvXGhsM9aojdZnbQvrXUdhWDjeKlr/o9rcHjdrt7Nu2M477c1O98Nw
iRHeuI5n8YSHbfWjqu82u2w2l7k+fs3pPps8J+iDtZr+Mby3cfTXOj9TeRePOLfBqMfCLu5hjXLA
hswR5ErUQycBjk78SBrvd6pnDngGvAO+AfE2bol7p2En+wlnnk/Np+cz8536XQhSHOVWOdWt55HX
LQl+UYon3GVU5vLu6Wg61+OeC+dxc9y3uTe4f4N+zf0B35ZWfKSpPgpSJZainKxoZ13BGFmVIoHI
4ggCESrSF9kZ2R0xRFbHI5FYXAzGgc2ofcTsMPvNyGHeYd5j/sI8ih11tcFsNhpEm0Ef8JCPsGK/
CMWSIIoeQQwIPMA3HBiu/V0tuvS6AGvQ6yUXy+IYEscmxgsszwsIIh2UeDc+dyMdgjrJxeFPcEh2
D6MrVYmXAYQ6l6zTm2Jy0EO+AgGnbDfKdhuCr8AUADjCVYGAH3pVbdklQL8ABTVZEtRiuSjckMUn
4UhRUOVYUZBVR9wf749fH18VXxvfFf8ibopvR9dgEujG9NvN4R/j1Cz+xj/KqZ6Sg/tCewlkzmak
yiXM2K4ZMgRcL+M/xwId/tN6mFZdfhbuZCErUwYIDLMMqwy7DHrDy/hqAkzTsvsX15swD2AT/Vyg
9nmoEWVkkNBkfr9AjQx6+AP1Lv3qPnyVpz4H4/jWqMT9N/teHudEle97TlXWylZbKqkknVRVtk56
SXc6abpJ0yloFhWxkQEBpV0AlUUHcBnXJ+0dr+COIiouY79Rx6swiDQtDejgOKg4OIJPXMcZkIvL
eGFEH6M+odP3nKokHRrl3rn/PvrDOafqVKUS6vx+v/P9LV8c4B/QIn0WXKFpRPpRPhgq2UTPA8PD
+Scr4jxxQteZietjCJglETDbRHQTPo9P8BUh2MT1vnIBGjF4cANh8fQPHn5eoEsQDYf0u7pmymFc
tzks/sNxTRw3bI58/5a//+2WG0Oa6WzBO9j2Rf9+898uf1W3pXgiROaP/d7QXs6lKmTq2NvkXyus
6GSkad04i080qavYLBwpt4SzHaq9U+isH91ytv0Coav+7JaL7D8Xfl5/Ucuv6le0PK30s/1yf6a/
Ywe7Q96R2dHxATiY+Sp/qOM78DX8mla86LFpyHYwbEeYVsK0nGlKQzmT6WBZNihneFnOpMM0Swdh
mocwTSCcTcdcMYqLsTE5JsV8Y2IdsUwsG8s1xtIxqZ+4Vg0gnE5ZfJYckSS+ysBMrKMj39KSD4fr
6+MdGJqz+dFGOgah0W43VlXZBaEK4mnGZUwZ80iuLjAajb5x6VgYzfbFL6lC34SvU51I5xZVkVXi
2K0wppW0ufV9U5x0xItMLa7Yx7unOOmAly1Fm0W85PiiNieik/JkVxEYamDxUGWHBRC7jEEaJ5Vo
nFSicVKJVthgnnY6BNTZ+ZIrOLNoybXcPTu4pxd9hu1HI/qYNqJPsjj2gz6snaPP43HD8Y9woT/N
kGvPaRr8WuWcnjzjYgJ5xujGHe3O49iSyqEp2YsuduCO9rp4/floTKNxExoZJ/LpYGUoaSYcXnI8
bKIZTQzPQQ2fIFbDe/RoyDe4v7XwVOGZW7XzI7g0pQneXliuyfinWKLPh2PhmPPx0Wd4TiKmDwyU
a5R/VxijHzsFEzKMn5ezUV3wiQqZn4Nkfh6S+TR8FCfYPu/1hPJK/+DnapYT8y8o0Bq2psWwmJ4f
np82ncueL1xQda5ssMhzlfuVpxTDd/L3YcIkW8NuWQwbSsGrbNE11etdHOViF1mpaUQzvXQ9rO8n
XlFt6fr6xnRVTRqUnNhs0YkVuS3Ek2jLR/eUi+STEa3mKV4Tjscj4apkWFEgrTCAFK3pMNcYq4nE
apJSLOmTWVaraUEgPBybnIbpfmJbH7LqMYZGR6pLjgG2k70HF/81VeLDSYc0ZvARHP/UY19aQlSr
YGhrK3k0FYbuH8eZvROAo+Wn0p4/4sbinAjyZEVkFqPILPYCL+MtFuAuAT/mrP7XsrSyDPzF0EeF
e9L47HPc/QyOhE1TynKTJujC2LLcvEjUl0UlDj+srJx4FwCygGQF7Yxq63UkZC+yXuS+UFhMLbEt
Fkz95BfEFy7SQqDmCpEeVzWRIluIPNlJLiWvcf2Cvo1YTrp0BGCznlPc8PU6piTynfRlpl0EyRiM
QaeDYJHrBC0uVcq61CrUxEDGFTPg7EZY1DH/ImAAPj8Ts4+WIOyEi+BSeBgaoOhDq6qHHpCnik1W
26QBvDVq0Chf5KZWUlGH81InrneX9yfX4DfPE85SLRquIOojedGFg977e4vjJo8zT5CuUJtuCbpk
OTvEbWVkN3SXEq9k4dj7xLMDb+MkK/HuwDnELfjtXk++ZP5O87smXnNsjBVG8THmZRUG4AzD54AB
49UYY3N+A0DahjzOb9BeYbFRtIUFMGKlqQZqMkVSInvxM5UFOPkTM8BcWY5KQdqpb2r2ZZ8ehTXc
98M2/IOMX2os88pf0K5Kw38BbWOtVATmNc6a/t3HSt89/JuNQ/WuRRmG5M7Kup3njKNxvckPmk+K
gNQK5H2eQ3aDatAMZ6tnP2t+MvRsPRkzR0M5w1XcNb5f+Lv5f/Xdx6/yrTH38E/61qX6zC86n+c3
+jYHdzqPNLopKMIkJB9m7vcRN9TfXv9I/bPONfWvNr7b+GmjpVrpJ9apvmhKjkYVWalmqzhPolkG
zQlINtmttc39cJ96LlxeDagmmbRZZRxOXVxL1iZydns1/ygtV5nxBQeQJFlFO45Lhik5L3fKF8iP
y8/J2+S9skX2tXjuaZBN+Poi0+Ombaa9JoNJHJHcOmR0YM2kgc+KhT/6qyvR1FNdh7CHqrGCy9GU
VqZ1mOkoWg0srNuAGbnmmcHDIIuaOHikl7XUW4qllAhSFcsveXTrVhBEt3CDL+MrS7qQyGZLbK60
4CkSuoqerB52LUkOGdOuldhbMzbtfvDZfe+PXN7Z3T37eclKeyjnnEcnP75hMZbhV3O3nL7p0rOu
ueLyrXOue3j1outfcNHLx13SSnlZhnL5ko/NGdijxcF+zdCduSlnzpt+AY7j16G1n46kLgCqYeR5
7G6sU210SnM1FEdAwOecmHKLouBWAkEzCW1SzN5l64dz+mKyVZIR4pmjJskAslhmq61KdqE3T5h8
yfBUYJfcPCZFufhF/F4eqXLi/LsrlwMvwoFSigTpEIbSaAdAAOdAsc71JHYcvWF7cTHUqQussMHW
EJlQfU713OpnlKcim+Bm24vBF+LbjTstewwfWw4Yv7QwgqERpo2jbB2w03Z68Bw4zdhl7rLNhZcY
L7NdTdxA3RC8LnRbcEvoJaUvKiB8cniDja7uH/zy+aBWJqvVdc2EDFoj4OYBjp6FhwU0YQXbGiYf
er8fmgrf9X288tWKqvJffXTffR/hZvh84J3XCv94ZXvh8GtP4R3B0K4VhOx4/C9/eRy1YgXdRKSZ
SXC4T6ZsLpyk+1atRQevuz+OfhjfF9on/0f0y7g54o4LY6VJ0UnxaVJX9Nz4AtcCcX70NtEu4BTd
lRw/kzvHvTB6Sfxbn9HkE2m3L0En2KjvdvoR+gHvKt9T7qfQveEYy7hE3q8xZcSAR49nguWMnDDb
eg2mwK89ctjmzFlm9oTgitDLISLkq+XlGF7knhjEhVsrYmRMrNlesc5I27TaZrRFYBbbIaxqhw4U
K5qHyDJ66BLHeHDxHCY9FoOXpsrgpVDJgQkrIJsBTWnyVa18TuO/mJ67f+sr7z07e+cUN814Ln5i
x87CUWjb+XvSEcBa8ruQz+Of0P3lg0/sOW0y72FqxiyE5Os7oR3rwk3oba9BuhBE7/uTF05PzksS
GC2t08vWUhpgUixBL56i/SmP3+/1KEFKUKqtXRRSg95qGb1vpA6SIvNBYLfxZuTpQk/IKnVD6IIQ
+mqjcjdy5fvhnb01ye4S229J8f3gkH2bRitC+8kB9O8I1oOfDpE1NkxcLxSVoNdpYS3YxAzpxWaQ
RB6fxMdxGDGGEGfYEhHLNqoMdMJZUzmwkvaURJmrEGUDoZuY+z654u3rrnv7yo8f0M4Xf7DqgQ8+
eGDVB4bPj16ObcvTO67bd821e6/fAT/SJbnn4497sCQTWiV+CkmyCCSwW51PCavdRJoYQ0wh5hCv
Ea9xfxQ/Yj8SP/b/u/fT0A+CQwwkAxmiJXiG/8zQLP+5oUX+y0I3+e/0rw6sDm4yuq4WtgS2k9vZ
NwJvBE2WVxmfJAEImSrZYzbIjM0+1ZfrAXAx0qB++KnqUaQczPXwcBG/jd+FTJGBF+Xk2goRnXRI
I1oe0irvD5VIdccZmQ0Cb0ImYaOfDwWJ/sGDZVOPgCOUBWEYOUuXTGDWS+YNdcf+Tfj0mfPfGs05
aS/d8I+bPyjsha4db0FquvjuypV7fPCxJ15vb3KJDEOnp0P/G5uQ5fi/N9+xbu1dGA++j3yHc5Fk
ZsBONaraJxu7jb+039zYY99g31jzSs2eGspjcVntO2hasWbqQSNE4N/wAgBKPQIQ/VBVfRBJbqRa
AdGuhFwFACuJ9XVek9VCKUgWVaoZ1ELJt0sTzVWqI+VW3Yvdu90Gt5i9ejN8s1g9O0kj7LTRn2mo
vQ1DvIED2m55POewa1gFrTNZ40cLWhsCNf5ECOJQ5M03/yRLBB3oRPRSkkITRHepFDkFNTs6sAj3
O1/A/Qtr775mWZPby1u4B+f9/Bp4m2ZoHQMTSlib2IzlcemCRwWLwLIe0nPZuKUa7EKS+b8KNxlu
QpIZB00wqDaO4xfzxMfyO9GD8oHoUflIxLQwcXndnNScpusdNyaWNN2Z6G56LHFv05pET9OWoJOw
YGswWzMQVqPRYlUIEKxp9Eq0R0Jr6QyubJQlqkYGK2NmS44wQROsrpKgRFG0tce63kq6rDiM/px1
l9Vo9WXr5e7winBPeH3YsC28K7wvfDhsCIuZ5EXHCatmLXAVIloMDADzB7BJzZd4oK3DjESFFG8F
/sEjwDd4ZEPSgjzs7zcELQBn1GstDXhI2JvwZJ2QGkrkFQUdIxeYLVeL8WYnES4ulweLfhZbESKb
YZvSlaaDvFnf+yLexbMmacScr8+4Ji4se/e3R4/+9t1lO++6649/vOuuncSOhzWLsXnqmNrzqzXG
x5mnJ0cf2wxhXx8EhYn3v/mnlff/6U9IF6YhXbgc6UILvEKtW+07KhEG6IZzTVebVsD7iR74JLEe
9hLUU6bfmDca+8yvmT8w7/WZfRbGo9ltFx/iCX6Wl+c9XoVJpDTAUzurobY21aAkaEq39w7omKWl
SBRax6+26Kwifm1J4/NwNtWYzaYblRaIKY+GRHU1Wu4WYDDTlMUqiXu9EO0TT6i2kUCWGrc17Gog
Gvrhf/S2TriozPHWXeC2gZLJ1wLrTGvr/6S86/hLpfICOPhyrz+SgbiOl/EV63iRQtI+v9FsivqN
Ygj6zAFdJZFOVmR4NwPT4JE+yR7idfQzU08pMhohaAijllVXx7Hmn0r1wimTV543+7ZZ54dEMVT4
Sguq/PLqWaNTl1VytjTNRrjo6PQJ4+7pHPiurL/kedfXSdcMHCxN6FAJae9LSBoEIwNIhGCXqklF
TIuqOEWcI14l3iKaOQc9g0c41mS3zjAaFbsQEFe5EY4lXyX64f0vBEwOOwXgVoiTWgRyQ5wGg1Fy
d/KQF6vOXjrk4dED2iq15b89NMzRA5WsN3c4y53ApCi+AGLFjUvhGfj/PeDVnLEz/oHrJo3Mhx8W
zj72TYWlQlgG26WNhZvIFu1/VgUeV2togIwzQZPnuWYGELoLXOXqBt2wm+gmV7mcZ1nusTxuWRPY
EjAGLH6cmA8gbTbaLP3wty8YDIpN/w+rTpvJN1WUWM4prAziZOkFKkMQJBkM2R1SVVWnARrE4BbY
B98G3qFEnkYhKiVLBw7kvx0Y4lsiuNaCNkD8P5eHWJZDJFhjujlL7L3x5oIDB0eICTNmjJpa+If2
AqwLb8H/+4FjmubPWbiiLqQp/p2XIi3fhtZ1JdLyLNG/GSSQGAuOfAIzWnm7NqqdrC1/Kfcbjtie
gUk+Ga1PJDPV2dZIPjoqkc8s4BeEbZdwMMw1c0QN35n4MPph5mD0YOZo9GjGMjI6MrMgsiC7hl8T
NkWy4TDQzbitbMMDWOk3ghAMhfCX2uk8HlUaIe/QrHAopISVQBjUNWnWoqFhfKahoSmj1GWyjE17
kDNFOZ02SmFwdTTyoPTSaO9qrTZa8fNcbQzPT0gkZkUTiVhUqY1GopGIlM3w2WwmzHMsJ4EwD0AY
cNkIbwxDJRcIuHN+UyxX25Srq6utJWw5lgGWHCQoHrvQ1kVhGH44GpmW3QJ7QBTNOBZnujOElGnI
XJghM9gaVY3g0N6Pdp/F1m4rQVslawM6wPuQySo2b4WPgW49+TFEbaCxjVpy6MihYrSulN3QKEfF
+lVP6zJDvR415gb39AbbcHHhnt7ACH0U0/roqdPGDUOkBohZDcucxTrok2cPfzrmN/xeZMpSJ6U3
cIP7en2RDK9VTDIZDptHNOIfNVOLSQ0h6DBC0LwlumXwG+Ttf1vJlER3oLsmF+/6vjcqZqSWYiAR
OzA15XLaIVxTjiXK5VjiCaHsFyucxVfhxTWarjiw4bio0A8fv0griTmMZ3OFB+EvCrdXuI4/wFps
PvBx4e+FmeVQ45VIo7YijeKRRnlBl5qZ7b7S/Us3Ah/2GRgzIpQ4AyNE1utexTCKFyBgCKDE0HQn
vY0maVGstIbYEJ7ECv6kBbz3ePv3DbZ/Jdehwqij3+pGv3UbwmTjiaTa5hrhanG2uka62lyjXKqr
wzXOysbszfaN/g21hjhshsS0wGzz7MBV5qsCxmZzOjDOPC4wzWxssIwYpenn3pFw5Pj2kSNHtSsj
3C48FZRYOJndze5jD7MGwNKsypLseCfLupyKOxrSgAJQaIVQxgcVJRRUos0N+mQT3UQ0jU81NTWk
lObxKp68eG8H7Bif7+hQ80pdyhSM1ddVVwVM0JwcoebAeFNSJn2y1UqaRzQ3R6NuyuGUPIIayjYI
3QIhHItVBaV4DJ/HumNE7Fg7SEn5dhzIAu3b2ne1k+3ihORvvRUxE3RQ01YeyqTPIgmwFD1nW8H/
gL3ZdSJNqKQ1JmyFNTAxHFQUUYVUnfCKlN1gtEUThngIGk0i5QnBamMyBL12H0YZGk0OIw2ENbq6
ENzwD5GUqcG/AwNq5sGP0Hd9hMDLOyXsCZdoxsWMf4Gv3dSvj/iXbEAj0EPBnFuLqGle7BBACWvI
ZAiYhIcjleFK+sXCy0bPlluuHHle84QJWq3IWU31l4werx12NtbVjurQpvdr1e/aITl72pXjxo8f
lzvz3IE+LM3Eg+rUcRcPvKMd39sxvSoxVz8ZckaQlF+GpHw6kvIWuEwd8a7pXQux3bTdQjxh2WDa
YCGXmLvNxBzzXMtcP/mI/ykTcUOoF24kyEBoQYgA0EAQQQurxyJc7pCbcI/Xyn4Udjim1bckJ3BC
5/jirqRjWhpE6SgxDNg6suN1YJvOtZjgFrgPSHCOylXJBjPCuCzLUFZK8u0VoYg3FFqDtysaehC8
FTG2HYJMRWSrC+fAEbRZ/PPM4n8W1/L+gNFitpgshClgRALnt1Tp2DapYVt/uXqRRx/96/N+Xhev
JTiyh6vuobu56HieIB3HS9EJ8Hb6jLtnXtjZcp4mD59oZIl/ufxn1y+pRLdFWVk6c2wieMfpA18N
oduZN3T868DXwwQEYcB7B/ca2pCE2IAHnqa2sIJB4D0C+QZ8w/Yu8WfjX8zv2kwLzfMZ4mLiYsN8
y3xqgeMy5mLuEo/FLZMu2UrarGa7DLC+uMS8Njo92qg63Nn1ANKgAVyIIGY/sUz1srJJRbeZVHTP
ItM20y7TPtNhk9HUD/f3epEJKvktaHM7NNC1BLsMOHCL7Y7mZNrKTqaAECg/eGQjzTt5z5bB/WjH
3d/rCDLBIX+yS0vE4dy0TcBUFx53DA5vcq5g3sajzkKhzow7NH9QrUKIz8zbWHQRdQLPeNp53HE8
ThP3D25XWXRAUQisWXCnpYlgiX5Q/psJcey2FJ+pjHK1FQ69sr3wd8hufwVy0z7p6fkEN/jcy4XD
kNn2MmQKh3//q7/ufezRfXtx5Lxwk6a9UdAI69R8I+VqjaOWrTsbTiO6HHMhWhPTQsdV8IbkFfW2
P5hepj40f2j9KP5h42emTymLSNaSN5jvJFeTa0mTENBUVkxViWKgShH0XcrG7jhuSxqtpIq7EXQk
Uq6cO5BDkupMyTYqIcOVBjMI5aKmmOyyQIuvqRY4paCrSq81MFSJ6crguwbtSqH3Q21aAOHH4gcn
LwmuDI9V2xuw31GnFQQ7JIhXvXHwL8/Hw+U111Ych3bdRSdSC6L/pEodF0ufuPbqG//PlYWBlz65
U0+jLaoIqT/2zkOr9+xZ/eAecvbq82ZdteuKvsLgpoJJr09FuCKnAaL59+7aveLe3btwNBKt3bNo
7cIgBc/cDGoGv93gak1g4Wtxta4DT/vXRckp4ALfXPBz3wL5SnCj7xf1vwR3+W6tXx17tPbB+mdi
a2t/U888GYaPJNZIaxKk7j84K8NAum22uXcUzbJuhqdgM1xyDoAvXufNsRjIO+vkAGXFEaK4DFYq
5ggUraLUTUEXtY86TJGUrzEpd4dWhHpC60OGXaF9ocMhMiQ2lILIlZEhjaqITC9aVFzunW/7sbAQ
OFlYuXJhfTzYMngQpBAQjvK1SBE3VPM1/WhlE8NWVo/a/ySfUA+KRoaFh9a+qkWStXhyYbEW0rtj
/4uFAUj+bt8dex56aA9uxBur8QoefbW0ovCHTRD2vTBYmHjvrl333rt7N86V4BgpeQ2y9m6Vv9EJ
a62d1AL2OvY29gHTY5w5oIdxQjuK3pvfvYVYh5wdVbUWnbKaKL6js/qsSHV1NKLU2Jy83YbWxGh2
QA7wTpqKRHOgxkTlabQZIl8Mu2R+ymU+bCbMvjrASxFXeHJYD+AdDpvCYu3A3UMbok4e1rnDOAvS
pjnWeqILI7bW/24p/kk3QbRyTHHl+jjeKbCBEoIqal1lMbj5pwKwBPHkE+Mm3ixylJMLZ8QRj2yD
V2nQ/XLsxe/U6H/k7D33T7vYx4lmLuybsaaQ0RaHZTzEi0V8s2twL1lAWjYWfq0u5/OB0QR7JpgJ
5o9dK60d8b9b3uTeGPNX7j3hvfY/j/kP7kDmizHHuCOZ78ewNs4kGNutY0KcW3C3+8fcoazKbHXZ
pnPntsxvWZC7vuWm3G0tt+We4jfw1N25vhBxtqUmEY41qqPaMj6vy2l221tBJt0QNtQ3u5x2kgIk
I+ZGjZIZuYPqh9mNpITLYuADaiDWLMsgZ57WKncGcWE+GfSNb5waziXcsop3SQHth+rMRQmYEMd1
mElTjJJt5xdVTiu6gnpcHNZgVk+5Th+vcddQkX5rRZm+nvdqxdkuBFhaRoxhpUCUi3ra3SGQ87eG
4AgJdewYdCrkvSHg8baPGlnVhrCML9fWEmoOAX40o0FpDKz0rlgepWGc0upvzPEZKvDi4OfAg7R3
LFLbdn4E0t5eRWgLDMV1tbIXvVCrBe2xVuR25HjUteAd10u70RnqxuItdiyPNtWxvM2VD+DnoDeD
b9qEgQWPu4otFu3ux1MP4sVMNqYelOP6vKmCfICv6fSDeCwSK5IPbtS9WZzXa5my7K6zcuMbbn1u
7EUXvPX660stbodGPxA94dWLnuw5e0rh9eVn7lm5jqypQpK6IugTxLZ4S2tNtq064OK84RtPW/j0
xQrv9AV/i8TXXR9qyF8/9qxUSsrMa7tsKfY670NoK4dZyeANNXLUDx1+n594kuqjXqHeoQ5Qxl84
b3Wucv7G+ZrtPZvJY4FmbEEM8ArVbTEYzBYF0rzVzbhohuWNoj3RD59QmWAuEjHnIAQmuyza+OWG
fviMytfWWqxSTH4NBOiAFFgc2BYwIgTwaW8ddvSQEB3Q0ixHtHSUVjQ/cEhPlGplUcdvwji/4vNT
NpvPGgKU3x4Cen5FS1d3wZKGM/zwFFUse3y+RXAjuL9D21xbrl4y7bURvIP2OqTvlqxcpxXKP4IX
g5yNlXvg7dNnN0kOkXE55Em3X02k8OT3+Cb8Hs9D73EmORvEkSW2U4Y+gagWoM/ismoW2J6y2O1W
i+LSE6k2/1nFRGpcxud1IAIj46VIRJaUOBRcvCTnQJzyeHOhYNBlseZol4mXSZskAeARsA9iTdCM
ZNllhmYcYK8eHmBvw2SO/KFSlVmxLOm/ux2WzK1KQRUbW+m4MDrLGUzGKGdgQoA18fqb19WQK6rh
S8CN1E9AYIgd3F/MGGoFIPGK16+tzYih01L9x61rd9yg/kyPBM07609rtGX4SnMjbni0Y8bVRFBb
jLumLHhRP9TjyHgNcmg3vA+tQRheoDaugWvYtRwpUZJNsksOySm5JOS55WALO5K7hLiUmc/PDz+H
bnqWY9UQpGi8EG4HcNCOlIN0nMU4HDSjUAyrb6LofxuCFWFQK6mBH5NpFmEykYRiJaAe9sx79bjn
WeWwJ0NAKLEMj/xIPgyAxPE8x/EcCwFVDHD66RxF5iirKZzj++EC1cYRuRSTZ55jSGYLXAA4aFUd
Kgsb2EVsD7ubNbAvweeQzEShXKzbRkDoM42xcAhUsE7ybSclKwwvvf6ROusfqbvGkUCdrXBcUK9p
+Ayx/u7C0+doYa8c7u+AmSisv1ObaMMZkWmkA6+ftpwTdP+vFAtrGRw03I9WspqsVZ+qFuKeW8ln
hac8/cRmYaPHAgiaWCrcIzwn/E7YKxQESw+xnthFkBaDxe01eN3VRMJQ7Y57Wgwt7tMMp7mnG6bz
M9wzxBnVl8CFhnnuSz2XipdW32C41v2Q8IDnN8Qaw7+5ezx9xFZDv3u9Z5O4qfoN4XXPn4U9nr8J
Bzw1NsEv1BA1Qo1nmbiseq2wVXjN+Br/sfAF/MLzPXFU+N7D6DVETrpcRKTzFdaptYsjEESkiBoh
D+OjnsjuCLk40h0hMIGBiERWa+wFpcheWKcmLtDIRSTmMHRaya+s8DmNyIAmoNW6WqtrVIpEBiSV
VVUpjcWgSKJ3lcZiGDxDTZdYDFKZxSBVsBikChaDVGQxbIP7kLt9FZKmfTgUCfepYQOYCiE51UDF
c7IvJ3E5hylnlyXJ4bCbFnmh9w8ixGn0GFgpqg1ZUa2uyYhqNI66qiDqRB/qXExGzKkXVsPqrfBp
jb5wh+oRphFqY2uGwPcR+D5CpZkM0Q+fVh1G6UI3dP+BN6zkc0Yc6mrI4qG3pTWjndbop+hrtBE9
QRvR57URPQyPKit4MkbVnV1qvMdIYLYDYXwJ7geJCo35tqurvHcfwoyGLkx4QH8DGt2hq0R3qDny
Gb4IvMezgPJH2ugD+OCfJjycEOTv6lqy5MS5EyeLtaOliENftUW0GOghQAOvkM0kGSeHVepWEhpK
c+TyeZv7561LlIt2F67qndt/zwIcnf4Mg95qSAQGDsAKDb2E4AcOEg9XaunFyN4uQFraQdynrgox
IZZgW5jpDOHHMZaQciG8nF0kLwpf2PEH+Af6LfYt+c3wm+lXMq90uCzACx5SyB8jL2iEBUknLGhE
BkknMhA5mHPlkKHkcmxOzkk5X2MunYvkwrnkmFxHLpvL5HJqiawQr6+P52caM/2wfqPU8XCexski
PyYtyLJgtxuBADFx4WGXcRESDd+4NLreG344zmr3yQ/HZ7qqUsUwgrFKHEtRPippypk+2wLNOlG1
AggfwNQFkT6ev9CFiQqYxKCRFTCd5pCXPlBiLxRHH/AO4y5onXFZfYmO8MdhdIS1RTrCt71sGI/7
cWwLjX/d4G9rP4HQoIbpZkyBqC1TICj0MTqIeQdBzINQyp8qkxj0rb+P8Tpcmab+wS82oFHf/PUc
UJHfsF+1srY8E7SxeXTXfvUMdMBQgqedQVtme8foIJuHuOsYEWDyEHcdI/w0OkJdBy5whriTqSqp
PeNCXZoX/e00xt1pDLTRyBbHjv7B7b00jyPf21UHOgi3oU7GHaw54Q+UwTjU+XInI0zoFWA/VeRu
ChM98OYY70Je+jdYKe4obC5s1TawwldBn4uLwZsLz0Y4dP1TvJ/NhX5YNRer0Kf4agS+WrjHLDiK
6ajWwut6rNMhmJFjeppFu4JjNF9BRtcqu2BBWrWqcJPhIaRVafgiAhPAy3qVGofsycIs0+lQPUe5
/6fYrNxE7gxlHpzHXMtdqyznliubmZe4LcpryvuKE6kmm2aZNKdjmqDDkSqDGb8S7A7C4GolGFQU
vxLGjIl1G+sbNN/QU6RMKDVpzqoXARqNq/USQCsEPl7bcjwNHuhJcR4Pzyk+Lo15E+vUy+PxlEac
UJJhhUunpbDCh8MKg9QXQB6wHIBpdIFlILAEjawVQx+/n8/5fEijCQx9IrlkY66mJukEwclBYnFw
X/Aw9kwzkzFdjTZKxsXGfcbDRpNRbEpu0ay4FgE60LWE/gyZv1KQoQL8FCstl1nqtUzrMt0oe/8J
xPNTl0un9PC7zRa6zdKmEzqLwnQS8RqWB5WJywrXi0Gfwy1ozIklcDqcsqTIx6H5+oGDv9RkTyOa
QzOyzazDbdWMcyfxvC5CSLiGIkbYRh8CgPw7kiYP+JtKOXGIGFqcFPHS4LfAMfg9oIAB+yPmFGk2
G0iFEjSRGculXBxHuxTBCQmWkBxO3uFwOuyEEwoOwg6dLgl4EOqVbHYKdhlyLipPLcLxOlHoWmSH
dtF7dUWIblKx3vlAmSBRrILFEQFk6qBmUgg9aU7gbRyZK21EFguNH2xA9qpkorwnZVZg9x7WQDeU
i96dWc7CElMiS743cAfRotVbDADiioFvdedu4sCoq/Ar3TGReOUKfPA6gERbYYC41/A5cAB5M3pH
TarDBmAGRMwW0VnkQbRNGsDOKvpaskjF0L6TuBcWkxpew7ofluEHGq9D5gMU/xaf2KB3qJHBYrsC
7a7I3zO8pTfj7ah9CYAJXTMtAMAsAGCdAQA1GwC7AQDHBgCcBwGgzwCA/RcAODS60TUPGj279eZ9
QG/ihXrzo2dWoWeH/giAjO5TPgIg0g1ADD0v/h4ASTRXg55V+wUADSbU0FzTowBk0edGfAZA6/kA
5D4GoD0AQH4jAOpaAMacA8DYNAAT0H1nrADgzBcBOKsetfV660we386OATBlOwBT0Wem3Q3AOW8C
MAMh1pkfAHAe+o5ZLwPQ9TsALqJRQ8+a+2sALkH3z0O/fwH63oWHAbgc/cbF6PNLrgfgigIAV+0A
4NqfA3ADuu8mFoClZxRbz6l2qp1qp9qpdqqdaqfaqXaqnWqn2ql2qp1qp9qpdqr9/9kAASDAfzwg
8RH0oWYC/+UfCYwAWABlswMnLgPieLfg8Yo+f6AKhIAMwpFoLF6dSNbU1tWnGhrTTZls83+SYz2v
TQRR+OVH29RD9VIQvYyVKjY0aaFgU2ttSWJN6iZtsvVXLWVNJsnS7W6Y3bRUBP8F/wMPihAPgkj/
CO9ePYlePIvowfjNZBoQ1BZFUNxl533vm/fevH07eQM5P52auTB7cY7mESCTvbx4JZdfumoUissr
pbK5eu36jZu31m6v0wb9BVdU/Ut7nI7hVWPEaIRG6RzN0CzN0Rqt01261+nAojtzluJqZh4zlpzp
vPnerWv9o5IedA3Rs57dl57PAD2Bth/5fuixxhEaDp/WOAo8rXE/sKHxAJXDd+SXjw7KmOE9jUM0
FnmhcZiGIq81joB/r3GUxqLDGvcDX9IY+URtMmkXFeRUQz0qkIzaeExqKGyQRy6eQFsxSkMTwHK0
wNvKgoFx4J8Ayije+s1IyV5mjMqYcajVs/HB5SC7601SCvcEjWs0pdgFeDiQJfjUkUOgvEqI5+MR
tI2xqnJoQbMld2pE5SuzqULfghS0Cc5DdX79TRhYjhxsrByoteXKDLq0qShG1mtflxm5YLpZ+ZQw
d5u8ZlU4azOzwZnhuV4AiqU90fSEFdiey5pOJcEyVmAdYJSUwVjZc1qS8VnOhd9kKjUxjmEqwRYc
h5XseiPwWYn7XGzzajGfXTTS8bTXEjYXBb6zXDbMw5Nae8pMYVX5liU2mVf7aY5M8LrtB1zwKrNd
VuEisKT0Wm6AUH7iP9+0RcpTlhaRXRrt7JstTAWMO7SM1Q3kUlIbr4WYcisf3u9PWP4TPzXZa9Fx
+86ERvCxBA7PME6WJK2iTT888hyds3sOh9/VPi29PblxdPZDbDCmWvSj0RVLyr2X7Y+dV58f9J2I
xaHKHq16+FcBBgCm7F6EDQplbmRzdHJlYW0NZW5kb2JqDTEgMCBvYmoNPDwvQ29udGVudHMgMiAw
IFIvQ3JvcEJveFswIDAgNTk1LjIyIDg0Ml0vTWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJdL1BhcmVu
dCA1NiAwIFIvUmVzb3VyY2VzPDwvRXh0R1N0YXRlPDwvR1MwIDY1IDAgUj4+L0ZvbnQ8PC9UVDAg
NjQgMCBSPj4vUHJvY1NldFsvUERGL1RleHRdPj4vUm90YXRlIDAvVHlwZS9QYWdlPj4NZW5kb2Jq
DTIgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCAxMTA4Pj5zdHJlYW0NCkiJnJdZ
b6NIEMffLc13qLfJrGIC+Jx9I8eMZpWMooTRrrTZhzYUds8AzXY3Ob79VjW+sONrjWRhTP/q+lfR
XMadi6+PPkxN5yKOfQggzjqB7/kh+HQ0Z4ORN4TRMPD6Y78HcdE5g0/xz06X/vQDupDQnd3AC3oh
xNeds2+lRV2i7V5rkVmYfx7ie7hTpbRKy3IKkU5m0mJia41mcQ98V89YTFBD6AfB0wdnxmcD8W9z
o42lcOgs7XWDcPFMGkhVUhdYWqBzU09+kk2wCi6v7mE0BlGmYGcI327iLxDr2tiPBm5xKnIHd3YB
7rV6lkaq0sAD5sJyBMRwi67nfLO+4OlsZm31+8WFZSSiJ9FmntLTi1wmWBrsyjJTT59AloBZxj6p
0jmSCougsnVYVU9oFVmlW+gfux6VR87lKAyCxmeJL8ygH2nLqXbSABKhMavz/O0chOEVb5CiSbSc
ILypWoOW0xmt5eRQeayWiXXBv0g74ysVObwsTzvnlJZNB69UivRVVKp0LuGr1SKxmEKmVdG+HQrK
Fzx9WAtflkleE+FRFlUuM0nrLh+v4bZJJFjCcRiLCFLO6SM6j6HvbSaTc+zqPK/yWmk5XMoMVHwp
JRCHq2oLL0JrUdo3NrOGallk7vseeisZb6u3nb4NPbOdWExyF8OVor5aVXS9KTaWkGsBpZ36UKu0
bhLhnXxAr1XhlXpC+u8B/62lxkZipbKNOI9n93eop+c1k6JYTQqxNimOsQDDOXueCoYGDksdf4cs
ZrjMVfKLgqiUtk3ZjVGJFKzJSmhRII0ws0KO28g+Z9eYGpcdwSB2tmj4E8evDV9ydv96YNWTGha1
CPw2ckDIrzWpLpclQqb0cdD1wINwR8GYzhn44ZbyFymqgZqGag4ldoO9KhizQ9fjWi8m48I5lxvu
i1KVXa4qzTaxbWnJXhZs4DkdIImXeXc03+pGbMBjUxeN3ChDaOV7ygt620gu2s1rRdV205vcWvjZ
JLakqptKJDtEtokcEi6i4f0qqOddg4p2oQ4rNejvKNiI2VW1HPo0Ux++XMEgCEZ0XqlcTSWa/ezB
zoKNnBjm/InMJQ02snB39ePI7l2yl9kdOQ1sIWOamoZEofR+Zwm50bRj7rDoe8RTz1BXaNE8gI70
0CFHbeRnQtJjodbs3P/DBuMdBaN9EkTJr1K95JhOG6We4Kpjf95RsICq9W2h+mdSLWaosUwOCGD9
CDeGDRUKqQ1eIeLOnYlyinCrpqe4HG41beRklfKer8u7na54tonS2KVZzjO86/v7DbyHDA8ggyOR
2yMxcjNmHzs8ib3eYZEbNvvYvQPsrfkVeYMDyP7pyOEB5OB05OgAcngAuWskMnt8gD06ib0qWFTT
Nk+bjxClKW1uzQmdtWQP3n1b2XNyzFbwpOW73oP+rM8BaZeTe7Dxoaeh5LevP2racgTn/NIVbt4D
8Pe9oPEQ/jMP8Cbu/CfAAOFPirENCmVuZHN0cmVhbQ1lbmRvYmoNMyAwIG9iag08PC9Db250ZW50
cyA0IDAgUi9Dcm9wQm94WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJveFswIDAgNTk1LjIyIDg0Ml0v
UGFyZW50IDU2IDAgUi9SZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9HUzAgNjUgMCBSPj4vRm9udDw8
L1RUMCA2NCAwIFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3RhdGUgMC9UeXBlL1BhZ2U+Pg1l
bmRvYmoNNCAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoIDExMDQ+PnN0cmVhbQ0K
SInEVsFy2zYQvWvG/7BHuyPLol07yTFN3LSdacaxONPORD5A4FJCQgIMAEp2v75vQUqmZKXTS6fy
wSQBvH379u2SP+Wjiw+zKS3D6CLPp5RRXo6y6WR6SVP8dVfXryY39Oomm/z4enpFeT06pbP8y+gc
i9MMDzR2nmeT7OqS8vej019tZG85nr/3qozU/+7zO/rdWROdN3ZJb71emcg6tp7Ddg99dGuuF+zp
cppl85MUZioB8h/6oF2ky5sU6R9pZBMiUPGuaHU0zh4BGxxNz4jeBqqdZ2oD+0DKFhTaRdDeLOTe
c/VEQPKsKoqmZlJNUxmtEj6OrI3mMO6J95Ct1eyjMjYaZGosxRVTw750vlZYS1HUWplKLUxlIiKU
sifwDvFI5kQKNAtv1qKmQFrmgqID4aZxPuJ+QyECXPmCao4rVwRCUFoqbE9FeIbtNQPskBlOeaNx
yrs6FXCQboC8eWLpVWMKCMM1++UWtk9+SyCMwUuvSAXgvLujP+/p8/3P765usuwhCeCEU7fGj5Ft
EEWRzQBrxraQPSzpBZqfzu7nZ2PcazbrvYV7LHT419fTh6TUgg+YFbzmyjXQTDRJNWl945AP5Neu
quBNOSLkfEKWu6E6x4qypxj4Ng51l1ipjHGlImllwUYclsqlnYetVOTE4VhFeswxNd6tTcGCKyfl
X+8QWptgevcI4ZpVQGOl60HOddd/9KlVW6PdPiIlw5LP/PSTu52fTf5Vo/ziNiyiJ+G8q0zJvmsD
gMIqF6mUoWFtSqOfdRGtvbIhWXR+ctTY0g+DvvrWs62fp8cKPlowW4Ic6KvSQEs8UtS4KA9UtRse
B+72blFxnXjsWBoZWLCC7xtwTJuVEbPGyHUTReut9GVbVT3tXgiNkeXVMtlGYRF9Bg81yivkLEMj
2UlmQPKzetZkADJIF201M1KOwpTQFNnsdR1V6glPCxlD0pG1eoIaa95rOofJNFDL87fWeLSnjWkA
aVdjdSy181zKuOvGzbZIx4oSVq6tCjFuAJGQFF/AbD0YLB7M0g68s6/8cRNhfpBbfJFOW3M39kyg
wulWuBKuoVjBpbFi5e1gQAFT6i+NLcmWIvzG+a/DskH1Wopj2/R2QSTP521QArVthgEc1md9Y0lT
zOZnF2iNnT6dO0qlxS3SuahHqyGIqZsqySy1mp/Yo0pqF2L3allx1aCAj6Y2f3HnwvOBDSfUzcMP
LVKoRAMZaddvbl4/7HXOs7ulLYIwKtKoER+jwh1KJybql1QssGVjIjye3hNdZskR++5uYBD24rea
9UpZE2pBQuVlqyoKs+35DujlcB+ALSqnv6bXBiBqrtENIaDU/WBU9mlo1dSjQ3od//2X626WiPq2
C78xqDTG6wGlPvqBQYdfEi8tuxuALy/+3+P/HY3vfU790Y6JUaRqQgc/vEKMfMT91sKi2Vi+3S4P
9xB9vpMhefXQ1+82H/0twADjSB4+DQplbmRzdHJlYW0NZW5kb2JqDTUgMCBvYmoNPDwvQ29udGVu
dHMgNiAwIFIvQ3JvcEJveFswIDAgNTk1LjIyIDg0Ml0vTWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJd
L1BhcmVudCA1NiAwIFIvUmVzb3VyY2VzPDwvRXh0R1N0YXRlPDwvR1MwIDY1IDAgUj4+L0ZvbnQ8
PC9UVDAgNjQgMCBSPj4vUHJvY1NldFsvUERGL1RleHRdPj4vUm90YXRlIDAvVHlwZS9QYWdlPj4N
ZW5kb2JqDTYgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCA5MzE+PnN0cmVhbQ0K
SImkVsFy2zYQvWsm/7BHpyMzlJI6nd6S2tNxZ9wmDWd6iHOAyKWJmAQYAJSjv89bkDIpS9bELizZ
FgS+fbvv7ZLvs9mrPz+ldONnr7IspQVl5WyRJumSUvz0//36Njmjt2eL5M1v6WvKmtkJvcy+zk7x
ZbrARo6Tp4tk8XpJ2fns5NIEdobD6blTZaBh/Zt9oCtrdLBOmxt65/JKB85D59hvz9Dfds3Nih0t
08Xi+kUMk0qA7JchaB9peRYjHaWxTBCUv3XaccMmeDI2qKCtOYA6wYh7RFmlPTXcWMJfbUrrGly8
ZlKmIOXJd3lFuTVBaSPQeG1PCOCA4ibxkzHuzycBjEtDqii0MJ9TqJhKW9f2ToqIOjeelGMquNSG
i99/LjenjG+tC1TzmmukGZzO/fFrdznH9Y48B7LlPcBdpaUqlXIqBzftORIOlWP8vo866jhmiaWb
VmnXawXQVuW3gK+t9/Pth4JrtZlHDaY705JjrZXTUelEdGSw2BL0le3qglZMnVermmm1ARjebVvr
fHTHiNWn1HmYVBx8n0Tyv7wpxZuEfIIMI7Or4bhDBUJ0g6WP9qL/zFIgpwDJzu+VQRyzm2bDyqMT
Ye0QJVN77KTmpc07aGPoW6dqHTYik/QAJKPrF/sliMspADqgKkOYCnfW3e5y+8cw8XfVtNADgLGz
tky1f8wtwlLS7ctAvuVclxoZaBP3ewRUQ9SS8ryvbX5Ln68+fjmk3ZFaXyDzTxsfuNmX6EmSPyKa
ZHIHE6vYz9qoGq5WNdpJh+pB24yKTbtFlSUmaYQDlja5LkQSMawPjlUzOgBx8H3dFTwoNiIWfPpV
B3CgVQdAGdPzaReK1DmIScy+ByUaWkNU24WCkzpTKHDo43u6PtGltNr1S7jIAco5oQwv4WJ2Dnt4
SZijc3K3pIf1OtcC/dx2gk8D5fAqhkQRkerN2B5CXdV517dYvBegl3BnOTAAhqK2bKIakmrshJ7Y
XprTpI5Q/cM2rfUI/typvZOosJ8ktFKCDKbFtIYxa9usYM2o2LTVd9wNKXcvlAIVcNJ65PvE5osP
E2v1/JvUZZAh4hiGFgHRb8pH424BQbof8rLZjwucQ8iOHx0+Mh43295trA+4MBeRB6NIi6DPBupF
5/rCrTD+mB/eYjDwcvZeHh2a+/EgNA4l+4ybzX/dnNDCqk7owbr43mp5/PqrwwhezOWpa/nwDNHn
D+qG6c2X4XnsIpv9EGAAohPmgw0KZW5kc3RyZWFtDWVuZG9iag03IDAgb2JqDTw8L0NvbnRlbnRz
IDggMCBSL0Nyb3BCb3hbMCAwIDU5NS4yMiA4NDJdL01lZGlhQm94WzAgMCA1OTUuMjIgODQyXS9Q
YXJlbnQgNTYgMCBSL1Jlc291cmNlczw8L0V4dEdTdGF0ZTw8L0dTMCA2NSAwIFI+Pi9Gb250PDwv
VFQwIDY0IDAgUj4+L1Byb2NTZXRbL1BERi9UZXh0XT4+L1JvdGF0ZSAwL1R5cGUvUGFnZT4+DWVu
ZG9iag04IDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9MZW5ndGggNDEyPj5zdHJlYW0NCkiJ
7FRNT8MwDL1X4j/4CIiVpGODK19CIIEQi8QBOGSZtwa1SZW4A/49SVc2GGNCAm64l8qx33t+sXIk
kt2zAYOJT3aFYMBBjBPOUpYBC9/sr7ef9mG/z9O9A9YFUSabsCUek044ZDwkVKjs8JR3MxAnyea5
IXQGqXPi5JigjRtxDZfWaLJOmwkcOpVrQkW1Q/9WA1d2iuUQHWSM8/uNhoZFArHdks6Ysn7DtFZG
gDuuy7qQpKcIJZLTyq9AfNff5Jo4J9AeHI7RORwBWZAeKF/g2DE85VrlTdJhZR2FuqksapyRLLBk
VRUvESKWSqVaUdZAhU7bEahcOqmCadqTVhFaLYR/HrqJEqUP1pVo6N1QHw2Yy1g95kCWVRFEf8ua
FRJ+5pE1xcv8hj9e27JnTUdEk6CsIW1qW/tw3HowAutAyUJFy6KQXNLSFeRB2RDRgG9nDhVoRhEz
Eui4sYElXeHBms1b4/Z/+y+2/52Mr96O23oHkCBuxFKcPlc6vlgXtUHgO/GhypZrAO6u5QSh99Au
+KlIXgUYAE0DUrsNCmVuZHN0cmVhbQ1lbmRvYmoNOSAwIG9iag08PC9Db250ZW50cyAxMCAwIFIv
Q3JvcEJveFswIDAgNTk1LjIyIDg0Ml0vTWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJdL1BhcmVudCA1
NiAwIFIvUmVzb3VyY2VzPDwvRXh0R1N0YXRlPDwvR1MwIDY1IDAgUj4+L0ZvbnQ8PC9UVDAgNjQg
MCBSPj4vUHJvY1NldFsvUERGL1RleHRdPj4vUm90YXRlIDAvVHlwZS9QYWdlPj4NZW5kb2JqDTEw
IDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9MZW5ndGggOTk3Pj5zdHJlYW0NCkiJpFbRbtpK
EH23lH+Yx7QKjg2E0L6FNrdqpVZpsHQrlT4s6zHZG3vX2l1D+Ps7uzZgwEREJRFC9s6cmXPOjD1J
gusv0wgWJrhOkghiSLIgjsKoDxH91b9ubsMR3I7icDiOBpAUwSW8S/4LenQziukCp5O9OIwHfUg+
B5dfpUUt0fY+a5ZZaD6PyQN8V1JYpYVcwJ3mT8Iit5VGszkDP9QSizlq6EdxPLvwMJEDSN43oDVS
f+SRXi1jENagxQ6UtUB9bAwueNh860XgcAZhTKETZgSHkuK4KHM07vh9EtRcRP0wGoNDisJhHzQG
WTBJWhT6og95jMcffPAwHA/bRFJaUiAYjjepXdpbOh+Hg2FH8k59Rh8G4U10Qh9PH0DyhK9SwlVB
DRsSxNLJTOW5WrlDdqXgGdcdAgBkleRWKMlyH64kSmvAPKmVhDlSgo87Fff0OVGjgo1NOtTvPo5W
k1STXPFnmFpd7fRtoZ5jGdhhi4aDju4gxUxITEFIf+YRWd6zoqghN1RrJk2ptIUHraziKofZJXE/
ewe/H//5NLi5if5QNLPAOPHF6B+MqjRHUFk7kZCZ0gVzRcCCEZ4mZLrUFrGsdKlINrLtVwsFWzcn
wVT86VQyja48SjZfkyk+PcCvR6C0ygf6C/hiURp3lskUOMt5lTOL27ncN4KxlNdYwQ1kWhVQVLl1
k9O0RbXdca506g2lPHOeSOGraZo+lKPYyNFQTebd8rnl8crfQ6rRrI3Foua1YdNxftHmwFiNrDBX
1BSlpVVVYCqorV47mGhaMZ0aj1gy/owkElV9L9NeO1mKS8FpXqhERpFCp3Ra23WdJVV0Syrrrwna
IwTTboUkc/Tu1ze7FCGGdU/tjBsqUiwFt7X9MrFwVo/JVZy5eetUBuVSOByKoRbIb85uLv3G7CtB
QLuyWs7q0qS9MsKzhtTtnb0pxRfvV/IgDZYfnbuyzAWvnflTTa9/qnso6pAT/m0KZmWpFW0tR21t
aZh7jPrkxmoFk2yBhRvf2UWnfWv1T1Ox3zZM3Wi163ECtFPvCJujL8YPT0rcfzx3szneUqEJs+HC
vB552BOlIHVdL355GUJv8oRvXMp6v4O3NOBfB5ak81ELb1rMdS+88kWIJZ7HyK4UCjasoH3UxcE5
ZE5oMza+oN2o9HZpNpPnt2VazxhXcoluCaDBQ7j9trzEaJnIaYmQ77aPjbJZc6Ze9vUoeGfTo0K7
IMO1mPs9sL9ApugfWeDfY45bPP5xrMOxJ/4y/ECSf6srQFpDeQgHn/uXUrg3wm+VpL125V4E+4dn
AH4/0DDD6E/TOL1A/S/AAHa8BFYNCmVuZHN0cmVhbQ1lbmRvYmoNMTEgMCBvYmoNPDwvQ29udGVu
dHMgMTIgMCBSL0Nyb3BCb3hbMCAwIDU5NS4yMiA4NDJdL01lZGlhQm94WzAgMCA1OTUuMjIgODQy
XS9QYXJlbnQgNTYgMCBSL1Jlc291cmNlczw8L0V4dEdTdGF0ZTw8L0dTMCA2NSAwIFI+Pi9Gb250
PDwvVFQwIDY0IDAgUj4+L1Byb2NTZXRbL1BERi9UZXh0XT4+L1JvdGF0ZSAwL1R5cGUvUGFnZT4+
DWVuZG9iag0xMiAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoIDgyOD4+c3RyZWFt
DQpIibyXbW/TMBDH30fiO9zLQZc0adcNIVRpYwNt0iBqw0ACXmTprQskTuW4ZZP84XGeE9tJx4Tw
pKh1zr+7+599q888Y/xhacM6NcaeZ4MD3p3h2JY9AVv8FZ9mJ9YxnBw71tFrewpebBzAS++nYYqX
tiMmAmFpOpYznYB3bhxcEoaUIDPPqX/HoBwLz4XrhIQsoSFZwykN7kOGAdtSTCsb+JjsML5FChPb
cb6/yN3YmQPvVem08DQ5zj0NhgHSGJnqGOWEHC4Nnge8RLIS0dRzfcAhTtfzSOXwa5/4a4yRMN7m
yMHOxbpSQbGonp61Xi8fU4Zx5kHVSvLLpQn5e/drG9joqwD3ZNqnWJejFmrE+6356WYThYHPwoRU
U6CoNwQwl4yiH2e7cheuMCkB3dj7FW0qwc2bT5duF16T6qxu2gLoFOXNavMmDyhIyB1SJAG2cwPw
7kO6Aten7LGKsJVim+NhhBtx0jJGE1hdt2Zf7eGcriAkKdJK7RZHLlunwrMOp7fCWn37HAyr6Khp
jPLOFOMq9Bl2KXVoXTzUD2W/8qpFlEcuHwvcJJTBWZQEvwotM5MFBhjuRB+Zm+aRyXtE5kqWwKhP
0oyIKxCdkXJZhlEpz5B6vFXmKkzvnQv4wJCkeR2rXdp0l7fZ9uo99l2N6mXZqmLMqgORPVqOKwsu
90tdmFwjaJn+uFM33o/rdBxQBAXF6TBOGrmOXxcyhE80OLk4FVdzFiRabTLumHB9cSqupi/KXL2J
Pn1Nl1RwWpM+nNIq64dT4XQmUwWX6TFXG6Uk6lztpXuKU8SgNE41a53JQHGKRUojVbk6E1VN+Ls9
1DX5LzjuVadOrfWgyd7iXLrjz+fuOOuxPVzFZJ51n33FEYvEyR7igmyjdnUNblnY68PUmfzL4uhw
un+pzYJ9JvWv8+f/KBfjfbgWdwBw3gxdETQ3gZaLMifHKq4ZQRLHW1I1tltkvxEJiNYUAQtjBL9p
e6n1JPJEkNvNMsIdRhAjo2GQCn9RJMIUL6xnajIV/OYIPIFex6p+eLrjL9tDQAZ+ZMk1uXjYhNm9
7GpLRGUOs+vYRCkcfHPFtQVOfpQXtQvP+CPAAEQ0KSENCmVuZHN0cmVhbQ1lbmRvYmoNMTMgMCBv
YmoNPDwvQ29udGVudHMgMTQgMCBSL0Nyb3BCb3hbMCAwIDU5NS4yMiA4NDJdL01lZGlhQm94WzAg
MCA1OTUuMjIgODQyXS9QYXJlbnQgNTYgMCBSL1Jlc291cmNlczw8L0V4dEdTdGF0ZTw8L0dTMCA2
NSAwIFI+Pi9Gb250PDwvVFQwIDY0IDAgUj4+L1Byb2NTZXRbL1BERi9UZXh0XT4+L1JvdGF0ZSAw
L1R5cGUvUGFnZT4+DWVuZG9iag0xNCAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3Ro
IDEyMDE+PnN0cmVhbQ0KSImkVk1z2zYQvWsm/2GPTseiSVlf7s127E7bNOOROGlnYh8gcikhAQEG
AGXr33cXJGVZVjxKS49tiQTfvt19+4CrtHf22zyGpeudpWkMCaRFL4mjeAAx/TSfRpNoDJNxEg2n
8TmkZe8E3qdfe316GCd0I6OV/SRKzgeQfuid/K49Wo2+/8GKwkN7zdI7+Mto6Y2VegmXNltJj5mv
LbpuDXwyaywXaGEQJ8n9uxAm5gDpL23QJtJgHCK9SYPghhHAjc5hvnEeSyjRW5k5yIxSFFkaHR2I
sIMX7gGMCGaGlbGemc/ROXq1v4XzVmhXSu8xB+JvwVWYyULSV8mlKESGLjqYzSvubWLnET9NgB8P
27922bx8MuBnN2lvfEFtGY+n9BaMadFwABZ7Re8qfaOXkxG/NImjadfLpIVrnwyii2kDN93CkT52
IHdI76NPk310Ll16Ta0PxYIrZbJvbTFBUGuEcyaTgmtXCSuopmgdtJSG0zbDmAlNBpAk0fnwQJbx
ITJBtuPRRTQaHiNbanS6QlgIRzwD5xlmWLFMOsL3J7PZ/Xv4Mru9Ph+N4gdSkl7jxhGjbiVHaGXj
vPDSeZbI/YmMMDptpBKgFK5R7SwhWKlbScEiVMly0Pt3fhezMLYUnv9BWSsvK4VhskrMpSA4i6J0
hJSpOmexbiX3U3NjADyVorAiTAmYgpqTfUOibZwHR/gYVihBX21TnGMmqQXOaiJPma8RdB3mfRvB
NSGOH5Vn1JVcrpDp4fcamWGLzc2hUPl+Mbp8f0hVaCA8SQVHJsgxwkD3hbVyLRR85aG3x2bOcpe6
6SBX1RsQSplHIqxzVj3dyITKuDRNeclEH40lJZha5wfsL1ykmAqIJUY/lyCLPcj8n5lrJD1Okgdw
dUWiKlH7QAGfWJ+kpLC065Fo6bRQlTVrmSOUxiLk6IVUVO4CMV/QC0C5Pg/I91oo6TesdkczYKmM
O0gZpb6kHQLdr/9dux+NayjmdaUkQ8Ls402rU3dsu+5Crv2gnsqHCrvjMA7oc8Yd7G9b9RrnSEnO
nz1lXpelsJvWm45Li3pOHRL8q5yBtbDS1A4MdZq2rQw132D/gMeVzFYgPUhHHXXSigVZDSn0kApZ
wC9svksvCKKwYSC92tBmcEvOhU+iJI2dBoFdklGZsx3Y51Z+Jk0ZuLOmID3Bo/QruO00xYIdjqaj
B0LzFN4FMPJTnQubw+XZ511ZdRitc5PMt8MXaHd86e4COR0PKKzadMp+ofbwxoICPcqcKDFM1ky0
ZIHw7k/bWdRMWGE4Cg8QV70wtYXa4UvJOxLWovZhhTZkspJOExTTm/8xBIHlp8vrP5kVhWS47aDu
jqZfNVvIvm3uUGTExv+COXcusO3BcceojhTxaXrWcGr2UAgicYTKe1tRK8Vea0U/M7yu4KMBCdW2
x6hnYg75LBfIWSxI3pxCJcPB8jS4gJNLTba6EnqJQdu8Nmgaf2yqWJIihDpzFbWWPIqo5Ng3RREg
S/Eky7pst90FjYlll+GCjJJ4+PCmFW9L9PrD8U3+uz4F2o+FimDvunmqJJ+p/6g1QnLKR+nB/hqA
L3diiTB9aOtJh61/BRgAo1pZTQ0KZW5kc3RyZWFtDWVuZG9iag0xNSAwIG9iag08PC9Db250ZW50
cyAxNiAwIFIvQ3JvcEJveFswIDAgNTk1LjIyIDg0Ml0vTWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJd
L1BhcmVudCA1NiAwIFIvUmVzb3VyY2VzPDwvRXh0R1N0YXRlPDwvR1MwIDY1IDAgUj4+L0ZvbnQ8
PC9UVDAgNjQgMCBSPj4vUHJvY1NldFsvUERGL1RleHRdPj4vUm90YXRlIDAvVHlwZS9QYWdlPj4N
ZW5kb2JqDTE2IDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9MZW5ndGggOTc0Pj5zdHJlYW0N
CkiJ5FZNb9s4EL0LyH8Y5JQsaoakqI/01qbpbg4beBMdCtQ90DLtqJVEr0g7m3+/Q1qypdjNBzaH
BaoAtqMhOfP43jzyYxac/X5LYWGCsyyjwCCbB4wSyoHi3+ZXlJAYkpgRkdIQsio4gdPsezDCIGX4
IseRI0ZYyCH7FJxc1VY1tbKjT42cW2ifm2wMf+q6sLop6gV8aPK7wqrcrhplujFwrdeqmqoGOGVs
cuTTUJcg+61NusnEY5/pyTJwOe3SXoxBN5vvLzdQGFD/WFXP1AyshmWj18VMwVyp2VTmP0DXcHlx
DcZKWxhb5AYmRy6LL8A/RT3XTYVhHPoVx34jB8rsFdXO7Gp5WQ3VqsTk0liQ+d+rwhQ+3f4G+KdX
bL84Wc9gKRtZKeTDwNebzxdxGPJ+vcMN2+Ic/GDgsIj2s1k8xhaSkCBzyt7r5gdIs0RSDei5Z7za
MS77jLuFL7PAKyvmnCQxhCzFHIJDo4J58DHrCdLX+liVYRL5yRGJeF+WuCzqORDpbmlKEg6MEZ5u
F99DtcvWw3ewE2ImCBdtSgfy1lHZnN2oXBVrFK+qLfKFspaNAvuwRCLL8gFKnUuLlBc1XI3hTiO5
CrldVjgeVYavkXAFg61hrulAJKK3NTt0Lsq36ELxEnSHIVFOzmkLCalDQCOrR/jlSq07bvsMkkGd
lBImgIdiSKEr9Rka+Tl7XEC3BRuQuDRNXwnyOQojTBrFbbrsTiFPVbG4szBVoC3+DyZXtWwKbeDe
h5/kOdercoYUTofsRWlKkDxxkDwX9LT+Z/KilBLetUBPZB1ttZ4p5wzGKolVniiyIO9Awu3V2JE8
vs2uYYGT7uWDc8rN68nR6A8S8nAIKEmIiEHE/CAiF30TQDHuW3fUtJVNTgkgUZsmcu6GKkWifs7L
A1SIp6iWMrduJJ4mRlk3bYAojtFMEVF6ENEm+jr7OAzJfXb6rpSs0RHnqxLQmxv07UEzRZEgqcCE
4lV+yBL2ONGeH7qlkzdvJhET3jXTZ1SQk5qsc/Ue5HJZFi1hpVqrLWDAYwr+0peYv/R6XarGn1w4
zY9BP8w3BjrYGhGS6Gd26ILibQQYCnLeddRUmtbAc13P/EEsS2yj45VBrc3Uush3sjx+B8fyHsuu
lfGHIM6xzt8HKEJOGLYRPSw6F30TFBw3q2uj3sXgGJTNJ6fO2PCioaRBO/eGIQeWsXWMttM8XGyj
7sgaapZTkmIfpfRVmo3CvUL3NYtL987w3oY8h59xd06L3bL7l8eXXICeuHv+OtP/J2W8ZDqK518B
BgAXJBugDQplbmRzdHJlYW0NZW5kb2JqDTE3IDAgb2JqDTw8L0NvbnRlbnRzIDE4IDAgUi9Dcm9w
Qm94WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJveFswIDAgNTk1LjIyIDg0Ml0vUGFyZW50IDU2IDAg
Ui9SZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9HUzAgNjUgMCBSPj4vRm9udDw8L1RUMCA2NCAwIFI+
Pi9Qcm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3RhdGUgMC9UeXBlL1BhZ2U+Pg1lbmRvYmoNMTggMCBv
YmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCAxNDQ+PnN0cmVhbQ0KSIlcjUELgkAUhO8P
+g9zrND1vbXWukYSdAp60KE6SGyiVEQm9PNb1JMzl2H4htkoJbsjo2woUWUI9E7Chi04uE/LzDhk
TsxixSn0SVPMtCZGLEZSC90Ojc6HEIcdS2Bv6CnrOurURvBfFA+DkfLfu/r4Bvv25SERLIsdM8D5
UJQe6+tl0t3kSn8BBgAE1igJDQplbmRzdHJlYW0NZW5kb2JqDTE5IDAgb2JqDTw8L0NvbnRlbnRz
IDIwIDAgUi9Dcm9wQm94WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJveFswIDAgNTk1LjIyIDg0Ml0v
UGFyZW50IDU3IDAgUi9SZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9HUzAgNjUgMCBSPj4vRm9udDw8
L1RUMCA2NCAwIFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3RhdGUgMC9UeXBlL1BhZ2U+Pg1l
bmRvYmoNMjAgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCAxNTE0Pj5zdHJlYW0N
CkiJnFdNc9s2EL17xv9hj05HViS7djq9pYrTujNOPbKaZCbyAQIhCw1JMAAoWf31fQuQ4ofFtFP6
YpHgfrx9+3b5y+Lk9a8PE3pyJ68XiwlNabE+mU7Gkwua4C/+d/VmfE1vrqfjH3+aXNIiOzmjV4u/
Ts7xcDLFDYmT59Px9PKCFu9Ozm5zr2yu/Pk7K9aeqmu+uKc7k2tvrM6f6K2VG+2V9KVVrj5DH8xW
ZStl6WIynS5Pg5sJO1j8UDmNni6ug6fvhvHjmOjWuRLmd9pvyKrCWM++M+WtlrRKjfxKpeNb88Xs
nj7PST17lTtt8iOuW47CvYN5vxGeNmKrSJpMUVmQznFTUSGc/65zNlvZGojDwZZMy0TR8mxVehIW
Zq1ZiVW6p9x4SnUGHBPyZvmKlqcvMaIQytqkqdnBxc9NZh24BlI0RH+GyFJhn1QMG8C+Jb6Zqiqx
Kh1j6/S0o0Q5/ZTHyE7bmeKSJvcCIInKbF6Gqps1ILMCNpTlxCnR67WyKvckU+EcsF7Dh+hZc4WS
eg2voihSLYUHbojxPY6qZ5EVqRoFDAK4N4xsgrDmIXJ3hFXhWp59njtA+mX+fnZ5PZ0+IqG1zhGC
U1uVdxNHVJnwMTowf2fs15bdGuFwZSIXTyrjnESe0LdSpNrvKTu0BiJ/YBoBDATtKszJ7wvleonH
iJKabhV5XCtmpovJQZUaI5Hix6E0XXMcPSqzVftA1DL1OA8G6zwUQYaY6vTkBpWSKJR2ONaPbHl2
d/thBvhgcms0v7pFgW/v8eSjub3Hk07Gv5md4gNNwY9TGVeryA702eN4ghyDwGRiHxuxsdO4GaqI
Vd9KbUNJHEJ5F8Bp8z0iyOgcY1o/dY4BPWuVQO00s48th6NA18WyZzpH3/6NAyyWplBWrDQTYfyf
hAddOTPWqlT4tmoEqWEm5CY/ZzwS4QVSmn14e3fTZ8sAvPzavTXeSJNGIl1dTR65oUVetxPzQD1z
4eHcGxwMEihYYlynch2gvaGVRvIw9PAwn8WXGC5wKQfYeC5orZ8RozOlBWlyaAHHa3IVAoumW52v
nIvNfhstrRSicKayIqQ1zkUmc9hsonoFvWpN1isdw+LYZXTf4iWeoJMqD077sir9LtwP+HdN2Upd
uAEd8xDJGbbCCoeG0UUsHbSoMCCBqwZAXbmB6hR1ZYJ4Nul3tE4E8ZVWr5pqP6D1QpiD1Xkos0zY
faWLXQ5cTy6vHqOIMqVq/Y7ma/Z1AeAur6aBO6DRFSZ01E7YJIwIZCMBkxXpi1GRplgTuHucslwL
t3deZTVgSIzLj6el3BD0Koo9zDNle8ZiU3MsmIfaMI9rAW4NnsBLCZYym5wzUguesKG7BmUJ/Y42
0CBPSxtGavw0HtHHP4BF+zbxKA+qIqIUVGkfKcvR0cjoVXtB0L5a/c9RhgrrcS/1BWMCxHlJqZTD
cIZ+p1RTQ9amtniQ25gyTRiJFxNc8pYHBqxJJJyEQ/WCUV4DmilXlytXsdDwveeY+73MOWQA6SBo
jkUzDhe8FqOaMaeEKyu55geIJCnl8CAPaSCcdO+CiCXE2uwxTEWqbLTBvkvQi/X/E8psUJ7Ap4Gi
tCAckfZMNYzDkB46dKuxrgkpS+Ch6ngdl7AhST/7FjsOlAyEawgysCRVLOiaO84J7tZDm/zLpOkj
iZFz1yCPhos7D8eblO21q31Kt04NQFnh5TpnAa7aiqiaol3xKpMoPDwVwLU+lBmTPGpta3XqiiTt
opo75YODuLTyLN4C6b5FHv1hNkS9jRM87hVhphRCflU+fmc0cfGeeEzPcqdk6fVW9f0e0zH+ErAB
ghqBrrk2asuzKDeqXnEdNpuwtzXUmWIBieGOhhqmDTcWE20S3tbi6FPP2IAAf2s0ov8BZlF3DMe7
PBWD6+8AO4CBISVgoP2BNOoO3t7w749h0ehYTLGeU4d1litf2X9J/v/xjfmpBNq8+Iypd908F5qb
/vcSZJiO+IP2on+GvtxDJGk6eaw+kG4WJ/8IMACfhMnfDQplbmRzdHJlYW0NZW5kb2JqDTIxIDAg
b2JqDTw8L0NvbnRlbnRzIDIyIDAgUi9Dcm9wQm94WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJveFsw
IDAgNTk1LjIyIDg0Ml0vUGFyZW50IDU3IDAgUi9SZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9HUzAg
NjUgMCBSPj4vRm9udDw8L1RUMCA2NCAwIFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3RhdGUg
MC9UeXBlL1BhZ2U+Pg1lbmRvYmoNMjIgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0
aCA2NjM+PnN0cmVhbQ0KSInsVU1v2zAMvQfof+CxGxLXTre0160thg7YULQGOmDdQZHphKslGRKd
j/36UYq7Jlm6w4DdpgCBY1KP7z1SyvtycPLhLodZGJyUZQ4FlPWgyLN8DLl8Nk9vz7IJnE2K7M15
fgqlGRzDq/L7YCTBvJAXWjJHRVacjqG8HBxfW0ZvkUeXXtUM/botb+CTs8TOk53BO6/nxKi58xie
cuCzW6CZoodxXhQPR6lMHguUr/uim0rjSar0RxobxGnj9GMYgsfWeQ7gLPAcISgjX+xRmQC1d2br
reu8xgzg2ib8VDotJzkels5XAlh1bUNaMVZQKVZQO58wDKogmgxaBgrQeregSpJ2oUzXMLUNApNB
QXNWI5AFXKBfCwZ70hvuQqScu242F3TBqzDQbJ8Y2pBsJGM6cXgN7KBV+hEZGhcEnhiMWsM0WW+c
xz5MPxSTswecTUs7IxxXEVHZKskTPRpDiDjSKz9HVUWZ1nGfzdhIfU8LUs0W7k5TRGhwYrVWAUMS
iB7rSCtiSDcoIEyRl4j2YMVd+ZGbx4bUlJrINYhfTSUAwOpREMiKH0pr11nODszU1gT1oA7gwomp
pk32uBq+3G7aIQwrccEJZs9cJvvi5jluZYaCuIvwcPSCreJXQ4bi6EzXydXz0VRatAHgdYtQE4oC
2gzrU4EoHX32kqt3qSqu5qoLiXZqOYISzjJe3j7h1V08dcL+HuPv3nrJ7k/cs7MWhaOCpUojhSvG
fgy2qCaxQ2moBBTLluUeSGhRUx3PipAKiZUQYrIdRlRhWMnYN67F6lB3fj/xu9p/FTv88H/7X2//
dzReurPvuyHIpaWaDPbW1aqleMV97CxCMYx/EOP9HPh6o2YSLb71g3xVDn4KMAAkR9baDQplbmRz
dHJlYW0NZW5kb2JqDTIzIDAgb2JqDTw8L0NvbnRlbnRzIDI0IDAgUi9Dcm9wQm94WzAgMCA1OTUu
MjIgODQyXS9NZWRpYUJveFswIDAgNTk1LjIyIDg0Ml0vUGFyZW50IDU3IDAgUi9SZXNvdXJjZXM8
PC9FeHRHU3RhdGU8PC9HUzAgNjUgMCBSPj4vRm9udDw8L1RUMCA2NCAwIFI+Pi9Qcm9jU2V0Wy9Q
REYvVGV4dF0+Pi9Sb3RhdGUgMC9UeXBlL1BhZ2U+Pg1lbmRvYmoNMjQgMCBvYmoNPDwvRmlsdGVy
L0ZsYXRlRGVjb2RlL0xlbmd0aCAxNDkyPj5zdHJlYW0NCkiJnFfRcts2EHz3TP7hJk9OR1IkJXb6
mtpO6s601chq2k6UB5AEJcQgwQKgFPXruweQEqkwbqdO7LFFaO9ud+8O+mF18fL9w5Q27uLlajWl
Ga3yi9l0Mp3TFP/ib1dvJtf05no2ef399BWtiotLerH6fDHGw+kML6Q4OZ5NZq/mtLq9uLwvvbSl
9ONbK3JPzddytaCfTam8sarc0FubbpWXqa+tdO0Z+sXsZJFIS/PpbLZ+FsJMOcDquyZojDS/DpGe
TONqQvS+VpnUqpSUG0tWVsZ6jl5Ib1VKiTbpI9WOX1qubhb0x3IgZCcAv3Y1mQH5t/Am/qFlA+ci
nnsaol8A0a3Kc2ll6UlUlVap8MqU7pjUImReyEwJ8laUjkugVFovVKkPtBU72SGmqR24WcBlECv/
qpWVBWK4Bi2me8STGakyMuANuboKQRg1VEDkt1JZMpW0IT3U/45xRHnoZT3ig5QIB27bIBywi3Ss
QRWVUDZmVVmzg1KnNB6WJMqMlkuqRPooceTj8t3Nq6ur6acu2vrSm41EUEt75bfkTG1TSYAqvcqb
tAbQb+8eWuD1i6PP+sIIK0FFDhQFtKZkE2L1lBJZpvg3oY81F+JAybAsjRgZAUx40lI43wkDRWsn
81qzEJ9rhyoOgVQ0ht1KkYHjTv0J8iGTc4WpdMEyqFGWWWUU88oc4rEqU4tAiOr4FChJ8GSvMr+d
dOG4QvlFFBU8LUq6X6w+dGttTIlTe2EzurMW52+MtWhjfry+fHd3c+SzwSzUZuu5KJIqktd2H+dt
nB+jLWEE0sa5wEr7fKN2HG5Im0zC/jooCn8VMTuRmNqDCtlDTGrrwAToNJVXhUIilThoI7Ke7ieF
jtQE9ph759Gfm8g0KjxpyN5Ot6LccJ6YeHtjH7u1p6aM3nCwz49mLyEiI8JZ7K7QP61nxA4ViURL
HL1HdzjS6lHCD+tnvUaEabLhkcHJaOEgMSfae7RXWuOH2zIPHTiW5YTWpIIE3iIxg6nZFf+UETAa
CgbF6XZ+YXAISZcBrhJW4ClISKCUyvEEqPjPLKcw6OiJUfZVvaEooQt4qDMQ28xOb+oJUiSqbPnK
OxXf56SF3XBqcYizQJnMsTsy1pHRWze2zq61V1Vn/IMXDAPss1hQKWUWokiRbrupj0h5zAckI12/
WVqCWeXgjlMVrgbIN1Mc0X6rcGBIjyYSGiuDVdmBBn0DFcI8T5RW/jA5La0++wMLEJArVLozKosC
VsrnQutR/KuQheGBhN6WkQh2GWhwBQ719mxLZH99Bro6lAtC2xyat5d1uB+EoZZhQGQ15u4AFtrS
ihRFqr8Zw7A1+hYMEPhFwj6sXDm8BTodYOsyJMSzmFfzpDcxRzzPuVxe2qc1N2RoLQ7SxmU5nE8c
molslhRUxltoJ6xqDITR1HeOq2QaNp7WcWE0Q/T5/eL2w/Ojk5MDffxzdvV6+gnJP0iJ7zi7r7ld
+5DidEUDxxDEYYnapnnyzqRulBs1+0Hw3mlZOYPsvyNOkkDTcKFf2fK/XfzmKC7sJS18924X7gih
NU05Zpky4cW/3/jY8GFoN3vdKV9HR+zjy70hd35XQyt4kxrt+pOcm7d2UZLzUds2KDgvwT//HfYQ
nHLc4GrYr3xuI7zci8O5PTlKy8Qi0o12dTxcmgBDXoVBPe4mVWTydLWIWjORbPhxEq4X57WvL+Vk
Mxn1K4/vfLhfrF9wFYI+/Hq/aOuKaaa2ThVMl6OFUYJWmCQ4ujX7swUG0jMtm/vpaVjGC6BXYQCh
LZnslA2BtDA2EB4wx+NnF5Z+DZOn/XHO/+rrEQhfQFxreKwhLGrikQuN4tprfQpNTf5NGeK9tdE+
+DheRRvaxgEDCnSdPeF0RFCZr/Xi0C807F/2r+LdwNuKj7X5xDnWwLsYsgVvXx0NcPM/Pqn9Xo8I
ZhR6Qmdfd18qxZ8Pf6phitmIPxbOz8/Qx4XY4On8U1Pe3eriHwEGAC8zpwANCmVuZHN0cmVhbQ1l
bmRvYmoNMjUgMCBvYmoNPDwvQ29udGVudHMgMjYgMCBSL0Nyb3BCb3hbMCAwIDU5NS4yMiA4NDJd
L01lZGlhQm94WzAgMCA1OTUuMjIgODQyXS9QYXJlbnQgNTcgMCBSL1Jlc291cmNlczw8L0V4dEdT
dGF0ZTw8L0dTMCA2NSAwIFI+Pi9Gb250PDwvVFQwIDY0IDAgUj4+L1Byb2NTZXRbL1BERi9UZXh0
XT4+L1JvdGF0ZSAwL1R5cGUvUGFnZT4+DWVuZG9iag0yNiAwIG9iag08PC9GaWx0ZXIvRmxhdGVE
ZWNvZGUvTGVuZ3RoIDEzMjc+PnN0cmVhbQ0KSImUV11v2zYUfTfQ/3Dflg6OaydNute2CdYMaxbE
Hjqg6QMtUjYbidRIKk7+/c4lJVlylKJLAEOWqPtxzrmH9IfV5M3vyzlt/OTNajWnBa3yyWI+m5/Q
HP/p6uzd7JzenS9mb3+bn9KqnBzR69X3yTEezhe4kWHl8WK2OD2h1cXk6MoE5YwKxxdO5IGav9vV
DX22RgfrtNnQe5dtdVBZqJ3y7Rq6tg+qXCtHJ/PF4u5VTDPnBKtfm6Qp08l5zPTDMhAubJXhD8qs
c6oQQVtD2uTWlenaKCWVJL+1dSFpzQvNg3rCLW1I4PEupojZuYWPN7S0tcsUXSifOV3FKHdHy4vL
5d1rQkMlTb02WODrbDvI2wvUL0HGQGuAwIX6GH1KTuCbwy1hqHL2QUsGTdC/tSh0eOoHc6qyLsyI
3htSj6KsCkW1RysCH9oTUuHFSrigM10JE0gZWVmNi1I8NR13WPfRJbyXiaIgLZUJOteoKAbbFHYt
imfPhPc20yIAvp0O29jQPuqeluXy9iPZnEolPOiXURs+OCVKQh9XpgEPDUxjkLHim4obENBwArCN
nYCkYGmtjUwiOCi39owpU5eIGxCUgvGzyHolsnsVSCCUV/xxyC4S8RuQ/c66+36sUhixUSXSkn/y
SMRUUV7YXQtAfBasLZjvwJyBlFxvIjYRyTFuON3ZcaiZb67L2BBbPBY74VTSPrjHl9R+7OOf20Yv
nkRhzWbA+56hjr4WTr4eo2u31QACFUPzRS3T4PBiJLp71UPhQ2Gze9oqIVkoKLct/QC4MbSufwJU
tG5Szy0rDAEKS+22ZHM7HaJNLBtHTWqxMdZDZ4PxjEQLn8QjVRC6QEjkkH62t6efd6Wz2Sk6ulWy
zrigzz0F9NOiahV05xtDD+zFblr4wo2XdRE0Q1qq4NDGmiEHz46l75xO5Fizl0JS9fS5m3BpNhHp
RalatnNny97NNGLsL929oEs1qtZKOW3lNKVu/JZdqhMZdNDM5lPUR5/GcRt5od811KIYjv5dYL5i
NZSqtGyolY2GYYcilSrXgCcZP/BJoo1DudPgfx2dVfJ7yTabzaUsGay29SZY6jj2EgVex40Ns5RQ
92wkgWQdt8Mo1eaNr5+vvrEN5v1ovQFsxIJN9gEmnOy9aRZBpM5z5XhJx1bEfIyUPdltuGm7Z0as
9ulQZrt7xpBcIy0//fX3nxcvWEgPK1+pjGnlF9tEyecxRrzLWVSCgRh2+MJ+2ZuMAzWDh8rWgLsx
a1CEcTXcXt85RlUzHQG4ZwJbkdj3B4WtFRYlhSaxygMxRu3wBA5HZw/8GC09jK5tHAAEYZ6bxgrr
4Wt2XftgFC513lQQna7JnIR9yMpgWDsNeeyshKOXozK1I3rINkmjLpTItkMwfaCteFDP4YuzjJNK
H0f1gBixWltv4gYzOMm0M9YWOPux9w1gO5u9BVyXj+hEpoHaCyMiQgYR0WimDm27RWfcWldxwo2v
y3TYwwB3ITMrcTjh0whI8OaXwJMovgNj7X2N+umT3aFpNzys6IMQfh8DJEJqOJWB47g3uhop6xCP
NFz8FGeVAQN6sw0MGsJoJ9ZpR22MjG0MR51C+t623JcJH+fGFNi8zxroKg1PVTJ7kCitO05TDamr
x6CMBzaYori3CjPqCIrlVjntOzPsDg198+cyUwpged9y2Wu5yzemj+cXz/fm57T/r9df2tq/1FPi
MyLP7fAPstT8M+ePGoAupvzr5uRwDX29wYmGFqffGrFcrib/CTAA4/I4KA0KZW5kc3RyZWFtDWVu
ZG9iag0yNyAwIG9iag08PC9Db250ZW50cyAyOCAwIFIvQ3JvcEJveFswIDAgNTk1LjIyIDg0Ml0v
TWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJdL1BhcmVudCA1NyAwIFIvUmVzb3VyY2VzPDwvRXh0R1N0
YXRlPDwvR1MwIDY1IDAgUj4+L0ZvbnQ8PC9UVDAgNjQgMCBSPj4vUHJvY1NldFsvUERGL1RleHRd
Pj4vUm90YXRlIDAvVHlwZS9QYWdlPj4NZW5kb2JqDTI4IDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURl
Y29kZS9MZW5ndGggMTI5ND4+c3RyZWFtDQpIiZxXXXMaNxR9Zyb/4U6enA4hgD+S9C1N0jSdSZtx
6NfYftDuXkDxIm0lLYT++p4rCVgw9ri1xx4bVud+nXOu+GHSe/Hhy5BmvvdiMhnSiCbT3mg4GI5p
iO/01/nLwQW9vBgNzl4NT2my6J3Qs8nX3nO8ORzhhRJPPh8NRqdjmrzrnXw0gZ3h8PydU9NA+ety
8pk+WaODddrM6I0r5zpwGVrHfvMM/WKXvCjY0Xg4Gl0/iWGGEmDyXQ6aIo0vYqQH07gYEL0xxN/U
oqmZ7JQULTg4XVJR2/L2CHgHKr5GNJlrTx5pamuo9Ug1zHkPUyJoH6SmxtnGeq5yGN+Jk+GCJV3X
rQ9OBY5QqmlqXaqIDzh5qUGDSg18iRzItoG0OVI80Zec2PlgNNiVs9eFe+vaVXH1+d3vN4Q6VU4Y
WZbWLHmNuFPrFik7VUgmjSpvkVTFtVrnAWXIpXI6PXl9AsTrZ2RNve4LlEeD2ARa6TDfLxH/qbAd
jKfrJx3ElI2f27auSFUVmOIjKH4BQzmFYyAL+qaFc+wDZv4r3vM6VnasZ5kCOIMkY9VLpWtV4HF0
WZK7nLz9TJeXm1JVmvnTGEI5p5eq3lKz22mirzrgmac01VxXg9hlhxHjxwLCxYibSldzXc5podZU
MC0sngG9pm293wIZBbugkFqHKV6wV5Z8KxAZUMJIoh93UbrjuT65+mt0fja86dPV5Y9vT09fn95g
RspU8dSnNzg23py7+jAajoc3CPOb58xLz124TVQ08OEBI/MtTQUpdvfYYGatBqs0pif5nb++eHWT
2LEJlYnQ+lbVdWxbxVM8XxHXnlfS6/49g/E2QcXgPqBo5SqfzydKSdaQpfGNdWEjxdwOqBXo+3QH
niEdPBklHpamTU3rxALS+Y514M+72u+gqY4dokJxkwOjSSpNmaTgAKxs2S6k8QdwFXs92xpKl3ZJ
U9bJafjVEj2H/EIrtqxqtCLJ4rjfzNhAAvV/9JoPeslJWVlqutZhHc0zUM3KS/qOeZsjPEey6MuZ
rJ8jtTVRCfHhiF2jsq2PbqBQZZz5n5epcv/9w7Z/WLGlXZfMPhQ1GERHZ4/uRxeTZNQ1HyAnb4Cu
RPheSjvo0GNW171hDk1emWSomS0p0rHx72SP0dgZRypGyStCGBM0jC8yK+2NCOe4ZL0UQssN4Jg4
RZ9r+Mdik4FvuARUuV3XLMdTtlD7Y4r/aKicWxuFVHBYcWKgKDPxpg9twbK8zmyEQLEzIH1lQr9L
t4JLBWeW/aPlJESymULeIeLhK8aM4Egbb9H/IFHx1mN9dPx3q51YYwk/iPZgkl1MZaWtrLvNdjLV
DupIKUuKm5wxyrQmDntZYEVHOyvWsk+iyHaJ70uh39lB4uFwkkMfqfUCrlTB4xbssQ85ym0fRlQM
bbRGlSU3IW5SsbhcQgcNZmjRkl05xoZOSX2x6TJ6fCG8+Qo7RGxrkncXClumf3BDSHcjYXCpfIfo
3WsVAqHf8NzW1PqWxevtdgbH5rO3BuJqjn4rGsmMzA6FEn9iU3LWjXbb4o7NZoWbBEjp2QzyxVJu
KTrfKUvHW/dCGW3hdaWVW3d6j7Q7tbPBwLa75N6rxbYYtLJYJ5rFwfXlZrPXzUr7svVygZ22Loob
vU17Z3BEdQ/cye/a4N1T/+NK/0cL2YJt2EAHX++/NVo+SPzcYkijvnx+GB8+g1LUDO+e3eRN/n7S
+1eAAQAIxu1qDQplbmRzdHJlYW0NZW5kb2JqDTI5IDAgb2JqDTw8L0NvbnRlbnRzIDMwIDAgUi9D
cm9wQm94WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJveFswIDAgNTk1LjIyIDg0Ml0vUGFyZW50IDU3
IDAgUi9SZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9HUzAgNjUgMCBSPj4vRm9udDw8L1RUMCA2NCAw
IFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3RhdGUgMC9UeXBlL1BhZ2U+Pg1lbmRvYmoNMzAg
MCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCAxNDI1Pj5zdHJlYW0NCkiJlFdNc9s2
EL1rxv9hb7U7lCLJddxr6iRNOnXqsZU2M5EPILgSUZMAC4CSlV/fXYAUSUnJJPZMzIDAfry3+xb8
bTF68fvDFNZu9GKxmMIMFqvRbDqZzmFKv/Hp6nryEq5fzia//Dq9hEU5OoeLxb+jMb2czmhB0s7x
bDK7nMPi9ej8vfZoNfrxaytWHpqf+8Ud3BqtvLFKr+GVlbnyKH1t0bV74IPZYJmihfl0NlueBTdT
drD4uXEaPc1fBk/fDON6AvCqqgolhVdGgzdw//YGrmaza3quTGHWilwfu+gZDGsAixz7R1yFUq0U
ZqA0fCajbPMRVqIoaIX8+K0B8opryhXdJBpYnrHxxuJKWefbPTuwWNCj4xg9bWWs3M55LKE0GRZQ
e1WoL4xbWReeMqLDx2gACJ29MBZqHbZMjiKneH2uXOdYWGzTkRT+rme1gZHTJwPjO0OpjX3zkMRF
uG3DaRYWVmhHuVAQy/PU+Bw2wiqhvVueJdADoNmt+yco+rh+i5kSvTdJeCVNmSodyHRgVn1rDBqB
vrxIekbUM9oIgRuAULuIMNLOiLJLeKGpt8ZkycddMMeb/T4YBxmulI7st2xV1ngjTRHK4fLqavo4
OUnQW0qzqm1lHIYcLFbGeiZWGq2pHbhS/6tFofyOq4EQpG7o6sElJxniDQcB97ILLG+Q6HaqVIVg
VG7j7l7C1Ic7LXNLPfoFoRLyCX00lxnQxoci3ZHtm7smbEd/JaoNQbGypgSjcYihLEydURpbYTPX
5BLWluduecHc9FFtvfTD6BnrR/Tw7q+Pf76GlbFsGiRaL4iNQWwp+i2ijg65Cd/rk5QMGiI57L/l
eQdkEjEG4rArh+UFbHO1PJP5SWZIAdZctEjMkSyW8ZlNNMG7GPWne0gLI5+oRx3gM7WkR4auj0BO
qRcY9idUfLKoM66c5jyVvpTGhqWejuwrs2eoV6RwZ81GZewr33uOgkn/LdFzR/UBqR076Blrw1dc
Z3tRD2KiDWRqtUKL2scSGdqiBuAwT7HiRIlEnXDuFAXJKQ6IgcwQtlxFsceXZxTaKVY+3Tfa6JD6
LjspxBlWhdlhNlDioB6h8/tSIfQO3k0u55fw+R39+wiMqOGWDrnL/Qz4hhQPO4c7NqjY32xp/LBV
Xubj25uPnb4x7uO2pIgTfktuHuqmEltp7FymgmMnZltdaFouxVxs8HT5nOLm62J3OIO/Mk9vSMEp
r3ARYEdtXr43C2xQdPC7iifTEXIH83Q4caluNZcwZStSulIkEerMyJrfwFbRpPbiCdkQFaUL5/vm
Gq/4LMqqiPVArVGwyORmu6/5qDWwNfYpxNVV+yncmptCL5cfwe16MutuNKlqJwRj9113mB+vpgRc
zfnE1u0wP8yLs1aSbwLIw9FJq9KDy9F+Dg/2Ckpm14rcYY+2Reqo+ymgONmjPjU12kyf5FBBic+S
u4D+DovE7I1GFWunK52O04WJD83Kc7ohnxzTWxrSUlV0kRn26XDSkhLsQrxUgHSDYYei0QIXMIfY
o++j7sVNPWvOWxQlKym3pcMiToFVNy046nQXTkeLCWhUXRr391/hqJ2e2thDuCwSx7bX911CPzlY
o0YrOIyTJMWIQ0Ol2N0HhN8rSGeN1clbJX2xG7wdkNQgKWlSGE0bSUR50HGrklHlXTiWCx7wNN0L
Q1fhRhHom4M7MRneDE29ztu506OKbpNUfJw14ZiH89aktfMaaeZUhAfxTdN2eNHkgp7N5vNHcGS4
IGu13VDG0QidZOEh4VjVWsaL6vJcTXCSHHGdKcJOpTXvovlFV/ayEspidqQJ/Y+dY5XYt/zxw/d/
K/1TJ0DVL4oJHPy8ea4Uf6H9UWuEWcIfZvPDPfD5Tqzp7dVj0xxvFqP/BRgATWppxw0KZW5kc3Ry
ZWFtDWVuZG9iag0zMSAwIG9iag08PC9Db250ZW50cyAzMiAwIFIvQ3JvcEJveFswIDAgNTk1LjIy
IDg0Ml0vTWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJdL1BhcmVudCA1NyAwIFIvUmVzb3VyY2VzPDwv
RXh0R1N0YXRlPDwvR1MwIDY1IDAgUj4+L0ZvbnQ8PC9UVDAgNjQgMCBSPj4vUHJvY1NldFsvUERG
L1RleHRdPj4vUm90YXRlIDAvVHlwZS9QYWdlPj4NZW5kb2JqDTMyIDAgb2JqDTw8L0ZpbHRlci9G
bGF0ZURlY29kZS9MZW5ndGggOTAwPj5zdHJlYW0NCkiJ3FbBbts4EL0b6D/MrWnhqJKzSfaaJuki
BVoEtoBdoOmBokYWG4nUklRc/f0+SrItu0luvayDAAk1fPPmvZmRP6azD3+tYlq72Yc0jSmhtJgl
cRQvKMbP8Nf5ZXRBlxdJ9Mef8Rml9eyE3qU/Zqd4GCc4kIg8TaLkbEHpzezkTnu2mv3pjRWFp/Gz
TO/pi9HKG6v0mq6sLJVn6VvLbhtDX80T1xlbWsRJ8vCmTxOHBOn7MemQaXHRZ3qVxmW0iIiumqZS
UmSqUr4jbyi1QrtKgIZ7Bn4C1p8RrcBRGU2AI1OQL7kvpbHGG2kq+rb8dH12fh5/p5ydtCpDOXgo
2blQJ64E3BFsmV7fUwYeexLRePrPkpSjjfKl0n0WJ03D25S/lk5kWZq6Zp2LQNC9zg5pVqbmXa6a
vVXS0cObPfQoHKCzyshHR7XoqHVctFXVUca4JBz8ykn4OQmdg0JjrMdB1s2Pirpyo39j6Vt1chrr
e0FF1O9IWhYeQgpk+LdVllGmn6IVxvYg+5zBW1GBNy6CG61Wy+tdWD00HiHVEJFPwYLopLzjqiBn
cEH4g1tBhsY0bRWgw4Mee1fGIOhUyL1HjZCP7KlkkaOrhdseONiGgx4oCBn+BwUyrX84EZUvTbsu
j5zf2zOpGmJp4yHUqtOytGDs+naA262VvGUJfMdHzYhBXCuNaLRpMKPmXImRoHt4Bw/vPNWtA3oF
WVyLUeoGf3a8J3AhjTQW49wYnQfQ669XX24Dg16j1c3taosevT56xyre6Z6gCzMVOn1TskU1Gr9w
x9hpHzhas2Y7dEE3pH5Bw6JQEm2zETZ3gb6ypPmnP9Ws1mUG/YasnfNcz8kgwh4kUvqwxQehe45U
iicQIFkaBRdgPNoTtAeMkrvQmiExYvaQb90vy2InGH0aLgRh+4a05knlgM5zFQwXFfgAtB7sR7qe
8CHDfT1u2xnSaD2uuKz1OA2zhyrGXQWTNyrHfAS3Q95d0ccmubBeZH+1QROEgRWQQ7Y2bF6r3GM0
EJhKGBB7qZ6zqNhXnDGiVLAkQ4Yc3lMY5ApzifWO5bMplSyphnGeclUUkHlSd8Z+w6zHJ4GaCi+p
QmBNb/emE/W0j55r0VfeQofcD4L/Z9d/H42X3uR/t3PisIUiOvrc/mxU+P7wucUuSObha8PiOIa+
3Ys1nl58Hxv3Np39J8AADKWSug0KZW5kc3RyZWFtDWVuZG9iag0zMyAwIG9iag08PC9Db250ZW50
cyAzNCAwIFIvQ3JvcEJveFswIDAgNTk1LjIyIDg0Ml0vTWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJd
L1BhcmVudCA1NyAwIFIvUmVzb3VyY2VzPDwvRXh0R1N0YXRlPDwvR1MwIDY1IDAgUj4+L0ZvbnQ8
PC9UVDAgNjQgMCBSPj4vUHJvY1NldFsvUERGL1RleHRdPj4vUm90YXRlIDAvVHlwZS9QYWdlPj4N
ZW5kb2JqDTM0IDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9MZW5ndGggMjc3Pj5zdHJlYW0N
CkiJ7FPLTsMwELxb4h/mWFDj2ikkvQZaoSJRVdQSB+AQ0m1iRBzkOIjPx0kDgvIQFw5IrC+r2dmZ
OXiPFRudrgTymo2UEpBQGyYFFyGEf9vuKOYR4kjyw4kYQ5VsgH11xwI/FNIDmWcGkstxCDVlg7lx
ZA25YGrTjUNfF2qJ88poV1ltciQ2K7SjzDWW6hcOFtUjlbdkEQopr/c6G9EaqIPedOsURp3TtzEm
HJgniwQnlan1mmzqtO8+0Xyj0GGAKsgSdA1TbTXSrF2GNnCFh9dV1pRkHP9RwnexOuSV/LH5X/+j
678X46sfftkMQQ7pPcdOzZ4edHtXZ40hyGF7TuEuB1fLNPfT+KY/tJlizwIMAFM53dkNCmVuZHN0
cmVhbQ1lbmRvYmoNMzUgMCBvYmoNPDwvQ29udGVudHMgMzYgMCBSL0Nyb3BCb3hbMCAwIDU5NS4y
MiA4NDJdL01lZGlhQm94WzAgMCA1OTUuMjIgODQyXS9QYXJlbnQgNTcgMCBSL1Jlc291cmNlczw8
L0V4dEdTdGF0ZTw8L0dTMCA2NSAwIFI+Pi9Gb250PDwvVFQwIDY0IDAgUj4+L1Byb2NTZXRbL1BE
Ri9UZXh0XT4+L1JvdGF0ZSAwL1R5cGUvUGFnZT4+DWVuZG9iag0zNiAwIG9iag08PC9GaWx0ZXIv
RmxhdGVEZWNvZGUvTGVuZ3RoIDgwMj4+c3RyZWFtDQpIidxVy27bMBC8G8g/7K1pYSuS0zrpMU3S
F9A2sAW0QJIDJa0tNhIpkJQd/X13KdmWHy166aU2YNCiuDM7Myu9iwdnH2YhLOzgLI5DiCCeD6Iw
CMcQ0rddvbkIJnAxiYLXl+E5xOXgFF7GPwcj2gwjupDSnaMoiM7HEN8MTj8ph0ahG90YMXfQfabx
HXzRSjptpFrAlUlz6TB1tUG7vge+6iWWCRoYh1H0cOJhQgaIX3WgLdJ44pH+SONtADDDtDbSNXCt
lZUZGuEkrY7U7VXx1wDiXFrIdFqXqBzMaWGJqVbgcqRuru/AYKWN427w2SEB0GZt+b/f/jH1lbty
QmVgc10XGSjtYCGXCEZaBKdprwGFK7Brusu6UEQ2kYV0klATbDSdPxQAiI2mIhna1MgEM5BqjW7h
fvr++nwSRY8kxUe9wiUpKx2IwurNCcv9bKTu6cectyaJAuZGlLjS5okpJ0itEtxcGyi3tgrnjS5E
gyZgDREeTnoqbDqU1taEvZIu759XiJnt6qedZ5gFf2XYJ+WxySV2wg5BtP8b67CEUjTMmPonE1cK
ZrPpNQNZJGH54jFxe8xas5nbShjiyEcU+T5SKBd5omvTQ6PWv5Gs7aVWgH1tO1qyzVNH2rPMBUVD
QJprmdLCy7HK0dejn4Y1Zw79dDkO6xb/hW1DUIn0CZ0NujRXNGscZrHnA1Bo0z2nmJVUBFX6mVkT
bWXwPMkifK40pyBp/Kbe9Nx1t1uxDXopCplKXZN8OsM2JAYJiPDmh7C2lwMSYyepW6Msj5+jmRr6
Cge+rUePOavUNJXbSdWuOcfjdcVTQ6NLE5tTzBmGVCcbKmFIyA7S0tCgn/CltDIpELp7WZWeGH5C
Ot29qZkv3saRZdrzj8KtTcYJ0Gzjkm3cebo0Ww12BCxQPInFoS5zo8teE8dE3WtsK2FldC4TejJk
UKuCottleJMpTktVCOrtWPQ5CDWdUE6mwuvJE3M44oeLw6f/oXP/6/F/R+N3b9Dv9RCQXxcB7H1u
nyvJ7+3PtUKIhvy6Hu/fA/d3lDuILh+7mb2NB78EGABwVGcADQplbmRzdHJlYW0NZW5kb2JqDTM3
IDAgb2JqDTw8L0NvbnRlbnRzIDM4IDAgUi9Dcm9wQm94WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJv
eFswIDAgNTk1LjIyIDg0Ml0vUGFyZW50IDU3IDAgUi9SZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9H
UzAgNjUgMCBSPj4vRm9udDw8L1RUMCA2NCAwIFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3Rh
dGUgMC9UeXBlL1BhZ2U+Pg1lbmRvYmoNMzggMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xl
bmd0aCA0MjI+PnN0cmVhbQ0KSInsVF1v0zAUfY/EfziPA6VZ3EEHj91aVYCGqmFpD8CDk9wmps41
sp0O/j03XUFjK7whXnAky7kf51wf+/pCZ6er9yXamJ1qXUJBbzJVFuUUpXx3qxfnxQznM1U8f1me
QffZCZ7qz9lEnKUSQy2RE1Wosyn0Ijt5zYkCU5osgtkkHMa1XuPKs00+WG4xD3VnE9VpCBR/xOCd
31FfUcC0VOrjkz1NORLoZwfSO6bpbM/0xzKkdmBeb9nfOmpa6onTEcB76XsboDuCGVLnQ8StH1wD
46KHs1tC8kid4S0uvbOMNYWt5ZhjFYwQYGWrSv5G3APYgqrKiiMQcUwypxxvyaYOok5LORaGce17
E2vDQ465s7gscEEtcS4Otke2DSx3o/vKtDxE3FAUxd3AzcYHqY9swM64wVSOUPt+3HmE4QZxaFsJ
tp4jPP8U+J5qgi0AIBPcN+woRImF34jRRjS+Hkaw4oiOjxePj+pXpuNZ/9P/efrfK+N3vXojN5+S
9FmBB2P59YsdX4g3AxNUPj4M04cx+LCWVoJ69elwo5c6+y7AAL3iJSkNCmVuZHN0cmVhbQ1lbmRv
YmoNMzkgMCBvYmoNPDwvQ29udGVudHMgNDAgMCBSL0Nyb3BCb3hbMCAwIDU5NS4yMiA4NDJdL01l
ZGlhQm94WzAgMCA1OTUuMjIgODQyXS9QYXJlbnQgNTggMCBSL1Jlc291cmNlczw8L0V4dEdTdGF0
ZTw8L0dTMCA2NSAwIFI+Pi9Gb250PDwvVFQwIDY0IDAgUj4+L1Byb2NTZXRbL1BERi9UZXh0XT4+
L1JvdGF0ZSAwL1R5cGUvUGFnZT4+DWVuZG9iag00MCAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNv
ZGUvTGVuZ3RoIDExMTk+PnN0cmVhbQ0KSImUllFT4kgQx9+p8jt08XJ6lcQkqKv3pqCCu6xZyOrW
LfswhkbmTGbYycRd99NfzyRgUBCMVZKQoaf71//unrO4sX859OE+b+zHsQ8BxJNG4Ht+CD79lXeH
H7wj+HAUeAfHfgvirLELe/F/DZde+gF9kdBKN/CCVghxp7HbExqVQO12FJtoqK5BHEFfCq6l4uIe
TlUy5RoTXSjM52vgs3zE7A4VhH4QjHbsNr7ZIP672rTcKTyyO73pRhB4AD0xkSpjmj8iDHCCCkVC
+722W7NivwP4ft7+/KN06xZzCiktxNiBvufAlZwykedSONCjxwjVAxe5A216uP6ry0RqXkX0NNox
xiuLtYuJMXz0oM1USuHeO9A8/z1LecI1tKW4p/24FIRD8wlPmH0Y7ZJDo70FlTqHpYsitrSJpYKv
nahJXnZgbJLhctQTlz3qRCp0MREuLXaVnrn+gVOzWyFctntVpE82Md52/C4DP/QtwV781Y0pRvtJ
eUg8uPTMW8vOZojSAjOmWIZEGlZDG+OEk4AIRm6D/FmwlOsnkBPIZ4jJ1GKVekoWHiVP8M48b6DF
ZoY7K60Wmqf8j9FnLwKS8C+pHnLiV4XuH9VCXya1hkG3FbZKEa1g0PXoLSFgyQNVyx3LcQxZkWqe
4ZizNRASmWWFWHicP5E0s9JHgS99XJWelyy+93uVzOG2cOALqbbZR5ZTYWYoNPTG9N9gNjD5vJ5I
kAOcSaUNrA3CKXKzaNg5HwKVfGYNfRvAWSqTh6azJs5lyf5Wd2Y1STWZ0YObkYMurzxz/WCdletE
y3k/eTeXLy+5/CsV1fUl3Q2TqdTagQHdV7X8CZHIDeJ2tAgur+r/DTZGx7WczyVNZaB4AmqOeDOm
X8UrSJUxN1u0XdcP1xnqs62K+xWlqHNTYeoWQpd0FhRKiZQwbKil1qGDKW13wxS3UlrqaSsx9Use
gxqPtwUyGz+6vr8u2CHO9POg2bKfDS7aQRCGFO2ZYiS9MvvNAf4seFkrZVuazz/oypy+ct1NLahd
L2n4xJ5QmYKm/cBs6CxUHJwcn7y3A5GVVuvENKEOZjyZYsqrSdWkHrc6H3PcNppoDcN65y7Xk9x3
e1HUH+1V3puNnfpQ98P3ysu4f3hoxgiVXJH+IRULqrNuqbLoHziFWNEwtjqLlNQykWk5ApGlbkx1
tbkIT2szYO46bfrc91vbS4R+GCx7C8Zd2yWGZuLnApWd9xrFmDq+GdXk+ISnaP1ed2Sw8Zg+UQuY
zgpaUbyLwEe7pvRGe+6ZnSYXiOM7Ntqh6tugQfPDaP/0Jrp4zh5FshrB1sI7CgyLC8VxTEJxIK7S
9trxZxy2xPMyktHOOvV9Gzz7Sbssq+wd6To4PD4kF69NM79aZOkW6Qz2ZpYW2dh8HntvuihZZTa2
EG49XyaU1UeVBYPXN9ufp80QpFbBUg9eXHR05eYUb08glArqqeHLNTQo2L05n/yogJ3Hjf8FGADG
mjihDQplbmRzdHJlYW0NZW5kb2JqDTQxIDAgb2JqDTw8L0NvbnRlbnRzIDQyIDAgUi9Dcm9wQm94
WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJveFswIDAgNTk1LjIyIDg0Ml0vUGFyZW50IDU4IDAgUi9S
ZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9HUzAgNjUgMCBSPj4vRm9udDw8L1RUMCA2NCAwIFI+Pi9Q
cm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3RhdGUgMC9UeXBlL1BhZ2U+Pg1lbmRvYmoNNDIgMCBvYmoN
PDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCA2ODM+PnN0cmVhbQ0KSInkVc9TGjEUvjPj//CG
k3aWNQsC9iiIVmdstxBrHfEQlwekLMk2m3Xkv+9LgC2I1k5n2kuzB7Ikm+99P5J0eOXwfMBgklcO
OWcQAR9XIhayOjB6lr1mO2xBuxWFR8esAXxe2YcD/q1So0EW0R8JzaxFYdSoAz+t7F8oi0ahrZ0a
Mbawan0ew5VW0moj1QROTDKVFhNbGMzXc+CjfsT5Axqosyga7nkY5gD4uxXoEqne8ki/LIOWu+uf
dZsRO7oHuEE1QRPAIAygOxVqZEQA1/RygzmVmxZqFMAVvdMQdELoFGYuVOARPPhWqw4wz6VWcEGE
pLCuGxttdaJT6D2ishCLZCYmCGNt4IuWCb6y1OdCpNIuoI+ZNpakqQZAZYOrO4AzfDCFMAsShB2H
L+ixw34tzZp91Pbst0lWnRtcZzrVE4l5CRm1A7gUagNxuFdibqv7DHxFzGO+bx0T5idrabHQC9oN
IUYzkyon7PNCjjCVinx34vSeLKqRy4Sdoo/JEnNXqq5W1pDApdLD/T7vxsODdf0ETA5jZssQsT/Q
rMUaTao/pqpStJpCcOJCkwozW3Yv9VTl5YDj9yGEgVTKoEymQanZdhj/bXwciWBrP70lxYaDrUaj
Tgp0cIKepOfYC+HMSBwZz7F6VaRWJiK3cJJ8L2QuPYtlGVsK/BR3o3VSncyAL7IlQ+f6q+6uEoIj
eEPWJXhOH37t52UqHBnyrEgX/lT5TRVuo+YRu3erXvDrGifC/pcwkhBuQzcawEUMGfmEFqwRKh+T
0E6pl50Sj0Km4kF6uzI0xJtOGDI2E0bMkfan24cbjrH2Rq27597udiz57Hb+58//XhmvXT03RQAU
CpGG8Kz1njLpLrzLQiFEgUtk/fkcuIvdzq9H96sbsMcrPwQYACXw4H4NCmVuZHN0cmVhbQ1lbmRv
YmoNNDMgMCBvYmoNPDwvQ29udGVudHMgNDQgMCBSL0Nyb3BCb3hbMCAwIDU5NS4yMiA4NDJdL01l
ZGlhQm94WzAgMCA1OTUuMjIgODQyXS9QYXJlbnQgNTggMCBSL1Jlc291cmNlczw8L0V4dEdTdGF0
ZTw8L0dTMCA2NSAwIFI+Pi9Gb250PDwvVFQwIDY0IDAgUj4+L1Byb2NTZXRbL1BERi9UZXh0XT4+
L1JvdGF0ZSAwL1R5cGUvUGFnZT4+DWVuZG9iag00NCAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNv
ZGUvTGVuZ3RoIDgyOD4+c3RyZWFtDQpIiaRWS1PbMBC+Z4b/sEfaIcZ2SGi5pUBpO6XDEHd6KD0o
8joR2JJHkgn8+65kOyGPkoQqF9lSdvd7aOVPSef4ahTCxHSOkySECJKsE4VBGENIv3rWPw0GcDqI
gpMPYQ+SonMI75L7TpcWw4hecNrZjYKoF0Ny0Tn8Ki1qibZ7oVlmoRm3yQ1cKyms0kJOYKj5VFjk
ttJo2j3wQz1iMUYNcRhFdwc+TegSJO+bpHWmeOAzvVrGsCxRpuIJhgHA+ZTJCcJ3NdkQ80UE/87V
YRGsAjtFuP183r1MXd1nUObIDILGggqlVWHAEAahJJRaKO3+4yI2YcpqnAvO/DozwKQLFiwq2ANM
EBGK1BHaFWizLnu0XGnsFkoyorIbhjsBSwhQpvJczZwITKOHWLB7qp17jgxwVZS0kq6AqZNPK2nX
k8dnbwFFQRWQKYjKK1RZBl8oOLGUws1U5KIkk6QoXRmMP0g1yzGdYIG0pyE92I55GMRbiIteD7IM
Z38Gw3CNmxb+ZomIkls0Vlf+bPjoqeKVxz1+hgL1xGVufXcCQlKa9rG3AydtEm/ieZwgOmrnfcrK
LJC7VWVBZWC4KtFNvOXXz6EfbZVrBt8Bb3OeEHJmCGaV50j55by6gbdF+3Qa9GBMBzEFenhhURpc
SZ5Xxu2icn20AtESY1uIWQVEZf0sU0Z9IBMTJ0TkS9CY0ztSFp+WCuyRR8lXqZOmaRwLmhZ+p1HU
TRBSzATN3J+Fbwy9fj/cQ71HYRbqffSnJE2pmZoXGXjOdN1+hDEV7k/BNbmtFiYTmri0M7VJnf0l
H6ZOPASJszYgIUiF4ZVDgFYLDuNc8QfqnEZxwVqm2qR3B8vKD/ZBNwx6W9pCvB+kvdtCdLar1BeY
ewM3ElAINtGsnDqDjxoyojfdKivxR/MeEh2BEZLXIIS7z1m9NBN22iCTrGnGyzKwspzfef9qIJ73
na0+QgeZDqKg28AK+0wVZUoXdQ5SzZ9JN8+0Kub+6Aexu3SdwVatstjS+w/emq7VtId4vT2slrMJ
8fpk9zJ+VUdA54blAayMy6dSuO+qbxUdMRKTPqfi1T3w+4YUhDj+03xoXSadvwIMAEPMwaYNCmVu
ZHN0cmVhbQ1lbmRvYmoNNDUgMCBvYmoNPDwvQ29udGVudHMgNDYgMCBSL0Nyb3BCb3hbMCAwIDU5
NS4yMiA4NDJdL01lZGlhQm94WzAgMCA1OTUuMjIgODQyXS9QYXJlbnQgNTggMCBSL1Jlc291cmNl
czw8L0V4dEdTdGF0ZTw8L0dTMCA2NSAwIFI+Pi9Gb250PDwvVFQwIDY0IDAgUj4+L1Byb2NTZXRb
L1BERi9UZXh0XT4+L1JvdGF0ZSAwL1R5cGUvUGFnZT4+DWVuZG9iag00NiAwIG9iag08PC9GaWx0
ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoIDgwMT4+c3RyZWFtDQpIiaRW226bQBB9t5R/GFmqlFaBAL6k
6pubRFUqtY1sqlZq+rCGwWwCu2hZ4uTvOwvYxsSxTbp+4bKeOXPOzFk++73zLzMHFnnv3PcdcMGP
eq5jOx449KuuRhf2GC7Grj386AzAT3un8N6/71n00nHpQUA7Ldd2Bx74V73TG6FRCdTWlWKRhnpN
/Vv4JgXXUnGxgIkKYq4x0IXCfLUHvstHTOeowHNc9+6kTOOYBP6HOmmVyRuXmfbCoHAS4DosM7IE
gpiJBeXiAnSMkFNuLgUMgYmwfBJxlWvImGILxbIYZFTGL1OXa/WXC3sHsAYM82xiD22A0DBgcdSR
xR51IBVaqRSMareIyXWQTkX5BqpMErk0PDKFJfiU3Uu1rjGQKdWBVJcEx/t0GG5F1s8sZBphXiQJ
avAMVRuaKBQ+ZQmr+eNJYmEU0WtD1E2IQnP9XGu24exGRFKlrIwRFlnCg/LafmPxL0AOXgW5jJ/h
UiqFCWUkpqb+5S38nrbwLbmOy3qEFJbpUQrOgOcgEEMMj1B6C9UKycj2DJZIBkUOdB/LpbknSYqg
EozXjO3o6nLxBnEKM6S95rJF24qZ43ENmhzVsIKaphaqDUtNMLsZ20vTVnkTe3RgMobdquw8EIOu
A9FSNUiY4tEzFLlJOLu6npFrBA/UjeYlU+pVUVdEm2ANTl9Mw0FZp5iSVW7JSmCotVgYlo1ChrfW
sqneQhIbBHNb32YNxg7rymbTS7O3CkQFIwtimCcyeDATkmvaylRYWvvdyXbECJmx9v+Y89mSZaWS
CSNb1ku5seYdJl5Vf0T7NkyItBLUxRrmiILOOucdsEfJu4z9D0KhANuHzJvKntjjA4MxOgpW53kY
HpiHdiOX/UcGQoT3g7gQD/3KFPoCl1Ur0cme9rt39SQkQPik89rUC2W0XIlMUEOek6Hm5i6T2mhN
nK83tkTP82JLif1KmtwGf17MrZZb1lmpaHJvw+k3ZDk1d0oAutn3XkrW+F5eHN9Ev4ozMEOc2NBa
108ZN99aXwuB4J6ZTyyvvQf+3LIFgjf4Wx/k137vnwADAPIyy/gNCmVuZHN0cmVhbQ1lbmRvYmoN
NDcgMCBvYmoNPDwvQ29udGVudHMgNDggMCBSL0Nyb3BCb3hbMCAwIDU5NS4yMiA4NDJdL01lZGlh
Qm94WzAgMCA1OTUuMjIgODQyXS9QYXJlbnQgNTggMCBSL1Jlc291cmNlczw8L0V4dEdTdGF0ZTw8
L0dTMCA2NSAwIFI+Pi9Gb250PDwvVFQwIDY0IDAgUj4+L1Byb2NTZXRbL1BERi9UZXh0XT4+L1Jv
dGF0ZSAwL1R5cGUvUGFnZT4+DWVuZG9iag00OCAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNvZGUv
TGVuZ3RoIDQwOT4+c3RyZWFtDQpIiexUS0/cMBC+R+I/fEeoiLHDbhZxowVVrdSCwBJI0INJJruG
xF45Do9/Xzu7FNjlUThwYnyxxuPvYY/mq0w2vh9xjNtkQ0oOAVklgjOegYc12w1HLMcoF2ywxTch
m2QVa/IiScMhFyFRhMpUMLGZQe4mqz+MJ2fIp7tOVR7zOJQH+GWN9tZpM8aOKybaU+E7R+1dDX7b
K2rOySHjQpyt9DQ8Esgvc9IZU5b3TC/KCHAW2PeTAEdlz6tqFBNlxtSyJ6AfAMXcDhsxoIweUk2+
StWVL6yjtLFGBfUpz18GeSwVkBNCZevaXscHUI4QtKFRF9bdyUJhm2k4KeEt+HD7nuCxtSfkzuwe
2Ybe6XbrFbejRTH/+Qlvtp1vvy535vZbrZyubnvAk0Oc17a4DFglYWq18RHXtF0z9doa6LbtCNr0
1W3ovJg8W4ngc8QQAyhTwtD1v4ohG7B3On9b+y1vlsmWu+Dz+gfLeO6/j7t1kIeqGRZi72aq45D7
2RmCWI+zLVuswemBGhOywZ/51NuTyV8BBgCTQ1fqDQplbmRzdHJlYW0NZW5kb2JqDTQ5IDAgb2Jq
DTw8L0NvbnRlbnRzIDUwIDAgUi9Dcm9wQm94WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJveFswIDAg
NTk1LjIyIDg0Ml0vUGFyZW50IDU4IDAgUi9SZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9HUzAgNjUg
MCBSPj4vRm9udDw8L1RUMCA2NCAwIFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3RhdGUgMC9U
eXBlL1BhZ2U+Pg1lbmRvYmoNNTAgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCA1
MTY+PnN0cmVhbQ0KSInMlE9z0zAQxe+e4Tu8GykkjuU4CfSUlGb6hymYRkyHIRxUW7bVOnKQpYaP
j+wacNLUw4UZ7Itntbvvp7eyTqgzPFt6SEtnSKkHApo4xHM9H559H7/GU3eC6YS4wRtvBLp2ejii
d87ALnrEBiKbOSAuGfmgp07vQmquJNeDU8USjea5piGuCil0oYRMMVdRJjSPtFG8/JWDD8UDX99y
Bd8jZPWilvEqAfqqEX1U8ie1UifG3OisUOVLzOPYapRW5mm7VnEdAz4JiRuDVY/HFevqqM5rFs8N
23JxAATWKoJlkegtUxzzBy4N7+OLyQzDqSi1EpFu1TWM1ZaZvLOG9HEpmExLA/jEIvlt2XeZkOyv
6BdrJvJjlEaWnG2/z7Ia2I2K9Z/ypxbuMh3ufMaLJLEGSN0m+yxZkohcMM3jbsB9vxpS5aZVYzez
jWdpFTsE20br2H2YWZSNPVsxl23KE3pwZB+VKCRGwynCMDg4nHnM7OhYjpCp+3bHK6Z0zsuMrXHO
mc7aaxebciuirI+lSZIiv7eRcIzR9WLXOFFZ9t6OPu4eznPnu95vIfkxXgcBSDAdYRIE5O3OyWlc
3tTGuKwyZnardy3+bWjHT9Yxhv+t/N9hPDeJG9MH12C5i71n8WMjqvvt0kgO0q+uNX8/B19DlnL4
42/Nhbegzk8BBgBqgVBqDQplbmRzdHJlYW0NZW5kb2JqDTUxIDAgb2JqDTw8L0NvbnRlbnRzIDUy
IDAgUi9Dcm9wQm94WzAgMCA1OTUuMjIgODQyXS9NZWRpYUJveFswIDAgNTk1LjIyIDg0Ml0vUGFy
ZW50IDU4IDAgUi9SZXNvdXJjZXM8PC9FeHRHU3RhdGU8PC9HUzAgNjUgMCBSPj4vRm9udDw8L1RU
MCA2NCAwIFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0+Pi9Sb3RhdGUgMC9UeXBlL1BhZ2U+Pg1lbmRv
YmoNNTIgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCA4MD4+c3RyZWFtDQpIiXIK
4dJ3DzZQSC/m0g8JMVAwVAhJ4zI00DMwUjAAQgjL1FzPTMHczFDPxMLAWCEkl0tDQTMki8tAQddQ
z9DYSCHEBSriGsIFEGAAr2MQWw0KZW5kc3RyZWFtDWVuZG9iag01MyAwIG9iag08PC9OdW1zWzAg
NTQgMCBSXT4+DWVuZG9iag01NCAwIG9iag08PC9TL0Q+Pg1lbmRvYmoNNTUgMCBvYmoNPDwvQ291
bnQgMjcvS2lkc1s1NiAwIFIgNTcgMCBSIDU4IDAgUl0vVHlwZS9QYWdlcz4+DWVuZG9iag01NiAw
IG9iag08PC9Db3VudCAxMC9LaWRzWzYzIDAgUiAxIDAgUiAzIDAgUiA1IDAgUiA3IDAgUiA5IDAg
UiAxMSAwIFIgMTMgMCBSIDE1IDAgUiAxNyAwIFJdL1BhcmVudCA1NSAwIFIvVHlwZS9QYWdlcz4+
DWVuZG9iag01NyAwIG9iag08PC9Db3VudCAxMC9LaWRzWzE5IDAgUiAyMSAwIFIgMjMgMCBSIDI1
IDAgUiAyNyAwIFIgMjkgMCBSIDMxIDAgUiAzMyAwIFIgMzUgMCBSIDM3IDAgUl0vUGFyZW50IDU1
IDAgUi9UeXBlL1BhZ2VzPj4NZW5kb2JqDTU4IDAgb2JqDTw8L0NvdW50IDcvS2lkc1szOSAwIFIg
NDEgMCBSIDQzIDAgUiA0NSAwIFIgNDcgMCBSIDQ5IDAgUiA1MSAwIFJdL1BhcmVudCA1NSAwIFIv
VHlwZS9QYWdlcz4+DWVuZG9iag01OSAwIG9iag08PC9MZW5ndGggMzg3My9TdWJ0eXBlL1hNTC9U
eXBlL01ldGFkYXRhPj5zdHJlYW0NCjw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2Vo
aUh6cmVTek5UY3prYzlkIj8+Cjx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6
eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDQuMi4xLWMwNDEgNTIuMzQyOTk2LCAyMDA4LzA1LzA3LTIw
OjQ4OjAwICAgICAgICAiPgogICA8cmRmOlJERiB4bWxuczpyZGY9Imh0dHA6Ly93d3cudzMub3Jn
LzE5OTkvMDIvMjItcmRmLXN5bnRheC1ucyMiPgogICAgICA8cmRmOkRlc2NyaXB0aW9uIHJkZjph
Ym91dD0iIgogICAgICAgICAgICB4bWxuczp4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEu
MC8iPgogICAgICAgICA8eG1wOkNyZWF0ZURhdGU+MjAxMS0xMi0xMlQxMTo1MzozNyswMTowMDwv
eG1wOkNyZWF0ZURhdGU+CiAgICAgICAgIDx4bXA6Q3JlYXRvclRvb2w+QWNyb2JhdCBQREZNYWtl
ciA5LjAgZm9yIFdvcmQ8L3htcDpDcmVhdG9yVG9vbD4KICAgICAgICAgPHhtcDpNb2RpZnlEYXRl
PjIwMTEtMTItMTJUMTE6NTM6MzkrMDE6MDA8L3htcDpNb2RpZnlEYXRlPgogICAgICAgICA8eG1w
Ok1ldGFkYXRhRGF0ZT4yMDExLTEyLTEyVDExOjUzOjM5KzAxOjAwPC94bXA6TWV0YWRhdGFEYXRl
PgogICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJv
dXQ9IiIKICAgICAgICAgICAgeG1sbnM6cGRmPSJodHRwOi8vbnMuYWRvYmUuY29tL3BkZi8xLjMv
Ij4KICAgICAgICAgPHBkZjpQcm9kdWNlcj5BY3JvYmF0IEVsZW1lbnRzIDkuMC4wIChXaW5kb3dz
KTwvcGRmOlByb2R1Y2VyPgogICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgICAgPHJkZjpEZXNj
cmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6ZGM9Imh0dHA6Ly9wdXJsLm9y
Zy9kYy9lbGVtZW50cy8xLjEvIj4KICAgICAgICAgPGRjOmZvcm1hdD5hcHBsaWNhdGlvbi9wZGY8
L2RjOmZvcm1hdD4KICAgICAgICAgPGRjOmNyZWF0b3I+CiAgICAgICAgICAgIDxyZGY6U2VxPgog
ICAgICAgICAgICAgICA8cmRmOmxpPkFMVTwvcmRmOmxpPgogICAgICAgICAgICA8L3JkZjpTZXE+
CiAgICAgICAgIDwvZGM6Y3JlYXRvcj4KICAgICAgICAgPGRjOnRpdGxlPgogICAgICAgICAgICA8
cmRmOkFsdD4KICAgICAgICAgICAgICAgPHJkZjpsaSB4bWw6bGFuZz0ieC1kZWZhdWx0Ij5BdWRp
by9WaWRlbyBUcmFuc3BvcnQgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAgICAgICAgICAg
IFE8L3JkZjpsaT4KICAgICAgICAgICAgPC9yZGY6QWx0PgogICAgICAgICA8L2RjOnRpdGxlPgog
ICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9
IiIKICAgICAgICAgICAgeG1sbnM6eG1wTU09Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9t
bS8iPgogICAgICAgICA8eG1wTU06RG9jdW1lbnRJRD51dWlkOjdiOTE5NzBkLTU1ZWMtNDBmNS04
NWFhLWQzNmUyNDcyZjdhYjwveG1wTU06RG9jdW1lbnRJRD4KICAgICAgICAgPHhtcE1NOkluc3Rh
bmNlSUQ+dXVpZDpjMThmNjZmOS04OTYzLTQwZDAtYmE2Yy0yODYzMWY1MjlhYTc8L3htcE1NOklu
c3RhbmNlSUQ+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICAgICA8cmRmOkRlc2NyaXB0aW9u
IHJkZjphYm91dD0iIgogICAgICAgICAgICB4bWxuczpwZGZ4PSJodHRwOi8vbnMuYWRvYmUuY29t
L3BkZngvMS4zLyI+CiAgICAgICAgIDxwZGZ4OkNvbXBhbnk+QWxjYXRlbC1MdWNlbnQ8L3BkZng6
Q29tcGFueT4KICAgICAgPC9yZGY6RGVzY3JpcHRpb24+CiAgIDwvcmRmOlJERj4KPC94OnhtcG1l
dGE+CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAK
PD94cGFja2V0IGVuZD0idyI/Pg0KZW5kc3RyZWFtDWVuZG9iag02MCAwIG9iag08PC9BdXRob3Io
QUxVKS9Db21wYW55KEFsY2F0ZWwtTHVjZW50KS9DcmVhdGlvbkRhdGUoRDoyMDExMTIxMjExNTMz
NyswMScwMCcpL0NyZWF0b3IoQWNyb2JhdCBQREZNYWtlciA5LjAgZm9yIFdvcmQpL01vZERhdGUo
RDoyMDExMTIxMjExNTMzOSswMScwMCcpL1Byb2R1Y2VyKEFjcm9iYXQgRWxlbWVudHMgOS4wLjAg
XChXaW5kb3dzXCkpL1RpdGxlKEF1ZGlvL1ZpZGVvIFRyYW5zcG9ydCBXb3JraW5nIEdyb3VwICAg
ICAgICAgICAgICAgICAgICAgICAgICAgUSk+Pg1lbmRvYmoNeHJlZg0KMCA2MQ0KMDAwMDAwMDAw
MCA2NTUzNSBmDQowMDAwMDMxNjY5IDAwMDAwIG4NCjAwMDAwMzE4NjQgMDAwMDAgbg0KMDAwMDAz
MzA0MiAwMDAwMCBuDQowMDAwMDMzMjM3IDAwMDAwIG4NCjAwMDAwMzQ0MTEgMDAwMDAgbg0KMDAw
MDAzNDYwNiAwMDAwMCBuDQowMDAwMDM1NjA2IDAwMDAwIG4NCjAwMDAwMzU4MDEgMDAwMDAgbg0K
MDAwMDAzNjI4MiAwMDAwMCBuDQowMDAwMDM2NDc4IDAwMDAwIG4NCjAwMDAwMzc1NDUgMDAwMDAg
bg0KMDAwMDAzNzc0MiAwMDAwMCBuDQowMDAwMDM4NjQwIDAwMDAwIG4NCjAwMDAwMzg4MzcgMDAw
MDAgbg0KMDAwMDA0MDEwOSAwMDAwMCBuDQowMDAwMDQwMzA2IDAwMDAwIG4NCjAwMDAwNDEzNTAg
MDAwMDAgbg0KMDAwMDA0MTU0NyAwMDAwMCBuDQowMDAwMDQxNzYxIDAwMDAwIG4NCjAwMDAwNDE5
NTggMDAwMDAgbg0KMDAwMDA0MzU0MyAwMDAwMCBuDQowMDAwMDQzNzQwIDAwMDAwIG4NCjAwMDAw
NDQ0NzMgMDAwMDAgbg0KMDAwMDA0NDY3MCAwMDAwMCBuDQowMDAwMDQ2MjMzIDAwMDAwIG4NCjAw
MDAwNDY0MzAgMDAwMDAgbg0KMDAwMDA0NzgyOCAwMDAwMCBuDQowMDAwMDQ4MDI1IDAwMDAwIG4N
CjAwMDAwNDkzOTAgMDAwMDAgbg0KMDAwMDA0OTU4NyAwMDAwMCBuDQowMDAwMDUxMDgzIDAwMDAw
IG4NCjAwMDAwNTEyODAgMDAwMDAgbg0KMDAwMDA1MjI1MCAwMDAwMCBuDQowMDAwMDUyNDQ3IDAw
MDAwIG4NCjAwMDAwNTI3OTQgMDAwMDAgbg0KMDAwMDA1Mjk5MSAwMDAwMCBuDQowMDAwMDUzODYz
IDAwMDAwIG4NCjAwMDAwNTQwNjAgMDAwMDAgbg0KMDAwMDA1NDU1MiAwMDAwMCBuDQowMDAwMDU0
NzQ5IDAwMDAwIG4NCjAwMDAwNTU5MzkgMDAwMDAgbg0KMDAwMDA1NjEzNiAwMDAwMCBuDQowMDAw
MDU2ODg5IDAwMDAwIG4NCjAwMDAwNTcwODYgMDAwMDAgbg0KMDAwMDA1Nzk4NCAwMDAwMCBuDQow
MDAwMDU4MTgxIDAwMDAwIG4NCjAwMDAwNTkwNTIgMDAwMDAgbg0KMDAwMDA1OTI0OSAwMDAwMCBu
DQowMDAwMDU5NzI4IDAwMDAwIG4NCjAwMDAwNTk5MjUgMDAwMDAgbg0KMDAwMDA2MDUxMSAwMDAw
MCBuDQowMDAwMDYwNzA4IDAwMDAwIG4NCjAwMDAwNjA4NTcgMDAwMDAgbg0KMDAwMDA2MDg5MyAw
MDAwMCBuDQowMDAwMDYwOTE4IDAwMDAwIG4NCjAwMDAwNjA5ODYgMDAwMDAgbg0KMDAwMDA2MTEx
MiAwMDAwMCBuDQowMDAwMDYxMjQzIDAwMDAwIG4NCjAwMDAwNjEzNTIgMDAwMDAgbg0KMDAwMDA2
NTMwMyAwMDAwMCBuDQp0cmFpbGVyDQo8PC9TaXplIDYxL0lEWzxENjcyNEE5MzE4QTA2N0EzNzQx
NzkyNUI1RjdFOTk3Mj48MUI2NTRFRUNFOTU5NUU0RUEwOEUyOEZCNEMzNjJDNjI+XT4+DQpzdGFy
dHhyZWYNCjExNg0KJSVFT0YNCg==

--_003_5F7BCCF5541B7444830A2288ABBEBC9621620F5344FRMRSSXCHMBSD_--

From kevin.gross@avanw.com  Mon Dec 12 12:23:34 2011
Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2C521F84DA for <avt@ietfa.amsl.com>; Mon, 12 Dec 2011 12:23:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.153
X-Spam-Level: 
X-Spam-Status: No, score=-0.153 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kAuNILLMahFE for <avt@ietfa.amsl.com>; Mon, 12 Dec 2011 12:23:33 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id 03F5A21F84D5 for <avt@ietf.org>; Mon, 12 Dec 2011 12:23:31 -0800 (PST)
Received: (qmail 10070 invoked by uid 0); 12 Dec 2011 20:23:08 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by cpoproxy3.bluehost.com with SMTP; 12 Dec 2011 20:23:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:To:From:Subject:Message-ID:Date:MIME-Version; bh=0TcXsAz5UPZbIlWz3gJsy8k9rzvyou6Cmq+5KZDppcs=;  b=SMBkb+Bg9i0kWme9NO5xL8dBblkeyieH/EZvk7i0hsKLqi5FvjEC3aNR4Iw9MS6Cn3iSSI0Zc4Wrei/HQuy0uM+nnfm0sKsftDmURY1btaBaHAPlZPvFjilbiTdCBfyg;
Received: from mail-ww0-f44.google.com ([74.125.82.44]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1RaCOy-0002wk-2w for avt@ietf.org; Mon, 12 Dec 2011 13:23:08 -0700
Received: by wgbdr13 with SMTP id dr13so9130261wgb.13 for <avt@ietf.org>; Mon, 12 Dec 2011 12:23:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.204.9 with SMTP id fk9mr677697wbb.5.1323721386571; Mon, 12 Dec 2011 12:23:06 -0800 (PST)
Received: by 10.223.102.129 with HTTP; Mon, 12 Dec 2011 12:23:06 -0800 (PST)
Date: Mon, 12 Dec 2011 13:23:06 -0700
Message-ID: <CALw1_Q3XG3jcWFk5F_7fvARX1HLzfvNT=O64kReB-cH2Xqqr_Q@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: avt@ietf.org
Content-Type: multipart/alternative; boundary=000e0cdf903a0738d104b3eae78d
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 74.125.82.44 authed with kevin.gross@avanw.com}
Subject: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 20:23:34 -0000

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

Here are some additional comments on the draft. Most of these are
suggestions for minor improvements. Items 6 and 7 represent significant
technical issues and may require discussion.

1/ Chance all occurrences of "play-out" to "playout".

2/ First line of 1.2 "Currently, most _interactive_ multimedia applications
make use of RTP and RTCP." Streaming applications commonly use HTTP.

3/ Last paragraph in 1.2 As information on RTP packet arrival times and
play-out times can be considered reception quality feedback information,
RTCP _is the appropriate conduit for delivery and playout delay information
for IDMS._" Convert from proposal to standards language.

4/ Second paragraph, section 1.3. Delete "one for the RTCP XR block type
and one for the new RTCP packet type." SDP parameters make the system work
and are not closely associated with these protocols.

5/ Additional paragraph to append to 1.4, "The ETSI TISPAN protocol differs
in that RTCP XR block are used to convey playout and delivery delays as
well as to send synchronization parameters to receivers. In this document,
a new RTCP packet type is defined to convey high-resolution synchronization
parameters to receivers.

6/ Packet Received NTP timestamp and Packet Received RTP timestamp
definitions in section 6 and Packet Received NTP timestamp definition in
section 7. What IDMS really wants to measure is when all data for the
indicated RTP timestamp is available to the rendering application. We'd
therefore like to know the arrival time of the last octet of the last
packet associated with this RTP timestamp. There is difficulty reliably
identifying the last packet. We could defining this as the last packet
before media clock advances but this does not appreciate out-of-order
generation and reordering by the network.

7/ In Packet Presented NTP timestamp definition in section 6, Clarify that
presentation time does not include any intentionally introduced delay.
Discuss presentation estimates. Suggested replacement for the
first sentence of the definition: "This timestamp reflects the wall clock
time at the earliest moment the data contained in the first octet of the
associated RTP packet could be presented to the user if no IDMS-directed
delay were introduced. In some cases, due to additional delays in external
equipment or sound propagation time through air, actual presentation time
to the user may not be accurately knowable. For a comfortable media
experience, it is preferable to delay audio with respect to video than
vise-versa. Pesimistic (longer) assumptions about playout delay should be
used for video and optimistic (shorter) ones for audio."

8/ Clarify use of 0 value in Packet Presented NTP timestamp definition in
section 6. If _no presentation timestamp is available_ then is shall be set
to 0.

9/  Packet Presented NTP timestamp in section 7. "This timestamp reflects
the wall clock time at the reference client at the moment the data
contained in the first octet of the associated RTP packet _should be
presented_ to the user. Change to directive language.

10/ SyncGroupID definition in sections 9 and 10. Remove "in network byte
order" qualifier. This qualifier may cause confusion, is not necessary and
is not applied to attribute definitions in RFC 4566.

11/ Editorial correction and clarification in section 13: "Normally,
the processing and play-out of the same media stream by _similar_ receivers
will take roughly the same amount of time. By synchronizing on packet
arrival times, you may _lose_ some accuracy, but it will be adequate for
many applications,

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org

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

Here are some additional comments on the draft. Most of these are suggestio=
ns for minor improvements. Items 6 and 7 represent significant technical is=
sues and may require discussion.<div><br></div><div>1/ Chance all=A0occurre=
nces=A0of &quot;play-out&quot; to &quot;playout&quot;.</div>
<div><br></div><div>2/ First line of 1.2 &quot;Currently, most _interactive=
_ multimedia applications make use of RTP and RTCP.&quot; Streaming applica=
tions commonly use HTTP.</div><div><br></div><div>3/ Last paragraph in 1.2=
=A0As information on RTP packet=A0arrival times and play-out times can be c=
onsidered reception quality=A0feedback information, RTCP _is the appropriat=
e conduit for delivery and playout delay information for IDMS._&quot; Conve=
rt from proposal to standards language.</div>
<div><br></div><div>4/ Second paragraph, section 1.3. Delete &quot;one for =
the RTCP XR block type and one=A0for the new RTCP packet type.&quot; SDP pa=
rameters make the system work and are not closely associated with these pro=
tocols.</div>
<div><br></div><div>5/ Additional=A0paragraph=A0to append to 1.4, &quot;The=
 ETSI TISPAN protocol differs in that RTCP XR block are used to convey play=
out and delivery delays as well as to send synchronization parameters to re=
ceivers.=A0In this document, a new RTCP packet type is defined to convey hi=
gh-resolution=A0synchronization parameters to receivers.</div>
<div><br></div><div>6/=A0Packet Received NTP timestamp and=A0Packet Receive=
d RTP timestamp definitions in section 6 and Packet Received NTP timestamp =
definition in section 7. What IDMS really wants to measure is when all data=
 for the indicated RTP timestamp is available to the rendering application.=
 We&#39;d therefore like to know the arrival time of the last octet of the =
last packet=A0associated=A0with this RTP timestamp. There is difficulty rel=
iably identifying the last packet. We could defining this as the last packe=
t before media clock advances but this does not=A0appreciate=A0out-of-order=
 generation and reordering by the network.</div>
<div><br></div><div>7/ In Packet Presented NTP timestamp definition in sect=
ion 6,=A0Clarify=A0that presentation time does not include any intentionall=
y introduced delay. Discuss presentation estimates. Suggested replacement f=
or the first=A0sentence=A0of the definition: &quot;This=A0timestamp reflect=
s the=A0wall clock time at the earliest moment the data contained in the fi=
rst octet=A0of the associated RTP packet could be presented to the user if =
no IDMS-directed delay were introduced. In some cases, due to additional de=
lays in external equipment or sound propagation time through air, actual pr=
esentation time to the user may not be=A0accurately=A0knowable. For a comfo=
rtable media experience, it is preferable to delay audio with respect to vi=
deo than vise-versa. Pesimistic (longer) assumptions about playout delay sh=
ould be used for video and optimistic (shorter) ones for audio.&quot;</div>
<div><br></div><div>8/ Clarify use of 0 value in Packet Presented NTP times=
tamp definition in section 6. If _no=A0presentation timestamp is available_=
 then is shall be set to 0.</div><div><br></div><div>9/=A0=A0Packet Present=
ed NTP timestamp in section 7. &quot;This timestamp reflects the=A0wall clo=
ck time at the reference client at the moment=A0the data contained in the f=
irst octet of the associated RTP packet _should be presented_ to=A0the user=
. Change to directive language.</div>
<div><br></div><div>10/ SyncGroupID definition in sections 9 and 10. Remove=
 &quot;in network byte order&quot; qualifier. This qualifier may cause conf=
usion, is not necessary and is not applied to attribute definitions in RFC =
4566.</div>
<div><br></div><div>11/ Editorial correction and clarification in section 1=
3: &quot;Normally, the=A0processing and play-out of the same media stream b=
y _similar_=A0receivers will take roughly the same amount of time. By synch=
ronizing=A0on packet arrival times, you may _lose_ some accuracy, but it wi=
ll be=A0adequate for many applications,</div>
<div><br></div><div>Kevin Gross<br><div>+1-303-447-0517</div><div>Media Net=
work Consultant<br><div>AVA Networks -=A0<a href=3D"http://www.avanw.com/" =
target=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http://www.X192.org" targ=
et=3D"_blank">www.X192.org</a></div>
</div><br>
</div>

--000e0cdf903a0738d104b3eae78d--

From bill.wu@huawei.com  Mon Dec 12 17:55:36 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D28FE21F8A4B; Mon, 12 Dec 2011 17:55:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.726
X-Spam-Level: 
X-Spam-Status: No, score=-5.726 tagged_above=-999 required=5 tests=[AWL=-0.327, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1atruK9p+hQh; Mon, 12 Dec 2011 17:55:34 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0863121F899D; Mon, 12 Dec 2011 17:55:34 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW400034DCIG7@szxga03-in.huawei.com>; Tue, 13 Dec 2011 09:55:30 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW40064FDCB4G@szxga03-in.huawei.com>; Tue, 13 Dec 2011 09:55:30 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFQ00493; Tue, 13 Dec 2011 09:55:18 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 09:55:16 +0800
Received: from w53375q (10.138.41.130) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 09:55:18 +0800
Date: Tue, 13 Dec 2011 09:55:17 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <F0B2A75386B84E639161CACF1AD401B0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 01:55:36 -0000

I am just a little doubt whether mapping RTP component into specific network node is the scope of MONARCH draft
since it was agreed early that the focus of monarch draft is to provide guideline on how to define XRBlock.
But I am fine if nobody has objection to your proposal, i.e., wide scope a little bit to talk about how to map RTP 
monitoring architecture to the network nodes.

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Monday, December 12, 2011 6:33 PM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


Hi Qin,

I'm very aware about all that.
It looks like that you are now agreeing that QoE measurements are CONDITIONAL ("you got a number of IF statements, there might be even more ...").

MONARCH is not talking about such conditions, thus some readers may got the impression that the metrics related to RTP traffic are UNCONDITIONAL (which is not true as you confirmed).

If you go back to my very first email: I did just propose to indicate the conditional aspect. Don't understand why such kind of valuable info would be not in scope of MONARCH. Hm?

Regards,
Albrecht

PS
I did use the notion of a control plane agnostic "RTP-to-PSTN gateway". You did indicate control plane specific gateway types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol specific examples, but it doesn't change the underlying issue.
The SIP side reporting capability based on RFC 6035 allows to report the outlined measurements, but the RFC itself does not specify whether the reported information is meaningful (which is OK because this is not subject of a reporting interface spec, it is rather subject of a network monitoring doc like MONARCH).
QoE measurements would be conditional in both gateway types (because such a gateway is NOT a user device despite the fact of an embedded SIP user agent entity).
Actually I would even question here the condition of "customer knows the original content" in many real network scenarios.



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Montag, 12. Dezember 2011 05:05
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Albrecht:
> My understanding to QoE measurment is:
> The factors that influence the QoE metric include encoding
> system, transport network, access network,home network and end device.
> If the customer(e.g., network operator) doesn't know the
> original content, the QoE metric should be usually measured
> at the user device.
> If the customer knows the original content, the QoE metric
> can be measured either in the network or at the user device.
> Given the growing popularity of connected devices, these
> devices may have different capability corresponding to CPU
> load, processing overhead, storage, batteries.
> If the cusomer want to measure QoE without considering
> connected devices with various capability , the QoE metric
> can be measured at the point between access network and home network.
>
> Regarding the monitoring scenario you mentioned, I am not
> familiar with such scenario with RTP-to-PSTN gateway deployed.
> But I am aware that there are scenarios with SIP to PSTN
> gateway or SIP to H.323 gateway widely deployed,  RFC6035
> defines a new SIP event package, vq-rtcpxr that enable the
> collection and  reporting of metrics that measure quality for
> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
> metric included is measured at the user device and mapped
> into the equivalent SIP vq-rtcpxr parameter since SIP session
> call is established end to end and RTP media stream is
> exchanged directly between one endpoint and the other endpoint.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Saturday, December 10, 2011 12:01 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> How do you explain to a network operator the value of QoE
> measurements by an RTP receiver / RTP monitor component
> located in an RTP-to-PSTN gateway?
>
> This would be a monitoring scenario inline with MONARCH, but
> with valueless QoE results, right?
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Donnerstag, 8. Dezember 2011 03:26
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > You reiterate what you propose for physical entities in the
> > early email.
> > I am still not convicing with that.
> >
> > Since we have RTP components like RTP end system, RTP mixer,
> > RTP media translator, RTP transport translator, RTP monitor
> > specified in RFC3550 can be built into these component as a
> > application. also monitor can be disjointed from these RTP
> > components as a third party monitor. why we need to specify
> > how to map RTP end system into user equipment, RTP translator
> > or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> > border gateway since we have already mapped monitor into
> > different RTP components.
> > How many PE types you can enumerate? why they should be scope
> > of RTP monitoring architecture?
> >
> > Also as specified in MONARCH draft, we have end sytem
> > metrics, transport level metric, transport level metric, they
> > can be measured and collected from the different RTP
> > comoponents specified in RFC3550, RFC5117. Apparently end
> > system metric can only be collected from RTP end system.
> > transport metric is collected from any RTP system in the RTP
> > monitoring architecture, regarding application level metric,
> > apparently they should be measured at the application layer
> > and can not be collected from RTP transport translator, Also
> > RTP transport translator is still a functional entity rather
> > than a physical entity. I am not convincing with what you
> > said about "contradiction", "lead to possible wrong expectations".
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Thursday, December 08, 2011 12:24 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > Qin,
> > that's NOT the point.
> >
> > All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> ENTITIES (FE).
> > e.g.,
> > - the RTP Monitor or RTP receiver FE may be located in
> > different PHYSICAL ENTITIES (PE), e.g.
> >         a1) a user equipment
> >         a2) a RTP-to-PSTN gateway
> >         a3) an IP-to-IP session border gateway (in a
> > back-to-back RTP endsystem topology)
> >         a3) ...
> >
> > - the RTP Monitor may be associated to an RTP transport
> translator ...
> >         b1) an IP-to-IP session border gateway
> >
> > The "RTP monitoring architecture" is IMPACTED by each
> > functional-to-physical mapping because e.g.
> > * QoE related metrics are questionable in case of a2
> > ("despite the fact of a RTP receiver function")
> > * application level metrics at the location of a RTP
> > transport translator are a contradiction in itself
> > * ...
> >
> > Again, it's not really changing the MONARCH draft because in
> > the very majority of scenarios it is correct. However, there
> > are few cases where the MONARCH description would be "too
> > high level", "not fully correct", "lead to possible wrong
> > expectations", ...
> >
> > Regards,
> > Albrecht
> >
> >
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Dienstag, 6. Dezember 2011 07:13
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > If you talk about existing RFC5117 RTP topology components,
> > > this has already been covered by the current version of
> > > draft-ietf-avtcore-monarch.
> > > In most cases, an RTP system using RTCP XR is architecturally
> > > no different from an RTP system which does not use RTCP XR.
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Monday, December 05, 2011 10:48 PM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > Hello Qin,
> > >
> > > to 1) Physical monitoring architecture
> > > Of course consideration of generic physical entities (PE),
> > > not specific to any network reference architectures defined
> > > by SDOs (like your refered entities).
> > > There would be just a few PE types ("given by the limited set
> > > of RTP topology components (RFC 5117)").
> > >
> > > to 2) (RFC 3550) Monitor function
> > > Right, that's a functional entity. The applicability of a
> > > monitor may be limited, dependent on ... (like in P.NAMS).
> > >
> > > to 3) your IMS network example
> > > Don't see the need to refer from MONARCH to a specific
> > > network architecture like IMS.
> > > Please also note that IMS is a functional architecture, not a
> > > physical architecture.
> > >
> > > Regards,
> > > Albrecht
> > >
> > > PS
> > > There are multiple options for adding the "RTP monitoring
> > > architecture" to a functional/physical network architecture:
> > > a) integrated approach: extension of existing functional
> > > entities or/and addition of RTP monitoring architectural
> > > components, extension or/and addition of
> > > signalling/management interfaces for control and
> > > configuration of RTP monitoring services, and reporting
> > > interfaces for measurement data ...
> > > b) overlay approach: separate specification to ...
> > >
> > >
> > > PSS
> > > BTW: there's a discussion paper with regards to the location
> > > of a monitor function in an IMS H.248 gateway entity:
> > > Measurements and statistics in IMS - Use Cases
> > > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > > 8_Kyoto_Japan/Docs/C3-100469.zip
> > > This is just fyi.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > Behalf Of Qin Wu
> > > > Sent: Freitag, 2. Dezember 2011 02:55
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi, Albrecht:
> > > > No offence, I am not really convinced with your proposal on
> > > > physical monitoring architecture.
> > > >  my counterquestion is what does physical monitoring
> > > > architecture looks like in your mind?
> > > > How many components do we have in such physical monitroing
> > > > architecture? what are they?
> > > > Take IMS network architecture as a example, they may have
> > > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > > described in draft-ietf-avtcore-monarch is mapped into
> > > > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > > > should be in the scope of IETF RTP monitoring
> archtiecture draft?
> > > >
> > > > Monitor described in  draft-ietf-avtcore-monarch is well
> > > > defined in the section 3 of RFC3550 as follows:
> > > > "
> > > >
> > > >    Monitor: An application that receives RTCP packets sent by
> > > >       participants in an RTP session, in particular the
> reception
> > > >       reports, and estimates the current quality of service for
> > > >       distribution monitoring, fault diagnosis and long-term
> > > > statistics.
> > > >       The monitor function is likely to be built into the
> > > > application(s)
> > > >       participating in the session, but may also be a separate
> > > >       application that does not otherwise participate and
> > > > does not send
> > > >       or receive the RTP data packets (since they are on
> > a separate
> > > >       port).  These are called third-party monitors.  It is also
> > > >       acceptable for a third-party monitor to receive
> the RTP data
> > > >       packets but not send RTCP packets or otherwise be
> > > counted in the
> > > >       session.
> > > >
> > > > "
> > > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > > implentation specific issue?
> > > > If this issue are really interesting, isn't it a good idea to
> > > > produce another new document to talk about this?
> > > > One good example for this motivation is this draft I like to
> > > > share with you:
> > > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > > y-00#section-4.6
> > > >
> > > > Regards!
> > > > -Qin
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Friday, December 02, 2011 12:20 AM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > My replies below ...
> > > > -Albrecht
> > > >
> > > > > -----Original Message-----
> > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi,
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > My replies below inline,
> > > > > Albrecht
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > > Hi,
> > > > > > ----- Original Message -----
> > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > To: <avt@ietf.org>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > > Subject: [AVTCORE] Types of monitoring
> architectures; RE: I-D
> > > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > >
> > > > > > > Dear All,
> > > > > > >
> > > > > > > there are different types of monitoring architectures,
> > > > > > particularily from perspective of QoE related performance
> > > > > parameters.
> > > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > > >
> > > > > > > Quality of Experience (QoE):
> > > > > > > The overall acceptability of an application or service, as
> > > > > > perceived subjectively by the end-user.
> > > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > > end-to-end system effects (client, terminal, network,
> > > > > > services infrastructure, etc.).
> > > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > > expectations and context.
> > > > > > >
> > > > > > > Important for MONARCH:
> > > > > > > 1st ... perceived by end-user
> > > > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > > > >
> > > > > > > That said, present RTP monitoring architecture in MONARCH
> > > > > > according clause 3 is not specific on the type of monitoring
> > > > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > > > to a terminal/user equipment (UE). This would be an
> > > > > > end-to-end IP network scenario.
> > > > > > >
> > > > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > > > be also located at the edge of an IP network, e.g. in a
> > > > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > > > the non-IP network part.
> > > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > > (I've Cc'd megaco list).
> > > > > > >
> > > > > > > An RTP Sender/Receiver located NOT in the UE
> would question
> > > > > > the value of RTP/RTCP QoE related performance measurements
> > > > > > (because the UE is located outside the RTP domain).
> > > > > > >
> > > > > > > Conclusions:
> > > > > > > - the set of meaningful performance metrics may be
> > > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > > whether in a UE, gateway, ...
> > > > > > > - don't see any impact on transport level metrics
> > > > > > > - ... but the set of meaningful application level metrics
> > > > > > >
> > > > > > > Proposal for MONARCH:
> > > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > > architecture" below clause 3
> > > > > > >
> > > > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > > > >
> > > > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > > > The location of the RTP Sender/Receiver entity may impact
> > > > > > the set of meaningful metrics.
> > > > > > > For instance: application level metrics for QoE related
> > > > > > performance metrics are questionable (or doesn't really make
> > > > > > sense at all) when measured in a network node (terminating
> > > > > > the RTP) instead of the user equipment."
> > > > > > >
> > > > > > > Something like this would help to avoid confusion.
> > > > > > > I even believe that a QoE measurement in a network node
> > > > > > would violate the QoE definition. Would be rather something
> > > > > > like QoE* ("remote QoE"):-(
> > > > > > >
> > > > > > > Such information would improve the MONARCH doc in
> > my opinion.
> > > > > > > Sorry for that late comment.
> > > > > > > Any views?
> > > > > >
> > > > > > [Qin]:
> > > > > > Albrrecht, if you follow ealry list discussion on
> > > > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > > > to position this document was
> > > > > > this daft should focus on guidelines for defining reporting
> > > > > > blocks. That is to say the main purpose of MONARCH draft
> > > > is how to
> > > > > > provide guidelines for the development of new RTCP XR block
> > > > > > types in XRBlock working group.
> > > > >
> > > > > [ABS] ... then the title "monitoring architectures" is
> > misleading.
> > > > > Proposal: keep title, revise scope section on focus
> > > > >
> > > > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > > > not expand scope into IP monitoring architecture.
> > > >
> > > > [ABS] That's wasn't the intent! Did just focus on the key word.
> > > >
> > > > >
> > > > > >
> > > > > > Therefore how and where to collect the metric from RTP
> > > > > > endpoint is not scope of this document, in my opinion. since
> > > > > > you may have many ways to do this and different vendors have
> > > > > > their different appoaches. It will be better to leave this
> > > > > > beyond the scope. But you are right, it will be more
> > > > > > reasonable to measure QoE related performance metric at the
> > > > > > RTP receiver.
> > > > >
> > > > > [ABS] I would disagree. At least your statement should be
> > > > > conditional, sth like
> > > > > "QoE related performance metrics may be measured in a RTP
> > > > > receiver, IF the RTP receiver function is located in user
> > > > > equipment (e.g. IP terminal), because QoE performance metrics
> > > > > are tightly coupled to the point of view of a 'user'.
> > > > > ... IF NOT, then ..."
> > > > >
> > > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > > right term from RTP perspective.
> > > > >
> > > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > > related metric can be placed either at the network or at
> > > the client.
> > > > > So I disagree with what you said.
> > > >
> > > > [ABS] Not convinced at all.
> > > > Guess you are referring to the "mid-point" models, right?
> > > > The usage of such that models depends on "prior knowledge
> > > > ..." information.
> > > > Thus, the applicability is conditional. You may not make such
> > > > a general statement.
> > > >
> > > >
> > > > >
> > > > > Also as I said, how and where to collect the metric from RTP
> > > > >  endpoint is not scope of this document. It depends on the
> > > > > model you are choosing, e.g., four operation modes specified
> > > > > in P.NAMS.
> > > > > Apparently this should not be specified again in RTP
> > > > > monitoring architecture document.
> > > > >
> > > > > >
> > > > > > Another point is it is not clear to me how RTP
> monitoring has
> > > > > > to do with architectureend to end IP network architecture .
> > > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > > Therefore I am quite doubt that we should describe anything
> > > > > > in this document like how
> > > > > > RTP entties is mapped into network entities/nodes at
> > > the IP layer.
> > > > >
> > > > > [ABS] I don't got any problems to talk about architectural
> > > > > framework for monitoring in this document. Such information
> > > > > is required and this is the only IETF AVT doc about it.
> > > > > The solution to this issue is rather simple to me:
> > > > > - split the MONARCH "monitoring architecture" in
> > > > > 1) a functional monitoring architecture (let's call it
> > 'FMA') and
> > > > > 2) a physical monitoring architecture (... 'PMA').
> > > > >
> > > > > - the present MONARCH doc would describe the FMA at the level
> > > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > > topology components according RFC 5117)
> > > > >
> > > > > - there are many options of functional-to-physical mappings,
> > > > > i.e. how a FMA would be mapped on a PMA
> > > > > - the mapping is typically dependent on considered network
> > > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> > networks)
> > > > >
> > > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > > mapping IF all RTP receiver/sender entities would be located
> > > > > in physical IP terminals (UEs)
> > > > > - etc
> > > > >
> > > > > [Qin]: I can understand your point, but you can not do that.
> > > > > Since this document is only focus on *RTP* monitoring
> > > > > architecture, that is what it said in AVTCore milestone:
> > > > > "
> > > > >
> > > > > Goals and Milestones:
> > > > >
> > > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > > Informational
> > > > >
> > > > > "
> > > >
> > > > [ABS] If you go back to my first email on this subject, and
> > > > if you look at my proposal: that's not a lot, nothing which
> > > > violates the charter, goals and milestones.
> > > >
> > > >
> > > > > Also if you really don't see how to map FMA to PMA, you may
> > > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > > As for how to use RTP monitoring architecture or RTP XR
> > > > > Report in the IMS network architecture, you may look at:
> > > > > http://tools.ietf.org/html/rfc6035
> > > >
> > > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > > primarily for physical IP user equipment with embedded RTP
> > > > sender/receiver function and SIP UA function.
> > > > However, the applicability of RFC 6035 is limited for a
> > > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > > located NOT in user equipment. Also the P.NAMS mid-point
> > > > model fails for such a scenario.
> > > >
> > > > > ITU-T H.248.48.
> > > > > But I haven't check the current status of H.248.48.
> > > >
> > > > [ABS] Work is finalized, see
> > > > http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> > > > 11121-TD-PLEN-0419
> > > >
> > > > >
> > > > > >
> > > > > > But as the author of this document, I am interested and open
> > > > > > to other opinions.:-)
> > > > >
> > > > > [ABS] Like to add a further aspect: a "functional monitoring
> > > > > architecture" may be considered as a network overlay,
> > > > > something which adds additional capabilities (here:
> > > > > measurement services, reporting services on top of basic RTP
> > > > > services).
> > > > > Such an overlay concept is nothing new: e.g., the
> > > > > MultiService Forum did define a "Performance Measurement &
> > > > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > > > considered as such.
> > > > >
> > > > > >
> > > > > > > Regards,
> > > > > > > Albrecht
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >> -----Original Message-----
> > > > > > >> From: avt-bounces@ietf.org
> [mailto:avt-bounces@ietf.org] On
> > > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > > >> To: i-d-announce@ietf.org
> > > > > > >> Cc: avt@ietf.org
> > > > > > >> Subject: [AVTCORE] I-D Action:
> > > > draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >>
> > > > > > >> A New Internet-Draft is available from the on-line
> > > > > > >> Internet-Drafts directories. This draft is a work
> > item of the
> > > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > > of the IETF.
> > > > > > >>
> > > > > > >> Title           : Monitoring Architectures for RTP
> > > > > > >> Author(s)       : Qin Wu
> > > > > > >>                           Geoff Hunt
> > > > > > >>                           Philip Arden
> > > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > > >> Pages           : 25
> > > > > > >> Date            : 2011-11-28
> > > > > > >>
> > > > > > >>    This memo proposes an architecture for
> > extending RTCP with
> > > > > > >> a new RTCP
> > > > > > >>    XR (RFC3611) block type to report new metrics
> > > > regarding media
> > > > > > >>    transmission or reception quality, following RTCP
> > > guideline
> > > > > > >>    established in RFC5968.  This memo suggests that a new
> > > > > > block should
> > > > > > >>    contain a single metric or a small number of metrics
> > > > > > relevant to a
> > > > > > >>    single parameter of interest or concern, rather than
> > > > > > containing a
> > > > > > >>    number of metrics which attempt to provide
> full coverage
> > > > > > >> of all those
> > > > > > >>    parameters of concern to a specific application.
> > > > > > Applications may
> > > > > > >>    then "mix and match" to create a set of blocks which
> > > > > > >> covers their set
> > > > > > >>    of concerns.  Where possible, a specific
> block should be
> > > > > > >> designed to
> > > > > > >>    be re-usable across more than one application, for
> > > > > > example, for all
> > > > > > >>    of voice, streaming audio and video.
> > > > > > >>
> > > > > > >>
> > > > > > >> A URL for this Internet-Draft is:
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > > >>
> > > > > > >> This Internet-Draft can be retrieved at:
> > > > > > >>
> > > > > >
> > > >
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >> _______________________________________________
> > > > > > >> Audio/Video Transport Core Maintenance
> > > > > > >> avt@ietf.org
> > > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > > >>
> > > > > > > _______________________________________________
> > > > > > > Audio/Video Transport Core Maintenance
> > > > > > > avt@ietf.org
> > > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > > >
> > > > > =
> > > > _______________________________________________
> > > > Audio/Video Transport Core Maintenance
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > >
> >
>

From bill.wu@huawei.com  Mon Dec 12 18:00:30 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 583091F0C47; Mon, 12 Dec 2011 18:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.714
X-Spam-Level: 
X-Spam-Status: No, score=-5.714 tagged_above=-999 required=5 tests=[AWL=-0.315, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVcDY9CrYn4E; Mon, 12 Dec 2011 18:00:28 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 989D71F0C35; Mon, 12 Dec 2011 18:00:27 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW4009E6DKP1E@szxga03-in.huawei.com>; Tue, 13 Dec 2011 10:00:25 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW4000O8DKOTH@szxga03-in.huawei.com>; Tue, 13 Dec 2011 10:00:25 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFU21489; Tue, 13 Dec 2011 10:00:24 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 10:00:22 +0800
Received: from w53375q (10.138.41.130) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 10:00:20 +0800
Date: Tue, 13 Dec 2011 10:00:19 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <FC7C5040B6114522BE1117B6F79D160A@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5344@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [AVTCORE] Update proposal; RE: [Megaco]  Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 02:00:30 -0000

Hi, Albrecht:
Thank for your proposal. I will how your proposed text can fit into RTP monitoring architecture
and reflect them in the new update. Thanks again.

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Monday, December 12, 2011 6:55 PM
Subject: Update proposal; RE: [Megaco] [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt



Might be more effective by continuing the discussion with a concrete text proposal, see attachments.
Any comments?
Albrecht

> -----Original Message-----
> From: megaco-bounces@ietf.org
> [mailto:megaco-bounces@ietf.org] On Behalf Of Schwarz,
> Albrecht (Albrecht)
> Sent: Montag, 12. Dezember 2011 11:33
> To: Qin Wu; avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] [AVTCORE] Types of monitoring
> architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi Qin,
>
> I'm very aware about all that.
> It looks like that you are now agreeing that QoE measurements
> are CONDITIONAL ("you got a number of IF statements, there
> might be even more ...").
>
> MONARCH is not talking about such conditions, thus some
> readers may got the impression that the metrics related to
> RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
>
> If you go back to my very first email: I did just propose to
> indicate the conditional aspect. Don't understand why such
> kind of valuable info would be not in scope of MONARCH. Hm?
>
> Regards,
> Albrecht
>
> PS
> I did use the notion of a control plane agnostic "RTP-to-PSTN
> gateway". You did indicate control plane specific gateway
> types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such
> signalling protocol specific examples, but it doesn't change
> the underlying issue.
> The SIP side reporting capability based on RFC 6035 allows to
> report the outlined measurements, but the RFC itself does not
> specify whether the reported information is meaningful (which
> is OK because this is not subject of a reporting interface
> spec, it is rather subject of a network monitoring doc like MONARCH).
> QoE measurements would be conditional in both gateway types
> (because such a gateway is NOT a user device despite the fact
> of an embedded SIP user agent entity).
> Actually I would even question here the condition of
> "customer knows the original content" in many real network scenarios.
>
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Montag, 12. Dezember 2011 05:05
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi, Albrecht:
> > My understanding to QoE measurment is:
> > The factors that influence the QoE metric include encoding system,
> > transport network, access network,home network and end device.
> > If the customer(e.g., network operator) doesn't know the original
> > content, the QoE metric should be usually measured at the
> user device.
> > If the customer knows the original content, the QoE metric can be
> > measured either in the network or at the user device.
> > Given the growing popularity of connected devices, these
> devices may
> > have different capability corresponding to CPU load, processing
> > overhead, storage, batteries.
> > If the cusomer want to measure QoE without considering connected
> > devices with various capability , the QoE metric can be measured at
> > the point between access network and home network.
> >
> > Regarding the monitoring scenario you mentioned, I am not familiar
> > with such scenario with RTP-to-PSTN gateway deployed.
> > But I am aware that there are scenarios with SIP to PSTN gateway or
> > SIP to H.323 gateway widely deployed,  RFC6035 defines a
> new SIP event
> > package, vq-rtcpxr that enable the collection and  reporting of
> > metrics that measure quality for RTP sessions. In such
> cases, RTCP XR
> > VOIP metric with QoE metric included is measured at the user device
> > and mapped into the equivalent SIP vq-rtcpxr parameter since SIP
> > session call is established end to end and RTP media stream is
> > exchanged directly between one endpoint and the other endpoint.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Saturday, December 10, 2011 12:01 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > How do you explain to a network operator the value of QoE
> measurements
> > by an RTP receiver / RTP monitor component located in an
> RTP-to-PSTN
> > gateway?
> >
> > This would be a monitoring scenario inline with MONARCH, but with
> > valueless QoE results, right?
> >
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Donnerstag, 8. Dezember 2011 03:26
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > You reiterate what you propose for physical entities in the early
> > > email.
> > > I am still not convicing with that.
> > >
> > > Since we have RTP components like RTP end system, RTP mixer, RTP
> > > media translator, RTP transport translator, RTP monitor
> specified in
> > > RFC3550 can be built into these component as a application. also
> > > monitor can be disjointed from these RTP components as a
> third party
> > > monitor. why we need to specify how to map RTP end system
> into user
> > > equipment, RTP translator or RTP mixer can be mapped into
> RTP-PSTN
> > > gateway, or IP to IP border gateway since we have already mapped
> > > monitor into different RTP components.
> > > How many PE types you can enumerate? why they should be
> scope of RTP
> > > monitoring architecture?
> > >
> > > Also as specified in MONARCH draft, we have end sytem metrics,
> > > transport level metric, transport level metric, they can
> be measured
> > > and collected from the different RTP comoponents specified in
> > > RFC3550, RFC5117. Apparently end system metric can only
> be collected
> > > from RTP end system.
> > > transport metric is collected from any RTP system in the RTP
> > > monitoring architecture, regarding application level metric,
> > > apparently they should be measured at the application
> layer and can
> > > not be collected from RTP transport translator, Also RTP
> transport
> > > translator is still a functional entity rather than a physical
> > > entity. I am not convincing with what you said about
> > > "contradiction", "lead to possible wrong expectations".
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Thursday, December 08, 2011 12:24 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > Qin,
> > > that's NOT the point.
> > >
> > > All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> > ENTITIES (FE).
> > > e.g.,
> > > - the RTP Monitor or RTP receiver FE may be located in different
> > > PHYSICAL ENTITIES (PE), e.g.
> > >         a1) a user equipment
> > >         a2) a RTP-to-PSTN gateway
> > >         a3) an IP-to-IP session border gateway (in a back-to-back
> > > RTP endsystem topology)
> > >         a3) ...
> > >
> > > - the RTP Monitor may be associated to an RTP transport
> > translator ...
> > >         b1) an IP-to-IP session border gateway
> > >
> > > The "RTP monitoring architecture" is IMPACTED by each
> > > functional-to-physical mapping because e.g.
> > > * QoE related metrics are questionable in case of a2
> ("despite the
> > > fact of a RTP receiver function")
> > > * application level metrics at the location of a RTP transport
> > > translator are a contradiction in itself
> > > * ...
> > >
> > > Again, it's not really changing the MONARCH draft because in the
> > > very majority of scenarios it is correct. However, there are few
> > > cases where the MONARCH description would be "too high
> level", "not
> > > fully correct", "lead to possible wrong expectations", ...
> > >
> > > Regards,
> > > Albrecht
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Dienstag, 6. Dezember 2011 07:13
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > If you talk about existing RFC5117 RTP topology
> components, this
> > > > has already been covered by the current version of
> > > > draft-ietf-avtcore-monarch.
> > > > In most cases, an RTP system using RTCP XR is
> architecturally no
> > > > different from an RTP system which does not use RTCP XR.
> > > >
> > > > Regards!
> > > > -Qin
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Monday, December 05, 2011 10:48 PM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > Hello Qin,
> > > >
> > > > to 1) Physical monitoring architecture Of course
> consideration of
> > > > generic physical entities (PE), not specific to any network
> > > > reference architectures defined by SDOs (like your refered
> > > > entities).
> > > > There would be just a few PE types ("given by the
> limited set of
> > > > RTP topology components (RFC 5117)").
> > > >
> > > > to 2) (RFC 3550) Monitor function
> > > > Right, that's a functional entity. The applicability of
> a monitor
> > > > may be limited, dependent on ... (like in P.NAMS).
> > > >
> > > > to 3) your IMS network example
> > > > Don't see the need to refer from MONARCH to a specific network
> > > > architecture like IMS.
> > > > Please also note that IMS is a functional architecture, not a
> > > > physical architecture.
> > > >
> > > > Regards,
> > > > Albrecht
> > > >
> > > > PS
> > > > There are multiple options for adding the "RTP monitoring
> > > > architecture" to a functional/physical network architecture:
> > > > a) integrated approach: extension of existing
> functional entities
> > > > or/and addition of RTP monitoring architectural components,
> > > > extension or/and addition of signalling/management
> interfaces for
> > > > control and configuration of RTP monitoring services, and
> > > > reporting interfaces for measurement data ...
> > > > b) overlay approach: separate specification to ...
> > > >
> > > >
> > > > PSS
> > > > BTW: there's a discussion paper with regards to the
> location of a
> > > > monitor function in an IMS H.248 gateway entity:
> > > > Measurements and statistics in IMS - Use Cases
> > > > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > > > 8_Kyoto_Japan/Docs/C3-100469.zip
> > > > This is just fyi.
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > > Behalf Of Qin Wu
> > > > > Sent: Freitag, 2. Dezember 2011 02:55
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi, Albrecht:
> > > > > No offence, I am not really convinced with your proposal on
> > > > > physical monitoring architecture.
> > > > >  my counterquestion is what does physical monitoring
> > > > > architecture looks like in your mind?
> > > > > How many components do we have in such physical monitroing
> > > > > architecture? what are they?
> > > > > Take IMS network architecture as a example, they may have
> > > > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > > > described in draft-ietf-avtcore-monarch is mapped
> into P-CSCF,
> > > > > S-CSCF, SBC, Media Gateway, Media Gateway Controller
> should be
> > > > > in the scope of IETF RTP monitoring
> > archtiecture draft?
> > > > >
> > > > > Monitor described in  draft-ietf-avtcore-monarch is
> well defined
> > > > > in the section 3 of RFC3550 as follows:
> > > > > "
> > > > >
> > > > >    Monitor: An application that receives RTCP packets sent by
> > > > >       participants in an RTP session, in particular the
> > reception
> > > > >       reports, and estimates the current quality of
> service for
> > > > >       distribution monitoring, fault diagnosis and long-term
> > > > > statistics.
> > > > >       The monitor function is likely to be built into the
> > > > > application(s)
> > > > >       participating in the session, but may also be a separate
> > > > >       application that does not otherwise participate
> and does
> > > > > not send
> > > > >       or receive the RTP data packets (since they are on
> > > a separate
> > > > >       port).  These are called third-party monitors.
> It is also
> > > > >       acceptable for a third-party monitor to receive
> > the RTP data
> > > > >       packets but not send RTCP packets or otherwise be
> > > > counted in the
> > > > >       session.
> > > > >
> > > > > "
> > > > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > > > implentation specific issue?
> > > > > If this issue are really interesting, isn't it a good idea to
> > > > > produce another new document to talk about this?
> > > > > One good example for this motivation is this draft I like to
> > > > > share with you:
> > > > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > > > y-00#section-4.6
> > > > >
> > > > > Regards!
> > > > > -Qin
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Friday, December 02, 2011 12:20 AM
> > > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > My replies below ...
> > > > > -Albrecht
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > > Hi,
> > > > > > ----- Original Message -----
> > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > > > Subject: RE: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > >
> > > > > > My replies below inline,
> > > > > > Albrecht
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: Re: [AVTCORE] Types of monitoring
> > architectures; RE:
> > > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > > >
> > > > > > > Hi,
> > > > > > > ----- Original Message -----
> > > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > > To: <avt@ietf.org>
> > > > > > > Cc: <megaco@ietf.org>
> > > > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > > > Subject: [AVTCORE] Types of monitoring
> > architectures; RE: I-D
> > > > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > > > >
> > > > > > >
> > > > > > > > Dear All,
> > > > > > > >
> > > > > > > > there are different types of monitoring architectures,
> > > > > > > particularily from perspective of QoE related performance
> > > > > > parameters.
> > > > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > > > >
> > > > > > > > Quality of Experience (QoE):
> > > > > > > > The overall acceptability of an application or
> service, as
> > > > > > > perceived subjectively by the end-user.
> > > > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > > > end-to-end system effects (client, terminal, network,
> > > > > > > services infrastructure, etc.).
> > > > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > > > expectations and context.
> > > > > > > >
> > > > > > > > Important for MONARCH:
> > > > > > > > 1st ... perceived by end-user 2nd QoE includes the
> > > > > > > > complete end-to-end sytem effects ...
> > > > > > > >
> > > > > > > > That said, present RTP monitoring architecture
> in MONARCH
> > > > > > > according clause 3 is not specific on the type of
> monitoring
> > > > > > > architecture. For instance, Fig. 1, it is
> possibly supposed
> > > > > > > that the "RTP Sender" and "RTP Receiver" entities
> are equal
> > > > > > > to a terminal/user equipment (UE). This would be an
> > > > > > > end-to-end IP network scenario.
> > > > > > > >
> > > > > > > > However, the "RTP Sender" and "RTP Receiver"
> entities may
> > > > > > > be also located at the edge of an IP network, e.g. in a
> > > > > > > gateway for IP-to-non-IP interworking, i.e. an UE
> located in
> > > > > > > the non-IP network part.
> > > > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > > > (I've Cc'd megaco list).
> > > > > > > >
> > > > > > > > An RTP Sender/Receiver located NOT in the UE
> > would question
> > > > > > > the value of RTP/RTCP QoE related performance
> measurements
> > > > > > > (because the UE is located outside the RTP domain).
> > > > > > > >
> > > > > > > > Conclusions:
> > > > > > > > - the set of meaningful performance metrics may be
> > > > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > > > whether in a UE, gateway, ...
> > > > > > > > - don't see any impact on transport level metrics
> > > > > > > > - ... but the set of meaningful application
> level metrics
> > > > > > > >
> > > > > > > > Proposal for MONARCH:
> > > > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > > > architecture" below clause 3
> > > > > > > >
> > > > > > > > #2: add a sub-clause 3.2 at the end of clause
> 3, sth like
> > > > > > > >
> > > > > > > > "3.2 RTP Sender/Receiver entities located in
> network nodes
> > > > > > > > The location of the RTP Sender/Receiver entity
> may impact
> > > > > > > the set of meaningful metrics.
> > > > > > > > For instance: application level metrics for QoE related
> > > > > > > performance metrics are questionable (or doesn't
> really make
> > > > > > > sense at all) when measured in a network node
> (terminating
> > > > > > > the RTP) instead of the user equipment."
> > > > > > > >
> > > > > > > > Something like this would help to avoid confusion.
> > > > > > > > I even believe that a QoE measurement in a network node
> > > > > > > would violate the QoE definition. Would be rather
> something
> > > > > > > like QoE* ("remote QoE"):-(
> > > > > > > >
> > > > > > > > Such information would improve the MONARCH doc in
> > > my opinion.
> > > > > > > > Sorry for that late comment.
> > > > > > > > Any views?
> > > > > > >
> > > > > > > [Qin]:
> > > > > > > Albrrecht, if you follow ealry list discussion on
> > > > > > > draft-hunt-avt-monarch-01, you will see the rough
> consensus
> > > > > > > to position this document was this daft should focus on
> > > > > > > guidelines for defining reporting blocks. That is
> to say the
> > > > > > > main purpose of MONARCH draft
> > > > > is how to
> > > > > > > provide guidelines for the development of new
> RTCP XR block
> > > > > > > types in XRBlock working group.
> > > > > >
> > > > > > [ABS] ... then the title "monitoring architectures" is
> > > misleading.
> > > > > > Proposal: keep title, revise scope section on focus
> > > > > >
> > > > > > [Qin]: No, the title is *RTP* monitoring
> architecture, we can
> > > > > > not expand scope into IP monitoring architecture.
> > > > >
> > > > > [ABS] That's wasn't the intent! Did just focus on the
> key word.
> > > > >
> > > > > >
> > > > > > >
> > > > > > > Therefore how and where to collect the metric from RTP
> > > > > > > endpoint is not scope of this document, in my
> opinion. since
> > > > > > > you may have many ways to do this and different
> vendors have
> > > > > > > their different appoaches. It will be better to
> leave this
> > > > > > > beyond the scope. But you are right, it will be more
> > > > > > > reasonable to measure QoE related performance
> metric at the
> > > > > > > RTP receiver.
> > > > > >
> > > > > > [ABS] I would disagree. At least your statement should be
> > > > > > conditional, sth like "QoE related performance
> metrics may be
> > > > > > measured in a RTP receiver, IF the RTP receiver function is
> > > > > > located in user equipment (e.g. IP terminal), because QoE
> > > > > > performance metrics are tightly coupled to the
> point of view
> > > > > > of a 'user'.
> > > > > > ... IF NOT, then ..."
> > > > > >
> > > > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > > > right term from RTP perspective.
> > > > > >
> > > > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > > > related metric can be placed either at the network or at
> > > > the client.
> > > > > > So I disagree with what you said.
> > > > >
> > > > > [ABS] Not convinced at all.
> > > > > Guess you are referring to the "mid-point" models, right?
> > > > > The usage of such that models depends on "prior
> knowledge ..."
> > > > > information.
> > > > > Thus, the applicability is conditional. You may not
> make such a
> > > > > general statement.
> > > > >
> > > > >
> > > > > >
> > > > > > Also as I said, how and where to collect the metric
> from RTP
> > > > > > endpoint is not scope of this document. It depends on the
> > > > > > model you are choosing, e.g., four operation modes
> specified
> > > > > > in P.NAMS.
> > > > > > Apparently this should not be specified again in RTP
> > > > > > monitoring architecture document.
> > > > > >
> > > > > > >
> > > > > > > Another point is it is not clear to me how RTP
> > monitoring has
> > > > > > > to do with architectureend to end IP network
> architecture .
> > > > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > > > Therefore I am quite doubt that we should
> describe anything
> > > > > > > in this document like how RTP entties is mapped
> into network
> > > > > > > entities/nodes at
> > > > the IP layer.
> > > > > >
> > > > > > [ABS] I don't got any problems to talk about architectural
> > > > > > framework for monitoring in this document. Such
> information is
> > > > > > required and this is the only IETF AVT doc about it.
> > > > > > The solution to this issue is rather simple to me:
> > > > > > - split the MONARCH "monitoring architecture" in
> > > > > > 1) a functional monitoring architecture (let's call it
> > > 'FMA') and
> > > > > > 2) a physical monitoring architecture (... 'PMA').
> > > > > >
> > > > > > - the present MONARCH doc would describe the FMA at
> the level
> > > > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > > > topology components according RFC 5117)
> > > > > >
> > > > > > - there are many options of functional-to-physical
> mappings,
> > > > > > i.e. how a FMA would be mapped on a PMA
> > > > > > - the mapping is typically dependent on considered network
> > > > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> > > networks)
> > > > > >
> > > > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > > > mapping IF all RTP receiver/sender entities would
> be located
> > > > > > in physical IP terminals (UEs)
> > > > > > - etc
> > > > > >
> > > > > > [Qin]: I can understand your point, but you can not do that.
> > > > > > Since this document is only focus on *RTP* monitoring
> > > > > > architecture, that is what it said in AVTCore milestone:
> > > > > > "
> > > > > >
> > > > > > Goals and Milestones:
> > > > > >
> > > > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > > > Informational
> > > > > >
> > > > > > "
> > > > >
> > > > > [ABS] If you go back to my first email on this
> subject, and if
> > > > > you look at my proposal: that's not a lot, nothing which
> > > > > violates the charter, goals and milestones.
> > > > >
> > > > >
> > > > > > Also if you really don't see how to map FMA to PMA, you may
> > > > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > > > As for how to use RTP monitoring architecture or
> RTP XR Report
> > > > > > in the IMS network architecture, you may look at:
> > > > > > http://tools.ietf.org/html/rfc6035
> > > > >
> > > > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > > > primarily for physical IP user equipment with embedded RTP
> > > > > sender/receiver function and SIP UA function.
> > > > > However, the applicability of RFC 6035 is limited for a
> > > > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > > > located NOT in user equipment. Also the P.NAMS
> mid-point model
> > > > > fails for such a scenario.
> > > > >
> > > > > > ITU-T H.248.48.
> > > > > > But I haven't check the current status of H.248.48.
> > > > >
> > > > > [ABS] Work is finalized, see
> > > > > http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> > > > > 11121-TD-PLEN-0419
> > > > >
> > > > > >
> > > > > > >
> > > > > > > But as the author of this document, I am
> interested and open
> > > > > > > to other opinions.:-)
> > > > > >
> > > > > > [ABS] Like to add a further aspect: a "functional
> monitoring
> > > > > > architecture" may be considered as a network overlay,
> > > > > > something which adds additional capabilities (here:
> > > > > > measurement services, reporting services on top of
> basic RTP
> > > > > > services).
> > > > > > Such an overlay concept is nothing new: e.g., the
> MultiService
> > > > > > Forum did define a "Performance Measurement & Monitoring
> > > > > > (PMM)" overlay network, or IETF RMON may be also
> considered as
> > > > > > such.
> > > > > >
> > > > > > >
> > > > > > > > Regards,
> > > > > > > > Albrecht
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >> -----Original Message-----
> > > > > > > >> From: avt-bounces@ietf.org
> > [mailto:avt-bounces@ietf.org] On
> > > > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > > > >> To: i-d-announce@ietf.org
> > > > > > > >> Cc: avt@ietf.org
> > > > > > > >> Subject: [AVTCORE] I-D Action:
> > > > > draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> A New Internet-Draft is available from the on-line
> > > > > > > >> Internet-Drafts directories. This draft is a work
> > > item of the
> > > > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > > > of the IETF.
> > > > > > > >>
> > > > > > > >> Title           : Monitoring Architectures for RTP
> > > > > > > >> Author(s)       : Qin Wu
> > > > > > > >>                           Geoff Hunt
> > > > > > > >>                           Philip Arden
> > > > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > > > >> Pages           : 25
> > > > > > > >> Date            : 2011-11-28
> > > > > > > >>
> > > > > > > >>    This memo proposes an architecture for
> > > extending RTCP with
> > > > > > > >> a new RTCP
> > > > > > > >>    XR (RFC3611) block type to report new metrics
> > > > > regarding media
> > > > > > > >>    transmission or reception quality, following RTCP
> > > > guideline
> > > > > > > >>    established in RFC5968.  This memo suggests
> that a new
> > > > > > > block should
> > > > > > > >>    contain a single metric or a small number of metrics
> > > > > > > relevant to a
> > > > > > > >>    single parameter of interest or concern, rather than
> > > > > > > containing a
> > > > > > > >>    number of metrics which attempt to provide
> > full coverage
> > > > > > > >> of all those
> > > > > > > >>    parameters of concern to a specific application.
> > > > > > > Applications may
> > > > > > > >>    then "mix and match" to create a set of
> blocks which
> > > > > > > >> covers their set
> > > > > > > >>    of concerns.  Where possible, a specific
> > block should be
> > > > > > > >> designed to
> > > > > > > >>    be re-usable across more than one application, for
> > > > > > > example, for all
> > > > > > > >>    of voice, streaming audio and video.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> A URL for this Internet-Draft is:
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > > > >>
> > > > > > > >> This Internet-Draft can be retrieved at:
> > > > > > > >>
> > > > > > >
> > > > >
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >> _______________________________________________
> > > > > > > >> Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > > > >>
> > > > > > > > _______________________________________________
> > > > > > > > Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > > > >
> > > > > > =
> > > > > _______________________________________________
> > > > > Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > >
> > > >
> > >
> >
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>

From bill.wu@huawei.com  Mon Dec 12 18:15:35 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C1821F8508; Mon, 12 Dec 2011 18:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.702
X-Spam-Level: 
X-Spam-Status: No, score=-5.702 tagged_above=-999 required=5 tests=[AWL=-0.303, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8QIy35A5A1Uw; Mon, 12 Dec 2011 18:15:33 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0F621F8507; Mon, 12 Dec 2011 18:15:33 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW400CNUE9P8P@szxga05-in.huawei.com>; Tue, 13 Dec 2011 10:15:25 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW4005S8E8B13@szxga05-in.huawei.com>; Tue, 13 Dec 2011 10:15:25 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFQ02550; Tue, 13 Dec 2011 10:15:24 +0800
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 10:15:21 +0800
Received: from w53375q (10.138.41.130) by szxeml408-hub.china.huawei.com (10.82.67.95) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 10:15:18 +0800
Date: Tue, 13 Dec 2011 10:15:17 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Colin Perkins <csp@csperkins.org>, "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
Message-id: <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <2BEF8708-58B8-4AEB-B3A6-702F46E58C12@csperkins.org>
Cc: megaco@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 02:15:35 -0000

Hi, Colin:
Thank for your suggestion. Besides Albrecht's proposed text, my additional proposal is to fix application level metric defintion in section 2
OLD text:
"
   Application level metrics

      Metrics relating to QoE related parameters.  These metrics are
      measured at the application level and focus on quality of content
      rather than network parameters. 
"
New text
"
   Application level metrics
 
      Metrics relating to application specific parameters or QoE related parameters. 
     Application specific parameters  are measured at the application level and focus
     on quality of content rather than network performance.  QoE related parameters
     reflect the end-to-end performance at the services level and is ususally measured
     at the user endpoint.
"

Regards!
-Qin
----- Original Message ----- 
From: "Colin Perkins" <csp@csperkins.org>
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
Cc: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>; <megaco@ietf.org>
Sent: Tuesday, December 13, 2011 12:56 AM
Subject: Re: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


Albrecht, Qin,

It doesn't seem controversial that some metrics are only meaningful in some scenarios, or when measured at certain points in a system. I don't see how adding a statement to the monarch draft to recognise that could be problematic. Is there anything else being suggested here?

Colin


On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
> Hi Qin,
> 
> I'm very aware about all that.
> It looks like that you are now agreeing that QoE measurements are CONDITIONAL ("you got a number of IF statements, there might be even more ...").
> 
> MONARCH is not talking about such conditions, thus some readers may got the impression that the metrics related to RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
> 
> If you go back to my very first email: I did just propose to indicate the conditional aspect. Don't understand why such kind of valuable info would be not in scope of MONARCH. Hm?
> 
> Regards,
> Albrecht
> 
> PS
> I did use the notion of a control plane agnostic "RTP-to-PSTN gateway". You did indicate control plane specific gateway types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol specific examples, but it doesn't change the underlying issue.
> The SIP side reporting capability based on RFC 6035 allows to report the outlined measurements, but the RFC itself does not specify whether the reported information is meaningful (which is OK because this is not subject of a reporting interface spec, it is rather subject of a network monitoring doc like MONARCH).
> QoE measurements would be conditional in both gateway types (because such a gateway is NOT a user device despite the fact of an embedded SIP user agent entity).
> Actually I would even question here the condition of "customer knows the original content" in many real network scenarios.
> 
> 
> 
>> -----Original Message-----
>> From: Qin Wu [mailto:bill.wu@huawei.com]
>> Sent: Montag, 12. Dezember 2011 05:05
>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>> Cc: megaco@ietf.org
>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>> 
>> Hi, Albrecht:
>> My understanding to QoE measurment is:
>> The factors that influence the QoE metric include encoding
>> system, transport network, access network,home network and end device.
>> If the customer(e.g., network operator) doesn't know the
>> original content, the QoE metric should be usually measured
>> at the user device.
>> If the customer knows the original content, the QoE metric
>> can be measured either in the network or at the user device.
>> Given the growing popularity of connected devices, these
>> devices may have different capability corresponding to CPU
>> load, processing overhead, storage, batteries.
>> If the cusomer want to measure QoE without considering
>> connected devices with various capability , the QoE metric
>> can be measured at the point between access network and home network.
>> 
>> Regarding the monitoring scenario you mentioned, I am not
>> familiar with such scenario with RTP-to-PSTN gateway deployed.
>> But I am aware that there are scenarios with SIP to PSTN
>> gateway or SIP to H.323 gateway widely deployed,  RFC6035
>> defines a new SIP event package, vq-rtcpxr that enable the
>> collection and  reporting of metrics that measure quality for
>> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
>> metric included is measured at the user device and mapped
>> into the equivalent SIP vq-rtcpxr parameter since SIP session
>> call is established end to end and RTP media stream is
>> exchanged directly between one endpoint and the other endpoint.
>> 
>> Regards!
>> -Qin
>> ----- Original Message -----
>> From: "Schwarz, Albrecht (Albrecht)"
>> <albrecht.schwarz@alcatel-lucent.com>
>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>> Cc: <megaco@ietf.org>
>> Sent: Saturday, December 10, 2011 12:01 AM
>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>> 
>> 
>> How do you explain to a network operator the value of QoE
>> measurements by an RTP receiver / RTP monitor component
>> located in an RTP-to-PSTN gateway?
>> 
>> This would be a monitoring scenario inline with MONARCH, but
>> with valueless QoE results, right?
>> 
>> 
>>> -----Original Message-----
>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>> Sent: Donnerstag, 8. Dezember 2011 03:26
>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>> Cc: megaco@ietf.org
>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>> 
>>> You reiterate what you propose for physical entities in the
>>> early email.
>>> I am still not convicing with that.
>>> 
>>> Since we have RTP components like RTP end system, RTP mixer,
>>> RTP media translator, RTP transport translator, RTP monitor
>>> specified in RFC3550 can be built into these component as a
>>> application. also monitor can be disjointed from these RTP
>>> components as a third party monitor. why we need to specify
>>> how to map RTP end system into user equipment, RTP translator
>>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
>>> border gateway since we have already mapped monitor into
>>> different RTP components.
>>> How many PE types you can enumerate? why they should be scope
>>> of RTP monitoring architecture?
>>> 
>>> Also as specified in MONARCH draft, we have end sytem
>>> metrics, transport level metric, transport level metric, they
>>> can be measured and collected from the different RTP
>>> comoponents specified in RFC3550, RFC5117. Apparently end
>>> system metric can only be collected from RTP end system.
>>> transport metric is collected from any RTP system in the RTP
>>> monitoring architecture, regarding application level metric,
>>> apparently they should be measured at the application layer
>>> and can not be collected from RTP transport translator, Also
>>> RTP transport translator is still a functional entity rather
>>> than a physical entity. I am not convincing with what you
>>> said about "contradiction", "lead to possible wrong expectations".
>>> 
>>> Regards!
>>> -Qin
>>> ----- Original Message -----
>>> From: "Schwarz, Albrecht (Albrecht)"
>>> <albrecht.schwarz@alcatel-lucent.com>
>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>> Cc: <megaco@ietf.org>
>>> Sent: Thursday, December 08, 2011 12:24 AM
>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>> 
>>> 
>>> Qin,
>>> that's NOT the point.
>>> 
>>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
>> ENTITIES (FE).
>>> e.g.,
>>> - the RTP Monitor or RTP receiver FE may be located in
>>> different PHYSICAL ENTITIES (PE), e.g.
>>>        a1) a user equipment
>>>        a2) a RTP-to-PSTN gateway
>>>        a3) an IP-to-IP session border gateway (in a
>>> back-to-back RTP endsystem topology)
>>>        a3) ...
>>> 
>>> - the RTP Monitor may be associated to an RTP transport
>> translator ...
>>>        b1) an IP-to-IP session border gateway
>>> 
>>> The "RTP monitoring architecture" is IMPACTED by each
>>> functional-to-physical mapping because e.g.
>>> * QoE related metrics are questionable in case of a2
>>> ("despite the fact of a RTP receiver function")
>>> * application level metrics at the location of a RTP
>>> transport translator are a contradiction in itself
>>> * ...
>>> 
>>> Again, it's not really changing the MONARCH draft because in
>>> the very majority of scenarios it is correct. However, there
>>> are few cases where the MONARCH description would be "too
>>> high level", "not fully correct", "lead to possible wrong
>>> expectations", ...
>>> 
>>> Regards,
>>> Albrecht
>>> 
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>> Sent: Dienstag, 6. Dezember 2011 07:13
>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>> Cc: megaco@ietf.org
>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>> 
>>>> If you talk about existing RFC5117 RTP topology components,
>>>> this has already been covered by the current version of
>>>> draft-ietf-avtcore-monarch.
>>>> In most cases, an RTP system using RTCP XR is architecturally
>>>> no different from an RTP system which does not use RTCP XR.
>>>> 
>>>> Regards!
>>>> -Qin
>>>> ----- Original Message -----
>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>> Cc: <megaco@ietf.org>
>>>> Sent: Monday, December 05, 2011 10:48 PM
>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>> 
>>>> 
>>>> Hello Qin,
>>>> 
>>>> to 1) Physical monitoring architecture
>>>> Of course consideration of generic physical entities (PE),
>>>> not specific to any network reference architectures defined
>>>> by SDOs (like your refered entities).
>>>> There would be just a few PE types ("given by the limited set
>>>> of RTP topology components (RFC 5117)").
>>>> 
>>>> to 2) (RFC 3550) Monitor function
>>>> Right, that's a functional entity. The applicability of a
>>>> monitor may be limited, dependent on ... (like in P.NAMS).
>>>> 
>>>> to 3) your IMS network example
>>>> Don't see the need to refer from MONARCH to a specific
>>>> network architecture like IMS.
>>>> Please also note that IMS is a functional architecture, not a
>>>> physical architecture.
>>>> 
>>>> Regards,
>>>> Albrecht
>>>> 
>>>> PS
>>>> There are multiple options for adding the "RTP monitoring
>>>> architecture" to a functional/physical network architecture:
>>>> a) integrated approach: extension of existing functional
>>>> entities or/and addition of RTP monitoring architectural
>>>> components, extension or/and addition of
>>>> signalling/management interfaces for control and
>>>> configuration of RTP monitoring services, and reporting
>>>> interfaces for measurement data ...
>>>> b) overlay approach: separate specification to ...
>>>> 
>>>> 
>>>> PSS
>>>> BTW: there's a discussion paper with regards to the location
>>>> of a monitor function in an IMS H.248 gateway entity:
>>>> Measurements and statistics in IMS - Use Cases
>>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
>>>> 8_Kyoto_Japan/Docs/C3-100469.zip
>>>> This is just fyi.
>>>> 
>>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>>>>> Behalf Of Qin Wu
>>>>> Sent: Freitag, 2. Dezember 2011 02:55
>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>> Cc: megaco@ietf.org
>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>> 
>>>>> Hi, Albrecht:
>>>>> No offence, I am not really convinced with your proposal on
>>>>> physical monitoring architecture.
>>>>> my counterquestion is what does physical monitoring
>>>>> architecture looks like in your mind?
>>>>> How many components do we have in such physical monitroing
>>>>> architecture? what are they?
>>>>> Take IMS network architecture as a example, they may have
>>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
>>>>> described in draft-ietf-avtcore-monarch is mapped into
>>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
>>>>> should be in the scope of IETF RTP monitoring
>> archtiecture draft?
>>>>> 
>>>>> Monitor described in  draft-ietf-avtcore-monarch is well
>>>>> defined in the section 3 of RFC3550 as follows:
>>>>> "
>>>>> 
>>>>>   Monitor: An application that receives RTCP packets sent by
>>>>>      participants in an RTP session, in particular the
>> reception
>>>>>      reports, and estimates the current quality of service for
>>>>>      distribution monitoring, fault diagnosis and long-term
>>>>> statistics.
>>>>>      The monitor function is likely to be built into the
>>>>> application(s)
>>>>>      participating in the session, but may also be a separate
>>>>>      application that does not otherwise participate and
>>>>> does not send
>>>>>      or receive the RTP data packets (since they are on
>>> a separate
>>>>>      port).  These are called third-party monitors.  It is also
>>>>>      acceptable for a third-party monitor to receive
>> the RTP data
>>>>>      packets but not send RTCP packets or otherwise be
>>>> counted in the
>>>>>      session.
>>>>> 
>>>>> "
>>>>> Isn't how to implent monitor into IMS netowork archtiecture a
>>>>> implentation specific issue?
>>>>> If this issue are really interesting, isn't it a good idea to
>>>>> produce another new document to talk about this?
>>>>> One good example for this motivation is this draft I like to
>>>>> share with you:
>>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
>>>>> y-00#section-4.6
>>>>> 
>>>>> Regards!
>>>>> -Qin
>>>>> ----- Original Message -----
>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>> Cc: <megaco@ietf.org>
>>>>> Sent: Friday, December 02, 2011 12:20 AM
>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>> 
>>>>> 
>>>>> My replies below ...
>>>>> -Albrecht
>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>> Cc: megaco@ietf.org
>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>> 
>>>>>> Hi,
>>>>>> ----- Original Message -----
>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>> Cc: <megaco@ietf.org>
>>>>>> Sent: Thursday, December 01, 2011 1:24 AM
>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>> 
>>>>>> 
>>>>>> My replies below inline,
>>>>>> Albrecht
>>>>>> 
>>>>>>> -----Original Message-----
>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>> Sent: Mittwoch, 30. November 2011 04:51
>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>> Cc: megaco@ietf.org
>>>>>>> Subject: Re: [AVTCORE] Types of monitoring
>> architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>> 
>>>>>>> Hi,
>>>>>>> ----- Original Message -----
>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>> To: <avt@ietf.org>
>>>>>>> Cc: <megaco@ietf.org>
>>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
>>>>>>> Subject: [AVTCORE] Types of monitoring
>> architectures; RE: I-D
>>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>> 
>>>>>>> 
>>>>>>>> Dear All,
>>>>>>>> 
>>>>>>>> there are different types of monitoring architectures,
>>>>>>> particularily from perspective of QoE related performance
>>>>>> parameters.
>>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
>>>>>>>> 
>>>>>>>> Quality of Experience (QoE):
>>>>>>>> The overall acceptability of an application or service, as
>>>>>>> perceived subjectively by the end-user.
>>>>>>>> NOTE 1 - Quality of experience includes the complete
>>>>>>> end-to-end system effects (client, terminal, network,
>>>>>>> services infrastructure, etc.).
>>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
>>>>>>> expectations and context.
>>>>>>>> 
>>>>>>>> Important for MONARCH:
>>>>>>>> 1st ... perceived by end-user
>>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
>>>>>>>> 
>>>>>>>> That said, present RTP monitoring architecture in MONARCH
>>>>>>> according clause 3 is not specific on the type of monitoring
>>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
>>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
>>>>>>> to a terminal/user equipment (UE). This would be an
>>>>>>> end-to-end IP network scenario.
>>>>>>>> 
>>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
>>>>>>> be also located at the edge of an IP network, e.g. in a
>>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
>>>>>>> the non-IP network part.
>>>>>>>> Note: such scenarios are considered by MEGACO gateways
>>>>>>> (I've Cc'd megaco list).
>>>>>>>> 
>>>>>>>> An RTP Sender/Receiver located NOT in the UE
>> would question
>>>>>>> the value of RTP/RTCP QoE related performance measurements
>>>>>>> (because the UE is located outside the RTP domain).
>>>>>>>> 
>>>>>>>> Conclusions:
>>>>>>>> - the set of meaningful performance metrics may be
>>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
>>>>>>> whether in a UE, gateway, ...
>>>>>>>> - don't see any impact on transport level metrics
>>>>>>>> - ... but the set of meaningful application level metrics
>>>>>>>> 
>>>>>>>> Proposal for MONARCH:
>>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
>>>>>>> architecture" below clause 3
>>>>>>>> 
>>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
>>>>>>>> 
>>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
>>>>>>>> The location of the RTP Sender/Receiver entity may impact
>>>>>>> the set of meaningful metrics.
>>>>>>>> For instance: application level metrics for QoE related
>>>>>>> performance metrics are questionable (or doesn't really make
>>>>>>> sense at all) when measured in a network node (terminating
>>>>>>> the RTP) instead of the user equipment."
>>>>>>>> 
>>>>>>>> Something like this would help to avoid confusion.
>>>>>>>> I even believe that a QoE measurement in a network node
>>>>>>> would violate the QoE definition. Would be rather something
>>>>>>> like QoE* ("remote QoE"):-(
>>>>>>>> 
>>>>>>>> Such information would improve the MONARCH doc in
>>> my opinion.
>>>>>>>> Sorry for that late comment.
>>>>>>>> Any views?
>>>>>>> 
>>>>>>> [Qin]:
>>>>>>> Albrrecht, if you follow ealry list discussion on
>>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
>>>>>>> to position this document was
>>>>>>> this daft should focus on guidelines for defining reporting
>>>>>>> blocks. That is to say the main purpose of MONARCH draft
>>>>> is how to
>>>>>>> provide guidelines for the development of new RTCP XR block
>>>>>>> types in XRBlock working group.
>>>>>> 
>>>>>> [ABS] ... then the title "monitoring architectures" is
>>> misleading.
>>>>>> Proposal: keep title, revise scope section on focus
>>>>>> 
>>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
>>>>>> not expand scope into IP monitoring architecture.
>>>>> 
>>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> Therefore how and where to collect the metric from RTP
>>>>>>> endpoint is not scope of this document, in my opinion. since
>>>>>>> you may have many ways to do this and different vendors have
>>>>>>> their different appoaches. It will be better to leave this
>>>>>>> beyond the scope. But you are right, it will be more
>>>>>>> reasonable to measure QoE related performance metric at the
>>>>>>> RTP receiver.
>>>>>> 
>>>>>> [ABS] I would disagree. At least your statement should be
>>>>>> conditional, sth like
>>>>>> "QoE related performance metrics may be measured in a RTP
>>>>>> receiver, IF the RTP receiver function is located in user
>>>>>> equipment (e.g. IP terminal), because QoE performance metrics
>>>>>> are tightly coupled to the point of view of a 'user'.
>>>>>> ... IF NOT, then ..."
>>>>>> 
>>>>>> [Qin]: I am not sure user equipment or IP terminal is the
>>>>>> right term from RTP perspective.
>>>>>> 
>>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
>>>>>> related metric can be placed either at the network or at
>>>> the client.
>>>>>> So I disagree with what you said.
>>>>> 
>>>>> [ABS] Not convinced at all.
>>>>> Guess you are referring to the "mid-point" models, right?
>>>>> The usage of such that models depends on "prior knowledge
>>>>> ..." information.
>>>>> Thus, the applicability is conditional. You may not make such
>>>>> a general statement.
>>>>> 
>>>>> 
>>>>>> 
>>>>>> Also as I said, how and where to collect the metric from RTP
>>>>>> endpoint is not scope of this document. It depends on the
>>>>>> model you are choosing, e.g., four operation modes specified
>>>>>> in P.NAMS.
>>>>>> Apparently this should not be specified again in RTP
>>>>>> monitoring architecture document.
>>>>>> 
>>>>>>> 
>>>>>>> Another point is it is not clear to me how RTP
>> monitoring has
>>>>>>> to do with architectureend to end IP network architecture .
>>>>>>> this draft mostly focus on discussing RTP level stuff.
>>>>>>> Therefore I am quite doubt that we should describe anything
>>>>>>> in this document like how
>>>>>>> RTP entties is mapped into network entities/nodes at
>>>> the IP layer.
>>>>>> 
>>>>>> [ABS] I don't got any problems to talk about architectural
>>>>>> framework for monitoring in this document. Such information
>>>>>> is required and this is the only IETF AVT doc about it.
>>>>>> The solution to this issue is rather simple to me:
>>>>>> - split the MONARCH "monitoring architecture" in
>>>>>> 1) a functional monitoring architecture (let's call it
>>> 'FMA') and
>>>>>> 2) a physical monitoring architecture (... 'PMA').
>>>>>> 
>>>>>> - the present MONARCH doc would describe the FMA at the level
>>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
>>>>>> topology components according RFC 5117)
>>>>>> 
>>>>>> - there are many options of functional-to-physical mappings,
>>>>>> i.e. how a FMA would be mapped on a PMA
>>>>>> - the mapping is typically dependent on considered network
>>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
>>> networks)
>>>>>> 
>>>>>> - the present MONARCH doc would describe the FMA-to-PMA
>>>>>> mapping IF all RTP receiver/sender entities would be located
>>>>>> in physical IP terminals (UEs)
>>>>>> - etc
>>>>>> 
>>>>>> [Qin]: I can understand your point, but you can not do that.
>>>>>> Since this document is only focus on *RTP* monitoring
>>>>>> architecture, that is what it said in AVTCore milestone:
>>>>>> "
>>>>>> 
>>>>>> Goals and Milestones:
>>>>>> 
>>>>>>  Feb 2011 - Submit Monitoring Architecture for RTP for
>>>>> Informational
>>>>>> 
>>>>>> "
>>>>> 
>>>>> [ABS] If you go back to my first email on this subject, and
>>>>> if you look at my proposal: that's not a lot, nothing which
>>>>> violates the charter, goals and milestones.
>>>>> 
>>>>> 
>>>>>> Also if you really don't see how to map FMA to PMA, you may
>>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
>>>>>> As for how to use RTP monitoring architecture or RTP XR
>>>>>> Report in the IMS network architecture, you may look at:
>>>>>> http://tools.ietf.org/html/rfc6035
>>>>> 
>>>>> [ABS] That's the SIP reporting interface, i.e., applicable
>>>>> primarily for physical IP user equipment with embedded RTP
>>>>> sender/receiver function and SIP UA function.
>>>>> However, the applicability of RFC 6035 is limited for a
>>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
>>>>> located NOT in user equipment. Also the P.NAMS mid-point
>>>>> model fails for such a scenario.
>>>>> 
>>>>>> ITU-T H.248.48.
>>>>>> But I haven't check the current status of H.248.48.
>>>>> 
>>>>> [ABS] Work is finalized, see
>>>>> http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
>>>>> 11121-TD-PLEN-0419
>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> But as the author of this document, I am interested and open
>>>>>>> to other opinions.:-)
>>>>>> 
>>>>>> [ABS] Like to add a further aspect: a "functional monitoring
>>>>>> architecture" may be considered as a network overlay,
>>>>>> something which adds additional capabilities (here:
>>>>>> measurement services, reporting services on top of basic RTP
>>>>>> services).
>>>>>> Such an overlay concept is nothing new: e.g., the
>>>>>> MultiService Forum did define a "Performance Measurement &
>>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
>>>>>> considered as such.
>>>>>> 
>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Albrecht
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: avt-bounces@ietf.org
>> [mailto:avt-bounces@ietf.org] On
>>>>>>>>> Behalf Of internet-drafts@ietf.org
>>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>> Cc: avt@ietf.org
>>>>>>>>> Subject: [AVTCORE] I-D Action:
>>>>> draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>> Internet-Drafts directories. This draft is a work
>>> item of the
>>>>>>>>> Audio/Video Transport Core Maintenance Working Group
>>>>> of the IETF.
>>>>>>>>> 
>>>>>>>>> Title           : Monitoring Architectures for RTP
>>>>>>>>> Author(s)       : Qin Wu
>>>>>>>>>                          Geoff Hunt
>>>>>>>>>                          Philip Arden
>>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> Pages           : 25
>>>>>>>>> Date            : 2011-11-28
>>>>>>>>> 
>>>>>>>>>   This memo proposes an architecture for
>>> extending RTCP with
>>>>>>>>> a new RTCP
>>>>>>>>>   XR (RFC3611) block type to report new metrics
>>>>> regarding media
>>>>>>>>>   transmission or reception quality, following RTCP
>>>> guideline
>>>>>>>>>   established in RFC5968.  This memo suggests that a new
>>>>>>> block should
>>>>>>>>>   contain a single metric or a small number of metrics
>>>>>>> relevant to a
>>>>>>>>>   single parameter of interest or concern, rather than
>>>>>>> containing a
>>>>>>>>>   number of metrics which attempt to provide
>> full coverage
>>>>>>>>> of all those
>>>>>>>>>   parameters of concern to a specific application.
>>>>>>> Applications may
>>>>>>>>>   then "mix and match" to create a set of blocks which
>>>>>>>>> covers their set
>>>>>>>>>   of concerns.  Where possible, a specific
>> block should be
>>>>>>>>> designed to
>>>>>>>>>   be re-usable across more than one application, for
>>>>>>> example, for all
>>>>>>>>>   of voice, streaming audio and video.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>> 
>>>>>>>>> This Internet-Draft can be retrieved at:
>>>>>>>>> 
>>>>>>> 
>>>>> 
>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>> avt@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>> avt@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>> 
>>>>>> =
>>>>> _______________________________________________
>>>>> Audio/Video Transport Core Maintenance
>>>>> avt@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>> 
>>>> 
>>> 
>> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



-- 
Colin Perkins
http://csperkins.org/




From albrecht.schwarz@alcatel-lucent.com  Tue Dec 13 03:16:48 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B28AD21F8876; Tue, 13 Dec 2011 03:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.335
X-Spam-Level: 
X-Spam-Status: No, score=-5.335 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHWgToCgBwmR; Tue, 13 Dec 2011 03:16:46 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id C1D0F21F85FF; Tue, 13 Dec 2011 03:16:45 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pBDBGWPK026461 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 13 Dec 2011 12:16:32 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Tue, 13 Dec 2011 12:16:32 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, Colin Perkins <csp@csperkins.org>
Date: Tue, 13 Dec 2011 12:16:31 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acy5PRkYFRCRYXF7SU232NZnMDRe1gAS1e7g
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F54B6@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <2BEF8708-58B8-4AEB-B3A6-702F46E58C12@csperkins.org> <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
In-Reply-To: <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 11:16:48 -0000

> Albrecht, Qin,
>
> It doesn't seem controversial that some metrics are only
> meaningful in some scenarios, or when measured at certain
> points in a system. I don't see how adding a statement to the
> monarch draft to recognise that could be problematic. Is
> there anything else being suggested here?
>
> Colin

Right.
No, nothing else is suggested.
(Send yesterday also an update proposal with initial text.)

Albrecht



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Dienstag, 13. Dezember 2011 03:15
> To: Colin Perkins; Schwarz, Albrecht (Albrecht)
> Cc: avt@ietf.org; megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Colin:
> Thank for your suggestion. Besides Albrecht's proposed text,
> my additional proposal is to fix application level metric
> defintion in section 2 OLD text:
> "
>    Application level metrics
>
>       Metrics relating to QoE related parameters.  These metrics are
>       measured at the application level and focus on quality
> of content
>       rather than network parameters.
> "
> New text
> "
>    Application level metrics
>
>       Metrics relating to application specific parameters or
> QoE related parameters.
>      Application specific parameters  are measured at the
> application level and focus
>      on quality of content rather than network performance.
> QoE related parameters
>      reflect the end-to-end performance at the services level
> and is ususally measured
>      at the user endpoint.
> "
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Colin Perkins" <csp@csperkins.org>
> To: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> Cc: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>; <megaco@ietf.org>
> Sent: Tuesday, December 13, 2011 12:56 AM
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Albrecht, Qin,
>
> It doesn't seem controversial that some metrics are only
> meaningful in some scenarios, or when measured at certain
> points in a system. I don't see how adding a statement to the
> monarch draft to recognise that could be problematic. Is
> there anything else being suggested here?
>
> Colin
>
>
> On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
> > Hi Qin,
> >
> > I'm very aware about all that.
> > It looks like that you are now agreeing that QoE
> measurements are CONDITIONAL ("you got a number of IF
> statements, there might be even more ...").
> >
> > MONARCH is not talking about such conditions, thus some
> readers may got the impression that the metrics related to
> RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
> >
> > If you go back to my very first email: I did just propose
> to indicate the conditional aspect. Don't understand why such
> kind of valuable info would be not in scope of MONARCH. Hm?
> >
> > Regards,
> > Albrecht
> >
> > PS
> > I did use the notion of a control plane agnostic
> "RTP-to-PSTN gateway". You did indicate control plane
> specific gateway types like SIP-to-PSTN or SIP-to-H.323. Now
> issue to use such signalling protocol specific examples, but
> it doesn't change the underlying issue.
> > The SIP side reporting capability based on RFC 6035 allows
> to report the outlined measurements, but the RFC itself does
> not specify whether the reported information is meaningful
> (which is OK because this is not subject of a reporting
> interface spec, it is rather subject of a network monitoring
> doc like MONARCH).
> > QoE measurements would be conditional in both gateway types
> (because such a gateway is NOT a user device despite the fact
> of an embedded SIP user agent entity).
> > Actually I would even question here the condition of
> "customer knows the original content" in many real network scenarios.
> >
> >
> >
> >> -----Original Message-----
> >> From: Qin Wu [mailto:bill.wu@huawei.com]
> >> Sent: Montag, 12. Dezember 2011 05:05
> >> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >> Cc: megaco@ietf.org
> >> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>
> >> Hi, Albrecht:
> >> My understanding to QoE measurment is:
> >> The factors that influence the QoE metric include encoding
> >> system, transport network, access network,home network and
> end device.
> >> If the customer(e.g., network operator) doesn't know the
> >> original content, the QoE metric should be usually measured
> >> at the user device.
> >> If the customer knows the original content, the QoE metric
> >> can be measured either in the network or at the user device.
> >> Given the growing popularity of connected devices, these
> >> devices may have different capability corresponding to CPU
> >> load, processing overhead, storage, batteries.
> >> If the cusomer want to measure QoE without considering
> >> connected devices with various capability , the QoE metric
> >> can be measured at the point between access network and
> home network.
> >>
> >> Regarding the monitoring scenario you mentioned, I am not
> >> familiar with such scenario with RTP-to-PSTN gateway deployed.
> >> But I am aware that there are scenarios with SIP to PSTN
> >> gateway or SIP to H.323 gateway widely deployed,  RFC6035
> >> defines a new SIP event package, vq-rtcpxr that enable the
> >> collection and  reporting of metrics that measure quality for
> >> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
> >> metric included is measured at the user device and mapped
> >> into the equivalent SIP vq-rtcpxr parameter since SIP session
> >> call is established end to end and RTP media stream is
> >> exchanged directly between one endpoint and the other endpoint.
> >>
> >> Regards!
> >> -Qin
> >> ----- Original Message -----
> >> From: "Schwarz, Albrecht (Albrecht)"
> >> <albrecht.schwarz@alcatel-lucent.com>
> >> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >> Cc: <megaco@ietf.org>
> >> Sent: Saturday, December 10, 2011 12:01 AM
> >> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>
> >>
> >> How do you explain to a network operator the value of QoE
> >> measurements by an RTP receiver / RTP monitor component
> >> located in an RTP-to-PSTN gateway?
> >>
> >> This would be a monitoring scenario inline with MONARCH, but
> >> with valueless QoE results, right?
> >>
> >>
> >>> -----Original Message-----
> >>> From: Qin Wu [mailto:bill.wu@huawei.com]
> >>> Sent: Donnerstag, 8. Dezember 2011 03:26
> >>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>> Cc: megaco@ietf.org
> >>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>
> >>> You reiterate what you propose for physical entities in the
> >>> early email.
> >>> I am still not convicing with that.
> >>>
> >>> Since we have RTP components like RTP end system, RTP mixer,
> >>> RTP media translator, RTP transport translator, RTP monitor
> >>> specified in RFC3550 can be built into these component as a
> >>> application. also monitor can be disjointed from these RTP
> >>> components as a third party monitor. why we need to specify
> >>> how to map RTP end system into user equipment, RTP translator
> >>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> >>> border gateway since we have already mapped monitor into
> >>> different RTP components.
> >>> How many PE types you can enumerate? why they should be scope
> >>> of RTP monitoring architecture?
> >>>
> >>> Also as specified in MONARCH draft, we have end sytem
> >>> metrics, transport level metric, transport level metric, they
> >>> can be measured and collected from the different RTP
> >>> comoponents specified in RFC3550, RFC5117. Apparently end
> >>> system metric can only be collected from RTP end system.
> >>> transport metric is collected from any RTP system in the RTP
> >>> monitoring architecture, regarding application level metric,
> >>> apparently they should be measured at the application layer
> >>> and can not be collected from RTP transport translator, Also
> >>> RTP transport translator is still a functional entity rather
> >>> than a physical entity. I am not convincing with what you
> >>> said about "contradiction", "lead to possible wrong expectations".
> >>>
> >>> Regards!
> >>> -Qin
> >>> ----- Original Message -----
> >>> From: "Schwarz, Albrecht (Albrecht)"
> >>> <albrecht.schwarz@alcatel-lucent.com>
> >>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >>> Cc: <megaco@ietf.org>
> >>> Sent: Thursday, December 08, 2011 12:24 AM
> >>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>
> >>>
> >>> Qin,
> >>> that's NOT the point.
> >>>
> >>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> >> ENTITIES (FE).
> >>> e.g.,
> >>> - the RTP Monitor or RTP receiver FE may be located in
> >>> different PHYSICAL ENTITIES (PE), e.g.
> >>>        a1) a user equipment
> >>>        a2) a RTP-to-PSTN gateway
> >>>        a3) an IP-to-IP session border gateway (in a
> >>> back-to-back RTP endsystem topology)
> >>>        a3) ...
> >>>
> >>> - the RTP Monitor may be associated to an RTP transport
> >> translator ...
> >>>        b1) an IP-to-IP session border gateway
> >>>
> >>> The "RTP monitoring architecture" is IMPACTED by each
> >>> functional-to-physical mapping because e.g.
> >>> * QoE related metrics are questionable in case of a2
> >>> ("despite the fact of a RTP receiver function")
> >>> * application level metrics at the location of a RTP
> >>> transport translator are a contradiction in itself
> >>> * ...
> >>>
> >>> Again, it's not really changing the MONARCH draft because in
> >>> the very majority of scenarios it is correct. However, there
> >>> are few cases where the MONARCH description would be "too
> >>> high level", "not fully correct", "lead to possible wrong
> >>> expectations", ...
> >>>
> >>> Regards,
> >>> Albrecht
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Qin Wu [mailto:bill.wu@huawei.com]
> >>>> Sent: Dienstag, 6. Dezember 2011 07:13
> >>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>>> Cc: megaco@ietf.org
> >>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>
> >>>> If you talk about existing RFC5117 RTP topology components,
> >>>> this has already been covered by the current version of
> >>>> draft-ietf-avtcore-monarch.
> >>>> In most cases, an RTP system using RTCP XR is architecturally
> >>>> no different from an RTP system which does not use RTCP XR.
> >>>>
> >>>> Regards!
> >>>> -Qin
> >>>> ----- Original Message -----
> >>>> From: "Schwarz, Albrecht (Albrecht)"
> >>>> <albrecht.schwarz@alcatel-lucent.com>
> >>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >>>> Cc: <megaco@ietf.org>
> >>>> Sent: Monday, December 05, 2011 10:48 PM
> >>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>
> >>>>
> >>>> Hello Qin,
> >>>>
> >>>> to 1) Physical monitoring architecture
> >>>> Of course consideration of generic physical entities (PE),
> >>>> not specific to any network reference architectures defined
> >>>> by SDOs (like your refered entities).
> >>>> There would be just a few PE types ("given by the limited set
> >>>> of RTP topology components (RFC 5117)").
> >>>>
> >>>> to 2) (RFC 3550) Monitor function
> >>>> Right, that's a functional entity. The applicability of a
> >>>> monitor may be limited, dependent on ... (like in P.NAMS).
> >>>>
> >>>> to 3) your IMS network example
> >>>> Don't see the need to refer from MONARCH to a specific
> >>>> network architecture like IMS.
> >>>> Please also note that IMS is a functional architecture, not a
> >>>> physical architecture.
> >>>>
> >>>> Regards,
> >>>> Albrecht
> >>>>
> >>>> PS
> >>>> There are multiple options for adding the "RTP monitoring
> >>>> architecture" to a functional/physical network architecture:
> >>>> a) integrated approach: extension of existing functional
> >>>> entities or/and addition of RTP monitoring architectural
> >>>> components, extension or/and addition of
> >>>> signalling/management interfaces for control and
> >>>> configuration of RTP monitoring services, and reporting
> >>>> interfaces for measurement data ...
> >>>> b) overlay approach: separate specification to ...
> >>>>
> >>>>
> >>>> PSS
> >>>> BTW: there's a discussion paper with regards to the location
> >>>> of a monitor function in an IMS H.248 gateway entity:
> >>>> Measurements and statistics in IMS - Use Cases
> >>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> >>>> 8_Kyoto_Japan/Docs/C3-100469.zip
> >>>> This is just fyi.
> >>>>
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> >>>>> Behalf Of Qin Wu
> >>>>> Sent: Freitag, 2. Dezember 2011 02:55
> >>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>>>> Cc: megaco@ietf.org
> >>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>
> >>>>> Hi, Albrecht:
> >>>>> No offence, I am not really convinced with your proposal on
> >>>>> physical monitoring architecture.
> >>>>> my counterquestion is what does physical monitoring
> >>>>> architecture looks like in your mind?
> >>>>> How many components do we have in such physical monitroing
> >>>>> architecture? what are they?
> >>>>> Take IMS network architecture as a example, they may have
> >>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> >>>>> described in draft-ietf-avtcore-monarch is mapped into
> >>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> >>>>> should be in the scope of IETF RTP monitoring
> >> archtiecture draft?
> >>>>>
> >>>>> Monitor described in  draft-ietf-avtcore-monarch is well
> >>>>> defined in the section 3 of RFC3550 as follows:
> >>>>> "
> >>>>>
> >>>>>   Monitor: An application that receives RTCP packets sent by
> >>>>>      participants in an RTP session, in particular the
> >> reception
> >>>>>      reports, and estimates the current quality of service for
> >>>>>      distribution monitoring, fault diagnosis and long-term
> >>>>> statistics.
> >>>>>      The monitor function is likely to be built into the
> >>>>> application(s)
> >>>>>      participating in the session, but may also be a separate
> >>>>>      application that does not otherwise participate and
> >>>>> does not send
> >>>>>      or receive the RTP data packets (since they are on
> >>> a separate
> >>>>>      port).  These are called third-party monitors.  It is also
> >>>>>      acceptable for a third-party monitor to receive
> >> the RTP data
> >>>>>      packets but not send RTCP packets or otherwise be
> >>>> counted in the
> >>>>>      session.
> >>>>>
> >>>>> "
> >>>>> Isn't how to implent monitor into IMS netowork archtiecture a
> >>>>> implentation specific issue?
> >>>>> If this issue are really interesting, isn't it a good idea to
> >>>>> produce another new document to talk about this?
> >>>>> One good example for this motivation is this draft I like to
> >>>>> share with you:
> >>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> >>>>> y-00#section-4.6
> >>>>>
> >>>>> Regards!
> >>>>> -Qin
> >>>>> ----- Original Message -----
> >>>>> From: "Schwarz, Albrecht (Albrecht)"
> >>>>> <albrecht.schwarz@alcatel-lucent.com>
> >>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >>>>> Cc: <megaco@ietf.org>
> >>>>> Sent: Friday, December 02, 2011 12:20 AM
> >>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>
> >>>>>
> >>>>> My replies below ...
> >>>>> -Albrecht
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
> >>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
> >>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>>>>> Cc: megaco@ietf.org
> >>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>>
> >>>>>> Hi,
> >>>>>> ----- Original Message -----
> >>>>>> From: "Schwarz, Albrecht (Albrecht)"
> >>>>>> <albrecht.schwarz@alcatel-lucent.com>
> >>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >>>>>> Cc: <megaco@ietf.org>
> >>>>>> Sent: Thursday, December 01, 2011 1:24 AM
> >>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>>
> >>>>>>
> >>>>>> My replies below inline,
> >>>>>> Albrecht
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
> >>>>>>> Sent: Mittwoch, 30. November 2011 04:51
> >>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>>>>>> Cc: megaco@ietf.org
> >>>>>>> Subject: Re: [AVTCORE] Types of monitoring
> >> architectures; RE:
> >>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>> ----- Original Message -----
> >>>>>>> From: "Schwarz, Albrecht (Albrecht)"
> >>>>>>> <albrecht.schwarz@alcatel-lucent.com>
> >>>>>>> To: <avt@ietf.org>
> >>>>>>> Cc: <megaco@ietf.org>
> >>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
> >>>>>>> Subject: [AVTCORE] Types of monitoring
> >> architectures; RE: I-D
> >>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>>>
> >>>>>>>
> >>>>>>>> Dear All,
> >>>>>>>>
> >>>>>>>> there are different types of monitoring architectures,
> >>>>>>> particularily from perspective of QoE related performance
> >>>>>> parameters.
> >>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> >>>>>>>>
> >>>>>>>> Quality of Experience (QoE):
> >>>>>>>> The overall acceptability of an application or service, as
> >>>>>>> perceived subjectively by the end-user.
> >>>>>>>> NOTE 1 - Quality of experience includes the complete
> >>>>>>> end-to-end system effects (client, terminal, network,
> >>>>>>> services infrastructure, etc.).
> >>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
> >>>>>>> expectations and context.
> >>>>>>>>
> >>>>>>>> Important for MONARCH:
> >>>>>>>> 1st ... perceived by end-user
> >>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
> >>>>>>>>
> >>>>>>>> That said, present RTP monitoring architecture in MONARCH
> >>>>>>> according clause 3 is not specific on the type of monitoring
> >>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
> >>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
> >>>>>>> to a terminal/user equipment (UE). This would be an
> >>>>>>> end-to-end IP network scenario.
> >>>>>>>>
> >>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
> >>>>>>> be also located at the edge of an IP network, e.g. in a
> >>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
> >>>>>>> the non-IP network part.
> >>>>>>>> Note: such scenarios are considered by MEGACO gateways
> >>>>>>> (I've Cc'd megaco list).
> >>>>>>>>
> >>>>>>>> An RTP Sender/Receiver located NOT in the UE
> >> would question
> >>>>>>> the value of RTP/RTCP QoE related performance measurements
> >>>>>>> (because the UE is located outside the RTP domain).
> >>>>>>>>
> >>>>>>>> Conclusions:
> >>>>>>>> - the set of meaningful performance metrics may be
> >>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
> >>>>>>> whether in a UE, gateway, ...
> >>>>>>>> - don't see any impact on transport level metrics
> >>>>>>>> - ... but the set of meaningful application level metrics
> >>>>>>>>
> >>>>>>>> Proposal for MONARCH:
> >>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
> >>>>>>> architecture" below clause 3
> >>>>>>>>
> >>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
> >>>>>>>>
> >>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
> >>>>>>>> The location of the RTP Sender/Receiver entity may impact
> >>>>>>> the set of meaningful metrics.
> >>>>>>>> For instance: application level metrics for QoE related
> >>>>>>> performance metrics are questionable (or doesn't really make
> >>>>>>> sense at all) when measured in a network node (terminating
> >>>>>>> the RTP) instead of the user equipment."
> >>>>>>>>
> >>>>>>>> Something like this would help to avoid confusion.
> >>>>>>>> I even believe that a QoE measurement in a network node
> >>>>>>> would violate the QoE definition. Would be rather something
> >>>>>>> like QoE* ("remote QoE"):-(
> >>>>>>>>
> >>>>>>>> Such information would improve the MONARCH doc in
> >>> my opinion.
> >>>>>>>> Sorry for that late comment.
> >>>>>>>> Any views?
> >>>>>>>
> >>>>>>> [Qin]:
> >>>>>>> Albrrecht, if you follow ealry list discussion on
> >>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
> >>>>>>> to position this document was
> >>>>>>> this daft should focus on guidelines for defining reporting
> >>>>>>> blocks. That is to say the main purpose of MONARCH draft
> >>>>> is how to
> >>>>>>> provide guidelines for the development of new RTCP XR block
> >>>>>>> types in XRBlock working group.
> >>>>>>
> >>>>>> [ABS] ... then the title "monitoring architectures" is
> >>> misleading.
> >>>>>> Proposal: keep title, revise scope section on focus
> >>>>>>
> >>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
> >>>>>> not expand scope into IP monitoring architecture.
> >>>>>
> >>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
> >>>>>
> >>>>>>
> >>>>>>>
> >>>>>>> Therefore how and where to collect the metric from RTP
> >>>>>>> endpoint is not scope of this document, in my opinion. since
> >>>>>>> you may have many ways to do this and different vendors have
> >>>>>>> their different appoaches. It will be better to leave this
> >>>>>>> beyond the scope. But you are right, it will be more
> >>>>>>> reasonable to measure QoE related performance metric at the
> >>>>>>> RTP receiver.
> >>>>>>
> >>>>>> [ABS] I would disagree. At least your statement should be
> >>>>>> conditional, sth like
> >>>>>> "QoE related performance metrics may be measured in a RTP
> >>>>>> receiver, IF the RTP receiver function is located in user
> >>>>>> equipment (e.g. IP terminal), because QoE performance metrics
> >>>>>> are tightly coupled to the point of view of a 'user'.
> >>>>>> ... IF NOT, then ..."
> >>>>>>
> >>>>>> [Qin]: I am not sure user equipment or IP terminal is the
> >>>>>> right term from RTP perspective.
> >>>>>>
> >>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
> >>>>>> related metric can be placed either at the network or at
> >>>> the client.
> >>>>>> So I disagree with what you said.
> >>>>>
> >>>>> [ABS] Not convinced at all.
> >>>>> Guess you are referring to the "mid-point" models, right?
> >>>>> The usage of such that models depends on "prior knowledge
> >>>>> ..." information.
> >>>>> Thus, the applicability is conditional. You may not make such
> >>>>> a general statement.
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> Also as I said, how and where to collect the metric from RTP
> >>>>>> endpoint is not scope of this document. It depends on the
> >>>>>> model you are choosing, e.g., four operation modes specified
> >>>>>> in P.NAMS.
> >>>>>> Apparently this should not be specified again in RTP
> >>>>>> monitoring architecture document.
> >>>>>>
> >>>>>>>
> >>>>>>> Another point is it is not clear to me how RTP
> >> monitoring has
> >>>>>>> to do with architectureend to end IP network architecture .
> >>>>>>> this draft mostly focus on discussing RTP level stuff.
> >>>>>>> Therefore I am quite doubt that we should describe anything
> >>>>>>> in this document like how
> >>>>>>> RTP entties is mapped into network entities/nodes at
> >>>> the IP layer.
> >>>>>>
> >>>>>> [ABS] I don't got any problems to talk about architectural
> >>>>>> framework for monitoring in this document. Such information
> >>>>>> is required and this is the only IETF AVT doc about it.
> >>>>>> The solution to this issue is rather simple to me:
> >>>>>> - split the MONARCH "monitoring architecture" in
> >>>>>> 1) a functional monitoring architecture (let's call it
> >>> 'FMA') and
> >>>>>> 2) a physical monitoring architecture (... 'PMA').
> >>>>>>
> >>>>>> - the present MONARCH doc would describe the FMA at the level
> >>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> >>>>>> topology components according RFC 5117)
> >>>>>>
> >>>>>> - there are many options of functional-to-physical mappings,
> >>>>>> i.e. how a FMA would be mapped on a PMA
> >>>>>> - the mapping is typically dependent on considered network
> >>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> >>> networks)
> >>>>>>
> >>>>>> - the present MONARCH doc would describe the FMA-to-PMA
> >>>>>> mapping IF all RTP receiver/sender entities would be located
> >>>>>> in physical IP terminals (UEs)
> >>>>>> - etc
> >>>>>>
> >>>>>> [Qin]: I can understand your point, but you can not do that.
> >>>>>> Since this document is only focus on *RTP* monitoring
> >>>>>> architecture, that is what it said in AVTCore milestone:
> >>>>>> "
> >>>>>>
> >>>>>> Goals and Milestones:
> >>>>>>
> >>>>>>  Feb 2011 - Submit Monitoring Architecture for RTP for
> >>>>> Informational
> >>>>>>
> >>>>>> "
> >>>>>
> >>>>> [ABS] If you go back to my first email on this subject, and
> >>>>> if you look at my proposal: that's not a lot, nothing which
> >>>>> violates the charter, goals and milestones.
> >>>>>
> >>>>>
> >>>>>> Also if you really don't see how to map FMA to PMA, you may
> >>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
> >>>>>> As for how to use RTP monitoring architecture or RTP XR
> >>>>>> Report in the IMS network architecture, you may look at:
> >>>>>> http://tools.ietf.org/html/rfc6035
> >>>>>
> >>>>> [ABS] That's the SIP reporting interface, i.e., applicable
> >>>>> primarily for physical IP user equipment with embedded RTP
> >>>>> sender/receiver function and SIP UA function.
> >>>>> However, the applicability of RFC 6035 is limited for a
> >>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
> >>>>> located NOT in user equipment. Also the P.NAMS mid-point
> >>>>> model fails for such a scenario.
> >>>>>
> >>>>>> ITU-T H.248.48.
> >>>>>> But I haven't check the current status of H.248.48.
> >>>>>
> >>>>> [ABS] Work is finalized, see
> >>>>> http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> >>>>> 11121-TD-PLEN-0419
> >>>>>
> >>>>>>
> >>>>>>>
> >>>>>>> But as the author of this document, I am interested and open
> >>>>>>> to other opinions.:-)
> >>>>>>
> >>>>>> [ABS] Like to add a further aspect: a "functional monitoring
> >>>>>> architecture" may be considered as a network overlay,
> >>>>>> something which adds additional capabilities (here:
> >>>>>> measurement services, reporting services on top of basic RTP
> >>>>>> services).
> >>>>>> Such an overlay concept is nothing new: e.g., the
> >>>>>> MultiService Forum did define a "Performance Measurement &
> >>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
> >>>>>> considered as such.
> >>>>>>
> >>>>>>>
> >>>>>>>> Regards,
> >>>>>>>> Albrecht
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: avt-bounces@ietf.org
> >> [mailto:avt-bounces@ietf.org] On
> >>>>>>>>> Behalf Of internet-drafts@ietf.org
> >>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
> >>>>>>>>> To: i-d-announce@ietf.org
> >>>>>>>>> Cc: avt@ietf.org
> >>>>>>>>> Subject: [AVTCORE] I-D Action:
> >>>>> draft-ietf-avtcore-monarch-08.txt
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> A New Internet-Draft is available from the on-line
> >>>>>>>>> Internet-Drafts directories. This draft is a work
> >>> item of the
> >>>>>>>>> Audio/Video Transport Core Maintenance Working Group
> >>>>> of the IETF.
> >>>>>>>>>
> >>>>>>>>> Title           : Monitoring Architectures for RTP
> >>>>>>>>> Author(s)       : Qin Wu
> >>>>>>>>>                          Geoff Hunt
> >>>>>>>>>                          Philip Arden
> >>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
> >>>>>>>>> Pages           : 25
> >>>>>>>>> Date            : 2011-11-28
> >>>>>>>>>
> >>>>>>>>>   This memo proposes an architecture for
> >>> extending RTCP with
> >>>>>>>>> a new RTCP
> >>>>>>>>>   XR (RFC3611) block type to report new metrics
> >>>>> regarding media
> >>>>>>>>>   transmission or reception quality, following RTCP
> >>>> guideline
> >>>>>>>>>   established in RFC5968.  This memo suggests that a new
> >>>>>>> block should
> >>>>>>>>>   contain a single metric or a small number of metrics
> >>>>>>> relevant to a
> >>>>>>>>>   single parameter of interest or concern, rather than
> >>>>>>> containing a
> >>>>>>>>>   number of metrics which attempt to provide
> >> full coverage
> >>>>>>>>> of all those
> >>>>>>>>>   parameters of concern to a specific application.
> >>>>>>> Applications may
> >>>>>>>>>   then "mix and match" to create a set of blocks which
> >>>>>>>>> covers their set
> >>>>>>>>>   of concerns.  Where possible, a specific
> >> block should be
> >>>>>>>>> designed to
> >>>>>>>>>   be re-usable across more than one application, for
> >>>>>>> example, for all
> >>>>>>>>>   of voice, streaming audio and video.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> A URL for this Internet-Draft is:
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >>>>>>>>>
> >>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
> >>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
> >>>>>>>>>
> >>>>>>>>> This Internet-Draft can be retrieved at:
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> Audio/Video Transport Core Maintenance
> >>>>>>>>> avt@ietf.org
> >>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
> >>>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> Audio/Video Transport Core Maintenance
> >>>>>>>> avt@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/avt
> >>>>>>>
> >>>>>> =3D
> >>>>> _______________________________________________
> >>>>> Audio/Video Transport Core Maintenance
> >>>>> avt@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/avt
> >>>>>
> >>>>
> >>>
> >>
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>
>
>
> --
> Colin Perkins
> http://csperkins.org/
>
>
>
>

From csp@csperkins.org  Tue Dec 13 14:54:48 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8275511E80AE; Tue, 13 Dec 2011 14:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.224
X-Spam-Level: 
X-Spam-Status: No, score=-101.224 tagged_above=-999 required=5 tests=[AWL=1.175, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMtwPJha7Mmt; Tue, 13 Dec 2011 14:54:46 -0800 (PST)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by ietfa.amsl.com (Postfix) with ESMTP id 3971211E809B; Tue, 13 Dec 2011 14:54:46 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.30]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RabFD-0003iy-cz; Tue, 13 Dec 2011 22:54:45 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
X-Priority: 3
In-Reply-To: <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
Date: Tue, 13 Dec 2011 22:54:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <1815848C-FE4C-48A0-8889-565198BEEC74@csperkins.org>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <2BEF8708-58B8-4AEB-B3A6-702F46E58C12@csperkins.org> <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: megaco@ietf.org, avt@ietf.org, "Schwarz, Albrecht \(Albrecht\)" <albrecht.schwarz@alcatel-lucent.com>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 22:54:48 -0000

Qin,

Both this, and Albrecht's suggested additions, look reasonable to me.

Colin



On 13 Dec 2011, at 02:15, Qin Wu wrote:
> Hi, Colin:
> Thank for your suggestion. Besides Albrecht's proposed text, my =
additional proposal is to fix application level metric defintion in =
section 2
> OLD text:
> "
>   Application level metrics
>=20
>      Metrics relating to QoE related parameters.  These metrics are
>      measured at the application level and focus on quality of content
>      rather than network parameters.=20
> "
> New text
> "
>   Application level metrics
>=20
>      Metrics relating to application specific parameters or QoE =
related parameters.=20
>     Application specific parameters  are measured at the application =
level and focus
>     on quality of content rather than network performance.  QoE =
related parameters
>     reflect the end-to-end performance at the services level and is =
ususally measured
>     at the user endpoint.
> "
>=20
> Regards!
> -Qin
> ----- Original Message -----=20
> From: "Colin Perkins" <csp@csperkins.org>
> To: "Schwarz, Albrecht (Albrecht)" =
<albrecht.schwarz@alcatel-lucent.com>
> Cc: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>; <megaco@ietf.org>
> Sent: Tuesday, December 13, 2011 12:56 AM
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE: I-D =
Action: draft-ietf-avtcore-monarch-08.txt
>=20
>=20
> Albrecht, Qin,
>=20
> It doesn't seem controversial that some metrics are only meaningful in =
some scenarios, or when measured at certain points in a system. I don't =
see how adding a statement to the monarch draft to recognise that could =
be problematic. Is there anything else being suggested here?
>=20
> Colin
>=20
>=20
> On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
>> Hi Qin,
>>=20
>> I'm very aware about all that.
>> It looks like that you are now agreeing that QoE measurements are =
CONDITIONAL ("you got a number of IF statements, there might be even =
more ...").
>>=20
>> MONARCH is not talking about such conditions, thus some readers may =
got the impression that the metrics related to RTP traffic are =
UNCONDITIONAL (which is not true as you confirmed).
>>=20
>> If you go back to my very first email: I did just propose to indicate =
the conditional aspect. Don't understand why such kind of valuable info =
would be not in scope of MONARCH. Hm?
>>=20
>> Regards,
>> Albrecht
>>=20
>> PS
>> I did use the notion of a control plane agnostic "RTP-to-PSTN =
gateway". You did indicate control plane specific gateway types like =
SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol =
specific examples, but it doesn't change the underlying issue.
>> The SIP side reporting capability based on RFC 6035 allows to report =
the outlined measurements, but the RFC itself does not specify whether =
the reported information is meaningful (which is OK because this is not =
subject of a reporting interface spec, it is rather subject of a network =
monitoring doc like MONARCH).
>> QoE measurements would be conditional in both gateway types (because =
such a gateway is NOT a user device despite the fact of an embedded SIP =
user agent entity).
>> Actually I would even question here the condition of "customer knows =
the original content" in many real network scenarios.
>>=20
>>=20
>>=20
>>> -----Original Message-----
>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>> Sent: Montag, 12. Dezember 2011 05:05
>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>> Cc: megaco@ietf.org
>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>=20
>>> Hi, Albrecht:
>>> My understanding to QoE measurment is:
>>> The factors that influence the QoE metric include encoding
>>> system, transport network, access network,home network and end =
device.
>>> If the customer(e.g., network operator) doesn't know the
>>> original content, the QoE metric should be usually measured
>>> at the user device.
>>> If the customer knows the original content, the QoE metric
>>> can be measured either in the network or at the user device.
>>> Given the growing popularity of connected devices, these
>>> devices may have different capability corresponding to CPU
>>> load, processing overhead, storage, batteries.
>>> If the cusomer want to measure QoE without considering
>>> connected devices with various capability , the QoE metric
>>> can be measured at the point between access network and home =
network.
>>>=20
>>> Regarding the monitoring scenario you mentioned, I am not
>>> familiar with such scenario with RTP-to-PSTN gateway deployed.
>>> But I am aware that there are scenarios with SIP to PSTN
>>> gateway or SIP to H.323 gateway widely deployed,  RFC6035
>>> defines a new SIP event package, vq-rtcpxr that enable the
>>> collection and  reporting of metrics that measure quality for
>>> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
>>> metric included is measured at the user device and mapped
>>> into the equivalent SIP vq-rtcpxr parameter since SIP session
>>> call is established end to end and RTP media stream is
>>> exchanged directly between one endpoint and the other endpoint.
>>>=20
>>> Regards!
>>> -Qin
>>> ----- Original Message -----
>>> From: "Schwarz, Albrecht (Albrecht)"
>>> <albrecht.schwarz@alcatel-lucent.com>
>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>> Cc: <megaco@ietf.org>
>>> Sent: Saturday, December 10, 2011 12:01 AM
>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>=20
>>>=20
>>> How do you explain to a network operator the value of QoE
>>> measurements by an RTP receiver / RTP monitor component
>>> located in an RTP-to-PSTN gateway?
>>>=20
>>> This would be a monitoring scenario inline with MONARCH, but
>>> with valueless QoE results, right?
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>> Sent: Donnerstag, 8. Dezember 2011 03:26
>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>> Cc: megaco@ietf.org
>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>=20
>>>> You reiterate what you propose for physical entities in the
>>>> early email.
>>>> I am still not convicing with that.
>>>>=20
>>>> Since we have RTP components like RTP end system, RTP mixer,
>>>> RTP media translator, RTP transport translator, RTP monitor
>>>> specified in RFC3550 can be built into these component as a
>>>> application. also monitor can be disjointed from these RTP
>>>> components as a third party monitor. why we need to specify
>>>> how to map RTP end system into user equipment, RTP translator
>>>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
>>>> border gateway since we have already mapped monitor into
>>>> different RTP components.
>>>> How many PE types you can enumerate? why they should be scope
>>>> of RTP monitoring architecture?
>>>>=20
>>>> Also as specified in MONARCH draft, we have end sytem
>>>> metrics, transport level metric, transport level metric, they
>>>> can be measured and collected from the different RTP
>>>> comoponents specified in RFC3550, RFC5117. Apparently end
>>>> system metric can only be collected from RTP end system.
>>>> transport metric is collected from any RTP system in the RTP
>>>> monitoring architecture, regarding application level metric,
>>>> apparently they should be measured at the application layer
>>>> and can not be collected from RTP transport translator, Also
>>>> RTP transport translator is still a functional entity rather
>>>> than a physical entity. I am not convincing with what you
>>>> said about "contradiction", "lead to possible wrong expectations".
>>>>=20
>>>> Regards!
>>>> -Qin
>>>> ----- Original Message -----
>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>> Cc: <megaco@ietf.org>
>>>> Sent: Thursday, December 08, 2011 12:24 AM
>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>=20
>>>>=20
>>>> Qin,
>>>> that's NOT the point.
>>>>=20
>>>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
>>> ENTITIES (FE).
>>>> e.g.,
>>>> - the RTP Monitor or RTP receiver FE may be located in
>>>> different PHYSICAL ENTITIES (PE), e.g.
>>>>       a1) a user equipment
>>>>       a2) a RTP-to-PSTN gateway
>>>>       a3) an IP-to-IP session border gateway (in a
>>>> back-to-back RTP endsystem topology)
>>>>       a3) ...
>>>>=20
>>>> - the RTP Monitor may be associated to an RTP transport
>>> translator ...
>>>>       b1) an IP-to-IP session border gateway
>>>>=20
>>>> The "RTP monitoring architecture" is IMPACTED by each
>>>> functional-to-physical mapping because e.g.
>>>> * QoE related metrics are questionable in case of a2
>>>> ("despite the fact of a RTP receiver function")
>>>> * application level metrics at the location of a RTP
>>>> transport translator are a contradiction in itself
>>>> * ...
>>>>=20
>>>> Again, it's not really changing the MONARCH draft because in
>>>> the very majority of scenarios it is correct. However, there
>>>> are few cases where the MONARCH description would be "too
>>>> high level", "not fully correct", "lead to possible wrong
>>>> expectations", ...
>>>>=20
>>>> Regards,
>>>> Albrecht
>>>>=20
>>>>=20
>>>>=20
>>>>> -----Original Message-----
>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>> Sent: Dienstag, 6. Dezember 2011 07:13
>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>> Cc: megaco@ietf.org
>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>=20
>>>>> If you talk about existing RFC5117 RTP topology components,
>>>>> this has already been covered by the current version of
>>>>> draft-ietf-avtcore-monarch.
>>>>> In most cases, an RTP system using RTCP XR is architecturally
>>>>> no different from an RTP system which does not use RTCP XR.
>>>>>=20
>>>>> Regards!
>>>>> -Qin
>>>>> ----- Original Message -----
>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>> Cc: <megaco@ietf.org>
>>>>> Sent: Monday, December 05, 2011 10:48 PM
>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>=20
>>>>>=20
>>>>> Hello Qin,
>>>>>=20
>>>>> to 1) Physical monitoring architecture
>>>>> Of course consideration of generic physical entities (PE),
>>>>> not specific to any network reference architectures defined
>>>>> by SDOs (like your refered entities).
>>>>> There would be just a few PE types ("given by the limited set
>>>>> of RTP topology components (RFC 5117)").
>>>>>=20
>>>>> to 2) (RFC 3550) Monitor function
>>>>> Right, that's a functional entity. The applicability of a
>>>>> monitor may be limited, dependent on ... (like in P.NAMS).
>>>>>=20
>>>>> to 3) your IMS network example
>>>>> Don't see the need to refer from MONARCH to a specific
>>>>> network architecture like IMS.
>>>>> Please also note that IMS is a functional architecture, not a
>>>>> physical architecture.
>>>>>=20
>>>>> Regards,
>>>>> Albrecht
>>>>>=20
>>>>> PS
>>>>> There are multiple options for adding the "RTP monitoring
>>>>> architecture" to a functional/physical network architecture:
>>>>> a) integrated approach: extension of existing functional
>>>>> entities or/and addition of RTP monitoring architectural
>>>>> components, extension or/and addition of
>>>>> signalling/management interfaces for control and
>>>>> configuration of RTP monitoring services, and reporting
>>>>> interfaces for measurement data ...
>>>>> b) overlay approach: separate specification to ...
>>>>>=20
>>>>>=20
>>>>> PSS
>>>>> BTW: there's a discussion paper with regards to the location
>>>>> of a monitor function in an IMS H.248 gateway entity:
>>>>> Measurements and statistics in IMS - Use Cases
>>>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
>>>>> 8_Kyoto_Japan/Docs/C3-100469.zip
>>>>> This is just fyi.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>>>>>> Behalf Of Qin Wu
>>>>>> Sent: Freitag, 2. Dezember 2011 02:55
>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>> Cc: megaco@ietf.org
>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>=20
>>>>>> Hi, Albrecht:
>>>>>> No offence, I am not really convinced with your proposal on
>>>>>> physical monitoring architecture.
>>>>>> my counterquestion is what does physical monitoring
>>>>>> architecture looks like in your mind?
>>>>>> How many components do we have in such physical monitroing
>>>>>> architecture? what are they?
>>>>>> Take IMS network architecture as a example, they may have
>>>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
>>>>>> described in draft-ietf-avtcore-monarch is mapped into
>>>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
>>>>>> should be in the scope of IETF RTP monitoring
>>> archtiecture draft?
>>>>>>=20
>>>>>> Monitor described in  draft-ietf-avtcore-monarch is well
>>>>>> defined in the section 3 of RFC3550 as follows:
>>>>>> "
>>>>>>=20
>>>>>>  Monitor: An application that receives RTCP packets sent by
>>>>>>     participants in an RTP session, in particular the
>>> reception
>>>>>>     reports, and estimates the current quality of service for
>>>>>>     distribution monitoring, fault diagnosis and long-term
>>>>>> statistics.
>>>>>>     The monitor function is likely to be built into the
>>>>>> application(s)
>>>>>>     participating in the session, but may also be a separate
>>>>>>     application that does not otherwise participate and
>>>>>> does not send
>>>>>>     or receive the RTP data packets (since they are on
>>>> a separate
>>>>>>     port).  These are called third-party monitors.  It is also
>>>>>>     acceptable for a third-party monitor to receive
>>> the RTP data
>>>>>>     packets but not send RTCP packets or otherwise be
>>>>> counted in the
>>>>>>     session.
>>>>>>=20
>>>>>> "
>>>>>> Isn't how to implent monitor into IMS netowork archtiecture a
>>>>>> implentation specific issue?
>>>>>> If this issue are really interesting, isn't it a good idea to
>>>>>> produce another new document to talk about this?
>>>>>> One good example for this motivation is this draft I like to
>>>>>> share with you:
>>>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
>>>>>> y-00#section-4.6
>>>>>>=20
>>>>>> Regards!
>>>>>> -Qin
>>>>>> ----- Original Message -----
>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>> Cc: <megaco@ietf.org>
>>>>>> Sent: Friday, December 02, 2011 12:20 AM
>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>=20
>>>>>>=20
>>>>>> My replies below ...
>>>>>> -Albrecht
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>> Cc: megaco@ietf.org
>>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>=20
>>>>>>> Hi,
>>>>>>> ----- Original Message -----
>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>>> Cc: <megaco@ietf.org>
>>>>>>> Sent: Thursday, December 01, 2011 1:24 AM
>>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>=20
>>>>>>>=20
>>>>>>> My replies below inline,
>>>>>>> Albrecht
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>>> Sent: Mittwoch, 30. November 2011 04:51
>>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>>> Cc: megaco@ietf.org
>>>>>>>> Subject: Re: [AVTCORE] Types of monitoring
>>> architectures; RE:
>>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>>=20
>>>>>>>> Hi,
>>>>>>>> ----- Original Message -----
>>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>>> To: <avt@ietf.org>
>>>>>>>> Cc: <megaco@ietf.org>
>>>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
>>>>>>>> Subject: [AVTCORE] Types of monitoring
>>> architectures; RE: I-D
>>>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>> Dear All,
>>>>>>>>>=20
>>>>>>>>> there are different types of monitoring architectures,
>>>>>>>> particularily from perspective of QoE related performance
>>>>>>> parameters.
>>>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
>>>>>>>>>=20
>>>>>>>>> Quality of Experience (QoE):
>>>>>>>>> The overall acceptability of an application or service, as
>>>>>>>> perceived subjectively by the end-user.
>>>>>>>>> NOTE 1 - Quality of experience includes the complete
>>>>>>>> end-to-end system effects (client, terminal, network,
>>>>>>>> services infrastructure, etc.).
>>>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
>>>>>>>> expectations and context.
>>>>>>>>>=20
>>>>>>>>> Important for MONARCH:
>>>>>>>>> 1st ... perceived by end-user
>>>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
>>>>>>>>>=20
>>>>>>>>> That said, present RTP monitoring architecture in MONARCH
>>>>>>>> according clause 3 is not specific on the type of monitoring
>>>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
>>>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
>>>>>>>> to a terminal/user equipment (UE). This would be an
>>>>>>>> end-to-end IP network scenario.
>>>>>>>>>=20
>>>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
>>>>>>>> be also located at the edge of an IP network, e.g. in a
>>>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
>>>>>>>> the non-IP network part.
>>>>>>>>> Note: such scenarios are considered by MEGACO gateways
>>>>>>>> (I've Cc'd megaco list).
>>>>>>>>>=20
>>>>>>>>> An RTP Sender/Receiver located NOT in the UE
>>> would question
>>>>>>>> the value of RTP/RTCP QoE related performance measurements
>>>>>>>> (because the UE is located outside the RTP domain).
>>>>>>>>>=20
>>>>>>>>> Conclusions:
>>>>>>>>> - the set of meaningful performance metrics may be
>>>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
>>>>>>>> whether in a UE, gateway, ...
>>>>>>>>> - don't see any impact on transport level metrics
>>>>>>>>> - ... but the set of meaningful application level metrics
>>>>>>>>>=20
>>>>>>>>> Proposal for MONARCH:
>>>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
>>>>>>>> architecture" below clause 3
>>>>>>>>>=20
>>>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
>>>>>>>>>=20
>>>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
>>>>>>>>> The location of the RTP Sender/Receiver entity may impact
>>>>>>>> the set of meaningful metrics.
>>>>>>>>> For instance: application level metrics for QoE related
>>>>>>>> performance metrics are questionable (or doesn't really make
>>>>>>>> sense at all) when measured in a network node (terminating
>>>>>>>> the RTP) instead of the user equipment."
>>>>>>>>>=20
>>>>>>>>> Something like this would help to avoid confusion.
>>>>>>>>> I even believe that a QoE measurement in a network node
>>>>>>>> would violate the QoE definition. Would be rather something
>>>>>>>> like QoE* ("remote QoE"):-(
>>>>>>>>>=20
>>>>>>>>> Such information would improve the MONARCH doc in
>>>> my opinion.
>>>>>>>>> Sorry for that late comment.
>>>>>>>>> Any views?
>>>>>>>>=20
>>>>>>>> [Qin]:
>>>>>>>> Albrrecht, if you follow ealry list discussion on
>>>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
>>>>>>>> to position this document was
>>>>>>>> this daft should focus on guidelines for defining reporting
>>>>>>>> blocks. That is to say the main purpose of MONARCH draft
>>>>>> is how to
>>>>>>>> provide guidelines for the development of new RTCP XR block
>>>>>>>> types in XRBlock working group.
>>>>>>>=20
>>>>>>> [ABS] ... then the title "monitoring architectures" is
>>>> misleading.
>>>>>>> Proposal: keep title, revise scope section on focus
>>>>>>>=20
>>>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
>>>>>>> not expand scope into IP monitoring architecture.
>>>>>>=20
>>>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
>>>>>>=20
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Therefore how and where to collect the metric from RTP
>>>>>>>> endpoint is not scope of this document, in my opinion. since
>>>>>>>> you may have many ways to do this and different vendors have
>>>>>>>> their different appoaches. It will be better to leave this
>>>>>>>> beyond the scope. But you are right, it will be more
>>>>>>>> reasonable to measure QoE related performance metric at the
>>>>>>>> RTP receiver.
>>>>>>>=20
>>>>>>> [ABS] I would disagree. At least your statement should be
>>>>>>> conditional, sth like
>>>>>>> "QoE related performance metrics may be measured in a RTP
>>>>>>> receiver, IF the RTP receiver function is located in user
>>>>>>> equipment (e.g. IP terminal), because QoE performance metrics
>>>>>>> are tightly coupled to the point of view of a 'user'.
>>>>>>> ... IF NOT, then ..."
>>>>>>>=20
>>>>>>> [Qin]: I am not sure user equipment or IP terminal is the
>>>>>>> right term from RTP perspective.
>>>>>>>=20
>>>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
>>>>>>> related metric can be placed either at the network or at
>>>>> the client.
>>>>>>> So I disagree with what you said.
>>>>>>=20
>>>>>> [ABS] Not convinced at all.
>>>>>> Guess you are referring to the "mid-point" models, right?
>>>>>> The usage of such that models depends on "prior knowledge
>>>>>> ..." information.
>>>>>> Thus, the applicability is conditional. You may not make such
>>>>>> a general statement.
>>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> Also as I said, how and where to collect the metric from RTP
>>>>>>> endpoint is not scope of this document. It depends on the
>>>>>>> model you are choosing, e.g., four operation modes specified
>>>>>>> in P.NAMS.
>>>>>>> Apparently this should not be specified again in RTP
>>>>>>> monitoring architecture document.
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Another point is it is not clear to me how RTP
>>> monitoring has
>>>>>>>> to do with architectureend to end IP network architecture .
>>>>>>>> this draft mostly focus on discussing RTP level stuff.
>>>>>>>> Therefore I am quite doubt that we should describe anything
>>>>>>>> in this document like how
>>>>>>>> RTP entties is mapped into network entities/nodes at
>>>>> the IP layer.
>>>>>>>=20
>>>>>>> [ABS] I don't got any problems to talk about architectural
>>>>>>> framework for monitoring in this document. Such information
>>>>>>> is required and this is the only IETF AVT doc about it.
>>>>>>> The solution to this issue is rather simple to me:
>>>>>>> - split the MONARCH "monitoring architecture" in
>>>>>>> 1) a functional monitoring architecture (let's call it
>>>> 'FMA') and
>>>>>>> 2) a physical monitoring architecture (... 'PMA').
>>>>>>>=20
>>>>>>> - the present MONARCH doc would describe the FMA at the level
>>>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
>>>>>>> topology components according RFC 5117)
>>>>>>>=20
>>>>>>> - there are many options of functional-to-physical mappings,
>>>>>>> i.e. how a FMA would be mapped on a PMA
>>>>>>> - the mapping is typically dependent on considered network
>>>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
>>>> networks)
>>>>>>>=20
>>>>>>> - the present MONARCH doc would describe the FMA-to-PMA
>>>>>>> mapping IF all RTP receiver/sender entities would be located
>>>>>>> in physical IP terminals (UEs)
>>>>>>> - etc
>>>>>>>=20
>>>>>>> [Qin]: I can understand your point, but you can not do that.
>>>>>>> Since this document is only focus on *RTP* monitoring
>>>>>>> architecture, that is what it said in AVTCore milestone:
>>>>>>> "
>>>>>>>=20
>>>>>>> Goals and Milestones:
>>>>>>>=20
>>>>>>> Feb 2011 - Submit Monitoring Architecture for RTP for
>>>>>> Informational
>>>>>>>=20
>>>>>>> "
>>>>>>=20
>>>>>> [ABS] If you go back to my first email on this subject, and
>>>>>> if you look at my proposal: that's not a lot, nothing which
>>>>>> violates the charter, goals and milestones.
>>>>>>=20
>>>>>>=20
>>>>>>> Also if you really don't see how to map FMA to PMA, you may
>>>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
>>>>>>> As for how to use RTP monitoring architecture or RTP XR
>>>>>>> Report in the IMS network architecture, you may look at:
>>>>>>> http://tools.ietf.org/html/rfc6035
>>>>>>=20
>>>>>> [ABS] That's the SIP reporting interface, i.e., applicable
>>>>>> primarily for physical IP user equipment with embedded RTP
>>>>>> sender/receiver function and SIP UA function.
>>>>>> However, the applicability of RFC 6035 is limited for a
>>>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
>>>>>> located NOT in user equipment. Also the P.NAMS mid-point
>>>>>> model fails for such a scenario.
>>>>>>=20
>>>>>>> ITU-T H.248.48.
>>>>>>> But I haven't check the current status of H.248.48.
>>>>>>=20
>>>>>> [ABS] Work is finalized, see
>>>>>> http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
>>>>>> 11121-TD-PLEN-0419
>>>>>>=20
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> But as the author of this document, I am interested and open
>>>>>>>> to other opinions.:-)
>>>>>>>=20
>>>>>>> [ABS] Like to add a further aspect: a "functional monitoring
>>>>>>> architecture" may be considered as a network overlay,
>>>>>>> something which adds additional capabilities (here:
>>>>>>> measurement services, reporting services on top of basic RTP
>>>>>>> services).
>>>>>>> Such an overlay concept is nothing new: e.g., the
>>>>>>> MultiService Forum did define a "Performance Measurement &
>>>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
>>>>>>> considered as such.
>>>>>>>=20
>>>>>>>>=20
>>>>>>>>> Regards,
>>>>>>>>> Albrecht
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: avt-bounces@ietf.org
>>> [mailto:avt-bounces@ietf.org] On
>>>>>>>>>> Behalf Of internet-drafts@ietf.org
>>>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
>>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>>> Cc: avt@ietf.org
>>>>>>>>>> Subject: [AVTCORE] I-D Action:
>>>>>> draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>>> Internet-Drafts directories. This draft is a work
>>>> item of the
>>>>>>>>>> Audio/Video Transport Core Maintenance Working Group
>>>>>> of the IETF.
>>>>>>>>>>=20
>>>>>>>>>> Title           : Monitoring Architectures for RTP
>>>>>>>>>> Author(s)       : Qin Wu
>>>>>>>>>>                         Geoff Hunt
>>>>>>>>>>                         Philip Arden
>>>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>> Pages           : 25
>>>>>>>>>> Date            : 2011-11-28
>>>>>>>>>>=20
>>>>>>>>>>  This memo proposes an architecture for
>>>> extending RTCP with
>>>>>>>>>> a new RTCP
>>>>>>>>>>  XR (RFC3611) block type to report new metrics
>>>>>> regarding media
>>>>>>>>>>  transmission or reception quality, following RTCP
>>>>> guideline
>>>>>>>>>>  established in RFC5968.  This memo suggests that a new
>>>>>>>> block should
>>>>>>>>>>  contain a single metric or a small number of metrics
>>>>>>>> relevant to a
>>>>>>>>>>  single parameter of interest or concern, rather than
>>>>>>>> containing a
>>>>>>>>>>  number of metrics which attempt to provide
>>> full coverage
>>>>>>>>>> of all those
>>>>>>>>>>  parameters of concern to a specific application.
>>>>>>>> Applications may
>>>>>>>>>>  then "mix and match" to create a set of blocks which
>>>>>>>>>> covers their set
>>>>>>>>>>  of concerns.  Where possible, a specific
>>> block should be
>>>>>>>>>> designed to
>>>>>>>>>>  be re-usable across more than one application, for
>>>>>>>> example, for all
>>>>>>>>>>  of voice, streaming audio and video.
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>>>=20
>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>> =
http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>=20
>>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>>>=20
>>>>>>>>>> This Internet-Draft can be retrieved at:
>>>>>>>>>>=20
>>>>>>>>=20
>>>>>>=20
>>>> =
ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>=20
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>>> avt@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>> avt@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>=20
>>>>>>> =3D
>>>>>> _______________________________________________
>>>>>> Audio/Video Transport Core Maintenance
>>>>>> avt@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>=20
>=20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
>=20
>=20
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



--=20
Colin Perkins
http://csperkins.org/




From bill.wu@huawei.com  Wed Dec 14 00:00:42 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4185D21F84B6; Wed, 14 Dec 2011 00:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.625
X-Spam-Level: 
X-Spam-Status: No, score=-5.625 tagged_above=-999 required=5 tests=[AWL=-0.226, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSnBNaoK4IVQ; Wed, 14 Dec 2011 00:00:39 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id EAD6321F8511; Wed, 14 Dec 2011 00:00:38 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW600L4ZORPYA@szxga05-in.huawei.com>; Wed, 14 Dec 2011 15:57:26 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW600KDUOQIOJ@szxga05-in.huawei.com>; Wed, 14 Dec 2011 15:57:25 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFV01231; Wed, 14 Dec 2011 15:57:24 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 14 Dec 2011 15:57:17 +0800
Received: from w53375q (10.138.41.130) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 14 Dec 2011 15:57:21 +0800
Date: Wed, 14 Dec 2011 15:57:20 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Colin Perkins <csp@csperkins.org>
Message-id: <D1B876207D0042219876F70FD85D3C1B@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <1815848C-FE4C-48A0-8889-565198BEEC74@csperkins.org>
Cc: megaco@ietf.org, avt@ietf.org, "Schwarz, Albrecht \(Albrecht\)" <albrecht.schwarz@alcatel-lucent.com>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2011 08:00:42 -0000

Okay, thanks.
----- Original Message ----- 
From: "Colin Perkins" <csp@csperkins.org>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: <megaco@ietf.org>; <avt@ietf.org>; "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
Sent: Wednesday, December 14, 2011 6:54 AM
Subject: Re: [AVTCORE] Types of monitoring architectures;RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


> Qin,
> 
> Both this, and Albrecht's suggested additions, look reasonable to me.
> 
> Colin
> 
> 
> 
> On 13 Dec 2011, at 02:15, Qin Wu wrote:
>> Hi, Colin:
>> Thank for your suggestion. Besides Albrecht's proposed text, my additional proposal is to fix application level metric defintion in section 2
>> OLD text:
>> "
>>   Application level metrics
>> 
>>      Metrics relating to QoE related parameters.  These metrics are
>>      measured at the application level and focus on quality of content
>>      rather than network parameters. 
>> "
>> New text
>> "
>>   Application level metrics
>> 
>>      Metrics relating to application specific parameters or QoE related parameters. 
>>     Application specific parameters  are measured at the application level and focus
>>     on quality of content rather than network performance.  QoE related parameters
>>     reflect the end-to-end performance at the services level and is ususally measured
>>     at the user endpoint.
>> "
>> 
>> Regards!
>> -Qin
>> ----- Original Message ----- 
>> From: "Colin Perkins" <csp@csperkins.org>
>> To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
>> Cc: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>; <megaco@ietf.org>
>> Sent: Tuesday, December 13, 2011 12:56 AM
>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt
>> 
>> 
>> Albrecht, Qin,
>> 
>> It doesn't seem controversial that some metrics are only meaningful in some scenarios, or when measured at certain points in a system. I don't see how adding a statement to the monarch draft to recognise that could be problematic. Is there anything else being suggested here?
>> 
>> Colin
>> 
>> 
>> On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
>>> Hi Qin,
>>> 
>>> I'm very aware about all that.
>>> It looks like that you are now agreeing that QoE measurements are CONDITIONAL ("you got a number of IF statements, there might be even more ...").
>>> 
>>> MONARCH is not talking about such conditions, thus some readers may got the impression that the metrics related to RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
>>> 
>>> If you go back to my very first email: I did just propose to indicate the conditional aspect. Don't understand why such kind of valuable info would be not in scope of MONARCH. Hm?
>>> 
>>> Regards,
>>> Albrecht
>>> 
>>> PS
>>> I did use the notion of a control plane agnostic "RTP-to-PSTN gateway". You did indicate control plane specific gateway types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol specific examples, but it doesn't change the underlying issue.
>>> The SIP side reporting capability based on RFC 6035 allows to report the outlined measurements, but the RFC itself does not specify whether the reported information is meaningful (which is OK because this is not subject of a reporting interface spec, it is rather subject of a network monitoring doc like MONARCH).
>>> QoE measurements would be conditional in both gateway types (because such a gateway is NOT a user device despite the fact of an embedded SIP user agent entity).
>>> Actually I would even question here the condition of "customer knows the original content" in many real network scenarios.
>>> 
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>> Sent: Montag, 12. Dezember 2011 05:05
>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>> Cc: megaco@ietf.org
>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>> 
>>>> Hi, Albrecht:
>>>> My understanding to QoE measurment is:
>>>> The factors that influence the QoE metric include encoding
>>>> system, transport network, access network,home network and end device.
>>>> If the customer(e.g., network operator) doesn't know the
>>>> original content, the QoE metric should be usually measured
>>>> at the user device.
>>>> If the customer knows the original content, the QoE metric
>>>> can be measured either in the network or at the user device.
>>>> Given the growing popularity of connected devices, these
>>>> devices may have different capability corresponding to CPU
>>>> load, processing overhead, storage, batteries.
>>>> If the cusomer want to measure QoE without considering
>>>> connected devices with various capability , the QoE metric
>>>> can be measured at the point between access network and home network.
>>>> 
>>>> Regarding the monitoring scenario you mentioned, I am not
>>>> familiar with such scenario with RTP-to-PSTN gateway deployed.
>>>> But I am aware that there are scenarios with SIP to PSTN
>>>> gateway or SIP to H.323 gateway widely deployed,  RFC6035
>>>> defines a new SIP event package, vq-rtcpxr that enable the
>>>> collection and  reporting of metrics that measure quality for
>>>> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
>>>> metric included is measured at the user device and mapped
>>>> into the equivalent SIP vq-rtcpxr parameter since SIP session
>>>> call is established end to end and RTP media stream is
>>>> exchanged directly between one endpoint and the other endpoint.
>>>> 
>>>> Regards!
>>>> -Qin
>>>> ----- Original Message -----
>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>> Cc: <megaco@ietf.org>
>>>> Sent: Saturday, December 10, 2011 12:01 AM
>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>> 
>>>> 
>>>> How do you explain to a network operator the value of QoE
>>>> measurements by an RTP receiver / RTP monitor component
>>>> located in an RTP-to-PSTN gateway?
>>>> 
>>>> This would be a monitoring scenario inline with MONARCH, but
>>>> with valueless QoE results, right?
>>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>> Sent: Donnerstag, 8. Dezember 2011 03:26
>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>> Cc: megaco@ietf.org
>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>> 
>>>>> You reiterate what you propose for physical entities in the
>>>>> early email.
>>>>> I am still not convicing with that.
>>>>> 
>>>>> Since we have RTP components like RTP end system, RTP mixer,
>>>>> RTP media translator, RTP transport translator, RTP monitor
>>>>> specified in RFC3550 can be built into these component as a
>>>>> application. also monitor can be disjointed from these RTP
>>>>> components as a third party monitor. why we need to specify
>>>>> how to map RTP end system into user equipment, RTP translator
>>>>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
>>>>> border gateway since we have already mapped monitor into
>>>>> different RTP components.
>>>>> How many PE types you can enumerate? why they should be scope
>>>>> of RTP monitoring architecture?
>>>>> 
>>>>> Also as specified in MONARCH draft, we have end sytem
>>>>> metrics, transport level metric, transport level metric, they
>>>>> can be measured and collected from the different RTP
>>>>> comoponents specified in RFC3550, RFC5117. Apparently end
>>>>> system metric can only be collected from RTP end system.
>>>>> transport metric is collected from any RTP system in the RTP
>>>>> monitoring architecture, regarding application level metric,
>>>>> apparently they should be measured at the application layer
>>>>> and can not be collected from RTP transport translator, Also
>>>>> RTP transport translator is still a functional entity rather
>>>>> than a physical entity. I am not convincing with what you
>>>>> said about "contradiction", "lead to possible wrong expectations".
>>>>> 
>>>>> Regards!
>>>>> -Qin
>>>>> ----- Original Message -----
>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>> Cc: <megaco@ietf.org>
>>>>> Sent: Thursday, December 08, 2011 12:24 AM
>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>> 
>>>>> 
>>>>> Qin,
>>>>> that's NOT the point.
>>>>> 
>>>>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
>>>> ENTITIES (FE).
>>>>> e.g.,
>>>>> - the RTP Monitor or RTP receiver FE may be located in
>>>>> different PHYSICAL ENTITIES (PE), e.g.
>>>>>       a1) a user equipment
>>>>>       a2) a RTP-to-PSTN gateway
>>>>>       a3) an IP-to-IP session border gateway (in a
>>>>> back-to-back RTP endsystem topology)
>>>>>       a3) ...
>>>>> 
>>>>> - the RTP Monitor may be associated to an RTP transport
>>>> translator ...
>>>>>       b1) an IP-to-IP session border gateway
>>>>> 
>>>>> The "RTP monitoring architecture" is IMPACTED by each
>>>>> functional-to-physical mapping because e.g.
>>>>> * QoE related metrics are questionable in case of a2
>>>>> ("despite the fact of a RTP receiver function")
>>>>> * application level metrics at the location of a RTP
>>>>> transport translator are a contradiction in itself
>>>>> * ...
>>>>> 
>>>>> Again, it's not really changing the MONARCH draft because in
>>>>> the very majority of scenarios it is correct. However, there
>>>>> are few cases where the MONARCH description would be "too
>>>>> high level", "not fully correct", "lead to possible wrong
>>>>> expectations", ...
>>>>> 
>>>>> Regards,
>>>>> Albrecht
>>>>> 
>>>>> 
>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>> Sent: Dienstag, 6. Dezember 2011 07:13
>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>> Cc: megaco@ietf.org
>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>> 
>>>>>> If you talk about existing RFC5117 RTP topology components,
>>>>>> this has already been covered by the current version of
>>>>>> draft-ietf-avtcore-monarch.
>>>>>> In most cases, an RTP system using RTCP XR is architecturally
>>>>>> no different from an RTP system which does not use RTCP XR.
>>>>>> 
>>>>>> Regards!
>>>>>> -Qin
>>>>>> ----- Original Message -----
>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>> Cc: <megaco@ietf.org>
>>>>>> Sent: Monday, December 05, 2011 10:48 PM
>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>> 
>>>>>> 
>>>>>> Hello Qin,
>>>>>> 
>>>>>> to 1) Physical monitoring architecture
>>>>>> Of course consideration of generic physical entities (PE),
>>>>>> not specific to any network reference architectures defined
>>>>>> by SDOs (like your refered entities).
>>>>>> There would be just a few PE types ("given by the limited set
>>>>>> of RTP topology components (RFC 5117)").
>>>>>> 
>>>>>> to 2) (RFC 3550) Monitor function
>>>>>> Right, that's a functional entity. The applicability of a
>>>>>> monitor may be limited, dependent on ... (like in P.NAMS).
>>>>>> 
>>>>>> to 3) your IMS network example
>>>>>> Don't see the need to refer from MONARCH to a specific
>>>>>> network architecture like IMS.
>>>>>> Please also note that IMS is a functional architecture, not a
>>>>>> physical architecture.
>>>>>> 
>>>>>> Regards,
>>>>>> Albrecht
>>>>>> 
>>>>>> PS
>>>>>> There are multiple options for adding the "RTP monitoring
>>>>>> architecture" to a functional/physical network architecture:
>>>>>> a) integrated approach: extension of existing functional
>>>>>> entities or/and addition of RTP monitoring architectural
>>>>>> components, extension or/and addition of
>>>>>> signalling/management interfaces for control and
>>>>>> configuration of RTP monitoring services, and reporting
>>>>>> interfaces for measurement data ...
>>>>>> b) overlay approach: separate specification to ...
>>>>>> 
>>>>>> 
>>>>>> PSS
>>>>>> BTW: there's a discussion paper with regards to the location
>>>>>> of a monitor function in an IMS H.248 gateway entity:
>>>>>> Measurements and statistics in IMS - Use Cases
>>>>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
>>>>>> 8_Kyoto_Japan/Docs/C3-100469.zip
>>>>>> This is just fyi.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> -----Original Message-----
>>>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>>>>>>> Behalf Of Qin Wu
>>>>>>> Sent: Freitag, 2. Dezember 2011 02:55
>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>> Cc: megaco@ietf.org
>>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>> 
>>>>>>> Hi, Albrecht:
>>>>>>> No offence, I am not really convinced with your proposal on
>>>>>>> physical monitoring architecture.
>>>>>>> my counterquestion is what does physical monitoring
>>>>>>> architecture looks like in your mind?
>>>>>>> How many components do we have in such physical monitroing
>>>>>>> architecture? what are they?
>>>>>>> Take IMS network architecture as a example, they may have
>>>>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
>>>>>>> described in draft-ietf-avtcore-monarch is mapped into
>>>>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
>>>>>>> should be in the scope of IETF RTP monitoring
>>>> archtiecture draft?
>>>>>>> 
>>>>>>> Monitor described in  draft-ietf-avtcore-monarch is well
>>>>>>> defined in the section 3 of RFC3550 as follows:
>>>>>>> "
>>>>>>> 
>>>>>>>  Monitor: An application that receives RTCP packets sent by
>>>>>>>     participants in an RTP session, in particular the
>>>> reception
>>>>>>>     reports, and estimates the current quality of service for
>>>>>>>     distribution monitoring, fault diagnosis and long-term
>>>>>>> statistics.
>>>>>>>     The monitor function is likely to be built into the
>>>>>>> application(s)
>>>>>>>     participating in the session, but may also be a separate
>>>>>>>     application that does not otherwise participate and
>>>>>>> does not send
>>>>>>>     or receive the RTP data packets (since they are on
>>>>> a separate
>>>>>>>     port).  These are called third-party monitors.  It is also
>>>>>>>     acceptable for a third-party monitor to receive
>>>> the RTP data
>>>>>>>     packets but not send RTCP packets or otherwise be
>>>>>> counted in the
>>>>>>>     session.
>>>>>>> 
>>>>>>> "
>>>>>>> Isn't how to implent monitor into IMS netowork archtiecture a
>>>>>>> implentation specific issue?
>>>>>>> If this issue are really interesting, isn't it a good idea to
>>>>>>> produce another new document to talk about this?
>>>>>>> One good example for this motivation is this draft I like to
>>>>>>> share with you:
>>>>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
>>>>>>> y-00#section-4.6
>>>>>>> 
>>>>>>> Regards!
>>>>>>> -Qin
>>>>>>> ----- Original Message -----
>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>>> Cc: <megaco@ietf.org>
>>>>>>> Sent: Friday, December 02, 2011 12:20 AM
>>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>> 
>>>>>>> 
>>>>>>> My replies below ...
>>>>>>> -Albrecht
>>>>>>> 
>>>>>>>> -----Original Message-----
>>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
>>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>>> Cc: megaco@ietf.org
>>>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> ----- Original Message -----
>>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>>>> Cc: <megaco@ietf.org>
>>>>>>>> Sent: Thursday, December 01, 2011 1:24 AM
>>>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>> 
>>>>>>>> 
>>>>>>>> My replies below inline,
>>>>>>>> Albrecht
>>>>>>>> 
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>>>> Sent: Mittwoch, 30. November 2011 04:51
>>>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>>>> Cc: megaco@ietf.org
>>>>>>>>> Subject: Re: [AVTCORE] Types of monitoring
>>>> architectures; RE:
>>>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> Hi,
>>>>>>>>> ----- Original Message -----
>>>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>>>> To: <avt@ietf.org>
>>>>>>>>> Cc: <megaco@ietf.org>
>>>>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
>>>>>>>>> Subject: [AVTCORE] Types of monitoring
>>>> architectures; RE: I-D
>>>>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Dear All,
>>>>>>>>>> 
>>>>>>>>>> there are different types of monitoring architectures,
>>>>>>>>> particularily from perspective of QoE related performance
>>>>>>>> parameters.
>>>>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
>>>>>>>>>> 
>>>>>>>>>> Quality of Experience (QoE):
>>>>>>>>>> The overall acceptability of an application or service, as
>>>>>>>>> perceived subjectively by the end-user.
>>>>>>>>>> NOTE 1 - Quality of experience includes the complete
>>>>>>>>> end-to-end system effects (client, terminal, network,
>>>>>>>>> services infrastructure, etc.).
>>>>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
>>>>>>>>> expectations and context.
>>>>>>>>>> 
>>>>>>>>>> Important for MONARCH:
>>>>>>>>>> 1st ... perceived by end-user
>>>>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
>>>>>>>>>> 
>>>>>>>>>> That said, present RTP monitoring architecture in MONARCH
>>>>>>>>> according clause 3 is not specific on the type of monitoring
>>>>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
>>>>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
>>>>>>>>> to a terminal/user equipment (UE). This would be an
>>>>>>>>> end-to-end IP network scenario.
>>>>>>>>>> 
>>>>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
>>>>>>>>> be also located at the edge of an IP network, e.g. in a
>>>>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
>>>>>>>>> the non-IP network part.
>>>>>>>>>> Note: such scenarios are considered by MEGACO gateways
>>>>>>>>> (I've Cc'd megaco list).
>>>>>>>>>> 
>>>>>>>>>> An RTP Sender/Receiver located NOT in the UE
>>>> would question
>>>>>>>>> the value of RTP/RTCP QoE related performance measurements
>>>>>>>>> (because the UE is located outside the RTP domain).
>>>>>>>>>> 
>>>>>>>>>> Conclusions:
>>>>>>>>>> - the set of meaningful performance metrics may be
>>>>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
>>>>>>>>> whether in a UE, gateway, ...
>>>>>>>>>> - don't see any impact on transport level metrics
>>>>>>>>>> - ... but the set of meaningful application level metrics
>>>>>>>>>> 
>>>>>>>>>> Proposal for MONARCH:
>>>>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
>>>>>>>>> architecture" below clause 3
>>>>>>>>>> 
>>>>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
>>>>>>>>>> 
>>>>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
>>>>>>>>>> The location of the RTP Sender/Receiver entity may impact
>>>>>>>>> the set of meaningful metrics.
>>>>>>>>>> For instance: application level metrics for QoE related
>>>>>>>>> performance metrics are questionable (or doesn't really make
>>>>>>>>> sense at all) when measured in a network node (terminating
>>>>>>>>> the RTP) instead of the user equipment."
>>>>>>>>>> 
>>>>>>>>>> Something like this would help to avoid confusion.
>>>>>>>>>> I even believe that a QoE measurement in a network node
>>>>>>>>> would violate the QoE definition. Would be rather something
>>>>>>>>> like QoE* ("remote QoE"):-(
>>>>>>>>>> 
>>>>>>>>>> Such information would improve the MONARCH doc in
>>>>> my opinion.
>>>>>>>>>> Sorry for that late comment.
>>>>>>>>>> Any views?
>>>>>>>>> 
>>>>>>>>> [Qin]:
>>>>>>>>> Albrrecht, if you follow ealry list discussion on
>>>>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
>>>>>>>>> to position this document was
>>>>>>>>> this daft should focus on guidelines for defining reporting
>>>>>>>>> blocks. That is to say the main purpose of MONARCH draft
>>>>>>> is how to
>>>>>>>>> provide guidelines for the development of new RTCP XR block
>>>>>>>>> types in XRBlock working group.
>>>>>>>> 
>>>>>>>> [ABS] ... then the title "monitoring architectures" is
>>>>> misleading.
>>>>>>>> Proposal: keep title, revise scope section on focus
>>>>>>>> 
>>>>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
>>>>>>>> not expand scope into IP monitoring architecture.
>>>>>>> 
>>>>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
>>>>>>> 
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Therefore how and where to collect the metric from RTP
>>>>>>>>> endpoint is not scope of this document, in my opinion. since
>>>>>>>>> you may have many ways to do this and different vendors have
>>>>>>>>> their different appoaches. It will be better to leave this
>>>>>>>>> beyond the scope. But you are right, it will be more
>>>>>>>>> reasonable to measure QoE related performance metric at the
>>>>>>>>> RTP receiver.
>>>>>>>> 
>>>>>>>> [ABS] I would disagree. At least your statement should be
>>>>>>>> conditional, sth like
>>>>>>>> "QoE related performance metrics may be measured in a RTP
>>>>>>>> receiver, IF the RTP receiver function is located in user
>>>>>>>> equipment (e.g. IP terminal), because QoE performance metrics
>>>>>>>> are tightly coupled to the point of view of a 'user'.
>>>>>>>> ... IF NOT, then ..."
>>>>>>>> 
>>>>>>>> [Qin]: I am not sure user equipment or IP terminal is the
>>>>>>>> right term from RTP perspective.
>>>>>>>> 
>>>>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
>>>>>>>> related metric can be placed either at the network or at
>>>>>> the client.
>>>>>>>> So I disagree with what you said.
>>>>>>> 
>>>>>>> [ABS] Not convinced at all.
>>>>>>> Guess you are referring to the "mid-point" models, right?
>>>>>>> The usage of such that models depends on "prior knowledge
>>>>>>> ..." information.
>>>>>>> Thus, the applicability is conditional. You may not make such
>>>>>>> a general statement.
>>>>>>> 
>>>>>>> 
>>>>>>>> 
>>>>>>>> Also as I said, how and where to collect the metric from RTP
>>>>>>>> endpoint is not scope of this document. It depends on the
>>>>>>>> model you are choosing, e.g., four operation modes specified
>>>>>>>> in P.NAMS.
>>>>>>>> Apparently this should not be specified again in RTP
>>>>>>>> monitoring architecture document.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Another point is it is not clear to me how RTP
>>>> monitoring has
>>>>>>>>> to do with architectureend to end IP network architecture .
>>>>>>>>> this draft mostly focus on discussing RTP level stuff.
>>>>>>>>> Therefore I am quite doubt that we should describe anything
>>>>>>>>> in this document like how
>>>>>>>>> RTP entties is mapped into network entities/nodes at
>>>>>> the IP layer.
>>>>>>>> 
>>>>>>>> [ABS] I don't got any problems to talk about architectural
>>>>>>>> framework for monitoring in this document. Such information
>>>>>>>> is required and this is the only IETF AVT doc about it.
>>>>>>>> The solution to this issue is rather simple to me:
>>>>>>>> - split the MONARCH "monitoring architecture" in
>>>>>>>> 1) a functional monitoring architecture (let's call it
>>>>> 'FMA') and
>>>>>>>> 2) a physical monitoring architecture (... 'PMA').
>>>>>>>> 
>>>>>>>> - the present MONARCH doc would describe the FMA at the level
>>>>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
>>>>>>>> topology components according RFC 5117)
>>>>>>>> 
>>>>>>>> - there are many options of functional-to-physical mappings,
>>>>>>>> i.e. how a FMA would be mapped on a PMA
>>>>>>>> - the mapping is typically dependent on considered network
>>>>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
>>>>> networks)
>>>>>>>> 
>>>>>>>> - the present MONARCH doc would describe the FMA-to-PMA
>>>>>>>> mapping IF all RTP receiver/sender entities would be located
>>>>>>>> in physical IP terminals (UEs)
>>>>>>>> - etc
>>>>>>>> 
>>>>>>>> [Qin]: I can understand your point, but you can not do that.
>>>>>>>> Since this document is only focus on *RTP* monitoring
>>>>>>>> architecture, that is what it said in AVTCore milestone:
>>>>>>>> "
>>>>>>>> 
>>>>>>>> Goals and Milestones:
>>>>>>>> 
>>>>>>>> Feb 2011 - Submit Monitoring Architecture for RTP for
>>>>>>> Informational
>>>>>>>> 
>>>>>>>> "
>>>>>>> 
>>>>>>> [ABS] If you go back to my first email on this subject, and
>>>>>>> if you look at my proposal: that's not a lot, nothing which
>>>>>>> violates the charter, goals and milestones.
>>>>>>> 
>>>>>>> 
>>>>>>>> Also if you really don't see how to map FMA to PMA, you may
>>>>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
>>>>>>>> As for how to use RTP monitoring architecture or RTP XR
>>>>>>>> Report in the IMS network architecture, you may look at:
>>>>>>>> http://tools.ietf.org/html/rfc6035
>>>>>>> 
>>>>>>> [ABS] That's the SIP reporting interface, i.e., applicable
>>>>>>> primarily for physical IP user equipment with embedded RTP
>>>>>>> sender/receiver function and SIP UA function.
>>>>>>> However, the applicability of RFC 6035 is limited for a
>>>>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
>>>>>>> located NOT in user equipment. Also the P.NAMS mid-point
>>>>>>> model fails for such a scenario.
>>>>>>> 
>>>>>>>> ITU-T H.248.48.
>>>>>>>> But I haven't check the current status of H.248.48.
>>>>>>> 
>>>>>>> [ABS] Work is finalized, see
>>>>>>> http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
>>>>>>> 11121-TD-PLEN-0419
>>>>>>> 
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> But as the author of this document, I am interested and open
>>>>>>>>> to other opinions.:-)
>>>>>>>> 
>>>>>>>> [ABS] Like to add a further aspect: a "functional monitoring
>>>>>>>> architecture" may be considered as a network overlay,
>>>>>>>> something which adds additional capabilities (here:
>>>>>>>> measurement services, reporting services on top of basic RTP
>>>>>>>> services).
>>>>>>>> Such an overlay concept is nothing new: e.g., the
>>>>>>>> MultiService Forum did define a "Performance Measurement &
>>>>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
>>>>>>>> considered as such.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Regards,
>>>>>>>>>> Albrecht
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: avt-bounces@ietf.org
>>>> [mailto:avt-bounces@ietf.org] On
>>>>>>>>>>> Behalf Of internet-drafts@ietf.org
>>>>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
>>>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>>>> Cc: avt@ietf.org
>>>>>>>>>>> Subject: [AVTCORE] I-D Action:
>>>>>>> draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>>>> Internet-Drafts directories. This draft is a work
>>>>> item of the
>>>>>>>>>>> Audio/Video Transport Core Maintenance Working Group
>>>>>>> of the IETF.
>>>>>>>>>>> 
>>>>>>>>>>> Title           : Monitoring Architectures for RTP
>>>>>>>>>>> Author(s)       : Qin Wu
>>>>>>>>>>>                         Geoff Hunt
>>>>>>>>>>>                         Philip Arden
>>>>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>> Pages           : 25
>>>>>>>>>>> Date            : 2011-11-28
>>>>>>>>>>> 
>>>>>>>>>>>  This memo proposes an architecture for
>>>>> extending RTCP with
>>>>>>>>>>> a new RTCP
>>>>>>>>>>>  XR (RFC3611) block type to report new metrics
>>>>>>> regarding media
>>>>>>>>>>>  transmission or reception quality, following RTCP
>>>>>> guideline
>>>>>>>>>>>  established in RFC5968.  This memo suggests that a new
>>>>>>>>> block should
>>>>>>>>>>>  contain a single metric or a small number of metrics
>>>>>>>>> relevant to a
>>>>>>>>>>>  single parameter of interest or concern, rather than
>>>>>>>>> containing a
>>>>>>>>>>>  number of metrics which attempt to provide
>>>> full coverage
>>>>>>>>>>> of all those
>>>>>>>>>>>  parameters of concern to a specific application.
>>>>>>>>> Applications may
>>>>>>>>>>>  then "mix and match" to create a set of blocks which
>>>>>>>>>>> covers their set
>>>>>>>>>>>  of concerns.  Where possible, a specific
>>>> block should be
>>>>>>>>>>> designed to
>>>>>>>>>>>  be re-usable across more than one application, for
>>>>>>>>> example, for all
>>>>>>>>>>>  of voice, streaming audio and video.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>> 
>>>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>>>> 
>>>>>>>>>>> This Internet-Draft can be retrieved at:
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>> 
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>>>> avt@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>>> avt@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>> 
>>>>>>>> =
>>>>>>> _______________________________________________
>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>> avt@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> _______________________________________________
>>> Audio/Video Transport Core Maintenance
>>> avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>> 
>> 
>> 
>> -- 
>> Colin Perkins
>> http://csperkins.org/
>> 
>> 
>> 
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
> 
> 
> 
> -- 
> Colin Perkins
> http://csperkins.org/
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From ramesh3184@gmail.com  Wed Dec 14 02:23:10 2011
Return-Path: <ramesh3184@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80B4A21F8B40 for <avt@ietfa.amsl.com>; Wed, 14 Dec 2011 02:23:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.523
X-Spam-Level: 
X-Spam-Status: No, score=-3.523 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnztai9lzlO0 for <avt@ietfa.amsl.com>; Wed, 14 Dec 2011 02:23:10 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0DAB021F8B36 for <avt@ietf.org>; Wed, 14 Dec 2011 02:23:09 -0800 (PST)
Received: by iaek3 with SMTP id k3so1234908iae.31 for <avt@ietf.org>; Wed, 14 Dec 2011 02:23:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=Jao22k2ETKbWwlAm4dXnyhUQUjJ0Wau0j/RzSUWzcVY=; b=EJssRphRsaaINxWm7Q9tkvkqpAUuFvxpyDNOvG+6JiA3ImPby9b+ezspZfySe0ccsm 31cYE/pXYLwNYA50UrAHMOfTh6CJ8Cs4GNZV/lBc0XxYEu/Fh7ksvmPELnfwkzHmhsTk /LIxPMwA83cOjNVS4/40TOC6l09KZ0+ocnBos=
MIME-Version: 1.0
Received: by 10.43.43.130 with SMTP id uc2mr18838606icb.35.1323858189650; Wed, 14 Dec 2011 02:23:09 -0800 (PST)
Received: by 10.50.100.233 with HTTP; Wed, 14 Dec 2011 02:23:09 -0800 (PST)
Date: Wed, 14 Dec 2011 15:53:09 +0530
Message-ID: <CAFLon=K8phF53nc7vrL5hPg2q1zq7up1yeV+uXVpemfKbiw4Aw@mail.gmail.com>
From: ramesh kumar <ramesh3184@gmail.com>
To: avt@ietf.org
Content-Type: multipart/alternative; boundary=bcaec52e601f208d1304b40ac1d2
Subject: [AVTCORE] Need Clarification on SSRC Usage in RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2011 10:23:10 -0000

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

Hi All,

I have a question on SSRC usage in RTP:

As per RFC 3550,

 The SSRC identifier is a
      randomly chosen value meant to be globally unique within a
      particular RTP session.  A participant need not
      use the same SSRC identifier for all the RTP sessions in a
      multimedia session.

Question:  Is there any possibility of SSRC Identifier be same across
consecutive RTP Sessions ? Does Standard emphasis on this ?

-- 
*Thanks & Regards,
R.Ramesh Kumar.
*

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

<div>Hi All,</div>
<div>=A0</div>
<div>I have a question on SSRC usage in RTP:</div>
<div>=A0</div>
<div>As per RFC 3550,</div>
<div>=A0</div>
<div>=A0The SSRC identifier is a<br>=A0=A0=A0=A0=A0 randomly chosen value m=
eant to be globally unique within a<br>=A0=A0=A0=A0=A0 particular RTP sessi=
on.=A0 A participant need not<br>=A0=A0=A0=A0=A0 use the same SSRC identifi=
er for all the RTP sessions in a<br>
=A0=A0=A0=A0=A0 multimedia session.</div>
<div>=A0</div>
<div>Question:=A0=A0Is there any possibility of=A0SSRC Identifier be same a=
cross consecutive RTP Sessions ? Does Standard emphasis on this ? <br clear=
=3D"all"><br>-- <br><font style=3D"BACKGROUND-COLOR:#ffffff" color=3D"#0000=
00"><em>Thanks &amp; Regards,<br>
R.Ramesh Kumar.<br></em></font></div>

--bcaec52e601f208d1304b40ac1d2--

From dbharrington@comcast.net  Tue Dec 13 10:16:00 2011
Return-Path: <dbharrington@comcast.net>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBF0521F89B8 for <avt@ietfa.amsl.com>; Tue, 13 Dec 2011 10:16:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNXqOdBL8eAk for <avt@ietfa.amsl.com>; Tue, 13 Dec 2011 10:16:00 -0800 (PST)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE2821F85A1 for <avt@ietf.org>; Tue, 13 Dec 2011 10:16:00 -0800 (PST)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta06.westchester.pa.mail.comcast.net with comcast id 8hPf1i0021ei1Bg56iG0mu; Tue, 13 Dec 2011 18:16:00 +0000
Received: from davidPC ([71.233.85.150]) by omta24.westchester.pa.mail.comcast.net with comcast id 8iFz1i01A3Ecudz3kiFz7e; Tue, 13 Dec 2011 18:16:00 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <avt@ietf.org>
Date: Tue, 13 Dec 2011 13:15:56 -0500
Message-ID: <0354667903064F32A184F2623C33D4A7@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
Thread-Index: Acy5srmCurKwh05ySdSymniy3nZ7xQAEHRRQ
X-Mailman-Approved-At: Wed, 14 Dec 2011 08:01:36 -0800
Subject: [AVTCORE] avtcore review of draft-ietf-fecframe-rtp-raptor-06.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 18:16:00 -0000

Hi,

As Responsible AD, I would like avtcore to check the text added to
draft-ietf-fecframe-rtp-raptor-06.txt in response to IESG comments.
This new text was not included in IETF Last Call.

Specifically, new section 10 describes RTP and RTCP usage for managing
losses between the sending app and the fecframe instance.

Please send your responses to fecframe@ietf.org and to me directly.

Thanks,
David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)



From ray.vanbrandenburg@tno.nl  Thu Dec 15 00:56:21 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE3E521F86A5 for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 00:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vQEK1N18nAB6 for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 00:56:18 -0800 (PST)
Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD1C21F86A6 for <avt@ietf.org>; Thu, 15 Dec 2011 00:56:17 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.71,356,1320620400"; d="scan'208,217";a="14053936"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.222]) by mailhost1b.tno.nl with ESMTP; 15 Dec 2011 09:56:12 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.242]) by EXC-CASHUB03.tsn.tno.nl ([134.221.225.222]) with mapi id 14.01.0323.003; Thu, 15 Dec 2011 09:56:12 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: Kevin Gross <kevin.gross@avanw.com>
Thread-Topic: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
Thread-Index: AQHMuQvz+3wC97PPk0GZDWSIW5lKWpXcmkOA
Date: Thu, 15 Dec 2011 08:56:11 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA158155F093E@EXC-MBX03.tsn.tno.nl>
References: <CALw1_Q3XG3jcWFk5F_7fvARX1HLzfvNT=O64kReB-cH2Xqqr_Q@mail.gmail.com>
In-Reply-To: <CALw1_Q3XG3jcWFk5F_7fvARX1HLzfvNT=O64kReB-cH2Xqqr_Q@mail.gmail.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.153]
Content-Type: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA158155F093EEXCMBX03tsntnon_"
MIME-Version: 1.0
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2011 08:56:22 -0000

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

Hi Kevin,

Thanks for your extensive comments. My comments inline.

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Kevin=
 Gross
Sent: maandag 12 december 2011 21:23
To: avt@ietf.org
Subject: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02

Here are some additional comments on the draft. Most of these are suggestio=
ns for minor improvements. Items 6 and 7 represent significant technical is=
sues and may require discussion.

1/ Chance all occurrences of "play-out" to "playout".

Ok

2/ First line of 1.2 "Currently, most _interactive_ multimedia applications=
 make use of RTP and RTCP." Streaming applications commonly use HTTP.

I agree.

3/ Last paragraph in 1.2 As information on RTP packet arrival times and pla=
y-out times can be considered reception quality feedback information, RTCP =
_is the appropriate conduit for delivery and playout delay information for =
IDMS._" Convert from proposal to standards language.

Ok.

4/ Second paragraph, section 1.3. Delete "one for the RTCP XR block type an=
d one for the new RTCP packet type." SDP parameters make the system work an=
d are not closely associated with these protocols.

I'm not sure what you mean here? The sentence is meant to indicate that thi=
s draft introduces two sets of SDP parameters: one for the new XR block typ=
e, and one for the new RTCP Packet Type (sections 9 and 10 respectively)

5/ Additional paragraph to append to 1.4, "The ETSI TISPAN protocol differs=
 in that RTCP XR block are used to convey playout and delivery delays as we=
ll as to send synchronization parameters to receivers. In this document, a =
new RTCP packet type is defined to convey high-resolution synchronization p=
arameters to receivers.

Ok.

6/ Packet Received NTP timestamp and Packet Received RTP timestamp definiti=
ons in section 6 and Packet Received NTP timestamp definition in section 7.=
 What IDMS really wants to measure is when all data for the indicated RTP t=
imestamp is available to the rendering application. We'd therefore like to =
know the arrival time of the last octet of the last packet associated with =
this RTP timestamp. There is difficulty reliably identifying the last packe=
t. We could defining this as the last packet before media clock advances bu=
t this does not appreciate out-of-order generation and reordering by the ne=
twork.

I'm not sure whether there is a functional difference between indicating th=
e arrival of the first packet or the last packet. Either way, what is calcu=
lated is delay. Of course jitter could result in the delay for the first pa=
cket and for the last packet to not be the same. However, this is not a sys=
tematic problem.

7/ In Packet Presented NTP timestamp definition in section 6, Clarify that =
presentation time does not include any intentionally introduced delay. Disc=
uss presentation estimates. Suggested replacement for the first sentence of=
 the definition: "This timestamp reflects the wall clock time at the earlie=
st moment the data contained in the first octet of the associated RTP packe=
t could be presented to the user if no IDMS-directed delay were introduced.=
 In some cases, due to additional delays in external equipment or sound pro=
pagation time through air, actual presentation time to the user may not be =
accurately knowable. For a comfortable media experience, it is preferable t=
o delay audio with respect to video than vise-versa. Pesimistic (longer) as=
sumptions about playout delay should be used for video and optimistic (shor=
ter) ones for audio."

I agree. I completely forgot our previous discussion on this topic. I will =
include this sentence in the next version.

8/ Clarify use of 0 value in Packet Presented NTP timestamp definition in s=
ection 6. If _no presentation timestamp is available_ then is shall be set =
to 0.

Ok.

9/  Packet Presented NTP timestamp in section 7. "This timestamp reflects t=
he wall clock time at the reference client at the moment the data contained=
 in the first octet of the associated RTP packet _should be presented_ to t=
he user. Change to directive language.

Ok.

10/ SyncGroupID definition in sections 9 and 10. Remove "in network byte or=
der" qualifier. This qualifier may cause confusion, is not necessary and is=
 not applied to attribute definitions in RFC 4566.

Ok.

11/ Editorial correction and clarification in section 13: "Normally, the pr=
ocessing and play-out of the same media stream by _similar_ receivers will =
take roughly the same amount of time. By synchronizing on packet arrival ti=
mes, you may _lose_ some accuracy, but it will be adequate for many applica=
tions,

Ok.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com<http://www.avanw.com/>, www.X192.org<http://ww=
w.X192.org>


This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div><font color=3D"#1F497D">Hi Kevin,</font></div>
<div><font color=3D"#1F497D">&nbsp;</font></div>
<div><font color=3D"#1F497D">Thanks for your extensive comments. My comment=
s inline. </font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font face=3D"Tahoma" size=3D"2"><span style=3D"font-size:10pt;"><b>Fr=
om:</b> avt-bounces@ietf.org [<a href=3D"mailto:avt-bounces@ietf.org">mailt=
o:avt-bounces@ietf.org</a>] <b>On Behalf Of </b>Kevin Gross<br>

<b>Sent:</b> maandag 12 december 2011 21:23<br>

<b>To:</b> avt@ietf.org<br>

<b>Subject:</b> [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02</=
span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">Here are some additional comments on the draft. Most of these are sugge=
stions for minor improvements. Items 6 and 7 represent significant technica=
l issues and may require discussion.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">1/ Chance all&nbsp;occurrences&nbsp;of &quot;play-out&quot; to &quot;pl=
ayout&quot;.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">Ok</font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">2/ First line of 1.2 &quot;Currently, most _interactive_ multimedia app=
lications make use of RTP and RTCP.&quot; Streaming applications commonly u=
se HTTP.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">I agree.</font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">3/ Last paragraph in 1.2&nbsp;As information on RTP packet&nbsp;arrival=
 times and play-out times can be considered reception quality&nbsp;feedback=
 information, RTCP _is the appropriate conduit for delivery
and playout delay information for IDMS._&quot; Convert from proposal to sta=
ndards language.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">Ok.</font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">4/ Second paragraph, section 1.3. Delete &quot;one for the RTCP XR bloc=
k type and one&nbsp;for the new RTCP packet type.&quot; SDP parameters make=
 the system work and are not closely associated with
these protocols.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">I&#8217;m not sure what you mean here? The sen=
tence is meant to indicate that this draft introduces two sets of SDP param=
eters: one for the new XR block type, and one for the new RTCP Packet Type =
(sections 9 and 10 respectively)</font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">5/ Additional&nbsp;paragraph&nbsp;to append to 1.4, &quot;The ETSI TISP=
AN protocol differs in that RTCP XR block are used to convey playout and de=
livery delays as well as to send synchronization parameters
to receivers.&nbsp;In this document, a new RTCP packet type is defined to c=
onvey high-resolution&nbsp;synchronization parameters to receivers.</span><=
/font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">Ok.</font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">6/&nbsp;Packet Received NTP timestamp and&nbsp;Packet Received RTP time=
stamp definitions in section 6 and Packet Received NTP timestamp definition=
 in section 7. What IDMS really wants to measure
is when all data for the indicated RTP timestamp is available to the render=
ing application. We'd therefore like to know the arrival time of the last o=
ctet of the last packet&nbsp;associated&nbsp;with this RTP timestamp. There=
 is difficulty reliably identifying the last
packet. We could defining this as the last packet before media clock advanc=
es but this does not&nbsp;appreciate&nbsp;out-of-order generation and reord=
ering by the network.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">I&#8217;m not sure whether there is a function=
al difference between indicating the arrival of the first packet or the las=
t packet. Either way, what is calculated is delay. Of course jitter could r=
esult in the delay for the first packet
and for the last packet to not be the same. However, this is not a systemat=
ic problem. </font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">7/ In Packet Presented NTP timestamp definition in section 6,&nbsp;Clar=
ify&nbsp;that presentation time does not include any intentionally introduc=
ed delay. Discuss presentation estimates. Suggested
replacement for the first&nbsp;sentence&nbsp;of the definition: &quot;This&=
nbsp;timestamp reflects the&nbsp;wall clock time at the earliest moment the=
 data contained in the first octet&nbsp;of the associated RTP packet could =
be presented to the user if no IDMS-directed delay were introduced.
In some cases, due to additional delays in external equipment or sound prop=
agation time through air, actual presentation time to the user may not be&n=
bsp;accurately&nbsp;knowable. For a comfortable media experience, it is pre=
ferable to delay audio with respect to video
than vise-versa. Pesimistic (longer) assumptions about playout delay should=
 be used for video and optimistic (shorter) ones for audio.&quot;</span></f=
ont></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">I agree. I completely forgot our previous disc=
ussion on this topic. I will include this sentence in the next version. </f=
ont></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">8/ Clarify use of 0 value in Packet Presented NTP timestamp definition =
in section 6. If _no&nbsp;presentation timestamp is available_ then is shal=
l be set to 0.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">Ok. </font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">9/&nbsp;&nbsp;Packet Presented NTP timestamp in section 7. &quot;This t=
imestamp reflects the&nbsp;wall clock time at the reference client at the m=
oment&nbsp;the data contained in the first octet of the associated
RTP packet _should be presented_ to&nbsp;the user. Change to directive lang=
uage.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">Ok.</font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">10/ SyncGroupID definition in sections 9 and 10. Remove &quot;in networ=
k byte order&quot; qualifier. This qualifier may cause confusion, is not ne=
cessary and is not applied to attribute definitions
in RFC 4566.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">Ok.</font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">11/ Editorial correction and clarification in section 13: &quot;Normall=
y, the&nbsp;processing and play-out of the same media stream by _similar_&n=
bsp;receivers will take roughly the same amount of time.
By synchronizing&nbsp;on packet arrival times, you may _lose_ some accuracy=
, but it will be&nbsp;adequate for many applications,</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3" color=3D"#1F497D"><span styl=
e=3D"font-size:12pt;">&nbsp;</span></font></div>
<div><font color=3D"#1F497D">Ok.</font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">Kevin Gross</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&#43;1-303-447-0517</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">Media Network Consultant</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">AVA Networks -&nbsp;<a href=3D"http://www.avanw.com/"><font color=3D"bl=
ue"><u>www.AVAnw.com</u></font></a>,&nbsp;<a href=3D"http://www.X192.org"><=
font color=3D"blue"><u>www.X192.org</u></font></a></span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size:12p=
t;">&nbsp;</span></font></div>
</span></font>
<font face=3D"monospace">This e-mail and its contents are subject to the DI=
SCLAIMER at http://www.tno.nl/emaildisclaimer</font></body>
</html>

--_000_FCC100FC8D6B034CB88CD8173B2DA158155F093EEXCMBX03tsntnon_--


From fboronat@dcom.upv.es  Thu Dec 15 09:21:26 2011
Return-Path: <fboronat@dcom.upv.es>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E29621F86EC for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 09:21:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IA7q6ua8RBSy for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 09:21:24 -0800 (PST)
Received: from marfik.cc.upv.es (marfik.cc.upv.es [158.42.249.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0A86A21F8678 for <avt@ietf.org>; Thu, 15 Dec 2011 09:21:22 -0800 (PST)
Received: from smtpx.upv.es (smtpxv.cc.upv.es [158.42.249.46]) by marfik.cc.upv.es (8.13.6/8.13.6) with ESMTP id pBFHLKBp023462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <avt@ietf.org>; Thu, 15 Dec 2011 18:21:20 +0100
Received: from smtp.upv.es (celaeno.cc.upv.es [158.42.249.55]) by smtpx.upv.es (8.14.3/8.14.3) with ESMTP id pBFHLUFD001043 for <avt@ietf.org>; Thu, 15 Dec 2011 18:21:30 +0100
Received: from [127.0.0.1] (fboronat2114.pc.upv.es [158.42.145.157]) by smtp.upv.es (8.13.6/8.13.6) with ESMTP id pBFHLIbR021661 for <avt@ietf.org>; Thu, 15 Dec 2011 18:21:19 +0100
Message-ID: <4EEA2C8D.5080909@dcom.upv.es>
Date: Thu, 15 Dec 2011 18:21:17 +0100
From: =?windows-1252?Q?Fernando_Boronat_Segu=ED?= <fboronat@dcom.upv.es>
Organization: UNIVERSIDAD =?windows-1252?Q?POLIT=C9CNICA_DE_VALENCIA?=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: fboronat@dcom.upv.es
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2011 17:21:27 -0000

Hi,

I write this mail on behalf of Mario Montagud and Fernando Boronat

Our comments are below with [F&M]

Regards



Here are some additional comments on the draft. Most of these are
suggestions for minor improvements. Items 6 and 7 represent significant
technical issues and may require discussion.

1/ Chance all occurrences of "play-out" to "playout".

[F&M] OK, we usually use playout in our papers. On the other hand, we 
are currently studying some media players and in their documentation we 
have found ‘playback’ instead of ‘playout’.


2/ First line of 1.2 "Currently, most _interactive_ multimedia applications
make use of RTP and RTCP." Streaming applications commonly use HTTP.

[F&M] Maybe we can also put: “Currently, many interactive multimedia 
applications make use of RTP and RTCP”


3/ Last paragraph in 1.2 As information on RTP packet arrival times and
play-out times can be considered reception quality feedback information,
RTCP _is the appropriate conduit for delivery and playout delay information
for IDMS._" Convert from proposal to standards language.


[F&M] We agree.


4/ Second paragraph, section 1.3. Delete "one for the RTCP XR block type
and one for the new RTCP packet type." SDP parameters make the system work
and are not closely associated with these protocols.

[F&M] We agree because both types are not defined yet. We can delete 
that sentence or use an alternative like this: “This document describes 
two SDP parameters for doing this, one for the RTCP XR block type and 
one for the new RTCP packet type (both types will described in Sections 
6 and 7, respectively, and the associated SDP parameters are presented 
in Sections 9 and 10, respectively)”.


5/ Additional paragraph to append to 1.4, "The ETSI TISPAN protocol differs
in that RTCP XR block are used to convey playout and delivery delays as
well as to send synchronization parameters to receivers. In this document,
a new RTCP packet type is defined to convey high-resolution synchronization
parameters to receivers.

[F&M] OK, although Section 12 presents the compatibility between ETSI 
TISPAN and this I-D.

6/ Packet Received NTP timestamp and Packet Received RTP timestamp
definitions in section 6 and Packet Received NTP timestamp definition in
section 7. What IDMS really wants to measure is when all data for the
indicated RTP timestamp is available to the rendering application. We'd
therefore like to know the arrival time of the last octet of the last
packet associated with this RTP timestamp.

[F&M] You are right.

There is difficulty reliably identifying the last packet. We could 
defining this as the last packet before media clock advances but this 
does not appreciate out-of-order generation and reordering by the network.

[F&M] We are not sure what you mean here. We should discuss this issue 
but we think we should define it as the last received RTP packet among 
all the sent RTP packets with the same RTP timestamp (regardless of its 
sequence number).


7/ In Packet Presented NTP timestamp definition in section 6, Clarify that
presentation time does not include any intentionally introduced delay.
Discuss presentation estimates. Suggested replacement for the
first sentence of the definition: "This timestamp reflects the wall clock
time at the earliest moment the data contained in the first octet of the
associated RTP packet could be presented to the user if no IDMS-directed
delay were introduced.

[F&M] We thought that it was implied but we agree.

In some cases, due to additional delays in external
equipment or sound propagation time through air, actual presentation time
to the user may not be accurately knowable. For a comfortable media
experience, it is preferable to delay audio with respect to video than
vise-versa. Pesimistic (longer) assumptions about playout delay should be
used for video and optimistic (shorter) ones for audio."

[F&M] We are not sure about including these sentences in the I-D but if 
you have already discussed it before, it is up to you.


8/ Clarify use of 0 value in Packet Presented NTP timestamp definition in
section 6. If _no presentation timestamp is available_ then is shall be set
to 0.

[F&M] OK

9/ Packet Presented NTP timestamp in section 7. "This timestamp reflects
the wall clock time at the reference client at the moment the data
contained in the first octet of the associated RTP packet _should be
presented_ to the user. Change to directive language.

[F&M] OK

10/ SyncGroupID definition in sections 9 and 10. Remove "in network byte
order" qualifier. This qualifier may cause confusion, is not necessary and
is not applied to attribute definitions in RFC 4566.

[F&M] OK


11/ Editorial correction and clarification in section 13: "Normally,
the processing and play-out of the same media stream by _similar_ receivers
will take roughly the same amount of time. By synchronizing on packet
arrival times, you may _lose_ some accuracy, but it will be adequate for
many applications,
[F&M] OK


Fernando and Mario


Regards
========================================================================
Dr. Fernando Boronat Seguí
Profesor Titular / Lecturer	
Dept. Comunicaciones           Tlf.-+34+962 849 300 Ext.-49341
Tlf. directo -+34+962 849 341  Fax.-+34+962 849 309 (Compartido)
UNIVERSIDAD POLITÉCNICA DE VALENCIA-CAMPUS DE GANDIA
Calle Pararaninfo, 1, CP. 46730, Grao de Gandia (Valencia), SPAIN
========================================================================



From kevin.gross@avanw.com  Thu Dec 15 10:29:48 2011
Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79C6321F8B01 for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 10:29:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.757
X-Spam-Level: 
X-Spam-Status: No, score=-0.757 tagged_above=-999 required=5 tests=[AWL=0.885,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s8GjisO4iHKM for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 10:29:47 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id BAACF21F8AFC for <avt@ietf.org>; Thu, 15 Dec 2011 10:29:47 -0800 (PST)
Received: (qmail 27729 invoked by uid 0); 15 Dec 2011 18:29:25 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by cpoproxy3.bluehost.com with SMTP; 15 Dec 2011 18:29:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:To:From:Subject:Message-ID:Date:MIME-Version; bh=lL3kA/qd2yQbtCIIoWvya60c+I+fStGOpybSLAwmspk=;  b=NLB1JZ/7TG5qZmUK0ZzaqL5txEL9qck3sJDevSM4mLOQ2UXIcqlZ7Zr/LINT63r0Wz1NLWv5hXCjuQ27pkZ1uNr4w3/HnDmYj3RxU7yD7AmPnHhZ2/DAENpu55pAexXe;
Received: from mail-fx0-f44.google.com ([209.85.161.44]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1RbG3Y-0005BY-R4 for avt@ietf.org; Thu, 15 Dec 2011 11:29:25 -0700
Received: by faas1 with SMTP id s1so2925692faa.31 for <avt@ietf.org>; Thu, 15 Dec 2011 10:29:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.109.106 with SMTP id hr10mr6998728wib.62.1323973763317; Thu, 15 Dec 2011 10:29:23 -0800 (PST)
Received: by 10.223.102.129 with HTTP; Thu, 15 Dec 2011 10:29:23 -0800 (PST)
Date: Thu, 15 Dec 2011 11:29:23 -0700
Message-ID: <CALw1_Q3bvuKxGtn+ZbWX11fTxNABmo-kk79bPqUEE+sbYZ9LUQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "avt@ietf.org" <avt@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8f3b9da5dabe5904b425a94a
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.161.44 authed with kevin.gross@avanw.com}
Subject: Re: [AVTCORE] Comment 4: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2011 18:29:48 -0000

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

My comment was trying to convey that I did not consider there to be a close
association between the SDP attributes and the XR and RTCP packets. I've
reread and now appreciate that there is for rtcp-xr:grp-sync and tcp-idms.

It is the clocksource attribute that does not have such an association. I
understand the plan is to move this into a draft Aidan is working on.

I'm OK to leave section 1.3 as is or accept Mario Montagud and Fernando
Boronat's suggested improvement.

Kevin Gross

On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ray) van <
ray.vanbrandenburg@tno.nl> wrote:

>  4/ Second paragraph, section 1.3. Delete "one for the RTCP XR block type
> and one for the new RTCP packet type." SDP parameters make the system wor=
k
> and are not closely associated with these protocols.
>
> I=92m not sure what you mean here? The sentence is meant to indicate that
> this draft introduces two sets of SDP parameters: one for the new XR bloc=
k
> type, and one for the new RTCP Packet Type (sections 9 and 10 respectivel=
y)
>
>
[F&M] We agree because both types are not defined yet. We can delete that
sentence or use an alternative like this: =93This document describes two SD=
P
parameters for doing this, one for the RTCP XR block type and one for the
new RTCP packet type (both types will described in Sections 6 and 7,
respectively, and the associated SDP parameters are presented in Sections 9
and 10, respectively)=94.

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

<div>My comment was trying to convey that I did not consider there to be a =
close association between the SDP attributes and the XR and RTCP packets. I=
&#39;ve reread and now appreciate that there is for rtcp-xr:grp-sync and tc=
p-idms.</div>
<div><br></div><div>It is the clocksource attribute that does not have such=
 an association. I understand the plan is to move this into a draft Aidan i=
s working on.</div><div><br></div><div>I&#39;m OK to leave section 1.3 as i=
s or accept=A0<span class=3D"Apple-style-span" style>Mario Montagud and Fer=
nando Boronat&#39;s suggested improvement.</span></div>
<div><span class=3D"Apple-style-span" style><br></span></div><div><span cla=
ss=3D"Apple-style-span" style>Kevin Gross</span></div><br><div class=3D"gma=
il_quote">On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ray) van <span =
dir=3D"ltr">&lt;<a href=3D"mailto:ray.vanbrandenburg@tno.nl">ray.vanbranden=
burg@tno.nl</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">






<div>

<div style=3D"font-family:Calibri;font-size:11pt"><span class=3D"Apple-styl=
e-span" style=3D"font-family:&#39;Times New Roman&#39;;font-size:16px">4/ S=
econd paragraph, section 1.3. Delete &quot;one for the RTCP XR block type a=
nd one=A0for the new RTCP packet type.&quot; SDP parameters make the system=
 work and are not closely associated with
these protocols.</span></div><div class=3D"im">
<div style=3D"font-family:Calibri;font-size:11pt"><font face=3D"Times New R=
oman" size=3D"3" color=3D"#1F497D"><span style=3D"font-size:12pt">=A0</span=
></font></div>
</div><div style=3D"font-family:Calibri;font-size:11pt"><font color=3D"#1F4=
97D">I=92m not sure what you mean here? The sentence is meant to indicate t=
hat this draft introduces two sets of SDP parameters: one for the new XR bl=
ock type, and one for the new RTCP Packet Type (sections 9 and 10 respectiv=
ely)</font></div>
<div class=3D"im">
<div style=3D"font-family:Calibri;font-size:11pt"><font face=3D"Times New R=
oman" size=3D"3"><span style=3D"font-size:12pt">=A0</span></font></div></di=
v></div></blockquote><div><span class=3D"Apple-style-span" style>[F&amp;M] =
We agree because both types are not defined yet. We can delete that sentenc=
e or use an alternative like this: =93This document describes two SDP param=
eters for doing this, one for the RTCP XR block type and one for the new RT=
CP packet type (both types will described in Sections 6 and 7, respectively=
, and the associated SDP parameters are presented in Sections 9 and 10, res=
pectively)=94.</span>=A0</div>
</div>

--e89a8f3b9da5dabe5904b425a94a--

From kevin.gross@avanw.com  Thu Dec 15 11:08:33 2011
Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAF4121F84AE for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 11:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.456
X-Spam-Level: 
X-Spam-Status: No, score=-0.456 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id beIT4XVwuUkq for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 11:08:33 -0800 (PST)
Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by ietfa.amsl.com (Postfix) with SMTP id 2F1FB21F84A9 for <avt@ietf.org>; Thu, 15 Dec 2011 11:08:32 -0800 (PST)
Received: (qmail 20447 invoked by uid 0); 15 Dec 2011 19:08:09 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy3.bluehost.com with SMTP; 15 Dec 2011 19:08:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=oTJba2OylXp49etcwVlIyBaVmsisKJNnlitf76ISyQg=;  b=IzEykCPwuF+0iVIh/3zThXZh8KN+5kvWk9SbOwQbJjsH+1MhADHKLSrPtTds9f1FwPrvOsG1EnovUzy0W7rZe8byJEPbScFGj6rHhwdCR+XUDlEdXX6X+3XwWW5e2g/5;
Received: from mail-ee0-f44.google.com ([74.125.83.44]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1RbGf2-0003r9-P8 for avt@ietf.org; Thu, 15 Dec 2011 12:08:09 -0700
Received: by eekc14 with SMTP id c14so1168764eek.31 for <avt@ietf.org>; Thu, 15 Dec 2011 11:08:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.109.106 with SMTP id hr10mr7299028wib.62.1323976087395; Thu, 15 Dec 2011 11:08:07 -0800 (PST)
Received: by 10.223.102.129 with HTTP; Thu, 15 Dec 2011 11:08:07 -0800 (PST)
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA158155F093E@EXC-MBX03.tsn.tno.nl>
References: <CALw1_Q3XG3jcWFk5F_7fvARX1HLzfvNT=O64kReB-cH2Xqqr_Q@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F093E@EXC-MBX03.tsn.tno.nl>
Date: Thu, 15 Dec 2011 12:08:07 -0700
Message-ID: <CALw1_Q2bSn6x_dHpO2KOSWkkC5ryjx8vVr2F+qywE76sz-uT9A@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "avt@ietf.org" <avt@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8f3b9da5615c8a04b42634db
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 74.125.83.44 authed with kevin.gross@avanw.com}
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2011 19:08:33 -0000

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

I believe what we want to measure is the interval between
the origination time for the first octet of packets at the sender and the
time the receiver has usable data. I believe the safe assumption is that
the receiver does not have usable data for a particular RTP timestamp until
he is sure he has received the last octet of the last packet associated
with that timestamp.

We can leave things as currently proposed, timestamp the first octet of the
first packet and assume that with all other receivers timestamping in the
same manner, synchronization based on packet receipt timestamps will work
out.

Or we can suggest a way to timestamp the last octet of the last packet.
Timestamping the last octet as oppose to the first is actually easier
because that's where the network interface will typically generate an
interrupt. Identifying the last packet in the presence of reordering and
packet loss is a bit tricky. I can make a more fully-formed proposal, but
before going to the trouble I'd like to get agreement on what we want to be
measuring here.

Kevin Gross

On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ray) van <
ray.vanbrandenburg@tno.nl> wrote:

>
> 6/ Packet Received NTP timestamp and Packet Received RTP timestamp
> definitions in section 6 and Packet Received NTP timestamp definition in
> section 7. What IDMS really wants to measure is when all data for the
> indicated RTP timestamp is available to the rendering application. We'd
> therefore like to know the arrival time of the last octet of the last
> packet associated with this RTP timestamp. There is difficulty reliably
> identifying the last packet. We could defining this as the last packet
> before media clock advances but this does not appreciate out-of-order
> generation and reordering by the network.
>
> I=92m not sure whether there is a functional difference between indicatin=
g
> the arrival of the first packet or the last packet. Either way, what is
> calculated is delay. Of course jitter could result in the delay for the
> first packet and for the last packet to not be the same. However, this is
> not a systematic problem.
>
> [F&M] You are right.

[F&M] We are not sure what you mean here. We should discuss this issue but
we think we should define it as the last received RTP packet among all the
sent RTP packets with the same RTP timestamp (regardless of its sequence
number).

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

<div>I=A0believe=A0what we want to measure is the interval between the=A0or=
igination=A0time for the first octet of packets at the sender and the time =
the receiver has usable data. I=A0believe=A0the safe assumption is that the=
 receiver does not have usable data for a particular RTP timestamp until he=
 is sure he has received the last octet of the last packet associated with =
that timestamp.</div>
<div><br></div><div>We can leave things as currently proposed, timestamp th=
e first octet of the first packet and assume that with all other receivers =
timestamping in the same manner, synchronization based on packet receipt ti=
mestamps will work out.<div>
<br></div><div>Or we can suggest a way to timestamp the last octet of the l=
ast packet. Timestamping the last octet as oppose to the first is actually =
easier because that&#39;s where the network interface will typically genera=
te an interrupt. Identifying the last packet in the=A0presence=A0of=A0reord=
ering=A0and packet loss is a bit tricky. I can make a more fully-formed pro=
posal, but before going to the trouble I&#39;d like to get agreement on wha=
t we want to be measuring here.<div>
<br clear=3D"all">Kevin Gross<br><div><br></div><div class=3D"gmail_quote">=
On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ray) van <span dir=3D"ltr=
">&lt;<a href=3D"mailto:ray.vanbrandenburg@tno.nl">ray.vanbrandenburg@tno.n=
l</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">






<div>

<div style=3D"font-family:Calibri;font-size:11pt"><span class=3D"Apple-styl=
e-span" style=3D"color:rgb(31,73,125);font-family:&#39;Times New Roman&#39;=
;font-size:16px">=A0</span></div><div class=3D"im">
<div style=3D"font-family:Calibri;font-size:11pt"><font face=3D"Times New R=
oman" size=3D"3"><span style=3D"font-size:12pt">6/=A0Packet Received NTP ti=
mestamp and=A0Packet Received RTP timestamp definitions in section 6 and Pa=
cket Received NTP timestamp definition in section 7. What IDMS really wants=
 to measure
is when all data for the indicated RTP timestamp is available to the render=
ing application. We&#39;d therefore like to know the arrival time of the la=
st octet of the last packet=A0associated=A0with this RTP timestamp. There i=
s difficulty reliably identifying the last
packet. We could defining this as the last packet before media clock advanc=
es but this does not=A0appreciate=A0out-of-order generation and reordering =
by the network.</span></font></div>
<div style=3D"font-family:Calibri;font-size:11pt"><font face=3D"Times New R=
oman" size=3D"3" color=3D"#1F497D"><span style=3D"font-size:12pt">=A0</span=
></font></div>
</div><div style=3D"font-family:Calibri;font-size:11pt"><font color=3D"#1F4=
97D">I=92m not sure whether there is a functional difference between indica=
ting the arrival of the first packet or the last packet. Either way, what i=
s calculated is delay. Of course jitter could result in the delay for the f=
irst packet
and for the last packet to not be the same. However, this is not a systemat=
ic problem. </font></div><div class=3D"im">
<div><font class=3D"Apple-style-span" face=3D"&#39;Times New Roman&#39;" si=
ze=3D"3"><br></font></div></div></div></blockquote><span class=3D"Apple-sty=
le-span" style>[F&amp;M] You are right.</span><div class=3D"im" style><br><=
span class=3D"Apple-style-span" style=3D"color:rgb(34,34,34)">[F&amp;M] We =
are not sure what you mean here. We should discuss this issue but we think =
we should define it as the last received RTP packet among all the sent RTP =
packets with the same RTP timestamp (regardless of its sequence number).</s=
pan><span class=3D"Apple-style-span" style=3D"color:rgb(0,0,0);font-family:=
arial;font-size:small">=A0</span></div>
</div></div></div></div>

--e89a8f3b9da5615c8a04b42634db--

From bill.wu@huawei.com  Thu Dec 15 17:50:58 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E93E21F8562 for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 17:50:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.777
X-Spam-Level: 
X-Spam-Status: No, score=-5.777 tagged_above=-999 required=5 tests=[AWL=-0.063, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVytyFH-eQNb for <avt@ietfa.amsl.com>; Thu, 15 Dec 2011 17:50:57 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 253C421F8560 for <avt@ietf.org>; Thu, 15 Dec 2011 17:50:57 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW9008JDX4PSZ@szxga05-in.huawei.com> for avt@ietf.org; Fri, 16 Dec 2011 09:50:49 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW9008BXX4OBF@szxga05-in.huawei.com> for avt@ietf.org; Fri, 16 Dec 2011 09:50:49 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFS76519; Fri, 16 Dec 2011 09:50:47 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 16 Dec 2011 09:50:41 +0800
Received: from w53375q (10.138.41.130) by szxeml411-hub.china.huawei.com (10.82.67.138) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 16 Dec 2011 09:50:28 +0800
Date: Fri, 16 Dec 2011 09:50:27 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Kevin Gross <kevin.gross@avanw.com>, avt@ietf.org
Message-id: <65A4736CE8B345C5A49604E36F37C112@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_Glj1OHjWYQh1GNzChQRl/A)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <CALw1_Q3bvuKxGtn+ZbWX11fTxNABmo-kk79bPqUEE+sbYZ9LUQ@mail.gmail.com>
Subject: Re: [AVTCORE] Comment 4: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 01:50:58 -0000

--Boundary_(ID_Glj1OHjWYQh1GNzChQRl/A)
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: 7BIT

Hi,
----- Original Message ----- 
>From: Kevin Gross 
>To: avt@ietf.org 
>Sent: Friday, December 16, 2011 2:29 AM
>Subject: Re: [AVTCORE] Comment 4: draft-ietf-avtcore-idms-02


>My comment was trying to convey that I did not consider there to be a close association between the SDP attributes and the XR and RTCP packets. I've reread and now appreciate >that there is for rtcp->xr:grp-sync and tcp-idms.

[Qin]: I assume you suggest to define xr-format as follows:

                    xr-format =/ rtcp-idms                   
                    rtcp-idms = "rtcp-idms" ":" [sync-grp] CRLF
I think that's a issue needing to be fixed. Also XR and new packets share the same SDP attribute parameter "rtcp-idms".
Maybe it will be reasonable to define xr-format as follows:
                    
            xr-format =/ rtcp-xr-idms                   
            rtcp-xr-idms = "rtcp-xr-idms" ":" [sync-grp] CRLF

to distinguish from SDP Parameter for RTCP IDMS Packet Type.

As for [syn-grp], I am interested to know who generate SyncGroupId? How it is generated? Is it same as Media Stream Correlation Identifier carried in the XR or RTCP IDMS packet?
or if not, how they are mapped?

>It is the clocksource attribute that does not have such an association. I understand the plan is to move this into a draft Aidan is working on.

[Qin]: In my view, since SDP attribute for both XR and RTCP IDMS packet share the same SyncGroupId?
I think it is possible and more general to associate [syn-grp] with clocksource attribute.

--Boundary_(ID_Glj1OHjWYQh1GNzChQRl/A)
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=Windows-1252" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19154">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=Apple-style-span>Hi,</SPAN></DIV>
<DIV><SPAN class=Apple-style-span>----- Original Message ----- </DIV></SPAN>
<DIV><SPAN class=Apple-style-span>&gt;From: Kevin Gross <BR>&gt;To: <A 
href="mailto:avt@ietf.org">avt@ietf.org</A> <BR>&gt;Sent: Friday, December 16, 
2011 2:29 AM<BR>&gt;Subject: Re: [AVTCORE] Comment 4: 
draft-ietf-avtcore-idms-02</SPAN></DIV>
<DIV>&nbsp;</DIV><SPAN class=Apple-style-span>
<DIV><BR>&gt;My comment was trying to convey that I did not consider there to be 
a close association between the SDP attributes and the XR and RTCP packets. I've 
reread and now appreciate &gt;that there is for rtcp-&gt;xr:grp-sync and 
tcp-idms.</DIV>
<DIV>&nbsp;</DIV>
<DIV>[Qin]: I assume you suggest to define xr-format as follows:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
xr-format 
=/&nbsp;rtcp-idms&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rtcp-idms 
= "rtcp-idms" ":" [sync-grp] CRLF<BR>I think that's&nbsp;a issue&nbsp;needing 
to&nbsp;be fixed. Also XR and new packets share the same SDP attribute parameter 
"rtcp-idms".</DIV>
<DIV>Maybe it will be reasonable to define xr-format as follows:</DIV>
<DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
xr-format 
=/&nbsp;rtcp-xr-idms&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
rtcp-xr-idms = "rtcp-xr-idms" ":" [sync-grp] CRLF<BR></DIV></DIV>
<DIV>to distinguish from SDP Parameter for RTCP IDMS Packet Type.</DIV>
<DIV>&nbsp;</DIV>
<DIV>As for [syn-grp], I am interested to know&nbsp;who 
generate&nbsp;SyncGroupId? How it is generated?&nbsp;Is it same as Media Stream 
Correlation Identifier&nbsp;carried in the XR or RTCP IDMS packet?</DIV>
<DIV>or if not, how they are mapped?</DIV><FONT size=2 face=&#23435;&#20307;></FONT>
<DIV><BR>&gt;It is the clocksource attribute that does not have such an 
association. I understand the plan is to move this into a draft Aidan is working 
on.<BR></DIV>
<DIV>[Qin]: In my view, since SDP attribute for both XR and RTCP IDMS packet 
share the same SyncGroupId?</DIV>
<DIV>I think it&nbsp;is possible&nbsp;and&nbsp;more general to associate 
[syn-grp] with clocksource attribute.</DIV></SPAN></BODY></HTML>

--Boundary_(ID_Glj1OHjWYQh1GNzChQRl/A)--

From kpfleming@digium.com  Fri Dec 16 09:21:40 2011
Return-Path: <kpfleming@digium.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4020721F8B73 for <avt@ietfa.amsl.com>; Fri, 16 Dec 2011 09:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcmPEiQ7+iuM for <avt@ietfa.amsl.com>; Fri, 16 Dec 2011 09:21:39 -0800 (PST)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id 288F921F8B72 for <avt@ietf.org>; Fri, 16 Dec 2011 09:21:39 -0800 (PST)
Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1RbbTW-0000b7-HC for avt@ietf.org; Fri, 16 Dec 2011 11:21:38 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 83C92D8005 for <avt@ietf.org>; Fri, 16 Dec 2011 11:21:38 -0600 (CST)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSfrtde1cB6f for <avt@ietf.org>; Fri, 16 Dec 2011 11:21:38 -0600 (CST)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id 2FCBED8002 for <avt@ietf.org>; Fri, 16 Dec 2011 11:21:38 -0600 (CST)
Message-ID: <4EEB7E21.5070707@digium.com>
Date: Fri, 16 Dec 2011 11:21:37 -0600
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: avt@ietf.org
References: <CAFLon=K8phF53nc7vrL5hPg2q1zq7up1yeV+uXVpemfKbiw4Aw@mail.gmail.com>
In-Reply-To: <CAFLon=K8phF53nc7vrL5hPg2q1zq7up1yeV+uXVpemfKbiw4Aw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [AVTCORE] Need Clarification on SSRC Usage in RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 17:21:40 -0000

On 12/14/2011 04:23 AM, ramesh kumar wrote:
> Hi All,
> I have a question on SSRC usage in RTP:
> As per RFC 3550,
>   The SSRC identifier is a
>        randomly chosen value meant to be globally unique within a
>        particular RTP session.  A participant need not
>        use the same SSRC identifier for all the RTP sessions in a
>        multimedia session.
> Question:  Is there any possibility of SSRC Identifier be same across
> consecutive RTP Sessions ? Does Standard emphasis on this ?

There is no definition of 'consecutive' that can be derived from the 
RFCs, so I assume that what you mean is "is it possible that the same 
SSRC identifier could appear in two RTP sessions that occur near each 
other in time?", and the answer is 'yes'. In fact, the same SSRC 
identifier could even appear in two simultaneous RTP sessions that are 
part of distinct SIP/H.323/etc. sessions.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

From ray.vanbrandenburg@tno.nl  Mon Dec 19 01:16:32 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4CC21F8B45 for <avt@ietfa.amsl.com>; Mon, 19 Dec 2011 01:16:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xl+DD4zpUrbC for <avt@ietfa.amsl.com>; Mon, 19 Dec 2011 01:16:29 -0800 (PST)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 47CA221F8B44 for <avt@ietf.org>; Mon, 19 Dec 2011 01:16:29 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.71,375,1320620400"; d="scan'208,217";a="61990083"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.221]) by mailhost1a.tno.nl with ESMTP; 19 Dec 2011 10:16:23 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.242]) by EXC-CASHUB02.tsn.tno.nl ([134.221.225.221]) with mapi id 14.01.0323.003; Mon, 19 Dec 2011 10:16:22 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: Kevin Gross <kevin.gross@avanw.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
Thread-Index: AQHMuQvz+3wC97PPk0GZDWSIW5lKWpXcmkOAgACco4CABbFHUA==
Date: Mon, 19 Dec 2011 09:16:22 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA158155F5214@EXC-MBX03.tsn.tno.nl>
References: <CALw1_Q3XG3jcWFk5F_7fvARX1HLzfvNT=O64kReB-cH2Xqqr_Q@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F093E@EXC-MBX03.tsn.tno.nl> <CALw1_Q2bSn6x_dHpO2KOSWkkC5ryjx8vVr2F+qywE76sz-uT9A@mail.gmail.com>
In-Reply-To: <CALw1_Q2bSn6x_dHpO2KOSWkkC5ryjx8vVr2F+qywE76sz-uT9A@mail.gmail.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.153]
Content-Type: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA158155F5214EXCMBX03tsntnon_"
MIME-Version: 1.0
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 09:16:32 -0000

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

Hi Kevin,

I think the question here is whether there is reason for there to be a syst=
ematic difference in transport delay between the first octet and the last o=
ctet (i.e. is there a reason for the last octet of an RTP packet to always =
take longer than the first octet?).

Of course jitter might cause some octets to experience a slightly longer or=
 shorter delay than others, but I don't believe there is a reason to assume=
 this is systematic. If this is the case, then I don't see a reason to furt=
her complicate things by measuring the packet arrival of the last octet ins=
tead of the first.

It is important to note that IDMS will always be, by its very nature, sligh=
tly behind the facts. Apart from the fact that it would not be very useful/=
scalable, RTCP rules out reporting on every single RTP packet. This means t=
hat IDMS will only use measure the delay of some subset of all RTP packets.=
 It therefore don't think it matters whether this measurement happens on th=
e first or the last octet, as long as every receiver does it in the same wa=
y.

Ray


From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Kevin=
 Gross
Sent: donderdag 15 december 2011 20:08
To: avt@ietf.org
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02

I believe what we want to measure is the interval between the origination t=
ime for the first octet of packets at the sender and the time the receiver =
has usable data. I believe the safe assumption is that the receiver does no=
t have usable data for a particular RTP timestamp until he is sure he has r=
eceived the last octet of the last packet associated with that timestamp.

We can leave things as currently proposed, timestamp the first octet of the=
 first packet and assume that with all other receivers timestamping in the =
same manner, synchronization based on packet receipt timestamps will work o=
ut.

Or we can suggest a way to timestamp the last octet of the last packet. Tim=
estamping the last octet as oppose to the first is actually easier because =
that's where the network interface will typically generate an interrupt. Id=
entifying the last packet in the presence of reordering and packet loss is =
a bit tricky. I can make a more fully-formed proposal, but before going to =
the trouble I'd like to get agreement on what we want to be measuring here.

Kevin Gross

On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ray) van <ray.vanbrandenb=
urg@tno.nl<mailto:ray.vanbrandenburg@tno.nl>> wrote:

6/ Packet Received NTP timestamp and Packet Received RTP timestamp definiti=
ons in section 6 and Packet Received NTP timestamp definition in section 7.=
 What IDMS really wants to measure is when all data for the indicated RTP t=
imestamp is available to the rendering application. We'd therefore like to =
know the arrival time of the last octet of the last packet associated with =
this RTP timestamp. There is difficulty reliably identifying the last packe=
t. We could defining this as the last packet before media clock advances bu=
t this does not appreciate out-of-order generation and reordering by the ne=
twork.

I'm not sure whether there is a functional difference between indicating th=
e arrival of the first packet or the last packet. Either way, what is calcu=
lated is delay. Of course jitter could result in the delay for the first pa=
cket and for the last packet to not be the same. However, this is not a sys=
tematic problem.

[F&M] You are right.

[F&M] We are not sure what you mean here. We should discuss this issue but =
we think we should define it as the last received RTP packet among all the =
sent RTP packets with the same RTP timestamp (regardless of its sequence nu=
mber).
This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"NL" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Kevin,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I think th=
e question here is whether there is reason for there to be a systematic dif=
ference in transport delay between the first octet and the
 last octet (i.e. is there a reason for the last octet of an RTP packet to =
always take longer than the first octet?).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Of course =
jitter might cause some octets to experience a slightly longer or shorter d=
elay than others, but I don&#8217;t believe there is a reason to
 assume this is systematic. If this is the case, then I don&#8217;t see a r=
eason to further complicate things by measuring the packet arrival of the l=
ast octet instead of the first.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">It is impo=
rtant to note that IDMS will always be, by its very nature, slightly behind=
 the facts. Apart from the fact that it would not be very
 useful/scalable, RTCP rules out reporting on every single RTP packet. This=
 means that IDMS will only use measure the delay of some subset of all RTP =
packets. It therefore don&#8217;t think it matters whether this measurement=
 happens on the first or the last octet,
 as long as every receiver does it in the same way. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ray<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]
<b>On Behalf Of </b>Kevin Gross<br>
<b>Sent:</b> donderdag 15 december 2011 20:08<br>
<b>To:</b> avt@ietf.org<br>
<b>Subject:</b> Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-=
02<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal">I&nbsp;believe&nbsp;what we want to measure is the i=
nterval between the&nbsp;origination&nbsp;time for the first octet of packe=
ts at the sender and the time the receiver has usable data. I&nbsp;believe&=
nbsp;the safe assumption is that the receiver does not have usable
 data for a particular RTP timestamp until he is sure he has received the l=
ast octet of the last packet associated with that timestamp.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We can leave things as currently proposed, timestamp=
 the first octet of the first packet and assume that with all other receive=
rs timestamping in the same manner, synchronization based on packet receipt=
 timestamps will work out.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Or we can suggest a way to timestamp the last octet =
of the last packet. Timestamping the last octet as oppose to the first is a=
ctually easier because that's where the network interface will typically ge=
nerate an interrupt. Identifying the
 last packet in the&nbsp;presence&nbsp;of&nbsp;reordering&nbsp;and packet l=
oss is a bit tricky. I can make a more fully-formed proposal, but before go=
ing to the trouble I'd like to get agreement on what we want to be measurin=
g here.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
Kevin Gross<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ra=
y) van &lt;<a href=3D"mailto:ray.vanbrandenburg@tno.nl">ray.vanbrandenburg@=
tno.nl</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"colo=
r:#1F497D">&nbsp;</span></span><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">6/&nbsp;Packet Received NTP timestamp and&nbsp;Packe=
t Received RTP timestamp definitions in section 6 and Packet Received NTP t=
imestamp definition in section 7. What IDMS really wants to measure is when=
 all data for the indicated RTP timestamp is
 available to the rendering application. We'd therefore like to know the ar=
rival time of the last octet of the last packet&nbsp;associated&nbsp;with t=
his RTP timestamp. There is difficulty reliably identifying the last packet=
. We could defining this as the last packet
 before media clock advances but this does not&nbsp;appreciate&nbsp;out-of-=
order generation and reordering by the network.<span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I&#8217;m not sure whethe=
r there is a functional difference between indicating the arrival of the fi=
rst packet or the last packet. Either way, what is calculated
 is delay. Of course jitter could result in the delay for the first packet =
and for the last packet to not be the same. However, this is not a systemat=
ic problem.
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span">[F&amp;M] You are r=
ight.</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<span class=3D"apple-style-span"><span style=3D"color:#222222">[F&amp;M] We=
 are not sure what you mean here. We should discuss this issue but we think=
 we should define it as the last received RTP packet among all the sent RTP=
 packets with the same RTP timestamp (regardless
 of its sequence number).</span></span><span class=3D"apple-style-span"><sp=
an style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blac=
k">&nbsp;</span></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<font face=3D"monospace">This e-mail and its contents are subject to the DI=
SCLAIMER at http://www.tno.nl/emaildisclaimer</font></body>
</html>

--_000_FCC100FC8D6B034CB88CD8173B2DA158155F5214EXCMBX03tsntnon_--


From ray.vanbrandenburg@tno.nl  Mon Dec 19 01:18:26 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC6E521F8A6F for <avt@ietfa.amsl.com>; Mon, 19 Dec 2011 01:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xm-ZamRg-9EJ for <avt@ietfa.amsl.com>; Mon, 19 Dec 2011 01:18:26 -0800 (PST)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 7FAC121F88A0 for <avt@ietf.org>; Mon, 19 Dec 2011 01:18:25 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.71,375,1320620400"; d="scan'208,217";a="61990222"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1a.tno.nl with ESMTP; 19 Dec 2011 10:18:24 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.242]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.01.0323.003; Mon, 19 Dec 2011 10:18:24 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: Qin Wu <bill.wu@huawei.com>, Kevin Gross <kevin.gross@avanw.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] Comment 4: draft-ietf-avtcore-idms-02
Thread-Index: AQHMu1eQ5ae6NBdpZ0WkJ85kg51qVZXds7UYgAUzfyA=
Date: Mon, 19 Dec 2011 09:18:23 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA158155F522A@EXC-MBX03.tsn.tno.nl>
References: <CALw1_Q3bvuKxGtn+ZbWX11fTxNABmo-kk79bPqUEE+sbYZ9LUQ@mail.gmail.com> <65A4736CE8B345C5A49604E36F37C112@china.huawei.com>
In-Reply-To: <65A4736CE8B345C5A49604E36F37C112@china.huawei.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.153]
Content-Type: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA158155F522AEXCMBX03tsntnon_"
MIME-Version: 1.0
Subject: Re: [AVTCORE] Comment 4: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 09:18:26 -0000

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

Hi Qin,

> As for [syn-grp], I am interested to know who generate SyncGroupId? How i=
t is generated? Is it same as Media Stream Correlation Identifier carried i=
n the XR or RTCP IDMS packet?
or if not, how they are mapped?

Yes, the SyncGroupID is the same as the Media Stream Correlation Identifier=
. During session setup it is generated as a random number, using the same p=
rinciples as are used for the generation of an SSRC.

Ray



From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Qin Wu
Sent: vrijdag 16 december 2011 2:50
To: Kevin Gross; avt@ietf.org
Subject: Re: [AVTCORE] Comment 4: draft-ietf-avtcore-idms-02

Hi,
----- Original Message -----
>From: Kevin Gross
>To: avt@ietf.org<mailto:avt@ietf.org>
>Sent: Friday, December 16, 2011 2:29 AM
>Subject: Re: [AVTCORE] Comment 4: draft-ietf-avtcore-idms-02


>My comment was trying to convey that I did not consider there to be a clos=
e association between the SDP attributes and the XR and RTCP packets. I've =
reread and now appreciate >that there is for rtcp->xr:grp-sync and tcp-idms.

[Qin]: I assume you suggest to define xr-format as follows:

                    xr-format =3D/ rtcp-idms
                    rtcp-idms =3D "rtcp-idms" ":" [sync-grp] CRLF
I think that's a issue needing to be fixed. Also XR and new packets share t=
he same SDP attribute parameter "rtcp-idms".
Maybe it will be reasonable to define xr-format as follows:

            xr-format =3D/ rtcp-xr-idms
            rtcp-xr-idms =3D "rtcp-xr-idms" ":" [sync-grp] CRLF
to distinguish from SDP Parameter for RTCP IDMS Packet Type.

As for [syn-grp], I am interested to know who generate SyncGroupId? How it =
is generated? Is it same as Media Stream Correlation Identifier carried in =
the XR or RTCP IDMS packet?
or if not, how they are mapped?

>It is the clocksource attribute that does not have such an association. I =
understand the plan is to move this into a draft Aidan is working on.
[Qin]: In my view, since SDP attribute for both XR and RTCP IDMS packet sha=
re the same SyncGroupId?
I think it is possible and more general to associate [syn-grp] with clockso=
urce attribute.
This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"NL" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Qin,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&gt; As for [syn-grp], I am int=
erested to know&nbsp;who generate&nbsp;SyncGroupId? How it is generated?&nb=
sp;Is it same as Media Stream Correlation Identifier&nbsp;carried in the XR=
 or RTCP IDMS packet?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">or if not, how they are mapped?=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yes, the S=
yncGroupID is the same as the Media Stream Correlation Identifier. During s=
ession setup it is generated as a random number, using the
 same principles as are used for the generation of an SSRC.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ray<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]
<b>On Behalf Of </b>Qin Wu<br>
<b>Sent:</b> vrijdag 16 december 2011 2:50<br>
<b>To:</b> Kevin Gross; avt@ietf.org<br>
<b>Subject:</b> Re: [AVTCORE] Comment 4: draft-ietf-avtcore-idms-02<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span">Hi,</span><o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span">----- Original Mess=
age ----- <o:p>
</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span">&gt;From: Kevin Gro=
ss </span><br>
<span class=3D"apple-style-span">&gt;To: <a href=3D"mailto:avt@ietf.org">av=
t@ietf.org</a>
</span><br>
<span class=3D"apple-style-span">&gt;Sent: Friday, December 16, 2011 2:29 A=
M</span><br>
<span class=3D"apple-style-span">&gt;Subject: Re: [AVTCORE] Comment 4: draf=
t-ietf-avtcore-idms-02</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
&gt;My comment was trying to convey that I did not consider there to be a c=
lose association between the SDP attributes and the XR and RTCP packets. I'=
ve reread and now appreciate &gt;that there is for rtcp-&gt;xr:grp-sync and=
 tcp-idms.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[Qin]: I assume you suggest to define xr-format as f=
ollows:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xr-format =
=3D/&nbsp;rtcp-idms&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rtcp-id=
ms =3D &quot;rtcp-idms&quot; &quot;:&quot; [sync-grp] CRLF<br>
I think that's&nbsp;a issue&nbsp;needing to&nbsp;be fixed. Also XR and new =
packets share the same SDP attribute parameter &quot;rtcp-idms&quot;.<o:p><=
/o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Maybe it will be reasonable to define xr-format as f=
ollows:<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; xr-format =3D/&nbsp;rtcp-xr-idms&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; <o:p>
</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; rtcp-xr-idms =3D &quot;rtcp-xr-idms&quot; &quot;:&quot; [syn=
c-grp] CRLF<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">to distinguish from SDP Parameter for RTCP IDMS Pack=
et Type.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">As for [syn-grp], I am interested to know&nbsp;who g=
enerate&nbsp;SyncGroupId? How it is generated?&nbsp;Is it same as Media Str=
eam Correlation Identifier&nbsp;carried in the XR or RTCP IDMS packet?<o:p>=
</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">or if not, how they are mapped?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
&gt;It is the clocksource attribute that does not have such an association.=
 I understand the plan is to move this into a draft Aidan is working on.<o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[Qin]: In my view, since SDP attribute for both XR a=
nd RTCP IDMS packet share the same SyncGroupId?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I think it&nbsp;is possible&nbsp;and&nbsp;more gener=
al to associate [syn-grp] with clocksource attribute.<o:p></o:p></p>
</div>
</div>
<font face=3D"monospace">This e-mail and its contents are subject to the DI=
SCLAIMER at http://www.tno.nl/emaildisclaimer</font></body>
</html>

--_000_FCC100FC8D6B034CB88CD8173B2DA158155F522AEXCMBX03tsntnon_--


From kevin.gross@avanw.com  Mon Dec 19 20:55:54 2011
Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D0F11E80C5 for <avt@ietfa.amsl.com>; Mon, 19 Dec 2011 20:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.342
X-Spam-Level: 
X-Spam-Status: No, score=-0.342 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A7nCpGbDrnUc for <avt@ietfa.amsl.com>; Mon, 19 Dec 2011 20:55:53 -0800 (PST)
Received: from oproxy4-pub.bluehost.com (oproxy4-pub.bluehost.com [69.89.21.11]) by ietfa.amsl.com (Postfix) with SMTP id E426D11E80C4 for <avt@ietf.org>; Mon, 19 Dec 2011 20:55:52 -0800 (PST)
Received: (qmail 23021 invoked by uid 0); 20 Dec 2011 04:55:28 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by cpoproxy1.bluehost.com with SMTP; 20 Dec 2011 04:55:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=fsyZT9aOcLb9CLexRIDhwT/77QXumlzl9A3JVC4wfsg=;  b=BvPaB7ayFQ3WNxuCQb+yEX5EwairOlS7lYpJX6fYA1vo045d3mHS6xwoIDCe0qZo9ip/94TZR6vetaKpRjPi4ZSwc4T1F22SpOC5/BXT4HmzU4vvTr8230S5jW8r/Nb0;
Received: from mail-ww0-f44.google.com ([74.125.82.44]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1Rcrjc-0000KD-HW for avt@ietf.org; Mon, 19 Dec 2011 21:55:28 -0700
Received: by wgbdr13 with SMTP id dr13so9034719wgb.13 for <avt@ietf.org>; Mon, 19 Dec 2011 20:55:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.209.146 with SMTP id gg18mr549733wbb.6.1324356927126; Mon, 19 Dec 2011 20:55:27 -0800 (PST)
Received: by 10.223.102.129 with HTTP; Mon, 19 Dec 2011 20:55:27 -0800 (PST)
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA158155F5214@EXC-MBX03.tsn.tno.nl>
References: <CALw1_Q3XG3jcWFk5F_7fvARX1HLzfvNT=O64kReB-cH2Xqqr_Q@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F093E@EXC-MBX03.tsn.tno.nl> <CALw1_Q2bSn6x_dHpO2KOSWkkC5ryjx8vVr2F+qywE76sz-uT9A@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F5214@EXC-MBX03.tsn.tno.nl>
Date: Mon, 19 Dec 2011 21:55:27 -0700
Message-ID: <CALw1_Q1swNG8XYBVy=zazAbeDM_aKdHYichB2Letjm7fgN77bA@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Content-Type: multipart/alternative; boundary=00151758a57c327b3d04b47ee0b5
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 74.125.82.44 authed with kevin.gross@avanw.com}
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 04:55:54 -0000

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

Scenario: Two devices playing video. Both on the same subnet. One connected
via gigabit Ethernet, the other via 802.11b. If we timestamp to the
beginning of the first packet, they both report the same delivery time.
IDMS will see no need to introduce any compensating delay. But, due to
the slower link, the 802.11b device does not receive all data for the frame
until potentially almost a frame later. I would expect presentation to be a
frame delayed with respect to the gigabit device which receives all data
for the frame within a few microseconds.

I don't know if that's a serious enough discrepancy to fret over - if you
care about one frame, you probably want to be syncing to presentation time
not receipt time. But, the other snag with referencing to first byte is
that network interface hardware naturally alerts the network stack to
receipt at last byte. That's the natural place to do a software timestamp.
Of course, it is possible to compute first byte timestamp knowing
interface speed and packet size. But why impose this burden if last byte is
what we want to be timestamping?

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Mon, Dec 19, 2011 at 2:16 AM, Brandenburg, R. (Ray) van <
ray.vanbrandenburg@tno.nl> wrote:

>  Hi Kevin,****
>
> ** **
>
> I think the question here is whether there is reason for there to be a
> systematic difference in transport delay between the first octet and the
> last octet (i.e. is there a reason for the last octet of an RTP packet to
> always take longer than the first octet?).****
>
> ** **
>
> Of course jitter might cause some octets to experience a slightly longer
> or shorter delay than others, but I don=92t believe there is a reason to
> assume this is systematic. If this is the case, then I don=92t see a reas=
on
> to further complicate things by measuring the packet arrival of the last
> octet instead of the first.****
>
> ** **
>
> It is important to note that IDMS will always be, by its very nature,
> slightly behind the facts. Apart from the fact that it would not be very
> useful/scalable, RTCP rules out reporting on every single RTP packet. Thi=
s
> means that IDMS will only use measure the delay of some subset of all RTP
> packets. It therefore don=92t think it matters whether this measurement
> happens on the first or the last octet, as long as every receiver does it
> in the same way. ****
>
> ** **
>
> Ray****
>
> ** **
>
> ** **
>
> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On Behalf Of =
*Kevin
> Gross
> *Sent:* donderdag 15 december 2011 20:08
> *To:* avt@ietf.org
> *Subject:* Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02*=
*
> **
>
> ** **
>
> I believe what we want to measure is the interval between
> the origination time for the first octet of packets at the sender and the
> time the receiver has usable data. I believe the safe assumption is that
> the receiver does not have usable data for a particular RTP timestamp unt=
il
> he is sure he has received the last octet of the last packet associated
> with that timestamp.****
>
> ** **
>
> We can leave things as currently proposed, timestamp the first octet of
> the first packet and assume that with all other receivers timestamping in
> the same manner, synchronization based on packet receipt timestamps will
> work out.****
>
> ** **
>
> Or we can suggest a way to timestamp the last octet of the last packet.
> Timestamping the last octet as oppose to the first is actually easier
> because that's where the network interface will typically generate an
> interrupt. Identifying the last packet in the presence of reordering and
> packet loss is a bit tricky. I can make a more fully-formed proposal, but
> before going to the trouble I'd like to get agreement on what we want to =
be
> measuring here.****
>
>
> Kevin Gross****
>
> ** **
>
> On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ray) van <
> ray.vanbrandenburg@tno.nl> wrote:****
>
>  ****
>
> 6/ Packet Received NTP timestamp and Packet Received RTP timestamp
> definitions in section 6 and Packet Received NTP timestamp definition in
> section 7. What IDMS really wants to measure is when all data for the
> indicated RTP timestamp is available to the rendering application. We'd
> therefore like to know the arrival time of the last octet of the last
> packet associated with this RTP timestamp. There is difficulty reliably
> identifying the last packet. We could defining this as the last packet
> before media clock advances but this does not appreciate out-of-order
> generation and reordering by the network.****
>
>  ****
>
> I=92m not sure whether there is a functional difference between indicatin=
g
> the arrival of the first packet or the last packet. Either way, what is
> calculated is delay. Of course jitter could result in the delay for the
> first packet and for the last packet to not be the same. However, this is
> not a systematic problem. ****
>
> ** **
>
> [F&M] You are right.****
>
>
> [F&M] We are not sure what you mean here. We should discuss this issue bu=
t
> we think we should define it as the last received RTP packet among all th=
e
> sent RTP packets with the same RTP timestamp (regardless of its sequence
> number). ****
>    This e-mail and its contents are subject to the DISCLAIMER at
> http://www.tno.nl/emaildisclaimer
>

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

<div>Scenario: Two devices playing video. Both on the same subnet. One conn=
ected via gigabit Ethernet, the other via 802.11b.=A0If we timestamp to the=
 beginning of the first packet, they both report the same delivery time. ID=
MS will see no need to introduce any compensating delay. But, due to the=A0=
slower=A0link, the 802.11b device does not receive all data for the frame u=
ntil potentially almost a frame later. I would expect presentation to be a =
frame delayed with respect to the gigabit device which receives all data fo=
r the frame within a few microseconds.</div>
<div><br></div><div>I don&#39;t know if that&#39;s a serious enough=A0discr=
epancy=A0to fret over - if you care about one frame, you probably want to b=
e syncing to presentation time not receipt time. But, the other snag with r=
eferencing=A0to first byte is that network interface hardware naturally ale=
rts the network stack to receipt at last byte. That&#39;s the natural place=
 to do a software timestamp. Of course, it is possible to compute first byt=
e timestamp knowing interface=A0speed=A0and packet size. But why impose thi=
s burden if last byte is what we want to be=A0timestamping?</div>
<div><div><br clear=3D"all">Kevin Gross<br><div>+1-303-447-0517</div><div>M=
edia Network Consultant<br><div>AVA Networks -=A0<a href=3D"http://www.avan=
w.com/" target=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http://www.X192.o=
rg" target=3D"_blank">www.X192.org</a></div>
</div>
<br><br><div class=3D"gmail_quote">On Mon, Dec 19, 2011 at 2:16 AM, Branden=
burg, R. (Ray) van <span dir=3D"ltr">&lt;<a href=3D"mailto:ray.vanbrandenbu=
rg@tno.nl">ray.vanbrandenburg@tno.nl</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">






<div lang=3D"NL" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Kevin,<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think th=
e question here is whether there is reason for there to be a systematic dif=
ference in transport delay between the first octet and the
 last octet (i.e. is there a reason for the last octet of an RTP packet to =
always take longer than the first octet?).<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Of course =
jitter might cause some octets to experience a slightly longer or shorter d=
elay than others, but I don=92t believe there is a reason to
 assume this is systematic. If this is the case, then I don=92t see a reaso=
n to further complicate things by measuring the packet arrival of the last =
octet instead of the first.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">It is impo=
rtant to note that IDMS will always be, by its very nature, slightly behind=
 the facts. Apart from the fact that it would not be very
 useful/scalable, RTCP rules out reporting on every single RTP packet. This=
 means that IDMS will only use measure the delay of some subset of all RTP =
packets. It therefore don=92t think it matters whether this measurement hap=
pens on the first or the last octet,
 as long as every receiver does it in the same way. <u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Ray<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> <a href=3D"mailto:avt-bounces@ietf.org" target=3D"_bl=
ank">avt-bounces@ietf.org</a> [mailto:<a href=3D"mailto:avt-bounces@ietf.or=
g" target=3D"_blank">avt-bounces@ietf.org</a>]
<b>On Behalf Of </b>Kevin Gross<br>
<b>Sent:</b> donderdag 15 december 2011 20:08<br>
<b>To:</b> <a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</=
a><br>
<b>Subject:</b> Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-=
02<u></u><u></u></span></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal">I=A0believe=A0what we want to measure is the interva=
l between the=A0origination=A0time for the first octet of packets at the se=
nder and the time the receiver has usable data. I=A0believe=A0the safe assu=
mption is that the receiver does not have usable
 data for a particular RTP timestamp until he is sure he has received the l=
ast octet of the last packet associated with that timestamp.<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">We can leave things as currently proposed, timestamp=
 the first octet of the first packet and assume that with all other receive=
rs timestamping in the same manner, synchronization based on packet receipt=
 timestamps will work out.<u></u><u></u></p>

<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Or we can suggest a way to timestamp the last octet =
of the last packet. Timestamping the last octet as oppose to the first is a=
ctually easier because that&#39;s where the network interface will typicall=
y generate an interrupt. Identifying the
 last packet in the=A0presence=A0of=A0reordering=A0and packet loss is a bit=
 tricky. I can make a more fully-formed proposal, but before going to the t=
rouble I&#39;d like to get agreement on what we want to be measuring here.<=
u></u><u></u></p>

<div>
<p class=3D"MsoNormal"><br clear=3D"all">
Kevin Gross<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ra=
y) van &lt;<a href=3D"mailto:ray.vanbrandenburg@tno.nl" target=3D"_blank">r=
ay.vanbrandenburg@tno.nl</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span><span style=3D"color:#1f497d">=A0</span></span=
><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;"><u></u><u></u></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">6/=A0Packet Received NTP timestamp and=A0Packet Rece=
ived RTP timestamp definitions in section 6 and Packet Received NTP timesta=
mp definition in section 7. What IDMS really wants to measure is when all d=
ata for the indicated RTP timestamp is
 available to the rendering application. We&#39;d therefore like to know th=
e arrival time of the last octet of the last packet=A0associated=A0with thi=
s RTP timestamp. There is difficulty reliably identifying the last packet. =
We could defining this as the last packet
 before media clock advances but this does not=A0appreciate=A0out-of-order =
generation and reordering by the network.<span style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><u></u><u></u></span>=
</p>

</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">=A0</span><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
"><u></u><u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I=92m not sure whether th=
ere is a functional difference between indicating the arrival of the first =
packet or the last packet. Either way, what is calculated
 is delay. Of course jitter could result in the delay for the first packet =
and for the last packet to not be the same. However, this is not a systemat=
ic problem.
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;"><u></u><u></u></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span>[F&amp;M] You are right.</span><u></u><u></u><=
/p>
<div>
<p class=3D"MsoNormal"><br>
<span><span style=3D"color:#222222">[F&amp;M] We are not sure what you mean=
 here. We should discuss this issue but we think we should define it as the=
 last received RTP packet among all the sent RTP packets with the same RTP =
timestamp (regardless
 of its sequence number).</span></span><span><span style=3D"font-family:&qu=
ot;Arial&quot;,&quot;sans-serif&quot;;color:black">=A0</span></span><u></u>=
<u></u></p>
</div>
</div>
</div>
</div>
</div>
</div></div></div>
<font face=3D"monospace">This e-mail and its contents are subject to the DI=
SCLAIMER at <a href=3D"http://www.tno.nl/emaildisclaimer" target=3D"_blank"=
>http://www.tno.nl/emaildisclaimer</a></font></div>

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

--00151758a57c327b3d04b47ee0b5--

From ray.vanbrandenburg@tno.nl  Wed Dec 21 02:10:32 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE4721F8548 for <avt@ietfa.amsl.com>; Wed, 21 Dec 2011 02:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id orISw7ST4b-A for <avt@ietfa.amsl.com>; Wed, 21 Dec 2011 02:09:57 -0800 (PST)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 00F7E21F853B for <avt@ietf.org>; Wed, 21 Dec 2011 02:09:46 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.71,387,1320620400"; d="scan'208,217";a="62124840"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.222]) by mailhost1a.tno.nl with ESMTP; 21 Dec 2011 11:09:29 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.242]) by EXC-CASHUB03.tsn.tno.nl ([134.221.225.222]) with mapi id 14.01.0323.003; Wed, 21 Dec 2011 11:09:29 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: Kevin Gross <kevin.gross@avanw.com>
Thread-Topic: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
Thread-Index: AQHMuQvz+3wC97PPk0GZDWSIW5lKWpXcmkOAgACco4CABbFHUIABPCWAgAH4nlA=
Date: Wed, 21 Dec 2011 10:09:27 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA158155F5E57@EXC-MBX03.tsn.tno.nl>
References: <CALw1_Q3XG3jcWFk5F_7fvARX1HLzfvNT=O64kReB-cH2Xqqr_Q@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F093E@EXC-MBX03.tsn.tno.nl> <CALw1_Q2bSn6x_dHpO2KOSWkkC5ryjx8vVr2F+qywE76sz-uT9A@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F5214@EXC-MBX03.tsn.tno.nl> <CALw1_Q1swNG8XYBVy=zazAbeDM_aKdHYichB2Letjm7fgN77bA@mail.gmail.com>
In-Reply-To: <CALw1_Q1swNG8XYBVy=zazAbeDM_aKdHYichB2Letjm7fgN77bA@mail.gmail.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.153]
Content-Type: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA158155F5E57EXCMBX03tsntnon_"
MIME-Version: 1.0
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 10:10:32 -0000

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

Hi Kevin,

> Scenario: Two devices playing video. Both on the same subnet. One connect=
ed via gigabit Ethernet, the other via 802.11b. If we timestamp to the begi=
nning of the first packet, they both report the same delivery time. IDMS wi=
ll see no need to introduce any compensating delay. But, due to the slower =
link, the 802.11b device does not receive all data for the frame until pote=
ntially almost a frame later. I would expect presentation to be a frame del=
ayed with respect to the gigabit device which receives all data for the fra=
me within a few microseconds.

I don't see why both devices would report the same delivery time? If the 80=
2.11b link is slower, than it would receive the packet at a later instant a=
nd would report a later timestamp right? Or am I missing something here?

> But, the other snag with referencing to first byte is that network interf=
ace hardware naturally alerts the network stack to receipt at last byte. Th=
at's the natural place to do a software timestamp. Of course, it is possibl=
e to compute first byte timestamp knowing interface speed and packet size. =
But why impose this burden if last byte is what we want to be timestamping?

I think we might be talking about two different things here. The term 'firs=
t octet' refers to the RTP layer and not the network/transport (IP/UDP/TCP)=
 layer. It is only meaningful in situations where the size of for example a=
 video frame (e.g. an I-frame) is so big that it is fragmented over differe=
nt RTP packets having the same RTP timestamp but different RTP sequence num=
bers. The network interface will only pass the packet to the RTP layer once=
 the entire UDP/TCP packet (including the last byte) has been received. How=
ever, from an RTP point of view, this might not mean that the entire RTP pa=
cket has been received - that is, more RTP packets with the same RTP timest=
amp but with a different sequence number, might still need to arrive.

Ray

From: Kevin Gross [mailto:kevin.gross@avanw.com]
Sent: dinsdag 20 december 2011 5:55
To: Brandenburg, R. (Ray) van
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02

Scenario: Two devices playing video. Both on the same subnet. One connected=
 via gigabit Ethernet, the other via 802.11b. If we timestamp to the beginn=
ing of the first packet, they both report the same delivery time. IDMS will=
 see no need to introduce any compensating delay. But, due to the slower li=
nk, the 802.11b device does not receive all data for the frame until potent=
ially almost a frame later. I would expect presentation to be a frame delay=
ed with respect to the gigabit device which receives all data for the frame=
 within a few microseconds.

I don't know if that's a serious enough discrepancy to fret over - if you c=
are about one frame, you probably want to be syncing to presentation time n=
ot receipt time. But, the other snag with referencing to first byte is that=
 network interface hardware naturally alerts the network stack to receipt a=
t last byte. That's the natural place to do a software timestamp. Of course=
, it is possible to compute first byte timestamp knowing interface speed an=
d packet size. But why impose this burden if last byte is what we want to b=
e timestamping?

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com<http://www.avanw.com/>, www.X192.org<http://ww=
w.X192.org>

On Mon, Dec 19, 2011 at 2:16 AM, Brandenburg, R. (Ray) van <ray.vanbrandenb=
urg@tno.nl<mailto:ray.vanbrandenburg@tno.nl>> wrote:
Hi Kevin,

I think the question here is whether there is reason for there to be a syst=
ematic difference in transport delay between the first octet and the last o=
ctet (i.e. is there a reason for the last octet of an RTP packet to always =
take longer than the first octet?).

Of course jitter might cause some octets to experience a slightly longer or=
 shorter delay than others, but I don't believe there is a reason to assume=
 this is systematic. If this is the case, then I don't see a reason to furt=
her complicate things by measuring the packet arrival of the last octet ins=
tead of the first.

It is important to note that IDMS will always be, by its very nature, sligh=
tly behind the facts. Apart from the fact that it would not be very useful/=
scalable, RTCP rules out reporting on every single RTP packet. This means t=
hat IDMS will only use measure the delay of some subset of all RTP packets.=
 It therefore don't think it matters whether this measurement happens on th=
e first or the last octet, as long as every receiver does it in the same wa=
y.

Ray


From: avt-bounces@ietf.org<mailto:avt-bounces@ietf.org> [mailto:avt-bounces=
@ietf.org<mailto:avt-bounces@ietf.org>] On Behalf Of Kevin Gross
Sent: donderdag 15 december 2011 20:08
To: avt@ietf.org<mailto:avt@ietf.org>
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02

I believe what we want to measure is the interval between the origination t=
ime for the first octet of packets at the sender and the time the receiver =
has usable data. I believe the safe assumption is that the receiver does no=
t have usable data for a particular RTP timestamp until he is sure he has r=
eceived the last octet of the last packet associated with that timestamp.

We can leave things as currently proposed, timestamp the first octet of the=
 first packet and assume that with all other receivers timestamping in the =
same manner, synchronization based on packet receipt timestamps will work o=
ut.

Or we can suggest a way to timestamp the last octet of the last packet. Tim=
estamping the last octet as oppose to the first is actually easier because =
that's where the network interface will typically generate an interrupt. Id=
entifying the last packet in the presence of reordering and packet loss is =
a bit tricky. I can make a more fully-formed proposal, but before going to =
the trouble I'd like to get agreement on what we want to be measuring here.

Kevin Gross

On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ray) van <ray.vanbrandenb=
urg@tno.nl<mailto:ray.vanbrandenburg@tno.nl>> wrote:

6/ Packet Received NTP timestamp and Packet Received RTP timestamp definiti=
ons in section 6 and Packet Received NTP timestamp definition in section 7.=
 What IDMS really wants to measure is when all data for the indicated RTP t=
imestamp is available to the rendering application. We'd therefore like to =
know the arrival time of the last octet of the last packet associated with =
this RTP timestamp. There is difficulty reliably identifying the last packe=
t. We could defining this as the last packet before media clock advances bu=
t this does not appreciate out-of-order generation and reordering by the ne=
twork.

I'm not sure whether there is a functional difference between indicating th=
e arrival of the first packet or the last packet. Either way, what is calcu=
lated is delay. Of course jitter could result in the delay for the first pa=
cket and for the last packet to not be the same. However, this is not a sys=
tematic problem.

[F&M] You are right.

[F&M] We are not sure what you mean here. We should discuss this issue but =
we think we should define it as the last received RTP packet among all the =
sent RTP packets with the same RTP timestamp (regardless of its sequence nu=
mber).
This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:NL;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"NL" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Kevin,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;
</span><span lang=3D"EN-US">Scenario: Two devices playing video. Both on th=
e same subnet. One connected via gigabit Ethernet, the other via 802.11b.&n=
bsp;If we timestamp to the beginning of the first packet, they both report =
the same delivery time. IDMS will see no
 need to introduce any compensating delay. But, due to the&nbsp;slower&nbsp=
;link, the 802.11b device does not receive all data for the frame until pot=
entially almost a frame later. I would expect presentation to be a frame de=
layed with respect to the gigabit device which
 receives all data for the frame within a few microseconds.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I don&#821=
7;t see why both devices would report the same delivery time? If the 802.11=
b link is slower, than it would receive the packet at a later instant
 and would report a later timestamp right? Or am I missing something here?<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;
</span><span lang=3D"EN-US">But, the other snag with referencing&nbsp;to fi=
rst byte is that network interface hardware naturally alerts the network st=
ack to receipt at last byte. That's the natural place to do a software time=
stamp. Of course, it is possible to compute
 first byte timestamp knowing interface&nbsp;speed&nbsp;and packet size. Bu=
t why impose this burden if last byte is what we want to be&nbsp;timestampi=
ng?</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I think we=
 might be talking about two different things here. The term &#8216;first oc=
tet&#8217; refers to the RTP layer and not the network/transport (IP/UDP/TC=
P)
 layer. It is only meaningful in situations where the size of for example a=
 video frame (e.g. an I-frame) is so big that it is fragmented over differe=
nt RTP packets having the same RTP timestamp but different RTP sequence num=
bers. The network interface will
 only pass the packet to the RTP layer once the entire UDP/TCP packet (incl=
uding the last byte) has been received. However, from an RTP point of view,=
 this might not mean that the entire RTP packet has been received &#8211; t=
hat is, more RTP packets with the same
 RTP timestamp but with a different sequence number, might still need to ar=
rive. <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ray<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Kevin Gross [mailto:kevin.gross@avanw.com]
<br>
<b>Sent:</b> dinsdag 20 december 2011 5:55<br>
<b>To:</b> Brandenburg, R. (Ray) van<br>
<b>Cc:</b> avt@ietf.org<br>
<b>Subject:</b> Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-=
02<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Scenario: Two devices playing video. Both on the sam=
e subnet. One connected via gigabit Ethernet, the other via 802.11b.&nbsp;I=
f we timestamp to the beginning of the first packet, they both report the s=
ame delivery time. IDMS will see no need
 to introduce any compensating delay. But, due to the&nbsp;slower&nbsp;link=
, the 802.11b device does not receive all data for the frame until potentia=
lly almost a frame later. I would expect presentation to be a frame delayed=
 with respect to the gigabit device which
 receives all data for the frame within a few microseconds.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I don't know if that's a serious enough&nbsp;discrep=
ancy&nbsp;to fret over - if you care about one frame, you probably want to =
be syncing to presentation time not receipt time. But, the other snag with =
referencing&nbsp;to first byte is that network interface
 hardware naturally alerts the network stack to receipt at last byte. That'=
s the natural place to do a software timestamp. Of course, it is possible t=
o compute first byte timestamp knowing interface&nbsp;speed&nbsp;and packet=
 size. But why impose this burden if last
 byte is what we want to be&nbsp;timestamping?<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
Kevin Gross<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&#43;1-303-447-0517<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Media Network Consultant<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">AVA Networks -&nbsp;<a href=3D"http://www.avanw.com/=
" target=3D"_blank">www.AVAnw.com</a>,&nbsp;<a href=3D"http://www.X192.org"=
 target=3D"_blank">www.X192.org</a><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Dec 19, 2011 at 2:16 AM, Brandenburg, R. (Ra=
y) van &lt;<a href=3D"mailto:ray.vanbrandenburg@tno.nl">ray.vanbrandenburg@=
tno.nl</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Kevin,</span><o:p></o=
:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I think the question her=
e is whether there is reason for there to be a systematic difference
 in transport delay between the first octet and the last octet (i.e. is the=
re a reason for the last octet of an RTP packet to always take longer than =
the first octet?).</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Of course jitter might c=
ause some octets to experience a slightly longer or shorter
 delay than others, but I don&#8217;t believe there is a reason to assume t=
his is systematic. If this is the case, then I don&#8217;t see a reason to =
further complicate things by measuring the packet arrival of the last octet=
 instead of the first.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">It is important to note =
that IDMS will always be, by its very nature, slightly behind
 the facts. Apart from the fact that it would not be very useful/scalable, =
RTCP rules out reporting on every single RTP packet. This means that IDMS w=
ill only use measure the delay of some subset of all RTP packets. It theref=
ore don&#8217;t think it matters whether
 this measurement happens on the first or the last octet, as long as every =
receiver does it in the same way.
</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ray</span><o:p></o:p></p=
>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN-US"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">
<a href=3D"mailto:avt-bounces@ietf.org" target=3D"_blank">avt-bounces@ietf.=
org</a> [mailto:<a href=3D"mailto:avt-bounces@ietf.org" target=3D"_blank">a=
vt-bounces@ietf.org</a>]
<b>On Behalf Of </b>Kevin Gross<br>
<b>Sent:</b> donderdag 15 december 2011 20:08<br>
<b>To:</b> <a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</=
a><br>
<b>Subject:</b> Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-=
02</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I&nbsp;believe&nbsp;what we want to measure is the interval betwee=
n the&nbsp;origination&nbsp;time for the first octet of packets at the send=
er and the time the receiver has usable data. I&nbsp;believe&nbsp;the
 safe assumption is that the receiver does not have usable data for a parti=
cular RTP timestamp until he is sure he has received the last octet of the =
last packet associated with that timestamp.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">We can leave things as currently proposed, timestamp the first oct=
et of the first packet and assume that with all other receivers timestampin=
g in the same manner, synchronization
 based on packet receipt timestamps will work out.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Or we can suggest a way to timestamp the last octet of the last pa=
cket. Timestamping the last octet as oppose to the first is actually easier=
 because that's where the network interface
 will typically generate an interrupt. Identifying the last packet in the&n=
bsp;presence&nbsp;of&nbsp;reordering&nbsp;and packet loss is a bit tricky. =
I can make a more fully-formed proposal, but before going to the trouble I'=
d like to get agreement on what we want to be measuring
 here.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br clear=3D"all">
Kevin Gross<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Thu, Dec 15, 2011 at 1:56 AM, Brandenburg, R. (Ray) van &lt;<a =
href=3D"mailto:ray.vanbrandenburg@tno.nl" target=3D"_blank">ray.vanbrandenb=
urg@tno.nl</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">6/&nbsp;Packet Received NTP timestamp and&nbsp;Packet Received RTP=
 timestamp definitions in section 6 and Packet Received NTP timestamp defin=
ition in section 7. What IDMS really wants to
 measure is when all data for the indicated RTP timestamp is available to t=
he rendering application. We'd therefore like to know the arrival time of t=
he last octet of the last packet&nbsp;associated&nbsp;with this RTP timesta=
mp. There is difficulty reliably identifying
 the last packet. We could defining this as the last packet before media cl=
ock advances but this does not&nbsp;appreciate&nbsp;out-of-order generation=
 and reordering by the network.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I&#8217;m not sure whether there is a f=
unctional difference between indicating the arrival of the first
 packet or the last packet. Either way, what is calculated is delay. Of cou=
rse jitter could result in the delay for the first packet and for the last =
packet to not be the same. However, this is not a systematic problem.
</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">[F&amp;M] You are right.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<span style=3D"color:#222222">[F&amp;M] We are not sure what you mean here.=
 We should discuss this issue but we think we should define it as the last =
received RTP packet among all the sent RTP packets with the same RTP timest=
amp (regardless of its sequence number).</span><span style=3D"font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o:p></o:=
p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;,&=
quot;serif&quot;">This e-mail and its contents are subject to the DISCLAIME=
R at
<a href=3D"http://www.tno.nl/emaildisclaimer" target=3D"_blank">http://www.=
tno.nl/emaildisclaimer</a></span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_FCC100FC8D6B034CB88CD8173B2DA158155F5E57EXCMBX03tsntnon_--

From kevin.gross@avanw.com  Wed Dec 21 08:33:02 2011
Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81EF021F8A4B for <avt@ietfa.amsl.com>; Wed, 21 Dec 2011 08:33:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.992
X-Spam-Level: 
X-Spam-Status: No, score=-0.992 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G2r4448AI5JN for <avt@ietfa.amsl.com>; Wed, 21 Dec 2011 08:33:01 -0800 (PST)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [69.89.24.6]) by ietfa.amsl.com (Postfix) with SMTP id 989E921F888A for <avt@ietf.org>; Wed, 21 Dec 2011 08:33:01 -0800 (PST)
Received: (qmail 12516 invoked by uid 0); 21 Dec 2011 16:32:39 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy9.bluehost.com with SMTP; 21 Dec 2011 16:32:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=Q2JY/RvSjJheVQpZxBJA+8IxGx4w7HkMWWDi/OlMtk4=;  b=mizhmJ+iwFlLWPXyQBE/ehVMIqmWoK+CzHh6vaCtrEjmXyY0ISkMfrc1qejtjfzkiRQHGkQm2J3UZWM1x9TllLgFOrUh7ynVnDUxAisZlkZZLF9yEChL2Tp3PBd4gsl4;
Received: from mail-we0-f172.google.com ([74.125.82.172]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1RdP5r-0006vu-Ic for avt@ietf.org; Wed, 21 Dec 2011 09:32:39 -0700
Received: by werb14 with SMTP id b14so3271419wer.31 for <avt@ietf.org>; Wed, 21 Dec 2011 08:32:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.136.231 with SMTP id w81mr4030730wei.3.1324485158131; Wed, 21 Dec 2011 08:32:38 -0800 (PST)
Received: by 10.223.102.129 with HTTP; Wed, 21 Dec 2011 08:32:38 -0800 (PST)
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA158155F5E57@EXC-MBX03.tsn.tno.nl>
References: <CALw1_Q3XG3jcWFk5F_7fvARX1HLzfvNT=O64kReB-cH2Xqqr_Q@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F093E@EXC-MBX03.tsn.tno.nl> <CALw1_Q2bSn6x_dHpO2KOSWkkC5ryjx8vVr2F+qywE76sz-uT9A@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F5214@EXC-MBX03.tsn.tno.nl> <CALw1_Q1swNG8XYBVy=zazAbeDM_aKdHYichB2Letjm7fgN77bA@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA158155F5E57@EXC-MBX03.tsn.tno.nl>
Date: Wed, 21 Dec 2011 09:32:38 -0700
Message-ID: <CALw1_Q0stsG-FpUskUr56gT55Mo6NXkV2mZhYLLfKfrF0UAXyQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Content-Type: multipart/alternative; boundary=0016e6d7ec675c5a0804b49cbbbc
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 74.125.82.172 authed with kevin.gross@avanw.com}
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Additional comments: draft-ietf-avtcore-idms-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 16:33:02 -0000

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

On Wed, Dec 21, 2011 at 3:09 AM, Brandenburg, R. (Ray) van <
ray.vanbrandenburg@tno.nl> wrote:

>  Hi Kevin,****
>
> ** **
>
> > Scenario: Two devices playing video. Both on the same subnet. One
> connected via gigabit Ethernet, the other via 802.11b. If we timestamp to
> the beginning of the first packet, they both report the same delivery tim=
e.
> IDMS will see no need to introduce any compensating delay. But, due to
> the slower link, the 802.11b device does not receive all data for the fra=
me
> until potentially almost a frame later. I would expect presentation to be=
 a
> frame delayed with respect to the gigabit device which receives all data
> for the frame within a few microseconds.****
>
> ** **
>
> I don=92t see why both devices would report the same delivery time? If th=
e
> 802.11b link is slower, than it would receive the packet at a later insta=
nt
> and would report a later timestamp right? Or am I missing something here?=
*
> ***
>
> **
>

[kg] The beginning of the first packet arrives at both at approximately the
same time. The slower link does not delay start of receipt. Because of the
lower bitrate, it takes longer for the rest of the packet and any
closely-spaced packets following to be received.

>  **
>
> > But, the other snag with referencing to first byte is that network
> interface hardware naturally alerts the network stack to receipt at last
> byte. That's the natural place to do a software timestamp. Of course, it =
is
> possible to compute first byte timestamp knowing interface speed and pack=
et
> size. But why impose this burden if last byte is what we want to
> be timestamping?****
>
> ** **
>
> I think we might be talking about two different things here. The term
> =91first octet=92 refers to the RTP layer and not the network/transport
> (IP/UDP/TCP) layer. It is only meaningful in situations where the size of
> for example a video frame (e.g. an I-frame) is so big that it is fragment=
ed
> over different RTP packets having the same RTP timestamp but different RT=
P
> sequence numbers. The network interface will only pass the packet to the
> RTP layer once the entire UDP/TCP packet (including the last byte) has be=
en
> received. However, from an RTP point of view, this might not mean that th=
e
> entire RTP packet has been received =96 that is, more RTP packets with th=
e
> same RTP timestamp but with a different sequence number, might still need
> to arrive. ** **
>
> **
>
[kg] Yes, I think we're misunderstanding each other. Let's sort out the
point above and come back to this.

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

<div class=3D"gmail_quote">On Wed, Dec 21, 2011 at 3:09 AM, Brandenburg, R.=
 (Ray) van <span dir=3D"ltr">&lt;<a href=3D"mailto:ray.vanbrandenburg@tno.n=
l">ray.vanbrandenburg@tno.nl</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">






<div lang=3D"NL" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Kevin,<=
u></u><u></u></span></p><div class=3D"im">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;
</span><span lang=3D"EN-US">Scenario: Two devices playing video. Both on th=
e same subnet. One connected via gigabit Ethernet, the other via 802.11b.=
=A0If we timestamp to the beginning of the first packet, they both report t=
he same delivery time. IDMS will see no
 need to introduce any compensating delay. But, due to the=A0slower=A0link,=
 the 802.11b device does not receive all data for the frame until potential=
ly almost a frame later. I would expect presentation to be a frame delayed =
with respect to the gigabit device which
 receives all data for the frame within a few microseconds.<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
</div><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I do=
n=92t see why both devices would report the same delivery time? If the 802.=
11b link is slower, than it would receive the packet at a later instant
 and would report a later timestamp right? Or am I missing something here?<=
u></u><u></u></span></p><div class=3D"im">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u></s=
pan></p></div></div></div></blockquote><div><br></div><div>[kg] The beginni=
ng of the first packet arrives at both at approximately the same time. The =
slower link does not delay start of receipt. Because of the lower bitrate, =
it takes longer for the rest of the packet and any closely-spaced packets f=
ollowing to be received.</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"NL" link=3D"blue" vlink=3D"purp=
le"><div><div class=3D"im"><p class=3D"MsoNormal"><span lang=3D"EN-US" styl=
e=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:#1f497d">=A0<u></u></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;
</span><span lang=3D"EN-US">But, the other snag with referencing=A0to first=
 byte is that network interface hardware naturally alerts the network stack=
 to receipt at last byte. That&#39;s the natural place to do a software tim=
estamp. Of course, it is possible to compute
 first byte timestamp knowing interface=A0speed=A0and packet size. But why =
impose this burden if last byte is what we want to be=A0timestamping?</span=
><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:#1f497d"><u></u><u></u></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
<u></u></span></p>
</div><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I th=
ink we might be talking about two different things here. The term =91first =
octet=92 refers to the RTP layer and not the network/transport (IP/UDP/TCP)
 layer. It is only meaningful in situations where the size of for example a=
 video frame (e.g. an I-frame) is so big that it is fragmented over differe=
nt RTP packets having the same RTP timestamp but different RTP sequence num=
bers. The network interface will
 only pass the packet to the RTP layer once the entire UDP/TCP packet (incl=
uding the last byte) has been received. However, from an RTP point of view,=
 this might not mean that the entire RTP packet has been received =96 that =
is, more RTP packets with the same
 RTP timestamp but with a different sequence number, might still need to ar=
rive. <u></u>
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0=
</span></p></div></div></blockquote><div>[kg] Yes, I think we&#39;re misund=
erstanding each other. Let&#39;s sort out the point above and come back to =
this.</div>
</div>

--0016e6d7ec675c5a0804b49cbbbc--

From internet-drafts@ietf.org  Fri Dec 30 15:09:24 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EAE521F8513; Fri, 30 Dec 2011 15:09:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCIJzYkxgYvF; Fri, 30 Dec 2011 15:09:24 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0BC21F84DA; Fri, 30 Dec 2011 15:09:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111230230924.32622.2169.idtracker@ietfa.amsl.com>
Date: Fri, 30 Dec 2011 15:09:24 -0800
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-vbr-audio-04.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Dec 2011 23:09:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Audio/Video Transport Core Maintenanc=
e Working Group of the IETF.

	Title           : Guidelines for the use of Variable Bit Rate Audio with S=
ecure RTP
	Author(s)       : Colin Perkins
                          Jean-Marc Valin
	Filename        : draft-ietf-avtcore-srtp-vbr-audio-04.txt
	Pages           : 7
	Date            : 2011-12-30

   This memo discusses potential security issues that arise when using
   variable bit rate audio with the secure RTP profile.  Guidelines to
   mitigate these issues are suggested.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avtcore-srtp-vbr-audio-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-srtp-vbr-audio-04.txt


From csp@csperkins.org  Fri Dec 30 15:16:40 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3124F21F8511 for <avt@ietfa.amsl.com>; Fri, 30 Dec 2011 15:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bnaFoCtb43UH for <avt@ietfa.amsl.com>; Fri, 30 Dec 2011 15:16:39 -0800 (PST)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by ietfa.amsl.com (Postfix) with ESMTP id 6136D21F84F8 for <avt@ietf.org>; Fri, 30 Dec 2011 15:16:39 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.30]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RglgH-0004dy-dH; Fri, 30 Dec 2011 23:16:38 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20111230230924.32622.2169.idtracker@ietfa.amsl.com>
Date: Fri, 30 Dec 2011 23:16:05 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A588527-C897-4491-8FB3-F3C6C122B40B@csperkins.org>
References: <20111230230924.32622.2169.idtracker@ietfa.amsl.com>
To: "avt@ietf.org WG" <avt@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-vbr-audio-04.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Dec 2011 23:16:40 -0000

On 30 Dec 2011, at 23:09, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories. This draft is a work item of the Audio/Video Transport Core =
Maintenance Working Group of the IETF.
>=20
> 	Title           : Guidelines for the use of Variable Bit Rate =
Audio with Secure RTP
> 	Author(s)       : Colin Perkins
>                          Jean-Marc Valin
> 	Filename        : draft-ietf-avtcore-srtp-vbr-audio-04.txt
> 	Pages           : 7
> 	Date            : 2011-12-30
>=20
>   This memo discusses potential security issues that arise when using
>   variable bit rate audio with the secure RTP profile.  Guidelines to
>   mitigate these issues are suggested.


This version strengthens the recommendations in the light of review by =
the security area, and discussion in SAAG at IETF 82. This was heavily =
influenced by http://www.cs.unc.edu/~fabian/papers/foniks-oak11.pdf

In the light of the changes, a new WG last call is likely required.

Colin


--=20
Colin Perkins
http://csperkins.org/



