[GROW] I-D Action: draft-ietf-grow-anycast-community-03.txt

internet-drafts@ietf.org Sun, 26 November 2023 13:22 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 43816C14CE44; Sun, 26 Nov 2023 05:22:05 -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: 11.15.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: grow@ietf.org
Message-ID: <170100492525.51051.16667160985606878398@ietfa.amsl.com>
Date: Sun, 26 Nov 2023 05:22:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/sRKBRUxrzkc8c-cNpNdk40lB9rc>
Subject: [GROW] I-D Action: draft-ietf-grow-anycast-community-03.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: Sun, 26 Nov 2023 13:22:05 -0000

Internet-Draft draft-ietf-grow-anycast-community-03.txt is now available. It
is a work item of the Global Routing Operations (GROW) WG of the IETF.

   Title:   A well-known BGP community to denote prefixes used for Anycast
   Authors: Maximilian Wilhelm
            Fredy Kuenzler
   Name:    draft-ietf-grow-anycast-community-03.txt
   Pages:   6
   Dates:   2023-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 Internet-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-03

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-anycast-community-03

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts