CVS gss/doc

[gss-commit]

Update of /home/cvs/gss/doc
In directory dopio:/tmp/cvs-serv10845

Modified Files:
        gss.texi 
Log Message:
Add.


--- /home/cvs/gss/doc/gss.texi  2004/11/19 13:27:26     1.68
+++ /home/cvs/gss/doc/gss.texi  2004/12/16 02:14:09     1.69
@@ -1544,7 +1544,6 @@
 @include texi/gss_oid_equal.texi
 @include texi/gss_copy_oid.texi
 @include texi/gss_duplicate_oid.texi
address@hidden texi/gss_release_oid.texi
 @include texi/gss_userok.texi
 
 @deftypefun {int} gss_encapsulate_token (gss_buffer_t @var{input_message}, 
gss_OID @var{token_oid}, gss_buffer_t @var{output_message})
@@ -1637,6 +1636,13 @@
 be allocated by the library, and deallocated (using the utility
 functions defined for this purpose) by the library.
 
+TBA: specification is unclear how memory for OIDs are managed.  For
+example, who is responsible for deallocate potentially newly allocated
+OIDs returned as @code{actual_mechs} in @code{gss_acquire_cred}?
+Further, are OIDs deeply copied into OID sets?  In other words, if I
+add an OID into an OID set, and modify the original OID, will the OID
+in the OID set be modified too?
+
 Another illustrating example is the sample GSS header file given in
 the RFC, which contains: