RFC 3132: Dormant Mode Host Alerting ("IP Paging") Problem Statement
In plain English — editorial summary, not part of the RFC
This memo describes paging, assesses the need for IP paging, and presents a list of recommendations for Seamoby charter items regarding work on paging. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3132
- Published
- June 2001
- Authors
- J. Kempf
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3154Requirements and Functional Architecture for an IP Host Alerting ProtocolCurrent
August 2001
- RFC 3096Requirements for robust IP/UDP/RTP header compressionCurrent
July 2001
- RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdated
September 2001
- RFC 3027Protocol Complications with the IP Network Address TranslatorCurrent
January 2001
- RFC 3022Traditional IP Network Address Translator (Traditional NAT)Current
January 2001
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
- RFC 3260New Terminology and Clarifications for DiffservCurrent
April 2002
- RFC 2983Differentiated Services and TunnelsCurrent
October 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?