RFC 3523: Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology
In plain English — editorial summary, not part of the RFC
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 memo provides information for the Internet community.
Document record
- Document ID
- RFC3523
- Published
- April 2003
- Authors
- J. Polk
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5442LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) Using Internet MailCurrent
March 2009
- RFC 3525Gateway Control Protocol Version 1Obsoleted
June 2003
- RFC 3515The Session Initiation Protocol (SIP) Refer MethodUpdated
April 2003
- RFC 3545Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and ReorderingCurrent
July 2003
- RFC 3497RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M VideoCurrent
March 2003
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
- RFC 3551RTP Profile for Audio and Video Conferences with Minimal ControlUpdated
July 2003
- RFC 3555MIME Type Registration of RTP Payload FormatsObsoleted
July 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?