FW: RFC 3939 on Calling Line Identification for Voice Mail Messag es
"Glenn Parsons" <[email protected]> Wed, 22 Dec 2004 10:58:41 -0500
| Newsgroups | gmane.ietf.vpim |
|---|---|
| Message-ID | <085091CB2CA14E4B8B163FFC37C84E9D0293168F@zcarhxm0.corp.nortel.com> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C4E83F.1111B0EC Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4E83F.1111B0EC" ------_=_NextPart_001_01C4E83F.1111B0EC Content-Type: text/plain; charset="iso-8859-1" FYI > ---------- > From: [email protected] on behalf of > [email protected] > Sent: Tuesday, December 21, 2004 6:18 PM > To: [email protected] > Cc: [email protected] > Subject: RFC 3939 on Calling Line Identification for Voice Mail > Messages > > <<ATT8255966.TXT>> <<rfc3939.URL>> <<ATT8255967.txt>> > > A new Request for Comments is now available in online RFC libraries. > > > RFC 3939 > > Title: Calling Line Identification for Voice Mail > Messages > Author(s): G. Parsons, J. Maruszak > Status: Standards Track > Date: December 2004 > Mailbox: [email protected], > [email protected] > Pages: 11 > Characters: 22739 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ema-vpim-clid-09.txt > > URL: ftp://ftp.rfc-editor.org/in-notes/rfc3939.txt > > > This document describes a method for identifying the originating > calling party in the headers of a stored voice mail message. Two new > header fields are defined for this purpose: Caller_ID and Called_Name. > Caller_id is used to store sufficient information for the recipient to > callback, or reply to, the sender of the message. Caller-name > provides the name of the person sending the message. > > This is now a Proposed Standard Protocol. > > This document specifies an Internet standards track protocol for > the Internet community, and requests discussion and suggestions > for improvements. Please refer to the current edition of the > "Internet Official Protocol Standards" (STD 1) for the > standardization state and status of this protocol. 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 [email protected]. Requests to be > added to or deleted from the RFC-DIST distribution list should > be sent to [email protected]. > > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > an EMAIL message to [email protected] with the message body > help: ways_to_get_rfcs. For example: > > To: [email protected] > 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 [email protected]. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > Submissions for Requests for Comments should be sent to > [email protected]. Please consult RFC 2223, Instructions to RFC > Authors, for further information. > > > Joyce K. Reynolds and Sandy Ginoza > 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. > > ------_=_NextPart_001_01C4E83F.1111B0EC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2658.2"> <TITLE>FW: RFC 3939 on Calling Line Identification for Voice Mail = Messages</TITLE> </HEAD> <BODY> <P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">FYI</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">----------</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:</FONT></B> <FONT = SIZE=3D2 FACE=3D"Arial">[email protected] on behalf of = [email protected]</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:</FONT></B> <FONT = SIZE=3D2 FACE=3D"Arial">Tuesday, December 21, 2004 6:18 PM</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:</FONT></B> = <FONT SIZE=3D2 FACE=3D"Arial">[email protected]</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:</FONT></B> = <FONT SIZE=3D2 FACE=3D"Arial">[email protected]</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:</FONT></B> = <FONT SIZE=3D2 FACE=3D"Arial">RFC = 3939 on Calling Line Identification for Voice Mail Messages</FONT> </P> <P><FONT FACE=3D"Arial" SIZE=3D2 COLOR=3D"#000000"> = <<ATT8255966.TXT>> </FONT><FONT FACE=3D"Arial" SIZE=3D2 = COLOR=3D"#000000"> <<rfc3939.URL>> </FONT><FONT = FACE=3D"Arial" SIZE=3D2 COLOR=3D"#000000"> = <<ATT8255967.txt>> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">A new Request for Comments is now = available in online RFC libraries.</FONT> </P> <BR> <P><FONT SIZE=3D2 = FACE=3D"Monaco"> RFC = 3939</FONT> </P> <P><FONT SIZE=3D2 = FACE=3D"Monaco"> = Title: Calling Line Identification for = Voice Mail</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> &n= bsp; = Messages</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> = Author(s): G. Parsons, J. Maruszak</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> = Status: Standards Track</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> = Date: December 2004</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> = Mailbox: [email protected],</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> &n= bsp; = [email protected]</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> = Pages: 11</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> Characters: = 22739</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> = Updates/Obsoletes/SeeAlso: None</FONT> </P> <P><FONT SIZE=3D2 = FACE=3D"Monaco"> I-D = Tag: draft-ema-vpim-clid-09.txt</FONT> </P> <P><FONT SIZE=3D2 = FACE=3D"Monaco"> = URL: </FONT><U> <FONT = COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Monaco"><A = HREF=3D"ftp://ftp.rfc-editor.org/in-notes/rfc3939.txt" = TARGET=3D"_blank">ftp://ftp.rfc-editor.org/in-notes/rfc3939.txt</A></FON= T></U> </P> <BR> <P><FONT SIZE=3D2 FACE=3D"Monaco">This document describes a method for = identifying the originating</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">calling party in the headers of a = stored voice mail message. Two new</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">header fields are defined for this = purpose: Caller_ID and Called_Name.</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">Caller_id is used to store = sufficient information for the recipient to</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">callback, or reply to, the sender of = the message. Caller-name</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">provides the name of the person = sending the message.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">This is now a Proposed Standard = Protocol.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">This document specifies an Internet = standards track protocol for</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">the Internet community, and requests = discussion and suggestions</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">for improvements. Please refer = to the current edition of the</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">"Internet Official Protocol = Standards" (STD 1) for the</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">standardization state and status of = this protocol. Distribution</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">of this memo is unlimited.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">This announcement is sent to the IETF = list and the RFC-DIST list.</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">Requests to be added to or deleted = from the IETF distribution list</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">should be sent to = [email protected]. Requests to be</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">added to or deleted from the = RFC-DIST distribution list should</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">be sent to = [email protected].</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">Details on obtaining RFCs via FTP or = EMAIL may be obtained by sending</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">an EMAIL message to = [email protected] with the message body </FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">help: ways_to_get_rfcs. For = example:</FONT> </P> <P><FONT SIZE=3D2 = FACE=3D"Monaco"> To: = [email protected]</FONT> <BR><FONT SIZE=3D2 = FACE=3D"Monaco"> Subject: = getting rfcs</FONT> </P> <P><FONT SIZE=3D2 = FACE=3D"Monaco"> help: = ways_to_get_rfcs</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">Requests for special distribution = should be addressed to either the</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">author of the RFC in question, or to = [email protected]. Unless</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">specifically noted otherwise on the = RFC itself, all RFCs are for</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">unlimited distribution.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">Submissions for Requests for Comments = should be sent to</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">[email protected]. = Please consult RFC 2223, Instructions to RFC</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">Authors, for further = information.</FONT> </P> <BR> <P><FONT SIZE=3D2 FACE=3D"Monaco">Joyce K. Reynolds and Sandy = Ginoza</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">USC/Information Sciences = Institute</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">...</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">Below is the data which will enable a = MIME compliant Mail Reader </FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">implementation to automatically = retrieve the ASCII version</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">of the RFCs.</FONT> </P> <BR> </BODY> </HTML> ------_=_NextPart_001_01C4E83F.1111B0EC-- ------_=_NextPart_000_01C4E83F.1111B0EC Content-Type: application/octet-stream; name="ATT8255966.TXT" Content-Disposition: attachment; filename="ATT8255966.TXT" Content-Type: Message/External-body; access-type="mail-server"; server="[email protected]" Content-Type: text/plain Content-ID: <[email protected]> RETRIEVE: rfc DOC-ID: rfc3939 ------_=_NextPart_000_01C4E83F.1111B0EC Content-Type: message/external-body; site="in-notes"; dir="rfc3939.txt"; mode="ftp.isi.edu"; access-type="anon-ftp" ------_=_NextPart_000_01C4E83F.1111B0EC Content-Type: text/plain; name="ATT8255967.txt" Content-Disposition: attachment; filename="ATT8255967.txt" _______________________________________________ IETF-Announce mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ietf-announce ------_=_NextPart_000_01C4E83F.1111B0EC Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ VPIM mailing list [email protected] https://www1.ietf.org/mailman/listinfo/vpim ------_=_NextPart_000_01C4E83F.1111B0EC--