Re: [dispatch] DISPATCH-78 topics - Alert URNs

<L.Liess@telekom.de> Thu, 10 June 2010 06:11 UTC

Return-Path: <L.Liess@telekom.de>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DA713A68CF for <dispatch@core3.amsl.com>; Wed, 9 Jun 2010 23:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0x9P-t9ur3HN for <dispatch@core3.amsl.com>; Wed, 9 Jun 2010 23:11:55 -0700 (PDT)
Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by core3.amsl.com (Postfix) with ESMTP id 62C2B3A6888 for <dispatch@ietf.org>; Wed, 9 Jun 2010 23:11:54 -0700 (PDT)
Received: from s4de9jsaanm.mgb.telekom.de (HELO S4DE9JSAANM.ost.t-com.de) ([10.125.177.122]) by tcmail51.telekom.de with ESMTP; 10 Jun 2010 08:11:46 +0200
Received: from S4DE9JSAANI.ost.t-com.de ([10.125.177.223]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.4675); Thu, 10 Jun 2010 08:11:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 Jun 2010 08:11:39 +0200
Message-ID: <40FB0FFB97588246A1BEFB05759DC8A004586080@S4DE9JSAANI.ost.t-com.de>
In-Reply-To: <AANLkTimrhjA3QLBk2qN2p7mbgsELDDhb_7kUMrxvwa6U@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dispatch] DISPATCH-78 topics - Alert URNs
Thread-Index: AcsH9xMRwYAcjGeeTNqDbYp7kJctbAAbJg8g
References: <AANLkTimrhjA3QLBk2qN2p7mbgsELDDhb_7kUMrxvwa6U@mail.gmail.com>
From: L.Liess@telekom.de
To: mary.ietf.barnes@gmail.com, laura.liess.dt@googlemail.com
X-OriginalArrivalTime: 10 Jun 2010 06:11:41.0004 (UTC) FILETIME=[CAF528C0:01CB0863]
Cc: RjS@nostrum.com, dispatch@ietf.org, gonzalo.camarillo@ericsson.com
Subject: Re: [dispatch] DISPATCH-78 topics - Alert URNs
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 06:11:56 -0000

Hi Mary,

Thanks a lot.

Laura
 

>-----Original Message-----
>From: dispatch-bounces@ietf.org 
>[mailto:dispatch-bounces@ietf.org] On Behalf Of Mary Barnes
>Sent: Wednesday, June 09, 2010 7:13 PM
>To: Laura Liess
>Cc: Robert Sparks; DISPATCH; Gonzalo Camarillo
>Subject: Re: [dispatch] DISPATCH-78 topics - Alert URNs
>
>Hi Laura,
>
>We did not consider this topic for pre-IETF-78 focus for the DISPATCH
>WG because the ADs are already in the process of preparing the charter
>for approval by the IESG, as I understood Gonzalo's emails on the
>topic.   I'll let ADs discuss the timeline for the chartering and
>really it would be up to them as to whether a meeting agenda slot
>would be requested for the topic.
>
>The current model we've been using is that past topics that have been
>agreed to be chartered have already been "dispatched" per se, per the
>summaries in the wiki:
>http://trac.tools.ietf.org/wg/dispatch/trac/wiki
>
>Thanks,
>Mary.
>
>
>
>
>On Wed, Jun 9, 2010 at 2:19 AM, Laura Liess
><laura.liess.dt@googlemail.com> wrote:
>> Hi Mary, Gonzalo,
>>
>> What about the Alert-Info URN?  We had a lot of discussion about the
>> charter and name, my opinion was that we had consensus on 
>the charter.
>> Dale would chair the WG.  I intend to submit a new draft version by
>> the end of June.
>> I also sent to you an e-mail some time ago asking for a time slot for
>> discussion in Masstricht. Is it anything I missed to do to get agenda
>> time?
>>
>> Thanks a lot
>> Laura
>>
>>
>>
>>
>> 2010/6/8 Mary Barnes <mary.ietf.barnes@gmail.com>:
>>> Hi all,
>>>
>>> Per the reminder posted on the ML on May 4th and as listed on the
>>> DISPATCH WG wiki, charter proposals for the topics to be
>>> handled/dispatched prior to and at IETF-78 were due on May 31st.
>>>
>>> We received charter proposals (problem 
>statements/deliverables) for the
>>> following, with links to most recent charter proposals and 
>discussion threads.
>>>
>>> o Session-ID:  updated charter proposal available
>>> http://www.ietf.org/mail-archive/web/dispatch/current/msg01967.html
>>>
>>> o Telepresence:  updated charter proposal available
>>> http://www.ietf.org/mail-archive/web/dispatch/current/msg01936.html
>>>
>>> o VIPR:  charter proposal
>>> http://www.ietf.org/mail-archive/web/dispatch/current/msg01930.html
>>>
>>> o TEL URI WG proposal:  discussion to focus on problem 
>statement and scope
>>> http://www.ietf.org/mail-archive/web/dispatch/current/msg01920.html
>>>
>>> The above items are the current targets for IETF-78 
>discussions.  Based
>>> on those discussions, agenda time will be allocated, items 
>dispatched
>>> and adhocs scheduled as appropriate. Note, that the minimum time we
>>> would allocate to a topic is 30 minutes and some may warrant 45
>>> minutes. If we schedule adhocs, we will try to have those announced
>>> around the time the agenda is finalized.
>>>
>>> The following items have also been discussed on the mailing 
>list, but
>>> are not yet ready for dispatching:
>>>
>>> o NGN Reason: Some interest. Needs more discussion and scoping.
>>> 
>http://datatracker.ietf.org/doc/draft-jesske-dispatch-reason-in
>-responses/
>>> 
>http://datatracker.ietf.org/doc/draft-jesske-dispatch-req-reaso
n-in-responses/
>>>
>>> o PAN - wait for more energy
>>> 
>http://datatracker.ietf.org/doc/draft-lawrence-sipforum-provider-alias/
>>>
>>> o  ACH - ACH analysis draft to happen as part of BLISS wind down
>>> http://datatracker.ietf.org/doc/draft-ietf-bliss-ach-analysis/
>>>
>>> o  ACH - HTTP API docs - need some hallway discussions
>>> http://datatracker.ietf.org/doc/draft-yusef-dispatch-ach-rest-api/
>>>
>>> o  Media security - needs additional ML discussion
>>> 
>http://datatracker.ietf.org/doc/draft-dawes-dispatch-mediasec-p
arameter/
>>>
>>> o Communication diversion and barring notification - 
>feedback thus far
>>> needs to be considered - i.e, problem statement to be clarified and
>>> alternate solutions to be consider (Note: IPR on the communication
>>> diversion draft)
>>> 
>http://datatracker.ietf.org/doc/draft-avasarala-dispatch-comm-d
iv-notification/
>>> 
>http://datatracker.ietf.org/doc/-avasarala-dispatch-comm-barrin
g-notification/
>>>
>>>
>>> As a reminder, the following are the cutoffs for drafts, so 
>please make
>>> sure that any drafts relevant to the topic are submitted 
>prior to those
>>> deadlines:
>>> * - 00 documents:  July 5th (< 4 weeks)
>>> * all other documents: July 12th (< 5 weeks)
>>>
>>> Please keep in mind that the focus of discussions should be 
>the problem
>>> statement, scope and proposed deliverables for the topic.
>>>
>>> As a reminder, items can be dispatched without being 
>discussed at a f2f
>>> meeting and the most effective way to achieve this is to 
>have problem
>>> statements, scope of topics and any relevant documents available for
>>> discussion, rather than documents focusing on solutions.
>>>
>>> Please, let the chairs know if there are any concerns.
>>>
>>> Thanks,
>>> Mary Barnes and Cullen Jennings
>>> DISPATCH WG chairs
>>> _______________________________________________
>>> dispatch mailing list
>>> dispatch@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dispatch
>>>
>>
>_______________________________________________
>dispatch mailing list
>dispatch@ietf.org
>https://www.ietf.org/mailman/listinfo/dispatch
>