[Dyncast] Updates on Dyncast drafts

Dirk Trossen <dirk.trossen@huawei.com> Mon, 15 February 2021 17:18 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: dyncast@ietfa.amsl.com
Delivered-To: dyncast@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A5B363A0E00 for <dyncast@ietfa.amsl.com>; Mon, 15 Feb 2021 09:18:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id IdQS4kKeLinb for <dyncast@ietfa.amsl.com>; Mon, 15 Feb 2021 09:18:39 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 986663A0DE6 for <dyncast@ietf.org>; Mon, 15 Feb 2021 09:18:39 -0800 (PST)
Received: from fraeml735-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DfW043WZdz67pJR for <dyncast@ietf.org>; Tue, 16 Feb 2021 01:13:24 +0800 (CST)
Received: from lhreml702-chm.china.huawei.com ( by fraeml735-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Mon, 15 Feb 2021 18:18:31 +0100
Received: from lhreml701-chm.china.huawei.com ( by lhreml702-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Mon, 15 Feb 2021 17:18:30 +0000
Received: from lhreml701-chm.china.huawei.com ([]) by lhreml701-chm.china.huawei.com ([]) with mapi id 15.01.2106.006; Mon, 15 Feb 2021 17:18:29 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: "dyncast@ietf.org" <dyncast@ietf.org>
Thread-Topic: Updates on Dyncast drafts
Thread-Index: AdcDvSx2r+cf0yWpRWyYDcGimwJNKQ==
Date: Mon, 15 Feb 2021 17:18:29 +0000
Message-ID: <33e65ba11ecb471b83248bf0a5aafc73@huawei.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_33e65ba11ecb471b83248bf0a5aafc73huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/ObZqTQzNyABCdzygLR7WTtSacbg>
Subject: [Dyncast] Updates on Dyncast drafts
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dyncast.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dyncast>, <mailto:dyncast-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dyncast/>
List-Post: <mailto:dyncast@ietf.org>
List-Help: <mailto:dyncast-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dyncast>, <mailto:dyncast-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2021 17:18:42 -0000

Dear All,

For the preparation to the planned side meeting at the upcoming IETF110 (more details on this will follow in a separate email), it is our intention to formulate use cases, problems and architectural requirements for addressing those problems in order to focus this side meeting on the following two main questions:
1. Are the use cases compelling and the problems worth to be discussed and possibly solved in the routing area?
2. What would be the best approach in doing so within the IETF, e.g., through a new WG focusing on dyncast or through contributions to existing, protocol-specific WGs, with problem and requirements kept as contributions to the RTG WG?

Depending on what the community thinks, we will go for a more formal meeting at IETF111.

As input material for our discussion, we have uploaded the following three Dyncast drafts to the datatracker, namely the Dyncast use case and problem statement at https://www.ietf.org/archive/id/draft-liu-dyncast-ps-usecases-01.txt and the Dyncast requirements at https://www.ietf.org/archive/id/draft-liu-dyncast-reqs-00.txt. We have also uploaded a draft outlining a possible Dyncast architecture at https://www.ietf.org/archive/id/draft-li-dyncast-architecture-00.txt

Any comments or views on either of those two questions above are warmly welcome in preparation to the planned side meeting. We hope to see many of you there.


Dirk (on hehalf of the authors of the Dyncast drafts)