Misc commentary

git-svn-id: svn://anonsvn.mit.edu/krb5/users/amb/referrals@18547 dc483132-0cff-0310-8789-dd5450dbe970

diff --git a/implementation.notes b/implementation.notes
index 7cdf9adea0a95ef01d94f70d1a0aaab381b348ae..22a7912c3fb4db69514d670eb0ecd79b23551798 100644 (file)
--- a/implementation.notes
+++ b/implementation.notes
@@ -222,3 +222,9 @@ B if asked, and that the client fallback to the standard
 non-referral-based traversal is the only functional path here.
 
 But is that really the right thing?
+
+misc questions answered:
+=======================
+- should do_traversal code for old-style lookups still be requesting referrals?
+  If so, within what scope should they actually be used?
+  - probably not.  the old traversal code is network-intensive and resilient enough as is.