< draft-ietf-sming-inet-modules-01.txt		draft-ietf-sming-inet-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 Internet Protocol Core Modules		SMIng Internet Protocol Core Modules
	draft-ietf-sming-inet-modules-01		draft-ietf-sming-inet-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 SMIng modules that introduce commonly used		This memo presents SMIng modules that introduce commonly used
	Internet Protocol specific data definitions. They are provided so		Internet Protocol specific data definitions. They are provided so
	that other SMIng modules that would otherwise define their own		that other SMIng modules that would otherwise define their own
	representations can import them from a common place.		representations can import them from a common place.
	The IETF-INET module defines types and classes for representing		The IETF-INET module defines types and classes for representing
	Internet Protocol specific information. It builds on RFC 2851 and		Internet Protocol specific information. It builds on RFC 2851 and
	extends it in several ways.		extends it in several ways.
	The IETF-INET-FILTER module extends the IETF-INET module by		The IETF-INET-FILTER module extends the IETF-INET module by providing
	providing generic definitions for typical IP packet filters.		generic definitions for typical IP packet filters.
	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-INET . . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. IETF-INET . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. IETF-INET-FILTER . . . . . . . . . . . . . . . . . . . . . . . 9		3. IETF-INET-FILTER . . . . . . . . . . . . . . . . . . . . . . . 9
	4. Usage Examples . . . . . . . . . . . . . . . . . . . . . . . . 11		4. Usage Examples . . . . . . . . . . . . . . . . . . . . . . . . 11
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 12		5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
	References . . . . . . . . . . . . . . . . . . . . . . . . . . 13		References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13
	A. OPEN ISSUES . . . . . . . . . . . . . . . . . . . . . . . . . 14		A. OPEN ISSUES . . . . . . . . . . . . . . . . . . . . . . . . . 14
			Full Copyright Statement . . . . . . . . . . . . . . . . . . . 15
	1. Introduction		1. Introduction
	SMIng [1] modules frequently need to represent Internet Protocol		SMIng [1] modules frequently need to represent Internet Protocol
	specific information such as IP addresses. This memo contains SMIng		specific information such as IP addresses. This memo contains SMIng
	modules which define a core set of SMIng types and classes to be		modules which define a core set of SMIng types and classes to be
	imported by other SMIng modules.		imported by other SMIng modules.
	The IETF-INET module provides core SMIng data definitions for the		The IETF-INET module provides core SMIng data definitions for the
	Internet Protocol suite. This module is derived from [3].		Internet Protocol suite. This module is derived from [3].
	The IETF-INET-FILTER module provides SMIng data definitions that		The IETF-INET-FILTER module provides SMIng data definitions that
	model Internet Protocol filters and components thereof.		model Internet Protocol filters and components thereof.
	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-INET		2. IETF-INET
	skipping to change at page 4, line 8 ¶		skipping to change at page 4, line 9 ¶
	//		//
	// Core type definitions for the Internet Protocol suite.		// Core type definitions for the Internet Protocol suite.
	//		//
	typedef InetPortNumber {		typedef InetPortNumber {
	type Unsigned32 (0..65535);		type Unsigned32 (0..65535);
	description		description
	"Represents a 16 bit port number of an Internet		"Represents a 16 bit port number of an Internet
	transport layer protocol. Port numbers are assigned by		transport layer protocol. Port numbers are assigned by
	IANA. A list of all assignments is available from		IANA. A list of all assignments is available from
	<http://www.iana.org/>.		<http://www.iana.org/>.
	The value zero is object-specific and must be defined as		The value zero is object-specific and must be defined as
	part of the description of any object which uses this		part of the description of any object which uses this
	syntax. Examples of the usage of zero might include		syntax. Examples of the usage of zero might include
	situations where a port number is unknown, or when the		situations where a port number is unknown, or when the
	value zero is used as a wildcard in a filter.";		value zero is used as a wildcard in a filter.";
	reference		reference
	"STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960";		"STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960";
	};		};
	typedef InetProtocolNumber {		typedef InetProtocolNumber {
	type Unsigned32 (0..255);		type Unsigned32 (0..255);
	skipping to change at page 5, line 6 ¶		skipping to change at page 5, line 8 ¶
	};		};
	typedef InetAddressPrefixLength {		typedef InetAddressPrefixLength {
	type Unsigned32;		type Unsigned32;
	description		description
	"Denotes the length of a generic Internet network address		"Denotes the length of a generic Internet network address
	prefix. A value of n corresponds to an IP address mask		prefix. A value of n corresponds to an IP address mask
	which has n contiguous 1-bits from the most significant		which has n contiguous 1-bits from the most significant
	bit (MSB) and all other bits set to 0.		bit (MSB) and all other bits set to 0.
	InetAddressPrefixLength values that are larger than		InetAddressPrefixLength values that are larger than
	the maximum length of an IP address for a specific		the maximum length of an IP address for a specific
	InetAddressType are treated as the maximum significant		InetAddressType are treated as the maximum significant
	value applicable for the InetAddressType. The maximum		value applicable for the InetAddressType. The maximum
	significant value is 32 for the InetAddressType		significant value is 32 for the InetAddressType
	'ipv4(1)' and 128 for the InetAddressType 'ipv6(2)'.		'ipv4(1)' and 128 for the InetAddressType 'ipv6(2)'.
	The maximum significant value for the InetAddressType		The maximum significant value for the InetAddressType
	'dns(16)' is 0.		'dns(16)' is 0.
	The value zero is object-specific and must be defined as		The value zero is object-specific and must be defined as
	part of the description of any object which uses this		part of the description of any object which uses this
	syntax. Examples of the usage of zero might include		syntax. Examples of the usage of zero might include
	situations where the Internet network address prefix		situations where the Internet network address prefix
	is unknown or does not apply.";		is unknown or does not apply.";
	};		};
	typedef InetAutonomousSystemNumber {		typedef InetAutonomousSystemNumber {
	type Unsigned32;		type Unsigned32;
	description		description
	"Represents an autonomous system number which identifies an		"Represents an autonomous system number which identifies an
	Autonomous System (AS). An AS is a set of routers under a		Autonomous System (AS). An AS is a set of routers under a
	single technical administration, using an interior gateway		single technical administration, using an interior gateway
	protocol and common metrics to route packets within the AS,		protocol and common metrics to route packets within the AS,
	and using an exterior gateway protocol to route packets to		and using an exterior gateway protocol to route packets to
	other ASs'. IANA maintains the AS number space and has		other ASs'. IANA maintains the AS number space and has
	delegated large parts to the regional registries.		delegated large parts to the regional registries.
	Autonomous system numbers are currently limited to 16 bits		Autonomous system numbers are currently limited to 16 bits
	(0..65535). There is however work in progress to enlarge the		(0..65535). There is however work in progress to enlarge the
	autonomous system number space to 32 bits. This textual		autonomous system number space to 32 bits. This textual
	convention therefore uses an Unsigned32 value without a		convention therefore uses an Unsigned32 value without a
	range restriction in order to support a larger autonomous		range restriction in order to support a larger autonomous
	system number space.";		system number space.";
	reference		reference
	"RFC 1771, RFC 1930";		"RFC 1771, RFC 1930";
	};		};
	//		//
	// Internet Protocol address types for specific IP versions.		// Internet Protocol address types for specific IP versions.
	//		//
	typedef InetAddressType {		typedef InetAddressType {
	type Enumeration (unknown(0), ipv4(1), ipv6(2),		type Enumeration (unknown(0), ipv4(1), ipv6(2),
	dns(16));		dns(16));
	description		description
	"A value that represents a type of Internet address.		"A value that represents a type of Internet address.
	unknown(0) An unknown address type. This value MUST		unknown(0) An unknown address type. This value MUST
	be used if the value of the corresponding		be used if the value of the corresponding
	address attribute is a zero-length string.		address attribute is a zero-length string.
	It may also be used to indicate an IP address		It may also be used to indicate an IP address
	which is not in one of the formats defined		which is not in one of the formats defined
	below.		below.
	skipping to change at page 12, line 41 ¶		skipping to change at page 13, line 4 ¶
	attribute TcpConnectionState state {		attribute TcpConnectionState state {
	access readonly;		access readonly;
	description		description
	"The current state of the TCP connection.";		"The current state of the TCP connection.";
	};		};
	attribute TcpConnectionCtrl ctrl {		attribute TcpConnectionCtrl ctrl {
	access readwrite;		access readwrite;
	description		description
	"A control which allows to change the state of the		"A control which allows to change the state of the
	TCP connection.";		TCP connection.";
	};		};
	description		description
	"This class contains information about a particular current		"This class contains information about a particular current
	TCP connection.";		TCP connection.";
	};		};
	};		};
	5. Security Considerations		5. 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.
	6. Acknowledgments		6. Acknowledgments
	Some definitions in this document are derived from RFC 2851 [3],		Some definitions in this document are derived from RFC 2851 [3],
	which was written by M. Daniele, B. Haberman, S. Routhier and J.		which was written by M. Daniele, B. Haberman, S. Routhier and J.
	Schoenwaelder.		Schoenwaelder.
	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] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder, J.,		[3] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder,
	"Textual Conventions for Internet Network Addresses", RFC 2851,		"Textual Conventions for Internet Network Addresses", RFC 2851,
	June 2000.		June 2000.
	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 13, line 36 ¶		skipping to change at page 14, line 4 ¶
	Frank Strauss		Frank Strauss
	TU Braunschweig		TU Braunschweig
	Bueltenweg 74/75		Bueltenweg 74/75
	38106 Braunschweig		38106 Braunschweig
	Germany		Germany
	Phone: +49 531 391-3266		Phone: +49 531 391-3266
	EMail: strauss@ibr.cs.tu-bs.de		EMail: strauss@ibr.cs.tu-bs.de
	URI: http://www.ibr.cs.tu-bs.de/		URI: http://www.ibr.cs.tu-bs.de/
	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-INET module.		definitions that should go into the IETF-SMING-INET module.
	Are the filters sufficiently flexible? - The filters probably need		Are the filters sufficiently flexible? - The filters probably need
	more work to cover more cases. Should the IETF-INET-FILTER module		more work to cover more cases. Should the IETF-INET-FILTER module
	become a separate document?		become a separate document?
	More examples needed? - Is it useful to include more examples, e.g.		More examples needed? - Is it useful to include more examples, e.g.
	on the usage of filters or subnets?		on the usage of filters or subnets?
	Dscp Definition - Does the InetDiffServCodePoint type definition		Dscp Definition - Does the InetDiffServCodePoint type definition
	really belong into this module?		really belong into this module?
	InetAddressDNS Format - 255a or 255t? Length restriction?		InetAddressDNS Format - 255a or 255t? Length restriction?
	Usage of the terms Endpoint and Address - Check the attribute		Usage of the terms Endpoint and Address - Check the attribute
	identifiers and descriptions of InetTransportEndpoint and		identifiers and descriptions of InetTransportEndpoint and
	InetSubnet: when should the term endpoint be used, and when		InetSubnet: when should the term endpoint be used, and when
	address?		address?
	InetProtocolNumber and InetTransportEndpoint - Should an		InetProtocolNumber and InetTransportEndpoint - Should an
	InetProtocolNumber attribute be added to the		InetProtocolNumber attribute be added to the
	InetTransportEndpoint?		InetTransportEndpoint?
	Undocumented typemap keyword - This feature needs more work. We
			Undocumented typemap keyword - This feature needs more work. We
	either define such a type casting mechanism or we add a real		either define such a type casting mechanism or we add a real
	discriminated union to the SMIng type system.		discriminated union to the SMIng type system.
	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. 38 change blocks.
	53 lines changed or deleted		52 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/