[GROW] I-D Action: draft-ietf-grow-anycast-community-00.txt
internet-drafts@ietf.org Sat, 26 November 2022 22:05 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A48AC14F738; Sat, 26 Nov 2022 14:05:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: grow@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 9.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: grow@ietf.org
Message-ID: <166950035422.41067.2034227921012751907@ietfa.amsl.com>
Date: Sat, 26 Nov 2022 14:05:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/6aGtQa4yvEZSmpw2vDs3Zzr53xQ>
Subject: [GROW] I-D Action: draft-ietf-grow-anycast-community-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Nov 2022 22:05:54 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Global Routing Operations WG of the IETF. Title : A well-known BGP community to denote prefixes used for Anycast Authors : Maximilian Wilhelm Fredy Kuenzler Filename : draft-ietf-grow-anycast-community-00.txt Pages : 7 Date : 2022-11-26 Abstract: In theory routing decisions on the Internet and by extension within ISP networks should always use hot-potato routing to reach any given destination. In reality operators sometimes choose to not use the hot-potato paths to forward traffic due to a variety of reasons, mostly motivated by traffic engineering considerations. For prefixes carrying anycast traffic in virtually all situations it is advisable to stick to the hot-potato principle. As operators mostly don't know which prefixes are carrying unicast or anycast traffic, they can't differentiate between them in their routing policies. To allow operators to take well informed decisions on which prefixes are carrying anycast traffic this document proposes a well-known BGP community to denote this property. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-grow-anycast-community/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-grow-anycast-community-00 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
- [GROW] I-D Action: draft-ietf-grow-anycast-commun… internet-drafts