Re: [Sip] BCP or Informational: Mechanisms for UA initiated privacy
"Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com> Wed, 07 January 2009 11:32 UTC
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 9335628C141; Wed, 7 Jan 2009 03:32:24 -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 BC45C28C12B for <sip@core3.amsl.com>; Wed, 7 Jan 2009 03:32:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.581
X-Spam-Level:
X-Spam-Status: No, score=-3.581 tagged_above=-999 required=5 tests=[AWL=-0.982, 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 k5GpseKW8I4f for <sip@core3.amsl.com>; Wed, 7 Jan 2009 03:32:23 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id AA3B03A6989 for <sip@ietf.org>; Wed, 7 Jan 2009 03:32:22 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n07BW4eQ028773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 7 Jan 2009 12:32:04 +0100
Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n07BW0a9026379; Wed, 7 Jan 2009 12:32:04 +0100
Received: from FIESEXC007.nsn-intra.net ([10.159.0.15]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 7 Jan 2009 12:32:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 07 Jan 2009 13:32:32 +0200
Message-ID: <C41BFCED3C088E40A8510B57B165C162F40EE3@FIESEXC007.nsn-intra.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D00167DF86@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] BCP or Informational: Mechanisms for UA initiated privacy
Thread-Index: AclwtMprehH/aWIQRWavHXEbsg0jaAAA/TmQAACz/5A=
References: <CED54617-F7DC-4EA9-9120-4B24BDC8AA12@ntt-at.com> <0D5F89FAC29E2C41B98A6A762007F5D00167DF86@GBNTHT12009MSX.gb002.siemens.net>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Elwell, John" <john.elwell@siemens.com>, Shida Schubert <shida@ntt-at.com>, sip@ietf.org
X-OriginalArrivalTime: 07 Jan 2009 11:32:03.0711 (UTC) FILETIME=[903138F0:01C970BB]
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 as well. Informational is a good choice. BCP would be quite far fetched. >-----Original Message----- >From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On >Behalf Of ext Elwell, John >Sent: 07 January, 2009 13:12 >To: Shida Schubert; sip@ietf.org >Cc: Drage, Keith (Keith) >Subject: Re: [Sip] BCP or Informational: Mechanisms for UA >initiated privacy > >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 > _______________________________________________ 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
- [Sip] BCP or Informational: Mechanisms for UA ini… Shida Schubert
- Re: [Sip] BCP or Informational: Mechanisms for UA… Elwell, John
- Re: [Sip] BCP or Informational: Mechanisms for UA… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Sip] BCP or Informational: Mechanisms for UA… Jonathan Rosenberg