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

Chaitanya Dhareshwar <chaitanyabd@gmail.com> Thu, 01 May 2014 02:28 UTC

Return-Path: <chaitanyabd@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 27D571A09DD; Wed, 30 Apr 2014 19:28:53 -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 EIPXXPJgq8g4; Wed, 30 Apr 2014 19:28:51 -0700 (PDT)
Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 882F31A09D9; Wed, 30 Apr 2014 19:28:51 -0700 (PDT)
Received: by mail-qc0-f175.google.com with SMTP id w7so1313622qcr.20 for <multiple recipients>; Wed, 30 Apr 2014 19:28:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=2RnryNmFC2pwkkG6GJvHXIqg6fn3QJw+cxpFkREG/Fw=; b=hmwph2Or+BF1+r6EIcp6nowSjqXWj2w0ANaSCtAHb3Zecboc4pY4sNnMy8ccV0WTzO fD0EsvKWYqoqWfcGRVQgf13jmBdhZQqUSJxkKGzLCKIYp71vzCkZZe6Okjex2pn4SOYs Qc+NAu9t2+PS74ReZAxBRHq0jQyr+DYqOYv7ugBslUOMzQN2BiE6Pz/kA9eiIYt0AweR PrGesWBefTUXryrztlv6w1aNNNFT7zCiLSJ+5TbzkvzeiOCS5/uZpUImYyHAw1ZpCMuU 6kWtAHuDO1B0x+80T3ixo+II7XXKQhwlNRUqdAznUViiAnR9n2AGPvvg5U9rirflb6Zy wwKg==
X-Received: by 10.224.0.142 with SMTP id 14mr10366505qab.72.1398911329611; Wed, 30 Apr 2014 19:28:49 -0700 (PDT)
MIME-Version: 1.0
From: Chaitanya Dhareshwar <chaitanyabd@gmail.com>
Date: Wed, 30 Apr 2014 19:28:49 -0700
Message-ID: <2576075144611874116@unknownmsgid>
Subject: RE: Call for volunteers for C/C++ API liaison manager
To: Joe Touch <touch@isi.edu>, IAB <iab@iab.org>, IETF Announce <ietf-announce@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wRv2PntgsWdGpbNWWXzbbqAMVKs
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: Thu, 01 May 2014 02:28:53 -0000

+1 Joe.

Chaitanya Dhareshwar

Mobile: +91.9820760253
From: Joe Touch
Sent: 5/1/2014 5:19
To: IAB; IETF Announce
Cc: IETF
Subject: Re: Call for volunteers for C/C++ API liaison manager


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