Re: [bess] Suggestion on v4-only/v6-only drafts

Robert Raszuk <robert@raszuk.net> Fri, 11 November 2022 20:32 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C823FC1522D7 for <bess@ietfa.amsl.com>; Fri, 11 Nov 2022 12:32:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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_FONT_FACE_BAD=0.001, 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 YeUq4hUyYuW7 for <bess@ietfa.amsl.com>; Fri, 11 Nov 2022 12:32:26 -0800 (PST)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (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 2DE29C1522D0 for <bess@ietf.org>; Fri, 11 Nov 2022 12:32:26 -0800 (PST)
Received: by mail-ej1-x62d.google.com with SMTP id ud5so15133992ejc.4 for <bess@ietf.org>; Fri, 11 Nov 2022 12:32:25 -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=MzjBRWZV4FTFFJ47qQN8bPxaDTuWz+EC0JSTCDKYPeQ=; b=IgxTtTpcMYXa6+Puy1tY8Two+EvJPfPbDtKHzcNP6xa5gVF0DHJW7XHooT1Cw94ILa rH4OeOXyhxIgI2bZWMLfDiZ2LEwzLhuWxqntG49hzc4PqhArfRhHqohqnduYvtqEqPUY b/0h3uyFK0cnNKkXOsdSWz3dn8gsnC6m83mEeo8cDMLrSKU9iQEGXtbe0hu3hBjO6eYy tefYwwrxEwC1AAKu1qs6YPCHy+yokg+bvq7yveuugomKmo8uQKSzKDVHe8k/jazYYG88 VdWD/I7rFE9nD9rYJ6nyGOYm+dZ9xtvmgmi+c6wEdBxytQ17JbCJRtz6lUuuSOD35zSY JXgg==
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=MzjBRWZV4FTFFJ47qQN8bPxaDTuWz+EC0JSTCDKYPeQ=; b=jZzCSYd+uPMGbVoy04D+EnCkOdcyaUGvLWhhfi7K2JUpp3Ge2KaqfBJKhwgkrsYUSy u2AMUruouaUxqkcL1zz8KU1dupUPfzFlbHB6NV2xV6XWSDwZidVrDS23Suhvp4AsjcxQ 5AnCI7zqzsZP8Y6C66EXLS/YyX7GqmmSoza0uO2eBEH9SzcdTZhC9EaVfjN+QEZWfLCL DDu0W4+zwFH2//dRuNfV3/vPLxwtKgwZS6PvxkVHKOd0xuwUCNM1vkg7ZLCTorrsmsM/ nBQkIKy7hJepr1SjlUqO8ulgjWDjMU85z3i0raskgBrPBWhWmdBkvyG3bLHio6Jx+5gI tcQw==
X-Gm-Message-State: ANoB5pmjsijoxLBXiFNXoogKYaN+WUZq4YgsiimY0j3nfGiWbWIE7Kqz mhQYJkpLRPrDtjieO/aW3uPN9VDjMlZCP+uHYoFvTw==
X-Google-Smtp-Source: AA0mqf7R32cZkEVBXM5ZtJme1OMOLcMMFqO9V4KisBfKEuSiOBVocF8sQRhccgjd4/EFHxToiRxirPlYoodFaoQ9XM0=
X-Received: by 2002:a17:906:9f04:b0:7ae:ed2:5367 with SMTP id fy4-20020a1709069f0400b007ae0ed25367mr3230783ejc.521.1668198743970; Fri, 11 Nov 2022 12:32:23 -0800 (PST)
MIME-Version: 1.0
References: <CAH6gdPzcMxor9hZy=+hS5oZPB_onU45-vh-ijm1jD2WPb0y+Gw@mail.gmail.com> <CAOj+MMGhpxG3eMmdk+Sqk_erapJUM8tjv-Sqm2J66KOEh1Ctrw@mail.gmail.com> <CAH6gdPxd8NfqNYaLjuPdyJ-RP1ezrprq=bkcXto8PBCvQ9j-RQ@mail.gmail.com>
In-Reply-To: <CAH6gdPxd8NfqNYaLjuPdyJ-RP1ezrprq=bkcXto8PBCvQ9j-RQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 11 Nov 2022 21:33:46 +0100
Message-ID: <CAOj+MMFWqnAT=rGLOJe0wkAR+5W_Qm8=v5OdEHFDByZYcZyvQg@mail.gmail.com>
To: Ketan Talaulikar <ketant.ietf@gmail.com>
Cc: Gyan Mishra <hayabusagsm@gmail.com>, BESS <bess@ietf.org>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008cb65a05ed37c9d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Y_3c0E-_7iguda3pLWocQjqrWGg>
Subject: Re: [bess] Suggestion on v4-only/v6-only drafts
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Nov 2022 20:32:29 -0000

Hi Ketan,

> I believe you are referring to the "BCP" (of Informational) content of
these drafts.

Quite the opposite ... I am referring to the Standards Track content ..
especially in respect to the IDR draft:

https://datatracker.ietf.org/doc/draft-mishra-idr-v4-islands-v6-core-4pe/

I do not find anything new in it that would not have already been
standardized. Especially I see lot's of text verbatim copied from RFC8950.

As far as BESS drafts I refrain from commenting as those drafts are IMO
unreadable. If you have an abstract spanning 3 pages and a quote to list
over 30 references that is right there not a good sign.

Thx,
R.


On Fri, Nov 11, 2022 at 1:43 PM Ketan Talaulikar <ketant.ietf@gmail.com>
wrote:

> Hi Robert,
>
> I believe you are referring to the "BCP" (of Informational) content of
> these drafts. If so, my impression is that the authors wanted to put this
> information together for the benefit of the operator community. I'll let
> them respond.
>
> You can see my comments during the BESS WG adoption poll for one of the
> drafts here [1].
>
> My concern was more the parts that need standardization need to be called
> out very succinctly (in hopefully a short draft) and the rest is all simply
> informational material that can be clubbed together to perhaps make more
> efficient use of reviewers time.
>
> Thanks,
> Ketan
>
> [1]
> https://mailarchive.ietf.org/arch/msg/bess/Wj-Y_m-t7C0bZ90NM-hmQbOYoPY/
>
>
> On Fri, Nov 11, 2022 at 5:59 PM Robert Raszuk <robert@raszuk.net> wrote:
>
>> Hi Ketan,
>>
>> If you are referring to interconnecting v4 only sites draft I have number
>> of comments:
>>
>> * The draft is not needed at all
>>
>> * we can seamlessly interconnect v4 sites over v6 core using v4 mapped v6
>> addresses
>>
>> * Zero control plane change is required/needed
>>
>> * number of vendors are shipping it
>>
>> Moreover sites even if today speaking v4 only sooner then later will talk
>> also v6. We can not ship a std track document which makes v6 deployment
>> harder or no-op for any site.
>>
>> Best,
>> Robert
>>
>> On Fri, Nov 11, 2022, 11:19 Ketan Talaulikar <ketant.ietf@gmail.com>
>> wrote:
>>
>>> Hi Gyan,
>>>
>>> Sharing a couple of suggestions here for your 5 drafts (4 in BESS + 1 in
>>> IDR) as we lost time due to the audio issues:
>>>
>>> (1) put the portions to be standardized (very focussed/small hopefully)
>>> in one single draft and post/share with both IDR and BESS since you are
>>> changing NH encoding (from what I heard?)
>>> (2) all other informational/BCP material could be combined in a single
>>> draft (perhaps the existing BESS WG draft)
>>>
>>> IMHO, that would facilitate an appropriate focussed review of the
>>> content/proposals.
>>>
>>> Thanks,
>>> Ketan
>>>
>>> _______________________________________________
>>> BESS mailing list
>>> BESS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/bess
>>>
>>