Re: [Iasa20] [EXTERNAL] Re: I-D Action: draft-ietf-iasa2-rfc6635bis-02.txt

Bob Hinden <bob.hinden@gmail.com> Fri, 04 January 2019 18:56 UTC

Return-Path: <bob.hinden@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 2FBE4130E89 for <iasa20@ietfa.amsl.com>; Fri, 4 Jan 2019 10:56:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 7wSYR6NYNWCw for <iasa20@ietfa.amsl.com>; Fri, 4 Jan 2019 10:56:35 -0800 (PST)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 E1A62130E85 for <iasa20@ietf.org>; Fri, 4 Jan 2019 10:56:34 -0800 (PST)
Received: by mail-wm1-x32e.google.com with SMTP id m22so2128150wml.3 for <iasa20@ietf.org>; Fri, 04 Jan 2019 10:56:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=UmXQu8B7PAAtxd+WPNHehyntgflzXXdcZMm995RScJ8=; b=ffoH0rGOfW+H/Oe7TuiBdYIzT4bh3e+TWSZKmBK5pR//HV7eTtv8tHqffJCP0VJt7/ DLWoBBsJeiGAmI2ml5/6p1xK6QF6KhFninn70Fi1o8e4jMGPX5F1AY58vxzqIMZDlRdM 1V+8rgTrvKt73XXZr8xdT8ydDKrpcBoh8w0NiBQb/LbkAO/WqJP82AYReqiXguG82fO2 l4TCCRxmfstKhcpjJ9SnmHai0u3+kHELxNbwn4DGyObI6Bo9TeqOkIRivwSbNmy8jYSZ oIeSBxFW2xLjpKKfcm1gxmu1PBL94z2mcsatmzbSYMW4CC7u5C85vF57lk9GEkpLUhsc DaTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=UmXQu8B7PAAtxd+WPNHehyntgflzXXdcZMm995RScJ8=; b=gBqWrEUmMs5Ew7pEuK0/5HJi9Ozj8NT1UimU2wjXeyVuh3/s5W9QJRY7D6609uFfgw 2N8aS7qb3YSsHTK0pVhaQarpWB1ezfn77vn20v8yKTQKv7/nwyxGt3ptLHhsHHdnxnTh Y07lsWXvkhQr4pqWCaxd7xTGtTXQf2irjZseYhG6UqrX0s3bM85MPeFOZhcG/Gjw9jYU ZYwZ4Y6jg7zQXcbwwhYgVyjmz8ikng7GvtQN6sg8Yv0ub0e/3o8a7DC/D4AXOgpVGKhb BvWxgZX93KDr5ei37fuDCYfvPRXla0p7JLYbQSahIbR2Y0o5llvCU986p0r6v8hPLOIp 8rJQ==
X-Gm-Message-State: AJcUukfvtkjZMc/BaQzm0hIHpY+96opHCZNl4hu0O5zFjM7jZ12cu9Is BW9pRDPgkhpKTEipzB6JQ3s=
X-Google-Smtp-Source: ALg8bN4CepAiF7SLv8LL1N1aAcZRXikd700NsYcppoeUKqBhE9GQyo8TuEkbu3STskfzXoPFd/MuEw==
X-Received: by 2002:a1c:9d57:: with SMTP id g84mr2195839wme.16.1546628192953; Fri, 04 Jan 2019 10:56:32 -0800 (PST)
Received: from ?IPv6:2601:647:4d01:f3a:b0e1:b641:c5ce:c7d2? ([2601:647:4d01:f3a:b0e1:b641:c5ce:c7d2]) by smtp.gmail.com with ESMTPSA id v133sm2814474wmf.19.2019.01.04.10.56.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Jan 2019 10:56:32 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <FF931316-E5ED-4424-BE66-002608A76620@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_56BFD8CB-C919-46CF-99DE-D25E357BFB01"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 04 Jan 2019 10:56:28 -0800
In-Reply-To: <98790DD6-605F-4EAB-8047-471398E77BCA@cable.comcast.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Russ Housley <housley@vigilsec.com>, IASA 2 WG <iasa20@ietf.org>
To: Jason Livingood <Jason_Livingood@comcast.com>
References: <154654420527.29641.4244408138304253256@ietfa.amsl.com> <D2CDCECF-2818-455D-9DBF-C1585FA7B188@vigilsec.com> <21F0C0AC-8A08-4E7C-9946-C7EC6C8A837F@gmail.com> <1771D900-8AB2-42DF-8D6E-615A77264082@vigilsec.com> <01C8E8EC-223D-41DE-AAE9-86344FD398EA@cable.comcast.com> <9000F587-B4A5-453A-B8A2-2462EAEF4574@gmail.com> <98790DD6-605F-4EAB-8047-471398E77BCA@cable.comcast.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/2Wf0gXHTSLBuPidft5q58FX77fY>
Subject: Re: [Iasa20] [EXTERNAL] Re: I-D Action: draft-ietf-iasa2-rfc6635bis-02.txt
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: Fri, 04 Jan 2019 18:56:37 -0000

Thanks, I will proceed.

Bob


> On Jan 4, 2019, at 10:44 AM, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
> 
> Sounds sensible, Bob, given the IAB stream.
> 
> On 1/4/19, 1:08 PM, "Bob Hinden" <bob.hinden@gmail.com> wrote:
> 
>    Jason,
> 
>> On Jan 4, 2019, at 6:10 AM, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
>> 
>> If it can be fixed now, no reason not to do so.
> 
>    In addition to removing the IAB as an author, Russ suggested adding something like this to the abstract:
> 
>      {{ RFC Editor: Please remove the following paragraph prior to publication. }}
> 
>      The IASA2 WG asks the IAB to publish this replacement for RFC 6635.
> 
>    I can do that for this and rfc6548bis, both are IAB stream documents.
> 
>    Please advise.
> 
>    Thanks,
>    Bob
> 
>> 
>> From: iasa20 <iasa20-bounces@ietf.org> on behalf of Russ Housley <housley@vigilsec.com>
>> Date: Thursday, January 3, 2019 at 3:10 PM
>> To: Bob Hinden <bob.hinden@gmail.com>
>> Cc: IASA 2 WG <iasa20@ietf.org>
>> Subject: Re: [Iasa20] I-D Action: draft-ietf-iasa2-rfc6635bis-02.txt
>> 
>> 
>> 
>> 
>>> On Jan 3, 2019, at 2:47 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>>> 
>>> Should I do an update now, or leave it for later (or the RFC Editor)?
>> 
>> T think that the WG Chairs need to make that call...
>> 
>> Russ
> 
> 
>