Re: [Detnet] [DetNet] Discussion on the WAN application in DetNet charter
Lou Berger <lberger@labn.net> Tue, 30 June 2020 10:05 UTC
Return-Path: <lberger@labn.net>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC543A115C for <detnet@ietfa.amsl.com>; Tue, 30 Jun 2020 03:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7XTLLx-hFZ1 for <detnet@ietfa.amsl.com>; Tue, 30 Jun 2020 03:05:48 -0700 (PDT)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E41DB3A1160 for <detnet@ietf.org>; Tue, 30 Jun 2020 03:05:47 -0700 (PDT)
Received: from cmgw14.unifiedlayer.com (unknown [10.9.0.14]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id 35AAF1E0870 for <detnet@ietf.org>; Tue, 30 Jun 2020 04:05:46 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id qD97jnfiBwNNlqD98jMdpn; Tue, 30 Jun 2020 04:05:46 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.3 cv=ZozD1ezG c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=nTHF0DUjJn0A:10:nop_rcvd_month_year a=Vy_oeq2dmq0A:10:endurance_base64_authed_username_1 a=r77TgQKjGQsHNAKrUKIA:9 a=1RTuLK3dAAAA:8 a=wU2YTnxGAAAA:8 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=0FD05c-RAAAA:8 a=dly4R1Ai8-zOeOADJfcA:9 a=avEM7_zoLP-kD5X4:21 a=w_vHeMqef_qcuOxL:21 a=CjuIK1q_8ugA:10:nop_charset_2 a=iNKulzQrdWWucG9jPiUA:9 a=CX3PEThGmL5Lcasp:21 a=wbrtIyoeTE0GmdJB:21 a=eh7uzM-ACoPYxfL8:21 a=_W_S_7VecoQA:10:nop_html a=kRpfLKi8w9umh8uBmg1i:22 a=Yz9wTY_ffGCQnEDHKrcv:22 a=w1C3t2QeGrPiZgrLijVG:22 a=l1rpMCqCXRGZwUSuRcM3:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:MIME-Version:Subject:References:In-Reply-To: Message-ID:Date:CC:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=7TDFrcV9+ajz4zdQfcLKMX3N0+Y81lFxyV4Lxh1/yvk=; b=yi0bYYNtCTfv9P6sS1O0i6srvo Wnu9xrJZkjM4rlHMWo4NjVmzOlH5qZkNJQ8CfGeCsQ+CEDBTBGmoLySP/hFykU6jZrr0YawtzkSEP cDMIefTGfmfpuwDUk3rG97+8H;
Received: from pool-100-15-105-234.washdc.fios.verizon.net ([100.15.105.234]:47930 helo=[11.5.0.140]) by box313.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <lberger@labn.net>) id 1jqD97-001VcI-NX; Tue, 30 Jun 2020 04:05:45 -0600
From: Lou Berger <lberger@labn.net>
To: xiong.quan@zte.com.cn
CC: detnet@ietf.org, "janos.farkas@ericsson.com" <Janos.Farkas@ericsson.com>
Date: Tue, 30 Jun 2020 06:05:45 -0400
Message-ID: <17304b088a8.277b.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <202006301453425267312@zte.com.cn>
References: 202006291721150302451@zte.com.cn <202006301453425267312@zte.com.cn>
User-Agent: AquaMail/1.24.0-1585 (build: 102400006)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------17304b08b3066bc277b19c5b4b"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.105.234
X-Source-L: No
X-Exim-ID: 1jqD97-001VcI-NX
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-105-234.washdc.fios.verizon.net ([11.5.0.140]) [100.15.105.234]:47930
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/EeQuY0dC9vpXJG5R0zJMV8gYO-4>
Subject: Re: [Detnet] [DetNet] Discussion on the WAN application in DetNet charter
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2020 10:05:50 -0000
Quan, Multi-domain is also in scope when those domains are "within a closed group of administrative control". Lou ---------- On June 30, 2020 2:54:41 AM <xiong.quan@zte.com.cn> wrote: > Hi Lou, > > > Thanks for your further clarification! > > I totally get that the DetNet mainly focus on a single administrative > control not a domain. > > In that case, DetNet can provide the end-to-end control and deterministric > properties. > > > > > Best Regards, > > Quan > > > > >>Re: [Detnet] [DetNet] Discussion on the WAN application in DetNet charter >>Lou Berger <lberger@labn.net> Mon, 29 June 2020 10:09 UTCShow header > > >>Quan, > >>Please read the use cases document -- which are just examples BTW. > >>As previously stated DetNet's scope is NOT limited to small or even single >>administrative control. "networks that are under a single administrative >>control or within a closed group of administrative control" includes any >>size network as well as any network under multiple party control when >>those parties cooperate on that control. > >>For example this may include all networks controlled by your favorite >>national mobile operator, anyone they buy network services from and anyone >>they sell services to. just as an example. > >>If you have a specific use case that you'd like to verify I suggest to >>describe it to the WG -- it's often easier to talk specifics than >>hypotheticals. > >>Lou > > > > > ---------- > On June 29, 2020 5:22:54 AM <xiong.quan@zte.com.cn> wrote: > >> Hi Lou, Janos and Andy, >> >> >> Thanks for your clarification! It is very appreciated! >> >> >> >> >> I probably understand the scope of the DetNet. The networks which are in a >> single administrative control are in scope of the DetNet. >> >> For example, the mobile backhaul network which is in a single >> administrative control is defintly included in DetNet. >> >> But what about the small networks which belong to different domains and >> large networks which belong to a single domain? >> >> IMO, the description in charter is confuesd. It only mentions the >> campus-wide networks and private WANs. >> >> >> >> >> Best Regards, >> >> Quan >> >> >> >> >> >>>Re: [Detnet] [DetNet] Discussion on the WAN application in DetNet charter >>>"Andrew G. Malis" <agmalis@gmail.com> Sun, 28 June 2020 21:21 UTCShow header >> >> >>>Quan, >> >>> Mobile backhaul is absolutely in scope, see section 6 of RFC 8578 for a >>> discussion. In addition, section 10 talks about its use with 5G bearer >>> networks. That RFC also has a number of other use cases. >> >>> Cheers, >>> Andy >> >> >> On Sun, Jun 28, 2020 at 3:28 PM Janos Farkas >> <Janos.Farkas=40ericsson.com@dmarc.ietf.org> wrote: >> >>> I fully agree with Lou. >>> >>> >>> >>> DetNet is NOT limited to small networks. >>> >>> As I wrote before, the key point is that DetNet is not for the big I >>> Internet. One reason is not to try to boil the ocean. >>> >>> Note that a key motivation for establishing DetNet was to be able to go >>> larger scale than TSN. >>> >>> >>> >>> Regards, >>> >>> Janos >>> >>> >>> >>> *From:* Lou Berger <lberger@labn.net>> *Sent:* Sunday, June 28, 2020 12:28 PM >>> *To:* xiong.quan@zte.com.cn; detnet@ietf.org> *Cc:* Janos Farkas >>> <Janos.Farkas@ericsson.com>om>gt;om>; detnet-chairs@ietf.org> *Subject:* Re: >>> [Detnet] [DetNet] Discussion on the WAN application in >>> DetNet charter >>> >>> >>> >>> Quan >>> >>> The key statement below is "networks that are under a single >>> administrative control or within a closed group of administrative control" >>> -- this statement allows for any sized network and does NOT restrict >>> DetNets to " small networks ". >>> >>> I suspect the types of networks you mention below will generally be built >>> "under a single administrative control or within a closed group of >>> administrative control". >>> >>> Lou >>> ------------------------------ >>> >>> On June 28, 2020 3:42:40 AM <xiong.quan@zte.com.cn> wrote: >>> >>> Dear Chairs and WG, >>> >>> >>> >>> I noticed that in DetNet Charter, it mentions that the networks which WG >>> foucs on as following shown. >>> >>> "The Working Group will initially focus on solutions for networks that are >>> under a single administrative control or within a closed group of >>> administrative control; these include not only campus-wide networks but >>> also can include private WANs. The DetNet WG will not spend energy on >>> solutions for large groups of domains such as the Internet." >>> >>> IMO, this description seenms to restrict the WAN application and limit the >>> DetNet to the small networks. >>> >>> I am not sure the WAN such as Metropolitan area network and Mobile >>> backhaul network is in the scope of DetNet. >>> >>> Could you please make some clarification about that? Thanks! >>> >>> >>> >>> Best Regards, >>> >>> Quan >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> detnet mailing list >>> >>> detnet@ietf.org>>> https://www.ietf.org/mailman/listinfo/detnet>>> >>> >>> _______________________________________________ >>> detnet mailing list >>> detnet@ietf.org> https://www.ietf.org/mailman/listinfo/detnet>> >> ---------- >> _______________________________________________ >> detnet mailing list >> detnet@ietf.org> https://www.ietf.org/mailman/listinfo/detnet> > > ---------- > _______________________________________________ > detnet mailing list > detnet@ietf.org > https://www.ietf.org/mailman/listinfo/detnet >
- [Detnet] [DetNet] Discussion on the WAN applicati… xiong.quan
- Re: [Detnet] [DetNet] Discussion on the WAN appli… Lou Berger
- Re: [Detnet] [DetNet] Discussion on the WAN appli… Janos Farkas
- Re: [Detnet] [DetNet] Discussion on the WAN appli… Andrew G. Malis
- Re: [Detnet] [DetNet] Discussion on the WAN appli… xiong.quan
- Re: [Detnet] [DetNet] Discussion on the WAN appli… Lou Berger
- Re: [Detnet] [DetNet] Discussion on the WAN appli… xiong.quan
- Re: [Detnet] [DetNet] Discussion on the WAN appli… Lou Berger
- Re: [Detnet] [DetNet] Discussion on the WAN appli… Grossman, Ethan A.
- [Detnet] 答复: [DetNet] Discussion on the WAN appli… xiong.quan