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

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 15 October 2019 13:49 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D58FC1200FB; Tue, 15 Oct 2019 06:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 YKk4OhGWyRlo; Tue, 15 Oct 2019 06:49:55 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 8775F12004C; Tue, 15 Oct 2019 06:49:54 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id y91so18071870ede.9; Tue, 15 Oct 2019 06:49:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=0dolklBmfA3OvN3WRmxmv5/b4xSHQGjRK/7ooxSGngs=; b=VxuRcr9TlTAcsfpjQA2F1OcaNLCYChMLCO4XpnCklxYT0NDsqIy6h7R/FUEqQSjCTK CU/FwlzotC0Wi1QT7YKteGqddQxZySaSXrQZpVIPwaJvNA4h4ab3jvd8wrb19fCrPjzQ LNDKCv53sLwghacBHZjaaNNCb60wW9Wwd3Cuh0J+/AkTCQ/1x33fdfZfpyEwogfyt14v 6++qxBJhMcw/evKN8/60TpnW+EJ0M/eq7aeG+TpI7/aFmDEzDfv3caI75SScuL3+Qxuc ysHHi9nnGimjLAIDKDd5daHvKa72AORXqvLE1qrzScqxqkT66KSr53kygJAk+heCWspd Ehwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=0dolklBmfA3OvN3WRmxmv5/b4xSHQGjRK/7ooxSGngs=; b=cnJzIKpKD7kVb7rgCJuAD67n/1Y41SumMblKEYuFOyQR0HZpCKMQtSKS9snIrcsMSl MuMkGuwq5cTq9w7R/T73FmudM23k85b6jolYVhRV4iD5T/srrjuWDdfuKgA0tpF6rZjt odaotwzprGQ6/L3nG2UV0/UdcB629CTBor3km2siwXmteE2hkwrOQvKK6eRdZXGYBm1O tHOrRcNw66xPXkNvd3pQM9BOjyVqBq49v9VXf2ROoEMOcSDHibxnVPBT/Qq8YNqb2DW4 laXHsd1J3dmdzlpTHqF4HujnyrghjpZMHnG07EF0gp9lM9VVXc1eKkclLxRyP6pKDjhn oNNw==
X-Gm-Message-State: APjAAAUJKDevdzGD4OwZUcgPzyJHLYYQ/JOPXcVR1ReMz07iX0Nt8w3V GiLcJbGNjs49NJ740shaxhMj0+5/
X-Google-Smtp-Source: APXvYqx5NJMSG4U67k2Pyk6+6hDU3cb9xPVbo+lM4p6wlILTivRkbwWZXHbrhsNp+7PD/Xc6txXObA==
X-Received: by 2002:a50:e606:: with SMTP id y6mr33301966edm.261.1571147392862; Tue, 15 Oct 2019 06:49:52 -0700 (PDT)
Received: from [156.106.225.202] ([156.106.225.202]) by smtp.gmail.com with ESMTPSA id qn27sm2867647ejb.84.2019.10.15.06.49.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Oct 2019 06:49:51 -0700 (PDT)
Date: Tue, 15 Oct 2019 15:49:42 +0200
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: SPRING WG List <spring@ietf.org>, "=?utf-8?Q?=E5=BE=90=E5=B0=8F=E8=99=8E(=E4=B9=89=E5=85=88)?=" <xiaohu.xxh@alibaba-inc.com>
Cc: idr <idr@ietf.org>
Message-ID: <05748614-0455-4763-91cd-a1669a8e08e7@Spark>
In-Reply-To: <cfdb4bb4-cd42-4717-af35-a70447a8ac79.xiaohu.xxh@alibaba-inc.com>
References: <157102976688.20872.8891510157374456894@ietfa.amsl.com> <eaac2838-0c1d-400f-9913-b30ac9cfdbf0.> <cfdb4bb4-cd42-4717-af35-a70447a8ac79.xiaohu.xxh@alibaba-inc.com>
X-Readdle-Message-ID: 05748614-0455-4763-91cd-a1669a8e08e7@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5da5ce7e_5e884adc_cdaa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/JOdpYFKG3Tn3rECU9vjeawPwM-0>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-performance-routing-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 13:49:58 -0000

Xiaohu,

few comments:

RFC7311 is very specific about containing routes with AIGP attribute within AIGP administrative domain, while not well defined in RFC7311, perhaps worth saying something?
The value field of the AIGP TLV in RFC7311 is 8 octets long - draft defines 4 octet value, I assume you are following RFC8570 and RFC7471 encoding?
Rather that making AIGP TLV and NETWORK_LATENCY TLV  mutually exclusive, perhaps defining how they interact, if both are present would be a better choice?
Capability Advertisement - 3rd para doesn’t parse, be clear if it applies to labelled routes only (RFC7311 is vague here - "tunneling of some sort”)
Manipulation of the Unidirectional Link delay sub-TLV in IGP’s could natively be done by using  Unidirectional Link Delay TLV in RFC8571.

3107 has been obsoleted by 8277

Cheers,
Jeff
On Oct 15, 2019, 11:57 AM +0200, 徐小虎(义先) <xiaohu.xxh@alibaba-inc.com>om>, wrote:
>
> 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,
> Xiaohu
>
>
>
>
>
> > ------------------------------------------------------------------
> > From:internet-drafts <internet-drafts@ietf.org>
> > Send Time:2019年10月14日(星期一) 13:09
> > To:i-d-announce <i-d-announce@ietf.org>
> > Cc:idr <idr@ietf.org>
> > 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
> >
> > Abstract:
> >    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:
> > https://datatracker.ietf.org/doc/draft-ietf-idr-performance-routing/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-idr-performance-routing-02
> > https://datatracker.ietf.org/doc/html/draft-ietf-idr-performance-routing-02
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-performance-routing-02
> >
> >
> > Please note that it may take a couple of minutes from the time of submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr