Re: [Idr] I-D Action: draft-ietf-idr-performance-routing-02.txt

" 徐小虎(义先) " <> Tue, 15 October 2019 09:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C452A1200B7; Tue, 15 Oct 2019 02:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LrpNEift_imB; Tue, 15 Oct 2019 02:57:30 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4FB141200B4; Tue, 15 Oct 2019 02:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=default; t=1571133446; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=fI7WN5QueZGDv0Tb5OVB4bv3kkXb5u1Ao/pxKw9f1+g=; b=mCRtXVUEpozBSHv8OrP4cxkCXO9cwcWO8bTt4TlKqYs1A8Kvtd4DZwePQM/CVY0o0r+DdQ97aQbOhLbmOo/11Wpd0ldlv1P5KBIHgN2Lcjyq4/HqnYNuSXhS7DBZF4AhdUovkmJOiwEXVpsAKGt176vARKesyXuD6MTkHI3Fxdg=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R201e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03308;; NM=1; PH=DW; RN=2; SR=0; TI=W4_5657687_v5ForWebDing_0A932696_1571033219413_o7001c24221;
Received: from WS-web ([W4_5657687_v5ForWebDing_0A932696_1571033219413_o7001c24221]) by e01l07394.eu6 at Tue, 15 Oct 2019 17:57:24 +0800
Date: Tue, 15 Oct 2019 17:57:24 +0800
From: "徐小虎(义先)" <>
To: SPRING WG List <>
Cc: idr <>
Reply-To: "徐小虎(义先)" <>
Message-ID: <>
X-Mailer: [Alimail-Mailagent revision 2765257][W4_5657687][v5ForWebDing][Safari]
MIME-Version: 1.0
References: <>, <eaac2838-0c1d-400f-9913-b30ac9cfdbf0.>
x-aliyun-mail-creator: W4_5657687_v5ForWebDing_NjATW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTJfNikgQXBwbGVXZWJLaXQvNjA1LjEuMTUgKEtIVE1MLCBsaWtlIEdlY2tvKSBWZXJzaW9uLzEyLjAuMyBTYWZhcmkvNjA1LjEuMTU=XQ
In-Reply-To: <eaac2838-0c1d-400f-9913-b30ac9cfdbf0.>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_32884_487e7940_5da59804_6d304"
Archived-At: <>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-performance-routing-02.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 Oct 2019 09:57:32 -0000

Hi all,

I just recently realized that the performance routing mechanism as described in this draft could facilitate the deployment of segment routing across multiple ASes of an administrative entity where low-latency SR paths across ASes are needed for carrying latency-sensitive and high-priority traffic. In this way, there is no need to resort to centralized TE controllers for calculating low-latency paths across ASes. 

Any comments and suggestions are welcome.

Best regards,

From:internet-drafts <>
Send Time:2019年10月14日(星期一) 13:09
To:i-d-announce <>
Cc:idr <>
Subject:[Idr] I-D Action: draft-ietf-idr-performance-routing-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing WG of the IETF.

        Title           : Performance-based BGP Routing Mechanism
        Authors         : Xiaohu Xu
                          Shraddha Hegde
                          Ketan Talaulikar
                          Mohamed Boucadair
                          Christian Jacquenet
 Filename        : draft-ietf-idr-performance-routing-02.txt
 Pages           : 10
 Date            : 2019-10-13

   The current BGP specification doesn't use network performance metrics
   (e.g., network latency) in the route selection decision process.
   This document describes a performance-based BGP routing mechanism in
   which network latency metric is taken as one of the route selection
   criteria.  This routing mechanism is useful for those server
   providers with global reach to deliver low-latency network
   connectivity services to their customers.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

Idr mailing list