[Isis-wg] AD review of draft-ietf-isis-remaining-lifetime-01

Alia Atlas <akatlas@gmail.com> Sat, 30 July 2016 04: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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFBCC12D0E7; Fri, 29 Jul 2016 21:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level:
X-Spam-Status: No, score=-102.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zoJ0bSvqd8_B; Fri, 29 Jul 2016 21:04:14 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 1B0B012B014; Fri, 29 Jul 2016 21:04:14 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id s63so106331956qkb.2; Fri, 29 Jul 2016 21:04:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=tGVNF74wxIvMMwlM0tx21uXY5V+SYCo1F9RWcNW8uMQ=; b=mFe0WKGJ46SWhppLum0V94xU3ZqrwfM0yPtYzuBG7Prm2Sih9TiK6XEZ3cs7489pKD ctgNkiAdaBpp6NeX09Ey9tR4ASgefOfCTQugr8J2Yiv4QqtdiQXQ46wg9k2Pz/tg1B0O jWPihoChmAaWNm/quJ0XTlMPg8g1mYKY2Yafw6e17ELoC5Xmh9MCiunAvr8Z90m2Bkmg bpHn8QfFYTYCbX3y8EHDj2PONCuHiqKQy1CJ2nhTcX58iw9urq7o2VKbU1qnhigBPrN+ ftr0qG8MRtGFAA5GuXoClRWYKAzKVEy190DDnU9ZZajvRiAZa0FOqXwBPLVtkUNXy4/0 RHbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tGVNF74wxIvMMwlM0tx21uXY5V+SYCo1F9RWcNW8uMQ=; b=AYtzqqcqUjrxazA01ZH4k+cMnZT3qfta6ADLaHNFGjJwnez54aLgBBvzr1z3fvjBYz c94ZbFOJDffnGnFHNZmgWjde26f8fX1O0nq5h6KJyWZ9+bUEAu6OUjAsBBk/Vww6fOHI ZXnTD0V90NkPVjS5wUCDJl8Q9LGW6ewaUeoeXI7fbZnjoM76F4m8P//4wfGvXp4Rfd3o 5e+49dZKyt6rpjiSlVaKxirPQjuKX/phXBLnFRVH/AGpxl/XddnleaP4wh24MlY8eBVQ ZOQBJdoR/u/5KnVmVZuoKPCMUlvxaJy3S2aPg0ZUM7FC7rNNrHgO8ZEoe0wajPzyrd3E PCAA==
X-Gm-Message-State: AEkoousCcH6u0B3hhE1ef/9JFxmjY6ZXHMYuGOFiF6iz7eQma7Z1lant+nrlNvSFAcBghz6mTG1m64fCgkYD7g==
X-Received: by 10.55.125.129 with SMTP id y123mr55750167qkc.204.1469851453115; Fri, 29 Jul 2016 21:04:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.52.193 with HTTP; Fri, 29 Jul 2016 21:04:12 -0700 (PDT)
From: Alia Atlas <akatlas@gmail.com>
Date: Sat, 30 Jul 2016 00:04:12 -0400
Message-ID: <CAG4d1rfuMoySO799ibhpStD1Kk8HMaxsBtAc-Hyi2=PTNuXZwA@mail.gmail.com>
To: "isis-wg@ietf.org" <isis-wg@ietf.org>, draft-ietf-isis-remaining-lifetime@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c060208bc52b70538d275dc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/wZ3_OEECXswrOLzM5-oaVXU7wJk>
Subject: [Isis-wg] AD review of draft-ietf-isis-remaining-lifetime-01
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 30 Jul 2016 04:04:16 -0000

First, I'd like to thank the many authors of this document for their work.
It's an interesting problem and the fix helps protect against an attack.

As is customary, I've done my AD review.  While I have no technical nits,
there are 6 authors on this document when - as you all know - the
acceptable limit is 5.  Please resolve this or send me a clear
justification as to why this document should be an exception.

I am requesting IETF Last Call and - assuming the author count is resolved
- hope to have this document on the IESG telechat on August 18.

Thanks,
Alia