IETF Logo Mail Archive

Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)

Robert Raszuk <robert@raszuk.net> Wed, 24 August 2022 16:59 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 22D73C1522AD for <idr@ietfa.amsl.com>; Wed, 24 Aug 2022 09:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 7P5BUaX7rSee for <idr@ietfa.amsl.com>; Wed, 24 Aug 2022 09:59:53 -0700 (PDT)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (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 29082C14F72D for <idr@ietf.org>; Wed, 24 Aug 2022 09:59:53 -0700 (PDT)
Received: by mail-ej1-x635.google.com with SMTP id d21so15376111eje.3 for <idr@ietf.org>; Wed, 24 Aug 2022 09:59:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=sitklPHBAX7qQikm1LMspzaoQR+eMwnlmPrumACOLyo=; b=BH5lvVub+KdYf4EVPa9wia3cRmtxhE299J1tAaPT/QJFI+lHWZbF+1LefYMZiXcCGe CtE4zr8TK6/WvGT8wZU0E1OBwdPBFNmnSblCK/1tnDzhCOhJw7gbgoXl0qAsFYHuA30t 9tUdl00f9YefbLb6CA5gzxnBdHqDXD06OWxJpC2aJJd9lxPGx2yMl8TDV6quIskZmMNa n4dLNHHx7fS+XMjGa2h61vkWQeQsXs8Yp0/MFDaKSPe9YmCB3KbAZq4QaFYRlIVzio6Y 0iP2rQuqA3WPF3Wy0i5Sk8POQ9179uzdPgaxcnmpBs3bT+dGSVmkIgCWld9gJxTB1M9R BVqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=sitklPHBAX7qQikm1LMspzaoQR+eMwnlmPrumACOLyo=; b=BQb3Se+eYCHHIZsaIxupIIMHtk8Vg3eGikwu7DaaEdCn4TwA5DCFk9xN9B1YTKYlfQ 0dr1ps6t8pF1K2eFpni466pht+sK9jp3DrioqwLMa2vA1h2vf3c0kaBqEBP5H1BZhcG7 bikhvYLZPnXKpF2RoAvyOoFU8fIpEfHA7vubOp7MV6xCY5YD6r6tQfu5aV+60my33qjT ldwBvhfilQqdDoOqcmFcS6+aUYa4tmEQvzX81k0UslmAafJvF75/x2ao87LMQ9NBqP0Q 8oRokPX5BvyX6DWp131oCM/ZM/dVfE4Ggv1SKRqn/ASYw2x24qvG5D8YnN+MYCpBg79w RfCQ==
X-Gm-Message-State: ACgBeo1S0SOUjg8kmdb6TCz/xiCRYL7uHN4gTw8o7AxFbxnv1ZsRtcdT kFgCTVljwJFqbEzH4yUC8n6VnP0BkR63GMJV9hwS7oKWJuc=
X-Google-Smtp-Source: AA6agR7jWFbh22PAqF9RsdXJ1xT07/WgQfWtPnUFQcw898jd+ma/w99JsjmfITnPBJu09f+kmN1ZvkWMY0++bewoCOo=
X-Received: by 2002:a17:907:1ddd:b0:73d:bfab:ac1 with SMTP id og29-20020a1709071ddd00b0073dbfab0ac1mr1872694ejc.600.1661360391121; Wed, 24 Aug 2022 09:59:51 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB487262F752C8777A1B9698EFB36B9@BYAPR08MB4872.namprd08.prod.outlook.com> <d9e07ea96dd64ea081ba763941a22b17@huawei.com> <6f9c478a2ef745818e3ef3d713218dae@huawei.com>
In-Reply-To: <6f9c478a2ef745818e3ef3d713218dae@huawei.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 24 Aug 2022 18:59:40 +0200
Message-ID: <CAOj+MMH+k4u4q-5tCM-0Hi6vQ+8Ynzd6QKV1dvnkwS=dkfJ=Nw@mail.gmail.com>
To: "Wanghaibo (Rainsword)" <rainsword.wang=40huawei.com@dmarc.ietf.org>
Cc: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f50a6405e6ff9bae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/nBZws9reMSQjKYUhauuKJsTVqLU>
Subject: Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)
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: Wed, 24 Aug 2022 16:59:57 -0000

Haibo,

To make the actual progress of this draft, we should avoid to discuss the
> solved points back and forth. For example, RTC mechanism is not suitable
> for the scenarios that described in this adoption draft, because:
>
> 1) RTC has no any automatic detection mechanism to determine which RT
> should be withdrawn now.
>
> 2) It is unpractical to set the quota value for <RT>, or <RT, PE> under
> VRF, because RT can't uniquely distinguish one VRF on one PE.
>
> 3) It is dangerous to propagate the RT based filter rule unconditionally
> in the intra-domain or inter-domain wide, as that done in current RTC
> mechanism.
>
>
>
> The conclusion, RTC is not the right direction to accomplish the goal.
>

Ad #1 - Neither does ORF. We are talking about new detection irrespective
what mechanism is used to propagate it.

Ad #2 - The unpractical quota is now in the draft under adoption. So if
this is unpractical we should stop this discussion.

Ad #3 - Nothing is more dangerous then filter on RD in VPNs.

Kind regards,
Robert

PS. You can use RTC to achieve what you need. You can also define new SAFI
and add your stuff to it for filtering. You can also use Flowspec v2. ORF
is a bad carrier for what you are trying to accomplish.

v2.23.0 | Report a Bug | By Email