| rfc9003v2.txt | rfc9003.txt | |||
|---|---|---|---|---|
| skipping to change at line 269 ¶ | skipping to change at line 269 ¶ | |||
| [UTR36] Davis, M., Ed. and M. Suignard, Ed., "Unicode Security | [UTR36] Davis, M., Ed. and M. Suignard, Ed., "Unicode Security | |||
| Considerations", Unicode Technical Report #36, August | Considerations", Unicode Technical Report #36, August | |||
| 2010, <http://unicode.org/reports/tr36/>. | 2010, <http://unicode.org/reports/tr36/>. | |||
| Appendix A. Changes to RFC 8203 | Appendix A. Changes to RFC 8203 | |||
| The maximum permitted length was changed from 128 to 255. | The maximum permitted length was changed from 128 to 255. | |||
| Feedback from operators based in regions that predominantly use | Feedback from operators based in regions that predominantly use | |||
| multibyte character sets showed that messages similar in meaning to | multibyte character sets showed that messages similar in meaning to | |||
| what can be sent in other languages in using single-byte encoding | what can be sent in other languages using single-byte encoding failed | |||
| failed to fit within the length constraints as specified by | to fit within the length constraints as specified by [RFC8203]. For | |||
| [RFC8203]. For example, the phrase "Planned work to add switch to | example, the phrase "Planned work to add switch to stack. Completion | |||
| stack. Completion time - 30 minutes" has a length of 65 bytes. Its | time - 30 minutes" has a length of 65 bytes. Its translation in | |||
| translation in Russian has a length of 139 bytes. | Russian has a length of 139 bytes. | |||
| If a Shutdown Communication message longer than 128 octets is sent to | If a Shutdown Communication message longer than 128 octets is sent to | |||
| a BGP speaker that implements [RFC8203], then that speaker will bring | a BGP speaker that implements [RFC8203], then that speaker will bring | |||
| it to the attention of an operator but will otherwise process the | it to the attention of an operator but will otherwise process the | |||
| NOTIFICATION message as normal. | NOTIFICATION message as normal. | |||
| Acknowledgements | Acknowledgements | |||
| The authors would like to gratefully acknowledge Tom Scholl, David | The authors would like to gratefully acknowledge Tom Scholl, David | |||
| Freedman, Jared Mauch, Jeff Haas, Peter Hessler, Bruno Decraene, John | Freedman, Jared Mauch, Jeff Haas, Peter Hessler, Bruno Decraene, John | |||
| skipping to change at line 315 ¶ | skipping to change at line 315 ¶ | |||
| Jakob Heitz | Jakob Heitz | |||
| Cisco | Cisco | |||
| 170 West Tasman Drive | 170 West Tasman Drive | |||
| San Jose, CA 95134 | San Jose, CA 95134 | |||
| United States of America | United States of America | |||
| Email: jheitz@cisco.com | Email: jheitz@cisco.com | |||
| John Scudder | John Scudder | |||
| Juniper Networks | Juniper Networks | |||
| 1194 N. Mathilda Ave | 1133 Innovation Way | |||
| Sunnyvale, CA 94089 | Sunnyvale, CA 94089 | |||
| United States of America | United States of America | |||
| Email: jgs@juniper.net | Email: jgs@juniper.net | |||
| Alexander Azimov | Alexander Azimov | |||
| Yandex | Yandex | |||
| Ulitsa Lva Tolstogo 16 | Ulitsa Lva Tolstogo 16 | |||
| Moscow | Moscow | |||
| 119021 | 119021 | |||
| End of changes. 2 change blocks. | ||||
| 6 lines changed or deleted | 6 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||