Transparent Interconnection of Lots of Links (TRILL) over IP
draft-mrw-trill-over-ip-03
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2013-10-16
|
|
Replaced by |
|
draft-ietf-trill-over-ip
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group M. Wasserman
Internet-Draft Painless Security
Intended status: Standards Track D. Eastlake
Expires: April 19, 2014 D. Zhang
Huawei Technologies
October 16, 2013
Transparent Interconnection of Lots of Links (TRILL) over IP
draft-mrw-trill-over-ip-03.txt
Abstract
The Transparent Interconnection of Lots of Links (TRILL) protocol is
implemented by devices called TRILL Switches or RBridges (Routing
Bridges). TRILL supports both point-to-point and multi-access links
and is designed so that a variety of link protocols can be used
between TRILL switch ports. This document standardizes methods for
encapsulating TRILL in IP(v4 or v6) to provide a unified TRILL
campus.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 19, 2014.
Copyright Notice
Copyright (c) 2013 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
Wasserman, et al. Expires April 19, 2014 [Page 1]
Internet-Draft TRILL over IP October 2013
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.
Table of Contents
1. Requirements Terminology . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Use Cases for TRILL over IP . . . . . . . . . . . . . . . . . 3
3.1. Remote Office Scenario . . . . . . . . . . . . . . . . . 3
3.2. IP Backbone Scenario . . . . . . . . . . . . . . . . . . 4
3.3. Important Properties of the Scenarios . . . . . . . . . . 4
3.3.1. Security Requirements . . . . . . . . . . . . . . . . 4
3.3.2. Multicast Handling . . . . . . . . . . . . . . . . . 4
3.3.3. RBridge Neighbor Discovery . . . . . . . . . . . . . 5
4. TRILL Packet Formats . . . . . . . . . . . . . . . . . . . . 5
4.1. TRILL Data Packet . . . . . . . . . . . . . . . . . . . . 5
4.2. TRILL IS-IS Packet . . . . . . . . . . . . . . . . . . . 6
5. Link Protocol Specifics . . . . . . . . . . . . . . . . . . . 6
6. Port Configuration . . . . . . . . . . . . . . . . . . . . . 7
7. TRILL over UDP/IP Format . . . . . . . . . . . . . . . . . . 7
8. Handling Multicast . . . . . . . . . . . . . . . . . . . . . 8
9. Use of DTLS . . . . . . . . . . . . . . . . . . . . . . . . . 8
10. Transport Considerations . . . . . . . . . . . . . . . . . . 9
10.1. Recursive Ingress . . . . . . . . . . . . . . . . . . . 9
10.2. Fat Flows . . . . . . . . . . . . . . . . . . . . . . . 9
10.3. Congestion Control . . . . . . . . . . . . . . . . . . . 10
11. MTU Considerations . . . . . . . . . . . . . . . . . . . . . 10
12. Middlebox Considerations . . . . . . . . . . . . . . . . . . 10
13. Security Considerations . . . . . . . . . . . . . . . . . . . 10
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
16.1. Normative References . . . . . . . . . . . . . . . . . . 12
16.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Requirements Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text