randy/draft-l3dl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

section out iana considerations

Browse source
This commit is contained in:
Randy Bush 2019-06-03 12:46:30 -07:00
parent 86f737a404
commit edbdca05b3
1 changed files with 90 additions and 85 deletions
Download patch file Download diff file Expand all files Collapse all files

169
draft-ietf-lsvr-l3dl.xml
View file

@ -525,21 +525,8 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
<t>The fields of the basic L3DL header are as follows:
<list style="hanging">
<t hangText="Type:">An integer differentiating PDU payload types
<list style="empty">
<?rfc subcompact="yes"?>
<t>0 – HELLO</t>
<t>1 - OPEN</t>
<t>2 - KEEPALIVE</t>
<t>3 - ACK</t>
<t>4 - IPv4 Announcement</t>
<t>5 - IPv6 Announcement</t>
<t>6 - MPLS IPv4 Announcement</t>
<t>7 - MPLS IPv6 Announcement</t>
<t>8-254 Reserved</t>
<t>255 - VENDOR</t>
<?rfc subcompact="no"?>
</list></t>
<t hangText="Type:">An integer differentiating PDU payload types.
See <xref target="iana-types"/>.</t>
<t hangText="Payload Length:">Total number of octets in the
Payload field.</t>
@ -1450,76 +1437,94 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
<section anchor="iana" title="IANA Considerations">
<t>This document requests the IANA create a registry for L3DL PDU
Type, which may range from 0 to 255. The name of the registry
should be L3DL-PDU-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>
PDU
Code PDU Name
---- -------------------
0 HELLO
1 OPEN
2 KEEPALIVE
3 ACK
4 IPv4 Announcement
5 IPv6 Announcement
6 MPLS IPv4 Announcement
7 MPLS IPv6 Announcement
8-254 Reserved
255 VENDOR
</artwork>
</figure>
<section anchor="iana-types" title="PDU Types">
<t>This document requests the IANA create a registry for L3DL
Signature Type, AKA Sig Type, which may range from 0 to 255. The
name of the registry should be L3DL-Signature-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>
Number Name
------ -------------------
0 Null
1-255 Reserved
</artwork>
</figure>
<t>This document requests the IANA create a registry for L3DL PDU
Type, which may range from 0 to 255. The name of the registry
should be L3DL-PDU-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>
PDU
Code PDU Name
---- -------------------
0 HELLO
1 OPEN
2 KEEPALIVE
3 ACK
4 IPv4 Announcement
5 IPv6 Announcement
6 MPLS IPv4 Announcement
7 MPLS IPv6 Announcement
8-254 Reserved
255 VENDOR
</artwork>
</figure>
<t>This document requests the IANA create a registry for L3DL PL
Flag Bits, which may range from 0 to 7. The name of the registry
should be L3DL-PL-Flag-Bits. 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>
Bit Bit Name
---- -------------------
0 Primary
1 Loopback
2-7 Reserved
</artwork>
</figure>
</section>
<t>This document requests the IANA create a registry for L3DL Error
Codes, a 16 bit integer. The name of the registry should be
L3DL-Error-Codes. 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>
Error
Code Error Name
---- -------------------
0 No Error
1 Logical Link Addressing Conflict
2 Authorization Failure in OPEN
3 Signature Failure in PDU
4 Announce/Withdraw Error
</artwork>
</figure>
<section anchor="iana-sigtype" title="Signature Type">
<t>This document requests the IANA create a registry for L3DL
Signature Type, AKA Sig Type, which may range from 0 to 255. The
name of the registry should be L3DL-Signature-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>
Number Name
------ -------------------
0 Null
1-255 Reserved
</artwork>
</figure>
</section>
<section anchor="iana-flags" title="Flag Bits">
<t>This document requests the IANA create a registry for L3DL PL
Flag Bits, which may range from 0 to 7. The name of the registry
should be L3DL-PL-Flag-Bits. 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>
Bit Bit Name
---- -------------------
0 Announce/Withdraw (ann == 0)
1 Primary
2 Underlay/Overlay (under == 0)
3 Loopback
4-7 Reserved
</artwork>
</figure>
</section>
<section anchor="iana-error" title="Error Codes">
<t>This document requests the IANA create a registry for L3DL Error
Codes, a 16 bit integer. The name of the registry should be
L3DL-Error-Codes. 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>
Error
Code Error Name
---- -------------------
0 No Error
1 Logical Link Addressing Conflict
2 Authorization Failure in OPEN
3 Signature Failure in PDU
4 Announce/Withdraw Error
</artwork>
</figure>
</section>
</section>