IETF Logo Mail Archive

RE: bettering open source involvement

"MH Michael Hammer (5304)" <MHammer@ag.com> Fri, 29 July 2016 05:51 UTC

Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10FAC12B069 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2016 22:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 oOdRUXOxdCF2 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2016 22:51:57 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.31]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 761C312B035 for <ietf@ietf.org>; Thu, 28 Jul 2016 22:51:57 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES533.agna.amgreetings.com ([::1]) with mapi id 14.03.0266.001; Fri, 29 Jul 2016 01:51:55 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Melinda Shore <melinda.shore@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Suzanne Woolf <suzworldwide@gmail.com>
Subject: RE: bettering open source involvement
Thread-Topic: bettering open source involvement
Thread-Index: AQHR6K32z6qsPvbhXUqzdnc9h24iiKAt7cYAgABwkICAAA6JAIAAGAIAgAAUxQCAAFqYgP//9MYw
Date: Fri, 29 Jul 2016 05:51:55 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B05266E238E@USCLES544.agna.amgreetings.com>
References: <CAA93jw71iUPb4vuFK5sMqo_CQEE9HSkchc9988=98FKUsv_1sw@mail.gmail.com> <CABSMSPUoBGgD6ioiCOScUUEnTUnGiNAYPavONyLpbWzNcRhvsg@mail.gmail.com> <42310584-34a6-5efc-59c3-ff7e7ec77624@gmail.com> <61563BA8-6790-43DE-B670-7040F206B9C9@gmail.com> <d56478d7-ae5c-381b-fd52-ee41d9a56358@gmail.com> <e4c113cd-dd59-5e02-39ff-70cf0896bfd9@gmail.com> <16aa8266-6856-93db-9a10-e3f5f30d2b93@gmail.com>
In-Reply-To: <16aa8266-6856-93db-9a10-e3f5f30d2b93@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.104.254.232]
x-kse-attachmentfiltering-interceptor-info: protection disabled
x-kse-serverinfo: USCLES533.agna.amgreetings.com, 9
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean, bases: 7/29/2016 1:49:00 AM
x-kse-dlp-scaninfo: Skipped
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tzMjK_08rJMKXTSFtdeGihqTOic>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 05:51:59 -0000


> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Melinda Shore
> Sent: Thursday, July 28, 2016 10:31 PM
> To: Brian E Carpenter; Suzanne Woolf
> Cc: IETF discussion list
> Subject: Re: bettering open source involvement
> 
> 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.
>

This! +1000

v2.23.0 | Report a Bug | By Email