<?xml version='1.0' encoding='utf-8'?>

<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">

<?rfc sortrefs="yes"?>
<?rfc subcompact="no"?>
<?rfc symrefs="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="3"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>

<rfc category="std" docName="draft-spaghetti-idr-deprecate-8-9-10-01" ipr="trust200902" submissionType="IETF">
    <front>
        <title abbrev="Deprecation Of BGP OPEN Error subcodes">
            Deprecation of BGP OPEN Message Error subcodes 8, 9, and 10.
        </title>

        <author fullname="Job Snijders" initials="J." surname="Snijders">
            <organization abbrev="Fastly">Fastly</organization>
            <address>
                <postal>
                    <city>Amsterdam</city>
                    <country>NL</country>
                </postal>
                <email>job@fastly.com</email>
            </address>
        </author>

        <date />

        <area>Routing</area>
        <workgroup>IDR</workgroup>
        <keyword>BGP</keyword>

        <abstract>
            <t>
                This document requests IANA to mark BGP OPEN Message Error subcodes 8, 9, and 10 as "deprecated".
            </t>
        </abstract>

    </front>

    <middle>
        <section anchor="intro" title="Introduction">
            <t>
                It has been discovered that certain BGP OPEN Message Error subcodes have been used in BGP implementations which have been deployed in the wild while not being assigned by the IANA for such usage.
                Unregistered usage of BGP OPEN Message Error subcodes can lead to increased difficulty when troubleshooting why BGP sessions are torn down.
            </t>

            <t>
                The use of these unregistered values was noticed when the concept of Route Leak Prevention and Detection using Roles in UPDATE and OPEN Messages <xref target="I-D.ietf-idr-bgp-open-policy"/> was initially assigned value 8 by IANA.
                It was subsequently discovered that a widely-deployed <xref target="RFC4271">BGP-4</xref> implementation had released code which used BGP OPEN Message Error Subcode 8.
                As a workaround, a new Early IANA Allocation is to be requested.
            </t>

            <t>
                The squatting of values 8, 9, and 10 has been confirmed by the involved vendors or through source code review.
            </t>
        </section>

        <section anchor="iana" title="IANA Considerations">
            <t>
                Per this document, IANA is requested to mark values 8, 9, and 10 as "deprecated" in the "OPEN Message Error subcodes" registry under the "Border Gateway Protocol (BGP) Parameters" group.
                The marking "deprecated" meaning "use is not recommended" (<xref target="RFC8126" />).
            </t>
        </section>

        <section anchor="security" title="Security Considerations">
            <t>
                There are no meaningful security consequences arising from this registry update.
            </t>
        </section>

    </middle>

    <back>

        <references title="Informative References">
            <?rfc include="reference.RFC.4271.xml"?>
            <?rfc include="reference.RFC.8126.xml"?>
            <?rfc include="reference.I-D.ietf-idr-bgp-open-policy-18.xml"?>
        </references>

<!--
        <section anchor="acknowledgements" title="Acknowledgements">
            <t>
            </t>
        </section>
-->
    </back>

</rfc>
