[MBONED]Re: Christopher Inacio's Discuss on draft-ietf-mboned-amt-yang-08: (with DISCUSS and COMMENT)
linchangwang <linchangwang.04414@h3c.com> Wed, 15 April 2026 07:11 UTC
Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: mboned@mail2.ietf.org
Delivered-To: mboned@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id DA65ADC8F813; Wed, 15 Apr 2026 00:11:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776237111; bh=2WEhLFifArc6ZbxR7U8+wT5M8CdymQqjdao/fxynYGM=; h=From:To:CC:Subject:Date; b=jtJ+frMA6aQRyXGULWzLFkZofHr8/BkPpvQxplHnUqVGZZvCnnessN6+Rpau4QYUh R4KW8J7gX4l1OpbaeAGnRRacJdWHd1BNHZI0l2AeAHDEXno1OD6Tndx0Bel9feBJCM FKPemCZbybV8Mr8/KPJkx+szxgQt1mOpNLDxnl00=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=h3c.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5IZcNXa5VLfk; Wed, 15 Apr 2026 00:11:48 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 604ECDC8F57F; Wed, 15 Apr 2026 00:10:10 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 63F79fUo025892; Wed, 15 Apr 2026 15:09:41 +0800 (+08) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX13-BJD.srv.huawei-3com.com (unknown [10.153.34.15]) by mail.maildlp.com (Postfix) with ESMTP id A5C6822F9572; Wed, 15 Apr 2026 15:21:05 +0800 (CST)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) by DAG6EX13-BJD.srv.huawei-3com.com (10.153.34.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Wed, 15 Apr 2026 15:09:41 +0800
Received: from DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738]) by DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738%17]) with mapi id 15.02.1258.027; Wed, 15 Apr 2026 15:09:41 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Christopher Inacio <stndrds-inacio@andrew.cmu.edu>, The IESG <iesg@ietf.org>
Thread-Topic: Christopher Inacio's Discuss on draft-ietf-mboned-amt-yang-08: (with DISCUSS and COMMENT)
Thread-Index: AdzMpsQNYfXhqBoHLUK7URFLoSOw+Q==
Date: Wed, 15 Apr 2026 07:09:41 +0000
Message-ID: <a5b7ca066836421d89d61a5166ff821c@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.142.193.222]
x-sender-location: DAG2
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 63F79fUo025892
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=h3c.com; s=default; t=1776236992; bh=2WEhLFifArc6ZbxR7U8+wT5M8CdymQqjdao/fxynYGM=; h=From:To:CC:Subject:Date; b=mqpD+Ia/y0CnPLTRkVNJjY3sP9LvFvZSp/k5rgJYYXQG3360oyTqliJA292L9DUkS 6JNDVGog1zhLRIfTDnf98DNSEETM3MbVI+XkqpSERR0AQhM1psLMsts4ZBOC7hscbz lRo/Ug23cpDeJkbM5Y87Wcytb/DQGWVqLIF41rzmv8Bk+QydYp1+W4ychbFnPHK350 KIt4hJHFMB+Wi1QA3GmXIH1sB/wPgcniMSPbN2oXIEgY04AS1oajyv+dg6B/2zVM/t qY4CFDMZi8ykHt3CAf43HocZwG/cGwaBwwYyEHgW9xGvyjI6sasmgb3FxyEn9hZfKL nhHkTTVLs6C4A==
Message-ID-Hash: Q52BDEUQTN2TSDFJNZY3HMXJZNZCCRDF
X-Message-ID-Hash: Q52BDEUQTN2TSDFJNZY3HMXJZNZCCRDF
X-MailFrom: linchangwang.04414@h3c.com
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" <austin.mantz@hpe.com>, "draft-ietf-mboned-amt-yang@ietf.org" <draft-ietf-mboned-amt-yang@ietf.org>, "mboned-chairs@ietf.org" <mboned-chairs@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [MBONED]Re: Christopher Inacio's Discuss on draft-ietf-mboned-amt-yang-08: (with DISCUSS and COMMENT)
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/5AC0_LSjuqHsWA2rtWPPaXNHQWk>
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>
Hi Christopher Inacio, Thank you for your comments. Detailed replies are provided below in [Changwang]. Thanks, Changwang 发件人: Christopher Inacio via Datatracker <noreply@ietf.org> 发送时间: 2026年4月15日 9:17 收件人: The IESG <iesg@ietf.org> 抄送: austin.mantz@hpe.com; draft-ietf-mboned-amt-yang@ietf.org; mboned-chairs@ietf.org; mboned@ietf.org 主题: Christopher Inacio's Discuss on draft-ietf-mboned-amt-yang-08: (with DISCUSS and COMMENT) Christopher Inacio has entered the following ballot position for draft-ietf-mboned-amt-yang-08: Discuss 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/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Overall, the draft is well written and quite clear, I appreciate the effort that went into the drafting of this. While I have 3 bullet points in here, this is really centered on one particular topic: How to understand the "MUST"s in the Operational Considerations section. * In this section, the ‘MUST’ is a requirement of operations? People ‘MUST’ do that? (Like people ‘MUST NOT’ share their passwords?). Also, wouldn’t the tunnel just fail if there are protocol mismatches? > 1367 5. Operational Considerations > > 1369 This document specifies a YANG data model for AMT that configures and > 1370 monitors address parameters for both Relay and Gateway functions. > 1371 Operators MUST monitor for address family mismatches between > 1372 associated address parameters to ensure correct protocol operation, > 1373 tunnel establishment, and forwarding behavior. * The “MUST”s in the Operatonal Considerations section are not present in RFC7450, the protocol specification. [Changwang] The operational considerations here are those that apply for the use of this model. Otherwise, pointing to existing provisions in the base spec (if any) would suffice. That effectively moves things where I would normal expect protocol negotiation errors into configuration checks. Further, it appears that many of the checks for this are reliant on human checking the configuration. Is that correct? I’m not clear on how to apply “MUST”s in a situation like this. [Changwang] Automated means can be used to monitor, detect, and even trigger corrective actions. The draft includes " It is RECOMMENDED that operators implement automated configuration validation tools to detect such address family mismatches. " * Why is this in the operations section? Isn’t this an implementation requirement? > 1412 Upon detecting an address family mismatch, the device MUST log an > 1413 appropriate error or alarm and prevent the inconsistent configuration > 1414 from being applied. Corrective actions include reconfiguring the > 1415 affected addresses to match the intended address family and verifying > 1416 routing reachability for the configured addresses. [Changwang] This is an important operational considerations per the guidance in https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-rfc5706bis-04#section-5. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks to the reviewers, Mike O., Behcet S., Robert W. (first time I read a YANG reviewer's review, actually,) for their insight. ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出的个人或群组。 禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。 如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件! This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
- [MBONED]Christopher Inacio's Discuss on draft-iet… Christopher Inacio via Datatracker
- [MBONED]Re: Christopher Inacio's Discuss on draft… linchangwang
- [MBONED]Re: Christopher Inacio's Discuss on draft… linchangwang
- [MBONED]Re: Christopher Inacio's Discuss on draft… stndrds-inacio stndrds-inacio