IETF Logo Mail Archive

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

<trevor.burbridge@bt.com> Wed, 25 January 2017 09:02 UTC

Return-Path: <trevor.burbridge@bt.com>
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 0425F12984C for <lmap@ietfa.amsl.com>; Wed, 25 Jan 2017 01:02:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.956
X-Spam-Level:
X-Spam-Status: No, score=-6.956 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.156, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] 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 kV9QYeblfJ0X for <lmap@ietfa.amsl.com>; Wed, 25 Jan 2017 01:02:18 -0800 (PST)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E582129893 for <lmap@ietf.org>; Wed, 25 Jan 2017 01:02:17 -0800 (PST)
Received: from E07HT05-UKBR.domain1.systemhost.net (193.113.197.167) by EVMED06-UKBR.bt.com (10.216.161.38) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 25 Jan 2017 09:02:13 +0000
Received: from rew09926dag03a.domain1.systemhost.net (10.55.202.18) by E07HT05-UKBR.domain1.systemhost.net (193.113.197.167) with Microsoft SMTP Server (TLS) id 8.3.342.0; Wed, 25 Jan 2017 09:02:15 +0000
Received: from rew09926dag03c.domain1.systemhost.net (10.55.202.26) by rew09926dag03a.domain1.systemhost.net (10.55.202.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 25 Jan 2017 09:02:11 +0000
Received: from rew09926dag03c.domain1.systemhost.net ([fe80::bd0c:3548:7105:cecb]) by rew09926dag03c.domain1.systemhost.net ([fe80::bd0c:3548:7105:cecb%12]) with mapi id 15.00.1210.000; Wed, 25 Jan 2017 09:02:12 +0000
From: <trevor.burbridge@bt.com>
To: <j.schoenwaelder@jacobs-university.de>, <philip.eardley@bt.com>
Thread-Topic: [lmap] AD evaluation: draft-ietf-lmap-information-model-16
Thread-Index: AQHSdoBcqRaIefyC2Ey00/mwC9xFFKFI5XUw
Date: Wed, 25 Jan 2017 09:02:11 +0000
Message-ID: <248d21f7ec4546b0af1fe98e604a4c8e@rew09926dag03c.domain1.systemhost.net>
References: <2CB94EA6-A5F9-4770-9E76-0C7E8676E9CF@cooperw.in> <22680E7F-38D2-46FE-8549-CBB783ECAF32@cooperw.in> <20170124202801.GB38068@elstar.local>
In-Reply-To: <20170124202801.GB38068@elstar.local>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.202.233]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/KTlDXaBBwyOM43w2eOY-gjXsYls>
Cc: 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
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:02:21 -0000

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>om>; 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/>

v2.8.7 | Report a Bug | By Email