[CCAMP] AD review of draft-ietf-ccamp-gmpls-general-constraints-ospf-te
"Adrian Farrel" <adrian@olddog.co.uk> Mon, 09 February 2015 21:53 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF3141A6EF2; Mon, 9 Feb 2015 13:53:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 DZW95CSBk4SA; Mon, 9 Feb 2015 13:53:54 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D10811A1A48; Mon, 9 Feb 2015 13:53:53 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id t19LrnLF004562; Mon, 9 Feb 2015 21:53:49 GMT
Received: from 950129200 (xdsl-77-74-119-17.c.btirol.at [77.74.119.17] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id t19Lrmma004556 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 9 Feb 2015 21:53:48 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: draft-ietf-ccamp-gmpls-general-constraints-ospf-te.all@tools.ietf.org
Date: Mon, 09 Feb 2015 21:53:48 -0000
Message-ID: <08a101d044b2$e2c73d40$a855b7c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdBEst8kNrktqnlPQrK4fkCKjG66tg==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21318.003
X-TM-AS-Result: No--18.050-10.0-31-10
X-imss-scan-details: No--18.050-10.0-31-10
X-TMASE-MatchedRID: 5jrCzlkkxksmMPeO88gK4HBRIrj8R47FQPCWRE0Lo8JkueSaR+/6ndFt mErgfwbM2bc+OIuXeVRZs4umC/0LtiUetYXFvf04TSPNp9e/u1PAWTziWGaDPKj5v7I4/SgYaF2 9jZP2X5eejMswFH3MZRYC4jP1GnU/Dc5IfPgQIojBVprK8rvWX+iY+s2L3xQE9ait85sNgkAIxY geqc1jTy9jQU5GdNMVl/nE+SiO7IZw+rm6wZ9/LolD2T5imTkJLJm8FOE9WLXJYIv7y0tu9v7np 1jxGcScTvm986Eb9qawG3wgUJicipO7ij3TaTVLo65WJt1k1O8TbU1KYGoQpxZIRcYzTqqlo8WM kQWv6iV95l0nVeyiuDrm2CwlZwVRvECLuM+h4RB+3BndfXUhXQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ccamp/LhO4s7VAB29ZiBl-iMTKv434dT0>
Cc: Alvaro Retana <aretana@cisco.com>, ccamp@ietf.org, teas@ietf.org
Subject: [CCAMP] AD review of draft-ietf-ccamp-gmpls-general-constraints-ospf-te
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2015 21:53:56 -0000
Authors! I have done my usual AD review of this document to prepare it for IETF last call and IESG evaluation. It's in good shape and my comments below are nearly completely editorial. Please have a look and let me know if you disagree. Otherwise, post a new revision and I'll take the document forward. Thanks for the work, Adrian --- You need to split the Authors' Addresses sections into: - Authors' Addresses reflecting those on the front page - Contributors containing all the others --- Section 1 has: The top-level TLV can take one of three values (1) Router Address [RFC3630], (2) Link [RFC3630], (3) Node Attribute defined in Section 2. Shouldn't this be: The top-level TLV can take one of three values (1) Router Address [RFC3630], (2) Link [RFC3630], (3) Node Attribute [RFC5786]. --- We need to do some work on the IANA stuff. In Section 2, please replace OLD Per [GEN-Encode], we have identified the following new Sub-TLVs to the Node Attribute TLV as defined in [RFC5786]. Detailed description for each newly defined Sub-TLV is provided in subsequent sections: Sub-TLV Type Length Name 14 (Suggested) variable Connectivity Matrix NEW Per [GEN-Encode], this document defines the Connectivity Matrix Sub- TLV of the Node Attribute TLV defined in [RFC5786]. The new Sub-TLV has Type TBD1 (to be assigned by IANA). END In Section 3, please replace OLD Per [GEN-Encode], we add the following additional link sub-TLVs to the link TLV in this document. Sub-TLV Type Length Name 26 (suggested) variable Port Label Restrictions NEW Per [GEN-Encode], this document defines the Port Label Restrictions Sub-TLV of the Link TLV defined in [RFC3630]. The new Sub-TLV has Type TBD2 (to be assigned by IANA). END In Section 7.1, please replace OLD This document defines a new sub-TLV of the Node Attribute TLV (Value 5). The assignment of the following new type in the "Types for sub- TLVs of TE Node Attribute TLV" portion of the "Open Shortest Path First (OSPF) Traffic Engineering TLVs" registry is needed: This document introduces the following sub-TLVs of Node Attribute TLV (Value 5): Type sub-TLV 14 (suggested, to be assigned by IANA) Connectivity Matrix NEW IANA maintains the "Open Shortest Path First (OSPF) Traffic Engineering TLVs" registry with a sub-registry called "Types for sub- TLVs of TE Node Attribute TLV". IANA is requested to assign a new code point as follows: Type | Sub-TLV | Reference -------+-------------------------------+------------ TBD1 | Connectivity Matrix sub-TLV | [This.I-D] END In Section 7.2, please replace OLD This document defines a new sub-TLV of the TE Link TLV (Value 2). The assignment of the following new type in the "Types for sub-TLVs of TE Link TLV" portion of the "Open Shortest Path First (OSPF) Traffic Engineering TLVs" registry is needed: Type sub-TLV 26 (suggested, to be assigned by IANA) Port Label Restrictions NEW IANA maintains the "Open Shortest Path First (OSPF) Traffic Engineering TLVs" registry with a sub-registry called "Types for sub- TLVs of TE Link TLV". IANA is requested to assign a new code point as follows: Type | Sub-TLV | Reference -------+-----------------------------------+------------ TBD2 | Port Label Restrictions sub-TLV | [This.I-D] END --- I think Section 6 should also reference 5250 since Opaque LSAs are, themselves, an attack vector. --- Did you consider including a short manageability section? Are there any existing management tools that are impacted by the new sub-TLVs? What might a user expect to configure related to these sub-TLVs? What might a user expect to be able to read from a device?