IETF Logo Mail Archive

Re: to/cc/bcc extension

John Panzer <jpanzer@acm.org> Sat, 16 October 2010 21:57 UTC

Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79B073A6ADF for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 16 Oct 2010 14:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.045
X-Spam-Level:
X-Spam-Status: No, score=-102.045 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4Wo-eEqPVZ1 for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 16 Oct 2010 14:57:51 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 759263A6B0D for <atompub-archive@ietf.org>; Sat, 16 Oct 2010 14:57:51 -0700 (PDT)
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9GLrDIG022772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Oct 2010 14:53:13 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9GLrDFf022771; Sat, 16 Oct 2010 14:53:13 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mail-pv0-f171.google.com (mail-pv0-f171.google.com [74.125.83.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9GLrCnW022766 for <atom-syntax@imc.org>; Sat, 16 Oct 2010 14:53:12 -0700 (MST) (envelope-from john@johnpanzer.com)
Received: by pvc22 with SMTP id 22so425391pvc.16 for <atom-syntax@imc.org>; Sat, 16 Oct 2010 14:53:11 -0700 (PDT)
Received: by 10.142.166.16 with SMTP id o16mr218499wfe.231.1287265990564; Sat, 16 Oct 2010 14:53:10 -0700 (PDT)
Received: from [192.168.1.100] ([70.132.7.70]) by mx.google.com with ESMTPS id w42sm10269117wfh.3.2010.10.16.14.53.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 16 Oct 2010 14:53:09 -0700 (PDT)
Message-ID: <4CBA1ED3.4040208@acm.org>
Date: Sat, 16 Oct 2010 14:53:23 -0700
From: John Panzer <jpanzer@acm.org>
Reply-To: jpanzer@acm.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: James Snell <jasnell@gmail.com>
CC: Atom-Syntax <atom-syntax@imc.org>
Subject: Re: to/cc/bcc extension
References: <AANLkTi=P5k0LpVxB-Q4HqeM+zZsHfoXrDuEbGZxX7PSU@mail.gmail.com>
In-Reply-To: <AANLkTi=P5k0LpVxB-Q4HqeM+zZsHfoXrDuEbGZxX7PSU@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070306080909030403080705"
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

  I like  the concept and this may be a reasonable implementation.  
There's related work done on this for OStatus and Salmon which might be 
worth looking at.

My big question though is what the semantics of this are supposed to be; 
the names are suggestive of email, clearly intentionally, but the spec 
doesn't state this.  Are there suggested semantics?  Or is intended to 
inherit semantics from email (which inherited from business snail mail...)?

(Also, bcc is untenable for use with signed content.)

On 10/15/2010 2:02 PM, James Snell wrote:
> Wanted to draw attention to this:
>
> http://tools.ietf.org/html/draft-norris-atompub-audience-00.html
>
> It introduces to/cc/bcc elements to an Atom entry.
>
> <entry>
>     ...
> <to>acct:john.doe@example.org <mailto:acct%3Ajohn.doe@example.org></to>
> <to>acct:bob@example.org <mailto:acct%3Abob@example.org></to>
> <cc>acct:jane.doe@example.org <mailto:acct%3Ajane.doe@example.org></cc>
> <cc>acct:jane@example.org <mailto:acct%3Ajane@example.org></cc>
> <bcc>acct:jean.deux@example.org 
> <mailto:acct%3Ajean.deux@example.org></bcc>
> <bcc>acct:max@example.org <mailto:acct%3Amax@example.org></bcc>
>     ...
> </entry>
>
> Comments are welcomed and requested.
>
> - James

v2.8.7 | Report a Bug | By Email