smilint output for ./RTP-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 1 |
| warning | 3 |
| Message Types |
|---|
| Type | Count |
|---|
| index-exceeds-too-large (warning) | 3 |
| object-identifier-not-prefix (error) | 1 |
Messages:
RTP-MIB
1: -- extracted from draft-ietf-avt-mib-rtp-bis-01.txt
2: -- at Thu Jun 29 06:06:37 2006
3:
4: RTP-MIB DEFINITIONS ::= BEGIN
5: IMPORTS
6: Counter32, Counter64, Gauge32, mib-2, Integer32,
7: MODULE-IDENTITY,
8: OBJECT-TYPE, Unsigned32 FROM SNMPv2-SMI
9: InetAddressType, InetAddress,
10: InetPortNumber FROM INET-ADDRESS-MIB
11: RowStatus, TestAndIncr,
12: TruthValue, DateAndTime FROM SNMPv2-TC
13: OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF
14: Utf8String FROM SYSAPPL-MIB
15: InterfaceIndex FROM IF-MIB;
16:
17: rtpMIBV2 MODULE-IDENTITY
18: LAST-UPDATED "200602260000Z" -- 26 February 2006
19: ORGANIZATION
20: "IETF AVT Working Group
21: Email: avt@ietf.org"
22: CONTACT-INFO
23: "Alan Clark
24: Telchemy
25: 3360 Martins Farm Rd
26: Suwanee, GA 20024
27: United States
28: Email: alan@telchemy.com
29:
30: Amy Pendleton
31: Nortel
32: 2380 Performance Drive
33: Richardson, TX 75081
34: Email: aspen@nortel.com"
35:
36: DESCRIPTION
37: "The managed objects of RTP systems. The MIB is
38: structured around three types of information.
39: 1. General information about RTP sessions such
40: as the session address.
41: 2. Information about RTP streams being sent to
42: an RTP session by a particular sender.
43: 3. Information about RTP streams received on an
44: RTP session by a particular receiver from a
45: particular sender.
46: There are two types of RTP Systems, RTP hosts and
47: RTP monitors. As described below, certain objects
48: are unique to a particular type of RTP System. An
49: RTP host may also function as an RTP monitor.
50: Refer to RFC 3550, 'RTP: A Transport Protocol for
51: Real-Time Applications,' section 3.0, for definitions."
52: REVISION "200602260000Z" -- 26 February 2006
53: DESCRIPTION "Version 2 of this MIB.
54: Published as draft-ietf-avt-mib-rtp-bis-01"
55: ::= { mib-2 nnn }
55: error -
Object identifier element `nnn' name only allowed as first element
56:
57: -- OBJECTS
58: --
59:
60: rtpMIBV2Objects OBJECT IDENTIFIER ::= { rtpMIBV2 1 }
61: rtpConformance OBJECT IDENTIFIER ::= { rtpMIBV2 2 }
62:
63: -- SESSION NEW INDEX
64: --
65:
66: rtpSessionNewIndex OBJECT-TYPE
67: SYNTAX TestAndIncr
68: MAX-ACCESS read-write
69: STATUS current
70: DESCRIPTION
71: "This object is used to assign values to rtpSessionIndex
72: as described in 'Textual Conventions for SMIv2'. For an RTP
73: system that supports the creation of rows, the network manager
74: would read the object, and then write the value back in
75: the Set that creates a new instance of rtpSessionEntry. If
76: the Set fails with the code 'inconsistentValue,' then the
77: process must be repeated; If the Set succeeds, then the object
78: is incremented, and the new instance is created according to
79: the manager's directions. However, if the RTP agent is not
80: acting as a monitor, only the RTP agent may create conceptual
81: rows in the RTP session table."
82: ::= { rtpMIBV2Objects 1 }
83:
84: -- SESSION INVERSE TABLE
85: --
86: rtpSessionInverseTable OBJECT-TYPE
87: SYNTAX SEQUENCE OF RtpSessionInverseEntry
88: MAX-ACCESS not-accessible
89: STATUS current
90: DESCRIPTION
91: "Maps source and destination address to or more rtpSessionIndex
92: values describing rows in the rtpSessionTable. This allows
93: rows to be retrieved in the rtpSessionTable corresponding to a
94: given session without having to walk the entire (potentially
95: large) table."
96: ::= { rtpMIBV2Objects 2 }
97:
98: rtpSessionInverseEntry OBJECT-TYPE
98: warning -
warning: index of row `rtpSessionInverseEntry' can exceed OID size limit by 393 subidentifier(s)
99: SYNTAX RtpSessionInverseEntry
100: MAX-ACCESS not-accessible
101: STATUS current
102: DESCRIPTION
103: "Each entry corresponds to exactly one entry in the
104: rtpSessionTable."
105: INDEX { rtpSessionSourceIPaddress, rtpSessionSourceRTPport,
106: rtpSessionDestIPaddress, rtpSessionDestRTPport,
107: rtpSessionCallState, rtpSessionIndex }
108: ::= { rtpSessionInverseTable 1 }
109:
110: RtpSessionInverseEntry ::= SEQUENCE {
111: rtpSessionInverseStartTime DateAndTime
112: }
113:
114: rtpSessionInverseStartTime OBJECT-TYPE
115: SYNTAX DateAndTime
116: MAX-ACCESS read-only
117: STATUS current
118: DESCRIPTION
119: "The local time at which this row was
120: created."
121: ::= { rtpSessionInverseEntry 1 }
122:
123: -- SESSION TABLE
124: --
125: rtpSessionTable OBJECT-TYPE
126: SYNTAX SEQUENCE OF RtpSessionEntry
127: MAX-ACCESS not-accessible
128: STATUS current
129: DESCRIPTION
130: "There's one entry in rtpSessionTable for each RTP session
131: on which packets are being sent, received, and/or
132: monitored."
133: ::= { rtpMIBV2Objects 3 }
134:
135: rtpSessionEntry OBJECT-TYPE
136: SYNTAX RtpSessionEntry
137: MAX-ACCESS not-accessible
138: STATUS current
139: DESCRIPTION
140: "Data in rtpSessionTable uniquely identify an RTP session. A
141: host RTP agent MUST create a read-only row for each session to
142: which packets are being sent or received. Rows MUST be created
143: by the RTP Agent at the start of a session when one or more
144: senders or receivers are observed. An RTP
145: session SHOULD be monitored to create management information on
146: all RTP streams being sent or received when the
147: rtpSessionMonitor has the TruthValue of 'true(1)'. An RTP
148: monitor SHOULD permit row creation with the side effect of
149: causing the RTP System to join the multicast session for the
150: purposes of gathering management information (additional
151: conceptual rows are created in the rtpRcvrTable and
152: rtpSenderTable). Thus, rtpSessionTable rows SHOULD be created
153: for RTP session monitoring purposes. Rows created by a
154: management application SHOULD be deleted via SNMP operations by
155: management applications. Rows created by management operations
156: are deleted by management operations by setting
157: rtpSessionRowStatus to 'destroy(6)'."
158: INDEX { rtpSessionCallState, rtpSessionIndex }
159: ::= { rtpSessionTable 1 }
160:
161: RtpSessionEntry ::= SEQUENCE {
162: rtpSessionCallState INTEGER,
163: rtpSessionIndex Integer32,
164: rtpSessionSessionIdentifier OCTET STRING,
165: rtpSessionStartTime DateAndTime,
166: rtpSessionStopTime DateAndTime,
167: rtpSessionSourceIPtype InetAddressType,
168: rtpSessionSourceIPaddress InetAddress,
169: rtpSessionSourceRTPport InetPortNumber,
170: rtpSessionSourceRTCPport InetPortNumber,
171: rtpSessionDestIPtype InetAddressType,
172: rtpSessionDestIPaddress InetAddress,
173: rtpSessionDestRTPport InetPortNumber,
174: rtpSessionDestRTCPport InetPortNumber,
175: rtpSessionSrceIdenType INTEGER,
176: rtpSessionSrceIdentifier OCTET STRING,
177: rtpSessionDestIdenType INTEGER,
178: rtpSessionDestIdentifier OCTET STRING,
179: rtpSessionIfIndex InterfaceIndex,
180: rtpSessionMonitor TruthValue,
181: rtpSessionSenderJoins Counter32,
182: rtpSessionReceiverJoins Counter32,
183: rtpSessionByes Counter32,
184: rtpSessionRowStatus RowStatus,
185: rtpSessionMaxNumEntries Integer32
186: }
187:
188: rtpSessionCallState OBJECT-TYPE
189: SYNTAX INTEGER { active(1),
190: completed(2)
191: }
192: MAX-ACCESS not-accessible
193: STATUS current
194: DESCRIPTION
195: "Index for this session within the Session ID
196: table. The value of this parameter shall be 2 if the
197: session is complete or inactive and 1 if the session
198: is still active."
199: ::= { rtpSessionEntry 1 }
200:
201: rtpSessionIndex OBJECT-TYPE
202: SYNTAX Integer32 (1..2147483647)
203: MAX-ACCESS not-accessible
204: STATUS current
205: DESCRIPTION
206: "The index of the conceptual row which is for SNMP purposes
207: only and has no relation to any protocol value. There is
208: no requirement that these rows are created or maintained
209: sequentially."
210: ::= { rtpSessionEntry 2 }
211:
212: rtpSessionSessionIdentifier OBJECT-TYPE
213: SYNTAX OCTET STRING (SIZE(0..128))
214: MAX-ACCESS read-only
215: STATUS current
216: DESCRIPTION
217: "Unique identifier for this session. A billing record
218: correlation identifier should be used if available,
219: otherwise an identifier such as SSRC can be used."
220: ::= { rtpSessionEntry 3 }
221:
222: rtpSessionStartTime OBJECT-TYPE
223: SYNTAX DateAndTime
224: MAX-ACCESS read-only
225: STATUS current
226: DESCRIPTION
227: "Call start time for this call. If the start time is not
228: known then this represents the earliest known time associated
229: with the call."
230: ::= { rtpSessionEntry 4 }
231:
232: rtpSessionStopTime OBJECT-TYPE
233: SYNTAX DateAndTime
234: MAX-ACCESS read-only
235: STATUS current
236: DESCRIPTION
237: "Call stop time for this call. If the call is still active
238: then this shall have the value 0. If the call is complete
239: but the time is unknown then this shall have the value of the
240: latest time associated with the call."
241: ::= { rtpSessionEntry 5 }
242:
243: rtpSessionSourceIPtype OBJECT-TYPE
244: SYNTAX InetAddressType
245: MAX-ACCESS read-only
246: STATUS current
247: DESCRIPTION
248: "IP address type for the originating IP endpoint for this
249: RTP stream."
250: ::= { rtpSessionEntry 6 }
251:
252: rtpSessionSourceIPaddress OBJECT-TYPE
253: SYNTAX InetAddress
254: MAX-ACCESS read-only
255: STATUS current
256: DESCRIPTION
257: "IP address for the originating IP endpoint for this
258: RTP stream."
259: ::= { rtpSessionEntry 7 }
260:
261: rtpSessionSourceRTPport OBJECT-TYPE
262: SYNTAX InetPortNumber
263: MAX-ACCESS read-only
264: STATUS current
265: DESCRIPTION
266: "Source UDP port for RTP. A value of 0 indicates
267: an unknown port number."
268: ::= { rtpSessionEntry 8 }
269:
270: rtpSessionSourceRTCPport OBJECT-TYPE
271: SYNTAX InetPortNumber
272: MAX-ACCESS read-only
273: STATUS current
274: DESCRIPTION
275: "Source UDP port for RTCP. A value of 0 indicates
276: an unknown port number."
277: ::= { rtpSessionEntry 9 }
278:
279: rtpSessionDestIPtype OBJECT-TYPE
280: SYNTAX InetAddressType
281: MAX-ACCESS read-only
282: STATUS current
283: DESCRIPTION
284: "Destination IP address type for this session."
285: ::= { rtpSessionEntry 10 }
286:
287: rtpSessionDestIPaddress OBJECT-TYPE
288: SYNTAX InetAddress
289: MAX-ACCESS read-only
290: STATUS current
291: DESCRIPTION
292: "Destination IP address for this session."
293: ::= { rtpSessionEntry 11 }
294:
295: rtpSessionDestRTPport OBJECT-TYPE
296: SYNTAX InetPortNumber
297: MAX-ACCESS read-only
298: STATUS current
299: DESCRIPTION
300: "Destination UDP port for RTP. A value of 0 indicates
301: an unknown port number."
302: ::= { rtpSessionEntry 12 }
303:
304: rtpSessionDestRTCPport OBJECT-TYPE
305: SYNTAX InetPortNumber
306: MAX-ACCESS read-only
307: STATUS current
308: DESCRIPTION
309: "Destination UDP port for RTCP.A value of 0 indicates
310: an unknown port number."
311: ::= { rtpSessionEntry 13 }
312:
313: rtpSessionSrceIdenType OBJECT-TYPE
314: SYNTAX INTEGER {dialedNumber (1),
315: urlID (2),
316: other (3) }
317: MAX-ACCESS read-only
318: STATUS current
319: DESCRIPTION
320: "Defines the type of address in parameter
321: rtpSessionSourceIdentifier"
322: ::= { rtpSessionEntry 14 }
323:
324: rtpSessionSrceIdentifier OBJECT-TYPE
325: SYNTAX OCTET STRING (SIZE(0..128))
326: MAX-ACCESS read-only
327: STATUS current
328: DESCRIPTION
329: "Alternate identifier to the IP address. This can be E.164,
330: DN, or URL."
331: ::= { rtpSessionEntry 15 }
332:
333: rtpSessionDestIdenType OBJECT-TYPE
334: SYNTAX INTEGER {dialedNumber (1),
335: urlID (2),
336: other (3) }
337: MAX-ACCESS read-only
338: STATUS current
339: DESCRIPTION
340: "Defines the type of address in parameter
341: rtpSessionDestIdentifier."
342: ::= { rtpSessionEntry 16 }
343:
344: rtpSessionDestIdentifier OBJECT-TYPE
345: SYNTAX OCTET STRING (SIZE(0..128))
346: MAX-ACCESS read-only
347: STATUS current
348: DESCRIPTION
349: "Alternate identifier to the IP address. This can be E.164,
350: DN, or URL."
351: ::= { rtpSessionEntry 17 }
352:
353: rtpSessionIfIndex OBJECT-TYPE
354: SYNTAX InterfaceIndex
355: MAX-ACCESS read-create
356: STATUS current
357: DESCRIPTION
358: "The ifIndex value is set to the corresponding value
359: from IF-MIB (See RFC 2233, 'The Interfaces Group MIB using
360: SMIv2'). This is the interface that the RTP stream is being sent
361: to or received from, or in the case of an RTP Monitor the
362: interface that RTCP packets will be received on. Cannot be
363: changed if rtpSessionRowStatus is 'active'."
364: ::= { rtpSessionEntry 18 }
365:
366: rtpSessionMonitor OBJECT-TYPE
367: SYNTAX TruthValue
368: MAX-ACCESS read-only
369: STATUS current
370: DESCRIPTION
371: "Boolean, Set to 'true(1)' if remote senders or receivers in
372: addition to the local RTP System are to be monitored using RTCP.
373: RTP Monitors MUST initialize to 'true(1)' and RTP Hosts SHOULD
374: initialize this 'false(2)'. Note that because 'host monitor'
375: systems are receiving RTCP from their remote participants they
376: MUST set this value to 'true(1)'."
377: ::= { rtpSessionEntry 19 }
378:
379: rtpSessionSenderJoins OBJECT-TYPE
380: SYNTAX Counter32
381: MAX-ACCESS read-only
382: STATUS current
383: DESCRIPTION
384: "The number of senders that have been observed to have
385: joined the session since this conceptual row was created
386: (rtpSessionStartTime). A sender 'joins' an RTP
387: session by sending to it. Senders that leave and then
388: re-join following an RTCP BYE (see RFC 3550, 'RTP: A
389: Transport Protocol for Real-Time Applications,' sec. 6.6)
390: or session timeout may be counted twice. Every time a new
391: RTP sender is detected either using RTP or RTCP, this counter
392: is incremented."
393: ::= { rtpSessionEntry 20 }
394:
395: rtpSessionReceiverJoins OBJECT-TYPE
396: SYNTAX Counter32
397: MAX-ACCESS read-only
398: STATUS current
399: DESCRIPTION
400: "The number of receivers that have been been observed to
401: have joined this session since this conceptual row was
402: created (rtpSessionStartTime). A receiver 'joins' an RTP
403: session by sending RTCP Receiver Reports to the session.
404: Receivers that leave and then re-join following an RTCP BYE
405: (see RFC 3550, 'RTP: A Transport Protocol for Real-Time
406: Applications,' sec. 6.6) or session timeout may be counted
407: twice."
408: ::= { rtpSessionEntry 21 }
409:
410: rtpSessionByes OBJECT-TYPE
411: SYNTAX Counter32
412: MAX-ACCESS read-only
413: STATUS current
414: DESCRIPTION
415: "A count of RTCP BYE (see RFC 3550, 'RTP: A Transport
416: Protocol for Real-Time Applications,' sec. 6.6) messages
417: received by this entity."
418: ::= { rtpSessionEntry 22 }
419:
420: rtpSessionRowStatus OBJECT-TYPE
421: SYNTAX RowStatus
422: MAX-ACCESS read-create
423: STATUS current
424: DESCRIPTION
425: "Value of 'active' when RTP or RTCP messages are being
426: sent or received by an RTP System. A newly-created
427: conceptual row must have the all read-create objects
428: initialized before becoming 'active'.
429: A conceptual row that is in the 'notReady' or 'notInService'
430: state MAY be removed after 5 minutes."
431: ::= { rtpSessionEntry 23 }
432:
433: rtpSessionMaxNumEntries OBJECT-TYPE
434: SYNTAX Integer32
435: MAX-ACCESS read-only
436: STATUS current
437: DESCRIPTION
438: "The maximum number of entries that can be supported
439: in this table."
440: ::= { rtpSessionEntry 24 }
441:
442:
443:
444:
445:
446:
447:
448:
449:
450:
451: -- SENDER INVERSE TABLE
452: --
453: rtpSenderInverseTable OBJECT-TYPE
454: SYNTAX SEQUENCE OF RtpSenderInverseEntry
455: MAX-ACCESS not-accessible
456: STATUS current
457: DESCRIPTION
458: "Maps rtpSenderIPAddress, rtpSessionIndex, to the rtpSenderSSRC
459: index of the rtpSenderTable. This table allows management
460: applications to find entries sorted by Sender IP address rather
461: than sorted by rtpSessionIndex. Given the rtpSessionDomain and
462: rtpSenderAddr, a set of rtpSessionIndex and rtpSenderSSRC values
463: can be returned from a tree walk. When rtpSessionIndex is
464: specified in the SNMP Get-Next operations, one or more
465: rtpSenderSSRC values may be returned."
466: ::= { rtpMIBV2Objects 4 }
467:
468: rtpSenderInverseEntry OBJECT-TYPE
468: warning -
warning: index of row `rtpSenderInverseEntry' can exceed OID size limit by 137 subidentifier(s)
469: SYNTAX RtpSenderInverseEntry
470: MAX-ACCESS not-accessible
471: STATUS current
472: DESCRIPTION
473: "Each entry corresponds to exactly one entry in the
474: rtpSenderTable - the entry containing the index pair,
475: rtpSessionIndex, rtpSenderSSRC."
476: INDEX { rtpSenderIPaddress, rtpSenderRTPport, rtpSessionCallState,
477: rtpSessionIndex, rtpSenderSSRC }
478: ::= { rtpSenderInverseTable 1 }
479:
480: RtpSenderInverseEntry ::= SEQUENCE {
481: rtpSenderInverseStartTime DateAndTime
482: }
483:
484: rtpSenderInverseStartTime OBJECT-TYPE
485: SYNTAX DateAndTime
486: MAX-ACCESS read-only
487: STATUS current
488: DESCRIPTION
489: "The time at which this row was
490: created."
491: ::= { rtpSenderInverseEntry 1 }
492:
493: -- SENDERS TABLE
494: --
495: rtpSenderTable OBJECT-TYPE
496: SYNTAX SEQUENCE OF RtpSenderEntry
497: MAX-ACCESS not-accessible
498: STATUS current
499: DESCRIPTION
500: "Table of information about a sender or senders to an RTP
501: Session. RTP sending hosts MUST have an entry in this table
502: for each stream being sent. RTP receiving hosts MAY have an
503: entry in this table for each sending stream being received by
504: this host. RTP monitors MUST create an entry for each observed
505: sender to a multicast RTP Session as a side-effect when a
506: conceptual row in the rtpSessionTable is made 'active' by a
507: manager."
508: ::= { rtpMIBV2Objects 5 }
509:
510: rtpSenderEntry OBJECT-TYPE
511: SYNTAX RtpSenderEntry
512: MAX-ACCESS not-accessible
513: STATUS current
514: DESCRIPTION
515: "Each entry contains information from a single RTP Sender
516: Synchronization Source (SSRC, see RFC 3550 'RTP: A Transport
517: Protocol for Real-Time Applications' sec.6). The session is
518: identified to the the SNMP entity by rtpSessionIndex.
519: Rows are removed by the RTP agent when a BYE is received
520: from the sender or when the sender times out (see RFC
521: 3550, Sec. 6.2.1) or when the rtpSessionEntry is deleted."
522: INDEX { rtpSessionCallState, rtpSessionIndex, rtpSenderSSRC }
523: ::= { rtpSenderTable 1 }
524:
525: RtpSenderEntry ::= SEQUENCE {
526: rtpSenderSSRC Unsigned32,
527: rtpSenderCNAME Utf8String,
528: rtpSenderIPtype InetAddressType,
529: rtpSenderIPaddress InetAddress,
530: rtpSenderRTPport InetPortNumber,
531: rtpSenderRTCPport InetPortNumber,
532: rtpSenderPackets Counter64,
533: rtpSenderOctets Counter64,
534: rtpSenderTool Utf8String,
535: rtpSenderSRs Counter32,
536: rtpSenderSRTime DateAndTime,
537: rtpSenderPT Integer32,
538: rtpSenderStartTime DateAndTime
539: }
540:
541: rtpSenderSSRC OBJECT-TYPE
542: SYNTAX Unsigned32
543: MAX-ACCESS not-accessible
544: STATUS current
545: DESCRIPTION
546: "The RTP SSRC, or synchronization source identifier of the
547: sender. The RTP session address plus an SSRC uniquely
548: identify a sender to an RTP session (see RFC 3550, 'RTP: A
549: Transport Protocol for Real-Time Applications' sec.3)."
550: ::= { rtpSenderEntry 1 }
551:
552: rtpSenderCNAME OBJECT-TYPE
553: SYNTAX Utf8String
554: MAX-ACCESS read-only
555: STATUS current
556: DESCRIPTION
557: "The RTP canonical name of the sender."
558: ::= { rtpSenderEntry 2 }
559:
560: rtpSenderIPtype OBJECT-TYPE
561: SYNTAX InetAddressType
562: MAX-ACCESS read-only
563: STATUS current
564: DESCRIPTION
565: "IP address type for the originating IP endpoint for this
566: RTP stream."
567: ::= { rtpSenderEntry 3 }
568:
569: rtpSenderIPaddress OBJECT-TYPE
570: SYNTAX InetAddress
571: MAX-ACCESS read-only
572: STATUS current
573: DESCRIPTION
574: "IP address for the originating IP endpoint for this
575: RTP stream."
576: ::= { rtpSenderEntry 4 }
577:
578: rtpSenderRTPport OBJECT-TYPE
579: SYNTAX InetPortNumber
580: MAX-ACCESS read-only
581: STATUS current
582: DESCRIPTION
583: "Source UDP port for RTP. A value of 0 indicates
584: an unknown port number."
585: ::= { rtpSenderEntry 5 }
586:
587: rtpSenderRTCPport OBJECT-TYPE
588: SYNTAX InetPortNumber
589: MAX-ACCESS read-only
590: STATUS current
591: DESCRIPTION
592: "Source UDP port for RTCP. A value of 0 indicates
593: an unknown port number."
594: ::= { rtpSenderEntry 6 }
595:
596: rtpSenderPackets OBJECT-TYPE
597: SYNTAX Counter64
598: MAX-ACCESS read-only
599: STATUS current
600: DESCRIPTION
601: "Count of RTP packets sent by this sender, or observed by
602:
603: an RTP monitor, since rtpSenderStartTime."
604: ::= { rtpSenderEntry 7 }
605:
606: rtpSenderOctets OBJECT-TYPE
607: SYNTAX Counter64
608: MAX-ACCESS read-only
609: STATUS current
610: DESCRIPTION
611: "Count of non-header RTP octets sent by this sender, or observed
612: by an RTP monitor, since rtpSenderStartTime."
613: ::= { rtpSenderEntry 8 }
614:
615:
616: rtpSenderTool OBJECT-TYPE
617: SYNTAX Utf8String (SIZE(0..127))
618: MAX-ACCESS read-only
619: STATUS current
620: DESCRIPTION
621: "Name of the application program source of the stream."
622: ::= { rtpSenderEntry 9 }
623:
624: rtpSenderSRs OBJECT-TYPE
625: SYNTAX Counter32
626: MAX-ACCESS read-only
627: STATUS current
628: DESCRIPTION
629: "A count of the number of RTCP Sender Reports that have
630: been sent from this sender, or observed if the RTP entity
631: is a monitor, since rtpSenderStartTime."
632: ::= { rtpSenderEntry 10 }
633:
634: rtpSenderSRTime OBJECT-TYPE
635: SYNTAX DateAndTime
636: MAX-ACCESS read-only
637: STATUS current
638: DESCRIPTION
639: "rtpSenderSRTime is the time at which
640: the last SR was received from this sender, in the case of a
641: monitor or receiving host. Or sent by this sender, in the
642: case of a sending host."
643: ::= { rtpSenderEntry 11 }
644:
645: rtpSenderPT OBJECT-TYPE
646: SYNTAX Integer32(0..127)
647: MAX-ACCESS read-only
648: STATUS current
649: DESCRIPTION
650: "Payload type from the RTP header of the most recently received
651: RTP Packet (see RFC 3550, 'RTP: A Transport Protocol for
652:
653: Real-Time Applications' sec. 5)."
654: ::= { rtpSenderEntry 12 }
655:
656: rtpSenderStartTime OBJECT-TYPE
657: SYNTAX DateAndTime
658: MAX-ACCESS read-only
659: STATUS current
660: DESCRIPTION
661: "The time at which this row was
662: created."
663: ::= { rtpSenderEntry 13 }
664:
665: --
666: -- RECEIVER INVERSE TABLE
667: --
668: rtpRcvrInverseTable OBJECT-TYPE
669: SYNTAX SEQUENCE OF RtpRcvrInverseEntry
670: MAX-ACCESS not-accessible
671: STATUS current
672: DESCRIPTION
673: "Maps rtpRcvrIPaddress and rtpSessionIndex to the rtpRcvrSRCSSRC
674: and rtpRcvrSSRC indexes of the rtpRcvrTable. This table allows
675: management applications to find entries by rtpRcvrIPaddress
676: rather than by rtpSessionIndex. Given rtpSessionDomain and
677: rtpRcvrIPaddress, a set of rtpSessionIndex, rtpRcvrSRCSSRC, and
678: rtpRcvrSSRC values can be returned from a tree walk. When
679: rtpSessionIndex is specified in SNMP Get-Next operations, one or
680: more rtpRcvrSRCSSRC and rtpRcvrSSRC pairs may be returned."
681: ::= { rtpMIBV2Objects 6 }
682:
683: rtpRcvrInverseEntry OBJECT-TYPE
683: warning -
warning: index of row `rtpRcvrInverseEntry' can exceed OID size limit by 138 subidentifier(s)
684: SYNTAX RtpRcvrInverseEntry
685: MAX-ACCESS not-accessible
686: STATUS current
687: DESCRIPTION
688: "Each entry corresponds to exactly one entry in the
689: rtpRcvrTable - the entry containing the index pair,
690: rtpSessionIndex, rtpRcvrSSRC."
691: INDEX { rtpRcvrIPaddress, rtpRcvrRTPport, rtpSessionCallState,
692: rtpSessionIndex, rtpRcvrSRCSSRC, rtpRcvrSSRC }
693: ::= { rtpRcvrInverseTable 1 }
694:
695: RtpRcvrInverseEntry ::= SEQUENCE {
696: rtpRcvrInverseStartTime DateAndTime
697: }
698:
699: rtpRcvrInverseStartTime OBJECT-TYPE
700: SYNTAX DateAndTime
701:
702: MAX-ACCESS read-only
703: STATUS current
704: DESCRIPTION
705: "The time at which this row was
706: created."
707: ::= { rtpRcvrInverseEntry 1 }
708:
709:
710: --
711: -- RECEIVERS TABLE
712: --
713: rtpRcvrTable OBJECT-TYPE
714: SYNTAX SEQUENCE OF RtpRcvrEntry
715: MAX-ACCESS not-accessible
716: STATUS current
717: DESCRIPTION
718: "Table of information about a receiver or receivers of RTP
719: session data. RTP hosts that receive RTP session packets
720: MUST create an entry in this table for that receiver/sender
721: pair. RTP hosts that send RTP session packets MAY create
722: an entry in this table for each receiver to their stream
723: using RTCP feedback from the RTP group. RTP monitors
724: create an entry for each observed RTP session receiver as
725: a side effect when a conceptual row in the rtpSessionTable
726: is made 'active' by a manager."
727: ::= { rtpMIBV2Objects 7 }
728:
729: rtpRcvrEntry OBJECT-TYPE
730: SYNTAX RtpRcvrEntry
731: MAX-ACCESS not-accessible
732: STATUS current
733: DESCRIPTION
734: "Each entry contains information from a single RTP
735: Synchronization Source that is receiving packets from the
736: sender identified by rtpRcvrSRCSSRC (SSRC, see RFC 3550,
737: 'RTP: A Transport Protocol for Real-Time Applications'
738: sec.6). The session is identified to the the RTP Agent entity
739: by rtpSessionIndex. Rows are removed by the RTP agent when
740: a BYE is received from the sender or when the sender times
741: out (see RFC 3550) or when the rtpSessionEntry is deleted."
742: INDEX { rtpSessionCallState, rtpSessionIndex, rtpRcvrSRCSSRC,
743: rtpRcvrSSRC }
744: ::= { rtpRcvrTable 1 }
745:
746: RtpRcvrEntry ::= SEQUENCE {
747: rtpRcvrSRCSSRC Unsigned32,
748: rtpRcvrSSRC Unsigned32,
749: rtpRcvrCNAME Utf8String,
750: rtpRcvrIPtype InetAddressType,
751: rtpRcvrIPaddress InetAddress,
752: rtpRcvrRTPport InetPortNumber,
753: rtpRcvrRTCPport InetPortNumber,
754: rtpRcvrRTT Gauge32,
755: rtpRcvrLostPackets Counter64,
756: rtpRcvrJitter Gauge32,
757: rtpRcvrTool Utf8String,
758: rtpRcvrRRs Counter32,
759: rtpRcvrRRTime DateAndTime,
760: rtpRcvrPT Integer32,
761: rtpRcvrPackets Counter64,
762: rtpRcvrOctets Counter64,
763: rtpRcvrStartTime DateAndTime
764: }
765:
766: rtpRcvrSRCSSRC OBJECT-TYPE
767: SYNTAX Unsigned32
768: MAX-ACCESS not-accessible
769: STATUS current
770: DESCRIPTION
771: "The RTP SSRC, or synchronization source identifier of the
772: sender. The RTP session address plus an SSRC uniquely
773: identify a sender or receiver of an RTP stream (see RFC
774: 3550, 'RTP: A Transport Protocol for Real-Time
775: Applications' sec.3)."
776: ::= { rtpRcvrEntry 1 }
777:
778: rtpRcvrSSRC OBJECT-TYPE
779: SYNTAX Unsigned32
780: MAX-ACCESS not-accessible
781: STATUS current
782: DESCRIPTION
783: "The RTP SSRC, or synchronization source identifier of the
784: receiver. The RTP session address plus an SSRC uniquely
785: identify a receiver of an RTP stream (see RFC 3550, 'RTP:
786: A Transport Protocol for Real-Time Applications' sec.3)."
787: ::= { rtpRcvrEntry 2 }
788:
789: rtpRcvrCNAME OBJECT-TYPE
790: SYNTAX Utf8String
791: MAX-ACCESS read-only
792: STATUS current
793: DESCRIPTION
794: "The RTP canonical name of the receiver."
795: ::= { rtpRcvrEntry 3 }
796:
797: rtpRcvrIPtype OBJECT-TYPE
798: SYNTAX InetAddressType
799: MAX-ACCESS read-only
800: STATUS current
801: DESCRIPTION
802: "Destination IP address type for this session."
803: ::= { rtpRcvrEntry 4 }
804:
805: rtpRcvrIPaddress OBJECT-TYPE
806: SYNTAX InetAddress
807: MAX-ACCESS read-only
808: STATUS current
809: DESCRIPTION
810: "Destination IP address for this session."
811: ::= { rtpRcvrEntry 5 }
812:
813: rtpRcvrRTPport OBJECT-TYPE
814: SYNTAX InetPortNumber
815: MAX-ACCESS read-only
816: STATUS current
817: DESCRIPTION
818: "Destination UDP port for RTP. A value of 0 indicates
819: an unknown port number."
820: ::= { rtpRcvrEntry 6 }
821:
822: rtpRcvrRTCPport OBJECT-TYPE
823: SYNTAX InetPortNumber
824: MAX-ACCESS read-only
825: STATUS current
826: DESCRIPTION
827: "Destination UDP port for RTCP.A value of 0 indicates
828: an unknown port number."
829: ::= { rtpRcvrEntry 7 }
830:
831: rtpRcvrRTT OBJECT-TYPE
832: SYNTAX Gauge32
833: MAX-ACCESS read-only
834: STATUS current
835: DESCRIPTION
836: "The round trip time measurement taken by the source of the
837: RTP stream based on the algorithm described on sec. 6 of
838: RFC 3550, 'RTP: A Transport Protocol for Real-Time
839: Applications.' This algorithm can produce meaningful
840: results when the RTP agent has the same clock as the stream
841: sender (when the RTP monitor is also the sending host for the
842: particular receiver). Otherwise, the entity should return
843: 'noSuchInstance' in response to queries against rtpRcvrRTT."
844: ::= { rtpRcvrEntry 8 }
845:
846: rtpRcvrLostPackets OBJECT-TYPE
847: SYNTAX Counter64
848: MAX-ACCESS read-only
849: STATUS current
850: DESCRIPTION
851: "A count of RTP packets lost as observed by this receiver
852: since rtpRcvrStartTime."
853: ::= { rtpRcvrEntry 9 }
854:
855: rtpRcvrJitter OBJECT-TYPE
856: SYNTAX Gauge32
857: MAX-ACCESS read-only
858: STATUS current
859: DESCRIPTION
860: "An estimate of delay variation as observed by this
861: receiver. (see RFC 3550, 'RTP: A Transport Protocol
862: for Real-Time Applications' sec.6.3.1 and A.8)."
863: ::= { rtpRcvrEntry 10 }
864:
865: rtpRcvrTool OBJECT-TYPE
866: SYNTAX Utf8String (SIZE(0..127))
867: MAX-ACCESS read-only
868: STATUS current
869: DESCRIPTION
870: "Name of the application program source of the stream."
871: ::= { rtpRcvrEntry 11 }
872:
873: rtpRcvrRRs OBJECT-TYPE
874: SYNTAX Counter32
875: MAX-ACCESS read-only
876: STATUS current
877: DESCRIPTION
878: "A count of the number of RTCP Receiver Reports that have
879: been sent from this receiver, or observed if the RTP entity
880: is a monitor, since rtpRcvrStartTime."
881: ::= { rtpRcvrEntry 12 }
882:
883: rtpRcvrRRTime OBJECT-TYPE
884: SYNTAX DateAndTime
885: MAX-ACCESS read-only
886: STATUS current
887: DESCRIPTION
888: "rtpRcvrRRTime is the time at which the last RTCP Receiver Report
889: was received from this receiver, in the case of a monitor or RR
890: receiver (the RTP Sender). It is the time at which the last
891: RR was sent by this receiver in the case of an RTP receiver
892: sending the RR."
893: ::= { rtpRcvrEntry 13 }
894:
895: rtpRcvrPT OBJECT-TYPE
896: SYNTAX Integer32(0..127)
897: MAX-ACCESS read-only
898: STATUS current
899: DESCRIPTION
900: "Static or dynamic payload type from the RTP header (see
901: RFC 3550, 'RTP: A Transport Protocol for Real-Time
902: Applications' sec. 5)."
903: ::= { rtpRcvrEntry 14 }
904:
905: rtpRcvrPackets OBJECT-TYPE
906: SYNTAX Counter64
907: MAX-ACCESS read-only
908: STATUS current
909: DESCRIPTION
910: "Count of RTP packets received by this RTP host receiver
911: since rtpRcvrStartTime."
912: ::= { rtpRcvrEntry 15 }
913:
914: rtpRcvrOctets OBJECT-TYPE
915: SYNTAX Counter64
916: MAX-ACCESS read-only
917: STATUS current
918: DESCRIPTION
919: "Count of non-header RTP octets received by this receiving RTP
920: host since rtpRcvrStartTime."
921: ::= { rtpRcvrEntry 16 }
922:
923: rtpRcvrStartTime OBJECT-TYPE
924: SYNTAX DateAndTime
925: MAX-ACCESS read-only
926: STATUS current
927: DESCRIPTION
928: "The time at which this row was created."
929: ::= { rtpRcvrEntry 17 }
930:
931: -- MODULE GROUPS
932: --
933: -- There are two types of RTP Systems, RTP hosts and RTP Monitors.
934: -- Thus there are three kinds of objects: 1) Objects common to both
935: -- kinds of systems, 2) Objects unique to RTP Hosts and 3) Objects
936: -- unique to RTP Monitors. There is a fourth group, 4) Objects that
937: -- SHOULD be implemented by Multicast hosts and RTP Monitors
938:
939: rtpGroups OBJECT IDENTIFIER ::= { rtpConformance 1 }
940: rtpSystemGroup OBJECT-GROUP
941: OBJECTS {
942: rtpSessionSessionIdentifier,
943: rtpSessionStartTime,
944: rtpSessionStopTime,
945: rtpSessionDestIPtype,
946: rtpSessionDestIPaddress,
947: rtpSessionDestRTPport,
948: rtpSessionDestRTCPport,
949: rtpSessionSrceIdenType,
950: rtpSessionSrceIdentifier,
951: rtpSessionDestIdenType,
952: rtpSessionDestIdentifier,
953: rtpSessionIfIndex,
954: rtpSessionSenderJoins,
955: rtpSessionReceiverJoins,
956: rtpSessionByes,
957: rtpSessionMonitor,
958: rtpSessionMaxNumEntries,
959: rtpSenderCNAME,
960: rtpSenderIPtype,
961: rtpSenderIPaddress,
962: rtpSenderRTPport,
963: rtpSenderRTCPport,
964: rtpSenderPackets,
965: rtpSenderOctets,
966: rtpSenderTool,
967: rtpSenderSRs,
968: rtpSenderSRTime,
969: rtpSenderStartTime,
970: rtpRcvrCNAME,
971: rtpRcvrIPtype,
972: rtpRcvrIPaddress,
973: rtpRcvrRTPport,
974: rtpRcvrRTCPport,
975: rtpRcvrLostPackets,
976: rtpRcvrJitter,
977: rtpRcvrTool,
978: rtpRcvrRRs,
979: rtpRcvrRRTime,
980: rtpRcvrStartTime
981: }
982: STATUS current
983: DESCRIPTION
984: "Objects available to all RTP Systems."
985: ::= { rtpGroups 1 }
986:
987: rtpHostGroup OBJECT-GROUP
988: OBJECTS {
989: rtpSessionSourceIPtype,
990: rtpSessionSourceIPaddress,
991: rtpSessionSourceRTPport,
992: rtpSessionSourceRTCPport,
993: rtpSenderPT,
994: rtpRcvrPT,
995: rtpRcvrRTT,
996: rtpRcvrOctets,
997: rtpRcvrPackets
998: }
999: STATUS current
1000: DESCRIPTION
1001: "Objects that are available to RTP Host systems, but may not
1002: be available to RTP Monitor systems."
1003: ::= { rtpGroups 2 }
1004:
1005: rtpMonitorGroup OBJECT-GROUP
1006: OBJECTS {
1007: rtpSessionNewIndex,
1008: rtpSessionRowStatus
1009: }
1010: STATUS current
1011: DESCRIPTION
1012: "Objects used to create rows in the RTP Session Table. These
1013: objects are not needed if the system does not create rows."
1014: ::= { rtpGroups 3 }
1015:
1016: rtpInverseGroup OBJECT-GROUP
1017: OBJECTS {
1018: rtpSessionInverseStartTime,
1019: rtpSenderInverseStartTime,
1020: rtpRcvrInverseStartTime
1021: }
1022: STATUS current
1023: DESCRIPTION
1024: "Objects used in the Inverse Lookup Tables."
1025: ::= { rtpGroups 4 }
1026:
1027: -- Compliance
1028: --
1029: rtpCompliances OBJECT IDENTIFIER ::= { rtpConformance 2 }
1030:
1031: rtpHostCompliance MODULE-COMPLIANCE
1032: STATUS current
1033: DESCRIPTION
1034: "Host implementations MUST comply."
1035: MODULE RTP-MIB
1036: MANDATORY-GROUPS {
1037: rtpSystemGroup,
1038: rtpHostGroup
1039: }
1040: GROUP rtpMonitorGroup
1041: DESCRIPTION
1042: "Host systems my optionally support row creation and deletion.
1043: This would allow an RTP Host system to act as an RTP Monitor."
1044: GROUP rtpInverseGroup
1045: DESCRIPTION
1046: "Multicast RTP Systems SHOULD implement the optional
1047: tables."
1048: OBJECT rtpSessionNewIndex
1049: MIN-ACCESS not-accessible
1050: DESCRIPTION
1051: "RTP system implementations support of
1052: row creation and deletion is OPTIONAL so
1053: implementation of this object is OPTIONAL."
1054: OBJECT rtpSessionDestIPtype
1055: MIN-ACCESS read-only
1056: DESCRIPTION
1057: "Row creation and deletion is OPTIONAL so
1058: read-create access to this object is OPTIONAL."
1059: OBJECT rtpSessionDestIPaddress
1060: MIN-ACCESS read-only
1061: DESCRIPTION
1062: "Row creation and deletion is OPTIONAL so
1063: read-create access to this object is OPTIONAL."
1064: OBJECT rtpSessionDestRTPport
1065: MIN-ACCESS read-only
1066: DESCRIPTION
1067: "Row creation and deletion is OPTIONAL so
1068: read-create access to this object is OPTIONAL."
1069: OBJECT rtpSessionDestRTCPport
1070: MIN-ACCESS read-only
1071: DESCRIPTION
1072: "Row creation and deletion is OPTIONAL so
1073: read-create access to this object is OPTIONAL."
1074: OBJECT rtpSessionIfIndex
1075: MIN-ACCESS read-only
1076: DESCRIPTION
1077: "Row creation and deletion is OPTIONAL so
1078: read-create access to this object is OPTIONAL."
1079: OBJECT rtpSessionRowStatus
1080: MIN-ACCESS not-accessible
1081: DESCRIPTION
1082: "Row creation and deletion is OPTIONAL so
1083: read-create access to this object is OPTIONAL."
1084:
1085: OBJECT rtpSessionInverseStartTime
1086: MIN-ACCESS not-accessible
1087: DESCRIPTION
1088: "Multicast RTP Systems SHOULD implement the optional
1089: tables."
1090:
1091: OBJECT rtpSenderInverseStartTime
1092: MIN-ACCESS not-accessible
1093: DESCRIPTION
1094: "Multicast RTP Systems SHOULD implement the optional
1095: tables."
1096: OBJECT rtpRcvrInverseStartTime
1097: MIN-ACCESS not-accessible
1098: DESCRIPTION
1099: "Multicast RTP Systems SHOULD implement the optional
1100: tables."
1101: ::= { rtpCompliances 1 }
1102:
1103: rtpMonitorCompliance MODULE-COMPLIANCE
1104: STATUS current
1105: DESCRIPTION
1106: "Monitor implementations must comply. RTP Monitors are not
1107: required to support creation or deletion."
1108: MODULE RTP-MIB
1109: MANDATORY-GROUPS {
1110: rtpSystemGroup,
1111: rtpMonitorGroup
1112: }
1113: GROUP rtpHostGroup
1114: DESCRIPTION
1115: "Monitor implementations may not have access to values in the
1116: rtpHostGroup."
1117: GROUP rtpInverseGroup
1118: DESCRIPTION
1119: "Multicast RTP Systems SHOULD implement the optional
1120: tables."
1121: OBJECT rtpSessionSourceIPtype
1122: MIN-ACCESS not-accessible
1123: DESCRIPTION
1124: "RTP monitor sourcing of RTP or RTCP data packets
1125: is OPTIONAL and implementation of this object is
1126: OPTIONAL."
1127: OBJECT rtpSessionSourceIPaddress
1128: MIN-ACCESS not-accessible
1129: DESCRIPTION
1130: "RTP monitor sourcing of RTP or RTCP data packets
1131: is OPTIONAL and implementation of this object is
1132: OPTIONAL."
1133:
1134: OBJECT rtpSessionSourceRTPport
1135: MIN-ACCESS not-accessible
1136: DESCRIPTION
1137: "RTP monitor sourcing of RTP or RTCP data packets
1138: is OPTIONAL and implementation of this object is
1139: OPTIONAL."
1140:
1141: OBJECT rtpSessionSourceRTCPport
1142: MIN-ACCESS not-accessible
1143: DESCRIPTION
1144: "RTP monitor sourcing of RTP or RTCP data packets
1145: is OPTIONAL and implementation of this object is
1146: OPTIONAL."
1147: OBJECT rtpRcvrPT
1148: MIN-ACCESS not-accessible
1149: DESCRIPTION
1150: "RTP monitor systems may not support
1151: retrieval of the RTP Payload Type from the RTP
1152: header (and may receive RTCP messages only). When
1153: queried for the payload type information"
1154: OBJECT rtpSenderPT
1155: MIN-ACCESS not-accessible
1156: DESCRIPTION
1157: "RTP monitor systems may not support
1158: retrieval of the RTP Payload Type from the RTP
1159: header (and may receive RTCP messages only). When
1160: queried for the payload type information."
1161: OBJECT rtpRcvrOctets
1162: MIN-ACCESS not-accessible
1163: DESCRIPTION
1164: "RTP monitor systems may receive only the RTCP messages
1165: and not the RTP messages that contain the octet count
1166: of the RTP message. Thus implementation of this
1167: object is OPTIONAL"
1168: OBJECT rtpRcvrPackets
1169: MIN-ACCESS not-accessible
1170: DESCRIPTION
1171: "RTP monitor systems may receive only the RTCP messages
1172: and not the RTP messages that contain the octet count
1173: of the RTP message. Thus implementation of this
1174: object is OPTIONAL."
1175: OBJECT rtpSessionIfIndex
1176: MIN-ACCESS read-only
1177: DESCRIPTION
1178: "Row creation and deletion is OPTIONAL so
1179: read-create access to this object is OPTIONAL."
1180: OBJECT rtpSessionInverseStartTime
1181: MIN-ACCESS not-accessible
1182: DESCRIPTION
1183: "Multicast RTP Systems SHOULD implement the optional
1184: tables."
1185:
1186: OBJECT rtpSenderInverseStartTime
1187: MIN-ACCESS not-accessible
1188: DESCRIPTION
1189: "Multicast RTP Systems SHOULD implement the optional
1190: tables."
1191: OBJECT rtpRcvrInverseStartTime
1192: MIN-ACCESS not-accessible
1193: DESCRIPTION
1194: "Multicast RTP Systems SHOULD implement the optional
1195: tables."
1196: ::= { rtpCompliances 2 }
1197: END
1198:
1199: --
1200: -- Copyright (C) The Internet Society (2006).
1201: --
1202: -- This document is subject to the rights, licenses and restrictions
1203: -- contained in BCP 78, and except as set forth therein, the authors
1204: -- retain all their rights.
1205: --
1206: -- This document and the information contained herein are provided on an
1207: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1208: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1209: -- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1210: -- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1211: -- INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1212: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1213: --
1214: -- Intellectual Property
1215: --
1216: -- The IETF takes no position regarding the validity or scope of any
1217: -- Intellectual Property Rights or other rights that might be claimed to
1218: -- pertain to the implementation or use of the technology described in
1219: -- this document or the extent to which any license under such rights
1220: -- might or might not be available; nor does it represent that it has
1221: -- made any independent effort to identify any such rights. Information
1222: -- on the procedures with respect to rights in RFC documents can be
1223: -- found in BCP 78 and BCP 79.
1224: --
1225: -- Copies of IPR disclosures made to the IETF Secretariat and any
1226: -- assurances of licenses to be made available, or the result of an
1227: -- attempt made to obtain a general license or permission for the use of
1228: -- such proprietary rights by implementers or users of this
1229: -- specification can be obtained from the IETF on-line IPR repository at
1230: -- http://www.ietf.org/ipr.
1231: --
1232: -- The IETF invites any interested party to bring to its attention any
1233: -- copyrights, patents or patent applications, or other proprietary
1234: -- rights that may cover technology that may be required to implement
1235: -- this standard. Please address the information to the IETF at ietf-
1236: -- ipr@ietf.org.
1237: --
1238: