Re: [i2rs] format for information models

Thomas Nadeau <tnadeau@juniper.net> Thu, 24 January 2013 19:15 UTC

Return-Path: <tnadeau@juniper.net>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53B5E21F87A3 for <i2rs@ietfa.amsl.com>; Thu, 24 Jan 2013 11:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.466
X-Spam-Level:
X-Spam-Status: No, score=-3.466 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WBjuddNr7X5S for <i2rs@ietfa.amsl.com>; Thu, 24 Jan 2013 11:15:13 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 3E6C421F8613 for <i2rs@ietf.org>; Thu, 24 Jan 2013 11:15:13 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUQGIPvJg2+NPtK6MqF+XDM/Y/l3EkCI3@postini.com; Thu, 24 Jan 2013 11:15:13 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 24 Jan 2013 11:12:47 -0800
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Thu, 24 Jan 2013 11:12:47 -0800
Received: from tx2outboundpool.messaging.microsoft.com (65.55.88.11) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 24 Jan 2013 11:15:10 -0800
Received: from mail86-tx2-R.bigfish.com (10.9.14.243) by TX2EHSOBE007.bigfish.com (10.9.40.27) with Microsoft SMTP Server id 14.1.225.23; Thu, 24 Jan 2013 19:12:40 +0000
Received: from mail86-tx2 (localhost [127.0.0.1]) by mail86-tx2-R.bigfish.com (Postfix) with ESMTP id D625F2E01BE for <i2rs@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 24 Jan 2013 19:12:39 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.197; KIP:(null); UIP:(null); (null); H:CH1PRD0511HT003.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -18
X-BigFish: PS-18(z426fnz98dI9371Ic85fh1804I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275ch1033IL17326ah8275dh18c673h8275bhz2dh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1155h)
Received: from mail86-tx2 (localhost.localdomain [127.0.0.1]) by mail86-tx2 (MessageSwitch) id 1359054756836873_2279; Thu, 24 Jan 2013 19:12:36 +0000 (UTC)
Received: from TX2EHSMHS028.bigfish.com (unknown [10.9.14.239]) by mail86-tx2.bigfish.com (Postfix) with ESMTP id BBD2C12007B; Thu, 24 Jan 2013 19:12:36 +0000 (UTC)
Received: from CH1PRD0511HT003.namprd05.prod.outlook.com (157.56.245.197) by TX2EHSMHS028.bigfish.com (10.9.99.128) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 24 Jan 2013 19:12:34 +0000
Received: from CH1PRD0511MB420.namprd05.prod.outlook.com ([169.254.9.167]) by CH1PRD0511HT003.namprd05.prod.outlook.com ([10.255.159.38]) with mapi id 14.16.0257.004; Thu, 24 Jan 2013 19:12:26 +0000
From: Thomas Nadeau <tnadeau@juniper.net>
To: Edward Crabbe <edc@google.com>
Thread-Topic: [i2rs] format for information models
Thread-Index: AQHN+bLV6Y3KBr0GQ0+aOQHBraurt5hYcZGAgAAy/gCAAAObAIAAA3aAgAAiH4D//63DAIAAXaUA//+tGgA=
Date: Thu, 24 Jan 2013 19:12:26 +0000
Message-ID: <F97700DB9B52414E8662360198681C8D22C64BE2@CH1PRD0511MB420.namprd05.prod.outlook.com>
In-Reply-To: <CACKN6JG-RkLVqj3hFq1fZC-nDO+-zph+Fpfs7kFz0wwP8rsxuw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [10.255.159.4]
Content-Type: multipart/alternative; boundary="_000_F97700DB9B52414E8662360198681C8D22C64BE2CH1PRD0511MB420_"
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%GOOGLE.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%JACOBS-UNIVERSITY.DE$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%OLDDOG.CO.UK$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: Adrian Farrel <adrian@olddog.co.uk>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "i2rs@ietf.org" <i2rs@ietf.org>, Alia Atlas <akatlas@gmail.com>
Subject: Re: [i2rs] format for information models
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i2rs>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 19:15:14 -0000

LoL!

From: Edward Crabbe <edc@google.com<mailto:edc@google.com>>
Date: Thursday, January 24, 2013 2:09 PM
To: Thomas Nadeau <tnadeau@juniper.net<mailto:tnadeau@juniper.net>>
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>>, Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>>, Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, "i2rs@ietf.org<mailto:i2rs@ietf.org>" <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Subject: Re: [i2rs] format for information models

I could not agree with your agreeing with me more.  ;)


On Thu, Jan 24, 2013 at 10:33 AM, Thomas Nadeau <tnadeau@juniper.net<mailto:tnadeau@juniper.net>> wrote:


From: Edward Crabbe <edc@google.com<mailto:edc@google.com>>
Date: Thursday, January 24, 2013 1:28 PM
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>>, Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>>, Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, "i2rs@ietf.org<mailto:i2rs@ietf.org>" <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Subject: Re: [i2rs] format for information models

+1 here.  If the relationships are hierarchical / acyclic then YANG would be a good choice /but/  we also have draft-amante-irs-topology-use-cases-0 on the table, and potentially some related documents incoming;  if these efforts move forward (ie: modelling inter layer relationships and the physical plant) we may want to look at other alternatives.

I think this is an interesting discussion to have; it's a bit premature to settle on a solution given the current uncertainty in the use case set, *but* it's almost never too early to start experimenting.

That is my (implied) point for supporting the Yang approach. Specifically, to me it is about picking an approach (that seems to have a lot of support) and just working with it until someone finds something better to use.   At this point we need to stop talking about which hammer to pick, and instead pick one and build something. Call it experimental or exploratory, but I would like us to start building some examples.  We can tear them down later, but its clear we won't get anywhere until we start somewhere.

--Tom


On Thu, Jan 24, 2013 at 8:26 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>> wrote:
On Thu, Jan 24, 2013 at 11:13:44AM -0500, Alia Atlas wrote:
> Juergen,
>
> What would you recommend for an information model for i2rs?
>

Frankly, I do not know. I am still unsure what the scope/complexity of
i2rs really is. To find out, I guess people just have to pick
something and get started. YANG tree diagrams are fine to get a quick
overview of YANG data models, they likely won't be the right tool if
many of data model items with more complex interrelationships are
involved - then you need additional diagrams.

/js

--
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587<tel:%2B49%20421%20200%203587>         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103<tel:%2B49%20421%20200%203103>         <http://www.jacobs-university.de/>
_______________________________________________
i2rs mailing list
i2rs@ietf.org<mailto:i2rs@ietf.org>
https://www.ietf.org/mailman/listinfo/i2rs


_______________________________________________
i2rs mailing list
i2rs@ietf.org<mailto:i2rs@ietf.org>
https://www.ietf.org/mailman/listinfo/i2rs