Re: [Raw] New Version Notification for draft-pthubert-raw-architecture-07.txt

Fabrice Theoleyre <theoleyre@unistra.fr> Mon, 07 June 2021 15:19 UTC

Return-Path: <theoleyre@unistra.fr>
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 4DBDB3A1A86 for <raw@ietfa.amsl.com>; Mon, 7 Jun 2021 08:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=unistra.fr
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 R7vmHNycosio for <raw@ietfa.amsl.com>; Mon, 7 Jun 2021 08:19:24 -0700 (PDT)
Received: from smtpout01-ext1.partage.renater.fr (smtpout01-ext1.partage.renater.fr [194.254.240.32]) by ietfa.amsl.com (Postfix) with ESMTP id 5386B3A1A10 for <raw@ietf.org>; Mon, 7 Jun 2021 08:19:24 -0700 (PDT)
Received: from zmtaauth01.partage.renater.fr (zmtaauth01.partage.renater.fr [194.254.240.25]) by smtpout10.partage.renater.fr (Postfix) with ESMTP id 314A7612C9; Mon, 7 Jun 2021 17:19:16 +0200 (CEST)
Received: from zmtaauth01.partage.renater.fr (localhost [127.0.0.1]) by zmtaauth01.partage.renater.fr (Postfix) with ESMTPS id 1C49A14065A; Mon, 7 Jun 2021 17:19:16 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zmtaauth01.partage.renater.fr (Postfix) with ESMTP id 08B7414065B; Mon, 7 Jun 2021 17:19:16 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.10.3 zmtaauth01.partage.renater.fr 08B7414065B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unistra.fr; s=CF279DD4-6F58-4C59-BB33-73FDC6DFC1E3; t=1623079156; bh=joHEvHuvvRkhvJHg3zItkWzTiKllyvjgG9s/Pamv7S0=; h=Mime-Version:From:Date:Message-Id:To; b=jAUh0Wv5/dN0OIcYsge5EKi4CBjFwVqZ0g+ingKkGxxOvavBLs98MCqag7LkAypR+ awkTRGXmVHX6QSeJCLFMpOayvoxLOjCPZs272XR9Ou+7RI9ZqaXZh9DSW08/MZ9O8w dCh1flbW+tnL6hXpPGGwm85+86wvgBDYHKJkRXc5RL8fg0FOG1bDz8U8gJuPELek6F bvrhiIftKajJ/KYgvNrYkwG2TCRAsTfAicQxRAa2BreTbJx10XZ4jpATZIVkg8m9IW N3VrVpHd5in2bOOLq2cDzlks/L570Di/MA0rTh6+mwTDh7HVjuup232wuJMMZeAS6l mtrQ07RrTz8bw==
X-Virus-Scanned: amavisd-new at zmtaauth01.partage.renater.fr
Received: from zmtaauth01.partage.renater.fr ([127.0.0.1]) by localhost (zmtaauth01.partage.renater.fr [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id MWzSAo6CK9I5; Mon, 7 Jun 2021 17:19:15 +0200 (CEST)
Received: from [192.168.1.203] (unknown [194.254.241.251]) by zmtaauth01.partage.renater.fr (Postfix) with ESMTPA id 85EF014065A; Mon, 7 Jun 2021 17:19:15 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Fabrice Theoleyre <theoleyre@unistra.fr>
In-Reply-To: <CO1PR11MB488138E10B33B92577BAEFF6D83B9@CO1PR11MB4881.namprd11.prod.outlook.com>
Date: Mon, 07 Jun 2021 17:19:15 +0200
Cc: Greg Mirsky <gregory.mirsky@ztetx.com>, "raw@ietf.org" <raw@ietf.org>, "gpapadopoulos.ietf@gmail.com" <gpapadopoulos.ietf@gmail.com>, "xvilajosana@uoc.edu" <xvilajosana@uoc.edu>, "Carlos J. Bernardos" <cjbc@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
Message-Id: <54AE436C-8EF9-4E15-88D9-F335FD3E8B13@unistra.fr>
References: <162281386516.32559.11779939327351153244@ietfa.amsl.com> <CO1PR11MB488138E10B33B92577BAEFF6D83B9@CO1PR11MB4881.namprd11.prod.outlook.com>
To: Pascal Thubert <pthubert@cisco.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-Renater-Ptge-SpamState: clean
X-Renater-Ptge-SpamScore: -100
X-Renater-Ptge-SpamCause: gggruggvucftvghtrhhoucdtuddrgeduledrfedtjedgkeeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecutffgpfetvffgtfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomhephfgrsghrihgtvgcuvfhhvgholhgvhihrvgcuoehthhgvohhlvgihrhgvsehunhhishhtrhgrrdhfrheqnecuggftrfgrthhtvghrnhepueevtdeuvedtueeuhfffveeuueeggeevffeileeugeektdfgheevgeeuledvhfefnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepudelgedrvdehgedrvdeguddrvdehudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduleegrddvheegrddvgedurddvhedupdhhvghloheplgduledvrdduieekrddurddvtdefngdpmhgrihhlfhhrohhmpefhrggsrhhitggvucfvhhgvohhlvgihrhgvuceothhhvgholhgvhihrvgesuhhnihhsthhrrgdrfhhrqedprhgtphhtthhopehpthhhuhgsvghrthestghishgtohdrtghomhdprhgtphhtthhopehgrhgvghhorhihrdhmihhrshhkhiesiihtvghtgidrtghomhdprhgtphhtthhopehrrgifsehivghtfhdrohhrghdprhgtphhtthhopehgphgrphgrughophhouhhlohhsrdhivghtfhesghhmrghilhdrtghomhdprhgtphhtthhopeigvhhilhgrjhhoshgr nhgrsehuohgtrdgvughupdhrtghpthhtoheptghjsggtsehithdruhgtfehmrdgvsh
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/lZ3Z4zF-5Ng4su1eCieyvxZLbKw>
Subject: Re: [Raw] New Version Notification for draft-pthubert-raw-architecture-07.txt
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: Mon, 07 Jun 2021 15:19:38 -0000

Hi Pascal,

I just read your draft. 

For the ingress / egress end-systems in section 4.3, shouldn’t you use the term MEP? 
Besides, I have the feeling that MEP should be the hosts at the border of the wireless part: in that way, you focus uniquely on the wireless links to collect all the measurements, etc.
It would be easier to manage. 

What’s your opinion?

Fabrice 






> Le 4 juin 2021 à 15:49, Pascal Thubert (pthubert) <pthubert@cisco.com> a écrit :
> 
> Many thanks for your comments Greg!
> 
> I added subsections to section 4.3 of draft-pthubert-raw-architecture 07; can you please have a look?
> 
> Coincidently the new text affects the (todo) section 4.3 of draft-ietf-raw-oam-support.
> 
> Fabrice and all, it would be nice that we sync on this. We might also exchange pieces of text between the 2 drafts.
> 
> Keep safe;
> 
> Pascal
> 
> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
> Sent: vendredi 4 juin 2021 15:38
> To: Georgios Z. Papadopoulos <georgios.papadopoulos@imt-atlantique.fr>; Georgios Papadopoulos <georgios.papadopoulos@imt-atlantique.fr>; Lou Berger <lberger@labn.net>; Pascal Thubert (pthubert) <pthubert@cisco.com>; Rex Buddenberg <buddenbergr@gmail.com>
> Subject: New Version Notification for draft-pthubert-raw-architecture-07.txt
> 
> 
> A new version of I-D, draft-pthubert-raw-architecture-07.txt
> has been successfully submitted by Pascal Thubert and posted to the IETF repository.
> 
> Name:		draft-pthubert-raw-architecture
> Revision:	07
> Title:		Reliable and Available Wireless Architecture/Framework
> Document date:	2021-06-04
> Group:		Individual Submission
> Pages:		35
> URL:            https://www.ietf.org/archive/id/draft-pthubert-raw-architecture-07.txt
> Status:         https://datatracker.ietf.org/doc/draft-pthubert-raw-architecture/
> Html:           https://www.ietf.org/archive/id/draft-pthubert-raw-architecture-07.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-pthubert-raw-architecture
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-pthubert-raw-architecture-07
> 
> Abstract:
>   Reliable and Available Wireless (RAW) provides for high reliability
>   and availability for IP connectivity over a wireless medium.  The
>   wireless medium presents significant challenges to achieve
>   deterministic properties such as low packet error rate, bounded
>   consecutive losses, and bounded latency.  This document defines the
>   RAW Architecture.  It builds on the DetNet Architecture and discusses
>   specific challenges and technology considerations needed to deliver
>   DetNet service utilizing scheduled wireless segments and other media,
>   e.g., frequency/time-sharing physical media resources with stochastic
>   traffic.
> 
> 
> 
> 
> The IETF Secretariat
> 
>