Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt

Gyan Mishra <hayabusagsm@gmail.com> Sat, 01 May 2021 18:50 UTC

Return-Path: <hayabusagsm@gmail.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 1BE753A24A9; Sat, 1 May 2021 11:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2JWKKdxepENJ; Sat, 1 May 2021 11:50:23 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35A1D3A24A7; Sat, 1 May 2021 11:50:22 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id f6-20020a17090a6546b029015088cf4a1eso1050903pjs.2; Sat, 01 May 2021 11:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=83ewtY59E0OCUvwgaF16EmPvsnpt+8BKcEeAF/IhQYk=; b=levbzZqtNXNa8i3nJjqXLRDlQBcUCn4ELQRqyedYDeAISORe+en+2KO9QIneWmtK5c p7tAomAmCGLwKCvrMwHqXRdg24/iq/8Bqk7JYdxZn9ZWfo+NmAPtREDRYnd5DgmCo7jH sKAPtxp8NIpzUMgwtRj/e0AkYztrO6BHqHJB5JxDaVOA3H7YwkhiaR+HI7dNqis8AVHp ucBnU0SYgY5/I/Y9A97EDmS1akv/LTXN3pJZv9ztAty8alU5Oupwb0UXAVs4qFteu3qo FiGzxYJSR3PB8IuN+irvE6uvk7m1qAlX+/meEwMaQwnNmy6diglFJbr/dfsUFrZxuqWG RWFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=83ewtY59E0OCUvwgaF16EmPvsnpt+8BKcEeAF/IhQYk=; b=mgPWbekzRkFzGiQ4fBAi5IuBxa6H08yZ+d89NLQt8bJSqJujPfobS5z10v1PQ3d56z PAI7g34PUaCHr1KlRS0DTf3IFEQ+/eUbcgTRZWFnYk1c8XUy5nYML3tRFChQjAT66MuJ qZj18x7flcvhCHK7gYeHM4dDj4h1ta4sT0zG6CykmvjnwboC4phiPgNV9LM19up2ReQj hQthwnD3winFgq0vHk8g588f1KNl7xMF7xEradkRF6XJEtEtgx4RbrhiacHofjxl4W1w tD/UKvypfcEfQZJX5XRrE+rWkdMF9fFvHnxcUyTE0DZ0SlwQWZsYn7cdEq+LpbHIfJKP 52mg==
X-Gm-Message-State: AOAM533A73q+5JGV65C6lM9CoCoTeVwWGCQFVBWsH7o8deXRxp+T1dp5 K36m/HIselWw0BHcqQ/5KOAWzQ2AcNmqLX0xzZqOt0u4Yr4=
X-Google-Smtp-Source: ABdhPJxwWNYdRzapu3Vt4l6zBnU/OUlx3nju2MCge0Mobv9md8LIIFsnAZQ0tMYhPO6rJXBkRAXOYty1TqMBV8ZAY1M=
X-Received: by 2002:a17:90b:88c:: with SMTP id bj12mr11476723pjb.112.1619895021843; Sat, 01 May 2021 11:50:21 -0700 (PDT)
MIME-Version: 1.0
References: <161781991426.15865.4191431758501856588@ietfa.amsl.com> <06a201d72be3$8e1e9b20$aa5bd160$@olddog.co.uk> <CABNhwV19LDNZa0SjJ9N_ee0P0Hbqr4MdHPTahR-VM78O6UWUGQ@mail.gmail.com> <CABNhwV0W8AYODXXg1XEw5CBKR+ivOos0gJy33fqanLC1UWHo7w@mail.gmail.com> <08e801d72d26$a5f764e0$f1e62ea0$@olddog.co.uk>
In-Reply-To: <08e801d72d26$a5f764e0$f1e62ea0$@olddog.co.uk>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 1 May 2021 14:50:01 -0400
Message-ID: <CABNhwV1suO-bbSU9gCVBKKVwdKN5jiWAzx1dGyyCMHPLOSY7fQ@mail.gmail.com>
To: adrian@olddog.co.uk
Cc: TEAS WG Chairs <teas-chairs@ietf.org>, teas@ietf.org
Content-Type: multipart/related; boundary="00000000000059db9505c14933c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/qo9Uo1iVR4f1-U_U1RE0-6KSU4Y>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
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: Sat, 01 May 2021 18:50:29 -0000

Hi Adrian

I reviewed the latest revision 11 and it looks excellent and well done by
all the feedback from WG thus far.

I am still in the process of building some minor updates as it relates to
design and architectural flavors of TE deployments as within Verizon we
have a variety of deployments and the goals are different in each
environment public internet or private MPLS / SR or internal
implementations.

The major difference in implementation is the goal of congestion control
and avoidance versus traffic flow bandwidth management as the goals and
objectives are very different and there is also as well a mixture hybrid of
both concepts as well.  Also some thoughts on what works well and what does
not and the critical component of overall good network capacity planning
and based on the congestion control or avoidance design that if your have
enough of capacity for high bw flows the amount of TE is minimal if any.
Also idea of leveraging IGP based metrics to provide bandwidth delay
framework which eliminates that function to be provided by TE concept
framework which also limits the amount of TE necessary.

I should be completed in about a week maybe less.

Kind Regards

Gyan

On Fri, Apr 9, 2021 at 5:56 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> Come one, come all [1]
>
>
>
> Yes. Let’s set end of April for everyone. Then I can do an update and then
> the chairs can last call it.
>
>
>
> Adrian
>
>
>
> [1] Moto of the No 253 (Hyderabad State) Squadron, Royal Air Force.
>
>
>
> *From:* Gyan Mishra <hayabusagsm@gmail.com>
> *Sent:* 09 April 2021 03:46
> *To:* adrian@olddog.co.uk
> *Cc:* TEAS WG Chairs <teas-chairs@ietf.org>rg>; teas@ietf.org
> *Subject:* Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
>
>
>
>
>
> Hi Adrian
>
>
>
> End of April works for me better as well if you are good.
>
>
>
> Thanks
>
>
>
> Gyan
>
>
>
> On Thu, Apr 8, 2021 at 10:42 PM Gyan Mishra <hayabusagsm@gmail.com> wrote:
>
>
>
> Hi Adrian
>
>
>
> I will plan to complete the review by tomorrow.
>
>
>
> Sorry for the delay.
>
>
>
> Kind Regards
>
>
>
> Gyan
>
>
>
> On Wed, Apr 7, 2021 at 3:24 PM Adrian Farrel <adrian@olddog.co.uk> wrote:
>
> With this version I have filled in the remaining TBDs:
> - small section on intent-based network
> - small section on multi-layer TE (thanks, Lou, for the suggestion)
> - change log from 3272
>
> As far as I'm concerned this document is complete modulo review comments.
>
> It *really* needs review, but I can't force you!
> Maybe you can look at the sections of special interest to you?
> Maybe the original Design Team could take another look?
>
> Otherwise: time for WG last call?
>
> Thanks,
> Adrian
>
> -----Original Message-----
> From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
> internet-drafts@ietf.org
> Sent: 07 April 2021 19:25
> To: i-d-announce@ietf.org
> Cc: teas@ietf.org
> Subject: I-D Action: draft-ietf-teas-rfc3272bis-11.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Traffic Engineering Architecture and
> Signaling WG of the IETF.
>
>         Title           : Overview and Principles of Internet Traffic
> Engineering
>         Author          : Adrian Farrel
>         Filename        : draft-ietf-teas-rfc3272bis-11.txt
>         Pages           : 91
>         Date            : 2021-04-07
>
> Abstract:
>    This document describes the principles of traffic engineering (TE) in
>    the Internet.  The document is intended to promote better
>    understanding of the issues surrounding traffic engineering in IP
>    networks and the networks that support IP networking, and to provide
>    a common basis for the development of traffic engineering
>    capabilities for the Internet.  The principles, architectures, and
>    methodologies for performance evaluation and performance optimization
>    of operational networks are also discussed.
>
>    This work was first published as RFC 3272 in May 2002.  This document
>    obsoletes RFC 3272 by making a complete update to bring the text in
>    line with best current practices for Internet traffic engineering and
>    to include references to the latest relevant work in the IETF.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-teas-rfc3272bis/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-teas-rfc3272bis-11
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-11
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-rfc3272bis-11
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
> --
>
> [image: Image removed by sender.] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
> *M 301 502-1347*
>
>
>
> --
>
> [image: Image removed by sender.] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
> *M 301 502-1347*
>
>
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*