draft-ietf-idr-bgp4-mib-05.txt

BCAST Implementation for NS2

                     This conformance group is obsolete,
                     replaced by bgp4MIBPathAttrGroup."
            ::= { bgpMIBGroups 3 }


        bgp4MIBPathAttrGroup OBJECT-GROUP
            OBJECTS { bgp4PathAttrPeer,
                      bgp4PathAttrIpAddrPrefixLen,
                      bgp4PathAttrIpAddrPrefix,
                      bgp4PathAttrOrigin,
                      bgp4PathAttrASPathSegment,
                      bgp4PathAttrNextHop,
                      bgp4PathAttrMultiExitDisc,
                      bgp4PathAttrLocalPref,
                      bgp4PathAttrAtomicAggregate,
                      bgp4PathAttrAggregatorAS,
                      bgp4PathAttrAggregatorAddr,




Expires June 2001                                             [Page 23]
INTERNET DRAFT                 BGP-4 MIB                   December 2000



                      bgp4PathAttrCalcLocalPref,
                      bgp4PathAttrBest,
                      bgp4PathAttrUnknown }
            STATUS  current
            DESCRIPTION
                    "A collection of objects for managing
                     BGP path entries."
            ::= { bgpMIBGroups 4 }


        bgp4MIBNotificationGroup NOTIFICATION-GROUP
            NOTIFICATIONS { bgpEstablished,
                            bgpBackwardTransition }
            STATUS  current
            DESCRIPTION
                    "A collection of notifications for signaling
                    changes in BGP peer relationships."
            ::= { bgpMIBGroups 5 }


    END

































Expires June 2001                                            [Page 24]
INTERNET DRAFT                 BGP-4 MIB                   December 2000



6. Intellectual Property


   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.



7. Acknowledgements


   We would like to acknowledge the assistance of all the members of the
   Inter-Domain Routing Working Group, and particularly the following
   individuals:


   Yakov Rekhter, cisco Systems
   Rob Coltun, Redback
   Guy Almes, Internet2
   Jeff Honig, Cornell Theory Center
   Marshall T. Rose, Dover Beach Consulting, Inc.
   Dennis Ferguson, Juniper Networks
   Mike Mathis, PSC
   John Krawczyk, Bay Networks
   Curtis Villamizar, Avici
   Dave LeRoy, Pencom Systems
   Paul Traina, Juniper Networks
   Andrew Partan, MFS
   Robert Snyder, cisco Systems
   Dimitry Haskin, Nortel 
   Peder Chr Norgaard, Telebit Communications A/S
   Joel Halpern, CTO Longitude Systems, Inc.
   Nick Thille, RedBack Networks
   Bert Wijnen, IBM
   Shane Wright, NextHop



   The origin of this document is from RFC 1269 "Definitions of Managed
   Objects for the Border Gateway Protocol (Version 3)" written by Steve
   Willis and John Burruss, which was updated by John Chu to support
   BGP-4 in RFC 1657.  The editors wishes to acknowledge the fine work
   of these original authors.




Expires June 2001                                            [Page 25]
INTERNET DRAFT                 BGP-4 MIB                   December 2001



8. References


   [1]  Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC
        1771, March 1995.


   [2]  Rekhter, Y., Gross, P., "Application of the Border Gateway
        Protocol in the Internet", RFC 1772, March 1995.


   [3]  Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
        Describing SNMP Management Frameworks", RFC 2271, Cabletron
        Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
        January 1998


   [4]  Rose, M., and K. McCloghrie, "Structure and Identification of
        Management Information for TCP/IP-based Internets", RFC 1155,
        Performance Systems International, Hughes LAN Systems, May 1990


   [5]  Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC
        1212, Performance Systems International, Hughes LAN Systems,
        March 1991


   [6]  M. Rose, "A Convention for Defining Traps for use with the
        SNMP", RFC 1215, Performance Systems International, March 1991


   [7]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Structure of Management Information for Version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1902, SNMP
        Research,Inc., Cisco Systems, Inc., Dover Beach Consulting,
        Inc., International Network Services, January 1996.


   [8]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
        Conventions for Version 2 of the Simple Network Management
        Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco
        Systems, Inc., Dover Beach Consulting, Inc., International
        Network Services, January 1996.


   [9]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Conformance Statements for Version 2 of the Simple Network
        Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc.,
        Cisco Systems, Inc., Dover Beach Consulting, Inc., International
        Network Services, January 1996.


   [10] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
        Network Management Protocol", RFC 1157, SNMP Research,
        Performance Systems International, Performance Systems
        International, MIT Laboratory for Computer Science, May 1990.


   [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,




Expires June 2001                                            [Page 26]
INTERNET DRAFT                 BGP-4 MIB                   December 2000



        "Introduction to Community-based SNMPv2", RFC 1901, SNMP
        Research, Inc., Cisco Systems, Inc., Dover Beach Consulting,
        Inc., International Network Services, January 1996.


   [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Transport Mappings for Version 2 of the Simple Network
        Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc.,
        Cisco Systems, Inc., Dover Beach Consulting, Inc., International
        Network Services, January 1996.


   [13] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
        Processing and Dispatching for the Simple Network Management
        Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron
        Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
        January 1998.


   [14] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
        for version 3 of the Simple Network Management Protocol
        (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998.


   [15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
        Operations for Version 2 of the Simple Network Management
        Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco
        Systems, Inc., Dover Beach Consulting, Inc., International
        Network Services, January 1996.


   [16] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
        2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
        Systems, January 1998


   [17] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
        Control Model (VACM) for the Simple Network Management Protocol
        (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software,
        Inc., Cisco Systems, Inc., January 1998



9. Security Considerations


   There are a number of management objects defined in this MIB that
   have a MAX-ACCESS clause of read-write:
        bgpPeerAdminStatus
        bgpPeerConnectRetryInterval
        bgpPeerHoldTimeConfigured
        bgpPeerKeepAliveConfigured
        bgpPeerMinASOriginationInterval
        bgpPeerMinRouteAdvertisementInterval


   These objects should be considered sensitive or vulnerable in most




Expires June 2001                                            [Page 27]
INTERNET DRAFT                 BGP-4 MIB                   December 2000



   network environments.  The support for SET operations in a non-secure
   environment without proper protection can have a negative effect on
   network operations.  Incorrect configuration of these parameters may
   cause BGP peer connections to terminate early or to send more routes
   under a flapping condition.


   There are a number of managed objects in this MIB that may be
   considered to contain sensitive information in the operation of a
   network.  For example, a BGP peer's local and remote addresses may be
   sensitive for ISPs who want to keep interface addresses on routers
   confidential to prevent router addresses used for a denial of service
   attack or spoofing.


   Therefore, it may be important in some environments to control read
   access to these objects and possibly to even encrypt the values of
   these object when sending them over the network via SNMP.  Not all
   versions of SNMP provide features for such a secure environment.


   SNMPv1 by itself is not a secure environment.  Even if the network
   itself is secure (for example by using IPSec), even then, there is no
   control as to who on the secure network is allowed to access and
   GET/SET (read/change/create/delete) the objects in this MIB.


   It is recommended that the implementers consider the security
   features as provided by the SNMPv3 framework.  Specifically, the use
   of the User-based Security Model RFC 2274 [14] and the View-based
   Access Control Model RFC 2275 [17] is recommended.


   It is then a customer/user responsibility to ensure that the SNMP
   entity giving access to an instance of this MIB, is properly
   configured to give access to the objects only to those principals
   (users) that have legitimate rights to indeed GET or SET
   (change/create/delete) them.



10. Authors' Address


   Susan Hares
   NextHop Technologies
   517 Williams
   Ann Arbor, MI 48103-4943
   Phone: [phone]
   Fax:   [phone]
   Email: [e-mail]



   Jeff Johnson




Expires August 1999                                            [Page 28]
INTERNET DRAFT                 BGP-4 MIB                   February 1999



   RedBack Networks, Inc.
   1389 Moffett Park Drive
   Sunnyvale, CA  94089
   Phone: [phone]
   Email: [e-mail]



   Steve Willis
   Argon Networks
   25 Porter Road
   Littleton, MA 01450
   Phone: [phone]
   Fax:   [phone]
   Email: [e-mail]



   John Burruss
   Windata Inc.
   543 Great Road
   Littleton MA 01460
   Phone: [phone]
   Email: [e-mail]



   John Chu
   Cosine Communications
   1200 Bridge Parkway
   Redwood City, CA 94065
   Phone: [phone]
   Email: [e-mail]




11. Full Copyright Statement


   Copyright (C) The Internet Society (1999).  All Rights Reserved.


   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than




Expires August 1999                                            [Page 29]
INTERNET DRAFT                 BGP-4 MIB                   February 1999



   English.


   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.


   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.









































Expires June 2001                                            [Page 30]