idnits 2.17.1 draft-combes-ipdvb-mib-rcs-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 3692. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3669. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3676. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3682. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 50 longer pages, the longest (page 88) being 60 lines == It seems as if not all pages are separated by form feeds - found 70 form feeds but 91 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 194 has weird spacing: '...tion of rcstS...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 15, 2007) is 6251 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 3243 == Unused Reference: 'ISO-MPEG' is defined on line 3593, but no explicit reference was found in the text == Unused Reference: 'ETSI-DAT' is defined on line 3598, but no explicit reference was found in the text == Unused Reference: 'ETSI-DVBS' is defined on line 3602, but no explicit reference was found in the text == Unused Reference: 'RFC4259' is defined on line 3613, but no explicit reference was found in the text Summary: 2 errors (**), 0 flaws (~~), 10 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IPDVB WG S. Combes 3 P. Amundsen 4 M. Lambert 5 H-P. Lexow 6 Internet Draft SatLabs Group 7 Expires: September 2007 March 15, 2007 9 The DVB-RCS MIB 10 draft-combes-ipdvb-mib-rcs-00.txt 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that 15 any applicable patent or other IPR claims of which he or she is 16 aware have been or will be disclosed, and any of which he or she 17 becomes aware will be disclosed, in accordance with Section 6 of 18 BCP 79. 20 This document may not be modified, and derivative works of it may not 21 be created, except to publish it as an RFC and to translate it into 22 languages other than English, or to extract section 3 as-is for 23 separate use. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html 41 This Internet-Draft will expire on September 15, 2007. 43 Abstract 45 This document describes MIB module for DVB-RCS. It defines a set of 46 new MIB entities to characterise the behaviour and performance of 47 network layer entities deploying DVB-RCS. 49 Table of Contents 51 1. Introduction...................................................2 52 2. Conventions used in this document..............................3 53 2.1. MIB Module................................................3 54 3. Definitions....................................................4 55 4. Security Considerations.......................................86 56 5. IANA Considerations...........................................86 57 6. Conclusions...................................................86 58 7. Acknowledgments...............................................86 59 8. References....................................................87 60 8.1. Normative References.....................................87 61 8.2. Informative References...................................87 62 9. Author's Addresses............................................88 63 Intellectual Property Statement..................................89 64 10. Disclaimer of Validity.......................................89 65 11. Copyright Statement..........................................90 67 1. Introduction 69 The SatLabs Group is an international non-profit EEIG (European 70 Economic Interest Grouping) committed to large-scale adoption and 71 deployment of the DVB-RCS standard [ETSI-RCS]. SatLabs members are 72 service providers, satellite operators, system integrators, terminal 73 manufacturers and technology providers with an interest in DVB-RCS. 75 Since its creation in 2001, the main goal of the SatLabs Group has 76 been to achieve interoperability between DVB-RCS terminals and 77 systems. Therefore, the Group has defined the SatLabs Qualification 78 Program which provides an independent certification process for DVB- 79 RCS Terminals based on System Recommendations defined by SatLabs. 81 To enhance products interoperability, beyond the physical and MAC 82 layers mechanisms defined in the DVB-RCS standard, SatLabs has 83 expanded its Recommendations in the field of DVB-RCS terminal 84 management [SATLABS]. 86 As part of this effort, SatLabs has drafted a common SNMP Management 87 Information Base (MIB) for DVB-RCS terminals. This MIB is defined in 88 the current document. 90 2. Conventions used in this document 92 This memo defines a portion of the Management Information Base (MIB) 93 for use with network management protocols in the Internet community. 95 For a detailed overview of the documents that describe the current 96 Internet-Standard Management Framework, please refer to section 7 of 97 RFC 3410 [RFC3410]. 99 Managed objects are accessed via a virtual information store, termed 100 the Management Information Base or MIB. MIB objects are generally 101 accessed through the Simple Network Management Protocol (SNMP). 102 Objects in the MIB are defined using the mechanisms defined in the 103 Structure of Management Information (SMI). This memo specifies a MIB 104 module that is compliant to the SMIv2, which is described in STD 58, 105 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 106 [RFC2580]. 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in RFC 2119. [RFC2119]. 112 2.1. MIB Module 114 The MIB module in this document uses the following IANA-assigned 115 OBJECT IDENTIFIER values: 117 +------------+----------------------------+ 118 | Descriptor | OBJECT IDENTIFIER value | 119 +------------+----------------------------+ 120 |dvbrcsIfMib |{ mib-2 transmission 239 } | 121 +------------+----------------------------+ 123 Table 1: Object Identifiers for the MIB 125 These values have been assigned for this MIB under the 126 'mib-2.transmission' subtree. 128 3. Definitions 130 dvbrcsIfMib DEFINITIONS ::= BEGIN 132 IMPORTS 134 MODULE-IDENTITY, transmission, NOTIFICATION-TYPE 136 FROM SNMPv2-SMI 138 TEXTUAL-CONVENTION, DisplayString, 140 PhysAddress, RowStatus FROM SNMPv2-TC; 142 dvbrcsIfMib MODULE-IDENTITY 144 LAST-UPDATED "200701111200Z" 146 ORGANIZATION "The SatLabs Group" 148 CONTACT-INFO 150 "The SatLabs Group 152 Web: www.satlabs.org 154 E-mail: info@satlabs.org " 156 DESCRIPTION 158 "SatLabs MIB subtree. Draft version A" 160 REVISION "200701111200Z" 162 DESCRIPTION 164 "Draft revision A of this MIB module. 166 Number in the transmission tree 239" 168 ::= { transmission 239 } 170 rcstSystem OBJECT IDENTIFIER ::= {dvbrcsIfMib 1} 172 rcstConfig OBJECT IDENTIFIER ::= {dvbrcsIfMib 2} 174 rcstStatus OBJECT IDENTIFIER ::= {dvbrcsIfMib 3} 176 rcstAction OBJECT IDENTIFIER ::= {dvbrcsIfMib 4} 178 installation OBJECT IDENTIFIER ::= {rcstSystem 1} 180 options OBJECT IDENTIFIER ::= {rcstSystem 2} 182 network OBJECT IDENTIFIER ::= {rcstConfig 1} 184 rtnLink OBJECT IDENTIFIER ::= {rcstConfig 2} 186 fwdLink OBJECT IDENTIFIER ::= {rcstConfig 3} 188 qos OBJECT IDENTIFIER ::= {rcstConfig 4} 190 -- 191 ===================================================================== 192 ======== 194 --- Definition of rcstSystem.installation group 196 -- 197 ===================================================================== 198 ======== 199 mibVersion OBJECT-TYPE 201 SYNTAX DisplayString 203 MAX-ACCESS read-only 205 STATUS current 207 DESCRIPTION 209 "This object is the MIB version. The first version is 1.0." 211 ::= {installation 1} 213 location OBJECT-TYPE 215 SYNTAX DisplayString 217 MAX-ACCESS read-write 219 STATUS current 221 DESCRIPTION 223 "Physical location of the ODU antenna expressed as Longitude, 225 Latitude and Altitude. The format used shall be NMEA 0183, 227 as shown below: 229 Latitude: llll.ll,a (a=N or S) 231 Longitude: yyy.yy,b (b=E or W) 233 Altitude: xxxx.x (in meters) 235 Examples: 237 4916.46,N Latitude 49 deg. 16.45 min. North 239 12311.12,W Longitude 123 deg. 11.12 min. West 240 545.4,M Altitude, Metres, above mean sea level 242 This location, and the satellite position are used to 244 calculate the RCST-satellite path delay. 246 Note: The system.sysLocation object of MIB-II provides 248 physical location of the IDU unit." 250 ::= {installation 2} 252 oduAntennaSize OBJECT-TYPE 254 SYNTAX DisplayString 256 MAX-ACCESS read-write 258 STATUS current 260 DESCRIPTION 262 "This object gives the diameter of the antenna. This value 264 shall be given in centimeter. Defined at Installation. The 266 object can be used in conjunction with environmental 268 requirements. " 270 ::= {installation 3} 272 oduAntennaGain OBJECT-TYPE 274 SYNTAX Integer32 276 MAX-ACCESS read-write 277 STATUS current 279 DESCRIPTION 281 "This field describes the antenna peak gain of the ODU and 283 shall be defined by the installer. The gain shall be given 285 in tenth of dBi for more flexibility, i.e. 46.5 dBi will be 287 represented by 465. Defined at installation." 289 ::= {installation 4} 291 oduSspa OBJECT-TYPE 293 SYNTAX Integer32 295 MAX-ACCESS read-write 297 STATUS current 299 DESCRIPTION 301 "This field describes the SSPA installed in the ODU and 303 shall be defined by the installer. The power shall be given 305 in tenth of Watt for more flexibility, i.e. 0,5 W will be 307 represented by 5, 1 W by 10 and 2 W by 20. 309 Defined at installation." 311 ::= {installation 5} 313 oduTxType OBJECT-TYPE 314 SYNTAX DisplayString 316 MAX-ACCESS read-write 318 STATUS current 320 DESCRIPTION 322 "Describes the type of transmitter installed in the ODU." 324 ::= {installation 6} 326 oduRxType OBJECT-TYPE 328 SYNTAX DisplayString 330 MAX-ACCESS read-write 332 STATUS current 334 DESCRIPTION 336 "Describes the type of LNB installed in the ODU, with 338 information such as vendor type, ouput type (single, twin, 340 quad,), etc.. " 342 ::= {installation 7} 344 oduRxBand OBJECT-TYPE 346 SYNTAX INTEGER 348 MAX-ACCESS read-write 350 STATUS current 352 DESCRIPTION 354 "Describes whether High Band or Low Band is selected in 355 the LNB. Specifying High Band results in activation of a 357 18-26 kHz tone with 0.4-0.8 Vpp in the Rx IFL cable: 359 (0) - High Band 361 (1) - Low Band " 363 ::= {installation 8} 365 oduRxLO OBJECT-TYPE 367 SYNTAX Integer32 369 MAX-ACCESS read-write 371 STATUS current 373 DESCRIPTION 375 " Frequency of LNB Local Oscillator (in 100 Hz)" 377 ::= {installation 9} 379 oduTxLO OBJECT-TYPE 381 SYNTAX Integer32 383 MAX-ACCESS read-write 385 STATUS current 387 DESCRIPTION 389 "Frequency of BUC Local Oscillator (in 100 Hz) " 391 ::= {installation 10} 393 antennaAlignmentState OBJECT-TYPE 395 SYNTAX INTEGER 397 MAX-ACCESS read-write 399 STATUS current 401 DESCRIPTION 403 " Indicates the state: 405 (1)-Start; 407 (2)-Deny; 409 (3)-Continue; 411 (4)-Stop; 413 (5)-Success; 415 (6)-Fail" 417 ::= {installation 11} 419 cwFrequency OBJECT-TYPE 421 SYNTAX Integer32 423 MAX-ACCESS read-write 425 STATUS current 427 DESCRIPTION 429 "Frequency at which the carrier is put up (in 100 Hz). 431 Minimum required precision is 1 kHz." 433 ::= {installation 12} 435 cwMaxDuration OBJECT-TYPE 437 SYNTAX Integer32 439 MAX-ACCESS read-write 441 STATUS current 443 DESCRIPTION 445 "Time after which the carrier must be put down (in seconds)" 447 ::= {installation 13} 449 cwPower OBJECT-TYPE 451 SYNTAX Integer32 453 MAX-ACCESS read-write 455 STATUS current 457 DESCRIPTION 459 "Specified in tenth of dBm. This parameter allows for fine 461 (manual) tuning of the power setup. Minimum required precision 463 is 1 dBm. It must be configurable while CW signal is on. Once 465 the power has been properly adjusted, the power setup is stored 467 in rcstConfigRtnLinkDefIfLevel." 469 ::= {installation 14} 471 co-PolReading OBJECT-TYPE 473 SYNTAX Integer32 474 MAX-ACCESS read-write 476 STATUS current 478 DESCRIPTION 480 "Co-Pol measured value (in 0.1 dB)" 482 ::= {installation 15} 484 x-PolReadingOBJECT-TYPE 486 SYNTAX Integer32 488 MAX-ACCESS read-write 490 STATUS current 492 DESCRIPTION 494 "Cross-Pol measured value (in 0.1 dB)" 496 ::= {installation 16} 498 co-PolTarget OBJECT-TYPE 500 SYNTAX Integer32 502 MAX-ACCESS read-write 504 STATUS current 506 DESCRIPTION 508 "Co-Pol target (in 0.1 dB) " 510 ::= {installation 17} 512 x-PolTarget OBJECT-TYPE 514 SYNTAX Integer32 516 MAX-ACCESS read-write 518 STATUS current 520 DESCRIPTION 522 "Cross-Pol target (in 0.1 dB)" 524 ::= {installation 18} 526 standByDurationOBJECT-TYPE 528 SYNTAX Integer32 530 MAX-ACCESS read-write 532 STATUS current 534 DESCRIPTION 536 "Time to wait in stand-by mode (in seconds)" 538 ::= {installation 19} 540 targetEsNO OBJECT-TYPE 542 SYNTAX Integer32 544 MAX-ACCESS read-write 546 STATUS current 548 DESCRIPTION 550 "This value describes the wanted Es/N0 value that enables 552 operation of the return link with the required error 554 performance. The values shall be given in tenth of dB and 556 the initial value shall be equal to 7 dB. The range shall be 558 from 0 dBm to 31.5 dBm with a precision of 0,1 dB." 560 ::= {installation 20} 562 --- rcstSystem.options group 564 mpegTrf OBJECT-TYPE 566 SYNTAX INTEGER 568 MAX-ACCESS read-only 570 STATUS current 572 DESCRIPTION 574 " Indicates whether the MPEG_TRF SatLabs option is supported 576 by the RCST: 578 Not supported (0) 580 Supported (1)" 582 ::= {options 1} 584 coarseSync OBJECT-TYPE 586 SYNTAX INTEGER 587 MAX-ACCESS read-only 589 STATUS current 591 DESCRIPTION 593 " Indicates whether the COARSE_SYNC SatLabs option is supported 595 by the RCST: 597 Not supported (0) 599 Supported (1)" 601 ::= {options 2} 603 wideHopp OBJECT-TYPE 605 SYNTAX INTEGER 607 MAX-ACCESS read-only 609 STATUS current 611 DESCRIPTION 613 " Indicates whether the WIDE_HOPP SatLabs option is supported 615 by the RCST: 617 Not supported (0) 619 Supported (1)" 621 ::= {options 3} 623 fastHopp OBJECT-TYPE 625 SYNTAX INTEGER 627 MAX-ACCESS read-only 628 STATUS current 630 DESCRIPTION 632 "Indicates whether the FAST_HOPP SatLabs option is supported 634 by the RCST: 636 Not supported (0) 638 Supported (1)" 640 ::= {options 4} 642 dynamicMfTdma OBJECT-TYPE 644 SYNTAX INTEGER 646 MAX-ACCESS read-only 648 STATUS current 650 DESCRIPTION 652 "Indicates whether the Dynamic_MF_TDMA SatLabs option is 654 supported by the RCST: 656 Not supported (0) 658 Supported (1)" 660 ::= {options 5} 662 routeId OBJECT-TYPE 664 SYNTAX INTEGER 666 MAX-ACCESS read-only 668 STATUS current 670 DESCRIPTION 671 "Indicates whether the ROUTE_ID SatLabs option is supported 673 by the RCST: 675 Not supported (0) 677 Supported (1)" 679 ::= {options 6} 681 contentionSync OBJECT-TYPE 683 SYNTAX INTEGER 685 MAX-ACCESS read-only 687 STATUS current 689 DESCRIPTION 691 "Indicates whether the CONTENTION_SYNC SatLabs option is 693 supported by the RCST: 695 Not supported (0) 697 Supported (1)" 699 ::= {options 7} 701 qpskLow OBJECT-TYPE 703 SYNTAX INTEGER 705 MAX-ACCESS read-only 707 STATUS current 709 DESCRIPTION 711 "Indicates whether the QPSKLOW SatLabs option is supported 713 by the RCST: 715 Not supported (0) 717 Supported (1)" 719 ::= {options 8} 721 m16Apsk OBJECT-TYPE 723 SYNTAX INTEGER 725 MAX-ACCESS read-only 727 STATUS current 729 DESCRIPTION 731 "Indicates whether the 16APSK SatLabs option is supported 733 by the RCST: 735 Not supported (0) 737 Supported (1)" 739 ::= {options 9} 741 m32Apsk OBJECT-TYPE 743 SYNTAX INTEGER 745 MAX-ACCESS read-only 747 STATUS current 749 DESCRIPTION 751 "Indicates whether the 32APSK SatLabs option is supported 753 by the RCST: 755 Not supported (0) 757 Supported (1)" 759 ::= {options 10} 761 normalFec OBJECT-TYPE 763 SYNTAX INTEGER 765 MAX-ACCESS read-only 767 STATUS current 769 DESCRIPTION 771 "Indicates whether the NORMALFEC SatLabs option is supported 773 by the RCST: 775 Not supported (0) 777 Supported (1)" 779 ::= {options 11} 781 multiTs OBJECT-TYPE 783 SYNTAX INTEGER 785 MAX-ACCESS read-only 787 STATUS current 789 DESCRIPTION 791 "Indicates whether the MULTITS SatLabs option is supported 793 by the RCST: 795 Not supported (0) 797 Supported (1)" 799 ::= {options 12} 801 gsTs OBJECT-TYPE 803 SYNTAX INTEGER 805 MAX-ACCESS read-only 807 STATUS current 809 DESCRIPTION 811 "Indicates whether the GSTS SatLabs option is supported 813 by the RCST: 815 Not supported (0) 817 Supported (1)" 819 ::= {options 13} 821 enhQos OBJECT-TYPE 823 SYNTAX INTEGER 825 MAX-ACCESS read-only 827 STATUS current 829 DESCRIPTION 831 "Indicates whether the ENHQOS SatLabs option is supported 833 by the RCST: 835 Not supported (0) 837 Supported (1)" 839 ::= {options 14} 841 pep OBJECT-TYPE 843 SYNTAX INTEGER 844 MAX-ACCESS read-only 846 STATUS current 848 DESCRIPTION 850 "Indicates whether the PEP SatLabs option is supported 852 by the RCST: 854 Not supported (0) 856 Supported (1)" 858 ::= {options 15} 860 http OBJECT-TYPE 862 SYNTAX INTEGER 864 MAX-ACCESS read-only 866 STATUS current 868 DESCRIPTION 870 "Indicates whether the HTTP SatLabs option is supported 872 by the RCST: 874 Not supported (0) 876 Supported (1)" 878 ::= {options 16} 880 ftp OBJECT-TYPE 882 SYNTAX INTEGER 884 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 889 "Indicates whether the FTP SatLabs option is supported by 891 the RCST: 893 Not supported (0) 895 Supported (1)" 897 ::= {options 17} 899 dhcp OBJECT-TYPE 901 SYNTAX INTEGER 903 MAX-ACCESS read-only 905 STATUS current 907 DESCRIPTION 909 " Indicates whether the DHCP SatLabs option is supported by 911 the RCST: 913 Not supported (0) 915 Supported (1)" 917 ::= {options 18} 919 dns OBJECT-TYPE 921 SYNTAX INTEGER 923 MAX-ACCESS read-only 925 STATUS current 927 DESCRIPTION 929 "Indicates whether the DNS SatLabs option is supported by 930 the RCST: 932 Not supported (0) 934 Supported (1)" 936 ::= {options 19} 938 avbdcRep OBJECT-TYPE 940 SYNTAX INTEGER 942 MAX-ACCESS read-only 944 STATUS current 946 DESCRIPTION 948 "Indicates whether the AVBDC_REP SatLabs option is supported by 950 the RCST: 952 Not supported (0) 954 Supported (1)" 956 ::= {options 20} 958 chIdStrict OBJECT-TYPE 960 SYNTAX INTEGER 962 MAX-ACCESS read-only 964 STATUS current 966 DESCRIPTION 968 "Indicates whether the CHID_STRICT SatLabs option is supported 970 by the RCST: 972 Not supported (0) 973 Supported (1)" 975 ::= {options 21} 977 rcstPara OBJECT-TYPE 979 SYNTAX INTEGER 981 MAX-ACCESS read-only 983 STATUS current 985 DESCRIPTION 987 "Indicates whether the RCST_PARA SatLabs option is supported 989 by the RCST: 991 Not supported (0) 993 Supported (1)" 995 ::= {options 22} 997 nlid OBJECT-TYPE 999 SYNTAX INTEGER 1001 MAX-ACCESS read-only 1003 STATUS current 1005 DESCRIPTION 1007 "Indicates whether the NLID SatLabs option is supported by 1009 the RCST: 1011 Not supported (0) 1013 Supported (1)" 1015 ::= {options 23} 1017 snmpAll OBJECT-TYPE 1019 SYNTAX INTEGER 1021 MAX-ACCESS read-only 1023 STATUS current 1025 DESCRIPTION 1027 "Indicates whether the SNMPALL SatLabs option is supported 1029 by the RCST: 1031 Not supported (0) 1033 Supported (1)" 1035 ::= {options 24} 1037 installLog OBJECT-TYPE 1039 SYNTAX INTEGER 1041 MAX-ACCESS read-only 1043 STATUS current 1045 DESCRIPTION 1047 "Indicates whether the INSTALL_LOG SatLabs option is supported 1049 by the RCST: 1051 Not supported (0) 1053 Supported (1)" 1055 ::= {options 25} 1057 fwdLinkStatus OBJECT-TYPE 1059 SYNTAX INTEGER 1061 MAX-ACCESS read-only 1063 STATUS current 1065 DESCRIPTION 1067 "Indicates whether the FWDLINKSTATUS SatLabs option is 1069 supported by the RCST: 1071 Not supported (0) 1073 Supported (1)" 1075 ::= {options 26} 1077 enhClassifier OBJECT-TYPE 1079 SYNTAX INTEGER 1081 MAX-ACCESS read-only 1083 STATUS current 1085 DESCRIPTION 1087 "Indicates whether the ENHCLASSIFIER SatLabs option is 1089 supported by the RCST: 1091 Not supported (0) 1093 Supported (1)" 1095 ::= {options 27} 1097 ---- rcstConfig.network group 1099 oamIpAddr OBJECT-TYPE 1101 SYNTAX IpAddress 1103 MAX-ACCESS read-write 1105 STATUS current 1107 DESCRIPTION 1109 "OAM IP Address of the RCST. This object used with both ip and 1111 interfaces MIB-II subgroups determines uniquely the interface 1113 through which OAM traffic is passing through. 1115 Note that the OAM IP address may be statically or dynamically 1117 assigned. It is system dependent whether the OAM IP address 1119 and the Traffic IP address are the same address." 1121 ::= {network 1} 1123 oamIpNetworkMask OBJECT-TYPE 1125 SYNTAX IpAddress 1127 MAX-ACCESS read-write 1129 STATUS current 1131 DESCRIPTION 1133 "Network Mask for the OAM IP Address." 1135 ::= {network 2} 1137 oamIpAddrAssign OBJECT-TYPE 1139 SYNTAX INTEGER 1141 MAX-ACCESS read-write 1143 STATUS current 1145 DESCRIPTION 1147 "Identifies whether the OAM IP address is statically 1149 ('static' - 1) or dynamically ('dynamic' - 2) assigned." 1151 ::= {network 3} 1153 lanIpAddress OBJECT-TYPE 1155 SYNTAX IpAddress 1157 MAX-ACCESS read-write 1159 STATUS current 1161 DESCRIPTION 1163 "IP address of the LAN interface" 1165 ::= {network 4} 1167 lanIpMask OBJECT-TYPE 1169 SYNTAX IpAddress 1171 MAX-ACCESS read-write 1173 STATUS current 1175 DESCRIPTION 1176 "Mask for the LAN interface" 1178 ::= {network 5} 1180 airInterfaceDefaultGateway OBJECT-TYPE 1182 SYNTAX IpAddress 1184 MAX-ACCESS read-write 1186 STATUS current 1188 DESCRIPTION 1190 "Default Gateway for the air interface" 1192 ::= {network 6} 1194 dnsServerIpAddress OBJECT-TYPE 1196 SYNTAX IpAddress 1198 MAX-ACCESS read-write 1200 STATUS current 1202 DESCRIPTION 1204 "IP address of the DNS server in the NCC." 1206 ::= {network 7} 1208 nccMgtIpAddress OBJECT-TYPE 1210 SYNTAX IpAddress 1212 MAX-ACCESS read-write 1214 STATUS current 1216 DESCRIPTION 1217 "IP address of the management server in the NCC." 1219 ::= {network 8} 1221 configFileDownloadUrl OBJECT-TYPE 1223 SYNTAX DisplayString 1225 MAX-ACCESS read-write 1227 STATUS current 1229 DESCRIPTION 1231 "Full path name for the configuration file download. 1233 It includes the protocol type (tftp or ftp) and the 1235 associated server IP address or hostname. Hostname can 1237 only be used if DNS is supported by the RCST." 1239 ::= {network 9} 1241 installLogFileDownloadUrl OBJECT-TYPE 1243 SYNTAX DisplayString 1245 MAX-ACCESS read-write 1247 STATUS current 1249 DESCRIPTION 1251 "Full path of the installation log file to download. 1253 It includes the protocol type (tftp or ftp) and the 1255 associated server IP address or hostname. Hostname can 1257 only be used if DNS is supported by the RCST. The installation 1259 log file can be created on the installer's computer 1260 and downloaded to the RCST." 1262 ::= {network 10} 1264 configFileUploadUrl OBJECT-TYPE 1266 SYNTAX DisplayString 1268 MAX-ACCESS read-write 1270 STATUS current 1272 DESCRIPTION 1274 "Full path name for the configuration file upload. 1276 It includes the protocol type (tftp or ftp) and the 1278 associated server IP address or hostname.Hostname can 1280 only be used if DNS is supported by the RCST." 1282 ::= {network 11} 1284 logFileUploadUrl OBJECT-TYPE 1286 SYNTAX DisplayString 1288 MAX-ACCESS read-write 1290 STATUS current 1292 DESCRIPTION 1294 "Full path of the event log file. It includes the protocol 1296 type (tftp or ftp) and the associated server IP address 1298 or hostname. Hostname can only be used if DNS is supported 1300 by the RCST." 1302 ::= {network 12} 1304 installLogFileUploadUrl OBJECT-TYPE 1306 SYNTAX DisplayString 1308 MAX-ACCESS read-write 1310 STATUS current 1312 DESCRIPTION 1314 "Full path of the installation log file. It includes the 1316 protocol type (tftp or ftp) and the associated server 1318 IP address or hostname. Hostname can only be used if DNS is 1320 supported by the RCST. The installation log file can be 1322 retrieved from the RCST by the NCC or by the installer 1324 via the LAN." 1326 ::= {network 13} 1328 ---- rcstConfig.rtnLink group 1330 maxEirp OBJECT-TYPE 1332 SYNTAX Integer32 1334 MAX-ACCESS read-write 1336 STATUS current 1338 DESCRIPTION 1340 "Maximum allowed EIRP in tenth of dBm on the return link." 1342 ::= {rtnLink 1} 1344 defIfLevel OBJECT-TYPE 1346 SYNTAX Integer32 1348 MAX-ACCESS read-write 1350 STATUS current 1352 DESCRIPTION 1354 "Default transmitted IF power level, specified in tenth of dBm, 1356 out of the IDU for sending a CSC burst at RCST reboot or 1358 power on. Applies to all signals transmitted by RCST 1360 (CW and traffic) immediately." 1362 ::= {rtnLink 2} 1364 ---- rcstConfig.fwdLink group 1366 ----------StartConfig subgroup (1) 1368 startConfig OBJECT IDENTIFIER 1370 ::={fwdLink 1} 1372 startConfigTable OBJECT-TYPE 1374 SYNTAX SEQUENCE OF StartConfigEntry 1376 MAX-ACCESS not-accessible 1378 STATUS current 1379 DESCRIPTION 1381 "Lists Forward Links attachment points (e.g. different for 1382 installation and operation). The table describes the forward link 1383 parameters used for the start-up stream with the NCC." 1385 ::={startConfig 1} 1387 startConfigEntry OBJECT-TYPE 1389 SYNTAX StartConfigEntry 1391 MAX-ACCESS not-accessible 1393 STATUS current 1395 DESCRIPTION 1397 "An entry in the Forward Link StartConfig table." 1399 INDEX { popId } 1401 ::= { startConfigTable 1 } 1403 StartConfigEntry ::= SEQUENCE { 1405 popId Integer32, 1407 freq Integer32, 1409 polar INTEGER, 1411 standard INTEGER, 1413 modulation INTEGER, 1415 rolloff INTEGER, 1417 symbRate Integer32, 1419 innerFec INTEGER, 1421 startConfigStatus RowStatus 1423 } 1425 popId OBJECT-TYPE 1427 SYNTAX Integer32 1429 MAX-ACCESS read-only 1431 STATUS current 1433 DESCRIPTION 1435 "Population identifier associated with the start-up 1437 forward link: 1439 -1: any (auto) 1441 0-n: specific StartPopId" 1443 ::={startConfigEntry 1} 1445 freq OBJECT-TYPE 1447 SYNTAX Integer32 1449 MAX-ACCESS read-only 1451 STATUS current 1453 DESCRIPTION 1455 "Frequency of the start transponder carrying a 1457 Network Information Table to which any RCST shall 1459 trigger to acquire forward link. ts value shall be given 1461 in multiple of 100 kHz." 1463 ::={startConfigEntry 2} 1465 polar OBJECT-TYPE 1467 SYNTAX INTEGER 1469 MAX-ACCESS read-only 1471 STATUS current 1473 DESCRIPTION 1475 "2-bit field giving the polarization of the start transponder 1477 carrying an Network Information Table to which any RCST shall 1479 trigger to acquire forward link: 1481 00: linear and horizontal 1483 01: linear and vertical 1485 10: circular left 1487 11: circular right" 1489 ::={startConfigEntry 3} 1491 standard OBJECT-TYPE 1493 SYNTAX INTEGER { 1495 auto (-1), 1497 dvbs (0), 1499 dvbs2 (1) 1501 } 1503 MAX-ACCESS read-only 1505 STATUS current 1507 DESCRIPTION 1509 "Specifies the transmission standard applied on the start 1510 transponder. The start transponder carries a 1512 Network Information Table that the RCST uses for acquiring 1514 the forward link signaling. Supported values are: 1516 -1: any (auto) 1518 0: DVB-S 1520 1: DVB-S2 1522 2-n: reserved " 1524 ::={startConfigEntry 4} 1526 modulation OBJECT-TYPE 1528 SYNTAX INTEGER { 1530 auto (0), 1532 qpsk (1), 1534 m8psk (2) 1536 } 1538 MAX-ACCESS read-only 1540 STATUS current 1542 DESCRIPTION 1544 "Specifies the modulation used on the start transponder 1546 carrying a NIT to which any RCST shall trigger to acquire 1548 forward link. 1550 0: any (auto) 1552 1: QPSK 1554 2: 8PSK 1556 Other values shall be as specified in the NIT." 1558 ::={startConfigEntry 5} 1560 rolloff OBJECT-TYPE 1562 SYNTAX INTEGER { 1564 auto (0), 1566 r035 (1), 1568 r025 (2), 1570 r020 (3) 1572 } 1574 MAX-ACCESS read-only 1576 STATUS current 1578 DESCRIPTION 1580 "Specifies the roll-off applied on the start transponder. 1582 The start transponder carries a Network Information Table 1584 that the RCST uses for acquiring the forward link signaling. 1585 This object is only relevant when the transmission standard is 'DVB- 1586 S2'. Supported values are: 1588 0: any (auto) 1590 1: 0.35 1592 2: 0.25 1594 3: 0.20 1596 4-n: reserved" 1598 ::={startConfigEntry 6} 1600 symbRate OBJECT-TYPE 1602 SYNTAX Integer32 1604 MAX-ACCESS read-only 1606 STATUS current 1608 DESCRIPTION 1610 "Specifies the symbol rate on the start transponder 1612 carrying a Network Information Table to which any RCST 1614 shall trigger to acquire forward link. Its value shall be 1616 given in multiple of 100 symbol/s." 1618 ::={startConfigEntry 7} 1620 innerFec OBJECT-TYPE 1622 SYNTAX INTEGER 1624 MAX-ACCESS read-only 1626 STATUS current 1628 DESCRIPTION 1630 "Specifies the inner Forward Error Correction used on the 1632 start transponder carrying a NIT to which any RCST shall 1634 trigger to acquire forward link. 1636 Supported values are: 1638 0: any (auto) 1640 1: 1/2 1642 2: 2/3 1644 3: 3/4 1645 4: 5/6 1647 5: 7/8 1649 6: 8/9 1651 7: 3/5 1653 8: 4/5 1655 9: 9/10 1657 10-14: reserved 1659 15: No inner code " 1661 ::={startConfigEntry 8} 1663 startConfigStatus OBJECT-TYPE 1665 SYNTAX RowStatus 1667 MAX-ACCESS read-only 1669 STATUS current 1671 DESCRIPTION 1673 "Standard SNMP row status" 1675 DEFVAL { active } 1677 ::={startConfigEntry 9} 1679 --Status subgroup (2) 1681 status OBJECT IDENTIFIER 1683 ::={fwdLink 2} 1684 statusTable OBJECT-TYPE 1686 SYNTAX SEQUENCE OF StatusEntry 1688 MAX-ACCESS not-accessible 1690 STATUS current 1692 DESCRIPTION 1694 "This table describes the current status of Forward Link 1695 interfaces." 1697 ::={status 1} 1699 statusEntry OBJECT-TYPE 1701 SYNTAX StatusEntry 1703 MAX-ACCESS not-accessible 1705 STATUS current 1707 DESCRIPTION 1709 "An entry in the Forward Link Status table. Each entry is 1710 associated with a physical interface. A RCST SHALL support at least 1711 one entry." 1713 INDEX { ifIndex } 1715 ::= { statusTable 1 } 1717 StatusEntry ::= SEQUENCE { 1719 ifIndex Integer32, 1721 netId Integer32, 1722 transmissionStandard INTEGER, 1724 frequency Integer32, 1726 polar INTEGER, 1728 fecInner INTEGER, 1730 symbolRate Integer32, 1732 rolloff INTEGER, 1734 modulation INTEGER, 1736 fecFrame INTEGER, 1738 pilot INTEGER, 1740 ber Integer32, 1742 cnr Integer32, 1744 statusStatus INTEGER 1746 } 1748 ifIndex OBJECT-TYPE 1750 SYNTAX Integer32 1752 MAX-ACCESS read-only 1754 STATUS current 1756 DESCRIPTION 1758 "Cross reference to the interface table" 1760 ::={statusEntry 1} 1762 netId OBJECT-TYPE 1764 SYNTAX Integer32 1765 MAX-ACCESS read-only 1767 STATUS current 1769 DESCRIPTION 1771 "Interactive network identifier of the forward 1773 link (from RMT)" 1775 ::={statusEntry 2} 1777 transmissionStandard OBJECT-TYPE 1779 SYNTAX INTEGER { 1781 dvbs (0), 1783 dvbs2ccm (1), 1785 dvbs2acm (2) 1787 } 1789 MAX-ACCESS read-write 1791 STATUS current 1793 DESCRIPTION 1795 "Specifies the transmission standard applied on the forward link. 1796 Supported values are (from RMT): 1798 0: DVB-S 1800 1: DVB-S2 using CCM 1802 2: DVB-S2 using ACM 1804 3: reserved" 1806 ::={statusEntry 3} 1808 frequency OBJECT-TYPE 1810 SYNTAX Integer32 1812 MAX-ACCESS read-write 1814 STATUS current 1816 DESCRIPTION 1818 "Frequency of the forward link (from RMT). Its value shall 1820 be given in multiple of 100 kHz." 1822 ::={statusEntry 4} 1824 polar OBJECT-TYPE 1826 SYNTAX INTEGER 1828 MAX-ACCESS read-write 1830 STATUS current 1832 DESCRIPTION 1834 "2-bit field giving the polarization of the forward link 1836 (from RMT): 1838 00: linear and horizontal 1840 01: linear and vertical 1842 10: circular left 1844 11: circular right" 1846 ::={statusEntry 5} 1848 fecInner OBJECT-TYPE 1850 SYNTAX INTEGER 1851 MAX-ACCESS read-write 1853 STATUS current 1855 DESCRIPTION 1857 "Specifies the inner Forward Error Correction of the 1859 forward link (from RMT). This object is not used for DVB-S2. 1861 Supported values are: 1863 0: 1/2 1865 1: 2/3 1867 2: 3/4 1869 3: 5/6 1871 4: 7/8 1873 5-14: reserved 1875 15: No inner code" 1877 ::={statusEntry 6} 1879 symbolRate OBJECT-TYPE 1881 SYNTAX Integer32 1883 MAX-ACCESS read-write 1885 STATUS current 1887 DESCRIPTION 1889 "Specifies the symbol rate of the forward link (from RMT). 1891 Its value shall be given in multiple of 100 symbol/s." 1893 ::={statusEntry 7} 1895 rolloff OBJECT-TYPE 1897 SYNTAX INTEGER 1899 MAX-ACCESS read-write 1901 STATUS current 1903 DESCRIPTION 1905 "Specifies the roll-off applied on the forward link 1907 (from RMT). This object is only relevant when the 1909 transmission standard is 'DVB-S2'. Supported values are: 1911 0: undefined 1913 1: 0.20 1915 2: 0.25 1917 3: 0.35 1919 4-1: reserved" 1921 ::={statusEntry 8} 1923 modulation OBJECT-TYPE 1925 SYNTAX INTEGER 1927 MAX-ACCESS read-write 1929 STATUS current 1931 DESCRIPTION 1933 "Indicates the modulation on the forward link. 1935 0: undefined 1937 1: QPSK (DVB-S) 1939 2: 8PSK 1940 3: reserved 1942 For DVB-S2 with CCM, the MODCOD is fixed. The MODCOD value is 1944 obtained from the PL Header of the PL frame every time the RCST 1946 acquires the FL. The MODCOD corresponds to the values as defined 1948 in the DVB-S2 standard: 1950 1: QPSK 1/4 1952 2: QPSK 1/3 1954 3: QPSK 2/5 1956 etc. 1958 For DVB-S2 with ACM, the RCST updates the modulation object 1960 from the PL Header every 10 sec." 1962 ::={statusEntry 9} 1964 fecFrame OBJECT-TYPE 1966 SYNTAX INTEGER { 1968 shortframe (0), 1970 longframe (1) 1972 } 1974 MAX-ACCESS read-only 1976 STATUS current 1978 DESCRIPTION 1980 "Indicates the frame size of the forward link (from PL 1981 header of DVB-S2). This object is only relevant when the 1983 transmission standard is 'DVB-S2'. Supported values are: 1985 0: Normal frame 1987 1: Short frame 1989 For DVB-S2 with CCM, the frame length is fixed. It is updated 1991 from the PL Header every time the RCST acquire the FL. 1993 For DVB-S2 with ACM, the RCST updates the frame length object 1995 from the PL Header every 10 sec." 1997 ::={statusEntry 10} 1999 pilot OBJECT-TYPE 2001 SYNTAX INTEGER { 2003 notused (0), 2005 used (1) 2007 } 2009 MAX-ACCESS read-only 2011 STATUS current 2013 DESCRIPTION 2015 "Indicates if pilot mode is used on the forward link (from PL 2017 header of DVB-S2). This object is only relevant when the 2019 transmission standard is 'DVB-S2'. Supported values are: 2021 0: Not used 2023 1: In use 2025 For DVB-S2 with CCM, the pilot is fixed. It is updated from 2026 the PL Header every time the RCST acquire the FL. 2028 For DVB-S2 with ACM, the RCST updates the pilot object from 2030 the PL Header every 10 sec." 2032 ::={statusEntry 11} 2034 ber OBJECT-TYPE 2036 SYNTAX Integer32 2038 MAX-ACCESS read-only 2040 STATUS current 2042 DESCRIPTION 2044 "Provides the RCST BER on the Forward Link in log10 units." 2046 ::={statusEntry 12} 2048 cnr OBJECT-TYPE 2050 SYNTAX Integer32 2052 MAX-ACCESS read-only 2054 STATUS current 2056 DESCRIPTION 2058 "Provides the RCST CNR on the Forward Link in 0.1 dB units." 2060 ::={statusEntry 13} 2062 statusStatus OBJECT-TYPE 2064 SYNTAX RowStatus 2065 MAX-ACCESS read-only 2067 STATUS current 2069 DESCRIPTION 2071 "Standard SNMP row status" 2073 DEFVAL { active } 2075 ::={statusEntry 14} 2077 ---- rcstConfig.qos group 2079 pktClassTable OBJECT-TYPE 2081 SYNTAX SEQUENCE OF PktClassEntry 2083 MAX-ACCESS not-accessible 2085 STATUS current 2087 DESCRIPTION 2089 "This table describes the packet classification used in the 2090 DVB-RCS terminal. The number of entries is specified by 2091 PktClassIndex. " 2093 ::={qos 1} 2095 pktClassEntry OBJECT-TYPE 2097 SYNTAX PktClassEntry 2099 MAX-ACCESS not-accessible 2101 STATUS current 2102 DESCRIPTION 2104 "An entry in the packet classification table. " 2106 INDEX { pktClassIndex } 2108 ::= { pktClassTable 1 } 2110 PktClassEntry ::= SEQUENCE { 2112 pktClassIndex INTEGER, 2114 pktClassDscpLow INTEGER, 2116 pktClassDscpHigh INTEGER, 2118 pktClassDscpMarkValue INTEGER, 2120 pktClassIPProtocol INTEGER, 2122 pktClassIPSrcAddr IpAddress, 2124 pktClassIPSrcAddrMask IpAddress, 2126 pktClassIPDstAddr IpAddress, 2128 pktClassIPDstAddrMask IpAddress, 2130 pktClassSrcPortLow INTEGER, 2132 pktClassSrcPortHigh INTEGER, 2134 pktClassDstPortLow INTEGER, 2136 pktClassDstPortHigh INTEGER, 2138 pktClassDstMacAddr PhysAddress, 2140 pktClassDstMacMask PhysAddress, 2142 pktClassSrcMacAddr PhysAddress, 2144 pktClassVlanId INTEGER, 2146 pktClassVlanCoS INTEGER, 2147 pktClassPhbAssociation INTEGER, 2149 pktClassStatus INTEGER 2151 } 2153 pktClassIndex OBJECT-TYPE 2155 SYNTAX INTEGER 2157 MAX-ACCESS read-only 2159 STATUS current 2161 DESCRIPTION 2163 "Index" 2165 ::={pktClassEntry 1} 2167 pktClassDscpLow OBJECT-TYPE 2169 SYNTAX INTEGER 2171 MAX-ACCESS read-write 2173 STATUS current 2175 DESCRIPTION 2177 "This object specifies the low value of a range 2179 of DSCP values to which a packet is compared. " 2181 ::={pktClassEntry 2} 2183 pktClassDscpHigh OBJECT-TYPE 2185 SYNTAX INTEGER 2187 MAX-ACCESS read-write 2188 STATUS current 2190 DESCRIPTION 2192 "This object specifies the high value of a range of 2194 DSCP values to which a packet is compared." 2196 ::={pktClassEntry 3} 2198 pktClassDscpMarkValue OBJECT-TYPE 2200 SYNTAX INTEGER 2202 MAX-ACCESS read-write 2204 STATUS current 2206 DESCRIPTION 2208 "This object is the DSCP value used to mark the packet, 2210 -1 indicates no DSCP marking, possible DSCP marks values 2212 are (0..63)" 2214 ::={pktClassEntry 4} 2216 pktClassIPProtocol OBJECT-TYPE 2218 SYNTAX INTEGER 2220 MAX-ACCESS read-write 2222 STATUS current 2224 DESCRIPTION 2226 "This object specifies the IP protocol to which a 2228 packet is compared." 2230 ::={pktClassEntry 5} 2232 pktClassIPSrcAddr OBJECT-TYPE 2234 SYNTAX IpAddress 2236 MAX-ACCESS read-write 2238 STATUS current 2240 DESCRIPTION 2242 "This object specifies the IP source address to which a 2244 packet is compared." 2246 ::={pktClassEntry 6} 2248 pktClassIPSrcAddrMask OBJECT-TYPE 2250 SYNTAX IpAddress 2252 MAX-ACCESS read-write 2254 STATUS current 2256 DESCRIPTION 2258 "This object specifies which bits of the IP source 2260 address will be matched." 2262 ::={pktClassEntry 7} 2264 pktClassIPDstAddr OBJECT-TYPE 2266 SYNTAX IpAddress 2268 MAX-ACCESS read-write 2270 STATUS current 2271 DESCRIPTION 2273 "This object specifies the IP destination address to which a 2275 packet is compared." 2277 ::={pktClassEntry 8} 2279 pktClassIPDstAddrMask OBJECT-TYPE 2281 SYNTAX IpAddress 2283 MAX-ACCESS read-write 2285 STATUS current 2287 DESCRIPTION 2289 "This object specifies which bits of the IP destination 2291 address will be matched." 2293 ::={pktClassEntry 9} 2295 pktClassSrcPortLow OBJECT-TYPE 2297 SYNTAX INTEGER 2299 MAX-ACCESS read-write 2301 STATUS current 2303 DESCRIPTION 2305 "This object specifies the low range of the source 2307 port to which a packet is compared. " 2309 ::={pktClassEntry 10} 2311 pktClassSrcPortHigh OBJECT-TYPE 2312 SYNTAX INTEGER 2314 MAX-ACCESS read-write 2316 STATUS current 2318 DESCRIPTION 2320 "This object specifies the high range of the source 2322 port to which a packet is compared. " 2324 ::={pktClassEntry 11} 2326 pktClassDstPortLow OBJECT-TYPE 2328 SYNTAX INTEGER 2330 MAX-ACCESS read-write 2332 STATUS current 2334 DESCRIPTION 2336 "This object specifies the low range of the destination 2338 port to which a packet is compared. " 2340 ::={pktClassEntry 12} 2342 pktClassDstPortHigh OBJECT-TYPE 2344 SYNTAX INTEGER 2346 MAX-ACCESS read-write 2348 STATUS current 2350 DESCRIPTION 2352 "This object specifies the high range of the destination 2354 port to which a packet is compared. " 2356 ::={pktClassEntry 13} 2358 pktClassDstMacAddr OBJECT-TYPE 2360 SYNTAX PhysAddress 2362 MAX-ACCESS read-write 2364 STATUS current 2366 DESCRIPTION 2368 "This object specifies the destination MAC address to 2370 which a packet is compared. " 2372 ::={pktClassEntry 14} 2374 pktClassDstMacMask OBJECT-TYPE 2376 SYNTAX PhysAddress 2378 MAX-ACCESS read-write 2380 STATUS current 2382 DESCRIPTION 2384 "This object specifies the mask of the destination MAC address 2386 to which a packet is compared. " 2388 ::={pktClassEntry 15} 2390 pktClassSrcMacAddr OBJECT-TYPE 2392 SYNTAX PhysAddress 2394 MAX-ACCESS read-write 2396 STATUS current 2397 DESCRIPTION 2399 "This object specifies the source MAC address to which a packet 2401 is compared." 2403 ::={pktClassEntry 16} 2405 pktClassVlanId OBJECT-TYPE 2407 SYNTAX INTEGER (0..7) 2409 MAX-ACCESS read-write 2411 STATUS current 2413 DESCRIPTION 2415 "This object specifies the VLAN id to which a packet is 2416 compared." 2418 ::={pktClassEntry 17} 2420 pktClassVlanCoS OBJECT-TYPE 2422 SYNTAX INTEGER 2424 MAX-ACCESS read-write 2426 STATUS current 2428 DESCRIPTION 2430 "This object specifies the VLAN Class of Service (CoS) 2432 to which a packet is compared. " 2434 ::={pktClassEntry 18} 2436 pktClassPhbAssociation OBJECT-TYPE 2437 SYNTAX INTEGER 2439 MAX-ACCESS read-write 2441 STATUS current 2443 DESCRIPTION 2445 "Associate the filter entry to a specific PHB (refer to 2446 PhbIndex)." 2448 ::={pktClassEntry 19} 2450 pktClassStatus OBJECT-TYPE 2452 SYNTAX RowStatus 2454 MAX-ACCESS read-only 2456 STATUS current 2458 DESCRIPTION 2460 "Standard SNMP row status" 2462 ::={pktClassEntry 20} 2464 -----PhbMappingTable 2466 phbMappingTable OBJECT-TYPE 2468 SYNTAX SEQUENCE OF PhbMappingEntry 2470 MAX-ACCESS not-accessible 2472 STATUS current 2474 DESCRIPTION 2475 "This table is a list of PHB MIB entries. This class 2476 describes the PHB mapping with the Request Class. The number of 2477 entries is specified by PhbIndex." 2479 ::={qos 2} 2481 phbMappingEntry OBJECT-TYPE 2483 SYNTAX PhbMappingEntry 2485 MAX-ACCESS not-accessible 2487 STATUS current 2489 DESCRIPTION 2491 "An entry in the PHB mapping table." 2493 INDEX { phbIndex } 2495 ::= { phbMappingTable 1 } 2497 PhbMappingEntry ::= SEQUENCE { 2499 phbIndex INTEGER, 2501 phbIdentifier INTEGER, 2503 phbName DisplayString, 2505 phbRequestClassAssociation INTEGER, 2507 phbMappingRowStatus INTEGER 2509 } 2511 phbIndex OBJECT-TYPE 2513 SYNTAX INTEGER 2515 MAX-ACCESS read-only 2516 STATUS current 2518 DESCRIPTION 2520 "Index of the PHB mapping table. A maximum of 64 entries can 2521 be created." 2523 ::={phbMappingEntry 1} 2525 phbIdentifier OBJECT-TYPE 2527 SYNTAX INTEGER (0..63) 2529 MAX-ACCESS read-write 2531 STATUS current 2533 DESCRIPTION 2535 "Identification of the PHB (0..63)." 2537 ::={phbMappingEntry 2} 2539 phbName OBJECT-TYPE 2541 SYNTAX DisplayString 2543 MAX-ACCESS read-write 2545 STATUS current 2547 DESCRIPTION 2549 "Name of the PHB" 2551 ::={phbMappingEntry 3} 2553 phbRequestClassAssociation OBJECT-TYPE 2555 SYNTAX INTEGER (0..15) 2556 MAX-ACCESS read-write 2558 STATUS current 2560 DESCRIPTION 2562 "This object is an association with this PHB 2564 and a Request class entry in the Request class table. 2566 (refer to a Request Class index)" 2568 ::={phbMappingEntry 4} 2570 phbMappingRowStatus OBJECT-TYPE 2572 SYNTAX RowStatus 2574 MAX-ACCESS read-only 2576 STATUS current 2578 DESCRIPTION 2580 "Standard SNMP row status" 2582 DEFVAL { active } 2584 ::={phbMappingEntry 5} 2586 ----qos.RequestClassTable 2588 requestClassTable OBJECT-TYPE 2590 SYNTAX SEQUENCE OF RequestClassEntry 2592 MAX-ACCESS not-accessible 2594 STATUS current 2595 DESCRIPTION 2597 "This table is a list of Request class entries. This class 2598 describes the layer 2 QoS objects. The number of entries is specified 2599 by RequestClassIndex. " 2601 ::={qos 3} 2603 requestClassEntry OBJECT-TYPE 2605 SYNTAX RequestClassEntry 2607 MAX-ACCESS not-accessible 2609 STATUS current 2611 DESCRIPTION 2613 "An entry in the Request class table." 2615 INDEX { requestClassIndex,requestClassPidIndex } 2617 ::= { requestClassTable 1 } 2619 RequestClassEntry ::= SEQUENCE { 2621 requestClassIndex INTEGER, 2623 requestClassName DisplayString, 2625 requestClassChanId INTEGER, 2627 requestClassVccVpi INTEGER, 2629 requestClassVccVci INTEGER, 2631 requestClassPidIndex INTEGER, 2633 requestClassPidValue INTEGER, 2635 requestClassCra INTEGER, 2637 requestClassRbdcMax INTEGER, 2639 requestClassRbdcTimeout INTEGER, 2641 requestClassVbdcMax INTEGER, 2643 requestClassVbdcTimeout INTEGER, 2645 requestClassVbdcMaxBackLog INTEGER, 2647 requestClassAvbdcRepTime INTEGER, 2649 requestClassRowStatus INTEGER 2651 } 2653 requestClassIndex OBJECT-TYPE 2655 SYNTAX INTEGER 2657 MAX-ACCESS read-only 2659 STATUS current 2661 DESCRIPTION 2663 "Index of the Request Class table. A maximum of 16 entries 2664 can be created." 2666 ::={requestClassEntry 1} 2668 requestClassName OBJECT-TYPE 2670 SYNTAX DisplayString 2672 MAX-ACCESS read-only 2674 STATUS current 2676 DESCRIPTION 2678 "Name of the Request class." 2680 ::={requestClassEntry 2} 2682 requestClassChanId OBJECT-TYPE 2684 SYNTAX INTEGER 2686 MAX-ACCESS read-only 2688 STATUS current 2690 DESCRIPTION 2692 "Channel id of the Request class." 2694 ::={requestClassEntry 3} 2696 requestClassVccVpi OBJECT-TYPE 2698 SYNTAX INTEGER 2700 MAX-ACCESS read-only 2702 STATUS current 2704 DESCRIPTION 2706 "Defines VPI used for the Request class (ATM profile)." 2708 ::={requestClassEntry 4} 2710 requestClassVccVci OBJECT-TYPE 2712 SYNTAX INTEGER 2714 MAX-ACCESS read-only 2716 STATUS current 2718 DESCRIPTION 2720 "Defines VCI used for the Request class (ATM profile)." 2722 ::={requestClassEntry 5} 2724 requestClassPidIndex OBJECT-TYPE 2726 SYNTAX INTEGER 2728 MAX-ACCESS read-only 2730 STATUS current 2732 DESCRIPTION 2734 "Index of the Request class Pid table. Only one Pid entry is 2736 required for short term QoS support " 2738 ::={requestClassEntry 6} 2740 requestClassPidValue OBJECT-TYPE 2742 SYNTAX INTEGER 2744 MAX-ACCESS read-write 2746 STATUS current 2748 DESCRIPTION 2750 "Define the PID used for the Request Class. 2752 One PID per RC will be used for the short term QoS support. " 2754 ::={requestClassEntry 7} 2756 requestClassCra OBJECT-TYPE 2758 SYNTAX INTEGER 2760 MAX-ACCESS read-write 2762 STATUS current 2764 DESCRIPTION 2765 "Define CRA level for the Request class in bit per second 2766 (b/s)." 2768 ::={requestClassEntry 8} 2770 requestClassRbdcMax OBJECT-TYPE 2772 SYNTAX INTEGER 2774 MAX-ACCESS read-write 2776 STATUS current 2778 DESCRIPTION 2780 " Max RBDC that can be requested for the Request class, in number 2781 of 2 Kb/s" 2783 ::={requestClassEntry 9} 2785 requestClassRbdcTimeout OBJECT-TYPE 2787 SYNTAX INTEGER 2789 MAX-ACCESS read-write 2791 STATUS current 2793 DESCRIPTION 2795 "Persistence of the RBDC request, expressed in superframes" 2797 ::={requestClassEntry 10} 2799 requestClassVbdcMax OBJECT-TYPE 2801 SYNTAX INTEGER 2803 MAX-ACCESS read-write 2805 STATUS current 2806 DESCRIPTION 2808 "Max VBDC that can be requested for the Request class, 2810 in payload units (one ATM cell or one MPEG packet) per 2811 superframe" 2813 ::={requestClassEntry 11} 2815 requestClassVbdcTimeout OBJECT-TYPE 2817 SYNTAX INTEGER 2819 MAX-ACCESS read-write 2821 STATUS current 2823 DESCRIPTION 2825 "Time after which the RCST considers that the pending requests 2826 are lost. 2828 The RCST may issue new request for that traffic. VBDC Timeout is 2830 expressed in superframes." 2832 ::={requestClassEntry 12} 2834 requestClassVbdcMaxBackLog OBJECT-TYPE 2836 SYNTAX INTEGER 2838 MAX-ACCESS read-write 2840 STATUS current 2842 DESCRIPTION 2844 "VBDC back Log per Request class. (expressed in bytes)" 2846 ::={requestClassEntry 13} 2848 requestClassAvbdcRepTime OBJECT-TYPE 2850 SYNTAX INTEGER 2852 MAX-ACCESS read-write 2854 STATUS current 2856 DESCRIPTION 2858 "Optional parameter. AVBDC requests can be sent periodically, 2860 according to the value of that parameter. 2862 AVBDCRepTime is expressed in superframes." 2864 ::={requestClassEntry 14} 2866 requestClassRowStatus OBJECT-TYPE 2868 SYNTAX RowStatus 2870 MAX-ACCESS read-only 2872 STATUS current 2874 DESCRIPTION 2876 "Standard SNMP row status" 2878 DEFVAL { active } 2880 ::={requestClassEntry 15} 2882 globalRbdcMax OBJECT-TYPE 2884 SYNTAX INTEGER 2886 MAX-ACCESS read-write 2888 STATUS current 2890 DESCRIPTION 2891 "The global RBDC max is for information only and it is 2892 optional. 2894 (expressed in number of 2 kb/s)" 2896 ::={qos 4} 2898 globalVbdcMax OBJECT-TYPE 2900 SYNTAX INTEGER 2902 MAX-ACCESS read-write 2904 STATUS current 2906 DESCRIPTION 2908 "The global VBDC max is for information only and it is 2909 optional. 2911 (expressed in payload units/superframe)" 2913 ::={qos 5} 2915 globalVbdcMaxBackLog OBJECT-TYPE 2917 SYNTAX INTEGER 2919 MAX-ACCESS read-write 2921 STATUS current 2923 DESCRIPTION 2925 "The global VBDC back log is used only if the VBDC back log is 2926 not 2928 configured in the Request class.(expressed in bytes)" 2930 ::={qos 6} 2932 globalAvbdcRepTime OBJECT-TYPE 2934 SYNTAX INTEGER 2936 MAX-ACCESS read-write 2938 STATUS current 2940 DESCRIPTION 2942 "The global AVBDC rep time is optional (expressed in 2943 superframes)." 2945 ::={qos 7} 2947 channelIdStrictDispatching OBJECT-TYPE 2949 SYNTAX INTEGER { 2951 not_strict (0), 2953 strict (1) 2955 } 2957 MAX-ACCESS read-write 2959 STATUS current 2961 DESCRIPTION 2963 "Indicates whether the RCST will strictly follow RC 2964 association when 2966 signaled through Channel_ID in the TBTP: 2968 No strict association (0) 2970 Strict association (1)" 2972 ::={qos 8} 2974 ---- rcstStatus group 2976 rcstMode OBJECT-TYPE 2978 SYNTAX INTEGER { 2980 installation (0), 2982 operational (1) 2984 } 2986 MAX-ACCESS read-write 2988 STATUS current 2990 DESCRIPTION 2992 "Allows to identify in which mode the RCST is and to return it 2993 to 2995 the installation mode when needed. Values for the RCST mode 2996 are: 2998 Installation (0) 3000 Operational (1)" 3002 ::={rcstStatus 1} 3004 faultStatus OBJECT-TYPE 3006 SYNTAX INTEGER { 3008 nofault (0), 3010 fault (1) 3012 } 3014 MAX-ACCESS read-only 3016 STATUS current 3017 DESCRIPTION 3019 "Provide the fault status of the terminal. The fault status 3020 management 3022 is vendor specific. Values for the Fault Status are: 3024 no fault (0) 3026 fault (1)" 3028 ::={rcstStatus 2} 3030 fwdLinkStatus OBJECT-TYPE 3032 SYNTAX INTEGER { 3034 notAcquired (0), 3036 acquired (1) 3038 } 3040 MAX-ACCESS read-only 3042 STATUS current 3044 DESCRIPTION 3046 "Provides the status of the RCST Forward Link. Values for the 3048 Forward Link Status are: 3050 Not acquired (0) 3052 Acquired (1)" 3054 ::={rcstStatus 3} 3056 rtnLinkStatus OBJECT-TYPE 3058 SYNTAX INTEGER { 3059 loggedOff (0), 3061 loggedOn (1) 3063 } 3065 MAX-ACCESS read-only 3067 STATUS current 3069 DESCRIPTION 3071 "Provides the status of the RCST Return Link. Values for the 3073 Return Link Status are: 3075 Logged-off (0) 3077 Logged-on (1)" 3079 ::={rcstStatus 4} 3081 logUpdated OBJECT-TYPE 3083 SYNTAX INTEGER { 3085 noUpdate (0), 3087 logfileUpdated (1) 3089 } 3091 MAX-ACCESS read-only 3093 STATUS current 3095 DESCRIPTION 3097 "Indicates the existence of an updated log file: 3099 No update (0) 3101 Log file updated (1) 3103 The RCST should remove the Log file updated indication 3104 as the log file is fetched by the NCC." 3106 ::={rcstStatus 5} 3108 downloadStatus OBJECT-TYPE 3110 SYNTAX INTEGER { 3112 success (1), 3114 failure (2) 3116 } 3118 MAX-ACCESS read-only 3120 STATUS current 3122 DESCRIPTION 3124 "Provide some information about the result of the software 3126 download process. The following values shall be supported: 3128 success (1) 3130 failure (2)" 3132 ::={rcstStatus 6} 3134 currentSoftwareVersion OBJECT-TYPE 3136 SYNTAX DisplayString 3138 MAX-ACCESS read-only 3140 STATUS current 3142 DESCRIPTION 3144 "Current software version of the Software Download material." 3145 ::={rcstStatus 7} 3147 alternateSoftwareVersion OBJECT-TYPE 3149 SYNTAX DisplayString 3151 MAX-ACCESS read-only 3153 STATUS current 3155 DESCRIPTION 3157 "Alternate software version of the Software Download material. " 3159 ::={rcstStatus 8} 3161 currentConfigFileVersion OBJECT-TYPE 3163 SYNTAX DisplayString 3165 MAX-ACCESS read-only 3167 STATUS current 3169 DESCRIPTION 3171 "Version of the activated configuration file. Version is vendor 3172 specific" 3174 ::={rcstStatus 9} 3176 pendingConfigFileVersion 3178 OBJECT-TYPE 3180 SYNTAX DisplayString 3182 MAX-ACCESS read-only 3184 STATUS current 3185 DESCRIPTION 3187 "Version of the last downloaded configuration file. 3189 Version is vendor specific" 3191 ::={rcstStatus 10} 3193 --- rcstAction group 3195 rebootCommand OBJECT-TYPE 3197 SYNTAX INTEGER { 3199 idle (1), 3201 normal (2), 3203 alternate (3) 3205 } 3207 MAX-ACCESS read-write 3209 STATUS current 3211 DESCRIPTION 3213 "This variable shall force the RCST to reboot 3215 (1)- idle 3217 (2)- normal reboot (from current software load) 3219 (3)- reboot from alternate load (swap to alternate load before 3220 reboot)" 3222 DEFVAL {1} 3224 ::={rcstAction 1} 3226 rcstTxDisable OBJECT-TYPE 3228 SYNTAX INTEGER { 3230 idle (1), 3232 disable (2), 3234 } 3236 MAX-ACCESS read-write 3238 STATUS current 3240 DESCRIPTION 3242 "This variable shall force the RCST to stop transmission 3243 (transmit disabled as defined in [1]): 3245 (1)- idle 3247 (2)- initiate Tx Disabled" 3249 DEFVAL {1} 3251 ::={rcstAction 2} 3253 userTrafficDisableOBJECT-TYPE 3255 SYNTAX INTEGER { 3257 idle (1), 3259 disable (2), 3261 } 3263 MAX-ACCESS read-write 3265 STATUS current 3267 DESCRIPTION 3268 "This variable shall disable user traffic (only RCST management 3269 traffic can be transmitted) 3271 (1)- idle 3273 (2)- disable user traffic" 3275 DEFVAL {1} 3277 ::={rcstAction 3} 3279 cwEnable OBJECT-TYPE 3281 SYNTAX INTEGER { 3283 off (1), 3285 on (2), 3287 } 3289 MAX-ACCESS read-write 3291 STATUS current 3293 DESCRIPTION 3295 "This variable shall force the RCST to start transmission of CW 3296 : 3298 (1)- off 3300 (2)- on" 3302 DEFVAL {1} 3304 ::={rcstAction 4} 3306 oduTxReferenceEnable OBJECT-TYPE 3308 SYNTAX INTEGER { 3309 off (1), 3311 on (2), 3313 } 3315 MAX-ACCESS read-write 3317 STATUS current 3319 DESCRIPTION 3321 "Enables activation and deactivation of 10 MHz reference 3323 clock in the Tx IFL cable: 3325 (1) off 3327 (2) on" 3329 DEFVAL {2} 3331 ::={rcstAction 5} 3333 oduTxDCEnable OBJECT-TYPE 3335 SYNTAX INTEGER { 3337 off (1), 3339 on (2), 3341 } 3343 MAX-ACCESS read-write 3345 STATUS current 3347 DESCRIPTION 3349 "Enables activation and deactivation of DC in the Tx IFL cable: 3351 (1) off 3353 (2) on" 3355 DEFVAL {2} 3357 ::={rcstAction 6} 3359 oduRxDCEnable OBJECT-TYPE 3361 SYNTAX INTEGER { 3363 off (1), 3365 on (2), 3367 } 3369 MAX-ACCESS read-write 3371 STATUS current 3373 DESCRIPTION 3375 "Enables activation and deactivation of DC in the Rx IFL cable: 3377 (1) off 3379 (2) on" 3381 DEFVAL {2} 3383 ::={rcstAction 7} 3385 downloadFileCommand OBJECT-TYPE 3387 SYNTAX INTEGER { 3389 idle (1), 3391 config (2), 3393 installationLog(3) 3395 } 3397 MAX-ACCESS read-write 3398 STATUS current 3400 DESCRIPTION 3402 "This variable shall initiate a RCST configuration file download 3403 process 3405 (1) idle 3407 (2) download RCST configuration file from TFTP/FTP server 3409 (3) download RCST installation log file from TFTP/FTP server 3411 (INSTALL_LOG OPTION)" 3413 DEFVAL {1} 3415 ::={rcstAction 8} 3417 uploadFileCommand OBJECT-TYPE 3419 SYNTAX INTEGER { 3421 idle (1), 3423 config (2), 3425 eventAlarm (3), 3427 installationLog (4) 3429 } 3431 MAX-ACCESS read-write 3433 STATUS current 3435 DESCRIPTION 3437 "This variable shall initiate a RCST upload process 3439 (1) idle 3441 (2) upload RCST configuration file to TFTP/FTP server 3442 (3) upload RCST event/alarm log file to TFTP/FTP server 3444 (4) upload RCST installation log file to TFTP/FTP server 3446 (INSTALL_LOG OPTION)" 3448 DEFVAL {1} 3450 ::={rcstAction 9} 3452 activateConfigFileCommand OBJECT-TYPE 3454 SYNTAX INTEGER { 3456 idle (1), 3458 activate (2) 3460 } 3462 MAX-ACCESS read-write 3464 STATUS current 3466 DESCRIPTION 3468 "Triggers the RCST to use the configuration file and update 3470 its parameters accordingly. Some RCST implementation may require 3472 a reboot for the parameters to take effect (vendor specific). 3474 (1) Idle 3476 (2) activate" 3478 DEFVAL {1} 3480 ::={rcstAction 10} 3482 rcstLogonCommand OBJECT-TYPE 3484 SYNTAX INTEGER { 3485 idle (1), 3487 logon (2) 3489 } 3491 MAX-ACCESS read-write 3493 STATUS current 3495 DESCRIPTION 3497 "This variable shall initiate a RCST logon 3499 (1) idle 3501 (2) initiate RCST logon" 3503 DEFVAL {1} 3505 ::={rcstAction 11} 3507 rcstLogoffCommand OBJECT-TYPE 3509 SYNTAX INTEGER { 3511 idle (1), 3513 logoff (2) 3515 } 3517 MAX-ACCESS read-write 3519 STATUS current 3521 DESCRIPTION 3523 "This variable shall initiate a RCST logoff 3525 (1) idle 3527 (2) initiate RCST logoff" 3529 DEFVAL {1} 3530 ::={rcstAction 12} 3532 END= 3534 4. Security Considerations 3536 Some of the readable objects in this MIB module (i.e., objects with a 3537 MAX-ACCESS other than not-accessible) may be considered sensitive or 3538 vulnerable in some network environments. 3540 SNMP versions prior to SNMPv3 did not include adequate security. Even 3541 if the network itself is secure (for example by using IPsec), even 3542 then, there is no control as to who on the secure network is allowed 3543 to access and GET/SET (read/change/create/delete) the objects in this 3544 MIB module. 3546 It is RECOMMENDED that implementers consider the security features as 3547 provided by the SNMPv3 framework (see [RFC3410], section 8), 3548 including full support for the SNMPv3 cryptographic mechanisms (for 3549 authentication and privacy). 3551 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3552 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3553 enable cryptographic security. It is then a customer/operator 3554 responsibility to ensure that the SNMP entity giving access to an 3555 instance of this MIB module, is properly configured to give access to 3556 the objects only to those principals (users) that have legitimate 3557 rights to indeed GET or SET (change/create/delete) them. 3559 5. IANA Considerations 3561 No action from IANA is needed. 3563 6. Acknowledgments 3565 The authors thank Gorry Fairhurst for advice in the preparation of 3566 this document. 3568 The authors recognize this document is a collective effort of the 3569 SatLabs Group (www.satlabs.org). 3571 7. References 3573 7.1. Normative References 3575 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3576 Requirement Levels", BCP 14, RFC 2119, March 1997 (BEST 3577 CURRENT PRACTICE). 3579 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3580 Schoenwaelder, Ed., "Structure of Management Information, 3581 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3583 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3584 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3585 STD 58, RFC 2579, April 1999. 3587 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3588 "Conformance Statements for SMIv2", STD 58, RFC 2580, April 3589 1999. 3591 7.2. Informative References 3593 [ISO-MPEG] ISO/IEC DIS 13818-1:2000, "Information Technology; 3594 Generic Coding of Moving Pictures and Associated Audio 3595 Information Systems", International Standardisation 3596 Organisation (ISO). 3598 [ETSI-DAT] EN 301 192, "Digital Video Broadcasting (DVB); DVB 3599 Specifications for Data Broadcasting", European 3600 Telecommunications Standards Institute (ETSI). 3602 [ETSI-DVBS] EN 301 421 "Digital Video Broadcasting (DVB); Modulation 3603 and Coding for DBS satellite systems at 11/12 GHz", 3604 European Telecommunications Standards Institute (ETSI). 3606 [ETSI-RCS] ETSI 301 791 "Digital Video Broadcasting (DVB); 3607 Interaction Channel for Satellite Distribution Systems", 3608 European Telecommunications Standards Institute (ETSI). 3610 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3611 "Introduction and Applicability Statements for Internet- 3612 Standard Management Framework", RFC 3410, December 2002. 3613 [RFC4259] Montpetit, M.-J., Fairhurst, G., Clausen, H., 3614 Collini-Nocker, B., and H. Linder, "A Framework for 3615 Transmission of IP Datagrams over MPEG-2 Networks", RFC 3616 4259, November 2005. 3618 [SATLABS] SatLabs System Recommendations, version 2, December 2006. 3619 Available at www.satlabs.org. 3621 8. Authors' Addresses 3623 Stephane Combes 3624 ESTEC 3625 European Space Agency 3626 Keplerlaan 1 - 3627 - P.O. Box 299 3628 2200 AG Noordwijk ZH 3629 The Netherlands 3631 Email: stephane.combes@esa.int 3632 URL: telecom.esa.int 3634 Petter Chr. Amundsen 3635 VeriSat AS 3636 P.O Box 1 3637 1330 Fornebu 3638 Norway 3640 Email: pca@verisat.no 3641 URL: www.verisat.no 3643 Micheline Lambert 3644 Advantech Satellite Networks 3645 2341 boul. Alfred-Nobel 3646 Saint-Laurent (Montreal,)H4S 2A9 3647 Quebec, Canada 3649 Email: micheline.lambert@advantechamt.com 3650 URL: www.advantechsatnet.com 3651 Hans-Peter Lexow 3652 STM Norway 3653 Vollsveien 21 3654 1366 Lysaker 3655 Norway 3657 Email: hlexow@stmi.com 3658 URL: www.stmi.com 3660 9. Intellectual Property Statement 3662 The IETF takes no position regarding the validity or scope of any 3663 Intellectual Property Rights or other rights that might be claimed to 3664 pertain to the implementation or use of the technology described in 3665 this document or the extent to which any license under such rights 3666 might or might not be available; nor does it represent that it has 3667 made any independent effort to identify any such rights. Information 3668 on the procedures with respect to rights in RFC documents can be 3669 found in BCP 78 and BCP 79. 3671 Copies of IPR disclosures made to the IETF Secretariat and any 3672 assurances of licenses to be made available, or the result of an 3673 attempt made to obtain a general license or permission for the use of 3674 such proprietary rights by implementers or users of this 3675 specification can be obtained from the IETF on-line IPR repository at 3676 http://www.ietf.org/ipr. 3678 The IETF invites any interested party to bring to its attention any 3679 copyrights, patents or patent applications, or other proprietary 3680 rights that may cover technology that may be required to implement 3681 this standard. Please address the information to the IETF at 3682 ietf-ipr@ietf.org. 3684 10. Disclaimer of Validity 3686 This document and the information contained herein are provided on an 3687 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3688 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 3689 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 3690 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 3691 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3692 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3694 11. Copyright Statement 3696 Copyright (C) The IETF Trust (2007). 3698 This document is subject to the rights, licenses and restrictions 3699 contained in BCP 78, and except as set forth therein, the authors 3700 retain all their rights. 3702 <<< RFC Ed Note: please remove the text below, prior to publications 3703 >>> 3705 Change Log. 3707 Rev -00 3709 - First draft, for comment by the community. 3711 <<>