Re: [Gendispatch] I-D Action: draft-rsalz-2028bis-00.txt

Colin Perkins <csp@csperkins.org> Wed, 08 September 2021 22:08 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B7B3A0A63 for <gendispatch@ietfa.amsl.com>; Wed, 8 Sep 2021 15:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
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 iBRj5JO3p5eo for <gendispatch@ietfa.amsl.com>; Wed, 8 Sep 2021 15:08:47 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D5C13A0A5F for <gendispatch@ietf.org>; Wed, 8 Sep 2021 15:08:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=7QrYjiSwtPD5xPyLw0lRdN5wFD9Z28rv+7o+QhfsDjk=; b=Iz9JepS2D57O4aA71wHSQPkG9u OnHJsbfPy7erB56eq1INY1g1gmD6KdUD+cLNButgNz5n3PhbYaSBL0B7y9u9zqqiCSQC8BQrrw6ZP VsijltIdjS/c6YIfkiUG1fhD6eyZV0oKY6QfW0yqwkYfNoVVBJ/wGeK8860W86TsUahn1uaz1BnDO 26dZwCxemokZe5aWVBd+Qh2YJ1ezo2/0FiUMnPkB4Qaf7HWyT+j1TScFN0piSBQ7vn5hXe/Ma7xW6 mMsVOPK2dDdlv1gZJP/vhO8gm0Rv61csFm6DPl83QI8EilZd6xQRuarKljOoLuljrppDti2s28HiI vRs9NSJg==;
Received: from [81.187.2.149] (port=35408 helo=[192.168.0.83]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1mO5kJ-0007JU-TF; Wed, 08 Sep 2021 23:08:44 +0100
From: Colin Perkins <csp@csperkins.org>
Message-Id: <61847102-F995-431C-9F01-91583AD6BA07@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_97BCBB62-A6BB-4EE2-8DCA-BC0FDB9816C4"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Wed, 08 Sep 2021 23:08:38 +0100
In-Reply-To: <163069758337.6471.7554165463937904967@ietfa.amsl.com>
Cc: "gendispatch@ietf.org" <gendispatch@ietf.org>
To: rsalz@akamai.com
References: <163069758337.6471.7554165463937904967@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/bp3kGE1S648q4psuFbfsDwS2VmE>
Subject: Re: [Gendispatch] I-D Action: draft-rsalz-2028bis-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2021 22:08:53 -0000

Hi,

Thanks for preparing this, it’s important to bring the material up-to-date. 

I have some comments about the material on the IRTF in section 4.7. 

I agree that the IRTF follows some of the IETF policies and procedures, but it also diverges from IETF procedures in some significant ways. Saying that it “generally follows” those procedures may give the wrong expectation.

The first paragraph of section 4.7 also states that: "If an IRTF activity generates a specification that is sufficiently stable to be considered for Internet standardization, the specification is processed through the IETF using the rules in this document”. This is not inaccurate, but perhaps over-emphasises the possibility that an IRTF group will produce a specification suitable for standardisation. IRTF outputs are sometimes experimental protocol specifications, but they’re also often research papers.

Section 4.7 continues with: "A Working Group may ask an IRTF Research Group for advice or other input”. This is correct, but it might be worth emphasising that such advice or input has no special status in IETF.

Finally, section 4.7 concludes: " Details of the organization and operation of the IRTF, the ISRG, and its Research Groups may be found in [IRTF]”. Aside from the typo (ISRG should be IRSG), this implies that the reader knows what is the IRSG but that’s not mentioned in this draft.

Given this, I suggest that section 4.7 of this draft could possibly be rephrased as follows (borrowing a lot of text from RFC 2014):

   The IRTF focuses on longer term research issues related
   to the Internet while the parallel organization, the 
   Internet Engineering Task Force (IETF), focuses on the
   shorter term issues of engineering and standards making.

   The products of IRTF research groups are typically research
   results that are published in scholarly conferences and
   journals. Research groups also sometimes develop experimental
   protocols or technologies that may be suitable for possible
   standardisation in IETF. Similarly, IETF working groups
   sometimes ask research groups for advice or other input. 
   Contributions from research groups, however, carry no more 
   weight than other community input, and go through the same
   standards setting process as any other proposal. 

   The IRTF is managed by the IRTF Chair in consultation with the
   Internet Research Steering Group (IRSG).  The IRSG membership
   includes the IRTF Chair, the chairs of the various Research Group
   and possibly other individuals ("members at large") from the 
   research community. Details of the organization and operation 
   of the IRTF, the ISRG, and its Research Groups may be found in
   [RFC 2014], [RFC 4440], [RFC 7418], [RFC 7827].

Cheers,
Colin




> On 3 Sep 2021, at 20:33, Internet-Drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>        Title           : Entitities Involved in the IETF Standards Process
>        Author          : Rich Salz
> 	Filename        : draft-rsalz-2028bis-00.txt
> 	Pages           : 10
> 	Date            : 2021-09-03
> 
> Abstract:
>   This document describes the individuals and organizations involved in
>   the IETF standards process as described in [IETFPROCS].  It includes
>   brief descriptions of the entities involved, and the role they place
>   in the standards process.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-rsalz-2028bis/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-rsalz-2028bis-00.html
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt



-- 
Colin Perkins
https://csperkins.org/