Last Call: <draft-ietf-idr-aigp-16.txt> (The Accumulated IGP Metric Attribute for BGP) to Proposed Standard

The IESG <> Tue, 25 March 2014 15:08 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7759A1A01AA; Tue, 25 Mar 2014 08:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ID2ijk-JPNkh; Tue, 25 Mar 2014 08:08:49 -0700 (PDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 2DA3C1A0133; Tue, 25 Mar 2014 08:08:49 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-idr-aigp-16.txt> (The Accumulated IGP Metric Attribute for BGP) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.2.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 25 Mar 2014 08:08:49 -0700
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 Mar 2014 15:09:00 -0000

The IESG has received a request from the Inter-Domain Routing WG (idr) to
consider the following document:
- 'The Accumulated IGP Metric Attribute for BGP'
  <draft-ietf-idr-aigp-16.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 2014-04-08. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   Routing protocols that have been designed to run within a single
   administrative domain ("IGPs") generally do so by assigning a metric
   to each link, and then choosing as the installed path between two
   nodes the path for which the total distance (sum of the metric of
   each link along the path) is minimized.  BGP, designed to provide
   routing over a large number of independent administrative domains
   ("autonomous systems"), does not make its path selection decisions
   through the use of a metric.  It is generally recognized that any
   attempt to do so would incur significant scalability problems, as
   well as inter-administration coordination problems.  However, there
   are deployments in which a single administration runs several
   contiguous BGP networks.  In such cases, it can be desirable, within
   that single administrative domain, for BGP to select paths based on a
   metric, just as an IGP would do.  The purpose of this document is to
   provide a specification for doing so.

The file can be obtained via

IESG discussion can be tracked via

The following IPR Declarations may be related to this I-D: