Re: [obscurity-interest] Prague face-to-face scheduling

Eric Brunner-Williams <ebw@abenaki.wabanaki.net> Fri, 18 March 2011 18:12 UTC

Return-Path: <ebw@abenaki.wabanaki.net>
X-Original-To: obscurity-interest@core3.amsl.com
Delivered-To: obscurity-interest@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D98D3A69D0 for <obscurity-interest@core3.amsl.com>; Fri, 18 Mar 2011 11:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Level:
X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599]
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 ojm0TWp1Q-zk for <obscurity-interest@core3.amsl.com>; Fri, 18 Mar 2011 11:12:25 -0700 (PDT)
Received: from abenaki.wabanaki.net (abenaki.wabanaki.net [65.99.1.133]) by core3.amsl.com (Postfix) with ESMTP id 1A2F73A69B2 for <obscurity-interest@ietf.org>; Fri, 18 Mar 2011 11:12:24 -0700 (PDT)
Received: from limpet.local (cpe-67-255-5-237.twcny.res.rr.com [67.255.5.237]) by abenaki.wabanaki.net (8.14.4/8.14.4) with ESMTP id p2IGM2FE021793; Fri, 18 Mar 2011 12:22:02 -0400 (EDT) (envelope-from ebw@abenaki.wabanaki.net)
Message-ID: <4D83A0DC.80708@abenaki.wabanaki.net>
Date: Fri, 18 Mar 2011 14:13:48 -0400
From: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
Organization: wampumpeag
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <CD18C9C4-C1A3-4D3E-B734-5DC9844FC914@softarmor.com> <4D839063.70302@abenaki.wabanaki.net> <AANLkTim_EmFWszP0qN7R11Y2kjYqADui1BYm-v=EDekZ@mail.gmail.com>
In-Reply-To: <AANLkTim_EmFWszP0qN7R11Y2kjYqADui1BYm-v=EDekZ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: obscurity-interest@ietf.org
Subject: Re: [obscurity-interest] Prague face-to-face scheduling
X-BeenThere: obscurity-interest@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion of communications obscurity and real-time communications." <obscurity-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/obscurity-interest>, <mailto:obscurity-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/obscurity-interest>
List-Post: <mailto:obscurity-interest@ietf.org>
List-Help: <mailto:obscurity-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/obscurity-interest>, <mailto:obscurity-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2011 18:12:26 -0000

As an alternative to continued guessing, perhaps you could share the 
particular definition(s) you have in mind.

On 3/18/11 2:02 PM, Dean Willis wrote:
> I confess I did not have that particular definition in mind, but it
> certainly represents an interesting use case.
>
>> On Mar 18, 2011 12:03 PM, "Eric Brunner-Williams"
>> <ebw@abenaki.wabanaki.net <mailto:ebw@abenaki.wabanaki.net>> wrote:
>>
>> I'm assuming that the phrase "counter-communication" refers to
>> interaction at an institutional "counter", and sensitive data is
>> communicated, e.g., personally identifying information and
>> pharmaceutical prescriptions or banking identifiers, etc.
>>
>> Is this a correct assumption?
>>
>> Thanks in advance,
>> Eric
>>
>> On 3/16/11 9:04 PM, IETF Secretariat wrote:
>>
>>     A new IETF non-working group email list has been created.
>>
>>     List address: obscurity-interest@ietf.org
>>     <mailto:obscurity-interest@ietf.org>
>>     Archive: http://www.ietf.org/mail-archive/web/obscurity-interest/
>>     To subscribe:
>>     https://www.ietf.org/mailman/listinfo/obscurity-interest
>>
>>     Description:  This list is for discussion of the requirements and
>>     technology for enabling communications, especially near or
>>     real-time,
>>     between persons subject to high levels of counter-communication
>>     interception. The requirements are believed to relate to
>>     privacy, data
>>     integrity, unlinkability, and the general intercept (lawful or
>>     otherwise)
>>     problem, which is broader than the "privacy" problem considered
>>     by IETF.
>>     This list intended to focus on practical requirement and
>>     actionable work
>>     rather than general theory. Discussion may lead to new protocol
>>     action,
>>     enhanced guidance for "security considerations" sections in IETF
>>     specifications, and further research inside or outside of the IETF.
>>
>>     For additional information, please contact the list administrators.
>>     _______________________________________________
>>     IETF-Announce mailing list
>>     IETF-Announce@ietf.org <mailto:IETF-Announce@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/ietf-announce
>>
>>
>>
>> _______________________________________________
>> obscurity-interest mailing list
>> obscurity-interest@ietf.org <mailto:obscurity-interest@ietf.org>
>> https://www.ietf.org/mailman/listinfo/obscurity-interest
>