-------------------------------------------------------
NETEXT2 BOF
Meeting agenda

TUESDAY, July 28, 2009
1300-1500 Afternoon Session I
-------------------------------------------------------
1. Blue sheets, scribe, agenda bashing
Chairs - 5 min

2. Problem scope
Jonne & Marcelo - 20 min

3. Overview of types of solutions
Julien & Suresh - 30 min

4. Requirements
Raj & Rajeev - 50 min

5. Next steps
ADs - 15 min
-------------------------------------------------------

NETEXT2 BOF description
-----------------------

Proxy Mobile IPv6 (PMIP6) [RFC5213] is a network based mobility
protocol built on Mobile IPv6 [RFC3775]. PMIP6 provides mobility to
IP hosts without requiring any protocol enhancements or additional
capabilities on the host.
Current PMIP6 specification fully defines how to provide mobility
support for mobile nodes with a single interface roaming in a PMIP6
domain. The goal of this BOF is gain understanding of how to support
nodes with multiple interfaces (of possible different technologies) in a
PMIP6 network.

In particular, this BOF assumes the following scenario:
We have a single PMIP6 domain that has deployed multiple
access technologies and needs to support nodes that have
multiple interfaces, possibly of different technologies.

In particular, the following capabilities are needed:

- Inter-technology handover support. The MN has initiated a
communication over one interface and it needs to be able to move
the established connection to a different interface of
a possibly different technology. The reason for moving
the communication to another interface is because of the MNs 
mobility and attaching via a different interface. Basically 
the ability to perform handovers that span different access 
technologies.

- Multihoming support. The MN with multiple interfaces of possibly
different technologies should be able to use them simultaneously to
exchange data and manage the mobility of communications
established through the different interfaces.

- Flow mobility. A MN with multiple interfaces of possibly
different technologies must be able to move a flow from
one interface to another. Moreover, the MN should be able
to inform the network through which interface it wishes
to receive different types of flows.

In order to provide the support for these capabilities, different
approaches can be envisioned, namely:
- L2 only approaches. In this type of approaches, the mechanisms 
to provide the required capabilities are fully L2 mechanisms and 
no modification of the IP layer is needed.
- L3 only approaches. In this type of approaches, the mechanism to
provide to required capabilities are located in the IP layer
- Hybrid L2/L3 approaches. In this case, some mechanisms are
located in L2 and other mechanisms are located in L3.
Now, the different possible approaches vary greatly in their nature
and resulting capabilities. To understanding the benefits and 
suitability of these alternatives, the requirements have to be 
properly defined and understood.

The main goal of the BOF is understanding the need for work in the 
IETF in this area. In order to do so, during the BOF, we will attempt to: 

1) Understand the applicable scenarios, and the problem statement related to
those
2) Understand the restrictions and requirement imposed to solutions to
address the problem statement and scenarios
3) Get an overview of the proposed solutions