Re: [teas-3272bis-design-team] First spin on section pushed
Adrian Farrel <adrian@olddog.co.uk> Wed, 11 March 2020 11:03 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas-3272bis-design-team@ietfa.amsl.com
Delivered-To: teas-3272bis-design-team@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D37933A16EE for <teas-3272bis-design-team@ietfa.amsl.com>; Wed, 11 Mar 2020 04:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 46QkprxiGP5f for <teas-3272bis-design-team@ietfa.amsl.com>; Wed, 11 Mar 2020 04:03:23 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 9BA643A16F0 for <teas-3272bis-design-team@ietf.org>; Wed, 11 Mar 2020 04:03:22 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 02BB3KNr020875; Wed, 11 Mar 2020 11:03:20 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 51D9E22040; Wed, 11 Mar 2020 11:03:20 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs3.iomartmail.com (Postfix) with ESMTPS id 3CB812203C; Wed, 11 Mar 2020 11:03:20 +0000 (GMT)
Received: from LAPTOPK7AS653V (236.red-2-139-174.staticip.rima-tde.net [2.139.174.236]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 02BB3JUr008187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 Mar 2020 11:03:19 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Loa Andersson' <loa@pi.nu>
Cc: teas-3272bis-design-team@ietf.org
References: <d5486fac-fc39-b948-9648-ec355c6895bf@pi.nu>
In-Reply-To: <d5486fac-fc39-b948-9648-ec355c6895bf@pi.nu>
Date: Wed, 11 Mar 2020 11:03:18 -0000
Organization: Old Dog Consulting
Message-ID: <05ec01d5f794$ac253e00$046fba00$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQMJZWeIS3Z2Sl+y4DMpGuDfY3fb/aXcXjfQ
Content-Language: en-gb
X-Originating-IP: 2.139.174.236
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25282.006
X-TM-AS-Result: No--8.433-10.0-31-10
X-imss-scan-details: No--8.433-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25282.006
X-TMASE-Result: 10--8.432900-10.000000
X-TMASE-MatchedRID: EMyCvCfVN1HxIbpQ8BhdbKCkgp86+voPqV3VmuIFNEtQKAQSutQYXB/p oFKGNxRgnD28w6kaUWUte+ObS/frGNcUNjoF7YuVmE9Jt7idrkyPzv8sr7ayo+z1WiSjvY2p0u5 faGP8ztSAHFxRgNqUtHj6qT/ioouPQSWnAG0egjEHz0YoejTeds4IwNH89rogT0IkL8xYhniEeE SyuRtYoSOTmcnjeRr9jG9RmeLPwxxhTSvDZHacpij8QbJIB1s2A9+f7dIjW4QINpIFnbd6mv6RO KSr3u5/0M5qACEBibN08uEQhOtSSDAvdQPMSC1zLGDmqzfHOB+/8f2bnaA7639nRLJB1yYQQIFN 0f9asdZfMjbJWOZK4shPMTURn101KdFN4fct4yzKrRqi7UPpbJS6BV7zHbBSmawSaFZ/FjTwDLs fS3OfPBGwc34Ib44GGtTYRuur4aMm2WWAELvR+X3O3F/Nshx5jiWciALpTNOxLSxkQHtzxkLgFm aW9jiQlrZcexeW6NcoZkddWg60ej6EcWhhvxcYNzdIxcQ9GkN9LQinZ4QefBrZLyuS+0VxsOzOn crmCoP3FLeZXNZS4DjAdLIal4R6feVIulezf5TmmpK25enXF52Q/skAQpf0P7UQ4jC795e0tkNm ueawEw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-3272bis-design-team/RM6C-1fUvuVL-_8Dss7R-RY-M48>
Subject: Re: [teas-3272bis-design-team] First spin on section pushed
X-BeenThere: teas-3272bis-design-team@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <teas-3272bis-design-team.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-3272bis-design-team>, <mailto:teas-3272bis-design-team-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-3272bis-design-team/>
List-Post: <mailto:teas-3272bis-design-team@ietf.org>
List-Help: <mailto:teas-3272bis-design-team-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-3272bis-design-team>, <mailto:teas-3272bis-design-team-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2020 11:03:25 -0000
How do you mean "pushed"? Are you working on the git version? I'm not sure how many times I have to say this but, we have abandoned git as a tool for this work. A -----Original Message----- From: Loa Andersson <loa@pi.nu> Sent: 11 March 2020 10:35 To: Adrian Farrel <adrian@olddog.co.uk> Cc: teas-3272bis-design-team@ietf.org Subject: First spin on section pushed Adrian, DT, I have pushed a first version of my meddling on section 2. From the start I planned to do three things - I have cleaned up some text, i.e. I read until I reached a sentence or word that I I did not understood, consulted other drafts and dictionaries and re-wrote I also think that lists are more readable that lists in flowing text, i.e. We have the following examples * blaabla blabla blobby * bip bap bim * crish crash crush is better that We have the following examples (1) blaabla blabla blobby, (2) bip bap bim, amd (3) crish crash crush. So there are a lot of lists, ifthere is a strong desired to get the original format back, I can do that. I also avoided numeric-bullets in the list, since it was way to easy to confuse list bullet 3. with section chapter 3. - I have not yet addressed the issue of what has happened over the 18 years since this document was published, will do that. - We aslo need to push some more modern examples in, I see what I can do, I've added some MPLS/GMPLS, but I need to think more. But thinks like PCE, SPRING (SR) , DETNET (determinism) and TEAS and should probably go somewhere. Data Center and centralized control. The I have a problem with part of section 2.5 2.5. Implementation and Operational Context "The operational context of Internet traffic engineering is characterized by constant changes which occur at multiple levels of abstraction. The implementation context requires effective planning, organization, and execution. The planning aspects may involve determining prior sets of actions to achieve desired objectives. Organizing involves arranging and assigning responsibility to the various components of the traffic engineering system and coordinating the activities to accomplish the desired Traffic Engineering (TE) objectives. Execution involves measuring and applying corrective or perfective actions to reach and maintain wanted TE goals." I don't understand the implication of "prior goals" I also wonder why Traffic Engineering (TE) appears for the first time here (25 pages into the document), should we push it to the terminology section. WHile I'm at it the layout of the terminology section could be improved, e.g.: Traffic flow - A stream of packets between two end-points that can be characterized in a certain way. A micro-flow has a more specific definition A micro-flow is a stream of packets with the same source and destination addresses, source and destination ports, and protocol ID. /Loa -- Loa Andersson email: loa@pi.nu Senior MPLS Expert Bronze Dragon Consulting phone: +46 739 81 21 64
- [teas-3272bis-design-team] First spin on section … Loa Andersson
- Re: [teas-3272bis-design-team] First spin on sect… Adrian Farrel
- Re: [teas-3272bis-design-team] First spin on sect… Loa Andersson
- Re: [teas-3272bis-design-team] First spin on sect… Adrian Farrel