Re: bettering open source involvement

Melinda Shore <> Fri, 29 July 2016 02:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 774C512D5F4 for <>; Thu, 28 Jul 2016 19:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S2pKSP9YI1Ms for <>; Thu, 28 Jul 2016 19:31:24 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 07F1312B050 for <>; Thu, 28 Jul 2016 19:31:24 -0700 (PDT)
Received: by with SMTP id iw10so26315918pac.2 for <>; Thu, 28 Jul 2016 19:31:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=oLZzt2xIvHPo2h+HjPsaoaf3SH8vBF/xJ8FkzvAd/ck=; b=DKKuynuB2v0qmHMsjwDlXSsKUu7F7WU0e/C7HOwozpR0rLhiLjQsTE+TRFRwUKMGJV UCt6xzZZnMQntI8UP+FF6QniSEkOcz4Z5uSfO7EUyya5/FeH2ml+fhUIukkomruMJwS8 qC1KERJfxnzQhfuA8eCgEgkJJo0HBj2OV2V68dACb/rJwlJUyJYMD2aDmWGl6Mzq2e0o Ci7gJctpsq0LJCbIf/pHFp6SyMYuYz6GSIoGPMuqsnOmujMDpPak1ewGKzbfJIT/z8LV 7WytlHQv/OjWAXqlH+MDOmMMgQm1OhYuz6yNczOD9RbKTAMSmRN7LtoRHgGttj10GYWO UlXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=oLZzt2xIvHPo2h+HjPsaoaf3SH8vBF/xJ8FkzvAd/ck=; b=EZoHIMba8XAs/Maazx86+EWYGFaEp0tp3bjwBpMixz/GAMFaAm/KDyQToLuoGiTlXX DbZG/eARM2abg8oDmlf020/Ptop8bDr23C01Gr3Pmqrbw3mSCH4Ka8iHSQVEBAQs+e9J h+6INzhysxk0CusNjs+Kuopb6AO37lPgz01CCYDCIkYPTgJvKb4Hils/NNlAt3/9cdVq SWeMgcYnCBeUusirv47GfPXSClYsKEI+N8e6iptTR/0AE/xbVwPULlf2e2cHEPL9FzCy XLRohTSJEXhGaUqYaqdZ2onUgAn18ap4VOBT4Kmv604v4KtSmnqmevA4vRSYHpfTFawF Abkg==
X-Gm-Message-State: AEkoout0U/jlH0kbxAlgI9h5Av5fSjc1bilu0v0jZrP606EX4SCPHYiukh1qaK82MDEiOA==
X-Received: by with SMTP id wr6mr64777618pac.147.1469759483624; Thu, 28 Jul 2016 19:31:23 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local ( []) by with ESMTPSA id 9sm20066635pfo.74.2016. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jul 2016 19:31:22 -0700 (PDT)
Subject: Re: bettering open source involvement
To: Brian E Carpenter <>, Suzanne Woolf <>
References: <> <> <> <> <> <>
From: Melinda Shore <>
Message-ID: <>
Date: Thu, 28 Jul 2016 18:31:13 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <>
Cc: IETF discussion list <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 29 Jul 2016 02:31:25 -0000

On 7/28/16 1:06 PM, Brian E Carpenter wrote:
> And there's our problem, right there. Protocols without APIs are
> pretty much useless these days. IPv6 without a socket API would have
> been an abject failure. Without RFC 2133, RFC 2292 and their successors,
> who knows how the POSIX and Winsock support for IPv6 would have turned
> out?

Not specifying APIs in the IETF clearly doesn't mean that
there are no APIs, clearly.

I'm certainly open to the possibility that we start tackling APIs
but I'm not sure it's a terrific idea.  For one thing, we already
have too much work.  For another, I'm not sure we'd produce
particularly good APIs. It's a different skill from developing and
specifying network protocols.  And thirdly, I'm not convinced that the
people implementing our protocols would want IETF-developed APIs.

This is completely subjective but my own sense is that the
#1 problem we have related to open source projects we take years
to produce specifications.