IETF Logo Mail Archive

RE: IP Traffic Engineering

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 27 September 2019 07:09 UTC

Return-Path: <adrian@olddog.co.uk>
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 B60611200B9 for <rtgwg@ietfa.amsl.com>; Fri, 27 Sep 2019 00:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.622
X-Spam-Level:
X-Spam-Status: No, score=-2.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.026, 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 sfSKv791OCvT for <rtgwg@ietfa.amsl.com>; Fri, 27 Sep 2019 00:09:37 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (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 0D7A51200B7 for <rtgwg@ietf.org>; Fri, 27 Sep 2019 00:09:36 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8R79Xsd022939; Fri, 27 Sep 2019 08:09:34 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 868582203B; Fri, 27 Sep 2019 08:09:33 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id 711832203A; Fri, 27 Sep 2019 08:09:33 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.72.158]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8R79J7T020400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 27 Sep 2019 08:09:29 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Robert Raszuk' <robert@raszuk.net>, 'RTGWG' <rtgwg@ietf.org>
References: <156953754350.31990.16627132446644830194@ietfa.amsl.com> <CAOj+MMEEn9uGH-qjapYw2guxnipcYE0u-3PH6wWPECiCQDhXiQ@mail.gmail.com>
In-Reply-To: <CAOj+MMEEn9uGH-qjapYw2guxnipcYE0u-3PH6wWPECiCQDhXiQ@mail.gmail.com>
Subject: RE: IP Traffic Engineering
Date: Fri, 27 Sep 2019 08:09:16 +0100
Organization: Old Dog Consulting
Message-ID: <01cd01d57502$81302c60$83908520$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01CE_01D5750A.E2F70560"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQItM2293xL5u2hvVIJi21pzMTBDhgGO+VjVpoMkIEA=
Content-Language: en-gb
X-Originating-IP: 87.112.72.158
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-24936.005
X-TM-AS-Result: No--17.164-10.0-31-10
X-imss-scan-details: No--17.164-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24936.005
X-TMASE-Result: 10--17.164400-10.000000
X-TMASE-MatchedRID: I31hiQfYWUPxIbpQ8BhdbLE811R1QfVapQH4ogtVQP0jRiu1AuxJTCko 1dMsTXMPOBnw4dMrzNOzIzPbbR0Bf2FSCbxk53PflVHM/F6YkvQ+8WcgUjQUwr142xO28EPeIN/ MbXxx+S29SRpUa5kjk0ilX3bPKz8IWkY/wO9j0sj7gWP0TNHLHJ65wfbk2wOLqx3Pdu5ede9aat ivxJpZNZMh3n0lEatF4slG5grepOhC5Wu7ciVZiKx4uE6v1cE6IE/7F7Rl639rRM6wvXgDaeryy xH88VhiWUPf74dX4h98a7wSyqJuYtllERdS6V4uGJADAbBHGUyCjlNkELBqNLztptzb+OwAv/Sm Q1tCm5R0T8LxrQX9uJmUk3gI3eML5TDi4+38dPatY/LInB7QgZoiESsm3R0sFBQ5IKls/A7gakF mO4shHoDGegIhjJ5nPvi3qqjYFHHH9Stknh6b9fLHPaGCgb3t9pLnYtQ99xKbuvvgpZZI+WTbiY p2G5E1NtrqBJtuOX5YFBU0+2PUKWE2dpl/p8cMCLQsumV/5S+CFkqa43bHmxwj+lmz7HEvMH5J9 m1W048fIxQrDmc0IpfrKASrZ1St3/EFjqNmqdlbhvctZXrlO2FLmZ/VV2Vhb59dURD98Z6hw9Wu z72XZdJXI3xMJLo+N862GpoHoW4sMLcUZMcjd4vptQwz5tsiwSJcbRHuoMfDv5dDcuT2eTryTzf soIMijaOMlOGY7eFOYCDDesGQl5cFdomgH0lnFEUknJ/kEl5ZDL1gLmoa/OYq7Exe0AIoz7345D 1T/l8gBwKKRHe+rzJEgRjNFtnBffPDRa4yKmJvONTj1a3Eks/MAmNKH9CvDqymlQ3h990=
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/rtgwg/Q7bcG44OG2H8Emdkvh_olavizwk>
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 07:09:40 -0000

Hi Robert,

 

It’s an interesting draft.

 

Did you know there is a working group chartered to work on IP Traffic Engineering Architecture? It’s TEAS.

 

Thanks,

Adrian

 

From: rtgwg <rtgwg-bounces@ietf.org> On Behalf Of Robert Raszuk
Sent: 27 September 2019 00:07
To: RTGWG <rtgwg@ietf.org>
Subject: IP Traffic Engineering

 

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

v2.23.0 | Report a Bug | By Email