RFC 1645 (rfc1645) - Page 1 of 18
Simple Network Paging Protocol - Version 2
Alternative Format: Original Text Document
Network Working Group A. Gwinn
Request for Comments: 1645 Southern Methodist University
Obsoletes: 1568 July 1994
Category: Informational
Simple Network Paging Protocol - Version 2
Status of this Memo
This memo provides information for the Internet community. This memo
does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
Abstract
This RFC suggests a simple way for delivering both alphanumeric and
numeric pages (one-way) to radio paging terminals. Gateways
supporting this protocol, as well as SMTP, have been in use for
several months for nationwide paging and messaging. In addition,
email filters and SNPP client software for Unix and Windows are
available at no cost. Please contact the author for more
information.
Earlier versions of this specification were reviewed by IESG members
and the "822 Extensions" Working Group. They preferred an alternate
strategy, as discussed under "Relationship to Other IETF Work",
below.
1. Introduction
Beepers are as much a part of computer nerdom as X-terminals
(perhaps, unfortunately, more). The intent of Simple Network Paging
Protocol is to provide a standard whereby pages can be delivered to
individual paging terminals. The most obvious benefit is the
elimination of the need for modems and phone lines to produce
alphanumeric pages, and the added ease of delivery of pages to
terminals in other cities or countries. Additionally, automatic page
delivery should be somewhat more simplified.
2. System Philosophy
Radio paging is somewhat taken for granted, because of the wide
availability and wide use of paging products. However, the actual
delivery of the page, and the process used (especially in wider area
paging) is somewhat complicated. When a user initiates a page, by
dialing a number on a telephone, or entering an alphanumeric page
through some input device, the page must ultimately be delivered to
Gwinn