Re: AUP agenda item

William Manning <bmanning@is.rice.edu> Sat, 19 March 1994 23:40 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03886; 19 Mar 94 18:40 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03882; 19 Mar 94 18:40 EST
Received: from arizvm1.CCIT.Arizona.EDU by CNRI.Reston.VA.US id aa12144; 19 Mar 94 18:40 EST
Received: from ARIZVM1.CCIT.ARIZONA.EDU by ARIZVM1.ccit.arizona.edu (IBM VM SMTP V2R2) with BSMTP id 6731; Sat, 19 Mar 94 16:40:07 MST
Received: from ARIZVM1.CCIT.ARIZONA.EDU (NJE origin LISTSERV@ARIZVM1) by ARIZVM1.CCIT.ARIZONA.EDU (LMail V1.1d/1.7f) with BSMTP id 7348; Sat, 19 Mar 1994 16:39:55 -0700
Date: Sat, 19 Mar 1994 17:37:46 -0600
Reply-To: "IETF WG on internet school networking (ISN)" <ISN-WG%UNMVMA.BITNET@arizvm1.ccit.arizona.edu>
X-Orig-Sender: "IETF WG on internet school networking (ISN)" <ISN-WG%UNMVMA.BITNET@arizvm1.ccit.arizona.edu>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: William Manning <bmanning@is.rice.edu>
Subject: Re: AUP agenda item
X-To: ISN-WG%UNMVMA.BITNET@arizvm1.ccit.arizona.edu
To: Multiple recipients of list ISN-WG <ISN-WG%UNMVMA.BITNET@arizvm1.ccit.arizona.edu>
In-Reply-To: <9403192256.AA06928@moe.rice.edu> from "Tracy LaQuey Parker" at Mar 19, 94 02:53:25 pm
Message-ID: <9403191840.aa12144@CNRI.Reston.VA.US>

Tracy sez:

Lots of good things that I agree with and some that I don't. (still
good things though).

> You've done a lot of work...

Mostly writing down common sense.  Don't take too much thought.

> What should happen here is
> some of the school technology directors on this list who have had personal
> experience can customize what you've done or write another document
> based on what they think is important.  How's that?

Sounds good to me.  and now for More soapboxing.

I think that what Don & I wrote down will form the basis for any AUP.
It certainly is in every AUP I have seen.  There are AUP components that
we left out, in part because they are site specific.  Others were added
because they have applicability to most situations.

I think this draft has many of the hallmarks of the site security policy
rfc.  Individual situations are too varied to document specifics.  The
IETF make standards that are global in scope, and much of what I see
from this group is US-centric.

I guess in the end, it really does not matter what we publish or don't.
Organizations -WILL- create AUPs based on what they think is important.
What we have is the opportunity to show that the IETF recognizes this and
documents some common sense items that should be considered when an AUP
is created.  I do not intend for this to be a default AUP that people can
use.  It is a reference document to cite when they create thier own.

--
Regards,
Bill Manning