[Isis-wg] AD review of draft-ietf-isis-pcr-03

Alia Atlas <akatlas@gmail.com> Mon, 07 December 2015 20:04 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C37F91A86E0; Mon, 7 Dec 2015 12:04:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 AWqClc2_sCQn; Mon, 7 Dec 2015 12:04:13 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (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 B4CCC1A854D; Mon, 7 Dec 2015 12:04:13 -0800 (PST)
Received: by obbww6 with SMTP id ww6so122119246obb.0; Mon, 07 Dec 2015 12:04:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=CvqvzFTIfUD3s00MDf9gR/5/1iTOdux/h8ggWrTul2k=; b=j/p9WF2jhA1hnbjxd6wFqZq/+SKKBpLi/jRA96KARKjD4zBpbwMKkCJiXARTNzjD5M eDUv9qik3AyX8RxJcOm6BdqZW5iFrBUpucPgpBYdhgT0nSgX7ingLtYoMc9GR00XqQK2 bi30ATiImWW/Q0wtgV5WqQicdR3ZZtkSoXhBDXOETvM+IT/VUPQutnSk9narqCeF4NCF ig3h/EmF8zugT0dhojo9iokfjt2aS8UEXhpWdkvUdnniCr7B6M0yfFN1h8Q0VFQWnXM+ IbszDlYJYkEfjyV9w+x9nZ1AK45WbbJ1vtAdEUZ7FBQ+gKYwbyPTkH/BQhSZeWyusMk+ qcvQ==
MIME-Version: 1.0
X-Received: by 10.182.251.130 with SMTP id zk2mr20161333obc.57.1449518653189; Mon, 07 Dec 2015 12:04:13 -0800 (PST)
Received: by 10.60.177.103 with HTTP; Mon, 7 Dec 2015 12:04:13 -0800 (PST)
Date: Mon, 07 Dec 2015 15:04:13 -0500
Message-ID: <CAG4d1rdx8Mw7=x0M5nyN_5mVomVJ0Mz0JuKa9oSXOB6GNkF==g@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: draft-ietf-isis-pcr@ietf.org, "isis-wg@ietf.org" <isis-wg@ietf.org>
Content-Type: multipart/alternative; boundary="089e01634c2a6b35700526545ca6"
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/CsGByubsRtM9EaaZwNG0BT8kqYg>
Subject: [Isis-wg] AD review of draft-ietf-isis-pcr-03
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2015 20:04:16 -0000

Hi,

As is customary, I have done my usual AD review of draft-ietf-isis-pcr-03
before requesting IETF Last Call.  First, I would like to thank the
authors, Janos, Nigel, Paul, Glenn, Peter, and Chris, as well as those who
provided helpful reviews for their hard work on this draft.

I do have a few comments from my review (given below) but I am comfortable
having this progress to IETF Last Call while the draft is updated.  I have
scheduled this draft for the IESG telechat on January 7.  Please  update
the draft as soon as practical.

Minor:

1)  In Section 6.2 h:  How to tell if a Delay Constraint is present isn't
clearly described.   I assume that one can tell by calculating the expected
length of the Hop sub-TLV without the Delay Constraint and then comparing
that value to the actual length (as reported in the TLV).  If the actual
length is 6 bytes more, then there is a Delay Constraint.   If that's the
mechanism, could you please clearly write it down.  As described, it sounds
like the way to tell is simply by trying to parse the last 6 bytes as a
TLV.  I am assuming that there's a reason you didn't simply use an
additional flag to indicate whether the Delay Constraint is present -
because the trick above only works once per TLV.

2) In Sec 6.4 f and 6.2 c7:  For reserved bits, generally it is good to
describe them as "MUST be set to 0 on sending and the value MUST be ignored
on reception".  This allows extensions to work in the future.

Nits:

a) In Figure 1, the size of the Res & Base VID is described as (0 or 2
bytes).  If present, based on the description for (d) and (e), I think it
is always 2 bytes.  The figure should reflect this.  The field is missing -
not 0 bytes - if the "Num Base VIDs" is 0.

b) I see the same issue in Figure 3.  If you want to show the variability,
perhaps indicate (n bytes if present) or such.

Thanks,
Alia