Re: bettering open source involvement

Melinda Shore <> Thu, 28 July 2016 19:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CF9B912D1DC for <>; Thu, 28 Jul 2016 12:52:52 -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 oD5aYR0dqm8l for <>; Thu, 28 Jul 2016 12:52:51 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c00::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 06E5A12D56C for <>; Thu, 28 Jul 2016 12:52:51 -0700 (PDT)
Received: by with SMTP id x72so24985365pfd.2 for <>; Thu, 28 Jul 2016 12:52:51 -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=PrW2/9jpqfJBbCxJJGA9agWuUsTxspT5hOS6HoCF3wM=; b=mKWyPI9j/EAZ06fxATh407LHRWmaf/aOiUs8FALu3efbnI3xPquew0ZNuYTlppOIcL w22dL58uwB6bbAQ62T8B8MkVONxdz0nH1LQep2UOch7AQ25+WrTXDT51tBpxLvtqQlhG pHFEUWQBIYk+dBJhUBVxu8m8/Gqi5/BqHXdDGMVqh/o0+QLbiO4vH5Pf3dIvZ7f7cB1H XsvrJLHAxM7o4jsrCSlQ9bwTeM7F1Pii+wGFN+K+XeY87R5M5UauvID4hnu7muXdPtAj vysPuunnLs8MDQLGc4TdGGUrQSkZMHY3ft/XuL4nLXpAy/E55cXdlGY7JQdIgpNdquyk ryPw==
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=PrW2/9jpqfJBbCxJJGA9agWuUsTxspT5hOS6HoCF3wM=; b=h0SX0Y3DSm8hHqHuzSXqUZ8mCkDobzUwowjrxWNnQSNrVL5cy+/P0CDvahvLmmYlvi 0DF2tfjXoeTw2JQBT81tDJTPQnV6WtO47RPktI18+Exbe13KFZKrguM0EbnDPTlfwZWg 1Ytkrx1BMB3WCUb61Xl8S388PJvasz49nFQEYLI7dfLEfZBInxuEbeZjBN2viYVy58k6 HBrNmhS5I32jNCKvckeE2Qk7VIDkkPLX2dJfiFzIEz84rDz98+EpAFUSZLggdWFiiXGp ycsG8C8iQIx9/XfU29E5Md96EJAsarzeK8B2RM/skFN+twn2CXLozxfHpKxHHZtukEFI WXqg==
X-Gm-Message-State: AEkoousgGpzLLuC3SCd+BKJHnEXgpixZQISioRd3dUuUhULxsNiEtQqd4w08J05+Tu+i2Q==
X-Received: by with SMTP id e11mr62534909pfd.153.1469735570406; Thu, 28 Jul 2016 12:52:50 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local ( []) by with ESMTPSA id o80sm19086262pfa.67.2016. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jul 2016 12:52:49 -0700 (PDT)
Subject: Re: bettering open source involvement
To: Suzanne Woolf <>
References: <> <> <> <>
From: Melinda Shore <>
Message-ID: <>
Date: Thu, 28 Jul 2016 11:52:38 -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=windows-1252; 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: Thu, 28 Jul 2016 19:52:53 -0000

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.