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

Bob Hinden <bob.hinden@gmail.com> Sat, 28 September 2019 00:01 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 423B4120058 for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 17:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.025
X-Spam-Level:
X-Spam-Status: No, score=-0.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 dif0EoFh2Rv3 for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 17:01:23 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 5E583120026 for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 17:01:23 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id a11so4963950wrx.1 for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 17:01:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=L48ebC/91654iifziLsn0OZw1QWJfdrOaxfYQUu4o7U=; b=UR7aCGO/LwQL0lISQM2w7wTxbnjBJTRWADnS3rIDaAruKRsI6M5l7CP6FapNbPmpkd knyEU5tQjJPvS7SHyQBl7Z0yFA+UjyEM3fZ5OzpNL9lP09W/zfWBKUt6KzMEe22sxDVU G+iC+l97bwbfTtAFF38xgU8ZoAPdpWfA1dc3KKiRivQs3xrIJCee1y6LO/LYBf1FmB5N 1Xx7H9Tv1AhPzYiyrtHpzAjSuQulkFoTEezqmR+cbsqoMVyp+je9NFI9bT0np4OHCsXg kd/S23dIhlKshj3Hr0nQFyV9uJDoIvJP2Cl4w036WRoPdk6NM2UJAdBwehpWvspJw6e/ S55A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=L48ebC/91654iifziLsn0OZw1QWJfdrOaxfYQUu4o7U=; b=JP8yc59u/h+Ft/apqtqw1u7wJN8to7sP6m/JeO23u7wtdmrYB0N/haBraX1U/c/WHr +mB1TsjYdHIBDQEuQDU1EUJIlRq3CQJyy9LBTOXUhkzLljXrbDumI4y2V4Me5mx1uMei tcq01nYf/ls6lEXMrTux+/6eAe/cB8c62py+lG6jQaS50TxU71GIhoIL8hcSuERmQURg rybihZB50wHwctvyzXdfOIIRkyOo/OZk/iohj1G59MFh15xUDMq1A5iGd2eqbY70m8DO slnVGqWKFgvgeDop5l3NkJhvEg7zPuDSNAwb6UXUADhT0FFl5xdEY9I7Yn3s0dCxIWML LwxA==
X-Gm-Message-State: APjAAAXYhW0k/ZLDxBV2856N1UpXMWqbxKFugQQ1vhAqjVqIMEYIBzmP AGgzBTL0GwkeQWzq5607DTZKjF++
X-Google-Smtp-Source: APXvYqxuC9KFJXrM2RemiNlAfMq6zWDbh5e7qHPRB89PuJs61lcKxx0EHaR4EDwRYplQHzZ+/HJWJQ==
X-Received: by 2002:adf:f404:: with SMTP id g4mr4623292wro.353.1569628881913; Fri, 27 Sep 2019 17:01:21 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:c13b:9b80:9c0b:6d08? ([2601:647:5a00:ef0b:c13b:9b80:9c0b:6d08]) by smtp.gmail.com with ESMTPSA id n18sm5238816wmi.20.2019.09.27.17.01.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Sep 2019 17:01:21 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <F7DA2F14-1A40-4397-A6AB-51B7E5284CF8@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C4D15426-7F0D-4E56-B31B-7C58A781E4E7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 27 Sep 2019 17:01:17 -0700
In-Reply-To: <6.2.5.6.2.20190910225210.0b9b30a0@elandnews.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, architecture-discuss@ietf.org, iab@iab.org
To: S Moonesamy <sm+ietf@elandsys.com>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com> <6.2.5.6.2.20190910225210.0b9b30a0@elandnews.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/jw4XxyCqMg0q3a-aAhqgmAL2m2o>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Sep 2019 00:01:25 -0000

Hi,

I am the document editor for this version of the document.

> On Sep 10, 2019, at 11:22 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
> 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
>> draft-ietf-iasa2-rfc6635bis-03.
>> 
>> The document is being considered for publication as an Informational RFC
>> within the IAB stream, and is available for inspection at:
>> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
>> 
>> The Call for Comment will last until 2019-10-02. Please send comments to
>> architecture-discuss@ietf.org and iab@iab.org.
> 
> The is a misspelled word in last sentence at the bottom of Page 3 of the draft.

I will fix in the next version.

> 
> 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.
> 

The direction on this draft was to only change parts of the document that related to the change from the IAOC to LLC.

The larger issues with the RFC Editor need to be resolved, but I don’t think the LLC related changes should be delayed until that is complete.   It’s going to take a while in my view.

Thanks,
Bob





> Regards,
> S. Moonesamy
> 
> 
> 
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss