IETF Logo Mail Archive

Re: [Anima] verification of manufacturer in BRSKI

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 23 February 2018 01:55 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B867126DD9 for <anima@ietfa.amsl.com>; Thu, 22 Feb 2018 17:55:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 idRZYCWW3DPk for <anima@ietfa.amsl.com>; Thu, 22 Feb 2018 17:55:08 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77D1E126BF6 for <anima@ietf.org>; Thu, 22 Feb 2018 17:55:08 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6EE8620091; Thu, 22 Feb 2018 21:02:33 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0F09C80706; Thu, 22 Feb 2018 20:55:06 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Anoop Kumar Pandey <anoop@cdac.in>
cc: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, anima@ietf.org
In-Reply-To: <003501d3aa07$a37f0560$ea7d1020$@cdac.in>
References: <003101d3a570$32e4c510$98ae4f30$@cdac.in> <22127.1519000017@obiwan.sandelman.ca> <005b01d3a95e$f0ba5680$d22f0380$@cdac.in> <18734556-d4a9-560f-724c-09287d4e0f20@gmail.com> <003501d3aa07$a37f0560$ea7d1020$@cdac.in>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Thu, 22 Feb 2018 20:55:05 -0500
Message-ID: <3963.1519350905@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ahEEFAv32PhQda2iADgnlQbi4os>
Subject: Re: [Anima] verification of manufacturer in BRSKI
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Feb 2018 01:55:10 -0000

Anoop Kumar Pandey <anoop@cdac.in> wrote:
    > Pledge verifying the
    > domain is anyway overrated.

So, I think you are saying that you do not subscribe to the problem statement.

    > Besides, it can also be done by verifying
    > the certificate of JRC during enrolment.

Please explain.
It would be great to simplify the protocol.

    > I would also like to quote/remind following lines from Section 1.3
    > [Scope of Solution] of the RFC:

    > “But this solution is not exclusive to the large, it is intended to
    > scale to thousands of devices located in hostile environments, such as
    > ISP provided CPE devices which are drop-shipped to the end user. The
    > situation where an order is fulfilled from distributed warehouse from
    > a common stock and shipped directly to the target location at the
    > request of the domain owner is explicitly supported. That stock
    > ("SKU") could be provided to a number of potential domain owners, and
    > the eventual domain owner will not know a-priori which device will go
    > to which location.”

Yes, it's designed exactly to deal with situation.
Are you saying that it fails in some way?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email