As per Relevance of the word indicates, we have this rfc below:
Network Working Group M.
Request for Comments: 1703 Dover Beach Consulting, Inc
Obsoletes: 1569 October 1994
Category:
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 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.
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 1703 Radio Paging -- Technical Procedures October 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
In addition to a telephone number, a PIN may also be required
uniquely identify a radio pager
2.1.
This number is used to construct the address of a radio
server, which forms the recipient address for the message, e.g.,
of
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@6.7.7.8.0.4.9.5.1.4.1.tpc.
where "ATOM" is an RFC 822 atom [1], an opaque string for use
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
"tpc.int". (The telephone number must not include any
access codes.)
Note that the mailbox syntax is purposefully restricted in
interests of pragmatism. To paraphrase STD 11, 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 1703 Radio Paging -- Technical Procedures October 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
paging server might be able to access many radio pagers,
wildcarding facilities of the DNS [3,4] are used accordingly.
example, if a radio paging 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 paging servers were willing to access
radio pager in that prefix, multiple MX resource records would
present. (The DNS servers for the TPC.INT subdomain perform
rudimentary form of load balancing by rotating the order of the
records returned on each query.)
It should be noted that the presence of a wildcard RR which matches
radio paging 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 paging 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 paging server's electronic
address. The radio paging server begins by looking at the local
of the address
3.1. Alpha-numeric Radio
If the local-part is either "pager.ATOM" or "pager-alpha.ATOM"
this indicates that the recipient is using an alpha-numeric
pager, and ATOM either identifies a paging network (CARRIER), or
radio pager identity number (PIN), or both, according to these rules
(1) if ATOM consists entirely of numeric characters, then ATOM is
PIN, and the domain-part refers to the IXO access
number for a radio paging carrier; otherwise
Rose [Page 3]
RFC 1703 Radio Paging -- Technical Procedures October 1994
(2) if ATOM does not contain a hyphen character ("-"), then ATOM
a CARRIER, a local database is consulted to determine
corresponding IXO access telephone number, and the
number corresponding to the domain-part is used to identify
radio pager; otherwise
(3) if ATOM does contain a hyphen character ("-"), then
to the left of the first hyphen is a CARRIER, and everything
the right of that hyphen is a PIN, a local database is
to determine the corresponding IXO access telephone number,
the PIN is used is used to identify the radio pager
If the local-part starts with "pager.", then the message sent to
radio pager consists of the body of the message; otherwise, if
local-part starts with "pager-alpha.", then the radio paging
determines which information in the headers and body of the
are used when constructing the paging message. For example,
radio paging servers might choose to examine the "To" and "Subject
fields, in addition to the body, whilst other radio paging
might choose to simply send the body verbatim
3.2. Numeric Radio
If the local-part is the literal string "pager-numeric" then
indicates that the recipient is using a numeric pager, and the
pager dials the telephone number corresponding to the domain-part
The message sent to the radio pager consists of the body of
message, which must consist solely of digits
3.3. MAILing versus
An SMTP client communicating with a radio paging server may
attempt either the MAIL or SEND command. The radio paging
MUST support the MAIL command, and MAY support any of the SEND, SOML
or 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
Rose [Page 4]
RFC 1703 Radio Paging -- Technical Procedures October 1994
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.4.
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 paging network. For
requirements, the primary constraints are server implementation
client/server network connectivity
A client that uses the SEND or SAML commands is explicitly
real-time transmission on the radio paging network and is
that the server reply code will carry a statement of success
failure about that transmission
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 radio paging server will be able to
paging requests to the server directly, without additional SMTP
relaying. That is, transmission from radio paging client to
will be one "SMTP-hop"only. This will eliminate any possibility
non-deterministic delay by the Internet itself
The combination of configuring radio paging server and 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 paging network
4. Usage
These examples make use of the "iddd.tpc.int" subdomain. The
servers for this subdomain, upon encountering a domain of the form
NUMBER.iddd.tpc.
Rose [Page 5]
RFC 1703 Radio Paging -- Technical Procedures October 1994
automatically create a CNAME RR of the form
R.E.B.M.U.N.iddd.tpc.
e.g.,
14159408776.iddd.tpc.
will be treated
6.7.7.8.0.4.9.5.1.4.1.tpc.
4.1. A MIME
To: pager-alpha.98765@18005551234.iddd.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 sent to the radio paging
having an IXO access telephone number of "+1-8005551234"
to the radio pager having a PIN of "98765".
4.2. A Non-MIME
To: pager-numeric@14159408776.iddd.tpc.
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
5. Server Configuration
A hypothetical radio paging carrier, e.g.,
Pigeon
might choose to integrate its radio paging services with Internet e
mail in the following fashion
Rose [Page 6]
RFC 1703 Radio Paging -- Technical Procedures October 1994
(1) The radio paging carrier establishes a top-level domain name
e.g.,
pigeon.
(2) The radio paging carrier installs and operates one or
radio paging servers, each having a unique entry in the DNS
e.g.,
ixo1.pigeon.net. IN A a.b.c.
Each of these radio paging servers runs an SMTP server
implements the SEND command as described in Section 3.3 above
(3) The radio paging carrier coordinates with the administrators
the TPC.INT subdomain to have the appropriate MX records
to the DNS, assigning cost values in the MX records to
any difference in the quality of service between the
paging servers, e.g.,
4.3.2.1.5.5.5.0.0.8.1.tpc.int. IN MX 5 ixo1.pigeon.net
4.3.2.1.5.5.5.0.0.8.1.tpc.int. IN MX 5 ixo2.pigeon.net
which would provide both load-balancing and
(particularly if the servers were located at different points
the Internet). At this point, messages can be sent using
addressing formats described in Section 2.2 above
(4) The radio paging carrier may choose to make available a
program which uses the SMTP SEND command, in order to
"real-time" delivery of messages into the radio paging network
(5) Finally, the radio paging carry may choose to assign each of
customers a mailbox, e.g.,
mrose@pager.pigeon.
which maps to the TPC.INT address for the customer's radio pager
The system(s) listed in the DNS for this domain would
the appropriate mail aliases for this mapping, e.g.,
R: 220 pager.pigeon.net SMTP
S: HELO malamud.
R: 220 pager.pigeon.
S: EXPN
R: 250
Rose [Page 7]
RFC 1703 Radio Paging -- Technical Procedures October 1994
At the carrier's discretion, these systems may also be
systems running the radio paging servers. However, this needn'
be the case. For example, consider a situation where a
program which uses the SMTP SEND command, wants to ensure that
is talking to radio paging server for an address: e.g.,
R: 220 pager.pigeon.net SMTP
S: EHLO malamud.
R: 220-pager.pigeon.
R: 220
S: VRFY
R: 551 User not local
try
R: 220 pager.pigeon.net SMTP
S: EHLO malamud.
R: 220-pager.pigeon.
R: 220
S: VRFY
R: 250
6. Security
Internet mail may be subject to monitoring by third parties, and
particular, message relays
7.
This document was motivated by RFC 1568 [6] and RFC 1645 [7].
addition, David Crocker, Carl Malamud, and Perry Metzger
provided substantive comments
8.
[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",
Laboratories, STD 14, RFC 974, BBN, January 1986.
[3] Mockapetris, P., "Domain Names -- Concepts and Facilities",
13, RFC 1034, USC/Information Sciences Institute, November 1987.
[4] Mockapetris, P., "Domain Names -- Implementation
Specification", STD 13, RFC 1035, USC/Information
Institute, November 1987.
Rose [Page 8]
RFC 1703 Radio Paging -- Technical Procedures October 1994
[5] Borenstein, N., and N. Freed, "MIME: Mechanisms for
and Describing the Format of Internet Message Bodies", RFC 1521,
Bellcore, Innosoft, September 1993.
[6] Gwinn, A., "Simple Network Paging Protocol - Version 1(b)",
1568, Southern Methodist University, January 1994.
[7] Gwinn, A., "Simple Network Paging Protocol - Version 2",
1645, Southern Methodist University, July 1994.
9. 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 9]
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
