Description:
|
bgp MODULE-IDENTITY
LAST-UPDATED "200601110000Z"
ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@ietf.org
Jeffrey Haas, Susan Hares (Editors)
NextHop Technologies
825 Victors Way
Suite 100
Ann Arbor, MI 48108-2738
Tel: +1 734 222-1600
Fax: +1 734 222-1602
E-mail: jhaas@nexthop.com
skh@nexthop.com"
DESCRIPTION
"The MIB module for the BGP-4 protocol.
Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4273; see the RFC itself for full legal notices."
REVISION "200601110000Z"
DESCRIPTION
"Changes from RFC 1657:
1) Fixed the definitions of the notifications to make them equivalent to their initial definition in RFC 1269.
2) Added compliance and conformance info.
3) Updated information for the values of bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, bgp4PathAttrASPathSegement.
4) Added additional clarification comments where needed.
5) Noted where objects do not fully reflect the protocol as Known Issues.
6) Updated the DESCRIPTION for the bgp4PathAttrAtomicAggregate object.
7) The following objects have had their DESCRIPTION clause modified to remove the text that suggested (using 'should' verb) initializing the counter to zero on a transition to the established state:
bgpPeerInUpdates, bgpPeerOutUpdates, bgpPeerInTotalMessages, bgpPeerOutTotalMessages
Those implementations that still do this are still compliant with this new wording.
Applications should not assume counters have started at zero.
Published as RFC 4273."
REVISION "199405050000Z"
DESCRIPTION
"Translated to SMIv2 and published as RFC 1657."
REVISION "199110261839Z"
DESCRIPTION
"Initial version, published as RFC 1269."
|
|
