Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))

S Moonesamy <> Wed, 11 September 2019 06:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D27C5120814; Tue, 10 Sep 2019 23:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.276
X-Spam-Status: No, score=0.276 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.b=TKG1JeCb; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.b=3Pc0gQM8
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uQhNzvh7PLGd; Tue, 10 Sep 2019 23:24:16 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BDA1512026E; Tue, 10 Sep 2019 23:24:16 -0700 (PDT)
Received: from ([]) (authenticated bits=0) by (8.15.2/8.14.5) with ESMTPSA id x8B6O4S5004767 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Sep 2019 23:24:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail2010; t=1568183055; x=1568269455; bh=6j2L22cpL4Hc+nMGi22XvxZ7eVQ2qOoTVsDjhfQmoD8=; h=Date:To:From:Subject:In-Reply-To:References; b=TKG1JeCbC4+iG0jkixrz/XAFF7KqKl3OQeHGoj3R3BuS1Lw4Z/s0YIRTU4LzVC3rS SzFj1m115fQVKbpGa0cItGcKaUo5WK0teSrmV2yCJHlu8CZzqMtmhfEizpAaAuHFoY MvA4h5SYKNORPb0XHjhBy+M1MRzThnMDD4xDCbqo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail; t=1568183055; x=1568269455;; bh=6j2L22cpL4Hc+nMGi22XvxZ7eVQ2qOoTVsDjhfQmoD8=; h=Date:To:From:Subject:In-Reply-To:References; b=3Pc0gQM8DtLy1y7aHhqFl82f6AY4HvMZy/3m4VJdimRZAMHCadBl7keTaX7WlDd4h nBcgRi2R54/XM2DcZC6D9oWqZJl13lPI2aal+Yr76fKsRJ5WPz5Why5MI7ccYfHpn9 mEuSABOwSPxCZVEWlcJ2sMpDAbDlV7bM+A3YszfY=
Message-Id: <>
X-Mailer: QUALCOMM Windows Eudora Version
Date: Tue, 10 Sep 2019 23:22:43 -0700
From: S Moonesamy <>
In-Reply-To: <156763077985.22753.8206505094680303304.idtracker@ietfa.ams>
References: <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Sep 2019 06:24:18 -0000

Dear Internet Architecture Board,
At 01:59 PM 04-09-2019, IAB Executive Administrative Manager wrote:
>This is an announcement of an IETF-wide Call for Comment on
>The document is being considered for publication as an Informational RFC
>within the IAB stream, and is available for inspection at:
>The Call for Comment will last until 2019-10-02. Please send comments to
> and

The is a misspelled word in last sentence at the bottom of Page 3 of the draft.

There has been a significant discussion of the RFC Editor Model since 
July.  Section 2.1.5 of draft-ietf-iasa2-rfc6635bis-03 was not 
adhered to since several years.  The qualification described in 
Section 2.1.6 does not reflect what would be sought in a person to 
fulfill the role of RFC Series Editor.  The description of the 
oversight role of the RFC Series Oversight Committee, described in 
Section 3.1, is not aligned with what could be envisioned for the RFC Series.

Given the above, it is not judicious to publish 
draft-ietf-iasa2-rfc6635bis-03 as a RFC without an adequate review of 
the draft.

S. Moonesamy