Skip to main content

Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology

The information below is for an old version of the document that is already published as an RFC.
Document Type This is an older version of an Internet-Draft that was ultimately published as an RFC.
Author James Polk
Last updated 2015-10-14 (Latest revision 2003-03-05)
Stream Internet Engineering Task Force (IETF)
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3523 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note The name is misleading - this is a very simple topology terms document that divides the cases of Internet and PSTN meeting and bridging - RFC-Editor note with new abstract and title is due
from me
Send notices to <>
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
        Pages:      6
        Characters: 10190
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-polk-ieprep-scenarios-03.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

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.