[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fwd: Re: WG Review: Layer 3 Virtual Private Networks (l3vpn)



Current system:
Add extra announcements. Write down what's actually happening, and get the secretariat to send it to ietf-announce and new-work.

Future system:
Let's design it carefullly. But there will ALWAYS be exception cases.

--On onsdag, juni 18, 2003 06:57:22 -0400 Thomas Narten <narten@us.ibm.com> wrote:

--On tirsdag, juni 17, 2003 20:12:04 -0700 Alex Zinin <zinin@psg.com>
wrote:

> FYI. BTW, it is not clear to me that these announcements
> should have gone to the new-work list, since we're splitting
> the WG, and actually make the charters tighter, not add more
> work... anyways...
>

It's new WGs. Better to send one message too many to new-work than to
send  too few.
Our announcement processes for WG charter management are too
mechanical and frequently do the Wrong Thing. When we get around to
adding charter managment to ID Tracker, we will need to have the
ability for the ADs to review the messages before they go out and edit
them when needed.

The announcment for the l2/l3 vpn charters needed a preamble giving
some background saying, e.g., ppvpn is going away and two WGs are
being formed. (Joel Halpern asked me after reading the first message
whether the overlapping tasks would be removed from the ppvpn
charter...)  Similar confusion has happened when a WG gets renamed,
but the announcements go out as "new" and (later) "closed".

Thomas