< draft-ietf-softwire-map-mib-08.txt		draft-ietf-softwire-map-mib-09.txt >
	Internet Engineering Task Force Y. Fu		Internet Engineering Task Force Y. Fu
	Internet-Draft CNNIC		Internet-Draft CNNIC
	Intended status: Standards Track S. Jiang		Intended status: Standards Track S. Jiang
	Expires: November 25, 2017 B. Liu		Expires: November 28, 2017 B. Liu
	Huawei Technologies Co., Ltd		Huawei Technologies Co., Ltd
	J. Dong		J. Dong
	Y. Chen		Y. Chen
	Tsinghua University		Tsinghua University
	May 24, 2017		May 27, 2017
	Definitions of Managed Objects for MAP-E		Definitions of Managed Objects for MAP-E
	draft-ietf-softwire-map-mib-08		draft-ietf-softwire-map-mib-09
	Abstract		Abstract
	This memo defines a portion of the Management Information Base (MIB)		This memo defines a portion of the Management Information Base (MIB)
	for using with network management protocols in the Internet		for using with network management protocols in the Internet
	community. In particular, it defines managed objects for MAP		community. In particular, it defines managed objects for MAP
	encapsulation (MAP-E) mode.		encapsulation (MAP-E) mode.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents 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."
	This Internet-Draft will expire on November 25, 2017.		This Internet-Draft will expire on November 28, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 22 ¶		skipping to change at page 2, line 22 ¶
	2. The Internet-Standard Management Framework . . . . . . . . . 2		2. The Internet-Standard Management Framework . . . . . . . . . 2
	3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	4. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3		4. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3
	4.1. The mapMIBObjects . . . . . . . . . . . . . . . . . . . . 3		4.1. The mapMIBObjects . . . . . . . . . . . . . . . . . . . . 3
	4.1.1. The mapRule Subtree . . . . . . . . . . . . . . . . . 3		4.1.1. The mapRule Subtree . . . . . . . . . . . . . . . . . 3
	4.1.2. The mapSecurityCheck Subtree . . . . . . . . . . . . 3		4.1.2. The mapSecurityCheck Subtree . . . . . . . . . . . . 3
	4.2. The mapMIBConformance Subtree . . . . . . . . . . . . . . 4		4.2. The mapMIBConformance Subtree . . . . . . . . . . . . . . 4
	5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4		5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 11		7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
	9.1. Normative References . . . . . . . . . . . . . . . . . . 13		9.1. Normative References . . . . . . . . . . . . . . . . . . 13
	9.2. Informative References . . . . . . . . . . . . . . . . . 13		9.2. Informative References . . . . . . . . . . . . . . . . . 14
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
	1. Introduction		1. Introduction
	Mapping of Address and Port (MAP) [RFC7597] is a stateless mechanism		Mapping of Address and Port (MAP) [RFC7597] is a stateless mechanism
	for running IPv4 over IPv6-only infrastructure. In particular, it		for running IPv4 over IPv6-only infrastructure. In particular, it
	includes two mode, translation mode or encapsulation mode. For the		includes two mode, translation mode or encapsulation mode. For the
	encapsulation mode, it provides an automatic tunnelling mechanism for		encapsulation mode, it provides an automatic tunnelling mechanism for
	providing IPv4 connectivity service to end users over a service		providing IPv4 connectivity service to end users over a service
	provider's IPv6 network		provider's IPv6 network
	skipping to change at page 4, line 19 ¶		skipping to change at page 4, line 19 ¶
	5. Definitions		5. Definitions
	The following MIB module imports definitions from [RFC2578],		The following MIB module imports definitions from [RFC2578],
	[RFC2579],[RFC2580],[RFC2863], and [RFC4001].		[RFC2579],[RFC2580],[RFC2863], and [RFC4001].
	MAP-E-MIB DEFINITIONS ::= BEGIN		MAP-E-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, OBJECT-TYPE, mib-2,		MODULE-IDENTITY, OBJECT-TYPE, mib-2,
	Integer32, Unsigned32, Counter64		Unsigned32, Counter64
	FROM SNMPv2-SMI --RFC2578		FROM SNMPv2-SMI --RFC2578
	TEXTUAL-CONVENTION		TEXTUAL-CONVENTION
	FROM SNMPv2-TC --RFC2579		FROM SNMPv2-TC --RFC2579
	ifIndex		ifIndex
	FROM IF-MIB --RFC2863		FROM IF-MIB --RFC2863
	InetAddressIPv6, InetAddressIPv4,		InetAddressIPv6, InetAddressIPv4,
	InetAddressPrefixLength		InetAddressPrefixLength
	FROM INET-ADDRESS-MIB --RFC4001		FROM INET-ADDRESS-MIB --RFC4001
	OBJECT-GROUP, MODULE-COMPLIANCE		OBJECT-GROUP, MODULE-COMPLIANCE
	FROM SNMPv2-CONF; --RFC2580		FROM SNMPv2-CONF; --RFC2580
	mapMIB MODULE-IDENTITY		mapMIB MODULE-IDENTITY
	LAST-UPDATED "201705240000Z"		LAST-UPDATED "201705270000Z"
	ORGANIZATION		ORGANIZATION
	"IETF Softwire Working Group"		"IETF Softwire Working Group"
	CONTACT-INFO		CONTACT-INFO
	"Yu Fu		"Yu Fu
	CNNIC		CNNIC
	No.4 South 4th Street, Zhongguancun		No.4 South 4th Street, Zhongguancun
	Beijing, P.R. China 100190		Beijing, P.R. China 100190
	EMail: fuyu@cnnic.cn		EMail: fuyu@cnnic.cn
	Sheng Jiang		Sheng Jiang
	skipping to change at page 5, line 20 ¶		skipping to change at page 5, line 20 ¶
	Yuchi Chen		Yuchi Chen
	Tsinghua University		Tsinghua University
	Department of Computer Science, Tsinghua University		Department of Computer Science, Tsinghua University
	Beijing 100084		Beijing 100084
	P.R. China		P.R. China
	Email: chenycmx@gmail.com"		Email: chenycmx@gmail.com"
	DESCRIPTION		DESCRIPTION
	"The MIB module is defined for management of objects in the		"The MIB module is defined for management of objects in the
	MAP-E BRs or CEs."		MAP-E BRs or CEs."
	REVISION "201705240000Z"		REVISION "201705270000Z"
	DESCRIPTION		DESCRIPTION
	"Initial version. Published as RFC xxxx."		"Initial version. Published as RFC xxxx."
	--RFC Ed.: RFC-edtitor pls fill in xxxx		--RFC Ed.: RFC-edtitor pls fill in xxxx
	::= { mib-2 xxx }		::= { mib-2 xxx }
	--xxx to be replaced withIANA-assigned value		--xxx to be replaced withIANA-assigned value
	mapMIBObjects OBJECT IDENTIFIER ::= {mapMIB 1}		mapMIBObjects OBJECT IDENTIFIER ::= {mapMIB 1}
	mapRule OBJECT IDENTIFIER		mapRule OBJECT IDENTIFIER
	::= { mapMIBObjects 1 }		::= { mapMIBObjects 1 }
	skipping to change at page 6, line 43 ¶		skipping to change at page 6, line 43 ¶
	SEQUENCE {		SEQUENCE {
	mapRuleID Unsigned32,		mapRuleID Unsigned32,
	mapRuleIPv6Prefix InetAddressIPv6,		mapRuleIPv6Prefix InetAddressIPv6,
	mapRuleIPv6PrefixLen InetAddressPrefixLength,		mapRuleIPv6PrefixLen InetAddressPrefixLength,
	mapRuleIPv4Prefix InetAddressIPv4,		mapRuleIPv4Prefix InetAddressIPv4,
	mapRuleIPv4PrefixLen InetAddressPrefixLength,		mapRuleIPv4PrefixLen InetAddressPrefixLength,
	mapRuleBRIPv6Address InetAddressIPv6,		mapRuleBRIPv6Address InetAddressIPv6,
	mapRulePSID RulePSID,		mapRulePSID RulePSID,
	mapRulePSIDLen Unsigned32,		mapRulePSIDLen Unsigned32,
	mapRuleOffset Unsigned32,		mapRuleOffset Unsigned32,
	mapRuleEALen Integer32,		mapRuleEALen Unsigned32,
	mapRuleType Integer32		mapRuleType RuleType
	}		}
	mapRuleID OBJECT-TYPE		mapRuleID OBJECT-TYPE
	SYNTAX Unsigned32 (1..4294967295)		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An identifier used to distinguish the multiple mapping		"An identifier used to distinguish the multiple mapping
	rule which is unique with each CE in the same BR."		rule which is unique with each CE in the same BR."
	::= { mapRuleEntry 1 }		::= { mapRuleEntry 1 }
	mapRuleIPv6Prefix OBJECT-TYPE		-- The object mapRuleIPv6Prefix is IPv6 specific and hence it does
			-- not use the version agnostic InetAddress.
			mapRuleIPv6Prefix OBJECT-TYPE
	SYNTAX InetAddressIPv6		SYNTAX InetAddressIPv6
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The IPv6 prefix defined in mapping rule which will be		"The IPv6 prefix defined in mapping rule which will be
	assigned to CE. The address type is given by		assigned to CE. The address type is given by
	mapRuleIPv6PrefixType."		mapRuleIPv6PrefixType."
	::= { mapRuleEntry 2 }		::= { mapRuleEntry 2 }
	mapRuleIPv6PrefixLen OBJECT-TYPE		mapRuleIPv6PrefixLen OBJECT-TYPE
	SYNTAX InetAddressPrefixLength		SYNTAX InetAddressPrefixLength
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The length of the IPv6 prefix defined in the mapping rule.		"The length of the IPv6 prefix defined in the mapping rule.
	As a parameter for mapping rule, it will be also assigned		As a parameter for mapping rule, it will be also assigned
	to CE."		to CE."
	::= { mapRuleEntry 3 }		::= { mapRuleEntry 3 }
			-- The object mapRuleIPv4Prefix is IPv4 specific and hence it does
			-- not use the version agnostic InetAddress.
	mapRuleIPv4Prefix OBJECT-TYPE		mapRuleIPv4Prefix OBJECT-TYPE
	SYNTAX InetAddressIPv4		SYNTAX InetAddressIPv4
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	" The IPv4 prefix defined in mapping rule which will be		" The IPv4 prefix defined in mapping rule which will be
	assigned to CE. The address type is given by		assigned to CE. The address type is given by
	mapRuleIPv4PrefixType."		mapRuleIPv4PrefixType."
	::= { mapRuleEntry 4 }		::= { mapRuleEntry 4 }
	skipping to change at page 7, line 46 ¶		skipping to change at page 8, line 4 ¶
	::= { mapRuleEntry 4 }		::= { mapRuleEntry 4 }
	mapRuleIPv4PrefixLen OBJECT-TYPE		mapRuleIPv4PrefixLen OBJECT-TYPE
	SYNTAX InetAddressPrefixLength		SYNTAX InetAddressPrefixLength
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The length of the IPv4 prefix defined in the mapping		"The length of the IPv4 prefix defined in the mapping
	rule. As a parameter for mapping rule, it will be also		rule. As a parameter for mapping rule, it will be also
	assigned to CE."		assigned to CE."
	::= { mapRuleEntry 5 }		::= { mapRuleEntry 5 }
			-- The object mapRuleBRIPv6Address is IPv6 specific and hence it does
			-- not use the version agnostic InetAddress.
	mapRuleBRIPv6Address OBJECT-TYPE		mapRuleBRIPv6Address OBJECT-TYPE
	SYNTAX InetAddressIPv6		SYNTAX InetAddressIPv6
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The IPv6 address of the BR which will be		"The IPv6 address of the BR which will be
	conveyed to CE."		conveyed to CE."
	::= { mapRuleEntry 6 }		::= { mapRuleEntry 6 }
	mapRulePSID OBJECT-TYPE		mapRulePSID OBJECT-TYPE
	skipping to change at page 8, line 42 ¶		skipping to change at page 8, line 51 ¶
	SYNTAX Unsigned32(0..15)		SYNTAX Unsigned32(0..15)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Bit length value of the number of significant bits in		"Bit length value of the number of significant bits in
	the PSID field. When it is set to 0, the PSID		the PSID field. When it is set to 0, the PSID
	field is to be ignored."		field is to be ignored."
	::= { mapRuleEntry 9 }		::= { mapRuleEntry 9 }
	mapRuleEALen OBJECT-TYPE		mapRuleEALen OBJECT-TYPE
	SYNTAX Integer32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The length of the Embedded-Address (EA) defined in		"The length of the Embedded-Address (EA) defined in
	mapping rule which will be assigned to CE."		mapping rule which will be assigned to CE."
	REFERENCE		REFERENCE
	"EA: section 3 of RFC 7597."		"EA: section 3 of RFC 7597."
	::= { mapRuleEntry 10 }		::= { mapRuleEntry 10 }
	mapRuleType OBJECT-TYPE		mapRuleType OBJECT-TYPE
	SYNTAX RuleType		SYNTAX RuleType
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"It represents the type of the mapping rule. the value of		"It represents the type of the mapping rule. the value of
	1 means it is a BMR; the value 2 means it is a FMR."		1 means it is a bmr; the value 2 means it is a fmr."
	REFERENCE		REFERENCE
	"bmr, fmr: section 5 of RFC 7597"		"bmr, fmr: section 5 of RFC 7597"
	::= { mapRuleEntry 11 }		::= { mapRuleEntry 11 }
	mapSecurityCheckTable OBJECT-TYPE		mapSecurityCheckTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MapSecurityCheckEntry		SYNTAX SEQUENCE OF MapSecurityCheckEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The (conceptual) table containing information on		"The (conceptual) table containing information on
	skipping to change at page 12, line 46 ¶		skipping to change at page 13, line 8 ¶
	RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to		RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
	enable cryptographic security. It is then a customer/operator		enable cryptographic security. It is then a customer/operator
	responsibility to ensure that the SNMP entity giving access to an		responsibility to ensure that the SNMP entity giving access to an
	instance of this MIB module is properly configured to give access to		instance of this MIB module is properly configured to give access to
	the objects only to those principals (users) that have legitimate		the objects only to those principals (users) that have legitimate
	rights to indeed GET or SET (change/create/delete) them.		rights to indeed GET or SET (change/create/delete) them.
	8. Acknowledgements		8. Acknowledgements
	The authors would like to thank for valuable comments from David		The authors would like to thank for valuable comments from David
	Harrington, Mark Townsley, Shishio Tsuchiya, Yong Cui and Suresh		Harrington, Mark Townsley, Shishio Tsuchiya, Yong Cui, Suresh
	Krishnan.		Krishnan, Bert Wijnen and Juergen Schoenwaelder.
	This document was produced using the xml2rfc tool [RFC2629].		This document was produced using the xml2rfc tool [RFC2629].
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
End of changes. 17 change blocks.
	17 lines changed or deleted		27 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/