30 likes | 133 Views
Frame Relay Service MIB Working Group. Tuesday, December 12 2000, 1700-1800 Chair: Andrew Malis, Vivace Networks Andy.Malis@vivacenetworks.com Guest Chair: Ken Rehbehn, krehbehn@megisto.com discussion: frnetmib@sunroof.eng.sun.com
E N D
Frame Relay Service MIB Working Group Tuesday, December 12 2000, 1700-1800 Chair: Andrew Malis, Vivace Networks Andy.Malis@vivacenetworks.com Guest Chair: Ken Rehbehn, krehbehn@megisto.com discussion: frnetmib@sunroof.eng.sun.com (un)subscribe requests to: frnetmib-request@ sunroof.eng.sun.com Email archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/
Agenda 1. Administrivia, current WG status 2. Ken Rehbehn, quick overview of the final revisions to RFC 3020 (was draft-ietf-frnetmib-mfrmib-04.txt), Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function 3. Rob Steinberger and Orly Nicklass, draft-ietf-frnetmib-frmrelay-service-02.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions (FRF.13) • Rob Steinberger and Orly Nicklass, Rob Steinberger and Orly Nicklass, draft-ietf-frnetmib-frsi-00.txt, Frame Relay Circuit Interface MIB • Open discussion
Other WG Status • Three New RFCs since last meeting: • RFC 2954, Definitions of Managed Objects for Frame Relay Service • RFC 2955, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function • RFC 3020, Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function • Expect WG to go into maintenance mode (i.e. just be the email list) once frmrelay-service and frsi MIBs complete