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

Gyan Mishra <hayabusagsm@gmail.com> Thu, 07 July 2022 16:39 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 A309BC159485 for <teas@ietfa.amsl.com>; Thu, 7 Jul 2022 09:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 (2048-bit key) header.d=gmail.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 nu5aC3xk9NHM for <teas@ietfa.amsl.com>; Thu, 7 Jul 2022 09:39:23 -0700 (PDT)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 E0E23C157B5F for <teas@ietf.org>; Thu, 7 Jul 2022 09:39:23 -0700 (PDT)
Received: by mail-pg1-x534.google.com with SMTP id s27so19470296pga.13 for <teas@ietf.org>; Thu, 07 Jul 2022 09:39:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6HJec7kWxeDXdj/rxUYlmgiRbvazkAWSeddZAUOjJ/k=; b=WIO/rHr+uubI0M/MMqSP1RtsxL9EegK3iWpeXBDqTdtddntD1zWHzjLST/OK4BJJJz pZVZ0Gwyim34gSdewIwT/0ll/FwS542jRBkMv7R0Qv8SEp/A9toaRN9AMry5aUfEBQlS 0pvQkinbJoGkiTGs3ruTcbM5d4W7G+tB1SvMs5mH5al4niq1FeCP8pxOrpkIR4TeOQtQ /+pxLVRlqADM9AxrTFWX2YqWtcP73lLsAVkXD+WlE+vbFVHWQFToeuLn9ymLKrobZdV3 zkZzSAz2hPPt1rWZYLrhO0z8kA50fCCOTF/4GXRPWeiavu54Z9mf6kuAHXToy5PqEBcZ WdGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6HJec7kWxeDXdj/rxUYlmgiRbvazkAWSeddZAUOjJ/k=; b=puE1gXi1BBhlX+eT9XdBsIZf094mMP3BGRvUXk2jEt7v0BjOg59gJy21YLnb1VjG12 D3Sx68myo7vRXcdRlimbKj6ewJguLrHfZYzkMQXc1aFETkg5FRqcgqhhsSaQNzlqgjft oTVOzU9yTgcR4UnqfiNpVPTA1Vc1lnTFhGw3p+Y5VhTcJXbtME/Ss5RCises1VZke8F4 idCQKC7ZjQd0NUk06iJZLq3fBlImQ3+BRYt3+WOasZwmroypzyDCjS3wpYIfmHeDYmMg pTP/IO/9WK3RxwsTLWGUK8FR7hBmMhME0CMPhH8VYeUfolj18wHLUY48dEB9wPC3KKz/ JOSg==
X-Gm-Message-State: AJIora8sbLorjQjtFTgUD4vNzO7cU3T2W3OiV+/o3cyYe3OONBBfFbFc EsdJqK8pOsKJk7W+Q8HP+Tn+UntcYjHpCW4/uMD5qAWH
X-Google-Smtp-Source: AGRyM1scoH9UVZyXNvO1stTV2hSjpP8mbcZpA89NqsWvXQQCpyTmncLPl3ncje5npgbwI3cbWNMGp069n7w5P3L0x3I=
X-Received: by 2002:a17:90a:d581:b0:1ef:a1d5:9904 with SMTP id v1-20020a17090ad58100b001efa1d59904mr6265774pju.93.1657211962885; Thu, 07 Jul 2022 09:39:22 -0700 (PDT)
MIME-Version: 1.0
References: <019b01d891ef$bb4f3050$31ed90f0$@olddog.co.uk> <0fd13ba5-4905-2cca-e72d-23d51d6306ba@joelhalpern.com>
In-Reply-To: <0fd13ba5-4905-2cca-e72d-23d51d6306ba@joelhalpern.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Thu, 07 Jul 2022 12:39:12 -0400
Message-ID: <CABNhwV1+r7wNU+VYZjVHn2Y9ksAFemBj4+KsfDsPK1yvJ6YROw@mail.gmail.com>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: TEAS WG <teas@ietf.org>, adrian@olddog.co.uk
Content-Type: multipart/alternative; boundary="0000000000005d8b1c05e339ba48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/RAXm7z4uEPxqu2y1lDF0Iy8IEJk>
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 16:39:27 -0000

I agree with Joel on deleting as well  Appendix A and B.

Updating Appendix A with history up to the present is almost like bringing
the body back into the Appendix with pointers.

Seems to me as repetitive.

For the SDO list of TE related work as is out of scope as well and it seems
to be stated in the abstract stating latest relevant work in the IETF.

   This work was first published as RFC 3272
<https://datatracker.ietf.org/doc/html/rfc3272> in May 2002.  This
document
   obsoletes RFC 3272 <https://datatracker.ietf.org/doc/html/rfc3272>
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.


I think it makes sense to delete Appendix B.

Thanks

Gyan

On Thu, Jul 7, 2022 at 10:19 AM Joel Halpern <jmh@joelhalpern.com> wrote:

> 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 listTeas@ietf.orghttps://www.ietf.org/mailman/listinfo/teas
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
-- 

<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*