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

mohamed.boucadair@orange.com Thu, 07 July 2022 12:06 UTC

Return-Path: <mohamed.boucadair@orange.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 98052C15C15A for <teas@ietfa.amsl.com>; Thu, 7 Jul 2022 05:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, 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 (2048-bit key) header.d=orange.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 eirUxOguOIGU for <teas@ietfa.amsl.com>; Thu, 7 Jul 2022 05:06:41 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (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 B4DCFC157B37 for <teas@ietf.org>; Thu, 7 Jul 2022 05:06:40 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar20.francetelecom.fr (ESMTP service) with ESMTPS id 4LdwB70z1Pz8srr; Thu, 7 Jul 2022 14:06:39 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1657195599; bh=qlBCEhgDk7d/Zmo/qS1rz2BSjGVAJzDX64G8Z3D85tA=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=SrRRbTaBKeumZdRT26S+XZzP0u6Cq/l2ZdIqkOM2nJmWAquUKpzd6AuHWX6EC7jm4 Q56hRtLwG2HYiv0fzi0X34lS2JeZ+iZ5cwyZgk1x4ajt/dLVfGxzPkvkzSJ16MNV0Z UrJY4+etK9Bk2JjSYV1CDzG6Iy1KEQK4VpFELdMQyM+HlR42VUSJXUUYQRyuJaQyEo Y/V1ooYzEM818SeCusSwJiUuLMa6MgwOy9iL/6Wh80DAeEhe9JX+PwIDsW8Ee+Kpbv iDuT9ESA9Hf+rX/KA3cnRMdI7bf84RPEY9d1+nkMjRLfNiKv6YEzz9r1a6a5Rp0/VG X+DMYxuBWq2YQ==
From: mohamed.boucadair@orange.com
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'TEAS WG' <teas@ietf.org>
CC: 'Don Fedyk' <dfedyk@labn.net>
Thread-Topic: [Teas] Questions about the Appendixes to draft-ietf-teas-rfc3272bis
Thread-Index: AdiR7nzP+p5wWs5WQ9uGPVEZndr9FwACZQ3w
Content-Class:
Date: Thu, 07 Jul 2022 12:06:38 +0000
Message-ID: <13149_1657195599_62C6CC4E_13149_120_1_ba94d8e4fa34437d865355daa24477b6@orange.com>
References: <019b01d891ef$bb4f3050$31ed90f0$@olddog.co.uk>
In-Reply-To: <019b01d891ef$bb4f3050$31ed90f0$@olddog.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-07-07T11:53:03Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=52d824a8-5976-4601-bc39-8486d8d49169; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.52]
Content-Type: multipart/alternative; boundary="_000_ba94d8e4fa34437d865355daa24477b6orangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/xpGi2RKaf1UXf0L_-8loYqRGdP4>
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 12:06:44 -0000

Hi Adrian, all,

I would retain both appendixes + make this change:


OLD:

   A historic overview of TE in telecommunications networks is provided in

   Appendix A<https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-19#appendix-A>, while Appendix B<https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-19#appendix-B> describes approaches in other standards

   bodies.

NEW

   A brief historic overview of TE in telecommunications networks is provided in

   Appendix A<https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-19#appendix-A>, while Appendix B<https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-19#appendix-B> describes some approaches in other standards

   bodies. It is out of the scope of this document to provide an exhaustive

   inventory of TE-related efforts conducted by all relevant SDOs. The content of

   these appendixes is inherited from RFC3272 (see Appendix C for more details).


BTW, the change log should be fixed s/4.7/4.6



   *  Appendix B<https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-19#appendix-B>: New for this document.



      -  Appendix B.1<https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-19#appendix-B.1>: Based on Section 4.7 of RFC 3272<https://datatracker.ietf.org/doc/html/rfc3272#section-4.7>.

Cheers,
Med

De : Teas <teas-bounces@ietf.org> De la part de Adrian Farrel
Envoyé : jeudi 7 juillet 2022 12:53
À : 'TEAS WG' <teas@ietf.org>
Cc : 'Don Fedyk' <dfedyk@labn.net>
Objet : [Teas] Questions about the Appendixes to draft-ietf-teas-rfc3272bis


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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.