Requirements and Functional Architecture for an IP Host Alerting Protocol
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3154.
|Authors||Behcet Sarikaya , Nobuyasu Nakajima , James Kempf , Pars Mutaf , R. Ramjee , Xiaofeng Xu , Yousuf Saifullah , Claude Castelluccia , Yoshihiro Ohba|
|Last updated||2013-03-02 (Latest revision 2001-05-21)|
|RFC stream||Internet Engineering Task Force (IETF)|
|Additional resources||Mailing list discussion|
|IESG||IESG state||RFC 3154 (Informational)|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. RFC 3154 Title: Requirements and Functional Architecture for an IP Host Alerting Protocol Author(s): J. Kempf, C. Castelluccia, P. Mutaf, N. Nakajima, Y. Ohba, R. Ramjee, Y. Saifullah, B. Sarikaya, X. Xu Status: Informational Date: August 2001 Mailbox: James.Kempf@Sun.COM, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, Yousuf.Saifullah@nokia.com, Behcet.Sarikaya@usa.alcatel.com, email@example.com Pages: 16 Characters: 31534 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-seamoby-paging-requirements-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3154.txt This document develops an architecture and a set of requirements needed to support alerting of hosts that are in dormant mode. The architecture and requirements are designed to guide development of an IP protocol for alerting dormant IP mobile hosts, commonly called paging. This document is a product of the Context Transfer, Handoff Candidate discovery and Dormant Mode Host Alerting Working Group of the 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.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.