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

BCAST Implementation for NS2

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

                     Obsoleted by bgp4MIBNewNotificationGroup"
            ::= { bgpMIBGroups 5 }

        bgp4MIBNewNotificationGroup NOTIFICATION-GROUP
            NOTIFICATIONS { bgpEstablishedNotification,
                            bgpBackwardTransNotification }
            STATUS current
            DESCRIPTION
                    "A collection of notifications for signaling
                     changes in BGP peer relationships.

                     Obsoletes bgp4MIBNotificationGroup."
            ::= { bgpMIBGroups 6 }



    END



8.  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


Expires May 2002                                               [Page 28]

INTERNET DRAFT                  BGP4-MIB                   November 2001



   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.


9.  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, Juniper Networks
   Rob Coltun, Redback
   Guy Almes, Internet2
   Jeff Honig, BSDi
   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, MFN
   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, Lucent
   Shane Wright, NextHop
   Mike McFadden, Riverstone Networks, Inc.
   Jon Saperia, JDS Consulting, Inc.
   Wayne Tackabury, Gold Wire Technology, Inc.
   Bill Fenner, AT&T Research

   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 wish to acknowledge the fine work  of
   these original authors.





Expires May 2002                                               [Page 29]

INTERNET DRAFT                  BGP4-MIB                   November 2001



10.  References

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


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


[RFC2571]   Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
            for Describing SNMP Management Frameworks", RFC 2571, April
            1999.

[RFC1155]   Rose, M., and K. McCloghrie, "Structure and Identification
            of Management Information for TCP/IP-based Internets", STD
            16, RFC 1155, May 1990.

[RFC1212]   Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
            16, RFC 1212, March 1991.

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

[RFC2578]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Structure of Management
            Information Version 2 (SMIv2)", STD 58, RFC 2578, April
            1999.

[RFC2579]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Textual Conventions for
            SMIv2", STD 58, RFC 2579, April 1999.

[RFC2580]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Conformance Statements for
            SMIv2", STD 58, RFC 2580, April 1999.

[RFC1157]   Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
            Network Management Protocol", STD 15, RFC 1157, May 1990.

[RFC1901]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Introduction to Community-based SNMPv2", RFC 1901, January
            1996.

[RFC1906]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Transport Mappings for Version 2 of the Simple Network
            Management Protocol (SNMPv2)", RFC 1906, January 1996.



Expires May 2002                                               [Page 30]

INTERNET DRAFT                  BGP4-MIB                   November 2001



[RFC2572]   Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
            Processing and Dispatching for the Simple Network Management
            Protocol (SNMP)", RFC 2572, April 1999.

[RFC2574]   Blumenthal, U., and B. Wijnen, "User-based Security Model
            (USM) for version 3 of the Simple Network Management
            Protocol (SNMPv3)", RFC 2574, April 1999.

[RFC1905]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Protocol Operations for Version 2 of the Simple Network
            Management Protocol (SNMPv2)", RFC 1905, January 1996.

[RFC2573]   Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
            RFC 2573, April 1999.

[RFC2575]   Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
            Access Control Model (VACM) for the Simple Network
            Management Protocol (SNMP)", RFC 2575, April 1999.

[RFC2570]   Case, J., Mundy, R., Partain, D., and B. Stewart,
            "Introduction to Version 3 of the Internet-standard Network
            Management Framework", RFC 2570, April 1999.




























Expires May 2002                                               [Page 31]

INTERNET DRAFT                  BGP4-MIB                   November 2001



11.  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
   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.




Expires May 2002                                               [Page 32]

INTERNET DRAFT                  BGP4-MIB                   November 2001



12.  Editors Address

   Jeff Haas, Sue Hares
   NextHop Technologies
   825 Victor's Way, Suite 100
   Ann Arbor, MI 48103
   Phone: [phone]
   Fax:   [phone]
   Email: [e-mail]
          [e-mail]


13.  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
   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 May 2002                                               [Page 33]









                           Table of Contents



1.  Status of this Memo .............................................. 1

2.  Copyright Notice ................................................. 2

3.  Abstract ......................................................... 2

4.  Introduction ..................................................... 2

5.  The SNMP Management Framework .................................... 2

6.  Overview ......................................................... 3

7.  Definitions ...................................................... 5

8.  Intellectual Property ........................................... 28

9.  Acknowledgements ................................................ 29

10. References ...................................................... 30

11. Security Considerations ......................................... 32

12. Editors Address ................................................. 33

13. Full Copyright Statement ........................................ 33





















                                    i