From speermint-bounces@ietf.org Thu May 10 15:50:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmEeQ-0004Xa-4Y; Thu, 10 May 2007 15:50:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmEeI-0004TR-Ff; Thu, 10 May 2007 15:50:02 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmEeI-00075G-5x; Thu, 10 May 2007 15:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 285BE329FF; Thu, 10 May 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HmEeI-0002uf-1f; Thu, 10 May 2007 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 10 May 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: speermint@ietf.org Subject: [Speermint] I-D ACTION:draft-ietf-speermint-consolidated-presence-im-usecases-01.txt X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : Presence & IM Use Cases Author(s) : A. Houri, et al. Filename : draft-ietf-speermint-consolidated-presence-im-usecases-01.txt Pages : 12 Date : 2007-5-10 The document describes several use cases of peering between two or more service providers that provide none VOIP based collaboration services and presence and IM in particular. These service providers create a peering relationship between themselves thus enabling their users to collaborate with users on other communities. The target of the document is to drive requirements for peering between domains that provide the none VOIP based collaboration services. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-speermint-consolidated-presence-im-usecases-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-5-10102940.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-speermint-consolidated-presence-im-usecases-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-5-10102940.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --NextPart-- From speermint-bounces@ietf.org Thu May 10 16:00:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmEoo-0000Bp-NR; Thu, 10 May 2007 16:00:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmEon-0000AX-Gi for speermint@ietf.org; Thu, 10 May 2007 16:00:53 -0400 Received: from mtagate1.de.ibm.com ([195.212.29.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmEol-0001AF-2T for speermint@ietf.org; Thu, 10 May 2007 16:00:53 -0400 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate1.de.ibm.com (8.13.8/8.13.8) with ESMTP id l4AK0oVp157818 for ; Thu, 10 May 2007 20:00:50 GMT Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l4AK0n9a4096156 for ; Thu, 10 May 2007 22:00:50 +0200 Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l4AK0iKj014114 for ; Thu, 10 May 2007 22:00:44 +0200 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l4AK0it0014029 for ; Thu, 10 May 2007 22:00:44 +0200 To: speermint@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF144 February 01, 2006 From: Avshalom Houri Message-ID: Date: Thu, 10 May 2007 23:00:32 +0300 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 10/05/2007 23:00:43, Serialize complete at 10/05/2007 23:00:43 X-Spam-Score: 0.1 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Subject: [Speermint] New version of presence and IM usecases X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1934165952==" Errors-To: speermint-bounces@ietf.org This is a multipart message in MIME format. --===============1934165952== Content-Type: multipart/alternative; boundary="=_alternative 006DE803C22572D7_=" This is a multipart message in MIME format. --=_alternative 006DE803C22572D7_= Content-Type: text/plain; charset="US-ASCII" Updated to address comments during the Prague meeting. Requirements are separated into a separate draft that will appear shortly. Please comment. http://www.ietf.org/internet-drafts/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt Thanks --Avshalom Attention is the hardest currency to pay --=_alternative 006DE803C22572D7_= Content-Type: text/html; charset="US-ASCII"
Updated to address comments during the Prague meeting.
Requirements are separated into a separate draft that will appear shortly.
Please comment.

http://www.ietf.org/internet-drafts/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt
Thanks
--Avshalom
  Attention is the hardest currency to pay
 --=_alternative 006DE803C22572D7_=-- --===============1934165952== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --===============1934165952==-- From speermint-bounces@ietf.org Fri May 11 21:31:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmgS6-00039o-Lg; Fri, 11 May 2007 21:31:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmgS6-00039j-1n for speermint@ietf.org; Fri, 11 May 2007 21:31:18 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmgS2-0000Jq-MH for speermint@ietf.org; Fri, 11 May 2007 21:31:18 -0400 Received: from rshockeyPC (h-68-165-240-38.mclnva23.covad.net [68.165.240.38]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l4C1Uw0l012507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 11 May 2007 18:31:00 -0700 From: "Richard Shockey" To: References: In-Reply-To: Date: Fri, 11 May 2007 21:30:53 -0400 Message-ID: <02d801c79435$2f7e6aa0$8e7b3fe0$@us> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Content-language: en-us Thread-Index: AceTPelQszySz/szQJyJTHzUMg3jpQA9xg+w x-cr-hashedpuzzle: AQbT BOIX BwGM B8ZE COF5 CnPB CuF+ DC9y D2u3 GcvN GxG/ Hv5e J4nW KFtX K9xa L7Eb; 1; cwBwAGUAZQByAG0AaQBuAHQAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {FAF6B192-4DAB-491E-9B3B-59FC6C8AE204}; cgBpAGMAaABhAHIAZABAAHMAaABvAGMAawBlAHkALgB1AHMA; Sat, 12 May 2007 01:30:50 GMT; RgBZAEkAIAAtACAAVwBoAGkAbABlACAAeQBvAHUAIABjAG8AbgB0AGkAbgB1AGUAIAB0AG8AIAB0AGEAbABrACAAbwB0AGgAZQByAHMAIABhAHIAZQAgAHQAcgB5AGkAbgBnACAAdABvACAAZwBlAHQAIABvAHIAZwBhAG4AaQB6AGUAZAAuAA== x-cr-puzzleid: {FAF6B192-4DAB-491E-9B3B-59FC6C8AE204} X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.2 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Subject: [Speermint] FYI - While you continue to talk others are trying to get organized. X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0807920161==" Errors-To: speermint-bounces@ietf.org This is a multipart message in MIME format. --===============0807920161== Content-Type: multipart/alternative; boundary="----=_NextPart_000_02D9_01C79413.A86CCAA0" Content-language: en-us This is a multipart message in MIME format. ------=_NextPart_000_02D9_01C79413.A86CCAA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit http://www.siptrunk.org/ ------=_NextPart_000_02D9_01C79413.A86CCAA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

http://www.siptrunk.org/

------=_NextPart_000_02D9_01C79413.A86CCAA0-- --===============0807920161== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --===============0807920161==-- From speermint-bounces@ietf.org Tue May 15 18:51:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ho5rC-00009U-7e; Tue, 15 May 2007 18:51:02 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ho5qj-000710-4u; Tue, 15 May 2007 18:50:33 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ho5qi-0005fT-P1; Tue, 15 May 2007 18:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 98E052AC7B; Tue, 15 May 2007 22:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Ho5qE-00043F-53; Tue, 15 May 2007 18:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 15 May 2007 18:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: speermint@ietf.org Subject: [Speermint] I-D ACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : VoIP SIP Peering Use Cases Author(s) : A. Uzelac, et al. Filename : draft-ietf-speermint-voip-consolidated-usecases-01.txt Pages : 20 Date : 2007-5-15 This document will capture the VoIP use case for SIP Peering. It is a consolidation of other Speermint use cases and will focus exclusively on VoIP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-speermint-voip-consolidated-usecases-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-5-15161655.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-speermint-voip-consolidated-usecases-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-5-15161655.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --NextPart-- From speermint-bounces@ietf.org Wed May 16 02:06:17 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoCeM-0005ca-OR; Wed, 16 May 2007 02:06:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoCeL-0005cS-F6 for speermint@ietf.org; Wed, 16 May 2007 02:06:13 -0400 Received: from mtagate3.de.ibm.com ([195.212.29.152]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoCeK-0005mc-O1 for speermint@ietf.org; Wed, 16 May 2007 02:06:13 -0400 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate3.de.ibm.com (8.13.8/8.13.8) with ESMTP id l4G66A2x181490 for ; Wed, 16 May 2007 06:06:10 GMT Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l4G665Hd2228264 for ; Wed, 16 May 2007 08:06:10 +0200 Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l4G65tWG018487 for ; Wed, 16 May 2007 08:05:55 +0200 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l4G65tSt018441 for ; Wed, 16 May 2007 08:05:55 +0200 To: speermint@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 August 18, 2005 From: Avshalom Houri Message-ID: Date: Wed, 16 May 2007 09:05:49 +0300 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 16/05/2007 09:05:55, Serialize complete at 16/05/2007 09:05:55 X-Spam-Score: 0.1 (/) X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d Subject: [Speermint] Fw: I-D ACTION:draft-houri-speermint-presence-im-requirements-00.txt X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0956863130==" Errors-To: speermint-bounces@ietf.org This is a multipart message in MIME format. --===============0956863130== Content-Type: multipart/alternative; boundary="=_alternative 00217AA0C22572DD_=" This is a multipart message in MIME format. --=_alternative 00217AA0C22572DD_= Content-Type: text/plain; charset="US-ASCII" FYC (comments). Baesed on http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-01.txt --Avshalom ----- Forwarded by Avshalom Houri/Haifa/IBM on 16/05/2007 09:04 ----- Internet-Drafts@ietf.org 16/05/2007 01:50 Please respond to internet-drafts@ietf.org To i-d-announce@ietf.org cc Subject I-D ACTION:draft-houri-speermint-presence-im-requirements-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Presence & IM Requirements Author(s) : A. Houri, et al. Filename : draft-houri-speermint-presence-im-requirements-00.txt Pages : 12 Date : 2007-5-15 The document lists requirements for peering between two or more service providers that provide none VOIP based collaboration services and presence and IM in particular. These service providers create a peering relationship between themselves thus enabling their users to collaborate with users on other communities. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-houri-speermint-presence-im-requirements-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ftp://anonymous@ftp.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --=_alternative 00217AA0C22572DD_= Content-Type: text/html; charset="US-ASCII"
FYC (comments). Baesed on

http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-01.txt

--Avshalom
----- Forwarded by Avshalom Houri/Haifa/IBM on 16/05/2007 09:04 -----
Internet-Drafts@ietf.org

16/05/2007 01:50
Please respond to
internet-drafts@ietf.org
To
i-d-announce@ietf.org
cc
Subject
I-D ACTION:draft-houri-speermint-presence-im-requirements-00.txt





A New Internet-Draft is available from the on-line Internet-Drafts
directories.


                Title                                  : Presence & IM Requirements
                Author(s)                 : A. Houri, et al.
                Filename                 : draft-houri-speermint-presence-im-requirements-00.txt
                Pages                                  : 12
                Date                                  : 2007-5-15
               
  The document lists requirements for peering between two or more
  service providers that provide none VOIP based collaboration services
  and presence and IM in particular.  These service providers create a
  peering relationship between themselves thus enabling their users to
  collaborate with users on other communities.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-houri-speermint-presence-im-requirements-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
                mailserv@ietf.org.
In the body type:
                "FILE /internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt".
               
NOTE:                 The mail server at ietf.org can return the document in
                MIME-encoded form by using the "mpack" utility.  To use this
                feature, insert the command "ENCODING mime" before the "FILE"
                command.  To decode the response(s), you will need "munpack" or
                a MIME-compliant mail reader.  Different MIME-compliant mail readers
                exhibit different behavior, especially when dealing with
                "multipart" MIME messages (i.e. documents which have been split
                up into multiple messages), so check your local documentation on
                how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://anonymous@ftp.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce
 --=_alternative 00217AA0C22572DD_=-- --===============0956863130== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --===============0956863130==-- From speermint-bounces@ietf.org Wed May 16 04:47:48 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoFAg-0005c6-GV; Wed, 16 May 2007 04:47:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoFAf-0005by-JL for speermint@ietf.org; Wed, 16 May 2007 04:47:45 -0400 Received: from mtagate8.de.ibm.com ([195.212.29.157]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoFAe-0002DL-P1 for speermint@ietf.org; Wed, 16 May 2007 04:47:45 -0400 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate8.de.ibm.com (8.13.8/8.13.8) with ESMTP id l4G8lh8S219092 for ; Wed, 16 May 2007 08:47:43 GMT Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l4G8lcrx4014244 for ; Wed, 16 May 2007 10:47:43 +0200 Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l4G8lSmQ030277 for ; Wed, 16 May 2007 10:47:28 +0200 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l4G8lSic029828 for ; Wed, 16 May 2007 10:47:28 +0200 In-Reply-To: To: speermint@ietf.org MIME-Version: 1.0 Subject: Re: [Speermint] Fw: I-D ACTION:draft-houri-speermint-presence-im-requirements-00.txt X-Mailer: Lotus Notes Release 7.0 August 18, 2005 From: Avshalom Houri Message-ID: Date: Wed, 16 May 2007 11:47:16 +0300 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 16/05/2007 11:47:27, Serialize complete at 16/05/2007 11:47:27 X-Spam-Score: 0.1 (/) X-Scan-Signature: 90e8b0e368115979782f8b3d811b226b X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1567773776==" Errors-To: speermint-bounces@ietf.org This is a multipart message in MIME format. --===============1567773776== Content-Type: multipart/alternative; boundary="=_alternative 003043E0C22572DD_=" This is a multipart message in MIME format. --=_alternative 003043E0C22572DD_= Content-Type: text/plain; charset="US-ASCII" Sorry it is based on: http://www.ietf.org/internet-drafts/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt (Should not send emails early in the morning...) Thanks --Avshalom Avshalom Houri/Haifa/IBM@IBMIL 16/05/2007 09:05 To speermint@ietf.org cc Subject [Speermint] Fw: I-D ACTION:draft-houri-speermint-presence-im-requirements-00.txt FYC (comments). Baesed on http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-01.txt --Avshalom ----- Forwarded by Avshalom Houri/Haifa/IBM on 16/05/2007 09:04 ----- Internet-Drafts@ietf.org 16/05/2007 01:50 Please respond to internet-drafts@ietf.org To i-d-announce@ietf.org cc Subject I-D ACTION:draft-houri-speermint-presence-im-requirements-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Presence & IM Requirements Author(s) : A. Houri, et al. Filename : draft-houri-speermint-presence-im-requirements-00.txt Pages : 12 Date : 2007-5-15 The document lists requirements for peering between two or more service providers that provide none VOIP based collaboration services and presence and IM in particular. These service providers create a peering relationship between themselves thus enabling their users to collaborate with users on other communities. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-houri-speermint-presence-im-requirements-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ftp://anonymous@ftp.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --=_alternative 003043E0C22572DD_= Content-Type: text/html; charset="US-ASCII"
Sorry it is based on:

http://www.ietf.org/internet-drafts/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt

(Should not send emails early in the morning...)

Thanks
--Avshalom


Avshalom Houri/Haifa/IBM@IBMIL

16/05/2007 09:05

To
speermint@ietf.org
cc
Subject
[Speermint] Fw: I-D        ACTION:draft-houri-speermint-presence-im-requirements-00.txt






FYC (comments). Baesed on

http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-01.txt


--Avshalom





----- Forwarded by Avshalom Houri/Haifa/IBM on 16/05/2007 09:04 -----
Internet-Drafts@ietf.org

16/05/2007 01:50
Please respond to
internet-drafts@ietf.org
To
i-d-announce@ietf.org
cc
Subject
I-D ACTION:draft-houri-speermint-presence-im-requirements-00.txt







A New Internet-Draft is available from the on-line Internet-Drafts
directories.


               Title                                  : Presence & IM Requirements
               Author(s)                 : A. Houri, et al.
               Filename                 : draft-houri-speermint-presence-im-requirements-00.txt
               Pages                                  : 12
               Date                                  : 2007-5-15
               
 The document lists requirements for peering between two or more
 service providers that provide none VOIP based collaboration services
 and presence and IM in particular.  These service providers create a
 peering relationship between themselves thus enabling their users to
 collaborate with users on other communities.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-houri-speermint-presence-im-requirements-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
               mailserv@ietf.org.
In the body type:
               "FILE /internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt".
               
NOTE:                 The mail server at ietf.org can return the document in
               MIME-encoded form by using the "mpack" utility.  To use this
               feature, insert the command "ENCODING mime" before the "FILE"
               command.  To decode the response(s), you will need "munpack" or
               a MIME-compliant mail reader.  Different MIME-compliant mail readers
               exhibit different behavior, especially when dealing with
               "multipart" MIME messages (i.e. documents which have been split
               up into multiple messages), so check your local documentation on
               how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://anonymous@ftp.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint
--=_alternative 003043E0C22572DD_=-- --===============1567773776== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --===============1567773776==-- From speermint-bounces@ietf.org Wed May 16 23:29:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoWgb-0007gw-KR; Wed, 16 May 2007 23:29:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoWga-0007gr-BO for speermint@ietf.org; Wed, 16 May 2007 23:29:52 -0400 Received: from pacdcimo01.cable.comcast.com ([24.40.8.145]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoWgZ-00076u-2y for speermint@ietf.org; Wed, 16 May 2007 23:29:52 -0400 Received: from ([10.195.246.152]) by pacdcimo01.cable.comcast.com with ESMTP id KP-BXT38.3665137; Wed, 16 May 2007 23:29:37 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by NJMDCEXCRLY01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 May 2007 23:29:37 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 16 May 2007 23:29:18 -0400 Message-ID: <45AEC6EF95942140888406588E1A660201A2984C@PACDCEXCMB04.cable.comcast.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [wg-business] Milestones Updated Thread-Index: AceYM40MrY4fkm09Sn6rlUgK3N+Rmw== From: "Livingood, Jason" To: X-OriginalArrivalTime: 17 May 2007 03:29:37.0318 (UTC) FILETIME=[98886C60:01C79833] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Subject: [Speermint] [wg-business] Milestones Updated X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org See the bottom of our charter (which is unchanged). =20 http://www.ietf.org/html.charters/speermint-charter.html Regards Jason _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Thu May 17 05:42:50 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HocVT-0004OU-RY; Thu, 17 May 2007 05:42:47 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HocVT-0004OP-1z for speermint@ietf.org; Thu, 17 May 2007 05:42:47 -0400 Received: from mtagate2.de.ibm.com ([195.212.29.151]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HocVS-0002JX-Ih for speermint@ietf.org; Thu, 17 May 2007 05:42:47 -0400 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate2.de.ibm.com (8.13.8/8.13.8) with ESMTP id l4H9gj37194532 for ; Thu, 17 May 2007 09:42:45 GMT Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l4H9geFw3858680 for ; Thu, 17 May 2007 11:42:45 +0200 Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l4H9gUFa007939 for ; Thu, 17 May 2007 11:42:30 +0200 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l4H9gUA6007705; Thu, 17 May 2007 11:42:30 +0200 In-Reply-To: <45AEC6EF95942140888406588E1A660201A2984C@PACDCEXCMB04.cable.comcast.com> To: "Livingood, Jason" Subject: Re: [Speermint] [wg-business] Milestones Updated MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 August 18, 2005 From: Avshalom Houri Message-ID: Date: Thu, 17 May 2007 12:42:13 +0300 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 17/05/2007 12:42:30, Serialize complete at 17/05/2007 12:42:30 X-Spam-Score: 0.1 (/) X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7 Cc: speermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0114622787==" Errors-To: speermint-bounces@ietf.org This is a multipart message in MIME format. --===============0114622787== Content-Type: multipart/alternative; boundary="=_alternative 00353C3CC22572DE_=" This is a multipart message in MIME format. --=_alternative 00353C3CC22572DE_= Content-Type: text/plain; charset="US-ASCII" Do not see the requirements milestone for presence and IM. Should be the same as VOIP (Feb 2008). First draft of these is available: http://www.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt Also, whenever IM is mentioned it should be presence and IM. Thanks --Avshalom "Livingood, Jason" 17/05/2007 06:29 To cc Subject [Speermint] [wg-business] Milestones Updated See the bottom of our charter (which is unchanged). http://www.ietf.org/html.charters/speermint-charter.html Regards Jason _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --=_alternative 00353C3CC22572DE_= Content-Type: text/html; charset="US-ASCII"
Do not see the requirements milestone for presence and IM.
Should be the same as VOIP (Feb 2008). First draft of these
is available:

http://www.ietf.org/internet-drafts/draft-houri-speermint-presence-im-requirements-00.txt

Also, whenever IM is mentioned it should be presence and IM.

Thanks
--Avshalom


"Livingood, Jason" <Jason_Livingood@cable.comcast.com>

17/05/2007 06:29

To
<speermint@ietf.org>
cc
Subject
[Speermint] [wg-business] Milestones Updated





See the bottom of our charter (which is unchanged).  

http://www.ietf.org/html.charters/speermint-charter.html

Regards
Jason

_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint
--=_alternative 00353C3CC22572DE_=-- --===============0114622787== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --===============0114622787==-- From speermint-bounces@ietf.org Thu May 17 23:39:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HotJ2-0002Qn-VO; Thu, 17 May 2007 23:39:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HotJ1-0002Qe-St for speermint@ietf.org; Thu, 17 May 2007 23:39:03 -0400 Received: from paoakoavas10.cable.comcast.com ([208.17.35.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HotJ0-0006vz-Jk for speermint@ietf.org; Thu, 17 May 2007 23:39:03 -0400 Received: from ([10.52.116.31]) by paoakoavas10.cable.comcast.com with ESMTP id KP-TDCH7.32861502; Thu, 17 May 2007 23:38:48 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 17 May 2007 23:38:48 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speermint] I-D ACTION:draft-ietf-speermint-consolidated-presence-im-usecases-01.txt Date: Thu, 17 May 2007 23:38:48 -0400 Message-ID: <45AEC6EF95942140888406588E1A660201A2987E@PACDCEXCMB04.cable.comcast.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] I-D ACTION:draft-ietf-speermint-consolidated-presence-im-usecases-01.txt Thread-Index: AceTPMMR/ELp3VadStaQ54KIUMMgUgFlIaXA References: From: "Livingood, Jason" To: X-OriginalArrivalTime: 18 May 2007 03:38:48.0215 (UTC) FILETIME=[0B4E6270:01C798FE] X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Cc: Avshalom Houri X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Please send any comments to the authors asap. If there are any immediate comments, I'd like to see them before Chicago, so they can come with a -02 rev. Thanks Jason=20 > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 > Sent: Thursday, May 10, 2007 3:50 PM > To: i-d-announce@ietf.org > Cc: speermint@ietf.org > Subject: [Speermint] I-D=20 > ACTION:draft-ietf-speermint-consolidated-presence-im-usecases-01.txt=20 >=20 > A New Internet-Draft is available from the on-line=20 > Internet-Drafts directories. > This draft is a work item of the Session PEERing for=20 > Multimedia INTerconnect Working Group of the IETF. >=20 > Title : Presence & IM Use Cases > Author(s) : A. Houri, et al. > Filename :=20 > draft-ietf-speermint-consolidated-presence-im-usecases-01.txt > Pages : 12 > Date : 2007-5-10 > =09 > The document describes several use cases of peering between two or > more service providers that provide none VOIP based collaboration > services and presence and IM in particular. These service=20 > providers > create a peering relationship between themselves thus=20 > enabling their > users to collaborate with users on other communities. The=20 > target of > the document is to drive requirements for peering between domains > that provide the none VOIP based collaboration services. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-speermint-conso > lidated-presence-im-usecases-01.txt >=20 > To remove yourself from the I-D Announcement list, send a=20 > message to i-d-announce-request@ietf.org with the word=20 > unsubscribe in the body of the message.=20 > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. >=20 > Internet-Drafts are also available by anonymous FTP. Login=20 > with the username "anonymous" and a password of your e-mail=20 > address. After logging in, type "cd internet-drafts" and then=20 > "get draft-ietf-speermint-consolidated-presence-im-usecases-01.txt". >=20 > A list of Internet-Drafts directories can be found in=20 > http://www.ietf.org/shadow.html or=20 > ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE=20 > /internet-drafts/draft-ietf-speermint-consolidated-presence-im > -usecases-01.txt". > =09 > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant=20 > mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. >=20 > Below is the data which will enable a MIME compliant mail=20 > reader implementation to automatically retrieve the ASCII=20 > version of the Internet-Draft. >=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Thu May 17 23:39:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HotJA-0002S5-7O; Thu, 17 May 2007 23:39:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HotJ8-0002Rr-W1 for speermint@ietf.org; Thu, 17 May 2007 23:39:10 -0400 Received: from paoakoavas09.cable.comcast.com ([208.17.35.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HotJ7-0006wD-KH for speermint@ietf.org; Thu, 17 May 2007 23:39:10 -0400 Received: from ([10.52.116.31]) by paoakoavas09.cable.comcast.com with ESMTP id KP-NTF18.42956709; Thu, 17 May 2007 23:38:48 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 17 May 2007 23:38:47 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Speermint] [wg-business] Milestones Updated Date: Thu, 17 May 2007 23:38:48 -0400 Message-ID: <45AEC6EF95942140888406588E1A660201A2987D@PACDCEXCMB04.cable.comcast.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] [wg-business] Milestones Updated Thread-Index: AceYZ8FDZ7id9Lp7Tnixj+StAUFaxAAaSiUw References: <45AEC6EF95942140888406588E1A660201A2984C@PACDCEXCMB04.cable.comcast.com> From: "Livingood, Jason" To: "Avshalom Houri" X-OriginalArrivalTime: 18 May 2007 03:38:47.0996 (UTC) FILETIME=[0B2CF7C0:01C798FE] X-Spam-Score: 0.3 (/) X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250 Cc: speermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2123627007==" Errors-To: speermint-bounces@ietf.org This is a multi-part message in MIME format. --===============2123627007== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C798FE.0B3279E7" This is a multi-part message in MIME format. ------_=_NextPart_001_01C798FE.0B3279E7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable You are correct - it is the same as VoIP. =20 J ________________________________ From: Avshalom Houri [mailto:AVSHALOM@il.ibm.com]=20 Sent: Thursday, May 17, 2007 5:42 AM To: Livingood, Jason Cc: speermint@ietf.org Subject: Re: [Speermint] [wg-business] Milestones Updated =09 =09 Do not see the requirements milestone for presence and IM.=20 Should be the same as VOIP (Feb 2008). First draft of these=20 is available:=20 =09 =09 http://www.ietf.org/internet-drafts/draft-houri-speermint-presence-im-re quirements-00.txt=20 =09 Also, whenever IM is mentioned it should be presence and IM.=20 =09 Thanks --Avshalom =09 =09 =09 =09 =09 =09 =09 "Livingood, Jason" =20 17/05/2007 06:29=20 To =20 cc Subject [Speermint] [wg-business] Milestones Updated =09 See the bottom of our charter (which is unchanged). =20 =09 http://www.ietf.org/html.charters/speermint-charter.html =09 Regards Jason =09 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint =09 =09 ------_=_NextPart_001_01C798FE.0B3279E7 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
You are correct - it is the same as=20 VoIP.
 
J

From: Avshalom Houri=20 [mailto:AVSHALOM@il.ibm.com]
Sent: Thursday, May 17, 2007 = 5:42=20 AM
To: Livingood, Jason
Cc:=20 speermint@ietf.org
Subject: Re: [Speermint] [wg-business] = Milestones=20 Updated


Do not see the = requirements=20 milestone for presence and IM.
Should be the same as VOIP (Feb 2008). First draft of = these=20
is available: =

http://www.ietf.org/internet-drafts/draft-houri-speermint-presen= ce-im-requirements-00.txt=20

Also, whenever IM is = mentioned it=20 should be presence and IM.

Thanks
--Avshalom






"Livingood, = Jason"=20 <Jason_Livingood@cable.comcast.com>

17/05/2007 06:29

To
<speermint@ietf.org>=20
cc
Subject
[Speermint] = [wg-business]=20 Milestones Updated

=




See the bottom of our charter (which is unchanged).=20 =  

http://www.ietf.org/html.charters/speermint-charter.html
Regards
Jason

____________________________________________= ___
Speermint=20 mailing=20 = list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/spee= rmint

------_=_NextPart_001_01C798FE.0B3279E7-- --===============2123627007== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --===============2123627007==-- From speermint-bounces@ietf.org Thu May 17 23:39:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HotJA-0002TE-HB; Thu, 17 May 2007 23:39:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HotJ9-0002Rz-A7 for speermint@ietf.org; Thu, 17 May 2007 23:39:11 -0400 Received: from paoakoavas09.cable.comcast.com ([208.17.35.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HotJ9-0006wD-08 for speermint@ietf.org; Thu, 17 May 2007 23:39:11 -0400 Received: from ([10.52.116.31]) by paoakoavas09.cable.comcast.com with ESMTP id KP-NTF18.42956710; Thu, 17 May 2007 23:38:48 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 17 May 2007 23:38:48 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speermint] I-D ACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt Date: Thu, 17 May 2007 23:38:48 -0400 Message-ID: <45AEC6EF95942140888406588E1A660201A2987F@PACDCEXCMB04.cable.comcast.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] I-D ACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt Thread-Index: AceXQ5LoKh6mOINvSpGrq35soxK40gBjgkkg References: From: "Livingood, Jason" To: X-OriginalArrivalTime: 18 May 2007 03:38:48.0309 (UTC) FILETIME=[0B5CBA50:01C798FE] X-Spam-Score: 0.0 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org As with the IM document, please get comments to the editor asap so we can come to Chicago with a -02 if necessary. Thanks Jason=20 > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 > Sent: Tuesday, May 15, 2007 6:50 PM > To: i-d-announce@ietf.org > Cc: speermint@ietf.org > Subject: [Speermint] I-D=20 > ACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt=20 >=20 > A New Internet-Draft is available from the on-line=20 > Internet-Drafts directories. > This draft is a work item of the Session PEERing for=20 > Multimedia INTerconnect Working Group of the IETF. >=20 > Title : VoIP SIP Peering Use Cases > Author(s) : A. Uzelac, et al. > Filename :=20 > draft-ietf-speermint-voip-consolidated-usecases-01.txt > Pages : 20 > Date : 2007-5-15 > =09 > This document will capture the VoIP use case for SIP Peering. It is=20 > a consolidation of other Speermint use cases and will focus=20 > exclusively on VoIP. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip- > consolidated-usecases-01.txt >=20 > To remove yourself from the I-D Announcement list, send a=20 > message to i-d-announce-request@ietf.org with the word=20 > unsubscribe in the body of the message.=20 > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. >=20 > Internet-Drafts are also available by anonymous FTP. Login=20 > with the username "anonymous" and a password of your e-mail=20 > address. After logging in, type "cd internet-drafts" and then=20 > "get draft-ietf-speermint-voip-consolidated-usecases-01.txt". >=20 > A list of Internet-Drafts directories can be found in=20 > http://www.ietf.org/shadow.html or=20 > ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE=20 > /internet-drafts/draft-ietf-speermint-voip-consolidated-usecas > es-01.txt". > =09 > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant=20 > mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. >=20 > Below is the data which will enable a MIME compliant mail=20 > reader implementation to automatically retrieve the ASCII=20 > version of the Internet-Draft. >=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Mon May 21 13:43:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqBuN-0006jS-MW; Mon, 21 May 2007 13:42:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqBuM-0006jL-QM for speermint@ietf.org; Mon, 21 May 2007 13:42:58 -0400 Received: from paoakoavas10.cable.comcast.com ([208.17.35.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqBuL-0005Kk-H0 for speermint@ietf.org; Mon, 21 May 2007 13:42:58 -0400 Received: from ([10.52.116.31]) by paoakoavas10.cable.comcast.com with ESMTP id KP-TDCH7.32939864; Mon, 21 May 2007 13:42:34 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 21 May 2007 13:42:34 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 21 May 2007 13:42:33 -0400 Message-ID: <45AEC6EF95942140888406588E1A660201A8A108@PACDCEXCMB04.cable.comcast.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [wg-business] WGLC for draft-ietf-speermint-consolidated-presence-im-usecases-01 Thread-Index: Acebz2lVIOAXLXIbTuCM59kog2h/xA== From: "Livingood, Jason" To: X-OriginalArrivalTime: 21 May 2007 17:42:34.0120 (UTC) FILETIME=[69EFB080:01C79BCF] X-Spam-Score: 1.1 (+) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Subject: [Speermint] [wg-business] WGLC for draft-ietf-speermint-consolidated-presence-im-usecases-01 X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Title : Presence & IM Use Cases Author(s) : A. Houri, et. al. Filename : draft-ietf-speermint-consolidated-presence-im-usecases-01.txt Pages : 12 Date : 9 May 2007 Abstract =20 The document describes several use cases of peering between two or more service providers that provide none VOIP based collaboration services and presence and IM in particular. These service providers create a peering relationship between themselves thus enabling their users to collaborate with users on other communities. The target of the document is to drive requirements for peering between domains that provide the none VOIP based collaboration services. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-consolidated-pr esence-im-usecases-01.txt The intent of the last call is to solicit comments before submitting the ID to the IESG. The purpose of a working group Last Call is in the style of "speak now or forever hold your peace" in case there are fundamental objections which have not gotten previous or adequate discussion, or minor errors which need correction. Work group last call will extend for 2 weeks from today, 21 May 2007, until at least 4 June 2007 (though we can modify that if new issues come up). Please post any comments in reply to the list, as well as to the editor(s) of this draft. Regards, Jason=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue May 22 05:13:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqQQO-0002m0-HB; Tue, 22 May 2007 05:13:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqQQN-0002ls-QN for speermint@ietf.org; Tue, 22 May 2007 05:12:59 -0400 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqQQM-0006jL-8C for speermint@ietf.org; Tue, 22 May 2007 05:12:59 -0400 Received: from [10.10.0.127] (nat.labs.nic.at [::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Tue, 22 May 2007 11:12:51 +0200 id 0006C00B.4652B414.00004530 Message-ID: <4652B3C9.9030405@enum.at> Date: Tue, 22 May 2007 11:11:37 +0200 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: speermint , Avshalom Houri , Edwin Aoki , Sriram Parameswar , speermint , "Livingood, Jason" , David Meyer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 1.1 (+) X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f Cc: Subject: [Speermint] NITS review (plus comments) of draft-speermint-consolidated-presence-im-usecases-01 X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Hi, I've done a NITS review of the consolidated IM/presence use case - i've also added some general comments about the draft - hope they help! idnits reports the following issues: --- idnits 2.04.07 /home/ietf/id/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt: Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748: ---------------------------------------------------------------------------- No issues found here. Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Too long document name: The document name (without revision number), 'draft-ietf-speermint-consolidated-presence-im-usecases', is 54 characters long, but may be at most 50 characters Checking nits according to http://www.ietf.org/ID-Checklist.html: ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of http://www.ietf.org/ID-Checklist.html for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- No issues found here. Summary: 2 errors (**), 1 warning (==), 0 comments (--). Run idnits with the --verbose option for more detailed information about the items above. ---- - I'm unsure how to best change the draft name, especially since my initial idea of "draft-speermint-presence-im-consolidated" does not make clear that this is a use cases document (might clash with future documents). I'd suggest the editors should consult with the chairs on this. - If RFC 2119 terminology is not to be used, please remove section 1 and the corresponding reference. - Please add an IANA considerations section, explaining that there are no such considerations since this document as a use case doc does not propose any protocols. - Document title: I think that "Presence & IM Use Cases" is way too generic in the context of the whole IETF. I'd suggest to a) expand "IM" and b) add the word "Peering", like "Presence & Instant Messaging Peering Use Cases". - Abstract: i think (warning - i'm not a native speaker!) that "non-VoIP" would be the desired term (most often, a lower case "o" is used, so i suggest sticking to that). - Introduction: i'd suggest changing "the management of the intercommunity link.." to "the management of such intercommunity links". Please expand the acronym "VoIP" here (at least once in the document, best on first use after the abstract). I also suggest changing "unless otherwise is stated" to "unless otherwise stated" (again, you might want to have that checked by a native-speaking reviewer). The last paragraph does not add much information, i suggest removing it. - 3.1 Simple Interdomain Subscription: small nit: From other documents i get the impression that language like "we have" is to be avoided in RFCs. I suggest rephrasing the first sentence. Generally, we should come to a conclusion whether all terminology from the terminology draft should be written like "Peer Network", to distinguish them from generic text. Jason? David? - 3.2 List Interdomain Subscription: Please expand URI (and make a informative reference) on first use. I'd use bullets for the two "sub-use-cases". I think that "SUBSCRIBE" is a request type, not a "session", although i know what that is intended to say. A reference to the respective draft about the SUBSCRIBE mechanisms would be good here. - 3.3 Authorization Migration: "presentities" is not defined - maybe add a reference to a definition. Same for "watchers". Also, a new term "peering network" is introduced - is that some generic term, or is it meant to be a "Peer Network". The last paragraph talks about "communities" again, and leaves it unclear whether a "community" translates 1:1 to a "Peer Network". Also, the last paragraph contains a lot of typos: "sharin", "informaiton", "associaed", "doucment", "otehr". I also suggest changing "users that should get it" to "users that should receive it". - 3.4 Page Mode IM: Please expand "SBE" on first use. - 3.5: Session Based IM: Please expand "MSRP". No need to refer to the definition of SBE again. - 3.6: "More or less fully standardized" is a very nice double oxymoron :) - I suggest rephrasing that (although i somehow like it). The second sentence of the last bullet ("Note that document sharing..") looks incomplete to me. I also think that the last paragraph should be rephrased, probably in a way that saying the list above is not exhaustive as new developments in the world of non-VoIP RTC surface. - 3.7: I'm not sure whether this section describes potential or existing use cases for peering. Some of the text gives general justification for the use case of IM peering - if that is the intended meaning of the text, it should probably be moved to the introduction section (or, even make a "Motivation for Peering" subscection?) - 4: Security Considerations: typo "there <-> they are". I think that the SEC reviewer will not be satisfied with the current text - if there are security considerations for those use cases (or related considerations, as privacy) they should at least be mentioned, even the document does not attempt to propose a solution. First thing that comes to my mind is trust relation between peers, esp. in the scenario described in section 3.3). As said above, please add an IANA section. Hope that helps, Alex _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue May 22 08:12:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqTDs-0006QQ-UT; Tue, 22 May 2007 08:12:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqTDr-0006O1-VD for speermint@ietf.org; Tue, 22 May 2007 08:12:15 -0400 Received: from mtagate2.de.ibm.com ([195.212.29.151]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqTDq-0008If-WB for speermint@ietf.org; Tue, 22 May 2007 08:12:15 -0400 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate2.de.ibm.com (8.13.8/8.13.8) with ESMTP id l4MCCCHS144098 for ; Tue, 22 May 2007 12:12:12 GMT Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l4MCCCUx3534942 for ; Tue, 22 May 2007 14:12:12 +0200 Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l4MCCBBY002234 for ; Tue, 22 May 2007 14:12:12 +0200 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l4MCCBp2002231; Tue, 22 May 2007 14:12:11 +0200 In-Reply-To: <4652B3C9.9030405@enum.at> To: Alexander Mayrhofer , "Livingood, Jason" MIME-Version: 1.0 Subject: Re: [Speermint] NITS review (plus comments) of draft-speermint-consolidated-presence-im-usecases-01 X-Mailer: Lotus Notes Release 7.0 August 18, 2005 From: Avshalom Houri Message-ID: Date: Tue, 22 May 2007 15:12:10 +0300 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 22/05/2007 15:12:10, Serialize complete at 22/05/2007 15:12:10 X-Spam-Score: 1.6 (+) X-Scan-Signature: 23336e92cd9b2f166f17126afcdd84ec Cc: speermint@ietf.org, Sriram Parameswar , Edwin Aoki X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0568338690==" Errors-To: speermint-bounces@ietf.org This is a multipart message in MIME format. --===============0568338690== Content-Type: multipart/alternative; boundary="=_alternative 00430618C22572E3_=" This is a multipart message in MIME format. --=_alternative 00430618C22572E3_= Content-Type: text/plain; charset="US-ASCII" Alexander & Jason, Many thanks for your review, intend to issue 02 in mid June. Anyone that has comments on the draft please send them asap. --Avshalom Alexander Mayrhofer 22/05/2007 12:11 To speermint , Avshalom Houri/Haifa/IBM@IBMIL, Edwin Aoki , Sriram Parameswar , speermint , "Livingood, Jason" , David Meyer cc Subject [Speermint] NITS review (plus comments) of draft-speermint-consolidated-presence-im-usecases-01 Hi, I've done a NITS review of the consolidated IM/presence use case - i've also added some general comments about the draft - hope they help! idnits reports the following issues: --- idnits 2.04.07 /home/ietf/id/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt: Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748: ---------------------------------------------------------------------------- No issues found here. Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Too long document name: The document name (without revision number), 'draft-ietf-speermint-consolidated-presence-im-usecases', is 54 characters long, but may be at most 50 characters Checking nits according to http://www.ietf.org/ID-Checklist.html: ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of http://www.ietf.org/ID-Checklist.html for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- No issues found here. Summary: 2 errors (**), 1 warning (==), 0 comments (--). Run idnits with the --verbose option for more detailed information about the items above. ---- - I'm unsure how to best change the draft name, especially since my initial idea of "draft-speermint-presence-im-consolidated" does not make clear that this is a use cases document (might clash with future documents). I'd suggest the editors should consult with the chairs on this. - If RFC 2119 terminology is not to be used, please remove section 1 and the corresponding reference. - Please add an IANA considerations section, explaining that there are no such considerations since this document as a use case doc does not propose any protocols. - Document title: I think that "Presence & IM Use Cases" is way too generic in the context of the whole IETF. I'd suggest to a) expand "IM" and b) add the word "Peering", like "Presence & Instant Messaging Peering Use Cases". - Abstract: i think (warning - i'm not a native speaker!) that "non-VoIP" would be the desired term (most often, a lower case "o" is used, so i suggest sticking to that). - Introduction: i'd suggest changing "the management of the intercommunity link.." to "the management of such intercommunity links". Please expand the acronym "VoIP" here (at least once in the document, best on first use after the abstract). I also suggest changing "unless otherwise is stated" to "unless otherwise stated" (again, you might want to have that checked by a native-speaking reviewer). The last paragraph does not add much information, i suggest removing it. - 3.1 Simple Interdomain Subscription: small nit: From other documents i get the impression that language like "we have" is to be avoided in RFCs. I suggest rephrasing the first sentence. Generally, we should come to a conclusion whether all terminology from the terminology draft should be written like "Peer Network", to distinguish them from generic text. Jason? David? - 3.2 List Interdomain Subscription: Please expand URI (and make a informative reference) on first use. I'd use bullets for the two "sub-use-cases". I think that "SUBSCRIBE" is a request type, not a "session", although i know what that is intended to say. A reference to the respective draft about the SUBSCRIBE mechanisms would be good here. - 3.3 Authorization Migration: "presentities" is not defined - maybe add a reference to a definition. Same for "watchers". Also, a new term "peering network" is introduced - is that some generic term, or is it meant to be a "Peer Network". The last paragraph talks about "communities" again, and leaves it unclear whether a "community" translates 1:1 to a "Peer Network". Also, the last paragraph contains a lot of typos: "sharin", "informaiton", "associaed", "doucment", "otehr". I also suggest changing "users that should get it" to "users that should receive it". - 3.4 Page Mode IM: Please expand "SBE" on first use. - 3.5: Session Based IM: Please expand "MSRP". No need to refer to the definition of SBE again. - 3.6: "More or less fully standardized" is a very nice double oxymoron :) - I suggest rephrasing that (although i somehow like it). The second sentence of the last bullet ("Note that document sharing..") looks incomplete to me. I also think that the last paragraph should be rephrased, probably in a way that saying the list above is not exhaustive as new developments in the world of non-VoIP RTC surface. - 3.7: I'm not sure whether this section describes potential or existing use cases for peering. Some of the text gives general justification for the use case of IM peering - if that is the intended meaning of the text, it should probably be moved to the introduction section (or, even make a "Motivation for Peering" subscection?) - 4: Security Considerations: typo "there <-> they are". I think that the SEC reviewer will not be satisfied with the current text - if there are security considerations for those use cases (or related considerations, as privacy) they should at least be mentioned, even the document does not attempt to propose a solution. First thing that comes to my mind is trust relation between peers, esp. in the scenario described in section 3.3). As said above, please add an IANA section. Hope that helps, Alex _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --=_alternative 00430618C22572E3_= Content-Type: text/html; charset="US-ASCII"
Alexander & Jason,

Many thanks for your review, intend to issue 02 in mid June.

Anyone that has comments on the draft please send them asap.

--Avshalom


Alexander Mayrhofer <alexander.mayrhofer@enum.at>

22/05/2007 12:11

To
speermint <speermint@ietf.org>, Avshalom Houri/Haifa/IBM@IBMIL, Edwin Aoki <aoki@aol.net>, Sriram Parameswar <Sriram.Parameswar@microsoft.com>, speermint <speermint@ietf.org>, "Livingood, Jason" <Jason_Livingood@cable.comcast.com>, David Meyer <dmm@1-4-5.net>
cc
Subject
[Speermint] NITS review (plus comments) of        draft-speermint-consolidated-presence-im-usecases-01






Hi,

I've done a NITS review of the consolidated IM/presence use case - i've also
added some general comments about the draft - hope they help!

idnits reports the following issues:

---
idnits 2.04.07

/home/ietf/id/draft-ietf-speermint-consolidated-presence-im-usecases-01.txt:

 Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748:
 ----------------------------------------------------------------------------

    No issues found here.

 Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
 ----------------------------------------------------------------------------

 ** Too long document name: The document name (without revision number),
    'draft-ietf-speermint-consolidated-presence-im-usecases', is 54
    characters long, but may be at most 50 characters


 Checking nits according to http://www.ietf.org/ID-Checklist.html:
 ----------------------------------------------------------------------------

 ** The document seems to lack an IANA Considerations section.  (See Section
    2.2 of http://www.ietf.org/ID-Checklist.html for how to handle the case
    when there are no actions for IANA.)


 Miscellaneous warnings:
 ----------------------------------------------------------------------------

 == The document doesn't use any RFC 2119 keywords, yet seems to have RFC
    2119 boilerplate text.


 Checking references for intended status: Proposed Standard
 ----------------------------------------------------------------------------

    No issues found here.

    Summary: 2 errors (**), 1 warning (==), 0 comments (--).

    Run idnits with the --verbose option for more detailed information about
    the items above.
----

- I'm unsure how to best change the draft name, especially since my initial
idea of "draft-speermint-presence-im-consolidated" does not make clear that
this is a use cases document (might clash with future documents). I'd
suggest the editors should consult with the chairs on this.

- If RFC 2119 terminology is not to be used, please remove section 1 and the
corresponding reference.

- Please add an IANA considerations section, explaining that there are no
such considerations since this document as a use case doc does not propose
any protocols.

- Document title: I think that "Presence & IM Use Cases" is way too generic
in the context of the whole IETF. I'd suggest to a) expand "IM" and b) add
the word "Peering", like "Presence & Instant Messaging Peering Use Cases".

- Abstract: i think (warning - i'm not a native speaker!) that "non-VoIP"
would be the desired term (most often, a lower case "o" is used, so i
suggest sticking to that).

- Introduction: i'd suggest changing "the management of the intercommunity
link.." to "the management of such intercommunity links". Please expand the
acronym "VoIP" here (at least once in the document, best on first use after
the abstract). I also suggest changing "unless otherwise is stated" to
"unless otherwise stated" (again, you might want to have that checked by a
native-speaking reviewer). The last paragraph does not add much information,
i suggest removing it.

- 3.1 Simple Interdomain Subscription: small nit: From other documents i get
the impression that language like "we have" is to be avoided in RFCs. I
suggest rephrasing the first sentence. Generally, we should come to a
conclusion whether all terminology from the terminology draft should be
written like "Peer Network", to distinguish them from generic text. Jason?
David?

- 3.2 List Interdomain Subscription: Please expand URI (and make a
informative reference) on first use. I'd use bullets for the two
"sub-use-cases". I think that "SUBSCRIBE" is a request type, not a
"session", although i know what that is intended to say. A reference to the
respective draft about the SUBSCRIBE mechanisms would be good here.

- 3.3 Authorization Migration: "presentities" is not defined - maybe add a
reference to a definition. Same for "watchers". Also, a new term "peering
network" is introduced - is that some generic term, or is it meant to be a
"Peer Network". The last paragraph talks about "communities" again, and
leaves it unclear whether a "community" translates 1:1 to a "Peer Network".
Also, the last paragraph contains a lot of typos: "sharin", "informaiton",
"associaed", "doucment", "otehr". I also suggest changing "users that should
get it" to "users that should receive it".

- 3.4 Page Mode IM: Please expand "SBE" on first use.

- 3.5: Session Based IM: Please expand "MSRP". No need to refer to the
definition of SBE again.

- 3.6: "More or less fully standardized" is a very nice double oxymoron :) -
I suggest rephrasing that (although i somehow like it). The second sentence
of the last bullet ("Note that document sharing..") looks incomplete to me.
I also think that the last paragraph should be rephrased, probably in a way
that saying the list above is not exhaustive as new developments in the
world of non-VoIP RTC surface.

- 3.7: I'm not sure whether this section describes potential or existing use
cases for peering. Some of the text gives general justification for the use
case of IM peering - if that is the intended meaning of the text, it should
probably be moved to the introduction section (or, even make a "Motivation
for Peering" subscection?)

- 4: Security Considerations: typo "there <-> they are". I think that the
SEC reviewer will not be satisfied with the current text - if there are
security considerations for those use cases (or related considerations, as
privacy) they should at least be mentioned, even the document does not
attempt to propose a solution. First thing that comes to my mind is trust
relation between peers, esp. in the scenario described in section 3.3).

As said above, please add an IANA section.

Hope that helps,

Alex


_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint
--=_alternative 00430618C22572E3_=-- --===============0568338690== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --===============0568338690==-- From speermint-bounces@ietf.org Tue May 22 09:17:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqUEw-00078q-1N; Tue, 22 May 2007 09:17:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqUEu-00078Y-Mn for speermint@ietf.org; Tue, 22 May 2007 09:17:24 -0400 Received: from paoakoavas09.cable.comcast.com ([208.17.35.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqUEu-0002iW-9T for speermint@ietf.org; Tue, 22 May 2007 09:17:24 -0400 Received: from ([10.52.116.31]) by paoakoavas09.cable.comcast.com with ESMTP id KP-NTF18.43052885; Tue, 22 May 2007 09:16:56 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 May 2007 09:16:56 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 22 May 2007 09:16:55 -0400 Message-ID: <45AEC6EF95942140888406588E1A660201A8A2C6@PACDCEXCMB04.cable.comcast.com> In-Reply-To: <4652B3C9.9030405@enum.at> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NITS review (plus comments) of draft-speermint-consolidated-presence-im-usecases-01 Thread-Index: AcecUW62esPsxTVoRHuxmNcRH4zIJwAIVlcg References: <4652B3C9.9030405@enum.at> From: "Livingood, Jason" To: "Alexander Mayrhofer" , "Avshalom Houri" , "Edwin Aoki" , "Sriram Parameswar" , "David Meyer" , X-OriginalArrivalTime: 22 May 2007 13:16:56.0956 (UTC) FILETIME=[790F33C0:01C79C73] X-Spam-Score: 1.1 (+) X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e Cc: Subject: [Speermint] RE: NITS review (plus comments) of draft-speermint-consolidated-presence-im-usecases-01 X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Great review Alex - thanks! My suggestion on naming: filename =3D draft-ietf-speermint-presence-im-usecases=20 title =3D Presence & Instant Messaging Peering Use Cases Regards Jason > -----Original Message----- > From: Alexander Mayrhofer [mailto:alexander.mayrhofer@enum.at]=20 > Sent: Tuesday, May 22, 2007 5:12 AM > To: speermint; Avshalom Houri; Edwin Aoki; Sriram Parameswar;=20 > speermint; Livingood, Jason; David Meyer > Subject: NITS review (plus comments) of=20 > draft-speermint-consolidated-presence-im-usecases-01 >=20 >=20 > Hi, >=20 > I've done a NITS review of the consolidated IM/presence use=20 > case - i've also added some general comments about the draft=20 > - hope they help! >=20 > idnits reports the following issues: >=20 > --- > idnits 2.04.07 >=20 > /home/ietf/id/draft-ietf-speermint-consolidated-presence-im-us ecases-01.txt: >=20 > Checking boilerplate required by RFC 3978 and 3979, updated=20 > by RFC 4748: > =20 > -------------------------------------------------------------- > -------------- >=20 > No issues found here. >=20 > Checking nits according to=20 > http://www.ietf.org/ietf/1id-guidelines.txt: > =20 > -------------------------------------------------------------- > -------------- >=20 > ** Too long document name: The document name (without=20 > revision number), > 'draft-ietf-speermint-consolidated-presence-im-usecases', is 54 > characters long, but may be at most 50 characters >=20 >=20 > Checking nits according to http://www.ietf.org/ID-Checklist.html: > =20 > -------------------------------------------------------------- > -------------- >=20 > ** The document seems to lack an IANA Considerations=20 > section. (See Section > 2.2 of http://www.ietf.org/ID-Checklist.html for how to=20 > handle the case > when there are no actions for IANA.) >=20 >=20 > Miscellaneous warnings: > =20 > -------------------------------------------------------------- > -------------- >=20 > =3D=3D The document doesn't use any RFC 2119 keywords, yet=20 > seems to have RFC > 2119 boilerplate text. >=20 >=20 > Checking references for intended status: Proposed Standard > =20 > -------------------------------------------------------------- > -------------- >=20 > No issues found here. >=20 > Summary: 2 errors (**), 1 warning (=3D=3D), 0 comments (--). >=20 > Run idnits with the --verbose option for more detailed=20 > information about > the items above. > ---- >=20 > - I'm unsure how to best change the draft name, especially=20 > since my initial idea of=20 > "draft-speermint-presence-im-consolidated" does not make=20 > clear that this is a use cases document (might clash with=20 > future documents). I'd suggest the editors should consult=20 > with the chairs on this. >=20 > - If RFC 2119 terminology is not to be used, please remove=20 > section 1 and the corresponding reference. >=20 > - Please add an IANA considerations section, explaining that=20 > there are no such considerations since this document as a use=20 > case doc does not propose any protocols. >=20 > - Document title: I think that "Presence & IM Use Cases" is=20 > way too generic in the context of the whole IETF. I'd suggest=20 > to a) expand "IM" and b) add the word "Peering", like=20 > "Presence & Instant Messaging Peering Use Cases". >=20 > - Abstract: i think (warning - i'm not a native speaker!)=20 > that "non-VoIP" > would be the desired term (most often, a lower case "o" is=20 > used, so i suggest sticking to that). >=20 > - Introduction: i'd suggest changing "the management of the=20 > intercommunity link.." to "the management of such=20 > intercommunity links". Please expand the acronym "VoIP" here=20 > (at least once in the document, best on first use after the=20 > abstract). I also suggest changing "unless otherwise is=20 > stated" to "unless otherwise stated" (again, you might want=20 > to have that checked by a native-speaking reviewer). The last=20 > paragraph does not add much information, i suggest removing it. >=20 > - 3.1 Simple Interdomain Subscription: small nit: From other=20 > documents i get the impression that language like "we have"=20 > is to be avoided in RFCs. I suggest rephrasing the first=20 > sentence. Generally, we should come to a conclusion whether=20 > all terminology from the terminology draft should be written=20 > like "Peer Network", to distinguish them from generic text. Jason? > David? >=20 > - 3.2 List Interdomain Subscription: Please expand URI (and=20 > make a informative reference) on first use. I'd use bullets=20 > for the two "sub-use-cases". I think that "SUBSCRIBE" is a=20 > request type, not a "session", although i know what that is=20 > intended to say. A reference to the respective draft about=20 > the SUBSCRIBE mechanisms would be good here. >=20 > - 3.3 Authorization Migration: "presentities" is not defined=20 > - maybe add a reference to a definition. Same for "watchers".=20 > Also, a new term "peering network" is introduced - is that=20 > some generic term, or is it meant to be a "Peer Network". The=20 > last paragraph talks about "communities" again, and leaves it=20 > unclear whether a "community" translates 1:1 to a "Peer Network". > Also, the last paragraph contains a lot of typos: "sharin",=20 > "informaiton", "associaed", "doucment", "otehr". I also=20 > suggest changing "users that should get it" to "users that=20 > should receive it". >=20 > - 3.4 Page Mode IM: Please expand "SBE" on first use. >=20 > - 3.5: Session Based IM: Please expand "MSRP". No need to=20 > refer to the definition of SBE again. >=20 > - 3.6: "More or less fully standardized" is a very nice=20 > double oxymoron :) - I suggest rephrasing that (although i=20 > somehow like it). The second sentence of the last bullet=20 > ("Note that document sharing..") looks incomplete to me. > I also think that the last paragraph should be rephrased,=20 > probably in a way that saying the list above is not=20 > exhaustive as new developments in the world of non-VoIP RTC surface. >=20 > - 3.7: I'm not sure whether this section describes potential=20 > or existing use cases for peering. Some of the text gives=20 > general justification for the use case of IM peering - if=20 > that is the intended meaning of the text, it should probably=20 > be moved to the introduction section (or, even make a=20 > "Motivation for Peering" subscection?) >=20 > - 4: Security Considerations: typo "there <-> they are". I=20 > think that the SEC reviewer will not be satisfied with the=20 > current text - if there are security considerations for those=20 > use cases (or related considerations, as > privacy) they should at least be mentioned, even the document=20 > does not attempt to propose a solution. First thing that=20 > comes to my mind is trust relation between peers, esp. in the=20 > scenario described in section 3.3). >=20 > As said above, please add an IANA section. >=20 > Hope that helps, >=20 > Alex >=20 >=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Thu May 24 09:59:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HrDr7-0005To-Cm; Thu, 24 May 2007 09:59:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HrDr5-0005Tj-Tv for speermint@ietf.org; Thu, 24 May 2007 09:59:51 -0400 Received: from pacdcimo01.cable.comcast.com ([24.40.8.145]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrDr4-00006p-L4 for speermint@ietf.org; Thu, 24 May 2007 09:59:51 -0400 Received: from ([10.52.116.31]) by pacdcimo01.cable.comcast.com with ESMTP id KP-BXT38.3899218; Thu, 24 May 2007 09:59:34 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 24 May 2007 09:59:34 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 24 May 2007 09:59:33 -0400 Message-ID: <45AEC6EF95942140888406588E1A660201A8A9F0@PACDCEXCMB04.cable.comcast.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [wg-business] 69th IETF - DRAFT Meeting Agenda for Review Thread-Index: AcedUyAHhTdmad+hTzSr2W8XvcQ3ZQAuGnjQ From: "Livingood, Jason" To: X-OriginalArrivalTime: 24 May 2007 13:59:34.0180 (UTC) FILETIME=[C21C1E40:01C79E0B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Subject: [Speermint] [wg-business] 69th IETF - DRAFT Meeting Agenda for Review X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org A draft IETF-69 agenda is up. Looks like we are *tentatively* schedules for Monday, 23 July, at 1300 hours. Jason -----Original Message----- From: IETF Agenda [mailto:agenda@ietf.org]=20 Sent: Wednesday, May 23, 2007 11:56 AM To: wgchairs@ietf.org; bofchairs@ietf.org; irsg@isi.edu; iesg@ietf.org Subject: 69th IETF - DRAFT Meeting Agenda for Review=20 Dear ALL: =20 The DRAFT agenda for the 69th IETF Meeting can be found at: https://datatracker.ietf.org/public/meeting_agenda_html.cgi?meeting_num=3D= 69. Please note that the agenda is in draft form and is subject to change. =20 We would like to ask you to review the Draft Agenda and send your comments to agenda@ietf.org. We shall be working on your comments until the Final Agenda is published which is on Monday, July 2nd) (Important Meeting Dates can be found at http://www.ietf.org/meetings/69-IETF.html). =20 We would really appreciate your inputs or suggestions on the draft agenda and shall try to accommodate your priorities if possible. =20 IETF Secretariat =20 +++ The milestones and deadlines for scheduling-related activities are as follows: =20 -- Cut-off date for requesting a Working Group session and for preliminary BOF proposals to ADs: Monday, May 21 at 17:00 ET (21:00 UTC/GMT). -- Cut-off date for requests to schedule BoFs: Monday, June 11 at 17:00 ET (21:00 UTC/GMT). -- Preliminary agenda published for comment: Friday, June 15 by midnight ET. -- Cut-off date for requests to reschedule a session: Wednesday, June 27 at 09:00 ET (13:00 UTC/GMT). -- Final agenda published: Monday, July 2 before midnight ET. -- Draft Working Group agendas due: Wednesday, July 11 at 17:00 ET (21:00 UTC/GMT). -- Revised Working Group agendas due: Monday, July 16 at 12:00 ET (16:00 UTC/GMT), upload using IETF Meeting Materials Management Tool _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Fri May 25 02:23:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HrTDC-000151-F7; Fri, 25 May 2007 02:23:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HrTDB-00014v-Om for speermint@ietf.org; Fri, 25 May 2007 02:23:41 -0400 Received: from mailgate.siemenscomms.co.uk ([195.171.110.225] helo=bemg01.siemenscomms.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrTDB-0005W7-5G for speermint@ietf.org; Fri, 25 May 2007 02:23:41 -0400 Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.0-24 #40642) with ESMTP id <0JIL00EBL336C0@siemenscomms.co.uk> for speermint@ietf.org; Fri, 25 May 2007 07:23:30 +0100 (BST) Date: Fri, 25 May 2007 07:23:39 +0100 From: "Elwell, John" Subject: RE: [Speermint] I-DACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt In-reply-to: A <45AEC6EF95942140888406588E1A660201A2987F@PACDCEXCMB04.cable.comcast.com> To: speermint@ietf.org, "Uzelac, Adam" Message-id: <0D5F89FAC29E2C41B98A6A762007F5D012F1BD@GBNTHT12009MSX.gb002.siemens.net> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-Topic: [Speermint] I-DACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt Thread-Index: AceXQ5LoKh6mOINvSpGrq35soxK40gBjgkkgAUT+LVA= Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: References: A <45AEC6EF95942140888406588E1A660201A2987F@PACDCEXCMB04.cable.comcast.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d Cc: "Livingood, Jason" X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Adam, I have reviewed this draft and I think it needs a lot more work to use consistent and well-defined terms and to make the distinction between indirect and assisted use cases more clear. When I read the previous version I thought I understood it, but now reading the present version more carefully I find I really don't understand it. Specific comments: 1. In section 2 (terminology) there is a reference to 06 of the terminology draft, followed by figure 1. Figure 1 uses many terms not defined in the terminology draft and there is no further explanation of these terms in section 2. Furthermore there is no explanation of how to interpret figure 1. Relevant information occurs later, but as it stands the document cannot be read in sequence. 2. There is also inconsistent terminology elsewhere, e.g., figure 2 shows LS-O, which in the accompanying text seems to be referred to as routing database. As another example, the text accompanying figure 3 mentions a proxy, which is not shown in figure 3. In 3.1.2.1 it mentions "The SBEs", yet the figure shows only a single SBE. 3. In section 3, terms like O-VSP, A-VSP and T-VSP are not defined. 4. In 3.1.3.1 it states "The direct peering use case with 2 SBEs is typically seen where both the originating and terminating domain are SPs." It can also occur where one or both domains are enterprises, although of course the other direct cases are also possible here. 5. Section 3.2.1 on indirect peering uses the terms A-SBE and A-DBE without definition. Section 3 uses the term A-VSP, but that is in the context of assisted peering, not indirect peering. Also the terms "Assisted PSP" and "Assisted domain" are used but not defined (here or in the terminology document). Firstly, the word "assisted" is confusing because it seems that it should be "assisting" rather than "assisted". Secondly the word seems more appropriate to assisted peering than to indirect peering. 6. In fact the definitions of indirect peering and assisted peering in the terminology draft are insufficient to make a clear distinction between the two. If signalling is routed securely from domain A to domain B via a proxy in a third domain, this would seem to fit both indirect peering and assisted peering, as defined in the terminology draft. Likewise I think it fits both indirect peering and assisted peering as described in section 3 of the consolidated uses cases draft. 7. Furthermore there doesn't seem to be a real distinction between figure 5 (indirect) and figure 6 (assisted). Both employ an LS-a, an A-SBE and an A-DBE. 8. The abbreviation "T" seems sometimes to be used for "Terminating" and sometimes for "Transit". 9. I think the terms "indirect" and "transit" are used interchangeably at times. If so, please use just a single term - if not, clarify the difference. 10. The indirect use case does not show egress SBEs in the originating and transit domains. Presumably this is a possibility. It is not feasible to show all permutations in figures, but at least there should be some mention in text of the possibility. However, see also the next comment, which may remove the need. 11. In general, trying to show the internal composition of a domain is not helpful. Issues of internal organisation (i.e., whether or not there is an egress SBE and/or ingress SBE) seem to cloud the real behaviour of domains, and in particular gets in the way of understanding the real differences between the 3 use cases (in particular, indirect and assisted). I would much prefer to see each domain treated as a black box. 12. I was asked to check whether this covered enterprise use cases identified in draft-elwell-speermint-enterprise-usecases-00. In as far as it goes, I guess it does in theory cover the use cases part, although not always explicitly. In particular there is no provision for two transit domains in series, e.g., enterprise 1 - carrier 1 - carrier 2 - enterprise 2. Note that the enterprise-usecases draft goes beyond use cases and discusses some technical issues too, and these are not covered in your draft (and indeed probably should not be covered in your draft). I look forward to the 02 version before Chicago. John > -----Original Message----- > From: Livingood, Jason [mailto:Jason_Livingood@cable.comcast.com] > Sent: 18 May 2007 04:39 > To: speermint@ietf.org > Subject: RE: [Speermint] > I-DACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt > > As with the IM document, please get comments to the editor asap so we > can come to Chicago with a -02 if necessary. > > Thanks > Jason > > > -----Original Message----- > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > > Sent: Tuesday, May 15, 2007 6:50 PM > > To: i-d-announce@ietf.org > > Cc: speermint@ietf.org > > Subject: [Speermint] I-D > > ACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt > > > > A New Internet-Draft is available from the on-line > > Internet-Drafts directories. > > This draft is a work item of the Session PEERing for > > Multimedia INTerconnect Working Group of the IETF. > > > > Title : VoIP SIP Peering Use Cases > > Author(s) : A. Uzelac, et al. > > Filename : > > draft-ietf-speermint-voip-consolidated-usecases-01.txt > > Pages : 20 > > Date : 2007-5-15 > > > > This document will capture the VoIP use case for SIP > Peering. It is > > a consolidation of other Speermint use cases and will focus > > exclusively on VoIP. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip- > > consolidated-usecases-01.txt > > > > To remove yourself from the I-D Announcement list, send a > > message to i-d-announce-request@ietf.org with the word > > unsubscribe in the body of the message. > > You can also visit > https://www1.ietf.org/mailman/listinfo/I-D-announce > > to change your subscription settings. > > > > Internet-Drafts are also available by anonymous FTP. Login > > with the username "anonymous" and a password of your e-mail > > address. After logging in, type "cd internet-drafts" and then > > "get draft-ietf-speermint-voip-consolidated-usecases-01.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html or > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE > > /internet-drafts/draft-ietf-speermint-voip-consolidated-usecas > > es-01.txt". > > > > NOTE: The mail server at ietf.org can return the document in > > MIME-encoded form by using the "mpack" utility. To use this > > feature, insert the command "ENCODING mime" before the "FILE" > > command. To decode the response(s), you will need "munpack" or > > a MIME-compliant mail reader. Different MIME-compliant > > mail readers > > exhibit different behavior, especially when dealing with > > "multipart" MIME messages (i.e. documents which have been split > > up into multiple messages), so check your local documentation on > > how to manipulate these messages. > > > > Below is the data which will enable a MIME compliant mail > > reader implementation to automatically retrieve the ASCII > > version of the Internet-Draft. > > > > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint > _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Fri May 25 11:57:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HrcAJ-0001hx-15; Fri, 25 May 2007 11:57:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HrcAH-0001hs-SO for speermint@ietf.org; Fri, 25 May 2007 11:57:17 -0400 Received: from unknown-230-det.globalcrossing.com ([64.208.159.230] helo=mailsrv.ams.gblxint.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrcA9-0003p7-7F for speermint@ietf.org; Fri, 25 May 2007 11:57:17 -0400 Received: from w3uspdy20.ams.gblxint.com (w3uspdy20.ams.gblxint.com [10.60.51.55]) by mailsrv.ams.gblxint.com (Postfix) with ESMTP id DEFA29652; Fri, 25 May 2007 11:57:08 -0400 (EDT) Received: from EVS2.ams.gblxint.com ([10.60.51.59]) by w3uspdy20.ams.gblxint.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 May 2007 11:57:08 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speermint] I-DACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt Date: Fri, 25 May 2007 11:57:07 -0400 Message-ID: In-reply-to: <0D5F89FAC29E2C41B98A6A762007F5D012F1BD@GBNTHT12009MSX.gb002.siemens.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] I-DACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt Thread-Index: AceXQ5LoKh6mOINvSpGrq35soxK40gBjgkkgAUT+LVAAP7QhQA== References: A <45AEC6EF95942140888406588E1A660201A2987F@PACDCEXCMB04.cable.comcast.com> <0D5F89FAC29E2C41B98A6A762007F5D012F1BD@GBNTHT12009MSX.gb002.siemens.net> From: "Uzelac, Adam" To: "Elwell, John" , X-OriginalArrivalTime: 25 May 2007 15:57:08.0621 (UTC) FILETIME=[594C23D0:01C79EE5] X-Spam-Score: 0.1 (/) X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96 Cc: "Livingood, Jason" X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Thank you for the feedback John. Expect a vastly re-worked version of this draft soon. We (the multiple authors) have an avalanche of feedback to filter through and incorporate. Some points below to pertaining to your feedback... In Prague - there were some folks that took exception to the definitions providing distinction between indirect and assisted use cases. With feedback from you and others, I believe we can clear up the ambiguity. =20 Also, due to a suggestion from the Prague meeting - the vast terminology section I originally has been moved to the terminology draft. The issue at hand is that a new version of the term draft with those additions has not been released yet. Adam Uzelac Director Converged Arch. Global Crossing 585-255-8916 > -----Original Message----- > From: Elwell, John [mailto:john.elwell@siemens.com]=20 > Sent: Friday, May 25, 2007 2:24 AM > To: speermint@ietf.org; Uzelac, Adam > Cc: Livingood, Jason; Rodrig, Benny (Benny) > Subject: RE: [Speermint]=20 > I-DACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt >=20 > Adam, >=20 > I have reviewed this draft and I think it needs a lot more=20 > work to use consistent and well-defined terms and to make the=20 > distinction between indirect and assisted use cases more=20 > clear. When I read the previous version I thought I=20 > understood it, but now reading the present version more=20 > carefully I find I really don't understand it. Specific comments: >=20 > 1. In section 2 (terminology) there is a reference to 06 of=20 > the terminology draft, followed by figure 1. Figure 1 uses=20 > many terms not defined in the terminology draft and there is=20 > no further explanation of these terms in section 2.=20 > Furthermore there is no explanation of how to interpret=20 > figure 1. Relevant information occurs later, but as it stands=20 > the document cannot be read in sequence. >=20 > 2. There is also inconsistent terminology elsewhere, e.g.,=20 > figure 2 shows LS-O, which in the accompanying text seems to=20 > be referred to as routing database. As another example, the=20 > text accompanying figure 3 mentions a proxy, which is not=20 > shown in figure 3. In 3.1.2.1 it mentions "The SBEs", yet the=20 > figure shows only a single SBE. >=20 > 3. In section 3, terms like O-VSP, A-VSP and T-VSP are not defined. >=20 > 4. In 3.1.3.1 it states "The direct peering use case with 2=20 > SBEs is typically seen where both the originating and=20 > terminating domain are SPs." It can also occur where one or=20 > both domains are enterprises, although of course the other=20 > direct cases are also possible here. >=20 > 5. Section 3.2.1 on indirect peering uses the terms A-SBE and=20 > A-DBE without definition. Section 3 uses the term A-VSP, but=20 > that is in the context of assisted peering, not indirect=20 > peering. Also the terms "Assisted PSP" and "Assisted domain"=20 > are used but not defined (here or in the terminology=20 > document). Firstly, the word "assisted" is confusing because=20 > it seems that it should be "assisting" rather than "assisted". > Secondly the word seems more appropriate to assisted peering=20 > than to indirect peering. >=20 > 6. In fact the definitions of indirect peering and assisted=20 > peering in the terminology draft are insufficient to make a=20 > clear distinction between the two. If signalling is routed=20 > securely from domain A to domain B via a proxy in a third=20 > domain, this would seem to fit both indirect peering and=20 > assisted peering, as defined in the terminology draft.=20 > Likewise I think it fits both indirect peering and assisted=20 > peering as described in section 3 of the consolidated uses=20 > cases draft. >=20 > 7. Furthermore there doesn't seem to be a real distinction=20 > between figure 5 (indirect) and figure 6 (assisted). Both=20 > employ an LS-a, an A-SBE and an A-DBE. >=20 > 8. The abbreviation "T" seems sometimes to be used for=20 > "Terminating" and sometimes for "Transit". >=20 > 9. I think the terms "indirect" and "transit" are used=20 > interchangeably at times. If so, please use just a single=20 > term - if not, clarify the difference. >=20 > 10. The indirect use case does not show egress SBEs in the=20 > originating and transit domains. Presumably this is a=20 > possibility. It is not feasible to show all permutations in=20 > figures, but at least there should be some mention in text of=20 > the possibility. However, see also the next comment, which=20 > may remove the need. >=20 > 11. In general, trying to show the internal composition of a=20 > domain is not helpful. Issues of internal organisation (i.e.,=20 > whether or not there is an egress SBE and/or ingress SBE)=20 > seem to cloud the real behaviour of domains, and in=20 > particular gets in the way of understanding the real=20 > differences between the 3 use cases (in particular, indirect=20 > and assisted). I would much prefer to see each domain treated=20 > as a black box. >=20 > 12. I was asked to check whether this covered enterprise use=20 > cases identified in=20 > draft-elwell-speermint-enterprise-usecases-00. In as far as=20 > it goes, I guess it does in theory cover the use cases part,=20 > although not always explicitly. In particular there is no=20 > provision for two transit domains in series, e.g., enterprise=20 > 1 - carrier 1 - carrier 2 - enterprise 2. Note that the=20 > enterprise-usecases draft goes beyond use cases and discusses=20 > some technical issues too, and these are not covered in your=20 > draft (and indeed probably should not be covered in your draft). >=20 > I look forward to the 02 version before Chicago. >=20 > John >=20 >=20 > > -----Original Message----- > > From: Livingood, Jason [mailto:Jason_Livingood@cable.comcast.com] > > Sent: 18 May 2007 04:39 > > To: speermint@ietf.org > > Subject: RE: [Speermint] > > I-DACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt > >=20 > > As with the IM document, please get comments to the editor=20 > asap so we=20 > > can come to Chicago with a -02 if necessary. > >=20 > > Thanks > > Jason > >=20 > > > -----Original Message----- > > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > > > Sent: Tuesday, May 15, 2007 6:50 PM > > > To: i-d-announce@ietf.org > > > Cc: speermint@ietf.org > > > Subject: [Speermint] I-D > > > ACTION:draft-ietf-speermint-voip-consolidated-usecases-01.txt > > >=20 > > > A New Internet-Draft is available from the on-line=20 > Internet-Drafts=20 > > > directories. > > > This draft is a work item of the Session PEERing for Multimedia=20 > > > INTerconnect Working Group of the IETF. > > >=20 > > > Title : VoIP SIP Peering Use Cases > > > Author(s) : A. Uzelac, et al. > > > Filename :=20 > > > draft-ietf-speermint-voip-consolidated-usecases-01.txt > > > Pages : 20 > > > Date : 2007-5-15 > > > =09 > > > This document will capture the VoIP use case for SIP > > Peering. It is > > > a consolidation of other Speermint use cases and=20 > will focus=20 > > > exclusively on VoIP. > > >=20 > > > A URL for this Internet-Draft is: > > > http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip- > > > consolidated-usecases-01.txt > > >=20 > > > To remove yourself from the I-D Announcement list, send a=20 > message to=20 > > > i-d-announce-request@ietf.org with the word unsubscribe=20 > in the body=20 > > > of the message. > > > You can also visit > > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > to change your subscription settings. > > >=20 > > > Internet-Drafts are also available by anonymous FTP.=20 > Login with the=20 > > > username "anonymous" and a password of your e-mail address. After=20 > > > logging in, type "cd internet-drafts" and then "get=20 > > > draft-ietf-speermint-voip-consolidated-usecases-01.txt". > > >=20 > > > A list of Internet-Drafts directories can be found in=20 > > > http://www.ietf.org/shadow.html or=20 > > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > >=20 > > > Internet-Drafts can also be obtained by e-mail. > > >=20 > > > Send a message to: > > > mailserv@ietf.org. > > > In the body type: > > > "FILE > > > /internet-drafts/draft-ietf-speermint-voip-consolidated-usecas > > > es-01.txt". > > > =09 > > > NOTE: The mail server at ietf.org can return the document in > > > MIME-encoded form by using the "mpack" utility. To use this > > > feature, insert the command "ENCODING mime" before the "FILE" > > > command. To decode the response(s), you will need "munpack" or > > > a MIME-compliant mail reader. Different MIME-compliant mail=20 > > > readers > > > exhibit different behavior, especially when dealing with > > > "multipart" MIME messages (i.e. documents which have been split > > > up into multiple messages), so check your local documentation on > > > how to manipulate these messages. > > >=20 > > > Below is the data which will enable a MIME compliant mail reader=20 > > > implementation to automatically retrieve the ASCII version of the=20 > > > Internet-Draft. > > >=20 > >=20 > > _______________________________________________ > > Speermint mailing list > > Speermint@ietf.org > > https://www1.ietf.org/mailman/listinfo/speermint > >=20 >=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint