[Idr] Shepherd initial report on RFC8203bis

"Susan Hares" <shares@ndzh.com> Sat, 08 June 2019 06:47 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38B9212018F; Fri, 7 Jun 2019 23:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.948
X-Spam-Level:
X-Spam-Status: No, score=0.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 nKRVEz0oP8rG; Fri, 7 Jun 2019 23:47:16 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (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 6CD19120169; Fri, 7 Jun 2019 23:47:16 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=166.177.57.113;
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Cc: <draft-ietf-idr-rfc8203bis@ietf.org>
Date: Sat, 8 Jun 2019 02:47:12 -0400
Message-ID: <079f01d51dc6$00d6b9a0$02842ce0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07A0_01D51DA4.79C65220"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdUdxFK+5yu67cZcSua+jSTsHxRVSg==
Content-Language: en-us
X-Antivirus: AVG (VPS 190607-4, 06/07/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/rhoFMTXcHeCiUEPEVPhex_M48Eg>
Subject: [Idr] Shepherd initial report on RFC8203bis
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jun 2019 06:47:18 -0000

Status:  Almost ready,  3 required editorial and need for implementation
report revision. 

 

https://datatracker.ietf.org/doc/draft-ietf-idr-rfc8203bis/shepherdwriteup/

 

Issues:  key editorial things for IESG submission need to be addressed: 

 

1)      RFC8203 must be mentioned in the introduction as well as current
references (top of front page, Abstract)

2)      NITS need to be resolved

 

  found: Need for different boiler plate or resolution on generation 

  

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may

     have content which was first submitted before 10 November 2008.  If you

     have contacted all the original authors and they are all willing to
grant

     the BCP78 rights to the IETF Trust, then this is fine, and you can
ignore

     this comment.  If not, you may need to add the pre-RFC5378 disclaimer. 

     (See the Legal Provisions document at

     https://trustee.ietf.org/license-info for more information.)

 

If this is in error and you are using XML conversion, please inquire on
xml2rfc tool list. 

 

3)      IN section: 5.  IANA Considerations

 

        Old:  /Cease Notification message subcodes/

       New: /BGP Cease NOTIFICATION message subcodes/

 

    The actual registry name is in the new text.  

 

4)      Implementation report for OPENBSD and BIRD need to be completed or
explained. 

(yes/no) in each category is not understandable.  

 

Cheerily, Susan Hares