IETF Logo Mail Archive

Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt

"Livingood, Jason" <Jason_Livingood@comcast.com> Mon, 22 October 2018 14:19 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 BA867126BED; Mon, 22 Oct 2018 07:19:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[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 mxZlyH5GVMVN; Mon, 22 Oct 2018 07:19:34 -0700 (PDT)
Received: from copdcmhout02.cable.comcast.com (copdcmhout02.cable.comcast.com [96.114.158.212]) (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 185AF124408; Mon, 22 Oct 2018 07:19:34 -0700 (PDT)
X-AuditID: 60729ed4-18dff7000000546c-0c-5bcddc7367e8
Received: from COPDCEXC35.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 copdcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id 55.60.21612.37CDDCB5; Mon, 22 Oct 2018 08:19:31 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC35.cable.comcast.com (147.191.125.134) 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 10:19:30 -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 10:19:30 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "rsalz@akamai.com" <rsalz@akamai.com>, "iasa20@ietf.org" <iasa20@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "sob@sobco.com" <sob@sobco.com>
Subject: Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt
Thread-Topic: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt
Thread-Index: AQHUaLIWWpnqiALk7Em/K8gy6dO0QqUo45cAgAAFbgCAAmmPAA==
Date: Mon, 22 Oct 2018 14:19:30 +0000
Message-ID: <26A20EA9-5EF8-4059-9A5B-56615E174D8B@cable.comcast.com>
References: <4915CD062D28D607D3D4AD44@PSB> <8906b727-f9c3-e7e1-164b-f7b88e48e74b@gmail.com> <1C77C07809EFB402E3E10907@PSB>
In-Reply-To: <1C77C07809EFB402E3E10907@PSB>
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: [68.87.29.9]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7B2A970E5F889040927CC792928E89D9@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNKsWRmVeSWpSXmKPExsWSUDRnsm7xnbPRBlO3y1q0XdzHZLFk+kYm i2cb57NYtF76w2bxf0sni8XxTmUHNo/JRxYwe+ycdZfdY8mSn0wel1e+ZvZ4ceAbcwBrVAOj TUlGUWpiiUtqWmpecaodlwIGsElKTcsvSnVNLMqpDErNSU3ErgykMiU1J7MstUgfqzH6WM1J 6GLKOLDzNXPBJ86KF8eaWRoYL3B2MXJySAiYSPxeNIupi5GLQ0hgF5PEg42LGCGcFiaJhpfX 2SCc04wSz3/+YARpYRMwk7i78AoziC0iECnx//0kVpAiZoEpjBIHn68GKxIWsJDY+2UxUDcH UJGlxO1N6hD1ThILJnSClbAIqEq09k9mArF5BVwk7p6+xwpiCwnUSXw/+5cFxOYU0JbY+XIi WJxRQEzi+6k1YPXMAuISt57MZ4J4QUBiyZ7zzBC2qMTLx//A6kUF9CV2TzjOCBGXk1j28w4z yDnMApoS63fpQ4yxkui7tYUVwlaUmNL9kB3iHEGJkzOfsEC0ikscPrKDdQKj5Cwkm2chTJqF ZNIsJJNmIZm0gJF1FSOfpZmeoaGJnqGphZ6RodEmRnASm3dlB+Pl6R6HGAU4GJV4eC/vOxst xJpYVlyZe4hRgoNZSYR35RKgEG9KYmVValF+fFFpTmrxIUZpDhYlcd5ig1PRQgLpiSWp2amp BalFMFkmDk6pBsammBe2ew/tD5t/jePEjBSHhS7rn86T87eT9XTKuPLV7uK044ufnDlh/79i QvqKl1dqMpxUVsV6T/S9/2Jb8L5j/FY357JfzzZduyyfb27J3+j9RY2+c5Yq1ASUWXsvm1Lx bkWz4F3vd7Z5GeHpNW/+Jh35W3Bar02WKWDqyXBnfduEqOWnC68psRRnJBpqMRcVJwIAmQ5A Jl4DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RrEZ734fvrLD5-miNXPSkh4TD8E>
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 14:19:36 -0000

That seems a rather odd claim. We've been very straightforward in our plans for updating these docs every step of the way, including by suggesting to the WG which ones needed to be updated, calling to adopt their update, asking for volunteers to do so, etc.

Jason

On 10/20/18, 5:27 PM, "iasa20 on behalf of John C Klensin" <iasa20-bounces@ietf.org on behalf of john-ietf@jck.com> wrote:
    
    Frankly, the only good reason I can see for generating all of
    these IASA2 documents just to change terminology is to create
    enough noise that the community doesn't notice and pay attention
    to changes that actually might be controversial.   I trust and
    assume that is not the intent of anyone involved.
    
        john
    
    
    
    _______________________________________________
    iasa20 mailing list
    iasa20@ietf.org
    https://www.ietf.org/mailman/listinfo/iasa20

v2.23.0 | Report a Bug | By Email