Re: bettering open source involvement

Alia Atlas <> Mon, 01 August 2016 14:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D9F3A12D599 for <>; Mon, 1 Aug 2016 07:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Status: No, score=-102.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, USER_IN_WHITELIST=-100] 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 6-yoX1MA5o1s for <>; Mon, 1 Aug 2016 07:07:22 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1561112D864 for <>; Mon, 1 Aug 2016 07:04:21 -0700 (PDT)
Received: by with SMTP id u25so104427047qtb.1 for <>; Mon, 01 Aug 2016 07:04:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n2ldTWfbsX/yZGRR1/1VSArbaiWHZXh74Bany64QENw=; b=eDmgkECqkECs2nJx4U7MMstIkVouIZsevdx2CnSEApB75Gr6U1jcLjz22BSXzPrhip vXBxpxTPlM2jgCjQIsmkCh1wKImwsK5sg7R0ZY2wYDf/eqNhlYK5k0eLs1KkOj4RF1DN SgbeIXAeqQFlj6Hh2hurD5FTaO53g2jO/NShIHFNc8/psx6L/1cqZX4cjyrllHr8eJUL hx9eVCEaxxtF5jeg8r3c7DEJqCdndu/KxkfBdqk9Pzz2ij+R95GcZiTEyH8K8RRFMNqG FrVwTZO0AmF6CCF6lvXzv7fAo8em3mIbCK7C5F3b7yBme4WnfoSSgOkOvinGclGcrlAt UoCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n2ldTWfbsX/yZGRR1/1VSArbaiWHZXh74Bany64QENw=; b=d+KLA7epXpfe6AjNUEifOslz5CWgN5Vvl21nVa3hTPHWAvY7HwlIozPzAvaYwtKBp9 Aupj1Ov3FcA/wWY3KaRKxXnFZZqVcSjvaj83W10qW/emGfmljPRscCK770Ogc8OlrKJq wfW3cY/cuynqko93yMcEd5ZqxD0sO0+LD6u+1o2SOmSALCN9xgRbUmnjfgDhuydvfJaO RaTT4aqijfcrMAS9KoepUk6wQzy6B2TqT/sPcdqPfu1Yd2Pv26Qk5QPS0jvPviONuJkj dNLcxum5FGmzpHInIX2iC8dSdhHERmi9Cgndjmot2kbVGKT7slREYUPfA9PtnyrAlCkX mGqg==
X-Gm-Message-State: AEkoout59jblj3fZXDvMt+gcheCWoSNaWfG6r46gLiPoitCtxvqcLqYHsqqwMi7os3v4K33+DtgnGAoZvvQX4A==
X-Received: by with SMTP id z36mr88190686qtb.5.1470060260145; Mon, 01 Aug 2016 07:04:20 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 1 Aug 2016 07:04:18 -0700 (PDT)
In-Reply-To: <>
References: <> <> <>
From: Alia Atlas <>
Date: Mon, 1 Aug 2016 10:04:18 -0400
Message-ID: <>
Subject: Re: bettering open source involvement
To: "Livingood, Jason" <>
Content-Type: multipart/alternative; boundary=001a11441d5e9ac85e05390313bb
Archived-At: <>
Cc: IETF Discussion Mailing 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: Mon, 01 Aug 2016 14:07:27 -0000

On Mon, Aug 1, 2016 at 9:44 AM, Livingood, Jason <> wrote:

> It is an interesting question on how the IETF will evolve. For example, at
> Bits & Bites, my team demonstrated a measurement system called XMAP that is
> based on the emerging IETF LMAP standards. We intend to open source that
> software, and use some hackathons to improve it in the next year or so. As
> it stands now, we’ll either use our own public code repository or partner
> with another organization (that may also have things like an ability to
> accept funds to continue support of the effort). What if, in some future
> state, a given working group had a code repository and the working group
> was chartered not just with developing the standards but maintaining
> implementations of the code?

Some WGs do already have github repositories that they use - and not just
for managing drafts.

I do think that there is a balance between what is ready for
standardization and what is still more experimental - but getting back to
having more experimental work that is backed by code could be helpful.

One concern would be keeping multiple implementations really happening and
also being clear on what are implementation choices versus interoperable

I think it is worth exploring more in this direction, while also
acknowledging that there is still and will continue to be a lot of
proprietary code that depends on IETF standards.


> Jason
> On 7/28/16, 4:30 PM, "ietf on behalf of Octavio Alvarez" <
> on behalf of> wrote:
>     On 07/28/2016 01:56 AM, Dave Taht wrote:
>     > At both ietf and BBF this past week a frequent topic of conversation
>     > was how to get more open source involvement in standards orgs...
>     Hi.
>     Do you mean "how to get open source implementations of IETF standards"
>     or "open source people gathered at IETF conferences" or something else?
>     Thanks.