add KRB5_TL_KADM5_E_DATA

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@8109 dc483132-0cff-0310-8789-dd5450dbe970

1 files changed, 16 insertions, 8 deletions

diff --git a/doc/kadm5/api-funcspec.tex b/doc/kadm5/api-funcspec.tex
index cfb06a37e..8e3074c19 100644
--- a/doc/kadm5/api-funcspec.tex
+++ b/doc/kadm5/api-funcspec.tex
@@ -323,14 +323,22 @@ typedef struct _krb5_tl_data {
     krb5_octet          * tl_data_contents;     
 } krb5_tl_data;
 \end{verbatim}
-The currently defined tagged data types are KRB5_TL_LAST_PWD_CHANGE,
-KRB5_TL_MOD_PRINC, and KRB5_TL_ADM_DATA, which store the last password
-modification time, time and modifier of last principal modification,
-and administration system data.  All of these entries are expected by
-the administration system and parsed out into fields of the
-kadm5_principal_ent_rec structure; they are also passed back in the
-tl_data list.  Any additional tagged data fields found in the database
-will also be provided, without interpretation.
+The libkdb library defines the tagged data types
+KRB5_TL_LAST_PWD_CHANGE, KRB5_TL_MOD_PRINC, and KRB5_TL_KADM_DATA,
+which store the last password modification time, time and modifier of
+last principal modification, and administration system data.  All of
+these entries are expected by the administration system and parsed out
+into fields of the kadm5_principal_ent_rec structure; they are also
+left in the tl_data list.
+
+The KADM5 API defines its own tagged data type, KRB5_TL_KADM5_E_DATA,
+which stores the contents of the e_data field of a krb5_db_entry.  The
+tagged data is only present if the database entry has extended data,
+and will only ever exist while KADM5 is implemented on top of the
+DB/DBM database mechansim.
+
+Any additional tagged data fields found in the database will also be
+provided, without interpretation.
 
 \item[key_data] An array of the principal's keys.  The keys contained
 in this array are encrypted in the Kerberos master key.  See section