RFC 7948 on Internet Exchange BGP Route Server Operations

rfc-editor@rfc-editor.org Wed, 07 September 2016 20:01 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64AAB12B3F8; Wed, 7 Sep 2016 13:01:49 -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 bcUT4rtXUG9A; Wed, 7 Sep 2016 13:01:39 -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 8AF3B12B30F; Wed, 7 Sep 2016 13:01:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 71D3AB80B91; Wed, 7 Sep 2016 13:01:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7948 on Internet Exchange BGP Route Server Operations
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160907200136.71D3AB80B91@rfc-editor.org>
Date: Wed, 7 Sep 2016 13:01:36 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/TpduD0maXvrTXyhgnzROCkL6ZO4>
Cc: drafts-update-ref@iana.org, grow@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 20:01:49 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7948

        Title:      Internet Exchange BGP Route Server Operations 
        Author:     N. Hilliard, E. Jasinska,
                    R. Raszuk, N. Bakker
        Status:     Informational
        Stream:     IETF
        Date:       September 2016
        Mailbox:    nick@inex.ie, 
                    elisa@bigwaveit.org, 
                    robert@raszuk.net,
                    nbakker@akamai.com
        Pages:      15
        Characters: 36787
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-ix-bgp-route-server-operations-05.txt

        URL:        https://www.rfc-editor.org/info/rfc7948

        DOI:        http://dx.doi.org/10.17487/RFC7948

The popularity of Internet Exchange Points (IXPs) brings new
challenges to interconnecting networks.  While bilateral External BGP
(EBGP) sessions between exchange participants were historically the
most common means of exchanging reachability information over an IXP,
the overhead associated with this interconnection method causes
serious operational and administrative scaling problems for IXP
participants.

Multilateral interconnection using Internet route servers can
dramatically reduce the administrative and operational overhead
associated with connecting to IXPs; in some cases, route servers are
used by IXP participants as their preferred means of exchanging
routing information.

This document describes operational considerations for multilateral
interconnections at IXPs.

This document is a product of the Global Routing Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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