< draft-song-pppext-mipv6-ppp-support-00.txt		draft-song-pppext-mipv6-ppp-support-01.txt >
	JunHyuk Song		JUNHYUK SONG
	INTERNET DRAFT ChaeYong Chong		INTERNET DRAFT CHAEYOUNG CHONG
	September 2001 SAMSUNG Elec.		October 2001 SAMSUNG ELECTRONICS
			DONGKIE LEIGH
			SK TELECOM
	MIPv6 IPCP configuration option for PPP IPv6CP		MIPv6 IPCP configuration option for PPP IPv6CP
	draft-song-pppext-mipv6-ppp-support-00.txt		draft-song-pppext-mipv6-ppp-support-01.txt
	Status of This Memo		Status of This Memo
	Distribution of this memo is unlimited.		Distribution of this memo is unlimited.
	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. Internet-Drafts are working		all provisions of Section 10 of RFC2026. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 43 ¶
	The Point-to-Point Protocol (PPP) [1] provides a standard method for		The Point-to-Point Protocol (PPP) [1] provides a standard method for
	transporting multi-protocol datagrams over point-to-point links. PPP		transporting multi-protocol datagrams over point-to-point links. PPP
	defines an extensible Link Control Protocol (LCP) for establishing,		defines an extensible Link Control Protocol (LCP) for establishing,
	configuring, and testing the data-link connection; and a family of		configuring, and testing the data-link connection; and a family of
	Network Control Protocols (NCPs) for establishing and configuring		Network Control Protocols (NCPs) for establishing and configuring
	different network-layer protocols.		different network-layer protocols.
	The MIPv6 link local router that support Mobile Node connection via		The MIPv6 link local router that support Mobile Node connection via
	PPP, need to know whether the PPP client is MIPv6 node or not.		PPP, need to know whether the PPP client is MIPv6 node or not.
	Because the link operator may have different local policy for MIPv6		Because the local operator may have different local access policy
	node (ex. support of user mobility). Currently, the IPv6CP option [2]		such as user authentication for the user mobility support [5] over
	supports establishment and configuration of the IPv6 over PPP.		MIPv6 [6]. Currently, the IPv6CP option [2] supports establishment
	However, MIPv6 link local router cannot differentiate IPv6 node and		and configuration of the IPv6 over PPP. However, MIPv6 link local
	MIPv6 node which is connected over PPP. This document defines the		router cannot differentiate between IPv6 node and MIPv6 mobile node
	new IPCP opton for the MIPv6 support.		which is connected over PPP. This document defines the new IPCP
			option for the MIPv6 support.
	1. Problem Statement		1. Introduction
	The MIPv6 Link local router which may be providing PPP connetion,		The MIPv6 link local router that support Mobile Node connection via
	currently cannot identify whether the connection is requested by		PPP, need to know whether the PPP client is MIPv6 node or not.
	Mobile IPv6 Node or IPv6 node. The MIPv6 service is value added		Because the local operator may have different local access policy
	service for the operator, and the operator may want to support user		such as user authentication for the user mobility support [5] over
	mobility service over Mobile IPv6. Therefore it is important to let		MIPv6 [6]. Currently, the IPv6CP option [2] supports establishment
	local router which is a PPP termination point to be able to identify		and configuration of the IPv6 over PPP. However, MIPv6 link local
	MIPv6 service.		router cannot differentiate between IPv6 node and MIPv6 mobile node
			which is connected over PPP. This document defines the new IPCP
			option for the MIPv6 support.
	2. Configuration Options		2. Configuration Options
	The Configuration Option format and basic options are already defined		The Configuration Option format and basic options are already defined
	for IPCP [3].		for IPCP [3].
	The most updated value of the IPCP Option Type field are specified in		The most updated value of the IPCP Option Type field are specified in
	the IANA website [4]. This document concerns the following values:		the IANA web site [4]. This document concerns the following values:
	[?] Mobile IPv6 (Pending for the IANA number assignment)		[?] Mobile IPv6 (Pending for the IANA number assignment)
	2.1. Mobile IPv6 Option		2.1. Mobile IPv6 Option
	Description		Description
	Some operator may want to differentiate IPv6 node and MIPv6 node.		Some operator may want to differentiate IPv6 node and MIPv6 node.
	This mechanism let Mobile Node to specify MIPv6 service.		This mechanism will let Mobile Node to specify MIPv6 service.
	A summary of the Configuration Option format is shown		A summary of the Configuration Option format is shown
	below. The fields are transmitted from left to right.		below. The fields are transmitted from left to right.
	The Mobile-IPv6 Configuration Option for IPCP is defined as follows:		The Mobile-IPv6 Configuration Option for IPCP is defined as follows:
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length | Interface-Identifier (MS Bytes)		| Type | Length | Interface-Identifier (MS Bytes)
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 3, line 39 ¶		skipping to change at page 3, line 27 ¶
	Default		Default
	If no valid interface identifier can be successfully negotiated,		If no valid interface identifier can be successfully negotiated,
	no default Interface-Identifier value should be assumed. The		no default Interface-Identifier value should be assumed. The
	procedures for recovering from such a case are unspecified.		procedures for recovering from such a case are unspecified.
	One approach is to manually configure the interface identifier of		One approach is to manually configure the interface identifier of
	the interface. [2]		the interface. [2]
	3. IANA Considerations		3. IANA Considerations
	Requires IPCP option number assignemnt		Requires IPCP option number assignment
			4. Acknowledgements
			Special thanks to Prof. Murali Venkatesh of Syracuse University.
	References		References
	[1] Simpson, W., "The Point-to-Point Protocol", STD 51, RFC		[1] Simpson, W., "The Point-to-Point Protocol", STD 51, RFC
	1661, July 1994.		1661, July 1994.
	[2] Dimitry Haskin and Ed Allen, "IP version 6 over PPP", RFC 2472		[2] Dimitry Haskin and Ed Allen, "IP version 6 over PPP", RFC 2472
	December 1998		December 1998
	[3] G. McGregor, "The PPP Internet Protocol Control Protocol (IPCP)		[3] G. McGregor, "The PPP Internet Protocol Control Protocol (IPCP)
	May 1992		May 1992
	[4] www.iana.org		[4] www.iana.org
			[5] JH SONG, CY CHONG, DK LEE, "IP user Mobility Support model"
			October 2002, draft-song-network-user-mobility-00.txt
			[6] David B. Johnson and C. Perkins. "Mobility Support in IPv6"
			draft-ietf-mobileip-ipv6-14.txt
	Addresses		Addresses
	Questions about this memo can be directed to the authors:		Questions about this memo can be directed to the authors:
	JUNHYUK SONG		JUNHYUK SONG
	SAMSUNG ELECTRONICS.		SAMSUNG ELECTRONICS.
	Mobile Development Team		Mobile Development Team
	Network Systems Division		Network Systems Division
	Phone: +82-31-779-6822		Phone: +82-31-779-6822
	Email: santajun@lycos.co.kr		Email: santajun@lycos.co.kr
	FAX: +82-31-7798769		FAX: +82-31-7798769
	CHAE YONG CHONG		CHAE YONG CHONG
	SAMSUNG ELECTRONICS.		SAMSUNG ELECTRONICS.
	Mobile Development Team		Mobile Development Team
	Network Systems Division		Network Systems Division
	Phone: +82-31-779-6822		Phone: +82-31-779-6822
	Email:cychong@samsung.com		Email:cychong@samsung.com
			DONGKIE LEIGH
			SK TELECOM
			Core Network Development Team
			Network R&D Center
			Phone +82-2-829-4640
			Email: galahad@netsgo.com
			FAX:+82-2-829-4612
End of changes. 12 change blocks.
	22 lines changed or deleted		38 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/