[Anima-bootstrap] Does discovery include the domain?

"Michael Behringer (mbehring)" <mbehring@cisco.com> Tue, 08 November 2016 14:29 UTC

Return-Path: <mbehring@cisco.com>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E31C8129CB6 for <anima-bootstrap@ietfa.amsl.com>; Tue, 8 Nov 2016 06:29:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.018
X-Spam-Status: No, score=-16.018 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_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id TQdy48ZEE1Jy for <anima-bootstrap@ietfa.amsl.com>; Tue, 8 Nov 2016 06:29:44 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06724129CB1 for <anima-bootstrap@ietf.org>; Tue, 8 Nov 2016 06:29:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1774; q=dns/txt; s=iport; t=1478615383; x=1479824983; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=M9T+grlFcEOsfIphDJKPAPl6eweGc0w4CJjG2nOfkmk=; b=hKebdGMl/ykX2LUr5lWuTYKWEx7oh1CR+CWkHEr6l1QutiNnfut0oCB4 WI0LqQ/vYp/0QaPiFTHRGrIS1xcEyVfsAJErSrvtTWK8Z+Qohgx9Xgrwg UEuW6L8sDBh3BeN20obJarUaMg0P1jIoYIJX9kbi8CSeaw1U62JTCUDth s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.31,462,1473120000"; d="scan'208,223";a="166721467"
Received: from alln-core-8.cisco.com ([]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Nov 2016 14:29:43 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com []) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id uA8ETg4L017629 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 8 Nov 2016 14:29:42 GMT
Received: from xch-rcd-006.cisco.com ( by XCH-RCD-014.cisco.com ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 8 Nov 2016 08:29:41 -0600
Received: from xch-rcd-006.cisco.com ([]) by XCH-RCD-006.cisco.com ([]) with mapi id 15.00.1210.000; Tue, 8 Nov 2016 08:29:41 -0600
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "Max Pritikin (pritikin)" <pritikin@cisco.com>
Thread-Topic: Does discovery include the domain?
Thread-Index: AdI5yypSlVd772bWQKC9kqDiW9cJXQ==
Date: Tue, 08 Nov 2016 14:29:41 +0000
Message-ID: <cbfb55b18160431ba8e5ebae35146c1c@XCH-RCD-006.cisco.com>
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: <https://mailarchive.ietf.org/arch/msg/anima-bootstrap/Z_YeAiaGQ7YK9huU0D0Fjn2niYc>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "anima-bootstrap@ietf.org" <anima-bootstrap@ietf.org>
Subject: [Anima-bootstrap] Does discovery include the domain?
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <anima-bootstrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-bootstrap/>
List-Post: <mailto:anima-bootstrap@ietf.org>
List-Help: <mailto:anima-bootstrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2016 14:29:45 -0000

From "Re: [Anima-bootstrap] Detailed BRSKI review, part 1", Max' email from 20 Oct: 

> > In the reference model we state that if a pledge has been rejected by a
> domain, it should preferably use other domains that are seen. We may want
> to add something at the end of 3.1.1. This is also the reason why the pledge
> needs to know if the Registrar has rejected it based on MASA input.
> CONCERN: Discovery doesn’t include a secure statement of the domain
> identity. So this behavior would imply something like “if the TLS
> authentication results in a domain that has explicitely rejected the Pledge
> previously then the attempt immediately fails and no request is initiated” in
> section 5?

Not straightforward. Up to now the pledge only knows it's rejected, not why. So this goes back to the discussion about a feedback to the pledge, which, as MichaelR pointed out, is not easy. But I think we need to be clear about it. 

We agree that "discovery doesn't include a *secure* statement of the domain". But I seem to recall that some folks were in favour of not including the domain info at all, for privacy / security reasons?  Or should we include the domain info in the discovery announcements of the proxy? Did we have a conclusion on that?