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

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/