IETF Logo Mail Archive

Re: [YANG] keyref

"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 23 January 2008 05:10 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHXsD-0003jj-7r; Wed, 23 Jan 2008 00:10:05 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHXsC-0003gn-P6 for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 00:10:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHXsC-0003dk-BC for yang@ietf.org; Wed, 23 Jan 2008 00:10:04 -0500
Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHXsB-00029Y-Nm for yang@ietf.org; Wed, 23 Jan 2008 00:10:04 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=tQlR+Ypi/lmcbayRGIdtNeCQQ5n4P6ne2NYXW2zhzTCqAwzOuAdVOw/HEin7Xvva; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [69.3.145.174] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1JHXrk-00042o-VR for yang@ietf.org; Wed, 23 Jan 2008 00:09:47 -0500
Message-ID: <000801c85d7e$54217380$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <yang@ietf.org>
References: <200801230358.m0N3wsub017849@idle.juniper.net>
Subject: Re: [YANG] keyref
Date: Tue, 22 Jan 2008 21:10:26 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8885d2a9c731cc89117baac027a51f661b534a7cb208a9be2d5350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.3.145.174
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

Hi -

> From: "Phil Shafer" <phil@juniper.net>
> To: "Andy Bierman" <ietf@andybierman.com>
> Cc: <yang@ietf.org>
> Sent: Tuesday, January 22, 2008 7:58 PM
> Subject: Re: [YANG] keyref 
...
> >IMO, the whole issue of relationships between config database nodes is larger
> >than this keyref clause.  The requirements for machine readable
> >object constraint languages and object/entity relationships needs to
> >be documented in detail and agreed upon.
> 
> So you want this issue pushed onto the Requirements Team?  Or do
> you want a distinct requirements effort for this?
...

Would you consider ITU Recommendation X.725 to be a reasonable
starting point?  (Even if it is a dozen years old, and is based
on even older work...)

Randy




_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang

v2.8.7 | Report a Bug | By Email