[Isis-wg] FW: [i2rs] I2RS requirements for IGP protocols

"Susan Hares" <shares@ndzh.com> Thu, 18 June 2015 22:37 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8BC11A1B2E for <isis-wg@ietfa.amsl.com>; Thu, 18 Jun 2015 15:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 B623ncMMXBAf for <isis-wg@ietfa.amsl.com>; Thu, 18 Jun 2015 15:37:34 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDF391A024E for <isis-wg@ietf.org>; Thu, 18 Jun 2015 15:37:33 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.166.245;
From: "Susan Hares" <shares@ndzh.com>
To: <isis-wg@ietf.org>
References: <009901d0aa16$e8465430$b8d2fc90$@ndzh.com>
In-Reply-To: <009901d0aa16$e8465430$b8d2fc90$@ndzh.com>
Date: Thu, 18 Jun 2015 18:37:31 -0400
Message-ID: <00c901d0aa17$5dc75a60$19560f20$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00CA_01D0A9F5.D6B8C7A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH8vG8wZvJB0MVebOQaJyjc6EC9TJ1atabg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/DaeS0dXgscTnwHnQHCFpXBYGPWs>
Cc: 'Jeffrey Haas' <jhaas@pfrc.org>, hannes@juniper.net, chopps@chopps.org
Subject: [Isis-wg] FW: [i2rs] I2RS requirements for IGP protocols
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2015 22:37:36 -0000

 

 

The I2RS WG is passing its requirements for I2RS protocol's to NETCONF.
These requirements include  ephemeral state, pub/sub, traceability,
authentication of I2rs client/agent, security and transport requirements.
As part of that work, we would like to confirm that the following things are
useful for the I2RS protocol to support.

 

.         IGP-REQ01: Track system-id used in ISIS instances and IS neighbors
on ISIS adjacencies  

.         IGP-REQ02: Allow ephemeral (temporary) configuration changes to
ISIS 

.         IGP-REQ03: Allow ephemeral configuration to fast-reroute in ISIS 

.         IGP-REQ04: Allow ephemeral load balancing configuration changes to
ISIS flows 

.         IGP-REQ05/REQ07: I2RS subscription (pub/sub) to ISIS notification
via I2RS  for interface, neighbor, database, and prefix 

.         IGP-REQ06: Subscription (pub/sub) or query of ISIS configuration
and dynamic statistics via I2RS (interface, neighbor, database) 

.         IGP-REQ08: Subscription (pub/sub) or query of  ISIS protocol
statistics 

 

The number IGP-REQxx refers to the numbering used in
draft-ietf-i2rs-usecase-reqs-summary-01
<http://datatracker.ietf.org/doc/draft-ietf-i2rs-usecase-reqs-summary/> .
Please let me know if these I2RS features ISIS changes that can help manage
short-term changes to ISIS topology for DDoS, changes to exits, or on-demand
bandwidth paths. 

 

 

How much yang model additions will these I2RS additions cost? 

All I2RS requirements can be implemented an ephemeral copy of the ISIS yang
module augmented by: a) 5+ notifications and b) I2RS L3 Topology model which
reads in the IGP data from ISIS. 

 

Thank you for your help. 

 

Sue Hares  

I2RS co-chair