PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol
RFC 6361
|
| Document |
Type |
|
RFC - Proposed Standard
(August 2011; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 6361 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Jari Arkko
|
|
IESG note |
|
James Carlson (carlsonj@workingcode.com) is the document shepherd.
|
|
Send notices to |
|
pppext-chairs@ietf.org
|
Internet Engineering Task Force (IETF) J. Carlson
Request for Comments: 6361 WorkingCode
Category: Standards Track D. Eastlake 3rd
ISSN: 2070-1721 Huawei
August 2011
PPP Transparent Interconnection of Lots of Links (TRILL) Protocol
Control Protocol
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6361.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Carlson & Eastlake Standards Track [Page 1]
RFC 6361 TRILL over PPP August 2011
Table of Contents
1. Introduction ....................................................2
2. PPP TRILL Negotiation ...........................................3
2.1. TNCP Packet Format .........................................3
2.2. TNP Packet Format ..........................................4
2.3. TLSP Packet Format .........................................5
3. TRILL PPP Behavior ..............................................5
4. Security Considerations .........................................6
5. IANA Considerations .............................................6
6. References ......................................................7
6.1. Normative References .......................................7
6.2. Informative References .....................................7
7. Acknowledgements ................................................8
1. Introduction
The TRILL Protocol [RFC6325] defines a set of mechanisms used to
communicate between RBridges. These devices can bridge together
large 802 networks using link-state protocols in place of the
traditional spanning tree mechanisms [RFC5556].
Over Ethernet, TRILL uses two separate Ethertypes to distinguish
between encapsulation headers, which carry user data, and link-state
messages, which compute network topology using a protocol based on
[IS-IS] [RFC6326]. These two protocols must be distinguished from
one another, and segregated from all other traffic.
In a network where PPP [RFC1661] is used to interconnect routers
(often over telecommunications links), it may be advantageous to be
able to bridge between Ethernet segments over those PPP links, and
thus integrate remote networks with an existing TRILL cloud. The
existing Bridging Control Protocol (BCP) [RFC3518] allows direct
bridging of Ethernet frames over PPP. However, this mechanism is
inefficient and inadequate for TRILL, which can be optimized for use
over PPP links.
To interconnect these devices over PPP links, three protocol numbers
are needed, and are reserved as follows:
Value (in hex) Protocol Name
-------------- -------------------------------------
005d TRILL Network Protocol (TNP)
405d TRILL Link State Protocol (TLSP)
805d TRILL Network Control Protocol (TNCP)
The usage of these three protocols is described in detail in the
following section.
Carlson & Eastlake Standards Track [Page 2]
Show full document text