Re: [Iasa20] [EXTERNAL] Re: AD review of draft-ietf-iasa2-rfc4071bis-04

"Livingood, Jason" <Jason_Livingood@comcast.com> Tue, 26 February 2019 14:16 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 B28E6128CE4 for <iasa20@ietfa.amsl.com>; Tue, 26 Feb 2019 06:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 IUWLszh_uN8l for <iasa20@ietfa.amsl.com>; Tue, 26 Feb 2019 06:16:07 -0800 (PST)
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 C6EC7130EA0 for <iasa20@ietf.org>; Tue, 26 Feb 2019 06:16:07 -0800 (PST)
X-AuditID: a2962c47-fbdff7000001abb1-5c-5c754a258b48
Received: from copdcexc34.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by copdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 6A.DB.43953.52A457C5; Tue, 26 Feb 2019 07:16:05 -0700 (MST)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by copdcexc34.cable.comcast.com (147.191.125.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 26 Feb 2019 09:16:05 -0500
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.1466.012; Tue, 26 Feb 2019 09:16:05 -0500
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Alissa Cooper <alissa@cooperw.in>
CC: IASA 2 WG <iasa20@ietf.org>
Thread-Topic: [Iasa20] [EXTERNAL] Re: AD review of draft-ietf-iasa2-rfc4071bis-04
Thread-Index: AQHUzd3PmxFUNeycYEmtOdv5k0bRnA==
Date: Tue, 26 Feb 2019 14:16:05 +0000
Message-ID: <7AA5530A-D94C-40B6-94AB-C52AE2ADB828@cable.comcast.com>
References: <91A5EFAD-BD9F-435E-B01A-7091B263374D@cooperw.in> <4C24F773-B07A-4017-8880-EFACDB76EC9D@cable.comcast.com> <3AAC674D-CD1C-4DDD-BA2A-91D3538B935B@cooperw.in> <3EB626EE-9401-4B8F-9FAC-1D262BF85F18@cable.comcast.com>
In-Reply-To: <3EB626EE-9401-4B8F-9FAC-1D262BF85F18@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.15.0.190115
x-originating-ip: [96.114.156.8]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A1763E34EEF4F441819CC346DB2C03C1@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGKsWRmVeSWpSXmKPExsWSUDRnsq6aV2mMwcuPvBbTz/xltFgyfSOT A5PHlycvmTyWLPnJFMAU1cBoU5JRlJpY4pKalppXnGrHpYABbJJS0/KLUl0Ti3Iqg1JzUhOx KwOpTEnNySxLLdLHaow+VnMSupgyfrXdYyqYoFWxo+kWawNji2YXIweHhICJxOrPyV2MXBxC AruYJO4dWMcG4bQwSSydv4ARwjnNKNEzcRdrFyMnB5uAmcTdhVeYQWwRAVWJq8d+sIHYzALy Escm/QOzhQWCJJ6+fckCURMs8X7aJlYIW0/i2uszLCCbWYB6l64BC/MKuEgsnfeYEcQWEnjO KNHYYQVicwq4Siza8IQdxGYUEJP4fmoNE8QqcYlbT+aD2RICAhJL9pxnhrBFJV4+/gc2U1RA X6L1+w9WiLiCxPb928DWMgtoSqzfpQ8xxkriVAvECcwCihJTuh+yQ5wjKHFy5hMWiFZxicNH drBOYJSchWTzLIRJs5BMmoVk0iwkkxYwsq5i5DU0M9IzNDXQMzHRMzfcxAhMPYum6bjvYPxw PvYQowAHoxIP71/H0hgh1sSy4srcQ4wSHMxKIryzXYBCvCmJlVWpRfnxRaU5qcWHGKU5WJTE eT95lsQICaQnlqRmp6YWpBbBZJk4OKUaGPfF/WXV9K9dVZP3lIl198myp3LpSWuWd35bvX+2 rOVn6e+J17QjE1o8NJZnXdj6MyCr4bmxk9zeXRPZDq29n/jr4W5eW3XDNdwmh7wlTpzTm741 96pAQcIHOaXPbLVXdrq90hORzvvaLPUjX9O8fvqc9VPec9cHZncd3C/WNjed1a3B/nJGjhJL cUaioRZzUXEiAE59cxU5AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/NHkwrfxxr6M_L9cC5GxyaJ2Wupc>
Subject: Re: [Iasa20] [EXTERNAL] Re: AD review of draft-ietf-iasa2-rfc4071bis-04
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <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: Tue, 26 Feb 2019 14:16:10 -0000

I've reflected on this a bit more and can see the benefit in further simplifying this, and reducing the need to tightly couple the text in the two docs.

Alissa - Could you support this simplification or something like it?

Principles of the IETF and ISOC Relationship
The principles of the relationship between the IETF and ISOC are outlined in {{?I-D.ietf-iasa2-rfc2031bis}}. In short, the IETF is responsible for the development of the Internet Standards and ISOC aids the IETF by providing it a legal entity within which the IETF LLC exists, as well as with financial support. 
    

On 2/25/19, 10:43 AM, "iasa20 on behalf of Livingood, Jason" <iasa20-bounces@ietf.org on behalf of Jason_Livingood@comcast.com> wrote:

    I understand the need to ensure these are aligned. The language is quite short and was intended as a summary for people who don’t want to read another document. If 2031bis changes during the review process, this would correspondingly change. Looking at the text (pasted below), the 1st paragraph is verbatim from Section 2 of 2031bis. Are you suggesting deletion of the 2nd paragraph or removal of the entire section (I'm not clear what action you suggest)?
    
    JL
    
    From the current doc:
    Principles of the IETF and ISOC Relationship
    ISOC and the IETF have historically been philosophically aligned. The principles of the relationship between the IETF and ISOC are outlined in {{?I-D.ietf-iasa2-rfc2031bis}}. ISOC's connection with the IETF community has always played an important role in its policy work. ISOC has always been an advocate for multistakeholder processes, which includes the technical community. Open standards are an explicit part of one of the focus areas in ISOC's mission: Advancing the development and application of Internet infrastructure, technologies, and open standards.
    
    On a practical level, the IETF LLC is a distinct entity (a disregarded entity) of ISOC. The IETF remains responsible for the development and quality of the Internet Standards. ISOC aids the IETF by providing it a legal entity within which the IETF LLC exists, as well as with financial support. ISOC has no influence whatsoever on the technical content of Internet Standards.
    
    On 2/25/19, 2:03 AM, "Alissa Cooper" <alissa@cooperw.in> wrote:
    
        
        
        > On Feb 24, 2019, at 3:45 PM, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
        > 
        > [JL] I am working on edits now in response to your list. I will comment as/if needed as I go. Here is one:
        >> == Section 3.5 ==
        >> Since we have an entire document about the IETF-ISOC relationship (draft-ietf-iasa2-rfc2031bis), why is this section needed?
        > 
        > [JL] It is a very short section - a few sentences. The idea was to give a quick sense of the IETF-ISOC relationship at a high level - so folks need not necessarily read the other longer document to see all the details. 
        
        Ok. The issue I see is that we will end up with two documents that say slightly different things, and people who have to interpret this later will wonder whether those distinctions are meaningful. The first paragraph of 3.5 is copied verbatim from 2031bis, so if that text changes before 2031bis is approved, there will be discrepancies. The second paragraph does not seem to come from 2031bis, and IIRC the WG spent quite some time settling on the precise language to use there to describe the legal relationship between the two entities. I would suggest just linking to specific sections of 2031bis so people can find the relevant bits when they need to.
        
        Thanks,
        Alissa
        
        > 
        > 
        > 
        > 
        
    
    _______________________________________________
    iasa20 mailing list
    iasa20@ietf.org
    https://www.ietf.org/mailman/listinfo/iasa20