Re: [irs-discuss] IRS Problem Statement Posted

Robert Raszuk <robert@raszuk.net> Mon, 30 July 2012 23:31 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: irs-discuss@ietfa.amsl.com
Delivered-To: irs-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23A4911E80BA for <irs-discuss@ietfa.amsl.com>; Mon, 30 Jul 2012 16:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level:
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
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 8vjzKEkYkd2s for <irs-discuss@ietfa.amsl.com>; Mon, 30 Jul 2012 16:31:30 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 1454911E809A for <irs-discuss@ietf.org>; Mon, 30 Jul 2012 16:31:29 -0700 (PDT)
Received: (qmail 522 invoked by uid 399); 30 Jul 2012 23:31:29 -0000
Received: from unknown (HELO ?130.129.19.9?) (robert@raszuk.net@130.129.19.9) by mail1310.opentransfer.com with ESMTPAM; 30 Jul 2012 23:31:29 -0000
X-Originating-IP: 130.129.19.9
References: <CC3C1DEF.28D6%tnadeau@juniper.net> <CE39F5249064D946AA3535E63A014619656FB98703@EUSAACMS0703.eamcs.ericsson.se> <CAG4d1rdS8pa=2cQFhrrV2ZRqdp91Zwf_GVMcWA7xFNFf7Mgh5w@mail.gmail.com> <50170D34.503@joelhalpern.com> <ED65813C-777D-4DA3-AA37-D371A365AD16@lucidvision.com>
In-Reply-To: <ED65813C-777D-4DA3-AA37-D371A365AD16@lucidvision.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <1FB014C5-8B5A-4D34-82AD-D8E64A0098FF@raszuk.net>
X-Mailer: iPad Mail (9B206)
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 30 Jul 2012 16:31:28 -0700
To: Thomas Nadeau <tnadeau@lucidvision.com>
Cc: Alia Atlas <akatlas@gmail.com>, Thomas Nadeau <tnadeau@juniper.net>, James Kempf <james.kempf@ericsson.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Subject: Re: [irs-discuss] IRS Problem Statement Posted
X-BeenThere: irs-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <irs-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/irs-discuss>
List-Post: <mailto:irs-discuss@ietf.org>
List-Help: <mailto:irs-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 23:31:31 -0000

Tom,

Yes indeed .. Clearly defining what problem are you trying to solve would be greatly helpful.

Best,
R.


Sent from my iPad

On Jul 30, 2012, at 3:54 PM, Thomas Nadeau <tnadeau@lucidvision.com>; wrote:

> 
> On Jul 30, 2012:3:39 PM, at 3:39 PM, "Joel M. Halpern" <jmh@joelhalpern.com>; wrote:
> 
>> Alia, I do have to disagree with one aspect of your characterization fo ForCES.  While the initial design goal was forwarding behavior, the protocol design is such that it is usable over a broad range of abstraction levels.
>> 
>> Similarly, depending upon exactly what we need, netconf + Netmad/YANG may be suitable / useable.
> 
>    We are not ruling out any existing solutions, either in whole or in part (modified). The goal right now is to define the problem space and a framework of components that can be used to solve that problem.
> 
>> On the other hand, I think that working out the problems and entities that need to be modeled first (which probably does need a dedicated working group), and then worrying about which protocol meets the requirements when we know what exactly we need.  At that point, the protocol work can be done wherever appropriate.
> 
>    Yes, that is precisely what the goals are right now.
> 
>    --Tom
> 
> 
>> 
>> yours,
>> Jitl
>> 
>> On 7/30/2012 6:27 PM, Alia Atlas wrote:
>>> Hi James,
>>> 
>>> Thanks for your thoughts.   Streaming (as I've heard) is not as good a
>>> description of the desired interface attributes as described in Sec
>>> 1.1, the functional overview.
>>> 
>>> IRS is NOT about having interfaces to the forwarding plane.  That's
>>> what ForCES is focused on.   This is about communication to a router
>>> to install/retrieve routing state into the routing system (FIB, IGPs,
>>> BGP, RSVP-TE, etc.)   IRS is NOT splitting the control plane from the
>>> router.
>>> 
>>> Are you suggesting that ForCES should drastically expand its scope?
>>> 
>>> Before we start debating what and whether to expand existing
>>> protocols, I think we need a common understanding of the problem we're
>>> trying to solve and the related framework.
>>> 
>>> Alia
>>> 
>>> On Mon, Jul 30, 2012 at 6:11 PM, James Kempf <james.kempf@ericsson.com>; wrote:
>>>> I don't understand why streaming is specified in this draft. And I don't understand why this draft isn't put in the Forces framework. Forces is a framework explicitedly designed for device to controller communication. Its major drawback it that it is a framework with a hole in the middle, in that there are no specified devices. This draft would fill that hole.
>>>> 
>>>> I don't think it is necessary to have a problem statement for router state update. Forces has already established that splitting the control plane into a separate device is, in some cases, an attractive design option. So I think this should be submitted to the Forces working group, or, at least, recast in the Forces framework.
>>>> 
>>>>                jak
>>>> 
>>>>> -----Original Message-----
>>>>> From: irs-discuss-bounces@ietf.org
>>>>> [mailto:irs-discuss-bounces@ietf.org] On Behalf Of Thomas Nadeau
>>>>> Sent: Monday, July 30, 2012 11:18 AM
>>>>> To: irs-discuss@ietf.org
>>>>> Subject: [irs-discuss] IRS Problem Statement Posted
>>>>> 
>>>>> 
>>>>> 
>>>>> Please review and discuss.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Tom, Alia, Ward
>>>>> 
>>>>> 
>>>>> http://lucidvision.com/draft-atlas-irs-problem-statement-00.txt
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> irs-discuss mailing list
>>>>> irs-discuss@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/irs-discuss
>>>>> 
>>>> _______________________________________________
>>>> irs-discuss mailing list
>>>> irs-discuss@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/irs-discuss
>>> _______________________________________________
>>> irs-discuss mailing list
>>> irs-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/irs-discuss
>>> 
>> _______________________________________________
>> irs-discuss mailing list
>> irs-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/irs-discuss
>> 
> 
> _______________________________________________
> irs-discuss mailing list
> irs-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/irs-discuss