IETF Logo Mail Archive

Re: [Idr] WG adoption call for draft-zzhang-idr-rt-derived-community-03 (12/27 to 1/13)

Robert Raszuk <robert@raszuk.net> Fri, 20 January 2023 20:58 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 11BBAC14F747 for <idr@ietfa.amsl.com>; Fri, 20 Jan 2023 12:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 FSb24kj2YUx8 for <idr@ietfa.amsl.com>; Fri, 20 Jan 2023 12:58:32 -0800 (PST)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 F22CFC14F739 for <idr@ietf.org>; Fri, 20 Jan 2023 12:58:31 -0800 (PST)
Received: by mail-wm1-x334.google.com with SMTP id c4-20020a1c3504000000b003d9e2f72093so6678718wma.1 for <idr@ietf.org>; Fri, 20 Jan 2023 12:58:31 -0800 (PST)
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:subject:date:message-id:reply-to; bh=R+jSjXibDFAlW4PXF/Ly7drmLlCqcINKEzlPmJepniw=; b=IrbWoGFclFM3uYL4YxbIyEzoxKaoyL4Iy5ubAjIA5CDer+GOuFVoXHsaNV5LWAbJQ5 uuM522ajVYnVQdMpOUJ/xdcHttRk4NdG0p5eF94+VO7UfdkvGk3A5a7T3ZNZDI/gxEsq X+eW39mQJ9bvHaBCyBRQlNeYoRowHErn+MFFWrdKB1QiqrNKGaCh7LJhJzK4nNI1W7eJ Tk1onNWNYp7gl5QZb2Azof2wPk72rrO+qzXueGy50YdngmheCtb/UBbbkYH08JLbGPJN NkIieP44jD1V9RT6Z453L8swtU2/iWMEgiPt5xDw13fjBGF8sPhnVYXdY7scm8Dm9n4G EFBA==
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:subject:date:message-id :reply-to; bh=R+jSjXibDFAlW4PXF/Ly7drmLlCqcINKEzlPmJepniw=; b=ZxU9nVyEn12lhAJUa5BSlp7Nk34j8z8prtJgRU+G25iDcEQkTMiHDl5Q8uhbWr6X8r f6tZBLyACBQvB58gcci3AyW7SxDvLjRjf01gZhPH+inV17VvdTIkRUQscBGu8MBVcF0/ L+DesKAb/JTlSY+PFxWg113CFnqt/mr+BdjOECA/OSXO1NGSDJMl+BgDOobpI94LJjgg 6N7YKg6E8qhL0BIek9def6987OxlICTWIWd3F4x3ufWbPVtHJEaHJIgT4YlJVG2Er778 Fym8q2mUTjHzpO+qcunchmmEUKw8DNF/YoCs04WzjlpiCTXGgME1PdRcOonPpdOnz8Fi EFZg==
X-Gm-Message-State: AFqh2koML5gFfTm4RCvOyKPAN962CqVZIZr5ThI3OHtCDcPuRGPH7miA lbVxSTkfBjxo//kMTRsEHUVydrdBp03ph3zFvlL2VyVWmXfl9Htu
X-Google-Smtp-Source: AMrXdXtIMzYcrcBMs7vi5hQ6DKumKJUM/khyKRrUmLhytnjBmZsUqIzI1kQR/nVGw6oPzARTygdER/XW6zYBa+v+qvs=
X-Received: by 2002:a05:600c:1d83:b0:3da:acb1:2ef6 with SMTP id p3-20020a05600c1d8300b003daacb12ef6mr1206059wms.194.1674248309909; Fri, 20 Jan 2023 12:58:29 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR08MB4872A3E10EEC0C0A6F96B5A1B3C59@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872A3E10EEC0C0A6F96B5A1B3C59@BYAPR08MB4872.namprd08.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 20 Jan 2023 21:58:18 +0100
Message-ID: <CAOj+MME+WNk=FXiy42zHkvGCr4Xj6suscTQuW1vJAv-qG1pCHw@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c745b305f2b84fa6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/QjXSfYgqq5sQzKur09AdvsuweQw>
Subject: Re: [Idr] WG adoption call for draft-zzhang-idr-rt-derived-community-03 (12/27 to 1/13)
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: Fri, 20 Jan 2023 20:58:36 -0000

Dear Sue and WG,

I would like to reiterate one major issue with this draft in the current
form.

Route Targets have been formally defined in RFC4360 as an extended
community with high order octet of  0x00, 0x01, or 0x02 and low order octet
of 0x02.

There are documents which do not formally update RFC4360, but define new
high order octet extended community values and also call it  Route Targets.
They usually reuse low-order octet value of 0x02.

The intention of this draft is to extend the notion of the Route Targets to
cover any extended community with low-order octet value of 0x02 claiming
this is de-facto unwritten standard.

So with the above we have few options here:

Option 1 - We make an update to RFC4360 redefining RT as any high-order
octet value with low-order octet of 0x02 then proceed with this draft.

or alternatively

Option 2 - Redefine this draft as a generic derived community where
low-order octet is 0x02 without calling it RT.

or alternatively

Option 3 - Collect all documents which define RT with different high-order
octet then 0x00, 0x01, or 0x02 and add them as a list to update RFC4360.
And keep doing this each time someone wants to define a new high order
octet type and call it RT.

Kind regards,
Robert


On Fri, Jan 20, 2023 at 9:30 PM Susan Hares <shares@ndzh.com> wrote:

> Greetings:
>
>
>
> The IDR WG did a call for draft-zzhang-idr-rt-derived-community-03.txt.
>
> https://mailarchive.ietf.org/arch/msg/idr/uwY3Hdrk2ned2hqMimpB6alhd9U/
>
>
>
> We have received a lite support and no objections.
>
> The IDR chairs are inclined to adopt this draft as a useful
>
> addition to BGP.
>
>
>
> As IDR document shepherd, I have queried the BESS and Grow WG
>
> (from 1/20 to 2/3) to determine if there are any objections to adopting
> this draft.
>
>
>
> The results of these queries to BESS and Grow will be summarized to this
>
> Thread on 2/4.
>
>
>
> Cheerily, Sue
>
> (shares@ndzh.com)
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

v2.23.0 | Report a Bug | By Email