Re: [Lsr] I-D Action: draft-ietf-ospf-lls-interface-id-05.txt

Peter Psenak <ppsenak@cisco.com> Wed, 25 July 2018 08:16 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED3B130E4A; Wed, 25 Jul 2018 01:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-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 sokojIMEHegH; Wed, 25 Jul 2018 01:16:26 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21C6B130F83; Wed, 25 Jul 2018 01:16:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3623; q=dns/txt; s=iport; t=1532506586; x=1533716186; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Rx/yHW046ynY3wOsNjq7FRtCs9Hq5YAkCYGh48/i2Ew=; b=lFNO3akDQSnWyV+M7pjUnpGwAIu9TjyGQn/zWpXIZ1ZpE4ixYuRCOXAO iGIB0kA/Nm+RU6HJgrVVQINixHOLY1Upt+cn4u4TiSz3Y2tRBQXkj9IO3 Oi3TxtShPq2xQhY/uo3rsHULVCnzqp0B9ary2sxr9p5c98rjQ4g8wUIIp 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D6AQCRMVhb/4QNJK1bGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNNY38og36UQ4IMjSiKGgsYDYRHAoJaITcVAQIBAQIBAQJ?= =?us-ascii?q?tHAyFNwEBAQMBASEVNgoBEAsYAgIFFgsCAgkDAgECARUwBgEMAQUCAQGDHYF?= =?us-ascii?q?/D69XgSAOhF6FdoELh3cXgUE/gRGDEoMbAQECAQEWhEeCVQKHbIUwjFYJhhW?= =?us-ascii?q?JH4FGRINSgkqFVYpEh2OBVyKBUjMaCBsVGiGCaQmLDIVAPTCOCgEB?=
X-IronPort-AV: E=Sophos;i="5.51,400,1526342400"; d="scan'208";a="147380744"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jul 2018 08:16:10 +0000
Received: from [10.60.140.53] (ams-ppsenak-nitro4.cisco.com [10.60.140.53]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTP id w6P8G89f002000; Wed, 25 Jul 2018 08:16:09 GMT
Message-ID: <5B5831C8.9090701@cisco.com>
Date: Wed, 25 Jul 2018 10:16:08 +0200
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Yingzhen Qu <yingzhen.qu@huawei.com>, "draft-ietf-ospf-lls-interface-id@ietf.org" <draft-ietf-ospf-lls-interface-id@ietf.org>
CC: "lsr@ietf.org" <lsr@ietf.org>
References: <153191356776.2859.14205758456640564525@ietfa.amsl.com> <3070DEEB-D659-4C12-93E9-F65009F6B73F@huawei.com>
In-Reply-To: <3070DEEB-D659-4C12-93E9-F65009F6B73F@huawei.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.60.140.53, ams-ppsenak-nitro4.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/iXm9bs5mOssdyaONfgsO6xeEGqU>
Subject: Re: [Lsr] I-D Action: draft-ietf-ospf-lls-interface-id-05.txt
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2018 08:16:30 -0000

Hi Yingzhen,

sure, I fix it with other comments that may come.

thanks,
Peter

On 25/07/18 06:10 , Yingzhen Qu wrote:
> Hi authors,
>
> I just run idnits against version 05, and there is still a warning:
>
>    Miscellaneous warnings:
>    ----------------------------------------------------------------------------
>
>    == The document seems to lack the recommended RFC 2119 boilerplate, even if
>       it appears to use RFC 2119 keywords -- however, there's a paragraph with
>       a matching beginning. Boilerplate error?
>
>       RFC 8174, paragraph 11:
>          The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>          "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
>          and "OPTIONAL" in this document are to be interpreted as
>          described in BCP 14 [RFC2119] [RFC8174] when, and only when, they
>          appear in all capitals, as shown here.
>
>       ... text found in draft:
>          The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>          "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
>          and "OPTIONAL" in this document are to be interpreted as
>          described in BCP14 [RFC2119] [RFC8174] when, and only when, they
> ........................^
>          appear in all capitals, as shown here.
>
>
> This is really minor. I suppose you can fix it later with other comments if there is any.
>
> Thanks,
> Yingzhen
>
>
> On 7/18/18, 4:33 AM, "Lsr on behalf of internet-drafts@ietf.org"; <lsr-bounces@ietf.org on behalf of internet-drafts@ietf.org>; wrote:
>
>
>      A New Internet-Draft is available from the on-line Internet-Drafts directories.
>      This draft is a work item of the Link State Routing WG of the IETF.
>
>              Title           : OSPF LLS Extensions for Local Interface ID Advertisement
>              Authors         : Peter Psenak
>                                Ketan Jivan Talaulikar
>                                Wim Henderickx
>                                Padma Pillay-Esnault
>      	Filename        : draft-ietf-ospf-lls-interface-id-05.txt
>      	Pages           : 7
>      	Date            : 2018-07-18
>
>      Abstract:
>         Every OSPF interface is assigned an identifier, Interface ID, which
>         uniquely identifies the interface on the router.  In some cases it is
>         useful to know the Interface ID assigned by the adjacent router on
>         its side of the adjacency (Remote Interface ID).
>
>         This draft describes the extensions to OSPF link-local signalling to
>         advertise the Local Interface Identifier.
>
>
>
>      The IETF datatracker status page for this draft is:
>      https://datatracker.ietf.org/doc/draft-ietf-ospf-lls-interface-id/
>
>      There are also htmlized versions available at:
>      https://tools.ietf.org/html/draft-ietf-ospf-lls-interface-id-05
>      https://datatracker.ietf.org/doc/html/draft-ietf-ospf-lls-interface-id-05
>
>      A diff from the previous version is available at:
>      https://www.ietf.org/rfcdiff?url2=draft-ietf-ospf-lls-interface-id-05
>
>
>      Please note that it may take a couple of minutes from the time of submission
>      until the htmlized version and diff are available at tools.ietf.org.
>
>      Internet-Drafts are also available by anonymous FTP at:
>      ftp://ftp.ietf.org/internet-drafts/
>
>      _______________________________________________
>      Lsr mailing list
>      Lsr@ietf.org
>      https://www.ietf.org/mailman/listinfo/lsr
>
>