IETF Logo Mail Archive

Re: [Rfcplusplus] A note on tonight's plenary

Adam Roach <adam@nostrum.com> Wed, 18 July 2018 20:06 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: rfcplusplus@ietfa.amsl.com
Delivered-To: rfcplusplus@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E691130FF8; Wed, 18 Jul 2018 13:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 vc5GaXg6ZlNa; Wed, 18 Jul 2018 13:06:15 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 928CF130FDF; Wed, 18 Jul 2018 13:06:15 -0700 (PDT)
Received: from dhcp-8743.meeting.ietf.org (dhcp-8743.meeting.ietf.org [31.133.135.67]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w6IK6B04059606 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 18 Jul 2018 15:06:12 -0500 (CDT) (envelope-from adam@nostrum.com)
To: Heather Flanagan <rse@rfc-editor.org>, Ted Hardie <ted.ietf@gmail.com>
Cc: "Andrew G. Malis" <agmalis@gmail.com>, rfcplusplus@ietf.org, IETF <ietf@ietf.org>
References: <CA+9kkMBcTB=Pqa1SwyCqrqcxaDdXO5unGq_jy1mP+TTFpmK+oA@mail.gmail.com> <CAA=duU1Z9P6JGJpk53YOGF-DLro1C03xUpLFMWjk8d29effOYg@mail.gmail.com> <CA+9kkMD1nev2OG9ePAKr2+s0G0MQGhxMdnjFm3S6PDS=eg21MA@mail.gmail.com> <F72911DA-BFA8-4A91-BD26-CA7EA4AA8B25@rfc-editor.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <a819c946-a747-29a0-b397-a1542c6576fe@nostrum.com>
Date: Wed, 18 Jul 2018 16:06:11 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <F72911DA-BFA8-4A91-BD26-CA7EA4AA8B25@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/7uy7i0PE533oRWKvvRo7JZuAmMw>
Subject: Re: [Rfcplusplus] A note on tonight's plenary
X-BeenThere: rfcplusplus@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: For discussion of the RFC++ BoF proposal and related ideas <rfcplusplus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfcplusplus/>
List-Post: <mailto:rfcplusplus@ietf.org>
List-Help: <mailto:rfcplusplus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 20:06:18 -0000

Thanks for the detailed outline, Heather! I have one bit of feedback.


On 7/18/18 15:34, Heather Flanagan wrote:
> The IETF community can also expect me to be reaching out to see if I 
> can find contacts within some of the big companies that reference our 
> documents to see what they know (or think they know) about RFCs and 
> how they would expect to find out about changes to the series.

In the interest of completeness, I would suggest that such an effort 
needs to include reaching out to the communities associated with 
open-source projects as well.

/a

v2.23.0 | Report a Bug | By Email