Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
RFC 1703

Document Type RFC - Informational (October 1994; No errata)
Obsoletes RFC 1569
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1703 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            M. Rose
Request for Comments: 1703                  Dover Beach Consulting, Inc.
Obsoletes: 1569                                             October 1994
Category: Informational

           Principles of Operation for the TPC.INT Subdomain:
                  Radio Paging -- Technical Procedures

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.

Table of Contents

   1. Introduction ...............................................    1
   2. Naming, Addressing, and Routing ............................    2
   2.1 Addressing ................................................    2
   2.2 Routing ...................................................    3
   3. Procedure ..................................................    3
   3.1 Alpha-numeric Radio Pagers ................................    3
   3.2 Numeric Radio Pagers ......................................    4
   3.3 MAILing versus SENDing ....................................    4
   3.4 Latency ...................................................    5
   4. Usage Examples .............................................    5
   4.1 A MIME Example ............................................    6
   4.2 A Non-MIME Example ........................................    6
   5. Server Configuration Example ...............................    6
   6. Security Considerations ....................................    8
   7. Acknowledgements ...........................................    8
   8. References .................................................    8
   9. Author's Address ...........................................    9

1.  Introduction

   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.

Rose                                                            [Page 1]
RFC 1703          Radio Paging -- Technical Procedures      October 1994

2.  Naming, Addressing, and Routing

   A radio pager is identified by a telephone number, e.g.,

     +1 415 940 8776

   where "+1" indicates the IDDD country code, and the remaining string
   is a telephone number within that country.

   In addition to a telephone number, a PIN may also be required to
   uniquely identify a radio pager.

2.1.  Addressing

   This number is used to construct the address of a radio paging
   server, which forms the recipient address for the message, e.g., one
   of:

     pager.ATOM@6.7.7.8.0.4.9.5.1.4.1.tpc.int
     pager-alpha.ATOM@6.7.7.8.0.4.9.5.1.4.1.tpc.int
     pager-numeric@6.7.7.8.0.4.9.5.1.4.1.tpc.int

   where "ATOM" is an RFC 822 atom [1], an opaque string for use in
   recipient identification when communicating with the paging network,
   and the domain-part is constructed by reversing the telephone number,
   converting each digit to a domain-label, and being placed under
   "tpc.int".  (The telephone number must not include any international
   access codes.)

   Note that the mailbox syntax is purposefully restricted in the
   interests of pragmatism.  To paraphrase STD 11, RFC 822, an atom is
   defined as:

     atom    = 1*atomchar

     atomchar=   <any upper or lowercase alphabetic character
                  (A-Z a-z)>
               / <any digit (0-9)>
               / "!" / "#" / "$" / "%" / "&" / "'" / "*" / "+"
               / "-" / "/" / "=" / "?" / "^" / "_" / "`" / "{"
               / "|" / "}" / "~"

   Finally, note that some Internet mail software (especially gateways
   from outside the Internet) impose stringent limitations on the size
   of a mailbox-string.  Thus, originating user agents should take care
   in limiting the local-part to no more than 70 or so characters.

Rose                                                            [Page 2]
RFC 1703          Radio Paging -- Technical Procedures      October 1994

2.2.  Routing

   The message is routed in exactly the same fashion as all other
   electronic mail, i.e., using the MX algorithm [2].  Since a radio
   paging server might be able to access many radio pagers, the
   wildcarding facilities of the DNS [3,4] are used accordingly.  For
   example, if a radio paging server residing at "dbc.mtview.ca.us" is
   willing to access any radio pager with a telephone number prefix of

     +1 415 940

   then this resource record might be present
Show full document text