Last Call: <draft-ietf-grow-wkc-behavior-03.txt> (Well-Known Community Policy Behavior) to Proposed Standard

The IESG <> Mon, 29 April 2019 21:17 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 8C560120195; Mon, 29 Apr 2019 14:17:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-grow-wkc-behavior-03.txt> (Well-Known Community Policy Behavior) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
CC: Job Snijders <>,,,,,
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Mon, 29 Apr 2019 14:17:53 -0700
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 29 Apr 2019 21:17:53 -0000

The IESG has received a request from the Global Routing Operations WG (grow)
to consider the following document: - 'Well-Known Community Policy Behavior'
  <draft-ietf-grow-wkc-behavior-03.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the mailing lists by 2019-05-13. Exceptionally, comments may be
sent to instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.


   Well-Known BGP Communities are manipulated inconsistently by current
   implementations.  This results in difficulties for operators.
   Network operators are encouraged to deploy consistent community
   handling across their networks, taking the inconsistent behaviors
   from the various BGP implementations they operate into consideration.
   Also, BGP implementors are expected to not create any further
   inconsistencies from this point forward.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.