Re: comments/questions of draft-yegin-dmm-cnet-homing-00

On Jul 24, 2013, at 11:56 AM, Jouni Korhonen wrote:

> Alper, authors,
> 
> In Section 3. is states:
> 
>  "CHA may be co-located with the CN, or located in the same site as the
>   CN, or located in an ISP serving that site.  Not all CNs may be
>   served by a CHA.  In case there is no CHA serving the CN, the MN and
>   the CN may communicate using the HoA via the HA.  It is expected that
>   CHAs would be deployed for dominant content sites on the Internet
>   (e.g., YouTube, Facebook, Netflix, etc.)"
> 
> What would be the motivation or business reason for a service/content
> provider to start offering a mobility anchoring service? High bandwidth
> sites as listed above would need invest quite much for such a platform.
> 

Here's our thinking:

- The direct benefit of this approach to the content provider is the reduction of transmission latency due to elimination of the triangular routes. This would enhance the their user experience.

- Considering the overall system (w/o distinguishing between the MNO and the content provider), providing anchoring/mobility near the CNet as opposed to doing it at a corner of the Internet reduces the overall cost. Given the savings, the involved parties can find a fair way to deal with it (i.e., some business deal).

On top of that, this can be provided by ISPs serving the content sites. Such ISPs can also have a business deal with the MNO for taking over the mobility management load.


> I also started thinking that in general this solution (and quite many
> other) seem to assume the CN is more or less stationary. How would the
> CHA concept be affected if the CN is also mobile? Would it allow any
> benefits over the legacy MIP variants? How would the CHA discovery 
> work in this case?
> 

We didn't consider mobile CNs. We are going after the major sources of mobile traffic, which is stemming from fixed sites.


> The examples in Sections 3. and 4. show DNS as the discovery mechanism
> for the CHA. However, there is no real description how the discovery
> is actually carried out (except conceptual CHA domain name referred
> in Section 3.

It's just a matter of storing cha.<yourdomain> in DNS and looking it up.
We can add some more verbiage, if this is not clear.

> Figure 1 step 2). Have you considered other discovery
> mechanisms than DNS?
> 

We did some but this one seemed to be the most straightforward. 
Any specific recommendations?

Alper




> - Jouni
> 
> 
> 
> 
>