Last Call: draft-ietf-sip-ua-privacy (UA-Driven Privacy Mechanism for SIP) to Informational RFC

The IESG <iesg-secretary@ietf.org> Mon, 27 April 2009 22:55 UTC

Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 659993A6F63; Mon, 27 Apr 2009 15:55:48 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Subject: Last Call: draft-ietf-sip-ua-privacy (UA-Driven Privacy Mechanism for SIP) to Informational RFC
Message-Id: <20090427225549.659993A6F63@core3.amsl.com>
Date: Mon, 27 Apr 2009 15:55:49 -0700
Cc: sip@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2009 22:55:49 -0000

The IESG has received a request from the Session Initiation Protocol WG 
(sip) to consider the following document:

- 'UA-Driven Privacy Mechanism for SIP '
   <draft-ietf-sip-ua-privacy-07.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-05-11. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-sip-ua-privacy-07.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16751&rfc_flag=0