Re: [Last-Call] RtgDir Last Call review: draft-ietf-raw-use-cases-05
CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> Wed, 07 September 2022 10:28 UTC
Return-Path: <cjbc@it.uc3m.es>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D969AC152702 for <last-call@ietfa.amsl.com>; Wed, 7 Sep 2022 03:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.005
X-Spam-Level:
X-Spam-Status: No, score=-7.005 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it.uc3m.es
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s4oibshHSrTy for <last-call@ietfa.amsl.com>; Wed, 7 Sep 2022 03:28:07 -0700 (PDT)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FCEBC152707 for <last-call@ietf.org>; Wed, 7 Sep 2022 03:28:06 -0700 (PDT)
Received: by mail-wr1-x42f.google.com with SMTP id e16so375026wrx.7 for <last-call@ietf.org>; Wed, 07 Sep 2022 03:28:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it.uc3m.es; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=fSwsNH2uUsf3rlfEatj0vGocOsKA3k2E68NyM2G/MuU=; b=BJhp/kqptE0VN8fHienPTRtoJ1YcdPLSsBBlLaMc4+XHdRNQOKmPjP/Po3uKSfCEzQ As6jKd7d/76jj2cYX8b/xekrCCCq36Cwf7hthWXxOyUoA1eS1Pm+dV6Z8gMZ+iT388KO 0vPF5mwk3QMy33E1iSSeVwQ29lPV71xPb61iSriYpHWW9NqSQmJSYbJziZ54zYSHq1Dm 5sWlfiKKFXRx5tN3CDA53vdPwG1x6tQndZDu90EgHxO0XALUpugxLD6suto1FWoxd588 6zk6yBirLGF+pXoK2oAtFZNoaxM0Ov7carAa8dldcqTFRXoPNzu2yDRFYl9eAGk5Tp8s xSog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=fSwsNH2uUsf3rlfEatj0vGocOsKA3k2E68NyM2G/MuU=; b=HuP6m0U6Toi+6vPKiPCA+/9VUZoHlVX0rU/uYSzOx8BrgKVPvSwfoZJZaRCZuEQZ2k cqtgVwKASUcWUWkmsvOcALJe1hIQeIgScYrZ3GtWDjitGmyVgEZMXKGhXz7dycCRhGjJ 9L4xRluQEgMccOc/kzJ87A+T2rGFmRMYoWAKB4JP8kDqJOoTS6BdEgwhP655OiEa/v2x D70pGE3wVngfuIh7pk6y/wPF4CLX6RvJRouBtSMHOuYVpmq2vK4ythGweOKsDDgI1YLx Mw+vyo2tnr8teHPH/tVJf3ZYJyMDVcQRBUe7IY3+JgYiv8U9d4LgpbfylxWVVDZnQgje ilwQ==
X-Gm-Message-State: ACgBeo2ylhQymCm299t3kny5k3QbtGMZIT6S8UroviKm6Y5ydBaXY9Gm bivLsuBmAW4njENI9MdihcFMvkX7SqLDGGnDQwU2HTmdk3o=
X-Google-Smtp-Source: AA6agR6pJHMxNdL7ZvV5mqMPt8BvXpk1dt4fkEJ3cfLznz4nQiwxtPOIZL/rveNzzJOKMMK6Gy1KY8TKM2IdiWa+CmY=
X-Received: by 2002:adf:e601:0:b0:228:60f6:2512 with SMTP id p1-20020adfe601000000b0022860f62512mr1711312wrm.334.1662546484097; Wed, 07 Sep 2022 03:28:04 -0700 (PDT)
MIME-Version: 1.0
References: <CA+fLEh+haDodDnwOTL+_AQw79fctDBQCF3HaAfx+yBnuQ8KgRg@mail.gmail.com>
In-Reply-To: <CA+fLEh+haDodDnwOTL+_AQw79fctDBQCF3HaAfx+yBnuQ8KgRg@mail.gmail.com>
From: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Date: Wed, 07 Sep 2022 12:27:48 +0200
Message-ID: <CALypLp9wXFKReYbKBr0JPm-R9Y=Op7723200qzyKOE89xSLs4w@mail.gmail.com>
To: Victoria Pritchard <pritchardv0@gmail.com>
Cc: rtg-dir@ietf.org, last-call@ietf.org, draft-ietf-raw-use-cases.all@ietf.org, raw@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009b8b9105e813c4ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/kdTsM2P3E2X6mmDPFJFcQIMUmBU>
Subject: Re: [Last-Call] RtgDir Last Call review: draft-ietf-raw-use-cases-05
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2022 10:28:10 -0000
Dear Victoria, Thanks a lot for your review and comments. Please see inline below. On Thu, Sep 1, 2022 at 7:25 PM Victoria Pritchard <pritchardv0@gmail.com> wrote: > Hello, > > I have been selected as the Routing Directorate reviewer for this draft. > The Routing Directorate seeks to review all routing or routing-related > drafts as they pass through IETF last call and IESG review, and sometimes > on special request. The purpose of the review is to provide assistance to > the Routing ADs. For more information about the Routing Directorate, please > see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir > > Although these comments are primarily for the use of the Routing ADs, it > would be helpful if you could consider them along with any other IETF Last > Call comments that you receive, and strive to resolve them through > discussion or by updating the draft. > > Document: draft-ietf-raw-use-cases-05 > Reviewer: Victoria Pritchard > Review Date: 01/09/2022 > Intended Status: Informational > > Summary: > > This document is basically ready for publication but has nits that > should be considered prior to publication. > > Comments: > > This is an interesting and informative draft, clearly identifying use > cases and the reliability, availability and latency characteristics which > are important to them. > > Major Issues: > > No major issues found. > > Minor Issues: > > No minor issues found. > > Nits: > > Introduction > - "by leveraging on lower (L2 and below) capabilities" -> "by leveraging > lower layer (Layer 2 and below) capabilities"? > [Carlos] OK, thanks, changed! > - " (RAW) is an effort to provide Deterministic > Networking Mechanisms on across a multi-hop path that includes a" - > dont need both 'on' and 'across' > [Carlos] OK, thanks, fixed! > > No terminology / acronyms / abbreviations section - most are actually > expanded inside the draft or are very well known but a few I did not > understand, e.g.: > - APT/TMA TMA/ENR ENR/ORP in figure 1 > - FRE in section 6.4 > > [Carlos] Thanks, we have clarified/expanded these terms. We might add a terminology section as well. > Figure 1 > - transceiver appears twice at the bottom left - is one instance meant to > be for LDACS GS on the right hand side of the figure? > [Carlos] I think it is meant to be for the "Airport based", but I'll check with the LDACS experts. > > 2 > - "while during > en-route" --> "during flight" / "while en-route" - don't need both. > [Carlos] Thanks, fixed! > 2.5.1 > - "what it is important is to keep " - "what is important is to keep" > [Carlos] Thanks, fixed! > > 3.1, 4.1, 5.1, etc. the sub-heading title > - capital letters needed for "use-case". Should section 2.1 also be > "Use-Case Description"? > [Carlos] Thanks, fixed! Not sure if the capitalization is correct (this would be fixed by the RFC Editor anyway). I've used "Use-Case" for the time being, as I agree it's important to be consistent in the titles and headings. > > 4.4 > - teh -> the > [Carlos] Thanks, fixed! > > 5.1 > - Blue-Ray -> Blu-ray > [Carlos] Thanks, fixed! > > 6.4 > - "Note thought," -> "Note though," > [Carlos] Thanks, fixed! > - "Dual/multiple link" - the sentence after this is hard to read, does it > mean "due to the competitions, interference is common"? Or "due to the fact > that competitions and interference are common"? > [Carlos] The second one, thanks, fixed! > > 7.1 "other time of vehicles" -> "other types of vehicles"? > [Carlos] Thanks, fixed! > > 8.1 "the use of multiples robots" -> "the use of multiple robots" > [Carlos] Thanks, fixed! > > 10 - "Future revisions of this document will include > specific text devoted to highlight this non-latency critical > requirements." > This seems to have already been added as a sub-section for all use cases. > [Carlos] True, thanks! All changes are incorporated in the pre -06 version. We will post a new version once we get all the comments from the directorates and IESG review. Thanks a lot! Carlos
- [Last-Call] RtgDir Last Call review: draft-ietf-r… Victoria Pritchard
- Re: [Last-Call] RtgDir Last Call review: draft-ie… CARLOS JESUS BERNARDOS CANO