draft-krishnan-mip6-firewall-vendor-02.txt		draft-krishnan-mip6-firewall-vendor-03.txt
	Network Working Group S. Krishnan		Network Working Group S. Krishnan
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Informational Y. Sheffer		Intended status: Standards Track Y. Sheffer
	Expires: May 21, 2008 Check Point		Expires: August 25, 2008 Check Point
	N. Steinleitner		N. Steinleitner
	University of Goettingen		University of Goettingen
	November 18, 2007		G. Bajko
			Nokia
			February 22, 2008
	Guidelines for firewall vendors regarding MIPv6 traffic		Guidelines for firewall vendors regarding MIPv6 traffic
	draft-krishnan-mip6-firewall-vendor-02		draft-krishnan-mip6-firewall-vendor-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 37		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 May 21, 2008.		This Internet-Draft will expire on August 25, 2008.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	This document presents some recommendations for firewall vendors to		This document presents some recommendations for firewall vendors to
	help them implement their firewalls in a way that allows Mobile IPv6		help them implement their firewalls in a way that allows Mobile IPv6
	signaling and data messages to pass through. This document describes		signaling and data messages to pass through. This document describes
	how to implement stateful packet filtering capability for MIPv6.		how to implement stateful packet filtering capability for MIPv6.
	Table of Contents		Table of Contents
	skipping to change at page 2, line 20		skipping to change at page 2, line 21
	3.1. Requirements . . . . . . . . . . . . . . . . . . . . . . . 3		3.1. Requirements . . . . . . . . . . . . . . . . . . . . . . . 3
	3.2. Detecting and parsing the Mobility Header . . . . . . . . . 3		3.2. Detecting and parsing the Mobility Header . . . . . . . . . 3
	3.3. Parsing Mobility Options . . . . . . . . . . . . . . . . . 3		3.3. Parsing Mobility Options . . . . . . . . . . . . . . . . . 3
	4. Allowing signaling response packets . . . . . . . . . . . . . . 4		4. Allowing signaling response packets . . . . . . . . . . . . . . 4
	5. Allowing data packets based on signaling . . . . . . . . . . . 5		5. Allowing data packets based on signaling . . . . . . . . . . . 5
	6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 6		6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 6
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
	8. Security Considerations . . . . . . . . . . . . . . . . . . . . 6		8. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
	9. Normative References . . . . . . . . . . . . . . . . . . . . . 7		9. Normative References . . . . . . . . . . . . . . . . . . . . . 7
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
	Intellectual Property and Copyright Statements . . . . . . . . . . 8		Intellectual Property and Copyright Statements . . . . . . . . . . 9
	1. Requirements notation		1. Requirements notation
	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 [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. Introduction		2. Introduction
	Network elements such as firewalls are an integral aspect of a		Network elements such as firewalls are an integral aspect of a
	skipping to change at page 8, line 4		skipping to change at page 8, line 4
	Email: yaronf@checkpoint.com		Email: yaronf@checkpoint.com
	Niklas Steinleitner		Niklas Steinleitner
	University of Goettingen		University of Goettingen
	Lotzestr. 16-18		Lotzestr. 16-18
	Goettingen		Goettingen
	Germany		Germany
	Email: steinleitner@cs.uni-goettingen.de		Email: steinleitner@cs.uni-goettingen.de
			Gabor Bajko
			Nokia
			Email: gabor.bajko@nokia.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
End of changes. 8 change blocks.
	8 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/