RFC 6361 on PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol

rfc-editor@rfc-editor.org Thu, 25 August 2011 23:11 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 709F721F8C42 for <ietf-announce@ietfa.amsl.com>; Thu, 25 Aug 2011 16:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.198
X-Spam-Level:
X-Spam-Status: No, score=-102.198 tagged_above=-999 required=5 tests=[AWL=-0.198, 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 xLPJjNYGDeXR for <ietf-announce@ietfa.amsl.com>; Thu, 25 Aug 2011 16:11:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 19C3F21F8C3C for <ietf-announce@ietf.org>; Thu, 25 Aug 2011 16:11:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5442198C257; Thu, 25 Aug 2011 16:12:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6361 on PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20110825231229.5442198C257@rfc-editor.org>
Date: Thu, 25 Aug 2011 16:12:29 -0700
Cc: 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: Thu, 25 Aug 2011 23:11:24 -0000

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

        
        RFC 6361

        Title:      PPP Transparent Interconnection of Lots 
                    of Links (TRILL) Protocol Control Protocol 
        Author:     J. Carlson, D. Eastlake 3rd
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2011
        Mailbox:    carlsonj@workingcode.com, 
                    d3e3e3@gmail.com
        Pages:      8
        Characters: 17705
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pppext-trill-protocol-08.txt

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

The Point-to-Point Protocol (PPP) defines a Link Control Protocol
(LCP) and a method for negotiating the use of multiprotocol traffic
over point-to-point links.  This document describes PPP support for
the Transparent Interconnection of Lots of Links (TRILL) Protocol,
allowing direct communication between Routing Bridges (RBridges) via
PPP links.  [STANDARDS-TRACK]

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