
From Martin.Stiemerling@neclab.eu  Fri Apr  1 01:01:53 2011
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: alto@core3.amsl.com
Delivered-To: alto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8929D3A6C08 for <alto@core3.amsl.com>; Fri,  1 Apr 2011 01:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.376
X-Spam-Level: 
X-Spam-Status: No, score=-102.376 tagged_above=-999 required=5 tests=[AWL=0.223, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4XEPmf84fQ7j for <alto@core3.amsl.com>; Fri,  1 Apr 2011 01:01:52 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 3D4D33A6837 for <alto@ietf.org>; Fri,  1 Apr 2011 01:01:52 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 12DEF2C000200; Fri,  1 Apr 2011 10:06:20 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVgPTCzyQlCy; Fri,  1 Apr 2011 10:06:19 +0200 (CEST)
Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.neclab.eu (Postfix) with ESMTP id EC64F2C0001DE; Fri,  1 Apr 2011 10:06:09 +0200 (CEST)
Received: from Polydeuces.office.hd ([169.254.3.246]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0270.001; Fri, 1 Apr 2011 10:03:22 +0200
From: Martin Stiemerling <Martin.Stiemerling@neclab.eu>
To: Piotr Wydrych <piotr.wydrych@agh.edu.pl>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] Regarding discussion during the Server-to-server presentation
Thread-Index: AQHL78L7aVtU0HhhGUuIJRGMrv/nAJRIpuCg
Date: Fri, 1 Apr 2011 08:03:21 +0000
Message-ID: <E84E7B8FF3F2314DA16E48EC89AB49F005D32F02@Polydeuces.office.hd>
References: <4D94AF7B.5000503@agh.edu.pl>
In-Reply-To: <4D94AF7B.5000503@agh.edu.pl>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.7.0.207]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [alto] Regarding discussion during the Server-to-server presentation
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2011 08:01:53 -0000

Hi Piotr,

Thanks for the links to the paper. I still need to read through, once the I=
ETF meeting is over.

  Martin

martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014=20


> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
> Piotr Wydrych
> Sent: Thursday, March 31, 2011 6:45 PM
> To: alto@ietf.org
> Subject: [alto] Regarding discussion during the Server-to-server
> presentation
>=20
> Folks,
>=20
> Regarding Martin's question if the situation when the outgoing traffic
> passes a different path than the incoming traffic is real:
> Yup, it's real. Please see the Table 1 in the paper entitled ``Optimal
> Choice of Peers based on BGP Information'', which is cited in
> draft-dulinski-alto-inter-alto-protocol-00 and
> draft-dulinski-alto-inter-problem-statement-00, and is available from
> [1].
>=20
> Regarding Jan Seedorf's comment that they have made experiments and
> that
> they confirm that the inter-ALTO aka. server-to-server communication
> helps:
> We have also confirmed the need of the inter-ALTO communication. Please
> see again [1,2] (where the AS-path length is taken into account) and
> the
> paper entitled ``Cost-driven Peer Rating Algorithm'' [3] (where the
> traffic costs are taken into account).
>=20
> [1] Free source:
> http://www.kt.agh.edu.pl/~cholda/wp-
> content/uploads/2011/02/ICC2010_1.pdf
> [2] Surely permanent, but paid source:
> http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=3D5502269
> [3] Free source:
> http://www.kt.agh.edu.pl/~wydrych/wp-content/uploads/2011/01/Cost-
> driven-Peer-Rating-Algorithm.pdf
> (permanent link will be provided by IEEE after ICC11)
>=20
> Best Regards,
> Piotr 'GhosT' Wydrych
> --
> Piotr 'GhosT' Wydrych .. xmpp:wydrych//agh.edu.pl ..
> http://wydrych.net/
>=20
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto

From vkg@bell-labs.com  Mon Apr 11 08:58:22 2011
Return-Path: <vkg@bell-labs.com>
X-Original-To: alto@core3.amsl.com
Delivered-To: alto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A314928C135 for <alto@core3.amsl.com>; Mon, 11 Apr 2011 08:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.595
X-Spam-Level: 
X-Spam-Status: No, score=-106.595 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gj8LqzSYcNTr for <alto@core3.amsl.com>; Mon, 11 Apr 2011 08:58:21 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 564D728C134 for <alto@ietf.org>; Mon, 11 Apr 2011 08:58:21 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p3BFwLeP004864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Mon, 11 Apr 2011 10:58:21 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p3BFwLlv014753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Mon, 11 Apr 2011 10:58:21 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p3BFwKkM026063 for <alto@ietf.org>; Mon, 11 Apr 2011 10:58:20 -0500 (CDT)
Message-ID: <4DA32595.7090707@bell-labs.com>
Date: Mon, 11 Apr 2011 11:00:21 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: [alto] Draft minutes for alto@IETF-80
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2011 15:58:22 -0000

Folks: The draft minutes for alto@IETF-80 are available at
the URL below.  Please send any corrections and clarifications
to the mailing list before we formally submit these.

Please note that the draft minutes contain link to the
audio and slide files (as usual), but in addition, they also
contain a link to the Meetecho URL providing
audio/video/slides/jabber.  The Meetecho link uses HTML-5,
so your mileage may vary depending on whether or not
your browser is compliant.

The link to the draft minutes is:
http://www.ietf.org/proceedings/80/minutes/alto.html

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From ben@niven-jenkins.co.uk  Wed Apr 13 04:32:47 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 2DF82E0748 for <alto@ietfc.amsl.com>; Wed, 13 Apr 2011 04:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.981
X-Spam-Level: 
X-Spam-Status: No, score=-103.981 tagged_above=-999 required=5 tests=[AWL=-0.382, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oeRdbjY9HH-s for <alto@ietfc.amsl.com>; Wed, 13 Apr 2011 04:32:46 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfc.amsl.com (Postfix) with ESMTP id 3411EE0743 for <alto@ietf.org>; Wed, 13 Apr 2011 04:32:46 -0700 (PDT)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-108-devlan.cachelogic.com) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1Q9yJT-0000mQ-2P for alto@ietf.org; Wed, 13 Apr 2011 12:32:47 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 Apr 2011 12:32:36 +0100
Message-Id: <F57A3851-9239-4AEF-9420-6BE84A439B9C@niven-jenkins.co.uk>
To: alto@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2011 11:32:47 -0000

Authors, Colleagues,

The meeting minutes from IETF 80 record:

"Jan Medved presents Network-to-server API.

  Jan Seedorf: scope of this work is explicitly excluded in RFC 5693
  ALTO WG scope description. Enrico: this is new work, currently not
  in the charter. We should hear it. Jan S.: we need to discuss if we
  need to standardized it. Eric: it does, but maybe not now."

Regarding whether we need to standardise the Network-to-server "API" for =
ALTO, my opinion is that we do not.

Extracting network topology by passively listening to routing protocols =
for various purposes including aiding with operations, diagnostics, root =
cause analysis, management, capacity planning, traffic engineering, etc. =
is not a new idea. There are multiple products on the market to enable =
operators to do just that.

An ALTO server that follows a similar approach as a mechanism to import =
network topology into its network topology/map/cost database is a =
reasonable proposition but in my opinion the ALTO WG should not attempt =
to standardise how a ALTO server should perform such integration with an =
operator's routing control plane(s), for example  because:

* Extracting network topology is not an interoperability issue between =
ALTO servers. Each ALTO server can extract the network topology =
independently and if the topology needs to be distributed between ALTO =
servers then it is an ALTO Server-Server API that needs standardising =
*not* an ALTO Server-Network API. Interoperation between an ALTO Server =
and the underlying network(s) is a solved problem as is demonstrated by =
the numerous interoperable implementations of routing protocols.

* Attempting to standardise a single approach is likely to limit the =
applicability of ALTO (or the relevancy of the ALTO Server-Network "API =
standard") because it is unlikely we would be able to converge on a =
single routing protocol that would satisfy the preferences of all =
operators that are likely to deploy an ALTO server.=20

Ben



From ping@pingpan.org  Wed Apr 13 08:29:32 2011
Return-Path: <ping@pingpan.org>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1A822E073E for <alto@ietfc.amsl.com>; Wed, 13 Apr 2011 08:29:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.976
X-Spam-Level: 
X-Spam-Status: No, score=-5.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxU1VkoVwuEG for <alto@ietfc.amsl.com>; Wed, 13 Apr 2011 08:29:30 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfc.amsl.com (Postfix) with SMTP id 77041E06A4 for <alto@ietf.org>; Wed, 13 Apr 2011 08:29:30 -0700 (PDT)
Received: from mail-px0-f180.google.com ([209.85.212.180]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKTaXBWQBBvarVqCqWsyv38x7zSCTIeJET@postini.com; Wed, 13 Apr 2011 08:29:30 PDT
Received: by mail-px0-f180.google.com with SMTP id 25so675407pxj.25 for <alto@ietf.org>; Wed, 13 Apr 2011 08:29:29 -0700 (PDT)
Received: by 10.142.7.4 with SMTP id 4mr8114289wfg.386.1302708569721; Wed, 13 Apr 2011 08:29:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.50.164 with HTTP; Wed, 13 Apr 2011 08:22:45 -0700 (PDT)
In-Reply-To: <F57A3851-9239-4AEF-9420-6BE84A439B9C@niven-jenkins.co.uk>
References: <F57A3851-9239-4AEF-9420-6BE84A439B9C@niven-jenkins.co.uk>
From: Ping Pan <ping@pingpan.org>
Date: Wed, 13 Apr 2011 08:22:45 -0700
Message-ID: <BANLkTinmRHDmTUJc5kXwse+2-_HKEHEMPw@mail.gmail.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: multipart/alternative; boundary=00504502b08e8b4bdc04a0ce7989
Cc: alto@ietf.org
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2011 15:29:32 -0000

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

On Wed, Apr 13, 2011 at 4:32 AM, Ben Niven-Jenkins
<ben@niven-jenkins.co.uk>wrote:

> Authors, Colleagues,
>
> The meeting minutes from IETF 80 record:
>
> "Jan Medved presents Network-to-server API.
>
>  Jan Seedorf: scope of this work is explicitly excluded in RFC 5693
>  ALTO WG scope description. Enrico: this is new work, currently not
>  in the charter. We should hear it. Jan S.: we need to discuss if we
>  need to standardized it. Eric: it does, but maybe not now."
>
> Regarding whether we need to standardise the Network-to-server "API" for
> ALTO, my opinion is that we do not.
>
>
I concur for now.

It's not clear to me that we fully understand the network abstraction
information to be gathered in the first place. Draft-sun has recommended to
gather information at BAS granularity. Another draft was talking about
inter-ISP network abstraction for better asyn transmission etc.Comcast has
shown that coarse and fine network maps have the similar effect...

Further, I think that the current ALTO WG scope is to define the mechanism
to bind application and network, not the actual network abstraction. Correct
me if I am wrong.

Regards,

Ping


> Extracting network topology by passively listening to routing protocols for
> various purposes including aiding with operations, diagnostics, root cause
> analysis, management, capacity planning, traffic engineering, etc. is not a
> new idea. There are multiple products on the market to enable operators to
> do just that.
>
> An ALTO server that follows a similar approach as a mechanism to import
> network topology into its network topology/map/cost database is a reasonable
> proposition but in my opinion the ALTO WG should not attempt to standardise
> how a ALTO server should perform such integration with an operator's routing
> control plane(s), for example  because:
>
> * Extracting network topology is not an interoperability issue between ALTO
> servers. Each ALTO server can extract the network topology independently and
> if the topology needs to be distributed between ALTO servers then it is an
> ALTO Server-Server API that needs standardising *not* an ALTO Server-Network
> API. Interoperation between an ALTO Server and the underlying network(s) is
> a solved problem as is demonstrated by the numerous interoperable
> implementations of routing protocols.
>
> * Attempting to standardise a single approach is likely to limit the
> applicability of ALTO (or the relevancy of the ALTO Server-Network "API
> standard") because it is unlikely we would be able to converge on a single
> routing protocol that would satisfy the preferences of all operators that
> are likely to deploy an ALTO server.
>
> Ben
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

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

<br><div class=3D"gmail_quote">On Wed, Apr 13, 2011 at 4:32 AM, Ben Niven-J=
enkins <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@niven-jenkins.co.uk">ben=
@niven-jenkins.co.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
;">

Authors, Colleagues,<br>
<br>
The meeting minutes from IETF 80 record:<br>
<br>
&quot;Jan Medved presents Network-to-server API.<br>
<br>
 =A0Jan Seedorf: scope of this work is explicitly excluded in RFC 5693<br>
 =A0ALTO WG scope description. Enrico: this is new work, currently not<br>
 =A0in the charter. We should hear it. Jan S.: we need to discuss if we<br>
 =A0need to standardized it. Eric: it does, but maybe not now.&quot;<br>
<br>
Regarding whether we need to standardise the Network-to-server &quot;API&qu=
ot; for ALTO, my opinion is that we do not.<br>
<br></blockquote><div><br></div><div>I concur for now.</div><div><br></div>=
<div>It&#39;s not clear to me that we fully understand the network abstract=
ion information to be gathered in the first place. Draft-sun has recommende=
d to gather information at BAS granularity. Another draft was talking about=
 inter-ISP network abstraction for better asyn transmission etc.Comcast has=
 shown that=A0coarse=A0and fine network maps have the similar effect...=A0<=
/div>

<div><br></div><div>Further, I think that the current ALTO WG scope is to d=
efine the mechanism to bind application and network, not the actual network=
=A0abstraction. Correct me if I am wrong.</div><div><br></div><div>Regards,=
</div>

<div><br></div><div>Ping</div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"=
>
Extracting network topology by passively listening to routing protocols for=
 various purposes including aiding with operations, diagnostics, root cause=
 analysis, management, capacity planning, traffic engineering, etc. is not =
a new idea. There are multiple products on the market to enable operators t=
o do just that.<br>


<br>
An ALTO server that follows a similar approach as a mechanism to import net=
work topology into its network topology/map/cost database is a reasonable p=
roposition but in my opinion the ALTO WG should not attempt to standardise =
how a ALTO server should perform such integration with an operator&#39;s ro=
uting control plane(s), for example =A0because:<br>


<br>
* Extracting network topology is not an interoperability issue between ALTO=
 servers. Each ALTO server can extract the network topology independently a=
nd if the topology needs to be distributed between ALTO servers then it is =
an ALTO Server-Server API that needs standardising *not* an ALTO Server-Net=
work API. Interoperation between an ALTO Server and the underlying network(=
s) is a solved problem as is demonstrated by the numerous interoperable imp=
lementations of routing protocols.<br>


<br>
* Attempting to standardise a single approach is likely to limit the applic=
ability of ALTO (or the relevancy of the ALTO Server-Network &quot;API stan=
dard&quot;) because it is unlikely we would be able to converge on a single=
 routing protocol that would satisfy the preferences of all operators that =
are likely to deploy an ALTO server.<br>


<br>
Ben<br>
<br>
<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote></div><br>

--00504502b08e8b4bdc04a0ce7989--

From jmedved@juniper.net  Wed Apr 13 16:56:01 2011
Return-Path: <jmedved@juniper.net>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 6699BE0723 for <alto@ietfc.amsl.com>; Wed, 13 Apr 2011 16:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q01-TWtxSiFI for <alto@ietfc.amsl.com>; Wed, 13 Apr 2011 16:56:00 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfc.amsl.com (Postfix) with ESMTP id 06CEBE06FC for <alto@ietf.org>; Wed, 13 Apr 2011 16:55:59 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTaY4Dhoy9OQbHFbiMUPvXz1Uhxv6ugwe@postini.com; Wed, 13 Apr 2011 16:56:00 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Wed, 13 Apr 2011 16:52:46 -0700
From: Jan Medved <jmedved@juniper.net>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>, "alto@ietf.org" <alto@ietf.org>
Date: Wed, 13 Apr 2011 16:54:40 -0700
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: Acv6NeNDBbLTmDs/T2uE0dGCTS0zAg==
Message-ID: <C9CB0B72.22029%jmedved@juniper.net>
In-Reply-To: <F57A3851-9239-4AEF-9420-6BE84A439B9C@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2011 23:56:01 -0000

Ben,

Please see inline.


Thanks,
Jan


On 4/13/11 4:32 AM, "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk> wrote:

>Authors, Colleagues,
>
>The meeting minutes from IETF 80 record:
>
>"Jan Medved presents Network-to-server API.
>
>  Jan Seedorf: scope of this work is explicitly excluded in RFC 5693
>  ALTO WG scope description. Enrico: this is new work, currently not
>  in the charter. We should hear it. Jan S.: we need to discuss if we
>  need to standardized it. Eric: it does, but maybe not now."
>
>Regarding whether we need to standardise the Network-to-server "API" for
>ALTO, my opinion is that we do not.
>
>Extracting network topology by passively listening to routing protocols
>for various purposes including aiding with operations, diagnostics, root
>cause analysis, management, capacity planning, traffic engineering, etc.
>is not a new idea. There are multiple products on the market to enable
>operators to do just that.

Agreed that extracting network topology by passively listening to routing
protocols is not a new idea. What is a new idea, though, is that it can be
accomplished by listening to a single protocol (BGP with TE extensions),
rather than listening to both BGP and IGPs.

This significantly simplifies (even enables) the operation and deployment
of an ALTO Server that wishes to listen routing protocol updates.
Streamlining / simplifying the ALTO Server's operation is the primary
motivation for this draft.


>
>An ALTO server that follows a similar approach as a mechanism to import
>network topology into its network topology/map/cost database is a
>reasonable proposition but in my opinion the ALTO WG should not attempt
>to standardise how a ALTO server should perform such integration with an
>operator's routing control plane(s), for example  because:
>
>* Extracting network topology is not an interoperability issue between
>ALTO servers. Each ALTO server can extract the network topology
>independently and if the topology needs to be distributed between ALTO
>servers then it is an ALTO Server-Server API that needs standardising
>*not* an ALTO Server-Network API.

Actually, extracting network topology and generating the abstracted
network topology (maps) is an interoperability issue between ALTO Servers,
and it can not be completely separated from the exchange of topology
between ALTO servers. For ALTO Servers to be able to exchange (and
reconcile) their respective abstracted topologies (maps) with each other,
the topologies need to be equivalent. This then drives the need for a
common set of data from which the topology is created and a normalized way
to generate the topology from the data (which we mentioned in the draft,
but did not attempt to specify).


>Interoperation between an ALTO Server and the underlying network(s) is a
>solved problem as is demonstrated by the numerous interoperable
>implementations of routing protocols.

Not really. First, the interoperable implementations of routing protocols
are used to talk between routers themselves, not as a northbound API to
the network. Now, we need to differentiate between BGP and IGPs. BGP can
(and has been) used to get network topology to interested clients. IGPs
are not, and it is highly unlikely that operators will let an ALTO Server
to hook into their IGP (at least this has been my experience over the past
several years...). Even if they do, there are a lot of issues with it -
security, worries about network stability, multi-area deployment
complexity, etc. (more listed in the draft). We need both BGP and IGP data
to generate cost maps, and unfortunately today there is no practical way
to get it.=20

Today, the vast majority of clients that need network topology data simply
hook into BGP. ALTO is much easier to use to get network topology than
BGP. But for ALTO to be usable for this purpose, we need a deterministic
way to generate ALTO maps from a well defined set of network data, so that
clients know what they're getting. One part of this definition is the
Network-Server API which defines the data set and the way to get it,
another is a normalized way to generate the maps.

>
>* Attempting to standardise a single approach is likely to limit the
>applicability of ALTO (or the relevancy of the ALTO Server-Network "API
>standard") because it is unlikely we would be able to converge on a
>single routing protocol that would satisfy the preferences of all
>operators that are likely to deploy an ALTO server.

I am not sure what you mean - there is a single routing protocol that
operators have converged on - BGP. If you mean operators have not
converged on a single IGP, I agree. But that is precisely one of the
problems we are addressing with the draft. Operators can use a single
protocol - BGP - that (with appropriate extensions) can convey all the
information required to generate ALTO maps. Since BGP has the necessary
security and policy knobs, and it is already being used to exchange
information between different admin domains, it is definitely a good
candidate for a northbound API to propagate topology information to
interested clients. Some of the diagnostics, root cause analysis,
management, capacity planning, traffic engineering etc. tools could also
benefit from this API, since it will make life a lot easier for them. Or,
better yet, they will be able to use the ALTO interface, which will make
it even easier :-)=20

Standardizing the way to get network topology through ALTO will extend
ALTO's applicability rather than limit it. If ALTO does not define a
standardized way to generate maps from topology data, people will simply
use BGP (eventually with extensions that will convey the TE / IGP topology
information), and bypass an ALTO Service that a provider may offer.

Now, I would like to point out that the draft is only focusing on ALTO
maps that are generated from network topology data. There can be other
maps, generated from other types of data (for example from RTD
measurements, network probes, or from resource utilization measurements),
which will require their own APIs. This "other data" and "other APIs" are
not in the scope of the draft.
=20
>
>Ben
>
>
>_______________________________________________
>alto mailing list
>alto@ietf.org
>https://www.ietf.org/mailman/listinfo/alto


From robert@raszuk.net  Thu Apr 14 00:01:04 2011
Return-Path: <robert@raszuk.net>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C7F0FE0845 for <alto@ietfc.amsl.com>; Thu, 14 Apr 2011 00:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4iAaZDwh6HT for <alto@ietfc.amsl.com>; Thu, 14 Apr 2011 00:01:04 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfc.amsl.com (Postfix) with ESMTP id B566AE065A for <alto@ietf.org>; Thu, 14 Apr 2011 00:01:03 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGqapk2rRDoG/2dsb2JhbACmIneIb5stnHaFbgSNb4Nz
X-IronPort-AV: E=Sophos;i="4.64,209,1301875200"; d="scan'208";a="680971877"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-6.cisco.com with ESMTP; 14 Apr 2011 07:00:57 +0000
Received: from [192.168.1.66] (sjc-raszuk-87113.cisco.com [10.20.147.254]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p3E70t3n018416; Thu, 14 Apr 2011 07:00:56 GMT
Message-ID: <4DA69BAD.2020501@raszuk.net>
Date: Thu, 14 Apr 2011 09:01:01 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
References: <F57A3851-9239-4AEF-9420-6BE84A439B9C@niven-jenkins.co.uk>
In-Reply-To: <F57A3851-9239-4AEF-9420-6BE84A439B9C@niven-jenkins.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: alto@ietf.org
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2011 07:01:04 -0000

Hi Ben,

 > Regarding whether we need to standardise the Network-to-server "API"
 > for ALTO, my opinion is that we do not.

I highly agree with that opinion. Any attempt to standardize ALTO server 
API to network is a clear attempt to limit it's range of functionality.

Number of reasons:

- Attaching an ALTO server as passive IGP node is not an issue. Using
   BGP to propagate local IGP area topology to ALTO server attached to
   such area is really highly questionable improvement

- Using BGP to propagate remote IGP topologies is just a way .. clearly
   there are other ways to propagate IGP topologies from remote areas

- As defined today draft-gredler-bgp-te-00 is very selective in what
   information is propagted from LSDB or TEDB. Each addition of such
   information would require a new BGP extension definition. This will
   block ALTO innovation. There were already proposals stated during the
   last IETF to carry entire LSDB in BGP as opaque information however
   those are beyond the scope of this WG discussion.

- ALTO servers even today can benefit from other ways to get network
   information which would not have to be carried in BGP.

Many thx,
R.







> Authors, Colleagues,
>
> The meeting minutes from IETF 80 record:
>
> "Jan Medved presents Network-to-server API.
>
>    Jan Seedorf: scope of this work is explicitly excluded in RFC 5693
>    ALTO WG scope description. Enrico: this is new work, currently not
>    in the charter. We should hear it. Jan S.: we need to discuss if we
>    need to standardized it. Eric: it does, but maybe not now."
>
> Regarding whether we need to standardise the Network-to-server "API" for ALTO, my opinion is that we do not.
>
> Extracting network topology by passively listening to routing protocols for various purposes including aiding with operations, diagnostics, root cause analysis, management, capacity planning, traffic engineering, etc. is not a new idea. There are multiple products on the market to enable operators to do just that.
>
> An ALTO server that follows a similar approach as a mechanism to import network topology into its network topology/map/cost database is a reasonable proposition but in my opinion the ALTO WG should not attempt to standardise how a ALTO server should perform such integration with an operator's routing control plane(s), for example  because:
>
> * Extracting network topology is not an interoperability issue between ALTO servers. Each ALTO server can extract the network topology independently and if the topology needs to be distributed between ALTO servers then it is an ALTO Server-Server API that needs standardising *not* an ALTO Server-Network API. Interoperation between an ALTO Server and the underlying network(s) is a solved problem as is demonstrated by the numerous interoperable implementations of routing protocols.
>
> * Attempting to standardise a single approach is likely to limit the applicability of ALTO (or the relevancy of the ALTO Server-Network "API standard") because it is unlikely we would be able to converge on a single routing protocol that would satisfy the preferences of all operators that are likely to deploy an ALTO server.
>
> Ben
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From ben@niven-jenkins.co.uk  Thu Apr 14 15:16:27 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 7276CE0715 for <alto@ietfc.amsl.com>; Thu, 14 Apr 2011 15:16:27 -0700 (PDT)
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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gx+ad4Bmg323 for <alto@ietfc.amsl.com>; Thu, 14 Apr 2011 15:16:26 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfc.amsl.com (Postfix) with ESMTP id 816A0E065C for <alto@ietf.org>; Thu, 14 Apr 2011 15:16:23 -0700 (PDT)
Received: from cpc10-cmbg15-2-0-cust121.5-4.cable.virginmedia.com ([86.30.246.122] helo=[192.168.0.3]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1QAUpt-0005YP-5j; Thu, 14 Apr 2011 23:16:25 +0100
References: <C9CB0B72.22029%jmedved@juniper.net>
In-Reply-To: <C9CB0B72.22029%jmedved@juniper.net>
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
Message-Id: <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk>
Content-Transfer-Encoding: quoted-printable
From: Benjamin Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Thu, 14 Apr 2011 23:16:20 +0100
To: Jan Medved <jmedved@juniper.net>
X-Mailer: Apple Mail (2.1078)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2011 22:16:27 -0000

Jan,

On 14 Apr 2011, at 00:54, Jan Medved wrote:
> On 4/13/11 4:32 AM, "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk> =
wrote:
>> * Extracting network topology is not an interoperability issue =
between
>> ALTO servers. Each ALTO server can extract the network topology
>> independently and if the topology needs to be distributed between =
ALTO
>> servers then it is an ALTO Server-Server API that needs standardising
>> *not* an ALTO Server-Network API.
>=20
> Actually, extracting network topology and generating the abstracted
> network topology (maps) is an interoperability issue between ALTO =
Servers,
> and it can not be completely separated from the exchange of topology
> between ALTO servers. For ALTO Servers to be able to exchange (and
> reconcile) their respective abstracted topologies (maps) with each =
other,
> the topologies need to be equivalent. This then drives the need for a
> common set of data from which the topology is created and a normalized =
way
> to generate the topology from the data (which we mentioned in the =
draft,
> but did not attempt to specify).

I think this is the crucial bit for me. If you want two ALTO servers to =
produce the same result you need to identify the key bits of information =
they need to obtain from the network and how they will translate that =
into a ALTO representation of the network.

How they extract that information from the network is an orthogonal =
problem. Throwing the entire IGP into BGP (or for that matter specifying =
that an ALTO server must listen to both BGP and the IGP) doesn't help =
you with interoperability as you haven't specified what information the =
ALTO server needs know and what it needs to do with that data to =
generate the network and cost maps, you've just specified one possible =
way to import the raw data into the ALTO server.

<snip>

> Standardizing the way to get network topology through ALTO will extend
> ALTO's applicability rather than limit it. If ALTO does not define a
> standardized way to generate maps from topology data, people will =
simply
> use BGP (eventually with extensions that will convey the TE / IGP =
topology
> information), and bypass an ALTO Service that a provider may offer.

But your draft (and any ALTO Server - Network API) doesn't address how =
to standardise the way to get topology through ALTO. It just proposes =
one possible way to get topology *into* an ALTO server.

Ben



From richard_woundy@cable.comcast.com  Fri Apr 15 07:31:46 2011
Return-Path: <richard_woundy@cable.comcast.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C7DA5E073B for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 07:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.463
X-Spam-Level: 
X-Spam-Status: No, score=-108.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zuVGnvyu819u for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 07:31:42 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by ietfc.amsl.com (Postfix) with ESMTP id ED578E06EC for <alto@ietf.org>; Fri, 15 Apr 2011 07:31:27 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.119912761; Fri, 15 Apr 2011 10:31:26 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0270.001; Fri, 15 Apr 2011 10:31:09 -0400
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: Benjamin Niven-Jenkins <ben@niven-jenkins.co.uk>, Jan Medved <jmedved@juniper.net>
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: AQHL+c6LkCewQmYft0q5jprYZPNCL5Rcu78AgAF22wCAAMJEMA==
Date: Fri, 15 Apr 2011 14:31:08 +0000
Message-ID: <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com>
References: <C9CB0B72.22029%jmedved@juniper.net> <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk>
In-Reply-To: <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [76.96.111.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 14:31:46 -0000

As a co-author of draft-medved-alto-svr-apis-00, let me explain my motivati=
ons for interest in this subject.

My primary motivation is to have *some* scalable means to populate (my) ALT=
O servers with current network information. Note that I don't think there n=
eeds to be only ONE way to populate ALTO servers. Certainly it needs to be =
possible to use manual configuration as well. Maybe there is room for propr=
ietary mechanisms as well -- perhaps ALTO server vendor-driven (eg unique r=
outing ingest mechanisms and algorithms), perhaps ALTO server purchaser-dri=
ven (eg via open/proprietary APIs to the ALTO server).

My secondary motivation is to ensure that, with respect to automated popula=
tion of network information into ALTO servers, I could choose ALTO server v=
endors and router vendors fairly independently. That's why the use of a com=
mon protocol (BGP) is of interest, because it is commonly implemented by ro=
uter vendors and commonly deployed by service providers. We had talked a lo=
ng time ago in ALTO about using "looking glass servers" as a potential netw=
ork information source, and usually looking glass servers are based on BGP =
routes.

That's why I am interested in an open specification for an ALTO server to n=
etwork API.

-- Rich

P.S. I don't think ALTO servers need to listen to BGP *and* the IGP.

-----Original Message-----
From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Ben=
jamin Niven-Jenkins
Sent: Thursday, April 14, 2011 6:16 PM
To: Jan Medved
Cc: alto@ietf.org
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API=
?

Jan,

On 14 Apr 2011, at 00:54, Jan Medved wrote:
> On 4/13/11 4:32 AM, "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk> wrote:
>> * Extracting network topology is not an interoperability issue between
>> ALTO servers. Each ALTO server can extract the network topology
>> independently and if the topology needs to be distributed between ALTO
>> servers then it is an ALTO Server-Server API that needs standardising
>> *not* an ALTO Server-Network API.
>=20
> Actually, extracting network topology and generating the abstracted
> network topology (maps) is an interoperability issue between ALTO Servers=
,
> and it can not be completely separated from the exchange of topology
> between ALTO servers. For ALTO Servers to be able to exchange (and
> reconcile) their respective abstracted topologies (maps) with each other,
> the topologies need to be equivalent. This then drives the need for a
> common set of data from which the topology is created and a normalized wa=
y
> to generate the topology from the data (which we mentioned in the draft,
> but did not attempt to specify).

I think this is the crucial bit for me. If you want two ALTO servers to pro=
duce the same result you need to identify the key bits of information they =
need to obtain from the network and how they will translate that into a ALT=
O representation of the network.

How they extract that information from the network is an orthogonal problem=
. Throwing the entire IGP into BGP (or for that matter specifying that an A=
LTO server must listen to both BGP and the IGP) doesn't help you with inter=
operability as you haven't specified what information the ALTO server needs=
 know and what it needs to do with that data to generate the network and co=
st maps, you've just specified one possible way to import the raw data into=
 the ALTO server.

<snip>

> Standardizing the way to get network topology through ALTO will extend
> ALTO's applicability rather than limit it. If ALTO does not define a
> standardized way to generate maps from topology data, people will simply
> use BGP (eventually with extensions that will convey the TE / IGP topolog=
y
> information), and bypass an ALTO Service that a provider may offer.

But your draft (and any ALTO Server - Network API) doesn't address how to s=
tandardise the way to get topology through ALTO. It just proposes one possi=
ble way to get topology *into* an ALTO server.

Ben


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

From robert@raszuk.net  Fri Apr 15 08:08:24 2011
Return-Path: <robert@raszuk.net>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 77CB3E08D6 for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 08:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnIgWvnkdULK for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 08:08:23 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfc.amsl.com (Postfix) with ESMTP id B46FAE0796 for <alto@ietf.org>; Fri, 15 Apr 2011 08:08:22 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHReqE2rRDoG/2dsb2JhbACmA3eIb55EnHuFbgSNeIN0
X-IronPort-AV: E=Sophos;i="4.64,219,1301875200"; d="scan'208";a="338383597"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-2.cisco.com with ESMTP; 15 Apr 2011 15:08:22 +0000
Received: from [192.168.1.51] (ams-raszuk-2-87113.cisco.com [10.55.99.78]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p3FF8KkE015659; Fri, 15 Apr 2011 15:08:21 GMT
Message-ID: <4DA85F5D.3050402@raszuk.net>
Date: Fri, 15 Apr 2011 17:08:13 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
References: <C9CB0B72.22029%jmedved@juniper.net>	<87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 15:08:24 -0000

Hi Richard,

> My secondary motivation is to ensure that, with respect to automated
> population of network information into ALTO servers, I could choose
> ALTO server vendors and router vendors fairly independently.

But do you need to have a RFC which mandates support of BGP-TE spec by 
an ALTO server ?

How about ALTO vendors which not have BGP code at all today ?

Are they out of luck to even propose ALTO servers ? I could really 
easily imagine an ALTO vendor which does not support BGP and collects 
network information (both routing and non-routing related) via their own 
self discovering application modules running on all or on subset of 
routers of given network. Result: no need to configure and maintain 
dozens if not more of BGP sessions both on the ALTO server as well as on 
the routers, no need to support BGP or IGP on ALTO server side.

And on the other hand if you want to choose a particular deployment 
model you can select ALTO server vendor which does support BGP-TE RFC 
XYZ. Just like today when you are buying routers or other network 
devices you just make sure they speak the same language as described in 
the protocol RFC XYZ. No need for another API spec to mandate support of 
RFC XYZ.

Cheers,
R.






From richard_woundy@cable.comcast.com  Fri Apr 15 08:44:37 2011
Return-Path: <richard_woundy@cable.comcast.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DFD85E08CC for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 08:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.099
X-Spam-Level: 
X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=-3.364, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v78Vlpi3ATg9 for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 08:44:37 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfc.amsl.com (Postfix) with ESMTP id 147F4E088E for <alto@ietf.org>; Fri, 15 Apr 2011 08:44:36 -0700 (PDT)
Received: from ([24.40.55.40]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.34120518; Fri, 15 Apr 2011 09:47:40 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0270.001; Fri, 15 Apr 2011 11:44:32 -0400
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: AQHL+c6LkCewQmYft0q5jprYZPNCL5Rcu78AgAF22wCAAMJEMIAAWHSA///AW9A=
Date: Fri, 15 Apr 2011 15:44:31 +0000
Message-ID: <1CA25301D2219F40B3AA37201F0EACD1134E8271@PACDCEXMB05.cable.comcast.com>
References: <C9CB0B72.22029%jmedved@juniper.net> <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com> <4DA85F5D.3050402@raszuk.net>
In-Reply-To: <4DA85F5D.3050402@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [76.96.111.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 15:44:38 -0000

I think you are mixing two things together, that I see as independent.

> But do you need to have a RFC which mandates support of BGP-TE spec by an=
 ALTO server ?
> How about ALTO vendors which not have BGP code at all today ?

There is a ALTO client-to-server protocol spec. There is a ALTO server-to-n=
etwork protocol spec. They should be independently specified, and can be in=
dependently implemented.

If you want to build a ALTO server that follows only the client-to-server p=
rotocol spec, go ahead. There is probably a market for a product like this.=
 This shouldn't be prohibited.

I think there are a number of parties that want an ALTO server that would f=
ollow specifications for both client-to-server and server-to-network protoc=
ols.

> I could really easily imagine an ALTO vendor which does not support BGP a=
nd collects network information (both routing and non-routing related) via =
their own self discovering application modules running on all or on subset =
of routers of given network.

So in other words, I need to deploy "application modules" on my routers for=
 your approach to work. And if your application modules didn't run on my ro=
uters, I have to replace my routers to enable ALTO support in my network. H=
mmm.

> And on the other hand if you want to choose a particular deployment=20
model you can select ALTO server vendor which does support BGP-TE RFC=20
XYZ.

Yes we could. The question is what needs to be carried in BGP-TE to be usef=
ul to ALTO servers. That's where the interoperability concerns arise, and w=
here an open specification is needed.

-- Rich

-----Original Message-----
From: Robert Raszuk [mailto:robert@raszuk.net]=20
Sent: Friday, April 15, 2011 11:08 AM
To: Woundy, Richard
Cc: Benjamin Niven-Jenkins; Jan Medved; alto@ietf.org
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API=
?

Hi Richard,

> My secondary motivation is to ensure that, with respect to automated
> population of network information into ALTO servers, I could choose
> ALTO server vendors and router vendors fairly independently.

But do you need to have a RFC which mandates support of BGP-TE spec by=20
an ALTO server ?

How about ALTO vendors which not have BGP code at all today ?

Are they out of luck to even propose ALTO servers ? I could really=20
easily imagine an ALTO vendor which does not support BGP and collects=20
network information (both routing and non-routing related) via their own=20
self discovering application modules running on all or on subset of=20
routers of given network. Result: no need to configure and maintain=20
dozens if not more of BGP sessions both on the ALTO server as well as on=20
the routers, no need to support BGP or IGP on ALTO server side.

And on the other hand if you want to choose a particular deployment=20
model you can select ALTO server vendor which does support BGP-TE RFC=20
XYZ. Just like today when you are buying routers or other network=20
devices you just make sure they speak the same language as described in=20
the protocol RFC XYZ. No need for another API spec to mandate support of=20
RFC XYZ.

Cheers,
R.






From vkg@bell-labs.com  Fri Apr 15 09:41:57 2011
Return-Path: <vkg@bell-labs.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id AF979E0714; Fri, 15 Apr 2011 09:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.266
X-Spam-Level: 
X-Spam-Status: No, score=-105.266 tagged_above=-999 required=5 tests=[AWL=1.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1WSM80L44DFR; Fri, 15 Apr 2011 09:41:53 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfc.amsl.com (Postfix) with ESMTP id CBEE5E0699; Fri, 15 Apr 2011 09:41:52 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p3FGfpmS009058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 15 Apr 2011 11:41:52 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p3FGfpJm013097 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Apr 2011 11:41:51 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p3FGfoCM014900; Fri, 15 Apr 2011 11:41:51 -0500 (CDT)
Message-ID: <4DA875CA.4010505@bell-labs.com>
Date: Fri, 15 Apr 2011 11:43:54 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9
MIME-Version: 1.0
To: "p2prg@irtf.org" <p2prg@irtf.org>, alto <alto@ietf.org>
Content-Type: multipart/mixed; boundary="------------070306010205050007050901"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: [alto] ns-3/ALTO: Influencing suboptimal peer selection
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 16:41:57 -0000

This is a multi-part message in MIME format.
--------------070306010205050007050901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Folks: In the Prague p2prg, I had presented an ns-3 simulation
of ALTO [1].

The topology was simple (see slide 4 of [1]): an
ISP (Chicago-ISP, PID 1), a peering link (ISP-Peering, PID 2),
a transit link (ISP-Transit, PID 5), and a couple of links
representing the rest of the Internet (Internet-1 and Internet-2,
PIDs 3 and 4, respectively).  A cost map was provided in
slide 5 of [1].

A couple of simulations were shown, the first showed results
of traffic transferred from the Chicago-ISP to rest of the
network without ALTO, and the second simulation showed the
resulting decrease in transit traffic and increase in peering
and intra-ISP traffic when ALTO is used.

I was running a third simulation, which is probably the most
interesting one.  It did not complete by the time p2prg was held
in Prague.  This simulation sheds some light on whether ALTO
can influence the choice of suboptimal peer selection.

One issue that has been talked about in ALTO is whether it can
influence the choice of sub-optimal peers; in other words,
can ALTO be used to purposely provide sub-optimal peers simply
because a peering relationship exists and the peers in the
peering network are sub-optimal (i.e., they may have less upload
bandwidth when compared to other peers).

The third simulation shows that this is not the case, and other
publications [2] have experimentally demonstrated that this
is not the case for BitTorrent at least.  BitTorrent exhibits
strong clustering behaviour, where similar-bandwidth peers
cluster together to ensure effective sharing incentives by
rewarding peers who contribute proportionally more to the
system.

To run the third simulation, I kept the cost map invariant.
However, I downgraded the data rate of the ISP-Peering
peers.  So, compared to the rest of the peers, the ISP-Peering
peers offer upload at a much reduced rate.  The expectation is
that over time, the peers in ISP-Chicago will stop preferring
peers in ISP-Peering, even though the cost to reach those peers
is minimal.  And, the peers in ISP-Chicago would start
preferring intra-ISP peers (i.e., other peers from ISP-Chicago),
and even peers from ISP-Transit.

This appears to indeed be the case, and the result is shown in
the attached PDF.  Here is a summary table; in the table below,
"Simulation 2" is the third simulation:

             |      Simulation 1         |      Simulation 2
Traffic     | (all peers have similar   | (peers in ISP-Peering
destined to |       data rates)         |  have lower data rates)
------------+---------------------------+-----------------------------
ISP-Chicago | 1.78 GB                   |   1.97 GB  (+ ~11%)
ISP-Transit | 1.84 GB                   |   2.14 GB  (+ ~16%)
ISP-Peering | 2.26 GB                   | 606.97 MB  (- ~3.7x)
Internet-1  | 2.03 GB                   |   2.38 GB  (+ ~15%)
Internet-2  | 2.12 GB                   |   2.35 GB  (+ ~12%)

[1] http://www.ietf.org/proceedings/80/slides/P2PRG-5.pdf
[2] "Clustering and sharing incentives in BitTorrent systems",
  Arnaud Legout, Nikitas Liogkas, Eddie Kohler and Lixia Zhang,
  ACM Sigmetrics, June 2007.

I thought some of you may find this interesting.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

--------------070306010205050007050901
Content-Type: application/pdf;
 name="bt-by-lan-128.0.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="bt-by-lan-128.0.pdf"

JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFIvRmlsdGVyIC9GbGF0ZURl
Y29kZT4+CnN0cmVhbQp4nJS9UdP2unEkdn9+xXcX+0LHJIABCd/FW1uurdpUdi1d7o1XK2i1
8chlyUkq/z4cYAbTrThVe0pln+mXjQ98SE4TAMnpf/lx/Xz/uOx//t/f6k9/8w/Pj9//+af7
+vF//7Q2/fiHv/9JLnl+3LXfP9TjMt4f/7TjftcRf+/lKvH3u9zt+/uv/Z/50+9/+hf7Z+1/
/p/f6o+/+83X4/vjY/5mfsT7x69sT+S+fq4fa/z8lG+L/vRXP66//s3/+Onf/+an//xT601i
Z3a8d2bFvjM73jvjHN+Z/+l9aH18R+XtP9en1L0P93XBbpRaz26s2HfD4tiNFftubM4v3o3y
/Dx4NwruRn3LHbux470bK/bd2PHeDef80t2o3x48vBuVdqNd79mNFftuWBy7sWLfjc35xbvR
5OfGu9FwN8oYPXZjx3s3Vuy7seO9G875xbtxtZ8L74bQbsjbzm6s2HfD4tiNFftubM4v3Y3S
K+9Ep524n3J2YsW+ExbHTqzYd2JzfvFOlPvnl3fjwd24n37Fbux478aKfTd2vHfDOb90N+73
+rnzbry4GyRhd/Fd+ifevT6e+LuU/Psv2A2pthv39/9LL3+pXGsfisgV+7Bi3wf/+9oH//va
B//7L96H0u7vWLzn6uS9qE99Yy9W7Hvhf1974X9fe+F//8V7UaX/XN7+b+jn2o02yhO7sWLf
Df/72g3/+9oN//sv3o32yM/32Y3/z9Ho9y2xGys+l+f6+9oN//vaDf/7L94NGfXnEbtR/u0s
qcV+8/OduT/97n+ih1/tO/f3n/p8t8vxCf378+7hN3/6xzn/8Nsf/+Wv/o//+jd//i9/bZ3l
Dsltp6d8sv7cm/4H/d3H/fPvfvvPf/xvTv9VrT+/32H5duj7N//bT3/1v/7H3/zvP/78uz/9
X7/709/++PUf9P/8p3/81z/88x9/FGPf93eu2/fvt8WN/uc//+nHf/j1f/rVv/vvf/jtP/7+
n9e/e7dvX99Dhc1/++P++TsCf/93//X/+dff/XmRyzcMqJcQ+z/97nd/+sMff/+3n+Z14/9v
fxf0u/x8yScrh/3Hf/3dn/74u3/91f23P8rP32UM/7RR/iNQyqLIofwvP/1Kfr5af3lXv1/2
xz//4V+N/P0V/r1a5WfLlF+V9y/39Jzq62fpl7TnG3WNMuyfPn/5xkj3M+THc39jhefLujHs
Kpg/iY3G/v/bfUO0f6vdr4/q9T1Aazv+BiNj2ODluc9gbccTkBKrjXWBPgIthFrIapGsNpop
4XtlixVPQEqsNmRYDH281Me7+0jW19r2cEAfg/oY3sdhfbGNHkeDFm21yC33d8GLH3injP3P
yI7X4fj+yXblP7PjCUiJ9cXN4gEtBrXYfSTr6+/7oe2u2WLFE5ASqw0bY7b7hRYvtXhXi2R9
rb+b/jc2zRaF+ijex2F9sWlPgT4K9VF2H8naJ6zVnBnseAJSYn2x9VcfaPFQi2e3OKwv/i68
1qCPRn007+Owvj1cf4c+GvXRdh/J8v4kk2bHE5ASy/uTDi06tei5V7IT87bj1qGPTn3s+Qaw
2rjsuHXoo1MfffeRrK+1xU8mzY4nICXW19r2EJK/UfI3T/5kfTdq20NI/kbJ3zz5k/X1JxZD
H5T8zZM/We19bA9fyKiXMupdGQWs9r525UPyt0FZO1bWAuv7TbfF0MegPlwZkvXF1YYY2YeQ
MogrQ7L2b5LrhRYvtXjPL99bvuP2XWMCyiCkDOLKkKwv5y+LoQ9SBgllOKzvqvyUSEAZhJRB
XBmS9fVne1geaPFQi51Ryfr6+46bgDIIKYO4MiTra23HDZRBSBnElSFZ+xoTUAYhZRBXhmR9
R7pb3KFFpxY7o5K1FVVAGYSUQVwZkrWzS0AZhJRBXBmStXNeQBmElEFAGcSV4bbj1gVaCLXw
jDosP26gDELKIK4Myfpar79DH6QM4sqQLD9uoAxCyiCuDMn6+rNr7IWMeimj3p1Ryfpar3hA
i0EtdtYm68tH6w+UQc6wILZ8icHDAonk7zte/8x3+PuVSbPjCUiJtS+KDsnfKfn7lbfsveWT
py9JOyR/p+TvO/mB9cXdYuiDkr/v5AfWFrReMml2PAEpsb7W9psg+Tslf9/JD6xPmK0/SP5O
yd938gNri2aH5O+U/N2TP1n7ougtk2bHE5ASy38TJH+n5O+e/Mnat70Oyd8p+bsnf7K+C2/F
0Aclf4/kP6ydDh2Sv1Py90j+w9ri3yH5OyV/9+RP1r7BdEj+TsnfY1hwWN4akr9T8vcH+ojk
/wStQ/J3Sv7+5tCjvzn06JD8nZK/e/In62tt/UHyd0r+Hsl/WFueOiR/p2FB38MCYH39rRj6
oGFBD2U4W/Zt7wFleEgZHleGZG15ekAZHlKGJ4YFh/XF35X/gDI8pAyPDwuStXPlAWV4SBke
HxYk69vD78p/QBkeUobHlSFZX+ti8QMtHmrhWXtYWx8fUIaHlOHxYUGytgY/oAwPKcMTynBY
3h8ow0PK8LgyJMuPAijDQ8rwhDIc1r4qH1CGh5ThAWV4QhmsNSjDQ8rwhDIc1h7Y2+rRadEx
owwpsT4NXn8XaCHUQrZSny3f4NmuSlCGh5Th2coArJ1dDyjDQ8rwxLDgsHauPM+AFoNaZEbt
LXsY8oAyPKQMTwwLDmsr6gPK8JAyPKEMh/X1Z78JlOEhZXhcGZL1HQVrPSCjBmXU2PfaZO2j
8IIyvKQMrytDsvZ1/IIyvKQMrytDsvY19oIyvKQMrytDsr7zPyx+oMVDLfx+flj7Tv2CMryk
DG/J+/nrY4bv1H8x9EHK8PqYIVlff5+uvKAMLynD62OGZO0MfmuHFp1a9JPne8t3xdhRAGV4
SRneGDMc1hfbbwJleEkZXleGZH3n3/4OyvCSMrxbGYC1r5hXBFoItZBzXe0t/ptAGV5ShjeU
4bD26OwFZXhJGd5QhsPyPQRleEkZ3lCGs2VPrt+nQYtGLXIKvrf4lQ/K8JIyvE/ez/eWrUQv
KMNLyvBuZQDWVrsXlOElZXh9KSFZ+777DsioQRk16rk77y1bu15QhpeU4R3vUbjXlcEmpQOU
YZAyjBgzHNb3m5rFL7R4qYWrz2Hte4kdvNPixowypMTa9/YByjBIGcb9nBHA3vLNXmwPQRkG
KcPwMUOy9l10gDIMUoZRcqQ/YinBfhMowyBlGLGUcFh72W2AMgxShlFzcW64MtgIcIAyDFKG
4cqQrD32HaAMg5RhhDIc1h7VDFCG4cqQW+42fjSciA6RMyAanvzNdhuSf1DyD0/+ZPkJg+Qf
lPwjJgyH9R3ML4EGJP+g5B8+YUjWTtIByT8o+cfTTiqPJ9fGBiT/oOQfkfyHtVfpByT/oOQf
PixI1neKu8XQByX/8GFBsvbq9oDkH5T8w5M/WW2dtwHJPyj5hyd/sr642jPC04fHE5ASq9k1
98UvtHipha/MH9Y6/+XK5Pd4AlJircc1X/xAi4da+Kr5YbXxlC8u0EehPjz5k7Wemnwx9FGo
D0/+ZHl/9c4W9cYW9c69qr4y3yzu0KJTix6rm75lnf9yNeijUR+e/Mny1g36aNRHgz5iHdFa
y5Ut5MIW4hl1WOvJzBcLtBBqsbM2WeuJRrk69NGpj1CGs2UJ8xdDH536cGVI1tfaflMf0GJQ
C3+edlgrV8qVyuDxhC33N4fB9bfvjyPSbMUnBV74ZzD5F1JirSeWXwxJ81LSvDtpkrUeVJVr
QGIOSkxP/mQ1U78vhj4G9eHJn6wvlh/lhuS/KflvT/5k7Qvvvh5o8VCL51yee8vu74bkvyn5
b0/+ZO0L74bkvyn5b0/+ZH23i+8o3JD8NyX/HasFh7UW+7+4Q4tOLXo8EvAta2203JD8NyX/
Xc/iu29ZI/Evhj4o+e96xuu+Zd2Syg3Jf1Py33HnP6w10vhigRZCLSTGI75lp8MNyX9T8t+e
/Mn6Wttxg+S/KflvT/5k+W+C5L8p+W9P/mT5FdMbtGjUouV11f12alclJP9NyX978ifLjxsk
//1QHzks8C1rUPHF0MdDfbgyJKvZoK98U7xs8VJGvTujkrVGZV/8QouXWrwxdvMtayReblCG
m5ThHme87lu+/tbfoQ9ShtuVIVlrhbDAa7YeT0BKrH3lF1CGQspQXBmStW/4BZShkDIUGBaU
G/oAZSikDOWGPlwZTLULKEMhZSiuDMnaZ7OAMhRShhLKcFjrbbFSQBkKKUNxZUjWzpUCylBI
GYorQ7LWQLIUUIZCylBcGZK1Vou+WKCFUAuJNSXfsh7qlQLKUEgZiitDstaq1xdDH6QMxZUh
WWtgXwooQyFlKKEMh7XmOV/coEWjFmfV3Les5yxfPKDFoBY7a5O187GAMhRShuLKkCzvD5Sh
kDKUmDCcLX7+QRkKKUNxZUiWHwVQhkLKUEIZDmutFpUCylBIGUoow2F5f6AMhZShuDIka98Z
KihDJWWorgzJ2nefCspQSRlqKMNheWtQhkrKUG/oIyYMYjH0QcpQY8JwWPveXktm1I4nICXW
egXqizu06NRiZ22y9giwgjJUUoYaE4bD8tagDJWUoVbow5XBVLu2zKgdT0BKrH3fraAMlZSh
ujIky480KEMlZagwZqiuDDZhrKAMlZShujIka73Q9MUDWgxq4ffzw9qThwrKUEkZqitDsrai
VlCGSspQXRmS5VclKEMlZaihDIflZ/N5ocVLLXJ6vLes56mlgjJUV4bcYqM9mpRUT/5NeI8Y
V0j+SslfI/kPy1sPSJpBSTOe7GM859JpkPyNkr/FsOCw1mOOL36gxUMtnngY4lv27btB8jdK
/ubJn6wtzO3u0KJTi37ke2/Zs+EGyd8o+Zsnf7L27aJB8jdK/ubJn6z1OmhpkPyNkr9F8h/W
Huq0KtBCqIWcAdHesmfcDZK/UfI3T/5kbSlvkPyNkr9F8p8tfqQh+Rslf4vVgsPaQtCkQYtG
LdqRi73FjzQkf6Pkb5H8h7UTqEHyN0r+1nMK3jz5r9di6IOSv3nyJ2tPGNuTGbXjCUiJtXOl
QfI3Sv72ZNY2T36TjgbJ32hY0GLCcFhbnhoMCxoNC5orQ7LWw5fSQBkaKUNzZUjWWun8Ysha
UoYWynBYe0AsoAxCyiCuDMlaDy2++IEWD7V44tGGb9k3MQFlEFIGCWU4W9abhl/coUWnFq4M
h7W1S0AZhJRBXBmStc+NgDKIK0NuuT/RJfmWWC1oO44VIoHkF0p+qefNd9+yhUAg+YWSX9pZ
fPctX+tiMfRByS+e/Mna82eB5BdKfvHkT9Z6q+aLG7Ro1MLH64e1R7ACyS+U/OLJn6w9ChBI
fqHkl1gtOKy9bCiQ/ELJL3HnPyy/jCD5hZJfPPmTtefoAskvlPzy5ExePPkv+zskv1Dyiyd/
stYTsi+GPij5JYYFh7VlVgYkzaCkGTmW3lv2KFkg+YWSX0aOpWXkwniH5O+U/D3mBIe1j1uH
5O+U/D3mBGfLvlH2OxNzxxOQEmvP6jskf6fk7578yfqufIsh+Tslf/fkT5b3B8nfaVjQY05w
WPuBQq+ZUTuegJRY3h8oQydl6KEMh7V1pYMydFKGHnOCw/I9BGXopAzdlSFZfjbbgBaDWow8
581v2d+V30EZOilDj2HBYfkegjJ0UobuypCs9Ry1dFCGTsrQQxkOaz0M++IXWrzU4jwy8y1f
bEcalKGTMnRXhmR5f6AM3ZUht9hqOd0iuif/InjyP7YTLyTNS0nz7qRJ1pbyDsnfKfm7J3+y
/PBD8ndK/h7Jf1j7hz6Q/A8l/+PJn6w9fX2uDi06tchJ7t6yb3sPJP9Dyf948ifr62/9Hfqg
5H88+XPLXlx+IPkfSv6n5JO3p+STt6cItBBqIWfUurdsmX0g+R9K/qfmRPqpOZF+IPkfSv6n
5kT6qZmYDyT/Q8n/tPNBnG/xPWwNWjRq0fJ3tFx8fyD5H0r+p+Xi+9NyvP5A8j+U/I/keP2J
YYGdTUj+h5L/iWHBYe1x9dMzMXc8ASmx9jjugeR/KPkfT/5k7dveA8n/UPI/nvzJ2tLxQPI/
NCx4nhSYx4cF67jBsOChYcETynBYewT7gDI8pAyPK0Oy9uOzB5ThIWV4XBmS5fkIyvCQMjyh
DIe15yAvKMNLyvDGnOCwtpS/oAwvKcPrypCsff5fUIaXlOG9z2t0vmXP0V9QhpeU4b1zJv/e
+bz8BWV4SRneWCo8rP1g5AVleEkZXleGZO0Z9wvK8JIyvK4MydoDyReU4SVleOt5Ld637Ov4
BWV4SRnelo/lXlcGu2JeUIaXlOF1ZUjWfjzwgjK8pAyvK0OyvDUow0vK8Ar0EcpQLYY+SBne
UIbD2qsTLyjDS8rwujIkay/8vqAMLynD68qQrH3lv6AMLynD+5zvaH2Ln01QhpeU4X1y8f19
cib/vpBRL2XUW85Mfm/xXAFleEkZ3jcX3983H6a/oAwvKcM78mH668pgayYvKMNLyvC6MiRr
54p93RItdjwBKbF2Bg9QhkHKMFwZkrV1ZYAyDFKG4cqQrD39G6AMg5RhxGrBYXnrkhm14wlI
ibXvcAOUYZAyDFeGZO17yQBlGKQMI8YMh7VHNQOUYZAyjBgznC2+h3VAi0EtcmF8b1mv+pcB
yjBIGYYrQ7L2QsQAZRikDCMmDIflRwGUYZAyDBgzDJgw2FAzW7zU4j1X+96y83GAMgxShtEz
a0eMGVYMfZAyjBgzHJZfMaAMg5RhxFLCYe2R7HgeaLEzKreMv5gvDM/9td1z38aRA3J/UO4P
z/1k7YclA3J/UO6PWCw4W/YU3eobZQvKmdHPRH5vWZPIemXuezwBKbHWffKLO7To1KLH3dS3
LCWv1w193NTHfV7W8S3tHcNigRZCLfzF98Nay0v1ytz3eAJSYq0r9Yuhj0J9ZO77lnXc6lWh
j0p91PNwz7esccsXN2jRqMX5itW3rFXcLx7QYlCL8+6rb1nLS/Vq0EejPjz3k7XGFF8MfTTq
w3M/WUtr6iXQh1AfMSo4LG+due/xBKTEWk+E6pW57/EEpMRaKvvF0EenPjz3k7Xmi/V6oI+H
+ojFgsNaa+Rf/ECLh1o8sZLuW/z856jA4wlIibVeDvpi6OOlPlwZkrXGX/Ua0MegPmK+cFie
XQOydlDWhjIc1lpVqDcow03KcIcyHNY+Nzcow03KcF/nyZ9vWbpcb1CGm5ThjvnCYa0VmHqD
MtykDLtIE7KWotYblOEmZbjLmeX7ln0UblCGm5ThdmVI1pq/1xuU4SZluOuZ5fuWNVb94gYt
GrVoMaL1Ld4fKMNNynDHqOCw1oit3qAMNynDHfOFw1qvyNQblOEmZbjbeZHGt/geSmbUjicg
JdYaFX7xCy1eavHG2NG3rDWCeoMy3KQMd64k+JadKzcow03KcMeo4LB2Bls1vNPiwYwypMTa
98QblOEmZbhdGZK1xhT1BmW4SRnu93wS41v2XfQGZbhJGe5QhsPaGnwPyKhBGTXOONu3+PkH
ZbhJGe5QhsPad9ECylBIGcp1auL4lrWe8sUdWnRq0WPVxbc0+9ykljszascTkBJrvXz9xQIt
hFqcQlK+pdnnJrWAMhRShuLKkKz1eOKLoQ9ShhJjhsNaa4FfPKDFoBYjVgx9y/ebrEYbKEMh
ZSiuDMnyowDKUEgZiitDsr7Y/g7KUEgZiitDsr7Yzk17ocVLLfyV+cPy/kAZCilDcWVI1tbg
AspQSBmKK0Oy1tyhFlCGQspQ+nle71t2Ppb+QIuHWmTW7i1rZa8WUIZCylBcGZLlRwGUoZAy
FFeGZK01/1pAGQopQ3nPkwHfsjPYqixmC8qo97y06lu2dhVQhkLKUEIZDmvnfAFlKKQMBZSh
xJjh+00VlKGSMtTrvGLnW/b4wQr9ZQuhFudbFt+y97CCMlRShnqfL9B8y77GKihDJWWorgzJ
2ue/gjJUUoYaY4bD2iOO79KHFo1anEddvmWrdgVlqKQM1ZUhWfveXkEZKilDjTHDYflxA2Wo
pAzVlSFZWx8rKEMlZajx9OGw1sPRL36hxUstXBkOa60q1ArKUEkZqitDsnwPQRkqKUMNZTis
fS+poAyVlKG6MiRr33crKEMlZaiuDMlaM+9aQRkqKUN9zvzct2ztqqAMlZShPmcNwLes2oC1
gjJUUoYaynBYa3Xkizu06NTiPM/zLX4dgzJUUoY6cg2gujLYDKmCMlRShurKkKx9T2ygDI2U
oYUyHNa+wzVQhkbK0FwZkrV/UwNlaKQMzZUhWfv8N1CGRsrQYsxwWPuqbKAMjZShlfOaj2/Z
o/4GytBIGZorQ7K2djVQhkbK0Mr50MW37DlVA2VopAytnlfmfct6EvHF0AcpQ3NlSJafm5YZ
teMJSIm17z4NlKGRMrR23o3zLfte0kAZGilDi9nEYa1nF18MfZAyNFeGZPlv6plRO56AlFhb
URsoQyNlaP186OJb9sy7gTI0Uob25Py8PWfl7ouhD1KG9pxXcHzLWjH+BBUy6qWMeu9YV/Yt
Ox8bKEMjZWhvZm1zZXhtD0EZGilDc2VI1r6LNlCGRsrQXBmSte8lcmVG7XgCUmKtVdUvFmgh
1OK8nOdbtmoLKIOQMkiMGQ5ra7CAMggpg7gyJGtf+XIPaDGoxflw1bfs0YCAMggpg8CYQVwZ
TIMFlEFIGcSVIVl7XCqgDELKIK4MyfqOmx3p+kKLl1r4/fyw1tskVUAZhJRB2nkFx7fs61hA
GYSUQdr5BM637Lm6gDIIKYPI+czOt/hRkAdaPNQiR/p7i59NUAYhZZBe8py7MnTrD5RBSBnE
lSFZe+wroAxCyiAxZjgs7+/p0CLeaI0t981vtH5joDt31ZPfphsCyS+U/OLJn6y9cCqQ/DKi
KkVssW+EG3U85Ky5WhwjmA753Sm/u+d3stY7U18s0EKoxe4jWbu/DvndKb/7fZ7K+Zatix3y
u1N+9/s8lfMt+z7VIb875Xe/z1M537LnnR3yu1N+93I+V/Ete9zQIb875Xcv56mcb9kr6B3y
u1N+93jCcFi+h5DfnfK717wr95or8x3yu1N+95Yr893z29ShQ353yu/eUkN65LedG8jvTvnd
I78Py88N5Hen/O6e37nFzz/kd6f87pHfh7XvhR3yu1N+934+sPct6z2Hb3oAfVB+d8/vZPke
Qn73p1OLnr/j6UcROtz5O935OyR/9+S3FfQOyd8p+bsnf7L2aKZD8ne68/eRz+x6rBbY+R+Q
UYMyypUhWfuqfEAZHlKG5zpvwPiWPXZ/QBkeUoYnVgsOa72vUR9QhoeU4bnPmzy+Zd8Ln7tB
i0Yt8o65t+zz/4AyPKQMz31qyfiWrXYPKMNDyvC4MiRrve/3xdAHKcNTzjc5vsX3sGZG7XgC
UmLtUdkDyvCQMjxx5z+sffd8QBkeUoYn5gSHta+xB5ThIWV42nle71v2k8tHMqN2PAEpsfbY
/QFleEgZHleGZO2cf0AZHlKGB5ThcWVYewjK8JAyPK4Mydo6/6T9gscTtvzllynfH88rdite
HZvtByT/Q8n/ePInaw9rH0j+h5L/ec+LNL5lJ+kzIGkGJY07LCSrjcv2EJL/oeR/PPmTtQ/N
C8n/UvK/kfyHtT5L/GKBFkItvL7kYe3h4Jv2Cx5PQEqsfdxeSP6Xkv/15E/WlvIXkv+l5H/v
8/qbb9lH+oXkfyn53xgWHNaeNLxpv+DxBKTE2sL8QvK/lPxvPa/Y+ZZ9Nl9I/peS/41hwWGt
r4bqC8n/UvK/nvzJ2oscb9oveDwBKbF2yr2Q/C8l/yuZmK8n/zpukPwvJf8ruYz3evKX5XUG
fVDyv7EgcFjrM7gv7tCiUwuv2HpY+wbzQvK/6L2ykBJrTwFeGBa8NCx4XRmStYq61xeU4SVl
eF0ZkrUf5L4vZNRLGRX2C2fLfpD7gjK8pAxvKMNh+ZUPyvCSMrxDMj9CGb7WA5RhkDKMUIbD
2mdzgDIMUoZxnWJVvmWrxABlGKQM4zpVYX3L/k0DlGGQMow7H9gPVwY7/wOUYZAyjPsUpPct
+/wPUIZByjBcGZK1l8IGKMMgZRiuDMnay4YDlGGQMoxQhsPaC9gDlGGQMgxXhmTt+9UAZRik
DKPlY7kRymDHDZRhkDKMUIbD2ko0QBkGKcNwZUjWHoYMUIZByjAkFwSGK8N36usAZRikDMOV
IVm+h6AMg5Rh9Mza0fNeO0AZBinDcGVI1h64DFCGQcownlNf0rfsu+gAZRikDOPN12xGTBhs
D0EZBinDeCVz0I1ZzD1ugDIMUoYxTlVY3+LHDZRhkDKMGDMcVrMSqeb9GC08noCUWKta6Bc3
aNGoxTFm8S0r5794QItBLY4y+JblC9CuG/q4qQ9XhmR5fzf0cVMfrgzJWsPbdqUxi8cTkBJr
vSL4xS+0eKnFMZjxLUuJ2lWhj0p91FPd1rf4ka7QR6U+6pvnI8YMdhTSmMXjCVvu7/aPg+Dv
j0/cuFbsM8d2CfwzmPwLKbH8hGXyezwBKbHW08R2pf2CxxOQEssPfya/xxOQEmutcLbrgT4e
6iOS/2xZ6+BfDH081EesFhzWGhy164WkeSlp3rM25luWdHyxQAuhFudbFt+yBpLtGtDHoD5i
WHBYfjYH9DGojyF5zsdZw/9iSBq3X8gt983VItt9nbH0iuOQ35DfN+X37fmdrDUebTfk9035
fd/nAZ5vWYtnX/xCi/jCNLbY//GuegovQqTwbTH8M5TCd6TwYe3r94YUvimF70jhw9pn8U4T
BY8nICXWEv12Qwrf6K20kBJrPX37YuijUR+R34e1yti3G/L7pvy+Pb+TtVYGv7hDi04tzlvp
vmUNo9oN+X1Tft/9DMl9y1pX+mLog/L77ufJum/x1pDfN+X3/UAfnt+WIzfk9035fT/nPV3f
4pcq5PdN+X2/V17Q7/mO7IsFWgi18OHyYa0BZLshv2/K7zvy+7DWgOWLoQ/K7ztXA33LGnh9
MSTmoMQc59mWb9lHocDNvdDNvVznfRjfso90geQvlPwlFgTOllWSrxVI/kLJX+Lmflj7SBdI
/oL2KgspsfYttcDNvdDNvZS88RZXhtUfKEMhZSiuDMnaKlFAGQopQwllOKydwQWUoZAylFCG
w9pXTAFlKKQMpZ2n3r5l60oBZSikDKWl+hRXBtOuAspQSBlKrAYe1rKr+OIOLTq1WBkFrPXF
XiugDKXHSl1ssdKqJN8lLBfLjv9pV9xvBZK/UPKXx/0eDmvLU0kHFY8nICXW8n5oBZK/UPKX
10fEh7WHHwWSv1Dyl5jzH9YW5gLJXyj5yziVKH3LGuV/MSTNoKRxy8VkrVH+F0NiUvKX8FY6
rPXRTKuQ/JWSv17n0xrfss9NheSvlPzVkz9Z65XyVtNBxeMJSIm1x7oVkr9S8tc7R8T1Psvb
rULyV0r+CiP7GsOCYTH0QclfY1hwWFtma/okeDwBKbFW3d0vfqDFQy38ln1Y+6qskPyVkr/G
sOCw/NxA8ldK/hrJf1jrkVar6ZPg8QSkxFoz7S/u0KJTizMf9y1r5aNVSP5Kw4Laz2uyvmUL
WoVhQaVhQe2nrFULJ+Zi5yZNFDyegJRY65FvAyfmRk7MLZyYk+W/CZSBnJjbcWI+rD2CBSfm
Rk7MLZyYk7VvYvWFjHopo94cS9c3b9ngxNwqKUMdecuurgzr/IMyVFKGsGlO1j43YNPcyKa5
hU1zstZK1Be/0OKlFudDVd+y+wOb5kY2zS1smpO1zybYNDeyaW5h05ysnY9g09zIprmFTXOy
9oS3pYmCxxOQEmutajewaW5k09zCpjlZ+4oBm+ZGNs0tbJqT5UcBlIFsmlvYNCdrZ3BLEwWP
JyAllp9NUAayaW5h05ys9eCzgU1zI5vmdmyaD2t9pNHAprmRTXMLm+ZkrcexDWyaG9k0t7Bp
TtZ6SNzAprmRTXMLm+ZkeX+gDGTT3MKmOVlbJcCmuZFNcwub5mT5kQZlIJvmFjbNydpqBzbN
jWyaWwtlOKz1FK41UIZGytBcGZLlVwwoA9k0twbK0NKPsYFNcyOb5hY2zcna+Qg2zY1smlvY
NCdrTx7AprmRTXM7Ns1ny75Tg01zI5vmFjbNyfI9BGUgm+YWNs3J2kcabJob2TS3sGlO1p7M
gU1zI5vmdmyaD2tfMWDT3MimuYVNc7L2mBFsmhvZNLewaU7Wnv6BTXMjm+YWNs3J2pMgsGlu
ZNPcwqY5WesZTgOb5kY2zS1smpO1V2rBprmRTXMLm+ZkLde9BjbNjWyaW9g0J6uZoVgDm+ZG
Ns1NwnXtsJqZrzWwaW5k09zcphlYe0QONs2NbJqbvGcN37c0eyzYwKa5kU1zc5tmYDWrUtLA
prmRTXNzm2Zg+VEAZRBSBgk/xsPak1IBZRBShvBwTtZeSgIP50Yezu14OB/W8oVr4OHcyMO5
uYczsPZvAg/nRh7OLTyck7VX58HDuZGHc+t3ruGDh3MDD+dGHs4NPJxbeDgP+02gDOTh3MLD
OVn7SIOHcyMP59bDqfWw9pUPHs6NPJwbeDi38HBevykdFlp4OOcWW1ykKXjYNG/C+Ya9gU1z
I5vmFjbNydoyCzbNjWya27FpPiy/KNJEweMJSIm1l6PBprmRTXPr6a3UwqbZVkDAprmRTXML
m+Zk7SEb2DQ3smlux6b5sPagu6eJgscTkBJr31rBprmRTXPr6dHewqbZRBNsmhvZNLewaU6W
n01IfrJpbsem+bD8KAxImkFJEyYKh7VvxmDT3MimuR2b5rNlTwXAprmRTXN7YMIQNs3N/g7J
TzbNLWyak7WnTU+aKHg8ASmx9tkEm+ZGNs3t2DQf1r4Zg01zI5vmFjbNydo3fLBpbmTT3B4Y
FhybZmsNyU82ze3YNB/WHriATXMjm+YWNs3J2pMgsGluZNPcwqY5Wav+VQOb5kY2ze3YNB/W
HoaATXMjm+Z2bJoPay8MgU1zI5vmFjbNyfIjDcpANs3NbZqBtfMRbJob2TS358knb2HTbE+Y
wKa5kU1zC5vmZO3hFNg0N7JpbmHTnCy/jkEZyKa5hU1zsvw3gTKQTXMLm+Zk7YUIsGluZNPc
wqY5WasiQQOb5kY2ze0JP8bD2v2BTXMjm+YWNs3J2hMUsGluZNPcwqY5Wbs/sGluZNPcwqY5
WfvOADbNjWya23ufV9x8y574gk1zI5vm9oYZ62Htpw1g09zIprm5TTOw9uQBbJob2TS3t+bq
f9g02zUGNs2NbJrbm8ZLLWyabYoJNs2NbJpb2DQna3272cCmuZFNcwub5mT5cQNlIJvm9sZS
wmHt8QPYNDeyaW5v+jG2sGkWOwqgDGTT3MKmOVn7Dgc2zY1smpvbNANr6zzYNDeyaW5vjBkO
y4902qs0smlub9irHNa++4BNcyOb5hY2zcna90SwaW5k09zcphlY6/XDBjbNjWya2xsG7mfL
fqQCNs2NbJqb2zQDa+s82DQ3smlux6b5sPbkAWyaG9k0t2PTfFh7SQxsmhvZNLeRTq0tbJpN
tcGmuZFNcxvpvdLCprmuvz/Q4qEWOWYIm+Zu/YEykE1zC5vmZO0rBmyaG9k0t7BpTta+jkd6
r3g8ASmx9p0BbJpb2DTnlvu+ePgfTszN4xhughNzIyfmFk7MydrPWUY6LHg8ASmx1jvtbUDy
D0r+Y9N8WH74IfnJprmFTXOy9nwNbJob2TS3sGlO1pbZkQ4LHk9ASizvD5KfbJpb2DQnaw+I
waa5hU1zbrFiV3yS3vMKawsnZpsfjBfy4qW8CGO1w9p3HXBibuTE3MKJOVmeh5Df5MTcwok5
WesxoIATs5ATs4QTc7JWCn7xAy0eanEemfmWlSMCTsxCTswSTszJWkkr4MQs5MQs4cScrKXW
Ak7MQk7MEk7MyVrJJeDELOTELOHEnKx11xFwYhZyYpZwYk7WOv8CTsxCTswSTszJWncEASdm
ISdmCSfmZPmRbtBHoz5iteCw1jhOwIlZyIlZwok5WUs1BJyYhZyY5TgxH9YaYwk4MQs5MUs4
MSdrPa4RcGIWcmKWcGJOlu9hJr+QE7McJ+bDWgvYAk7McmHyL6TEWkIg1wN9PNRH3vklbJrt
4yawaRayaZawaU6Wn/9UBiGbZgmb5mQtlRCwaRayaZawaU7WeuNFwKZZyKZZwqY5WeszGwGb
ZiGbZgmb5mQtyxgBm2Yhm2YJm+Zk7aMANs1CNs0SNs3JWrNhAZtmIZtmCZvmZK2XKQRsmoVs
miVsmpO1ZngCNs1CNs1yp72KhE3zdwkL2DQL2TRL2DQna9UJErBpFrJplrBpTtZ6tCVg0yz3
WSqMLfbqJ36mLuHEvAmSuwrJT07MEk7MyVov2Qo4MQs5MUs4MSdrjU0EnJiFnJglnJiTtaUD
nJiFnJglnJiTtaYyAk7MQk7McpyYD2sLATgxCzkxSzgxJ2t9jCzgxCzkxCzhxJxb/KJ4IWle
Spq35qXjJgrrSEPykxOz3OnRLuHE3OxIQ/KTE7OEE3OyfA8h+cmJWcKJObesJ68CTsxCTswS
TszJ2ucfnJiFnJglnJiTtab6Ak7MQk7MEk7MyVpTSwEnZiEnZgkn5mRtKS9pouDxBKTEWoNX
ASdmISdmCSfmZG2ZBSdmISdmOU7Mh7UFDZyYhZyYJZyYk7XmJFLSRMHjCUiJtUb7Ak7MEk7M
ucXEC0etEmbLixA27Ovv8M9Q8ofZcrLWyuAXD2gxqMXxYvAta2YnYLYsZLYsYbacrC0EYLYs
ZLYsYbacrFVTUMBsWchsWcJsOVlbCEr6JHg8ASmx1nqMgNmykNmyhNlysrYEgtmykNmyhNly
srw/SH4yW5YwW06WX6qQ/GS2LGG2nKydQGC2LGS2LMds+bDWHETAbFnIbFlquipKmC3baAbM
loXMliXMlpO13nUVMFsWMluWMFtO1podC5gtC5ktS5gtJ2tNFAXMliXMlnPLbbuESRN+yotQ
z8M1AT9lIT9lCT/lZK2FUgE/ZSE/ZQk/5WT5bkN+k5+yhJ9ystanLwJ+ykJ+ynL8lA9rlZ4R
8FMW8lOW8FNO1r6HgJ+ykJ+yHD/ls8UvI0h+8lOW46d8WP6bIPnJT1nCTzlZexgFfspCfsoS
fsrJ2ndo8FMW8lOW46d8WN9RsPMPyV8p+asnf7L2vbBC8ldK/jBbTpanAyQ/mS3LMVs+W7bY
gNmykNmyhNlystZbWgJmy0JmyxJmy8naewhmy0Jmy9Lgzh9myzZpALNlIbNlCbPlZK2iWgJm
y0JmyxJmy8naU0swWxYyW5YwW07WviWB2bKQ2bKE2XKy1oM2AbNlIbNlCbPlZO1pBpgtC5kt
S5gtJ2s9MBQwWxYyW5YwW07WllkwWxYyW5YwW07WXrIAs2Uhs2UJs+Vk7QUIMFsWMluWMFtO
1r4lgdmykNmyhNlysvb4B8yWhcyWJcyWk7XHcWC2LGS2LGG2nCzfwzRKEDJbljBbTpafTVAG
MluWMFtO1h5OgdmykNmyHLPlw/IjDcpAZssSZsvJ2stUbUBGjfjeNLbchd3cJfyUNyHn4+Cn
LOSnLOGnnKz1voeAn7KQn7KEn3Ky9oUn6YXg8QSkxNq3PfBTFvJTlvBTTtZasxbwUxbyU5bw
U07WHp6Dn7IIJb+k07pv2eNRSS8EjycgJZb3B8lPZssSZsvJ2sIMZstCZstyzJYPa1/cYLYs
ZLYsYbacrD12l/RC8HgCUmLtaQaYLQuZLUuYLSdrr8eA2bKQ2bIcs+XD2qvBYLYsZLYsYbac
rJ2kkl4IHk9ASqx9owSzZSGzZQmz5WT5HkLyk9myHLPlw/IrH5KfzJblmC0f1nooJmC2LGS2
LGG2nKz1mEbAbFnIbFnCbDlZ3h8MC8hsWcJsOVn7ygezZSGzZQmz5WTtWxKYLQuZLUuYLSdr
PaQUMFsWMlsWN1sGlrcGZSCzZQmz5WQ1q70iYLYsZLYsbrYMrPY+K4Y+SBncbBlYy69JwGxZ
yGxZ3GwZWFvtwGxZyGxZwmw5Wev1SQGzZSGzZXGzZWDtdVcwWxYyW5YwW06W9wfKQGbLEmbL
yVqvTwqYLQuZLYubLQNrqwSYLQuZLUuYLSdrvZEgYLYsZLYsYbacLN9DUAYyW5YwW07WVm0w
WxYyW5YwW07WVlQwW5ZOytCf8wK9b9kLdB2UoZMyhBNzsrz1Cxn1UkaFS8ph+VEAZSAnZgkn
5mTt0QA4MQs5MUuHMUM4MZvagROzkBOzhBNzsrYSgROzkBOzhBNzsrw1KAM5MUs4MSdrP+8C
J2YhJ2YJJ+Zk7fEDODFLODHnltu+f8AhVJgtb8J55UXAbFnIbFnCbDlZe04IZstCZssSZsvJ
8h8KyU9myxJmy8naM1UwWxYyW5YwW07WXjkHs2Uhs2U5ZsuHtWf1YLYsZLYsYbacW/bABcyW
hcyWJcyWk7VvxmC2LGS2LGG2nKx9qYLZspDZsoTZcrL2HATMloXMluWYLR+Wn01IfjJblmO2
fFh7bvu8kDQvJc2bM+AnzdMEzJaFzJblSfM0CbPlbscNkp/MliXMlpO1FwHBbFnIbFnCbDlZ
e7XoTbsDjycgJdZ+ZgBmy0JmyxJmy8naggZmy0Jmy/KmeZqE2bJdlWC2LGS2LGG2nKw9LHzT
7sDjCUiJta8YMFsWMluWMFtO1j6bYLYsZLYsYbacrH2DAbNlIbNlCbPlZPlvSrsDjycgJdae
d4LZspDZshyz5cPatwswWxYyW5YwW07Wfn0EzJaFzJYlzJaTtYUZzJaFzJYlzJaTtR9dg9my
kNmyhNlysta3UAJmy0JmyxJmy8nai8tgtixktixhtpysfRMDs2Uhs2UJs+Vk7bUfMFsWMluW
Y7Z8WFuJwGxZyGxZwmw5WX42QRnIbFnCbDlZez0DzJaFzJYlzJaTtc8/mC0LmS3LMVs+rD3U
AbNlIbNlCbPlZG0lArNlIbNlCbPlZO01XjBbFjJbljBbTtZ60UzAbFnIbFnCbDlZe6UTzJaF
zJYlzJaTtZ/Pg9mykNmyhNlysvb6K5gtC5ktyzFbPiw/CqAMZLYsYbacrD0aALNlIbNlGTBm
OGbLt8XQR4s35WLLff/FM0fwU5bwU16nOL1OhPyUJfyUk7UXfsFPWchPWcJPOVnrbUABP2Uh
P2UJP+Vk+SmG5Cc/ZQk/5WTtR9fgpywDvU4WUmL5b4LkH5T84bacrC3+4LYs5LYs4bacrD0M
AbdlIbdlCbflZO3nj+C2LOS2LOG2nKzVXwe35U5uyz3clpO1HoZ1cFvu5Lbcw205WWv5s4Pb
cie35R5uy8laS/cd3JY7uS13d1sG1npTsoPbcie35R5uy8lag+4Obsud3JZ7uC0naz047OC2
3MltuR+35cNaQ50Obsud3Jb7cVs+LO8vk7+T23IPt+VkrUF3B7flHm7LueUv3Th6GCpvwnnn
pl9pd+DxBKTEWrrYwVC5k6FyD0PlZK3RfgdD5U6Gyv3KOUE/hsrFYuijUx9hqHxYfqmm3YHH
E5ASayVQB0PlTobKPQyVk7Xunh0MlTsZKvdjqHxY6+7ZwVC5k6FyD0PlZK3XJ/s1IGkGJY3b
HSTLj9uAxByUmKPn0Y3k//YQDJU7GSr3MFRO1holdzBU7mSo3I+h8mEt0ex32h14PAEpsfYe
gqFyJ0PlX9Di1z9dP+x///D3Hvzp9z/9y0/3jv0/v9Uff/ebn/7mH94fd/vxm/kR7x+/ur8N
5bp//n5F6T/XT8p+oz/91X/49X/61b/773/47T/+/p//+jf/46d//5uf/vNPd/y7t928Hyth
+FiF5rGz7Y7+/63Nv7ad/ZJzl+PJeB1m+WIvwTVqxBOQMuu1Co5RaKdfEU9Ayixbfrmh0M4d
5XgSKbP6au3lNGREPAEps2Tt4TgLGx5PQMosqxRwR6GdJhFPQMosEevPP5rfnEEtltQhy5Zy
7yi08+nMHeV4EimzzNTni/0VhRbxBKTMEjtPUWjHRlNRjieRMsseXNyn0M6JJyBlllk+3VFo
p514AlJmfRNci8/ChscTkDJL7JuJKLQjJ56AlFn2yOaOQjtSIp6AlFmyfl87YnxHOZ5Eyiyr
QPHFT4x5PJ6AlFl7D6PQTol4AlJmWXWI+xTauSKegJRZsv7ezwjmbqdKXyBlllXruKPQzjUi
noCUWWYMdkehnXtEPAEps/aRfs4rCnc7yhBImWUVKO4otFPeiCcgZZY9Frqj0M4tEU9AyixZ
58m/jltH3b+hS6TM2vHO+fetEU9Ayqx9HUc5jTviCUiZZQ/d7ii0c9WIJyBl1jfBtfg9vzzK
8SRSZsk3U7mj0E4pEU9AyqxviGaxK8MV8QSkzLJHaHcU2rH7ihxlCKTMWroShXaKRDwBKbPW
2YxCO/WOeAJSZondiaLQTqkRT0DKLHvEfEehHbv25ChDIGXWbh2fzvWIJyBllpnz3afQzokn
IGXWyscotGNZJ0cZAimzzDLwFlAGIWXwcjzI8tgz6o54AlJmLV2RqLVRI56AlFliHyJ4oR37
QuuWowyBlFny2NUTZTt7xBOQMssullvyu7o7yvEkUmZZmtxRaOduEU9Ayiy5rO8o23niCUiZ
ZSJ0Q6GdW1IZHCmzLE3uHl/PvBFPQMosu7zunt/N3v3C+7mX40GWvel0e6Gd9zt8d5TjSaTM
Mmm8vdDO+/aIJyBllr3ac3uhnaWCUY4nkTLLDGRvL7Tzvm/EE5Ayq60jsnPenGDuKMeTSJll
g407Cu2Y0vajDIGUWWY5e/d23gi6sxxPIGVWsztcVOFZv/UoQyBl1pcsXyzn/YW7H2UIpMyy
N+juqMJzXxFPQMqsfTZDGXrEE5AyS/bfTxWeux9lCKTM2nGMGSTiCUiZZUOHO6rwrH/1oT62
MiBrH7c3xyX9xXFJ38qArLaufFeGdTyPMgRSZtnA7D5VeErEE5Ayy94EvKMKj2laP8oQSJll
9tVf7MrwRDwBKbPsLdY7qvDYvfI5yhBImWVThDuq8JimPTlmcKTMavU7blGF5/vP/ZwxQyBl
lhmQf/F7Muo5Y4ZAyix7U/aOKjz2CP05yhBImdVW31GCq0Q8ASmzbDp1nyo8b8QTkDKr2Yf1
UYXnOvEEpMzaR8GVYe3HUYZAyix7y/s+VXhOPAEps6qN+h9QhoeUwWv1IKutYxjKUCOegJRZ
Zr1+RxWedS30yKhAyixbCri9Co89P7qjVk8iZVZdx82L8w2JeAJSZrV1RGLMUCKegJRZS+ej
Co/l0PNgRnmtHmTZ++13VOGxO+qTYwZHyqz9m0IZrognIGWWVUq+owrPyoIcMzhSZtWVzcML
510RT0DKrNX6zW/x7/coQyBlVrXxXFThsev7PcoQSJllX4zcUYXHrr33KEMgZVa19QevwmPl
Se6o1ZNImVVMH70Kz7qDR62eRMosWzK7vQqPvW93v2fMEEiZtX+TjxneO+IJSJm1rsqowmOZ
HbV6Eimz7KuUO6rwlCviCUiZZctxd1ThKSeegJRZ1dayvAqPPV+9o1ZPImVWtfG8V+FZV1LU
6kmkzKp294kqPOu3pjI4UmYVy/83lOGNeAJSZhWb476hDE/EE5Ayax/pJ+fnUasnkTLLKqLf
UYVnZcSD93Ov1YOsfRSibKdEPAEps6rlf1ThWb/vrDMEUmbtfIxv8VvEE5Aya+lKVOExTYta
PYmUWc2yOarw2Kh25JjBkTKryvq7q0+LeAJSZlUbZUYVHrvHRK2eRMqsaqsJUYXH7kRRqyeR
Mmtd+VGFx+6o44wZAimzqt0ZogpPxhOQMqva3HDEOkOLeAJSZtni8z1qrtxlrZ5Ayqylj1Gi
x0aGI4t7OlJm1b7i88nvPVIZHCmz1nU8YszwRjwBKbNqX38XaCHUYisDsKrpcZToaVfEE5Ay
q9pqW5ToWWc5ZxOOlFlrPDeiPpdEPAEps6plWpToscyOQj6JlFm2aHuPUAaJeAJSZjVb8Yz6
Pes8nTFDIGXWmicMHzPYWs04Y4ZAyqxm8/ao32N3onGUIZAya81eon7P+peOMgRSZn0H7keJ
+j1SI56AlFntsodVUdPzjngCUmbZ2SxRv6ddEU9Ayqx22b8U3+r2iCcgZZaN50rU73lKxBOQ
MsvUrkT9nl4jnoCUWbXaHkZ9rh7xBKTMMrUrUb8n4wlImWXaVaJ+j5x4AlJmmTNIifo9619q
1IcrA7DsY+US9XvqiScgZZaNg0rU72kl4glImbX7C2U48QSkzNrnP4p3vRFPQMqsfdyihMeJ
JyBllmlXifo97cQTkDLLdL5E/Z7NGdRixN0gWHVdPaEMd8QTkDKrrr31L3b6FfEEpMyyr35L
1O+REfEEpMyq6xiO80FyuY4yBFJmVcubqN/zjaLLfZQhkDJr/aao32NXa1T5SaTMqpY3Ub/H
9uM+yhBImVXvFT/n2r2PMgRSZpnLUIn6Pd8Ytdy5zuBImWWjgRL1e75ELnd+6+9ImbVyPur3
1BrxBKTMqrL+fkb65a4w0i93KEOy9nHLyl4lq/wEUmbV57HYM6pFPAEps2wlpERxn3biCUiZ
ZV96lyjus37fUYZAyqylqFHcp5x4AlJmtWLXQhT36RFPQMosW20pUdxHJOIJSJllY5Ry55ih
3DhmKF4CCFl7D6Omp0Q8ASmz2m1H+j0fC5coAZRImWXf6pco7lNKxBOQMmv3N85Iv9wDRvrF
SwAha19jrgz1iXgCUmbZSLZEcZ9y4glImWW1E0oU97GMKEcZAimzbPZSCowZCo0ZSowZkmUz
vRLFfda/elMfMZtI1u4vKnu9EU9AyiwbkZco7lNPPAEps2zVqJziPieegJRZNqcqUdzHcqgc
ZQikzLK5YSmuDKvvowyBlFn1sSPiynBJxBOQMmtdY1H5x7SyHGUIpMyypyclKv+UGvEEpMxa
95ISynBHPAEps/Zvim/5nognIGWWrbaUqPxTTjwBKbOqWH9R8+/EE5Ayq9rYt8Rs4ol4AlJm
7f7iW74n4glImbVGA1H5Zx2dVAZHyixbTy5R+ce0sqQyOFJm1W59p0NAKUcZAimzlnZF5R/r
ux5lCKTMqq1a/Jx7VE1lcKTMssotJSr/rH/1pj5cGYBVbZ5wKv9IxBOQMqve9i9F5Z874glI
mVXeFXsVzRHxBKTMquv3xWzijngCUmYtDY6yQOtfrdQHjBmcZc6EJcoCZTwBKbPWGD7KAtn9
uB5lCKTMWhpcYcxQaczgxYOQZav15ZQFOvEEpMxao/4oC2SZFsWDEimz1hjllAV6Ip6AlFm2
dlKiLJApbT3KEEiZtfIxygLVE09Ayqx9Np+cO0fxoETKrPra74viHz3iCUiZtcZzURZoc15q
8Z5RXw1lsP5CGWrEE5Aya7f2z3nWvzoe7GM82cdm2ZOmEmWB7EpqOWZwpMyylw5LlAW6r4gn
IGXWGtVEWSC757ejDIGUWet+dcoClYgnIGWWvRZXoiyQzSzbUYZAyqx1v4qyQKVFPAEps6wi
UImyQKZ8LZXBkTJr3amjLJCNj6J4UCJllr2UW6IskM3h21GGQMoscwctURbI9L+lMjhSZrX1
+2KdoUY8ASmzmmVzy0+ASxQPSqTMWmP4KAu0zkAqgyNllj1LL1EWyLKudZyft5hNJKutK9SV
wVaQ2lGGQMqsdYdr+f1/ieJBiZRZa/YSZYEsh9qDWevFg5C1j0LMJlrEE5Aya1+VURZoRDwB
KbP2NRYOASXiCUiZ1daZDWWQiCcgZZa9d1CiZpCNouUoQyBlVqsrPjWDiqQyOFJmWQmcIukQ
4PEEpMwSG5dGzaB6RTwBKbPsDbFyagb1iCcgZZa9vVVOzaAW8QSkzGp2h5NYZ2gRT0DKLLH1
gKgZZKtJcpQhkDLLfk6JmkHriKQyOFJm2Rt7JWoG9RLxBKTMEst5iSLCEvEEpMzaxy0+AR4R
T0DKrPbaHkZxgDviCUiZ1Ya1jnWGEvEEpMyyxCoSY4Y34glImSWWwVEzaF17RxkCKbP2b3py
DUAeXAPwykLIajaKOjWDnognIGWWvY5coGZQkRwzOFJmid2Do2aQabMMHIV7ZSFkeZyjcBk4
CvfKQsiyt7dK1AyyNcCeswlHyqzvB1r8nKPbczbhSJklpitRM8jurlFZKJEya7d2ZbBxcD/K
EEiZZW+bFq8ZNNbeHmUIpMxa11iP2USNeAJSZtnryCVqBlk2R2WhRMqspXY9lOGNeAJSZlnR
tRI1g0xves4mHCmz9nGLIqM14glImWUvF5cenwj2iCcgZdbSlagZtH5fjhkcKbPEFOPUDGoR
T0DKLCvTVqJmkJx4AlJmia0zRc0guSOegJRZ9hFBiZpBtrrTjzIEUmbZTaFEzaC1H0cZAimz
9pGOIqNXxBOQMss+OyhRM8jmcFFZKJEyaylR1Awy/e9HGQIps/YVE8pQIp6AlFn2bnWJmkF2
dJ6jDIGUWe29Lc65c1QWSqTM+nb3i6M4wBXxBKTMsnerS9QMkifiCUiZte5wT8wmesQTkDJr
XWOnoFCLeAJSZq2zGQWFTJufivNzLzuELLH7ShQUsrvEU3F+7mWHkGXfBZRTUKhHPAEps+y2
Xk5BoRbxBKTMsrf8yykoJBFPQMosWdeC5Ej/ERzpe9khZC21OwWFTjwBKbP22ew5P4+yQ4mU
WTYQKFFQqPSIJyBl1j5urgx2r3yOMgRSZsk6hk+qz/Og+njZIWSJjVeeUAaJeAJSZonNZKKg
0LrejjIEUmaJzQCerCZWnqMMgZRZYuOuU1BoRDwBKbOWPr4xmxgRT0DKLJuAlSgoVFvEE5Ay
a404oqCQXRfvUYZAyiybhpQoKGTZ/N64BuBlh5Altg7/xgpkj3gCUmbZZLVEQaEiEU9Ayiz7
TqNEQSEbfbxHGQIps5bOR0Ehy//3KEMgZdYao7xRgbRHPAEps9YVcwoKXRFPQMqsNQuLgkL3
iScgZZbYzDsKCq1/VagPVwZg2dSzREEhm5G9qQyOlFlr/BAFhWy++x5lCKTMaq/1F2UF7ogn
IGWWTdlKFBSyjHhTGRwps8RWVaOg0DrLOZtwpMyyb1pKFBRav+8979A7UmbJyptQhhNPQMos
+2ytREGhdWaPMgRSZi0lioJC14knIGXWGmuNLCtQouxQImXWuvtEQaFy4glImWXfPpcoKGR6
M44yBFJm2Sd+JQoK2d6OXGdwpMyS9S9FqbETT0DKrDX2jYJCGU9AyiyxZyFRUMjuMSPHDI6U
WeueeAoKPRFPQMosW2gpUVBo7W3F9XYvO4QsW/gqUVDIxivjKEMgZdbSrpEFRwqUHXKkzLJF
qTJgzDBozOA1iZAl9hwvqg3ZNR01iRIps9bIKaoNWZ6OjlnrNYmQJabgUW2ojIgnIGWWLWmU
qDa0rqRcZ3CkzBIbyUa1IRvhRk2iRMos+4CyRLWhxTnKEEiZJTbri2pDrUU8ASmzdj5mtaEy
cp3BkTJrrZ2cakNPxBOQMsuusRrVhr6+63XBGkD1mkTIstlLjWpD31GvVyqDI2WW3a9qVBuq
NeIJSJkl61+6/T39EfEEpMwyXalRbUhOPAEps2wxp16pDPVCZahekwhZ0p8vjiKEJ56AlFm2
VFZPtaETT0DKLPuovEa1oVsinoCUWbL+JVeGu0Y8ASmzZJ3ZqFreI56AlFm2oFqvGDOMiCcg
ZZatqtZTiqhHPAEps+y7/RqliGqJeAJSZtnHvzVKETWJeAJSZlkG1yvWGU48ASmz+rViv59L
xBOQMquvKz9KET0RT0DKLHns90UpojfiCUiZtY9CzCZOPAEps+wT8XplHbJ6pTI4Umb1T7Vr
lCJqJeIJSJlli2s1ShHVEvEEpMyyT6vrHbOJEfEEpMyyheF6ex0yuSKegJRZMr6r8i5nDcDj
CUiZtVtHHbITT0DKLHm+83/Xswbg8QSkzLJP3b/YM+qOeAJSZtlH5V88cq9yzOBImWVLsPWO
2cSJJyBl1m4ds4kn4glImdVNlW4vUrb2XCr+DvHqF8mygghf7Mpw4glImWVj33rnOoPHE5Ay
yyqsfPF7MurOMYMjZdbKrvs5T+I8noCUWTbz/uLn3DnvowyBlFny2h5mkTKPJyBllj3U+OJT
KcTjCUiZZQ+Z6j3OKNzjCUiZtfTxDmXoEU9Ayqz+zdtqicLFJeIJSJm19rBEkbI74glImbWu
/OIlx7pEPAEps9aRLqEMI+IJSJllo7NaXBmeE09AyixbNfpiHzO8EU9AyqylEqX4yt2JJyBl
1o5dGXqPeAJSZi3tKq4M6+gcZQikzFoZXFwZbLxSjjIEUmb1y1o3f0//xBOQMmvlfHFl6Cee
gJRZ6+5TXBlMm8tRhkDKrDVyKjFmOPEEpMza579n1u54AlJm9cuunihfKBFPQMosWVdPzCbu
iCcgZda+jmM2USKegJRZso7he96U9XgCUmZZWZlaQhlOPAEps2RlMChDIWUoPmYA1jrSNcYM
d8QTkDJrHelvCPgjRhk7noCUWbaiU+t9vonzeAJSZtlD2C+WcyXWowyBlFlr5FRjzFAjnoCU
WVaz6IvPUzKPJyBlltU/q9WVwdS8HmUIpMxad7gaY4Ya8QSkzFo6X6N2aYl4AlJm7SMdzyZG
xBOQMku+S7jWUIYa8QSkzNp76MrQrognIGXW3sNQhhLxBKTMkteuN1cGOfEEpMyS265KVwa7
H9ejDIGUWVbgqNbnzM89noCUWbaqWutz1gA8noCUWXsPQxlaxBOQMmsft/c87fN4AlJm2bsN
3+nPNYA6cA2gDn/alyx7rvrFfj8/8QSkzLLVyNpCGU48ASmzrF5jba4MdudrRxkCKbPWvK25
MthvbUcZAimz1nFrMWY48QSkzFra1UIZrognIGXWul81VwabDbSjDIGUWfZaQ23lfF3j8QSk
zLK6erWFMpx4AlJmrRlrc2UoJeIJSJm15gmt1TyDreIZbKfOXbDW3LC1886dxxOQMmvHMZvo
EU9Ayqx9FFwZbLzSjjIEUmbt1r3kL+8Ff3kv2cdmWVGr2kIZasQTkDLL6gPW9uT8vD04P28x
ZkjWGmu1WGd4Ip6AlFndFMMe2q9r94l4AlJm9WJ7+2bWtheztm1lQFY3HWuuDOsKPcoQSJkl
r12hrgz9xBOQMmtdMbZEHHecHU9Ayqx135VQhhNPQMosez5cJcYMJ56AlFlLtcWVoZ14AlJm
rbVFGwxFfux4AlJm2WtYVWDMIDRmkK0MyFrnX1wZTJvlKEMgZdYaM4org41X5ShDIGXWynkT
4nV0R8QTkDJrjfqlnbd3PJ6AlFlLUSWU4Yl4AlJmybC9lfNtn8cTkDLLXierVpz1HCvBkb4h
Zdbew17ynB9lCKTM6uuIuDLYaoIcZQikzFrjIIkxwx3xBKTMWivQtnR09urpuFdPP+vUztpH
wZVhcY4yBFJm7SvGlcHmKHKUIZAya5//GDNIxBOQMmtfY0OghVALyStxs6woYu2uDHZH7UcZ
Aimz7LW42l0ZnjviCUiZtUYDPcYMEvEEpMyyFzRrjzHDiScgZda6t/f7PO3zeAJSZq0VhF7O
1zUeT0DKrPXUoYcyXBFPQMosWUchnk30iCcgZdbew5r3817xft5rzs+dtWYvveWafj/KEEiZ
tVaNekv16Q3Vp/uYAVjruVEPZZCIJyBllr3M+sVPnsGjDIGUWfaKbe2hDBLxBKTMWuOH3k89
AI8nIGXWWg/orgx2D+5HGQIps9adoT89f8dRhkDKLHktBmXopAzdlQFYa3zdXRnWMTzKEEiZ
ZfV+a491hhrxBKTMWuPS7spQTzwBKbPsCX99rvNmjccTkDJrtX5inWFEPAEps6wscn3S9MDj
CUiZZeWEvzjvtTuegJRZax793KcujscTkDJrzSweV4aMJyBl1lKJJ1YgTzwBKbOs1G99as3f
USv+jupz52SZpHyxZ61EPAEps9bY94nZRI14AlJmrVx52nkPwOMJSJm1Vm4fOVW5PJ6AlFmy
fp8rg91XnqMMgZRZdhupDyjDQ8rwhDIka41LH1eGtedHGQIps9bK7fOcL188noCUWbu/p0OL
Ti167tWTa/qPK4ONiZ6jDIGUWTJei8/bOx5PQMqsdW9/3KHCMvs5DhWBlFn2fuoX+7f6LeIJ
SJm1np68oQwj4glImbXuV68rw33iCUiZta781x0qbPT5HoeKQMqs9QTzdWWw4/keZQikzFqj
zPc+79x5PAEps6y8c31jzPBGPAEpszz2VbU34glImbVG5G897/V5PAEps9Z68htjhhLxBKTM
2ufGlcGut/coQyBl1pqFveFQ0SOegJRZ68p/JbP2FczaVzJrnbVWh1/J1cH3KEMgZdbuL9YZ
rognIGXWUu3XHSruE09AyqyVXe9zKmx4PAEps/a5idnEiScgZdZSu9eVwcZE71GGQMqsfTbD
oeKJeAJSZi2df0MZ7ognIGXWGl+/41TY8HgCUmatNy5GKMMd8QSkzFpKNK5TlcvjCUiZZe9D
1uHKcJ94AlJmrWee4873AMZRhkDKrHWNDVcGuy7GUYZAyqw10xuuDHZdjKMMgZRZ62nvcGWw
lbdxlCGQMmutz4xQBol4AlJmrZn3cGWwFaRxlCGQMquv3xeziRNPQMqsdR2PUIYTT0DKrDVj
Ha4MplDjKEMgZVZfZxbWGQatM4yYTSRr76Ergz03HEcZAimz1sx79Mza0TFrR8/5ubP2HsaY
oUQ8ASmz1ohjPKfKpscTkDJrzbxHjBlGxBOQMmvdqYcrwzqzRxkCKbPWPGHsnLeXmT2egJRZ
9vXIF0se3RwzOFJmyXfI2nV5H2/EE5Ayy56+f7G/jXviCUiZZfO2Lz7K4PEEpMyyeUK7XBmu
E09AyqzdnyvDdeIJSJlls/t2uXfNXSOegJRZdv6/2NfbJeIJSJllz6Db5cpwt4gnIGWW3Uu+
+M3zEcpwkDLLVLtd7l1z3xFPQMqs3dqVYXMeavFkH64M6zzJqeLh8QSkzLJ3mNolT57zowyB
lFk2e2lXP+/ceTwBKbPsDcov7nkGc8zgSJllKtGuUIYn4glImWXLJl/s6wwj4glImdVX3+9Z
VfN4AlJm2cz7i8/XNR5PQMqsfR3HmOHEE5Ayy3TliyXP+VGGQMosW3z+4vONu8cTkDLLFobb
fZ1RuMcTkDLLlqu/eJzzcR9lCKTMWtfYfZ8nih5PQMosu+9+8Vm583gCUmb19S+5MizOUYZA
yiwbz33xe47uncrgSJllI9l2hzJcEU9AyqylwXc983OPJyBllq1rtDtcre6IJyBlli27f7Fn
7RvxBKTMsjfw2+3KcJ14AlJm2TctX3zeofd4AlJm2SOKdvcz0vd4AlJm7T2MMcOIeAJSZsm6
3h7o46E+fDYBrH3cYp2hRjwBKbNsxtru97xD7/EEpMxa+ni7MtQTT0DKLJurtzuUoUc8ASmz
lq7cuQLp8QSkzFq6cocT5oknIGWWraq2EspQI56AlFlWFeGLxzkfJdcZHCmz1hVTYswgEU9A
yix70vTF50mcxxOQMstqsrRS8n5eCt7PSznuXMFaaldcGdZ+HGUIpMyyLwlaCWU48QSkzLIZ
0hc/J89LKoMjZdYaa5V2ntF7PAEps9ZdtLRUn9JQfUo4YSZrt44VyCviCUiZta7jsnPeTBI8
noCUWbY63Iorw3XiCUiZtcZzJZwwS8QTkDKrrfPv7rejRTwBKbP2NRauVhLxBKTMstpLrbw+
Cr8inoCUWevOUGKdoUY8ASmzzLGyFVcGU/NylCGQMsu+lfri9sPnHx5PQMose8T9xT4KHxFP
QMqsdR3X63wl5PEEpMyy77G+eJwzWI8yBFJm2csWrYar1YknIGWWfeG4SkPHKLzeOAqvrgzA
MkvTVmE2UWk2UbcyIMtenfhiHzOMiCcgZZZ9+dRqPfNzjycgZZZ9777KPK4+SsQTkDLL3vFr
NcYMEvEEpMyybztXQfdzBlMZHCmzZB11OU/iPJ6AlFm7tZw1AI8nIGXWPgr9vPHr8QSkzDLf
33Z8sa+IJyBlln1x2mo4YY6IJyBllr0V2MI9e+3tUYZAyqw1qjnu2XfEE5Ayy2r9tHDPtjFq
umcHUmatDK5vjsLri6Pw6k6YwFoj8nDPrieegJRZS4nCPbuceAJSZq0RR7hn2zlL9+xAyqx1
FFo4YbaIJyBl1lK7cM+2/Uj37EDKrHUvCfdsO8vpnh1ImWXfV7dwz7Y8TffsQMose0Xqiz2j
esQTkDLLqri0cM+285Tu2YGUWStXwj179X2UIZAyax+3UIYW8QSkzLL1/WU6EnnejkNFIGXW
Gg2Ee/Y6y4JZe9yzk2Vv7LXjni0RT0DKrH7bHroy2BWa7tmBlFl9HRFXBhvPp3t2IGVWX8fN
lUF6xBOQMquv8/RI7tVRhkDKLFsjbeGevf6lVAZHyiyPJc9HKoMjZdY+m6EMV8QTkDJLVqa5
Mny3LY8nIGXWzi5QhkbKEO7ZwFrz6HDPLieegJRZ9r17C/fscuIJSJm1RpnHPfuJeAJSZnmc
9/N0zw6kzFraFe7Za8+PMgRSZtlz7hbu2XYG0j07kDJrnc3jnt0jnoCUWfakqYV7tl1J6Z4d
SJkldvWEe7bdUdM9O5Ayax+FUIYa8QSkzLJvWlq4Z18nnoCUWeteEu7ZNn5M9+xAyqy1ShHu
2bZqnO7ZgZRZdupbuGfbymS6ZwdSZtn3DU3C765GPAEps6yiYHNf7Pc58QSkzFrZJTGbeCKe
gJRZduqb+2LbY8l23LMPUmatu4/7Yltplnbcsw9SZq3xw3HPPvEEpMxa6/vhnl1OPAEps9bZ
PO7ZPeIJSJllJVmb+2JbUZp23LMPUmatuUi4Z9tvTffsQMqstUbaQxkk4glImWU17xq4Zzdy
z27hng0sqwfRwj3bZjLpnh1ImWW1floPj9wr4glImbXmbeCe3cg9u/UYMyTL3jxs4Z69fmt6
1zhSZq0MDvfs+8QTkDLLLq8W7tk2qk337EDKLKuw0o579oh4AlJmWZ2q79Z+5XWVTpiOlFlr
NtnT1ap1dLVq7p6NrDXTC/fs1XfOJhwps/a5iXWGK+IJSJm15p89vGtqxBOQMmutOYR7tt2P
0z07kDJrqV24Z68syDGDI2VWs/Hccc+WiCcgZZZ91PHFbx6rdKhwpMyyCl3tuGc/EU9Ayiz7
DKQ9MJt4aDYR7tnAWr8p3LNtvJLu2YGUWUu1n/CueSKegJRZ5gLfjnv2FfEEpMxa5z/cs9sV
8QSkzFrzzwfGDA+NGdw9G1lWYr0d9+wr4glImWWVlFq4Z5sqpXt2IGXWmquHe7bdidI9O5Ay
y+ovt+Oe/UY8ASmz1j3xuGe/EU9Ayqx9FFwZ7hNPQMqslcHui73PQMc1gCfGDMla+viEE2aN
eAJSZtnXoC3cs+uIeAJSZtknTC3cs1uNeAJSZjW724V79rq+0+/OkTLLJhUt3LPXbz3KEEiZ
te5X4Z5tqxfpnh1ImWW1FNsTTpgl4glImbVyPtyzbT/SPTuQMmu1Dvdsm9Wke3YgZdYaP4R7
tu1HumcHUmbZR0/tDWV4I56AlFlrBeENj1yJeAJSZi0lcl/s9fziuGcfpMxaKwhvKMMV8QSk
zFrXWLhn1xHxBKTMssF4C/dsmzOke3YgZdaa6YV7tq2qp3t2IGVWX2cz1hneiCcgZdbew3TC
bMc9+yBl1nqaFe7ZckU8ASmz1hsX7ou97nzHPfsgZdZ63vLGmOGKeAJSZtl0qr3hXTMinoCU
WfbdTAv37HriCUiZZW8kNffFXvfK4559kDJrPQtxX2x7T7Id9+yDlFlLg90Xez2HOe7ZBymz
1pr1cc9+I56AlFlrZnHcs088ASmz1vsTIz1y23HPPkiZta7jkd41baB3TXP3bGSt1ZYBY4ZB
YwZ3z0bWmkeHe/ba26MMgZRZ6wlmuGeXK+IJSJm15obDHSrs+h7HoSKQMstqVbdwz7Y7Rrpn
B1Jm7aMQyvBEPAEps2z5p4V7to0+0z07kDLLlrHWLq8rsUY8ASmz1gjwuGe3iCcgZda+Ynq+
B5Du2YGUWWs9INyzrzviCUiZZQYP67OxUOrRceVudH9PP1nrzapwz177kcrgSJm1cj7cs8uJ
JyBl1nqWHu7Z5cQTkDJrzSZH+N21iCcgZdZSiXDPtmxO9+xAyqz19D3cs1dm52zCkTLLlrEk
3LOvE09AyixbW/zi8yTO4wlImWXzTwn37C/rJN2zAymz7DdJuGd//5F0zw6kzLJ7ooR7dh0R
T0DKLMsuCffseuIJSJllOS/hnn1LxBOQMstGshLu2eWJeAJSZtlbNhLu2fXEE5Ayy1amJNyz
1xnIdQZHyix7n0XCPbtdEU9Ayiwbz8lxz+4RT0DKLBs/SLhn1xNPQMqsff5dGUqPeAJSZsk6
T33k7+gDf4crA7BsSVzCPXsd9aMMgZRZ9pRUrhwzyIVjBnH3bGTZ3UfCPbvUiCcgZZZ92SHh
nr2ui1QGR8osuydKuGeXFvEEpMyS/ffzXp+ke3YgZZatM0m4Z7c34glImWWjZQn37O8/ku7Z
gZRZ62yGe7YdnXTPDqTMspVCCffsb7Yk6Z4dSJkl6++xAjkinoCUWbu/9K6RdM8OpMyyUaaE
e/Z3OUu6ZwdSZtnYV8I9u9eIJyBl1tKVcM+WGvEEpMxa11i4Z2+OUIvzzl2w7FmIhHv22vOj
DIGUWVYHVMI92zQ/3bMDKbN6tXPjytCeiCcgZZZ93yDhnt1OPAEps2zxWY579h3xBKTMWmoX
7tmmHumeHUiZZZ/sS7hnW6ale3YgZdY+bu/5WlbSPTuQMqt321tXhnUGjjIEUmbtfHRlaCee
gJRZ9m2OhHv22vNcZ3CkzOp2Rw33bLs/pnt2IGWWzT8l3LNlRDwBKbOsWIGEe7aUiCcgZZbV
H5Bwz24l4glImWVfMn9ZfL588XgCUmbt31TOM3pJ9+xAyiwznpLjnt0inoCUWfYEU8I921Qw
3bMDKbPsEcWn3Ge93eMJSJnV1zF0ZbBMS/fsQMqsvn5fOGHeEU9Ayqzd2pVh9X2UIZAyax9p
d6iw3CzHoSKQMmu37uftHUn37EDKLDPQknDPNvVI9+xAyiz7IkLCPbuXiCcgZdbKlRIeuVfE
E5Aya5//UIYW8QSkzLJqNBLu2aab6Z4dSJllj6Uk3LPXfqQyOFJmdVl/f/NqT2VwpMyyCity
3LNLxBOQMsvqc0i4Z9s1ne7ZgZRZSx/DPdvGR+meHUiZZV8AS7hn31fEE5Aya421wj3bjki6
ZwdSZll9Dgn3bLvbpXt2IGVWtxFHuGcvTjphOlJm2fdYEu7ZNp5P9+xAyix7mCzhnl3eiCcg
ZZY9hJVwz16/Nf3uHCmzrGaqHPdsiXgCUmZ5fOr7SLpnB1Jm9XWeJO+14J7tSJllz6DluGeX
iCcgZZatUki4Z7cTT0DKLFtBkHDPtlFbumcHUmbZSwpy3LNrxBOQMmuNzsI9O+MJSJllrwNI
uGfb3TXdswMps9Y8+rhnPxFPQMqs3V+4WrWIJyBl1lK7cM82dU337EDKLHtDTBqMGRqNGdw9
G1lrPBfu2e3EE5Ayy17PkHDPljfiCUiZZS+/SLhn1xNPQMqsNYYP9+zV91GGQMqsNSsO92wb
z6d7diBl1lpBCPfs68QTkDLLnoVIuGfbFZru2YGUWXsPXRlMm9M9O5Ayy9asJdyzbYUk3bMD
KbPE8j/cs/ffYb1d3D0bWbb2LuGe3U48ASmzZP295/w83bMDKbPsHVgJ9+x1DI8yBFJm7SMd
3jUt4glImWVv8ki4Z6+zfJQhkDJrKdFxzz7xBKTMknW9hUeuRDwBKbPsvWdp6Xfn8YQtpjry
40+/OwtnLSzt6o7/ySe+YZBtBzkNsgMps+yjBwmD7KtH/P9S9ja71iM7cva8rqKG9qDbykyl
ljQ1YBie2d11A4bRadg40YDP1/ePT2QyKAbgifsAXYz9PntrLf1QzJQyuIqCUn4azWhC0TJe
RUEpWxoz2SDbbodfg2wqKGWPnyYbZFvZ8zXIpoJS9qrgZIPsnvEqCkrZY7Q52Z5mMF5FQSkv
Ktgg2z/H17gqFJQy486ZDbJPxqsoKGWehJMNsu20/RpkU0EpT/7z/CbO5lknziabXX6UPUya
bJBtBcbXIJsKSnmazQbZGa+ioJSZiU02yLZbx9cgmwpKeeqYbGl3Ml5FQSmfnGWDbLuBfg2y
qaDU9D3ClnaT8SoKStljgpkNsi/Gqygo5RNDbJBtE5xfg2wqKLXPyieNt+bXIJsKStmS3ckG
2UfGqygo5aUnG2TbFfE1yKaCUl7eskH2kfEqCkr5sYnW1/YEdWaD7FRQyl7Ln2yQ7X81MwMV
lPIzP1pfm1PNzAbZqaCUP1KJ1tf3bzJeRUEpfxQRra9v3yPMDKmg1PRtj++W/TXIpoJS+7fP
2EZnvIqCUn782SDbcszXIJsKSvm0NBtk++f42tOEglJ+Z4jW1/YS6MwG2amglD9+YoNsyx5f
g2wqKLWPP6cSbsarKChlL/JPNsj2T56ZgQpK2ePAyQbZls2/BtlUUMoe1U02yLZM+zXIpoJS
9pL9ZINsu3d9DbKpoJRPZLNBtv/Vrz1NKCjlRQUbZPve+RpXhYJS/mCBDbKtSvgaZFNBKbut
TzbItiz4NcimglJerLJB9hevoqCUlzpskO1/9WtcFQpKRfw9bPsaZFNBKXOinmyQbXXF1yCb
CkrN/fNZfmPKb0Qx/1F+v2KDbLvnfw2yqaCUP+5gg+zfwXgVBaXMtXuyQbb//JtKCAWlzsd/
HkPwwXgVBaXsJeKZDbIb41UUlLLCbLJBtmWMr0E2FZSyVz0mG2RbVvoaZFNBqb2967uffw2y
qaCUD83YIHtcjFdRUMozUTbIPhivoqDU9CPLBtkZr6KglFdOv/sbHv/uOjz+RROKQtlS8Pn7
WtrNX21pN6NBdqU8B7NBtg1WvgbZVFDKlhdMNsi2wePXIJsKStnL6fNmE4rJeBUFpTx3sUG2
3bu+BtlUUMrGPzMbZD+MV1FQyl69mWyQbWfr1yCbCkrZyO/Nw1Hpn4xXUVDqtIcXbJBtZ9LX
IJsKStkL15MNsu0ofw2yqaDUaXcGNsi2u9LXIJsKStkrRG/8XbX3qFftPbJFLakds6VdY7yK
glKnXc1skG33mK9BNhWUsrWekw2y7cHS1yCbCkrZa/mTDbJbZ7yKglI2rp5skG1T1F+DbCoo
ZT01Jhtk24Tz1yCbCkrZC/CTDbLtLvE1yKaCUufl8Z33wa9BNhWUsnH8zAbZD+NVFJTyewkb
ZFuG+hpkU0Epe113skH2yHgVBaVssDrZINvGJV+DbCoo5RND2SD7ZryKglJmeT3ZINvqo69B
NhWU2r8dmcH2+tcgmwpK+eMONsi2uYGvQTYVlPJH2WyQbcfpa5BNBaUi/h7Dfw2yqaCULSSe
bJA9M15FQSmfls4G2SfjVRSUsmHhZINs3ztfZggFpXw69yk1wyM1QzTIrpS9lDezQXZjvIqC
UmYUOUuD7CkNsmc0yK6UT2qyQbafF1/jqlBQav82G1fdjFdRUMon5Nkg2x7bfQ2yqaCU9SWY
bJB9ZbyKglI+o8MG2TZd+TXIpoJSXmWyQbZ/169mCAWl/Jpng2y7Y3wNsqmg1PSzMjKD1Stf
g2wqKOW1Fhtk2/jqa5BNBaXs9beLDbLfz3F9DbKpoJRVNRcbZO+fl4dtVzTIrpRNXV5skP3u
9etrkE0FpezefkXra3sYcGWD7FRQ6vxdbxyZ4R0uXF+DbCooZUvHLjbI7pPxKgpK2VjkygbZ
Ga+ioNT0bbMJxcN4FQWlztv223i+TzWe+qlYM3zUPjbMDCfjVRSUsrneiw2yz4xXUVDKXhW8
jq+lXcSrKChlc3IXG2TPh/EqCkpNP9++0cR11NHExQbZhbL+PFc2yO6MV1FQavo+ZOOqwXgV
BaVspvBig+x5MF5FQSl73HFlg+yMV1FQyu7tFxtk+6f9MkMoKGU1/HVEE4p+MV5FQSl7InCx
Qbbvz8wMVFDKzzE2yLZP/jXIpoJSVvte2SD7YryKglLWT+xq0YTC9kjLJhRUUMq6nF1skN1/
jP/ff+Of/zj+tP/903+O4O//84//80fbcfznf+DP//jXH//hn+4/2/nnX+sF25//0N5/6G3+
4/uNxvmP9zvS+Qt//Lv/8s//9R/++vt//9f/73/927//63//8Z/++uO/Od7s7/bjN//8mcnj
z41891Oh/c/v9v9v//zPf0xrNd+2J9E0y9UWnkT39f7eoMPpZLyKglJWQrVwG7rfBNrSkygV
lLKmqi3chmyGp6UnUSoINezW2sJt6PK/SueRVBBqXP6dwofMPzndylJBKG/n1Og29O6rlp5E
qSCUN5lqdBuaN+NVFIQa1lGuhduQzRa39CRKBaGGvfPxxvHmw2S8ioJQ3tSo0W3oLaFbehKl
glDDbAYa3YZ+Ga+iIJS3QWrn51DY0pMoFYQa+9P2nCyNeBUFobwZUKPb0O9hvIqCUN4MqNFt
6LoZr6Ig1LBnLo1uQ2MwXkVBqGHTxG8c25iMV1EQap8x4Ta0PznXCqaCUPHbsT74PhmvoiDU
sKdmLdyGbPKppSdRKgg17ObYwm3IHiy09CRKBaGGORq1cBuyxwQtPYlSQahhb2S2cBvaR4CZ
IRWEGtfPPmF4ijwP41UUhPK2O+1kJ4Qf41UUhPJ2To1uQ+eP8SoKQg17HtLOz20o4lUUhBo2
Y9/Oz4espSdRKgg1bDa90W3oyXgVBaGGmTg0ug09Ga+iINS+5uk29A5vWnoSpYJQb368Ld4D
n+NkvIqCUMOe0rRwG7KndC09iVJBqGE2HC3chjzfpCdRKgg1bEF/S7ehH+NVFISK7TEzHIxX
URDKG1k1ug3Nh/EqCkKNy7Ir3Yb8r3JFUCoINfxuR7ehORivoiDUuz37hPO7atOTKBWE2ucx
3YbOm/EqCkK9sW0v1vpsZspv7Kv2o7x5WZvMDAfjVRSE8qZfjW5DfpwyM1BBqGG2D41uQ3b9
pydRKgj17gWP4/FDxqsoCPV+Qvt+d65ZaulJlApCDbPhaHQbOi7GqygI9X5C/3lMZE7GqygI
NcxgoaXb0GC8ioJQw57rNLoN2XWTnkSpINQ+K8NtyF6maulJlApCDXui1cJtyNJkS0+iVBAq
YnqK/BivoiCUtyJr4TZkRXdLT6JUEGqYkUoLt6Hzi1dREMpbw7VwG7LCo6UnUSoINexpUwu3
IZuIaOlJlApCvZ/Qfx6DkpvxKgpC7TMm3IZskrmlJ1EqCOVN8RrdhmbGqygINey5Trt2ZthH
mZkhFYR6a3GPY7riYryKglDDrD4a3YacycxABaG8TVhLt6GD8SoKQsWx2Zlh709mhlQQalx+
rYSniF8RzAypINS+Huk29O7wlp5EqSDUW3HYtsNtyO5j6UmUCkINe377xnsbVq9cmRmoIJQ3
3mt0G7L9mZ5EqSDU+wlPi/dV+w4XWnoSpYJQ77F5jybdhsbNeBUFod49bduLzGDH6ZeZgQpC
vduzbe/MYC/jtvQkSgWh9v0q3IZsENPSkygVhHr39Lvf6DZk98fflxlCQahhz1Yb3YbsyKYn
USoI9ca27cgMvncyM1BBqDdL2F/amWHsn8dVmwpCxfZ2Zhg2GkhPolQQatjzwhZuQ/ZydEtP
olQQaty+D8OHzKrB9CRKBaGGbaqF25BNC7T0JEoFoeJo7swwfH8yM6SCUN5ssdFt6BiMV1EQ
6t0LttfDbejIeBUFod5sZ7+9M4O9Qt/SkygVhHqvR9tvOzPs78rMkApC7Zox3IbMOrqlJ1Eq
CPXWvnat7LU+o0/GqygIte8M4TbkfzU9iVJBqGGJroXb0LA7anoSpYJQEe/MYItSWnoSpYJQ
e7wTbkPDRkvpSZQKQu3RZLgNdcub6UmUCkINS78t3IZGy3gVBaGGncIt3Ib2d2VmSAWhhl0m
LdyG/GxNT6JUEOq9X9le2JnBFr609CRKBaF2lgi3IZuaa+lJlApCeRPPFm5DY2S8ioJQwy7F
Fm5Dw0YZ6UmUCkLt6zHchkbPeBUFoWJPXzHv92O8ioJQ+84QbkP9yXgVBaG8RWoLt6F9BLgi
KBWEGnZhtXAbMov4lp5EqSDUsPeYWrgN7b2TmYEKQu2KPNyGho1k0pMoFYQa9i5IC7ehfZ0+
ctX6iqBKDXsjooXbkOeb9CRKBaHem8T72+E2dNoYJT2JUkGoYe+0tHAbGjbST0+iVBBq2MXb
wm1o2B5JT6JUEGrXc+E2NOz7pSdRKgj1bu/9TuE25FdEehKlglDe3reF29CwO0Z6EqWCUPGd
IjPYmPHJzEAFocZt51i4DdlEdEtPolQQypuqtnAb8ryZnkSpIJS3k20PM8NkvIqCUMNSSnsi
M8yMV1EQytvJtnAbGlfGqygI9W7P9mFkBrsHpydRKggV+401w8N4FQWh3u3ZXghXY7t3PcwM
qSDU8OcU4TY07h/jVRSEGvf++a4ZzoxXURAq4jtfmGrpSZQKQg17cfyNv9HEI6OJZ2eGQnkb
1hZuQ6fNTKcnUSoINczFrIXbkI9q0pMoFYQa9j5WD7ehd4cyXkVBqPeMuS2OSv9gvIqCUN48
uYfbkB3lnp5EqSCUZ7sebkPn0RivoiDUsPKkh9vQ+cWrKAj1ZqJu8Y85sacnUSoI5aP7Hm5D
YzyMV1EQyltT93AbGjPjVRSE8jbe/WDNcDFeRUGoYW+c9nAbslYpPT2JUkEovyf2cBuyBdI9
PYlSQSi/M/RwGxp+ZDMzUEEobxXew21of47MDFQQKo7mlxn6UTNDPyIzfJRniR5uQ3t/Xk/d
u9fDXBL/Mm4/spEZrpvxKgpC+ciih9uQ5f+enkSpINSw90d7uA0NPxeyZqCCUD4W6eE2NM6T
8SoKQg0rgXq4DQ3/edYMVBBq3H7dRM0wbsarKAi1r/lwG3qHyIxXURDK7+093Ib8u6YnUSoI
9R5N++3IDO/J2dOTKBWE2udYuA2NdjFeRUEov1/1cBuytks9PYlSQSi/i/ZwG7IqoacnUSoI
Nez90d5KZmiSGbYnUaV2fmzMDIPxKgpCDSswe2NmGIxXURBqWBHbw23oPUUZr6Ig1LCiqYfb
kM2Q9PQkSgWhhi0q7eE2ZIvJe3oSpYJQw16M7eE25Jk2PYlSQajx+BmzFwKddt2kJ1EqCDWs
oOnhNnT6kWVmSAWh4oyJzGBXc3oSpYJQ3la9N84zXIxXURDKm733cBs6/dPeOXMXCkK9V5ft
hcgMT8arKAj1fkKLn/F9qmfUTxWZ4aP2PTHchva5l5mBCkK923v/UrgNWYXb05MoFYQa9t5+
D7chs2fo6UmUCkK9v/2ePZ01Q2O8ioJQ+wruHE1cjFdREMpr394jM/jnyMxABaH2Xgi3IavU
e3oSpYJQOweH25DNJvX0JEoFoXwWr3dmhpvxKgpC7ftVZ2ZojFdREGrYNFbvzAyD8SoKQu37
VbgN+bmXnkSpIFQcm8gMlivTkygVhBo20fLutiPvOP0bTYSCUO8ZY9u7zu+bX2f95jszFOr9
hP7zfT+/TsarKAj1/vabH8NtaPinzcxABaGGTdq+8d6GVTg9awYqCBVn5T2+T3WP+qkiM3yU
z8/0XmqGLjVDj5rho+LYsGYYjFdREMrHVD3chsaV8SoKQg17obSH25DntPQkSgWh3t8eFsfs
YMarKAjlo5cebkNmDtPTkygVhBo2SdjDbWhYhZOeRKkg1M6o4TY0rDpPT6JUEGrX1+E21O+T
8SoKQg17T64P1gwn41UUhNrjhFFqhiE1wyijiRGZwTJquA1Zq8aenkSpINSuasJtyGv79CRK
BaH8yV8PtyHPzelJlApCxX5jzZDxKgpC7RwcbkM+GkhPolQQat99wm3Ia5f0JEoFod7qzD4h
M8NkvIqCUMPWlvXB0cTJeBUFofZYJNyG9lH+3fWY/3JWLf5l2BRTD7eh9x8Yr6Ig1K7Iw23I
67z0JEoFoYYt0uqDmeFkvIqCUMOmLnu4De2/+vzqNp59RX3UsMXjPdyG7AlUT0+iVBDqvSf6
z+Np3814FQWhduUUbkNe7aQnUSoItavlcBvy+1h6EqWCUPs7hduQvSLX05MoFYR648PiK+9q
6UmUCkLtPR1uQ/afnp5EqSDUrh/Cbcjv4OlJlApC7ZFFuA3ZC7o9PYlSQah9xoTbkLVL7elJ
lApCDVv31cNtyJ4h9vQkSgWhfParh9vQaXfX9CRKBaHi+M+v0k9PolQQyufF+8nRRMarKAj1
HhvbhzGasBmS9CRKBaH2SC/chvzOl55EqSDUuz3/+Z5Vs3twehKlglDDFjH2cBvaeydHE1QQ
ajx+FezMsM9WZoZUEGrYSsp+cgayMV5FQajYXiweHoPxKgpCDVu518OKyN5H6GlYlApCDVvW
1cOK6BwP41UUlDrsnjjDh8zGcJOZIRWUOmz8SSsiu9ulYVEqCDVsQrXTiujIeBUFpWydUacV
kY2Q07AoFYQathqtz8gMduebmRmooJSto+i0IrLjlIZFqSDUsCnxTisiu3elYVEqKGUrejqt
iOwenIZFqSDUeCwHT/qdn4xXURBq2MK8Tisi35/MDKkgVOxpLh6+GK+ioNThez0yg/88MwMV
hHq3Z3/pygXKEa+ioNThez2WCNqVnYZFqaDUYVmJVkT+XZkZUkGpw+6Pk5lhMF5FQanDRkhh
RWSvJvc0LEoFpWyCu9OKyH+ebmVUUOrwPRKLhzfzk9/wJUmV8u2FFZG91dXTsCgVlDpsT4cV
kS2072lYlApKHdebK2lFZPkmDYtSQanD5oPCimj/VWaGVFDKVj91WhHZrHEaFqWCUodvu195
JqZhUSooddh4l1ZEZ2e8ioJS9jCg04rIsmAaFqWCUjtmZmiMV1FQytYsdloR+afNzEAFpQ6r
V2hFZHV3GhalglLHYz+PzGD5Jg2LUkGpw6pzWhHZuD0Ni1JBqX00w4rIPy0zQyooddjcIq2I
xsV4FQWlDrsnhhWRLSjoaViUCkodfvZEZrBKJA2LUkGo8fh+CysiPwLMDKkg1M6PtCKykVMa
FqWCUG9sfykyg2WoNCxKBaGGrWbutCLyM+nLDKEg1Bu/e51WRFavpGFRKgg1zD+6/2g40hiv
oiDU+9vvXggrIlve3NOwKBWUsrWwnVZE58V4FQWlPK+kFdHJeBUFpWxla08rooPxKgpK2QPS
TisiO8ppWJQKSvkVTCsimxVJw6JUUOqwEcCPJmU341UUlLLVhz2siOwW39OwKBWUOvZf2let
VR9pWJQKQg1bwd5pReR7JDMDFZQ6rOr/fd6lPQ2LUkGpw6ratCK6GK+ioJTnFVoRWb2ShkWp
oNRh4zZaEfn3y5qBCkr5vSStiE7Gqygotc8Y2hdmvIqCUp6DaUVk1UcaFqWCUocfWdYMk/Eq
CkodlvnCimj6uZCZgQpK2SPVfkfN8GS8ioJS/glpRfTFqygoZevRe1gReSWShkWpoJTv6bAi
siFJT8OiVFDqsBmEm6OJyXgVBaXstYZOKyI7e9KwKBWU8qsrrYgexqsoKHXYM4ubJmUn41UU
lLLHtv2mSdnNeBUFpZrdg8OKyM+kNCxKBaXasD0SmaHfjFdRUMoeivewIrL+Zz0Ni1JBqWZj
w7AismFoT8OiVFDqsLtPWBF5XZGGRamglOdHWhHZ8500LEoFpQ6rOG8am07Gqygo5bXvzdHE
YLyKglL2IkS/P5OynoZFqaBUG/7ztAruaViUCkrZ4+dOKyL/fp/3cSgoZQ+TO62ILEOlYVEq
KGWuBZ1WRFaDpWFRKijV9s+vvEelYVEqKOXnGK2I7K6dhkWpoJS9DtDDisiW+/U0LEoFpZrN
OYQVkVm79DQsSgWlfE+HFZHXxGlYlApKNas+aEVkcwPPVzOEglLNst1TRhOPjCbCsKhS7fI4
qvDOeBUFpZrNcocVkU2C9TQsSgWl9p4+0witp2FRKijVbIYtrIhsgqqnYVEqKNWsnqMVkT3f
S8OiVFDKXjnoYUXkFVUaFqWCUvsTfoYjPQ2LUkGpZnciWhFZvZKGRamgVJse7yvK7kRpWJQK
StlLCp1WRHZHTcOiVFBqn5U0Kct4FQWlzFmjPzQpuxivoqDU/u2wIrI5lTQsSgWlzMllhBWR
nXsjDYtSQSk780daEd2MV1FQyl54GmFFZPexkYZFqaDUYYbvYUVkR3mkYVEqKLW3F5nh6oxX
UVDKXpcZtCK6b8arKCjV3uM0aEV0/RivoqBUezc1wopo+l+iYVEqKNUOjyMz3IxXUVDKcteg
FZF/v69mCAWl7FoZtCLyT5s1AxWUsjN/HFEzvPk44lUUlGqn7fXIDNdgvIqCUnaHG7Qieg7G
qygo1X627TApOwbjVRSU6n6ORWZ4L4CIV1FQqt3+89/eRsarKCjV/Oy5Y61+xqsoKNV+thci
M3zxKgpK9WZ7JDLDk/EqCkr1w86FyAz3wXgVBaWaXV1hRWS9ZUYaFqWCUvaCzQgrIptoG2lY
lApKdTvf2r7mbZl1xKsoKNV925EZfoPxKgpK2Ytbo0VmeBrjVRSUshee3rhso8s2dmaoVH8v
rNEiM/wuxqsoKGUv8bxxuF88jFdRUKpbDm5hX9gyXkVBqe7fb1/zNh0b8SoKSvXTf162cco2
dmaolL3qNdoM94vJeBUFpZrlyhaZwRyaWmYGKijVLIO3yAzzYryKglL72HCe4Wa8ioJS9rLe
aGFS9st4FQWl+mHH6TMpi3gVBaWaXZuNNcPFeBUFpfb2mBluxqsoKNVu216YlFmubLQySwWl
9tX1XJlFGzNDKijV7Tj1yAzveC7iVRSU6nYv6TQ2vRmvoqBUt33YW/riRLyKglLdtx2ZYf98
luPRIzMUyl6LGz0yw53xKgpK9W6fNjLDPBmvoqCU3xl6fzKX7HgVBaXssIwemcGZzAxUUMpe
6XzjJzNcz5qBCkrZ1xmdmeFmvIqCUnYg3zjutRmvoqCUn8e9ZIYumaHvzFCpZrmy09j0YLyK
glLNz7HIDH6cMjNQQSm7sN74u2p3vIqCUt33yC/u5w/jVRSU2kczMsPvZLyKglLtsjgyg5/f
mRmooJRXsmYY5998Ml5FQSmvOHpkht9kvIqCUs2P02dsGvEqCkq1/p5jI0YTdgRGjiaooFR7
T5Y3/q7aHa+ioJTNa4zR0ucu4lUUlPIaZURm+OJVFJTy/DhYMxyMV1FQys/K99Tf32MwXkVB
Kc9Eg5kh41UUlPIzZkRmmBmvoqBUsyM7IjOcGa+ioFSzzDf4bKIzXkVBKXt1e4wz7uc/xqso
KOV16Zjf/XzMej8fUTMUymvfEZnBP3lmBiooZcsnxojMcDfGqygo1bodp8gM7WS8ioJSzb9f
1AzPyXgVBaWs7B0jMkP7MV5FQan9nVgzNMarKCjVTvtL9/Xt3cwMVFCq2Sh8PPG0L+NVFJSy
eY03jnmGi/EqCkr5yOLkDOTNeBUFpbqNAM7IDE/Gqygo1d//jJM1w8V4FQWlvMo8IzPY/jwz
M1BBKVsAM07OM2S8ioJStgBmnJEZ7D52ZmagglJe9Z/7mrdXHCJeRUGp9th3isxg964zMwMV
lOp2/M8YTdj5duZoggpK7e2d6XMX8SoKSnnVf7JmOBivoqCU5+AzagZnsmagglLdrs1zX/N7
7zAzpIJSzaqo91+/bVy9buOKK+qj+uHxngOw0evJzJAKSvmZf7JmOBmvoqDU3gsxz2C1xJnz
DFRQqvtZee8q3EaWO15FQSm/X537mjfD/YhXUVBqH80ntvFjvIqCUlZaj5PzDBmvoqCU1/A2
XczzaserKCjlR3MyMxyMV1FQyueAZstn9BGvoqBUsww+WTNkvIqCUj4Ks8LIM0PGqygo5Xe4
ua95eyUr4lUUlPKzcvZvfD57HZ/PGE0Uyq+VWeYZpswzTGaGj/IK0JIyM8OOV1FQau+FyAw2
ApiZGaigVG/+8zvz7syagQpKNRsnzqgZLI/NrBmooFTv9ttzX1FfvIqCUjaEHpOZoTFeRUGp
fVZGZrgexqsoKNUe+23OM2S8ioJSfr+yaSTfVzfjVRSU8jmHua/5vXeYGVJBKa/OZmQGP5My
M1BBKVt+N2ZkhiPjVRSU8txlHyDPxCevqFBQyhahjSsyg83VXJkZqKCULaZzS2XPVw/jVRSU
8tr3KjXDJTXDxczwUT7Su5gZfoxXUVDKnyFckRnsnn9lZqCCUn6tXBxNZLyKglJ+Vl4xmrgy
XkVBKZv4ekvfeHfwYbyKglL7O41vfH6NOj6/xv19c2YG+0v7mvdRzcXMkApK+Xjniprhi1dR
UMqfU1yRGaxGvTIzUEGpbk8drsgMlmOuzAxUUGp/J2aGzngVBaV87uSKzHBkvIqCUj4TcjEz
nIxXUVDKpn/c8o/3j+uXM3ehoJTX11dkBj8XMjNQQSm/M1wxmrC6+8rRBBWUajbKuGKewSqD
K+cZqKCUz7ZckRm+eBUFpWyCe/yOfA8g4lUUlPKR9+/4tvE76jZ+Mc9QKH+O9+M8w4/xKgpK
2ZNxNxz1b94Yr6KglN+pf5EZ7C7xy8xABaW8Zvz174niLzMDFZTyLPGLzDAzXkVBKVtUPn4j
xs4P41UUlLIJvDeOKvxhvIqCUvu3WTOcjFdRUMqm/Nz6llfUT0YTv8gMhfIZTzMD9e9xMl5F
QSk/j38zZgcn41UUlLJp3vFjZsh4FQWl9rGJeQa7mn85z0AFpZpl1x97TzTGqygo5WORHzPD
ZLyKglL+LOR3f3P6vxxNUEEpm1xzoxz/VDfjVRSU8nHC7/nm9H/ZoYIKSu39FpnBj2xmBioo
ZdO8bq3jx/xivIqCUp4fb2aGg/EqCkr5/eo+nrw+7iPv56GglD8xu1vMtw/Gqygo5bXv3WJ8
nvEqCkrZ5LMbSdlvjIxXUVCqWya6d4eKYG75jbiiPsqm9n1BOuv2e9RZtTsyQ6H2d4qawaqo
O2sGKijlcw531Ax+zLJmoIJStsjfDeP+FqOzOztUUEGpbjPp9/yu2nvWq/aOzFAoe3DiSxB9
G53xKgpKdZuHv69vdvBmZkgFpcxu4o2vzO13dqigglLdxtQ3M8PNeBUFpcx04Y2v7wh+o4lQ
UKrbveuOmsGy4J01AxWU2mfMPb9jzg4VqaDU3gv7mvf8fzMzpIJSZrTh9m+swu+nVuF3ZIZC
+Zn/xGjC3sR4cjRBBaX8aD7HN2J5jjpieZgZPsrnTp7IDLbtJzMDFZTq0+KoGWz0+mTNQAWl
7HHOeKJmsHPvyZqBCkr5ewdP1Aw2AnyyZqCCUl4BPv17s+bJzEAFpbq94fGMb3bwGXV28InM
UCg/jx/WDI3xKgpK7ZgzkCfjVRSU8pH3E5nBzu8nMwMVlPKn1g8zw8V4FQWlus0aPRxNHIxX
UVDK5+SeqBn8k2fNQAWl/A73XN/4/Lnq+PyJzFCoPuw4/b7x+fOr4/MnMkOh/LnRE5nBKpEn
MwMVlPIR0hM1Q894FQWlfNboub/7+XPX+/lzz5xbCspnQp6oGa6D8SoKSnnN+ERmsLmBJzMD
FZSy+f3ziJrh3X0Rr6KgVHuz3RvnM/qIV1FQyqozX7T4tz2ei3gVBaWsgZkvy47RRMSrKChl
I6Q3fr5PlZmBCkrZ82Ff1Pu3PeqPeBUFpWyG7Y1vniURr6KglI13fBGQf4/JeBUFpVqz346a
YU7GqygoZXXQeZz5zl3EqygoZbZ9b/z7tnH+6jbOeBL3Ufbyiy8Iies84lUUlDKDvDeO9wAO
xqsoKGXjT1+o+rc9qol4FQWl7OmiL1nwvTsYr6KgVPejGZnB92FmBiooZXdRX+BpvzEH41UU
lNrH/445/cF4FQWlbJ7pjXN8HvEqCkrZNe/LO/Jsz8xABaXasN/+RhMRr6KglL0J+sbx/Pxm
vIqCUu39cO9pE1dtZ7yKglI2snjjqBkG41UUlLJ3/Hy5Dc/E9o0mQkEpe83EL5i4O0e8ioJS
9kKHP+y23zgzXkVBKXum88ZZ6Ue8ioJS3a7NxsxwMl5FQSmb/fJXmZmp29fVKhSUsvl9f834
b3u+I+JVFJTq/pfOfBs34lUUlLJX1t4Elu/pR7yKglJ29/EpMP9UjfEqCkrZyNtvKP4bP8ar
KChl42h/ZSi/R2YGKihl4zZ/CObf48d4FQWlzPrM01Hu3awZqKCUOcf6be5veyQb8SoKSvXb
fz4zi7ZvNBEKSg3/S5EZ7I7aMjNQQalx2Kf9ZiAjXkVBqe7n2PPda9tT77UtMkOhzPTNS2bf
xo/xKgpKWT3nj2nsN/qP8SoKSnW7M/SoGexM6lkzUEEp32+dnTB/jFdRUMpG3u9GY759MF5F
QSmzBvSXIpkTe2YGKii1P2FkhtEYr6Kg1PBtj3xTNuJVFJQap237zPn2iFdRUKrb2dPZCXMw
XkVBqb29WbYxZRs7M1RqdPu0kRns/O6ZGaiglL2s58NvP+ad8SoKSnW7J/bIDFbn9cwMVFDK
Tkgfwvxtr3yMeBUFpfZvR787P/ey3x0VlGp+FbCr1cV4FQWlzFHSJzd4/+iZGaiglO0yvyj9
m/8Yr6KglM31vnGsrjkYr6KglM0nv3Gurol4FQWlbEWEJxee7SMzAxWUsov3jXP9YMSrKChl
c73niK5Wdtce2dWKCkqZRa7bRNs2LFeOzAxUUMpr+LGveWtvGvEqCkp5BTgiM7TJeBUFpewt
/3NEj1yrV0f2yKWCUs23HV2tnpPxKgpKec04IjP4PszMQAWlbPWIm7v7MT8Yr6KglJ/HIzph
Wg02shMmFZTqfi5EZvC/mpmBCkrZs3Q3g819lZmBCkp51R99sa0fcMSrKChl79meIzpU+HHK
DhVUUKrbvSv6Yk/fdmYGKijV7zcrRfdsr3aye3YqKNV9j0RmsAye3bNTQSmvAEd0wuwH41UU
lLJEd7J7tlXqX/dsKijVfS9EZrAM9XXPpoJSfoc7WTN0xqsoKOXH5oxOmLZ3zuyESQWlbL7s
ZPdsy4Jf92wqKGU30JPds+0e83XPpoJSPjZk92zLY1/3bCoo1ffP403Zh/EqCkr5GcPu2cfD
eBUFpbxyYvdsOxe+7tlUUMpmh092z/b9+Y0mQkGpvn8es2on41UUlPIRUnbPPhmvoqBU9+83
872+M7tnp4JS+/jHPIPdibJ7dioo5VV/dM++fK/nDCQVlLJnbGd0z758fzIzpIJSft+N7tlX
PxivoqDUPpqcZzgZr6KglI9F2D17M1N+Y+aIJaj9nSIz+HHKzEAFpWwVzMnu2TZu/7pnU0Gp
PuyMYc3wY7yKglK+F9g92+5dX/dsKijlFTm7Z8+H8SoKStmTjZPds636/LpnU0Epe453To4m
DsarKCi1fzsyg+W07J6dCkpZQXOye7ZVtV/3bCooZcXfye7ZdpS/7tlUUKo/HsfbOyfjVRSU
8qzN7tnnyXgVBaX8jGH3bN87Z6305/ldUUHZEOFk9+wxGa+ioFT3fTjzieL5dc+mglKeu9g9
22Yvvu7ZVFDKry52z7bZva97NhWUsoVuJ7tnW775umdTQanmeyQ6YT4Zr6KgVPNjEzWDXXVf
92wqKGXvYp3snm1X2tc9mwpKeX5k92y7K33ds6mglFfks4wmpowmZmSGQu2zkjVDY7yKglL2
lPRk92w7yl/3bCoo5TNs7J5tFc7XPZsKSvkVHN2zfYyS3bNTQSl79+eM7tk+d5rds1NBKR+L
sHu2zdx/3bOpoJS9bXpG92zziTize3YqKOUztxdrhsF4FQWlvBq4WDMMxqsoKOVnTHTPtjcS
z+yenQpK7U8YmcGu7OyenQpKdT+ykRmsDs7u2amglD3tPaN7tjmvnNk9OxWUsid/76093awi
XkVBKX/qEN2zfZSZ3bNTQSl7O/7M7tmT8SoKSvkoLLpn72OWowkqKGUL1994++L8JuNVFJTy
J3/snm1zEV/3bCoo5ff2i5lhMF5FQSlrW3Rm9+yT8SoKSvnTxSv63d0Zr6KglI/Conu2OXed
2T07FZTy5y3snm1H9uueTQWl7D3CM7pn+3fN7tmpoJQf/1/0u7Ns/st+d1RQylaineye7Z82
+91RQSl7onxG92w/L7J7dioo5TMI0T3bx6XZPTsVlPK7D7tnW0X1dc+mglL+FIjds+0M/bpn
U0Epv+aje7aP4bN7diooZW+Vn9E923yZz+yenQpKeZ6P7tl+r8zu2amglF+P0T177x1mhlRQ
yuc1fqwZJuNVFJTy0Ut0z/a8md2zU0EpvzNE92xbJXpm9+xUUMreET/ZPdtqya97NhWUanaH
i+7Zp80BZvfsVFDKDCrO6J59+pHNTphUUGrHrBkm41UUlPL5suiebR6LZ3bPTgWlfE/fJTPc
khnuyAyF8rMyumf7X83u2amglI9eonu21xXZPTsVlPIxbnTPtgVQZ3bPTgWl7M2qM7pn+8xC
ds9OBaXa9J//Ml/d3zxDKCjlT9/vMs9wyzzDHZmhUL15fOWZmN2zU0EpWw16RvdsK8zP7J6d
Ckp5JXtzNJHxKgpK+bUS3bMvP8rMDKmglM9yR/fs/clnvaJ292yh/L4b3bP9KVd2z04FpZrl
yuie7W9iZPfsVFDKc3B0z/bnMNk9OxWUar4Pf7HyJeNVFJSyB6RndM+29TRnds9OBaXs/e0z
umfbm0pnds9OBaVszfB5c56hMV5FQSm/t0f3bM/N2T07FZTyaz66Z/tcdnbPTgWl/Ng8HE00
xqsoKGXOJOfDeYab8SoKStlD8TO6Z/v5nd2zU0Ep32/RPdtnYbJ7dioo5W9WRfdsH19n9+xU
UMpeBzgfjiYG41UUlLK2kOczYuzcGa+ioJS9ZnJG92zzsD6ze3YqKGWOBedTMsMjmeGJzFAo
ewXkjO7ZNhV0ZvfsVFDKXrA5n+hdY7nyyd41VFDKzNLO6J7tlWF2z04FpbwCjO7Z+0zKzEAF
peyFjvNhzZDxKgpKebZ7rnhPfzBeRUEpn3OI7tn+xlV2z04FpTw/PiUzPJIZdvdsofyJWXTP
9mfs2T07FZTy+9Vzx9h5MF5FQanmZ2hkBsse2T07FZRqfr493zP67J6dCkqZ9dmM7tk2pTWz
e3YqKGWvy7xxXLUP41UUlDKfwxnds21cOrN7dioo1fbPf/zm8/gyQygoZV4m82BmmIxXUVDK
1pXN6J5tV93M7tmpoJR55MzjywzzqJlhHpEZCmXOujO6Z1uFO7N7diooZZ6p82BmOBmvoqCU
GbLNg6OJh/EqCkrZU+sZ3bPtPZeZ3bNTQSmrAGd0z7Y6b2b37FRQyq7HGd2zra6Y2T07FZSy
e/uM7tn7vMjMQAWlbBQ2o3v29H2YmYEKSpkV3Yzu2TY9PrN7diootc+YyAxjMF5FQSl7x28e
zAwH41UUlLJaa0b3bFvxMbN7diooZXXpPJgZfoxXUVBqn2ORGfrJeBUFpew594zu2Tb/NLN7
diooZY7mM7pnWxU9s3t2KihllpOzlczQJDM0ZoaPMnPHGd2zbQZxZvfsVFDKr8fonm1jrZnd
s1NBKXN/n61f36fqV/1U0bumUFbVzOiebdXnzO7ZqaCUzQHN6J5tNfHM7tmpoJTn4Oie7fkm
u2englI2spjRPdvPveyenQpK9WFHc+YKnpnds1NBKXMUnNE92/xBZ3bPTgWlul3B0T37Go3x
KgpKdf+0V9zPL8arKCjV919Kh42Z3bNTQSmb8ZzRPduzYHbPTgWl7Fn6jO7Ztnx/ZvfsVFDK
nuPN6J699yc7VKSCUv1nn3Zf89fVGK+ioNT+7adctY9ctU/ZxqbsDeMZ3bNtzc7M7tmpoJQf
m+iefdn9Mbtnp4JS9kbrjO7ZNi6d2T07FZSycfSM7tlmXDCze3YqKOV3uOiebb4EM7tnp4JS
9m7D7D1WvjyMV1FQyl4hnNE9e39XZoZUUMpet5zRPduaUM3snp0KSpnr7Yzu2fZkc2b37FRQ
au+3M66oH+NVFJSKeF+1M+NVFJSy2ndG9+zLMlR2z04FpfZ3mmUbU7Yx5/fNIzOc/pee73jM
px6P+V1RQXXf65EZ/K9mZqCCUvam9Izu2dZMa2b37FRQqvv3i9GEnz05mqCCUrZ6ffbfd0X1
X72i+i/XuJPqvu3IDH5eZGagglJ7e8wMD+NVFJTqVjlH92x7RDWze3YqKOVZIrpnX/NgvIqC
UrYycEb3bHNemdk9OxWU8uMf3bPNt2Nm9+xUUMrP/Oie7Xkzu2englL2NsSM7tm2Mnhm9+xU
UMpemJ3RPdtrsOyenQpK2Uu5M7pnm2/HzO7ZqaCU+eTO6J599YxXUVDK5khndM+2dVozu2en
glJ7v525Vn9m9+xUUKr7cYrMYNd/ds9OBaX8jBmsGR7Gq/yLuTnOP//+L3t3ODLzZIs22n5y
R4NsWwAzs0F2Kihlk8wzGmTb4+eZDbJTQSnLlzMaZE8/FDlgoIJStnxzjm8qYY46lTBHXPyF
spfAZjTItncSZjbITgWl7AH7jAbZXphlg+xUUMruRjMaZNvT/5kNslNBqe6n1DeVMEedSpgj
Lv5Cdb80nt/3qbI9DRWU8kQQDbI90WWD7FRQyrL4jAbZ9nLYzAbZqaBU95/HxW+nbTbITgWl
/BNGg2x7G2Nmg+xUUGrHcfFfGa+ioJQX9tEg28v3bJCdCkrZ46d5csCQ8SoKSvlQ4GRLu4fx
KgpKWRuZebLZ5WC8ioJSPhyPBtn7k+eAgQpK+eA6GmTbdPXMBtmpoJSXU9Ege/4a41UUlOr+
naJx1XUwXkVBKXv1Zp7MDAfjVRSU6r4Pr7TwmdkgOxWUsoVg82Qb3IfxKgpKeRkSDbLtJZ6Z
DbJTQanuP79z2n5mg+xUUGp/p5hK8CsipxKooJQPHk42rhqMV1FQyieGTra0G4xXUVDKb8bR
INsHxNkgOxWU8oFWtL62xRAzG2SnglK2bGXOaE8zMl5FQSmfUGGD7PNhvIqCUj5UZoPsazBe
RUEpH26wQfZ5Ml5FQSlbejznyIdtEa+ioJRfK9Eg24uNbJCdCkr5pA0bZNuk3dcgmwpK+UCL
DbJ/Ga+ioFTbP3/y/jG/ZpehoJS9ejPZINsqhq9BNhWUssnyOZkZJuNVFJSyR45zsg1uxqso
KLWPDZtQHIxXUVDKRuKTDbKtXvkaZFNBqebnQmQGP06ZGaiglE/URetre3wws0F2KihlC3Zm
tL72CaNskJ0KSjX/fk++DDu/BtlUUGqflU8u7J1fg2wqKOV3hosDhofxKgpK+X6L1tde9maD
7FRQyh7uTTbItk/7NcimglI2wzOj9fX84lUUlPJrhQ2y7Zz+GmRTQalmZ+jFzNAZr6KglD3K
nmyQ/cWrKChlr/dMNsi2u/bXIJsKSplF/2SDbP9Lp2wjMkOh7MH0ZINsOy++BtlUUMqrGjbI
tvPta5BNBaVsDntmg+yL8SoKStnc72SDbLuavwbZVFBqH80rH/XPr0E2FZQyg/fJBtk2ePwa
ZFNBKXsdcUbra3tMOLNBdioo5fUcG2TbhNrXIJsKSu2jeeer+PNrkE0FpXx6nQ2ye2e8ioJS
9shxskG2H9nMDFRQqtmdgQ2ybXr0a5BNBaWsD9fMBtkZr6KglPXImtEg2yvcbJCdCkqZd8OM
1tdeH2WD7FRQyjwoJhtkb+aS34htfJR/JzbItpHs1yCbCko1OzZskN0zXkVBKT+P2SDb7mNf
g2wqKGU+FzMbZE/GqygoZc+qJhtkW6X2NcimglLNRn3R+vq0fJMNslNBKeukNqNBtr1cPLNB
diootT8h2+BejFdRUMqeI002yLYz9GuQTQWlmo30ovX1/hxsQpEKStkD9skG2edkvIqCUmbO
M9kg2zLU1yCbCkrZM7eZDbIPxqsoKGVNpt/yISr9m/EqCkodVktE6+vTrzRmhlRQyusgNsi2
3Pw1yKaCUvaqx2SDbHsg8zXIpoJS9pLLvI944fZmvIqCUvZ0a0bra89p2SA7FZQy+5jJBtl3
xqsoKGXtOGc2yD4Zr6KglOfHu8ei24xXUVDKr3k2yLZRxtcgmwpK+eieDbItK30NsqmgVDs8
jpeAMl5FQSnzmnnjeBn2YbyKglL20tGM1tebycxABaXMX2hG6+vTqoRskJ0KSnk1EK2vbd3n
zAbZqaDUPmNmLCnIeBUFpTxrR+trG4DPbJCdCkp5fmSD7HMwXkVBqcP/0r7m7cX4mQ2yU0Gp
fY7ta/68JuNVFJTaeyEaZNv98WuQTQWlmm+bDbIfxqsoKGXeP5MNsq1e+RpkU0Epe113ZoPs
yXgVBaWaja/YINtmk74G2VRQymcQ2CDbvt/XIJsKSvmIlQ2y/a822UZLcy9SPv5kg+znYryK
glLWCGhG62t/xJ0NslNBKX/dKlpfBzPlN2J28KP8RZpofW0LjGc2yE4FpXyExAbZdqV9DbKp
oJRnbTbIfjrjVRSUsgUiM1pf+xxwNshOBaW8OovW1/ay3swG2amglI8sovW1GUjObJCdCkod
++dpZTe/BtlUUMrezZrP17hqPrVx1YwG2ZWynrDz+drgzmyQnQpKeR0Ura+tR8HMBtmpoJRf
wWyQfU/Gqygo5XmFDbKt+vwaZFNBKXuzZz4lMzySGdggu1B7L0Rm8LM1MwMVlDq6x9efrMiy
QXYqKGUv317ZIPthvIqCUuaUeEXra6t2rmyQnQpKmePjxQbZ7/3x+hpkU0Gpw7fdJiuAKxtk
p4JStheugzXDxXgVBaWO7j+P+3ljvIqCUsewvRCjiXeMcn0NsqmglN2vLjbI7o3xKgpKHbdt
jzXDj/EqCkpZfX2xQbbvkWxpRwWlmh+byAzjZLyKglL7+EcTinExXkVBqeO9gV5skD1+jFdR
UMr+c7FB9hiMV1FQ6vAjG6OJcTNeRUEpG+Nexy9feYt4FQWlLM9f0fraZhCvbJCdCko1/7Qc
TXTGqygo1fw7RWbwMzQzAxWUsgrwOp6s9CNeRUEpq84uNshunfEqCkpZtrui9bWfe9kgOxWU
8nMsWl9bTXxlg+xUUMpG3ldrYYqV8SoKSvnRjNbX1vHsygbZ/4+/8c9/HH/a//7pP0fw9//5
x//5o+04/vM/8Od//OuP//BP95/vfvlrvWD78x/a+w+9P//4/tXz/Edz/v0Lf/y7//Kv//Yv
f//Xf/m3f+j//q///cd/+uuP//aHgc3+bLc3D352xN1X+dkP/Pc/v5v/v/3zP/8xzWW1bUsi
f9u4hSWRrc17KwPf4/fVGK+ioNS7OyyO2c6L8SoKQo3nvUYbzYbui/EqCkKN82e/fe/ffqvp
RkuiT0Go/njsNmTj8u8aZmWfglDdVo+1bTbknZ0aLYk+BaH6/Sajts2GvN9UoyXRpyBUf977
b9tmQ8MazTVaEn0KQnVbp/XGvg17FSTiVRSE6vdhf8kXAXp/o0ZLok9BqPc72fbcOGCY40Cj
JdGnIFS3tXltmw15R6RGS6JPQah+v3e6N97bOCbjVRSEer+T/SVfBOh9gRotiT4Fofrjf8mX
B3tfoEZLok9BqPcT2l5wS5Fhj18aLYk+BaH677HtuQ3ZsNnjiFdREOrd0/ZzXwS4zyRaEn0K
QvXf/vn1bSMWEX8KQnVbH9u22dCwB2iNlkSfglD953/p2tsYGa+iIFS3dYxtmw0NMzpqtCT6
FITqNu3QttnQuL54FQWhuq26attsaFy/k/EqCkL1p9lx2pnh5+ceM0MqCNVtpV3bZkPe2anR
kuhTEKrfzc63J67ah/EqCkJ167PQttnQsMn7RkuiT0GofQVvs6FhE+uNlkSfglDvJ/Sf7yvq
3eGNlkSfglDd1q62WTLDlMwwIzN8VLf1sW1GZnjvbm1mZqCCUO8V/O6RGZnBzr2ZmYEKQu38
uM2GxuXb7rxqqSBUt94abZsNjZ9vm5khFYR6P6HtEWaGk/EqCkJ16/jRttmQ97RqtCT6FITq
1oGlbbOhcT2D8SoKQvXH9/rODPago9GS6FMQqt9+ZHdm+B0n41UUhOrWe6Zts6F9ftOS6FMQ
Ks6xa1+1/v0uXrVUEGrfr2ZkBruDz8wMVBCq2/RJ22ZD3v+r0ZLoUxDqvVbs++3MYA4QjZZE
n4JQ++raZkPv3vkxXkVBqDdL2HGKzGD5f2ZmoIJQ3WuUbTY0fv5zZoZUEKpbV5G2zYbeT34x
XkVBqP7YvWSbDQ3zWmi0JPoUhOq2PrZts6Fhj3gaLYk+BaG6TU61KzKDna1XZgYqCPV+Qo/3
Nt7haKMl0acgVGyv9+83eq+/4QuCKtWti0XbZkPelazRkuhTEOq9M9jPIzMcGa+iINR7/C+L
9zZsr9OS6FMQqts637bNhoY9eGq0JPoUhHrjbvG+at+ioNGS6FMQqts633YxMwzGqygI1W0V
dbsiM7ST8SoKQnVbH9uunRnsEU/EqygodTT7TjszeL1CS6JPQaj3ty3emcHHDLQk+hSUOnyv
/2Ibk/EqCkL1x7cXmcF/npmBCkL127e9M8Pl1xAzQyoI9Y4T7Ay9v6uWlkSfglDd+tu0KzKD
ZdcrMwMVhOo20f3Gext2J7oyM1BBqcNy5S8yg/2lX2YGKgjVH7vb/SIzjIxXURBqf6dtNjS8
GqQl0acg1M6Pv8gMVhP9MjNQQah3L1jMzPAwXkVBqG5T4+0XNYPdx35ZM1BBqG4OAO0XmcHu
K7/MDFQQKr5TZAar2n6ZGaggVLfV4O0XmeHOeBUFpQ67t/8iM1wX41UUlDqskv1FZvDPkZmB
CkrZOt+2zYaGPTpstCT6FJSyldptmw2N249TLBX8FITaOXibDQ3bbKMl0acg1Bvb9iIz+FHO
zEAFpWxeuf2iZvCjnDUDFZSyidW2zYbevXMzXkVBqX2tRM1gOf+XNQMVlDp8j0RmOCfjVRSE
evO8/Twyw5HxKgpC7dHLNht6a+LOeBUFobo9qmh3ZAbb9p2ZgQpCvWf+afHexp3xKgpK2fR7
u6NmcCZrBioI9Z75P4v3VXtnvIqCUN06kbVtNrRHmbQk+hSUsmnrdkdmuDNeRUEpW9Xe7sgM
dhXcmRmooFSzu+g2Gxp2yTRaEn0KStkTwLbNhobPvNCS6FNQyuxw2h2ZwbLHnZmBCko1/06R
GZ7JeBUFpewJYNtmQ+Pn32/yiqKCUrY6v22zoX2d0pLoUxCqW7ezdsdowo9AjiaooNQ+NpEZ
7I5xZ2agglL2hm7bZkPeLbXRkuhTUMreOWl3ZIbnZLyKglI23dvuyAzzZLyKglJt/3xvw+qK
OzMDFZSyXidtmw0Ney2k0ZLoU1Cqnx779WgvRzRaEn0KStn76G2bDQ0f79KS6FNQyt7pbdts
aNjrLY2WRJ+CUvYUvm2zoWEXcqMl0aeglJmjtW02tOs8WhJ9CkrZssG2zYaGzybQkuhTUKrt
eN/PbST75GiCCkqZKX57Rv+++ej1m+/MUClr/dm22dC47dyjJdGnoFT37xSZ4cx4FQWlrNFU
22ZD3lm20ZLoU1Cq+6edsY3GeBUFpbrdJbbZkHeWbbQk+hSUsgWT7YmaoQ/GqygoFfH89m6O
JqiglJl3tGdf8z4b/TAzpIJS3c/Kfc378wtaEn0KSpmlettmQ+P2vc7MkApKWa+Tts2GgmFm
SAWlho2Kn33N33Y1P8wMqaDUsJHME5nBsvmTmYEKStmq3fZEZrCc9mRmoIJS1hemH5EZ3qzU
j8wMVFDKvtMb7228Y+qIV1FQyhZf9yMyQz8Zr6Kg1P7tyAwj41UUlLLVrf2IzHDcjFdRUMpW
nPdtNjRsFrfTkuhTUMrOyr7NhnzU32lJ9CkotT9hZIZ2Ml5FQanuez1GE/7zHE1QQSkzL+9H
1Ay/m/EqCkrZqre+zYb8XtlpSfQpKDV8j0RmOA/GqygoZQ02+hGZ4TgYr6Kg1PDjFJnBj3Jm
BiooZWu7+zYb8uzRaUn0KShl13w/IjMcF+NVFJSyVVb9iJrhl/EqCkp134eRGfrBeBUFpWwd
fN9mQz5G6bQk+hSUGsOOf2SG38F4FQWl9p6OzHA0xqsoKGV9enormaFJZtiWREL58d9mQ37P
77Qk+hSU2r8dmcE+bcvMQAWlhn3CFpnBzr2WmYEKSr0XzhtHZnjvY71lZqCCUmPap+15r+20
JPoUlLJl3H2bDQ17lbTTkuhTUGp/wsgM5814FQWl7BF3b1Ez3CfjVRSUsgXsfZsNjdu/38kr
igpKnXaGbrOhYQVUpyXRp6DUOTzez+j7YLyKglL2vkTfZkPD5oM6LYk+BaXs/ay+zYbG42dS
rBb6FJQ6/djsa96Km05Lok9BqX1sIjP4mZSZgQpK2ePO3qJmeDJeRUEpewesb7Mh7/veaUn0
KShlr070bTY07FlYpyXRp6DU6fswMsOZ8SoKSpkxQm/MDBmvoqDUaRljmw29n+NivIqCUtbB
q3dmhsZ4FQWlhp1vPTLDzHgVBaWGHf/OmuFmvIqCUuMdIfUemeFsjFdRUMpeTOk9MoPtnZ6Z
gQpKjZ99wsgMdi70zAxUUMrvVz3mGe4f41UUlDJXlN45z3AxXkVBqWH3x202NGxKq9OS6FNQ
ypoh9m02tO9jtCT6FJQaw38+vyOYNQMVlBp2hvaoGUZnvIqCUtbnrW+zofdMOhivoqCUOa/0
zpqhMV5FQalxWRyZoT2MV1FQytbv9x41w3kxXkVBqXHZkY3M4GdrZgYqKPX+n8W7Zrgm41UU
lHoPjr1jNr4jmJmBCkqZk0zvkRnGj/EqCkqd9tvbbGjYc8NOS6JPQSn/7RGZwT7tyMxABaXM
DKOPyAzvqKaPzAxUUMrsTPqIzGAZY2RmoIJSZk7St9nQzrS0JPoUlBo2ktlmQ7vupiXRp6DU
aXXwiMzQbsarKCj17kSLv9HEkNHEiMxQKHtZr2+zoZ1paUn0KSh12h11RM1g1c7ImoEKSnk1
MCIz+D7MzEAFpU7f68wMg/EqCkp5/bCdiHZupl/Rp6DUedjxj8xgd6WRmYEKStmLdH1EZrAr
bWRmoIJStqk+mBkuxqsoKDX8OP1yVq3Tr+hTUMpeQOvbiWjYdFOnX9GnoNTw78ea4WS8ioJS
p58L+5q3N4c6/Yo+BaXOw47Ts6+o+2G8ioJS9mJjP6NmeC7GqygoNd6U0s/IDHaGnpkZqKCU
/WI/IzNYFXVmZqCCUvZaXN9ORLuKpl/Rp6DUafX8GZnBvuuZmYEKSpkJUT+jZrDK4MyagQpK
2VvHfTsR7SNAv6JPQSmz4unbiWjXFfQr+hSU2tuLzGAjjjMzAxWU8or8jMxgZ9KZmYEKSpkJ
UT9jNGHV4JmjCSoo5dXydiLyWbFOv6JPQSnP2mdkBj8vMjNQQSnPKyczw8N4FQWl9m9HZrDR
0pmZgQpKWYLo24lojwDpV/QpKDX2z+Oq/TFeRUEpv/uckRksj52ZGaig1D7z9zVvbxR0+hV9
Ckp55XRGzWBzXGfWDFRQyk6Wvp2I4nMwM6SCUmd7fz6jZrAcM7NmoIJSfm/fTkTDloB1+hV9
CkqZI0qf26PssOw66WSWCkINa9jcw4nInuP29CtKBaGGrZ/q24lo2ORqp1/Rp6CUvTzZw4no
8O/XcxuhINSwdUd9Rmawc2FmZqCCUvasuNOJyD8t1xGmglDDNtW3E9Gw6fFOv6JPQSlzAOzh
RGSLe3r6FaWCUGP694vMYLl5ZmagglLWFKFvJ6JhnQc6/Yo+BaXssPTtRBRHgJkhFZSyF2Z7
OBHZWrOefkWpINSwleBvvLfhZ0/OM1BBKfNp6eFEZEuOevoVpYJQw/xNejgRHVY5p19RKgg1
Tv9+22/kaBmvoiDUsBdmezgR2XsOPf2KUkGoOP6xQnA0xqsoCDXMMLSHE5GtYezpV5QKQu0z
P5yI/HOkX1EqCDXsRdMeTkSHHYH0K0oFoYZ5EvRwIjqujFdREGrYyuMeTkS2DqinX1EqCDXs
dcseTkS2EKqnX1EqCDXMpKuHE5GtYezpV5QKQo3pnzZWCFq9kn5FqSDUsBdmezgR2YOBnn5F
qSCUrxHo4US0GbqSpIJQw9qM9HAisuWLPf2KUkEoXx3R6URkczXpV5QKQg1bQd3DichWC/b0
K0oFoWJPb1eB472Qe/oVpYJQw9b49nAi2kc5MwMVhHpjOzaxQtDuj+lXlApCDbt4ezgRHXav
TL+iVBBq2DrifjEz/BivoiBUHJuoGXx/Zs1ABaXMj6lvJ6KdN+lX9CkoNf3a3Ne8vZ/c6Vf0
KShl67r7FTXD3RmvoqCULVTov6gZ7Az9Zc1ABaWsaWHfTkRvbu6MV1FQyu8+24no/auD8SoK
Svm1Ek5Etiy2p19RKgjlK616OBF5vkm/olQQathNoYcTka1b7elXlApCDfMe6XQisist/YpS
Qaid7X4lM/wkM/wiM3zUMC+xHk5Eh40s068oFYTad2o6Edl8YPoVpYJQe16cTkRWS6RfUSoI
9Y6Q7DtFzWCzIr+sGaig1Nzx3oaNBtKvKBWEGrbOvocT0WEzVulXlApCDTMu7OFE5Pkm/YpS
Qah9BYcT0WH3rvQrSgWhxuV7mn4jF+NVFIQa049/1Ax+JmXNQAWhhi1t6OFE5Lk5/YpSQah9
BYcTkT1Y7ulXlApC7YwaTkSH/6WsGagg1L6331Ez2Bj+zpqBCkIN8x7p4UTknzz9ilJBqH0e
hxORLU3v6VeUCkINWwzRw4nIj0D6FaWCUMOsz/sdmcFmFu7MDFQQaljZ28OJyF5x6OlXlApC
DVs40sOJyK+69CtKBaHeT+g/39t4foxXURAq4vAo++JVFIQa9rp+Dycia1/T068oFYTyVVD9
/vxGevoVpYJQ4/K9wJphMF5FQShfidjTiSjjVRSE8nfSezoRHYxXURBqWPHX6UQ0L8arKAjl
K636Tb+Rg/EqCkK927M9HZnhuhivoiDUuPzn4VHm34/eA6kgVPw2nYh+jFdRECqOTTgR2bg9
/YpSQahx+flGJ6LJeBUFoYYVyj2ciMzAoKdfUSoI5WtJO52IxsV4FQWhfJVHpxORnXvpV5QK
Qg3rz9zpRGQjp/QrSgWhhrUA6XQissog/YpSQahh5WKnE5EdgfQrSgWhhi1h6nQismcW6VeU
CkK9x8bjvQ3LgulXlApC+aqbTieiazBeRUGofY7RicjGoulXlApC+Qq+XpyI+iOZYfsVVeo9
Nrbt8CizDJ5+Rakg1Ls9j8Nz9GS8ioJQsafDvdBmL9KvKBWEGrZ4q4cT0f7kzAypINSw8r2H
E5E1G+/pV5QKQvnq0x5OROYL0tOvKBWEGj+rOOhE5H+JmSEVhPK1pD2ciPbZmpmBCkL5++L9
oa/pZLyKglBxdT3Xtw26kqSCUH6tDDoRvXtnpF9RKgg1rv3zi9fHSL+iVBBq2FTACCcie/lp
pF9RKgjlax0GnYjerzbSrygVhPI1fyOciPbn6Ef9VDszFGr8Lo/DoyzjVRSE8tV146BH2WC8
ioJQ75627zTCJehgvIqCUO/RtD1NJ6KD8SoKQvla0kEnovFjvIqCUL5OZxxfZhhHzQzjiJrh
o/y5+jiYGW7GqygI9f62HSdmhoxXURDK8/wIJ6Lm287MQAWhxs86voQTUXuvm5F+RakglD+b
HEd0SfBzj5khFYQatrxo0InovhivoiCUr2MbdCK6b8arKAjl77aMcCIyr72RfkWpIJS/4TEO
dknIeBUFoXyF6wgnIutNMNKvKBWE8jUbg05EdtWlX1EqCOXZboQTkb1sM9KvKBWE2p+w7cxg
rfsiXkVBqH1WhvuQ9XEY6VeUCkL5GrPRIjPYcWqZGagglN/hRtuZwV5+ingVBaHGz38eXujv
RRbxKgpCvcff9sjODPZCT8SrKAg1zCrXFzP5b9yMV1EQyt8w90VA9htPY7yKglC+LmS0nRms
D1DEqygI9V5dtt+2R5m99hXxKgpC+frh0SIzXD/GqygINWx56misGTJeRUGod789Ft/fEWRm
SAWhfOXbaNujzF7ci3gVBaHe7dnx35nB2tFFvIqCUO9ZaXFkhudgvIqCUO704IuA8lPdv/qp
IjN8VJwxT/qBRryKglBxHkdmODNeRUGoYRMUo+/MYM0wI15FQaj9nXpkBrvH9MwMVBBq2BTT
6NtxzN7fj3gVBaH2OdYjM7SH8SoKQr2xbW9nBntFLuJVFITa95LOzHAzXkVBqGETkcPa+fD+
seNVFITaFUePmsGu0541AxWE8jfrfMnC33Y3nIhXURDK1y6OHpnBKpGemYEKQvl61TfeV9TR
GK+iINSwBfij78zg53dnZkgFoXwVrS+F8fvgxXgVBaF8HO1Lk/w3DsarKAjlq/6HtVHz49EZ
r6Ig1LAJ1dEjM7Sb8SoKQvlKEl+OlsdcaoYemeH7F6/IR4/MYJVBz8xABaHcI8kXUrDe3fEq
CkINm1D1l1RZl/QvM4SCUHE0OZqYjFdREMq9bMaImqH/GK+iIJS7lLzxrsLPjFdREGrfqcfO
DDbfEfEqCkK9sW1vZwavXQYzQyoI5a5KY0TNYHlzZM1ABaF2XWqvOPLc3fEqCkK955h9p/5k
vho9r9pQEGrYYxBf2MLzamRmoIJQ47IrbdDxeDJeRUGody/YtmM0YVfayNEEFYR6qwHbh5EZ
RmO8ioJQsd+iZvBzIWsGKgj17gWPIzN0xqsoCLWvlcGa4WC8ioJQe8Q6IjPY3W5kZqCCUHFW
hq/p78d4FQWhhpnEvPHexnExXkVBqPHz6yYyg3/XzAxUEGpYW9Y33lft+WO8ioJQceZHZugP
41UUhIrzODLDPRivoiDUsIdlviyC448zawYqCLXP/POI+/lgvIqCUO7cNM6oGez6P7NmoIJQ
w2xl/PUq1qJnZgYqCOVzcv5Crx+Pk/EqCkL57NcbR2Z4GK+iINTOXWdkBjtbz8wMVBDKPS7G
yZphMl5FQaidg8+oGey8OLNmoIJQvh5vWPOA/FTnqJ/q3FfUR+1xwhmZwUYDZ2YGKgjlbl3j
ZM3QGa+iIJSvRPQXL/+2uw1GvIqCUHuccF5xRQ3GqygI5d5C/sqpn1eD8SoKQrnL1Th/OTsY
8SoKQvlqlXHGaKJnvIqCUHscbY98/Xj8GK+iIFRcK5EZ7D52ZmagglDuozHOp33H/Gn1mEdm
+KhdX58xmmgZr6Ig1DBXz2GtfVjp73gVBaF8xfEbzzzm88sMoSDUPvNn1Ax2vs2sGagg1B7p
TdYMJ+NVFITa+80swjlW2/EqCkLt/Dh3ZvA732RmSAWh3NV1zBhN2Nk6czRBBaHe3PXu6cnM
0BmvoiDUvubN8Jt14o5XURBqXP6XzvHtq3PUfbUzQ6F2Rp2RGVpjvIqCUHFsIjP8bsarKAi1
s4Q9iPYrqjFeRUGoPTs8IzNYVTszM1BBKF97MmZkBj9bMzNQQag9CpuRGWy2bWZmoIJQe1bV
mvvxrrbjVRSE2mPDGZnBKrWZmYEKQvn6+jeO8XljvIqCUHv0MiMzjIxXURDKV/YMawfIDLfj
VRSE8vVf44rMYPXKlZmBCkL5em63V/bjMRmvoiDU3gsXM8NkvIqCUMNMrfy1C44Hr2+eIRSE
2nNAV4unfSfjVRSEevPjey5cUTPYNXRlzUAFodwf0q2oee5e3zxDKAi173BXZAaraq/MDFQQ
as8zXeP+vvm46zePzPBRuy69mBkexqsoCOXuaW8c23gYr6Ig1K6DrsgMI+NVFITas9xXZAZ7
AnFlZqCCUO5y5Sbc+c2vOgdwRWb4qD3Xe0VmsDmVKzMDFYTy55E+VcH5kutXZwevXzztS+o9
x/zncdWejFdREGrYq3fvn/iq8OuuVfgVmeGj9uj+iprBMviVNQMVhPL3Dt7/t0cTvkdyNEEF
oXaev3Zm8FmYi5khFYTac0C/nRlssjviVRSE2ufYL+YZrBr85TwDFYTyJ7F+m/Nx1GC8ioJQ
ezRptwf/5j/GqygINcwO0h8Y8n7+a/V+/ovM8FH7PP5FZrBz4ZeZgQpC7eeRv8gMlj1+mRmo
INSeHbZ05Gd7Z7yKglC76v9FZrD50l9mBioItZ9H/s6yjVO2EZnho/Z5/IvMYE8df5kZqCDU
nnOwspzzojteRUGofRf97czg5/ePmSEVhNqV7C8yQ894FQWhdgX44wzkYLyKglA7S/x+MXN3
MF5FQaj9/OvHmmEwXkVBqH1P/EVm8L+UmYEKQo378p/7NmyiLeJVFIRyZzMvIjia+D15Pw8F
od79ZnuBNcNkvIqCUO6w4//PtzEYr6Ig1L6L3lEzWN68s2agglD7Tn0fT97V7iOvqFAQaleZ
984M/iTtZmZIBaH2rNEdowmrie8cTVBBqP305I7RhJ3Td44mqCDUHrfdPa6oH+NVFITaT63v
yAxWS9yZGaggVOy3yAz+XTMzUEGoPca9IzPYCPnOzEAFodyp1M3j7Dcsx9wn77VUEMo9KN2K
wc+Si/EqCkL5em5fjuhnycN4FQWh/ND76e/bmIxXURBq/PzsueJJ3GS8ioJQ76bsPN6ZodtI
/2ZmSAWhhtlzjjsyg80/3ZkZqCDUMLtUX0Ts36MxXkVBqGEvYr/x/M6rO6vwUBBqv9twMzNM
xqsoCLWrzDsyg3+/zAxUEGqfMU9kBrsinswMVBBqn8cPM8PDeBUFofbV9URmuB/GqygItavM
JzKDPc18MjNQQah9jj2RGWx89WRmoIJQ+y2bJzKD5ZgnMwMVhNqV7BOZ4TgZr6Ig1M5dT2QG
u2s/mRmoINT7nWwvMDNMxqsoCLWfsT3MDJPxKgpC7RHrc37j8+es4/OHmSGp+ISRGbx/VGYG
Kgi1n7c8kRl+Ga+iINS+7z7MDD/GqygItZ8oP5EZ+mS8ioJQ+87wRGawO9GTmYEKQu2nJ88v
ZgcvxqsoCOV+Ob5oleOoJzMDFYSKPX1HpX8zXkVBqDj+T7y982O8ioJQu354IjNYLflkZqCC
UP70/TxiNPEegYhXURDKa983jrFzxqsoCOUVoC9gjBou4lUUhHqHOvefvkTbxziD8SoKQvkT
M2/iGOOoiFdREMqfOvgCX/uN99KPeBUFobwif+N4EnczXkVBKB8h+YKgGBVFvIqCUMMaVbzx
3ka7Ga+iIJSP9M7jjEq/MV5FQahhSy7fOJ7EDcarKAjl9xJfHOJn4sV4FQWhfMbzjeOJ4sV4
FQWhfFTsi1ZjlBrxKgpC+Tsavnzhb/upY8SrKAjlWfs8IjP4Uc7MQAWhvOD3xZ5xr414FQWh
vMOAL/XIs+TOWbVQEMpnbr3BYsxGRbyKglB+v/KlHpEZIl5FQag4mjHPMG7GqygI5ePoN445
/R/jVRSE8ikmbwLs1+BkvIqCUPt6bDsz2Igj4lUUhPKJFl964/ePm/EqCkL5LJ5fPH6P+jFe
RUEov1/5g2/7DTu/GzNDKgjlUzNvHDN3Ga+iIJRPMXky8717M15FQah3vx1/+mvNMUcW8SoK
Qvk6Jn/lOJ4CRLyKglD+NrY/Ko+xQcSrKAj1ZiI7mlEzHBfjVRSE8m5wPh0W96iIV1EQalyH
fdorx+cRr6Ig1L77tKgZroPxKgpC+ZNxfyAWo7uIV1EQKs6YyAzPzXgVBaF8rO63PJs16D/G
qygI5dNYfvF4vdsYr6Ig1DuysHhnhuF7hJkhFYTy9wj9Ubn/xsl4FQWhvEOND/f9m2e8ioJQ
Pv708tm30RmvoiCUz8n5I5uo+iJeRUEof/vXH4L6dX4xXkVBKPfy90ls7t2emYEKQvlT6/cD
5Pg84lUUhNq5q0dmsL3eMzNQQSivGb1Qze+RmYEKQrkP09l3ZhjvZiNeRUEon27wQtV+w+4S
nZkhFYTymUL/kr6vDsarKAjl7s0+1MhPxcyQCkIN6w35xntWrd+MV1EQyt03fSjuZ2JjvIqC
UOP28y0yg90re2YGKgjlIwsfzsR4MOJVFIRyR8k3nt822CM3FYTaGbVHzXD/GK+iIJRPlflE
h19RB+NVFIRyd3O/QL2SuRivoiBUnMdPPj+PeBUFoXwq+Y3zbdyIV1EQyt8w9kTjV1RjvIqC
UD7GfePYxsl4FQWh/KnDOVrcawfjVRSE8ocab7yr8GcwXkVBKH/ryU9sVvqj10p/xGjio957
e//TT2zWiUNGEyNqho/yB1nnGPGmbGe8ioJQ/qbbG8fqmsl4FQWhYntnPqOPeBUFofzZ1Dli
NGF3vpGjCSoI5c90zjFbnu1j5px+KAjl3cfOMfMZfcSrKAi1z8rBmuFivIqCULtaHpxnOBmv
oiDUrgbGL9/GjXgVBaH2mR/ds7vd87N7dioI5f1NzuyenfEqCkLFd4qawe7BI2sGKgjl7z2/
cdxrG+NVFITymdtz98X2pHeye/anINS+X43IDL53MjNQQSh/G+I8j+9+fh71fr67Z1dq39vP
484jeB53OYLncWcFcEZXPKvIz5azaufZyqzaeUZm+Chf83WeUTPYePfMmoEKQu364Yyawe4S
Z9YMVBDK1wW88S9z4tnzGX0oCOVPrc/dF3ufSeye/SkI5fOw5+6LvSsqds/+FITyTlTnGaMJ
u8+fOZqgglDvfrNPe8bY+cd4FQWhdg7efbH3yIndsz8FoXYNf0ZmsPPtzMxABaF8JfN5Xt8c
wHnVOYAzMsNH7TmHk88mbsarKAjljzvP3Rfbn72d7J79KQjlz27PMzKD3Y/PzAxUEMofXp5n
ZAY/ypkZqCCUPwY5z8gMlpvPzAxUEMqfnpxnZAb/rpkZqCDUrrXOyAw24jgzM1BBKJ+tP8/I
DDZaOjMzUEEofyJwzsgMtndmZgYqCOVzpOeMzHD+GK+iIJS7N58zMoNVnDMzAxWE2jXjbPm0
75yZGagglL8ndc5ettFlG5EZPmrXc7svthc3J7tnfwpCeQ/Hc0ZmsFmYmZmBCkL9/5R9y851
uW7cvJ+ih8nAztaF6zINEBgZxj5vEFgBgqaBHBjI62cVyaJEIBPj4KBZ+69v7yUtibpRLJ+R
S3iGV2ivA2lh+buR8Azw5pKegUgLy86/pszdo2SePUrCM2zWgCzklPAMGB8lPQORFpavRSQ8
w5P2OpAWlvcuCc9gn6dnINLCshOB6brY3uuonr2RFpZ7IgnPgFFb0jMQaWH5zMl1se1m16R6
9kZaWD4vlVhN2DvL1QSRFpaPV66LbTFak+rZG2lh+SgqnDNM2utAWljRH8MzWAtNz0CkheV+
RcIzWGtNz0CkhWUZ7afrYtvp6aR69kZaWKZMPK/wDPBKV3oGIi0sH+Euzhku2utAWljeH6+W
EULzSs9ApIXlfd51sX2NQvXsjbSw7Ox2XjFnGGmvA2lh2Q3geYVnQN+80jMQaWFZVPm8jjnD
VeYMV8wZNsuCX6brYntLonr2RlpYdjY1r/AM9uTpGYi0sL63ic/DM1yT9jqQFpZ7iSs8w5y0
14G0sOxO5De0x/r8or0OpIXlOzqui+2nEVTP3kgLy2eZV3gGjBJXegYiLayo6fAM6DdXegYi
Lax4m7efks2014G0sLwHuy62nwhSPXsjLayot/AMGPOv9AxEWlg+971in8FqJPcZiLSwLCZ5
Xm/co2+014G0sHw/wHWxfXVG9eyNtLAsCm26Lrafw1A9eyMtLB+vXBfb4gsn1bM30sLy9c7d
7mwld8v1eSAtLJ+Ruy623VCbVM/eSAvLa9p1se2keVI9eyMtLG+V97HPcJd9hjs8w2ZZHMi8
uc/wo70OpIXlu8Oui+2nQ1TP3kgLy/es78Mz3MUz3JwzJMuiAucd+wxoC3fuMxBpYdlN/3lz
NfHQXgfSwvKzQtfF9n5K9eyNtLDs3sy8wzNgv+NOz0CkhRXvhp7hpb0OpIXl/fGO1QRGjDtX
E0RaWD5Hue/MizPv9AxEWlgWqTDv8AwY+e70DERaWD5euS625fqaVM/eSAvLVy93eAbjpGcg
0sLyWeb97l21+z131Vw9+2SZps18wjM8aa8DaWGNB3tAT3gGtNYnPQORFtaAEPF8uJrotNeB
tLBM+Wi6LravfamevZEWls8fnvAMqMMnPQORFpbFlM0nPMPXAeaTnoFIC8tiFecTngG1/qRn
INLC8tW962JPqCVOqmdvpIXl7/8Jz3CnvQ6kheW7w66L7TNcqmdvpIX11QI+l7wlNJ+cMxBp
Yfnul+ti++431bM30sLyNdVz7TP6J+cMRFpYHgHzhGfAeduTnoFICyvqLXYg4Zupnr2RFpbP
4V0X245XJ9WzN9LC8t2WJzzDddFeB9LC8mih58k4/fmkZyDSwvLIkSc8g/WC9AxEWliWu2+6
LraP+VTP3kgLywL853N4hqd4hlDPPlh202a+4Rnwzt70DERaWD5HecMzvI32OpAWlkcRuC62
HZBPqmdvpIXls8y3ZQz9fHPOQKSF5SfKLz3Dj/Y6kBaWZUWYb3gG+LE3PQORFpZFBc53xM2X
H+11IC0sP3VwXWwLOZlUz95IC8v33t/wDBgf3/QMRFpYHjPzhmeA53vTMxBpYVmOg/ma9oQF
24S9DqSFNS4rk3sGJE6bVM/eSAvL56UvPUPa60BaWJbncL7hGdAL3vQMRFpY8TavN33ie2Wc
fiAtrAEXP10X2/ciqJ69kRaWZX6brovtfpPq2RtpYfm+xhueAbttb3oGIi0sn2W+z5Oj2vvk
WBtIC8vnc294BszU3vQMRFpY0SrDM2Bf603PQKSFZbd55Bee4fNj8kvPQKSFZTOnz44eddNe
B9LCsnym8gvP8PvRXgfSwrI8ufILz/CVT37pGYi0sGxGLj96hkl7HUgLy84Q5BeeYby014G0
sOx+nPzCMzShvQ6khWV77+K62JZxV6ievZEWVtQbPcNLex1IC8vi1uQXnuGbGcgvPQORFpat
vMV1se00W6ievZEWls1L5RdzhkdorwNpYVmfl9+VO3fyu46dO/ltzxD/YmOJ/MIzXJ32OpAW
lu1MyS88w/2jvQ6khWUrC/lxzvDQXgfSwrL8Z/KLOYO1pJwzEGlh2Z6c/GIHckza60BaWHbd
S37hGeyb0jMQaWHZvob8wjNYradnINLC+t4/3iw9w0V7HUgLy6J/pXHO8NBeB9LCstzh0sIz
tJf2OpAWll3flkbP0GivA2lhWdyBNHqGH+11IC2sgS0maeEZ0E9begYiLSyLMJYW2jXf/Eha
atcQaWFZlL80zhk67XUgLSz3XS08w2y014G0sNyvtPAM8M0tPQORFpZF5orrYtuKQ6ievZEW
lo0l0sIzjIf2OpAWls3hxXWxLdOgUD17Iy0sb5Ut9hnQs1vuMxBpYVn2E3FdbLu/IVTP3kgL
y3a/xHWxLa5CqJ69kRaWzZal3ZmVS1p6BiItLNsJkRZzBnuzOWcg0sKyPSBxXWw73xOqZ2+k
hWXzB3Fd7Am1XaF69kZaWLbeEdfFjm99y2+EZ9gsi/cS18W2yGOhevZGWli2aySui+3vjOrZ
G2lh2XpHXBfbIl2F6tkbaWHZjQhxXWxbXwvVszfSwrIISunhGTDy9fQMRFpYdsFYeo/bNTft
dSAtLK9p18W2cEKhevZGWlh2RVxcF9tCL4Xq2RtpYdmNU+mxz4D5Uc99BiItLIualT5/u3ap
UJFIC8vuPovrYpMj5S9iDyBZPiZ2yZ076XLs3EmoZx+s+GuRXfL0DERaWHY9VbrsHtXl7FHd
FSoOlu0nSw/PgFlbT89ApIU1IJ8h/cqsXNLTMxBpYVnsqPRYTcCP9VxNEGlh2cpC+p133MNe
B9LCsj056fQMk/Y6kBaW3WqVHp7BniM9A5EWlkVpSqdnSHsdSAtrQM5EengGeI+enoFIC8vn
jCM8A2YGIz0DkRaWrXdkhGdAuxjpGYi0sLzlj/AM6BEjPQORFpadFcqIHUisUUbuQBJpYX21
gL8Oz4A1w0jPQKSFZZf8ZYRnQP8f6RmItLDcz4/wDENorwNpYdn+jAzuQArtdSAtLG/5IzyD
1Wd6BiItLNtVlRGe4b1orwNpYVkUgYzwDPbb6RmItLC+doy/Ds/gHCl/4b+xWVHT4Rlk0l4H
0sKyaDoZ9Ayd9jqQFpbpV8vgnOGivQ6khTUezFFGeAZ7s+kZiLSwvK8Meoab9jqQFpZFMct4
8oxeRnoGIi0s2+WWEZ4BvXmkZyDSwrI7XzLCM1j50jMQaWGZ9rq4LrblrxKqZ2+khWVnCDLD
M8B7zPQMRFpYplkuMzzD91Jlpmcg0sIa2BKXGZ4Bs9qZnoFIC+uzBXZm5RKqZ2+khWXa0jLD
MxgnPQORFpadTYnrYvtqgOrZG2lh+exsxmpipL0OpIVlZ4UyQ7sGvnKmdg2RFpbdgpEZqlbo
ETNVrYi0sOz8S2asJuDBZ64miLSwfD/AdbF9RU717I20sEzZXlwX2+dgVM/eSAvL19GTc4ZG
ex1IC8sSO8i8MnpHZnoGIi0si0mWGZ5h2+tAWlgWySOTChUX7XUgLawBcSuZ4Rkwd5npGYi0
sAY26mWGZ8A+ykzPQKSF9fV2/HZ4BitregYiLSy7HC8zFCqw4pipUEGkhfX9Hr4pPAN2k2Z6
BiItLEuCIfLb47n8zvE81LMPliUMEYl9hueivQ6khWU3bURa3nwJex1IC8s9Uahn2y5Mqmcn
0sKy2B9xXWxfX1M9eyMtLIvSFOl75076uXMX6tkH62sxsEO7BuOxpHYNkRbW9zZRh0OyR6V6
diItLB93JTwD1leSnoFIC2s8Vr6YM2B1lurZibSw7H6cSGjX3GmvA2lh+VgiktE7IqldQ6SF
5XvWIpnFQyT17oi0sHwXL9SzcU4pqZ6dSAsr3mZo11itp3YNkRZW1FuoWtlvp6oVkRaWr6lC
PRsCH5Lq2Ym0sHwOH+rZtruX6tmJtLC+3zM7ynHTXgfSwvr6I347VK2wckr17ERaWO61Qz3b
W2vq3RFpYVlqJwn1bBsxUj07kRaWpUSSi57hob0OpIXlO1Ohno0TQUn17ERaWL5iDfVsbAVJ
qmcn0sLy2XKoZ1sfSvXsRFpY3ipDPbvZN6VnINLC8ll/qGfj/FtSPTuRFpZFHkqoZyMmSFI9
O5EWlu/1hno28vpLqmcn0sKy2B8J9WycZkuqZyfSwrLcfXJtVSu5TlUrCfXsg2WnWZLq2YP2
OpAWlsWtyUUlzJv2OpAWlvv5UM/2t5yegUgLy2c1oZ6NrPCS6tmJtLDsDoWEejZiGCXVsxNp
Ydk9DbnoGRrtdSAtLItJlusZ+53nnIFIC8tP5a5QtcKePNWzN9LCshSgcoVn6GmvA2lh2b19
ucIzYMS40jMQaWFZYlK5QyP3vmmvA2lhWXpOuUMjFx6c6tkbaWENBGjKTb27tNeBtLC8Fqie
jXnwVs8m0sJyvxLq2VbWVM9OpIU17ma29yi8s1TPTqSFNVAcCfVsa9+pnp1IC2ugsQjVs9+X
9jqQFpYpPQrVs7GbsNWzibSwTP1WQj27YSRK9exEWlh+skH1bKyWtno2kRaWxZrITc/w0l4H
0sKyaFO56Rk67XUgLSzfsw717AZfmerZibSw3NvdVMJMex1IC8tXeqGejYw+kurZibSw7P6o
hHo2Duck1bMTaWHZHQq5QyPX2nRq5BJpYVk8i1A922ok1bOJtLBMF0JCPdvmR6menUgLyyK+
JdSzm9VhegYiLSw/dXhCuwYj6pPaNURaWD4yhHo2jsEk1bMTaWH5KPpQI/ehvQ6kheWnJ6Ge
DQ1PSfXsRFpY8YRUwkx7HUgLy/f3n8MzPMUzPNS7S5af44V6tq36Uz07kRaWpfqVUM9uv057
HUgLy/3jE9o12G17UruGSAvLT2JDPRuRSpLq2Ym0sLxVPvQMaa8DaWF9rRJPeMwZinq2UD17
syx7lhzq2VLUs4Xq2ZtlkVUS6tnmzVM9O5EW1rjsbYZ6NvzmVs8m0sIy9XShejbiHLZ6NpEW
1risVYZnsLaXnoFIC8vUuoXq2VY72zME0sKye/tC9WyMXVs9m0gLy5RQherZ2Lnf6tlEWlgW
Gyepnt1orwNpYX1t7Pu9UM9umEukenYiLSzfL6N69nPRXgfSwrK8FkL17DvtdSAtLPfzVM/G
unSrZxNpYXnsD9Wz7057HUgLy2OYqJ6NE4+tnk2khWU3soXq2ZhxbvVsIi0s0ygTqmfPtNeB
tLBov+nbt3o2kRaWj7tUz8bYtdWzibSwohZiNYFZ21bPJtLC8lgsqmdjJNrq2URaWAMTfgn1
7N/TaK8DaWGNy8rnngFBXJLq2Ym0sCwGVl56hpv2OpAWVtQbPUPa60BaWJZHQUI923p2qmcn
0sKym5oS6tnmb1I9O5EWlsd7UT0bsUZbPZtIC8vy6kmoZ3vt0DMk0sKySGkJ9exfb7TXgbSw
LC7nonr2m/Y6kBbWwJWyK9SzkVLxSvXsRFpYNl5doZ6N1JBXqmcn0sKi7bPw9tJeB9LCsnH3
CvVs1M6V6tmJtLBM5uAK9ezf55WuVM9OpIVl9XaFevZvCO11IC0si62+Qj0b49iV6tmJtLDs
bV6hnv17LtrrQFpYFot1UT37J7TXgbSwLJfJRfXsnvY6kBaWtePr5woV3i6oUJFIC8siq65Q
z/7dD+11IC0syxRzhXo2PrpSPTuRFlb8dXiG+6K9DqSFFe34jvG8014H0sKyWxcX1bOtLaTe
HZEWlsUqXlTPHoP2OpAWlt03uaieLWmvA2lhfb4Lf+0KFZgZhr0OpIVlfv76UQlz0l4H0sLy
FtPoGQbtdSAtLIvAv0I929peqmcn0sL67K8OW8v1edjrQFpYNi+9Qj3b3nKqZ/8H/+Jf/vj9
if/98z+F8ff/9cf/+aO5Hf/5n/rnf/3bH//ln58/vzr62/qI7c9/aN8/9Dn+8fumOf8RaYH/
pn/8p//+b//+r3//t3/9939o//lv//uP//a3P/6HfW3D13ac5N94+5aA+f3z7//6x4p//n7+
//fP//KHhR83z1ckv69FtshqhG25b5Zg7wWX+MJeB9LKws53i3xFXzXRXgfSwho4YGyRiej9
xuLGfEUbaWF17JW2yEQ070Z7HUgLqyOFZhuWo6y/xolMZhtpYTWE7TfPRNQfe9q4R7iRVtbv
G+ObZyLqOBlqzFe0kVYWBqDmmYj6+43LjfmKNtLCapjYfLb/xiW014G0sBomT80zEXVEKTXm
K9pIKwtB+M0zEXVEQjXmK9pIC6shwXXzTEQdl/ga8xVtpJX1++EJu/9Gv2ivA2lhNUy3mmci
6oj0aMxXtJEWVnv989trV2ivA2lhNaQPb56JqONkqDFf0UZaWO39Ou9n229AaSDsdSAtrIbT
ueaZiPpjbznuEW6khdVwIts8E1FHbEhjvqKNtLDaY59bvpGOmKPGfEUbaWG1xz/337hv2utA
WlgN0/jmmYg6Ljw25ivaSCvr1/BurM93bEE05ivaSCvrB7/imYg6rmc15ivaSCsL6aqbZyLq
r31TeIaNtLJ+1m/shmDHGX5jvqKNtLC+Po/fC8/QOu11IK2sn/Wu8Azvj/Y6kFYWRtbmmYi8
ZzNf0UZaWbhM0DwT0ffknfY6kFYW0m43Cc8wL9rrQFpZVm8SngFvQNIzEGllISV2k/AM/aW9
DqSV9UPv8kxE7jeZr2gjrSwk6m4SnuFOex1IKwvJwJtnIuqIAWvMV7SRVtbvwdOGZ7CnTc9A
pJWFKXbzTEQdMauN+Yo20srCKXPzTEQdwhKN+Yo20srCfYTmmYg6Lus25ivaSCsL16WaZyLq
iO9tzFe0kVYW5qrNMxFF27vYa4m0snBG2TwTkY9jzFe0kVYW7pQ2z0TUsZXSmK9oI60spPZu
ErOBd9JeB9LKwtle80xE3uuYr2gjrSyvt/AMbdBeB9LK6va03udt7sJ8RRtpZeEaRfNMRB3y
I435ijbSykK4e/NMRN18DPMVbaSVhQjUdoVnwJu90jMQaWUhW0nzTEQdG1WN+Yo20srCnLt5
JqLvydNeB9LKwkld80xE8RxxW2gjrSzEvzfPRNQhd9GYr2gjrSxccWieiegbMR7a60BaWc3q
LTzDm/Y6kFYWIiSaZyLquBDcmK9oI62sZmXyPv/CVzJf0UZaWcg6367wDCK014G0sqx3eSai
juvWjfmKNtLK8vfvfR4XacNeB9LKsv4YmYh+7aK9DqSF1RFP2q7wDM9Fex1IKwvZrlpkIsJu
TGO+oo20sDou9LQr5gz2HDlnINLKavD5V3gGzLuu9AxEWlm4bNOu8Az2ZtMzEGllIe6vXeEZ
MKJe6RmItLKwY9yu8Ay/i/Y6kFZWh++KTEQ/zDiZr2gjLayOCO12h2eAj7nTMxBpZeHqTLvD
M6Csd3oGIq2s9pj9pBe9t2cIpJWFWJ12h2fAm73TMxBpZflfh2cYP9rrQFpZiJdrd3iGkfY6
kFYWTiLaHasJK2uuJoi0svwJwzO8g/Y6kFYW7ja1yET0w5jPfEUbaWF13P1rkYnIZs7MV7SR
FlZHru8WmYhwIbgxX9FGWlifjb/2G4K40t2Yr2gjLayOSPPmmYjcNzNf0UZaWYixbzc9w4/2
OpBW1hj4pvAMvdFeB9LC+poxntZvCGKTtTFf0UZaWL1jVhOZiLwPhWfYSAurdyuf5xv5Wft+
+BtEWli929OGZ8DOy52egUgry7ydZyLyVQ3zFW2klYVTm/bEnAGj9pNzBiKtLAgLtIdzhkl7
HUgrCxHaLTIRYSu+MV/RRlpYHXHjzTMRfT3ipr0OpJWFyOb2hGdAm37SMxBpZQ282chEhC3s
xnxFG2lhdVy2aZGJyFZ9zFe0kRZWx+WOFpmIGkZX5ivaSAurT/jgyERkHpz5ijbSwurjNtt/
AysZ5ivaSAvr+z3Um3uGZmWlZ0ikhUVb/C9u2utAWlifm4cdnuGetNeBtLDi3YRnwOrsSc9A
pJVlnigyEfk7u3/nG7x/6a/8X/qEJ4pMRLZaYr6ijbSwOi6ptMhE1OzN0jMk0sL63j++yT0D
tn4b8xVtpIXVp9WhewacgzfmK9pIC6tPazF+DwiiKI35ijbSwvocqn1upw82zjNf0UZaWJ+T
+P46MhEhTr0xX9FGWlhdsHqJTESI9W3MV7SRFlafaAuRiQin8435ijbSwvoeFt/kNwSRUa0x
X9FGWlhd8G4iExHuGjbmK9pIC+vrXQ32nX2Q+Yo20sL66g1lcs+ATPphrwNpYX31NmBbr4Ve
aGO+oo20sL6/xhO6Z+hWVnqGRFpYXdAfIxORrQCYr2gjLazP/tr0654B987CXgfSwuqC/eTI
RNQxjjFf0UZaWB2bBy0yEeGWZWO+oo20sDquOLTIRBQcKX/hv7FZn42/vuM3Ju11IC2sjlD0
FpmIurVWeoZEWlhfLaCm3TMgD3tjvqKNtLD6hTl8ZCKCKEpjvqKNtLD6ZW/WPcPAavmlZ0ik
hdVve0/uGQbWQcxXtJEWVsfCpUUmomHlo2dIpIXVr+9F9shEBAGZ/kvPQKSF1a+7/2lb9lHy
sNeBtLA6YpN7ZCLCje3OfEUbaWF1aJX1yETk30rPkEgLqyM2oEcmItx67b/0DERaWB0B2T0y
EeFqeme+oo20sDqyh/TIRITW2pmvaCMtrI5b0z0yEfmTp2cg0sLqiJjukYkId3H7Lz0DkRbW
Vyaz/Tek014H0sLq2G7okYkIt+E68xVtpIXVkaejRyYiXALvzFe0kRZWR8R0j0xEUOXov/QM
RFpYHTFAPTIRjd9Dex1IC+urN/sm71E97XUgLaz46+0Z+u/0DN3zFZ2sjpj3HpmIsE7sv/QM
RFpYHQHZPTIRQXu4/9IzEGlhdcTn9MhEhAvznfmKNtLC6re10PAMY9JeB9LC+lolfi/mDPYG
cs5ApIXVccO8RyYiCPp05ivaSAur4zZ+j0xE1i6Yr2gjLayOZUiPTET+rfQMibSwOhZ5PTIR
DTw58xVtpIXVEWTcIxMRZs6d+Yo20sLquCHYIxPRkJv2OpAW1jdo4/fcMwz7nJ4hkRZWR6ht
j0xE/uT0DIm0sDpu4/fIRITj7s58RRtpYdn5To9MRLjM3pmvaCMtrI7TxR6ZiGb/0V4H0sLq
WCL0yEQ0x4/2OpAWVofEd49MRBP+n/mKNtLC6rhB2yMTEa73duYr2kgL63vCBvv137hprwNp
YXVM33tkIvJ3Rs+QSAur4xZ7j0xEOPrszFe0kRZWhyh4j0xE82m014G0sKLlh2ew1pOegUgL
62tjKJ97Bhz0d+Yr2kgLqz9Wvpgz3A/tdSAtLDtX75GJaP4a7XUgLayOQOYemYgg9dV7egYi
LayOe4s9MhFhr6b39AxEWlgdIaq90zMM2utAWlhfmb421sMzzLTXgbSw7ISuRyYiBKn0np6B
SAurv1Yj4RkwJ+rpGYi0sOy8rUcmIhvHenoGIi0sO1e3DRT7i0Z7HUgLy2IpemQiwq5I7+kZ
iLSw3KNGJiIoKPaecwYiLayOCws9MhEN+IKecwYiLayOrZne3TMMzAY7PUMiLawok3sGCMJ1
5ivaSAuLf+1zBozBPecMRFpYHVsaPTIRjW2vA2lhdWwr9h5zBvShnnMGIi0sO8ftkYloYHxk
vqKNtLB8ZIhMRAPzx56egUgLy+KkemQiGpip9ZwzEGlh+VgSmYgGfHNPz0CkhdWxpdEjE9Hs
aa8DaWFZlFWPTET2rSM9A5EW1vds3+9FJiIkxujMV7SRFpadLvfIRITUJp35ijbSwoon9BuC
SFTSma9oIy0sO+3vkYlooP+P9AxEWlhfn8fvuWeY214H0sKyc/UemYjG22mvA2lhdVxr6ZGJ
CIF7nfmKNtLC6tia6ZGJaGL2yXxFG2lhdeSe6OOYM4wyZ/B8RSfL5w+RiWjCm4+cMxBpYbkP
jkxENq9gvqKNtLD6YzUScwa06ZFzBiItrKi3mDNg9jFyzkCkhdVxw7xHJiL8bB/pGYi0sLyv
RCai4Z/nTD+QFpb34MhEhGC0PnLOQKSF1ZGno0cmIkhe9pGegUgLq79W65wzNNrrQFpYHVt+
PTIRYYe1M1/RRlpY3mIm5wyT9jqQFpbPOCIT0fjcS5/pGYi0sLyNRSYifEmf6RmItLC8z0cm
IoTIdeYr2kgLq79Yt0cmool+M9MzEGlhfX+Nb3LPgP905ivaSAurI314j0xEE/5/pmcg0sKy
888emYiQlqczX9FGWlhRpvnbTzV/51O5ZzhYdh7dIxORzdRnegYiLSyfw0cmomlPm56BSAsr
nlBipp/2OpAWlp3d98hEZN58pmcg0sKyiJsemYjM38z0DERaWHZ23+d1/MZVfiM8w2b57Cwy
EcFZdOYr2kgLi7b3WmtJ6RmItLCir4RnwKg00zMQaWF1XNzrkYnIewQ9QyItrO/38HnMGTCj
mjlnINLC6ki13iMTERpOn+kZiLSwPvvrwZGJaGI/SNIzEGlhWdRCj0xENuYzX9FGWlnYCrBj
gc8WjCtCz5BIKwuXVHpkIhLMzpmvaCOtrB9mHJGJSNALmK9oI60sbHz1yESEQMrOfEUbaWXh
mlGX8AzYJ5D0DERaWVis9shEdGHEYL6ijbSysI3VIxMRfrYzX9FGWlk/ezfuGWQ+tNeBtLJ+
9m7cM4i9ZXqGRFpZiAPqkYloYqUv6RmItLKwudYjExFeUWe+oo20sn7YG4hMRAie7cxXtJEW
VselOjtos/fx0l4H0sr6WY24ZxCM2sxXtJFWFu6B9chEJFgtM1/RRlpZP2tv4RkwVkp6BiKt
LERG9MhEhODZznxFG2ll/dCbIxORt4uXPYpIKwuXhnpkIrowBjNf0UZaWcgO3iMTkfUI5iva
SCsLmRJ6ZCJC0GlnvqKNtLJwqa5HJiKB/2e+oo20srCV3CMTkWAWfaVnINLKwqZtj0xECL3s
zFe0kVYW4oV7ZCJCwq5+pWcg0sqyFhOZiHBu2JmvaCOtLNyy65GJCMGznfmKNtLKQox4j0xE
CJjuV3oGIq0s3GnpkYlI2k17HUgryzxqZCLCaWZnvqKNtLJwObBHJiLc5e/MV7SRVhaOQXpk
IvI3QM+QSCvrh3lXZCK64KGYr2gjrSwcnPTIRHTBKzFf0UZaWB0Hiz0yEaEj9ys9A5FWFq4T
9shEhHPcfqVnINLC+ualqEPv8/7O6BkSaWXhIKtHJiKceXfmK9pIC8uiW3tkIpL2o70OpJWF
47UemYgEO8XMV7SRFpbFw/abnmHQXgfSyvrBx0QmIvkN2utAWljf/OF7/5GJyEalOz0DkVaW
tfzIRGR96E7PQKSVZd4uMhFd9uTpGYi0snDTtUcmIgwQnfmKNtLCsrjeHpmIJtYlzFe0kVaW
tfzIRGRe8E7PQKSV9bOnDc+A8fFOz0CklYWj4R6ZiGwEZ76ijbSwOq6898hEZPvlzFe0kRaW
zzIjE9FEa71zzkCklWVje2QiEufQ+xBpZeFed49MRIJ9RuYr2kgrC9HxPTIRIYlhZ76ijbSy
cBW2RyYi69l3egYirSzEGvXIRHTZ09IzJNLKQlaifodnsHaRnoFIKwt5pXpkIhL/nL2WSCsL
OW16ZCKynn2nZyDSymrWV2LOYL0u5wxEWlm43dyf8AwY85/0DERaWTg+6JGJSLCb8KRnINLK
QsbSHpmIrH0/6RmItLIQD9kjExEuRnTmK9pIK6tj7HpiNYFZ25OrCSKtLDuPjkxEmAL3Jz0D
kVaWlymyCsALMl/RRlpZUPDuzETkn3M1QaSVhawrdt0q/4KeIZFWVrc6ZI6yH+11IK0sHFH0
yERk0RfMV7SRVhaiZjszEVnt5JyBSCsL0didmYjuSXsdSCur2/uPTERYnTFf0UZaWYjL6pGJ
CBPB/uScgUgrC9nzOzMRPWmvA2llWWwLMxFhZvCkZyDSyvInZI6yi/Y6kFZWhz9mJiL7VnqG
RFpZtjPJTET2zugZEmllDWuhzER0014H0srC/YYemYgwae7MV7SRVhaiTXtmInpprwNpZdkJ
HTMR4RyX+Yo20spCvF9nJqKW9jqQVhaiyntkIrK4LOYr2kgra6DPRyYiTB078xVtpJWFqLce
mYhwnam/6RmItLLGzz6PTERprwNpZeHIqL/MUSa014G0siC20iMTkbW9Nz0DkVaW9eDIRIQc
Kp35ijbSysIxYY9MRMgG15mvaCOtLOvzzERkNSLsUURaWR2rsJeeYdBeB9LK8lYZngG94E3P
QKSVhdtV/aVnGLTXgbSyOlavkYnIIqCYr2gjrSwcAHVmInrSXgfSyjK/wkxE9k3bMwTSyjK/
kpmIXtrrQFpZdubNTETW697stYG0snBAOpiJ6OtD45eegUgrC084mInoemivA2llIU/9YCai
lvY6kFYWMsgOZiL6fMFgvqKNtLJwEj9+zFE2aa8DaWUh8nREJiLElw3mK9pIKwvRFyMyEUH7
aTBf0UZaWcPKN6JHpb0OpJWFkWFkJiKhvQ6klTW+lcX4MUfZj/Y6kFbW9+d/jh8zHgvtdSCt
LBzhjV94hktorwNpZX1/DjuyBKW9DqSV9XXhz45MRPaW6RkSaWXhoHcwE5H8aK8DaWUhomD8
QiXBap2eIZFWFqIvBjMRvQ/tdSCtLIRnjMxEdNFeB9LKGlbrkYnouWmvA2ll4ZR8/CIXekt7
HUgr61u+wnbP8N6014G0shDhMZiJ6BuVBvMVbaSV9S0tYV/0iaPlnIFIK2t8I+pooZKAJ2/0
DIm0suxtesYhb63MV7SRVtbn6T47PMNPaK8DaWUhJmQ05jUdtNeBtLIwOxstPAP6f0vPQKSV
NZ4JO3pUo70OpJU14WNaZC98Ou11IK0sHD/bhaC/PE992OtAWlk42RotPMOd9jqQVtYQfFPk
KMOI0YS9lkgry99/eIaR9jqQVhaiYT4fGdkLO+11IK0snDSOxlzoaa8DaWUNa9ORo8za9J29
NpBWlvWVFp5hDNrrQFpZCGX5lnv+G/AYLT0DkVYWIoHtQpD9xk17HUgrC0mtRoscZdaSXvZa
Iq0s812Nc4a014G0snDy+w2+/hufewl7HUgrC5ERNsCz5D09A5FW1vjWcN88xXvUN1MLex1I
K2s89rlkS+zpGYi0ssaF3wvPIGmvA2ll4babLUI54vT0DERaWcN+u3uP6mmvA2ll2Sja6RnS
XgfSyrI21pnX9KK9DqSVZS2mc87w0l4H0srq9manz8IxKrm9DqSV9VX1n7a8ML87aK8DaWWZ
1+6xmoDn67maINLK+lr9n7YU+8vX12GvA2llIV58QFLNSj5prwNpZSH12Tf1j1770l4H0sqa
3ewYzy/a60BaWYjG/+Zb/huYd/X0DERaWcPa2+M96tdprwNpZWHf1ybAf3nuw7DXgbSyzD92
Zi+8aa8DaWVNzLUHsxf+aK8DaWWZJ/qmgF6Oh/Y6kFbWQFa/0fZ4Pto5no/wDAfLxpIRnuH3
o70OpJVlfWWEZ8DsY6RnINLKQiCdhTty9ur2OpBWlrX8EZ5h2+tAWlnfbPxPu+RiraTRXgfS
yuqv2ZFz9Ed7HUgra1ith2f4vbTXgbSybEwc3udv9LpBz5BIK8ta5QjPYPWZnoFIK8tm/YNz
hkZ7HUgry+Zag3lNH9rrQFpZ2C+zqf9fsZId9AyJtLK8FsIzbHsdSCvLnzAyHmPlNO78jUBa
WUij+LWB8Aw37XUgrSzz2uOJ9flLex1IKwsZJL6vaLt/pGcg0sqyMXG8uXMX9jqQVpaNVzM8
A75ppmcg0spCpKMFrLJ/zPQMRFpZ1rtmZCl9B+11IK0sNEgLtfrLs+2GvQ6klYXOa8G9f/le
XdjrQFpZ9jZnj527tNeBtLJsrjXDM/yE9jqQVpY/YXgGrPRnegYirSxE43/2m5565pyBSCsL
XfHr8t6jsB/k9jqQVpatXiY9Q6O9DqSVZXPfSc8waa8DaWUNjEQzPMN90V4H0srCjZjP13uP
wvrB7XUgraxh3xRzBum014G0smz0mZwz3LTXgbSybDYwvc/jqC3sdSCtLJvJ4vj3r1hfu70O
pJVle1kz5gzWh3LOQKSVZT54hmd4hfY6kFYWbmB8tv+GCO11IK0snCF83+BjLfa13F4H0srC
kPvZsXM3aK8DaWVZO5aYM6BHSM4ZiLSybGSQmDNgTiQ5ZyDSykKs6mfv8dztdSCtrI6Vtxxz
BilzBnHPcLJwmvXZPp5fN+11IK0sTP6+PuneB+9M6BkSaWXZ/BrpMOgZ3F4H0sqy3UjxPo+w
lrDXgbSybMYhsZqAp5VcTRBpZQ3MPiQ8g72z9AxEWlmY0NihNH2J2+tAWlnWgyU8A+aokp6B
SCsLIeif7b3WOey1RFpZuEX7/T88w0V7HUgry3bx5PYehVmC2+tAWlnI6GEhY3/FmlHSMxBp
ZSE++bNjdzDtdSCtrGm1Hp7BWk96BiKtLKRF/mzxunporwNpZdkOwuV9HreHwl4H0sqyJ7y8
z0OSKex1IK2sibZwhWe40l4H0spC8L2FYFjJX9rrQFpZtktx0TMM2utAWlmIxh9XeAa0hSs9
A5FWlrXKK+YMGOevnDMQaWV9//3smDOMtNeBtLJws8eE8OwvbtrrQFpZth9wxZwB89Ur5wxE
WlmYLn527Ok32utAWlm4UTku7jMI7XUgrSxcTrFgIGvtN+11IK0sZIQy6Qp7qov2OpBWltd0
zBnsPeWcgUgry0bR647TvkF7HUgrC9dZLKDCWuKP9jqQVpbtsF3hGXDicaVnINLK8id89h7A
9Zx7AFfMGQ6W+a7L+/z1pr0OpJU1rD++exZ+vecs/HpjFr5Ztiq+vc/b3tBNz5BIKwsLMGsQ
bIl3zhmItLJspXfHagLz1TtXE0RaWdPtWJ8/tNeBtLJs7+QOz9Ae2utAWlm4pGnCa2ztd3oG
Iq0sXI2zoA37jZf2OpBWFpY65prMJzba60BaWdPqMDwDVgN3egYirSzbO7nDM6Bv3ukZiLSy
vN7CMzw/2utAWlnYBLEp+l+xF+H2OpBW1rBvCs+A0fVOz0CklWX98aZnENrrQFpZth9wcwcy
7XUgrSw7Jb3vlr7kvjOyJpBWlvWuOzwDzsXu9AxEWlm2sri9z9tYedMzJNLKmlYL3udxCyrs
dSCtLH//r4/n1lpfjudEWlneKt/Yb39orwNpZdkTPjFnwJzoyTkDkVaWrT+f8AyokSc9A5FW
ltX089vj+fM7x/Pn9+b7CJadKD/hGTCXeNIzEGll2Rr3Cc+AtvCkZyDSyjIv8YRnwN7Ak56B
SCsLd+XG071HYTXwdPYoIq0sbEp9tR2e4aK9DqSVZTvpT3gGq8/0DERaWTafe7zP29r3oWdI
pJU1rdZnjOcX7XUgrSzcav5+08/PsV/60DMk0sqa6JuPxPr8pr0OpJVlM/Lnit94aa8DaWWZ
R32umIW/tNeBtLJw52883ucf+JiHniGRVta0Wvc+j8wCYa8DaWXh7vt46BkG7XUgrSxsEn62
96h70F4H0sqy+dzzxh7ATXsdSCvLTt+f8Azjpr0OpJVlf/3SM6S9DqSVZX3l5T7DRXsdSCvL
5r5veAb0ujc9A5FWls0Z3/AMmB+96RmItLKQM3W83uet7b30DIm0suz0/aVn6LTXgbSykJlm
vOEZMMN90zMQaWWZt3vH3rl7x7lz94ZnOFi2Z/2GZ8D+7JuegUgry3aN3pgzWPlyzkCklWUn
Zi89w4/2OpBWlu1SvDFnsCfPOQORVtawWo85Q2+014G0svwJY86AvvnmnIFIK8v25N7wDOjZ
b3oGIq0si3R7Y86AEePNOQORVpbFe70xZxiN9jqQVpadIbzcgZy014G0smwO/4ZneNNeB9LK
stifNzyDtYv0DERaWTareWOfAfOKN/cZiLSy+vefzw9H9E7a60BaWTi2nb9fRu+EvQ6klYXD
S5NnjHli2OtAWlkIOZi/Fjt3D+11IK0sHHGboKO1q0Z7HUgrC7cVTGbyLz+NCHsdSCsLB++f
HXsAP9rrQFpZ/Ye/HnFG32ivA2ll4Ub2Z/vu4Ocxwl4H0srqPzztjLXzpL0OpJWFUJbP9pO4
KbTXgbSykFFy/sIzjJv2OpBWVrdvkojT77TXgbSy3L5y7Rz2OpBWFgI65i88w7bXgbSycKdl
/sIzyEV7HUgrq994s9xnaLTXgbSyoBFggtnWo36014G0svwJwzO0QXsdSCsL93/mLzzD7LTX
gbSy2o1WGfsMVoe5z0CklYUAm8/Ok7iw14G0sqBpYoLA+A0ZtNeBtLLsr9tv99r2O3tt++3f
CBZuDJnM5F9+1yXsdSCtLORPNZF0ayWd9jqQVla3v+6Do1rY60BaWf6EPfb0hfY6kFZWRx22
8AxoSS09A5FWFlLRmaSz1e6P9jqQVhbS9pls9F9+vynsdSCtrD7wnmLO0C/a60BaWdBgn837
/GWf0zMk0spq/rnvqqFNNypUJNLK8r8Oz/BrtNeBtLLM27XwDFejvQ6kldUu1PQd3mfQXgfS
yrK+0jhn6LTXgbSyoJUzW3gGjBItPQORVhY02D87du4m7XUgrSx/N+EZMEq09AxEWlnttc9j
D+ClvQ6klYUg0NnCM8wf7XUgrSwkLJw95gxv2utAWllInTn7L3fuwl4H0spC2OjssZrY9jqQ
Vpa1/B6eAT2ip2cg0spCo589PMO214G0sqwWeswZ4NN6zhmItLKsxfRYTWAE77maINLKQibf
2b3PP/bk9AyJtLLMd3Xv89h6CHsdSCsLIZ2zh2ewp03PQKSVhTtGs8c+A+ZHPfcZiLSy8FOz
S6zPX9rrQFpZ0D2Y/Yr1+UN7HUgra/xQC97ncRE47HUgraxuNc05w4/2OpBWFtYin+2zcIwY
ndo1ibSycHdtds4ZLtrrQFpZCECb/YkTxbTXgbSyurXj2IHEDKfnDiSRVhaCQGd/527tb66d
A2ll+ROGZ5BOex1IKwtB0nOEZ8AsYaRnINLKsln/4Jzhpb0OpJVlc8bRMh4u7HUgrSybo4yW
cQBhrwNpZZmXGLGauIX2OpBWVtgR8dtprwNpZdl4NVyhAodaYa8DaWWZtxsxZ7he2utAWlkN
PmZwNdFprwNpZZknGrGaeF/a60BaWTbCDYmTuIf2OpBWFlLLzuF9Hoq1Ya8DaWV1q3Xv89Za
Bz1DIq0saDDNEXMG+JiRcwYiraxubeHOmLuw14G0shDPMkMX23oE1bM30spCvs4Z6tnQVJ2p
np1IKwsJVmeoZ3tZc85ApJWFbjKHK1QgHjrsdSCtLESOTNfFth3dSfXsjbSykPB2jvAM1nrS
MxBpZeEUaLoutkVJTKpnb6SVhdvSn/3kDGBSoSKRVhaS6s4ZngEz9ZmegUgrC6oSc4ZnuIX2
OpBWFu6PzhlzBozHM+cMRFpZyCAxpytU4L5A2OtAWlkdcyLXxbbT7En17I20shCuP10X2/Zn
J9WzN9LKwmWI6brY47YaoWdIpJXl9TZjT7/RXgfSykKa6jkl79HPmZ6BSCurY0Y+Zc/0p5wz
/Rme4WDZ/GGGZ2iN9jqQVhYSpk/Xxfa9CKpnb6SV1dFvXBfbjj4n1bM30srq9p7CM8DzzfQM
RFpZNsLNmDPA/8+cMxBpZWHInTPmDPAYM+cMRFpZtifnuth2qjKpnr2RVhauMM1Jz/DQXgfS
yvJ2/Oae/qR69kZaWVhITuFq4qa9DqSVZfUmv9xvn5KegUgry9bqEp4BY5ekZyDSyuqY1bou
ts8lqZ69kVYWZA6mhGfAXFvSMxBpZdlY4rrYPs+jevZGWllQqJmuiz0gzDepnr2RVhYyrEyJ
1YQ9ba4miLSyoLw5JVYTeGeSqwkirSybcUh4hnvQXgfSyrJ2LOEZ7rTXgbSykBVhCucMaa8D
aWX5+w/PgF4n6RmItLK83q44iWu014G0sjpGO6FnaLTXgbSybKfQdbF9RkX17I20svz9h2fY
9jqQVhYS2E/XxfZxjOrZG2ll+RM+eSN3Ss4ZiLSybIUk79Fr39JrwzMcLORqmPJu7yPv6X1c
PbuwoEU4XRf7mx/9aK8DaWXZGvcKz3CnvQ6klWVPeIVnwNh1pWcg0srCwmVe4Rla2utAWlk2
7routvsCqmdvpJVlNX31jKGfV3oGIq2sjpHoijkDVgNXzhmItLJwb39eMWfAGcmVcwYirSyb
X7sutgXCTKpnb6SVhYik6brYdmY1qZ69kVYWbl1M18X+3vJFex1IKwvLkHnRM/xorwNpZWF5
+w3t3qNG2utAWlk4x5uhnm07PamenUgra1iNhGfA7PNKz0CklYU7LTPUs/0N5JyBSCsLkevz
ut/9zu/3fOd3RNZslv/es3fVrufcVXP17MJCRo95hWew+kzPQKSV5b0rPAPmxFd6BiKtrGG9
+Y077pP2OpBWFqICZ6hn2z5Bqmcn0srCVsC8wzNgV+xOz0CklYU7X/PmnCHtdSCtLETszbvF
bdlJex1IKwvxRfPueY9+3ukZiLSyoBEx71hN4A3cuZog0srCkm3e4RnQWu/0DERaWbhjNG96
hov2OpBW1rDPwzOgF9zpGYi0snBtbd6cM0za60BaWcPeLFcTnfY6kFaW+a5Qz0YGgJnq2Ym0
sswThXq2nSGmenYirSzz8/eVt2vmnZ6BSCtr2HsKz7DtdSCtLFt531xNdNrrQFpZ3T+PuL5G
ex1IKwu3eWaoZyOCYaZ6diKtLETZzJtzhpf2OpBWFiIV5h2eAauaOz0DkVaWeVTXxfbZJ9Wz
N9LKgqbmfGLOgNPsJ+cMRFpZtjvsutjjwTqR6tkbaWXhRt0M9WyIEs9Uz06klYWo2em62ANC
1JPq2RtpZSG73HRdbJ9XUD17I60sXBGfoZ6NWLOZ6tmJtLJw73KGejZiGGeqZyfSyoJwyAz1
bFv1p3p2Iq0sbDHNh3OGtNeBtLKsxYR6tu0ap3p2Iq0sxOzPUM9+sA+f6tmJtLLMo4Z6tu2K
pXp2Iq0st6/Ybx+014G0soa1tyuzeMwnPQORVha2/ObDOUOjvQ6klYWcRTPUs21un+rZibSy
bIct1LNtFybVsxNpZSHea4Z6tkURpXp2Iq0s7yvhGax86RmItLJsBzrUs5HTb6Z6diKtLPPa
oZ6NYP+Z6tmJtLJsjRvq2RggZqpnJ9LKsrVIqGfb3CXVsxNpZdncN9SzLbog1bMTaWUhecQM
9WybfaZ6diKtLHs3oZ5tJ82pnp1IKwuHZTPUs5EtYaZ6diKtLIt6ekeM55P2OpBWVscqLNSz
7TQi1bMTaWXZLt7LOUOnvQ6klYVjwhnq2RZLk+rZibSyLN7rde0J5D4Iex1IKwtHwzPUsy8r
Kz1DIq0sZJGcoZ59b3sdSCsL4ogz1LMxaZ6pnp1IK8tWeu/17ndOhYpEWllfI/vsOzJmpb0O
pJUFubgZ6tkYTGeqZyfSyvJW+ezYwVTPTqSV5e/m2efnLxUqEmlleX9847Sv014H0srCQe8M
9WxvrekZiLSy4Lsk1LNxy0dSPTuRVhZOST87em2jvQ6klYVDcQn1bOQ5lVTPTqSVhUQ0EurZ
yJ8rqZ6dSCsL8wcJ9ezbvjU9A5FWFuZBEurZOFuQVM9OpJUFLyGhno17c5Lq2Ym0soZ9U8wZ
WqO9DqSVhdtuEurZXp/pGYi0snDELaGejXg2SfXsRFpZ0EqSUM/GilxSPTuRVhaOjCTUszFf
lVTPTqSVhTwj8tueQX6nZ5AfVxObhdWL/DhnmLTXgbSysG6TUM/GjpWkenYirSzM4eXHOcOP
9jqQVta090/P0GmvA2llTav1J7zPj/Y6kFYWItcl1LNx9UtSPTuRVhbuHkioZ2O/Q1I9O5FW
FsZECfXs23pzegYirSysqSTUsxEVLKmenUgrC2O7hHo2copLqmcn0srCDrSEejauckuqZyfS
ysJYIqGefdk3tfyNQFpZiCOUUM/GdpOkenYirSycjEuoZ2MrSFI9O5FWFuZz0jhnENrrQFpZ
SF4noZ5tPi3VsxNpZWHGIaGebf4m1bMTaWVh51ZCPRsRu5Lq2Ym0siA3KqGeffe014G0srBC
klDPxtxeUj07kVbWsCekZ3hprwNpZWGFJKGejawokurZibSyEL4koZ6NXTFJ9exEWlmIVJBQ
z8YsWlI9O5FWFqIIJNSzsUMiqZ6dSCvLxqtQz8bekKR6diKtLOx4SqhnY14hqZ6dSCsL+c8k
1LNv6xHpGYi0sob9dngGSXsdSCsLuZEl1LOxmySpnp1IKwt5X6RzznDTXgfSysJuvYR6NjY+
JdWzE2llYb0joZ6NyEpJ9exEWlnDnrZHr31orwNpZdlsINSz7Q2kenYirSybDYR6Nq6LS6pn
J9LKMi8R6tm4iSqpnp1IKwu79dJn9Nq014G0sqxVhno2tuYk1bMTaWVhtiyhnm1jZapnJ9LK
wmxZuhy/IeU3YjVxsMxLdNeewFXVsNeBtLK6tQV6hkl7HUgry8bEUM+GlIakenYiraxhfx2r
iZH2OpBW1rR6c+2Jx2qEChWJtLIQZiKhnv1Yj3iOnTtx9ezCQlCVhHo2brtKqmcn0srCnUgJ
9WxEb0qqZyfSykJaMgn1bEibSKpnJ9LKwh6QhHq2zSVTPTuRVhbU2iXUs7EOklTPTqSVZS0m
1LOtR6R6diKtLAgRS6hn4wxRUj07kVYWzhAk1LOhZSypnp1IKwv7+zLoGW7a60BaWbjVKoNz
hh/tdSCtLOSXlVDPxr6NpHp2Iq0sJBOUUM+2HpHq2Ym0sqbV9MxoXEn17ERaWcPebHiG50d7
HUgrCzK2EurZz5i014G0spAmTgY9Q9rrQFpZCA6TUM9GlJ2kenYirSyEL0moZz9WvvQMRFpZ
E/OHUM9+MHdJ9exEWlm4Xy2hnm19KNWzE2ll2Zoq1LMR3Sypnp1IKwt7vRLq2dj9llTPTqSV
ZSuLUM/GXTBJ9exEWlm4IS+hng2BKEn17ERaWQgtklDPxtmCpHp2Iq0syNhKqGc/6EOpnp1I
KwtixxLq2dgel1TPTqSVNbHnEOrZD2bqqZ6dSCsL+bYk1LMfzBJSPTuRVtawbwrPgJ6W6tmJ
tLJsLAn1bJu1pXp2Iq0shL9KqGfjDFFSPTuRVpaNDKGejdsxkurZibSyoKQuoZ6NczFJ9exE
WlkIYJbJOUPa60BaWV7Trj3x+OfsUURaWTaKTnqGH+11IK0syFVLqGcjyYOkenYirSzrXZOe
4aW9DqSVNa0thEIFZtGpnp1IKwuvXkI9+7HfTs9ApJWFFIcS6tnYtJdUz06klQUVZwn17OdJ
ex1IKwvBYTJde+K1WqdCRSKtLAQ2SqhnQ6deUj07kVbWxGww1LOREENSPTuRVtbE/kPoYiN5
iKR6diKtLHR3kVCowI6FpEIFkVYWsluL0DN02utAWlnIciShi42YIEn17ERaWchTJaGLjehN
SfXsRFpZ5lHFtScejHZChYpEWlleC97nnyftdSCtLGT0kNDFtvE41bMTaWWh80roYuPgTFI9
O5FWFoZDkVCowIxTUqGCSCsL+VIkdLFtjEn17ERaWbYqDl1s28tO9exEWlmITpFQz7bdvVTP
TqSVhSFXJBQq7C2nQgWRVpZ5idDF9vpMz0CklYXJn4Qutq21Uj07kVbWRA8OXWyb26d6diKt
LNsjDV3sx74pPQORVpZ5otDFfjCipnp2Iq0s88Ghi23ePNWzE2llDfT50MVGmidJ9exEWlk4
7ZXQxUZ6JEn17ERaWViySehi245Vqmcn0sqyfY3QxbaVbKpnJ9LKwjm3hC62zaJTPTuRVpbt
w16cM6S9DqSVhTuRErrYthpI9exEWlm2FgldbEQkSqpnJ9LKsp3C0MW2PeBUz06klYVbMHJx
n+FHex1IK8tOgUIXG0FckurZibSybBcvdLFxyiWpnp1IKwunchK62Ihnk1TPTqSVZXsOoYtt
/j/VsxNpZXVrC+EZrNbTMxBpZWFLQ0IXG3crJNWzE2ll4e6BhHo27m9Iqmcn0sqyVXHoYt/G
yR1IIq0sRK5LqGfbaV2qZyfSympWh6F3N9NeB9LKatYWQgkTZz2pnp1IKwsyUhK62EhSKqme
nUgrC2JKclPv7qa9DqSVhZvMErrYCNaUVM9OpJUFKR4JXWyrnVTPTqSVhS0/CV1s8zepnp1I
KwubthLq2XcT2utAWlnYtJXQxUbRJNWzE2llNbS30MVGw5FUz06klQXJLQldbDROSfXsRFpZ
zd7T1siVVM9OpJXV/Jte/4ub9jqQVhaSFchNJcxGex1IK6tPszPzl6R6diKtLFzZl5uqVjft
dSCtLNzHkpuqVj/a60BaWUgkIKGLbSvAVM9OpJVlPvjmnOGmvQ6klYX4IrlDoQJrhjsVKoi0
srze6Ble2utAWlndeldo5OLkN9WzE2llIRuNhC42qk9SPTuRVpZ5uycUKrA39KRCBZFWFu4x
yUNVq0l7HUgrC0JH8nDO0GivA2llmZ8PXWw7VUn17ERaWdbGntCusSdP7RoirSwcnMhDvbtJ
ex1IKwt3jOTZeneS6tmJtLJw91mong0/ttWzibSyzKM+1K6ZtNeBtLIg5SZUz8ab3erZRFpZ
kKoSqme3H+11IK2sZjUd6tlYvW71bCKtLOtdVM9G29vq2URaWch4I1TPtqdNVSsirSwcE0qq
Zw/a60BaWda7QhcbquqS6tmJtLJspKZ6trXWnDMQaWV5TYd6NvzmVs8m0srC8ZqkevZFex1I
KwuHTPJQIzftdSCtLJszhi42YuYk1bMTaWUhC5hQPXvb60BaWQOzc6pn32mvA2ll4chIUj37
or0OpJWFuDWhejb8/1bPJtLKspEhdLEtJijVsxNpZZnvejlnuGivA2llWU2/nDMM2utAWll9
2uf+G4gcOtSzA2ll2Yw8dLGD85a/2Gf0VM+2egtVK/umVLUi0sqyKLTQxfbaSc9ApJVlXoLq
2Zg/bvVsIq0sZIqRVM+etNeBtLJwYC1Uz8YsYatnE2ll2Qlm6GIjNlZSPTuRVhaOCSV0sb0+
c85ApJWF9B9C9ex5014H0srqmGuFLjZucEqqZyfSyrIVUuhiWxxYqmcn0srC8ZpQPRu7MFs9
m0gry+KLXurdPbTXgbSykP7jCl1sxOtcqZ6dSCsLR5EX1bM/H3Nt9WwirSy0yovq2d84dm31
bCKtLOSkv6ie7RwpfxFn9JuFqMArdLExHl+pnp1IKwvv/wpdbEgeXKmenUgrC6viK3SxUZ9X
qmcn0srqViPUrvnRXgfSyur++ct3fm31bCKtLCjfXD+uJibtdSCtLGTJu0IXGzlOrlTPTqSV
5e/GtSfQvsNeB9LK8ncTqlb9R3sdSCsLUR1Xqmc/tNeBtLKwz3RRPdu+9Sq/ETuQBwsRlNeP
2jVCex1IKwvnw1eqZzfa60BaWUhEc1E9+057HUgrCxFJF9Wzr4f2OpBWFrKfXD/q3TXa60Ba
WV6mULUajfY6kFYWsvdeoYttLSnVsxNpZSF/zUX17DZorwNpZdnvNapaddrrQFpZWLddoYuN
+eq11bP/Y3/xL398//x///j9if/98z/9IZB9b54fyELK27A8YBa83zyPj10vaJ6hZ77fVLd5
7p2JZM3fPN4//1pS83w5tF//no/jOW4+e8L2z79nbZ6XZiKxdPOMM9/n/bO7f/6NuZ/95O96
/peJk6jmmV3sIkPznC0TqaA/+94caZtjdx7n2/Cdl3/+w3de8Tns28vyAz/K3sGPsn9V2Dy7
iF0Xap43ZD4Pnj/K/jWKNqPsXz9vEmXH33p+Druo0oRl/8GOMn71I1H2Dn73snxttUmUveM7
o+x4Nomyf/O65vkmvD4lyo5yyVF2ibI3fOcl+zuj7N8cvUmU3b4zyt7xbE+UxewoIzgsu9nx
+fdbnqfAn8czEEycQTXPLTBxBtmuKDvqzfMBfJ/jb73sSGbfrig76vNi2b9n8Hv38bdRdry7
i2U3+8qyXFF21P8VZcd7uaLs9jnL/tXb9ez2cLHs4ETZUVcXy272m+/ujrKjru5471+x2x3v
/Wd2tIfv+f3G8/d5h31nHd4s+wX73hyWHd9zlP1m2fF5lB3t3G/wTiy/mt/NnUiw326+d3xn
lB1l8Zuy3jZulh3fz/eOv/WyI7V/8xup/j1PlB3P/ETZ8WwP3/sLe7/fJ9779/Ptiff+fHXy
jF0nfsNyYoHTnih7x9962bHka37f0Z/HbzLG37LsD2zZ/PuX/ddvDMbze9mtfvyWn9fbw/f+
vVO/med19UTZ0R/9Nt33txP2fu9+A87ftd9tm0iP396+2/bL/o6/pa/7wb6yvb1zt+GX7x3f
E+/d7fDP+Nvrt3832vy3HGvv8d7fe/uoN947fPgb7/1rRp/9pk9+o+yC74yyfxOg/ov3/j3i
Zz98hv6Lsn+P239R9m+i0X9R9gt/G2U3zmj0h/0XZRd8Po/P6evwucQYhO9k2e/PjrJ/9dx/
UfaJv72yLP0XZXf73c8fZb/w/E+OQf0XZb/xeZT9a7e9RdnxnH7XwTktyo7nbFH2/n1Pi7J/
Re1+p8D8ZG8j23ZvfO9fuVqU/Wsb3WP3vSwtyj7wnVF2+9souz3PFe8Rzxllt++Msg98HmUf
+PwZbGO9Pdm2e4uyf26oN7b572895tufv0fZ8d57Oz6PsqOeO8uOv42yf6+/9yg7ytKj7BMc
+jqzwz/je6LsHd/Psn/12a8cy3qPsn/jRe/XLmNnmweHvg42y47vYdlRlii7caLsqP/Bspt9
78/Z5gV2juPdo0dt/tNHlB3tbYzj8yg76tmjNP2djuO9jyg7+t2Isn9znu7RkN7+R5Qd9TlY
dvwt2zx+9w4fhe+Psrv9ZN2O9/j8vfN5ZpT9Gxf6jLLjXU++9w77yj47o+zd7Cg7+Cw7vmdI
9uXJst+wZX8/+zu+R+b+ftn9d0bZPzfUZ5Qd/c6jr7wsM8qOOplRdtTVjLL/8Awsu8C+s90K
yz5h3/m+hGX/wb6yrqTv/ivs77BHzre7jPTbXaLs36q8S5Qd/Vei7N/8pEuUHW1VouxoA8L3
/sB+97Pdu19LlP2Hz/neB+zdtj2Ow9uwvNs/X2zzN+w736PHS3gfv6LsF2y2eXCi7PD5HpcQ
nCg76uSKsht/yv7d+WbbuKLsxmfZv3q76Osa7PDb+P4ou3Gi7GZH2W/wnzvr/GLZzb7ze+4o
O/qpnxv7u7uj7HLD3mPW3feY5eezXrf32P33HruMd5Td+HP77Xvutn3zveN3o+xoz37e6O3t
jrLj3d13jtf9Ztnx+ZNrkH5H2TFO3e9RRrb5z34OX/f8cj7Wn7b79dP2uPywvwtsyb78jJxv
92fsMeuJsuN5nig7/PwTZbfPWfYB+02f8ETZ4WMflh3PfG+//dy7X/vJRZTl2ePyE2WH33je
XSd+QuDlfaPsqJM3yo6+9rbj8/7L9/XyvX/18PK937Bl80fMq2FH2eEH3uO9v0eb951lL+PL
9272s58nyo726Tu4YUfZ0Q7fKDvGi/fd/dp3Sq0Pjt8v3+P4/XKuMnzf8pvrvrBzDBq/Xfbx
i7JD3es3ci05fOfP/Or4RdmhOvyLsn/tYfz43vH9cnweZYcq1S/KDgWmH/s7OFF2qKj+7ns/
Q5Qdekg/tvnfZ799l4tl/76/RdmH2Rfr2UJNwoeM1rJfW8gDv6f17NejRdmhydSi7MaJskPF
rc2ck3z2u/ky2PY+O8fr0fjenz/tOI7lbXfPd9fuXGvYIR/fY3uyX1uASj5DlB3vsUfZoeDb
6eu+v+0t94Lswqr5z6/sne/9+dOOP8K/fXbsBX3f36Ps9j1Rdugn9ig7lEr7fDYnyo667ZLj
tckhsYz9uunTLLFgfs+d/tzSP7G8/bmyrvpR9v7mfMw2tNkGxi/XTZZSiM82+N6/ZxhRdrSH
0WfW8+jpoyyVVn5nlB11OFh2cGaumyzxX/Kj7HgXg77u+dPEJ6P/WuAw62qw7LCf9OeW7i6f
OcqO/jJY9u87Z5Qd72tG2fG3k++9/WmBt3zOyfcOfs81hV0UY9+ZUfZu9rt/a+a8y8Lj+S5m
lB16ulOe/bfX7qfz2v133um7Pvumj/2qc5dxRtmhbTqj7HiPk20emvK/H/3kZ0vWs7Scc362
5PNLy7nHkCg76lai7GiTwjaP7x85Jxkycz312bnO+qbzu227xn38bpT9eqhL721VjvfuWvJh
R9mvRv1395MSZXdbsp1cUfY7Fdidc7Ucs0Ib3d/X1XJNEXrm3h6uKDt89TXm5o/tt68oO+rk
mrmWDK3v+C2WXajP7e/xirL3VNsO/lH2K8oOX309e8y63u3PrzfnHqE37e38/uVcJTSi/T26
+rM/wx1lR73dPdcgocUc/DGyjd1R9jmojOzPds/cIwo1Y2/n91H2O8pufLb5SdVg2jE2pQaw
t9ubZe9U5524lxG6u/6dT5S9/aiV6+3wib363qhv63X+8L0/1KT1vvDEXr0ptkbZTU03yg7d
6ifKPlPv1cv4RNm3EquPd8+V66xQT/X38kTZ0f6fKHtr1DL1MfSJcwpT231/+/lZ9kbNUP/d
N8qOenh/e/x9W+57hzanP8NLX5dKm+733ii76WyOPWa9LHujbqXXzyt7vH6j7NCafaPsxr/2
e3zv3AMMTUd/jy/bfKMOo+1zhsJifOcbnz9URbS9x9A7tLKHkqHtq4dGYXBaztNCV9Dmb6EY
aPUTWoDx/Xzvjfp9tHMPITT34nfZ5jt18uK3WPab2nbmq0O1ztpP6NFZnYTSnLXD0JCL333T
n4fum9styo7vbzyfSn02812hrxY2y96oiebP30aur0PHzN5FKJTZWBbaY7Y3Hqpi5vdCL8za
VSiBmS8Kja/4nP19UJcrnvnJdVNoaVmbDJUsazOhf2VtLJSt/Ht6lB3f3/nehTpT/v297ffb
o+zG6fv9dpa9UanJn6fP9GmhruR15bpJdhYQiki2LgutI9qxtz+pT+R15cpDts8fmkLeTvqT
e4OhA2TtPxR+rP2Hdo+tQUKVx39r/HIdHUo63oZHS/8c6jfmx0LXxut2xF59Sy0af87Bsk/q
x9jYFMow1q9D88X8Rqi5eL2NK/t1KLDY2DrzTDZVU7yt8kx23FQ68ffLM9meuiX+WzyTRd69
yXPJSa0Q/12eyY5OfQ/vs7Onf548kzVdi302N/NMdlIhI36XZ7KpamFrhMkzWdMVuXL/ZPJM
1jh3zjknz2Tt+1n2VHmw8WvOo+xzn81NnsmijHkme1MNwd8vz2SN33OfZOaZ7EXVAX8ensmi
7fFMdqY6gPcXnslafn22+cGM/HZGFrn2LfFjZNG39JeRH9/bc5zJYniLnPYT2xYzz2R/zEPv
/THPZC/mjrfzrMkzWfzt1bY/P85kJ89k38zL7t9/nMlOnsm2zIVOO9fR89rn0ZNnsvY8+4xm
8kwWviLPZH/MAO7t+bp3/+WZLOozz2SFmbbje979fnkmaxmNeT51M6O195277bbNM9mZmaf9
veeZ7I85ob2d8EwW/eXeZ3Mzz2Qf5l52PxNnsv791y4jz2R3jmNvSzyTtWd+5v7bZ49ZcSaL
KcXkmSw4PJO1vKdRdunM2ev1//CcQphn133+07c/55ksno1nsnMyn62tDSNTbXyn5Dp68kzW
Mv/yjCZzxXqdP0fZeSZreVTvXGtE5lWb40VOVR8j8kz2YR5Ub//vPpecPJNFPfNMFt/PM1nP
C9rzeXgmi2d+eU5xM69n2HP3a57JWo5Oyfn25Jms/VaU3XJFXtt3vXuvfvJM1nNWvtt+tk97
nz0u80zWyvvmPqfwTLZ1Zme0cgnPZBGTzTPZ8TJXohVPeCaLe0Y8k+03MxfauxCeydr3s7//
mEfQqkN4Jrtz/9k4Inkm+2O+PvPJ8tvvXX47DkF4JmvP8OSYJTyTtQyLbPMPs9TZGYfwTBbf
wzPZntnkbG4gPJO13GU8p/gxg5vtzwjPZHHXg2eybsvm82zuZQ40ayfCM1nLxbXPKYRnspZx
K8ouN7OIxfM8Y38/z2he5vQKPs/iL+bh8mfgmaxk7izrj9L3eXTku7JmKnkmm9mrvN54Jmt5
vrhX35gxKmyeR9/M8mR+L/I3Wb8TnsmiHngma3m97vRpkSfJfIvwTHbezG0UHJZdmI/IyzX2
2ZzwTBZthmeyuCPCM1nLOdRz3iU8kx2Zn8fGLOGZLPJS8UzW/pbnU5ntxvZPJM9kb2aoiWdj
2Ruzyni7yjPZwUwwFj8gPJO13DjPs8vy5r6o8EwWdyfn8d55JmtZJ6Ls8jCzifdHnsm2h9lI
bPwSnslaHo04p/j9mBvE65ZnsvAPPJOFT+CZ7MzsHN5+eCa7M2oEn3v1nbkuvC3xTNa+/8m9
wcg8QXv3a57J2j33KLvna2j57ngma7kJ9nm0yI7BiEwKweHZXOZF8OfnmSzaucRePfpFnskK
swy4v80z2cnMAP4e80xWeJs/nv/JsUx4Jms5At6jjG/Ot4Vnsr+86W7DofBM1j5vsZ4S3ju3
mKu4UW7nOMIzWbunPmLO2Xm/230pz2SNM2P8vXjb2uuBZ7K4z8kzWeNfOf4Kz2T7y/vK7tN4
Jmuf85zi4e1hf+88k0W98UwW9cMzWfu87bGJZ7JoAzyTdTvnJMIzWbtdyHNJ4Q1W75t5Jtt4
69T7OM9k0U54Jtvzdqg/c57J/nhvM3733mPWvc+nhGeyuCnBM1m7JcyzeOGdRvf5zz6fEp7J
+v3EPV4/PJ+6eCvQf5dnsngvPJO1v+X5VOPtO38XPJPFHINnsq3zLpyPxTyT9RtvuU8iPJPF
+8oz2Ze3ybx+eCZrv8v3nre+/Bl4Jos2wzNZ1A/PZOFXeSaLm308k4VvfPf5lOSZ7ORdpfie
scffPJPNO0Vh872/vO3jPpZnsnY36Xr2M/C9d96qib/l+VTehPG2wTNZu5Hzpo+6eCbb8i6K
+cm4S2L+/OKZbM+bIdaerzyT/fHOhrWZi2eyxmHZ824F7ZyrxK0Hq8+LZ7L95k0FG++u3+7v
cbvAynXlmWznjQB7pxfPZPvFKP74zjfHpivPZC/G1Ft9Ruy78/1Mtsa3I+4x4tuRE47x7XAT
jG+/7HPfTxDj+z4SluKMb//8cca3w10yvh1HJoxvl3dkfDtcPOPbcYTD+Pav/2V8u9w7vh3D
A+PbxWLjZ3wuGd/ufF9bYQuA8e1ise6+n4AtBsa34xiJ8e3+/V52bA0wvh3DBuPbxWLpfW3l
dpTdnvmNMvaMbxfE3MZeCkKOGN/+tZeMb78snrzvOom9FPtdYdl/Gd+O4ZPx7f75jLLs+HYr
Y+yl4AiN8e1hS9ZJ7KV8c5+Mb//8d8a341EY345iML5djvh2VA3j21EMxrfjsRjfjmkN49tR
fYxvF4sP9/UFji0Z3z4tTt7LjqbA+HYcYTK+feJ9xV7KV5iMb8c0i/Ht/rtRdo91l2172fH6
Gd/u3+lln/b8XnY0Kca3Y1rG+HYc5TK+HdNHxrdPiy2PsiOeOfZSpsWHe9kxrWR8+7S4dJZ9
Znz7HDu+3b/Hy47pL+PbB9p57KVMi5mPsuMuQOyloHszvn3Yd0bZLU4+ym5x9b62wtSZ8e3+
t152bMUyvn1YPL+vL+zz2EvBUT3j27EMYHw77uEwvh13IRnfjizBjG/3v/Wy23PGXgqWB4xv
h9tifDvy5jO+HRqQjG9HeAHj27vFqHvZ+9szvt2/39cX2HpmfLt/T5Qdsf3PUfbYS7E6ib0U
5I9ifDvCERjfDnUixrcP+MPYS7Hnj72UccS3I2cw49vhahnfbnX4suyS8e32zBHfjkz9jG9H
RkvGtyNXJePbrY1FfDt02xjfDtfJ+PYJf/gebT7i2yf8beylWL+IvZTpMe3Rtn8Z347fZXw7
wiYY3442xvh21Bvj2xH2wfj2ccS3o64Y3z4sdj3K3nd8+7AY9Sj7Ed/uzxBtXnZ8O+qK8e2o
c8a3D4u3j/du8fC+vsDykvHtw2Lmo80jVj/2UuxvYy8Fd/MY3w5FC8a348iE8e1474xvt7I3
ln1kfLt/Z5T9vjO+Hf6B8e1Y1jK+3eoz9lIQesL4dvgNxrejbTC+3fnx3hHvHXspWEIzvt05
UXZ7tij7s+PbsURnfDv6BePb0b8Y3+6cKPvc8e3wM4xvR99hfDv6GuPboaHG+HZ7tthLwbjA
+HZ7FxHf7n/rZYffYHw7Mg4yvh0Z1hnf7pwo+5wZ3w4fy/h2hBMxvt3qKvZScEOb8e3YtmB8
O8KkGN+OvAiMb0f+Asa3D4s5P9577KWMI77d2nbspVjdDkm/zfh2a+exl2JtY7DskvHtVsbY
S/HfvaOMPePbrY0Nln1mfLt/7usLjC+Mb8fUjfHt1k5iL8XeUeylYJrF+HZ7R7GXgm0Uxrfb
+429FEw9Gd+OI0DGt0+LjY+y4z3GXoq17dhLmRbHHm3e4vCv3bZjL8X6Reyl+Pd42f05o83b
s4Wvs7j6KDtiUGMvBaFajG8Xi0v3sgvaZOylYL7E+HbMixjfPvG+Ir5d0MdjLwV/xvh2zMcY
347wKca3+3dG2Z8r49vn+2R8O4rE+HZBeWMvxf+WZR8Z345pK+PbEc7F+PawvewWix5lf38Z
3y6ok9hL8c+j7PCrsZdizxZ7KWJx4+OX9Xax7C3j2/07o+xow7GXYnUSeykIL2N8O7alGN8u
8Dmxl4KpOePbUfWMb/fvf6JOZsa3W/1cLHvL+HbMdRnfjrA5xrcjPI7x7WIx6iz7zPh2e7bY
S7Hfjb0UQYx37KVgTs74drxmxrdjHs74drEY+yj73PHt/ru+rsQrZ3y7f2eU3WLmo+zoLxHf
jlA8xrcjdI/x7YJ+EXspVocR344uxPh2aw+xl4JuwPh2hAYyvh1dkfHtmPMzvt3qPPZSrG1E
fLs9T+ylWD+KvRRB/429FLEY9Sg72kDspcznzvh2dCfGtwv8ZOylYO3A+HY54tuxTGJ8u9VP
7KXIEd9u7yX2UrBWZXw7lluMb5cjvl2O+HbBWPAebf5lm+8Z3w6XxPh2q6vYS4HrYXw7QjAZ
327tJ/ZSBPcIYi8F7oDx7YL2GXspWMIxvh3hlYxv9zJG2S2G3/cT8GyMb0e/YHw73hHj28Xi
3puwThjfDlfC+HaEYzK+He6J8e1Y+jK+XSzuPd67xdXHe0eMWcS3w08yvh1rasa3Y6nJ+HaU
l/Ht1+/K+PbLnj/KfveMb/fvibI/v4xvR7gn49vhqhjfjuUr49vhUhnfjrBRxrf751H2e8e3
Y3nM+HYsfRnffrUd3+6fz/hcMr4dS3TGt6OtMr4d+xWMb7dyRXw7+i/j2xHeyvh2uH7Gt2No
YXy71WHEtyN0lfHtxo/4dnv+iG+374/4drQrxrfDzzC+3eoh4tvdjveOuuos+5Px7ddvx7db
2SO+3d5LxLdb+4n4dn+GK97vm/HtYvH2UXZ75if3iBjfjm0OxreLlTfavMWEs7/v+HY54tsx
NDK+3drPYNlHxrdjD4rx7fa+Ir7d6jzi2/376efvjG93fpTd+FH2Z8e3C+ItI74dWzCMb4ef
ZHy786Ps9p1PjFlvxrdjTGR8O/we49uxR8f4dutTEd9u3znZ32fGt9s7ivh2DPOMb8eeGOPb
rT/Oo81HfLv1tYhvd9vL7t8jx+ce84mtH8a3Yw+N8e3WliK+HRqdjG9HvjjGt1+IO434dnl2
fLs9T8S32zuN+HaZO77d6lkOXxfx7ZgGMb7dniHi263tyVH2iG+3dh7x7VafEd+OcHPGt2Pa
xPh250fZLU4+3jvaTMS3m7+N+Hb/nii7PU+U3Z4hym7P5nGP2HpjfDumWYxvt/d+sew7vt3e
dcS3W3+P+Hbz8xHfLvY90eaNP3Ivl/Ht5mcivt3GlIhvx1SS8e2YbjK+3drAxbLPjG+3+o/4
dnnujG+3Nhzx7dgjZXy7tcmIb8d4zfh2+/xmf9/x7dg2ZXy79dmIb5cjvl2O+HZsjzK+/bK4
dL73mfHtVpaIbzf/GfHtYrHxLPuOb7c2ebO/t4xvd869/fbNsu/4dnvXEd+OOSTj221ceH67
/0Z8uz1/xLfbeBfx7dYOI779stj1aPNubx8V8e3mYyO+3X8r2jz6UcS32/NHfLv51Yhvd06U
/drx7VauiG/334r3jnqL+Hb/Xd+rtzqP+HZrwxHfbvOB97fH5YhvxxyP8e029kV8uz1bxLdb
/4r4dhs3I77dfMg7dv+N+Par7fh2e+aXZb8yvv2yuPp478a/tk+L+HbnR9nRHiK+3fpvxLfb
+434dmvzEd+OdQHj2wWKtxHfjnGZ8e3oU4xvR5tnfLtzWvZrxrfjGRjfjrGV8e14F4xvRz0z
vt0/j7J7THuM1zu+Hf2C8e2Y7zG+HfXA+Ha4Cca3XxYD/2T/ZXy7P/Nu84xvh6tlfDtcKuPb
4XYZ327PFvHteKeMb78s7r1n22Z8O9on49utbhvPaGbGt8NNM75dxo5vx9qB8e1w94xvd360
+bHj2/07o+yIkYv4dqvDiG9HX2Z8u9VJxLdbnUR8O/wk49vliG+35+kt5ySMb8feBePbrd4i
vh3zc8a3o78wvt3aUuf51Mj4dv/8eO+dZd/x7dbGIr592jPcbT8bz2iujG+3+u/7bI7x7VjL
ML4dwy3j2+2ZI75d2o5vx1SA8e1YrzG+HceBjG/H8M/4dqxfGN+ONTLj2zE3Y3y7WFx6lN3i
5+Nszj6Pstv3RNktLp1lfzK+HfM0xrdbO4kzWeylML7dyhvx7daeeSZ77fh2aw+Tbf7O+Har
N57J4l3wTNZi11n2N+PbsY/B+HYrC89k7Tuj7O+Ob7f3HmeymI8xvv1CnGqcyV72W9Hf7Tu9
7JfF0nvZ4RsZ3x72rhOeyVrcPt/7nfHt1md5Jis7vt3aobRx2E/WFc9k35bx7fa7cSaL8YXx
7YJYX57J2vdE2ceOb7d3wTNZi5PnueTI+HbM4Rnfjv00xrdbuXgmO3rGt9t74Zls3/Ht5sN5
Jovf5Zks4mDjTNb6QpzJmm/kmWzb8e1Y4zO+XTymPfcQGN+O+dv/a+purqXFkSAM79saJPFr
xpyxYRwY/xd9I/KNVK36O9V1KRIJIZQPSXy74yUnq92Kb79szslLfm/7dp93nZO92rfXb3G+
P1f7dp/7d2Jf7dtP9bHkZN/Rvl3rRfHtug2Ib/ffJier44xvVx45vt37QE7W52Bysuo/ycnq
uQNysj6XyclqDTa+3W1HTra2U7E7XnKyPoZPcvFX+3bdrsS3i/fFt6vrx7e7jcjJai0uvt2x
k5P15+Rk3QfIyerWJb7d5zs5WR+f9+d8f9PuV/t2deX4dp9f5GRv/27Guqt9u6875GQ9HyAn
62vEm9jv9u26p4hv13wmvt3XgvfnfCcn67GXnKz7PzlZzwHIyXqfycl63CAn63P2S59f7dt9
ruHbL1v0n9jJyV527Gn3r327+xs52dqftPvTvl1L8PHtnv98P7GTk/W1mJyszzt8u48DOVlf
l8nJahiKb7/85nPW6uUPj9Fzj/h2tV18u+KKb1fs8e2X/Xli37798vveM86v9u3qY/Ht6gPx
7bUPxG5LT57i6DfN+zoY3349/d54z//j29V28e1XWfc3Y058+2W7/hM7OVmNb/Htl6172n22
b7/OfkO5+2p8u4/JSJ/vN4n7WhDffvut8BX7vUb79vvYvl1DbXy7jxs5Wd1Ox7fXNmut/t7v
vCbGr+814tvv9bVv1zkY365b8fh23YPHt98/vr3+tmJXSia+/a53M/P50779tpkndjvz6+dz
Yvf2a62+Pif262zfrvl8fLtjwbfXPiT2r327LjPx7ffVb+L1ekV8+z367bl1DMnJ6n4zvt19
iZys1hDi22+/4XT1fVZ8uy6l8e26NMa3a+0xvp1/M1c52rfr2hrf7jcErn2+x7dfb78DtfoV
OVldtuPbfc6Sk63vfE8fN3Kyt9/1SOxj+3ZNC+LbNdWIb3ffPtPn+w2bdb6fyVOs9u31/bPn
JPHtl2z/mbX67dsvW/e710/i22v75Cn8HtKnx+349sv7n9hX+3b+/fR5Sk7Wb0BNTnZt3657
ivh2XWvi269z+3Zdm+Lb3R+Sk9VbF5KTfe727T7+187Nxbf72F7JS37t231MruRo+m13nj7G
t19+ZyOxa5xJTvbst8r5HjO+3X2SnKz7anKyfj9U8hRn+3bv/53YZ/t2j/nJyX79/jM+Tz76
bN/usbdzstu3+1qTnKz34e55eHy7rmXx7Ve9zavn2/HtHoeTk1V/SE529huxPJ+Jb79+fLv7
THKy9W8+P9q3Xz++3W3UOdmrfbuWg+Pbz+9q3675any7ulR8u+YM8e31nbvX8OPbfXw6J7t9
u/sPvv30W4ne3beTk/Wbr5KTfdu3+1glJ6uq/p2TPdu3+w2u+PbT7wEhJ/v1+2z+/na2b9cc
Jr69/k3sandysrrli2/X3Du+XadufLuW+OPbNa+Ob/cbTJOT1TMUnZP92rdrLnp1TvZq3+5x
5tt5ivj2+pzY/eaS0etm8e38m2vT9u0ee5OT/fr9GzWWkpO99psxvI4X3+7x8Ns5mvh2j9vk
ZLV0Ht/u8SQ5WfXD7yf25GS9n9/svtQ52a99u/pJfLuGv/h2tXV8+9+9Rft23RPFt+tciG+/
bOAX9xRP+/b6LWJf27drzhbfrrErvv2yY6fP26vT52fX1ff4Ft+ua0F8u9o6vl19O75d43l8
u/eNnKz6any7UkHx7UoXbd8+27e/cpvr6b4R3650IL59aTqOb1+3/9brSE6l4NudbsG3L+WY
8O1L8wF8u9Mh+PalW2t8u1Mj+PZVHn7W53bvvrdyegPfvjT049uXxkx8e+1PraXwue8r1+Ua
8nd9vp749qU1Fnz70hwP375uGe9aS3HqAt/uVAq+fd2uRV+xazjGt/u9Kfh2v4ED316xX8Qu
B3sR+93125eWBvDt6zm7fjvfqdiVhsG3+x0U+Ha/dwbf/vedM7699rnWUv7+3fXbnf7Btzud
g2/3++jw7X/bad/u93bg2/2OAnz73/e7frvfM4dv91vR8O21n7WW4neA4tv5t+8vnPLBt69n
+3anlPDtfpsbvt1vm8G31/7cxD7at/ttlfj2v578xLcvLRng253awbfzWxX77VjeHeNN7Pb2
xK5a2Tex67x4iH11/Xa/SQ/f7vcu4Nv/vvPFt1cbPcSuWuUPsbvuOrGXaa8YZaQfYvd3KnZd
ovDt67WZv6sdr/bt/C7t7t8l9rd9u9+ujG/32z7w7dX3Hvq83rlQayl1/GstxW+8wLfzb/q8
nbnvL+q8e4n9bd/ud1nh25fCwLf/tVH79joOL7F/7dv9Vl18e8VYaylsn9hH+3anAPHtSyHh
25emLPj26s+1lrI0FcC3L13O8e3rdb30il1TB3z7el133fcX1cdqLcXvgse3O1WJb+dvK3a/
4+Aj9rPrtzuViG9fOhz4dqcS8e1/31nx7WyzYn/XE9++PObXWsp63/bt/Lti13Od+HanBvHt
q2rUE7vdOLHbmRO7jN9B7OuIb1/v9u1/x2fGt/u8xrc7pYpvd2oW3740HcS3u+3w7T7++Han
bPHt/C6xy4DVWsp67epp9+eOb1+aAuLbfS7g29dbNdsrRlv9n9gHsduH8z5p11on9vOIb3cb
4dvdjvj2pSkgvr2O4aDd3zO+3e9Hx7evqq9esbueba2lLNdhrrWU5frktZayXL93ELv3h3b/
jvh2p4fx7X5DPL7daWl8e7XdSOx3fLvfq45vd7oa317xTmKX95vEfrzx7XVsay3F4xi+vdpo
5nw/49urjSbt7t+i3Vf79r/9OeLb/R5zfLvT8/j2paET385+8q5jedpJ7Lt+u88dfPtyXeJF
7Kt9u88LfPvS0IZvr+O55u7Di9jlw9dPn1/EruNZaynVTxaxy5GuxN6+vY5traVUuyxiv5/4
9vW6Bjvt7v2vdza61vpKu5/x7cu1jhexy1su3sf+df12UwN8e/Wfk9jVXrWWUn978kbz94hv
r+2fxP50/fbq/yexuzY7fV7n3Uns8ti1lsI+JPb27Uvv5sC31/lVaykmFPh2swZ8+/qO9u1L
t2f4dr5Tsev2Cd++XNObtZTDtdxrHelwLfSK/fu2b9ctB759uW45vl1Tdnz70nAc367bCXy7
+QK+fWkpHN/O9uu+8rCf53yX1ce3H/bzdW91yA+zlnKo77GWctix11qKhuD49sNO/nv6O6yl
iB3Etx+ueV73VmIH8e26LYlvP+zJay1FfCG+/XBt9rqvrH8Tu716raWIq8a3iynEtx/3rt9e
v1trKcdP/fZDbXcn9ie+fX3eJu1ue1/vCfvUr3jTuG478e1LdV/x7aYn+Pa/z1f79sO12Ynd
3yF2u/S6r9QlML7d8bKWcly7fvthW173lUe596/2bbZvP9TPWUsRK4lv9zFhLeXQOcVaituC
tZTaH9pdx4G1lMOunnbXOMZaii6H8e3Hj2/XLW58u7fPWsphx07srtNO7Nds3358T/t2XSbj
28fYvn3YqKfdV/t20ZP4dtGW+HYfQ9ZSRFvi291XWUvRJT++XQwlvl2X1fh2XUrj23WbHd8+
yrrfvW+speiyHd8+dO6zluLts5YyNBdiLUVkOb5dTDm+fWgc/n5iZy1lXNu3j3PXb9flPL69
vn/z+a7fLhId365Le3x77Sexa1xiLaU+/+jDb/v2YX9O7PKER9p9tm+v7xC7HTux26sTu+qy
spYyjqN9+3B99R17fLv2P75dVCi+fVTN9opRNYdZS5neN2J/t28f7/bt48e3i2vHt4v7xLeP
b9dv1xQkvn2e27fPY9dv15Qovl1TnPj26bruFbumJvHt896+fdrGV+zT9d4rdk2P4tuH7OhI
u8/27fVbiX37dnGl+HZRp/j2+g7t/u767RVXxa43pMe3T9c5J/Yy7RXL2PXb5719u9hTfLuP
P759lGmvGGWw8e36s/j2+ePbvc/4dnGu+PbhfaPd3+3bp518xV6/S+yuG0+7q3/i290f8O3D
lp52V21efPuQbca3a0yIbx8/vt3HEN/u/cS3+/jg270/+PbxbN8+5Frx7Zr+xre7T67Evuu3
a1of3y5mF98+nl2/Xd00vr3+lthd453Y5/btGhPi293/8e1zbN+ut47Ht7sf4tt1CxHfrluI
+Hb38zPtfrVvn7bltLu/c67u52fafbZvF7OLbx/Pat8+j12/3fuPb6/tVOzz3vXb3Ub49vpd
+vzYvt19G9/u38W3e2y50u7bt/s8wre7vfDt3s8rsc/27e5v+PbaDrGP7dvHs+u3zx/frtM1
vr32k9i/7dvdRvh2n/v4dvcrfLtuq+Lbfazw7dN11Ild/fxO7Lt+u88vfLvHdny7Y8G3ez/x
7RqS4tvrbxP79u3zx7d7zMe3i0XGt9ffEvvcvt3jA759uob8s/swvt3HH98+XPs9fX779vHj
233+4tt9zcK36/ob3+72xbe77+HbfRzw7br1jW/XEBbfXp8Tu515zvenfbv3Gd+uYTS+vX4r
ff5o3+5zAd/uawG+XUNVfLv7PL69tpl2X+3bfQzx7W4jfLuvR/h291V8u4ba+Pap44Nvn67l
Tuz+W2LXuY9v1611fLsYa3y7Lgnx7VPPIuHbp2u8l3sUY41v1617fLtobHx77c977e0Qu+w6
vt37/yX27ds9VuDbxTLi23XZiG/3NR3f7v6Gb596Du5L7Ff79vp32n22b/d1Ft8uwhvf7rHr
S5+/2reLEce3+5qCb/f58mWs2759/NRvd9/Dt2sMj28fduzHmX4V3z5c/5w+bzdOn5eFw7dr
vIpv1zkS3z7Grt8+f+q3D9eBPzl/d/32UbXcn5yD8e26rsW3T/8u7a56qvj22of3yJgT367Y
49vH2r5d88P4dnHw+Hb1//h2zc3i2zWNiG/XFCG+XdeO+PYpw49v17gU3z5/6rdPu3fa/ad+
u9olvn269nvFrnM2vl3nVHy7lp/i29fc9dvnO9q3L7v3il2MO759et8q9uUa6cTuuujEruM/
0+dH+/ZpN07sNurE7u9X7MsGvmIX745vF0OPb6/vVOxi4vHtmorFt0/XXb97PI9vr88fztOn
fbvqVMS3a3Px7RpL49s1xsa3z3P79mmLTuzqn/h2LXfGt7tvr58+j2/XPDy+fdjAr74ux7cP
14E/+zoe3z7Xrt8+bdeJ3bXWb65ZV/v2qbbunOzXvn3ayRP7HO3bdcji26e38+32PdPuu367
xqj4djVhfLvPNXz7LOv+9P7g291/8O0aV+PbZ1n3u88XfPu0jb/2eY1vdz/Ht+vaFN8+q5b7
tX+X2HVs8e31t8Su/o9vn64/T+zaDr7d/RnfrvE/vl3XrPj2+rxiVxeJb5+unU7s39W+3ccZ
3+79wberu8e3T5t5YtexutLuT/v26dryD3OS7duHf4vY7djf3Y74dvdnfHvtJ7Hr+SN8u8er
O+1+t2/XXCW+3ecCvl3zxvh2j5/3T7vfGeuO9u31fWK3qyf282zfrutXfLvHeXy75tXx7T6P
8O26JY5v9/UL3+62xrcrTRLf7usavt3nEb7d1wh8u+Zs8e3eB3z7sDOfzLve9u0+35+c77t+
u68jz0/s+HbNk+Pb57HrtztGfLvHhCexb9/u449v19w4vn24TvtLjKt9e/2b2DVG4du9fXy7
9/NNn9/1231u4ts1/4lvHzbkc1+X8e1z3O3bdd8X3+7+iW93LPh2j8P4drcpvn3oGQF8u48t
vn1c27frEhjfrjlwfLvuPePb3db4dseOb/dv4du1/hDfrktvfLu3+Y2eV8e367Id3z5+6rdr
GhHfrvvx+PYxtm/XFCS+XUtR8e3ub/j2sbZv93HDt/vcx7f7GOLbfT3Ct7uN8O3DDp/Ybe+J
XU4P365pR3y71tzi20dZd2I/27ePquXea4Px7cMWPbF/7du1RBXfPl0T/jrS3+LbFWN8u9o6
vn08u367lrfi22t/KvbpWvHELnuGb1efjG+vfUu77/rtWk+Ob9dyXny7luri2x0jvl3r0vHt
6ifx7Rpb4tt9bPHt6v/x7VN1ZfHt03XXL+5BZvv2aQ9/95pPfLvGw/h2XYvj23XNim8X+45v
r88rds1X49v9W/j2Obdv1zkb3+72wrdPe3Xqbrmu+6Qd3/btWueMb58/9dv5d49d8e31t8R+
Xu3bp/383WtE8e3TNp7Y1Qfw7fPa9dvrO4l9+3YfB3z7dN11Ytc+4Nu9//h2Xffj2zXFjG+f
NufEvrZv19gY317bJHZbemK3OSf2a9dv9/6vxL7rt+tQxrfrXi++fbre+9PX5fh2NU98+7S9
J3Zb/e/p44Bvnz/126et++g1ovj2+vcc3c/x7WNt3+4+j28frq9Ojubbvt3nL77dfQnfPv23
V89J4tvnT/123QfFt7tv4Nunrfu79t8Su/o/vt3jDL7d7Ytv93l0pd23b/e4gW/3OXvNPXbh
23VPGt/uWPDtHk/Iyfo8uhL73b5dc5L4do3P8e26xsW312+Ro5FDJic7bNeft8cxcrK674hv
H7bx5Gi+7dt9/O+j5yrx7cN2ndh/fLtjISc77l2/ffz4ds1V4tu1Bh7fPuzMz56TXPfOzcW3
a0iNb6/fJXa1NTnZ4TrtiX20b6/fJXaN1fh2XePi28fY9duPZ/t2pXDi23VLH9+uJYD4dv8t
OdlxbN/ufU5O9vvat+uSE98+5mjfrjRSfHt9P7HP9u3juNq367oc3671k/h2XaLi25VvjW8/
XCue2NVnyMlqzhDfrvlGfPuoWu6cv9u3D9dIJ/a5fbtjJyfr85qc7Di2b9eSR3y75jPx7Vpq
uX5ystdPTja+3cc5OVkdw+Rk7d6J/ad+e23n7dxrfPtwPfmv56Lx7cO11o9eB4tv9/mYnKzO
weRkn9m+3XOh5GTv2b7d50tysjrOyck+T/t296vkZNfVvv0o616xnNu3K8UY3+4+8yUXv9q3
+5gkJ6vnNcjJ1nbIxc/Rvl3zz/h2LcPFt2vZLr79sEsfV7YT3364Ljq5+HW1b1cbxbcf792+
XX04vn34t7bBiG8/nrd9u/4T337Y1ScXP9u365jHtw97+LT7rt+u/hbfrn4V367jFt/ufSMn
q/M3vt2/2779aN9u64tvP12zvbyr3sER334+I759fv6315GmbnXw7VPmCt8+P9c8P+rzu+u3
TzvVWkuZ9pa1ljJ1+4Rvn6/qWpdv//vbrt8+P7t331dOGUJ8+3xca/2sz/27vreaT1n3u/7d
vn3aG9daytRtGL59vtu3T9264Nunav7j26dumfDtUz4T3z61jI5vr3hrLWV+Zd0rFtt1Yrdd
J3Z514vYr67fPl+79IrdhvYidhv1it2utdZS5mc/X7G/dvUVu01sraWwb/fVbVRrKWYZ+PZp
v1prKRVXraXMz6a9YnffqLWUqaV/fPuUEcK3T90W4ttNPfDtU+9TwLfznVntq5rVtZYyv7N9
+5Spw7fPzzXVfX8x9R4EfPv8dv32qVtTfPvUbWF8+7Hrt/993vXb12HTTrv7O8RuA0/srvFO
7HLsN7Grdje+XQYM3z71bhF8e/3tk9hXfPvUOzLw7eYv+Pb5Vc32uf+W2L/t2w/XZi/rK6sW
367byPh23bLi2+vYPon9aN9+uN57ne+H67E/P7GU9T28z8R+tm+v86LWUsxr8O1T70OJb9cQ
jG//2//27VMpn/j2Y23fftiol/GWN4hv17Upvn3s+u1mIvHtujbFt+tWGd8+lQqKb6/fqtg1
t4xvH64zX7GPqtlen5d1r8+/r337PLdvn3bj5Zw1z4xvH66jXuZz2I2Xd5326hX7qH/X53L4
+PbpuusVu+vP49uVc4lvn7brFft0bfaKXfdo8e38m8/P9u3T+1mxaz05vl3pgfh2MY74dtfY
x7fr1jG+XWmG+Pb5df12k5T49vqc2OUP8e26xY1v137Gt9f3id1+nthl5PDt0/Xey3wuO3li
t1ev2JctfcVe9d7Lu86367cv3bPEt0+b+cT+tG93vWt8e22/YlcaI77d+4Bvr88r9qqXXrG7
zja+fcmt4durXnrFXt+v2F0jHd/uWuL49qrNXrGf62jfLg4S3+5au/j2079VsddvVey67MW3
nz++3TW08e3n2L5dt9/x7a7Jj293zXx8+5rbt1fddWKX18W3a0oR315114ldbYRvX7Prty+9
JyK+Xbmw+Ha9EyG+3XXU8e1KI8W3a0kivn3dR/t23S/Ht1dtdmKXF8W3iyjFt1dteWLX5/h2
f45v121/fPtpi16xn7blk1i6fvvy+w7w7Ut+Fd9eddrLeFet+J92x7ef9vO0+zrat4slxbe7
3ji+Xf87vr3qyZf11RQqvt310lfafbRvr1rxZX1dHx7fvr6u3778HgF8u6ZZ8e2u84xvr5rq
xK5jjm8/7dLXtb9D7Nfbvl3LKPHt7rf4dh9nfLuPyXn/fJ52/9q3r7Lub7cLvr32n3a/un77
0q7Et5826hW727rWUtZlT16xu1Yzvt11v2stZV325MSuc7x8u58Ri293jfFaSzF7im93bW18
OzXb63nS0fXbV9VmJ3bXh6/Y9dw9vn3pOXp8+6p67xW7ppj4dvahjLdqX+Dba/9rLWVpyohv
X64jXWspS89Q49vX7VroxH62bzfVwrcvTTHx7X7mFN++XK/7JvZ3xLcvPXONb2f7FbvoFb7d
9ArfvhQqvn3puen49votYteYgG93vXp8u57Ljm/XlD2+3fXA8e1V85zYbeCJ3d8ndhvyWX1Y
17WH2Hf9dlM2fHu1b62l1JiMbz/vI7699vmh3dcX3760fIZvr3hrLcVcDN++Lu8DsduxE/vV
9dvreD7ErrZ+if1r3177XGspS1N5fPu6XI+d2K+u375u11Gv2G+b9or93r593fbqFfvjGu+0
u7dDuz/t283a8O1LXQ3fbtaGbzeDw7f/3e3e8e18/j77t4jd9r5iV5fFt5uv4dv9fCu+fSkt
im9fqmODb1/qdvj2dZ9dv/3vt0Z8u5+fxbfXvtVaip8jxrf//daKb//7zopvZ/vErnH7S+wr
vt3PO+Pb/0b7K77dzzjj2/3sJ76duL6OBd++7rvrty/XKT3S7k98uwkgvv1vCtO+3RwQ3/63
/Tu+/e93r/h2P+OMb/eztPh2P2uGb//7vH27jzm+/W+qcsS3+xkufPvSbQm+3c8C49v9DB2+
3c/B4dv9HDS+3c+04tt93PDt9f1Bu7v+ObHLlw5in12/fT3258Qug1e+fWkpE99uJohvN1vE
t//F1fXb/Ww1vn3pthDf/rfNL77dzwXj280r8e0mlfh2P7eOb2d/vrH3mdhlLCex628nff7q
+u21b5PYrxXfXm0xE/sV3179Ya5+rhDf7meQ8e1+9hnfvnQLjW/389H4dp+z+HY/P45vXxoi
8e1mnfh292d8u2sO4NuXhkh8O79L7LblxH60b6/2XcSu5xoWsevZh0Xsrp0+K0bVQl/ELqu8
6POu907scsgr7T7j29lm2n3Et1csi/P9fuPb2c+KXUsb+Pb12OpzvqufLGL3/n9j7zOxyxif
xF613GuMci33il3LHPh2j134do9L+PY6Viex28nT7jq2J7HLYZZvrz5/JvYzvt1sF99efb58
uykwvt31DfDtfh4W317nbPl2YiF2e3tiv9q3mwXj2/2cNb699v+i3XV+XbT7euPb6xiWbze/
xrebUOPbK/by7eu2e6/YfTwvYvdvEbuOQ/n2GlfLt5sa49vrPLro83f79jrXLmJ3LXpif9u3
+7lafLsJMr7dz27j22s7N7HL/d6JfcW3m2Lj28218e3VXjexa8wp31598qbdrxHfXn3mJnbX
iid2u3Ta3XXmb65ZK779b9+O+Pal6Re+vc7r8u2+puPb65iXb6+x5aHdtW8Pff4Z8e113pVv
X1q2w7fXPj/E7trpGetGfHv184fY1xHfXvv8EPsz49urHZ/E3r69+ttDu9uxP/saVL692q58
u2k4vt1sHd/+t82u327ajm+vdnyP3b7l26sfvsSuceYldl0XXmJXPy/fXtfZl9i9zYrd5+ZL
7N8d3+6aFfh2P7uNb/fP49vXY29ftWheG/WKXcuC+PalZUd8+9KUF99e1/qX2FfXb6/9+XK+
3/HtFddH7PbhFbv37UvsM769+uc399j1EbvGzI9217XpS+xHfDvfp91n+/Zq0y9j3RHfXsf/
o911Xfjo8+rD38/5/hG79+E7ug+Ub/d1Gd/uvopvd3/Dty/RQHy7r0f4do/z+Hb3Z3y7zxd8
+9KSPb7d5xe+fel2Dt/utsC3ezzEt/s8xbd7boBv93HGt7uL49tdBwbf7vET3+42wrfzu19f
x/HtHm7w7RXjIPb3jm/3OIZvdxvh2z184Ns93ODbl+pJ4tt9z4Jv97wX3/53fFZ8u+sp4dtX
1WMn9nvEt/v6i29nf4hdNWlH6i+d8e1//f+Mb/ecDd/uOjz4dp+D+HaPXfh2z0vx7a7xgm/3
dRbfXsdq0ufVvuXbXYsA3+7THt/u8Q3f7noj+PalXBu+3fUu8O3rtb1Pux/x7a5TgW+v41m+
3cMTvt31UvDt7DM1iFwfPjWIVny7z018u8d5fLuHfny75zn49r+2nvHtvuTg2z2/wrfzndSe
+uLbfe3At7veEb699nPR7q7H/tPuizo82n9yssoV4tv5W9pddndRi0Y2kppjbiNqjum6j2+v
tj6pv/S1b/e9D769+gA1xzQnx7f7Ootv95iJb3fdIXz73zZHfHsd2/PafZuaY7o/xbfXuU/N
MV328O2+VuLbfanDt/sygG/3dQHfXn2JmmMat8/UHPue+HaPjfh21xvBt1ffo+aY5jz49upj
1Bx7XWudGkTqz9Qc829d6fMrvn09Nupp9/btFdd193iOb6/jQ80x95/UHBtHfHu10fXudkzN
McdI7NcR3+46LWdqjskkU3PM7UXNMcd4/8R+z55Xn6k5pn6emmN312/3VAPf7msNvn0pj3+m
5piOQ2qO6Xmim7pbdunE/nX9drZP7Hf79oo3Nce8TWK/un6756749jrHu+ZY+/Zqo9Qce8/4
9urPT2pPHfHttZ+pOXbf8e01rqbmmMbe1BzT80rkZHV/jW+va1lqjslIp+aYfyt9fsa3V9/o
mmNHfHu1UWqO6bx4fvo8NcfkK/Dtf1OuGd++Xvtw2r2s+9N9gJzsYxtP7HpWJTXHdF6Tk/U+
pOaYxlVysq/NfM73N769zp039da6fjvbfHbfTs0xjRupOaZ5S2qOOS5qDL5vfLun4Ph231/g
26tvkJP1dZycrPshOVlfT8nJ6j4d3+55Gr69xnlysh6rycl67kFOVvfm+HbXeMS3V5/8dr01
fDu/Sx2e+cS3e/0K315jwvfuuUr59upj5GRrP4ld1vFInx/x7V5jxLd7zRPf7v6Mb/fYjm/3
PRS+3WP1lZpj3iaxy/Kl5pgd+3WkT+LbHTu+3W2Bb/f4g293/79Sc8yOfdccu1JzTDVayck+
NvbEfjzx7Z6X4tu9Voxv920tvt3XdHy760/i2z1fxbd7Ho5vr2NFTtbHhJzsM7t+u9sC3+6+
jW+v/SQnq3UJfLvHJXy7+y2+3eMDvt1jC77dfQDf7nME3+45Er7d4wy+3ecIvt3zeXy753v4
dt+C4ttr++Rkn6rZzrVpxbd7nolv970qvr3ajpxsfZ46e298u8fYKzXHzi++3XNFfLv7P77d
Yxe+3feJV9cca9/uWm349up75GR1juDba/9Tc0zONjXHdKxSc+zu+u11zMnJPvbqq++zrtQc
G2d8u6/jV2qOrTO+ne1fPe+6UnPMRj11t7749oqFnKzmsfh2j8P4dt/7XKk55hr11ByTz0zN
McWSmmNy8qk5drZvdw0xfLuvNfj26lfkZHUtw7f7PgLf7msQvr3O8dQcs7Gn5tjs+u2+pb9S
c2z7ds9PrtQcU33prjm24ttd4xHf7ltlfPvfd874di8N4Nu9xIBv9/0Fvr2ODznZxwae2L/2
7a4Xh293HTZ8e7UpOdnXNp7Yv/bt1RbkZD32kpP1OEZOtn6XPMXq+u117pCTdd8mJ/uuEd/+
F2PXb6/jTE5Wyzf4di/H4Ntr/CEn6/ORnKz77Z12f+Pbq5+Tk9X8Dd9eY+l99lwF3+61Mny7
rzv4ds+p8O11zMnJup/cyVPM+HbP+fHtnrvi2+s6RU5Wy4X4dt9T49u9pIhv97Igvn3dX/v2
2g45WR8TcrLPuOLbl/4M3760K/h259fw7c5L4ttr/H+Smxvx7Z434ttr7H2So2nfXufXk3Z/
4ts9t8e3e46Bb/eaPL7d82F8e43zb3I0Z3x7tSM5WV8XyMk+27fXGP7u/NSVnOw34tvrGL7k
JZ8jvr32MzlZXS/enZe8kpPV81adk+367c4LX8nJej/JyeoYdk72jm93fhDf7rnWlZys65kf
e4zqnGz79jrm5GQ9V/mSo+n67b6fvTon2749/+51Tnw726HdR9dvd93pKzlZ2/idn8K3s03a
3cb+IZYvvr3mSMnJuoY8fV7nKTlZzUnu5GSfL77dbXQnJ1v/vtKm+HYvo+PbvU18u+e6d3Ky
tui0u907ff5r3+59xrd7/nN3TrZ9O58T+9n12z3Pv5OTfUZ8u+8R8O3Oj+Pbfczx7bU/ycmO
Fd/uesX4dvfJ9u3ynPh2DUnx7WN1/falyxW+fbr+ML5dS3v4djPH+Pbj6PrtU4cb3z7U/Pj2
oW4R365pNL592KDi20Uk8e3DbrbWUsZX1v2pf8/49vHJo5ZvN1HFtw9d+/Dt47V1v+vzsu7+
/HMN9jLedsL4dtVIjG/XEm18u/1traUMW258++G4iP3dvl3T7vh218zHt3ub+PbDXp3YFRe+
Xcu78e1a9o1vV43E+HZ1zfh2e118u1Ls8e26RYlvVzo/vl3PZ8W3a6k0vl1LvfHtSrfHt9c2
yzlPe/iKfbi2/Mfnd/t2LY/GtysNH98+ju3btQwd365l1vj26VrrFfuY27cPO/Py7cN/W7Hb
/eLbHRe+vfahYneM+HZNu/HtU6n0+HbdTsS3D9dmr9h12xDfPl0fnthdQ57Ydazw7XpmM75d
twrx7eMd7dt1WxLfXp8T+9i+Xc8oxbfX9yv26drpxC4rXmspU/VM8O1//+767VNLyfHtej4U
3z6X671X7Mse/qlY1E8eYn+7fvuc9vAVu48bvl2cIr5dy9/49iniEN8urhrfPnf99im/im83
5cS3m1ri2+dpT16xywnj2/++M+Lb8++KReMPvr1+q2L38am1lCm3iW83zcS3z3V2/fZ52sxX
7Kf3x/cX5oP49nm5dnrFrndE4tun3tuCb5/yhPh2U0h8+19cXb99yq3h26fe94Fvn0pv49un
309RaylThg3fPvWOG3z7vFybvWK/XFu+Yr/8WxX7baNesevdQPj2qfeR4dvN/vDtJnr49uma
/LWWMm26ai1l2oyVb5+al+Lbp/I++Pap6zK+3cQQ3z5tzGotZeqeFN8+NXfFt//97RPfPnXa
49un7VmtpUzNXfHtpof49ikjhG/n84pd82R8u4khvn1qvoFvn48dfsX+uD58xa57W3z71D0y
vn3qNMC3z8dWfPD5Hd8+HzvzWc8f+TsVu6aS+Pb5ujb7yed3fPvUdQ3fPtXd8e1TqVl8+9S9
Ib59qlY/vn1WTfiKXfe8+Pb5uZ78u/b+V+yvjnmtpczX+8zzLHLUtZZiMohvn1XXvWLX1BDf
Pl1ze/Isj4x3raWYD+Lb/ewVvt3PmuHb/Ywbvr2O5yT2dcW3Tw0f+Hb+ltjrc547a98+Nczh
22fVkCd27zOxO0ZiV1vUWsqseubErn5Vaynzcy13YrdFJ3Z/f1Ysq+u3z2/7dj9rhm8308S3
Tw0f+Pap+3p8e/WBRew6trWWYqaJb2ebxF6m/exYai2l4l2JfcW3T78joNZSpoYzfHvtz0ns
6g8nsdu9/8ReaylTKXZ8+9/nI759fvbqxL66fjt/S+yuqX7uvl1rKXz/qlieL77dz9nh2/0M
Gr69+lWtpeTf746F2OVaT9pdBvskdlnTk9hdz7xi1/Nr8e06vePbq+563Vu5tjZrKRqS4tt1
yxHfPlyzffFM1te+vWqn13qC63Lj20UN4ttdW5u1FBEBfLvpany7a4CzlqLnduPbD9v7Wk/Q
bU98+6ExkLUU169mLcU1t1lL0TPm8e1Va30Q49e+XUNnfLvmqPHt3h/WUqoeO7GrvVhL0b1D
fLuPJ2sprhnOWkrVeyd2jb2spbgOea2lTF3S4tt1i4Vv/+uTo32769XXWoqfl4xvr3rvtLvt
N7Grn9daynSdfNZSqu46sWv7rKXoGWd8u5+1jG//qd/u5wfj23X5xLebI+Pbqx+yluK2Zi1F
z2XHt2teHd/u9wKwlqJn9OLbqzZ7xa66BPHten4/vn04lmp31wDHt09b9LqvVE2M+HbN8eLb
xSDi2/3sGGsp9bcVu2qOxbcP13uv2KfNfN1Tz7Prt5u6xrdr3hvfPr0PFbtYbXz7vLdv9zN0
rKXU9+ueWvUJ49v9XA9rKcsO/+OZu9m+XfPG+HY/h8Vaip49jG+f7/btS7GzljKrTjvP3G3f
rstJfLvSBvHtjpe1FF3G4tsdO2sposDx7bWfxK5nhVhLmc/27bqExLf7mLCW4mPCWoqfKWMt
xXVWWUtxjV/WUsSd49tVcyO+3XXIj8R+tW/XPUV8+xrbt+v4x7eLlcS3i4/Et+tyFd8uShLf
Lm4S365LZny7yG98+3Ld+IrdNWxZS1n28y/PZG3fvuRmWUtZtuK0u2uq0+6u5V6x+3dHYv/a
t4s1x7erX8W3r/ds337KQ+LbdVmNbxd/iW9f19m+vfaB2GUU8e3rx7cvm/xnx4Jv1/Qivl3s
Jr5dSz/x7WvXb/dzYfHt57F9+7IbH8TS9dtNruPbdd8U376u7dvdjvh27xu+3fuDb5929SfP
k77t232c8e3LddqJXYYZ367lp/j203Xan36eNL592d6/PFt3tG/3McS3n/LD+HYfH3y7mFF8
u9sC3+5Y8O2acsW3rx/fLkoV3y5uFd++7NJpd9d1J/ar67dXP19p97t9u8ao+Pb149vr+8T+
fe3bfZzx7brfj2932+Hb3Ub4dj23GN/uuM7E/rZvV6jx7f5dfLv7Er69vr/6edL4doUX3+7z
4ky7j/btSzYV3752/XY//xvf7nY5f9od376qZvvosQjf7mOLb9dzrPHtGtvj29Wc8e3eZ3y7
j/+VPr99+/y2b3c9any7az7j292H8e0e9/Dts2q5V4yuu54+/7Vvd7z49tP12In96vrtNY7h
27WeEN+uaXR8+2k///Gc6Wrf7vMd3+7v49vPc/t2TbXj2z0O4NtPm3PaXfuJb1/39u26LYlv
9zmOb1e3i2/Xc8rx7bpViG/Xek58e20/sXf99nW69jux67zAt9f30+7bty/HWLH7PMW3Lztz
+vzR9dtrm/h2jxX49uW668RetdzrmKi/4dtPm/n19liBb69tJvazffuye792jPh2n+P4dl8H
8e2OC9/u/o9vP9+u384+fMfeT9p9nu3bfQ7i2719fLuvp/h2n5v4dh8HfLtu8+LbNfTEt3t8
xre7j+HbT/v5k+vv1779VFvg292f8e0+nvj28+z67X5mP75dz4DHt2toi293H8O3+7qMb/fn
+HbHgm93X8W3u+/h208b9bGvy1/Guqd9u48bvt1jL77d4wy+3dcjfLvHAXz7sp+n3f192n10
/faaX+HbPUfCt69dv736Nr7dcxV8u/sJvt01h/Htrk+Ob1/H9u2ux4tvdy1lfPvc9dt9SY5v
d51tfLtrq+LbZ9Vsr3sK12wn9mu2b3ftaHx7/bvM5/zx7a5zjm9XDcz4dtcBxrfX9yt23YPE
t1eNd2KXZ8O3V631iv2nfrvvR+Lbp436YNz+2rfX9xP71b69arCXe3Ttbnz7tGk/WSvo+u1r
lHW/9+fEruOGb1edvfh2xzIS+9G+3bV28e31W8T+df12Tw3j211nGN/uGrwzsW/f7v3Ht48f
3+7t4Nu9P/h2ark/fazw7VUfPu3+tW+frvFesStvEt++5Gnx7dPbf/o6Ht/uuuX4dk2h4ttd
0xvfrqlhfHt9n9iPrt9e/Rzf7r6Hb3ffwLdXDXZi/7p+e7URvt3HDd8+7Mnp80/Xb6/2wre7
Ljq+fdrP0+6uwZ4+f7Rvd+16crLLtdmJXR4b3+4a4/h2zR/i27XEGd++ju3bdd8a3z7t0gfn
9WjfrnvA+HbXYca3690r8e1Vs512V1vg22ub1KJx7Xdiv6/27e4D+HbXKMa3+x0K+HbXi8a3
u73w7WrO+HaPXfh2vx8B3177zPnuOurEPu727T6X8e3TXp12lz3Gt7strl2HJ77dNeqvtPto
3+7+cKUG0fbtrpuNb699yFh3tW+f6j/4do9v+Pb549v9DgV8e32f2G31P+6jR/t25cLi231u
4tv9fXy73/WAb3eb4tu9fXy76gPHt/sdE/h292F8+7JdP5l3rfbtOg3i23VaxrfrmhXfvuzk
n77XiG9frglPLRp/JzWI7vbtFVdiP9q3a54W367TO7593du3n66XnhpET/t21ZyJb1+u976Y
pz3t25ete8Wu26T49mVXnz5/tG/38XlSf+ls375+fLvPX3z7LOvOvOtt3655SHy7ru/x7T6e
T2L/2rd7XMW3634qvl3zzPh2rWvFt+t2N75d93Tx7UoJxLevH9/u/cG3L9d7p911PPHt9W9i
t1FPux/t27X2Et/u8QrfrjlSfHvFQs0x9c/UHPPfUnfr6vrtdS586fNX+3a/6wTf7t/6Undr
tG/3PAff7vfRpOaYxrHUHNMzC11z7GzfrstnfPv88e1+D8L3c77j29ePb5+u2Z7Yt2+v33p/
Ykzsd/v2Ze/N+X53/XbPu66uOXa3b1cfiG9Xn4lvd11rfPsaXb/d903x7brcxrcrLRTfrstJ
fLvWHOLbdV7Et+ucim9X345vP70P1N2yn6fd5UtTc+zavl1tF9+ucye+fdqBE7v2H9/uGtH4
dtchx7e7VnZqjsk9jrT71b7dNcZHas297duV9otvX7t+u5dv4tt1vsS3a1oT3z5dNz59/mvf
7jZKzbGz67d7DSq+fZ3bt6/Z9du9phHfXnXdR4/b8e3LHp66W3bv8+52T80xHQd8u8bt+Hbv
J7592aXT52WGf2qOxbdPG/u71wTi29e3ffvpbe66W/HtmvrEt+veLb5dy0zx7Rpb4tuXDTmx
f9u3K+UZ366xPb59VS131va/9u1aw4xv11JafPvp7RO7XT19XnGl5ti1ffu567e7Nld8u2rG
xrfrHja+3edOao49d/t29//UHNM5uHb9pfh2pSHj20/XQqfmmH346DWi+PZl9546e2/7dk0r
49t9/FNzTLYT376u7dtr+9dux9Qcs10ndu8nsdvYP7Tj3b5dy23x7dexfbumSvHtmtLFt5/y
26k5to727Qo7vl3ruvHtWoeJb9eaT3y7jye+vbZD7HK/V+qtHe3b1Wzx7VqjiG/3eXql1txq
367mjG/3cSAnu+zYafej67fX2EhO1seHnKyPLTnZZbtOn7c/p89XzfbRYwI5WV1z49s9ZpKT
nU/Xb69zgZysxzdysrqPiG/3dYScrMcxcrLLddevr899crLT+7nzU/HtruF/Jze32rdr/hzf
Pp7t213HHt+uNEx8u985gm93vW5yskpvxLf7fRnkZDV0xre7pj05Wdf0Jifrd3yQk3VddHz7
KPdecw8dtye5ubt9u99nQU7W78UgJ+t3CjzJzb3t2/2+Enx7bZPcnOP6uM862rf7uOHb/d4K
crJKmcS3+5gnJ6t9w7frkhDf7vc7kJPVvWp8u48nvn3Yqycn+7Zvd/3/5GSPrt/u9ZD4dr8r
gZys4yIn6/YlJ1vbJy+pMZCcrN/98Sb2r337+PHtqtMY367LydU52bN9u48/OVkfq+RktX1y
sn7fSnKy6s/JyXqbxH4/7dt9HJKTnVf7dl1i49t9vUtO1nXaOd/1rBM52fl0/fY6X8jJrtn1
22sOQ05Wywrx7bq8xbdrP+PbtXYd3655Wny79iG+fdmQrz6v49tnWffOX8S3ax0svr1+61r7
t8jRHHf7do058e2a78W36xoa364lj7tzsnf7dq1LxLfX3xL76vrtXgO5Oyf7tW/XOYVv/+8/
hq9DP1PrJzrX/v+/v//xn3/+BfepuVNlbmRzdHJlYW0KZW5kb2JqCjYgMCBvYmoKODUyMjEK
ZW5kb2JqCjQgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNjEyIDc5Ml0KL1Jv
dGF0ZSA5MC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0K
L0V4dEdTdGF0ZSA5IDAgUgovRm9udCAxMCAwIFIKPj4KL0NvbnRlbnRzIDUgMCBSCj4+CmVu
ZG9iagozIDAgb2JqCjw8IC9UeXBlIC9QYWdlcyAvS2lkcyBbCjQgMCBSCl0gL0NvdW50IDEK
L1JvdGF0ZSA5MD4+CmVuZG9iagoxIDAgb2JqCjw8L1R5cGUgL0NhdGFsb2cgL1BhZ2VzIDMg
MCBSCi9NZXRhZGF0YSAxMSAwIFIKPj4KZW5kb2JqCjcgMCBvYmoKPDwvVHlwZS9FeHRHU3Rh
dGUKL09QTSAxPj5lbmRvYmoKOSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iagoxMCAwIG9i
ago8PC9SOAo4IDAgUj4+CmVuZG9iago4IDAgb2JqCjw8L0Jhc2VGb250L0hlbHZldGljYS9U
eXBlL0ZvbnQKL1N1YnR5cGUvVHlwZTE+PgplbmRvYmoKMTEgMCBvYmoKPDwvVHlwZS9NZXRh
ZGF0YQovU3VidHlwZS9YTUwvTGVuZ3RoIDEzNzA+PnN0cmVhbQo8P3hwYWNrZXQgYmVnaW49
J++7vycgaWQ9J1c1TTBNcENlaGlIenJlU3pOVGN6a2M5ZCc/Pgo8P2Fkb2JlLXhhcC1maWx0
ZXJzIGVzYz0iQ1JMRiI/Pgo8eDp4bXBtZXRhIHhtbG5zOng9J2Fkb2JlOm5zOm1ldGEvJyB4
OnhtcHRrPSdYTVAgdG9vbGtpdCAyLjkuMS0xMywgZnJhbWV3b3JrIDEuNic+CjxyZGY6UkRG
IHhtbG5zOnJkZj0naHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4LW5z
IycgeG1sbnM6aVg9J2h0dHA6Ly9ucy5hZG9iZS5jb20vaVgvMS4wLyc+CjxyZGY6RGVzY3Jp
cHRpb24gcmRmOmFib3V0PScyZmEwMWQ0Yi05ZjkxLTExZWItMDAwMC03OGEyODBmODU0M2Qn
IHhtbG5zOnBkZj0naHR0cDovL25zLmFkb2JlLmNvbS9wZGYvMS4zLycgcGRmOlByb2R1Y2Vy
PSdHUEwgR2hvc3RzY3JpcHQgOC42MycvPgo8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0n
MmZhMDFkNGItOWY5MS0xMWViLTAwMDAtNzhhMjgwZjg1NDNkJyB4bWxuczp4YXA9J2h0dHA6
Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8nIHhhcDpNb2RpZnlEYXRlPSdGcmkgLUFwLXIgVDE1
OiAxOjE6MjU6OjcgJyB4YXA6Q3JlYXRlRGF0ZT0nRnJpIC1BcC1yIFQxNTogMToxOjI1Ojo3
ICc+PHhhcDpDcmVhdG9yVG9vbD5nbnVwbG90IDQuMiBwYXRjaGxldmVsIDIgPC94YXA6Q3Jl
YXRvclRvb2w+PC9yZGY6RGVzY3JpcHRpb24+CjxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0
PScyZmEwMWQ0Yi05ZjkxLTExZWItMDAwMC03OGEyODBmODU0M2QnIHhtbG5zOnhhcE1NPSdo
dHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvbW0vJyB4YXBNTTpEb2N1bWVudElEPScyZmEw
MWQ0Yi05ZjkxLTExZWItMDAwMC03OGEyODBmODU0M2QnLz4KPHJkZjpEZXNjcmlwdGlvbiBy
ZGY6YWJvdXQ9JzJmYTAxZDRiLTlmOTEtMTFlYi0wMDAwLTc4YTI4MGY4NTQzZCcgeG1sbnM6
ZGM9J2h0dHA6Ly9wdXJsLm9yZy9kYy9lbGVtZW50cy8xLjEvJyBkYzpmb3JtYXQ9J2FwcGxp
Y2F0aW9uL3BkZic+PGRjOnRpdGxlPjxyZGY6QWx0PjxyZGY6bGkgeG1sOmxhbmc9J3gtZGVm
YXVsdCc+YnQtYnktbGFuLTEyOC4wLnBzPC9yZGY6bGk+PC9yZGY6QWx0PjwvZGM6dGl0bGU+
PGRjOmNyZWF0b3I+PHJkZjpTZXE+PHJkZjpsaT52aWpheTwvcmRmOmxpPjwvcmRmOlNlcT48
L2RjOmNyZWF0b3I+PC9yZGY6RGVzY3JpcHRpb24+CjwvcmRmOlJERj4KPC94OnhtcG1ldGE+
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKPD94cGFja2V0IGVuZD0n
dyc/PgplbmRzdHJlYW0KZW5kb2JqCjIgMCBvYmoKPDwvUHJvZHVjZXIoR1BMIEdob3N0c2Ny
aXB0IDguNjMpCi9DcmVhdGlvbkRhdGUoRnJpIEFwciAxNSAxMToyNTo0NyAyMDExKQovTW9k
RGF0ZShEOjIwMTEwNDE1MTEyNTQ3LTA0JzAwJykKL1RpdGxlKGJ0LWJ5LWxhbi0xMjguMC5w
cykKL0NyZWF0b3IoZ251cGxvdCA0LjIgcGF0Y2hsZXZlbCAyICkKL1N1YmplY3QoZ251cGxv
dCBwbG90KQovQXV0aG9yKHZpamF5KT4+ZW5kb2JqCnhyZWYKMCAxMgowMDAwMDAwMDAwIDY1
NTM1IGYgCjAwMDAwODU1NTYgMDAwMDAgbiAKMDAwMDA4NzIzMiAwMDAwMCBuIAowMDAwMDg1
NDg3IDAwMDAwIG4gCjAwMDAwODUzMjcgMDAwMDAgbiAKMDAwMDAwMDAxNSAwMDAwMCBuIAow
MDAwMDg1MzA2IDAwMDAwIG4gCjAwMDAwODU2MjEgMDAwMDAgbiAKMDAwMDA4NTcyMSAwMDAw
MCBuIAowMDAwMDg1NjYyIDAwMDAwIG4gCjAwMDAwODU2OTEgMDAwMDAgbiAKMDAwMDA4NTc4
NSAwMDAwMCBuIAp0cmFpbGVyCjw8IC9TaXplIDEyIC9Sb290IDEgMCBSIC9JbmZvIDIgMCBS
Ci9JRCBbPDAxN0RFNDIwRDhCRTg0RjlBRDlBM0I3NUJCNTlEMkM4PjwwMTdERTQyMEQ4QkU4
NEY5QUQ5QTNCNzVCQjU5RDJDOD5dCj4+CnN0YXJ0eHJlZgo4NzQ1NwolJUVPRgo=
--------------070306010205050007050901--

From jmedved@juniper.net  Fri Apr 15 09:59:03 2011
Return-Path: <jmedved@juniper.net>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 6E535130062 for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 09:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7daheuYsE8Ew for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 09:59:02 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfc.amsl.com (Postfix) with ESMTP id 0F748130060 for <alto@ietf.org>; Fri, 15 Apr 2011 09:59:01 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKTah5UzX3AWvRSu7FCwaXeivg8AHyvpOS@postini.com; Fri, 15 Apr 2011 09:59:02 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Fri, 15 Apr 2011 09:55:15 -0700
From: Jan Medved <jmedved@juniper.net>
To: Benjamin Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Fri, 15 Apr 2011 09:57:11 -0700
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: Acv7jeQbOxtUz1YiQaG5dL2/5U4Ttg==
Message-ID: <C9CDC38B.2263E%jmedved@juniper.net>
In-Reply-To: <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 16:59:03 -0000

Ben,

On 4/14/11 3:16 PM, "Benjamin Niven-Jenkins" <ben@niven-jenkins.co.uk>
wrote:

>>Standardizing the way to get network topology through ALTO will extend
>>ALTO's applicability rather than limit it. If ALTO does not define a
>>standardized way to generate maps from topology data, people will simply
>>use BGP (eventually with extensions that will convey the TE / IGP
>>topology
>>information), and bypass an ALTO Service that a provider may offer.
>
>But your draft (and any ALTO Server - Network API) doesn't address how to
>standardise the way to get topology through ALTO.

Fair enough. We do state that the way to get the topology through ALTO
should be standardized, though:

Section 4.1.1, Requirements, last paragraph:

"  In addition to having a standardized Server-to-Network interface, the
   algorithms for generation of ALTO network / cost maps and for
   endpoint ranking should be normalized as well, to facilitate inter-
   operability of different ALTO Server implementations.  "

The idea is to have the algorithm defined in a separate draft.



>It just proposes one possible way to get topology *into* an ALTO server.
>
Yes. And having done this a couple of times, I am convinced it is the
easiest way to do it ;-)



Thanks,
/Jan



From ben@niven-jenkins.co.uk  Fri Apr 15 10:10:55 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C406213002E for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 10:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.487
X-Spam-Level: 
X-Spam-Status: No, score=-103.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7AgEmZbSqbl for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 10:10:55 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.64]) by ietfc.amsl.com (Postfix) with ESMTP id C5C2913002D for <alto@ietf.org>; Fri, 15 Apr 2011 10:10:54 -0700 (PDT)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-108-devlan.cachelogic.com) by mail6.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1QAmXn-0006Rh-3o; Fri, 15 Apr 2011 18:10:55 +0100
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com>
Date: Fri, 15 Apr 2011 18:10:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6485E35C-0BF4-49DF-B43B-AC9EE87A263F@niven-jenkins.co.uk>
References: <C9CB0B72.22029%jmedved@juniper.net> <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 17:10:56 -0000

Rich,

On 15 Apr 2011, at 15:31, Woundy, Richard wrote:

> As a co-author of draft-medved-alto-svr-apis-00, let me explain my =
motivations for interest in this subject.
>=20
> My primary motivation is to have *some* scalable means to populate =
(my) ALTO servers with current network information. Note that I don't =
think there needs to be only ONE way to populate ALTO servers. Certainly =
it needs to be possible to use manual configuration as well. Maybe there =
is room for proprietary mechanisms as well -- perhaps ALTO server =
vendor-driven (eg unique routing ingest mechanisms and algorithms), =
perhaps ALTO server purchaser-driven (eg via open/proprietary APIs to =
the ALTO server).

The reason I do not think an ALTO Server - Network API needs to be =
specified in ALTO is not because I think ALTO servers do not need to =
extract topology from the network in a scalable way but because I see no =
Standards Track work for the ALTO WG to do to achieve that aim.

I could paraphrase the contents of draft-medved-alto-svr-apis-00 as "Go =
implement draft-gredler-bgp-te-00 and here are some reasons why BGP is =
good". Therefore the solution proposed is not really =
draft-medved-alto-svr-apis-00 it is draft-gredler-bgp-te-00.

As someone with a background in routing draft-medved-alto-svr-apis-00 =
adds nothing to draft-gredler-bgp-te-00 and certainly nothing that =
warrants the status of a Standards Track document.

Now, I guess given ALTO is not in the Routing Area there may be folks in =
ALTO who are not routing experts and some level of informational =
material explaining how routing can be used to obtain topology may be =
useful, but that's an Informational document at best (it could be a BCP =
once there's some real world experience of doing it).

> My secondary motivation is to ensure that, with respect to automated =
population of network information into ALTO servers, I could choose ALTO =
server vendors and router vendors fairly independently. That's why the =
use of a common protocol (BGP) is of interest, because it is commonly =
implemented by router vendors and commonly deployed by service =
providers. We had talked a long time ago in ALTO about using "looking =
glass servers" as a potential network information source, and usually =
looking glass servers are based on BGP routes.

No objection there. ISIS and OSPF are also commonly implemented by =
router vendors and commonly deployed by service providers :-) In my mind =
a Standards Track document coming out of ALTO that says "The answer is =
to load everything in BGP" sets the precedent that the IETF 'mandated' =
way to do it loading your IGP into BGP, when IMO that is one possible =
way that is likely to suit some but not all service providers.
=20
> That's why I am interested in an open specification for an ALTO server =
to network API.

IMO those open specifications exist in the form of the RFCs that =
describe existing (and future) routing protocols and extensions.

To summarise my position:
- I believe that passively listening to routing is a reasonable =
approach.
- I do not believe there is Standards Track work for the ALTO WG to do =
to describe how to passively listen to a routing protocol. If ALTO =
generates additional requirements that cannot be met by existing =
roputing protocols ALTO could specify those and take them to the =
appropriate Routing Area WG to produce a solution. I think =
draft-medved-alto-svr-apis-00 clearly demonstrates that as it contains =
no protocol specification at all and leaves all that to =
draft-gredler-bgp-te-00 which can be taken up with the IDR WG.

> -- Rich
>=20
> P.S. I don't think ALTO servers need to listen to BGP *and* the IGP.

I think this really depends on the particular service provider's =
network. When I look at how service providers are requesting automatic =
topology import into our CDN product  some are requesting ALTO, some are =
requesting just BGP and some are certainly requesting that we listen to =
both BGP and the IGP.

Ben


From robert@raszuk.net  Fri Apr 15 10:15:39 2011
Return-Path: <robert@raszuk.net>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C9D2A13007C for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 10:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOvHsNAq+itw for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 10:15:39 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfc.amsl.com (Postfix) with ESMTP id 707B1130067 for <alto@ietf.org>; Fri, 15 Apr 2011 10:15:38 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwBAAF8qE2rRDoI/2dsb2JhbACYCo1/d4hvnxmdB4VuBI14g3Q
X-IronPort-AV: E=Sophos;i="4.64,220,1301875200"; d="scan'208";a="431084763"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-1.cisco.com with ESMTP; 15 Apr 2011 17:15:37 +0000
Received: from [192.168.1.51] (ams-raszuk-2-87113.cisco.com [10.55.99.78]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3FHFZB7004931; Fri, 15 Apr 2011 17:15:36 GMT
Message-ID: <4DA87D30.3070503@raszuk.net>
Date: Fri, 15 Apr 2011 19:15:28 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
References: <C9CB0B72.22029%jmedved@juniper.net>	<87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com> <4DA85F5D.3050402@raszuk.net> <1CA25301D2219F40B3AA37201F0EACD1134E8271@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <1CA25301D2219F40B3AA37201F0EACD1134E8271@PACDCEXMB05.cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 17:15:40 -0000

To clarify .. I was not mixing two things. I was only referring to ALTO
server-to-network part in my last two posts.

So to conclude my opinion is:

- ALTO client to server protocol - required

- ALTO server to network protocol - not needed

- ALTO server to server spec - perhaps required, but only to define 
server to server network map abstraction such that two ALTO servers from 
different vendors could exchange/share their maps. Useful especially in 
the inter-domain applications (example: CDNs).

Rgs,
R.


> I think you are mixing two things together, that I see as
> independent.
>
>> But do you need to have a RFC which mandates support of BGP-TE spec
>> by an ALTO server ? How about ALTO vendors which not have BGP code
>> at all today ?
>
> There is a ALTO client-to-server protocol spec. There is a ALTO
> server-to-network protocol spec. They should be independently
> specified, and can be independently implemented.
>
> If you want to build a ALTO server that follows only the
> client-to-server protocol spec, go ahead. There is probably a market
> for a product like this. This shouldn't be prohibited.
>
> I think there are a number of parties that want an ALTO server that
> would follow specifications for both client-to-server and
> server-to-network protocols.
>
>> I could really easily imagine an ALTO vendor which does not support
>> BGP and collects network information (both routing and non-routing
>> related) via their own self discovering application modules running
>> on all or on subset of routers of given network.
>
> So in other words, I need to deploy "application modules" on my
> routers for your approach to work. And if your application modules
> didn't run on my routers, I have to replace my routers to enable ALTO
> support in my network. Hmmm.
>
>> And on the other hand if you want to choose a particular
>> deployment
> model you can select ALTO server vendor which does support BGP-TE
> RFC XYZ.
>
> Yes we could. The question is what needs to be carried in BGP-TE to
> be useful to ALTO servers. That's where the interoperability concerns
> arise, and where an open specification is needed.
>
> -- Rich
>
> -----Original Message----- From: Robert Raszuk
> [mailto:robert@raszuk.net] Sent: Friday, April 15, 2011 11:08 AM To:
> Woundy, Richard Cc: Benjamin Niven-Jenkins; Jan Medved;
> alto@ietf.org Subject: Re: [alto] Do we need to standardise an ALTO
> Server to Network API?
>
> Hi Richard,
>
>> My secondary motivation is to ensure that, with respect to
>> automated population of network information into ALTO servers, I
>> could choose ALTO server vendors and router vendors fairly
>> independently.
>
> But do you need to have a RFC which mandates support of BGP-TE spec
> by an ALTO server ?
>
> How about ALTO vendors which not have BGP code at all today ?
>
> Are they out of luck to even propose ALTO servers ? I could really
> easily imagine an ALTO vendor which does not support BGP and
> collects network information (both routing and non-routing related)
> via their own self discovering application modules running on all or
> on subset of routers of given network. Result: no need to configure
> and maintain dozens if not more of BGP sessions both on the ALTO
> server as well as on the routers, no need to support BGP or IGP on
> ALTO server side.
>
> And on the other hand if you want to choose a particular deployment
> model you can select ALTO server vendor which does support BGP-TE
> RFC XYZ. Just like today when you are buying routers or other
> network devices you just make sure they speak the same language as
> described in the protocol RFC XYZ. No need for another API spec to
> mandate support of RFC XYZ.
>
> Cheers, R.
>
>
>
>
>
>
>


From richard_woundy@cable.comcast.com  Fri Apr 15 10:40:23 2011
Return-Path: <richard_woundy@cable.comcast.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 197D3E06B2 for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 10:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.417
X-Spam-Level: 
X-Spam-Status: No, score=-103.417 tagged_above=-999 required=5 tests=[AWL=-1.682, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PzgNVvpRGR-d for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 10:40:22 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfc.amsl.com (Postfix) with ESMTP id 05FBFE067E for <alto@ietf.org>; Fri, 15 Apr 2011 10:40:11 -0700 (PDT)
Received: from ([24.40.55.41]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.34150160; Fri, 15 Apr 2011 11:43:22 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0270.001; Fri, 15 Apr 2011 13:40:07 -0400
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: AQHL+c6LkCewQmYft0q5jprYZPNCL5Rcu78AgAF22wCAAMJEMIAAergA//+/75A=
Date: Fri, 15 Apr 2011 17:40:07 +0000
Message-ID: <1CA25301D2219F40B3AA37201F0EACD1134E860E@PACDCEXMB05.cable.comcast.com>
References: <C9CB0B72.22029%jmedved@juniper.net> <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com> <6485E35C-0BF4-49DF-B43B-AC9EE87A263F@niven-jenkins.co.uk>
In-Reply-To: <6485E35C-0BF4-49DF-B43B-AC9EE87A263F@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [76.96.111.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 17:40:23 -0000

> I see no Standards Track work for the ALTO WG to do to achieve that aim.

My opinion: I do agree that this work is outside the scope of the current A=
LTO charter.

I think the essential question is whether this effort should be captured in=
 an ALTO re-charter. It seems we will have diverging opinions there. I'll d=
efer to the WG chairs to figure out how to determine consensus or lack ther=
eof.

> I could paraphrase the contents of draft-medved-alto-svr-apis-00 as "Go i=
mplement draft-gredler-bgp-te-00 and here are some reasons why BGP is good"=
. Therefore the solution proposed is not really draft-medved-alto-svr-apis-=
00 it is draft-gredler-bgp-te-00.

Well, I agree, sort of. draft-medved-* is just a motivation document at thi=
s time, eg why we want it, what we think are the requirements. draft-gredle=
r-* defines the new BGP encodings but doesn't say much how an ALTO server w=
ould leverage that information. draft-gredler-* also is concerned with MPLS=
-TE, which is way outside the scope of ALTO.

A third document is needed (or significant updates to the other two) to say=
 how an ALTO server would consume and react to the BGP TE information.

But right now there doesn't seem to be a forum for this discussion. It is n=
ot in scope for ALTO yet (my opinion), and it seems that IDR is not the ide=
al forum.

> If ALTO generates additional requirements that cannot be met by existing =
[routing] protocols ALTO could specify those and take them to the appropria=
te Routing Area WG to produce a solution.

That is a possible approach.

> I think draft-medved-alto-svr-apis-00 clearly demonstrates that as it con=
tains no protocol specification at all and leaves all that to draft-gredler=
-bgp-te-00 which can be taken up with the IDR WG.

Sigh. It might also clearly demonstrate that the protocol specification wor=
k to make BGP TE work specifically with ALTO servers hasn't started yet. An=
d that draft-medved-alto-svr-apis-00 is written as a motivational (use case=
 / requirements) document not as a standards track protocol document.

I guess we might have to agree to disagree.

-- Rich

-----Original Message-----
From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk]=20
Sent: Friday, April 15, 2011 1:11 PM
To: Woundy, Richard
Cc: Jan Medved; alto@ietf.org
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API=
?

Rich,

On 15 Apr 2011, at 15:31, Woundy, Richard wrote:

> As a co-author of draft-medved-alto-svr-apis-00, let me explain my motiva=
tions for interest in this subject.
>=20
> My primary motivation is to have *some* scalable means to populate (my) A=
LTO servers with current network information. Note that I don't think there=
 needs to be only ONE way to populate ALTO servers. Certainly it needs to b=
e possible to use manual configuration as well. Maybe there is room for pro=
prietary mechanisms as well -- perhaps ALTO server vendor-driven (eg unique=
 routing ingest mechanisms and algorithms), perhaps ALTO server purchaser-d=
riven (eg via open/proprietary APIs to the ALTO server).

The reason I do not think an ALTO Server - Network API needs to be specifie=
d in ALTO is not because I think ALTO servers do not need to extract topolo=
gy from the network in a scalable way but because I see no Standards Track =
work for the ALTO WG to do to achieve that aim.

I could paraphrase the contents of draft-medved-alto-svr-apis-00 as "Go imp=
lement draft-gredler-bgp-te-00 and here are some reasons why BGP is good". =
Therefore the solution proposed is not really draft-medved-alto-svr-apis-00=
 it is draft-gredler-bgp-te-00.

As someone with a background in routing draft-medved-alto-svr-apis-00 adds =
nothing to draft-gredler-bgp-te-00 and certainly nothing that warrants the =
status of a Standards Track document.

Now, I guess given ALTO is not in the Routing Area there may be folks in AL=
TO who are not routing experts and some level of informational material exp=
laining how routing can be used to obtain topology may be useful, but that'=
s an Informational document at best (it could be a BCP once there's some re=
al world experience of doing it).

> My secondary motivation is to ensure that, with respect to automated popu=
lation of network information into ALTO servers, I could choose ALTO server=
 vendors and router vendors fairly independently. That's why the use of a c=
ommon protocol (BGP) is of interest, because it is commonly implemented by =
router vendors and commonly deployed by service providers. We had talked a =
long time ago in ALTO about using "looking glass servers" as a potential ne=
twork information source, and usually looking glass servers are based on BG=
P routes.

No objection there. ISIS and OSPF are also commonly implemented by router v=
endors and commonly deployed by service providers :-) In my mind a Standard=
s Track document coming out of ALTO that says "The answer is to load everyt=
hing in BGP" sets the precedent that the IETF 'mandated' way to do it loadi=
ng your IGP into BGP, when IMO that is one possible way that is likely to s=
uit some but not all service providers.
=20
> That's why I am interested in an open specification for an ALTO server to=
 network API.

IMO those open specifications exist in the form of the RFCs that describe e=
xisting (and future) routing protocols and extensions.

To summarise my position:
- I believe that passively listening to routing is a reasonable approach.
- I do not believe there is Standards Track work for the ALTO WG to do to d=
escribe how to passively listen to a routing protocol. If ALTO generates ad=
ditional requirements that cannot be met by existing roputing protocols ALT=
O could specify those and take them to the appropriate Routing Area WG to p=
roduce a solution. I think draft-medved-alto-svr-apis-00 clearly demonstrat=
es that as it contains no protocol specification at all and leaves all that=
 to draft-gredler-bgp-te-00 which can be taken up with the IDR WG.

> -- Rich
>=20
> P.S. I don't think ALTO servers need to listen to BGP *and* the IGP.

I think this really depends on the particular service provider's network. W=
hen I look at how service providers are requesting automatic topology impor=
t into our CDN product  some are requesting ALTO, some are requesting just =
BGP and some are certainly requesting that we listen to both BGP and the IG=
P.

Ben


From richard_woundy@cable.comcast.com  Fri Apr 15 10:51:49 2011
Return-Path: <richard_woundy@cable.comcast.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DDE4CE0865 for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 10:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.856
X-Spam-Level: 
X-Spam-Status: No, score=-102.856 tagged_above=-999 required=5 tests=[AWL=-1.121, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3zgUbpOzdMLL for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 10:51:49 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfc.amsl.com (Postfix) with ESMTP id DEEADE086D for <alto@ietf.org>; Fri, 15 Apr 2011 10:51:48 -0700 (PDT)
Received: from ([24.40.55.40]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.34153075; Fri, 15 Apr 2011 11:54:51 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0270.001; Fri, 15 Apr 2011 13:51:43 -0400
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: AQHL+c6LkCewQmYft0q5jprYZPNCL5Rcu78AgAF22wCAAMJEMIAAergA///FnYA=
Date: Fri, 15 Apr 2011 17:51:42 +0000
Message-ID: <1CA25301D2219F40B3AA37201F0EACD1134E862E@PACDCEXMB05.cable.comcast.com>
References: <C9CB0B72.22029%jmedved@juniper.net> <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com> <6485E35C-0BF4-49DF-B43B-AC9EE87A263F@niven-jenkins.co.uk>
In-Reply-To: <6485E35C-0BF4-49DF-B43B-AC9EE87A263F@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [76.96.111.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 17:51:50 -0000

One last set of comments.

> I do not believe there is Standards Track work for the ALTO WG to do to d=
escribe how to passively listen to a routing protocol.

I could be persuaded to your point of view, if it can be shown that passive=
ly listening to one or more routing protocol(s) is sufficient for interoper=
able network information updates and distribution from routers to ALTO serv=
ers. And I suppose in return, you will expect someone to document why passi=
ve listening is not sufficient, which would be a fair pushback.

If folks are suggesting that service providers need to load a proprietary a=
pplication module on their routers to get network information into their AL=
TO servers, then I will be very un-persuaded. And very unhappy.

-- Rich

-----Original Message-----
From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk]=20
Sent: Friday, April 15, 2011 1:11 PM
To: Woundy, Richard
Cc: Jan Medved; alto@ietf.org
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API=
?

Rich,

On 15 Apr 2011, at 15:31, Woundy, Richard wrote:

> As a co-author of draft-medved-alto-svr-apis-00, let me explain my motiva=
tions for interest in this subject.
>=20
> My primary motivation is to have *some* scalable means to populate (my) A=
LTO servers with current network information. Note that I don't think there=
 needs to be only ONE way to populate ALTO servers. Certainly it needs to b=
e possible to use manual configuration as well. Maybe there is room for pro=
prietary mechanisms as well -- perhaps ALTO server vendor-driven (eg unique=
 routing ingest mechanisms and algorithms), perhaps ALTO server purchaser-d=
riven (eg via open/proprietary APIs to the ALTO server).

The reason I do not think an ALTO Server - Network API needs to be specifie=
d in ALTO is not because I think ALTO servers do not need to extract topolo=
gy from the network in a scalable way but because I see no Standards Track =
work for the ALTO WG to do to achieve that aim.

I could paraphrase the contents of draft-medved-alto-svr-apis-00 as "Go imp=
lement draft-gredler-bgp-te-00 and here are some reasons why BGP is good". =
Therefore the solution proposed is not really draft-medved-alto-svr-apis-00=
 it is draft-gredler-bgp-te-00.

As someone with a background in routing draft-medved-alto-svr-apis-00 adds =
nothing to draft-gredler-bgp-te-00 and certainly nothing that warrants the =
status of a Standards Track document.

Now, I guess given ALTO is not in the Routing Area there may be folks in AL=
TO who are not routing experts and some level of informational material exp=
laining how routing can be used to obtain topology may be useful, but that'=
s an Informational document at best (it could be a BCP once there's some re=
al world experience of doing it).

> My secondary motivation is to ensure that, with respect to automated popu=
lation of network information into ALTO servers, I could choose ALTO server=
 vendors and router vendors fairly independently. That's why the use of a c=
ommon protocol (BGP) is of interest, because it is commonly implemented by =
router vendors and commonly deployed by service providers. We had talked a =
long time ago in ALTO about using "looking glass servers" as a potential ne=
twork information source, and usually looking glass servers are based on BG=
P routes.

No objection there. ISIS and OSPF are also commonly implemented by router v=
endors and commonly deployed by service providers :-) In my mind a Standard=
s Track document coming out of ALTO that says "The answer is to load everyt=
hing in BGP" sets the precedent that the IETF 'mandated' way to do it loadi=
ng your IGP into BGP, when IMO that is one possible way that is likely to s=
uit some but not all service providers.
=20
> That's why I am interested in an open specification for an ALTO server to=
 network API.

IMO those open specifications exist in the form of the RFCs that describe e=
xisting (and future) routing protocols and extensions.

To summarise my position:
- I believe that passively listening to routing is a reasonable approach.
- I do not believe there is Standards Track work for the ALTO WG to do to d=
escribe how to passively listen to a routing protocol. If ALTO generates ad=
ditional requirements that cannot be met by existing roputing protocols ALT=
O could specify those and take them to the appropriate Routing Area WG to p=
roduce a solution. I think draft-medved-alto-svr-apis-00 clearly demonstrat=
es that as it contains no protocol specification at all and leaves all that=
 to draft-gredler-bgp-te-00 which can be taken up with the IDR WG.

> -- Rich
>=20
> P.S. I don't think ALTO servers need to listen to BGP *and* the IGP.

I think this really depends on the particular service provider's network. W=
hen I look at how service providers are requesting automatic topology impor=
t into our CDN product  some are requesting ALTO, some are requesting just =
BGP and some are certainly requesting that we listen to both BGP and the IG=
P.

Ben


From robert@raszuk.net  Fri Apr 15 13:37:08 2011
Return-Path: <robert@raszuk.net>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 61431E06A4 for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 13:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2TLIkpzAgxH for <alto@ietfc.amsl.com>; Fri, 15 Apr 2011 13:37:07 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfc.amsl.com (Postfix) with ESMTP id AA511E067F for <alto@ietf.org>; Fri, 15 Apr 2011 13:37:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAM2rqE2rRDoI/2dsb2JhbACmCXeIb58GnQiFbgSNeIN0
X-IronPort-AV: E=Sophos;i="4.64,221,1301875200"; d="scan'208";a="338666888"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-2.cisco.com with ESMTP; 15 Apr 2011 20:37:07 +0000
Received: from [192.168.1.66] (sjc-raszuk-87113.cisco.com [10.20.147.254]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3FKb5lu030640; Fri, 15 Apr 2011 20:37:06 GMT
Message-ID: <4DA8AC78.3070808@raszuk.net>
Date: Fri, 15 Apr 2011 22:37:12 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
References: <C9CB0B72.22029%jmedved@juniper.net>	<87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk>	<1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com>	<6485E35C-0BF4-49DF-B43B-AC9EE87A263F@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E862E@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <1CA25301D2219F40B3AA37201F0EACD1134E862E@PACDCEXMB05.cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 20:37:08 -0000

Rich,

> One last set of comments.

Likewise :)

>> I do not believe there is Standards Track work for the ALTO WG to
>> do to describe how to passively listen to a routing protocol.
>
> I could be persuaded to your point of view, if it can be shown that
> passively listening to one or more routing protocol(s) is sufficient
> for interoperable network information updates and distribution from
> routers to ALTO servers. And I suppose in return, you will expect
> someone to document why passive listening is not sufficient, which
> would be a fair pushback.

But BGP-TE is a clear example of passive listening.

> If folks are suggesting that service providers need to load a
> proprietary application module on their routers to get network
> information into their ALTO servers, then I will be very
> un-persuaded. And very unhappy.

I did not mean at all that such module should be proprietary. It should 
come with ALTO server for wide vendor's range of routing platforms.

Cheers,
R.

From dave.mcdysan@verizon.com  Mon Apr 18 07:21:04 2011
Return-Path: <dave.mcdysan@verizon.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 45343E06D6 for <alto@ietfc.amsl.com>; Mon, 18 Apr 2011 07:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.321
X-Spam-Level: 
X-Spam-Status: No, score=-3.321 tagged_above=-999 required=5 tests=[AWL=0.278,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNpSnv+vMRLQ for <alto@ietfc.amsl.com>; Mon, 18 Apr 2011 07:21:00 -0700 (PDT)
Received: from sacmail2.verizon.com (sacmail2.verizon.com [192.76.84.41]) by ietfc.amsl.com (Postfix) with ESMTP id 21447E0703 for <alto@ietf.org>; Mon, 18 Apr 2011 07:20:52 -0700 (PDT)
Received: from fldsmtpi03.verizon.com (fldsmtpi03.verizon.com [166.68.71.145]) by sacmail2.verizon.com (8.13.7+Sun/8.13.3) with ESMTP id p3IEKpJ3029927 for <alto@ietf.org>; Mon, 18 Apr 2011 10:20:52 -0400 (EDT)
From: "Mcdysan, David E" <dave.mcdysan@verizon.com>
X-IronPort-AV: E=Sophos;i="4.64,232,1301875200"; d="scan'208";a="32425064"
Received: from fhdp1lumxc7hb02.verizon.com (HELO FHDP1LUMXC7HB02.us.one.verizon.com) ([166.68.59.189]) by fldsmtpi03.verizon.com with ESMTP; 18 Apr 2011 14:20:51 +0000
Received: from fhdp1lumxc7v11.us.one.verizon.com ([169.254.1.15]) by FHDP1LUMXC7HB02.us.one.verizon.com ([2002:a644:3bbd::a644:3bbd]) with mapi; Mon, 18 Apr 2011 10:20:51 -0400
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Mon, 18 Apr 2011 10:20:48 -0400
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: Acv909HLCLFHOx1vRqCxkNa4PdWknA==
Message-ID: <C9D1BFA2.1430C%dave.mcdysan@one.verizon.com>
In-Reply-To: <1CA25301D2219F40B3AA37201F0EACD1134E860E@PACDCEXMB05.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.1.0.101012
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2011 14:21:04 -0000

As a co-author of draft-medved-alto-svr-apis-00, I have some responses to
this thread in line below.

Thanks,

Dave


On Friday4/15/11 1:40 PM, "Woundy, Richard"
<Richard_Woundy@cable.comcast.com> wrote:

>> I see no Standards Track work for the ALTO WG to do to achieve that aim.
>
>My opinion: I do agree that this work is outside the scope of the current
>ALTO charter.
>
>I think the essential question is whether this effort should be captured
>in an ALTO re-charter. It seems we will have diverging opinions there.
>I'll defer to the WG chairs to figure out how to determine consensus or
>lack thereof.
>
>> I could paraphrase the contents of draft-medved-alto-svr-apis-00 as "Go
>>implement draft-gredler-bgp-te-00 and here are some reasons why BGP is
>>good". Therefore the solution proposed is not really
>>draft-medved-alto-svr-apis-00 it is draft-gredler-bgp-te-00.
>
>Well, I agree, sort of. draft-medved-* is just a motivation document at
>this time, eg why we want it, what we think are the requirements.
>draft-gredler-* defines the new BGP encodings but doesn't say much how an
>ALTO server would leverage that information. draft-gredler-* also is
>concerned with MPLS-TE, which is way outside the scope of ALTO.

I think the following summary is more accurate than the above:

Note that section 4.1.1 is requirements, and states all of them as
"should" (I.e., SHOULD) and are not mandatory.

Section 4.1.2 describes A solution that meets many of the desirable
requirements.=20

>
>A third document is needed (or significant updates to the other two) to
>say how an ALTO server would consume and react to the BGP TE information.
>
>But right now there doesn't seem to be a forum for this discussion. It is
>not in scope for ALTO yet (my opinion), and it seems that IDR is not the
>ideal forum.
>
>> If ALTO generates additional requirements that cannot be met by
>>existing [routing] protocols ALTO could specify those and take them to
>>the appropriate Routing Area WG to produce a solution.
>
>That is a possible approach.
>
>> I think draft-medved-alto-svr-apis-00 clearly demonstrates that as it
>>contains no protocol specification at all and leaves all that to
>>draft-gredler-bgp-te-00 which can be taken up with the IDR WG.
>
>Sigh. It might also clearly demonstrate that the protocol specification
>work to make BGP TE work specifically with ALTO servers hasn't started
>yet. And that draft-medved-alto-svr-apis-00 is written as a motivational
>(use case / requirements) document not as a standards track protocol
>document.
>
>I guess we might have to agree to disagree.

I agree with Rich that the use case/ requirements is separable from the
protocol specifics.

Ben, would separating these address what appears to be one of your major
comments?

I suggest that we first focus on the requirements and where that work is
best chartered.=20

>
>-- Rich
>
>-----Original Message-----
>From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk]
>Sent: Friday, April 15, 2011 1:11 PM
>To: Woundy, Richard
>Cc: Jan Medved; alto@ietf.org
>Subject: Re: [alto] Do we need to standardise an ALTO Server to Network
>API?
>
>Rich,
>
>On 15 Apr 2011, at 15:31, Woundy, Richard wrote:
>
>> As a co-author of draft-medved-alto-svr-apis-00, let me explain my
>>motivations for interest in this subject.
>>=20
>> My primary motivation is to have *some* scalable means to populate (my)
>>ALTO servers with current network information. Note that I don't think
>>there needs to be only ONE way to populate ALTO servers. Certainly it
>>needs to be possible to use manual configuration as well. Maybe there is
>>room for proprietary mechanisms as well -- perhaps ALTO server
>>vendor-driven (eg unique routing ingest mechanisms and algorithms),
>>perhaps ALTO server purchaser-driven (eg via open/proprietary APIs to
>>the ALTO server).
>
>The reason I do not think an ALTO Server - Network API needs to be
>specified in ALTO is not because I think ALTO servers do not need to
>extract topology from the network in a scalable way but because I see no
>Standards Track work for the ALTO WG to do to achieve that aim.
>
>I could paraphrase the contents of draft-medved-alto-svr-apis-00 as "Go
>implement draft-gredler-bgp-te-00 and here are some reasons why BGP is
>good". Therefore the solution proposed is not really
>draft-medved-alto-svr-apis-00 it is draft-gredler-bgp-te-00.
>
>As someone with a background in routing draft-medved-alto-svr-apis-00
>adds nothing to draft-gredler-bgp-te-00 and certainly nothing that
>warrants the status of a Standards Track document.
>
>Now, I guess given ALTO is not in the Routing Area there may be folks in
>ALTO who are not routing experts and some level of informational material
>explaining how routing can be used to obtain topology may be useful, but
>that's an Informational document at best (it could be a BCP once there's
>some real world experience of doing it).
>
>> My secondary motivation is to ensure that, with respect to automated
>>population of network information into ALTO servers, I could choose ALTO
>>server vendors and router vendors fairly independently. That's why the
>>use of a common protocol (BGP) is of interest, because it is commonly
>>implemented by router vendors and commonly deployed by service
>>providers. We had talked a long time ago in ALTO about using "looking
>>glass servers" as a potential network information source, and usually
>>looking glass servers are based on BGP routes.
>
>No objection there. ISIS and OSPF are also commonly implemented by router
>vendors and commonly deployed by service providers :-) In my mind a
>Standards Track document coming out of ALTO that says "The answer is to
>load everything in BGP" sets the precedent that the IETF 'mandated' way
>to do it loading your IGP into BGP, when IMO that is one possible way
>that is likely to suit some but not all service providers.
>=20
>> That's why I am interested in an open specification for an ALTO server
>>to network API.
>
>IMO those open specifications exist in the form of the RFCs that describe
>existing (and future) routing protocols and extensions.
>
>To summarise my position:
>- I believe that passively listening to routing is a reasonable approach.
>- I do not believe there is Standards Track work for the ALTO WG to do to
>describe how to passively listen to a routing protocol. If ALTO generates
>additional requirements that cannot be met by existing roputing protocols
>ALTO could specify those and take them to the appropriate Routing Area WG
>to produce a solution. I think draft-medved-alto-svr-apis-00 clearly
>demonstrates that as it contains no protocol specification at all and
>leaves all that to draft-gredler-bgp-te-00 which can be taken up with the
>IDR WG.
>
>> -- Rich
>>=20
>> P.S. I don't think ALTO servers need to listen to BGP *and* the IGP.
>
>I think this really depends on the particular service provider's network.
>When I look at how service providers are requesting automatic topology
>import into our CDN product  some are requesting ALTO, some are
>requesting just BGP and some are certainly requesting that we listen to
>both BGP and the IGP.
>
>Ben
>
>_______________________________________________
>alto mailing list
>alto@ietf.org
>https://www.ietf.org/mailman/listinfo/alto


From sprevidi@cisco.com  Mon Apr 18 10:03:35 2011
Return-Path: <sprevidi@cisco.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 24878E0802 for <alto@ietfc.amsl.com>; Mon, 18 Apr 2011 10:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FzSV+2rbOELt for <alto@ietfc.amsl.com>; Mon, 18 Apr 2011 10:03:34 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfc.amsl.com (Postfix) with ESMTP id 8BC43E07FA for <alto@ietf.org>; Mon, 18 Apr 2011 10:03:32 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3IGhTU7003113; Mon, 18 Apr 2011 18:43:29 +0200 (CEST)
Received: from [192.168.62.100] (dhcp-10-61-108-98.cisco.com [10.61.108.98]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3IGhNLJ010240; Mon, 18 Apr 2011 18:43:24 +0200 (CEST)
From: stefano previdi <sprevidi@cisco.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
In-Reply-To: <1CA25301D2219F40B3AA37201F0EACD1134E862E@PACDCEXMB05.cable.comcast.com>
References: <C9CB0B72.22029%jmedved@juniper.net> <87FF1BBD-4053-4A9D-8CB2-9386698CA088@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E7EC7@PACDCEXMB05.cable.comcast.com> <6485E35C-0BF4-49DF-B43B-AC9EE87A263F@niven-jenkins.co.uk> <1CA25301D2219F40B3AA37201F0EACD1134E862E@PACDCEXMB05.cable.comcast.com>
Message-Id: <5EA911A7-EB36-44EB-B243-25F4AF2D97A0@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 18 Apr 2011 18:43:23 +0200
X-Mailer: Apple Mail (2.935.3)
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2011 17:03:35 -0000

On Apr 15, 2011, at 7:51 PM, Woundy, Richard wrote:
> One last set of comments.
>
>> I do not believe there is Standards Track work for the ALTO WG to  
>> do to describe how to passively listen to a routing protocol.
>
> I could be persuaded to your point of view, if it can be shown that  
> passively listening to one or more routing protocol(s) is sufficient  
> for interoperable network information updates and distribution from  
> routers to ALTO servers. And I suppose in return, you will expect  
> someone to document why passive listening is not sufficient, which  
> would be a fair pushback.
>
> If folks are suggesting that service providers need to load a  
> proprietary application module on their routers to get network  
> information into their ALTO servers, then I will be very un- 
> persuaded. And very unhappy.

After some initial deployments of ALTO servers, it seems that sometimes
operators prefer not to extend their igp/bgp scheme to a server not
sitting in the network layer (IOW: not a router). Keep also in mind that
link-state technology has no such concept of "passive listener" and you
always have to hope that your isis/ospf nodes are going to be good
citizens.

BGP is obviously more robust in this context and probably is one of the
motivations of draft-gredler-bgp-te-00 authors. What puzzles me with
draft-gredler-bgp-te-00 (in its current version) is the non-ability to
pass any existing igp TLV that may be used by ALTO server (probably
something amendable).  So my opinion is that:

a. it makes sense to have a routing API in order for an application to
    extract routing topology information without having to participate  
to
    the routing scheme and there are ALTO implementors already working  
on
    that.

b. it makes sense for an operator to have a unified/standardized way to
    plug an ALTO server without having to bind the ALTO server to a
    specific router flavor.

c. it makes sense to evaluate if a routing API may leverage existing
    protocols. draft-gredler-bgp-te-00 is probably one attempts to do
    that. It looks to me it needs substantial modifications but worth to
    be evaluated.

d. The use of routing protocols or (new) routing API is not mutually
    exclusive.

e. IETF WG (ALTO, routing, others) will determine the best WG if/where
    routing APIs have to be worked out.

Thanks.
s.

>
> -- Rich
>
> -----Original Message-----
> From: Ben Niven-Jenkins [mailto:ben@niven-jenkins.co.uk]
> Sent: Friday, April 15, 2011 1:11 PM
> To: Woundy, Richard
> Cc: Jan Medved; alto@ietf.org
> Subject: Re: [alto] Do we need to standardise an ALTO Server to  
> Network API?
>
> Rich,
>
> On 15 Apr 2011, at 15:31, Woundy, Richard wrote:
>
>> As a co-author of draft-medved-alto-svr-apis-00, let me explain my  
>> motivations for interest in this subject.
>>
>> My primary motivation is to have *some* scalable means to populate  
>> (my) ALTO servers with current network information. Note that I  
>> don't think there needs to be only ONE way to populate ALTO  
>> servers. Certainly it needs to be possible to use manual  
>> configuration as well. Maybe there is room for proprietary  
>> mechanisms as well -- perhaps ALTO server vendor-driven (eg unique  
>> routing ingest mechanisms and algorithms), perhaps ALTO server  
>> purchaser-driven (eg via open/proprietary APIs to the ALTO server).
>
> The reason I do not think an ALTO Server - Network API needs to be  
> specified in ALTO is not because I think ALTO servers do not need to  
> extract topology from the network in a scalable way but because I  
> see no Standards Track work for the ALTO WG to do to achieve that aim.
>
> I could paraphrase the contents of draft-medved-alto-svr-apis-00 as  
> "Go implement draft-gredler-bgp-te-00 and here are some reasons why  
> BGP is good". Therefore the solution proposed is not really draft- 
> medved-alto-svr-apis-00 it is draft-gredler-bgp-te-00.
>
> As someone with a background in routing draft-medved-alto-svr- 
> apis-00 adds nothing to draft-gredler-bgp-te-00 and certainly  
> nothing that warrants the status of a Standards Track document.
>
> Now, I guess given ALTO is not in the Routing Area there may be  
> folks in ALTO who are not routing experts and some level of  
> informational material explaining how routing can be used to obtain  
> topology may be useful, but that's an Informational document at best  
> (it could be a BCP once there's some real world experience of doing  
> it).
>
>> My secondary motivation is to ensure that, with respect to  
>> automated population of network information into ALTO servers, I  
>> could choose ALTO server vendors and router vendors fairly  
>> independently. That's why the use of a common protocol (BGP) is of  
>> interest, because it is commonly implemented by router vendors and  
>> commonly deployed by service providers. We had talked a long time  
>> ago in ALTO about using "looking glass servers" as a potential  
>> network information source, and usually looking glass servers are  
>> based on BGP routes.
>
> No objection there. ISIS and OSPF are also commonly implemented by  
> router vendors and commonly deployed by service providers :-) In my  
> mind a Standards Track document coming out of ALTO that says "The  
> answer is to load everything in BGP" sets the precedent that the  
> IETF 'mandated' way to do it loading your IGP into BGP, when IMO  
> that is one possible way that is likely to suit some but not all  
> service providers.
>
>> That's why I am interested in an open specification for an ALTO  
>> server to network API.
>
> IMO those open specifications exist in the form of the RFCs that  
> describe existing (and future) routing protocols and extensions.
>
> To summarise my position:
> - I believe that passively listening to routing is a reasonable  
> approach.
> - I do not believe there is Standards Track work for the ALTO WG to  
> do to describe how to passively listen to a routing protocol. If  
> ALTO generates additional requirements that cannot be met by  
> existing roputing protocols ALTO could specify those and take them  
> to the appropriate Routing Area WG to produce a solution. I think  
> draft-medved-alto-svr-apis-00 clearly demonstrates that as it  
> contains no protocol specification at all and leaves all that to  
> draft-gredler-bgp-te-00 which can be taken up with the IDR WG.
>
>> -- Rich
>>
>> P.S. I don't think ALTO servers need to listen to BGP *and* the IGP.
>
> I think this really depends on the particular service provider's  
> network. When I look at how service providers are requesting  
> automatic topology import into our CDN product  some are requesting  
> ALTO, some are requesting just BGP and some are certainly requesting  
> that we listen to both BGP and the IGP.
>
> Ben
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From jmedved@juniper.net  Mon Apr 18 11:01:14 2011
Return-Path: <jmedved@juniper.net>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 20C9CE0783 for <alto@ietfc.amsl.com>; Mon, 18 Apr 2011 11:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qSx7QLCFoK9W for <alto@ietfc.amsl.com>; Mon, 18 Apr 2011 11:01:13 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfc.amsl.com (Postfix) with ESMTP id 31FC8E076F for <alto@ietf.org>; Mon, 18 Apr 2011 11:01:13 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKTax8ZpviFN7p42t1JkIzfG+6sqtFtTEY@postini.com; Mon, 18 Apr 2011 11:01:13 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Mon, 18 Apr 2011 10:53:22 -0700
From: Jan Medved <jmedved@juniper.net>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>, "EXT - Richard_Woundy@cable.comcast.com" <Richard_Woundy@cable.comcast.com>
Date: Mon, 18 Apr 2011 10:55:24 -0700
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: Acv98ctRL5+8lkFqTAiz1Z8hHngygA==
Message-ID: <C9CF1F91.22C01%jmedved@juniper.net>
In-Reply-To: <6485E35C-0BF4-49DF-B43B-AC9EE87A263F@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.10.0.110310
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2011 18:01:14 -0000

On 4/15/11 10:10 AM, "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk> wrote:

>I think this really depends on the particular service provider's network.
>When I look at how service providers are requesting automatic topology
>import into our CDN product  some are requesting ALTO, some are
>requesting just BGP and some are certainly requesting that we listen to
>both BGP and the IGP.
>
This actually underlines the need for standardizing what data is acquired
from the network, how the data is normalized, and how the ALTO server
acquires topology data from the network. If the ALTO server can accurately
reflect the topology of the underlying network, there is no need for the
CDN to listen to routing protocols. All the CDN needs to do is to
interface with the ALTO Server, which makes the CDN implementation a lot
simpler. This in turn allows for better interoperability between CDNs and
interoperability between the network and different CDNs operating on top
of=20
it.=20

Protocol selection aside, this discussion should be about the APIs and
utility of standardizing the map exchange. WRT the discussion of the
Network API: the pro is that ALTO servers will have the same information,
the con is that they won't and have a technology with different maps and
views of the network.



/Jan


From sprevidi@cisco.com  Mon Apr 18 12:03:33 2011
Return-Path: <sprevidi@cisco.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D161CE087D for <alto@ietfc.amsl.com>; Mon, 18 Apr 2011 12:03:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MbpSejpgynAd for <alto@ietfc.amsl.com>; Mon, 18 Apr 2011 12:03:33 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfc.amsl.com (Postfix) with ESMTP id C6906E0870 for <alto@ietf.org>; Mon, 18 Apr 2011 12:03:32 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3IIJgAT010772; Mon, 18 Apr 2011 20:19:42 +0200 (CEST)
Received: from [192.168.62.100] (dhcp-10-61-108-98.cisco.com [10.61.108.98]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3IIJfIn014778; Mon, 18 Apr 2011 20:19:41 +0200 (CEST)
Message-Id: <C92840C1-872D-4380-9DE9-7727CAB76BE1@cisco.com>
From: stefano previdi <sprevidi@cisco.com>
To: Jan Medved <jmedved@juniper.net>
In-Reply-To: <C9CF1F91.22C01%jmedved@juniper.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 18 Apr 2011 20:19:41 +0200
References: <C9CF1F91.22C01%jmedved@juniper.net>
X-Mailer: Apple Mail (2.935.3)
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2011 19:03:34 -0000

On Apr 18, 2011, at 7:55 PM, Jan Medved wrote:
>
> On 4/15/11 10:10 AM, "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk>  
> wrote:
>
>> I think this really depends on the particular service provider's  
>> network.
>> When I look at how service providers are requesting automatic  
>> topology
>> import into our CDN product  some are requesting ALTO, some are
>> requesting just BGP and some are certainly requesting that we  
>> listen to
>> both BGP and the IGP.
>>
> This actually underlines the need for standardizing what data is  
> acquired
> from the network, how the data is normalized, and how the ALTO server
> acquires topology data from the network.


I don't think we need to define what exact piece of information alto
should retrieve but rather how to formalize a link-state, TE or bgp
topology into an api so it can be retrieved independently from routing
layer operations and deployed protocols.


> If the ALTO server can accurately
> reflect the topology of the underlying network, there is no need for  
> the
> CDN to listen to routing protocols.


but the CDN does NOT listen to routing protocols anyway. The ALTO server
does it and CDN only interoperates with ALTO.



> All the CDN needs to do is to
> interface with the ALTO Server, which makes the CDN implementation a  
> lot
> simpler.


again: this happens today when ALTO plays routing protocols.

s.


> This in turn allows for better interoperability between CDNs and
> interoperability between the network and different CDNs operating on  
> top
> of
> it.
>
> Protocol selection aside, this discussion should be about the APIs and
> utility of standardizing the map exchange. WRT the discussion of the
> Network API: the pro is that ALTO servers will have the same  
> information,
> the con is that they won't and have a technology with different maps  
> and
> views of the network.
>
>
>
> /Jan
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From ben@niven-jenkins.co.uk  Tue Apr 19 09:43:44 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 455E3E0758 for <alto@ietfc.amsl.com>; Tue, 19 Apr 2011 09:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.475
X-Spam-Level: 
X-Spam-Status: No, score=-103.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xN1Euc2npcUf for <alto@ietfc.amsl.com>; Tue, 19 Apr 2011 09:43:43 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfc.amsl.com (Postfix) with ESMTP id 49D0CE0712 for <alto@ietf.org>; Tue, 19 Apr 2011 09:43:43 -0700 (PDT)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-108-devlan.cachelogic.com) by mail10.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1QCE1e-0005nJ-6B; Tue, 19 Apr 2011 17:43:42 +0100
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <C9D1BFA2.1430C%dave.mcdysan@one.verizon.com>
Date: Tue, 19 Apr 2011 17:43:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA327E7B-16AD-4AB8-A7C1-963D4457F2CA@niven-jenkins.co.uk>
References: <C9D1BFA2.1430C%dave.mcdysan@one.verizon.com>
To: "Mcdysan, David E" <dave.mcdysan@verizon.com>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2011 16:43:44 -0000

Dave, Colleagues,

Please see inline below.

Ben

On 18 Apr 2011, at 15:20, Mcdysan, David E wrote:
>>> I could paraphrase the contents of draft-medved-alto-svr-apis-00 as =
"Go
>>> implement draft-gredler-bgp-te-00 and here are some reasons why BGP =
is
>>> good". Therefore the solution proposed is not really
>>> draft-medved-alto-svr-apis-00 it is draft-gredler-bgp-te-00.
>>=20
>> Well, I agree, sort of. draft-medved-* is just a motivation document =
at
>> this time, eg why we want it, what we think are the requirements.
>> draft-gredler-* defines the new BGP encodings but doesn't say much =
how an
>> ALTO server would leverage that information. draft-gredler-* also is
>> concerned with MPLS-TE, which is way outside the scope of ALTO.
>=20
> I think the following summary is more accurate than the above:
>=20
> Note that section 4.1.1 is requirements, and states all of them as
> "should" (I.e., SHOULD) and are not mandatory.
>=20
> Section 4.1.2 describes A solution that meets many of the desirable
> requirements.=20
>=20
>>=20
>> A third document is needed (or significant updates to the other two) =
to
>> say how an ALTO server would consume and react to the BGP TE =
information.
>>=20
>> But right now there doesn't seem to be a forum for this discussion. =
It is
>> not in scope for ALTO yet (my opinion), and it seems that IDR is not =
the
>> ideal forum.
>>=20
>>> If ALTO generates additional requirements that cannot be met by
>>> existing [routing] protocols ALTO could specify those and take them =
to
>>> the appropriate Routing Area WG to produce a solution.
>>=20
>> That is a possible approach.
>>=20
>>> I think draft-medved-alto-svr-apis-00 clearly demonstrates that as =
it
>>> contains no protocol specification at all and leaves all that to
>>> draft-gredler-bgp-te-00 which can be taken up with the IDR WG.
>>=20
>> Sigh. It might also clearly demonstrate that the protocol =
specification
>> work to make BGP TE work specifically with ALTO servers hasn't =
started
>> yet. And that draft-medved-alto-svr-apis-00 is written as a =
motivational
>> (use case / requirements) document not as a standards track protocol
>> document.
>>=20
>> I guess we might have to agree to disagree.
>=20
> I agree with Rich that the use case/ requirements is separable from =
the
> protocol specifics.
>=20
> Ben, would separating these address what appears to be one of your =
major
> comments?

Yes. I would prefer ALTO WG to focus on:
- What information an ALTO server needs from the network to do its job =
(which may differ by use case).
- What an ALTO server may want (or be required) to do with that =
information

> I suggest that we first focus on the requirements and where that work =
is
> best chartered.=20
>=20

Did you mean to insert a 'not' to make 'and not where that work is =
chartered'? If so, then I'd say that is a fine suggestion and one I =
heartily agree with :-)

Ben


From dave.mcdysan@verizon.com  Tue Apr 19 10:22:42 2011
Return-Path: <dave.mcdysan@verizon.com>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D9322E0841 for <alto@ietfc.amsl.com>; Tue, 19 Apr 2011 10:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.367
X-Spam-Level: 
X-Spam-Status: No, score=-3.367 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nW-7OVWaridP for <alto@ietfc.amsl.com>; Tue, 19 Apr 2011 10:22:42 -0700 (PDT)
Received: from sacmail4.verizon.com (sacmail4.verizon.com [192.76.84.42]) by ietfc.amsl.com (Postfix) with ESMTP id 0B97EE0828 for <alto@ietf.org>; Tue, 19 Apr 2011 10:22:31 -0700 (PDT)
Received: from fldsmtpi02.verizon.com (fldsmtpi02.verizon.com [166.68.71.144]) by sacmail4.verizon.com (8.13.7+Sun/8.13.3) with ESMTP id p3JHMUY2005809 for <alto@ietf.org>; Tue, 19 Apr 2011 13:22:30 -0400 (EDT)
From: "Mcdysan, David E" <dave.mcdysan@verizon.com>
X-IronPort-AV: E=Sophos;i="4.64,240,1301875200"; d="scan'208";a="33565081"
Received: from fhdp1lumxc7hb01.verizon.com (HELO FHDP1LUMXC7HB01.us.one.verizon.com) ([166.68.59.188]) by fldsmtpi02.verizon.com with ESMTP; 19 Apr 2011 17:22:30 +0000
Received: from fhdp1lumxc7v11.us.one.verizon.com ([169.254.1.15]) by FHDP1LUMXC7HB01.us.one.verizon.com ([2002:a644:3bbc::a644:3bbc]) with mapi; Tue, 19 Apr 2011 13:22:30 -0400
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Tue, 19 Apr 2011 13:22:28 -0400
Thread-Topic: [alto] Do we need to standardise an ALTO Server to Network API?
Thread-Index: Acv+tlxYQoPi8xrgRV+5dEHEWEGnzQ==
Message-ID: <C9D334BE.1549C%dave.mcdysan@one.verizon.com>
In-Reply-To: <EA327E7B-16AD-4AB8-A7C1-963D4457F2CA@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.1.0.101012
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2011 17:22:43 -0000

Hi Ben,

A response to your question below.
Dave

On Tuesday4/19/11 12:43 PM, "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk>
wrote:

>Dave, Colleagues,
>
>Please see inline below.
>
>Ben
>
>On 18 Apr 2011, at 15:20, Mcdysan, David E wrote:
>>>> I could paraphrase the contents of draft-medved-alto-svr-apis-00 as
>>>>"Go
>>>> implement draft-gredler-bgp-te-00 and here are some reasons why BGP is
>>>> good". Therefore the solution proposed is not really
>>>> draft-medved-alto-svr-apis-00 it is draft-gredler-bgp-te-00.
>>>=20
>>> Well, I agree, sort of. draft-medved-* is just a motivation document at
>>> this time, eg why we want it, what we think are the requirements.
>>> draft-gredler-* defines the new BGP encodings but doesn't say much how
>>>an
>>> ALTO server would leverage that information. draft-gredler-* also is
>>> concerned with MPLS-TE, which is way outside the scope of ALTO.
>>=20
>> I think the following summary is more accurate than the above:
>>=20
>> Note that section 4.1.1 is requirements, and states all of them as
>> "should" (I.e., SHOULD) and are not mandatory.
>>=20
>> Section 4.1.2 describes A solution that meets many of the desirable
>> requirements.=20
>>=20
>>>=20
>>> A third document is needed (or significant updates to the other two) to
>>> say how an ALTO server would consume and react to the BGP TE
>>>information.
>>>=20
>>> But right now there doesn't seem to be a forum for this discussion. It
>>>is
>>> not in scope for ALTO yet (my opinion), and it seems that IDR is not
>>>the
>>> ideal forum.
>>>=20
>>>> If ALTO generates additional requirements that cannot be met by
>>>> existing [routing] protocols ALTO could specify those and take them to
>>>> the appropriate Routing Area WG to produce a solution.
>>>=20
>>> That is a possible approach.
>>>=20
>>>> I think draft-medved-alto-svr-apis-00 clearly demonstrates that as it
>>>> contains no protocol specification at all and leaves all that to
>>>> draft-gredler-bgp-te-00 which can be taken up with the IDR WG.
>>>=20
>>> Sigh. It might also clearly demonstrate that the protocol specification
>>> work to make BGP TE work specifically with ALTO servers hasn't started
>>> yet. And that draft-medved-alto-svr-apis-00 is written as a
>>>motivational
>>> (use case / requirements) document not as a standards track protocol
>>> document.
>>>=20
>>> I guess we might have to agree to disagree.
>>=20
>> I agree with Rich that the use case/ requirements is separable from the
>> protocol specifics.
>>=20
>> Ben, would separating these address what appears to be one of your major
>> comments?
>
>Yes. I would prefer ALTO WG to focus on:
>- What information an ALTO server needs from the network to do its job
>(which may differ by use case).
>- What an ALTO server may want (or be required) to do with that
>information
>
>> I suggest that we first focus on the requirements and where that work is
>> best chartered.=20
>>=20
>
>Did you mean to insert a 'not' to make 'and not where that work is
>chartered'? If so, then I'd say that is a fine suggestion and one I
>heartily agree with :-)

Sorry, the following is what I had in mind, with CHANGES IN ALL CAPS.

I suggest that THE ALTO WG first focus on the requirements and THEN AS A
NEXT STEP (E.G., A SEPARATE DRAFT) DETERMINE where ANY NEEDED
INFORMATIONAL, BCP OR PROTOCOL work AS DETERMINED FROM THE REQUIREMENTS
ANALYSIS WOULD best BE chartered.




>
>Ben
>


From buptxiaozhu@gmail.com  Tue Apr 26 18:15:13 2011
Return-Path: <buptxiaozhu@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E44AE06AD for <alto@ietfa.amsl.com>; Tue, 26 Apr 2011 18:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.439
X-Spam-Level: 
X-Spam-Status: No, score=-1.439 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gr2c4Rk2PpBB for <alto@ietfa.amsl.com>; Tue, 26 Apr 2011 18:15:12 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 611CAE069D for <alto@ietf.org>; Tue, 26 Apr 2011 18:15:12 -0700 (PDT)
Received: by ywi6 with SMTP id 6so540361ywi.31 for <alto@ietf.org>; Tue, 26 Apr 2011 18:15:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=1wV56u8C9mWw1Rzx7Z+W9ofvLU7lx6J6DFpe0m0zBzM=; b=oKjzSKxeqQ7wmNtBvbmUgZxhiVSzmgD3NCmnmfx6Z5R2JY6iScbrLFRm08ude7qGkZ YUQQsR8NWNqayLmpevfVe/N35y0/iGC5Bj8XMzbSS+kTplAr+Xrb0uIL+pf0JqdEkECn XC3rB+swtuNAO99FyrlFohDtlIP+Lf692sgoU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=k8NSthG17FmEAxyvQ8mGMLV4E44ZQAFcQb0KkrWkBQ0Zjz03trxL7qHpjXC45CXf/J Idt4jMJeth1kKfyPHT/y1Ljgyr6Ku8S/Sc6jN+dXcJRnSe5o+F4xQ2pYWfFjHkbp/cmr gw16Twne5eEhEqFUYVU7r9QSJRxlGZSCdoohg=
MIME-Version: 1.0
Received: by 10.150.196.13 with SMTP id t13mr1266014ybf.365.1303866911862; Tue, 26 Apr 2011 18:15:11 -0700 (PDT)
Received: by 10.151.101.13 with HTTP; Tue, 26 Apr 2011 18:15:11 -0700 (PDT)
Date: Wed, 27 Apr 2011 09:15:11 +0800
Message-ID: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com>
From: =?UTF-8?B?5pyx5r2H?= <buptxiaozhu@gmail.com>
To: alto@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd2e56c1db04104a1dc2c61
Subject: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 01:15:13 -0000

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

hi, everyone:

have the ALTO considered the use cases of wireless, which means how to make
the selection of the peers in the wireless environment?

could anybody be kind to instruct me if the ALTO have the consideration.

thx in advance!
--=20
Best wishes,

Beijing University of Posts & Telecommunications (BUPT)
Zhu Xiao  ( =E6=9C=B1=E6=BD=87 )
E-mail: buptxiaozhu@gmail.com
mobile:+86 134-8881-9004

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

hi, everyone:<div><br></div><div>have the ALTO=C2=A0considered=C2=A0the use=
 cases of wireless, which means how to make the selection of the peers in t=
he wireless=C2=A0environment?<br clear=3D"all"><br></div><div>could anybody=
 be kind to=C2=A0instruct=C2=A0me if the ALTO have the consideration.=C2=A0=
</div>
<div><br></div><div>thx in advance!</div><div>-- <br>Best wishes,<br><br>Be=
ijing University of Posts &amp; Telecommunications (BUPT)<br>Zhu Xiao=C2=A0=
 ( =E6=9C=B1=E6=BD=87 )<br>E-mail: <a href=3D"mailto:buptxiaozhu@gmail.com"=
 target=3D"_blank">buptxiaozhu@gmail.com</a><br>
mobile:+86 134-8881-9004<br>
</div>

--000e0cd2e56c1db04104a1dc2c61--

From robert.varga@pantheon.sk  Thu Apr 21 17:26:00 2011
Return-Path: <robert.varga@pantheon.sk>
X-Original-To: alto@ietfc.amsl.com
Delivered-To: alto@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 18365E0673 for <alto@ietfc.amsl.com>; Thu, 21 Apr 2011 17:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8LrMVKHU7gtl for <alto@ietfc.amsl.com>; Thu, 21 Apr 2011 17:25:59 -0700 (PDT)
Received: from amalka.pantheon.sk (amalka.pantheon.sk [81.89.59.174]) by ietfc.amsl.com (Postfix) with ESMTP id 89C44E065C for <alto@ietf.org>; Thu, 21 Apr 2011 17:25:59 -0700 (PDT)
Received: from [10.0.2.15] (unknown [216.239.45.19]) by amalka.pantheon.sk (Postfix) with ESMTPSA id 0BF812073E for <alto@ietf.org>; Fri, 22 Apr 2011 02:26:00 +0200 (CEST)
Message-ID: <4DB0CB13.4050602@pantheon.sk>
Date: Fri, 22 Apr 2011 02:25:55 +0200
From: Robert Varga <robert.varga@pantheon.sk>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110322 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: alto@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 27 Apr 2011 00:06:24 -0700
Subject: [alto] Interop at IETF-81?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Apr 2011 00:29:27 -0000

Hi everyone,

given the intent of doing interoperability testing during IETF-81 in
Quebec, I think we need to start planning for that. The major question
is which version of the ALTO Protocol draft are we going to standardize
on. With 07 being the last one published, it may be a good target, but
if I understand it correctly, there already are some proposed changes
which mandate an update.

Given the meeting is taking place July 24-29, I propose we decide on the
interop standard by the end of May, which leaves ~5 weeks for publishing
an updated draft (if that is the consensus) and whole 8 weeks for
implementations to converge on it. Would that do as a plan?

Thanks,
Robert

From enrico.marocco@telecomitalia.it  Wed Apr 27 00:21:52 2011
Return-Path: <enrico.marocco@telecomitalia.it>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21460E06F3 for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 00:21:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.719
X-Spam-Level: 
X-Spam-Status: No, score=-100.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BRgvG401UWCG for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 00:21:51 -0700 (PDT)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id 307C7E06F2 for <alto@ietf.org>; Wed, 27 Apr 2011 00:21:51 -0700 (PDT)
Received: from GRFHUB701BA020.griffon.local (10.188.101.111) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 27 Apr 2011 09:21:46 +0200
Received: from MacLab.local (163.162.180.246) by smtp.telecomitalia.it (10.188.101.114) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 27 Apr 2011 09:21:45 +0200
Message-ID: <4DB7C408.6090305@telecomitalia.it>
Date: Wed, 27 Apr 2011 09:21:44 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080001020609090600090009"
Subject: [alto] Adopting draft-kiesel-alto-3pdisc-05
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 07:21:52 -0000

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

Hi all,

following on from the strong consensus shown during the meeting in
Prague, the chairs would like to issue a last call for objections about
adopting draft-kiesel-alto-3pdisc-05 as the base text for the discovery
mechanism milestone in the ALTO charter. If anyone is opposed to such
adoption or has a better candidate draft for the discovery mechanism
milestone, please speak up by Wednesday, May 4.

--=20
Ciao,
Enrico


--------------ms080001020609090600090009
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITpDCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGsjCCBZqgAwIBAgIDAZXQMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTAwOTAyMjE0NjQ5
WhcNMTEwOTA0MDczNDM2WjCBnTEgMB4GA1UEDRMXMjUxNDUwLTVBOWo3QUhXTXgzNkVHa2Qx
HjAcBgNVBAoTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEpMCcGA1UEAxMgU3RhcnRDb20gRnJl
ZSBDZXJ0aWZpY2F0ZSBNZW1iZXIxLjAsBgkqhkiG9w0BCQEWH2Vucmljby5tYXJvY2NvQHRl
bGVjb21pdGFsaWEuaXQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCVq5Ial9/2
azyFbgXY2+yMbEwHjhOWlXcwa7sdnRZ6BUXjusppAmshM1SPz+IZYfLdqancntuhkG/YKR4T
Mg0SzWz3bDtCQjga0FSBQ5v2Up8kT/Q0F4/hkYrsTaKfL+WA2cjQtn8+K0fD3t/1tcuTuIHw
fesN6w1VDn4HhFj3WGSXok9Zxk7609/Z4ZBqr3trmQ5Dl6pwb8pO1kE/ggH7qCx537ybIByS
dxzcPNzbryGJiCfy4iXaws0xsl4xEQXDJFixLjgJm+AOTXb37AAgwKq+v9t3qIH6AHAbPBO6
I/qpoQ/zYMs1s9CoKkNDa9DsJlgyZdPH/vyFvCi/dDJ7AgMBAAGjggMIMIIDBDAJBgNVHRME
AjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0O
BBYEFCTMmq/In1ufC0+wdpHdBvezAYWcMB8GA1UdIwQYMBaAFFNy7ZKc4NrLAVx8fpY1TvLU
uFGCMCoGA1UdEQQjMCGBH2Vucmljby5tYXJvY2NvQHRlbGVjb21pdGFsaWEuaXQwggFCBgNV
HSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAuBggrBgEFBQcCARYiaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYBBQUHAgIwgaowFBYNU3RhcnRDb20g
THRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNlZSBzZWN0aW9uICpMZWdhbCBMaW1p
dGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGlj
eSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjBjBgNV
HR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMCug
KaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMIGOBggrBgEFBQcB
AQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNz
MS9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRz
L3N1Yi5jbGFzczEuY2xpZW50LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0
c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADWaaCjv4EfYGz4rrds8wLUpSPTi1tnO3hIm
/Hg0SHqDRWRv3AG/OjUKYj+UKKAzhhEoYYrYCxhQfO3uEAC4Mez+DWDsBymKHsRkpf/0efoh
mDe60HN81V6jB7hSB+FHaJ5QCBhJ/yasltL7HMl92dpRHYlnKXoXAiIoZUY54eYh09Gyk8su
xgaiAwWtn4NnTqnQTjYOOly+WOZ/M6AlmkTErzjliIyAJOIceWzByJs6iIvLXzqpdoZ1+BzE
TvoyaVidF13Xc8opUGSqYTyaVKwumrA5eUOZrLzdunkT8JuWgAx81syHYjSeD4ae+EoMFRJ8
gVm6vGPNETTSbFjGM38wggayMIIFmqADAgECAgMBldAwDQYJKoZIhvcNAQEFBQAwgYwxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGln
aXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFBy
aW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDA5MDIyMTQ2NDlaFw0xMTA5MDQw
NzM0MzZaMIGdMSAwHgYDVQQNExcyNTE0NTAtNUE5ajdBSFdNeDM2RUdrZDEeMBwGA1UEChMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMSkwJwYDVQQDEyBTdGFydENvbSBGcmVlIENlcnRpZmlj
YXRlIE1lbWJlcjEuMCwGCSqGSIb3DQEJARYfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxp
YS5pdDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJWrkhqX3/ZrPIVuBdjb7Ixs
TAeOE5aVdzBrux2dFnoFReO6ymkCayEzVI/P4hlh8t2pqdye26GQb9gpHhMyDRLNbPdsO0JC
OBrQVIFDm/ZSnyRP9DQXj+GRiuxNop8v5YDZyNC2fz4rR8Pe3/W1y5O4gfB96w3rDVUOfgeE
WPdYZJeiT1nGTvrT39nhkGqve2uZDkOXqnBvyk7WQT+CAfuoLHnfvJsgHJJ3HNw83NuvIYmI
J/LiJdrCzTGyXjERBcMkWLEuOAmb4A5NdvfsACDAqr6/23eogfoAcBs8E7oj+qmhD/NgyzWz
0KgqQ0Nr0OwmWDJl08f+/IW8KL90MnsCAwEAAaOCAwgwggMEMAkGA1UdEwQCMAAwCwYDVR0P
BAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUJMyar8if
W58LT7B2kd0G97MBhZwwHwYDVR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwKgYDVR0R
BCMwIYEfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDCCAUIGA1UdIASCATkwggE1
MIIBMQYLKwYBBAGBtTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9wb2xpY3kucGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9p
bnRlcm1lZGlhdGUucGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEa
gZFMaW1pdGVkIExpYWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBv
ZiB0aGUgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJs
ZSBhdCBodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6Ap
oCeGJWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwK6ApoCeGJWh0dHA6
Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYI
KwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9j
YTBCBggrBgEFBQcwAoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNz
MS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzAN
BgkqhkiG9w0BAQUFAAOCAQEANZpoKO/gR9gbPiut2zzAtSlI9OLW2c7eEib8eDRIeoNFZG/c
Ab86NQpiP5QooDOGEShhitgLGFB87e4QALgx7P4NYOwHKYoexGSl//R5+iGYN7rQc3zVXqMH
uFIH4UdonlAIGEn/JqyW0vscyX3Z2lEdiWcpehcCIihlRjnh5iHT0bKTyy7GBqIDBa2fg2dO
qdBONg46XL5Y5n8zoCWaRMSvOOWIjIAk4hx5bMHImzqIi8tfOql2hnX4HMRO+jJpWJ0XXddz
yilQZKphPJpUrC6asDl5Q5msvN26eRPwm5aADHzWzIdiNJ4Php74SgwVEnyBWbq8Y80RNNJs
WMYzfzGCA9AwggPMAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwGV0DAJBgUrDgMCGgUAoIICEDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0xMTA0MjcwNzIxNDRaMCMGCSqGSIb3DQEJBDEWBBSEQZ61I6XjcCJdqr5uLDOI
s/Yq0zBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG
9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgaUGCSsG
AQQBgjcQBDGBlzCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMBldAw
gacGCyqGSIb3DQEJEAILMYGXoIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg
Q0ECAwGV0DANBgkqhkiG9w0BAQEFAASCAQBhysOjlS+2uKhDeJ1LPnOlgGWT/E1+vut6DSYw
lVwxT22dugk7Tf3AtX5s/MCbUKak+ccxu13TzznWB0SmMYTw3mJCW9DI684ykFDrV3yYLb1B
wkCiTTI9OY9jCYjUrCblOGQjvQMUYSGqmAG7A+sZYxP8kSiXB9Lky98rIq9l2O6sJXLgaEhH
jcs9S2a/TjbsQUmJwJGTkqXYaprjvLaOSW/qOECaoTrlnieNtc7xx5a9TvfXfnq8PaRYCJBw
oP0ionDU2XGtriTV2D+JqcB58uWUt1090ZC4XRMrmkWjh8B530fi0D2Z+eY3kgQRrlOEIk66
8X03gSgwTI/VeFd2AAAAAAAA
--------------ms080001020609090600090009--

From sebi@smtp.ehlo.wurstkaes.de  Wed Apr 27 01:23:11 2011
Return-Path: <sebi@smtp.ehlo.wurstkaes.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C06D9E06EE for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 01:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f01Uj8CCxTol for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 01:23:11 -0700 (PDT)
Received: from hd00e.hd.wurstkaes.de (hd00e.hd.wurstkaes.de [213.240.180.126]) by ietfa.amsl.com (Postfix) with ESMTP id 09EB7E06D7 for <alto@ietf.org>; Wed, 27 Apr 2011 01:23:10 -0700 (PDT)
Received: from gw01.loc ([192.168.0.65]:59373 helo=smtp.ehlo.wurstkaes.de) by hd00e.hd.wurstkaes.de with esmtp (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QF01a-0002a1-QC; Wed, 27 Apr 2011 10:23:07 +0200
Received: from sebi by smtp.ehlo.wurstkaes.de with local (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QF015-0005Jj-Ud; Wed, 27 Apr 2011 10:22:35 +0200
Date: Wed, 27 Apr 2011 10:22:35 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: ?????? <buptxiaozhu@gmail.com>
Message-ID: <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 08:23:11 -0000

Hi,

On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:
> hi, everyone:
> 
> have the ALTO considered the use cases of wireless, which means how to make
> the selection of the peers in the wireless environment?

the ALTO protocols and procedures feature mechanisms that can be
leveraged in a mobile / wireless scenario. IMO there are two issues:

1. When a client is moving between different sections of an access
   network it may have to find a new ALTO server which is able
   to give guidance that is useful at the new client position.
   draft-kiesel-alto-3pdisc-05, sec. 1.3 states:

   o  A change of the IP address at an interface invalidates the result
      of the ALTO server discovery procedure.  For instance, if the IP
      address assigned to a mobile host changes due to host mobility, it
      is required to run the ALTO server discovery procedure for the new
      IP address without relying on earlier gained information.


2. The actual strategy (algorithm) for selecting peers is out of scope
   of the standardization process, as there are many different scenarios
   with different constraints and optimization goals (e.g., in a given
   mobile access network, is the backhaul capacity an issue or not?). 
   
   The ALTO client protocol together with a procedure for defining new
   Host Characteristics Attributes (cost types) is able to convey the
   input for a variety of different selection algorithms.


does this make sense?


thanks
sebastian

From sprevidi@cisco.com  Wed Apr 27 02:40:11 2011
Return-Path: <sprevidi@cisco.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00F7DE06F5 for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 02:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C6URNln2C-yo for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 02:40:06 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 87177E064B for <alto@ietf.org>; Wed, 27 Apr 2011 02:40:06 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3R9HZiU027726; Wed, 27 Apr 2011 11:17:35 +0200 (CEST)
Received: from [192.168.62.100] (dhcp-10-61-107-117.cisco.com [10.61.107.117]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3R9HX1S021293; Wed, 27 Apr 2011 11:17:34 +0200 (CEST)
Message-Id: <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com>
From: stefano previdi <sprevidi@cisco.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
In-Reply-To: <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 27 Apr 2011 11:17:33 +0200
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de>
X-Mailer: Apple Mail (2.935.3)
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 09:40:11 -0000

On Apr 27, 2011, at 10:22 AM, Sebastian Kiesel wrote:
> Hi,
>
> On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:
>> hi, everyone:
>>
>> have the ALTO considered the use cases of wireless, which means how  
>> to make
>> the selection of the peers in the wireless environment?
>
> the ALTO protocols and procedures feature mechanisms that can be
> leveraged in a mobile / wireless scenario. IMO there are two issues:
>
> 1. When a client is moving between different sections of an access
>   network it may have to find a new ALTO server which is able
>   to give guidance that is useful at the new client position.
>   draft-kiesel-alto-3pdisc-05, sec. 1.3 states:
>
>   o  A change of the IP address at an interface invalidates the result
>      of the ALTO server discovery procedure.  For instance, if the IP
>      address assigned to a mobile host changes due to host mobility,  
> it
>      is required to run the ALTO server discovery procedure for the  
> new
>      IP address without relying on earlier gained information.


mobility is often at layer-2 and this mean you will need some other
mechanisms in order to enrich your maps/ecs with wireless-l2 derived
topology info.

I agree with you: not sure these mechanisms needs standardization.

s.


> 2. The actual strategy (algorithm) for selecting peers is out of scope
>   of the standardization process, as there are many different  
> scenarios
>   with different constraints and optimization goals (e.g., in a given
>   mobile access network, is the backhaul capacity an issue or not?).
>
>   The ALTO client protocol together with a procedure for defining new
>   Host Characteristics Attributes (cost types) is able to convey the
>   input for a variety of different selection algorithms.
>
>
> does this make sense?
>
>
> thanks
> sebastian
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From buptxiaozhu@gmail.com  Wed Apr 27 08:18:24 2011
Return-Path: <buptxiaozhu@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B491AE07C1 for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 08:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ybc+LoanIvmu for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 08:18:24 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id BA688E0721 for <alto@ietf.org>; Wed, 27 Apr 2011 08:18:23 -0700 (PDT)
Received: by gyf3 with SMTP id 3so768298gyf.31 for <alto@ietf.org>; Wed, 27 Apr 2011 08:18:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=UM6iUrEFqEecaBMOxkzt2LdMdV+6d8M6V3kmLNa5u/g=; b=wvIAdpf3w8ehFxlAl0Mmw6t3np+lJHI9FlrQ0zi+O4FDm+0wAHs9qBdyNjt5EDMFHd wPdKKsNT+ZJsD/lMvObsoh8OuL5xh8um5w3LjUui+JhlPYzoutwVX5FzuEbTcs9Jadic 0iSeyFE92HL78eIjnjNePsltcSBTIahGCq1FE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=awoiRetLz/Vx/jpuxJgUTlUg/MdIrORjke44Nh0NGx/XXccCBzbIn0qWZRX3ABhmz1 aqpuzK9kEyoPREEqD9IDK3T2IGThUqrZpHnxy++7jrA7VdRJ1v4HGxw8QrqfBJXcBFCz kJBfS3efIn/G4ryG99V455DJrV9nBBLTKsCYA=
MIME-Version: 1.0
Received: by 10.150.66.11 with SMTP id o11mr2005403yba.159.1303917503132; Wed, 27 Apr 2011 08:18:23 -0700 (PDT)
Received: by 10.150.12.3 with HTTP; Wed, 27 Apr 2011 08:18:23 -0700 (PDT)
In-Reply-To: <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de>
Date: Wed, 27 Apr 2011 23:18:23 +0800
Message-ID: <BANLkTinVVfgbmFZJ49kY6zgUpYQcycxV1Q@mail.gmail.com>
From: =?UTF-8?B?5pyx5r2H?= <buptxiaozhu@gmail.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: multipart/alternative; boundary=000e0cd516b097341d04a1e7f3a0
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 15:18:24 -0000

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

hi, Sebastian

thx for your time!
comments inline:D

On Wed, Apr 27, 2011 at 4:22 PM, Sebastian Kiesel <ietf-alto@skiesel.de>wro=
te:

> Hi,
>
> On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:
> > hi, everyone:
> >
> > have the ALTO considered the use cases of wireless, which means how to
> make
> > the selection of the peers in the wireless environment?
>
> the ALTO protocols and procedures feature mechanisms that can be
> leveraged in a mobile / wireless scenario. IMO there are two issues:
> what is IMO stands for?
> 1. When a client is moving between different sections of an access
>   network it may have to find a new ALTO server which is able
>   to give guidance that is useful at the new client position.
>   draft-kiesel-alto-3pdisc-05, sec. 1.3 states:
>
>   o  A change of the IP address at an interface invalidates the result
>      of the ALTO server discovery procedure.  For instance, if the IP
>      address assigned to a mobile host changes due to host mobility, it
>      is required to run the ALTO server discovery procedure for the new
>      IP address without relying on earlier gained information.
> what does the IP address refer to in  "it is required to run the ALTO
> server discovery procedure for the new IP address without relying on earl=
ier
> gained information"?  the new IP address of the roaming user which may
> allocated by GGSN or wifi AP?  however, that allocation process has nothi=
ng
> to do with the ALTO server discovery. or it is not correct of  my
> understanding ?
>
> 2. The actual strategy (algorithm) for selecting peers is out of scope
>   of the standardization process, as there are many different scenarios
>   with different constraints and optimization goals (e.g., in a given
>   mobile access network, is the backhaul capacity an issue or not?).
> can i understand "how to make the selection is the issues decided by P2P
> application"?
>   The ALTO client protocol together with a procedure for defining new
>   Host Characteristics Attributes (cost types) is able to convey the
>   input for a variety of different selection algorithms.
> do you mean the selection algorithms can be self-defined by client itself=
?
>
> does this make sense?
>
>
> thanks
> sebastian
>



--=20
Best wishes,

Beijing University of Posts & Telecommunications (BUPT)
Zhu Xiao  ( =E6=9C=B1=E6=BD=87 )
E-mail: buptxiaozhu@gmail.com
mobile:+86 134-8881-9004

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

hi,=C2=A0Sebastian=C2=A0<div><br></div><div>thx for your time!</div><div>co=
mments inline:D</div><div><br><div class=3D"gmail_quote">On Wed, Apr 27, 20=
11 at 4:22 PM, Sebastian Kiesel <span dir=3D"ltr">&lt;<a href=3D"mailto:iet=
f-alto@skiesel.de">ietf-alto@skiesel.de</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;">Hi,<br>
<div class=3D"im"><br>
On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:<br>
&gt; hi, everyone:<br>
&gt;<br>
&gt; have the ALTO considered the use cases of wireless, which means how to=
 make<br>
&gt; the selection of the peers in the wireless environment?<br>
<br>
</div>the ALTO protocols and procedures feature mechanisms that can be<br>
leveraged in a mobile / wireless scenario. IMO there are two issues:<br>
<font class=3D"Apple-style-span" color=3D"#ff0000">what is IMO stands for?<=
/font><br>
1. When a client is moving between different sections of an access<br>
 =C2=A0 network it may have to find a new ALTO server which is able<br>
 =C2=A0 to give guidance that is useful at the new client position.<br>
 =C2=A0 draft-kiesel-alto-3pdisc-05, sec. 1.3 states:<br>
<br>
 =C2=A0 o =C2=A0A change of the IP address at an interface invalidates the =
result<br>
 =C2=A0 =C2=A0 =C2=A0of the ALTO server discovery procedure. =C2=A0For inst=
ance, if the IP<br>
 =C2=A0 =C2=A0 =C2=A0address assigned to a mobile host changes due to host =
mobility, it<br>
 =C2=A0 =C2=A0 =C2=A0is required to run the ALTO server discovery procedure=
 for the new<br>
 =C2=A0 =C2=A0 =C2=A0IP address without relying on earlier gained informati=
on.<br><font class=3D"Apple-style-span" color=3D"#ff0000">what does the IP =
address refer to in =C2=A0&quot;it is required to run the ALTO server disco=
very procedure for the new IP address without relying on earlier gained=C2=
=A0information&quot;? =C2=A0the new IP address of the roaming user which ma=
y allocated by GGSN or wifi AP? =C2=A0however, that allocation process has =
nothing to do with the ALTO server discovery. or it is not correct of =C2=
=A0my understanding ?</font><br>

<br>
2. The actual strategy (algorithm) for selecting peers is out of scope<br>
 =C2=A0 of the standardization process, as there are many different scenari=
os<br>
 =C2=A0 with different constraints and optimization goals (e.g., in a given=
<br>
 =C2=A0 mobile access network, is the backhaul capacity an issue or not?).<=
br><font class=3D"Apple-style-span" color=3D"#ff0000">can i understand &quo=
t;how to make the selection is the issues=C2=A0decided=C2=A0by P2P applicat=
ion&quot;?<br>
</font>
 =C2=A0 The ALTO client protocol together with a procedure for defining new=
<br>
 =C2=A0 Host Characteristics Attributes (cost types) is able to convey the<=
br>
 =C2=A0 input for a variety of different selection algorithms.<br><font cla=
ss=3D"Apple-style-span" color=3D"#ff0000">do you mean the selection algorit=
hms can be self-defined by client itself?</font><br>
<br>
does this make sense?<br>
<br>
<br>
thanks<br>
<font color=3D"#888888">sebastian<br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br>Best wishes,<br>=
<br>Beijing University of Posts &amp; Telecommunications (BUPT)<br>Zhu Xiao=
=C2=A0 ( =E6=9C=B1=E6=BD=87 )<br>E-mail: <a href=3D"mailto:buptxiaozhu@gmai=
l.com" target=3D"_blank">buptxiaozhu@gmail.com</a><br>
mobile:+86 134-8881-9004<br>
</div>

--000e0cd516b097341d04a1e7f3a0--

From ben@niven-jenkins.co.uk  Wed Apr 27 08:45:21 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33804E0827 for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 08:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.058
X-Spam-Level: 
X-Spam-Status: No, score=-104.058 tagged_above=-999 required=5 tests=[AWL=-0.459, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-mw6rlrETCX for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 08:45:20 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7CF5AE06EC for <alto@ietf.org>; Wed, 27 Apr 2011 08:45:17 -0700 (PDT)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-108-devlan.cachelogic.com) by mail6.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1QF6vV-0001k4-Pw; Wed, 27 Apr 2011 16:45:18 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Apr 2011 16:45:15 +0100
Message-Id: <63A9CDFD-B60E-43B3-8C7F-86F405B378E8@niven-jenkins.co.uk>
To: alto@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: Grant Watson <grant.watson@bt.com>, Nabil N Bitar <nabil.n.bitar@verizon.com>
Subject: [alto] New draft on use cases for ALTO & CDNs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 15:45:21 -0000

Colleagues,

During the ALTO meeting at IETF80 I made some comments at the microphone =
highlighting my concerns with the scope of draft-penno-alto-cdn-03 being =
far too wide and that we should first focus on documenting the use cases =
and requirements.

To that end I've been working with a couple of folks to co-author a =
draft focussed on documenting the use cases for ALTO & CDNs, the =
thinking being that a fresh draft with a tighter focus than =
draft-penno-alto-cdn-03 makes highlighting and discussing the use cases =
without slipping into possible solution mechanisms much simpler and =
cleaner.

We have just published a -00 version which is available here:
http://tools.ietf.org/html/draft-jenkins-alto-cdn-use-cases-00
=20
So far we have only included details on two use cases and included =
placeholders for another two because we wanted to socialise the work =
early to see if others were interested in contributing text for the use =
cases they have as well as to solicit early feedback on the structure =
and focus of the draft.

Comments/Suggestions/etc on the draft are welcomed.

Ben







From ben@niven-jenkins.co.uk  Wed Apr 27 08:49:42 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D64C9E083B for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 08:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.981
X-Spam-Level: 
X-Spam-Status: No, score=-103.981 tagged_above=-999 required=5 tests=[AWL=-0.382, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PChOyYa7a9e for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 08:49:42 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.64]) by ietfa.amsl.com (Postfix) with ESMTP id 2C085E0831 for <alto@ietf.org>; Wed, 27 Apr 2011 08:49:38 -0700 (PDT)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-108-devlan.cachelogic.com) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1QF6zh-0004ro-BK; Wed, 27 Apr 2011 16:49:37 +0100
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <C9D334BE.1549C%dave.mcdysan@one.verizon.com>
Date: Wed, 27 Apr 2011 16:49:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE69ECF1-4A0D-44C8-9D5B-4ADFF9B29894@niven-jenkins.co.uk>
References: <C9D334BE.1549C%dave.mcdysan@one.verizon.com>
To: "Mcdysan, David E" <dave.mcdysan@verizon.com>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Do we need to standardise an ALTO Server to Network API?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 15:49:43 -0000

Dave,

Apologies for taking some time to respond, please see below.

On 19 Apr 2011, at 18:22, Mcdysan, David E wrote:
> On Tuesday4/19/11 12:43 PM, "Ben Niven-Jenkins" =
<ben@niven-jenkins.co.uk>
>>> I agree with Rich that the use case/ requirements is separable from =
the
>>> protocol specifics.
>>>=20
>>> Ben, would separating these address what appears to be one of your =
major
>>> comments?
>>=20
>> Yes. I would prefer ALTO WG to focus on:
>> - What information an ALTO server needs from the network to do its =
job
>> (which may differ by use case).
>> - What an ALTO server may want (or be required) to do with that
>> information
>>=20
>>> I suggest that we first focus on the requirements and where that =
work is
>>> best chartered.=20
>>>=20
>>=20
>> Did you mean to insert a 'not' to make 'and not where that work is
>> chartered'? If so, then I'd say that is a fine suggestion and one I
>> heartily agree with :-)
>=20
> Sorry, the following is what I had in mind, with CHANGES IN ALL CAPS.
>=20
> I suggest that THE ALTO WG first focus on the requirements and THEN AS =
A
> NEXT STEP (E.G., A SEPARATE DRAFT) DETERMINE where ANY NEEDED
> INFORMATIONAL, BCP OR PROTOCOL work AS DETERMINED FROM THE =
REQUIREMENTS
> ANALYSIS WOULD best BE chartered.

Agreed - I think we're on the same page :-) The first step (IMO) is =
definitely to start by focussing on requirements and determining which =
place is best to do any follow-on work can wait until after we have the =
requirements.

Ben


From sebi@smtp.ehlo.wurstkaes.de  Wed Apr 27 08:55:43 2011
Return-Path: <sebi@smtp.ehlo.wurstkaes.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F68E06CE for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 08:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_44=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id liUSOdnifiei for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 08:55:42 -0700 (PDT)
Received: from hd00e.hd.wurstkaes.de (hd00e.hd.wurstkaes.de [213.240.180.126]) by ietfa.amsl.com (Postfix) with ESMTP id 3FCC2E06C9 for <alto@ietf.org>; Wed, 27 Apr 2011 08:55:41 -0700 (PDT)
Received: from gw01.loc ([192.168.0.65]:52087 helo=smtp.ehlo.wurstkaes.de) by hd00e.hd.wurstkaes.de with esmtp (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QF75W-0004UG-Nf; Wed, 27 Apr 2011 17:55:38 +0200
Received: from sebi by smtp.ehlo.wurstkaes.de with local (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QF752-0005Jf-8r; Wed, 27 Apr 2011 17:55:08 +0200
Date: Wed, 27 Apr 2011 17:55:08 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: ?????? <buptxiaozhu@gmail.com>
Message-ID: <20110427155508.GG3781@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <BANLkTinVVfgbmFZJ49kY6zgUpYQcycxV1Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BANLkTinVVfgbmFZJ49kY6zgUpYQcycxV1Q@mail.gmail.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 15:55:43 -0000

On Wed, Apr 27, 2011 at 11:18:23PM +0800, ?????? wrote:
> hi, Sebastian
> 
> thx for your time!
> comments inline:D
> 
> On Wed, Apr 27, 2011 at 4:22 PM, Sebastian Kiesel <ietf-alto@skiesel.de>wrote:
> 
> > Hi,
> >
> > On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:
> > > hi, everyone:
> > >
> > > have the ALTO considered the use cases of wireless, which means how to
> > make
> > > the selection of the peers in the wireless environment?
> >
> > the ALTO protocols and procedures feature mechanisms that can be
> > leveraged in a mobile / wireless scenario. IMO there are two issues:
> > what is IMO stands for?
> > 1. When a client is moving between different sections of an access
> >   network it may have to find a new ALTO server which is able
> >   to give guidance that is useful at the new client position.
> >   draft-kiesel-alto-3pdisc-05, sec. 1.3 states:
> >
> >   o  A change of the IP address at an interface invalidates the result
> >      of the ALTO server discovery procedure.  For instance, if the IP
> >      address assigned to a mobile host changes due to host mobility, it
> >      is required to run the ALTO server discovery procedure for the new
> >      IP address without relying on earlier gained information.
> what does the IP address refer to in  "it is required to run the ALTO
> server discovery procedure for the new IP address without relying on earlier
> gained information"?  the new IP address of the roaming user which may
> allocated by GGSN or wifi AP?  however, that allocation process has nothing
> to do with the ALTO server discovery. or it is not correct of  my
> understanding ?

if the client (peer) notices that it has received a new ip address from
dhcp,ggsn,etc. it has to re-run the ALTO server discovery, because
getting a new address might be the result of a (significant) movement.


> > 2. The actual strategy (algorithm) for selecting peers is out of scope
> >   of the standardization process, as there are many different scenarios
> >   with different constraints and optimization goals (e.g., in a given
> >   mobile access network, is the backhaul capacity an issue or not?).
> > can i understand "how to make the selection is the issues decided by P2P
> > application"?
> >   The ALTO client protocol together with a procedure for defining new
> >   Host Characteristics Attributes (cost types) is able to convey the
> >   input for a variety of different selection algorithms.
`
> do you mean the selection algorithms can be self-defined by client itself?

yes. the ALTO protocol specification only specifies the protocol for
requesting and receiving information from the ALTO server. This data
can be used for influencing the peer selection. But the actual algorithm
to do the selection is not being standardized, as this is highly
application specific.


regards
sebastian

From vkg@bell-labs.com  Wed Apr 27 09:05:16 2011
Return-Path: <vkg@bell-labs.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7514FE0795 for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 09:05:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bbfh5GxRt5rD for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 09:05:16 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id D7DFDE0756 for <alto@ietf.org>; Wed, 27 Apr 2011 09:05:15 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p3RG5Eq2012210 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 27 Apr 2011 11:05:15 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p3RG5E2U025952 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 27 Apr 2011 11:05:14 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p3RG5DDp028284; Wed, 27 Apr 2011 11:05:13 -0500 (CDT)
Message-ID: <4DB83F3D.8060107@bell-labs.com>
Date: Wed, 27 Apr 2011 11:07:25 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9
MIME-Version: 1.0
To: Robert Varga <robert.varga@pantheon.sk>
References: <4DB0CB13.4050602@pantheon.sk>
In-Reply-To: <4DB0CB13.4050602@pantheon.sk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: alto@ietf.org
Subject: Re: [alto] Interop at IETF-81?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 16:05:16 -0000

On 04/21/2011 07:25 PM, Robert Varga wrote:
> given the intent of doing interoperability testing during IETF-81 in
> Quebec, I think we need to start planning for that. The major
> question is which version of the ALTO Protocol draft are we going to
> standardize on. With 07 being the last one published, it may be a
> good target, but if I understand it correctly, there already are some
> proposed changes which mandate an update.
>
> Given the meeting is taking place July 24-29, I propose we decide on
> the interop standard by the end of May, which leaves ~5 weeks for
> publishing an updated draft (if that is the consensus) and whole 8
> weeks for implementations to converge on it. Would that do as a
> plan?

Robert: Thank you for getting this started.

I do think that it is time to start thinking of the logistics
related to the interop.  Please give me and my co-chairs a
couple of days to ruminate on how we want to move forward.

We will be back with a concrete plan in a day or so.

Regards,

- vijay (on behalf of Enrico and Jon as well).
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From sebi@smtp.ehlo.wurstkaes.de  Wed Apr 27 13:00:13 2011
Return-Path: <sebi@smtp.ehlo.wurstkaes.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B98E074D for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 13:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3vq9MyOKZ3T for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 13:00:11 -0700 (PDT)
Received: from hd00e.hd.wurstkaes.de (hd00e.hd.wurstkaes.de [213.240.180.126]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE39E072C for <alto@ietf.org>; Wed, 27 Apr 2011 13:00:11 -0700 (PDT)
Received: from gw01.loc ([192.168.0.65]:57858 helo=smtp.ehlo.wurstkaes.de) by hd00e.hd.wurstkaes.de with esmtp (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QFAu5-0005cY-Em; Wed, 27 Apr 2011 22:00:05 +0200
Received: from sebi by smtp.ehlo.wurstkaes.de with local (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QFAtb-0006P2-0f; Wed, 27 Apr 2011 21:59:35 +0200
Date: Wed, 27 Apr 2011 21:59:34 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: stefano previdi <sprevidi@cisco.com>
Message-ID: <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 20:00:13 -0000

Hi stefano,

On Wed, Apr 27, 2011 at 11:17:33AM +0200, stefano previdi wrote:
> On Apr 27, 2011, at 10:22 AM, Sebastian Kiesel wrote:
>> Hi,
>>
>> On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:
>>> hi, everyone:
>>>
>>> have the ALTO considered the use cases of wireless, which means how  
>>> to make
>>> the selection of the peers in the wireless environment?
>>
>> the ALTO protocols and procedures feature mechanisms that can be
>> leveraged in a mobile / wireless scenario. IMO there are two issues:
>>
>> 1. When a client is moving between different sections of an access
>>   network it may have to find a new ALTO server which is able
>>   to give guidance that is useful at the new client position.
>>   draft-kiesel-alto-3pdisc-05, sec. 1.3 states:
>>
>>   o  A change of the IP address at an interface invalidates the result
>>      of the ALTO server discovery procedure.  For instance, if the IP
>>      address assigned to a mobile host changes due to host mobility,  
>> it
>>      is required to run the ALTO server discovery procedure for the  
>> new
>>      IP address without relying on earlier gained information.
>
>
> mobility is often at layer-2 and this mean you will need some other
> mechanisms in order to enrich your maps/ecs with wireless-l2 derived
> topology info.

I agree. But the creation of maps based on the (wireless) topology and
other {cost,distance,performance,...}-related information as well as
feeding them into the ALTO server is out of scope of the protocol spec.

The paragraph above is about ALTO server discovery:

If the client notices that it has been assigned a different IP address,
one reason may be a significant movement in the network, e.g., handover
from one mobility anchor to another, and therefore a new ALTO server
discovery might be required (of course, there might be other reasons for
getting a new IP addres, but doing a new discovery then won't hurt).

Are there any networks using layer-2 mobility which are so huge, that a
client should discover and use different ALTO servers while moving
around even though it can retain the same IP address?

Thanks,
Sebastian

From buptxiaozhu@gmail.com  Wed Apr 27 18:27:52 2011
Return-Path: <buptxiaozhu@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2A5CE0849 for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 18:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.833
X-Spam-Level: 
X-Spam-Status: No, score=-2.833 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qE4UeTLVFEaH for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 18:27:52 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id C7C5AE066F for <alto@ietf.org>; Wed, 27 Apr 2011 18:27:51 -0700 (PDT)
Received: by yic13 with SMTP id 13so989965yic.31 for <alto@ietf.org>; Wed, 27 Apr 2011 18:27:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jXHAIyEmDGxp9FR5J+5vzz3yVJwiNkwsoOAuu3taYvg=; b=PjsPZVZ38xkwK+5uDlZvXs2weNvGVKiv4JQcwzf6j99jxpDW+Aa1uaaD1ZMA5Oj6Gu c/riahSFSM9SL8NVbIQjon5TisvzGGj3Z7YygDSPKBbNICVUuL91YzJtWCTBzI1ulBkN hvfnnKjXqPWOJ/XLBsIdTGGX4WqnHPNvhcd00=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=C8NY9ZPzObNQTAKWQ94tqXEFHBjIN0L9ydKJhyhXIBHpqCGW/wWPsDSFizkRPj985o Wq7Xqz610bWn0fhbgZ8Z74/DNe6LLglqSJII3GW58tP78RcNBMz4SuGJqLya2nJK/5kP K/r4SQQxNNzLZzYA/G3SEfujoUSKdpQlSV69Q=
MIME-Version: 1.0
Received: by 10.150.200.1 with SMTP id x1mr2399884ybf.387.1303954071122; Wed, 27 Apr 2011 18:27:51 -0700 (PDT)
Received: by 10.150.12.3 with HTTP; Wed, 27 Apr 2011 18:27:51 -0700 (PDT)
In-Reply-To: <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com> <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de>
Date: Thu, 28 Apr 2011 09:27:51 +0800
Message-ID: <BANLkTin-qoS0o-L-M4X9qkM2O+TPstRrAg@mail.gmail.com>
From: =?UTF-8?B?5pyx5r2H?= <buptxiaozhu@gmail.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: multipart/alternative; boundary=000e0cd348a23675e304a1f07761
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 01:27:52 -0000

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

hi Sebastian :

comments inline:D

On Thu, Apr 28, 2011 at 3:59 AM, Sebastian Kiesel <ietf-alto@skiesel.de>wro=
te:

> Hi stefano,
>
> On Wed, Apr 27, 2011 at 11:17:33AM +0200, stefano previdi wrote:
> > On Apr 27, 2011, at 10:22 AM, Sebastian Kiesel wrote:
> >> Hi,
> >>
> >> On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:
> >>> hi, everyone:
> >>>
> >>> have the ALTO considered the use cases of wireless, which means how
> >>> to make
> >>> the selection of the peers in the wireless environment?
> >>
> >> the ALTO protocols and procedures feature mechanisms that can be
> >> leveraged in a mobile / wireless scenario. IMO there are two issues:
> >>
> >> 1. When a client is moving between different sections of an access
> >>   network it may have to find a new ALTO server which is able
> >>   to give guidance that is useful at the new client position.
> >>   draft-kiesel-alto-3pdisc-05, sec. 1.3 states:
> >>
> >>   o  A change of the IP address at an interface invalidates the result
> >>      of the ALTO server discovery procedure.  For instance, if the IP
> >>      address assigned to a mobile host changes due to host mobility,
> >> it
> >>      is required to run the ALTO server discovery procedure for the
> >> new
> >>      IP address without relying on earlier gained information.
> >
> >
> > mobility is often at layer-2 and this mean you will need some other
> > mechanisms in order to enrich your maps/ecs with wireless-l2 derived
> > topology info.
>
> I agree. But the creation of maps based on the (wireless) topology and
> other {cost,distance,performance,...}-related information as well as
> feeding them into the ALTO server is out of scope of the protocol spec.
>
> why does the creation of this map is out of the scope of the protocol spe=
c?
 the ALTO server should provider the information to client to make sure tha=
t
P2P application make the appropriated selection for the wireless peer.



> The paragraph above is about ALTO server discovery:
>
> If the client notices that it has been assigned a different IP address,
> one reason may be a significant movement in the network, e.g., handover
> from one mobility anchor to another, and therefore a new ALTO server
> discovery might be required (of course, there might be other reasons for
> getting a new IP addres, but doing a new discovery then won't hurt).
>
> Are there any networks using layer-2 mobility which are so huge, that a
> client should discover and use different ALTO servers while moving
> around even though it can retain the same IP address?
>
> Thanks,
> Sebastian
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>



--=20
Best wishes,

Beijing University of Posts & Telecommunications (BUPT)
Zhu Xiao  ( =E6=9C=B1=E6=BD=87 )
E-mail: buptxiaozhu@gmail.com
mobile:+86 134-8881-9004

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

hi=C2=A0Sebastian :<div><br></div><div>comments inline:D</div><div><div><br=
><div class=3D"gmail_quote">On Thu, Apr 28, 2011 at 3:59 AM, Sebastian Kies=
el <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf-alto@skiesel.de">ietf-alto@=
skiesel.de</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;">Hi stefano,<br>
<div class=3D"im"><br>
On Wed, Apr 27, 2011 at 11:17:33AM +0200, stefano previdi wrote:<br>
&gt; On Apr 27, 2011, at 10:22 AM, Sebastian Kiesel wrote:<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:<br>
&gt;&gt;&gt; hi, everyone:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; have the ALTO considered the use cases of wireless, which mean=
s how<br>
&gt;&gt;&gt; to make<br>
&gt;&gt;&gt; the selection of the peers in the wireless environment?<br>
&gt;&gt;<br>
&gt;&gt; the ALTO protocols and procedures feature mechanisms that can be<b=
r>
&gt;&gt; leveraged in a mobile / wireless scenario. IMO there are two issue=
s:<br>
&gt;&gt;<br>
&gt;&gt; 1. When a client is moving between different sections of an access=
<br>
&gt;&gt; =C2=A0 network it may have to find a new ALTO server which is able=
<br>
&gt;&gt; =C2=A0 to give guidance that is useful at the new client position.=
<br>
&gt;&gt; =C2=A0 draft-kiesel-alto-3pdisc-05, sec. 1.3 states:<br>
&gt;&gt;<br>
&gt;&gt; =C2=A0 o =C2=A0A change of the IP address at an interface invalida=
tes the result<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0of the ALTO server discovery procedure. =C2=A0=
For instance, if the IP<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0address assigned to a mobile host changes due =
to host mobility,<br>
&gt;&gt; it<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0is required to run the ALTO server discovery p=
rocedure for the<br>
&gt;&gt; new<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0IP address without relying on earlier gained i=
nformation.<br>
&gt;<br>
&gt;<br>
&gt; mobility is often at layer-2 and this mean you will need some other<br=
>
&gt; mechanisms in order to enrich your maps/ecs with wireless-l2 derived<b=
r>
&gt; topology info.<br>
<br>
</div>I agree. But the creation of maps based on the (wireless) topology an=
d<br>
other {cost,distance,performance,...}-related information as well as<br>
feeding them into the ALTO server is out of scope of the protocol spec.<br>
<br></blockquote><div><font class=3D"Apple-style-span" color=3D"#ff0000">wh=
y does the creation of this map is out of the scope of the protocol spec? =
=C2=A0the ALTO server should provider the information to client to make sur=
e that P2P application make the=C2=A0appropriated=C2=A0selection for the wi=
reless peer.</font></div>
<div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The paragraph above is about ALTO server discovery:<br>
<br>
If the client notices that it has been assigned a different IP address,<br>
one reason may be a significant movement in the network, e.g., handover<br>
from one mobility anchor to another, and therefore a new ALTO server<br>
discovery might be required (of course, there might be other reasons for<br=
>
getting a new IP addres, but doing a new discovery then won&#39;t hurt).<br=
>
<br>
Are there any networks using layer-2 mobility which are so huge, that a<br>
client should discover and use different ALTO servers while moving<br>
around even though it can retain the same IP address?<br>
<br>
Thanks,<br>
<div><div></div><div class=3D"h5">Sebastian<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Best wishes=
,<br><br>Beijing University of Posts &amp; Telecommunications (BUPT)<br>Zhu=
 Xiao=C2=A0 ( =E6=9C=B1=E6=BD=87 )<br>E-mail: <a href=3D"mailto:buptxiaozhu=
@gmail.com" target=3D"_blank">buptxiaozhu@gmail.com</a><br>
mobile:+86 134-8881-9004<br>
</div></div>

--000e0cd348a23675e304a1f07761--

From sprevidi@cisco.com  Wed Apr 27 23:44:17 2011
Return-Path: <sprevidi@cisco.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA46CE064B for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 23:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43d18WMKUJHC for <alto@ietfa.amsl.com>; Wed, 27 Apr 2011 23:44:17 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id E8587E062A for <alto@ietf.org>; Wed, 27 Apr 2011 23:44:16 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3S6eV5j023702; Thu, 28 Apr 2011 08:40:31 +0200 (CEST)
Received: from [192.168.62.100] (ams3-vpn-dhcp7799.cisco.com [10.61.94.118]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3S6eT8S010523; Thu, 28 Apr 2011 08:40:30 +0200 (CEST)
Message-Id: <71AAC95B-4D4E-4285-8298-F5BEBAA01111@cisco.com>
From: stefano previdi <sprevidi@cisco.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
In-Reply-To: <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 28 Apr 2011 08:40:29 +0200
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com> <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de>
X-Mailer: Apple Mail (2.935.3)
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 06:44:17 -0000

On Apr 27, 2011, at 9:59 PM, Sebastian Kiesel wrote:

> Hi stefano,
>
> On Wed, Apr 27, 2011 at 11:17:33AM +0200, stefano previdi wrote:
>> On Apr 27, 2011, at 10:22 AM, Sebastian Kiesel wrote:
>>> Hi,
>>>
>>> On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:
>>>> hi, everyone:
>>>>
>>>> have the ALTO considered the use cases of wireless, which means how
>>>> to make
>>>> the selection of the peers in the wireless environment?
>>>
>>> the ALTO protocols and procedures feature mechanisms that can be
>>> leveraged in a mobile / wireless scenario. IMO there are two issues:
>>>
>>> 1. When a client is moving between different sections of an access
>>>  network it may have to find a new ALTO server which is able
>>>  to give guidance that is useful at the new client position.
>>>  draft-kiesel-alto-3pdisc-05, sec. 1.3 states:
>>>
>>>  o  A change of the IP address at an interface invalidates the  
>>> result
>>>     of the ALTO server discovery procedure.  For instance, if the IP
>>>     address assigned to a mobile host changes due to host mobility,
>>> it
>>>     is required to run the ALTO server discovery procedure for the
>>> new
>>>     IP address without relying on earlier gained information.
>>
>>
>> mobility is often at layer-2 and this mean you will need some other
>> mechanisms in order to enrich your maps/ecs with wireless-l2 derived
>> topology info.
>
> I agree. But the creation of maps based on the (wireless) topology and
> other {cost,distance,performance,...}-related information as well as
> feeding them into the ALTO server is out of scope of the protocol  
> spec.


well, yes, that's what I stated in my previous email...


> The paragraph above is about ALTO server discovery:
>
> If the client notices that it has been assigned a different IP  
> address,
> one reason may be a significant movement in the network, e.g.,  
> handover
> from one mobility anchor to another, and therefore a new ALTO server
> discovery might be required (of course, there might be other reasons  
> for
> getting a new IP addres, but doing a new discovery then won't hurt).
>
> Are there any networks using layer-2 mobility which are so huge,  
> that a
> client should discover and use different ALTO servers while moving
> around even though it can retain the same IP address?


in a clever implementation, the use of a particular ALTO server
is mostly dictated by the boundaries of the infra/routing domain
where the client resides. IOW: as long as you stay within the same
SP infrastructure, there shouldn't be reasons to change ALTO server.


s.


>
> Thanks,
> Sebastian


From sebi@smtp.ehlo.wurstkaes.de  Thu Apr 28 01:50:19 2011
Return-Path: <sebi@smtp.ehlo.wurstkaes.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2BB4E0686 for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 01:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XIYhwMupltMy for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 01:50:18 -0700 (PDT)
Received: from hd00e.hd.wurstkaes.de (hd00e.hd.wurstkaes.de [213.240.180.126]) by ietfa.amsl.com (Postfix) with ESMTP id 4354BE062A for <alto@ietf.org>; Thu, 28 Apr 2011 01:50:17 -0700 (PDT)
Received: from gw01.loc ([192.168.0.65]:44646 helo=smtp.ehlo.wurstkaes.de) by hd00e.hd.wurstkaes.de with esmtp (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QFMvL-0000l6-Ki; Thu, 28 Apr 2011 10:50:11 +0200
Received: from sebi by smtp.ehlo.wurstkaes.de with local (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QFMur-0001iB-6s; Thu, 28 Apr 2011 10:49:41 +0200
Date: Thu, 28 Apr 2011 10:49:41 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: stefano previdi <sprevidi@cisco.com>
Message-ID: <20110428084941.GA6504@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com> <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de> <71AAC95B-4D4E-4285-8298-F5BEBAA01111@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <71AAC95B-4D4E-4285-8298-F5BEBAA01111@cisco.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 08:50:19 -0000

Hi Stefano,

On Thu, Apr 28, 2011 at 08:40:29AM +0200, stefano previdi wrote:
>> Are there any networks using layer-2 mobility which are so huge, that a
>> client should discover and use different ALTO servers while moving
>> around even though it can retain the same IP address?
>
>
> in a clever implementation, the use of a particular ALTO server
> is mostly dictated by the boundaries of the infra/routing domain
> where the client resides. IOW: as long as you stay within the same
> SP infrastructure, there shouldn't be reasons to change ALTO server.

And moving to another SP implies change of mobile client's IP address?

If this is (almost) always true, a changing IP address is a good
trigger for re-discovery.

Thanks,
Sebastian


From sprevidi@cisco.com  Thu Apr 28 03:10:04 2011
Return-Path: <sprevidi@cisco.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18D6E0723 for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 03:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEd+T6wgl+Xa for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 03:10:03 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB83E0721 for <alto@ietf.org>; Thu, 28 Apr 2011 03:10:02 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3S9wkav025943; Thu, 28 Apr 2011 11:58:46 +0200 (CEST)
Received: from dhcp-rom2-144-254-191-61.cisco.com (dhcp-rom2-144-254-191-61.cisco.com [144.254.191.61]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3S9wj95000828; Thu, 28 Apr 2011 11:58:45 +0200 (CEST)
Message-Id: <63C0C7B3-BB9F-4D93-A02D-64ECB0AED615@cisco.com>
From: stefano previdi <sprevidi@cisco.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <63A9CDFD-B60E-43B3-8C7F-86F405B378E8@niven-jenkins.co.uk>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 28 Apr 2011 11:58:45 +0200
References: <63A9CDFD-B60E-43B3-8C7F-86F405B378E8@niven-jenkins.co.uk>
X-Mailer: Apple Mail (2.935.3)
Cc: Grant Watson <grant.watson@bt.com>, Nabil N Bitar <nabil.n.bitar@verizon.com>, alto@ietf.org
Subject: Re: [alto] New draft on use cases for ALTO & CDNs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 10:10:04 -0000

Ben,

On Apr 27, 2011, at 5:45 PM, Ben Niven-Jenkins wrote:
> Colleagues,
>
> During the ALTO meeting at IETF80 I made some comments at the  
> microphone highlighting my concerns with the scope of draft-penno- 
> alto-cdn-03 being far too wide and that we should first focus on  
> documenting the use cases and requirements.
>
> To that end I've been working with a couple of folks to co-author a  
> draft focussed on documenting the use cases for ALTO & CDNs, the  
> thinking being that a fresh draft with a tighter focus than draft- 
> penno-alto-cdn-03 makes highlighting and discussing the use cases  
> without slipping into possible solution mechanisms much simpler and  
> cleaner.


makes sense.


> We have just published a -00 version which is available here:
> http://tools.ietf.org/html/draft-jenkins-alto-cdn-use-cases-00
>
> So far we have only included details on two use cases and included  
> placeholders for another two because we wanted to socialise the work  
> early to see if others were interested in contributing text for the  
> use cases they have as well as to solicit early feedback on the  
> structure and focus of the draft.


splitting the current alto-cdn document makes sense to me and we
need to define:
a. use cases
b. requirements
c. proposed solutions

your draft addresses the use cases and you may want to merge the
use cases sections we currently have in the alto-cdn draft so to
focus that one only on the proposed solution(s).

The question is about requirements: do we want to include them
in one of the two drafts or into a separate document ?

s.


> Comments/Suggestions/etc on the draft are welcomed.
>
> Ben
>
>
>
>
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From sebi@smtp.ehlo.wurstkaes.de  Thu Apr 28 03:41:14 2011
Return-Path: <sebi@smtp.ehlo.wurstkaes.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5819FE06F5 for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 03:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9lFEH58mVbxA for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 03:41:13 -0700 (PDT)
Received: from hd00e.hd.wurstkaes.de (hd00e.hd.wurstkaes.de [213.240.180.126]) by ietfa.amsl.com (Postfix) with ESMTP id 3C857E0659 for <alto@ietf.org>; Thu, 28 Apr 2011 03:41:13 -0700 (PDT)
Received: from gw01.loc ([192.168.0.65]:46629 helo=smtp.ehlo.wurstkaes.de) by hd00e.hd.wurstkaes.de with esmtp (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QFOeh-0001Hr-R0; Thu, 28 Apr 2011 12:41:07 +0200
Received: from sebi by smtp.ehlo.wurstkaes.de with local (Exim 4.69) (envelope-from <sebi@smtp.ehlo.wurstkaes.de>) id 1QFOeC-0002Ex-CB; Thu, 28 Apr 2011 12:40:36 +0200
Date: Thu, 28 Apr 2011 12:40:36 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: ?????? <buptxiaozhu@gmail.com>
Message-ID: <20110428104036.GJ3781@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com> <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de> <BANLkTin-qoS0o-L-M4X9qkM2O+TPstRrAg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BANLkTin-qoS0o-L-M4X9qkM2O+TPstRrAg@mail.gmail.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 10:41:14 -0000

On Thu, Apr 28, 2011 at 09:27:51AM +0800, ?????? wrote:
> > I agree. But the creation of maps based on the (wireless) topology and
> > other {cost,distance,performance,...}-related information as well as
> > feeding them into the ALTO server is out of scope of the protocol spec.
> >
> why does the creation of this map is out of the scope of the protocol spec?

Which information to put into the map depends on the network technology,
topology, optimization goals, policies (e.g. how much information about
the network is an ISP willing to disclose), how much effort you want to
spend, etc. So it would be difficult to write down an one-size-fits-all
algorithm. Furhermore, the algorithms used for creating the maps may be
a field where different ALTO server vendors may come up with different
solutions, i.e., market competition.

For interoperability between ALTO clients and servers of different
vendors it is important that the syntax of the map and the request/reply
protocol is clearly specified. This is within the scope of the document.

> the ALTO server should provider the information to client to make sure that
> P2P application make the appropriated selection for the wireless peer.

I agree.

In your wireless scenario, is there any kind of guiding information
you would like to transport from the ALTO server to the ALTO client,
which cannot be expressed with the syntax in the current protocol
specification?


Thanks,
S.

From jmedved@juniper.net  Thu Apr 28 08:33:04 2011
Return-Path: <jmedved@juniper.net>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6403CE0685 for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 08:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KqYxZ8IMrG3 for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 08:33:03 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 70369E0670 for <alto@ietf.org>; Thu, 28 Apr 2011 08:33:03 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTbmIqH3IgVgsOcFLEVx8ZZWnLLes8izY@postini.com; Thu, 28 Apr 2011 08:33:03 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Thu, 28 Apr 2011 08:30:33 -0700
From: Jan Medved <jmedved@juniper.net>
To: stefano previdi <sprevidi@cisco.com>, Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Thu, 28 Apr 2011 08:30:30 -0700
Thread-Topic: [alto] New draft on use cases for ALTO & CDNs
Thread-Index: AcwFuTaEZ+VhbkoDSv2zy26TB5mc0A==
Message-ID: <C9DED2F8.27A3F%jmedved@juniper.net>
In-Reply-To: <63C0C7B3-BB9F-4D93-A02D-64ECB0AED615@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.10.0.110310
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Grant Watson <grant.watson@bt.com>, Nabil N Bitar <nabil.n.bitar@verizon.com>, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] New draft on use cases for ALTO & CDNs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 15:33:04 -0000

On 4/28/11 2:58 AM, "stefano previdi" <sprevidi@cisco.com> wrote:

>Ben,
>
>On Apr 27, 2011, at 5:45 PM, Ben Niven-Jenkins wrote:
>> Colleagues,
>>
>> During the ALTO meeting at IETF80 I made some comments at the
>> microphone highlighting my concerns with the scope of draft-penno-
>> alto-cdn-03 being far too wide and that we should first focus on
>> documenting the use cases and requirements.
>>
>> To that end I've been working with a couple of folks to co-author a
>> draft focussed on documenting the use cases for ALTO & CDNs, the
>> thinking being that a fresh draft with a tighter focus than draft-
>> penno-alto-cdn-03 makes highlighting and discussing the use cases
>> without slipping into possible solution mechanisms much simpler and
>> cleaner.
>
>
>makes sense.
>
>
>> We have just published a -00 version which is available here:
>> http://tools.ietf.org/html/draft-jenkins-alto-cdn-use-cases-00
>>
>> So far we have only included details on two use cases and included
>> placeholders for another two because we wanted to socialise the work
>> early to see if others were interested in contributing text for the
>> use cases they have as well as to solicit early feedback on the
>> structure and focus of the draft.
>
>
>splitting the current alto-cdn document makes sense to me and we
>need to define:
>a. use cases
>b. requirements
>c. proposed solutions

This seems to be most logical split.

>
>your draft addresses the use cases and you may want to merge the
>use cases sections we currently have in the alto-cdn draft so to
>focus that one only on the proposed solution(s).

The first two uses cases in draft-jenkins-cdn-use-cases are described in
draft-penno-alto-cdn. Agreed that the text from draft-penno-alto-cdn
should be merged into the appropriate sections of
draft-jenkins-cdn-use-cases.

>
>The question is about requirements: do we want to include them
>in one of the two drafts or into a separate document ?
>
>s.

/Jan

>
>
>> Comments/Suggestions/etc on the draft are welcomed.
>>
>> Ben
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>
>_______________________________________________
>alto mailing list
>alto@ietf.org
>https://www.ietf.org/mailman/listinfo/alto


From ben@niven-jenkins.co.uk  Thu Apr 28 11:28:00 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9F3E069A for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 11:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.927
X-Spam-Level: 
X-Spam-Status: No, score=-103.927 tagged_above=-999 required=5 tests=[AWL=-0.328, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gatdGwEH2hTc for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 11:27:59 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.64]) by ietfa.amsl.com (Postfix) with ESMTP id 72F7DE0669 for <alto@ietf.org>; Thu, 28 Apr 2011 11:27:59 -0700 (PDT)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-108-devlan.cachelogic.com) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1QFVwU-00033H-4Z; Thu, 28 Apr 2011 19:27:58 +0100
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <C9DED2F8.27A3F%jmedved@juniper.net>
Date: Thu, 28 Apr 2011 19:27:55 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2486FF57-F49D-4B62-8279-800CC0E3DB78@niven-jenkins.co.uk>
References: <C9DED2F8.27A3F%jmedved@juniper.net>
To: Jan Medved <jmedved@juniper.net>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: Grant Watson <grant.watson@bt.com>, Nabil N Bitar <nabil.n.bitar@verizon.com>, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] New draft on use cases for ALTO & CDNs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 18:28:00 -0000

Jan, Stefano, Colleagues,

On 28 Apr 2011, at 16:30, Jan Medved wrote:
> On 4/28/11 2:58 AM, "stefano previdi" <sprevidi@cisco.com> wrote:
>> splitting the current alto-cdn document makes sense to me and we
>> need to define:
>> a. use cases
>> b. requirements
>> c. proposed solutions
>=20
> This seems to be most logical split.
>=20

Agreed.

>>=20
>> your draft addresses the use cases and you may want to merge the
>> use cases sections we currently have in the alto-cdn draft so to
>> focus that one only on the proposed solution(s).
>=20
> The first two uses cases in draft-jenkins-cdn-use-cases are described =
in
> draft-penno-alto-cdn. Agreed that the text from draft-penno-alto-cdn
> should be merged into the appropriate sections of
> draft-jenkins-cdn-use-cases.

I'm OK with that. When I read draft-penno-alto-cdn I found it hard to =
extract text that is pure use case though but if you could provide text =
or pointers to sections I'm happy to start discussing how we could merge =
the use case text in draft-penno-alto-cdn with that in =
draft-jenkins-alto-cdn-use-cases.

>> The question is about requirements: do we want to include them
>> in one of the two drafts or into a separate document ?

My opinion is that the requirements should be documented separately to =
the solutions. I don't currently have a strong opinion about whether =
they should be documented in draft-jenkins-alto-cdn-use-cases or a =
separate draft.=20

Ben


From sprevidi@cisco.com  Thu Apr 28 11:47:42 2011
Return-Path: <sprevidi@cisco.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56EBAE06C3 for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 11:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kYWzQg3HAewy for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 11:47:41 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 7C350E06A8 for <alto@ietf.org>; Thu, 28 Apr 2011 11:47:41 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3SIhqRZ014479; Thu, 28 Apr 2011 20:43:52 +0200 (CEST)
Received: from [192.168.62.100] (ams3-vpn-dhcp7999.cisco.com [10.61.95.62]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3SIhnwK027132; Thu, 28 Apr 2011 20:43:50 +0200 (CEST)
Message-Id: <7EE205E8-9652-4E5E-B3D3-10994282019A@cisco.com>
From: stefano previdi <sprevidi@cisco.com>
To: Jan Medved <jmedved@juniper.net>, Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <2486FF57-F49D-4B62-8279-800CC0E3DB78@niven-jenkins.co.uk>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 28 Apr 2011 20:43:49 +0200
References: <C9DED2F8.27A3F%jmedved@juniper.net> <2486FF57-F49D-4B62-8279-800CC0E3DB78@niven-jenkins.co.uk>
X-Mailer: Apple Mail (2.935.3)
Cc: Nabil N Bitar <nabil.n.bitar@verizon.com>, alto@ietf.org, Grant Watson <grant.watson@bt.com>
Subject: Re: [alto] New draft on use cases for ALTO & CDNs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 18:47:42 -0000

Ben, Jan, Nabil, Grant, Richard, Richard, Reinaldo,

thinking more about it, I believe the requirements will have to be put
into a separate draft, for clarity.

I agree with Jan about the duplication of text between alto-cdn and your
draft so we should merge. Therefore, I'd propose the following plan:

Co-authors of alto-cdn and jenkins draft meet and propose a unified
use cases description draft. At this stage most of the work will be just
editorial (cut/paste) as we clearly agree on the content (i.e.: use case
description).

It would be good to come reasonably soon with a proposal to the WG.

How does it sound ?

s.


On Apr 28, 2011, at 8:27 PM, Ben Niven-Jenkins wrote:

> Jan, Stefano, Colleagues,
>
> On 28 Apr 2011, at 16:30, Jan Medved wrote:
>> On 4/28/11 2:58 AM, "stefano previdi" <sprevidi@cisco.com> wrote:
>>> splitting the current alto-cdn document makes sense to me and we
>>> need to define:
>>> a. use cases
>>> b. requirements
>>> c. proposed solutions
>>
>> This seems to be most logical split.
>>
>
> Agreed.
>
>>>
>>> your draft addresses the use cases and you may want to merge the
>>> use cases sections we currently have in the alto-cdn draft so to
>>> focus that one only on the proposed solution(s).
>>
>> The first two uses cases in draft-jenkins-cdn-use-cases are  
>> described in
>> draft-penno-alto-cdn. Agreed that the text from draft-penno-alto-cdn
>> should be merged into the appropriate sections of
>> draft-jenkins-cdn-use-cases.
>
> I'm OK with that. When I read draft-penno-alto-cdn I found it hard  
> to extract text that is pure use case though but if you could  
> provide text or pointers to sections I'm happy to start discussing  
> how we could merge the use case text in draft-penno-alto-cdn with  
> that in draft-jenkins-alto-cdn-use-cases.
>
>>> The question is about requirements: do we want to include them
>>> in one of the two drafts or into a separate document ?
>
> My opinion is that the requirements should be documented separately  
> to the solutions. I don't currently have a strong opinion about  
> whether they should be documented in draft-jenkins-alto-cdn-use- 
> cases or a separate draft.
>
> Ben
>


From buptxiaozhu@gmail.com  Thu Apr 28 18:13:03 2011
Return-Path: <buptxiaozhu@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59D2E06EC for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 18:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.988
X-Spam-Level: 
X-Spam-Status: No, score=-2.988 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqxoIY-UB2oY for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 18:13:03 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id E7C7DE0691 for <alto@ietf.org>; Thu, 28 Apr 2011 18:13:00 -0700 (PDT)
Received: by yxk30 with SMTP id 30so1228662yxk.31 for <alto@ietf.org>; Thu, 28 Apr 2011 18:13:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GZhJwpFFODnGoHXziiZWgU4HZkPG2zHgUbxFfLhycUQ=; b=fl43tzmw7DS7QOFy47PFDa3BC2IQXkysupySNotgTC+7p7RUpXJ2t/cylmEZITZ3XL Ae/nmIZoclPNIHEo1kJxFsltzmoy4xJyDxJZRO3140KIruCfPd8/Kg6/B6OKOiko0FP3 +1Z8Vaps89ehgZCJfXzcKTRYTWR1uwgrUcZsA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XCdyE5lVEJjsofiP+sZufUlaVYHssa54M1v6FQFcLqFCB+9FmzywnjsnDNXFvrLDJd g8g+/rc3ANp/THcJ/Q40PYOjcffar+LEOhDoYLKMnfQWDXGWUW2IxEvkIvbUrKCiVn7O Pfwns2a68I/PgXsvfZXuE9AgQIQFQSK9ef3Ng=
MIME-Version: 1.0
Received: by 10.150.68.9 with SMTP id q9mr4015586yba.102.1304039579971; Thu, 28 Apr 2011 18:12:59 -0700 (PDT)
Received: by 10.150.12.3 with HTTP; Thu, 28 Apr 2011 18:12:59 -0700 (PDT)
In-Reply-To: <20110428104036.GJ3781@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com> <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de> <BANLkTin-qoS0o-L-M4X9qkM2O+TPstRrAg@mail.gmail.com> <20110428104036.GJ3781@nat01e.ehlo.wurstkaes.de>
Date: Fri, 29 Apr 2011 09:12:59 +0800
Message-ID: <BANLkTinErkWau4P6AdyPBvCnXe4K6DNJnQ@mail.gmail.com>
From: =?UTF-8?B?5pyx5r2H?= <buptxiaozhu@gmail.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: multipart/alternative; boundary=000e0cd597deeff28804a2045fbd
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2011 01:13:04 -0000

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

hi Sebastian =EF=BC=9A

   - firstly, i agree that the creation of the map, which is tightly relate=
d
   to the algorithm, is within the protocol.
   - secondly, i am not sure the information contained in current map
   structure is complete or not, because the current protocol describe that=
 :


   1. the cost map just includes cost type and cost mode
   2. the network map just includes PID and endpoint address

does the information include the cell id or ap id?

On Thu, Apr 28, 2011 at 6:40 PM, Sebastian Kiesel <ietf-alto@skiesel.de>wro=
te:

> On Thu, Apr 28, 2011 at 09:27:51AM +0800, ?????? wrote:
> > > I agree. But the creation of maps based on the (wireless) topology an=
d
> > > other {cost,distance,performance,...}-related information as well as
> > > feeding them into the ALTO server is out of scope of the protocol spe=
c.
> > >
> > why does the creation of this map is out of the scope of the protocol
> spec?
>
> Which information to put into the map depends on the network technology,
> topology, optimization goals, policies (e.g. how much information about
> the network is an ISP willing to disclose), how much effort you want to
> spend, etc. So it would be difficult to write down an one-size-fits-all
> algorithm. Furhermore, the algorithms used for creating the maps may be
> a field where different ALTO server vendors may come up with different
> solutions, i.e., market competition.
>
> For interoperability between ALTO clients and servers of different
> vendors it is important that the syntax of the map and the request/reply
> protocol is clearly specified. This is within the scope of the document.
>
> > the ALTO server should provider the information to client to make sure
> that
> > P2P application make the appropriated selection for the wireless peer.
>
> I agree.
>
> In your wireless scenario, is there any kind of guiding information
> you would like to transport from the ALTO server to the ALTO client,
> which cannot be expressed with the syntax in the current protocol
> specification?
>
>
> Thanks,
> S.
>



--=20
Best wishes,

Beijing University of Posts & Telecommunications (BUPT)
Zhu Xiao  ( =E6=9C=B1=E6=BD=87 )
E-mail: buptxiaozhu@gmail.com
mobile:+86 134-8881-9004

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

hi=C2=A0Sebastian =EF=BC=9A<div><ul><li>firstly, i agree that the creation =
of the map, which is tightly related to the=C2=A0algorithm, is within the p=
rotocol.</li><li>secondly, i am not sure the information contained in curre=
nt map structure is complete or not, because the current protocol describe =
that :</li>

</ul><ol><li>the cost map just includes cost type and cost mode</li><li>the=
 network map just includes PID and endpoint address</li></ol><div>does the =
information include the cell id or ap id?</div><div><br><div class=3D"gmail=
_quote">
On Thu, Apr 28, 2011 at 6:40 PM, Sebastian Kiesel <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ietf-alto@skiesel.de" target=3D"_blank">ietf-alto@skiesel.de=
</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>On Thu, Apr 28, 2011 at 09:27:51AM +080=
0, ?????? wrote:<br>
&gt; &gt; I agree. But the creation of maps based on the (wireless) topolog=
y and<br>
&gt; &gt; other {cost,distance,performance,...}-related information as well=
 as<br>
&gt; &gt; feeding them into the ALTO server is out of scope of the protocol=
 spec.<br>
&gt; &gt;<br>
&gt; why does the creation of this map is out of the scope of the protocol =
spec?<br>
<br>
</div>Which information to put into the map depends on the network technolo=
gy,<br>
topology, optimization goals, policies (e.g. how much information about<br>
the network is an ISP willing to disclose), how much effort you want to<br>
spend, etc. So it would be difficult to write down an one-size-fits-all<br>
algorithm. Furhermore, the algorithms used for creating the maps may be<br>
a field where different ALTO server vendors may come up with different<br>
solutions, i.e., market competition.<br>
<br>
For interoperability between ALTO clients and servers of different<br>
vendors it is important that the syntax of the map and the request/reply<br=
>
protocol is clearly specified. This is within the scope of the document.<br=
>
<div><br>
&gt; the ALTO server should provider the information to client to make sure=
 that<br>
&gt; P2P application make the appropriated selection for the wireless peer.=
<br>
<br>
</div>I agree.<br>
<br>
In your wireless scenario, is there any kind of guiding information<br>
you would like to transport from the ALTO server to the ALTO client,<br>
which cannot be expressed with the syntax in the current protocol<br>
specification?<br>
<br>
<br>
Thanks,<br>
<font color=3D"#888888">S.<br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br>Best wishes,<br>=
<br>Beijing University of Posts &amp; Telecommunications (BUPT)<br>Zhu Xiao=
=C2=A0 ( =E6=9C=B1=E6=BD=87 )<br>E-mail: <a href=3D"mailto:buptxiaozhu@gmai=
l.com" target=3D"_blank">buptxiaozhu@gmail.com</a><br>

mobile:+86 134-8881-9004<br>
</div></div>

--000e0cd597deeff28804a2045fbd--

From buptxiaozhu@gmail.com  Fri Apr 29 00:25:57 2011
Return-Path: <buptxiaozhu@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29EB2E067C for <alto@ietfa.amsl.com>; Fri, 29 Apr 2011 00:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.066
X-Spam-Level: 
X-Spam-Status: No, score=-3.066 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58l5faSdBRXR for <alto@ietfa.amsl.com>; Fri, 29 Apr 2011 00:25:56 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0B09DE068B for <alto@ietf.org>; Fri, 29 Apr 2011 00:25:55 -0700 (PDT)
Received: by yxk30 with SMTP id 30so1301136yxk.31 for <alto@ietf.org>; Fri, 29 Apr 2011 00:25:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4vouuJgoR+1WEhpEDBkt7vRhdtb6aqhqneONMM8hIX8=; b=UuC2nNbhiDqy9hIVWgK20dRk6PIPD+UNDaukvoND2/TUq3YKGc8tqPlXEQdnG7N+jP PhOra4/AZvKOFVjH4mYmlOdF0x6FM9wG+E1iMRXeJ3wpo+mbkMdQhis3fsX9fdHFSRA3 RUAKvL3OcozxQpbgmYfWtzGXRGRrjmIiyfi8A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=E/1TK8ui6v7QnH992OgbLxMarvvB8ZtbrEu0mgtajNfa7V/Z7Co26PYA7c0KuQEXF+ wsP6taceIaeMChLNipXOYdU9CmJRj/vqpbBAVbEGou4xWH55rPPFI6mDpEoKyea4yn2s vUBIN2aYc5tqphsLNAsKte77RCLXbsyDVKkg0=
MIME-Version: 1.0
Received: by 10.151.79.5 with SMTP id g5mr4263693ybl.330.1304061955308; Fri, 29 Apr 2011 00:25:55 -0700 (PDT)
Received: by 10.150.12.3 with HTTP; Fri, 29 Apr 2011 00:25:55 -0700 (PDT)
In-Reply-To: <20110428104036.GJ3781@nat01e.ehlo.wurstkaes.de>
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com> <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de> <BANLkTin-qoS0o-L-M4X9qkM2O+TPstRrAg@mail.gmail.com> <20110428104036.GJ3781@nat01e.ehlo.wurstkaes.de>
Date: Fri, 29 Apr 2011 15:25:55 +0800
Message-ID: <BANLkTikgTa5qLEqXQ8t_bJB3YtaowJUhpA@mail.gmail.com>
From: =?UTF-8?B?5pyx5r2H?= <buptxiaozhu@gmail.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: multipart/alternative; boundary=0015174bed889c7e4204a209959e
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2011 07:25:57 -0000

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

hi Sebastian =EF=BC=9A

   - firstly, i agree that the creation of the map, which is tightly relate=
d
   to the algorithm, is within the protocol.
   - secondly, i am not sure the information contained in current map
   structure is complete or not, because the current protocol describe that=
 :


   1. the cost map just includes cost type and cost mode
   2. the network map just includes PID and endpoint address

does the information include the cell id or ap id?

On Thu, Apr 28, 2011 at 6:40 PM, Sebastian Kiesel <ietf-alto@skiesel.de>wro=
te:

> On Thu, Apr 28, 2011 at 09:27:51AM +0800, ?????? wrote:
> > > I agree. But the creation of maps based on the (wireless) topology an=
d
> > > other {cost,distance,performance,...}-related information as well as
> > > feeding them into the ALTO server is out of scope of the protocol spe=
c.
> > >
> > why does the creation of this map is out of the scope of the protocol
> spec?
>
> Which information to put into the map depends on the network technology,
> topology, optimization goals, policies (e.g. how much information about
> the network is an ISP willing to disclose), how much effort you want to
> spend, etc. So it would be difficult to write down an one-size-fits-all
> algorithm. Furhermore, the algorithms used for creating the maps may be
> a field where different ALTO server vendors may come up with different
> solutions, i.e., market competition.
>
> For interoperability between ALTO clients and servers of different
> vendors it is important that the syntax of the map and the request/reply
> protocol is clearly specified. This is within the scope of the document.
>
> > the ALTO server should provider the information to client to make sure
> that
> > P2P application make the appropriated selection for the wireless peer.
>
> I agree.
>
> In your wireless scenario, is there any kind of guiding information
> you would like to transport from the ALTO server to the ALTO client,
> which cannot be expressed with the syntax in the current protocol
> specification?
>
>
> Thanks,
> S.
>



--=20
Best wishes,

Beijing University of Posts & Telecommunications (BUPT)
Zhu Xiao  ( =E6=9C=B1=E6=BD=87 )
E-mail: buptxiaozhu@gmail.com
mobile:+86 134-8881-9004

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

hi=C2=A0Sebastian =EF=BC=9A<div><ul><li>firstly, i agree that the creation =
of the map, which is tightly related to the=C2=A0algorithm, is within the p=
rotocol.</li><li>secondly, i am not sure the information contained in curre=
nt map structure is complete or not, because the current protocol describe =
that :</li>
</ul><ol><li>the cost map just includes cost type and cost mode</li><li>the=
 network map just includes PID and endpoint address</li></ol><div>does the =
information include the cell id or ap id?</div><div><br><div class=3D"gmail=
_quote">
On Thu, Apr 28, 2011 at 6:40 PM, Sebastian Kiesel <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ietf-alto@skiesel.de">ietf-alto@skiesel.de</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Thu, Apr 28, 2011 at 09:27:51AM +0800, ?????? wrote:<b=
r>
&gt; &gt; I agree. But the creation of maps based on the (wireless) topolog=
y and<br>
&gt; &gt; other {cost,distance,performance,...}-related information as well=
 as<br>
&gt; &gt; feeding them into the ALTO server is out of scope of the protocol=
 spec.<br>
&gt; &gt;<br>
&gt; why does the creation of this map is out of the scope of the protocol =
spec?<br>
<br>
</div>Which information to put into the map depends on the network technolo=
gy,<br>
topology, optimization goals, policies (e.g. how much information about<br>
the network is an ISP willing to disclose), how much effort you want to<br>
spend, etc. So it would be difficult to write down an one-size-fits-all<br>
algorithm. Furhermore, the algorithms used for creating the maps may be<br>
a field where different ALTO server vendors may come up with different<br>
solutions, i.e., market competition.<br>
<br>
For interoperability between ALTO clients and servers of different<br>
vendors it is important that the syntax of the map and the request/reply<br=
>
protocol is clearly specified. This is within the scope of the document.<br=
>
<div class=3D"im"><br>
&gt; the ALTO server should provider the information to client to make sure=
 that<br>
&gt; P2P application make the appropriated selection for the wireless peer.=
<br>
<br>
</div>I agree.<br>
<br>
In your wireless scenario, is there any kind of guiding information<br>
you would like to transport from the ALTO server to the ALTO client,<br>
which cannot be expressed with the syntax in the current protocol<br>
specification?<br>
<br>
<br>
Thanks,<br>
<font color=3D"#888888">S.<br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br>Best wishes,<br>=
<br>Beijing University of Posts &amp; Telecommunications (BUPT)<br>Zhu Xiao=
=C2=A0 ( =E6=9C=B1=E6=BD=87 )<br>E-mail: <a href=3D"mailto:buptxiaozhu@gmai=
l.com" target=3D"_blank">buptxiaozhu@gmail.com</a><br>
mobile:+86 134-8881-9004<br>
</div></div>

--0015174bed889c7e4204a209959e--

From sprevidi@cisco.com  Fri Apr 29 03:11:30 2011
Return-Path: <sprevidi@cisco.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF279E06F2 for <alto@ietfa.amsl.com>; Fri, 29 Apr 2011 03:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5mNzLZXnGj9l for <alto@ietfa.amsl.com>; Fri, 29 Apr 2011 03:11:29 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 81CFEE06DD for <alto@ietf.org>; Fri, 29 Apr 2011 03:11:29 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3T8vqPt002975; Fri, 29 Apr 2011 10:57:52 +0200 (CEST)
Received: from [192.168.62.100] (dhcp-10-55-82-129.cisco.com [10.55.82.129]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p3T8vlTH028851; Fri, 29 Apr 2011 10:57:47 +0200 (CEST)
Message-Id: <948E1F17-234A-4393-9B95-4895B4C7E1B8@cisco.com>
From: stefano previdi <sprevidi@cisco.com>
To: =?UTF-8?B?5pyx5r2H?= <buptxiaozhu@gmail.com>
In-Reply-To: <BANLkTinErkWau4P6AdyPBvCnXe4K6DNJnQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 29 Apr 2011 10:57:46 +0200
References: <BANLkTimR2KFY5zYHyVAV6TFPJU2L=P5upw@mail.gmail.com> <20110427082235.GF3781@nat01e.ehlo.wurstkaes.de> <6F83CBA0-F0B9-4D5A-82E2-2F7FE6480CE3@cisco.com> <20110427195934.GH3781@nat01e.ehlo.wurstkaes.de> <BANLkTin-qoS0o-L-M4X9qkM2O+TPstRrAg@mail.gmail.com> <20110428104036.GJ3781@nat01e.ehlo.wurstkaes.de> <BANLkTinErkWau4P6AdyPBvCnXe4K6DNJnQ@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
Cc: alto@ietf.org
Subject: Re: [alto] some use cases and its considerations in ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2011 10:11:30 -0000

On Apr 29, 2011, at 3:12 AM, =E6=9C=B1=E6=BD=87 wrote:
> hi Sebastian =EF=BC=9A
> 	=E2=80=A2 firstly, i agree that the creation of the map, which =
is tightly =20
> related to the algorithm, is within the protocol.


the protocol specifies the semantic of the map content. How you
came to that (from whatever source) is out of protocol spec.


> 	=E2=80=A2 secondly, i am not sure the information contained in =
current map =20
> structure is complete or not, because the current protocol describe =20=

> that :
> 	=E2=80=A2 the cost map just includes cost type and cost mode


I believe the cost mode will reflect the topology layer you leveraged
in order to build your maps/ecs.


> 	=E2=80=A2 the network map just includes PID and endpoint address
> does the information include the cell id or ap id?


it will be reflected in your pid's.

s.



> On Thu, Apr 28, 2011 at 6:40 PM, Sebastian Kiesel =
<ietf-alto@skiesel.de=20
> > wrote:
> On Thu, Apr 28, 2011 at 09:27:51AM +0800, ?????? wrote:
> > > I agree. But the creation of maps based on the (wireless) =20
> topology and
> > > other {cost,distance,performance,...}-related information as =20
> well as
> > > feeding them into the ALTO server is out of scope of the =20
> protocol spec.
> > >
> > why does the creation of this map is out of the scope of the =20
> protocol spec?
>
> Which information to put into the map depends on the network =20
> technology,
> topology, optimization goals, policies (e.g. how much information =20
> about
> the network is an ISP willing to disclose), how much effort you want =20=

> to
> spend, etc. So it would be difficult to write down an one-size-fits-=20=

> all
> algorithm. Furhermore, the algorithms used for creating the maps may =20=

> be
> a field where different ALTO server vendors may come up with different
> solutions, i.e., market competition.
>
> For interoperability between ALTO clients and servers of different
> vendors it is important that the syntax of the map and the request/=20
> reply
> protocol is clearly specified. This is within the scope of the =20
> document.
>
> > the ALTO server should provider the information to client to make =20=

> sure that
> > P2P application make the appropriated selection for the wireless =20
> peer.
>
> I agree.
>
> In your wireless scenario, is there any kind of guiding information
> you would like to transport from the ALTO server to the ALTO client,
> which cannot be expressed with the syntax in the current protocol
> specification?
>
>
> Thanks,
> S.
>
>
>
> --=20
> Best wishes,
>
> Beijing University of Posts & Telecommunications (BUPT)
> Zhu Xiao  ( =E6=9C=B1=E6=BD=87 )
> E-mail: buptxiaozhu@gmail.com
> mobile:+86 134-8881-9004


From ben@niven-jenkins.co.uk  Fri Apr 29 04:36:45 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D35BE06FE for <alto@ietfa.amsl.com>; Fri, 29 Apr 2011 04:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.186
X-Spam-Level: 
X-Spam-Status: No, score=-103.186 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wzuaxrsH6nv for <alto@ietfa.amsl.com>; Fri, 29 Apr 2011 04:36:44 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id C8980E06DD for <alto@ietf.org>; Fri, 29 Apr 2011 04:36:44 -0700 (PDT)
Received: from cpc10-cmbg15-2-0-cust121.5-4.cable.virginmedia.com ([86.30.246.122] helo=[192.168.0.3]) by mail10.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1QFm03-0002Gc-Jr for alto@ietf.org; Fri, 29 Apr 2011 12:36:43 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Message-Id: <4B6D7A00-499E-4218-8FA7-B40976BAB57C@niven-jenkins.co.uk>
Date: Fri, 29 Apr 2011 12:36:42 +0100
To: alto@ietf.org
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [alto] draft-ietf-alto-reqs-08 & CDNs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2011 11:36:45 -0000

Colleagues,

During the ALTO WG meeting at IETF 80 it was requested that people =
review draft-ietf-alto-reqs-08 to ensure that the stated requirements do =
not conflict with any upcoming CDN work.

Today I read draft-ietf-alto-reqs-08 in detail and it is my opinion that =
while the use cases for ALTO & CDN may raise additional requirements, =
none of the current requirements would prevent the use of ALTO in the =
context of a CDN.

However, my reading of the draft generated a number of comments which I =
will detail in a separate e-mail to the mailing list.

Ben


From ben@niven-jenkins.co.uk  Fri Apr 29 04:52:56 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA21E074A for <alto@ietfa.amsl.com>; Fri, 29 Apr 2011 04:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.279
X-Spam-Level: 
X-Spam-Status: No, score=-103.279 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id onnpIHBy6y5w for <alto@ietfa.amsl.com>; Fri, 29 Apr 2011 04:52:52 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.64]) by ietfa.amsl.com (Postfix) with ESMTP id 09B09E06C0 for <alto@ietf.org>; Fri, 29 Apr 2011 04:52:52 -0700 (PDT)
Received: from cpc10-cmbg15-2-0-cust121.5-4.cable.virginmedia.com ([86.30.246.122] helo=[192.168.0.3]) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1QFmFe-0003jh-AO for alto@ietf.org; Fri, 29 Apr 2011 12:52:51 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=windows-1252
Message-Id: <896E0EF5-C67E-4BF4-B907-51C5DA426F03@niven-jenkins.co.uk>
Date: Fri, 29 Apr 2011 12:52:49 +0100
To: alto@ietf.org
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [alto] Comments on draft-ietf-alto-reqs-08
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2011 11:52:56 -0000

Colleagues,

Today I read draft-ietf-alto-reqs-08 in detail and my reading of the =
draft generated a number of comments which I have detailed below.

I appreciate that WG Last Call for draft-ietf-alto-reqs ended on the =
25th February and that therefore my comments are somewhat late, for that =
I apologise and can only offer the excuse that I was not actually active =
in ALTO work during the Last Call period.

I hope my comments can still be taken into account as I believe that =
addressing them will result in am improved document.

My comments:

1)
I'm not sure it's reasonable to reference the ALTO Charter without =
giving a link as the charter will change over time and the reference is =
likely intended to be a reference to a historical version of the =
charter.

The current [ALTO-charter] reference refers to the Feb 2009 charter for =
which a suitable link may be:
http://tools.ietf.org/wg/alto/charters?item=3Dcharter-alto-2009-02-11.txt

2)
The requirement numbering appears to embed the draft's version number =
within the requirement number. Is the intent to remove that when =
published as an RFC and have numbers like AR-1?=20

3)
Throughout the document I find the use of "client protocol" confusing. =
Surely it is just the "ALTO protocol". draft-ietf-alto-protocol-07 does =
not use the term "client protocol" at all.

4)
ARv08-1 would appear to be redundant as it essentially states "An ALTO =
server MUST implement the ALTO Protocol" which is simply obvious and I =
wouldn't think need to be explicitly stated, although stating it is =
harmless.

5)
The same comment as for ARv08-1 applies to ARv08-2 except =
s/server/client/

6)
   ARv08-3: The format of the ALTO query message MUST allow the
   ALTO client to solicit guidance for selecting appropriate resource
   providers.

I'm struggling to parse what this requirement actually means. I think =
what is trying to be conveyed is that the ALTO protocol MUST support a =
service to enable an ALTO client to present a list of candidates =
resource providers and have the ALTO server provide guidance on the =
ranking of those candidates? I don't see what that really has to do with =
the format of query message.

7)
Similarly for ARv08-4 if there is a requirement for the ALTO protocol to =
support a service where to ALTO server offers guidance to clients is it =
really necessary to explicitly state that the format of the ALTO =
response message MUST support encoding that guidance. The phrase =
teaching granny to suck eggs comes to mind.

8)
   REQ.  ARv08-5: The detailed specification of a protocol is out of the
   scope of this document.  However, any protocol specification that
   claims to implement the ALTO client protocol MUST be compliant to the
   requirements itemized in this document.

I'm not sure what is meant by "MUST be compliant" in this context - the =
ALTO protocol it MUST include protocol elements for all MUST =
requirements, for all MUST & SHOULD requirements, something else? Anyway =
this requirement seems aimed at setting some ground rules for comparing =
different proposed protocol solutions against one another and as far as =
I can see there is only one candidate protocol being developed and =
therefore the requirement would seem somewhat redundant.=20

9)
   REQ.  ARv08-6: The ALTO client protocol MUST support the usage of
   several different host group descriptor types.

"MUST support =85 several" is very vague for a MUST level requirement. A =
pedant could say a protocol that only supports 3 different host group =
descriptors is sufficient and I don't think that's really the intent of =
the requirement.

I would suggest re-wording/re-structuring ARv08-6, ARv08-7, ARv08-8 & =
ARv08-9 to more clearly express the following intent (if you agree I can =
work with the authors to produce exact text):

- The ALTO protocol MUST support Host group descriptors of type IPv4 =
prefix & IPv6 prefix
- The ALTO protocol MUST be extensible to enable support of other host =
group descriptor types in future, for example by explicitly typing host =
group descriptor records and maintaining an IANA registry of defined =
types.
- The ALTO protocol MUST define a minimum set of host group descriptor =
types that MUST be supported by all implementations in order to aid =
inter-operability.

10)
ARv08-11 & ARv08-12. While the intent of these requirements may be =
laudable I really struggle to envision how they could actually be =
implemented or whether they are actually achievable in all =
circumstances.

11)
ARv08-14 appears to be a duplicate of ARv08-13

12)
ARv08-15 is similar to ARv08-6 in that it states the protocol "MUST =
support =85 several" and the following requirements 16, 17 & 18 are =
similar than requirements 7, 8 & 9.

I'd suggest removing ARv08-15 and then either inserting a requirement =
between 17 & 18 (or including some text in 18) to state that the =
protocol MUST be extensible to enable the support of new rating =
criteria.

Also you may want to consider explicitly stating what the "basic set of =
criteria types, which MUST be supported are". "Relative operator's =
preference" is obviously one as it's an explicit requirement for the =
protocol to support it but are there others?

13)
   REQ.  ARv08-20: Applications using ALTO guidance MUST NOT rely on the
   ALTO guidance to avoid network congestion.  Instead, applications
   MUST use other appropriate means, such as TCP based transport, to
   avoid causing excessive congestion.

I struggle to see the relevance of the second sentence to the =
requirement. The first sentence essentially says "in the presence of =
congestion you MUST NOT rely on ALTO to avoid that congestion" which =
seems reasonable, however the second sentence says "applications should =
avoid causing excessive congestion" which doesn't appear to relate to =
the requirement to not use ALTO to avoid congestion that has already =
been caused (quite possibly by a different application/client/user). I'd =
suggest removing the second sentence.

14)
ARv08-21 & 22 are similar to ARv08-3 & 4. I don't think the query =
message/response is relevant. I think you want the protocol to allow an =
ALTO client to request guidance based on the client's preferred rating =
criteria.

Also ARv08-21 mentions the client being able to express a relative =
relevance between different rating criteria but it is unclear to me how =
an ALTO server could satisfy such a requirement given that it may not be =
possible to directly compare (and therefore order) different rating =
criteria. If this part of the requirement is to remain I think you need =
to be more explicit about what you mean by "relative relevance"

15)
ARv08-24 & 25. I don't think the placement of the ALTO client relative =
to the ultimate consumer of the information really affects the mode of =
operation of the protocol.

I think what you want to express is:
- An ALTO server MUST NOT assume that the ALTO client making requests =
will be the ultimate consumer of the information contained in any =
response.
- The ALTO protocol MUST support embedding any required consumer related =
information in the protocol itself.

16)
ARv08-26. Do you really mean to restrict this requirement to only =
separation from "the operator of the IP access network" or do you =
actually mean to say "The ALTO protocol MUST be designed in a way that =
the ALTO service can be provided by an entity which is not the operator =
of the underlying [IP?] network"?

17)
   REQ.  ARv08-28: The ALTO client protocol MUST support at least one of
   these two modes, either the target-aware or the target-independent
   query mode.

   REQ.  ARv08-29: The ALTO client protocol SHOULD support both the
   target-aware and the target-independent query mode.

Do you really mean this? I can see that an implementation may only want =
to support one or other mode, but if both modes are valid then surely =
the protocol itself should provide support for both and I believe the =
ALTO protocol spec does in fact support both modes.

18)
   REQ.  ARv08-30: The ALTO client protocol SHOULD support lifetime
   attributes, to enable caching of recommendations at ALTO clients.

What is a "lifetime attribute"? It implies to me an attribute that is =
permanent whereas I suspect you really mean "a TTL or similar mechanism, =
to enable caching"?

19)
   REQ.  ARv08-31: The ALTO client protocol SHOULD specify an aging
   mechanism, which allows to give newer recommendations precedence over
   older ones.

I don't really understand the motivation for this requirement. Surely =
more recent responses always take precedence over earlier responses? I'm =
struggling to see a situation where a client would receive a "younger" =
recommendation before an "older" one and need the capability to say =
"although I received recommendation X after recommendation Y I can see =
that Y is younger so I will discard X".

20)
ARv08-33 is pretty vague. I'm not sure a requirement that essentially =
states that the protocol MUST support scenarios where the client is =
behind NAT by itself is implementable. Are there specific use cases that =
could be articulated that the protocol needs to accommodate for?

21)
   REQ.  ARv08-40: An ALTO server, which is operating close to its
   capacity limit, MUST be able to inform clients about its impending
   overload situation, and reject new conversation attempts.

I'm not sure how this would be implemented. If the server is able to =
inform the client about its impending overload, has it not by definition =
already entered into a conversation with the client and therefore the =
situation is already covered by ARv08-39?

22)
In the first sentence of section 3.2 I think "one or more" is better =
language to use rather than "one or several". I would also s/is =
supported/may be supported/

Additionally the introduction text in section 3.2 seems to end rather =
abruptly and not be entirely related to the rest of the section.

Was there an intent to have some additional text, for example "The =
following requirements apply to any ALTO server discovery mechanism"?

23)
ARv08-41, 42, 43 & 44. Is there really any value in separating out =
requirements between "resource consumer initiated ALTO server discovery" =
and "third-party ALTO server discovery" given that the requirements are =
actually identical?

I think the actual requirements are:
- An ALTO server discovery mechanism MUST support ALTO server discovery =
by ALTO clients irrespective of whether the ALTO client will be the =
ultimate consumer of the ALTO information or whether the ALTO client =
will be making queries on behalf on another entity which is the ultimate =
consumer.
- ALTO clients MUST be able to perform ALTO server discovery =
irrespective of whether they or the ultimate consumer of the ALTO =
information are located behind NAT.

24)
ARv08-49, 50 & 51. The intent is not that authentication and encryption =
mechanisms MUST be built-in to the protocol itself but that the =
requirement can be adequately met by a substrate over which the ALTO =
protocol operates (e.g. mechanisms already provided by HTTP/HTTPS)?

25)
   REQ.  ARv08-52: The ALTO client protocol MUST support different
   levels of detail in queries and responses, in order for the operator
   of an ALTO service to be able to control how much information (e.g.,
   about the network topology) is disclosed.

Is this really a requirement on the ALTO protocol or is it a requirement =
on the ALTO server?

The same comment also applies to ARv08-54.

26)
ARv08-53. This requirement seems related to ARv08-32 on reuse of =
responses and may be better place after that requirement to make the =
association between the two clearer.

27)
   REQ.  ARv08-55: The ALTO client protocol SHOULD be defined in a way,
   that the operator of one ALTO server cannot easily deduce the
   resource identifier (e.g., file name in P2P file sharing) which the
   resource consumer seeking ALTO guidance wants to access.

Is the intent
A) A P2P (or other) client does not want to expose themselves or their =
clients to revealing the actual resources they intend to =
access/distribute; or
B) A P2P (or other) client may be willing to reveal the resource they =
intend to access to their local ALTO server but does not want that =
information being redistributed?

Given that ALTO is independent of resource identifier and is about =
relationships between end points not between resources it seems to be an =
irrelevant requirement. Or if the intent is (A) it is probably better =
stated along those lines, e.g. that the ALTO protocol SHOULD NOT require =
the specific resource to be accessed to be included in ALTO requests.

I can see that an ALTO server may want to return different responses =
depending on the category of resource (or possibly more precisely the =
category of consumer) and we don't want to preclude that, e.g. returning =
a different response to a P2P client than it would to a CDN.

28)
   REQ.  ARv08-56: The ALTO client protocol MUST support appropriate
   mechanisms to protect the ALTO service against DoS attacks.

Is this actually a requirement on the protocol itself, i.e. that it =
needs specific protocol machinery to protect against DoS attacks or is =
it a more general requirement on server implementation and deployment =
strategy?

29)
Section 5.2.1 & 5.2.3 cover a number of potential security issues and =
cite examples of how they may be addressed. It might be useful to also =
refer to specific requirements stated earlier in the document that =
address those scenarios.

Even if not included directly within the document such an exercise (if =
it hasn't been done already) might help to ensure a possible requirement =
has not been inadvertently overlooked.


Ben


From richard.alimi@gmail.com  Sat Apr 30 08:30:34 2011
Return-Path: <richard.alimi@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6E8E06D5 for <alto@ietfa.amsl.com>; Sat, 30 Apr 2011 08:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCySr21eldEm for <alto@ietfa.amsl.com>; Sat, 30 Apr 2011 08:30:33 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id B9331E0664 for <alto@ietf.org>; Sat, 30 Apr 2011 08:30:33 -0700 (PDT)
Received: by iwn39 with SMTP id 39so4782789iwn.31 for <alto@ietf.org>; Sat, 30 Apr 2011 08:30:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type; bh=RFblxWdDSSYsMFC+qdi+YwBwnRX+xmFcdi51UdcTqqs=; b=Z6naAApkZHK7bPmT7yY304pLZOTVTVqZnhjn4LzAmND9G8U2zWSBbmoNxPJmqxGiND i/iXNuEKoNMoybtOYRbsrz5UpDNU/wzCpAk5vhK7dgHfp5rvUJoBAHc+oQ4IjxGbboF4 RssW13bDgbYaCvTndWPisxXdMQC1AHBzWCOMk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=a+sb8ZBwN8LTLCerOUvcAAum915GZJJVrV6di0ACcfGQ4SytzSse2zezulhVsnHwbq yIc2ZUcAz/j5CJmBrCJgyR+UZwInWwgDQQPeDTiN3OTNbzo+cp0v2h0/kodlrgZOD0MT ucR+qqHhQ5/OX2/Q8i51/gMmFOBHVL8B/g7rg=
Received: by 10.42.1.12 with SMTP id 12mr7976971ice.366.1304177433267; Sat, 30 Apr 2011 08:30:33 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.172.14 with HTTP; Sat, 30 Apr 2011 08:30:13 -0700 (PDT)
In-Reply-To: <7EE205E8-9652-4E5E-B3D3-10994282019A@cisco.com>
References: <C9DED2F8.27A3F%jmedved@juniper.net> <2486FF57-F49D-4B62-8279-800CC0E3DB78@niven-jenkins.co.uk> <7EE205E8-9652-4E5E-B3D3-10994282019A@cisco.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sat, 30 Apr 2011 08:30:13 -0700
X-Google-Sender-Auth: V8HOhtWumALyA4LCNKj5PVy1hI0
Message-ID: <BANLkTimH+QB=Excv0ab4ntgXeUV01WYKiw@mail.gmail.com>
To: stefano previdi <sprevidi@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Nabil N Bitar <nabil.n.bitar@verizon.com>, alto@ietf.org, Grant Watson <grant.watson@bt.com>
Subject: Re: [alto] New draft on use cases for ALTO & CDNs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Apr 2011 15:30:34 -0000

On Thu, Apr 28, 2011 at 11:43 AM, stefano previdi <sprevidi@cisco.com> wrote:
> Ben, Jan, Nabil, Grant, Richard, Richard, Reinaldo,
>
> thinking more about it, I believe the requirements will have to be put
> into a separate draft, for clarity.
>
> I agree with Jan about the duplication of text between alto-cdn and your
> draft so we should merge. Therefore, I'd propose the following plan:
>
> Co-authors of alto-cdn and jenkins draft meet and propose a unified
> use cases description draft. At this stage most of the work will be just
> editorial (cut/paste) as we clearly agree on the content (i.e.: use case
> description).
>
> It would be good to come reasonably soon with a proposal to the WG.
>
> How does it sound ?

This sounds great to me.

Rich

>
> s.
>
>
> On Apr 28, 2011, at 8:27 PM, Ben Niven-Jenkins wrote:
>
>> Jan, Stefano, Colleagues,
>>
>> On 28 Apr 2011, at 16:30, Jan Medved wrote:
>>>
>>> On 4/28/11 2:58 AM, "stefano previdi" <sprevidi@cisco.com> wrote:
>>>>
>>>> splitting the current alto-cdn document makes sense to me and we
>>>> need to define:
>>>> a. use cases
>>>> b. requirements
>>>> c. proposed solutions
>>>
>>> This seems to be most logical split.
>>>
>>
>> Agreed.
>>
>>>>
>>>> your draft addresses the use cases and you may want to merge the
>>>> use cases sections we currently have in the alto-cdn draft so to
>>>> focus that one only on the proposed solution(s).
>>>
>>> The first two uses cases in draft-jenkins-cdn-use-cases are described in
>>> draft-penno-alto-cdn. Agreed that the text from draft-penno-alto-cdn
>>> should be merged into the appropriate sections of
>>> draft-jenkins-cdn-use-cases.
>>
>> I'm OK with that. When I read draft-penno-alto-cdn I found it hard to
>> extract text that is pure use case though but if you could provide text or
>> pointers to sections I'm happy to start discussing how we could merge the
>> use case text in draft-penno-alto-cdn with that in
>> draft-jenkins-alto-cdn-use-cases.
>>
>>>> The question is about requirements: do we want to include them
>>>> in one of the two drafts or into a separate document ?
>>
>> My opinion is that the requirements should be documented separately to the
>> solutions. I don't currently have a strong opinion about whether they should
>> be documented in draft-jenkins-alto-cdn-use-cases or a separate draft.
>>
>> Ben
>>
>
>

From richard.alimi@gmail.com  Sat Apr 30 09:10:36 2011
Return-Path: <richard.alimi@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B20D9E0664 for <alto@ietfa.amsl.com>; Sat, 30 Apr 2011 09:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djZoKEt+g-5t for <alto@ietfa.amsl.com>; Sat, 30 Apr 2011 09:10:36 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 06C3DE069D for <alto@ietf.org>; Sat, 30 Apr 2011 09:10:35 -0700 (PDT)
Received: by iyn15 with SMTP id 15so4791940iyn.31 for <alto@ietf.org>; Sat, 30 Apr 2011 09:10:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=jaSzEVfdv964XI0foB17o8wvXa277p8AyHuW2KT+qSI=; b=ChqPr5cnGTbmd+gNkcKTCwJFczDI1w/sb8ncQVXu/5+Z8yUtmkEC4nkzqYiqJmLz0D +9ILxovRnpYd8eDuO6tlkpIPfN5d2lpH45svpKNvliPwvdkm9n4aCdkVpss/aU1Z5Myw oOe4wRfxUx6LGV6ei5dW5JOBC2vwwjx8qRyhA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=hJ/xE62shqjrRfvFoKW/SM/Y5rDhUhgkxyjvGRZ6p/L+zbCTZlI+QqwJ+VPOb92fjU WLHfd8w/2LVvTpOSLKVNT+jnNXyyhuobEgtqBJ3sg9dJ5crUNtv9TQ1pog/IVpifVV/y 7wnYoaMatYFJpUjPnFCVf99OB25x4K2lJrgFE=
Received: by 10.231.195.40 with SMTP id ea40mr4735077ibb.167.1304179834125; Sat, 30 Apr 2011 09:10:34 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.172.14 with HTTP; Sat, 30 Apr 2011 09:10:14 -0700 (PDT)
In-Reply-To: <4DA875CA.4010505@bell-labs.com>
References: <4DA875CA.4010505@bell-labs.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sat, 30 Apr 2011 09:10:14 -0700
X-Google-Sender-Auth: VK9KDTVEPVdqOgeUCjkf3WI7Rkw
Message-ID: <BANLkTi=XHvOGB+P-GiKtpt=Q2NofpaeWaA@mail.gmail.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "p2prg@irtf.org" <p2prg@irtf.org>, alto <alto@ietf.org>
Subject: Re: [alto] ns-3/ALTO: Influencing suboptimal peer selection
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Apr 2011 16:10:36 -0000

Hi Vijay,

Very interesting results!  It does look like it converges to a good
result, but I'm wondering if it would be possible to reduce the
convergence time further (smaller than 10m). Can you give some more
details on how ALTO was integrated with the BitTorrent clients here?
Was it used for ranking peers returned from a tracker, or also
peer-exchange (if enabled)?  How often were new peers discovered from
a tracker or peer-exchange? Was it a greedy strategy in which only
closest peers were chosen, or were a few sub-optimal peers chosen for
robustness?

Thanks!
Rich

On Fri, Apr 15, 2011 at 9:43 AM, Vijay K. Gurbani <vkg@bell-labs.com> wrote=
:
> Folks: In the Prague p2prg, I had presented an ns-3 simulation
> of ALTO [1].
>
> The topology was simple (see slide 4 of [1]): an
> ISP (Chicago-ISP, PID 1), a peering link (ISP-Peering, PID 2),
> a transit link (ISP-Transit, PID 5), and a couple of links
> representing the rest of the Internet (Internet-1 and Internet-2,
> PIDs 3 and 4, respectively). =A0A cost map was provided in
> slide 5 of [1].
>
> A couple of simulations were shown, the first showed results
> of traffic transferred from the Chicago-ISP to rest of the
> network without ALTO, and the second simulation showed the
> resulting decrease in transit traffic and increase in peering
> and intra-ISP traffic when ALTO is used.
>
> I was running a third simulation, which is probably the most
> interesting one. =A0It did not complete by the time p2prg was held
> in Prague. =A0This simulation sheds some light on whether ALTO
> can influence the choice of suboptimal peer selection.
>
> One issue that has been talked about in ALTO is whether it can
> influence the choice of sub-optimal peers; in other words,
> can ALTO be used to purposely provide sub-optimal peers simply
> because a peering relationship exists and the peers in the
> peering network are sub-optimal (i.e., they may have less upload
> bandwidth when compared to other peers).
>
> The third simulation shows that this is not the case, and other
> publications [2] have experimentally demonstrated that this
> is not the case for BitTorrent at least. =A0BitTorrent exhibits
> strong clustering behaviour, where similar-bandwidth peers
> cluster together to ensure effective sharing incentives by
> rewarding peers who contribute proportionally more to the
> system.
>
> To run the third simulation, I kept the cost map invariant.
> However, I downgraded the data rate of the ISP-Peering
> peers. =A0So, compared to the rest of the peers, the ISP-Peering
> peers offer upload at a much reduced rate. =A0The expectation is
> that over time, the peers in ISP-Chicago will stop preferring
> peers in ISP-Peering, even though the cost to reach those peers
> is minimal. =A0And, the peers in ISP-Chicago would start
> preferring intra-ISP peers (i.e., other peers from ISP-Chicago),
> and even peers from ISP-Transit.
>
> This appears to indeed be the case, and the result is shown in
> the attached PDF. =A0Here is a summary table; in the table below,
> "Simulation 2" is the third simulation:
>
> =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0Simulation 1 =A0 =A0 =A0 =A0 | =A0 =
=A0 =A0Simulation 2
> Traffic =A0 =A0 | (all peers have similar =A0 | (peers in ISP-Peering
> destined to | =A0 =A0 =A0 data rates) =A0 =A0 =A0 =A0 | =A0have lower dat=
a rates)
> ------------+---------------------------+-----------------------------
> ISP-Chicago | 1.78 GB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 1.97 GB =
=A0(+ ~11%)
> ISP-Transit | 1.84 GB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 2.14 GB =
=A0(+ ~16%)
> ISP-Peering | 2.26 GB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | 606.97 MB =A0=
(- ~3.7x)
> Internet-1 =A0| 2.03 GB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 2.38 GB=
 =A0(+ ~15%)
> Internet-2 =A0| 2.12 GB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 2.35 GB=
 =A0(+ ~12%)
>
> [1] http://www.ietf.org/proceedings/80/slides/P2PRG-5.pdf
> [2] "Clustering and sharing incentives in BitTorrent systems",
> =A0Arnaud Legout, Nikitas Liogkas, Eddie Kohler and Lixia Zhang,
> =A0ACM Sigmetrics, June 2007.
>
> I thought some of you may find this interesting.
>
> Thanks,
>
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: =A0 http://ect.bell-labs.com/who/vkg/
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>
