[i2rs] IETF sessions

"Susan Hares" <shares@ndzh.com> Fri, 04 November 2016 00:20 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8F13E1294B1 for <i2rs@ietfa.amsl.com>; Thu, 3 Nov 2016 17:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id WJcAIkP0i691 for <i2rs@ietfa.amsl.com>; Thu, 3 Nov 2016 17:20:33 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A23F129589 for <i2rs@ietf.org>; Thu, 3 Nov 2016 17:20:33 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: "Susan Hares" <shares@ndzh.com>
To: <i2rs@ietf.org>
Date: Thu, 3 Nov 2016 20:18:10 -0400
Message-ID: <045d01d23630$edadb4c0$c9091e40$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdI2LAECqyZhv9/0SaqxkPlOJDc5XQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/FX_mpjpqis27pGD0LluKmCxV7SA>
Cc: 'Russ White' <russ@riw.us>, "'Ersue, Mehmet \(Nokia - DE/Munich\)'" <mehmet.ersue@nokia.com>, 'Alia Atlas' <akatlas@gmail.com>, 'Mahesh Jethanandani' <mjethanandani@gmail.com>, 'Benoit Claise' <bclaise@cisco.com>, "'Alvaro Retana \(aretana\)'" <aretana@cisco.com>
Subject: [i2rs] IETF sessions
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 04 Nov 2016 00:20:35 -0000


The I2RS WG had 2 sessions for IETF 97.  One session (on Monday) was
schedule to settle any requirement issues prior to meeting with NETCONF or
NETMOD.  The second session was for the I2RS Data models.   At this point,
it appears that the requirements session will not be necessary.   The
requirements documents are going through the IESG or awaiting a revision
form the authors.   So, we believe we are at last through the requirements
phase of the work.   The next steps for the I2RS protocol and I2RS data
model changes is to work through these changes in NETMOD and NETCONF, and to
create open source implementations of these ideas. 

We plan to cancel the Monday meeting and just hold the WG session on
Wednesday from 15:20 - 16:20.  This email is to call for presentations to
see if all the presentations will be able to fit within single hour time

This session will focus on new model presentations for I2RS related models -
both protocol specific (BGP, OSPF, ISIS, MPLS) or protocol-independent.   At
that time, we will also present results from the I2RS work at the hackathon.
Due to the late announcement, we will be accepting presentations with drafts
that made the cut-off, drafts that you might published on the first day of
IETF (Monday), or ideas that you would like feedback on.  

Sue Hares and Russ White 

Status of I2RS Requirement documents 
The I2RS requirements for the additions to the Yang data modeling language
and NETCONf/RESTCONF protocols are making good progress through the IESG
publication progress.  Here's our status: 

RFC7920 - Protocol problem [done]
RFC7921 - I2RS architecture [done] 
RFC7922 - I2RS traceability
RFC7923 - I2RS pub-sub requirements 

draft-ietf-i2rs-protocol-security-requirements-17.txt:  approved for RFC
draft-ietf-i2rs-ephemeral-state-21.txt:  has two issues to address, but I
expect this will be completed by the IETF 97. 

draft-ietf-i2rs-security-environment-reqs-01:   This draft needs an update,
but the protocol work can continue without this draft.
(Draft-ietf-i2rs-security-environment-req-02 missed the update, but will be
available at IETF 97.  We'll have a short review discussion at IETF 97, but
the WG LC will start after IETF) 

draft-i2rs-hares-protocol-strawman-03.txt - will be updated with
experimental results, but the protocol suggestions will be forwarded to the
NETCONF/NETMOD Working groups as alternative drafts. 


-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of "IETF Secretariat"
Sent: Friday, October 21, 2016 7:21 PM
To: i2rs-chairs@ietf.org; shares@ndzh.com
Cc: i2rs@ietf.org; akatlas@gmail.com
Subject: [i2rs] i2rs - Requested sessions have been scheduled for IETF 97

Dear Susan Hares,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by the original request.

i2rs Session 1 (2:00:00)
    Monday, Afternoon Session I 1330-1530
    Room Name: Studio 2 size: 80
    i2rs Session 2 (1:00:00)
    Wednesday, Afternoon Session II 1520-1620
    Room Name: Studio 2 size: 80

Request Information:

Working Group Name: Interface to the Routing System Area Name: Routing Area
Session Requester: Susan Hares

Number of Sessions: 2
Length of Session(s):  2 Hours, 1 Hour
Number of Attendees: 50
Conflicts to Avoid: 
 First Priority: idr trill i2nsf rtgarea rtgwg netconf netmod  Second
Priority: bess nfvrg sdnrg sidr

Special Requests:

i2rs mailing list