(As an individual contributor and co-author.) Thanks for extending this, Sue. Maybe it will help the WG to have a reminder about what this document does.
It’s a revision of RFC 8203. First, here is the rfcdiff vs. RFC 8203: http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=rfc8203&url2=draft-ietf-idr-rfc8203bis It is quite short, especially when you skip over the boilerplate and "RFC EDITOR: REMOVE BEFORE PUBLICATION” sections. The sole normative change vs. 8203 is the deletion of one sentence: OLD: Length: this 8-bit field represents the length of the Shutdown Communication field in octets. The length value MUST range from 0 to 128 inclusive. When the length value is zero, no Shutdown Communication field follows. NEW: Length: this 8-bit field represents the length of the Shutdown Communication field in octets. When the length value is zero, no Shutdown Communication field follows. The reason for this change is summarized in in Appendix B: Feedback from operators based in regions which predominantly use multibyte character sets, showed that messages similar in meaning to what can be send in other languages in using single-byte encoding, failed to fit within the Length constraints as specified by [RFC8203]. For example, the phrase: 'Planned work to add switch to stack. Completion time - 30 minutes' has length 65 bytes. Its translation in Russian 'Плановые работы по д
 86;бавлению к&# 1086;ммутатора& #1074; стек.Время 
 79;авершения - 30минут' (See PDF for non-ASCII character string) has length 139 bytes. Now you do not need to actually go read the draft in order to know everything you need to respond to the WGLC. :-) Thanks, —John > On Jul 25, 2019, at 5:25 PM, Susan Hares <[email protected]> wrote: > > Greetings IDR: > > The IDR WG call for input on draft-ietf-idr-rfc8203bis-04.txt has received > only 2 comments. Since this is a draft that updates an operationally needed > feature, I am extending the WG LC until 8/6/2019. > > If you believe this draft is ready for publication, please respond to this WG > LC. > > Sue Hares > > From: Idr [mailto:[email protected]] On Behalf Of Susan Hares > Sent: Tuesday, July 9, 2019 9:13 AM > To: 'idr wg' > Subject: [Idr] WG LC for Extended BGP Administrative Shutdown Communication > (bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23) > > This begins a 2 week WG last call for draft-ietf-idr-rfc8203bis-04.txt from > July 9, 2019 to July 23, 2019. . > > Please consider if you believe this revision of RFC8203 (Administrative > Shutdown) > a) Will benefit operational networks, > b) is technically complete, and > c) ready for publication. > > In your comments, please indicate whether you “support” or “do not support” > its publication. > > This draft contains IPR notice that causes “IPR warnings”. The authors > believe that this text is automatically generated by the IETF tools and the > warning is not appropriate. > > As the shepherd, I am investigating this issue. If you have specific > knowledge on this issue, you may send it to the list or to me directly. > > Cheerily, Susan Hares > _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
