[6tisch] Barry Leiba's No Objection on draft-ietf-6tisch-msf-12: (with COMMENT)

Barry Leiba via Datatracker <noreply@ietf.org> Thu, 12 March 2020 02:07 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: 6tisch@ietf.org
Delivered-To: 6tisch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B7C6C3A113C; Wed, 11 Mar 2020 19:07:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-6tisch-msf@ietf.org, 6tisch-chairs@ietf.org, 6tisch@ietf.org, Pascal Thubert <pthubert@cisco.com>, pthubert@cisco.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <158397886725.19691.18438195402571370937@ietfa.amsl.com>
Date: Wed, 11 Mar 2020 19:07:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/AzHYGRVX647TE5yNlTSzSVhR0fY>
Subject: [6tisch] Barry Leiba's No Objection on draft-ietf-6tisch-msf-12: (with COMMENT)
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2020 02:07:48 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-6tisch-msf-12: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-6tisch-msf/



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

I was going to ask that you expand “DODAG” in first use, because it’s not
marked as sufficiently common in the RFC Editor’s abbreviation list.  But,
really, I think the better answer is to ask the responsible AD to ask the RFC
Editor to put that asterisk on both DAG and DODAG at this point.