IETF Logo Mail Archive

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

Ladislav Lhotka <lhotka@nic.cz> Tue, 27 February 2018 08:38 UTC

Return-Path: <lhotka@nic.cz>
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 E6BB612702E for <netmod@ietfa.amsl.com>; Tue, 27 Feb 2018 00:38:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level:
X-Spam-Status: No, score=-7.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 JFdHS7xSr3aN for <netmod@ietfa.amsl.com>; Tue, 27 Feb 2018 00:38:50 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 DDDCB1200B9 for <netmod@ietf.org>; Tue, 27 Feb 2018 00:38:49 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:1f99:257b:62cc:c0d5]) by mail.nic.cz (Postfix) with ESMTPSA id 4B6D262686 for <netmod@ietf.org>; Tue, 27 Feb 2018 09:38:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1519720728; bh=Stkw1aE6vmZtmPr8j7uvLOOow/8FcYTiDxUMPB3MYSA=; h=From:To:Date; b=fkhdvw2Ecr1ZR64MEHTSDxqrKMf5up+IllRtb4bUmUNblTKlqONsAydjASy0kx6Wi 4DVvlR+KQAmaFB/rNSRx+vCBqusVeYt08zob5JSmtaYSwbKPsIsAXJoe+p2qwvhN+/ nF+elplU0ASK5iex6vMGQUCi0UwrjZXckLrDIXiE=
Message-ID: <1519720727.10739.1.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: netmod@ietf.org
Date: Tue, 27 Feb 2018 09:38:47 +0100
In-Reply-To: <20180227083116.xtlnju34s7ksjntc@elstar.local>
References: <87woz2a3x1.fsf@chopps.org> <596f5e0b-301e-e102-bcae-c3421b24455b@cisco.com> <87lgfg9ded.fsf@chopps.org> <20180226.160921.622063322182936097.mbj@tail-f.com> <20180227083116.xtlnju34s7ksjntc@elstar.local>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.5
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/O2h5vARQwIPYQWJiTu4GiEKkd1I>
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 08:38:52 -0000

On Tue, 2018-02-27 at 09:31 +0100, Juergen Schoenwaelder 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?

I would say so. It would be immediately usable for the inline case.

Lada

> 
> /js
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

v2.23.0 | Report a Bug | By Email