-
Notifications
You must be signed in to change notification settings - Fork 1
/
draft-snijders-idr-8203bis.txt
224 lines (141 loc) · 7.82 KB
/
draft-snijders-idr-8203bis.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
IDR J. Snijders
Internet-Draft NTT
Updates: 8203 (if approved) A. Azimov
Intended status: Standards Track Qrator
Expires: June 11, 2018 December 8, 2017
Extended BGP Administrative Shutdown Communication
draft-snijders-idr-rfc8203bis-00
Abstract
This document updates RFC8203 by defining an Extended BGP
Administrative Shutdown Communication to improve communication using
multibyte character sets.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC8174].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 11, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Snijders & Azimov Expires June 11, 2018 [Page 1]
Internet-Draft BGP Shutdown December 2017
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Changes to RFC 8203 . . . . . . . . . . . . . . . . . . . . . 2
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 3
5. Normative References . . . . . . . . . . . . . . . . . . . . 3
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
The Administrative Shutdown Communication [RFC8203] is a simple
mechanism to transit a short freeform UTF-8 [RFC3629] message as part
of a Cease NOTIFICATION message [RFC4271] to inform the peer why the
BGP session is being shutdown or reset.
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;ммутатора
в стек.
Время завеl
8;шения - 30
минут' (See PDF for non-ASCII character
string) has length 139 bytes.
This document extends the length of the Administrative Shutdown
Communication to 255 octets.
2. Changes to RFC 8203
This section updates [RFC8203] to specify the maximum length of an
Administrative Shutdown Communication.
Snijders & Azimov Expires June 11, 2018 [Page 2]
Internet-Draft BGP Shutdown December 2017
The following paragraph replaces the Length definition in Section 2
(Shutdown Communication):
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 following paragraph replaces the second paragraph of Section 5
(Security Considerations):
As BGP Shutdown Communications are likely to appear in syslog
output, there is a risk that carefully constructed Shutdown
Communication might be formatted by receiving systems in a way to
make them appear as additional syslog messages. To limit the
ability to mount such an attack, the BGP Shutdown Communication is
limited to 255 octets in length.
3. Security Considerations
TBD
4. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION
This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in RFC7942. The
description of implementations in this section is intended to assist
the IETF in its decision processes in progressing drafts to RFCs.
Please note that the listing of any individual implementation here
does not imply endorsement by the IETF. Furthermore, no effort has
been spent to verify the information presented here that was supplied
by IETF contributors. This is not intended as, and must not be
construed to be, a catalog of available implementations or their
features. Readers are advised to note that other implementations may
exist.
As of today these vendors have produced an implementation of the
Shutdown Communication:
o TBD..
5. Normative References
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <https://www.rfc-editor.org/info/rfc3629>.
Snijders & Azimov Expires June 11, 2018 [Page 3]
Internet-Draft BGP Shutdown December 2017
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8203] Snijders, J., Heitz, J., and J. Scudder, "BGP
Administrative Shutdown Communication", RFC 8203,
DOI 10.17487/RFC8203, July 2017,
<https://www.rfc-editor.org/info/rfc8203>.
Appendix A. Acknowledgements
The authors would like to gratefully acknowledge Misha Grishin (MSK-
IX) for raising the length issue.
The authors would like to thank Jakob Heitz and John Scudder for
their work on [RFC8203].
Authors' Addresses
Job Snijders
NTT Communications
Theodorus Majofskistraat 100
Amsterdam 1065 SZ
The Netherlands
Email: [email protected]
Alexander Azimov
Qrator Labs
Email: [email protected]
Snijders & Azimov Expires June 11, 2018 [Page 4]