rfc3584

NetworkWorkingGroupR.FryeRequestforComments:3584VibrantSolutionsBCP:74D.LeviObsoletes:2576NortelNetworksCategory:BestCurrentPracticeS.RouthierWindRiverSystems,Inc.B.WijnenLucentTechnologiesAugust2003CoexistencebetweenVersion1,Version2,andVersion3oftheInternet-standardNetworkManagementFrameworkStatusofthisMemoThisdocumentspecifiesanInternetBestCurrentPracticesfortheInternetCommunity,andrequestsdiscussionandsuggestionsforimprovements.Distributionofthismemoisunlimited.CopyrightNoticeCopyright(C)TheInternetSociety(2003).AllRightsReserved.AbstractThepurposeofthisdocumentistodescribecoexistencebetweenversion3oftheInternet-standardNetworkManagementFramework,(SNMPv3),version2oftheInternet-standardNetworkManagementFramework(SNMPv2),andtheoriginalInternet-standardNetworkManagementFramework(SNMPv1).ThisdocumentalsodescribeshowtoconvertMIBmodulesfromSMIv1formattoSMIv2format.ThisdocumentobsoletesRFC2576.Frye,etal.BestCurrentPractice[Page1]RFC3584CoexistencebetweenSNMPversionsAugust2003TableOfContents1.Overview..........................31.1.SNMPv1........................41.2.SNMPv2........................41.3.SNMPv3........................52.SMIandManagementInformationMappings...........52.1.MIBModules......................62.1.1.ObjectDefinitions..............62.1.2.TrapandNotificationDefinitions......82.2.ComplianceStatements.................92.3.CapabilitiesStatements................93.TranslatingNotificationParameters.............103.1.TranslatingSNMPv1NotificationParameterstoSNMPv2NotificationParameters............113.2.TranslatingSNMPv2NotificationParameterstoSNMPv1NotificationParameters............124.ApproachestoCoexistenceinaMulti-lingualNetwork....144.1.SNMPv1andSNMPv2AccesstoMIBData.........144.2.Multi-lingualimplementations.............154.2.1.CommandGenerator...............154.2.2.CommandResponder...............164.2.2.1.HandlingCounter64.........164.2.2.2.MappingSNMPv2Exceptions......174.2.2.2.1.MappingnoSuchObjectandnoSuchInstance....184.2.2.2.2.MappingendOfMibView...184.2.2.3.ProcessingAnSNMPv1GetReques...184.2.2.4.ProcessingAnSNMPv1GetNextRequest.194.2.2.5.ProcessingAnSNMPv1SetRequest...204.2.3.NotificationOriginator............214.2.4.NotificationReceiver.............214.3.ProxyImplementations.................224.3.1.UpstreamVersionGreaterThanDownstreamVersion....................224.3.2.UpstreamVersionLessThanDownstreamVersion.234.4.ErrorStatusMappings.................255.MessageProcessingModelsandSecurityModels........265.1.Mappings.......................265.2.TheSNMPv1MPModelandSNMPv1Community-basedSecurityModel....................265.2.1.ProcessingAnIncomingRequest........275.2.2.GeneratingAnOutgoingResponse........295.2.3.GeneratingAnOutgoingNotification......295.2.4.ProxyForwardingOfRequests.........305.3.TheSNMPCommunityMIBModule.............306.IntellectualPropertyStatement...............427.Acknowledgments.......................43Frye,etal.BestCurrentPractice[Page2]RFC3584CoexistencebetweenSNMPversionsAugust20038.SecurityConsiderations...................439.References.........................449.1.NormativeReferences.................449.2.InformativeReferences................46AppendixA.ChangeLog.....................47A.1.ChangesFromRFC2576.................47A.2.ChangesBetweenRFC1908andRFC2576.........49Editors’Addresses.......................50FullCopyrightStatement....................511.OverviewThepurposeofthisdocumentistodescribecoexistencebetweenversion3oftheInternet-standardNetworkManagementFramework,termedtheSNMPversion3framework(SNMPv3),version2oftheInternet-standardNetworkManagementFramework,termedtheSNMPversion2framework(SNMPv2),andtheoriginalInternet-standardNetworkManagementFramework(SNMPv1).ThekeywordsMUST,MUSTNOT,REQUIRED,SHALL,SHALLNOT,SHOULD,SHOULDNOT,RECOMMENDED,MAY,andOPTIONALinthisdocumentaretobeinterpretedasdescribedinRFC2119[RFC2119].Therearefourgeneralaspectsofcoexistencedescribedinthisdocument.Eachoftheseisdescribedinaseparatesection:-ConversionofMIBdocumentsbetweenSMIv1andSMIv2formatsisdocumentedinsection2.-Mappingofnotificationparametersisdocumentedinsection3.-ApproachestocoexistencebetweenentitieswhichsupportthevariousversionsofSNMPinamulti-lingualnetworkisdocumentedinsection4.Thissectionaddressestheprocessingofprotocoloperationsinmulti-lingualimplementations,aswellasbehaviourofproxyimplementations.-TheSNMPv1MessageProcessingModelandCommunity-BasedSecurityModel,whichprovidesmechanismsforadaptingSNMPv1intotheView-BasedAccessControlModel(VACM)[20],isdocumentedinsection5(thissectionalsoaddressestheSNMPv2cMessageProcessingModelandCommunity-BasedSecurityModel).Frye,etal.BestCurrentPractice[Page3]RFC3584CoexistencebetweenSNMPversionsAugust20031.1.SNMPv1SNMPv1isdefinedbythesedocuments:-STD15,RFC1157[RFC1157]whichdefinestheSimpleNetworkManagementProtocol(SNMPv1),theprotocolusedfornetworkaccesstomanagedobjects.-STD16,RFC1155[RFC1155]whichdefinestheStructureofManagementInformation(SMIv1),themechanismsusedfordescribingandnamingobjectsforthepurposeofmanagement.-STD16,RFC1212[RFC121