Re: [i2rs] RIB Model draft

t.petch <ietfc@btconnect.com> Fri, 11 October 2013 09:07 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F8C21E80E0 for <i2rs@ietfa.amsl.com>; Fri, 11 Oct 2013 02:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.733
X-Spam-Level:
X-Spam-Status: No, score=-4.733 tagged_above=-999 required=5 tests=[AWL=-1.866, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZedtnGhvXOx7 for <i2rs@ietfa.amsl.com>; Fri, 11 Oct 2013 02:07:00 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe005.messaging.microsoft.com [207.46.163.28]) by ietfa.amsl.com (Postfix) with ESMTP id 61AB611E817D for <i2rs@ietf.org>; Fri, 11 Oct 2013 02:06:53 -0700 (PDT)
Received: from mail135-co9-R.bigfish.com (10.236.132.251) by CO9EHSOBE016.bigfish.com (10.236.130.79) with Microsoft SMTP Server id 14.1.225.22; Fri, 11 Oct 2013 09:06:52 +0000
Received: from mail135-co9 (localhost [127.0.0.1]) by mail135-co9-R.bigfish.com (Postfix) with ESMTP id B83CF80110; Fri, 11 Oct 2013 09:06:52 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(zz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzc2hz8275ch1de098h1033IL1de097h8275bh8275dhz2dh2a8h5a9h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail135-co9 (localhost.localdomain [127.0.0.1]) by mail135-co9 (MessageSwitch) id 1381482410468885_29774; Fri, 11 Oct 2013 09:06:50 +0000 (UTC)
Received: from CO9EHSMHS019.bigfish.com (unknown [10.236.132.228]) by mail135-co9.bigfish.com (Postfix) with ESMTP id 6D26E4E0085; Fri, 11 Oct 2013 09:06:50 +0000 (UTC)
Received: from AM2PRD0710HT003.eurprd07.prod.outlook.com (157.56.249.213) by CO9EHSMHS019.bigfish.com (10.236.130.29) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 11 Oct 2013 09:06:50 +0000
Received: from DB3PRD0411HT003.eurprd04.prod.outlook.com (157.56.253.53) by pod51017.outlook.com (10.255.165.38) with Microsoft SMTP Server (TLS) id 14.16.371.2; Fri, 11 Oct 2013 09:06:39 +0000
Message-ID: <019f01cec660$f2220940$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Nitin Bahadur <nitinb@juniper.net>, "Joel M. Halpern" <jmh@joelhalpern.com>, Russ White <russw@riw.us>
References: <CE7C3959.305BD%nitinb@juniper.net>
Date: Fri, 11 Oct 2013 09:57:42 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.53]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%0$Dn%JUNIPER.NET$RO%1$TLS%0$FQDN%$TlsDn%
Cc: i2rs@ietf.org
Subject: Re: [i2rs] RIB Model draft
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 11 Oct 2013 09:07:15 -0000

----- Original Message -----
From: "Nitin Bahadur" <nitinb@juniper.net>
To: "Joel M. Halpern" <jmh@joelhalpern.com>; "Russ White" <russw@riw.us>
Cc: <i2rs@ietf.org>
Sent: Thursday, October 10, 2013 7:13 PM
<snip>
>
>AS Paths are a BGP construct.  If you are not running BGP then the
>question above (about two paths from the I2RS agent) would seem to
>apply.  If you do have a BGP running, then the BGP is usually where
that
>sort of policy lives.  My concern is that this mechanism assumes a RIB
>agent that handles BGP specific operations.  I would prefer to leave
BGP
>mediation to the BGP model.

There were folks who had expressed interest in inter-domain paths.
That's
why this
was added. I agree with you that the handling logic will be BGP'ish and
there is an
implicit assumption that the RIB agent can handle this.

However, it's obvious (at least to me), that most of the use-cases for
I2RS will be
intra-domain and a device that does not support inter-as/bgp should be
fine for
most of the deployment use-cases.

<tp>
I keep on thinking that producing designs without agreed requirements,
use cases, is often a costly mistake.

My thinking on use cases was quite different, but unless and until we
have the discussion on eg
 draft-white-irs-use-case-00.txt et al.
who knows?

Tom Petch




<snip>