RFC 6396 on Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format

rfc-editor@rfc-editor.org Tue, 01 November 2011 04:56 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 C47C221F8ED2; Mon, 31 Oct 2011 21:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.667
X-Spam-Level:
X-Spam-Status: No, score=-101.667 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tb4nKyjqUcNJ; Mon, 31 Oct 2011 21:56:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5CF2821F8ED1; Mon, 31 Oct 2011 21:56:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1A196B1E004; Mon, 31 Oct 2011 21:52:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6396 on Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
From: rfc-editor@rfc-editor.org
Message-Id: <20111101045215.1A196B1E004@rfc-editor.org>
Date: Mon, 31 Oct 2011 21:52:15 -0700
Cc: grow@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Tue, 01 Nov 2011 04:56:33 -0000

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

        
        RFC 6396

        Title:      Multi-Threaded Routing Toolkit (MRT) Routing 
                    Information Export Format 
        Author:     L. Blunk, M. Karir,
                    C. Labovitz
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2011
        Mailbox:    ljb@merit.edu, 
                    mkarir@merit.edu, 
                    labovit@deepfield.net
        Pages:      33
        Characters: 73982
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-mrt-17.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6396.txt

This document describes the MRT format for routing information
export.  This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name.  The
format can be used to export routing protocol messages, state
changes, and routing information base contents.  [STANDARDS-TRACK]

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

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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