| 1 |
<pre>Internet Engineering Task Force (IETF) J. Carlson |
| 2 |
Request for Comments: 6361 WorkingCode |
| 3 |
Category: Standards Track D. Eastlake 3rd |
| 4 |
ISSN: 2070-1721 Huawei |
| 5 |
August 2011 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">PPP Transparent Interconnection of Lots of Links (TRILL) Protocol</span> |
| 9 |
<span class="h1">Control Protocol</span> |
| 10 |
|
| 11 |
Abstract |
| 12 |
|
| 13 |
The Point-to-Point Protocol (PPP) defines a Link Control Protocol |
| 14 |
(LCP) and a method for negotiating the use of multiprotocol traffic |
| 15 |
over point-to-point links. This document describes PPP support for |
| 16 |
the Transparent Interconnection of Lots of Links (TRILL) Protocol, |
| 17 |
allowing direct communication between Routing Bridges (RBridges) via |
| 18 |
PPP links. |
| 19 |
|
| 20 |
Status of This Memo |
| 21 |
|
| 22 |
This is an Internet Standards Track document. |
| 23 |
|
| 24 |
This document is a product of the Internet Engineering Task Force |
| 25 |
(IETF). It represents the consensus of the IETF community. It has |
| 26 |
received public review and has been approved for publication by the |
| 27 |
Internet Engineering Steering Group (IESG). Further information on |
| 28 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 29 |
|
| 30 |
Information about the current status of this document, any errata, |
| 31 |
and how to provide feedback on it may be obtained at |
| 32 |
<a href="http://www.rfc-editor.org/info/rfc6361">http://www.rfc-editor.org/info/rfc6361</a>. |
| 33 |
|
| 34 |
Copyright Notice |
| 35 |
|
| 36 |
Copyright (c) 2011 IETF Trust and the persons identified as the |
| 37 |
document authors. All rights reserved. |
| 38 |
|
| 39 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 40 |
Provisions Relating to IETF Documents |
| 41 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 42 |
publication of this document. Please review these documents |
| 43 |
carefully, as they describe your rights and restrictions with respect |
| 44 |
to this document. Code Components extracted from this document must |
| 45 |
include Simplified BSD License text as described in Section 4.e of |
| 46 |
the Trust Legal Provisions and are provided without warranty as |
| 47 |
described in the Simplified BSD License. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Carlson & Eastlake Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6361">RFC 6361</a> TRILL over PPP August 2011</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. PPP TRILL Negotiation ...........................................<a href="#page-3">3</a> |
| 61 |
<a href="#section-2.1">2.1</a>. TNCP Packet Format .........................................<a href="#page-3">3</a> |
| 62 |
<a href="#section-2.2">2.2</a>. TNP Packet Format ..........................................<a href="#page-4">4</a> |
| 63 |
<a href="#section-2.3">2.3</a>. TLSP Packet Format .........................................<a href="#page-5">5</a> |
| 64 |
<a href="#section-3">3</a>. TRILL PPP Behavior ..............................................<a href="#page-5">5</a> |
| 65 |
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-6">6</a> |
| 66 |
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-6">6</a> |
| 67 |
<a href="#section-6">6</a>. References ......................................................<a href="#page-7">7</a> |
| 68 |
<a href="#section-6.1">6.1</a>. Normative References .......................................<a href="#page-7">7</a> |
| 69 |
<a href="#section-6.2">6.2</a>. Informative References .....................................<a href="#page-7">7</a> |
| 70 |
<a href="#section-7">7</a>. Acknowledgements ................................................<a href="#page-8">8</a> |
| 71 |
|
| 72 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 73 |
|
| 74 |
The TRILL Protocol [<a href="./rfc6325" title=""Routing Bridges (RBridges): Base Protocol Specification"">RFC6325</a>] defines a set of mechanisms used to |
| 75 |
communicate between RBridges. These devices can bridge together |
| 76 |
large 802 networks using link-state protocols in place of the |
| 77 |
traditional spanning tree mechanisms [<a href="./rfc5556" title=""Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement"">RFC5556</a>]. |
| 78 |
|
| 79 |
Over Ethernet, TRILL uses two separate Ethertypes to distinguish |
| 80 |
between encapsulation headers, which carry user data, and link-state |
| 81 |
messages, which compute network topology using a protocol based on |
| 82 |
[<a href="#ref-IS-IS" title=""Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473)"">IS-IS</a>] [<a href="./rfc6326" title=""Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS"">RFC6326</a>]. These two protocols must be distinguished from |
| 83 |
one another, and segregated from all other traffic. |
| 84 |
|
| 85 |
In a network where PPP [<a href="./rfc1661" title=""The Point-to-Point Protocol (PPP)"">RFC1661</a>] is used to interconnect routers |
| 86 |
(often over telecommunications links), it may be advantageous to be |
| 87 |
able to bridge between Ethernet segments over those PPP links, and |
| 88 |
thus integrate remote networks with an existing TRILL cloud. The |
| 89 |
existing Bridging Control Protocol (BCP) [<a href="./rfc3518" title=""Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP)"">RFC3518</a>] allows direct |
| 90 |
bridging of Ethernet frames over PPP. However, this mechanism is |
| 91 |
inefficient and inadequate for TRILL, which can be optimized for use |
| 92 |
over PPP links. |
| 93 |
|
| 94 |
To interconnect these devices over PPP links, three protocol numbers |
| 95 |
are needed, and are reserved as follows: |
| 96 |
|
| 97 |
Value (in hex) Protocol Name |
| 98 |
-------------- ------------------------------------- |
| 99 |
005d TRILL Network Protocol (TNP) |
| 100 |
405d TRILL Link State Protocol (TLSP) |
| 101 |
805d TRILL Network Control Protocol (TNCP) |
| 102 |
|
| 103 |
The usage of these three protocols is described in detail in the |
| 104 |
following section. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Carlson & Eastlake Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6361">RFC 6361</a> TRILL over PPP August 2011</span> |
| 111 |
|
| 112 |
|
| 113 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 114 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 115 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 116 |
|
| 117 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. PPP TRILL Negotiation</span> |
| 118 |
|
| 119 |
The TRILL Network Control Protocol (TNCP) is responsible for |
| 120 |
negotiating the use of the TRILL Network Protocol (TNP) and TRILL |
| 121 |
Link State Protocol (TLSP) on a PPP link. TNCP uses the same option |
| 122 |
negotiation mechanism and state machine as described for LCP |
| 123 |
(<a href="./rfc1661#section-4">Section 4 of [RFC1661]</a>). |
| 124 |
|
| 125 |
TNCP packets MUST NOT be exchanged until PPP has reached the Network- |
| 126 |
Layer Protocol phase. Any TNCP packets received when not in that |
| 127 |
phase MUST be silently ignored. |
| 128 |
|
| 129 |
The encapsulated network layer data, carried in TNP packets, and |
| 130 |
topology information, carried in TLSP packets, MUST NOT be sent |
| 131 |
unless TNCP is in the Opened state. If a TNP or TLSP packet is |
| 132 |
received when TNCP is not in the Opened state and LCP is in the |
| 133 |
Opened state, an implementation MUST silently discard the unexpected |
| 134 |
TNP or TLSP packet. |
| 135 |
|
| 136 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. TNCP Packet Format</span> |
| 137 |
|
| 138 |
Exactly one TNCP packet is carried in the PPP Information field, with |
| 139 |
the PPP Protocol field set to hex 805d (TNCP). A summary of the TNCP |
| 140 |
packet format is shown below. The fields are transmitted from left |
| 141 |
to right. |
| 142 |
|
| 143 |
0 1 2 3 |
| 144 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 145 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 146 |
| Code | Identifier | Length | |
| 147 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 148 |
| Data ... |
| 149 |
+-+-+-+-+ |
| 150 |
|
| 151 |
Code |
| 152 |
|
| 153 |
Only LCP Code values 1 through 7 (Configure-Request, |
| 154 |
Configure-Ack, Configure-Nak, Configure-Reject, Terminate-Request, |
| 155 |
Terminate-Ack, and Code-Reject) are used. All other codes SHOULD |
| 156 |
result in a TNCP Code-Reject reply. |
| 157 |
|
| 158 |
Identifier and Length |
| 159 |
|
| 160 |
These are as documented for LCP. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Carlson & Eastlake Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6361">RFC 6361</a> TRILL over PPP August 2011</span> |
| 167 |
|
| 168 |
|
| 169 |
Data |
| 170 |
|
| 171 |
This field contains data formatted as described in <a href="./rfc1661#section-5">Section 5 of |
| 172 |
[RFC1661]</a>. Codes 1-4 use Type-Length-Data sequences, Codes 5 |
| 173 |
and 6 use uninterpreted data, and Code 7 uses a Rejected-Packet, |
| 174 |
all as described in [<a href="./rfc1661" title=""The Point-to-Point Protocol (PPP)"">RFC1661</a>]. |
| 175 |
|
| 176 |
Because no Configuration Options have been defined for TNCP, |
| 177 |
negotiating the use of the TRILL Protocol with IS-IS for the link |
| 178 |
state protocol is the default when no options are specified. A |
| 179 |
future document may specify the use of Configuration Options to |
| 180 |
enable different TRILL operating modes, such as the use of a |
| 181 |
different link state protocol. |
| 182 |
|
| 183 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. TNP Packet Format</span> |
| 184 |
|
| 185 |
When TNCP is in the Opened state, TNP packets are sent by setting the |
| 186 |
PPP Protocol field to hex 005d (TNP) and placing TRILL-encapsulated |
| 187 |
data representing exactly one encapsulated packet in the PPP |
| 188 |
Information field. |
| 189 |
|
| 190 |
A summary of this format is provided below: |
| 191 |
|
| 192 |
0 1 2 3 |
| 193 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 194 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 195 |
| V | R |M|Op-Length| Hop Count | Egress (RB2) Nickname | |
| 196 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 197 |
| Ingress (RB1) Nickname | Inner Destination MAC ... |
| 198 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- |
| 199 |
|
| 200 |
This is identical to the TRILL Ethernet format (<a href="./rfc6325#section-4.1">Section 4.1 of |
| 201 |
[RFC6325]</a>, "Ethernet Data Encapsulation"), except that the Outer MAC |
| 202 |
(Media Access Control) header and Ethertype are replaced by the PPP |
| 203 |
headers and Protocol Field, and the Ethernet Frame Check Sequence |
| 204 |
(FCS) is not present. Both user data and End-Station Address |
| 205 |
Distribution Information (ESADI) packets are encoded in this format. |
| 206 |
|
| 207 |
The PPP FCS follows the encapsulated data on links where the PPP FCS |
| 208 |
is in use. |
| 209 |
|
| 210 |
Unlike the TRILL Ethernet encapsulation, PPP nodes do not have MAC |
| 211 |
addresses, so no outer MAC is present. (High-Level Data Link Control |
| 212 |
(HDLC) addresses MAY be present in some situations; such usage is |
| 213 |
outside the scope of this document.) |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Carlson & Eastlake Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6361">RFC 6361</a> TRILL over PPP August 2011</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. TLSP Packet Format</span> |
| 226 |
|
| 227 |
When TNCP is in the Opened state, TLSP packets are sent by setting |
| 228 |
the PPP Protocol field to hex 405d (TLSP) and placing exactly one |
| 229 |
IS-IS Payload (<a href="./rfc6325#section-4.2.3">Section 4.2.3 of [RFC6325]</a>, "TRILL IS-IS Frames") in |
| 230 |
the PPP Information field. |
| 231 |
|
| 232 |
Note that point-to-point IS-IS links have only an arbitrary circuit |
| 233 |
ID, and do not use MAC addresses for identification. |
| 234 |
|
| 235 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. TRILL PPP Behavior</span> |
| 236 |
|
| 237 |
1. On a PPP link, TRILL always uses point-to-point (P2P) Hellos. |
| 238 |
There is no need for TRILL-Hello frames, nor is per-port |
| 239 |
configuration necessary. P2P Hello messages, per "Point-to-Point |
| 240 |
IS to IS hello PDU" (Section 9.7 of [<a href="#ref-IS-IS" title=""Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473)"">IS-IS</a>]), do not use Neighbor |
| 241 |
IDs in the same manner as on Ethernet. However, per |
| 242 |
<a href="./rfc6325#section-4.2.4.1">Section 4.2.4.1 of [RFC6325]</a>, the three-way IS-IS handshake using |
| 243 |
extended circuit IDs is required on point-to-point links, such |
| 244 |
as PPP. |
| 245 |
|
| 246 |
2. RBridges are never appointed forwarders on PPP links. If an |
| 247 |
implementation includes BCP [<a href="./rfc3518" title=""Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP)"">RFC3518</a>], then it MUST ensure that |
| 248 |
only one of BCP or TNCP is negotiated on a link, and not both. If |
| 249 |
the peer is an RBridge, then there is no need to pass |
| 250 |
unencapsulated frames, as the link can have no TRILL-ignorant peer |
| 251 |
to be concerned about. If the peer is not an RBridge, then TNCP |
| 252 |
negotiation fails and TRILL is not used on the link. |
| 253 |
|
| 254 |
3. An implementation that has only PPP links might have no |
| 255 |
Organizationally Unique Identifier (OUI) that can form an IS-IS |
| 256 |
System ID. Resolving that issue is outside the scope of this |
| 257 |
document; however, it is strongly RECOMMENDED that all TRILL |
| 258 |
implementations have at least one zero-configuration mechanism to |
| 259 |
obtain a valid System ID. Refer to ISO/IEC 10589 [<a href="#ref-IS-IS" title=""Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473)"">IS-IS</a>] |
| 260 |
regarding System ID uniqueness requirements. |
| 261 |
|
| 262 |
4. TRILL MTU-probe and TRILL MTU-ack messages (<a href="./rfc6325#section-4.3.2">Section 4.3.2 of |
| 263 |
[RFC6325]</a>) are not needed on a PPP link. Implementations MUST NOT |
| 264 |
send MTU-probe messages and SHOULD NOT reply to these messages. |
| 265 |
The MTU computed by LCP SHOULD be used instead. Negotiating an |
| 266 |
LCP MTU of at least 1524, to allow for an inner Ethernet payload |
| 267 |
of 1500 octets, is RECOMMENDED. |
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Carlson & Eastlake Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6361">RFC 6361</a> TRILL over PPP August 2011</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 282 |
|
| 283 |
Existing PPP and IS-IS security mechanisms may play important roles |
| 284 |
in a network of RBridges interconnected by PPP links. At the TRILL |
| 285 |
IS-IS layer, the IS-IS authentication mechanism [<a href="./rfc5304" title=""IS-IS Cryptographic Authentication"">RFC5304</a>] [<a href="./rfc5310" title=""IS-IS Generic Cryptographic Authentication"">RFC5310</a>] |
| 286 |
prevents fabrication of link-state control messages. |
| 287 |
|
| 288 |
Not all implementations need to include specific security mechanisms |
| 289 |
at the PPP layer, for example if they are designed to be deployed |
| 290 |
only in cases where the networking environment is trusted or where |
| 291 |
other layers provide adequate security. A complete enumeration of |
| 292 |
possible deployment scenarios and associated threats and options is |
| 293 |
not possible and is outside the scope of this document. For |
| 294 |
applications involving sensitive data, end-to-end security should |
| 295 |
always be considered in addition to link security to provide security |
| 296 |
in depth. |
| 297 |
|
| 298 |
However, in case a PPP layer authentication mechanism is needed to |
| 299 |
protect the establishment of a link and identify a link with a known |
| 300 |
peer, implementation of the PPP Challenge Handshake Authentication |
| 301 |
Protocol (CHAP) [<a href="./rfc1994" title=""PPP Challenge Handshake Authentication Protocol (CHAP)"">RFC1994</a>] is RECOMMENDED. Should greater flexibility |
| 302 |
than that provided by CHAP be required, the Extensible Authentication |
| 303 |
Protocol (EAP) [<a href="./rfc3748" title=""Extensible Authentication Protocol (EAP)"">RFC3748</a>] is a good alternative. |
| 304 |
|
| 305 |
If TRILL-over-PPP packets also require confidentiality, the PPP |
| 306 |
Encryption Control Protocol (ECP) link encryption mechanisms |
| 307 |
[<a href="./rfc1968" title=""The PPP Encryption Control Protocol (ECP)"">RFC1968</a>] can protect the confidentiality and integrity of all |
| 308 |
packets on the PPP link. |
| 309 |
|
| 310 |
And when PPP is run over tunneling mechanisms, such as the Layer Two |
| 311 |
Tunneling Protocol (L2TP) [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>], tunnel security protocols may be |
| 312 |
available. |
| 313 |
|
| 314 |
For general TRILL protocol security considerations, see [<a href="./rfc6325" title=""Routing Bridges (RBridges): Base Protocol Specification"">RFC6325</a>]. |
| 315 |
|
| 316 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span> |
| 317 |
|
| 318 |
IANA has assigned three PPP Protocol field values, 005d, 405d, and |
| 319 |
805d, as described in <a href="#section-1">Section 1</a> of this document. |
| 320 |
|
| 321 |
IANA has created a new "PPP TNCP Configuration Option Types" registry |
| 322 |
in the PPP-Numbers registry, using the same format as the existing |
| 323 |
"PPP LCP Configuration Option Types" registry. |
| 324 |
|
| 325 |
All TNCP Configuration Option Types except 0 are "Unassigned" and |
| 326 |
available for future use, based on "IETF Review", as described in |
| 327 |
<a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a> [<a href="./rfc5226" title="">RFC5226</a>]. Option 0 is allocated for use with Vendor-Specific |
| 328 |
Options, as described in [<a href="./rfc2153" title=""PPP Vendor Extensions"">RFC2153</a>]. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Carlson & Eastlake Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6361">RFC 6361</a> TRILL over PPP August 2011</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span> |
| 338 |
|
| 339 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span> |
| 340 |
|
| 341 |
[<a id="ref-RFC1661">RFC1661</a>] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", |
| 342 |
STD 51, <a href="./rfc1661">RFC 1661</a>, July 1994. |
| 343 |
|
| 344 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 345 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 346 |
|
| 347 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 348 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 349 |
May 2008. |
| 350 |
|
| 351 |
[<a id="ref-RFC6325">RFC6325</a>] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and A. |
| 352 |
Ghanwani, "Routing Bridges (RBridges): Base Protocol |
| 353 |
Specification", <a href="./rfc6325">RFC 6325</a>, July 2011. |
| 354 |
|
| 355 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span> |
| 356 |
|
| 357 |
[<a id="ref-IS-IS">IS-IS</a>] International Organization for Standardization, |
| 358 |
"Intermediate system to Intermediate system intra-domain |
| 359 |
routeing information exchange protocol for use in |
| 360 |
conjunction with the protocol for providing the |
| 361 |
connectionless-mode Network Service (ISO 8473)", ISO/IEC |
| 362 |
10589:2002, Second Edition, November 2002. |
| 363 |
|
| 364 |
[<a id="ref-RFC1968">RFC1968</a>] Meyer, G., "The PPP Encryption Control Protocol (ECP)", |
| 365 |
<a href="./rfc1968">RFC 1968</a>, June 1996. |
| 366 |
|
| 367 |
[<a id="ref-RFC1994">RFC1994</a>] Simpson, W., "PPP Challenge Handshake Authentication |
| 368 |
Protocol (CHAP)", <a href="./rfc1994">RFC 1994</a>, August 1996. |
| 369 |
|
| 370 |
[<a id="ref-RFC2153">RFC2153</a>] Simpson, W., "PPP Vendor Extensions", <a href="./rfc2153">RFC 2153</a>, May 1997. |
| 371 |
|
| 372 |
[<a id="ref-RFC3518">RFC3518</a>] Higashiyama, M., Baker, F., and T. Liao, "Point-to-Point |
| 373 |
Protocol (PPP) Bridging Control Protocol (BCP)", |
| 374 |
<a href="./rfc3518">RFC 3518</a>, April 2003. |
| 375 |
|
| 376 |
[<a id="ref-RFC3748">RFC3748</a>] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. |
| 377 |
Levkowetz, Ed., "Extensible Authentication Protocol |
| 378 |
(EAP)", <a href="./rfc3748">RFC 3748</a>, June 2004. |
| 379 |
|
| 380 |
[<a id="ref-RFC3931">RFC3931</a>] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed., |
| 381 |
"Layer Two Tunneling Protocol - Version 3 (L2TPv3)", |
| 382 |
<a href="./rfc3931">RFC 3931</a>, March 2005. |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Carlson & Eastlake Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6361">RFC 6361</a> TRILL over PPP August 2011</span> |
| 391 |
|
| 392 |
|
| 393 |
[<a id="ref-RFC5304">RFC5304</a>] Li, T. and R. Atkinson, "IS-IS Cryptographic |
| 394 |
Authentication", <a href="./rfc5304">RFC 5304</a>, October 2008. |
| 395 |
|
| 396 |
[<a id="ref-RFC5310">RFC5310</a>] Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R., |
| 397 |
and M. Fanto, "IS-IS Generic Cryptographic |
| 398 |
Authentication", <a href="./rfc5310">RFC 5310</a>, February 2009. |
| 399 |
|
| 400 |
[<a id="ref-RFC5556">RFC5556</a>] Touch, J. and R. Perlman, "Transparent Interconnection of |
| 401 |
Lots of Links (TRILL): Problem and Applicability |
| 402 |
Statement", <a href="./rfc5556">RFC 5556</a>, May 2009. |
| 403 |
|
| 404 |
[<a id="ref-RFC6326">RFC6326</a>] Eastlake, D., Banerjee, A., Dutt, D., Perlman, R., and A. |
| 405 |
Ghanwani, "Transparent Interconnection of Lots of Links |
| 406 |
(TRILL) Use of IS-IS", <a href="./rfc6326">RFC 6326</a>, July 2011. |
| 407 |
|
| 408 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span> |
| 409 |
|
| 410 |
The authors thank Jari Arkko, Stewart Bryant, Ralph Droms, Linda |
| 411 |
Dunbar, Adrian Farrel, Stephen Farrell, Radia Perlman, Mike Shand, |
| 412 |
and William A. Simpson for their comments and help. |
| 413 |
|
| 414 |
Authors' Addresses |
| 415 |
|
| 416 |
James Carlson |
| 417 |
WorkingCode |
| 418 |
25 Essex Street |
| 419 |
North Andover, MA 01845 USA |
| 420 |
|
| 421 |
Phone: +1-781-301-2471 |
| 422 |
EMail: [email protected] |
| 423 |
|
| 424 |
|
| 425 |
Donald E. Eastlake 3rd |
| 426 |
Huawei Technologies |
| 427 |
155 Beaver Street |
| 428 |
Milford, MA 01757 USA |
| 429 |
|
| 430 |
Phone: +1-508-333-2270 |
| 431 |
EMail: [email protected] |
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
Carlson & Eastlake Standards Track [Page 8] |
| 445 |
</pre> |