draft-ietf-mext-firewall-vendor-01.txt   draft-ietf-mext-firewall-vendor-02.txt 
Network Working Group S. Krishnan Network Working Group S. Krishnan
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track Y. Sheffer Intended status: Standards Track Y. Sheffer
Expires: November 19, 2009 Check Point Expires: April 30, 2010 Check Point
N. Steinleitner N. Steinleitner
University of Goettingen University of Goettingen
G. Bajko G. Bajko
Nokia Nokia
May 18, 2009 October 27, 2009
Guidelines for firewall vendors regarding MIPv6 traffic Guidelines for firewall vendors regarding MIPv6 traffic
draft-ietf-mext-firewall-vendor-01 draft-ietf-mext-firewall-vendor-02
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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.
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 Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
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 November 19, 2009. This Internet-Draft will expire on April 30, 2010.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
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 and DSMIPv6 signaling and data messages to pass through. This
how to implement stateful packet filtering capability for MIPv6. document describes how to implement stateful packet filtering
capability for MIPv6 and DSMIPv6.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. MIPv6 Firewall Primitives . . . . . . . . . . . . . . . . . . . 3 3. MIPv6 Firewall Primitives . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . 4 3.3. Parsing Mobility Options . . . . . . . . . . . . . . . . . 4
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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
9. Normative References . . . . . . . . . . . . . . . . . . . . . 7 9. Normative References . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
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 4, line 9 skipping to change at page 4, line 9
messages. Thus the firewalls need to be able to recognize the messages. Thus the firewalls need to be able to recognize the
presence of the mobility header and be able to parse the contents of presence of the mobility header and be able to parse the contents of
the Mobility Header. The MH is described in section 6.1 of [RFC3775] the Mobility Header. The MH is described in section 6.1 of [RFC3775]
and the format of the same is scribed in section 6.1.1 of [RFC3775]. and the format of the same is scribed in section 6.1.1 of [RFC3775].
Firewalls need to be able to at least understand the contents of the Firewalls need to be able to at least understand the contents of the
MH Type field that describes the type of signaling message carried. MH Type field that describes the type of signaling message carried.
3.3. Parsing Mobility Options 3.3. Parsing Mobility Options
The Mobility Header can carry additional information in the form of The Mobility Header can carry additional information in the form of
mobility options as described in section 6.2 of [RFC3775]. Some of mobility options as described in section 6.2 of [RFC3775] and section
these mobility options need to be understood for proper creation of 3 of [RFC5555]. Some of these mobility options need to be understood
state on the firewalls. Hence firewalls must be able to parse the for proper creation of state on the firewalls. Hence firewalls must
mobility options defined in [RFC3775]. be able to parse the mobility options defined in [RFC3775] and
[RFC5555].
4. Allowing signaling response packets 4. Allowing signaling response packets
The MIPv6 signalling messages are usually performed as a request- The MIPv6 signalling messages are usually performed as a request-
response pair. The request message is usually allowed by setting up response pair. The request message is usually allowed by setting up
a static firewall rule to allow the traffic to pass through. The a static firewall rule to allow the traffic to pass through. The
response message on the other hand can be dynamically allowed if the response message on the other hand can be dynamically allowed if the
firewall can automatically setup a filter for the response packets firewall can automatically setup a filter for the response packets
when the request packet passes through. This is not trivial, but when the request packet passes through. This is not trivial, but
fortunately is straightforward. There are 3 message pairs that are fortunately is straightforward. There are 3 message pairs that are
skipping to change at page 5, line 27 skipping to change at page 5, line 27
STATEFUL_PINHOLE_LIFETIME, unless renewed by new mobility messages. STATEFUL_PINHOLE_LIFETIME, unless renewed by new mobility messages.
This document recommends that the default value of This document recommends that the default value of
STATEFUL_PINHOLE_LIFETIME be set to 30 seconds. STATEFUL_PINHOLE_LIFETIME be set to 30 seconds.
These dynamic rules MUST be immediately deleted after the return These dynamic rules MUST be immediately deleted after the return
message passes through. e.g. Once a return HoT message for a HoTI message passes through. e.g. Once a return HoT message for a HoTI
passes through, the pinhole must be immediately removed. The loss of passes through, the pinhole must be immediately removed. The loss of
the HoT packet after passing the firewall needs to be handled by the the HoT packet after passing the firewall needs to be handled by the
original MN retransmitting the HoTI message. original MN retransmitting the HoTI message.
A DSMIPv6 client [RFC5555] having been configured with only a v4 CoA,
will tunnel the MIP6 signaling messages to the HA's IPv4 address
using its IPv4 CoA. These messages are either IP-in-IP encapsulated
(protocol number 4) or UDP&IP encapsulated and sent to the
destination UDP port number 4191.
The firewall SHOULD understand the Binding Update and Biding
Acknowledgement Message Extensions and check the status of the F
flag. If the F flag is set to zero in both the BU and the BA, the
firewall MUST set up a dynamic filter for the return packets:
Destination Address: IPv4 CoA of the MN
Protocol: 4 (IP-in-IP)
Source Address: IPv4 address of the HA
When the F flag is set to 1 in either the BU and BA, the firewall
does not need to take any special action, as the signaling packets
will be UDP encapsulated.
5. Allowing data packets based on signaling 5. Allowing data packets based on signaling
Once the MIPv6 signaling completes, the data traffic can begin to Once the MIPv6 signaling completes, the data traffic can begin to
flow. The traffic filters for the data traffic can be inferred from flow. The traffic filters for the data traffic can be inferred from
the contents of the signaling messages that setup the session. This the contents of the signaling messages that setup the session. This
section describes how firewalls can intelligently setup filters for section describes how firewalls can intelligently setup filters for
data traffic based on signaling traffic.The following example data traffic based on signaling traffic.The following example
describes how to setup a filter for allowing incoming route optimized describes how to setup a filter for allowing incoming route optimized
messages from a CN to an MN after the MN sent a BU message to a CN. messages from a CN to an MN after the MN sent a BU message to a CN.
skipping to change at page 7, line 27 skipping to change at page 7, line 45
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
[RFC4487] Le, F., Faccin, S., Patil, B., and H. Tschofenig, "Mobile [RFC4487] Le, F., Faccin, S., Patil, B., and H. Tschofenig, "Mobile
IPv6 and Firewalls: Problem Statement", RFC 4487, IPv6 and Firewalls: Problem Statement", RFC 4487,
May 2006. May 2006.
[RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers", RFC 5555, June 2009.
Authors' Addresses Authors' Addresses
Suresh Krishnan Suresh Krishnan
Ericsson Ericsson
8400 Decarie Blvd. 8400 Decarie Blvd.
Town of Mount Royal, QC Town of Mount Royal, QC
Canada Canada
Phone: +1 514 345 7900 x42871 Phone: +1 514 345 7900 x42871
Email: suresh.krishnan@ericsson.com Email: suresh.krishnan@ericsson.com
skipping to change at page 9, line 4 skipping to change at line 332
Lotzestr. 16-18 Lotzestr. 16-18
Goettingen Goettingen
Germany Germany
Email: steinleitner@cs.uni-goettingen.de Email: steinleitner@cs.uni-goettingen.de
Gabor Bajko Gabor Bajko
Nokia Nokia
Email: gabor.bajko@nokia.com Email: gabor.bajko@nokia.com
Full Copyright Statement
Copyright (C) The IETF Trust (2009).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 12 change blocks. 
17 lines changed or deleted 49 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/