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

Linda Dunbar <linda.dunbar@huawei.com> Wed, 07 October 2015 15:43 UTC

Return-Path: <linda.dunbar@huawei.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 EE3CD1AC42F for <i2rs@ietfa.amsl.com>; Wed, 7 Oct 2015 08:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 0KbgiDK3BQjc for <i2rs@ietfa.amsl.com>; Wed, 7 Oct 2015 08:43:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 210B81AC415 for <i2rs@ietf.org>; Wed, 7 Oct 2015 08:43:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CCE60930; Wed, 07 Oct 2015 15:43:21 +0000 (GMT)
Received: from DFWEML705-CHM.china.huawei.com (10.193.5.142) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 7 Oct 2015 16:43:21 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml705-chm ([10.193.5.142]) with mapi id 14.03.0235.001; Wed, 7 Oct 2015 08:43:11 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Susan Hares <shares@ndzh.com>, "i2rs@ietf.org" <i2rs@ietf.org>
Thread-Topic: [i2rs] draft-ietf-i2rs-rib-info-model-07 - WG LC from (10/6 to 10/20/2015)
Thread-Index: AdEAlyAxuYWhD++/Qk2AqdHuY4uxjAAf7pWg
Date: Wed, 07 Oct 2015 15:43:11 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657D6888C@dfweml701-chm>
References: <009a01d10098$2b03bfb0$810b3f10$@ndzh.com>
In-Reply-To: <009a01d10098$2b03bfb0$810b3f10$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.133.40]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657D6888Cdfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/CYJ2SfY3UTO7GBDRiNmq0Mktz2E>
Cc: 'Nitin Bahadur' <nitin_bahadur@yahoo.com>, "sriganesh.kini@ericsson.com" <sriganesh.kini@ericsson.com>
Subject: Re: [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 15:43:29 -0000

Support,

Linda

From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, October 06, 2015 7:36 PM
To: i2rs@ietf.org
Cc: 'Nitin Bahadur'; sriganesh.kini@ericsson.com
Subject: [i2rs] draft-ietf-i2rs-rib-info-model-07 - WG LC from (10/6 to 10/20/2015)

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