Re: [i2rs] IETF 91 meeting requested - call for agenda; status reports?

"Acee Lindem (acee)" <acee@cisco.com> Sat, 27 September 2014 23:37 UTC

Return-Path: <acee@cisco.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 634241A006A for <i2rs@ietfa.amsl.com>; Sat, 27 Sep 2014 16:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.286
X-Spam-Level:
X-Spam-Status: No, score=-15.286 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 7yG13xG0UuUo for <i2rs@ietfa.amsl.com>; Sat, 27 Sep 2014 16:37:24 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C00A1A0069 for <i2rs@ietf.org>; Sat, 27 Sep 2014 16:37:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=45074; q=dns/txt; s=iport; t=1411861045; x=1413070645; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=eOQRb6rOIFlmngt5Rio+nifwiM8pahO7O1rpZClA0wM=; b=WcW6YWAbqeiqKblzgtGUXIuOHJfPtCsj3nqLaEJWiU7hnGqjxckUuX/R JG+X9ZXPhgZCfIzY+MxM02sQimFcZQb9OG5+NG4QJSZm4bObTRC/WA5gm IiAuYvsFeu/r9230P0HiSZDfiPHumSPlfmFsa2iCA5INEqHT7gnXMxjay w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFADZJJ1StJV2S/2dsb2JhbABggkhGU1cEyFgBCYdOAnsWAXuEAwEBAQIBAQEBARoQQQsFBwQCAQgOAwMBAQEhAQYHJwsUCQgCBAENBQmILQgNvigBF4xLgnEQAgEtEQ0EBgEGhEUFkWWEOocJlV2DY2wBgUeBAgEBAQ
X-IronPort-AV: E=Sophos; i="5.04,611,1406592000"; d="scan'208,217"; a="81931045"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-3.cisco.com with ESMTP; 27 Sep 2014 23:37:24 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s8RNbMlR019294 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 27 Sep 2014 23:37:23 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Sat, 27 Sep 2014 18:37:22 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Susan Hares <shares@ndzh.com>, 'Jeffrey Haas' <jhaas@pfrc.org>
Thread-Topic: [i2rs] IETF 91 meeting requested - call for agenda; status reports?
Thread-Index: AQHP2OquSp4i883k10igxhKi8uSjxpwSg0UAgAInDICAAM9KAIAATJgA///GhwCAAFalgP//wVqAgABRF4D//8ETAA==
Date: Sat, 27 Sep 2014 23:37:22 +0000
Message-ID: <D04CC017.3B94%acee@cisco.com>
References: <20140925180055.GB1239@pfrc> <3C001E8E-FB91-4E31-9258-9E376F46AD8E@juniper.net> <00b501cfda04$2b4db130$81e91390$@ndzh.com> <D04C8E0F.3B4F%acee@cisco.com> <003201cfda92$1c49c230$54dd4690$@ndzh.com> <D04C9D5E.3B5B%acee@cisco.com> <005401cfdaa0$b297d070$17c77150$@ndzh.com> <D04CB1B4.3B84%acee@cisco.com> <000c01cfdaa9$eab7b570$c0272050$@ndzh.com>
In-Reply-To: <000c01cfdaa9$eab7b570$c0272050$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.152.196]
Content-Type: multipart/alternative; boundary="_000_D04CC0173B94aceeciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/q_UmWtzlU28IP_Waz1q5tdBsMVo
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
Subject: Re: [i2rs] IETF 91 meeting requested - call for agenda; status reports?
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 27 Sep 2014 23:37:28 -0000


From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Saturday, September 27, 2014 at 7:22 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Jeff Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>
Cc: "i2rs@ietf.org<mailto:i2rs@ietf.org>" <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Subject: RE: [i2rs] IETF 91 meeting requested - call for agenda; status reports?

Acee:

Thank you for the pointer to the message in ISIS.  Perhaps since Chris just declared consensus Friday the 9/19/14 that he will get around to posting these drafts.

I’m not sure why you are suggesting that these drafts have not been previously posted.

https://datatracker.ietf.org/doc/draft-litkowski-isis-yang-isis-cfg/
https://datatracker.ietf.org/doc/draft-yeung-netmod-ospf/




To be clear, I understand from your work that you are declaring consensus on the yang models for OSPF model based on your knowledge of the private multi-vendor design team.

As you noted, both the presentations at IETF 90 called for participation. These design teams are much less private than the OSPF/ISIS IM/DM drafts you submitted yesterday.

You are stating at the OSPF chair that those models have the front seat in looking at the I2RS models without reading any of the I2RS IM/DM drafts we have prepared.

The work on the OSPF and ISIS YANG models pre-dated the drafts you have submitted yesterday by quite some time so I don’t see we should consider replacing it.

 Please confirm that I understand this message so that I can determine the next steps to take with these drafts.

Your next step should be to review the OSPF/ISIS drafts.

Thanks,A
Acee




Sue

From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Saturday, September 27, 2014 6:32 PM
To: Susan Hares; 'Jeffrey Haas'
Cc: i2rs@ietf.org<mailto:i2rs@ietf.org>
Subject: Re: [i2rs] IETF 91 meeting requested - call for agenda; status reports


From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Saturday, September 27, 2014 at 6:16 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Jeff Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>
Cc: "i2rs@ietf.org<mailto:i2rs@ietf.org>" <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Subject: RE: [i2rs] IETF 91 meeting requested - call for agenda; status reports?

Acee:

I’m confused by this email thread because these slides state the authors are looking for co-authors for netmod drafts. Are you as the co-chair of OSPF declaring consensus on the OSPF yang model draft?

Yes – and there are now multi-vendor design teams in place.


Would you point me to the email that indicates the WG Adoption call and conclusion?

We haven’t adopted yet in OSPF. ISIS adoption is in progress. I already searched the proceedings for the presentations. Note that the list archives offer a search capability… Anyway, here is the ISIS message:

http://www.ietf.org/mail-archive/web/isis-wg/current/msg03679.html



The drafts I suggested are I2RS drafts for the I2RS datastore that allow it to configure the routing agent directly. The only way these two drafts interact is if the option 4 proposed by the Yang 1.1 interim (created 9/19/14) works.  It is unclear if it will work – that’s under discussion. There is no reason to stop the I2RS DM/IM models required by I2RS charter work while we find out if option 4 works.

And out of curiosity, if we are now considering option 4 why don’t you want more input and collaboration that provides insight from people who looked at the OSPF for the I2RS use that option 4 suggests?  We have complete IM and DM (yang compiled) for the configuration we thought was necessary for I2RS if the agent talked directly to the routing process (the assumption of all I2RS with unique data store).

Please review the OSPF and ISIS drafts with respect to option 4.

Thanks,
Acee





Sue

PS – the ISIS Draft is not listed as approved or listed on the ISIS mail list as approved. It has not been updated since 6/27/14.  If you believe it should be listed that way, you might want to talk to the ISIS co-chairs.

From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Saturday, September 27, 2014 5:06 PM
To: Susan Hares; 'Jeffrey Haas'
Cc: i2rs@ietf.org<mailto:i2rs@ietf.org>
Subject: Re: [i2rs] IETF 91 meeting requested - call for agenda; status reports?

Sue:

Did you look at the archives for the OSPF and ISIS WGs? Both drafts were presented at IETF 90 in Toronto. We intend to cross review the OSPF YANG model in both the netmod and OSPF WGs. The ISIS YANG Model is already being accepted as an ISIS WG document.

http://www.ietf.org/proceedings/90/slides/slides-90-isis-0.pdf
http://www.ietf.org/proceedings/90/slides/slides-90-ospf-8.pdf

Acee

From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Saturday, September 27, 2014 at 4:32 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Jeff Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>
Cc: "i2rs@ietf.org<mailto:i2rs@ietf.org>" <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Subject: RE: [i2rs] IETF 91 meeting requested - call for agenda; status reports?

Acee:

Was this work announced on any list at IETF for general contribution?  I don’t see an announcement on the ospf list or the ISIS list?  Perhaps you could point me to the list where this was announced?

Sue


From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Saturday, September 27, 2014 3:58 PM
To: Susan Hares; 'Jeffrey Haas'
Cc: i2rs@ietf.org<mailto:i2rs@ietf.org>
Subject: Re: [i2rs] IETF 91 meeting requested - call for agenda; status reports?



From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Friday, September 26, 2014 at 11:36 PM
To: Jeff Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>
Cc: "i2rs@ietf.org<mailto:i2rs@ietf.org>" <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Subject: Re: [i2rs] IETF 91 meeting requested - call for agenda; status reports?


Jeff:



Please add to the agenda the following drafts: I2RS yang Data and Information models for ISIS, OSPF, Basic Network Policy (BNP), PBR and BGP.  PBR and BGP will be uploaded next week after some internal review.

HI Sue,
We are currently have drafts for the OSPF and ISIS YANG models and have multi-vendor design teams contributing to them. This works is being done in the OSPF and ISIS WG groups. You are welcome to review it but please don’t create confusion with alternate drafts.

Thanks,
Acee









The PBR model is the information model that is a collaboration between the PBR (draft-kini-i2rs-pbr-info-model-00) and the (draft-hares-i2rs-policy-info-model).   We hoped to have the agreement on the text early next week (just 1 technical discussion).   The author team has had meetings in August and September.



Please add the use case to the agenda.



One question – should I be submitting these I2RS configuration IM/DM as netmod models? If so, I will do this as well.



Sue



-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Dean Bogdanovic
Sent: Thursday, September 25, 2014 2:44 PM
To: Jeffrey Haas
Cc: i2rs@ietf.org<mailto:i2rs@ietf.org>
Subject: Re: [i2rs] IETF 91 meeting requested - call for agenda; status reports?



Jeff,



To kickstart the discussions



looking at what is needed in NETMOD and NETCONF for I2RS



datastore for I2RS (use cases for ephemeral data store)



working on ACL YANG model - with ACL model available and draft-ietf-netmod-routing-cfg-15 being fixed, PBR info model (draft-kini-i2rs-pbr-info-model-00) can be extended into data model. I'll try to submit the draft by the deadline (it is dependent on new draft-ietf-netmod-routing-cfg, probably draft-ietf-netmod-routing-cfg-16, being published)



Dean



On Sep 25, 2014, at 2:00 PM, Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>> wrote:



> Your chairs have been a bit over-busy recently with travel to unicast

> people doing various bits of chartered work.  This means we've been

> behind on some of our goals in terms of getting regular design

> sessions running.  I know that at least a couple calls have happened

> that I've missed that Sue Hares has done, so some progress is being made.

>

> We've requested a 1 hour time slot for IETF 91 in Honolulu to give us

> a chance to talk.  This is a call for agenda slots.

>

> This is also a call for status reports.

>

> We've had some productive discussion about requests to netmod/netconf,

> albeit ones that haven't converged yet.

>

> What have you been up to?

>

> -- Jeff & Ed

>

> _______________________________________________

> 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