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

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 25 January 2017 09:18 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 B988D1298A4 for <lmap@ietfa.amsl.com>; Wed, 25 Jan 2017 01:18:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.399
X-Spam-Level:
X-Spam-Status: No, score=-7.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199] 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 IauCcw07H8L4 for <lmap@ietfa.amsl.com>; Wed, 25 Jan 2017 01:18:34 -0800 (PST)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04E8512989C for <lmap@ietf.org>; Wed, 25 Jan 2017 01:18:34 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id C86B378D; Wed, 25 Jan 2017 10:18:32 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.205]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id BuZH43Op94UN; Wed, 25 Jan 2017 10:18:30 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Wed, 25 Jan 2017 10:18:32 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 42874200AC; Wed, 25 Jan 2017 10:18:32 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id AELUtcFrZK9A; Wed, 25 Jan 2017 10:18:31 +0100 (CET)
Received: from elstar.jacobs.jacobs-university.de (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 93F46200AB; Wed, 25 Jan 2017 10:18:31 +0100 (CET)
Received: by elstar.jacobs.jacobs-university.de (Postfix, from userid 501) id 6F9C33E4AF9B; Wed, 25 Jan 2017 10:18:35 +0100 (CET)
Date: Wed, 25 Jan 2017 10:18:35 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: trevor.burbridge@bt.com
Message-ID: <20170125091835.GB40411@elstar.jacobs.jacobs-university.de>
Mail-Followup-To: trevor.burbridge@bt.com, philip.eardley@bt.com, alissa@cooperw.in, lmap@ietf.org
References: <2CB94EA6-A5F9-4770-9E76-0C7E8676E9CF@cooperw.in> <22680E7F-38D2-46FE-8549-CBB783ECAF32@cooperw.in> <20170124202801.GB38068@elstar.local> <248d21f7ec4546b0af1fe98e604a4c8e@rew09926dag03c.domain1.systemhost.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: 8bit
In-Reply-To: <248d21f7ec4546b0af1fe98e604a4c8e@rew09926dag03c.domain1.systemhost.net>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/mEJP-SyLWjIBP3ebtHdZ9biyS-k>
Cc: philip.eardley@bt.com, alissa@cooperw.in, lmap@ietf.org
Subject: Re: [lmap] AD evaluation: draft-ietf-lmap-information-model-16
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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: Wed, 25 Jan 2017 09:18:36 -0000

Trevor,

this is also the explanation I came up with but the document does not
really explain this. Alissa, would this resolve your comment if I try
to add text that tries to explain this distinction? Would it help to
add examples?

- SSH host keys are I think examples of MA credentials while SSH user
  authentication keys and authorization lists are channel
  credentials.

- X.509 certificates defining trust to X.509 root authorities are
  examples of MA credentials. while X.509 client ceritifcates for TLS
  communication are channel credentials.

(Lets see whether I got this right. ;-)

/js

On Wed, Jan 25, 2017 at 09:02:11AM +0000, trevor.burbridge@bt.com wrote:
> Initially the MA credentials were the private credentials of the MA and the channel credentials were the public credentials for each channel end-point.
> 
> Trevor.
> 
> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
> Sent: 24 January 2017 20:28
> To: Burbridge,T,Trevor,TUB8 R <trevor.burbridge@bt.com>; Eardley,PL,Philip,TUB8 R <philip.eardley@bt.com>
> Cc: lmap@ietf.org; Alissa Cooper <alissa@cooperw.in>
> Subject: Re: [lmap] AD evaluation: draft-ietf-lmap-information-model-16
> 
> Trevor and Phil,
> 
> do you recall the reason why we have channel credentials and MA global credentials? How are the MA global credentials supposed to be used?
> 
> /js
> 
> On Tue, Jan 24, 2017 at 11:03:11AM -0500, Alissa Cooper wrote:
> > 
> > > 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
> > _______________________________________________
> > lmap mailing list
> > lmap@ietf.org
> > https://www.ietf.org/mailman/listinfo/lmap
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>