IETF Logo Mail Archive

Re: [Iasa20] draft-ietf-iasa2-consolidated-upd-06

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 07 March 2019 19:46 UTC

Return-Path: <brian.e.carpenter@gmail.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 4E361131167 for <iasa20@ietfa.amsl.com>; Thu, 7 Mar 2019 11:46:47 -0800 (PST)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 PwHFBzJGMTle for <iasa20@ietfa.amsl.com>; Thu, 7 Mar 2019 11:46:45 -0800 (PST)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 1E889131140 for <iasa20@ietf.org>; Thu, 7 Mar 2019 11:46:45 -0800 (PST)
Received: by mail-pg1-x532.google.com with SMTP id b2so12065422pgl.9 for <iasa20@ietf.org>; Thu, 07 Mar 2019 11:46:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=LXRmTc2mgbbmXcFczKnWty+dFq0ktqOAkbBjsxm6H/4=; b=SASI5wUefki6P7ENaQvRwk/KoTF03+2/Eqpa/HErDbhd9lXgmBUmyVM6DEvtXMfhQl 8Yzu7gclq4+d5VXxVJ1QRVRqp0DJyF+hBbNDcumcbY6Yxit6Y+ema0emuf3ThhwU/lmp kHZTHdV0IbizSjmekPXfTBoX2XqRb9inC8/lEBoLAoI2wQLyFgvnMf4nmnys/h7/g+wn rBfAgp84yeRRFKDQq6jMishOdlQSZcsmjoZqxqZj97SS+nhBrHZ58+kdP1YUYFuGF+dg CY3YmzlCv/wltuQEwcDOnL0Cnh3WVIdCMXNAJch/yLciS1j4O/nkWjQGsT0o7S5BxU9J B+Ww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=LXRmTc2mgbbmXcFczKnWty+dFq0ktqOAkbBjsxm6H/4=; b=D+MqF0DYoY91/KTXpXzFzbhjXtanG0jNfV/krQ1I+JLRoXp3VExuHik0O+tc2pZYpm o57TEov3ukhh9Z0+FvVMDzPtANH93O5PKjVLLx2h2A97N6FkM0m25PsGguaWu6c6vmp/ FOIDJf7dSvTJw+DNASAhWYYfm1qj3M1nyx5dz5hO4z7Don+PjpQ+WXAGD7DTGmaGs2oV s1PTvu+oY9b7kh6SfKHEWUg9/3Kwn0idWe7/9J2Y1EzCos9MAIoFI1oyK94WzBZx3f75 c+NLu5ui4vDlXgBTu6ZgrjOLzSLUpvMysmBIPpPoscbT+ichGQZZ1oZDNn2kVUuzY/ZX /8bg==
X-Gm-Message-State: APjAAAWDFGz15hCc6siJlRe2rYC6Mi958K/Yl5UMS0Uvr1H9qOUpwCBC NUEIjLs/34E4pkMAQTnfi47ewSF0
X-Google-Smtp-Source: APXvYqzl5dFM3plUSYEWySQGsjsWRszMtX93M6EA4kfJKmEutryMxmXsWEvWUo2DHNVGEuNEEQZTcg==
X-Received: by 2002:a17:902:121:: with SMTP id 30mr9978589plb.315.1551988004230; Thu, 07 Mar 2019 11:46:44 -0800 (PST)
Received: from [192.168.178.30] ([118.148.79.176]) by smtp.gmail.com with ESMTPSA id l64sm7250388pga.87.2019.03.07.11.46.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Mar 2019 11:46:43 -0800 (PST)
To: Alissa Cooper <alissa@cooperw.in>, John C Klensin <john-ietf@jck.com>
Cc: iasa20@ietf.org
References: <A7B72177ABB2B2F0BEE7763B@PSB> <567462F2-46E3-445E-BDA3-493DA7AD31CC@cooperw.in>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <4faec579-e4dd-f138-4c96-f26d9945c307@gmail.com>
Date: Fri, 08 Mar 2019 08:46:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <567462F2-46E3-445E-BDA3-493DA7AD31CC@cooperw.in>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/HiZe2adkC5gQvWOxXEdH_EpV16s>
Subject: Re: [Iasa20] draft-ietf-iasa2-consolidated-upd-06
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: Thu, 07 Mar 2019 19:46:47 -0000

On 08-Mar-19 06:12, Alissa Cooper wrote:
> Thanks. I still don’t think this is quite right because there is no basis for this working group to obsolete or render historic RFC 3929 simply because it mentions the IETF Executive Director. It seems that RFC 3929 should be treated in Section 2 the same as the other documents in that section.

There's a more general issue: tracking down all "open" Experimental RFCs and deciding which of them need to be closed off as Historic or Obsolete or both. <joke>No doubt the IESG will be doing this in its copious free time.</joke> But for the present, doesn't it make more sense to clear both 3929 and 4633 up right away? I agree that it's outside the WG's mandate, strictly interpreted, but if the IESG consents, is that really a problem?

    Brian

> 
> Alissa
> 
>> On Mar 7, 2019, at 1:52 AM, John C Klensin <john-ietf@jck.com> wrote:
>>
>> Hi.
>>
>> draft-ietf-iasa2-consolidated-upd-06 should be posted in a few
>> minutes.  I hope this version reflects changes requested since
>> -05 was posted at the end of January.  In particular, it
>> reflects the suggestions from the RFC Editor and the  separate
>> status of the RFC 3716 as an IAB document and the text supplied
>> by Alissa in her note yesterday.
>>
>> The bad news is that when I read Section 4 after patching those
>> changes in, it was just too convoluted and I had to restructure
>> and rewrite it.  I hope the changes are at least tolerable to
>> everyone and that I didn't make mistakes that would require
>> another iteration.  Of course, if I did and problems are
>> spotted, I'll be happy to that.  
>>
>> On the other hand, if the language reflects the WG's intent
>> sufficiently well but some of my phrasing doesn't line up with
>> the needs of the IAB or RFC Editor, I recommend that we attach
>> appropriate notes and let them sort it out with each
>> other and the IESG if needed on AUTH48 rather than trying to
>> make small editorial changes by committee nit-picking.   Just my
>> preference, of course, YMMD.
>>
>>    john
>>
>>
>> _______________________________________________
>> iasa20 mailing list
>> iasa20@ietf.org
>> https://www.ietf.org/mailman/listinfo/iasa20
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>

v2.23.0 | Report a Bug | By Email