Early Review of draft-ietf-idr-rfc8203bis-04
review-ietf-idr-rfc8203bis-04-opsdir-early-romascanu-2019-10-01-00
| Request | Review of | draft-ietf-idr-rfc8203bis |
|---|---|---|
| Requested revision | No specific revision (document currently at 08) | |
| Type | Early Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2019-09-25 | |
| Requested | 2019-09-11 | |
| Requested by | Susan Hares | |
| Authors | Job Snijders , Jakob Heitz , John Scudder , Alexander Azimov | |
| I-D last updated | 2019-10-01 | |
| Completed reviews |
Opsdir Early review of -04
by Dan Romascanu
(diff)
Rtgdir Early review of -04 by Christian Hopps (diff) Secdir Last Call review of -06 by David Mandelberg (diff) Opsdir Last Call review of -06 by Dan Romascanu (diff) Genart Last Call review of -06 by Dale R. Worley (diff) |
|
| Comments |
Second request with more data
The ID NIT Regarding this draft that states the text below is on the
BCP 78 rights for RFC 4486. These have been granted and confirmed
during the RFC8203 discussion. The reviewers can ignore this point.
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.)
|
|
| Assignment | Reviewer | Dan Romascanu |
| State | Completed | |
| Request | Early review on draft-ietf-idr-rfc8203bis by Ops Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/7OLMAOHDwvRbWOAt7zuwask93bI | |
| Reviewed revision | 04 (document currently at 08) | |
| Result | Has issues | |
| Completed | 2019-10-01 |
review-ietf-idr-rfc8203bis-04-opsdir-early-romascanu-2019-10-01-00
This document defines an enhancement to the BGP Cease NOTIFICATION message "Administrative Shutdown" and "Administrative Reset" subcodes for operators to transmit a short freeform message to describe why a BGP session was shutdown or reset. This document updates RFC 4486 and obsoletes RFC 8203 by defining an Extended BGP Administrative Shutdown Communication to improve communication using multibyte character sets. It's clear and rather straightforward, so a full RFC 5706 review would not apply. However, I have some questions and issues that I would suggest to be clarified before advancement and approval. 1. The document will obsolete, if approved, [RFC 8203]. The rationale for this change is currently relegated in Appendix B. I suggest to be moved up forward in the document, in the introduction section. 2. The 'Changes to RFC 8203' section should include an explicit list of the changes such as length field and usage of multibyte character sets. 3. I do not know how widely deployed RFC 8203 may be, but we cannot exclude that some versions do exist out there. I suggest that the Operational Considerations sections include some information about what caution need to be taken by the operators when migrating from supporting RFC 8203 to the new RFC. 4. What does 'an invalid length value' mean in 'Error Handling' now? Previously RFC 8203 had a requirement that 'The length value MUST range from 0 to 128 inclusive.' This does not exist any longer now.