From ieprep-bounces@ietf.org Fri Aug 03 00:42:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGozB-0004lj-MP; Fri, 03 Aug 2007 00:42:01 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGoz8-0004lT-1s; Fri, 03 Aug 2007 00:41:58 -0400 Received: from [202.99.23.227] (helo=people.com.cn) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IGoz7-0004X6-2p; Fri, 03 Aug 2007 00:41:57 -0400 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jmc446b303f8; Fri, 03 Aug 2007 12:53:45 +0800 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm3c46adda12; Mon, 30 Jul 2007 18:51:53 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm7d46a773cf; Wed, 25 Jul 2007 20:00:23 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Wed, 25 Jul 2007 20:00:21 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID2yB-0003WH-6r; Mon, 23 Jul 2007 14:49:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID2y7-0003S1-R1; Mon, 23 Jul 2007 14:49:19 -0400 Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID2y6-00074b-KV; Mon, 23 Jul 2007 14:49:19 -0400 Received: by bosco.isi.edu (Postfix, from userid 70) id B5E7CDA980; Mon, 23 Jul 2007 11:47:24 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20070723184724.B5E7CDA980@bosco.isi.edu> Date: Mon, 23 Jul 2007 11:47:24 -0700 (PDT) X-Spam-Score: -15.0 (---------------) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-AIMC-AUTH: (null) X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: rfc-editor@rfc-editor.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: rfc-editor@rfc-editor.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8 Cc: ieprep@ietf.org, rfc-editor@rfc-editor.org Subject: [Ieprep] RFC 4958 on A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain X-BeenThere: ieprep@ietf.org List-Id: Internet Emergency Preparedness Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ieprep-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4958 Title: A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain Author: K. Carlberg Status: Informational Date: July 2007 Mailbox: carlberg@g11.org.uk Pages: 28 Characters: 44008 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ieprep-domain-frame-08.txt URL: http://www.rfc-editor.org/rfc/rfc4958.txt This document presents a framework discussing the role of various protocols and mechanisms that could be considered candidates for supporting Emergency Telecommunication Services (ETS) within a single administrative domain. Comments about their potential usage as well as their current deployment are provided to the reader. Specific solutions are not presented. This memo provides information for the Internet community. This document is a product of the Internet Emergency Preparedness Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From ieprep-bounces@ietf.org Mon Aug 06 18:43:13 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIBHw-0001pq-10; Mon, 06 Aug 2007 18:43:00 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIBHu-0001ph-FU; Mon, 06 Aug 2007 18:42:58 -0400 Received: from [202.99.23.227] (helo=people.com.cn) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IIBHt-0007tJ-Ip; Mon, 06 Aug 2007 18:42:58 -0400 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jmd246b7d71e; Tue, 07 Aug 2007 06:54:51 +0800 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jmc446b303f8; Fri, 03 Aug 2007 12:53:45 +0800 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm3c46adda12; Mon, 30 Jul 2007 18:51:53 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm7d46a773cf; Wed, 25 Jul 2007 20:00:23 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Wed, 25 Jul 2007 20:00:21 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID2yB-0003WH-6r; Mon, 23 Jul 2007 14:49:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID2y7-0003S1-R1; Mon, 23 Jul 2007 14:49:19 -0400 Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID2y6-00074b-KV; Mon, 23 Jul 2007 14:49:19 -0400 Received: by bosco.isi.edu (Postfix, from userid 70) id B5E7CDA980; Mon, 23 Jul 2007 11:47:24 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20070723184724.B5E7CDA980@bosco.isi.edu> Date: Mon, 23 Jul 2007 11:47:24 -0700 (PDT) X-Spam-Score: -15.0 (---------------) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-AIMC-AUTH: (null) X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: rfc-editor@rfc-editor.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: rfc-editor@rfc-editor.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: rfc-editor@rfc-editor.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8 Cc: ieprep@ietf.org, rfc-editor@rfc-editor.org Subject: [Ieprep] RFC 4958 on A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain X-BeenThere: ieprep@ietf.org List-Id: Internet Emergency Preparedness Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ieprep-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4958 Title: A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain Author: K. Carlberg Status: Informational Date: July 2007 Mailbox: carlberg@g11.org.uk Pages: 28 Characters: 44008 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ieprep-domain-frame-08.txt URL: http://www.rfc-editor.org/rfc/rfc4958.txt This document presents a framework discussing the role of various protocols and mechanisms that could be considered candidates for supporting Emergency Telecommunication Services (ETS) within a single administrative domain. Comments about their potential usage as well as their current deployment are provided to the reader. Specific solutions are not presented. This memo provides information for the Internet community. This document is a product of the Internet Emergency Preparedness Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep