NextHop Technologies, Inc.

BGP-4 MIB Status, IETF 56

Jeffrey Haas

NextHop Technologies, Inc.

V1 MIB

• Last Call has been issued.• Many editorial comments have been received.• New SNMP boiler plates need to be incorporated.• No structural changes made, however a large

amount of text will be altered due to the boilerplate. Do we need to do another last call after the changes?

• Changes will be incorporated within 2 weeks after end of this IETF. Promise!

NextHop Technologies, Inc.

V1 MIB, cont.

• As part of the standardization process, we need implementation reports. We did this before, we’ll need to do it again.

• Please e-mail jhaas@nexthop.com so we can coordinate the report for your implementation.

NextHop Technologies, Inc.

V2 MIB

• As a side-effect of the V1 MIB Last Call, we have received new attention on the V2 MIB. Thanks for the feedback.

• V2 MIB needs to incorporate further work to incorporate latest changes to BGP draft, especially the FSM.

• We need more reviewers.• A MIB-2 OID will be pursued as part of the latest

changes.

NextHop Technologies, Inc.

V2 MIB, cont.

• The index method for RFC-based extensions has been questioned. We will pursue further discussion of this in the mailing list.