From exim@www1.ietf.org Mon Aug 4 08:58:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA24243 for ; Mon, 4 Aug 2003 08:58:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jeuc-0005Sf-HK for ieprep-archive@odin.ietf.org; Mon, 04 Aug 2003 08:58:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h74Cw6uK020992 for ieprep-archive@odin.ietf.org; Mon, 4 Aug 2003 08:58:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jeuc-0005SV-Aw for ieprep-web-archive@optimus.ietf.org; Mon, 04 Aug 2003 08:58:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA24233 for ; Mon, 4 Aug 2003 08:58:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19jeua-0000qD-00 for ieprep-web-archive@ietf.org; Mon, 04 Aug 2003 08:58:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19jeua-0000q9-00 for ieprep-web-archive@ietf.org; Mon, 04 Aug 2003 08:58:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jeuX-0005Ro-16; Mon, 04 Aug 2003 08:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jete-0005RM-2J for ieprep@optimus.ietf.org; Mon, 04 Aug 2003 08:57:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA24202 for ; Mon, 4 Aug 2003 08:57:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19jetc-0000pw-00 for ieprep@ietf.org; Mon, 04 Aug 2003 08:57:04 -0400 Received: from bells.cs.ucl.ac.uk ([128.16.5.31]) by ietf-mx with smtp (Exim 4.12) id 19jetb-0000ps-00 for ieprep@ietf.org; Mon, 04 Aug 2003 08:57:04 -0400 Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Mon, 4 Aug 2003 13:57:01 +0100 To: ieprep@ietf.org cc: Janet.Gunn@DynCorp.com Date: Mon, 04 Aug 2003 13:56:59 +0100 Message-ID: <1510.1060001819@cs.ucl.ac.uk> From: Ken Carlberg Subject: [Ieprep] Telephony Framework document and Megaco Priorities Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , > The Telephony Framework document says (about MEGACO): > > "The protocol does not specify individual values for priority. We > also do not recommend the definition of a well known value for the > MEGAGO priority. Any values set should be a function of any SLAs > that have been established regarding the handling of emergency > traffic. In addition, given that priority values denote precedence > (according to the Megaco protocol), then by default the ETS telephony > data flows should probably receive the same priority as other non- > emergency calls. This approach follows the objective of not relying > on preemption as the default treatment of emergency-related." > > But the Megaco document (3525) says > > "The priority is used for a Context in order to provide the MG with > information about a certain precedence handling for a Context." > > Nothing about preemption. > > Therefore it seems to me that "denoting precedence" is exactly what we > DO want to do in the ETS/TDR context. ok, i'll reword/cut-down the last two sentences of the original passage so as not to directly associate preemption with precedence. also using the term ETS may be a bit too general and encompassing in this particular case. -ken _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Mon Aug 11 16:51:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05791 for ; Mon, 11 Aug 2003 16:51:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mJdB-00041h-9x for ieprep-archive@odin.ietf.org; Mon, 11 Aug 2003 16:51:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BKp5PD015471 for ieprep-archive@odin.ietf.org; Mon, 11 Aug 2003 16:51:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mJdB-00041S-6C for ieprep-web-archive@optimus.ietf.org; Mon, 11 Aug 2003 16:51:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05782 for ; Mon, 11 Aug 2003 16:50:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mJd9-0002IJ-00 for ieprep-web-archive@ietf.org; Mon, 11 Aug 2003 16:51:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mJd8-0002IF-00 for ieprep-web-archive@ietf.org; Mon, 11 Aug 2003 16:51:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mJd6-00040j-PN; Mon, 11 Aug 2003 16:51:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mJcc-0003zs-0o for ieprep@optimus.ietf.org; Mon, 11 Aug 2003 16:50:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05768 for ; Mon, 11 Aug 2003 16:50:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mJca-0002Hx-00 for ieprep@ietf.org; Mon, 11 Aug 2003 16:50:28 -0400 Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu) by ietf-mx with esmtp (Exim 4.12) id 19mJcZ-0002Hu-00 for ieprep@ietf.org; Mon, 11 Aug 2003 16:50:27 -0400 Received: from newdev.harvard.edu (localhost [127.0.0.1]) by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h7BKoM9n012056 for ; Mon, 11 Aug 2003 16:50:22 -0400 (EDT) Received: (from sob@localhost) by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h7BKoMV0012055 for ieprep@ietf.org; Mon, 11 Aug 2003 16:50:22 -0400 (EDT) Date: Mon, 11 Aug 2003 16:50:22 -0400 (EDT) From: Scott Bradner Message-Id: <200308112050.h7BKoMV0012055@newdev.harvard.edu> To: ieprep@ietf.org Subject: [Ieprep] comments on draft-ietf-ieprep-ets-general-03 Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , fyi - the IESG discussed draft-ietf-ieprep-ets-general-03 last week and has some comments see https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=9799&rfc_flag=0 for the comments Scott _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Thu Aug 14 18:57:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00892 for ; Thu, 14 Aug 2003 18:57:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nR1l-0004id-C8 for ieprep-archive@odin.ietf.org; Thu, 14 Aug 2003 18:57:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7EMv5WD018135 for ieprep-archive@odin.ietf.org; Thu, 14 Aug 2003 18:57:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nR1l-0004iQ-8Y for ieprep-web-archive@optimus.ietf.org; Thu, 14 Aug 2003 18:57:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00888 for ; Thu, 14 Aug 2003 18:56:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nR1i-0006j8-00 for ieprep-web-archive@ietf.org; Thu, 14 Aug 2003 18:57:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19nR1h-0006j3-00 for ieprep-web-archive@ietf.org; Thu, 14 Aug 2003 18:57:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nR1h-0004ho-Nk; Thu, 14 Aug 2003 18:57:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nR1D-0004hW-LG for ieprep@optimus.ietf.org; Thu, 14 Aug 2003 18:56:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00881 for ; Thu, 14 Aug 2003 18:56:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nR1A-0006iv-00 for ieprep@ietf.org; Thu, 14 Aug 2003 18:56:28 -0400 Received: from tungsten.btinternet.com ([194.73.73.81]) by ietf-mx with esmtp (Exim 4.12) id 19nR19-0006is-00 for ieprep@ietf.org; Thu, 14 Aug 2003 18:56:27 -0400 Received: from host81-132-55-178.in-addr.btopenworld.com ([81.132.55.178] helo=alpha002) by tungsten.btinternet.com with esmtp (Exim 3.22 #23) id 19nR19-0006YF-00 for ieprep@ietf.org; Thu, 14 Aug 2003 23:56:28 +0100 Reply-To: From: "Lawrence Stromski" To: Date: Thu, 14 Aug 2003 23:56:25 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Content-Transfer-Encoding: 7bit Subject: [Ieprep] Power Outages - North East US 14/08 Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I'm based in the UK, I'm just watching the Internet and the News reports at 23:23 British Summer Time literally during the power outage that affected the North East of the US. I thought I'd just record a few notes with this mailing list, from a UK point of view. (I am hanging off the BT Global Network in the UK, bt.net.) It's very difficult to ascertain exactly what's down, and if it's a result of the power outages. So far, I have no connectivity on the ATDN, AOL Transit Data Network beyond their London router, pop1-loh-P5-2.atdn.net. This is preventing me from making a connection to the CNN Webserver, www.cnn.com. "America Online spokesman Nicholas Graham said the company, the largest U.S. Internet service, had witnessed a dip in simultaneous users at 1 p.m. EDT. The count fell from 2.4 million members online to 2.1 million." -CNet News. AOL seem to be a recurring theme in this power outage. Were they less prepared than any other company or network? No response on Global Crossings network past London. so3-2-0-622M.cr2.LON3.gblx.net. This is preventing communication with the Global Crossings web server too. No response from denver-br2.bbnplanet.net 4.0.0.118 past Washington DC, Level3. so-1-0-0.bbr1.Washington1.level3.net. Taking a quick look also at our company's What's Up Gold (we are privately connected across the globe through Global Crossings) nothing happened. All our sites remained up, including Elizabeth, Baltimore, Chicago Heights. I think because there are so many possible routes across the pond, and so much redundancy in North East US, a power outage like this will make a very small dent in the Internet. Looking at internettrafficreport.com, there is definitely a noticeable mark corresponding to the power outage. Packet Loss goes up, response times go up. I guess in the 21st century world, power outages don't necessarily mean network/internetwork outages any more. That's just my take on things. And just as I finish writing this up, www.cnn.com has recovered, and I can now connect. Links: http://news.com.com/2100-1011_3-5063997.html?tag=fd_top Regards, -Lawrence Stromski. _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Thu Aug 14 19:03:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01095 for ; Thu, 14 Aug 2003 19:03:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nR7X-0004sB-ER for ieprep-archive@odin.ietf.org; Thu, 14 Aug 2003 19:03:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7EN33Mc018724 for ieprep-archive@odin.ietf.org; Thu, 14 Aug 2003 19:03:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nR7X-0004rv-90 for ieprep-web-archive@optimus.ietf.org; Thu, 14 Aug 2003 19:03:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01048 for ; Thu, 14 Aug 2003 19:02:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nR7U-0006mi-00 for ieprep-web-archive@ietf.org; Thu, 14 Aug 2003 19:03:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19nR7T-0006me-00 for ieprep-web-archive@ietf.org; Thu, 14 Aug 2003 19:02:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nR7V-0004pQ-Jv; Thu, 14 Aug 2003 19:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nR6x-0004ok-17 for ieprep@optimus.ietf.org; Thu, 14 Aug 2003 19:02:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01033 for ; Thu, 14 Aug 2003 19:02:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nR6t-0006mK-00 for ieprep@ietf.org; Thu, 14 Aug 2003 19:02:23 -0400 Received: from kc-msxproto1.kc.umkc.edu ([134.193.143.167]) by ietf-mx with esmtp (Exim 4.12) id 19nR6t-0006mG-00 for ieprep@ietf.org; Thu, 14 Aug 2003 19:02:23 -0400 Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211]) by kc-msxproto1.kc.umkc.edu with Microsoft SMTPSVC(6.0.3790.0); Thu, 14 Aug 2003 18:02:18 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 14 Aug 2003 18:02:18 -0500 Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B01108067@KC-MAIL4.kc.umkc.edu> Thread-Topic: Internet failures Thread-Index: AcNiuBwEH69WCyCaTQqJGbYOI6li1w== From: "Ayyasamy, Senthilkumar \(UMKC-Student\)" To: X-OriginalArrivalTime: 14 Aug 2003 23:02:18.0463 (UTC) FILETIME=[1C4A1EF0:01C362B8] Content-Transfer-Encoding: quoted-printable Subject: [Ieprep] OT: Internet failures Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Remember how we talk about Internet (particularly "routing" failures): "We should all learn from the power system how to make Internet more=20 fault tolerant" Well... I can't recall any Internet failure that took out connectivity for several east-coast cities :-) _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Thu Aug 14 21:55:09 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04344 for ; Thu, 14 Aug 2003 21:55:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nTnf-000255-EV for ieprep-archive@odin.ietf.org; Thu, 14 Aug 2003 21:54:43 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7F1shG4007995 for ieprep-archive@odin.ietf.org; Thu, 14 Aug 2003 21:54:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nTnf-00024s-Bf for ieprep-web-archive@optimus.ietf.org; Thu, 14 Aug 2003 21:54:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04333 for ; Thu, 14 Aug 2003 21:54:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nTnc-0007YA-00 for ieprep-web-archive@ietf.org; Thu, 14 Aug 2003 21:54:40 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19nTnb-0007Y7-00 for ieprep-web-archive@ietf.org; Thu, 14 Aug 2003 21:54:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nTmy-00021z-VR; Thu, 14 Aug 2003 21:54:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nTml-00021l-EQ for ieprep@optimus.ietf.org; Thu, 14 Aug 2003 21:53:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04316 for ; Thu, 14 Aug 2003 21:53:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nTmi-0007Xt-00 for ieprep@ietf.org; Thu, 14 Aug 2003 21:53:44 -0400 Received: from mtahqs3.ncr.disa.mil ([164.117.144.157] helo=pfwhqs1.ncr.disa.mil) by ietf-mx with smtp (Exim 4.12) id 19nTmh-0007Xg-00 for ieprep@ietf.org; Thu, 14 Aug 2003 21:53:43 -0400 Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 15 Aug 2003 01:56:22 UT Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19) id ; Thu, 14 Aug 2003 21:53:10 -0400 Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D02EF4F9C@emshqs1.ncr.disa.mil> From: "Nguyen, An" To: "'Lawrence Stromski '" , "'ieprep@ietf.org '" Subject: RE: [Ieprep] Power Outages - North East US 14/08 Date: Thu, 14 Aug 2003 21:53:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Just a curiosity, I wonder how this power outage caused any problem for the PSTN. An -----Original Message----- From: Lawrence Stromski To: ieprep@ietf.org Sent: 8/14/03 6:56 PM Subject: [Ieprep] Power Outages - North East US 14/08 Hi, I'm based in the UK, I'm just watching the Internet and the News reports at 23:23 British Summer Time literally during the power outage that affected the North East of the US. I thought I'd just record a few notes with this mailing list, from a UK point of view. (I am hanging off the BT Global Network in the UK, bt.net.) It's very difficult to ascertain exactly what's down, and if it's a result of the power outages. So far, I have no connectivity on the ATDN, AOL Transit Data Network beyond their London router, pop1-loh-P5-2.atdn.net. This is preventing me from making a connection to the CNN Webserver, www.cnn.com. "America Online spokesman Nicholas Graham said the company, the largest U.S. Internet service, had witnessed a dip in simultaneous users at 1 p.m. EDT. The count fell from 2.4 million members online to 2.1 million." -CNet News. AOL seem to be a recurring theme in this power outage. Were they less prepared than any other company or network? No response on Global Crossings network past London. so3-2-0-622M.cr2.LON3.gblx.net. This is preventing communication with the Global Crossings web server too. No response from denver-br2.bbnplanet.net 4.0.0.118 past Washington DC, Level3. so-1-0-0.bbr1.Washington1.level3.net. Taking a quick look also at our company's What's Up Gold (we are privately connected across the globe through Global Crossings) nothing happened. All our sites remained up, including Elizabeth, Baltimore, Chicago Heights. I think because there are so many possible routes across the pond, and so much redundancy in North East US, a power outage like this will make a very small dent in the Internet. Looking at internettrafficreport.com, there is definitely a noticeable mark corresponding to the power outage. Packet Loss goes up, response times go up. I guess in the 21st century world, power outages don't necessarily mean network/internetwork outages any more. That's just my take on things. And just as I finish writing this up, www.cnn.com has recovered, and I can now connect. Links: http://news.com.com/2100-1011_3-5063997.html?tag=fd_top Regards, -Lawrence Stromski. _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Thu Aug 14 22:28:09 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04787 for ; Thu, 14 Aug 2003 22:28:09 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nUJc-0002qK-Kq for ieprep-archive@odin.ietf.org; Thu, 14 Aug 2003 22:27:44 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7F2RiU8010922 for ieprep-archive@odin.ietf.org; Thu, 14 Aug 2003 22:27:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nUJc-0002q5-ED for ieprep-web-archive@optimus.ietf.org; Thu, 14 Aug 2003 22:27:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04769 for ; Thu, 14 Aug 2003 22:27:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nUJZ-0007fC-00 for ieprep-web-archive@ietf.org; Thu, 14 Aug 2003 22:27:41 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19nUJY-0007f9-00 for ieprep-web-archive@ietf.org; Thu, 14 Aug 2003 22:27:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nUIv-0002nG-M5; Thu, 14 Aug 2003 22:27:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nUIY-0002n3-Kx for ieprep@optimus.ietf.org; Thu, 14 Aug 2003 22:26:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04755 for ; Thu, 14 Aug 2003 22:26:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nUIV-0007ej-00 for ieprep@ietf.org; Thu, 14 Aug 2003 22:26:35 -0400 Received: from host.paix.pch.net ([206.220.231.245] helo=paixhost.pch.net) by ietf-mx with esmtp (Exim 4.12) id 19nUIU-0007eg-00 for ieprep@ietf.org; Thu, 14 Aug 2003 22:26:34 -0400 Received: from ns1.pch.net (ns1.pch.net [206.220.231.1]) by paixhost.pch.net (8.11.6p2/8.11.6) with ESMTP id h7F2OoM14152; Thu, 14 Aug 2003 19:24:50 -0700 (PDT) Date: Thu, 14 Aug 2003 19:24:50 -0700 (PDT) From: Bill Woodcock To: "Nguyen, An" cc: "'Lawrence Stromski '" , "'ieprep@ietf.org '" Subject: RE: [Ieprep] Power Outages - North East US 14/08 In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D02EF4F9C@emshqs1.ncr.disa.mil> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , On Thu, 14 Aug 2003, Nguyen, An wrote: > Just a curiosity, I wonder how this power outage caused any problem for the > PSTN. Repeater huts without generators are starting to go offline, as their batteries run out. -Bill _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Fri Aug 15 11:06:04 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00045 for ; Fri, 15 Aug 2003 11:06:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ng95-0006wN-Jw for ieprep-archive@odin.ietf.org; Fri, 15 Aug 2003 11:05:39 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7FF5dCD026675 for ieprep-archive@odin.ietf.org; Fri, 15 Aug 2003 11:05:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ng95-0006wA-Ff for ieprep-web-archive@optimus.ietf.org; Fri, 15 Aug 2003 11:05:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29998 for ; Fri, 15 Aug 2003 11:05:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ng92-00033n-00 for ieprep-web-archive@ietf.org; Fri, 15 Aug 2003 11:05:36 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ng92-00033k-00 for ieprep-web-archive@ietf.org; Fri, 15 Aug 2003 11:05:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ng8S-0006rO-M1; Fri, 15 Aug 2003 11:05:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ng7k-0006nY-C3 for ieprep@optimus.ietf.org; Fri, 15 Aug 2003 11:04:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29952 for ; Fri, 15 Aug 2003 11:04:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ng7h-00032i-00 for ieprep@ietf.org; Fri, 15 Aug 2003 11:04:13 -0400 Received: from gnat.inet.org ([63.108.254.91]) by ietf-mx with esmtp (Exim 4.12) id 19ng7h-00032T-00 for ieprep@ietf.org; Fri, 15 Aug 2003 11:04:13 -0400 Received: from extremenetworks.com (unknown [10.18.3.103]) by gnat.inet.org (Postfix) with ESMTP id 85B8C67108 for ; Fri, 15 Aug 2003 11:37:15 -0400 (EDT) Date: Fri, 15 Aug 2003 11:03:55 -0400 Subject: Re: [Ieprep] Power Outages - US NE 14aug03 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: RJ Atkinson To: ieprep Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit http://news.bbc.co.uk/2/hi/technology/3153347.stm BBC News reports the Internet fared well: ------------------------------------------ The net has survived the US power outage largely unscathed. Firms monitoring the internet's core cables said the blackout had not slowed traffic or caused any significant delays. Experts said the net's structure helped it cope with the shutdown of networks in the affected areas. Some websites were briefly troubled by an increase in visitors looking for news about the power problems but they easily coped with the surge. ...more online at above URL... _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Fri Aug 15 12:08:09 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01793 for ; Fri, 15 Aug 2003 12:08:09 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nh79-0002Sq-D6 for ieprep-archive@odin.ietf.org; Fri, 15 Aug 2003 12:07:43 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7FG7hmL009466 for ieprep-archive@odin.ietf.org; Fri, 15 Aug 2003 12:07:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nh79-0002Sa-8g for ieprep-web-archive@optimus.ietf.org; Fri, 15 Aug 2003 12:07:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01779 for ; Fri, 15 Aug 2003 12:07:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nh77-0003Vz-00 for ieprep-web-archive@ietf.org; Fri, 15 Aug 2003 12:07:42 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19nh77-0003Vw-00 for ieprep-web-archive@ietf.org; Fri, 15 Aug 2003 12:07:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nh6S-0002Eu-Rd; Fri, 15 Aug 2003 12:07:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nh5p-0002DE-Qg for ieprep@optimus.ietf.org; Fri, 15 Aug 2003 12:06:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01732 for ; Fri, 15 Aug 2003 12:06:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nh5o-0003Vb-00 for ieprep@ietf.org; Fri, 15 Aug 2003 12:06:20 -0400 Received: from capella.nps.navy.mil ([131.120.254.83] helo=[140.32.132.66]) by ietf-mx with esmtp (Exim 4.12) id 19nh5n-0003VX-00 for ieprep@ietf.org; Fri, 15 Aug 2003 12:06:19 -0400 Received: from no.name.available by [140.32.132.66] via smtpd (for [132.151.6.1]) with ESMTP; Fri, 15 Aug 2003 09:02:53 -0700 Received: from ro179-31.ro.nps.navy.mil (ro179-31.ro.nps.navy.mil [131.120.179.31]) by capella.nps.navy.mil (8.12.9/8.12.9) with ESMTP id h7FG6BxK028751 for ; Fri, 15 Aug 2003 09:06:11 -0700 (PDT) Subject: [Fwd: Re: [Ieprep] Power Outages - US NE 14aug03] From: Rex Buddenberg To: ieprep@ietf.org Content-Type: text/plain Message-Id: <1060963218.3750.11.camel@ro179-31.ro.nps.navy.mil> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 15 Aug 2003 09:00:18 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Probably worth distinguishing between core and periphery. An ISP will consider the core to be it's core routers and the fiber between them plus the NOC. The periphery would include residential installations (cable modems and LAN/computers attached. In between there's room for some haggling about what's core or not -- cable head end? All ISPs of any scale that I've seen have backup power -- usually a generator out back -- for the NOC. Ditto for the core routers. That leaves the line huts that Woody mentioned last night. If they're backed up, the the core is likely to stay up. At least until the diesels run out of fuel. Having the core up doesn't mean the ISP has any customers though. If my ISP has its head end backed up (likely), then is the local fanout backed at the nodes? And finally, can I keep things up at the house? I have a cable modem, a local router and hub and the end systems that are attached. Alas, only the laptop has backup power. The router and cable modem don't require much amperage but if we're going to build robust systems those things need some kind of backup. On Fri, 2003-08-15 at 08:03, RJ Atkinson wrote: > http://news.bbc.co.uk/2/hi/technology/3153347.stm > > > BBC News reports the Internet fared well: > ------------------------------------------ > The net has survived the US power outage largely unscathed. > > Firms monitoring the internet's core cables said the blackout had not > slowed traffic or caused any significant delays. > > Experts said the net's structure helped it cope with the shutdown of > networks in the affected areas. > > Some websites were briefly troubled by an increase in visitors looking > for news about the power problems but they easily coped with the surge. > > ...more online at above URL... > > > _______________________________________________ > Ieprep mailing list > Ieprep@ietf.org > https://www1.ietf.org/mailman/listinfo/ieprep -- b _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Fri Aug 15 12:30:10 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02462 for ; Fri, 15 Aug 2003 12:30:10 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nhST-0003ei-4q for ieprep-archive@odin.ietf.org; Fri, 15 Aug 2003 12:29:45 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7FGTjC0014046 for ieprep-archive@odin.ietf.org; Fri, 15 Aug 2003 12:29:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nhSS-0003eT-UF for ieprep-web-archive@optimus.ietf.org; Fri, 15 Aug 2003 12:29:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02454 for ; Fri, 15 Aug 2003 12:29:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nhSR-0003gW-00 for ieprep-web-archive@ietf.org; Fri, 15 Aug 2003 12:29:43 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19nhSQ-0003gT-00 for ieprep-web-archive@ietf.org; Fri, 15 Aug 2003 12:29:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nhRk-0003bh-JQ; Fri, 15 Aug 2003 12:29:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nhRU-0003bU-Nv for ieprep@optimus.ietf.org; Fri, 15 Aug 2003 12:28:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02441 for ; Fri, 15 Aug 2003 12:28:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nhRT-0003gL-00 for ieprep@ietf.org; Fri, 15 Aug 2003 12:28:43 -0400 Received: from gnat.inet.org ([63.108.254.91]) by ietf-mx with esmtp (Exim 4.12) id 19nhRS-0003gI-00 for ieprep@ietf.org; Fri, 15 Aug 2003 12:28:42 -0400 Received: from extremenetworks.com (unknown [10.18.3.103]) by gnat.inet.org (Postfix) with ESMTP id 1B1D367105; Fri, 15 Aug 2003 13:02:02 -0400 (EDT) Date: Fri, 15 Aug 2003 12:28:41 -0400 Subject: Re: [Fwd: Re: [Ieprep] Power Outages - US NE 14aug03] Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: ieprep@ietf.org To: Rex Buddenberg From: RJ Atkinson In-Reply-To: <1060963218.3750.11.camel@ro179-31.ro.nps.navy.mil> Message-Id: <883CD670-CF3D-11D7-A2D7-00039357A82A@extremenetworks.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Friday, Aug 15, 2003, at 12:00 America/Montreal, Rex Buddenberg wrote: > In between there's room for some haggling about what's core or not -- > cable head end? At least in the case of Cox Cable (US), their headends are built out to the same standards as a Class-5 telephone switching station -- with big battery banks and an on-site backup generator. In fact, there is normally a class-5 PSTN switch as part of their installation, since in most markets they are a CLEC offering residential PSTN (not over VoIP, but PSTN directly over HFC). Generally speaking, if there are active amps/lasers between the head-end and the customer, lack of power to those amps/lasers would mean that folks downstream of the amp/laser would be unlikely to remain connected. Not all HFC deployments in the US include active components downstream from the headend. Ran _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Fri Aug 15 16:16:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11887 for ; Fri, 15 Aug 2003 16:16:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nkzX-0000DZ-N3 for ieprep-archive@odin.ietf.org; Fri, 15 Aug 2003 16:16:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7FKG7td000831 for ieprep-archive@odin.ietf.org; Fri, 15 Aug 2003 16:16:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nkzX-0000DK-Iu for ieprep-web-archive@optimus.ietf.org; Fri, 15 Aug 2003 16:16:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11872 for ; Fri, 15 Aug 2003 16:16:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nkzV-0005ft-00 for ieprep-web-archive@ietf.org; Fri, 15 Aug 2003 16:16:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19nkzV-0005fq-00 for ieprep-web-archive@ietf.org; Fri, 15 Aug 2003 16:16:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nkzS-0000AV-6w; Fri, 15 Aug 2003 16:16:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nkye-00009v-OG for ieprep@optimus.ietf.org; Fri, 15 Aug 2003 16:15:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11865 for ; Fri, 15 Aug 2003 16:15:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nkyd-0005fk-00 for ieprep@ietf.org; Fri, 15 Aug 2003 16:15:11 -0400 Received: from kc-msxproto1.kc.umkc.edu ([134.193.143.167]) by ietf-mx with esmtp (Exim 4.12) id 19nkyc-0005fh-00 for ieprep@ietf.org; Fri, 15 Aug 2003 16:15:10 -0400 Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211]) by kc-msxproto1.kc.umkc.edu with Microsoft SMTPSVC(6.0.3790.0); Fri, 15 Aug 2003 15:15:11 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Fwd: Re: [Ieprep] Power Outages - US NE 14aug03] Date: Fri, 15 Aug 2003 15:15:09 -0500 Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B01108069@KC-MAIL4.kc.umkc.edu> Thread-Topic: [Fwd: Re: [Ieprep] Power Outages - US NE 14aug03] Thread-Index: AcNjR0N/w8s7PsjrTy2TjSzP2MRYlgAIR+if From: "Ayyasamy, Senthilkumar \(UMKC-Student\)" To: "Rex Buddenberg" , X-OriginalArrivalTime: 15 Aug 2003 20:15:11.0275 (UTC) FILETIME=[EE0867B0:01C36369] Content-Transfer-Encoding: quoted-printable Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable btw, the so-called Internet failures under discussion ( web/mail server down, failures due to the BLAST worm) are _not_ network failures; they are failure of the system attached to the network. It is the job of an application service provider to make his/one's client system more redundant and robust. network worked fine by=20 way of spreading the worm. _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Sun Aug 17 22:34:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26352 for ; Sun, 17 Aug 2003 22:34:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19oZqP-0002ds-VE for ieprep-archive@odin.ietf.org; Sun, 17 Aug 2003 22:34:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7I2Y5mp010150 for ieprep-archive@odin.ietf.org; Sun, 17 Aug 2003 22:34:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19oZqP-0002dd-Qx for ieprep-web-archive@optimus.ietf.org; Sun, 17 Aug 2003 22:34:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26347 for ; Sun, 17 Aug 2003 22:33:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19oZqM-0004DR-00 for ieprep-web-archive@ietf.org; Sun, 17 Aug 2003 22:34:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19oZqL-0004DN-00 for ieprep-web-archive@ietf.org; Sun, 17 Aug 2003 22:34:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19oZqK-0002cw-Nf; Sun, 17 Aug 2003 22:34:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19oZpe-0002bC-31 for ieprep@optimus.ietf.org; Sun, 17 Aug 2003 22:33:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26341 for ; Sun, 17 Aug 2003 22:33:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19oZpa-0004DK-00 for ieprep@ietf.org; Sun, 17 Aug 2003 22:33:14 -0400 Received: from sj-core-4.cisco.com ([171.68.223.138]) by ietf-mx with esmtp (Exim 4.12) id 19oZpa-0004DF-00 for ieprep@ietf.org; Sun, 17 Aug 2003 22:33:14 -0400 Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h7I2Wgpp007984; Sun, 17 Aug 2003 19:32:42 -0700 (PDT) Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id TAA13418; Sun, 17 Aug 2003 19:32:41 -0700 (PDT) Message-Id: <4.3.2.7.2.20030817212612.021f0918@localhost> X-Sender: jmpolk@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 17 Aug 2003 21:32:53 -0500 To: Rex Buddenberg , ieprep@ietf.org From: "James M. Polk" Subject: Re: [Fwd: Re: [Ieprep] Power Outages - US NE 14aug03] In-Reply-To: <1060963218.3750.11.camel@ro179-31.ro.nps.navy.mil> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , At 09:00 AM 8/15/2003 -0700, Rex Buddenberg wrote: > Having the core up doesn't mean the ISP has any customers though. If >my ISP has its head end backed up (likely), then is the local fanout >backed at the nodes? And finally, can I keep things up at the house? I >have a cable modem, a local router and hub and the end systems that are >attached. Alas, only the laptop has backup power. The router and cable >modem don't require much amperage but if we're going to build robust >systems those things need some kind of backup. That's why I've invested so much in APC (I have 9 UPSs throughout the house). They last between 15 minutes and 12 hours, depending on what they're attached to -- and can take on Texas-sized lightning storms ;-) cheers, James ******************* The answer is "42", what's the question? _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Mon Aug 18 11:18:38 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22602 for ; Mon, 18 Aug 2003 11:18:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ollp-00012t-7n for ieprep-archive@odin.ietf.org; Mon, 18 Aug 2003 11:18:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7IFI9Mi004018 for ieprep-archive@odin.ietf.org; Mon, 18 Aug 2003 11:18:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ollp-00012j-3Y for ieprep-web-archive@optimus.ietf.org; Mon, 18 Aug 2003 11:18:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22557 for ; Mon, 18 Aug 2003 11:18:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ollo-0007kj-00 for ieprep-web-archive@ietf.org; Mon, 18 Aug 2003 11:18:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19olln-0007kg-00 for ieprep-web-archive@ietf.org; Mon, 18 Aug 2003 11:18:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ollh-0000yW-Eq; Mon, 18 Aug 2003 11:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19olkv-0000sq-Eh for ieprep@optimus.ietf.org; Mon, 18 Aug 2003 11:17:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22493 for ; Mon, 18 Aug 2003 11:17:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19olku-0007im-00 for ieprep@ietf.org; Mon, 18 Aug 2003 11:17:12 -0400 Received: from capella.nps.navy.mil ([131.120.254.83] helo=[140.32.132.66]) by ietf-mx with esmtp (Exim 4.12) id 19olkt-0007ij-00 for ieprep@ietf.org; Mon, 18 Aug 2003 11:17:11 -0400 Received: from no.name.available by [140.32.132.66] via smtpd (for [132.151.6.1]) with ESMTP; Mon, 18 Aug 2003 08:13:35 -0700 Received: from ro178-30.ro.nps.navy.mil (ro178-30.ro.nps.navy.mil [131.120.178.30]) by capella.nps.navy.mil (8.12.9/8.12.9) with ESMTP id h7IFGpxK014707; Mon, 18 Aug 2003 08:16:51 -0700 (PDT) Subject: Re: [Fwd: Re: [Ieprep] Power Outages - US NE 14aug03] From: Rex Buddenberg To: "James M. Polk" Cc: ieprep@ietf.org In-Reply-To: <4.3.2.7.2.20030817212612.021f0918@localhost> References: <4.3.2.7.2.20030817212612.021f0918@localhost> Content-Type: text/plain Message-Id: <1061183472.3755.23.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 18 Aug 2003 08:10:37 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit > ******************* > The answer is "42", what's the question? But only in Hitchikers Guide. The answer is 8 days. The question was how long was USS Cole without power. Yes, I have a lab full of UPSs too. Small routers and hubs are in the same league as laptops -- 50-100 watts. I think the technology to look at for emergency services and distributed power is fuel cells. Unfortunately, the commercial industry hasn't yet found the right configuration: - drive your car. Too big for our needs. - drive your cellphone. Too small. - drive your laptop -- probably about right. We've been plumbing the vendors for something in a 19" rack configuration that'd drive a router for a few days. Fuel cells of this ilk come with a UPS to bridge the gap from when the lights go out and when the cell gets up to speed. >From there on, endurance is limited by the size of the hydrogen bottle. This technology looks promising but is pretty juvenile as yet. On Sun, 2003-08-17 at 19:32, James M. Polk wrote: > At 09:00 AM 8/15/2003 -0700, Rex Buddenberg wrote: > > > Having the core up doesn't mean the ISP has any customers though. If > >my ISP has its head end backed up (likely), then is the local fanout > >backed at the nodes? And finally, can I keep things up at the house? I > >have a cable modem, a local router and hub and the end systems that are > >attached. Alas, only the laptop has backup power. The router and cable > >modem don't require much amperage but if we're going to build robust > >systems those things need some kind of backup. > > That's why I've invested so much in APC (I have 9 UPSs throughout the > house). They last between 15 minutes and 12 hours, depending on what > they're attached to -- and can take on Texas-sized lightning storms ;-) > > > > > cheers, > James -- b _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Tue Aug 19 09:53:43 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10622 for ; Tue, 19 Aug 2003 09:53:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19p6vG-0005ja-0r for ieprep-archive@odin.ietf.org; Tue, 19 Aug 2003 09:53:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7JDrH2n022042 for ieprep-archive@odin.ietf.org; Tue, 19 Aug 2003 09:53:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19p6vF-0005jR-U0 for ieprep-web-archive@optimus.ietf.org; Tue, 19 Aug 2003 09:53:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10614 for ; Tue, 19 Aug 2003 09:53:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19p6vD-0000OY-00 for ieprep-web-archive@ietf.org; Tue, 19 Aug 2003 09:53:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19p6vD-0000OU-00 for ieprep-web-archive@ietf.org; Tue, 19 Aug 2003 09:53:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19p6uz-0005ii-DV; Tue, 19 Aug 2003 09:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19p6um-0005iP-MV for ieprep@optimus.ietf.org; Tue, 19 Aug 2003 09:52:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10593 for ; Tue, 19 Aug 2003 09:52:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19p6uk-0000OE-00 for ieprep@ietf.org; Tue, 19 Aug 2003 09:52:46 -0400 Received: from gnat.inet.org ([63.108.254.91]) by ietf-mx with esmtp (Exim 4.12) id 19p6uj-0000OA-00 for ieprep@ietf.org; Tue, 19 Aug 2003 09:52:46 -0400 Received: from extremenetworks.com (unknown [10.18.3.103]) by gnat.inet.org (Postfix) with ESMTP id 4047F67104 for ; Tue, 19 Aug 2003 10:20:48 -0400 (EDT) Date: Tue, 19 Aug 2003 09:52:38 -0400 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: RJ Atkinson To: ieprep Content-Transfer-Encoding: 7bit Message-Id: <651F98E3-D24C-11D7-8F01-00039357A82A@extremenetworks.com> X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [Ieprep] Fwd: [e2e] e2e delay characteristics Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit The note below appeared on the IRTF End-to-End RG's public mailing list this morning. Since it provides measured data on delay and congestion in a typical IP backbone, it might be of interest to some folks here. Ran Begin forwarded message: > From: Konstantina Papagiannaki > Date: Mon Aug 18, 2003 18:02:09 America/Montreal > To: Matthew Wright > Cc: end2end-interest@postel.org > Subject: Re: [e2e] e2e delay characteristics > Message-Id: <200308182202.h7IM29r23652@athens.sprintlabs.com> > In-Reply-To: Message from Matthew Wright of > "Sat, 16 Aug 2003 08:25:37 EDT." > <200308161225.h7GCPbo14731@gslacks.cs.umass.edu> > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > > This is not exactly what you are looking for, but it may give you an > idea of > what the delays look like for packets that transit the core of a > backbone > network. At http://ipmon.sprint.com/delaystat/ you can see the > distribution of > delays experienced through the Sprint IP network. Equal Cost MultiPath > generates sometimes distributions with multiple modes, depending on > how many > equal paths exist through the network and what their propagation > delays are > (an example is > http://ipmon.sprint.com/delaystat/delay.php?date=20021121&linkpa > ir=results/20021121/sj-01.0-to-nyc-27.0). There is very little > evidence of > congestion in the core, so if you are looking for congestion and loss, > this > type of statistics are definitely not what you are looking for:-) > > Hope this helps... > > Dina _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Wed Aug 27 02:30:39 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23744 for ; Wed, 27 Aug 2003 02:30:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rtef-0002Vg-Df for ieprep-archive@odin.ietf.org; Wed, 27 Aug 2003 02:19:41 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7R6Jd8p009631 for ieprep-archive@odin.ietf.org; Wed, 27 Aug 2003 02:19:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rrO5-0001uC-Kg for ieprep-web-archive@optimus.ietf.org; Tue, 26 Aug 2003 23:54:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15267 for ; Tue, 26 Aug 2003 23:54:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rrO3-00039X-00 for ieprep-web-archive@ietf.org; Tue, 26 Aug 2003 23:54:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19rrO2-00039U-00 for ieprep-web-archive@ietf.org; Tue, 26 Aug 2003 23:54:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rmpM-0005Go-NW; Tue, 26 Aug 2003 19:02:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rdbO-00033V-MH for ieprep@optimus.ietf.org; Tue, 26 Aug 2003 09:11:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02630 for ; Tue, 26 Aug 2003 09:11:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rdbM-0000UJ-00 for ieprep@ietf.org; Tue, 26 Aug 2003 09:11:12 -0400 Received: from mcl-its-dq.saic.com ([149.8.64.40]) by ietf-mx with esmtp (Exim 4.12) id 19rdbL-0000UD-00 for ieprep@ietf.org; Tue, 26 Aug 2003 09:11:11 -0400 Received: from mcl-its-ieg01.mail.saic.com by mcl-its-dq.saic.com for ieprep@ietf.org; Tue, 26 Aug 2003 09:08:36 -0400 Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12]) by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.21) with SMTP id M2003082609083430073 for ; Tue, 26 Aug 2003 09:08:34 -0400 Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2655.55) id ; Tue, 26 Aug 2003 09:07:29 -0400 Message-Id: From: "King, Kimberly S." To: "Ieprep (E-mail)" Date: Tue, 26 Aug 2003 09:08:34 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Subject: [Ieprep] Call for improved cell phone service during emergencies Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , A couple of interesting articles on reliable wireless service prompted by the recent blackouts. http://www.cellular-news.com/story/9590.shtml http://www.businessweek.com/technology/content/aug2003/tc20030826_3914_tc024 .htm _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Wed Aug 27 02:55:00 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28485 for ; Wed, 27 Aug 2003 02:55:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rtXs-0001Q7-Lo for ieprep-archive@odin.ietf.org; Wed, 27 Aug 2003 02:12:40 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7R6CbG6005443 for ieprep-archive@odin.ietf.org; Wed, 27 Aug 2003 02:12:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rr3D-0000tY-LA for ieprep-web-archive@optimus.ietf.org; Tue, 26 Aug 2003 23:32:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13049 for ; Tue, 26 Aug 2003 23:32:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rr3B-0002dJ-00 for ieprep-web-archive@ietf.org; Tue, 26 Aug 2003 23:32:49 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19rr3A-0002dD-00 for ieprep-web-archive@ietf.org; Tue, 26 Aug 2003 23:32:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rmpm-0005Nk-Sy; Tue, 26 Aug 2003 19:02:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19reSD-00047D-9H for ieprep@optimus.ietf.org; Tue, 26 Aug 2003 10:05:49 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04828; Tue, 26 Aug 2003 10:05:42 -0400 (EDT) Message-Id: <200308261405.KAA04828@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ieprep@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 26 Aug 2003 10:05:42 -0400 Subject: [Ieprep] I-D ACTION:draft-ietf-ieprep-ets-general-04.txt Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet Emergency Preparedness Working Group of the IETF. Title : General Requirements for Emergency Telecommunication Service Author(s) : K. Carlberg, R. Atkinson Filename : draft-ietf-ieprep-ets-general-04.txt Pages : 10 Date : 2003-8-26 This document presents a list of general requirements in support of Emergency Telecommunications Service (ETS). Solutions to these requirements are not presented in this document. Additional requirements pertaining to specific applications, or types of applications, are to be specified in separate document(s). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ieprep-ets-general-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ieprep-ets-general-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ieprep-ets-general-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-8-26102425.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ieprep-ets-general-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ieprep-ets-general-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-8-26102425.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From exim@www1.ietf.org Thu Aug 28 04:27:48 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16422 for ; Thu, 28 Aug 2003 04:27:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sDXe-0006n2-A5 for ieprep-archive@odin.ietf.org; Wed, 27 Aug 2003 23:33:46 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7S3XkIw026099 for ieprep-archive@odin.ietf.org; Wed, 27 Aug 2003 23:33:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19s8dn-00043u-Nm for ieprep-web-archive@optimus.ietf.org; Wed, 27 Aug 2003 18:19:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14103 for ; Wed, 27 Aug 2003 18:19:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19s8dk-0001kT-00 for ieprep-web-archive@ietf.org; Wed, 27 Aug 2003 18:19:44 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19s8dk-0001kQ-00 for ieprep-web-archive@ietf.org; Wed, 27 Aug 2003 18:19:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19s4yR-0001Ms-06; Wed, 27 Aug 2003 14:24:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19s18U-0005GA-94 for ieprep@optimus.ietf.org; Wed, 27 Aug 2003 10:18:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00514 for ; Wed, 27 Aug 2003 10:18:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19s18S-0006WW-00 for ieprep@ietf.org; Wed, 27 Aug 2003 10:18:56 -0400 Received: from [149.8.64.40] (helo=mcl-its-dq.saic.com) by ietf-mx with esmtp (Exim 4.12) id 19s18R-0006WP-00 for ieprep@ietf.org; Wed, 27 Aug 2003 10:18:55 -0400 Received: from mcl-its-ieg01.mail.saic.com by mcl-its-dq.saic.com for ieprep@ietf.org; Wed, 27 Aug 2003 10:18:02 -0400 Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11]) by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.21) with SMTP id M2003082710180120686 for ; Wed, 27 Aug 2003 10:18:01 -0400 Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2655.55) id ; Wed, 27 Aug 2003 10:18:01 -0400 Message-Id: From: "King, Kimberly S." To: "Ieprep (E-mail)" Date: Wed, 27 Aug 2003 10:17:51 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Subject: [Ieprep] Web for emergency notification Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , "Here's how RAINS-Net works: When a 9-1-1 call comes into a dispatch center, the information an operator types into the dispatch center computers can be routed to a cell phone message or a pop-up dialog box on a PC. In the case of an emergency event like a hazardous waste spill, those people on the RAINS-Net network would be notified immediately, and the dialog box might direct them to additional multimedia information, such as a video on how to respond to a hazardous waste spill. The RAINS-Net system, which goes live on Thursday, already has about 1,000 files that provide additional information on emergency situations. " http://www.nwfusion.com/news/2003/0820coaliuses.html _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep