Bidirectional Forwarding Detection (BFD) Padding Alteration
draft-xiao-bfd-padding-alteration-00

Document Type Active Internet-Draft (individual)
Last updated 2020-02-28
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
BFD Working Group                                                 X. Min
Internet-Draft                                                 ZTE Corp.
Intended status: Standards Track                       February 28, 2020
Expires: August 31, 2020

      Bidirectional Forwarding Detection (BFD) Padding Alteration
                  draft-xiao-bfd-padding-alteration-00

Abstract

   This document describes the procedures of the Bidirectional
   Forwarding Detection (BFD) protocol to alter BFD padding, using BFD
   in Asynchronous mode.

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 August 31, 2020.

Copyright Notice

   Copyright (c) 2020 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
   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.

Min                      Expires August 31, 2020                [Page 1]
Internet-Draft           BFD Padding Alteration            February 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   2
   2.  Turn On BFD Padding . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Switch From the Small BFD Packets . . . . . . . . . . . .   3
     2.2.  Switch From the Start of a BFD Session  . . . . . . . . .   4
   3.  Increase BFD Padding  . . . . . . . . . . . . . . . . . . . .   4
   4.  Decrease BFD Padding  . . . . . . . . . . . . . . . . . . . .   4
   5.  Turn Off BFD Padding  . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   "BFD Encapsulated in Large Packets" [I-D.ietf-bfd-large-packets]
   defines a new BFD variable bfd.PaddedPduSize, which can be configured
   to the value the BFD transport protocol payload size is increased to,
   and the contents of this additional payload MUST be zero.  In other
   words, the BFD protocol can be used to verify path MTU with BFD
   padding.

   Considering that there are implementations that do not support Large
   BFD Packets, [I-D.ietf-bfd-large-packets] specifies that when an
   implementation is incapable of processing Large BFD Packets, the BFD
   state machine will behave as if it were not receiving Control
   packets.  The implementation would follow standard BFD procedures
   with regards to not having received Control packets.

   "Bidirectional Forwarding Detection (BFD)" [RFC5880] specifies the
   Poll Sequence as an exchange of BFD Control packets that is used in
   some circumstances to ensure that the remote system is aware of
   parameter changes.

   This document describes the procedures of the Bidirectional
   Forwarding Detection (BFD) protocol to alter BFD padding, using BFD
   in Asynchronous mode.  The procedure defined in this document refers
   to but differs from the Poll Sequence defined in Section 6.5 of
   [RFC5880].

1.1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP

Min                      Expires August 31, 2020                [Page 2]
Internet-Draft           BFD Padding Alteration            February 2020

   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Turn On BFD Padding

   There are two scenarios when turning on BFD padding.  One is to turn
   on BFD padding when the BFD session is Up and running with the Small
Show full document text