Re: Call for volunteers for C/C++ API liaison manager

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Thu, 01 May 2014 04:36 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C06A1A09B9 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 21:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 1MYLhAENpgle for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 21:36:22 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD191A0851 for <ietf@ietf.org>; Wed, 30 Apr 2014 21:36:22 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id wp4so3115846obc.7 for <ietf@ietf.org>; Wed, 30 Apr 2014 21:36:20 -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=9ASixMOHUZk9lySt/N8bSRGAU4KcsapIwvWSbxc6L4w=; b=zHisvHkmyxwM41zSAT+AeM+Wq0MOrZImRUCM1s+rZhdWAUXq3nSNjfEcITUTj0F3Nb /wD0Tgz9zIlAhEllJCXq3U3T2847YHscEXJkuWvpCs8nzX6DLWXip3cHZK5NbwcyLvmT npurpVFQaUDHpI0H+D14wqZpQo3YiBKn7PVWt/vXARE+9U0EtASrSDmR8FhQZxiY/81a Go/Icv9n8B/gjrgti8hhnohIgcsMuUL4rHUUYczXCH69ob/4uVai67PR0JH4dO3zTO/2 ABSfNJ2iU8wLS2cdM0GGPg81s8mWgWH4fomziM11IbKuaz8+XCkEUDKjWJpXicAR9sT/ qsJA==
X-Received: by 10.60.115.129 with SMTP id jo1mr9300001oeb.0.1398918980770; Wed, 30 Apr 2014 21:36:20 -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 zc8sm56610512obc.1.2014.04.30.21.36.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Apr 2014 21:36:20 -0700 (PDT)
Message-ID: <5361CF41.3030105@gmail.com>
Date: Wed, 30 Apr 2014 23:36:17 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Call for volunteers for C/C++ API liaison manager
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org> <53618BDD.1080900@isi.edu> <5361B341.4000200@gmail.com> <5361BDC2.9020409@isi.edu>
In-Reply-To: <5361BDC2.9020409@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3NsCac2CBMBvA7syTTY1lf4KEfs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 04:36:24 -0000

On 04/30/2014 10:21 PM, Joe Touch wrote:
>
>
> On 4/30/2014 7:36 PM, Melinda Shore wrote:
>> On 4/30/14 3:48 PM, Joe Touch wrote:
>>> (that doesn't preclude the benefit of a liason to a language-standards
>>> group, but we shouldn't be seeing IETF proposals for such instances 
>>> IMO).
>>
>> Probably not, but it seems pretty clear that deployment
>> of some IETF protocols has suffered from either the lack
>> of a comprehensive API, or crappy API.
>
> +1
>
> However, somewhere along the line, AFAICT the IETF started thinking of 
> protocol APIs as language implementations, and decided (rightly) that 
> the latter was out of scope, and threw the baby out with the bathwater.
>
> IMO, a protocol is *incomplete* without its protocol API.

FWIW, Martin and I understand this, and that's one of the points I've 
been stressing about the IETF 89 TAPS BOF.

I'd like to throw the baby back in. The bathwater can stay gone.

Spencer, who is really disturbed at the word picture he just drew ;-)