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> Mon, 23 January 2023 21:08 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 E42D3C14CEE3 for <idr@ietfa.amsl.com>; Mon, 23 Jan 2023 13:08:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.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_NONE=-0.0001, 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 Dx4G98vdTk7N for <idr@ietfa.amsl.com>; Mon, 23 Jan 2023 13:08:42 -0800 (PST)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 03CD0C14CE52 for <idr@ietf.org>; Mon, 23 Jan 2023 13:08:16 -0800 (PST)
Received: by mail-wm1-x32e.google.com with SMTP id f19-20020a1c6a13000000b003db0ef4dedcso11509584wmc.4 for <idr@ietf.org>; Mon, 23 Jan 2023 13:08:16 -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=fzHAV82E3/SqrU0YiQ7rU5zS0ZkwZegnL0P6QfzXbLQ=; b=Q8Djp//QHmF+9bUSdmwOuKHS6etcOnZ1cjmeuG1pnxzegVgDEMSgd48frwJtkqjYWG BAXMtJWXB5UYqUibrQup5uhry/AGua03pNkX0lvD4c0KPzieOz+mj8ZeFUi0vbT0HEY8 XWQyyZk+R1yjkgDNLsnlA9/5P1l2nbyj2opAMl149tnN5KR7qd61NwQlUDDzGkHOTmL7 6V+IjO+qw0r0X6rU+aQJwvharxNktXOaWJZ6EqbWY0PTUvgOfFhVBhs86BmcoICGHw/7 4DY4VmrmxWhp5UR++0HInaxJW3l+gkLuPWk/t/nBAh9F/Z0whyith9TK5QwXzJ404MfR l00A==
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=fzHAV82E3/SqrU0YiQ7rU5zS0ZkwZegnL0P6QfzXbLQ=; b=XKuiGKvAMVX0e7tjcjC8dj9Qvbh14HKfoGPPCacpvFpJH0P0187pMWKbkNGADNJEjd q0H58fuhVx+GsYZx1SBLA9dL1oR9nLoSIZ1ZxSwS2ChyGcFJtMglGSh4z+q0dv1u9Mcz LnXwRQlEMoHiDrQrciNIPqfr+JvnpYPGMYYKP97H5LV4bgmpu2MWTCghd2/bThk2YfAg aln9y0DZ+8fyyCIOr9GYDybxSqtdThKHdFlwKQSv5x9Rbv3nIcm/9NmMXGz6nacWD3AC irOqmaNqLA52nrbTdih3NNzk6fUuKRRxwQN4v8L2dz2M54RkE2JPXlgxZx630TpAilQD S8kg==
X-Gm-Message-State: AFqh2kpiC4HLNytTzrcS/n7W6UdRFNI/6xS7qFGuDffI8QQNhaXjdVgs h0pJsjXIdLTFYPP51L16fqf3L6e4vP0UaTaiPSCnvfob3WJ4ptJ3
X-Google-Smtp-Source: AMrXdXuc5uUNQGlhdFmkz8pqemcxB3MKQqw7ONaXXNXnQs5KRWFTamQm8oJIl7VSFBeuALoyauPQMhkqZp+WIs5T7/s=
X-Received: by 2002:a05:600c:43c7:b0:3d3:5315:8de with SMTP id f7-20020a05600c43c700b003d3531508demr2231276wmn.50.1674508094542; Mon, 23 Jan 2023 13:08:14 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR08MB4872A3E10EEC0C0A6F96B5A1B3C59@BYAPR08MB4872.namprd08.prod.outlook.com> <CAOj+MME+WNk=FXiy42zHkvGCr4Xj6suscTQuW1vJAv-qG1pCHw@mail.gmail.com> <BYAPR08MB4872D5B455B8F3CA6D4B0C70B3CA9@BYAPR08MB4872.namprd08.prod.outlook.com> <CAOj+MMHFTdiMrFejzeNgxRGcfmmQpj-b7MiheH36ML-kDAZLgg@mail.gmail.com> <BL0PR05MB56528A4078937238E079A348D4C89@BL0PR05MB5652.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB56528A4078937238E079A348D4C89@BL0PR05MB5652.namprd05.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 23 Jan 2023 22:08:03 +0100
Message-ID: <CAOj+MMEkahQCinWzkxwWkcvFEEcZaR4aG=OTyJnjcxwtK3xmqw@mail.gmail.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
Cc: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002625c005f2f4cc6b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_wiyKhoabmrxSzH5iWxZYdUScYw>
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: Mon, 23 Jan 2023 21:08:46 -0000

Hi Jeffrey,

Zzh> There is already RFC 4684 based on Route Target though 😊 In fact, RT
> Constrain implementations can and should be enhanced to handle newer types
> for Route Targets (e.g., EVPN ES-Import Route Target) even though we
> don’t need to update RFC4684.
>

Please note that when we wrote RFC4684 we only had in mind Route-Targets as
per normative reference of RFC4360.

So if you think extending RTC to new RTs is needed/wanted at least
normative reference needs to be updated with new RFCs defining new types of
RTs.

Alternatively just like in the case of the subject draft we could perhaps
generalize RFC4684 in RFC4684bis to accommodate carrying any type of
extended community if there is a real use case for it. And honestly
observing where BGP is going it clearly looks so.

Regards,
Robert

v2.23.0 | Report a Bug | By Email