Re: [Iasa20] fundamental brokenness of iasa2 updates (was Re: draft-ietf-iasa2-rfc2418bis-01.txt)

"Livingood, Jason" <Jason_Livingood@comcast.com> Mon, 22 October 2018 23:51 UTC

Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1386A12DD85; Mon, 22 Oct 2018 16:51:35 -0700 (PDT)
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 6TFHRBo3q8zJ; Mon, 22 Oct 2018 16:51:33 -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 0DF74126BED; Mon, 22 Oct 2018 16:51:33 -0700 (PDT)
X-AuditID: a2962c47-d4dff70000003e3c-57-5bce6278762f
Received: from COPDCEXC37.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 0C.68.15932.8726ECB5; Mon, 22 Oct 2018 17:51:20 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC37.cable.comcast.com (147.191.125.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 22 Oct 2018 19:51:31 -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.1466.009; Mon, 22 Oct 2018 19:51:31 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Scott Bradner <sob@sobco.com>, Alissa Cooper <alissa@cooperw.in>
CC: IASA 2 WG <iasa20@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: [Iasa20] fundamental brokenness of iasa2 updates (was Re: draft-ietf-iasa2-rfc2418bis-01.txt)
Thread-Topic: [Iasa20] fundamental brokenness of iasa2 updates (was Re: draft-ietf-iasa2-rfc2418bis-01.txt)
Thread-Index: AQHUakt4VvoiIavUDEum12Qn6pwWv6UsCtKAgAABHQD//+PIAA==
Date: Mon, 22 Oct 2018 23:51:31 +0000
Message-ID: <CB09ACE9-2C8C-42E4-825D-EAF2D14F3CF7@cable.comcast.com>
References: <4915CD062D28D607D3D4AD44@PSB> <8906b727-f9c3-e7e1-164b-f7b88e48e74b@gmail.com> <1C77C07809EFB402E3E10907@PSB> <DE6E9C0D-C46B-4010-9E6D-8438DE687275@sobco.com> <2A42A5D2-9785-4350-92A5-0FDFD54AD17F@cable.comcast.com> <9A5B610BA33D4336A91409DA@PSB> <CABtrr-UdUaZpoy8JroUL8oNkibc=F8hJ1ksnmvar0a1x3VCNrQ@mail.gmail.com> <541E68A8540C1AB8D39A96E4@PSB> <313EA233-92B1-4D61-AECA-099ADEECD063@sobco.com> <D7D597C1-F934-4748-9AEF-998CD8771DB5@cooperw.in> <8B5D1F95-5018-4B05-A461-DB0912CC82C7@sobco.com>
In-Reply-To: <8B5D1F95-5018-4B05-A461-DB0912CC82C7@sobco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.3.181015
x-originating-ip: [96.115.73.253]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BED9950B59D7B343B988BB8E00EE7F11@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGKsWRmVeSWpSXmKPExsWSUDRnsm5F0rlog1NzdC2mn/nLaLFk+kYm i2cb57NYHO9UdmDx+PLkJZPHkiU/mTxeHPjGHMAc1cBoU5JRlJpY4pKalppXnGrHpYABbJJS 0/KLUl0Ti3Iqg1JzUhOxKwOpTEnNySxLLdLHaow+VnMSupgy/iw7x1hwRKDi6fSbrA2MPQJd jJwcEgImEsumbGPsYuTiEBLYxSQxcd9dZginhUniwNwN7BDOaUaJv2vnsoO0sAmYSdxdeIUZ xBYRcJG41DQTLM4s4Cvx4e43MFtYIEfi/vRfrBA1uRLHtmxig7CdJG5P/c4EYrMIqEp8/NAO NocXaM6sN4+hzuhnkVgzaQbQIA4OTgFbiQN3wWoYBcQkvp9awwSxS1zi1pP5TBAvCEgs2XOe GcIWlXj5+B/YXlEBfYndE44zQsQVJfZ9WMEMMpJZQFNi/S59iDFWEkd6fzNC2IoSU7ofskOc IyhxcuYTFohWcYnDR3awTmCUnIVk8yyESbOQTJqFZNIsJJMWMLKuYuQ1NDPSMzQ10DMx0TM3 3MQITE2Lpum472D8cD72EKMAB6MSD2+A/7loIdbEsuLK3EOMEhzMSiK88X5AId6UxMqq1KL8 +KLSnNTiQ4zSHCxK4rzhBqeihQTSE0tSs1NTC1KLYLJMHJxSDYzNE4xYrKzU5X/8KxTNsVX8 HHQtzSHpxAGbPsYDD6esYzq82XaCXvmO+f/FvmqXPO5iOBNsc+vFQ9FnLnNudnYoV4YU72bc +MaPxfy748fenccu84v0BJkYvDhxXq7hVoHcVeNn318s/hV031tx637WzS8uCR9gUWY/UMY6 92Nw4jkZl3ZNLy8lluKMREMt5qLiRAAu13MNSQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y_o2ps92BXVFZElj4ItkAGm_jOY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 23:51:36 -0000

Echoing Alissa's note: it is nice to have some additional and quite experienced eyes on these documents. It's not a sexy or fun thing to work on, for sure, but important nonetheless. 

In any case, having specific feedback on what to improve or challenge, particularly when offered in such a succinct a way as you have below, is always appreciated and will make the eventual work product better in the end.

JL

On 10/22/18, 5:34 PM, "ietf on behalf of Scott Bradner" <ietf-bounces@ietf.org on behalf of sob@sobco.com> wrote:

    full explanations (in the documents) keeps people from having to make assumptions
    I do not want to be driven to making assumptions which is why I’m asking for explanations in the documents 
    
    Scott
    
    > On Oct 22, 2018, at 5:28 PM, Alissa Cooper <alissa@cooperw.in> wrote:
    > 
    > Hi,
    > 
    > I wanted to remind everyone that the IASA2 WG has requested publication of a total of two documents so far. All of the rest of the documents are still under discussion in the working group and will be undergoing IETF last call only after the WG requests publication and I do AD reviews. I would encourage people to continue making constructive suggestions for how to improve the documents in the WG and avoid making assumptions about authors’ motivations. Thus far we’ve had a great constructive dialogue with lots of people chipping in to do this less-than-thrilling administrative work, which is very much appreciated.
    > 
    > Regards,
    > Alissa