From agentx-bounces@ietf.org Fri Feb 17 15:02:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FABoS-0002qY-II; Fri, 17 Feb 2006 15:02:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FABoQ-0002pQ-IK; Fri, 17 Feb 2006 15:02:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29598;
	Fri, 17 Feb 2006 15:00:54 -0500 (EST)
Received: from pop-knobcone.atl.sa.earthlink.net ([207.69.195.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FAC2r-0005kn-5g; Fri, 17 Feb 2006 15:17:41 -0500
Received: from h-64-105-34-171.snvacaid.dynamic.covad.net ([64.105.34.171]
	helo=oemcomputer)
	by pop-knobcone.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1FABoL-0007ZB-00; Fri, 17 Feb 2006 15:02:37 -0500
Message-ID: <001201c633fd$4a910bc0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <agentx@ietf.org>, "Disman" <disman@ietf.org>,
	"LTRU Working Group" <ltru@ietf.org>
Date: Fri, 17 Feb 2006 12:03:58 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Agentx] Fw: IETF Server Migration  Part 2. 
X-BeenThere: agentx@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SNMP Agent Extensibility <agentx.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/agentx>,
	<mailto:agentx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/agentx>
List-Post: <mailto:agentx@ietf.org>
List-Help: <mailto:agentx-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/agentx>,
	<mailto:agentx-request@ietf.org?subject=subscribe>
Sender: agentx-bounces@ietf.org
Errors-To: agentx-bounces@ietf.org

Hi -

This is relevant to the operation of all three of these mailing lists.

Randy, list admin

----- Original Message ----- 
> From: "IETF Secretariat" <ietf-secretariat@ietf.org>
> To: "IETF Announcement list" <ietf-announce@ietf.org>
> Sent: Friday, February 17, 2006 5:52 AM
> Subject: IETF Server Migration Part 2. 
>
> Hi All,
> 
> NeuStar Secretariat Services will be migrating the IETF to new servers in
> accordance with the schedule below.  All work will be done on the weekends to
> minimize disruptions, but there are periods when services will be down.
> 
> As the second part of the IETF server migration, we will be installing new
> mailman servers over this weekend.  
> 
> We believe we are prepared for this move, but, as with all migrations of this
> size and complexity, there may be some glitches.  If you experience any
> difficulties over this period, or notice anything amiss with the mailing lists,
> then please send email to ietf-action@ietf.org and copy the IAD at iad@ietf.org.
>   In case of an emergency, please call the emergency
> number: +1 301-858-6268.
> 
> Migration Schedule with expected down times:
> 
> Feb 18:
>    a. Mailing List Services (www1.ietf.org)
>       - Down Time: 7:00 AM ET.
>       - Up Time: It could be as early as 03:00 PM ET. and as late as 
>                  7:00 AM ET., the next day depending on DNS propagation  
>                  latency. See note below.
>    b. Request Tracker Services (ticket.ietf.org)
>       - Down Time: 7:00 AM ET.
>       - Up Time: It could be as early as 03:00 PM ET. and as late as 
>                  7:00 AM ET., the next day depending on DNS propagation  
>                  latency. See note below.
> 
>       Please note that the down time for the RT system affects only those 
>       people who have accounts with the site.  One will stil be able to 
>       send a message to the Secretariat (ietf-action@ietf.org, etc).  
>       Messages will be hold up in the IETF mail server and released when 
>       the RT system is back in service.
> 
> If it becomes necessary to change these plans, then we will send a second
> message to the list with the updated schedule. 
> 
> Thanks.
> 
> IETF Secretariat.
> 
> Note: Most of the name servers will be updated and bring the services from our
> new servers within couple of hours after migrations.  However, depends on their
> network environment, some names servers may be updated a little later than
> others.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce





