draft-ietf-rsvp-mib-06.txt   draft-ietf-rsvp-mib-07.txt 
RSVP Management Information Base RSVP Management Information Base
draft-ietf-rsvp-mib-06.txt draft-ietf-rsvp-mib-07.txt
Thu May 22 10:17:17 PDT 1997 Tue May 27 11:24:30 PDT 1997
Fred Baker Fred Baker
Cisco Systems Cisco Systems
519 Lado Drive 519 Lado Drive
Santa Barbara, California 93111 Santa Barbara, California 93111
fred@cisco.com fred@cisco.com
John Krawczyk John Krawczyk
skipping to change at page 4, line 42 skipping to change at page 4, line 42
Thus, if a RESV message is received for session Thus, if a RESV message is received for session
224.1.2.3+UDP+4455 with two filter/flow spec groups describing 224.1.2.3+UDP+4455 with two filter/flow spec groups describing
a sender 1.2.3.4 and another sender 1.2.7.8, these two will a sender 1.2.3.4 and another sender 1.2.7.8, these two will
show in the MIB as two separate rows: one for show in the MIB as two separate rows: one for
224.1.2.3+UDP+4455 from 1.2.3.4 and the other for 224.1.2.3+UDP+4455 from 1.2.3.4 and the other for
224.1.2.3+UDP+4455 from 1.2.7.8. 224.1.2.3+UDP+4455 from 1.2.7.8.
4.3. Semantics of Writing the Path and Reservation State 4.3. Semantics of Writing the Path and Reservation State
Databases Databases
The path and reservation state tables are writeable. The The path and reservation state tables are writeable. Writing
objective of writing one of these table is to insert new state into the Path and Reservation State databases allows one to
as if it had been received in a valid Path or Resv message. perform RSVP reservations without authenticating through RSVP
State created in this way by SNMP does not time out and cannot mechanisms, but rather through SNMP mechanisms. State created
be deleted by receiving an RSVP teardown message; it can only in this way by SNMP does not time out and cannot be deleted by
be deleted by SNMP. Deletion is accomplished by writing receiving an RSVP teardown message; it can only be deleted by
'destroy' to the associated Row Status object, and this will SNMP. Deletion is accomplished by writing 'destroy' to the
initiate a teardown message as if the state had timed out. associated Row Status object, and this will initiate a
teardown message as if the state had timed out.
4.4. Intended use of Flow Notifications 4.4. Intended use of Flow Notifications
4.4.1. The lostFlow Notification 4.4.1. The lostFlow Notification
The Lost Flow notification is an asychronous event that The Lost Flow notification is an asychronous event that
signifies that a flow is no longer being observed. signifies that a flow is no longer being observed.
4.4.2. The newFlow Notification 4.4.2. The newFlow Notification
skipping to change at page 6, line 24 skipping to change at page 6, line 24
TimeStamp, TestAndIncr, TimeInterval TimeStamp, TestAndIncr, TimeInterval
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
Port, SessionNumber, SessionType, Port, SessionNumber, SessionType,
Protocol, QosService, intSrvFlowStatus, Protocol, QosService, intSrvFlowStatus,
MessageSize, BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB MessageSize, BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB
ifIndex, InterfaceIndex FROM IF-MIB; ifIndex, InterfaceIndex FROM IF-MIB;
rsvp MODULE-IDENTITY rsvp MODULE-IDENTITY
LAST-UPDATED "9511030500Z" -- Thu May 22 10:17:17 PDT 1997 LAST-UPDATED "9511030500Z" -- Tue May 27 11:24:30 PDT 1997
ORGANIZATION "IETF RSVP Working Group" ORGANIZATION "IETF RSVP Working Group"
CONTACT-INFO CONTACT-INFO
" Fred Baker " Fred Baker
Postal: Cisco Systems Postal: Cisco Systems
519 Lado Drive 519 Lado Drive
Santa Barbara, California 93111 Santa Barbara, California 93111
Tel: +1 805 681 0115 Tel: +1 805 681 0115
E-Mail: fred@cisco.com E-Mail: fred@cisco.com
John Krawczyk John Krawczyk
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/