IETF Logo Mail Archive

Re: [Anima-bootstrap] Can the proxy add information during bootstrap?

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 13 April 2016 00:46 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2F312D9E8 for <anima-bootstrap@ietfa.amsl.com>; Tue, 12 Apr 2016 17:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mbz58ryoi56n for <anima-bootstrap@ietfa.amsl.com>; Tue, 12 Apr 2016 17:46:55 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0329512D9E1 for <anima-bootstrap@ietf.org>; Tue, 12 Apr 2016 17:46:55 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id e128so23507315pfe.3 for <anima-bootstrap@ietf.org>; Tue, 12 Apr 2016 17:46:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=wE4TxW+tbhl3w+EYzOFhJXqkJe9LbWHIKPx8WO819kI=; b=vMiBKt33OD3oDmxfyVp56brReR+a4npk36kMtNjm8QtGrCkwAlBqrmtgxcL383LlG0 VDpI+r9ZUgQ+U6xx+akxHHLJIK2w8nB3ZJTf06adzCxk32zL22+uEbev6YKEFGduIHsN CRNBu2MtvS9f4HgRMRofUQ696A7U2gAffZAtAUvghgW0E7mjv9jueJGpjUlfQNfOZmil 6dTCHn3y8CHLsnJJ3nN5vCU01aDEHH6apGw9JMZiUaN1J5dbCgx8MX4KAlQLmUmnxrSi rcKlOUIgH8chxvm0Nv75oP6XtiMWAMDxvey8ouESVRbl27zwRbkxDHdGZVwN5o+Y89ok 0zQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=wE4TxW+tbhl3w+EYzOFhJXqkJe9LbWHIKPx8WO819kI=; b=Yk2f1i8ksyFB4GLDV9PwaV5eOWmGIpfsKuIEAMqTzch+26w5sE9bwhS2h748QIpJY/ AYm8WzVzmRUlrfMJKnDH8QVBGtOZpNm/jdSaCtE+7cQ6/HOYE249RlMGl6to83z+Z2re eexBmI2YBPujjO2dOg0CX8pYIzdY4BQ2tQU8Gr6nXTCEW7hJ//nEeG360i3dO/3upvcc bbgEL2yxY2Sc9Kp1xNwRqM8hLLXCy2rrqg381PisIHEoX6NqBGXrpEFol9QXzqistbUb FawqEdsGUAa5dtphW7a1B8F9EFLuiiSEaZ1q3Nmf+YDaytbqAC+KxjTLmA8H5gKDhUcr pjCw==
X-Gm-Message-State: AOPr4FWuRCJ3URHiC0WRwzydIefN5O6H1P6dt1lu7EHA3ckdvTwZ2QrPREEkWQ2ASvWZgw==
X-Received: by 10.98.73.142 with SMTP id r14mr8878194pfi.140.1460508414547; Tue, 12 Apr 2016 17:46:54 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by smtp.gmail.com with ESMTPSA id l4sm46250031pfi.73.2016.04.12.17.46.51 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 17:46:52 -0700 (PDT)
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima-bootstrap@ietf.org" <anima-bootstrap@ietf.org>
References: <5c12b5d6940d4970bd3c0ad4c94b4696@XCH-RCD-006.cisco.com> <14252.1460506458@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <570D96FE.1000105@gmail.com>
Date: Wed, 13 Apr 2016 12:46:54 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <14252.1460506458@obiwan.sandelman.ca>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-bootstrap/8z6rOwaXxJxm8W1tNIPN1oBEJ34>
Subject: Re: [Anima-bootstrap] Can the proxy add information during bootstrap?
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: Wed, 13 Apr 2016 00:46:56 -0000

On 13/04/2016 12:14, Michael Richardson wrote:
> 
> Michael Behringer (mbehring) <mbehring@cisco.com> wrote:
>     > When a new device enrols, an operator will want to know WHERE this
>     > device is connecting. This includes the proxy identity, plus the
>     > interface on the proxy. (Potentially more)
> 
>     > The proxy identity can be figured out by looking at the source address
>     > of the incoming packets; but the interface information needs to be
>     > added explicitly, somehow.
> 
> Yes, source address of encapsulating packet, and since it's an ACP, and since
> the proxy negotiated via GRASP with the registrar, the registrar already
> knows everything.
> 
> I don't see the problem.
> 
>     > Can our enrolment process as described today support such proxy
>     > options? If not, I think we need to re-think...
> 
> I think it's a MITM attack for the proxy to add any information to the secure part.
> Any information not under the security enclosure may be untrustworthy.

If there's a need to discover topology, which I understood
Michael B was after, couldn't that be done after enrolment, with
no security risk?

   Brian

v2.23.0 | Report a Bug | By Email