Re: [Raw] Intdir telechat review of draft-ietf-raw-use-cases-08

CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> Tue, 29 November 2022 19:34 UTC

Return-Path: <cjbc@it.uc3m.es>
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 4734BC152584 for <raw@ietfa.amsl.com>; Tue, 29 Nov 2022 11:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.996
X-Spam-Level:
X-Spam-Status: No, score=-6.996 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, 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 e9_LNvgNqpjw for <raw@ietfa.amsl.com>; Tue, 29 Nov 2022 11:33:56 -0800 (PST)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 6B85BC14F746 for <raw@ietf.org>; Tue, 29 Nov 2022 11:33:56 -0800 (PST)
Received: by mail-lj1-x232.google.com with SMTP id n1so13767791ljg.3 for <raw@ietf.org>; Tue, 29 Nov 2022 11:33:56 -0800 (PST)
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:message-id:reply-to; bh=3SgXfZJPWgLIM/PPI5dO9X/zGtTQZtDPOmg0F04Mm20=; b=QLVhIv/mcgMacDZPQVd/E6KPjkqtte09d4gcWncKqkD9PM+/TxDfHWs1vT/D393ILN VjY0h4lPbhvhhyNU0bGwIHWJ/HnhpFirix1VUQz6FTvThZhjTOg2+NeW5ApAVOc9yQES ileNzfWvuvx6H9sfLTxiNN1vYy+YYp7aSg2fG8pjHD5feYPphyvaS6DtzfWIYoyYvK7A 8doz8UmPwuJTGhiViM0VRszQutk6PL9PbtoJjhH9TyVVviBIc4ez7GTGhW0wdWalWHlK L28eCeFiigLz1pQww7XgBMXvvrtYOLAIbee9caGbSSdMij3E/xXu9WwtNguqJS5sNw43 4+bA==
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:message-id :reply-to; bh=3SgXfZJPWgLIM/PPI5dO9X/zGtTQZtDPOmg0F04Mm20=; b=7yBDijXvHGIcsHp4mKOaPfW+VHYM6iA42226sZ3cOUOdlnZ32oRpgEOCtYo9lKopDQ rDQNMHCzj9fgjkJs3mU69aWgeH8a5G2bjbAaNA/UULDlyIzLMjB+99OySKYMFoy6bfMI ZkhAaaEmtQuAFXP+F4ElcTmiCy9NDEi4GYTcVR13EEJg79+tGikXDpGrnj0Z76HVSVcJ 6TT9kfPXYGRNk02XzUdJh+4nRl9Yp+/T2JIF2DFRi92Lif6v716cjDJjOspHSZMBeOMk 5BmrHWVZ4vupL9u2GyvNpZzO6QiEV3OQslJUeklThyQ/NLrdY6CDB1xr+CgB2fjOPTar r9pw==
X-Gm-Message-State: ANoB5pmYbH+FWsgfM/9BP/9Q4PYXD+9ONqHqay9phHDckbtdORk66JYJ 2yHQ7xkAiJwOES+1qbDgml0kmJmmUvdUPOVilLdUudPVUUk=
X-Google-Smtp-Source: AA0mqf4mJwKK64Tr4LBTdPSzkZoe2kz0R3+sOAa0kJyOjhe5uXCoZeu3qxOVfI0tRg9k7zPmp3q3oVqMLhgZwAgXFkY=
X-Received: by 2002:a2e:3211:0:b0:279:7e51:a1ad with SMTP id y17-20020a2e3211000000b002797e51a1admr9461133ljy.65.1669750434209; Tue, 29 Nov 2022 11:33:54 -0800 (PST)
MIME-Version: 1.0
References: <166969633175.1497.7774961298697616216@ietfa.amsl.com>
In-Reply-To: <166969633175.1497.7774961298697616216@ietfa.amsl.com>
From: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Date: Tue, 29 Nov 2022 20:33:38 +0100
Message-ID: <CALypLp_6QY3VVeCeuHBPr6drP-adEdCoP4QyFkXJYALS8XcqWw@mail.gmail.com>
To: Suresh Krishnan <sureshk@cisco.com>
Cc: int-dir@ietf.org, draft-ietf-raw-use-cases.all@ietf.org, last-call@ietf.org, raw@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007f1f4605eea111b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/6YivE9dCpJq0EpQdmTgPTE-W0nE>
Subject: Re: [Raw] Intdir telechat review of draft-ietf-raw-use-cases-08
X-BeenThere: raw@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 29 Nov 2022 19:34:00 -0000

Hi Suresh,

Thanks a lot for your review. Please, see inline below some responses from
our side.

On Tue, Nov 29, 2022 at 5:32 AM Suresh Krishnan via Datatracker <
noreply@ietf.org> wrote:

> Reviewer: Suresh Krishnan
> Review result: Ready with Issues
>
> Reviewer: Suresh Krishnan
> Review result: Ready with Nits
>
> I am an assigned INT directorate reviewer for draft-ietf-raw-use-cases.
> These comments were written primarily for the benefit of the Internet Area
> Directors. Document editors and shepherd(s) should treat these comments
> just
> like they would treat comments from any other IETF contributors and resolve
> them along with any other Last Call comments that have been received. For
> more
> details on the INT Directorate, see
> https://datatracker.ietf.org/group/intdir/about/.
>
>
> Based on my review, if I was on the IESG I would ballot a NO OBJECTION on
> this
> document. The document is well written and easy to understand. There are a
> few
> minor issues I found that you may wish to address.
>
> Minor issues:
>
> * Section 1
>
> The following text looks a bit out of date since 5G has already been
> deployed for
> quite some time.
>
> "*  IMT-2020 has recognized Ultra-Reliable Low-Latency Communication
>     (URLLC) as a key functionality for the upcoming 5G."
>
> It probably needs to be rewritten.
>

[Carlos] Yes, thanks for pointing this out. We will rewrite this in the
next revision of the draft.


>
> * Section 2
>
> I know the developments are fairly new but have you considered how LEO
> satellite technology affects this area?
>
> [Carlos] Good point. I will ask the experts in the aeronautical area in
the WG to propose a way to address this comment.


> * Section 4.3
>
> Would it be useful to refer to RFC9030 in addition to RFC7554 to point
> to related IETF work?
>

[Carlos] Yes, thanks. We'll add this reference.

Thanks!

Carlos