Re: [Anima-bootstrap] BRSKI State Machine

"Michael Behringer (mbehring)" <> Tue, 08 November 2016 10:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E056512962B for <>; Tue, 8 Nov 2016 02:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -16.019
X-Spam-Status: No, score=-16.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6uXXRkMnZOxe for <>; Tue, 8 Nov 2016 02:53:04 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AB2DB129504 for <>; Tue, 8 Nov 2016 02:53:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2912; q=dns/txt; s=iport; t=1478602384; x=1479811984; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=oUZ6Vm0qIrZqpGxn3vEomuDeYK2WasmBuzuftkoqvFM=; b=TWEqBsHKnaE4EtTZFmGgYL4OrlcF2J/Yvtf22pjVtxHGCD7dYtR7rLJL uXuvCigtzW/XYvbO9tWh1V35H8lixEDXUjTRCj41J6kT4I8Bf8s6KjO0M 1wVGNwKbWu5AcJgys3L26BQWBF9E6hYhdrfX+ESL6dYjRkOHcUto7hiNV w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.31,609,1473120000"; d="scan'208";a="345855489"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Nov 2016 10:53:03 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id uA8Ar3rN014467 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 8 Nov 2016 10:53:03 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 8 Nov 2016 04:53:03 -0600
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Tue, 8 Nov 2016 04:53:02 -0600
From: "Michael Behringer (mbehring)" <>
To: Michael Richardson <>, "Max Pritikin (pritikin)" <>
Thread-Topic: [Anima-bootstrap] BRSKI State Machine
Thread-Index: AdImIxW8sCw9I7ieQW++wlMDDTidqAC0b9kAAIa8w4ADpwZZYA==
Date: Tue, 08 Nov 2016 10:53:02 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>
Subject: Re: [Anima-bootstrap] BRSKI State Machine
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 08 Nov 2016 10:53:10 -0000

>     MB> But, we'll need the same method also for the ACP draft: When both
>     MB> nodes have a certificate, they need to discover each other as well.
>     MB> I've been haggling with Toerless about this :-)   I think we should
>     MB> take the mDNS insecure discovery into a separate, new draft.
>     > I don’t follow. mDNS simply *is* insecure. This is important since we
>     > can’t establish a secure discovery yet.

MichaelR, I don't understand your logic below. 
> mDNS is just fine to find *a* proxy for a pledge that doesn't know anything
> else.
> (And couldn't verify the proxy anyway).
> I'm still unclear how the GRASP multicast discovery process is going to work
> (the details) such that it leads to an IKEv2 connection.  *All* we need to form
> the ACP links is a multicast that says, "I speak ACP"

Exactly. I think mDNS *could* be used to give exactly that information. 

> , and as I suggested
> before, this could be an multicast IKEv2 PARENT_I1 as much as
> anything else.   Or we use the GRASP discovery multicast port, and the
> response is not a TCP connection that says, "I'm here", as much as just an
> IKEv2 packet instead.

That is an alternative, valid method. But I don't see why you couldn't use mDNS to find all ACP capable nodes? 

To me it still seems most logical to have a standalone method to do ANIMA discovery, and use the result of the discovery in various ways. Today: 
- message "I'm a proxy" --> launch bootstap as a pledge (If local node not in a domain)
- message "I'm an ACP capable device" --> establish the ACP (authenticating that device, of course)

And in the future, we may well have other things to discover: 
- message "I'm a device from domain X" --> start a security association and negotiate cross domain 
   features, such as BGP parameters. 
- message "I'm a constrained device - use method x to talk to me". 

We could do different methods for all of those; I still think it would be nice to have a simple, universal way to discover adjacent nodes in the ANIMA context. Where am I going wrong?