Re: [Udp35] Trying to learn about udp35

Michael Welzl <michawe@ifi.uio.no> Thu, 22 May 2014 09:50 UTC

Return-Path: <michawe@ifi.uio.no>
X-Original-To: udp35@ietfa.amsl.com
Delivered-To: udp35@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B09071A0056 for <udp35@ietfa.amsl.com>; Thu, 22 May 2014 02:50:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtGkuButMLUl for <udp35@ietfa.amsl.com>; Thu, 22 May 2014 02:50:47 -0700 (PDT)
Received: from mail-out5.uio.no (mail-out5.uio.no [IPv6:2001:700:100:10::17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39D061A0169 for <udp35@ietf.org>; Thu, 22 May 2014 02:50:47 -0700 (PDT)
Received: from mail-mx6.uio.no ([129.240.10.40]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1WnPe8-00005u-BW; Thu, 22 May 2014 11:50:44 +0200
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx6.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1WnPe7-0006Th-Gl; Thu, 22 May 2014 11:50:44 +0200
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="iso-8859-1"
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <537DB72F.4030707@gmail.com>
Date: Thu, 22 May 2014 11:50:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DE30253-FE34-4652-8F45-9C590A13BBB0@ifi.uio.no>
References: <CAGD1bZYA4esRRYfSeRjBnJv4pGyRyg3x7xBBd_C=-NfxDD9rpA@mail.gmail.com> <537A3BA5.2070406@gmail.com> <CAGD1bZas6ur_uS=YaPedXqLCaVcxk+kGo=bO+axFQdTJaB5eHw@mail.gmail.com> <E81DA188-091C-4E23-BAC7-09702F9C66E3@trammell.ch> <9F7FA388-3AA3-496F-B727-E2D8872B82C5@ifi.uio.no> <537DB72F.4030707@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-UiO-SPF-Received:
X-UiO-Ratelimit-Test: rcpts/h 9 msgs/h 3 sum rcpts/h 21 sum msgs/h 9 total rcpts 16611 max rcpts/h 44 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-6.1, required=5.0, autolearn=disabled, RP_MATCHES_RCVD=-1.051, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 221F44956448797F7D2F54E189D9CE65717ED36E
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -60 maxlevel 80 minaction 2 bait 0 mail/h: 3 total 5410 max/h 16 blacklist 0 greylist 0 ratelimit 0
Archived-At: http://mailarchive.ietf.org/arch/msg/udp35/UHet-9Cbtk71siTvpqRVOgXbEgQ
Cc: udp35@ietf.org
Subject: Re: [Udp35] Trying to learn about udp35
X-BeenThere: udp35@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Life beyond UDP <udp35.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/udp35>, <mailto:udp35-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/udp35/>
List-Post: <mailto:udp35@ietf.org>
List-Help: <mailto:udp35-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/udp35>, <mailto:udp35-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 09:50:50 -0000

Hi,

First of all, thank you Spencer for sharing this!

More below:

On 22. mai 2014, at 10:37, Spencer Dawkins wrote:

> Hi, Michael (and all),
> 
> I've seen notes from Joe and Brian, but I'm replying to yours.
> 
> The most important thing I've seen someone say is ... please don't stop the analysis work you're doing on piece A, on the TAPS mailing list. We set up a separate mailing list for big-picture noodling about several pieces and how they fit together, so that our conversation here wouldn't be a distraction for TAPS.
> 
> Creating one or more working groups isn't the end game, so let's not be distracted by that, either. Figuring out how to solve an important problem that people have been banging their heads against for a few decades, and get applications to take advantage of transport mechanisms that aren't TCP and aren't UDP so that evolving transport makes a difference to the way the Internet works, is the end game, at least in my mind. We don't need to have a BOF at all, if we can come up with a plan without one.
> 
> If not having a working group creates obstructions, please let us know. For now, TAPS has an e-mail list and can do the analysis work there. You don't have an approved charter yet, but TAPS doesn't need one to talk. You don't need an approved charter to have a design session in Toronto, assuming that you don't need 100 people charging their laptops and reading e-mail in the same room while people make Powerpoint presentations to make progress. If TAPS needs something else to move forward, please tell us.

This seems problematic. I have given this quite some thought now. At first, I thought I'd just create a list of things we need, and we can get going. Here's what came to my mind:

1. Motivation. People need to know the context of what's going on, I need to send them a "formal" email telling them some conclusion after the BoF; right now nobody does anything as everybody is just waiting. By "need to know the context" I mean that TAPS needs to know which RFCs will be produced, with what status. We'd have to refine the charter just to have a plan - e.g. right now we have a number of drafts, what do we do with them? Merge some, kill some? That would depend on the plan, which is the charter. But can we be sure that RFCs are really going to be published, and really get the status we wish for, when it's only a "wish" and not an approved charter? I think not being a WG will leave people unsure about these matters.

- Management. There need to be chairs, ideally not myself.

More about motivation: I recently visited another University which is interested in this work. Being IETF-experienced academics, they could be very helpful in TAPS, and I see them as representative for a larger group of (potential) TAPS participants. When I talked to them about TAPS, their whole take was "isn't the IETF getting obsolete? Will this EVER happen? Aren't we better off just doing research on our own?" but yet they were very interested **BECAUSE** of the prospect of this being a WG, which, to them, is an indication of the IETF really wanting to make a change.

However, if I imagine how they'd react to "this is just a mailing list now, we can meet anyway and perhaps publish RFCs too without being a WG, let's just get work done" then I'm not very hopeful. After all, a WG also comes with a certain visibility that reflects in e.g. project reviews and project proposals written by academics. In other words, being involved in a WG has more value to them (any academic - and academics, I think, could play a valuable role here) than being involved in a less formal activity.

To conclude: you wrote "if not having a working group creates obstructions, please let us know" => frankly, I actually do believe that this approach will create significant disappointment and will let us lose some key people early on. Now I can imagine that WGs can be slow, with too many people involved, discussions ratholing, etc. etc. - but then there is the positive value of a certain visibility, an IETF-approved charter, some trust on behalf of the folks involved that what comes out has at least SOME chance of deployment...  all in all, I do think we really should create a WG, and maybe eliminate slow-ness by just narrowing the charter accordingly.


> I think the TAPS conversation in London was successful in setting a direction. My read is that at least some of the other IESG and IAB members agree with that. I note that TAPS was one of only two topics from the IESG for the joint IESG/IAB session at the retreat a couple of weeks ago, and joint IESG/IAB face-to-face time is precious enough that we don't spend it on stuff that doesn't matter.
> 
> The IAB folk can correct me if I'm wrong, but one of the UDP35 topics is that IAB folk are proposing that the IAB charter a program in this space *in addition to TAPS*, and I would like to see them providing a home for architectural work beyond "here's a protocol spec or two", which is what an IETF working group would provide. I'd like to have the IAB's perspective inform any engineering work the IESG charters in the IETF.
> 
> For the purposes of the UDP35 discussion, I don't want the Saturday afternoon session in Toronto to be the tail that wags the dog. The reason we mention it at all was to let people know we'd like to have that session before everyone books their tickets to arrive Sunday morning:-)
> 
> We need to be talking now, mostly in e-mail. We do need to level-set early in that conversation, and that's harder to do via e-mail. I would like to see a kickoff call among the folks on this mailing list, and sooner rather than later. I hope scheduling it during the week of June 2 is realistic.
> 
> If no one else sends out a doodle poll this week for a kickoff call the week of June , I'll do it Monday.

Sounds all good to me...

Cheers,
Michael

> 
> Does this make sense?
> 
> Thanks,
> 
> Spencer, who will be traveling for the next several hours ... so please, don't wait for me to talk amongst yourselves :-)
> 
> On 05/21/2014 12:05 PM, Michael Welzl wrote:
>> Hi all,
>> 
>> Glad to be onboard!
>> 
>> As for the slide deck, it looks very interesting but it also reminds me of much that we have already discussed in the TAPS effort. Note that this non-WG-forming BOF in London was preceded by a bar BOF, which was preceded by more work ... e.g. we have worked out a draft charter at some point, and agreed to do things pretty similar to what seems to be proposed in these slides. Now surely I'm missing the bigger picture here, but I'd like to make a plea to not go back to square one but instead continue from where things already are at (see https://sites.google.com/site/transportprotocolservices/ ). If this means having a WG-forming BoF in Toronto, then I guess it's about time to get this organized.
>> 
>> I can imagine that we want to do more than what we have written into our charter, but what I'm suggesting is not to wait with piece A of the puzzle just because we in fact want pieces A, B and perhaps C too, and we have to still find out if/how to do pieces B and C. I'm having a hard time imagining that piece A just won't fit, whatever B and C may look like, so why not get A done?!
>> 
>> Cheers,
>> Michael
>> 
>> 
>> On 21. mai 2014, at 12:30, Brian Trammell <ietf@trammell.ch> wrote:
>> 
>>> hi Jana, all,
>>> 
>>> Apologies for silence to date on this point; I'm traveling way too much this month. The basic problem statement is hidden in the slide deck I presented at the IESG/IAB meeting in Cancun, attached. We'll want to have a level setting call (most probably early next week) to expand upon this.
>>> 
>>> Cheers,
>>> 
>>> Brian
>>> 
>>> <udp35-cancun.pdf>
>>> On 20 May 2014, at 19:54, Jana Iyengar <jri@google.com> wrote:
>>> 
>>>> Thanks for the update, Spencer; I'll look for the poll. I would like to make travel arrangements soon, and I'm waiting to hear about when the pre-IETF meeting will be held so that I can book accordingly. I'd like to book soon, so I hope to hear about the schedule soon ... but if nothing's been finalized yet, I understand.
>>>> 
>>>> 
>>>> On Mon, May 19, 2014 at 10:13 AM, Spencer Dawkins <spencerdawkins.ietf@gmail.com> wrote:
>>>> 
>>>> On 05/13/2014 10:47 AM, Jana Iyengar wrote:
>>>> Hello all,
>>>> 
>>>> I'm writing to learn more about udp35 and the secret cabal meeting that is allegedly happening Saturday evening before the IETF. Can someone post a link or some summary of the goals of this group?
>>>> 
>>>> Thanks much!
>>>> - jana
>>>> 
>>>> Hi, Jana,
>>>> 
>>>> If I understood correctly, the plan is that we'll schedule a conference call Real Soon Now to level-set folks, just as soon as someone sends out a doodle poll so we can figure out when :-)
>>>> 
>>>> So, please stay tuned ...
>>>> 
>>>> Spencer
>>>> 
>>>> _______________________________________________
>>>> Udp35 mailing list
>>>> Udp35@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/udp35
>>>> 
>>>> _______________________________________________
>>>> Udp35 mailing list
>>>> Udp35@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/udp35
>>> _______________________________________________
>>> Udp35 mailing list
>>> Udp35@ietf.org
>>> https://www.ietf.org/mailman/listinfo/udp35
>