Re: Charter updates, changes, etc.

I think there is in fact a parallel between the notion of a virus-checking
service and the notion of doing rights-checking.

In the virus checking scenario, the callout server must either call
another entity that contains the virus-signatures, or itself be
loaded/updated with the virus-signatures.

In the case of rights-checking, the callout server must deal
with an entity (server) belonging to a rights-clearance house.
In other words, the content carries bits indicating that the content
contains copyrighted material.  The same bits (when scanned) triggers
the callout server in the same way (or every content item gets scanned).

It is very clear that the IETF is *not* the body that should deal
with *copyright interpretation*.  However, various technologies being
standardized in the IETF (eg. PKIX, XMLsig, Key management, AAA) are being
used or will be part of the larger DRM infrastructure.  Thus, in fact,
the IETF has a major role in defining technologies that allow
for both rights-enforcement and fair-use copying.

An interesting question:  when a person "publishes" a page on his/her
website, the usual lay understanding is that the page can be
"viewed" through a "viewer" (browser), but never copied.
In this simple scenario, would caches (eg. Akamai-type) violate
copyright of that person by keeping the page "too long" in
caches (be it memory or system harddisk).

thomas
------


At 3/28/01||11:32 AM, you wrote:
At 11:47 3/28/2001 -0700, Hilarie Orman wrote:
IETF discussions of copyright interpretation are usually ratholes,
let's try not to go there directly, but sort of glance along the
side with things like "pragma no opes" or "use explicit
opes service only" or "opes service must be signed
by provider domain" or other things.

I'd mostly agree with that; this is one of those interesting areas where you
can abuse the technology in some wonderful ways if you don't care about the
law.

I'm not so keen on the notion of the "pragma no opes" - I'd prefer explicit
prohibition of modification unless otherwise noted (though obviously there will
always be someone that'll break that rule anyway).  The implications of doing a
transformation are somewhat greater than of caching without authorization, and
I think we have to consider that in our design decisions.


------------------------------------------------------------------------
Thomas Hardjono       email1: thardjono(_at_)yahoo(_dot_)com
                      email2: hardjono(_at_)nortelnetworks(_dot_)com
                      Tel: +1-978-288-4538
------------------------------------------------------------------------

__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/?.refer=text