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

Robert Moskowitz <rgm-ietf@htt-consult.com> Wed, 05 July 2017 13:36 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 190AE131D0A for <ideas@ietfa.amsl.com>; Wed, 5 Jul 2017 06:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 BysXQUky8tuI for <ideas@ietfa.amsl.com>; Wed, 5 Jul 2017 06:36:12 -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 5F4CB131D11 for <ideas@ietf.org>; Wed, 5 Jul 2017 06:36:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 6D4DE615D8 for <ideas@ietf.org>; Wed, 5 Jul 2017 09:36:10 -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 7p6TzvnpMRC0 for <ideas@ietf.org>; Wed, 5 Jul 2017 09:36:03 -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 A9EB16093E for <ideas@ietf.org>; Wed, 5 Jul 2017 09:36:03 -0400 (EDT)
To: ideas@ietf.org
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Message-ID: <9084360a-160e-944a-96aa-0b33379ccdb8@htt-consult.com>
Date: Wed, 05 Jul 2017 09:35:59 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/Qf2mMxOBEO7W4qCpuJIo2V_QDU4>
Subject: [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 13:36:15 -0000

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