RFC1703 on Radio Paging -- Technical Procedures

"Joyce K. Reynolds" <jkrey@isi.edu> Tue, 25 October 1994 20:47 UTC

Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09308; 25 Oct 94 16:47 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa17921; 25 Oct 94 16:47 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09295; 25 Oct 94 16:47 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09163; 25 Oct 94 16:44 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa17848; 25 Oct 94 16:44 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA29783>; Tue, 25 Oct 1994 13:44:59 -0700
Message-Id: <199410252044.AA29783@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1703 on Radio Paging -- Technical Procedures
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 25 Oct 1994 13:45:43 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


        RFC 1703:

        Title:      Principles of Operation for the TPC.INT Subdomain:
                    Radio Paging -- Technical Procedures             
        Author:     M. Rose
        Mailbox:    mrose@dbc.mtview.ca.us
        Pages:      9
        Characters: 17,985
        Obsoletes:  1569


As an adjunct to the usual, two-way electronic mail service, it is at
times useful to employ a one-way text notification service, called
radio paging.  This memo describes a technique for radio paging using
the Internet mail infrastructure.  In particular, this memo focuses on
the case in which radio pagers are identified via the international
telephone network.  The technique described by this memo, mapping
telephone numbers to domain names, is derived from the TPC.INT
subdomain.  Consult RFC 1530, "Principles of Operation for the TPC.INT
Subdomain: General Principles and Policy" for overview information.

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.

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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  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@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
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://ds.internic.net/rfc/rfc1703.txt"><ftp://ds.internic.net/rfc/rfc1703.txt>