Cancelling Atlanta meeting
Mark Day <markday <at> cisco.com>
2002-11-13 16:06:14 GMT
As you probably know, the purpose of an IETF WG meeting is to identify and
resolve issues that are not readily fixed in email/teleconferences, and to
take advantage of the presence of people from other WGs. Practically
speaking, having a productive meeting requires the presence of at least a
substantial fraction of the people who are active and engaged in the WG, who
are typically authors/editors or active on the mailing list.
Since sending out the message below last Friday, the only messages I have
received from editors and authors are regrets that they are not able to come
While I am grateful that Paul Knight has volunteered to present open issues
on the threats document, we will still be missing at least 4 of the 6
authors for that draft. I have no volunteers/substitutes to present any of
the other group drafts -- I know definitively that none of the editors are
coming, with one exception where I haven't heard.
Accordingly, I am cancelling the CDI meeting planned for Atlanta.
I would be interested in opinions about whether we think CDI can finish its
remaining documents, and if so, how.
> -----Original Message-----
> From: owner-cdn <at> ops.ietf.org [mailto:owner-cdn <at> ops.ietf.org]On Behalf Of
> Mark Day
> Sent: Friday, November 08, 2002 3:07 PM
> To: cdn <at> ops.ietf.org
> Subject: Proposed agenda / should we meet?
> Below is a proposed agenda for a meeting in Atlanta. However, I recently
> learned that neither the editor of the new threat model nor the editor of
> the architecture document will be present. So if we are meeting I need
> substitutes to (a) present the open issues for those documents and (b) own
> the task of capturing any changes or solutions that come out of
> the meeting.
> If we can't hit critical mass to make some sort of meaningful progress in
> Atlanta, I expect I will cancel the meeting.
> Content Distribution Internetworking (CDI)
> Thursday November 21, 1300-1500
> Chair: Mark Day <markday <at> cisco.com>
> Review of status of all group drafts (5 min)
> MODEL draft-ietf-cdi-model-02
> KNOWN-MECHANISMS draft-ietf-cdi-known-request-routing-01
> ARCHITECTURE draft-ietf-cdi-architecture-01
> RR-REQS draft-ietf-cdi-request-routing-reqs-01
> AAA-REQS draft-ietf-cdi-aaa-reqs-01
> SCENARIOS draft-ietf-cdi-scenarios-01
> THREATS draft-ietf-cdi-threat-00
> DIST-REQS [No draft currently available]
> Summary of goals, open issues in THREATS (20 min)
> Discussion (20 min)
> Summary of non-THREATS-related open issues in drafts (20 min).
> Discussion (40 min)