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

Dean Willis <dean.willis@softarmor.com> Fri, 18 March 2011 18:00 UTC

Return-Path: <dean.willis@softarmor.com>
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 0AC623A69DB for <obscurity-interest@core3.amsl.com>; Fri, 18 Mar 2011 11:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 FEXRg92GXaem for <obscurity-interest@core3.amsl.com>; Fri, 18 Mar 2011 11:00:37 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id EDC6C3A69DA for <obscurity-interest@ietf.org>; Fri, 18 Mar 2011 11:00:36 -0700 (PDT)
Received: by iyi12 with SMTP id 12so4943002iyi.31 for <obscurity-interest@ietf.org>; Fri, 18 Mar 2011 11:02:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.74.71 with SMTP id v7mr431318icj.232.1300471326408; Fri, 18 Mar 2011 11:02:06 -0700 (PDT)
Received: by 10.42.80.7 with HTTP; Fri, 18 Mar 2011 11:02:06 -0700 (PDT)
Received: by 10.42.80.7 with HTTP; Fri, 18 Mar 2011 11:02:06 -0700 (PDT)
In-Reply-To: <4D839063.70302@abenaki.wabanaki.net>
References: <CD18C9C4-C1A3-4D3E-B734-5DC9844FC914@softarmor.com> <4D839063.70302@abenaki.wabanaki.net>
Date: Fri, 18 Mar 2011 13:02:06 -0500
Message-ID: <AANLkTim_EmFWszP0qN7R11Y2kjYqADui1BYm-v=EDekZ@mail.gmail.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
Content-Type: multipart/alternative; boundary="90e6ba3fd24d7380f3049ec593ce"
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:00:38 -0000

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>
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
> 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
> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>
>
_______________________________________________
obscurity-interest mailing list
obscurity-interest@ietf.org
https://www.ietf.org/mailman/listinfo/obscurity-interest