Re: [Teas] WG adoption poll - draft-dt-teas-rfc3272bis

Adrian Farrel <adrian@olddog.co.uk> Tue, 30 June 2020 21:02 UTC

Return-Path: <adrian@olddog.co.uk>
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 C66B33A0857; Tue, 30 Jun 2020 14:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 DHRocDfpeeqF; Tue, 30 Jun 2020 14:02:21 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 2B6F33A0859; Tue, 30 Jun 2020 14:02:19 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 05UL2HbA031779; Tue, 30 Jun 2020 22:02:17 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3A8A42204E; Tue, 30 Jun 2020 22:02:16 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS id 253732204C; Tue, 30 Jun 2020 22:02:16 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.113.100.254]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 05UL2Fgx008310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Jun 2020 22:02:15 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Dhruv Dhody' <dhruv.ietf@gmail.com>, 'Vishnu Pavan Beeram' <vishnupavan@gmail.com>
Cc: 'TEAS WG Chairs' <teas-chairs@ietf.org>, 'TEAS WG' <teas@ietf.org>
References: <CA+YzgTt3fWp7FJ=VchzWGChxcSq6GYNuwseM1zJqByxm9CKKXQ@mail.gmail.com> <CAB75xn6pgMzE8nsqVewxAAxmNu1S=myJbS-27hpjQwJOBFd6EQ@mail.gmail.com>
In-Reply-To: <CAB75xn6pgMzE8nsqVewxAAxmNu1S=myJbS-27hpjQwJOBFd6EQ@mail.gmail.com>
Date: Tue, 30 Jun 2020 22:02:14 +0100
Organization: Old Dog Consulting
Message-ID: <002401d64f21$bb88d430$329a7c90$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQF8mBxKPsHsWejWq0Xf7Uh+PFlHFALHVCS4qY7XtGA=
Content-Language: en-gb
X-Originating-IP: 87.113.100.254
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-25514.002
X-TM-AS-Result: No--19.582-10.0-31-10
X-imss-scan-details: No--19.582-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25514.002
X-TMASE-Result: 10--19.581700-10.000000
X-TMASE-MatchedRID: z5DqD3Ob673xIbpQ8BhdbPVY7U3NX8JgvHa+hRvAUH2nRvssirgAK1ze gaTRgHDQaGl+ugcBSPTcK8dpI2l61lx82Dll5goXC4s/hE51YdU1X1Ls767cpvvVzx/lhjlVwXL S0LkPCahqtcFyWV8w2qnRne1AoPgPSVk5Oq20YbmHpfBSejqaSUjEWwwu715stXl9IxEPXOroFK ygcaLrBeWAB5Xe+PJGlb9/RDYAaWiiQBlI5LgsFZKOhFK/JknQ0nXvwjW2mSWKXNybanokT00eP cPkZVp/1vbSSQ7LlvGS2HehsT2UYLF6nptaEfP/Hbdv6Uke88AhXHiVbGfuY9pSUoaJ2MP7O3fT +Qx3V4twR3kDso7qD5k+LFtTeIQncdV1fv9AzTBHwu6JXQlo7vi5Y2zeHO9DuhsYdHl6O2u0CmL k+JEYOs4uXWEI31o5LZn3hGAjnii+KpxDEf1mdmgws6g0ewz2EVLbw+/8oMVo5YsPsbyLXVOiwG vrPOJI/ye/3Hc9K1qf9j8xhbvJP8kwYM+oZdHXqa6SJk58+La6hgVvSdGKo23D6f6IpbLIIvLBZ n8IAhiWPrJR4gE9bqW6CtebkgpwTpxma7wJmYrH9K2ZqHQWln0tCKdnhB58vqq8s2MNhPAL4KbF 8qbADAzKt8/2P4LVvECLuM+h4RB+3BndfXUhXQ==
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/H_SNR9jJpA1uf9He-YPFY3TjiHg>
Subject: Re: [Teas] WG adoption poll - draft-dt-teas-rfc3272bis
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Jun 2020 21:02:25 -0000

Hi Dhruv,

Thanks for being interested. We can wait for a review, but don't feel you
have to do it in one pass: it is an enormous document.

I think the "changes since last version" will need to be descriptive text
rather than a section-by-section analysis. I'll add a place holder for it.

Your question on 1.2 is good: and I turn it right back at you! What do you
think?

Your pointer for 4.1.3 is good and will be worked on.

A

-----Original Message-----
From: Teas <teas-bounces@ietf.org> On Behalf Of Dhruv Dhody
Sent: 30 June 2020 15:45
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>; TEAS WG <teas@ietf.org>
Subject: Re: [Teas] WG adoption poll - draft-dt-teas-rfc3272bis

Hi,
Thanks to Adrian & DT for this work!

I wanted to do a substantial review of the I-D but it looks like that
has to wait for a later date :)

I managed to skim through it focusing on the changes and caught
nothing that should impede the adoption of this work.
I would have liked to see a section listing changes since RFC 3272
(but not sure how practical that is).
The diff-tool [1] was somewhat useful.

Two random points -
=
- Query: In section 1.2 -

   The key elements required in any TE solution are:

   1.  Policy
   2.  Path steering
   3.  Resource management

Does that mean any solution that just does 1 and 2 and doesn't do 3 is
not TE? Would SR-Policy and BIER-Tree engineering fall under that?
Note that we have SR-MPLS covered (rightfully so) in Section 4.1.14
under IETF techniques. I am wondering if partial-TE is a thing?
=
- Section 4.1.3, this needs to be updated -

   A number of IETF working groups have been engaged in activities
   related to the RSVP protocol.  These include the original RSVP
   working group, the MPLS working group, the Resource Allocation
   Protocol working group, and the Policy Framework working group.
=

Thanks!
Dhruv

[1]
https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=rfc3272&url2=draft-dt
-teas-rfc3272bis-11

On Tue, Jun 16, 2020 at 11:09 PM Vishnu Pavan Beeram
<vishnupavan@gmail.com> wrote:
>
> All,
>
> This is start of a two week poll on making
> draft-dt-teas-rfc3272bis-11 a TEAS working group document.
> Please send email to the list indicating "yes/support" or "no/do not
> support". If indicating no, please state your reservations with the
> document. If yes, please also feel free to provide comments you'd
> like to see addressed once the document is a WG document.
>
> The poll ends June 30th.
>
> Thanks,
> Pavan
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas