REQ5: dmm requirement -- Compatibility

h chan <[email protected]>
Newsgroups gmane.ietf.nemo
Message-ID <6E31144C030982429702B11D6746B98C270DD20A__16859.401172451$1346973280$gmane$org@SZXEML505-MBS.china.huawei.com>
Please check this updated REQ5 in draft-ietf-dmm-requirements-02:

   REQ5:  Compatibility

          The DMM solution MUST be able to co-exist with existing
          network deployments and end hosts.  For example, depending on
          the environment in which DMM is deployed, DMM solutions may
          need to be compatible with other deployed mobility protocols
          or may need to interoperate with a network or mobile hosts/
          routers that do not support DMM protocols.  Furthermore, a DMM
          solution SHOULD work across different networks, possibly
          operated as separate administrative domains, when allowed by
          the trust relationship between them.

          Motivation: The motivations of this requirement are (1) to
          preserve backwards compatibility so that existing networks and
          hosts are not affected and continue to function as usual, and
          (2) enable inter-domain operation if desired.

   This requirement addresses the following related problem O-PS2.

   O-PS2:  Complicated deployment with too many MIP variants and
           extensions

           Deployment is complicated with many variants and extensions
           of MIP.  When introducing new functions which may add to the
           complexity, existing solutions are more vulnerable to break.

H Anthony Chan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.