194 lines
6.2 KiB
XML
194 lines
6.2 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!-- <!DOCTYPE rfc SYSTEM "rfc2629.dtd"> -->
|
|
<?rfc comments="yes"?>
|
|
<?rfc compact="yes"?>
|
|
<?rfc subcompact="no"?>
|
|
<?rfc inline="yes"?>
|
|
<?rfc sortrefs="yes"?>
|
|
<?rfc symrefs="yes"?>
|
|
<?rfc toc="yes"?>
|
|
<?rfc tocdepth="6"?>
|
|
<?rfc tocindent="yes"?>
|
|
<?rfc tocompact="yes"?>
|
|
|
|
<rfc consensus="yes" category="std" submissionType="IETF" docName="draft-ymbk-idr-l3nd-ulpc-01" ipr="trust200902">
|
|
|
|
<front>
|
|
|
|
<title>L3ND Upper-Layer Protocol Configuration</title>
|
|
|
|
<author fullname="Randy Bush" initials="R." surname="Bush">
|
|
<organization>Arrcus & IIJ</organization>
|
|
<address>
|
|
<postal>
|
|
<street>5147 Crystal Springs</street>
|
|
<city>Bainbridge Island</city>
|
|
<region>WA</region>
|
|
<code>98110</code>
|
|
<country>US</country>
|
|
</postal>
|
|
<email>randy@psg.com</email>
|
|
</address>
|
|
</author>
|
|
|
|
<author fullname="Keyur Patel" initials="K." surname="Patel">
|
|
<organization>Arrcus</organization>
|
|
<address>
|
|
<postal>
|
|
<street>2077 Gateway Place, Suite #400</street>
|
|
<city>San Jose</city>
|
|
<region>CA</region>
|
|
<code>95119</code>
|
|
<country>United States of America</country>
|
|
</postal>
|
|
<email>keyur@arrcus.com</email>
|
|
</address>
|
|
</author>
|
|
|
|
<date />
|
|
|
|
<abstract>
|
|
|
|
<t>This document uses the Layer-3 Neighbor Discovery protocol to
|
|
communicate the parameters needed to exchange inter-device Upper
|
|
Layer Protocol Configuration for upper-layer protocols such as the
|
|
BGP family.
|
|
</t>
|
|
|
|
</abstract>
|
|
|
|
<note title="Requirements Language">
|
|
|
|
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
|
|
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
|
|
"OPTIONAL" in this document are to be interpreted as described in
|
|
BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when,
|
|
and only when, they appear in all capitals, as shown here.</t>
|
|
|
|
</note>
|
|
|
|
</front>
|
|
|
|
<middle>
|
|
|
|
<section anchor="intro" title="Introduction">
|
|
|
|
<t>Massive Data Centers (MDCs) which use upper-layer protocols such
|
|
as BGP4 and other routing protocols may use the Layer-3 Neighbor
|
|
Discovery Protocol, L3ND, <xref target="I-D.ymbk-idr-l3nd"/> to
|
|
reveal the inter-device links of the topology. It is desirable for
|
|
devices to facilitate the configuration parameters of those upper
|
|
layer protocols to enable more hands-free configuration. This
|
|
document defines a new L3ND PDU to communicate these Upper-Layer
|
|
Protocol Configuration parameters.</t>
|
|
|
|
</section>
|
|
|
|
<section anchor="terminology" title="Reading and Terminology">
|
|
|
|
<t>The reader is assumed to have read Layer-3 Neighbor Discovery
|
|
<xref target="I-D.ymbk-idr-l3nd"/>. The terminology and PDUs there
|
|
are assumed here.</t>
|
|
|
|
<t>Familiarity with the BGP4 Protocol <xref target="RFC4271"/> is
|
|
assumed.</t>
|
|
|
|
</section>
|
|
|
|
<section anchor="ulps" title="Upper-Layer Protocol Configuration PDU">
|
|
|
|
<t>To communicate parameters required to configure peering and
|
|
operation of Upper-Layer Protocols at IP layer-3 and above, e.g.,
|
|
BGP sessions on a link, a neutral sub-TLV based Upper-Layer Protocol
|
|
PDU is defined as follows:</t>
|
|
|
|
<!--
|
|
protocol "Version = 0:8,Type = 8:8,Payload Length:32,ULPC Type:8,AttrCount:8,Attribute List ...:32"
|
|
-->
|
|
|
|
<figure>
|
|
<artwork>
|
|
0 1 2 3
|
|
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
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
| Version = 0 | Type = 8 | Payload Length |
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
| | ULPC Type | AttrCount |
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
| Attribute List ... |
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
</artwork>
|
|
</figure>
|
|
|
|
<t>The Type and Payload Length are defined in <xref
|
|
target="I-D.ymbk-idr-l3nd"/> apply to this PDU.</t>
|
|
|
|
<t>As the ULPC PDU may contain keying material, e.g. <xref
|
|
target="RFC2385"/>, it SHOULD BE over TLS.</t>
|
|
|
|
<t>Any keying material in the PDU SHOULD BE salted and hashed.</t>
|
|
|
|
<t>The BGP Authentication sub-TLV provides for provisioning MD5,
|
|
which is a quite weak hash, horribly out of fashion, and kills
|
|
puppies. But, like it or not, it has been sufficient against the
|
|
kinds of attacks BGP TCP sessions have endured. So it is what BGP
|
|
deployments use.</t>
|
|
|
|
</section>
|
|
|
|
<section anchor="iana" title="IANA Considerations">
|
|
|
|
<t>This document requests the IANA create a new entry in the L3DL PDU
|
|
Type registry as follows:</t>
|
|
<figure>
|
|
<artwork>
|
|
PDU
|
|
Code PDU Name
|
|
---- -------------------
|
|
9 ULPC
|
|
</artwork>
|
|
</figure>
|
|
|
|
<t>This document requests the IANA create a registry for L3DL ULPC
|
|
Type, which may range from 0 to 255. The name of the registry
|
|
should be L3DL-ULPC-Type. The policy for adding to the registry is
|
|
RFC Required per <xref target="RFC5226"/>, either standards track or
|
|
experimental. The initial entries should be the following:</t>
|
|
<figure>
|
|
<artwork>
|
|
Value Name
|
|
----- -------------------
|
|
0 Reserved
|
|
1 BGP
|
|
2-255 Reserved
|
|
</artwork>
|
|
</figure>
|
|
|
|
</section>
|
|
|
|
<section anchor="acks" title="Acknowledgments">
|
|
|
|
<t>The authors thank Rob Austein and Sue Hares.</t>
|
|
|
|
</section>
|
|
|
|
</middle>
|
|
|
|
<back>
|
|
|
|
<references title="Normative References">
|
|
<?rfc include="reference.RFC.2119.xml"?>
|
|
<?rfc include="reference.RFC.4271.xml"?>
|
|
<!--<?rfc include="reference.RFC.4760.xml"?> -->
|
|
<?rfc include="reference.RFC.5226.xml"?>
|
|
<?rfc include="reference.RFC.8174.xml"?>
|
|
<?rfc include="reference.I-D.ymbk-idr-l3nd.xml"?>
|
|
</references>
|
|
<references title="Informative References">
|
|
<?rfc include="reference.RFC.2385.xml"?>
|
|
<!--<?rfc include="reference.RFC.4808.xml"?> -->
|
|
<!--<?rfc include="reference.RFC.7210.xml"?> -->
|
|
</references>
|
|
|
|
</back>
|
|
</rfc>
|