IETF Logo Mail Archive

Fwd: IP Traffic Engineering

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

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B48A512000F; Thu, 26 Sep 2019 17:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 4y7a1bbnESaG; Thu, 26 Sep 2019 17:07:00 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 4EFC912008A; Thu, 26 Sep 2019 17:07:00 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id j31so5123242qta.5; Thu, 26 Sep 2019 17:07:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:to; bh=9rWS7DmHGC99YIjJJU5dJNH56Poq9b/dDeU4CkRX0hM=; b=d11ceS5J0ik1xKO4rPAr+taacx5vPCiVXwPb6Obhm+PerRD/FrY/ACiNau/cVu2eXI rdnFNUCk4FKH2orUHAKkCfGEiDHyvtodI04hQPK5TqHVLmkLLEYIt+CzDkze/UqMvtdw oVFcBfqMeLL+4tfE21Eu2vFe+k2x5NfLOH5lN5YTG+V/eZj/OQgdVJtpoBtkVHrz9RKz ov/wUx9N7fyjKUd7aPgSocB2ccUg8YJmp9S06iLgTJ/Ke9phrolZDo1cqw2SmeSIsNgX HmP1NOjnRf6a4XcH0OkM+D3RAtiQI+CJE8ggsNmik5kCpVtQPhbTKnwUogmatQZ35aze D7HQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:to; bh=9rWS7DmHGC99YIjJJU5dJNH56Poq9b/dDeU4CkRX0hM=; b=frpOfiSAfkDTf8p68awGANBFq4nvIS5YOXcZmcnhrvOGY2IxSbXWgjnsaOyowM4JfV 7eXWHNSY8EySMxZagCQfXLiUQkD0ePps64GzMHpgzXx9tnxiNIXqZa83GaNxNWxFjlwt 21PdMCc7wyzcpJEXvYHZ0j5IbLI8/JHZdhekLbvPnkkol0Djl6nuPeqCpIjzoH/7o7QC YgDqkNBGbTzkrwGU7ENEM8QivoPWUlDERFx+Mu/dzQ2Lsa5ybb0pQGQd534a1AnGlLAZ wyrJobfkjPFBDUhH6X7IHRSv3J0Sti+J02rvE7YVHh9P3OiMBKSi5GUYPLsuPMNIbMKI DxPA==
X-Gm-Message-State: APjAAAWT9bud/ulrLuX0hn2q3buGeirSt6qefuV6KUudbkUSic+ARuM4 shLJML3IzjefXF2wnCUaWXw=
X-Google-Smtp-Source: APXvYqy0vSpmi+vY5jOk1lpbFx3/P45r8dL75Lv4nNJfgTABD5piGoOah49AEVy7J5kUHfrc5VJyFg==
X-Received: by 2002:ac8:4550:: with SMTP id z16mr7467954qtn.4.1569542819141; Thu, 26 Sep 2019 17:06:59 -0700 (PDT)
Received: from ?IPv6:2600:1003:b003:900c:48a7:4c09:576d:1214? ([2600:1003:b003:900c:48a7:4c09:576d:1214]) by smtp.gmail.com with ESMTPSA id v4sm389835qkj.28.2019.09.26.17.06.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Sep 2019 17:06:58 -0700 (PDT)
From: Gyan Mishra <hayabusagsm@gmail.com>
X-Google-Original-From: Gyan Mishra <hayabusaGSM@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-6FDA610F-28DE-457D-9F69-79F800F12B82"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Thu, 26 Sep 2019 20:06:57 -0400
Subject: Fwd: IP Traffic Engineering
Message-Id: <C8D4D5FD-BB64-4D47-A927-D4C71836C248@gmail.com>
References: <CAOj+MMEEn9uGH-qjapYw2guxnipcYE0u-3PH6wWPECiCQDhXiQ@mail.gmail.com>
To: 6man@ietf.org, 6man-chairs@ietf.org, rbonica=40juniper.net@dmarc.ietf.org, markzzzsmith@gmail.com
X-Mailer: iPhone Mail (16G102)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/p0XkOXp4itB7FPjxi7ekSyScuFM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 00:07:04 -0000

6man

I just saw this submitted by Robert Raszuk.

Looks interesting and maybe an alternative to counter the issues we are running into with SRv6 with the Spring WG with eh insertion and encapsulation violation of RFC8200. 

Maybe this will help in that regards.



Gyan

Sent from my iPhone

Begin forwarded message:

> From: Robert Raszuk <robert@raszuk.net>
> Date: September 26, 2019 at 7:06:44 PM EDT
> 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
> 
> 
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email