Le 30/01/2014 15:03, Brian Haberman a écrit :
Anthony,
      I am fine with that.  I would like feedback from the rest of the WG
on these changes.

Brian

On 1/29/14 1:53 PM, h chan wrote:
Delete those explanatory sentences then.

    REQ5:  Co-existence with deployed networks and hosts

           The DMM solution MUST be able to co-exist with existing
           network deployments and end hosts.
           Furthermore, a DMM solution SHOULD work across different
           networks, possibly operated as separate administrative
           domains, when allowed by the trust relationship between them.

I agree with this formulation of this requirement.

If I take a route update mechanism (such as based on BGP), I think it could fulfill that requirement.

Many network deployments involve BGP, so this would be compatible.

When inter-connecting domains in a secure manner, BGP would also work.

The problem would be, of course, not to disturb it too much, if I can say so. I suppose there is a requirement for this as well.

Alex


H Anthony Chan


-----Original Message-----
From: Brian Haberman [mailto:[email protected]]
Sent: Wednesday, January 29, 2014 8:01 AM
To: h chan; [email protected]; [email protected]; Peter 
McCann
Subject: Re: [DMM] AD Evaluation: draft-ietf-dmm-requirements



On 1/28/14 4:33 PM, h chan wrote:
Regarding the following:

- What is meant by co-exist in REQ5?  Does this mean that a DMM solution does 
not break an existing one?  Or does it mean that it must inter-operate with 
existing ones?  Is this like IPv4 and IPv6 being incompatible, but can run 
concurrently on the same network?  Or does this mean there needs to be some 
mechanism for interaction (i.e., like NAT64)?



I think the bottom line is that the existing ones do not break.



Original

    REQ5:  Co-existence with deployed networks and hosts



           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 co-exist with a network or mobile
hosts/routers

           that do not support DMM protocols.  The mobile node may also

           move between different access networks, where some of them
may

           support neither DMM nor another mobility protocol.

           Furthermore, a DMM solution SHOULD work across different

           networks, possibly operated as separate administrative

           domains, when allowed by the trust relationship between them.



We can change to:

    REQ5:  Co-existence with deployed networks and hosts



           The DMM solution MUST be able to co-exist with existing

           network deployments and end hosts without breaking them.
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 co-exist with a network or mobile
hosts/routers

           that do not support DMM protocols.  The mobile node may also

           move between different access networks, where some of them
may

           support neither DMM nor another mobility protocol.

           Furthermore, a DMM solution SHOULD work across different

           networks, possibly operated as separate administrative

           domains, when allowed by the trust relationship between them.

The "without breaking" is fine.  However, the "need to be compatible with" 
phrasing is still problematic.  Is that inferring that in some situations that a DMM solution would 
need to interact with, for example, PMIP?

Regards,
Brian




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



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

Reply via email to