Re: [Udp35] TAPS BOF and moving the transport API forward

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Mon, 26 May 2014 21:47 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
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 BBE811A02A1 for <udp35@ietfa.amsl.com>; Mon, 26 May 2014 14:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level:
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, SPF_PASS=-0.001] 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 JY6rkoZv7iKq for <udp35@ietfa.amsl.com>; Mon, 26 May 2014 14:47:08 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75A6C1A029C for <udp35@ietf.org>; Mon, 26 May 2014 14:47:08 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id m1so8840793oag.12 for <udp35@ietf.org>; Mon, 26 May 2014 14:47:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=5ZtnePV2DU2gK6S6gPlA7pVmqgZeOh8+vhvco2/efXk=; b=bNngYecQcN2gZKbBTKu9hyufXW4LaEAAviUTCLTOAFixIxeQMEbMAevvlgGHQVB5ZS AALqaFhP69u3wzyq6Prn4mczZuK3NFG3ZyELvvw4cHHhgsgCdQBvKtErEXbm6usZDeiZ 2wvqxAvu6ZzWiRPE2RrnIZwhzKyBjXdKpT2qPHXd2xWC3a9PEguYhMPyJujMsUkCR5Px K+PrxrdMicSFt+BjF3wp6GVRgmqweROlgDgXCJFg6JTlAd1op+ZEhjxCw/rJsrwM4fsH irTVl2P0cWikLo9xy7dR181jtKgU1c7pTpMctKZCbe3E6wuLhwbJdTtHzkS5YhMQKGA+ twOg==
X-Received: by 10.182.214.98 with SMTP id nz2mr1176341obc.62.1401140825362; Mon, 26 May 2014 14:47:05 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id r10sm20386641obf.16.2014.05.26.14.47.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 May 2014 14:47:04 -0700 (PDT)
Message-ID: <5383B657.1060907@gmail.com>
Date: Mon, 26 May 2014 16:47:03 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: udp35@ietf.org
References: <537B6932.9050809@erg.abdn.ac.uk> <537BA5CF.4000602@gmail.com> <2f67fd4139a3a40a2df96f1e7db57a95.squirrel@www.erg.abdn.ac.uk> <537DD281.5030408@gmail.com> <A8BF265F-DAEB-426C-9616-0A60AAD6A35F@ifi.uio.no> <966E90E6-5DD3-4897-8891-9ABBB3203274@trammell.ch> <AF068429-8094-4558-9038-A443377B02DD@ifi.uio.no> <8EC8A658-5FA9-464B-8B09-6D3A94222B13@trammell.ch> <6B4A2FF8-E4BA-4355-B792-F99D8970D9C8@ifi.uio.no> <A2BE43E7-5635-4CA2-9F3A-9CEFD277F283@ifi.uio.no> <64EA69DB-0643-4485-84B6-7440533878E2@trammell.ch> <9c49932c616d4c5ae7195ad035874b82.squirrel@www.erg.abdn.ac.uk> <D2D82A97-5892-45D2-B703-8AA8B5AF071F@trammell.ch> <5383720E.6050400@gmail.com> <B292476A-6A2A-45A1-B7C4-7C4BFC7957DD@trammell.ch>
In-Reply-To: <B292476A-6A2A-45A1-B7C4-7C4BFC7957DD@trammell.ch>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/udp35/blqQmn6lKKSfmrcgZAUjKyp0l4w
Subject: Re: [Udp35] TAPS BOF and moving the transport API forward
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: Mon, 26 May 2014 21:47:09 -0000

On 05/26/2014 04:16 PM, Brian Trammell wrote:
> hi Spencer, all,
>
> a quick response to one point, inline; more later...
>
> On 26 May 2014, at 18:55, Spencer Dawkins <spencerdawkins.ietf@gmail.com> wrote:
>
>>>> My understanding on how and why the
>>>> group meets would depends on understanding more of this thread.
>>> The intention of the meeting on Saturday is more or less to continue the discussion we're having right now, in person, in front of a whiteboard; the format is "by-invitation brainstorming session" as opposed to an IAB workshop, for example, mainly because the whiteboard's there, and larger workshops are less productive per unit time.
>> On openness ... nothing we've talked about is a secret from the community.
> Indeed, the list archives are also open.
>
>> We created this mailing list because we had enough person-to-person e-mail flying around about next steps that we needed one, but this isn't a cabal. The IETF doesn't do that, except in places like Nomcom.
>>
>> The IAB actually can restrict participation - open IAB workshop calls for participation/papers are a relatively recent innovation. So I'm hoping the IAB does consider this to be a workshop, but of course I don't control that ("please do the right thing").
> We're calling the Saturday evening thing a "side meeting" as opposed to a "workshop", as there was no call for position papers or vetting thereof, rather invitation sent to people we figured would have something to say, given where we think the problem lies (if you're on this list, you're invited, apologies if that's not been clear).
>
> To elaborate on what I said in my previous message: the _sole_ reason for doing it this way as opposed to with an open call is to limit the _number_ rather than the _set_ of people in the room, because we know what we have is kind of a vague and uncooked idea, and we would like a chance to talk it over with a small group of knowledgable people who've thought a lot about the space before taking it to the wider community. As we're seeing in this thread, there's a _whole lot_ of overlap with TAPS, and a few ideas we think are architecturally related but which don't quite fit, and we'd like to figure out the best way to get everything that needs to get done to address this problem done.

Brian, thanks for connecting the dots. It is complicated.

I'd like to see _something_ to happen on the IETF side, between now and 
Toronto, without interfering with what the IAB is doing on the bigger 
picture.

That's why I'm encouraging Michael and co-conspirators to propose a 
minimal charter that would allow protocol work to get started.

Just to unmuddle the next muddle - I was hoping that we would have a 
UDP35 conference call really soon, so we can be preparing for the side 
meeting in Toronto, and not be starting from scratch on Saturday 
evening. I expected we'd talk through the notes you sent to the mailing 
list last week, as a starting point.

I had planned to send out a Doodle poll today, so we could get the 
conference call scheduled, but, without interfering with what the IAB is 
doing on the bigger picture am now thinking that you and Joe need to be 
there, so I should start with dates/times that work for you. Could you 
two suggest a few date/times?

Thanks,

Spencer

So, I think