[MBONED]Gorry Fairhurst's No Objection on draft-ietf-mboned-amt-yang-07: (with COMMENT)

Gorry Fairhurst via Datatracker <noreply@ietf.org> Mon, 13 April 2026 10:03 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@mail2.ietf.org
Received: from [10.244.6.151] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 12639DB1D211; Mon, 13 Apr 2026 03:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776074639; bh=OHMkctqC+yuIWvGNWupC5xO2CxO0hRSTmMAwB+wi2CM=; h=From:To:Cc:Subject:Reply-To:Date; b=tRMwCsRaO86M+o4YIBWoTqlNSg2sTUL51TBFe7r3RZiBd358cStsUelR/alr/i3uV gQpqNJlvP1rXBbyiqz/iBPCIuS514WhZ4akgm4rfCYLCifrFjCwFtnr0sIE21SPo1u gUufnKpspKHvCcCNjRqhOy23VycHcel4hJ1XzyS8=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gorry Fairhurst via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177607463884.633274.8474400129026397069@dt-datatracker-647897bf7-7f2k5>
Date: Mon, 13 Apr 2026 03:03:59 -0700
Message-ID-Hash: XBPNIH6Z6RFIODIE4RBMZ3IA5OZQ24UO
X-Message-ID-Hash: XBPNIH6Z6RFIODIE4RBMZ3IA5OZQ24UO
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mboned.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: austin.mantz@hpe.com, draft-ietf-mboned-amt-yang@ietf.org, mboned-chairs@ietf.org, mboned@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: [MBONED]Gorry Fairhurst's No Objection on draft-ietf-mboned-amt-yang-07: (with COMMENT)
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/xkyzlapdi9WZGlw6M5-hUTHGluE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Owner: <mailto:mboned-owner@ietf.org>
List-Post: <mailto:mboned@ietf.org>
List-Subscribe: <mailto:mboned-join@ietf.org>
List-Unsubscribe: <mailto:mboned-leave@ietf.org>

Gorry Fairhurst has entered the following ballot position for
draft-ietf-mboned-amt-yang-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-amt-yang/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for the work done in this document, I enjoted reading this. I have
reviwed previous AMT documents, but do not see specific transport topics in
this document. There were, however,  a few places where terminolog is defined,
but could be more consistently applied.

NiTs:
/a AMT Relay/ perhaps ought to be /an AMT Relay/
/AMT relay/AMT Relay/ - in various places, since "Relay" is already capitalised
without AMT? /AMT gateway/AMT Gateway/ - for consistency in text and the
comments? /Support of relay or gateway is indicated/Support of an AMT Relay or
an AMT Gateway is indicated/ /relay discovery message/Relay Discovery message/
- as per RFC7450. /relay discovery address/Relay Discovery Address/ - as per
RFC7450. /relay address/Relay Address/ - as per RFC7450.

Regards,

Gorry