Hello folks,

I'm not sure that SDN considerations are a requirement for DMM,
but I am sure that we should at least allow the discussion.

One possibility would be that SDNC would collect information
from DMM, and influence the distribution of mobility anchors.
That's got to be relevant.

Regards,
Charlie P.


On 7/16/2012 7:50 AM, jouni korhonen wrote:
On Jul 13, 2012, at 8:11 AM, Keshav.A.K. wrote:

Hi,

I have one basic question about thinking process going on this these days
...
There is a global Trend to 'Centralized the Controlling Function' by 'SDNC
concept' which can be used to program network/Nodes ...
Conversely there is thinking process going on to distribute the existing
'Centralized Functionality'.

I there is strong requirement to converge these thinking process.
While SDNs, SNDPs etc are interesting and partially may overlap conceptually
I think there is no requirement or even a need trying to mate these two
together in a DMM solution requirement level. SDN technologies can well be
applied in the implementation space, though.

- Jouni



keshava



-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Monday, July 09, 2012 6:47 PM
To: [email protected]
Cc: [email protected]
Subject: [DMM] I-D Action: draft-ietf-dmm-requirements-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Distributed Mobility Management Working
Group of the IETF.

        Title           : Requirements of distributed mobility management
        Author(s)       : H Anthony Chan
        Filename        : draft-ietf-dmm-requirements-00.txt
        Pages           : 16
        Date            : 2012-07-06

Abstract:
   The traditional hierarchical structure of cellular networks has led
   to deployment models which are heavily centralized.  Mobility
   management with centralized mobility anchoring in existing
   hierarchical mobile networks is quite prone to suboptimal routing and
   issues related to scalability.  Centralized functions present a
   single point of failure, and inevitably introduce longer delays and
   higher signaling loads for network operations related to mobility
   management.  This document defines the requirements for distributed
   mobility management for IPv6 deployment.  The objectives are to match
   the mobility deployment with the current trend in network evolution,
   to improve scalability, to avoid single point of failure, to enable
   transparency to upper layers only when needed, etc.  The distributed
   mobility management also needs to be compatible with existing network
   deployments and end hosts, and be secured.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-requirements

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dmm-requirements-00


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm
_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm



--
Regards,
Charlie P.

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm

Reply via email to