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

Alessandro Vesely <vesely@tana.it> Fri, 02 May 2014 12:12 UTC

Return-Path: <vesely@tana.it>
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 0F9221A6F8B for <ietf@ietfa.amsl.com>; Fri, 2 May 2014 05:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.073
X-Spam-Level:
X-Spam-Status: No, score=-3.073 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-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 ZBco7Jg9mTAO for <ietf@ietfa.amsl.com>; Fri, 2 May 2014 05:12:38 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 1D6701A09A5 for <ietf@ietf.org>; Fri, 2 May 2014 05:12:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1399032753; bh=acmBloaMPlykhmyBMfmx8RICj9j+UNU7jyjS9d8XQKg=; l=684; h=Date:From:To:CC:References:In-Reply-To; b=k/edjab2z4AmJLSs20VU6muLT1oh8yTgkXe3H4bxg7CTUG+KLeyNhX5YEFV5IUPXR OYuMIv0PvLlTiWug0wRUN6jW7cMJDbBqmEUPRG6nIzdWCP90kDJRKTu2ppFgm6MbS+ Ye4U9VTcb3KBIQYcYci1j9NVAL+rGBGBoGj2GTa0=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Fri, 02 May 2014 14:12:33 +0200 id 00000000005DC039.0000000053638BB1.00000DB1
Message-ID: <53638BB1.10704@tana.it>
Date: Fri, 02 May 2014 14:12:33 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0
MIME-Version: 1.0
To: 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>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6OyxfamPvUNOFB4fCCnbUwiC6uU
Cc: IAB <iab@iab.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: Fri, 02 May 2014 12:12:39 -0000

On Thu 01/May/2014 04:36:49 +0200 Melinda Shore wrote:
> 
> 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.

+1.  But I don't think the call refers to "language standards".  C and
C++, in particular, don't standardize such fundamental features as
multithreading.  Although it mentioned WG14 and WG21, the IAB call
didn't say ISO/IEC JTC1/SC22 also participates in the Single Unix
Specification, which would seem a more appropriate place for Internet
related APIs.

Ale