< draft-yegani-gre-key-extension-02.txt		draft-yegani-gre-key-extension-03.txt >
	Network Working Group P. Yegani		Network Working Group P. Yegani
	Internet-Draft G. Dommety		Internet-Draft G. Dommety
	Intended status: Standards Track Cisco Systems		Intended status: Standards Track Cisco Systems
	Expires: September 3, 2007 A. Lior		Expires: December 3, 2007 A. Lior
	Bridgewater Systems		Bridgewater Systems
	K. Chowdhury		K. Chowdhury
	J. Navali		J. Navali
	Starent Networks		Starent Networks
	March 2, 2007		June 2007
	GRE Key Extension for Mobile IPv4		GRE Key Extension for Mobile IPv4
	draft-yegani-gre-key-extension-02		draft-yegani-gre-key-extension-03
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	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
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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."
	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 September 3, 2007.		This Internet-Draft will expire on December 3, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	The GRE specification contains a Key field, which MAY contain a value		The GRE specification contains a Key field, which MAY contain a value
	that is used to identify a particular GRE data stream. This		that is used to identify a particular GRE data stream. This
	specification defines a new Mobile IP extension that is used to		specification defines a new Mobile IP extension that is used to
	skipping to change at page 4, line 22 ¶		skipping to change at page 4, line 22 ¶
	session.		session.
	If the FA does not support GRE encapsulation, the FA MUST reset the		If the FA does not support GRE encapsulation, the FA MUST reset the
	'G' bit in the Agent Advertisement message. In this case, if the MN		'G' bit in the Agent Advertisement message. In this case, if the MN
	sets the 'G' bit in the Registration Request message, the FA returns		sets the 'G' bit in the Registration Request message, the FA returns
	a Registration Reply message to the MN with code 'Requested		a Registration Reply message to the MN with code 'Requested
	Encapsulation Unavailable' (0x48) per [RFC3344].		Encapsulation Unavailable' (0x48) per [RFC3344].
	If the FA allows GRE encapsulation, and either the MN requested GRE		If the FA allows GRE encapsulation, and either the MN requested GRE
	encapsulation or local policy dictates using GRE encapsulation for		encapsulation or local policy dictates using GRE encapsulation for
	the session, the FA MUST include the GRE Key in the GRE-KEY Extension		the session, the FA MUST include the GRE Key in the GRE Key Extension
	in all Mobile IP Registration Requests (including initial, renewal		in all Mobile IP Registration Requests (including initial, renewal
	and de-registration requests) before forwarding the request to the		and de-registration requests) before forwarding the request to the
	HA. The GRE key assignment in the FA and the HA is outside the scope		HA. The FA may include a GRE key of value zero in the GRE Key
	of this memo.		Extension to signal that the HA assign GRE keys in both directions.
			The GRE key assignment in the FA and the HA is outside the scope of
			this memo.
	The GRE Key Extension SHALL follow the format defined in [RFC3344].		The GRE Key Extension SHALL follow the format defined in [RFC3344].
	This extension SHALL be added after the MN-HA and MN-FA Challenge and		This extension SHALL be added after the MN-HA and MN-FA Challenge and
	MN-AAA extensions (if any) and before the FA-HA Auth extension (if		MN-AAA extensions (if any) and before the FA-HA Auth extension (if
	any).		any).
	4.2. Home Agent Requirements for GRE Tunneling Support		4.2. Home Agent Requirements for GRE Tunneling Support
	The HA MUST follow the procedures specified in RFC 3344 in processing		The HA MUST follow the procedures specified in RFC 3344 in processing
	this extension in Registration Request messages. If the HA receives		this extension in Registration Request messages. If the HA receives
	skipping to change at page 5, line 8 ¶		skipping to change at page 5, line 10 ¶
	without the GRE Key Extension, it SHALL send an RRP with code 'Poorly		without the GRE Key Extension, it SHALL send an RRP with code 'Poorly
	Formed Request (0xY2)'.		Formed Request (0xY2)'.
	If the HA receives a Registration Request with a GRE Key Extension		If the HA receives a Registration Request with a GRE Key Extension
	but without the 'G' bit set, the HA SHOULD treat this as if 'G' bit		but without the 'G' bit set, the HA SHOULD treat this as if 'G' bit
	is set in the Registration Request i.e., the presence of GRE Key		is set in the Registration Request i.e., the presence of GRE Key
	Extension indicates a request for GRE encapsulation.		Extension indicates a request for GRE encapsulation.
	If the HA receives the GRE Key Extension in a Registration Request		If the HA receives the GRE Key Extension in a Registration Request
	and recognizes the GRE Key Extension as well as supports GRE		and recognizes the GRE Key Extension as well as supports GRE
	encapsulation, it SHOULD accept the RRQ and send a RRP with code		encapsulation, the following procedures should apply:
	'Accepted (0)'. The HA MUST assign a GRE key and include the GRE Key
	Extension in the RRP before sending it to the FA. The HA MUST		The HA SHOULD accept the RRQ and send a RRP with code 'Accepted (0)'.
	include the GRE Key Extension in all RRPs in response to any RRQ that		The HA MUST assign a GRE key and include the GRE Key Extension in the
	included GRE Key Extension, when a GRE key is available for the		RRP before sending it to the FA. The HA MUST include the GRE Key
	registration.		Extension in all RRPs in response to any RRQ that included GRE Key
			Extension, when a GRE key is available for the registration.
			If the HA receives the GRE Key Extension in the initial Registration
			Request and recognizes the GRE Key Extension carrying a GRE key value
			of zero, it SHOULD accept the RRQ and send a RRP with code 'Accepted
			(0)'. The HA MUST assign GRE keys for both directions and include
			these keys in the GRE Key Extension in the RRP before sending it to
			the FA. The HA MUST include the GRE Key Extension in the RRP in
			response to the initial RRQ that included GRE Key Extension, when a
			GRE key is available for the registration.
	4.3. Mobile Node Requirements for GRE Tunneling Support		4.3. Mobile Node Requirements for GRE Tunneling Support
	If the MN is capable of supporting GRE encapsulation, it SHOULD set		If the MN is capable of supporting GRE encapsulation, it SHOULD set
	the 'G' bit in the Flags field in the Registration Request per		the 'G' bit in the Flags field in the Registration Request per
	[RFC3344].		[RFC3344].
	5. GRE Key Extension and Tunneling Procedures		5. GRE Key Extension and Tunneling Procedures
	GRE tunneling support for Mobile IP will permit asymmetric GRE keying		GRE tunneling support for Mobile IP will permit asymmetric GRE keying
End of changes. 7 change blocks.
	13 lines changed or deleted		25 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/