Simple Network Management Protocol
                                 Version 2 with
                           Transitional Authentication
                                        
                                        
                         a Proposal to the SNMPv2 WG by
                                        
               Bert Wijnen, Uri Blumenthal, N. C. Hien (IBM Corp)
                                        
                              Bob Natale (ACE*COMM)
                                        
                                    July 1995

========
                                What is SNMPv2t?

               SNMPv2t is the convergence of:
               
                    - SNMPv1 Message Wrapper
               
                    - SNMPv1 Community-based Authentication
               
                    - SNMPv2 "Payloads":
                         - SNMPv2 SMI, TC, MIBv2
                         - SNMPv2 PDUs, Protocol Operations
                         - SNMPv2 Conformance Statements
               - - - - - - - - - - - - - - - - - - - - - - -
                    - SNMPv2 "Texture"
                         - SNMPv2 Introduction Document
                         - SNMPv2 Transport Mappings
                         - SNMPv2 <-> SNMPv1 Coexistence
               ---------------------------------------------
                    - SNMPv1 "Extensions"
                         - Standardized Remote Configuration
                         - Enhanced Authentication Schemes and Services
========

                           What is an SNMPv2t Message?

          The syntax of an SNMPv2t message differs from that of an SNMPv1
          message as follows:
          
               - The version component is changed to 1.
          
               - The data component contains an SNMPv2 PDU
          
          An SNMPv2t message is an ASN.1 value with the following syntax:
          
               Message ::=
                   SEQUENCE {
                      version
                         INTEGER {v2t (1)},
                      community                 -- as per RFC1157
                         OCTET STRING,          -- SNMPv1 communityName
                      data                      -- as SNMPv2 Drafts
                         PDUs                   -- SNMPv2 PDUs
                   }
========

                        What Problems does SNMPv2t Solve?

       1.  Lack of Consensus within WG wrt "Security Architecture" and
           Remote Configuration Issues
          
       2.  Sense of Instability Resulting from Recent "Revolutionary" Changes
          
       3.  Long Delay in Marketplace Deployment of Solid SNMPv2 Features
           which have Established Consensus
          
       4.  Need/Desire to Advance Stable Documents to Draft Standard Status
          
       5.  Need to Recapture Marketplace Confidence and Momentum
          
       6.  Need to Regain Working Group Harmony and Process Efficiency
          
       7.  Need to Allow More (Ample) Time to Resolve Problem #1

========

                        What are the Benefits of SNMPv2t?

     The following are among the major expected benefits of the SNMPv2t
     implementation and deployment alternative:
     
     1.  Widely understood and accepted parts of SNMPv2 will be put to work
          with minimal additional delay
     
     2.  Easy and quick implementation and deployment by vendors
     
     3.  Slip-streamable introduction of SNMPv2t products into the field
          (no "all at once" or "all or nothing" approach required)
     
     4.  No administrative reconfiguration required by users to achieve
          "better SNMP" with same level of security currently used today
     
     5.  Smoother transition to future more secure SNMP products
          (certainly for the users; and possibly for most vendors too)