[RTG-DIR]Rtgdir last call review of draft-ietf-ccamp-rfc9093-bis-11

Gyan Mishra via Datatracker <noreply@ietf.org> Mon, 02 September 2024 04:56 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rtg-dir@ietf.org
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from [10.244.2.118] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 04CC6C14F5E8; Sun, 1 Sep 2024 21:56:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gyan Mishra via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172525300265.981632.9152324606577036628@dt-datatracker-68b7b78cf9-q8rsp>
Date: Sun, 01 Sep 2024 21:56:42 -0700
Message-ID-Hash: L25RS5Q4Z6XKKQFSU3SRX7C5VZULOQUX
X-Message-ID-Hash: L25RS5Q4Z6XKKQFSU3SRX7C5VZULOQUX
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-dir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ccamp@ietf.org, draft-ietf-ccamp-rfc9093-bis.all@ietf.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Gyan Mishra <hayabusagsm@gmail.com>
Subject: [RTG-DIR]Rtgdir last call review of draft-ietf-ccamp-rfc9093-bis-11
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/U9G4pE1TPz_Dsmnpvzgf73B87HI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-dir-owner@ietf.org>
List-Post: <mailto:rtg-dir@ietf.org>
List-Subscribe: <mailto:rtg-dir-join@ietf.org>
List-Unsubscribe: <mailto:rtg-dir-leave@ietf.org>

Reviewer: Gyan Mishra
Review result: Ready

I have reviewed the latest version 11 of
the draft.  Many thanks to the authors in updating RFC 9193.

AFAIK I believe in this case a BIS to RFC 9193 was the correct path taken to
fix all the Layer 0 data types that were missing in RFC 9193. Nicely done and
very thorough work done by the authors and all contributors.

Major issues:
None

Minor issues:
None

Nits:
None