Marco Liebsch | 18 Dec 12:03 2014
Picon

Data-Plane anchors in a control-/data-plane separated deyploment

Folks,

at IETF91 we received the valid comment to converge on a definition of the term ‘anchor’.
In the FPSM discussion, we so far distinguished Data-Plane Anchor (DPA), traditionally a downlink encap function,
Data-Plane Node (DPN), which is more located in the access to terminate tunnels, and regular transport nodes.

Another comment was about a scenario where a single flow may traverse multiple DPAs on its way to the
MN.

 

I’d like to propose and discuss the following:
In a decentralized data-plane and a control-/data-plane separated deployment, I consider it a reasonable
assumption that each of the so far unambiguously named data-plane nodes can take the role of the other.
So, we may solely refer to a single type of function, e.g. Data-Plane Anchor (DPA), which receives policies
from the Control-Plane.

For a certain deployment, it’s the Control-Plane that determines the role and associated policies for each involved
DPA.

 

Data-Plane nodes are agnostic to the role they play in mobility management.

Control-Plane determines the role of each DPA according to the preferred deployment and configures the
policies accordingly.

 

I think such assumption allows flexible deployment and eases description in our specifications.

 

I am not good in drawing ASCII, but I gave it a try (for downlink operation only).

Using PMIP6 terms, the middle-DPA in the figure below serves as kind of LMA, left DPA as MAG,
right DPA (one or multiple) may enforce per-host rules for traffic steering.

 

Would be happy to get your opinion on this proposal.

 

marco

 

                           

               +--------------------------+

               |      Control-Plane       |

               +--------------------------+

                |             |         |

                |             |         |

                |             |         |

         \ /    V             V         V

+--+     -o-  +---+         +---+     +---+   +--+

|MN| ---- |---|DPA|<========|DPA|<----|DPA|<--|CN|         

+--+      |   +---+         +---+     +---+   +--+

              Rules:       Rules:     Rules:

              Decap,       Encap,     host-route

              Forward      Forward,

                          qos

 

 

 

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Marco Liebsch | 18 Dec 10:53 2014
Picon

[FPSM] Friday's WebEx call

Please find below the WebEx info for tomorrow’s FPSM call.

I put the following items on the agenda:

 

() Confirmation of IETF91 discussion and received advice

() Synergies with other IETF activity

() FPSM data model

() Next steps

() Chat about.. Expectation from concrete protocol implementations (if time permits)

() Chat about.. Deployment models (if time permits)

() Usual AoB for the year’s end.. J

 

marco

 

 

 

 

Topic: DMM

Date: Friday, December 19, 2014

Time: 7:00 am, Pacific Standard Time (San Francisco, GMT-08:00)

Meeting Number: 200 916 187

Password: dmm

 

-------------------------------------------------------

To join the meeting online(Now from mobile devices!)

-------------------------------------------------------

1. Go to

https://cisco.webex.com/ciscosales/j.php?MTID=mc842327a99d63e82b748e4dfebed

a664

2. If requested, enter your name and email address.

3. If a password is required, enter the meeting password: dmm

4. Click "Join".

5. If the meeting includes a teleconference, follow the instructions that

appear on your screen.

 

-------------------------------------------------------

To join the audio conference only

-------------------------------------------------------

To receive a call back, provide your phone number when you join the

meeting, or call the number below and enter the access code.

Call-in toll number (US/Canada): +1-408-525-6800

Call-in toll-free number (US/Canada): +1-866-432-9903

 

Having trouble dialing in? Try these backup numbers:

Call-in toll-free number (US/Canada): +1-866-432-9903

Call-in toll number (US/Canada): +1-408-525-6800

 

Access code:200 916 187

Global call-in numbers:

https://cisco.webex.com/ciscosales/globalcallin.php?serviceType=MC&ED=29675

6737&tollFree=1

Toll-free dialing restrictions:

http://www.webex.com/pdf/tollfree_restrictions.pdf

 

 

 

 

CCP:+14085256800x200916187#

 

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio

and any documents and other materials exchanged or viewed during the

session to be recorded. By joining this session, 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 session. Please note that any such recordings may be subject

to discovery in the event of litigation.

 

 

 

 

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Marco Liebsch | 12 Dec 14:53 2014
Picon

[FPSM] next WT call

Folks,

as follow-up of two good work team side meetings during IETF91, I’d like to schedule
this year’s last telco. Please participate in the doodle poll (pointer below in this eMail)
if you plan to attend.

 

Best regards,

Marco

 

http://doodle.com/5ax4qr3zrtms3t94

 

 

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
H Anthony Chan | 10 Dec 18:28 2014
Picon

enhanced mobility anchor teleconference

 
The second teleconference of enhanced mobility anchor work team was held on Nov 26 at 7am Central time. The participants are
Jouni Korhonen
Alex Petrescu
Danny Moses
Fred Templin
Giang Nguyen
Jong-Hyouk Lee
Seil Jeon
Xuan
H Anthony Chan

Introduction: Anthony quoted the charter statement about the possible work items and suggests to clarify what is the anchor and discuss/understand the technical issues.
• Enhanced mobility anchoring: define protocol solutions for a gateway and mobility anchor assignment and mid-session mobility anchor switching that go beyond what has been specified, for example, in RFC 6097, 6463, and 5142. Traffic steering associated with the anchor switch is also in-scope if deemed appropriate.

Danny proposes a draft definition of a mobility anchor. It is modified to include both hosts and mobile router. The discussion has changed to mention only router and not switch. It appears this definition is basically the purpose of the anchor:
• A mobility anchor is a network entity that overrides the basic function of routers in order to assure that traffic flows to and from a mobile node/router even when it hands off from one network to another with different IP prefixes

Alex presented about the differences in mobility anchor for host versus networks in order to help us understand whether enhanced anchor applies also to mobile router. Fred noted that the basics for a moving network applies to AERO which is also a solution for moving network.

Jong-Hyouk asked whether the work on enhanced mobility anchor assumes the AAA functions are present. It is suggested to present/discuss in more details next time.

Seil would like to propose solution on anchor switching, and it is suggested to present in the next teleconference. 
 
Presentations which have been revised per comments during the teleconference are attached.

H Anthony Chan

Attachment (enhanced-anchor-for-moving-networks.pptx): application/vnd.openxmlformats-officedocument.presentationml.presentation, 77 KiB
Attachment (EnhancedMobilityAnchor.pptx): application/vnd.openxmlformats-officedocument.presentationml.presentation, 103 KiB
_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Jouni | 24 Nov 23:36 2014
Picon

WebEx meeting scheduled: DMM Enhanced anchor telco

DMM Enhanced anchor telco

Wednesday 26 November 2014
7:00  |  Central Standard Time (Chicago, GMT-06:00)  |  1 hr 30 min
 
Join WebEx meeting
(Join WebEx meeting)
Meeting number:
649 556 328
Meeting password: dmm1911
 
Join by phone
1-877-668-4493 Call-in toll free number (US/Canada)
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 649 556 328
Toll-free calling restrictions
 
Add this meeting to your calendar.
 
Can't join the meeting? Contact support.
 
IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. You should inform all meeting attendees prior to recording if you intend to record the meeting.
Attachment (WebEx_Meeting.ics): text/calendar, 4798 bytes

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Alexandru Petrescu | 12 Nov 06:43 2014
Picon

Mobile IPv6 maintenance: HA never deletes a tunnel

Hello,

There is a bug in an otherwise very good Mobile IPv6 Home Agent 
implementation.  This particular Home Agent never deletes a tunnel 
interface.  As such it does not support MNs which are silent for a 
while; when they come back up the tunnel is still there and cant be 
modified.

A forcing de-register (BU lifetime 0) does not delete it either.

This particular platform has a good Mobile IPv4 implementation.

Am I the only one to experience this bug?

Alex
Jouni Korhonen | 10 Nov 14:48 2014
Picon

meeting slides

Folks,

Send your slide material to the chairs latest by Tuesday lunchtime.

Jouni & Dapeng
The IESG | 7 Nov 18:44 2014
Picon

Document Action: 'Distributed Mobility Management: Current practices and gap analysis' to Informational RFC (draft-ietf-dmm-best-practices-gap-analysis-09.txt)

The IESG has approved the following document:
- 'Distributed Mobility Management: Current practices and gap analysis'
  (draft-ietf-dmm-best-practices-gap-analysis-09.txt) as Informational
RFC

This document is the product of the Distributed Mobility Management
Working Group.

The IESG contact persons are Brian Haberman and Ted Lemon.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dmm-best-practices-gap-analysis/

Technical Summary

   The present document analyzes deployment practices of existing IP
   Mobility protocols in a distributed mobility management environment.
   The analyzed IP level (i.e., layer 3) mobility protocols include those
   developed by IETF and also those developed by other SDOs that have
   been widely deployed. Due the plurality of different mobility enabling 
   protocol and solutions, the analysis has been intentionally limited to
   IP level (i.e., layer 3) protocol that typically are based on some sort of
   tunneling solution. The document then identifies existing limitations when
   compared to the distributed mobility management requirements defined in
   draft-ietf-dmm-requirements for a distributed mobility management solution.

   On the existing IP mobility enabling architectures (outside mobile VPNs or
   IETF defined IP mobility solutions), the document considers only the 3GPP 
   GPRS/EPS system and service provider Wi-Fi due their dominant positions
   in the market place.

Working Group Summary

   The document creation was not entirely smooth as seen from the timeline.
   There are several aspects in the existing deployments making use of IP
   mobility (such as the 3GPP GPRS/EPS) that already today include many
   enhancements on the deployment & product feature level that can be seen
   as a step towards distributed mobility management. The line between what
   is a gap and what can be achieved with today's tools was not always exactly
   clear. However, the WG has an agreement on the gaps described in this
   document and the fact that the most prevalent solutions that exist are not
   defined in IETF and are specific to certain system architectures.

Document Quality

   There are no implementations of this document, since it only
   presents an analysis of existing protocols and deployments to
   what is intended to be achieved with distributed mobility management.

   The document has received multiple thorough reviews in the WG.

Personnel

   Jouni Korhonen (jouni.nospam@...) is the document shepherd.
   Brian Haberman (briad@...) is the AD.
Marco Liebsch | 2 Nov 21:40 2014
Picon

[FPSM] Work Item call#2 agenda and WebEx info

Please find below the WebEx details for the 2nd work item call on Forwarding Path and Signaling Management.

Thanks to Sri for providing the WebEx communications platform.

The call is scheduled on Monday, 3rd Nov 2014 from 16:00 CET / 07:00am PST. Duration is 90 min.

 

Below are the proposed items for the call’s agenda. Please let me know if you have additional
agenda items in mind which we should discuss during this call.

 

--- Draft agenda FPSM WI call#2 ---

 

-          Tools: platform for slides/document sharing, WebEx

-          Discussion of categories and associated use cases

o   Tunnel Management

o   Routing Policy Management

o   IP Route Management

o   Traffic Steering Policies

o   QoS Policies

o   Queries

o   Notifications

-          Need for session awareness at DPA/DPN?

 

 

 

 

 

--------

Topic: DMM - CP/DP Interface Meeting #2 
Date: Monday, November 3, 2014 
Time: 7:00 am, Pacific Standard Time (San Francisco, GMT-08:00) 
Meeting Number: 207 634 298 
Password: dmm 

------------------------------------------------------- 
To join the meeting online(Now from mobile devices!) 
------------------------------------------------------- 
1. Go to https://cisco.webex.com/ciscosales/j.php?MTID=m090408bb558e6f1f68e9cf58643b15bd 
2. If requested, enter your name and email address. 
3. If a password is required, enter the meeting password: dmm 
4. Click "Join". 
5. If the meeting includes a teleconference, follow the instructions that appear on your screen. 

------------------------------------------------------- 
To join the audio conference only 
------------------------------------------------------- 
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code. 
Call-in toll number (US/Canada): +1-408-525-6800 
Call-in toll-free number (US/Canada): +1-866-432-9903 

Having trouble dialing in? Try these backup numbers: 
Call-in toll-free number (US/Canada): +1-866-432-9903 
Call-in toll number (US/Canada): +1-408-525-6800 

Access code:207 634 298 
Global call-in numbers: https://cisco.webex.com/ciscosales/globalcallin.php?serviceType=MC&ED=290960577&tollFree=1 
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf 


 

_______________________________________________
dmm mailing list
dmm@...
https://www.ietf.org/mailman/listinfo/dmm
Alper Yegin | 1 Nov 17:36 2014

Fwd: Invitation to WebEx meeting: IETF DMM Mobility Exposure & Selection WT call#2

Second conference call for Mobility Exposure & Selection WT is on Nov 6th, 4:30-6:00pm (GMT+02).
Webex details are below.

In this call, we'll discuss the following item (among the ones we determined on the first call):

- Describe how IP address type is communicated between the apps and IP stack on the MN.

Alper









Begin forwarded message:

From: Alper Yegin via Cisco WebEx <admin-tlbQiRySkngAvxtiuMwx3w@public.gmane.org>
Subject: Invitation to WebEx meeting: IETF DMM Mobility Exposure & Selection WT call#2
Date: November 1, 2014 6:26:16 PM GMT+02: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:
  
IETF DMM Mobility Exposure & Selection WT call#2
Thu, Nov 6, 4:30 pm | 1 hr 30 min
Istanbul (Eastern Europe Time, GMT+02:00)
Host: Alper Yegin
  
 
Add the attached iCalendar (.ics) file to your calendar.
 

Agenda

This meeting does not have an agenda.
 

Access Information

Where:   WebEx Online
Meeting number:   239 022 558
Password:   This meeting does not require a password.
 

Audio Connection

+44-203-478-5289 UK Domestic Toll
Access code: 239 022 558

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
Alexandru Petrescu | 29 Oct 16:15 2014
Picon

Maintenance of Mobile IPv6

Hello,

There are a few things that I think are needed for the maintenance of 
protocol Mobile IPv6; most important appear first:

- help with automated portal authentication in WLAN.  Hopping on and
   off from a WiFi hotspot to another, even without moving physically,
   is often obstructed by web portal authentication requiring user
   to type to fill forms; this is not only inconvenient, but in some
   cases it is impossible, like with vehicular networks where the
   driver is forbidden by law to type while behind the wheel.

- bugs in an otherwise reliable Mobile IPv6 implementation of
   a particular equipment manufacturer (HA never deletes a tunnel,
   lifetime: remaining never): should the bugs be corrected or shoudl
   the spec modified to reflect what the implementation actually
   does?  Should protocol workarounds be designed to deal with this
   problem?

- future of the maintenance of the linux open source Mobile IPv6
   implementation: just for my clarification - is it still ok?  Is there
   some project behind it?  Or is it dying?  Currently the email list
   seems silent, and the latest software releases date back to more than
   one year.

- elimination, or reducing the effect, of the necessity of the 'focal
   point' Home Agent: route optimization for the masses and for moving
   networks as deployed in vehicles.

- Mobile IPv6 and IPv6 NAT Traversal;

- IPv6 NAT in a moving network;

- bypassing Mobile IPv6 implementation (and use IPv6 NATting) in cases
   of particular applications, based on destination IPv6 address and
   IPv6-only-when-reversed FQDN name.

- the use of ULAs combined with Global addresses, with Mobile IPv6
   (e.g. ULA HoA but GUA CoA, or reverse).

What do you think?

Alex

Gmane