Re: [netmod] Proposal for minimalist full NMDA support in schema mount

Martin Bjorklund <mbj@tail-f.com> Tue, 27 February 2018 09:15 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 265F4127333 for <netmod@ietfa.amsl.com>; Tue, 27 Feb 2018 01:15:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 6x2aeSJtXD7Z for <netmod@ietfa.amsl.com>; Tue, 27 Feb 2018 01:15:41 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id EA2D412702E for <netmod@ietf.org>; Tue, 27 Feb 2018 01:15:40 -0800 (PST)
Received: from localhost (h-80-27.A165.priv.bahnhof.se [212.85.80.27]) by mail.tail-f.com (Postfix) with ESMTPSA id B50CA1AE02C9; Tue, 27 Feb 2018 10:15:38 +0100 (CET)
Date: Tue, 27 Feb 2018 10:15:38 +0100 (CET)
Message-Id: <20180227.101538.284842947165973615.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: chopps@chopps.org, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20180227083116.xtlnju34s7ksjntc@elstar.local>
References: <87lgfg9ded.fsf@chopps.org> <20180226.160921.622063322182936097.mbj@tail-f.com> <20180227083116.xtlnju34s7ksjntc@elstar.local>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pBphpz7tmSPxYnITpQrn64KAUxU>
Subject: Re: [netmod] Proposal for minimalist full NMDA support in schema mount
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Feb 2018 09:15:42 -0000

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> On Mon, Feb 26, 2018 at 04:09:21PM +0100, Martin Bjorklund wrote:
> > Hi,
> > 
> > Christian Hopps <chopps@chopps.org> wrote:
> > > 
> > > Hi Rob,
> > > 
> > > You do realize that no-one trying to actually deploy and run networks
> > > cares about live-discovery of different schema per datastore for the
> > > same mount point right? Like 99.999% of the clients know where things
> > > are supposed to reside and expect them to be there.
> > 
> > But then why advertise anything at all?   We can do a *much* simpler
> > solution by just having the mountpoint extension, and nothing else.
> > Clients will know what to find anyway.
> >
> 
> So it this a possible way out of the current situation? We publish a
> trimmed down document that just defines the mount point extension and
> we do an update of this document that adds all the details needed to
> obtain the schema information?

Not optimal, but I can accept this as a way to move forward.


/martin