Re: The RFC Format docs are now RFCs

"Patrik Fältström " <paf@frobbit.se> Sun, 18 December 2016 14:31 UTC

Return-Path: <paf@frobbit.se>
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 7D8B3129475 for <ietf@ietfa.amsl.com>; Sun, 18 Dec 2016 06:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.801
X-Spam-Level:
X-Spam-Status: No, score=-5.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se
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 z-bjhoXihQjU for <ietf@ietfa.amsl.com>; Sun, 18 Dec 2016 06:31:54 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C57D312941A for <ietf@ietf.org>; Sun, 18 Dec 2016 06:31:53 -0800 (PST)
Received: from [192.165.72.120] (unknown [IPv6:2a02:80:3ffc:0:815e:b546:f9a3:3ca0]) by mail.frobbit.se (Postfix) with ESMTPSA id 6B25922427; Sun, 18 Dec 2016 15:31:50 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1482071510; bh=eRQKIZoP9wai3CWTlJN/uikfN5ji2Dd+yWW5hEk4tI8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mPqUZAe/CH6b6In1R/ZcnQ0guhR1aUiK0WCkmAsOhy+d41QSG24OXnpc15q5fQjIC H1wTUvPB5JgVi1d2eNKMT7XPGI+midHupev0iLzSWmU19rZx5CVYt7Gil50H3fH2fn r3hY4k2khsvK4ZTuYd7GALBicG20HtxjCGUF4kFg=
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Eliot Lear" <lear@cisco.com>
Subject: Re: The RFC Format docs are now RFCs
Date: Sun, 18 Dec 2016 15:31:50 +0100
Message-ID: <7437BAB3-35EF-4CCC-8EB0-F3676641EB16@frobbit.se>
In-Reply-To: <1cc7fa0a-5f4f-0c08-071d-a1a9b1f7aa20@cisco.com>
References: <2530302c-cab3-09b1-6c2d-39c2bd84ecf6@rfc-editor.org> <1cc7fa0a-5f4f-0c08-071d-a1a9b1f7aa20@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_18E66320-5341-44F8-BDA1-8D263FCD87AE_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6072)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Mu54t_fIdWpZUYrTmLxEkUUo7Lk>
Cc: rfc-interest@rfc-editor.org, Heather Flanagan <rse@rfc-editor.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2016 14:31:55 -0000

Well done!!!

   Patrik Fältström ;-)

On 18 Dec 2016, at 10:17, Eliot Lear wrote:

> Congratulations to all!
>
> Eliot
>
>
> On 12/16/16 6:14 PM, Heather Flanagan (RFC Series Editor) wrote:
>>
>> Hello all,
>>
>> The RFC Format requirements documents were published this morning.
>> This represents an enormous amount of work on the part of the RFC
>> Format Design Team, and an enormous amount of patience and feedback
>> from the community. Of course, the work isn't quite done - all of
>> these RFCs will undergo a -bis cycle so we can document the "as built"
>> instead of just the "as proposed." But regardless of the amount of
>> work still to come, this is a big milestone for the project!
>>
>> So, thank you all, and stay tuned for the next steps of code
>> development, testing, and collecting feedback!
>>
>> -Heather Flanagan, RSE
>>
>> The RFC Format Design Team:
>>
>>   * Nevil Brownlee (ISE)
>>   * Heather Flanagan (RSE)
>>   * Tony Hansen
>>   * Joe Hildebrand
>>   * Paul Hoffman
>>   * Ted Lemon
>>   * Julian Reschke
>>   * Adam Roach
>>   * Alice Russo
>>   * Robert Sparks (Tools Team liaison)
>>   * Dave Thaler
>>
>>
>> The RFCs, in suggested reading order:
>>
>>   * "RFC Format Framework " - https://www.rfc-editor.org/info/rfc7990
>>   * "The "xml2rfc" Version 3 Vocabulary" -
>>     https://www.rfc-editor.org/info/rfc7991
>>   * "HTML Format for RFCs" - https://www.rfc-editor.org/info/rfc7992
>>   * "Cascading Style Sheets (CSS) Requirements for RFCs" -
>>     https://www.rfc-editor.org/info/rfc7993
>>   * "Requirements for Plain-Text RFCs" -
>>     https://www.rfc-editor.org/info/rfc7994
>>   * "PDF Format for RFCs" - https://www.rfc-editor.org/info/rfc7995
>>   * "SVG Drawings for RFCs: SVG 1.2 RFC" -
>>     https://www.rfc-editor.org/info/rfc7996
>>   * "The Use of Non-ASCII Characters in RFCs" -
>>     https://www.rfc-editor.org/info/rfc7997
>>   * ""xml2rfc" Version 3 Preparation Tool Description" -
>>     https://www.rfc-editor.org/info/rfc7997
>>