Re: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 12 December 2022 08:59 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D66F2C14F741; Mon, 12 Dec 2022 00:59:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=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 VtdopGirHCXn; Mon, 12 Dec 2022 00:59:00 -0800 (PST)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 E8BA3C14F693; Mon, 12 Dec 2022 00:58:54 -0800 (PST)
Received: by mail-lj1-x235.google.com with SMTP id h10so11771007ljk.11; Mon, 12 Dec 2022 00:58:54 -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=4pM8q6bSj/6LmYf+HXx8golYUXPtdwDAEoo6zIQtcXo=; b=iQguMgnVH+R61pntzWLwPVt5QHDYOsBUMj4TCpwnp6to5nAS2gler1qPwY5Qz1rDcA uaLHG7LsNqsb8vL72uIUlU7oE+GUfqeKFy6cWalcC+IhtA1DciuFt4kbcUOTfMbHXWTR ACwdw0d+7w79pAYa4TqGdx1SPYgMTg1RY/YZG1XSzOQ5XpZIdGFQAY/IbNc7tamGhfm5 FNFbHboKd4Zhyr+r4OQ41HUb3H3dWDUFuwkyjWpxugP2ewcCoZYMjeLrTkagBBP2Kp+0 GFtBrIWxSaoQWtp1okJcx1Yf0Mfk3Bbz3+5yHH/VVW2zREqypqXRWi6GctdgDjfYxIGi Bbqw==
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=4pM8q6bSj/6LmYf+HXx8golYUXPtdwDAEoo6zIQtcXo=; b=uBFoBnarObB+lFx0L02dASfh1fcpzfaPMK+luXb61uotzMbk52Co2jhDOvL43P32i+ 5WhiI7zwIKNuUJLSuJytM8VDlxMYA20tCwMdi44EQNMRLfAlze1rykXgZPuGOcc0l+0+ BfSxiYj7afHuada+3JKz3obiB5F4z7Hf2KvmeV1sCQ1T0hnYTePN3DvoVSm94RI/lXHp RH9QOHs/2VFeJZkaxJVHlhyrVbFEII3z7ZdpkoRRJrFPU1uvwfV4cqvzCwZ1/gU2B48j 5E1LgxV9Vnh79H/qj3okvrrv6Z7oKDTRh/eGbm4cKIEge7/98WnH0tRwhfindSO8Nyw1 4e3Q==
X-Gm-Message-State: ANoB5plD869fKTtZbQDjTR3z5B3/W4pMge9JIsiUbE34H4w+oxOjAgC0 W5gMa0R11uzWiFBqyEdzNJZi/P+9jKtSuZ0OgSw=
X-Google-Smtp-Source: AA0mqf42i7a0msjZUrhJL3L3yXIZMjFu8UxT+Hn8QNe7cysBblCTP9uW/6stjbs0uZRN42wpVx7PkXTcnClfNIb8Adg=
X-Received: by 2002:a2e:9904:0:b0:27a:3b33:f425 with SMTP id v4-20020a2e9904000000b0027a3b33f425mr427463lji.349.1670835532925; Mon, 12 Dec 2022 00:58:52 -0800 (PST)
MIME-Version: 1.0
References: <CAH56bmBnqi4peTWUXOVy0KRRXRc1L7TP+atFfVF6qb_OKBMBwg@mail.gmail.com> <C303F9BF-F96A-4710-A4B5-4228807C07F7@gmail.com> <52907137-CA5A-4042-AB2C-23FD9B032210@gmail.com> <E1p2SAw-006HQa-3s@mta0.cl.cam.ac.uk> <2D989E7C-EBFB-42C4-9D55-F934A1437B19@gmail.com> <Y5M5PNT6PV/YsG/V@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <Y5M5PNT6PV/YsG/V@faui48e.informatik.uni-erlangen.de>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Mon, 12 Dec 2022 11:00:33 +0200
Message-ID: <CADnDZ88rbsee4wt_8sLVdXUztO_E6FyuMsHdRvF3NGmQ8j4bVQ@mail.gmail.com>
Subject: Re: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)
To: Toerless Eckert <tte@cs.fau.de>
Cc: Dino Farinacci <farinacci@gmail.com>, BIER WG <bier@ietf.org>, routing-discussion@ietf.org, tsv-area@ietf.org, Matt Mathis <mattmathis=40google.com@dmarc.ietf.org>, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, pim <pim@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006b122805ef9db6da"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/xBXp5N1-Rrdy-Pd5NxsXOarnlLg>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-area/>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2022 08:59:03 -0000

Thanks Toerless,

I agree we need more interaction between experts, and I will add also we
need interaction with directors.

On Fri, Dec 9, 2022 at 3:34 PM Toerless Eckert <tte@cs.fau.de> wrote:

> On Tue, Dec 06, 2022 at 12:54:57PM -0800, Dino Farinacci wrote:
> > > path exploration? but consider the shadow pricing...
> >
> > Just something semi-formal where we can meet regularly. But first,
> please lets articuulate the problem very clearly. And bring operators in so
> they can confirm the problem that researchers are stating are real problems
> that need solving.
>
> I actually would love to just have a standing forum to better bring
> routing researchers
> together with industrial routing experts.


IMHO, there are: Academic experts, Industry experts, and Research experts,
each engineer_expert has their methods, skills and experiences, some
ietf_participants have the three experience and some don't, however, we
need in IETF to have all to discuss together in all IETF WGs.

Aka: not focussed on a specific issue
> (as Tony's past RRG instance). E.g.: where researcher can ask questions to
> the experts, or propose
> research and ask if/how this is useful to the industry, and where industry
> folks can
> ask for researchers to look into specific issues (i think there are for
> example a lot of
> simulations to investigate behaviors that we'd like to have from the
> undustry).
>

Researchers should be engineering_experts, in IETF we are not Teaching we
are Working like any company that has research workers and research experts.


> Not sure if "Research Group" is the right name for this. I think it would
> be a lot
> closer to the SIG concept (
> https://wiki.ietf.org/en/group/iesg/specialinterestgroups),
> except that that concept was built and specified around interaction
> between IETF
> and operational considerations of a specific community. Not on bringing
> more researchers
> back to the IETF.
>

Yes IETF groups has separated Research Group (RG) drafts and Working Group
(WG) drafts, but still IETF does not separate participants or
engineering_experts. Is there an IETF_RFC that states that IETF WG
participants are only industry_experts?


> We do have a subset of what i think such an RRG would do in rtgwg -
> researchers bring ideas -
> and then they most often figure out that they can only proceed when they
> throw themselves
> fully into the RFC process (which most of them cannot/wantnot do). And
> from what i
> understand even this is not always welcome by rtgwg, because it does take
> a significant
> amount of time that folks feel should better be spent on actual WG
> deliverables.
>
> Of course, i am mostly interested in the ietf->research direction, e.g.:
> where the IETF
> community can better raise the questions of interest to be researched
> because the way i
> see it, there is no forum whatsover for this part.
>

All companies need excellent planning of products that need
engineering_research_experts, so there is a need for working with all
experts together with engineering_directions, not industry direction, not
academic direction and not research direction.

AB