On Nov 17, 2011, at 11:05 AM, "Brian E Carpenter" <[email protected]> wrote: > I don't see how we could define a helpful API until the generic problem > of scope is solved (see my previous message). We have no general way > for an application to know or describe the scope that applies to itself and > the peer(s) it wants to talk to.
It seems to me that applications "knowing" what scope they want to talk to is a very isolated special case. E.g., perhaps your set-top box knows that it needs to go through your cable ISP's provisioning domain to get streaming video. But generally speaking, your application wants to connect through whatever provisioning domain works best, which is something no provisioning domain can claim to know; it is something only the host can determine. _______________________________________________ mif mailing list [email protected] https://www.ietf.org/mailman/listinfo/mif
