Re: [OSPF] Suresh Krishnan's No Objection on draft-ietf-ospf-ospfv3-lsa-extend-21: (with COMMENT)

"Acee Lindem (acee)" <acee@cisco.com> Wed, 24 January 2018 20:11 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E42AA127871; Wed, 24 Jan 2018 12:11:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 B8-3MNSZ6dQB; Wed, 24 Jan 2018 12:11:19 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDA3B12700F; Wed, 24 Jan 2018 12:11:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2094; q=dns/txt; s=iport; t=1516824679; x=1518034279; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=rgdcsyGOWd5bSGyQnNsdnd/gSPrn7fyQZ5j4ZRnPiPA=; b=dXMnbZC/8b/8U+tFMLvR/aAU7qTLH2Bso8AbP3iTD9Y2nuvkH9W3wctF b9+RoYlA6ouNI2aHvcWsfmqsClsapsOyEyksTr8AWjnsn9hJghQ3jniZx eoxA+Bj3hGrmaHXfHbwxM55EkmqPpkL0rQCHfjJU4vyDlAnTZgyvqoIuf o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AkAQBj52ha/4cNJK1eGQEBAQEBAQEBAQEBAQcBAQEBAYNCZnQnB4NWiiSOZ5lCFYICCiOFGAIahGdUGAEBAQEBAQEBAmsohSQGIxFFEAIBCBoCJgICAjAVEAIEAQ0FijUQs0WCJ4pbAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBD4NDghWDaIMFgy8CAQEBAYE6ARIBgzYxgjQFil6ZKAKIEo1NghuGH4tqjVmJUQIRGQGBOwEfOWBXEQhwFWcBgX+DCYFOeAGLbYElgRcBAQE
X-IronPort-AV: E=Sophos;i="5.46,409,1511827200"; d="scan'208";a="60620972"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Jan 2018 20:11:18 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w0OKBHOA021443 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 24 Jan 2018 20:11:18 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 24 Jan 2018 15:11:17 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Wed, 24 Jan 2018 15:11:17 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Suresh Krishnan <suresh@kaloom.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-ospf-ospfv3-lsa-extend@ietf.org" <draft-ietf-ospf-ospfv3-lsa-extend@ietf.org>, "Peter Psenak (ppsenak)" <ppsenak@cisco.com>, "ospf-chairs@ietf.org" <ospf-chairs@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: Suresh Krishnan's No Objection on draft-ietf-ospf-ospfv3-lsa-extend-21: (with COMMENT)
Thread-Index: AQHTlSbglvpVMR4MukeWhB7MK8uJgaODdKwA
Date: Wed, 24 Jan 2018 20:11:17 +0000
Message-ID: <4775BB48-EBF8-4B07-AA70-EA088870A1E8@cisco.com>
References: <151680722696.25644.17704112504428127535.idtracker@ietfa.amsl.com>
In-Reply-To: <151680722696.25644.17704112504428127535.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <EF743154E2FE0A4B8FCC9EF7B9BD0549@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/_8H0GpVmpurky3OoKCNiwXrmFOo>
Subject: Re: [OSPF] Suresh Krishnan's No Objection on draft-ietf-ospf-ospfv3-lsa-extend-21: (with COMMENT)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 20:11:21 -0000

Hi Suresh, 

On 1/24/18, 10:20 AM, "Suresh Krishnan" <suresh@kaloom.com> wrote:

    Suresh Krishnan has entered the following ballot position for
    draft-ietf-ospf-ospfv3-lsa-extend-21: 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 https://www.ietf.org/iesg/statement/discuss-criteria.html
    for more information about IESG DISCUSS and COMMENT positions.
    
    
    The document, along with other ballot positions, can be found here:
    https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-lsa-extend/
    
    
    
    ----------------------------------------------------------------------
    COMMENT:
    ----------------------------------------------------------------------
    
    * Section 3.10 and 3.11
    
    What does the sub-TLV length mean here? Are values other than 4 and 16
    permitted? If not, how is the packet treated (sub TLV is ignored?)

My thought was to allow for further sub-TLVs defined recursively. However, one would still need a minimum length of 4 or 16 for the forwarding address TLVs. I will add this constraint and will indicate that the TLV is treated as malformed if it is not at least 4 or 16 octets respectively. Similarly, for the Route Tag sub-TLV, I'll indicate that the length must be at least 4 octets. 

Thanks,
Acee