IETF Logo Mail Archive

[i2rs] draft-ietf-i2rs-rib-info-model-07 - WG LC from (10/6 to 10/20/2015)

"Susan Hares" <shares@ndzh.com> Wed, 07 October 2015 00:36 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 C1F9F1B2F9C for <i2rs@ietfa.amsl.com>; Tue, 6 Oct 2015 17:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.354
X-Spam-Level:
X-Spam-Status: No, score=-96.354 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 JrbJt8u_5hQ4 for <i2rs@ietfa.amsl.com>; Tue, 6 Oct 2015 17:36:17 -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 92E351B2F8C for <i2rs@ietf.org>; Tue, 6 Oct 2015 17:36:17 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.84.146;
From: Susan Hares <shares@ndzh.com>
To: i2rs@ietf.org
Date: Tue, 06 Oct 2015 20:36:08 -0400
Message-ID: <009a01d10098$2b03bfb0$810b3f10$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009B_01D10076.A3F3A650"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdEAlyAxuYWhD++/Qk2AqdHuY4uxjA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/Mjnl9RgvISJy76HicIO_yQVPBHU>
Cc: 'Nitin Bahadur' <nitin_bahadur@yahoo.com>, sriganesh.kini@ericsson.com
Subject: [i2rs] draft-ietf-i2rs-rib-info-model-07 - WG LC from (10/6 to 10/20/2015)
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: <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: Wed, 07 Oct 2015 00:36:18 -0000

This begins a 2 week WG LC on draft-ietf-i2rs-rib-info-model-07.txt.   You
can obtain the document by going to: 

http://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-info-model/

 

The question you should consider: 

 

1)      Does this RIB info-model work will for read query and write query
for small number of routes (1-10 routes)?

2)      Does this RIB info-model work for a large number of routes 100,000
routes?  

3)      Is the next-hop methodology support everything you wish in the I2RS
RIB? 

4)      The default mode for I2RS transport is a secure encrypted transport.
Does this information model need to have any portion of the model available
over an insecure transport? 

 

Sue Hares

v2.23.0 | Report a Bug | By Email