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

Hector Santos <hsantos@isdg.net> Thu, 01 May 2014 03:05 UTC

Return-Path: <hsantos@isdg.net>
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 798C61A09DD for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 20:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level:
X-Spam-Status: No, score=-102.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 b2ptz6NknR5g for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 20:05:46 -0700 (PDT)
Received: from listserv.winserver.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 882141A09DC for <ietf@ietf.org>; Wed, 30 Apr 2014 20:05:46 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1071; t=1398913538; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=B4mCKTkhggcg7+jWS+AZRu9v8DI=; b=HVj261bs+JhTi7vEWwUR 2kJJ7WY53hBD6meQKUDnFcb0ltH+cImcpLsiKTuPkJkj/5FAwV3AP2YNccdiIA0Q I85fioWqV6WKVN3ejdRNCFXEahLPdrYgV4pfTZJdZFJ6eMhe6gLt8TXj7CWEjpy5 7CUhVT8c87hpiE0EvfBYZyc=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 30 Apr 2014 23:05:38 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2022099389.3.3564; Wed, 30 Apr 2014 23:05:37 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1071; t=1398913441; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=1HZEXjn TwQNWHVnBNk/pAP2p23XIo+KizQdR7UYstFU=; b=ui+Os/MiDM4RWOdM2wwX8DL qa10US++HaCOSMT4X5Ih+gvAJwBl8PfBi2gUnu8vDzFvwzUZSARoy6QHv094kUpj P5O2bwYgr0i201vOp+RLXTZNa/fIRefdSNGdl9Jc+FCwpcwJj3rPajO3w3TLTpFq QOrQysQUeb8EITuOks2I=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 30 Apr 2014 23:04:01 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2041617765.9.13700; Wed, 30 Apr 2014 23:04:01 -0400
Message-ID: <5361B9FF.4020107@isdg.net>
Date: Wed, 30 Apr 2014 23:05:35 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: 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>
In-Reply-To: <5361B341.4000200@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D9mNrYFbC85c-5DCcqX_w83qkh8
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 03:05:51 -0000

On 4/30/2014 10: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.  I'm thinking of
> IPSec, newer DNS features, etc.  I think it's very much
> in the interest of the IETF to have someone around who
> can talk to some of the language standards bodies about
> how to expose protocol features, how to deal with options,
> etc.

Its a good idea, but you have to watch out for a dependency that would 
exclude other languages and also platforms out there, especially with 
higher level languages, server-side scripting languages.  If your 
liaison manager is experienced with many languages, that would be a 
plus. Its a difficult task to manage a multiple language API for 
examples of IETF protocols.  But it can be done.

-- 
HLS