[Teas] RFC3272bis -- Design Team

Vishnu Pavan Beeram <vishnupavan@gmail.com> Tue, 18 December 2018 04:43 UTC

Return-Path: <vishnupavan@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 DDD8713107B; Mon, 17 Dec 2018 20:43:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 86B4fykEq29m; Mon, 17 Dec 2018 20:43:17 -0800 (PST)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (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 86A2F131074; Mon, 17 Dec 2018 20:43:17 -0800 (PST)
Received: by mail-pg1-x534.google.com with SMTP id m1so5568707pgq.8; Mon, 17 Dec 2018 20:43:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=3CA3jglgKfxqJ9pREnvH3O8ht1Id/BZ+8KNCTkKmE1s=; b=bSrGgJQy7+x1vDG7A3K7mIUWEFItXoC6jCcVwmcvfMXGwx+jPXFgZDUF2VlxKZVxtC uG+IBY6ahIxis3MgT/TKt2CMYHCKsbKs22VKa1+Bg8Wrxl0nMJj1OrtxENkZ6lW6Iwf5 wMBY6wV4RdEvD9ku0XDRqnBf+OLtF+AKcPAjAF2u9phKvEbdxK/+KUkAA7tVbHw1xAU1 7rIo/+sn9vLqM+mZ5qtzjHbXA5V46cHt/nAAZ+mBBB05KbHCMk2yGCDFt4xj8b14yQbE DhuSGig/LoTRdq3oV9TqialU/tCht0vtzqMukOcWAvt2J/o7nlH7p9UXwMhRS4s6l72c 2Hnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=3CA3jglgKfxqJ9pREnvH3O8ht1Id/BZ+8KNCTkKmE1s=; b=WQpNVbXmUxhv36ga+x1T+Zj024+PmVbn7vH2u0jszcoFcnDZ3Z5dKFgxa0u0GLqtU8 973C2KN97U2R7hkBz2YQeKSWKJHk5RiXuMkxbxJUS0a2PzCsW8AkTIkTabT+Km4vY/UA fqSMGH6bxA22XnSHs0V5+L7fLjbJSFGl36txcPeAsseuel6c6BfajXx44fojdObOFAjI VjEZwanBpKNJSEzONxKTI9IzbFCDupZbZ2WctRPNuk8uiEPEi/LFtiHC/ZGW2UNcL+hM mtf8I1H8CcazwEUruex+evGXHDtRZfzRr3XllI1Wj7ovEyfJH2WtbHwjgy44E/GEkYE7 dhOQ==
X-Gm-Message-State: AA+aEWZC5l/GF7PYuQe/c3iWnu6KkP7+hObmndMmLd5WZOQnX05/0XP+ NDhOkSbxHvaKxY/ukXDF3iDYxQSJcvK36Nu7KAl4DuC6Ysk=
X-Google-Smtp-Source: AFSGD/W+ZVXhwJH4fV3+0TmPRFEjmfeduwCDnBJTVFnXQNzEZ70buJhlZ9hiPV4jtx0MiOaR4vofXVZK0VFUzc+r/N8=
X-Received: by 2002:aa7:80d7:: with SMTP id a23mr15098863pfn.86.1545108196717; Mon, 17 Dec 2018 20:43:16 -0800 (PST)
MIME-Version: 1.0
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Mon, 17 Dec 2018 23:43:05 -0500
Message-ID: <CA+YzgTvnBe+M=w6rFcShQkg9Xa9m1TUvPrbmr=zuV+kcfxJOHg@mail.gmail.com>
To: TEAS WG <teas@ietf.org>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003477b8057d4489dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/5h8rtdmarv6G1Df7ehH0yUpgITU>
Subject: [Teas] RFC3272bis -- Design Team
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, 18 Dec 2018 04:43:19 -0000

WG,

RFC3272 (Overview and Principles of Internet Traffic Engineering, May 2002)
has served us well over the years, but (as mentioned during the WG session
in Montreal) we believe that it is time to revisit this document and cover
some of the newer TE principles, paradigms, functions and requirements in
detail.

We are looking to establish a short lived Design Team to put together an
RFC3272bis document. The goal of the Design Team will be to present planned
changes in Prague and publish a draft in time for discussion in Montreal
(IETF 105, July 2019), with an expectation that the document will become a
WG draft post the Montreal session.

If you would like to be a part of this Design Team, please do reach out to
the chairs (off-list) before Jan 7th, 2019.

Regards,
Pavan and Lou