As per Relevance of the word technical, we have this rfc below:
Network Working Group M.
Request for Comments: 1569 Dover Beach Consulting, Inc
Category: Informational January 1994
Principles of Operation for the TPC.INT Subdomain
Radio Paging -- Technical
Status of this
This memo provides information for the Internet community. This
does not specify an Internet standard of any kind. Distribution
this memo is unlimited
Table of
1. Introduction ................................................ 1
2. Naming, Addressing, and Routing ............................. 2
2.1 Addressing ................................................. 2
2.2 Routing .................................................... 3
3. Procedure ................................................... 3
3.1 MAILing versus SENDing ..................................... 4
3.2 Latency .................................................... 4
4. Usage Examples .............................................. 5
4.1 MIME-based ................................................. 5
4.2 Non-MIME ................................................... 5
5. Security Considerations ..................................... 6
6. Acknowledgements ............................................ 6
7. References .................................................. 6
8. Author's Address ............................................ 6
1.
As an adjunct to the usual, two-way electronic mail service, it is
times useful to employ a one-way text notification service,
radio paging. This memo describes a technique for radio paging
the Internet mail infrastructure. In particular, this memo
on the case in which radio pagers are identified via
international telephone network
The technique described by this memo, mapping telephone numbers
domain names, is derived from the TPC.INT subdomain. Consult
1530, "Principles of Operation for the TPC.INT Subdomain:
Principles and Policy" for overview information
Rose [Page 1]
RFC 1569 Radio Paging -- Technical Procedures January 1994
2. Naming, Addressing, and
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
is a telephone number within that country
2.1.
This number is used to construct the address of a radio pager server
which forms the recipient address for the message, e.g., one of
pager-alpha@6.7.7.8.0.4.9.5.1.4.1.tpc.
pager-numeric@6.7.7.8.0.4.9.5.1.4.1.tpc.
where the domain-part is constructed by reversing the
number, converting each digit to a domain-label, and being
under "tpc.int." (The telephone number must not include
international access codes.)
In addition, addresses of the
pager.ATOM@6.7.7.8.0.4.9.5.1.4.1.tpc.
pager-alpha.ATOM@6.7.7.8.0.4.9.5.1.4.1.tpc.
pager-numeric.ATOM@6.7.7.8.0.4.9.5.1.4.1.tpc.
where "ATOM" is an (optional) RFC 822 atom [1], are reserved
future use. Note that the mailbox syntax is purposefully
in the interests of pragmatism. To paraphrase RFC 822, an atom
defined as
atom = 1*
atomchar=
(A-Z a-z)>
/
/ "!" / "#" / "$" / "%" / "&" / "'" / "*" / "+"
/ "-" / "/" / "=" / "?" / "^" / "_" / "`" / "{"
/ "|" / "}" / "~"
Finally, note that some Internet mail software (especially
from outside the Internet) impose stringent limitations on the
of a mailbox-string. Thus, originating user agents should take
in limiting the local-part to no more than 70 or so characters
Rose [Page 2]
RFC 1569 Radio Paging -- Technical Procedures January 1994
2.2.
The message is routed in exactly the same fashion as all
electronic mail, i.e., using the MX algorithm [2]. Since a
pager server might be able to access many radio pagers,
wildcarding facilities of the DNS [3,4] are used accordingly.
example, if a radio pager server residing at "dbc.mtview.ca.us"
willing to access any radio pager with a telephone number prefix
+1 415 940
then this resource record might be
*.0.4.9.5.1.4.1.tpc.int. IN MX 10 dbc.mtview.ca.us
Naturally, if several radio pager servers were willing to access
radio pager in that prefix, multiple MX resource records would
present
It should be noted that the presence of a wildcard RR which matches
radio pager server's address does not imply that the
telephone number is valid, or, if valid, that a radio pager
identified by the phone number. Rather, the presence of a
RR indicates that a radio pager server is willing to attempt access
3.
When information is to be sent to a radio pager, the user
constructs an RFC 822 message, containing a "Message-ID" field and
textual content (e.g., a "text/plain" content [5]).
The message is then sent to the radio pager server's electronic
address
The radio pager server begins by looking at the local part of
address. If the local-part is the literal string "pager-alpha"
this indicates that the recipient is using an alpha-numeric pager
The radio pager server consults a local database to determine how
send the page based on the domain-part. This local
includes information about the protocol used to talk to the
network and the access number. As such, a radio pager server
register itself in the DNS as providing service only to those
numbers for which it has such knowledge
Otherwise, if the local-part is the literal string "pager-numeric
then this indicates that the recipient is using a numeric pager.
radio pager server may consult a local database to determine how
send the page based on the domain-part; or, it may dial the
Rose [Page 3]
RFC 1569 Radio Paging -- Technical Procedures January 1994
specified in the domain-part directly
For alpha-numeric pagers, the radio pager server determines
information found in the headers and body of the message are
when constructing the paging message. For example, some radio
servers might choose to examine the "To" and "Subject" fields,
addition to the body, whilst other radio pager servers might
to simply send the body verbatim
For numeric pagers, the radio pager server sends only the body,
must consistent solely of digits
3.1. MAILing versus
An SMTP client communicating with a radio pager server may
attempt either the MAIL or SEND command. The radio pager server
support the MAIL command, and MAY support any of the SEND, SOML,
SAML commands
If the MAIL command is used, then a positive completion reply to
the RCPT and DATA commands indicates, at a minimum, that the
has been queued for transmission into the radio paging network
the recipient, but is at least queued for transmission into the
paging network
If the SEND command is used, then a positive completion reply to
the RCPT and DATA commands indicates that the message has
accepted by the radio paging network for delivery to the recipient
If the SOML or SAML command is used, then a positive completion
to both the RCPT and DATA commands indicates that the message
have been accepted by the radio paging network for delivery to
recipient
3.2.
Although the Internet electronic mail service tends to
delivery in a timely and reliable manner, some paging services
wish to provide a higher degree of assurance to their clients,
particular guaranteeing that a positive reply code means that
page has been sent on the radio network. For such requirements,
primary constraints are server implementation and client/
network connectivity
A client that uses the SEND or SAML commands is explicitly
real-time transmission on the radio network and is requiring that
server reply code will carry a statement of success or failure
that transmission
Rose [Page 4]
RFC 1569 Radio Paging -- Technical Procedures January 1994
The IP level of the Internet performs datagram store-and-
service, but gives the end system hosts the appearance of
connectivity, by virtue of allowing interactive service.
Internet electronic mail service adds another layer of store-and
forward indirection, so that messages may go through any number
relays (and/or gateways). This may introduce arbitrarily
delays of minutes, hours, or days
A client that configures their Internet attachment to permit "direct
SMTP connectivity to a pager server will be able to submit
requests to the server directly, without additional SMTP-relaying
That is, transmission from paging client to paging server will be
"SMTP-hop"only. This will eliminate any possibility of non
deterministic delay by the Internet itself
The combination of configuring paging server and paging client
allow direct IP/SMTP-level interaction and ensuring that they
SEND or SAML commands only will mean that a client receiving
positive reply from the server is assured that the page has been
on the radio network
4. Usage
4.1. MIME-
To: pager-alpha@6.7.7.8.0.4.9.5.1.4.1.tpc.
cc: Marshall Rose
From: Carl Malamud
Date: Thu, 22 Jul 1993 08:38:00 -0800
Subject: First example, for an alphanumeric
Message-ID: <19930908220700.1@malamud.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-
A brief textual message
4.2. Non-
To: pager-numeric@6.7.7.8.0.4.9.5.1.4.1.tpc.
cc: Marshall Rose
From: Carl Malamud
Date: Thu, 22 Jul 1993 08:38:00 -0800
Subject: Second example, for a numeric
Message-ID: <19930908220700.2@malamud.com
2026282044
Rose [Page 5]
RFC 1569 Radio Paging -- Technical Procedures January 1994
5. Security
Internet mail may be subject to monitoring by third parties, and
particular, message relays
6.
This document was motivated by "Simple Network Paging Protocol -
Version 1", by Allen Gwinn of Southern Methodist University
David H. Crocker and Carl Malamud also provided substantive comments
7.
[1] Crocker, D., "Standard for the Format of ARPA Internet
Messages", STD 11, RFC 822, University of Delaware, August 1982.
[2] Partridge, C., "Mail Routing and the Domain System", STD 14,
974, BBN, January 1986.
[3] Mockapetris, P., "Domain Names -- Concepts and Facilities",
13, RFC 1034, Information Sciences Institute, November 1987.
[4] Mockapetris, P., "Domain Names -- Implementation
Specification", STD 13, RFC 1035, Information Sciences Institute
November 1987.
[5] Borenstein, N., and N. Freed, "MIME (Multipurpose Internet
Extensions) Part One: Mechanisms for Specifying and
the Format of Internet Message Bodies", RFC 1521, Bellcore
Innosoft, September 1993.
8. Author's
Marshall T.
Dover Beach Consulting, Inc
420 Whisman
Mountain View, CA 94043-2186
Phone: +1 415 968 1052
Fax: +1 415 968 2510
EMail: mrose@dbc.mtview.ca.
Rose [Page 6]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
