IETF Logo Mail Archive

[Din] Re: next steps for DINRG

Lixia Zhang <lixia@cs.ucla.edu> Mon, 21 October 2024 13:59 UTC

Return-Path: <lixia@cs.ucla.edu>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFD8C1D52FA for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 06:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Level:
X-Spam-Status: No, score=-2.005 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=cs.ucla.edu
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 xwYR0KuiU82v for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 06:59:01 -0700 (PDT)
Received: from mail.cs.ucla.edu (mail.cs.ucla.edu [131.179.128.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7423EC1D52F0 for <din@irtf.org>; Mon, 21 Oct 2024 06:59:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 0CEB73C011BC5; Mon, 21 Oct 2024 06:59:01 -0700 (PDT)
Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10032) with ESMTP id BqU6A_SVEasu; Mon, 21 Oct 2024 06:59:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id C0EE03C011BDD; Mon, 21 Oct 2024 06:59:00 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu C0EE03C011BDD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1729519140; bh=OnOpTJbtN8CsbK+GBqyIk+jK7j8F2dCnnIp5sMbXKZ8=; h=Mime-Version:From:Date:Message-Id:To; b=ge1yDKZDN4/++zg/YOcXtKShnPt2Z7DGy/H6R5VazBnER0ARcCDdwlE/5zu7Rph6K Aa7OorpkmYgNKlDY5y1ZNRpsfdz42E6VD/PHvuSjJCFmZ/9Nf8HtgQxxnscKurImn8 AbLHOQb1aus0SYCmAxCbUpe2etuJJqSYl1yjqbDFmhWAL0uK9Lt7JXMf2ir2sSvOMW PcRBMk6/o4pCno/w+J3cEaF8vV6opa/aNdXjkaMhOm1eGnfk60cepKe/0roj4xxFgI 8cCxUDA5qL/eayAY4kMPjO4eaKmvEka78PhCzYNAOA+HwPiFGM6iqJbhStPi7CCTtU ZIuVx85ty896A==
X-Virus-Scanned: amavis at mail.cs.ucla.edu
Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id lHTSAJHngy1b; Mon, 21 Oct 2024 06:59:00 -0700 (PDT)
Received: from smtpclient.apple (syn-076-091-005-005.res.spectrum.com [76.91.5.5]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id 9EC583C011BC5; Mon, 21 Oct 2024 06:59:00 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\))
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <SLXP216MB1148A522A273D65A18CBF2EBEE412@SLXP216MB1148.KORP216.PROD.OUTLOOK.COM>
Date: Mon, 21 Oct 2024 06:58:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <70809EE4-5B15-4E31-8040-BDE0B17F0698@cs.ucla.edu>
References: <18BAB346-D64A-40A3-A29B-9146562E5674@dkutscher.net> <6d66bdb8-b546-40b1-b723-ee8ac80b8adb@app.fastmail.com> <BYAPR01MB4391391642D149D59316D9F0CB402@BYAPR01MB4391.prod.exchangelabs.com> <SLXP216MB1148A522A273D65A18CBF2EBEE412@SLXP216MB1148.KORP216.PROD.OUTLOOK.COM>
To: "\"김우태(Operation연구TF)\"" <utae.kim@kt.com>
X-Mailer: Apple Mail (2.3818.100.11.1.3)
Message-ID-Hash: O33HFL64OXQHCHUDLOG57RULMTOTWSAC
X-Message-ID-Hash: O33HFL64OXQHCHUDLOG57RULMTOTWSAC
X-MailFrom: lixia@cs.ucla.edu
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-din.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "din@irtf.org" <din@irtf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Din] Re: next steps for DINRG
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/uYr26iBZzDxjRyX_JgBs8EH7TbE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Owner: <mailto:din-owner@irtf.org>
List-Post: <mailto:din@irtf.org>
List-Subscribe: <mailto:din-join@irtf.org>
List-Unsubscribe: <mailto:din-leave@irtf.org>

Hi Utae, 

note that DINRG is a research group. A research group explores  research topics but does not develop protocol standard.

regarding "changed directions about DINRG": You can find DINRG's recharter at https://datatracker.ietf.org/group/dinrg/about/

Lixia

> On Oct 19, 2024, at 1:29 AM, 김우태(Operation연구TF) <utae.kim@kt.com> wrote:
> 
> Dear All;
>  I have some questions about DINRG.
> At first, I know DINRG focused on standardization about distributed network architecture, and protocols.
> I can’t find progress till now from then, if anybody have for it, it’s better to share progress for us to understand and agree.
> (including changed directions about DINRG)
>  Thanks,
>  BR utae.

v2.28.0 | Report a Bug | By Email | System Status