Re: [Lsr] [draft-ietf-lsr-flex-algo-08] Clarification on ASLA usage for flex-algo

Sarah Chen <sarahchen@arista.com> Fri, 07 August 2020 23:33 UTC

Return-Path: <sarahchen@arista.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E628B3A07D2 for <lsr@ietfa.amsl.com>; Fri, 7 Aug 2020 16:33:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=arista.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 BJIp3nBdTYQ5 for <lsr@ietfa.amsl.com>; Fri, 7 Aug 2020 16:33:17 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 318CD3A0317 for <lsr@ietf.org>; Fri, 7 Aug 2020 16:33:17 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id x5so3018581wmi.2 for <lsr@ietf.org>; Fri, 07 Aug 2020 16:33:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arista.com; s=googlenew; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=paWX/bviLd4jyE+u2QdmlC0pizYl/hfnlhpFgOxpdcs=; b=BswvXgrfP5kUUfrxhuTd5Bgl8Ji6Zu1L6Kg9CBtr2t7yt9GXZ/bt8mwds7S6MtKIvS RdIZ0EnVPhWCG0yAh5Rmmy4iLsclTQ90Qd8dNvOjea9LQRKh9Kh7rG4r9hk0Dtl+SETf kQsqNPdOyRCH747QHmJetHXJe1vYtnzSI6J2xb01LZhkXd9HiOMxXe7eNkvggQK8eTz0 To3dmScMFmkW3h8JvWoLos3WcSNWO9FwLIAmsQ8S+ZN3MnPqzgnerLNG1EHOs7maD8AU +Y3koQs5JxoyG4qDDvysJ+nNquVMl+i44yw6Cfd7xwQs3d/g/giHSA4ERq1AiWI8O1c9 +FFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=paWX/bviLd4jyE+u2QdmlC0pizYl/hfnlhpFgOxpdcs=; b=cgbvJ0Z18igul9zm1Jv/+5BBUhvA/cGxZQxfXNxHGbKfdfs9SUKzHKulVpxDd4LDQm HkjDEoZevJif52GEK6AH3La04NbB6nV+BPtMcrpujLfpRdWRLl1pclt0OFbszEp7Z4Wu vPjtNmPEUn/nuLNFPdIy1AteVQswmA2CKL4v7nBplRGDYP6FyPoZkfu464/sCK6vbDJN 3Gox90saxzU4dIoVx0irY4jiYRwCvwdwQThYTvRtyxofy2VhnGoHpIcfAoNHTDqUXOQ0 OlsMN5n8yvQkQDUSGyWt+DVkjPh+87yh95GBPI5TybFmZaVcdEbHRzmhs7k5x1CdRQlf ePdw==
X-Gm-Message-State: AOAM533g+qzRDECJMPdOVGFTjv+ecHmH6b03Nsw3+DguPFuW+IHlodct f47wJetDEVp4MTyudeUvbbZjMkKGjkHPWoHqNnW0sg==
X-Google-Smtp-Source: ABdhPJy18H53/gC9t3ni+gQIvdg9Txrj4Kt/IykJzPdSvsM4Jqv3y778FgB7twBfWSgHVJZVivYj8E/T0ISM6u0wPaI=
X-Received: by 2002:a1c:49c6:: with SMTP id w189mr13932038wma.97.1596843195528; Fri, 07 Aug 2020 16:33:15 -0700 (PDT)
MIME-Version: 1.0
References: <AM0PR07MB6386B2403358CE285F24C423E0480@AM0PR07MB6386.eurprd07.prod.outlook.com> <2504c28e-4cc0-4505-0eff-943a033cbad0@cisco.com> <AM0PR07MB638602985A8BA5F73361C3C2E0480@AM0PR07MB6386.eurprd07.prod.outlook.com> <92f1fd3a-9a53-53a3-1da8-96c91824d742@cisco.com> <FF39BFDE-A195-4919-A331-B528346A2FC5@tony.li>
In-Reply-To: <FF39BFDE-A195-4919-A331-B528346A2FC5@tony.li>
From: Sarah Chen <sarahchen@arista.com>
Date: Fri, 07 Aug 2020 16:33:04 -0700
Message-ID: <CADhmtX0nA7QhenXH6XNXaYX6qFbc0LxeGpvh8PrCDNbx4LN3Ow@mail.gmail.com>
To: Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>
Cc: Tony Li <tony.li@tony.li>, "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-lsr-flex-algo@ietf.org" <draft-ietf-lsr-flex-algo@ietf.org>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>
Content-Type: multipart/alternative; boundary="0000000000006e9b8b05ac5207f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/T8-TcV05g3xt1Xbvdcq53n1yz3A>
Subject: Re: [Lsr] [draft-ietf-lsr-flex-algo-08] Clarification on ASLA usage for flex-algo
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Aug 2020 23:33:19 -0000

Hi, Peter,

The flex-algo draft mentions "Min Unidirectional Link Delay as defined in [
RFC7810 <https://tools.ietf.org/html/rfc7810>]". When reading RFC7810, I
found two Sub-TLVs:

4.1. Unidirectional Link Delay Sub-TLV 4.2. Min/Max Unidirectional Link
Delay Sub-TLV

Could you please clarify which one should be used? If "Min/Max
Unidirectional Link Delay Sub-TLV" is used, will the max delay carried in
the subTLV be ignored?

Thanks,
Sarah

On Fri, Aug 7, 2020 at 8:30 AM <tony.li@tony.li> wrote:

>
> Peter,
>
>
> >> . The existing description in section 5.1 indicate that legacy encoding
> (RFC7810 and RFC5305) is used for link attributes. That is not correct
> based upon section 11. To avoid ambiguity can an explicit reference be
> added for [I-D.ietf-isis-te-app]?
> >
> >
> > well, section 5.1. is correct. The Min Unidirectional Link Delay and TE
> Default metric respectively were defined in RFC7810 and RFC5305. The fact
> that we advertise them in ASLA does not change their origin.
>
>
> Could we please get a clarification in section 5.1 then?  The references
> there to 7810 and 5305 without any qualification strongly suggest that the
> encoding from those RFCs should be used.
>
>
> >> Could in section 11 be explicit reference to (e)ag, te-metric and delay
> link attributes MUST be encoded using ASLA..
> >
> > Section 11 already says:
> >
> >   Link attribute advertisements that are to be used during Flex-
> >   Algorithm calculation MUST use the Application Specific Link
> >   Attribute (ASLA) advertisements defined in [I-D.ietf-isis-te-app] or
> >   [I-D.ietf-ospf-te-link-attr-reuse].
> >
> > I'm not sure what else can we say. Listing the ones we use today wold be
> dangerous, because we may define additional ones later and we want the ASLA
> to be mandatory for all of them.
>
>
> You could add a sentence that says:
>
>         In particular, the Min Unidirectional Link Delay, TE Default
> Metric, Administrative Group, Extended Administrative Group, Shared Risk
> Link Group Value TLVs are all to be encoded iin the ASLA advertisements for
> use with FlexAlgo.
>
> Please add any I missed.
>
> Regards,
> Tony
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>