Re: [pim] Last Call: <draft-ietf-pim-msdp-yang-08.txt> (A YANG DataModel for Multicast Source Discovery Protocol (MSDP)) to Proposed Standard

<> Thu, 23 January 2020 08:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 11C501201B7; Thu, 23 Jan 2020 00:00:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iSj1pm1E8fdf; Thu, 23 Jan 2020 00:00:46 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E24D0120111; Thu, 23 Jan 2020 00:00:45 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTPS id C1849834CDD93181D796; Thu, 23 Jan 2020 16:00:43 +0800 (CST)
Received: from ([]) by with SMTP id 00N80Jfa060619; Thu, 23 Jan 2020 16:00:20 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp04[null]) by mapi (Zmail) with MAPI id mid203; Thu, 23 Jan 2020 16:00:19 +0800 (CST)
Date: Thu, 23 Jan 2020 16:00:19 +0800
X-Zmail-TransId: 2afc5e2952935e5173ee
X-Mailer: Zmail v1.0
Message-ID: <>
In-Reply-To: <>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: 00N80Jfa060619
Archived-At: <>
Subject: Re: [pim] Last Call: <draft-ietf-pim-msdp-yang-08.txt> (A YANG DataModel for Multicast Source Discovery Protocol (MSDP)) to Proposed Standard
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Jan 2020 08:00:49 -0000

Hi Tom,

Thank you very much for your review!

I updated the draft to 11 version. 

About the RFC number, I'll update the draft when I get the number. :-)




发件人:tompetch <>
收件人:IETF-Announce <>; <>;
抄送人 <>; <>; <>;
日 期 :2020年01月23日 00:21
主 题 :Re: [pim] Last Call: <draft-ietf-pim-msdp-yang-08.txt> (A YANG DataModel for Multicast Source Discovery Protocol (MSDP)) to Proposed Standard

RFC8349 says that a new identity MUST be defined for a new control plane protocol - I see no such definition here

RFC8349 says that augments should be to control-plane-protocols/control-plane-protocol as is seen in the OSPF and the other LSR YANG modules; here I see an augment to control-plane-protocols which seems wrong to me

many features but no idea where to look them up - I think every YANG feature needs a YANG reference to an I-D/RFC

I find a list of features and references in the body of an I-D valuable

YANG modules must be plain text; [3618] in the module description does not look like plain text. Other references e.g. RFC8177 look ok although some have a space in them and some do not

leaf tcp-connection-source says that ipv4 must be enabled but the when statement does not test for enabled, just for configured

rpc clear peer clears everything if there is no address - this is fail danger, a specific value for clear all would IMHO be better engineering

XXXX is likely to mean this I-D/RFC but I always like to see a specific direction to the RFC Editor to that effect, just the once, somewhere near the front.

In the same vein, a direction to replace the dates with date of publication  would not go amiss

Tom Petch
From: IETF-Announce <> on behalf of The IESG <>
Sent: 15 January 2020 20:29
To: IETF-Announce
Subject: Last Call: <draft-ietf-pim-msdp-yang-08.txt> (A YANG Data Model for Multicast Source Discovery Protocol (MSDP)) to Proposed Standard

The IESG has received a request from the Protocols for IP Multicast WG (pim)
to consider the following document: - 'A YANG Data Model for Multicast Source
Discovery Protocol (MSDP)'
  <draft-ietf-pim-msdp-yang-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the mailing lists by 2020-01-30. Exceptionally, comments may
be sent to instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.


   This document defines a YANG data model for the configuration and
   management of Multicast Source Discovery Protocol (MSDP) Protocol.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

IETF-Announce mailing list

pim mailing list