[Docs] [txt|pdf|xml|html] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (RFC 8203) 00 01 draft-ietf-idr-rfc8203bis 

IDR                                                          J. Snijders
Internet-Draft                                                       NTT
Updates: 8203 (if approved)                                    A. Azimov
Intended status: Standards Track                                  Qrator
Expires: June 10, 2018                                  December 7, 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 10, 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 10, 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
   'Плановые
   работы по д&#10
   86;бавлению к&#
   1086;ммутатора
   в стек.
   Время заве&#108
   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 10, 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 10, 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: job@ntt.net


   Alexander Azimov
   Qrator Labs

   Email: aa@qrator.net














Snijders & Azimov         Expires June 10, 2018                 [Page 4]

Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/