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

Joe Touch <touch@isi.edu> Wed, 30 April 2014 23:48 UTC

Return-Path: <touch@isi.edu>
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 B61F21A6F65; Wed, 30 Apr 2014 16:48:52 -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 Q47huSdCK_sd; Wed, 30 Apr 2014 16:48:51 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA1A1A6F63; Wed, 30 Apr 2014 16:48:51 -0700 (PDT)
Received: from [128.9.184.196] ([128.9.184.196]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s3UNmi5T001440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 30 Apr 2014 16:48:44 -0700 (PDT)
Message-ID: <53618BDD.1080900@isi.edu>
Date: Wed, 30 Apr 2014 16:48:45 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IAB <iab@iab.org>, IETF Announce <ietf-announce@ietf.org>
Subject: Re: Call for volunteers for C/C++ API liaison manager
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org>
In-Reply-To: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MXwgClJez2WOeHlS5tkDx09y2nk
Cc: IETF <ietf@ietf.org>
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: Wed, 30 Apr 2014 23:48:53 -0000

On 4/30/2014 8:20 AM, IAB Chair wrote:
> We often see proposals for APIs (most commonly C APIs) discussed in
> the IETF.

A protocol "API" isn't language-specific; it describes (or ought to) the 
upper and lower layer interactions, e.g., as was done in RFC793.

When we propose an API in the IETF, it should be for that protocol API, 
not for a language API (which is an instance, specific to a language and 
also often an OS, of that protocol API).

(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).

Joe