Re: We've got lift-off

Sally Hambridge <sallyh@LUDWIG.SC.INTEL.COM> Tue, 01 May 2001 18:28 UTC

Received: from mailbag.cps.intel.com ([192.102.199.72]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06804 for <run-archive@LISTS.IETF.ORG>; Tue, 1 May 2001 14:28:19 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72]) by mailbag.cps.intel.com (8.9.3/8.9.3/d: relay.m4,v 1.6 2000/11/24 22:10:56 iwep Exp iwep $) with ESMTP id KAA21485; Tue, 1 May 2001 10:59:34 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 5585 for IETF-RUN@MAILBAG.INTEL.COM; Tue, 1 May 2001 10:59:33 -0700
Received: from clio.sc.intel.com (scfdns01.sc.intel.com [143.183.152.25]) by mailbag.cps.intel.com (8.9.3/8.9.3/d: relay.m4,v 1.6 2000/11/24 22:10:56 iwep Exp iwep $) with ESMTP id KAA21481 for <ietf-run@mailbag.cps.intel.com>; Tue, 1 May 2001 10:59:33 -0700 (PDT)
Received: from Ludwig.sc.intel.com (ludwig.sc.intel.com [143.183.53.32]) by clio.sc.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.36 2001/04/18 16:16:02 root Exp $) with SMTP id RAA13715; Tue, 1 May 2001 17:57:21 GMT
Received: by Ludwig.sc.intel.com (4.1/SMI-4.1) id AA17205; Tue, 1 May 01 10:55:45 PDT
Message-ID: <10105011755.AA17205@Ludwig.sc.intel.com>
Date: Tue, 01 May 2001 10:55:45 -0700
Reply-To: IETF-RUN <IETF-RUN@mailbag.cps.INTEL.COM>
Sender: IETF-RUN <IETF-RUN@mailbag.cps.INTEL.COM>
From: Sally Hambridge <sallyh@LUDWIG.SC.INTEL.COM>
Subject: Re: We've got lift-off
Comments: To: tedgavin@newsguy.com
To: IETF-RUN@mailbag.cps.INTEL.COM

>
>
Ted - check with April on the process for revisions - and if
you want to add the confirmed opt-in stuff I think it would
make the doc better, but I think it would have to go through
the entire approval loop again

As for spamcon, I can't think of anything special....

Sally
>
Ted said:
>Speaking of RFC-3098, how does everyone feel about making a quick
>amendment and resubmitting? We've gotten some good feedback and
>suggestions that would indicate that perhaps something is missing. In
>the discussion, we neglected to include a mail-loop approval, which
>essentially prevents the activity of an opt-in request until the
>requestor actually does something (click on a link, reply to the
>message, etc...). This shifts the responsibility from the user (having
>to deal with unauthorized subscriptions) to the list owners (having to
>verify each address prior to inclusion). It's a MAPS-endorsed
>protection, and I think it warrants inclusion in some text from the
>IETF.
>
>I'd be happy to make the changes and present it to the group and up
>the chain for resubmission, but I'd like to see what Sally, April and
>the group have to say about it.
>
>On another note, I've been asked to speak at SPAMCON regarding this
>subject and Responsible Use, from the business perspective as well as
>the policy perspective. Anyone have any points they'd like to see
>included?
>
>Ted
>
>