idnits 2.17.1 draft-ietf-seamoby-paging-requirements-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3154 5 Title: Requirements and Functional Architecture for an IP 6 Host Alerting Protocol 7 Author(s): J. Kempf, C. Castelluccia, P. Mutaf, N. Nakajima, 8 Y. Ohba, R. Ramjee, Y. Saifullah, B. Sarikaya, 9 X. Xu 10 Status: Informational 11 Date: August 2001 12 Mailbox: James.Kempf@Sun.COM, pars.mutaf@inria.fr, 13 claude.castelluccia@inria.fr, 14 nnakajima@tari.toshiba.com, 15 yohba@tari.toshiba.com, ramjee@bell-labs.com, 16 Yousuf.Saifullah@nokia.com, 17 Behcet.Sarikaya@usa.alcatel.com, 18 xiaofeng.xu@usa.alcatel.com 19 Pages: 16 20 Characters: 31534 21 Updates/Obsoletes/SeeAlso: None 23 I-D Tag: draft-ietf-seamoby-paging-requirements-01.txt 25 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3154.txt 27 This document develops an architecture and a set of requirements 28 needed to support alerting of hosts that are in dormant mode. The 29 architecture and requirements are designed to guide development of 30 an IP protocol for alerting dormant IP mobile hosts, commonly called 31 paging. 33 This document is a product of the Context Transfer, Handoff Candidate 34 discovery and Dormant Mode Host Alerting Working Group of the of the 35 IETF. 37 This memo provides information for the Internet community. It does 38 not specify an Internet standard of any kind. Distribution of this 39 memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.