IEPREP (Internet Emergency Preparedness) By: Jeffery Pelletier

Outline Explanation of IEPREP (Internet Emergency Preparedness) Some major threats to an network (ie. Examples) RFC 3487 RFC 3690 RFC 3523 RFC 3689 RFC 4190 RFC 4375 Statistics from 9/11

IEPREP Created for times of emergency and/or disasters. – Access to any public telecommunications at hand Conventional phone Internet Access PDAs Cell Phone IP Telephones The objectives: – Create Network that will not get over congested in the time of an emergency. – Have uninterrupted communication between emergency personal. – Have proper authorization given to certain individuals.

Potential Threats to a Network Natural Disasters – Hurricanes – Floods – Tornados – Tsunamis – Fires – Earthquakes Man-Made Threats – Terrorist Attacks – Plane Crashes – Hackers

RFC 3487 Session Initiation Protocol (SIP) – In times of emergencies, there needs to be access to circuit switched networks by emergency personal. – SIP contain large handling capabilities – Limited though due to network capacities. Network Topologies: – IP end-to-end – IP to CSN Network Models: – Pre-configured for ETS Can modify behavior of certain protocols – Transparent Model Transfer valid IP packets but has no control over protocols – SIP/RTP transparent User is in control of incoming/outgoing calls – Restricted SIP Cannot add certain SIP protocols

RFC 3690 IP telephony requirements Mapping used to distinguish PSTN lines – Regular traffic vs. emergency traffic Exists in Application layer – To keep track of billing – To keep track of authorized usage. (abuse of service)

RFC 3523 Describes topology naming conventions for IEPREP phone calls Four topologies: – IP bridging IP core between two circuit-switched networks – IP at the start An IP phone makes a call to a circuit switched phone – IP at the end A circuit switched phone makes a call to an IP phone – End-to-End IP There are no circuit switched network phones and IP phones are used at both ends

RFC 3689 Emergency Telecommunications System (ETS) – Network setup for use in the times of emergencies Explains labeling – Numeric – Alphanumeric – String of bits Emergency Standards – T1.631 = Used in accordance with the GETS system. – E.106 = Guide to PSTN phone lines in the times of an emergency. – F.706 = Extends E.106 into Multimedia type applications. – H and I = Multi-level label mechanism for emergency communications. Four Requirements – IF Signaling = Fact that there is an emergency present. – Labels = Method to determine content of traffic. – Policy = Determines explanation of a specific characteristic. – Network Functionality = Probabilities vs. Guarantees.

RFC 4190 Emergency system other than the norm – 911 system in US – 999 system in England Need for a system that extends national boundaries. Governmental Emergency Telecommunications Systems (GETS) – United States Emergency System – First overseen by National Communication System – Post 9/11, now overseen by newly formed Department of Homeland Security. – Given priority over regular phone traffic. – Credit card like approach used for authorization. – Service guarantee (certain amount of packets get through no-matter what) Agencies Included in GETS development and advancement: – Federal Emergency Agency (FEMA) – NASA – Department of Transportation

RFC 4375 ETS – Single administrative Domain 4 examples – Resource Domain = Router or a host and the physical media used connect the two. – Administrative Domain = Collection of resources under one single authority. – Transmit Domain = Transmits data from one domain to another. – Stub Domain = Administrative domain that deals with the source of destination of an IP packet.

Statistics from 9/11 AT&T had call numbers of 430 million – Up from 100 million from the previous day. Verizon Wireless had a 100 percent call increase from the previous day. Increase of 100 percent of Washington DC phone usage. Increase of 1000 percent of New Jersey phone usage.

QUESTION???????