Re: [perpass] Getting started...

Randy Bush <> Sat, 17 August 2013 10:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BDDE111E80DF for <>; Sat, 17 Aug 2013 03:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zlCGdxyCq6qt for <>; Sat, 17 Aug 2013 03:19:06 -0700 (PDT)
Received: from ( [IPv6:2001:418:8006::18]) by (Postfix) with ESMTP id 619CD21F9A25 for <>; Sat, 17 Aug 2013 03:19:03 -0700 (PDT)
Received: from localhost ([] by with esmtp (Exim 4.76) (envelope-from <>) id 1VAdb1-0000BO-Ab; Sat, 17 Aug 2013 10:18:59 +0000
Date: Sat, 17 Aug 2013 19:18:57 +0900
Message-ID: <>
From: Randy Bush <>
To: Stephen Farrell <>
In-Reply-To: <>
References: <> <> <>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Subject: Re: [perpass] Getting started...
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The perpass list is for discussion of the privacy properties of IETF protocols and concrete ways in which those could be improved. " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 17 Aug 2013 10:19:06 -0000

> I hope so. We had some good discussions in Berlin at any rate and my
> hope is that at least the people involved in that will chime in.  But
> I guess we'll see when we see.

ok, ok.

imiho, there are a vast number of areas we can improve.  as you point
out, a privacy version of jeff's danvers rfc is one start.  another is
just painting privacy by default on the walls at home.  

i know bgp payload does not excite a lot of folk, but encrypting it
makes ip space tracability just that much harder.  and opportunistic
encryption would be trivial to negotiate in the bgp open.  and i am
looking at bgpsec doing payload encryption.

i would love it if my email client ( well, normal email clients :-)
automagically encrypted to the recipients for whom i have a public key.
maybe the folk way up there at layer seven can come up with an even
better idea.

i could drivel on.  but there are a lot of folk far smarter at this
stuff than i.

oh, and can we try to take the constructive road, not the negative
games?  my .procmailrc is too long already.