
From root@core3.amsl.com  Mon Feb  1 06:15:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: simple@ietf.org
Delivered-To: simple@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id C24353A694C; Mon,  1 Feb 2010 06:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100201141501.C24353A694C@core3.amsl.com>
Date: Mon,  1 Feb 2010 06:15:01 -0800 (PST)
Cc: simple@ietf.org
Subject: [Simple] I-D Action:draft-ietf-simple-xcap-diff-14.txt
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2010 14:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP for Instant Messaging and Presence Leveraging Extensions Working Group of the IETF.


	Title           : An Extensible Markup Language (XML) Document Format for Indicating A Change in XML Configuration Access Protocol (XCAP) Resources
	Author(s)       : J. Rosenberg, J. Urpalainen
	Filename        : draft-ietf-simple-xcap-diff-14.txt
	Pages           : 26
	Date            : 2010-02-01

This specification defines a document format that can be used to
indicate that a change has occurred in a document managed by the
Extensible Markup Language (XML) Configuration Access Protocol
(XCAP).  This format reports which document has changed and its
former and new entity tags.  It can report the differences between
versions of the document, using an XML patch format.  It can report
existing element and attribute content when versions of an XCAP
server document change.  XCAP diff documents can be delivered to diff
clients using a number of means, including a Session Initiation
Protocol (SIP) event package.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-simple-xcap-diff-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-simple-xcap-diff-14.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-02-01061009.I-D@ietf.org>


--NextPart--

From Jari.Urpalainen@nokia.com  Mon Feb  1 23:27:21 2010
Return-Path: <Jari.Urpalainen@nokia.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B37E3A6AB4 for <simple@core3.amsl.com>; Mon,  1 Feb 2010 23:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 lTdmEDh3NAVE for <simple@core3.amsl.com>; Mon,  1 Feb 2010 23:27:20 -0800 (PST)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 8AD2F3A6AB5 for <simple@ietf.org>; Mon,  1 Feb 2010 23:27:20 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o127Ri0o024862 for <simple@ietf.org>; Tue, 2 Feb 2010 09:27:54 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Feb 2010 09:27:50 +0200
Received: from mgw-da02.ext.nokia.com ([147.243.128.26]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Feb 2010 09:27:49 +0200
Received: from [172.21.37.231] (esdhcp037231.research.nokia.com [172.21.37.231]) by mgw-da02.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o127Rjhh021621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <simple@ietf.org>; Tue, 2 Feb 2010 09:27:47 +0200
Message-ID: <4B67D3F0.3010202@nokia.com>
Date: Tue, 02 Feb 2010 09:27:44 +0200
From: Jari Urpalainen <jari.urpalainen@nokia.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "simple@ietf.org" <simple@ietf.org>
References: <20100201141501.C24353A694C@core3.amsl.com>
In-Reply-To: <20100201141501.C24353A694C@core3.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Feb 2010 07:27:50.0159 (UTC) FILETIME=[3982E1F0:01CAA3D9]
X-Nokia-AV: Clean
Subject: Re: [Simple] I-D Action:draft-ietf-simple-xcap-diff-14.txt
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 07:27:21 -0000

ext Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the SIP for Instant Messaging and Presence Leveraging Extensions Working Group of the IETF.
>
>
> 	Title           : An Extensible Markup Language (XML) Document Format for Indicating A Change in XML Configuration Access Protocol (XCAP) Resources
> 	Author(s)       : J. Rosenberg, J. Urpalainen
> 	Filename        : draft-ietf-simple-xcap-diff-14.txt
> 	Pages           : 26
> 	Date            : 2010-02-01
>   
changes from version 13 (iesg review):
-clarifications to terminology
-added example section to describe the three basic features: listing of 
collection content, patching and xcap component subscriptions
-added section 6 to clarify the usage context of this mime type
-security section updates
-various other nit fixes
br Jari


From ben@nostrum.com  Tue Feb  2 13:13:25 2010
Return-Path: <ben@nostrum.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01D6A3A6970 for <simple@core3.amsl.com>; Tue,  2 Feb 2010 13:13:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001]
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 HBvo1jUHSyQl for <simple@core3.amsl.com>; Tue,  2 Feb 2010 13:13:23 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id C2AAE3A686A for <simple@ietf.org>; Tue,  2 Feb 2010 13:13:22 -0800 (PST)
Received: from dn3-175.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o12LDvS1053484 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Feb 2010 15:13:57 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/alternative; boundary=Apple-Mail-18--924771267
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC743C57135FDB@ESESSCMS0354.eemea.ericsson.se>
Date: Tue, 2 Feb 2010 15:13:57 -0600
Message-Id: <849B84C2-C30D-435F-A73F-AB84022838CE@nostrum.com>
References: <FF84A09F50A6DC48ACB6714F4666CC743C57135FDB@ESESSCMS0354.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1077)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] MSRP ACM: Usage of COMEDIA-TLS needed after all?
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 21:13:25 -0000

--Apple-Mail-18--924771267
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Christer, can you point out the text in 4975 to which you refer? If you =
are talking about the last 3 paragraphs of section 14.4, the point of =
this was not to specify that the offerer must send the fingerprint, but =
simply to show how RFC 4474 interacts with a fingerprint in the offer.

In fact, that section talks about TLS in peer-to-peer mode--that is, =
mutual authentication with self-signed certs on both ends. In this case =
_both_ parties are likely to send fingerprints. In the case where one =
end uses a self-signed cert and the other uses a CA-signed cert, the =
party with the self-signed cert would need to send a =
fingerprint--regardless of which party was active.

As far a reference to RFC 4572, my concern is that we don't accidentally =
institute a requirement to send fingerprints when using a CA-signed =
certificate, instead of a self-signed one. If I recall correctly, RFC =
4572 assumes you are always using self-signed certs. If we do reference =
it, we need to make sure we scope the reference to include "how =
fingerprints work" and not the "requirement to _always_ use a =
fingerprint".



On Jan 29, 2010, at 5:23 AM, Christer Holmberg wrote:

> =20
> Hi,
> =20
> A while ago, it was agreed that we will not refer to COMEDIA-TLS in =
the ACM draft, based on the argument that the TLS procedures in 4975 =
already covers all we need.
> =20
> However, when reading the 4975 text we've spotted an issue with using =
only the 4975 TLS procedures in ACM:
> =20
> 4975 says that the "SDP offerer" provides the fingerprint. The text =
does NOT talk about the "active party" providing the fingerprint, which =
I guess is due to the 4975 definition that the SDP offerer is always the =
active party.
> =20
> But, when COMEDIA is used, the SDP answerer can become the active =
party. But, there is no text in 4975 about the SDP answerer providing =
the fingerprint.
> =20
> Now, there are two ways of solving this:
> =20
> 1. In ACM we specify that an SDP offer with active and actpass shall =
contain the fingerprint, and that an SDP answer with active shall =
contain the fingerprint.
> =20
> OR
> =20
> 2. In ACM we refer to the COMEDIA-TLS procedures, that species the =
usage of mutual authentication, which means both the SDP offer and SDP =
answer will always contain the fingerprint.
> =20
> My preference is option 2. Since we use COMEDIA, I think it is much =
more feasible to also use COMEDIA-TLS, instead of specifying new =
additional MSRP specific TLS procedures.
> =20
> So, if we go for option 2, I propose the following changes/additions =
to the ACM draft:
> =20
> ----------
> =20
> 4.3.  TLS
> =20
>    If MSRP UAs negotiate a TLS transport connection for MSRP, the Uas =
SHALL follow the procedures defined in [RFC4975]. The
>    active MSRP UA will take the role of the TLS client, and the =
passive UA will take the role of the TLS server.
> =20
> ----------
> =20
> 6.  Security Considerations
> =20
>    Use of the COMEDIA procedures changes the connection model =
described in RFC 4975 in that any MSRP endpoint might set up the TCP or
>    TCP/TLS connection, and not only the client sending the SDP offer.
> =20
>    TLS security is not compromised by this fact, since mutual =
authentication [RFC4572] is used - both endpoints provides certificate =
fingerprints
>    in SDP and certificates in TLS independent of if they are active or =
passive. The endpoint that receives the TLS connection can always verify =
the source
>    of the connection, independent of if the connection is set up from =
the SDP offerer or answerer.
> =20
> ----------
> =20
> If people are ok with this, I will add the text to the draft.
> =20
> =20
> Regards,
> =20
> Christer
> =20
> =20
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


--Apple-Mail-18--924771267
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><base href=3D"x-msg://269/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div>Christer, can you point out the text in 4975 =
to which you refer? If you are talking about the last 3 paragraphs of =
section 14.4, the point of this was not to specify that the offerer must =
send the fingerprint, but simply to show how RFC 4474 interacts with a =
fingerprint in the offer.</div><div><br></div><div>In fact, that section =
talks about TLS in peer-to-peer mode--that is, mutual authentication =
with self-signed certs on both ends. In this case _both_ parties are =
likely to send fingerprints. In the case where one end uses a =
self-signed cert and the other uses a CA-signed cert, the party with the =
self-signed cert would need to send a fingerprint--regardless of which =
party was active.</div><div><br></div><div>As far a reference to RFC =
4572, my concern is that we don't accidentally institute a requirement =
to send fingerprints when using a CA-signed certificate, instead of a =
self-signed one. If I recall correctly, RFC 4572 assumes you are always =
using self-signed certs. If we do reference it, we need to make sure we =
scope the reference to include "how fingerprints work" and not the =
"requirement to _always_ use a =
fingerprint".</div><div><br></div><div><br></div><br><div><div>On Jan =
29, 2010, at 5:23 AM, Christer Holmberg wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div><font face=3D"Arial, =
sans-serif" size=3D"3"><div>&nbsp;</div><div><font =
size=3D"2">Hi,</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">A while ago, it was =
agreed that we will not refer to COMEDIA-TLS in the ACM draft, based on =
the argument that the TLS procedures in 4975 already covers all we =
need.</font></div><div><font size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">However, when reading the 4975 text we've spotted an issue =
with using only the 4975 TLS procedures in ACM:</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">4975 says that the =
"SDP offerer" provides the fingerprint. The text does NOT talk about the =
"active party" providing the fingerprint, which I guess is due to the =
4975 definition that the SDP offerer is always the active =
party.</font></div><div><font size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">But, when COMEDIA is used, the SDP answerer can become the =
active party. But, there is no text in 4975 about the SDP answerer =
providing the fingerprint.</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">Now, there are two =
ways of solving this:</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">1. In ACM we specify =
that an SDP offer with active and actpass shall contain the fingerprint, =
and that an SDP answer with active shall contain the =
fingerprint.</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">OR</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">2. In ACM we refer =
to the COMEDIA-TLS procedures, that species the usage of mutual =
authentication, which means both the SDP offer and SDP answer will =
always contain the fingerprint.</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">My preference is =
option 2. Since we use COMEDIA, I think it is much more feasible to also =
use COMEDIA-TLS, instead of specifying new additional MSRP specific TLS =
procedures.</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">So, if we go for =
option 2, I propose the following changes/additions to the ACM =
draft:</font></div><div><font size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">----------</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font face=3D"Courier New, monospace" =
size=3D"2">4.3.&nbsp; TLS</font></div><div><font face=3D"Courier New, =
monospace" size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">&nbsp;&nbsp; If MSRP UAs negotiate a TLS transport connection =
for MSRP, the Uas SHALL follow the procedures defined in [RFC4975]. =
The</font></div><div><font size=3D"2">&nbsp;&nbsp; active MSRP UA will =
take the role of the TLS client, and the passive UA will take the role =
of the TLS server.</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">----------</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">6.&nbsp; Security =
Considerations</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">&nbsp;&nbsp; Use of =
the COMEDIA procedures changes the connection model described in RFC =
4975 in that any MSRP endpoint might set up the TCP =
or</font></div><div><font size=3D"2">&nbsp;&nbsp; TCP/TLS connection, =
and not only the client sending the SDP offer.</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">&nbsp;&nbsp; TLS =
security is not compromised by this fact, since mutual authentication =
[RFC4572] is used - both endpoints provides certificate =
fingerprints</font></div><div><font size=3D"2">&nbsp;&nbsp; in SDP and =
certificates in TLS independent of if they are active or passive. The =
endpoint that receives the TLS connection can always verify the =
source</font></div><div><font size=3D"2">&nbsp;&nbsp; of the connection, =
independent of if the connection is set up from the SDP offerer or =
answerer.</font></div><div><font size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">----------</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font size=3D"2">If people are ok =
with this, I will add the text to the draft.</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">Regards,</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">Christer</font></div><div><font =
size=3D"2">&nbsp;</font></div><div><font =
size=3D"2">&nbsp;</font></div></font>_____________________________________=
__________<br>Simple mailing list<br><a =
href=3D"mailto:Simple@ietf.org">Simple@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/simple">https://www.ietf.org=
/mailman/listinfo/simple</a><br></div></span></blockquote></div><br></body=
></html>=

--Apple-Mail-18--924771267--

From ben@estacado.net  Tue Feb  2 13:24:56 2010
Return-Path: <ben@estacado.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4E703A69A8 for <simple@core3.amsl.com>; Tue,  2 Feb 2010 13:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.024
X-Spam-Level: 
X-Spam-Status: No, score=-2.024 tagged_above=-999 required=5 tests=[AWL=0.575,  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 UKjUgBG-MI4k for <simple@core3.amsl.com>; Tue,  2 Feb 2010 13:24:56 -0800 (PST)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id 798E43A69A3 for <simple@ietf.org>; Tue,  2 Feb 2010 13:24:55 -0800 (PST)
Received: from [172.16.3.175] (dn3-175.estacado.net [172.16.3.175]) (authenticated bits=0) by estacado.net (8.14.3/8.14.2) with ESMTP id o12LPTRp048452 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Feb 2010 15:25:30 -0600 (CST) (envelope-from ben@estacado.net)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC743C5731447B@ESESSCMS0354.eemea.ericsson.se>
Date: Tue, 2 Feb 2010 15:25:29 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FB3BD82-1903-43BA-AA30-FD9F179917AE@estacado.net>
References: <05FD3015-9D28-43CF-B44A-E14CBEB4E464@nostrum.com> <7BA83419-CE5E-4677-99F7-9B19F8863DCD@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C571987A8@ESESSCMS0354.eemea.ericsson.se> <6F445EC4-32AD-4A12-82B3-37ED00F3DC30@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C5720739D@ESESSCMS0354.eemea.ericsson.se> <44628806-B9D9-43AB-8E51-809ECDE94236@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C57241F38@ESESSCMS0354.eemea.ericsson.se> <CE9069DC-4359-4E81-89BA-0075D2876308@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C57242720@ESESSCMS0354.eemea.ericsson.se> <C9F76C52-AF84-4958-9DBD-D181A10F6CC1@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C572E0E43@ESESSCMS0354.eemea.ericsson.se> <FF84A09F50A6DC48ACB6714F4666CC743C572E0E50@ESESSCMS0354.eemea.ericsson.se> <FF84A09F50A6DC48ACB6714F4666CC743C5731447B@ESESSCMS0354.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1077)
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] WGLC MSRP ACM Security Considerations [was: RE: WGLC of msrp-acm and msrp-sessionmatch - Ben's comments]
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 21:24:56 -0000

On Jan 26, 2010, at 3:19 AM, Christer Holmberg wrote:

>=20
> What about the following text?
>=20
> ---------
>=20
> According to the connection model defined in [RFC4975], the MSRP UA =
which sends the SDP offer is the "active", ", and it is responsible for =
creating the MSRP transport
> connection towards the remote UA if a new connection is required. The =
"active" UA also takes the role as TLS client, if TLS is used to protect =
the MSRP messages.
>=20
> When COMEDIA is used, either the sender or the receiver of the SDP =
offer can become "active", and therefor also take the role as TLS =
client. However, there are no procedures in
> [RFC4975] that would break in case the receiver of the SDP offerer =
takes the role as TLS client, and the level of security provided by TLS =
is not affected."

I think that's a good start. I propose adding the following sentence =
between the first and second sentence of your second paragraph:

"The TLS client is responsible for matching the server's certificate to =
the peer's MSRP URI regardless of whether the it acted as the SDP =
offerer or answerer."

I also suggest this additional paragraph, either before or after the TLS =
parts:

"RFC 4975 requires the active party to immediately issue a SEND request =
once the connection is established. This allows the passive party to =
bind the inbound TCP connection to the message session identified by its =
MSRP URI. The use of COMEDIA does not change this requirement. However, =
the active party is no longer assumed to be the SDP offerer. "

>=20
> ---------
>=20
> Regards,
>=20
> Christer
>=20
>=20
>=20
>> -----Original Message-----
>> From: simple-bounces@ietf.org=20
>> [mailto:simple-bounces@ietf.org] On Behalf Of Christer Holmberg
>> Sent: 25. tammikuuta 2010 15:45
>> To: Ben Campbell
>> Cc: Simple WG
>> Subject: [Simple] WGLC MSRP ACM Security Considerations [was:=20
>> RE: WGLC of msrp-acm and msrp-sessionmatch - Ben's comments]
>>=20
>>=20
>> Hi,
>>=20
>> Sorry, forgot to remove some text, in order to make it more clear.
>>=20
>>>> If we don't use COMEDIA-TLS, but simply refer to 4975 for=20
>> TLS, I guess there shouldn't be any issues. Or?
>>>>=20
>>> I think there may be some language in the security consideration=20
>>> section of 4975 concerning how you match the certificate to=20
>> the server=20
>>> that we need to check to make sure it does not contain assumptions=20=

>>> about which party is client or server.
>>>=20
>>=20
>> I was reading the security considerations of 4975, and didn't=20
>> find any such assumptions.
>>=20
>> The text generally talks about sending the fingerprint in=20
>> SDP, but I can't find any specific assumptions.
>>=20
>> Regards,
>>=20
>> Christer
>> _______________________________________________
>> Simple mailing list
>> Simple@ietf.org
>> https://www.ietf.org/mailman/listinfo/simple
>>=20
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


From christer.holmberg@ericsson.com  Tue Feb  2 13:55:31 2010
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FCE93A6985 for <simple@core3.amsl.com>; Tue,  2 Feb 2010 13:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[AWL=-1.828, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 XBPntiw6skWi for <simple@core3.amsl.com>; Tue,  2 Feb 2010 13:55:30 -0800 (PST)
Received: from mailgw10.se.ericsson.net (unknown [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 350BE3A65A6 for <simple@ietf.org>; Tue,  2 Feb 2010 13:55:30 -0800 (PST)
X-AuditID: c1b4fb3d-b7b85ae00000097d-08-4b689f775e63
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id AD.42.02429.77F986B4; Tue,  2 Feb 2010 22:56:07 +0100 (CET)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.1.22]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Tue, 2 Feb 2010 22:56:07 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
Date: Tue, 2 Feb 2010 22:56:06 +0100
Thread-Topic: [Simple] MSRP ACM: Usage of COMEDIA-TLS needed after all?
Thread-Index: AcqkTml6gC+ZubKZTt2gfOU9MwK64gAAkSv4
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC743C58377CE9@ESESSCMS0354.eemea.ericsson.se>
References: <FF84A09F50A6DC48ACB6714F4666CC743C57135FDB@ESESSCMS0354.eemea.ericsson.se>, <849B84C2-C30D-435F-A73F-AB84022838CE@nostrum.com>
In-Reply-To: <849B84C2-C30D-435F-A73F-AB84022838CE@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] MSRP ACM: Usage of COMEDIA-TLS needed after all?
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 21:55:31 -0000

Hi Ben,

>Christer, can you point out the text in 4975 to which you refer? If you ar=
e talking about the last 3 paragraphs of section 14.4,

Yes.

>the point of this was not to specify that the offerer must send the finger=
print, but simply to show how RFC 4474 interacts with a fingerprint in the =
offer.
>
>In fact, that section talks about TLS in peer-to-peer mode--that is, mutua=
l authentication with self-signed certs on both ends. In this case _both_ p=
arties are likely to send fingerprints.

Where is that specified?

The beginning of the section does talk about sending fingerprints in SDP, b=
ut is it clear that both parties send it?

>In the case where one end uses a self-signed cert and the other uses a CA-=
signed cert, the party with the self-signed cert would need to send a finge=
rprint--regardless of which party was active.

Correct. I am only talking about the case when both parties use self signed=
 certs.

>As far a reference to RFC 4572, my concern is that we don't accidentally i=
nstitute a requirement to send fingerprints when using a CA-signed certific=
ate, instead of a self-signed one. If I recall correctly, RFC 4572 assumes =
you are always using self-signed certs. If we do
>reference it, we need to make sure we scope the reference to include "how =
fingerprints work" and not the "requirement to _always_ use a fingerprint".

I don't think 4572 requires the usage of self-signed certs. It describes wh=
at you do (sending fingerprint) IF you use self-signed certs.

But, we could add clarification text saying that the 4572 procedures are fo=
llowed if the UA is using a self-signed cert.

However, IF 4975 already specifies that both endpoints include fingerprint =
attributes then I am not sure we need to refer to 4572. But, it is at least=
 not very clear to me when reading 4975 :)

Regards,

Christer





On Jan 29, 2010, at 5:23 AM, Christer Holmberg wrote:


Hi,

A while ago, it was agreed that we will not refer to COMEDIA-TLS in the ACM=
 draft, based on the argument that the TLS procedures in 4975 already cover=
s all we need.

However, when reading the 4975 text we've spotted an issue with using only =
the 4975 TLS procedures in ACM:

4975 says that the "SDP offerer" provides the fingerprint. The text does NO=
T talk about the "active party" providing the fingerprint, which I guess is=
 due to the 4975 definition that the SDP offerer is always the active party=
.

But, when COMEDIA is used, the SDP answerer can become the active party. Bu=
t, there is no text in 4975 about the SDP answerer providing the fingerprin=
t.

Now, there are two ways of solving this:

1. In ACM we specify that an SDP offer with active and actpass shall contai=
n the fingerprint, and that an SDP answer with active shall contain the fin=
gerprint.

OR

2. In ACM we refer to the COMEDIA-TLS procedures, that species the usage of=
 mutual authentication, which means both the SDP offer and SDP answer will =
always contain the fingerprint.

My preference is option 2. Since we use COMEDIA, I think it is much more fe=
asible to also use COMEDIA-TLS, instead of specifying new additional MSRP s=
pecific TLS procedures.

So, if we go for option 2, I propose the following changes/additions to the=
 ACM draft:

----------

4.3.  TLS

   If MSRP UAs negotiate a TLS transport connection for MSRP, the Uas SHALL=
 follow the procedures defined in [RFC4975]. The
   active MSRP UA will take the role of the TLS client, and the passive UA =
will take the role of the TLS server.

----------

6.  Security Considerations

   Use of the COMEDIA procedures changes the connection model described in =
RFC 4975 in that any MSRP endpoint might set up the TCP or
   TCP/TLS connection, and not only the client sending the SDP offer.

   TLS security is not compromised by this fact, since mutual authenticatio=
n [RFC4572] is used - both endpoints provides certificate fingerprints
   in SDP and certificates in TLS independent of if they are active or pass=
ive. The endpoint that receives the TLS connection can always verify the so=
urce
   of the connection, independent of if the connection is set up from the S=
DP offerer or answerer.

----------

If people are ok with this, I will add the text to the draft.


Regards,

Christer


_______________________________________________
Simple mailing list
Simple@ietf.org<mailto:Simple@ietf.org>
https://www.ietf.org/mailman/listinfo/simple


From christer.holmberg@ericsson.com  Tue Feb  2 13:57:29 2010
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BE493A6985 for <simple@core3.amsl.com>; Tue,  2 Feb 2010 13:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.182
X-Spam-Level: 
X-Spam-Status: No, score=-2.182 tagged_above=-999 required=5 tests=[AWL=-1.745, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 1BMKtXoPX-vP for <simple@core3.amsl.com>; Tue,  2 Feb 2010 13:57:28 -0800 (PST)
Received: from mailgw9.se.ericsson.net (unknown [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 239403A69B2 for <simple@ietf.org>; Tue,  2 Feb 2010 13:57:27 -0800 (PST)
X-AuditID: c1b4fb39-b7c2dae000007b99-f3-4b689fedce42
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 37.03.31641.DEF986B4; Tue,  2 Feb 2010 22:58:06 +0100 (CET)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.1.22]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Tue, 2 Feb 2010 22:58:05 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@estacado.net>
Date: Tue, 2 Feb 2010 22:57:12 +0100
Thread-Topic: [Simple] WGLC MSRP ACM Security Considerations [was: RE: WGLC of msrp-acm and msrp-sessionmatch - Ben's comments]
Thread-Index: AcqkTrO1kiCS1FdvTwab3aDKcbvJjAAA/kWQ
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC743C58377CEA@ESESSCMS0354.eemea.ericsson.se>
References: <05FD3015-9D28-43CF-B44A-E14CBEB4E464@nostrum.com> <7BA83419-CE5E-4677-99F7-9B19F8863DCD@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C571987A8@ESESSCMS0354.eemea.ericsson.se> <6F445EC4-32AD-4A12-82B3-37ED00F3DC30@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C5720739D@ESESSCMS0354.eemea.ericsson.se> <44628806-B9D9-43AB-8E51-809ECDE94236@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C57241F38@ESESSCMS0354.eemea.ericsson.se> <CE9069DC-4359-4E81-89BA-0075D2876308@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C57242720@ESESSCMS0354.eemea.ericsson.se> <C9F76C52-AF84-4958-9DBD-D181A10F6CC1@estacado.net> <FF84A09F50A6DC48ACB6714F4666CC743C572E0E43@ESESSCMS0354.eemea.ericsson.se> <FF84A09F50A6DC48ACB6714F4666CC743C572E0E50@ESESSCMS0354.eemea.ericsson.se> <FF84A09F50A6DC48ACB6714F4666CC743C5731447B@ESESSCMS0354.eemea.ericsson.se>, <2FB3BD82-1903-43BA-AA30-FD9F179917AE@estacado.net>
In-Reply-To: <2FB3BD82-1903-43BA-AA30-FD9F179917AE@estacado.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] WGLC MSRP ACM Security Considerations [was: RE: WGLC of msrp-acm and msrp-sessionmatch - Ben's comments]
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 21:57:29 -0000

Hi,

Your text looks ok, but let's get back to this one once we've figured out w=
hether we need to reference 4572 or not (see other thread).

Regards,

Christer

________________________________________
From: Ben Campbell [ben@estacado.net]
Sent: Tuesday, February 02, 2010 11:25 PM
To: Christer Holmberg
Cc: Simple WG
Subject: Re: [Simple] WGLC MSRP ACM Security Considerations [was: RE: WGLC =
of msrp-acm and msrp-sessionmatch - Ben's comments]

On Jan 26, 2010, at 3:19 AM, Christer Holmberg wrote:

>
> What about the following text?
>
> ---------
>
> According to the connection model defined in [RFC4975], the MSRP UA which=
 sends the SDP offer is the "active", ", and it is responsible for creating=
 the MSRP transport
> connection towards the remote UA if a new connection is required. The "ac=
tive" UA also takes the role as TLS client, if TLS is used to protect the M=
SRP messages.
>
> When COMEDIA is used, either the sender or the receiver of the SDP offer =
can become "active", and therefor also take the role as TLS client. However=
, there are no procedures in
> [RFC4975] that would break in case the receiver of the SDP offerer takes =
the role as TLS client, and the level of security provided by TLS is not af=
fected."

I think that's a good start. I propose adding the following sentence betwee=
n the first and second sentence of your second paragraph:

"The TLS client is responsible for matching the server's certificate to the=
 peer's MSRP URI regardless of whether the it acted as the SDP offerer or a=
nswerer."

I also suggest this additional paragraph, either before or after the TLS pa=
rts:

"RFC 4975 requires the active party to immediately issue a SEND request onc=
e the connection is established. This allows the passive party to bind the =
inbound TCP connection to the message session identified by its MSRP URI. T=
he use of COMEDIA does not change this requirement. However, the active par=
ty is no longer assumed to be the SDP offerer. "

>
> ---------
>
> Regards,
>
> Christer
>
>
>
>> -----Original Message-----
>> From: simple-bounces@ietf.org
>> [mailto:simple-bounces@ietf.org] On Behalf Of Christer Holmberg
>> Sent: 25. tammikuuta 2010 15:45
>> To: Ben Campbell
>> Cc: Simple WG
>> Subject: [Simple] WGLC MSRP ACM Security Considerations [was:
>> RE: WGLC of msrp-acm and msrp-sessionmatch - Ben's comments]
>>
>>
>> Hi,
>>
>> Sorry, forgot to remove some text, in order to make it more clear.
>>
>>>> If we don't use COMEDIA-TLS, but simply refer to 4975 for
>> TLS, I guess there shouldn't be any issues. Or?
>>>>
>>> I think there may be some language in the security consideration
>>> section of 4975 concerning how you match the certificate to
>> the server
>>> that we need to check to make sure it does not contain assumptions
>>> about which party is client or server.
>>>
>>
>> I was reading the security considerations of 4975, and didn't
>> find any such assumptions.
>>
>> The text generally talks about sending the fingerprint in
>> SDP, but I can't find any specific assumptions.
>>
>> Regards,
>>
>> Christer
>> _______________________________________________
>> Simple mailing list
>> Simple@ietf.org
>> https://www.ietf.org/mailman/listinfo/simple
>>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple=

From ben@nostrum.com  Tue Feb  2 14:31:17 2010
Return-Path: <ben@nostrum.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD2E828C0E7 for <simple@core3.amsl.com>; Tue,  2 Feb 2010 14:31:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, SPF_PASS=-0.001]
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 HGeA7Y8jKsbG for <simple@core3.amsl.com>; Tue,  2 Feb 2010 14:31:16 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 36CC728C0D7 for <simple@ietf.org>; Tue,  2 Feb 2010 14:31:15 -0800 (PST)
Received: from dn3-175.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o12MVh1d059510 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Feb 2010 16:31:48 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC743C58377CE9@ESESSCMS0354.eemea.ericsson.se>
Date: Tue, 2 Feb 2010 16:31:41 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F06B5AFC-8E83-455D-96FC-7ACEC4493225@nostrum.com>
References: <FF84A09F50A6DC48ACB6714F4666CC743C57135FDB@ESESSCMS0354.eemea.ericsson.se>, <849B84C2-C30D-435F-A73F-AB84022838CE@nostrum.com> <FF84A09F50A6DC48ACB6714F4666CC743C58377CE9@ESESSCMS0354.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1077)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] MSRP ACM: Usage of COMEDIA-TLS needed after all?
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 22:31:17 -0000

<as individual>

On Feb 2, 2010, at 3:56 PM, Christer Holmberg wrote:

> Hi Ben,
>=20
>> Christer, can you point out the text in 4975 to which you refer? If =
you are talking about the last 3 paragraphs of section 14.4,
>=20
> Yes.
>=20
>> the point of this was not to specify that the offerer must send the =
fingerprint, but simply to show how RFC 4474 interacts with a =
fingerprint in the offer.
>>=20
>> In fact, that section talks about TLS in peer-to-peer mode--that is, =
mutual authentication with self-signed certs on both ends. In this case =
_both_ parties are likely to send fingerprints.
>=20
> Where is that specified?
>=20
> The beginning of the section does talk about sending fingerprints in =
SDP, but is it clear that both parties send it?
>=20

Well, it could certainly be more clear. But, the first sentence of the =
section says, "TLS can be used with a self-signed certificate as long as =
there is a mechanism for _both_ sides_ to ascertain that the other side =
used the correct certificate."  (emphasis added)

The rest of the section describes how an endpoint sends the information =
to do this for a self-signed cert. So I think it's reasonable to assume =
that each party that is providing a self-signed cert would send the =
fingerprint attribute.


>> In the case where one end uses a self-signed cert and the other uses =
a CA-signed cert, the party with the self-signed cert would need to send =
a fingerprint--regardless of which party was active.
>=20
> Correct. I am only talking about the case when both parties use self =
signed certs.
>=20
>> As far a reference to RFC 4572, my concern is that we don't =
accidentally institute a requirement to send fingerprints when using a =
CA-signed certificate, instead of a self-signed one. If I recall =
correctly, RFC 4572 assumes you are always using self-signed certs. If =
we do
>> reference it, we need to make sure we scope the reference to include =
"how fingerprints work" and not the "requirement to _always_ use a =
fingerprint".
>=20
> I don't think 4572 requires the usage of self-signed certs. It =
describes what you do (sending fingerprint) IF you use self-signed =
certs.

It presents itself as what you do if you want to use TLS on sessions =
established via SDP. And it specifically requires mutual authentication, =
and does not support a mode where one side is self-signed and the other =
is not. (Or at least, in that mode, it requires the device with a =
CA-signed cert to still send a fingerprint)

>=20
> But, we could add clarification text saying that the 4572 procedures =
are followed if the UA is using a self-signed cert.
>=20

That would probably be okay.

> However, IF 4975 already specifies that both endpoints include =
fingerprint attributes then I am not sure we need to refer to 4572. But, =
it is at least not very clear to me when reading 4975 :)

RFC 4975 Section 14.4, third paragraph, already says the endpoint MUST =
use the fingerprint attribute according to 4572. =46rom the context , I =
interpret this as meaning an endpoint that wants to authenticate itself =
with a self-signed cert must do this, but that is not explicit.

BTW, I fully agree that that section is vague in places, and unclear on =
what the normative language actually applies to. A clarification draft =
might be a good thing, but I don't think we want to add that baggage to =
the ACM draft this late in the process.

>=20
> Regards,
>=20
> Christer
>=20
>=20
>=20
>=20
>=20
> On Jan 29, 2010, at 5:23 AM, Christer Holmberg wrote:
>=20
>=20
> Hi,
>=20
> A while ago, it was agreed that we will not refer to COMEDIA-TLS in =
the ACM draft, based on the argument that the TLS procedures in 4975 =
already covers all we need.
>=20
> However, when reading the 4975 text we've spotted an issue with using =
only the 4975 TLS procedures in ACM:
>=20
> 4975 says that the "SDP offerer" provides the fingerprint. The text =
does NOT talk about the "active party" providing the fingerprint, which =
I guess is due to the 4975 definition that the SDP offerer is always the =
active party.
>=20
> But, when COMEDIA is used, the SDP answerer can become the active =
party. But, there is no text in 4975 about the SDP answerer providing =
the fingerprint.
>=20
> Now, there are two ways of solving this:
>=20
> 1. In ACM we specify that an SDP offer with active and actpass shall =
contain the fingerprint, and that an SDP answer with active shall =
contain the fingerprint.
>=20
> OR
>=20
> 2. In ACM we refer to the COMEDIA-TLS procedures, that species the =
usage of mutual authentication, which means both the SDP offer and SDP =
answer will always contain the fingerprint.
>=20
> My preference is option 2. Since we use COMEDIA, I think it is much =
more feasible to also use COMEDIA-TLS, instead of specifying new =
additional MSRP specific TLS procedures.
>=20
> So, if we go for option 2, I propose the following changes/additions =
to the ACM draft:
>=20
> ----------
>=20
> 4.3.  TLS
>=20
>   If MSRP UAs negotiate a TLS transport connection for MSRP, the Uas =
SHALL follow the procedures defined in [RFC4975]. The
>   active MSRP UA will take the role of the TLS client, and the passive =
UA will take the role of the TLS server.
>=20
> ----------
>=20
> 6.  Security Considerations
>=20
>   Use of the COMEDIA procedures changes the connection model described =
in RFC 4975 in that any MSRP endpoint might set up the TCP or
>   TCP/TLS connection, and not only the client sending the SDP offer.
>=20
>   TLS security is not compromised by this fact, since mutual =
authentication [RFC4572] is used - both endpoints provides certificate =
fingerprints
>   in SDP and certificates in TLS independent of if they are active or =
passive. The endpoint that receives the TLS connection can always verify =
the source
>   of the connection, independent of if the connection is set up from =
the SDP offerer or answerer.
>=20
> ----------
>=20
> If people are ok with this, I will add the text to the draft.
>=20
>=20
> Regards,
>=20
> Christer
>=20
>=20
> _______________________________________________
> Simple mailing list
> Simple@ietf.org<mailto:Simple@ietf.org>
> https://www.ietf.org/mailman/listinfo/simple
>=20


From ben@nostrum.com  Wed Feb  3 08:17:24 2010
Return-Path: <ben@nostrum.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD9E03A6C45 for <simple@core3.amsl.com>; Wed,  3 Feb 2010 08:17:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001]
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 JTk2rGRTpWlc for <simple@core3.amsl.com>; Wed,  3 Feb 2010 08:17:24 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id A720628C18C for <simple@ietf.org>; Wed,  3 Feb 2010 08:17:02 -0800 (PST)
Received: from dn3-175.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o13GHhPV042783 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <simple@ietf.org>; Wed, 3 Feb 2010 10:17:43 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Feb 2010 10:17:43 -0600
Message-Id: <DE0D5C0A-8F1A-4661-BFD7-124E63C436E1@nostrum.com>
To: Simple WG <simple@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1077)
X-Mailer: Apple Mail (2.1077)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Subject: [Simple] IETF77
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 16:17:24 -0000

<as-chair>

Given that most, if not all, of our chartered work items are winding =
down, the SIMPLE chairs do not plan to request meeting time at IETF77 in =
Anaheim. If you think we really do need to meet, please bring discussion =
to the SIMPLE list ASAP. The deadline for requesting a meeting slot is =
17:00 PST on Monday, 8 Feb.

Thanks!

Ben.



From christer.holmberg@ericsson.com  Wed Feb  3 11:41:51 2010
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B91728C0F9 for <simple@core3.amsl.com>; Wed,  3 Feb 2010 11:41:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level: 
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[AWL=-0.588, 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 DirAxp8TDetp for <simple@core3.amsl.com>; Wed,  3 Feb 2010 11:41:50 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id CFEED3A6A7F for <simple@ietf.org>; Wed,  3 Feb 2010 11:41:49 -0800 (PST)
X-AuditID: c1b4fb3d-b7b85ae00000097d-60-4b69d1a703d0
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id ED.A8.02429.7A1D96B4; Wed,  3 Feb 2010 20:42:32 +0100 (CET)
Received: from esessmw0191.eemea.ericsson.se (153.88.115.84) by esessmw0184.eemea.ericsson.se (153.88.115.83) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 3 Feb 2010 20:42:31 +0100
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.1.22]) by esessmw0191.eemea.ericsson.se ([10.2.3.60]) with mapi; Wed, 3 Feb 2010 20:42:31 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
Date: Wed, 3 Feb 2010 20:42:30 +0100
Thread-Topic: [Simple] MSRP ACM: Usage of COMEDIA-TLS needed after all?
Thread-Index: AcqkWAo01lhPNWglTdmQ+VAgfB1c5wAr5aix
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC743C58377CF6@ESESSCMS0354.eemea.ericsson.se>
References: <FF84A09F50A6DC48ACB6714F4666CC743C57135FDB@ESESSCMS0354.eemea.ericsson.se>, <849B84C2-C30D-435F-A73F-AB84022838CE@nostrum.com> <FF84A09F50A6DC48ACB6714F4666CC743C58377CE9@ESESSCMS0354.eemea.ericsson.se>, <F06B5AFC-8E83-455D-96FC-7ACEC4493225@nostrum.com>
In-Reply-To: <F06B5AFC-8E83-455D-96FC-7ACEC4493225@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] MSRP ACM: Usage of COMEDIA-TLS needed after all?
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 19:41:51 -0000

Hi,

>>>In fact, that section talks about TLS in peer-to-peer mode--that is, mut=
ual authentication with self-signed certs on both ends. In this case _both_=
 parties are likely to send fingerprints.
>>
>>Where is that specified?
>>
>>The beginning of the section does talk about sending fingerprints in SDP,=
 but is it clear that both parties send it?
>
>
>Well, it could certainly be more clear. But, the first sentence of the sec=
tion says, "TLS can be used with a self-signed certificate as long as there=
 is a mechanism for _both_ sides_ to ascertain that the other side used the=
 correct certificate."  (emphasis added)
>
>The rest of the section describes how an endpoint sends the information to=
 do this for a self-signed cert. So I think it's reasonable to assume that =
each party that is providing a self-signed cert would send the fingerprint =
attribute.
>
>>>In the case where one end uses a self-signed cert and the other uses a C=
A-signed cert, the party with the self-signed cert would need to send a fin=
gerprint--regardless of which party was active.
>>
>>Correct. I am only talking about the case when both parties use self sign=
ed certs.
>>
>>>As far a reference to RFC 4572, my concern is that we don't accidentally=
 institute a requirement to send fingerprints when using a CA-signed certif=
icate, instead of a self-signed one. If I recall correctly, RFC 4572 assume=
s you are always using self-signed certs. If we do
>>>reference it, we need to make sure we scope the reference to include "ho=
w fingerprints work" and not the "requirement to _always_ use a fingerprint=
".
>>
>>I don't think 4572 requires the usage of self-signed certs. It describes =
what you do (sending fingerprint) IF you use self-signed certs.
>
>It presents itself as what you do if you want to use TLS on sessions estab=
lished via SDP. And it specifically requires mutual authentication, and doe=
s not support a mode where one side is self-signed and the other is not. (O=
r at least, in that mode, it requires the device with a=20
>CA-signed cert to still send a fingerprint)
>
>>
>>But, we could add clarification text saying that the 4572 procedures are =
followed if the UA is using a self-signed cert.
>>
>
>That would probably be okay.
>
>>However, IF 4975 already specifies that both endpoints include fingerprin=
t attributes then I am not sure we need to refer to 4572. But, it is at lea=
st not very clear to me when reading 4975 :)
>
>RFC 4975 Section 14.4, third paragraph, already says the endpoint MUST use=
 the fingerprint attribute according to 4572. From the context , I interpre=
t this as meaning an endpoint that wants to authenticate itself with a self=
-signed cert must do this, but that is not explicit.
>
>BTW, I fully agree that that section is vague in places, and unclear on wh=
at the normative language actually applies to. A clarification draft might =
be a good thing, but I don't think we want to add that baggage to the ACM d=
raft this late in the process.

I agree, but if we choose to refer to the 4975 procedures we can at least m=
ake it clear in the ACM spec.

Regards,

Christer







> Hi,
>
> A while ago, it was agreed that we will not refer to COMEDIA-TLS in the A=
CM draft, based on the argument that the TLS procedures in 4975 already cov=
ers all we need.
>
> However, when reading the 4975 text we've spotted an issue with using onl=
y the 4975 TLS procedures in ACM:
>
> 4975 says that the "SDP offerer" provides the fingerprint. The text does =
NOT talk about the "active party" providing the fingerprint, which I guess =
is due to the 4975 definition that the SDP offerer is always the active par=
ty.
>
> But, when COMEDIA is used, the SDP answerer can become the active party. =
But, there is no text in 4975 about the SDP answerer providing the fingerpr=
int.
>
> Now, there are two ways of solving this:
>
> 1. In ACM we specify that an SDP offer with active and actpass shall cont=
ain the fingerprint, and that an SDP answer with active shall contain the f=
ingerprint.
>
> OR
>
> 2. In ACM we refer to the COMEDIA-TLS procedures, that species the usage =
of mutual authentication, which means both the SDP offer and SDP answer wil=
l always contain the fingerprint.
>
> My preference is option 2. Since we use COMEDIA, I think it is much more =
feasible to also use COMEDIA-TLS, instead of specifying new additional MSRP=
 specific TLS procedures.
>
> So, if we go for option 2, I propose the following changes/additions to t=
he ACM draft:
>
> ----------
>
> 4.3.  TLS
>
>   If MSRP UAs negotiate a TLS transport connection for MSRP, the Uas SHAL=
L follow the procedures defined in [RFC4975]. The
>   active MSRP UA will take the role of the TLS client, and the passive UA=
 will take the role of the TLS server.
>
> ----------
>
> 6.  Security Considerations
>
>   Use of the COMEDIA procedures changes the connection model described in=
 RFC 4975 in that any MSRP endpoint might set up the TCP or
>   TCP/TLS connection, and not only the client sending the SDP offer.
>
>   TLS security is not compromised by this fact, since mutual authenticati=
on [RFC4572] is used - both endpoints provides certificate fingerprints
>   in SDP and certificates in TLS independent of if they are active or pas=
sive. The endpoint that receives the TLS connection can always verify the s=
ource
>   of the connection, independent of if the connection is set up from the =
SDP offerer or answerer.
>
> ----------
>
> If people are ok with this, I will add the text to the draft.
>
>
> Regards,
>
> Christer
>
>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org<mailto:Simple@ietf.org>
> https://www.ietf.org/mailman/listinfo/simple
>=

From ben@nostrum.com  Wed Feb  3 12:41:42 2010
Return-Path: <ben@nostrum.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5241528C1B2 for <simple@core3.amsl.com>; Wed,  3 Feb 2010 12:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001]
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 TIT1S91r9jMS for <simple@core3.amsl.com>; Wed,  3 Feb 2010 12:41:41 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 268AB28C18B for <simple@ietf.org>; Wed,  3 Feb 2010 12:41:40 -0800 (PST)
Received: from dn3-175.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o13KgKjO063864 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 3 Feb 2010 14:42:20 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC743C58377CF6@ESESSCMS0354.eemea.ericsson.se>
Date: Wed, 3 Feb 2010 14:42:19 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <61647E24-3CCD-44C6-BFCC-0397506F280B@nostrum.com>
References: <FF84A09F50A6DC48ACB6714F4666CC743C57135FDB@ESESSCMS0354.eemea.ericsson.se>, <849B84C2-C30D-435F-A73F-AB84022838CE@nostrum.com> <FF84A09F50A6DC48ACB6714F4666CC743C58377CE9@ESESSCMS0354.eemea.ericsson.se>, <F06B5AFC-8E83-455D-96FC-7ACEC4493225@nostrum.com> <FF84A09F50A6DC48ACB6714F4666CC743C58377CF6@ESESSCMS0354.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1077)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] MSRP ACM: Usage of COMEDIA-TLS needed after all?
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 20:41:42 -0000

On Feb 3, 2010, at 1:42 PM, Christer Holmberg wrote:

>> RFC 4975 Section 14.4, third paragraph, already says the endpoint =
MUST use the fingerprint attribute according to 4572. =46rom the context =
, I interpret this as meaning an endpoint that wants to authenticate =
itself with a self-signed cert must do this, but that is not explicit.
>>=20
>> BTW, I fully agree that that section is vague in places, and unclear =
on what the normative language actually applies to. A clarification =
draft might be a good thing, but I don't think we want to add that =
baggage to the ACM draft this late in the process.
>=20
> I agree, but if we choose to refer to the 4975 procedures we can at =
least make it clear in the ACM spec.
>=20

Okay, I guess it's reasonable to add something to the effect of "If =
either endpoint wishes to use a self-signed TLS certificate to =
authenticate itself to its peer, it MUST include the certificate =
fingerprint in a fingerprint attribute as described in RFC 4975. This is =
true whether for both the active and passive party.=20

Do we need to say something about the TLS server requesting a =
client-cert if the peer provided a fingerprint?=20

We also might want a disclaimer that this only applies for peer-to-peer =
MSRP. If MSRP relays are present, they will not see the SDP payloads, =
and therefore not see the fingerprint. This limits them to using =
CA-certified certs. A client of the relay will authenticate with the =
AUTH method. A peer connecting to the relay would merely need to prove =
it had possession of the correct session URI by presenting it in the =
To-Path header field of an initial SEND request.=

From ibc@aliax.net  Mon Feb  8 10:16:29 2010
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67E343A746A for <simple@core3.amsl.com>; Mon,  8 Feb 2010 10:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 R34hB+YF9W+E for <simple@core3.amsl.com>; Mon,  8 Feb 2010 10:16:28 -0800 (PST)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 0A0C63A7463 for <simple@ietf.org>; Mon,  8 Feb 2010 10:16:27 -0800 (PST)
Received: by ewy28 with SMTP id 28so2830327ewy.28 for <simple@ietf.org>; Mon, 08 Feb 2010 10:17:27 -0800 (PST)
Received: by 10.213.66.5 with SMTP id l5mr4114036ebi.15.1265653044922; Mon, 08 Feb 2010 10:17:24 -0800 (PST)
Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 7sm12170870eyb.34.2010.02.08.10.17.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Feb 2010 10:17:23 -0800 (PST)
From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: simple@ietf.org
Date: Mon, 8 Feb 2010 19:17:19 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; )
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201002081917.19213.ibc@aliax.net>
Subject: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 18:16:29 -0000

Hi, I've already complained against the design of XCAP protocol and got good
responses and explanations from this maillist. I appreciate them, however I
would like to complain again:


XCAP reuses Xpath 1.0 by including some restrictions (for example a Xpath
result cannot be multiple nodes, but just one). Ok, no problem, by adding s=
ome
extra-logic I can implement such restrictions in my XCAP server (which reus=
es
an existing XML library supporting Xpath 1.0).

The problem is that XCAP also adds some "features" to the original Xpath 1.0
making it incompatible with existing Xpath libraries. I mean the "default
document namespace" feature.


Let's suppose a resource-list document as follows:

=2D--------------------------------------------------
<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<resource-lists xmlns=3D"urn:ietf:params:xml:ns:resource-lists">

  <list name=3D"oma_buddylist">
    <external anchor=3D"http://xcap.example.org/resource-lists/users/sip:jo=
e@example.org/index/~~/resource-lists/list%5B@name=3D%22list-a%22%5D"/>
  </list>

  <list name=3D"list-a">
    <display-name>My Golf Team</display-name>
    <entry uri=3D"sip:bob@example.com" />
    <entry uri=3D"sip:bert@example.com" />
  </list>

</resource-lists>
=2D--------------------------------------------------


So the client inspects the list "oma_buddylist" and gets
"http://xcap.example.org/resource-lists/users/sip:joe@example.org/index/~~/=
resource-lists/list%5B@name=3D%22list-a%22%5D"
which points to another list "list-a" within the same document.

Then the client extracts the Xpath expression:

  "/resource-lists/list%5B@name=3D%22list-a%22%5D"

And now the client must use Xpath to get such list. Unfortunatelly the exis=
ting Xpath
expression is not a valid "Xpath 1.0 expression": there are no node prefixes
and the document includes a default namespace "urn:ietf:params:xml:ns:resou=
rce-lists"
for all the nodes.

So the client must do a dirty hack and transform the Xpath expression to so=
mething
like this:

  "/ns:resource-lists/ns:list%5B@name=3D%22list-a%22%5D"

Then the client can use its favourite XML/Xpath1.0 library:

  list_a =3D xpath(
    document,
    '/ns:resource-lists/ns:list[@name=3D"list-a"]',
    {"ns" =3D> "urn:ietf:params:xml:ns:resource-lists"}
  )


This is a really dirty hack as the client must parse and transform the exis=
ting Xpath
expression by itself before using it within its XML/Xpath library.
The same occurs in server side.


So, what's the benefit of the XCAP added feature "default document namespac=
e"?
Just "saving bandwith". Ok, let's check it:

a) Using pure Xpath 1.0 specifications:

  GET /resource-lists/users/sip:alice@example.org/index/~~/ns:resource-list=
s/ns:list%5B@name=3D%22list-a%22%5D?xmlns(ns=3D"urn:ietf:params:xml:ns:reso=
urce-lists)" HTTP/1.1

b) Using the XCAP "cool" feature (default document namespace):

  GET /resource-lists/users/sip:alice@example.org/index/~~/resource-lists/l=
ist%5B@name=3D%22list-a%22%5D HTTP/1.1


So using case b) we have saved 56 bytes, is it really a so nice benefit?
And the only price we've payed for such increible benefit is the fact that =
we
*cannot* use any *existing* XML/Xpath1.0 library. Instead we must code our =
own
pseudo-Xpath library implementing the XCAP "additions", so cool...


I don't know if IETF (and more specifically the SIMPLE group) asks itself w=
hy
nobody wants to implement SIP rich presence and XCAP. There you have a good
example. It seems that all these specifications are intented for vendors/op=
erators,
companies which can pay developers to code a XCAP aware Xpath library (not =
compatible
with Xpath 1.0 specification).


I've talked about this issue with a member of the W3C XML Core Working Grou=
p, also
a developer of a very famous XML library. Here his responses when I explain=
ed him
the XCAP vs Xpath1.0 issue:

> Sorry, that's not XPath behaviour, and not possible with XXXXXXX which
> implements XPath. I'm very surprized that such a deviation from a W3C
> standard was allowed in an IETF specification, there used to be liaison
> between W3C and IETF to avoid this kind of problems.


Then I told him about the "benefit" of XCAP ("saving bandwidth"). His respo=
nse:

> Very misplaced attempt at optimizing. Note that HTTP is itself
> extremely verbose compared to a binary protocol, but hint hint it's
> the protocol which prevailed ! The XCAP authors didn't even managed to
> learn the lesson from the very protocol they are using.



So we end with XCAP, a specification which forces us to code a pseudo-XML/X=
path
parser from scrath as the specification is not compatible with those
published by the W3C organization.
It seems that Xpath2.0 allows the concept of "application default namespace"
(as XCAP), but I consider unappropriate to require a Xpath2.0 library just =
to
save 56 bytes (most of the available XML libraries implement Xpath 1.0 rath=
er
than 2.0).


Best regards.



=2D-=20
I=C3=B1aki Baz Castillo <ibc@aliax.net>

From emmartins@gmail.com  Mon Feb  8 10:39:02 2010
Return-Path: <emmartins@gmail.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99D363A6AD0 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 10:39:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 wbtZqjNkCNhK for <simple@core3.amsl.com>; Mon,  8 Feb 2010 10:39:01 -0800 (PST)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 3F7163A6991 for <simple@ietf.org>; Mon,  8 Feb 2010 10:39:01 -0800 (PST)
Received: by ewy28 with SMTP id 28so2857933ewy.28 for <simple@ietf.org>; Mon, 08 Feb 2010 10:40:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vLI3qMaXjrDyyD2v1sfAeaRqZ9Yw/VG4IPDaQSvxg6I=; b=ESrM4OUfwexhMwA8AX0t2Q+UPpD/1tCMOXzJLJvS1qiylGoxYqAyXhReplcgNUn1Jc UgQn/J6IIq9s6xA+EXWXVwcqltP8l4SAHEj2xUxEhwcDW1J4aFQPsFruSlY8awqy6Bhh 3d0OetoELclwY1vkZPSmGa09/biZ9tRJPaJ+E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mP0o06of0LJPOP4uH0FaaGfMfuW9YSGAM5G9OlWZUz6E/0JBNvcnuoPXPHHefNXkfQ 0O/EMplnCUeMwAUBkS9Suj2nuseUf2wJTVSu9hUZ+nX9sb7+wWsbBDzk1yZYPCpa5Arg DxAU5qjKB0Wv+wpx/fyEQOu3zJoX+E/ADlHgc=
MIME-Version: 1.0
Received: by 10.216.88.195 with SMTP id a45mr491846wef.63.1265654399828; Mon,  08 Feb 2010 10:39:59 -0800 (PST)
In-Reply-To: <201002081917.19213.ibc@aliax.net>
References: <201002081917.19213.ibc@aliax.net>
Date: Mon, 8 Feb 2010 18:39:59 +0000
Message-ID: <c128d1a11002081039p1aec458csbb96f5b16a0f76d0@mail.gmail.com>
From: Eduardo Martins <emmartins@gmail.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: simple@ietf.org
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 18:39:02 -0000

What code language you are using?

-- Eduardo

-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
http://emmartins.blogspot.com
http://www.redhat.com/solutions/telco

On Mon, Feb 8, 2010 at 6:17 PM, I=F1aki Baz Castillo <ibc@aliax.net> wrote:
> Hi, I've already complained against the design of XCAP protocol and got g=
ood
> responses and explanations from this maillist. I appreciate them, however=
 I
> would like to complain again:
>
>
> XCAP reuses Xpath 1.0 by including some restrictions (for example a Xpath
> result cannot be multiple nodes, but just one). Ok, no problem, by adding=
 some
> extra-logic I can implement such restrictions in my XCAP server (which re=
uses
> an existing XML library supporting Xpath 1.0).
>
> The problem is that XCAP also adds some "features" to the original Xpath =
1.0
> making it incompatible with existing Xpath libraries. I mean the "default
> document namespace" feature.
>
>
> Let's suppose a resource-list document as follows:
>
> ---------------------------------------------------
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <resource-lists xmlns=3D"urn:ietf:params:xml:ns:resource-lists">
>
> =A0<list name=3D"oma_buddylist">
> =A0 =A0<external anchor=3D"http://xcap.example.org/resource-lists/users/s=
ip:joe@example.org/index/~~/resource-lists/list%5B@name=3D%22list-a%22%5D"/=
>
> =A0</list>
>
> =A0<list name=3D"list-a">
> =A0 =A0<display-name>My Golf Team</display-name>
> =A0 =A0<entry uri=3D"sip:bob@example.com" />
> =A0 =A0<entry uri=3D"sip:bert@example.com" />
> =A0</list>
>
> </resource-lists>
> ---------------------------------------------------
>
>
> So the client inspects the list "oma_buddylist" and gets
> "http://xcap.example.org/resource-lists/users/sip:joe@example.org/index/~=
~/resource-lists/list%5B@name=3D%22list-a%22%5D"
> which points to another list "list-a" within the same document.
>
> Then the client extracts the Xpath expression:
>
> =A0"/resource-lists/list%5B@name=3D%22list-a%22%5D"
>
> And now the client must use Xpath to get such list. Unfortunatelly the ex=
isting Xpath
> expression is not a valid "Xpath 1.0 expression": there are no node prefi=
xes
> and the document includes a default namespace "urn:ietf:params:xml:ns:res=
ource-lists"
> for all the nodes.
>
> So the client must do a dirty hack and transform the Xpath expression to =
something
> like this:
>
> =A0"/ns:resource-lists/ns:list%5B@name=3D%22list-a%22%5D"
>
> Then the client can use its favourite XML/Xpath1.0 library:
>
> =A0list_a =3D xpath(
> =A0 =A0document,
> =A0 =A0'/ns:resource-lists/ns:list[@name=3D"list-a"]',
> =A0 =A0{"ns" =3D> "urn:ietf:params:xml:ns:resource-lists"}
> =A0)
>
>
> This is a really dirty hack as the client must parse and transform the ex=
isting Xpath
> expression by itself before using it within its XML/Xpath library.
> The same occurs in server side.
>
>
> So, what's the benefit of the XCAP added feature "default document namesp=
ace"?
> Just "saving bandwith". Ok, let's check it:
>
> a) Using pure Xpath 1.0 specifications:
>
> =A0GET /resource-lists/users/sip:alice@example.org/index/~~/ns:resource-l=
ists/ns:list%5B@name=3D%22list-a%22%5D?xmlns(ns=3D"urn:ietf:params:xml:ns:r=
esource-lists)" HTTP/1.1
>
> b) Using the XCAP "cool" feature (default document namespace):
>
> =A0GET /resource-lists/users/sip:alice@example.org/index/~~/resource-list=
s/list%5B@name=3D%22list-a%22%5D HTTP/1.1
>
>
> So using case b) we have saved 56 bytes, is it really a so nice benefit?
> And the only price we've payed for such increible benefit is the fact tha=
t we
> *cannot* use any *existing* XML/Xpath1.0 library. Instead we must code ou=
r own
> pseudo-Xpath library implementing the XCAP "additions", so cool...
>
>
> I don't know if IETF (and more specifically the SIMPLE group) asks itself=
 why
> nobody wants to implement SIP rich presence and XCAP. There you have a go=
od
> example. It seems that all these specifications are intented for vendors/=
operators,
> companies which can pay developers to code a XCAP aware Xpath library (no=
t compatible
> with Xpath 1.0 specification).
>
>
> I've talked about this issue with a member of the W3C XML Core Working Gr=
oup, also
> a developer of a very famous XML library. Here his responses when I expla=
ined him
> the XCAP vs Xpath1.0 issue:
>
>> Sorry, that's not XPath behaviour, and not possible with XXXXXXX which
>> implements XPath. I'm very surprized that such a deviation from a W3C
>> standard was allowed in an IETF specification, there used to be liaison
>> between W3C and IETF to avoid this kind of problems.
>
>
> Then I told him about the "benefit" of XCAP ("saving bandwidth"). His res=
ponse:
>
>> Very misplaced attempt at optimizing. Note that HTTP is itself
>> extremely verbose compared to a binary protocol, but hint hint it's
>> the protocol which prevailed ! The XCAP authors didn't even managed to
>> learn the lesson from the very protocol they are using.
>
>
>
> So we end with XCAP, a specification which forces us to code a pseudo-XML=
/Xpath
> parser from scrath as the specification is not compatible with those
> published by the W3C organization.
> It seems that Xpath2.0 allows the concept of "application default namespa=
ce"
> (as XCAP), but I consider unappropriate to require a Xpath2.0 library jus=
t to
> save 56 bytes (most of the available XML libraries implement Xpath 1.0 ra=
ther
> than 2.0).
>
>
> Best regards.
>
>
>
> --
> I=F1aki Baz Castillo <ibc@aliax.net>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple
>

From ibc@aliax.net  Mon Feb  8 10:45:24 2010
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BC6028C164 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 10:45:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.049
X-Spam-Level: 
X-Spam-Status: No, score=-1.049 tagged_above=-999 required=5 tests=[AWL=-1.250, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5]
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 cEwehNwnCMrk for <simple@core3.amsl.com>; Mon,  8 Feb 2010 10:45:23 -0800 (PST)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by core3.amsl.com (Postfix) with ESMTP id BA22728C153 for <simple@ietf.org>; Mon,  8 Feb 2010 10:45:22 -0800 (PST)
Received: by ey-out-2122.google.com with SMTP id 22so1533198eye.51 for <simple@ietf.org>; Mon, 08 Feb 2010 10:46:22 -0800 (PST)
Received: by 10.213.1.214 with SMTP id 22mr4343102ebg.16.1265654782389; Mon, 08 Feb 2010 10:46:22 -0800 (PST)
Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 5sm5902101eyf.4.2010.02.08.10.46.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Feb 2010 10:46:21 -0800 (PST)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: simple@ietf.org
Date: Mon, 8 Feb 2010 19:46:17 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; )
References: <201002081917.19213.ibc@aliax.net> <c128d1a11002081039p1aec458csbb96f5b16a0f76d0@mail.gmail.com>
In-Reply-To: <c128d1a11002081039p1aec458csbb96f5b16a0f76d0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201002081946.18031.ibc@aliax.net>
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 18:45:24 -0000

El Lunes, 8 de Febrero de 2010, Eduardo Martins escribi=F3:
> What code language you are using?

Does it matter? Well, I'm using Ruby with a XMl library (Nokogiri [*]) whic=
h=20
is a LibXML2 wrapper.


[*] http://nokogiri.org/=20


=2D-=20
I=F1aki Baz Castillo <ibc@aliax.net>

From emmartins@gmail.com  Mon Feb  8 11:23:43 2010
Return-Path: <emmartins@gmail.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F4A43A73FA for <simple@core3.amsl.com>; Mon,  8 Feb 2010 11:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.201
X-Spam-Level: 
X-Spam-Status: No, score=0.201 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5]
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 rWO9nE5MXNwx for <simple@core3.amsl.com>; Mon,  8 Feb 2010 11:23:42 -0800 (PST)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by core3.amsl.com (Postfix) with ESMTP id 475443A7265 for <simple@ietf.org>; Mon,  8 Feb 2010 11:23:42 -0800 (PST)
Received: by ey-out-2122.google.com with SMTP id 22so1542476eye.51 for <simple@ietf.org>; Mon, 08 Feb 2010 11:24:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Nyu2TwLHRdiwD27kr4/2sp4P1ZH+h1OJWm6vT9nX0p4=; b=Ed2n7w+zOkjBuJosyKlmYSGS2F19DU9DGuLuea1qmCYQfPPrvYFyrTRs5oNg3YBQHo Jdf/mJdkU2+NFvHgolwJE7u4o3nEIQMCANhIUL4gGm7S3xlYx5/7A8ivb35TKrlKQTIx nRuI/k40OCzszQAN9j4xwdoxwjYOBER2gQEFQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=HjNVgAGZMgmwR5chiusBYnc60HuxZ4hcA43Ek+pZgT4Aukx5Coi1caL0sD1XjqpMxA bndjVglN98CwfhHe7Zz1QHd6GiqchHmUefWj6+LaTwsdTI0i0k71NHKV4QK9/WaKvb35 zhAagCLykGQtTig9jexzVpxmX+QSmE4SU8Q0Q=
MIME-Version: 1.0
Received: by 10.216.90.210 with SMTP id e60mr2433005wef.120.1265657082157;  Mon, 08 Feb 2010 11:24:42 -0800 (PST)
In-Reply-To: <201002081946.18031.ibc@aliax.net>
References: <201002081917.19213.ibc@aliax.net> <c128d1a11002081039p1aec458csbb96f5b16a0f76d0@mail.gmail.com> <201002081946.18031.ibc@aliax.net>
Date: Mon, 8 Feb 2010 19:24:42 +0000
Message-ID: <c128d1a11002081124i42b2868bh62a08d3641e64231@mail.gmail.com>
From: Eduardo Martins <emmartins@gmail.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: simple@ietf.org
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 19:23:43 -0000

It doesn't matter, but could make your life easier by proposing API x
or y, but no luck regarding Ruby.

-- Eduardo

-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
http://emmartins.blogspot.com
http://www.redhat.com/solutions/telco



On Mon, Feb 8, 2010 at 6:46 PM, I=F1aki Baz Castillo <ibc@aliax.net> wrote:
> El Lunes, 8 de Febrero de 2010, Eduardo Martins escribi=F3:
>> What code language you are using?
>
> Does it matter? Well, I'm using Ruby with a XMl library (Nokogiri [*]) wh=
ich
> is a LibXML2 wrapper.
>
>
> [*] http://nokogiri.org/
>
>
> --
> I=F1aki Baz Castillo <ibc@aliax.net>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple
>

From ibc@aliax.net  Mon Feb  8 11:54:20 2010
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B9953A70D4 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 11:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.674
X-Spam-Level: 
X-Spam-Status: No, score=-1.674 tagged_above=-999 required=5 tests=[AWL=0.625,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 ZBxfEx3FtH0c for <simple@core3.amsl.com>; Mon,  8 Feb 2010 11:54:19 -0800 (PST)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 747153A70BE for <simple@ietf.org>; Mon,  8 Feb 2010 11:54:19 -0800 (PST)
Received: by ewy28 with SMTP id 28so2948822ewy.28 for <simple@ietf.org>; Mon, 08 Feb 2010 11:55:18 -0800 (PST)
Received: by 10.213.100.160 with SMTP id y32mr147369ebn.49.1265658916928; Mon, 08 Feb 2010 11:55:16 -0800 (PST)
Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 23sm12622425eya.43.2010.02.08.11.55.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Feb 2010 11:55:15 -0800 (PST)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: simple@ietf.org
Date: Mon, 8 Feb 2010 20:55:11 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; )
References: <201002081917.19213.ibc@aliax.net> <201002081946.18031.ibc@aliax.net> <c128d1a11002081124i42b2868bh62a08d3641e64231@mail.gmail.com>
In-Reply-To: <c128d1a11002081124i42b2868bh62a08d3641e64231@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201002082055.11408.ibc@aliax.net>
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 19:54:20 -0000

El Lunes, 8 de Febrero de 2010, Eduardo Martins escribi=F3:
> It doesn't matter, but could make your life easier by proposing API x
> or y, but no luck regarding Ruby.

Thanks. I suspect you could point to some Java XML library implementing Xpa=
th=20
2.0, something perhaps implemented in Movicents.

However I don't want to use Movicents because it violates the GPL license: =
it=20
claims to be GPL but doesn't let to use commercial usage of it (for that=20
paying for other kind of license is required, something which violates the =
GPL=20
terms).

Regards.

=2D-=20
I=F1aki Baz Castillo <ibc@aliax.net>

From ibc@aliax.net  Mon Feb  8 11:54:48 2010
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C17F928C101 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 11:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.674
X-Spam-Level: 
X-Spam-Status: No, score=-1.674 tagged_above=-999 required=5 tests=[AWL=0.625,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 hHBc7RowwOxX for <simple@core3.amsl.com>; Mon,  8 Feb 2010 11:54:48 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 6767B3A70BE for <simple@ietf.org>; Mon,  8 Feb 2010 11:54:48 -0800 (PST)
Received: by wwa36 with SMTP id 36so1774636wwa.31 for <simple@ietf.org>; Mon, 08 Feb 2010 11:55:46 -0800 (PST)
Received: by 10.216.85.78 with SMTP id t56mr378625wee.223.1265658946251; Mon, 08 Feb 2010 11:55:46 -0800 (PST)
Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 5sm6097990eyf.2.2010.02.08.11.55.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Feb 2010 11:55:45 -0800 (PST)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: simple@ietf.org
Date: Mon, 8 Feb 2010 20:55:11 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; )
References: <201002081917.19213.ibc@aliax.net> <201002081946.18031.ibc@aliax.net> <c128d1a11002081124i42b2868bh62a08d3641e64231@mail.gmail.com>
In-Reply-To: <c128d1a11002081124i42b2868bh62a08d3641e64231@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201002082055.11408.ibc@aliax.net>
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 19:54:48 -0000

El Lunes, 8 de Febrero de 2010, Eduardo Martins escribi=F3:
> It doesn't matter, but could make your life easier by proposing API x
> or y, but no luck regarding Ruby.

Thanks. I suspect you could point to some Java XML library implementing Xpa=
th=20
2.0, something perhaps implemented in Movicents.

However I don't want to use Movicents because it violates the GPL license: =
it=20
claims to be GPL but doesn't let to use commercial usage of it (for that=20
paying for other kind of license is required, something which violates the =
GPL=20
terms).

Regards.

=2D-=20
I=F1aki Baz Castillo <ibc@aliax.net>

From emmartins@gmail.com  Mon Feb  8 16:27:48 2010
Return-Path: <emmartins@gmail.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F24C83A6E02 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 16:27:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 cptvh1-Ac-JE for <simple@core3.amsl.com>; Mon,  8 Feb 2010 16:27:48 -0800 (PST)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id ED5C53A6868 for <simple@ietf.org>; Mon,  8 Feb 2010 16:27:47 -0800 (PST)
Received: by ewy28 with SMTP id 28so3250789ewy.28 for <simple@ietf.org>; Mon, 08 Feb 2010 16:28:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xUTRAGMyJgOsX3UFFNrYfi+Cs2YoRFZXnVyhWj/Zkf0=; b=sR+Jy1oVYZxD6WypTxU3o+35aAZTr8GyamyiqNkvm2MskD8bbaIKYnNZHGBfdHgE8Z tHSU5vPjWL0d2wf39W4Hk/ZHW5kIPYpppAkXUcAbkw19h51mgkfEoQRIs+5qKzJZBBOH ZSOUfJPthEg1j15mTZCvq0YDivSHXJDOfmv5Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Wh6/eYFJ/ZzkvOguYYixEPehKjrcsIjDYElcyKFA0nHD3xt/qrsgJeD0H9eYapg+YQ //asmVICsMhA09l7USXF/aEKL0S3FxJbp0v0IsWRTgcr9LIqyMRJ4sQAI4uIWYe0R+yv MwWVLxJq4ptiKWjXJOaLNHT39Tpu7+nXUE0EI=
MIME-Version: 1.0
Received: by 10.216.89.85 with SMTP id b63mr2443071wef.175.1265675326716; Mon,  08 Feb 2010 16:28:46 -0800 (PST)
In-Reply-To: <201002082055.11408.ibc@aliax.net>
References: <201002081917.19213.ibc@aliax.net> <201002081946.18031.ibc@aliax.net> <c128d1a11002081124i42b2868bh62a08d3641e64231@mail.gmail.com> <201002082055.11408.ibc@aliax.net>
Date: Tue, 9 Feb 2010 00:28:46 +0000
Message-ID: <c128d1a11002081628s69261eb4v411bc2b6f4bde176@mail.gmail.com>
From: Eduardo Martins <emmartins@gmail.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: simple@ietf.org
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 00:27:49 -0000

Actually the whole Mobicents Platform nowadays uses LGPL, you can do
whatever you want with it. Red Hat or JBoss business never was selling
software.

As for the API used by the XDM Server on this matter, it is nothing
more then the javax.xml.xpath standard one in Java SE 5.0 or later,
but it involves a couple tricks:

1) Add a special NamespaceContext where the empty element prefix
points to the default document namespace
2) Prefix all elements in the path without prefix with empty prefix.

-- Eduardo

-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
http://emmartins.blogspot.com
http://www.redhat.com/solutions/telco

On Mon, Feb 8, 2010 at 7:55 PM, I=F1aki Baz Castillo <ibc@aliax.net> wrote:
> El Lunes, 8 de Febrero de 2010, Eduardo Martins escribi=F3:
>> It doesn't matter, but could make your life easier by proposing API x
>> or y, but no luck regarding Ruby.
>
> Thanks. I suspect you could point to some Java XML library implementing X=
path
> 2.0, something perhaps implemented in Movicents.
>
> However I don't want to use Movicents because it violates the GPL license=
: it
> claims to be GPL but doesn't let to use commercial usage of it (for that
> paying for other kind of license is required, something which violates th=
e GPL
> terms).
>
> Regards.
>
> --
> I=F1aki Baz Castillo <ibc@aliax.net>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple
>

From ibc@aliax.net  Mon Feb  8 16:38:36 2010
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A908E3A6F50 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 16:38:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.882
X-Spam-Level: 
X-Spam-Status: No, score=-1.882 tagged_above=-999 required=5 tests=[AWL=0.417,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 KXPTPEar4IXS for <simple@core3.amsl.com>; Mon,  8 Feb 2010 16:38:36 -0800 (PST)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id B142F3A69A0 for <simple@ietf.org>; Mon,  8 Feb 2010 16:38:35 -0800 (PST)
Received: by ewy28 with SMTP id 28so3258334ewy.28 for <simple@ietf.org>; Mon, 08 Feb 2010 16:39:36 -0800 (PST)
Received: by 10.213.100.139 with SMTP id y11mr2313368ebn.1.1265675976489; Mon, 08 Feb 2010 16:39:36 -0800 (PST)
Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 5sm13005036eyh.8.2010.02.08.16.39.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Feb 2010 16:39:35 -0800 (PST)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: simple@ietf.org
Date: Tue, 9 Feb 2010 01:39:31 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; )
References: <201002081917.19213.ibc@aliax.net> <201002082055.11408.ibc@aliax.net> <c128d1a11002081628s69261eb4v411bc2b6f4bde176@mail.gmail.com>
In-Reply-To: <c128d1a11002081628s69261eb4v411bc2b6f4bde176@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201002090139.31545.ibc@aliax.net>
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 00:38:36 -0000

El Martes, 9 de Febrero de 2010, Eduardo Martins escribi=F3:
> Actually the whole Mobicents Platform nowadays uses LGPL, you can do
> whatever you want with it. Red Hat or JBoss business never was selling
> software.

Has this changed recently? Some months ago (~6) I got a reply from a Red Ha=
t=20
person involved in Mobicents telling me that the Mobicents license=20
(theorically GPL) doesn't allow me to use to provide commercial sevice.


> As for the API used by the XDM Server on this matter, it is nothing
> more then the javax.xml.xpath standard one in Java SE 5.0 or later,
> but it involves a couple tricks:
>=20
> 1) Add a special NamespaceContext where the empty element prefix
> points to the default document namespace
> 2) Prefix all elements in the path without prefix with empty prefix.

I do a similar hack in my XCAP server. I parse the Xpath and add "dfns:" in=
=20
all the non  prefixed nodes, and later I use "dfns"=3D>AUID_DEFAULT_NAMESPA=
CE=20
before invoking the Xpath parser.

The problem is that clients need to implement the same "trick" in order to=
=20
parse <external> entries in the documents :(

Thanks a lot for your comments.


=2D-=20
I=F1aki Baz Castillo <ibc@aliax.net>

From ibc@aliax.net  Mon Feb  8 16:59:10 2010
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3A113A74EC for <simple@core3.amsl.com>; Mon,  8 Feb 2010 16:59:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level: 
X-Spam-Status: No, score=-1.987 tagged_above=-999 required=5 tests=[AWL=0.312,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 0vOJjEr53V03 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 16:59:10 -0800 (PST)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id ACE693A74EB for <simple@ietf.org>; Mon,  8 Feb 2010 16:59:09 -0800 (PST)
Received: by ewy28 with SMTP id 28so3272570ewy.28 for <simple@ietf.org>; Mon, 08 Feb 2010 17:00:12 -0800 (PST)
Received: by 10.213.110.2 with SMTP id l2mr2048884ebp.94.1265677212321; Mon, 08 Feb 2010 17:00:12 -0800 (PST)
Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 28sm8215618eyg.36.2010.02.08.17.00.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Feb 2010 17:00:10 -0800 (PST)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: simple@ietf.org
Date: Tue, 9 Feb 2010 02:00:07 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; )
References: <201002081917.19213.ibc@aliax.net> <c128d1a11002081628s69261eb4v411bc2b6f4bde176@mail.gmail.com> <201002090139.31545.ibc@aliax.net>
In-Reply-To: <201002090139.31545.ibc@aliax.net>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201002090200.07226.ibc@aliax.net>
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 00:59:10 -0000

El Martes, 9 de Febrero de 2010, I=F1aki Baz Castillo escribi=F3:
> > Actually the whole Mobicents Platform nowadays uses LGPL, you can do
> > whatever you want with it. Red Hat or JBoss business never was selling
> > software.
>=20
> Has this changed recently? Some months ago (~6) I got a reply from a Red
>  Hat  person involved in Mobicents telling me that the Mobicents license
>  (theorically GPL) doesn't allow me to use to provide commercial sevice.

Extracted from =20
http://www.mobicents.org/faq.html#What_license_is_Mobicents_distri

=2D----------------------
Mobicents is distributed under a flexible dual license policy. The default=
=20
distribution license is GNU General Public License (GPL), the most popular=
=20
=46ree Open Source Software (FOSS) license in the world. Users would consid=
er=20
purchasing a commercial license if they intend to redistribute Mobicents al=
ong=20
with proprietary code or offer a commercial onlince service based on=20
Mobicents. Other popular Open Source Products with similar licensing policy=
=20
include MySQL, Asterisk, and Java ME.
=2D----------------------

This is a violation of the GPL license as it says "Users would consider=20
purchasing a commercial license if they intend to redistribute Mobicents al=
ong=20
with proprietary code or ***offer a commercial onlince service based on=20
Mobicents***".

Also the examples of "similar licensing policy" mentioning MySQL, Asterisk,=
=20
and Java ME are wrong. I can take a GPL version of MySQL or Asterisk and of=
fer=20
a commercial online service.

So Mobicents license is not GPL as GPL does allow me to take the software,=
=20
build an online service and charge my clients for such service.

I also asked about it to FSF which allows with me after reading the softwar=
e=20
license and terms.

Please, if you are involved in the project take this into consideration. I=
=20
already told about this with other member of the project and got these=20
responses:

"Mobicents is distributed under the GPL umbrella license.
I am not a lawyer and cannot address the questions you raise regarding =20
the interpretation of the GPL license terms."

"You can use Mobicents to develop the service, but unless you open =20
source your code, you should deploy on a licensed JBCP instance."


This last response is a violation of the GPL license.


Thanks a lot.

=2D-=20
I=F1aki Baz Castillo <ibc@aliax.net>

From emmartins@gmail.com  Mon Feb  8 17:19:13 2010
Return-Path: <emmartins@gmail.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A7DC28C0E3 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 17:19:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.049
X-Spam-Level: 
X-Spam-Status: No, score=-1.049 tagged_above=-999 required=5 tests=[AWL=1.250,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 yMsVXaO0VUSI for <simple@core3.amsl.com>; Mon,  8 Feb 2010 17:19:11 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 6EF3F28C0D8 for <simple@ietf.org>; Mon,  8 Feb 2010 17:19:11 -0800 (PST)
Received: by wwa36 with SMTP id 36so1872564wwa.31 for <simple@ietf.org>; Mon, 08 Feb 2010 17:20:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=YsvBNk7Gczw1f7tMbgXeBwscrIuzoZ6Dk3miFOdW4YE=; b=QVjDsQWMTdqrhNR0Hwj1/++UKCvz6xBY/HtI9Dmeabrbtin4zP70tboYQ2UEYFT88v xPssFaWYYwZPj4a2WFM9NhBG1R/uWZfLloho1C3S9de18RYdB2c+E5wFays9IR8d3glE l3KZByuN8KThol1+KLWvHcOgdvTXBebPSR7dQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qS+gdnLY/1Tg0DoQS/TOVVT6TGqLBDGkncs3VHxKAv9pdCULRDSDRHYHqXmzOGzjbq fhTyweXUlGpfbrIUXuUBU86EPz0YBkRVtRIjDS8U4brKcbc4hUdMJhG2msoBMTkqnSYa 5aXYcFSG05cynaZ+U1LKXoDQz4eDWAeWMv7sA=
MIME-Version: 1.0
Received: by 10.216.171.138 with SMTP id r10mr3131842wel.153.1265678411042;  Mon, 08 Feb 2010 17:20:11 -0800 (PST)
In-Reply-To: <201002090200.07226.ibc@aliax.net>
References: <201002081917.19213.ibc@aliax.net> <c128d1a11002081628s69261eb4v411bc2b6f4bde176@mail.gmail.com> <201002090139.31545.ibc@aliax.net> <201002090200.07226.ibc@aliax.net>
Date: Tue, 9 Feb 2010 01:20:11 +0000
Message-ID: <c128d1a11002081720p697852e5gf327f75287ef94d7@mail.gmail.com>
From: Eduardo Martins <emmartins@gmail.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: simple@ietf.org
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 01:19:13 -0000

That faq entry is out of date and is misleading, thanks for the alert,
will be fixed. Anyway, as I said, currently all is LGPL.

-- Eduardo

-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
http://emmartins.blogspot.com
http://www.redhat.com/solutions/telco

On Tue, Feb 9, 2010 at 1:00 AM, I=F1aki Baz Castillo <ibc@aliax.net> wrote:
> El Martes, 9 de Febrero de 2010, I=F1aki Baz Castillo escribi=F3:
>> > Actually the whole Mobicents Platform nowadays uses LGPL, you can do
>> > whatever you want with it. Red Hat or JBoss business never was selling
>> > software.
>>
>> Has this changed recently? Some months ago (~6) I got a reply from a Red
>> =A0Hat =A0person involved in Mobicents telling me that the Mobicents lic=
ense
>> =A0(theorically GPL) doesn't allow me to use to provide commercial sevic=
e.
>
> Extracted from
> http://www.mobicents.org/faq.html#What_license_is_Mobicents_distri
>
> -----------------------
> Mobicents is distributed under a flexible dual license policy. The defaul=
t
> distribution license is GNU General Public License (GPL), the most popula=
r
> Free Open Source Software (FOSS) license in the world. Users would consid=
er
> purchasing a commercial license if they intend to redistribute Mobicents =
along
> with proprietary code or offer a commercial onlince service based on
> Mobicents. Other popular Open Source Products with similar licensing poli=
cy
> include MySQL, Asterisk, and Java ME.
> -----------------------
>
> This is a violation of the GPL license as it says "Users would consider
> purchasing a commercial license if they intend to redistribute Mobicents =
along
> with proprietary code or ***offer a commercial onlince service based on
> Mobicents***".
>
> Also the examples of "similar licensing policy" mentioning MySQL, Asteris=
k,
> and Java ME are wrong. I can take a GPL version of MySQL or Asterisk and =
offer
> a commercial online service.
>
> So Mobicents license is not GPL as GPL does allow me to take the software=
,
> build an online service and charge my clients for such service.
>
> I also asked about it to FSF which allows with me after reading the softw=
are
> license and terms.
>
> Please, if you are involved in the project take this into consideration. =
I
> already told about this with other member of the project and got these
> responses:
>
> "Mobicents is distributed under the GPL umbrella license.
> I am not a lawyer and cannot address the questions you raise regarding
> the interpretation of the GPL license terms."
>
> "You can use Mobicents to develop the service, but unless you open
> source your code, you should deploy on a licensed JBCP instance."
>
>
> This last response is a violation of the GPL license.
>
>
> Thanks a lot.
>
> --
> I=F1aki Baz Castillo <ibc@aliax.net>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple
>

From ibc@aliax.net  Mon Feb  8 17:26:00 2010
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF6EF3A74F0 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 17:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.049
X-Spam-Level: 
X-Spam-Status: No, score=-2.049 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 2Zz-nEEry6+2 for <simple@core3.amsl.com>; Mon,  8 Feb 2010 17:26:00 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 2268C3A74EE for <simple@ietf.org>; Mon,  8 Feb 2010 17:26:00 -0800 (PST)
Received: by vws13 with SMTP id 13so2420952vws.31 for <simple@ietf.org>; Mon, 08 Feb 2010 17:26:59 -0800 (PST)
Received: by 10.220.125.8 with SMTP id w8mr43340vcr.168.1265678819776; Mon, 08 Feb 2010 17:26:59 -0800 (PST)
Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 26sm49154280vws.4.2010.02.08.17.26.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Feb 2010 17:26:58 -0800 (PST)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: simple@ietf.org
Date: Tue, 9 Feb 2010 02:26:54 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; )
References: <201002081917.19213.ibc@aliax.net> <201002090200.07226.ibc@aliax.net> <c128d1a11002081720p697852e5gf327f75287ef94d7@mail.gmail.com>
In-Reply-To: <c128d1a11002081720p697852e5gf327f75287ef94d7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201002090226.54633.ibc@aliax.net>
Subject: Re: [Simple] XCAP is not developer-friendly as it doesn't allow using a standard XML/Xpath1.0 library
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 01:26:01 -0000

El Martes, 9 de Febrero de 2010, Eduardo Martins escribi=F3:
> That faq entry is out of date and is misleading, thanks for the alert,
> will be fixed. Anyway, as I said, currently all is LGPL.

Nice to know. Thanks a lot.=20


=2D-=20
I=F1aki Baz Castillo <ibc@aliax.net>

From christer.holmberg@ericsson.com  Thu Feb 18 05:54:27 2010
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A59EA3A7968 for <simple@core3.amsl.com>; Thu, 18 Feb 2010 05:54:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 HZ60ga1RsHxh for <simple@core3.amsl.com>; Thu, 18 Feb 2010 05:54:27 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id B61613A72CF for <simple@ietf.org>; Thu, 18 Feb 2010 05:54:26 -0800 (PST)
X-AuditID: c1b4fb3d-b7b85ae00000097d-35-4b7d46f7a6cc
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 6A.78.02429.7F64D7B4; Thu, 18 Feb 2010 14:56:08 +0100 (CET)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.27]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Thu, 18 Feb 2010 14:56:04 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Simple WG <simple@ietf.org>
Date: Thu, 18 Feb 2010 14:56:03 +0100
Thread-Topic: Draft new version: draft-ietf-simple-msrp-acm-05
Thread-Index: Acqwohvj/Vq91Bx9S5GSfNWW4lFHMQ==
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC7447519E3583@ESESSCMS0354.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_FF84A09F50A6DC48ACB6714F4666CC7447519E3583ESESSCMS0354e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [Simple] Draft new version: draft-ietf-simple-msrp-acm-05
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2010 13:54:27 -0000

--_000_FF84A09F50A6DC48ACB6714F4666CC7447519E3583ESESSCMS0354e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi,

I've submitted a new version of the ACM draft.

Based on WGLC comments, I've updated the TLS section and the Security Consi=
derations section.

All the issues I've been informed about should now be solved, as far as thi=
s draft is concerned.

Regards,

Christer


--_000_FF84A09F50A6DC48ACB6714F4666CC7447519E3583ESESSCMS0354e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"3">
<div>&nbsp;</div>
<div><font size=3D"2">Hi,</font></div>
<div><font size=3D"2">&nbsp;</font></div>
<div><font size=3D"2">I've submitted a new version of the ACM draft.</font>=
</div>
<div><font size=3D"2">&nbsp;</font></div>
<div><font size=3D"2">Based on WGLC comments, I've updated the TLS section =
and the Security Considerations section.</font></div>
<div><font size=3D"2">&nbsp;</font></div>
<div><font size=3D"2">All the issues I've been informed about should now be=
 solved, as far as this draft is concerned.</font></div>
<div><font size=3D"2">&nbsp;</font></div>
<div><font size=3D"2">Regards,</font></div>
<div><font size=3D"2">&nbsp;</font></div>
<div><font size=3D"2">Christer</font></div>
<div><font size=3D"2">&nbsp;</font></div>
</font>
</body>
</html>

--_000_FF84A09F50A6DC48ACB6714F4666CC7447519E3583ESESSCMS0354e_--

From root@core3.amsl.com  Thu Feb 18 06:00:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: simple@ietf.org
Delivered-To: simple@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id A3C2E3A7F72; Thu, 18 Feb 2010 06:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100218140001.A3C2E3A7F72@core3.amsl.com>
Date: Thu, 18 Feb 2010 06:00:01 -0800 (PST)
Cc: simple@ietf.org
Subject: [Simple] I-D Action:draft-ietf-simple-msrp-acm-05.txt
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2010 14:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP for Instant Messaging and Presence Leveraging Extensions Working Group of the IETF.


	Title           : An Alternative Connection Model for the Message Session Relay Protocol (MSRP)
	Author(s)       : C. Holmberg, S. Blau
	Filename        : draft-ietf-simple-msrp-acm-05.txt
	Pages           : 9
	Date            : 2010-02-18

This document defines an alternative connection model for Message
Session Relay Protocol (MSRP) User Agents (UAs), which uses the
connection-oriended media (COMEDIA) mechanism in order to create the
MSRP transport connection.  The model allows MSRP UAs behind Network
Address Translators (NATs) to negotiate which UA will initiate the
establishment of the TCP connection, in order for MSRP messages to
traverse the NAT.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-acm-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-simple-msrp-acm-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-02-18055336.I-D@ietf.org>


--NextPart--

From ben@estacado.net  Mon Feb 22 14:43:42 2010
Return-Path: <ben@estacado.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5A3328C3F8 for <simple@core3.amsl.com>; Mon, 22 Feb 2010 14:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[AWL=0.288,  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 cI2sY9TMtJDP for <simple@core3.amsl.com>; Mon, 22 Feb 2010 14:43:42 -0800 (PST)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id A26F53A8403 for <simple@ietf.org>; Mon, 22 Feb 2010 14:43:41 -0800 (PST)
Received: from [172.16.3.174] (dn3-174.estacado.net [172.16.3.174]) (authenticated bits=0) by estacado.net (8.14.3/8.14.2) with ESMTP id o1MMjZ5w069766 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 22 Feb 2010 16:45:36 -0600 (CST) (envelope-from ben@estacado.net)
From: Ben Campbell <ben@estacado.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Feb 2010 16:45:35 -0600
Message-Id: <9D76EF5C-30D7-4B12-97AC-54C8A43EA1D9@estacado.net>
To: Simple WG <simple@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1077)
X-Mailer: Apple Mail (2.1077)
Cc: Jari Urpalainen <jari.urpalainen@nokia.com>
Subject: [Simple] WGLC (repeat) of draft-ietf-simple-xcap-diff-14
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2010 22:43:43 -0000

This is a repeat Working Group Last Call on =
draft-ietf-simple-xcap-diff-14. The IESG review of this draft resulted =
in some new examples and normative text, so our AD has asked us to take =
another look at it before he approves it for publication. Jari indicated =
the following changes:

> changes from version 13 (iesg review):
> -clarifications to terminology
> -added example section to describe the three basic features: listing =
of collection content, patching and xcap component subscriptions
> -added section 6 to clarify the usage context of this mime type
> -security section updates
> -various other nit fixes

The draft is available at =
http://tools.ietf.org/html/draft-ietf-simple-xcap-diff-14

The WGLC will conclude on 9 March 2010. Please send your comments, =
including NITS and "this is ready to go" type comments, to the authors =
and the working group.

Thanks!

Ben.=

From ben@estacado.net  Thu Feb 25 14:02:29 2010
Return-Path: <ben@estacado.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4408328C44F for <simple@core3.amsl.com>; Thu, 25 Feb 2010 14:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.955
X-Spam-Level: 
X-Spam-Status: No, score=-1.955 tagged_above=-999 required=5 tests=[AWL=0.644,  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 gsqgirs2hYGr for <simple@core3.amsl.com>; Thu, 25 Feb 2010 14:02:28 -0800 (PST)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id A26D328C45E for <simple@ietf.org>; Thu, 25 Feb 2010 14:02:27 -0800 (PST)
Received: from [10.0.1.12] (adsl-68-94-26-218.dsl.rcsntx.swbell.net [68.94.26.218]) (authenticated bits=0) by estacado.net (8.14.3/8.14.2) with ESMTP id o1PM4Q86071947 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Feb 2010 16:04:31 -0600 (CST) (envelope-from ben@estacado.net)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <20100218140001.A3C2E3A7F72@core3.amsl.com>
Date: Thu, 25 Feb 2010 16:04:21 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C29E2DF-1755-470C-BB51-A8111671A0D9@estacado.net>
References: <20100218140001.A3C2E3A7F72@core3.amsl.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1077)
Cc: Simple WG <simple@ietf.org>
Subject: [Simple] draft-ietf-simple-msrp-acm-05: TLS mutual authentication
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 22:02:29 -0000

Do you mean to have all of the requirements in section 4.3 scoped to =
"UAs conformant to this specification"? That's not clear to me for the =
requirements in the 2nd and 3rd paragraph. I don't have issues having =
these requirements for ACM clients, but I'm not sure this draft should =
be making normative statements about how MSRP UAs use TLS in _general_.

Section 4.3 still seems to require all MSRP UAs that use TLS to have a =
certificate of some form, either a self-signed or a PKI certified one. =
It also implies a MUST level requirement to do mutual authentication, =
even though the prior paragraph says they SHOULD do mutual =
authentication. Should the paragraph have started with something to the =
effect of "When using mutual authentication..."?


On Feb 18, 2010, at 8:00 AM, internet-drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the SIP for Instant Messaging and =
Presence Leveraging Extensions Working Group of the IETF.
>=20
>=20
> 	Title           : An Alternative Connection Model for the =
Message Session Relay Protocol (MSRP)
> 	Author(s)       : C. Holmberg, S. Blau
> 	Filename        : draft-ietf-simple-msrp-acm-05.txt
> 	Pages           : 9
> 	Date            : 2010-02-18
>=20
> This document defines an alternative connection model for Message
> Session Relay Protocol (MSRP) User Agents (UAs), which uses the
> connection-oriended media (COMEDIA) mechanism in order to create the
> MSRP transport connection.  The model allows MSRP UAs behind Network
> Address Translators (NATs) to negotiate which UA will initiate the
> establishment of the TCP connection, in order for MSRP messages to
> traverse the NAT.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-acm-05.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <Mail Attachment>_______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


From ben@estacado.net  Thu Feb 25 14:20:37 2010
Return-Path: <ben@estacado.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C95573A8727 for <simple@core3.amsl.com>; Thu, 25 Feb 2010 14:20:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.027
X-Spam-Level: 
X-Spam-Status: No, score=-2.027 tagged_above=-999 required=5 tests=[AWL=0.572,  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 tPHbKvnZrvXu for <simple@core3.amsl.com>; Thu, 25 Feb 2010 14:20:37 -0800 (PST)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id 99CBF3A8726 for <simple@ietf.org>; Thu, 25 Feb 2010 14:20:36 -0800 (PST)
Received: from [10.0.1.12] (adsl-68-94-26-218.dsl.rcsntx.swbell.net [68.94.26.218]) (authenticated bits=0) by estacado.net (8.14.3/8.14.2) with ESMTP id o1PMMdIg074845 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Feb 2010 16:22:44 -0600 (CST) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
From: Ben Campbell <ben@estacado.net>
Date: Thu, 25 Feb 2010 16:22:34 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E56D969-E7FA-44B8-85D2-123A76C14D79@estacado.net>
References: <20100118073002.7CEAC3A680E@core3.amsl.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1077)
Cc: Simple WG <simple@ietf.org>
Subject: [Simple] Comments on draft-ietf-simple-msrp-sessmatch-02
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 22:20:37 -0000

I've got some new editorial comments:

-- section 4.1: I think the paragraph in section 5.4 or RFC 4975 that =
you refer to is the 10th one, not the ninth one.

-- section 4.2, 2nd sentence:

I think you've got a cut-and-paste error somewhere in this sentence.=20

Thanks!

Ben.=

From ben@estacado.net  Thu Feb 25 14:41:33 2010
Return-Path: <ben@estacado.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 628AC28C476 for <simple@core3.amsl.com>; Thu, 25 Feb 2010 14:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.084
X-Spam-Level: 
X-Spam-Status: No, score=-2.084 tagged_above=-999 required=5 tests=[AWL=0.515,  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 J1+9+J5ayDWY for <simple@core3.amsl.com>; Thu, 25 Feb 2010 14:41:32 -0800 (PST)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id 067DC3A85C4 for <simple@ietf.org>; Thu, 25 Feb 2010 14:41:31 -0800 (PST)
Received: from [10.0.1.12] (adsl-68-94-26-218.dsl.rcsntx.swbell.net [68.94.26.218]) (authenticated bits=0) by estacado.net (8.14.3/8.14.2) with ESMTP id o1PMh8SZ078142 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Feb 2010 16:43:39 -0600 (CST) (envelope-from ben@estacado.net)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <7C29E2DF-1755-470C-BB51-A8111671A0D9@estacado.net>
Date: Thu, 25 Feb 2010 16:43:39 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C3FB9DB-778A-489D-9C0E-08365D36BA16@estacado.net>
References: <20100218140001.A3C2E3A7F72@core3.amsl.com> <7C29E2DF-1755-470C-BB51-A8111671A0D9@estacado.net>
To: Ben Campbell <ben@estacado.net>
X-Mailer: Apple Mail (2.1077)
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] draft-ietf-simple-msrp-acm-05: TLS mutual authentication
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 22:41:33 -0000

Also, I meant to say "Otherwise, this version addresses my WGLC =
comments."

On Feb 25, 2010, at 4:04 PM, Ben Campbell wrote:

> Do you mean to have all of the requirements in section 4.3 scoped to =
"UAs conformant to this specification"? That's not clear to me for the =
requirements in the 2nd and 3rd paragraph. I don't have issues having =
these requirements for ACM clients, but I'm not sure this draft should =
be making normative statements about how MSRP UAs use TLS in _general_.
>=20
> Section 4.3 still seems to require all MSRP UAs that use TLS to have a =
certificate of some form, either a self-signed or a PKI certified one. =
It also implies a MUST level requirement to do mutual authentication, =
even though the prior paragraph says they SHOULD do mutual =
authentication. Should the paragraph have started with something to the =
effect of "When using mutual authentication..."?
>=20
>=20
> On Feb 18, 2010, at 8:00 AM, internet-drafts@ietf.org wrote:
>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>> This draft is a work item of the SIP for Instant Messaging and =
Presence Leveraging Extensions Working Group of the IETF.
>>=20
>>=20
>> 	Title           : An Alternative Connection Model for the =
Message Session Relay Protocol (MSRP)
>> 	Author(s)       : C. Holmberg, S. Blau
>> 	Filename        : draft-ietf-simple-msrp-acm-05.txt
>> 	Pages           : 9
>> 	Date            : 2010-02-18
>>=20
>> This document defines an alternative connection model for Message
>> Session Relay Protocol (MSRP) User Agents (UAs), which uses the
>> connection-oriended media (COMEDIA) mechanism in order to create the
>> MSRP transport connection.  The model allows MSRP UAs behind Network
>> Address Translators (NATs) to negotiate which UA will initiate the
>> establishment of the TCP connection, in order for MSRP messages to
>> traverse the NAT.
>>=20
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-acm-05.txt
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>> <Mail Attachment>_______________________________________________
>> Simple mailing list
>> Simple@ietf.org
>> https://www.ietf.org/mailman/listinfo/simple
>=20
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


From ben@estacado.net  Thu Feb 25 14:49:01 2010
Return-Path: <ben@estacado.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBDC03A85C5 for <simple@core3.amsl.com>; Thu, 25 Feb 2010 14:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.131
X-Spam-Level: 
X-Spam-Status: No, score=-2.131 tagged_above=-999 required=5 tests=[AWL=0.468,  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 mf03PRpgrGlN for <simple@core3.amsl.com>; Thu, 25 Feb 2010 14:49:01 -0800 (PST)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id B07193A85B7 for <simple@ietf.org>; Thu, 25 Feb 2010 14:49:00 -0800 (PST)
Received: from [10.0.1.12] (adsl-68-94-26-218.dsl.rcsntx.swbell.net [68.94.26.218]) (authenticated bits=0) by estacado.net (8.14.3/8.14.2) with ESMTP id o1PMp4i5079362 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Feb 2010 16:51:08 -0600 (CST) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <8E56D969-E7FA-44B8-85D2-123A76C14D79@estacado.net>
Date: Thu, 25 Feb 2010 16:50:58 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4F9F9F4-CEBF-4243-B4BD-0778733BAEC5@estacado.net>
References: <20100118073002.7CEAC3A680E@core3.amsl.com> <8E56D969-E7FA-44B8-85D2-123A76C14D79@estacado.net>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Simple WG <simple@ietf.org>
X-Mailer: Apple Mail (2.1077)
Subject: Re: [Simple] Comments on draft-ietf-simple-msrp-sessmatch-02
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 22:49:01 -0000

Also, I meant to say "Otherwise, this version addresses my WGLC =
comments."

On Feb 25, 2010, at 4:22 PM, Ben Campbell wrote:

>=20
>=20
> I've got some new editorial comments:
>=20
> -- section 4.1: I think the paragraph in section 5.4 or RFC 4975 that =
you refer to is the 10th one, not the ninth one.
>=20
> -- section 4.2, 2nd sentence:
>=20
> I think you've got a cut-and-paste error somewhere in this sentence.=20=

>=20
> Thanks!
>=20
> Ben.
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


From christer.holmberg@ericsson.com  Sun Feb 28 08:40:45 2010
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7588F3A8588 for <simple@core3.amsl.com>; Sun, 28 Feb 2010 08:40:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 zgyJIxxGBIEK for <simple@core3.amsl.com>; Sun, 28 Feb 2010 08:40:44 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 33B793A77D0 for <simple@ietf.org>; Sun, 28 Feb 2010 08:40:28 -0800 (PST)
X-AuditID: c1b4fb3d-b7c72ae00000040e-43-4b8a9c7b30fa
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id D3.FC.01038.B7C9A8B4; Sun, 28 Feb 2010 17:40:27 +0100 (CET)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.139]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Sun, 28 Feb 2010 17:40:27 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@estacado.net>
Date: Sun, 28 Feb 2010 17:40:26 +0100
Thread-Topic: draft-ietf-simple-msrp-acm-05: TLS mutual authentication
Thread-Index: Acq2ZoV1GMq+Vw8eT7yTxxmPGPBwwACKx+Ly
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC7457ECAD805B@ESESSCMS0354.eemea.ericsson.se>
References: <20100218140001.A3C2E3A7F72@core3.amsl.com>, <7C29E2DF-1755-470C-BB51-A8111671A0D9@estacado.net>
In-Reply-To: <7C29E2DF-1755-470C-BB51-A8111671A0D9@estacado.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] draft-ietf-simple-msrp-acm-05: TLS mutual authentication
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Feb 2010 16:40:45 -0000

Hi Ben,

>Do you mean to have all of the requirements in section 4.3 scoped to "UAs =
conformant to this specification"?=20
>That's not clear to me for the requirements in the 2nd and 3rd paragraph. =
I don't have issues having these=20
>requirements for ACM clients, but I'm not sure this draft should be making=
 normative statements about how=20
>MSRP UAs use TLS in _general_.
>
>Section 4.3 still seems to require all MSRP UAs that use TLS to have a cer=
tificate of some form, either a=20
>self-signed or a PKI certified one. It also implies a MUST level requireme=
nt to do mutual authentication, even=20
>though the prior paragraph says they SHOULD do mutual authentication. Shou=
ld the paragraph have started=20
>with something to the effect of "When using mutual authentication..."?

The 1st paragraph is ACM specific, so I think having normative text is ok. =
I can clarify that muthual authentication only applies when the UAs have ce=
rtificates.

"If an MSRP UA conformant to this document uses TLS, it MUST use the
TLS mechanisms defined in [RFC4975] and [RFC4976].  If the MSRP UAs=20
have TLS certificates, when establishing a TLS connection between peer MSRP=
 UAs,=20
mutual authentication of the TLS connection SHOULD be done.  From TLS=20
authentication point of view it is thus irrelevant whether an endpoint take=
s the=20
active or passive role."

The 2nd paragraph is not ACM specific - it is supposed to be a clarfication=
 of the procedures in RFC 4975. So, I do agree that we probably should not =
use "MUST" etc in the text. Instead we could say something like:

"In accordance with [RFC4975], if an MSRP UA has a TLS certificate, it alwa=
ys sends the certificate to the other endpoint during the TLS establishment=
. If an MSRP UA uses a self-signed TLS certificate to authenticate itself t=
o MSRP peers it also includes its certificate fingerprint in the SDP."

Also here I added "if an MSRP UA has a TLS certificate", to indicate that i=
t is not mandated by 4975.

The 3rd paragraph does not contain normative text in my opinion. It simply =
says that MSRP relays won't receive the SDP payloads containing the fingerp=
rint attributes.

Regards,

Christer



On Feb 18, 2010, at 8:00 AM, internet-drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the SIP for Instant Messaging and Presence L=
everaging Extensions Working Group of the IETF.
>
>
>       Title           : An Alternative Connection Model for the Message S=
ession Relay Protocol (MSRP)
>       Author(s)       : C. Holmberg, S. Blau
>       Filename        : draft-ietf-simple-msrp-acm-05.txt
>       Pages           : 9
>       Date            : 2010-02-18
>
> This document defines an alternative connection model for Message
> Session Relay Protocol (MSRP) User Agents (UAs), which uses the
> connection-oriended media (COMEDIA) mechanism in order to create the
> MSRP transport connection.  The model allows MSRP UAs behind Network
> Address Translators (NATs) to negotiate which UA will initiate the
> establishment of the TCP connection, in order for MSRP messages to
> traverse the NAT.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-acm-05.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <Mail Attachment>_______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple=
