Re: [Lsr] Shepherd review of draft-ietf-ospf-ospfv2-hbit-05

Padmadevi Pillay Esnault <padma@huawei.com> Thu, 09 August 2018 23:05 UTC

Return-Path: <padma@huawei.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 4CF51130E79; Thu, 9 Aug 2018 16:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 51dj4e1Q3shc; Thu, 9 Aug 2018 16:05:55 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5CCD130E0C; Thu, 9 Aug 2018 16:05:54 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 91F70A16E54A0; Fri, 10 Aug 2018 00:05:51 +0100 (IST)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.399.0; Fri, 10 Aug 2018 00:05:53 +0100
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.107]) by SJCEML702-CHM.china.huawei.com ([169.254.4.139]) with mapi id 14.03.0399.000; Thu, 9 Aug 2018 16:05:42 -0700
From: Padmadevi Pillay Esnault <padma@huawei.com>
To: Yingzhen Qu <yingzhen.qu@huawei.com>, "draft-ietf-ospf-ospfv2-hbit@ietf.org" <draft-ietf-ospf-ospfv2-hbit@ietf.org>
CC: Padmadevi Pillay Esnault <padma@huawei.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Shepherd review of draft-ietf-ospf-ospfv2-hbit-05
Thread-Index: AQHUMDV+VLGDzHkKXUmvkmcPGmtQRA==
Date: Thu, 09 Aug 2018 23:05:41 +0000
Message-ID: <26B79163-D044-418D-9081-AC4313BFBC2D@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.209.216.230]
Content-Type: multipart/alternative; boundary="_000_26B79163D044418D9081AC4313BFBC2Dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/yGGtpgXxzkRN1jzKa8MWnCQ7k0A>
Subject: Re: [Lsr] Shepherd review of draft-ietf-ospf-ospfv2-hbit-05
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: Thu, 09 Aug 2018 23:05:58 -0000

Yingzhen

Thank you for your comment.
Will respin the draft to address them.

Padma

From: Lsr <lsr-bounces@ietf.org> on behalf of Yingzhen Qu <yingzhen.qu@huawei.com>
Date: Thursday, August 9, 2018 at 3:17 PM
To: "draft-ietf-ospf-ospfv2-hbit@ietf.org" <draft-ietf-ospf-ospfv2-hbit@ietf.org>
Cc: "lsr@ietf.org" <lsr@ietf.org>
Subject: [Lsr] Shepherd review of draft-ietf-ospf-ospfv2-hbit-05

Dear authors,

I’m assigned to do the shepherd review for draft-ietf-ospf-ospfv2-hbit-05.

The following question needs to be answered in the review:

(16) Will publication of this document change the status of any existing
     RFCs?  Are those RFCs listed on the title page header, listed in
     the abstract, and discussed in the introduction? If the RFCs are
     not listed in the Abstract and Introduction, explain why, and point
     to the part of the document where the relationship of this document
     to the other RFCs is discussed. If this information is not in the
     document, explain why the WG considers it unnecessary.

draft-ietf-ospf-ospfv2-hbit-05 does change RFC 2328, and this needs to be added in the title pager header, the abstract, and introduction. So please do an update version of the draft to include the required changes.

Also, please fix the nits in the abstract: “however it will not used as a transit router.”.

Thanks,
Yingzhen