Re: [Teas] Questions about the Appendixes to draft-ietf-teas-rfc3272bis

Joel Halpern <jmh@joelhalpern.com> Thu, 07 July 2022 14:19 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7895C15D470 for <teas@ietfa.amsl.com>; Thu, 7 Jul 2022 07:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.002
X-Spam-Level:
X-Spam-Status: No, score=-9.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id azMg9FsE_1Xs for <teas@ietfa.amsl.com>; Thu, 7 Jul 2022 07:19:05 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9AA9C15A736 for <teas@ietf.org>; Thu, 7 Jul 2022 07:19:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4Ldz6r1ChZz1pMJV; Thu, 7 Jul 2022 07:19:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1657203540; bh=sd8PFfmE+X+pF0Wmf0+BNIiqdxEKqu+r8bu4A5Woo0c=; h=Date:Subject:To:References:From:In-Reply-To:From; b=GOpTzy4U4pVcnxZGuWlVIQegsyRT4E5lvd/t7EitZFidERhYeqhGDF66oXWzZ9oBx bh8mZDnFCaZHprNZSAGWkQtz62Gd/zljJbwqkv4v+DtwjUat/C1fIJQr7689/lF5Yp rqgoBQ70qtQ5zxd5fjtm+XMGlSUjsVXMXAL3Dp7U=
X-Quarantine-ID: <8F_xe6o0wAR0>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.181] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4Ldz6q3Vl2z1p5tx; Thu, 7 Jul 2022 07:18:58 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------PEeNpeXN8QhodRgtJJzw6u6V"
Message-ID: <0fd13ba5-4905-2cca-e72d-23d51d6306ba@joelhalpern.com>
Date: Thu, 07 Jul 2022 10:18:55 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: adrian@olddog.co.uk, 'TEAS WG' <teas@ietf.org>
References: <019b01d891ef$bb4f3050$31ed90f0$@olddog.co.uk>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <019b01d891ef$bb4f3050$31ed90f0$@olddog.co.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/uaTAAn8xd52_8qc3LLO1Y_xYX-A>
Subject: Re: [Teas] Questions about the Appendixes to draft-ietf-teas-rfc3272bis
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2022 14:19:09 -0000

Personally, I think we can delete both appendices.  While having an 
historic record is important, the earlier RFC contains that for historic 
purposes.  I do not think that it behooves the community to try to bring 
those two sections up to date, which is what would seem to be required 
if we want to keep them in the document.


Yours,

Joel

On 7/7/2022 6:53 AM, Adrian Farrel wrote:
>
> Hi,
>
> We have just one thing remaining after working group last call…
>
> Don raised some concerns about the Appendixes to this draft and this 
> is an attempt to focus the questions and possibly drive answers.
>
> Appendix A.  Historic Overview
>
>   * Should we delete or retain this Appendix?
>   * If we retain it, should we include some text indicating that it is
>     a subjective view? (If so, what text?)
>   * If we retain it, should we regard it as "History before what is in
>     the body of the text" or should we try to make the history
>     continue towards the present by including pointers back into the
>     body text? (If so, someone is going to need to do that work!)
>   * If we retain it, should we look to fill any gaps between the end
>     of the history documented in the Appendix and the start of the
>     material in the body text?
>
> Appendix B.  Overview of Traffic Engineering Related Work in Other SDOs
>
>   * Should we delete or retain this Appendix?
>   * If we retain it, should it attempt to list out other (all?) SDOs
>     that have done TE work? (If so, who will try to compile this list?)
>
> I would really appreciate any thoughts on these points and, depending 
> on your answers, some (promises of) text.
>
> Thanks,
>
> Adrian
>
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas