[Idr] RFC 7947 on Internet Exchange BGP Route Server
rfc-editor@rfc-editor.org Wed, 07 September 2016 20:01 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7626612B2E7; Wed, 7 Sep 2016 13:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.13
X-Spam-Level:
X-Spam-Status: No, score=-104.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuVYpmAqJaOj; Wed, 7 Sep 2016 13:01:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C9E512B264; Wed, 7 Sep 2016 13:01:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 88C1EB80B8B; Wed, 7 Sep 2016 13:01:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160907200124.88C1EB80B8B@rfc-editor.org>
Date: Wed, 07 Sep 2016 13:01:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Hh4y5YQs-Bsdl3eVf2_KDJUQf-w>
Cc: drafts-update-ref@iana.org, idr@ietf.org, rfc-editor@rfc-editor.org
Subject: [Idr] RFC 7947 on Internet Exchange BGP Route Server
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 20:01:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7947
Title: Internet Exchange BGP Route Server
Author: E. Jasinska, N. Hilliard,
R. Raszuk, N. Bakker
Status: Standards Track
Stream: IETF
Date: September 2016
Mailbox: elisa@bigwaveit.org,
nick@inex.ie,
robert@raszuk.net,
nbakker@akamai.com
Pages: 12
Characters: 26589
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-ix-bgp-route-server-12.txt
URL: https://www.rfc-editor.org/info/rfc7947
DOI: http://dx.doi.org/10.17487/RFC7947
This document outlines a specification for multilateral
interconnections at Internet Exchange Points (IXPs). Multilateral
interconnection is a method of exchanging routing information among
three or more External BGP (EBGP) speakers using a single
intermediate broker system, referred to as a route server. Route
servers are typically used on shared access media networks, such as
IXPs, to facilitate simplified interconnection among multiple
Internet routers.
This document is a product of the Inter-Domain Routing Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC