Re: [Ideas] draft-padma-ideas-problem-statement and "Common Infrastructure"

Robert Moskowitz <rgm-ietf@htt-consult.com> Wed, 05 July 2017 14:16 UTC

Return-Path: <rgm-ietf@htt-consult.com>
X-Original-To: ideas@ietfa.amsl.com
Delivered-To: ideas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEC57129B37 for <ideas@ietfa.amsl.com>; Wed, 5 Jul 2017 07:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 n7S1qDAS1BvM for <ideas@ietfa.amsl.com>; Wed, 5 Jul 2017 07:16:18 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB225131609 for <ideas@ietf.org>; Wed, 5 Jul 2017 07:16:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id E4610620B9; Wed, 5 Jul 2017 10:16:16 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8eJLwYd0cSqV; Wed, 5 Jul 2017 10:16:09 -0400 (EDT)
Received: from lx120e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id CEEA862067; Wed, 5 Jul 2017 10:16:08 -0400 (EDT)
To: tjw ietf <tjw.ietf@gmail.com>
References: <9084360a-160e-944a-96aa-0b33379ccdb8@htt-consult.com> <CADyWQ+FK7AJA4vvKG9oT+EwRVJkGWU7iiw62jCpLykxJeqeuGg@mail.gmail.com>
Cc: ideas@ietf.org
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Message-ID: <1788bf20-2ee5-c2fd-0108-ff4b2b779848@htt-consult.com>
Date: Wed, 05 Jul 2017 10:16:06 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CADyWQ+FK7AJA4vvKG9oT+EwRVJkGWU7iiw62jCpLykxJeqeuGg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------C4FD8A562DF2B074A8DBEDC8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/qw4b-vZ3DOeBo4OF_0tRuZJMEfQ>
Subject: Re: [Ideas] draft-padma-ideas-problem-statement and "Common Infrastructure"
X-BeenThere: ideas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions relating to the development, clarification, and implementation of control-plane infrastructures and functionalities in ID enabled networks." <ideas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas>, <mailto:ideas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas/>
List-Post: <mailto:ideas@ietf.org>
List-Help: <mailto:ideas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas>, <mailto:ideas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 14:16:20 -0000

Tim,

Well it seems I got an upgrade to contributing to the problem 
statement.  I missed that in the last go around hours before the draft 
cutoff.  Thanks Padma.

I said 'requirements' to soften the blow, so to speak, about 'why NOT 
LDAP'.  Plus the data model to see if it can fit into an LDAP schema.

Of course we could always go with DAP instead for richer policy control 
and distributed data support!  (was it actually 20 years ago that I 
worked on this stuff? yikes!)

Bob

On 07/05/2017 10:05 AM, tjw ietf wrote:
> Bob!
>
> Brian and I had chatted briefly about charter direction and we wanted 
> to hear some of the discussions during the session. And that's what 
> they pay us the big bucks for!
>
> But I have to agree with your plan of attack.  If we could give some 
> guidance:
>
> - work on the problem statement and gap analysis but don't invest 
> larger cycles of time on them.
>
> - requirements are good to capture, but we will shy away from turning 
> them into published documents as they will change over time
>
> - some discussion on LDAP is very necessary as the code base has 
> gotten quite mature.
>
> tim
>
> On Wed, Jul 5, 2017 at 9:35 AM, Robert Moskowitz 
> <rgm-ietf@htt-consult.com <mailto:rgm-ietf@htt-consult.com>> wrote:
>
>     Disclaimer: I had a hand in edits to this version, though I am not
>     listed in the Ack section.  In particular I pushed for "Common
>     Infrastructure", not "Common Control Plane".
>
>
>     We have been talking a lot about Identity and Identifier and
>     metadata.  One of the tasks of this workgroup (and charter item)
>     needs to be data modeling of what is intended to be stored/available.
>
>     Further there needs to be Yet Another Gap Analysis (YAGA? :) ) on
>     why NOT LDAP or some other mature xyz data store access protocol. 
>     I start with LDAP as there is actually a fit, and the various
>     server implementations are very mature with good, secure, backends
>     and data replication tools.
>
>     It is time to start thinking charter.  The problem statement, gap
>     analysis, and use cases is barely a start. What the group is going
>     to DO is focus now.
>
>     So I propose two work items:
>
>     Common Infrastructure data modeling (and someone other than me can
>     do it in YANG).
>     Common Infrastructure protocol requirements with a subsection on
>     LDAP comparision.
>
>     Bob
>
>
>     _______________________________________________
>     Ideas mailing list
>     Ideas@ietf.org <mailto:Ideas@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ideas
>     <https://www.ietf.org/mailman/listinfo/ideas>
>
>
>
>
> _______________________________________________
> Ideas mailing list
> Ideas@ietf.org
> https://www.ietf.org/mailman/listinfo/ideas