RFC 3523
Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology
🎀 Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology
Okay bestie, here's the deal 💅 This is RFC 3523, and it's an Informational doc from April 2003. It's from the Network Working Group, and the author is J. Polk (that's James M. Polk) at Cisco Systems 🦋 It doesn't list any RFCs it obsoletes or updates, so it's standing on its own ✨
Status of this Memo
This memo is just giving info to the Internet community 🌸 It doesn't specify an Internet standard of any kind, and it can be distributed without limits ✨
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. 💜
Abstract
Okay so this doc sets up the topology naming conventions for Internet Emergency Preparedness (IEPREP) phone calls 📞 The idea is that everyone uses the same names, so the IEPREP Working Group stays focused during discussions and when they're writing requirements, gap analysis, and other solutions docs. It's giving clarity 🔥
Table of Contents
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1 Motivation. . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Terms and Definitions . . . . . . . . . . . . . . . . . . 2
2. IEPREP Topologies. . . . . . . . . . . . . . . . . . . . . . 2
2.1 Topology "IP Bridging" . . . . . . . . . . . . . . . . . 3
2.2 Topology "IP at the Start". . . . . . . . . . . . . . . . 3
2.3 Topology "IP at the End". . . . . . . . . . . . . . . . . 4
2.4 Topology "End-to-End IP". . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Author's Address. . . . . . . . . . . . . . . . . . . . . . . 5
8. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 61. Introduction 🧚
This doc is all about the topology naming conventions used when talking about IEPREP phone calls ✨ These names should be used to focus the IEPREP Working Group (WG) during discussions and when writing requirements, gap analysis, and other solutions documents.
Honestly there's been so much confusion on the IEPREP list and in every meeting about which topologies IEPREP is even considering 😭 Hopefully this doc gives every reader and author one reference set of named architectures. Main character energy 👑
This memo tries to stay agnostic about IP signaling or control protocols (SIP, MEGACO, etc.), and also about any underlying Quality of Service (QOS) mechanisms (Diffserv, RSVP, NSIS, etc.) 💖
1.1 Motivation
Simply put, the goal is for everyone to reference the same named topologies so the dialog is actually useful and less confusing, and the WG can keep moving 🦋
1.2 Terms and Definitions
These acronyms need to be spelled out for clarity 🍓
CSN = Circuit Switched Network
GW = Gateway (CSN to IP, or IP to CSN)2. IEPREP Topologies 🌈
Okay so there are 4 topologies that get mentioned a lot, but barely written down, in this WG's work so far 🙈 The subsections below name and describe each one.
The 4 topologies, quickly:
- Topology "IP Bridging"
- Topology "IP at the Start"
- Topology "IP at the End"
- Topology "End-to-End IP"
2.1 Topology "IP Bridging"
This one is sometimes called "IP in the Middle" of two CSNs 🫶 In this topology, a CSN phone of any type starts (dials) a call to another CSN phone, with an IP core sitting between the two CSNs.
This topology should simplistically look like this:
Circuit Internet Circuit
Switched IP or IP Switched
Network Ingress IP Segment Egress Network
-----------+ +--------------+ +-----------
| +----+ | IP | +----+ |
CSN | | | | | | | | CSN
Phone ------->| GW |----------------------->| GW |-------->Phone
| | | | | | | |
| +----+ | | +----+ |
-----------+ +--------------+ +-----------
Figure 1. Topology "IP Bridging"2.2 Topology "IP at the Start"
In this one, the initiating party places (dials) the call from an IP Phone (PDA or computer), and the called party is in the CSN 💅
Internet Circuit
or CSN Switched
IP Segment Ingress Network
-------------------+ +---------------
| +----+ |
IP | | | | CSN
Phone ------------------>| GW |--------> Phone
| | | |
| +----+ |
-------------------+ +---------------
Figure 2. Topology "IP at the Start"2.3 Topology "IP at the End"
This time the calling party places the call from a CSN phone, and the called party is in an IP network 🌸
Circuit Internet
Switched CSN or
Network Egress IP Segment
-------------------+ +---------------
| +----+ |
CSN | | | | IP
Phone ------------------>| GW |--------> Phone
| | | |
| +----+ |
-------------------+ +---------------
Figure 3. Topology "IP at the End"2.4 Topology "End-to-End IP"
This topology has no circuit switched sections in the call path, which is giving pure IP vibes ✨
Internet
or
IP Network
+-----------------------------------------+
| |
+---------+ +-----------+
| |
| IP IP |
| Phone --------------------------------------------> Phone |
| |
+---------+ +-----------+
| |
+-----------------------------------------+
Figure 4. Topology "End to End IP"Even though it's drawn as one big IP cloud, the Internet is really a bunch of loosely connected IP domains 🌈 An End-to-End IP call will probably cross a number of these domains and/or multiple network providers, and that can affect the call 👀
3. Security Considerations 💀
This document only suggests a common naming convention for IEPREP WG discussions, so there are no special security considerations. Phew 🫶
4. IANA Considerations 🍓
There are no IANA considerations within this document.
5. Acknowledgements 💖
Thank you to Scott Bradner, Kimberly King, and Mike Pierce for their comments and suggestions 🧚
6. References 📚
There are no references at the present time.
7. Author's Address 🦋
James M. Polk Cisco Systems 2200 East President George Bush Turnpike Richardson, Texas 75082 USA
EMail: jmpolk@cisco.com
8. Full Copyright Statement 🎀
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the Internet Society. ✨
📦 where this page comes from
- ietf: rfc3523 2003-04
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms