IETF Logo Mail Archive

Re: [lmap] AD evaluation: draft-ietf-lmap-information-model-16

Alissa Cooper <alissa@cooperw.in> Tue, 24 January 2017 16:03 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B43F129A9B for <lmap@ietfa.amsl.com>; Tue, 24 Jan 2017 08:03:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=aBSDIl9n; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=FwqKijPJ
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 06TREi1ysOG8 for <lmap@ietfa.amsl.com>; Tue, 24 Jan 2017 08:03:13 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C348012961D for <lmap@ietf.org>; Tue, 24 Jan 2017 08:03:13 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 1D28020A63 for <lmap@ietf.org>; Tue, 24 Jan 2017 11:03:13 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 24 Jan 2017 11:03:13 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=NPP153WiS1Go9uw tmOLgxYpbZYM=; b=aBSDIl9nNK4xhWnOdbzF8HLI6NIbCklWCFrw93OAkc2oD8V GqCJVnH1Di/7chk+k93A2b2bCLY5Cz27MLPFAFnzvH6OoJu2p975dIGpRwnTZHql aZAt+GpaE8kdKpMN/Hd1w5+7C8doNXwN0WQe9d291xMSXCGYlxlwj53wMS3M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=NPP153WiS1Go9uwtmOLgxYpbZYM=; b=FwqKijPJgDby0+5CsV5q RUOYNlddF74qv4qj8LCZAFS9AKDpStosDJ0gj/e9mJvVOEJyXvyAi9AbK3DCOQJ3 kHQervzB+4WAsjkIdP/eRChMrKAgAZWIN7Cd0zwuIQkEdukDu/gak9m3+q1I/AWw 7z/ifHNEY7BIqHm58hq0HZQ=
X-ME-Sender: <xms:wXqHWAYCX1h4GBnup11zPehFR_Eb6PyZUqouBuNQhojB7kmu1QppOA>
X-Sasl-enc: L3Y6Xl8CmgsjJQlKz16PA//i7j/klgYmj2HTRsCIjLjc 1485273792
Received: from sjc-alcoop-8818.cisco.com (unknown [128.107.241.167]) by mail.messagingengine.com (Postfix) with ESMTPA id 8DBD024428 for <lmap@ietf.org>; Tue, 24 Jan 2017 11:03:12 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <2CB94EA6-A5F9-4770-9E76-0C7E8676E9CF@cooperw.in>
Date: Tue, 24 Jan 2017 11:03:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <22680E7F-38D2-46FE-8549-CBB783ECAF32@cooperw.in>
References: <2CB94EA6-A5F9-4770-9E76-0C7E8676E9CF@cooperw.in>
To: lmap@ietf.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/AQgGwHut7ohBBFroep_nYZyeu4M>
Subject: Re: [lmap] AD evaluation: draft-ietf-lmap-information-model-16
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Large Scale Measurement of Access network Performance <lmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lmap>, <mailto:lmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lmap/>
List-Post: <mailto:lmap@ietf.org>
List-Help: <mailto:lmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lmap>, <mailto:lmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jan 2017 16:03:15 -0000

> On Jan 23, 2017, at 2:22 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> (2) Are ma-preconfig-credentials and ma-config-credentials meant to be credentials only for the MA to be authenticated by a Controller or Collector? I assume that the credentials that allow the MA to authenticate other endpoints, and to protect communications to those endpoints, are stored in ma-channel-credentials, but it would help to clarify which set of credentials each of these fields is referring to.

Just to reinforce this, now that I’m doing a review of draft-ietf-lmap-yang: it seems that the model in draft-ietf-netconf-netconf-client-server defines both the client and server credentials. So if that is supposed to fulfill the channel credentials in the information model, what happens if the ma-config-credentials for the MA are different than the ones in the ma-channel-obj for the MA? Which ones is the MA supposed to use?

Thanks,
Alissa

v2.23.0 | Report a Bug | By Email