IETF Logo Mail Archive

Re: [Idr] WG adoption call for draft-abraitis-bgp-version-capability-08, to end September 25

Robert Raszuk <robert@raszuk.net> Tue, 10 January 2023 12: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 6531FC16ED07 for <idr@ietfa.amsl.com>; Tue, 10 Jan 2023 04:23:03 -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=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 R34eDw8h92q0 for <idr@ietfa.amsl.com>; Tue, 10 Jan 2023 04:22:59 -0800 (PST)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 4AC6CC16ECF1 for <idr@ietf.org>; Tue, 10 Jan 2023 04:22:59 -0800 (PST)
Received: by mail-wm1-x336.google.com with SMTP id p1-20020a05600c1d8100b003d8c9b191e0so9736017wms.4 for <idr@ietf.org>; Tue, 10 Jan 2023 04:22:59 -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=7ydWZKC4J2WlRmG42WQu7jUqB9KtTKsg/DaljnJ+iRg=; b=YQMyY/zbgHLHfFQYDf+G3v6w/+CBDaNY1rY+wKOrXAGcR2xM7YLvqw+9kQHkU3Gy63 9Zz21EN0RmawtpV7qbSVWZmPwcQ6E6vea7G/LJzNpDDQ2EVx8FH1ccVGo2xhP14UEaW0 5E3evQkfM7n95ZyiGM16yMqpjhndLILv5FtyNAbOG+BABkNd+m87j575WKObvYNkk29s oCPNCGgKxa7wXRrb9y7sMkVv81drd7zkOxEjyKEjBiiCqtffAuzAKj5whwyOSZp9j3/N J476LM7QUrWl7t6CGV50C50eSijcUP3ttwm+J0Byvmb7IOFpTUzaXQDApvohnLmy6fuN v9kg==
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=7ydWZKC4J2WlRmG42WQu7jUqB9KtTKsg/DaljnJ+iRg=; b=rc17peM8kxyfnQ1Ez6i+HROIkcsloKaVxK9+tyFTp0e7JcfCRfE7OI7iX9B7PauVoJ AiK/xzYWY4rg0MKVS47RqVZO1HmmQjFgU/Cjf+Mjsefv7ha2iFQqtqK6sEsKUx9YkaKN OYjs4sn1/qMedG3sePmMyC9mRc+ifDSd0kwULD63Gl3stdSdmbqijfjCobDusXg9LEx8 wXWZsSRUYC/2H4U/Q0WggqeYc/hlVDubRvJA1sraxxNiwKDda3JXFe8ngCmRJVdkXb/X quSj8GfYg0tXERS8/bbZm4b9d1Z3aRd5fLr0grMyhQp7pu0YkjeSjKIG+tAKwYzh5k/x j9Lw==
X-Gm-Message-State: AFqh2ko1twtMjpaY0vyWEX3g8MmqDMVj2q6wXCkjhT0V9+DmVnQDUxvA SUcaAbv3nHjxonHrtgKmFj18wjOwT3vIiy9DkOBOgg==
X-Google-Smtp-Source: AMrXdXtUQdgQJcCjcnAJWeq2MhMq7yx/1kxsyNPwq/CrVhCvWBjJ3oU20jXpb3RrrRoT6arevxbADbNeCODKYyDlWHY=
X-Received: by 2002:a05:600c:3592:b0:3d0:9be8:9463 with SMTP id p18-20020a05600c359200b003d09be89463mr4855863wmq.194.1673353376895; Tue, 10 Jan 2023 04:22:56 -0800 (PST)
MIME-Version: 1.0
References: <081E5E98-8D7B-452E-8517-EECBE72E3D7F@juniper.net> <64E754F4-CB63-4F2E-92A3-43ADEA1EC4AB@juniper.net> <20201028215313.GA8863@pfrc.org> <CAOj+MMFH35TB10gpeX80645qEZF3irFk0XVyyLZzkXagcTtwAA@mail.gmail.com> <20201029113316.GB8863@pfrc.org> <CAOj+MMHvVgP0SSTSLqcUHizfk_kR1tUjo0u8p3AnKiuHFr=VaQ@mail.gmail.com> <BYAPR11MB3207AE20610604C5310C0BBAC0140@BYAPR11MB3207.namprd11.prod.outlook.com> <007c01d6ae71$4513eec0$cf3bcc40$@tsinghua.org.cn> <8560_1604052018_5F9BE432_8560_210_1_53C29892C857584299CBF5D05346208A48FDBBFD@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <20201103163259.GC7455@pfrc.org> <CAJwpseXrj46EY7ccXYNH-aWqfykGD99obOaA5qLMNHfoWG7ptQ@mail.gmail.com> <CAMMESsx=c__3UR57zCXLUp62q2ua9YXPT90f-ThqDUJzCYiGjQ@mail.gmail.com>
In-Reply-To: <CAMMESsx=c__3UR57zCXLUp62q2ua9YXPT90f-ThqDUJzCYiGjQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 10 Jan 2023 13:22:45 +0100
Message-ID: <CAOj+MMG+_aHkc0=+FNvJ8tcTu9W-GpmVxJf=6JeD=zZK+AyjUw@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: Donatas Abraitis <donatas.abraitis=40hostinger.com@dmarc.ietf.org>, "Jakob Heitz (jheitz)" <jheitz=40cisco.com@dmarc.ietf.org>, bruno.decraene@orange.com, IDR List <idr@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>, John Scudder <jgs=40juniper.net@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009d2a6c05f1e7f1f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/yhvTTsMTqPFQ4QnWFL68m9ASNqI>
Subject: Re: [Idr] WG adoption call for draft-abraitis-bgp-version-capability-08, to end September 25
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: Tue, 10 Jan 2023 12:23:03 -0000

All,

In order not to repeat the points made and vastly ignored in this thread
before in Sep 2020 I do think that what is proposed should NOT be carried
in BGP Capabilities.

Instead if authors would like to proceed I suggest to carry it in new *BGP
Message Type* (perhaps Informational as we have this written out already)
or at least as a new *BGP Open Optional Parameter Type (not as BGP
Capability Type 2)*.

Stuffing 64 octets of free form text  into BGP Capabilites, while breaking
current BGP Capabilities functionality for opaque stuff seems completely
unjustified.

Regards,
R.





On Tue, Jan 10, 2023 at 1:04 PM Alvaro Retana <aretana.ietf@gmail.com>
wrote:

> On January 10, 2023 at 2:27:34 AM, Donatas Abraitis wrote:
>
>
> Donatas:
>
> Hi!
>
> > I'm still concerned and want to get back to this idea somehow, it's
> really
> > convenient.
> >
> > > PS1. And on the other hand if it is not adopted here it will likely get
> > > published as an RFC anyway in the ISE track.
> >
> > Who can help me with how to proceed this way as ISE track?
>
> Taking a document through the ISE track is a DIY job -- send email to
> rfc-ise@rfc-editor.org; the process is here:
> https://www.rfc-editor.org/about/independent/
>
>
> Adrian is not the ISE anymore, so please point Eliot Lear (the new
> ISE) to this thread.  You can cc me for any additional background that
> may be needed.
>
> Thanks!!
>
> Alvaro.
>

v2.23.0 | Report a Bug | By Email