
From prvs=18829a7440=gonzalo.camarillo@ericsson.com  Wed Jun 19 00:03:40 2013
Return-Path: <prvs=18829a7440=gonzalo.camarillo@ericsson.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB23421F9F62 for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 00:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.004
X-Spam-Level: 
X-Spam-Status: No, score=-106.004 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gC+LOsE9WmXI for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 00:03:25 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id A5F9421F9F60 for <rai@ietf.org>; Wed, 19 Jun 2013 00:03:24 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-7a-51c157bb046c
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 0A.F0.15700.BB751C15; Wed, 19 Jun 2013 09:03:23 +0200 (CEST)
Received: from [131.160.126.60] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Jun 2013 09:03:23 +0200
Message-ID: <51C157BA.70509@ericsson.com>
Date: Wed, 19 Jun 2013 10:03:22 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: rai@ietf.org
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJJMWRmVeSWpSXmKPExsUyM+Jvre7u8IOBBptOm1l83vKM1YHRY8mS n0wBjFHcNkmJJWXBmel5+nYJ3Bm3121hKvjAV9E5+zVzA2MrTxcjJ4eEgInE3ROrGSFsMYkL 99azdTFycQgJnGKUmHXoKAuEs4ZRYuvju6wgVbwCmhKzzk0H62ARUJXomf+FCcRmE7CQ2HLr PguILSoQJTFn3QM2iHpBiZMzn4DFRQQEJBY8W8EMYgsDbZ6ybgETxGZJiS0v2tlBbGYBPYkp V1sYIWx5ie1v54DVCwloSyx/1sIygZF/FpKxs5C0zELSsoCReRUje25iZk56ueEmRmBIHdzy W3cH46lzIocYpTlYlMR5P5zaFSgkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDE0RwSQEDacbWH7k8 KXWeRosONeiLMjhWc/bpnHOzY/t9ucLW60CdxqV37gcW+gVrr333bOlvpmmbmArXr2LdNVmW S/dZS7TAVP/Gi6tuVK1WLn7nbKiyX2ct94Mj3w8/619zpmXStolTv/owayy9fGsFYwHjvTmK 5UcNfdQW3Tl0UOpygl9XymGHeVe6lFiKMxINtZiLihMBN8gERPwBAAA=
Subject: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 07:03:40 -0000

Folks,

as you know, in the RAI area we have always considered having effective
processes to help us produce relevant and timely specifications a very
important issue. When our environment has changed, we have sometimes
modified or fine tuned our processes in order to continue being
effective. A few examples (among many others) of such changes were the
introduction of mentors, the old SIPPING process, P headers, and the
current DISPATCH process.

It is time for us to look at the current state of affairs and discuss
whether or not we need to do certain things in a different way.

In particular, we currently have a few groups (e.g., RTCWeb and CLUE)
that work on higher-level constructions, which use elements developed in
other working groups. For example, CLUE could potentially specify a
mechanism that used mechanisms developed in MMUSIC or AVTEXT such as the
offer/answer model and a number of RTP extensions.

Note that what we called "higher-level constructions" above are referred
to by different names by different people: architectures, applications,
frameworks, etc. It does not really matter how we call them because this
discussion is not about terminology and it is fairly clear what this
type of work is about.

The way this type of work is currently done in RAI requires the
high-level WGs and the WGs developing the individual pieces to
communicate often. Those communications are not always easy, since
different WGs sometimes have different views on priorities,
requirements, use cases, etc.

What we would like to get your feedback on is: do we need a better way
to handle this type of work in RAI or our current process is as good as
it gets?

Note that we are interested in getting constructive feedback and ideas
on how to improve things. Please, focus your feedback on those aspects.

Thanks,

Gonzalo
(on behalf of both RAI ADs)


From br@brianrosen.net  Wed Jun 19 06:05:42 2013
Return-Path: <br@brianrosen.net>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60E2A21F9BFE for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 06:05:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.307
X-Spam-Level: 
X-Spam-Status: No, score=-100.307 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VIeElYJ72Ovv for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 06:05:38 -0700 (PDT)
Received: from mm2.idig.net (unknown [70.33.247.98]) by ietfa.amsl.com (Postfix) with ESMTP id BD58921F9BC8 for <rai@ietf.org>; Wed, 19 Jun 2013 06:05:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brianrosen.net; s=default;  h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=zxCz4GBxJ7QGa4rw7bSns8bm2aSQA9drXJCWfny4Oek=;  b=V0YGVqYw/XFq5LnsqAjeIL/woPCxeZPlV+4F/rXo1y4R8F2kNBWctmjX5/E++UJSMhNVwQShLQHc/UHKV4BXV1Swtgg5wen2O6JN6nHm7wAE7/QkihgB9WsXjdydZ6Sde+Z/s3d1Ea2M8ANXs+hm3MML8aI3Q2Jq6ZPX3oHNH0Y=;
Received: from neustargw.va.neustar.com ([209.173.53.233]:42920 helo=[10.33.193.17]) by mm2.idig.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <br@brianrosen.net>) id 1UpI4k-0000Eq-Aw; Wed, 19 Jun 2013 09:05:26 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <51C157BA.70509@ericsson.com>
Date: Wed, 19 Jun 2013 09:05:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net>
References: <51C157BA.70509@ericsson.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-Mailer: Apple Mail (2.1508)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - mm2.idig.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Get-Message-Sender-Via: mm2.idig.net: authenticated_id: br@brianrosen.net
Cc: rai@ietf.org
Subject: Re: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 13:05:42 -0000

Suppose we treated this as a mini-WG
1. The chairs and ADs work out a charter, with a limited WG time period =
to discuss. No IESG participation.
2. One chair is appointed from among the affected WG chairs
3. A new email list is created
4. Discussion is held during one of the WG meeting slots.  It can =
alternate perhaps between the affected groups.  The mini-group doesn't =
get a slot, but of course it may result in a WG asking for two slots for =
a particular meeting.
5. If there are cross AD issues, one AD is selected

Put a cap on this effort, and make it short - 2 meeting cycles maybe.  =
If they can't agree, then most likely each of the WGs will need to come =
up with their own solutions.
The mini-WG milestone may not be a submitted draft, it could be a mature =
draft, that would be finished in one of the affected WGs.  It could even =
be a general agreement on the solution, rather than an actual mature =
draft.  At the end, the mail list is closed., further discussion if any =
happens in the WGs.

Brian
On Jun 19, 2013, at 3:03 AM, Gonzalo Camarillo =
<Gonzalo.Camarillo@ericsson.com> wrote:

> Folks,
>=20
> as you know, in the RAI area we have always considered having =
effective
> processes to help us produce relevant and timely specifications a very
> important issue. When our environment has changed, we have sometimes
> modified or fine tuned our processes in order to continue being
> effective. A few examples (among many others) of such changes were the
> introduction of mentors, the old SIPPING process, P headers, and the
> current DISPATCH process.
>=20
> It is time for us to look at the current state of affairs and discuss
> whether or not we need to do certain things in a different way.
>=20
> In particular, we currently have a few groups (e.g., RTCWeb and CLUE)
> that work on higher-level constructions, which use elements developed =
in
> other working groups. For example, CLUE could potentially specify a
> mechanism that used mechanisms developed in MMUSIC or AVTEXT such as =
the
> offer/answer model and a number of RTP extensions.
>=20
> Note that what we called "higher-level constructions" above are =
referred
> to by different names by different people: architectures, =
applications,
> frameworks, etc. It does not really matter how we call them because =
this
> discussion is not about terminology and it is fairly clear what this
> type of work is about.
>=20
> The way this type of work is currently done in RAI requires the
> high-level WGs and the WGs developing the individual pieces to
> communicate often. Those communications are not always easy, since
> different WGs sometimes have different views on priorities,
> requirements, use cases, etc.
>=20
> What we would like to get your feedback on is: do we need a better way
> to handle this type of work in RAI or our current process is as good =
as
> it gets?
>=20
> Note that we are interested in getting constructive feedback and ideas
> on how to improve things. Please, focus your feedback on those =
aspects.
>=20
> Thanks,
>=20
> Gonzalo
> (on behalf of both RAI ADs)
>=20
> _______________________________________________
> RAI mailing list
> RAI@ietf.org
> https://www.ietf.org/mailman/listinfo/rai


From mary.ietf.barnes@gmail.com  Wed Jun 19 07:35:21 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68EC021F9C4D for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 07:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.301
X-Spam-Level: 
X-Spam-Status: No, score=-103.301 tagged_above=-999 required=5 tests=[AWL=0.298, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAQSoXRjpQ4q for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 07:35:17 -0700 (PDT)
Received: from mail-qe0-f49.google.com (mail-qe0-f49.google.com [209.85.128.49]) by ietfa.amsl.com (Postfix) with ESMTP id 27CA821F9C4C for <rai@ietf.org>; Wed, 19 Jun 2013 07:35:17 -0700 (PDT)
Received: by mail-qe0-f49.google.com with SMTP id cz11so3272505qeb.22 for <rai@ietf.org>; Wed, 19 Jun 2013 07:35:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2Jh1wqEQUrecHgbZHF8dDvFnMmWa2xLdA460iROcaDw=; b=SGOICroG0lJmkfz+sXWsVb1IUVEFCbWX17aAgaJI+yXtaW+vGt8nTmjnn9ujFKG1UK 2w3Ho+2llTnKowbWen0DTuK/C9a4lImrf4D2Du2sye0J1cZ0ZKKGpRm/a6c2n4F6lBJW gYscw9gLow5RNQTqvS23rD69djJ+zj4a0ggm/gjJ7A+vRMewJwfD3sMi3cUPn8Sz67Qv ZHfjAC3Fytbp4PRKeekUEwMedhS8TyXf9Tc4Ft1/2vw/56mjanDQYb6fK+tw4gbiVejk WXD5wMsPsIQv9difm4m/xNo83LzMH6D9pqELOImDMZOYkcUchlSO9eSjH8OcQmjSUjQZ w4OQ==
MIME-Version: 1.0
X-Received: by 10.224.38.133 with SMTP id b5mr4021434qae.78.1371652516607; Wed, 19 Jun 2013 07:35:16 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Wed, 19 Jun 2013 07:35:16 -0700 (PDT)
In-Reply-To: <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net>
References: <51C157BA.70509@ericsson.com> <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net>
Date: Wed, 19 Jun 2013 09:35:16 -0500
Message-ID: <CAHBDyN5zFVfj6we1X_PXoGKjax1h-X2Qots9EO6vbogmhduF1w@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Brian Rosen <br@brianrosen.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "rai@ietf.org" <rai@ietf.org>
Subject: Re: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 14:35:21 -0000

I like Brian's suggestion as one of the big issues here is that we
have debated some of these issues for eons so it would be good to set
a deadline.  I would strongly suggest that a WG chair that has a
vested interest in a particular proposal (i.e., as an author or
perhaps even with colleagues as co-authors) should NOT be one of the
WG chairs for this joint activity.

Thanks for raising this issue.

Mary.

On Wed, Jun 19, 2013 at 8:05 AM, Brian Rosen <br@brianrosen.net> wrote:
> Suppose we treated this as a mini-WG
> 1. The chairs and ADs work out a charter, with a limited WG time period t=
o discuss. No IESG participation.
> 2. One chair is appointed from among the affected WG chairs
> 3. A new email list is created
> 4. Discussion is held during one of the WG meeting slots.  It can alterna=
te perhaps between the affected groups.  The mini-group doesn't get a slot,=
 but of course it may result in a WG asking for two slots for a particular =
meeting.
> 5. If there are cross AD issues, one AD is selected
>
> Put a cap on this effort, and make it short - 2 meeting cycles maybe.  If=
 they can't agree, then most likely each of the WGs will need to come up wi=
th their own solutions.
> The mini-WG milestone may not be a submitted draft, it could be a mature =
draft, that would be finished in one of the affected WGs.  It could even be=
 a general agreement on the solution, rather than an actual mature draft.  =
At the end, the mail list is closed., further discussion if any happens in =
the WGs.
>
> Brian
> On Jun 19, 2013, at 3:03 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsso=
n.com> wrote:
>
>> Folks,
>>
>> as you know, in the RAI area we have always considered having effective
>> processes to help us produce relevant and timely specifications a very
>> important issue. When our environment has changed, we have sometimes
>> modified or fine tuned our processes in order to continue being
>> effective. A few examples (among many others) of such changes were the
>> introduction of mentors, the old SIPPING process, P headers, and the
>> current DISPATCH process.
>>
>> It is time for us to look at the current state of affairs and discuss
>> whether or not we need to do certain things in a different way.
>>
>> In particular, we currently have a few groups (e.g., RTCWeb and CLUE)
>> that work on higher-level constructions, which use elements developed in
>> other working groups. For example, CLUE could potentially specify a
>> mechanism that used mechanisms developed in MMUSIC or AVTEXT such as the
>> offer/answer model and a number of RTP extensions.
>>
>> Note that what we called "higher-level constructions" above are referred
>> to by different names by different people: architectures, applications,
>> frameworks, etc. It does not really matter how we call them because this
>> discussion is not about terminology and it is fairly clear what this
>> type of work is about.
>>
>> The way this type of work is currently done in RAI requires the
>> high-level WGs and the WGs developing the individual pieces to
>> communicate often. Those communications are not always easy, since
>> different WGs sometimes have different views on priorities,
>> requirements, use cases, etc.
>>
>> What we would like to get your feedback on is: do we need a better way
>> to handle this type of work in RAI or our current process is as good as
>> it gets?
>>
>> Note that we are interested in getting constructive feedback and ideas
>> on how to improve things. Please, focus your feedback on those aspects.
>>
>> Thanks,
>>
>> Gonzalo
>> (on behalf of both RAI ADs)
>>
>> _______________________________________________
>> RAI mailing list
>> RAI@ietf.org
>> https://www.ietf.org/mailman/listinfo/rai
>
> _______________________________________________
> RAI mailing list
> RAI@ietf.org
> https://www.ietf.org/mailman/listinfo/rai

From john@jlc.net  Wed Jun 19 07:43:35 2013
Return-Path: <john@jlc.net>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4BA21F9CAF for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 07:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.098
X-Spam-Level: 
X-Spam-Status: No, score=-106.098 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSFUKG-4nek8 for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 07:43:30 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA8B21F9C41 for <rai@ietf.org>; Wed, 19 Jun 2013 07:43:30 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 3174F33C20; Wed, 19 Jun 2013 10:43:29 -0400 (EDT)
Date: Wed, 19 Jun 2013 10:43:29 -0400
From: John Leslie <john@jlc.net>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <20130619144329.GC44982@verdi>
References: <51C157BA.70509@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51C157BA.70509@ericsson.com>
User-Agent: Mutt/1.4.1i
Cc: rai@ietf.org
Subject: Re: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 14:43:35 -0000

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> wrote:
> 
> It is time for us to look at the current state of affairs and discuss
> whether or not we need to do certain things in a different way.
> 
> In particular, we currently have a few groups (e.g., RTCWeb and CLUE)
> that work on higher-level constructions, which use elements developed in
> other working groups. For example, CLUE could potentially specify a
> mechanism that used mechanisms developed in MMUSIC or AVTEXT such as the
> offer/answer model and a number of RTP extensions.

   There is a very obvious three-way interaction among CLUE, RTCWeb, and
MMUSIC. The process is dangerously close to stalled because there's no
hope of reaching agreement on which roadblock needs to be cleared first.

   :^( :^( :^(

> Note that what we called "higher-level constructions" above are referred
> to by different names by different people: architectures, applications,
> frameworks, etc. It does not really matter how we call them because this
> discussion is not about terminology and it is fairly clear what this
> type of work is about.

   Alas, it's not as clear as you think.

> The way this type of work is currently done in RAI requires the
> high-level WGs and the WGs developing the individual pieces to
> communicate often. Those communications are not always easy, since
> different WGs sometimes have different views on priorities,
> requirements, use cases, etc.

   That's not the problem. Communication among the WGs is quite good:
there are essentially no arguments which piece belongs in which WG.
The problem perhaps stems from all three WGs needing to follow the work
of both RTCWeb and MMUSIC (thus including folks who otherwise wouldn't
pay attention); but the actual problem is that the dependencies are
too strict.

   My advice, when this sort of situation occurs, is to chop out the
strict dependencies. In this case, MMUSIC seems unable to resolve
"Plan A" vs. "Plan B". Thus, management should find a way to make
that choice no longer gating on RTCWeb and CLUE.

   Perhaps it's not obvious how to do that; but once you give your
attention to _that_ as the problem, several approaches should become
apparent.

> What we would like to get your feedback on is: do we need a better way
> to handle this type of work in RAI or our current process is as good as
> it gets?

   This doesn't strike me as a "process" question exactly. But we do
need some mechanism to find a way to decouple issues which deserve to
be settled in a different WG without requiring everyone to join that
other WG.

   (This is particularly painful to me right now, since I find myself
unable to give enough attention to both RTCWeb and MMUSIC, when what
I really want is to make progress in CLUE.)

   I'm not going to make any particular recommendation on how to
decouple these issues in this email; but I'm willing to do so in a
different email if Gonzalo asks for it.

--
John Leslie <john@jlc.net>

From ben@nostrum.com  Wed Jun 19 08:54:49 2013
Return-Path: <ben@nostrum.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3AB921F9D73 for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 08:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5sf4totI88q for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 08:54:47 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD4C21F9D3E for <rai@ietf.org>; Wed, 19 Jun 2013 08:54:47 -0700 (PDT)
Received: from [172.20.10.2] (mobile-166-147-069-103.mycingular.net [166.147.69.103]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5JFsdrB003138 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Jun 2013 10:54:40 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net>
Date: Wed, 19 Jun 2013 10:54:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B7CBDE1-7472-4312-935C-6B7D2284A90F@nostrum.com>
References: <51C157BA.70509@ericsson.com> <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net>
To: Brian Rosen <br@brianrosen.net>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 166.147.69.103 is authenticated by a trusted mechanism)
Cc: rai@ietf.org
Subject: Re: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 15:54:49 -0000

Hi Brian,

It's not clear to me what scope you intend for the mini-wg. Does it =
handle the "higher-level constructions"? Is it responsible for breaking =
the interdependency logjams? Something else?

What keeps the min-wg from becoming the union of all interested parties =
from all the existing wgs? (Or was that what you intended?)

Thanks!

Ben.

On Jun 19, 2013, at 8:05 AM, Brian Rosen <br@brianrosen.net> wrote:

> Suppose we treated this as a mini-WG
> 1. The chairs and ADs work out a charter, with a limited WG time =
period to discuss. No IESG participation.
> 2. One chair is appointed from among the affected WG chairs
> 3. A new email list is created
> 4. Discussion is held during one of the WG meeting slots.  It can =
alternate perhaps between the affected groups.  The mini-group doesn't =
get a slot, but of course it may result in a WG asking for two slots for =
a particular meeting.
> 5. If there are cross AD issues, one AD is selected
>=20
> Put a cap on this effort, and make it short - 2 meeting cycles maybe.  =
If they can't agree, then most likely each of the WGs will need to come =
up with their own solutions.
> The mini-WG milestone may not be a submitted draft, it could be a =
mature draft, that would be finished in one of the affected WGs.  It =
could even be a general agreement on the solution, rather than an actual =
mature draft.  At the end, the mail list is closed., further discussion =
if any happens in the WGs.
>=20
> Brian
> On Jun 19, 2013, at 3:03 AM, Gonzalo Camarillo =
<Gonzalo.Camarillo@ericsson.com> wrote:
>=20
>> Folks,
>>=20
>> as you know, in the RAI area we have always considered having =
effective
>> processes to help us produce relevant and timely specifications a =
very
>> important issue. When our environment has changed, we have sometimes
>> modified or fine tuned our processes in order to continue being
>> effective. A few examples (among many others) of such changes were =
the
>> introduction of mentors, the old SIPPING process, P headers, and the
>> current DISPATCH process.
>>=20
>> It is time for us to look at the current state of affairs and discuss
>> whether or not we need to do certain things in a different way.
>>=20
>> In particular, we currently have a few groups (e.g., RTCWeb and CLUE)
>> that work on higher-level constructions, which use elements developed =
in
>> other working groups. For example, CLUE could potentially specify a
>> mechanism that used mechanisms developed in MMUSIC or AVTEXT such as =
the
>> offer/answer model and a number of RTP extensions.
>>=20
>> Note that what we called "higher-level constructions" above are =
referred
>> to by different names by different people: architectures, =
applications,
>> frameworks, etc. It does not really matter how we call them because =
this
>> discussion is not about terminology and it is fairly clear what this
>> type of work is about.
>>=20
>> The way this type of work is currently done in RAI requires the
>> high-level WGs and the WGs developing the individual pieces to
>> communicate often. Those communications are not always easy, since
>> different WGs sometimes have different views on priorities,
>> requirements, use cases, etc.
>>=20
>> What we would like to get your feedback on is: do we need a better =
way
>> to handle this type of work in RAI or our current process is as good =
as
>> it gets?
>>=20
>> Note that we are interested in getting constructive feedback and =
ideas
>> on how to improve things. Please, focus your feedback on those =
aspects.
>>=20
>> Thanks,
>>=20
>> Gonzalo
>> (on behalf of both RAI ADs)
>>=20
>> _______________________________________________
>> RAI mailing list
>> RAI@ietf.org
>> https://www.ietf.org/mailman/listinfo/rai
>=20
> _______________________________________________
> RAI mailing list
> RAI@ietf.org
> https://www.ietf.org/mailman/listinfo/rai


From mary.ietf.barnes@gmail.com  Wed Jun 19 09:53:33 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8812921F9D88 for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 09:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.416
X-Spam-Level: 
X-Spam-Status: No, score=-102.416 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKp9GKUe3P5P for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 09:53:32 -0700 (PDT)
Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7D45C21F9D86 for <rai@ietf.org>; Wed, 19 Jun 2013 09:53:32 -0700 (PDT)
Received: by mail-qc0-f171.google.com with SMTP id n1so3158812qcw.16 for <rai@ietf.org>; Wed, 19 Jun 2013 09:53:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=AZf6Vg41KGsISV3br8Cw80kkCOQ8PsfO6w1jIJZUP4s=; b=GPESBuk9li7a+1grxp7+3Ygg1u7vmMO7ghlO5N/hoRtKMZMxCU9vglqdmetnuxbHGQ o8kfGPpXc1OduDhWAk+/7imxjR0JlX+HzqmK3Sa9UXUCVEneMTnInNf9Wg/u63PDtzUM R9I6AVrsRfv4edqH1lnglLVIffhmOd3yFm/Pz/R51e2Wj2YLHUt0rT1J3z++1wymyC27 forZEDsFn4yGHBpi0RiJF+fsmsucunial362zPBxw9F+0zA6UZulB0j6uXwgIeE7oGz/ pQhrl4guUGqq5sTgfmw88RrKYWiDM/b4Zd6h/crNlwAtgFa5rRT183VcntgMaOOKNvMG vxoA==
MIME-Version: 1.0
X-Received: by 10.224.180.133 with SMTP id bu5mr4797462qab.50.1371660811820; Wed, 19 Jun 2013 09:53:31 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Wed, 19 Jun 2013 09:53:31 -0700 (PDT)
In-Reply-To: <6B7CBDE1-7472-4312-935C-6B7D2284A90F@nostrum.com>
References: <51C157BA.70509@ericsson.com> <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net> <6B7CBDE1-7472-4312-935C-6B7D2284A90F@nostrum.com>
Date: Wed, 19 Jun 2013 11:53:31 -0500
Message-ID: <CAHBDyN4UJiWY2KZg2Z2qv7AmDPByzeHEg=ft-xq1AZvNkMw9Fw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "rai@ietf.org" <rai@ietf.org>
Subject: Re: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 16:53:33 -0000

I'm not Brian but I'll go ahead and respond with my perspective [MB].

Mary.

On Wed, Jun 19, 2013 at 10:54 AM, Ben Campbell <ben@nostrum.com> wrote:
> Hi Brian,
>
> It's not clear to me what scope you intend for the mini-wg. Does it handl=
e the "higher-level constructions"? Is it responsible for breaking the inte=
rdependency logjams? Something else?
[MB] I believe the "higher-level constructions" (which are
"applications" in my mind) are the responsibility of the group
chartered to create that solution based on existing protocols as well
as any new protocols the specific WG deems necessary.  The new mini-WG
is intended to deal with the solution requirements that may need to
change existing protocols. [/MB]
>
> What keeps the min-wg from becoming the union of all interested parties f=
rom all the existing wgs? (Or was that what you intended?)
[MB] The new mini-WG would be the union of all the parties that are
interested in reusing and changing existing protocols. This doesn't
impact the existing WGs chartered to define the solution for the
"higher-level constructions" - this does impact some of the existing
protocol building blocks that they may need to reuse and extend.
While we have WGs that are explicitly chartered to define new
extensions (e.g., MMUSIC for SDP), it's impossible to isolate the
solution aspects (from the "higher-level construct" WGs) and
requirements from the extensions that might be needed in the other WG.
 This gets to be particularly problematic in the case where you have
two WGs defining new "applications".  The big issue is figuring out
who is responsible for guiding the work in the existing WG where
extensions need to be defined.  Again, it's impossible to do the work
and have sensible discussions without understanding some aspects
required by the solution (and why they are required). While it's
tempting for the chairs of the WG where extensions need to be defined
to suggest that "application" discussions are out of scope, that just
doesn't work.  By having chairs from all the WGs involved represented
in the new mini-WG, everyone has "equal stakes" so to speak in
ensuring that a solution is reached.  Setting a specific deadline is
extremely helpful as it helps deal with deadlock situations and the
reality that the new "applications" may not be able to use the same
extensions, for example.
[/MB]
>
> Thanks!
>
> Ben.
>
> On Jun 19, 2013, at 8:05 AM, Brian Rosen <br@brianrosen.net> wrote:
>
>> Suppose we treated this as a mini-WG
>> 1. The chairs and ADs work out a charter, with a limited WG time period =
to discuss. No IESG participation.
>> 2. One chair is appointed from among the affected WG chairs
>> 3. A new email list is created
>> 4. Discussion is held during one of the WG meeting slots.  It can altern=
ate perhaps between the affected groups.  The mini-group doesn't get a slot=
, but of course it may result in a WG asking for two slots for a particular=
 meeting.
>> 5. If there are cross AD issues, one AD is selected
>>
>> Put a cap on this effort, and make it short - 2 meeting cycles maybe.  I=
f they can't agree, then most likely each of the WGs will need to come up w=
ith their own solutions.
>> The mini-WG milestone may not be a submitted draft, it could be a mature=
 draft, that would be finished in one of the affected WGs.  It could even b=
e a general agreement on the solution, rather than an actual mature draft. =
 At the end, the mail list is closed., further discussion if any happens in=
 the WGs.
>>
>> Brian
>> On Jun 19, 2013, at 3:03 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericss=
on.com> wrote:
>>
>>> Folks,
>>>
>>> as you know, in the RAI area we have always considered having effective
>>> processes to help us produce relevant and timely specifications a very
>>> important issue. When our environment has changed, we have sometimes
>>> modified or fine tuned our processes in order to continue being
>>> effective. A few examples (among many others) of such changes were the
>>> introduction of mentors, the old SIPPING process, P headers, and the
>>> current DISPATCH process.
>>>
>>> It is time for us to look at the current state of affairs and discuss
>>> whether or not we need to do certain things in a different way.
>>>
>>> In particular, we currently have a few groups (e.g., RTCWeb and CLUE)
>>> that work on higher-level constructions, which use elements developed i=
n
>>> other working groups. For example, CLUE could potentially specify a
>>> mechanism that used mechanisms developed in MMUSIC or AVTEXT such as th=
e
>>> offer/answer model and a number of RTP extensions.
>>>
>>> Note that what we called "higher-level constructions" above are referre=
d
>>> to by different names by different people: architectures, applications,
>>> frameworks, etc. It does not really matter how we call them because thi=
s
>>> discussion is not about terminology and it is fairly clear what this
>>> type of work is about.
>>>
>>> The way this type of work is currently done in RAI requires the
>>> high-level WGs and the WGs developing the individual pieces to
>>> communicate often. Those communications are not always easy, since
>>> different WGs sometimes have different views on priorities,
>>> requirements, use cases, etc.
>>>
>>> What we would like to get your feedback on is: do we need a better way
>>> to handle this type of work in RAI or our current process is as good as
>>> it gets?
>>>
>>> Note that we are interested in getting constructive feedback and ideas
>>> on how to improve things. Please, focus your feedback on those aspects.
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>> (on behalf of both RAI ADs)
>>>
>>> _______________________________________________
>>> RAI mailing list
>>> RAI@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rai
>>
>> _______________________________________________
>> RAI mailing list
>> RAI@ietf.org
>> https://www.ietf.org/mailman/listinfo/rai
>
> _______________________________________________
> RAI mailing list
> RAI@ietf.org
> https://www.ietf.org/mailman/listinfo/rai

From mary.ietf.barnes@gmail.com  Wed Jun 19 09:54:57 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEA6D21F9DA6 for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 09:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.453
X-Spam-Level: 
X-Spam-Status: No, score=-102.453 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VvYlNcDxbfR9 for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 09:54:55 -0700 (PDT)
Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 6B75421F9D8E for <rai@ietf.org>; Wed, 19 Jun 2013 09:54:50 -0700 (PDT)
Received: by mail-qc0-f171.google.com with SMTP id n1so3159683qcw.16 for <rai@ietf.org>; Wed, 19 Jun 2013 09:54:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Z/yakUf/T9hahKOQDlQZFNfJWUozk0ZwSl06oibLOpI=; b=0CvzXlV42Y3Lb5jRaEdxbpxKH3FvDxykDcTkLtwn7jEAFmzqjIVbQo9EoyuQBajQ25 T58NFt4bOiuWyKDikElgUMjDX+FH1vXCRm0TX5fMMro1TE2X/IX7dOhHdLPjIGIH88W3 qi2lNM3DHcXxTAgaRYujN7lSAmwntyZMPjpe9qOZzw14coWjROChE/kJQi7RBi5Or57C e/k9fDvwtMGJX9jMiA2eas/V8d5FzW4geUD7XoKvx5NL2vpP5qvn5sJI0eR/QuUrLF+q Qhxg7CkBnr+6C4USWcXE3789I4TGtlvZMyFMDnGxNJy411LinOlcoY1/9uXHyo5HcXrY nMMw==
MIME-Version: 1.0
X-Received: by 10.229.177.10 with SMTP id bg10mr1379729qcb.135.1371660889932;  Wed, 19 Jun 2013 09:54:49 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Wed, 19 Jun 2013 09:54:49 -0700 (PDT)
In-Reply-To: <CAHBDyN4UJiWY2KZg2Z2qv7AmDPByzeHEg=ft-xq1AZvNkMw9Fw@mail.gmail.com>
References: <51C157BA.70509@ericsson.com> <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net> <6B7CBDE1-7472-4312-935C-6B7D2284A90F@nostrum.com> <CAHBDyN4UJiWY2KZg2Z2qv7AmDPByzeHEg=ft-xq1AZvNkMw9Fw@mail.gmail.com>
Date: Wed, 19 Jun 2013 11:54:49 -0500
Message-ID: <CAHBDyN6Zfh0nZ53g88nfgNcU3oxEex_6igcVy19Qz1Wv5u4T2A@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "rai@ietf.org" <rai@ietf.org>
Subject: Re: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 16:54:57 -0000

BTW, if you want a real live example as to the extent of the current
problem, just listen to the first 25 minutes of the MMUSIC virtual
interim held this past Monday.

Mary.

On Wed, Jun 19, 2013 at 11:53 AM, Mary Barnes
<mary.ietf.barnes@gmail.com> wrote:
> I'm not Brian but I'll go ahead and respond with my perspective [MB].
>
> Mary.
>
> On Wed, Jun 19, 2013 at 10:54 AM, Ben Campbell <ben@nostrum.com> wrote:
>> Hi Brian,
>>
>> It's not clear to me what scope you intend for the mini-wg. Does it hand=
le the "higher-level constructions"? Is it responsible for breaking the int=
erdependency logjams? Something else?
> [MB] I believe the "higher-level constructions" (which are
> "applications" in my mind) are the responsibility of the group
> chartered to create that solution based on existing protocols as well
> as any new protocols the specific WG deems necessary.  The new mini-WG
> is intended to deal with the solution requirements that may need to
> change existing protocols. [/MB]
>>
>> What keeps the min-wg from becoming the union of all interested parties =
from all the existing wgs? (Or was that what you intended?)
> [MB] The new mini-WG would be the union of all the parties that are
> interested in reusing and changing existing protocols. This doesn't
> impact the existing WGs chartered to define the solution for the
> "higher-level constructions" - this does impact some of the existing
> protocol building blocks that they may need to reuse and extend.
> While we have WGs that are explicitly chartered to define new
> extensions (e.g., MMUSIC for SDP), it's impossible to isolate the
> solution aspects (from the "higher-level construct" WGs) and
> requirements from the extensions that might be needed in the other WG.
>  This gets to be particularly problematic in the case where you have
> two WGs defining new "applications".  The big issue is figuring out
> who is responsible for guiding the work in the existing WG where
> extensions need to be defined.  Again, it's impossible to do the work
> and have sensible discussions without understanding some aspects
> required by the solution (and why they are required). While it's
> tempting for the chairs of the WG where extensions need to be defined
> to suggest that "application" discussions are out of scope, that just
> doesn't work.  By having chairs from all the WGs involved represented
> in the new mini-WG, everyone has "equal stakes" so to speak in
> ensuring that a solution is reached.  Setting a specific deadline is
> extremely helpful as it helps deal with deadlock situations and the
> reality that the new "applications" may not be able to use the same
> extensions, for example.
> [/MB]
>>
>> Thanks!
>>
>> Ben.
>>
>> On Jun 19, 2013, at 8:05 AM, Brian Rosen <br@brianrosen.net> wrote:
>>
>>> Suppose we treated this as a mini-WG
>>> 1. The chairs and ADs work out a charter, with a limited WG time period=
 to discuss. No IESG participation.
>>> 2. One chair is appointed from among the affected WG chairs
>>> 3. A new email list is created
>>> 4. Discussion is held during one of the WG meeting slots.  It can alter=
nate perhaps between the affected groups.  The mini-group doesn't get a slo=
t, but of course it may result in a WG asking for two slots for a particula=
r meeting.
>>> 5. If there are cross AD issues, one AD is selected
>>>
>>> Put a cap on this effort, and make it short - 2 meeting cycles maybe.  =
If they can't agree, then most likely each of the WGs will need to come up =
with their own solutions.
>>> The mini-WG milestone may not be a submitted draft, it could be a matur=
e draft, that would be finished in one of the affected WGs.  It could even =
be a general agreement on the solution, rather than an actual mature draft.=
  At the end, the mail list is closed., further discussion if any happens i=
n the WGs.
>>>
>>> Brian
>>> On Jun 19, 2013, at 3:03 AM, Gonzalo Camarillo <Gonzalo.Camarillo@erics=
son.com> wrote:
>>>
>>>> Folks,
>>>>
>>>> as you know, in the RAI area we have always considered having effectiv=
e
>>>> processes to help us produce relevant and timely specifications a very
>>>> important issue. When our environment has changed, we have sometimes
>>>> modified or fine tuned our processes in order to continue being
>>>> effective. A few examples (among many others) of such changes were the
>>>> introduction of mentors, the old SIPPING process, P headers, and the
>>>> current DISPATCH process.
>>>>
>>>> It is time for us to look at the current state of affairs and discuss
>>>> whether or not we need to do certain things in a different way.
>>>>
>>>> In particular, we currently have a few groups (e.g., RTCWeb and CLUE)
>>>> that work on higher-level constructions, which use elements developed =
in
>>>> other working groups. For example, CLUE could potentially specify a
>>>> mechanism that used mechanisms developed in MMUSIC or AVTEXT such as t=
he
>>>> offer/answer model and a number of RTP extensions.
>>>>
>>>> Note that what we called "higher-level constructions" above are referr=
ed
>>>> to by different names by different people: architectures, applications=
,
>>>> frameworks, etc. It does not really matter how we call them because th=
is
>>>> discussion is not about terminology and it is fairly clear what this
>>>> type of work is about.
>>>>
>>>> The way this type of work is currently done in RAI requires the
>>>> high-level WGs and the WGs developing the individual pieces to
>>>> communicate often. Those communications are not always easy, since
>>>> different WGs sometimes have different views on priorities,
>>>> requirements, use cases, etc.
>>>>
>>>> What we would like to get your feedback on is: do we need a better way
>>>> to handle this type of work in RAI or our current process is as good a=
s
>>>> it gets?
>>>>
>>>> Note that we are interested in getting constructive feedback and ideas
>>>> on how to improve things. Please, focus your feedback on those aspects=
.
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>> (on behalf of both RAI ADs)
>>>>
>>>> _______________________________________________
>>>> RAI mailing list
>>>> RAI@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rai
>>>
>>> _______________________________________________
>>> RAI mailing list
>>> RAI@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rai
>>
>> _______________________________________________
>> RAI mailing list
>> RAI@ietf.org
>> https://www.ietf.org/mailman/listinfo/rai

From michael.hammer@yaanatech.com  Wed Jun 19 10:00:05 2013
Return-Path: <michael.hammer@yaanatech.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E407121F9DCD for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 10:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level: 
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9+S9B5u4k+c for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 10:00:01 -0700 (PDT)
Received: from email1.corp.yaanatech.com (email1.corp.yaanatech.com [205.140.198.134]) by ietfa.amsl.com (Postfix) with ESMTP id 266D021F9DCE for <rai@ietf.org>; Wed, 19 Jun 2013 10:00:01 -0700 (PDT)
Received: from EX2K10MB2.corp.yaanatech.com ([fe80::5d11:66a1:e508:6871]) by ex2k10hub1.corp.yaanatech.com ([::1]) with mapi id 14.01.0218.012; Wed, 19 Jun 2013 10:00:00 -0700
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "mary.ietf.barnes@gmail.com" <mary.ietf.barnes@gmail.com>, "ben@nostrum.com" <ben@nostrum.com>
Thread-Topic: [RAI] RAI processes for handling work effectively
Thread-Index: AQHObLsiUYsTs/DVMEKqA1lf9YZhB5k9dzQAgAAvRACAABB4gIAAAF2A//+LB5A=
Date: Wed, 19 Jun 2013 16:59:59 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB3A03DF0F9@ex2k10mb2.corp.yaanatech.com>
References: <51C157BA.70509@ericsson.com> <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net> <6B7CBDE1-7472-4312-935C-6B7D2284A90F@nostrum.com> <CAHBDyN4UJiWY2KZg2Z2qv7AmDPByzeHEg=ft-xq1AZvNkMw9Fw@mail.gmail.com> <CAHBDyN6Zfh0nZ53g88nfgNcU3oxEex_6igcVy19Qz1Wv5u4T2A@mail.gmail.com>
In-Reply-To: <CAHBDyN6Zfh0nZ53g88nfgNcU3oxEex_6igcVy19Qz1Wv5u4T2A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.17.100.216]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_00C9_01CE6CEC.E7261F40"
MIME-Version: 1.0
Cc: "rai@ietf.org" <rai@ietf.org>
Subject: Re: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 17:00:06 -0000

------=_NextPart_000_00C9_01CE6CEC.E7261F40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Mary,

Your description seems too broad.  Most WGs would see themselves doing what
you describe.

The issue seems to be more architectural, when two or more WGs think that
the subject matter falls within their domain.
So, it seems the mini-WG is there to scale back the scopes of the WGs so as
to make them mutually exclusive.

Mike


-----Original Message-----
From: rai-bounces@ietf.org [mailto:rai-bounces@ietf.org] On Behalf Of Mary
Barnes
Sent: Wednesday, June 19, 2013 12:55 PM
To: Ben Campbell
Cc: rai@ietf.org
Subject: Re: [RAI] RAI processes for handling work effectively

BTW, if you want a real live example as to the extent of the current
problem, just listen to the first 25 minutes of the MMUSIC virtual interim
held this past Monday.

Mary.

On Wed, Jun 19, 2013 at 11:53 AM, Mary Barnes <mary.ietf.barnes@gmail.com>
wrote:
> I'm not Brian but I'll go ahead and respond with my perspective [MB].
>
> Mary.
>
> On Wed, Jun 19, 2013 at 10:54 AM, Ben Campbell <ben@nostrum.com> wrote:
>> Hi Brian,
>>
>> It's not clear to me what scope you intend for the mini-wg. Does it
handle the "higher-level constructions"? Is it responsible for breaking the
interdependency logjams? Something else?
> [MB] I believe the "higher-level constructions" (which are 
> "applications" in my mind) are the responsibility of the group 
> chartered to create that solution based on existing protocols as well 
> as any new protocols the specific WG deems necessary.  The new mini-WG 
> is intended to deal with the solution requirements that may need to 
> change existing protocols. [/MB]
>>
>> What keeps the min-wg from becoming the union of all interested 
>> parties from all the existing wgs? (Or was that what you intended?)
> [MB] The new mini-WG would be the union of all the parties that are 
> interested in reusing and changing existing protocols. This doesn't 
> impact the existing WGs chartered to define the solution for the 
> "higher-level constructions" - this does impact some of the existing 
> protocol building blocks that they may need to reuse and extend.
> While we have WGs that are explicitly chartered to define new 
> extensions (e.g., MMUSIC for SDP), it's impossible to isolate the 
> solution aspects (from the "higher-level construct" WGs) and 
> requirements from the extensions that might be needed in the other WG.
>  This gets to be particularly problematic in the case where you have 
> two WGs defining new "applications".  The big issue is figuring out 
> who is responsible for guiding the work in the existing WG where 
> extensions need to be defined.  Again, it's impossible to do the work 
> and have sensible discussions without understanding some aspects 
> required by the solution (and why they are required). While it's 
> tempting for the chairs of the WG where extensions need to be defined 
> to suggest that "application" discussions are out of scope, that just 
> doesn't work.  By having chairs from all the WGs involved represented 
> in the new mini-WG, everyone has "equal stakes" so to speak in 
> ensuring that a solution is reached.  Setting a specific deadline is 
> extremely helpful as it helps deal with deadlock situations and the 
> reality that the new "applications" may not be able to use the same 
> extensions, for example.
> [/MB]
>>
>> Thanks!
>>
>> Ben.
>>
>> On Jun 19, 2013, at 8:05 AM, Brian Rosen <br@brianrosen.net> wrote:
>>
>>> Suppose we treated this as a mini-WG 1. The chairs and ADs work out 
>>> a charter, with a limited WG time period to discuss. No IESG
participation.
>>> 2. One chair is appointed from among the affected WG chairs 3. A new 
>>> email list is created 4. Discussion is held during one of the WG 
>>> meeting slots.  It can alternate perhaps between the affected groups.
The mini-group doesn't get a slot, but of course it may result in a WG
asking for two slots for a particular meeting.
>>> 5. If there are cross AD issues, one AD is selected
>>>
>>> Put a cap on this effort, and make it short - 2 meeting cycles maybe.
If they can't agree, then most likely each of the WGs will need to come up
with their own solutions.
>>> The mini-WG milestone may not be a submitted draft, it could be a mature
draft, that would be finished in one of the affected WGs.  It could even be
a general agreement on the solution, rather than an actual mature draft.  At
the end, the mail list is closed., further discussion if any happens in the
WGs.
>>>
>>> Brian
>>> On Jun 19, 2013, at 3:03 AM, Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> wrote:
>>>
>>>> Folks,
>>>>
>>>> as you know, in the RAI area we have always considered having 
>>>> effective processes to help us produce relevant and timely 
>>>> specifications a very important issue. When our environment has 
>>>> changed, we have sometimes modified or fine tuned our processes in 
>>>> order to continue being effective. A few examples (among many 
>>>> others) of such changes were the introduction of mentors, the old 
>>>> SIPPING process, P headers, and the current DISPATCH process.
>>>>
>>>> It is time for us to look at the current state of affairs and 
>>>> discuss whether or not we need to do certain things in a different way.
>>>>
>>>> In particular, we currently have a few groups (e.g., RTCWeb and 
>>>> CLUE) that work on higher-level constructions, which use elements 
>>>> developed in other working groups. For example, CLUE could 
>>>> potentially specify a mechanism that used mechanisms developed in 
>>>> MMUSIC or AVTEXT such as the offer/answer model and a number of RTP
extensions.
>>>>
>>>> Note that what we called "higher-level constructions" above are 
>>>> referred to by different names by different people: architectures, 
>>>> applications, frameworks, etc. It does not really matter how we 
>>>> call them because this discussion is not about terminology and it 
>>>> is fairly clear what this type of work is about.
>>>>
>>>> The way this type of work is currently done in RAI requires the 
>>>> high-level WGs and the WGs developing the individual pieces to 
>>>> communicate often. Those communications are not always easy, since 
>>>> different WGs sometimes have different views on priorities, 
>>>> requirements, use cases, etc.
>>>>
>>>> What we would like to get your feedback on is: do we need a better 
>>>> way to handle this type of work in RAI or our current process is as 
>>>> good as it gets?
>>>>
>>>> Note that we are interested in getting constructive feedback and 
>>>> ideas on how to improve things. Please, focus your feedback on those
aspects.
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>> (on behalf of both RAI ADs)
>>>>
>>>> _______________________________________________
>>>> RAI mailing list
>>>> RAI@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rai
>>>
>>> _______________________________________________
>>> RAI mailing list
>>> RAI@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rai
>>
>> _______________________________________________
>> RAI mailing list
>> RAI@ietf.org
>> https://www.ietf.org/mailman/listinfo/rai
_______________________________________________
RAI mailing list
RAI@ietf.org
https://www.ietf.org/mailman/listinfo/rai

------=_NextPart_000_00C9_01CE6CEC.E7261F40
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIRPzCCBBow
ggMCAhEAi1t1VoRUhQsAz684SM6xpDANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNOTkxMDAxMDAwMDAwWhcNMzYwNzE2MjM1OTU5WjCByjELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk
IHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IC0gRzMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDd
hNS5tPmn2PMEeJzePdxsExbZet0kUWbAxyZZDawGCMKU0TMf8IM1H24byN6qbhVOVCfvxG0a7Avj
DvBEpVfHQFgeo0cfcexg9m2UyBg57f5CGFbf5ExJEHhOAXY1YxI23Wa8AQQ2o1Vo1aI2CayrISZU
Bq0/yhTgrMqtBh2V4vid8eBg/8J/dStMzNr+h5kh6rr+PlTX0ll42zxuz6ATABq4J6HkvmeWyqDF
s5zdyXWe6zCaX6PN2a54GT8j6VzbKb2tVcgbVIxj9uim6sc3ElyjKR4C2dsfO7TXD1ZHgRUESq+D
J9HFWIjB3faqp6MY2miqbRFR4b9la5+WdtE9AgMBAAEwDQYJKoZIhvcNAQEFBQADggEBAKtmjdez
useatuZV0AXxnzGNWqrZqkYmD3Htpa1TVmIBRypE6f4/dAsTm7n0TRuy0V+yttKIXLOfzcvUp9lg
lYQ6+ME3HWHK57DF5ZHaVKasMYGul97NCKy4wJeAf25ypOdpE5VlH8STPP15jwTUPk/q957OzWd8
T2UC/5GFVHPH/zb3hi3s0F5P/xGfcgbWuBrxTA0mZeJEgB7Hn+Pd6Ara7KUggGlooU9+4WvPB0H6
g468ON2wLhGxa7JCzJq8+UgieUoZD7IcPiB02WrDvvIoeBNWeU9tUOobsLVXsTdmWCPz3A/fCofE
74YF1TgUYJmjS94GlnEs8tu2H6TvP+4wggZCMIIFKqADAgECAhA4qwAv/66Wt1b/OVr7XecbMA0G
CSqGSIb3DQEBBQUAMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAd
BgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWdu
LCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNz
IDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHMzAeFw0xMTA5MDEw
MDAwMDBaFw0yMTA4MzEyMzU5NTlaMIGmMQswCQYDVQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMg
Q29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBl
cnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFs
IFN1YnNjcmliZXIgQ0EgLSBHNDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMbsJ/0d
Y/Q7HYrB0xzIyIKGtrhKhpKqgVxyyjANL55BIlcwISWQmqP0rCrGiBeGYXITdi7sA8snm48ggDfg
5IraVaZQD/y5XCNpiUKhuh+v7w75pMkK8fg3ssbZkkqufd+4RB+buj+MBv7YI09IUSNqYISo7icv
YN+W8hoqjDyPAMxPy/ogjrw19uHwmrYF8/wdP8YUew7a8gXk04MCpsVpcLSp5Fbp2x1c9KY24mu1
Hiot3L677joEsDAIrV9obMa9BpaIhOfmqWQtvDgwu4gmw2dmZrS0d/nAoccOcu9m4uW5yuDzhXc1
mN7UHLD+ZnHiOMtufE9AVeuX2agYHu0CAwEAAaOCAkQwggJAMDgGCCsGAQUFBwEBBCwwKjAoBggr
BgEFBQcwAYYcaHR0cDovL3BraS1vY3NwLnZlcmlzaWduLmNvbTASBgNVHRMBAf8ECDAGAQH/AgEA
MGwGA1UdIARlMGMwYQYLYIZIAYb4RQEHFwEwUjAmBggrBgEFBQcCARYaaHR0cDovL3d3dy5zeW1h
dXRoLmNvbS9jcHMwKAYIKwYBBQUHAgIwHBoaaHR0cDovL3d3dy5zeW1hdXRoLmNvbS9ycGEwNAYD
VR0fBC0wKzApoCegJYYjaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS1nMy5jcmwwDgYDVR0P
AQH/BAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFWZXJpU2lnbk1QS0ktMi05NzAdBgNV
HQ4EFgQUrfnDk3IttbkoYeSk12DVxApeGgEwgfEGA1UdIwSB6TCB5qGB0KSBzTCByjELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk
IHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IC0gRzOCEQCLW3VWhFSFCwDPrzhIzrGkMA0GCSqGSIb3DQEBBQUA
A4IBAQDWj8Ham4jys2xNH1gvugFRXXTBRujDuHuf1kDx7/8yuolrwA40Q5+kmeak8F1IM2KFhWH+
I4gijGCbK5xlSZTEojgkSKVcpVBLaOliIqeT6Jkibj1buxBCDh9MdUc0VgmP+L2MPPNcu9KWcFRw
Yk3v0RC+nUgsXuyGaweC8D3hJScoLOAWdh6z/eViltKKPV8rrvtcwhO3ZWPLNHZDn9aHmaturZXB
AD9GJ4H/Nd4jDkPcFF8y+cop78JSMPWZ3bmB+DolII2CaPK5IYV0ZgThhjkWMvIt1iqoyd7ZAAJP
4xggxaWBVraV3tOCrfh7Jb5kfC6gunAs+Pl14nRNB22EMIIG1zCCBb+gAwIBAgIQEB3dROkPDT0Q
6QYEc74tcjANBgkqhkiG9w0BAQUFADCBpjELMAkGA1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVj
IENvcnBvcmF0aW9uMR8wHQYDVQQLExZTeW1hbnRlYyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQ
ZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVh
bCBTdWJzY3JpYmVyIENBIC0gRzQwHhcNMTMwNDAxMDAwMDAwWhcNMTQwNDAyMjM1OTU5WjCBzjEu
MCwGA1UEAwwlUGVyc29uYSBOb3QgVmFsaWRhdGVkIC0gMTM2NDg0MjY5NDQ0MzErMCkGCSqGSIb3
DQEJARYcbWljaGFlbC5oYW1tZXJAeWFhbmF0ZWNoLmNvbTEPMA0GA1UECwwGUy9NSU1FMR4wHAYD
VQQLDBVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxHzAdBgNVBAsMFlN5bWFudGVjIFRydXN0IE5ldHdv
cmsxHTAbBgNVBAoMFFN5bWFudGVjIENvcnBvcmF0aW9uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAh2AtKQNowI8ILmNvdcY16moA8CH7hjSvGDNofwWsh4quEfZ6VQGtDhhOjUmW6JVq
719MH8FNJcVr8oAiVaK3nNeJTL2wO68LpgX6tcZ/z22pJoz98wHzgfWf3pfEUYrCqYg2V3m6oe0t
kd+OaeY8DmPVSpG7as0rkoEzeNwCtmpYjkm96mBO6/AQwsowSLbSuqkEGykp1k47KiPBtxhbp2um
IReh94vPrr1O9zXau9oGMvABJjigYQ2e5AhhhDdK8qOkhgkMAJN2nvLqY+VFrnFIsb5noQ/tP2M/
ct9qwRZ5kUaumRqE/XzV3rH8PoacZW/YvcwAp8Gr1ZaHCMRl+wIDAQABo4IC1TCCAtEwDAYDVR0T
AQH/BAIwADAOBgNVHQ8BAf8EBAMCBaAwIAYDVR0lAQH/BBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBTlvYUx4PMlUy6uvceJkDMK4jBDZjAnBgNVHREEIDAegRxtaWNoYWVsLmhhbW1l
ckB5YWFuYXRlY2guY29tMB8GA1UdIwQYMBaAFK35w5NyLbW5KGHkpNdg1cQKXhoBMIIBKwYIKwYB
BQUHAQEEggEdMIIBGTCCARUGCCsGAQUFBzAChoIBB2xkYXA6Ly9kaXJlY3RvcnkudmVyaXNpZ24u
Y29tL0NOJTIwJTNEJTIwU3ltYW50ZWMlMjBDbGFzcyUyMDElMjBJbmRpdmlkdWFsJTIwU3Vic2Ny
aWJlciUyMENBJTIwLSUyMEc0JTJDJTIwT1UlMjAlM0QlMjBQZXJzb25hJTIwTm90JTIwVmFsaWRh
dGVkJTJDJTIwT1UlMjAlM0QlMjBTeW1hbnRlYyUyMFRydXN0JTIwTmV0d29yayUyQyUyME8lMjAl
M0QlMjBTeW1hbnRlYyUyMENvcnBvcmF0aW9uJTJDJTIwQyUyMCUzRCUyMFVTP2NBQ2VydGlmaWNh
dGU7YmluYXJ5MF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9wa2ktY3JsLnN5bWF1dGguY29tL2Nh
XzU2MWMxMDM2OTBjOTdhNjkyNDdhMGVmMDcxYWM4MWFmL0xhdGVzdENSTC5jcmwwbAYDVR0gBGUw
YzBhBgtghkgBhvhFAQcXATBSMCYGCCsGAQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2Nw
czAoBggrBgEFBQcCAjAcGhpodHRwOi8vd3d3LnN5bWF1dGguY29tL3JwYTAqBgpghkgBhvhFARAD
BBwwGgYRYIZIAYb4RQEQAQICBAGGsxcWBTEwOTIyMA0GCSqGSIb3DQEBBQUAA4IBAQAae/er4pfB
TpqK6c/uJ9D8dVJzzNX26akkB8z/29totzbkpFAIlXRh02iNVK+GnsgS1gwu3FOvjgT5M4i+cNxD
vTJVcnZNXns75JUGX3UsWQbtSySrVzQx8lMtwW6nXHM5GlEaY8/jKVpambG2q9OHjmwMTz7I4A+y
KiiGCGdhE23dFOvku6t/oiwqFnXJmb4o75kbVevKEOd34MIj0P7Q8+1mZcNYEUTYKadoPXFyTWnO
2HTMvFcGgdLFKcqb13clWeW3/B5WjdBimpMjbvwi8ZbrhFdp7Y3NLKFSRH8W29rt0LW7zULxii0z
34NGsBkW9w95PLzTsqmKD4Yv5AkIMYIEkjCCBI4CAQEwgbswgaYxCzAJBgNVBAYTAlVTMR0wGwYD
VQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29y
azEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFz
cyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEc0AhAQHd1E6Q8NPRDpBgRzvi1yMAkGBSsO
AwIaBQCgggKrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDYx
OTE2NTk1OFowIwYJKoZIhvcNAQkEMRYEFN9tb615r3Ualnl43ATePpSoZoZDMIGrBgkqhkiG9w0B
CQ8xgZ0wgZowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBFjAKBggqhkiG9w0DBzALBglghkgBZQME
AQIwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEo
MAcGBSsOAwIaMAsGCWCGSAFlAwQCAzALBglghkgBZQMEAgIwCwYJYIZIAWUDBAIBMIHMBgkrBgEE
AYI3EAQxgb4wgbswgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlv
bjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3Qg
VmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJl
ciBDQSAtIEc0AhAQHd1E6Q8NPRDpBgRzvi1yMIHOBgsqhkiG9w0BCRACCzGBvqCBuzCBpjELMAkG
A1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBvcmF0aW9uMR8wHQYDVQQLExZTeW1hbnRl
YyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMT
LlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzQCEBAd3UTpDw09
EOkGBHO+LXIwDQYJKoZIhvcNAQEBBQAEggEATMdO1F8pZFJ0QF17VD1+ULERXH4cDDiFRb91BnlZ
R8Cxzl/XwqIMye8RmFI/MjrMPMESQmiCdGghAByzLfW1U0S6+5NXpyzNVdZxr/F7flsv+preEoCI
JiXybiqwNub6NtpZpF7Z4oY/l2/DlhF1Pk+WvjQsf8/72+/ZHGkOjti0fGmnjiQMobvObr5/jd2q
DFuIQCIrDB47oH8eKNdsedw2tEqFVMuaDwWipZ0ZrnJOjntv4hWPKhxYvA8GRlsm7IA5KXi5qTNd
Gl3IHdFU+YptWUrovAyFzTYjRNc8xlJQRXhxQTHuFXARiw13c9jBdZSIhjW1fsEMfS1SSVvepQAA
AAAAAA==

------=_NextPart_000_00C9_01CE6CEC.E7261F40--

From mary.ietf.barnes@gmail.com  Wed Jun 19 10:09:15 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75FA621F9E0B for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 10:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.339
X-Spam-Level: 
X-Spam-Status: No, score=-103.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEsewSRsnImy for <rai@ietfa.amsl.com>; Wed, 19 Jun 2013 10:09:11 -0700 (PDT)
Received: from mail-qe0-f41.google.com (mail-qe0-f41.google.com [209.85.128.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9901F21F9E04 for <rai@ietf.org>; Wed, 19 Jun 2013 10:09:01 -0700 (PDT)
Received: by mail-qe0-f41.google.com with SMTP id b4so3420271qen.0 for <rai@ietf.org>; Wed, 19 Jun 2013 10:09:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZU7ISk/x/EWqGQpRCJQnX4Sj53AaYO4zGCyOVQVxkYk=; b=P2INA2LfYeHTY6WJYEVMTmsHnSNWW72qaxo7fAbK+UEoMpvD51hLVyW28Fov46338D N2zqnnu/mws09hkHXcprBe76Fd68af483AJOBl9RpRDPj2WltDlEAJmjPKkly3lEqSgt RoRrwTE4Ulc/9UwbcHlSfkxrfGlZOydLZAKNyz8h0XMcE831SV5ScGeTljXFrZLi/cei F5fY0bjDOuwEA11tFo194huZpMRPwTw0WlYSuE5aSjke2ut7YrsSnkTcI4V2oPaL8DEN 99qOwYta4QNAP6CE2m++27sECCpAMP/AAkBFKeXPIc/z0YmL3c/6OlDv0rrCfHd1X4vr ijLA==
MIME-Version: 1.0
X-Received: by 10.224.187.67 with SMTP id cv3mr4614376qab.98.1371661741093; Wed, 19 Jun 2013 10:09:01 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Wed, 19 Jun 2013 10:09:00 -0700 (PDT)
In-Reply-To: <00C069FD01E0324C9FFCADF539701DB3A03DF0F9@ex2k10mb2.corp.yaanatech.com>
References: <51C157BA.70509@ericsson.com> <53BDCCA9-CBC5-4992-BE2D-7A96250202F7@brianrosen.net> <6B7CBDE1-7472-4312-935C-6B7D2284A90F@nostrum.com> <CAHBDyN4UJiWY2KZg2Z2qv7AmDPByzeHEg=ft-xq1AZvNkMw9Fw@mail.gmail.com> <CAHBDyN6Zfh0nZ53g88nfgNcU3oxEex_6igcVy19Qz1Wv5u4T2A@mail.gmail.com> <00C069FD01E0324C9FFCADF539701DB3A03DF0F9@ex2k10mb2.corp.yaanatech.com>
Date: Wed, 19 Jun 2013 12:09:00 -0500
Message-ID: <CAHBDyN45=EmJ800Fi9hFca4un=OeAF8iAbAdn3c5zNWnaD0e9w@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Michael Hammer <michael.hammer@yaanatech.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "rai@ietf.org" <rai@ietf.org>
Subject: Re: [RAI] RAI processes for handling work effectively
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 17:09:15 -0000

On Wed, Jun 19, 2013 at 11:59 AM, Michael Hammer
<michael.hammer@yaanatech.com> wrote:
> Mary,
>
> Your description seems too broad.  Most WGs would see themselves doing what
> you describe.
[MB] Yes, but on a scale that the existing protocol is being much less
impacted and with the WGs doing "application" stuff being much more
discrete solutions. So, we haven't encountered this problem nearly to
the degree we are right now.  Again, listen to the first 25 minutes of
the MMUSIC interim on Monday and consider that there was no conclusion
(yet again) on that topic.  [/MB]
>
> The issue seems to be more architectural, when two or more WGs think that
> the subject matter falls within their domain.
> So, it seems the mini-WG is there to scale back the scopes of the WGs so as
> to make them mutually exclusive.
[MB] I can kind of see your point BUT for that to work, you need a
very clear understanding of what parts of the application can be
removed from scope - if we could do that, we wouldn't have the problem
we do right now. For example, CLUE still hasn't decided how much we
will signal in SDP versus in a specific CLUE channel.  The more we do
in SDP, the more dependency we have on what is being defined in MMUSIC
to support RTCWEB.   I won't even try to explain where RTCWEB is - you
can scan the archives there and see for yourself.
>
> Mike
>
>
> -----Original Message-----
> From: rai-bounces@ietf.org [mailto:rai-bounces@ietf.org] On Behalf Of Mary
> Barnes
> Sent: Wednesday, June 19, 2013 12:55 PM
> To: Ben Campbell
> Cc: rai@ietf.org
> Subject: Re: [RAI] RAI processes for handling work effectively
>
> BTW, if you want a real live example as to the extent of the current
> problem, just listen to the first 25 minutes of the MMUSIC virtual interim
> held this past Monday.
>
> Mary.
>
> On Wed, Jun 19, 2013 at 11:53 AM, Mary Barnes <mary.ietf.barnes@gmail.com>
> wrote:
>> I'm not Brian but I'll go ahead and respond with my perspective [MB].
>>
>> Mary.
>>
>> On Wed, Jun 19, 2013 at 10:54 AM, Ben Campbell <ben@nostrum.com> wrote:
>>> Hi Brian,
>>>
>>> It's not clear to me what scope you intend for the mini-wg. Does it
> handle the "higher-level constructions"? Is it responsible for breaking the
> interdependency logjams? Something else?
>> [MB] I believe the "higher-level constructions" (which are
>> "applications" in my mind) are the responsibility of the group
>> chartered to create that solution based on existing protocols as well
>> as any new protocols the specific WG deems necessary.  The new mini-WG
>> is intended to deal with the solution requirements that may need to
>> change existing protocols. [/MB]
>>>
>>> What keeps the min-wg from becoming the union of all interested
>>> parties from all the existing wgs? (Or was that what you intended?)
>> [MB] The new mini-WG would be the union of all the parties that are
>> interested in reusing and changing existing protocols. This doesn't
>> impact the existing WGs chartered to define the solution for the
>> "higher-level constructions" - this does impact some of the existing
>> protocol building blocks that they may need to reuse and extend.
>> While we have WGs that are explicitly chartered to define new
>> extensions (e.g., MMUSIC for SDP), it's impossible to isolate the
>> solution aspects (from the "higher-level construct" WGs) and
>> requirements from the extensions that might be needed in the other WG.
>>  This gets to be particularly problematic in the case where you have
>> two WGs defining new "applications".  The big issue is figuring out
>> who is responsible for guiding the work in the existing WG where
>> extensions need to be defined.  Again, it's impossible to do the work
>> and have sensible discussions without understanding some aspects
>> required by the solution (and why they are required). While it's
>> tempting for the chairs of the WG where extensions need to be defined
>> to suggest that "application" discussions are out of scope, that just
>> doesn't work.  By having chairs from all the WGs involved represented
>> in the new mini-WG, everyone has "equal stakes" so to speak in
>> ensuring that a solution is reached.  Setting a specific deadline is
>> extremely helpful as it helps deal with deadlock situations and the
>> reality that the new "applications" may not be able to use the same
>> extensions, for example.
>> [/MB]
>>>
>>> Thanks!
>>>
>>> Ben.
>>>
>>> On Jun 19, 2013, at 8:05 AM, Brian Rosen <br@brianrosen.net> wrote:
>>>
>>>> Suppose we treated this as a mini-WG 1. The chairs and ADs work out
>>>> a charter, with a limited WG time period to discuss. No IESG
> participation.
>>>> 2. One chair is appointed from among the affected WG chairs 3. A new
>>>> email list is created 4. Discussion is held during one of the WG
>>>> meeting slots.  It can alternate perhaps between the affected groups.
> The mini-group doesn't get a slot, but of course it may result in a WG
> asking for two slots for a particular meeting.
>>>> 5. If there are cross AD issues, one AD is selected
>>>>
>>>> Put a cap on this effort, and make it short - 2 meeting cycles maybe.
> If they can't agree, then most likely each of the WGs will need to come up
> with their own solutions.
>>>> The mini-WG milestone may not be a submitted draft, it could be a mature
> draft, that would be finished in one of the affected WGs.  It could even be
> a general agreement on the solution, rather than an actual mature draft.  At
> the end, the mail list is closed., further discussion if any happens in the
> WGs.
>>>>
>>>> Brian
>>>> On Jun 19, 2013, at 3:03 AM, Gonzalo Camarillo
> <Gonzalo.Camarillo@ericsson.com> wrote:
>>>>
>>>>> Folks,
>>>>>
>>>>> as you know, in the RAI area we have always considered having
>>>>> effective processes to help us produce relevant and timely
>>>>> specifications a very important issue. When our environment has
>>>>> changed, we have sometimes modified or fine tuned our processes in
>>>>> order to continue being effective. A few examples (among many
>>>>> others) of such changes were the introduction of mentors, the old
>>>>> SIPPING process, P headers, and the current DISPATCH process.
>>>>>
>>>>> It is time for us to look at the current state of affairs and
>>>>> discuss whether or not we need to do certain things in a different way.
>>>>>
>>>>> In particular, we currently have a few groups (e.g., RTCWeb and
>>>>> CLUE) that work on higher-level constructions, which use elements
>>>>> developed in other working groups. For example, CLUE could
>>>>> potentially specify a mechanism that used mechanisms developed in
>>>>> MMUSIC or AVTEXT such as the offer/answer model and a number of RTP
> extensions.
>>>>>
>>>>> Note that what we called "higher-level constructions" above are
>>>>> referred to by different names by different people: architectures,
>>>>> applications, frameworks, etc. It does not really matter how we
>>>>> call them because this discussion is not about terminology and it
>>>>> is fairly clear what this type of work is about.
>>>>>
>>>>> The way this type of work is currently done in RAI requires the
>>>>> high-level WGs and the WGs developing the individual pieces to
>>>>> communicate often. Those communications are not always easy, since
>>>>> different WGs sometimes have different views on priorities,
>>>>> requirements, use cases, etc.
>>>>>
>>>>> What we would like to get your feedback on is: do we need a better
>>>>> way to handle this type of work in RAI or our current process is as
>>>>> good as it gets?
>>>>>
>>>>> Note that we are interested in getting constructive feedback and
>>>>> ideas on how to improve things. Please, focus your feedback on those
> aspects.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Gonzalo
>>>>> (on behalf of both RAI ADs)
>>>>>
>>>>> _______________________________________________
>>>>> RAI mailing list
>>>>> RAI@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/rai
>>>>
>>>> _______________________________________________
>>>> RAI mailing list
>>>> RAI@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rai
>>>
>>> _______________________________________________
>>> RAI mailing list
>>> RAI@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rai
> _______________________________________________
> RAI mailing list
> RAI@ietf.org
> https://www.ietf.org/mailman/listinfo/rai

From mary.ietf.barnes@gmail.com  Thu Jun 20 10:44:26 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E39221F9F4E; Thu, 20 Jun 2013 10:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.433
X-Spam-Level: 
X-Spam-Status: No, score=-102.433 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UgZkMQfH59G3; Thu, 20 Jun 2013 10:44:25 -0700 (PDT)
Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 270AE21F9F5D; Thu, 20 Jun 2013 10:44:25 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id i13so465976qae.20 for <multiple recipients>; Thu, 20 Jun 2013 10:44:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=P7IX4sX1uAhu2G+vBCZNEjrkyxVGl+ZDH1k2KGmIeJw=; b=GcK71ekH2PYbS/1A7+vBcaGimudvirG3kfna3rVnasiNbEaPvYMn+6ElxlgOtkSc13 4eTYArwFpihyCdSU5VanHRDxu4ZybBo7weFx7BusD1dVV/KZCYcaqjeD3N2H0dgzuFlu EwOXkDa0lE/kzZfG5+2B6jq33xzNgDM8nd2OkHTV9Bg9v/WngmwiKmZ/fxKConmlbCeW zqr1XLgwqieoLkCQQ6c4/5FVX8BLvxlZck+QcRncWCJ5NaRktaPudTzuuRgf8CeEE+15 eSdYM8vAm3zI74U90McVJrG24wx5bBms70v/XBzCIj0KxNuyJYVsLFNWKN8T0THyKjqN +cNA==
MIME-Version: 1.0
X-Received: by 10.224.72.203 with SMTP id n11mr10212822qaj.13.1371750264650; Thu, 20 Jun 2013 10:44:24 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Thu, 20 Jun 2013 10:44:24 -0700 (PDT)
In-Reply-To: <20130619221422.22392.12062.idtracker@ietfa.amsl.com>
References: <20130619221422.22392.12062.idtracker@ietfa.amsl.com>
Date: Thu, 20 Jun 2013 12:44:24 -0500
Message-ID: <CAHBDyN6LB3C_5DUrzvjv51Z2Pb101PCT2nPJhz4wYy5spSeksw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "rai@ietf.org" <rai@ietf.org>, DISPATCH <dispatch@ietf.org>, CLUE <clue@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: [RAI] Fwd: NOMCOM 2013 - UPDATE of validated volunteers list so far
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 17:44:26 -0000

Thanks to the RAI folks who have volunteered!  This is a great way to
serve the community.  [Note: I really would volunteer but I can't due
to my IAB role].  The time commitment is most intense towards year
end, but the role of a voting member can be fairly well managed, in
particular since you have a great Nomcom chair this year!

Thanks,
Mary.


---------- Forwarded message ----------
From: NomCom Chair 2013 <nomcom-chair-2013@ietf.org>
Date: Wed, Jun 19, 2013 at 5:14 PM
Subject: NOMCOM 2013 - UPDATE of validated volunteers list so far
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: ietf@ietf.org


Below is the current validated list of volunteers for Nomcom
2013.  If your name has a *, I'm waiting for a message back
from you.

Big thanks to everyone who has volunteered!

Now what are the rest of you waiting for?

We still need quite a few to get up to 200 volunteers.
Please reply and volunteer - include in the email: your
First Name, Last Name, email addresses you've used in the
last few years in registering for IETF meetings, preferred
email address, primary affiliation, and a contact phone
number for use if you're selected.

Thanks,

Allison Mankin
Nomcom 2013 Chair


1 John Scudder
2 Stephen Hanna
3 Wassim Haddad
4 Russ White
5 Stephan Wenger
6 ZHAO Yi
7 Eric Gray
8 Steve Kent
9 Toerless Eckert
10 Alia Atlas
11 Victor Kuarsingh
12 Yizhou LI
13 Gonzalo Salgueiro
14 Gang CHEN
15 Ning KONG
16 Marcelo Bagnulo
17 SHEN Shuo =E6=B2=88=E7=83=81 (Sean)
18 Fernando Gont
19 Glen Zorn
20 Reinaldo Penno
21 Klaas Wierenga
22 Pascal Thubert
23 Mehmet Ersue
24 Ole Troan
25 Jouni Korhonen
26 Giles Heron
27 Gunter Van de Velde
28 Arturo Servin
29 Eric Vyncke
30 Cullen Jennings
31 Tina Tsou
32 Dhruv Dhody
33 Hongyu LI (Julio)
34 Scott Mansfield
35 John Drake
36 Andrew McLachlan
37 Derek Atkins
38 Suhas Nandakumar
39 Eric Rescorla
40 Karen Seo
41 Stig Venaas
42 Stan Ratliff
43 Ignas Bagdonas
44 Peter Yee
45 Donald Eastlake
46 ZHOU Qian (Cathy)
47 Sam Hartman
48 Lixia Zhang
49 Teemu Savolainen
50 Alvaro Retana
51 Terry Manderson
52 Bill VerSteeg
53 Melinda Shore
54 IJsbrand Wijnands
55 Karen O'Donoghue
56 Benson Schliesser
57 Ari Ker=C3=A4nen
58 Fangwei HU
59 Mach CHEN
60 Hui Deng
61 LIU Dapeng
62 Jaap Akkerhuis
63 Magnus Westerlund
64 Zehn CAO
65 Zaheduzzaman Sarker
66 Bhumip Khasnabish
67 Andrew Chi
68 Thomas Nadeau
69 Steven C (Craig) Whilte
70 Orit Levin
71 Sam Aldrin
72 Paul Ebersman
73 Christopher Liljenstolpe
74 Uma Chunduri
75 Suresh Krishnan
76 Varun Singh
77 Ron Bonica
78 Bill (William) Manning
79 Radia Perlman
80 Daniele Ceccarelli
81 Deborah Brungard
82 Kostas Pentikousis
83 Gregory Mirsky
84 Dave Sinicrope
85 Thomas Walsh
86 Zhaohui (Jeffrey) ZHANG
87 Xian ZHANG
88 Mark Townsley
89 Hannes Gredler
90 Brian Trammell
91 Carlos Martinez
92 Peter Koch
93 Daniel Migault
94 Yi (Aaron) Ding
95 Michael Richardson
96 Sohel Khan
97 John Bradley
98 Huaimo Chen
99 Matthew Campagna
100 Keith Drage
101 Chris Bowers
102 Jakob Heitz
103 Tomofumi Okubo
104 Emil Ivov
105 Timothy B. Terriberry
106 JIANG Yuanlong
107 Luigi Iannone
108 Damien Saucez
109 Lou Berger
110 Yana Stamcheva
111 Ond=C5=99ej Sur=C3=BD
112 Marcin Pilarski
113 Michael StJohns
114 Wes George
115 Christian O'Flaherty
116 Uwe Rauschenbach
117 Olafur Gudmundsson
118 Shwetha Subray Bhandari*
119 Tobias Gondrom
120 Christer Holmberg
121 Susan Hares
122 Kiran Kumar Chittimaneni
123 Donald Fedyk
124 Stephen Botzko*
125 Li Xue*
126 John Sauer*
