draft-ietf-avt-mib-rtp-bis-00.txt   draft-ietf-avt-mib-rtp-bis-01.txt 
Internet Engineering Task Force A. Clark Internet Engineering Task Force A. Clark
Internet-Draft Telchemy Incorporated Internet-Draft Telchemy Incorporated
Expires: 18 August 2006 A. Pendleton Expires: 22 December 2006 A. Pendleton
Nortel Nortel
February 2006 Real-time Transport Protocol (RTP) MIB Version 2
draft-ietf-avt-mib-rtp-bis-01
Real Time Protocol (RTP) MIB Version 2
draft-ietf-avt-mib-rtp-bis-00
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on 18 August 2006. This Internet-Draft will expire on 22 December 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines objects for managing Real-Time Transport In particular, it defines objects for managing Real-Time Transport
skipping to change at page 5, line 42 skipping to change at page 5, line 42
RTP session by a particular receiver from a RTP session by a particular receiver from a
particular sender. particular sender.
There are two types of RTP Systems, RTP hosts and There are two types of RTP Systems, RTP hosts and
RTP monitors. As described below, certain objects RTP monitors. As described below, certain objects
are unique to a particular type of RTP System. An are unique to a particular type of RTP System. An
RTP host may also function as an RTP monitor. RTP host may also function as an RTP monitor.
Refer to RFC 3550, 'RTP: A Transport Protocol for Refer to RFC 3550, 'RTP: A Transport Protocol for
Real-Time Applications,' section 3.0, for definitions." Real-Time Applications,' section 3.0, for definitions."
REVISION "200602260000Z" -- 26 February 2006 REVISION "200602260000Z" -- 26 February 2006
DESCRIPTION "Version 2 of this MIB. DESCRIPTION "Version 2 of this MIB.
Published as draft-ietf-avt-mib-rtp-bis-00" Published as draft-ietf-avt-mib-rtp-bis-01"
::= { mib-2 nnn } ::= { mib-2 nnn }
-- OBJECTS -- OBJECTS
-- --
rtpMIBV2Objects OBJECT IDENTIFIER ::= { rtpMIBV2 1 } rtpMIBV2Objects OBJECT IDENTIFIER ::= { rtpMIBV2 1 }
rtpConformance OBJECT IDENTIFIER ::= { rtpMIBV2 2 } rtpConformance OBJECT IDENTIFIER ::= { rtpMIBV2 2 }
-- SESSION NEW INDEX -- SESSION NEW INDEX
-- --
rtpSessionNewIndex OBJECT-TYPE rtpSessionNewIndex OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX TestAndIncr
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to assign values to rtpSessionIndex "This object is used to assign values to rtpSessionIndex
as described in 'Textual Conventions for SMIv2'. For an RTP as described in 'Textual Conventions for SMIv2'. For an RTP
system that supports the creation of rows, the network manager system that supports the creation of rows, the network manager
would read the object, and then write the value back in would read the object, and then write the value back in
the Set that creates a new instance of rtpSessionEntry. If the Set that creates a new instance of rtpSessionEntry. If
skipping to change at page 6, line 26 skipping to change at page 6, line 19
would read the object, and then write the value back in would read the object, and then write the value back in
the Set that creates a new instance of rtpSessionEntry. If the Set that creates a new instance of rtpSessionEntry. If
the Set fails with the code 'inconsistentValue,' then the the Set fails with the code 'inconsistentValue,' then the
process must be repeated; If the Set succeeds, then the object process must be repeated; If the Set succeeds, then the object
is incremented, and the new instance is created according to is incremented, and the new instance is created according to
the manager's directions. However, if the RTP agent is not the manager's directions. However, if the RTP agent is not
acting as a monitor, only the RTP agent may create conceptual acting as a monitor, only the RTP agent may create conceptual
rows in the RTP session table." rows in the RTP session table."
::= { rtpMIBV2Objects 1 } ::= { rtpMIBV2Objects 1 }
-- SESSION INVERSE TABLE -- SESSION INVERSE TABLE
-- --
rtpSessionInverseTable OBJECT-TYPE rtpSessionInverseTable OBJECT-TYPE
SYNTAX SEQUENCE OF RtpSessionInverseEntry SYNTAX SEQUENCE OF RtpSessionInverseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maps source and destination address to or more rtpSessionIndex "Maps source and destination address to or more rtpSessionIndex
values describing rows in the rtpSessionTable. This allows values describing rows in the rtpSessionTable. This allows
rows to be retrieved in the rtpSessionTable corresponding to a rows to be retrieved in the rtpSessionTable corresponding to a
skipping to change at page 7, line 14 skipping to change at page 7, line 7
rtpSessionInverseStartTime OBJECT-TYPE rtpSessionInverseStartTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local time at which this row was "The local time at which this row was
created." created."
::= { rtpSessionInverseEntry 1 } ::= { rtpSessionInverseEntry 1 }
-- SESSION TABLE -- SESSION TABLE
-- --
rtpSessionTable OBJECT-TYPE rtpSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF RtpSessionEntry SYNTAX SEQUENCE OF RtpSessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"There's one entry in rtpSessionTable for each RTP session "There's one entry in rtpSessionTable for each RTP session
on which packets are being sent, received, and/or on which packets are being sent, received, and/or
monitored." monitored."
skipping to change at page 13, line 5 skipping to change at page 13, line 27
rtpSessionMaxNumEntries OBJECT-TYPE rtpSessionMaxNumEntries OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of entries that can be supported "The maximum number of entries that can be supported
in this table." in this table."
::= { rtpSessionEntry 24 } ::= { rtpSessionEntry 24 }
-- SENDER INVERSE TABLE -- SENDER INVERSE TABLE
-- --
rtpSenderInverseTable OBJECT-TYPE rtpSenderInverseTable OBJECT-TYPE
SYNTAX SEQUENCE OF RtpSenderInverseEntry SYNTAX SEQUENCE OF RtpSenderInverseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maps rtpSenderIPAddress, rtpSessionIndex, to the rtpSenderSSRC "Maps rtpSenderIPAddress, rtpSessionIndex, to the rtpSenderSSRC
index of the rtpSenderTable. This table allows management index of the rtpSenderTable. This table allows management
applications to find entries sorted by Sender IP address rather applications to find entries sorted by Sender IP address rather
skipping to change at page 13, line 48 skipping to change at page 14, line 37
rtpSenderInverseStartTime OBJECT-TYPE rtpSenderInverseStartTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time at which this row was "The time at which this row was
created." created."
::= { rtpSenderInverseEntry 1 } ::= { rtpSenderInverseEntry 1 }
-- SENDERS TABLE -- SENDERS TABLE
-- --
rtpSenderTable OBJECT-TYPE rtpSenderTable OBJECT-TYPE
SYNTAX SEQUENCE OF RtpSenderEntry SYNTAX SEQUENCE OF RtpSenderEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of information about a sender or senders to an RTP "Table of information about a sender or senders to an RTP
Session. RTP sending hosts MUST have an entry in this table Session. RTP sending hosts MUST have an entry in this table
for each stream being sent. RTP receiving hosts MAY have an for each stream being sent. RTP receiving hosts MAY have an
skipping to change at page 22, line 13 skipping to change at page 23, line 13
::= { rtpRcvrEntry 16 } ::= { rtpRcvrEntry 16 }
rtpRcvrStartTime OBJECT-TYPE rtpRcvrStartTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time at which this row was created." "The time at which this row was created."
::= { rtpRcvrEntry 17 } ::= { rtpRcvrEntry 17 }
-- MODULE GROUPS -- MODULE GROUPS
-- --
-- There are two types of RTP Systems, RTP hosts and RTP Monitors. -- There are two types of RTP Systems, RTP hosts and RTP Monitors.
-- Thus there are three kinds of objects: 1) Objects common to both -- Thus there are three kinds of objects: 1) Objects common to both
-- kinds of systems, 2) Objects unique to RTP Hosts and 3) Objects -- kinds of systems, 2) Objects unique to RTP Hosts and 3) Objects
-- unique to RTP Monitors. There is a fourth group, 4) Objects that -- unique to RTP Monitors. There is a fourth group, 4) Objects that
-- SHOULD be implemented by Multicast hosts and RTP Monitors -- SHOULD be implemented by Multicast hosts and RTP Monitors
rtpGroups OBJECT IDENTIFIER ::= { rtpConformance 1 } rtpGroups OBJECT IDENTIFIER ::= { rtpConformance 1 }
rtpSystemGroup OBJECT-GROUP rtpSystemGroup OBJECT-GROUP
OBJECTS { OBJECTS {
rtpSessionSessionIdentifier, rtpSessionSessionIdentifier,
skipping to change at page 23, line 55 skipping to change at page 24, line 55
OBJECTS { OBJECTS {
rtpSessionInverseStartTime, rtpSessionInverseStartTime,
rtpSenderInverseStartTime, rtpSenderInverseStartTime,
rtpRcvrInverseStartTime rtpRcvrInverseStartTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used in the Inverse Lookup Tables." "Objects used in the Inverse Lookup Tables."
::= { rtpGroups 4 } ::= { rtpGroups 4 }
-- Compliance -- Compliance
-- --
rtpCompliances OBJECT IDENTIFIER ::= { rtpConformance 2 } rtpCompliances OBJECT IDENTIFIER ::= { rtpConformance 2 }
rtpHostCompliance MODULE-COMPLIANCE rtpHostCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Host implementations MUST comply." "Host implementations MUST comply."
MODULE RTP-MIB MODULE RTP-MIB
MANDATORY-GROUPS { MANDATORY-GROUPS {
rtpSystemGroup, rtpSystemGroup,
rtpHostGroup rtpHostGroup
} }
GROUP rtpMonitorGroup GROUP rtpMonitorGroup
DESCRIPTION DESCRIPTION
"Host systems my optionally support row creation and deletion. "Host systems my optionally support row creation and deletion.
skipping to change at page 29, line 15 skipping to change at page 31, line 27
9. Informative References 9. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and Stewart, B., [RFC3410] Case, J., Mundy, R., Partain, D. and Stewart, B.,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for Internet
Standard Management Framework", RFC 3410, December 2002 Standard Management Framework", RFC 3410, December 2002
10. Authors' Addresses 10. Authors' Addresses
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
3360 Martins Farm Road, Ste 200 2905 Premiere Parkway, Suite 280
Suwanee, Georgia 30024 Duluth, Georgia 30097
U.S.A. U.S.A.
Email: alan@telchemy.com Email: alan@telchemy.com
Amy Pendleton Amy Pendleton
Nortel Nortel
2380 Performance Drive 2380 Performance Drive
Richardson, Texas 75081 Richardson, Texas 75081
U.S.A. U.S.A.
Email: aspen@nortel.com Email: aspen@nortel.com
 End of changes. 9 change blocks. 
11 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/