[IETF-IDRM] Fwd: Re: [IDRM] draft-irtf-idrm-handle-system-00.txt

Thomas Hardjono thardjono@mediaone.net
Wed, 23 May 2001 14:32:44 -0400


>Date: Tue, 22 May 2001 23:05:59 -0700
>From: Mark Baugher <mbaugher@cisco.com>
>Subject: Re: [IDRM] draft-irtf-idrm-handle-system-00.txt
>X-Sender: mbaugher@mira-sjc5-6.cisco.com
>To: ietf-idrm@lists.elistx.com
>Cc: ssun@cnri.reston.va.us, llannom@cnri.reston.va.us
>X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
>List-Owner: <mailto:ietf-idrm-help@lists.elistx.com>
>List-Post: <mailto:ietf-idrm@lists.elistx.com>
>List-Subscribe: <mailto:ietf-idrm-request@lists.elistx.com?body=subscribe>
>List-Unsubscribe: <mailto:ietf-idrm-request@lists.elistx.com?body=unsubscribe>
>List-Archive: <http://lists.elistx.com/archives/ietf-idrm>
>List-Help: <http://lists.elistx.com/elists/admin_email.shtml>,
>  <mailto:ietf-idrm-request@lists.elistx.com?body=help>
>
>Oh, by the way, this note is commenting upon 
>draft-irtf-idrm-handle-system-00.txt and not 
>draft-irtf-idrm-handle-system-protocol-00.txt - I made a mistake in the 
>Subject line that I'll correct in subsequent responses.
>
>Mark
>At 10:26 PM 5/22/2001 -0700, Mark Baugher wrote:
>>I have a number of comments on this draft.  I also plan to post comments 
>>on the two other handle drafts, draft-irtf-idrm-handle-system-def-00.txt 
>>and draft-irtf-idrm-handle-system-protocol-00.txt.  I'll start with 
>>draft-irtf-idrm-handle-system-00.txt comments, a couple at a time since 
>>my other questions and comments may be resolved along the way.
>>
>>My first comment is that there does not seem to be name-resolution draft 
>>in the mix.  Is this not to be published?  I can see a lot of uses for a 
>>namespace that is not global, such as between a content provider 
>>(publisher) and service provider (distributor) that want to use the 
>>metadata facilities of handles to store rights information with the 
>>content work and to identify one or more "official repositories" for the 
>>content work.  If you're requiring a global namespace but not publishing 
>>the resolution mechanisms, then this seems to be an impediment to many 
>>business-to-business uses.
>>
>>Mark