From isms-bounces@lists.ietf.org Tue Aug 01 09:50:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7udQ-0005MW-Sd; Tue, 01 Aug 2006 09:50:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G649K-0002a5-0A for isms@ietf.org; Thu, 27 Jul 2006 07:35:30 -0400 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G649I-0002Kp-Fq for isms@ietf.org; Thu, 27 Jul 2006 07:35:29 -0400 Received: from [10.1.1.104] (mito.netlab.nec.de [195.37.70.39]) by kyoto.netlab.nec.de (Postfix) with ESMTP id EE2AB1BAC4D; Thu, 27 Jul 2006 13:19:20 +0200 (CEST) Date: Thu, 27 Jul 2006 13:35:24 +0200 From: Juergen Quittek To: isms@ietf.org Subject: Re: [Isms] Conference call on notifications and call home Message-ID: In-Reply-To: References: X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 X-Mailman-Approved-At: Tue, 01 Aug 2006 09:50:11 -0400 Cc: 'Sam Hartman' , Avi Lior , Jeffrey Hutzelman X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org Dear all, Below please find the access parameters for the conference call. I apologize for the late announcement. My original call reservation failed for strange reasons. I had to take another provider that unfortunately only offers a German dial-in number: Tel.: +49 69 2711 0800 code: 32784# The first greeting is in German (sorry) but followed by an English one. We have made good experiences with participation via Skype Out. I have already started negotiating a contract with another conference bridge provider. Follow-up conference calls will most probably be more convenient. Thanks, Juergen Q. --On 25.07.2006 14:26 Uhr +0200 Juergen Quittek wrote: > Dear all, > > At our session in Montreal, we stopped the discussion on > agent initiated channels for notifications and on what we > call "call home" and agreed to continue it in a conference > call. > > Juergen S. and I tried to find a good time for this call, > but it is already summer and many people are having their > vacation soon. > > Based on advice from our area director we chose to make this > an open conference call where every WG member can participate. > > The time we suggest is > > Thursday, July 27, 10am EST (DST) > > I apologize for the late announcement and for potential > inconveniences for participants form the west coast. > We checked in advance at which time at least some of the > main contributors of the discussion in Montreal would be > available, and it looks like either take this date or we > have to delay the discussion for at least three weeks until > people return from vacations. > > > Subject of the phone conference will be a rather technical > discussion that (hopefully) brings us in a position that we > can decide soon on how to deliver notifications with ISMS. > The results of the discussion will be brought to the mailing > list where I hoe that we can close this issue soon after > the conference call. > > Please find a suggestion for the agenda below. > > The access parameters will be announced soon. We are currently > looking for an operator that provides dial-in numbers in the US > as well as in Europe. > > Thanks, > > Juergen > > Agenda for the ISMS phone conference on July 27 > > 1. Agenda bashing > > 2. Call Home for SSH > > Main subject will be agent initiated channels for notifications. > Juergen S. raised this issue in our last session. Please find his > slides at > > > > The main question to be answered is: "Is the reverse creation of > an SSH session as suggested in the slides an acceptable solution > for ISMS notifications? > > 3. Alternative approaches > > If call home for SSH does not work, alternatives need to be > discussed. Wes listed three of them in his email from July 17: > > . > > We will have as look at all three and try to identify pros and cons > for each of them. > > 4. Summary of technical results > > > > > _______________________________________________ > Isms mailing list > Isms@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/isms _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms