One document matched: draft-dickson-sidr-route-leak-reqts-00.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "D:/Program%20Files/XML%20Copy%20Editor/dtd/rfc2629.dtd" [
  <!ENTITY rfc2119 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
  <!ENTITY rfc1033 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1033.xml'>
  <!ENTITY rfc1034 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1034.xml'>
  <!ENTITY rfc1035 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml'>
  <!ENTITY rfc2136 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2136.xml'>
  <!ENTITY rfc2181 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2181.xml'>
  <!ENTITY rfc2308 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2308.xml'>
  <!ENTITY rfc2119 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
  <!ENTITY rfc4033 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4033.xml'>
  <!ENTITY rfc4034 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4034.xml'>
  <!ENTITY rfc4035 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4035.xml'>
  <!ENTITY rfc4035 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5011.xml'>
   <!ENTITY rfc5155 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5155.xml'>
]>
<?rfc compact="yes" ?>
<rfc ipr="trust200902" docName="draft-dickson-sidr-route-leak-reqts-00">
<?rfc toc='yes'?>
<front>
    <Creation month="March" year="2012" day="4" />
    <creation month="March" year="2012" day="4" />
    <created month="March" year="2012" day="4" />

    <title abbrev="Route Leak Detection Requirements">
Route Leaks -- Requirements for Detection and Prevention thereof
</title>
    <author initials="B.P." surname="Dickson" fullname="Brian Dickson">
      <organization>
Brian Dickson
</organization>
      <address>
        <postal>
          <street>
703 Palmer Drive,
</street>
          <city>
Herndon
</city>
          <region>
VA
</region>
          <code>
20170
</code>
          <country>
USA
</country>
        </postal>
        <email>
brian.peter.dickson@gmail.com
</email>
      </address>
    </author>
    <date month="March" year="2012"/>
    <area>Internet</area>
    <workgroup>sidr</workgroup>
    <keyword>
DNSOP
</keyword>
    <abstract>
      <t>
      The Border Gateway Protocol, version 4, (BGP4) provides the means to advertise reachability for IP prefixes.
      This reachability information is propagated in a peer-to-peer topology.
      Sometimes routes are announced to peers for which the local peering policy does not permit.
      And sometimes routes are propagated indiscriminantly, once they have been accepted.
    <vspace blankLines="1" />
   This document considers the situations that can lead to routes being leaked, and tries to find acceptable definitions for describing these scenarios.
   <vspace blankLines="1" />
   The purpose of these definitions is to facilitate discussion on what a route leak is, and what the scope of the problem space for route leaks is.
   This, in turn, is intended to inform a requirements document for detection of (and prevention of) route leaks.
   And finally, the definitions and requirements are intended to allow proposed solutions which meet these criteria, and to facilitate evaluation of proposed solutions.
    <vspace blankLines="1" />
   The fundamental objective is to "solve the route leaks problem".
</t>
    </abstract>
    <note title="Author's Note">
    <t>
      Intended Status: Informational.
    </t>
    </note>
  </front>
<middle>
<section title="Introduction">


<section title="Rationale">
<t>
   This document is a placeholder, version 00 to meet the cut-off deadline.
</t>
</section> 
<section title="Requirements">
<t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
      "OPTIONAL" in this document are to be interpreted as described in
      <xref target="RFC2119" />.
</t>
</section>
<section title="Terminology">
<t>
The reader is assumed to be familiar with the IETF.</t>
</section>
</section>
<section title="Security Considerations">
<t>
None per se.
</t>
</section>
<section title="IANA Considerations">
<t>
   This document contains no IANA-specific material.
</t>
</section>
<section title="Acknowledgements">
<t>
To be added later.
</t>
</section>
</middle>
  <back>
    <references title="Normative References">
      &rfc1033;
      &rfc1034;
      &rfc1035;
      &rfc2136;
      &rfc2181;
      &rfc2308;
      &rfc4033;
      &rfc4034;
      &rfc4035;
      &rfc5011;
      &rfc5155;
    </references>
    <references title="Informative References">
    &rfc2119;
    </references>
  </back>
</rfc>