Protocol Action: 'AS-wide Unique BGP Identifier for BGP-4' to Proposed Standard (draft-ietf-idr-bgp-identifier-14.txt)

The IESG <> Tue, 31 May 2011 15:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2F5ECE0749; Tue, 31 May 2011 08:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Y2rM7P04x1cU; Tue, 31 May 2011 08:31:20 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id 45034E0818; Tue, 31 May 2011 08:31:16 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'AS-wide Unique BGP Identifier for BGP-4' to Proposed Standard (draft-ietf-idr-bgp-identifier-14.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <>
Date: Tue, 31 May 2011 08:31:16 -0700
Cc: idr mailing list <>, idr chair <>, RFC Editor <>
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 31 May 2011 15:31:25 -0000

The IESG has approved the following document:
- 'AS-wide Unique BGP Identifier for BGP-4'
  (draft-ietf-idr-bgp-identifier-14.txt) as a Proposed Standard

This document is the product of the Inter-Domain Routing Working Group.

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:

Technical Summary

The base BGP specification defined the BGP Identifier as "a valid
IPv4 host address".  This is problematic in some contexts
including IPv6-only networks.  This document relaxes the
definition to be a 4-octet unsigned, non-zero integer, and relaxes
the "uniqueness" requirement so that only AS-wide uniqueness of
the BGP Identifiers is required. These revisions to the base BGP
specification do not introduce any backward compatibility issue.

Working Group Summary

 The document has received extensive WG review and is generally
 non-controversial and clearly needed.

Document Quality

There are several existing implementations, and furthermore the
document makes no on-the-wire protocol changes and is backward
compatible.  The document does not use RFC 2119 language but I
don't view this as a problem. 


John Scudder is the Document Shepherd for this document.
Stewart Bryant is the Responsible Area Director.

RFC Editor Note

At the end of the abstract please add:

 This document updates RFC 4271.