< draft-ietf-avt-rtp-mib-12.txt   draft-ietf-avt-rtp-mib-13.txt >
Audio Video Transport Group Mark Baugher Audio Video Transport Group Mark Baugher
Internet-Draft Intel Corp. Internet-Draft Intel Corp.
Expires September 6, 2000 Irina Suconick Expires September 6, 2000 Irina Suconick
VideoServer Corp. VideoServer Corp.
Bill Strahm Bill Strahm
Intel Corp. Intel Corp.
March 6, 2000 March 6, 2000
Real-Time Transport Protocol Real-Time Transport Protocol
Management Information Base Management Information Base
<draft-ietf-avt-rtp-mib-12.txt> <draft-ietf-avt-rtp-mib-13.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of section 10 of RFC2026. Internet-Drafts are with all provisions of section 10 of RFC2026. Internet-Drafts are
working documents of the Internet Engineering Task Force working documents of the Internet Engineering Task Force
(IETF), its areas, and its working groups. Note that other (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months. Internet-Drafts may be updated, replaced, or made months. Internet-Drafts may be updated, replaced, or made
obsolete by other documents at any time. It is not obsolete by other documents at any time. It is not
appropriate to use Internet-Drafts as reference material or to appropriate to use Internet-Drafts as reference material or to
cite them other than as a ``working draft'' or ``work in progress.'' cite them other than as a ``working draft'' or ``work in progress.''
To learn the current status of any Internet-Draft, please
check the 1id-abstracts.txt listing contained in the Internet-
Drafts Shadow Directories on ftp.ietf.org, nic.nordu.net,
venera.isi.edu, or munnari.oz.au.
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
skipping to change at page 7, line 19 skipping to change at page 7, line 19
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, Unsigned32 FROM SNMPv2-SMI OBJECT-TYPE, Unsigned32 FROM SNMPv2-SMI
RowStatus, TAddress, RowStatus, TAddress,
TDomain, TestAndIncr, TDomain, TestAndIncr,
TimeStamp, TruthValue FROM SNMPv2-TC TimeStamp, TruthValue FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF
Utf8String FROM SYSAPPL-MIB Utf8String FROM SYSAPPL-MIB
InterfaceIndex FROM IF-MIB; InterfaceIndex FROM IF-MIB;
rtpMIB MODULE-IDENTITY rtpMIB MODULE-IDENTITY
LAST-UPDATED "200006260000Z" -- 26 June 2000 LAST-UPDATED "200012070000Z" -- 12 July 2000
ORGANIZATION ORGANIZATION
"IETF AVT Working Group "IETF AVT Working Group
Email: rem-conf@es.net" Email: rem-conf@es.net"
CONTACT-INFO CONTACT-INFO
"Mark Baugher "Mark Baugher
Postal: Intel Corporation Postal: Intel Corporation
2111 NE 25th Avenue 2111 NE 25th Avenue
Hillsboro, OR 97124 Hillsboro, OR 97124
United States United States
Tel: +1 503 466 8406 Tel: +1 503 466 8406
skipping to change at page 8, line 20 skipping to change at page 8, line 20
an RTP session by a particular sender. an RTP session by a particular sender.
3. Information about RTP streams received on an 3. Information about RTP streams received on an
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 1889, 'RTP: A Transport Protocol for Refer to RFC 1889, 'RTP: A Transport Protocol for
Real-Time Applications,' section 3.0, for definitions." Real-Time Applications,' section 3.0, for definitions."
REVISION "200006260000Z" -- 26 June 2000 REVISION "200012070000Z" -- 12 July 2000
DESCRIPTION "Initial version of this MIB. DESCRIPTION "Initial version of this MIB.
Published as RFC xxx." -- RFC-Editor assigns xxx Published as RFC xxx." -- RFC-Editor assigns xxx
::= { mib-2 xxx } -- to be assigned by IANA ::= { mib-2 xxx } -- to be assigned by IANA
-- --
-- OBJECTS -- OBJECTS
-- --
rtpMIBObjects OBJECT IDENTIFIER ::= { rtpMIB 1 } rtpMIBObjects OBJECT IDENTIFIER ::= { rtpMIB 1 }
rtpConformance OBJECT IDENTIFIER ::= { rtpMIB 2 } rtpConformance OBJECT IDENTIFIER ::= { rtpMIB 2 }
skipping to change at page 9, line 13 skipping to change at page 9, line 13
::= { rtpMIBObjects 1 } ::= { rtpMIBObjects 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 rptSessionDomain, rtpSessionRemAddr, and rtpSessionLocAddr "Maps rtpSessionDomain, rtpSessionRemAddr, and rtpSessionLocAddr
TAddress pairs to an unsigned integer index, TAddress pairs to one or more rtpSessionIndex values, each
rtpSessionInverseIndex, which has the rtpSessionIndex value that describing a row in the rtpSessionTable. This makes it possible
maps to the same rtpSessionDomain, rtpSessionRemAddr, and to retrieve the row(s) in the rtpSessionTable corresponding to a
rtpSessionLocAddr in the rtpSessionTable. rtpSessionIndex can given session without having to walk the entire (potentially
thereby be retrieved based upon the domain and TAddress pair large) table."
that uniquely define an RTP Session."
::= { rtpMIBObjects 2 } ::= { rtpMIBObjects 2 }
rtpSessionInverseEntry OBJECT-TYPE rtpSessionInverseEntry OBJECT-TYPE
SYNTAX RtpSessionInverseEntry SYNTAX RtpSessionInverseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry corresponds to exactly one entry in the "Each entry corresponds to exactly one entry in the
rtpSessionTable - the entry containing the triple, rtpSessionTable - the entry containing the tuple,
rtpSessionDomain, rtpSessionRemAddr, and rtpSessionLocAddr." rtpSessionDomain, rtpSessionRemAddr, rtpSessionLocAddr
and rtpSessionIndex."
INDEX { rtpSessionDomain, rtpSessionRemAddr, rtpSessionLocAddr, INDEX { rtpSessionDomain, rtpSessionRemAddr, rtpSessionLocAddr,
rtpSessionIndex } rtpSessionIndex }
::= { rtpSessionInverseTable 1 } ::= { rtpSessionInverseTable 1 }
RtpSessionInverseEntry ::= SEQUENCE { RtpSessionInverseEntry ::= SEQUENCE {
rtpSessionInverseStartTime TimeStamp rtpSessionInverseStartTime TimeStamp
} }
rtpSessionInverseStartTime OBJECT-TYPE rtpSessionInverseStartTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
skipping to change at page 32, line 27 skipping to change at page 32, line 27
5. Acknowledgements 5. Acknowledgements
The authors wish to thank Bert Wijnen and the participants from the The authors wish to thank Bert Wijnen and the participants from the
ITU SG-16 management effort for their helpful comments. Alan Batie ITU SG-16 management effort for their helpful comments. Alan Batie
and Bill Lewis from Intel also contributed greatly to the RTP MIB and Bill Lewis from Intel also contributed greatly to the RTP MIB
through their review of various drafts of the MIB and their work through their review of various drafts of the MIB and their work
on the implementation of an SNMP RTP Monitor. Stan Naudus from 3Com on the implementation of an SNMP RTP Monitor. Stan Naudus from 3Com
and John Du from Intel contributed to the original RTP MIB design and and John Du from Intel contributed to the original RTP MIB design and
co-authored the original RTP MIB draft documents; much of their work co-authored the original RTP MIB draft documents; much of their work
remains in the current RTP MIB. remains in the current RTP MIB. Bill Fenner provided solid feedback
that improved the quality of the final document.
6. Intellectual Property 6. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
 End of changes. 8 change blocks. 
13 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/