IETF Logo Mail Archive

Re: [Idr] Clarifications on draft-ietf-idr-segment-routing-te-policy

Robert Raszuk <robert@raszuk.net> Thu, 13 April 2023 09:23 UTC

Return-Path: <robert@raszuk.net>
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 3E523C169515 for <idr@ietfa.amsl.com>; Thu, 13 Apr 2023 02:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Irdwa92fuJc for <idr@ietfa.amsl.com>; Thu, 13 Apr 2023 02:23:55 -0700 (PDT)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ACF0C13AE32 for <idr@ietf.org>; Thu, 13 Apr 2023 02:23:55 -0700 (PDT)
Received: by mail-wr1-x431.google.com with SMTP id s12so5055565wrb.1 for <idr@ietf.org>; Thu, 13 Apr 2023 02:23:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1681377833; x=1683969833; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8UL2z2yZqHTX83mtboAkYhAPb9XgpQVifolsyvurx2w=; b=S+SAXz9RtyXGxf1/CLzuX/bHybzZrIMle//nbhcigP1srX5PTbHEDWus9gYR3mbevd kMtcJgVJQXNWd4Ql+PXBOz+rJxHNpJ232Cg4VSFewFkTpfbyEghlj5wTR9ih382pTQas mvxTrOHfW+t2drG8mfSFoZg/mUT3pXayKCa9MBT6m5BXqjcPR1FqEZq506okKeofwp6X wm5vnPCU2mkHRqbe0SSF/ssx0NlWcwhy5H7PM3sPhbV2otxcCusL6Lx8TiwYVJ75W/Kw j44O3ur1uLCvX5++uCRx/pNv+/eZpXNibYIpRfL317cD9YE5YfdUPqIDIgFx/bKnI6KZ 2hCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681377833; x=1683969833; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8UL2z2yZqHTX83mtboAkYhAPb9XgpQVifolsyvurx2w=; b=XgF15UqfuCXbKR2hiT4OG1qdvGeMduwgwqIzecBt/nHkCTXn/+9Pl1w15ZZbtC4ayk UUi8DEfjvyGekVJgnGdDEKBNMScVkIkyxIScxKq9B1ojLKL6f4BDwycZXWelHY61Ro0Y DZwAW/GVBnGhXAc8D+EY0fqfn5k9FkwvKNiCrt3QdZkWs2gDByr2/bBqPKoLNx1DsxvV rC8FI9E0d1m+q2ykfzP9IHbWiUtlgzn2K1frVER7NLISx8obK+Ut7baDcAMP2ISHA4Ze bDowzzIxnsgOCwsoXQlSnfNX7R1P4zh7c8tot9QHGkeiHK+UODpmEDY4fqfyzUJu/8Xd HUQA==
X-Gm-Message-State: AAQBX9dXVmGESM37YnbugFHKQwzqLXe0nBXyW1j+hxGEyBDB9Euz10dM G7UsCDmazFOB9X0YQbJcqe85VKTf3XTgY9jt9UwOvsj3yUVD7eZbJVk=
X-Google-Smtp-Source: AKy350atsZPOWqfmX4rYYALNiQLpJAyURm7VjFmLQxoJI1bqHBKQC0cCvic3J0b8CEcFkrv+zsv6vD5y0uacJmIC7kI=
X-Received: by 2002:a5d:5225:0:b0:2f5:9146:700f with SMTP id i5-20020a5d5225000000b002f59146700fmr219638wra.11.1681377833449; Thu, 13 Apr 2023 02:23:53 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com> <CAB75xn70k8xE3QaNKqHkHn=22gD0NEG65o1uooB6puNx4xWB6A@mail.gmail.com> <43a2fb5f9f3747ea9c31423d19e332d1@huawei.com> <CAB75xn4Dk7Ge9VAbB9eQ9Pqh+1mzJH0_29OqX-PB40t1sD9H7Q@mail.gmail.com> <ME3P282MB29401E421BAE4C236C86DC18FC919@ME3P282MB2940.AUSP282.PROD.OUTLOOK.COM> <CAH6gdPytvU2w9Fp6DjsnaXBDk9cVvONkptUVQdvusdv7=Mv5Zg@mail.gmail.com> <MEYP282MB2942D2A3F89D210C01C9107CFC979@MEYP282MB2942.AUSP282.PROD.OUTLOOK.COM> <CAH6gdPw2HeWfif8w=d_kqGJio+hPwznnf1k3ju8a+F1nyiQREQ@mail.gmail.com> <7f1a916911724ee7ad88219394ef7c18@huawei.com>
In-Reply-To: <7f1a916911724ee7ad88219394ef7c18@huawei.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 13 Apr 2023 11:23:42 +0200
Message-ID: <CAOj+MMH3PKdJ=3mekp+KcN8aQ3k6TYyBdbF6cPpfZCTdTrx6oA@mail.gmail.com>
To: "tanzhen (A)" <tanzhen6=40huawei.com@dmarc.ietf.org>
Cc: Ketan Talaulikar <ketant.ietf@gmail.com>, "li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com>, authors <draft-ietf-idr-segment-routing-te-policy.authors@ietf.org>, "idr@ietf.org" <idr@ietf.org>, idr-ads <idr-ads@ietf.org>, idr-chairs <idr-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007f164405f9344821"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/cQQRotpTHzhV3X74mX_DGI9m-Cs>
Subject: Re: [Idr] Clarifications on draft-ietf-idr-segment-routing-te-policy
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 13 Apr 2023 09:23:59 -0000

Hi,

> https://datatracker.ietf.org/doc/draft-ding-idr-rtc-for-bgp-flow-sr/

I am sorry but this is completely broken.

You can not have different formats of NLRIs for the same AFI/SAFI.

Please do not call this RTC extension as this has nothing to do with RTC.

Route Target is not "IPv4 Address Specific Extended Community"

If you are willing to provide such filtering please use a different name
and a different (new) AFI/SAFI.

Regards,
Robert.


On Thu, Apr 13, 2023 at 11:13 AM tanzhen (A) <tanzhen6=
40huawei.com@dmarc.ietf.org> wrote:

> Ketan, Zhenqiang Li,
>
>
>
> Hi.
>
>
>
> We posted a new draft last month, which might be a good way to solve your
> problem.
>
>
>
> In the draft, we proposed to extend the application scenarios of RTC to
> BGP Flow and BGP SR-Policy for outbound route filtering (ORF). You can find
> more details here:
> https://datatracker.ietf.org/doc/draft-ding-idr-rtc-for-bgp-flow-sr/
>
>
>
> Looking forward to your comments.
>
>
>
> Thank you.
>

v2.23.0 | Report a Bug | By Email