Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id DDC44C14F5EE;
	Thu, 20 Jun 2024 10:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.524
X-Spam-Level: 
X-Spam-Status: No, score=0.524 tagged_above=-999 required=5
	tests=[BAYES_00=-1.9, DKIM_ADSP_DISCARD=1.8, DKIM_INVALID=0.1,
	DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399,
	RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_KAM_HTML_FONT_INVALID=0.01,
	T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01,
	T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001,
	URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001]
	autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key)
	reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194])
	by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UQwu6JV98E1z; Thu, 20 Jun 2024 10:10:32 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest
 SHA256)
	(No client certificate requested)
	by ietfa.amsl.com (Postfix) with ESMTPS id CED4DC1840CE;
	Thu, 20 Jun 2024 10:10:32 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51])
	(authenticated bits=0)
	by nostrum.com (8.18.1/8.18.1) with ESMTPSA id 45KH5oag042039
	(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO);
	Thu, 20 Jun 2024 12:05:51 -0500 (CDT)
	(envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com;
	s=default; t=1718903151;
	bh=FaBWZyOXeL1GmoAF3izQNIOEoQEZVAlGWtDyqV05OnY=;
	h=Date:Subject:From:To:Reply-To:References:In-Reply-To;
	b=q7m4iZHGe7TlT74vqC55ZTR5I6ETEDZt3U51WaIukZeBAyxIU+8dTdNm9qvv9hV3z
	 bIaojI+8cr5mEcBTjHkGbNYQXp5tCpVt26onmFGh9V1VwmmcLFT4WGm/evh4wNKezm
	 JITcLv7B/QTZ2RvfSw89okDsmL3W65ixO8kO6emo=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be
 [192.168.1.102]
Content-Type: multipart/alternative;
 boundary="------------TK95gBgbs0nVj7d225U0hSIT"
Message-ID: <c324e990-4114-4dee-b922-c12cfd081baf@nostrum.com>
Date: Thu, 20 Jun 2024 12:05:45 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Robert Sparks <rjsparks@nostrum.com>
To: Working Chairs <wgchairs@ietf.org>, "irsg@irtf.org" <irsg@irtf.org>,
        tools-discuss <tools-discuss@ietf.org>
References: <cf00c2ea-c9cd-43ca-93d3-bd3f5bd6fb92@nostrum.com>
 <48d4e9eb-fd0e-4f97-9873-d6b616347533@nostrum.com>
Content-Language: en-US
Autocrypt: addr=rjsparks@nostrum.com; keydata=
 xsDNBFx4PQwBDADIIJqFKIeYNmVR3iH8YnNqwApV+ci83VqFaPg0UXZAZ1utH/2O2LOLJKmV
 Ol11+lOSfH4OJgpARt37PWbqfG2TzzGfEucRBPMAV8TEDmzKL+7/OUMLEoPeexgxz6ADxK2Q
 ACKKzHhF30y4fx2fn9rYZrCvYHV9HDKcfFotNLna0U6P6wu70L0mT2hcjQgZ7+8HSZCpK2XG
 PTya1mEiMklH6+UHfcTLoAxd3chQiseRi19/TQZZCD3LuuaGFWyTIeF9ZNWV9yL0HQeb/XMs
 tmZnObSSHSUbZwn5PR9Uf+3iW7jdG5JuXBvNbDpAHfLyPXRqxErM/nCLrbwGB6AgNSKFCwkL
 lb3uxsGFWcOt6sedrjixoVUO2k4zQWVnCUCwFHGrgIxUK24dI8oqydGPctXAKj5VqoCVJBv6
 4JxSpiR+V8fl3A8gksBUnuIMLNlRjB5RAgZaSUpaOkXsWUBA8Z75wQWoIzkJIeMm29w2l1kB
 B9kGMdyiXGr2JV8VQZ4lAscAEQEAAc0kUm9iZXJ0IFNwYXJrcyA8cmpzcGFya3NAbm9zdHJ1
 bS5jb20+wsEUBBMBCAA+FiEEGNywdGDCHUYBwWN3bipqV3X5ExgFAmXhDnYCGwMFCQ0rmNQF
 CwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQbipqV3X5ExiEpwwAknrYjNHDI2l50IC1lpQB
 SnmCLvuu4pEESpRaBx1Te7vZBHr740dMbKQv/ZYYekw/NfFfoq2Ptguz5BXHwtyx3hKKjBUA
 U/rP62bl+x77yTJ0+I5k2hJ1p1DWNqXHWK3SEM0IUvjWpMGlfXPu7iVYCBGPKBDglQ4GWpzU
 HmSAX/8Zww6+ZbrXM0VgA+hLSHivyHextX4mJwoLRcuY99ecvkdWwFnKoDlEsKozdv9NW+QT
 h1rFvAtXf2ZCGwIveAMJPbHbRY3uFVp+oMvBbP7m5teffB8Ki5kuO1Y1Wqd9UPhiVDZmUuyC
 PXymQErskbOB6DcNSSFH7ZHuLM4V+zyziYWTT6foBv0ynA+a3Ofxo+rKPVHLybZlO9bQcI0Q
 TIE8yT0oqd3kWMaMIyrKZURVUpzcDgRnx6ujckLLyAC1H8L0tuntPwZOo5PAq3P7SUiWlc0L
 5HbA0L//BE6eeWn6U3xOgaJNF2+YRVICNtWpXcR3Mr4k1uXW4JkE7lyoufbnzsDNBFx4PQwB
 DAC03e1kk41e9Z9FuVW8UKWIkVUBeH3gfJMsb94d/c0cqBMRw5rulSY7+U76rw4AXo792LZn
 ydjDfoL0GQxGqkrZh397Sn9P/sLCb5I+wC14251nkmh5tmU2sQqCk+g9nykcE/NJft/zFkeb
 HHCKAosK6glO+W0YPHc/k7nXt/fLz7dMRpFpmqFXWjeN2VtwKr9znMg9+iX6XfgAJPMdDNH8
 fn30Cp5TIsn5WCI70+JztgvfjFhD15Eb3rtDdOfOydjGCV2ZVxfM8ECmc8Z3DrThyiC2M3uo
 2Y50rs6MH+TmVCtpHkISnH7B+80Vy2SC60K9l2xgCaezN1SlkQy3ZpprzcDrNTI8FcJa/UUM
 ayMGvSDGEGuHZRaNUyXP3jQ8oss+067axmNr5vgjpf01kmE1RJtiGEDWmCr8u1SbVQjdax6C
 pDqq3RKoX2ZVGLtkdDYZbsqSq4TgmFukoijWRbLxsFBdeEgruTViWRw4PKZav0piLxrhHUGI
 m6F6JFngapUAEQEAAcLA/AQYAQgAJhYhBBjcsHRgwh1GAcFjd24qald1+RMYBQJl4Q52AhsM
 BQkNK5jUAAoJEG4qald1+RMYaCML/jp+3W9OedMRVk5XQ3Urxu7g09qaeAfBAArLlE7F13Xt
 WuGUN7JwZ8hZt8Rsx1+Uz/Zq2TIPjl8PmgIqCSkuvZrxacr+drYARtO00Af71qHVoh4gZTae
 iOwEuOGhhtCVI3vvKLMDv1ex0scvD4rJTsIk/zqEDCJNDVOf09Szj0CW0vJOYxrIV0sG/UoM
 7Ui5/eB4tlN5AFIXuTJzo6BzaUAJVut74Ss2i93qwtwjGw44iEqPVhqKMCDYuB9+bm13ft+H
 Vr7viRZobd+60NTWrfZhkpmzhb4Qiib9qXhrUoa2EXqVOIy+LMQoiwjF9/iK+5FSA18c52FP
 ODkDgkica826W9AnBasS6gXQr0bO1BCJu84Fp2RQcjB4IFP+sKVoN3EZTByyUKK4NnSLF3lJ
 /G+vQhisnuJS+e+emZ8UxZBOK8upAhrhHJj0Wju2W0uTQTxlBME0/uNsvA/KaudLNhlQiUYN
 7Fl3rswvQk/iD+utnQdWJbRgIsqesNXbQCOimQ==
In-Reply-To: <48d4e9eb-fd0e-4f97-9873-d6b616347533@nostrum.com>
Message-ID-Hash: 5RU5JAS3I35X7KSCZHDVFI7WJK7PICA6
X-Message-ID-Hash: 5RU5JAS3I35X7KSCZHDVFI7WJK7PICA6
X-MailFrom: rjsparks@nostrum.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation;
 header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia;
 implicit-dest; max-recipients; max-size; news-moderation; no-subject;
 digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Reply-To: tools-discuss <tools-discuss@ietf.org>
Subject: =?utf-8?q?=5BTools-discuss=5D_Final_Reminder=3A_Key_IETF_service_outages_dur?=
 =?utf-8?q?ing_transition_to_new_infrastructure_on_20_June?=
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/tools-discuss/iYlKsSTjFhgzN0jasUuHZGknniU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

This is a multi-part message in MIME format.
--------------TK95gBgbs0nVj7d225U0hSIT
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

We are on track to make these changes and will begin at the scheduled 
time below. Another message will be sent when we are finished.

On 6/19/24 11:51 AM, Robert Sparks wrote:
>
> Reminder of the planned outage.
>
> On 6/12/24 10:03 AM, Robert Sparks wrote:
>>
>> As part of moving to a new cloud infrastructure, the IETF Datatracker 
>> and related services will be unavailable starting at 1800 UTC on 
>> Thursday 20 June. The outages are expected to last no more than 4 
>> hours; updates will be posted when availability resumes.
>>
>>
>> The following services will transition to the new cloud infrastructure:
>>
>>
>>    • the IETF Datatracker,
>>
>>    • the www.ietf.org website,
>>
>>    • the IETF Mailarchive, and
>>
>>    • the IMAP and rsync services.
>>
>>
>> IMPORTANT: Please do not plan to rely on the IETF Datatracker or the 
>> affected systems during the 4-hour window starting at 1800 UTC on 
>> Thursday 20 June.
>>
>>
>> Any service that relies on IETF Datatracker also will be affected. 
>> The following services will not be available:
>>
>>
>>    • the IETF meeting registration system, and
>>
>>    • any interim meeting sessions that use MeetEcho integrated with 
>> the IETF Datatracker.
>>
>>
>> The following services will be impaired, with any features requiring 
>> logging in unavailable:
>>
>>
>>    • the IETF Notes service (editing notes will not be possible)
>>
>>    • IETF wikis, including wiki.ietf.org and chairs.ietf.org (editing 
>> wiki pages will not be possible)
>>
>>    • The IETF Zulip service (any new connection will not work)
>>
>>
>> OF PARTICULAR NOTE: Posting Internet-Drafts (I-Ds) to the IETF 
>> repository will be unavailable during the outage; this includes 
>> automated posting of I-Ds via the IETF Datatracker API, such as via 
>> Github actions in repositories used to develop I-Ds.
>>
>>
>> Please see this blog post for more details:
>>
>>
>> https://www.ietf.org/blog/it-infrastructure-outage-2024-06-20/ 
>> <https://www.ietf.org/blog/it-infrastructure-outage-2024-06-20/>
>>
>>
>> The blog post will be updated once this phase of the IT 
>> infrastructure transition is complete.
>>
>>
>> RjS
>>
>>
>> IETF Tools Project Manager
>>
--------------TK95gBgbs0nVj7d225U0hSIT
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>We are on track to make these changes and will begin at the
      scheduled time below. Another message will be sent when we are
      finished.</p>
    <div class="moz-cite-prefix">On 6/19/24 11:51 AM, Robert Sparks
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:48d4e9eb-fd0e-4f97-9873-d6b616347533@nostrum.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p>Reminder of the planned outage.<br>
      </p>
      <div class="moz-cite-prefix">On 6/12/24 10:03 AM, Robert Sparks
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:cf00c2ea-c9cd-43ca-93d3-bd3f5bd6fb92@nostrum.com">
        <meta http-equiv="content-type"
          content="text/html; charset=UTF-8">
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
          id="docs-internal-guid-43f1d6c6-7fff-adfc-009d-587fb59e676e"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">As part of moving to a new cloud infrastructure, the IETF Datatracker and related services will be unavailable starting at 1800 UTC on Thursday 20 June. The outages are expected to last no more than 4 hours; updates will be posted when availability resumes.</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">The following services will transition to the new cloud infrastructure:</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • the IETF Datatracker, </span></p>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • the <a
          class="moz-txt-link-abbreviated" href="http://www.ietf.org"
          moz-do-not-send="true">www.ietf.org</a> website,</span></p>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • the IETF Mailarchive, and</span></p>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • the IMAP and rsync services.</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">IMPORTANT: Please do not plan to rely on the IETF Datatracker or the affected systems during the 4-hour window starting at 1800 UTC on Thursday 20 June.</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Any service that relies on IETF Datatracker also will be affected. The following services will not be available:</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • the IETF meeting registration system, and</span></p>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • any interim meeting sessions that use MeetEcho integrated with the IETF Datatracker.</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">The following services will be impaired, with any features requiring logging in unavailable:</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • the IETF Notes service (editing notes will not be possible)</span></p>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • IETF wikis, including wiki.ietf.org and chairs.ietf.org (editing wiki pages will not be possible)</span></p>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">   • The IETF Zulip service (any new connection will not work)</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">OF PARTICULAR NOTE: Posting Internet-Drafts (I-Ds) to the IETF repository will be unavailable during the outage; this includes automated posting of I-Ds via the IETF Datatracker API, such as via Github actions in repositories used to develop I-Ds.</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Please see this blog post for more details:</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><a
href="https://www.ietf.org/blog/it-infrastructure-outage-2024-06-20/"
            style="text-decoration:none;" moz-do-not-send="true"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;-webkit-text-decoration-skip:none;text-decoration-skip-ink:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">https://www.ietf.org/blog/it-infrastructure-outage-2024-06-20/</span></a><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;"> </span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">The blog post will be updated once this phase of the IT infrastructure transition is complete.</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Inter,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">RjS</span></p>
        <br>
        <p dir="ltr"
          style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:12pt;font-family:Inter,sans-serif;color:#333741;background-color:#ffffff;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">IETF Tools Project Manager</span></p>
      </blockquote>
    </blockquote>
  </body>
</html>

--------------TK95gBgbs0nVj7d225U0hSIT--

