Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
 by core3.amsl.com (Postfix) with ESMTP id F26313A6829;
 Wed,  7 Jan 2009 03:12:21 -0800 (PST)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by core3.amsl.com (Postfix) with ESMTP id E6F823A6829
 for <sip@core3.amsl.com>; Wed,  7 Jan 2009 03:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066, 
 BAYES_00=-2.599]
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 BbqNqL2Aji1Q for <sip@core3.amsl.com>;
 Wed,  7 Jan 2009 03:12:20 -0800 (PST)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
 [195.171.110.225])
 by core3.amsl.com (Postfix) with ESMTP id 2A8E83A6806
 for <sip@ietf.org>; Wed,  7 Jan 2009 03:12:20 -0800 (PST)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
 by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
 with ESMTP id <0KD30078KLS6QI@siemenscomms.co.uk> for sip@ietf.org; Wed,
 07 Jan 2009 11:12:06 +0000 (GMT)
Date: Wed, 07 Jan 2009 11:12:05 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <CED54617-F7DC-4EA9-9120-4B24BDC8AA12@ntt-at.com>
To: Shida Schubert <shida@ntt-at.com>, sip@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D00167DF86@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: BCP or Informational: Mechanisms for UA initiated privacy
Thread-Index: AclwtMprehH/aWIQRWavHXEbsg0jaAAA/TmQ
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <CED54617-F7DC-4EA9-9120-4B24BDC8AA12@ntt-at.com>
Cc: "Drage, Keith \(Keith\)" <drage@alcatel-lucent.com>
Subject: Re: [Sip] BCP or Informational: Mechanisms for UA initiated privacy
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
 <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
 <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I agree.

John 

> -----Original Message-----
> From: Shida Schubert [mailto:shida@ntt-at.com] 
> Sent: 07 January 2009 10:43
> To: sip@ietf.org List
> Cc: Elwell, John; Drage, Keith (Keith)
> Subject: BCP or Informational: Mechanisms for UA initiated privacy
> 
> 
>   At the last meeting, Keith asked the group to provide feedback on
> whether the draft-ietf-sip-ua-privacy addressing the milestone
> "Mechanisms for UA initiated privacy" should proceed as BCP or
> as an informational.
> 
>   As a co-author of the draft, my inclination is to go informational.
> 
>   Reason is because the 2 specifications the draft requires, namely
> GRUU and TURN aren't widely deployed, and neither are RFCs
> (Although GRUU I believe is pretty close.).
> 
>   Despite the fact that people I talked to are keen on implementing
> these specifications, I don't think the draft which requires and
> depends on specifications that aren't widely deployed neither RFC
> should be proceeded as a Best Current Practice..
> 
>   Regards
>    Shida
> 
>   
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

