<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-operational-message" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-operational-message-00">
   <front>
      <title>BGP OPERATIONAL Message</title>
      <author initials="D." surname="Freedman" fullname="David Freedman">
         <organization>Claranet</organization>
      </author>
      <author initials="R." surname="Raszuk" fullname="Robert Raszuk">
         <organization>NTT MCL Inc.</organization>
      </author>
      <author initials="R." surname="Shakir" fullname="Rob Shakir">
         <organization>BT</organization>
      </author>
      <date month="March" day="13" year="2012" />
      <abstract>
	 <t>   The BGP Version 4 routing protocol (RFC4271) is now used in many
   ways, crossing boundaries of administrative and technical
   responsibility.

   The protocol lacks an operational messaging plane which could be
   utilised to diagnose, troubleshoot and inform upon various conditions
   across these boundaries, securely, during protocol operation, without
   disruption.

   This document proposes a new BGP message type, the OPERATIONAL
   message, which can be used to effect such a messaging plane for use
   both between and within Autonomous Systems.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-operational-message-00" />
   
</reference>
