Marco Liebsch | 23 Jan 18:06 2015

[FPSM] next telco

Please enter your availability for a 90min WebEx call next week by this week Saturday.






dmm mailing list
Alper Yegin | 23 Jan 14:28 2015

Mobility Exposure and Selection WT call


Please mark your availability on the following doodle for our next DMM WG Mobility Exposure and Selection WT call:

Register your availability no later than the end of Monday (Jan 26).


dmm mailing list
Z.W. Yan | 12 Jan 01:54 2015

New Version Notification for draft-yan-dmm-hnprenum-00.txt

We submitted a draft about the HNP renumbering support in PMIPv6.
As stated in this draft, the HNP renumbering was mentioned in PMIPv6 specification (RFC 5213), but the solution was not given.
We adopt the RFC 7077 to solve this issue and then this drfat is an extension of RFC 7077 or a use case of RFC 7077.
Besides, the DNS update caused by the HNP renumbering is briefly discussed.
Because we are not sure whether DMM has interest on this issue and the related solution, please check this draft and give us comments and feedbacks.
Thank all of you.
Z.W. Yan
dmm mailing list
Chun Tung Chou | 3 Jan 12:22 2015


                           Call for Papers
                           ACM NANOCOM 2015
2nd ACM International Conference on Nanoscale Computing and Communication
September 21 - 22, 2015
Boston, MA, USA
Submission deadline: March 6, 2015

The ACM NANOCOM series of conferences aim to bring together researchers from
diverse disciplines  that can foster and develop new communication and computing
paradigms for nanoscale devices. Following the inaugural edition of the
conference in Atlanta, Georgia in May 2014, the second edition of the conference
will take place in Boston, Massachusetts on September 21-22, 2015.

We invite submissions with original (unpublished and not currently under review)
and novel contributions on nanoscale communication in areas including (but not
limited to), the following:

* Nano-electromagnetic communication
[ Plasmonic and nanophotonic devices for THz and optical communication;
Channel modeling for THz and optical communication.]

* Molecular communication
[ Communication components in the biological/ chemical/ mechanical environments;
Channel modeling for molecular communication.]

* Information theory for nanoscale communication networks

* Network architecture and protocols for nanoscale communication networks

* Experiments, implementation and testbeds for nanoscale communication networks

* Interfaces among nanoscale communication networks

* Energy efficiency in nanoscale communication networks

* Nano-computing paradigms
[ Neuromorphic computing, DNA and molecular computing, membrane computing and
quantum computing.]

* Future emerging applications of nano/molecular communication
[ Internet of Nano-Things or Nano-Bio-Things, Wireless Nanosensor Networks,
Wireless Network on Chip, nanomedicine, targeted drug delivery, and other
future and emerging applications.]

Submission Instructions and Important Dates:

Papers submitted to ACM NANOCOM 2015 must be original, not previously published
or accepted for  publication elsewhere, and they must not be submitted to any
other event or publication during the  entire review process. Paper submissions
should follow the ACM double-column format for conferences, available at:

A maximum of 6 pages are allowed for each paper, all figures and references
included.  Submitted papers will undergo a peer review process, coordinated by
the Program Committee.  All accepted paper will be published by ACM and submitted
for indexing by ISI, EI Compendex, Scopus, Google Scholar and many more. In
addition to the main conference, ACM NANOCOM 2015 will have a series of special
sessions, as well as poster sessions.

Full Paper Due:                      March 6, 2015
Notification of Acceptance:          May 6, 2015
Camera Ready Paper Due:              July 1, 2015

General Chairs:
Faramarz Fekri, Georgia Institute of Technology, USA
Sasitharan Balasubramaniam, Tampere University of Technology, Finland

General Vice-Chair:
Tommaso Melodia, Northeastern University

Technical Program Committee Chairs:
Tadashi Nakano, Osaka University
Ilangko Balasingham, Norwegian University of Science and Technology

Steering Committee:
Ian F. Akyildiz, Georgia Institute of Technology
Raghupathy Sivakumar, Georgia Institute of Technology
Faramarz Fekri, Georgia Institute of Technology
Sasitharan Balasubramaniam, Tampere University of Technology
Ozgur Akan, Koc University
Albert Cabellos, Universitat Polit├Ęcnica de Catalunya

Contact Us:
Tadashi Nakano, Osaka University, Japan
e-mail: tadasi.nakano@...
Ilangko Balasingham, Norwegian University of Science and Technology, Norway
e-mail: ilangko.balasingham@...

Chun Tung Chou
Associate Professor
School of Computer Science and Engineering
The University of New South Wales
Sydney, NSW 2052, Australia
Phone: +61-2-9385 7203
Fax:+61-2-9385 5995
Email: ctchou@...

Legal disclaimer:
The CRICOS Provider Code for UNSW is 00098G.
Marco Liebsch | 18 Dec 12:03 2014

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


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


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


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.






               |      Control-Plane       |


                |             |         |

                |             |         |

                |             |         |

         \ /    V             V         V

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

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

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

              Rules:       Rules:     Rules:

              Decap,       Encap,     host-route

              Forward      Forward,





dmm mailing list
Marco Liebsch | 18 Dec 10:53 2014

[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







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


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:


Toll-free dialing restrictions:







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
Marco Liebsch | 12 Dec 14:53 2014

[FPSM] next WT call


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,




dmm mailing list
H Anthony Chan | 10 Dec 18:28 2014

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
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
Jouni | 24 Nov 23:36 2014

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
Alexandru Petrescu | 12 Nov 06:43 2014

Mobile IPv6 maintenance: HA never deletes a tunnel


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 

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?

Jouni Korhonen | 10 Nov 14:48 2014

meeting slides


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

Jouni & Dapeng