[Detnet] proposed revised Charter
Janos Farkas <Janos.Farkas@ericsson.com> Fri, 06 March 2020 14:29 UTC
Return-Path: <Janos.Farkas@ericsson.com>
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 152D63A07C6; Fri, 6 Mar 2020 06:29:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 QVYI9hFpirJM; Fri, 6 Mar 2020 06:29:34 -0800 (PST)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00068.outbound.protection.outlook.com [40.107.0.68]) (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 5A4143A07C0; Fri, 6 Mar 2020 06:29:34 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kcQWEOOal69o2bik4wGpii7Zs+q4ts9RbLTsloFatixKAGSkUTAB1wzx1zsvfa7sdPvLKQgjRqnDx/arZRyldmNuUdpXqT/0Naln+aepaf6GIrOmitpOGA0+hPhexXuhkDq0JNrDEtaPS4dwSvzoLUx9qLrrbfXO0nGsFugogp9zqQE4ja7euq3FmfVJsb1dmS7+vN5grns1YIAsykqoHSu7spnpydWzJzGfE/Q0VKUuT3p/LW1AfUMEJWiE8pKOmz0ul9u2LuSF7C+dMYT9UbfIJJKWmnc0Hp/wbK+EHM0OwKyxVOvyc5lA7gpEETI27jFao0dSXwBsT765jibFZQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=reF/NvdAE5dq3xi3f/CergXBQSuqg8pQYEmLxXAhMVE=; b=RgnG0CCiZGG+DeG2z8aya1Ke7PqpAMq9P1zTCRqCUrRw/fb5vQsVT4cxYjplXMMuIguy08htsOxPJxCDkDyQJrtF8de6+KQ1EyjDUmKkIkgaCubJ74u/3a7QG9Qi6wDR1fmcNrRIVdXzGPZTMZ0mJzmmIoQXDbx7xmaaxbutFq4/G9MQR8HqDIQvAQbzdHSyiiMZzAe3U3t9WEl54oaqlsqVt2yxdchdb12kw1m7hUQSyXJrjNt1YKenq5vbJijCzYv6HMVJRkuC4LQSy98WZ8aDo8Tuz7Rum1isdcNmqg87bZmpQrVw/aZpWjmyUOu0J2YX4lEGLLQGu7kT4EKzwg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=reF/NvdAE5dq3xi3f/CergXBQSuqg8pQYEmLxXAhMVE=; b=NtCDZgZZS60ozIy9QFWCIbO/PWS5a9afOfJqHoziHsfzrajysDuHtdYgYXWYJadxPr9tratqJ2Kr6fex+K5KvcdfEj+GBp37mp6AmwuTXd/vB5Hb5JNRK9fdgFKNpb14rO+cGqXjx8Uv30r86QgOsywWFSkbDZ2guHzKxcRSYDk=
Received: from VI1PR07MB4415.eurprd07.prod.outlook.com (20.176.2.145) by VI1PR07MB4429.eurprd07.prod.outlook.com (20.176.4.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.11; Fri, 6 Mar 2020 14:29:31 +0000
Received: from VI1PR07MB4415.eurprd07.prod.outlook.com ([fe80::75e0:7958:2a2d:9f90]) by VI1PR07MB4415.eurprd07.prod.outlook.com ([fe80::75e0:7958:2a2d:9f90%7]) with mapi id 15.20.2793.013; Fri, 6 Mar 2020 14:29:31 +0000
From: Janos Farkas <Janos.Farkas@ericsson.com>
To: DetNet WG <detnet@ietf.org>
CC: DetNet Chairs <detnet-chairs@ietf.org>
Thread-Topic: proposed revised Charter
Thread-Index: AdXzw4Na/3Iyfl7kTAGzUI0+7HmeLA==
Date: Fri, 06 Mar 2020 14:29:31 +0000
Message-ID: <VI1PR07MB4415A43D54F389223C378B89F2E30@VI1PR07MB4415.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Janos.Farkas@ericsson.com;
x-originating-ip: [176.63.29.69]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 70b40a59-31dd-43fd-94d7-08d7c1dac910
x-ms-traffictypediagnostic: VI1PR07MB4429:
x-microsoft-antispam-prvs: <VI1PR07MB4429D51B793196EE19FF7F0DF2E30@VI1PR07MB4429.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3631;
x-forefront-prvs: 0334223192
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(136003)(396003)(366004)(376002)(39860400002)(189003)(199004)(7696005)(8936002)(5660300002)(81166006)(66556008)(6506007)(66946007)(66446008)(64756008)(66476007)(52536014)(9686003)(478600001)(4326008)(966005)(26005)(8676002)(186003)(81156014)(316002)(66574012)(6916009)(55016002)(76116006)(450100002)(71200400001)(33656002)(7116003)(2906002)(86362001)(3480700007); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB4429; H:VI1PR07MB4415.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6dcN4hhrnrm62uuWAJBZNH+baIzdl+JtcisCilTfhcpRSbC5LXvkuEaWLcIIImP7k9smN6cPeNsEhoLHINYuI75LC6/RsWTEkhABvyN62mwPJYOaOsQdQpUoC9wFXXoEXTGI5yiUH3iOa/v+Qu9c/K1nsSaDRF8yVeigwzSRNXUCuVQ3Lj9+7oqGDLUC+6T03xerCNy+RUCoAyxGRI8/1xtlEDOKwrLtlxs8Inn9AhZh1lk6wyLyxUXyPoIU+IVigxrnnXvqzhK27rkiDTWVKTU0HfCMD+ej5Q2FbjZvtRAANPhk5c0QzZriBHE8uSPDBZP4wvb6An41HITzGwhI1alPBVgncsYPIQXfBWLC5amb3Vi9GlEowmOQI+rP+d3HBlufanegt80fbmWlf4zvk91aLHn8enRtm8CmSdCKHElkI7knb7pX3M1KbIshFdVSI1Su1933Pq3PpPiE3ooREd2qQyEek6FJTPk048+vHUkC5O3JQj+NFsAytx3GtGkMffrXpiJPHb6hBYL75XjrIg==
x-ms-exchange-antispam-messagedata: B3TmUxp38P7J7J2DThc+aIWl+vx3uY9efvbRGLBNwZBy0kixmAe0OV28bjUKB/0akdNketXh6RHCB+fGfIKzyAgc9zuKvKmctIbRDvD/1+lXe+dR5HaKHZi1/EGsjtKn5JQA6nq9gIRoXa+/Elw6RQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_VI1PR07MB4415A43D54F389223C378B89F2E30VI1PR07MB4415eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 70b40a59-31dd-43fd-94d7-08d7c1dac910
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2020 14:29:31.5430 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: eSojymt4ozlRmDBFippV+aSUhB/ydCWHr6ZN/dk1Nojt7MVKNWZrhegmaBiTKwURyFXzG+ZCl0nAmrVA5cEH46xwbYC120HgwVNm/ac9+Ac=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4429
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/_kNsJscFrwiD8BeWF7AcH3FmOEE>
Subject: [Detnet] proposed revised 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: Fri, 06 Mar 2020 14:29:37 -0000
WG, As discussed at the last IETF, it is time for us to update our charter. We have put together the following proposal: The Deterministic Networking (DetNet) Working Group focuses on deterministic data paths that operate over Layer 2 bridged and Layer 3 routed segments, where such paths can provide bounds on latency, loss, and packet delay variation (jitter), and high reliability. The Working Group addresses Layer 3 aspects in support of applications requiring deterministic networking. The Working Group collaborates with the IEEE 802.1 Time-Sensitive Networking (TSN) Task Group, which is responsible for Layer 2 operations, to ensure an aligned architecture for both Layer 2 and Layer 3. Example applications for deterministic networks include professional and home audio/video, multimedia in transportation, engine control systems, and industrial automation, as well as other general industrial and vehicular applications being considered by the IEEE 802.1 TSN Task Group. 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 address solutions for large groups of domains such as the Internet. The Working Group is responsible for the overall DetNet architecture and DetNet-specific specifications that encompasses the data plane, OAM (Operations, Administration, and Maintenance), time synchronization, management, control, and security aspects which are required to enable a multi-hop path, and forwarding along the path, with the deterministic properties of controlled latency, low packet loss, low packet delay variation, and high reliability. The work applies to point-to-point (unicast) and point-to-multipoint (multicast) flows which can be characterized in a manner that allows the network to 1) reserve the appropriate resources for the flows in advance, and 2) release/reuse the resources when they are no longer required. The work covers the characterization of flows, the encapsulation of frames, the required forwarding behaviors, as well as the state that may need to be established in intermediate nodes. Layer 3 data plane technologies that can be used include: IP and MPLS, and Layer 2 encapsulations that run over IP and/or MPLS, such as pseudowires and GRE. The Working Group will document which deployment environments and types of topologies are within (or outside) the scope of the DetNet architecture. This work focuses on the data plane aspects and is independent from any path setup protocol or mechanism. The working group will also document DetNet Controller Plane [1] approaches that reuse existing IETF solutions, such as Path Computation Element (PCE), and identify the appropriate Working Group for any extensions needed to support DetNet. Documents produced by the Working Group will be compatible with the work done in IEEE802.1 TSN and other IETF Working Groups. The Working Group's scope explicitly excludes modifications of transport protocols, OAM, Layer 3 forwarding, encapsulations, and control plane protocols, but it may define requirements for such modifications and identify the appropriate Working Group for any needed modifications. DetNet is chartered to work in the following areas: Overall architecture: This work encompasses the data plane, OAM, time synchronization, management, control, and security aspects. Data plane: This work will document how to use IP and/or MPLS to support a data plane method of flow identification and packet forwarding over Layer 3. Other IETF defined data plane technologies may also be used. Controller Plane: This work will document how to use IETF control plane solutions to support DetNet. This work includes identification of any gaps in existing solutions and identifying the appropriate Working Group for any needed extensions. Data flow information model: This work will identify the information needed for flow establishment and control and be used by reservation protocols and YANG data models. The work will be independent from the protocol(s) used to control the flows (e.g. YANG+NETCONF/RESTCONF, PCEP or GMPLS). YANG models: This work will document device and link capabilities (feature support) and resources (e.g. buffers, bandwidth) for use in device configuration and status reporting. Such information may also be used when advertising the deterministic network elements to a control plane. Control plane related information will be independent from the protocol(s) which may be used to advertise this information (e.g. IS-IS or GMPLS extensions). Any new YANG models will be coordinated with the Working Groups that define any base models that are to be augmented. As needed, vertical requirements: This effort will detail the requirements for deterministic networks in various industries that have previously not been documented or cannot be supported using defined DetNet solutions. To investigate whether existing data plane encryption mechanisms can be applied, possibly opportunistically, to improve security and privacy. The Working Group coordinates with other relevant IETF Working Groups, including CCAMP, PCE, PALS, TEAS, OSPF, IS-IS, TSVWG, RAW, and 6TisSCH. As the work progresses, requirements may be provided to the responsible Working Group, e.g. PCE, TEAS, and CCAMP, with DetNet acting as a focal point to maintain the consistency of the overall architecture and related solutions. The WG will liaise with appropriate groups in IEEE and other Standards Development Organizations (SDOs). [1] The DetNet Controller Plane is defined in RFC 8655 as "the aggregation of the Control and Management Planes" The difference compared to the current charter is available at: https://etherpad.ietf.org:9009/p/detnet-recharter Our plan is to submit revised charter to the IESG after IETF 107. Given the number of remote participants, we are happy to have the discussion fully on the list. Please submit your comments on the list. Regards, Lou and Janos
- [Detnet] proposed revised Charter Janos Farkas
- Re: [Detnet] proposed revised Charter Andrew G. Malis
- Re: [Detnet] proposed revised Charter Grossman, Ethan A.
- Re: [Detnet] proposed revised Charter Pascal Thubert (pthubert)
- Re: [Detnet] proposed revised Charter Balázs Varga A
- Re: [Detnet] proposed revised Charter Lou Berger
- Re: [Detnet] proposed revised Charter Lou Berger
- Re: [Detnet] proposed revised Charter Greg Mirsky
- Re: [Detnet] proposed revised Charter Kingshuk Mandal
- Re: [Detnet] proposed revised Charter Gengxuesong (Geng Xuesong)
- Re: [Detnet] proposed revised Charter Grossman, Ethan A.
- Re: [Detnet] proposed revised Charter xiong.quan
- Re: [Detnet] proposed revised Charter Gengxuesong (Geng Xuesong)
- Re: [Detnet] proposed revised Charter Lou Berger
- Re: [Detnet] proposed revised Charter Lou Berger
- Re: [Detnet] proposed revised Charter Lou Berger
- Re: [Detnet] proposed revised Charter Lou Berger
- Re: [Detnet] proposed revised Charter Lou Berger
- Re: [Detnet] proposed revised Charter Black, David
- Re: [Detnet] proposed revised Charter Lou Berger
- Re: [Detnet] proposed revised Charter Black, David
- Re: [Detnet] proposed revised Charter Lou Berger