Gen-ART Last Call review of draft-ietf-isis-mi-bis-02

Orit Levin <> Fri, 07 April 2017 03:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2B897127058; Thu, 6 Apr 2017 20:26:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5iMFajAQ5Eqq; Thu, 6 Apr 2017 20:26:46 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0341F129446; Thu, 6 Apr 2017 20:26:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GLFhJr/BFrNmaCDelZ1GM0u4CsbiBwY46ojzAcJXllU=; b=LQHj8c8Q/v7QbXLXxBdYOStPBzkkYYWAry5MWReG/2Dot0eD4cc/JASXi/VtHDBXdEpv/Vmc38rV7haMYbnMksU+M/vw6Tc2Z5vY21rpZO6IFNmYQ7aLYx8v3/YVdLQTLy2IPzxQr6TnPUlufAHdMU1eJm2xCpRvCzf5g/DkV2U=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Fri, 7 Apr 2017 03:26:44 +0000
Received: from ([]) by ([]) with mapi id 15.01.1019.019; Fri, 7 Apr 2017 03:26:44 +0000
From: Orit Levin <>
To: "" <>
CC: "" <>, "" <>
Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJA==
Date: Fri, 7 Apr 2017 03:26:44 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results:; dkim=none (message not signed) header.d=none;; dmarc=none action=none;
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2121; 7:C1QK1mUv/ryjQAGMCyaaNd1PxAKsnpV/3x7xPYPH9XTcf5jQM5rWPb60DBT/QQ2IxYuQSBPkGMOdIqLppRytbOqbRoHi3/1muyQvt3Pditsl41HmkYKwrMlHWmD67oQGzjSFYQwG9SZpRyfCeUJeANx8ccXK4XqcYa5RIcrZurEINQJ3ukQPvFI2hEaEB4fIy1bkOrO9fq0Fi5lz+V8ni6FmsLbPNOcZRLikD+LlojAjuM94L+Ua/I284kf+TyT/1sMjRamLCEjCPIIjMNZl6jXscM1WEHEawztq9K4PxDVq0D2wMBVU+IFX1u63C7XoNh6ZhTsvt0eVEgAo0jzKwrgVTn2tznsBjqmSp7DKJlE=
x-ms-office365-filtering-correlation-id: 3cf57564-a829-4d97-c9ac-08d47d65ea6a
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:CY1PR0301MB2121;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(192374486261705)(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123555025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(20161123560025)(6072148); SRVR:CY1PR0301MB2121; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2121;
x-forefront-prvs: 0270ED2845
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39840400002)(39400400002)(39860400002)(39850400002)(377424004)(2351001)(66066001)(8990500004)(5660300001)(53936002)(6506006)(38730400002)(110136004)(10090500001)(5005710100001)(77096006)(99286003)(5640700003)(6306002)(9686003)(7736002)(6436002)(2906002)(74316002)(55016002)(305945005)(10290500002)(2501003)(33656002)(230783001)(4326008)(3660700001)(102836003)(6916009)(3846002)(6116002)(7696004)(81166006)(50986999)(2900100001)(8936002)(54356999)(189998001)(8676002)(86362001)(25786009)(3280700002)(122556002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2121;; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2017 03:26:44.1930 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2121
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 07 Apr 2017 03:26:48 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair.  Please treat these comments just like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-isis-mi-bis-02
Reviewer: Orit Levin
Review Date: 2017-04-06
IETF LC End Date: 2017-04-07
IESG Telechat date: 2017-04-13

Summary: This draft is "ready with issues" for publication.

Major issues: None.

Minor issues:

1. Add text explaining the reason (or reasons) for replacing the original RFC 6822 from 2012. 
Reason: It is a "bis" draft and there is no mention about it in the text.
2. In Abstract, state clearly that this standard introduces the support for instances vs. other already existing concepts also listed in the Abstract (i.e., circuits, adjacencies,  topologies, etc.).
Reason: The wording is not clear about what is the new feature vs. what are the new benefits vs. what was the original baseline
3. Throughout the document, use "standard instance" instead of "IID = 0" or "IID #0".
Reason: Expressions "standard instance", "IID = 0" and "IID #0" are used interchangeably throughout the document. It seems that they all refer to the same thing - the implementation of the original protocol without the concept of instances. Please, correct me if I am wrong.
4. In section 2 par 3, change "support" and "operates" to "MUST support" to use requirements language.
5. In section 2 par 2, change "may" to either "can" or "MAY" to clarify the intent.
6. In section 2.1 par 3, clarify whether IID #0 is ever being used on the wire. Explain the concept of the "standard interface" (see previous comment).
Reason: It seems to me that IID #0 MUST never be used on the wire. Please, correct me if I am wrong.
7. In section 2.1, rephrase "marks ... by including" to "MUST include" to use requirements language.
8. In section 2.4.1 par 2 second sentence, the sentence starting with "However" needs to be rewritten using standards language to explain its intent. 
9. In section 2.5, replace "exists" with "MUST be performed".
10. In section 2.5.1, replace "only operates" with "MUST only be performed".
11. In section 2.5.2, replace "This requires" with "It is REQUIRED".
12. In section 2.5.2 third sentence, after "inconsistent" insert "due to their configuration". Please, correct me if I am wrong.
13. In section 7 Security Considerations, discuss possible additional security considerations (or the lack of them) related to the introduction of "instances".
Reason: Beyond the normal IETF procedure, this is especially important because "multiple instances allow isolation of resources..." Can this isolation, if observed or interfered, be damaging beyond the previous "standard interface" situation.

Nits/editorial comments:
1. Compare (Diff) the current draft with the published RFC 6822. You will find that many of the editorial corrections got lost in the bis version. Omitted corrections throughout the document include "instance-specific", " topology (or topologies)", "Type-Length-Value" and others.
2. In Introduction par 4, either change the two "may" to capitals or replace with "can" to clarify the intent.
3. In Introduction par 5, add references to where in the document the two methods are described. Also, consider changing "defined" to "described".
4. In Introduction par 7, move the last paragraph before listing the examples and adjust the text accordingly, for clarity.
5. In section 2.3, replace "normal" with "usual".
6. In section 2.6.1 first sentence, replace "not to cause" to "to avoid".