Re: [i2rs] RIB Model draft

Alia Atlas <akatlas@gmail.com> Fri, 11 October 2013 12:47 UTC

Return-Path: <akatlas@gmail.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 3212F11E81BD for <i2rs@ietfa.amsl.com>; Fri, 11 Oct 2013 05:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 tagged_above=-999 required=5 tests=[AWL=-0.576, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, J_CHICKENPOX_33=0.6, NO_RELAYS=-0.001, SARE_UNSUB18=0.131]
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 S1g7ikkHM2+Q for <i2rs@ietfa.amsl.com>; Fri, 11 Oct 2013 05:47:03 -0700 (PDT)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id B412B11E81A9 for <i2rs@ietf.org>; Fri, 11 Oct 2013 05:47:00 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id g12so2417108oah.29 for <i2rs@ietf.org>; Fri, 11 Oct 2013 05:47:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JoF2oCwvddLhLKt3x5OtZqU80rlV9iQ9Ha9inJhIs2M=; b=CHsUKC52khfOBclm9lRuyL/y2yqWu9EVV93KBrRmm5Q83DO/xMGKy5uBJnP9QdhmRT eMG4DEUuVf/wqjURpXhqk43RK9F/UHlAj7GvXvibIWzomAHeaZW3TTpJh5tBWH52wacy aDSJdmbPjeVV40ehPL1jO02SlP/2GnUTW2u4/uF7Usm7VmGoqEeR2AxizblhVAb4ysoU 2lfQY9bfStvHE+7MjZHO5MDir6mPT+cKQ+ygyMsrXM+py9d/aEWdg++2veftxQyaLoia NzHCiDchsF3UwoE1+cVYi0Xu8QTAuI6Zc/t1NR69v6OVjcj38Aj+N5q4op/eP4TJv6Bz N28Q==
MIME-Version: 1.0
X-Received: by 10.182.142.2 with SMTP id rs2mr393147obb.60.1381495620180; Fri, 11 Oct 2013 05:47:00 -0700 (PDT)
Received: by 10.182.56.229 with HTTP; Fri, 11 Oct 2013 05:47:00 -0700 (PDT)
In-Reply-To: <019f01cec660$f2220940$4001a8c0@gateway.2wire.net>
References: <CE7C3959.305BD%nitinb@juniper.net> <019f01cec660$f2220940$4001a8c0@gateway.2wire.net>
Date: Fri, 11 Oct 2013 08:47:00 -0400
Message-ID: <CAG4d1rc=_TdeKmJunxAbBr5evi0p42BFnUF0LcfDa98RYdcuzw@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: "t.petch" <ietfc@btconnect.com>
Content-Type: multipart/alternative; boundary="001a11c20e26b322bc04e876831c"
Cc: Russ White <russw@riw.us>, "i2rs@ietf.org" <i2rs@ietf.org>, Nitin Bahadur <nitinb@juniper.net>, "Joel M. Halpern" <jmh@joelhalpern.com>
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 12:47:04 -0000

Tom,

A discussion would be great!  Why don't you start it?

Alia


On Fri, Oct 11, 2013 at 4:57 AM, t.petch <ietfc@btconnect.com> wrote:

>
> ----- 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>
>
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>