Re: [mmox] Permissions

[Jesrad <[e-mail]>]

Very interesting point, thank you !

I figure we can have local caching with encrypted, timestamped copies,
and have the original grid/host only transmit the decryption key to
the intended endpoint. That way, we can have caching without unwanted
disclosure of the data to the caching middlemen.

On Mon, Feb 23, 2009 at 8:49 PM, Lawson English <[e-mail]> wrote:
> Jesrad wrote:
>>
>> This amounts to an implementation of some DRM, if I understand it
>> correctly. Would it be part of the protocol that grids are to
>> machine-read it and enforce it ? I would guess so if there is also a
>> section of the protocol addressing asset exchange. In this case the
>> problem is still more complex than anticipated (how do I restrict next
>> owner or next grid from restricting next owner or grid from
>> grid-exchanging the asset, etc.)
>>
>> Nevertheless, the entire issue is avoided by keeping content hosted in
>> its original grid, and the renderview being supplied by multiple
>> sources (according to the endpoint identity's credentials, if required
>> by the source grid implementation). Isn't it ?
>>
>
> Just how many separately hosted grids/asset servers are we talking about
> here?
>
> And how many assets?
>
>
> SL, sorry to keep bringing it up, but its an important usecase, has 20,000
> simulators and some
> ludicrous number of "assets" to deal with. If there's no local caching of
> assets on any other grid,
> permissions allowing, then the SL servers would be expected to be asset
> server to the metaverse
> and they already groan under the strain of talking to the limited SL world.
> The metaverse is
> projected to become 100-100x larger than Secondlife. the AWG's original
> mission was to try to
> desing a SL-like meta-grid that would handle such "scary numbers." We can't
> just handwave
> the issues away and suggest that existing systems and architectures will
> "just do it" in some way.
>
>
> Permissions/digital rights  of SOME kind is required for any asset that
> isn't identified as
> Creative Commons" and even there, a CC license can vary quite a bit. there's
> a ccREL
> (rights expression language) defined just to identify variations of the
> Creative Commons license,
> and CC is NOT enough to handle all the possible needs for digital rights.
>
>
> L
>