IETF Logo Mail Archive

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

Ketan Talaulikar <ketant.ietf@gmail.com> Fri, 11 November 2022 12:43 UTC

Return-Path: <ketant.ietf@gmail.com>
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 AA9C4C14F74E; Fri, 11 Nov 2022 04:43:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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, FREEMAIL_FROM=0.001, 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=gmail.com
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 mFxC97e2wYw3; Fri, 11 Nov 2022 04:43:50 -0800 (PST)
Received: from mail-oa1-x2a.google.com (mail-oa1-x2a.google.com [IPv6:2001:4860:4864:20::2a]) (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 E5AFAC14F738; Fri, 11 Nov 2022 04:43:50 -0800 (PST)
Received: by mail-oa1-x2a.google.com with SMTP id 586e51a60fabf-13ae8117023so5277376fac.9; Fri, 11 Nov 2022 04:43:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1bBwMHzuWubghAAkPl+1r+zRpwmwJVIaFmyFYyWN5BQ=; b=l4zp96723oipQr50pRUDzTV6cp1jIkD+lnEh6cld//JqHTTF3WMiViCPtlHamMkZ2k 9exDThrKmBWPjI6VMj/0J05O7E3HUMNFGnsYoUyH5AnbrQdZIphFuRNiWMfNMItpFbI2 Z+onD4eZV/S6ykE2AT+NtN7OMKsBLGADKFVl3eC2I2hHcYeclSvFhe1oH8vi1Cx4PTAH pMlhCpPiwSYUk+21YL1sceapAlZgqGvrN0jgxeT1E5AjID3oOgZSa3xgu6vLW89ATDIn FE3FTeS9bTO1Y+poB5NhSZbej207FA3OHmIm/QyvV0hlEf5LP6I6OBcdiB7ed8/okjim Qu0w==
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=1bBwMHzuWubghAAkPl+1r+zRpwmwJVIaFmyFYyWN5BQ=; b=uLn0Hw1K2zoRose07Osjf2YLILGkJ746hh4DFtcs744cLDmAC1Z1Hup/eyHbT3nAOu ZrU80QIywdWmnX3yb5WO3OEftH0l2Vul9GIVh5g5/cgkvG7Hn7FAT0+/n18FsNYNXwSQ QPdZrwEpOZjCtHLIRaZUd0rem1a2EHrFBAS4EfyWi/PZ9/E3J3WWWYBDc1poQwhA5oA9 8oL3gXp39cBtiMC56N9j+ymaTfkoawD9L7Ibq2wFZHPC9aGpNlCbCvWVR8rhuVWYpTyu 4/hjy6KImUQRMBar2JYtVBfE9ORKF8EIpwveCncOycSYL03ShfNlRji89FwNcSjP7mQG xhCw==
X-Gm-Message-State: ANoB5plkzJ6qVrHloSoOINs6QWI24T9koF+aEOGVr3lmT9mcAxrNoGFB yoyYCtNhwjOYeQu7SZr5oaUHzQ5or5PiS7SFbpE=
X-Google-Smtp-Source: AA0mqf6DVl7h4SRUPngsCgyA/NF2cuFLC6f/UMjMYkT+ImSrqxfY+pbEDs85sa71iyWkEPPoL8QKuY+FWi24kYsypsg=
X-Received: by 2002:a05:6870:f710:b0:132:7840:b966 with SMTP id ej16-20020a056870f71000b001327840b966mr654007oab.229.1668170629713; Fri, 11 Nov 2022 04:43:49 -0800 (PST)
MIME-Version: 1.0
References: <CAH6gdPzcMxor9hZy=+hS5oZPB_onU45-vh-ijm1jD2WPb0y+Gw@mail.gmail.com> <CAOj+MMGhpxG3eMmdk+Sqk_erapJUM8tjv-Sqm2J66KOEh1Ctrw@mail.gmail.com>
In-Reply-To: <CAOj+MMGhpxG3eMmdk+Sqk_erapJUM8tjv-Sqm2J66KOEh1Ctrw@mail.gmail.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Fri, 11 Nov 2022 18:13:37 +0530
Message-ID: <CAH6gdPxd8NfqNYaLjuPdyJ-RP1ezrprq=bkcXto8PBCvQ9j-RQ@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Gyan Mishra <hayabusagsm@gmail.com>, BESS <bess@ietf.org>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cf130a05ed313d3c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/GTLQbl4fp5uYHUjExOul82im3I4>
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 12:43:54 -0000

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
>>
>

v2.23.0 | Report a Bug | By Email