
From christer.holmberg@ericsson.com  Tue Jun  1 04:54:44 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 7E65A3A69C1 for <simple@core3.amsl.com>; Tue,  1 Jun 2010 04:54:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.018
X-Spam-Level: 
X-Spam-Status: No, score=-3.018 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_50=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, 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 UWzb0WNi20qI for <simple@core3.amsl.com>; Tue,  1 Jun 2010 04:54:43 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id A50AE3A69C7 for <simple@ietf.org>; Tue,  1 Jun 2010 04:54:42 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b13ae0000071b2-46-4c04f4f5a27e
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id DE.3F.29106.5F4F40C4; Tue,  1 Jun 2010 13:54:29 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.84]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Tue, 1 Jun 2010 13:54:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "'simple@ietf.org'" <simple@ietf.org>
Date: Tue, 1 Jun 2010 13:54:28 +0200
Thread-Topic: [Simple] AD Review: draft-ietf-simple-msrp-acm-08.txt
Thread-Index: AcsA32Kj2X9s37QlSoivav7pLhmoSwAoaqKA
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC7465C62029CD@ESESSCMS0354.eemea.ericsson.se>
References: <4BE96D00.3030908@ericsson.com> <FF84A09F50A6DC48ACB6714F4666CC7465C54362D6@ESESSCMS0354.eemea.ericsson.se> <4C03E57C.9010303@ericsson.com>
In-Reply-To: <4C03E57C.9010303@ericsson.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: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Simple] AD Review: draft-ietf-simple-msrp-acm-08.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, 01 Jun 2010 11:54:44 -0000

Hi,

I have now submitted a new version (-09) of the ACM draft.

Regards,

Christer=20

> -----Original Message-----
> From: Gonzalo Camarillo=20
> Sent: 31. toukokuuta 2010 19:36
> To: Christer Holmberg
> Cc: simple@ietf.org
> Subject: Re: [Simple] AD Review: draft-ietf-simple-msrp-acm-08.txt
>=20
> Hi Christer,
>=20
> thanks for your answers. Please, revise the draft along the=20
> lines of your answers below so that I can start its IETF LC.
>=20
> Thanks,
>=20
> Gonzalo
>=20
> On 20/05/2010 8:14 PM, Christer Holmberg wrote:
> > Hi,
> > =20
> >> I have received a publication request for the following draft:
> >>
> >> https://datatracker.ietf.org/doc/draft-ietf-simple-msrp-acm/
> >>
> >> I have a few comments on the draft. The draft states that the main=20
> >> motivation for using COMEDIA is NAT traversal. The draft needs to=20
> >> explain why things like ICE TCP are not applicable or are=20
> inferior to=20
> >> the mechanism described in the draft. Section 5 touches upon this.
> > =20
> >  Assuming you have sessmatch, I guess one could use ICE TCP.
> > =20
> > (If you do NOT have sessmatch, and use ICE, the a=3Dpath address will=20
> > point to the STUN/TURN server, and you will end up with the uri=20
> > address comparision mismatch issue that sessmatch addresses.)
> > =20
> > Using comedia is much more "light weight" than using ICE,=20
> so I guess that is the main motivation for using comedia.
> > =20
> > Regarding ICE TCP, there has been some issues (mostly=20
> related to dual synch, afaik), but I don't know what the=20
> current status of those are. And, the latest version of the=20
> ICE TCP draft expired on april 16th.
> > =20
> > ------------------
> > =20
> >> Also, since the draft claims that this is an improvement over the=20
> >> standard way of establishing MSRP connections, the draft should=20
> >> briefly describe how it is superior. Is it only that one=20
> can specify=20
> >> which endpoint will start the TCP connection or are there other=20
> >> advantages of using COMEDIA?
> > =20
> >  For MSRP, that is the main advantage, yes.
> > =20
> > One could also say that an advantage is that the TCP=20
> connection establishement mechanism is consistant to the ones=20
> used for other types TCP transported media, but the main=20
> advantage is still NAT traversal.
> > =20
> >  (COMEDIA also defines the connection attribute, but MSRP=20
> does not use=20
> > it.)
> > =20
> >  ------------------
> > =20
> >> I found this sentence somewhat confusing:
> >>
> >> "User Agents that are likely to be deployed in networks where User=20
> >> Agents need to establish the TCP connections in order to traverse=20
> >> NATs SHOULD support this specification in order to improve=20
> the odds=20
> >> of being able to communicate across NATs."
> >>
> >> Does this simply mean that this mechanism is applicable in=20
> scenarios=20
> >> with NATs because it improves the odds of successfully=20
> establishing=20
> >> connections in such an environment?
> > =20
> > Yes.
> > =20
> >  But, the main point of the sentence is to make clear that=20
> it is not only useful for the entities behind the NATs to=20
> support the mechanism, but also for other entities in=20
> networks where NATs are deployed - even if those entities are=20
> not behind NATs.
> > =20
> >  This paragraph has been modified a number of times, but=20
> maybe the following text would be more clear:
> > =20
> >  "User Agents that are likely to be deployed in networks with NATs=20
> > SHOULD support this specification. It will improve  the=20
> odds of being=20
> > able to make TCP connections successfully traverse NATs,=20
> since User Agents behind NATs can be  requested to initiate=20
> the establishment of the TCP connections."
> >=20
> > =20
> >  ------------------
> > =20
> > =20
> >> The following normative statement seems redundant since=20
> support for=20
> >> COMEDIA has already been mandated:
> >>
> >> "An MSRP UA MUST support the a=3Dsetup "active", "actpass"=20
> and "passive"
> >> attribute values."
> >>
> >> If this sentence is meant as a clarification, it should=20
> not use RFC2119 language.
> >>
> > The MSRP UA does not need to support all attribute values,=20
> so it needs to be clear which it needs to support.
> > =20
> >  But, I guess "MUST" could be changed to "must".
> > =20
> >  At one point we made a WG decission to not talk about the=20
> "holdconn" attribute value, but if it makes the text more=20
> clear I could add something like:
> > =20
> >  "MSRP UAs compliant to this specification MUST NOT send=20
> the "holdconn" attribute, and MUST ignore it if received."
> > =20
> > =20
> >  ------------------
> > =20
> > =20
> >> The same with this sentence:
> >>
> >> "In accordance with [RFC4145], if the a=3Dsetup attribute value is=20
> >> "active", the port number value SHOULD be 9."
> >>
> >> The idea is not to informatively specify things that are=20
> already specified in COMEDIA.
> > =20
> >  Ok. I can change "SHOULD" to "should".
> > =20
> > =20
> >  ------------------
> > =20
> > =20
> >> The authors may want to consider splitting Section 4.2=20
> into several=20
> >> sections. One with general guidelines on how to use=20
> COMEDIA in this=20
> >> environment, another on which values on the COMEDIA=20
> parameters need=20
> >> to be used for backwards compatibility reasons (i.e., to interact=20
> >> with regular MRSP endpoints). The other would describe the=20
> policy to=20
> >> be used when setting those values to maximize the chances=20
> to traverse=20
> >> NATs. I would keep this last section at a SHOULD or=20
> RECOMMENDED level=20
> >> (at
> >> maximum) because endpoints in some environments might want to do=20
> >> things differently.
> > =20
> > I guess we could remove the second paragraph ("The a=3Dsetup=20
> attribute is particurlarly..."), because the introduction of=20
> the draft already says the same for comedia in general.
> > =20
> > So, the remaining section could e.g. be divided into two=20
> sub sections, as below:
> > =20
> > "4.2.  a=3Dsetup
> > =20
> >   4.2.1 General
> > =20
> >   An MSRP UA uses the SDP a=3Dsetup attribute [RFC4145], in order
> >   to negotiate which endpoint will create the MSRP=20
> transport connection
> >   towards the other UA.
> >  =20
> >   An MSRP UA MUST always include an explicit a=3Dsetup=20
> attribute in its
> >   SDP offers and answers, since it might be useful for the other
> >   endpoint, or for entities in the network, to know whether the UA
> >   supports COMEDIA or not.
> >=20
> >   An MSRP UA must support the a=3Dsetup "active", "actpass"=20
> and "passive"
> >   attribute values.
> > =20
> >   4.2.2 Attribute usage
> > =20
> >   When the a=3Dsetup attribute value is "actpass" or "passive", the IP
> >   address and port values in the MSRP URI of the SDP a=3Dpath=20
> attribute
> >   MUST contain the actual address and port values on which=20
> the UA can
> >   receive a TCP Open request for the MSRP transport connection.
> > =20
> >   In accordance with [RFC4145], if the a=3Dsetup attribute value is
> >   "active", the port number value should be 9.
> > =20
> >   If an MSRP UA can provide a global IP address that the=20
> other endpoint
> >   can use as destination for a TCP Open request, the UA MUST use the
> >   a=3Dsetup "actpass" attribute value in SDP offers.  This is=20
> in order to
> >   allow the remote UA to send an SDP answer with an a=3Dsetup "active"
> >   attribute value if the UA is located behind NAT, and in=20
> order to be
> >   compatible with UAs that do not support COMEDIA and thus always
> >   will act as passive endpoints.  If an MSRP UA cannot provide the
> >   actual transport address, the UA MUST use the a=3Dsetup "active"
> >   attribute value.
> > =20
> >   The MSRP UA MUST NOT use the a=3Dsetup "passive" attribute=20
> value in an SDP
> >   offer.
> > =20
> >   The MSRP UA can determine that it provides a global IP=20
> address in the
> >   following scenarios:
> > =20
> >   - the UA can determine that it is not located behind a NAT;
> > =20
> >   - the UA relays its MSRP transport connections via a relay (e.g.
> >     MSRP relay or TURN server); or
> > =20
> >   - the UA has used Session Traversal Utilities for NAT (STUN)
> >     [RFC5389] signaling to retrieve NAT address and port through the
> >     local port to be used for the eventual transport=20
> connection, while
> >     also having determined that the NAT is not address restricted.
> > =20
> >  Some UAs can determine whether the SIP [RFC3261] signaling has=20
> > traversed a NAT by inspecting the SIP Via header field in the 200
> > (OK) response to the initial SIP REGISTER request, and=20
> comparing the=20
> > IP addresses in the Via sent-by and the received header field=20
> > parameters.  If the IP addresses are not the same then the UA can=20
> > determine that there is a NAT in the path.  Even though the media=20
> > transport might not traverse the NAT, it is safe to assume that it=20
> > will, and set the a=3Dsetup attribute accordingly.  This comparing=20
> > mechanism does not work in all scenarios, though.  For=20
> example, if SIP=20
> > a requests crosses a SIP proxy before crossing a NAT, the=20
> UA will not=20
> > be able to detect the NAT by comparing the IP addresses.
> > =20
> > If an SDP offer includes an a=3Dsetup "actpass" attribute=20
> value, the SDP=20
> > answer MAY include an a=3Dsetup "active" attribute value, but SHOULD=20
> > include a=3Dsetup "passive" attribute value if the SDP answerer knows=20
> > that it is not located behind a NAT.
> > =20
> > Once the active UA has established the MSRP transport=20
> connection, the=20
> > UA must immediately send an MSRP SEND request, as defined in=20
> > [RFC4975].
> > =20
> > NOTE: According to [RFC4975] the initiating UA is always=20
> active, but=20
> > when COMEDIA is used the a=3Dsetup attribute is used to=20
> negotiate which=20
> > UA becomes active."
> >=20
> >=20
> > Regards,
> >=20
> > Christer
>=20
> =

From root@core3.amsl.com  Tue Jun  1 05: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 864BC3A690E; Tue,  1 Jun 2010 05:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100601120001.864BC3A690E@core3.amsl.com>
Date: Tue,  1 Jun 2010 05:00:01 -0700 (PDT)
Cc: simple@ietf.org
Subject: [Simple] I-D Action:draft-ietf-simple-msrp-acm-09.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, 01 Jun 2010 12: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-09.txt
	Pages           : 9
	Date            : 2010-06-01

This document defines an alternative connection model for Message
Session Relay Protocol (MSRP) User Agents (UAs), which uses the
connection-oriented media (COMEDIA) mechanism in order to create the
MSRP transport connection.  The model allows MSRP UAs behind Network
Address Translators (NATs) to negotiate which endpoint initiates 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-09.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-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From christer.holmberg@ericsson.com  Tue Jun  1 05:22:50 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 D2BCE28C4E5 for <simple@core3.amsl.com>; Tue,  1 Jun 2010 05:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.681
X-Spam-Level: 
X-Spam-Status: No, score=-3.681 tagged_above=-999 required=5 tests=[AWL=0.459,  BAYES_20=-0.74, J_CHICKENPOX_14=0.6, 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 cVqLVs5lzkKt for <simple@core3.amsl.com>; Tue,  1 Jun 2010 05:22:49 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id E94B528C4DE for <simple@ietf.org>; Tue,  1 Jun 2010 05:21:45 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b13ae0000071b2-7a-4c04fb4cb376
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id AC.F2.29106.C4BF40C4; Tue,  1 Jun 2010 14:21:32 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.84]) by esessmw0184.eemea.ericsson.se ([153.88.115.81]) with mapi; Tue, 1 Jun 2010 14:21:32 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "'simple@ietf.org'" <simple@ietf.org>
Date: Tue, 1 Jun 2010 14:21:31 +0200
Thread-Topic: [Simple] AD review: draft-ietf-simple-msrp-sessmatch-05
Thread-Index: AcsA317aP7cN03S4SkKBh+YXcxYcyAApVo8g
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC7465C6202A15@ESESSCMS0354.eemea.ericsson.se>
References: <4BE96CFF.2020402@ericsson.com> <FF84A09F50A6DC48ACB6714F4666CC7465C54362D9@ESESSCMS0354.eemea.ericsson.se> <4C03E575.5030505@ericsson.com>
In-Reply-To: <4C03E575.5030505@ericsson.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: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Simple] AD review: draft-ietf-simple-msrp-sessmatch-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: Tue, 01 Jun 2010 12:22:51 -0000

Hi,

I have now submitted a new version (-06) of the SESSMATCH draft.

Regards,

Christer =20

> -----Original Message-----
> From: Gonzalo Camarillo=20
> Sent: 31. toukokuuta 2010 19:36
> To: Christer Holmberg
> Cc: simple@ietf.org
> Subject: Re: [Simple] AD review: draft-ietf-simple-msrp-sessmatch-05
>=20
> Hi Christer,
>=20
> thanks for your answers. Please, revise the draft along the=20
> lines of your answers below so that I can start its IETF LC.
>=20
> Thanks,
>=20
> Gonzalo
>=20
> On 20/05/2010 8:50 PM, Christer Holmberg wrote:
> > Hi,
> >=20
> >> I have received a publication request for the following draft:
> >>
> >> https://datatracker.ietf.org/doc/draft-ietf-simple-msrp-sessmatch/
> >>
> >> I have a few comments on the draft. Adding a few words=20
> describing how=20
> >> the path mechanism works would be useful. With such an=20
> explanation,=20
> >> it would be easier for readers to understand what this=20
> extension is about.
> >=20
> > My assumption was that the reader is familar with MSRP and=20
> the path attribute, but I can add some explanation words.
> >=20
> > What about adding the following sentence to the 3rd=20
> paragraph of section 1:
> >=20
> > "The SDP a=3Dpath attribute is used to establish the routeset=20
> for the MSRP messages associated with the session."
> >=20
> > ------------------
> >=20
> >> The draft states that with this extension, ALGs in the=20
> path need to=20
> >> only be SDP aware as opposed to MSRP aware. That text=20
> implies that an=20
> >> ALG using standard MSRP can already introduce itself in the path=20
> >> (although with a bit more of work).
> >=20
> > The text is probably a little confusing, and mixes up things.
> >=20
> > The main point is that, currently, the *media relay* of an=20
> ALGs needs to modify the MSRP messages, rather than just=20
> passing them as data (as it does for most other media types).=20
> >=20
> > The *signalling handler* of an ALG needs to be MSRP aware,=20
> in the sense that it needs to modify the a=3Dpath attribute=20
> rather than the c/m line.
> >=20
> > So, maybe the following text is more clear:
> >=20
> > "The SDP a=3Dpath attribute is used to establish the routeset=20
> for the MSRP messages associated with the session.
> > Due to the fact that MSRP UAs check consistency between address=20
> > information in the MSRP messages and in the Session Description=20
> > Protocol (SDP) a=3Dpath attribute, when an ALG modifies the address=20
> > information of the a=3Dpath attribute, it forces the media=20
> relay of the ALG to act as an MSRP Back-To-Back User Agent=20
> (B2BUA) in order to perform the corresponding modifications=20
> in the MSRP messages, whereas for other media types the media=20
> relay only needs to modify the IP and transport headers."
> >=20
> > Do you think that is more clear?
> >=20
> >=20
> > ------------------
> >=20
> >=20
> >> So, one could think that the security properties of the protocol=20
> >> would not be affected much. However, the security=20
> considerations are=20
> >> not very clear about this. The Security Considerations=20
> Section should=20
> >> clear on what it is actually describing at any given time.=20
> Clarifying which threats that section talks about would make=20
> the text much easier to understand (e.g., does the=20
> man-in-the-middle introduce itself in the path by modifying=20
> the SDP or just modifies MSRP packets?).
> >=20
> > Would the following be more clear:
> >=20
> > "However, since a man-in-the-middle would in any case be able to=20
> > modify the domain information in both the SDP and the MSRP=20
> messages,=20
> > e.g in order to insert itself in the MSRP signalling path=20
> or to route MSRP messages to non-intended entities, this does=20
> not  introduce any new security risk."
> >=20
> > I also had a look at the remaining text in the security section.
> >=20
> > If needed, to the end of the 3rd paragraph I could end the=20
> following:
> >=20
> > "Based on this information, users can trigger some actions=20
> in order to=20
> > check whether network entities work correctly, or whether =20
> a man-in-the-middle has modified the SDP a=3Dpath attribute,=20
> for the same reasons as described earlier."
> >=20
> > The 2 last paragraphs I think are clear, because they=20
> describe how the TLS authentication mechanism can be affected.
> >=20
> >=20
> > Regards,
> >=20
> > Christer
>=20
> =

From root@core3.amsl.com  Tue Jun  1 05:30:05 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 585D128C2CC; Tue,  1 Jun 2010 05:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100601123002.585D128C2CC@core3.amsl.com>
Date: Tue,  1 Jun 2010 05:30:01 -0700 (PDT)
Cc: simple@ietf.org
Subject: [Simple] I-D Action:draft-ietf-simple-msrp-sessmatch-06.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, 01 Jun 2010 12:30:05 -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           : Session Matching Update for the Message Session Relay Protocol (MSRP)
	Author(s)       : C. Holmberg, S. Blau
	Filename        : draft-ietf-simple-msrp-sessmatch-06.txt
	Pages           : 6
	Date            : 2010-06-01

This document updates the session matching procedure defined in
sections 5.4 and 7.3 of RFC 4975, so that an Message Session Relay
Protocol (MSRP) User Agent (UA) only uses the session-id part of the
MSRP URI in order to perform the consistency checks.  The update
allows intermediaries, Application Layer Gateways (ALGs), to modify
the address information in the MSRP URI of the Session Description
Protocol (SDP) a=path attribute, without the need for the
intermediaries to terminate and do the correlating modifications in
the associated MSRP messages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-sessmatch-06.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-sessmatch-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From hisham.khartabil@gmail.com  Thu Jun  3 19:43:01 2010
Return-Path: <hisham.khartabil@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 D5E7E3A67F5 for <simple@core3.amsl.com>; Thu,  3 Jun 2010 19:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.236
X-Spam-Level: ****
X-Spam-Status: No, score=4.236 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45]
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 CXyYGpH+5U0K for <simple@core3.amsl.com>; Thu,  3 Jun 2010 19:42:56 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 087543A6862 for <simple@ietf.org>; Thu,  3 Jun 2010 19:42:55 -0700 (PDT)
Received: by pxi19 with SMTP id 19so72761pxi.31 for <simple@ietf.org>; Thu, 03 Jun 2010 19:42:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=XGOy8yAbxpZJ2S3rQyi/T7QlXt+LX3xQNkP6PmD62Uw=; b=HYmwUa2X4fZa6CZj1sAzbDWMyNzkp5bIIm0JTh0Tgt/fmfBwPzRPhXE9pECSxqkLWY D5kE9MjUUhngN4FpyRMeAYQAAfePrF40PRnmIoEYQ1tGVYnFbCPus+fKjrR3kPaUySjA Aypu7grVs++j4lJeXqOLkSZuwMc+3IyyXKm2o=
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; b=Xh16/nb/Ezzl6YwlB57K/RgObvJYss/rDaM0Wfhnp6DCr4DqMy7pVNVI+Fif5pIKMO Un1Q6eCnJeUNywnaGK1KkUxuhvQOfYA7RCpWR5DAPi7qxDn5NmdHcrI2g6jy1XaSSct1 tMiaQJKMNa1Gd9yzdRurJdgxAL4uMi62shqiY=
MIME-Version: 1.0
Received: by 10.142.75.17 with SMTP id x17mr7680073wfa.46.1275619356828; Thu,  03 Jun 2010 19:42:36 -0700 (PDT)
Received: by 10.143.4.21 with HTTP; Thu, 3 Jun 2010 19:42:36 -0700 (PDT)
In-Reply-To: <0L3G0014DUYV7L@mmp2.samsung.com>
References: <AcsDhdek3iSCsMJqQYq8W2S5ezBBkQ==> <0L3G0014DUYV7L@mmp2.samsung.com>
Date: Fri, 4 Jun 2010 12:42:36 +1000
Message-ID: <AANLkTimVxbJZtdpyA-6huNLoVQPetu5P1kCoNrmU9pkD@mail.gmail.com>
From: Hisham Khartabil <hisham.khartabil@gmail.com>
To: =?EUC-KR?B?wMy9wr/r?= <sy7216.lee@samsung.com>
Content-Type: multipart/alternative; boundary=001636e1fb60a1e4b904882b463d
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] Question about RFC5438 wrt OMA CPM
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: Fri, 04 Jun 2010 02:43:02 -0000

--001636e1fb60a1e4b904882b463d
Content-Type: text/plain; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable

Hi,

Section 12.1.3.1 does mention that the request-uri and the To header field
in the IMDN (which is a SIP MESSAGE request) are populated from the From
header field of the IM (which is a SIP MESSAGE request).

This is the initial step. You then need to do some processing.

If there are IMDN-Record-Route headers in the payload of the IM, then you
need to add the 1st URI of that IMDN-Record-Route header field into the
route set of the IMDN as the last entry (see RFC3261 for route set
definition). You then need to follow RFC3261 for population of Request-URI
and Route header fields according to the route set.

The route set could be initially empty and therefore the only the uri from
the IMDN-Record-Route is the only one. Or it could be populated with
whatever the client has pre-configured (for example, an outbound proxy) and
therefore the uri is added to the end f that route set.

This is normal RFC3261 behaviour.

Thanks,
Hisham

2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>

>  *Dear Eric Burger, Hisham Khartabil and Christer Holmberg,*
>
> * *
>
> *This is Seungyong Lee from Samsung Electronics and in charge of OMA(Open
> Mobile Alliance) CPM (Converged-IP Messaging).*
>
> *CPM 1.0 supports IMDN for requesting/receiving delivery notifications an=
d
> read reports. *
>
> *In the last CPM meeting (in MAY) there was a heated debate about IMDN
> routing, especially how to populate the Request-URI of IMDN.*
>
> * *
>
> *A delegate from Ericsson argued on the basis of the e-mail thread (*see
> http://www.ietf.org/mail-archive/web/simple/current/msg08759.html*) that
> the Request-URI of IMDN should be set to the top-most address of
> IMDN-Record-Router header in the received IM where as Samsung retorted th=
at
> the Request-URI is populated from SIP From header of the received IM, whi=
ch
> is based on section 12.1.3.1 in RFC5438.*
>
> *Section 12.1.3.1 says **=A1=B0=A1=A6snip**=A1=A6 For IMDNs, the IM Recip=
ient populates
> the SIP Request-URI and the SIP To header field using the address that
> appeared in the SIP From header field in the IM.**=A1=B1*
>
> * *
>
> *The routing mechanism of IMDN that I**=A1=AF**m thinking of is very simi=
lar
> with the SIP routing. That is, Request-URI is populated from SIP From hea=
der
> and also SIP Route header is from IMDN-Route header. Because it is SIP
> headers that is used for routing in SIP/IP core, some CPIM headers for IM=
DN
> (e.g. IMDN Route header) needs to be reflected in SIP headers (e.g. SIP
> Route header).*
>
> * *
>
> *Could you let me know your intended routing scenario from RFC5438 author=
s
> **=A1=AF** perspective?*
>
> *Your quick reply would be so much appreciated and helpful to complete CP=
M
> 1.0 without delay.*
>
> * *
>
> *Thanks*
>
> *Sincerely,*
>
> * *
>
> *Seungyong Lee*
>
> *Samsung Electronics*
>
> *DMC Research Lab*
>
> *Biz: +82-31-279-5450*
>
> *E-mail: sy7216.lee@samsung.com*
>

--001636e1fb60a1e4b904882b463d
Content-Type: text/html; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>Section 12.1.3.1 does mention that the request-uri and the To he=
ader field in the IMDN (which is a SIP MESSAGE request) are populated from =
the From header field of the IM (which is a SIP MESSAGE request).<br><br>
This is the initial step. You then need to do some processing.<br><br>If th=
ere are IMDN-Record-Route headers in the payload of the IM, then you need t=
o add the 1st URI of that IMDN-Record-Route header field into the route set=
 of the IMDN as the last entry (see RFC3261 for route set definition). You =
then need to follow RFC3261 for population of Request-URI and Route header =
fields according to the route set.<br>
<br>The route set could be initially empty and therefore the only the uri f=
rom the IMDN-Record-Route is the only one. Or it could be populated with wh=
atever the client has pre-configured (for example, an outbound proxy) and t=
herefore the uri is added to the end f that route set.<br>
<br>This is normal RFC3261 behaviour.<br><br>Thanks,<br>Hisham<br><br><div =
class=3D"gmail_quote">2010/6/4 =C0=CC=BD=C2=BF=EB <span dir=3D"ltr">&lt;<a =
href=3D"mailto:sy7216.lee@samsung.com">sy7216.lee@samsung.com</a>&gt;</span=
><br><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; =
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">














<div link=3D"blue" vlink=3D"purple" lang=3D"KO">

<div style=3D"">

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Dear Eric Burger, =
Hisham Khartabil and Christer Holmberg,</span></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">This is Seungyong =
Lee from Samsung Electronics and in
charge of OMA(Open Mobile Alliance)
CPM (Converged-IP Messaging).</span></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">CPM 1.0 supports I=
MDN for requesting/receiving
delivery notifications and read reports. </span></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">In the last CPM me=
eting (in MAY) there was a heated
debate about IMDN routing, especially how to populate the Request-URI of IM=
DN.</span></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">A delegate from Er=
icsson argued on the basis of the
e-mail thread (</span></font></b><font face=3D"Arial"><span style=3D"font-f=
amily: Arial;" lang=3D"EN-US">see <a href=3D"http://www.ietf.org/mail-archi=
ve/web/simple/current/msg08759.html" target=3D"_blank">http://www.ietf.org/=
mail-archive/web/simple/current/msg08759.html</a></span></font><b><span sty=
le=3D"font-weight: bold;" lang=3D"EN-US">) that the Request-URI of IMDN sho=
uld be
set to the top-most address of IMDN-Record-Router header in the received IM
where as Samsung retorted that the Request-URI is populated from SIP From
header of the received IM, which is based on section 12.1.3.1 in RFC5438.</=
span></b></p>

<p class=3D"MsoNormal" style=3D"text-align: left;" align=3D"left"><b><font =
face=3D"=B9=D9=C5=C1" size=3D"2"><span style=3D"font-size: 10pt; font-weigh=
t: bold;" lang=3D"EN-US">Section
12.1.3.1 says </span></font></b><b><font face=3D"Times New Roman"><span sty=
le=3D"font-family: &quot;Times New Roman&quot;; font-weight: bold;" lang=3D=
"EN-US">&ldquo;&hellip;</span></font><span lang=3D"EN-US">snip</span></b><b=
><font face=3D"Times New Roman"><span style=3D"font-family: &quot;Times New=
 Roman&quot;; font-weight: bold;" lang=3D"EN-US">&hellip;</span></font><spa=
n lang=3D"EN-US"> For IMDNs, the IM Recipient populates the SIP Request-URI=
 and the
SIP To header field using the address that appeared in the SIP From header
field in the IM.</span></b><b><font face=3D"Times New Roman"><span style=3D=
"font-family: &quot;Times New Roman&quot;; font-weight: bold;" lang=3D"EN-U=
S">&rdquo;</span></font></b><font face=3D"Courier"><span style=3D"font-fami=
ly: Courier;" lang=3D"EN-US"></span></font></p>


<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">The routing mechan=
ism of IMDN that I</span></font></b><b><font face=3D"Arial"><span style=3D"=
font-family: Arial; font-weight: bold;" lang=3D"EN-US">&rsquo;</span></font=
></b><b><font face=3D"=B1=BC=B8=B2"><span style=3D"font-weight: bold;" lang=
=3D"EN-US">m thinking of
is very similar with the SIP routing. That is, Request-URI is populated fro=
m
SIP From header and also SIP Route
header is from IMDN-Route header. Because it is SIP headers that is used fo=
r
routing in SIP/IP core, some CPIM headers for IMDN (e.g. IMDN Route header)=
 needs to be reflected
in SIP headers (e.g. SIP Route
header).</span></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Could you let me k=
now your intended
routing scenario from RFC5438 authors</span></font></b><b><font face=3D"Ari=
al"><span style=3D"font-family: Arial; font-weight: bold;" lang=3D"EN-US">&=
rsquo;</span></font></b><b><font face=3D"=B1=BC=B8=B2"><span style=3D"font-=
weight: bold;" lang=3D"EN-US"> perspective?</span></font></b></p>


<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Your quick reply w=
ould be so much
appreciated and helpful to complete CPM 1.0 without delay.</span></font></b=
></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Thanks</span></fon=
t></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Sincerely,</span><=
/font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Seungyong Lee</spa=
n></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Samsung Electronic=
s</span></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">DMC Research Lab</=
span></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"FR">Biz: +82-31-279-5450<=
/span></font></b></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"FR">E-mail: <a href=3D"ma=
ilto:sy7216.lee@samsung.com" target=3D"_blank">sy7216.lee@samsung.com</a></=
span></font></b></p>


</div>

</div>


</blockquote></div><br>

--001636e1fb60a1e4b904882b463d--

From hisham.khartabil@gmail.com  Thu Jun  3 22:56:41 2010
Return-Path: <hisham.khartabil@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 6B7D43A6987 for <simple@core3.amsl.com>; Thu,  3 Jun 2010 22:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.236
X-Spam-Level: ****
X-Spam-Status: No, score=4.236 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45]
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 m8jGg+VILTTe for <simple@core3.amsl.com>; Thu,  3 Jun 2010 22:56:34 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 747733A691B for <simple@ietf.org>; Thu,  3 Jun 2010 22:56:34 -0700 (PDT)
Received: by gwb11 with SMTP id 11so620476gwb.31 for <simple@ietf.org>; Thu, 03 Jun 2010 22:56:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=q9hyyGcXv+a0aGhXwNDw6W+jmfsAIw2lG81rrHzGOuU=; b=Pvd3nwzO3KMAuw5vWR+wcPbyUXsE3oCZGqEu28UGl3u41s7l0AFzLbkKaND9nbE5UD n5FoQqPgoO+6c7LvbLX73uQmbzSbTjQXo66eV7listp0SdRL3Ho46/Xk2JuS7L1Pzp8v ClUxroIv10Rq6cgqdyf4SwSR0rf6hMyc+Pcl0=
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; b=ZaKiRHaaLpkr3aIWeegctFtGw5RD3OG5Q8hfODox4MLdEsH5/Lf267twbC7Aw7+5bR M5PAoje0ag4BgUE3ebKGGLuxd6/fL41WSsDad9f0neMNBrKE5mMV5XkEWuZ2uZI9xYK9 UXk3/S9iGhB+QALv69qV1JZUmHfz5x1QUwKKQ=
MIME-Version: 1.0
Received: by 10.101.182.11 with SMTP id j11mr11284298anp.171.1275630978332;  Thu, 03 Jun 2010 22:56:18 -0700 (PDT)
Received: by 10.100.11.17 with HTTP; Thu, 3 Jun 2010 22:56:18 -0700 (PDT)
In-Reply-To: <0L3G00G7PZHPUP@mmp1.samsung.com>
References: <AANLkTimVxbJZtdpyA-6huNLoVQPetu5P1kCoNrmU9pkD@mail.gmail.com> <0L3G00G7PZHPUP@mmp1.samsung.com>
Date: Fri, 4 Jun 2010 15:56:18 +1000
Message-ID: <AANLkTiluy6D51MFbDmQhIBSseIx37irCyQN_YLrOHl3g@mail.gmail.com>
From: Hisham Khartabil <hisham.khartabil@gmail.com>
To: =?EUC-KR?B?wMy9wr/r?= <sy7216.lee@samsung.com>
Content-Type: multipart/alternative; boundary=001636c92c6053f99404882dfb60
Cc: Simple WG <simple@ietf.org>
Subject: Re: [Simple] Question about RFC5438 wrt OMA CPM
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: Fri, 04 Jun 2010 05:56:41 -0000

--001636c92c6053f99404882dfb60
Content-Type: text/plain; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable

Not all the URIs in the IMDN-Record-Route, just the 1st one. You then follo=
w
the procedure in RFC3261 to route the MESSAGE request.

2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>

>  Hi Hisahm,
>
>
>
> Thanks for your quick reply.
>
>
>
> If my understanding is right, you mention that the Request-URI of IMDN is
> populated from the SIP From header of the IM and in addition, route set
> recorded in the IMDN-Record-Route header should be included in the SIP Ro=
ute
> header in order to guarantee to have IMDN traversed through the SIP Proxi=
es
> whose address was recorded in the IMDN-Record-Route header.
>
>
>
> My understanding is right?
>
>
>
> Regards,
>
> Seungyong
>
>
>
>
>  ------------------------------
>
> *From:* Hisham Khartabil [mailto:hisham.khartabil@gmail.com]
> *Sent:* Friday, June 04, 2010 11:43 AM
> *To:* =C0=CC=BD=C2=BF=EB
> *Cc:* eburger@standardstrack.com; christer.holmberg@ericsson.com; Simple
> WG
> *Subject:* Re: Question about RFC5438 wrt OMA CPM
>
>
>
> Hi,
>
> Section 12.1.3.1 does mention that the request-uri and the To header fiel=
d
> in the IMDN (which is a SIP MESSAGE request) are populated from the From
> header field of the IM (which is a SIP MESSAGE request).
>
> This is the initial step. You then need to do some processing.
>
> If there are IMDN-Record-Route headers in the payload of the IM, then you
> need to add the 1st URI of that IMDN-Record-Route header field into the
> route set of the IMDN as the last entry (see RFC3261 for route set
> definition). You then need to follow RFC3261 for population of Request-UR=
I
> and Route header fields according to the route set.
>
> The route set could be initially empty and therefore the only the uri fro=
m
> the IMDN-Record-Route is the only one. Or it could be populated with
> whatever the client has pre-configured (for example, an outbound proxy) a=
nd
> therefore the uri is added to the end f that route set.
>
> This is normal RFC3261 behaviour.
>
> Thanks,
> Hisham
>
> 2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>
>
> *Dear Eric Burger, Hisham Khartabil and Christer Holmberg,*
>
> * *
>
> *This is Seungyong Lee from Samsung Electronics and in charge of OMA(Open
> Mobile Alliance) CPM (Converged-IP Messaging).*
>
> *CPM 1.0 supports IMDN for requesting/receiving delivery notifications an=
d
> read reports. *
>
> *In the last CPM meeting (in MAY) there was a heated debate about IMDN
> routing, especially how to populate the Request-URI of IMDN.*
>
> * *
>
> *A delegate from Ericsson argued on the basis of the e-mail thread (*see
> http://www.ietf.org/mail-archive/web/simple/current/msg08759.html*) that
> the Request-URI of IMDN should be set to the top-most address of
> IMDN-Record-Router header in the received IM where as Samsung retorted th=
at
> the Request-URI is populated from SIP From header of the received IM, whi=
ch
> is based on section 12.1.3.1 in RFC5438.*
>
> *Section 12.1.3.1 says **=A1=B0=A1=A6snip**=A1=A6 For IMDNs, the IM Recip=
ient populates
> the SIP Request-URI and the SIP To header field using the address that
> appeared in the SIP From header field in the IM.**=A1=B1*
>
> * *
>
> *The routing mechanism of IMDN that I**=A1=AFm thinking of is very simila=
r with
> the SIP routing. That is, Request-URI is populated from SIP From header a=
nd
> also SIP Route header is from IMDN-Route header. Because it is SIP header=
s
> that is used for routing in SIP/IP core, some CPIM headers for IMDN (e.g.
> IMDN Route header) needs to be reflected in SIP headers (e.g. SIP Route
> header).*
>
> * *
>
> *Could you let me know your intended routing scenario from RFC5438 author=
s
> **=A1=AF perspective?*
>
> *Your quick reply would be so much appreciated and helpful to complete CP=
M
> 1.0 without delay.*
>
> * *
>
> *Thanks*
>
> *Sincerely,*
>
> * *
>
> *Seungyong Lee*
>
> *Samsung Electronics*
>
> *DMC Research Lab*
>
> *Biz: +82-31-279-5450*
>
> *E-mail: sy7216.lee@samsung.com*
>
>
>

--001636c92c6053f99404882dfb60
Content-Type: text/html; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable

Not all the URIs in the IMDN-Record-Route, just the 1st one. You then follo=
w the procedure in RFC3261 to route the MESSAGE request.<br><br><div class=
=3D"gmail_quote">2010/6/4 =C0=CC=BD=C2=BF=EB <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sy7216.lee@samsung.com">sy7216.lee@samsung.com</a>&gt;</span><br=
>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">















<div link=3D"blue" vlink=3D"blue" lang=3D"KO">

<div>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">Hi Hisahm,</=
span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">&nbsp;</span=
></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">Thanks for y=
our quick reply.</span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">&nbsp;</span=
></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">If my unders=
tanding is right, you mention
that the Request-URI of IMDN is populated from the SIP From header of the I=
M
and in addition, route set recorded in the IMDN-Record-Route header should =
be
included in the SIP Route
header in order to guarantee to have IMDN traversed through the SIP Proxies
whose address was recorded in the IMDN-Record-Route header.</span></font></=
p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">&nbsp;</span=
></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">My understan=
ding is right?</span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">&nbsp;</span=
></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">Regards,</sp=
an></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">Seungyong</s=
pan></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">&nbsp;</span=
></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"=B1=BC=B8=B2" size=3D"2=
"><span style=3D"font-size: 10pt; color: navy;" lang=3D"EN-US">&nbsp;</span=
></font></p>

<div>

<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><fo=
nt face=3D"=B1=BC=B8=B2" size=3D"3"><span style=3D"font-size: 12pt;" lang=
=3D"EN-US">

<hr align=3D"center" width=3D"100%" size=3D"2">

</span></font></div>

<p class=3D"MsoNormal"><b><font face=3D"Tahoma" size=3D"2"><span style=3D"f=
ont-size: 10pt; font-family: Tahoma; font-weight: bold;" lang=3D"EN-US">Fro=
m:</span></font></b><font face=3D"Tahoma" size=3D"2"><span style=3D"font-si=
ze: 10pt; font-family: Tahoma;" lang=3D"EN-US">
Hisham Khartabil [mailto:<a href=3D"mailto:hisham.khartabil@gmail.com" targ=
et=3D"_blank">hisham.khartabil@gmail.com</a>] <br>
<b><span style=3D"font-weight: bold;">Sent:</span></b> Friday, June 04, 201=
0 11:43 AM<br>
<b><span style=3D"font-weight: bold;">To:</span></b> </span></font><font si=
ze=3D"2"><span style=3D"font-size: 10pt;">=C0=CC=BD=C2=BF=EB</span></font><=
font face=3D"Tahoma" size=3D"2"><span style=3D"font-size: 10pt; font-family=
: Tahoma;" lang=3D"EN-US"><br>

<b><span style=3D"font-weight: bold;">Cc:</span></b> <a href=3D"mailto:ebur=
ger@standardstrack.com" target=3D"_blank">eburger@standardstrack.com</a>;
<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christe=
r.holmberg@ericsson.com</a>; Simple WG<br>
<b><span style=3D"font-weight: bold;">Subject:</span></b> Re: Question abou=
t
RFC5438 wrt OMA CPM</span></font><span lang=3D"EN-US"></span></p>

</div><div><div></div><div class=3D"h5">

<p class=3D"MsoNormal"><font face=3D"=B1=BC=B8=B2" size=3D"3"><span style=
=3D"font-size: 12pt;" lang=3D"EN-US">&nbsp;</span></font></p>

<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><font face=3D"=B1=BC=
=B8=B2" size=3D"3"><span style=3D"font-size: 12pt;" lang=3D"EN-US">Hi,<br>
<br>
Section 12.1.3.1 does mention that the request-uri and the To header field =
in
the IMDN (which is a SIP MESSAGE request) are populated from the From heade=
r
field of the IM (which is a SIP MESSAGE request).<br>
<br>
This is the initial step. You then need to do some processing.<br>
<br>
If there are IMDN-Record-Route headers in the payload of the IM, then you n=
eed
to add the 1st URI of that IMDN-Record-Route header field into the route se=
t of
the IMDN as the last entry (see RFC3261 for route set definition). You then
need to follow RFC3261 for population of Request-URI and Route header field=
s
according to the route set.<br>
<br>
The route set could be initially empty and therefore the only the uri from =
the
IMDN-Record-Route is the only one. Or it could be populated with whatever t=
he
client has pre-configured (for example, an outbound proxy) and therefore th=
e
uri is added to the end f that route set.<br>
<br>
This is normal RFC3261 behaviour.<br>
<br>
Thanks,<br>
Hisham</span></font></p>

<div>

<p class=3D"MsoNormal"><font face=3D"=B1=BC=B8=B2" size=3D"3"><span style=
=3D"font-size: 12pt;" lang=3D"EN-US">2010/6/4</span></font><span lang=3D"EN=
-US"> </span>=C0=CC=BD=C2=BF=EB<span lang=3D"EN-US"> &lt;<a href=3D"mailto:=
sy7216.lee@samsung.com" target=3D"_blank">sy7216.lee@samsung.com</a>&gt;</s=
pan></p>


<div link=3D"blue" vlink=3D"purple">

<div>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Dear Eric Burger, =
Hisham Khartabil and Christer Holmberg,</span></font></b><span lang=3D"EN-U=
S"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">This is Seungyong =
Lee from Samsung Electronics and in charge
of OMA(Open Mobile Alliance)
CPM (Converged-IP Messaging).</span></font></b><span lang=3D"EN-US"></span>=
</p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">CPM 1.0 supports I=
MDN for requesting/receiving delivery
notifications and read reports. </span></font></b><span lang=3D"EN-US"></sp=
an></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">In the last CPM me=
eting (in MAY) there was a heated debate
about IMDN routing, especially how to populate the Request-URI of IMDN.</sp=
an></font></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">A delegate from Er=
icsson argued on the basis of the e-mail
thread (</span></font></b><font face=3D"Arial"><span style=3D"font-family: =
Arial;" lang=3D"EN-US">see <a href=3D"http://www.ietf.org/mail-archive/web/=
simple/current/msg08759.html" target=3D"_blank">http://www.ietf.org/mail-ar=
chive/web/simple/current/msg08759.html</a></span></font><b><span style=3D"f=
ont-weight: bold;" lang=3D"EN-US">) that the Request-URI of IMDN should be
set to the top-most address of IMDN-Record-Router header in the received IM
where as Samsung retorted that the Request-URI is populated from SIP From
header of the received IM, which is based on section 12.1.3.1 in RFC5438.</=
span></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Section 12.1.3.1 s=
ays </span></font></b><b><font face=3D"Times New Roman"><span style=3D"font=
-family: &quot;Times New Roman&quot;; font-weight: bold;" lang=3D"EN-US">&l=
dquo;&hellip;</span></font><span lang=3D"EN-US">snip</span></b><b><font fac=
e=3D"Times New Roman"><span style=3D"font-family: &quot;Times New Roman&quo=
t;; font-weight: bold;" lang=3D"EN-US">&hellip;</span></font><span lang=3D"=
EN-US"> For IMDNs, the IM Recipient
populates the SIP Request-URI and the SIP To header field using the address
that appeared in the SIP From header field in the IM.</span></b><b><font fa=
ce=3D"Times New Roman"><span style=3D"font-family: &quot;Times New Roman&qu=
ot;; font-weight: bold;" lang=3D"EN-US">&rdquo;</span></font></b><span lang=
=3D"EN-US"></span></p>


<p class=3D"MsoNormal"><b><font face=3D"=B9=D9=C5=C1" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">The
routing mechanism of IMDN that I</span></font></b><b><font face=3D"Arial"><=
span style=3D"font-family: Arial; font-weight: bold;" lang=3D"EN-US">&rsquo=
;</span></font><span lang=3D"EN-US">m thinking of is very similar with the =
SIP routing. That is,
Request-URI is populated from SIP From header and also SIP Route header is =
from IMDN-Route
header. Because it is SIP headers that is used for routing in SIP/IP core, =
some
CPIM headers for IMDN (e.g. IMDN Route header) needs to be reflected in SIP
headers (e.g. SIP Route header).</span></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Could
you let me know your intended routing scenario from RFC5438 authors</span><=
/font></b><b><font face=3D"Arial"><span style=3D"font-family: Arial; font-w=
eight: bold;" lang=3D"EN-US">&rsquo;</span></font><span lang=3D"EN-US"> per=
spective?</span></b><span lang=3D"EN-US"></span></p>


<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Your
quick reply would be so much appreciated and helpful to complete CPM 1.0
without delay.</span></font></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Thanks</span></fon=
t></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Sincerely,</span><=
/font></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">&nbsp;</span></fon=
t></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Seungyong
Lee</span></font></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">Samsung
Electronics</span></font></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"EN-US">DMC
Research Lab</span></font></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"FR">Biz:
+82-31-279-5450</span></font></b><span lang=3D"EN-US"></span></p>

<p class=3D"MsoNormal"><b><font face=3D"=B1=BC=B8=B2" size=3D"2"><span styl=
e=3D"font-size: 10pt; font-weight: bold;" lang=3D"FR">E-mail: <a href=3D"ma=
ilto:sy7216.lee@samsung.com" target=3D"_blank">sy7216.lee@samsung.com</a></=
span></font></b><span lang=3D"EN-US"></span></p>


</div>

</div>

</div>

<p class=3D"MsoNormal"><font face=3D"=B1=BC=B8=B2" size=3D"3"><span style=
=3D"font-size: 12pt;" lang=3D"EN-US">&nbsp;</span></font></p>

</div></div></div>

</div>


</blockquote></div><br>

--001636c92c6053f99404882dfb60--

From ben@nostrum.com  Fri Jun  4 07:14:33 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 B35473A694C for <simple@core3.amsl.com>; Fri,  4 Jun 2010 07:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.132
X-Spam-Level: *
X-Spam-Status: No, score=1.132 tagged_above=-999 required=5 tests=[AWL=-1.318,  BAYES_50=0.001, MIME_CHARSET_FARAWAY=2.45, 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 IeixGLwHYuqT for <simple@core3.amsl.com>; Fri,  4 Jun 2010 07:14:32 -0700 (PDT)
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 2362228C124 for <simple@ietf.org>; Fri,  4 Jun 2010 07:14:30 -0700 (PDT)
Received: from [10.0.1.9] (adsl-68-94-10-95.dsl.rcsntx.swbell.net [68.94.10.95]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o54EEDjZ049954 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 4 Jun 2010 09:14:14 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=euc-kr
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <AANLkTiluy6D51MFbDmQhIBSseIx37irCyQN_YLrOHl3g@mail.gmail.com>
Date: Fri, 4 Jun 2010 09:14:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <602F3A08-1857-4EE8-9C7B-F4B61BE90179@nostrum.com>
References: <AANLkTimVxbJZtdpyA-6huNLoVQPetu5P1kCoNrmU9pkD@mail.gmail.com> <0L3G00G7PZHPUP@mmp1.samsung.com> <AANLkTiluy6D51MFbDmQhIBSseIx37irCyQN_YLrOHl3g@mail.gmail.com>
To: Hisham Khartabil <hisham.khartabil@gmail.com>
X-Mailer: Apple Mail (2.1078)
Received-SPF: pass (nostrum.com: 68.94.10.95 is authenticated by a trusted mechanism)
Cc: =?utf-8?B?7J207Iq57Jqp?= <sy7216.lee@samsung.com>, Simple WG <simple@ietf.org>
Subject: Re: [Simple] Question about RFC5438 wrt OMA CPM
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: Fri, 04 Jun 2010 14:14:33 -0000

With all due respects to Hisham as an author of the RFC, I have to =
disagree with this position. The described behavior mixes layers between =
SIP and IM/IMDN.

Section 7.2.1, paragraph 4, says:

"If IMDN-Record-Route header fields appear in the IM,
   the IM Recipient constructing the IMDN MUST copy the contents of the
   IMDN-Record-Route header fields into IMDN-Route header fields in the
   IMDN and maintain their order.  The IMDN is then sent to the URI in
   the top IMDN-Route header field."

So the operative question is what is mean by "send to the URI". In SIP, =
"send to the URI" means to put that URI in the request-URI. Basically =
we're talking about sending a SIP MESSAGE request that is targeted to =
the IM intermediary. Note that such an intermediary is an endpoint from =
the SIP perspective, not a SIP proxy. It is up to that intermediary to =
forward the IMDN by sending a _new_ MESSAGE request to the now top-most =
IMDN-Route value.

Keep in mind there may be any number of SIP proxies between the IMDN =
sender and the IM intermediary, and there may in fact be preloaded SIP =
Route headers pointing to these. But that should have nothing to do with =
IMDN-Route processing.


Thanks!

Ben.




On Jun 4, 2010, at 12:56 AM, Hisham Khartabil wrote:

> Not all the URIs in the IMDN-Record-Route, just the 1st one. You then =
follow the procedure in RFC3261 to route the MESSAGE request.
>=20
> 2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>
> Hi Hisahm,
>=20
> =20
> Thanks for your quick reply.
>=20
> =20
> If my understanding is right, you mention that the Request-URI of IMDN =
is populated from the SIP =46rom header of the IM and in addition, route =
set recorded in the IMDN-Record-Route header should be included in the =
SIP Route header in order to guarantee to have IMDN traversed through =
the SIP Proxies whose address was recorded in the IMDN-Record-Route =
header.
>=20
> =20
> My understanding is right?
>=20
> =20
> Regards,
>=20
> Seungyong
>=20
> =20
> =20
> From: Hisham Khartabil [mailto:hisham.khartabil@gmail.com]=20
> Sent: Friday, June 04, 2010 11:43 AM
> To: =C0=CC=BD=C2=BF=EB
> Cc: eburger@standardstrack.com; christer.holmberg@ericsson.com; Simple =
WG
> Subject: Re: Question about RFC5438 wrt OMA CPM
>=20
> =20
> Hi,
>=20
> Section 12.1.3.1 does mention that the request-uri and the To header =
field in the IMDN (which is a SIP MESSAGE request) are populated from =
the =46rom header field of the IM (which is a SIP MESSAGE request).
>=20
> This is the initial step. You then need to do some processing.
>=20
> If there are IMDN-Record-Route headers in the payload of the IM, then =
you need to add the 1st URI of that IMDN-Record-Route header field into =
the route set of the IMDN as the last entry (see RFC3261 for route set =
definition). You then need to follow RFC3261 for population of =
Request-URI and Route header fields according to the route set.
>=20
> The route set could be initially empty and therefore the only the uri =
from the IMDN-Record-Route is the only one. Or it could be populated =
with whatever the client has pre-configured (for example, an outbound =
proxy) and therefore the uri is added to the end f that route set.
>=20
> This is normal RFC3261 behaviour.
>=20
> Thanks,
> Hisham
>=20
> 2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>
>=20
> Dear Eric Burger, Hisham Khartabil and Christer Holmberg,
>=20
> =20
>=20
> This is Seungyong Lee from Samsung Electronics and in charge of =
OMA(Open Mobile Alliance) CPM (Converged-IP Messaging).
>=20
> CPM 1.0 supports IMDN for requesting/receiving delivery notifications =
and read reports.
>=20
> In the last CPM meeting (in MAY) there was a heated debate about IMDN =
routing, especially how to populate the Request-URI of IMDN.
>=20
> =20
>=20
> A delegate from Ericsson argued on the basis of the e-mail thread (see =
http://www.ietf.org/mail-archive/web/simple/current/msg08759.html) that =
the Request-URI of IMDN should be set to the top-most address of =
IMDN-Record-Router header in the received IM where as Samsung retorted =
that the Request-URI is populated from SIP =46rom header of the received =
IM, which is based on section 12.1.3.1 in RFC5438.
>=20
> Section 12.1.3.1 says =A1=B0=A1=A6snip=A1=A6 For IMDNs, the IM =
Recipient populates the SIP Request-URI and the SIP To header field =
using the address that appeared in the SIP =46rom header field in the =
IM.=A1=B1
>=20
> =20
>=20
> The routing mechanism of IMDN that I=A1=AFm thinking of is very =
similar with the SIP routing. That is, Request-URI is populated from SIP =
=46rom header and also SIP Route header is from IMDN-Route header. =
Because it is SIP headers that is used for routing in SIP/IP core, some =
CPIM headers for IMDN (e.g. IMDN Route header) needs to be reflected in =
SIP headers (e.g. SIP Route header).
>=20
> =20
>=20
> Could you let me know your intended routing scenario from RFC5438 =
authors=A1=AF perspective?
>=20
> Your quick reply would be so much appreciated and helpful to complete =
CPM 1.0 without delay.
>=20
> =20
>=20
> Thanks
>=20
> Sincerely,
>=20
> =20
>=20
> Seungyong Lee
>=20
> Samsung Electronics
>=20
> DMC Research Lab
>=20
> Biz: +82-31-279-5450
>=20
> E-mail: sy7216.lee@samsung.com
>=20
> =20
>=20
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


From hisham.khartabil@gmail.com  Fri Jun  4 19:14:12 2010
Return-Path: <hisham.khartabil@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 4C7393A6833 for <simple@core3.amsl.com>; Fri,  4 Jun 2010 19:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.644
X-Spam-Level: ***
X-Spam-Status: No, score=3.644 tagged_above=-999 required=5 tests=[AWL=0.592,  BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_CHARSET_FARAWAY=2.45]
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 HG3N2SOm0M-7 for <simple@core3.amsl.com>; Fri,  4 Jun 2010 19:13:59 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 9C3D83A686C for <simple@ietf.org>; Fri,  4 Jun 2010 19:13:59 -0700 (PDT)
Received: by gyh4 with SMTP id 4so1412117gyh.31 for <simple@ietf.org>; Fri, 04 Jun 2010 19:13:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=WdTqN4ayAuF4wEJwKPGSVsLEus5CDBIfiyL/O8kzZ2o=; b=a+ccnE66ViZB1386yEI1ZadInB1OKmSn2hm0aSJ3nKtiUjTWQSBZ9KIcxfflxpNL/s ZZh6jqbUcG3DufL3tUignMb4jPgdRZ62P/gjTniJs2/ubu3aAUThMKTIWVCkOfh0+/Or UIXeNO7gCkEPWFOSS0V6yOPzPkwn5SnSGsL1U=
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; b=EqkhWMLWWNdBk35i5ncPUzCpGV46RVxC976ErpFBKnLjaWDEH7QLuKDsT1jNsTWTX6 138ZU32QjF/qEpoUbqSJnqgiYKQq4IgfidEFpT0Sti+v9i8HKjzqaJZ4GI9Jxg6cw1GA 4cJHw5YVeW98/Gc3QzAedMVTTMvMaHUC14URI=
MIME-Version: 1.0
Received: by 10.101.10.9 with SMTP id n9mr12931291ani.113.1275704022808; Fri,  04 Jun 2010 19:13:42 -0700 (PDT)
Received: by 10.100.11.17 with HTTP; Fri, 4 Jun 2010 19:13:42 -0700 (PDT)
In-Reply-To: <602F3A08-1857-4EE8-9C7B-F4B61BE90179@nostrum.com>
References: <AANLkTimVxbJZtdpyA-6huNLoVQPetu5P1kCoNrmU9pkD@mail.gmail.com> <0L3G00G7PZHPUP@mmp1.samsung.com> <AANLkTiluy6D51MFbDmQhIBSseIx37irCyQN_YLrOHl3g@mail.gmail.com> <602F3A08-1857-4EE8-9C7B-F4B61BE90179@nostrum.com>
Date: Sat, 5 Jun 2010 12:13:42 +1000
Message-ID: <AANLkTinQfm2AzGmXkTZC9RwmUTYrn5qgnoTo9Dzm4Su9@mail.gmail.com>
From: Hisham Khartabil <hisham.khartabil@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=0016e6d27c681e3aa904883efd42
Cc: =?EUC-KR?B?wMy9wr/r?= <sy7216.lee@samsung.com>, Simple WG <simple@ietf.org>
Subject: Re: [Simple] Question about RFC5438 wrt OMA CPM
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: Sat, 05 Jun 2010 02:14:12 -0000

--0016e6d27c681e3aa904883efd42
Content-Type: text/plain; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable

Ben,

I'm trying to make sense of why that last sentence in section 12.1.3.1 was
added (obviously in a later version of the draft).

What you describe is not much different than what I described. The
IMDN-Route value will end up in the Request-URI either way. It will be put
there either by the UAC as part of the "sending" prcedure or by a SIP proxy
on the path. The only minor issue here is that you will have a SIP Route
header carrying the final recepient's URI (which was copied from the IM Fro=
m
header).th that of X.

After some thinking, I can't find a reason why that sentence in section
12.1.3.1 was placed there. The thinking could've been that this is a new SI=
P
MESSAGE request and RFC3261 sections 8.1.1.1 and 8.1.1.2 suggests putting
the logical address of the final recipient in there.

In any case, unless someone objects, I have no issue in creating and errata
on RFC5438 striking out that sentence and adding modification text along th=
e
times of what Ben describes the behaviour should be. I don't it makes such
of a difference either way.

Regards,
Hisham

2010/6/5 Ben Campbell <ben@nostrum.com>

> With all due respects to Hisham as an author of the RFC, I have to disagr=
ee
> with this position. The described behavior mixes layers between SIP and
> IM/IMDN.
>
> Section 7.2.1, paragraph 4, says:
>
> "If IMDN-Record-Route header fields appear in the IM,
>   the IM Recipient constructing the IMDN MUST copy the contents of the
>   IMDN-Record-Route header fields into IMDN-Route header fields in the
>   IMDN and maintain their order.  The IMDN is then sent to the URI in
>   the top IMDN-Route header field."
>
> So the operative question is what is mean by "send to the URI". In SIP,
> "send to the URI" means to put that URI in the request-URI. Basically we'=
re
> talking about sending a SIP MESSAGE request that is targeted to the IM
> intermediary. Note that such an intermediary is an endpoint from the SIP
> perspective, not a SIP proxy. It is up to that intermediary to forward th=
e
> IMDN by sending a _new_ MESSAGE request to the now top-most IMDN-Route
> value.
>
> Keep in mind there may be any number of SIP proxies between the IMDN send=
er
> and the IM intermediary, and there may in fact be preloaded SIP Route
> headers pointing to these. But that should have nothing to do with
> IMDN-Route processing.
>
>
> Thanks!
>
> Ben.
>
>
>
>
> On Jun 4, 2010, at 12:56 AM, Hisham Khartabil wrote:
>
> > Not all the URIs in the IMDN-Record-Route, just the 1st one. You then
> follow the procedure in RFC3261 to route the MESSAGE request.
> >
> > 2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>
> > Hi Hisahm,
> >
> >
> > Thanks for your quick reply.
> >
> >
> > If my understanding is right, you mention that the Request-URI of IMDN =
is
> populated from the SIP From header of the IM and in addition, route set
> recorded in the IMDN-Record-Route header should be included in the SIP Ro=
ute
> header in order to guarantee to have IMDN traversed through the SIP Proxi=
es
> whose address was recorded in the IMDN-Record-Route header.
> >
> >
> > My understanding is right?
> >
> >
> > Regards,
> >
> > Seungyong
> >
> >
> >
> > From: Hisham Khartabil [mailto:hisham.khartabil@gmail.com]
> > Sent: Friday, June 04, 2010 11:43 AM
> > To: =C0=CC=BD=C2=BF=EB
> > Cc: eburger@standardstrack.com; christer.holmberg@ericsson.com; Simple
> WG
> > Subject: Re: Question about RFC5438 wrt OMA CPM
> >
> >
> > Hi,
> >
> > Section 12.1.3.1 does mention that the request-uri and the To header
> field in the IMDN (which is a SIP MESSAGE request) are populated from the
> From header field of the IM (which is a SIP MESSAGE request).
> >
> > This is the initial step. You then need to do some processing.
> >
> > If there are IMDN-Record-Route headers in the payload of the IM, then y=
ou
> need to add the 1st URI of that IMDN-Record-Route header field into the
> route set of the IMDN as the last entry (see RFC3261 for route set
> definition). You then need to follow RFC3261 for population of Request-UR=
I
> and Route header fields according to the route set.
> >
> > The route set could be initially empty and therefore the only the uri
> from the IMDN-Record-Route is the only one. Or it could be populated with
> whatever the client has pre-configured (for example, an outbound proxy) a=
nd
> therefore the uri is added to the end f that route set.
> >
> > This is normal RFC3261 behaviour.
> >
> > Thanks,
> > Hisham
> >
> > 2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>
> >
> > Dear Eric Burger, Hisham Khartabil and Christer Holmberg,
> >
> >
> >
> > This is Seungyong Lee from Samsung Electronics and in charge of OMA(Ope=
n
> Mobile Alliance) CPM (Converged-IP Messaging).
> >
> > CPM 1.0 supports IMDN for requesting/receiving delivery notifications a=
nd
> read reports.
> >
> > In the last CPM meeting (in MAY) there was a heated debate about IMDN
> routing, especially how to populate the Request-URI of IMDN.
> >
> >
> >
> > A delegate from Ericsson argued on the basis of the e-mail thread (see
> http://www.ietf.org/mail-archive/web/simple/current/msg08759.html) that
> the Request-URI of IMDN should be set to the top-most address of
> IMDN-Record-Router header in the received IM where as Samsung retorted th=
at
> the Request-URI is populated from SIP From header of the received IM, whi=
ch
> is based on section 12.1.3.1 in RFC5438.
> >
> > Section 12.1.3.1 says =A1=B0=A1=A6snip=A1=A6 For IMDNs, the IM Recipien=
t populates the
> SIP Request-URI and the SIP To header field using the address that appear=
ed
> in the SIP From header field in the IM.=A1=B1
> >
> >
> >
> > The routing mechanism of IMDN that I=A1=AFm thinking of is very similar=
 with
> the SIP routing. That is, Request-URI is populated from SIP From header a=
nd
> also SIP Route header is from IMDN-Route header. Because it is SIP header=
s
> that is used for routing in SIP/IP core, some CPIM headers for IMDN (e.g.
> IMDN Route header) needs to be reflected in SIP headers (e.g. SIP Route
> header).
> >
> >
> >
> > Could you let me know your intended routing scenario from RFC5438
> authors=A1=AF perspective?
> >
> > Your quick reply would be so much appreciated and helpful to complete C=
PM
> 1.0 without delay.
> >
> >
> >
> > Thanks
> >
> > Sincerely,
> >
> >
> >
> > Seungyong Lee
> >
> > Samsung Electronics
> >
> > DMC Research Lab
> >
> > Biz: +82-31-279-5450
> >
> > E-mail: sy7216.lee@samsung.com
> >
> >
> >
> > _______________________________________________
> > Simple mailing list
> > Simple@ietf.org
> > https://www.ietf.org/mailman/listinfo/simple
>
>

--0016e6d27c681e3aa904883efd42
Content-Type: text/html; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable

Ben,<br><br>I&#39;m trying to make sense of why that last sentence in secti=
on 12.1.3.1 was added (obviously in a later version of the draft).<br><br>W=
hat you describe is not much different than what I described. The IMDN-Rout=
e value will end up in the Request-URI either way. It will be put there eit=
her by the UAC as part of the &quot;sending&quot; prcedure or by a SIP prox=
y on the path. The only minor issue here is that you will have a SIP Route =
header carrying the final recepient&#39;s URI (which was copied from the IM=
 From header).th that of X.<br>
<br>After some thinking, I can&#39;t find a reason why that sentence in sec=
tion 12.1.3.1 was placed there. The thinking could&#39;ve been that this is=
 a new SIP MESSAGE request and RFC3261 sections 8.1.1.1 and 8.1.1.2 suggest=
s putting the logical address of the final recipient in there.<br>
<br>In any case, unless someone objects, I have no issue in creating and er=
rata on RFC5438 striking out that sentence and adding modification text alo=
ng the times of what Ben describes the behaviour should be. I don&#39;t it =
makes such of a difference either way.<br>
<br>Regards,<br>Hisham<br><br><div class=3D"gmail_quote">2010/6/5 Ben Campb=
ell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.co=
m</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margin: 0pt =
0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex=
;">
With all due respects to Hisham as an author of the RFC, I have to disagree=
 with this position. The described behavior mixes layers between SIP and IM=
/IMDN.<br>
<br>
Section 7.2.1, paragraph 4, says:<br>
<br>
&quot;If IMDN-Record-Route header fields appear in the IM,<br>
 &nbsp; the IM Recipient constructing the IMDN MUST copy the contents of th=
e<br>
 &nbsp; IMDN-Record-Route header fields into IMDN-Route header fields in th=
e<br>
 &nbsp; IMDN and maintain their order. &nbsp;The IMDN is then sent to the U=
RI in<br>
 &nbsp; the top IMDN-Route header field.&quot;<br>
<br>
So the operative question is what is mean by &quot;send to the URI&quot;. I=
n SIP, &quot;send to the URI&quot; means to put that URI in the request-URI=
. Basically we&#39;re talking about sending a SIP MESSAGE request that is t=
argeted to the IM intermediary. Note that such an intermediary is an endpoi=
nt from the SIP perspective, not a SIP proxy. It is up to that intermediary=
 to forward the IMDN by sending a _new_ MESSAGE request to the now top-most=
 IMDN-Route value.<br>

<br>
Keep in mind there may be any number of SIP proxies between the IMDN sender=
 and the IM intermediary, and there may in fact be preloaded SIP Route head=
ers pointing to these. But that should have nothing to do with IMDN-Route p=
rocessing.<br>

<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<div><div></div><div class=3D"h5"><br>
<br>
<br>
<br>
On Jun 4, 2010, at 12:56 AM, Hisham Khartabil wrote:<br>
<br>
&gt; Not all the URIs in the IMDN-Record-Route, just the 1st one. You then =
follow the procedure in RFC3261 to route the MESSAGE request.<br>
&gt;<br>
&gt; 2010/6/4 =C0=CC=BD=C2=BF=EB &lt;<a href=3D"mailto:sy7216.lee@samsung.c=
om">sy7216.lee@samsung.com</a>&gt;<br>
&gt; Hi Hisahm,<br>
&gt;<br>
&gt;<br>
&gt; Thanks for your quick reply.<br>
&gt;<br>
&gt;<br>
&gt; If my understanding is right, you mention that the Request-URI of IMDN=
 is populated from the SIP From header of the IM and in addition, route set=
 recorded in the IMDN-Record-Route header should be included in the SIP Rou=
te header in order to guarantee to have IMDN traversed through the SIP Prox=
ies whose address was recorded in the IMDN-Record-Route header.<br>

&gt;<br>
&gt;<br>
&gt; My understanding is right?<br>
&gt;<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Seungyong<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: Hisham Khartabil [mailto:<a href=3D"mailto:hisham.khartabil@gmai=
l.com">hisham.khartabil@gmail.com</a>]<br>
&gt; Sent: Friday, June 04, 2010 11:43 AM<br>
&gt; To: =C0=CC=BD=C2=BF=EB<br>
&gt; Cc: <a href=3D"mailto:eburger@standardstrack.com">eburger@standardstra=
ck.com</a>; <a href=3D"mailto:christer.holmberg@ericsson.com">christer.holm=
berg@ericsson.com</a>; Simple WG<br>
&gt; Subject: Re: Question about RFC5438 wrt OMA CPM<br>
&gt;<br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt; Section 12.1.3.1 does mention that the request-uri and the To header f=
ield in the IMDN (which is a SIP MESSAGE request) are populated from the Fr=
om header field of the IM (which is a SIP MESSAGE request).<br>
&gt;<br>
&gt; This is the initial step. You then need to do some processing.<br>
&gt;<br>
&gt; If there are IMDN-Record-Route headers in the payload of the IM, then =
you need to add the 1st URI of that IMDN-Record-Route header field into the=
 route set of the IMDN as the last entry (see RFC3261 for route set definit=
ion). You then need to follow RFC3261 for population of Request-URI and Rou=
te header fields according to the route set.<br>

&gt;<br>
&gt; The route set could be initially empty and therefore the only the uri =
from the IMDN-Record-Route is the only one. Or it could be populated with w=
hatever the client has pre-configured (for example, an outbound proxy) and =
therefore the uri is added to the end f that route set.<br>

&gt;<br>
&gt; This is normal RFC3261 behaviour.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Hisham<br>
&gt;<br>
&gt; 2010/6/4 =C0=CC=BD=C2=BF=EB &lt;<a href=3D"mailto:sy7216.lee@samsung.c=
om">sy7216.lee@samsung.com</a>&gt;<br>
&gt;<br>
&gt; Dear Eric Burger, Hisham Khartabil and Christer Holmberg,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; This is Seungyong Lee from Samsung Electronics and in charge of OMA(Op=
en Mobile Alliance) CPM (Converged-IP Messaging).<br>
&gt;<br>
&gt; CPM 1.0 supports IMDN for requesting/receiving delivery notifications =
and read reports.<br>
&gt;<br>
&gt; In the last CPM meeting (in MAY) there was a heated debate about IMDN =
routing, especially how to populate the Request-URI of IMDN.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; A delegate from Ericsson argued on the basis of the e-mail thread (see=
 <a href=3D"http://www.ietf.org/mail-archive/web/simple/current/msg08759.ht=
ml" target=3D"_blank">http://www.ietf.org/mail-archive/web/simple/current/m=
sg08759.html</a>) that the Request-URI of IMDN should be set to the top-mos=
t address of IMDN-Record-Router header in the received IM where as Samsung =
retorted that the Request-URI is populated from SIP From header of the rece=
ived IM, which is based on section 12.1.3.1 in RFC5438.<br>

&gt;<br>
&gt; Section 12.1.3.1 says &ldquo;&hellip;snip&hellip; For IMDNs, the IM Re=
cipient populates the SIP Request-URI and the SIP To header field using the=
 address that appeared in the SIP From header field in the IM.&rdquo;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The routing mechanism of IMDN that I&rsquo;m thinking of is very simil=
ar with the SIP routing. That is, Request-URI is populated from SIP From he=
ader and also SIP Route header is from IMDN-Route header. Because it is SIP=
 headers that is used for routing in SIP/IP core, some CPIM headers for IMD=
N (e.g. IMDN Route header) needs to be reflected in SIP headers (e.g. SIP R=
oute header).<br>

&gt;<br>
&gt;<br>
&gt;<br>
&gt; Could you let me know your intended routing scenario from RFC5438 auth=
ors&rsquo; perspective?<br>
&gt;<br>
&gt; Your quick reply would be so much appreciated and helpful to complete =
CPM 1.0 without delay.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt; Sincerely,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Seungyong Lee<br>
&gt;<br>
&gt; Samsung Electronics<br>
&gt;<br>
&gt; DMC Research Lab<br>
&gt;<br>
&gt; Biz: +82-31-279-5450<br>
&gt;<br>
&gt; E-mail: <a href=3D"mailto:sy7216.lee@samsung.com">sy7216.lee@samsung.c=
om</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div>&gt; _______________________________________________<br>
&gt; Simple mailing list<br>
&gt; <a href=3D"mailto:Simple@ietf.org">Simple@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/simple" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/simple</a><br>
<br>
</blockquote></div><br>

--0016e6d27c681e3aa904883efd42--

From wwwrun@core3.amsl.com  Mon Jun  7 07:43:21 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: simple@ietf.org
Delivered-To: simple@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id D9A493A67C3; Mon,  7 Jun 2010 07:40:42 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100607144321.D9A493A67C3@core3.amsl.com>
Date: Mon,  7 Jun 2010 07:40:42 -0700 (PDT)
Cc: simple@ietf.org
Subject: [Simple] Last Call: draft-ietf-simple-msrp-sessmatch (Session Matching Update for the Message Session Relay Protocol (MSRP)) to Proposed Standard
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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, 07 Jun 2010 14:43:22 -0000

The IESG has received a request from the SIP for Instant Messaging and 
Presence Leveraging Extensions WG (simple) to consider the following document:

- 'Session Matching Update for the Message Session Relay Protocol (MSRP) '
   <draft-ietf-simple-msrp-sessmatch-06.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-06-21. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-sessmatch-06.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=19446&rfc_flag=0


From wwwrun@core3.amsl.com  Mon Jun  7 07:43:21 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: simple@ietf.org
Delivered-To: simple@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id DEA283A814B; Mon,  7 Jun 2010 07:39:58 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100607144321.DEA283A814B@core3.amsl.com>
Date: Mon,  7 Jun 2010 07:39:58 -0700 (PDT)
Cc: simple@ietf.org
Subject: [Simple] Last Call: draft-ietf-simple-msrp-acm (An Alternative Connection Model for the Message Session Relay Protocol (MSRP)) to Proposed Standard
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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, 07 Jun 2010 14:43:22 -0000

The IESG has received a request from the SIP for Instant Messaging and 
Presence Leveraging Extensions WG (simple) to consider the following document:

- 'An Alternative Connection Model for the Message Session Relay Protocol 
   (MSRP) '
   <draft-ietf-simple-msrp-acm-09.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-06-21. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-acm-09.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18161&rfc_flag=0


From sy7216.lee@samsung.com  Thu Jun  3 20:11:00 2010
Return-Path: <sy7216.lee@samsung.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 DAE013A688A for <simple@core3.amsl.com>; Thu,  3 Jun 2010 20:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.43
X-Spam-Level: ****
X-Spam-Status: No, score=4.43 tagged_above=-999 required=5 tests=[BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4,  RELAY_IS_203=0.994]
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 1NVQ1MnfzyLG for <simple@core3.amsl.com>; Thu,  3 Jun 2010 20:10:55 -0700 (PDT)
Received: from mailout5.samsung.com (mailout5.samsung.com [203.254.224.35]) by core3.amsl.com (Postfix) with ESMTP id 33A9E3A6782 for <simple@ietf.org>; Thu,  3 Jun 2010 20:10:52 -0700 (PDT)
Received: from epmmp1 (mailout5.samsung.com [203.254.224.35]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0L3G00IMVZHPEA@mailout1.samsung.com> for simple@ietf.org; Fri, 04 Jun 2010 12:10:38 +0900 (KST)
Received: from retail ([168.219.197.176]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0L3G00G7OZHPUP@mmp1.samsung.com> for simple@ietf.org; Fri, 04 Jun 2010 12:10:37 +0900 (KST)
Date: Fri, 04 Jun 2010 12:10:31 +0900
From: =?ks_c_5601-1987?B?wMy9wr/r?= <sy7216.lee@samsung.com>
In-reply-to: <AANLkTimVxbJZtdpyA-6huNLoVQPetu5P1kCoNrmU9pkD@mail.gmail.com>
To: 'Hisham Khartabil' <hisham.khartabil@gmail.com>
Message-id: <0L3G00G7PZHPUP@mmp1.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: multipart/alternative; boundary="Boundary_(ID_Vhc5BkA2I9rH2W5mF0jTGA)"
Thread-index: AcsDj5hEBNI6ecPBRrmA3Esg9DLZpQAApSqw
X-Mailman-Approved-At: Mon, 07 Jun 2010 08:22:56 -0700
Cc: 'Simple WG' <simple@ietf.org>
Subject: Re: [Simple] Question about RFC5438 wrt OMA CPM
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: Fri, 04 Jun 2010 04:59:05 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_Vhc5BkA2I9rH2W5mF0jTGA)
Content-type: text/plain; charset=ks_c_5601-1987
Content-transfer-encoding: quoted-printable

Hi Hisahm,

=20

Thanks for your quick reply.

=20

If my understanding is right, you mention that the Request-URI of IMDN =
is
populated from the SIP From header of the IM and in addition, route set
recorded in the IMDN-Record-Route header should be included in the SIP
Route header in order to guarantee to have IMDN traversed through the =
SIP
Proxies whose address was recorded in the IMDN-Record-Route header.

=20

My understanding is right?

=20

Regards,

Seungyong

=20

=20

  _____ =20

From: Hisham Khartabil [mailto:hisham.khartabil@gmail.com]=20
Sent: Friday, June 04, 2010 11:43 AM
To: =C0=CC=BD=C2=BF=EB
Cc: eburger@standardstrack.com; christer.holmberg@ericsson.com; Simple =
WG
Subject: Re: Question about RFC5438 wrt OMA CPM

=20

Hi,

Section 12.1.3.1 does mention that the request-uri and the To header =
field
in the IMDN (which is a SIP MESSAGE request) are populated from the From
header field of the IM (which is a SIP MESSAGE request).

This is the initial step. You then need to do some processing.

If there are IMDN-Record-Route headers in the payload of the IM, then =
you
need to add the 1st URI of that IMDN-Record-Route header field into the
route set of the IMDN as the last entry (see RFC3261 for route set
definition). You then need to follow RFC3261 for population of =
Request-URI
and Route header fields according to the route set.

The route set could be initially empty and therefore the only the uri =
from
the IMDN-Record-Route is the only one. Or it could be populated with
whatever the client has pre-configured (for example, an outbound proxy) =
and
therefore the uri is added to the end f that route set.

This is normal RFC3261 behaviour.

Thanks,
Hisham

2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>

Dear Eric Burger, Hisham Khartabil and Christer Holmberg,

=20

This is Seungyong Lee from Samsung Electronics and in charge of OMA(Open
Mobile Alliance) CPM (Converged-IP Messaging).

CPM 1.0 supports IMDN for requesting/receiving delivery notifications =
and
read reports.=20

In the last CPM meeting (in MAY) there was a heated debate about IMDN
routing, especially how to populate the Request-URI of IMDN.

=20

A delegate from Ericsson argued on the basis of the e-mail thread (see
http://www.ietf.org/mail-archive/web/simple/current/msg08759.html) that =
the
Request-URI of IMDN should be set to the top-most address of =
IMDN-Record-
Router header in the received IM where as Samsung retorted that the =
Request-
URI is populated from SIP From header of the received IM, which is based =
on
section 12.1.3.1 in RFC5438.

Section 12.1.3.1 says =A1=B0=A1=A6snip=A1=A6 For IMDNs, the IM Recipient =
populates the
SIP Request-URI and the SIP To header field using the address that =
appeared
in the SIP From header field in the IM.=A1=B1

=20

The routing mechanism of IMDN that I=A1=AFm thinking of is very similar =
with
the SIP routing. That is, Request-URI is populated from SIP From header =
and
also SIP Route header is from IMDN-Route header. Because it is SIP =
headers
that is used for routing in SIP/IP core, some CPIM headers for IMDN =
(e.g.
IMDN Route header) needs to be reflected in SIP headers (e.g. SIP Route
header).

=20

Could you let me know your intended routing scenario from RFC5438 =
authors=A1=AF
perspective?

Your quick reply would be so much appreciated and helpful to complete =
CPM 1.
0 without delay.

=20

Thanks

Sincerely,

=20

Seungyong Lee

Samsung Electronics

DMC Research Lab

Biz: +82-31-279-5450

E-mail: sy7216.lee@samsung.com

=20


--Boundary_(ID_Vhc5BkA2I9rH2W5mF0jTGA)
Content-type: text/html; charset=ks_c_5601-1987
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dks_c_5601-1987">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"date"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"time"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:=B9=D9=C5=C1;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:=B1=BC=B8=B2;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@=B1=BC=B8=B2";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@=B9=D9=C5=C1";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=B1=BC=B8=B2;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:=B1=BC=B8=B2;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:99.25pt 3.0cm 3.0cm 3.0cm;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DKO link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'>Hi =
Hisahm,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'>Thanks for your quick =
reply.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'>If my understanding is right, you =
mention
that the Request-URI of IMDN is populated from the SIP From header of =
the IM
and in addition, route set recorded in the IMDN-Record-Route header =
should be
included in the <st1:Street w:st=3D"on"><st1:address w:st=3D"on">SIP =
Route</st1:address></st1:Street>
header in order to guarantee to have IMDN traversed through the SIP =
Proxies
whose address was recorded in the IMDN-Record-Route =
header.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'>My understanding is =
right?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'>Regards,<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'>Seungyong<o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D=B1=BC=B8=B2><span lang=3DEN-US style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Hisham Khartabil [mailto:hisham.khartabil@gmail.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, June 04, =
2010 <st1:time
o:ls=3D"trans" Hour=3D"11" Minute=3D"43" w:st=3D"on">11:43 =
AM</st1:time><br>
<b><span style=3D'font-weight:bold'>To:</span></b> </span></font><font =
size=3D2><span
style=3D'font-size:10.0pt'>=C0=CC=BD=C2=BF=EB</span></font><font =
size=3D2 face=3DTahoma><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:Tahoma'><br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
eburger@standardstrack.com;
christer.holmberg@ericsson.com; Simple WG<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: Question =
about
RFC5438 wrt OMA CPM</span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3 =
face=3D=B1=BC=B8=B2><span
lang=3DEN-US style=3D'font-size:12.0pt'>Hi,<br>
<br>
Section 12.1.3.1 does mention that the request-uri and the To header =
field in
the IMDN (which is a SIP MESSAGE request) are populated from the From =
header
field of the IM (which is a SIP MESSAGE request).<br>
<br>
This is the initial step. You then need to do some processing.<br>
<br>
If there are IMDN-Record-Route headers in the payload of the IM, then =
you need
to add the 1st URI of that IMDN-Record-Route header field into the route =
set of
the IMDN as the last entry (see RFC3261 for route set definition). You =
then
need to follow RFC3261 for population of Request-URI and Route header =
fields
according to the route set.<br>
<br>
The route set could be initially empty and therefore the only the uri =
from the
IMDN-Record-Route is the only one. Or it could be populated with =
whatever the
client has pre-configured (for example, an outbound proxy) and therefore =
the
uri is added to the end f that route set.<br>
<br>
This is normal RFC3261 behaviour.<br>
<br>
Thanks,<br>
Hisham<o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><st1:date o:ls=3D"trans" Year=3D"2010" Month=3D"6" =
Day=3D"4" w:st=3D"on"><font
 size=3D3 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:12.0pt'>2010/6/4</span></font></st1:date><span
lang=3DEN-US> </span>=C0=CC=BD=C2=BF=EB<span lang=3DEN-US> &lt;<a
href=3D"mailto:sy7216.lee@samsung.com">sy7216.lee@samsung.com</a>&gt;<o:p=
></o:p></span></p>

<div link=3Dblue vlink=3Dpurple>

<div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>Dear Eric Burger, Hisham Khartabil and Christer =
Holmberg,</span></font></b><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>&nbsp;</span></font></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>This is Seungyong Lee from Samsung Electronics and in =
charge
of OMA(Open Mobile <st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Alliance</st1:place></st1:City>)
CPM (Converged-IP Messaging).</span></font></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>CPM 1.0 supports IMDN for requesting/receiving =
delivery
notifications and read reports. </span></font></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>In the last CPM meeting (in MAY) there was a heated =
debate
about IMDN routing, especially how to populate the Request-URI of =
IMDN.</span></font></b><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>&nbsp;</span></font></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>A delegate from Ericsson argued on the basis of the =
e-mail
thread (</span></font></b><font face=3DArial><span lang=3DEN-US =
style=3D'font-family:
Arial'>see <a
href=3D"http://www.ietf.org/mail-archive/web/simple/current/msg08759.html=
"
target=3D"_blank">http://www.ietf.org/mail-archive/web/simple/current/msg=
08759.html</a></span></font><b><span
lang=3DEN-US style=3D'font-weight:bold'>) that the Request-URI of IMDN =
should be
set to the top-most address of IMDN-Record-Router header in the received =
IM
where as Samsung retorted that the Request-URI is populated from SIP =
From
header of the received IM, which is based on section 12.1.3.1 in =
RFC5438.</span></b><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>Section 12.1.3.1 says </span></font></b><b><font
face=3D"Times New Roman"><span lang=3DEN-US style=3D'font-family:"Times =
New Roman";
font-weight:bold'>=A1=B0=A1=A6</span></font><span =
lang=3DEN-US>snip</span></b><b><font
face=3D"Times New Roman"><span lang=3DEN-US style=3D'font-family:"Times =
New Roman";
font-weight:bold'>=A1=A6</span></font><span lang=3DEN-US> For IMDNs, the =
IM Recipient
populates the SIP Request-URI and the SIP To header field using the =
address
that appeared in the SIP From header field in the IM.</span></b><b><font
face=3D"Times New Roman"><span lang=3DEN-US style=3D'font-family:"Times =
New Roman";
font-weight:bold'>=A1=B1</span></font></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B9=D9=C5=C1><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold'>&nbsp;</span></font></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>The
routing mechanism of IMDN that I</span></font></b><b><font =
face=3DArial><span
lang=3DEN-US =
style=3D'font-family:Arial;font-weight:bold'>=A1=AF</span></font><span
lang=3DEN-US>m thinking of is very similar with the SIP routing. That =
is,
Request-URI is populated from SIP From header and also <st1:Street =
w:st=3D"on"><st1:address
 w:st=3D"on">SIP Route</st1:address></st1:Street> header is from =
IMDN-Route
header. Because it is SIP headers that is used for routing in SIP/IP =
core, some
CPIM headers for IMDN (e.g. IMDN Route header) needs to be reflected in =
SIP
headers (e.g. SIP Route header).</span></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>&nbsp;</span></font></b><span=

lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>Could
you let me know your intended routing scenario from RFC5438 =
authors</span></font></b><b><font
face=3DArial><span lang=3DEN-US =
style=3D'font-family:Arial;font-weight:bold'>=A1=AF</span></font><span
lang=3DEN-US> perspective?</span></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>Your
quick reply would be so much appreciated and helpful to complete CPM 1.0
without delay.</span></font></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>&nbsp;</span></font></b><span=

lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>Thanks</span></font></b><span=

lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>Sincerely,</span></font></b><=
span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>&nbsp;</span></font></b><span=

lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>Seungyong
Lee</span></font></b><span lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>Samsung
Electronics</span></font></b><span lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-weight:bold'>DMC
Research Lab</span></font></b><span lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DFR =
style=3D'font-size:10.0pt;font-weight:bold'>Biz:
+82-31-279-5450</span></font></b><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3D=B1=BC=B8=B2><span lang=3DFR =
style=3D'font-size:10.0pt;font-weight:bold'>E-mail: <a
href=3D"mailto:sy7216.lee@samsung.com" =
target=3D"_blank">sy7216.lee@samsung.com</a></span></font></b><span
lang=3DEN-US><o:p></o:p></span></p>

</div>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_Vhc5BkA2I9rH2W5mF0jTGA)--

From gonzalo.camarillo@ericsson.com  Mon Jun  7 08:29:40 2010
Return-Path: <gonzalo.camarillo@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 71C863A67B3 for <simple@core3.amsl.com>; Mon,  7 Jun 2010 08:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.7
X-Spam-Level: 
X-Spam-Status: No, score=-102.7 tagged_above=-999 required=5 tests=[AWL=0.700,  J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOZuaH31viNN for <simple@core3.amsl.com>; Mon,  7 Jun 2010 08:29:39 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id B32F028C6BA for <simple@ietf.org>; Mon,  7 Jun 2010 02:50:27 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b13ae0000071b2-78-4c0cc0e47ab1
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id C8.97.29106.4E0CC0C4; Mon,  7 Jun 2010 11:50:28 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 7 Jun 2010 11:50:28 +0200
Received: from [131.160.37.44] ([131.160.37.44]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 7 Jun 2010 11:50:27 +0200
Message-ID: <4C0CC0E3.5030504@ericsson.com>
Date: Mon, 07 Jun 2010 12:50:27 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <4BE96CFF.2020402@ericsson.com> <FF84A09F50A6DC48ACB6714F4666CC7465C54362D9@ESESSCMS0354.eemea.ericsson.se> <4C03E575.5030505@ericsson.com> <FF84A09F50A6DC48ACB6714F4666CC7465C6202A15@ESESSCMS0354.eemea.ericsson.se>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC7465C6202A15@ESESSCMS0354.eemea.ericsson.se>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jun 2010 09:50:27.0737 (UTC) FILETIME=[DBDC6890:01CB0626]
X-Brightmail-Tracker: AAAAAA==
Cc: "'simple@ietf.org'" <simple@ietf.org>
Subject: Re: [Simple] AD review: draft-ietf-simple-msrp-sessmatch-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: Mon, 07 Jun 2010 15:29:40 -0000

Hi,

I have just requested an IETF LC on this document. It will start shortly.

Cheers,

Gonzalo


On 01/06/2010 3:21 PM, Christer Holmberg wrote:
> 
> Hi,
> 
> I have now submitted a new version (-06) of the SESSMATCH draft.
> 
> Regards,
> 
> Christer  
> 
>> -----Original Message-----
>> From: Gonzalo Camarillo 
>> Sent: 31. toukokuuta 2010 19:36
>> To: Christer Holmberg
>> Cc: simple@ietf.org
>> Subject: Re: [Simple] AD review: draft-ietf-simple-msrp-sessmatch-05
>>
>> Hi Christer,
>>
>> thanks for your answers. Please, revise the draft along the 
>> lines of your answers below so that I can start its IETF LC.
>>
>> Thanks,
>>
>> Gonzalo
>>
>> On 20/05/2010 8:50 PM, Christer Holmberg wrote:
>>> Hi,
>>>
>>>> I have received a publication request for the following draft:
>>>>
>>>> https://datatracker.ietf.org/doc/draft-ietf-simple-msrp-sessmatch/
>>>>
>>>> I have a few comments on the draft. Adding a few words 
>> describing how 
>>>> the path mechanism works would be useful. With such an 
>> explanation, 
>>>> it would be easier for readers to understand what this 
>> extension is about.
>>>
>>> My assumption was that the reader is familar with MSRP and 
>> the path attribute, but I can add some explanation words.
>>>
>>> What about adding the following sentence to the 3rd 
>> paragraph of section 1:
>>>
>>> "The SDP a=path attribute is used to establish the routeset 
>> for the MSRP messages associated with the session."
>>>
>>> ------------------
>>>
>>>> The draft states that with this extension, ALGs in the 
>> path need to 
>>>> only be SDP aware as opposed to MSRP aware. That text 
>> implies that an 
>>>> ALG using standard MSRP can already introduce itself in the path 
>>>> (although with a bit more of work).
>>>
>>> The text is probably a little confusing, and mixes up things.
>>>
>>> The main point is that, currently, the *media relay* of an 
>> ALGs needs to modify the MSRP messages, rather than just 
>> passing them as data (as it does for most other media types). 
>>>
>>> The *signalling handler* of an ALG needs to be MSRP aware, 
>> in the sense that it needs to modify the a=path attribute 
>> rather than the c/m line.
>>>
>>> So, maybe the following text is more clear:
>>>
>>> "The SDP a=path attribute is used to establish the routeset 
>> for the MSRP messages associated with the session.
>>> Due to the fact that MSRP UAs check consistency between address 
>>> information in the MSRP messages and in the Session Description 
>>> Protocol (SDP) a=path attribute, when an ALG modifies the address 
>>> information of the a=path attribute, it forces the media 
>> relay of the ALG to act as an MSRP Back-To-Back User Agent 
>> (B2BUA) in order to perform the corresponding modifications 
>> in the MSRP messages, whereas for other media types the media 
>> relay only needs to modify the IP and transport headers."
>>>
>>> Do you think that is more clear?
>>>
>>>
>>> ------------------
>>>
>>>
>>>> So, one could think that the security properties of the protocol 
>>>> would not be affected much. However, the security 
>> considerations are 
>>>> not very clear about this. The Security Considerations 
>> Section should 
>>>> clear on what it is actually describing at any given time. 
>> Clarifying which threats that section talks about would make 
>> the text much easier to understand (e.g., does the 
>> man-in-the-middle introduce itself in the path by modifying 
>> the SDP or just modifies MSRP packets?).
>>>
>>> Would the following be more clear:
>>>
>>> "However, since a man-in-the-middle would in any case be able to 
>>> modify the domain information in both the SDP and the MSRP 
>> messages, 
>>> e.g in order to insert itself in the MSRP signalling path 
>> or to route MSRP messages to non-intended entities, this does 
>> not  introduce any new security risk."
>>>
>>> I also had a look at the remaining text in the security section.
>>>
>>> If needed, to the end of the 3rd paragraph I could end the 
>> following:
>>>
>>> "Based on this information, users can trigger some actions 
>> in order to 
>>> check whether network entities work correctly, or whether  
>> a man-in-the-middle has modified the SDP a=path attribute, 
>> for the same reasons as described earlier."
>>>
>>> The 2 last paragraphs I think are clear, because they 
>> describe how the TLS authentication mechanism can be affected.
>>>
>>>
>>> Regards,
>>>
>>> Christer
>>
>>


From gonzalo.camarillo@ericsson.com  Mon Jun  7 10:12:48 2010
Return-Path: <gonzalo.camarillo@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 5D0113A6C12 for <simple@core3.amsl.com>; Mon,  7 Jun 2010 10:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_50=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rQN88GwalXa9 for <simple@core3.amsl.com>; Mon,  7 Jun 2010 10:12:46 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 7531628C6B9 for <simple@ietf.org>; Mon,  7 Jun 2010 02:50:25 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b13ae0000071b2-63-4c0cc0e0a35b
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id F4.97.29106.0E0CC0C4; Mon,  7 Jun 2010 11:50:24 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 7 Jun 2010 11:50:23 +0200
Received: from [131.160.37.44] ([131.160.37.44]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 7 Jun 2010 11:50:23 +0200
Message-ID: <4C0CC0DF.4080809@ericsson.com>
Date: Mon, 07 Jun 2010 12:50:23 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <4BE96D00.3030908@ericsson.com> <FF84A09F50A6DC48ACB6714F4666CC7465C54362D6@ESESSCMS0354.eemea.ericsson.se> <4C03E57C.9010303@ericsson.com> <FF84A09F50A6DC48ACB6714F4666CC7465C62029CD@ESESSCMS0354.eemea.ericsson.se>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC7465C62029CD@ESESSCMS0354.eemea.ericsson.se>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jun 2010 09:50:23.0472 (UTC) FILETIME=[D9519F00:01CB0626]
X-Brightmail-Tracker: AAAAAA==
Cc: "'simple@ietf.org'" <simple@ietf.org>
Subject: Re: [Simple] AD Review: draft-ietf-simple-msrp-acm-08.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, 07 Jun 2010 17:12:48 -0000

Hi,

I have just requested an IETF LC on this document. It will start shortly.

Cheers,

Gonzalo

On 01/06/2010 2:54 PM, Christer Holmberg wrote:
> 
> Hi,
> 
> I have now submitted a new version (-09) of the ACM draft.
> 
> Regards,
> 
> Christer 
> 
>> -----Original Message-----
>> From: Gonzalo Camarillo 
>> Sent: 31. toukokuuta 2010 19:36
>> To: Christer Holmberg
>> Cc: simple@ietf.org
>> Subject: Re: [Simple] AD Review: draft-ietf-simple-msrp-acm-08.txt
>>
>> Hi Christer,
>>
>> thanks for your answers. Please, revise the draft along the 
>> lines of your answers below so that I can start its IETF LC.
>>
>> Thanks,
>>
>> Gonzalo
>>
>> On 20/05/2010 8:14 PM, Christer Holmberg wrote:
>>> Hi,
>>>  
>>>> I have received a publication request for the following draft:
>>>>
>>>> https://datatracker.ietf.org/doc/draft-ietf-simple-msrp-acm/
>>>>
>>>> I have a few comments on the draft. The draft states that the main 
>>>> motivation for using COMEDIA is NAT traversal. The draft needs to 
>>>> explain why things like ICE TCP are not applicable or are 
>> inferior to 
>>>> the mechanism described in the draft. Section 5 touches upon this.
>>>  
>>>  Assuming you have sessmatch, I guess one could use ICE TCP.
>>>  
>>> (If you do NOT have sessmatch, and use ICE, the a=path address will 
>>> point to the STUN/TURN server, and you will end up with the uri 
>>> address comparision mismatch issue that sessmatch addresses.)
>>>  
>>> Using comedia is much more "light weight" than using ICE, 
>> so I guess that is the main motivation for using comedia.
>>>  
>>> Regarding ICE TCP, there has been some issues (mostly 
>> related to dual synch, afaik), but I don't know what the 
>> current status of those are. And, the latest version of the 
>> ICE TCP draft expired on april 16th.
>>>  
>>> ------------------
>>>  
>>>> Also, since the draft claims that this is an improvement over the 
>>>> standard way of establishing MSRP connections, the draft should 
>>>> briefly describe how it is superior. Is it only that one 
>> can specify 
>>>> which endpoint will start the TCP connection or are there other 
>>>> advantages of using COMEDIA?
>>>  
>>>  For MSRP, that is the main advantage, yes.
>>>  
>>> One could also say that an advantage is that the TCP 
>> connection establishement mechanism is consistant to the ones 
>> used for other types TCP transported media, but the main 
>> advantage is still NAT traversal.
>>>  
>>>  (COMEDIA also defines the connection attribute, but MSRP 
>> does not use 
>>> it.)
>>>  
>>>  ------------------
>>>  
>>>> I found this sentence somewhat confusing:
>>>>
>>>> "User Agents that are likely to be deployed in networks where User 
>>>> Agents need to establish the TCP connections in order to traverse 
>>>> NATs SHOULD support this specification in order to improve 
>> the odds 
>>>> of being able to communicate across NATs."
>>>>
>>>> Does this simply mean that this mechanism is applicable in 
>> scenarios 
>>>> with NATs because it improves the odds of successfully 
>> establishing 
>>>> connections in such an environment?
>>>  
>>> Yes.
>>>  
>>>  But, the main point of the sentence is to make clear that 
>> it is not only useful for the entities behind the NATs to 
>> support the mechanism, but also for other entities in 
>> networks where NATs are deployed - even if those entities are 
>> not behind NATs.
>>>  
>>>  This paragraph has been modified a number of times, but 
>> maybe the following text would be more clear:
>>>  
>>>  "User Agents that are likely to be deployed in networks with NATs 
>>> SHOULD support this specification. It will improve  the 
>> odds of being 
>>> able to make TCP connections successfully traverse NATs, 
>> since User Agents behind NATs can be  requested to initiate 
>> the establishment of the TCP connections."
>>>
>>>  
>>>  ------------------
>>>  
>>>  
>>>> The following normative statement seems redundant since 
>> support for 
>>>> COMEDIA has already been mandated:
>>>>
>>>> "An MSRP UA MUST support the a=setup "active", "actpass" 
>> and "passive"
>>>> attribute values."
>>>>
>>>> If this sentence is meant as a clarification, it should 
>> not use RFC2119 language.
>>>>
>>> The MSRP UA does not need to support all attribute values, 
>> so it needs to be clear which it needs to support.
>>>  
>>>  But, I guess "MUST" could be changed to "must".
>>>  
>>>  At one point we made a WG decission to not talk about the 
>> "holdconn" attribute value, but if it makes the text more 
>> clear I could add something like:
>>>  
>>>  "MSRP UAs compliant to this specification MUST NOT send 
>> the "holdconn" attribute, and MUST ignore it if received."
>>>  
>>>  
>>>  ------------------
>>>  
>>>  
>>>> The same with this sentence:
>>>>
>>>> "In accordance with [RFC4145], if the a=setup attribute value is 
>>>> "active", the port number value SHOULD be 9."
>>>>
>>>> The idea is not to informatively specify things that are 
>> already specified in COMEDIA.
>>>  
>>>  Ok. I can change "SHOULD" to "should".
>>>  
>>>  
>>>  ------------------
>>>  
>>>  
>>>> The authors may want to consider splitting Section 4.2 
>> into several 
>>>> sections. One with general guidelines on how to use 
>> COMEDIA in this 
>>>> environment, another on which values on the COMEDIA 
>> parameters need 
>>>> to be used for backwards compatibility reasons (i.e., to interact 
>>>> with regular MRSP endpoints). The other would describe the 
>> policy to 
>>>> be used when setting those values to maximize the chances 
>> to traverse 
>>>> NATs. I would keep this last section at a SHOULD or 
>> RECOMMENDED level 
>>>> (at
>>>> maximum) because endpoints in some environments might want to do 
>>>> things differently.
>>>  
>>> I guess we could remove the second paragraph ("The a=setup 
>> attribute is particurlarly..."), because the introduction of 
>> the draft already says the same for comedia in general.
>>>  
>>> So, the remaining section could e.g. be divided into two 
>> sub sections, as below:
>>>  
>>> "4.2.  a=setup
>>>  
>>>   4.2.1 General
>>>  
>>>   An MSRP UA uses the SDP a=setup attribute [RFC4145], in order
>>>   to negotiate which endpoint will create the MSRP 
>> transport connection
>>>   towards the other UA.
>>>   
>>>   An MSRP UA MUST always include an explicit a=setup 
>> attribute in its
>>>   SDP offers and answers, since it might be useful for the other
>>>   endpoint, or for entities in the network, to know whether the UA
>>>   supports COMEDIA or not.
>>>
>>>   An MSRP UA must support the a=setup "active", "actpass" 
>> and "passive"
>>>   attribute values.
>>>  
>>>   4.2.2 Attribute usage
>>>  
>>>   When the a=setup attribute value is "actpass" or "passive", the IP
>>>   address and port values in the MSRP URI of the SDP a=path 
>> attribute
>>>   MUST contain the actual address and port values on which 
>> the UA can
>>>   receive a TCP Open request for the MSRP transport connection.
>>>  
>>>   In accordance with [RFC4145], if the a=setup attribute value is
>>>   "active", the port number value should be 9.
>>>  
>>>   If an MSRP UA can provide a global IP address that the 
>> other endpoint
>>>   can use as destination for a TCP Open request, the UA MUST use the
>>>   a=setup "actpass" attribute value in SDP offers.  This is 
>> in order to
>>>   allow the remote UA to send an SDP answer with an a=setup "active"
>>>   attribute value if the UA is located behind NAT, and in 
>> order to be
>>>   compatible with UAs that do not support COMEDIA and thus always
>>>   will act as passive endpoints.  If an MSRP UA cannot provide the
>>>   actual transport address, the UA MUST use the a=setup "active"
>>>   attribute value.
>>>  
>>>   The MSRP UA MUST NOT use the a=setup "passive" attribute 
>> value in an SDP
>>>   offer.
>>>  
>>>   The MSRP UA can determine that it provides a global IP 
>> address in the
>>>   following scenarios:
>>>  
>>>   - the UA can determine that it is not located behind a NAT;
>>>  
>>>   - the UA relays its MSRP transport connections via a relay (e.g.
>>>     MSRP relay or TURN server); or
>>>  
>>>   - the UA has used Session Traversal Utilities for NAT (STUN)
>>>     [RFC5389] signaling to retrieve NAT address and port through the
>>>     local port to be used for the eventual transport 
>> connection, while
>>>     also having determined that the NAT is not address restricted.
>>>  
>>>  Some UAs can determine whether the SIP [RFC3261] signaling has 
>>> traversed a NAT by inspecting the SIP Via header field in the 200
>>> (OK) response to the initial SIP REGISTER request, and 
>> comparing the 
>>> IP addresses in the Via sent-by and the received header field 
>>> parameters.  If the IP addresses are not the same then the UA can 
>>> determine that there is a NAT in the path.  Even though the media 
>>> transport might not traverse the NAT, it is safe to assume that it 
>>> will, and set the a=setup attribute accordingly.  This comparing 
>>> mechanism does not work in all scenarios, though.  For 
>> example, if SIP 
>>> a requests crosses a SIP proxy before crossing a NAT, the 
>> UA will not 
>>> be able to detect the NAT by comparing the IP addresses.
>>>  
>>> If an SDP offer includes an a=setup "actpass" attribute 
>> value, the SDP 
>>> answer MAY include an a=setup "active" attribute value, but SHOULD 
>>> include a=setup "passive" attribute value if the SDP answerer knows 
>>> that it is not located behind a NAT.
>>>  
>>> Once the active UA has established the MSRP transport 
>> connection, the 
>>> UA must immediately send an MSRP SEND request, as defined in 
>>> [RFC4975].
>>>  
>>> NOTE: According to [RFC4975] the initiating UA is always 
>> active, but 
>>> when COMEDIA is used the a=setup attribute is used to 
>> negotiate which 
>>> UA becomes active."
>>>
>>>
>>> Regards,
>>>
>>> Christer
>>
>>


From ben@nostrum.com  Mon Jun  7 10:23:53 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 C62573A6AAA for <simple@core3.amsl.com>; Mon,  7 Jun 2010 10:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.118
X-Spam-Level: **
X-Spam-Status: No, score=2.118 tagged_above=-999 required=5 tests=[AWL=-2.118,  BAYES_50=0.001, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, 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 kLOp+zDgq2ev for <simple@core3.amsl.com>; Mon,  7 Jun 2010 10:23:52 -0700 (PDT)
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 F0A9928C60D for <simple@ietf.org>; Mon,  7 Jun 2010 09:04:25 -0700 (PDT)
Received: from dn3-174.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 o57FSIRW095292 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Jun 2010 10:28:18 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: multipart/alternative; boundary=Apple-Mail-22--882924565
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <0L3G00G7PZHPUP@mmp1.samsung.com>
Date: Mon, 7 Jun 2010 10:28:22 -0500
Message-Id: <A2723BB7-DFFF-4569-8195-50D70C539349@nostrum.com>
References: <0L3G00G7PZHPUP@mmp1.samsung.com>
To: =?utf-8?B?7J207Iq57Jqp?= <sy7216.lee@samsung.com>
X-Mailer: Apple Mail (2.1078)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: 'Simple WG' <simple@ietf.org>
Subject: Re: [Simple] Question about RFC5438 wrt OMA CPM
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, 07 Jun 2010 17:23:53 -0000

--Apple-Mail-22--882924565
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=euc-kr

Hi Seungyong,

Please take a look at the email exchange between myself an Hisham. It =
might change your interpretation.

In particular, SIP proxies are never recorded in IMDN-Record-Route. Only =
IM intermediaries, which can generally be considered endpoints from a =
SIP perspective.=20


On Jun 3, 2010, at 10:10 PM, =C0=CC=BD=C2=BF=EB wrote:

> Hi Hisahm,
> =20
> Thanks for your quick reply.
> =20
> If my understanding is right, you mention that the Request-URI of IMDN =
is populated from the SIP =46rom header of the IM and in addition, route =
set recorded in the IMDN-Record-Route header should be included in the =
SIP Route header in order to guarantee to have IMDN traversed through =
the SIP Proxies whose address was recorded in the IMDN-Record-Route =
header.
> =20
> My understanding is right?
> =20
> Regards,
> Seungyong
> =20
> =20
> From: Hisham Khartabil [mailto:hisham.khartabil@gmail.com]=20
> Sent: Friday, June 04, 2010 11:43 AM
> To: =C0=CC=BD=C2=BF=EB
> Cc: eburger@standardstrack.com; christer.holmberg@ericsson.com; Simple =
WG
> Subject: Re: Question about RFC5438 wrt OMA CPM
> =20
> Hi,
>=20
> Section 12.1.3.1 does mention that the request-uri and the To header =
field in the IMDN (which is a SIP MESSAGE request) are populated from =
the =46rom header field of the IM (which is a SIP MESSAGE request).
>=20
> This is the initial step. You then need to do some processing.
>=20
> If there are IMDN-Record-Route headers in the payload of the IM, then =
you need to add the 1st URI of that IMDN-Record-Route header field into =
the route set of the IMDN as the last entry (see RFC3261 for route set =
definition). You then need to follow RFC3261 for population of =
Request-URI and Route header fields according to the route set.
>=20
> The route set could be initially empty and therefore the only the uri =
from the IMDN-Record-Route is the only one. Or it could be populated =
with whatever the client has pre-configured (for example, an outbound =
proxy) and therefore the uri is added to the end f that route set.
>=20
> This is normal RFC3261 behaviour.
>=20
> Thanks,
> Hisham
>=20
> 2010/6/4 =C0=CC=BD=C2=BF=EB <sy7216.lee@samsung.com>
> Dear Eric Burger, Hisham Khartabil and Christer Holmberg,
> =20
> This is Seungyong Lee from Samsung Electronics and in charge of =
OMA(Open Mobile Alliance) CPM (Converged-IP Messaging).
> CPM 1.0 supports IMDN for requesting/receiving delivery notifications =
and read reports.
> In the last CPM meeting (in MAY) there was a heated debate about IMDN =
routing, especially how to populate the Request-URI of IMDN.
> =20
> A delegate from Ericsson argued on the basis of the e-mail thread (see =
http://www.ietf.org/mail-archive/web/simple/current/msg08759.html) that =
the Request-URI of IMDN should be set to the top-most address of =
IMDN-Record-Router header in the received IM where as Samsung retorted =
that the Request-URI is populated from SIP =46rom header of the received =
IM, which is based on section 12.1.3.1 in RFC5438.
> Section 12.1.3.1 says =A1=B0=A1=A6snip=A1=A6 For IMDNs, the IM =
Recipient populates the SIP Request-URI and the SIP To header field =
using the address that appeared in the SIP =46rom header field in the =
IM.=A1=B1
> =20
> The routing mechanism of IMDN that I=A1=AFm thinking of is very =
similar with the SIP routing. That is, Request-URI is populated from SIP =
=46rom header and also SIP Route header is from IMDN-Route header. =
Because it is SIP headers that is used for routing in SIP/IP core, some =
CPIM headers for IMDN (e.g. IMDN Route header) needs to be reflected in =
SIP headers (e.g. SIP Route header).
> =20
> Could you let me know your intended routing scenario from RFC5438 =
authors=A1=AF perspective?
> Your quick reply would be so much appreciated and helpful to complete =
CPM 1.0 without delay.
> =20
> Thanks
> Sincerely,
> =20
> Seungyong Lee
> Samsung Electronics
> DMC Research Lab
> Biz: +82-31-279-5450
> E-mail: sy7216.lee@samsung.com
> =20
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


--Apple-Mail-22--882924565
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=euc-kr

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Hi Seungyong,</div><div><br></div><div>Please take a look at the =
email exchange between myself an Hisham. It might change your =
interpretation.</div><div><br></div><div>In particular, SIP proxies are =
never recorded in IMDN-Record-Route. Only IM intermediaries, which can =
generally be considered endpoints from a SIP =
perspective.&nbsp;</div><div><br></div><br><div><div>On Jun 3, 2010, at =
10:10 PM, =C0=CC=BD=C2=BF=EB wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><o:smarttagtype =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"Street">
<o:smarttagtype =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place"=
 downloadurl=3D"http://www.5iantlavalamp.com/">
<o:smarttagtype =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags">
<o:smarttagtype =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"address">
<o:smarttagtype =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"date">=

<o:smarttagtype =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"time">=

<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:=B9=D9=C5=C1;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:=B1=BC=B8=B2;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@=B1=BC=B8=B2";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@=B9=D9=C5=C1";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=B1=BC=B8=B2;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:=B1=BC=B8=B2;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:99.25pt 3.0cm 3.0cm 3.0cm;}
div.Section1
	{page:Section1;}
-->
</style>



<div lang=3D"KO" link=3D"blue" vlink=3D"blue">

<div class=3D"Section1"><p class=3D"MsoNormal"><font size=3D"2" =
color=3D"navy" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy">Hi =
Hisahm,<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font =
size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy"><o:p>&nbsp;</o:p></span></font></p><=
p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2=
"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:navy">Thanks for =
your quick reply.<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font=
 size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy"><o:p>&nbsp;</o:p></span></font></p><=
p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2=
"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:navy">If my =
understanding is right, you mention
that the Request-URI of IMDN is populated from the SIP =46rom header of =
the IM
and in addition, route set recorded in the IMDN-Record-Route header =
should be
included in the <st1:street w:st=3D"on"><st1:address w:st=3D"on">SIP =
Route</st1:address></st1:street>
header in order to guarantee to have IMDN traversed through the SIP =
Proxies
whose address was recorded in the IMDN-Record-Route =
header.<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font =
size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy"><o:p>&nbsp;</o:p></span></font></p><=
p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2=
"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:navy">My =
understanding is right?<o:p></o:p></span></font></p><p =
class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2">=
<span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy"><o:p>&nbsp;</o:p></span></font></p><=
p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2=
"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy">Regards,<o:p></o:p></span></font></p=
><p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" =
face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy">Seungyong<o:p></o:p></span></font></=
p><p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" =
face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy"><o:p>&nbsp;</o:p></span></font></p><=
p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"=B1=BC=B8=B2=
"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;color:navy"><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3D"MsoNormal" align=3D"center" =
style=3D"text-align:center"><font size=3D"3" face=3D"=B1=BC=B8=B2"><span =
lang=3D"EN-US" style=3D"font-size:12.0pt">

<hr size=3D"2" width=3D"100%" align=3D"center" tabindex=3D"-1">

</span></font></div><p class=3D"MsoNormal"><b><font size=3D"2" =
face=3D"Tahoma"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span=
></font></b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:Tahoma">
Hisham Khartabil [mailto:hisham.khartabil@gmail.com] <br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Friday, June 04, =
2010 <st1:time o:ls=3D"trans" hour=3D"11" minute=3D"43" w:st=3D"on">11:43 =
AM</st1:time><br>
<b><span style=3D"font-weight:bold">To:</span></b> </span></font><font =
size=3D"2"><span style=3D"font-size:10.0pt">=C0=CC=BD=C2=BF=EB</span></fon=
t><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:Tahoma"><br>
<b><span style=3D"font-weight:bold">Cc:</span></b> <a =
href=3D"mailto:eburger@standardstrack.com">eburger@standardstrack.com</a>;=

<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>; Simple WG<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: Question =
about
RFC5438 wrt OMA CPM</span></font><span =
lang=3D"EN-US"><o:p></o:p></span></p>

</div><p class=3D"MsoNormal"><font size=3D"3" face=3D"=B1=BC=B8=B2"><span =
lang=3D"EN-US" =
style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></span></font></p><p =
class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"3" =
face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:12.0pt">Hi,<br>
<br>
Section 12.1.3.1 does mention that the request-uri and the To header =
field in
the IMDN (which is a SIP MESSAGE request) are populated from the =46rom =
header
field of the IM (which is a SIP MESSAGE request).<br>
<br>
This is the initial step. You then need to do some processing.<br>
<br>
If there are IMDN-Record-Route headers in the payload of the IM, then =
you need
to add the 1st URI of that IMDN-Record-Route header field into the route =
set of
the IMDN as the last entry (see RFC3261 for route set definition). You =
then
need to follow RFC3261 for population of Request-URI and Route header =
fields
according to the route set.<br>
<br>
The route set could be initially empty and therefore the only the uri =
from the
IMDN-Record-Route is the only one. Or it could be populated with =
whatever the
client has pre-configured (for example, an outbound proxy) and therefore =
the
uri is added to the end f that route set.<br>
<br>
This is normal RFC3261 behaviour.<br>
<br>
Thanks,<br>
Hisham<o:p></o:p></span></font></p>

<div><p class=3D"MsoNormal"><st1:date o:ls=3D"trans" year=3D"2010" =
month=3D"6" day=3D"4" w:st=3D"on"><font size=3D"3" face=3D"=B1=BC=B8=B2"><=
span lang=3D"EN-US" =
style=3D"font-size:12.0pt">2010/6/4</span></font></st1:date><span =
lang=3D"EN-US"> </span>=C0=CC=BD=C2=BF=EB<span lang=3D"EN-US"> &lt;<a =
href=3D"mailto:sy7216.lee@samsung.com">sy7216.lee@samsung.com</a>&gt;<o:p>=
</o:p></span></p>

<div link=3D"blue" vlink=3D"purple">

<div><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">Dear Eric Burger, Hisham Khartabil and Christer =
Holmberg,</span></font></b><span lang=3D"EN-US"><o:p></o:p></span></p><p =
class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">&nbsp;</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">This is Seungyong Lee from Samsung Electronics and in =
charge
of OMA(Open Mobile <st1:city w:st=3D"on"><st1:place =
w:st=3D"on">Alliance</st1:place></st1:city>)
CPM (Converged-IP Messaging).</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">CPM 1.0 supports IMDN for requesting/receiving =
delivery
notifications and read reports. </span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">In the last CPM meeting (in MAY) there was a heated =
debate
about IMDN routing, especially how to populate the Request-URI of =
IMDN.</span></font></b><span lang=3D"EN-US"><o:p></o:p></span></p><p =
class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">&nbsp;</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">A delegate from Ericsson argued on the basis of the =
e-mail
thread (</span></font></b><font face=3D"Arial"><span lang=3D"EN-US" =
style=3D"font-family:
Arial">see <a =
href=3D"http://www.ietf.org/mail-archive/web/simple/current/msg08759.html"=
 =
target=3D"_blank">http://www.ietf.org/mail-archive/web/simple/current/msg0=
8759.html</a></span></font><b><span lang=3D"EN-US" =
style=3D"font-weight:bold">) that the Request-URI of IMDN should be
set to the top-most address of IMDN-Record-Router header in the received =
IM
where as Samsung retorted that the Request-URI is populated from SIP =
From
header of the received IM, which is based on section 12.1.3.1 in =
RFC5438.</span></b><span lang=3D"EN-US"><o:p></o:p></span></p><p =
class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">Section 12.1.3.1 says </span></font></b><b><font =
face=3D"Times New Roman"><span lang=3D"EN-US" =
style=3D"font-family:&quot;Times New Roman&quot;;
font-weight:bold">=A1=B0=A1=A6</span></font><span =
lang=3D"EN-US">snip</span></b><b><font face=3D"Times New Roman"><span =
lang=3D"EN-US" style=3D"font-family:&quot;Times New Roman&quot;;
font-weight:bold">=A1=A6</span></font><span lang=3D"EN-US"> For IMDNs, =
the IM Recipient
populates the SIP Request-URI and the SIP To header field using the =
address
that appeared in the SIP =46rom header field in the =
IM.</span></b><b><font face=3D"Times New Roman"><span lang=3D"EN-US" =
style=3D"font-family:&quot;Times New Roman&quot;;
font-weight:bold">=A1=B1</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B9=D9=C5=C1"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:=B9=D9=C5=C1;
font-weight:bold">&nbsp;</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">The
routing mechanism of IMDN that I</span></font></b><b><font =
face=3D"Arial"><span lang=3D"EN-US" =
style=3D"font-family:Arial;font-weight:bold">=A1=AF</span></font><span =
lang=3D"EN-US">m thinking of is very similar with the SIP routing. That =
is,
Request-URI is populated from SIP =46rom header and also <st1:street =
w:st=3D"on"><st1:address w:st=3D"on">SIP =
Route</st1:address></st1:street> header is from IMDN-Route
header. Because it is SIP headers that is used for routing in SIP/IP =
core, some
CPIM headers for IMDN (e.g. IMDN Route header) needs to be reflected in =
SIP
headers (e.g. SIP Route header).</span></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">&nbsp;</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">Could
you let me know your intended routing scenario from RFC5438 =
authors</span></font></b><b><font face=3D"Arial"><span lang=3D"EN-US" =
style=3D"font-family:Arial;font-weight:bold">=A1=AF</span></font><span =
lang=3D"EN-US"> perspective?</span></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">Your
quick reply would be so much appreciated and helpful to complete CPM 1.0
without delay.</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">&nbsp;</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">Thanks</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">Sincerely,</span></font></b><s=
pan lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">&nbsp;</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">Seungyong
Lee</span></font></b><span lang=3D"EN-US"><o:p></o:p></span></p><p =
class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">Samsung
Electronics</span></font></b><span lang=3D"EN-US"><o:p></o:p></span></p><p=
 class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-weight:bold">DMC
Research Lab</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"FR" =
style=3D"font-size:10.0pt;font-weight:bold">Biz:
+82-31-279-5450</span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><font =
size=3D"2" face=3D"=B1=BC=B8=B2"><span lang=3D"FR" =
style=3D"font-size:10.0pt;font-weight:bold">E-mail: <a =
href=3D"mailto:sy7216.lee@samsung.com" =
target=3D"_blank">sy7216.lee@samsung.com</a></span></font></b><span =
lang=3D"EN-US"><o:p></o:p></span></p>

</div>

</div>

</div><p class=3D"MsoNormal"><font size=3D"3" face=3D"=B1=BC=B8=B2"><span =
lang=3D"EN-US" =
style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>


_______________________________________________<br>Simple mailing =
list<br><a =
href=3D"mailto:Simple@ietf.org">Simple@ietf.org</a><br>https://www.ietf.or=
g/mailman/listinfo/simple<br></o:smarttagtype></o:smarttagtype></o:smartta=
gtype></o:smarttagtype></o:smarttagtype></o:smarttagtype></blockquote></di=
v><br></body></html>=

--Apple-Mail-22--882924565--

From fluffy@cisco.com  Mon Jun  7 10:29:25 2010
Return-Path: <fluffy@cisco.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 7A79E3A69D9; Mon,  7 Jun 2010 10:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.203
X-Spam-Level: 
X-Spam-Status: No, score=-109.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CV42xEtaBGU2; Mon,  7 Jun 2010 10:29:24 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id F14D728CB7F; Mon,  7 Jun 2010 09:35:24 -0700 (PDT)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqcGAAu9DEyrR7Hu/2dsb2JhbACSDIs5X3GmQJoUhRcEg0o
X-IronPort-AV: E=Sophos;i="4.53,379,1272844800"; d="scan'208";a="260242152"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-2.cisco.com with ESMTP; 07 Jun 2010 16:34:38 +0000
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o57GYbgT005860; Mon, 7 Jun 2010 16:34:37 GMT
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
Impp: xmpp:cullenfluffyjennings@jabber.org
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <20100607144321.DEA283A814B@core3.amsl.com>
Date: Mon, 7 Jun 2010 10:34:36 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <80745E4A-820D-4BAF-B9C5-C4981509DDAA@cisco.com>
References: <20100607144321.DEA283A814B@core3.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1078)
Cc: simple@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [Simple] Last Call: draft-ietf-simple-msrp-acm (An Alternative Connection Model for the Message Session Relay Protocol (MSRP)) to Proposed Standard
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, 07 Jun 2010 17:29:25 -0000

I can not see why this draft is needed other than making MITM attacks =
easier. I request that this not proceed until we can figure out what is =
going to happen to draft-ietf-simple-msrp-sessmatch then decide if these =
changes to MSRP are needed or if the existing mechanism are sufficient.=20=



On Jun 7, 2010, at 8:39 AM, The IESG wrote:

> The IESG has received a request from the SIP for Instant Messaging and=20=

> Presence Leveraging Extensions WG (simple) to consider the following =
document:
>=20
> - 'An Alternative Connection Model for the Message Session Relay =
Protocol=20
>   (MSRP) '
>   <draft-ietf-simple-msrp-acm-09.txt> as a Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to =
the
> ietf@ietf.org mailing lists by 2010-06-21. Exceptionally,=20
> comments may be sent to iesg@ietf.org instead. In either case, please=20=

> retain the beginning of the Subject line to allow automated sorting.
>=20
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-acm-09.txt
>=20
>=20
> IESG discussion can be tracked via
> =
https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag=3D=
18161&rfc_flag=3D0
>=20
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


Cullen Jennings
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html




From christer.holmberg@ericsson.com  Mon Jun  7 21:44:52 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 2B1873A6947; Mon,  7 Jun 2010 21:44:52 -0700 (PDT)
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 fSaaBAXiezEo; Mon,  7 Jun 2010 21:44:51 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id ED9383A6888; Mon,  7 Jun 2010 21:44:48 -0700 (PDT)
X-AuditID: c1b4fb39-b7b80ae000001aa1-db-4c0dcac0d816
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 26.F4.06817.0CACD0C4; Tue,  8 Jun 2010 06:44:48 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.84]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Tue, 8 Jun 2010 06:44:48 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 8 Jun 2010 06:42:08 +0200
Thread-Topic: [Simple] Last Call: draft-ietf-simple-msrp-acm (An Alternative Connection Model for the Message Session Relay Protocol	(MSRP)) to Proposed Standard
Thread-Index: AcsGaBS6nnK6bBi2Q1moep+oUsGVKQAXN8bG
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC7465C605A8AC@ESESSCMS0354.eemea.ericsson.se>
References: <20100607144321.DEA283A814B@core3.amsl.com>, <80745E4A-820D-4BAF-B9C5-C4981509DDAA@cisco.com>
In-Reply-To: <80745E4A-820D-4BAF-B9C5-C4981509DDAA@cisco.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@ietf.org" <simple@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [Simple] Last Call: draft-ietf-simple-msrp-acm (An Alternative	Connection Model for the Message Session Relay Protocol	(MSRP)) to Proposed Standard
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, 08 Jun 2010 04:44:52 -0000

Hi,

I am not I understand what this draft has to do with MITM attacks. This is =
related to which MSRP UA becomes "active", by applying COMEDIA.

ACM is a separate thing from SESSMATCH - which is the reason the WG decided=
 to split it into two drafts in the first place (originally ACM and SESSMAT=
CH was a single draft).

Regards,

Christer


________________________________________
From: simple-bounces@ietf.org [simple-bounces@ietf.org] On Behalf Of Cullen=
 Jennings [fluffy@cisco.com]
Sent: Monday, June 07, 2010 7:34 PM
To: ietf@ietf.org
Cc: simple@ietf.org; IETF-Announce
Subject: Re: [Simple] Last Call: draft-ietf-simple-msrp-acm (An Alternative=
     Connection Model for the Message Session Relay Protocol (MSRP)) to Pro=
posed Standard

I can not see why this draft is needed other than making MITM attacks easie=
r. I request that this not proceed until we can figure out what is going to=
 happen to draft-ietf-simple-msrp-sessmatch then decide if these changes to=
 MSRP are needed or if the existing mechanism are sufficient.


On Jun 7, 2010, at 8:39 AM, The IESG wrote:

> The IESG has received a request from the SIP for Instant Messaging and
> Presence Leveraging Extensions WG (simple) to consider the following docu=
ment:
>
> - 'An Alternative Connection Model for the Message Session Relay Protocol
>   (MSRP) '
>   <draft-ietf-simple-msrp-acm-09.txt> as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to the
> ietf@ietf.org mailing lists by 2010-06-21. Exceptionally,
> comments may be sent to iesg@ietf.org instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-acm-09.txt
>
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag=
=3D18161&rfc_flag=3D0
>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple


Cullen Jennings
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html



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

From technology789@gmail.com  Tue Jun  8 20:44:33 2010
Return-Path: <technology789@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 2398C3A6847 for <simple@core3.amsl.com>; Tue,  8 Jun 2010 20:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 8F-zSsrVrh6W for <simple@core3.amsl.com>; Tue,  8 Jun 2010 20:44:31 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 7B34E3A6803 for <simple@ietf.org>; Tue,  8 Jun 2010 20:44:31 -0700 (PDT)
Received: by gwj16 with SMTP id 16so127731gwj.31 for <simple@ietf.org>; Tue, 08 Jun 2010 20:44:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=o+3dMXx7jYBIAKhmYzQHaZJUbJ223+YKmfBFK30wGxw=; b=RKlBZFBpl0p9+TNrpmeIuCb9HAQqGsbj3yIQFVAh0FeWd45GngCfI1FdKA/GD3rCeE F2Sh0Vzx0t5gcFdtuPXpABBSMafpTVxrjWo5xTNjaCO/qbQdG7pttU/16ivYMIgb67/x 1KzgL4tImlnho6l01JOoBd3qZL+xh4D5LB2yA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tH3JbvYjCk1DU116fAabKVWV1uljqenI2fPRBH0HatsSCoq8ABf582IaxCmD3ArVGj JXfrS+Avqeygsp5MGq/yzZz1lsfpN37SawJQ7AEarud9a7giy5qHm7PBFDz2jYnlm12H seQVlzFqr4KNGbP7p9EJDcpOXucXHo9XVHH+Y=
MIME-Version: 1.0
Received: by 10.229.250.206 with SMTP id mp14mr6304452qcb.62.1276055067917;  Tue, 08 Jun 2010 20:44:27 -0700 (PDT)
Received: by 10.229.17.203 with HTTP; Tue, 8 Jun 2010 20:44:27 -0700 (PDT)
Date: Wed, 9 Jun 2010 10:44:27 +0700
Message-ID: <AANLkTikJwB0vzHoDecEcTSOiBB8oYSxoli3AeiEgAglC@mail.gmail.com>
From: Ngoc Son <technology789@gmail.com>
To: SIMPLE <simple@ietf.org>
Content-Type: multipart/alternative; boundary=0016363b8b1e09e61c048890b9f4
Subject: [Simple] Identity of resource in SIP event notification
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, 09 Jun 2010 03:47:43 -0000

--0016363b8b1e09e61c048890b9f4
Content-Type: text/plain; charset=ISO-8859-1

Hi everybody,

I have one confusing thing when study about event notification using SIP,
that is identification of resource which is being subscribed. Suppose that
SUBSCRIBEs from Alice (sip:alice@example.com <sip%3Aalice@example.com>) are
sent to Presence Server (sip:ps.example.com) to subscribe presence
information of Bob (sip:bob@example.com <sip%3Abob@example.com>)

+>    RFC 3265, section 3.1.2 state that:
"

Identification of events is provided by three pieces of information:
Request URI, Event Type, and (optionally) message body.

The Request URI of a SUBSCRIBE request, most importantly, contains
   enough information to route the request to the appropriate entity per
   the request routing procedures outlined in SIP [1
<http://tools.ietf.org/html/rfc3265#ref-1>].  It also contains
   enough information to identify the resource for which event
   notification is desired, but not necessarily enough information to
   uniquely identify the nature of the event

"
It means that Request-URI is used as identification of resource. First
SUBSCRIBE from Alice has Request-URI is
sip:bob@example.com<sip%3Abob@example.com>,
which is correct to indicate resource Bob. But from second SUBSCRIBE,
Request-URI will be URI of Presence Server (sip:ps.example.com), because
after receiving response and NOTIFY from PS, Alice's UA will updates Remote
target which is indicated in Contact header of NOTIFY from Presence Server.
So, is it correctly identification of resource? And why don't we use To
header as identification of resource?

+>    In addition, in RFC 4660 about functional description of filtering,
section 5.2.1:
"

The subscriber may have chosen to leave the URI in the filter
   undefined.  If the URI is not defined within the filter, the filter
   applies to the resource identified in the Request-URI.

   Similarly, the subscriber may have chosen to include a URI in the
   filter.  In this case, the filter applies to all notifications sent
   with content associated with the resource with that URI for this
   subscription.  If the Request-URI and the URI in the filter do not
   match, the filter may be ignored or rejected.

"
So, if second SUBSCRIBE from Alice contain filter which has filter-URI is
URI of Bob, request-URI (sip:ps.example.com) and filter-URI (
sip:bob@example.com <sip%3Abob@example.com>) do not match and filter may be
ignored.
If this SUBSCRIBE contain filter which doesn't has filter-URI, this filter
will be used for resource identified in Request-URI (sip:ps.example.com). It
is not correct because this filter is for presence info of Bob.
So, again, why don't we use To header as identification of resource in SIP
event notification mechanism?

Thanks,

-- 
Regards!
DinhNgocSon
Email: technology789@gmail.com
Developer at Xener Systems

--0016363b8b1e09e61c048890b9f4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi everybody,<br><br>I have one confusing thing when study about event noti=
fication using SIP, that is identification of resource which is being subsc=
ribed. Suppose that SUBSCRIBEs from Alice (<a href=3D"mailto:sip%3Aalice@ex=
ample.com">sip:alice@example.com</a>) are  sent to Presence Server (sip:<a =
href=3D"http://ps.example.com">ps.example.com</a>) to subscribe presence in=
formation of Bob (<a href=3D"mailto:sip%3Abob@example.com">sip:bob@example.=
com</a>) <br>
<br>+&gt;=A0 =A0 RFC 3265, section 3.1.2 state that:<br>&quot;<pre class=3D=
"newpage">Identification of events is provided by three pieces of informati=
on:<br>Request URI, Event Type, and (optionally) message body.<br><br>The R=
equest URI of a SUBSCRIBE request, most importantly, contains<br>
   enough information to route the request to the appropriate entity per<br=
>   the request routing procedures outlined in SIP [<a href=3D"http://tools=
.ietf.org/html/rfc3265#ref-1" title=3D"&quot;SIP: Session Initiation Protoc=
ol&quot;">1</a>].  It also contains<br>
   enough information to identify the resource for which event<br>   notifi=
cation is desired, but not necessarily enough information to<br>   uniquely=
 identify the nature of the event<br></pre>&quot;<br clear=3D"all">It means=
 that Request-URI is used as identification of resource. First SUBSCRIBE fr=
om Alice has Request-URI is <a href=3D"mailto:sip%3Abob@example.com">sip:bo=
b@example.com</a>, which is correct to indicate resource Bob. But from seco=
nd SUBSCRIBE, Request-URI will be URI of Presence Server (sip:<a href=3D"ht=
tp://ps.example.com">ps.example.com</a>), because after receiving response =
and NOTIFY from PS, Alice&#39;s UA will updates Remote target which is indi=
cated in Contact header of NOTIFY from Presence Server. So, is it correctly=
 identification of resource? And why don&#39;t we use To header as identifi=
cation of resource?<br>
<br>+&gt;=A0=A0=A0 In addition, in RFC 4660 about functional description of=
 filtering, section 5.2.1:<br>&quot;<pre class=3D"newpage">The subscriber m=
ay have chosen to leave the URI in the filter<br>   undefined.  If the URI =
is not defined within the filter, the filter<br>
   applies to the resource identified in the Request-URI.<br><br>   Similar=
ly, the subscriber may have chosen to include a URI in the<br>   filter.  I=
n this case, the filter applies to all notifications sent<br>   with conten=
t associated with the resource with that URI for this<br>
   subscription.  If the Request-URI and the URI in the filter do not<br>  =
 match, the filter may be ignored or rejected.</pre>&quot;<br>So, if second=
 SUBSCRIBE from Alice contain filter which has filter-URI is URI of Bob, re=
quest-URI (sip:<a href=3D"http://ps.example.com">ps.example.com</a>) and fi=
lter-URI (<a href=3D"mailto:sip%3Abob@example.com">sip:bob@example.com</a>)=
 do not match and filter may be ignored.<br>
If this SUBSCRIBE contain filter which doesn&#39;t has filter-URI, this fil=
ter will be used for resource identified in Request-URI (sip:<a href=3D"htt=
p://ps.example.com">ps.example.com</a>). It is not correct because this fil=
ter is for presence info of Bob. <br>
So, again, why don&#39;t we use To header as identification of resource in =
SIP event notification mechanism?<br><br>Thanks,<br>=A0 <br>-- <br>Regards!=
<br>DinhNgocSon<br>Email: <a href=3D"mailto:technology789@gmail.com">techno=
logy789@gmail.com</a><br>
Developer at Xener Systems<br>

--0016363b8b1e09e61c048890b9f4--

From pkyzivat@cisco.com  Wed Jun  9 06:18:12 2010
Return-Path: <pkyzivat@cisco.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 07C1F3A6976 for <simple@core3.amsl.com>; Wed,  9 Jun 2010 06:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.949
X-Spam-Level: 
X-Spam-Status: No, score=-9.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 rMnkWrIASV1X for <simple@core3.amsl.com>; Wed,  9 Jun 2010 06:18:10 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 9CC723A6974 for <simple@ietf.org>; Wed,  9 Jun 2010 06:18:10 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKMxD0xAZnwM/2dsb2JhbACeRnGjKJoIglcBgkAEkEA
X-IronPort-AV: E=Sophos;i="4.53,391,1272844800"; d="scan'208";a="119716393"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 09 Jun 2010 13:18:11 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o59DIBSE017132; Wed, 9 Jun 2010 13:18:11 GMT
Message-ID: <4C0F9496.6050002@cisco.com>
Date: Wed, 09 Jun 2010 09:18:14 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Ngoc Son <technology789@gmail.com>
References: <AANLkTikJwB0vzHoDecEcTSOiBB8oYSxoli3AeiEgAglC@mail.gmail.com>
In-Reply-To: <AANLkTikJwB0vzHoDecEcTSOiBB8oYSxoli3AeiEgAglC@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SIMPLE <simple@ietf.org>
Subject: Re: [Simple] Identity of resource in SIP event notification
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, 09 Jun 2010 13:18:12 -0000

inline

Ngoc Son wrote:
> Hi everybody,
> 
> I have one confusing thing when study about event notification using 
> SIP, that is identification of resource which is being subscribed. 
> Suppose that SUBSCRIBEs from Alice (sip:alice@example.com 
> <mailto:sip%3Aalice@example.com>) are sent to Presence Server 
> (sip:ps.example.com <http://ps.example.com>) to subscribe presence 
> information of Bob (sip:bob@example.com <mailto:sip%3Abob@example.com>)
> 
> +>    RFC 3265, section 3.1.2 state that:
> "
> 
> Identification of events is provided by three pieces of information:
> Request URI, Event Type, and (optionally) message body.
> 
> The Request URI of a SUBSCRIBE request, most importantly, contains
> 
>    enough information to route the request to the appropriate entity per
>    the request routing procedures outlined in SIP [1 <http://tools.ietf.org/html/rfc3265#ref-1>].  It also contains
> 
>    enough information to identify the resource for which event
>    notification is desired, but not necessarily enough information to
>    uniquely identify the nature of the event
> 
> "
> It means that Request-URI is used as identification of resource. First 
> SUBSCRIBE from Alice has Request-URI is sip:bob@example.com 
> <mailto:sip%3Abob@example.com>, which is correct to indicate resource 
> Bob.

yes.

> But from second SUBSCRIBE, Request-URI will be URI of Presence 
> Server (sip:ps.example.com <http://ps.example.com>), because after 
> receiving response and NOTIFY from PS, Alice's UA will updates Remote 
> target which is indicated in Contact header of NOTIFY from Presence 
> Server.

By "second subscribe" I guess you mean an in-dialog refresh of the 
subscription, right?

This will use whatever contact URI has been provided. It is the 
responsibility of the server to ensure that in-dialog requests are 
associated with the same resource as the original subscription. If 
necessary, it should put an identification of the resource in the 
contact URI. If it hasn't done so, then presumably there is no ambiguity 
or else it has some other way to decide.

> So, is it correctly identification of resource? And why don't we 
> use To header as identification of resource?

Generally the To URI isn't used for anything - its a historical 
artifact. In the case of INVITE, it won't work for identifying the 
target once a call has been forwarded. The same principle holds for 
SUBSCRIBE, though its perhaps less common for a presence subscription to 
be forwarded.

> +>    In addition, in RFC 4660 about functional description of 
> filtering, section 5.2.1:
> "
> 
> The subscriber may have chosen to leave the URI in the filter
>    undefined.  If the URI is not defined within the filter, the filter
> 
>    applies to the resource identified in the Request-URI.
> 
>    Similarly, the subscriber may have chosen to include a URI in the
>    filter.  In this case, the filter applies to all notifications sent
>    with content associated with the resource with that URI for this
> 
>    subscription.  If the Request-URI and the URI in the filter do not
>    match, the filter may be ignored or rejected.
> 
> "
> So, if second SUBSCRIBE from Alice contain filter which has filter-URI 
> is URI of Bob, request-URI (sip:ps.example.com <http://ps.example.com>) 
> and filter-URI (sip:bob@example.com <mailto:sip%3Abob@example.com>) do 
> not match and filter may be ignored.

The initial subscribe identifies the resource/resources to be subscribed 
to. IMO all the filter can do is remove things from consideration. 
Normally the subscribe will identify only a single resource, in which 
case filtering the URI can only be a no-op or else reduce the 
subscription to nothing. However sometimes the target of the initial 
subscribe identifies a number of URIs. In 3gpp this can happen because 
an AOR can have other associated AORs, and subscribing to one is 
considered to imply subscribing to all. Another way is to subscribe to a 
resource-list, which identifies a number of URIs. In those cases 
filtering by URI would have actual utility.

	Thanks,
	Paul

> If this SUBSCRIBE contain filter which doesn't has filter-URI, this 
> filter will be used for resource identified in Request-URI 
> (sip:ps.example.com <http://ps.example.com>). It is not correct because 
> this filter is for presence info of Bob.
> So, again, why don't we use To header as identification of resource in 
> SIP event notification mechanism?
> 
> Thanks,
>  
> -- 
> Regards!
> DinhNgocSon
> Email: technology789@gmail.com <mailto:technology789@gmail.com>
> Developer at Xener Systems
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple

From gonzalo.camarillo@ericsson.com  Thu Jun 10 00:51:22 2010
Return-Path: <gonzalo.camarillo@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 799F03A68F2; Thu, 10 Jun 2010 00:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level: 
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iENp0pz3EQTS; Thu, 10 Jun 2010 00:51:21 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id C0C1B3A682A; Thu, 10 Jun 2010 00:51:20 -0700 (PDT)
X-AuditID: c1b4fb39-b7b80ae000001aa1-42-4c10997942dd
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 26.D4.06817.979901C4; Thu, 10 Jun 2010 09:51:21 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 10 Jun 2010 09:51:21 +0200
Received: from [131.160.126.167] ([131.160.126.167]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 10 Jun 2010 09:51:20 +0200
Message-ID: <4C109978.8080809@ericsson.com>
Date: Thu, 10 Jun 2010 10:51:20 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <20100607144321.DEA283A814B@core3.amsl.com> <80745E4A-820D-4BAF-B9C5-C4981509DDAA@cisco.com>
In-Reply-To: <80745E4A-820D-4BAF-B9C5-C4981509DDAA@cisco.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Jun 2010 07:51:21.0009 (UTC) FILETIME=[B7518210:01CB0871]
X-Brightmail-Tracker: AAAAAA==
Cc: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, "simple@ietf.org" <simple@ietf.org>
Subject: Re: [Simple] Last Call: draft-ietf-simple-msrp-acm (An Alternative Connection Model for the Message Session Relay Protocol	(MSRP)) to Proposed Standard
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, 10 Jun 2010 07:51:22 -0000

Hi Cullen,

note that these two drafts were a single draft in the past but the WG
decided to split it in two. That is why I have started both IETF LCs at
the same time. So, if you have comments on the sessmatch draft, now it
would be a good time to listen to them since that draft is also
undergoing its IETF LC.

Thanks,

Gonzalo

On 07/06/2010 7:34 PM, Cullen Jennings wrote:
> 
> I can not see why this draft is needed other than making MITM attacks easier. I request that this not proceed until we can figure out what is going to happen to draft-ietf-simple-msrp-sessmatch then decide if these changes to MSRP are needed or if the existing mechanism are sufficient. 
> 
> 
> On Jun 7, 2010, at 8:39 AM, The IESG wrote:
> 
>> The IESG has received a request from the SIP for Instant Messaging and 
>> Presence Leveraging Extensions WG (simple) to consider the following document:
>>
>> - 'An Alternative Connection Model for the Message Session Relay Protocol 
>>   (MSRP) '
>>   <draft-ietf-simple-msrp-acm-09.txt> as a Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action.  Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2010-06-21. Exceptionally, 
>> comments may be sent to iesg@ietf.org instead. In either case, please 
>> retain the beginning of the Subject line to allow automated sorting.
>>
>> The file can be obtained via
>> http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-acm-09.txt
>>
>>
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18161&rfc_flag=0
>>
>> _______________________________________________
>> Simple mailing list
>> Simple@ietf.org
>> https://www.ietf.org/mailman/listinfo/simple
> 
> 
> Cullen Jennings
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> 
> 
> 
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www.ietf.org/mailman/listinfo/simple
> 


From ibc@aliax.net  Thu Jun 10 06:49:08 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 EE6B53A68BA for <simple@core3.amsl.com>; Thu, 10 Jun 2010 06:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.923
X-Spam-Level: 
X-Spam-Status: No, score=0.923 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, 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 heVP2fOrBMex for <simple@core3.amsl.com>; Thu, 10 Jun 2010 06:49:08 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 2E2BE3A68B9 for <simple@ietf.org>; Thu, 10 Jun 2010 06:49:08 -0700 (PDT)
Received: by vws9 with SMTP id 9so2840712vws.31 for <simple@ietf.org>; Thu, 10 Jun 2010 06:49:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.17.147 with SMTP id s19mr176987qaa.324.1276177744525; Thu,  10 Jun 2010 06:49:04 -0700 (PDT)
Received: by 10.220.187.3 with HTTP; Thu, 10 Jun 2010 06:49:04 -0700 (PDT)
In-Reply-To: <4C0F9496.6050002@cisco.com>
References: <AANLkTikJwB0vzHoDecEcTSOiBB8oYSxoli3AeiEgAglC@mail.gmail.com> <4C0F9496.6050002@cisco.com>
Date: Thu, 10 Jun 2010 15:49:04 +0200
Message-ID: <AANLkTikt1lZsPtTK9U3-lWQ6qwlSz8OgjJbTU_lSfIOb@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Paul Kyzivat <pkyzivat@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: SIMPLE <simple@ietf.org>
Subject: Re: [Simple] Identity of resource in SIP event notification
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, 10 Jun 2010 13:49:09 -0000

2010/6/9 Paul Kyzivat <pkyzivat@cisco.com>:
> By "second subscribe" I guess you mean an in-dialog refresh of the
> subscription, right?
>
> This will use whatever contact URI has been provided. It is the
> responsibility of the server to ensure that in-dialog requests are
> associated with the same resource as the original subscription. If
> necessary, it should put an identification of the resource in the contact
> URI. If it hasn't done so, then presumably there is no ambiguity or else =
it
> has some other way to decide.

The subscription is a dialog and the presence server can be aware of
such dialog (by keeping a subscription dialogs list taking the
call-id, from/to tags) so IMHO there is no need for a special Contact
URI param or any other kind of identifier.

Regards.


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

From ben@nostrum.com  Wed Jun 23 11:24:14 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 5825D3A67EF for <simple@core3.amsl.com>; Wed, 23 Jun 2010 11:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.875
X-Spam-Level: 
X-Spam-Status: No, score=-1.875 tagged_above=-999 required=5 tests=[AWL=0.725,  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 Likpx5MPyjkD for <simple@core3.amsl.com>; Wed, 23 Jun 2010 11:24:13 -0700 (PDT)
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 231EF3A68C6 for <simple@ietf.org>; Wed, 23 Jun 2010 11:24:11 -0700 (PDT)
Received: from [10.0.1.9] (adsl-68-94-15-65.dsl.rcsntx.swbell.net [68.94.15.65]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o5NIOHCs084580 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <simple@ietf.org>; Wed, 23 Jun 2010 13:24:18 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 23 Jun 2010 13:24:12 -0500
References: <20100621214909.D25A428C13B@core3.amsl.com>
To: Simple WG <simple@ietf.org>
Message-Id: <617B86CD-6A50-401E-BB37-2D3AAD9B556A@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Received-SPF: pass (nostrum.com: 68.94.15.65 is authenticated by a trusted mechanism)
Subject: [Simple] Fwd: Nomcom 2010-2011: Second Call for Volunteers
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, 23 Jun 2010 18:24:14 -0000

Hi Everyone,

Please consider volunteering for the NomCom!

Thanks!

Ben.

Begin forwarded message:

> From: NomCom Chair <nomcom-chair@ietf.org>
> Date: June 21, 2010 4:49:08 PM CDT
> To: IETF Announcement list <ietf-announce@ietf.org>
> Subject: Nomcom 2010-2011: Second Call for Volunteers 
> 
> Hi all, 
> 
> This is the Second call for Volunteers for the 2010-11 nomcom.  We are
> just about halfway through the volunteer period so if you are considering
> volunteering please do so very soon. 
> 
> I am pleased to report that we have 29 volunteers thus far whose
> qualifications have been confirmed by the secretariat. I have notified
> each of these volunteers by email.  
> 
> If you volunteered before 08:00 PDT (15:00 UTC) on June 21 to serve as a
> voting member and have not received a confirmation email from me, please
> re-submit and bring to my attention right away!
> 
> However, we need many more volunteers.  You have until 17:00 PDT (24:00
> UTC) on July 8, 2010 to volunteer for nomcom but it is much better if you
> volunteer as early as possible.  The more volunteers, the better chance we
> have of choosing a random yet representative cross section of the IETF
> pouplation.   
> 
> As a reminder, volunteers must have attended 3 of the past 5 IETF
> meetings - per RFC 3777, which means 3 of the following meetings: IETF-73,
> IETF-74, IETF-75, IETF-76 and IETF-77.  If you qualify, and are willing to
> forgo appointment to any of the positions for which the nominating
> committee is responsible, please volunteer.  
> 
> The 10 nominating committee members are selected randomly from a pool of
> volunteers.  The details of the operation of nomcom may be found in RFC
> 3777.  The process on how to volunteer for nomcom is in the initial
> announcement:  https://datatracker.ietf.org/ann/nomcom/2330/
> 
> The lists of open positions and people whose terms end in March 2011 and
> thus the positions for which the nominating committee is responsible are
> summarized in the initial announcement:
> https://datatracker.ietf.org/ann/nomcom/2330/
> 
> The 29 volunteers who have thus far been qualified by the secretariat
> are: 
> 
> Fred Baker, Cisco Systems
> 
> Stephan Wenger, Vidyo, Inc.
> 
> Marc Blanchet, Viagenie
> 
> Lixia Zhang, UCLA 
> 
> John Drake, Juniper Networks
> 
> Ole Troan, Cisco
> 
> Jiankang Yao, CNNIC
> 
> Wassim Haddad, Ericsson
> 
> Yi Zhao, Huawei USA
> 
> Teemu Savolainen, Nokia
> 
> Jouni Korhonen, Nokia Siemens Networks
> 
> Mehmet Ersue, Nokia Siemens Networks
> 
> Christian Schmidt, Nokia Siemens Networks 
> 
> Stephen Hanna, Juniper Networks
> 
> Suresh Krishnan, Ericsson
> 
> Eric Gray, Ericsson
> 
> David Sinicrope, Ericsson
> 
> Jan Melen, Ericsson
> 
> Richard Barnes, BBN Technologies
> 
> Hugo Salgado Hernandez, NIC Chile
> 
> Ning Zong, Huawei Technologies
> 
> Qin Wu, Huawei Technologies
> 
> Karen Seo, BBN Technologies
> 
> Haibin Song, Huawei Technologies
> 
> Susan Hares, Huawei Technologies
> 
> Tony Hansen. AT&T Labs
> 
> Fuqing Huang, Huawei Technologies Co., Ltd.
> 
> Huub van Helvoort, Huawei Technologies
> 
> Miya Kohno, Juniper Networks
> 
> The primary activity for this nomcom will begin just prior to IETF-78 in
> Maastricht and should be completed in early January 2011.  The nomcom will
> be collecting requirements from the community, as well as talking to
> candidates and to community members about candidates. There will be weekly
> conference calls to ensure progress. Thus, being a nomcom member does
> require some time commitment.  
> 
> While, there is no requirement in RFC 3777 that a participant attend IETF
> meetings while serving on nomcom, please consider that during the IETF
> meetings, people that do not attend would be expected to remotely
> participate during the day in the time zones of the meeting locations -
> Maastricht at the end of July and Beijing in November. 
> 
> If you are not yet sure you would like to volunteer, please consider that
> nomcom members play a very important role in shaping the leadership of the
> IETF.  Ensuring the leadership of the IETF is fair and balanced and
> comprised of those who can lead the IETF in the right direction is an
> important responsibility that rests on the IETF participants at large.
> Volunteering for the nomcom is a good way of contributing in that
> direction.
> 
> Please volunteer by sending an email before:
> 17:00 PDT (24:00 UTC) July 8, 2010 as follows:
> 
> To: nomcom-chair@ietf.org
> Subject: Nomcom 2010-11 Volunteer
> 
> Please include the following information in the body:
> 
> <Your Full Name>  // As you enter in the IETF Registration Form,
>                  // First/Given name followed by Last/Family Name 
> 
> <Current Primary Affiliation>
>                  // typically what goes in the Company field
>                  // in the IETF Registration Form 
> 
> [<all email addresses used to Register for the past 5 IETF meetings>]
> <Preferred email address>  //
> 
> <Telephone number>         // For confirmation if selected
> 
> Please expect an email response from me within 3 days stating whether or
> not you are qualified.  If you don't receive a response, please re-send
> your email with the tag "Duplicate:" added to the subject line.
> 
> Thank you and I hope to hear from you,
> 
> Thomas Walsh
> Chair, Nomcom 2010-11
> Email: nomcom-chair@ietf.org
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From gonzalo.camarillo@ericsson.com  Tue Jun 29 03:18:30 2010
Return-Path: <gonzalo.camarillo@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 33EAA3A67D9; Tue, 29 Jun 2010 03:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.238
X-Spam-Level: 
X-Spam-Status: No, score=-105.238 tagged_above=-999 required=5 tests=[AWL=1.361, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QRfe0JeVUtkC; Tue, 29 Jun 2010 03:18:29 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 7DE743A68F2; Tue, 29 Jun 2010 03:18:28 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b90ae00000278d-3f-4c29c87eeebd
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 50.A3.10125.E78C92C4; Tue, 29 Jun 2010 12:18:38 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 29 Jun 2010 12:18:37 +0200
Received: from [131.160.126.184] ([131.160.126.184]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 29 Jun 2010 12:18:37 +0200
Message-ID: <4C29C87D.1040108@ericsson.com>
Date: Tue, 29 Jun 2010 13:18:37 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: ietf@ietf.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Jun 2010 10:18:37.0624 (UTC) FILETIME=[70333380:01CB1774]
X-Brightmail-Tracker: AAAAAA==
Cc: Cullen Jennings <fluffy@cisco.com>, Ted Hardie <hardie@qualcomm.com>, draft-ietf-simple-msrp-acm@tools.ietf.org, draft-ietf-simple-msrp-sessmatch@tools.ietf.org, IESG <iesg@ietf.org>, simple@ietf.org
Subject: [Simple] Status update on draft-ietf-simple-msrp-acm and draft-ietf-simple-msrp-sessmatch
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, 29 Jun 2010 10:18:30 -0000

Hi,

the authors of the following drafts received a few IETF LC comments:

https://datatracker.ietf.org/doc/draft-ietf-simple-msrp-acm/
https://datatracker.ietf.org/doc/draft-ietf-simple-msrp-sessmatch/

They are going to address those comments as soon as they have the time.

Cheers,

Gonzalo
