Decprecate Atomic Aggregate
draft-hares-deprecate-atomic-aggregate-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml html 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)
IDR                                                             S. Hares
Internet-Draft                                                    Huawei
Updates: 4271 (if approved)                               March 13, 2017
Intended status: Standards Track
Expires: September 14, 2017

                      Decprecate Atomic Aggregate
             draft-hares-deprecate-atomic-aggregate-00.txt

Abstract

   This document deprecates the support for the BGP well-know
   discretionary attribute ATOMIC_AGGREGATE specified in RFC4271.  It
   proposes the changes to RFC4271 to remove its support.

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 [RFC2119].

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 http://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 September 14, 2017.

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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Hares                  Expires September 14, 2017               [Page 1]
Internet-Draft         Deprecate Atomic Aggregate             March 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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Changes to Section 4.3  . . . . . . . . . . . . . . . . . . .   2
   3.  Changes to Section 5 - Path Attributes  . . . . . . . . . . .   3
   4.  Changes to Section 9  . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Changes to section 9.1.4  . . . . . . . . . . . . . . . .   3
     4.2.  Section 9.2 Changes . . . . . . . . . . . . . . . . . . .   4
   5.  Operational Considerations  . . . . . . . . . . . . . . . . .   4
   6.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The ATOMIC_AGGREGATE well-known discretionary attribute is specified
   in [RFC4271] in section 5.1.6.  This document specifies the changes
   to RFC4271 in order to remove the ATOMIC_AGGREGATE attribute.

2.  Changes to Section 4.3

   delete the following text:

Hares                  Expires September 14, 2017               [Page 2]
Internet-Draft         Deprecate Atomic Aggregate             March 2017

          f) ATOMIC_AGGREGATE (Type Code 6)

             ATOMIC_AGGREGATE is a well-known discretionary attribute of
             length 0.
Show full document text