Re: [Isis-wg] Barry Leiba's No Objection on draft-ietf-isis-extended-sequence-no-tlv-05: (with COMMENT)

Uma Chunduri <> Tue, 21 April 2015 15:59 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 85D4A1ACEFE; Tue, 21 Apr 2015 08:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iSIzEkwCkRQr; Tue, 21 Apr 2015 08:59:49 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 369011ACF08; Tue, 21 Apr 2015 08:59:49 -0700 (PDT)
X-AuditID: c618062d-f79686d0000030a8-fb-55361cc7af90
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id B2.DE.12456.7CC16355; Tue, 21 Apr 2015 11:47:51 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0210.002; Tue, 21 Apr 2015 11:59:47 -0400
From: Uma Chunduri <>
To: Barry Leiba <>, The IESG <>
Thread-Topic: Barry Leiba's No Objection on draft-ietf-isis-extended-sequence-no-tlv-05: (with COMMENT)
Thread-Index: AQHQe68hjrHmvPj5+kC8C1F5rXP6V51Xnkfg
Date: Tue, 21 Apr 2015 15:59:46 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZXLrHW/e4jFmowZlNqhaHFl9itZi2+SCz RcvJH+wWC3tns1u0/fnAYjHjz0RmiyvdC9ksjh56z+rA4XHv7mImj5ZVvcweS5b8ZApgjuKy SUnNySxLLdK3S+DKeD1/PXvBHNmKxXtXMDcw7pHpYuTkkBAwkTgw7Q0bhC0mceHeeiCbi0NI 4CijxLOpB5khnOWMEi/eLGcGqWIT0JP4OPUnO4gtIuAs8ebSHyaQImaBR8wS7f2nWEESwgIZ EmvfPWCEKMqUmNK3mwnCNpJ4e3YtWJxFQFWifeltsNW8Ar4SL1dPB1sgJOAo8evLQrA4p4CT xLY778GWMQKd9/3UGrA5zALiEreezGeCOFtAYsme88wQtqjEy8f/WCFsJYmPv+cD9XIA1WtK rN+lD9GqKDGl+yE7xFpBiZMzn7BMYBSbhWTqLISOWUg6ZiHpWMDIsoqRo7Q4tSw33chgEyMw 1o5JsOnuYNzz0vIQowAHoxIP7wI701Ah1sSy4srcQ4zSHCxK4ryLHhwMERJITyxJzU5NLUgt ii8qzUktPsTIxMEp1cA4b4tUzj2nb0plO6XML53qrPthFN75XDzUYu2PMrc09SWrGt69/j3r hsz7x597G9p47DdaHWyoWWrZu/h12p1PwR4X+SaGfFI3ZEhtO1D0+tr8auFPm5bMf2m/asmZ 5y2WvaoBnU9Ct0gof2UQWvDhxKwrUnYc+pMPL3Ys6YqWEtHOvP9Z8MU3JZbijERDLeai4kQA bUQ3EpYCAAA=
Archived-At: <>
Cc: "" <>, "" <>, "" <>, "" <>, "" <>, "" <>
Subject: Re: [Isis-wg] Barry Leiba's No Objection on draft-ietf-isis-extended-sequence-no-tlv-05: (with COMMENT)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 21 Apr 2015 15:59:51 -0000

Hi Barry,

Thank you for your review, please see in-line [Uma]:

Uma C.

-----Original Message-----
From: Barry Leiba [] 
Sent: Monday, April 20, 2015 2:15 PM
To: The IESG
Subject: Barry Leiba's No Objection on draft-ietf-isis-extended-sequence-no-tlv-05: (with COMMENT)

Barry Leiba has entered the following ballot position for
draft-ietf-isis-extended-sequence-no-tlv-05: 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
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


With respect to keeping the ESSN increasing, you mention cold-starting the router... but what about when the router hardware is replaced?  The mechanism outlined in Section 10.1 should cover things there (just make sure that the old and new routers both have the time set correctly),
[Uma]: Right, 10.1 should cover this. As specified in 10.1, 2nd paragraph".. especially after cold
   restarts or any other similar events."
Did I answer your question?

 but the mechanism in 10.2 won't.  Does this matter?  Or will the new router always have new keys, so it doesn't matter (I guess the last sentence in
10.2 covers that)?
[Uma]: Yes, changing keys is the last resort, per 10.2 -
" If the non-volatile
   storage is ever repaired or upgraded such that the contents are lost,
   keys MUST be changed to prevent replay attacks."

FWIW, I can change "upgraded" to "router hardware is upgraded"!

As long as you call Sections 10 and 11 "Appendix", the RFC Editor will move them to the end and re-number them.  Please check in AUTH48 to be sure the forward references to Section 10 (in Sections 3 and 3.1) are correct.  Or perhaps just don't call those sections appendices.  It seems to me that they're useful enough and brief enough to be part of the document main.

[Uma]: Thank you and (Alvaro too) for pointing out this. I shall remove the section numbering and update the references to point to correct Appendix.