IETF Logo Mail Archive

Re: [Sipping] WGLC Review: draft-ietf-sipping-capacity-attribute-01.txt

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Fri, 22 September 2006 15:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GQme5-0006d3-0I; Fri, 22 Sep 2006 11:08:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GQme3-0006ct-9F for sipping@ietf.org; Fri, 22 Sep 2006 11:08:51 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GQmdu-0007vN-Fx for sipping@ietf.org; Fri, 22 Sep 2006 11:08:51 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id BEB834F00E0; Fri, 22 Sep 2006 17:08:39 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 22 Sep 2006 17:08:38 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 22 Sep 2006 17:08:38 +0200
Received: from [131.160.36.35] (EH3I2003TGFCPET.lmf.ericsson.se [131.160.36.35]) by mail.lmf.ericsson.se (Postfix) with ESMTP id A0A7F24C5; Fri, 22 Sep 2006 18:08:38 +0300 (EEST)
Message-ID: <4513FC76.7080903@ericsson.com>
Date: Fri, 22 Sep 2006 18:08:38 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] WGLC Review: draft-ietf-sipping-capacity-attribute-01.txt
References: <62B9B0847CC47543B6B3B5E26BD268E60E92541D@zrc2hxm2.corp.nortel.com> <45137B1C.40408@ericsson.com> <4513FC1E.6090004@softarmor.com>
In-Reply-To: <4513FC1E.6090004@softarmor.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Sep 2006 15:08:39.0010 (UTC) FILETIME=[FBD3FC20:01C6DE58]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: Miguel Garcia <Miguel.An.Garcia@nokia.com>, sipping@ietf.org, Mary Barnes <mary.barnes@nortel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Agreed.

Gonzalo

Dean Willis wrote:
> Gonzalo Camarillo wrote:
>> Hi,
>>
>> recommending S/MIME and SIPS has been the standard practice in all the 
>> drafts SIPPING has been producing in a long time. I do not think this 
>> draft is the place to discuss the relationship between TLS, IPsec, 
>> VPNs, etc. I believe such relationship must be tackled by the SIP 
>> specification and its updates.
>>
> 
> Right, but it needs to be written in some way like "using message 
> privacy mechanisms such as TLS or S/MIME," rather than the current text, 
> which appears to limit the solution space to TLS and S/MIME.
> 
> -- 
> dean


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

v2.26.15 | Report a Bug | By Email | System Status