Re: identity persistence and comparison issues
Geoff Huston <[email protected]>
| Newsgroups | gmane.ietf.multi6 |
|---|---|
| Message-ID | <[email protected]> |
Many thanks Joe - I'd be willing to use these points. Geoff At 05:12 AM 15/06/2004, Joe Touch wrote: >Hi, all, > >Here are the issues I sent separately to Elliot Lear to add to his 'q&a' >draft, which might overlap some of the content of Geoff Huston's... > >---------------- > >Some additional questions came to mind; use at your own risk... > >1. you ask if a solution can be aggregated > > this presumes that aggregation is beneficial, > i.e., it would be useful to add > "is aggregation useful or necessary to the solution?" > >2. you asked about load on nameserver. based on some solutions I've seen, >it would be useful to ask: > > does the solution create an alterate DNS-like service? > should this be separate from or part of the DNS? > >3. does the endpoint ID change on the fly or is it static/cacheable? > > specific variants of this issue: > > a) are two IDs comparable within the same app over time? > i.e., can an ID change? if so, can the old ID be used? > > b) can two IDs on different apps on the same node be compared? > > c) can two IDs on different nodes be compared? > >this specifically affects debugging, logging, and caching. > >Joe > >