IETF Logo Mail Archive

Re: IP Traffic Engineering

Gyan Mishra <hayabusagsm@gmail.com> Fri, 27 September 2019 00:21 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B2DB1200B3 for <rtgwg@ietfa.amsl.com>; Thu, 26 Sep 2019 17:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_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 Hdecr4chiIS2 for <rtgwg@ietfa.amsl.com>; Thu, 26 Sep 2019 17:21:29 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 9EC0C1200B5 for <rtgwg@ietf.org>; Thu, 26 Sep 2019 17:21:29 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id w2so592412qkf.2 for <rtgwg@ietf.org>; Thu, 26 Sep 2019 17:21:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HAqSYaE7XP90VaQUl2QInuUaWophjMjE2bSCNsPjSOQ=; b=g3UICPa3PSpDkq/3aYVqZfR3+Rz/cBoCvpNfIXgRiHYNuNyd8Bze9kqkamjlka6kY8 dFIfZAXe33nUC56AoCB+wD3KaP9Y6yAKa/omCEIf3cMFmdwyES6UYzd6byKGWX+oZ6oE YAjTVjZegWTol90i+RZg7CzNuS7Pb5X5chhcxVcTk/26gdaYgo+KdaQGKXg3v3xmwU+K LWVr/YwnRr8dFFsBX0yiqQQx+OpY574WfzNAOprbZe7DFjI9v6i2sEPm9UXeRJnz5934 qANGD/jmUuU3n3VS/OPdK4Uh33/U5RgQat4MHmJ9ynV+TU7xJJR/EthFV9ZPSzouGyKf IQCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HAqSYaE7XP90VaQUl2QInuUaWophjMjE2bSCNsPjSOQ=; b=eebX4+uuTR0zxQrfdn4NUHWC5czkw66WnD5ZHwEEEL2mN++t1Jd2HBE/Lk5KcfT/iG r6oVTKoi3Hnv0WnSyaX4EVGBYnrjUrlP4R9ONec500DKlLseHix1YSTCmCvtBpEiPETL A0624WtwuKwhJi8FcZR8QOf1/09MfDbSKYHsekJS5wpU1IfCxVFQme3XcWFOrul+X9IT LnJ+oEy6HU8FXV6DpLiPePHrsoj2FjFp5g+3FEO52QV7PeHwQg1VagenEc+P03oCehBc AcjDW5hMTNODu2UgJR3GC9qNkpTAcxfcrBFCRxdrAhMPqDkrh8EIeBQmZHl+1lH64fwQ A6HA==
X-Gm-Message-State: APjAAAWH28XkVeukjhs+T4/yNIBilV10AnrDT+Misg53T/o+SD+CcMOw p8s+KbA8G5KpEfJaUoElb4Fz6c4R
X-Google-Smtp-Source: APXvYqy6lNvN/WPgd6Y1t5d94upxNduRr4YZuFVPGEgs03XPw+tVfX8zdrSmNZacC+Q2NBoBWJklmA==
X-Received: by 2002:a37:57c6:: with SMTP id l189mr2017645qkb.246.1569543688190; Thu, 26 Sep 2019 17:21:28 -0700 (PDT)
Received: from [192.168.1.213] (pool-72-83-194-140.washdc.fios.verizon.net. [72.83.194.140]) by smtp.gmail.com with ESMTPSA id c201sm411048qke.128.2019.09.26.17.21.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Sep 2019 17:21:27 -0700 (PDT)
From: Gyan Mishra <hayabusagsm@gmail.com>
X-Google-Original-From: Gyan Mishra <hayabusaGSM@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-8CC6CD1B-837D-470D-9252-AB7132C9B2B4"
Mime-Version: 1.0 (1.0)
Subject: Re: IP Traffic Engineering
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <4e6db4e3-f2a7-ad08-3b94-524adadf5ff9@labn.net>
Date: Thu, 26 Sep 2019 20:21:26 -0400
Cc: Robert Raszuk <robert@raszuk.net>, RTGWG <rtgwg@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <C3417880-586F-421E-AED2-3CE4B93FF45A@gmail.com>
References: <156953754350.31990.16627132446644830194@ietfa.amsl.com> <CAOj+MMEEn9uGH-qjapYw2guxnipcYE0u-3PH6wWPECiCQDhXiQ@mail.gmail.com> <4e6db4e3-f2a7-ad08-3b94-524adadf5ff9@labn.net>
To: Lou Berger <lberger@labn.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/4q0gKA30DjSGKqLl79UtVCOYrO0>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 00:21:32 -0000

Or maybe PCE WG

Sent from my iPhone

> On Sep 26, 2019, at 8:10 PM, Lou Berger <lberger@labn.net> wrote:
> 
> I suspect this is in the scope of the TE Architecture ... (TEAS)  WG...
> 
>> On 9/26/2019 7:06 PM, Robert Raszuk wrote:
>> Dear RTGWG,
>> 
>> I just submitted a document where I present new perspective on traffic engineering for IP networks. As the scope of the new architecture and deployment target does not fit any other working group I decided to submit it to RTGWG. 
>> 
>> Comments, opinions, contribution - very welcome !
>> 
>> Kind regards,
>> Robert. 
>> 
>> - - - 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> 
>> 
>>         Title           : IP Traffic Engineering Architecture with Network Programming
>>         Author          : Robert Raszuk
>>         Filename        : draft-raszuk-rtgwg-ip-te-np-00.txt
>>         Pages           : 22
>>         Date            : 2019-09-26
>> 
>> Abstract:
>>    This document describes a control plane based IP Traffic Engineering
>>    Architecture where path information is kept in the control plane by
>>    selected nodes instead of being inserted into each packet on ingress
>>    of an administrative domain.  The described proposal is also fully
>>    compatible with the concept of network programming.
>> 
>>    It is positioned as a complimentary technique to native SRv6 and can
>>    be used when there are concerns with increased packet size due to
>>    depth of SID stack, possible concerns regarding exceeding MTU or more
>>    strict simplicity requirements typically seen in number of enterprise
>>    networks.  The proposed solution is applicable to both IPv4 or IPv6
>>    based networks.
>> 
>>    As an additional added value, detection of end to end path liveness
>>    as well as dynamic path selection based on real time path quality is
>>    integrated from day one in the design.
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-raszuk-rtgwg-ip-te-np/
>> 
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-raszuk-rtgwg-ip-te-np-00
>> https://datatracker.ietf.org/doc/html/draft-raszuk-rtgwg-ip-te-np-00
>> 
>> 
>> 
>> 
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email