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

"Susan Hares" <shares@ndzh.com> Sat, 27 September 2014 20:32 UTC

Return-Path: <shares@ndzh.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 CD7B01A02FE for <i2rs@ietfa.amsl.com>; Sat, 27 Sep 2014 13:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=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 HW8oppfYpMwr for <i2rs@ietfa.amsl.com>; Sat, 27 Sep 2014 13:32:14 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4CB1A02D6 for <i2rs@ietf.org>; Sat, 27 Sep 2014 13:32:13 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.172.144;
From: Susan Hares <shares@ndzh.com>
To: "'Acee Lindem (acee)'" <acee@cisco.com>, 'Jeffrey Haas' <jhaas@pfrc.org>
References: <20140925180055.GB1239@pfrc> <3C001E8E-FB91-4E31-9258-9E376F46AD8E@juniper.net> <00b501cfda04$2b4db130$81e91390$@ndzh.com> <D04C8E0F.3B4F%acee@cisco.com>
In-Reply-To: <D04C8E0F.3B4F%acee@cisco.com>
Date: Sat, 27 Sep 2014 16:32:08 -0400
Message-ID: <003201cfda92$1c49c230$54dd4690$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0033_01CFDA70.953A6C20"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQF6CdpPDPl0C8Ln1ozC47wAm7/GlQIExceRAawuzi4B220d0ZyUq+FQ
X-Authenticated-User: skh@ndzh.com
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/OVYNFWlbAEIfOA-qDNCNBV-Ob3g
Cc: 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 20:32:17 -0000

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
Subject: Re: [i2rs] IETF 91 meeting requested - call for agenda; status
reports?

 

 

 

From: Susan Hares <shares@ndzh.com>
Date: Friday, September 26, 2014 at 11:36 PM
To: Jeff Haas <jhaas@pfrc.org>
Cc: "i2rs@ietf.org" <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
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 < <mailto:jhaas@pfrc.org>
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

>  <mailto:i2rs@ietf.org> i2rs@ietf.org

>  <https://www.ietf.org/mailman/listinfo/i2rs>
https://www.ietf.org/mailman/listinfo/i2rs

 

_______________________________________________

i2rs mailing list

 <mailto:i2rs@ietf.org> i2rs@ietf.org

 <https://www.ietf.org/mailman/listinfo/i2rs>
https://www.ietf.org/mailman/listinfo/i2rs