Updated sming charter

["Durham, David" <david.durham@intel.com>]

As previously noted, some have asked that the sming wg charter be updated to
reflect current realities. Please see the below updated charter and, if you
have comments, please post them by 10/7/2002.

Cheers,
-Dave

Description of Working Group:
   This working group shall develop a standards-track specification
   for the next generation data definition language for specifying
   network management data. As a starting point, the WG has used 
   the SMIng language developed in the IRTF Network Management
   Research Group. The new SMIv3 will represent a superset of 
   the best features of SMIv2 (Structure of Management Information
   version 2) and the SPPI (Structure of Policy Provisioning
   Information).
 
   The objective is to replace both the SMIv2 and the SPPI with a
   single language as the data definition language for the 
   monitoring, configuration, and provisioning of network devices. 
   The SMIv3 is to be mapped onto the underlying management 
   protocol(s).
    
   The language developed will enable the modeling of network
   management information in a manner that provides the benefits of
   object-oriented design. To achieve this, the language must allow
   the design of highly reusable syntactic/semantic components
   (templates) that can be reused by multiple IETF working groups
   for convenience, consistency, and to maximize interoperability
   in device management. A registration mechanism will also be
   described for reusable components defined using the language
   so that their existence and purpose may be archived. 
 
   The language will provide for the definition of a data model
   that allows a variety of implementation-specific technologies 
   to be derived from a single definition. To demonstrate this, 
   the working group will define one or two technology specific
   transport mappings: one for SNMP (potentially embedded in the
   language), and possibly one for COPS (as an independent
   mapping document).
 
   The language will also provide: 
 
   - syntax optimized for parseability, human readability,
     and non-redundancy 
 
   - conventions for representing inheritance and containment
     of defined data 
 
   - enhanced attribute-level and association-level constraints 
 
   - a maximal amount of machine-parseable syntax so that
     programmatic tools can aid in modeling and implementation 
 
   This working group will also define typical usage scenarios for
   the language and highlight its features. Finally, it will
   develop a framework by which reusable components specified
   using this language can be registered and made readily available
   for continued reuse and improvement. 
 
   The working group will not define models for specific technologies,
   except as required for illustrative examples. Specific models are
   to be developed by the subject matter experts using the SMIng in
   the appropriate technology specific WGs. 

New realistic milestones.

Done    IRTF documents complete & submitted to IETF  
Done    Submit Revised I-Ds including requirements I-D  
Done    Meet at 50th IETF  
Done    Submit revised I-D for requirements document  
Done    WG Last Call on requirements document as Informational RFC  
Done    Submit revised I-D for Data Definition Language and Usage document  
Done    Meet at 51st IETF
Done    1st Interim 
Done    Proposal submission process
Done    Proposal selection process
Done    Capabilities MIB
Done    2nd Interim
OCT 02  Submit Initial SMIv3 Language Definition 
OCT 02  Updated SMIv3 Capabilities MIB 
NOV 02  55th IETF meeting  
DEC 02  Finalized SMIv3 Language Definition
JAN 02  Submit SMIv3 MIB Modules(core types)
JAN 03  Submit SMIv3 Guidelines 
FEB 03  Last call SMIv3 language for PS
FEB 03  INET Modules (textual conventions)
MAR 03  Submit Transition from SMIv2
MAR 03  Submit COPS mapping

APR 03    Registrar framework defined for reusable components as an I-D 
MAY 03    Last call Guidelines, Modules and Transitions 
JUN 03    Last call on Registrar Framework document as Informational RFC  
AUG 03    Working Group closes