Re: [trill] Alvaro Retana's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)

"Susan Hares" <shares@ndzh.com> Tue, 23 January 2018 22:40 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 989C712D86A; Tue, 23 Jan 2018 14:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k0QVoe9avlKg; Tue, 23 Jan 2018 14:40:06 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 470E712D84E; Tue, 23 Jan 2018 14:40:06 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=166.176.249.181;
From: "Susan Hares" <shares@ndzh.com>
To: "'Alvaro Retana'" <aretana.ietf@gmail.com>, "'The IESG'" <iesg@ietf.org>
Cc: <draft-ietf-trill-p2mp-bfd@ietf.org>, <trill-chairs@ietf.org>, <trill@ietf.org>
References: <151672235841.13930.4801042755640327832.idtracker@ietfa.amsl.com>
In-Reply-To: <151672235841.13930.4801042755640327832.idtracker@ietfa.amsl.com>
Date: Tue, 23 Jan 2018 17:40:02 -0500
Message-ID: <00d001d3949b$1c0074b0$54015e10$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQAzHUELBC6B9gGWJaHNwykFsvkjBKbC+3Kg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/gsvt07wufHBW7ppIzAcbszASxMQ>
Subject: Re: [trill] Alvaro Retana's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2018 22:40:08 -0000

Alvaro: 
Thank you for the feedback. 
Sue Hares

-----Original Message-----
From: Alvaro Retana [mailto:aretana.ietf@gmail.com] 
Sent: Tuesday, January 23, 2018 10:46 AM
To: The IESG
Cc: draft-ietf-trill-p2mp-bfd@ietf.org; Susan Hares; trill-chairs@ietf.org; trill@ietf.org
Subject: Alvaro Retana's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)

Alvaro Retana has entered the following ballot position for
draft-ietf-trill-p2mp-bfd-08: 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-trill-p2mp-bfd/



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

(1) The first reference to I-D.ietf-bfd-multipoint appears in Section 5; please add one in the Introduction when Multipoint BFD is initially mentioned.

(2) I think that using Normative Language (without quotation marks) to mention what is specified somewhere else can result in confusion as to which is the authoritative document.  This seems to be the case in Section 4: "If the M bit of the TRILL Header of the RBridge channel packet containing a BFD Control packet is non-zero, the packet MUST be dropped [RFC7175]."  The sentence sounds as if the behavior is specified in rfc7175, but that document says (in Section
3.2 (BFD Control Frame Processing)): "The following tests SHOULD be performed...Is the M bit in the TRILL Header non-zero?  If so, discard the frame."  Note that the behavior specified in rfc7175 doesn't use a "MUST".  The text in this document seems to be used to explain why a new message is needed, and not in a Normative way -- please clarify the text so that there is no inconsistency with respect to rfc7175.

(3) Section 5 says that the "processing in Section 3.2 of [RFC7175] applies...If the M bit is zero, the packet is discarded."  Section 3.2 has that "SHOULD" that I mentioned above, and it also mentions potential security issues, which are not referenced in this document.  Are there reasons to keep the "SHOULD" and not use "MUST" instead (for the p2mp case)?  If the same semantics as in rfc7175 are kept, then the Security Considerations should include the concerns.