< draft-ietf-sming-modules-01.txt		draft-ietf-sming-modules-02.txt >
	Network Working Group F. Strauss		Network Working Group F. Strauss
	Internet-Draft J. Schoenwaelder		Internet-Draft J. Schoenwaelder
	Expires: August 31, 2001 TU Braunschweig		Expires: January 18, 2002 TU Braunschweig
	K. McCloghrie		July 20, 2001
	Cisco Systems
	March 02, 2001
	SMIng Core Modules		SMIng Core Modules
	draft-ietf-sming-modules-01		draft-ietf-sming-modules-02
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as		other groups may also distribute working documents as Internet-
	Internet-Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum of six		Internet-Drafts are draft documents valid for a maximum of six months
	months and may be updated, replaced, or obsoleted by other documents		and may be updated, replaced, or obsoleted by other documents at any
	at any time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on August 31, 2001.		This Internet-Draft will expire on January 18, 2002.
			Copyright Notice
			Copyright (C) The Internet Society (2001). All Rights Reserved.
	Abstract		Abstract
	This memo presents an SMIng module that introduces core data types		This memo presents an SMIng module that introduces core data types
	such as counters, date and time related types, and various string		such as counters, date and time related types, and various string
	types. These definitions build on RFC 2578 and RFC 2579.		types. These definitions build on RFC 2578 and RFC 2579.
	Copyright Notice
	Copyright (C) The Internet Society (2001). All Rights Reserved.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. IETF-SMING . . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. IETF-SMING . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 11		3. Security Considerations . . . . . . . . . . . . . . . . . . . 11
	4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11		4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
	References . . . . . . . . . . . . . . . . . . . . . . . . . . 11		References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12
	A. OPEN ISSUES . . . . . . . . . . . . . . . . . . . . . . . . . 13		A. OPEN ISSUES . . . . . . . . . . . . . . . . . . . . . . . . . 13
			Full Copyright Statement . . . . . . . . . . . . . . . . . . . 14
	1. Introduction		1. Introduction
	SMIng [1] modules are built on top of some core definitions. These		SMIng [1] modules are built on top of some core definitions. These
	core definitions are imported from some "well-defined" core modules		core definitions are imported from some "well-defined" core modules
	described in this memo.		described in this memo.
	The IETF-SMING module defines a set of common SMIng data types.		The IETF-SMING module defines a set of common SMIng data types.
	These data types are generally applicable for modelling all areas of		These data types are generally applicable for modelling all areas of
	management information. Among these types are counter types, string		management information. Among these types are counter types, string
	types and date and time related types. This module is derived from		types and date and time related types. This module is derived from
	RFC 2578 [3] and [4].		RFC 2578 [3] and [4].
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [2].		document are to be interpreted as described in [2].
	2. IETF-SMING		2. IETF-SMING
	module IETF-SMING {		module IETF-SMING {
	skipping to change at page 11, line 38 ¶		skipping to change at page 11, line 46 ¶
	identity null {		identity null {
	description		description
	"An identity used to represent null pointer values.";		"An identity used to represent null pointer values.";
	};		};
	};		};
	3. Security Considerations		3. Security Considerations
	This module does not define any management objects. Instead, it		This module does not define any management objects. Instead, it
	defines a set of SMIng types and classes which may be used by other		defines a set of SMIng types and classes which may be used by other
	SMIng modules to define management objects. These data definitions		SMIng modules to define management objects. These data definitions
	have no security impact on the Internet.		have no security impact on the Internet.
	4. Acknowledgments		4. Acknowledgments
	Some definitions in this document are derived from RFC 2578 [3] and		Some definitions in this document are derived from RFC 2578 [3] and
	RFC 2579 [4], which were written by K. McCloghrie, D. Perkins, J.		RFC 2579 [4], which were written by K. McCloghrie, D. Perkins, J.
	Schoenwaelder, J. Case, M. Rose, and S. Waldbusser.		Schoenwaelder, J. Case, M. Rose, and S. Waldbusser.
	References		References
	[1] Strauss, F., Schoenwaelder, J., McCloghrie, K., "SMIng - Next		[1] Strauss, F. and J. Schoenwaelder, "SMIng - Next Generation
	Generation Structure of Management Information",		Structure of Management Information", draft-ietf-sming-02.txt,
	draft-ietf-sming-01.txt, March 2001.		July 2001.
	[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", RFC 2119, BCP 14, March 1997.		Levels", RFC 2119, BCP 14, March 1997.
	[3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,		[3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
	M., Waldbusser, S., "Structure of Management Information		M. and S. Waldbusser, "Structure of Management Information
	Version 2 (SMIv2)", RFC 2578, STD 59, April 1999.		Version 2 (SMIv2)", RFC 2578, STD 59, April 1999.
	[4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,		[4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
	M., Waldbusser, S., "Textual Conventions for SMIv2", RFC 2579,		M. and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579,
	STD 59, April 1999.		STD 59, April 1999.
	Authors' Addresses		Authors' Addresses
	Frank Strauss		Frank Strauss
	TU Braunschweig		TU Braunschweig
	Bueltenweg 74/75		Bueltenweg 74/75
	38106 Braunschweig		38106 Braunschweig
	Germany		Germany
	skipping to change at page 12, line 42 ¶		skipping to change at page 13, line 5 ¶
	Juergen Schoenwaelder		Juergen Schoenwaelder
	TU Braunschweig		TU Braunschweig
	Bueltenweg 74/75		Bueltenweg 74/75
	38106 Braunschweig		38106 Braunschweig
	Germany		Germany
	Phone: +49 531 391-3289		Phone: +49 531 391-3289
	EMail: schoenw@ibr.cs.tu-bs.de		EMail: schoenw@ibr.cs.tu-bs.de
	URI: http://www.ibr.cs.tu-bs.de/		URI: http://www.ibr.cs.tu-bs.de/
	Keith McCloghrie
	Cisco Systems
	170 West Tasman Drive
	San Jose, CA 95134-1706
	USA
	Phone: +1 408 526 5260
	EMail: kzm@cisco.com
	URI: http://www.cisco.com/
	Appendix A. OPEN ISSUES		Appendix A. OPEN ISSUES
	What else is missing? - There might be more core type or class		What else is missing? - There might be more core type or class
	definitions that should go into the IETF-SMING module. Things		definitions that should go into the IETF-SMING module. Things
	that come to mind are types for Roles and RoleCombinations or		that come to mind are types for Roles and RoleCombinations or
	types for Tags and TagLists.		types for Tags and TagLists.
	Split Core Module? - Should the SMIng core module be split into		Split Core Module? - Should the SMIng core module be split into
	several smaller modules each focussing on a specific aspect (e.g.		several smaller modules each focussing on a specific aspect (e.g.
	strings, date and time, ...)?		strings, date and time, ...)?
	TimeStamp - The description of the TimeStamp type builds on		TimeStamp - The description of the TimeStamp type builds on
	sysUpTime.		sysUpTime.
	TimeInterval - Define TimeInterval based on Unsigned32 and remove		TimeInterval - Define TimeInterval based on Unsigned32 and remove
	the last sentence from the description?		the last sentence from the description?
	Ugly Formats like `255t' - A better solution for e.g. the `255t'
			Ugly Formats like `255t' - A better solution for e.g. the `255t'
	length restriction of Utf8String255?		length restriction of Utf8String255?
	Class Definitions - Maybe, we should define useful classes, like
	one which combines RowStatus and StorageType (and perhaps even an		Class Definitions - Maybe, we should define useful classes, like one
			which combines RowStatus and StorageType (and perhaps even an
	OwnerString)?		OwnerString)?
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (2001). All Rights Reserved.		Copyright (C) The Internet Society (2001). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implmentation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph		kind, provided that the above copyright notice and this paragraph are
	are included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
	developing Internet standards in which case the procedures for		developing Internet standards in which case the procedures for
	copyrights defined in the Internet Standards process must be		copyrights defined in the Internet Standards process must be
	followed, or as required to translate it into languages other than		followed, or as required to translate it into languages other than
	English.		English.
	The limited permissions granted above are perpetual and will not be		The limited permissions granted above are perpetual and will not be
	revoked by the Internet Society or its successors or assigns.		revoked by the Internet Society or its successors or assigns.
	This document and the information contained herein is provided on an		This document and the information contained herein is provided on an
	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING		"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING		TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION		BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
	HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF		HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
			Acknowledgement
			Funding for the RFC Editor function is currently provided by the
			Internet Society.
End of changes. 26 change blocks.
	48 lines changed or deleted		42 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/