IETF Logo Mail Archive

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

"WORLEY, Dale R (Dale)" <dworley@avaya.com> Mon, 14 June 2010 02:40 UTC

Return-Path: <dworley@avaya.com>
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 0870D3A6804 for <dispatch@core3.amsl.com>; Sun, 13 Jun 2010 19:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.369
X-Spam-Level:
X-Spam-Status: No, score=-0.369 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2WbL-wc7KdS for <dispatch@core3.amsl.com>; Sun, 13 Jun 2010 19:40:24 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id EC2083A67E3 for <dispatch@ietf.org>; Sun, 13 Jun 2010 19:40:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,412,1272859200"; d="scan'208";a="222852004"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 13 Jun 2010 22:40:27 -0400
X-IronPort-AV: E=Sophos;i="4.53,412,1272859200"; d="scan'208";a="483117201"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 13 Jun 2010 22:40:26 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.188]) by DC-US1HCEX1.global.avaya.com ([::1]) with mapi; Sun, 13 Jun 2010 22:40:26 -0400
From: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Sun, 13 Jun 2010 22:37:12 -0400
Thread-Topic: [dispatch] DISPATCH-78 topics - Alert URNs
Thread-Index: AcsJXXs00HycXaI2R6yBkx/Ino0pAwCDQMbw
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FD73618F@DC-US1MBEX4.global.avaya.com>
References: <AANLkTimrhjA3QLBk2qN2p7mbgsELDDhb_7kUMrxvwa6U@mail.gmail.com>, <4C1224FF.5050105@ericsson.com>
In-Reply-To: <4C1224FF.5050105@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Robert Sparks <RjS@nostrum.com>, DISPATCH <dispatch@ietf.org>
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: Mon, 14 Jun 2010 02:40:25 -0000

________________________________________
From: Gonzalo Camarillo [Gonzalo.Camarillo@ericsson.com]

yes, Mary's description is correct. The process is as follows. Once we
agreed on the charter, I requested the IESG to review it. This charter
will be discussed in the next IESG telechat (the coming Thursday),
actually. Once the IESG is happy with it, the next step will be to have
an IETF-wide review. After that, we will be able to charter the WG.

In any case, as we have said a number of times, proponents of a
particular piece of work should not stop working on it while we charter
their WG. They are encouraged to continue making progress in parallel
with the chartering process.
________________________________________

That is all fine, but what are the implications regarding getting a time slot at Maastricht?  There seem to be two choices:  a slot within Dispatch, or a separately scheduled Salud session.  What we do not want to get stuck with is not being able to get time in Dispatch (because a charter has been proposed) and not being able to get a separate session (because the charter hasn't gone through all the approval steps), as that would prevent any session at  Maastricht.

Dale

v2.23.0 | Report a Bug | By Email