[Trust-router] Captured items from the side meeting

Sam Hartman <hartmans@painless-security.com> Mon, 25 March 2013 17:21 UTC

Return-Path: <hartmans@painless-security.com>
X-Original-To: trust-router@ietfa.amsl.com
Delivered-To: trust-router@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91DAB21F9020 for <trust-router@ietfa.amsl.com>; Mon, 25 Mar 2013 10:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPcj-Wia1-7p for <trust-router@ietfa.amsl.com>; Mon, 25 Mar 2013 10:21:02 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 078E521F901F for <trust-router@ietf.org>; Mon, 25 Mar 2013 10:21:02 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id DACD62016B for <trust-router@ietf.org>; Mon, 25 Mar 2013 13:20:09 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id ABF79447D; Mon, 25 Mar 2013 13:21:00 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: trust-router@ietf.org
Date: Mon, 25 Mar 2013 13:21:00 -0400
Message-ID: <tsl8v5be6pv.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Trust-router] Captured items from the side meeting
X-BeenThere: trust-router@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "ABFAB Trust Router discussion list." <trust-router.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trust-router>, <mailto:trust-router-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trust-router>
List-Post: <mailto:trust-router@ietf.org>
List-Help: <mailto:trust-router-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trust-router>, <mailto:trust-router-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2013 17:21:02 -0000

Hi.

I want to thank those who attended the side meeting and/or rtgarea
presentation at IETF 86.
I notice that we don't seem to have sent pointers to the bar bof slides
here.
I'll see if we can arrange for that soon.

I did want to capture a few items I heard at the side meeting and ask
for any items I missed.

1) Brian recommended that we keep the mapping layer (the routing
protocol) separate from the TID protocol so that another mapping
mechanism could potentially be substituted.
He drew an analogy between LISP and trust router.
In LISP, mapping between map servers and map resolvers is carried over a
BGP overlay in the default instantiation, but there are other proposals
for how mapping could be handled.

I certainly never noticed that similarity, and if Margaret did, she
never mentioned it to me. 
Thanks Brian for pointing that out; it's something to ponder.

2) Brian and Sandy both brought up the Byzantine failure question. I
hope I have provided an answer to that.


In particular, I'm wondering if any of Klaas or Hannes's questions
require updates or whether they made any suggestions for changes.

At the IETf meeting we also received a number of other use cases to
consider:

1) In the rtgarea meeting we were asked whether something like trust
router could key some of the KARP use cases; I think group keying.

2) We were advised to take a look at what's going on in CDNI and see if
their federated trust problem would be useful.

We're also aware from previous discussions that various AAA roaming
problems are similar to trust-router's problem statement outside the
specific ABFAB context.

--Sam