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> Mon, 29 August 2022 19:11 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 00FBDC1524D5 for <idr@ietfa.amsl.com>; Mon, 29 Aug 2022 12:11:16 -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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 e_k8O6F2Sl9T for <idr@ietfa.amsl.com>; Mon, 29 Aug 2022 12:11:10 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 ED81EC1522B4 for <idr@ietf.org>; Mon, 29 Aug 2022 12:11:10 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id z2so11407564edc.1 for <idr@ietf.org>; Mon, 29 Aug 2022 12:11:10 -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=VeNSv0b20EmI9jDpsatKwNhI/mo8emMbkieIOTtKK2o=; b=LCmQ2QFClp3mdJ2HqmYHXQsTgkALP5NPj2CEaI9qyyHxZTf3Y/oz4Hdmh+rQKfCwWj ZzJntObw2jbV6/3fkuUK/STtkAc+cr34I+E2gQmBsuWusmKzyap3nJTnu9gq6u5xtg3d PeOAQSuMeEll9EOQMm2IGMYhe4GYOdApXm7l4IThvaghnH08y+1uKmSqBHVemXPA7aX7 29G7EUzNK/sl8RyXooqoy50mMo5MOOdlYnsPZdPwF2Ig41ci5BDWU2zzr0VHyyUaDu+b 8h69vsMbI45BPpkHIop7PwCtKWaB10wJXmsHUiMayah5JO4lEoGD81y4OwhU7uO0Iac3 AcDQ==
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=VeNSv0b20EmI9jDpsatKwNhI/mo8emMbkieIOTtKK2o=; b=FuNWmpRMLjXE+H3+P6ardi6k/rJdnjaJNkixCGeURddNlWhNswIRW3i/2wfsrW5FGC 5jsLDQOo5R55uFc5PEULbIX642GN+KXlW4hGB2fuZE1PBCss69jxHzbhtjYTgdTUCJxl INZ6hduL0Tca7eXMoVaUPQe1AwZoMQvTeUOxiQ8TP5sM+tOiZZuuRm6yDkUjYJbEgNhX zK0GNodhy8MlxNCw9RGSjQgHQnpsxjNKhz7Mzo+vnrpLD9lxohmm/Pi3Z5TDHL3KrkPf B+8dUIaq7mZq1KlTGrS0KtWjeeU1KmuX3Ne5qH5VOBf4OILrbpIj05fIPErvhHyUwyCa GPeQ==
X-Gm-Message-State: ACgBeo07pPa476B4PY5IN6OxscWkQ7T5q7H67iBlkaoCbLFkYriC8IwN hPf+psq/b/bxE290Gytnicu+mr4SYCDelc2D2GdimA==
X-Google-Smtp-Source: AA6agR7wsLOZsqHCj1QVPEJm9SRtbaRU6N9sVVISZwdTTqL+gm0pDCd/xJnpwEMgBLdm8CmvlP8AQU9BicLbOSWh1R4=
X-Received: by 2002:a05:6402:5508:b0:43a:896e:8edd with SMTP id fi8-20020a056402550800b0043a896e8eddmr17706026edb.203.1661800269234; Mon, 29 Aug 2022 12:11:09 -0700 (PDT)
MIME-Version: 1.0
References: <CAOj+MMELVifgg4Yj38kyncDGYzS5fJG-43_kRc7YLwJiTPANUA@mail.gmail.com> <23D1B383-F794-402E-AB1B-D966F8F3375B@tsinghua.org.cn> <CAOj+MMGs9gU=xC0UG4Xaiv5feo2U6VFXkdAxmk6arN_bxe_mSg@mail.gmail.com> <BYAPR08MB4872E197715724FC1E853725B3769@BYAPR08MB4872.namprd08.prod.outlook.com> <CAOj+MMEY=0iQ=vBGYJ=M=Pd=3gvjZVwWCZC_XPXzXDsD-7_a6A@mail.gmail.com> <CABNhwV0zR+YWte146WZ6jD=-bBm_1KcAxVJrkkiiT8gMsHwcsA@mail.gmail.com> <CAOj+MME1ibRf4d6REs2UgZhpW=vANJMAiGhBcpgq5SBPs0+mnA@mail.gmail.com> <CABNhwV0e_dfGCtuuj3EfWrZxqcufNa_G4wRuQqEYpnGJ7eS4pA@mail.gmail.com>
In-Reply-To: <CABNhwV0e_dfGCtuuj3EfWrZxqcufNa_G4wRuQqEYpnGJ7eS4pA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 29 Aug 2022 21:10:58 +0200
Message-ID: <CAOj+MMEep7y3CGmpydY2cqF_wvJhmdhNT2EHnY_dtWNnLbJX_w@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: Susan Hares <shares@ndzh.com>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bc626605e7660642"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-gNXLsUH-s7wrLw8CwiyHqm7LLo>
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: Mon, 29 Aug 2022 19:11:16 -0000

Hello Gyan,

> After adoption based on WG feedback value proposition we
> can add back as desired by the WG.

Many thx for being sincerely honest here.

But this is one of the reasons why I oppose the adoption of version -03. If
we are to adopt a specification it's complete core functionality should be
described in the version under adoption.

Propagating ORF messages between nodes (even if you locally rebuild them)
is one of the elements of a core functionality. Same for modifying how ORF
works today which other authors keep mentioning in their messages.

Also note that it is easy to add text and extend protocol. It is however
much harder to run analysis of all corner cases such addition may trigger
in real networks.

"WG feedback value proposition" just does not cut it.

Thx a lot,
Robert


Just pushing ORF to adjacent RR and not mitigating the issue is not a
>>>> proper action.
>>>>
>>>
>>>     Gyan>The draft addresses both mitigation to adjacency RR as well as
>>> upstream to source PE using the source PE TLV.
>>>
>>
>> Excuse me ?
>>
>> Can you point me to text in the -03 version of the draft where this
>> propagation of filters to upstream source PE has been described ?
>>
>
>     Gyan> My fault, sorry for simplicity of the mechanism we removed the
> propagation upstream to source.  After adoption based on WG feedback value
> proposition we can add back as desired by the WG.
>
> Thx,
>> Robert
>>
>> --
>
> <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions A**rchitect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
>
>
> *M 301 502-1347*
>
>

v2.23.0 | Report a Bug | By Email