From fluffy@cisco.com Wed Apr 6 08:48:57 2011 Return-Path: X-Original-To: privacydir@core3.amsl.com Delivered-To: privacydir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B295E28C0F6 for ; Wed, 6 Apr 2011 08:48:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.57 X-Spam-Level: X-Spam-Status: No, score=-110.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CDMjGAggV+-0 for ; Wed, 6 Apr 2011 08:48:50 -0700 (PDT) Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 06F733A69CD for ; Wed, 6 Apr 2011 08:48:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1961; q=dns/txt; s=iport; t=1302105016; x=1303314616; h=from:content-transfer-encoding:subject:date:references: to:message-id:mime-version; bh=LMv5v/TiIBqwhfDea72l5wksVXur+BRuE1IcI/lBYHo=; b=e2h8TNZbxwTIk5cNHxdV9bc3zgVT2QokRQfaGCoDPpywdJAP7rp9mSMc hVLDg7yyAUoMCv0hqlg5KBRojFWK352zgxrn6j6NDJZdCTlLUqUlw4GYD zIgkUoRBbZdkgxvBWq2oPjnI/iBw/7tYldzL72Rcp6xUnFdyAc2NQJePW Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApIIAEKLnE2rRDoG/2dsb2JhbACYbI0Md4h5nCOcRYVsBIVOh26DYw X-IronPort-AV: E=Sophos;i="4.63,311,1299456000"; d="scan'208";a="331825154" Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-2.cisco.com with ESMTP; 06 Apr 2011 15:50:15 +0000 Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p36FoFfJ017577 for ; Wed, 6 Apr 2011 15:50:15 GMT From: Cullen Jennings Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 6 Apr 2011 09:53:28 -0600 References: <20110406125020.17538.70016.idtracker@localhost> To: privacydir@ietf.org Message-Id: <5F626EDA-0746-43AB-AAA5-2F7B87B21D6A@cisco.com> Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [privacydir] Fwd: [siprec] Last Call: (Use Cases and Requirements for SIP-based Media Recording (SIPREC)) to Informational RFC X-BeenThere: privacydir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "Privacy Directorate to develop the concept of privacy considerations for IETF specifications and to review internet-drafts for privacy considerations." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2011 15:48:57 -0000 I think this draft deserves a careful review from someone on the privacy = directorate that has not been too involved. A key thing to know is that = when this WG was chartered, we agreed to the charter text=20 The working group will make sure that any protocol specified addresses = these concerns and includes mechanisms to alert users to the fact that a session they are participating in is being recorded. The choice of the word "users" was driven around all users in the = session need to know, not just one end of the call.=20 Begin forwarded message: > From: The IESG > Date: April 6, 2011 6:50:20 AM MDT > To: IETF-Announce > Cc: siprec@ietf.org > Subject: [siprec] Last Call: (Use Cases = and Requirements for SIP-based Media Recording (SIPREC)) to = Informational RFC > Reply-To: ietf@ietf.org >=20 >=20 > The IESG has received a request from the SIP Recording WG (siprec) to > consider the following document: > - 'Use Cases and Requirements for SIP-based Media Recording (SIPREC)' > as an Informational RFC >=20 > 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 2011-04-20. 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. >=20 > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-siprec-req/ >=20 > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-siprec-req/ >=20 >=20 >=20 > No IPR declarations have been submitted directly on this I-D. > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec