Protocol Action: 'Calling Line Identification for Voice Mail Messages' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 16 June 2004 15:22 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07226 for <ietf-announce-archive@ietf.org>; Wed, 16 Jun 2004 11:22:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BacEn-0000pN-Oo for ietf-announce-archive@ietf.org; Wed, 16 Jun 2004 11:22:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BabSg-0000uW-00 for ietf-announce-archive@ietf.org; Wed, 16 Jun 2004 10:32:23 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BaagC-0001Ve-00; Wed, 16 Jun 2004 09:42:18 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by mx2.foretec.com with esmtp (Exim 4.24) id 1BaaMP-000127-Fk; Wed, 16 Jun 2004 09:21:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BaYmg-0006SH-4W; Wed, 16 Jun 2004 07:40:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BaU0t-0002wo-Rv for ietf-announce@megatron.ietf.org; Wed, 16 Jun 2004 02:35:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04449 for <ietf-announce@ietf.org>; Wed, 16 Jun 2004 02:35:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BaU0q-0002HY-S7 for ietf-announce@ietf.org; Wed, 16 Jun 2004 02:35:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BaRu0-0003Iu-00 for ietf-announce@ietf.org; Wed, 16 Jun 2004 00:19:57 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BaMy5-00030C-00; Tue, 15 Jun 2004 19:03:49 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BaMt9-0000s0-1a; Tue, 15 Jun 2004 18:58:43 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1BaMt9-0000s0-1a@megatron.ietf.org>
Date: Tue, 15 Jun 2004 18:58:43 -0400
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'Calling Line Identification for Voice Mail Messages' to Proposed Standard
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has approved the following document:

- 'Calling Line Identification for Voice Mail Messages '
   <draft-ema-vpim-clid-09.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product 
of an IETF Working Group. 

The IESG contact person is Scott Hollenbeck.

Technical Summary
   
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. Called-name provides
the name of the person sending the message.
   
Working Group Summary
   
This document was originally produced by the Electronic Mail 
Association (EMA). It was reviewed by the VPIM working group but is not 
a product of that group.
   
Protocol Quality
   
Ned Freed reviewed the specification for the IESG.

RFC Editor note

Please add this sentence to the end of paragraph two in Section 3.2 (after 
"Though it is desirable that an international number not be truncated to 10 
digits if it contains more, it is recognized that this will happen due to 
limitations of various systems."):

"Implementors of this specification should be aware that some phone systems 
are known to truncate international numbers, even though it is recognized 
that this is undesirable behavior."


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce