header
Click on the red underlined text to get to the source
... There is currently a need for a mechanism to identify the originating
party of a voice mail message, outside of the "FROM" header
information. The telephone number and name of the caller are
...
... typically available from the telephone network, but there is no
obvious header field to store this in an Internet Mail message.
...
... [RFC2076] currently lists "phone" as an Internet message header which
would hold the originating party's telephone number, but it is listed
...
... would hold the originating party's telephone number, but it is listed
as "non-standard", i.e., usage of this header is not generally
recommended. It also has no defined format, making the information
unparsable. There is no similar entry for the originator's name.
...
... unparsable. There is no similar entry for the originator's name.
It is proposed that two new message header fields be included to hold
this information, namely the Calling Line Identification ("Caller ...
...
The Calling Line Identification header ("Caller-ID") holds sufficient
information for the recipient's voice mail system ...
... reply to, the sender of the message. The number that is contained in
this header is supplied by the telephone system. The exact format of
the data received depends on the type of call, that is -- internal or
...
... (e.g., subaddress, redirecting number), as well as the meta-data, are
not intended to be stored in this header.
...
... Date Header ...
... T1.401]. This MAY be used, as
there is an existing "Date" Internet header to hold this information.
It is a local implementation decision whether this time or the local
system time will be recorded in the "Date" header ...
... header to hold this information.
It is a local implementation decision whether this time or the local
system time will be recorded in the "Date" header.
...
...
As a result, for the caller name header defined in this document,
characters are represented with ASCII characters. However, if a name
...
... in [RFC2234]. While the semantics of these headers are defined in
sections 4 and 5, the syntax uses the 'unstructured' token defined in
...
...
Note that unlisted and restricted numbers are not a concern as these
header fields are defined to contain what the called party would see
(e.g., 'Private Name'), as opposed to the complete details exchanged
between service providers ...
... However, it must also be noted that this mechanism allows the
explicit indication of phone numbers in the headers of an email
message (used to store voice messages ...
... voice messages). While the rationale for this
is reviewed in section 1, the recipient of this message may not be
aware that this information is contained in the headers unless the
user's client presents the information. Its use is intended to be
...
... Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text ", RFC 2047draft, November 1996. ...