Return-Path: 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 7B70512D56D for ; Thu, 28 Jul 2016 13:20:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 7tXqlwdC4z3P for ; Thu, 28 Jul 2016 13:20:49 -0700 (PDT) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60D6B12D1D0 for ; Thu, 28 Jul 2016 13:20:48 -0700 (PDT) Received: by mail-lf0-x234.google.com with SMTP id b199so57479475lfe.0 for ; Thu, 28 Jul 2016 13:20:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=a//8VcT8PcZycQ/BD1WkQg6Kf9+HGr0WAANF+NIvvvo=; b=JPw+8xZGNxrPeAwtsLaXPuVGEQ2IfR0otVLXm3EdEtSwHOt7CXEfzUcJ/WgcAMIm6q qIzF4fFCUPlb2Fj3sWxmWvE+77m9dVGV0R4lRKl47YXwl1SpWOexe8v0Tk/JJ3FmiYuw yRPjPJ3pSRRpMmZpKq9Md2q48GoU3rICqxzSsAdETkpRvblF/yRPVFQ6iQjuGLjpsK0x 6zYMLq+YuBUzcolXZsjFlvCSn1NyUHrNucthFNw4BOK65foYvYDRHAPjs6+h2oa07Kqb AaIXFawUdYSHDxtmleq8TM9G0OmZkIR3Hx2meFvz6cEr0tTce7BzrO9gCIg/iJPbr/k1 N5tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=a//8VcT8PcZycQ/BD1WkQg6Kf9+HGr0WAANF+NIvvvo=; b=in0PnVtylngU6Yj8N8jR7jorqOVkFYusXL4etTuywqpDCEJPzw5ZSS8tbRH5+rcHF7 sT/ypP5tTmTN2seIox/GW1dJOf+MgOcDuRO10UNtBNrPyoLjI7HGKRvxlwXTZlQrs4rP JqWgthXcR4RYhRm69OdduCxbbSVehPM34+cS24l7eo05IV+mGwCYIhM5gmy8mH/KBLU6 1Aq5hXqiHA6VkASNHWMkoWQ1rbauvuK8+22nnRfKeqqzb3lnGvpRMawWnecyf0jfBAqD dMKJ97tc1D2PJsckG57PfRJ3AZfuo+HZIAgPomxQE8RqRzHi6gqSHbvGi3dMayxZoLgg fRVg== X-Gm-Message-State: AEkoouu5FZGim7z+MOhYMQJWvqLH2TGvttja345Ud64HVguwlaXELaMp7bhiQb5AA1QRxLO++3wNEwZi9HecrA== X-Received: by 10.46.69.193 with SMTP id s184mr3700547lja.29.1469737246059; Thu, 28 Jul 2016 13:20:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.144.83 with HTTP; Thu, 28 Jul 2016 13:20:45 -0700 (PDT) In-Reply-To: References: <42310584-34a6-5efc-59c3-ff7e7ec77624@gmail.com> <61563BA8-6790-43DE-B670-7040F206B9C9@gmail.com> From: Riccardo Bernardini Date: Thu, 28 Jul 2016 22:20:45 +0200 Message-ID: Subject: Re: bettering open source involvement To: IETF discussion list Content-Type: multipart/alternative; boundary=001a114b107c76ef9b0538b7de95 Archived-At: X-BeenThere: ietf@ietf.org 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: Thu, 28 Jul 2016 20:20:50 -0000 --001a114b107c76ef9b0538b7de95 Content-Type: text/plain; charset=UTF-8 A seemingly OT question (but it has its reasons): there is an URL (or something) that I can give to someone as a "pointer" to this thread? On Thu, Jul 28, 2016 at 10:04 PM, MH Michael Hammer (5304) wrote: > I think another issue is the speed at which IETF working groups move and > the speed at which many open source projects move. > > Mike > > > -----Original Message----- > > From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Melinda Shore > > Sent: Thursday, July 28, 2016 3:53 PM > > To: Suzanne Woolf > > Cc: IETF discussion list > > Subject: Re: bettering open source involvement > > > > On 7/28/16 10:26 AM, Suzanne Woolf wrote: > > > As an aside, DNS is one of the areas where there's actually a pretty > > > active give-and-take between standards and open source development-- > > > some of the leading implementations of the protocol are open source > > > and have been for years, and there's been enormous benefit in an open > > > "code to current spec; test multiple implementations; debug; revise > > > code; revise spec" cycle for DNSSEC some years ago or some of the > > > DPRIVE work more recently. > > > > Well, the PyCon thing took more the form of outreach to the > > application/systems programming community, who were not aware of some > > of the issues that the IETF has been working on for years. Many of these > > technical communities tend to be less familiar with network plumbing > issues, > > even those that have significant (if indirect) impact on them, or that > could > > help them solve problems they're facing in their applications. > > That the IETF does not do APIs is pretty much a matter of both faith and > > practice, but there are groups out there implementing IETF protocols and > > providing the APIs that allow application developers to use those > protocols > > and services. > > That is part of the open source landscape, as well. > > > > Melinda > > --001a114b107c76ef9b0538b7de95 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
A seemingly OT question (but it has its reasons): there is= an URL (or something) that I can give to someone as a "pointer" = to this thread? =C2=A0

On Thu, Jul 28, 2016 at 10:04 PM, MH Michael Hammer (5304)= <= MHammer@ag.com> wrote:
I th= ink another issue is the speed at which IETF working groups move and the sp= eed at which many open source projects move.

Mike

> -----Original Message-----
> From: ietf [mailto:ietf-bounc= es@ietf.org] On Behalf Of Melinda Shore
> Sent: Thursday, July 28, 2016 3:53 PM
> To: Suzanne Woolf
> Cc: IETF discussion list
> Subject: Re: bettering open source involvement
>
> On 7/28/16 10:26 AM, Suzanne Woolf wrote:
> > As an aside, DNS is one of the areas where there's actually a= pretty
> > active give-and-take between standards and open source developmen= t--
> > some of the leading implementations of the protocol are open sour= ce
> > and have been for years, and there's been enormous benefit in= an open
> > "code to current spec; test multiple implementations; debug;= revise
> > code; revise spec" cycle for DNSSEC some years ago or some o= f the
> > DPRIVE work more recently.
>
> Well, the PyCon thing took more the form of outreach to the
> application/systems programming community, who were not aware of some<= br> > of the issues that the IETF has been working on for years.=C2=A0 Many = of these
> technical communities tend to be less familiar with network plumbing i= ssues,
> even those that have significant (if indirect) impact on them, or that= could
> help them solve problems they're facing in their applications.
> That the IETF does not do APIs is pretty much a matter of both faith a= nd
> practice, but there are groups out there implementing IETF protocols a= nd
> providing the APIs that allow application=C2=A0 developers to use thos= e protocols
> and services.
> That is part of the open source landscape, as well.
>
> Melinda


--001a114b107c76ef9b0538b7de95--