[Raw] RAW updated charter
"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 18 September 2019 15:10 UTC
Return-Path: <pthubert@cisco.com>
X-Original-To: raw@ietfa.amsl.com
Delivered-To: raw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7119F1209A4; Wed, 18 Sep 2019 08:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=IXay29Oi; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=kJJV+uQS
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 yPlCJI0UsTlP; Wed, 18 Sep 2019 08:10:11 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9667120962; Wed, 18 Sep 2019 08:10:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29893; q=dns/txt; s=iport; t=1568819410; x=1570029010; h=from:to:cc:subject:date:message-id:mime-version; bh=CDXc0UczYa1H5WFs1lprxTi0gq24iMtn4iROncvAQ2w=; b=IXay29Oiy7ugH2Mt7xEE81ib+xlKqobRhB2Tb7F4yLVdQS8BYKge1dWd 1cmvU9LDuKCaBnkrLxXvtwEO45z43h70P0ggm2YIKCYvwJ850Slu5sHcQ +kBsgTFKw/JOnTT67u4dWK3bRrU5oz4cqD/bOuhneTlhDiDdkOvlp8jO+ 4=;
IronPort-PHdr: 9a23:8p8exBR7DZF54ZUHvWn1yCVutNpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOjQmHNlIWUV513q6KkNSXs35Yg6arw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BJEgBHSIJd/4kNJK1mHAEBAQQBAQcEAQGBZ4EWLyQsA21WIAQLKodpA4p4g1qPEQQOgmmCaIIBgUKBEANUCQEBAQwBASMKAgEBhD8CgwMjOBMCAwkBAQQBAQECAQUEbYUtAQuFTRYbEwEBLgkBEQFAQCYBBA4NEweDAYEdTQMdAQIMpTkCgTiIYYIlgn0BAQWFCRiCFwMGgTSMCRiBQD+BEAFGgheDVAKBKRIGAQEgK4MQgiaMcyGHaokhjmIKgiKHBYIQgwKCGYZvmSGOEIgPkHsCBAIEBQIOAQEFgWkhgVhwFTuCbFAQFIFOg3KFFIU/cwGBKIx6DheCLgEB
X-IronPort-AV: E=Sophos;i="5.64,521,1559520000"; d="scan'208,217";a="620127582"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 18 Sep 2019 15:10:09 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x8IFA96g018403 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 18 Sep 2019 15:10:09 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 18 Sep 2019 10:10:08 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 18 Sep 2019 11:10:08 -0400
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 18 Sep 2019 10:10:08 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=b4d/Syw6DvYk2dCMTd5n/hagmoaAe5S+zjvlNf5ynGFThFekF8sw/gr4VgPzBaECKZTt++efNZZoYqGDYTH7oAnvsibUIfoEN7SCWJnQMoA6NArEJI8eV0h7uIgXjaL8YhBfRor26nffTW0TuDxgwa3N8CUYQ8TMJnv9F80nmCqfZbcS0hLGZnOltIoGcPejnXd3XgDeKIeyy2O4cHOSJv9ui3VK43J5oY72SCqnzSCZhkWav9D1dY2cW4MQYqYxTPwtDw/fj3LDw1mYjMLuIA1EB62lRqwBg+ChonNH0Xr9ChSBATKzMeP5B04mPStfGgwEozskDHbA55qdbnBIew==
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=KV3SK05YUH7Ex/y6gzHkjYUzXP2aAAhv65Say6j6XeM=; b=jxqDzArb4g3KMH44DfevHaf0jKt76RXy/Pa9tFXzNMfpYzRfzgaWcfrD+Wr2rDQ9+cD2Y6R1QrlOSOVqswRk8qSSz0LuCQ6N1rWmODliHl7jyPKNDvRLpez4fnELy4F4MKXrIw2TFAX+dYfQUmO9NuvbO1BD9ypMler3q1BzFPGgSZZOCsw6Ncjar/zB3nXWXFDr2hGtcSD2/UJKCGZv6/I1noh4w8+QV9dQLANmSqYOTN4to7fkOlFWEUCoQMk4GswqwVCal1HPTMaB4ulp5YnVUGRqJdwcHyGMR8jpI2ENitbwvIMbnFh/DzXaWYRaUDuO5QKjv+suon3frz4i6Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KV3SK05YUH7Ex/y6gzHkjYUzXP2aAAhv65Say6j6XeM=; b=kJJV+uQSWvVpVqLcaXsp3a0/ZTbv/VSEb5CCmLRcvDMgq1HRsS6KjARtbwXw8i+KwwNlzeVM03Flj3o4vsudRz3oXUDndW4cOimjCPSXZtZxxgtNGvoRmS9y/fTeq3jvGO/Lv1Ex2XbXXCFB0qCI8KwlOyR4qphmr1I88flEJM8=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4032.namprd11.prod.outlook.com (20.179.149.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.13; Wed, 18 Sep 2019 15:10:07 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::6986:12d5:b54f:f5ee]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::6986:12d5:b54f:f5ee%7]) with mapi id 15.20.2263.023; Wed, 18 Sep 2019 15:10:07 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "raw@ietf.org" <raw@ietf.org>
CC: "detnet-chairs@ietf.org" <detnet-chairs@ietf.org>, "'Grossman, Ethan A. (eagros@dolby.com)'" <eagros@dolby.com>, "Dr. Corinna Schmitt" <corinna.schmitt@unibw.de>
Thread-Topic: RAW updated charter
Thread-Index: AdVuMujF/HmNokwNTx+VmqISIapSgg==
Date: Wed, 18 Sep 2019 15:09:39 +0000
Deferred-Delivery: Wed, 18 Sep 2019 15:09:21 +0000
Message-ID: <MN2PR11MB3565D06ACBFD638CD0D1047CD88E0@MN2PR11MB3565.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [2001:420:44f3:1300:151a:fc55:1e6d:b77c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 11f0e862-0731-405a-1ee2-08d73c4a4a87
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600167)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB4032;
x-ms-traffictypediagnostic: MN2PR11MB4032:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB4032329315EE53366F32BA7CD88E0@MN2PR11MB4032.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01644DCF4A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(39860400002)(396003)(376002)(346002)(136003)(189003)(199004)(102836004)(2501003)(14454004)(86362001)(6436002)(6506007)(54906003)(7696005)(55016002)(99286004)(790700001)(6116002)(52536014)(14444005)(606006)(256004)(316002)(6916009)(7736002)(5660300002)(2906002)(71190400001)(66446008)(8936002)(81166006)(2351001)(81156014)(71200400001)(486006)(478600001)(6666004)(8676002)(33656002)(476003)(7116003)(3480700005)(74316002)(966005)(64756008)(66946007)(66556008)(66476007)(76116006)(1730700003)(186003)(25786009)(54896002)(9686003)(5640700003)(6306002)(46003)(4326008)(236005); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4032; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 3K2dmM1kxx1DOqfKwLlEV2w7PrGEmsidWh+TjNc5GE24vCgfq+uQSYb3DhXskzSMGvrpbgcjCMWpaxYTK9RvAjvvAVEdnI4NYsyveNF2VSrsi6/2i+rjg61i94gqpYOJcZCx8jZ7bPg+Xjyciwa4eQIX4+QWLmiKik1Zt0qeq/6ioELvqu5aY4/UCJBP1M+2r5L6nK1A+EVGtlHnb18BUSOhJIfS6QYQokKM3coBiblyJ74TqDCHyVQ5YYrygCtiJHsC/LY/PiPyDenm9A2QHSC2sAtpttNoVDU/NNkPpGXlyY/PzqNzKz9dlH2qiy573O8+SDwHo6efe/Thg/da//jQnO9AJR6mFpSzGZcNyWL4PuKbHSUc5jsJTrNFmhmiiPIyWkF0GYo3IJ0x37z8eRQNeDOozi3bEdjFENJklj8=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB3565D06ACBFD638CD0D1047CD88E0MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 11f0e862-0731-405a-1ee2-08d73c4a4a87
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Sep 2019 15:10:07.0760 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: FZppWlZPuJnjV8GrC8cnzVpYMVsgsYKNqfmySP00HPZnRYDvZ0jQAbWGFkEPC6xc6/qe0MnO1dOyLCDWCp2SWA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4032
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/1cTEoOQN1YafAbBB2lfKU7msXAM>
Subject: [Raw] RAW updated charter
X-BeenThere: raw@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: reliable and available wireless <raw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/raw>, <mailto:raw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/raw/>
List-Post: <mailto:raw@ietf.org>
List-Help: <mailto:raw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/raw>, <mailto:raw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 15:10:20 -0000
Dear all At the meeting at IETF 105, a number of comments were discussed. In particular, Lou's point about whether RAW is a technology group (over foo) or a L2 agnostic IP layer thingy. As a way to program TSCH it was an over foo. As a DetNet inheritance it was IP layer. We had to choose. The discussion leaned towards an IP layer thingy, which leaves the TSCH programming out. On the side, we had to open to other technologies but since it is hard to say that we work on *, we thought that keeping a list of focus technologies on which we can evaluate our proposals (like LPWAN does for instance) was still preferable. Another comment was to clarify the scope. We are now clearly a specialization of DetNet. Janos indicated in a long mail that it could mean that the work should be done within DetNet. Considering the load at DetNet and the current interests, I tend to prefer a separate group with a focus, see note1 below. On the side, we appear to be the only BoF request for Singapore https://trac.tools.ietf.org/bof/trac/wiki . We need all hands on the deck this time! I maintain the charter here: https://trac.tools.ietf.org/bof/trac/wiki/RAW and cc'ed the current very below. Proposed charter --------------------- Bringing determinism in a packet network means eliminating the statistical effects of multiplexing (jitter and collision loss) in the transmissions. Wireless networks operate on a shared medium, and thus transmissions cannot be fully deterministic due to uncontrolled interferences, including the self-induced multipath fading. However, scheduling the transmissions can alleviate those effects by leveraging diversity in the spatial, time and frequency domains, providing a more reliable and available service. Deterministic Networking is an attempt to mostly eliminate packet loss for a committed bandwidth with a guaranteed worst-case end-to-end latency, even when co-existing with best-effort traffic in a shared network. This innovation is enabled by recent developments in technologies including IEEE 802.1 TSN (for Ethernet LANs) and IETF DetNet (for wired IP networks). It is getting traction in various industries including manufacturing, online gaming, professional A/V, cellular radio and others, making possible many cost and performance optimizations. Reliable and Available Wireless (RAW) networking services extend DetNet to approach end-to-end deterministic performances in a network with scheduled wireless segments, possibly combined with wired segments, and possibly sharing physical resources with non-deterministic traffic. The wireless and wired media are fundamentally different at the physical level, and while the generic Problem Statement for DetNet applies to the wired as well as the wireless media, the methods to achieve RAW have to differ from those used to support time-sensitive networking over wires, as a RAW solution will need to address less consistent transmissions, energy conservation and shared spectrum efficiency. The development of RAW technologies has been lagging behind deterministic efforts for wired systems both at the IEEE and the IETF. But recent efforts at the IEEE and 3GPP indicate that wireless is finally catching up at the lower layer and that it is now possible for the IETF to extend DetNet for wireless segments that are capable of scheduled wireless transmissions. The intent for RAW is to provide DetNet elements that are specialized for short range radios. From this inheritance, RAW stays agnostic to the radio layer underneath though the capability to schedule transmissions is assumed. How the PHY is programmed to do so, and whether the radio is single-hop or meshed, are unknown at the IP layer and not part of the RAW abstraction. Still, in order to focus on real-worlds issues and assert the feasibility of the proposed capabilities, RAW will focus on selected technologies that can be scheduled at the lower layers: IEEE Std. 802.15.4 timeslotted channel hopping (TSCH), 3GPP 5G ultra-reliable low latency communications (URLLC), IEEE 802.11ax/be where 802.11be is extreme high throughput (EHT), and L-band Digital Aeronautical Communications System (LDACS) -see Note1-. The establishment of a path is not in-scope for RAW. It may be the product of a centralized Controller Plane as described for DetNet. As opposed to wired networks, the action of installing a path over a set of wireless links may be very slow relative to the speed at which the radio conditions vary, and it makes sense in the wireless case to provide redundant forwarding solutions along a complex path and to leave it to the RAW Network Plane to select which of those forwarding solutions are to be used for a given packet based on the current conditions. The path installed by the Controller Plane should provide a high degree of radio redundancy and diversity (DetNet PREOF, end-to-end network coding, and possibly radio-specific abstracted techniques such as ARQ, overhearing, frequency diversity, time-slotting, and possibly others). The goal of the RAW operation is to control redundant transmissions along a path at the forwarding timescale to maintain the expected service level while optimizing the usage of constrained resources such as energy and spectrum. The scope of the RAW WG comprises Network plane protocol elements such as OAM and in-band control to enable the RAW operation at the Service and at the forwarding sub-layers, e.g., controlling whether to use packet replication, Hybrid ARQ and coding, with a constraint to limit the use of redundancy when it is really needed, e.g., when a spike of loss is observed. RAW observes the path in quasi real-time. The WG will consider the applicability of existing tools -see Note2- such as L2-triggers, DLEP -see Note3-, BFD and in-band-OAM to observe the path, and BIER-TE and Segment Routing to control the use of the path on individual packets. RAW forwarding decisions may be made at the ingress and signaled in-band. Alternatively, they may be made at intermediate hops and depend on the state of the next hop and local policies, in which case a different in-band signaling may be needed. The group will produce the following deliverables -see Note2-: 1) An informational document describing deterministic wireless use cases, in continuation to the DetNet Use Cases document 2) An informational document describing the technologies that the group will cover (e.g., URLLC, TSCH, 802.11ax/be and possibly LDACS) 3) Produce a Standards Track document to enable operations, administration and maintenance (OAM) inside a RAW network, providing packet loss evaluation, self-testing and automated adaptation to enable trade-offs between resilience and energy consumption. Note1: The Working Group will leverage cross-participation with the associated set of stakeholders to ensure that the work taking place corresponds to real demands and that the proposed solutions are indeed applicable. Participants coming from the wireless industry are not expected to be familiar with the IETF nor interested with the current DetNet activities on pseudowires and MPLS. It makes sense to provide them with a separate WG were attendees can talk a same language with folks that share a common interest. Note2: A problem statement and one or more applicability statements will be produced that may or may not be suited for archiving, to be decided at a later time. Note3: As a technique to provide a radio-specific DetNet service and forwarding sub-layers, RAW appears to belong to the routing Area. Overlaps with MANET were identified (e.g., the use of DLEP), but as an approach towards Deterministic Networking, RAW is neither mobile nor ad-hoc, but pretty much the very opposite. Comments welcome as usual ! Pascal
- [Raw] RAW updated charter Pascal Thubert (pthubert)