[I've cc'd this to web_ino_mgt as I suspect the info is of value to many]
Dear Miles,
Apologies for the delay in reply. E-mail comes in floods these days.
THIRD-PARTY USE OF JANET WITH SPECIFIC REFERENCE TO THE WWW e.g., banner-ads
----------------------------------------------------------------------------
A quick look at what you need to do when you have third-party content on
your web-server/ -site.
The JANET Acceptable Use Policy isn't a good starting point but the
document Sponsored and Proxy Connections to JANET is. In particular, the
following paragraph detail the main issue:
http://www.ja.net/documents/connections_v2.html#2.3
So, if a third-party (see
http://www.ja.net/documents/connections_v2.html#3.1 for definition) is to
host information (re: objects) on the web-server of a primary connection
'holder', then they must be considered as a PROXY CONNECTION.
Fine. What next?
http://www.ja.net/documents/connections_v2.html#5 provides the meat.
The bottom line is that each third-party must be licensed (and that means
registered). There are 500 licences provided with a primary connection - so
a DB is required to keep track of them.
>From conversations with UKERNA, this means that eveything from a site to a
graphical link (banner-ad?!) needs to be licensed as a PROXY.
And there we have it!
Best wishes,
Stephen...
_____________________________________________________
Stephen Emmott - Web Editor
http://www.kcl.ac.uk/
-----------------------------------------------------
Press & Public Relations Office,
rm 4.14, Waterloo Bridge House,
57 Waterloo Road, London SE1 8WA
-----------------------------------------------------
tel: +44 (0) 171 872 3342; fax: +44 (0) 171 872 0214
-----------------------------------------------------
.gamut - Web Editors' forum:
http://www.gold.ac.uk/gamut/
_____________________________________________________
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|