--- 1/draft-ietf-grow-bmp-11.txt 2015-07-22 02:15:36.933311410 -0700 +++ 2/draft-ietf-grow-bmp-12.txt 2015-07-22 02:15:37.025313625 -0700 @@ -1,21 +1,21 @@ Network Working Group J. Scudder, Ed. Internet-Draft Juniper Networks Intended status: Standards Track R. Fernando -Expires: January 21, 2016 Cisco Systems +Expires: January 23, 2016 Cisco Systems S. Stuart Google - July 20, 2015 + July 22, 2015 BGP Monitoring Protocol - draft-ietf-grow-bmp-11 + draft-ietf-grow-bmp-12 Abstract This document defines a protocol, BMP, that can be used to monitor BGP sessions. BMP is intended to provide a more convenient interface for obtaining route views for research purpose than the screen- scraping approach in common use today. The design goals are to keep BMP simple, useful, easily implemented, and minimally service- affecting. BMP is not suitable for use as a routing protocol. @@ -27,21 +27,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on January 21, 2016. + This Internet-Draft will expire on January 23, 2016. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -873,22 +873,23 @@ support regardless. If the router receives a withdraw for a prefix even before the peer dump procedure visits that prefix, then the router would clean up that route from its internal state and will not forward it to the monitoring station. In this case, the monitoring station may receive a bogus withdraw it can safely ignore. 10. IANA Considerations - IANA is requested to create the registries for the following BMP - parameters. + IANA is requested to create registries for the following BMP + parameters, to be organized in a new group "BGP Monitoring Protocol + (BMP) Parameters": 10.1. BMP Message Types This document defines seven message types for transferring BGP messages between cooperating systems (Section 4): o Type 0: Route Monitor o Type 1: Statistics Report o Type 2: Peer Down Notification o Type 3: Peer Up Notification