[radext] #168: Remaining issues for dynamic-discovery draft

["radext issue tracker" <[e-mail]>]

#168: Remaining issues for dynamic-discovery draft

 This ticket captures the remaining comments on the ML that need to be
 worked on:

 1) NAIRealm certificate extension

 1.1 allocation of an OID is pending
 1.2 Comment by JS: "Are you sure you want NAIRealms to be IA5String and
 not UTF8String?  This is an I18N question."
 1.3 Comment by JS: "This text would appear to say that foo.*.bar is a
 legal wildcard NAI realm. Is that what you want?"

 2) Privacy (JS)

 "Should there be a potential privacy concern noted in this document
 surrounding the question of what information can leak based on the
 domain(s)
 being queried?  I am not sure that there is any usable information leaking
 here but this is not even close to my forte."

 3) subsequent lookup steps (JS)

 "In section 2.3.3 - May want to be a bit more detailed here about the
 subsequent lookup steps.  Presumably this is not starting with step 8 but
 I
 could be wrong.  I.e. do we take the set of result names and go back to
 step
 4 with new values of R?"

 These will be dealt with after -07 is out.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |      Owner:  draft-ietf-radext-
  [e-mail]           |  [e-mail]
     Type:  defect                   |     Status:  new
 Priority:  major                    |  Milestone:
Component:  dynamic-discovery        |    Version:  1.0
 Severity:  Active WG Document       |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/168>
radext <http://tools.ietf.org/radext/>