[Ieprep] RFC 3523 on Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology
rfc-editor@rfc-editor.org Thu, 17 April 2003 22:18 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11835 for <ieprep-archive@odin.ietf.org>; Thu, 17 Apr 2003 18:18:39 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3HMRwS14674 for ieprep-archive@odin.ietf.org; Thu, 17 Apr 2003 18:27:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3HMRw814671 for <ieprep-web-archive@optimus.ietf.org>; Thu, 17 Apr 2003 18:27: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 SAA11824 for <ieprep-web-archive@ietf.org>; Thu, 17 Apr 2003 18:18:08 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196HkC-0003D2-00 for ieprep-web-archive@ietf.org; Thu, 17 Apr 2003 18:20:36 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 196HkC-0003Cy-00 for ieprep-web-archive@ietf.org; Thu, 17 Apr 2003 18:20:36 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3HMQV814609; Thu, 17 Apr 2003 18:26:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3HMP9814530 for <ieprep@optimus.ietf.org>; Thu, 17 Apr 2003 18:25: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 SAA11644; Thu, 17 Apr 2003 18:15:20 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196HhT-0003CS-00; Thu, 17 Apr 2003 18:17:47 -0400
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 196HhS-0003CL-00; Thu, 17 Apr 2003 18:17:47 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h3HMHx013593; Thu, 17 Apr 2003 15:17:59 -0700 (PDT)
Message-Id: <200304172217.h3HMHx013593@gamma.isi.edu>
To: IETF-Announce:;
Cc: rfc-editor@rfc-editor.org, ieprep@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 17 Apr 2003 15:17:59 -0700
Subject: [Ieprep] RFC 3523 on Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology
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: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
A new Request for Comments is now available in online RFC libraries. RFC 3523 Title: Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology Author(s): J. Polk Status: Informational Date: April 2003 Mailbox: jmpolk@cisco.com Pages: 6 Characters: 10190 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-polk-ieprep-scenarios-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3523.txt This document defines the topology naming conventions that are to be used in reference to Internet Emergency Preparedness (IEPREP) phone calls. These naming conventions should be used to focus the IEPREP Working Group during discussions and when writing requirements, gap analysis and other solutions documents. This document is a product of the Internet Emergency Preparedness Working Group of the IETF. 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.echo 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.