draft-ietf-grow-wkc-behavior-07.txt   draft-ietf-grow-wkc-behavior-08.txt 
Network Working Group J. Borkenhagen Network Working Group J. Borkenhagen
Internet-Draft AT&T Internet-Draft AT&T
Updates: 1997 (if approved) R. Bush Updates: 1997 (if approved) R. Bush
Intended status: Standards Track IIJ & Arrcus Intended status: Standards Track IIJ & Arrcus
Expires: December 12, 2019 R. Bonica Expires: December 15, 2019 R. Bonica
Juniper Networks Juniper Networks
S. Bayraktar S. Bayraktar
Cisco Systems Cisco Systems
June 10, 2019 June 13, 2019
Well-Known Community Policy Behavior Well-Known Community Policy Behavior
draft-ietf-grow-wkc-behavior-07 draft-ietf-grow-wkc-behavior-08
Abstract Abstract
Well-Known BGP Communities are manipulated differently across various Well-Known BGP Communities are manipulated differently across various
current implementations; resulting in difficulties for operators. current implementations; resulting in difficulties for operators.
Network operators should deploy consistent community handling across Network operators should deploy consistent community handling across
their networks while taking the inconsistent behaviors from the their networks while taking the inconsistent behaviors from the
various BGP implementations into consideration.. This document various BGP implementations into consideration.. This document
recommends specific actions to limit future inconsistency, namely BGP recommends specific actions to limit future inconsistency, namely BGP
implementors must not create further inconsistencies from this point implementors must not create further inconsistencies from this point
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 12, 2019. This Internet-Draft will expire on December 15, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 14 skipping to change at page 5, line 14
is not formally a Well-Known Community as it is not in [IANA-WKC]; is not formally a Well-Known Community as it is not in [IANA-WKC];
but taken from the Reserved range [0x00000000-0x0000FFFF]. but taken from the Reserved range [0x00000000-0x0000FFFF].
This merely notes an inconsistency. It is not a plea to 'protect' This merely notes an inconsistency. It is not a plea to 'protect'
the entire IANA list from "set community." the entire IANA list from "set community."
5. Note for Those Writing RFCs for New Community-Like Attributes 5. Note for Those Writing RFCs for New Community-Like Attributes
When establishing new [RFC1997]-like attributes (large communities, When establishing new [RFC1997]-like attributes (large communities,
wide communities, etc.), RFC authors should state explicitly how the wide communities, etc.), RFC authors should state explicitly how the
> new attribute is to be handled. new attribute is to be handled.
6. Action Items 6. Action Items
Network operators are encouraged to limit their use of the "set" Network operators are encouraged to limit their use of the "set"
directive (within reason), to improve consistency across platforms. directive (within reason), to improve consistency across platforms.
Unfortunately, it would be operationally disruptive for vendors to Unfortunately, it would be operationally disruptive for vendors to
change their current implementations. change their current implementations.
Vendors SHOULD clearly document the behavior of "set" directive in Vendors MUST clearly document the behavior of "set" directive in
their implementations. their implementations.
Vendors MUST ensure that their implementations' "set" directive Vendors MUST ensure that their implementations' "set" directive
treatment of any specific community does not change if/when that treatment of any specific community does not change if/when that
community becomes a new Well-Known Community through future community becomes a new Well-Known Community through future
standardization. For most implementations, this means that the "set" standardization. For most implementations, this means that the "set"
directive MUST continue to remove the community; for those directive MUST continue to remove the community; for those
implementations where the "set" directive removes no communities, implementations where the "set" directive removes no communities,
that behavior MUST continue. that behavior MUST continue.
 End of changes. 6 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/