From nobody Fri Jun 13 02:33:16 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18351A03EC for ; Fri, 13 Jun 2014 02:33:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Jo_-10GcD9g for ; Fri, 13 Jun 2014 02:33:13 -0700 (PDT) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B14B31A038C for ; Fri, 13 Jun 2014 02:33:12 -0700 (PDT) X-AuditID: c1b4fb2d-f79776d000001085-0b-539ac5563469 Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 02.3A.04229.655CA935; Fri, 13 Jun 2014 11:33:10 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.28]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0174.001; Fri, 13 Jun 2014 11:33:10 +0200 From: Christer Holmberg To: "dispatch@ietf.org" Thread-Topic: Draft new version: draft-holmberg-dispatch-iotl-01 Thread-Index: Ac+G6g7Z5F/uw7djTE+rrkYnMNLI9w== Date: Fri, 13 Jun 2014 09:33:09 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B1D360A23@ESESSMB209.ericsson.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.19] Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D360A23ESESSMB209erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+JvjW7Y0VnBBn3TdC2WTlrA6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujBkvr7AXzJSs6Orby9TAOFmsi5GTQ0LAROL/z3XsELaYxIV7 69lAbCGBo4wSy3riuhi5gOzFjBInl04AKuLgYBOwkOj+pw1SIyKgLXF0VRcziC0sYC0x/eR3 Zoi4g8ShEw/ZIGw9iZalrYwgNouAqsSRaxvBdvEK+EosmbIAzGYE2vv91BomEJtZQFzi1pP5 TBD3CEgs2XOeGcIWlXj5+B8rhK0o0f60gRGiPl9i3dHfzBAzBSVOznzCMoFRaBaSUbOQlM1C UgYR15FYsPsTG4StLbFs4WtmGPvMgcdMyOILGNlXMYoWpxYX56YbGeulFmUmFxfn5+nlpZZs YgRGxMEtv3V3MK5+7XiIUYCDUYmH94HSrGAh1sSy4srcQ4zSHCxK4ryXNKqDhQTSE0tSs1NT C1KL4otKc1KLDzEycXBKNTBGfDr8y932v3lpaOk54ZP7bAyPx1r8FrSYuLvqIO9sy5eMa1pO 5hge1uVfzXA1Z+Lcb61KWmvaP0nFzX4yaW7ufG9Tz5n5H1YmTpxyyzGQOXOZ5O7+nfcLNmns EnkdN/3ahsnLclIrK/zMqqXD9FbIua1O+PQnZE7cp3vi2bO3CiW+3VK9uKhbiaU4I9FQi7mo OBEASQyLcWkCAAA= Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/M4tBeMjfY-u-lXwnCdWrk3s_LgU Subject: [dispatch] Draft new version: draft-holmberg-dispatch-iotl-01 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2014 09:33:15 -0000 --_000_7594FB04B1934943A5C02806D1A2204B1D360A23ESESSMB209erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Based on the comments from Paul and Dale, we have submitted a new version o= f the draft-holmberg-dispatch-iotl draft. It still aims at specifying a generic mechanism. But, as discussed earlier,= we may change it into a 3GPP specific one. We added some text on things that needed to be clarified (see change log), = and we also added some example flows. Regards, Christer --_000_7594FB04B1934943A5C02806D1A2204B1D360A23ESESSMB209erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

Based on the comments from Paul and Dale, we have su= bmitted a new version of the draft-holmberg-dispatch-iotl draft.=

 

It still aims at specifying a generic mechanism. But= , as discussed earlier, we may change it into a 3GPP specific one.

 

We added some text on things that needed to be clari= fied (see change log), and we also added some example flows.

 

Regards,

 

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D360A23ESESSMB209erics_-- From nobody Fri Jun 13 09:20:33 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9891B299E for ; Fri, 13 Jun 2014 09:20:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.235 X-Spam-Level: X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rq3MKfp7ywdf for ; Fri, 13 Jun 2014 09:20:32 -0700 (PDT) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id B659F1A00D2 for ; Fri, 13 Jun 2014 09:20:31 -0700 (PDT) Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta07.westchester.pa.mail.comcast.net with comcast id DqF41o0060cZkys57sLXke; Fri, 13 Jun 2014 16:20:31 +0000 Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta10.westchester.pa.mail.comcast.net with comcast id DsLX1o00A3ZTu2S3WsLX6x; Fri, 13 Jun 2014 16:20:31 +0000 Message-ID: <539B24CF.3060902@alum.mit.edu> Date: Fri, 13 Jun 2014 12:20:31 -0400 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: dispatch@ietf.org References: <7594FB04B1934943A5C02806D1A2204B1D360A23@ESESSMB209.ericsson.se> In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D360A23@ESESSMB209.ericsson.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1402676431; bh=tsjYbfpXl58/ug66OWj6j4QMdp2I0saxZ9os49/wxvg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=szHLTS0TSIzar6pYNawXzVIX6VKYPulz81G6GeudSc1Ntxlq2L6moDd6o3eflzE0c CcEJTnMwfBUgtFXH/PZ0u/C7KoaFi/UXi4vy0miY+j5h0p3CHUBuImzf1doEgVx4pD sY9Rvm3b/l4D5TJuc64rvmkl88unFLfNiKTArG1T7kRxP6Er5K45kS7qIzMHaTcWhZ 8QExLO0E2YsHFX7wMG8lTkcTPLP6BlqL7ubgweroCNZarvW4zIaC0T7ticDEzh04MX rqhGC0mavIl0mt9I4LW0W/7eLf+N+zHQwNkRhIPOk/1Jt+y6r3z/FsYTdl21Q7MlLb 4oSnWU83HqDhQ== Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/2gmcvoLW6PfL9OtPb8vbxaa9VU4 Subject: Re: [dispatch] Draft new version: draft-holmberg-dispatch-iotl-01 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2014 16:20:32 -0000 On 6/13/14 5:33 AM, Christer Holmberg wrote: > Hi, > > Based on the comments from Paul and Dale, we have submitted a new > version of the draft-holmberg-dispatch-iotl draft. > > It still aims at specifying a generic mechanism. But, as discussed > earlier, we may change it into a 3GPP specific one. > > We added some text on things that needed to be clarified (see change > log), and we also added some example flows. Intro: A traffic leg might be associated with multiple SIP dialogs, e.g. in case a B2BUA which modifies the SIP dialog identifier is located within the traffic leg. This raises questions in my mind about the architectural model you have in mind. I think of a "leg" as a segment of the path that an individual session traverses. Multiple sessions may follow similar paths, and thus may have legs that traverse the same set of nodes, but are those the same "leg"? It may not make any material difference, but I find it confusing. Thanks, Paul From nobody Sat Jun 14 02:13:01 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CB31B28AE for ; Sat, 14 Jun 2014 02:12:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4m7yM6_PtcYc for ; Sat, 14 Jun 2014 02:12:58 -0700 (PDT) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F8081B2BEB for ; Sat, 14 Jun 2014 02:12:57 -0700 (PDT) X-AuditID: c1b4fb25-f79226d000004024-c9-539c1217611b Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C7.04.16420.7121C935; Sat, 14 Jun 2014 11:12:55 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.4]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0174.001; Sat, 14 Jun 2014 11:12:55 +0200 From: Christer Holmberg To: Paul Kyzivat , "dispatch@ietf.org" Thread-Topic: [dispatch] Draft new version: draft-holmberg-dispatch-iotl-01 Thread-Index: Ac+G6g7Z5F/uw7djTE+rrkYnMNLI9wAKJLqAACd4VeI= Date: Sat, 14 Jun 2014 09:12:54 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B1D375329@ESESSMB209.ericsson.se> References: <7594FB04B1934943A5C02806D1A2204B1D360A23@ESESSMB209.ericsson.se>, <539B24CF.3060902@alum.mit.edu> In-Reply-To: <539B24CF.3060902@alum.mit.edu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.16] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUyM+Jvja640Jxggw0HVC2WTlrAarFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj+4wDzAWzOCr6Fy1hbGDczNbFyMkhIWAi cejPWmYIW0ziwr31QHEuDiGBo4wS3Z0n2SGcRYwSv870MHUxcnCwCVhIdP/TBmkQEQiWOHh4 JwtIWFjAS2L34iAQU0TAW6KlORmiwkqi+dxaVpAwi4CqRNsxY5Awr4CvxOtj91lAbCGBXIkP RyCu4RTQkdj78AGYzQh0zfdTa5hAbGYBcYlbT+YzQVwpILFkz3moi0UlXj7+xwphK0rsPNvO DFGvI7Fg9yc2CFtbYtnC18wQewUlTs58wjKBUXQWkrGzkLTMQtIyC0nLAkaWVYyixanFSbnp RsZ6qUWZycXF+Xl6eaklmxiBEXJwy2/VHYyX3zgeYhTgYFTi4VWwmR0sxJpYVlyZe4hRmoNF SZz3/pdZwUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYBdI5gwUeOV4W4ao7efgkl8VjkRTr YItckXOXEubdWqq+vv90rOi6UEn1vc/37LueqxT4ftffpv3ZdtnuxxgDF8rOdpgy6c7V25zB /1gPX5iXs1x9z+d7LJfdT14L1CnINGHzU6r7+Dt7sbFd9ZMnE/7t6r959N+0PLuHXcxC9m7G Acf6911Yo8RSnJFoqMVcVJwIAM9s0UZxAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/ZIOm5bgcPgRW3T7XtaM0VY8Yyec Subject: Re: [dispatch] Draft new version: draft-holmberg-dispatch-iotl-01 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2014 09:12:59 -0000 Hi, >> Based on the comments from Paul and Dale, we have submitted a new >> version of the draft-holmberg-dispatch-iotl draft. >> >> It still aims at specifying a generic mechanism. But, as discussed >> earlier, we may change it into a 3GPP specific one. >> >> We added some text on things that needed to be clarified (see change >> log), and we also added some example flows. > > Intro: > > A traffic leg might be > associated with multiple SIP dialogs, e.g. in case a B2BUA which > modifies the SIP dialog identifier is located within the traffic leg. > > This raises questions in my mind about the architectural model you have > in mind. I think of a "leg" as a segment of the path that an individual > session traverses. Multiple sessions may follow similar paths, and thus > may have legs that traverse the same set of nodes, but are those the > same "leg"? They may be, but they don't have to be. A traffic leg is not a "static thin= g", which automatically applies to all sessions. Regards, Christer= From nobody Mon Jun 16 07:25:00 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 618EC1A0043 for ; Mon, 16 Jun 2014 07:24:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s6Vt4wWHpA83 for ; Mon, 16 Jun 2014 07:24:58 -0700 (PDT) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id D50221A0032 for ; Mon, 16 Jun 2014 07:24:57 -0700 (PDT) Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta02.westchester.pa.mail.comcast.net with comcast id F00k1o0070mv7h0512Qxjg; Mon, 16 Jun 2014 14:24:57 +0000 Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta11.westchester.pa.mail.comcast.net with comcast id F2Qw1o0151KKtkw3X2QxqM; Mon, 16 Jun 2014 14:24:57 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s5GEOupS006128; Mon, 16 Jun 2014 10:24:56 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s5GEOujf006127; Mon, 16 Jun 2014 10:24:56 -0400 Date: Mon, 16 Jun 2014 10:24:56 -0400 Message-Id: <201406161424.s5GEOujf006127@hobgoblin.ariadne.com> From: worley@ariadne.com (Dale R. Worley) Sender: worley@ariadne.com (Dale R. Worley) To: Paul Kyzivat In-reply-to: <539B24CF.3060902@alum.mit.edu> (pkyzivat@alum.mit.edu) References: <7594FB04B1934943A5C02806D1A2204B1D360A23@ESESSMB209.ericsson.se> <539B24CF.3060902@alum.mit.edu> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1402928697; bh=8FsQLcMFROXezAEtt+iE4hY5u6wmHbXazWkK3+/n+no=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=I8W5KzyeGPMGaT7ieWfPpaoiI18iLGReVhehB00vf4WIFOxRTuP9RGoLjqk5wBUw0 QFuAvVQjs7gtZEnutCHJ4x39n1+3+26XY3DdTbqBdL05LRsUVHe9u0l1j15ZapZsdz fvijVPgB27h+Q4jAeesMCpGaMe8KWS+ZfMqp5zD1WZl5HJRlQm4KCSMp5KxqRrlBET W4IgN0QxbrU8wK2Fh96ibXmExmYOgVjXxlJ3T/djHPQ3oPOANVzNrUYOs4LrIuuXFo e3UMqz1i5+y6dmNDajykFhXsz9ybypDTsbQHCQox/U+mAI0CDG52kzoBSdmZlNSJ8C uC/GBeJ9IQ4xA== Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/klzqcvUP2LE_xHCrQhRch3FZz4Y Cc: dispatch@ietf.org Subject: Re: [dispatch] Draft new version: draft-holmberg-dispatch-iotl-01 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 14:24:59 -0000 > From: Paul Kyzivat > A traffic leg might be > associated with multiple SIP dialogs, e.g. in case a B2BUA which > modifies the SIP dialog identifier is located within the traffic leg. > > This raises questions in my mind about the architectural model you have > in mind. I think of a "leg" as a segment of the path that an individual > session traverses. Multiple sessions may follow similar paths, and thus > may have legs that traverse the same set of nodes, but are those the > same "leg"? The problem is that we lack terminology. A B2BUA can do anything, but almost all the time, what it does in interconnect pairs of dialogs, coupling their lifetines and arranging for the media arriving on one to depart on the other and vice-versa (though sometimes with some sort of transformation). So there is often a sequence of dialogs that are connected end-to-end by B2BUAs. We don't have a word for that sequence of dialogs. What this draft wants to say is that the sequence of dialogs can be cut into segments, which are called "legs", and certain specific processing (signaling or media) is expected to be done at the junction points between the legs, based on the categories that the legs belong to. Dale From nobody Mon Jun 16 11:48:14 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4F61A014C for ; Mon, 16 Jun 2014 11:48:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QcS06YlpI69l for ; Mon, 16 Jun 2014 11:48:12 -0700 (PDT) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82D861A013B for ; Mon, 16 Jun 2014 11:48:11 -0700 (PDT) X-AuditID: c1b4fb25-f79226d000004024-2f-539f3be94baa Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id F0.7D.16420.9EB3F935; Mon, 16 Jun 2014 20:48:09 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.4]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0174.001; Mon, 16 Jun 2014 20:48:08 +0200 From: Christer Holmberg To: "Dale R. Worley" , Paul Kyzivat Thread-Topic: [dispatch] Draft new version: draft-holmberg-dispatch-iotl-01 Thread-Index: Ac+G6g7Z5F/uw7djTE+rrkYnMNLI9wAKJLqAAJcIdx0ACQMl2A== Date: Mon, 16 Jun 2014 18:48:08 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B1D388B49@ESESSMB209.ericsson.se> References: <7594FB04B1934943A5C02806D1A2204B1D360A23@ESESSMB209.ericsson.se> <539B24CF.3060902@alum.mit.edu>, <201406161424.s5GEOujf006127@hobgoblin.ariadne.com> In-Reply-To: <201406161424.s5GEOujf006127@hobgoblin.ariadne.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.19] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrCLMWRmVeSWpSXmKPExsUyM+Jvje5L6/nBBsseiVgsnbSA1WLFhgOs Fi9PlDkwe/x9/4HJY/L+r8weS5b8ZApgjuKySUnNySxLLdK3S+DK6Hv9jbXgF0/Fop5HrA2M s7m6GDk5JARMJP79284OYYtJXLi3nq2LkYtDSOAoo0Tj96+MEM4iRon+pXeAqjg42AQsJLr/ aYM0iAgESmzrOs0KYjMLaEv8v76OEaREWMBLYvfiIBBTRMBboqU5GcJ0kuidLAJSzCKgKvHz 0zkWEJtXwFdi1bU/TBCLFjNKtB3fB3YOp4CDxJFd65hBbEag076fWsMEsUlc4taT+UwQJwtI LNlznhnCFpV4+fgfK4StKNH+tIERol5HYsHuT2wwVy5b+JoZYrGgxMmZT1gmMIrNQjJ2FpKW WUhaZiFpWcDIsopRtDi1OCk33chYL7UoM7m4OD9PLy+1ZBMjMJoObvmtuoPx8hvHQ4wCHIxK PLwLDOYHC7EmlhVX5h5ilOZgURLnXXhuXrCQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGxlCW mkiPcyeP99Zr6C0RiK1Usfv+9bjuZ6GG+f/s5cS+Wkc9+1H299y1TPkFzhV8HbWbOIpWZ/a8 i2ydP/nyR+YdB/32ci921ot8s+TxpMDWefb/Pvh/VajlMj6xeJv8tX/hitPFjnk/kxTtf2Z4 verzifgnGwv1tu092L5igQODmfCxM9d3eSmxFGckGmoxFxUnAgAkLLZjhwIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/rvrU6TmkKm9jpLWMavxoA2CC9bs Cc: "dispatch@ietf.org" Subject: Re: [dispatch] Draft new version: draft-holmberg-dispatch-iotl-01 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 18:48:13 -0000 Hi, >> A traffic leg might be >> associated with multiple SIP dialogs, e.g. in case a B2BUA which >> modifies the SIP dialog identifier is located within the traffic leg= . >> >> This raises questions in my mind about the architectural model you have >> in mind. I think of a "leg" as a segment of the path that an individual >> session traverses. Multiple sessions may follow similar paths, and thus >> may have legs that traverse the same set of nodes, but are those the >> same "leg"? > > The problem is that we lack terminology. A B2BUA can do anything, but > almost all the time, what it does in interconnect pairs of dialogs, > coupling their lifetines and arranging for the media arriving on one > to depart on the other and vice-versa (though sometimes with some sort > of transformation). So there is often a sequence of dialogs that are > connected end-to-end by B2BUAs. > > We don't have a word for that sequence of dialogs. Well, the "session", as identified by the INSIPID session-id, can identity = a sequence of dialog.=20 > What this draft wants to say is that the sequence of dialogs can be > cut into segments, which are called "legs", and certain specific > processing (signaling or media) is expected to be done at the junction > points between the legs, based on the categories that the legs belong > to. Correct. But, it is important to remember that a traffic leg can orginate/terminate = in the middle of a dialog or INSIPID session, which means that different pa= rts of the same dialog/INSIPID session can be associated with different tra= ffic legs. Regards, Christer= From ratarius@qti.qualcomm.com Mon Jun 16 12:31:57 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8BF41A01B1 for ; Mon, 16 Jun 2014 12:31:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.951 X-Spam-Level: X-Spam-Status: No, score=-4.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqW95Zy8Pp6t for ; Mon, 16 Jun 2014 12:31:56 -0700 (PDT) Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86AEF1A016D for ; Mon, 16 Jun 2014 12:31:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1402947116; x=1434483116; h=from:to:subject:date:message-id:mime-version; bh=Te9luj+aa6DiFGWeU5d1Ss4lFF9t/iZbWlR9QKaWEgQ=; b=eCtzoW9ppPDCAma+RvyfcMk2Ogufid5HuUfqb8Wg6BoJt9dkWabr8HPa /HWuwahGh6Laf4ntMkKjxLp/waHsY3XdnaGgGuKC+cLXEdR3lOfPL1/3G sQoYvIOXKWA+BzTHPIEVFG4sOnS7JYyOA/zqlDsizarcdGt/KxPxTbM+P 8=; X-IronPort-AV: E=McAfee;i="5600,1067,7471"; a="134779560" Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine02.qualcomm.com with ESMTP; 16 Jun 2014 12:31:56 -0700 X-IronPort-AV: E=Sophos; i="5.01,487,1400050800"; d="scan'208,217"; a="29908580" Received: from nasanexhc12.na.qualcomm.com ([172.30.39.187]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 16 Jun 2014 12:31:55 -0700 Received: from NASANEXD02C.na.qualcomm.com ([169.254.6.233]) by nasanexhc12.na.qualcomm.com ([172.30.39.187]) with mapi id 14.03.0181.006; Mon, 16 Jun 2014 12:31:55 -0700 From: "Atarius, Roozbeh" To: "dispatch@ietf.org" Thread-Topic: MEID URN Thread-Index: Ac+Jlu8FjStcWJ84QX6af3JG7fXmEg== Date: Mon, 16 Jun 2014 19:31:55 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.39.5] Content-Type: multipart/alternative; boundary="_000_C3C66925F8E93F45881272F7297F66EC2D0F98B0NASANEXD02Cnaqu_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/k_GMRh9SKyd8akCYwwAHkcIII9c X-Mailman-Approved-At: Mon, 16 Jun 2014 16:12:11 -0700 Subject: [dispatch] MEID URN X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 19:33:35 -0000 --_000_C3C66925F8E93F45881272F7297F66EC2D0F98B0NASANEXD02Cnaqu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello all, I have uploaded two drafts 1- draft-atarius-dispatch-meid-urn-05 https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn/ 2- draft-atarius-dispatch-meid-urn-as-instanceid-00 https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn-as-instanc= eid/ Please provide comments if any. Thanks Roozbeh Atarius --_000_C3C66925F8E93F45881272F7297F66EC2D0F98B0NASANEXD02Cnaqu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello all,

 

I have uploaded two drafts

 

1-      draft-atarius-dispatch-meid-urn-05

https://datatracker.ietf.org/doc/draft-ata= rius-dispatch-meid-urn/        =  

2-      draft-atarius-dispatch-meid-urn-as-instanceid-00

https://datatracker.ietf.org= /doc/draft-atarius-dispatch-meid-urn-as-instanceid/   &n= bsp;         

 

Please provide comments if any.

 

Thanks

Roozbeh Atarius

 

--_000_C3C66925F8E93F45881272F7297F66EC2D0F98B0NASANEXD02Cnaqu_-- From nobody Tue Jun 17 07:49:14 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70E4C1A0024 for ; Tue, 17 Jun 2014 07:49:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RvQpwbN7fKwg for ; Tue, 17 Jun 2014 07:49:09 -0700 (PDT) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id 13A301A0008 for ; Tue, 17 Jun 2014 07:49:08 -0700 (PDT) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta09.westchester.pa.mail.comcast.net with comcast id FSLH1o0020vyq2s59Sp8T8; Tue, 17 Jun 2014 14:49:08 +0000 Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta05.westchester.pa.mail.comcast.net with comcast id FSp81o0071KKtkw3RSp8gM; Tue, 17 Jun 2014 14:49:08 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s5HEn7cZ014245; Tue, 17 Jun 2014 10:49:07 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s5HEn7w6014244; Tue, 17 Jun 2014 10:49:07 -0400 Date: Tue, 17 Jun 2014 10:49:07 -0400 Message-Id: <201406171449.s5HEn7w6014244@hobgoblin.ariadne.com> From: worley@ariadne.com (Dale R. Worley) Sender: worley@ariadne.com (Dale R. Worley) To: "Atarius\, Roozbeh" In-reply-to: (ratarius@qti.qualcomm.com) References: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1403016548; bh=nP1PR3FO0AIeyv5XfeGlnelYi6+uf4Cv3c07kMJylk8=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=gm/evAW0Hey4n3EoAw0DsWoy7TIFel6833u8rOe2FY18C3mu49GWC+8tyXRgTE2D3 9PLGGmtJqyhIJI1UGwFHXFBXVTLhywixRBCCfYd2NjQufcCLyB3AKdzKGYqGkR9Nfz z0F9ydFNI+yY7Tbz8QEOcz1a4ki+NeqDnfU1ehur2foul2uGOAXY7YKG5bEni8+6VD k80eylq5rVXz6YwD7kipfpijglCcr2krvEmJAGGf4lqHaYmL2WHrPqqMKtKAIyMlfs CMpvgi1xqYRQFgEtC7c5Z7f5Z75eQlFkMM0jbOK3LeZh0Y6FYkIPyNIFtNdOPZV1La AJ9qnPjv1aHgA== Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/6GZJHOECtsH2dsznmJ4fXNaXlFc Cc: dispatch@ietf.org Subject: Re: [dispatch] MEID URN X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 14:49:13 -0000 > From: "Atarius, Roozbeh" > 1- draft-atarius-dispatch-meid-urn-05 What is the relationship between this and RFC 7254? How does MEI differ from IMEI? Given that RFC 7254 exists, do we need to provide URNs for MEIs? Dale From nobody Tue Jun 17 08:27:21 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8E31A004B for ; Tue, 17 Jun 2014 08:27:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxXTIHE5FUg7 for ; Tue, 17 Jun 2014 08:27:14 -0700 (PDT) Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id 9BD8C1A0024 for ; Tue, 17 Jun 2014 08:27:14 -0700 (PDT) Received: from xct105cnc.rim.net ([10.65.161.205]) by mhs213cnc.rim.net with ESMTP/TLS/AES128-SHA; 17 Jun 2014 11:27:09 -0400 Received: from XCT115CNC.rim.net (10.65.161.215) by XCT105CNC.rim.net (10.65.161.205) with Microsoft SMTP Server (TLS) id 14.3.174.1; Tue, 17 Jun 2014 11:27:09 -0400 Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT115CNC.rim.net ([::1]) with mapi id 14.03.0174.001; Tue, 17 Jun 2014 11:27:08 -0400 From: Andrew Allen To: "worley@ariadne.com" , "ratarius@qti.qualcomm.com" Thread-Topic: [dispatch] MEID URN Thread-Index: Ac+Jlu8FjStcWJ84QX6af3JG7fXmEgApGHutAAFSP+s= Date: Tue, 17 Jun 2014 15:27:08 +0000 Message-ID: In-Reply-To: <201406171449.s5HEn7w6014244@hobgoblin.ariadne.com> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.65.160.252] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/OZRwV-ODUzJbghWV36yrEvKi0qs Cc: "dispatch@ietf.org" Subject: Re: [dispatch] MEID URN X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 15:27:19 -0000 3GPP2 CDMA devices that do not support 3GPP networks do not have an IMEI an= d only have an MEID. So we need to support MEID as well for those devices a= nd this is defined in 3GPP TS 24.229.=20 The MEID encoding is different - it is hex digits as opposed to decimal dig= its as used in the IMEI. Also there is no software version for the MEID. Al= so ownership of the MEID is different - The GSMA do not control the MEID al= location. Andrew ----- Original Message ----- From: Dale R. Worley [mailto:worley@ariadne.com] Sent: Tuesday, June 17, 2014 10:49 AM Eastern Standard Time=0A= To: Atarius, Roozbeh Cc: dispatch@ietf.org Subject: Re: [dispatch] MEID URN > From: "Atarius, Roozbeh" > 1- draft-atarius-dispatch-meid-urn-05 What is the relationship between this and RFC 7254? How does MEI differ from IMEI? Given that RFC 7254 exists, do we need to provide URNs for MEIs? Dale _______________________________________________ dispatch mailing list dispatch@ietf.org https://www.ietf.org/mailman/listinfo/dispatch From nobody Tue Jun 17 12:28:26 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70DC81A014E for ; Tue, 17 Jun 2014 12:28:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbGplxHEsCMr for ; Tue, 17 Jun 2014 12:28:23 -0700 (PDT) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id E95521A00C0 for ; Tue, 17 Jun 2014 12:28:22 -0700 (PDT) Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta02.westchester.pa.mail.comcast.net with comcast id FPlm1o0081YDfWL51XUN4H; Tue, 17 Jun 2014 19:28:22 +0000 Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta20.westchester.pa.mail.comcast.net with comcast id FXUM1o00A1KKtkw3gXUMN7; Tue, 17 Jun 2014 19:28:22 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s5HJSKeD007038; Tue, 17 Jun 2014 15:28:20 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s5HJSKsl007032; Tue, 17 Jun 2014 15:28:20 -0400 Date: Tue, 17 Jun 2014 15:28:20 -0400 Message-Id: <201406171928.s5HJSKsl007032@hobgoblin.ariadne.com> From: worley@ariadne.com (Dale R. Worley) Sender: worley@ariadne.com (Dale R. Worley) To: Andrew Allen In-reply-to: (aallen@blackberry.com) References: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1403033302; bh=bmDAgfhI5PJBiz/iKxAPGDAJ+HtCwhf5cMBULHRPHx4=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=lmWa/nnvo64tGr+yEZppdlx7NCdDdZamOTQZ3+c3YfN2e98TvjjRuU3cQkOHyPxmh HXmBRjjoZuK9IY+helhzvZFuzGzkfgYGRGCZjQ84kTi0PHapZuDUERfImHUT0adtnI l7DTVZY4wSjWQClevF22DU9bzziQ5OsyNp3J7n28/3lJKvK5HC8G3jGa36qO8Rzs7c e/oCyJtjm0hRJOtnXHlTU77v0FYiFDvQ5Ufh+hFTeO9ZW1yp0dhsvCOgGn6mPJffco gWqP/5kDN5OfWoutarkkDy4FaDmdtcOGKgxW+tbpdXLz2nf4vfp7ZphHGReyJyAWW3 3IOhw8IxRx87A== Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/X8eqQJqW57udg3eKngL-ZxEfIu8 Cc: dispatch@ietf.org Subject: Re: [dispatch] MEID URN X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 19:28:24 -0000 > From: Andrew Allen > > 3GPP2 CDMA devices that do not support 3GPP networks do not have an > IMEI and only have an MEID. OK, that explains why we need this. You may want to incorporate these answers into the introduction, or into some sort of "motivation" section, so the relationships are clear to the reader who isn't familiar with 3GPP/3GPP2. Dale From nobody Wed Jun 18 12:32:49 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3845E1A029F for ; Wed, 18 Jun 2014 12:32:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LNsE-lZb7CRj for ; Wed, 18 Jun 2014 12:32:46 -0700 (PDT) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59E331A0289 for ; Wed, 18 Jun 2014 12:32:46 -0700 (PDT) Received: by mail-wi0-f173.google.com with SMTP id cc10so8222339wib.12 for ; Wed, 18 Jun 2014 12:32:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=CRnErWyro3fs6hIgY8KZwVv3eSZ56MY5sYlHgBUkY+o=; b=Q16Emi9O7AKdBSOPHHcPHxsAv1Og4Dy0w6Z9ObZFeA/1GThpMmzuiGVgaiYtTLS/oL picWqkEib0LZ/HNsSHNEuxPD5skZ/u+Qj2BUq3cUY4DFXvA1IopJ/JId8qTyN6lK6UwY cTcuJvUXCQIh7RXtZis3up5MilZXxSeqjAEhh5cLvCrCel4PXsLngcD9UJxw5yw2XHnA sHbV4xAbr1sZVm2AIYfnnoX5oOjKIatsVWsyyMwUFD15/X4/EReXm9dDDvrmeTfjkkcu zhebi9Q+LbXxbMy8b/W3C/vUBQAizS5o6faGXjzIQsC6gRx0IKjhwQTUduJeMa5vGfAA 0nKA== MIME-Version: 1.0 X-Received: by 10.194.92.244 with SMTP id cp20mr15874wjb.109.1403119965017; Wed, 18 Jun 2014 12:32:45 -0700 (PDT) Received: by 10.194.51.134 with HTTP; Wed, 18 Jun 2014 12:32:44 -0700 (PDT) Date: Wed, 18 Jun 2014 12:32:44 -0700 Message-ID: From: Martin Thomson To: dispatch.chairs@tools.ietf.org, dispatch@ietf.org Content-Type: text/plain; charset=UTF-8 Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/Ez0d_3HZxUjEUc1jd5fTdOMHl6Y Cc: Doug Turner Subject: [dispatch] Charter Proposal: Web Push X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2014 19:32:48 -0000 I notice that the deadlines have been added to the wiki [1], and we're already past them. I didn't see any announcement, so I apologize for being a little late with this request. We don't believe that this work is enough to need a full BOF, only a short time in a dispatch session. We'd like to request that time now. Charter: Many applications require continuous access to network communications so that real-time events - such as incoming calls or messages - can be conveyed (or "pushed") to the user in a timely fashion. Uncoordinated use of the network from multiple applications can contribute to unnecessary use of the network on devices. For instance, maintaining sessions can dominate costs over the long term, since events are relatively rare. This is particularly onerous for battery-powered devices, on which network communication contributes a significant portion of power drain. Each independent session independently incurs overheads, causing unnecessary resource usage on devices. Several modern computing platforms provide a push notification service that consolidates application events, distributing those events to applications as they arrive. The single session avoids duplicated overhead costs on devices. This working group will develop a protocol that applications can use to request the delivery of application data to a device using a consolidated push notification service. This protocol will include the ability to push the same message to multiple devices. The work may include an exemplar protocol for devices registering with push services. This work will be done in collaboration with the W3C Webapps Working Group, who are developing a Web Push API for use in web applications (see ). Milestones: 2015-05 Send web push protocol draft to the IESG as Proposed Standard From nobody Thu Jun 19 06:48:51 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71C071A03A3 for ; Thu, 19 Jun 2014 06:48:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LzdZ7mWLg3Tn for ; Thu, 19 Jun 2014 06:48:45 -0700 (PDT) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F1651A0369 for ; Thu, 19 Jun 2014 06:48:45 -0700 (PDT) Received: by mail-we0-f170.google.com with SMTP id w61so2414067wes.29 for ; Thu, 19 Jun 2014 06:48:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2DlfCYaR+RhlUnQOHvmk+ip4BFb1aHBcV8j+wyipXTU=; b=EGRDYMcP99x2KVhZb+20ljTlii8AzH6sgPndOKgCYE5ABLLbxwiKzgGaQf/b4bAKwi UQooAijHN03TvZzWMrcEdpa1c2WyG1um5X95FVoCDaXNWga1pzaI70IQOaIdcg7Aa8j8 uQLIg04LHT9TDCuuYIosTZuf4Wh3dz6e7BWY+F9sgtI5AKtIftCeu8gpw1MxAS5BWZPQ 0o6/TB8t2BO7JRMg7Fk1tEEP2Jc0W4brCVaWY4OkLTCKTovV3y514c5oWIRZJ4uxcaqp MQcbpNHUzZjeWrdIT/tUsNk9k/lZwDVKgQuma1Ws6XQ20H+/aAey17PXnx4GuMWVe8yB 2akQ== MIME-Version: 1.0 X-Received: by 10.180.218.41 with SMTP id pd9mr6730566wic.7.1403185723781; Thu, 19 Jun 2014 06:48:43 -0700 (PDT) Received: by 10.217.116.201 with HTTP; Thu, 19 Jun 2014 06:48:43 -0700 (PDT) In-Reply-To: References: Date: Thu, 19 Jun 2014 08:48:43 -0500 Message-ID: From: Mary Barnes To: Martin Thomson Content-Type: multipart/alternative; boundary=001a1134d4089eba8904fc30a2e5 Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/w4Oj1k7FlXEGWn4VKfowUQM2TzM Cc: dispatch.chairs@tools.ietf.org, DISPATCH , Doug Turner Subject: Re: [dispatch] Charter Proposal: Web Push X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2014 13:48:47 -0000 --001a1134d4089eba8904fc30a2e5 Content-Type: text/plain; charset=UTF-8 Thanks! Mary. On Wed, Jun 18, 2014 at 2:32 PM, Martin Thomson wrote: > I notice that the deadlines have been added to the wiki [1], and we're > already past them. I didn't see any announcement, so I apologize for > being a little late with this request. > > We don't believe that this work is enough to need a full BOF, only a > short time in a dispatch session. We'd like to request that time now. > > Charter: > > Many applications require continuous access to network communications > so that real-time events - such as incoming calls or messages - can > be conveyed (or "pushed") to the user in a timely fashion. > Uncoordinated use of the network from multiple applications can > contribute to unnecessary use of the network on devices. For > instance, maintaining sessions can dominate costs over the long term, > since events are relatively rare. This is particularly onerous for > battery-powered devices, on which network communication contributes a > significant portion of power drain. Each independent session > independently incurs overheads, causing unnecessary resource usage on > devices. > > Several modern computing platforms provide a push notification > service that consolidates application events, distributing those > events to applications as they arrive. The single session avoids > duplicated overhead costs on devices. > > This working group will develop a protocol that applications can use > to request the delivery of application data to a device using a > consolidated push notification service. This protocol will include the > ability to push the same message to multiple devices. The work may > include an exemplar protocol for devices registering with push > services. > > This work will be done in collaboration with the W3C Webapps Working > Group, who are developing a Web Push API for use in web applications > (see ). > > Milestones: > > 2015-05 Send web push protocol draft to the IESG as Proposed Standard > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > --001a1134d4089eba8904fc30a2e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks!=C2=A0

Mary.


On Wed, Jun 18, 2014 = at 2:32 PM, Martin Thomson <martin.thomson@gmail.com>= wrote:
I notice that the deadlines have been added = to the wiki [1], and we're
already past them. =C2=A0I didn't see any announcement, so I apologize = for
being a little late with this request.

We don't believe that this work is enough to need a full BOF, only a short time in a dispatch session. =C2=A0We'd like to request that time = now.

Charter:

=C2=A0 =C2=A0Many applications require continuous access to network communi= cations
=C2=A0 =C2=A0so that real-time events - such as incoming calls or messages = - can
=C2=A0 =C2=A0be conveyed (or "pushed") to the user in a timely fa= shion.
=C2=A0 =C2=A0Uncoordinated use of the network from multiple applications ca= n
=C2=A0 =C2=A0contribute to unnecessary use of the network on devices. =C2= =A0For
=C2=A0 =C2=A0instance, maintaining sessions can dominate costs over the lon= g term,
=C2=A0 =C2=A0since events are relatively rare. =C2=A0This is particularly o= nerous for
=C2=A0 =C2=A0battery-powered devices, on which network communication contri= butes a
=C2=A0 =C2=A0significant portion of power drain. =C2=A0Each independent ses= sion
=C2=A0 =C2=A0independently incurs overheads, causing unnecessary resource u= sage on
=C2=A0 =C2=A0devices.

=C2=A0 =C2=A0Several modern computing platforms provide a push notification=
=C2=A0 =C2=A0service that consolidates application events, distributing tho= se
=C2=A0 =C2=A0events to applications as they arrive. =C2=A0The single sessio= n avoids
=C2=A0 =C2=A0duplicated overhead costs on devices.

=C2=A0 =C2=A0This working group will develop a protocol that applications c= an use
=C2=A0 =C2=A0to request the delivery of application data to a device using = a
=C2=A0 =C2=A0consolidated push notification service. =C2=A0This protocol wi= ll include the
=C2=A0 =C2=A0ability to push the same message to multiple devices. =C2=A0Th= e work may
=C2=A0 =C2=A0include an exemplar protocol for devices registering with push=
=C2=A0 =C2=A0services.

=C2=A0 =C2=A0This work will be done in collaboration with the W3C Webapps W= orking
=C2=A0 =C2=A0Group, who are developing a Web Push API for use in web applic= ations
=C2=A0 =C2=A0(see <http://www.w3.org/TR/push-api/>).

Milestones:

=C2=A0 2015-05 Send web push protocol draft to the IESG as Proposed Standar= d

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

--001a1134d4089eba8904fc30a2e5-- From nobody Thu Jun 26 11:29:01 2014 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F8F1B2FA6 for ; Thu, 26 Jun 2014 11:28:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.652 X-Spam-Level: X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8FgE2lAyIXQI for ; Thu, 26 Jun 2014 11:28:54 -0700 (PDT) Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C76591B2D73 for ; Thu, 26 Jun 2014 11:06:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1403805988; x=1435341988; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=E6XscCXKAiYmJc7Ok12rafG7OWf3eNZg5scZuPnG4YQ=; b=CM7DR6V2qmid7zF3w0CWXR2MjV4xP/VFlNfkFVG+GG6oSjUq7ZaqMCZ9 MtTymPviL7VHbNR9aDM+UA4Sw9WXuJj28M6i8Czo+0EL5IbzKAVGV05Wz h7ayJcQCBubKrUSLrXpcBM2RGe8Ia5a9uOyd/zBX3E0PK6WhP3D7ezQce k=; X-IronPort-AV: E=McAfee;i="5600,1067,7481"; a="67735014" Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth01.qualcomm.com with ESMTP; 26 Jun 2014 11:06:27 -0700 X-IronPort-AV: E=Sophos;i="5.01,554,1400050800"; d="scan'208";a="29988731" Received: from nasanexhc12.na.qualcomm.com ([172.30.39.187]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 26 Jun 2014 11:06:27 -0700 Received: from NASANEXD02C.na.qualcomm.com ([169.254.6.233]) by nasanexhc12.na.qualcomm.com ([172.30.39.187]) with mapi id 14.03.0181.006; Thu, 26 Jun 2014 11:06:26 -0700 From: "Atarius, Roozbeh" To: "Dale R. Worley" , Andrew Allen Thread-Topic: [dispatch] MEID URN Thread-Index: Ac+Jlu8FjStcWJ84QX6af3JG7fXmEpuDtpdQ Date: Thu, 26 Jun 2014 18:06:25 +0000 Message-ID: References: <201406171928.s5HJSKsl007032@hobgoblin.ariadne.com> In-Reply-To: <201406171928.s5HJSKsl007032@hobgoblin.ariadne.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [199.106.115.192] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/AFns7lBkcx9pZmFsY5MpbjK5mkE Cc: "dispatch@ietf.org" Subject: Re: [dispatch] MEID URN X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2014 18:28:59 -0000 Done! http://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn/ thanks Roozbeh Atarius -----Original Message----- From: Dale R. Worley [mailto:worley@ariadne.com]=20 Sent: Tuesday, June 17, 2014 12:28 PM To: Andrew Allen Cc: dispatch@ietf.org Subject: Re: [dispatch] MEID URN > From: Andrew Allen >=20 > 3GPP2 CDMA devices that do not support 3GPP networks do not have an=20 > IMEI and only have an MEID. OK, that explains why we need this. You may want to incorporate these answers into the introduction, or into so= me sort of "motivation" section, so the relationships are clear to the read= er who isn't familiar with 3GPP/3GPP2. Dale