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

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.

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?

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. Figure 1 step 2). Have you considered other discovery
mechanisms than DNS?

- Jouni