IETF Secretariat | 20 Jul 00:32 2014
Picon

Milestones changed for dmm WG

Changed milestone "Submit I-D 'Gap Analysis' to the IESG for
consideration as an Informational RFC.", resolved as "Done".

URL: http://datatracker.ietf.org/wg/dmm/charter/
Alper Yegin | 19 Jul 10:44 2014

DMM solution space categorization



I've updated the list with the I-Ds suggested by Behcet/Fred/Jouni.

Please see below for my opinions about how each category relates to the overall work.
Comments welcome.


1. Per-flow IP address configuration according to mobility needs

Apps indicating their mobility needs to the IP stack on the MN, and associated IP configuration signaling between the MN and the network.

draft-bhandari-dhc-class-based-prefix-03
draft-korhonen-dmm-prefix-properties-00.txt
draft-yegin-dmm-ondemand-mobility-02

This category is essential, given that we all agree mobility will be treated on a per-flow basis.
(and once we dive into the category, I'd say the aforementioned I-Ds are complementary).



2. Mobility solution selection 

MN determining the type of mobility solution(s) it'd apply to a given flow.

draft-yegin-ip-mobility-orchestrator-00

In recognition of L4+ mobility solutions (such as MPTCP, SIP, apps having their own), this also becomes essential for a DMM solution. Some people may argue, discussion is very welcome.



3. IP anchor selection

MN selecting the IP anchor node after it decides to use IP anchoring (whether in the access network or the core network).

draft-aliahmad-dmm-anchor-selection-00.txt

This category is supporting the Category 4, 5 and 6. This is about more intelligent way of picking the IP anchor once the type of anchor is determined.
This may produce a standalone I-D, or may be folded into individual solutions in those categories. 


4. Access network anchoring

Anchoring IP address within the access network using IP-in-IP tunneling.

draft-bernardos-dmm-cmip-01
draft-bernardos-dmm-pmip-03
draft-bernardos-dmm-distributed-anchoring-04
draft-chan-dmm-enhanced-mobility-anchoring-00
draft-sarikaya-dmm-for-wifi-00.txt
draft-seite-dmm-dma-07.txt
draft-xuan-dmm-nemo-dmm-02.txt
draft-korhonen-dmm-local-prefix-01

The need for this category is well-understood. The challenge is having plethora of solutions. Though the main concept is common… 


5. Corresponding node/network anchoring

Anchoring IP address on the Corresponding Node or Corresponding Network.

Mobile IPv6 route optimization
draft-yegin-dmm-cnet-homing-02
draft-xiong-dmm-ip-reachability-01
draft-templin-aerolink-29


This category of solutions are also needed (for their ability to produce better paths and different applicability with respect to the Category 4)


6. Host-route based intra-domain solutions

Non-tunneling solutions.

draft-chan-dmm-enhanced-mobility-anchoring-00
draft-matsushima-stateless-uplane-vepc-02
draft-mccann-dmm-flatarch-00
draft-sarikaya-dmm-for-wifi-00.txt

Solutions in this category are competing with the Category 4 type solutions. There are various pros and cons. IMHO, we cannot resolve that contest, hence we should produce solution for both categories and let the industry pick and choose. Given that these solutions are isolated from the other components (categories), standardizing both should not have adverse impact on the overall DMM complexity.

Alper



_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Jouni Korhonen | 18 Jul 19:29 2014
Picon

Presentation slideware for IETF90 meeting

Folks,

Those who are on the agenda send your slideware to the chairs latest 
during Tuesday for the Thursday meeting slot, and latest during 
Wednesday for the Friday meeting slot.

- Jouni & Dapeng
Alper Yegin | 16 Jul 09:00 2014

Invitation to WebEx meeting: Next-Generation Mobility Protocols and Architectures, Call #6

Folks,

Tomorrow's presentation is "IP Mobility Protocols for Multihomed Residential Gateways (RG) in Fixed Networks" by Pierrick.

See below for the Webex details.

Alper



Begin forwarded message:

From: Alper Yegin via Cisco WebEx <admin-tlbQiRySkngAvxtiuMwx3w@public.gmane.org>
Subject: Invitation to WebEx meeting: Next-Generation Mobility Protocols and Architectures, Call #6
Date: July 16, 2014 9:54:34 AM GMT+03:00

div,p,td,span{word-wrap:break-word; word-break:normal;} table{border-collapse:separate}
Hi,
 
Alper Yegin is inviting you to this WebEx meeting:
  
Next-Generation Mobility Protocols and Architectures, Call #6
Thu, Jul 17, 5:00 pm | 1 hr 30 min
Istanbul (Eastern Europe Summer Time, GMT+03:00)
Host: Alper Yegin
  
 
Add the attached iCalendar (.ics) file to your calendar.
 

Agenda

Pierrick Seite will be presenting "IP Mobility Protocols for Multihomed Residential Gateways (RG) in Fixed Networks"
 

Access Information

Where:   WebEx Online
Meeting number:   237 746 746
Password:   This meeting does not require a password.
 

Audio Connection

+44-203-478-5289 UK Domestic Toll
Access code: 237 746 746

Can't access your meeting? Get help.
Delivering the power of collaboration
Cisco WebEx Team
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the meeting to be recorded. By joining this meeting, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the meeting. Please note that any such recordings may be subject to discovery in the event of litigation.

©2014 Cisco and/or its affiliates. All rights reserved.
MT-A-001


_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Alper Yegin | 12 Jul 13:13 2014

DMM solution space

Folks,

I went over the solutions and categorized them.

I haven't covered all of the solutions (due to lack of time). For any I-D that is missing, please state the name and where you think it belongs to.

When we agree with the categorization and the candidates for each, then we can proceed to discussing how we can converge. 

Note: Multiple I-Ds under each category may be complementary, competing, or orthogonal (e.g., due to different applicability). It's case by case.


Cheers,



- Per-flow IP address configuration according to mobility needs

Apps indicating their mobility needs to the IP stack on the MN, and associated IP configuration signaling between the MN and the network.

draft-bhandari-dhc-class-based-prefix-03
draft-korhonen-dmm-prefix-properties-00.txt
draft-yegin-dmm-ondemand-mobility-02

- Mobility solution selection 

MN determining the type of mobility solution(s) it'd apply to a given flow.

draft-yegin-ip-mobility-orchestrator-00

- IP anchor selection

MN selecting the IP anchor node after it decides to use IP anchoring (whether in the access network or the core network).

draft-aliahmad-dmm-anchor-selection-00.txt


- Access network anchoring

Anchoring IP address within the access network using IP-in-IP tunneling.

draft-bernardos-dmm-cmip-01
draft-bernardos-dmm-pmip-03
draft-bernardos-dmm-distributed-anchoring-04
draft-chan-dmm-enhanced-mobility-anchoring-00
draft-sarikaya-dmm-for-wifi-00.txt
draft-seite-dmm-dma-07.txt
draft-xuan-dmm-nemo-dmm-02.txt


- Corresponding node/network anchoring

Anchoring IP address on the Corresponding Node or Corresponding Network.

Mobile IPv6 route optimization
draft-yegin-dmm-cnet-homing-02
draft-xiong-dmm-ip-reachability-01

- Host-route based intra-domain solutions

Non-tunneling solutions.

draft-chan-dmm-enhanced-mobility-anchoring-00
draft-matsushima-stateless-uplane-vepc-02
draft-mccann-dmm-flatarch-00


_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Marco Liebsch | 11 Jul 17:59 2014
Picon

demand for DMM traffic steering

Folks, I would like to discuss the demand for DMM traffic steering as preparation for
Toronto.

 

DMM enables smart deployment and selection of network components serving as User-Plane
anchor to the mobile node. The MN’s IP address or prefix (HNP/HoA) is assigned to the selected
anchor and bound to the MN’s locator (CoA, pCoA, ..)

 

Now, there are two cases:

 

(1) Selected anchor is in the network of the MN’s HoA/HNP (topologically correct address)

(2) Selected anchor is not in the network of the MN’s HoA/HNP (topologically incorrect address)

 

Case (1) is what IP mobility assumed so far. Default routes in the transport network deliver the
packet into the network which hosts the MN’s assigned anchor.

 

Case (2) can happen in 2 cases:

(a) MN gets assigned a new anchor mid-session but wants to keep its HoA/HNP. That’s what has been
called so far anchor re-location

(b) MN has a stable IP address (e.g. profile-bound) but the network wants to select an anchor
according to the requested service, i.e. anchor should be close to a local server or CDN cache.
In that case the MN’s IP address will be topologically incorrect from the very beginning of its
attachment.

 

All cases (a) and (b) may require steering the MN’s traffic according to a host policy, as the
route deviates from the default.

 

First questions we may rise:

I)                    Are we on the same page regarding the above cases?

II)                  What comes first in DMM: IP address configuration or anchor selection?

 

Hope we can discuss some opinions ahead of the meeting.

marco

 

 

 

 

 

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Behcet Sarikaya | 8 Jul 21:59 2014
Picon

Re: [Dime] Important dates - IETF90 getting close

Hi Jouni,

Can you please add a slot for our draft
draft-sarikaya-dmm-for-wifi-00.txt into the agenda?

Thanks,

Behcet

On Wed, Jun 18, 2014 at 1:42 AM, Jouni Korhonen
<jouni.nospam@...> wrote:
> Folks,
>
> Just to remind you..
>
> 4 July: Internet Draft submission - both -00 and revisions.
>
> 7 July: WG chairs upload WG agendas.
>
> 11 July: Early Bird registration and payment cut-off; the cost to
>         register goes up.
>
> 18 July: Last day to pre-register and pre-pay.
>
> 20-25 July:  90th IETF Meeting in Toronto, ON, Canada.
>         We have requested one meeting slots.
>
> _______________________________________________
> DiME mailing list
> DiME@...
> https://www.ietf.org/mailman/listinfo/dime
Jouni Korhonen | 5 Jul 18:04 2014
Picon

WGLC #3 for draft-ietf-dmm-best-practices-gap-analysis-06

Folks,

This email starts a one week WGLC #3 for 
draft-ietf-dmm-best-practices-gap-analysis-06. The WGLC ends 12th July 
2014 EOB (EEST). Silence is accounted as an acceptance for the content.

Once the WGLC passes the next step is shipping the I-D out of the WG and 
we are then ready to move forward progressing the new WG work.

- Jouni (as a DMM co-chair)
Satoru Matsushima | 5 Jul 11:00 2014
Picon

draft-matsushima-stateless-uplane-vepc-03

Hello DMM,

We have submitted an revised version of the stateless u-plane draft. Please review it and share your comments.

cheers,
--satoru

---------- Forwarded message ----------
From: <internet-drafts-EgrivxUAwEY@public.gmane.org>
Date: Sat, Jul 5, 2014 at 8:42 AM
Subject: New Version Notification for draft-matsushima-stateless-uplane-vepc-03.txt


A new version of I-D, draft-matsushima-stateless-uplane-vepc-03.txt
has been successfully submitted by Satoru Matsushima and posted to the
IETF repository.

Name:           draft-matsushima-stateless-uplane-vepc
Revision:       03
Title:          Stateless user-plane architecture for virtualized EPC (vEPC)
Document date:  2014-07-04
Group:          Individual Submission
Pages:          23
URL:            http://www.ietf.org/internet-drafts/draft-matsushima-stateless-uplane-vepc-03.txt
Status:         https://datatracker.ietf.org/doc/draft-matsushima-stateless-uplane-vepc/
Htmlized:       http://tools.ietf.org/html/draft-matsushima-stateless-uplane-vepc-03
Diff:           http://www.ietf.org/rfcdiff?url2=draft-matsushima-stateless-uplane-vepc-03

Abstract:
   We envision a new mobile architecture for the future Evolved Packet
   Core (EPC).  The new architecture is designed to support the
   virtualization scheme called NFV (Network Function Virtualization).
   In our architecture, the user plane of EPC is decoupled from the
   control-plane and uses routing information to forward packets of
   mobile nodes.  Although the EPC control plane will run on hypervisor,
   our proposal does not modify the signaling of the EPC control plane.
   The benefits of our architecture are 1) scalability, 2) flexibility
   and 3) Manageability.  How to run the EPC control plane on NFV is out
   of our focus in this document.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Behcet Sarikaya | 4 Jul 17:57 2014
Picon

New Version Notification for draft-sarikaya-dmm-for-wifi-00.txt

A new version of I-D, draft-sarikaya-dmm-for-wifi-00.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Name:           draft-sarikaya-dmm-for-wifi
Revision:       00
Title:          Distributed Mobility Management Protocol for WiFi
Users in Fixed Network
Document date:  2014-07-03
Group:          Individual Submission
Pages:          9
URL:
http://www.ietf.org/internet-drafts/draft-sarikaya-dmm-for-wifi-00.txt
Status:         https://datatracker.ietf.org/doc/draft-sarikaya-dmm-for-wifi/
Htmlized:       http://tools.ietf.org/html/draft-sarikaya-dmm-for-wifi-00

Abstract:
   As networks are moving towards flat architectures, a distributed
   approach is needed to mobility management.  This document defines a
   distributed mobility management protocol.  Protocol is based on
   mobility aware virtualized routing system with software-defined
   network support.  Routing is in Layer 2 in the access network and in
   Layer 3 in the core network.  Smart phones access the network over
   IEEE 802.11 (Wi-Fi) interface and can move in home, hotspot and
   enterprise buildings.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat
Alper Yegin | 1 Jul 09:38 2014

Invitation to WebEx meeting: Next-Generation Mobility Protocols and Architectures, Call #5



Call#5, "Next-Generation POP: A Driver for DMM", is tomorrow (Wednesday) at 4pm CET.

Slides can be downloaded from: http://yegin.org/NGmobility/NGPOP_DMM.pdf

Webex details are below.


Begin forwarded message:



div,p,td,span{word-wrap:break-word; word-break:normal;} table{border-collapse:separate}
Hi,
 
Alper Yegin is inviting you to this WebEx meeting:
  
Next-Generation Mobility Protocols and Architectures, Call #5
Wed, Jul 2, 5:00 pm | 1 hr 30 min
Istanbul (Eastern Europe Summer Time, GMT+03:00)
Host: Alper Yegin
  
 
Add the attached iCalendar (.ics) file to your calendar.
 

Agenda

Pierrick Seite will be presenting "Next-Generation POP: A Driver for DMM" 

Slides can be downloaded from http://yegin.org/NGmobility/NGPOP_DMM.pdf
 

Access Information

Where:   WebEx Online
Meeting number:   234 208 564
Password:   This meeting does not require a password.
 

Audio Connection

+44-203-478-5289 UK Domestic Toll
Access code: 234 208 564

Can't access your meeting? Get help.
Delivering the power of collaboration
Cisco WebEx Team
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the meeting to be recorded. By joining this meeting, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the meeting. Please note that any such recordings may be subject to discovery in the event of litigation.

©2014 Cisco and/or its affiliates. All rights reserved.
MT-A-001


_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm

Gmane