Re: [Iasa20] Adam Roach's Yes on draft-ietf-iasa2-rfc2031bis-05: (with COMMENT)

"Livingood, Jason" <Jason_Livingood@comcast.com> Thu, 22 August 2019 19:32 UTC

Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB25F120B17 for <iasa20@ietfa.amsl.com>; Thu, 22 Aug 2019 12:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=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=comcast.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 f-pqDJxx-8bY for <iasa20@ietfa.amsl.com>; Thu, 22 Aug 2019 12:32:32 -0700 (PDT)
Received: from copdcmhout01.cable.comcast.com (copdcmhout01.cable.comcast.com [162.150.44.71]) (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 0093D120AF7 for <iasa20@ietf.org>; Thu, 22 Aug 2019 12:32:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=comcast.com; s=20190412; c=relaxed/simple; q=dns/txt; i=@comcast.com; t=1566502332; x=2430415932; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=FfklhIBR50lZwmnxDYO7MoP9ThDSyfpWlR+PWRTWaYc=; b=uTLivwNQGIJfEVy2ZzQZxIqDl0z53WemTMrSadush9VMD6JLIlh1iQmjzKztto77 gAnApVhsPIC7Lw5QVd653TrcG5MFgW59UESlO3RftKjiHqroWP6u7TKYjde25Xfe KYn+ecgWsIb/0/3GzFKitj0iUpJa2OPfkBc1w09KfOgm2amh59zABoa/6Ij6cPvp DiAcAUwynogs1YVqgiWOksEXYAJJziYEaKOqpXoQDFYRxPa2Io8z4ckuZ9zUg6V0 1tjVj61Yl0nBNAp7oJityyboYFAZoA2Uz833tQFdfTMz/e8tDXlk8te9YM8sqUAj hQrBvLTA9BQ+lFas/7NmuQ==;
X-AuditID: a2962c47-a9fff7000002e144-9a-5d5eedbc5158
Received: from COPDCEXC38.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by copdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 9A.5C.57668.CBDEE5D5; Thu, 22 Aug 2019 13:32:12 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC38.cable.comcast.com (147.191.125.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 22 Aug 2019 15:32:28 -0400
Received: from COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94]) by COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1713.008; Thu, 22 Aug 2019 15:32:28 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-iasa2-rfc2031bis@ietf.org" <draft-ietf-iasa2-rfc2031bis@ietf.org>, Jon Peterson <jon.peterson@neustar.biz>, "iasa2-chairs@ietf.org" <iasa2-chairs@ietf.org>, "iasa20@ietf.org" <iasa20@ietf.org>
Thread-Topic: Adam Roach's Yes on draft-ietf-iasa2-rfc2031bis-05: (with COMMENT)
Thread-Index: AQHVVwWZDs6U+wVaZkaArIXWahMjsacHkp2A
Date: Thu, 22 Aug 2019 19:32:28 +0000
Message-ID: <83A5F665-FE3C-40F6-AD80-31E89A79479F@cable.comcast.com>
References: <156627095730.5187.6096483491684286207.idtracker@ietfa.amsl.com>
In-Reply-To: <156627095730.5187.6096483491684286207.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1c.0.190812
x-originating-ip: [68.87.29.10]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4CC9E2367D40AC4CA733EE4FCA8D613B@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrAKsWRmVeSWpSXmKPExsWSUDRnsu6et3GxBpP/iVns+buI3WL7gdeM Fr13v7NbLJm+kclixp+JzBZnGiwd2DyWLPnJ5LGj4Tmzx6ydT1gCmKMaGG1KMopSE0tcUtNS 84pT7bgUMIBNUmpaflGqa2JRTmVQak5qInZlIJUpqTmZZalF+liN0cdqTkIXU8aXhuiCSzIV OxdNYmlg/CLdxcjJISFgInF03QnmLkYuDiGBI0wSy2YtZoNwWpgk9qyczwrhnGaU+HXtAytI C5uAmcTdhVeYQWwRAWuJ080nwdqZBa4xSuz7+54NJCEsEChx/OtmJoiiIIm5X55A2UYSz2dC DGIRUJX4s3MKO4jNK+AisfHpX7ChQgI+EttndoHN4RTwlXhxdg5YnFFATOL7qTVgc5gFxCVu PZnPBPGDgMSSPeeZIWxRiZeP/4HNFxXQl1jyYzMrRFxe4siEfyxdjBxAvZoS63fpQ4yxkrhw bQorhK0oMaX7IdQ5ghInZz5hgWgVlzh8ZAfrBEbJWUg2z0KYNAvJpFlIJs1CMmkBI+sqRl5D MyM9Q1MDPRMTPXPDTYzAdLVomo77DsYP52MPMQpwMCrx8Lo+j4sVYk0sK67MPcQowcGsJMJb NhEoxJuSWFmVWpQfX1Sak1p8iFGag0VJnPduV2yskEB6YklqdmpqQWoRTJaJg1OqgXG7QZTE PP6tT6wzFyoeelul+LHR+cybvsj5Yau83l9T+R7S2OMVJPt4UbzkLa7kOfu/zdW5/cQk0eku R4bNVAurs71RLA8P/Hc9eU+s+qpAzmzra7uOTjqwuMr00d603Ojsgoy0D+GpRz8G73xXpmag 8ifY7H/ajxmTd6Ts2Wt/3NTFlHvj939KLMUZiYZazEXFiQCrHh0MUwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/ldK6OTNs4pp_3MXofS2cTGp6Qqg>
Subject: Re: [Iasa20] Adam Roach's Yes on draft-ietf-iasa2-rfc2031bis-05: (with COMMENT)
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2019 19:32:35 -0000

Changes to be made to a -06 update shortly.
Thanks!!
Jason

On 8/19/19, 11:16 PM, "Adam Roach via Datatracker" <noreply@ietf.org> wrote:

    Adam Roach has entered the following ballot position for
    draft-ietf-iasa2-rfc2031bis-05: Yes
    
    When responding, please keep the subject line intact and reply to all
    email addresses included in the To and CC lines. (Feel free to cut this
    introductory paragraph, however.)
    
    
    Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
    for more information about IESG DISCUSS and COMMENT positions.
    
    
    The document, along with other ballot positions, can be found here:
    https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc2031bis/
    
    
    
    ----------------------------------------------------------------------
    COMMENT:
    ----------------------------------------------------------------------
    
    Thanks for a clear, easy-to-read document. I have two small comments.
    
    ---------------------------------------------------------------------------
    
    §1:
    
    >  This led to documenting
    >  things such as the IETF standards process [RFC2026], the IETF
    >  organizational structure [RFC2028], the IETF Nominating Committee
    >  (NomCom) procedures [RFC2282], and the IETF-ISOC relationship
    >  [RFC2031].
    
    The selection of RFC 2282 here seems arbitrary, as it was not the initial
    version of BCP 10 (which would be RFC 2027), nor is it the current one
    (RFC 7437). Perhaps a reference directly to BCP 10 instead of a specific
    RFC would be the cleanest way to address this (as mention of an obsoleted
    version without also pointing to the current procedure seems a bit awkward).
    
    ---------------------------------------------------------------------------
    
    §7:
    
    >  Under the new IASA 2.0 structure, the IETF is solely responsible for
    >  its administration, including the IETF Trust, IAB, IESG, IETF working
    >  groups, and other IETF processes.  A further exploration of this can
    >  be found in Section 4 of [I-D.ietf-iasa2-rfc4071bis].
    
    The mention of "the IETF" in "...the IETF is solely responsible..." feels
    somewhat ambiguous on the heels of significant treatment of the IETF LLC.
    Clearly, the responsibilities enumerated here are the responsibility of
    "The IETF" as that term has historically been used (the IETF community at
    large). Perhaps including "IETF LLC" in the list of things that "the IETF"
    is responsible for would make the distinction more clear.