Re: [Iasa20] Roman Danyliw's No Objection on draft-ietf-iasa2-rfc2031bis-05: (with COMMENT)

"Livingood, Jason" <Jason_Livingood@comcast.com> Thu, 22 August 2019 20:07 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 7C2B6120C2B for <iasa20@ietfa.amsl.com>; Thu, 22 Aug 2019 13:07:01 -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=unavailable 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 l6BvRsbqz4Kf for <iasa20@ietfa.amsl.com>; Thu, 22 Aug 2019 13:06:59 -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 9FAB7120C6A for <iasa20@ietf.org>; Thu, 22 Aug 2019 13:06:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=comcast.com; s=20190412; c=relaxed/simple; q=dns/txt; i=@comcast.com; t=1566504401; x=2430418001; 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=pszZwZ09+ANsnjH0yDu2i46sCif9p1W8n/3Bdv2Q+ew=; b=4toE7ztmiQATsjXsXp+pETA9Rm0OU54hzzQqHwbdaYfZ4vmO0v7yjK6AbMUBNSok F6V7ElS/prpSdAHc9i1MKvJHcETgaGPYVkQ3N4TSTm+zRv9l3XpfqmHUJPfIdd6w ms2z3nrmZgNlqsfBDc0Q3WhUP9tXTLWL44zm1QPlICwt7BUJVLG48A1rc6Rf2Xed RaBcJ0V20qfnIxgdzAByB+CzfPh/eu+KtJ4PDA3+tXzDa3p2FoU2JMuRXdvVTotb 8rReYl9NF47ZkbhS76TqnYxBn6H5J2jSZGCajCt0y7Gru7c2gSJxQ6lHYuuFSYct hOrF/NK6ooYfcgRH8alTng==;
X-AuditID: a2962c47-a9fff7000002e144-59-5d5ef5d123ec
Received: from COPDCEXC40.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 DB.AF.57668.1D5FE5D5; Thu, 22 Aug 2019 14:06:41 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC40.cable.comcast.com (147.191.125.139) 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 16:06:57 -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 16:06:57 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Roman Danyliw <rdd@cert.org>, 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: Roman Danyliw's No Objection on draft-ietf-iasa2-rfc2031bis-05: (with COMMENT)
Thread-Index: AQHVV4pefrP/5CeIe0OMvVWuRax+3KcHmziA
Date: Thu, 22 Aug 2019 20:06:57 +0000
Message-ID: <A9349C27-F8FF-4848-ACF2-696E4DA8F8EF@cable.comcast.com>
References: <156632798201.457.1362280444323430129.idtracker@ietfa.amsl.com>
In-Reply-To: <156632798201.457.1362280444323430129.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: [96.115.73.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3A2673D94EF0FE46B13C320240322A2B@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPKsWRmVeSWpSXmKPExsWSUDRnsu7Fr3GxBu2tEhbbD7xmtOi9+53d Ysn0jUwWM/5MZLY402Bp8bmNzYHNY8YGH48lS34yeexoeM4cwBzVwGhTklGUmljikpqWmlec aselgAFsklLT8otSXROLciqDUnNSE7ErA6lMSc3JLEst0sdqjD5WcxK6mDI2TjvKWHBBquLf +v2MDYw/JLsYOTkkBEwk9nz6xdLFyMUhJHCESWLW0//sEE4Lk8Srr+eYIZzTjBIL1+xmBGlh EzCTuLvwCjOILSJgJdGx7QpYO7PANUaJfX/fs4EkhAViJa5N7WGFKIqTOPnxMJRtJPH44AIw m0VAVWLa/LXsIDavgIvEulVPwIYKCXhLbD3wCKyGU8BHYubeK2AzGQXEJL6fWsMEYjMLiEvc ejKfCeIHAYkle84zQ9iiEi8f/wPrFRXQl1jyYzMrRFxR4tc8kDkcQL2aEut36UOMsZJYvbWP HcJWlJjS/RDqHEGJkzOfsEC0ikscPrKDdQKj5Cwkm2chTJqFZNIsJJNmIZm0gJF1FSOvoZmR nqGpgZ6JiZ654SZGYLJaNE3HfQfjh/OxhxgFOBiVeHhdn8fFCrEmlhVX5h5ilOBgVhLhLZsI FOJNSaysSi3Kjy8qzUktPsQozcGiJM57tys2VkggPbEkNTs1tSC1CCbLxMEp1cDI9HnjKkWx ac5fanQOSHsm/c7S+rRkXVhdtb965qNXsZdYPp7ysVpmqCX5/6jd/BnHtb5PZi8OVzW/Lut+ 1sYoLk1Y7LJx+vagdfLui+P6b2j17qyxfLNJytBvRcua5Taf8thiD9VqWk+Xl121QF1tZ3pH 3a9SqxeGGw577y1qfMnGncskwKXEUpyRaKjFXFScCACcsnFgUgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/eYCWUjgAq09vyfB7Dt4BWHvASlM>
Subject: Re: [Iasa20] Roman Danyliw's No Objection 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 20:07:02 -0000

Thanks and these changes will be made in the -06 shortly.

In response to your question on funding support, ISOC has only agreed to provide funding of a specific dollar figure through FY2020, after which a joint re-assessment will be conducted on future. I'll try to generalize the text. I don't think anyone expects that funding to go away in the foreseeable future of course.

Jason

On 8/20/19, 3:06 PM, "Roman Danyliw via Datatracker" <noreply@ietf.org> wrote:

    Roman Danyliw has entered the following ballot position for
    draft-ietf-iasa2-rfc2031bis-05: No Objection
    
    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:
    ----------------------------------------------------------------------
    
    ** Section 1.  Typo.  s/the the/the/
    
    ** Section 3 makes the absolute statement that “the IETF and ISOC acknowledge
    that ISOC has no influence whatsoever on the technical content of the Internet
    standards”.  Section 4 reminds us that “ISOC maintain[ing] liaison
    relationships … with other … SDOs”.  Stretching a bit, given the reliance of
    the IETF on these key SDO relationships, the ability to or timeliness in
    forming/keeping these relationships could conceivably indirectly influence
    technical standards.  IMO, s/ISOC has no influence/ISOC has no direct
    influence/.
    
    Derived from Hilarie Orman’s SECDIR review:
    
    ** Section 7.  Per “Under the terms of the Operating Agreement [OpAgreement]
    between ISOC and the IETF, ISOC has agreed to provide some funding support for
    the IETF (ISOC has historically provided the IETF with significant financial
    support)”, what is the difference between “some funding” and “significant
    funding support”?
    
    ** References.  Explicitly point to
    https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf for [OpAgreement]