Re: [Edm] Some thoughts on Sep 1 meeting, Issue 1

Vijay Gurbani <> Thu, 10 September 2020 18:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7DD863A0F85 for <>; Thu, 10 Sep 2020 11:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 lyGyTKU1UO1M for <>; Thu, 10 Sep 2020 11:49:55 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5FF063A0F69 for <>; Thu, 10 Sep 2020 11:49:52 -0700 (PDT)
Received: by with SMTP id gr14so10297496ejb.1 for <>; Thu, 10 Sep 2020 11:49:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SBpaAEfvJY2XhjWd/S5zCPGeebiFI5ZoM+83To1Ow5Y=; b=lHWatTdAZjVXk/e/RPKmAeT7cOC7Tp6l4js3i1IWsIPgUz4Ova6JGVi5/o0QWQQg+Y zEnzNtlRHENIe8YbWiJv/UDqtgR8afTnPAwd9VRCcEPEmYxllV/3UZkxRdvT5hei442a rsILV4E0LNKbfoDk9vj7jPaoajcSpe7KqSfox3MeaIAnW9vMyoR+IGA4gl4YXnbqR6I/ fK8A5+p0pLrFVUgVa6Y71DfjcTNOXFmapPjXTfl+XtWJrd/mjZuRfVcnFvNnby9vGrXI 5s5BMQ8Qo09j4NxmbP9hMjWTE9wAVmruBKBct/MyC6BYBDbAJUe3J9EH1ev5/IEOkjJn 1ocA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SBpaAEfvJY2XhjWd/S5zCPGeebiFI5ZoM+83To1Ow5Y=; b=PgV2nW+NBHaU992+MlSsynyrHjFmIb1nVum1JXNUhs6/iNnlZZj/tRrPrjBXHml70H esXrHM2mV4DKaQPsUTp7zTPuK5lJlPGs3LhXzHz/pz5oZr3tlKe3lEnE/E0FYDVeAW5t C8RFMD0ZPcoMxbk+JAeM3JIyJXOyeGRpRT9h8GGD6Tl3w4Kbiu9LDk57UxiCH3Zgt/pS e/kOntQsmWsYfrPyg50CHaqz6+kUkTA5+ao9XenaqrtwUKwSvLTOJ4Sx7uQK67zmolM5 hzfv9Q9rZoNrRAyNSMIrHtglzPN9F2rFNvkDxNSgKFiHgV/iFYpvOLqB91DohKq6mpc6 3rTw==
X-Gm-Message-State: AOAM531uHjXBlqUKx88qXvlxkb6EA2gYl70bVLXoxt/0t1sqSOi34A/w 2T2ATJFhaaixHClsWgQwTWb4sUVyWE9sF3IsobY=
X-Google-Smtp-Source: ABdhPJxJJe6pNXoFNZ5WYvXzbVIlkfL819z1S7idD+/VdPgvYykXv1AINoKu4NEjhwlNE+imEp7Cj4ZOtXB/ZwEQx/8=
X-Received: by 2002:a17:906:edc4:: with SMTP id sb4mr10149542ejb.144.1599763790922; Thu, 10 Sep 2020 11:49:50 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <>
In-Reply-To: <>
From: Vijay Gurbani <>
Date: Thu, 10 Sep 2020 13:49:30 -0500
Message-ID: <>
To: Mirja Kuehlewind <>
Cc:, Spencer Dawkins at IETF <>
Content-Type: multipart/alternative; boundary="0000000000007b870e05aefa0899"
Archived-At: <>
Subject: Re: [Edm] Some thoughts on Sep 1 meeting, Issue 1
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Evolvability, Deployability, & Maintainability \(Proposed\) Program" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 10 Sep 2020 18:50:01 -0000

Dear Mirja: Thanks for your time.  More inline.

On Thu, Sep 10, 2020 at 1:33 PM Mirja Kuehlewind <>

> Just very quickly some points. Having read all RFCs that we have published
> in the four years of my AD time I can tell you that RFC7942 is used form
> time to time. However, it also addresses a different problem then what you
> ask for, namely how do people in the wg know about existing
> implementations.

OK, it is good to know that we are eating our own dog food, albeit in small
portions.  If RFC7942 is in the ballpark, but addresses a slightly
different problem, then perhaps we can see what can be salvaged by an
rfc7942-bis.  The problem of people in the WG knowing about existing
implementations is (I believe) easily solved by anyone participating in a
WG meeting (or list), most should quickly pick up where the most promising
implementations are.  The bigger problem is what about others that do not
participate in the WG deliberations, and more importantly, how to highlight
implementations that tracked the I-D to when it became an RFC, but all of a
sudden, in the post RFC world, there is no clear path for newcomers on how
to find the code.

QUIC decides to use another tool for this purpose; I guess for several
> reason, one being that many implementors in QUIC who have been new to the
> IETF are actually more familiar with GitHub than any IETF procedures.

Right, and the fact that QUIC put this GitHub URL in the I-D itself
underscores my point on why it is important to maintain such links to help
non-IETF implementers by providing them information in the RFC itself.
Especially after the I-D becomes an RFC.

> My expectation is that note you mentioned for QUIC will be removed before
> publication as RFC.

That would be a tremendous loss of information for the non-IETF development
community.  I am sure some will stumble on the QUIC GitHub, and I am
equally sure that many will not.  I am arguing to make such an informal
tie-in more explicit and institutionalized.


- vijay