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:36 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 1B49EC1763B1 for <idr@ietfa.amsl.com>; Tue, 10 Jan 2023 04:36:01 -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_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 vGbwC-04kqJ3 for <idr@ietfa.amsl.com>; Tue, 10 Jan 2023 04:35:56 -0800 (PST)
Received: from mail-wr1-f50.google.com (mail-wr1-f50.google.com [209.85.221.50]) (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 69CBEC131C65 for <idr@ietf.org>; Tue, 10 Jan 2023 04:35:56 -0800 (PST)
Received: by mail-wr1-f50.google.com with SMTP id e3so2353542wru.13 for <idr@ietf.org>; Tue, 10 Jan 2023 04:35:56 -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=WwE/zTaoZFlXgEhYKhHy2kUHLvvuVt+vH2joRYOQV00=; b=XwLoFlBR++MJjzPM/TkgwBho/qzZK57/kXcSIAYlpCgHvIQfhFzC/GZlpAONEd4BdK 2C1ZM149KElCZvkEvLW4UifINzK56FV6DF9a2Am9Cnq/HmbF2W+uHeU7bhzViGpvqBKw XZW0zhMUcjTTbbtrDNoBzFo+STAXKEmmG7Nd6Ho890OaROd41g3Zmevc2r3JLEaLDBPc dtRv2UO1Mp++QIdmHfCrML8yakGGLWtEfRSHVGcIGYVgBwUntlqTz4duG5IQ/WMpYh5I TbXK75ftQpeKFCorIUb0tX81iTSbGc4ZXWqMPWfJbkQpuVRNlp1Fiwznkc2JxvvYLwwQ 8MMQ==
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=WwE/zTaoZFlXgEhYKhHy2kUHLvvuVt+vH2joRYOQV00=; b=sk+kbfhG1FAu08kG3G2SD2V+sf50sfKNMV0q+TDT0WFhda9+AZEJR9CT8QCtmBEc+G wpk3ys1PLXUB9T07M51XtnZb+MA8ykOXTQeqQnDTorF4BxmAfxexTlPKaQw9Kj6fCYJa 6sut/q2wvsVZ0YrGkQNzaB13miaA/sz9DG1RshMJgBg7qVp87KviOZbmBy9YjQBl4Ju2 Noo6OOxPxEMtSdEtDytoOa3zEl72KUK4Rf208gaPqfpBw2ew/63fscHXsgWIo/QMRMnC g2JxlYNP9YeYDdvE2pL9u+HTmFfsukVEeS7edXOTJ9TOJzMPJnT12yY5TVf+JVBH0Xll MIMA==
X-Gm-Message-State: AFqh2koS3z9XBM2idONHkh6qqXxYoXKcR3hFyTjLuNtetMUgUt5WNBr9 PhOTNI/zbXjPZ38/pG6D98wMNmxbwVcfTGwvsAHh8A==
X-Google-Smtp-Source: AMrXdXu05KjfEfmeR8qAEFp8PhnlIX7m6kWgKDYhe/14PZq7KqOvdt6QlxHmwWDxVx1krZr5sieo8yFN5CR+H9+nuGE=
X-Received: by 2002:a05:6000:108d:b0:2bd:bbbf:aaf0 with SMTP id y13-20020a056000108d00b002bdbbbfaaf0mr61527wrw.230.1673354154605; Tue, 10 Jan 2023 04:35:54 -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> <CAOj+MMG+_aHkc0=+FNvJ8tcTu9W-GpmVxJf=6JeD=zZK+AyjUw@mail.gmail.com> <CAJwpseWAt5oUEMqUE85m+PNSEv_kfONScUSdGooq4XpP6EwFYg@mail.gmail.com>
In-Reply-To: <CAJwpseWAt5oUEMqUE85m+PNSEv_kfONScUSdGooq4XpP6EwFYg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 10 Jan 2023 13:35:43 +0100
Message-ID: <CAOj+MMHCvyE7vDiP3iBOC+EHgpBsKUESXs4GvcHFbHj_VSChTg@mail.gmail.com>
To: Donatas Abraitis <donatas.abraitis@hostinger.com>
Cc: Alvaro Retana <aretana.ietf@gmail.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>, bruno.decraene@orange.com, IDR List <idr@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>, John Scudder <jgs@juniper.net>
Content-Type: multipart/alternative; boundary="000000000000f8121305f1e81fb2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_0gy-pEtbSCdkzBbem8CzAIYO7g>
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:36:01 -0000

Hi Donatas,

>From my pov if you are willing to switch encoding to new type of BGP Open
Optional Parameter this could go in fast track of IDR too. Seems useful and
not very harmful. And requires just few lines of changes to the draft :)

And while doing those changes you can delete section 3.1 entirely and
extend this to use 255 octets to be even more useful. If you like you could
divide this space into few blocks: OS-NAME, OS-VERSION etc ...

Cheers,
R.





On Tue, Jan 10, 2023 at 1:29 PM Donatas Abraitis <
donatas.abraitis@hostinger.com> wrote:

> An additional Open Optional Parameter sounds good to me also. Robert, do
> you agree on moving this direction + ISE track?
>
> On Tue, Jan 10, 2023 at 2:23 PM Robert Raszuk <robert@raszuk.net> wrote:
>
>> 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.
>>>
>>
>
> --
>
> *Donatas Abraitis*
> *Principal Systems Engineer*
> @: donatas.abraitis@hostinger.com
> W: www.hostinger.com
>
>
> This message and its attachments may contain privileged and confidential
> information. If you are not the intended recipient, do not use, copy, or
> disclose this information. Please notify the sender and permanently delete
> the message from your system.