RFC 4375 on Emergency Telecommunications Services (ETS) Requirements for a Single Administrative Domain

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.


        RFC 4375

        Title:      Emergency Telecommunications Services (ETS)
                    Requirements for a Single Administrative Domain
        Author(s):  K. Carlberg
        Status:     Informational
        Date:       January 2006
        Mailbox:    carlberg@g11.org.uk
        Pages:      8
        Characters: 17037
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ieprep-domain-req-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4375.txt


This document presents a list of requirements in support of Emergency
Telecommunications Service (ETS) within a single administrative
domain.  This document focuses on a specific set of administrative
constraints and scope.  Solutions to these requirements are not
presented in this document.

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.

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.
<ftp://ftp.isi.edu/in-notes/rfc4375.txt>
_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux